BSC support for CBSP (cell broadcast service protocol)
Right now, the only way to send cell broadcast messages is to use the BSC VTY.
3GPP Specifies CBSP in TS 48.049 as the protocol used between BSC and CBC to configure which kind of messages shall be broadcast where, and for how long.
It's a simple TLV based protocol encapsulated in TCP, so the protocol itself should be rather easy to support. However, it requires an underlying SMSCB scheduler that provides the required functionality for routing/scheduling. See #3536.
gsm0808_utils: Introduce gsm0808_msgb_put_cell_id_u()
This function is doing the bulk work of encoding a given Cell
ID List item. gsm0808_enc_cell_id_list2() is modified to be a
wrapper / loop around the new function.
The purpose of this is to expose Cell ID List Entry encoding
so that the upcoming CBSP protocol encoder can re-use this code.
gsm0808_utils: Add gsm0808_decode_cell_id_u()
This function parses a single Cell ID list element into a
'union gsm0808_cell_id_u'. This function is going to be used
by the upcoming CBSP support.
CBSP (Cell Broadcast Service Protocol; 3GPP TS 48.049) support
This introduces definitions as well as a parser+encoder for the
Cell Broadcast Service Protocol (CBSP) as specified in 3GPP TS 48.049.
CBSP is used on the interface between CBC and BSC.
#9 Updated by laforge almost 2 years ago
- Priority changed from Low to Normal
I've been re-reading specs and thinking a bit more about implementation. They key part of this seems to be:
The allocator takes care of determining if a new SMSCB message of given size (number of pages), repetition period and category(priority) can still be sent over the given channel (basic/extended) at a given BTS.
This allocator then is executed for each cell in the list of cells where the message is to be broadcast, and the results from the allocator determine if we send a CBSP WRITE-REPLACE COMPLETE or a WRITE-REPLACE FAILURE. Where interestingly, the FAILURE can very well be a partial failure, containing a list of cells in which it failed and in which it succeeded.
The scheduler runs for each BTS separately. It has a list of SMSCB which are to be broadcast in this BTS, and must determine which page of which SMSCB message to transmit at which given point in time to ensure the repetition period is respected
The CBSP client will connect/reconnect to the CBC, ensure the link works (keep-alive).
It will [optionally] use some Osmocom-propietary means to identify the BSC (and its served cells) to the CBC, avoiding the need for manual configuration of this data out-of-band to the CBC.
The spec appears to require the BSC to accept an inbound TCP connection from the CBC. We should support this for interoperability. Only one CBC can ever talk to a BSC, so we should have some kind of "either client or server" configuration. Only one connection shall be accepted in the server-side socket.
Iterative approach¶In terms of an interative implementation approach, the following short-cuts could be taken while stubbing out some of the functionality:
- assume that there's unlimited CBCH capacity, i.e. accept all WRITE-REPLACE even if they cannot be scheduled. Works for low CBCH load situations, which are likely in practise
- always broadcast each SMSCB on all cells in the BSC, avoiding implementing 5 different ways on how the Cell List can be encoded in CBSP
Let's first implement BSC_Tests.ttcn coverage for SMSCB/CBSP and then use that to drive the implementation. Emulating a number of BTSs on the RSL side as well as the CBC on the CBSP side are sufficient for testing anything we need.
#11 Updated by laforge over 1 year ago
- % Done changed from 10 to 60
laforge/cbspbranch of osmo-bsc.git. It is currently untested, but should do the following things:
- handling of WRITE_REPLACE, KILL and RESET procedures via CBSP from the CBC
- VTY configuration for the CBSP link
- CBSP TCP client and server role
- CBSP LOAD QUERY
- CBSP MSG STATUS QUERY
- tests, tests, tests
#13 Updated by laforge over 1 year ago
- % Done changed from 60 to 80