Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
2,001 | 4.2.2.6 Number of released active E-RABs | a) This measurement provides the number of released E-RABs that were active at the time of release. E-RABs with bursty flow are seen as being active when there is user data in the queue in any of the directions. E-RABs with continuous flow are always seen as active E-RABs in the context of this measurement. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On transmission by the eNodeB/RN of an E-RAB RELEASE INDICATION message; or on transmission by the eNB/RN of an E-RAB RELEASE RESPONSE message for the E-RAB release initiated by the MME/DeNB with the exception of corresponding E-RAB RELEASE COMMAND message with “Cause” equal to “Normal Release” or on transmission by the eNodeB/RN of UE CONTEXT RELEASE COMPLETE for the UE context release initiated by the eNB/RN with the exception of the corresponding UE CONTEXT RELEASE REQUEST message with cause “User inactivity”, “CSG Subscription Expiry”, or any “cause” indicating a successful CS fallback (e.g., cause “CS Fallback triggered”, “UE Not Available for PS Service”, or “Redirection towards 1xRTT”) or a succesful mobility activity (e.g., cause “Inter-RAT Redirection”); or on transmission by the eNodeB/RN of UE CONTEXT RELEASE COMPLETE message for the UE context release initiated by the MME/DeNB with the exception of the corresponding UE CONTEXT RELEASE COMMAND message with "Cause" equal to “Normal Release” ", “detach”, “Handover Cancelled” or any “cause” indicating a successful CS fallback (e.g., cause “Redirection towards 1xRTT”) or a succesful mobility activity (e.g., cause “Successful Handover”, “Inter-RAT Redirection” or “S1 Intra system Handover triggered”) or on receipt by the eNB of a PATH SWITCH REQUEST ACKNOWLEDGE or PATH SWITCH REQUEST FAILED message by which some or all E-RABs in the corresponding PATH SWITCH REQUEST need to be released , or on transmission of a RESET ACKNOWLEDGE message to MME/DeNB; or on receipt of a RESET ACKNOWLEDGE message from MME/DeNB, if any of the UL or DL are considered active according to the definition used for "Number of active UEs" in TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] . E-RABs with bursty flow are considered active when there is still data in the DL or UL buffer. E-RABs with continuous flow are always seen as active E-RABs in the context of this measurement.Each corresponding E-RAB to release is added to the relevant measurement per QCI. The possible QCIs are described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs attempted to release when the E-RAB is active according to the definition of bursty flow/continuous flow. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. How to define for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of this document. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.RelActNbr.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) This measurement is to support the Retainability KPI “E-RAB Retainability” defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.2.6 |
2,002 | 6.2.5.1.4.2 Derivation of packet filter for UL direction from DL user data packet | If the UE needs to derive a packet filter for UL direction from the DL user data packet (see subclause 6.2.5.1.4.3 and 6.2.5.1.4.4), the UE shall proceed as follows: a) if the received DL user data packet belongs to a PDU session of IPv4 or IPv4v6 PDU session type and is an IPv4 packet and: 1) the protocol field of the received DL user data packet indicates TCP as specified in IETF RFC 793 [33]; 2) the protocol field of the received DL user data packet indicates UDP as specified in IETF RFC 768 [32]; or 3) the protocol field of the received DL user data packet indicates ESP as specified in IETF RFC 4303 [38] and an uplink IPSec SA corresponding to a downlink IPSec SA indicated in the security parameters index field of the received DL user data packet exists; then the packet filter for UL direction contains the following packet filter components: 1) an IPv4 remote address component set to the value of the source address field of the received DL user data packet; 2) an IPv4 local address component set to the value of the destination address field of the received DL user data packet; 3) a protocol identifier/next header type component set to the value of the protocol field of the received DL user data packet; 4) if the protocol field of the received DL user data packet indicates TCP as specified in IETF RFC 793 [33] or UDP as specified in IETF RFC 768 [32]: i) a single local port type component set to the value of the destination port field of the received DL user data packet; and ii) a single remote port type component set to the value of the source port field of the received DL user data packet; 5) if the protocol field of the received DL user data packet indicates ESP as specified in IETF RFC 4303 [38], an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL user data packet exists and the SPI of the uplink IPSec SA is known to the NAS layer: i) a security parameter index type component set to the security parameters index of the uplink IPSec SA corresponding to the downlink IPSec SA indicated in the security parameters index field of the received DL user data packet; and 6) if the protocol field of the received DL user data packet indicates UDP and the received DL user data packet contains a UDP-encapsulated ESP header as specified in IETF RFC 3948 [55], an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL user data packet exists and the SPI of the uplink IPSec SA is known to the NAS layer: i) a security parameter index type component set to the security parameters index of the uplink IPSec SA corresponding to the downlink IPSec SA indicated in the security parameters index field of the ESP header field of the UDP-encapsulated ESP header as specified in IETF RFC 3948 [55] of the received DL user data packet; otherwise it is not possible to derive a packet filter for UL direction from the DL user data packet; b) if the received DL user data packet belongs to a PDU session of IPv6 or IPv4v6 PDU session type and is an IPv6 packet and: 1) the last next header field of the received DL user data packet indicates TCP as specified in IETF RFC 793 [33]; 2) the last next header field of the received DL user data packet indicates UDP as specified in IETF RFC 768 [32]; or 3) the last next header field of the received DL user data packet indicates ESP as specified in IETF RFC 4303 [38] and an uplink IPSec SA corresponding to a downlink IPSec SA indicated in the security parameters index field of the received DL user data packet exists; then the packet filter for UL direction contains the following packet filter components: 1) an IPv6 remote address/prefix length component set to the value of the source address field of the received DL user data packet; 2) an IPv6 local address/prefix length component set to the value of the destination address field of the received DL user data packet; 3) a protocol identifier/next header type component set to the value of the last next header field of the received DL user data packet; 4) if the last next header field of the received DL user data packet indicates TCP as specified in IETF RFC 793 [33] or UDP as specified in IETF RFC 768 [32]: i) a single local port type component set to the value of the destination port field of the received DL user data packet; and ii) a single remote port type component set to the value of the source port field of the received DL user data packet; 5) if the last next header field of the received DL user data packet indicates ESP as specified in IETF RFC 4303 [38], an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL user data packet exists and the SPI of the uplink IPSec SA is known to the NAS layer: i) a security parameter index type component set to the security parameters index of the uplink IPSec SA corresponding to the downlink IPSec SA indicated in the security parameters index field of the received DL user data packet; and 6) if the last next header field of the received DL user data packet indicates UDP, and the received DL user data packet contains a UDP-encapsulated ESP header as specified in IETF RFC 3948 [55], an uplink IPSec SA corresponding to a downlink IPSec SA of the SPI in the DL user data packet exists and the SPI of the uplink IPSec SA is known to the NAS layer: i) a security parameter index type component set to the security parameters index of the uplink IPSec SA corresponding to the downlink IPSec SA indicated in the security parameters index field of the ESP header field of the UDP-encapsulated ESP header as specified in IETF RFC 3948 [55] of the received DL user data packet; otherwise it is not possible to derive a packet filter for UL direction from the DL user data packet; c) if the received DL user data packet belongs to a PDU session of Ethernet PDU session type, the packet filter for UL direction contains the following packet filter components: 1) a destination MAC address component set to the source MAC address of the received DL user data packet; 2) a source MAC address component set to the destination MAC address of the received DL user data packet; 3) if one or more 802.1Q C-TAG is included in the received DL user data packet, an 802.1Q C-TAG VID component set to the outermost 802.1Q C-TAG VID of the received DL user data packet and an 802.1Q C-TAG PCP/DEI component set to the outermost 802.1Q C-TAG PCP/DEI of the received DL user data packet; 4) if one or more 802.1Q S-TAG is included in the received DL user data packet, an 802.1Q S-TAG VID component set to the outermost 802.1Q S-TAG VID of the received DL user data packet and an 802.1Q S-TAG PCP/DEI component set to the outermost 802.1Q S-TAG PCP/DEI of the received DL user data packet; 5) If the Ethertype field of the received DL user data packet is set to a value of 1536 or above, an Ethertype component set to the Ethertype of the received DL user data packet; 6) if the Ethertype field of the Ethernet frame header indicates that the data carried in the Ethernet frame is IPv4 data, the UE shall also add to the packet filter for UL direction the IP-specific components based on the contents of the IP header of the received DL user data packet as described in bullet a) above; and 7) if the Ethertype field of the Ethernet frame header indicates that the data carried in the Ethernet frame is IPv6 data, the UE shall also add to the packet filter for UL direction the IP-specific components based on the contents of the IP header of the received DL user data packet as described in bullet b) above; and d) if the received DL user data packet belongs to a PDU session of PDU session type other than Ethernet, IPv4, IPv6 and IPv4v6, it is not possible to derive a packet filter for UL direction from the DL user data packet. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.5.1.4.2 |
2,003 | 6.3.1A Service-level authentication and authorization procedure 6.3.1A.1 General | The purpose of the service-level authentication and authorization (service-level-AA) procedure is to enable the DN using NEF services for authentication: a) to authenticate the upper layers of the UE, when establishing the PDU session; b) to authorize the upper layers of the UE, when establishing the PDU session; c) both of the above; or d) to re-authenticate the upper layers of the UE after establishment of the PDU session. The service-level authentication and authorization procedure is used for UUAA as specified in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]. NOTE 1: The authentication protocol for UUAA is out of scope of 3GPP in this release of specification. The service-level authentication and authorization procedure can be performed only during or after the UE-requested PDU session procedure establishing a non-emergency PDU session. The service-level authentication and authorization procedure shall not be performed during or after the UE-requested PDU session establishment procedure establishing an emergency PDU session. If the service-level authentication and authorization procedure is performed during the UE-requested PDU session establishment procedure: a) and the service-level-AA procedure of the UE completes successfully, the service-level-AA response is transported from the network to the UE as a part of the UE-requested PDU session establishment procedure in the PDU SESSION ESTABLISHMENT ACCEPT message; or b) and the service-level-AA procedure of the UE completes unsuccessfully, the service-level-AA response is transported from the network to the UE as a part of the UE-requested PDU session establishment procedure in the PDU SESSION ESTABLISHMENT REJECT message. NOTE 2: If the SMF receives the HTTP code set to "4xx" or "5xx" as specified in 3GPP TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [20AA] or the SMF detects a UUAA-SM failure as specified in 3GPP TS 29.256[ Uncrewed Aerial Systems Network Function (UAS-NF); Aerial Management Services; Stage 3 ] [21B], then the SMF considers that the UUAA-SM procedure has completed unsuccessfully. If the service-level authentication and authorization procedure is performed for the established PDU session with re-authentication purpose: a) and the service-level-AA procedure of the UE completes successfully, the service-level-AA response is transported from the network to the UE as a part of the network-requested PDU session modification procedure in the PDU SESSION MODIFICATION COMMAND message; or b) and the service-level-AA procedure of the UE completes unsuccessfully, the service-level-AA response is transported from the network to the UE as a part of the network-requested PDU session release procedure in the PDU SESSION RELEASE COMMAND message. There can be several rounds of exchange of a service-level-AA payload for the service to complete the service-level authentication and authorization of the request for a PDU session (see example in figure 6.3.1A.1-1). If the UE receives the service-level-AA response in the PDU SESSION ESTABLISHMENT ACCEPT message or the PDU SESSION ESTABLISHMENT REJECT message, the UE passes it to the upper layer. Figure 6.3.1A.1-1: Service-level authentication and authorization procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1A |
2,004 | 5.7.17 Derivation of pathloss reference for TA validation of SRS for Positioning transmission and CG-SDT in RRC_INACTIVE | Upon request from lower layer for pathloss reference derivation for TA validation for SRS for Positioning transmission or CG-SDT in RRC_INACTIVE, the UE shall: 1> acquire SIB2, if stored version is invalid; 1> if nrofSS-BlocksToAverage or absThreshSS-BlocksConsolidation is not present or if absThreshSS-BlocksConsolidation is present and the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation: 2> derive the downlink pathloss reference RSRP for TA validation as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215[ NR; Physical layer measurements ] [24]; 1> else: 2> derive the downlink pathloss reference RSRP for TA validation as the linear average of the power values of up to nrofSS-BlocksToAverage of the highest beam measurement quantity values above absThreshSS-BlocksConsolidation, where each beam measurement quantity is described in TS 38.215[ NR; Physical layer measurements ] [24]. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.17 |
2,005 | 8.17.2.1 IAB Inter-CU topological redundancy procedure | The inter-CU topological redundancy procedure enables the establishment, modification and release of redundant paths in IAB-topologies underneath different IAB-donor-CUs. Since topological redundancy uses NR-DC for the IAB-MT, it is only supported for IAB-nodes operating in the SA mode. Figure 8.17.2.1-1 shows an example of the inter-CU topological redundancy procedure, where a second backhaul path is established for a dual-connecting IAB-node via a separate IAB-topology that is not controlled by the F1-terminating IAB-donor-CU. The dual-connecting IAB-DU retains the F1 connection with the F1-terminating IAB-donor-CU. Since the dual-connecting IAB-MT also maintains an RRC connection with the non-F1-terminating IAB-donor-CU, this procedure renders the dual-connecting IAB-node as a boundary IAB-node. Figure 8.17.2.1-1 IAB inter-CU topology redundancy procedure 1. The NR-DC establishment procedure is performed for the IAB-MT of the dual-connecting IAB-node as described in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12], clause 10.2. This procedure can be conducted before or after establishment of the F1 interface between the IAB-DU and an IAB-donor-CU. 2. The F1-terminating IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the non-F1-terminating IAB-donor-CU to provide the context of the traffic to be offloaded. 3. The non-F1-terminating IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the second parent IAB-DU, which includes an RRCReconfiguration message for the dual-connecting IAB-MT. The RRC configuration includes a BAP address for the boundary node, pertaining to the non-F1-terminating IAB-donor-CU’s topology. The RRC configuration may include new TNL address(es) for the dual-connecting IAB-node, anchored at the second-path, i.e., at the IAB-donor-DU under the non-F1-terminating IAB-donor-CU. In case IPsec tunnel mode is used to protect the F1 and non-F1 traffic, the new TNL address refers to the outer IP address. 4. The second parent IAB-DU forwards the received RRCReconfiguration message to the dual-connecting IAB-MT. 5. The dual-connecting IAB-MT responds to the second parent IAB-DU with an RRCReconfigurationComplete message. 6. The second parent IAB-DU sends an UL RRC MESSAGE TRANSFER message to the non-F1-terminating IAB-donor-CU, to convey the received RRCReconfigurationComplete message. 7. The non-F1-terminating IAB-donor-CU may configure or modify BH RLC channels and BAP-sublayer routing entries on the second path between the dual-connecting IAB-node and the second-path IAB-donor-DU, as well as DL mappings on the second-path IAB-donor-DU for the dual-connecting IAB-node’s second path. The DL mappings may be based on the TNL address(es) allocated to the dual-connecting IAB-node in step 3. These configurations may support the transport of UP and non-UP traffic on the second path. 8. The non-F1-terminating IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the F1-terminating IAB-donor-CU, to provide the mapping information for the traffic to be offloaded as indicated in step 2. The message includes the L2 info necessary to configure the dual-connecting IAB-node with the UL mappings for this traffic. The message includes the DSCP/IPv6 Flow Label values to be used for the DL traffic to be offloaded. 9. The F1-terminating IAB-donor-CU updates the boundary node with the UL BH information received from the non-F1-terminating IAB-donor-CU in Step 8 for the traffic to be offloaded. This step may also update UL FTEID and DL FTEID associated with individual GTP-tunnel(s). The affected GTP tunnel(s) will be switched to use the dual-connecting IAB-node’s new TNL address(es). This step may use non-UE associated signaling in E1 and/or F1 interface to provide updated UP configuration for F1-U tunnels of multiple connected UEs or child IAB-MTs. Implementation must ensure the avoidance of potential race conditions, i.e., that no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. The F1-terminating IAB-donor-CU may also provide UL BH information associated with non-UP traffic. New TNL addresses for F1-C traffic configured in step 3, if any, can be added to the dual-connecting IAB-DU’s F1-C association(s) with the F1-terminating IAB-donor-CU. If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the dual-connecting IAB-node and the F1-terminating IAB-donor-CU may be established using the new TNL address information of the dual-connecting IAB-node. The dual-connecting IAB-node sends an F1AP gNB-DU CONFIGURATION UPDATE message to the F1-terminating IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for offloaded F1-U traffic. NOTE: The IP address selected by the boundary IAB-node for a traffic needs to be anchored at the IAB-donor-DU whose BAP address is contained in the BAP routing ID of the UL mapping for this traffic, and configured by the IAB-donor (MN/SN) of the egress topology of the traffic. 10. The F1-terminating IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the non-F1-terminating IAB-donor-CU, to modify the context of the dual-connecting IAB-node’s offloaded traffic. The message may include the DL TNL address information used for the offloaded traffic and reported by the boundary node in step 9. The non-F1-terminating IAB-donor-CU may use this information to configure DL mappings on the second-path IAB-donor-DU. 11. The non-F1-terminating IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the F1-terminating IAB-donor-CU. 12. The steps above, may be repeated, except step 1, if needed, for the F1-terminating IAB-donor-CU to request addition, modification, or release of the offloaded traffic. The non-F1-terminating IAB-donor-CU can fully or partially reject the addition or modification requested by the F1-terminating IAB-donor-CU. The non-F1-terminating IAB-donor-CU may request the modification of the L2 transport for the offloaded traffic in the non-F1-terminating IAB-donor-CU’s topology using the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. The F1-terminating IAB-donor-CU reconfigures UL BH mappings accordingly and acknowledges the modification via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. The non-F1-terminating IAB-donor-CU may further reconfigure the TNL addresses of the dual-connecting IAB-node via RRC. The traffic offload for descendant nodes follows the same procedure as defined for the partial migration in clause 8.17.3.2. The F1-terminating IAB-donor-CU may request full or partial release of the offloaded traffic from the non-F1-terminating IAB-donor-CU by initiating the IAB Transport Migration Management procedure towards the non-F1-terminating IAB-donor-CU (e.g., for the purpose of revoking, or in case UE bearers are released). The traffic offload for the dual-connecting IAB-node and the descendent nodes can be partially or fully revoked, resulting in the return of the offloaded traffic back to the F1-terminating IAB-donor-CU’s topology. Full or partial traffic revoking can be initiated by the F1-terminating IAB-donor-CU by initiating the IAB Transport Migration Management procedure towards the non-F1-terminating IAB-donor-CU. The non-F1-terminating IAB-donor-CU can request partial or full revoking of traffic offload from the F1-terminating IAB-donor-CU by initiating the IAB Transport Migration Modification procedure towards the F1-terminating IAB-donor-CU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.17.2.1 |
2,006 | 4.16.1.1 Number of Secondary Node Additions without SN terminated bearers | a) This measurement provides the number of Secondary Node Addition attempts without SN terminated bearers. b) CC c) On transmission by the MN of an SgNB Addition Request message to SN, the request not include SN terminated bearers. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ENDC.SNAdditionAttWoSnErab. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.16.1.1 |
2,007 | 16.14.3.2.1 Handover | The same principle as described in 9.2.3.2 applies unless hereunder specified: During mobility between NTN and Terrestrial Network (TN), a UE is not required to connect to both NTN and TN at the same time. NOTE: NTN TN handover refers to mobility in both directions, i.e. from NTN to TN (hand-in) and from TN to NTN (hand-out). DAPS handover is not supported for NTN in this release of the specification. UE may support mobility between gNBs operating with NTN payloads in different orbits (e.g., GSO, NGSO at different altitudes). RACH-less handover as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6] is supported in NTNs. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.3.2.1 |
2,008 | 12.1.1 GTP-C overload problem | GTP-C entities can communicate with other GTP-C peers in direct contact (e.g. MME and SGW) or remote GTP-C peers through intermediate GTP-C entities (e.g. MME and PGW via the SGW). In normal conditions, requests sent by a GTP-C entity can be processed by the receiving GTP-C entity which can send back a message indicating the result of the request (success/failure). Overload situations in a GTP-C entity occur when the number of incoming requests exceeds the maximum request throughput supported by the receiving GTP-C entity, e.g. when the internal available resources of the GTP-C entity, such as processing power or memory, are not sufficient to serve the number of incoming requests. As a consequence of the overload situation, the receiving GTP-C entity cannot successfully process the exceeding proportion of requests. These requests can be either simply dropped or extremely delayed in the processing. At best, the GTP-C entity may have enough internal resources to send back to the request initiator a message indicating that the requests cannot be successfully processed. Whatever the behaviour of the overloaded GTP-C entities, the rate of successfully processed requests and consequently the overall performances of the network decrease. NOTE: GTP-C overload control does not target to address transport network congestion. It assumes a transport network that is still capable to exchange signalling traffic. Given the nature of GTP-C protocol in how it relies on retransmissions of unacknowledged requests (GTP-C is carried over UDP transport), when a GTP-C entity experiences overload (or severe overload) the number of unacknowledged GTP-C messages compounds exponentially and can lead to a node congestion or even collapse. An overload or failure of a node can lead to an increase of the load on the other nodes in the network and, in the worst case, turn into a complete network issue via a snowball effect. The impact of GTP-C overload to services can be such as: - loss of PDN connectivity (IMS, Internet …) and associated services; - loss of ability to setup and release radio and core network bearers necessary to support services e.g. GBR bearers for VoLTE or dedicated bearers for Voice over WLAN; - loss of ability to report to the PGW/PCRF user's information changes, e.g. location information for emergency services and lawful intercept, changes in RAT or QoS; - and billing errors and a loss of revenue. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.1.1 |
2,009 | 6.1.4.2 Guidance on linking authentication confirmation to Nudm_UECM_Registration procedure from AMF | This sub-clause gives informative guidance on how a home operator could link authentication confirmation (or the lack thereof) to subsequent Nudm_UECM_Registration procedures from AMF to achieve protection against certain types of fraud, as mentioned in the preceding sub-clause. Approach 1: The home network records the time of the most recent successfully verified authentication confirmation of the subscriber together with the identity of the 5G visited network that was involved in the authentication. When a new Nudm_UECM_Registration Request arrives from a visited network, the home network checks whether there is a sufficiently recent authentication of the subscriber by this visited network. If not, the Nudm_UECM_Registration Request is rejected. The rejection message may include, according to the home networks policy, an indication that the visited network should send a new Nausf_UEAuthentication_Authenticate Request (cf. sub-clause 6.1.2 of the present document) for fetching a new authentication vector before repeating the Nudm_UECM_Registration Request. NOTE 1: With this approach, the authentication procedure and the Nudm_UECM_Registration procedure are performed independently. They are coupled only through linking information in the home network. NOTE 2: It is up to the home network to set the time threshold to define what 'sufficiently recent' is. Approach 2: As a variant of the above Approach 1, Approach 2 is based on a more fine-grained policy applied by the home network; the home network could classify roaming partners into different categories, depending on the trust - e.g. derived from previous experience placed in them, for example as follows: - For a visited network in the first category, the home network would require a successful authentication 'immediately preceding' the Nudm_UECM_Registration Request from an AMF. - For a visited network in the second category, the home network would only check that an authentication in a network visited by the subscriber was sufficiently recent (taking into account that there may have been a security context transfer between the visited networks). - For a visited network in the third category, the home network would perform no checks regarding Nudm_UECM_Registration Requests and authentication at all. Further approaches are possible, depending on the home operator's policy. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.4.2 |
2,010 | B.2 Protocol errors (e.g., unknown message) class | Cause #95 – Semantically incorrect message This ESM cause is used to report receipt of a message with semantically incorrect contents. Cause #96 – Invalid mandatory information This ESM cause indicates that the equipment sending this ESM cause has received a message with a non-semantical mandatory IE error. Cause #97 – Message type non-existent or not implemented This ESM cause indicates that the equipment sending this ESM cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this ESM cause. Cause #98 – Message type not compatible with protocol state This ESM cause indicates that the equipment sending this ESM cause has received a message not compatible with the protocol state. Cause #99 – Information element non-existent or not implemented This ESM cause indicates that the equipment sending this ESM cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the ESM cause. However, the information element is not required to be present in the message in order for the equipment sending the ESM cause to process the message. Cause #100 – Conditional IE error This ESM cause indicates that the equipment sending this cause has received a message with conditional IE errors. Cause #101 – Message not compatible with protocol state This ESM cause indicates that a message has been received which is incompatible with the protocol state. Cause #111 – Protocol error, unspecified This ESM cause is used to report a protocol error event only when no other ESM cause in the protocol error class applies. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | B.2 |
2,011 | 5.30.2.7 Access to PLMN services via stand-alone non-public networks | To access PLMN services, a UE in SNPN access mode that has successfully registered with an SNPN may perform another registration via the SNPN User Plane with a PLMN (using the credentials of that PLMN) following the same architectural principles as specified in clause 4.2.8 (including the optional support for PDU Session continuity between PLMN and SNPN using the Handover of a PDU Session procedures in clauses 4.9.2.1 and 4.9.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) and the SNPN taking the role of "Untrusted non-3GPP access". Annex D, clause D.3 provides additional details. NOTE: QoS differentiation in the SNPN can be provided on per-IPsec Child Security Association basis by using the UE or network requested PDU Session Modification procedure described in clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In the PLMN, N3IWF determines the IPsec child SAs as defined in clause 4.12 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The N3IWF is preconfigured by PLMN to allocate different IPsec child SAs for QoS Flows with different QoS profiles. To support QoS differentiation in the SNPN with network-initiated QoS, the mapping rules between the SNPN and the PLMN are assumed to be governed by an SLA including: 1) mapping between the DSCP markings for the IPsec child SAs on NWu and the corresponding QoS, which is the QoS requirement of the PLMN and is expected to be provided by the SNPN, and 2) N3IWF IP address(es) in the PLMN. The non-alteration of the DSCP field on NWu is also assumed to be governed by an SLA and by transport-level arrangements that are outside of 3GPP scope. The packet detection filters in the SNPN can be based on the N3IWF IP address and the DSCP markings on NWu. To support QoS differentiation in the SNPN with UE-requested QoS, the UE can request for an IPsec SA the same 5QI from the SNPN as the 5QI provided by the PLMN. It is assumed that UE-requested QoS is used only when the 5QIs used by the PLMN are from the range of standardized 5QIs. The packet filters in the requested QoS rule can be based on the N3IWF IP address and the SPI associated with the IPsec SA. Refer to clause D.7 for details on how to support QoS differentiation. When the UE accesses the PLMN over NWu via a SNPN, the AMF in the serving PLMN shall send an indication toward the UE during the Registration procedure to indicate whether an IMS voice over PS session is supported or not. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.7 |
2,012 | 5.31.14 Support of rate control of user data 5.31.14.1 General | The rate of user data sent to and from a UE (e.g. a UE using CIoT 5GS Optimisations) can be controlled in two different ways: - Serving PLMN Rate Control; - Small Data Rate Control. Serving PLMN Rate Control is intended to allow the Serving PLMN to protect its AMF and the Signalling Radio Bearers in the NG-RAN from the load generated by NAS Data PDUs. Small Data Rate Control is intended to allow HPLMN operators to offer customer services such as "maximum of Y messages per day". NOTE: Existing Session-AMBR mechanisms are not suitable for such a service since, for radio efficiency and UE battery life reasons, an AMBR of e.g. > 100kbit/s is desirable and such an AMBR translates to a potentially large daily data volume. The SMF in the Serving PLMN may send the Small Data rate control parameter for an emergency PDU session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.14 |
2,013 | 16.14.3.1 Mobility in RRC_IDLE and RRC_INACTIVE | The same principles as described in 9.2.1 apply to mobility in RRC_IDLE for NTN and the same principles as described in 9.2.2 apply to mobility in RRC_INACTIVE for NTN unless hereunder specified. The network may broadcast multiple Tracking Area Codes (TACs) per PLMN in an NR NTN cell. A TAC change in the System Information is under network control, i.e. it may not be exactly synchronised with real-time illumination of beams on ground. For the NTN-TN mobility, the network may broadcast cell information on NR TN and EUTRA TN coverage areas in SIB25. This is supported for Earth-Fixed, Quasi-Earth-fixed and Earth-Moving cells. The coverage information consists in a list of geographical TN areas, with associated frequency information also indicated. UE can skip TN measurement based on the broadcast TN coverage information. The UE can determine the network type (terrestrial or non-terrestrial) implicitly by the existence of cellBarredNTN in SIB1. The NTN ephemeris is provided in SIB19. In an NTN cell, it includes serving cell's NTN payload ephemeris and optionally neighbouring cell's NTN payload ephemeris. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.3.1 |
2,014 | 6.2.2 Logical Channels | Different kinds of data transfer services as offered by MAC. Each logical channel type is defined by what type of information is transferred. Logical channels are classified into two groups: Control Channels and Traffic Channels. Control channels are used for the transfer of control plane information only: - Broadcast Control Channel (BCCH): a downlink channel for broadcasting system control information. - Paging Control Channel (PCCH): a downlink channel that carries paging messages. - Common Control Channel (CCCH): channel for transmitting control information between UEs and network. This channel is used for UEs having no RRC connection with the network. - Dedicated Control Channel (DCCH): a point-to-point bi-directional channel that transmits dedicated control information between a UE and the network. Used by UEs having an RRC connection. Traffic channels are used for the transfer of user plane information only: - Dedicated Traffic Channel (DTCH): point-to-point channel, dedicated to one UE, for the transfer of user information. A DTCH can exist in both uplink and downlink. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.2.2 |
2,015 | B.2.1.2.1 EAP TLS without subscription identifier privacy | For EAP TLS, if the operator determines to not provide subscription identifier privacy for the UE in TLS layer (e.g., in TLS 1.2 without privacy option), the subscription identifier protection in NAS layer, i.e., in Step 1 of Figure B.2.1-1, becomes ineffective privacy-wise. Therefore, the operator may just choose that UE uses "null-scheme" for calculation of SUCI which is sent in NAS layer. However, the operator may anyway use other than null-schemes (e.g., one of ECIES schemes) for simplification of having single scheme for all UEs in NAS layer even though privacy is not enhanced in this particular case. The operator could also determine not to provide subscription identifier privacy for the UE in NAS layer even though the TLS layer inherently provides subscription identifier privacy (e.g., in TLS 1.3). In such case, the operator may just choose that UE uses "null-scheme" for calculation of SUCI which is sent in NAS layer. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | B.2.1.2.1 |
2,016 | 8.51.10 en-gNB ID | The Target Type is an en-gNB ID for: - a TNL address discovery request of a candidate en-gNB via the S1 interface or via inter-system signalling (see clauses 22.3.6.2 and 22.3.6.3 of 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [19]). In this case, the Target ID field shall be coded as depicted in Figure 8.51.10-1. Figure 8.51.10-1: Target ID for Type en-gNB ID The en-gNB ID Length field, in bits 1 to 6 of octet 9, indicates the length of the en-gNB ID in number of bits. Bits 7 and 8 of octet 9 shall be encoded as follows: - Bit 7 - ETAC: when set to "1", octets p to (p+1) shall be present and encode a TAC (EPS); otherwise, octets p to (p+1) shall be absent. - Bit 8 - 5TAC: when set to "1", octets q to (q+2) shall be present and encode a 5GS TAC; otherwise, octets q to (q+2) shall be absent. The en-gNB ID consists of 22 to 32 bits. The en-gNB ID shall be coded as the gNodeB ID field of the gNodeB ID in clause 8.51.7. When present, the TAC shall consist of 2 octets and shall be coded as the TAC field of the Macro eNodeB ID in clause 8.51.3. When present, the 5GS TAC shall consist of 3 octets and shall be coded as the 5GS TAC field of the gNodeB ID in ubclause 8.51.7. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.51.10 |
2,017 | 4.2.2 Roaming architecture | Figure 4.2.2-1: Roaming architecture for 3GPP accesses. Home routed traffic NOTE 1: Additional interfaces/reference points for 2G/3G accesses are documented in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. The figures 4.2.2-2 and 4.2.2-3 represent the Roaming with local breakout case with Application Function (AF) in the Home Network and in the Visited Network respectively. The concurrent use of AF's in the home network and AF's in the visited network is not excluded. Figure 4.2.2-2: Roaming architecture for local breakout, with home operator's application functions only NOTE 2: See TS 23.203[ Policy and charging control architecture ] [6] for the role of and functions related to Home and Visited PCRF and S9/Rx reference points. NOTE 3: In figure 4.2.2-2, the control plane signalling and the user plane for accessing to Home Operator's services traverse over the SGi reference point via the Visited Operator's PDN. Figure 4.2.2-3: Roaming architecture for local breakout, with visited operator's application functions only | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2 |
2,018 | 5.30.2.5 Network access control | If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a self-assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to temporarily prevent the UE from automatically selecting and registering with the same SNPN. If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a coordinated assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to permanently prevent the UE from automatically selecting and registering with the same SNPN. NOTE: The details of rejection and cause codes is defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. If a UE performs the registration in an SNPN using credentials from a Credentials Holder (i.e. the CH is the PLMN/SNPN that owns the UE subscription and controls the access) and the Credentials Holder does not authorize the UE to access that specific SNPN due to access authorization based on subscription data or invalid time for accessing an SNPN that provides access to Localized Services, then the UDM, in the Credentials Holder, can reject the UE which results in AMF rejecting the registration request from the UE with an appropriate cause code to prevent the UE from automatically selecting and registering with the same SNPN using credentials from the Credentials Holder as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. In order to prevent access to SNPNs for authorized UE(s) in the case of network congestion/overload, Unified Access Control information is configured per SNPN (i.e. as part of the subscription information that the UE has for a given SNPN) and provided to the UE as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.5 |
2,019 | – SL-DRX-Config | The IE SL-DRX-Config is used to configure DRX related parameters for NR sidelink communication/discovery. The SL DRX timers should be calculated in the unit of physical slot. SL-DRX-Config information element -- ASN1START -- TAG-SL-DRX-CONFIG-START SL-DRX-Config-r17 ::= SEQUENCE { sl-DRX-ConfigGC-BC-r17 SL-DRX-ConfigGC-BC-r17 OPTIONAL, -- Cond HO sl-DRX-ConfigUC-ToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIndex-r16 OPTIONAL, -- Need N sl-DRX-ConfigUC-ToAddModList-r17 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DRX-ConfigUC-Info-r17 OPTIONAL, -- Need N ... } SL-DRX-ConfigUC-Info-r17 ::= SEQUENCE { sl-DestinationIndex-r17 SL-DestinationIndex-r16 OPTIONAL, -- Need N sl-DRX-ConfigUC-r17 SL-DRX-ConfigUC-r17 OPTIONAL, -- Need N ... } -- TAG-SL-DRX-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,020 | 8.2.2.3.3 Minimum Requirement 2Tx antenna port (demodulation subframe overlaps with aggressor cell ABS) | The requirements for non-MBSFN ABS are specified in Table 8.2.2.3.3-2, with the addition of parameters in Table 8.2.2.3.3-1 and the downlink physical channel setup according to Annex C.3.2 and Annex C.3.3. The requirements for MBSFN ABS are specified in Table 8.2.2.3.3-4, with the addition of parameters in Table 8.2.2.3.3-3 and the downlink physical channel setup according to Annex C.3.2 and Annex C.3.3. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell. In Tables 8.2.2.3.3-1 and 8.2.2.3.3-3, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.2.2.3.3-1: Test Parameters for Large Delay CDD (FRC) – Non-MBSFN ABS Table 8.2.2.3.3-2: Minimum Performance Large Delay CDD (FRC) – Non-MBSFN ABS Table 8.2.2.3.3-3: Test Parameters for Large Delay CDD (FRC) – MBSFN ABS Table 8.2.2.3.3-4: Minimum Performance Large Delay CDD (FRC) – MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.3.3 |
2,021 | 6.46.7 Satellite and Relay UEs | For a 5G system with satellite access, the following requirements apply: - A 5G system with satellite access shall be able to support relay UE's with satellite access. NOTE: The connection between a relay UE and a remote UE is the same regardless of whether the relay UE is using satellite access or not. - A 5G system with satellite access shall support mobility management of relay UEs and the remote UEs connected to the relay UE between a 5G satellite access network and a 5G terrestrial network, and between 5G satellite access networks. - A 5G system with satellite access shall support joint roaming between different 5G networks of a relay UE and the remote UEs connected to that relay UE. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.46.7 |
2,022 | 8.11.2.2.3 CE Mode A with TM9 interference model | The requirements are specified in Table 8.11.2.2.3-2, with the addition of parameters in Table 8.11.2.2.3-1. In Table 8.11.2.2.3-2, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the MPDCCH performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.11.2.2.3-1: Test Parameters for MPDCCH (TM9 interference model) Table 8.11.2.2.3-2: Minimum performance CE Mode A MPDCCH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.11.2.2.3 |
2,023 | 5.15.5.2.2 Modification of the Set of Network Slice(s) for a UE | The set of Network Slices for a UE can be changed at any time while the UE is registered with a network, and may be initiated by the network, or by the UE, under certain conditions as described below. The network, based on local policies, subscription changes and/or UE mobility and/or UE Dispersion data classification, operational reasons (e.g. a Network Slice instance is no longer available or load level information or service experience for a Network Slice or network slice instance provided by the NWDAF), may change the set of Network Slice(s) to which the UE is registered and provide the UE with a new Registration Area and/or Allowed NSSAI and the mapping of this Allowed NSSAI to HPLMN S-NSSAIs, for each Access Type over which the UE is registered. In addition, the network may provide the Configured NSSAI for the Serving PLMN, the associated mapping information, and the rejected S-NSSAIs. The network may perform such a change over each Access Type during a Registration procedure or trigger a notification towards the UE of the change of the Network Slices using a UE Configuration Update procedure as specified in clause 4.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The new Allowed NSSAI(s) and the mapping to HPLMN S-NSSAIs are determined as described in clause 5.15.5.2.1 (an AMF Re-allocation may be needed). The AMF provides the UE with: - an indication that the acknowledgement from UE is required; - Configured NSSAI for the Serving PLMN (if required), rejected S-NSSAI(s) (if required) and TAI list, and - the new Allowed NSSAI with the associated mapping of Allowed NSSAI for each Access Type (as applicable) unless the AMF cannot determine the new Allowed NSSAI (e.g. all S-NSSAIs in the old Allowed NSSAI have been removed from the Subscribed S-NSSAIs). Furthermore: - If the changes to the Allowed NSSAI require the UE to perform immediately a Registration procedure because they affect the existing connectivity to AMF (e.g. the new S-NSSAIs require a separate AMF that cannot be determined by the current serving AMF, or the AMF cannot determine the Allowed NSSAI) or due to AMF local policies also when the changes does not affect the existing connectivity to AMF: - The serving AMF indicates to the UE the need for the UE to perform a Registration procedure without including the GUAMI or 5G-S-TMSI in the access stratum signalling after entering CM-IDLE state. The AMF shall release the NAS signalling connection to the UE to allow to enter CM-IDLE after receiving the acknowledgement from UE. - When the UE receives indications to perform a Registration procedure without including the GUAMI or 5G-S-TMSI in the access stratum signalling after entering CM-IDLE state, then: - The UE deletes any stored (old) Allowed NSSAI and associated mapping as well as any (old) rejected S-NSSAI. - The UE shall initiate a Registration procedure with the registration type Mobility Registration Update after the UE enters CM-IDLE state as specified in as described in step 4 of clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UE shall include a Requested NSSAI (as described in clause 5.15.5.2.1) with the associated mapping of Requested NSSAI in the Registration Request message. Also, the UE shall include, subject to the conditions set out in clause 5.15.9, a Requested NSSAI in access stratum signalling but no GUAMI. - If the AMF determines that the S-NSSAI in the Allowed NSSAI is replaced with Alternative S-NSSAI, the AMF provides the mapping of old S-NSSAI to the Alternative S-NSSAI to the UE (as described in clause 5.15.19). If there is an established PDU Session associated with emergency services, then the serving AMF indicates to the UE the need for the UE to perform a Registration procedure but does not release the NAS signalling connection to the UE. The UE performs the Registration procedure only after the release of the PDU Session used for the emergency services. In addition to sending the new Allowed NSSAI to the UE, when a Network Slice used for a one or multiple PDU Sessions is no longer available for a UE, the following applies: - If the Network Slice becomes no longer available under the same AMF and the Network Slice Replacement is not used (e.g. due to UE subscription change), the AMF indicates to the SMF(s) which PDU Session ID(s) corresponding to the relevant S-NSSAI shall be released. SMF releases the PDU Session according to clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the Network Slice Replacement is used, the AMF performs Network Slice Replacement as described in clause 5.15.19. - If the Network Slice becomes no longer available upon a change of AMF (e.g. due to Registration Area change), the new AMF indicates to the old AMF that the PDU Session(s) corresponding to the relevant S-NSSAI shall be released. The old AMF informs the corresponding SMF(s) to release the indicated PDU Session(s). The SMF(s) release the PDU Session(s) as described in clause 4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Then the new AMF modifies the PDU Session Status correspondingly. The PDU Session(s) context is locally released in the UE after receiving the PDU Session Status in the Registration Accept message. The UE uses either the URSP rules (which includes the NSSP) or the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] to determine whether ongoing traffic can be routed over existing PDU Sessions belonging to other Network Slices or establish new PDU Session(s) associated with same/other Network Slice. In order to change the set of S-NSSAIs the UE is registered to over an Access Type, the UE shall initiate a Registration procedure over this Access Type as specified in clause 5.15.5.2.1. If, for an established PDU Session: - none of the values of the S-NSSAIs of the HPLMN in the mapping of the Requested NSSAI to S-NSSAIs of the HPLMN included in the Registration Request matches the S-NSSAI of the HPLMN associated with the PDU Session; or - none of the values of the S-NSSAIs in the Requested NSSAI matches the value of the S-NSSAI of HPLMN associated with the PDU Session and the mapping of the Requested NSSAI to S-NSSAIs of the HPLMN is not included in the Registration Request, the network shall release this PDU Session as follows. - the AMF informs the corresponding SMF(s) to release the indicated PDU Session(s). The SMF(s) release the PDU Session(s) as described in clause 4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Then the AMF modifies the PDU Session Status correspondingly. The PDU Session(s) context is locally released in the UE after receiving the PDU Session Status from the AMF. A change of the set of S-NSSAIs (whether UE or Network initiated) to which the UE is registered may, subject to operator policy, lead to AMF change, as described in clause 5.15.5.2.1. If the AMF supports the Network Slice Replacement feature and is configured to use the NSSF to trigger the Network Slice Replacement, the AMF subscribes with the NSSF for notifications when any of the S-NSSAIs served by the AMF (e.g. the S-NSSAI in the Serving PLMN and the HPLMN S-NSSAI in roaming case) has to be replaced as described in clause 5.15.19. If the AMF supports the Network Slice Instance Replacement and configured to use Network Slice Instance Replacement, the AMF subscribes with the NSSF for notifications when a Network Slice instances served by the AMF is congested or no longer available as described in clause 5.15.20. The AMF may perform Network Slice Replacement for the PDU Session as described in clause 5.15.19. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.5.2.2 |
2,024 | 8 Handling of unknown, unforeseen, and erroneous protocol data 8.1 General | The procedures specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and call-related supplementary service handling in 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21] apply to those messages which pass the checks described in this subclause. This subclause also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. Error handling concerning the value part of the Facility IE and of the SS Version Indicator IE are not in the scope of the present document. It is defined in 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21] and the 3GPP TS 24.08[ None ] x series. Sub subclauses 8.1 to 8.8 shall be applied in order of precedence. Most error handling procedures are mandatory for the mobile station. Detailed error handling procedures in the network are implementation dependent and may vary from PLMN to PLMN. However, when extensions of this protocol are developed, networks will be assumed to have the error handling that is indicated in this subclause as mandatory ("shall") and that is indicated as strongly recommended ("should"). Subclauses 8.2, 8.3, 8.4, 8.5 and 8.7.2 do not apply to the error handling in the network applied to the receipt of initial layer 3 message: If the network diagnoses an error described in one of these subclauses in the initial layer 3 message received from the mobile station, it shall either: - try to recognize the classmark and then take further implementation dependent actions; or - release the RR-connection. Also, the error handling of the network is only considered as mandatory or strongly recommended when certain thresholds for errors are not reached during a dedicated connection. For definition of semantical and syntactical errors see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20], subclause 11.4.2. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8 |
2,025 | 11.2 Inter-node RRC messages 11.2.1 General | This clause specifies RRC messages that are sent either across the X2-, Xn- or the NG-interface, either to or from the gNB, i.e. a single 'logical channel' is used for all RRC messages transferred across network nodes. The information could originate from or be destined for another RAT. -- ASN1START -- TAG-NR-INTER-NODE-DEFINITIONS-START NR-InterNodeDefinitions DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS AffectedCarrierFreqCombList-r16, AffectedCarrierFreqRangeCombList-r18, ARFCN-ValueNR, ARFCN-ValueEUTRA, CandidateServingFreqListNR-r16, CandidateServingFreqRangeListNR-r18, CellIdentity, CGI-InfoEUTRA, CGI-InfoNR, CondReconfigExecCondSCG-r17, CSI-RS-Index, CSI-RS-CellMobility, DRX-Config, EUTRA-PhysCellId, FeatureSetDownlinkPerCC-Id, FeatureSetUplinkPerCC-Id, FlightPathInfoReport-r18, FreqBandIndicatorNR, GapConfig, IDC-TDM-Assistance-r18, maxBandComb, maxBands, maxBandsEUTRA, maxCandidateBandIndex-r18, maxCellSFTD, maxFeatureSetsPerBand, maxFreq, maxFreqIDC-MRDC, maxNrofCombIDC, maxNrofCondCells-r16, maxNrofCondCells-1-r17, maxNrofPhysicalResourceBlocks, maxNrofSCells, maxNrofServingCells, maxNrofServingCells-1, maxNrofServingCellsEUTRA, maxNrofIndexesToReport, maxSimultaneousBands, MBSInterestIndication-r17, MeasQuantityResults, MeasResultCellListSFTD-EUTRA, MeasResultCellListSFTD-NR, MeasResultList2NR, MeasResultSCG-Failure, MeasResultServFreqListEUTRA-SCG, MUSIM-CandidateBandList-r18, MUSIM-CapRestriction-r18, MUSIM-GapConfig-r17, NeedForGapsInfoNR-r16, NeedForGapNCSG-InfoNR-r17, NeedForGapNCSG-InfoEUTRA-r17, NeedForInterruptionInfoNR-r18, OverheatingAssistance, OverheatingAssistance-r17, P-Max, PhysCellId, RadioBearerConfig, RAN-NotificationAreaInfo, ReferenceConfiguration-r18, ReportConfigNR, RRCReconfiguration, ServCellIndex, SetupRelease, SSB-Index, SSB-MTC, SSB-ToMeasure, SS-RSSI-Measurement, ShortMAC-I, SubcarrierSpacing, UEAssistanceInformation, UE-CapabilityRAT-ContainerList, maxNrofCLI-RSSI-Resources-r16, maxNrofCLI-SRS-Resources-r16, RSSI-ResourceId-r16, SDT-Config-r17, SidelinkUEInformationNR-r16, SRS-ResourceId, UE-RadioPagingInfo-r17 FROM NR-RRC-Definitions; -- TAG-NR-INTER-NODE-DEFINITIONS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 11.2 |
2,026 | 5.2.8.2 Nsmf_PDUSession Service 5.2.8.2.1 General | Service description: This service operates on the PDU Sessions. The following are the key functionalities of this NF service: - (between AMF and SMF) Creation / Deletion / Modification of AMF-SMF interactions for PDU Sessions; The resource handled between AMF and SMF via Create / Update / Release SM context operations corresponds to the AMF-SMF association for a PDU Session; When the AMF has got no association with an SMF to support a PDU Session, the AMF creates such association via the Nsmf_PDUSession_CreateSMContext operation. The context created is identified via the SM Context ID. Otherwise (e.g. at hand-over between 3GPP and Non 3GPP access) the AMF uses the Nsmf_PDUSession_UpdateSMContext operation. NOTE 1: In TS 29.502[ 5G System; Session Management Services; Stage 3 ] [36] SM Context ID is referred to as smContextRef for N11 and pduSessionRef and pduSessionUri for N16. When the UE is handed-over from an (old) AMF towards another (new) AMF, the old AMF provides the new AMF with the SMF addressing information corresponding to the AMF-SMF association related with each PDU Session of that UE. The new AMF can thus further act upon the association with the SMF via Nsmf_PDUSession_UpdateSMContext and Nsmf_PDUSession_ReleaseSMContext operations. This may take place: - at inter AMF change due to AMF planned maintenance or due to AMF failure described in clause 5.21.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; - at inter AMF mobility in CM-CONNECTED state described in clause 4.9.1.3; - at inter AMF mobility in CM-IDLE state described in clause 4.2.2.2. - (between AMF and SMF) Passing MO Small Data from AMF to SMF in clause 4.24.1. - (between V-SMF and H-SMF) Creation / Deletion / Modification of PDU Sessions; - (between V-SMF/I-SMF and (H-)SMF) Transferring MO Small Data from V-SMF/I-SMF to (H-)SMF in clause 4.25.4. - (between V-SMF/I-SMF and (H-)SMF) Transferring MT Small Data from (H-)SMF to V-SMF/I-SMF in clause 4.24.5. Even though the V-SMF creates the PDU Session resource onto the H-SMF, each of the V-SMF and of the H-SMF needs to be able to modify a PDU Session and/or to ask for PDU Session Release. Thus, at Nsmf_PDUSession_Create, V-SMF informs the H-SMF about addressing information for its corresponding PDU Session resource, allowing H-SMF to use later on the Nsmf_PDUSession_Update and Nsmf_PDUSession_Release and Nsmf_PDUSession_StatusNotify operations. NOTE 2: The PDU Session resource in V-SMF is created when the AMF requests to create SM context of this PDU Session NOTE 3: H-SMF also informs the consumer (V-SMF) about addressing information about its PDU Session resource, but this is part of normal resource creation operation in REST and not specific to this service. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2 |
2,027 | 4.1.1.3 Failed RRC connection establishments | a) This measurement provides the number of RRC establishment failures for each establishment cause. b) CC c) Transmission of an RRCConnectionReject message by the eNodeB/RN to the UE or an expected RRCConnectionSetupComplete message not received by the eNodeB/RN. Each failed RRC connection establishment is added to the relevant per establishment cause measurement. The possible causes are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The sum of all supported per cause measurements shall equal the total number of RRC connection establishment failures. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form RRC.ConnEstabFail.Cause where Cause identifies the establishment cause. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.1.1.3 |
2,028 | 5.3.5.18.6 LTM cell switch execution | Upon the indication by lower layers that an LTM cell switch procedure is triggered, or upon performing LTM cell switch following cell selection performed while timer T311 was running, as specified in 5.3.7.3, the UE shall: 1> release/clear all current dedicated radio configuration associated with the cell group for which the LTM cell switch procedure is triggered except for the following: - the logicalChannelIdentity and logicalChannelIdentityExt of RLC bearers configured in RLC-BearerConfig and the associated RLC entities, their state variables, buffers, and timers; - the UE variables VarLTM-Config, VarLTM-ServingCellNoResetID, and VarLTM-ServingCellUE-MeasuredTA-ID. 2> if the LTM cell switch is triggered on the MCG: - the MCG C-RNTI; - the AS security configurations associated with the master key; - for each SRB/DRB in current UE configuration which is using the master key: - keep the associated PDCP and SDAP entities, their state variables, buffers and timers; - release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity; 2> else, if the LTM cell switch is triggered on the SCG: - the AS security configurations associated with the secondary key; - for each SRB/DRB in current UE configuration which is using the secondary key: - keep the associated PDCP and SDAP entities, their state variables, buffers and timers; - release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity; 1> release/clear all current common radio configuration associated with the cell group for which the LTM cell switch procedure is triggered; 1> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311 associate to cell group for which the LTM cell switch procedure is triggered; 1> if the value of field ltm-NoResetID contained within the LTM-Candidate IE in VarLTM-Config indicated by lower layers or for the selected cell in accordance with 5.3.7.3 is not equal to the value of ltm-ServingCellNoResetID within VarLTM-ServingCellNoResetID: 2> for each logicalChannelId and logicalChannelIdExt that is part of the current UE configuration for the cell group for which the LTM cell switch procedure is triggered: 3> after the end of this procedure, re-establish the corresponding RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], after applying the LTM configuration in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config; 2> for each drb-Identity value that is part of the current UE configuration: 3> if this DRB is an AM DRB: 4> after the end of this procedure, trigger the PDCP entity of this DRB to perform data recovery as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5], after applying the LTM configuration in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config; 2> replace the value of ltm-ServingCellNoResetID in VarLTM-ServingCellNoResetID with the value of ltm-NoResetID in the LTM-Candidate in VarLTM-Config indicated by lower layers or for the selected cell in accordance with 5.3.7.3;1> if the LTM-Candidate IE in VarLTM-Config indicated by lower layers or for the selected cell in accordance with 5.3.7.3 contains the field ltm-UE-MeasuredTA-ID: 2> replace the value of ltm-ServingCellUE-MeasuredTA-ID in VarLTM-ServingCellUE-MeasuredTA-ID with the value received within ltm-UE-MeasuredTA-ID; 1> if ltm-ConfigComplete is not included within the LTM-Candidate IE in VarLTM-Config indicated by lower layers or for the selected cell in accordance with 5.3.7.3: 2> consider ltm-ReferenceConfiguration in VarLTM-Config, associated with the cell group for which the LTM cell switch procedure is triggered, to be the current UE configuration for the fields and configurations which have been released and to be released by the actions above in this procedure; NOTE 1: When the UE considers the reference configuration to be the current UE configuration, the UE should store fields and configurations that are part of the reference configuration but should not execute any actions or procedures triggered by the reception of an RRCReconfiguration message which are described in clause 5.3.5.3. 1> if the LTM cell switch is triggered by an indication from lower layers: 2> apply the RRCReconfiguration message in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config identified by the LTM candidate configuration identity received from lower layers according to clause 5.3.5.3; 1> else (LTM cell switch triggered upon cell selection performed while timer T311 was running): 2> apply the RRCReconfiguration message in ltm-CandidateConfig within LTM-Candidate IE in VarLTM-Config related to the LTM candidate configuration identity for the selected cell (i.e., in accordance with 5.3.7.3) according to clause 5.3.5.3; 1> release the radio bearer(s) and the logical channel(s) that are part of the current UE configuration but not part of the LTM candidate configuration either indicated by lower layers or for the selected cell in accordance with 5.3.7.3, or the LTM reference configuration (in case the LTM candidate configuration does not include ltm-ConfigComplete). NOTE 2: When ltm-ConfigComplete is not included for an LTM candidate configuration, before an LTM cell switch is triggered a UE implementation may generate and store an RRC reconfiguration message by applying the received LTM candidate configuration on top of the LTM reference configuration, and the stored RRC reconfiguration message is applied when the LTM cell switch is triggered. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.18.6 |
2,029 | 8.1 UE Identities | In this clause, the identities used by NR connected to 5GC are listed. For scheduling at cell level, the following identities are used: - C-RNTI: unique UE identification used as an identifier of the RRC Connection and for scheduling; - CG-SDT-CS-RNTI: unique UE identification used for Configured Grant-based SDT in the uplink; - CI-RNTI: identification of cancellation in the uplink; - CS-RNTI: unique UE identification used for Semi-Persistent Scheduling in the downlink or configured grant in the uplink; - INT-RNTI: identification of pre-emption in the downlink; - MCS-C-RNTI: unique UE identification used for indicating an alternative MCS table for PDSCH and PUSCH; - P-RNTI: identification of Paging and System Information change notification in the downlink; - SI-RNTI: identification of Broadcast and System Information in the downlink; - SP-CSI-RNTI: unique UE identification used for semi-persistent CSI reporting on PUSCH. For power and slot format control, the following identities are used: - SFI-RNTI: identification of slot format; - TPC-PUCCH-RNTI: unique UE identification to control the power of PUCCH; - TPC-PUSCH-RNTI: unique UE identification to control the power of PUSCH; - TPC-SRS-RNTI: unique UE identification to control the power of SRS. During the random access procedure, the following identities are also used: - RA-RNTI: identification of the Random Access Response in the downlink; - MSGB-RNTI: identification of the Random Access Response for 2-step RA type in the downlink; - Temporary C-RNTI: UE identification temporarily used for scheduling during the random access procedure; - Random value for contention resolution: UE identification temporarily used for contention resolution purposes during the random access procedure. For NR connected to 5GC, the following UE identity is used at NG-RAN level: - I-RNTI: used to identify the UE context in RRC_INACTIVE. For UE power saving purpose, the following identities are used: - PS-RNTI: used to determine if the UE needs to monitor PDCCH on the next occurrence of the connected mode DRX on-duration; - PEI-RNTI: used to determine if the UE needs to monitor the associated PO. For IAB the following identity is used: - AI-RNTI: identification of the DCI carrying availability indication for soft symbols of an IAB-DU. For Network-Controlled Repeater the following identity is used: - NCR-RNTI: identification of the DCI carrying side control information. For MBS, the following identities are used: - G-RNTI: Identifies dynamically scheduled PTM transmissions of MTCH(s); - G-CS-RNTI: Identifies configured scheduled PTM transmissions of MTCH(s) scheduled with configured grant; - MCCH-RNTI: Identifies transmissions of MCCH and MCCH change notification. For sidelink, the following identities are used: - SL-RNTI: unique UE identification used for NR sidelink communication scheduling; - SL-CS-RNTI: unique UE identification used for configured sidelink grant for NR sidelink communication; - SL Semi-Persistent Scheduling V-RNTI: unique UE identification used for semi-persistent scheduling for V2X sidelink communication; - SL-PRS-RNTI: unique UE identification used for SL-PRS transmission scheduling on dedicated SL-PRS resource pool; - SL-PRS-CS-RNTI: unique UE identification used for configured sidelink grant for SL-PRS transmission on dedicated SL-PRS resource pool. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 8.1 |
2,030 | 13.2.3.2 Data-type encryption policy | The SEPP shall contain an operator-controlled protection policy that specifies which types of data shall be encrypted. The data-types defined are the following: - Data of the type 'SUPI'; - Data of the type 'authentication vector'; - Data of the type 'location data'; - Data of the type 'cryptographic material'; - Data of the type 'authorization token'. The policy shall be specific per roaming partner. The policy shall contain a policy identifier and a release number referring to the release it is applicable for. The data-type encryption policies in the two partner SEPPs shall be equal to enforce a consistent ciphering of IEs on N32-f. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.3.2 |
2,031 | 7.7.2 Conditional IE errors | When upon receipt of a EMM or ESM message the UE diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error, or when it receives a EMM or ESM message containing at least one syntactically incorrect conditional IE, the UE shall ignore the message and shall return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #100 "conditional IE error". When the network receives a message and diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE, the network shall either: - try to treat the message (the exact further actions are implementation dependent); or - ignore the message except that it should return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #100 "conditional IE error". | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.7.2 |
2,032 | Annex N (normative): Ranking of reject causes for Location Registration (MM and GMM) in a shared network | This annex describes how the reject cause is determined: - for a network sharing non-supporting MS in a shared network with multi-operator core network (MOCN) configuration; or - for any MS in a multi-operator core network (MOCN) with common GERAN, when a location registration request from the MS is redirected among CN operators via the shared RAN (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109]) and is rejected by all core networks. In the following, the term 'location registration' is used for location area updating, GPRS attach, combined GPRS attach, routing area updating, and combined routing area updating. i) If the location registration request was either: 1) accepted; 2) rejected with a reject cause different from #11, #12, #13, #14, #15, #17, and #25; or 3) rejected with a reject cause #17 when the MSC or the SGSN received an error not indicating "system failure", "data missing" or "unexpected data value" from the HLR (see 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [37] and 3GPP TS 29.010[ Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP) ] [152]), then one of the following actions is taken: - in UTRAN Iu mode, the MSC or SGSN shall include the redirection completed information element in the RANAP DIRECT TRANSFER message transmitting the location registration accept message or location registration reject message to the RNC. According to 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c], the RNC will then forward the location registration accept message or the location registration reject message to the MS. - in A/Gb mode, the shall use DTAP message and SGSN shall use BSSGP DL-UNIDATA message to carry the location registration accept message or location registration reject message to the . According to 3GPP TS 48.008[ None ] [85] and 3GPP TS 48.018[ None ] [86], the will then forward the location registration accept message or location registration reject message to the MS. ii) If the location registration request was either: 1) rejected with one of the reject causes #11, #12, #13, #14, #15, and #25; or 2) rejected with a reject cause #17 when the MSC or the SGSN received an error indicating "system failure", "data missing" or "unexpected data value" from the HLR (see 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [37] and 3GPP TS 29.010[ Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP) ] [152]), then one of the following actions is taken: - in UTRAN Iu mode, the MSC or SGSN shall include a redirection indication in the RANAP DIRECT TRANSFER message transmitting the location registration reject message to the RNC. According to 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c], the RNC will then initiate the redirection procedure towards the next CN operator and treat the response from the core network according to (i) and (ii). - in A/Gb mode, the shall use BSSMAP Reroute Command message and SGSN shall use BSSGP DL-UNIDATA message to transmit the location registration reject message to the with a redirection indication. According to 3GPP TS 48.008[ None ] [85] and 3GPP TS 48.018[ None ] [86], the will then initiate the redirection procedure towards the next CN operator and treat the response from the core network according to (i), (ii) and (iii). iii) If the location registration request was rejected including a redirection indication and with one of the reject causes #11, #12, #13, #14, #15, #17, and #25 by all CN operators taking part in a shared network, the RNC for UTRAN Iu mode or the for A/Gb mode shall determine the reject cause with the highest rank from the received reject causes and send a location registration reject message containing this reject cause to the MS. The ranking of the reject causes, from the lowest rank to the highest rank, is given by: #11 < #12 < #13 < #14 < #15 < #25 < #17. iv) If the location registration request was rejected with one of the reject causes #11, #12, #13, #14, and #15 by all CN operators taking part in a shared network in a specific location area, but there is at least one additional CN operator taking part in a shared network in another location area of the shared network defined by the same common PLMN identity, the RNC for UTRAN Iu mode or the for A/Gb mode shall send a location registration reject message with the reject cause #15 to the MS. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | Annex |
2,033 | – RSRP-Range | The IE RSRP-Range specifies the value range used in RSRP measurements and thresholds. For measurements, integer value for RSRP measurements is according to Table 10.1.6.1-1 in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. For thresholds, the actual value is (IE value – 156) dBm, except for the IE value 127, in which case the actual value is infinity. RSRP-Range information element -- ASN1START -- TAG-RSRP-RANGE-START RSRP-Range ::= INTEGER(0..127) -- TAG-RSRP-RANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,034 | 8.7.7 TDD (DC) | The parameters specified in Table 8.7.7-1 are valid for all TDD DC tests unless otherwise stated. Table 8.7.7-1: Common Test Parameters (TDD) For UE not supporting 256QAM, the requirements are specified in Table 8.7.7-2, with the addition of the parameters in Table 8.7.7-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.7-3. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements are specified in Table 8.7.7-4, with the addition of the parameters in Table 8.7.7-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.7-5. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements in Table 8.7.7-2 are not applicable. The applicability of ther requirements are specified in Clause 8.1.2.3A. Table 8.7.7-2: Minimum requirement (DC 64QAM) Table 8.7.7-3: Test points for sustained data rate (FRC DC 64QAM) Table 8.7.7-4: Minimum requirement (DC 256QAM) Table 8.7.7-5: Test points for sustained data rate (FRC DC 256QAM) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.7 |
2,035 | 4.3.24 RAN user plane congestion management function 4.3.24.1 General | The user plane congestion management function addresses how the system can effectively mitigate RAN user plane congestion in order to reduce the negative impact on the perceived service quality. The congestion mitigation measures include traffic prioritization, traffic reduction and limitation of traffic, and shall be able to manage user plane traffic across a range of variables including the user's subscription, the type of application, and the type of content. Congestion mitigation can be performed in the RAN or in the CN, or in a combined way both in the RAN and in the CN. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.24 |
2,036 | 9.5.9 Modify PDP context request (Network to MS direction) | This message is sent by the network to the MS to request modification of an active PDP context. See table 9.5.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: modify PDP context request (NETWORK to MS Direction) Significance: global Direction: network to MS Table 9.5.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : modify PDP context request (Network to MS direction) message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.5.9 |
2,037 | 5.5.4.2 Reaction of call control | Depending whether call re-establishment is allowed or not and on its actual state, call control shall decide to either request re-establishment or to release the MM connection. a) Re-establishment not required If the call is in the call establishment or call clearing phase, i.e. any state other than the "active" state or the "mobile originating modify" state, call control shall release the MM connection b) Re-establishment required If the call is in the "active" state or "mobile originating modify" state, the indication from MM that re-establishment is possible shall cause call control to request re-establishment from the MM connection, suspend any further message to be sent and await the completion of the re-establishment procedure. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.4.2 |
2,038 | – FeatureSets | The IE FeatureSets is used to provide pools of downlink and uplink features sets. A FeatureSetCombination refers to the IDs of the feature set(s) that the UE supports in that FeatureSetCombination. The BandCombination entries in the BandCombinationList then indicate the ID of the FeatureSetCombination that the UE supports for that band combination. The entries in the lists in this IE are identified by their index position. For example, the FeatureSetUplinkPerCC-Id = 4 identifies the 4th element in the featureSetsUplinkPerCC list. NOTE: When feature sets (per CC) IEs require extension in future versions of the specification, new versions of the FeatureSetDownlink, FeatureSetUplink, FeatureSets, FeatureSetDownlinkPerCC and/or FeatureSetUplinkPerCC will be created and instantiated in corresponding new lists in the FeatureSets IE. For example, if new capability bits are to be added to the FeatureSetDownlink, they will instead be defined in a new FeatureSetDownlink-rxy which will be instantiated in a new featureSetDownlinkList-rxy list. If a UE indicates in a FeatureSetCombination that it supports the FeatureSetDownlink with ID #5, it implies that it supports both the features in FeatureSetDownlink #5 and FeatureSetDownlink-rxy #5 (if present). The number of entries in the new list(s) shall be the same as in the original list(s). FeatureSets information element -- ASN1START -- TAG-FEATURESETS-START FeatureSets ::= SEQUENCE { featureSetsDownlink SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink OPTIONAL, featureSetsDownlinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC OPTIONAL, featureSetsUplink SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink OPTIONAL, featureSetsUplinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC OPTIONAL, ..., [[ featureSetsDownlink-v1540 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1540 OPTIONAL, featureSetsUplink-v1540 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1540 OPTIONAL, featureSetsUplinkPerCC-v1540 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1540 OPTIONAL ]], [[ featureSetsDownlink-v15a0 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v15a0 OPTIONAL ]], [[ featureSetsDownlink-v1610 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1610 OPTIONAL, featureSetsUplink-v1610 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1610 OPTIONAL, featureSetDownlinkPerCC-v1620 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1620 OPTIONAL ]], [[ featureSetsUplink-v1630 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1630 OPTIONAL ]], [[ featureSetsUplink-v1640 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1640 OPTIONAL ]], [[ featureSetsDownlink-v1700 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1700 OPTIONAL, featureSetsDownlinkPerCC-v1700 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1700 OPTIONAL, featureSetsUplink-v1710 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1710 OPTIONAL, featureSetsUplinkPerCC-v1700 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1700 OPTIONAL ]], [[ featureSetsDownlink-v1720 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1720 OPTIONAL, featureSetsDownlinkPerCC-v1720 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1720 OPTIONAL, featureSetsUplink-v1720 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1720 OPTIONAL ]], [[ featureSetsDownlink-v1730 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1730 OPTIONAL, featureSetsDownlinkPerCC-v1730 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1730 OPTIONAL ]], [[ featureSetsDownlink-v1800 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1800 OPTIONAL, featureSetsDownlinkPerCC-v1800 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1800 OPTIONAL, featureSetsUplink-v1800 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1800 OPTIONAL, featureSetsUplinkPerCC-v1800 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1800 OPTIONAL ]] } FeatureSets-v16d0 ::= SEQUENCE { featureSetsUplink-v16d0 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v16d0 OPTIONAL } -- TAG-FEATURESETS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,039 | 6.2.1 Principle of handling Application Protocol Identities | An Application Protocol Identity (AP ID) is allocated when a new UE-associated logical connection is created in either an NG-RAN node or an AMF. An AP ID shall uniquely identify a logical connection associated to a UE over the NG interface or Xn interface within a node (NG-RAN node or AMF) or over the F1 interface or over the E1 interface or over the W1 interface. Upon receipt of a message that has a new AP ID from the sending node, the receiving node shall store the AP ID of the sending node for the duration of the logical connection. The receiving node shall assign the AP ID to be used to identify the logical connection associated to the UE and include it as well as the previously received new AP ID from the sending node, in the first returned message to the sending node. In all subsequent messages to and from sending node, both AP IDs of sending node and receiving node shall be included. For MBS-associated logical connections of the E1 interface and the F1 interface the same principles for AP IDs apply as for UE-associated logical connections. The definitions of AP IDs as used on NG interface or Xn interface or F1 interface or E1 interface are shown below: RAN UE NGAP ID: A RAN UE NGAP ID shall be allocated so as to uniquely identify the UE over the NG interface within an gNB. When an AMF receives an RAN UE NGAP ID it shall store it for the duration of the UE-associated logical NG-connection for this UE. Once known to an AMF this is included in all UE associated NGAP signalling. The RAN UE NGAP ID shall be unique within the logical NG-RAN node. AMF UE NGAP ID: An AMF UE NGAP ID shall be allocated so as to uniquely identify the UE over the NG interface within the AMF. When a NG-RAN node receives an AMF UE NGAP ID it shall store it for the duration of the UE-associated logical NG-connection for this UE. Once known to a NG-RAN node this ID is included in all UE associated NGAP signalling. The AMF UE NGAP ID shall be unique within an AMF Set as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. Old NG-RAN node UE XnAP ID: An Old NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within a source NG-RAN node. When a target NG-RAN node receives an Old NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to a target NG-RAN node this ID is included in all UE associated XnAP signalling. The Old NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. New NG-RAN node UE XnAP ID: A New NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within a target NG-RAN node. When a source NG-RAN node receives a New NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to a source NG-RAN node this ID is included in all UE associated XnAP signalling. The New NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. M-NG-RAN node UE XnAP ID: An M-NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within an M-NG-RAN node for dual connectivity. When an S-NG-RAN node receives an M-NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to an S-NG-RAN node this ID is included in all UE associated XnAP signalling. The M-NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. S-NG-RAN node UE XnAP ID: A S-NG-RAN node UE XnAP ID shall be allocated so as to uniquely identify the UE over the Xn interface within an S-NG-RAN node for dual connectivity. When an M-NG-RAN node receives a S-NG-RAN node UE XnAP ID it shall store it for the duration of the UE-associated logical Xn-connection for this UE. Once known to an M-NG-RAN node this ID is included in all UE associated XnAP signalling. The S-NG-RAN node UE XnAP ID shall be unique within the logical NG-RAN node. gNB-CU UE F1AP ID: A gNB-CU UE F1AP ID shall be allocated so as to uniquely identify the UE over the F1 interface within a gNB-CU. When a gNB-DU receives a gNB-CU UE F1AP ID it shall store it for the duration of the UE-associated logical F1-connection for this UE. The gNB-CU UE F1AP ID shall be unique within the gNB-CU logical node. gNB-DU UE F1AP ID: A gNB-DU UE F1AP ID shall be allocated so as to uniquely identify the UE over the F1 interface within a gNB-DU. When a gNB-CU receives a gNB-DU UE F1AP ID it shall store it for the duration of the UE-associated logical F1-connection for this UE. The gNB-DU UE F1AP ID shall be unique within the gNB-DU logical node. gNB-CU-CP UE E1AP ID: A gNB-CU-CP UE E1AP ID shall be allocated so as to uniquely identify the UE over the E1 interface within a gNB-CU-CP (respectively an ng-eNB-CU-CP, or an eNB-CP as defined in TS 36.401[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description ] [28]). When a gNB-CU-UP (respectively an ng-eNB-CU-UP, or an eNB-UP as defined in TS 36.401[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description ] [28]) receives a gNB-CU-CP UE E1AP ID it shall store it for the duration of the UE-associated logical E1-connection for this UE. The gNB-CU-CP UE E1AP ID shall be unique within the gNB-CU-CP (respectively the ng-eNB-CU-CP, or the eNB-CP as defined in TS 36.401[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description ] [28]) logical node. gNB-CU-UP UE E1AP ID: A gNB-CU-UP UE E1AP ID shall be allocated so as to uniquely identify the UE over the E1 interface within a gNB-CU-UP (respectively an ng-eNB-CU-UP, or an eNB-UP as defined in TS 36.401[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description ] [28]). When a gNB-CU-CP (respectively an ng-eNB-CU-CP, or an eNB-CP as defined in TS 36.401[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description ] [28]) receives a gNB-CU-UP UE E1AP ID it shall store it for the duration of the UE-associated logical E1-connection for this UE. The gNB-CU-UP UE E1AP ID shall be unique within the gNB-CU-UP (respectively the ng-eNB-CU-UP, or the eNB-UP as defined in TS 36.401[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Architecture description ] [28]) logical node. ng-eNB-CU UE W1AP ID: An ng-eNB-CU UE W1AP ID shall be allocated so as to uniquely identify the UE over the W1 interface within an ng-eNB-CU. When an ng-eNB-DU receives an ng-eNB-CU UE W1AP ID it shall store it for the duration of the UE-associated logical W1-connection for this UE. The ng-eNB-CU UE W1AP ID shall be unique within the ng-eNB-CU logical node. ng-eNB-DU UE W1AP ID: An ng-eNB-DU UE W1AP ID shall be allocated so as to uniquely identify the UE over the W1 interface within an ng-eNB-DU. When an ng-eNB-CU receives an ng-eNB-DU UE W1AP ID it shall store it for the duration of the UE-associated logical W1-connection for this UE. The ng-eNB-DU UE W1AP ID shall be unique within the ng-eNB-DU logical node. gNB-CU MBS F1AP ID: A gNB-CU MBS F1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the F1 interface within a gNB-CU. When a gNB-DU receives a gNB-CU MBS F1AP ID it shall store it for the duration of the MBS-associated logical F1-connection for that MBS Session. The gNB-CU MBS F1AP ID shall be unique within the gNB-CU logical node. gNB-DU MBS F1AP ID: A gNB-DU MBS F1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the F1 interface within a gNB-DU. When a gNB-CU receives a gNB-DU MBS F1AP ID it shall store it for the duration of the MBS-associated logical F1-connection for this MBS Session. The gNB-DU MBS F1AP ID shall be unique within the gNB-DU logical node. gNB-CU-CP MBS E1AP ID: A gNB-CU-CP MBS E1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the E1 interface within a gNB-CU-CP. When a gNB-CU-UP receives a gNB-CU-CP MBS E1AP ID it shall store it for the duration of the MBS-associated logical E1-connection for that MBS Session. The gNB-CU-CP MBS E1AP ID shall be unique within the gNB-CU-CP logical node. gNB-CU-UP MBS E1AP ID: A gNB-CU-UP MBS E1AP ID shall be allocated so as to uniquely identify the MBS Session Context over the E1 interface within a gNB-CU-UP. When a gNB-CU-CP receives a gNB-CU-UP MBS E1AP ID it shall store it for the duration of the MBS-associated logical E1-connection for this MBS Session. The gNB-CU-UP MBS E1AP ID shall be unique within the gNB-CU-UP logical node. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.2.1 |
2,040 | 5.2.3.2.5 PLMN-SEARCH | The UE shall perform PLMN selection or SNPN selection. If a new PLMN is selected, the UE shall reset the registration attempt counter and initiate a registration procedure for mobility and periodic registration update (see subclause 5.5.1.3). If a new SNPN is selected, the UE shall reset the registration attempt counter and initiate a mobility registration update if the UE supports access to an SNPN using credentials from a credentials holder or when the SNPNs are equivalent SNPNs or both (see subclause 4.14.2) and the last registered SNPN and the newly selected SNPN are both identified by globally-unique SNPN identities. Otherwise the UE, may perform de-registration locally and shall initiate a registration procedure for initial registration (see subclause 5.5.1.2.2).If the selected cell in the new PLMN is known not to be able to provide normal service, the UE may perform de-registration locally and initiate an initial registration for emergency services. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.2.5 |
2,041 | 16.1 RADIUS Authentication and Authorization | RADIUS Authentication and Authorization shall be used according to RFC 2865 [38], RFC 3162 [50] and RFC 4818 [97]. The RADIUS client function may reside in a GGSN/P-GW. When the GGSN receives a Create PDP Context request message or the P-GW receives an initial access request (e.g. Create Session Request) the RADIUS client function may send the authentication information to an authentication server, which is identified during the APN provisioning. The authentication server checks that the user can be accepted. The response (when positive) may contain network information, such as an IPv4 address and/or IPv6 prefix for the user when the GGSN or P-GW is interworking with the AAA server. The information delivered during the RADIUS authentication can be used to automatically correlate the users identity (the MSISDN or IMSI) to the IPv4 address and/or IPv6 prefix, if applicable, assigned/confirmed by the GGSN/P-GW or the authentication server respectively. The same procedure applies, in case of sending the authentication to a ‘proxy’ authentication server. RADIUS Authentication is only applicable to the primary PDP context. When the GGSN receives an Access-Accept message from the authentication server it shall complete the PDP context activation procedure. If Access-Reject or no response is received, the GGSN shall reject the PDP Context Activation attempt with a suitable cause code, e.g. User Authentication failed. The GGSN may also use the RADIUS re-authorization procedure for the purpose of IPv4 address allocation to the MS for PDP type of IPv4v6 after establishment of a PDN connection. For EPS, RADIUS Authentication is applicable to the initial access request. When the P-GW receives an Access-Accept message from the authentication server it shall complete the initial access procedure. If Access-Reject or no response is received, the P-GW shall reject the initial access procedure with a suitable cause code. The P-GW may also use the RADIUS re-authorization procedure for the purpose of IPv4 address allocation to the UE for PDN type of IPv4v6 after establishment of a PDN connection. The use cases that may lead this procedure are: - Deferred IPv4 address allocation via DHCPv4 procedure after successful attach on 3GPP accesses. - Deferred IPv4 address allocation after successful attach in trusted non-3GPP IP access on S2a. - Deferred IPv4 home address allocation via DSMIPv6 Re-Registration procedure via S2c. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16.1 |
2,042 | 4.5.2A Determination of the access identities and access category associated with a request for access for UEs operating in SNPN access operation mode over 3GPP access | When the UE needs to initiate an access attempt in one of the events listed in subclause 4.5.1, the UE shall determine one or more access identities from the set of standardized access identities, and one access category from the set of standardized access categories and operator-defined access categories, to be associated with that access attempt. The set of the access identities applicable for the request is determined by the UE in the following way: a) for each of the access identities 1, 2, 11, 12, 13, 14 and 15 in table 4.5.2A.1, the UE shall check whether the access identity is applicable in the selected SNPN, if a new SNPN is selected, or otherwise if it is applicable in the RSNPN or equivalent SNPN; and b) if none of the above access identities is applicable, then access identity 0 is applicable. Table 4.5.2A.1: Access identities The contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), if the PLMN subscription is selected, and the rules specified in table 4.5.2A.1 are used to determine the applicability of access identity 1 in the SNPN. When the contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), if the PLMN subscription is selected, do not indicate the UE is configured for access identity 1 for the SNPN, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message and the MPS indicator bit of the Priority indicator IE in the CONFIGURATION UPDATE COMMAND message to determine if access identity 1 is valid. The contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), if the PLMN subscription is selected, and the rules specified in table 4.5.2A.1 are used to determine the applicability of access identity 2 in the SNPN. When the contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), if the PLMN subscription is selected, do not indicate the UE is configured for access identity 2 for the SNPN, the UE uses the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 2 is valid. The contents of the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), if an entry of "list of subscriber data" is selected, or in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), if the PLMN subscription is selected, and the rules specified in table 4.5.2A.1 are used to determine the applicability of access classes 11 to 15 in the SNPN. In order to determine the access category applicable for the access attempt, the NAS shall check the rules in table 4.5.2A.2, and use the access category for which there is a match for barring check. If the access attempt matches more than one rule, the access category of the lowest rule number shall be selected. If the access attempt matches more than one operator-defined access category definition, the UE shall select the access category from the operator-defined access category definition with the lowest precedence value (see subclause 4.5.3). NOTE: The case when an access attempt matches more than one rule includes the case when multiple events trigger an access attempt at the same time. When multiple events trigger an access attempt at the same time, how the access attempt is checked for multiple events is up to UE implementation. Table 4.5.2A.2: Mapping table for access categories | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.2A |
2,043 | 5.5.1.4 Sequence hopping | Sequence hopping only applies for reference-signals of length . For reference-signals of length , the base sequence number within the base sequence group is given by . For reference-signals of length , the base sequence number within the base sequence group in slot is defined by where the pseudo-random sequence is given by clause 7.2. The parameter Sequence-hopping-enabled provided by higher layers determines if sequence hopping is enabled or not. Sequence hopping for PUSCH can be disabled for a certain UE through the higher-layer parameter Disable-sequence-group-hopping despite being enabled on a cell basis unless the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure. For PUSCH or SPUCCH/PUCCH format 4 transmission with ≥ 6 RBs, the pseudo-random sequence generator shall be initialized with at the beginning of each radio frame where is given by clause 5.5.1.5. For SRS, the pseudo-random sequence generator shall be initialized with at the beginning of each radio frame where is given by clause 5.5.1.5 and is given by clause 5.5.1.3. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.1.4 |
2,044 | 9.11.2.13 Service-level-AA payload | The purpose of the Service-level-AA payload information element is to carry the upper layer payload for authentication and authorization between the UE and the service-level-AA server. The Service-level-AA payload information element is coded as shown in figure 9.11.2.13.1 and table 9.11.2.13.1. The Service-level-AA payload information element is a type 6 information element with minimum length of 4 octets and maximum length of 65538 octets. Figure 9.11.2.13.1: Service-level-AA payload information element Table 9.11.2.13.1: Service-level-AA payload information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.2.13 |
2,045 | 24.3B ProSe Application Code Suffix | The ProSe Application Code Suffix as described in 3GPP TS 23.303[ Proximity-based services (ProSe); Stage 2 ] [103] is an identifier to be appended to a ProSe Application Code Prefix. The ProSe Application Code Suffix is of variable length. The length of the ProSe Application Code Suffix shall be incremented in multiple of 8, with a minimum size of 8 bits and a maximum size of 152 bits. The sum of the length of the ProSe Application Code Prefix and the length of the ProSe Application Code Suffix shall be 184 bits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.3B |
2,046 | 4.23.5.1 PDU Session establishment procedure | For non roaming or LBO roaming, it includes the following cases: - If the service area of the selected SMF includes the current UE location, the UE requested PDU Session Establishment procedure is same as described in clause 4.3.2.2.1. - If the service area of the selected SMF does not include the current UE location and the UE does not request for a MA PDU Session, the AMF selects an I-SMF that serves the area where UE camps. The UE requested PDU Session Establishment procedure for Home-routed Roaming defined in clause 4.3.2.2.2 is used to establish the PDU Session. Compared to the procedure defined in clause 4.3.2.2.2, the V-SMF and V-UPF are replaced by I-SMF and I-UPF and H-SMF and H-UPF are replaced by SMF and UPF(PSA) respectively. Also, only the S-NSSAI with the value defined by the serving PLMN is sent to the SMF. The I-SMF provides the DNAI list it supports to SMF and the SMF provides the DNAI(s) of interest for this PDU Session to I-SMF based on the DNAI list information received from I-SMF as defined in Figure 4.23.9.1-1 step 1. This may happen e.g. at PDU Session mobility from non-3GPP access to 3GPP access as defined in clause 4.23.15. - If the service area of the selected SMF does not include the current UE location and the UE requests a MA PDU Session, then the AMF rejects the MA PDU Session Establishment procedure. - When the delegated discovery is used, the SCP selects the SMF as described in Annex E. - If an I-SMF is selected and the PDU Session supports mechanisms for redundant transmission defined in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF rejects the PDU Session Establishment Request. - If an I-SMF is selected and the PDU Session supports Time Sensitive Communications (as defined in clauses 5.27 and 5.28 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), or if the PDU session supports redundant transmission defined in clauses 5.33.2.1 or 5.33.2.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF may, based on local policy, reject the PDU Session Establishment Request. - If the selected SMF cannot serve the target DNAI requested by the PCC rule, the SMF issues Nsmf_PDUSession_SMContextStatusNotify to provide the target DNAI information to the AMF. The procedure of Home-routed Roaming defined in clause 4.3.2.2.2 is used to establish the PDU Session. Compared to this procedure, the V-SMF and V-UPF are replaced by I-SMF and I-UPF respectively and H-SMF and H-UPF are replaced by SMF and UPF(PSA) respectively. The AMF selects an I-SMF that serves this target DNAI in step 2. Then AMF sends a Nsmf_PDUSession_CreateSMContext Request to the I-SMF as defined in step 3a and the target DNAI received from SMF is included in the message. - The S-NSSAI registered to UDM by SMF is always the S-NSSAI of HPLMN. For the Home-Routed roaming case, the UE requested PDU Session Establishment procedure for Home-routed Roaming in clause 4.3.2.2.2 can be reused with the following change. - If the service area of the selected V-SMF does not include the current UE location and the UE requests a MA PDU Session, then the AMF rejects the MA PDU Session Establishment procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.5.1 |
2,047 | – LTM-Config | The IE LTM-Config is used to provide LTM candidate configurations. LTM-Config information element -- ASN1START -- TAG-LTM-CONFIG-START LTM-Config-r18 ::= SEQUENCE { ltm-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need M ltm-CandidateToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-CandidateId-r18 OPTIONAL, -- Need N ltm-CandidateToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-Candidate-r18 OPTIONAL, -- Need N ltm-ServingCellNoResetID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Cond FirstLTM-Only ltm-CSI-ResourceConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfig-r18 OPTIONAL, -- Need N ltm-CSI-ResourceConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfigId-r18 OPTIONAL, -- Need N attemptLTM-Switch-r18 ENUMERATED {true} OPTIONAL, -- Cond LTM-MCG ltm-ServingCellUE-MeasuredTA-ID-r18 INTEGER (1..maxNrofLTM-Configs-r18-plus-1) OPTIONAL, -- Cond LTM ... } -- TAG-LTM-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,048 | 7.2.3.2 Wireless road-side infrastructure backhaul | Intelligent Transport Systems embrace a wide variety of communications-related applications that are intended to increase travel safety, minimize environmental impact, improve traffic management, and maximize the benefits of transportation to both commercial users and the general public. Road-side infrastructure such as traffic light controllers, roadside units, traffic monitoring in urban areas and along highways and streets is wirelessly connected to traffic control centres for management and control purposes. The backhaul communication between the road-side infrastructure and the traffic control centre requires low-latency, high communication service availability, and high-capacity connections for reliable distribution of data. Road-side infrastructure is deployed alongside streets in urban areas and alongside major roads and highways every 1-2 km. For more information about infrastructure backhaul, see clause D.5. To support wireless road-side infrastructure backhaul the 5G system shall support the performance requirements in table 7.2.3.2-1. Table 7.2.3.2-1 Performance requirements for wireless ITS infrastructure backhaul scenario | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.2.3.2 |
2,049 | A.3.2 High-level message structure | Within each logical channel type, the associated RRC PDU (message) types are alternatives within a CHOICE, as shown in the example below. -- /example/ ASN1START DL-DCCH-Message ::= SEQUENCE { message DL-DCCH-MessageType } DL-DCCH-MessageType ::= CHOICE { c1 CHOICE { dlInformationTransfer DLInformationTransfer, handoverFromEUTRAPreparationRequest HandoverFromEUTRAPreparationRequest, mobilityFromEUTRACommand MobilityFromEUTRACommand, rrcConnectionReconfiguration RRCConnectionReconfiguration, rrcConnectionRelease RRCConnectionRelease, securityModeCommand SecurityModeCommand, ueCapabilityEnquiry UECapabilityEnquiry, spare1 NULL }, messageClassExtension SEQUENCE {} } -- ASN1STOP A nested two-level CHOICE structure is used, where the alternative PDU types are alternatives within the inner level c1 CHOICE. Spare alternatives (i.e., spare1 in this case) may be included within the c1 CHOICE to facilitate future extension. The number of such spare alternatives should not extend the total number of alternatives beyond an integer-power-of-two number of alternatives (i.e., eight in this case). Further extension of the number of alternative PDU types is facilitated using the messageClassExtension alternative in the outer level CHOICE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.2 |
2,050 | 6.5.1 RRC integrity mechanisms | RRC integrity protection shall be provided by the PDCP layer between UE and gNB and no layers below PDCP shall be integrity protected. Replay protection shall be activated when integrity protection is activated (except for when the selected integrity protection algorithm is NIA0, see Annex D). Replay protection shall ensure that the receiver accepts each particular incoming PDCP COUNT value only once using the same AS security context. The use and mode of operation of the 128-NIA algorithms are specified in Annex D. The input parameters to the 128-bit NIA algorithms as described in Annex D are the RRC message as MESSAGE, an 128-bit integrity key KRRCint as KEY, a 5-bit bearer identity BEARER which value is assigned as specified by TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [23], the 1-bit direction of transmission DIRECTION and a bearer specific direction dependent 32-bit input COUNT which corresponds to the 32-bit PDCP COUNT. The RRC integrity checks shall be performed both in the ME and the gNB. In case failed integrity check (i.e. faulty or missing MAC-I) is detected after the start of integrity protection, the concerned message shall be discarded. This can happen on the gNB side or on the ME side. UE may trigger a recovery procedure as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22]. NOTE: Failed integrity check does not always imply that the concerned message is silently discarded. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.1 |
2,051 | 4.3.1.1 TMSI reallocation initiation by the network | The network initiates the TMSI reallocation procedure by sending a TMSI REALLOCATION COMMAND message to the mobile station and starts the timer T3250. The TMSI REALLOCATION COMMAND message contains a new combination of TMSI and LAI allocated by the network or a LAI and the IMSI if the used TMSI shall be deleted. Usually the TMSI-REALLOCATION COMMAND message is sent to the mobile station using a RR connection in ciphered mode (see 3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.1.1 |
2,052 | B.3 NR Operation with Shared Spectrum | NR Radio Access operating with shared spectrum channel access can support the following deployment scenarios: - Scenario A: Carrier aggregation between NR in licensed spectrum (SpCell) and NR in shared spectrum (SCell); - Scenario A.1: SCell is not configured with uplink (DL only); - Scenario A.2: SCell is configured with uplink (DL+UL). - Scenario B: Dual connectivity between LTE in licensed spectrum and NR in shared spectrum (PSCell); - Scenario C: NR in shared spectrum (PCell); - Scenario D: NR cell in shared spectrum and uplink in licensed spectrum; - Scenario E: Dual connectivity between NR in licensed spectrum (PCell) and NR in shared spectrum (PSCell). Carrier aggregation of cells in shared spectrum is applicable to all deployment scenarios. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | B.3 |
2,053 | 5.6.6 Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session | At PDU Session Establishment to a DN: - The DN-specific identity (TS 33.501[ Security architecture and procedures for 5G System ] [29]) of a UE may be authenticated/authorized by the DN. NOTE 1: the DN-AAA server may belong to the 5GC or to the DN. - If the UE provides authentication/authorization information corresponding to a DN-specific identity during the Establishment of the PDU Session, and the SMF determines that Secondary authentication/authorization of the PDU Session Establishment is required based on the SMF policy associated with the DN, the SMF passes the authentication/authorization information of the UE to the DN-AAA server via the UPF if the DN-AAA server is located in the DN. If the SMF determines that Secondary authentication/authorization of the PDU Session Establishment is required but the UE has not provided a DN-specific identity as part of the PDU Session Establishment request, the SMF requests the UE to indicate a DN-specific identity using EAP procedures as described in TS 33.501[ Security architecture and procedures for 5G System ] [29]. If the Secondary authentication/authorization of the PDU Session Establishment fails, the SMF rejects the PDU Session Establishment. NOTE 2: If the DN-AAA server is located in the 5GC and reachable directly, then the SMF may communicate with it directly without involving the UPF. - The DN-AAA server may authenticate/authorize the PDU Session Establishment. - When DN-AAA server authorizes the PDU Session Establishment, it may send DN Authorization Data for the established PDU Session to the SMF. The DN authorization data for the established PDU Session may include one or more of the following: - A DN Authorization Profile Index which is a reference to authorization data for policy and charging control locally configured in the SMF or PCF. - a list of allowed MAC addresses for the PDU Session; this shall apply only for PDU Session of Ethernet PDU type and is further described in clause 5.6.10.2. - a list of allowed VLAN tags for the PDU Session; this shall apply only for PDU Session of Ethernet PDU type and is further described in clause 5.6.10.2. - DN authorized Session AMBR for the PDU Session. The DN Authorized Session AMBR for the PDU Session takes precedence over the subscribed Session-AMBR received from the UDM. - Framed Route information (see clause 5.6.14) for the PDU Session. - L2TP information, such as LNS IP address and/or LNS host name, as described in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [132]. SMF policies may require DN authorization without Secondary authentication/authorization. In that case, when contacting the DN-AAA server for authorization, the SMF provides the GPSI of the UE if available. Such Secondary authentication/authorization takes place for the purpose of PDU Session authorization in addition to: - The 5GC access authentication handled by AMF and described in clause 5.2. - The PDU Session authorization enforced by SMF with regards to subscription data retrieved from UDM. Based on local policies the SMF may initiate Secondary authentication/authorization at PDU Session Establishment. The SMF provides the GPSI, if available, in the signalling exchanged with the DN-AAA during Secondary authentication/authorization. After the successful Secondary authentication/authorization, a session is kept between the SMF and the DN-AAA. The UE provides the authentication/authorization information required to support Secondary authentication/authorization by the DN over NAS SM. If a UE is configured with DNNs, which are subject to secondary authentication/authorization, the UE stores an association between the DNN and corresponding credentials for the secondary authentication/authorization. NOTE 3: How the UE is aware that a DNN is subject to secondary authentication/authorization (e.g. based on local configuration) is out of scope of this specification. The UE may support remote provisioning of credentials for secondary authentication/authorization, as specified in clause 5.39. A UE that supports to be provisioned with the credentials used for secondary authentication/authorization over UP remote provisioning shall use connectivity over an S-NSSAI/DNN which can access the provisioning server to establish a PDU session for remote provisioning as defined in clause 5.39. NOTE 4: The credentials for secondary authentication/authorization are not specified. SMF policies or subscription information (such as defined in Table 5.2.3.3.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) may trigger the need for SMF to request the Secondary authentication/authorization and/or UE IP address / Prefix from the DN-AAA server. When SMF adds a PDU Session Anchor (such as defined in clause 5.6.4) to a PDU Session Secondary authentication/authorization is not carried out, but SMF policies may require SMF to notify the DN when a new prefix or address has been added to or removed from a PDU Session or N6 traffic routing information has been changed for a PDU Session. When SMF gets notified from UPF with the addition or removal of MAC addresses to/from a PDU Session, the SMF policies may require SMF to notify the DN-AAA server. Indication of PDU Session Establishment rejection is transferred by SMF to the UE via NAS SM. If the DN-AAA sends DN Authorization Data for the authorized PDU Session to the SMF and dynamic PCC is deployed, the SMF sends the PCF the DN authorized Session AMBR and/or DN Authorization Profile Index in the DN Authorization Data for the established PDU Session. If the DN-AAA sends DN Authorization Profile Index in DN Authorization Data to the SMF and dynamic PCC is not deployed, the SMF uses the DN Authorization Profile Index to refer the locally configured information. NOTE 5: DN Authorization Profile Index is assumed to be pre-negotiated between the operator and the administrator of DN-AAA server. If the DN-AAA does not send DN Authorization Data for the established PDU Session, the SMF may use locally configured information. At any time, a DN-AAA server may revoke the authorization for a PDU Session or update DN Authorization Data for a PDU Session. According to the request from DN-AAA server, the SMF may release or update the PDU Session. See clause 5.6.14 when the update involves Framed Route information. At any time, a DN-AAA server or SMF may trigger Secondary Re-authentication procedure for a PDU Session established with Secondary Authentication as specified in clause 11.1.3 of TS 33.501[ Security architecture and procedures for 5G System ] [29]. During Secondary Re-authentication/Re-authorization, if the SMF receives from DN-AAA the DN authorized Session AMBR and/or DN Authorization Profile Index, the SMF shall report the received value(s) to the PCF. The procedure for secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session is described in clause 4.3.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The support for L2TP on N6 is further specified in clause 5.8.2.16, and the procedure for establishment of L2TP tunnelling on N6 for a PDU Session is described in clause 4.3.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 6: The L2TP Tunnel information sent to the SMF can, for example, be provisioned in the DN-AAA server per DNN/S-NSSAI or per SUPI or GPSI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.6 |
2,054 | – EUTRA-MultiBandInfoListAerial | The IE EUTRA-MultiBandInfoListAerial indicates the list of frequency bands for aerial UE in addition to the band represented by CarrierFreq for which cell reselection parameters are common, and a list of additionalPmax and additionalSpectrumEmission. EUTRA-MultiBandInfoListAerial information element -- ASN1START -- TAG-EUTRA-MULTIBANDINFOLISTAERIAL-START EUTRA-MultiBandInfoListAerial-r18 ::= SEQUENCE (SIZE (1..maxMultiBands)) OF EUTRA-MultiBandInfoAerial-r18 EUTRA-MultiBandInfoAerial-r18 ::= SEQUENCE { eutra-FreqBandIndicator-r18 FreqBandIndicatorEUTRA, eutra-NS-PmaxListAerial-r18 EUTRA-NS-PmaxList OPTIONAL -- Need R } -- TAG-EUTRA-MULTIBANDINFOLISTAERIAL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,055 | – UplinkConfigCommon | The IE UplinkConfigCommon provides common uplink parameters of a cell. UplinkConfigCommon information element -- ASN1START -- TAG-UPLINKCONFIGCOMMON-START UplinkConfigCommon ::= SEQUENCE { frequencyInfoUL FrequencyInfoUL OPTIONAL, -- Cond InterFreqHOAndServCellAdd initialUplinkBWP BWP-UplinkCommon OPTIONAL, -- Cond ServCellAdd dummy TimeAlignmentTimer } UplinkConfigCommon-v1700 ::= SEQUENCE { initialUplinkBWP-RedCap-r17 BWP-UplinkCommon OPTIONAL -- Need R } -- TAG-UPLINKCONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,056 | 6.2.28 NSACF | The Network Slice Admission Control Function (NSACF) supports the following functionality: - Support of monitoring and controlling the number of registered UEs per network slice. - Support of monitoring and controlling the number of UEs with at least one PDU Session/PDN Connection per network slice in case of EPC interworking. - Support of monitoring and controlling the number of established PDU Sessions per network slice. - Support of event based Network Slice status notification and reports to a consumer NF. - Acting as a Centralized NSACF in PLMNs deploying a centralized architecture as described in clause 5.15.11.0. - Support of different type of NSAC modes for roaming UEs for the number of UEs per network slice. - Support of different type of NSAC modes for roaming UEs for the number of PDU Sessions per network slice. - Acting as a Primary NSACF in PLMNs deploying a hierarchal architecture as described in clause 5.15.11.0. The details of the NSACF functionality are defined in clause 5.15.11. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.28 |
2,057 | 7.2.2 Scenarios and KPIs | Different deployments of URLLC capabilities will depend on the 3GPP system being able to meet specific sets of KPIs with different values and ranges applicable for each attribute. A common, yet flexible, 5G approach to URLLC will enable the 5G system to meet the specific sets of KPIs needed in a given implementation. To provide clear and precise requirements for specific types of services, the corresponding KPI requirements are included in other specifications as follows: - Cyber-physical control applications in vertical domains can be found in 22.104 [21]. - V2X can be found in 22.186 [9]. - Rail communications can be found in 22.289 [23]. Some scenarios requiring very low latency and very high communication service availability are described below: - Motion control – Conventional motion control is characterised by high requirements on the communications system regarding latency, reliability, and availability. Systems supporting motion control are usually deployed in geographically limited areas but can also be deployed in wider areas (e.g. city- or country-wide networks), access to them can be limited to authorized users, and they can be isolated from networks or network resources used by other cellular customers. - Discrete automation – Discrete automation is characterised by high requirements on the communications system regarding reliability and availability. Systems supporting discrete automation are usually deployed in geographically limited areas, access to them can be limited to authorized users, and they can be isolated from networks or network resources used by other cellular customers. - Process automation – Automation for (reactive) flows, e.g. refineries and water distribution networks. Process automation is characterized by high requirements on the communications system regarding communication service availability. Systems supporting process automation are usually deployed in geographically limited areas, access to them is usually limited to authorized users, and it will usually be served by non-public networks. - Automation for electricity distribution and smart grid (mainly medium and high voltage). Electricity distribution and smart grid are is characterized by high requirements on the communications service availability and security, as well as low latency in some cases. In contrast to the above use cases, electricity distribution and smart grid are deeply immersed into the public space. Since electricity distribution is an essential infrastructure, it is well served by network slices to provide service isolation and security, or by non-public networks. - Wireless road-side infrastructure backhaul in intelligent transport systems – Automation solutions for the infrastructure supporting street-based traffic. This use case addresses the connection of the road-side infrastructure, e.g. roadside units, with other infrastructure, e.g. a traffic guidance system. As is the case for automation electricity, the nodes are deeply immersed into the public space. - Remote control – Remote control is characterised by a UE being operated remotely by a human or a computer. For example, Remote Driving enables a remote driver or a V2X application to operate a remote vehicle with no driver or a remote vehicle located in a dangerous environment. - Rail communications (e.g. railway, rail-bound mass transit) have been using 3GPP based mobile communication (e.g. GSM-R) already for some time, while there is still a driver on-board of the train. The next step of the evolution will be providing fully automated train operation that requires highly reliable communication with moderate latencies but at very high speeds of up to 500 km/h. For specific requirements, refer to the specifications noted above [21], [9], [23]. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.2.2 |
2,058 | 5.8.2.9.1 UPF Constructing the "End marker" Packets | In the case of inter NG-RAN Handover procedure without UPF change, SMF shall indicate the UPF to switch the N3 path(s) by sending an N4 Session Modification Request message with the new AN Tunnel Info of NG RAN and in addition, provide an indication to the UPF to send the end marker packet(s) on the old N3 user plane path. On receiving this indication, the UPF shall construct end marker packet(s) and send it for each N3 GTP-U tunnel towards the source NG RAN after sending the last PDU on the old path. In the case of inter NG-RAN Handover procedure with change of the UPF terminating N3, the SMF shall request the UPF with N9 reference point to the UPF terminating N3 to switch the N9 user plane path(s) by sending an N4 Session Modification Request message (N4 session ID, new CN Tunnel Info of the UPF terminating N3) and in addition, provide an indication to this UPF to send the end marker packet(s) on the old path. On receiving this indication, the UPF shall construct end marker packet(s) and send it for each N9 GTP-U tunnel towards the source UPF after sending the last PDU on the old path. On receiving the end marker packet(s) on N9 GTP-U tunnel, source UPF shall forward the end marker packet(s) and send it for each N3 GTP-U tunnel towards the source NG RAN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.9.1 |
2,059 | 7.6.3.1 Minimum requirements | The relative throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Table 7.6.3.1-1. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements only apply for carriers assigned in the paired part. Table 7.6.3.1-1: Narrow-band blocking For the UE which supports inter-band CA configuration in Table 7.3.1-1A, PUW power defined in Table 7.6.3.1-1 is increased by the amount given by ΔRIB,c in Table 7.3.1-1A. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.3.1 |
2,060 | – SL-L2RemoteUE-Config | The IE SL-L2RemoteUE-Config is used to configure L2 U2N relay operation related configurations used by L2 U2N Remote UE, or L2 U2U relay operation related configurations used by L2 U2U Remote UE. SL-L2RemoteUE-Config information element -- ASN1START -- TAG-SL-L2REMOTEUE-CONFIG-START SL-L2RemoteUE-Config-r17 ::= SEQUENCE { sl-SRAP-ConfigRemote-r17 SL-SRAP-Config-r17 OPTIONAL, --Need M sl-UEIdentityRemote-r17 RNTI-Value OPTIONAL, -- Cond FirstRRCReconfig ..., [[ sl-U2U-RelayUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-U2U-RelayUE-ToAddMod-r18 OPTIONAL, -- Need N sl-U2U-RelayUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL -- Need N ]] } SL-U2U-RelayUE-ToAddMod-r18 ::= SEQUENCE { sl-L2IdentityRelay-r18 SL-DestinationIdentity-r16, sl-PeerRemoteUE-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-PeerRemoteUE-ToAddMod-r18 OPTIONAL, -- Need N sl-PeerRemoteUE-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16 OPTIONAL, -- Need N ... } SL-PeerRemoteUE-ToAddMod-r18 ::= SEQUENCE { sl-TargetUE-Identity-r18 SL-DestinationIdentity-r16, sl-SRAP-ConfigU2U-r18 SL-SRAP-ConfigU2U-r18, ... } -- TAG-SL-L2REMOTEUE-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,061 | – SupportedBandwidth | The IE SupportedBandwidth is used to indicate the channel bandwidth supported by the UE on one carrier of a band of a band combination. SupportedBandwidth information element -- ASN1START -- TAG-SUPPORTEDBANDWIDTH-START SupportedBandwidth ::= CHOICE { fr1 ENUMERATED {mhz5, mhz10, mhz15, mhz20, mhz25, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100}, fr2 ENUMERATED {mhz50, mhz100, mhz200, mhz400} } SupportedBandwidth-v1700 ::= CHOICE { fr1-r17 ENUMERATED {mhz5, mhz10, mhz15, mhz20, mhz25, mhz30, mhz35, mhz40, mhz45, mhz50, mhz60, mhz70, mhz80, mhz90, mhz100}, fr2-r17 ENUMERATED {mhz50, mhz100, mhz200, mhz400, mhz800, mhz1600, mhz2000} } -- TAG-SUPPORTEDBANDWIDTH-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,062 | – SIB25 | SIB25 contains TN coverage information to assist neighbour cell measurements for the UEs in an NTN cell. SIB25 information element -- ASN1START -- TAG-SIB25-START SIB25-r18 ::= SEQUENCE { coverageAreaInfoList-r18 CoverageAreaInfoList-r18 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } CoverageAreaInfoList-r18 ::= SEQUENCE (SIZE (1..maxTN-AreaInfo-r18)) OF CoverageAreaInfo-r18 CoverageAreaInfo-r18 ::= SEQUENCE { tn-AreaId-r18 TN-AreaId-r18, tn-ReferenceLocation-r18 ReferenceLocation-r17, tn-DistanceRadius-r18 INTEGER(0..65536) } -- TAG-SIB25-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,063 | 10.11.1 EN-DC | The secondary RAT data volume reporting function is used to report the data volume of secondary RAT to CN. In EN-DC, if configured, the MN reports the uplink and downlink data volumes of used NR resources to the EPC on a per EPS bearer basis as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]. Periodic reporting is performed by periodically sending the Secondary RAT Data Usage Report messages to the MME. The data volume is counted by the node hosting PDCP. Downlink data volume is counted in bytes of PDCP SDUs successfully delivered to the UE over NR (for RLC AM) or transmitted to the UE over NR (for RLC UM). Uplink data volume is counted in bytes of PDCP SDUs received by the node hosting PDCP over NR. Forwarded packets shall not be counted when PDCP entity is relocated. When PDCP duplication is activated, packets shall be counted only once. Figure 10.11.1-1: Secondary RAT data volume periodic reporting - EN-DC Figure 10.11.1-1 shows an example signalling flow for secondary RAT data volume periodic reporting: 1. If the periodic reporting is configured, then the SN periodically sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes of used NR radio resources for the related SN-terminated E-RABs. 2. The MN sends the Secondary RAT Data Usage Report message to MME to provide information on the used NR resource. NOTE: The Secondary RAT Data Usage Report message sent by the MN may also include secondary RAT report information of MN-terminated bearers. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.11.1 |
2,064 | 8.1.2.8A Applicability of performance requirements for UE supporting coverage enhancement | The applicability and test rules are defined for the tests for UE supporting coverage enhancement with narrowband transmission in Table 8.1.2.8A-1 and 8.1.2.8A-2. Table 8.1.2.8A-1: Applicability rules for PDSCH requirements (FDD) Table 8.1.2.8A-2: Applicability rules for PDSCH requirements (TDD) The applicability and test rules are defined for the tests for UE supporting coverage enhancement with wideband transmission in Table 8.1.2.8A-3 and 8.1.2.8A-4. Table 8.1.2.8A-3: Applicability rules for PDSCH requirements (FDD) Table 8.1.2.8A-4: Applicability rules for PDSCH requirements (TDD) The applicability and test rules are defined for the tests for UE supporting coverage enhancement in Tables 8.1.2.8A-5 and 8.1.2.8A-6. Table 8.1.2.8A-5: Applicability rules for PDSCH requirements (FDD) Table 8.1.2.8A-6: Applicability rules for PDSCH requirements (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.1.2.8A |
2,065 | 1.2 Application to the interface structures | The procedures defined in the present document apply to the interface structures defined in 3GPP TS 44.003[ None ] [16] and 3GPP TS 25.301[ None ] [128]. They use the functions and services provided by lower layers defined in 3GPP TS 44.005[ None ] [18] and 3GPP TS 44.006[ None ] [19] or 3GPP TS 25.331[ None ] [23c], 3GPP TS 25.322[ None ] [19b] and 3GPP TS 25.321[ None ] [19a]. 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20] gives the general description of layer 3 (A/Gb mode) and Non Access Stratum (Iu mode and S1 mode) including procedures, messages format and error handling. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 1.2 |
2,066 | 5.2.6.16.4 Nnef_AnalyticsExposure_Notify service operation | Service operation name: Nnef_AnalyticsExposure_Notify Description: NEF reports the analytics to the NF consumer that has previously subscribed. Inputs, Required: Analytics ID(s), Notification Correlation Information, Analytic information (defined on a per Analytics ID basis). These input parameters are detailed in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Inputs, Optional: Timestamp of analytics generation, Probability assertion, Termination Request specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Outputs, Required: Operation execution result indication. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.16.4 |
2,067 | 10.5.6.3.12 PVS name | The purpose of the PVS name container contents is to indicate the fully qualified domain name information and, optionally, the related DNN and S-NSSAI. The PVS name container contents are coded as shown in figure 10.5.6.3.12-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.3.Z-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.6.3.12-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PVS name Table 10.5.6.3.12-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PVS name | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.3.12 |
2,068 | 5.5.1.2.2 S1-based handover, normal | This procedure describes the S1-based handover in the normal case, clause 5.5.1.2.3 describes it when the procedure is rejected by the target eNodeB or the target MME and clause 5.5.1.2.4 describes when the procedure is canceled by the source eNodeB. Figure 5.5.1.2.2-1: S1-based handover NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 16 and 16a concern GTP based S5/S8. NOTE 2: If the Serving GW is not relocated, the box "Source Serving GW" in figure 5.5.1.2.2-1 is acting as the target Serving GW. 1. The source eNodeB decides to initiate an S1-based handover to the target eNodeB. This can be triggered e.g. by no X2 connectivity to the target eNodeB, or by an error indication from the target eNodeB after an unsuccessful X2-based handover, or by dynamic information learnt by the source eNodeB. 2. The source eNodeB sends Handover Required (Direct Forwarding Path Availability, Source to Target transparent container, target eNodeB Identity, CSG ID, CSG access mode, target TAI, S1AP Cause) to the source MME. The source eNodeB indicates which bearers are subject to data forwarding. Direct Forwarding Path Availability indicates whether direct forwarding is available from the source eNodeB to the target eNodeB. This indication from source eNodeB can be based on e.g. the presence of X2. The target TAI is sent to MME to facilitate the selection of a suitable target MME. When the target cell is a CSG cell or a hybrid cell, the source eNodeB shall include the CSG ID of the target cell. If the target cell is a hybrid cell, the CSG access mode shall be indicated. 3. The source MME selects the target MME as described in clause 4.3.8.3 on "MME Selection Function" and if it has determined to relocate the MME, it sends a Forward Relocation Request (MME UE context, Source to Target transparent container, RAN Cause, target eNodeB Identity, CSG ID, CSG Membership Indication, target TAI, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, Direct Forwarding Flag, Serving Network, Local Home Network ID, LTE-M UE Indication) message to the target MME. The target TAI is sent to the target MME to help it to determine whether S-GW relocation is needed (and, if needed, aid SGW selection). The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed. In network sharing scenarios Serving Network denotes the serving core network. The source MME shall perform access control by checking the UE's CSG subscription when CSG ID is provided by the source eNodeB. If there is no subscription data for this CSG ID or the CSG subscription is expired, and the target cell is a CSG cell, the source MME shall reject the handover with an appropriate cause unless the UE has emergency bearer services. The MME UE context includes IMSI, MSISDN, ME Identity, UE security context, UE Network Capability, AMBR, Selected CN operator ID, APN restriction, Serving GW address and TEID for control signalling, and EPS Bearer context(s), UE Radio Capability ID. The MME UE context received from the source MME contains the MSISDN if the MSISDN was available at the source MME. An EPS Bearer context includes the PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, APN, Serving GW addresses and TEIDs for uplink traffic, and TI. Based on the CIoT EPS Optimisation capabilities of the target MME (determined according to the target MME selection procedure of clause 4.3.8.3) the source MME only includes the EPS Bearer Context(s) that the target MME can support. If none of the UE's EPS Bearers can be supported by the selected target MME, the source MME rejects the S1 handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB. If the target MME supports CIoT EPS Optimisation and the use of header compression has been negotiated between the UE and the source MME, the source MME also includes in the Forward Relocation Request the previously negotiated Header Compression Configuration that includes the information necessary for the ROHC channel setup but not the RoHC context itself. If the source MME includes EPS Bearer Context, in addition to the Serving GW IP address and TEID for S1-U use plane, the source MME also includes Serving GW IP address and TEID for S11-U, if available. NOTE 3: If the handover is successful, the source MME will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 14. The non-included bearers are locally released by the UE following the Bearer Context Status synchronisation that occurs during the Tracking Area Update at step 18. If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW the source MME shall include the Local Home Network ID of the source cell in the EPS Bearer context corresponding to the SIPTO at the Local Network PDN connection. RAN Cause indicates the S1AP Cause as received from source eNodeB. The source MME includes the CSG ID in the Forward Relocation Request when the target cell is a CSG or hybrid cell. When the target cell is a hybrid cell, or if there are one or several emergency bearers and the target cell is a CSG cell, the CSG Membership Indication indicating whether the UE is a CSG member shall be included in the Forward Relocation Request message. The Direct Forwarding Flag indicates if direct forwarding is applied, or if indirect forwarding is going to be set up by the source side. The target MME shall determine the Maximum APN restriction based on the APN Restriction of each bearer context in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction value. If the UE receives only emergency services and the UE is UICCless, IMSI can not be included in the MME UE context in Forward Relocation Request message. For emergency attached UEs, if the IMSI cannot be authenticated, then the IMSI shall be marked as unauthenticated. Also, in this case, security parameters are included only if available. If a UE is RLOS attached, the old MME includes an RLOS indication to the new MME. If the RLOS attached UE in the old MME does not have a USIM, IMSI can not be included in the Forward Relocation Request message. If the RLOS attached UE has USIM but the IMSI cannot be successfully authenticated, then the IMSI shall be marked as unauthenticated. Also, in this case, security parameters are included only if available. If the Old MME is aware the UE is a LTE-M UE, it provides the LTE-M UE Indication to the new MME. 4. If the MME has been relocated, the target MME verifies whether the source Serving GW can continue to serve the UE. If not, it selects a new Serving GW as described in clause 4.3.8.2 on "Serving GW Selection Function". If the MME has not been relocated, the source MME decides on this Serving GW re-selection. If the source Serving GW continues to serve the UE, no message is sent in this step. In this case, the target Serving GW is identical to the source Serving GW. If a new Serving GW is selected, the target MME sends a Create Session Request (bearer context(s) with PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, Serving Network, UE Time Zone) message per PDN connection to the target Serving GW. The target Serving GW allocates the S-GW addresses and TEIDs for the uplink traffic on S1_U reference point (one TEID per bearer). The target Serving GW sends a Create Session Response (Serving GW addresses and uplink TEID(s) for user plane) message back to the target MME. 5. The Target MME sends Handover Request (EPS Bearers to Setup, AMBR, S1AP Cause, Source to Target transparent container, CSG ID, CSG Membership Indication, Handover Restriction List, UE Radio Capability ID) message to the target eNodeB. This message creates the UE context in the target eNodeB, including information about the bearers, and the security context. For each EPS Bearer, the Bearers to Setup includes Serving GW address and uplink TEID for user plane, and EPS Bearer QoS. If the direct forwarding flag indicates unavailability of direct forwarding and the target MME knows that there is no indirect data forwarding connectivity between source and target, the Bearers to Setup shall include "Data forwarding not possible" indication for each EPS bearer. Handover Restriction List is sent if available in the Target MME; it is described in clause 4.3.5.7 "Mobility Restrictions". S1AP Cause indicates the RAN Cause as received from source MME. The Target MME shall include the CSG ID and CSG Membership Indication when provided by the source MME in the Forward Relocation Request message. The target eNodeB sends a Handover Request Acknowledge (EPS Bearer Setup list, EPS Bearers failed to setup list Target to Source transparent container) message to the target MME. The EPS Bearer Setup list includes a list of addresses and TEIDs allocated at the target eNodeB for downlink traffic on S1-U reference point (one TEID per bearer) and addresses and TEIDs for receiving forwarded data if necessary. If the UE-AMBR is changed, e.g. all the EPS bearers which are associated to the same APN are rejected in the target eNodeB, the MME shall recalculate the new UE-AMBR and signal the modified UE-AMBR value to the target eNodeB. If none of the default EPS bearers have been accepted by the target eNodeB, the target MME shall reject the handover as specified in clause 5.5.1.2.3. If the target cell is a CSG cell, the target eNodeB shall verify the CSG ID provided by the target MME, and reject the handover with an appropriate cause if it does not match the CSG ID for the target cell. If the target eNodeB is in hybrid mode, it may use the CSG Membership Indication to perform differentiated treatment for CSG and non-CSG members. If the target cell is a CSG cell, and if the CSG Membership Indication is "non member", the target eNodeB only accepts the emergency bearers. If the MME supports RACS as defined in clause 5.11.3a and has UE Radio Capability ID stored in the UE's context it includes it in the Handover Request message, if target eNodeB supports RACS. 6. If indirect forwarding applies and the Serving GW is relocated, the target MME sets up forwarding parameters by sending Create Indirect Data Forwarding Tunnel Request (target eNodeB addresses and TEIDs for forwarding) to the Serving GW. The Serving GW sends a Create Indirect Data Forwarding Tunnel Response (target Serving GW addresses and TEIDs for forwarding) to the target MME. If the Serving GW is not relocated, indirect forwarding may be set up in step 8 below. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 7. If the MME has been relocated, the target MME sends a Forward Relocation Response (Cause, Target to Source transparent container, Serving GW change indication, EPS Bearer Setup List, Addresses and TEIDs) message to the source MME. For indirect forwarding, this message includes Serving GW Address and TEIDs for indirect forwarding (source or target). Serving GW change indication indicates a new Serving GW has been selected. 8. If indirect forwarding applies, the source MME sends Create Indirect Data Forwarding Tunnel Request (addresses and TEIDs for forwarding) to the Serving GW. If the Serving GW is relocated it includes the tunnel identifier to the target serving GW. The Serving GW responds with a Create Indirect Data Forwarding Tunnel Response (Serving GW addresses and TEIDs for forwarding) message to the source MME. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 9. The source MME sends a Handover Command (Target to Source transparent container, Bearers subject to forwarding, Bearers to Release) message to the source eNodeB. The Bearers subject to forwarding includes list of addresses and TEIDs allocated for forwarding. The Bearers to Release includes the list of bearers to be released. 9a. The Handover Command is constructed using the Target to Source transparent container and is sent to the UE. Upon reception of this message the UE will remove any EPS bearers for which it did not receive the corresponding EPS radio bearers in the target cell. 9b. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends a RAN Usage data Report (Secondary RAT usage data, handover flag) message to the source MME. The handover flag indicates to the MME that it should buffer the report before forwarding the Secondary RAT usage data. 10. The source eNodeB sends the eNodeB Status Transfer message to the target eNodeB via the MME(s) to convey the PDCP and HFN status of the E-RABs for which PDCP status preservation applies, as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The source eNodeB may omit sending this message if none of the E-RABs of the UE shall be treated with PDCP status preservation. If there is an MME relocation the source MME sends this information to the target MME via the Forward Access Context Notification message which the target MME acknowledges. The source MME or, if the MME is relocated, the target MME, sends the information to the target eNodeB via the MME Status Transfer message. 11. The source eNodeB should start forwarding of downlink data from the source eNodeB towards the target eNodeB for bearers subject to data forwarding. This may be either direct (step 11a) or indirect forwarding (step 11b). 12. After the UE has successfully synchronized to the target cell, it sends a Handover Confirm message to the target eNodeB. Downlink packets forwarded from the source eNodeB can be sent to the UE. Also, uplink packets can be sent from the UE, which are forwarded to the target Serving GW and on to the PDN GW. 13. The target eNodeB sends a Handover Notify (TAI+ECGI, Local Home Network ID) message to the target MME. If Dual Connectivity is activated for the UE, the PSCell ID shall be included in the Handover Notify message. For SIPTO at the Local Network with stand-alone GW architecture, the target eNodeB shall include the Local Home Network ID of the target cell in the Handover Notify message. 14. If the MME has been relocated, the target MME sends a Forward Relocation Complete Notification message to the source MME. The source MME in response sends a Forward Relocation Complete Acknowledge (Secondary RAT usage data) message to the target MME. The source MME includes Secondary RAT usage data in this message if it received this in step 9b. Regardless if MME has been relocated or not, a timer in source MME is started to supervise when resources in Source eNodeB and if the Serving GW is relocated, also resources in Source Serving GW shall be released. Upon receipt of the Forward Relocation Complete Acknowledge message the target MME starts a timer if the target MME allocated S-GW resources for indirect forwarding. For all bearers that were not included in the Forward Relocation Request message sent in step 3, the MME now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF. 15. The MME sends a Modify Bearer Request (eNodeB address and TEID allocated at the target eNodeB for downlink traffic on S1-U for the accepted EPS bearers, ISR Activated, Secondary RAT usage data if PGW secondary RAT usage data reporting is active, User Location Information, PSCell ID) message to the target Serving GW for each PDN connection, including the PDN connections that need to be released. If the PDN GW requested location information change reporting and/or User CSG information (determined from the UE context), the MME also includes the User Location Information IE (if it is different compared to the previously sent information) and/or User CSG Information IE in this message. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If Serving GW is not relocated but the Serving Network has changed or if the MME has not received any old Serving Network information from the old MME, the MME includes the Serving Network IE in this message. For the case that neither MME nor S-GW changed, if ISR was activated before this procedure MME should maintain ISR. The UE is informed about the ISR status in the Tracking Area Update procedure. If the Serving GW supports Modify Access Bearers Request procedure and if there is no need for the SGW to send the signalling to the PDN GW, the MME may send Modify Access Bearers Request (eNodeB address and TEID allocated at the target eNodeB for downlink traffic on S1 U for the accepted EPS bearers, ISR Activated) per UE to the Serving GW to optimise the signalling. If Serving GW is not relocated and if Secondary RAT usage data was received in step 9a, the MME includes the Secondary RAT usage data in the message. If the Serving GW has been relocated and if PGW Secondary RAT reporting is active, the MME includes the Secondary RAT usage data and also includes a flag stating that the Serving GW should not process the information and only forward it to the PDN GW. If PSCell ID is received in step 13, the MME includes it in Modify Bearer Request message. The MME releases the non-accepted dedicated bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. If the default bearer of a PDN connection has not been accepted by the target eNodeB and there are other PDN connections active, the MME shall handle it in the same way as if all bearers of a PDN connection have not been accepted. The MME releases these PDN connections by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. When the Modify Bearer Request does not indicate ISR Activated the Serving GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the Serving GW reserved. 16. If the Serving GW is relocated, the target Serving GW assigns addresses and TEIDs (one per bearer) for downlink traffic from the PDN GW. It sends a Modify Bearer Request (Serving GW addresses for user plane and TEID(s), Serving Network, PDN Charging Pause Support Indication, Secondary RAT usage data) message per PDN connection to the PDN GW(s). The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 15. The Serving GW also includes Serving Network IE if it is present in step 4 or step 15. The Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers. The PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the target Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. The PDN GW starts sending downlink packets to the target GW using the newly received address and TEIDs. These downlink packets will use the new downlink path via the target Serving GW to the target eNodeB. The Secondary RAT usage data is included if it was received in step 15 and if PGW secondary RAT usage data reporting is active. If the Serving GW is not relocated, but has received the User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE and/or Serving Network IE from the MME in step 15, the Serving GW shall inform the PDN GW(s) about these information that e.g. can be used for charging, by sending the message Modify Bearer Request (User Location Information IE, UE Time Zone IE, User CSG Information IE, Serving Network IE) to the PDN GW(s) concerned. A Modify Bearer Response message is sent back to the Serving GW. If the Serving GW is not relocated and it has not received User Location Information IE nor UE Time Zone IE nor User CSG Information IE nor Serving Network IE from the MME in step 15, no message is sent in this step and downlink packets from the Serving-GW are immediately sent on to the target eNodeB. If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. The source Serving GW shall forward the "end marker" packets to the source eNodeB. If data forwarding -direct or indirect) occurs, the source eNodeB shall forward the "end marker" packets to the target eNodeB via the forwarding tunnel. 17. The Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic) message to the MME as a response to a Modify Bearer Request message, or a Modify Access Bearers Response (Serving GW address and TEID for uplink traffic) as a response to a Modify Access Bearers Request message. If the Serving GW cannot serve the MME Request in the Modify Access Bearers Request message without S5/S8 signalling other than to unpause charging in the PDN GW or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, it shall respond to the MME with indicating that the modifications are not limited to S1-U bearers, and the MME shall repeat its request using Modify Bearer Request message per PDN connection. If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. If data forwarding -direct or indirect) occurs, the source eNodeB shall forward the "end marker" packets to the target eNodeB via the forwarding tunnel.18. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies. For a UE supporting CIoT EPS Optimisations, the EPS bearer status information shall be included in the TAU Request. The MME shall then indicate the EPS bearer status to the UE in the TAU Accept and the UE shall locally release any non-transferred bearer. The target MME knows that it is a Handover procedure that has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source MME and target MME. In this case, the target MME shall set the Header Compression Context Status for each EPS Bearer in the TAU Accept message based on information obtained in step 3. 19. When the timer started in step 14 expires the source MME sends a UE Context Release Command () message to the source eNodeB. The source eNodeB releases its resources related to the UE and responds with a UE Context Release Complete () message. When the timer started in step 14 expires and if the source MME received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, LBI, Operation Indication, Secondary RAT usage data, User Location Information, PSCell ID) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data is included if it was received in step 9b. PSCell ID is included if it was received in step 9b. The Source Serving GW acknowledges with Delete Session Response () messages. If ISR has been activated before this procedure, the cause indicates to the Source S-GW that the Source S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 20. If indirect forwarding was used then the expiry of the timer at source MME started at step 14 triggers the source MME to send a Delete Indirect Data Forwarding Tunnel Request message to the S-GW to release the temporary resources used for indirect forwarding that were allocated at step 8. 21. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target MME started at step 14 triggers the target MME to send a Delete Indirect Data Forwarding Tunnel Request message to the target S-GW to release temporary resources used for indirect forwarding that were allocated at step 6. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.1.2.2 |
2,069 | 11.1.2 Defining a feature | A feature is a function extending the base GTPv2 functionality that has a significant meaning to the operation of GTPv2, i.e. a single new parameter without a substantial meaning to the functionality of the GTPv2 endpoints should not be defined to be a new feature. A functionality requiring the definition of a new GTPv2 message or extending the use of an existing message over a new interface should be defined as a feature. NOTE: Features are ultimately defined on a case-by-case basis on the merits of defining an extension as a feature. Features should be defined so that they are independent from each other. A GTP-C entity may support the same feature over different interfaces, e.g. an SGW may support a feature over both S11 and S4 interface, however support of a feature on a given interface shall not depend on the support of the same or another feature on another interface. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.1.2 |
2,070 | 5.37.6 UL/DL policy control based on round-trip latency requirement | For XR and other interactive media services that require very low Round-Trip (RT) latency, Uplink-Downlink policy control may be supported to meet the RT latency requirement. RT latency requirement is the upper bound for the sum of UL delay and DL delay of a single data flow or two different data flows between UE and N6 termination point at the UPF. PCF may support Uplink-Downlink policy control based on RT latency requirement based on an RT latency indication from AF (as defined in clause 6.1.3.27.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) during the AF session with the required QoS procedure as defined in clause 4.15.6.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AF can provide an RT latency indication with a single direction delay requirement between the UE and the PSA UPF expressed as the QoS Reference parameter or individual QoS parameters (as defined in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). The RT latency indication indicates the need to meet the RT latency requirement for data flow, i.e. doubling of the single direction delay requirement between the UE and the PSA UPF expressed by the QoS Reference parameter or individual QoS parameter. PCF determines the data flow's UL PDB and DL PDB based on the RT latency requirement. The UL PDB and DL PDB can be unequal, but their sum shall not exceed the RT latency requirement. The PCF shall generate two PCC rules, one for UL QoS flow for UL traffic of the data flow and one for DL QoS flow for DL traffic of the data flow, respectively. PCF shall assign the 5QIs for each of these two PCC rules according to the derived UL PDB and DL PDB. To support UL and DL delay tracking, the QoS monitoring for UL packet delay and the DL packet delay (as defined in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) shall be triggered respectively to request tracking the UL packet delay of the QoS flow used in UL and DL packet delay of the QoS flow used in DL independently. Based on the QoS monitoring results, the PCF may readjust the UL PDB and/or DL PDB under the consideration of the RT latency requirement to better fit the new situation. The Uplink-Downlink policy control based on round-trip latency requirement for two unidirectional service data flows is described in clause 6.1.3.27.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE: How the PCF derives the round-trip latency and takes policy decisions is up to the implementation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.6 |
2,071 | 5.2.4.2 Call activation for SRVCC | If the MS - supports SRVCC and the MS has a voice media stream previously carried over the PS domain that is handed over to the CS domain via SRVCC; - supports SRVCC or vSRVCC and the MS has a voice media stream and a video media stream of a single session previously in S1 mode carried over the PS domain and only the voice media stream is handed over to the CS domain via SRVCC; or - supports 5G-SRVCC handover from NG-RAN to UTRAN and the MS has a voice media stream previously in the N1 mode that is handed over to the CS domain via 5G-SRVCC handover from NG-RAN to UTRAN and the session is in the "confirmed" state (defined in IETF RFC 3261 [137]), and the call control entity in "null" state receives indication "MM connection establishment due to SRVCC handover", the call control entity of the MS shall enter the "active" state, set the auxiliary state (defined in 3GPP TS 24.083[ Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 ] [27]) to "idle", set the multi party auxiliary state (defined in 3GPP TS 24.084[ Multi Party (MPTY) supplementary service; Stage 3 ] [28]) to "idle" and indicate the call establishment to upper layers. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. If a single voice media stream is handed over and: - if the session is on hold, the setting of the auxiliary state (as defined in 3GPP TS 24.083[ Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 ] [27]) is described in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136]; and - if the session is a conferencing session, the setting of the multi party auxiliary state (as defined in 3GPP TS 24.084[ Multi Party (MPTY) supplementary service; Stage 3 ] [28]) is described in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136]. If the MS supports single radio PS to CS access transfer for calls in alerting state as specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B, and the MS has a single voice media stream over the PS domain that is handed over to the CS domain via SRVCC, and the call control entity of the MS in the "null" state receives an indication "MM connection establishment due to SRVCC handover" then: - the call control entity shall indicate to the upper layers that call establishment is due to SRVCC handover; - if the upper layers indicate that the media stream(s) is/are associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.2, the call control entity of the MS shall enter the "call delivered" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call; and - if the upper layers indicate that the media stream(s) is/are associated with a mobile terminating session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.1, the call control entity of the MS shall enter the "call received" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. If the MS supports single radio PS to CS SRVCC for originating calls in pre-alerting phase as specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B, and the MS has a single voice media stream over the PS domain that is handed over to the CS domain via SRVCC, and the call control entity of the MS in the "null" state receives an indication "MM connection establishment due to SRVCC handover" then: - the call control entity shall indicate to the upper layers that call establishment is due to SRVCC handover; and - if the upper layers indicate that the media stream(s) is/are associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.3, the call control entity of the MS shall enter the "mobile originating call proceeding" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. If the MS supports single radio PS to CS SRVCC for terminating calls in pre-alerting phase as specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B, and the MS has a single voice media stream over the PS domain that is handed over to the CS domain via SRVCC, and the call control entity of the MS in the "null" state receives an indication "MM connection establishment due to SRVCC handover" then: - the call control entity shall indicate to the upper layers that call establishment is due to SRVCC handover; and - if the upper layers indicate that the media stream(s) is/are associated with a mobile terminated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.2, the call control entity of the MS shall enter the "call present" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. NOTE: As the MS is entering "call present" state, it must send a CALL CONFIRMED message to the network, even even the call context (including codecs) is already available at the MSC in order to enter "mobile terminating call confirmed" state. If the MS has additional voice media streams carried over the PS domain that are handed over to the CS domain via SRVCC, the call states for the transactions and the setting of the TI value and TI flag for these additional media streams are described in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136]. If the MS supports multicall, the MS shall locally set SI value to "1" and the MS shall assume that the network does not support multicall. The network shall also locally set SI value to "1". If the MS has a mobile originating session in the "early" state (as defined in IETF RFC 3261 [137]) and is providing an internally generated alerting indication to the user prior to the SRVCC handover, then after transitioning from the PS domain, the MS shall continue to provide the internal alerting indication to the user. The alerting indication is stopped when the user connection is attached. If the MS has a mobile originated session established upon a request from the upper layers to establish an eCall over IMS, then after transitioning from the PS domain, the MS shall support inband transfer of the updated MSD according to 3GPP TS 26.267[ eCall data transfer; In-band modem solution; General description ] [161]. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.4.2 |
2,072 | 5.37.3 Support of ECN marking for L4S to expose the congestion information 5.37.3.1 General | L4S (Low Latency, Low Loss and Scalable Throughput) is described in IETF RFC 9330 [159], IETF RFC 9331 [160] and IETF RFC 9332 [161]. It exposes congestion information by marking ECN bits in the IP header of the user IP packets between the UE and the application server to trigger application layer rate adaptation. In 5G System, ECN marking for L4S may be supported. ECN marking for L4S is enabled on a per QoS Flow basis in the uplink and/or downlink direction and may be used for GBR and non-GBR QoS Flows. ECN marking for the L4S in the IP header is supported in either the NG-RAN (see clause 5.37.3.2 and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]), or in the PSA UPF (see clause 5.37.3.3). NOTE 1: Based on operator's network configuration and policies, SMF decides whether NG-RAN or PSA UPF based ECN marking for L4S is used. In the case of ECN marking for L4S by PSA UPF, the NG-RAN is instructed to perform congestion information monitoring and report to the PSA UPF the congestion information (i.e. a percentage of packets that UPF uses for ECN marking for L4S) of the QoS Flow on UL and/or DL directions via GTP-U header extension to PSA UPF. NOTE 2: As for any QoS Flow, QoS rules in the UE and PDRs in the PSA UPF control which packets are bound to the L4S enabled QoS flow. The Packet Filter Set in the QoS rule or PDR can use packet filter(s) in clause 5.7.6.2 (e.g. match packets with ECT(1) or CE (See RFC 9331 [160]) together with IP 5 tuple) to steer traffic to an L4S enabled QoS Flow. NOTE 3: A QoS Flow may be enabled with ECN marking for L4S requirement e.g. statically when a PDU session is established based on configuration in SMF or PCF, or dynamically based on detection of the L4S traffic (e.g. match packets with ECT(1) or CE (See RFC 9331 [160]) together with IP 5 tuple) in the IP header whereby SMF or PCF triggers a setup of a QoS Flow enabled for L4S, or by requests by an AF. NOTE 4: To support this functionality, the UE needs to support L4S feedback as described in IETF RFC 9330 [159], which is not in the scope of 3GPP. When serving PSA UPF or NG-RAN is changed e.g. due to inter-NG-RAN handover or PSA UPF relocation, target NG-RAN and target PSA UPF, if supported, should continue to perform ECN marking for L4S for the QoS Flow. However, if not available (i.e. ECN marking for L4S is not supported in both, target NG-RAN and target PSA UPF), AF should be notified when ECN marking for L4S had been enabled for the QoS Flow based on AF request. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.3 |
2,073 | 6.28.1 Description | The 5G system is expected to meet the service requirements for cyber-physical control applications in vertical domains. A vertical domain is a particular industry or group of enterprises in which similar products or services are developed, produced, and provided. Automation refers to the control of processes, devices, or systems in vertical domains by automatic means. The main control functions of automated control systems include taking measurements, comparing results, computing any detected or anticipated errors, and correcting the process to avoid future errors. These functions are performed by sensors, transmitters, controllers, and actuators. Cyber-physical systems are to be understood as systems that include engineered, interacting networks of physical and computational components. Cyber-physical control applications are to be understood as applications that control physical processes. Cyber-physical control applications in automation follow certain activity patterns, which are open-loop control, closed-loop control, sequence control, and batch control. Communication services supporting cyber-physical control applications need to be ultra-reliable, dependable with a high communication service availability, and often require low or (in some cases) very low end-to-end latency. Communication in automation in vertical domains follows certain communication patterns. The most well-known is periodic deterministic communication, others are a-periodic deterministic communication and Smart Grid. Smart Grid is a term that refers to enhanced cyber-physical control of electrical grids and to related application. Smart Grid operation can cover power generation, transmission, distribution, and consumption, which can require high communication service availability and communication service reliability, and in some cases a low end-to-end latency with more accurate clock synchronization. 5G system functionalities can be used for Smart Grid control, monitoring, availability assurance, service security, isolation and etc.Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation and energy automation. For more information about cyber-physical control applications in specific vertical domains, see clauses D.1 to D.4. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.28.1 |
2,074 | .1A Minimum requirements for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one E-UTRA band the in-band blocking requirements are defined with the uplink active on the band(s) other than the band whose downlink is being tested. For adjacent downlink bands separated by less than 30 MHz the frequency separation between the center frequencies of adjacent component carriers belonging to different bands shall be ≥ BW1/2 + BW2/2 + 2FIoffset,case j for Case j interferers, j = 1,2, where BWk/2 are the channel bandwidths of carrier k, k = 1,2. The UE shall meet the requirements specified in subclause 7.6.1.1 for each component carrier while all downlink carriers are active. For the UE which supports inter band CA configuration in Table 7.3.1-1A, PInterferer power defined in Table 7.6.1.1-2 is increased by the amount given by ΔRIB,c in Table 7.3.1-1A. For E-UTRA CA configurations including an operating band without uplink operation or an operating band with an unpaired DL part (as noted in Table 5.5-1), the requirements for all downlinks shall be met with the single uplink carrier active in each band capable of UL operation. The requirements for the component carrier configured in the operating band without uplink operation are specified in Table 7.6.1.1A-0, Table 7.6.1.1A-0a and Table 7.6.1.1A-0b. The requirements for a component carrier configured in Band 49 are specified in Table 7.6.1.1A-0a and Table 7.6.1.1A-0b. Table 7.6.1.1A-0: In-band blocking for additional operating bands for carrier aggregation Table 7.6.1.1A-0a: In band blocking parameters for additional operating bands for carrier aggregation Table 7.6.1.1A-0b: In-band blocking for additional operating bands for carrier aggregation For E-UTRA CA configurations listed in Table 7.3.1A-0a under conditions for which reference sensitivity for the operating band being tested is N/A, the in-band blocking requirements of subclause 7.6.1.1A do not apply. For intra-band contiguous carrier aggregation the downlink SCC(s) shall be configured at nominal channel spacing to the PCC. For FDD, the PCC shall be configured closest to the uplink band. All downlink carriers shall be active throughout the test. The uplink output power shall be set as specified in Table .1A-1 with the uplink configuration set according to Table 7.-1 for the applicable carrier aggregation configuration. For UE(s) supporting one uplink carrier, the uplink configuration of the PCC shall be in accordance with Table 7.3.1-2. The UE shall fulfil the minimum requirement in presence of an interfering signal specified in Tables .1A-1 and Tables 7.6.-2 being on either side of the aggregated signal. The throughput of each carrier shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes , A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex /A.5.2.1) with parameters specified in Tables 7.6.-1 and 7.6.1.1A-2. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements also apply for an SCC assigned in the unpaired part with parameters specified in Tables 7.6.2.1A-1 and 7.6.2.1A-2. For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, each larger than or equal to 5 MHz, the in-band blocking requirements are defined with the uplink configuration in accordance with Table 7.3.1A-3. For this uplink configuration, the UE shall meet the requirements for each sub-block as specified in subclause 7.6.1.1 and in this subclause for one component carrier and two component carriers per sub-block, respectively. The requirements apply for in-gap and out-of-gap interferers while all downlink carriers are active. Table .1A-1: In band blocking parameters Table .1A-2: In-band blocking For combinations of intra-band and inter-band carrier aggregation and one uplink carrier assigned to one E-UTRA band, the requirement is defined with the uplink active in the band other than that supporting the downlink(s) under test. The uplink configuration shall be in accordance with Table 7.3.1A-3 when the uplink is active in the band supporting two or more non-contiguous component carriers, Table 7.3.1A-1 when the uplink is active in a band supporting two contiguous component carriers and in accordance with Table 7.3.1-2 when the uplink is active in a band supporting one carrier per band. The downlink PCC shall be configured closer to the uplink operating band than the downlink SCC(s) when the uplink is active in band(s) supporting contiguous aggregation. For these uplink configurations, the UE shall meet the in-band blocking requirements for intra-band non-contiguous carrier aggregation with RIBNC = 0 dB for all sub-block gaps (Table 7.3.1A-3) for the two or more non-contiguous downlink sub-blocks, the requirements for intra-band contiguous carrier aggregation for the contiguously aggregated downlink carriers and for any remaining component carrier(s) the requirements specified in subclause 7.6.1. For contiguously aggregated component carriers configured in Band 46, the said requirements for intra-band contiguous carrier aggregation of downlink carriers are replaced by requirements in Table 7.6.1.1A-3 and 7.6.1.1A-4. For non-contiguously aggregated component carriers configured in Band 46, the said requirements are applied to each sub-block for in-gap and out-of-gap interferers. For the sub-block with a single component carrier, the requirement is replaced by Table 7.6.1.1A-0a and 7.6.1.1A-0b. For the sub-block with two or more contiguous component carriers, the requirement is replaced by Table 7.6.1.1A-3 and 7.6.1.1A-4. All downlink carriers shall be active throughout the tests and the requirements for the downlinks shall be met with the single uplink carrier active in each band capable of uplink operation. Table .1A-3: In band blocking parameters Table .1A-4: In-band blocking | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | .1A |
2,075 | 5.16.2.2 SMS over NAS transport | 5G System supports SMS over NAS via both 3GPP access and non-3GPP access. During Registration procedure, a UE that wants to use SMS provides an "SMS supported" indication over NAS signalling indicating the UE's capability for SMS over NAS transport. "SMS supported" indication indicates whether UE can support SMS delivery over NAS. If the core network supports SMS functionality, the AMF includes "SMS allowed" indication to the UE, and whether SMS delivery over NAS is accepted by the network. SMS is transported via NAS transport message, which can carry SMS messages as payload. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.2.2 |
2,076 | – HandoverPreparationInformation | This message is used to transfer the NR RRC information used by the target gNB during handover preparation or UE context retrieval, e.g. in case of resume or re-establishment, including UE capability information. This message is also used for transferring the information between the CU and DU. Direction: source gNB/source RAN to target gNB or CU to DU. HandoverPreparationInformation message -- ASN1START -- TAG-HANDOVER-PREPARATION-INFORMATION-START HandoverPreparationInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ handoverPreparationInformation HandoverPreparationInformation-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } HandoverPreparationInformation-IEs ::= SEQUENCE { ue-CapabilityRAT-List UE-CapabilityRAT-ContainerList, sourceConfig AS-Config OPTIONAL, -- Cond HO rrm-Config RRM-Config OPTIONAL, as-Context AS-Context OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } AS-Config ::= SEQUENCE { rrcReconfiguration OCTET STRING (CONTAINING RRCReconfiguration), ..., [[ sourceRB-SN-Config OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, sourceSCG-NR-Config OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, sourceSCG-EUTRA-Config OCTET STRING OPTIONAL ]], [[ sourceSCG-Configured ENUMERATED {true} OPTIONAL ]], [[ sdt-Config-r17 SDT-Config-r17 OPTIONAL ]] } AS-Context ::= SEQUENCE { reestablishmentInfo ReestablishmentInfo OPTIONAL, configRestrictInfo ConfigRestrictInfoSCG OPTIONAL, ..., [[ ran-NotificationAreaInfo RAN-NotificationAreaInfo OPTIONAL ]], [[ ueAssistanceInformation OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL -- Cond HO2 ]], [[ selectedBandCombinationSN BandCombinationInfoSN OPTIONAL ]], [[ configRestrictInfoDAPS-r16 ConfigRestrictInfoDAPS-r16 OPTIONAL, sidelinkUEInformationNR-r16 OCTET STRING OPTIONAL, sidelinkUEInformationEUTRA-r16 OCTET STRING OPTIONAL, ueAssistanceInformationEUTRA-r16 OCTET STRING OPTIONAL, ueAssistanceInformationSCG-r16 OCTET STRING (CONTAINING UEAssistanceInformation) OPTIONAL, -- Cond HO2 needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL ]], [[ configRestrictInfoDAPS-v1640 ConfigRestrictInfoDAPS-v1640 OPTIONAL ]], [[ needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL, needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17 OPTIONAL, mbsInterestIndication-r17 OCTET STRING (CONTAINING MBSInterestIndication-r17) OPTIONAL ]], [[ needForInterruptionInfoNR-r18 NeedForInterruptionInfoNR-r18 OPTIONAL, flightPathInfoReport-r18 FlightPathInfoReport-r18 OPTIONAL ]] } ConfigRestrictInfoDAPS-r16 ::= SEQUENCE { powerCoordination-r16 SEQUENCE { p-DAPS-Source-r16 P-Max, p-DAPS-Target-r16 P-Max, uplinkPowerSharingDAPS-Mode-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic } } OPTIONAL } ConfigRestrictInfoDAPS-v1640 ::= SEQUENCE { sourceFeatureSetPerDownlinkCC-r16 FeatureSetDownlinkPerCC-Id, sourceFeatureSetPerUplinkCC-r16 FeatureSetUplinkPerCC-Id } ReestablishmentInfo ::= SEQUENCE { sourcePhysCellId PhysCellId, targetCellShortMAC-I ShortMAC-I, additionalReestabInfoList ReestabNCellInfoList OPTIONAL } ReestabNCellInfoList ::= SEQUENCE ( SIZE (1..maxCellPrep) ) OF ReestabNCellInfo ReestabNCellInfo::= SEQUENCE{ cellIdentity CellIdentity, key-gNodeB-Star BIT STRING (SIZE (256)), shortMAC-I ShortMAC-I } RRM-Config ::= SEQUENCE { ue-InactiveTime ENUMERATED { s1, s2, s3, s5, s7, s10, s15, s20, s25, s30, s40, s50, min1, min1s20, min1s40, min2, min2s30, min3, min3s30, min4, min5, min6, min7, min8, min9, min10, min12, min14, min17, min20, min24, min28, min33, min38, min44, min50, hr1, hr1min30, hr2, hr2min30, hr3, hr3min30, hr4, hr5, hr6, hr8, hr10, hr13, hr16, hr20, day1, day1hr12, day2, day2hr12, day3, day4, day5, day7, day10, day14, day19, day24, day30, dayMoreThan30} OPTIONAL, candidateCellInfoList MeasResultList2NR OPTIONAL, ..., [[ candidateCellInfoListSN-EUTRA MeasResultServFreqListEUTRA-SCG OPTIONAL ]] } -- TAG-HANDOVER-PREPARATION-INFORMATION-STOP -- ASN1STOP NOTE 1: The following table indicates per source RAT whether RAT capabilities are included or not. NOTE 2: The following table indicates, in case of inter-RAT handover from E-UTRA, which additional IEs are included or not: | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,077 | 4.22.2.1 Non-roaming and Roaming with Local Breakout | The signalling flow for a MA PDU Session establishment when the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, is based on the signalling flow in Figure 4.3.2.2.1-1 with the following differences and clarifications: - The PDU Session Establishment Request message may be sent over the 3GPP access or over the non-3GPP access. In the steps below, it is assumed that it is sent over the 3GPP access, unless otherwise specified. - In step 1, the UE provides Request Type as "MA PDU Request" in UL NAS Transport message and its ATSSS Capabilities as defined in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] in PDU Session Establishment Request message. The "MA PDU Request" Request Type in the UL NAS Transport message indicates to the network that this PDU Session Establishment Request is to establish a new MA PDU Session and to apply one or more steering functionalities (defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.32.6) for steering the traffic of this MA PDU session over multiple accesses. If the UE requests an S-NSSAI and the UE is registered over both accesses, it shall request an S-NSSAI that is allowed on both accesses. The UE indicates to AMF whether it supports non-3GPP access path switching, i.e. whether the UE can transfer the non-3GPP access path of the MA PDU Session from a source non-3GPP access (N3IWF/TNGF) to a target non-3GPP access (a different N3IWF/TNGF). - In step 2, if the AMF supports MA PDU sessions, then the AMF selects an SMF, which supports MA PDU sessions. If the AMF supports non-3GPP access path switching and the UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF selects a SMF that supports non-3GPP access path switching, if such an SMF is available. - In step 3, the AMF informs the SMF that the request is for a MA PDU Session by including "MA PDU Request" indication and in addition, it indicates to SMF whether the UE is registered over both accesses. If the AMF determines that the UE is registered via both accesses, but the requested S-NSSAI is not allowed on both accesses, then the AMF shall reject the MA PDU session establishment. If the AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the selected SMF supports non-3GPP path switching and UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF indicates whether the UE supports non-3GPP path switching to the SMF. The AMF shall reject the PDU Session Establishment request if the request is for a LADN. - In step 4, the SMF retrieves, via Session Management subscription data, the information whether the MA PDU session is allowed or not. - In step 7, if dynamic PCC is to be used for the MA PDU Session, the SMF sends an "MA PDU Request" indication to the PCF in the SM Policy Control Create message and the ATSSS Capabilities of the MA PDU session. The SMF provides the currently used Access Type(s) and RAT Type(s) to the PCF. The PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. The PCF provides PCC rules that include MA PDU session control information, as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. From the received PCC rules, the SMF derives (a) ATSSS rules, which will be sent to UE for controlling the traffic steering, switching and splitting in the uplink direction and (b) N4 rules, which will be sent to UPF for controlling the traffic steering, switching and splitting in the downlink direction. If the UE indicates the support of "ATSSS-LL Capability", the SMF may derive the Measurement Assistance Information. If the SMF receives a UP Security Policy for the PDU Session with Integrity Protection set to "Required" and the MA PDU session is being established over non-3GPP access, the SMF does not verify whether the access can satisfy the UP Security Policy. - In the remaining steps of Figure 4.3.2.2.1-1, the SMF establishes the user-plane resources over the 3GPP access, i.e. over the access where the PDU Session Establishment Request was sent on: - In step 10, the N4 rules derived by SMF for the MA PDU session are sent to UPF and two N3 UL CN tunnels info are allocated by the UPF. If the ATSSS LL functionality is supported for MA PDU Session, the SMF may instruct the UPF to initiate performance measurement for this MA PDU Session. If the MPTCP functionality and/or the MPQUIC functionality is supported for the MA PDU Session, the SMF may instruct the UPF to activate the MPTCP functionality and/or the MPQUIC functionality for this MA PDU Session. In step 10a, the UPF allocates addressing information for the Performance Measurement Function (PMF) in the UPF. If the UPF receives from the SMF a list of QoS flows over which access performance measurements may be performed, the UPF allocates different UDP ports or different MAC addresses per QoS flow per access. In step 10b, the UPF sends the addressing information for the PMF in the UPF to the SMF. If UDP ports or MAC addresses are allocated per QoS flow and per access, the UPF sends the PMF IP address information and UDP ports with the related QFI to the SMF in the case of IP PDU sessions and sends the MAC addresses with the related QFI to the SMF in the case of Ethernet PDU sessions. In step 10a, if the message from the SMF instructs the UPF to activate MPTCP functionality, the UPF allocates the UE "MPTCP link-specific multipath" addresses/prefixes. In step 10b, the UPF sends the "MPTCP link-specific multipath" addresses/prefixes and MPTCP proxy information to the SMF. If the message from the SMF instructs the UPF to activate MPQUIC functionality, the UPF allocates the UE "MPQUIC link-specific multipath" addresses/prefixes. In step 10b, the UPF sends the "MPQUIC link-specific multipath" addresses/prefixes and MPQUIC proxy information to the SMF. The "MPTCP link-specific multipath" addresses/prefixes and the "MPQUIC link-specific multipath" addresses/prefixes may be the same. - In step 11, for the MA PDU session, the SMF includes an "MA PDU session Accepted" indication in the Namf_Communication_N1N2MessageTransfer message to the AMF and indicates to AMF that the N2 SM Information included in this message should be sent over 3GPP access. The AMF marks this PDU session as MA PDU session based on the received "MA PDU session Accepted" indication. If the AMF indicated in step 3 that non-3GPP path switching while maintaining two N2 connections for non-3GPP access is supported, the SMF indicates support of non-3GPP path switching in the PDU Session Establishment Accept message. - In step 13, the UE receives a PDU Session Establishment Accept message, which indicates to UE that the requested MA PDU session was successfully established. This message includes the ATSSS rules for the MA PDU session, which were derived by SMF. If the ATSSS -LL functionality is supported for the PDU Session, the SMF may include the addressing information of PMF in the UPF into the Measurement Assistance Information. If the MPTCP functionality is supported for the MA PDU Session, the SMF shall include the "MPTCP link-specific multipath" addresses/prefixes of the UE and the MPTCP proxy information. If the MPQUIC functionality is supported for the MA PDU Session, the SMF shall include the "MPQUIC link-specific multipath" addresses/prefixes of the UE and the MPQUIC proxy information. - After step 18 in Figure 4.3.2.2.1-1, if the SMF was informed in step 2 that the UE is registered over both accesses, then the SMF initiates the establishment of user-plane resources over non-3GPP access too. The SMF sends an Namf_Communication_N1N2MessageTransfer to the AMF including N2 SM Information and indicates to AMF that the N2 SM Information should be sent over non-3GPP access. Namf_Communication_N1N2MessageTransfer does not include an N1 SM Container for the UE because this was sent to UE in step 13. After this step, the two N3 tunnels between the PSA and RAN/AN are established. The last step above is not executed when the UE is registered over one access only, in which case the MA PDU Session is established with user-plane resources over one access only. How user-plane resources can be added over an access of the MA PDU Session is specified in clause 4.22.7. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.2.1 |
2,078 | 5.3.5.5.3 RLC bearer release | The UE shall: 1> for each logicalChannelIdentity/LogicalChannelIdentityExt value included in the rlc-BearerToReleaseList/rlc-BearerToReleaseListExt that is part of the current UE configuration within the same cell group (LCH release); or 1> for each logicalChannelIdentity value that is to be released as the result of an SCG release according to 5.3.5.4: 2> release the RLC entity or entities as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], clause 5.1.3; 2> release the corresponding logical channel. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.3 |
2,079 | 9.3.3.2 Bearer capability 1 and bearer capability 2 | The bearer capability 1 information element shall be included if the network has to specify at least one of the negotiable parameters described in 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36], or if the bearer capability 1 information element received in the SETUP message included the "fixed network user rate" parameter. When the bearer capability 1 information element is followed by the bearer capability 2 IE in the SETUP, the above rule applies to both bearer capability 1 IE and bearer capability 2 IE. Except those cases identified in 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36], if either bearer capability needs to be included, both shall be included. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.3.2 |
2,080 | 5.27.1 Time Synchronization 5.27.1.1 General | For supporting time synchronization service, the 5GS is configured to operate in one or multiple PTP instances and to operate in one of the following modes (if supported) for each PTP instance: 1) as time-aware system as described in IEEE Std 802.1AS [104], 2) as Boundary Clock as described in IEEE Std 1588 [126], provisioned by the profiles supported by this 3GPP specification including SMPTE Profile for Use of IEEE Std 1588 [126] Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]; NOTE 1: Via proper configuration of the IEEE Std 1588 [126] data set members, the 5G internal system clock can become the time source for the PTP grandmaster function for the connected networks in the case of mode 1 and mode 2. NOTE 2: In some cases where the 5G internal system clock is the time source for the PTP grandmaster function for the connected networks, it might not be required for the UE to receive gPTP or PTP messages over user plane. The UE and DS-TT uses the 5G timing information and generates the necessary gPTP or PTP message for the end station, if needed (this is implementation specific). 3) as peer-to-peer Transparent Clock as described in IEEE Std 1588 [126], provisioned by the profiles supported by this 3GPP specification including SMPTE Profile for Use of IEEE Std 1588 Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]; or 4) as end-to-end Transparent Clock as described in IEEE Std 1588 [126], provisioned by the profiles supported by this 3GPP specification including SMPTE Profile for Use of IEEE Std 1588 Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]. NOTE 3: When the GM is external, the operation of 5GS as Boundary Clock assumes that profiles that are supported by the 5GS allows the exemption specified in clauses 9.5.9 and 9.5.10 of IEEE Std 1588 [126] where the originTimestamp (or preciseOriginTimestamp in case of two-step operation) is not required to be updated with the syncEventEgressTimestamp (and a Local PTP Clock locked to the external GM). As described in clause 5.27.1.2.2, only correctionField is updated with the 5GS residence time and link delay, in a similar operation as specified by IEEE Std 802.1AS [104]. The configuration of the time synchronization service in 5GS for option 1 by TSN AF and CNC is described in clause 5.28.3, and for options 1-4 by AF/NEF and TSCTSF in clause 5.27.1.8 and clause 5.28.3. The 5GS shall be modelled as an IEEE Std 802.1AS [104] or IEEE Std 1588 [126] compliant entity based on the above configuration. NOTE 4: This release of the specification does not support the PTP management mechanism or PTP management messages as described in clause 15 in IEEE Std 1588 [126]. The DS-TT and NW-TT at the edge of the 5G system may support the IEEE Std 802.1AS [104] or other IEEE Std 1588 [126] profiles' operations respective to the configured mode of operation. The UE, gNB, UPF, NW-TT and DS- TTs are synchronized with the 5G GM (i.e. the 5G internal system clock) which shall serve to keep these network elements synchronized. The TTs located at the edge of 5G system fulfil some functions related to IEEE Std 802.1AS [104] and may fulfil some functions related to IEEE Std 1588 [126], e.g. (g)PTP support and timestamping. Figure 5.27.1-1 illustrates the 5G and PTP grandmaster (GM) clock distribution model via 5GS. Figure 5.27.1-1: 5G system is modelled as PTP instance for supporting time synchronization Figure 5.27.1-1 depicts the two synchronizations systems considered: the 5G Clock synchronization and the (g)PTP domain synchronization. - 5G Access Stratum-based Time Distribution: Used for NG RAN synchronization and also distributed to the UE. The 5G Access Stratum-based Time Distribution over the radio interface towards the UE is specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. This method may be used to either further distribute the 5G timing to devices connected to a UE (using implementation-specific means) or to support the operation of the (g)PTP-based time distribution method. - (g)PTP-based Time Distribution: Provides timing among entities in a (g)PTP domain. This process follows the applicable profiles of IEEE Std 802.1AS [104] or IEEE Std 1588 [126]. This method relies on the 5G access stratum-based time distribution method to synchronize the UE/DS-TT and on the 5GS time synchronization to synchronize the gNB (which, in turn, may synchronize the DS-TT) and the NW-TT. The gNB needs to be synchronized to the 5G GM clock. The 5GS supports two methods for determining the grandmaster PTP Instance and the time-synchronization spanning tree. - Method a), BMCA procedure. - Method b), local configuration. This is further described in clause 5.27.1.6. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1 |
2,081 | 5.5.1.3.5 Mobility and periodic registration update not accepted by the network | If the mobility and periodic registration update request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value. If the mobility and periodic registration update request is rejected due to general NAS level mobility management congestion control, the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346. In NB-N1 mode, if the mobility and periodic registration update request is rejected due to operator determined barring (see 3GPP TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [20AB]), the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346. When the UE performs inter-system change from S1 mode to N1 mode, if the AMF is informed that verification of the integrity protection of the TRACKING AREA UPDATE REQUEST message included by the UE in the EPS NAS message container IE of the REGISTRATION REQUEST message has failed in the MME, then: a) If the AMF can retrieve the current 5G NAS security context as indicated by the ngKSI and 5G-GUTI sent by the UE, the AMF shall proceed as specified in subclause 5.5.1.3.4; b) if the AMF cannot retrieve the current 5G NAS security context as indicated by the ngKSI and 5G-GUTI sent by the UE, or the ngKSI or 5G-GUTI was not sent by the UE, the AMF may initiate the identification procedure by sending the IDENTITY REQUEST message with the "Type of identity" of the 5GS identity type IE set to "SUCI" before taking actions as specified in subclause 4.4.4.3; or c) If the AMF needs to reject the mobility and periodic registration update procedure, the AMF shall send REGISTRATION REJECT message including 5GMM cause #9 "UE identity cannot be derived by the network". If the REGISTRATION REJECT message with 5GMM cause #76 or #78 was received without integrity protection, then the UE shall discard the message. If the REGISTRATION REJECT message with 5GMM cause #62 was received without integrity protected, the behaviour of the UE is specified in subclause 5.3.20.2. Based on operator policy, if the mobility and periodic registration update request is rejected due to core network redirection for CIoT optimizations, the network shall set the 5GMM cause value to #31 "Redirection to EPC required". NOTE 1: The network can take into account the UE's S1 mode capability, the EPS CIoT network behaviour supported by the UE or the EPS CIoT network behaviour supported by the EPC to determine the rejection with the 5GMM cause value #31 "Redirection to EPC required". If the mobility and periodic registration update request is rejected because: a) all the S-NSSAI(s) included in the requested NSSAI (i.e. Requested NSSAI IE or Requested mapped NSSAI IE) are rejected; b) the UE set the NSSAA bit in the 5GMM capability IE to: 1) "Network slice-specific authentication and authorization supported" and; i) void; ii) all default S-NSSAIs are not allowed; or iii) network slice-specific authentication and authorization has failed or been revoked for all default S-NSSAIs and based on network local policy, the network decides not to initiate the network slice-specific re-authentication and re-authorization procedures for any default S-NSSAI requested by the UE; or 2) "Network slice-specific authentication and authorization not supported" and all subscribed default S-NSSAIs marked as default are either not allowed or are subject to network slice-specific authentication and authorization; and i) void; or ii) void; and c) no emergency PDU session has been established for the UE; the network shall set the 5GMM cause value of the REGISTRATION REJECT message to #62 "No network slices available" and shall include, in the rejected NSSAI of the REGISTRATION REJECT message, all the S-NSSAI(s) which were included in the requested NSSAI. If the UE has set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the rejected S-NSSAI(s) shall be included in the Extended rejected NSSAI IE of the REGISTRATION REJECT message. Otherwise, the rejected S-NSSAI(s) shall be included in the Rejected NSSAI IE of the REGISTRATION REJECT message. In roaming scenarios, if the Extended rejected NSSAI IE is included in the REGISTRATION REJECT message, the AMF shall provide mapped S-NSSAI(s) for the rejected NSSAI. If the UE supports extended rejected NSSAI and the AMF determines that maximum number of UEs reached for one or more S-NSSAI(s) in the requested NSSAI as specified in subclause 4.6.2.5, the AMF shall include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE in the REGISTRATION REJECT message. In addition, the AMF may include a back-off timer value for each S-NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE of the REGISTRATION REJECT message. If the mobility and periodic registration update request from a UE supporting CAG is rejected due to CAG restrictions, the network shall set the 5GMM cause value to #76 "Not authorized for this CAG or authorized for CAG cells only" and should include the "CAG information list" in the CAG information list IE or the Extended CAG information list IE in the REGISTRATION REJECT message. NOTE 2: The network cannot be certain that "CAG information list" stored in the UE is updated as result of sending of the REGISTRATION REJECT message with the CAG information list IE or the Extended CAG information list IE, as the REGISTRATION REJECT message is not necessarily delivered to the UE (e.g due to abnormal radio conditions). NOTE 3: The "CAG information list" can be provided by the AMF and include no entry if no "CAG information list" exists in the subscription. NOTE 3A: If the UE supports extended CAG information list, the CAG information list can be included either in the CAG information list IE or Extended CAG information list IE. NOTE 3B: It is unexpected for network to send REGISTRATION REJECT message to the UE with 5GMM cause value #76 in non-CAG cell and not indicate "Indication that the UE is only allowed to access 5GS via CAG cells" for the serving PLMN in the Extended CAG information list or the CAG information list. If the UE does not support extended CAG information list, the CAG information list shall not be included in the Extended CAG information list IE. If the mobility and periodic registration update request from a UE not supporting CAG is rejected due to CAG restrictions, the network shall operate as described in bullet i) of subclause 5.5.1.3.8. If the UE's mobility and periodic registration update request is via a satellite NG-RAN cell and the network determines that the UE is in a location where the network is not allowed to operate, see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], the network shall set the 5GMM cause value in the REGISTRATION REJECT message to #78 "PLMN not allowed at the present UE location". NOTE 4: When the UE accessing network for emergency services, it is up to operator and regulatory policies whether the network needs to determine if the UE is in a location where network is not allowed to operate. If the AMF receives the mobility and periodic registration update request including the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE and the AMF determines that the UE is not allowed to use UAS services via 5GS based on the user's subscription data and the operator policy, the AMF shall return a REGISTRATION REJECT message with 5GMM cause #79 “UAS services not allowed”. If the mobility and periodic registration update request from a UE supporting MINT is rejected due to a disaster condition no longer being applicable in the current location of the UE, the network shall set the 5GMM cause value to #11 "PLMN not allowed" or #13 "Roaming not allowed in this tracking area" and may include a disaster return wait range in the Disaster return wait range IE in the REGISTRATION REJECT message. If the UE initiates the registration procedure for disaster roaming and the AMF determines that it does not support providing disaster roaming services for the determined PLMN with disaster condition to the UE, then the AMF shall send a REGISTRATION REJECT message with 5GMM cause #80 “Disaster roaming for the determined PLMN with disaster condition not allowed”. If the AMF receives the mobility and periodic registration update request over non-3GPP access and detects that the N3IWF used by the UE is not compatible with the allowed NSSAI and the UE has indicated its support for slice-based N3IWF selection in the REGISTRATION REQUEST message, the AMF may send a REGISTRATION REJECT message with 5GMM cause #81 "Selected N3IWF is not compatible with the allowed NSSAI" and may provide information for a suitable N3IWF in the REGISTRATION REJECT message indicating the suitable N3IWF that is compatible with the requested NSSAI. If the AMF receives the mobility and periodic registration update request over non-3GPP access and detects that the TNGF used by the UE is not compatible with the allowed NSSAI and the UE has indicated its support for slice-based TNGF selection in the REGISTRATION REQUEST message, the AMF may send a REGISTRATION REJECT message with 5GMM cause #82 "Selected TNGF is not compatible with the allowed NSSAI" and may provide information for a suitable TNAN in the TNAN information IE in the REGISTRATION REJECT message indicating the suitable TNGF that is compatible with the requested NSSAI. If the AMF received multiple TAIs from the satellite NG-RAN as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], and determines that, by UE subscription and operator's preferences, all of the received TAIs are forbidden for roaming or for regional provision of service, the AMF shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE; or b) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE; or c) both; in the REGISTRATION REJECT message. Regardless of the 5GMM cause value received in the REGISTRATION REJECT message via satellite NG-RAN, - if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE in the REGISTRATION REJECT message and if the TAI(s) included in the IE is not part of the list of "5GS forbidden tracking areas for roaming", the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for roaming"; and - if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the REGISTRATION REJECT message and if the TAI(s) included in the IE is not part of the list of "5GS forbidden tracking areas for regional provision of service", the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for regional provision of service". In a shared network, the UE shall construct the TAI of the cell from one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and the TAC received on the broadcast system information. Whenever a REGISTRATION REJECT message is received by the UE: - with the 5GMM cause #11 "PLMN not allowed", the chosen PLMN identity shall be stored in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.19A; - with the 5GMM cause #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", #15 "no suitable cells in tracking Area", or #62 "No network slices available", the constructed TAI shall be stored in the suitable list; or - as a response to registration procedure for mobility registration update initiated in 5GMM-CONNECTED mode, the UE need not update forbidden lists with the selected PLMN identity or the constructed TAI, respectively. Furthermore, the UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message. #3 (Illegal UE); or #6 (Illegal ME). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19a.1. In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19a.2. In case of SNPN, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19a.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19a.2. If the UE is not registered for onboarding services in SNPN, the UE shall delete the list of equivalent PLMNs (if any) or the list of equivalent SNPNs (if any), and shall move to 5GMM-DEREGISTERED.NO-SUPI state. If the message has been successfully integrity checked by the NAS, then the UE shall: 1) set the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events to UE implementation-specific maximum value in case of PLMN if the UE maintains these counters; 2) set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events to UE implementation-specific maximum value in case of SNPN if the UE maintains these counters; and If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.7a of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. If the UE is in EMM-REGISTERED state, the UE shall move to EMM-DEREGISTERED state. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the UE is registered for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #7 (5GS services not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19a.1; In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for 5GS services until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19a.2. In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19a.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19a.2. If the UE is not registered for onboarding services in SNPN, the UE shall move to 5GMM-DEREGISTERED.NO-SUPI state. If the message has been successfully integrity checked by the NAS, then the UE shall: 1) set the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events to UE implementation-specific maximum value in case of PLMN if the UE maintains these counters; 2) set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events to UE implementation-specific maximum value in case of SNPN if the UE maintains these counters; and If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. If the UE is registered for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #9 (UE identity cannot be derived by the network). The UE shall set the 5GS update status to 5U2 NOT UPDATED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall enter the state 5GMM-DEREGISTERED. If the UE has initiated the registration procedure in order to enable performing the service request procedure for emergency services fallback, the UE shall attempt to select an E-UTRA cell connected to EPC or 5GCN according to the domain priority and selection rules specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the UE finds a suitable E-UTRA cell, it then proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. If the rejected request was neither for initiating an emergency PDU session nor for emergency services fallback, the UE shall subsequently, automatically initiate the initial registration procedure. NOTE 5: User interaction is necessary in some cases when the UE cannot re-establish the PDU session(s) automatically. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. #10 (implicitly de-registered). The UE shall enter the state 5GMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped 5G NAS security context or partial native 5G NAS security context. If the UE has initiated the registration procedure in order to enable performing the service request procedure for emergency services fallback, the UE shall attempt to select an E-UTRA cell connected to EPC or 5GCN according to the domain priority and selection rules specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the UE finds a suitable E-UTRA cell, it then proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. If the rejected request was neither for initiating an emergency PDU session nor for emergency services fallback, the UE shall perform a new registration procedure for initial registration. NOTE 6: User interaction is necessary in some cases when the UE cannot re-establish the PDU session(s) automatically. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM state as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. #11 (PLMN not allowed). This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in subclause 5.3.19a.1, delete the list of equivalent PLMNs, reset the registration attempt counter. For 3GPP access, the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. For non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message has been successfully integrity checked by the NAS and the UE maintains the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same PLMN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. If the UE receives the Disaster return wait range IE in the REGISTRATION REJECT message and the UE supports MINT, the UE shall delete the disaster return wait range stored in the ME, if any, and store the disaster return wait range included in the Disaster return wait range IE in the ME. #12 (Tracking area not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. If: 1) the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE is not included in the REGISTRATION REJECT message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. #13 (Roaming not allowed in this tracking area). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access the UE shall delete the list of equivalent PLMNs (if available) or the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter. For 3GPP acess the UE shall change to state 5GMM-REGISTERED.PLMN-SEARCH, and for non-3GPP access the UE shall change to state 5GMM-REGISTERED.LIMITED-SERVICE. If the UE is registered in S1 mode and operating in dual-registration mode, the PLMN that the UE chooses to register in is specified in subclause 4.8.3. Otherwise if: 1) the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the REGISTRATION REJECT message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and shall remove the current TAI from the stored TAI list if present. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. For 3GPP access the UE shall perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. If the UE receives the Disaster return wait range IE in the REGISTRATION REJECT message and the UE supports MINT, the UE shall delete the disaster return wait range stored in the ME, if any, and store the disaster return wait range included in the Disaster return wait range IE in the ME. #15 (No suitable cells in tracking area). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). The UE shall reset the registration attempt counter and shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. If the UE has initiated the registration procedure in order to enable performing the service request procedure for emergency services fallback, the UE shall attempt to select an E-UTRA cell connected to EPC or 5GC according to the emergency services support indicator (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]). If the UE finds a suitable E-UTRA cell, it then proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. Otherwise, the UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. If: 1) the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the REGISTRATION REJECT message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and shall remove the current TAI from the stored TAI list, if present. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and shall remove the current TAI from the stored TAI list, if present. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. If received over non-3GPP access the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.3.7. #22 (Congestion). If the T3346 value IE is present in the REGISTRATION REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.3.7. The UE shall abort the registration procedure for mobility and periodic registration update. If the rejected request was not for initiating an emergency PDU session, the UE shall set the 5GS update status to 5U2 NOT UPDATED, reset the registration attempt counter and change to state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. The UE shall stop timer T3346 if it is running. If the REGISTRATION REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE. If the REGISTRATION REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]. The UE stays in the current serving cell and applies the normal cell reselection process. The registration procedure for mobility and periodic registration update is started, if still necessary, when timer T3346 expires or is stopped. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. If the registration procedure for mobility and periodic registration update was initiated for an MO MMTEL voice call (i.e. access category 4), or an MO MMTEL video call (i.e. access category 5), or an MO IMS registration related signalling (i.e. access category 9) or for NAS signalling connection recovery during an ongoing MO MMTEL voice call (i.e. access category 4), or during an ongoing MO MMTEL video call (i.e. access category 5) or during an ongoing MO IMS registration related signalling (i.e. access category 9), then a notification that the request was not accepted due to network congestion shall be provided to upper layers. NOTE 8: Upper layers specified in 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13C] and 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] handle the notification that the request was not accepted due to network congestion. If the UE is registered for onboarding services in SNPN, the UE may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. #27 (N1 mode not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). Additionally, the UE shall reset the registration attempt counter and shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. If the message has been successfully integrity checked by the NAS, the UE shall set: 1) the PLMN-specific N1 mode attempt counter for 3GPP access and the PLMN-specific N1 mode attempt counter for non-3GPP access for that PLMN in case of PLMN; or 2) the SNPN-specific attempt counter for 3GPP access for the current SNPN and the SNPN-specific attempt counter for non-3GPP access for the current SNPN in case of SNPN; to the UE implementation-specific maximum value. The UE shall disable the N1 mode capability for the specific access type for which the message was received (see subclause 4.9). If the message has been successfully integrity checked by the NAS, the UE shall disable the N1 mode capability also for the other access type (see subclause 4.9). If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED. Additionally, the UE shall reset the tracking area updating attempt counter and enter the state EMM-REGISTERED. #31 (Redirection to EPC required). 5GMM cause #31 received by a UE that has not indicated support for CIoT optimizations or not indicated support for S1 mode or received by a UE over non-3GPP access is considered an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). The UE shall reset the registration attempt counter and enter the state 5GMM- REGISTERED.LIMITED-SERVICE. The UE shall enable the E-UTRA capability if it was disabled and disable the N1 mode capability for 3GPP access (see subclause 4.9.2). If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. #62 (No network slices available). The UE shall abort the registration procedure for mobility and periodic registration update procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. Additionally, the UE shall reset the registration attempt counter. The UE receiving the rejected NSSAI in the REGISTRATION REJECT message takes the following actions based on the rejection cause in the rejected S-NSSAI(s): "S-NSSAI not available in the current PLMN or SNPN" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN or SNPN as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, an entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available in the current registration area" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area over the current access until switching off the UE, the UE moving out of the current registration area, the UICC containing the USIM is removed, an entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the failed or revoked NSSAA as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.1 and 4.6.2.2. "S-NSSAI not available due to maximum number of UEs reached" Unless the back-off timer value received along with the S-NSSAI is zero, the UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over the current access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclauses 4.6.1 and 4.6.2.2. NOTE 8: If the back-off timer value received along with the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached is zero as specified in subclause 10.5.7.4a of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12], the UE does not consider the S-NSSAI as the rejected S-NSSAI. If there is one or more S-NSSAIs in the rejected NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", then for each S-NSSAI, the UE shall behave as follows: a) stop the timer T3526 associated with the S-NSSAI, if running; b) start the timer T3526 with: 1) the back-off timer value received along with the S-NSSAI, if a back-off timer value is received along with the S-NSSAI that is neither zero nor deactivated; or 2) an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and c) remove the S-NSSAI from the rejected NSSAI for the maximum number of UEs reached when the timer T3526 associated with the S-NSSAI expires. If the UE has an allowed NSSAI or configured NSSAI and: 1) at least S-NSSAI of the allowed NSSAI or configured NSSAI is not included in the rejected NSSAI, the UE may stay in the current serving cell, apply the normal cell reselection process and start a registration procedure for mobility and periodic registration update with a requested NSSAI that includes any S-NSSAI from the allowed S-NSSAI or the configured NSSAI that is not in the rejected NSSAI. 2) all the S-NSSAI(s) in the allowed NSSAI and configured NSSAI are rejected and at least one S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" and: i) the REGISTRATION REJECT message is integrity protected, the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the REGISTRATION REJECT message and the REGISTRATION REJECT message is received from one of the TAI(s) in the current registration area, the UE shall store the TAI(s) belonging to the registration area in the list of "5GS forbidden tracking areas for roaming". If the REGISTRATION REJECT message is received from a TAI not in the current registration area, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". The UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; or ii) the REGISTRATION REJECT message is integrity protected and the UE is operating in SNPN access operation mode and the REGISTRATION REJECT message is received from one of the TAI(s) in the current registration area, the UE shall store the TAI(s) belonging to current registration area in the list of "5GS forbidden tracking areas for roaming" for the current SNPN. If the REGISTRATION REJECT message is received from a TAI not in the current registration area, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". If the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. 3) otherwise, the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if the UE does not have an allowed NSSAI and each S-NSSAI in the configured NSSAI, if available, was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" as described in subclause 4.9. If the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and, 1) if at least one S-NSSAI in the default configured NSSAI is not rejected, the UE may stay in the current serving cell, apply the normal cell reselection process, and start a registration procedure for mobility and periodic registration update with a requested NSSAI with that default configured NSSAI; or 2) if all the S-NSSAI(s) in the default configured NSSAI are rejected and at least one S-NSSAI is rejected due to "S-NSSAI not available in the current registration area", i) if the REGISTRATION REJECT message is integrity protected and the UE is not operating in SNPN access operation mode and the REGISTRATION REJECT message is received from one of the TAI(s) in the current registration area, the UE shall store the TAI(s) belonging to current registration area in the list of "5GS forbidden tracking areas for roaming". If the REGISTRATION REJECT message is received from a TAI not in the current registration area, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". The UE shall memorize the TAI(s) was stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; or ii) If the REGISTRATION REJECT message is integrity protected and the UE is operating in SNPN access operation mode and the REGISTRATION REJECT message is received from one of the TAI(s) in the current registration area, the UE shall store the TAI(s) belonging to current registration area in the list of "5GS forbidden tracking areas for roaming". If the REGISTRATION REJECT message is received from a TAI not in the current registration area, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming". The UE shall memorize the TAI(s) was stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. 3) otherwise, the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if each S-NSSAI in the default configured NSSAI was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" as described in subclause 4.9. If 1) the UE has allowed NSSAI for the current PLMN or SNPN or configured NSSAI for the current PLMN or SNPN or both and all the S-NSSAIs included in the allowed NSSAI or the configured NSSAI or both are rejected; or 2) the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and all the S-NSSAIs included in the default configured NSSAI are rejected, and the UE has rejected NSSAI for the maximum number of UEs reached, and the UE wants to obtain services in the current serving cell without performing a PLMN selection or SNPN selection, the UE may stay in the current serving cell and attempt to use the rejected S-NSSAI(s) for the maximum number of UEs reached in the current serving cell after the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the tracking area updating attempt counter and enter the state EMM-REGISTERED. #72 (Non-3GPP access to 5GCN not allowed). When received over non-3GPP access the UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter and enter the state 5GMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS, the UE shall set: 1) the PLMN-specific N1 mode attempt counter for non-3GPP access for that PLMN in case of PLMN; or 2) the SNPN-specific attempt counter for non-3GPP access for that SNPN in case of SNPN; to the UE implementation-specific maximum value. NOTE 10: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). The UE shall disable the N1 mode capability for non-3GPP access (see subclause 4.9.3). As an implementation option, the UE may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If received over 3GPP access the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.3.7. #73 (Serving network not authorized). This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs, reset the registration attempt counter, store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A. For 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message has been successfully integrity checked by the NAS, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the tracking area updating attempt counter and enter the state EMM-DEREGISTERED. #74 (Temporarily not authorized for this SNPN). 5GMM cause #74 is only applicable when received from a cell belonging to an SNPN. 5GMM cause #74 received from a cell not belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and store the SNPN identity in the "temporarily forbidden SNPNs" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is not registered for onboarding services in SNPN, for 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and for non-3GPP access the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE amd perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #75 (Permanently not authorized for this SNPN). 5GMM cause #75 is only applicable when received from a cell belonging to an SNPN with a globally-unique SNPN identity. 5GMM cause #75 received from a cell not belonging to an SNPN or a cell belonging to an SNPN with a non-globally-unique SNPN identity is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and store the SNPN identity in the "permanently forbidden SNPNs" or "permanently forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] list for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "permanently forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is not registered for onboarding services in SNPN, for 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and for non-3GPP access the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE amd perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #76 (Not authorized for this CAG or authorized for CAG cells only). This cause value received via non-3GPP access or from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. The UE shall set the 5GS update status to 5U3.ROAMING NOT ALLOWED, store the 5GS update status according to subclause 5.1.3.2.2, and reset the registration attempt counter. If 5GMM cause #76 is received from: 1) a CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the REGISTRATION REJECT message, the UE shall: i) replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN; ii) replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or NOTE 10: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored. iii) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended CAG information list IE does not contain the serving VPLMN's entry. Otherwise, the UE shall delete the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN, if the CAG-ID(s) are authorized based on the "Allowed CAG list". In the case the "allowed CAG list" for the current PLMN only contains a range of CAG-IDs, how the UE deletes the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN is up to UE implementation. In addition: i) if the entry in the "CAG information list" for the current PLMN does not include an "indication that the UE is only allowed to access 5GS via CAG cells" or if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and one or more CAG-ID(s) are authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list"; ii) if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and no CAG-ID is authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list"; or iii) if the "CAG information list" does not include an entry for the current PLMN, then the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list". 2) a non-CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the REGISTRATION REJECT message, the UE shall: i) replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN; ii) replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or NOTE 11: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored. iii) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended CAG information list IE does not contain the serving VPLMN's entry. Otherwise, the UE shall store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN, if any. If the "CAG information list" stored in the UE does not include the current PLMN's entry, the UE shall add an entry for the current PLMN to the "CAG information list" and store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN. If the UE does not have a stored "CAG information list", the UE shall create a new "CAG information list" and add an entry with an "indication that the UE is only allowed to access 5GS via CAG cells" for the current PLMN. In addition: i) if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated CAG information; or ii) if no CAG-ID is authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list". If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED, reset the tracking area updating attempt counter and enter the state EMM-REGISTERED. #77 (Wireline access area not allowed). 5GMM cause #77 is only applicable when received from a wireline access network by the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device). 5GMM cause #77 received from a 5G access network other than a wireline access network and 5GMM cause #77 received by the W-AGF acting on behalf of the FN-BRG are considered as abnormal cases and the behaviour of the UE is specified in subclause 5.5.1.3.7. When received over wireline access network, the 5G-RG and the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2), shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI, shall reset the registration attempt counter, shall enter the state 5GMM-DEREGISTERED and shall act as specified in subclause 5.3.23. NOTE 12: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite NG-RAN cell is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.3.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location" and shall start a corresponding timer instance (see subclause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the normal tracking area updating procedure is rejected with the EMM cause with the same value. #79 (UAS services not allowed). The UE shall abort the registration procedure for mobility and periodic registration update procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. Additionally, the UE shall reset the registration attempt counter. The UE may re-attempt the registration procedure to the current PLMN for services other than UAS services and shall not include the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of REGISTRATION REQUEST message unless the UE receives a CONFIGURATION UPDATE COMMAND message including the service-level-AA service status indication in the Service-level-AA container IE with the UAS field set to "UAS services enabled". If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the tracking area updating attempt counter and enter the state EMM-REGISTERED. #80 (Disaster roaming for the determined PLMN with disaster condition not allowed). The UE shall abort the registration procedure for mobility and periodic registration update procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. Additionally, the UE shall reset the registration attempt counter. The UE shall not attempt to register for disaster roaming on this PLMN for the determined PLMN with disaster condition for a period in the range of 12 to 24 hours. The UE shall not attempt to register for disaster roaming on this PLMN for a period in the range of 3 to 10 minutes. The UE shall perform PLMN selection as described in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the message has been successfully integrity checked by the NAS and the UE maintains the PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition, the UE shall set the PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the tracking area updating attempt counter and enter the state EMM-REGISTERED. #81 (Selected N3IWF is not compatible with the allowed NSSAI). The UE shall abort the registration procedure for mobility and periodic registration update procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. If the N3IWF identifier IE is included in the REGISTRATION REJECT message and the UE supports slice-based N3IWF selection, the UE may use the provided N3IWF identifier IE in N3IWF selection as specified in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18] prior to an immediate consecutive initial registration attempt to the network, otherwise the UE shall ignore the N3IWF identifier IE. #82 (Selected TNGF is not compatible with the allowed NSSAI). The UE shall abort the registration procedure for mobility and periodic registration update procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. If the TNAN information IE is included in the REGISTRATION REJECT message and the UE supports slice-based TNGF selection, the UE may use the provided TNAN information IE in TNAN selection as specified in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18] prior to an immediate consecutive registration attempt to the network, otherwise the UE shall ignore the TNAN information IE. Other values are considered as abnormal cases. The behaviour of the UE in those cases is specified in subclause 5.5.1.3.7. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.5 |
2,082 | 5.4.1 GUTI reallocation procedure 5.4.1.1 General | The purpose of the GUTI reallocation procedure is to allocate a GUTI and optionally to provide one or more of the following to a particular UE: - a new TAI list; - a new DCN-ID; and - in WB-S1 mode, if the UE supports RACS, either a UE radio capability ID deletion indication or a UE radio capability ID. The reallocation of a GUTI is performed by the unique procedure defined in this clause. This procedure can only be initiated by the MME in state EMM-REGISTERED. The GUTI can also be implicitly reallocated at attach or tracking area updating procedures. The implicit reallocation of a GUTI is described in the clauses which specify these procedures (see clause 5.5.1 and 5.5.3). The PLMN identity in the GUTI indicates the current registered PLMN. NOTE 1: The GUTI reallocation procedure is usually performed in ciphered mode. NOTE 2: Normally, the GUTI reallocation will take place in conjunction with another mobility management procedure, e.g. as part of tracking area updating. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1 |
2,083 | 5.16.2 SMS over NAS 5.16.2.1 General | This clause includes feature description for supporting SMS over NAS in 5G System. Support for SMS incurs the following functionality: - Support for SMS over NAS transport between UE and AMF. This applies to both 3GPP and Non 3GPP accesses. - Support for AMF determining the SMSF for a given UE. - Support for subscription checking and actual transmission of MO/MT-SMS transfer by the SMSF. - Support for MO/MT-SMS transmission for both roaming and non-roaming scenarios. - Support for selecting proper domains for MT SMS message delivery including initial delivery and re-attempting in other domains. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.2 |
2,084 | 10.1.4.2 Mapping to physical resources | The sequence shall be multiplied with the amplitude scaling factor and mapped in sequence starting with to the sub-carriers. The set of sub-carriers used in the mapping process shall be identical to the corresponding NPUSCH transmission as defined in clause 10.1.3.6. The mapping to resource elements shall be in increasing order of first, then , and finally the slot number. The values of the symbol index in a slot are given in Table 10.1.4.2-1. Table 10.1.4.2-1: Demodulation reference signal location for NPUSCH. If higher layer parameter resourceReservationConfigUL is configured, then in case of NPUSCH format 1 transmission associated with C-RNTI or SPS C-RNTI using UE-specific NPDCCH search space and the Resource reservation field in the DCI is set to 1 including NPUSCH format 1 transmission without a corresponding NPDCCH, or in case of NPUSCH format 2 transmission associated with C-RNTI using UE-specific NPDCCH search space, - In a subframe for or a slot for that is overlapping with any fully reserved uplink subframe as defined in clause 16.5 in [4], - for , the demodulation reference signal transmission is postponed until the next NB-IoT uplink subframe that is not fully reserved. - for , the demodulation reference signal transmission in the slot is postponed until the next slot spanning over two contiguous uplink subframes not overlapping with any uplink subframe that is fully reserved. - In a subframe for or a slot for that is not overlapping with any fully reserved uplink subframe, any demodulation reference signal transmission in SC-FDMA symbols overlapping with reserved symbols is dropped. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.1.4.2 |
2,085 | 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN | Figure 5.3.8.2-1 shows the case when UE camps on E-UTRAN and Detach Request is sent to MME. Figure 5.3.8.2-1: UE-Initiated Detach Procedure - UE camping on E-UTRAN NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 6, 7 and 8 concern GTP based S5/S8 1. The UE sends NAS message Detach Request (GUTI, Switch Off) to the MME. This NAS message is used to trigger the establishment of the S1 connection if the UE was in ECM-IDLE mode. Switch Off indicates whether detach is due to a switch off situation or not. The eNodeB forwards this NAS message to the MME along with the TAI+ECGI of the cell which the UE is using. If the MME receives a Detach Request via a CSG cell with Switch Off parameter indicating that detach is not due to a switch off situation, and the CSG subscription for this CSG ID and associated PLMN is absent or expired, the MME shall trigger a MME-initiated Detach procedure as specified in clause 5.3.8.3. If Dual Connectivity is active for the UE, the PSCell ID shall be included in the Uplink NAS Transport that carries the Detach Request message. NOTE 2: Security procedures may be invoked if the NAS message is used to establish the S1 connection. NOTE 3: For emergency attached or RLOS attached UEs that were not successfully authenticated, security procedures are not performed. 2. If the UE has no activated PDN connection, then steps 2 to 10 are not executed. If the PLMN has configured secondary RAT usage data reporting, the MME shall wait for step 11, if applicable, and shall perform step 12 before step 2 onwards. For any PDN connection to the SCEF, the MME indicates to the SCEF that the PDN connection for the UE is no longer available according to TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] and steps 2 to 10 are not executed. For PDN connections to the P-GW, the active EPS Bearers in the Serving GW regarding this particular UE are deactivated by the MME sending Delete Session Request (LBI, User Location Information (ECGI), Secondary RAT usage data, PSCell ID) per PDN connection to the Serving GW. If ISR is activated, then the Serving GW shall not release the Control Plane TEID allocated for MME/SGSN until it receives the Delete Session Request message in step 5. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If Secondary RAT usage data report was received from RAN, the MME includes this in the Delete Session Request message. If MME has received PSCell ID from eNodeB, the MME includes it in Delete Session Request. 3. When the S-GW receives the first Delete Session Request message from the MME or SGSN in ISR activated state, the Serving GW deactivates ISR, releases the related EPS Bearer context information and responds with Delete Session Response (Cause). When the S-GW receives the Delete Session Request message from the MME or SGSN in ISR deactivated state, the Serving GW releases the related EPS Bearer context information and jumps to step 6 by sending a Delete Session Request (LBI) message per PDN connection to the PDN GW. After step 7 the Serving GW responds back to the MME/SGSN with the Delete Session Response (Cause and, optionally, APN Rate Control Status according to clause 4.7.7.3) message. 4. If ISR is activated, MME sends Detach Indication (Cause) message to the associated SGSN. The Cause indicates complete detach. 5. The active PDP contexts in the Serving GW regarding this particular UE are deactivated by the SGSN sending Delete Session Request (LBI, CGI/SAI) per PDN connection to the Serving GW. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. 6. If ISR is activated, Serving GW deactivates ISR. If ISR is not activated in the Serving GW, the Serving GW sends Delete Session Request (LBI, User Location Information (ECGI or CGI/SAI), Secondary RAT usage data) per PDN connection to the PDN GW. If ISR is not activated, this step shall be triggered by step 2. This message indicates that all bearers belonging to that PDN connection shall be released. If the MME and/or SGSN sends UE's Location Information, and/or UE Time Zone Information, and/or Secondary RAT usage data in step 2 and/or step 5, the S-GW includes the User Location Information, and/or UE Time Zone, and/or User CSG Information with the least age in this message and/or Secondary RAT usage data information. 7. The PDN GW acknowledges with Delete Session Response (Cause and, optionally, APN Rate Control Status according to clause 4.7.7.3). 8. The PDN GW employs a PCEF initiated IP-CAN Session Termination Procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] with the PCRF to indicate to the PCRF that EPS Bearer is released if PCRF is applied in the network. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. 9. The Serving GW acknowledges with Delete Session Response (Cause and, optionally, APN Rate Control Status). 10. The SGSN sends Detach Acknowledge message to the MME (optionally APN Rate Control Status). If received, the MME stores the APN Rate Control Status in the MM context. 11. If Switch Off indicates that detach is not due to a switch off situation, the MME sends a Detach Accept to the UE. 12. The MME releases the S1-MME signalling connection for the UE by sending S1 Release Command to the eNodeB with Cause set to Detach. The details of this step are covered in the "S1 Release Procedure", as described in clause 5.3.5. NOTE 4: In the "S1 Release Procedure", if Dual Connectivity was active at the time of the release, the eNodeB includes the PSCell ID. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.8.2.1 |
2,086 | 5.3.5.5.9 SCell Addition/Modification | The UE shall: 1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition): 2> add the SCell, corresponding to the sCellIndex, in accordance with the sCellConfigCommon and sCellConfigDedicated; 2> if the sCellState is included: 3> configure lower layers to consider the SCell to be in activated state; 2> else: 3> configure lower layers to consider the SCell to be in deactivated state; 2> for each measId included in the measIdList within VarMeasConfig: 3> if SCells are not applicable for the associated measurement; and 3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId: 4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId; 2> if the SCellConfig contains the goodServingCellEvaluationBFD: 3> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2. 1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification): 2> modify the SCell configuration in accordance with the sCellConfigDedicated; 2> if the sCellToAddModList was received in an RRCReconfiguration message including reconfigurationWithSync, or received in an RRCResume message, or received in an RRCReconfiguration message including reconfigurationWithSync embedded in an RRCResume message or embedded in an RRCReconfiguration message or embedded in an E-UTRA RRCConnectionReconfiguration message or embedded in an E-UTRA RRCConnectionResume message, or received in an RRCReconfiguration message embedded in an RRCReconfiguration message or embedded in an E-UTRA RRCConnectionReconfiguration message activating deactivated SCG: 3> if the sCellState is included: 4> configure lower layers to consider the SCell to be in activated state; 3> else: 4> configure lower layers to consider the SCell to be in deactivated state. 2> if the SCellConfig contains the goodServingCellEvaluationBFD: 3> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.9 |
2,087 | – TimeToTrigger | The IE TimeToTrigger specifies the value range used for time to trigger parameter, which concerns the time during which specific criteria for the event needs to be met in order to trigger a measurement report. Value ms0 corresponds to 0 ms and behaviour as specified in 7.1.2 applies, value ms40 corresponds to 40 ms, and so on. TimeToTrigger information element -- ASN1START -- TAG-TIMETOTRIGGER-START TimeToTrigger ::= ENUMERATED { ms0, ms40, ms64, ms80, ms100, ms128, ms160, ms256, ms320, ms480, ms512, ms640, ms1024, ms1280, ms2560, ms5120} -- TAG-TIMETOTRIGGER-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,088 | 4.7 EPS mobility management and EPS session management in NB-S1 mode | A UE in NB-S1 mode (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) shall calculate the value of the applicable NAS timer: - indicated in table 10.2.1 plus 240s; and - indicated in table 10.3.1 plus 180s. The timer value obtained is used as described in the appropriate procedure clause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted. When an MME that supports NB-S1 mode performs NAS signalling with a UE, which is using NB-S1 mode, the MME shall calculate the value of the applicable NAS timer: - indicated in table 10.2.2 plus 240s; and - indicated in table 10.3.2 plus 180s. The timer value obtained is used as described in the appropriate procedure clause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted. NOTE 1: If the tracking area updating procedure is initiated in EMM-CONNECTED mode, the MME can stop any running implementation specific supervision timer if it is started when sending an ESM DATA TRANSPORT message to the UE. NOTE 2: As NB-S1 mode includes the case when satellite access is used in EPS, the values for applicable NAS timers specified in this clause apply also for satellite access. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7 |
2,089 | 5.2.2.3.7 eCALL-INACTIVE | The UE camps on a suitable cell or an acceptable cell in a PLMN selected as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] but initiates no 5GMM signalling with the network and ignores any paging requests. The UE shall leave substate 5GMM-DEREGISTERED.eCALL-INACTIVE state only when one of the following events occur: a) if the USIM is removed, the UE enters substate 5GMM-DEREGISTERED.NO-SUPI; b) if coverage is lost, the UE enters substate 5GMM-DEREGISTERED.PLMN-SEARCH; c) if the UE is deactivated (e.g. powered off) by the user, the UE enters state 5GMM-NULL; d) if the UE receives a request from upper layers to establish an eCall over IMS, the UE enters state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. The UE then uses the relevant 5GMM and 5GSM procedures to establish the eCall over IMS at the earliest opportunity; or e) if the UE receives a request from upper layers to establish a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service, the UE enters state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. Once the registration procedure is completed, the UE uses the relevant 5GMM and 5GSM procedures to establish the non-emergency call. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.2.3.7 |
2,090 | 10.5.4.21 Progress indicator | The purpose of the progress indicator information element is to describe an event which has occurred during the life of a call. The progress indicator information element is coded as shown in figure 10.5.107/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.127/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The progress indicator is a type 4 information element with a length of 4 octets. Figure 10.5.107/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Progress indicator information element Table 10.5.127/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Progress indicator information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.21 |
2,091 | 5.23 Autonomous Uplink | Autonomous uplink is supported on the SCells only. At most one autonomous uplink configuration is supported per SCell. Multiple autonomous uplink configurations can be activated and be active simultaneously when there is more than one SCell. Autonomous uplink and Uplink Semi-Persistent Scheduling cannot be active simultaneously on the same SCell. When autonomous uplink is configured by RRC, the following information is provided in AUL-Config (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]): - AUL C-RNTI; - HARQ process IDs aul-HARQ-Processes that are configured for autonomous UL HARQ operation, the time period aul-RetransmissionTimer before triggering a new transmission or a retransmission of the same HARQ process using autonomous uplink; - The bitmap aul-Subframes that indicates the subframes that are configured for autonomous UL HARQ operation. When the autonomous uplink configuration is released by RRC, the corresponding configured grant shall be cleared. If AUL-Config is configured, the MAC entity shall: - consider that a configured uplink grant occurs in those subframes for which aul-Subframes is set to 1 (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). If AUL confirmation has been triggered and not cancelled: - if the MAC entity has UL resources allocated for new transmission for this TTI: - instruct the Multiplexing and Assembly procedure to generate an AUL confirmation MAC Control Element as defined in clause 6.1.3.16; - cancel the triggered AUL confirmation. The MAC entity shall clear the configured uplink grant for the SCell immediately after first transmission of AUL confirmation MAC Control Element triggered by the AUL release for this SCell. NOTE: Retransmissions for uplink transmissions using autonomous uplink can continue after clearing the corresponding configured uplink grant. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.23 |
2,092 | 5.34.9 Support of the Deployment Topologies with specific SMF Service Areas feature within and between PLMN(s) | When Deployments Topologies with specific SMF Service Areas need to be used in a PLMN for a S-NSSAI, all AMF serving this S-NSSAI are configured to support Deployments Topologies with specific SMF Service Areas. NOTE 1: The specifications do not support AMF selection related with Deployment Topologies with specific SMF Service Areas. For HR roaming, the AMF discovers at PDU Session establishment whether a H-SMF supports V-SMF change based on feature support indication received from the NRF, possibly via the SCP. When the V-PLMN requires Deployments Topologies with specific SMF Service Areas but no H-SMF can be selected that supports V-SMF change, a H-SMF not supporting V-SMF change may be selected by the VPLMN. In that case, and if a V-SMF serving the full VPLMN is available, AMF should prefer to select such V-SMF. In this release of the specifications, when an AMF detects the need to change the V-SMF while the H-SMF does not support V-SMF change, the AMF shall not trigger V-SMF change but shall trigger the release of the PDU Session. NOTE 2: The AMF can determine whether the H-SMF supports V-SMF change based on NRF look up. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34.9 |
2,093 | 9.12.1.1 FDD | For the parameters specified in Table 9.12.1.1-1, Table 9.12.1.1-2 and Table 9.12.1.1-3 using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.12.1.1-4 by the following a) a CQI index not in the set {median CQI -1, median CQI, median CQI +1} shall be reported at least % of the time; b) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index and that obtained when transmitting a fixed transport format configured according to the wideband CQI median shall be ≥ ; c) when transmitting the transport format indicated by each reported wideband CQI index, the average BLER for the indicated transport formats shall be greater or equal to 0.02. Table 9.12.1.1-1: Fading test for slot-PDSCH (FDD) Table 9.12.1.1-2: Fading test for subslot-PDSCH (FDD) Table 9.12.1.1-3: SPDCCH parameters (FDD) Table 9.12.1.1-4: Minimum requirement for slot/subslot-PDSCH (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.12.1.1 |
2,094 | 4.1.1.2.1 GPRS MS operating in mode A or B in a network that operates in mode I | If the network operates in mode I, GPRS MSes that operate in mode A or B and wish to be or are simultaneously IMSI attached for GPRS and non-GPRS services, shall use the combined GPRS attach and the combined and periodic routing area updating procedures instead of the corresponding MM specific procedures IMSI attach and normal and periodic location area updating. A GPRS MS operating in mode A or B in a network that operates in mode I, shall perform the combined GPRS attach or routing area update procedure regardless the value of the ATT flag. If a GPRS MS is operating in mode A or B in a network that operates in mode I the IMSI detach shall be performed by the GMM using the combined GPRS detach procedure. A GPRS MS operating in mode A or B in a network that operates in mode I, shall perform the combined GPRS detach procedure regardless the value of the ATT flag. A GPRS MS operating in mode A or B in network that operates in mode I, shall use the combined GMM specific procedures in place of the MM specific procedures unless the re-activation of the MM specific procedures is explicitly described, so all conditions describing when to trigger an MM specific procedure listed in subclauses 4.3 and 4.4 shall not apply. A GPRS MS operating in mode A or B in a network that operates in mode I should not use any MM timers relating to MM specific procedures, (e.g. T3210, T3211, T3212, T3213) unless the re-activation of the MM specific procedures is explicitly described. If the MM timers are already running, the MS should not react on the expiration of the timers. NOTE 1: Whenever GMM performs a combined GMM procedure, a GPRS MS enters the MM state MM LOCATION UPDATING PENDING in order to prevent the MM from performing a location area updating procedure. If the authentication procedure is performed by MM and the authentication is rejected by the network (i.e. upon receive of AUTHENTICATION REJECT), the MS shall in addition set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall, if available, delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number stored. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. The MS shall abort any GMM procedure and shall enter state GMM-DEREGISTERED. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the EPS authentication is not accepted by the network. If the PS or CS domain is barred because of domain specific access control, a GPRS MS operating in mode A or B in a network that operates in mode I shall act as if in network operation mode II and access to the barred domain shall be stopped entirely. If the MS detects that a domain is barred, this shall not trigger any MM or GMM specific procedure. A GPRS MS operating in mode A or B in a network that operates in mode I shall perform a normal location updating procedure (in order to remove the Gs association in the MSC/VLR) when the following conditions are fulfilled: - the GPRS MS has camped on a cell where the PS domain is barred and the CS domain is unbarred; and - T3312, T3311, T3302, or T3330 expires; and - for the last attempt to update the registration of the location area a combined GMM procedure was performed. Additionally the MS shall treat the expiry of T3312 when the PS domain changes from barred to unbarred, analogous to the descriptions for the cases when the timer expires out of coverage or in a cell that does not support GPRS (see subclause 4.7.2.2). If timer T3312 expires and both the PS and CS domain are barred, then a GPRS MS operating in mode A or B in a network that operates in mode I shall treat the expiry of T3312 when the GPRS MS detects that the PS or CS domain becomes unbarred, analogous to the descriptions for the cases when the timer expires out of coverage (see subclause 4.7.2.2). If the PS domain is barred and timer T3312 expires during an ongoing CS connection, then a GPRS MS operating in mode A or B in a network that operates in mode I shall treat the expiry of T3312 when the MM state MM-IDLE is entered, analogous to the descriptions for the cases when the timer expires out of coverage or in a cell that does not support GPRS (see subclause 4.7.2.2), or in a cell where the PS domain is barred. A GPRS MS operating in mode A or B in a network that operates in mode I shall perform a combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" (in order to establish the Gs association in the MSC/VLR) when the following conditions are fulfilled: - the GPRS MS detects that CS or PS domain or both change from barred to unbarred; - as a result of the change of the domain specific barring status, both domains are unbarred; and - for the last attempt to update the registration of the location area an MM specific procedure was performed (see subclause 4.7.5.2.1) or for the last attempt to update the registration of the routing area a normal routing area update was performed. A GPRS MS operating in mode A or B on a PLMN which is part of "forbidden PLMNs for GPRS service" list in a network that is operating in mode I shall act as if in network operation mode II and proceed with appropriate MM procedures. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.2.1 |
2,095 | 12.2.7 Issues in the network with partial support of the feature | The Load Control feature should be supported homogenously across all the SGWs and PGWs in the network. Not supporting this feature homogeneously across the SGWs and PGWs may result in poor load balancing in the network such that the SGWs or PGWs not supporting the feature may operate near their maximum capacity (thus being more vulnerable to overload conditions) while SGWs or PGWs supporting the feature have free capacity. The Load Control feature should be supported homogenously across all the MMEs, S4-SGSNs, ePDGs and TWANs. However, use of the feature when not all of these nodes support the feature may not necessarily create a problem since the load may remain fairly balanced across the SGWs and PGWs assuming that the network imbalance caused by the non-supporting node may get rectified by the supporting nodes making use of dynamic load information while selecting the SGWs and PGWs. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.2.7 |
2,096 | 5.6.2.2.1 Paging for EPS services through E-UTRAN using S-TMSI | 5.6.2.2.1.1 General The network shall initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" when: - NAS signalling messages, cdma2000® signalling messages or user data is pending to be sent to the UE; - no NAS signalling connection exists (see example in figure 5.6.2.2.1.1); and - there is no paging restriction applied in the network for that paging. If the network has downlink user data pending for a UE, the MME has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to: a) "All paging is restricted", the network should not initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE; b) "All paging is restricted except for voice service", the network should initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE only when: 1) the pending downlink user data for the UE is considered as voice service related by the network; c) "All paging is restricted except for specified PDN connection(s)", the network should initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE only when: 1) for PDN connection(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending; or d) "All paging is restricted except for voice service and specified PDN connection(s)", the network should initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE only when: 1) the pending downlink user data for the UE is considered as voice service related by the network; or 2) for PDN connection(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending. If the network has downlink signalling pending for a UE and the MME has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to: a) "All paging is restricted", the network should not initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE; b) "All paging is restricted except for voice service", the network should initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE only when: 1) the pending downlink signalling for the UE is EMM signalling or ESM signalling of the PDN connection of voice service; c) "All paging is restricted except for specified PDN connection(s)", the network should initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE only when: 1) the pending downlink signalling for the UE is EMM signalling; or 2) for PDN connection(s) that paging is not restricted based on the stored paging restriction, the network has downlink ESM signalling pending; or d) "All paging is restricted except for voice service and specified PDN connection(s)", the network should initiate the paging procedure for EPS services using S-TMSI with CN domain indicator set to "PS" for the UE only when: 1) the pending downlink signalling for the UE is EMM signalling or ESM signalling of the PDN connection of voice service; or 2) for PDN connection(s) that paging is not restricted based on the stored paging restriction, the network has downlink ESM signalling pending. NOTE 1: If the network pages the UE due to downlink signalling pending, the network initiates the release of the NAS signalling connection after network-requested procedure is completed. For the UE using eDRX, the network initiates the paging procedure when NAS signalling messages, cdma2000® signalling messages or user data is pending to be sent to the UE within the paging time window. If NAS signalling messages, cdma2000® signalling messages or user data is pending to be sent to the UE outside the paging time window and the eDRX value that the network provides to the UE in the Extended DRX parameters IE during the last attach procedure or the last tracking area updating procedure is not all zeros (i.e. the E-UTRAN eDRX cycle length duration is higher than 5.12 seconds), the network initiates the paging procedure at T time ahead of the beginning of the next paging time window. NOTE 2: T time is a short time period based on implementation. The operator can take possible imperfections in the synchronization between the CN and the UE into account when choosing T time. Figure 5.6.2.2.1.1: Paging procedure using S-TMSI To initiate the procedure the EMM entity in the network requests the lower layer to start paging (see 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20], 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]) and shall start the timer: - T3415 for this paging procedure, if the network accepted to use eDRX for the UE and the UE does not have a PDN connection for emergency bearer services. - Otherwise, T3413 for this paging procedure. If the network detects that the pending user data to be sent to the UE is related to the voice service as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [7] and the network decides to initiate the paging procedure based on the stored paging restriction information, if any, the EMM entity in the network should request the lower layer to include the Voice Service Indication in the Paging message when the UE and the network support the paging indication for voice services. If the network starts timer T3415, the network shall set timer T3415 to a value smaller than the value of timer T3-RESPONSE (see 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [16D] for further details on timer T3-RESPONSE). The EMM entity may provide the lower layer with a list of CSG IDs, including the CSG IDs of both the expired and the not expired subscriptions. If there is a PDN connection for emergency bearer services established, the EMM entity in the network shall not provide the list of CSG IDs to the lower layer. If the negotiated UE paging probability information is available in the EMM context of the UE, the EMM entity shall provide the lower layer with the negotiated UE paging probability information (see 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20], 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]). Upon reception of a paging indication, if control plane CIoT EPS optimization is not used by the UE, the UE shall stop the timer T3346, if running, and shall initiate: - a service request procedure to respond to the paging (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] and 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]); or - a tracking area updating procedure as specified in clauses 5.5.3.2.2 and 5.5.3.3.2. and additionally if the UE is in the EMM-IDLE mode with suspend indication, resume the suspended NAS signalling connection to the MME as specified in clause 5.3.1.3. Upon reception of a paging indication, if control plane CIoT EPS optimization is used by the UE, the UE shall stop the timer T3346, if running, and shall additionally: - initiate a service request procedure as specified in clause 5.6.1.2.2 if the UE is in the EMM-IDLE mode without suspend indication; - initiate a tracking area updating procedure as specified in clauses 5.5.3.2.2; or - proceed the behaviour as specified in clause 5.3.1.3 if the UE is in the EMM-IDLE mode with suspend indication. NOTE 3: If the UE is in the EMM-IDLE mode without suspend indication and has an uplink user data to be sent to the network using control plane CIoT EPS optimization when receiving the paging indication, the UE can piggyback the uplink user data during the service request procedure initiated to respond to the paging, as specified in clause 5.6.1.2.2. Upon reception of a paging indication, if the network supports the reject paging request and the MUSIM UE decides not to accept the paging, the UE may initiate a service request procedure to reject the paging as specified in clause 5.6.1.1. NOTE 4: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. If the paging for EPS services was received during an ongoing UE-initiated EMM specific procedure or service request procedure, then the UE shall ignore the paging. The network shall proceed with the EMM specific procedure or the service request procedure, and stop the timer for the paging procedure (i.e. either timer T3413 or timer T3415). If the network receives an ATTACH REQUEST message when the paging procedure is ongoing, it should be considered as an abnormal case, and the behaviour of the network for this case is specified in clause 5.6.2.2.1.2. The network shall stop the timer for the paging procedure (i.e. either timer T3413 or timer T3415) when an integrity-protected response is received from the UE and successfully integrity checked by the network or when the EMM entity in the MME receives an indication from the lower layer that it has received the S1-AP UE context resume request message as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]. If the response received is not integrity protected, or the integrity check is unsuccessful, the timer for the paging procedure (i.e. either timer T3413 or timer T3415) shall be kept running unless: - the UE has a PDN connection for emergency bearer services; or - the response received is a TRACKING AREA UPDATE REQUEST message and the security mode control procedure or authentication procedure performed during tracking area updating procedure has completed successfully. Upon expiry of timer T3413, the network may reinitiate paging. If the network, while waiting for a response to the paging sent without paging priority, receives downlink signalling or downlink data associated with priority EPS bearers, the network shall stop the timer for the paging procedure (i.e. either timer T3413 or timer T3415), and then initiate the paging procedure with paging priority. Upon expiry of timer T3415, the network shall abort the paging procedure and shall proceed as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. 5.6.2.2.1.2 Abnormal cases on the network side The following abnormal case can be identified: a) ATTACH REQUEST message received when paging procedure is ongoing. If an integrity-protected ATTACH REQUEST message is received from the UE and successfully integrity checked by the network, the network shall abort the paging procedure. If the ATTACH REQUEST message received is not integrity protected, or the integrity check is unsuccessful, the paging procedure shall be progressed. The paging procedure shall be aborted when the EPS authentication procedure performed during attach procedure is completed successfully. 5.6.2.2.1.3 Abnormal cases in the UE The following abnormal case can be identified: a) The paging indication received for a UE that is attached for access to RLOS A UE attached for access to RLOS shall ignore the paging indication from the network. b) The paging indication received when UE-initiated EMM specific procedure or service request procedure is ongoing. The UE shall ignore the paging indication from the network. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.2.2.1 |
2,097 | – MeasAndMobParameters | The IE MeasAndMobParameters is used to convey UE capabilities related to measurements for radio resource management (RRM), radio link monitoring (RLM) and mobility (e.g. handover). MeasAndMobParameters information element -- ASN1START -- TAG-MEASANDMOBPARAMETERS-START MeasAndMobParameters ::= SEQUENCE { measAndMobParametersCommon MeasAndMobParametersCommon OPTIONAL, measAndMobParametersXDD-Diff MeasAndMobParametersXDD-Diff OPTIONAL, measAndMobParametersFRX-Diff MeasAndMobParametersFRX-Diff OPTIONAL } MeasAndMobParameters-v1700 ::= SEQUENCE { measAndMobParametersFR2-2-r17 MeasAndMobParametersFR2-2-r17 OPTIONAL } MeasAndMobParametersCommon ::= SEQUENCE { supportedGapPattern BIT STRING (SIZE (22)) OPTIONAL, ssb-RLM ENUMERATED {supported} OPTIONAL, ssb-AndCSI-RS-RLM ENUMERATED {supported} OPTIONAL, ..., [[ eventB-MeasAndReport ENUMERATED {supported} OPTIONAL, handoverFDD-TDD ENUMERATED {supported} OPTIONAL, eutra-CGI-Reporting ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting ENUMERATED {supported} OPTIONAL ]], [[ independentGapConfig ENUMERATED {supported} OPTIONAL, periodicEUTRA-MeasAndReport ENUMERATED {supported} OPTIONAL, handoverFR1-FR2 ENUMERATED {supported} OPTIONAL, maxNumberCSI-RS-RRM-RS-SINR ENUMERATED {n4, n8, n16, n32, n64, n96} OPTIONAL ]], [[ nr-CGI-Reporting-ENDC ENUMERATED {supported} OPTIONAL ]], [[ eutra-CGI-Reporting-NEDC ENUMERATED {supported} OPTIONAL, eutra-CGI-Reporting-NRDC ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting-NEDC ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting-NRDC ENUMERATED {supported} OPTIONAL ]], [[ reportAddNeighMeasForPeriodic-r16 ENUMERATED {supported} OPTIONAL, condHandoverParametersCommon-r16 SEQUENCE { condHandoverFDD-TDD-r16 ENUMERATED {supported} OPTIONAL, condHandoverFR1-FR2-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, nr-NeedForGap-Reporting-r16 ENUMERATED {supported} OPTIONAL, supportedGapPattern-NRonly-r16 BIT STRING (SIZE (10)) OPTIONAL, supportedGapPattern-NRonly-NEDC-r16 ENUMERATED {supported} OPTIONAL, maxNumberCLI-RSSI-r16 ENUMERATED {n8, n16, n32, n64} OPTIONAL, maxNumberCLI-SRS-RSRP-r16 ENUMERATED {n4, n8, n16, n32} OPTIONAL, maxNumberPerSlotCLI-SRS-RSRP-r16 ENUMERATED {n2, n4, n8} OPTIONAL, mfbi-IAB-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting-NPN-r16 ENUMERATED {supported} OPTIONAL, idleInactiveEUTRA-MeasReport-r16 ENUMERATED {supported} OPTIONAL, idleInactive-ValidityArea-r16 ENUMERATED {supported} OPTIONAL, eutra-AutonomousGaps-r16 ENUMERATED {supported} OPTIONAL, eutra-AutonomousGaps-NEDC-r16 ENUMERATED {supported} OPTIONAL, eutra-AutonomousGaps-NRDC-r16 ENUMERATED {supported} OPTIONAL, pcellT312-r16 ENUMERATED {supported} OPTIONAL, supportedGapPattern-r16 BIT STRING (SIZE (2)) OPTIONAL ]], [[ -- R4 19-2 Concurrent measurement gaps concurrentMeasGap-r17 CHOICE { concurrentPerUE-OnlyMeasGap-r17 ENUMERATED {supported}, concurrentPerUE-PerFRCombMeasGap-r17 ENUMERATED {supported} } OPTIONAL, -- R4 19-1 Network controlled small gap (NCSG) nr-NeedForGapNCSG-Reporting-r17 ENUMERATED {supported} OPTIONAL, eutra-NeedForGapNCSG-Reporting-r17 ENUMERATED {supported} OPTIONAL, -- R4 19-1-1 per FR Network controlled small gap (NCSG) ncsg-MeasGapPerFR-r17 ENUMERATED {supported} OPTIONAL, -- R4 19-1-2 Network controlled small gap (NCSG) supported patterns ncsg-MeasGapPatterns-r17 BIT STRING (SIZE(24)) OPTIONAL, -- R4 19-1-3 Network controlled small gap (NCSG) supported NR-only patterns ncsg-MeasGapNR-Patterns-r17 BIT STRING (SIZE(24)) OPTIONAL, -- R4 19-3-2 pre-configured measurement gap preconfiguredUE-AutonomousMeasGap-r17 ENUMERATED {supported} OPTIONAL, -- R4 19-3-1 pre-configured measurement gap preconfiguredNW-ControlledMeasGap-r17 ENUMERATED {supported} OPTIONAL, handoverFR1-FR2-2-r17 ENUMERATED {supported} OPTIONAL, handoverFR2-1-FR2-2-r17 ENUMERATED {supported} OPTIONAL, -- RAN4 14-1: per-FR MG for PRS measurement independentGapConfigPRS-r17 ENUMERATED {supported} OPTIONAL, rrm-RelaxationRRC-ConnectedRedCap-r17 ENUMERATED {supported} OPTIONAL, -- R4 25-3: Parallel measurements with multiple measurement gaps parallelMeasurementGap-r17 ENUMERATED {n2} OPTIONAL, condHandoverWithSCG-NRDC-r17 ENUMERATED {supported} OPTIONAL, gNB-ID-LengthReporting-r17 ENUMERATED {supported} OPTIONAL, gNB-ID-LengthReporting-ENDC-r17 ENUMERATED {supported} OPTIONAL, gNB-ID-LengthReporting-NEDC-r17 ENUMERATED {supported} OPTIONAL, gNB-ID-LengthReporting-NRDC-r17 ENUMERATED {supported} OPTIONAL, gNB-ID-LengthReporting-NPN-r17 ENUMERATED {supported} OPTIONAL ]], [[ -- R4 25-1: Parallel measurements on multiple SMTC-s for a single frequency carrier parallelSMTC-r17 ENUMERATED {n4} OPTIONAL, -- R4 19-2-1 Concurrent measurement gaps for EUTRA concurrentMeasGapEUTRA-r17 ENUMERATED {supported} OPTIONAL, serviceLinkPropDelayDiffReporting-r17 ENUMERATED {supported} OPTIONAL, -- R4 19-1-4 Network controlled small gap (NCSG) performing measurement based on flag deriveSSB-IndexFromCellInter ncsg-SymbolLevelScheduleRestrictionInter-r17 ENUMERATED {supported} OPTIONAL ]], [[ eventD1-MeasReportTrigger-r17 ENUMERATED {supported} OPTIONAL, independentGapConfig-maxCC-r17 SEQUENCE { fr1-Only-r17 INTEGER (1..32) OPTIONAL, fr2-Only-r17 INTEGER (1..32) OPTIONAL, fr1-AndFR2-r17 INTEGER (1..32) OPTIONAL } OPTIONAL ]], [[ interSatMeas-r17 ENUMERATED {supported} OPTIONAL, deriveSSB-IndexFromCellInterNon-NCSG-r17 ENUMERATED {supported} OPTIONAL ]], [[ -- R4 31-1 Enhanced L3 measurement reporting for unknown SCell activation if the valid L3 measurement results are available l3-MeasUnknownSCellActivation-r18 ENUMERATED {supported} OPTIONAL, -- R4 31-3 Shorter measurement interval for unknown SCell activation shortMeasInterval-r18 ENUMERATED {supported} OPTIONAL, nr-NeedForInterruptionReport-r18 ENUMERATED {supported} OPTIONAL, measSequenceConfig-r18 ENUMERATED {supported} OPTIONAL, cellIndividualOffsetPerMeasEvent-r18 ENUMERATED {supported} OPTIONAL ]] } MeasAndMobParametersXDD-Diff ::= SEQUENCE { intraAndInterF-MeasAndReport ENUMERATED {supported} OPTIONAL, eventA-MeasAndReport ENUMERATED {supported} OPTIONAL, ..., [[ handoverInterF ENUMERATED {supported} OPTIONAL, handoverLTE-EPC ENUMERATED {supported} OPTIONAL, handoverLTE-5GC ENUMERATED {supported} OPTIONAL ]], [[ sftd-MeasNR-Neigh ENUMERATED {supported} OPTIONAL, sftd-MeasNR-Neigh-DRX ENUMERATED {supported} OPTIONAL ]], [[ dummy ENUMERATED {supported} OPTIONAL ]] } MeasAndMobParametersFRX-Diff ::= SEQUENCE { ss-SINR-Meas ENUMERATED {supported} OPTIONAL, csi-RSRP-AndRSRQ-MeasWithSSB ENUMERATED {supported} OPTIONAL, csi-RSRP-AndRSRQ-MeasWithoutSSB ENUMERATED {supported} OPTIONAL, csi-SINR-Meas ENUMERATED {supported} OPTIONAL, csi-RS-RLM ENUMERATED {supported} OPTIONAL, ..., [[ handoverInterF ENUMERATED {supported} OPTIONAL, handoverLTE-EPC ENUMERATED {supported} OPTIONAL, handoverLTE-5GC ENUMERATED {supported} OPTIONAL ]], [[ maxNumberResource-CSI-RS-RLM ENUMERATED {n2, n4, n6, n8} OPTIONAL ]], [[ simultaneousRxDataSSB-DiffNumerology ENUMERATED {supported} OPTIONAL ]], [[ nr-AutonomousGaps-r16 ENUMERATED {supported} OPTIONAL, nr-AutonomousGaps-ENDC-r16 ENUMERATED {supported} OPTIONAL, nr-AutonomousGaps-NEDC-r16 ENUMERATED {supported} OPTIONAL, nr-AutonomousGaps-NRDC-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, cli-RSSI-Meas-r16 ENUMERATED {supported} OPTIONAL, cli-SRS-RSRP-Meas-r16 ENUMERATED {supported} OPTIONAL, interFrequencyMeas-NoGap-r16 ENUMERATED {supported} OPTIONAL, simultaneousRxDataSSB-DiffNumerology-Inter-r16 ENUMERATED {supported} OPTIONAL, idleInactiveNR-MeasReport-r16 ENUMERATED {supported} OPTIONAL, -- R4 6-2: Support of beam level Early Measurement Reporting idleInactiveNR-MeasBeamReport-r16 ENUMERATED {supported} OPTIONAL ]], [[ increasedNumberofCSIRSPerMO-r16 ENUMERATED {supported} OPTIONAL ]] } MeasAndMobParametersFR2-2-r17 ::= SEQUENCE { handoverInterF-r17 ENUMERATED {supported} OPTIONAL, handoverLTE-EPC-r17 ENUMERATED {supported} OPTIONAL, handoverLTE-5GC-r17 ENUMERATED {supported} OPTIONAL, idleInactiveNR-MeasReport-r17 ENUMERATED {supported} OPTIONAL, ... } -- TAG-MEASANDMOBPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,098 | 9.4.11 Authentication and ciphering reject | This message is sent by the network to the MS to indicate that authentication has failed (and that the receiving MS shall abort all activities). See table 9.4.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: AUTHENTICATION AND CIPHERING REJECT Significance: dual Direction: network to MS Table 9.4.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : AUTHENTICATION AND CIPHERING REJECT message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.11 |
2,099 | 4.11.1.5.3 Tracking Area Update | The following changes are applied to clause 5.3.3.1 (Tracking area update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]: - Step 2: The UE shall in Access Stratum signalling include GUMMEI that is mapped from 5G-GUTI following the mapping rules specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the UE indicates it as a native GUMMEI and should in addition indicate it as "Mapped from 5G-GUTI". The UE shall, in the TAU request message, include EPS GUTI that is mapped from 5G-GUTI following the mapping rules specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE indicates that it is moving from 5GC. The UE integrity protects the TAU request message using the 5G security context. If the UE supports any of the CIoT 5GS Optimisations included in 5GC Preferred Network Behaviour, then the UE shall include its 5GC Preferred Network Behaviour if it included its EPC Preferred Network Behaviour in the TAU request. MME may steer the UE from EPC by rejecting the TAU request with an appropriate cause value. The MME should take into account availability of 5GC to the UE and the Preferred and Supported Network Behaviour (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) before steering the UE from EPC. - Step 5 and message Context Response may include new information Return preferred. Return preferred is an indication by the AMF of a preferred return of the UE to the last used 5GS PLMN at a later access change to a 5GS shared network. RFSP in Use Validity Time is provided by the AMF to the MME if the AMF selects the RFSP Index in use identical to the authorized RFSP Index as specified in clause 5.4.3.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and validity time is received from PCF as specified in clause 4.16.2.2 and in clause 6.1.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The MME handles RFSP Index as specified in clause 4.11.1.5.8. The MME may store the last used 5GS PLMN ID in UE's MM Context. The MME may provide E-UTRAN with a Handover Restriction List taking into account the last used 5GS PLMN ID and the Return Preferred indication. The Handover Restriction List contains a list of PLMN IDs as specified by TS 23.251[ Network sharing; Architecture and functional description ] [35]. - Step 9a IP-CAN Session Modification procedure: It is replaced by SM Policy Association Modification as specified in clause 4.16.5. - Step 13 and HSS use of Cancel Location The HSS/UDM de-registers any old AMF node by sending an Nudm_UECM_DeregistrationNotification service operation to the registered AMF for 3GPP access. The registered AMF for 3GPP access initiates AM Policy Association Termination procedure as defined in clause 4.16.3.2 and UE Policy Association Termination procedure as defined in clause 4.16.13.1. - Step 17: If the DNN and SMF+PGW-C FQDN for S5/S8 interface association exist, the HSS/UDM sends APN mapped form DNN and SMF+PGW-C FQDN for S5/S8 to UE. - Step 20 and MME processing of the partial Tracking Area Update (TAU) procedure. The MME may use an indication Return preferred from Context Response at step 6 when deciding the PLMN list content. The MME may provide the eNodeB with a PLMN list. The Handover Restriction List contains a list of PLMN IDs as specified by TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.5.3 |
2,100 | 4.17.5 NF/NF service discovery across PLMNs in the case of discovery made by NF service consumer | In the case that the NF service consumer intends to discover the NF/NF service in home PLMN, the NRF in serving PLMN needs to request "NF Discovery" service from NRF in the home PLMN. The procedure is depicted in the figure below: Figure 4.17.5-1: NF/NF service discovery across PLMNs 1. The NF service consumer in the serving PLMN invokes Nnrf_NFDiscovery_Request (Expected Service Name, NF type of the expected NF, home PLMN ID, serving PLMN ID, NF type of the NF service consumer) to an appropriate configured NRF in the serving PLMN. The request may also include optionally producer NF Set ID, NF Service Set ID, S-NSSAI, NSI ID if available and other service related parameters. A complete list of parameters is provided in service definition in clause 5.2.7.3.2. NOTE 1: The use of NSI ID within a PLMN depends on the network deployment. 2. The NRF in serving PLMN identifies NRF in home PLMN (hNRF) based on the home PLMN ID and it requests "NF Discovery" service from NRF in home PLMN according the procedure in Figure 4.17.4-1 to get the expected NF profile(s) of the NF instance(s) deployed in the home PLMN. As the NRF in the serving PLMN triggers the "NF Discovery" on behalf of the NF service consumer, the NRF in the serving PLMN shall not replace the information of the service requester NF, i.e. NF consumer ID, in the Discovery Request message it sends to the hNRF. The hNRF may further query an appropriate local NRF in the home PLMN based on the input information received from NRF of the serving PLMN. The FQDN of the local NRF or Endpoint Address of local NRF's NF Discovery service in the home PLMN may be configured in the hNRF or may need to be discovered based on the input information. 3. The NRF in serving PLMN provides same as step 3 in clause 4.17.4 applies. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.5 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.