Cell broadcast Testbed

Test CB messages in your Lab using a Mini EPC (MiniCore) and LTE eNodeB (LTE LabKit)

The cell broadcast center testbed is a complete network bundle that allows testing the transmission of messages to mobile phones.

It includes the LTE LabKit (LTE eNodeB) and the MiniCore (MME). It is fully configured and intended for use as an LTE cell broadcast center testbed and learning environment according to ETSI Rel. 15.

Cell Broadcast (CB) is a one-to-many geo-targeted messaging system. A broadcast message can be sent out from one cell, a set of cells within one area, or an entire network. 

Components

  • MiniCore
    » A software-defined MME component with CBS standard.
    » This is in the operator's radio network, and it manages the group of cells.
    » MiniCore disseminates the Cell Broadcast message to the targeted cells.
  • LTE LabKit
    » A highly configurable test eNodeB/BTS
    » As a cell broadcasting testbed, it works as a Radio Node.
    » This is the component that sends the Cell Broadcast message wireless to the mobile devices.

Benefits of using a testbed for your CBC

The main benefit is that it gives you the possibility to test emergency broadcast without actually delivering emergency messages to the general public. You can do a small limited test in the laboratory of emergency broadcast and still involve a real core network equipment without the danger of accidentally releasing a test message to everyone in the region.

The CBC testbed is developed according to the procedures described in 3GPP TS29.168 (SBc-AP standard) version 15.5.0, section 9.1.3.4 Warning Message Delivery Procedure in E-UTRAN.

  • Fully configured, fully functional CBC testbed
    » Your testing efforts must give you control over the network and be fast and easy to implement.
    » The Cell Broadcast Testbed is providing you with full control over the testing network.
  • Cost-effective solution that increases your revenue
    » You can register a positive cash flow due to the fact that the CB Testbed is a cost-effective network solution that spares you of the costs of testing CB messages with the real operator network.
  • Easy to install, light and silent equipment
    » The CB Testbed comes already set up – just connect the equipment to the internet and start operating.
    » You can install the Testbed on your desk and start operating. It can even be taken on the road for easier demos or presentations of Cell Broadcasting technology.
  • Easy to purchase
    » We implemented the credit card purchasing method to ease the acquisition process.
    » The price is public and you can decide your expenses and your ROI before spending time and money on the pre-sale process.
CBC testbed

Specifications

  • WRITE-REPLACE-WARNING-REQUEST Request/Indication
  • WRITE-REPLACE-WARNING-CONFIRM Response/Confirm
  • STOP-WARNING-REQUEST Request/Indication
  • STOP-WARNING-CONFIRM Response/Confirm
  • WRITE-REPLACE-WARNING-INDICATION Request/Indication - this is sent to all connected CBCs
  • STOP-WARNING-INDICATION Request/Indication - this is sent to all connected CBCs

Functionality of the CBC testbed

The Cell broadcast center testbed MME can be connected to multiple CBCs. The CBC establishes the SCTP association.

If neither the List of TAIs IE, nor the Global eNB ID IE (if this is supported) are present in WRITE-REPLACE WARNING REQUEST message, the MME is forwarding the message towards all connected eNBs.

  • MME functionality
  • WRITE-REPLACE-WARNING-REQUEST/Confirm
    • Send to a single TAI: the message is sent to the corresponding ENB, and generate confirm with success
    • Send to both TAIs:
      • both connected: message sent to both ENB, and generate confirm with success
      • one of the ENBs is down: message set to the up ENB, generate confirm that says the TAI for which the warning message could not be delivered
    • List of TAI contains an unknown TAI: the CBC testbed generates confirmation that says that cannot deliver to that TAI
    • List of all unknown TAIs: Generates Confirmation with Cause Tracking area not valid
    • No TAI list or ENBId provided: sends to all ENBs
    • EnbID provided: sends to Enb with that ID, generate confirm
      • with success if ENB is up
      • with failure otherwise
    • activate WRITE-REPLACE-WARNING-INDICATION if set in the request
  • STOP-WARNING-REQUEST/Confirm
    • Send to a single TAI: check that the message is sent to the corresponding ENB, and generate confirm with success
    • Send to both TAIs:
      • both connected: message sent to both ENB, and generate confirm with success
      • one of the ENBs is down: message set to the up ENB, generate confirm that says the TAI for which the warning message could not be delivered
    • List of TAI contains an unknown TAI: generate confirm that says that cannot deliver to that TAI
    • List of all unknown TAIs: Generate Confirm with Cause Tracking area not valid
    • No TAI list or ENBId provided: send to all ENBs
    • activate STOP-WARNING-INDICATION if set in the request
  • WRITE-REPLACE-WARNING-INDICATION procedure
    • this is activated only if requested by the CBC and if configured in MME
  • WARNING-REPLACE-REQ was sent to 2 EnBs, it waits answers from both
    • if both report failure, the testbed generates WRITE-REPLACE-WARNING-INDICATION to CBC with no BroadcastAreaList
    • if one fails, one succeeds, it generates WRITE-REPLACE-WARNING-IND to CBC with BroadcastAreaList containing the area that succeeded
    • if both succeed, then it generates WRITE-REPLACE-WARNING-IND to CBC with BroadcastAreaList containing both
    • if multiple CBCs are connected to the MME, the message is sent to all
  • STOP-WARNING-INDICATION procedure
    • check that is activated only if requested by the CBC and if configured in MME
    • KILL REQ was sent to 2 EnBs, wait answers from both
      • if both report failure, generate STOP-WARNING-INDICATION to CBC with no BroadcastCancelledAreaList, and with a BroadcastEmptyAreaList containing the ENB IDs of both ENBs
    • if one fails, one succeeds, generate STOP-WARNING-INDICATION to CBC with BroadcastCancelliedAreaList containing the list from the ENB that succeeded and BroadcastEmptyArea containing the ENB id that failed
    • if both succeed, generate STOP-WARNING-INDICATION to CBC with BroadcastCancelledAreaList containing both list from both ENBs
    • check that the STOP-WARNING-INDICATION contains the same message identifier as the request
    • check that if multiple CBCs are connected to the MME, the message is sent to all
  • eNodeB functionality
  • WRITE-REPLACE WARNING REQUEST
    • If the ENB is already broadcasting a message and it receives a message
      • with a different MsgID and/or Serial Number from those broadcasted and Concurrent Warning Message Ind is not present, the ENB replaces the broadcasted message with the new one.
      • with a different MsgID and/or Serial Number from those broadcasted and Concurrent Warning Message Ind is present, the ENB adds the message to the one already broadcasted.
      • with a MsgID and/or Serial Number that is already broadcasted, the ENB will not start a new broadcast, but simply responds with a confirmation
    • If the ENB is not already broadcasting a message, the ENB broadcasts the message
      • in ConcurrentWarningMessageInd is present and the NumberOfBroadcastRequested is 0, the message is broadcasted indefinitely until asked to stop by MME. If RepetitionPeriod is 0, the message is only broadcasted once
    • if WarningAreaList is not included, message is broadcasted to all cells from the ENB
    • if WarningType is included, the ENB broadcast the message ignoring RepetitionPeriod and Number of Broadcasts IE (see TS 36.331). WarningSecuriryInformation is added for the primary information in present in the S1AP request.
    • if DCS and WarningMessageContents are included, the broadcast will honour the Repetition period and Number of Broadcasts. Warning Area Coordinates is broadcasted with the warning message if included.
    • ENB responds with Write-ReplaceWarningResponse to the MME:
      • if BroadcastCompletedAreaList is not included, the MME will interpret this as failure to broadcast to all cells in the ENB