hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.3.1 Application or Change of Barring in the HLR/HSS/UDM | If barring of roaming is applied to a subscription (or modified or removed) by administrative action in the HLR/HSS/UDM, the HLR/HSS/UDM shall update the subscription information accordingly. If the HLR/HSS/UDM determines from the identity of the VLR and/or the SGSN and/or MME and/or the AMF that the mobile subscriber is currently registered in a barred PLMN, the HLR/HSS/UDM shall put the barring into effect by using a Cancel Location operation to the VLR and/or the SGSN and /or to the MME when applied in HLR/HSS or a UECM Deregistration to AMF when applied in UDM, as shown in figure 2.3.1/1. In the 5G Core case, barring of roaming may be stored in UDR. Upon change of barring of roaming in UDR, UDM clears also user registration in UDR using Nudr_DM_Update operation and unsubscribes to changes on barring of roaming data using Nudr_DM_Unsubscribe operation.
If the mobile subscriber is not currently registered in a barred PLMN, the HLR/HSS/UDM shall take no further action.
MS MSC VLR or SGSN or MME HLR/HSS
ODB of roaming applied
Cancel
<-----------
location
Figure 2.3.1/1: Immediate Application of Barring of Roaming in HLR/HSS
UE AMF UDM
ODB of roaming applied
UECM Deregistration
<----------
Deregistration
<----------
Figure 2.3.1/2: Immediate Application of Barring of Roaming in UDM |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.3.2 Invocation of Barring | Barring of roaming is invoked in the HLR/HSS/UDM. If the HLR receives a request from a VLR for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the MSC and the BSS/RNS to the mobile station over the radio path. If the HLR receives a request from a SGSN for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HLR shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the SGSN and the BSS/RNS to the mobile station over the radio path. If the HSS receives a request from a MME for location updating for a mobile which is attempting to roam to an area prohibited by Operator Determined Barring, the HSS shall reject the location updating request with an appropriate error indication and this error indication shall be relayed by the MME to the mobile station over the radio path. If the UDM receives a request from an AMF for 5G registration for a user equipment who is attempting to roam to an area prohibited by Operator Determined Barring, the UDM shall reject the registration request with an appropriate error indication and this error indication shall be relayed by the AMF to the user equipment over the radio path.
In the 5G Core case, barring of roaming can be optionally stored in UDR. Upon change of barring of roaming in UDR, UDM clears also user registration in UDR using Nudr_DM_Update operation and unsubscribes to changes on barring of roaming data using Nudr_DM_Unsubscribe operation.
Indicative message flow diagrams for the handling of Operator Determined Barring of roaming are given in figures 2.3.2/1, 2.3.2/2, 2.3.2/3 and 2.3.2/4.
MS MSC VLR HLR
Roaming barred because of ODB
LR request
------------->
Location update
---------------->
request Update
Location
----------->
request
Reject
<-----------
(cause)
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/1: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited VLR
MS SGSN HLR
Roaming barred because of ODB
LR request
------------->
GPRS Update
Location
---------------->
request
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/2: Operator Determined Barring of Roaming invocation in HLR. Roaming in a prohibited SGSN
MS MME HSS
Roaming barred because of ODB
LR request
------------->
Update
Location
---------------->
request
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/3: Operator Determined Barring of Roaming invocation in HSS. Roaming in a prohibited MME
UE AMF UDM
Roaming barred because of ODB
Registration request
------------->
UECM Registration
---------------->
request
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.3.2/4: Operator Determined Barring of Roaming invocation in UDM. Roaming in a prohibited AMF |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.4 Barring of Supplementary Services Access | Barring of supplementary services access encompasses the general barring of supplementary services management category specified in 3GPP TS 22.041 [2] and the specific categories of barring of registration of a call forwarded-to number and barring of invocation of call transfer. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.4.1 Application or Change of Barring in the HLR | If barring of supplementary services access is applied to a subscription (or existing barring of supplementary services access is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and, if necessary, transfer the updated subscription information to the VLR using one or more Insert Subscriber Data operations, as shown in figure 2.1.1/1.
If the VPLMN does not support Operator Determined Barring of supplementary service access, the VLR shall indicate this in the acknowledgement to the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.4.2 Invocation of Barring | Barring of supplementary services access is invoked in the HLR or the VLR, depending on the supplementary service operation.
Barring of access to the following supplementary service operations is invoked in the HLR:
- registration;
- erasure;
- activation;
- deactivation;
- password registration;
- processing unstructured SS data.
An indicative message flow diagram for the handling in the HLR of Operator Determined Barring of access to supplementary services is given in figure 2.4.2/1.
MS MSC VLR HLR
Access to Supplementary Services barred because of ODB
SS request
------------->
SS activity
---------------->
request
SS
activity
----------->
request
Reject
<-----------
(cause)
Reject
<----------------
(cause)
Reject
<-------------
(cause)
Figure 2.4.2/1: Operator Determined Barring of Access to Supplementary Services in the HLR
NOTE 1: Although the HLR handles interrogation of some supplementary services, Operator Determined Barring of interrogation of all supplementary services is invoked in the VLR. This reduces the amount of analysis which the VLR must perform on supplementary service requests before deciding whether to relay a supplementary service request to the HLR or reject it because of Operator Determined Barring of access to supplementary services. Operator Determined Barring of control of PLMN specific supplementary services is invoked in the VLR for the same reason.
NOTE 2: Although the VLR handles some processing of unstructured SS data, and therefore has to check for Operator Determined Barring of access to supplementary services, a check is also specified in the HLR to guard against the case where the VLR does not support Operator Determined Barring of access to supplementary services.
Barring of access to the following supplementary service operations is invoked in the VLR:
- interrogation;
- invocation;
- control of PLMN specific supplementary services;
- processing unstructured SS data.
An indicative message flow diagram for the handling in the VLR of Operator Determined Barring of access to supplementary services is given in figure 2.4.2/2.
MS MSC VLR
Access to Supplementary Services barred because of ODB
SS request
------------->
SS activity
---------------->
request
Reject
<----------------
(cause)
Reject
<-----------------
(Cause)
Figure 2.4.2/2: Operator Determined Barring of Access to Supplementary Services in the VLR |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.4.3 Operator Determined Barring of access to supplementary service not supported in VLR | If the VLR does not support Operator Determined Barring of access to supplementary services the HLR shall take the following actions:
The VLR supports only phase 1:
If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request with the appropriate phase 1 error (illegal SS operation or system failure).
The VLR supports phase 2 but does not support this Operator Determined Barring category:
If the HLR receives a request which should normally be barred by the VLR the HLR shall reject the request instead of the VLR.
Note that requests handled locally by the VLR (e.g. interrogation) will not be barred. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.5 Barring of MS initiated PDP context activation | Barring of MS initiated PDP context activation shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2]. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.5.1 Application or Change of Barring in the HLR | If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the SGSN using one or more Insert Subscriber Data operations, as shown in figure 2.5.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
MS SGSN HLR
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.5.1/1: Transfer of updated subscription information to SGSN |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.5.2 Invocation of Barring | Barring of MS initiated PDP context activation is invoked in the SGSN. If the SGSN receives a request for an MS initiated PDP context activation which is prohibited by Operator Determined Barring, the SGSN will return a negative response to the request with an appropriate error indication via the BSS/RNS to the mobile station over the radio path.
NOTE: Barring of MS initiated PDP context activation for Packet Oriented Services is not applicable for Local IP Access (LIPA).
Barring of MS initiated PDP context activation is performed in the SGSN while the SGSN selects the APN and GGSN. The APN operator identifier, a part of selected APN is referred to make a judgement whether to be barred or not. The detail mechanism of the ODB judgement is specified in the 3G TS 23.060 [4].
Indicative message flow diagram for the handling of Operator Determined Barring of MS initiated PDP context activation is given in figures 2.5.2/1.
MS SGSN
MS initiated PDP context activation barred because of ODB
Activate PDP
context request
---------------->
Reject
<----------------
(cause)
Figure 2.5.2/1: Operator Determined Barring of MS initiated PDP context activation in the SGSN
2.5A Barring of EPS Bearer context establishment
Barring of EPS Bearer context establishment shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.5A.1 Application or Change of Barring in the HSS
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly, and transfer the updated subscription information to the MME using one or more Insert Subscriber Data operations, as shown in figure 2.5A.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the MME shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HSS shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
MS MME HSS
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.5A.1/1: Transfer of updated subscription information to MME
2.5A.2 Invocation of Barring
Barring of EPS Bearer context establishment is invoked in the MME. If the MME receives from an UE connected over E-UTRAN an attach or PDN connectivity request which is prohibited by Operator Determined Barring, the MME shall return a negative response to the request with an appropriate error indication to the UE over the E-UTRAN radio path.
NOTE: Barring of EPS Bearer context establishment for Packet Oriented Services is not applicable for Local IP Access (LIPA).
For subscribers completely barred from the Packet Oriented Services, the MME shall reject attach requests.
Barring of EPS Bearer context establishsment for other barring categories for the Packet Oriented Services requires the MME to selects the APN and PDN-GW before it can determine whether a request for EPS Bearer context establishment shall be barred or not:
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in HPLMN, then the MME shall reject the attach or PDN connectivity request,
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in VPLMN, then the MME shall reject the attach or PDN connectivity request.
Indicative message flow diagram for the handling of Operator Determined Barring of EPS Bearer context establishment is given in figures 2.5A.2/1.
UE MME
E-UTRAN PDN connectivity barred because of ODB
Attach Request, or
PDN Connectivity request
---------------->
Reject
<----------------
(cause)
Figure 2.5A.2/1: Operator Determined Barring of EPS Bearer Context Establishment in the MME
2.5B Barring of PDU Session establishment
Barring of PDU Session establishment shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.5B.1 Application or Change of Barring in the UDM
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF/SMF using Nudm_SDM Notification operation, as shown in figure 2.5B.1/1.
MS AMF or SMF UDM
ODB of Packet Oriented Services applied, modified or removed
Nudm_SDM
Notification
<-----------
Figure 2.5B.1/1: Transfer of updated subscription information to AMF/SMF
2.5B.2 Invocation of Barring
Barring of PDU Session establishment is invoked in the SMF. If the SMF receives from an UE connected over 5GS a PDU Session connectivity request which is prohibited by Operator Determined Barring, the SMF shall return a negative response to the request with an appropriate error indication to the UE over the 5G radio path.
NOTE: Barring of PDU Session establishment for Packet Oriented Services is not applicable for Local Access Data Network (LADN).
For subscribers completely barred from the Packet Oriented Services, the AMF may reject the registration requests.
Barring of PDU Session establishment for other barring categories for the Packet Oriented Services, the SMF determines whether a request for PDU Session establishment shall be barred or not based on the subscription data from UDM as below:
- For "bar subscribers completely from the Packet Oriented Services", the SMF shall reject the PDU connectivity request.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", if the subscriber is not located in the HPLMN and the SMF being accessed is located in HPLMN, then the SMF shall reject the PDU connectivity request,
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", if the subscriber is not located in the HPLMN and the SMF being accessed is located in VPLMN, then the SMF shall reject the PDU connectivity request.
The AMF may also determine a request for PDU Session establishment shall be barred or not based on above scenarios and indicate the SMF to reject the request.
Indicative message flow diagram for the handling of Operator Determined Barring of PDU Session establishment is given in figures 2.5B.2/1.
UE SMF
5G PDU connectivity barred because of ODB
PDU Connectivity request
---------------->
Reject
<----------------
(cause)
Figure 2.5B.2/1: Operator Determined Barring of PDU Session Establishment in the SMF |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.6 Barring of Network initiated PDP context activation | Barring of Network initiated PDP context activation shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2]. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.6.1 Application or Change of Barring in the HLR | If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. It is not necessary to transfer the updated subscription information to the SGSN. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.6.2 Invocation of Barring | Barring of Network initiated PDP context activation is invoked in the HLR. If the HLR receives a request for routing information for a PDP context activation directed to a mobile station which is subject to barring of Packet Oriented Services, the HLR will return a negative response to the request for routing information, with an appropriate error indication. The GGSN may relay this error indication to the PDP PDU incoming network using the appropriate interworking.
An indicative message flow diagram for the handling of Operator Determined Barring of Network initiated PDP context activation is given in figure 2.6.2/1.
HLR GGSN N/W
Network initiated PDP context activation barred because of ODB
Incoming PDP PDU
<---------------
(address)
Send routing
<----------------
info request
for GPRS
Reject
---------------->
(cause)
Operator option: error indication returned to network
Reject
--------------->
(cause)
Figure 2.6.2/1: Operator Determined Barring of Network initiated PDP context activation
2.6A Barring of existing PDP contexts
Barring of existing PDP contexts shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3G TS 22.041 [2].
2.6A.1 Application or Change of Barring in the HLR
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly, and transfer the updated subscription information to the SGSN using one or more Insert Subscriber Data operations, as shown in figure 2.6A.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the SGSN shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HLR shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
MS SGSN HLR
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.6A.1/1: Transfer of updated subscription information to SGSN
2.6A.2 Invocation of Barring
Barring of existing PDP contexts is invoked in the SGSN. If the SGSN receives Insert Subsciber Data message due to barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HLR, the SGSN shall take the following action depending on barring category when one or more PDP contexts exist in SGSN.
- For "bar subscribers completely from the Packet Oriented Services", SGSN shall deactivate all existing PDP contexts.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", SGSN shall check whether or not the subscriber is located in the HPLMN. If it is not and the GGSN being accessed is located in HPLMN, then all associated PDP contexts with this path shall be deactivated..
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", SGSN shall check whether or not the subscriber is located in the HPLMN. If it is not and the GGSN being accessed is located in VPLMN, then all associated PDP contexts with this path shall be deactivated.
NOTE: Barring of existing PDP contexts for Packet Oriented Services is not applicable for Local IP Access (LIPA).
2.6B Barring of existing EPS Bearer contexts
Barring of existing EPS Bearer contexts shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.6B.1 Application or Change of Barring in the HSS
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly, and transfer the updated subscription information to the MME using one or more Insert Subscriber Data operations, as shown in figure 2.6B.1/1.
If the VPLMN does not support Operator Determined Barring of Packet Oriented Services, the MME shall indicate this in the acknowledgement of the Insert Subscriber Data message. The HSS shall then, as an operator option, apply barring of roaming as described in clause 2.3 or take any other action decided by the operator of the HPLMN.
UE MME HSS
ODB of Packet Oriented Services applied, modified or removed
Insert
Subscriber
<-----------
data
Figure 2.6B.1/1: Transfer of updated subscription information to MME
2.6B.2 Invocation of Barring
Barring of existing EPS Bearer contexts is invoked in the MME. If the MME receives Insert Subscriber Data message due to barring of Packet Oriented Services being applied to a subscription (or existing barring of Packet Oriented Services is modified) by administrative action in the HSS, the MME shall take the following action depending on barring category when one or more EPS Bearer contexts exist in MME.
- For "bar subscribers completely from the Packet Oriented Services", MME shall deactivate all existing EPS Bearer contexts.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in HPLMN, then all associated EPS Bearer contexts with this path shall be deactivated.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", MME shall check whether or not the subscriber is located in the HPLMN. If it is not and the PDN-GW being accessed is located in VPLMN, then all associated EPS Bearer contexts with this path shall be deactivated.
NOTE: Barring of existing EPS Bearer contexts for Packet Oriented Services is not applicable for Local IP Access (LIPA).
2.6C Barring of existing PDU Sessions
Barring of existing PDU Sessions shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2].
2.6C.1 Application or Change of Barring in the UDM
If barring of Packet Oriented Services is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the UDM, the UDM shall update the subscription information accordingly, and transfer the updated subscription information to the AMF using Nudm_SDM Notification operation, as shown in figure 2.6C.1/1.
UE AMF UDM
ODB of Packet Oriented Services applied, modified or removed
Nudm_SDM
Notification
<-----------
Figure 2.6C.1/1: Transfer of updated subscription information to AMF
2.6C.2 Invocation of Barring
Barring of existing PDU Sessions is invoked in the AMF. If the AMF receives Nudm_SDM Notification message due to barring of Packet Oriented Services being applied to a subscription (or existing barring of Packet Oriented Services is modified) by administrative action in the UDM, or if the new AMF received the barring of Packet Oriented Services from the UDM during a mobility registration procedure, the AMF shall take the following action depending on barring category when one or more PDU Sessions exist in AMF.
- For "bar subscribers completely from the Packet Oriented Services", AMF shall request SMF to release all existing PDU Sessions.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN", AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in HPLMN, then all associated PDU Sessions with this path shall be released by the SMF on request of the AMF.
- For "bar a subscriber from requesting Packet Oriented Services from access points that are within the roamed to VPLMN", AMF shall check whether or not the subscriber is located in the HPLMN. If it is not and the SMF being accessed is located in VPLMN, then all associated PDU sessions with this path shall be released by the SMF on request of the AMF.
NOTE: Barring of existing EPS Bearer contexts for Packet Oriented Services is not applicable for Local Access Data Network (LADN). |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.7 Interactions of Operator Determined Barring with Supplementary Services | The following interactions of Operator Determined Barring with supplementary services have been identified: |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.7.1 Call Forwarding | The interactions between Operator Determined Barring and Call Forwarding are specified in 3GPP TS 22.041 [2].
The interaction where Operator Determined Barring is applied when there is an existing Call Forwarding programme which is in contravention of the Operator Determined Barring programme is shown in the message flow diagram in figure 2.7.1/1. The HLR modifies the subscription information for the mobile subscriber to show that the contravening call forwarding programme is quiescent, and forwards the modified subscription information to the VLR. No indication is forwarded to the mobile station or the user.
MS MSC VLR HLR
ODB applied when Call Forwarding programme contravenes ODB
Insert
Subscriber
<-----------
data
Figure 2.7.1/1: Effect of Operator Determined Barring on Call Forwarding programme
The interaction where the user attempts to activate or register a call forwarding programme which is in contravention of an operator determined barring category is shown in the message flow diagram in figure 2.7.1/2.
MS MSC VLR HLR
Request for Call Forwarding programme contravening ODB
SS request
(register or
------------->
activate CF)
SS activity
---------------->
request
SS
activity
----------->
request
Reject
<-----------
(cause)
Reject
<----------------
(cause)
Operator option: error indication returned to MS
Reject
<-------------
(cause)
Figure 2.7.1/2: Interaction between Operator Determined Barring and Call Forwarding |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.7.2 Closed User Group | The interaction between Operator Determined Barring and Closed User Group is specified in 3GPP TS 22.041 [2]. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for Closed User Group. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.7.3 Call Barring | The interaction between Operator Determined Barring and the Call Barring supplementary service is specified in 3GPP TS 22.041 [2]. In order to meet the service requirement, the checks of a call request in the HLR (for incoming calls) or VLR (for outgoing calls) against the Operator Determined Barring programme shall be carried out before the checks for the Call Barring supplementary service. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.8 Barring of services in I-WLAN | NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN related requirements specified in the present Clause are no longer maintained.
Barring of interworked services in I-WLAN upon the activation of W-APN shall be performed based on the Operator Determined Barring for Packet Oriented Services as defined in 3GPP TS 29.234 [5]. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.8.1 Change of Barring in the HSS | If barring of Packet Oriented Services for I-WLAN is applied to a subscription (or existing barring of Packet Oriented Services is modified or removed) by administrative action in the HSS, the HSS shall update the subscription information accordingly. It is necessary to transfer the updated User Profile Data and subscription information to the 3GPP AAA Server if the subscriber is currently using interworked WLAN services. After downloading the update User Profile Data the 3GPP AAA Server shall initiate re-authorization of the W-APN if there is an existing connection established. The HSS initiated User Profile Data update indication followed by the 3GPP AAA Server download of the updated User Profile Data and re-authorization request is shown in the message flow diagram in Figure 2.8.1/1.
WLAN-UE (Visited/Home) PDG 3GPP AAA Server HSS
ODB of Packet Oriented Services applied, modified or removed
Update of
User Profile
<-----------
data
Download
User Profile
<----------->
data
Re-authorization Request
if there is existing W-APN
connection established
<-----------
Figure 2.8.1/1: Transfer of updated User profile Data to 3GPP AAA Server |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.8.2 Barring of interworked packet services in I-WLAN | The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5].
Barring of interworked WLAN packet services is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization which is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a negative response to the request with an appropriate error code.
Indicative message flow diagram for the handling of Operator Determined Barring of interworked WLAN packet services is given in figure 2.8.2/1.
WLAN-UE (Visited/Home) PDG 3GPP AAA Server HSS
Activation of W-APN when interworked packet services are barred
W-APN (re-)authorization
----------->
Authorization Reject
<-----------
Figure 2.8.2/1: Authorization attempt of a interworked packet services when the WLAN-UE is connecting via a PDG located either in Visited or Home PLMN |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.8.3 Barring of W-APN Activation in I-WLAN | The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5].
Barring of specific W-APN is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization which is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a negative response to the request with an appropriate error code.
Indicative message flow diagram for the handling of Operator Determined Barring of a specific W-APN is given in figure 2.8.3/1.
WLAN-EU (Visited/Home) PDG 3GPP AAA Server HSS
Activation of W-APN when the said W-APN is barred
W-APN (re-)authorization
----------->
Authorization Reject
<-----------
Figure 2.8.3/1: Authorization attempt of a W-APN when the WLAN-UE is connecting via a PDG located either in Visited or Home PLMN |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.8.4 Barring of public Internet access in I-WLAN | The interactions between Operator Determined Barring and W-APN activation/authorization are specified in 3GPP TS 29.234 [5].
Barring of specific public Internet access through a specific W-APN is invoked in the 3GPP AAA Server. If the 3GPP AAA Server receives a request for a W-APN activation/authorization where public Internet access is prohibited by Operator Determined Barring, the 3GPP AAA Server shall return a positive response to the request with appropriate routing policies that allow the PDG filter IP traffic to or from public Internet.
Indicative message flow diagram for the handling of Operator Determined Barring of a specific W-APN is given in figure 2.8.4/1.
WLAN-EU (Visited/Home) PDG 3GPP AAA Server HSS
Activation of W-APN when access to public Internet is barred
W-APN (re-)authorization
----------->
Authorization Accept and
Routing Policy Download
<-----------
Figure 2.8.4/1: Authorization of a W-APN when public Internet access is barred |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.9 Barring of Access to All Except Some Specific DNNs/APNs | |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.9.1 General | Barring of access to all except some specific DNNs/APNs shall be performed based on the Operator Determined Barring for Packet Oriented Services defined in 3GPP TS 22.041 [2]. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.9.2 Application or Change of Barring in the UDM/HSS/HLR | When barring of access to all except some specific DNNs/APNs is invoked in the UDM/HSS/HLR, the UDM/HSS/HLR shall update the subscription profile to contain only the specific non barred DNNs/APNs as the subscribed DNNs/APNs and indicate the updated subscription information to the AMF, SMF, MME or the SGSN.
If the existing default DNN/APN is barred, one of the specific non barred DNN/APNs shall be the new default DNN/APN.
The UDM/HSS/HLR shall disable any other barring of Packet Oriented Services when this function is used.
When barring of access to all except some specific DNNs/APNs is removed in the UDM/HSS/HLR, the UDM/HSS/HLR shall update the subscription profile to restore the originally subscribed DNNs/APNs, including the original default DNN/APN and indicate the updated subscription information to the AMF, SMF, the MME or the SGSN.
For 5GC, if the AMF/SMF/UDM supports the "OdbExemptedDnn" feature, when barring of access to all except some specific DNNs is invoked, the UDM may provision the odbPacketServices together with odbExemptedDnnData which contains those specific DNNs exempted from the barring, without or with spatial and time validity conditions. When barring of access to all except some specific DNNs is removed in the UDM, the UDM removes the odbPacketServices in the AccessAndMobilitySubscriptionData and SessionManagementSubscriptionData. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.9.3 Invocation of Barring | When the AMF, the SMF, the MME or the SGSN updates the subscription, and if the subscriber has existing PDN connectivity for DNNs/APNs not in the received list of subscribed DNN/APN, the SMF, MME or the SGSN deactivates the PDU/PDN connectivity for these DNNs/APNs as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4].
To bar a subscriber from access to all except some specific DNNs/APNs, when the AMF, the MME or the SGSN receives PDU/PDN Connectivity Request message from the UE or the MS, the AMF, the MME or the SGSN shall check whether or not the requested DNN/APN is included in the list of subscribed DNNs/APNs for the subscriber. If included, then the AMF, the MME or the SGSN continues the Attach or UE-requested PDU/PDN connectivity or MS-requested PDP Context Activation procedures as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4]. If not included, then the AMF, the MME or the SGSN rejects the Attach or UE-requested PDU/PDN connectivity or MS-requested PDP Context Activation requests as specified in 3GPP TS 23.502 [7], 3GPP TS 23.401 [6] and 3GPP TS 23.060 [4]. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3 Information stored in location registers | |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.1 Information stored in the HLR/HSS | The HLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of outgoing calls (including mobile originated short messages) - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing calls when roaming outside the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring of incoming calls (including mobile terminated short messages) - one of:
- Barring of all incoming calls;
- Barring of all incoming calls when roaming outside the home PLMN country;
- Barring of all incoming calls when roaming outside the zone of the home PLMN country.
Barring of roaming - one of:
- Barring of roaming outside the home PLMN;
- Barring of roaming outside the home PLMN country.
Barring of outgoing premium rate calls - one or both of:
- Barring of outgoing premium rate (information) calls;
- Barring of outgoing premium rate (entertainment) calls.
Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Supplementary Services Management.
Barring of registration of call forwarding - one of:
- Barring of registration of any forwarded-to number;
- Barring of registration of any international forwarded-to number;
- Barring of registration of any international forwarded-to number except a number within the HPLMN country;
- Barring of registration of any inter-zonal forwarded-to number;
- Barring of registration of any inter-zonal forwarded-to number except a number within the HPLMN country.
Barring of invocation of call transfer:
one of:
- Barring of invocation of any call transfer;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN;
and independently:
- Barring of invocation of call transfer where both calls are calls charged to the served subscriber;
and independently:
- Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR.
Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN;
- Barring of access to all except some specific APNs.
3.1A Information stored in the UDM/UDR
Barring of roaming - one of:
- Barring of roaming outside the home PLMN;
- Barring of roaming outside the home PLMN country.
- Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN;
- Barring of access to all except some specific DNNs, optionally with spatial and time validity conditions. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.2 Information stored in the VLR | The VLR must store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of outgoing calls (including mobile originated short messages) - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring of outgoing premium rate calls - one or both of:
- Barring of outgoing premium rate (information) calls;
- Barring of outgoing premium rate (entertainment) calls.
Barring specific to the home PLMN - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Supplementary Services Management.
Barring of invocation of call transfer:
one of:
- Barring of invocation of any call transfer;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates, i.e. the call is either an outgoing international call or an incoming call when the served subscriber roams outside the HPLMN country;
- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates, i.e. the call is either an outgoing inter-zonal call or an incoming call when the served subscriber roams to a VPLMN in a different zone from the HPLMN.
and independently:
- Barring of invocation of call transfer where both calls are calls charged to the served subscriber;
and independently:
- Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.3 Information stored in the SGSN | The SGSN shall store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of mobile originated short messages - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring specific to the home PLMN of mobile originated short messages - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
3.3A Information stored in the MME
The MME shall store subscription information for each mobile subscriber to define which of the following categories of barring is to be applied, independently of each other:
Barring of mobile originated short messages - one of:
- Barring of all outgoing calls;
- Barring of all outgoing international calls;
- Barring of all outgoing international calls except those directed to the home PLMN country;
- Barring of all outgoing inter-zonal calls;
- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;
- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.
Barring specific to the home PLMN of mobile originated short messages - when the mobile station is registered in its home PLMN, any one or more of:
- Operator Specific Barring (Type 1);
- Operator Specific Barring (Type 2);
- Operator Specific Barring (Type 3);
- Operator Specific Barring (Type 4).
Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.4 Transfer of Subscription Information from HLR to VLR | The following subscription information for Operator Determined Barring must be transferred from the HLR to the VLR when a mobile station registers in a VLR:
- Barring of outgoing calls;
- Barring of outgoing premium rate calls;
- Barring of supplementary services management;
- Barring of invocation of call transfer.
In addition, when a mobile station registers in a VLR in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN must be transferred from the HLR to the VLR. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.5 Transfer of Subscription Information from HLR to SGSN | The following subscription information for Operator Determined Barring shall be transferred from the HLR to the SGSN when a mobile station registers in a SGSN:
- Barring of outgoing calls (which leads to barring of mobile originated short messages).
The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the HLR to the SGSN when a mobile station registers in a SGSN:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
In addition, when a mobile station registers in a SGSN in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the HLR to the SGSN.
3.5A Transfer of Subscription Information from HSS to MME
The following subscription information for Operator Determined Barring shall be transferred from the HLR to the MME when a mobile station registers in a MME:
- Barring of outgoing calls (which leads to barring of mobile originated short messages).
The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the HSS to the MME when a mobile station registers in a MME:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.
In addition, when a mobile station registers in an MME in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the HLR to the MME. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.6 I-WLAN Information stored in the HSS | The HSS shall store subscription information for each I-WLAN subscriber to define which of the following categories of barring is to be applied, independently of each other. These barring categories are applied to WLAN 3GPP IP Access:
- Barring of Interworking WLAN completely from the interworked service capabilities.
- Barring of a subscriber from requesting interworking through Packet Data Gateways that are within the HPLMN whilst the subscriber is WLAN connected via a VPLMN.
- Barring a subscriber from requesting packet-oriented services from Packet Data Gateways that are within the roamed to VPLMN.
- Barring of a subscriber from requesting direct Internet access from Packet Data Gateways that are within the I-WLAN. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.7 Transfer of User Profile Data from HSS to 3GPP AAA Server | The following User Profile Data for Operator Determined Barring must be transferred from the HSS to the 3GPP AAA Server when a WLAN-UE authenticates to 3GPP AAA Server and the I-WLAN service:
- Barring of Interworking WLAN completely from the interworked service capabilities
- Barring of a subscriber from requesting interworking through Packet Data Gateways that are within the HPLMN whilst the subscriber is WLAN connected via a VPLMN
- Barring a subscriber from requesting packet-oriented services from Packet Data Gateways that are within the roamed to VPLMN
- Barring of a subscriber from requesting direct Internet access from Packet Data Gateways that are within the I-WLAN |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.8 Information stored in the AMF/SMF | Barring of Packet Oriented Services - one of:
- Barring of all Packet Oriented Services;
- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;
- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN. |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 3.9 Transfer of Subscription Information from UDM to AMF/SMF | The following subscription information for Operator Determined Barring for Packet Oriented Services shall be transferred from the UDM to the AMF/SMF: - Barring of all Packet Oriented Services; - Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN; - Barring of Packet Oriented Services from access points that are within the roamed to VPLMN. In addition, when a mobile station registers in an AMF in its home PLMN the subscription information for Operator Determined Barring specific to the home PLMN shall be transferred from the UDM to the AMF/SMF. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version Apr 1999 Transferred to 3GPP CN1 CN#03 Approved at CN#03 3.0.0 CN#04 001 Corrections to text to introduce barring of SMS calls for GPRS 3.1.0 CN#11 Version updated from R99 to Rel-4 after CN#11 4.0.0 CN#11 002 Add PDP context activation barring scenario, etc 4.0.0 CN#15 References updated 4.0.1 CN#16 Release 5 after CN#16 5.0.0 CN#24 007r2 2 ODB handling for existing PDP contexts 6.0.0 CT#35 0008 1 Realization of Operator Determined Barring 7.0.0 CT#40 0009 1 ODB for 3GPP access in EPS 8.0.0 CT#42 Copyright Notification updated 8.0.1 CT#42 0011 1 Operator Determined Barring for EPS 8.1.0 CT#46 - Update to Rel-9 version (MCC) 9.0.0 CT#50 0012 2 LIPA for ODB case 10.0.0 CT#57 Update to Rel-11 version (MCC) 11.0.0 CT#58 0014 3 Addition of APN to the condition of the ODB judgment 11.1.0 CT#59 0015 1 Updating Default APN by HSS when Barring of access to all except some specific APNs applied 11.2.0 CT#59 0016 1 Barring of Access to All Except Some Specific APNs 11.2.0 CT#59 0017 ODB Not Applied to Emergency Bearer Services 11.2.0 CT#60 0018 1 SMS in MME 11.3.0 2014-09 - Update to Rel-12 version (MCC) 12.0.0 CT#68 0019 1 Correction to the I-WLAN reference 12.1.0 2015-12 - Update to Rel-13 version (MCC) 13.0.0 2017-03 - Update to Rel-14 version (MCC) 14.0.0 2018-06 - Update to Rel-15 version (MCC) 15.0.0 2018-12 CT#82 CP-183092 0020r3 3 F Introduction of Barring of Roaming in 5GC 15.1.0 2020-03 CT#87e CP-200045 0021 1 F Invocation of ODB 16.0.0 2021-03 CT#91e CP-210053 0022 1 F ODB handling in SMF 16.1.0 2022-03 - - - - - Update to Rel-17 version (MCC) 17.0.0 2023-12 CT#102 CP-233073 0025 - A Clean Up 17.1.0 2023-12 CT#102 CP-233071 0023 1 F Essential Correction for Barring of PDU Session in 5GS 17.1.0 2023-12 CT#102 CP-233044 0026 - F ODB clarification 18.0.0 2024-06 CT#104 CP-241050 0027 3 F AMF Determined PDU Session Establishment Rejection Due to ODB 18.1.0 2024-09 CT#105 CP-242033 0028 - B ODB Exempted DNNs 19.0.0 |
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 1 Scope
| The present document describes the Cell Broadcast short message service (CBS) for GSM and UMTS.
For GSM it defines the primitives over the Cell Broadcast Centre - Base Station System (CBC-BSS) interface and the message formats over the Base Station System - Mobile Station (BSS-MS) interface for Teleservice 23 as specified in 3GPP TS 22.003 [2].
For UMTS it defines the interface requirements for the Cell Broadcast Centre – UMTS Radio Network System (RNS) interface and the radio interface requirements for UMTS Radio Acces Networks to support CBS as specified in 3GPP TS 22.003 [2].
The present document also describes the Public Warning System (PWS) for GSM, UMTS, E-UTRAN, satellite E-UTRAN, NG‑RAN, and satellite NG-RAN, see 3GPP TS 22.268 [28].
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 1.1 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] Void
[2] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)".
[3] 3GPP TS 23.038: "Alphabets and language‑specific information".
[4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[5] Void.
[6] 3GPP TR 03.49 Version 7.0.0: "Digital cellular telecommunication system (Phase 2+); Example protocol stacks for interconnecting Cell Broadcast Centre (CBC) and Base Station Controler (BSC)".
[7] 3GPP TS 44.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".
[8] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[9] Void.
[10] 3GPP TS 48.052: "Base Station Controller ‑ Base Transceiver Station (BSC - BTS) interface; Interface principles".
[11] 3GPP TS 48.058: "Base Station Controller ‑ Base Transceiver Station (BSC - BTS) interface; Layer 3 specification".
[12] ITU-T Recommendation X.210: "Information technology - Open systems interconnection - Basic Reference Model: Conventions for the definition of OSI services".
[13] 3GPP TS 48.008: "Mobile-services Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification".
[14] 3GPP TS 23.042: "Compression algorithm for text messaging services".
[15] 3GPP TS 23.048: "Security Mechanisms for the SIM application toolkit".
[16] 3GPP TS 25.331: "Radio Resource Control (RRC); Protocol specification".
[17] 3GPP TS 25.401: "UTRAN Overall Description".
[18] 3GPP TS 31.102: "Characteristics of the USIM Application".
[19] 3GPP TS 25.324: "Broadcast/Multicast Control BMC".
[20] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[21] 3GPP TR 25.925: "Radio Interface for Broadcast/Multicast Services".
[22] Void.
[23] Void.
[24] Void.
[25] GSMA AD.26: "Coding of Cell Broadcast Functions".
[26] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[27] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol".
[28] 3GPP TS 22.268: "Public Warning System (PWS) Requirements".
[29] 3GPP TS 25.419: "UTRAN Iu-BC Interface: Service Area Broadcast Protocol (SABP)".
[30] 3GPP TS 48.049: "Base Station Controller - Cell Broadcast Centre (BSC-CBC) Interface Specification; Cell Broadcast Service Protocol (CBSP)".
[31] Void.
[32] ETSI TS 102 900: "European Public Warning System (EU-ALERT) using the Cell Broadcast Service".
[33] IETF RFC 4960: "Stream Control Transmission Protocol".
[34] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[35] 3GPP TS 29.168: "Cell Broadcast Centre interfaces with the Evolved Packet Core".
[36] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[37] Void.
[38] 3GPP TS 23.007: "Restoration Procedures".
[39] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[40] 3GPP TS 38.413: "NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP)".
[41] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[42] IETF RFC 9113: "HTTP/2".
[43] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[44] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[45] 3GPP TS 23.527: "5G System; Restoration Procedures; Stage 2".
[46] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2".
[47] ATIS-0700041: "WEA 3.0: Device-Based Geo-Fencing".
[48] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[49] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
[50] 3GPP TS 23.251: "Network Sharing; Architecture and functional description".
[51] 3GPP TS 38.401: "NG-RAN; Architecture description"
[52] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3"
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 1.2 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [20] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [20].
5GS 5G System
5GCN 5G Core Network
EPC Evolved Packet Core
ePWS enhancements of Public Warning System
NR New Radio
SNPN Stand-alone Non-Public Network
ULI User Location Information
WEA Wireless Emergency Alert
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 1.3 Definitions
| For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Additional ULI: TAI and NR CGI of a PLMN or a SNPN to which the MWAB-gNB provides access, that reflects the location of the MWAB-UE (see Additional ULI in 3GPP TS 23.501 [39] subclause 5.49.4), or TAI and NR CGI of a PLMN to which the IAB-donor of the MBSR provides access, and which is the ULI of the IAB-UE of the MBSR (see Additional ULI in 3GPP TS 23.501 [39] subclause 5.35A.6).
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501 [39] apply:
5G System
IAB-donor
MBSR
MWAB
MWAB-gNB
NG-RAN
For the purposes of the present document, the following terms and definitions given in 3GPP TS 38.300 [44] apply:
gNB
NG-RAN node
ng-eNB
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.122 [39] apply:
Subscribed SNPN
For the purposes of the present document, the following terms and definitions given in 3GPP TS 38.401 [51] apply:
gNB-DU
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.501 [52] apply:
MWAB-UE
MBSR-UE
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 2 General description
| The CBS service is analogous to the Teletex service offered on television, in that like Teletex, it permits a number of unacknowledged general CBS messages to be broadcast to all receivers within a particular region. CBS messages are broadcast to defined geographical areas known as cell broadcast areas. These areas may comprise of one or more cells, or may comprise the entire PLMN or SNPN. Individual CBS messages will be assigned their own geographical coverage areas by mutual agreement between the information provider and the PLMN or SNPN operator. CBS messages may originate from a number of Cell Broadcast Entities (CBEs), which are connected to the Cell Broadcast Centre. CBS messages are then sent from the CBC to the cells, in accordance with the CBS's coverage requirements.
A CBS page comprises of 82 octets, which, using the default character set, equates to 93 characters. Other Data Coding Schemes may also be used, as described in 3GPP TS 23.038 [3]. Up to 15 of these pages may be concatenated to form a CBS messagee. Each page of such CBS message will have the same message identifier (indicating the source of the message), and the same serial number. Using this information, the MS/UE is able to identify and ignore re‑broadcasts of already received messages.
CBS messages are broadcast cyclically by the cell at a frequency and for a duration agreed with the information provider. The frequency at which CBS messages are repeatedly transmitted will be dependent on the information that they contain; for example, it is likely that dynamic information such as road traffic information, will require more frequent transmission than weather information. The repetition period will also be affected by the desire for CBS messages to be received by high speed mobiles which rapidly traverse cells. Reception of CBS messages for an MS/UE is not a requirement if it is connected in the CS domain. It should be possible for an MS/UE to receive messages if it is connected in the PS domain and no data is currently transmitted.
CS-Domain
CS-Connected
CS-Idle
CS-Idle
PS-Domain
-
PS-Idle
PS-Connected
Reception of CBS Message
Not possible
Possible
Depends on RRC mode
NOTE: In case the UE is in CS-Idle and PS-Connected Mode it depends on the Radio Resource Control State whether reception of CBS messages is possible. The relevant states are described in 3GPP TS 25.331 [16].
GSM only [CBS messages may be broadcast on two different cell broadcast channels, which are characterized by different QoS. A MS is always able to read the basic channel (see 3GPP TS 45.002 [8]). The reading of the extended channel may collide with other tasks of the MS. Therefore the probability of receiving a CBS message on the extended channel is smaller than on the basic channel. The reading of the extended channel for MSs is optional. The scheduling on the channels will be done independently].
To permit mobiles to selectively display only those CBS messages required by the MS/UE user, CBS messages are assigned a message class which categorises the type of information that they contain and the language (Data Coding Scheme) in which the CBS message has been compiled. Through the use of appropriate MMI, the user is then able to ignore message types that he does not wish to receive, e.g. advertising information or messages in an unfamiliar language.
A network may be able to remotely activate mobile terminals in order to enable them to receive CBS messages, according to regulatory requirements (see 3GPP TS 25.331 [16]).
PWS provides a service that allows the network to distribute warning messages on behalf of public authority. PWS enables the distribution of ETWS, CMAS (aka WEA), KPAS and EU-Alert warning messages in GSM, UMTS, E-UTRAN, and NG‑RAN.
Some of the PWS warning message distribution mechanisms are access technology specific, but some CBS procedures and related message structures are common for GSM and UMTS, and some CBS procedures and related message structures are common for E-UTRAN and NG‑RAN.
The language-independent content mapped to an event or a disaster can be included in a warning message that is transparently passed from CBC to UEs. UEs with user interface which support the ePWS language-independent content functionality can display the entire warning message that they receive.
UEs with no user interface which support the ePWS disaster characteristics functionality can derive the characteristics of a disaster from the message identifier of a received warning message.
Requirements applicable for E-UTRAN are also applicable for satellite E-UTRAN, unless otherwise specified.
Requirements applicable for NG-RAN are also applicable for satellite NG-RAN, unless otherwise specified.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 3 Network Architecture
| |
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 3.0 General
| The chosen network architectures differ for GSM, UMTS, EPS, and 5GS. In clause 3.1 the GSM network architecture is descripted, in clause 3.2 the UMTS network architecture, in clause 3.3 the EPS network architecture, and in clause 3.4 the 5GS network architecture.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 3.1 GSM Network Architecture
| The basic network structure of CBS is depicted by figure 1.
Figure 1
- message transfer on link 1 is outside the scope of 3GPP specifications;
- message transfer on link 2 is described in clause 9.1;
- message transfer on link 3 is described in 3GPP TS 48.058 [11];
- message transfer on link 4 is described in 3GPP TS 44.012 [7] and the timing of messages transferred on link 4 is described in 3GPP TS 45.002 [8].
3GPP TS 23.251 [50] specifies additional requirements for providing CBS in shared GERAN.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 3.2 UMTS Network Architecture
| The basic network structure of CBS is depicted by figure 2.
Figure 2
The basic network structure replaces the GSM BSS with the UTRAN containing the RNC and the Node B. The cell broadcast centre (CBC) is part of the core network and connected to a routing node e.g. a 3G SGSN via the Bc reference point. Thus the CBC can reach every RNC via the user plane of the Iu interface. On the logical interface between the CBC and the RNC protocol is described in 3GPP TS 25.419 [29]. The other UTRAN related interfaces are described in the according UTRAN specifications based on the 3GPP TR 25.925 [21]. Based on this architecture and the current requirements for cell broadcast the core network elements like MSC, VLR, HLR etc are not involved for the service delivery.
The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
3GPP TS 23.251 [50] specifies additional requirements for providing CBS in shared UTRAN.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 3.3 EPS Network Architecture
| The basic network structure of PWS architecture in E-UTRAN is depicted by figure 3.3-1.
Figure 3.3-1: PWS architecture
The cell broadcast centre (CBC) is part of the core network and connected to the MME via the SBc reference point. The interface between the CBC and the MME is described in 3GPP TS 29.168 [35] and the interface between the MME and the eNodeB is described in 3GPP TS 36.413 [34].
The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
3GPP TS 23.251 [50] specifies additional requirements for providing PWS in shared E-UTRAN.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 3.4 5GS Network Architecture
| Figures 3.4-1, 3.4.-2 and 3.4-3 depict the basic network structure of 5GS PWS architecture.
Figure 3.4-1 depicts the 5GS PWS system architecture, using service-based interfaces between CBCF and AMF, showing how the network functions interact with each other. This option is further described in clauses 4 to 8. The service-based interfaces are further described in clause 9A.
Figure 3.4-1: 5GS PWS architecture
NOTE: No services are provided by CBCF or PWS-IWF, thus no service-based interfaces are depicted for these NFs in the 5GS PWS architecture.
Figure 3.4-2 depicts the basic network structure of 5GS PWS architecture using the reference point representation showing how the network functions interact with each other when no PWS-IWF is used. This option is further described in clauses 4 to 8.
Figure 3.4-2: 5GS PWS architecture in reference point representation without PWS-IWF
Figure 3.4-3 depicts the basic network structure of 5GS PWS architecture using the reference point representation showing how the network functions interact with each other when PWS-IWF is used. This option is further described in Annex B.
Figure 3.4-3: 5GS PWS architecture in reference point representation with PWS-IWF
The 5GS PWS architecture contains the following service-based interface:
Namf: Service-based interface exhibited by AMF.
The 5GS PWS architecture contains the following reference points:
N2: Reference point between the NG-RAN and the AMF.
NOTE 1: NG-RAN can be NR based or E-UTRA based (See 3GPP TS 23.501 [39] , 3GPP TS 38.413 [40] and 3GPP TS 36.413 [34]).
N50: Reference point between the AMF and the CBCF or between the AMF and the PWS-IWF.
NOTE 2: N50 uses service-based interfaces, further described in clause 9A of the present document.
SBc: Reference point between the PWS-IWF and the CBC.
The CBE and the interface between CBE and CBC are out of scope of 3GPP specifications.
In shared NG-RAN, PWS is provided via a single common CBCF which connects to the shared NG-RAN via one or more AMFs, or via a single common CBC which connects to the shared NG-RAN via one or more AMFs and one or more PWS-IWFs. The deployment and configuration of the common CBCF or the common CBC is per agreement between the sharing operators. The sharing operators need to coordinate PWS between each other.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 4 CBE Functionality
| The functionality of the CBE is outside of the scope of 3GPP specifications; however it is assumed that the CBE is responsible for all aspects of formatting CBS messages, including the splitting of a CBS message into a number of pages.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 5 CBC Functionality
| In 3GPP the CBC is integrated as a node in the core network.
The CBC may be connected to several BSCs/RNCs/MMEs/PWS-IWFs. The CBC may be connected to several CBEs. The CBC shall be responsible for the management of CBS messages including:
- allocation of serial numbers;
- modifying or deleting CBS messages held by the BSC/RNC/eNodeB/NG-RAN node;
- initiating broadcast by sending fixed length CBS messages to a BSC/RNC/eNodeB/NG-RAN node for each language provided by the cell, and where necessary padding the pages to a length of 82 octets (see 3GPP TS 23.038 [3]);
- determining the set of cells to which a CBS message should be broadcast, and indicating within the Serial Number the geographical scope of each CBS message;
- determining the time at which a CBS message should commence being broadcast;
- determining the time at which a CBS message should cease being broadcast and subsequently instructing each BSC/RNC/eNodeB/NG-RAN node to cease broadcast of the CBS message;
- determining the period at which broadcast of the CBS message should be repeated;
- determining the cell broadcast channel in GSM, on which the CBS message should be broadcast.
- when CBS transmits emergency messages, allocation of "emergency indication" to differentiate it from normal CBS messages, including the "Cell ID/Service Area ID list", "warning type", "warning message". If "warning type" is of 'test', only UEs which are specially designed for testing purposes may display warning message.
To work efficiently on the interfaces, the BSC/RNC - which is normally controlling more than one cell of a broadcast area - should be used as a concentrator as far as CBS message handling is concerned. Hence, the CBC should work on lists of cells when issuing CB related requests towards the BSC/RNC.
5A CBCF Functionality
In 3GPP the CBCF is a network function in the 5G core network.
The CBCF may be connected to several AMFs. The CBCF may be connected to several CBEs. The CBCF shall be responsible for the management of CBS messages including:
- allocation of serial numbers;
- modifying or deleting CBS messages held by the NG-RAN node;
- initiating broadcast by sending fixed length CBS messages to a NG-RAN node for each language provided by the cell, and where necessary padding the pages to a length of 82 octets (see 3GPP TS 23.038 [3]);
- determining the set of cells to which a CBS message should be broadcast, and indicating within the Serial Number the geographical scope of each CBS message;
- determining the time at which a CBS message should commence being broadcast;
- determining the time at which a CBS message should cease being broadcast and subsequently instructing each NG-RAN node to cease broadcast of the CBS message;
- determining the period at which broadcast of the CBS message should be repeated;
- when CBS transmits emergency messages, allocation of "emergency indication" to differentiate it from normal CBS messages, including the "Cell ID/Service Area ID list", "warning type", "warning message". If "warning type" is of 'test', only UEs which are specially designed for testing purposes may display warning message.
The CBCF supports service based interface. The CBCF uses AMF communication services to forward warning messages to the NG-RAN and to subscribe to receive warning delivery related notifications.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 6 BSC/RNC/MME/AMF Functionality
| The BSC/RNC shall interface to only one CBC. A BSC may interface to several BTSs as indicated by 3GPP TS 48.052 [10]. An RNC may interface to several Node Bs.
The MME may interface to one CBC or multiple CBCs (i.e. the MME is allowed to have SCTP transport associations established with one or multiple CBCs). An MME may interface to several eNodeBs.
The AMF may interface to one CBCF or multiple CBCFs (i.e. the AMF is allowed to have HTTP/2 application layer associations with one or multiple CBCFs). An AMF may interface to several NG-RAN nodes.
The BSC/RNC/MME/AMF shall be responsible for:
BSC
RNC
MME
AMF
Interpretation of commands from the CBC.
Storage of messages from the CBC.
Not applicable
Scheduling of CBS messages on the CBCH.
Scheduling of CBS messages on the CBS related radio resources.
Not applicable
Not applicable
Providing an indication to the CBC when the desired repetition period cannot be achieved.
Not applicable
Providing to the CBC acknowledgement of successful execution/forwarding of commands received from the CBC.
Reporting to the CBC failure when a command received from the CBC is not understood or cannot be executed.
Not applicable.
Not applicable.
Report the Broadcast Completed Area List, the Broadcast Cancelled Area List, PWS Restart Indication and the PWS Failure Indication received from eNB(s) to all CBCs that the MME interfaces with.
Report the Broadcast Completed Area List, the Broadcast Cancelled Area List, PWS Restart Indication and the PWS Failure Indication received from NG-RAN nodes to all CBCFs and PWS-IWFs that the AMF interfaces with.
Routing of CBS messages to the appropriate BTSs.
Routing of CBS messages to the appropriate Node Bs.
Routing of warning messages to the appropriate eNodeBs in the indicated Tracking Area.
Routing of warning messages to the appropriate NG-RAN nodes in the indicated Tracking Area.
Transferring CBS information to each appropriate BTS via a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message (see 3GPP TS 48.058 [11]), indicating the channel which shall be used.
The Node B has no functionality regarding CBS. This implies that CBS messages do not have to be transmitted explicitly to the Node Bs for further processing.
Not applicable.
Not applicable.
Optionally generating Schedule Messages, indicating the intended schedule of transmissions (see 3GPP TS 44.012 [7]).
Generating Schedule Messages, indicating the intended schedule of transmissions (see 3GPP TS 25.324 [19]). The conversion of GSM related CB DRX Information is a function of the RNC (3GPP TS 25.401 [17]).
Not applicable.
Not applicable.
Optionally receiving CBCH Load Indication messages and reacting by broadcasting a burst of scheduled CBS messages or by suspending the broadcast for a period indicated by BTS (see 3GPP TS 48.058 [11]).
Not applicable.
Not applicable.
Not applicable.
Broadcasting the ETWS Primary Notification message upon receipt of the WRITE-REPLACE message including the Paging-ETWS-Indicator. The ETWS Primary Notification message is broadcasted according to the Warning Period parameter.
Sending ETWS messages to mobile terminals upon receiving CBS transmission request from CBC including the Paging-ETWS-Indicator. Emergency indication can be included in the paging messages, based on the warning type information conveyed from CBC.
Sending the Write-Replace Warning Request message to the appropriate eNodeBs upon receiving warning message transmission request from CBC.
Sending the Write-Replace Warning Request message to the appropriate NG-RAN nodes upon receiving warning message transmission request from CBCF or PWS-IWFs.
To work efficiently on the interfaces, the BSC/RNC should forward CB related messages to the CBC using cell lists as far as applicable.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 7 BTS Functionality
| Only GSM [The BTS is responsible for conveying CBS information received via SMS BROADCAST REQUEST or SMS BROADCAST COMMAND messages over the radio path to the MS.
- optionally generating CBCH Load Indication messages, indicating an underflow or overflow situation on the CBCH (see 3GPP TS 48.058 [11]).]
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 8 MS/UE Functionality
| |
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 8.1 General MS/UE Functionality
| Only GSM [The MS is responsible for recombination of the blocks received via the radio path to reconstitute the CBS message.]
The precise method of display of CBS messages is outside the scope of 3GPP specifications, however it is assumed that an MS/UE will:
MS
UE
Discard sequences transferred via the radio path (see 3GPP TS 44.012 [7]) which do not consist of consecutive blocks.
Discard corrupt CBS messages received on the radio interface.
Have the ability to discard CBS information which is not in a suitable data coding scheme.
Have the ability to discard a CBS message which has a message identifier indicating that it is of subject matter which is not of interest to the MS/UE.
Have the ability to detect duplicate messages as specified in clause 8.2;
Have the ability to transfer a CBS message to an external device, when supported ;
Optionally enter CBS DRX mode based upon received Schedule Messages (see 3GPP TS 44.012 [7]);
Enter CBS DRX mode based upon received Schedule Messages (see 3GPP TS 25.324 [19]).
Optionally skip reception of the remaining block(s) of a CBS message which do(es) not contain cell broadcast information (see 3GPP TS 44.012 [7]);
Not applicable.
Optionally read the extended channel.
Not applicable for UMTS, E-UTRAN, and NG-RAN.
Enable the user to activate/deactivate CBS through MMI
Enable the user to maintain a "search list" and receive CBS messages with a Message Identifier in the list while discarding CBS messages with a Message Identifier not in the list.
Discard CBS messages in Message Identifier value range "A000hex-AFFFhex" unless received from HPLMN, EHPLMN, PLMN that is equivalent to HPLMN or EHPLMN, the subscribed SNPN, or an SNPN equivalent to the subscribed SNPN.
Allow the user to enter the Message Identifier via MMI only for the 1 000 lowest codes.
Be capable of receiving CBS messages consisting of up to 15 pages.
Be capable of receiving CBS messages consisting of up to 1230 octets in UTRAN or warning messages of up to 9600 octets in E-UTRAN, or NG-RAN.
When emergency indication is included in the received paging and/or CBS/warning message, behave as specified in 3GPP TS 22.268 [28].
If the emergency indication includes the value for "test", mobile terminals which are not used for testing purpose silently discard the paging message and do not receive the corresponding CBS/warning message.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 8.2 Duplication Detection Function
| The MS/UE uses a common duplication detection function for all messages received in GSM, UMTS, E-UTRAN, satellite E-UTRAN, NG-RAN and satellite NG-RAN.
In a PLMN or SNPN, upon reception of a new message, the MS/UE shall perform duplication detection on the messages. Those messages that are received from the same PLMN or SNPN, in the certain time period specified by the duplication detection time are subject to duplication detection. The MS/UE shall not perform duplication detection on messages whose duplication detection time has elapsed. The value of the duplication detection time to be used by the MS/UE shall be derived from the MCC of the current PLMN or SNPN as follows:
- If the message was received from a PLMN and
- the MCC of the PLMN = 440 or = 441 (Japan); or
- the MCC of the PLMN = 9xx (shared MCC) and the UE has determined that the country of UE location is Japan
NOTE 0: How the UE determines that the country of the UE location is Japan in this case is up to the UE implementation.
duplication detection time shall be 1 hour; and
- For all other cases, duplication detection time shall be 24 hours.
If the messages are received from the same PLMN or SNPN, then:
1) the MS/UE shall check whether the Serial Number associated with the Message Identifier of the new message matches the Serial Number of any of those messages with the same Message Identifier that have been received and displayed to the user and that are subject to the duplication detection; and
2) the MS/UE may check other criteria for detecting duplicates. An example of such a criterion is whether the actual contents of the two messages are the same.
NOTE 1: Criterion 2 allows the UE to present more than 1024 different messages received within the duplication detection time period and will prevent those messages with the same Serial Number but with different message content to be rejected as duplicates.
If criterion 1 is fulfilled and any implemented additional checks (as described in criterion 2) are also met, then the MS/UE shall consider the new message as duplicated and shall ignore it. If the Geographical Scope is not PLMN/SNPN wide the validity of the Serial Number may be considered as described in clause 9.4.1.2.1.
If the messages are received from different PLMNs or SNPNs, then (as described in clause 9.4.1.2.1) "the CBS message is only relevant to the PLMN or SNPN in which it is broadcast, so any change of PLMN (including a change to another PLMN which is an ePLMN) or SNPN means the CBS message is "new"". Therefore, the MS/UE is not required to conduct duplication detection on messages received from different PLMNs/SNPNs.
NOTE 2: A duplicate message can only be received once by the user in a PLMN/SNPN during a duplication detection time. When the UE is in a different PLMN /SNPN then receiving a duplicate message once by the user, that was received earlier in a different PLMN/SNPN, can be tolerated.
For ETWS, duplicate message detection shall be performed independently for primary and secondary notifications.
8.3 ePWS functionality
The ePWS functionality consists of the ePWS language-independent content functionality and the ePWS disaster characteristics functionality as follows:
1) UEs with user interface which support the ePWS language-independent content functionality and which are capable of displaying text-based warning messages should be capable of displaying the language-independent content mapped to an event or a disaster (e.g. character such as Unicode based pictogram mapping to a disaster) that is part of user information contained in the content of a warning message transparently passed from CBC to UEs.
NOTE 1: Language-independent contents mapped to disasters need to be formatted to be suitable to be included in a warning message. It could be unicode symbol or symbol based on GSM 7 bit default alphabet. It is desirable that standardised symbols mapped to disasters are applied in all countries that provide warning messages for public safety. This will make it possible for foreigners to intuitively understand the meaning of language-independent contents displayed to their devices.
Editor's note [WI: ePWS, CR#202]: FFS on what character(s) such as Unicode based pictogram(s) are the language-independent content mapped to an event or a disaster.
2) UEs with user interface which support the ePWS language-independent content functionality and which are incapable of displaying text-based warning messages should be capable of mapping message identifiers of received warning messages to language-independent contents stored in those UEs. When a warning message is received, such a UE should be capable of displaying of a language-independent content stored in the UE mapped from the message identifier of the received warning message.
NOTE 2: This ePWS functionality is not applied for such UEs if they are not capable of storing any language-independent content.
3) UEs with no user interface which support the ePWS disaster characteristics functionality should be capable of identifying the characteristics of a disaster derived from the message identifier of a received warning message in order to take appropriate action.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9 Protocols and Protocol Architecture
| |
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1 Requirements on Core Network and Radio Access Network
| |
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.1 GSM Radio Access Network
| Commands interpreted by the BSC will result in a sequence of 4 SMS BROADCAST REQUEST messages or 1 SMS BROADCAST COMMAND message being sent to a BTS, which in turn result in a sequence of 4 blocks each 22 octets long being transferred via the BTS-MS interface (see 3GPP TS 44.012 [7]).
With the SMS BROADCAST REQUEST mode of operation, the 88 octet fixed length CBS page which is specified in clause 9.3 is split into four 22 octet blocks which are carried in SMS BROADCAST REQUEST messages as follows:
octets 1‑22 are transferred in the 1st SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating first block;
octets 23‑44 are transferred in the 2nd SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating second block;
octets 45‑66 are transferred in the 3rd SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating third block;
octets 67‑88 are transferred in the 4th SMS BROADCAST REQUEST
with a sequence number (see 3GPP TS 44.012 [7]) indicating fourth block.
Figure 3 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST REQUEST mode of operation.
Figure 3
With the SMS BROADCAST COMMAND mode of operation, the BSC sends to the BTS in one single message the 88 octet fixed length CBS page. The BTS then splits the page into four 22 octet blocks, adds the sequence number (see 3GPP TS 44.012 [7]) and transmits the four resulting blocks on the air.
Figure 4 illustrates the protocol architecture and the scope of the various GSM Specifications for the SMS BROADCAST COMMAND mode of operation.
Figure 4
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.2 UMTS Radio Access Network
| Commands interpreted by the RNC will result in one SMS BROADCAST COMMAND sent to the UE. The CBS messages are completely transparent to the Node B, i.e. no manipulation of the data like e.g. fragmentation is done at the Node B.
Figure 4a
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.3 Warning Message Delivery
| |
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.3.4 Warning Message Delivery Procedure in E-UTRAN
| |
e2219d60c1c9a192756e2fe7890303a5 | 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.
For ETWS, if primary notification and secondary notification are indicated in the same Write-Replace Warning Request message (i.e. both "warning type" and "warning message" are included in the Write-Replace Warning Request), then the primary and secondary notification have the same Message Identifier and Serial Number.
|
e2219d60c1c9a192756e2fe7890303a5 | 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" and proceeds as follows:
a) If the Warning Area Coordinates are not present:
The UE indicates the contents of the "warning message" to the user;
b) 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;
c) 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: and
d) 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 ETWS secondary notification, 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 Serial Number and Message Identifier combination of the ETWS secondary notification and if the Serial Number and Message Identifier combination of the stored "warning message" matches the Serial Number and Message Identifier combination of the ETWS secondary notification, the UE shall remove the "warning message" from the list of "warning messages" to be checked for geo-fencing.
NOTE 4A: For case d) above, the UE performs the removal of the matching message before storing the new message.
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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.3.4.4 Abnormal cases in the UE
| For ETWS, if the UE receives a primary notification and a secondary notification in reverse order (i.e. a secondary notification is received before a primary notification that carries the same Message Identifier and Serial Number), the UE shall discard the primary notification and shall not display it.
NOTE: How the UE detects that the primary notification and the secondary notification are received in reverse order is up to the UE implementation.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.3.5 Warning Message Delivery Procedure in NG-RAN
| |
e2219d60c1c9a192756e2fe7890303a5 | 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.
For ETWS, if primary notification and secondary notification are indicated in the same Write-Replace Warning Request message (i.e. both "warning type" and "warning message" are included in the Write-Replace Warning Request), then the primary and secondary notification have the same Message Identifier and Serial Number.
|
e2219d60c1c9a192756e2fe7890303a5 | 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 MWAB-gNB of an MWAB additionally checks for any match of the contents of the Warning Area List NG-RAN with the cell ID or the TAI of the Additional ULI, to identify whether to distribute the warning message. The IAB-donor of an MBSR additionally checks for any match of the contents of the Warning Area List NG-RAN with the cell ID or the TAI of the Additional ULI for the MBSR, to identify whether to distribute the warning message via the gNB-DU of the MBSR.
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. If the list of NG-RAN TAIs is included, the MWAB-gNB of an MWAB is connected to the AMF, and the TAI of the Additional ULI of the MWAB-gNB is in the list of NG-RAN TAIs, then the AMF shall additionally forward the message to the MWAB-gNB. If the list of NG-RAN TAIs is included, the IAB-donor of an MBSR is connected to the AMF, and the TAI of the Additional ULI of the IAB-donor for the MBSR is in the list of NG-RAN TAIs, then the AMF shall additionally forward the message to the IAB-donor of the MBSR.
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" and proceeds as follows:
a) If the Warning Area Coordinates are not present:
The UE indicates the contents of the "warning message" to the user.
b) 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.
c) 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.
d) 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 ETWS secondary notification, 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 Serial Number and Message Identifier combination of the ETWS secondary notification and if the Serial Number and Message Identifier combination of the stored "warning message" matches the Serial Number and Message Identifier combination of the ETWS secondary notification, the UE shall remove the "warning message" from the list of "warning messages" to be checked for geo-fencing.
NOTE 3A: For case d) above, the UE performs the removal of the matching message before storing the new message.
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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.3.5.4 Abnormal cases in the UE
| For ETWS, if the UE receives a primary notification and a secondary notification in reverse order (i.e. a secondary notification is received before a primary notification that carries the same Message Identifier and Serial Number), the UE shall discard the primary notification and shall not display it.
NOTE: How the UE detects that the primary notification and the secondary notification are received in reverse order is up to the UE implementation.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.1.4 UMTS Protocol Overview
|
Figure 5
|
e2219d60c1c9a192756e2fe7890303a5 | 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
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.2 Requirements on the CBC-RAN, CBC-MME and CBCF-AMF interfaces
| |
e2219d60c1c9a192756e2fe7890303a5 | 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".
|
e2219d60c1c9a192756e2fe7890303a5 | 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".
|
e2219d60c1c9a192756e2fe7890303a5 | 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].
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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).
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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).
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 23.041 | 9.2.15 Void
| |
e2219d60c1c9a192756e2fe7890303a5 | 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]).
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
e2219d60c1c9a192756e2fe7890303a5 | 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]).
|
e2219d60c1c9a192756e2fe7890303a5 | 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).
|
e2219d60c1c9a192756e2fe7890303a5 | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.