Project

General

Profile

Bug #2525

BA-IND in neighbor lists is not different on SI2xxx and SI5xxx

Added by laforge 10 months ago. Updated 9 months ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
10/01/2017
Due date:
% Done:

100%

Estimated time:
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.

History

#1 Updated by laforge 10 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

#2 Updated by laforge 10 months ago

  • % Done changed from 20 to 90

#3 Updated by laforge 10 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

patches merged to openbsc.git and osmo-bsc.git

#4 Updated by laforge 9 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)