hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.1 General
|
In GSM and UMTS, the cell broadcast service can be used to transfer CBS messages related to public warning. This requires reception of CBS messages to be permanently activated in the mobile terminal.
Warning message delivery is similar to cell broadcast service. It permits a number of unacknowledged warning messages to be broadcast to MS/UEs within a particular area. Reception of warning messages is enabled as defined later on in this specification.
For warning messages received from a PLMN, 3GPP TS 31.102 [18] defines a USIM data file for configuration of warning messages reception. In case of a non-existing or empty USIM data file, the MS/UE accepts all warning messages on all PLMNs. As specified in 3GPP TS 31.102 [18], the MS/UE can be configured to ignore all warning messages received in its HPLMN or in a PLMN equivalent to it. As specified in 3GPP TS 31.102 [18], the MS/UE can be configured to ignore all warning messages received in a VPLMN or in a PLMN equivalent to it.
A UE in limited service state, and configured according to the USIM data file to display warning messages on that PLMN, shall display warning messages to the user.
For warning messages received from an SNPN:
- 3GPP TS 23.122 [49] defines configuration parameters in each entry of the "list of subscriber data" for configuration of warning message reception. In case the configuration parameters are not present in the selected entry of the "list of subscriber data", the UE accepts all warning messages on all SNPNs. As specified in 3GPP TS 23.122 [49], when using an entry of the "list of subscriber data" to access an SNPN, the UE can be configured to ignore all warning messages received in the subscribed SNPN of the selected entry of the "list of subscriber data". As specified in 3GPP TS 23.122 [49], when using an entry of the "list of subscriber data" to access an SNPN, the UE can be configured to ignore all warning messages received in an SNPN other than the subscribed SNPN of the selected entry of the "list of subscriber data"; and
- 3GPP TS 31.102 [18] defines a USIM data file for configuration of warning message reception when the UE accesses an SNPN using the PLMN subscription. In case of a non-existing or empty USIM data file, the UE accepts all warning messages on all SNPNs. As specified in 3GPP TS 31.102 [18], the UE can be configured to ignore all warning messages received in an SNPN.
In GSM, an ETWS capable MS uses the procedure as outlined in clause 9.1.3.2. See 3GPP TS 44.018 [26] and 3GPP TS 44.060 [27] for details on the radio interface.
In UMTS, an ETWS capable UE uses the procedure as outlined in clause 9.1.3.3. See 3GPP TS 25.331 [16] for details on the radio interface.
In E-UTRAN, an ETWS capable UE or a CMAS capable UE uses the procedures as outlined in clause 9.1.3.4. See 3GPP TS 36.331 [36] for details on the radio interface.
In NG-RAN, an ETWS capable UE or a CMAS capable UE uses the procedures as outlined in clause 9.1.3.5. See 3GPP TS 36.331 [36] and 3GPP TS 38.331 [48] for details on the radio interface.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.2 Warning Message Delivery Procedure in GSM
|
When a warning message is sent in GERAN, the following message flow applies. The warning message request from the CBE will trigger a broadcast of an ETWS emergency message (containing the ETWS Primary Notification) and/or a CBS message (constituting a Secondary Notification) on the radio interface. The ETWS emergency message is conveyed by the paging message which can invoke mobile terminals to start receiving CBS messages without MMI. Mobile stations invoked to start receiving CBS messages this way may stop receiving CBS messages (without MMI) after a predefined period of time.
Figure 9.1.3.2-1: Warning message delivery procedure in GERAN
1. Network registration and security procedures are performed.
NOTE 1: This step is performed each time an MS is attached to a NW (e.g. after each power-on).
2. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information ("warning type", "warning message", "impacted area", and "time period") to the CBC. The CBC shall authenticate this request. The "warning type" takes one of the following values: earthquake, tsunami, earthquake and tsunami, test, or other.
3. Using the "impacted area information", the CBC identifies which BSCs need to be contacted and constructs the "Cell list" for the cells in which the information is to be broadcast.
The CBC shall send a WRITE-REPLACE message to all the identified BSCs. If the emergency information received from the CBE contains warning information to be sent both in an ETWS emergency message and in a CBS message, then the CBC need to send this information in separate WRITE-REPLACE messages to the identified BSCs accordingly:
- When containing an ETWS emergency message the WRITE-REPLACE message includes the "Paging ETWS Indicator" to differentiate it from a normal CBS message, as well as (among other parameters) the "Cell list", "warning type" (which constitutes a part of the ETWS Primary Notification message, see clause 9.4.1.3), and the "warning period" parameter.
- When containing a CBS message the WRITE-REPLACE message includes the "Channel Indicator" to differentiate it from an ETWS emergency message, as well as (among other parameters) the "Cell list", "Repetition Period", "No of Broadcasts Requested" and the "CBS Message Information" parameter(s).
The CBC shall not include the "digital signature" or "timestamp" information.
NOTE 2: Due to requirements in earlier versions of this document, it is possible for "digital signature" and "timestamp" information (included in the "Warning Security Information" parameter) to be transmitted within the WRITE-REPLACE message.
4. The BSCs use the "Cell list" information to identify in which cells the warning message needs to be broadcasted.
a) When the WRITE-REPLACE message contains an ETWS emergency message, the BSC/BTS:
1) shall include the ETWS emergency message within the paging message and start sending the paging messages in all paging groups for the time duration requested by the CBC in the "warning period" parameter. The paging message contains the "ETWS indicator", based on the "Paging ETWS Indicator" received in the WRITE-REPLACE message, and the ETWS Primary Notification message as defined in clause 9.4.1.3. When the "warning type" in the ETWS Primary Notification message is set to 'other', all of the warning information is included in the broadcasted CBS message.
2) may send the ETWS Primary Notification message in other messages (Application Information, see 3GPP TS 44.018 [26], and Packet Application Information, see 3GPP TS 44.060 [27]) in order to reach mobiles in connected mode.
b) When the WRITE-REPLACE message contains a CBS message the BSC/BTS shall start to broadcast the CBS message on the Cell Broadcast channel according to the "Repetition Period" and "No of Broadcasts Requested" requested by the CBC.
5. Upon reception of the paging message containing the ETWS Primary Notification message, if the MS is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]) the ETWS capable MS alerts the user immediately as indicated by the "warning type" value, and starts reading the Cell Broadcast channel in order to acquire a possible broadcasted CBS message containing the Secondary Notification message.
Upon reception of the CBS message containing the Secondary Notification message, the ETWS capable MS immediately indicates the contents of the Secondary Notification message to the user.
NOTE 3: If the MS receives the same ETWS Primary Notification message more than once it silently discards the last received Primary Notification message.
NOTE 4: When the "warning type" is set to 'test', the MS silently discards the ETWS Primary Notification message. The MS does not start reading the Cell Broadcast channel in this case. However, the MS specially designed for testing purposes can perform user alerting and proceed to the reception of the broadcasted CBS message as described above.
NOTE 5: If the MS is configured to ignore warnings on that PLMN (see 3GPP TS 31.102 [18]), the MS does not try to acquire the broadcasted CBS message described above.
The MS shall perform duplication detection of the received message as specified in clause 8.2.
The MS shall ignore the values of "digital signature" and "timestamp" if received in the "Warning Security Information" parameter.
NOTE 2: Due to requirements in earlier versions of this document, it is possible for "digital signature" and "timestamp" information (included in the "Warning Security Information" parameter) to be transmitted within the WRITE-REPLACE message.
6. The BSC sends a WRITE-REPLACE COMPLETE message to the CBC in response to the WRITE-REPLACE message.
7. CBC sends acknowledgement message to CBE.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.3 Warning Message Delivery Procedure in UMTS
|
When a warning message is sent in UTRAN, the following message flow applies. In this case, the paging message with a new emergency indication can invoke mobile terminals to start receiving CBS messages without MMI. Mobile stations invoked to start receiving CBS messages this way may stop receiving CBS messages (without MMI) after a period of time, which should not be less than 30 minutes in case DRX-Level-2 is used, and 2 minutes in case DRX-Level-1 is used.
Figure 9.1.3.3-1: Warning message delivery procedure in UTRAN
1. Network registration and security (e.g. mutual authentication) procedures are performed.
NOTE 1: This step is performed each time a UE is attached to a network (e.g. after each power-on).
2. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information ("warning type", "warning message", "impacted area", and "time period") to the CBC. The CBC shall authenticate this request. The "warning type" takes one of the following values: earthquake, tsunami, earthquake and tsunami, test, or other.
3. Using the "impacted area information", the CBC identifies which RNCs need to be contacted and constructs the "Service Area ID list" for the cells in which the information is to be broadcast.
The CBC shall send a WRITE-REPLACE message to all the identified RNCs. The message shall include an "emergency indication" to differentiate it from normal Cell Broadcast information, as well as the "Service Area ID list", "warning type", "warning message".
The CBC shall not include the "digital signature" or "timestamp" information.
NOTE 2: Due to requirements in earlier versions of this document, it is possible for "digital signature" and "timestamp" information to be transmitted within "warning message".
4. The RNCs use the "Service Area ID list" information to identify which Node Bs they need to reach, and then, they relay information to them using the appropriate Iub interface message.
5. The Node B receives the Iub message containing the emergency indication. As parallel actions, the RNC/Node B:
a) shall start to broadcast the "warning message". This is broadcast by using a Cell Broadcast channel and modified System Information messages. This broadcast information is repeated continuously by the Node B for the "time period" requested by the CBE.
b) shall use paging messages in every paging group to alert idle mode mobiles to receive the broadcast warning message. Typically these paging messages are repeated in all paging groups for several DRX periods. The paging message contains the "ETWS indication" based on the "warning type" information. When the "warning type" is set to 'other', all of the warning information is included in the broadcast "warning message".
c) may send the "ETWS indication" in other messages (System Information Change Indication or ETWS Primary Notification With Security) in order to reach mobiles in connected mode. Inclusion of "ETWS indication" is the same as that of the paging message mentioned above.
6. If the UE is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]) the UE alerts the user immediately, using "warning type" value upon the reception of the "ETWS Indication".
NOTE 3: If the UE received the "ETWS Indication" more than once it will silently discard the optional primary notification.
NOTE 4: When the "warning type" is 'test', the UE silently discards the "ETWS Indication" and does not perform the reception of the broadcast message described below. However, the UE specially designed for testing purposes can perform user alerting described above and proceed to the reception of the broadcast message described below
NOTE 5: If the UE is configured to ignore warnings on that PLMN (see 3GPP TS 31.102 [18]) the UE does not perform the reception of the broadcast message described below.
Upon the reception of the"ETWS Indication", the UE activates the reception of the broadcast messages containing the "warning message" as the secondary notification. The UE indicates the contents of the "warning message" to the user.
The UE shall perform duplication detection of the received message as specified in clause 8.2.
The UE shall ignore the values of "digital signature" and "timestamp" if received.
NOTE 6: The "digital signature" and "timestamp" can be received due to requirements in earlier versions of this document.
7. The RNC node sends a BMC REPORT-SUCCESS to the CBC in response to Write-Replace.
8. CBC sends acknowledgement message to CBE.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.4 Warning Message Delivery Procedure in E-UTRAN
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.4.1 General
|
The maximum size of the warning message for E-UTRAN is different from that for UTRAN/GERAN.
When S1-flex is used, the eNodeB may receive duplicated warning messages. Duplicated messages can be detected by checking the message identifier and serial number fields and they shall not be transmitted on the radio interface.
E-UTRA connected to both EPC and 5GCN (see 3GPP TS 36.300 [46]) may receive warning messages from both EPC and 5GCN. Duplicated messages can be detected by checking the message identifier and serial number fields and duplicate messages shall not be transmitted on the radio interface.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.4.2 Warning Message Delivery Procedure
|
The warning message to be broadcast is delivered via MMEs to multiple eNodeBs. The eNodeB(s) are responsible for scheduling the broadcast of the new message and the repetitions in each cell.
The overall warning message delivery procedure is presented in figure 9.1.3.4.2-1:
Figure 9.1.3.4.2-1: Warning message delivery procedure in E-UTRAN
0. Network registration and security (e.g. mutual authentication) procedures are performed.
NOTE 1: This step is performed each time a UE is attached to a network (e.g. after each power on).
1. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information (e.g. "warning type", "warning message", "impacted area", "time period") to the CBC. The CBC shall authenticate this request.
NOTE 2: A warning message 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 if the ePWS language-independent content functionality (see clause 8.3) is supported by CBE.
2. Using the "impacted area" information, the CBC identifies which MMEs need to be contacted and determines the information to be place into the Warning Area List Information Element. The CBC sends a Write-Replace Warning Request message containing the warning message to be broadcast and the delivery attributes (Message identifier, Serial Number, list of TAIs, Warning Area List, OMC ID, CWM Indicator, Send Write-Replace-Warning-Indication, Global eNB ID, Warning Area Coordinates) to MMEs.
The warning messages use the coding scheme for CBS data specified in 3GPP TS 23.038 [3].
The list of TAIs is only used by the MME. The MME uses it for selecting which eNodeBs to forward the Write-Replace Warning Request message to.
If the Write-Replace Warning Request message is sent to reload cells served by an eNodeB, for which the CBC has previously received a Restart Indication (see clause 15A.1 of TS 23.007 [38]), the CBC shall include the Global eNB ID IE with the identity of this eNodeB in the Write-Replace Warning Request message.
The Warning Area List shall be a list of Cell IDs or a list of TAIs or one or more Emergency Area IDs. The Warning Area List is only used by the eNodeB. The eNodeB is configured with the TAI(s) and Cell ID(s) it serves and the Emergency Area ID(s) that it belongs to. The eNodeB checks for any match of the contents of the Warning Area List with these IDs to identify the cells where to distribute the warning message. The Warning Area List is an optional information element. If the Warning Area is absent, it shall be interpreted as "all cells on the eNodeB". The number of cell IDs will be limited by the message size on SBc and S1-MME. An Emergency Area ID is unique within the PLMN.
The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 9 is destined. Co-location of that OMC with the CBC is an operator option.
CBC shall set the Concurrent Warning Message (CWM) indicator in all Write-Replace Warning Request messages, if the PLMN supports concurrent warning message broadcasts.
The CBC shall not include the "digital signature" or "timestamp" information.
CBC shall set the Send Write-Replace-Warning Indication element in case the MME is requested to forward the Broadcast Scheduled Area List in a Write-Replace Warning Indication for the warning message.
NOTE 3: Due to requirements in earlier versions of the specification, it is possible that "digital signature" and "timestamp" information are transmitted within the "warning message".
CBC includes the Warning Area Coordinates in the Write-Replace-Warning Request message based on operator policy.
3. The MME sends a Write-Replace Warning Confirm message that indicates to the CBC that the MME has started to distribute the warning message to eNodeBs.
The Write-Replace Warning Confirm message may contain the Unknown Tracking Area List IE. The Unknown Tracking Area List IE identifies the Tracking Areas that are unknown to the MME and where the Request cannot be delivered.
If this message is not received by the CBC within an appropriate time period, the CBC can attempt to deliver the warning message via another MME in the same pool area.
4. Upon reception of the Write-Replace Confirm messages from the MMEs, the CBC may confirm to the CBE that it has started to distribute the warning message.
5. The MME forwards Write-Replace Warning Message Request to eNodeBs. The MME shall use the list of TAIs to determine the eNodeBs in the delivery area. If the list of TAIs is not included and no Global eNB ID has been received from the CBC, the message is forwarded to all eNodeBs that are connected to the MME. If a Global eNB ID has been received from the CBC, the MME shall forward the message only to the eNodeB indicated by the Global eNB ID IE.
6. When S1-flex is used the eNodeB may receive same message from multiple MMEs. The eNodeB detects duplicate messages by checking the message identifier and serial number fields within the warning message. If any redundant messages are detected only the first one received will be broadcasted by the cells. The eNodeB shall use the Warning Area List information to determine the cell(s) in which the message is to be broadcast. The eNodeBs return a Distribute Warning Message Response to the MME, even if it was a duplicate.
If there is a warning broadcast message already ongoing and the CWM Indicator is included in the Write-Replace Warning Message Request, the eNodeB does not stop existing broadcast message but start broadcasting the new message concurrently. Otherwise the eNodeB shall immediately replace the existing broadcast message with the newer one.
NOTE 4: If concurrent warning messages are not supported, this requires the CBE/CBC to take care that 'lower' priority warnings are not sent while a higher priority warning is still being sent.
The eNodeB broadcasts the message frequently according to the attributes set by the CBC that originated the warning message distribution.
7. If the UE has been configured to receive warning messages, and the UE is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]), then the UE proceeds as follows:
The UE can use "warning type" values, 'earthquake', 'tsunami' or 'earthquake and tsunami', immediately to alert the user. When "warning type" is 'test', the UE silently discards the primary notification, but the UE specially designed for testing purposes may proceed with the following procedures.
The UE activates reception of the broadcast messages containing the "warning message".
If the Warning Area Coordinates are not present:
The UE indicates the contents of the "warning message" to the user.
If the Warning Area Coordinates are present, and if the UE is unable to determine its location:
The UE indicates the contents of the "warning message" to the user.
If the Warning Area Coordinates are present, and the UE determines it is inside the Warning Area Coordinates:
The UE indicates the contents of the "warning message" to the user.
If the Warning Area Coordinates are present, and the UE determines it is outside the Warning Area Coordinates:
The UE does not indicate the contents of the "warning message" to the user. The UE shall store the "warning message" in the list of "warning messages" to be checked for geo-fencing during a UE implementation specific time which shall not be greater than 24 hours. Upon expiration of the UE implementation specific time, the UE shall remove the stored "warning message" from the list of "warning messages" to be checked for geo-fencing.
If the "warning message" is a geo-fencing trigger message (see clause 9.4.1.2.2) then:
- if the list of "warning messages" to be checked for geo-fencing stored at the UE is not empty, the UE shall, for each "warning message" stored at the UE in the list of "warning messages" to be checked for geo-fencing, compare the Serial Number and Message Identifier combination of the stored "warning message" to the list of Serial Number and Message Identifier combinations included in the Warning Message Content IE (CB Data) of the geo-fencing trigger message and encoded as specified in ATIS-0700041 [47], and:
1) if the Serial Number and Message Identifier combination of the stored "warning message" matches one of the Serial Number and Message Identifier combinations included in the geo-fencing trigger message, and:
a) the UE:
i) is able to determine its location and determines it is inside the Warning Area Coordinates of the stored "warning message"; or
ii) is unable to determine its location,
indicate the contents of the stored "warning message" to the user, remove the "warning message" from the list of "warning messages" to be checked for geo-fencing and then discard the geo-fencing trigger message; or
b) the UE is able to determine its location and determines it is outside the Warning Area Coordinates of the stored "warning message", discard the geo-fencing trigger message; or
2) if none of Serial Number and Message Identifier combinations of the stored "warning message" matches any of the Serial Number and Message Identifier combinations included in the Warning Message Content IE (CB Data) of the geo-fencing trigger message, discard the geo-fencing trigger message; and
- if the list of "warning messages" to be checked for geo-fencing stored at the UE is empty, the UE shall discard the geo-fencing trigger message.
If a language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) is included as part of user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs:
- UEs with user interface which support the ePWS language-independent content functionality (see clause 8.3) and which are capable of displaying text-based warning messages should be capable of displaying the entire warning message that they receive.
Editor's note [WI: ePWS, CR#203]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.
8. If the Send Warning-Message-Indication parameter was present in the Write-Replace Warning Request and it is configured in the MME based on operator policy, the MME shall forward the Broadcast Scheduled Area Lists in a Write-Replace Warning Indication(s) to the CBC. The Broadcast Scheduled Area List shall contain the Broadcast Completed Area List the MME has received from the eNodeB. The MME may aggregate Broadcast Completed Area Lists it receives from eNodeBs.
NOTE 5: Support for sending of Write-Replace Warning Indication(s) to the CBC is optional in the MME.
9. From the Write-Replace Warning Response messages returned by eNodeB's the MME determines the success or failure of the delivery and creates a trace record. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.4.3 Warning Message Cancel Procedure
|
The cancel warning message delivery procedure takes place when CBE requests to stop the on-going broadcast of warning messages.
Figure 9.1.3.4.3-1: Warning message cancel procedure in E-UTRAN
1. CBE initiates procedure by sending Stop Emergency Broadcast Request (e.g. "Message Identifier and Serial Number"), to the CBC. The CBC shall authenticate this request.
2. The CBC identifies which MMEs need to be contacted and determines the information to be place into the Warning Area Information Element. The CBC sends a Stop Warning Request message (Message Identifier, Serial Number, Tracking Area ID list, Warning Area, OMC ID, Send Stop Warning Indication) to MMEs.
The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 8 is destined. Co-location of that OMC with the CBC is an operator option.
The CBC sets the Send Stop Warning Indication element in case the MME is requested to forward the Broadcast Completed Area List in a Stop Warning Indication for the warning message.
3. The MME sends a Stop Warning Confirm message that indicates to the CBC that the MME has started to distribute the Kill Request message to eNodeBs.
If this message is not received by the CBC within an appropriate time period, the CBC can attempt to send Stop Warning Request via another MME in the same pool area.
4. Upon reception of the Stop Warning Confirm messages from the MMEs, the CBC may confirm to the CBE that it has initiated the Warning message cancel procedure.
5. The MME forwards the request from the CBC by Kill Request to eNodeB's. The MME shall use the Tracking Area ID list to determine the eNodeBs that may have warning message broadcast ongoing. In case the Tracking Area ID list is not included the Kill Request is forwarded to all eNodeBs that are connected to the MME.
6. The eNodeB shall stop broadcasting the warning message identified by the Message Identifier and Serial Number in the areas identified by Warning Area IDs. If the Warning Area is absent, it shall be interpreted as "all cells on the eNodeB").
When S1-Flex is used the eNodeB may receive same Kill Request from multiple MMEs, if any redundant Kill Requests are detected only the response to the first MME shall contain statistics related to the cancelled broadcast.
7. If the Send Stop Warning Indication parameter was present in the Stop Warning Request and it is configured in the MME based on operator policy, the MME forwards the Broadcast Cancelled Area List it has received from the eNodeB in a Stop Warning Indication(s) to the CBC. The MME may aggregate Broadcast Cancelled Area Lists it receives from eNodeBs.
If the CBC has requested the MME to send Stop Warning Indications, then the CBC releases the Serial Number of a message after it has stopped receiving the Stop Warning Indications for that message.
NOTE: Support for Stop Warning Indication(s) is optional in the MME.
8. From the Kill Response messages returned by eNodeB's the MME creates a trace record (e.g. number of times a particular message has been broadcasted in a given warning area) related to the cancelled message. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.5 Warning Message Delivery Procedure in NG-RAN
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.5.1 General
|
The maximum size of the warning message for NG-RAN is the same as the maximum size defined for E-UTRAN.
When the CBCF sends warning messages to multiple AMFs for the same warning area, the gNodeB may receive duplicated warning messages. Duplicated messages can be detected by checking the message identifier and serial number fields and they shall not be transmitted on the radio interface.
The Warning Message Delivery procedure messages and the Warning Message Cancel procedure messages are transported with the NonUeN2MessageTransfer service operation between CBCF and AMF (see clause 9A) and via N2 between AMF and NG-RAN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.5.2 Warning Message Delivery Procedure
|
The warning message to be broadcast is delivered via AMFs to multiple NG-RAN nodes. The NG-RAN node(s) are responsible for scheduling the broadcast of the new message and the repetitions in each cell.
The overall warning message delivery procedure is presented in figure 9.1.3.5.2-1:
Figure 9.1.3.5.2-1: Warning message delivery procedure in NG-RAN
0. Network registration and security (e.g. mutual authentication) procedures are performed.
NOTE 1: This step is performed each time a UE is attached to a network (e.g. after each power on).
1. CBE (e.g. Information Source such as PSAP or Regulator) sends emergency information (e.g. "warning type", "warning message", "impacted area", "time period") to the CBC. The CBCF shall authenticate this request.
NOTE 2: A warning message 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 if the ePWS language-independent content functionality (see clause 8.3) is supported by CBE.
2. Using the "impacted area" information, the CBCF identifies which AMFs need to be contacted and determines the information to be placed into the Warning Area List NG-RAN Information Element. The CBCF sends a Write-Replace Warning Request NG-RAN message containing the warning message to be broadcast and the delivery attributes (Message Identifier, Serial Number, list of NG-RAN TAIs, Warning Area List NG-RAN, OMC ID, CWM Indicator, Send Write-Replace-Warning-Indication, Global RAN Node ID, Warning Area Coordinates) to AMFs.
The warning messages use the coding scheme for CBS data specified in 3GPP TS 23.038 [3].
The list of NG-RAN TAIs is only used by the AMF. The AMF uses it for selecting which NG-RAN node(s) to forward the Write-Replace Warning Request NG-RAN message to.
If the Write-Replace Warning Request NG-RAN message is sent to reload cells served by a NG-RAN node, for which the CBCF has previously received a Restart Indication (see clause 15A.1 of TS 23.007 [38]), the CBCF shall include the Global RAN Node ID IE with the identity of this NG-RAN node in the Write-Replace Warning Request NG-RAN message.
The Warning Area List NG-RAN shall be a list of Cell IDs or a list of NG-RAN TAIs or one or more Emergency Area IDs. The Warning Area List NG-RAN is only used by the NG-RAN node. The NG-RAN node is configured with the NG-RAN TAI(s) and Cell ID(s) it serves and the Emergency Area ID(s) that it belongs to. The NG-RAN node checks for any match of the contents of the Warning Area List NG-RAN with these IDs to identify the cells where to distribute the warning message. The Warning Area List NG-RAN is an optional information element. If the Warning Area List NG-RAN is absent, it shall be interpreted as "all cells on the NG-RAN node". The number of cell IDs will be limited by the message size on N50 and N2. An Emergency Area ID is unique within the PLMN or SNPN.
The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 9 is destined. Co-location of that OMC with the CBCF is an operator option.
The CBCF shall set the Concurrent Warning Message (CWM) indicator in all Write-Replace Warning Request NG-RAN messages, if the PLMN or SNPN supports concurrent warning message broadcasts.
The CBCF shall not include the "digital signature" or "timestamp" information.
The CBCF shall set the Send Write-Replace-Warning Indication element in case the AMF is requested to forward the Broadcast Scheduled Area List in a Write-Replace Warning Indication NG-RAN for the warning message.
The CBCF includes the Warning Area Coordinates in the Write-Replace-Warning-Request-NG-RAN message based on operator policy.
3. The AMF sends a Write-Replace Warning Confirm NG-RAN message that indicates to the CBCF that the AMF has started to distribute the warning message to NG-RAN nodes.
The Write-Replace Warning Confirm NG-RAN message may contain the Unknown Tracking Area List IE. The Unknown Tracking Area List IE identifies the Tracking Areas that are unknown to the AMF and where the Request cannot be delivered.
If this message is not received by the CBCF within an appropriate time period, the CBCF can attempt to deliver the warning message via another AMF in the same AMF region.
4. Upon reception of the Write-Replace Confirm NG-RAN messages from the AMFs, the CBCF may confirm to the CBE that it has started to distribute the warning message.
5. The AMF forwards Write-Replace Warning Message Request NG-RAN to NG-RAN nodes. The AMF shall use the list of NG-RAN TAIs to determine the NG-RAN nodes in the delivery area. If the list of NG-RAN TAIs is not included and no Global RAN Node ID has been received from the CBCF, the message is forwarded to all NG-RAN nodes that are connected to the AMF, subject to the RAT Selector NG-RAN. If a Global RAN Node ID has been received from the CBCF, the AMF shall forward the message only to the NG-RAN node indicated by the Global RAN Node ID IE.
6. When the CBCF sends warning messages to multiple AMFs for the same warning area, the NG-RAN node may receive the same message from multiple AMFs. The NG-RAN node detects duplicate messages by checking the message identifier and serial number fields within the warning message. If any redundant messages are detected only the first one received will be broadcasted by the cells. The NG-RAN node shall use the Warning Area List NG-RAN information to determine the cell(s) in which the message is to be broadcast. The NG-RAN nodes return a Write Replace Warning Message Response to the AMF, even if it was a duplicate.
If there is a warning broadcast message already ongoing and the CWM Indicator is included in the Write-Replace Warning Request NG-RAN message, the NG-RAN node does not stop the existing broadcast message but starts broadcasting the new message concurrently. Otherwise the NG-RAN node shall immediately replace the existing broadcast message with the newer one.
NOTE 3: If concurrent warning messages are not supported, this requires the CBE/CBCF to take care that 'lower' priority warnings are not sent while a higher priority warning is still being sent.
The NG-RAN node broadcasts the message frequently according to the attributes set by the CBCF that originated the warning message distribution.
7. If the UE has been configured to receive warning messages, and the UE is configured to accept warnings on that PLMN (see 3GPP TS 31.102 [18]) or SNPN (see 3GPP TS 23.122 [49]), then the UE proceeds as follows:
The UE can use "warning type" values, 'earthquake', 'tsunami' or 'earthquake and tsunami', immediately to alert the user. When "warning type" is 'test', the UE silently discards the primary notification, but the UE specially designed for testing purposes may proceed with the following procedures.
The UE activates reception of the broadcast messages containing the "warning message".
If the Warning Area Coordinates are not present:
The UE indicates the contents of the "warning message" to the user.
If the Warning Area Coordinates are present, and if the UE is unable to determine its location:
The UE indicates the contents of the "warning message" to the user.
If the Warning Area Coordinates are present, and the UE determines it is inside the Warning Area Coordinates:
The UE indicates the contents of the "warning message" to the user.
If the Warning Area Coordinates are present, and the UE determines it is outside the Warning Area Coordinates:
The UE does not indicate the contents of the "warning message" to the user. The UE shall store the "warning message" in the list of "warning messages" to be checked for geo-fencing during a UE implementation specific time which shall not be greater than 24 hours. Upon expiration of the UE implementation specific time, the UE shall remove the stored "warning message" from the list of "warning messages" to be checked for geo-fencing.
If the "warning message" is a geo-fencing trigger message (see clause 9.4.1.2.2) then:
- if the list of "warning messages" to be checked for geo-fencing stored at the UE is not empty, the UE shall, for each "warning message" stored at the UE in the list of "warning messages" to be checked for geo-fencing, compare the Serial Number and Message Identifier combination of the stored "warning message" to the list of Serial Number and Message Identifier combinations included in the Warning Message Content IE (CB Data) of the geo-fencing trigger message and encoded as specified in ATIS-0700041 [47], and:
1) if the Serial Number and Message Identifier combination of the stored "warning message" matches one of the Serial Number and Message Identifier combinations included in the geo-fencing trigger message, and:
a) the UE:
i) is able to determine its location and determines it is inside the Warning Area Coordinates of the stored "warning message"; or
ii) is unable to determine its location,
indicate the contents of the stored "warning message" to the user, remove the "warning message" from the list of "warning messages" to be checked for geo-fencing and then discard the geo-fencing trigger message; or
b) the UE is able to determine its location and determines it is outside the Warning Area Coordinates of the stored "warning message", discard the geo-fencing trigger message; or
2) if none of Serial Number and Message Identifier combinations of the stored "warning message" matches any of the Serial Number and Message Identifier combinations included in the Warning Message Content IE (CB Data) of the geo-fencing trigger message, discard the geo-fencing trigger message; and
- if the list of "warning messages" to be checked for geo-fencing stored at the UE is empty, the UE shall discard the geo-fencing trigger message.
If a language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) is included as part of user information contained in the content of a CBS-Message-Information-Page transparently passed from CBC to UEs:
- UEs with user interface which support the ePWS language-independent content functionality (see clause 8.3) and which are capable of displaying text-based warning messages should be capable of displaying the entire warning message that they receive.
Editor's note [WI: ePWS, CR#203]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.
8. If the Send Warning-Message-Indication parameter was present in the Write-Replace Warning Request NG‑RAN and it is configured in the AMF based on operator policy, the AMF shall forward the Broadcast Scheduled Area Lists in a Write-Replace Warning Indication(s) NG-RAN to the CBCF. The Broadcast Scheduled Area List shall contain the Broadcast Completed Area List the AMF has received from the NG-RAN node. The AMF may aggregate Broadcast Completed Area Lists it receives from NG-RAN nodes.
NOTE 4: Support for sending of Write-Replace Warning Indication(s) NG-RAN to the CBCF is optional in the AMF.
9. From the Write-Replace Warning Response messages returned by NG-RAN nodes the AMF determines the success or failure of the delivery and creates a trace record. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.3.5.3 Warning Message Cancel Procedure
|
The cancel warning message delivery procedure takes place when CBE requests to stop the on-going broadcast of warning messages.
Figure 9.1.3.5.3-1: Warning message cancel procedure in NG-RAN
1. CBE initiates procedure by sending Stop Emergency Broadcast Request (e.g. "Message Identifier and Serial Number"), to the CBCF. The CBCF shall authenticate this request.
2. The CBCF identifies which AMFs need to be contacted and determines the information to be placed into the Warning Area Information Element. The CBC sends a Stop Warning Request NG-RAN message (Message Identifier, Serial Number, Tracking Area ID list, Warning Area, OMC ID, Send Stop Warning Indication) to AMFs.
The message may include an OMC ID. If present, it indicates the OMC to which the Trace record generated in step 8 is destined. Co-location of that OMC with the CBCF is an operator option.
The CBCF sets the Send Stop Warning Indication element in case the AMF is requested to forward the Broadcast Completed Area List in a Stop Warning Indication NG-RAN for the warning message.
3. The AMF sends a Stop Warning Confirm NG-RAN message that indicates to the CBCF that the AMF has started to distribute the Cancel Request message to NG-RAN nodes.
If this message is not received by the CBCF within an appropriate time period, the CBCF can attempt to send Stop Warning Request NG-RAN via another AMF in the same AMF region.
4. Upon reception of the Stop Warning Confirm NG-RAN messages from the AMFs, the CBCF may confirm to the CBE that it has initiated the Warning message cancel procedure.
5. The AMF forwards the request from the CBCF by a Cancel Request to NG-RAN nodes. The AMF shall use the Tracking Area ID list to determine the NG-RAN nodes that may have warning message broadcast ongoing. In case the Tracking Area ID list is not included the Cancel Request is forwarded to all NG-RAN nodes that are connected to the AMF, subject to the RAT Selector NG-RAN.
6. The NG-RAN node shall cancel broadcasting the warning message identified by the Message Identifier and Serial Number in the areas identified by Warning Area IDs. If the Warning Area is absent, it shall be interpreted as "all cells on the NG-RAN node".
When the CBCF sends cancel messages to multiple AMFs for the same warning area, the NG-RAN node may receive same Cancel Request from multiple AMFs, if any redundant Cancel Requests are detected only the response to the first AMF shall contain statistics related to the cancelled broadcast.
7. If the Send Stop Warning Indication parameter was present in the Stop Warning Request NG-RAN and it is configured in the AMF based on operator policy, the AMF forwards the Broadcast Cancelled Area List it has received from the NG-RAN node in a Stop Warning Indication(s) NG-RAN to the CBCF. The AMF may aggregate Broadcast Cancelled Area Lists it receives from NG-RAN nodes.
If the CBCF has requested the AMF to send Stop Warning Indications NG-RAN, then the CBCF releases the Serial Number of a message after it has stopped receiving the Stop Warning Indications NG-RAN for that message.
NOTE: Support for Stop Warning Indication(s) NG-RAN is optional in the AMF.
8. From the Cancel Response messages returned by NG-RAN nodes the AMF creates a trace record (e.g. number of times a particular message has been broadcasted in a given warning area) related to the cancelled message. Any OMC ID received in step 2 is written to the trace record to permit the O&M system to deliver them to the desired destination.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.4 UMTS Protocol Overview
|
Figure 5
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.5 E-UTRAN Protocol Overview
|
Legend:
- SBc Application Protocol (SBc-AP): Application Layer Protocol between CBC and MME. This protocol supports transfer of warning messages.
- S1 Application Protocol (S1-AP): Application Layer Protocol between the eNodeB and the MME.
- SCTP for the control plane (SCTP): This protocol guarantees delivery of signalling messages between MME and eNodeB (S1). SCTP is defined in RFC 4960 [33].
Figure 9.1.5-1: CBC - eNodeB
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.1.6 NG-RAN Protocol Overview
|
Figure 9.1.6-1: CBCF - NG-RAN
Legend:
- NG application protocol information for cell broadcast (NG-AP-CB): Subset of NG-AP information that the AMF relays between the AN and the CBCF. NG-AP-CB corresponds to a subset of NG-AP defined in 3GPP TS 38.413 [40].
- NG application protocol (NGAP): Application layer protocol between the NG-RAN node and the AMF. The NGAP protocol is defined in 3GPP TS 38.413 [40].
- SCTP for the control plane (SCTP): This protocol guarantees delivery of signalling messages between AMF and NG-RAN (N2). SCTP is defined in IETF RFC 4960 [33].
- HTTP/2: Application layer protocol for Service based interface between AMF and CBCF. HTTP/2 is defined in IETF RFC 9113 [42].
NOTE: NG-RAN protocol stack for the case where AMF and CBC inter-connects via PWS-IWF is described in annex B.3.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2 Requirements on the CBC-RAN, CBC-MME and CBCF-AMF interfaces
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.0 General
|
The requirements are described by primitives. The term primitive is used to indicate "an abstract, implementation independent interaction between a service user and a service provider" (see ITU-T Recommendation X.210 [12]). For the CBC-BSC/RNC/MME or CBCF-AMF interface, the service provider would be the protocol interconnecting the CBC and BSC/RNC/MME or the CBCF and AMF. A Primitive may therefore be viewed as an abstract, implementation independent request/indication or response/confirm interaction between the service user (CBC/CBCF or BSC/RNC/MME/AMF) and the service provider (protocol). A set of primitives for use between the CBC and BSC/RNC/MME and CBCF and AMF are specified appropriate to the functionality assigned to the CBC/CBCF and BSC/RNC/MME/AMF in clause 5 and clause 6. In order to allow future extensions to the primitives, where possible a primitive shall not be rejected because a parameter is not recognized; the recipient shall ignore the parameter in question and process the remainder of the primitive's parameters as usual.
NOTE: The primitives for the CBCF-AMF interface are also applicable to the PWS-IWF – AMF interface, and the primitives for the CBC-MME interface are also applicable to the CBC-PWS-IWF interface.
The following table gives an overview over the existing primitives:
Name
Originator
Type
Reference
WRITE-REPLACE
CBC
Request/Indication
9.2.2
KILL
CBC
Request/Indication
9.2.3
REPORT
BSC/RNC
Response/Confirm
9.2.4
STATUS-LOAD-QUERY
CBC
Request/Indication
9.2.5
STATUS-LOAD-QUERY
BSC/RNC
Response/Confirm
9.2.6
STATUS-MESSAGE-QUERY
CBC
Request/Indication
9.2.7
STATUS-MESSAGE-QUERY
BSC/RNC
Response/Confirm
9.2.8
REJECT
BSC/RNC
Response/Confirm
9.2.9
RESTART-INDICATION
BSC/RNC
Request/Indication
9.2.10
RESET
CBC
Request/Indication
9.2.11
FAILURE-INDICATION
BSC/RNC
Request/Indication
9.2.12
SET-DRX
CBC
Request/Indication
9.2.13
SET-DRX-REPORT
BSC
Response/Confirm
9.2.14
WRITE-REPLACE-WARNING-REQUEST
CBC
Request/Indication
9.2.16
WRITE-REPLACE-WARNING-CONFIRM
MME
Response/Confirm
9.2.17
STOP-WARNING-REQUEST
CBC
Request/Indication
9.2.18
STOP-WARNING-CONFIRM
MME
Response/Confirm
9.2.19
WRITE-REPLACE-WARNING-INDICATION
MME
Request/Indication
9.2.20
STOP-WARNING-INDICATION
MME
Request/Indication
9.2.21
RESTART-INDICATION-E-UTRAN
MME
Request/Indication
9.2.22
FAILURE-INDICATION-E-UTRAN
MME
Request/Indication
9.2.23
RESET-COMPLETE
BSC/RNC
Response/Confirm
9.2.24
RESET-FAILURE
BSC/RNC
Response/Confirm
9.2.25
WRITE-REPLACE-WARNING-REQUEST-NG-RAN
CBCF/PWS-IWF
Request/Indication
9.2.26
WRITE-REPLACE-WARNING-CONFIRM-NG-RAN
AMF
Response/Confirm
9.2.27
STOP-WARNING-REQUEST-NG‑RAN
CBCF/PWS-IWF
Request/Indication
9.2.28
STOP-WARNING-CONFIRM-NG‑RAN
AMF
Response/Confirm
9.2.29
WRITE-REPLACE-WARNING-INDICATION-NG‑RAN
AMF
Request/Indication
9.2.30
STOP-WARNING-INDICATION-NG‑RAN
AMF
Request/Indication
9.2.31
RESTART-INDICATION-NG‑RAN
AMF
Request/Indication
9.2.32
FAILURE-INDICATION-NG‑RAN
AMF
Request/Indication
9.2.33
In GSM the CBC is integrated into the Core Network. The protocol between the CBC and BSC is defined in 3GPP TS 48.049 [30].
In UMTS the CBC is integrated into the Core Network. The protocol between the CBC and RNC is defined in 3GPP TS 25.419 [29].
In E-UTRAN the CBC is integrated into the Core Network. The protocol between the CBC and MME is defined in 3GPP TS 29.168 [35].
In NG-RAN the CBCF/PWS-IWF is integrated into the Core Network. The protocol between the CBCF/PWS-IWF and AMF is defined in 3GPP TS 29. 518 [41].
NOTE 1: The primitives used in NG-RAN are transported with the NonUeN2MessageTransfer and NonUeN2InfoNotfy service operations between CBCF and the AMF (see clause 9A) and via N2 from AMF to NG-RAN.
NOTE 2: In the following definitions, M indicates "mandatory parameter", O indicates "optional parameter" and C indicates "conditional parameter".
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.1 Identification of a CBS message
|
In GSM within a CBC-BSC interface, a CBS message is uniquely identified by the quartet (Message Identifier, Serial Number, Cell Identifier, Channel Indicator).
In UMTS within the CBC-RNC interface, in E-UTRAN within the CBC-MME interface, and in NG-RAN within the CBCF-AMF interface and CBC – PWS-IWF interface, a CBS message is uniquely identified by the triplet (Message Identifier, Serial Number, Cell Identifier).
This means that even when two CBS messages have the same semantic contents (for example the same weather forecast) but in different languages or coding schemes, they are considered as different and must therefore be identified by a different quartet.
The Serial Number (Old-Serial-Number or New-Serial-Number) is managed cyclically and therefore this does not prevent the re-use of the same quartet for a different CBS message when the serial number have been incremented a sufficient number of times. How to manage the ambiguity is described subsequently.
This unique identification of a CBS message across the CBC-BSC interface is used in all the primitives defined hereafter. This means that the quartet/triplet will be implicitly or explicitly present in every interface primitive which applies to a given CBS message.
This unique quartet/triplet will be referred in the rest of the document as the "message reference".
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.2 WRITE-REPLACE Request/Indication
|
PARAMETER
REFERENCE
PRESENCE (UMTS/GSM)
Message-Identifier
9.3.1
M/M
Old-Serial-Number
9.3.2
O/O
New-Serial-Number
9.3.3
M/M
Cell-List
9.3.5.1
M/M
GSM only [Channel Indicator
9.3.6
O] (note 1)
Category
9.3.7
O/C (note 2)
Repetition-Period
9.3.8
M/C (note 2)
No-of-Broadcasts-Requested
9.3.9
M/C (note 2)
Number-of-Pages
9.3.4
M/C (note 2)
Data Coding Scheme
9.3.18
M/C (note 2)
CBS-Message-Information-Page 1
9.3.19
M/C (note 2)
CBS-Message-Information-Length 1
9.3.20
M/C (note 2)
CBS-Message-Information-Page 2
9.3.19
O/O
CBS-Message-Information-Length 2
9.3.20
O/O
:
:
CBS-Message-Information-Page n
9.3.19
O/O
CBS-Message-Information-Length n
9.3.20
O/O
Paging-ETWS-Indicator
9.3.23
O/O (note 1)
Warning-Type
9.3.24
O/C (note 3)
Warning-Security-Information
9.3.25
O/C (note 3)
GSM only [Warning Period
9.3.26
C] (note 3)
UMTS only [Broadcast Message Content Validity Indicator
9.3.48
O] (note 4)
NOTE 1: Only one of these two optional parameters may be simultaneously present in the primitive. The Channel Indicator parameter is included if the primitive contains a CBS message. The Paging-ETWS-Indicator parameter is included if the primitive contains an ETWS emergency message.
NOTE 2: In GSM this parameter is included if the Channel Indicator parameter is present in the primitive.
NOTE 3: In GSM this parameter is included if the Paging-ETWS-Indicator parameter is present in the primitive.
NOTE 4: In UMTS this parameter is included if the Broadcast Message Content IE present in the primitive does not contain any valid information.
This primitive is sent by the CBC to the BSC/RNC. As this primitive can be used either to broadcast a new CBS message or replace a CBS message already broadcast, the CBC will use the presence and content of the Old‑Serial‑Number and New-Serial-Number fields in this primitive to instruct the BSC/RNC as follows:
a) Old-Serial-Number not present/New-Serial-Number present:
- This is a write request which will be interpreted by the BSC/RNC as an instruction to broadcast a new CBS message in all the cells of the Cell list.
- GSM only [The CBS message will be broadcasted on the channel derived by the Channel Indicator (see the clause on parameters that describes the implicit value of the Channel Indicator when not present in the CBS message)].
The following table identifies the BSC/RNC's behaviour:
Success/Failure of write request
BSC/RNC behaviour
Success
The BSC/RNC completes the following parameters to be returned in the Report PDU:
- a '0' value is entered in the number of broadcasts completed list for the cell
- no entry is made in the failure list for the cell
Failure
The BSC/RNC completes the following parameters to be returned in the Report PDU:
- no entry is made in the number of broadcasts completed list for the cell
- an entry is made in the failure list for the new CBS message identifying the failure cause for the cell
- The BSC/RNC will build as many message references as the number of cells in the list. These message references will be used in particular in the subsequent primitives.
- When a message reference is already known by the BSC/RNC for certain cells in the list (even if the Update field of the Serial-Number is different), the primitive will be rejected for those cells with the cause "message reference already used". The list of cells where the message reference is not valid will be provided in the failure list of the REPORT primitive. For these cells no entry will be made in the number of broadcasts completed parameter.
b) Old-Serial-Number present/New-Serial-Number present.
- This is a replace request which will be interpreted by the BSC/RNC as a kill request for the CBS message with the old serial number, followed by a write request for the CBS message with the new serial number. The handling of the new serial number in the write part of this request, is as described above in the write request where no Old-Serial-Number is supplied. These two kill and write requests are executed sequentially. If the kill request is unsuccessful, the BSC/RNC does not proceed to execute the write request. The kill request will stop broadcast of, and cause all information currently associated with the combination of message identifier, old serial number, GSM only [Channel Indicator] and the list of cells in the Cell list to be deleted from the cells in the BSC/RNC (i.e. for all cells provided in the Cell-List parameter). If the kill request is successful, the subsequent write request information conveyed in the primitive replaces the killed CBS message. The following table identifies the BSC/RNC's behaviour:
Success/Failure of kill request
BSC/RNC behaviour
Success
The BSC/RNC proceeds to execute the write request:
- Write successful: the BSC/RNC completes the following parameters to be returned in the Report PDU:
- An entry is made in the number of broadcasts completed list for the cell.
- No entry is made in the failure list for the cell.
- Write unsuccessful: the BSC/RNC completes the following parameters to be returned in the Report PDU:
- An entry is made in the number of broadcasts completed list for the cell.
- An entry is made in the failure list for the new CBS message identifying the failure cause for the cell.
Failure
The BSC/RNC does not proceed to execute the write request, and completes the following parameters to be returned in the Report PDU:
- no entry is made in the number of completed broadcasts list.
- an entry is made for the old CBS message in the failure list identifying the failure cause for the cell.
All cells which should perform the broadcasting are mentioned in the Cell-List parameter.
The broadcast of the referenced CBS message in the cells which are not mentioned in the Cell-List remains unaffected.
If no category is present, the default category is interpreted by the BSC/RNC, see the parameter clause.
This primitive is responded by a REPORT or REJECT primitive.
NOTE: GSM only [In the case of multipage CBS messages, the individual pages are considered as independent by the BSC scheduling algorithm].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.3 KILL Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message-Identifier
9.3.1
M
Old-Serial-Number
9.3.2
M
Cell-List
9.3.5.1
M
GSM only [Channel Indicator
9.3.6
O]
This primitive is sent by the CBC to the BSC/RNC. The CBC will use this primitive to kill the message indicated by the combination of message identifier, serial number, GSM only [Channel Indicator] and the cells indicated in the Cell-List of this KILL request, i.e. the primitive will halt broadcast of the message in the indicated cells and remove any knowledge of the message from the BSC/RNC for these cells. The broadcast of the referenced message in the cells which are not mentioned in the Cell-List remains unaffected. This primitive is responded with a REPORT or REJECT primitive.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.4 REPORT Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message-Identifier
9.3.1
M
Serial-Number
9.3.2/9.3.3
M
GSM only [Channel Indicator
9.3.6
O]
No-of-Broadcasts-Completed-List
9.3.10
O
Failure-List
9.3.14
O
This primitive will be sent by the BSC/RNC to the CBC in response to WRITE-REPLACE and KILL primitives. The Serial-Number field will contain the old serial number if this primitive is sent in response to a KILL primitive, and the new serial number if the primitive is sent in response to a WRITE-REPLACE primitive.
The No-of-Broadcasts-Completed-List, if present, may contain for each cell the number of broadcasts of the (replaced or killed) CB message with the old message reference sent to this particular cell for broadcast. The serial number information element in the case of a WRITE-REPLACE does not refer to the message for which the number of broadcasts completed information is supplied. The Failure-List, if present, may contain those cells which were present in the related WRITE-REPLACE or KILL primitive and failed the requested operation.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.5 STATUS-LOAD-QUERY Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Cell-List
9.3.5.1
M
GSM only [Channel Indicator]
9.3.6
O
This primitive is sent by the CBC to the BSC/RNC in order to obtain the current loading of the CBCH/UTRAN Radio Resource of particular cells referenced in the Cell-List parameter. This primitive is responded by a STATUS‑LOAD‑QUERY Response/Confirm or a REJECT primitive.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.6 STATUS-LOAD-QUERY Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Radio-Resource-Loading-List
9.3.15
O
Failure-List
9.3.14
O
GSM only [Channel Indicator]
9.3.6
O
This primitive will be sent by the BSC/RNC in response to the STATUS-LOAD-QUERY Request/Indication primitive.
The Radio-Resource-Loading-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the CBCH loading/ UTRAN Radio Resource loading of this particular cell.
NOTE: For cells with DRX the load caused by the schedule messages will be included in the load calculation.
The Radio-ResourceLoading-List will not be present if all cells indicated in the related STATUS-LOAD-QUERY Request/Indication failed the requested operation.
The Failure-List, if present, may contain all cells for which the requested operation failed (e.g. because the cells CBCH is not available in a BTS). The STATUS-LOAD-QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-LOAD-QUERY Request failed the requested operation.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.7 STATUS-MESSAGE-QUERY Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message-Identifier
9.3.1
M
Old-Serial-Number
9.3.2
M
Cell-List
9.3.5.1
M
GSM only [Channel Indicator]
9.3.6
O
This primitive is sent by the CBC to the BSC/RNC in order to obtain the current status of a CB-message for the cells referenced in the Cell-List parameter. This primitive is responded by the STATUS-MESSAGE-QUERY Response/Confirm or by a REJECT Response/Confirm.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.8 STATUS-MESSAGE-QUERY Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message-Identifier
9.3.1
M
Old-Serial-Number
9.3.2
M
No-of-Broadcasts-Completed-List
9.3.10
O
Failure-List
9.3.14
O
GSM only [Channel Indicator]
9.3.6
O
This primitive will be sent by the BSC/RNC to the CBC in response to a STATUS-MESSAGE-QUERY Request/Indication primitive.
The No-of-Broadcasts-Completed-List, if present, may contain each cell which successfully performed the requested operation and for each of these cells the number of times this CB message has been sent to this particular cell for broadcast (parameter Number-of-Broadcasts-Completed; this parameter is not included for the cell if the old message reference is not known to the BSC/RNC, and an entry is made in the failure list). The No-of-Broadcasts-Completed-List will not be present if all cells indicated in the related STATUS-MESSAGE-QUERY Request failed the requested operation.
The Failure-List may contain all cells for which the requested operation failed (e.g. because the broadcast of the requested message was never requested before or because the cells CBCH is not available). The STATUS‑MESSAGE‑QUERY Response/Confirm will not contain the Failure-List parameter if none of the cells in the Cell-List of the related STATUS-MESSAGE-QUERY Request failed the requested operation.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.9 REJECT Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Cause
9.3.16
M
Diagnostic
9.3.17
O
Message-Identifier
9.3.1
O
Serial Number
9.3.2
O
This primitive is sent by the BSC/RNC to the CBC in response to any primitive which is not understood (e.g. invalid parameter or parameter value).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.10 RESTART-INDICATION Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Cell-List
9.3.5.2
M
Recovery Indication
9.3.21
O
GSM only [Broadcast Message Type]
9.3.27
O
The RESTART-INDICATION Request is used by the BSC/RNC to indicate to the CBC a CB related restart situation in one or more of its cells (e.g. when an existing or a new cell becomes operational during normal BSC/RNC operation or when the BSC/RNC initialises).
Any referenced cell are again in CB-operational state (have resumed CB operation). The parameter Recovery Indication, if present, indicates whether CB related data are lost for the cells referenced in the Cell-List and have to be re-loaded. If the Recovery Indication parameter is absent, the CBC shall interpret it as the Recovery Indication with the value data lost.
The CBC upon receiving a RESTART INDICATION indication, marks the cell as operational again. It will usually generate WRITE-REPLACE requests for this cell, according to the actual CB message loading at the moment of the restart.
NOTE: A RESTART-INDICATION can be triggered from the CBC by a RESET Request. This allows recovery from situations, where a PDU occasionally may be lost.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.11 RESET Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Cell-List
9.3.5.1
M
The RESET Request is used by the CBC to force one or more cells of one BSC/RNC into CB-idle state.
The RESET Request may also be used by the CBC to request the CB operational state of cells earlier indicated to have failed (polling CB operational state).
If a BSC/RNC receives a RESET Request, the indicated cells enter idle state (same state as after "power on"). All CB related information concerning earlier CB messages in a referenced cell is lost.
The BSC/RNC acknowledges the RESET Request for each cell by a RESET-COMPLETE response or, if not adequate, by a RESET-FAILUREresponse.
Several responses may be combined using a cell list in the RESET-COMPLETE or RESET-FAILURE response.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.12 FAILURE-INDICATION Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Cell-List
9.3.5.2
M
GSM only [Broadcast Message Type]
9.3.27
O
The FAILURE-INDICATION Request is used by the BSC/RNC to indicate to the CBC a CB related problem situation in one or more of its cells.
Any referenced cell enters CB-not-operational state. The status of the CBS messages is undefined until the Restart‑Indication is sent. It remains in not-operational state until a RESTART-INDICATION request (see clause 9.1.10) indicates normal CB operation (again).
The CBC upon receiving a FAILURE-INDICATION, marks this cell as failed. It will generally not generate further WRITE‑REPLACE requests for this cell, up to the point when the CBC is informed by a RESTART indication, that the cell has resumed CB operation.
The BSC/RNC refuses further WRITE-REPLACE requests from the CBC with the cause "cell‑broadcast‑not‑operational" when any referenced cell is in the CB-not-operational state.
NOTE: A FAILURE-INDICATION can be triggered by a RESET Request. This allows recovery from situations, where a PDU occasionally may be lost.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.13 SET-DRX Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Cell-List
9.3.5.1
M
Schedule-Period
9.3.12
O
Reserved-Slots
9.3.13
O
GSM only [Channel Indicator]
9.3.6
O
This primitive is applicable in GSM only. In UMTS DRX is a mandatory feature in the RNC and no activation/ deactivation function on CBS related radio resources controlled by the CBC is necessary.
The SET-DRX Request is used by the CBC to set DRX specific parameters i.e. the schedule period and the number of slots reserved for high priority CBS messages, see 3GPP TS 44.012 [7]. At least one of the Schedule-Period or Reserved-Slots parameters must be present in the primitive. If this primitive is not supported, the BSC may use default values.
If a BSC receives a SET-DRX Indication, the new DRX parameters will be taken into account starting from the next schedule period in each cell, see 3GPP TS 44.012 [7].
If a BSC receives a SET-DRX Indication, the new DRX parameters will be applied for all cells that do not handle any broadcast message (null loading).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.14 SET-DRX- REPORT Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Cell-List
9.3.5.2
O
Failure-List
9.3.14
O
GSM only [Channel Indicator]
9.3.6
O
This primitive will be sent by the BSC to the CBC in response to a SET-DRX Request/Indication primitive.
The Failure-List will contain those cells which were present in the Request message and which failed the requested operation.
If the new schedule period parameters are not acceptable on a cell due to the load of the cell, the cause "bss‑capacity‑exceeded" is used in the Failure-list.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.15 Void
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.16 WRITE-REPLACE-WARNING-REQUEST Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Repetition-Period E-UTRAN
9.3.36
M
No-of-Broadcasts-Requested
9.3.9
M
List of TAIs
9.3.29
O
Warning Area List
9.3.30
O
Extended Repetition-Period
9.3.37
O
Warning-Type
9.3.24
O
Warning-Security-Information
9.3.25
O
Data Coding Scheme
9.3.18
O (NOTE 1)
Warning Message Content E-UTRAN
9.3.35
O
OMC ID
9.3.31
O
Concurrent Warning Message Indicator
9.3.32
O
Send Write-Replace-Warning-Indication
9.3.39
O
Global eNB ID
9.3.46
O
List of NG-RAN TAIs
9.3.54
O
Warning Area List NG-RAN
9.3.55
O
Warning Message Content NG-RAN
9.3.51
O
Global RAN Node ID
9.3.53
O
RAT Selector NG-RAN
9.3.56
O
Warning Area Coordinates
9.3.63
O
Test Flag
9.3.64
O (NOTE 2)
NOTE1: The Data Coding Scheme IE is not required for ETWS primary notification but it is mandatory for ETWS secondary notification and CMAS warning messages when Warning Message Content E-UTRAN IE is present.
NOTE 2: This IE may only be included if the CBC sends the request to a PWS-IWF.
This primitive is sent by the CBC to the MME or to the PWS-IWF.
The WRITE-REPLACE-WARNING-REQUEST Request/Indication primitive is to request the MME and the AMF to start or overwrite a warning message broadcast. The response to this Request/Indication primitive is sent by the MME or the AMF in a corresponding WRITE-REPLACE-WARNING-CONFIRM primitive.
If the message is sent to the MME, then the List of TAIs IE, the Warning Area List IE, the Warning Message Content E‑UTRAN IE and the Global eNB ID IE may be used and the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE, the Warning Message Content NG-RAN IE, the Global RAN Node ID IE and the RAT Selector NG-RAN IE shall not be used.
If the message is sent to the PWS-IWF, then the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE, the Warning Message Content NG-RAN IE, the Global RAN Node ID IE and the RAT Selector NG-RAN IE may be used and the List of TAIs IE, the Warning Area List IE, the Repetition-Period E-UTRAN IE, the Extended Repetition Period IE, the Warning Message Content E-UTRAN IE, and the Global eNB ID IE shall not be used. The WRITE-REPLACE-WARNING-REQUEST Request/Indication primitive shall then be forwarded to the AMF.
NOTE: For ETWS Primary Notification, the Repetition Period IE and the Number of Broadcasts Requested IE are ignored by eNB if included in WRITE-REPLACE-WARNING-REQUEST message (see 3GPP TS 36.413 [34]).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.17 WRITE-REPLACE-WARNING-CONFIRM Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Cause E-UTRAN
9.3.33
M
Criticality Diagnostics
9.3.34
O
Unknown Tracking Area List
9.3.38
O
Cause NG-RAN
9.3.50
O
Unknown NG-RAN Tracking Area List
9.3.57
O
This primitive is sent by the MME or by the PWS-IWF to the CBC. The PWS-IWF receives this message from the AMF.
The WRITE-REPLACE-WARNING-CONFIRM Response/Confirm primitive is to acknowledge the start or overwrite of a WRITE-REPLACE-WARNING-REQUEST for a warning message.
If the message is received from an MME then the Cause E-UTRAN IE and the Unknown Tracking Area IE may be present. If the message is received from an AMF via a PWS-IWF then the Cause NG-RAN IE and the Unknown NG-RAN Tracking Area List may be present.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.18 STOP-WARNING-REQUEST Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
List of TAIs
9.3.29
O
Warning Area List
9.3.30
O
OMC ID
9.3.31
O
Send Stop Warning Indication
9.3.41
O
Stop-All Indicator
9.3.43
O
List of NG-RAN TAIs
9.3.54
O
Warning Area List NG-RAN
9.3.55
O
RAT Selector NG-RAN
9.3.56
O
This primitive is sent by the CBC to the MME or to the PWS-IWF.
The STOP-WARNING-REQUEST Request/Indication primitive is sent to request to stop a warning message broadcast. The response to this Request/Indication primitiveis sent by the MME or the AMF in a corresponding STOP-WARNING-CONFIRM primitive.
If the message is sent to an MME, then the List of TAIs IE and the Warning Area List IE may be used and the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE and the RAT Selector NG-RAN IE shall not be used.
If the message is sent to the PWS-IWF, then the List of NG-RAN TAIs IE, the Warning Area List NG-RAN IE and the RAT Selector NG-RAN IE may be used and the List of TAIs IE and the Warning Area List IE shall not be used. The STOP-WARNING-REQUEST Request/Indication primitive shall then be forwarded to the AMF.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.19 STOP-WARNING-CONFIRM Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Cause E-UTRAN
9.3.33
M
Criticality Diagnostics
9.3.34
O
Unknown Tracking Area List
9.3.38
O
Cause NG-RAN
9.3.50
O
Unknown NG-RAN Tracking Area List
9.3.57
O
This primitive is sent by the MME or by the PWS-IWF to the CBC. The PWS-IWF receives this message from the AMF.
The STOP-WARNING-CONFIRM Response/Confirm primitive is to acknowledge the receipt of the STOP-WARNING-REQUEST primitive for a warning message.
If the message is received from an MME then the Cause E-UTRAN IE and the Unknown Tracking Area IE may be present. If the message is received from an AMF via the PWS-IWF then the Cause NG-RAN IE and the Unknown NG-RAN Tracking Area List may be present.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.20 WRITE-REPLACE-WARNING-INDICATION Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Broadcast Scheduled Area List
9.3.40
O
Broadcast Scheduled Area List NG-RAN
9.3.58
O
Broadcast Empty Area List
9.3.44
O
Broadcast Empty Area List NG-RAN
9.3.60
O
This Indication is sent by the MME to report to the CBC the Broadcast Scheduled Area List(s) the MME has received from the eNodeB(s) as Broadcast Completed Area List. If the MME has received a WRITE REPLACE WARNING RESPONSE without a Broadcast Completed Area List, then the eNodeB ID shall be included in the Broadcast Empty Area List instead. Multiple responses from eNodeBs may be combined in a Broadcast Scheduled Area List.
This Indication is sent by an AMF via the PWS-IWF to report to the CBC the Broadcast Scheduled Area List(s) NG-RAN the AMF has received from the NG-RAN node(s) as Broadcast Completed Area List. If the AMF has received a WRITE-REPLACE WARNING RESPONSE without a Broadcast Completed Area List, then the gNodeB ID shall be included in the Broadcast Empty Area List NG-RAN instead. Multiple responses from NG-RAN nodes may be combined by the AMF in a Broadcast Scheduled Area List NG-RAN.
If the MME or the PWS-IWF interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME or PWS-IWF shall forward the same WRITE-REPLACE-WARNING-INDICATION message to all CBCs.
The Broadcast Scheduled Area List IE or Broadcast Scheduled Area List NG-RAN IE is not included in the WRITE-REPLACE WARNING INDICATION when the broadcast is unsuccessful in all the cells within the eNodeBs or NG-RAN nodes.
If the message is received from an MME then the Broadcast Scheduled Area List IE may be present. If the message is received from an AMF via the PWS-IWF then the Broadscast Scheduled Area List NG-RAN IE may be present.
The Broadcast Empty Area List IE may be included in the WRITE-REPLACE-WARNING-INDICATION when the MME has received at least one WRITE REPLACE WARNING RESPONSE without Broadcast Completed Area List IE.
The Broadcast Empty Area List NG-RAN IE may be included in the WRITE-REPLACE-WARNING-INDICATION when the AMF has received at least one WRITE REPLACE WARNING RESPONSE without Broadcast Completed Area List IE.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.21 STOP-WARNING-INDICATION Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Broadcast Cancelled Area List
9.3.42
O
Broadcast Empty Area List
9.3.44
O
Broadcast Cancelled Area List NG-RAN
9.3.59
O
Broadcast Empty Area List NG-RAN
9.3.60
O
This primitive is sent by the MME to the CBC.
The STOP-WARNING-INDICATION Request/Indication primitive is to report to the CBC the Broadcast Cancelled Area List the MME has received from the eNodeB in a KILL RESPONSE. If the MME has received a KILL RESPONSE without a Broadcast Cancelled Area List IE, then the eNodeB ID shall be included in the Broadcast Empty Area List instead. The MME may aggregate Broadcast Cancelled Area Lists it receives from eNodeBs.
If the MME interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME shall forward the same STOP-WARNING-INDICATION primitive to all CBCs.
This primitive is sent by an AMF via the PWS-IWF to the CBC.
The STOP-WARNING-INDICATION Request/Indication primitive is to report to the CBC the Broadcast Cancelled Area List the AMF has received from the NG-RAN nodes in a PWS CANCEL RESPONSE. If the AMF has received a PWS CANCEL RESPONSE without a Broadcast Cancelled Area List IE, then the NG-RAN node ID shall be included in the Broadcast Empty Area List NG-RAN instead. The AMF may aggregate Broadcast Cancelled Area Lists it receives from NG-RAN nodes and send them to the CBC via the PWS-IWF.
If the message is received from an MME then the Broadcast Cancelled Area List IE may be present. If the message is received from an AMF via the PWS-IWF then the Broadcast Cancelled Area List NG-RAN IE may be present.
The Broadcast Cancelled Area List IE or Broadcast Cancelled Area List NG-RAN IE is included in the STOP-WARNING-INDICATION when stopping the broadcast was successful in at least one of the cells within the eNodeBs or NG-RAN nodes.
The Broadcast Empty Area List IE shall be included in the STOP-WARNING-INDICATION when the MME has received at least one KILL RESPONSE without Broadcast Cancelled Area List IE.
The Broadcast Empty Area List NG-RAN IE shall be included in the STOP-WARNING-INDICATION when the AMF has received at least one PWS CANCEL RESPONSE without Broadcast Cancelled Area List IE.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.22 RESTART-INDICATION-E-UTRAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Restarted Cell List
9.3.45
M
Global eNB ID
9.3.46
M
List of TAIs
9.3.29
M
Emergency Area ID List
9.3.47
O
Restarted Cell List NG-RAN
9.3.61
O
Global RAN Node ID
9.3.53
O
List of NG-RAN TAIs
9.3.54
O
The RESTART-INDICATION-E-UTRAN message is sent by the MME to the CBC upon receipt of a PWS Restart Indication from an eNodeB, to indicate that the PWS service is restarted in one or more or all cells served by an eNodeB, i.e. the service has become operational and no warning message data is available for these cell(s). Upon receipt of that message, the CBC shall reload the cells if required. See clause 15A.1 of 3GPP TS 23.007 [38].
If the MME interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME shall forward the same RESTART-INDICATION-E-UTRAN message to all CBCs.
The RESTART-INDICATION-E-UTRAN primitive is sent by a PWS-IWF to the CBC, triggered by the AMF sending a RESTART-INDICATION-NG-RAN message to the PWS-IWF upon receipt of a PWS Restart Indication from a NG-RAN node. The RESTART-INDICATION-E-UTRAN message indicates to the CBC that the PWS service is restarted in one or more or all cells served by a NG-RAN node, i.e. the service has become operational and no warning message data is available for these cell(s). Upon receipt of that message, the CBC shall reload the cells if required.
If the indication is received from the PWS-IWF then the Restarted Cell List NG‑RAN IE, the Global RAN Node ID IE and List of NG-RAN TAIs IE shall be present and the Restarted Cell List IE, the Global eNB ID IE and List of TAIs IE are populated with a dummy value (all zeros).
The List of TAIs or List of NG-RAN TAIs, and the Emergency Area ID List shall contain the Tracking Area IDs and Emergency Area IDs (if any) that are configured for the restarted cells listed in the Restarted Cell List, or in the Restarted Cell List NG-RAN.
Upon receiving a RESTART-INDICATION-E-UTRAN shortly after a preceding one, if:
a) the same Restarted Cell List NG-RAN is included in both messages; or
b) the same Restarted Cell List is included in both messages and the Restarted Cell List NG-RAN is absent in both messages;
the CBC shall consider the RESTART-INDICATION-E-UTRAN as a duplicate message and shall ignore it.
NOTE: The CBC can receive the same PWS Restart Indication message via two MMEs of the MME pool for redundancy reasons (see clause 15A.1 of 3GPP TS 23.007 [38]).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.23 FAILURE-INDICATION-E-UTRAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Failed Cell List
9.3.49
M
Global eNB ID
9.3.46
M
Failed Cell List NG-RAN
9.3.62
O
Global RAN Node ID
9.3.53
O
The FAILURE-INDICATION-E-UTRAN message is sent by the MME to the CBC upon receipt of a PWS Failure Indication from an eNodeB, to indicate that ongoing PWS operation in one or more or all cells served by that eNodeB has failed.
If the MME interfaces with multiple CBCs (i.e. has active SCTP associations established with multiple CBCs), the MME shall forward the same FAILURE-INDICATION-E-UTRAN message to all CBCs.
The FAILURE-INDICATION-E-UTRAN message is sent by a PWS-IWF to the CBC, triggered by the AMF sending a FAILURE-INDICATION-NG-RAN message to the PWS-IWF upon receipt of a PWS Failure Indication from a NG-RAN node. The FAILURE-INDICATION-E-UTRAN message indicates to the CBC that ongoing PWS operation in one or more or all cells served by that NG-RAN node has failed.
If the indication is received from a PWS-IWF then the Failed Cell List NG-RAN IE and the Global RAN Node ID IE shall be present and the Failed Cell List IE and the Global eNB ID IE are populated with a dummy value (all zeros).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.24 RESET-COMPLETE Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Cell List
9.3.5.2
M
This primitive will be sent by the BSC/RNC to the CBC in response to a RESET Request primitive if the RESET Request was successful in all the cells, which are indicated in the Cell List.
If the RESET Request was not successful in all the cells then the BSC/RNC shall respond with a RESET-FAILURE Response.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.25 RESET-FAILURE Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Failed Cell List
9.3.5.2
M
Cell List
9.3.5.2
O
This primitive will be sent by the BSC/RNC to the CBC in response to a RESET Request/Indication primitive if the RESET Request was not successful in all the cells.
The cells where the RESET Request failed are indicated in the Failed Cell List and the Cell List contains the list of cells where the RESET was successful, if any.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.26 WRITE-REPLACE-WARNING-REQUEST-NG-RAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Repetition-Period NG-RAN
9.3.52
M
No-of-Broadcasts-Requested
9.3.9
M
RAT Selector NG-RAN
9.3.56
M
List of NG-RAN TAIs
9.3.54
O
Warning Area List NG-RAN
9.3.55
O
Warning-Type
9.3.24
O
Warning-Security-Information
9.3.25
O
Data Coding Scheme
9.3.18
O (NOTE)
Warning Message Content NG-RAN
9.3.51
O
OMC ID
9.3.31
O
Concurrent Warning Message Indicator
9.3.32
O
Send Write-Replace-Warning-Indication
9.3.39
O
Global RAN Node ID
9.3.53
O
Warning Area Coordinates
9.3.63
O
Test Flag
9.3.64
O
NOTE: The Data Coding Scheme IE is not required for ETWS primary notification but it is mandatory for ETWS secondary notification and CMAS warning messages when Warning Message Content NG-RAN IE is present.
This primitive is sent by the CBCF to the AMF to request start or overwrite of a warning message broadcast and is responded to by the AMF in a WRITE-REPLACE-WARNING-CONFIRM-NG-RAN response.
NOTE: For ETWS Primary Notification, the Repetition Period IE and the Number of Broadcasts Requested IE are ignored by NG-RAN node if included in WRITE-REPLACE-WARNING-REQUEST-NG-RAN.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.27 WRITE-REPLACE-WARNING-CONFIRM-NG-RAN Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Cause NG-RAN
9.3.50
M
Criticality Diagnostics
9.3.34
O
Unknown NG-RAN Tracking Area List
9.3.57
O
This primitive is sent by the AMF to the CBCF to acknowledge the CBCF on the start or overwrite of a WRITE-REPLACE-WARNING-REQUEST-NG-RAN for a warning message.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.28 STOP-WARNING-REQUEST-NG-RAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
RAT Selector NG-RAN
9.3.56
M
List of NG-RAN TAIs
9.3.54
O
Warning Area List NG-RAN
9.3.55
O
OMC ID
9.3.31
O
Send Stop Warning Indication
9.3.41
O
Stop-All Indicator
9.3.43
O
This primitive is sent by the CBCF to the AMF to request to stop a warning message broadcast and is responded to by the AMF in a STOP-WARNING-CONFIRM-NG-RAN response.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.29 STOP-WARNING-CONFIRM-NG-RAN Response/Confirm
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Cause NG-RAN
9.3.50
M
Criticality Diagnostics
9.3.34
O
Unknown NG-RAN Tracking Area List
9.3.57
O
This primitive is sent by the AMF to the CBCF to acknowledge the CBCF on receipt of the STOP-WARNING-REQUEST-NG-RAN for a warning message.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.30 WRITE-REPLACE-WARNING-INDICATION-NG-RAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Broadcast Scheduled Area List NG-RAN
9.3.58
O
Broadcast Empty Area List NG-RAN
9.3.60
O
This Indication is sent by the AMF to report to the CBCF the Broadcast Scheduled Area List(s) the AMF has received from the NG-RAN node(s) as Broadcast Completed Area List. If the AMF has received a WRITE-REPLACE WARNING RESPONSE without a Broadcast Completed Area List, then the gNodeB ID shall be included in the Broadcast Empty Area List NG-RAN instead. Multiple responses from NG-RAN nodes may be combined in a Broadcast Scheduled Area List.
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same WRITE-REPLACE-WARNING-INDICATION-NG-RAN message to all CBCFs.
The Broadcast Scheduled Area List IE is not included in the WRITE-REPLACE WARNING INDICATION-NG‑RAN when the broadcast is unsuccessful in all the cells within the NG-RAN nodes.
The Broadcast Empty Area List NG-RAN IE may be included in the WRITE-REPLACE-WARNING-INDICATION when the AMF has received at least one WRITE REPLACE WARNING RESPONSE without Broadcast Completed Area List IE.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.31 STOP-WARNING-INDICATION-NG-RAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Message Identifier
9.3.1
M
Serial-Number
9.3.3
M
Broadcast Cancelled Area List NG-RAN
9.3.59
O
Broadcast Empty Area List NG-RAN
9.3.60
O
This message is sent by the AMF to report to the CBCF the Broadcast Cancelled Area List the AMF has received from the NG-RAN node in a CANCEL RESPONSE. If the AMF has received a CANCEL RESPONSE without a Broadcast Cancelled Area List IE, then the NG-RAN node ID shall be included in the Broadcast Empty Area List instead. The AMF may aggregate Broadcast Cancelled Area Lists it receives from NG-RAN nodes.
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same STOP-WARNING-INDICATION-NG‑RAN message to all CBCFs.
The Broadcast Cancelled Area List IE is included in the STOP-WARNING-INDICATION-NG-RAN when cancelling the broadcast was successful in at least one of the cells within the NG-RAN nodes.
The Broadcast Empty Area List IE shall be included in the STOP-WARNING-INDICATION-NG-RAN when the AMF has received at least one CANCEL RESPONSE without Broadcast Cancelled Area List IE.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.32 RESTART-INDICATION-NG-RAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Restarted Cell List NG-RAN
9.3.61
M
Global RAN Node ID
9.3.53
M
List of NG-RAN TAIs
9.3.54
M
Emergency Area ID List
9.3.47
O
The RESTART-INDICATION-NG-RAN message is sent by the AMF to the CBCF upon receipt of a PWS Restart Indication from a NG-RAN node, to indicate that the PWS service is restarted in one or more or all cells served by an NG-RAN node, i.e. the service has become operational and no warning message data is available for these cell(s). Upon receipt of that message, the CBCF shall reload the cells if required. See 3GPP TS 23.527 [45].
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same RESTART-INDICATION-NG-RAN message to all CBCFs.
The List of TAIs and the Emergency Area ID List shall contain the Tracking Area IDs and Emergency Area IDs (if any) that are configured for the restarted cells listed in the Restarted Cell List.
Upon receiving a RESTART-INDICATION-NG-RAN shortly after a preceding one, if the same Restarted Cell List NG-RAN is included in both messages, the CBCF shall consider the RESTART-INDICATION-NG-RAN as a duplicate message and shall ignore it.
NOTE: The CBCF can receive the same PWS Restart Indication message via two AMFs of the AMF region for redundancy reasons (see 3GPP TS 23.527 [45]).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.2.33 FAILURE-INDICATION-NG-RAN Request/Indication
|
PARAMETER
REFERENCE
PRESENCE
Message Type
9.3.28
M
Failed Cell List NG-RAN
9.3.62
M
Global RAN Node ID
9.3.53
M
The FAILURE-INDICATION-NG-RAN message is sent by the AMF to the CBCF upon receipt of a PWS Failure Indication from a NG-RAN node, to indicate that ongoing PWS operation in one, more or all cells served by that NG-RAN node has failed.
If the AMF interfaces with multiple CBCFs, the AMF shall forward the same FAILURE-INDICATION-NG-RAN message to all CBCFs.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3 Parameters
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.4 Number-of-Pages
|
This parameter enables the number of pages in the CBS message to be indicated.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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);
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.17 Diagnostic
|
Provides additional information associated with Cause parameter and may contain parameter which could not be interpreted/executed.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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]).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
9.3.22 Void
| |
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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).
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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].
|
9201f34afeb642e42ea0146931dc4de9
|
23.041
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.