Feature #1630
closedImplement SI2quater generation in OpenBSC / OsmoBTS
100%
Description
Implementation of E-UTRAN neighbor cell reporting via System Information 2 quater in OsmoBTS/OsmoBSC/OsmoNITB software including unit
tests and system test and fixing existing known SI2ter scheduling issues.
- Verifying existing SI2ter is scheduled, use something like osmo-bts + gsmtap to see that it is scheduled at the right frame
- bitvec for encoding the SI2 quater messages
- Scheduling (segmented) SI2 quater messages in osmo-bts
- VTY options to represent them. This is the most involved one so the actual interface and commands should be discussed.
OsmoBSC/OsmoNITB¶
- Extending SI3 to indicate presence of SI2quater
- Encoding of SI2quater messages with only the following optional parts (details see above):
- Priority and E-UTRAN Parameters Description, containing
- Serving Cell Priority Parameters Description
- E-UTRAN Parameters Description, containing
- Repeated E-UTRAN Neighbour Cells, with all their fields
- Repeated E-UTRAN Not Allowed Cells, with all their fields
- only implement the fixed single PCID (which can be repeated) encoding, not the bit-map / bit-masking encoding options
- Repeated E-UTRAN PCID to TA mapping
- Priority and E-UTRAN Parameters Description, containing
- Implementing "fragmentation" of SI2quater over multiple messages with their respective Index/Count fields
- Sending SI2quater via A-bis RSL to the BTS
- "E-UTRAN Measurement Parameters Description"
- "GPRS E-UTRAN Measurement Parameters Description"
- "Extended EARFCNs" (EARFCN > 65535)
- "MEASUREMENT INFORMATION" messages to instruct MS to provide measurement results for LTE while on GSM/GPRS
- "Fast Acquisition" with UTRAN_Start/UTRAN_Stop
OsmoBTS¶
- Fixing the existing SI2ter scheduling issues that may exist
- Implement receiving SI2quater via A-bis RSL, taking into account there mgiht be multiple fragmented messages with index/count
- Implement scheduling of SI2quater
Test Cases¶
- Implement unit tests for SI2qater encoding in BSC (part of "make check")
- Impement code that receives GSMTAP BCCH frames from OsmoBTS and verifies that only the correct expected SI messages occur at the right point in tme (FN / ...). This will be a separate program/tool, which hopefully we can later run together with osmo-bts-virtual as part of "make check", as the virtual BTS requires no real BTS hardware.
Related issues
Updated by laforge about 8 years ago
feel free to create a child ticket in the OsmoBTS project to track the status of the BTS-specific parts.
Updated by laforge about 8 years ago
The SI2quater description can be found Chapter 10.5.2.33b of TS 44.018 version 13.0.0 Release 13. Please use only this specifiation document/version, and not any other/older versions for reference.
Updated by msuraev about 8 years ago
- File si_check.gawk added
- Status changed from New to In Progress
Attached is GNU Awk script which checks whether SI in a given .pcap are scheduled properly. Usage example is inside. Since script works with .csv as input it could be easily adopted later on to serve as part of "make check".
Using that script I've checked .pcap obtained via osmocom-bb's ./mobile app - no errors in 2ter (or any other) scheduling found so far.
Updated by laforge about 8 years ago
- Related to Feature #1660: segmented SI2quater support added
Updated by msuraev about 8 years ago
Improved version of test script will be merged into osmo-bts/contrib.
Updated by laforge about 8 years ago
- Related to Feature #1666: Implement UARFCN support for SI2quater added