The Cell Broadcast Service in the test set allows you to send cell broadcast messages to the mobile station that are transmitted at a defined repetition interval (see Cell Broadcast Setup - General for more information). This allows the mobile station to receive the message even if entering the cell after the first transmission. The cell broadcast messages can be from one to fifteen pages in length, and are transmitted by the test set until the cell broadcast service is disabled or the state of the message(s) being transmitted is set to OFF.
The test set can enable up to three different messages to be transmitted each Repetition Period using the Cell Broadcast Service. The repetition period can potentially be set smaller than the time it takes to transmit all enabled messages, so priority is given to the messages in the following order (from high to low): message 1, message 2, then message 3. If there is not enough space to transmit the enabled messages, the test set either truncates the lowest priority messages or does not send them.
There are several message parameters that the test set allows you to set. It is important that you configure your mobile station to receive cell broadcast messages. This is done by enabling reception of messages in your mobile station and specifying the message parameters that it can receive, and set the parameters according to the type of cell broadcast message your mobile station is allow to receive. Cell broadcast messages are not acknowledged by the mobile station.
In addition to the pre-defined text strings, you can specify a custom text string and custom data to be sent in a cell broadcast message. See Cell Broadcast Messages -Content for more information on configuring the contents of the cell broadcast message.
The Cell Broadcast messages are transmitted by the Broadcast and Multicast Control (BMC) protocol layer over the CTCH (Common Traffic Channel) logical channel. The messages are sent using DRX (Discontinuous Reception) on the CTCH, and the CBS Schedule message states which fragments of CBS messages will be sent in specific frames. The MAC layer multiplexes the CTCH onto the FACH transport channel with the CCCH (Common Control Channel) logical channel. The FACH is then multiplexed onto the S-CCPCH (Secondary Common Control Physical Channel) with the PCH (Paging Channel) transport channel, which also uses DRX to transmit in particular frames. The test set gives priority to the PCH over the FACH. Thus, it is possible that CBS data might not be transmitted in the intended slot because the slot contains PCH data instead. If this occurs, the CBS data is sent in the subsequent slot, and the CBS data for the subsequent slot is discarded by the test set.
The BMC is responsible for the handling, scheduling and transmission of CBS messages. Its purpose is to allow the UE to selectively receive messages using Discontinuous Reception (DRX), by broadcasting a CBS Schedule Message in addition to the CBS message. The CBS schedule message contains information about subsequent CBS messages, including the timing of each transmission in the next schedule period. Each schedule period consists of transmission blocks called Common Traffic Channel Block Sets (CTCH-BS), and contains information about the subsequent scheduling period. The number of blocks in the scheduling period is limited by the 8-bit "Length of CBS Scheduling Period"; the value range being 1 to 256. Additionally, the CBS Schedule Message contains an 8-bit field "Offset to Begin CTCH-BS Index", ranging from 1 to 255, which points to the starting block of the next CBS Schedule period.
The CTCH is defined by 3GPP TS 25.301 as a point to multipoint unidirectional channel for the transfer of dedicated user information for all or a group of specified UEs. For CBS, the MAC layer multiplexes the CTCH onto the FACH with a fixed transport block size and TTI, where TTI is the transmission time interval that the FACH carries the CTCH. The TTI for the FACH is fixed at 10 ms in the test set, and can therefore transmit data 100 times a second. The actual TTI intervals in the FACH to be utilized by the CTCH are determined by the CTCH Allocation Period and the CBS Frame Offset parameter settings.
The block size of the FACH is fixed in the test set so that 20 octets of data are available for each CTCH interval. Some of this space is used up for RLC headers. The formula to determine the number of blocks needed to carry a message of size X octets is:
Number of Blocks = (X+20)/19
. The repetition period and allocation period both affect the bandwidth of CBS messages. If there is space to transmit only a portion of a message, the test set will truncate the message where possible and lower priority messages are not sent.
All three of the messages available for use in the test set's Cell Broadcast Service can be configured independently. The content of each message can include either one of two predefined text messages, a custom text message or a custom binary/UCS2 message.
There are several configurable parameters for each cell broadcast message. The serial number is made up of three of these parameters: Geographical Scope, Message Code, and Update Number as shown in the diagram below. Refer to 3GPP TS 23.041 version 9.6.0 section 22.214.171.124 for more information about cell broadcast message parameters.
|Octet 1||Octet 2|
|GS||Message Code||Update Number|
Additionally, each message is classified by topic and allocated a message identifier, data coding scheme, and message content. The following list contains all the configurable cell broadcast message parameters offered by the test set.
State- allows you to configure which messages are sent using CBS. The message state must be
ONfor each message you want to send. The
Statefor Message 1 is set to
The GPIB command for this parameter is CALL:SMService:CBRoadcast:MESSage[<n>]:STATe .
The GPIB command for this parameter is CALL:SMService:CBRoadcast:MESSage[<n>]:GSCope .
The GPIB command for this parameter is CALL:SMService:CBRoadcast:MESSage[<n>]:CODE .
This parameter is used to identify a particular version of a message. This is useful for reporting a dynamic situation, where a message may be reporting one event (such as road works or road construction ahead), but the details change periodically (the length of the tail-back or traffic jam caused, for example). A mobile station which remains in one cell for a length of time receives messages with the same message code but increments the update numbers as updated versions of the same message are received. A mobile station that has just entered a cell receives only the most recent version of the message, followed by any subsequent versions. The update number wraps from 15 to 0.
The GPIB command for this parameter is CALL:SMService:CBRoadcast:MESSage[<n>]:UPDate .
Several categories of message topics are identified in 3GPP TS 23.041 version 9.6.0 section 126.96.36.199.2. The main topics are location services (LCS), the earthquake and tsunami warning system (ETWS), and the commercial mobile alert system (CMAS). Many message identifier values are reserved for future use but will likely be specified in future releases of 3GPP TS 23.041.
ETWS and CMAS are part of the public warning system (PWS) required for use in the United States. Message identifier values in the decimal range 4352 to 4356 are used for ETWS. CMAS defines three classes of warning notification: presidential, imminent threat and child abduction emergency (e.g. Amber Alert). Message identifier values within the decimal range 4370 to 4399 are used for CMAS. The exact meaning of each message identifier value is specified in 3GPP TS 23.041 version 9.6.0 section 188.8.131.52.2.
The GPIB command for this parameter is CALL:SMService:CBRoadcast:MESSage[<n>]:IDENtifier .
Data Coding Scheme Specification
The GPIB command to specify the which method is used is CALL:SMService:CBRoadcast:MESSage[<n>]:DCSCheme[:SPECify] .
Data Coding Scheme Language
This parameter sets the data coding scheme value associated with the indicated language. The data coding scheme indicates the intended handling of messages, the alphabet and coding of the message content, and the associated language of the text. Changing this parameter does not translate the text of a message or change the message contents; it is used to configure the message's data coding scheme value.
The GPIB command to specify the how the mobile station interprets the content of received text messages by specifying a language is CALL:SMService:CBRoadcast:MESSage[<n>]:DCSCheme:LANGuage .
Data Coding Scheme Value
This parameter sets the 8-bit data coding scheme value that indicates the intended handling of messages, the alphabet and coding of the message content, and the associated language of the text. Changing this parameter does not translate the text of a message, it is used to automatically configure the message's data coding scheme.
The GPIB command to specify the how the mobile station interprets the content of received text messages by specifying the data coding scheme value is CALL:SMService:CBRoadcast:MESSage[<n>]:DCSCheme:VALue .
Contentassociates the message with the actual data to be sent by the test set. See Cell Broadcast Messages -Content for more specific information on the cell broadcast messages that can be sent from the test set.
The GPIB command for this parameter is CALL:SMService:CBRoadcast:MESSage[<n>]:CONTent .
The repetition period determines how often the cell broadcast messages are transmitted. The repetition period is applied to all cell broadcast messages. The test set checks the value of the repetition period every time a schedule is built. If the value has changed from its previous value, then the next message repetition time is recalculated based on the new repetition period setting.
Several Cell Broadcast Service (CBS) message options are available which allow you to choose or create messages to be sent. You can set the
Custom Text, or Custom Data
. See the sections below for more information about these settings.
This instrument provides functional testing of cell broadcast SMS by sending up to three broadcast messages to the device under test. Two fixed text messages and user defined text or binary/UCS2 messages are available for selection. The second fixed message spans multiple pages.
You can set the cell broadcast message to send a customized text message by setting the Content
parameter to Custom Text
. You can define the text for the custom text cell broadcast message using the following GPIB command:
For the custom user defined text message, the test set accepts a 7-bit ASCII string. This string is then encoded using the ETSI Default Alphabet before it is transmitted. The ASCII code for each character in this string is mapped to the ETSI Default Alphabet character with the same code. Characters present in the user defined text message whose ASCII and ETSI Default Alphabet codes are not identical will be received and displayed by the mobile station as the ETSI Default Alphabet character with the original ASCII character's code. This behavior is only noticeable with certain user defined text messages as all of the predefined text messages use only alphanumeric and basic punctuation characters.
You can set the cell broadcast message to send a customized data message by setting the Content
parameter to Custom Data
. You can define the binary data/UCS2 for the custom data cell broadcast message using the following GPIB command: