Project

General

Profile

Feature #3536

BSC: support for repeated scheduling of SMSCB messages

Added by laforge about 1 year ago. Updated 3 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
Start date:
09/09/2018
Due date:
% Done:

100%

Spec Reference:
Tags:

Description

So far, the only way to have a SMSCB message sent is to use the VTY to manually send a message to a specific BTS.

So the user needs to:
  • know exactly which BTS to sen the message via
  • repeat the comamnd or the commands to repeat the transmission of that message
What's missing is some kind of scheduler that would take care of
  • repeatedly re-broadcasting messages until some expiration time is reached
  • round-robin iterating over multiple messages
  • allow messages to have CID/LAC or network-wide scope and take care of sending it to all CBCH-enabled BTSs within that scope
  • properly prioritize emergency (ETWS/CMAS/...) messages

If this is implemented, it should be done with keeping TS 48.049 (CBSP) in mind. The capabilities required by CBSP should be supported to allow easy integration of CBSP.


Related issues

Related to OsmoBSC - Feature #3537: BSC support for CBSP (cell broadcast service protocol)Resolved05/06/201905/06/2019

History

#1 Updated by laforge about 1 year ago

  • Related to Feature #3537: BSC support for CBSP (cell broadcast service protocol) added

#2 Updated by laforge about 1 year ago

  • Tags set to SMSCB

#3 Updated by laforge 7 months ago

  • Assignee set to laforge

#4 Updated by laforge 6 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 60
the bulk of the work on the scheduler has been implemented together with the CBSP protocol handing in the laforge/cbsp branch 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
  • building a scheduler data structure from the pages of the active SMSCB, taking into account their individual broadcast periods/intervals
  • removing SMSCB from the scheduler once the requested number of broadcasts has completed
  • providing a function to pull one SMSCB page from the scheduler
  • VTY configuration for the CBSP link
  • CBSP TCP client and server role

The scheduler runs separate for each BTS, and each BTS has separate scheduler instances for BASIC and EXTENDED CBCH

These parts are missing:
  • actually sending the 'pulled' SMSCB pages to the BTS for actual transmission
  • CBSP LOAD QUERY
  • CBSP MSG STATUS QUERY
  • tests, tests, tests

#5 Updated by laforge 5 months ago

  • Priority changed from Normal to Urgent

#6 Updated by laforge 3 months ago

  • % Done changed from 60 to 80

#7 Updated by laforge 3 months ago

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

all patches merged

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)