9.3 Parameters
23.0413GPPRelease 18Technical realization of Cell Broadcast Service (CBS)TS
9.3.1 Message-Identifier
This parameter identifies source/type of a CBS message and is passed transparently from the CBC to the MS/UE. Its format is defined in clause 9.4.1.2.2.
9.3.2 Old-Serial-Number
This parameter equates to the parameter – Serial Number sent between the BSC/RNC and the MS/UE. Its format is defined in clause 9.4.1.2.1.
This parameter enables a particular existing CBS message, from the source/type indicated by the message identifier, to be identified.
9.3.3 New-Serial-Number
This parameter equates to the parameter – Serial Number sent between the BSC/RNC and the MS/UE. Its format is defined in clause 9.4.1.2.1.
This parameter enables CBS message change to be indicated since it is altered every time the CBS message is changed. The serial number identifies a particular CBS message, which may be several pages in length, from the source indicated by the message identifier.
9.3.4 Number-of-Pages
This parameter enables the number of pages in the CBS message to be indicated.
9.3.5 Cell-List
The cell-list identifies a sequence of one or more cells to which the primitives apply.
The following applies for GSM only:
The cells in the list are described in 3GPP TS 48.008 [13] and can be identified by the CBC or BSC in LAC and CI format or CI format only.
In addition (see 3GPP TS 48.008 [13]) it is possible for the CBC to refer to all cells in a LAC or in a complete BSC. If supplied, the Cell-List parameter must refer to at least one cell.
The following applies for UMTS only:
a) For CBS the cells are refered to as Service Areas. As described in 3GPP TS 25.401 [17] a Service Area Identifier (SAI) is used to uniquely identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN.
b) The Service Area Code (SAC) together with the PLMN-Id and the LAC will constitute the Service Area Identifier.
– SAI = PLMN-Id + LAC + SAC.
c) The SAC is defined by the operator, and set in the RNC via O&M.
NOTE: For CBS, a Service Area shall consist of only one Cell. The mapping of SAI onto cell is controlled by the RNC and managed by an O&M function.Given the above differences between cell identification in the two directions, a cell list sent from the CBC to the BSC/RNC has a different structure compared to a cell list sent from the BSC/RNC to the CBC. The different cell lists are described in clauses 9.3.5.1 and 9.3.5.2.
The following applies for E-UTRAN only:
– The cells in the list are described in 3GPP TS 36.413 [34].
The following applies for NG-RAN only:
– The cells in the list are described in 3GPP TS 38.413 [40].
9.3.5.1 Cell-List sent from CBC to BSC/RNC
The CBC to BSC/RNC Cell-List contains a length parameter identifying the number of cell-identifications present in the list, a Cell-Id-Discriminator, which is common for all cell-identifications in the list, and a sequence of cell‑identifications.
Description of list elements:
|
PARAMETER |
PRESENCE |
|
Length |
M |
|
Cell-Id-Discriminator |
M |
|
Cell-Identification |
M |
The Cell-Id-Discriminator has one of the following formats:
|
Format |
Description |
|
LAC and CI in GSM; |
3GPP TS 48.008 [13] |
|
CI only; |
3GPP TS 48.008 [13] |
|
all cells in the BSC/RNC belonging to a certain Location Area; |
Example in 3GPP TR 03.49 [6] |
|
all cells in the BSC; |
Example in 3GPP TR 03.49 [6] |
|
SAI in UMTS |
3GPP TS 25.401 [17] |
The Cell-identification is repeated for each cell included in the list. The Cell-List must refer to at least one cell.
9.3.5.2 Cell-List sent from BSC/RNC to CBC
The BSC/RNC to CBC Cell-List contains a sequence of cell-identifiers as defined in clause 9.3.11. The Cell-List must contain at least one cell-identifier as defined in clause 9.3.11.
9.3.6 Channel Indicator
The following applies for GSM only:
This parameter indicates the CB channel, which shall be used for broadcasting the data:
– basic channel;
– extended channel (supporting such a channel by the network or MSs is optional);
9.3.7 Category
This indicates the priority of the message:
– High Priority: to be broadcast at the earliest opportunity.
– Background: to be broadcast when no CBS messages of category "High Priority" or "Normal" are broadcast. The repetition period defines the minimum broadcast requirement.
– Normal: to be broadcast according to the associated repetition period.
If the category is omitted, the default category implied is "Normal" message.
9.3.8 Repetition-Period
This indicates the period of time after which broadcast of the CBS message should be repeated. The minimum period with which a CBS message consisting of one page may be broadcast over the air interface is a period of 1.883 s in GERAN. The minimum period with which a CBS message may be broadcast over the air interface in UTRAN is a period of 1 s.
The value of "Repetition-Period" shall be in the range 1 to 4095 for GERAN and in the range of 1 to 4096 for UTRAN, where each unit will represent the value of one minimum period.
NOTE: In previous versions of the present specification the the maximum Repetition-Period was defined to be 1024.
In the event of a conflict where the BSS/RNS has more than one CBS message to send at the same time, the BSC/RNC shall decide the order of such CBS messages as an implementation matter.
NOTE: The time period 1.883 s approximately reflects one 8 x 51 multiframe sequence of the GSM radio interface. The higher capacity of the RNC enables the CBC to send more than one CBS message consisting of one page with the minimum repetition rate to a Node B.
9.3.9 No-of-Broadcasts-Requested
This specifies the number of times the CBS message is to be broadcast.
The parameter may take any value up to 65535 (this maximum allows the CBS message to be broadcast approximately every 1.883 s for more than 24 h). If the parameter is set to 0 then the CBS message will be broadcast indefinitely (i.e. until the BSC receives an appropriate Kill-Message Request/Indication primitive).
9.3.10 No-of-Broadcasts-Completed-List
This parameter is a list indicating the number of times that the CBS message (i.e. all pages of the CBS message) has been sent to each cell in the Cell-List for broadcast over the air interface.
The cells in the list are described as per clause 9.3.11.
Description of list elements:
|
PARAMETER |
PRESENCE |
|
Cell Identifier |
M |
|
No-of-Broadcasts-completed |
M |
|
No-of-Broadcasts-Compl-Info |
O |
The information above is repeated for the number of cells in the list.
To each cell in the list the information element No-of-Broadcasts-completed is associated. This information element is related to the particular referenced cell in the list and contains the number of times a CBS message (i.e. all pages of a CBS message) has been sent to this cell for broadcast. The No-of-Broadcasts-completed information element represents the number of full broadcasts made of a CBS message, and that the CBS message is being (or had been) broadcast.
The optional No-of-Broadcasts-Compl-Info information element may be supplied to indicate to the CBC one of the following cases:
– overflow;
the count of the number of full broadcasts made of a CBS message has overflowed, and that the CBS message is being (or had been) broadcast. The actual number of broadcasts completed is greater than the value indicated in the No-of-Broadcasts-completed information element;
– unknown;
indicates that there is no information regarding the number of broadcasts completed in the BSC/RNC for the CBS message with the old serial number. The value indicated in the No-of-Broadcasts-completed information element is undefined in this case.
The No-of-Broadcasts-Completed-List must contain at least one cell.
9.3.11 Cell-Identifier
The cell-identifier consists of a cell-id-discriminator and cell-identification pair.
Description of list elements:
|
PARAMETER |
PRESENCE |
|
Cell-Id-Discriminator |
M |
|
Cell-Identification |
M |
The Cell-Id-Discriminator has one of the following formats:
|
Format |
Description |
|
LAC and CI in GSM |
3GPP TS 48.008 [13] |
|
CI only |
3GPP TS 48.008 [13] |
|
SAI in UMTS |
3GPP TS 25.401 [17] |
The BSC can use the ‘LAC and CI’ format for a cell identifier in any response to the CBC. The BSC may also use the ‘CI only’ format for a cell identifier when responding to a CBC primitive that had contained a cell with ‘CI only’ format for a cell identifier. The RNC uses the SAI format for a cell identifier in any response to the CBC.
9.3.12 Schedule-Period
The following applies for GSM only:Indicates the DRX schedule period length, see 3GPP TS 44.012 [7].
The following values should be coded:
– no DRX;
– length of the schedule period.
If a schedule period length greater than 40 is used, the schedule message cannot be built entirely if more than 40 CBS messages have to be described in the period. Therefore, schedule period length shall be reduced to 40.
9.3.13 Reserved-Slots
The following applies for GSM only:Indicates the number of slots marked as "free slots reading advised" in the schedule message and considered as reserved in a DRX schedule period for incoming high priority CBS messages, not scheduled in the current schedule period, see 3GPP TS 44.012 [7].
The spacing of the reserved slots is implementation dependent.
Reserved slots shall receive a 40 value at maximum, taking into account the constraint for schedule period length.
9.3.14 Failure-List
This identifies the list of cells for which the BSC/RNC could not complete the request. The failure cause for each cell is indicated.
The cells in the list are described as per clause 9.3.11.
Description of list elements:
|
PARAMETER |
PRESENCE |
|
Cell Identifier |
M |
|
Cause |
M |
|
Diagnostic |
O |
The information above is repeated for the number of cells that failed.
To each cell in the list the information elements Cause and, as an implementation option, Diagnostic are associated. These are related to the particular referenced cell in the list.
The Failure-List must contain at least one cell.
9.3.15 Radio-Resource-Loading-List
A list of the predicted short term load of each cell in the list expressed as a percentage. The calculation of this percentage is an implementation matter. The load should reflect the number of used slots, and schedule messages and reserved slots must be taken into account. The cells in the list are described as per clause 9.3.11.
Description of list elements:
|
PARAMETER |
PRESENCE |
|
Cell Identifier |
M |
|
Radio-Resource-Loading |
M |
The information above is repeated for the number of cells in the list.
To each cell in the list the information element Radio-Resource-Loading is associated. This information element is related to the particular referenced cell in the list and contains the cells load.
Note that for cells with DRX the load caused by the schedule messages will be included in the Radio-Resource load.
The Radio-Resource-Loading-List must contain at least one cell.
9.3.16 Cause
Indicates reason why the BSC/RNC was not able to interpret or execute the received primitive. The causes are given in table 1.
Table 1
|
Cause |
Reason |
|
Parameter-not-recognized |
Sent when the recipient (CBC or BSC/RNC) was unable to act upon the primitive received due to an unrecognized parameter. A primitive should not be rejected only because a parameter is not recognized as this would prevent extensions to the service |
|
parameter-value-invalid |
Sent when a failure occurred due to the value of a parameter being invalid, e.g. out of range, or in Write-Replace, the parameter "no of pages" does not equal the number of pages received |
|
valid-CBS-message-not- identified |
Sent when the BSC/RNC does not recognize the CBS message reference |
|
cell-identity-not-valid |
Sent when the BSC/RNC does not recognize a cell Identity |
|
unrecognized-primitive |
Sent when the BSC/RNC did not recognize the primitive at all |
|
missing-mandatory-element |
Sent when a mandatory element is missing from the primitive |
|
bss-capacity-exceeded |
Sent when a write-replace fails because the BSC/RNC cannot meet the requested repetition period or when the set-drx parameters cannot be applied because of the cell loading |
|
GSM only [cell-memory-exceeded |
Sent when the local cell memory has been exceeded] |
|
bss-memory-exceeded |
Sent when the BSS/RNS is unable to store a CBS message as the BSS/RNS memory has been exceeded |
|
cell-broadcast-not-supported |
Sent when the CBCH/CBS related Radio Resource is not configured for a cell |
|
cell-broadcast-not-operational |
Sent when the CBCH/CBS related radio resource is not available because of error conditions or due to maintenance activities |
|
incompatible-DRX-parameter |
Sent when the DRX parameter(s) cannot be applied. |
|
GSM only [Extended-channel-not-supported |
Sent when a write-replace fails because the extended channel is not configured for a cell] |
|
message-reference already-used |
Sent when the recipient (BSC/RNC) was unable to act upon the write_replace received due to a previous write_replace received with the same message_reference. |
|
unspecified-error |
Sent when none of the above cause values apply |
9.3.17 Diagnostic
Provides additional information associated with Cause parameter and may contain parameter which could not be interpreted/executed.
9.3.18 Data Coding Scheme
This parameter identifies the alphabet or coding employed for the message characters and message handling at the MS/UE and is passed transparently from the CBC to the MS/UE. This parameter is defined in 3GPP TS 23.038 [3].
9.3.19 CBS-Message-Information-Page n
This parameter is of a fixed length of 82 octets and carries up to and including 82 octets of user information. Where the user information is less than 82 octets, the remaining octets must be filled with padding (see 3GPP TS 23.038 [3]).
The content of a CBS-Message-Information-Page is passed transparently from the CBC to the MS/UE.
In GSM the CBS-Message-Information-Page n becomes the ‘Content of Message’ parameter at the MS.
In UMTS and E-UTRAN, the CBS-Message-Information-Pages together with the associated CBS-Message-Information-Length parameter are broadcasted as a single unit over the radio inteface, and are part of ‘CB Data’ parameter at the UE.
In the case where the user information is GSM 7 bit default alphabet encoded, the appropriate padding characters and bit-fill are added to the end of the user information to complete the CBC-Message-Information-Page (see 3GPP TS 23.038 [3]).
In the case where the user information is 8 bit encoded, the appropriate padding octets are added to the end of the user information to complete the CBC-Message-Information-Page (see 3GPP TS 23.038 [3]).
9.3.19.1 Identification of a directory number within a CBS-Message-Information-Page
For information relating to this feature see 3GPP TS 23.040 [4].
9.3.20 CBS-Message-Information-Length n
This parameter gives the number of octets of the CBS-Message-Information-Page n containing user information. The remaining octets of the CBS-Message-Information-Page n contain only padding information and are not included in this parameter.
In the case where the user information is encoded using the GSM 7 bit default alphabet and the last character terminates at an octet boundary, this parameter indicates the number of octets of user information. In the case where the last character does not terminate at an octet boundary, this parameter indicates the number of octets up to the octet boundary immediately following the last GSM 7 bit default alphabet character of user information.
In UMTS and E-UTRAN, the CBS-Message-Information-Pages together with the associated CBS-Message-Information-Length parameter are broadcasted as a single unit over the radio inteface, and are part of ‘CB Data’ parameter at the UE.
9.3.21 Recovery-Indication
Indicates whether the CBS related data was lost or is still available.
The following values should be coded:
– Data-available;
– Data-lost.
9.3.22 Void
9.3.23 Paging-ETWS-Indicator
This parameter indicates that emergency information shall be sent over the paging message.
In UMTS the parameter remotely activates the UE to receive CBS messages.
In GSM the parameter indicates that an ETWS emergency message is included in the WRITE-REPLACE primitive.
9.3.24 Warning-Type
This parameter is set when ETWS is used. It has three fields in order to contain warning type value, emergency user alert and popup indications.
The warning type value field indicates the following 5 warning types as its values; earthquake, tsunami, earthquake and tsunami, test, and other. Also, other warning types can be defined in the future if it is required.
The values for this parameter are expressed in 7-bit string. The following table shows the values and their corresponding warning types.
|
Warning typeValue |
Warning type |
|
0000000 |
Earthquake |
|
0000001 |
Tsunami |
|
0000010 |
Earthquake and Tsunami |
|
0000011 |
Test |
|
0000100 |
Other |
|
0000101-1111111 |
Reserved for future use |
The fields for emergency user alert and popup indications are type binary. They are used to command mobile terminals to activate emergency user alert and message popup in order to alert the users upon the reception of ETWS primary notification (e.g. paging message). The codings for the fields are shown below:
|
Field |
Emergency User Alert |
Popup |
||
|
Value |
0 |
1 |
0 |
1 |
|
Instruction to Terminal |
No instruction as to emergency alert. |
Activate emergency user alert. |
No instruction as to popup. |
Activate popup on the display. |
NOTE: Emergency user alert includes alerting tone and other user alerting means such as vibration, according to the UE’s capability. The types of alert (e.g. the kind of tone, vibration, etc) are implementation dependent and may be subject to regulatory requirements.
The encoding of the Warning-Type parameter is as shown below. The warning type value shall be mutually exclusive and binary encoded.
|
Octet 1 |
Octet 2 |
||||||||||||||
|
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
0 |
|
Warning Type Value |
Emergency User |
Popup |
Padding |
||||||||||||
|
Alert |
|||||||||||||||
The values of this parameter are sent to the mobile terminals (e.g. over the paging message which remotely activates the UE to receive CBS messages).
9.3.25 Warning-Security-Information
This parameter is only set when ETWS primary notification is sent with security. This parameter is 50 bytes in length and contains 7 byte timestamp and 43 byte digital signature.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Year |
octet 1 |
|||||||
|
Month |
octet 2 |
|||||||
|
Day |
octet 3 |
|||||||
|
Hour |
octet 4 |
|||||||
|
Minute |
octet 5 |
|||||||
|
Second |
octet 6 |
|||||||
|
Time zone |
octet 7 |
|||||||
|
Digital Signature |
octet 8 – octet 50 |
|||||||
Year (octet 1, bits 1-8): This field uses the same format as the Year field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4].
Month (octet 2, bits 1-8): This field uses the same format as the Month field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4].
Day (octet 3, bits 1-8): This field uses the same format as the Day field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4].
Hour (octet 4, bits 1-8): This field uses the same format as the Hour field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4].
Minute (octet 5, bits 1-8): This field uses the same format as the Minute field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4].
Second (octet 6, bits 1-8): This field uses the same format as the Second field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4].
Time Zone (octet 7, bits 1-8): This field uses the same format as the Time Zone field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 23.040 [4].
Digital Signature (octet 8 – 50, bits 1-8): This field contains the 43 byte digital signature.
9.3.26 Warning Period
This parameter indicates the length of the period during which the ETWS emergency message is to be broadcasted in the BSC. This parameter is applicable for GSM only.
9.3.27 Broadcast Message Type
This parameter is applicable for GSM only.
It indicates if the primitive including this parameter is referring to:
– CBS message broadcasting; or
– ETWS emergency message broadcasting.
9.3.28 Message Type
This parameter is applicable for E-UTRAN and NG-RAN only.
The Message Type IE uniquely identifies the message being sent; see 3GPP TS 29.168 [35] for E-UTRAN and 3GPP TS 29.518 [41] for NG-RAN.
9.3.29 List of TAIs
This parameter is applicable for E-UTRAN only.
The Tracking Area ID List IE is used to uniquely identify a Tracking Area; see 3GPP TS 36.413 [36] for E-UTRAN.
9.3.30 Warning Area List
This parameter is applicable for E-UTRAN only.
The Warning Area List IE indicates the areas where the warning message needs to be broadcast. The Warning Area List consists of a Cell ID list (see clause 9.3.5) or a TAI list (see clause 9.3.29) or an Emergency Area ID list; see clause 9.3.47.
9.3.31 OMC ID
This parameter is applicable for E-UTRAN and NG-RAN only.
The OMC ID IE indicates the identity of an Operation and Maintenance Centre to which Trace Records shall be sent. This element consists of a string of maximum 20 octets; see 3GPP TS 29.168 [35] for E-UTRAN and 3GPP TS 29.518 [41] for NG-RAN.
9.3.32 Concurrent Warning Message Indicator
This parameter is applicable for E-UTRAN and NG-RAN only.
The Concurrent Warning Message Indicator IE indicates to eNB that the received warning message is a new message to be scheduled for concurrent broadcast with any other ongoing broadcast of warning messages. This element is an enumerated type; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN.
NOTE: The Concurrent Warning Message Indicator IE is always present for non-ETWS (eg. CMAS) messages. The Concurrent Warning Message Indicator is not applicable for ETWS.
9.3.33 Cause-E-UTRAN
This parameter is applicable for E-UTRAN only.
The purpose of the Cause E-UTRAN IE is to indicate the reason for a particular event for the SBc-AP protocol. This element is an integer; see 3GPP TS 29.168 [35].
9.3.34 Criticality Diagnostics
This parameter is applicable for E-UTRAN and NG-RAN only.
The Criticality Diagnostics IE is sent by the MME/AMF when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which IEs were not comprehended or were missing; see 3GPP TS 29.168 [35] for E-UTRAN and 3GPP TS 29.518 [41] for NG-RAN.
9.3.35 Warning Message Content E-UTRAN
This parameter is applicable for E-UTRAN only.
The Warning Message Content E-UTRAN IE contains user information, e.g., the message with warning contents, and will be broadcast over the radio interface. This element is a string of maximum 9600 octets; see 3GPP TS 36.413 [36].
NOTE: If the ePWS language-independent content functionality (see clause 8.3) is supported by CBE, a user information can include a language-independent content mapped to an event or a disaster that is compatible with texts used to describe user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs.
The content of Warning Message Content E-UTRAN IE consists of the following parameters:
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Number-of-Pages |
9.3.4 |
M |
|
CBS-Message-Information-Page 1 |
9.3.19 |
M |
|
CBS-Message-Information-Length 1 |
9.3.20 |
M |
|
CBS-Message-Information-Page 2 |
9.3.19 |
O |
|
CBS-Message-Information-Length 2 |
9.3.20 |
O |
|
… |
: |
|
|
CBS-Message-Information-Page n |
9.3.19 |
O |
|
CBS-Message-Information-Length n |
9.3.20 |
O |
|
NOTE: n equal to or less than 15 |
||
9.3.36 Repetition-Period E-UTRAN
This parameter is applicable for E-UTRAN only.
The Repetition Period E-UTRAN IE indicates the periodicity in seconds of the warning message to be broadcast.This element is an integer with a value between 0 and 4095; see 3GPP TS 36.413 [36].
9.3.37 Extended Repetition-Period
This parameter is applicable for E-UTRAN only.
The Extended Repetition-Period IE indicates the periodicity in seconds of the warning message to be broadcast. This IE is used if the Repetition Period has a value larger than 4095 and is an integer between 4096 and (217-1); see 3GPP TS 36.413 [36] for E-UTRAN.
9.3.38 Unknown Tracking Area List
This parameter is applicable for E-UTRAN and NG-RAN only.
The Unknown Tracking Area List IE identifies the Tracking Areas that are unknown to the MME/AMF and where the Request cannot be delivered.This IE is of type List of TAI (see clause 9.3.29).
This IE shall not be included if the Cause IE indicates Tracking area not valid. The Cause IE indicating Tracking area not valid is used when all Tracking Areas in the Request are invalid.
9.3.39 Send Write-Replace-Warning-Indication
This parameter is applicable for E-UTRAN and NG-RAN only.
For E-UTRAN:
The Send Write-Replace-Warning-Indication IE indicates to the MME that the MME shall send the WRITE-REPLACE WARNING INDICATION to the CBC for the warning message. This element is an enumerated type; see 3GPP TS 29.168 [35].
For NG-RAN:
The Send Write-Replace-Warning-Indication IE indicates to the AMF that the AMF shall send the WRITE-REPLACE WARNING INDICATION-NG-RAN to the CBCF for the warning message. This element is an enumerated type; see 3GPP TS 29.518 [41].
9.3.40 Broadcast Scheduled Area List
This parameter is applicable for E-UTRAN and NG-RAN only.
The Broadcast Scheduled Area List IE indicates the areas where initiation of a broadcast was performed successfully. A Broadcast Scheduled Area List is received by the MME/AMF from an eNodeB/NG-RAN node as Broadcast Completed Area List; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN.
9.3.41 Send Stop Warning Indication
This parameter is applicable for E-UTRAN and NG-RAN only.
For E-UTRAN:
The Send Stop Warning Indication IE is an indication for the MME to send the STOP-WARNING-INDICATION to the CBC for the warning message. This element is an enumerated type; see 3GPP TS 29.168 [35].
For NG-RAN:
The Send Stop Warning Indication IE is an indication for the AMF to send the STOP-WARNING-INDICATION-NG-RAN to the CBCF for the warning message. This element is an enumerated type; see 3GPP TS 29.518 [41].
9.3.42 Broadcast Cancelled Area List
This parameter is applicable for E-UTRAN and NG-RAN only.
The Broadcast Cancelled Area List IE indicates the areas where broadcast was stopped successfully; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN.
9.3.43 Stop-All Indicator
This parameter is applicable for E-UTRAN and NG-RAN only.
For E-UTRAN:
The Stop-All Indicator IE in the STOP-WARNING-REQUEST is sent by the MME to the eNodeB in the Kill Request (see 3GPP TS 36.413 [36]). This is to indicate to the eNB that the Message Identifier IE and the Serial Number IE in the Kill Request shall be ignored and the request applies to all messages in the Warning Area.
NOTE 1: The CBC may use the Message Identifier IE and/or the Serial Number IE to associate the STOP-WARNING-INDICATION and the STOP-WARNING-RESPONSE with the STOP-WARNING-REQUEST.
The Stop-All Indicator IE is an enumerated type; see 3GPP TS 29.168 [35].
For NG-RAN:
The Stop-All Indicator IE in the STOP-WARNING-REQUEST-NG-RAN is sent by the AMF to the NG-RAN node in the Cancel Request (see 3GPP TS 38.413 [40]). This is to indicate to the NG-RAN node that the Message Identifier IE and the Serial Number IE in the Cancel Request shall be ignored and the request applies to all messages in the Warning Area.
NOTE 2: The CBCF may use the Message Identifier IE and/or the Serial Number IE to associate the STOP-WARNING-INDICATION-NG-RAN and the STOP-WARNING-RESPONSE-NG-RAN with the STOP-WARNING-REQUEST-NG-RAN.
The Stop-All Indicator IE is an enumerated type; see 3GPP TS 29.518 [41].
9.3.44 Broadcast Empty Area List
This parameter is applicable for E-UTRAN and NG-RAN only.
For E-UTRAN:
The Broadcast Empty Area List IE contains a list of the eNodeB IDs (see clause 9.3.46) of eNodeBs that have responded to the the MME with a
– WRITE-REPLACE WARNING RESPONSE message in which the Broadcast Completed Area List IE was not included (see 3GPP TS 36.413 [34]), or
– KILL RESPONSE message in which the Broadcast Cancelled Area List IE was not included (see 3GPP TS 36.413 [34]).
The MME may aggregate eNodeB IDs into the Broadcast Empty Area List.
For NG-RAN:
The Broadcast Empty Area List IE contains a list of the RAN Node IDs (see clause 9.3.53) of NG-RAN nodes that have responded to the the AMF with a
– WRITE-REPLACE WARNING RESPONSE message in which the Broadcast Completed Area List IE was not included (see 3GPP TS 38.413 [40]), or
– PWS CANCEL RESPONSE message in which the Broadcast Cancelled Area List IE was not included (see 3GPP TS 38.413 [40]).
The AMF may aggregate NG-RAN node IDs into the Broadcast Empty Area List.
9.3.45 Restarted-Cell-List
This parameter is applicable for E-UTRAN and NG-RAN only.
The Restarted-Cell-List IE lists the cells which have restarted and where warning messages have been stopped if any were ongoing. See 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN.
9.3.46 Global eNB ID
This parameter is applicable for E-UTRAN only.
The Global eNB ID IE is used to globally identify an eNB. See 3GPP TS 36.413 [36].
9.3.47 Emergency Area ID List
This parameter is applicable for E-UTRAN and NG-RAN only.
The Emergency Area ID List IE is used to indicate the area which has the emergency impact; see 3GPP TS 36.413 [36] for E-UTRAN and 3GPP TS 38.413 [40] for NG-RAN.
9.3.48 Broadcast Message Content Validity Indicator
This parameter is applicable for UMTS only.
The Broadcast Message Content Validity Indicator IE if included in the WRITE-REPLACE message indicates that the Broadcast Message Content IE does not contain any valid information and is to be ignored. This element is an enumerated type; see 3GPP TS 25.419 [29].
9.3.49 Failed-Cell-List
This parameter is applicable for E-UTRAN and NG-RAN only.
The Failed-Cell-List IE lists the cells where ongoing PWS operation has failed. See 3GPP TS 36.413 [36] for E‑UTRAN and 3GPP TS 38.413 [40] for NG-RAN.
9.3.50 Cause-NG-RAN
This parameter is applicable for NG-RAN only.
The purpose of the Cause-NG-RAN IE is to indicate the reason for a particular event for the N50 protocol. This element is an integer; see 3GPP TS 29.518 [41].
9.3.51 Warning Message Content NG-RAN
This parameter is applicable for NG-RAN only.
The Warning Message Content NG-RAN IE contains user information, e.g., the message with warning contents, and will be broadcast over the radio interface. This element is a string of maximum 9600 octets; see 3GPP TS 38.413 [40].
NOTE: If the ePWS language-independent content functionality (clause 8.3) is supported by CBE, a user information can include a language-independent content mapped to an event or a disaster that is compatible with texts used to describe user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs.
The content of Warning Message Content NG-RAN IE consists of the following parameters:
|
PARAMETER |
REFERENCE |
PRESENCE |
|
Number-of-Pages |
9.3.4 |
M |
|
CBS-Message-Information-Page 1 |
9.3.19 |
M |
|
CBS-Message-Information-Length 1 |
9.3.20 |
M |
|
CBS-Message-Information-Page 2 |
9.3.19 |
O |
|
CBS-Message-Information-Length 2 |
9.3.20 |
O |
|
… |
: |
|
|
CBS-Message-Information-Page n |
9.3.19 |
O |
|
CBS-Message-Information-Length n |
9.3.20 |
O |
|
NOTE: n equal to or less than 15 |
||
9.3.52 Repetition-Period NG-RAN
This parameter is applicable for NG-RAN only.
The Repetition Period NG-RAN IE indicates the periodicity in seconds of the warning message to be broadcast.This element is an integer with a value between 0 and 217-1; see 3GPP TS 38.413 [40].
9.3.53 Global RAN Node ID
This parameter is applicable for NG-RAN only.
The Global RAN Node ID IE is used to globally identify a NG-RAN node (i.e. a Global gNB ID or a Global ng-eNB ID). See 3GPP TS 38.413 [40].
9.3.54 List of NG-RAN TAIs
This parameter is applicable for NG-RAN only.
The List of NG-RAN TAIs IE is used to uniquely identify NG-RAN Tracking Areas; see 3GPP TS 38.413 [40].
9.3.55 Warning Area List NG-RAN
This parameter is applicable for NG-RAN only.
The Warning Area List NG-RAN IE indicates the areas where the warning message needs to be broadcast. The Warning Area List NG-RAN consists of a Cell ID list (see clause 9.3.5) or a NG-RAN TAI list (see clause 9.3.54) or an Emergency Area ID list; see clause 9.3.47.
9.3.56 RAT Selector NG-RAN
This parameter is applicable for NG-RAN only.
The RAT Selector NG-RAN IE shall be present to indicate to the AMF if the request shall be distributed to attached ng‑eNBs or to gNBs. See 3GPP TS 29.518 [41].
NOTE: The CBC and the AMF do not support handling of concurrent responses from ng-eNBs and gNBs for the same request.
9.3.57 Unknown NG-RAN Tracking Area List
This parameter is applicable for NG-RAN only.
The Unknown NG-RAN Tracking Area List IE identifies the Tracking Areas that are unknown to the AMF and where the request cannot be delivered. This IE is of type List of NG-RAN TAIs (see clause 9.3.54).
This IE shall not be included if the Cause IE indicates Tracking area not valid. The Cause IE indicating Tracking area not valid is used when all Tracking Areas in the request are invalid.
9.3.58 Broadcast Scheduled Area List NG-RAN
This parameter is applicable for NG-RAN only.
The Broadcast Scheduled Area List NG-RAN IE indicates the areas where initiation of a broadcast was performed successfully. A Broadcast Scheduled Area List is received by the AMF from an NG-RAN Node as Broadcast Completed Area List. See 3GPP TS 38.413 [40].
9.3.59 Broadcast Cancelled Area List NG-RAN
This parameter is applicable for NG-RAN only.
The Broadcast Cancelled Area List NG-RAN IE indicates the areas where broadcast was stopped successfully; see 3GPP TS 38.413 [40].
9.3.60 Broadcast Empty Area List NG-RAN
This parameter is applicable for NG-RAN only.
The Broadcast Empty Area List NG-RAN IE contains a list of the Global RAN Node IDs (see clause 9.3.53) of NG-RAN Nodes that have responded to the the AMF with a
– WRITE-REPLACE WARNING RESPONSE message in which the Broadcast Completed Area List IE was not included (see 3GPP TS 38.413 [40]), or
– PWS CANCEL RESPONSE message in which the Broadcast Cancelled Area List IE was not included (see 3GPP TS 38.413 [40]).
The AMF may aggregate NG-RAN Node IDs into the Broadcast Empty Area List NG-RAN.
9.3.61 Restarted Cell List NG-RAN
This parameter is applicable for NG-RAN only.
The Restarted Cell List NG-RAN IE lists the cells which have restarted and where warning messages have been stopped if any were ongoing. See 3GPP TS 38.413 [40].
9.3.62 Failed Cell List NG-RAN
This parameter is applicable for NG-RAN only.
The Failed Cell List NG-RAN IE lists the cells where ongoing PWS operation has failed. See 3GPP TS 38.413 [40].
9.3.63 Warning Area Coordinates
This parameter is applicable for E-UTRAN and NG-RAN only.
The Warning Area Coordinates IE indicates alert area coordinates of a warning message. The eNB and NG-RAN node pass this information to the UE. The UE uses this information to conditionally display (see clause 9.1.3.4.2 and clause 9.1.3.5.2) the warning message contents.
The Warning Area Coordinates IE is encoded as specified in ATIS-0700041 [47].
9.3.64 Test Flag
The Test Flag IE may be included to indicate to the NG-RAN node that the request is to be processed and responded to normally, but shall not result in broadcast over the air and shall not allocate any resources (i.e. the request cannot be cancelled).