8 MS/UE Functionality
23.0413GPPRelease 18Technical realization of Cell Broadcast Service (CBS)TS
8.1 General MS/UE Functionality
Only GSM [The MS is responsible for recombination of the blocks received via the radio path to reconstitute the CBS message.]
The precise method of display of CBS messages is outside the scope of 3GPP specifications, however it is assumed that an MS/UE will:
|
MS |
UE |
|
|
Discard sequences transferred via the radio path (see 3GPP TS 44.012 [7]) which do not consist of consecutive blocks. |
Discard corrupt CBS messages received on the radio interface. |
|
|
Have the ability to discard CBS information which is not in a suitable data coding scheme. |
||
|
Have the ability to discard a CBS message which has a message identifier indicating that it is of subject matter which is not of interest to the MS/UE. |
||
|
Have the ability to detect duplicate messages as specified in clause 8.2; |
||
|
Have the ability to transfer a CBS message to an external device, when supported ; |
||
|
Optionally enter CBS DRX mode based upon received Schedule Messages (see 3GPP TS 44.012 [7]); |
Enter CBS DRX mode based upon received Schedule Messages (see 3GPP TS 25.324 [19]). |
|
|
Optionally skip reception of the remaining block(s) of a CBS message which do(es) not contain cell broadcast information (see 3GPP TS 44.012 [7]); |
Not applicable. |
|
|
Optionally read the extended channel. |
Not applicable for UMTS, E-UTRAN, and NG-RAN. |
|
|
Enable the user to activate/deactivate CBS through MMI |
||
|
Enable the user to maintain a "search list" and receive CBS messages with a Message Identifier in the list while discarding CBS messages with a Message Identifier not in the list. |
||
|
Discard CBS messages in Message Identifier value range "A000hex-AFFFhex" unless received from HPLMN, EHPLMN, PLMN that is equivalent to HPLMN or EHPLMN, or a subscribed SNPN. |
||
|
Allow the user to enter the Message Identifier via MMI only for the 1 000 lowest codes. |
||
|
Be capable of receiving CBS messages consisting of up to 15 pages. |
Be capable of receiving CBS messages consisting of up to 1230 octets in UTRAN or warning messages of up to 9600 octets in E-UTRAN, or NG-RAN. |
|
|
When emergency indication is included in the received paging and/or CBS/warning message, behave as specified in 3GPP TS 22.268 [28]. If the emergency indication includes the value for "test", mobile terminals which are not used for testing purpose silently discard the paging message and do not receive the corresponding CBS/warning message. |
||
8.2 Duplication Detection Function
The MS/UE uses a common duplication detection function for all messages received in GSM, UMTS, E-UTRAN and NG-RAN.
In a PLMN, upon reception of a new message, the MS/UE shall perform duplication detection on the messages. Those messages that are received from the same PLMN in the certain time period specified by the duplication detection time are subject to duplication detection. The MS/UE shall not perform duplication detection on messages whose duplication detection time has elapsed.The value of the duplication detection time to be used by the MS/UE shall be derived from the MCC of the current PLMN as follows:
– If MCC = 440 or MCC = 441 (Japan), duplication detection time shall be 1 hour;
– For all other MCCs, duplication detection time shall be 24 hours.
In an SNPN, upon reception of a new message, the MS/UE shall perform duplication detection on the messages. Those messages that are received in the certain time period specified by the duplication detection time are subject to duplication detection. The MS/UE shall not perform duplication detection on messages whose duplication detection time has elapsed. The value of the duplication detection time to be used by the MS/UE shall be 24 hours.
The MS/UE shall check:
1) whether the Serial Number associated with the Message Identifier of the new message matches the Serial Number of any of those messages with the same Message Identifier that have been received and displayed to the subscriber and that are subject to the duplication detection.
Additionally, the MS/UE may check:
2) other criteria for detecting duplicates. An example of such a criterion is whether the actual contents of the two messages is the same.
If criterion 1 is fulfilled and any implemented additional checks (as described in criterion 2) are also met, then the MS/UE shall consider the new message as duplicated and shall ignore it. If the Geographical Scope is not PLMN/SNPN wide the validity of the Serial Number may be considered as described in clause 9.4.1.2.1.
For ETWS, duplicate message detection shall be performed independently for primary and secondary notifications.
8.3 ePWS functionality
The ePWS functionality consists of the ePWS language-independent content functionality and the ePWS disaster characteristics functionality as follows:
1) UEs with user interface which support the ePWS language-independent content functionality and which are capable of displaying text-based warning messages should be capable of displaying the language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) that is part of user information contained in the content of a warning message transparently passed from CBC to UEs.
NOTE 1: Language-independent contents mapped to disasters need to be formatted to be suitable to be included in a warning message. It could be unicode symbol or symbol based on GSM 7 bit default alphabet. It is desirable that standardised symbols mapped to disasters are applied in all countries that provide warning messages for public safety. This will make it possible for foreigners to intuitively understand the meaning of language-independent contents displayed to their devices.
Editor’s note [WI: ePWS, CR#202]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.
2) UEs with user interface which support the ePWS language-independent content functionality and which are incapable of displaying text-based warning messages should be capable of mapping message identifiers of received warning messages to language-independent contents stored in those UEs. When a warning message is received, such a UE should be capable of displaying of a language-independent content stored in the UE mapped from the message identifier of the received warning message.
NOTE 2: This ePWS functionality is not applied for such UEs if they are not capable of storing any language-independent content.
3) UEs with no user interface which support the ePWS disaster characteristics functionality should be capable of identifying the characteristics of a disaster derived from the message identifier of a received warning message in order to take appropriate action.