Bug #2964
handover_decision_2: measurement report number compared to lchan->meas_rep_last_seen_nr often overflows to zero (255 range) and hence an old report may be seen as new every once per 255 cycle
Start date:
02/19/2018
Due date:
% Done:
0%
Spec Reference:
Description
the algorithm should probably clear out all meas_rep_last_seen_nr in lchans that match the just incoming mr.
Related issues
History
#1 Updated by neels almost 2 years ago
- Related to Feature #1606: hand-over for load distribution among BTSs added
#2 Updated by neels over 1 year ago
- Assignee set to neels
(assigning to me to avoid this being lost in unassigned-land)
#3 Updated by neels over 1 year ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
#4 Updated by neels about 1 month ago
- Status changed from In Progress to New
- Priority changed from Normal to Low
- % Done changed from 80 to 0
trying to recap the state of this issue, I can't see any reason why this would be at 80%.
Resetting to indicate that we would need testing to play through a situation of erroneously using an old measurement report as new.
Not sure if this is even remotely realistic.
