Actions
Bug #2525
closedBA-IND in neighbor lists is not different on SI2xxx and SI5xxx
Start date:
10/01/2017
Due date:
% Done:
100%
Spec Reference:
Description
Each SI2xxx and SI5xxx type message contains a BA-IND flag that can be 0 or 1. In our case,
it's typically 0, except fro SI2quater, where it is 1.
When a MS sends measurement reports, it can indicate to which BA-IND the report belongs. This is commonly used to differentiate between reports against neighbor lists communicated on BCCH (SI2xxx) and reports against neighbor lists communicated on SACCH (SI5xxx).
Let's make sure we set all SI2xxx BA-IND to 0 and all SI5xxx BA-IND to 1 to facilitate this behavior.
Actions
