hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.2 Barring of Incoming Calls or Mobile Terminated Short Messages | |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.2.1 Application or Change of Barring in the HLR | If barring of incoming calls or mobile terminated short messages is applied to a subscription (or existing barring of incoming calls or mobile terminated short messages is modified or removed) by administrative action in the HLR, the HLR will update the subscription information accordingly. It is not necessary to trans... |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.2.2 Invocation of Barring | Barring of incoming calls is invoked in the HLR. If the HLR receives a request for routing information for a call directed to a mobile station which is subject to barring of incoming calls, the HLR will return a negative response to the request for routing information, with an appropriate error indication. The Gateway ... |
c5195074c429803154bc8b9cf2be11b9 | 23.015 | 2.3 Barring of Roaming | |
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 ... |
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 indicatio... |
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 th... |
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 unstructu... |
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 op... |
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 ... |
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 ... |
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 informati... |
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 fl... |
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 t... |
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... |
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... |
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 subscr... |
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 Deter... |
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... |
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 ... |
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 exist... |
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] ... |
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 interna... |
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 interna... |
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 o... |
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... |
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... |
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.
... |
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 in... |
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;... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 speci... |
a3b117234c7e2cb4e7f7e3871635bcca | 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.
-... |
a3b117234c7e2cb4e7f7e3871635bcca | 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
... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 3 Network Architecture
| |
a3b117234c7e2cb4e7f7e3871635bcca | 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.
|
a3b117234c7e2cb4e7f7e3871635bcca | 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 3G... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 t... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 ser... |
a3b117234c7e2cb4e7f7e3871635bcca | 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.
|
a3b117234c7e2cb4e7f7e3871635bcca | 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 t... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 ma... |
a3b117234c7e2cb4e7f7e3871635bcca | 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]).]
|
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 8 MS/UE Functionality
| |
a3b117234c7e2cb4e7f7e3871635bcca | 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 (s... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9 Protocols and Protocol Architecture
| |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.1 Requirements on Core Network and Radio Access Network
| |
a3b117234c7e2cb4e7f7e3871635bcca | 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 mo... |
a3b117234c7e2cb4e7f7e3871635bcca | 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
|
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.1.3 Warning Message Delivery
| |
a3b117234c7e2cb4e7f7e3871635bcca | 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 t... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 m... |
a3b117234c7e2cb4e7f7e3871635bcca | 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.1.3.4 Warning Message Delivery Procedure in E-UTRAN
| |
a3b117234c7e2cb4e7f7e3871635bcca | 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.... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 delive... |
a3b117234c7e2cb4e7f7e3871635bcca | 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.1.3.5 Warning Message Delivery Procedure in NG-RAN
| |
a3b117234c7e2cb4e7f7e3871635bcca | 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 mess... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.1.4 UMTS Protocol Overview
|
Figure 5
|
a3b117234c7e2cb4e7f7e3871635bcca | 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 s... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.1.6 NG-RAN Protocol Overview
|
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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2 Requirements on the CBC-RAN, CBC-MME and CBCF-AMF interfaces
| |
a3b117234c7e2cb4e7f7e3871635bcca | 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 interc... |
a3b117234c7e2cb4e7f7e3871635bcca | 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 m... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.2 WRITE-REPLACE Request/Indication
| The WRITE-REPLACE Request/Indication primitive is specified in table 9.2.2-1.
Table 9.2.2-1: 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.3 KILL Request/Indication
| The KILL Request/Indication primitive is specified in table 9.2.3-1.
Table 9.2.3-1: 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.4 REPORT Response/Confirm
| The REPORT Response/Confirm primitive is specified in table 9.2.4-1.
Table 9.2.4-1: 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 p... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.5 STATUS-LOAD-QUERY Request/Indication
| The STATUS-LOAD-QUERY Request/Indication primitive is specified in table 9.2.5-1.
Table 9.2.5-1: 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.6 STATUS-LOAD-QUERY Response/Confirm
| The STATUS-LOAD-QUERY Response/Confirm primitive is specified in table 9.2.6-1.
Table 9.2.6-1: 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 res... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.7 STATUS-MESSAGE-QUERY Request/Indication
| The STATUS-MESSAGE-QUERY Request/Indication primitive is specified in table 9.2.7-1.
Table 9.2.7-1: 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.8 STATUS-MESSAGE-QUERY Response/Confirm
| The STATUS-MESSAGE-QUERY Response/Confirm primitive is specified in table 9.2.8-1.
Table 9.2.8-1: 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 Indi... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.9 REJECT Response/Confirm
| The REJECT Response/Confirm primitive is specified in table 9.2.9-1.
Table 9.2.9-1: 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 wh... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.10 RESTART-INDICATION Request/Indication
| The RESTART-INDICATION Request/Indication primitive is specified in table 9.2.10-1.
Table 9.2.10-1: 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.11 RESET Request/Indication
| The RESTART-INDICATION Request/Indication primitive is specified in table 9.2.10-1.
Table 9.2.10-1: RESTART-INDICATION 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 a... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.12 FAILURE-INDICATION Request/Indication
| The FAILURE-INDICATION Request/Indication primitive is specified in table 9.2.12-1.
Table 9.2.12-1: 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.13 SET-DRX Request/Indication
| The SET-DRX Request/Indication primitive is specified in table 9.2.13-1.
Table 9.2.13-1: 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 ... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.14 SET-DRX- REPORT Response/Confirm
| The SET-DRX-REPORT Response/Confirm primitive is specified in table 9.2.14-1.
Table 9.2.14-1: 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.15 Void
| |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.16 WRITE-REPLACE-WARNING-REQUEST Request/Indication
| The WRITE-REPLACE-WARNING-REQUEST Request/Indication primitive is specified in table 9.2.16-1.
Table 9.2.16-1: 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-Br... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.17 WRITE-REPLACE-WARNING-CONFIRM Response/Confirm
| The WRITE-REPLACE-WARNING-CONFIRM Response/Confirm primitive is specified in table 9.2.17-1.
Table 9.2.17-1: 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
... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.18 STOP-WARNING-REQUEST Request/Indication
| The STOP-WARNING-REQUEST Request/Indication primitive is specified in table 9.2.18-1.
Table 9.2.18-1: 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... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.19 STOP-WARNING-CONFIRM Response/Confirm
| The STOP-WARNING-CONFIRM Response/Confirm primitive is specified in table 9.2.19-1.
Table 9.2.19-1: 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
Unknow... |
a3b117234c7e2cb4e7f7e3871635bcca | 23.041 | 9.2.20 WRITE-REPLACE-WARNING-INDICATION Request/Indication
| The WRITE-REPLACE-WARNING-INDICATION Request/Indication primitive is specified in table 9.2.20-1.
Table 9.2.20-1: 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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.