Bug #3002
openHO2: handover decision for dynamic timeslots
0%
Description
The recent handover_decision_2.c hasn't been duly tested in the presence of dynamic timeslots.
Particularly TCH/F_TCH/H_PDCH timeslots are potentially both TCH/F or TCH/H, which might require another spin on the handover_decision_2.c code.
Related issues
Updated by neels over 5 years ago
- Blocked by Bug #2963: Measurement Reports cease to be useful some time into a voice call / after handover (not sure which project has the bug / bugs yet) added
Updated by neels over 5 years ago
(need to get useful measurement reports to be able to test this properly, hence blocked-by #2963)
Updated by neels over 5 years ago
- Related to Feature #1606: hand-over for load distribution among BTSs added
Updated by neels about 5 years ago
Aspects to consider:
It is benificial if PDCH are in consecutive timeslots.- If dynamic timeslots are in use, it makes sense to trigger re-assignment to move them as far away from dedicated PDCH as possible.
- If a dedicated TCH timeslot becomes available, it makes sense to re-assign away from a dyn TS towards a dedicated timeslot.
An unused dynamic timeslot may count as both 1 free TCH/F and 2 free TCH/H. If one TCH/H becomes used, this implicitly also reduces the number of free TCH/F. The lchan picking algorithm must not get confused by that.
A dynamic timeslot being available as PDCH is benificial to GPRS service. So, if a neighboring cell is unloaded and has good rxlev, we may want to handover away from dynamic timeslots to make room for PDCH. rxlev vs PDCH tradeoff should be configurable.
Updated by neels about 5 years ago
- Related to Feature #1608: various handover improvements, meta-issue added
