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
⌀ |
|---|---|---|---|---|---|---|---|
3,901 | 7.1 Group Identities | Logical groups of subscribers to the Voice Group Call Service or to the Voice Broadcast Service are identified by a Group Identity (Group ID). Group IDs for VGCS are unique within a PLMN. Likewise, Group IDs for VBS are unique within a PLMN. However, no uniqueness is required between the sets of Group IDs. These sets may be intersecting or even identical, at the option of the network operator. The Group ID is a number with a maximum value depending on the composition of the voice group call reference or voice broadcast call reference defined in clause 7.3. For definition of Group ID on the radio interface, A interface and Abis interface, see 3GPP TS 44.068[ Group Call Control (GCC) protocol ] [46] and 3GPP TS 44.069[ Broadcast Call Control (BCC) protocol ] [47]. For definition of Group ID coding on MAP protocol interfaces, see 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [31]. VGCS or VBS shall also be provided for roaming. If this applies, certain Group IDs shall be defined as supra-PLMN Group IDs which have to be co-ordinated between the network operators and which shall be known in the networks and in the SIM. The format of the Group ID is identical for VBS and VGCS. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 7.1 |
3,902 | A.31 Monitoring of user data transmission via WLAN for LWIP | For LWIP, the IP Packets transferred between the UE and LWIP-SeGW are encapsulated using IPsec in order to provide security to the packets that traverse WLAN. The end to end path between the UE and eNB via the WLAN network is referred to as the LWIP tunnel. A single IPSec tunnel is used per UE for all the data bearers that are configured to send and/ or receive data over WLAN. Each data bearer may be configured so that traffic for that bearer can be routed over the IPsec tunnel in only downlink, only uplink, or both uplink and downlink over WLAN. The operator needs to know the performance regarding user data transmission via WLAN for LWIP. | 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 | A.31 |
3,903 | 5.9.10 UE Radio Capability ID | The UE Radio Capability ID is a short pointer with format defined in TS 23.003[ Numbering, addressing and identification ] [19] that is used to uniquely identify a set of UE Radio Capabilities (excluding UTRAN and NB-IoT capabilities). The UE Radio Capability ID is assigned either by the serving PLMN or by the UE manufacturer, as follows: - UE manufacturer-assigned: The UE Radio Capability ID may be assigned by the UE manufacturer in which case it includes a UE manufacturer identification (i.e. a Vendor ID). In this case, the UE Radio Capability ID uniquely identifies a set of UE radio capabilities and the UE Radio Capability for Paging for a UE by this manufacturer in any PLMN. - PLMN-assigned: If a UE manufacturer-assigned UE Radio Capability ID is not used by the UE or the serving network, or it is not recognised by the serving PLMN UCMF, the UCMF may allocate UE Radio Capability IDs for the UE corresponding to each different set of UE radio capabilities the PLMN may receive from the UE at different times. In this case, the UE Radio Capability IDs the UE receives are applicable to the serving PLMN and uniquely identify the corresponding sets of UE radio capabilities and and the UE Radio Capability for Paging(s) in this PLMN. The PLMN assigned UE Radio Capability ID includes a Version ID in its format. The value of the Version ID is the one configured in the UCMF, at time the UE Radio Capability ID value is assigned. The Version ID value makes it possible to detect whether a UE Radio Capability ID is current or outdated. NOTE: For the case the PLMN is configured to store PLMN assigned IDs in the UE manufacturer-assigned operation requested list defined in clause 5.4.4.1a, then the algorithm for assignment of PLMN-assigned UE Radio Capability ID shall assign different UE Radio Capability IDs for UEs with different TAC value. The type of UE Radio Capability ID (UE manufacturer-assigned or PLMN-assigned) is distinguished when a UE Radio Capability ID is signalled. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.10 |
3,904 | 4.2.2.2 Registration procedures 4.2.2.2.2 General Registration | Figure 4.2.2.2.2-1: Registration procedure 1. UE to (R)AN: AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, [last visited TAI (if available)], Security parameters, [Requested NSSAI], [Mapping Of Requested NSSAI], [Default Configured NSSAI Indication], [UE Radio Capability Update], [UE MM Core Network Capability], [PDU Session status], [List Of PDU Sessions To Be Activated], [Follow-on request], [MICO Indication], [Requested Active Time], [Requested DRX parameters for E-UTRA and NR], [Requested DRX parameters for NB-IoT], [extended idle mode DRX parameters], [LADN DNN(s) or Indicator Of Requesting LADN Information], [NAS message container], [Support for restriction of use of Enhanced Coverage], [Preferred Network Behaviour], [UE paging probability information], [Paging Subgrouping Support Indication], [UE Policy Container (the list of PSIs, indication of UE support for ANDSP, the operating system identifier, Indication of URSP Provisioning Support in EPS, UE capability of reporting URSP rule enforcement to network, UE capability of supporting VPLMN-specific URSP rules)] and [UE Radio Capability ID], [Release Request indication], [Paging Restriction Information], PEI, [PLMN with Disaster Condition], [Requested Periodic Update time], [Unavailability Period Duration], [Start of Unavailability Period], [Unavailability Type])). NOTE 1: The UE Policy Container and its usage is defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of NG-RAN, the AN parameters include e.g. 5G-S-TMSI or GUAMI, the Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and NSSAI information, the AN parameters also include Establishment cause. The Establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the NSSAI information as part of the AN parameters is dependent on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter, as specified in clause 5.15.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AN parameters shall also include an IAB-Indication if the UE is an IAB-node accessing 5GS. The AN parameters shall also include a MBSR Indication if the UE is part of an MBSR node accessing 5GS attempting MBSR operation in the PLMN as specified in clause 5.35A.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Registration type indicates if the UE wants to perform an Initial Registration (i.e. the UE is in RM-DEREGISTERED state), a Mobility Registration Update (i.e. the UE is in RM-REGISTERED state and initiates a Registration procedure due to mobility or due to the UE needs to update its capabilities or protocol parameters, or to request a change of the set of network slices it is allowed to use), a Periodic Registration Update (i.e. the UE is in RM-REGISTERED state and initiates a Registration procedure due to the Periodic Registration Update timer expiry, see clause 4.2.2.2.1), an Emergency Registration (i.e. the UE is in limited service state), a Disaster Roaming Initial Registration, or a Disaster Roaming Mobility Registration Update. When the UE is using E-UTRA, the UE indicates its support of CIoT 5GS Optimisations, which is relevant for the AMF selection, in the RRC connection establishment signalling associated with the Registration Request. When the UE is performing an Initial Registration or a Disaster Roaming Registration the UE shall indicate its UE identity in the Registration Request message as follows, listed in decreasing order of preference in the case of registration with a PLMN: i) a 5G-GUTI mapped from an EPS GUTI, if the UE has a valid EPS GUTI. ii) a native 5G-GUTI assigned by the PLMN to which the UE is attempting to register, if available; iii) a native 5G-GUTI assigned by an equivalent PLMN to the PLMN to which the UE is attempting to register, if available; iv) a native 5G-GUTI assigned by any other PLMN, if available; or NOTE 2: This can also be a 5G-GUTIs assigned via another access type. v) Otherwise, the UE shall include its SUCI in the Registration Request as defined in TS 33.501[ Security architecture and procedures for 5G System ] [15]. If the UE is registering with an SNPN, when the UE is performing an Initial Registration the UE shall indicate its UE identity in the Registration Request message as follows, listed in decreasing order of preference: i) a native 5G-GUTI assigned by the same SNPN to which the UE is attempting to register, if available; ii) a native 5G-GUTI assigned by an equivalent SNPN to the SNPN to which the UE is attempting to register along with the NID of the SNPN that assigned the 5G-GUTI, if available; iii) a native 5G-GUTI assigned by any other SNPN along with the NID of the SNPN that assigned the 5G-GUTI, if available; or iv) Otherwise, the UE shall include its SUCI in the Registration Request as defined in TS 33.501[ Security architecture and procedures for 5G System ] [15]. When the UE performing an Initial Registration has both a valid EPS GUTI and a native 5G-GUTI, the UE shall also indicate the native 5G-GUTI as Additional GUTI. If more than one native 5G-GUTIs are available, the UE shall select the 5G-GUTI in decreasing order of preference among items (ii)-(iv) in the list above. The NAS message container shall be included if the UE is sending a Registration Request message as an Initial NAS message and the UE has a valid 5G NAS security context and the UE needs to send non-cleartext IEs, see clause 4.4.6 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. If the UE does not need to send non-cleartext IEs, the UE shall send a Registration Request message without including the NAS message container. If the UE does not have a valid 5G NAS security context, the UE shall send the Registration Request message without including the NAS message container. The UE shall include the entire Registration Request message (i.e. containing cleartext IEs and non-cleartext IEs) in the NAS message container that is sent as part of the Security Mode Complete message in step 9b. When the UE is performing an Initial Registration (i.e. the UE is in RM-DEREGISTERED state) with a native 5G-GUTI then the UE shall indicate the related GUAMI information in the AN parameters. When the UE is performing an Initial Registration with its SUCI, the UE shall not indicate any GUAMI information in the AN parameters. When the UE is performing an Initial Registration or a Mobility Registration and if CIoT 5GS Optimisations are supported the UE shall indicate its Preferred Network Behaviour (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If S1 mode is supported the UE's EPC Preferred Network Behaviour is included in the S1 UE network capabilities in the Registration Request message, see clause 8.2.6.1 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. For an Emergency Registration, the SUCI shall be included if the UE does not have a valid 5G-GUTI available; the PEI shall be included when the UE has no SUPI and no valid 5G-GUTI. In other cases, the 5G-GUTI is included and it indicates the last serving AMF. The UE may provide the UE's usage setting based on its configuration as defined in clause 5.16.3.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE provides Requested NSSAI (as described in clause 5.15.5.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and if the UE supports the subscription-based restrictions to simultaneous registration of network slices, also taking into account the NSSRG Information constraints as described in clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and in the case of Initial Registration or Mobility Registration Update, the UE includes the Mapping Of Requested NSSAI (if available), which is the mapping of each S-NSSAI of the Requested NSSAI to the HPLMN S-NSSAIs, to ensure that the network is able to verify whether the S-NSSAI(s) in the Requested NSSAI are permitted based on the Subscribed S-NSSAIs. In the case of inter PLMN mobility, if the serving PLMN S-NSSAI(s) corresponding to the established PDU Session(s) are not present in the UE, the associated HPLMN S-NSSAI(s) associated with the established PDU Session(s) shall be provided in the Mapping Of Requested NSSAI as described in clause 5.15.5.2.1 TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UEs supports reconnection to the network due to RAN timing synchronization status change as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], the UE indicates the support of this capability to the network. If the UE supports UE configuration of network-controlled Slice Usage Policy and the UE stores Slice Usage Policy, the UE shall include an on demand S-NSSAI in the Requested NSSAI only when applications in the UE require data transmission by a PDU session associated with the on demand S-NSSAI as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE includes the Default Configured NSSAI Indication if the UE is using a Default Configured NSSAI, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE may include UE paging probability information if it supports the assignment of WUS Assistance Information or AMF PEIPS Assistance Information from the AMF (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The UE may include Paging Subgrouping Support Indication as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of Mobility Registration Update, the UE includes in the List Of PDU Sessions To Be Activated the PDU Sessions for which there are pending uplink data. When the UE includes the List Of PDU Sessions To Be Activated, the UE shall indicate PDU Sessions only associated with the access the Registration Request is related to. As defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25] the UE shall include always-on PDU Sessions which are accepted by the network in the List Of PDU Sessions To Be Activated even if there are no pending uplink data for those PDU Sessions. NOTE 3: A PDU Session corresponding to a LADN is not included in the List Of PDU Sessions To Be Activated when the UE is outside the area of availability of the LADN. The UE MM Core Network Capability is provided by the UE and handled by AMF as defined in clause 5.4.4a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE includes in the UE MM Core Network Capability an indication if it supports Request Type flag "handover" for PDN connectivity request during the attach procedure as defined in clause 5.17.2.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE supports 'Strictly Periodic Registration Timer Indication', the UE indicates its capability of 'Strictly Periodic Registration Timer Indication' in the MICO Indication. If the UE supports CAG, the UE indicates its capability of "CAG supported" in the UE MM Core Network Capability. If the UE operating two or more USIMs, supports and intends to use one or more Multi-USIM feature(s), the UE indicates one or more Multi-USIM specific features described in clause 5.38 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] in the UE MM Core Network Capability. If the UE supports equivalent SNPNs, the UE indicates its capability of "equivalent SNPNs" in the UE MM Core Network Capability. If the UE supports Unavailability Period, the UE indicates its capability of "Unavailability Period Support" in the UE MM Core Network Capability. If the UE supports LADN per DNN and S-NSSAI, the UE indicates its support of LADN per DNN and S-NSSAI in the UE MM Core Network Capability. If the UE supports the Network Slice Replacement feature, the UE indicates support for Network Slice Replacement feature as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE supports UE configuration of network-controlled Slice Usage Policy, the UE indicates its capability of "UE Configuration of network-controlled Slice Usage Policy" in the UE MM Core Network Capability as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE may provide either the LADN DNN(s) or an Indication Of Requesting LADN Information as described in clause 5.6.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If available, the last visited TAI shall be included in order to help the AMF produce Registration Area for the UE. NOTE 4: With NR satellite access, the last visited TAI is determined as specified in clause 5.4.11.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Security parameters are used for Authentication and integrity protection, see TS 33.501[ Security architecture and procedures for 5G System ] [15]. Requested NSSAI indicates the Network Slice Selection Assistance Information (as defined in clause 5.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The PDU Session status indicates the previously established PDU Sessions in the UE. When the UE is connected to the two AMFs belonging to different PLMN via 3GPP access and non-3GPP access then the PDU Session status indicates the established PDU Session of the current PLMN in the UE. The Follow-on request is included when the UE has pending uplink signalling and the UE doesn't include List Of PDU Sessions To Be Activated, or the Registration type indicates the UE wants to perform an Emergency Registration. In Initial Registration and Mobility Registration Update, UE provides the UE Requested DRX parameters, as defined in clause 5.4.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE may provide the extended idle mode DRX parameters as defined in clause 5.31.7.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to request extended idle mode DRX. The UE provides UE Radio Capability Update indication as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE includes the MICO Indication and optionally a Requested Active Time value and Requested Periodic Update time value if the UE wants to use MICO Mode with Active Time. For a UE using NR satellite access that provides discontinuous coverage, the UE may include an Unavailability Type, an Unavailability Period Duration and/or Start of Unavailability Period as described in clause 5.4.13.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE may indicate its Service Gap Control Capability in the UE MM Core Network Capability, see clause 5.31.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For a UE with a running Service Gap timer in the UE, the UE shall not set Follow-on Request indication or Uplink data status in the Registration Request message (see clause 5.31.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), except for network access for regulatory prioritized services like Emergency services or exception reporting. If UE supports RACS and has been assigned UE Radio Capability ID(s), the UE shall indicate a UE Radio Capability ID as defined in clause 5.4.4.1a of TS 23.501[ System architecture for the 5G System (5GS) ] [2] as non-cleartext IE. The PEI may be retrieved in initial registration from the UE as described in clause 4.2.2.2.1. If a UE supports the subscription-based restrictions to simultaneous registration of network slices feature, it includes the NSSRG handling support indication in the UE 5GMM Core Network Capability according to clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF stores whether the UE supports this feature in the UE context. If a UE supports the temporary available network slices feature, it includes the indication of support for temporary available network slices in the UE 5GMM Network Capability according to clause 5.15.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When a Multi-USIM UE wants to enter CM-IDLE state immediately e.g. after having performed mobility or periodic registration, it includes the Release Request indication and optionally provides Paging Restriction Information. When the UE is performing a Disaster Roaming Registration, the UE may indicate the PLMN with Disaster Condition for the cases as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. If the UE and network have indicated support Unavailability Period and an event is triggered in the UE that would make the UE unavailable for a certain period of time, the UE indicates Unavailability Period by including Unavailability Period Duration and/or Start of Unavailability Period as described in clause 5.4.1.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2. If a 5G-S-TMSI or GUAMI is not included or the 5G-S-TMSI or GUAMI does not indicate a valid AMF the (R)AN, based on (R)AT and Requested NSSAI, if available, selects an AMF The (R)AN selects an AMF as described in clause 6.3.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If UE is in CM-CONNECTED state, the (R)AN can forward the Registration Request message to the AMF based on the N2 connection of the UE. If the (R)AN cannot select an appropriate AMF, it forwards the Registration Request to an AMF which has been configured, in (R)AN, to perform AMF selection. 3. (R)AN to new AMF: N2 message (N2 parameters, Registration Request (as described in step 1) and [LTE-M Indication]. When NG-RAN is used, the N2 parameters include the Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Location Information and Cell Identity related to the cell in which the UE is camping, UE Context Request which indicates that a UE context including security information needs to be setup at the NG-RAN. When NG-RAN is used, the N2 parameters shall also include the Establishment cause and IAB-Indication or MBSR Indication if the indication is received in AN parameters in step 1. Mapping Of Requested NSSAI is provided only if available. If the Registration type indicated by the UE is Periodic Registration Update, then steps 4 to 19 may be omitted. When the Establishment cause is associated with priority services (e.g. MPS, MCS), the AMF includes a Message Priority header to indicate priority information. Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [17]. The RAT Type the UE is using is determined (see clause 4.2.2.2.1) and based on it the AMF determines whether the UE is performing Inter-RAT mobility to or from NB-IoT. If the AMF receives the LTE M indication, then it considers that the RAT Type is LTE-M and stores the LTE-M Indication in UE Context. If a UE includes a Preferred Network Behaviour, this defines the Network Behaviour the UE supports and is expecting to be available in the network as defined in clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has included the Preferred Network Behaviour and what the UE indicated it supports in Preferred Network Behaviour is incompatible with the network support, the AMF shall reject the Registration Request with an appropriate cause value (e.g. one that avoids retries on this PLMN). If there is a Service Gap timer running in the UE Context in AMF for the UE and Follow-on Request indication or Uplink data status is included in the Registration Request message, the AMF shall ignore the Follow-on Request indication and Uplink data status and not perform any of the actions related to the status. If the UE has included a UE Radio Capability ID in step 1 and the AMF supports RACS, the AMF stores the Radio Capability ID in UE context. For NR satellite access, the AMF may verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 5.4.11.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE receives a Registration Reject message with cause value indicating that the PLMN is not allowed to operate at the present UE location, the UE shall attempt to select a PLMN as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. For a Disaster Roaming Registration, based on the ULI (including Cell ID) received from the NG-RAN, the PLMN with Disaster Condition derived from the UE's 5G-GUTI, derived from the UE's SUCI or indicated by the UE and the local configuration, the AMF determines if Disaster Roaming service can be provided. If the current location is not subject to Disaster Roaming service or the Disaster Roaming service is not provided to the PLMN with Disaster Condition derived from the UE's 5G-GUTI, derived from the UE's SUCI or indicated by UE, then the AMF should reject the Registration Request indicating a suitable Cause value. 4. [Conditional] new AMF to old AMF: Namf_Communication_UEContextTransfer (complete Registration Request) or new AMF to UDSF: Nudsf_Unstructured Data Management_Query(). The new AMF determines the old AMF using the UE's 5G-GUTI. If the new AMF received an NID in the Registration request, it determines that the 5G-GUTI was assigned by an SNPN and determines the old AMF using the 5G-GUTI and NID of the SNPN. (With UDSF Deployment): If the UE's 5G-GUTI was included in the Registration Request and the serving AMF has changed since last Registration procedure, new AMF and old AMF are in the same AMF Set and UDSF is deployed, the new AMF retrieves the stored UE's SUPI and UE context directly from the UDSF using Nudsf_UnstructuredDataManagement_Query service operation or they can share stored UE context via implementation specific means if UDSF is not deployed. This includes also event subscription information by each NF consumer for the given UE. In this case, the new AMF uses integrity protected complete Registration request NAS message to perform and verify integrity protection. (Without UDSF Deployment): If the UE's 5G-GUTI was included in the Registration Request and the serving AMF has changed since last Registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation on the old AMF including the complete Registration Request NAS message, which may be integrity protected, as well as the Access Type, to request the UE's SUPI and UE Context. See clause 5.2.2.2.2 for details of this service operation. In this case, the old AMF uses either 5G-GUTI and the integrity protected complete Registration request NAS message, or the SUPI and an indication that the UE is validated from the new AMF, to verify integrity protection if the context transfer service operation invocation corresponds to the UE requested. The old AMF also transfers the event subscriptions information by each NF consumer, for the UE, to the new AMF. If the old AMF has not yet reported a non-zero MO Exception Data Counter to the (H-)SMF, the Context Response also includes the MO Exception Data Counter. If the old AMF has PDU Sessions for another access type (different from the Access Type indicated in this step) and if the old AMF determines that there is no possibility for relocating the N2 interface to the new AMF, the old AMF returns UE's SUPI and indicates that the Registration Request has been validated for integrity protection, but does not include the rest of the UE context. For inter PLMN mobility, UE Context information includes HPLMN S-NSSAIs corresponding to the Allowed NSSAI for each Access Type and Partially Allowed NSSAI, without Allowed NSSAI and Partially Allowed NSSAI of old PLMN. NOTE 5: The new AMF Sets the indication that the UE is validated according to step 9a, if the new AMF has performed successful UE authentication after previous integrity check failure in the old AMF. NOTE 6: The NF consumers do not need to subscribe for the events once again with the new AMF after the UE is successfully registered with the new AMF. If the new AMF has already received UE contexts from the old AMF during handover procedure, then step 4,5 and 10 shall be skipped. For an Emergency Registration, if the UE identifies itself with a 5G-GUTI that is not known to the AMF, steps 4 and 5 are skipped and the AMF immediately requests the SUPI from the UE. If the UE identifies itself with PEI, the SUPI request shall be skipped. Allowing Emergency Registration without a user identity is dependent on local regulations. 5. [Conditional] old AMF to new AMF: Response to Namf_Communication_UEContextTransfer (SUPI, UE Context in AMF (as per Table 5.2.2.2.2-1)) or UDSF to new AMF: Nudsf_Unstructured Data Management_Query(). The old AMF may start an implementation specific (guard) timer for the UE context. If the UDSF was queried in step 4, the UDSF responds to the new AMF for the Nudsf_Unstructured Data Management_Query invocation with the related contexts including established PDU Sessions, the old AMF includes SMF information DNN, S-NSSAI(s) and PDU Session ID, active NGAP UE-TNLA bindings to N3IWF/TNGF/W-AGF, the old AMF includes information about the NGAP UE-TNLA bindings. If the Old AMF was queried in step 4, Old AMF responds to the new AMF for the Namf_Communication_UEContextTransfer invocation by including the UE's SUPI and UE Context. If old AMF holds information about established PDU Session(s) and it is not an Initial Registration, the old AMF includes SMF information, DNN(s), S-NSSAI(s) and PDU Session ID(s). If old AMF holds UE context established via N3IWF, W-AGF or TNGF, the old AMF includes the CM state via N3IWF, W-AGF or TNGF. If the UE is in CM-CONNECTED state via N3IWF, W-AGF or TNGF, the old AMF includes information about the NGAP UE-TNLA bindings. If old AMF fails the integrity check of the Registration Request NAS message, the old AMF shall indicate the integrity check failure. If the new AMF is configured to allow emergency services for unauthenticated UE, the new AMF behaves as follows: - If the UE has only an emergency PDU Session, the AMF either skips the authentication and security procedure or accepts that the authentication may fail and continues the Mobility Registration Update procedure; or - If the UE has both emergency and non emergency PDU Sessions and authentication fails, the AMF continues the Mobility Registration Update procedure and deactivates all the non-emergency PDU Sessions as specified in clause 4.3.4.2. NOTE 7: The new AMF can determine if a PDU Session is used for emergency service by checking whether the DNN matches the emergency DNN. If old AMF holds information about AM Policy Association and the information about UE Policy Association (i.e. the Policy Control Request Trigger for updating UE Policy as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), the old AMF includes the information about the AM Policy Association, the UE Policy Association and PCF ID. In the roaming case, V-PCF ID and H-PCF ID are included. If old AMF was a consumer of UE related NWDAF services, the old AMF includes information about active analytics subscriptions, i.e. the Subscription Correlation ID, NWDAF identifier (i.e. Instance ID or Set ID), Analytics ID(s) and associated Analytics specific data in the Namf_Communication_UEContextTransfer response. Usage of the analytics information by the new AMF is specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. During inter PLMN mobility, the handling of the UE Radio Capability ID in the new AMF is as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 8: When new AMF uses UDSF for context retrieval, interactions between old AMF, new AMF and UDSF due to UE signalling on old AMF at the same time is implementation issue. 6. [Conditional] new AMF to UE: Identity Request (). If the SUCI is not provided by the UE nor retrieved from the old AMF the Identity Request procedure is initiated by AMF sending an Identity Request message to the UE requesting the SUCI. 7. [Conditional] UE to new AMF: Identity Response (). The UE responds with an Identity Response message including the SUCI. The UE derives the SUCI by using the provisioned public key of the HPLMN, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [15]. 8. The AMF may decide to initiate UE authentication by invoking an AUSF. In that case, the AMF selects an AUSF based on SUPI or SUCI, as described in clause 6.3.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the AMF is configured to support Emergency Registration for unauthenticated SUPIs and the UE indicated Registration type Emergency Registration, the AMF skips the authentication or the AMF accepts that the authentication may fail and continues the Registration procedure. 9a. If authentication is required, the AMF requests it from the AUSF; if Tracing Requirements about the UE are available at the AMF, the AMF provides Tracing Requirements in its request to AUSF. For a Disaster Roaming Registration, the AMF may provide the indication of Disaster Roaming service in its request to AUSF. Upon request from the AMF, the AUSF shall execute authentication of the UE. The authentication is performed as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. The AUSF selects a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and gets the authentication data from UDM. The AUSF may provide the indication of Disaster Roaming service to UDM if the indication is received from AMF. For a Disaster Roaming Registration, the AUSF executes authentication of the UE based on the local policy and/or local configuration as specified in clause 5.40.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and in TS 33.501[ Security architecture and procedures for 5G System ] [15]. Once the UE has been authenticated the AUSF provides relevant security related information to the AMF. If the AMF provided a SUCI to AUSF, the AUSF shall return the SUPI to AMF only after the authentication is successful. After successful authentication in new AMF, which is triggered by the integrity check failure in old AMF at step 5, the new AMF invokes step 4 above again and indicates that the UE is validated (i.e. through the reason parameter as specified in clause 5.2.2.2.2). 9b If NAS security context does not exist, the NAS security initiation is performed as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. If the UE had no NAS security context in step 1, the UE includes the full Registration Request message as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. The AMF decides if the Registration Request needs to be rerouted as described in clause 4.2.2.2.3, where the initial AMF refers to the AMF. 9c. The AMF initiates NGAP procedure to provide the 5G-AN with security context as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10] if the 5G-AN had requested for UE Context. Also, if the AMF decides that EPS fallback is supported (e.g. based on UE capability to support Request Type flag "handover" for PDN connectivity request during the attach procedure as defined in clause 5.17.2.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], subscription data and local policy), the AMF shall send an indication "Redirection for EPS fallback for voice is possible" towards 5G-AN as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. Otherwise, the AMF indicates "Redirection for EPS fallback for voice is not possible". In addition, if Tracing Requirements about the UE are available at the AMF, the AMF provides the 5G-AN with Tracing Requirements in the NGAP procedure. 9d. The 5G-AN stores the security context and acknowledges to the AMF. The 5G-AN uses the security context to protect the messages exchanged with the UE as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. 10. [Conditional] new AMF to old AMF: Namf_Communication_RegistrationStatusUpdate (PDU Session ID(s) to be released e.g. due to slice not supported). If the AMF has changed the new AMF informs the old AMF that the registration of the UE in the new AMF is completed by invoking the Namf_Communication_RegistrationStatusUpdate service operation. If the authentication/security procedure fails, then the Registration shall be rejected and the new AMF invokes the Namf_Communication_RegistrationStatusUpdate service operation with a reject indication towards the old AMF. The old AMF continues as if the UE context transfer service operation was never received. The new AMF determines the PDU Session(s) that cannot be supported in the new Registration Area in the cases below: - If one or more of the S-NSSAIs used in the old Registration Area cannot be served in the target Registration Area. - When continuity of the PDU Session(s) cannot be supported between networks (e.g. SNPN-SNPN mobility, inter-PLMN mobility where no HR agreement exists). If any of the cases is met, the new AMF invokes the Namf_Communication_RegistrationStatusUpdate service operation including the rejected PDU Session ID towards the old AMF. Then the new AMF modifies the PDU Session Status correspondingly. The old AMF informs the corresponding SMF(s) to locally release the UE's SM context by invoking the Nsmf_PDUSession_ReleaseSMContext service operation. If new AMF received in the UE context transfer in step 5 the information about the AM Policy Association and the UE Policy Association and decides, based on local policies, not to use the PCF(s) identified by the PCF ID(s) for the AM Policy Association and the UE Policy Association, then it will inform the old AMF that the AM Policy Association and the UE Policy Association in the UE context is not used any longer and then the PCF selection is performed in step 15. If the new AMF received in the UE context transfer in step 5 the information about UE related analytics subscription(s), the new AMF may take over the analytics subscription(s) from the old AMF. Otherwise, if the new AMF instead determines to create new analytics subscription(s), it informs the old AMF about the analytics subscriptions (identified by their Subscription Correlation ID) that are not needed any longer and the old AMF may now unsubscribe those NWDAF analytics subscriptions for the UE according to TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. 11. [Conditional] new AMF to UE: Identity Request/Response (PEI). If the PEI was not provided by the UE nor retrieved from the old AMF the Identity Request procedure is initiated by AMF sending an Identity Request message to the UE to retrieve the PEI. The PEI shall be transferred encrypted unless the UE performs Emergency Registration and cannot be authenticated. For an Emergency Registration, the UE may have included the PEI in the Registration Request. If so, the PEI retrieval is skipped. If the UE supports RACS as indicated in UE MM Core Network Capability, the AMF shall use the PEI of the UE to obtain the IMEI/TAC for the purpose of RACS operation. 12. Optionally the new AMF initiates ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation (see clause 5.2.4.2.2). The PEI check is performed as described in clause 4.7. For an Emergency Registration, if the PEI is blocked, operator policies determine whether the Emergency Registration procedure continues or is stopped. 13. If step 14 is to be performed, the new AMF, based on the SUPI, selects a UDM, then UDM may select a UDR instance. See clause 6.3.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF selects a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 14a-c. If the AMF has changed since the last Registration procedure, if UE Registration type is Initial Registration or Emergency Registration, or if the UE provides a SUPI which does not refer to a valid context in the AMF, or if the UE registers to the same AMF it has already registered to a non-3GPP access (i.e. the UE is registered over a non-3GPP access and initiates this Registration procedure to add a 3GPP access), the new AMF registers with the UDM using Nudm_UECM_Registration for the access to be registered (and subscribes to be notified when the UDM deregisters this AMF). The UDM based on the "Registration Type" in the Nudm_UECM_Registration request, can act on SoR information according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. In this case, if the AMF does not have event exposure subscription information for this UE, the AMF indicates it to UDM. Then, if the UDM has existing applicable event exposure subscriptions for events detected in AMF for this UE or for any of the groups this UE belongs to (possibly retrieved from UDR), UDM invokes the Namf_EventExposure_Subscribe service for recreating the event exposure subscriptions. The AMF provides the "Homogenous Support of IMS Voice over PS Sessions" indication (see clause 5.16.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) to the UDM. The "Homogenous Support of IMS Voice over PS Sessions" indication shall not be included unless the AMF has completed its evaluation of the support of "IMS Voice over PS Session" as specified in clause 5.16.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. During initial Registration, if the AMF and UE supports SRVCC from NG-RAN to UTRAN the AMF provides UDM with the UE SRVCC capability. If the AMF determines that only the UE SRVCC capability has changed, the AMF sends UE SRVCC capability to the UDM. NOTE 9: At this step, it is possible that the AMF does not have all the information needed to determine the setting of the IMS Voice over PS Session Supported indication for this UE (see clause 5.16.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). Hence the AMF can send the "Homogenous Support of IMS Voice over PS Sessions" later on in this procedure. After AMF has successfully completed the Nudm_UECM_Registration operation and if the AMF does not have subscription data for the UE, the AMF retrieves the Access and Mobility Subscription data, SMF Selection Subscription data, UE context in SMF data and LCS mobile origination using Nudm_SDM_Get. If the AMF already has subscription data for the UE but the SoR Update Indicator in the UE context requires the AMF to retrieve SoR information depending on the NAS Registration Type ("Initial Registration" or "Emergency Registration") (see Annex C of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]), the AMF retrieves the Steering of Roaming information using Nudm_SDM_Get. This requires that UDM may retrieve this information from UDR by Nudr_DM_Query. After a successful response is received, the AMF subscribes to be notified using Nudm_SDM_Subscribe when the data requested is modified, UDM may subscribe to UDR by Nudr_DM_Subscribe. The GPSI is provided to the AMF in the Access and Mobility Subscription data from the UDM if the GPSI is available in the UE subscription data. The UDM may provide indication that the subscription data for network slicing is updated for the UE. If the UE is subscribed to MPS in the serving PLMN, "MPS priority" is included in the Access and Mobility Subscription data provided to the AMF. If the UE is subscribed to MCX in the serving PLMN, "MCX priority" is included in the Access and Mobility Subscription data provided to the AMF. The UDM also provides the IAB-Operation allowed indication or MBSR Operation allowed indication to AMF as part of the Access and Mobility Subscription data. The AMF shall trigger the setup of the UE context in NG-RAN, or modification of the UE context in NG-RAN if the initial setup is at step 9c, including an indication that the IAB-node is authorized or MBSR is authorized. If a S-NSSAI in the Subscribed S-NSSAIs is subject to network slice usage control and the S-NSSAI is dedicated for a single AF, the UDM may provide a Slice Usage Policy information including whether a network slice is on demand and a slice deregistration inactvity timer value for the Subscribed S-NSSAIs as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For a Disaster Roaming Registration, the AMF may provide the indication of Disaster Roaming service to the UDM. The UDM provides the subscription data for a Disaster Roaming service to the AMF based on the local policy and/or the local configuration as specified in clause 5.40.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF provides MINT support indication via Nudm_UECM_Registration towards UDM, if UE includes the MINT support indication in the 5GMM capability as specified in clause 5.40.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] or if the MINT support indication in the 5GMM capability is changed. If the AMF receives a priority indication (e.g. MPS, MCX) as part of the Access and Mobility Subscription data, but the UE did not provide an Establishment cause associated with priority services, the AMF shall include a Message Priority header to indicate priority information for all subsequent messages. Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [17]. The new AMF provides the Access Type it serves for the UE to the UDM and the Access Type is set to "3GPP access". The UDM stores the associated Access Type together with the serving AMF and does not remove the AMF identity associated to the other Access Type if any. The UDM may store in UDR information provided at the AMF registration by Nudr_DM_Update. If the UE was registered in the old AMF for an access and the old and the new AMFs are in the same PLMN, the new AMF sends a separate/independent Nudm_UECM_Registration to update UDM with Access Type set to access used in the old AMF, after the old AMF relocation is successfully completed. The new AMF creates an UE context for the UE after getting the Access and Mobility Subscription data from the UDM. The Access and Mobility Subscription data includes whether the UE is allowed to include NSSAI in the 3GPP access RRC Connection Establishment in clear text. The Access and Mobility Subscription data may include Enhanced Coverage Restricted information. If received from the UDM and the UE included support for restriction of use of Enhanced Coverage in step 1, the AMF determines whether Enhanced Coverage is restricted or not for the UE as specified in clause 5.31.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and stores the updated Enhanced Coverage Restricted information in the UE context. The Access and Mobility Subscription data may include the NB-IoT UE Priority. For subscribed S-NSSAIs subject to NSAC, the AMF stores the corresponding applicable NSAC admission mode. The subscription data may contain Service Gap Time parameter. If received from the UDM, the AMF stores this Service Gap Time in the UE Context in AMF for the UE. If the AMF has the LADN service area and UE indication of support for LADN per DNN and S-NSSAI, the AMF applies LADN per DNN and S-NSSAI as described in 5.20b.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For an Emergency Registration in which the UE was not successfully authenticated, the AMF shall not register with the UDM. The AMF enforces the Mobility Restrictions as specified in clause 5.3.4.1.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For an Emergency Registration, the AMF shall not check for Mobility Restrictions, access restrictions, regional restrictions or subscription restrictions. For an Emergency Registration, the AMF shall ignore any unsuccessful registration response from UDM and continue with the Registration procedure. NOTE 10: The AMF can, instead of the Nudm_SDM_Get service operation, use the Nudm_SDM_Subscribe service operation with an Immediate Report Indication that triggers the UDM to immediately return the subscribed data if the corresponding feature is supported by both the AMF and the UDM. 14d. When the UDM stores the associated Access Type (e.g. 3GPP) together with the serving AMF as indicated in step 14a, it will cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2) to the old AMF corresponding to the same (e.g. 3GPP) access, if one exists. If the timer started in step 5 is not running, the old AMF may remove the UE context for the same Access Type. Otherwise, the AMF may remove UE context for the same Access Type when the timer expires. If the serving NF removal reason indicated by the UDM is Initial Registration, then, as described in clause 4.2.2.3.2, the old AMF invokes the Nsmf_PDUSession_ReleaseSMContext (SM Context ID) service operation towards all the associated SMF(s) of the UE to notify that the UE is deregistered from old AMF for the same Access Type. The SMF(s) shall release the PDU Session on getting this notification. If the old AMF has established an AM Policy Association and a UE Policy Association with the PCF(s) and the old AMF did not transfer the PCF ID(s) to the new AMF (e.g. new AMF is in different PLMN), the old AMF performs an AMF-initiated Policy Association Termination procedure, as defined in clause 4.16.3.2 and performs an AMF-initiated UE Policy Association Termination procedure, as defined in clause 4.16.13.1. In addition, if the old AMF transferred the PCF ID(s) in the UE context but the new AMF informed in step 10 that the AM Policy Association information and UE Policy Association information in the UE context will not be used then the old AMF performs an AMF-initiated Policy Association Termination procedure, as defined in clause 4.16.3.2 and performs an AMF-initiated UE Policy Association Termination procedure, as defined in clause 4.16.13.1. If the old AMF has an N2 connection for that UE (e.g. because the UE was in RRC_INACTIVE state but has now moved to E-UTRAN or moved to an area not served by the old AMF), the old AMF shall perform AN Release (see clause 4.2.6) with a cause value that indicates that the UE has already locally released the NG-RAN's RRC Connection. If the UE context in the old AMF contains an Allowed NSSAI or Partially Allowed NSSAI including one or more S-NSSAI(s) subject to NSAC, the old AMF upon receipt of the Nudm_UECM_DeregistrationNotification from the UDM, sends an update request message for each S-NSSAI subject to NSAC to the corresponding NSACF(s) with update flag parameter set to decrease (see clause 4.2.11.2). At the end of registration procedure, the AMF may initiate synchronization of event exposure subscriptions with the UDM if the AMF does not indicate unavailability of event exposure subscription in step 14a. NOTE 11: The AMF can initiate synchronization with UDM even if events are available in the UE context (e.g. as received from old AMF) at any given time and based on local policy. This can be done during subscription change related event. 14e. [Conditional] If old AMF does not have UE context for another access type (i.e. non-3GPP access), the Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe. 15. If the AMF decides to initiate PCF communication, the AMF acts as follows. If the new AMF decides to use the (V-)PCF identified by the (V-)PCF ID included in UE context from the old AMF in step 5, the AMF contacts the (V-)PCF identified by the (V-)PCF ID to obtain policy. If the AMF decides to perform PCF discovery and selection and the AMF selects a (V)-PCF and may select an H-PCF (for roaming scenario) as described in clause 6.3.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and according to the V-NRF to H-NRF interaction described in clause 4.3.2.2.3.3. 16. [Optional] new AMF performs an AM Policy Association Establishment/Modification. For an Emergency Registration, this step is skipped. If the new AMF selects a new (V-)PCF in step 15, the new AMF performs AM Policy Association Establishment with the selected (V-)PCF as defined in clause 4.16.1.2. If the (V-)PCF identified by the (V-)PCF ID included in UE context from the old AMF is used, the new AMF performs AM Policy Association Modification with the (V-)PCF as defined in clause 4.16.2.1.2. If the AMF notifies the Mobility Restrictions (e.g. UE location) to the PCF for adjustment, or if the PCF updates the Mobility Restrictions itself due to some conditions (e.g. application in use, time and date), the PCF shall provide the updated Mobility Restrictions to the AMF. If the subscription information includes Tracing Requirements, the AMF provides the PCF with Tracing Requirements. If the AMF supports DNN replacement, the AMF provides the PCF with the Allowed NSSAI and Partially Allowed NSSAI and if available, the Mapping Of Allowed NSSAI and Mapping Of Partially Allowed NSSAI. If the PCF supports DNN replacement, the PCF provides the AMF with triggers for DNN replacement. If the PCF supports the slice replacement, the PCF provides the AMF with triggers for slice replacement. If a S-NSSAI in subject to network slice usage control, the PCF may provide a Slice Usage Policy information including, whether a network slice is on demand and a slice deregistration inactvity timer value, for the Subscribed S-NSSAIs as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 17. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext (). For an Emergency Registered UE (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]), this step is applied when the Registration Type is Mobility Registration Update. The AMF invokes the Nsmf_PDUSession_UpdateSMContext (see clause 5.2.8.2.6) in the following scenario(s): - If the List Of PDU Sessions To Be Activated is included in the Registration Request in step 1, the AMF sends Nsmf_PDUSession_UpdateSMContext Request to SMF(s) associated with the PDU Session(s) in order to activate User Plane connections of these PDU Session(s). Steps from step 5 onwards described in clause 4.2.3.2 are executed to complete the User Plane connection activation without sending the RRC Inactive Assistance Information and without sending MM NAS Service Accept from the AMF to (R)AN described in step 12 of clause 4.2.3.2. When a User Plane connection for a PDU Session is activated, the AS layer in the UE indicates it to the NAS layer. - If the AMF has determined in step 3 that the UE is performing Inter-RAT mobility to or from NB-IoT, the AMF sends Nsmf_PDUSession_UpdateSMContext Request to SMF(s) associated with the UEs PDU Session(s), so the SMF(s) can update them according to the "PDU Session continuity at inter RAT mobility" subscription data. Steps from step 5 onwards described in clause 4.2.3.2 are executed without sending MM NAS Service Accept from the AMF to (R)AN described in step 12 of clause 4.2.3.2. When the serving AMF has changed, the new serving AMF notifies the SMF for each PDU Session that it has taken over the responsibility of the signalling path towards the UE: the new serving AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the PDU Session is to be re-activated. NOTE 12: If the UE moves into a different PLMN, the AMF in the serving PLMN can insert or change the V-SMF(s) in the serving PLMN for Home Routed PDU session(s). In addition, a V-SMF is removed in case the UE moves from a VPLMN into the HPLMN. In these cases, the same procedures described in clause 4.23.3 are applied for the V-SMF change as for the I-SMF change (i.e. by replacing the I-SMF with V-SMF). During inter-PLMN change, if the same SMF is used, session continuity can be supported depending on operator policies. Steps from step 5 onwards described in clause 4.2.3.2 are executed. In the case that the intermediate UPF insertion, removal, or change is performed for the PDU Session(s) not included in "PDU Session(s) to be re-activated", the procedure is performed without N11 and N2 interactions to update the N3 user plane between (R)AN and 5GC. The AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF in the following scenario: - If any PDU Session status indicates that it is released at the UE, the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF in order to release any network resources related to the PDU Session. If the serving AMF is changed, the new AMF shall wait until step 18 is finished with all the SMFs associated with the UE. Otherwise, steps 19 to 22 can continue in parallel to this step. 18. [Conditional] If the new AMF and the old AMF are in the same PLMN, the new AMF sends a UE Context Modification Request to N3IWF/TNGF/W-AGF as specified in TS 29.413[ Application of the NG Application Protocol (NGAP) to non-3GPP access ] [64]. If the AMF has changed and the old AMF has indicated that the UE is in CM-CONNECTED state via N3IWF, W-AGF or TNGF and if the new AMF and the old AMF are in the same PLMN, the new AMF creates an NGAP UE association towards the N3IWF/TNGF/W-AGF to which the UE is connected. This automatically releases the existing NGAP UE association between the old AMF and the N3IWF/TNGF/W-AGF. 19. N3IWF/TNGF/W-AGF sends a UE Context Modification Response to the new AMF. 19a. [Conditional] After the new AMF receives the response message from the N3IWF, W-AGF or TNGF in step 19, the new AMF registers with the UDM using Nudm_UECM_Registration as step 14a, but with the Access Type set to "non-3GPP access". The UDM stores the associated Access Type together with the serving AMF and does not remove the AMF identity associated to the other Access Type if any. The UDM may store in UDR information provided at the AMF registration by Nudr_DM_Update. 19b. [Conditional] When the UDM stores the associated Access Type (i.e. non-3GPP) together with the serving AMF as indicated in step 19a, it will cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2) to the old AMF corresponding to the same (i.e. non-3GPP) access. The old AMF removes the UE context for non-3GPP access. 19c. The Old AMF unsubscribes with the UDM for subscription data using Nudm_SDM_unsubscribe. 20a. Void. 21. New AMF to UE: Registration Accept (5G-GUTI, Registration Area, [Mobility restrictions], [PDU Session status], [Allowed NSSAI], [Mapping Of Allowed NSSAI], [Partially Allowed NSSAI], [Mapping Of Partially Allowed NSSAI], [TAI List for S-NSSAIs in Partially Allowed NSSAI], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI], [NSSRG Information], [NSAG Information], [rejected S-NSSAIs], [TAI List for any rejected S-NSSAI Partially in the RA], [Pending NSSAI], [Mapping Of Pending NSSAI], [Periodic Registration Update timer], [Active Time], [Strictly Periodic Registration Timer Indication], [LADN Information], [MICO Indication], [IMS Voice over PS session supported Indication], [Emergency Service Support indicator], [Accepted DRX parameters for E-UTRA and NR], [Accepted DRX parameters for NB-IoT], [extended idle mode DRX parameters], [Paging Time Window], [Network support of Interworking without N26], [Access Stratum Connection Establishment NSSAI Inclusion Mode], [Network Slicing Subscription Change Indication], [Operator-defined access category definitions], [List of equivalent PLMNs], [Enhanced Coverage Restricted information], [Supported Network Behaviour], [Service Gap Time], [PLMN-assigned UE Radio Capability ID], [PLMN-assigned UE Radio Capability ID deletion], [WUS Assistance Information], [AMF PEIPS Assistance Information], [Truncated 5G-S-TMSI Configuration], [Connection Release Supported], [Paging Cause Indication for Voice Service Supported], [Paging Restriction Supported], [Reject Paging Request Supported], [Paging Restriction Information acceptance / rejection], ["List of PLMN(s) to be used in Disaster Condition"], [Disaster Roaming wait range information], [Disaster Return wait range information], [Forbidden TAI(s)], [List of equivalent SNPNs], [Registered NID], [Unavailability Period Support], [MBSR authorization information], [Return To Coverage Notification Not Required], [Unavailability Period Duration], [Start of Unavailability Period], [S-NSSAI location availability information], [Mapping Of Alternative NSSAI], [Slice Usage Policy], [Maximum Time Offset]). If the Requested NSSAI does not include S-NSSAIs which map to S-NSSAIs of the HPLMN subject to Network Slice-Specific Authentication and Authorization and the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE in the current UE's Tracking Area and if no default S-NSSAI(s) not yet involved in the current UE Registration procedure could be further considered, the AMF shall reject the UE Registration and shall include in the rejection message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. The Allowed NSSAI for the Access Type for the UE is included in the N2 message carrying the Registration Accept message. The Allowed NSSAI contains only S-NSSAIs that do not require, based on subscription information, Network Slice-Specific Authentication and Authorization and based on the UE Context in the AMF, those S-NSSAIs for which Network Slice-Specific Authentication and Authorization previously succeeded, regardless of the Access Type. The Mapping Of Pending NSSAI is the mapping of each S-NSSAI of the Pending NSSAI for the Serving PLMN to the HPLMN S-NSSAIs. If the UE has indicated its support for the Partial Network Slice support in a Registration Area (see clause 5.15.17 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) in the UE MM Core Network Capability in the Registration Request, the AMF may include Partially Allowed NSSAI in the Registration Accept with the related TAI List for S-NSSAIs in Partially allowed NSSAI as per TS 23.501[ System architecture for the 5G System (5GS) ] [2] clause 5.1517 and in the N2 message carrying the Registration Accept message without the TAI List for S-NSSAIs in Partially allowed NSSAI. The Partially Allowed NSSAI contains only S-NSSAIs that do not require, based on subscription information, Network Slice-Specific Authentication and Authorization and based on the UE Context in the AMF, those S-NSSAIs for which Network Slice-Specific Authentication and Authorization previously succeeded, regardless of the Access Type. The Mapping Of Partially Allowed NSSAI is the mapping of each S-NSSAI of the Partially Allowed NSSAI for the Serving PLMN to the HPLMN S-NSSAIs. If the UE has indicated its support for the Partial Network Slice support in a Registration Area (see clause 5.15.17 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) in the UE MM Core Network Capability in the Registration Request, the AMF may include S-NSSAI(s) rejected partially in the RA in the Registration Accept with the applicable TAI List for rejected S-NSSAI partially in the RA. If the UE has indicated its support of the Network Slice-Specific Authentication and Authorization procedure in the UE MM Core Network Capability in the Registration Request, AMF includes in the Pending NSSAI the S-NSSAIs that map to an S-NSSAI of the HPLMN which in the subscription information has indication that it is subject to Network Slice-Specific Authentication and Authorization, as described in clause 4.6.2.4 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. In such case, the AMF then shall trigger at step 25 the Network Slice-Specific Authentication and Authorization procedure, specified in clause 4.2.9.2, except, based on Network policies, for those S-NSSAIs for which Network Slice-Specific Authentication and Authorization have already been initiated on another Access Type for the same S-NSSAI(s). The UE shall not attempt re-registration with the S-NSSAIs included in the list of Pending NSSAIs until the Network Slice-Specific Authentication and Authorization procedure has been completed, regardless of the Access Type. If the UE has not indicated its support of the Network Slice-Specific Authentication and Authorization procedure in the UE 5GMM Core Network Capability in the Registration Request and the Requested NSSAI includes S-NSSAIs which map to HPLMN S-NSSAIs subject to Network Slice-Specific Authentication and Authorization, the AMF includes those S-NSSAIs in the Requested NSSAI in the Rejected S-NSSAIs. If no S-NSSAI can be provided in the Allowed NSSAI because: - all the S-NSSAI(s) in the Requested NSSAI are to be subject to Network Slice-Specific Authentication and Authorization; or - no Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI matches any of the Subscribed S-NSSAIs and all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs are to be subject to Network Slice-Specific Authentication and Authorization. The AMF shall provide an empty Allowed NSSAI. Upon receiving an empty Allowed NSSAI and a Pending NSSAI, the UE is registered in the PLMN but shall wait for the completion of the Network Slice-Specific Authentication and Authorization procedure without attempting to use any service provided by the PLMN on any access, except e.g. emergency services (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]), until the UE receives an Allowed NSSAI. The AMF stores the NB-IoT Priority retrieved in Step 14 and associates it to the 5G-S-TMSI allocated to the UE. If the Registration Request message received over 3GPP access does not include any Paging Restriction Information, the AMF shall delete any stored Paging Restriction Information for this UE and stop restricting paging accordingly. If the Registration Request message received over 3GPP access includes the Paging Restriction Information, AMF may accept or reject the Paging Restriction Information requested by the UE based on operator policy. If the AMF rejects the Paging Restriction Information, the AMF removes any stored Paging Restriction Information from the UE context and discards the UE requested Paging Restriction Information. If the AMF accepts the Paging Restriction Information from the UE, the AMF stores the Paging Restriction Information from the UE in the UE context and informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the Registration Accept message. If the Registration Request message received over 3GPP access includes a Release Request indication, then: - the AMF updates the UE context with any received Paging Restriction Information, then enforces it in the network triggered Service Request procedure as described in clause 4.2.3.3; - the AMF does not establish User Plane resources and triggers the AN release procedure as described in clause 4.2.6 after the completion of Registration procedure. The AMF sends a Registration Accept message to the UE indicating that the Registration Request has been accepted. 5G-GUTI is included if the AMF allocates a new 5G-GUTI. Upon receiving a Registration Request message of type "Initial Registration", "mobility registration update", "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update" from the UE, the AMF shall include a new 5G-GUTI in the Registration Accept message. Upon receiving a Registration Request message of type "periodic registration update" from the UE, the AMF should include a new 5G-GUTI in the Registration Accept message. If the UE is already in RM-REGISTERED state via another access in the same PLMN, the UE shall use the 5G-GUTI received in the Registration Accept for both registrations. If no 5G-GUTI is included in the Registration Accept, then the UE uses the 5G-GUTI assigned for the existing registration also for the new registration. If the AMF allocates a new Registration area, it shall send the Registration area to the UE via Registration Accept message. For a Disaster Roaming Registration, the AMF allocates the Registration Area limited to the area with Disaster Condition as specified in clause 5.40 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If there is no Registration area included in the Registration Accept message, the UE shall consider the old Registration Area as valid. Mobility Restrictions is included if mobility restrictions applies for the UE and Registration Type is not Emergency Registration. The AMF indicates the established PDU Sessions to the UE in the PDU Session status. The UE removes locally any internal resources related to PDU Sessions that are not marked as established in the received PDU Session status. If the AMF invokes the Nsmf_PDUSession_UpdateSMContext procedure for UP activation of PDU Session(s) in step 18 and receives rejection from the SMF, then the AMF indicates to the UE the PDU Session ID and the cause why the User Plane resources were not activated. When the UE is connected to the two AMFs belonging to different PLMN via 3GPP access and non-3GPP access then the UE removes locally any internal resources related to the PDU Session of the current PLMN that are not marked as established in received PDU Session status. If the PDU Session status information was in the Registration Request, the AMF shall indicate the PDU Session status to the UE. If the RAT Type is NB-IoT and the network is configured to use the Control Plane Relocation Indication procedure then the AMF shall include in the Registration Accept message the Truncated 5G-S-TMSI Configuration that the UE using Control Plane CIoT 5GS Optimisation uses to create the Truncated 5G-S-TMSI, see clause 5.31.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Allowed NSSAI provided in the Registration Accept is valid in the Registration Area and it applies for all the PLMNs which have their Tracking Areas included in the Registration Area. The Mapping Of Allowed NSSAI is the mapping of each S-NSSAI of the Allowed NSSAI to the HPLMN S-NSSAIs. The Mapping Of Configured NSSAI is the mapping of each S-NSSAI of the Configured NSSAI for the Serving PLMN to the HPLMN S-NSSAIs. For non-roaming UE, if the UE has indicated its support of Slice Usange Policy in the UE 5GMM Core Network Capability, the AMF may include Slice Usage Policies for the slices in the Configured NSSAI as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the Slice Usage Policy, the AMF indicates if an S-NSSAI is on demand slice and slice deregistration inactivity timer value. If the AMF includes slice deregistration timer value, the UE starts any slice deregistration inactivity timer for the on demand S-NSSAIs as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has indicated its support of the subscription-based restrictions to simultaneous registration of network slices feature in the UE 5GMM Core Network Capability, the AMF includes, if available, the NSSRG Information, defined in clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has not indicated its support of the subscription-based restrictions to simultaneous registration of network slices feature and the subscription information for the UE includes NSSRG information and the AMF is providing the Configured NSSAI to the UE, the Configured NSSAI shall include the S-NSSAIs according to clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has indicated its support for temporary available network slices feature in the UE 5GMM Core Network Capability, the AMF includes validity time defined in clause 5.15.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has not indicated its support for temporary available network slices feature in the UE 5GMM Core Network Capability and the AMF is providing the Configured NSSAI to the UE, the Configured NSSAI shall not include the S-NSSAIs if the validity time indicates S-NSSAI is not available according to clause 5.15.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has indicated its support of the NSAG feature in the 5GMM Core Network Capability, the AMF includes, if available, the NSAG Information, defined in clause 5.15.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF shall include in the Registration Accept message the LADN Information for the list of LADNs, described in clause 5.6.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], that are available within the Registration area determined by the AMF for the UE. If the UE indicates its support of LADN per DNN and S-NSSAI in the UE MM Core Network Capability, the AMF may include LADN Information per DNN and S-NSSAI. The AMF may include Operator-defined access category definitions to let the UE determinine the applicable Operator-specific access category definitions as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. If the UE included MICO Indication in the Registration Request, then AMF responds in the Registration Accept message whether MICO mode should be used in the MICO Indication. When MICO mode is allowed for the UE, the AMF may include an Active Time value and/or Strictly Periodic Registration Timer Indication in the Registration Accept message. The AMF determines the Periodic Registration Update timer value, Active Time value and the Strictly Periodic Registration Timer Indication based on: - local configuration; - Expected UE Behaviour if available; - UE indicated preferences; - UE capability; - UE subscription information; - if using a RAN that provides discontinuous coverage, UE availability (see clause 5.4.13.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]); and - network policies, or any combination of them so as to enable UE power saving, as described in clause 5.31.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF determines to apply the Strictly Periodic Registration Timer Indication to the UE if the UE indicates its capability of the Strictly Periodic Registration Timer Indication in the registration request message, as described in step 1. If the AMF provides the Periodic Registration Update timer value with the Strictly Periodic Registration Timer Indication to the UE, the UE and the AMF start the Periodic Registration Update timer after this step, as described in clause 5.31.7.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of registration over 3GPP access, the AMF Sets the IMS Voice over PS session supported Indication as described in clause 5.16.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In order to set the IMS Voice over PS session supported Indication the AMF may need to perform the UE Capability Match Request procedure in clause 4.2.8a to check the compatibility of the UE and NG-RAN radio capabilities related to IMS Voice over PS. If the AMF hasn't received Voice Support Match Indicator from the NG-RAN on time then, based on implementation, AMF may set IMS Voice over PS session supported Indication and update it at a later stage. In the case of registration over 3GPP access and the AMF has retrieved or determined according to local configuration a Target NSSAI and a corresponding RFSP Index for the purpose of allowing the NG-RAN to redirect the UE to a cell supporting network slices not available in the current TA as described in clause 5.3.4.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF provides the Target NSSAI and the corresponding RFSP Index to the NG-RAN. In the case of registration over non-3GPP access, the AMF Sets the IMS Voice over PS session supported Indication as described in clause 5.16.3.2a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Emergency Service Support indicator informs the UE that emergency services are supported, i.e. the UE is allowed to request PDU Session for emergency services. If the AMF received "MPS priority" from the UDM as part of Access and Mobility Subscription data, based on operator policy, "MPS priority" is included in the Registration Accept message to the UE to inform the UE whether configuration of Access Identity 1 is valid within the selected PLMN, as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. If the AMF received "MCX priority" from the UDM as part of Access and Mobility Subscription data, based on operator policy and UE subscription to MCX Services, "MCX priority" is included in the Registration Accept message to the UE to inform the UE whether configuration of Access Identity 2 is valid within the selected PLMN, as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. The Accepted DRX parameters are defined in clause 5.4.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF includes Accepted DRX parameters for NB-IoT, if the UE included Requested DRX parameters for NB-IoT in the Registration Request message. The AMF Sets the Network support of Interworking without N26 parameter as described in clause 5.17.2.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the AMF accepts the use of extended idle mode DRX, the AMF includes the extended idle mode DRX parameters and Paging Time Window as described in 5.31.7.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For a UE using NR satellite access that provides discontinuous coverage, the AMF may determine extended idle mode DRX parameters and Paging Time Window considering the Unavailability Period Duration (if available), Start of Unavailability Period (if available) and the UE requested extended idle mode DRX parameters as described in clause 5.4.13.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UDM intends to indicate the UE that subscription has changed, the Network Slicing Subscription Change Indication is included. If the AMF includes Network Slicing Subscription Change Indication, then the UE shall locally erase all the network slicing configuration for all PLMNs and if applicable, update the configuration for the current PLMN based on any received information. The Access Stratum Connection Establishment NSSAI Inclusion Mode, as specified in clause 5.15.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], is included to instruct the UE on what NSSAI, if any, to include in the Access Stratum connection establishment. The AMF can set the value to modes of operation a,b,c defined in clause 5.15.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] in the 3GPP Access only if the Inclusion of NSSAI in RRC Connection Establishment Allowed indicates that it is allowed to do so. For a UE registered in a PLMN, the AMF may provide a List of equivalent PLMNs which is handled as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. The AMF shall not provide a list of equivalent SNPNs to the UE. For a UE registered in an SNPN and the UE has included support of equivalent SNPNs in step 1, the AMF may provide a List of equivalent SNPNs which is handled as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. The AMF shall not provide a list of equivalent PLMNs to the UE. If the UE included support for restriction of use of Enhanced Coverage in step 1, the AMF sends the Enhanced Coverage Restricted information to the NG-RAN in N2 message. The AMF also sends Enhanced Coverage Restricted information to the UE in the Registration Accept message. If the UE receives Enhanced Coverage Restricted information in the Registration Accept message, the UE shall store this information and shall use the value of Enhanced Coverage Restricted information to determine if Enhanced Coverage feature should be used or not. If the UE and the AMF have negotiated to enable MICO mode via MICO Indication and the AMF uses the Extended connected timer, then the AMF provides the Extended Connected time value to NG-RAN (see clause 5.31.7.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) in this step. The Extended Connected Time value indicates the minimum time the RAN should keep the UE in RRC_CONNECTED state regardless of inactivity. For a UE using NR satellite access that provides discontinuous coverage, the AMF may determine the Extended Connected Timer value considering the Unavailability Period Duration (if available), Start of Unavailability Period (if available) as described in clause 5.4.13.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF indicates the CIoT 5GS Optimisations it supports and accepts in the Supported Network Behaviour information (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) if the UE included Preferred Network Behaviour in its Registration Request. The AMF may steer the UE from 5GC by rejecting the Registration Request. The AMF should take into account the Preferred and Supported Network Behaviour (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and availability of EPC to the UE before steering the UE from 5GC. If the AMF accepts MICO mode as indicated in Registration Accept via MICO Indication and knows there may be mobile terminated data or signalling pending, the AMF maintains the N2 connection for at least the Extended Connected Time as described in clause 5.31.7.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and provides the Extended Connected Time value to the RAN. The AMF includes Service Gap Time if Service Gap Time is present in the subscription information (steps 14a-c) or the Service Gap Time has been updated by the Subscriber Data Update Notification to AMF procedure (see clause 4.5.1) and the UE has indicated UE Service Gap Control Capability. If the UE receives a Service Gap Time in the Registration Accept message, the UE shall store this parameter and apply Service Gap Control (see clause 5.31.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the network supports WUS grouping (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the AMF shall send the WUS Assistance Information to the UE. If the UE provided the UE paging probability information in Step 1, the AMF takes it into account to determine the WUS Assistance Information. If the UE provided Paging Subgrouping Support Indication in step 1, a supporting AMF may provide the AMF PEIPS Assistance Information, including the Paging Subgroup ID as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the UE and the AMF supports RACS as defined in clause 5.4.4.1a of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the AMF needs to configure the UE with a UE Radio Capability ID and the AMF already has the UE radio capabilities other than NB-IoT radio capabilities for the UE, the AMF may provide the UE with the UE Radio Capability ID for the UE radio capabilities the UCMF returns to the AMF in a Nucmf_assign service operation for this UE. Alternatively, when the UE and the AMF support RACS, the AMF may provide the UE with an indication to delete any PLMN-assigned UE Radio Capability ID in this PLMN (see clause 5.4.4.1a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the UE is "CAG supported" and the AMF needs to update the CAG information of the UE, the AMF may include the CAG information as part of the Mobility Restrictions in the Registration Accept message. If the UE has indicated the support of Unavailability Period in the UE MM Core Network Capability in the Registration Request, the AMF shall indicate to the UE whether the corresponding feature is supported by providing the "Unavailability Period Support" indication. If the UE has provided Unavailability Period Duration and/or Start of Unavailability Period in step 1, the AMF shall store the received Unavailability Period Duration and/or Start of Unavailability Period in UE context. The AMF considers that the UE is unavailable at the start of unavailability period as described in clause 5.4.1.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF may provide Periodic Registration Update timer based on Unavailability Period Duration and/or Start of Unavailability Period indicated by the UE as described in clause 5.4.1.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Multi-USIM UE has indicated support for one or more Multi-USIM Specific Capabilities in the UE 5GMM Core Network Capability in step 1, the AMF shall indicate to the Multi-USIM UE whether the corresponding one or more Multi-USIM specific features described in clause 5.38 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] are supported, based on network capability and preference by the network (i.e. based on local network policy), by providing one or more of the Connection Release Supported, Paging Cause Indication for Voice Service Supported, Paging Restriction Supported and Reject Paging Request Supported indications. The AMF shall only indicate Paging Restriction Supported together with either Connection Release Supported or Reject Paging Request Supported. The UE shall only use Multi-USIM specific features that the AMF indicated as being supported. If the NG-RAN provides MBSR indication in step 3 and the subscription data received in step 14 does not allow the MBSR operation, the AMF may either accept the registration with providing the MBSR authorization information to MBSR (IAB-UE), or the AMF may reject the registration if the PLMN does not allow the MBSR (IAB-UE) to be registered to the PLMN as specified in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE and AMF supports Disaster Roaming service, the AMF may include the "list of PLMN(s) to be used in Disaster Condition", Disaster Roaming wait range information and Disaster Return wait range information as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If AMF receives multiple TAIs from the NG-RAN in step 3 and determines that some, but not all of them are forbidden by subscription or by operator policy, the AMF shall include the forbidden TAI(s) in the Registration Accept message. In the case of Emergency Registration, the AMF shall not indicate support for any Multi-USIM specific features to the UE. If the UE has included support of equivalent SNPNs in step 1 and the serving SNPN changes, the AMF shall include the Registered NID in the Registration Accept message as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For a UE using NR satellite access that provides discontinuous coverage, the AMF may provide Return To Coverage Notification Not Required, which requests the UE in CM-IDLE state to not perform the Mobility Registration Update procedure when it returns to coverage and/or provide the UE with a Unavailability Period Duration and/or Start of Unavailability Period (if available), as described in clause 5.4.13.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF may determine a Maximum Time Offset and provide it to UE when it is allowed to initiate NAS signalling with the network as described in clause 5.4.13.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has indicated the support of S-NSSAI location availability information, the AMF may include S-NSSAI location availability information as described in clause 5.15.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE indicated a support for the Network Slice Replacement feature in the 5GMM Core Network Capability and the AMF determines that an S-NSSAI from an Allowed NSSAI is to be replaced with an Alternative S-NSSAI (as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the AMF includes the Mapping Of Alternative NSSAI within the Registration Accept message to the UE and also adds the Alternative S-NSSAI to the Allowed NSSAI and/or Configured NSSAI, if not already included. The Mapping Of Alternative NSSAI is the mapping of each Alternative S-NSSAI, included in the Allowed NSSAI and/or Configured NSSAI, to the corresponding replaced VPLMN S-NSSAI or HPLMN S-NSSAI (as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the UE has indicated a support for reconnection to the network due to RAN timing synchronization status in step 1 as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], and if the AMF received "clock quality detail level" either as part of an AM Policy Association procedure or from the UDM as part of Clock Quality Reporting Control Information (CQRCI) included in the Access and Mobility Subscription data, "UE reconnection indication" is included in the Registration Accept message to the UE to inform the UE when to connect to the network in case when the UE later detects that the NG-RAN timing synchronization status has changed while the UE is in RRC IDLE or RRC INACTIVE state, as specified in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 21b. [Optional] The new AMF performs a UE Policy Association Establishment as defined in clause 4.16.11. For an Emergency Registration, this step is skipped. The new AMF sends a Npcf_UEPolicyControl Create Request to PCF. PCF sends a Npcf_UEPolicyControl Create Response to the new AMF. PCF triggers UE Configuration Update Procedure as defined in clause 4.2.4.3. 22. [Conditional] UE to new AMF: Registration Complete (). The UE sends a Registration Complete message to the AMF when it has successfully updated itself after receiving any of the [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI], [NSSRG Information], [NSAG Information] and a Network Slicing Subscription Change Indication, or CAG information in step 21. The UE sends a Registration Complete message to the AMF to acknowledge if a new 5G-GUTI was assigned. If new 5G-GUTI was assigned, then the UE passes the new 5G-GUTI to its 3GPP access' lower layer when a lower layer (either 3GPP access or non-3GPP access) indicates to the UE's RM layer that the Registration Complete message has been successfully transferred across the radio interface. NOTE 13: The above is needed because the NG-RAN may use the RRC_INACTIVE state and a part of the 5G-GUTI is used to calculate the Paging Frame (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [44] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [43]). It is assumed that the Registration Complete is reliably delivered to the AMF after the 5G-AN has acknowledged its receipt to the UE. When the List Of PDU Sessions To Be Activated is not included in the Registration Request and the Registration procedure was not initiated in CM-CONNECTED state, the AMF releases the signalling connection with UE, according to clause 4.2.6. When the Follow-on request is included in the Registration Request, the AMF should not release the signalling connection after the completion of the Registration procedure. If the AMF is aware that some signalling is pending in the AMF or between the UE and the 5GC, the AMF should not release the signalling connection immediately after the completion of the Registration procedure. If the UE has provided Unavailability Period Duration and not included Start of Unavailability Period in step 1, the AMF shall release the signalling connection immediately after the completion of the Registration procedure. If the UE has indicated Start of Unavailability Period in step 1, the AMF shall release the signalling connection before the start of unavailability period. If PLMN-assigned UE Radio Capability ID is included in step 21, the AMF stores the PLMN-assigned UE Radio Capability ID in UE context if receiving Registration Complete message. If the UE receives PLMN-assigned UE Radio Capability ID deletion indication in step 21, the UE shall delete the PLMN-assigned UE Radio Capability ID(s) for this PLMN. 23. [Conditional] AMF to UDM: If the Access and Mobility Subscription data provided by UDM to AMF in 14b includes Steering of Roaming information with an indication that the UDM requests an acknowledgement of the reception of this information from the UE, the AMF provides the UE acknowledgement to UDM using Nudm_SDM_Info. For more details regarding the handling of Steering of Roaming information refer to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. 23a. For Registration over 3GPP Access, if the AMF does not release the signalling connection, the AMF sends the RRC Inactive Assistance Information to the NG-RAN. For Registration over non-3GPP Access, if the UE is also in CM-CONNECTED state on 3GPP access, the AMF sends the RRC Inactive Assistance Information to the NG-RAN. If the Multi-USIM UE has indicated support for the Paging Cause Indication for Voice Service feature and the network supports the Paging Cause Indication for Voice Service, the AMF shall include an indication in the RRC Inactive Assistance Information that the UE supports the Paging Cause Indication for Voice Service to NG-RAN to enable NG-RAN to apply the Paging Cause Indication for Voice Service feature for RAN based paging. The AMF also uses the Nudm_SDM_Info service operation to provide an acknowledgment to UDM that the UE received CAG information, or the Network Slicing Subscription Change Indication (see step 21 and step 22) and acted upon it. 24. [Conditional] AMF to UDM: After step 14a and in parallel to any of the preceding steps, the AMF shall send a "Homogeneous Support of IMS Voice over PS Sessions" indication to the UDM using Nudm_UECM_Update: - If the AMF has evaluated the support of IMS Voice over PS Sessions, see clause 5.16.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; and - If the AMF determines that it needs to update the Homogeneous Support of IMS Voice over PS Sessions, see clause 5.16.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 25. [Conditional] If the UE indicates its support for Network Slice-Specific Authentication and Authorization procedure in the UE MM Core Network Capability in Registration Request and any S-NSSAI of the HPLMN is subject to Network Slice-Specific Authentication and Authorization, the related procedure is executed at this step (see clause 4.2.9.1). Once the Network Slice-Specific Authentication and Authorization procedure is completed for all S-NSSAIs, the AMF shall trigger a UE Configuration Update procedure to deliver an Allowed NSSAI (or Partially Allowed NSSAI) containing also the S-NSSAIs for which the Network Slice-Specific Authentication and Authorization was successful and include any rejected NSSAIs with an appropriate rejection cause value. The AMF stores an indication in the UE context for any S-NSSAI of the HPLMN subject to Network Slice-Specific Authentication and Authorization for which the Network Slice-Specific Authentication and Authorization succeeds. Once completed the Network Slice-Specific Authentication and Authorization procedure, if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE, which is already authenticated and authorized successfully by a PLMN and if no default S-NSSAI(s) could be further considered, the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 and shall include in the explicit De-Registration Request message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. If Unavailability Period Duration is received from the UE and there is "Loss of Connectivity" monitoring event subscription for the UE, the AMF triggers "Loss of Connectivity" monitoring event report and includes the remaining values of the Unavailability Period Duration as described in clause 4.15. The mobility related event notifications towards the NF consumers are triggered at the end of this procedure for cases as described in clause 4.15.4. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2.2 |
3,905 | 4.3.15a.2 SIPTO at the Local Network with stand-alone GW (with S-GW and L-GW collocated) function | SIPTO at the Local Network is achieved using a stand-alone GW (with S-GW and L-GW collocated) residing in the Local Network. A (H)eNB supporting SIPTO at the Local Network with the stand-alone GW includes the Local Home Network ID to the MME in every INITIAL UE MESSAGE, every UPLINK NAS TRANSPORT control message, HANDOVER NOTIFY and PATH SWITCH REQUEST messages. If a SIPTO PDN connection is initiated as an additional subsequent PDN connection, the MME should check if the S-GW is optimal for the user's current location. If it is not, and if the network supports S-GW relocation without being triggered by a mobility event, the MME may decide to perform an MME triggered Serving GW relocation according to clause 5.10.4, when possible (e.g. no other restrictions apply). For SIPTO at the Local Network with a stand-alone GW, the location of the Serving GW may be determined based on the operator policy and user's profile regarding support of SIPTO at Local Network so that: - At attachment to the (H)eNB, a local S-GW can always be selected independent of whether a SIPTO at the Local Network PDN connection is established or not. If mobility is performed to the macro network without having a SIPTO connection, a S-GW relocation can be performed as specified via existing mobility procedures with S-GW relocation. - At attachment to a (H)eNB, a macro S-GW may be allocated for PDN connection in the operator's network. If a new PDN connection is requested by the UE that requires that a local S-GW is selected to provide for SIPTO at the Local Network, S-GW relocation from the macro S-GW to the local S-GW shall be performed as specified in clause 5.10.4. As IP data session continuity for SIPTO at the Local Network PDN connection is not supported in this release of the specification, subsequent to handover completion the (target) MME should disconnect the SIPTO at the Local Network PDN connection with "reactivation requested" cause as specified in clause 5.10.3, unless the Local Home Network ID is not changed. The IP data session should be maintained if the Local Home Network ID is not changed. If the UE has no other PDN connection and the Local Home Network ID is changed, the (target) MME initiates "explicit detach with reattach required" procedure according to clause 5.3.8.3. Upon completion of Tracking Area Update procedure, the (new) MME shall trigger the re-establishment of the SIPTO at the Local Network PDN connection when it detects that the UE has moved away from the (H)eNB and to a (H)eNB with different Local Home Network ID, as specified in clause 5.3.3 and clause 5.3.4. NOTE: It is expected that all MMEs/SGSNs in a PLMN have support for SIPTO at the Local Network where the operator deploys this feature, in order to support mobility procedures. For a mobility event where target MME/SGSN does not support SIPTO at the Local Network, the handling of PDN deactivation for SIPTO at Local Network PDN connection is not specified. | 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.15a.2 |
3,906 | 9.3.1.2.3 FDD (Modulation and TBS index Table 2 and 4-bit CQI Table 2 are used) | For the parameters specified in Table 9.3.1.2.3-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.2.3-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. In this test, 4-bit CQI Table 2 in Table 7.2.3-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6], and Modulation and TBS index table 2 in Table 7.1.7.1-1A for PDSCH in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] are applied. Table 9.3.1.2.3-1 Sub-band test for FDD Table 9.3.1.2.3-2 Minimum requirement (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.3.1.2.3 |
3,907 | 7.6.3 Repeated IEs | If an information element with format T, TV, TLV, or TLV-E is repeated in a message in which repetition of the information element is not specified in clause 8 of the present document, the UE shall handle only the contents of the information element appearing first and shall ignore all subsequent repetitions of the information element. When repetition of information elements is specified, the UE shall handle only the contents of specified repeated information elements. If the limit on repetition of information elements is exceeded, the UE shall handle the contents of information elements appearing first up to the limit of repetitions and shall ignore all subsequent repetitions of the information element. The network should follow the same procedures. | 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.6.3 |
3,908 | 7.3.6 Context Response | A Context Response message shall be sent as a response to a previous Context Request message, in the scenarios identified in clause 7.3.5. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "IMSI/IMEI not known" - "P-TMSI Signature mismatch" - "User authentication failed" - "Target access restricted for the subscriber" Based on the subscription profile, when the access to the target RAT is prohibited for the subscriber, the old MME/SGSN/AMF may reject the Context Request message with the cause "Target access restricted for the subscriber". When the source MME/SGSN/AMF supports one or more of the CIoT optimization features as indicated through the CIoT Optimizations Support Indication IE specified in clause 8.125, and if the target node is a MME and the target MME has not set the AWOPDN bit of the CIoT Optimizations Support Indication IE set to 1 in the Context Request message as specified in clause 8.125, the source MME/SGSN/AMF shall reject the Context Request with a cause value of "Request Rejected" under the following conditions (conditions are mutually exclusive): - If the UE is attached to the source MME/SGSN without any PDN connection through the SGW and PGW and without any SCEF PDN connection; - if the UE is attached to the source MME/SGSN with only the PDN connection(s) of PDN type "non-IP", through the SGW and the PGW but the UE has not activated any SCEF PDN connection and the target MME/AMF has not set the SGNIPDN bit of the CIoT Optimizations Support Indication IE set to 1 in the Context Request message as specified in clause 8.125; - if the UE is attached to the the source MME/SGSN with only the SCEF PDN connection(s) but the UE has not activated any PDN connection through the SGW and PGW and the target MME has not set the SCNIPDN bit of the CIoT Optimizations Support Indication IE set to 1 in the Context Request message as specified in clause 8.125; - if the UE is attached to the source MME/SGSN with only PDN connection(s) of PDN type "non-IP", through the SGW and the PGW and at least one SCEF PDN connection and the target MME has neither set the SGNIPDN bit nor the SCNIPDN bit of the CIoT Optimizations Support Indication IE set to 1 in the Context Request message as specified in clause 8.125; - if the UE is registered to the source AMF without any PDU session; - if the UE is registered to the source AMF with only PDU session(s) of type "Unstructured" or "Ethernet", and the target MME has not set the SGNIPDN bit of the CIoT Optimizations Support Indication IE set to 1 in the Context Request message as specified in clause 8.125. NOTE 2: Among the CIoT optimization features, only the support of SCEF Non-IP PDN connection and the support of SGi Non-IP PDN connection are applicable to a SGSN. NOTE 3: 5GS supports Attach without PDU session. 5GS can also support Unstructured and Ethernet PDU session types, which are assimilated to "SGi Non-IP PDN connections" over N26 if Ethernet PDN connection type in EPC is not supported; otherwise, the Ethernet PDU session in 5GS can move to EPC seamlessly. If the target node is a MME and the target MME has not set the ETHPDN bit in the Indication IE to 1 in the Context Request message as specified in clause 8.12, or the target node is a SGSN, the source MME shall reject the Context Request with a cause value of "Request Rejected" if the UE is attached to the source MME with only PDN connection(s) of PDN type "Ethernet". Table 7.3.6-1 specifies the presence requirements and conditions of the IEs in the message. Table 7.3.6-1: Information Elements in a Context Response Table 7.3.6-2: MME/SGSN/AMF UE EPS PDN Connections within Context Response The Bearer Context shall be coded as depicted in Table 7.3.6-3. Table 7.3.6-3: Bearer Context within MME/SGSN/AMF UE EPS PDN Connections within Context Response Table 7.3.6-4: Remote UE Context Connected within MME/SGSN UE EPS PDN Connections within Context Response Table 7.3.6-5: MME/SGSN UE SCEF PDN Connections within Context Response Table 7.3.6-6: PGW Change Info with Context Response | 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 | 7.3.6 |
3,909 | 5.4.1.3 Mobile Initiated Connection Only (MICO) mode | A UE may indicate preference for MICO mode during Initial Registration or Mobility Registration Update procedure. The AMF, based on local configuration, Expected UE Behaviour and/or Network Configuration parameters if available from the UDM, UE indicated preferences, UE subscription information and network policies, or any combination of them, determines whether MICO mode is allowed for the UE and indicates it to the UE during Registration procedure. If NWDAF is deployed, the AMF may also use analytics on UE mobility and/or UE communication generated by NWDAF (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]) to decide MICO mode parameters. If the UE does not indicate preference for MICO mode during Registration procedure, the AMF shall not activate MICO mode for this UE. The UE and the AMF re- negotiate the MICO mode at every subsequent Registration procedure. When the UE is in CM-CONNECTED, the AMF may deactivate MICO mode by triggering Mobility Registration Update procedure through UE Configuration Update procedure as described in clause 4.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AMF assigns a registration area to the UE during the Registration procedure. When the AMF indicates MICO mode to a UE, the registration area is not constrained by paging area size. If the AMF serving area is the whole PLMN, based on local policy, and subscription information, may decide to provide an "all PLMN" registration area to the UE. In that case, re-registration to the same PLMN due to mobility does not apply. If Mobility Restrictions are applied to a UE in MICO mode, the AMF needs to allocate an Allowed Area/Non-Allowed Area to the UE as specified in clause 5.3.4.1. When the AMF indicates MICO mode to a UE, the AMF considers the UE always unreachable while the UE CM state in the AMF is CM-IDLE. The AMF rejects any request for downlink data delivery for UE in MICO mode and whose UE CM state in the AMF is CM-IDLE with an appropriate cause. For MT-SMS over NAS, the AMF notifies the SMSF that UE is not reachable, then the procedure of the unsuccessful Mobile terminating SMS delivery described in clause 4.13.3.9 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] is performed. The AMF also defers location services, etc. The UE in MICO mode is only reachable for mobile terminated data or signalling when the UE is in CM-CONNECTED. A UE in MICO mode need not listen to paging while in CM-IDLE. A UE in MICO mode may stop any access stratum procedures in CM-IDLE, until the UE initiates transition from CM-IDLE to CM-CONNECTED due to one of the following triggers: - A change in the UE (e.g. change in configuration) requires an update of its registration with the network. - Periodic registration timer expires. - MO data pending. - MO signalling pending (e.g. SM procedure initiated). If a registration area that is not the "all PLMN" registration area is allocated to a UE in MICO mode, then the UE determines if it is within the registration area or not when it has MO data or MO signalling, and the UE performs Mobility Registration Update before the UE initiates the MO data or MO signalling if it is not within the registration area. A UE initiating emergency service shall not indicate MICO preference during Registration procedure. When the MICO mode is already activated in the UE, the UE and AMF shall locally disable MICO mode after PDU Session Establishment procedure for Emergency Services is completed successfully. The UE and the AMF shall not enable MICO mode until the AMF accepts the use of MICO mode in the next registration procedure. To enable an emergency call back, the UE should wait for a UE implementation-specific duration of time before requesting the use of MICO mode after the release of the emergency PDU session. In order to enable power saving for MT reachability e.g. for Cellular IoT, enhancements to MICO mode are specified in clause 5.31.7: - MICO mode with Extended Connected Time. - MICO mode with Active Time. - MICO mode and Periodic Registration Timer Control. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.1.3 |
3,910 | 5.3.5.13c FR2 UL gap configuration | The UE shall: 1> if ul-GapFR2-Config is set to setup: 2> if an FR2 UL gap configuration is already setup, release the FR2 UL gap configuration; 2> setup the FR2 UL gap configuration indicated by the ul-GapFR2-Config in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: SFN mod T = FLOOR (gapOffset/10); if the UGRP is larger than 5ms: subframe = gapOffset mod 10; else: subframe = gapOffset or (gapOffset +5); with T = CEIL(UGRP/10). 1> else if ul-GapFR2-Config is set to release: 2> release the FR2 UL gap configuration. NOTE 1: For ul-GapFR2-Config configuration with synchronous CA, the SFN and subframe of a serving cell on FR2 frequency is used in the gap calculation. For ul-GapFR2-Config configuration with asynchronous CA, the SFN and subframe of a serving cell on FR2 frequency indicated by the refFR2-ServCellAsyncCA in ul-GapFR2-Config is used in the gap calculation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13c |
3,911 | 6.8.2.1.2 State transition from RRC_CONNECTED to RRC_INACTIVE | The gNB/ng-eNB shall send to the UE an RRCRelease with suspendConfig message that is ciphered and integrity protected in PDCP layer using a current AS security context. The gNB/ng-eNB shall include a fresh I-RNTI, and an NCC in that RRCRelease with suspendConfig message. The I-RNTI is used for context identification, and the UE ID part of the I-RNTI assigned by the gNB/ng-eNB shall be different in consecutive suspends of the same UE. This is to avoid tracking of UEs based on the I-RNTI. If the gNB/ng-eNB has a fresh and unused pair of {NCC, NH}, the gNB/ng-eNB shall include the NCC in the RRCRelease with suspendConfig message. Otherwise, the gNB/ng-eNB shall include the same NCC associated with the current KgNB in the RRCRelease with suspendConfig message. The NCC is used for AS security. The gNB/ng-eNB shall delete the current AS keys KRRCenc, KUPenc (if available), and KUPint (if available) after sending the RRCRelease with suspendConfig message to the UE, but shall keep the current AS key KRRCint. If the sent NCC value is fresh and belongs to an unused pair of {NCC, NH}, the gNB/ng-eNB shall save the pair of {NCC, NH} in the current UE AS security context and shall delete the current AS key KgNB. If the sent NCC value is equal to the NCC value associated with the current KgNB, the gNB/ng-eNB shall keep the current AS key KgNB and NCC. The gNB/ng-eNB shall store the sent I-RNTI together with the current UE context including the remainder of the AS security context. Upon receiving the RRC Release with suspendConfig message from the gNB/ng-eNB, the UE shall verify that the integrity of the received RRCRelease with suspendConfig message is correct by checking the PDCP MAC-I. If this verification is successful, then the UE shall take the received NCC value and save it as stored NCC with the current UE context. The UE shall delete the current AS keys KRRCenc, KUPenc (if available), and KUPint (if available), but keep the current AS key KRRCint key. If the stored NCC value is different from the NCC value associated with the current KgNB, the UE shall delete the current AS key KgNB. If the stored NCC is equal to the NCC value associated with the current KgNB, the UE shall keep the current AS key KgNB. The UE shall store the received I-RNTI together with the current UE context including the remainder of the AS security context, for the next state transition. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.2.1.2 |
3,912 | – MeasResultsSL | The IE MeasResultsSL covers measured results for NR sidelink communication/discovery. MeasResultsSL information element -- ASN1START -- TAG-MEASRESULTSSL-START MeasResultsSL-r16 ::= SEQUENCE { measResultsListSL-r16 CHOICE { measResultNR-SL-r16 MeasResultNR-SL-r16, ... }, ... } MeasResultNR-SL-r16 ::= SEQUENCE { measResultListCBR-NR-r16 SEQUENCE (SIZE (1.. maxNrofSL-PoolToMeasureNR-r16)) OF MeasResultCBR-NR-r16, ... } MeasResultCBR-NR-r16 ::= SEQUENCE { sl-poolReportIdentity-r16 SL-ResourcePoolID-r16, sl-CBR-ResultsNR-r16 SL-CBR-r16, ... } -- TAG-MEASRESULTSSL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,913 | 6.6.3.1 Minimum requirements | Unless otherwise stated, the spurious emission limits apply for the frequency ranges that are more than FOOB (MHz) in Table 6.6.3.1-1 from the edge of the channel bandwidth. The spurious emission limits in Table 6.6.3.1-2 apply for all transmitter band configurations (NRB) and channel bandwidths. NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. Table 6.6.3.1-1: Boundary between E-UTRA out of band and spurious emission domain Table 6.6.3.1-2: Spurious emissions limits | 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 | 6.6.3.1 |
3,914 | 5.2.3.1 Initiation | Before call establishment can be initiated in the mobile station, the MM connection shall be established by the network. After the arrival of an appropriate stimulus (for example a Remote User Free Indication), the corresponding call control entity in the network shall initiate the MM connection establishment according to clause 4, enter the "CC connection pending" state and start timer T331. The request to establish the MM connection is passed from the CM sublayer to the MM sublayer. It contains the necessary routing information derived from the received stimulus. Upon completion of the MM connection, the call control entity of the mobile station shall send a START CC message to its peer entity in the network. The mobile station shall then enter the "Wait for network information" state and start timer T332. If the network receives a START CC message while in the "CC connection pending" state, the network stops T331, sends the CC-ESTABLISHMENT message, starts timer T333 and enters the "CC-establishment present" state. The MM connection establishment may be unsuccessful for a variety of reasons, in which case the MM sublayer in the network will inform the CC entity in the network with an indication of the reason for the failure. The CC entity shall then stop all running timers, enter the "Null" state and inform all appropriate entities within the network. If timer T331 expires, the network shall abort the MM connection establishment attempt, stop all running CC timers, enter the "Null" state and inform all appropriate entities within the network. | 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.3.1 |
3,915 | 10.4.1 EN-DC | The Secondary Node Release procedure may be initiated either by the MN or by the SN and is used to initiate the release of the UE context at the SN. The recipient node of this request can reject it, e.g., if a SN change procedure is triggered by the SN. In case of CPA or inter-SN CPC, this procedure may be initiated either by the MN or the candidate SN, and it is used to cancel all the prepared PSCells at the candidate SN and initiate the release of related UE context at the candidate SN. It does not necessarily need to involve signalling towards the UE, e.g., in case of the RRC connection re-establishment due to Radio Link Failure in MN. MN initiated SN Release Figure 10.4.1-1: SN Release procedure – MN initiated Figure 10.4.1-1 shows an example signalling flow for the MN initiated Secondary Node Release procedure when SN Release is confirmed by SN. 1. The MN initiates the procedure by sending the SgNB Release Request message. If applicable, the MN provides data forwarding addresses to the SN. 2. The SN confirms SN Release by sending the SgNB Release Request Acknowledge message. If appropriate, the SN may reject SN Release, e.g. if the SN change procedure is triggered by the SN. NOTE 0: If CPA or inter-SN CPC is configured, upon reception of the SgNB Release Request Acknowledge message the MN cancels all CPAC with the target candidate SN(s). 3/4. If required, the MN indicates in the RRCConnectionReconfiguration message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. NOTE 1: If data forwarding is applied, timely coordination between steps 1 and 2 may minimize gaps in service provision, this is however regarded to be an implementation matter. 5. For bearers using RLC AM, the SN sends the SN Status Transfer message. 6. Data forwarding from the SN to the MN may start. 7. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 2: If data forwarding is applied, the order the SN sends the Secondary RAT Data Usage Report message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the Secondary RAT Data Usage Report message. 8. If applicable, the path update procedure is initiated. 9. Upon reception of the UE Context Release message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. SN initiated SN Release Figure 10.4.1-2: SN Release procedure – SN initiated Figure 10.4.1-2 shows an example signalling flow for the SN initiated Secondary Node Release procedure. 1. The SN initiates the procedure by sending the SgNB Release Required message which may contain inter-node message to support delta configuration. 2. If applicable, the MN provides data forwarding addresses to the SN in the SgNB Release Confirm message. The SN may start data forwarding and stop providing user data to the UE as early as it receives the SgNB Release Confirm message. NOTE 2a: If CPA or inter-SN CPC is configured, upon reception of the SgNB Release Required message the MN cancels all CPAC with the target candidate SN(s). 3/4. If required, the MN indicates in the RRCConnectionReconfiguration message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. NOTE 3: If data forwarding is applied, timely coordination between steps 2 and 3 may minimize gaps in service provision. This is however regarded to be an implementation matter. 5. For bearers using RLC AM, the SN sends the SN Status Transfer message. 6. Data forwarding from the SN to the MN may start. 7. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 4: If data forwarding is applied, the order the SN sends the Secondary RAT Data Usage Report message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the Secondary RAT Data Usage Report message. 8. If applicable, the path update procedure is initiated. 9. Upon reception of the UE Context Release message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. | 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.4.1 |
3,916 | – HighSpeedConfig | The IE HighSpeedConfig is used to configure parameters for high speed scenarios. HighSpeedConfig information element -- ASN1START -- TAG-HIGHSPEEDCONFIG-START HighSpeedConfig-r16 ::= SEQUENCE { highSpeedMeasFlag-r16 ENUMERATED {true} OPTIONAL, -- Cond SpCellOnly highSpeedDemodFlag-r16 ENUMERATED {true} OPTIONAL, -- Need R ... } HighSpeedConfig-v1700 ::= SEQUENCE { highSpeedMeasCA-Scell-r17 ENUMERATED {true} OPTIONAL, -- Cond SCellOnly highSpeedMeasInterFreq-r17 ENUMERATED {true} OPTIONAL, -- Cond SpCellOnly2 highSpeedDemodCA-Scell-r17 ENUMERATED {true} OPTIONAL, -- Need R ... } HighSpeedConfigFR2-r17 ::= SEQUENCE { highSpeedMeasFlagFR2-r17 ENUMERATED {set1, set2} OPTIONAL, -- Need R highSpeedDeploymentTypeFR2-r17 ENUMERATED {unidirectional, bidirectional} OPTIONAL, -- Need R highSpeedLargeOneStepUL-TimingFR2-r17 ENUMERATED {true} OPTIONAL, -- Need R ... } -- TAG-HIGHSPEEDCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,917 | 4.4.4.2 Integrity checking of NAS signalling messages in the UE | Except the messages listed below, no NAS signalling messages shall be processed by the receiving EMM entity in the UE or forwarded to the ESM entity, unless the network has established secure exchange of NAS messages for the NAS signalling connection: - EMM messages: - IDENTITY REQUEST (if requested identification parameter is IMSI); - AUTHENTICATION REQUEST; - AUTHENTICATION REJECT; - ATTACH REJECT (if the EMM cause is not #25 or #78); - DETACH ACCEPT (for non switch off); - TRACKING AREA UPDATE REJECT (if the EMM cause is not #25 or #78); - SERVICE REJECT (if the EMM cause is not #25 or #78). NOTE: These messages are accepted by the UE without integrity protection, as in certain situations they are sent by the network before security can be activated. All ESM messages are integrity protected. Once the secure exchange of NAS messages has been established, the receiving EMM or ESM entity in the UE shall not process any NAS signalling messages unless they have been successfully integrity checked by the NAS. If NAS signalling messages, having not successfully passed the integrity check, are received, then the NAS in the UE shall discard that message. The processing of the SECURITY MODE COMMAND message that has not successfully passed the integrity check is specified in clause 5.4.3.5. If any NAS signalling message is received as not integrity protected even though the secure exchange of NAS messages has been established by the network, then the NAS shall discard this message. | 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.4.4.2 |
3,918 | – MBS-NonServingInfoList | The IE MBS-NonServingInfoList is used to inform network of the frequencies, CFR information and subcarrier spacing for MBS broadcast reception on the non-serving cell. MBS-NonServingInfoList information element -- ASN1START -- TAG-MBS-NONSERVINGINFOLIST-START MBS-NonServingInfoList-r18 ::= SEQUENCE (SIZE (1..maxFreqMBS-r17)) OF NonServingInfo-r18 NonServingInfo-r18 ::= SEQUENCE { freqInfoMBS-r18 FreqInfoMBS-r18 OPTIONAL, cfr-InfoMBS-r18 CHOICE { cfr-Bandwidth-r18 INTEGER (1..maxNrofPhysicalResourceBlocks), cfr-LocationAndBW-r18 CFR-LocationAndBW-r18 } OPTIONAL, subcarrierSpacing-r18 SubcarrierSpacing OPTIONAL } FreqInfoMBS-r18 ::= SEQUENCE { carrierFreqMBS-r18 ARFCN-ValueNR, freqBandIndicatorMBS-r18 FreqBandIndicatorNR } CFR-LocationAndBW-r18 ::= SEQUENCE { locationAndBandwidthMBS-r18 INTEGER (0..37949) OPTIONAL, absoluteFrequencyPointA-MBS-r18 ARFCN-ValueNR OPTIONAL, offsetToCarrierMBS-r18 INTEGER (0..2199) OPTIONAL } -- TAG-MBS-NONSERVINGINFOLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,919 | 13.2.2 N32-c connection between SEPPs 13.2.2.1 General | When the negotiated security mechanism to use over N32, according to the procedure in clause 13.5, is PRINS (described in clause 13.2), the SEPPs use the established TLS connection (henceforth referred to as N32-c connection) to negotiate the N32-f specific associated security configuration parameters required to enforce application layer security on HTTP messages exchanged between the SEPPs. A second N32-c connection is established by the receiving SEPP to enable it to not only receive but also send HTTP Requests. The N32-c connection is used for the following purposes: - Key agreement: The SEPPs independently export keying material associated with the first N32-c connection between them and use it as the pre-shared key for generating the shared session key required. - Parameter exchange: The SEPPs exchange security related configuration parameters that they need to protect HTTP messages exchanged between the two Network Functions (NF) in their respective networks. - Error handling: The receiving SEPP sends an error signalling message to the peer SEPP when it detects an error on the N32-f interface. The following security related configuration parameters may be exchanged between the two SEPPs: a. Modification policy. A modification policy, as specified in clause 13.2.3.4, indicates which IEs can be modified by an IPX provider of the sending SEPP. b. Data-type encryption policy. A data-type encryption policy, as specified in 13.2.3.2, indicates which types of data will be encrypted by the sending SEPP. c. Cipher suites for confidentiality and integrity protection, when application layer security is used to protect HTTP messages between them. d. N32-f context ID. As specified in clause 13.2.2.4.1, N32-f context ID identifies the set of security related configuration parameters applicable to a protected message received from a SEPP in a different PLMN. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.2 |
3,920 | – TDD-UL-DL-ConfigCommon | The IE TDD-UL-DL-ConfigCommon determines the cell specific Uplink/Downlink TDD configuration. TDD-UL-DL-ConfigCommon information element -- ASN1START -- TAG-TDD-UL-DL-CONFIGCOMMON-START TDD-UL-DL-ConfigCommon ::= SEQUENCE { referenceSubcarrierSpacing SubcarrierSpacing, pattern1 TDD-UL-DL-Pattern, pattern2 TDD-UL-DL-Pattern OPTIONAL, -- Need R ... } TDD-UL-DL-Pattern ::= SEQUENCE { dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10}, nrofDownlinkSlots INTEGER (0..maxNrofSlots), nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1), nrofUplinkSlots INTEGER (0..maxNrofSlots), nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1), ..., [[ dl-UL-TransmissionPeriodicity-v1530 ENUMERATED {ms3, ms4} OPTIONAL -- Need R ]] } -- TAG-TDD-UL-DL-CONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,921 | 4.1.2.3 Failed RRC connection re-establishments | a) This measurement provides the number of RRC re-establishment failures for each re-establishment cause. b) CC. c) Transmission of an RRCConnectionReestablishmentReject message by the eNodeB/RN to the UE or an expected RRCConnectionReestablishmentComplete message not received by the eNodeB/RN. Each failed RRC connection re-establishment is added to the relevant per re-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 re-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.ConnReEstabFail.Cause where Cause identifies the re-establishment.cause. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. 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.1.2.3 |
3,922 | 10.2 ASN.1 violation or encoding error | The UE shall: 1> when receiving an RRC message on the BCCH, CCCH, PCCH, MCCH or a PC5 RRC message on SBCCH for which the abstract syntax is invalid [6]: 2> ignore the message. NOTE: This clause applies in case one or more fields is set to a value, other than a spare, reserved or extended value, not defined in this version of the transfer syntax. E.g. in the case the UE receives value 12 for a field defined as INTEGER (1..11). In cases like this, it may not be possible to reliably detect which field is in the error hence the error handling is at the message level. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.2 |
3,923 | 4.8.2.2b Network Triggered Connection Resume in RRC_INACTIVE with CN based MT communication handling | When the UE is in CM-CONNECTED with RRC_INACTIVE state with CN based mobile terminating (MT) communication handling, high latency communication as described in clause 5.31.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] is applied. This procedure may be triggered by MT data, or a N1 procedure from SMF and UPF as shown in Figure 4.8.2.2b-1. When the procedure is triggered by other NFs (e.g. SMSF, LMF, GMLC), the UPF (or SMF) in the following figure should be replaced by the respective NF (the corresponding service operations used by other NFs when they communicate with AMF may also be different from the service operations used by SMF/UPF). For MT-SMS delivery request from SMSF, see also procedures defined in clause 4.13.3.6, clause 4.13.3.7 and clause 4.13.3.8. During the procedure, the NG-RAN (i.e. gNB) performs RAN paging towards the UE based on the N2 message from the AMF in order to trigger the UE triggered Connection Resume procedure in clause 4.8.2.2. Figure 4.8.2.2b-1: Network Triggered Connection Resume for UE in RRC_INACTIVE with CN based MT communication handling 1a. When downlink data is received and the SMF/UPF is requested to perform buffering as specified in clause 4.8.1.1a, the UPF/SMF checks with AMF for the possibility of data delivery, similar to step 2 of clause 4.24.2 with the following differences: - The UPF provides the DL data size information of the QoS Flow when sending Data Notification to SMF if the UPF has received instruction from SMF. - In the Namf_MT_EnableUEReachability the SMF may also send the following parameters the PPI, the ARP and the 5QI, DL data size and/or QFI for the QoS Flow of the PDU Session which triggered the request for paging policy differentiation as defined in clause 5.4.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF, while waiting for UE triggered Connection Resume indication or a reject response (with Estimated Maximum Wait time) from the AMF, receives any additional Data Notification message due to additional data packets for another QoS Flow associated with a higher priority (i.e. ARP priority level) than the priority indicated to the AMF in the previous Namf_MT_EnableUEReachability, or the SMF derive a different Paging Policy Indicator according to the additional Data Notification, the SMF invokes a new Namf_MT_EnableUEReachability indicating the higher priority or different Paging Policy Indicator to the AMF. The information contained in the new Namf_MT_EnableUEReachability request overrides the information from the previous Namf_MT_EnableUEReachability request that is stored in the AMF. If the SMF receives any additional Data Notification messages due to additional data packets for another QoS Flow associated with same or lower priority than the priority indicated to the AMF in the previous Namf_MT_EnableUEReachability or if the SMF has sent the second Namf_MT_EnableUEReachability message indicating the higher priority and receives additional downlink data packets for this UE, based on local configuration, the SMF either buffers these Data Notification messages and does not send a new Namf_MT_EnableUEReachability message, or the SMF sends a new Namf_MT_EnableUEReachability message to AMF. - The AMF determines if the UE is reachable based on the stored eDRX values for RRC_INACTIVE state provided by NG-RAN in clause 4.8.1.1a. If the UE is unreachable, the AMF stores the information received in the Namf_MT_EnableUEReachability request and provides the Estimated Maximum Wait time in the response message based on the eDRX values for RRC_INACTIVE in AMF (steps 2-5 are postponed until the UE becomes reachable). If the UE is considered reachable, step 2 is executed immediately. NOTE 1: This handling is similar to CM-IDLE with eDRX. When the AMF provides the Estimated Maximum Wait time, it can consider the time needed for RRC level procedures (e.g. RRC RNA update procedure) when UE wakes up from the eDRX cycle. NOTE 2: The other NFs can use the Namf_Communication_N1N2MessageTransfer service operation to deliver the MT signalling. 2. When the AMF determines that the UE is reachable, the AMF sends a RAN Paging Request message to NG-RAN with the request for the UE's RRC connection to be resumed. The AMF may include the following per QoS Flow parameter(s) the PPI, the ARP and the 5QI, DL data size and/or QFI for the QoS Flow(s) of the PDU Session in the RAN Paging Request message to trigger and enable RAN paging. If the AMF receives MT signalling (i.e. via Namf_Communication_N1N2MessageTransfer) in step 1a, AMF includes DL Signalling indication in the N2 RAN Paging Request message. 3. NG-RAN performs RAN paging towards the UE considering the parameters provided by the AMF. Based on the DL data size for QoS Flow(s), if it's provided, the NG-RAN determines whether to set the MT-SDT flag as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]). 4. When the UE receives RAN paging, it initiates the UE triggered Connection Resume procedure and NG-RAN notifies CN as specified in clause 4.8.2.2 including the N2 Notification in step 3b. 5. The UPF triggers downlink data delivery if there is any. The AMF sends downlink NAS messages if there is any. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.8.2.2b |
3,924 | 2.6 Structure of TLLI | A TLLI is built by the MS or by the SGSN either on the basis of the P-TMSI (local or foreign TLLI), or directly (random or auxiliary TLLI), according to the following rules. The TLLI consists of 32 bits, numbered from 0 to 31 by order of significance, with bit 0 being the LSB. A local TLLI is built by an MS which has a valid P-TMSI as follows: bits 31 down to 30 are set to 1; and bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI. A foreign TLLI is built by an MS which has a valid P-TMSI as follows: bit 31 is set to 1 and bit 30 is set to 0; and bits 29 down to 0 are set equal to bits 29 to 0 of the P-TMSI. A random TLLI is built by an MS as follows: bit 31 is set to 0; bits 30 down to 27 are set to 1; and bits 0 to 26 are chosen randomly. An auxiliary TLLI is built by the SGSN as follows: bit 31 is set to 0; bits 30 down to 28 are set to 1; bit 27 is set to 0; and bits 0 to 26 can be assigned independently. Other types of TLLI may be introduced in the future. Part of the TLLI codespace is re-used in GERAN to allow for the inclusion of the GERAN Radio Network Temporary Identifier in RLC/MAC messages. The G-RNTI is defined in 3GPP TS 44.118[ None ] [29]. The structure of the TLLI is summarised in table 1. Table 1: TLLI structure 'T', 'R', 'A' and 'X' indicate bits which can take any value for the type of TLLI. More precisely, 'T' indicates bits derived from a P-TMSI, 'R' indicates bits chosen randomly, 'A' indicates bits chosen by the SGSN, 'G' indicates bits derived from the assigned G-RNTI and 'X' indicates bits in reserved ranges. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.6 |
3,925 | 6.42.2 Requirements | The 5G system shall support efficient operation of mobile base station relays. The 5G system shall be able to support means, for a mobile network operator, to configure, provision and control the operation of a mobile base station relay, e.g. activation/deactivation, permitted location(s) or time of operation. The 5G system shall be able to support provisioning and configuration mechanisms to control UEs’ selection and access to a mobile base station relay, e.g. based on UE’s authorization, geographic or temporary restrictions, relay’s load. The 5G system shall be able to support RAN sharing between multiple PLMNs for UEs connected to the 5G network via mobile base station relays. NOTE 1: the above requirement assumes both relay and (donor) RAN resources, including UE access link and relay backhaul link, are shared among operators. The 5G system shall be able to configure and provision specific required QoS for traffic relayed via a mobile base station relay. NOTE 2: QoS is end-to-end, i.e. from UE to 5GC. Subject to regulatory requirements and based on operator policy, the 5G system shall support means to configure and expose monitoring information of a mobile base station relay to an MNO’s authorized third-party. The 5G system shall be able to provide means to optimize network behaviour to efficiently deliver data based on the mobility information (e.g., itinerary), known or predicted, of mobile base station relays. The 5G system shall be able to support communication from/to users of one MNO (MNO-A) via mobile base station relays, where the traffic between the relay and the MNO-A network is transported using 5G connectivity (RAN and 5GC) provided by a different MNO (MNO-B). NOTE 3: The 5G connectivity provided to the MNO-A relays by the different MNO (MNO-B) assumes a generic wireless backhaul transport, independent from the mobile base station relay functionalities. The 5G system shall be able to support UEs connectivity to RAN using simultaneously, a link without mobile base station relay and a link via a mobile base station relay, or simultaneous links via different mobile base station relays. NOTE 4: The above requirements cover scenarios were the two links (to the RAN) could be connected to the same or different RAN node(s), and assuming both relay(s) and RAN belong to the same PLMN. The 5G system shall be able to provide means to support efficient UE cell selection and cell reselection (between mobile base station relays or between relays and RAN) in the presence of mobile base station relays. The 5G system shall be able to ensure end-to-end service continuity, in the presence of mobile base station relays. NOTE 5: The above requirement intends to cover different scenarios of UE mobility (e.g. UE moving between two mobile base station relays, or between macro RAN and relay) and relay mobility (e.g. base station relay moving between different donor RAN nodes). The 5G system shall be able to support mechanisms to optimize mobility and energy efficiency for UEs located in a vehicle equipped with a base station relay. NOTE 6: The above requirements cover scenarios where mobile base station relays provide 5G access for both UEs in the vehicle and around the vehicle. The 5G system shall be able to support incremental deployment of connectivity by means of one or a series of mobile base station relays for use only in specific locations where UEs would receive no other 3GPP access (terrestrial or non-terrestrial) coverage, e.g., for public safety scenarios. The 5G system shall be able to support mobile base station relays using 3GPP satellite NG-RAN (NR satellite access). The 5G system shall be able to support mobile base station relays accessing to 5GC via NR satellite access and NR terrestrial access simultaneously. The 5G system shall be able to support service continuity for mobile base station relays using at least one 3GPP satellite NG-RAN. NOTE 7: This requirement applies to scenarios where there is a transition between two 3GPP NG-RAN, operated by the same MNO, involving at least one 3GPP satellite NG-RAN. The 5G system shall be able to identify and differentiate UEs’ traffic carried via a mobile base station relay and collect charging information, including specific relay information (e.g. geographic location served by the relay). The 5G system shall support means for a mobile base station relay to have a certain subscription with a HPLMN, used to get access and connectivity to the HPLMN network (via a donor RAN). The 5G system shall support the ability of a base station relay to roam from its HPLMN into a VPLMN. The 5G system shall support mechanisms, for the HPLMN controlling a mobile base station relay, to enable/disable mobile relay operation if the relay is roaming in a VPLMN. The 5G system shall support mechanisms to disable mobile relay operation by a VPLMN where a mobile base station relay is roaming to. The 5G system shall be able to fulfil necessary regulatory requirements (e.g. for support of emergency services) when UEs access the 3GPP network via a mobile base station relay. The 5G system shall be able to support priority services (e.g. MPS) when UEs access the 3GPP network via a mobile base station relay. The 5G system shall be able to support location services for the UEs accessing 5GS via a mobile base station relay. The 5G system shall ensure that existing end-to-end 5G security between the UE and 3GPP network is unaffected when the UE accesses the 3GPP network via a mobile base station relay. The 5G system shall be able to minimize radio interference possibly caused by mobile base station relays. The 5G system shall minimize the impact of the presence of mobile base station relays on radio network management (e.g. through automatic neighbour cell list configuration). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.42.2 |
3,926 | 8.1 Overview | This clause defines the structure of the messages of the Layer 3 (L3) protocols defined in the present document. These are standard L3 messages as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. Each definition given in the present clause includes: a) a brief description of the message direction and use, including whether the message has: 1. Local significance, i.e. relevant only on the originating or terminating access; 2. Access significance, i.e. relevant in the originating and terminating access, but not in the network; 3. Dual significance, i.e. relevant in either the originating or terminating access and in the network; or 4. Global significance, i.e. relevant in the originating and terminating access and in the network. b) a table listing the Information Elements (IE) known in the message and the order of their appearance in the message. All IEs that may be repeated are explicitly indicated (The V, LV and LV-E formatted IEs, which compose the imperative part of the message, occur before the T, TV, TLV and TLV-E formatted IEs which compose the non-imperative part of the message, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]). In a (maximal) sequence of consecutive IEs with half octet length, the first IE with half octet length occupies bits 1 to 4 of octet N, the second IE bits 5 to 8 of octet N, the third IE bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements. For each information element the table indicates: 1. The Information Element Identifier (IEI), in hexadecimal notation, if the IE has format T, TV, TLV or TLV-E. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-). NOTE 1: The same IEI can be used for different information element types in different messages of the same protocol. NOTE 2: If a message includes a Type 6 IE container information element, then the same IEI can be used for different information element types in the Type 6 IE container information element and in other parts of the same message. 2. The name of the information element (which may give an idea of the semantics of the element). The name of the information element followed by "IE" or "information element" is used in this technical report as reference to the information element within a message. 3. The name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced subclause of clause 9 of the present document describing the value part of the information element. 4. The presence requirement indication (M, C, or O) for the IE as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. 5. The format of the information element (T, V, TV, LV, TLV, LV-E or TLV-E) as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. 6. The length of the information element (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by link layer protocol. This indication is non-normative. c) subclauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant message which together with other conditions specified in the present document define when the information elements shall be included or not, what non-presence of such IEs means, and – for IEs with presence requirement C – the static conditions for presence or non-presence of the IEs or for both cases (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]). | 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 | 8.1 |
3,927 | 4.1.2.1.2 Substates of the MM IDLE state | For the description of the behaviour of the MS the MM IDLE state is subdivided in several substates, also called the service states. The service state pertains to the whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM). The service state depends on the update status (see subclause 4.1.2.2) and on the selected cell. 19.1 NORMAL SERVICE Valid subscriber data are available, update status is U1, a cell is selected that belongs to the LA where the subscriber is registered. In this state, all requests from the CM layers are treated normally. 19.2 ATTEMPTING TO UPDATE Valid subscriber data are available, update status is U2 and a cell is selected. Requests from upper layers are accepted. Emergency call requests are treated normally, otherwise the request triggers first a location updating attempt in the selected cell, and then triggers the needed procedure only in case of successful location updating, otherwise the request is rejected. 19.3 LIMITED SERVICE Valid subscriber data are available, update status is U3, and a cell is selected, which is known not to be able to provide normal service. Only emergency services are offered. 19.4 NO IMSI No valid subscriber data (no SIM/USIM, or the SIM/USIM is not considered valid by the ME), and a cell is selected. Only emergency services are offered. 19.5 NO CELL AVAILABLE No cell can be selected. This state is entered after a first intensive search failed (state 19.7). Cells are searched at a low rhythm. This state is also entered when S1 mode is activated in the MS and current cell is an E-UTRAN cell. No services, except those provided by CS fallback and SMS over SGs, are offered. 19.6 LOCATION UPDATE NEEDED Valid subscriber data are available, and for some reason a location updating must be done as soon as possible (for instance update status is U1 but the selected cell is not in the registered LA, or the timer has expired). This state is usually of no duration, but can last, e.g. due to access class control, (see subclause 4.1.1.2.1). 19.7 PLMN SEARCH The mobile station is searching for PLMNs, and the conditions for state 19.8 are not met. This state is ended when either a cell is selected (the new state is 19.1, 19.3 or 19.6), or when it is concluded that no cell is available for the moment (the new state is 19.5). 19.8 PLMN SEARCH, NORMAL SERVICE Valid subscriber data are available, update status is U1, a cell is selected which belongs to the LA where the subscriber is registered, and the mobile station is searching for PLMNs. This state is ended when either a cell is selected (the new state is 19.1, 19.3 or 19.6), or when it is concluded that no cell is available for the moment (the new state is 19.5). 19.9 RECEIVING GROUP CALL (NORMAL SERVICE) Only applicable for mobile stations supporting VGCS listening or VBS listening. Valid subscriber data are available, update status is U1, a VGCS channel or VBS channel is received in a cell that belongs to the LA where the subscriber is registered. In this state, only requests from the GCC or BCC layers are treated. 19.10 RECEIVING GROUP CALL (LIMITED SERVICE) Only applicable for mobile stations supporting VGCS listening or VBS listening. Valid subscriber data are available, update status is U3, a VGCS channel or VBS channel is received in a cell which is known not to be able to provide normal service. In this state, only requests from the GCC or BCC layers for the reception of VGCS or VBS calls are treated and group call emergency services are offered. 19.11 eCALL INACTIVE Valid subscriber data are available, update status is U4, and a cell is selected, which is expected to be able to provide normal service. Only emergency services and test/reconfiguration calls (see 3GPP TS 22.101[ Service aspects; Service principles ] [8]) can be initiated by the mobile station. This state is applicable only to an eCall only mobile station (as determined by information configured in USIM). The state is entered by the mobile station in order to avoid MM activity and MM signalling in the absence of an emergency call or test/reconfiguration call. The state is ended when an emergency services or test/reconfiguration calls[8] is initiated by the mobile station, the new state depends on the result of the procedure when returning to MM-IDLE described in subclause 4.2.3. | 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.2.1.2 |
3,928 | 6.2.23 NSSAAF | The Network Slice-specific and SNPN Authentication and Authorization Function (NSSAAF) supports the following functionality: - Support for Network Slice-Specific Authentication and Authorization as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3] with a AAA Server (AAA-S). If the AAA-S belongs to a third party, the NSSAAF may contact the AAA-S via a AAA proxy (AAA-P). - Support for access to SNPN using credentials from Credentials Holder using AAA server (AAA-S) as specified in clause 5.30.2.9.2 or using credentials from Default Credentials Server using AAA server (AAA-S) as specified in clause 5.30.2.10.2. If the Credentials Holder or Default Credentials Server belongs to a third party, the NSSAAF may contact the AAA server via a AAA proxy (AAA-P). NOTE: When the NSSAAF is deployed in a PLMN, the NSSAAF supports Network Slice-Specific Authentication and Authorization, while when the NSSAAF is deployed in a SNPN the NSSAAF can support Network Slice-Specific Authentication and Authorization and/or the NSSAAF can support access to SNPN using credentials from Credentials Holder. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.23 |
3,929 | 9.3.4.1.2 TDD | For the parameters specified in Table 9.3.4.1.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.4.1.2-2 and by the following a) the ratio of the throughput obtained when transmitting on a randomly selected subband among the best M subbands reported by the UE the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected subband in set S shall be ≥ ; The requirements only apply for subbands of full size and the random scheduling across the subbands is done by selecting a new subband in each available downlink transmission instance for TDD. The transport block size TBS (wideband CQI median) is that resulting from the code rate which is closest to that indicated by the wideband CQI median and theentry in Table 7.1.7.2.1-1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] that corresponds to the subband size. Table 9.3.4.1.2-1 Sub-band test for single antenna transmission (TDD) Table 9.3.4.1.2-2 Minimum requirement (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 | 9.3.4.1.2 |
3,930 | 5.30.3.4 Network and cell (re-)selection, and access control | The following is assumed for network and cell selection, and access control: - The CAG cell shall broadcast information such that only UEs supporting CAG are accessing the cell (see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]); NOTE 1: The above also implies that cells are either CAG cells or normal PLMN cells. For network sharing scenario between SNPN, PNI-NPN and PLMNs, please see clause 5.18. - In order to prevent access to NPNs for authorized UE(s) in the case of network congestion/overload, existing mechanisms defined for Control Plane load control, congestion and overload control in clause 5.19 can be used, as well as the access control and barring functionality described in clause 5.2.5, or Unified Access Control using the access categories as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] can be used. - For aspects of automatic and manual network selection in relation to CAG, see TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]; - For aspects related to cell (re-)selection, see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]; - If the UE is accessing a CAG cell and the corresponding entry of the Allowed CAG list configured on the UE is associated with validity information, the UE may trigger cell reselection and/or network selection procedure if the evaluation of the validity condition changes. - The Mobility Restrictions shall be able to restrict the UE's mobility according to the Allowed CAG list (if configured in the subscription) and include an indication whether the UE is only allowed to access 5GS via CAG cells (if configured in the subscription) as described in clause 5.30.3.3; - The AMF shall update the Allowed CAG list in the Mobility Restrictions towards NG-RAN if the evaluation of the validity condition of an entry in the Allowed CAG list changes between true and false, unless the AMF releases the NAS signalling connection to the UE based on operator's policy if the evaluation of the validity condition changes from true to false. - During transition from CM-IDLE to CM-CONNECTED and during Registration after connected mode mobility from E-UTRAN to NG-RAN as described in clause 4.11.1.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]: - The AMF shall verify whether UE access is allowed by Mobility Restrictions: NOTE 2: It is assumed that the AMF is made aware of the supported CAG Identifier(s) of the CAG cell by the NG-RAN. - If the UE is accessing the 5GS via a CAG cell and if at least one of the CAG Identifier(s) received from the NG-RAN is part of the UE's Allowed CAG list (for entries with validity information if any, the evaluation of the condition is true), then the AMF accepts the NAS request; - If the UE is accessing the 5GS via a CAG cell and if none of the CAG Identifier(s) received from the NG-RAN are part of the UE's Allowed CAG list (for entries with validity information if any, the evaluation of the condition is true), then the AMF rejects the NAS request and the AMF should include CAG information in the NAS reject message. The AMF shall then release the NAS signalling connection for the UE by triggering the AN release procedure; and - If the UE is accessing the 5GS via a non-CAG cell and the UE's subscription contains an indication that the UE is only allowed to access CAG cells, then the AMF rejects the NAS request and the AMF should include CAG information in the NAS reject message. The AMF shall then release the NAS signalling connection for the UE by triggering the AN release procedure. - During transition from RRC_INACTIVE to RRC_CONNECTED state: - When the UE initiates the RRC Resume procedure for RRC_INACTIVE to RRC_CONNECTED state transition in a CAG cell, NG-RAN shall reject the RRC Resume request from the UE if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list according to the Mobility Restrictions received from the AMF or if no Allowed CAG list has been received from the AMF. - When the UE initiates the RRC Resume procedure for RRC_INACTIVE to RRC_CONNECTED state transition in a non-CAG cell, NG-RAN shall reject the UE's Resume request if the UE is only allowed to access CAG cells according to the Mobility Restrictions received from the AMF. - During connected mode mobility procedures within NG-RAN, i.e. handover procedures as described in clause 4.9.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]: - Source NG-RAN shall not handover the UE to a target NG-RAN node if the target is a CAG cell and none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list in the Mobility Restriction List or if no Allowed CAG list has been received from the AMF; - Source NG-RAN shall not handover the UE to a non-CAG cell if the UE is only allowed to access CAG cells based on the Mobility Restriction List; - If the target cell is a CAG cell, target NG-RAN shall reject the N2 based handover procedure if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list in the Mobility Restriction List or if no Allowed CAG list has been received from the AMF; - If the target cell is a non-CAG cell, target NG-RAN shall reject the N2 based handover procedure if the UE is only allowed to access CAG cells based on the Mobility Restriction List. - Update of Mobility Restrictions: - When the AMF receives the Nudm_SDM_Notification from the UDM and the AMF determines that the Allowed CAG list or the indication whether the UE is only allowed to access CAG cells have changed; - The AMF shall update the Mobility Restrictions in the UE and NG-RAN accordingly under the conditions as described in clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 3: When the UE is accessing the network for emergency services the conditions for AMF in clause 5.16.4.3 apply. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.3.4 |
3,931 | 5.4.12.2 Core Network Assistance for PEIPS | To support the Paging Early Indication with Paging Subgrouping (PEIPS), Paging Subgrouping Support Indication and the PEIPS Assistance Information is used by the AMF and NG-RAN to help determine whether PEIPS applies to the UE and which paging subgroup used when paging the UE (see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). In the Registration Request message, the Paging Subgrouping Support Indication indicates whether the UE supports PEIPS with AMF PEIPS Assistance Information. If the UE includes Paging Subgrouping Support Indication, the UE may also include the paging probability information to assist the AMF. If the AMF supports PEIPS assistance and if the UE provided Paging Subgrouping Support Indication, the AMF stores the indication in the UE context in AMF. The AMF may use local configuration, the UE's paging probability information if provided, information provided by the RAN (e.g. any of the Information On Recommended Cells And RAN nodes For Paging), and/or previous statistical information for the UE to determine the AMF PEIPS Assistance Information. The AMF PEIPS Assistance Information includes the Paging Subgroup ID. NOTE 1: To minimise MT voice call setup latency, the AMF could allocate Paging Subgroup IDs taking into account whether or not the UE is likely to receive IMS voice over PS session calls. NOTE 2: To avoid MT traffic for more mobile UEs causing more stationary UEs to be woken up, the AMF could allocate Paging Subgroup IDs taking into account the UE's mobility pattern. If the AMF has determined AMF PEIPS Assistance Information for the UE, the AMF stores it in the UE context in AMF and provides it to the UE in every Registration Accept message. If the AMF has determined AMF PEIPS Assistance Information, the AMF shall provide it to NG RAN when paging the UE. In addition, in order to support PEIPS for UEs in RRC_INACTIVE mode, the AMF shall provide the AMF PEIPS Assistance Information to NG-RAN as part of the RRC Inactive Assistance Information. The NG-RAN chooses on a per-cell basis whether to use PEIPS and which paging subgrouping mechanism to use. When using AMF allocated subgroups, both the UE and NG-RAN use the AMF PEIPS Assistance Information to determine the paging subgroup to apply as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. The AMF may use the UE Configuration Update procedure (as described in clause 4.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) and N2 UE Context Modification procedure (as described in clause 8.3.4 of TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]) to update the AMF PEIPS Assistance Information in the UE and NG-RAN. When the UE has an active emergency PDU Session: - The UE shall not signal Paging Subgrouping Support Indication in the Registration Request message. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.12.2 |
3,932 | 8.3.14.3 Protocol configuration options | This IE shall be included in the message when, during the attach procedure, the UE wishes to transmit security protected (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and: a) the UE is in WB-S1 mode; b) the requested PDN Type is different from non-IP and Ethernet; and c) the requested APN is not for UAS services. This IE shall be included if: a) the UE supports local IP address in traffic flow aggregate description and TFT filter; b) the UE is in WB-S1 mode; c) the requested PDN Type is different from non-IP and Ethernet; and d) the requested APN is not for UAS services. This IE shall not be included if the Extended protocol configuration options IE is included in the message. | 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 | 8.3.14.3 |
3,933 | – CSI-SemiPersistentOnPUSCH-TriggerStateList | The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure the UE with list of trigger states for semi-persistent reporting of channel state information on L1. See also TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.2. CSI-SemiPersistentOnPUSCH-TriggerStateList information element -- ASN1START -- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-START CSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE(SIZE (1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerState CSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE { associatedReportConfigInfo CSI-ReportConfigId, ..., [[ sp-CSI-MultiplexingMode-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ csi-ReportSubConfigTriggerList-r18 CSI-ReportSubConfigTriggerList-r18 OPTIONAL, -- Need R ltm-AssociatedReportConfigInfo-r18 LTM-CSI-ReportConfigId-r18 OPTIONAL -- Need R ]] } -- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,934 | 6.6.2B Out of band emission for UL-MIMO | For UE supporting UL-MIMO, the requirements for Out of band emissions resulting from the modulation process and non-linearity in the transmitters are specified at each transmit antenna connector. For UEs with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the requirements in subclause 6.6.2 apply to each transmit antenna connector. The requirements shall be met with the UL-MIMO configurations specified in Table 6.2.2B-2. If UE is configured for transmission on single-antenna port, the requirements in subclause 6.6.3 apply. | 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 | 6.6.2B |
3,935 | 8.9.3.2 gNB-CU-UP initiated bearer context release | Figure 8.9.3.2-1 shows the procedure used to release the bearer context in the gNB-CU-UP initiated by the gNB-CU-UP. Figure 8.9.3.2-1: Bearer context release over F1-U – gNB-CU-UP initiated 0. Bearer context release is triggered in gNB-CU-UP e.g., due to local failure. 1. The gNB-CU-UP sends a BEARER CONTEXT RELEASE REQUEST message to request the release of the bearer context in the gNB-CU-UP. This message may contain the PDCP status. 2.- 5. If the PDCP status needs to be preserved, the E1 Bearer Context Modification and the F1 UE Context Modification procedures are performed. The E1 Bearer Context Modification procedure is used to convey data forwarding information to the gNB-CU-UP. The gNB-CU-CP may receive the UE Context Release from the MeNB. 6. The gNB-CU-CP sends a BEARER CONTEXT RELEASE COMMAND message to release the bearer context in the gNB-CU-UP. 7. The gNB-CU-UP responds with a BEARER CONTEXT RELEASE COMPLETE to confirm the release of the bearer context including also data forwarding information. 8. F1 UE context release procedure may be performed to release the UE context in the gNB-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.3.2 |
3,936 | 5.6.11 UE presence in Area of Interest reporting usage by SMF | When a PDU Session is established or modified, or when the user plane path has been changed (e.g. UPF re-allocation/addition/removal), SMF may determine an Area of Interest, e.g. based on UPF Service Area, subscription by PCF for reporting UE presence in Presence Reporting Area, etc. For 3GPP access, the Area of Interest corresponds: - either to Presence Information that may correspond to: - a list of Tracking Areas; or - a list of Presence Reporting Area ID(s) and optionally the elements comprising TAs and/or NG-RAN nodes and/or cells identifiers corresponding to the PRA ID(s); or - a LADN DNN; or - a LADN DNN and a S-NSSAI; or - a S-NSSAI. For Non-3GPP access, the Area of Interest corresponds to: - N3GPP TAI (see clause 5.3.2.3). For UE location change into or out of an "area of interest", the SMF subscribes to "UE mobility event notification" service provided by AMF for reporting of UE presence in Area of Interest as described in clause 5.3.4.4. The AMF may send the UE location to the SMF along with the notification, e.g. for UPF selection. Upon reception of a notification from AMF, the SMF determines how to deal with the PDU Session, e.g. reallocate UPF. In the case of LADN, the SMF provides the LADN DNN to the AMF to subscribe to "UE mobility event notification" for reporting UE presence in LADN service area. Upon reception of a notification from the AMF, the SMF determines how to deal with the PDU Session as described in clause 5.6.5. In the case of Partial Network Slice Support and Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas as described in clauses 5.15.17 and 5.15.18, the SMF provides the S-NSSAI to the AMF to "UE mobility event notification" for reporting UE presence in slice restriction area. Upon reception of a notification from the AMF, the SMF determines how to deal with the PDU Session as described in clauses 5.15.17 and 5.15.18. For use cases related to policy control and charging decisions, the PCF may subscribe to event reporting from the SMF or the AMF, for UE presence in a Presence Reporting Area. A Presence Reporting Area can be: - A "UE-dedicated Presence Reporting Area", defined in the subscriber profile and composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN; or derived from the Area of Interest provided by the Application Function to the PCF (see clause 5.6.7) and composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN; or - A "Core Network predefined Presence Reporting Area", predefined in the AMF and composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN. In the case of Change of UE Presence in Presence Reporting Area, for core network predefined Presence Reporting Area, the AMF determines the "area of interest" corresponding to the Presence Reporting Area Identifier(s), provided by the PCF or the SMF, as a list of TAIs and/or cell identifiers and/or NG-RAN node identifiers based on local configuration. For UE-dedicated Presence Reporting Areas, the subscription for UE location change notification for an "area of interest" shall contain the PRA Identifier(s) and the list(s) of TAs, or NG-RAN Node identifier and/or cell identifiers composing the Presence Reporting Area(s). For Core Network predefined Presence Reporting Areas, the subscription for UE location change notification for an "area of interest" shall contain the PRA identifier(s). NOTE 1: If the Presence Reporting Area (PRA) and RAN Notification Area (RNA) are partially overlapping, the PCF will not get notified for the change of PRA when UE enters or leaves the PRA but remains in the RNA in CM-CONNECTED with RRC_INACTIVE state, because AMF is not informed. Each Core Network predefined Presence Reporting Area can be configured with a priority level in the AMF. In order to prevent overload, the AMF may set the reporting for one or more of the received Presence Reporting Area(s) to inactive under consideration of the priority configured for each of Core Network predefined Presence Reporting Area(s), while storing the reporting request for this Presence Reporting Area in the UE context. NOTE 2: Change of UE presence in Presence Reporting Area reporting does not apply to home routed roaming. The AMF may be configured with a PRA identifier which refers to a Set of Core Network predefined Presence Reporting Areas. If the PCF subscribes to change of UE location for an area of interest for a Set of Presence reporting areas and provides a PRA identifier then the SMF may subscribe for event reporting for this Set of Presence Reporting Areas by only indicating this PRA Identifier in the area of interest. When the Presence Reporting Area(s) to be reported belong to a set of Core Network predefined Presence Reporting Areas in which the AMF is requested to report on change of UE presence, the AMF shall additionally add to the report the PRA Identifier of the Set of Core Network predefined Presence Reporting Areas. Upon change of AMF, the PRA identifier(s) and if provided, the list(s) of Presence Reporting Area elements are transferred for all PDU sessions as part of MM Context information to the target AMF during the mobility procedure. If one or more Presence Reporting Area(s) was set to inactive, the target AMF may decide to reactivate one or more of the inactive Presence Reporting Area(s). The target AMF indicates per PDU session to the corresponding SMF/PCF the PRA identifier(s) and whether the UE is inside or outside the Presence Reporting Area(s) as well as the inactive Presence Reporting Area(s), if any. NOTE 3: The target AMF cannot set the Presence Reporting Area(s) received from the source serving node to inactive. The subscription may be maintained during the life of PDU Session, regardless of the UP activation state of PDU Session (i.e. whether UP connection of the PDU Session is activated or not). SMF may determine a new area of interest, and send a new subscription to the AMF with the new area of interest. SMF un-subscribes to "UE mobility event notification" service when PDU Session is released. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.11 |
3,937 | 7.3.3 SI Modification | Change of system information (other than for ETWS/CMAS, see clause 16.4) only occurs at specific radio frames, i.e. the concept of a modification period is used. System information may be transmitted a number of times with the same content within a modification period, as defined by its scheduling. The modification period is configured by system information. When the network changes (some of the) system information, it first notifies the UEs about this change, i.e. this may be done throughout a modification period. In the next modification period, the network transmits the updated system information. Upon receiving a change notification, the UE acquires the new system information from the start of the next modification period. The UE applies the previously acquired system information until the UE acquires the new system information. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.3.3 |
3,938 | 9.2.4 CM Re-establishment request | This message is sent by the mobile station to the network to request re-establishment of a connection if the previous one has failed. See table 9.2.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CM RE-ESTABLISHMENT REQUEST Significance: dual Direction: mobile station to network Table 9.2.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CM RE-ESTABLISHMENT REQUEST message content NOTE: In A/Gb mode, the maximum number of octets that can be transferred is 20. | 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.2.4 |
3,939 | Annex E (normative): Procedure for sub-domain allocation | When a 3GPP member company identifies the need for a new sub-domain name of ".3gppnetwork.org", that 3GPP member company shall propose a CR to this specification at the earliest available meeting of the responsible working group for this TS. The CR shall propose a new sub-domain name. The new sub-domain proposed shall be formatted in one of the formats as described in the following table. Table E.1: Sub-domain formats for the "3gppnetwork.org" domain and their respective intended usage NOTE 1: "<service_ID>" is a chosen label, conformant to DNS naming conventions (usually IETF RFC 1035 [19] and IETF RFC 1123 [20]) that clearly and succinctly describe the service and/or operation that is intended to use this sub-domain. NOTE 2: "<MNC>" and "<MCC>" are the MNC (padded to the left with a zero, if only a 2-digit MNC) and MCC of a PLMN. NOTE 3: "NID", "<MNC>" and "<MCC>" are the NID (hexadecimal digits as specified in clause 12.7), MNC (padded to the left with a zero, if only a 2-digit MNC) and MCC identifying a Stand-alone Non-Public Network (SNPN). Care should be taken when choosing which format a domain name should use. Once a format has been chosen, the responsible working group shall then check the CR and either endorse it or reject it. If the CR is endorsed, then the responsible working group shall send an LS to the GSMA NG with TSG-CT in copy. The LS shall describe the following key points: - the context - the service - intended use - involved actors - proposed new sub-domain name GSMA NG will then verify the consistence of the proposal and its usage within the domain's structure and interworking rules (e.g. access to the GRX/IPX Root DNS servers). GSMA NG will then endorse or reject the proposal and inform the responsible working group (in 3GPP) and also TSG CT. It is possible that GSMA NG will also specify, changes to the newly proposed sub-domain name (e.g. due to requested sub-domain name already allocated). NOTE 4: There is no need to request GSMA NG for new labels to the left of an already GSMA NG approved "<service_ID>". It is the responsibility of the responsible working group to ensure uniqueness of such new labels. It should be noted that services already defined to use the ".gprs" domain name will continue to do so and shall not use the new domain name of ".3gppnetwork.org"; this is to avoid destabilising services that are already live. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
3,940 | 9.1 gNB Synchronization | The gNB shall support a logical synchronization port for phase-, time- and/or frequency synchronization. Logical synchronization port for phase- and time-synchronization shall provide: 1) accuracy that allows to meet the gNB requirements on maximum relative phase difference for all gNBs in synchronized TDD-unicast area; 2) continuous time without leap seconds traceable to common time reference for all gNBs in synchronized TDD-unicast area. In the case the TDD-unicast area is not isolated, the common time reference shall be traceable to the Coordinated Universal Time (UTC). A logical synchronization port for phase- and time-synchronization may also be provided for e.g., all gNBs in FDD time domain inter-cell interference coordination synchronization area. Furthermore common SFN initialization time shall be provided for all gNBs in synchronized TDD-unicast area. In case of non isolated networks, the start of the radio frame on the output shall be synchronous with the input time reference, i.e., when an UTC traceable reference is required, the start of the radio frame shall be aligned with the start time of the UTC second. Unless otherwise mutually agreed by the operators of the cells in non isolated networks and/or unless different SFN initialization offsettings do not affect operators’ networks in the same area, the common SFN initialization time should be 1980-01-06T00:00:19 International Atomic Time (TAI). Based on this information, the gNB may derive the SFN according to the following formula: , where: time time adjusted by the common SFN initialization time, in units of 10 ms to match the length of radio frame and accuracy accordingly; period(SFN) SFN period. In case gNB is connected via TDM interface, it may be used to frequency synchronize the gNB. The characteristics of the clock in the gNB shall be designed taking into account that the jitter and wander performance requirements on the interface are in accordance with network limits for output wander at traffic interfaces of either ITU-T Recommendation G.823 [8], ITU-T Recommendation G.824 [9] or network limits for the maximum output jitter and wander at any hierarchical interface of ITU-T Recommendation G.825 [10], whichever is applicable. In case gNB is connected via Ethernet interface and the network supports Synchronous Ethernet, the gNB may use this interface to get frequency synchronization. In this case the design of the gNB clock should be done considering the jitter and wander performance requirements on the interface are as specified for output jitter and wander at EEC interfaces of ITU-T Recommendation G.8261/Y.1361 [11], defined in clause 9.2.1. Further considerations on Synchronous Ethernet recommendations and architectural aspects are defined in clause 12.2.1 and Annex A of ITU-T Recommendation G.8261/Y.1361 [11]. A configurable LTE TDD-offset of start frame shall be supported by all gNBs in synchronized TDD-unicast areas in order to achieve interoperability in coexistence scenarios. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 9.1 |
3,941 | 7.3.1A Minimum requirements (QPSK) for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one E-UTRA band the 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.3.1-1, Table 7.3.1-1a and Table 7.3.1-2. The reference sensitivity is defined to be met with all downlink component carriers active and one of the uplink carriers active. The uplink resource blocks shall be located as close as possible to the primary downlink operating band but confined within the transmission bandwidth configuration for the channel bandwidth (Table 5.6-1). The primary downlink operating band is the downlink band of the active uplink operating band. The UE shall meet the requirements specified in subclause 7.3.1 with the following exceptions. For the bands supporting 4 antenna ports which are in Table 7.3.1-1a, the minimum requirements for reference sensitivity in the reference sensitivity exception tables shall be modified by the amount given in ΔRIB,4R in Table 7.3.1-1a for the applicable E-UTRA bands unless otherwise specified. For the bands supporting 8 antenna ports which are in Table 7.3.1-1aa, the minimum requirements for reference sensitivity in the reference sensitivity exception tables shall be modified by the amount given in ΔRIB,8R in Table 7.3.1-1aa for the applicable E-UTRA bands unless otherwise specified. For the UE that supports any of the E-UTRA CA configurations given in Table 7.3.1A-0a, exceptions to the requirements for a band(s) specified in subclause 7.3.1 are allowed when the band(s) is impacted by harmonic interference from the uplink transmission in a lower-frequency band of the same CA configuration. For these exceptions, the UE shall meet the requirements specified in Table 7.3.1A-0a and Table 7.3.1A-0b. These exceptions also apply to any higher order CA or DC combination containing one of the exception combinations in this clause as subset. Table 7.3.1A-0a: Reference sensitivity for carrier aggregation QPSK PREFSENS, CA (exceptions due to harmonic issue) Table 7.3.1A-0b: Uplink configuration for the low band (exceptions due to harmonic issue) For the UE that supports any of the E-UTRA CA configurations given in Table 7.3.1A-0bA, exceptions to the requirements for a band(s) specified in subclause 7.3.1 are allowed when the band(s) is impacted by the uplink being active within a specified frequency range as noted in Table 7.3.1A-0bA. For these exceptions, the UE shall meet the requirements specified in Table 7.3.1A-0bA and Table 7.3.1A-0bB. These exceptions also apply to any higher order CA or DC combination containing one of the exception combinations in this clause as subset. Table 7.3.1A-0bA: Reference sensitivity for carrier aggregation QPSK PREFSENS, CA (exceptions for two bands due to close proximity of UL to DL channel) Table 7.3.1A-0bB: Uplink configuration for the uplink band (exceptions for two bands due to close proximity of UL to DL channel) Table 7.3.1A-0bC: Void Table 7.3.1A-0bD: Void Table 7.3.1A-0bD1: Void Table 7.3.1A-0bD2: Void Table 7.3.1A-0bD3: Void Table 7.3.1A-0bD4: Void or the UE that supports any of the E-UTRA CA configurations given in Table 7.3.1A-0bE, exceptions to the requirements for a band(s) specified in subclause 7.3.1 are allowed when the band(s) is impacted by uplink being active in the applicable active UL bands of the same CA configuration in Table 7.3.1A-0bE. For these exceptions, the UE shall meet the reference sensitivities specified in Table 7.3.1A-0bE and Table 7.3.1A-0bF. These exceptions also apply to any higher order CA or DC combination containing one of the exception combinations in this clause as subset. Table 7.3.1A-0bE: Reference sensitivity for carrier aggregation QPSK PREFSENS, CA (exceptions due to cross band isolation issues of TDD and FDD bands) Table 7.3.1A-0bF: Uplink configuration for reference sensitivity (exceptions due to cross band isolation issues of TDD and FDD bands) For band combinations including operating bands without uplink band (as noted in Table 5.5-1), the requirements are specified in Table 7.3.1A-0d and for any uplink band with uplink configuration specified in Table 7.3.1-2. These requirements also apply to any higher order CA or DC combination containing one of the exception combinations in this clause as subset. Table 7.3.1A-0d: Reference sensitivity QPSK PREFSENS (CA with a SDL band) Table 7.3.1A-0e: Void For band combinations including operating band 46 (Table 5.5-1), the requirements are specified in Table 7.3.1A-0eA for the uplink in any band other than band 46 with the uplink configuration specified in Table 7.3.1-2 and Table 7.3.1A-0eC. These requirements also apply to any higher order CA or DC combination containing one of the combinations in this clause as subset. For band combinations including operating band 49 (Table 5.5-1), the requirements are specified in Table 7.3.1A-0eA for the uplink in any band other than Band 49 with uplink configurations specified in Table 7.3.1-2 and measurement exclusion region in Table 7.3.1A-0eD. These requirements also apply to any higher order CA or DC combination containing one of the combinations in this clause as subset. Table 7.3.1A-0eA: Reference sensitivity QPSK PREFSENS (CA with band 46 or Band 49) Table 7.3.1A-0eB: Void Table 7.3.1A-0eC specifies the Band 46 reference measurement exclusion region for different licensed component carriers and channel bandwidth. The exclusion region is defined according to the licensed component carrier channel bandwidth. The UL configurations to be adopted for the test are specified in Table 7.3.1-2. The exclusion region in Table 7.3.1A-0eC is specified for the case of 10MHz and 20MHz channel bandwidth in Band 46. Table 7.3.1A-0eC: Band 46 Reference sensitivity measurement exclusion region in MHz. Table 7.3.1A-0eD specifies the Band 49 reference measurement exclusion region for different licensed component carriers and channel bandwidth. The exclusion region is defined according to the licensed component carrier channel bandwidth. The UL configurations to be adopted for the test are specified in Table 7.3.1-2. Table 7.3.1A-0eD: Band 49 reference sensitivity measurement exclusion region in MHz. In all cases for single uplink inter-band CA, unless given by Table 7.3.1-3 for the band with the active uplink carrier, the applicable reference sensitivity requirements shall be verified with the network signalling value NS_01 (Table 6.2.4-1) configured. For inter-band carrier aggregation with one component carrier per operating band (up to four downlinks) and the uplink assigned to two E-UTRA bands the 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.3.1-1, Table 7.3.1-1a and Table 7.3.1-2. The reference sensitivity is defined to be met with all downlink component carriers active and both of the uplink carriers active. For E-UTRA CA configurations with uplink and downlink assigned to two E-UTRA bands given in Table 7.3.1A-0f, the reference sensitivity is defined only for the specific uplink and downlink test points which are specified in Table 7.3.1A-0f. For E-UTRA CA configurations with uplink assigned to two E-UTRA bands and downlink assigned to three E-UTRA bands given in Table 7.3.1A-0g, the reference sensitivity is defined only for the specific uplink and downlink test points which are specified in Table 7.3.1A-0g. For these test points the reference sensitivity requirement specified in Table 7.3.1-1 and Table 7.3.1-1a are relaxed by the amount of the corresponding parameter MSD given in Table 7.3.1A-0f and Table 7.3.1A-0g. The allowed exceptions defined in Table 7.3.1A-0a and Table 7.3.1A-0b for inter-band carrier aggregation with a single active uplink are also applicable for dual uplink operation. Table 7.3.1A-0f: 2DL/2UL interband Reference sensitivity QPSK PREFSENS and uplink/downlink configurations Table 7.3.1A-0g: 3DL/2UL interband Reference sensitivity QPSK PREFSENS and uplink/downlink configurations For intra-band contiguous carrier aggregation the throughput of each component carrier 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.3.1-1, Table 7.3.1-1a, Table 7.3.1-1A, Table 7.3.1-1B, Table 7.3.1-1C, Table 7.3.1A-0h and Table 7.3.1A-1. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the power levels in Table 7.3.1-1 and Table 7.3.1-1a also apply for an SCC assigned in the unpaired part. The requirement is verified using an uplink CA configuration with the largest number of carriers supported by the UE. Table 7.3.1A-0h, Table 7.3.1A-1 and Table 7.3.1A-2 specifies the maximum number of allocated uplink resource blocks for which the intra-band contiguous carrier aggregation reference sensitivity requirement shall be met. The PCC and SCC allocations as defined in Table 7.3.1A-0h, Table 7.3.1A-1 and Table 7.3.1A-2 form a contiguous allocation where TX–RX frequency separations of the component carriers are as defined in Table 5.7.4-1. In case downlink CA configuration has additional SCC(s) compared to uplink CA configuration those are configured furthers away from uplink band. For UE(s) supporting one uplink carrier, the uplink configuration of the PCC shall be in accordance with Table 7.3.1-2 and the downlink PCC carrier center frequency shall be configured closer to uplink operating band than any of the downlink SCC center frequency. Unless given by Table 7.3.1-3, the reference sensitivity requirements shall be verified with the network signalling value NS_01 (Table 6.2.4-1) configured. Table 7.3.1A-0h: Intra-band contiguous CA uplink configuration for reference sensitivity for Bandwidth Class B Table 7.3.1A-1: Intra-band contiguous CA uplink configuration for reference sensitivity for Bandwidth Class C Table 7.3.1A-2: Intra-band contiguous CA uplink configuration for reference sensitivity for Bandwidth Class D For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, the throughput of each downlink component carrier 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) and parameters specified in Table 7.3.1-1, Table 7.3.1-1a, Table 7.3.1-1A, Table 7.3.1-1B, Table 7.3.1-1C and Table 7.3.1A-3 with the reference sensitivity power level increased by RIBNC given in Table 7.3.1A-3 for the SCC(s). For aggregation of more than two downlink FDD carriers with one uplink carrier the reference sensitivity is defined only for the specific uplink and downlink test points which are specified in Table 7.3.1A-3. The requirements apply with all downlink carriers active. Unless given by Table 7.3.1-3, the reference sensitivity requirements shall be verified with the network signalling value NS_01 (Table 6.2.4-1) configured. Table 7.3.1A-3: Intra-band non-contiguous CA with one uplink configuration for reference sensitivity For intra-band non-contiguous carrier aggregation with two uplink and downlink carriers the reference sensitivity is defined to be met with both downlink and uplink carriers activated. The downlink PCC and SCC minimum requirements for reference sensitivity power level as specified in Table 7.3.1-1, Table 7.3.1-1a, Table 7.3.1-1A, Table 7.3.1-1B and Table 7.3.1-1C are increased by amount of ΔR2UL_PCC and ΔR2UL_SCC which are defined in Table 7.3.1A-4 when uplink PCC and SCC allocations are according to the Table 7.3.1A-4. Table 7.3.1A-4: Intra-band non-contiguous CA with two uplinks configuration for reference sensitivity For combinations of intra-band and inter-band carrier aggregation, the requirement is defined with an uplink configuration in accordance with Table 7.3.1A-3 when the uplink is active in the band supporting two or more non-contigous component carriers, Table 7.3.1A-1 when the uplink (up to two contiguously aggregated uplink carriers) is active in a band supporting two contiguous component carriers and in accordance with Table 7.3.1-2 when an 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. The carrier center frequency of PCC in the UL operating band is configured closer to the DL operating band when the uplink is active in band(s) supporting non-contiguous aggregation. For these uplink configurations, the UE shall meet the reference sensitivity requirements for intra-band non-contiguous carrier aggregation of two or more 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.3.1. For the two or more component carriers within the same band, RIBNC = 0 dB for all sub-block gaps (Table 7.3.1A-3) when the uplink is active in another band. All downlink carriers shall be active throughout the tests and the requirements for the downlinks shall be met with all uplink carriers active in each band capable of UL operation. For component carriers configured in Band 46, the said requirements for intra-band carrier aggregation of downlink carriers are replaced by the requirements in Table 7.3.1A-0eA for the uplink in any band other than band 46 with the uplink configuration specified in Table 7.3.1-2. Unless given by Table 7.3.1-3, the reference sensitivity requirements shall be verified with the network signalling value NS_01 (Table 6.2.4-1) configured. Table 7.3.1A-5: Void Table 7.3.1A-6: Void | 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.3.1A |
3,942 | 13.3.1.2 IPv6 Prefix allocation via IPv6 stateless address autoconfiguration via DHCPv6 | When the IPv6 prefix is allocated from the external PDN, it is the P-GW’s responsibility to obtain the IPv6 prefix for external PDN, allocate and release the IPv6 prefix. The P-GW may use DHCPv6 to obtain the IPv6 prefix from the external PDN. In this context, the P-GW shall act as a DHCP client as per IETF RFC 3315 [46] towards the external DHCPv6 server. The use cases between the UE and the P-GW that may lead the P-GW to interwork with the external DHCPv6 servers are described in subclause 11.2.1.3.1a. | 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 | 13.3.1.2 |
3,943 | 5.6.1 Service request procedure 5.6.1.1 General | The purpose of the service request procedure is to transfer the EMM mode from EMM-IDLE to EMM-CONNECTED mode. If the UE is not using EPS services with control plane CIoT EPS optimization, this procedure is used to establish the radio and S1 bearers when user data or signalling is to be sent. If the UE is using EPS services with control plane CIoT EPS optimization, this procedure can be used for UE initiated transfer of user data via the control plane. Another purpose of this procedure is to invoke MO/MT CS fallback or 1xCS fallback procedures. This procedure is used when: - the network has downlink signalling pending; - the UE has uplink signalling pending; - the UE or the network has user data pending and the UE is in EMM-IDLE mode; - the UE is in EMM-CONNECTED mode and has a NAS signalling connection only; the UE is using EPS services with control plane CIoT EPS optimization, and it has user data pending which is to be transferred via user plane radio bearers; - the UE in EMM-IDLE or EMM-CONNECTED mode has requested to perform mobile originating/terminating CS fallback or 1xCS fallback; - the network has downlink cdma2000® signalling pending; - the UE has uplink cdma2000® signalling pending; - the UE has to request resources for ProSe direct discovery or Prose direct communication; - the UE has to request resources for V2X communication over PC5; - the UE that is MUSIM UE and in EMM-IDLE mode requests the network to remove the paging restriction; or - to indicate to the network that the MUSIM UE requests the release of the NAS signalling connection or reject paging. The service request procedure is initiated by the UE, however, for the downlink transfer of signalling, cdma2000® signalling or user data in EMM-IDLE mode, the trigger is given by the network by means of the paging procedure (see clause 5.6.2). The UE shall invoke the service request procedure when: a) the UE in EMM-IDLE mode receives a paging request using S-TMSI with CN domain indicator set to "PS" from the network; NOTE: 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. b) the UE, in EMM-IDLE mode, has pending user data to be sent; c) the UE, in EMM-IDLE mode, has uplink signalling pending; d) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use CS fallback and has a mobile originating CS fallback request from the upper layer; e) the UE in EMM-IDLE mode is configured to use CS fallback and receives a paging request with CN domain indicator set to "CS", or the UE in EMM-CONNECTED mode is configured to use CS fallback and receives a CS SERVICE NOTIFICATION message; f) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use 1xCS fallback and has a mobile originating 1xCS fallback request from the upper layer; g) the UE in EMM-CONNECTED mode is configured to use 1xCS fallback and accepts cdma2000® signalling messages containing a 1xCS paging request received over E-UTRAN; h) the UE, in EMM-IDLE mode, has uplink cdma2000® signalling pending to be transmitted over E-UTRAN; i) the UE, in EMM-IDLE or EMM-CONNECTED mode, is configured to use 1xCS fallback, accepts cdma2000® signalling messages containing a 1xCS paging request received over cdma2000® 1xRTT, and the network supports dual Rx CSFB or provide CS fallback registration parameters (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]); j) the UE, in EMM-IDLE or EMM-CONNECTED mode, has uplink cdma2000® signalling pending to be transmitted over cdma2000® 1xRTT, and the network supports dual Rx CSFB or provide CS fallback registration parameters (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]); k) the UE performs an inter-system change from S101 mode to S1 mode and has user data pending; l) the UE in EMM-IDLE mode has to request resources for ProSe direct discovery or Prose direct communication (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]); m) the UE, in EMM-CONNECTED mode and has a NAS signalling connection only, is using EPS services with control plane CIoT EPS optimization and has pending user data to be sent via user plane radio bearers; n) the UE in EMM-IDLE mode has to request resources for V2X communication over PC5 (see 3GPP TS 23.285[ Architecture enhancements for V2X services ] [47]); o) the network supports the paging restriction and the UE that is MUSIM UE and in EMM-IDLE mode is requesting the network to remove the paging restriction; p) the network supports the NAS signalling connection release and the MUSIM UE in EMM-CONNECTED mode requests the network to release the NAS signalling connection and, if the network supports the paging restriction, optionally includes paging restriction; or q) the network supports the reject paging request and the MUSIM UE, in EMM-IDLE mode when responding to paging rejects the paging request from the network, requests the network to release the NAS signalling connection and, if the network supports the paging restriction, optionally includes paging restriction. If one of the above criteria to invoke the service request procedure is fulfilled, then the service request procedure may only be initiated by the UE when the following conditions are fulfilled: - its EPS update status is EU1 UPDATED, and the current TAI of the current serving cell is included in the TAI list; and - no EMM specific procedure is ongoing. The MUSIM UE shall not initiate service request procedure for requesting the network to release the NAS signalling connection if the UE is attached for emergency bearer services or if the UE has a PDN connection for emergency bearer services established. To enable the emergency call back, the UE shall not initiate service request procedure for requesting the network to release the NAS signalling connection for a UE implementation-specific duration of time after the completion of the emergency bearer services. NOTE 1: AS indications (indications from lower layers) are results of procedures triggered by MME in service request procedure. Triggered procedures could be e.g. RRC connection reconfiguration procedure (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) and inter system PS handover to GERAN or UTRAN procedure as a result of CSFB procedure (see 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [9]). NOTE 2: For 1xCS fallback, the UE sends the EXTENDED SERVICE REQUEST message and starts timer T3417. The procedure is considered completed upon receiving indication of system change from AS. Figure 5.6.1.1.1: Service request procedure (part 1) NOTE 1: Security protected NAS message: this could be e.g. a SECURITY MODE COMMAND, SERVICE ACCEPT, or ESM DATA TRANSPORT message. NOTE 2: AS indications (indications from lower layers) are results of procedures triggered by MME in service request procedure. Triggered procedures could be e.g. an RRC connection release procedure or RRC connection reconfiguration procedure (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). Figure 5.6.1.1.2: Service request procedure (part 2) A service request attempt counter is used to limit the number of service request attempts and no response from the network. The service request attempt counter shall be incremented as specified in clause 5.6.1.6. The service request attempt counter shall be reset when: - a normal or periodic tracking area updating or a combined tracking area updating procedure is successfully completed; - a service request procedure in order to obtain packet services is successfully completed; - a service request procedure is rejected as specified in clause 5.6.1.5 or clause 5.3.7b; or - the UE moves to EMM-DEREGISTERED state. | 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.1 |
3,944 | 5.15.11.1.2 Hierarchical NSAC architecture | In the Hierarchical NSAC architecture, the NSACFs deployed in the NSAC service areas interacts with the Primary NSACF when needed, and as explained below. The main differences between the non-Hierarchical architecture and the Hierarchical architecture is that the AMFs and the NSACFs deployed in the Hierarchical architecture support the following: - When the AMF triggers an NSAC request to the NSACF, the AMF includes the UE already Registered indication if the AMF can determine that the UE has been registered with the S-NSSAI in one NSAC service area before. If the AMF does not include the UE already Registered indication, the registration request to the indicated S-NSSAI is determined as initial registration, i.e. the UE has not been registered in any service area before. The AMF determines the UE already Registered indication based on the received Allowed NSSAI information from the source AMF (in case of inter AMF handover) or from SMF+PGW-C (in case of mobility from EPS to 5GS). - There are two types of UE admission control: quota-based control or threshold-based control. A PLMN is configured to deploy only one type of UE admission control. Based on the type of UE admission control configured for the PLMN, the NSACF handles the NSAC request as described below: - For NSACFs supporting quota-based control, if the NSACF receives a request to increase the number of UEs and the number of UEs registered for a network slice has reached the local maximum number of UEs provisioned in the NSACF, or upon receiving a request to decrease the number of UEs and no UE entry is present in the NSACF, the NSACF interacts with the Primary NSACF for the handling of the NSAC request for the UE. The Primary NSACF may return in the response an updated local maximum number of registered UEs value to the NSACF based on the status of registered UEs for the Network Slice and which enables the NSACF to handle locally the request. Alternatively, and if the request to increase the number of UEs includes the UE already Registered indication, the Primary NSACF may admit the UE request and store the UE entry which allows for service continuity. The Primary NSACF may also reject the request. If the NSACF receives a request to increase the number of UEs and the local maximum number of UEs is not reached, the NSACF handles the request locally and sends a response to the AMF without interaction with the Primary NSACF. - For NSACF supporting threshold-based control, the NSACF is initially configured with a UE admission threshold and a local maximum number of Registered UEs to be admitted. Threshold-based control refers to an admission threshold, defined in percentage, against provisioned local maximum number in NSACF (e.g. an admission threshold of 80% refers to the case when 80% of the provisioned local maximum number should be used). If upon a receiving a request to increase the number of UEs without a UE already Registered indication and if UE admission threshold is at or above the threshold level configured at the NSACF, the NSACF immediately rejects the NSAC request. If the received request includes the UE already Registered indication and if UE admission is at or above the threshold level configured at the NSACF, the NSACF accepts the request to enable UE admission and allow for service continuity as long as the local maximum number of Registered UEs have not been reached. If the local maximum number of registered UEs value have been reached, the NSACF interacts with the Primary NSACF for the handling of the NSAC request for the UE. The NSACF does not include the UE already Registered indication in this case. The Primary NSACF may return an updated UE admission threshold value to the NSACF in the response which enables the NSACF to handle the request locally. Alternatively, the Primary NSACF may handle and store the UE entry. The Primary NSACF may also reject the request. - For both options, the Primary NSACF supports the following capabilities depending on the NSACF configuration: - Returning a new updated local maximum number of Registered UEs for the NSACF to admit if the NSACF is configured to support the quota-based UE admission control; or - Returning a new updated UE admission threshold for the NSACF to apply if the NSACF is configured to support the threshold-based UE admission control; - The Primary NSACF handles, stores entries only related to UEs which the NSAC request includes the UE already Registered indication, that are already admitted in an existing NSAC service area but cannot be admitted in the new NSAC service area due to no remaining local maximum number of registered UEs, as long as the overall PLMN number of registered UEs at the Primary NSACF is not exhausted. The Primary NSACF informs the NSACF in its response; - Based on the response from the Primary NSACF, the NSACF determines whether to accept or reject the NSAC request for UE registration. In addition, the NSACF may also update the local maximum number of Registered UEs or admission threshold respectively if the related updated value is received; - At any time, the Primary NSACF can update the NSACFs local maximum number of Registered UEs or admission threshold through the Nnsacf_NSAC_LocalNumberUpdate operation as described in clause 4.2.11.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The updated values provided from the Primary NSACF to the NSACFs may directly apply to current NSAC pending request in NSACF and are used for all future requests. - The Primary NSACF subscribes with all NSACFs to obtain the number of currently registered UEs at all NSACFs. Based on the obtained information, the Primary NSACF can update the NSACF with local maximum number of registered UEs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.1.2 |
3,945 | 9.12.2.2 TDD | For the parameters specified in Table 9.12.2.2-1and Table 9.12.2.2-2 using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.12.2.2-3 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.2.2-1: Fading test for slot-PDSCH (TDD) Table 9.12.2.2-2: SPDCCH parameters (TDD) Table 9.12.2.2-3: Minimum requirement for slot-PDSCH (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 | 9.12.2.2 |
3,946 | 10.5.3.4 Identity type | The purpose of the Identity Type information element is to specify which identity is requested. The Identity Type information element is coded as shown in figure 10.5.78/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.92/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Identity Type is a type 1 information element. Figure 10.5.78/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Identity Type information element Table 10.5.92/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Identity Type 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.3.4 |
3,947 | D.8.5.1 Common procedures | When on receipt of a message, a) an "imperative message part" error; or b) a "missing mandatory IE" error is diagnosed or when a message containing: a) a syntactically incorrect mandatory IE; b) an IE with an IEI unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]); or c) an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]) is received, the UE shall ignore the UPDS message; the network shall proceed as follows: the network shall: 1) try to treat the message (the exact further actions are implementation dependent); or 2) ignore the message. | 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 | D.8.5.1 |
3,948 | 4.1.1.8 Handling of security related parameters at switch on and switch off | At switch on, an ME supporting UTRAN Iu mode shall proceed as follows: - if a USIM is inserted, the ME shall read the STARTCS and STARTPS value from the USIM. If STARTCS and/or STARTPS read from the USIM are greater than or equal to the maximum value of STARTCS and STARTPS provided on the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) or the CKSN or GPRS CKSN stored on the USIM indicates "no key available", the ME shall set the START value in the volatile memory of the ME for the corresponding core network domain(s) to zero. In addition if the read STARTCS and/or STARTPS are greater than or equal to the maximum value, the ME shall delete the corresponding CKSN or GPRS CKSN from the ME and the USIM. The ME shall set the STARTCS and STARTPS value on the USIM to the maximum value of STARTCS and STARTPS provided on the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]); and - if a SIM is inserted, the ME shall read the STARTCS and STARTPS value from the non-volatile memory. If STARTCS and/or STARTPS read from the non-volatile memory are greater than or equal to the default value specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a], subclause 6.8.2.4 or the CKSN or GPRS CKSN stored on the SIM indicates "no key available", the ME shall set the START value in the volatile memory of the ME for the corresponding core network domain(s) to zero. In addition if the read STARTCS and/or STARTPS are greater than or equal to the default value, the ME shall delete the corresponding CKSN or GPRS CKSN from the ME. The ME shall set the STARTCS and STARTPS value in the non-volatile memory to the default value specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a], subclause 6.8.2.4. NOTE: The lower layer handles the STARTCS and STARTPS value stored in the volatile memory of the ME as specified in 3GPP TS 25.331[ None ] [23c]. Only at switch off, an ME supporting UTRAN Iu mode shall proceed for each of the two domains, CS and PS, as follows: - if since switch on the ME performed an authentication procedure for the respective domain and stored the new security context on the USIM or SIM, and the new security context was not taken into use, the ME shall set the START value for this domain on the USIM or, if a SIM is inserted, in the non-volatile memory to zero; and - otherwise, if a security context for the respective domain is stored on the USIM or SIM, i.e. the CKSN or GPRS CKSN stored on the USIM or SIM is different from "no key available", the ME shall store the current START value used by the lower layer for this domain on the USIM or, if a SIM is inserted, in the non-volatile memory. | 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.8 |
3,949 | 5.7.2.4.2 Usage of Notification control with Alternative QoS Profiles at handover | During handover, the prioritized list of Alternative QoS Profile(s) (if available) is provided to the Target NG-RAN per QoS Flow in addition to the QoS profile. If the Target NG-RAN is not able to guarantee the GFBR, the PDB and the PER included in the QoS profile and if Alternative QoS Profiles are provided to the Target NG-RAN and the Target NG-RAN supports Alternative QoS Profiles, the Target NG-RAN checks whether the GFBR, the PDB and the PER values that it can fulfil match any of the Alternative QoS Profile(s) taking the priority order into account. If there is a match between one of the Alternative QoS Profiles and the GFBR, the PDB and the PER values that Target NG-RAN can fulfil, the Target NG-RAN shall accept the QoS Flow and indicate the reference to that Alternative QoS Profile to the Source NG-RAN. For delay-critical GBR QoS flows, the Target NG-RAN also takes into consideration whether it is able to accept the MDBV if it is included in the Alternative QoS profile. If there is no match to any Alternative QoS Profile, the Target NG-RAN rejects QoS Flows for which the Target NG-RAN is not able to guarantee the GFBR, the PDB, the PER and if available, an associated MDBV included in the QoS profile. After the handover is completed and a QoS Flow has been accepted by the Target NG-RAN based on an Alternative QoS Profile, the Target NG-RAN shall treat this QoS Flow in the same way as if it had sent a notification that the "GFBR can no longer be guaranteed" with a reference to that Alternative QoS Profile to the SMF (as described in clause 5.7.2.4.1b). If a QoS Flow has been accepted by the Target NG-RAN based on an Alternative QoS Profile, the reference to the matching Alternative QoS Profile is provided from the Target NG-RAN to the AMF (which forwards the message to the SMF) during the Xn and N2 based handover procedures as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. After the handover is completed successfully, the SMF shall send a notification to the PCF that the "GFBR can no longer be guaranteed" for a QoS Flow (see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] for details) if the SMF has received a reference to an Alternative QoS Profile and this reference indicates a change in the previously notified state of this QoS Flow. If the PCF has not indicated differently, the SMF shall also use NAS signalling (that is sent transparently through the RAN) to inform the UE about the QoS parameters (i.e. 5QI, GFBR, MFBR) corresponding to the new state of the QoS Flow. NOTE: A state change for the QoS Flow comprises a change from QoS profile fulfilled to Alternative QoS Profile fulfilled as well as the state change between fulfilled Alternative QoS Profiles. If a QoS Flow has been accepted by the Target NG-RAN based on the QoS Profile, the SMF shall interpret the fact that a QoS Flow is listed as transferred QoS Flow in the message received from the AMF as a notification that "GFBR can be guaranteed again" for this QoS Flow. After the handover is successfully completed, the Target NG-RAN performs as described in clause 5.7.2.4.1b. If the SMF has previously notified the PCF that the "GFBR can no longer be guaranteed" and the SMF does not receive an explicit notification that the "GFBR can no longer be guaranteed" for that QoS Flow from the Target NG-RAN within a configured time, the SMF shall notify the PCF that the "GFBR can be guaranteed again". If a QoS Flow has been accepted by the Target NG-RAN and SMF did not receive from the Target NG-RAN a reference to any Alternative QoS Profile and the SMF has previously informed the UE about QoS parameters corresponding to any of the Alternative QoS Profile(s), the SMF shall use NAS signalling to inform the UE about the QoS parameters corresponding to the QoS Profile. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.4.2 |
3,950 | 4.4.6.1 User plane architecture to support 5G LAN-type service | The general User Plane architectures described in clause 4.2.3 and clause 4.2.4 apply to 5G LAN-type services, with the additional options described in this clause. Figure 4.4.6.1-1 depicts the non-roaming user plane architecture to support 5G LAN-type service using local switch. Figure 4.4.6.1-1: Local-switch based user plane architecture in non-roaming scenario Figure 4.4.6.1-2 depicts the non-roaming user plane architecture to support 5G LAN-type service using N19 tunnel. Figure 4.4.6.1-2: N19-based user plane architecture in non-roaming scenario NOTE: As described in clause 5.29.3, the PSA UPFs can be controlled by a dedicated SMF, a dedicated SMF Set or multiple SMF Sets. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.6.1 |
3,951 | 6.3.5A.1.1 Minimum requirements | For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, the absolute power control tolerance is specified on each component carrier exceed the minimum output power as defined in subclause 6.3.2A and the total power is limited by maximum output power as defined in subclause 6.2.2A. The requirements defined in Table 6.3.5.1.1-1 shall apply on each component carrier with all component carriers active. The requirements can be tested by time aligning any transmission gaps on all the component carriers. For intra-band contiguous carrier aggregation bandwidth class B, C and D and intra-band non-contiguous carrier aggregation the absolute power control tolerance per component carrier is given in Table 6.3.5.1.1-1. | 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 | 6.3.5A.1.1 |
3,952 | P.4 Inter-system change between A/Gb mode and S1 mode | An MS is required to perform routing area updating for IMS voice termination at inter-system change from S1 mode to A/Gb mode and tracking area updating for IMS voice termination at inter-system change from A/Gb mode to S1 mode if: 1) conditions 1 and 2 of annex P.3 are fulfilled; 2) the "IMS voice over PS session indicator" received for S1 mode has the value "IMS voice over PS session in S1 mode supported"; and 3) the voice domain preference for E-UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [134] is not "CS voice only". | 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 | P.4 |
3,953 | 5.2.13.2.5 Nbsf_Management_Update service operation | Service Operation name: Nbsf_Management_Update Description: Replaces the list of UE address(es) for a PDU Session or replace PCF id or PCF address(es) for a PDU Session or for a UE.. NOTE 1: For example, PCF-2 may update its PCF id when level of binding is NF Instance and PCF-1 fails and PCF-2 is the new NF Instance handling the PDU Session or the UE. Inputs, Required: Binding Identifier for the PDU Session. UE address can contain IP address/prefix or Ethernet address as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 2: For support of time sensitive communication and time synchronization (as described in clause 5.28.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) the UE address contains the DS-TT port MAC address for Ethernet type PDU Session. Inputs, Optional: UE address(es), PCF id, PCF address(es). Outputs, Required: Result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.13.2.5 |
3,954 | 5.4A.3.1 Slot-SPUCCH | The complex-valued modulation symbols shall be generated as described in clause 5.4.2A. Depending on if the slot-SPUCCH is transmitted in the first or the second slot of the subframe, different block-wise spreading with the orthogonal sequences or is applied. Each spreading results in sets of values each according to: where - (see clause 5.4.2A) if transmitted in the first slot, and (see clause 5.4.2A), if transmitted in the second slot. - The orthogonal sequences and are given by Table 5.4.2A-1 Resources used for transmission of SPUCCH format 3 are identified by a resource index from which the quantities and are derived according to clause 5.4A.3 by replacing with . Each set of complex-valued symbols shall be cyclically shifted and transform precoded according to clause 5.4.2A with replaced by in the transform precoding. | 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.4A.3.1 |
3,955 | – MBS-SessionInfoListMulticast | The IE MBS-SessionInfoListMulticast provides a list of MBS multicast sessions transmitted via multicast MRB for RRC_INACTIVE UEs and, for each MBS multicast session, the associated G-RNTI and scheduling information. MBS-SessionInfoListMulticast information element -- ASN1START -- TAG-MBS-SESSIONINFOLISTMULTICAST-START MBS-SessionInfoListMulticast-r18 ::= SEQUENCE (SIZE (1..maxNrofMBS-Session-r17)) OF MBS-SessionInfoMulticast-r18 MBS-SessionInfoMulticast-r18 ::= SEQUENCE { mbs-SessionId-r18 TMGI-r17, g-RNTI-r18 RNTI-Value OPTIONAL, -- Need R mrb-ListMulticast-r18 MRB-ListMulticast-r18 OPTIONAL, -- Need R mtch-SchedulingInfo-r18 DRX-ConfigPTM-Index-r17 OPTIONAL, -- Need S mtch-NeighbourCell-r18 BIT STRING (SIZE(maxNeighCellMBS-r17)) OPTIONAL, -- Need S pdsch-ConfigIndex-r18 PDSCH-ConfigIndex-r17 OPTIONAL, -- Need S mtch-SSB-MappingWindowIndex-r18 MTCH-SSB-MappingWindowIndex-r17 OPTIONAL, -- Cond MTCH-Mapping thresholdIndex-r18 INTEGER (0..maxNrofThresholdMBS-r18) OPTIONAL, -- Need R pdcp-SYNC-Indicator-r18 ENUMERATED {true} OPTIONAL, -- Cond RRCRelease stopMonitoringRNTI-r18 ENUMERATED {true} OPTIONAL -- Need R } MRB-ListMulticast-r18 ::= SEQUENCE (SIZE (1.. maxMRB-r17)) OF MRB-InfoMulticast-r18 MRB-InfoMulticast-r18 ::= SEQUENCE { pdcp-Config-r18 MRB-PDCP-ConfigMulticast-r18, rlc-Config-r18 MRB-RLC-ConfigMulticast-r18, ... } MRB-PDCP-ConfigMulticast-r18 ::= SEQUENCE { pdcp-SN-SizeDL-r18 ENUMERATED {len12bits, len18bits}, headerCompression-r18 CHOICE { notUsed NULL, rohc SEQUENCE { maxCID-r18 INTEGER (1..16) DEFAULT 15, profiles-r18 SEQUENCE { profile0x0000-r18 BOOLEAN, profile0x0001-r18 BOOLEAN, profile0x0002-r18 BOOLEAN } } }, t-Reordering-r17 ENUMERATED {ms1, ms10, ms40, ms160, ms500, ms1000, ms1250, ms2750} OPTIONAL -- Need R } MRB-RLC-ConfigMulticast-r18 ::= SEQUENCE { logicalChannelIdentity-r18 CHOICE { logicalChannelIdentitymulticast-r18 LogicalChannelIdentity, logicalChannelIdentityExt-r18 LogicalChannelIdentityExt-r17 }, sn-FieldLength-r18 ENUMERATED {size6, size12}, t-Reassembly-r18 T-Reassembly OPTIONAL -- Need R } -- TAG-MBS-SESSIONINFOLISTMULTICAST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,956 | 6.8.2.1.3 State transition from RRC_INACTIVE to RRC_CONNECTED to a new gNB/ng-eNB | When the UE decides to resume the RRC connection to transit from RRC_INACTIVE to RRC_CONNECTED, the UE sends RRCResumeRequest message on SRB0 and hence it is not integrity protected. However, the RRCResumeRequest message shall include the I-RNTI and a ResumeMAC-I/shortResumeMAC-I. The I-RNTI (short or full I-RNTI) is used for context identification and its value shall be the same as the I-RNTI that the UE had received from the source gNB/ng-eNB in the RRCRelease with suspendConfig message. The ResumeMAC-I/shortResumeMAC-I is a 16-bit message authentication token, the UE shall calculate it using the integrity algorithm (NIA or EIA) in the stored AS security context, which was negotiated between the UE and the source gNB/ng-eNB and the current KRRCint with the following inputs: - KEY : it shall be set to current KRRCint; - BEARER : all its bits shall be set to 1. - DIRECTION : its bit shall be set to 1; - COUNT : all its bits shall be set to 1; - MESSAGE : it shall be set to VarResumeMAC-Input/VarShortInactiveMAC-Input as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22] for gNB and in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69] for ng-eNB with following inputs: source PCI, target Cell-ID, source C-RNTI. For protection of all RRC messages except RRCReject message following the sent RRCResumeRequest message, the UE shall derive a KNG-RAN* using the target PCI, target ARFCN-DL/EARFCN-DL and the KgNB/NH based on either a horizontal key derivation or a vertical key derivation as defined in clause 6.9.2.1.1 and Annex A.11/Annex A.12. The UE shall further derive KRRCint, KRRCenc, KUPenc (optionally), and KUPint (optionally) from the newly derived KNG-RAN*. When the target gNB/ng-eNB receives the RRCResumeRequest message from the UE, the target gNB/ng-eNB extracts the I-RNTI from the RRCResumeRequest message. The target gNB/ng-eNB contacts the source gNB/ng-eNB based on the information in the I-RNTI by sending an Xn-AP Retrieve UE Context Request message with the following included: I-RNTI, the ResumeMAC-I/shortResumeMAC-I and target Cell-ID, in order to allow the source gNB/ng-eNB to validate the UE request and to retrieve the UE context including the UE 5G AS security context. The source gNB/ng-eNB retrieves the stored UE context including the UE 5G AS security context from its database using the I-RNTI. The source gNB/ng-eNB verifies the ResumeMAC-I/shortResumeMAC-I using the current KRRCint key stored in the retrieved UE 5G AS security context (calculating the ResumeMAC-I/shortResumeMAC-I in the same way as described above). If the verification of the ResumeMAC-I/shortResumeMAC-I is successful, then the source gNB/ng-eNB calculates KNG-RAN* using the target cell PCI, target ARFCN-DL/EARFCN-DL and the KgNB/NH in the current UE 5G AS security context based on either a horizontal key derivation or a vertical key derivation according to whether the source gNB/ng-eNB has an unused pair of {NCC, NH} as described in Annex A.11/Annex A.12. The source gNB/ng-eNB can obtain the target PCI and target ARFCN-DL/EARFCN-DL from a cell configuration database by means of the target Cell-ID which was received from the target gNB/ng-eNB. Then the source gNB/ng-eNB shall respond with an Xn-AP Retrieve UE Context Response message to the target gNB/ng-eNB including the UE context that contains the UE 5G AS security context. The UE 5G AS security context sent to the target gNB/ng-eNB shall include the newly derived KNG-RAN*, the NCC associated to the KNG-RAN*, the UE 5G security capabilities, UP security policy, the UP security activation status with the corresponding PDU session ID(s), and the ciphering and integrity algorithms used by the UE with the source cell. The target gNB/ng-eNB shall check if it supports the ciphering and integrity algorithms the UE used with the last source cell. If the target gNB/ng-eNB does not support the ciphering and integrity algorithms used in the last source cell or if the target gNB/ng-eNB prefers to use different algorithms than the source gNB/ng-eNB, then the target gNB/ng-eNB shall send an RRC Setup/RRCSetup message on SRB0 to the UE in order to proceed with RRC connection establishment as if the UE was in RRC_IDLE (i.e., a fallback procedure). If the target gNB/ng-eNB supports the ciphering and integrity algorithms used with the last source cell and these algorithms are the chosen algorithms by the target gNB/ng-eNB, the target gNB/ng-eNB shall derive new AS keys (RRC integrity key, RRC encryption key and UP keys) using the algorithms the UE used with the source cell and the received KNG-RAN*. The target gNB/ng-eNB shall reset all PDCP COUNTs to 0 and activate the new keys in PDCP layer. The target gNB/ng-eNB shall respond to the UE with an RRC Resume message on SRB1 which is integrity protected and ciphered in PDCP layer using the new RRC keys. If the UP security activation status can be supported in the target gNB/ng-eNB, the target gNB/ng-eNB shall use the UP security activations that the UE used at the last source cell. Otherwise, the target gNB/ng-eNB shall respond with an RRC Setup message to establish a new RRC connection with the UE. When the UE receives the RRCResume message, the UE shall decrypt the message using the KRRCenc that was derived based on the newly derived KNG-RAN*. The UE shall also verify the <RRC Connection Resume> message by verifying the PDCP MAC-I using the KRRCint that was derived from the newly derived KNG-RAN* If verification of the RRCResume message is successful, the UE shall delete the current KRRCint key and the UE shall save the KRRCint, KRRCenc, KUPenc (optionally), and KUPint (optionally) from the newly derived KNG-RAN* as part of the UE current AS security context. In this case, the UE shall send the RRCResumeComplete message both integrity protected and ciphered to the target gNB/ng-eNB on SRB1 using the current KRRCint and KRRCenc. The UE shall use the UP security activations that were used before tansition to the RRC Inactive. If the UE receives RRCReject message from the target gNB/ng-eNB in response to the UE <RRC Resume Request> message, the UE shall delete newly derived AS keys used for connection resumption attempt, including newly derived KNG-RAN*, newly derivedRRC integrity key, RRC encryption key and UP keys, and keep the current KRRCint and the KgNB/NH in its current AS context. Security is fully resumed on UE side after reception and processing of RRCResume message. The UE can receive data on DRB(s) after having received and processed RRC connection resume message. UL data on DRB(s) can be sent after RRCResumeComplete message has been successfully sent. After a successful transition from RRC_INACTIVE to RRC_CONNECTED the target gNB/ng-eNB shall perform Path Switch procedure with the AMF. The AMF shall verify the UE security capability as described in the clause 6.7.3.1, and the SMF shall veirfy the UE security policy as described in the clause 6.6.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.2.1.3 |
3,957 | 5.3.5.15 L2 U2N or U2U Relay UE configuration 5.3.5.15.1 General | The network configures the L2 U2N or U2U Relay UE with relay operation related configurations. For each connected L2 U2N or U2U Remote UE indicated in sl-L2IdentityRemote, the network provides the configuration parameters used for relaying. The L2 U2N Relay UE shall: 1> if sl-L2RelayUE-Config is set to setup: 2> if the sl-L2RelayUE-Config contains the sl-RemoteUE-ToReleaseList: 3> perform the L2 U2N Remote UE release as specified in 5.3.5.15.2; 2> if the sl-L2RelayUE-Config contains the sl-RemoteUE-ToAddModList: 3> perform the L2 U2N Remote UE addition/modification as specified in 5.3.5.15.3; 1> else if sl-L2RelayUE-Config is set to release: 2> release the relay operation related configurations. The L2 U2U Relay UE shall: 1> if sl-L2RelayUE-Config is set to setup: 2> if the sl-L2RelayUE-Config contains the sl-U2U-RemoteUE-ToReleaseList: 3> perform the L2 U2U Remote UE release as specified in 5.3.5.15.2; 2> if the sl-L2RelayUE-Config contains the sl-U2U-RemoteUE-ToAddModList: 3> perform the L2 U2U Remote UE addition/modification as specified in 5.3.5.15.3; 1> else if sl-L2RelayUE-Config is set to release: 2> release the related configurations. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.15 |
3,958 | – RateMatchPatternLTE-CRS | The IE RateMatchPatternLTE-CRS is used to configure a pattern to rate match around LTE CRS. See TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.1.4.2. RateMatchPatternLTE-CRS information element -- ASN1START -- TAG-RATEMATCHPATTERNLTE-CRS-START RateMatchPatternLTE-CRS ::= SEQUENCE { carrierFreqDL INTEGER (0..16383), carrierBandwidthDL ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1}, mbsfn-SubframeConfigList EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need M nrofCRS-Ports ENUMERATED {n1, n2, n4}, v-Shift ENUMERATED {n0, n1, n2, n3, n4, n5} } LTE-CRS-PatternList-r16 ::= SEQUENCE (SIZE (1..maxLTE-CRS-Patterns-r16)) OF RateMatchPatternLTE-CRS -- TAG-RATEMATCHPATTERNLTE-CRS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,959 | 6.3.3.3 Selection of an UPF for a particular PDU Session | If there is an existing PDU Session, and the SMF receives another PDU Session request to the same DNN and S-NSSAI, and if the SMF determines that interworking with EPC is supported for this PDU Session as specified in clause 4.11.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the SMF should select the same UPF, otherwise, if the SMF determines that interworking with EPC is not supported for the new PDU Session, a different UPF may be selected. For the same DNN and S-NSSAI if different UPF are selected at 5GC, when the UE is moved to EPC network, there is no requirement to enforce APN-AMBR. Whether and how to apply APN-AMBR for the PDN Connection associated with this DNN/APN is implementation dependent, e.g. possibly only AMBR enforcement per PDU Session applies. The following parameter(s) and information may be considered by the SMF for UPF selection and re-selection: - UPF's dynamic load. - Analytics (i.e. statistics or predictions) for UPF load, Service Experience analytics and/or DN Performance analytics per UP path (including UPF and/or DNAI and/or AS instance) and UE related analytics (UE mobility, UE communication, and expected UE behavioural parameters) as received from NWDAF (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]), if NWDAF is deployed. - UPF's relative static capacity among UPFs supporting the same DNN. - UPF location available at the SMF. - UE location information. - Capability of the UPF and the functionality required for the particular UE session: An appropriate UPF can be selected by matching the functionality and features required for an UE. - Data Network Name (DNN). - PDU Session Type (i.e. IPv4, IPv6, IPv4v6, Ethernet Type or Unstructured Type) and if applicable, the static IP address/prefix. - SSC mode selected for the PDU Session. - UE subscription profile in UDM. - DNAI as included in the PCC Rules and described in clause 5.6.7. - Local operator policies. - S-NSSAI. - Access technology being used by the UE. - Information related to user plane topology and user plane terminations, that may be deduced from: - 5G-AN-provided identities (e.g. CellID, TAI), available UPF(s) and DNAI(s); - Identifiers (i.e. a FQDN and/or IP address(es)) of N3 terminations provided by a W-AGF or a TNGF or a TWIF; - Information regarding the user plane interfaces of UPF(s). This information may be acquired by the SMF using N4; - Information regarding the N3 User Plane termination(s) of the AN serving the UE. This may be deduced from 5G-AN-provided identities (e.g. CellID, TAI); - Information regarding the N9 User Plane termination(s) of UPF(s) if needed; - Information regarding the User plane termination(s) corresponding to DNAI(s). - RSN, support for redundant GTP-U path or support for redundant transport path in the transport layer (as in clause 5.33.2) when redundant UP handling is applicable. - Information regarding the ATSSS Steering Capability of the UE session (e.g. any combination of ATSSS-LL capability, MPTCP capability, MPQUIC capability) and information on the UPF support of RTT measurements without PMF. - Support for UPF allocation of IP address/prefix. - Support of the IPUPS functionality, specified in clause 5.8.2.14. - Support for High latency communication (see clause 5.31.8). - Support for functionality associated with high data rate low latency services, eXtended Reality (XR) and interactive media services, specified in clause 5.37 (for example, ECN marking for L4S, specified in clause 5.37.3, PDU Set Marking, specified in clause 5.37.5, UE power saving management, specified in clause 5.37.8). - User Plane Latency Requirements within AF request (see clause 5.6.7.1 and clause 6.3.6 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]). - List of supported Event ID(s) for exposure of UPF-related information via service based interface (see clause 7.2.29 and clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). NOTE 1: How the SMF determines information about the user plane network topology from information listed above, and what information is considered by the SMF, is based on operator configuration. NOTE 2: In this release the SMF uses no additional parameters for UPF selection for a PDU Session serving TSC or Deterministic Networking. If a PDU Session needs to connect to a specific UPF hosting a specific TSN 5GS bridge or 5GS router, this can be achieved e.g. by using a dedicated DNN/S-NSSAI combination. A W-AGF or a TNGF may provide Identifiers of its N3 terminations when forwarding over N2 uplink NAS signalling to the 5GC. The AMF may relay this information to the SMF, as part of session management signalling for a new PDU Session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.3.3 |
3,960 | 6.33.1 Description | Audio-Visual (AV) production includes television and radio studios, live news-gathering, sports events, music festivals, among others. Typically, numerous wireless devices such as microphones, in-ear monitoring systems or cameras are used in these scenarios. In the future, the wireless communication service for such devices are expected to be provided by a 5G system. AV production applications require a high degree of confidence, since they are related to the capturing and transmission of data at the beginning of a production chain. This differs drastically when compared to other multimedia services because the communication errors will be propagated to the entire audience that is consuming that content both live and on recorded media. Furthermore, the transmitted data is often post-processed with filters which could actually amplify defects that would be otherwise not noticed by humans. Therefore, these applications call for uncompressed or slightly compressed data, and very low probability of errors. These devices will also be used alongside existing technologies which have a high level of performance and so any new technologies will need to match or improve upon the existing workflows to drive adoption of the technology. The 3GPP system already plays an important role in the distribution of AV media content and services. Release 14 contains substantial enhancements to deliver TV services of various kinds, from linear TV programmes for mass audiences to custom-tailored on-demand services for mobile consumption. However, it is expected that also in the domain of AV content and service production, 3GPP systems will become an important tool for a market sector with steadily growing global revenues. There are several areas in which 3GPP networks can help to produce AV content and services in an efficient and flexible manner. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.33.1 |
3,961 | 4.22.3.4 Home-routed, the UE registered to different PLMNs over both access | In the case of home-routed roaming, when the UE is registered to different PLMNs over 3GPP access and non-3GPP access, the procedure for establishing a MA PDU Session when the UE requests a single-access PDU Session in an ATSSS capable PLMN but no policy in the UE and no local restrictions mandate a single access, is the same with the procedure specified in clause 4.22.2.2.2, with the following clarifications and modifications: - In step 1, the UE sets Request Type to initial request and it may include an "MA PDU Network-Upgrade Allowed" indication 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. - In step 2, if the AMF receives the "MA PDU Network-Upgrade Allowed" indication, the AMF may select a V-SMF that supports MA PDU sessions. - In step 3, the AMF sends the "MA PDU Network-Upgrade Allowed" indication, if received from the UE. - In step 6, the V-SMF provides the "MA PDU Network-Upgrade Allowed" indication, if received from AMF. - After step 6, if the H-SMF receives the "MA PDU Network-Upgrade Allowed" indication, the H-SMF may decide to convert the single-access PDU Session requested by the UE into a MA PDU Session, if dynamic PCC is not to be used. The H-SMF may take this decision based on local operator policy, subscription data indicating whether the MA PDU session is allowed or not and/or other conditions, which are not specified in the present document. - In step 9, if dynamic PCC is to be used for the MA PDU Session, the H-SMF sends an "MA PDU Network-Upgrade Allowed" indication to H-PCF in the SM Policy Control Create message if the MA PDU session is allowed based on the subscription data. The H-SMF also provides the ATSSS Capabilities of the MA PDU session. - In step 13, the H-SMF sends "MA PDU session Accepted" indication to V-SMF in the Nsmf_PDUSession_Create Response message. - In step 14, the V-SMF includes the "MA PDU session Accepted" indication in the Namf_Communication_N1N2MessageTransfer message to the AMF. The AMF mark this PDU session as MA PDU session based on the received "MA PDU session Accepted" indication. - In step 16, the UE receives a PDU Session Establishment Accept message, which includes ATSSS rules and indicates to UE that the requested single-access PDU session was established as a MA PDU Session. - After the MA PDU Session is established over one access, the UE shall send another PDU Session Establishment Request over the other access containing the same PDU Session ID that was provided over the first access. The UE also sets Request Type as "MA PDU Request" in UL NAS Transport message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.3.4 |
3,962 | 6.4.3.3 NAS integrity failure handling | The supervision of failed NAS integrity checks shall be performed both in the ME and the AMF. In case of failed integrity check (i.e. faulty or missing NAS-MAC) is detected after the start of NAS integrity protection, the concerned message shall be discarded except for some NAS messages specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. For those exceptions the AMF shall take the actions specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35] when receiving a NAS message with faulty or missing NAS-MAC. Discarding NAS messages can happen on the AMF side or on the ME side. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.3.3 |
3,963 | 4.7.1.8 List of forbidden PLMNs for GPRS service | The Mobile Equipment shall contain a list of "forbidden PLMNs for GPRS service". This lists shall be erased when the MS is switched off or when the SIM/USIM is removed or upon the expiry of the timer T3245 as described in subclause 4.1.1.6. The PLMN identification received on the BCCH shall be added to the list whenever a GPRS attach or routing area update is rejected by the network with the cause "GPRS services not allowed in this PLMN" or whenever a GPRS detach is initiated by the network with the cause "GPRS services not allowed in this PLMN". In a shared network, the MS shall choose 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 ] [14]. The PLMN identity selected for a GPRS attach procedure, or the PLMN identity used to construct the RAI that triggered the routing area updating procedure shall be added to the list of "forbidden PLMNs for GPRS service" whenever such a procedure is rejected by the network with the cause "GPRS services not allowed in this PLMN". Whenever a GPRS detach is initiated by the network with the cause "GPRS services not allowed in this PLMN", the PLMN identity that was selected for GPRS attach procedure or routing area update procedure shall be added to the list of "forbidden PLMNs for GPRS service". The maximum number of possible entries in this list is implementation dependent, but must be at least one entry. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted. | 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.7.1.8 |
3,964 | 8.9.1.1.2 Closed-loop spatial multiplexing performance (Cell-Specific Reference Symbols) | 8.9.1.1.2.1 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port The requirements are specified in Table 8.9.1.1.2.1-2, with the addition of the parameters in Table 8.9.1.1.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with frequency selective precoding. Table 8.9.1.1.2.1-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) Table 8.9.1.1.2.1-2: Minimum performance Single-Layer Spatial Multiplexing (FRC) 8.9.1.1.2.2 Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Port The requirements are specified in Table 8.9.1.1.2.2-2, with the addition of the parameters in Table 8.9.1.1.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with frequency selective precoding. Table 8.9.1.1.2.2-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) Table 8.9.1.1.2.2-2: Minimum performance Single-Layer Spatial Multiplexing (FRC) 8.9.1.1.2.3 Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Ports with CRS assistance information The requirements are specified in Table 8.9.1.1.2.3-2, with the addition of parameters in Table 8.9.1.1.2.3-1. In Table 8.9.1.1.2.3-1, 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 closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cells. Table 8.9.1.1.2.3-1: Test Parameters Table 8.9.1.1.2.3-2: Minimum performance for PDSCH | 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.9.1.1.2 |
3,965 | 5.15.18.3 Network based monitoring and enforcement of Network Slice Area of Service not matching deployed Tracking Areas | OAM may configure RRM policies for S-NSSAIs on a per cell basis as defined in TS 28.541[ Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 ] [149], i.e. cells outside the Network Slice Area of Service while in a TA supporting the S-NSSAI are allocated with no RRM resources for the S-NSSAI. The network may enforce the NS-AoS for an S-NSSAI as follows: 1. The network may monitor the validity of the S-NSSAI for UE in CM-CONNECTED state, i.e. the AMF subscribes to the AoI using the Location information of the S-NSSAI location availability information as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. 2. If the non-supporting UE makes a PDU Session establishment request with an S-NSSAI that is not valid as per the S-NSSAI location availability information, the AMF may reject the NAS Transport message with a back-off timer using S-NSSAI based congestion control as described in clause 5.19.7.4. 3. If the AMF determines that the UE in CM-CONNECTED has moved outside the NS-AoS, the AMF performs the following logic: a) If the non-supporting UE has other S-NSSAI(s) in the Allowed NSSAI, then the AMF may update the UE with a UE Configuration Update by removing the S-NSSAI from the Allowed NSSAI (which causes the UE to locally release the PDU Sessions) and optionally removing the S-NSSAI from the Configured NSSAI and then, the AMF requests the SMF to locally release in the network any PDU Sessions with that S-NSSAI as per step 1f in clause 4.2.3.4 in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Alternatively, the AMF requests the SMF to release PDU Sessions with that S-NSSAI. b) If the non-supporting UE does not have any other S-NSSAI in the Allowed NSSAI, then the AMF may update the UE with a UE Configuration Update by removing the S-NSSAI from the Allowed NSSAI (which causes the UE to locally release the PDU Sessions) and optionally removing the S-NSSAI from the Configured NSSAI, and adding a default S-NSSAI to the Allowed NSSAI and then, the AMF requests the SMF to locally release in the network any PDU Sessions with the removed S-NSSAI as per step 1f in clause 4.2.3.4 in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Alternatively, the AMF requests the SMF to release PDU Sessions with that S-NSSAI. NOTE: Whether the AMF removes the S-NSSAI from Allowed NSSAI and Configured NSSAI or only releases the associated PDU Sessions when the AMF enforces the NS-AoS is up to AMF configuration. c) For a non-supporting UE that does not have any other S-NSSAI in the Allowed NSSAI nor in the Configured NSSAI, then the AMF indicates to the SMF to release the PDU Session. 4. If the AMF determines that the S-NSSAI becomes valid e.g. the UE has moved into the NS-AoS, the AMF may update the UE with a UCU e.g. including the S-NSSAI in the Configured NSSAI. 5. When the AMF determines that the S-NSSAI of a PDU Session is restricted to an NS-AoS in the PDU session, the AMF indicates to the SMF that the PDU Session is subject to area restriction for the S-NSSAI. As a result, the SMF subscribes to "UE mobility event notification" for reporting UE presence in Area of Interest by providing S-NSSAI to the AMF as described in clauses 5.6.11 and 5.3.4.4. When SMF is notified that the UE location is outside of Area of Interest, SMF shall not send user data as payload of NAS message (see clause 5.31.4.1) in downlink directions and disable data notification. 6. When the SMF is notified by the AMF that the UE location is UNKNOWN as defined in Annex D, clauses D.1 and D.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], then based on operator policy SMF may enable downlink data notification and trigger the Network triggered Service Request procedure to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. Editor's note: Whether and based on what criteria to trigger the reporting and the applicability to the CP CIOT optimization use cases are FFS. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.18.3 |
3,966 | 8.3.1.3.2 Minimum requirements with Same Cell ID (with multiple NZP CSI-RS resources) | The requirements are specified in Table 8.3.1.3.2-3, with the additional parameters in Tables 8.3.1.3.2-1 and 8.3.1.3.2-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where the two transmission point share the same Cell ID. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the timing difference between two transmission points, channel parameters estimation and rate matching according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ (PQI) signalling defined in [6]. In Tables 8.3.1.3.2-1 and 8.3.1.3.2-2, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals and PBCH, and transmission point 2 (TP 2) has same Cell ID as TP 1. Multiple NZP CSI-RS resources and ZP CSI-RS resources are configured. In each sub-frame, DL PDSCH transmission is dynamically switched between 2 TPs with multiple PDSCH RE Mapping and Quasi-Co-Location Indicator configuration (PQI). Configurations of PDSCH RE Mapping and Quasi-Co-Location Indicator and downlink transmission hypothesis are defined in Table 8.3.1.3.2-2. The downlink physical channel setup for TP 1 is according to Table C.3.4-1 and for TP 2 according to Table C.3.4-2. Table 8.3.1.3.2-1: Test Parameters for timing offset compensation with DPS transmission Table 8.3.1.3.2-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.1.3.2-3: Performance Requirements for timing offset compensation with DPS transmission | 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.3.1.3.2 |
3,967 | 4.16.13.2 PCF-initiated UE Policy Association Termination | Figure 4.16.13.2-1: PCF-initiated UE Policy Association Termination This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the H-PCF interacts with the V-PCF to request removing Policy Association. The PCF is subscribed to notification of changes in Data Set "Policy Data" for a UE Policy Association ID. 1. The Policy data is removed, either the Data Set "Policy Data" or the Data Subset "UE context policy control". 2. The UDR sends the Nudr_DM_Notify_Request (Notification correlation Id, Policy Data, SUPI, UE Context Policy Control data, updated data) including the SUPI, the Data Set Identifier, the Data Subset Identifier and the Updated Data including empty "Policy Data" or empty "UE context policy control". 3. The PCF sends the Nudr_DM_Notify_Response to confirm reception and the result to UDR. 4. The PCF may notify the AMF of the removal of the UE Policy Association via Npcf_UEPolicyControl_UpdateNotify service operation. Alternatively, the PCF may decide to maintain the Policy Association if a default profile is applied, in this case steps 4, 5 and 6 are not executed. In the non-roaming case, the PCF unsubscribes to analytics from NWDAF if any. 5. The AMF acknowledges the operation. 6. Steps 2-5 in clause 4.16.13.1 AMF-initiated UE Policy Association Termination are performed to remove the UE Policy Association for this UE and the subscription to Policy Control Request Triggers for that UE Policy Association. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.13.2 |
3,968 | 7A.2.3 Key hierarchy for trusted non-3GPP access | The key hierarchy described in clause 6.2.1 applies, with the following changes: The key derived for non-3GPP access is called KTNGF in the context of trusted access. The key KTNGF received from AMF is used for two different purposes; to setup IPSec SAs between the UE and the TNGF and to create WLAN keys between the UE and the TNAP. To separate the keys for these purposes, the key hierarchy in Figure 7A.2.3-1 shall be used. The KTIPSec key is used to setup IPSec SAs and the KTNAP key is used to setup access security. The keys KTIPSec and KTNAP are derived as described in Clause A.22. Figure 7A.2.3-1 Key hierarchy for trusted non-3GPP access | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7A.2.3 |
3,969 | 5.2.27.4.6 Ntsctsf_ASTI_UpdateNotify operation | Service operation name: Ntsctsf_ASTI_UpdateNotify Description: Forward the notification for the 5G access stratum time distribution status change. When the TSCTSF detects a change, it invokes Ntsctsf_ASTI_UpdateNotify service operation to the NF consumer(s) which has subscribed for the event. Inputs, Required: Notification Correlation ID, Status of the access stratum time distribution (active or inactive). Inputs, Optional: If the Status of the access stratum time distribution is inactive due to acceptance criteria, Clock quality acceptance criteria result, impacted UE list. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.4.6 |
3,970 | 4.2.5 Messages with GTPv2 defined replies: Classification of Initial and Triggered Messages | An Initial message is a GTPv2 message that is not triggered as a response to another GTPv2 message across the given interface. The expected reply to a Request message is a Triggered message and the reply has the same message name as the Request but with "Response" replacing "Request". NOTE 1: If the SGW receives a "Create Session Request" on S11/S4, this can trigger either of the following GTPv2 messages across S5/S8: "Create Session Request" or "Modify Bearer Request". However, neither of these messages across S5/S8 is considered to be a Triggered message. If a Request message is a reply to a Command message, then the Request message is a Triggered message; otherwise the Request message is an Initial message. Responses do not have replies except when a "Context Acknowledge" is required as a reply to "Context Response" message as specified in relevant Stage 2 procedures. Context Acknowledge is always triggered message and does not have a reply. NOTE 2: The "Context Acknowledge" message is sent only if the "Context Response" message is received with the acceptance cause. A message whose name ends in "Command" is always an initial message. If a "Command" message fails, the name of the reply message is constructed by replacing "Command" with "Failure Indication". Apart from "Downlink Data Notification Failure Indication" message, a "Failure Indication" is a Triggered message. The "Failure Indication" message does not have a reply. If a "Command" message is successful, its reply will be a Request as specified in relevant Stage 2 procedures. A message whose name ends in "Notification" is always an Initial message, The expected Triggered message in reply has the same message name but with "Acknowledge" replacing "Notification", except for the case of the message "Downlink Data Notification" which has the reply "Downlink Data Notification Acknowledge" and "PGW Resart Notification" which has the reply "PGW Restart Notification Acknowledge". An "Acknowledge" message does not have a reply. CS Paging Indication, Stop Paging Indication, RAN Information Relay, Configuration Transfer Tunnel, Trace Session Activation, Trace Session Deactivation, ISR Status Indication and Downlink Data Notification Failure Indication messages are Initial messages that do not have a reply. A Version Not Supported Indication message is a Triggered message. | 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 | 4.2.5 |
3,971 | 4.7.7.4 GPRS ciphering key sequence number | The security parameters for authentication and ciphering are tied together in sets. In a GSM authentication challenge, from a challenge parameter RAND both the authentication response parameter SRES and the GPRS GSM ciphering key can be computed given the secret key associated to the IMSI. In a UMTS authentication challenge, from a challenge parameter RAND, the authentication response parameter RES and the GPRS UMTS ciphering key and the GPRS UMTS integrity key can be computed given the secret key associated to the IMSI. Furthermore, in the USIM a GPRS GSM ciphering key can be computed from the GPRS UMTS integrity key and the GPRS UMTS ciphering key by means of an unkeyed conversion function. Furthermore, in A/Gb mode if a GEA ciphering algorithm that requires a 128-bit ciphering key is taken into use, then a GPRS GSM Kc128 shall also be calculated as described in the subclause 4.7.7.3a. Furthermore, in A/Gb mode, if the MS and the network support integrity protection, when a GIA integrity algorithm that requires a 128-bit integrity key is taken into use, then a GPRS GSM Kint shall also be calculated as described in the subclause 4.7.7.3b. In order to allow start of ciphering on a logical link without authentication, GPRS ciphering key sequence numbers are introduced. The GPRS ciphering key sequence number is managed by the network such that the AUTHENTICATION AND CIPHERING REQUEST message contains the GPRS ciphering key sequence number allocated to the GPRS GSM ciphering key (in case of a GSM authentication challenge) or the GPRS UMTS ciphering key and the GPRS UMTS integrity key (in case of a UMTS authentication challenge) which may be computed from the RAND parameter carried in that message. If an authentication and ciphering procedure has been completed successfully and a GPRS ciphering key sequence number is stored in the network, the network shall include a different GPRS ciphering key sequence number in the AUTHENTICATION AND CIPHERING REQUEST message when it intiates a new authentication and ciphering procedure. If a GPRS ciphering key sequence number is contained in the first message during a GMM procedure, the network shall include a different GPRS ciphering key sequence number in the AUTHENTICATION_AND_CIPHERING REQUEST message when it initiates an authentication and ciphering procedure. The MS stores the GPRS ciphering key sequence number with the GPRS GSM ciphering key (in case of a GSM authentication challenge) and the GPRS UMTS ciphering key and the GPRS UMTS integrity key (in case of a UMTS authentication challenge), and includes the corresponding GPRS ciphering key sequence number in the ROUTING AREA UPDATE REQUEST, SERVICE REQUEST and ATTACH REQUEST messages. If the GPRS ciphering key sequence number is deleted, the associated GPRS GSM ciphering key, GPRS UMTS ciphering key, GPRS UMTS integrity key, GPRS GSM Kc128 and GPRS GSM Kint shall be deleted if any (i.e. the established GSM security context or the UMTS security context is no longer valid). In Iu mode, the network may choose to start ciphering and integrity checking with the stored GPRS UMTS ciphering key and the stored GPRS UMTS integrity key (under the restrictions given in 3GPP TS 42.009[ Security aspects ] [5] and 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) if the stored GPRS ciphering key sequence number and the one given from the MS are equal. In A/Gb mode, the network may choose to start ciphering with the stored GPRS GSM ciphering key or GPRS GSM Kc128 (under the restrictions given in 3GPP TS 42.009[ Security aspects ] [5]) if the stored GPRS ciphering key sequence number and the one given from the MS are equal and the previously negotiated ciphering algorithm is known and supported in the network. When ciphering is requested at GPRS attach, the authentication and ciphering procedure shall be performed since the MS does not store the ciphering algorithm after entering state GMM-DEREGISTERED. NOTE 1: The decision of starting ciphering with the GPRS GSM ciphering key or the GPRS GSM Kc128 depends on whether the network indicates in the AUTHENTICATION AND CIPHERING REQUEST message a GEA ciphering algorithm which requires a 64 or 128-bit ciphering key as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. In A/Gb mode, if MS indicates support of integrity protection in the MS network capability IE to the network, if the ME has a Integrity Algorithm IE and a Ciphering Algorithm IE stored in the ME non-volatile memory at MS power on, then the GMM layer shall calculate a GPRS GSM Kint key as described in subclause 4.7.7.3b and a GPRS GSM Kc128 key as described in subclause 4.7.7.3a and indicate to the LLC layer before sending the ATTACH REQUEST message that LLC layer shall start integrity protection with the indicated GPRS GSM Kint key and the integrity algorithm (indicated in the stored Integrity Algorithm IE). The GMM layer shall also assign the GPRS GSM Kc128 key and the ciphering algorithm (indicated in the stored Ciphering Algorithm IE) to the LLC layer. The network shall start integrity protection in the LLC layer after reception of the ATTACH REQUEST message with the stored GPRS GSM Kint and the integrity algorithm identified by the stored GPRS GSMintegrity algorithm used when UE was previously attached if the GPRS GSMintegrity algorithm is known and supported in the network, and if the stored GPRS ciphering key sequence number and the one given from the MS are equal. Upon GPRS attach, if ciphering is to be used, an AUTHENTICATION AND CIPHERING REQUEST message shall be sent to the MS to start ciphering. In A/Gb mode, upon GPRS attach, if the MS and network supports integrity protection, then the network may choose to start ciphering with the stored GPRS GSM ciphering key or GPRS GSM Kc128 (under the restrictions given in 3GPP TS 42.009[ Security aspects ] [5]) if the stored GPRS ciphering key sequence number and the one given from the MS in the ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message are equal and the previously negotiated ciphering algorithm is known and supported in the network, without initiating a authentication and ciphering procedure. If the GPRS ciphering key sequence number stored in the network does not match the GPRS ciphering key sequence number received from the MS in the ATTACH REQUEST message, then the network should authenticate the MS. In A/Gb mode, the MS starts ciphering after sending the AUTHENTICATION AND CIPHERING RESPONSE message. The network starts ciphering when a valid AUTHENTICATION AND CIPHERING RESPONSE is received from the MS. In Iu mode, the MS starts ciphering and integrity checking according to the conditions specified in specification 3GPP TS 25.331[ None ] [23c]. In A/Gb mode, as an option, the network may decide to continue ciphering without sending an AUTHENTICATION AND CIPHERING REQUEST message after receiving a ROUTING AREA UPDATE REQUEST message with a valid GPRS ciphering key sequence number. Both the MS and the network shall use the latest ciphering parameters. The network starts ciphering when sending the ciphered ROUTING AREA UPDATE ACCEPT message to the MS. The MS starts ciphering after receiving a valid ciphered ROUTING AREA UPDATE ACCEPT message from the network. NOTE 2: In some specifications the term KSI (Key Set Identifier) is used instead of the term GPRS ciphering key sequence number. | 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.7.7.4 |
3,972 | 9.5.4 Activate Secondary PDP Context Request | This message is sent by the MS to the network to request activation of an additional PDP context associated with the same PDP address and APN as an already active PDP context. See Table 9.5.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: activate SECONDARY PDP context REQUEST Significance: global Direction: MS to network Table 9.5.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : ACTIVATE SECONDARY PDP CONTEXT REQUEST 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.4 |
3,973 | 8.94 Additional Protocol Configuration Options (APCO) | The Additional Protocol Configuration Options (APCO) information element is used to exchange additional protocol configuration options between the TWAN/ePDG and the PGW. The Additional Protocol Configuration Options information element is specified in 3GPP TS 29.275[ Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3 ] [26] and its GTPv2 coding is shown in figure 8.94-1. Figure 8.94-1: Additional Protocol Configuration Options Octets (5 to m) of the Additional Protocol Configuration Options IE are encoded as specified in 3GPP TS 29.275[ Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3 ] [26]. | 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.94 |
3,974 | 5.3.5.6.6 Multicast MRB release | The UE shall: 1> for each mrb-Identity value included in the mrb-ToReleaseList that is part of the current UE configuration; or 1> for each mrb-Identity value that is to be released as the result of full configuration according to 5.3.5.11: 2> release the PDCP entity and the mrb-Identity; NOTE 1: The UE does not consider the message as erroneous if the mrb-ToReleaseList includes any mrb-Identity value that is not part of the current UE configuration. NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.6.6 |
3,975 | C.3 Elliptic Curve Integrated Encryption Scheme (ECIES) C.3.1 General | The use of ECIES for concealment of the SUPI shall adhere to the SECG specifications [29] and [30]. Processing on UE side and home network side are described in high level in clauses C.3.2 and C.3.3. When the SUPI is of type IMSI, the subscription identifier part of the IMSI (i.e., MSIN) that is used to construct the scheme-input shall be coded as hexadecimal digits using packed BCD coding where the order of digits within an octet is same as the order of MSIN digits specified in Figure 9.11.3.4.3a of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. If the MSIN is composed of an odd number of digits, then the bits 5 to 8 of final octet shall be coded as "1111". When the SUPI is of type network specific identifier, the subscription identifier part of the SUPI that is used to construct the scheme-input shall follow the encoding rules specified in Annex B.2.1.2 of TS 33.220[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) ] [28]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.3 |
3,976 | 13.3.2.2 Indirect communication | In indirect communication scenarios, the NF Service Producer and NF Service Consumer shall use implicit authentication by relying on authentication between NF Service Consumer and SCP, and between SCP and NF Service Producer, provided by the transport layer protection solution, NDS/IP, or physical security. NOTE 0: Mutual authentication between NF Service Consumer and NF Service Producer is not achieved with hop-by-hop security. If the PLMN uses token-based authorization as specified by clause 13.4.1.2 and the PLMN’s policy mandates that the NRF authenticates the NF Service Consumer before granting an access token, the access token indicates to the NF Service Producer that the NF Service Consumer has been authenticated by the NRF. If additional authentication of the NF Service Consumer is required, the NF Service Producer authenticates the NF Service Consumer at the application layer using CCA based authentication as specified in clause 13.3.8. The NF Service Consumer authentication based on CCA based authentication is optional to use, and based on operator policy. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.2.2 |
3,977 | 10.5.1.12 Core Network System Information (Iu mode only) | The purpose of the Core Network System Information is to provide the MS with actual parameter settings of system information parameters controlling MM and GMM functionality. The Core Network system information is included in specific information elements within some RRC messages sent to MS, see 3GPP TS 25.331[ None ] [23c]. NOTE: These IEs do not have an IEI or a length indicator, because these IEs are never present in any layer 3 messages, Hence these IEs do not conform to the general IE rules defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. | 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.1.12 |
3,978 | 4.3.12.3 Mobility and Access Restrictions for Emergency Services | When Emergency Services are supported and local regulation requires Emergency Sessions to be provided regardless of mobility or access restrictions, the Mobility Restrictions in clause 4.3.5.7, should not be applied to UEs receiving emergency services. When the E-RABs for emergency bearers are established, the ARP value for emergency bearer services indicates the usage for emergency services to the E-UTRAN. During handovers, the source E-UTRAN and source MME ignore any UE related restrictions during handover evaluation when there are active emergency bearers. E-UTRAN shall not initiate handover to GERAN PS domain. During handover to a CSG cell, if the UE is not a CSG member of target CSG cell and has emergency bearer services, the target eNodeB only accepts the emergency bearers and the target MME releases the non-emergency PDN connections that were not accepted by the target eNodeB as specified in clause 5.10.3. Such UEs behave as emergency attached. During Tracking Area Update procedures, including a TAU as part of a handover, the target MME ignores any mobility or access restrictions for UE with emergency bearer services where required by local regulation. Any non-emergency bearer services are deactivated, according to clause 5.10.3, by the target MME when not allowed by the subscription for the target location. Such UEs behave as emergency attached. To allow the emergency attached UE to get access to normal services after the emergency session has ended and when it has moved to a new area that is not stored by the UE as a forbidden area, the UE may explicitly detach and reattach to normal services without waiting for the emergency PDN connection deactivation by the PDN GW. This functionality applies to all mobility procedures. | 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.12.3 |
3,979 | 4.3.1.4.3 Attempted outgoing inter-frequency handovers – gap-assisted measurement | This measurement provides the number of attempted outgoing inter-frequency handovers, when measurement gaps are used [12]. CC. Transmission of the RRCConnectionReconfiguration message by the eNB/RN to UE triggering the handover, indicating the attempt of an outgoing inter-frequency handover when measurement gaps are used (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). A single integer value. HO.InterFreqMeasGapOutAtt EUtranCellFDD EUtranCellTDD Valid for packet switched traffic 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.3.1.4.3 |
3,980 | 27.2.2 Format of V2X Control Function FQDN | The V2X Control Function Fully Qualified Domain Name (V2X Control Function FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the V2X Control Function is located. The V2X Control Function FQDN is composed of six labels. The last two labels shall be "3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "v2xcontrolfunction.epc". The V2X Control Function FQDN shall be constructed as follows: "v2xcontrolfunction.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "v2xcontrolfunction.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" format of the V2X Control Function FQDN shall be: - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the V2X Control Function FQDN. As an example, the V2X Control Function FQDN for MCC 345 and MNC 12 is coded in the DNS as: "v2xcontrolfunction.epc.mnc012.mcc345.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 27.2.2 |
3,981 | 9.3.7.1 FDD | For the parameters specified in Table 9.3.7.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.7.1-2 and by the following. a) the ratio of the throughput obtained when transmitting based on UE PUSCH 3-2 reported wideband CQI and subband PMI and that obtained when transmitting based on PUSCH 3-1 reported wideband CQI and wideband PMI shall be ≥ b) The ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS based on UE PUSCH3-2 reported subband CQI and subband PMI and that obtained when transmitting on a randomly selected sub-band in set S based on PUSCH 1-2 reported wideband CQI and subband PMI shall be ≥ The transport block sizes TBS for wideband CQI and subband CQI are selected according to RC.17 FDD for test 1 and according to RC.18 FDD for test 2. Table 9.3.7.1-1 Sub-band test for FDD Table 9.3.7.1-2 Minimum requirement (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.3.7.1 |
3,982 | 5.3.3.6 Routing Area Update with MME interaction and with S-GW change | The Routing Area Update with S-GW change procedure takes place when a UE that is registered with an MME selects a UTRAN or GERAN cell and the S-GW is changed by the procedure. In this case, the UE changes to a Routing Area that the UE has not yet registered with the network. This procedure is initiated by an ECM-IDLE state UE and may also be initiated if the UE is in ECM-CONNECTED state. This RA update case is illustrated in Figure 5.3.3.6-1. NOTE 1: This procedure covers the MME to 2G or 3G SGSN RAU. Figure 5.3.3.6-1: Routing Area Update with MME interaction and with S-GW change NOTE 2: 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 8 and 10 concern GTP based S5/S8 1. The UE selects a UTRAN or GERAN cell. This cell is in a Routing Area that the UE not yet registered with the network or the UE reselects a UTRAN or GERAN cell and the TIN indicates "GUTI". The UE in ECM-CONNECTED state may change to the GERAN cell through Network Assisted Cell Change (NACC). 2a. The UE sends a Routing Area Update Request (old RAI, old P-TMSI, P-TMSI Type, UE Core Network Capability, MS Network Capability, P-TMSI Signature, additional P-TMSI/RAI, KSI, Voice domain preference and UE's usage setting) message to the new SGSN. The UE shall set the P-TMSI Type to indicate whether the P-TMSI is a native P-TMSI or is mapped from a GUTI. If the UE's TIN indicates "GUTI" and the UE holds a valid GUTI then the UE indicates the GUTI as the old P-TMSI and old RAI. If the UE's TIN indicates "P-TMSI" or "RAT-related TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are indicated as old P-TMSI and old RAI. Mapping a GUTI to a P-TMSI and an RAI is specified in TS 23.003[ Numbering, addressing and identification ] [9]. If the UE holds a valid P-TMSI and related RAI and the old P-TMSI and old RAI indicate a P-TMSI/RAI mapped from a GUTI, then the UE indicates these parameters as additional P-TMSI/RAI. The old P-TMSI is indicated in the RAU Request message for Iu-mode only. For Gb mode the TLLI is derived from the value that is determined as the old P-TMSI according to the rules above. The routing parameter that is signalled in the RRC signalling to the RNC for routing to the SGSN is derived from the identifier that is signalled as the old P-TMSI according to the rules above. For a combined MME/SGSN the RAN is configured to route the NRI(s) of this combined node to the same combined node. The RAN is also configured to route NRI(s) of P-TMSIs that are generated by the UE's mapping of the GUTIs allocated by the combined node. Such a RAN configuration may also be used for separate nodes to avoid changing nodes in the pool caused by inter RAT mobility. If the UE has a follow-on request, i.e. if there is pending uplink traffic (signalling or data), the 3G-SGSN may use, as an implementation option, the follow-on request indication to release or keep the Iu connection after the completion of the RA update procedure. KSI is mapped from an eKSI identifying a KASME if the UE indicates a P-TMSI mapped from GUTI in the information element "old P-TMSI". KSI identifies a (CK, IK) pair if the UE indicates a P-TMSI in the information element "old P-TMSI". The UE sets the voice domain preference and UE's usage setting according to its configuration, as described in clause 4.3.5.9. 2b. The RNC shall add the Routing Area Identity, CSG access mode, CSG ID before forwarding the message to the SGSN. This RA identity corresponds to the RAI in the MM system information sent by the RNC to the UE. The BSS shall add the Cell Global Identity (CGI) of the cell where the UE is located before passing the message to the new SGSN. CSG ID is provided by RAN if the UE sends the RAU Request message via a CSG cell or a hybrid cell. CSG access mode is provided if the UE sends the RAU Request message via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the SGSN shall consider the cell as a CSG cell. For SIPTO at the Local Network the with stand-alone GW architecture the RNC includes the Local Home Network ID in the Initial UE Message and in Direct Transfer message if the target cell is in a Local Home Network. 3. The new S4 SGSN determines the type of the old node, i.e. MME or SGSN, as specified in clause 4.3.19, uses the old RAI received from the UE to derive the old MME address, and the new S4 SGSN sends a Context Request (P-TMSI, old RAI, New SGSN Address, P-TMSI Signature) message to the old MME to get the context for the UE. To validate the Context Request the old MME uses a NAS token mapped from the P-TMSI Signature. If the UE is not known in the old MME, the old MME responds with an appropriate error cause. If integrity check fails in the old MME, the old MME responds with an appropriate error cause which should initiate the security functions in the new S4 SGSN. If the security functions authenticate the UE correctly, the new S4 SGSN shall send a Context Request (IMSI, old RAI, New SGSN Address, UE Validated) message to the old MME. UE Validated indicates that the new S4 SGSN has authenticated the UE. If the new S4 SGSN indicates that it has authenticated the UE or if the old MME authenticates the UE, the old MME starts a timer. If the UE with emergency bearers is not authenticated in the old MME (in a network supporting unauthenticated UEs) the old MME continues the procedure with sending a Context Response and starting the timer also when it cannot validate the Context Request. 4. The old MME responds with a Context Response (MM Context, EPS Bearer Contexts, Serving GW signalling Address and TEID(s), MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone and ISR Supported) message. The MM context contains security related information as well as other parameters (including IMSI) as described in clause 5.7.2 (Information Storage for MME). The PDN GW Address and TEID(s) (for GTP-based S5/S8) or GRE Keys (PMIP-based S5/S8) for uplink traffic and control plane, and the TI(s) is part of the EPS Bearer context(s). The unused Authentication Quintets in the MM Context may be sent if stored by the MME and if the MME received the unused Authentication Quintets from the same SGSN previously. If the UE receives only emergency bearer services from the old MME and the UE is UICCless, IMSI can not be included in the Context Response. 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. ISR Supported is indicated if the old MME and associated Serving GW are capable to activate ISR for the UE. The new SGSN shall ignore the UE Core Network Capability in the MM Context of the Context Response only when it has previously received an UE Core Network Capability in the Routing Area Request. If UE is not known in the old MME, the old MME responds with a appropriate error cause. The new SGSN maps the EPS bearers to PDP contexts 1-to-1 and maps the EPS Bearer QoS parameter values of an EPS bearer to the Release 99 QoS parameter values of a bearer context as defined in Annex E. The PDP context(s) are established in the indicated order. The SGSN deactivates the PDP contexts which cannot be established. If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW, the old MME shall include the Local Home Network ID of the old cell in the EPS Bearer context corresponding to the SIPTO at the Local Network PDN connection. If the UE uses power saving functions and the DL Data Buffer Expiration Time for the UE has not expired (see High latency communication in clause 4.3.17.7), the old MME indicates Buffered DL Data Waiting in the Context Response. When this is indicated, the new SGSN shall invoke data forwarding (corresponding to clause 5.3.3.1A) and setup the user plane in conjunction to the RAU procedure for delivery of the buffered DL data to the UE. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS Bearer Context(s) included in the Context Response message. The old MME only transfers the EPS Bearer Context(s) that the new SGSN supports. If not supported, EPS Bearer Context(s) of non-IP PDN connection are not transferred to the new SGSN. EPS Bearer Context(s) of Ethernet PDN connection type are not transferred to the new SGSN. If the EPS Bearer Context(s) of a PDN connection has not been transferred, the old MME shall consider all bearers of that PDN connection as failed and release that PDN connection by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. 5. Security functions may be executed. Procedures are defined in clause 5.3.10 on "Security Function". For ongoing emergency services only, if the new SGSN is configured to support emergency bearer services in limited service state, it may skip the authentication procedure or proceed even if authentication fails. If the new SGSN does not support emergency bearer services in limited service state, then it rejects the RAU request with an appropriate reject cause. 6. If the new SGSN identifies that the RAT type has changed, the SGSN checks the subscription information to identify for each APN whether to maintain the PDN connection, disconnect the PDN connection with a reactivation request or disconnect PDN connection without reactivation request. If the SGSN decides to deactive a PDN connection it performs SGSN-initiated PDN Connection Deactivation procedure after tracking area procedure is completed. Existing SM cause values as specified in TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47] (e.g. #39, "reactivation requested"; #66 "Requested APN not supported in current RAT and PLMN combination"; and for a dedicated bearer, possibly #37 "QoS not accepted") are used to cause predictable UE behaviour. The new SGSN determines to relocate the Serving GW. The Serving GW is relocated when the old Serving GW cannot continue to serve the UE. The new SGSN may also decide to relocate the Serving GW if a new Serving GW is expected to serve the UE longer and/or with a more optimal UE to PDN GW path, or if a new Serving GW can be co-located with the PDN GW. Selection of a new Serving GW is performed according to clause 4.3.8.2 on "Serving GW selection function". The new SGSN sends a Context Acknowledge (Serving GW change indication) message to the old MME. Serving GW change indication indicates a new Serving GW has been selected. The old MME marks in its context that the information in the GWs is invalid. This ensures that the old MME updates the GWs if the UE initiates a TAU procedure back to the old MME before completing the ongoing RAU procedure. NOTE 3: Updating the GWs refers to deletion of session(s) on the Serving GW followed by re-creation of session(s) on the Serving GW. The re-creation of session(s) on the Serving GW will result in successful re-establishment of the S5/S8 tunnel between the selected Serving GW and the PDN GW. The old MME deletes all bearer resources of the UE when the timer started in step 3 expires. If the security functions do not authenticate the UE correctly, then the RAU is rejected, and the new S4 SGSN sends a reject indication to the old MME. The MME shall continue as if the Identification and Context Request was never received. For UE using CIoT EPS Optimisation without any activated PDN connection, the steps 7, 8, 9, 10, 11, 16 and 17 are skipped. 7. In this procedure flow the Serving GW is relocated. The SGSN sends a Create Session Request (IMSI, bearer contexts, SGSN Address and TEID for the control plane, RAT Type, Type, the Protocol Type over S5/S8, Serving Network, UE Time Zone, etc) message per PDN connection to the selected new Serving GW. The PDN GW address is indicated in the bearer contexts. Type indicates to the Serving GW to send the Modify Bearer Request to the PDN GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. RAT type indicates a change in radio access. As it is a mobility from E-UTRAN, if the target SGSN supports location information change reporting, the target SGSN shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information, the SGSN also includes the User CSG Information IE in this message. 8. The new Serving GW sends the message Modify Bearer Request (Serving GW Address, Serving GW TEID, RAT type, Serving Network) per PDN connection to the PDN GW concerned. User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE are also included if they are present in step 7. 9. If dynamic PCC is deployed, and RAT type information or UE location information or UE Time Zone needs to be conveyed from the PDN GW to the PCRF, then the PDN GW shall send this information to the PCRF by means of an IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 4: The PDN GW does not need to wait for the PCRF response, but continues in the next step. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure. 10. The PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target SGSN, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. 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. If the source Serving GW has no downlink user plane established, the Serving GW shall discard the "end marker" received from the PDN GW and shall not send Downlink Data Notification. Otherwise the Serving GW shall forward the "end marker" packets to the source eNodeB. 11. The new Serving GW updates its bearer context. This allows the Serving GW to route Bearer PDUs to the PDN GW when received from RNC. The new Serving GW returns a Create Session Response (Serving GW address and TEID, PDN GW Address and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8, MS Info Change Reporting Action) at the PDN GW(s) for uplink traffic) message to the SGSN. When the SGSN receives the Create Session Response message, the SGSN checks if there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the SGSN and in such a case sends an event notification (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). 12. The new SGSN verifies whether it holds subscription data for the UE identified by the P-TMSI, the additional P-TMSI/RAI or by the IMSI received with the context data from the old CN node. The additional P-TMSI/RAI allows the new SGSN to find any already existing UE context stored in the new SGSN. If there are no subscription data in the new SGSN for this UE, or for some network sharing scenario (e.g. GWCN) if the PLMN-ID of the RAI supplied by the RNC is different from that of the RAI in the UE's context, then the new SGSN informs the HSS of the change of SGSN by sending an Update Location (SGSN Number, SGSN Address, IMSI, Homogenous Support of IMS Voice over PS Session, UE SRVCC capability, equivalent PLMN list) message to the HSS. For "Homogenous Support of IMS Voice over PS Sessions", see clause 5.3.8A of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. The inclusion of the equivalent PLMN list indicates that the SGSN supports the inter-PLMN handover to a CSG cell in an equivalent PLMN using the subscription information of the target PLMN. If the UE initiates the RAU procedure in a VPLMN supporting Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN (via Service Level Agreement) and the SGSN needs to retrieve the CSG subscription information of the UE from the CSS, the SGSN initiates the Update CSG Location Procedure with CSS as described in clause 5.3.12. 13. The HSS sends a Cancel Location (IMSI, Cancellation Type) message to the old SGSN with the Cancellation Type set to Update Procedure. When receiving the Cancel Location message the old SGSN removes all the UE contexts. The old SGSN acknowledges with a Cancel Location Ack (IMSI) message. 14. When receiving the Context Acknowledge message from the new S4 SGSN and if the old MME has an S1-MME association for the UE, the source MME sends a S1-U Release Command to the source eNodeB after the timer started in step3 has expired. The RRC connection is released by the source eNodeB. The source eNodeB confirms the release of the RRC connection and of the S1-U connection by sending a S1-U Release Complete message to the source MME. 15. The HSS acknowledges the Update Location message by sending an Update Location Ack (IMSI, Subscription Data) to the new SGSN. If the Update Location is rejected by the HSS, the new SGSN rejects the RAU Request from the UE with an appropriate cause. In such cases, the SGSN releases any local SGSN EPS Bearer contexts for this particular UE, and additionally deletes the EPS bearer resources in the new Serving GW by sending the Delete Session Request (Cause, Operation Indication) messages to the new Serving GW. The Operation Indication flag shall not be set. Therefore, the new Serving GW receiving this request shall not initiate a delete procedure towards the PDN GW. The new SGSN validates the UE's presence in the (new) RA. If due to regional subscription restrictions or access restrictions (e.g. CSG restrictions) the UE is not allowed to be attached in the RA, the SGSN rejects the Routing Area Update Request with an appropriate cause to the UE and notifies the HSS of the rejection. The Subscription Data may contain the CSG subscription data for the registered PLMN and for the equivalent PLMN list requested by SGSN in step 12. If the UE initiates the RAU procedure at a CSG cell, the new S4 SGSN shall check whether the CSG ID and associated PLMN is contained in the CSG subscription and is not expired. If the CSG ID and associated PLMN is not present or expired, the S4 SGSN shall send a RAU reject message to the UE with an appropriate cause value. The UE shall remove the CSG ID and associated PLMN from its Allowed CSG list if present. 16. When the timer started in step 3 expires and the old MME received the Serving GW change indication in the Context Acknowledge message, the old MME deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the old Serving GW. The operation Indication flag is not set, that indicates to the old Serving GW that the old Serving GW shall not initiate a delete procedure towards the PDN GW. If ISR is activated the cause indicates to the old S-GW that the old S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 17. The old Serving GW acknowledges with Delete Session Response (Cause) messages. The old Serving GW discards any packets buffered for the UE. 18. If due to regional subscription restrictions or access restrictions the UE is not allowed to access the RA: - For UEs with ongoing emergency bearer services, the new SGSN accept the Routing Area Update Request and deactivates the non-emergency PDP contexts as specified in clause 9.2.4.2 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If the Routing Area Update procedure is initiated in PMM-IDLE/STANDBY state, all non-emergency PDP Contexts are deactivated by the Routing Area Update procedure without PDP Context deactivation signalling between the UE and the SGSN. - For all other cases, the new SGSN rejects Routing Area Update Request with an appropriate cause to the UE and notifies the HSS of rejection (details of this notification is specified in stage 3). The new SGSN responds to the UE with a Routing Area Update Accept (P-TMSI, P-TMSI Signature, Emergency Service Support indicator, PDP context status) message. The Emergency Service Support indicator informs the UE that Emergency bearer services are supported over UTRAN. For an S-GW change ISR Activated is never indicated by the SGSN to the UE as it needs a TAU with the same S-GW first to activate ISR. For an SGSN change ISR is not activated by the new SGSN to avoid context transfer procedures with two old CN nodes. When receiving the RAU Accept message, as there is no ISR Activated indication, the UE shall set its TIN to "P-TMSI". In Iu mode, if after step 7 the new SGSN receives a Downlink Data Notification message or any other downlink signalling message while the UE is still connected, the new SGSN may prolong the PS signalling connection with the UE. If there is DL data buffered for a UE using power saving functions (i.e. the DL Data Buffer Expiration Time in the MM context for the UE in the SGSN has not expired), the user plane setup is performed in conjunction with the RAU Accept message. If the RAU procedure is initiated by manual CSG selection and occurs via a CSG cell, the UE upon receiving the RAU Accept message shall add the CSG ID and associated PLMN to its Allowed CSG list if it is not already present. Manual CSG selection is not supported if the UE has emergency bearers established. With the PDP context status information, the UE shall deactivate all those bearers contexts locally which are active in the UE, but are indicated by the SGSN as being inactive. If the user plane setup is performed in conjunction with the RAU Accept message and the RAU is performed via a hybrid cell, then the SGSN shall send an indication whether the UE is a CSG member to the RAN along with the RANAP message. Based on this information, the RAN may perform differentiated treatment for CSG and non-CSG members. NOTE 5: If the UE receives a RAU Accept message via a hybrid cell, the UE does not add the corresponding CSG ID and associated PLMN to its Allowed CSG list. Adding a CSG ID and associated PLMN to the UE's local Allowed CSG list for a hybrid cell is performed only by OTA or OMA DM procedures. NOTE 6: When ISR Activated is indicated and the UE's TIN indicates "P-TMSI" the TIN is not changed. When ISR Activated is indicated and the UE's TIN indicates "GUTI" or "RAT-related TMSI" the UE shall set its TIN to "RAT-related TMSI". 19. If the P-TMSI was included in the RAU Accept message, the UE acknowledges the new P-TMSI by returning a Routing Area Update Complete message to the SGSN. 20. For Iu-mode, if the UE has uplink data or signalling pending it shall send a Service Request (P-TMSI, CKSN, Service Type) message to the new SGSN. If a P-TMSI was allocated in step 18, that P-TMSI is the one included in this message. Service Type specifies the requested service. Service Type shall indicate one of the following: Data or Signalling. 21. If the UE has sent the Service Request, the new 3G SGSN requests the RNC to establish a radio access bearer by sending a RAB Assignment Request (RAB ID(s), QoS Profile(s), GTP SNDs, GTP SNUs, PDCP SNUs) message to the RNC. If Direct Tunnel is established the SGSN provides to the RNC the Serving GW's Address for User Plane and TEID for uplink data. 22. If the SGSN established Direct Tunnel in step 21) it shall send Modify Bearer Request to the Serving GW and include the RNC's Address for User Plane and downlink TEID for data. The Serving GW updates the Address for User Plane and TEID for downlink data and return a Modify Bearer Response. NOTE 7: EPS does not support any CAMEL procedures. In the case of a rejected routing area update operation, due to regional subscription, roaming restrictions, access restrictions (see TS 23.221[ Architectural requirements ] [27] and TS 23.008[ Organization of subscriber data ] [28]) or because the SGSN cannot determine the HLR address to establish the locating updating dialogue, the new SGSN should not construct an MM context. In the case of receiving the subscriber data from HLR, the new SGSN may construct an MM context and store the subscriber data for the UE to optimise signalling between the SGSN and the HSS. A reject shall be returned to the UE with an appropriate cause and the PS signalling connection shall be released. Upon return to idle, the UE shall act according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. If the new SGSN is unable to update the bearer context in one or more P-GWs, the new SGSN shall deactivate the corresponding bearer contexts as described in clause "SGSN-initiated PDP Context Deactivation Procedure" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. This shall not cause the SGSN to reject the routing area update. The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each bearer context in the Context Response message and then store the new Maximum APN restriction value. The PDP contexts shall be prioritized by the new SGSN. If the new SGSN is unable to support the same number of active PDP contexts as received from old MME, the prioritisation is used to decide which PDP contexts to maintain active and which ones to delete. In any case, the new SGSN shall first update all PDP contexts in one or more P-GWs and then deactivate the PDP context(s) that it cannot maintain as described in clause "SGSN-initiated PDP Context Deactivation Procedure" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. This shall not cause the SGSN to reject the routing area update. If the routing area update procedure fails a maximum allowable number of times, or if the SGSN returns a Routing Area Update Reject (Cause) message, the MS shall enter IDLE state. | 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.3.6 |
3,983 | 10.5.2 Composition of the IFPSI | No more than 15 digits <------------------------------> 3d 3d | <-----><-----><------//--------> +-----++-----++------//--------+ | || || | +---++---++---//----+ MCC CON FPIN | NFPSI <------------------------> IFPSI <> Figure 18: Structure of IFPSI The IFPSI is composed of the following elements (each element shall consist of decimal digits only): - Mobile Country Code (MCC) consisting of three digits. The MCC identifies the country of the CTS-FP subscriber (e.g. 208 for France); - CTS Operator Number (CON). Its length is three digits; - Fixed Part Identification Number (FPIN) identifying the CTS-FP subscriber. The National Fixed Part Subscriber Identity (NFPSI) consists of the CTS Operator Number and the Fixed Part Identification Number. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10.5.2 |
3,984 | 6.5.2 Transmit modulation quality | Transmit modulation quality defines the modulation quality for expected in-channel RF transmissions from the UE. The transmit modulation quality is specified in terms of: - Error Vector Magnitude (EVM) for the allocated resource blocks (RBs) - EVM equalizer spectrum flatness derived from the equalizer coefficients generated by the EVM measurement process - Carrier leakage - In-band emissions for the non-allocated RB All the parameters defined in subclause 6.5.2 are defined using the measurement methodology specified in Annex F. | 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 | 6.5.2 |
3,985 | I.2.2 EAP framework, selection of authentication method, and EAP method credentials I.2.2.1 General | The EAP authentication framework is supported by the 5GS as described in clause 6.1.1.2. The UE and the SNPN may support 5G AKA, EAP-AKA', or any other key-generating EAP authentication method. Selection of the authentication methods is dependent on NPN configuration. NOTE 1: For EAP-AKA' (as well as 5G AKA), the selection is described in clause 6.1.2. For authentication, that is not using EAP-AKA' (or 5G AKA), the selection is NPN operator deployment specific and out of scope of this specification. When an EAP authentication method other than EAP-AKA' is selected, the chosen method determines the credentials needed in the UE and network. These credentials, called the EAP-method credentials, shall be used for authentication. NOTE 2: How credentials for EAP methods other than EAP-AKA' are stored and processed within the UE is out of the scope for standalone non-public networks. NOTE 3: Storage and processing of credentials for EAP-AKA' (as well as 5G AKA) is described in clause 6 of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.2 |
3,986 | 12.3.5.1 Definition 12.3.5.1.1 General description | Within a message, one or multiple instances of the Overload Control Information (OCI) IE may be included by the same GTP-C entity. Each instance shall provide information about the overload condition to allow the receiver to apply mitigation actions which will result in an efficient alleviation of the overload condition at the sender. The GTP-C entity shall always include the full set of overload control information, i.e. all the node level and/or APN level applicable instances of the OCI IE, when signalling overload control information in a message for the first time or subsequently towards the receiver, even when only a subset of the overload control information has changed. All the instances of the OCI IE provided by a given GTP-C entity in a message shall contain the same Overload Control Sequence Number. The Overload Control Sequence Number shall be incremented whenever the overload control information is modified (see clause 12.3.5.1.2.1). When including overload control information for some APN(s), the PGW should not provide any node level Overload Control Information unless the node level information is also applicable. The receiver shall overwrite any stored overload control information of a peer with the newly received overload control information (received via one or multiple instances of OCI IE) from the same GTP-C peer entity, if the new information is more recent than the old information as indicated by the Overload Control Sequence Number, e.g. if the receiver has stored 'X' instances of the OCI IE for a peer GTP-C entity, it shall overwrite those 'X' instances with the new set of 'Y' instances received in a message from the same GTP-C peer entity, where X, Y are any integer numbers. The receiver shall consider all the parameters received in the same instance of the OCI IE in conjunction while applying the overload mitigation action. When more than one instance of the OCI IE is included, the receiver shall consider the parameters included in each instance independently, while applying the overload mitigation action. The parameters are further described in clauses 12.3.5.1.2 and 12.3.5.1.3. Overload control information may be extended with new parameters in future versions of the specification. Any new parameter will have to be categorized as: - Non-critical optional parameters: the support of these parameters is not critical for the receiver. The receiver can successfully and correctly comprehend the Overload Control Information instance, containing one or more of these parameters, by using the other parameters and ignoring the non-critical optional parameters. - Critical optional parameters: the support of these parameters is critical for the receiver to correctly comprehend the instance of the Overload Control Information containing one or more of these parameters. The sender may include one or more non-critical optional parameter(s) within any instance of Overload Control Information, without having the knowledge of the receiver's capability to support the same. However, the sender shall only include one or more critical optional parameter(s) in any instance of Overload Control Information towards a receiver, if the corresponding receiver is known to support these parameter(s). The sender may be aware of this either via signalling methods or by configuration; this will have to be defined when introducing any such new parameter in the future. Each instance of the OCI shall be associated by default to the GTP-C entity corresponding to the peer node's IP address of the PDN connection, over which the OCI IE is received, i.e. to the IP address received within the "Sender F-TEID for control plane" IE, the "PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface" IE or within the "MME/S4-SGSN Identifier" IE. Alternatively, the GW (i.e. SGW and PGW) nodes may send Overload Control Information which is associated with the GW node's identity, i.e. the FQDN or IP address of the GW node received from the HSS (for a PGW) or the DNS (for an SGW or PGW), the identity determined during the GW selection. In that case, the GW node shall provide an explicit indication that the OCI IE included in the message belongs to the GW node's identity. | 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.3.5.1 |
3,987 | 5.38.6 Paging Timing Collision Control | To avoid possible paging occasion collision and to enhance the likelihood that paging is received successfully for different USIMs, a Multi-USIM UE may need a new 5G-GUTI to modify the timing of the Paging Occasions (POs) for a USIM when the USIM's registration is not emergency registration. When a Multi-USIM UE needs a 5G-GUTI assignment, it performs a Mobility Registration Update without any specific indication (i.e. it is using a normal Registration procedure). This triggers the AMF to allocate a new 5G-GUTI and provide it to the Multi-USIM UE in the Registration Accept message. NOTE: It is recommended to avoid excessive signalling load from UE due to this procedure. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.38.6 |
3,988 | 4.3.7.4.1a Throttling of Downlink Data Notification Requests | Under unusual circumstances (e.g. when the MME load exceeds an operator configured threshold), the MME may restrict the signalling load that its SGWs are generating on it, if configured to do so. The MME can reject Downlink Data Notification requests for non-priority traffic for UEs in idle mode or to further offload the MME, the MME can request the SGWs to selectively reduce the number of Downlink Data Notification requests it sends for downlink non-priority traffic received for UEs in idle mode according to a throttling factor and for a throttling delay specified in the Downlink Data Notification Ack message. The SGW determines whether a bearer is to be subjected to the throttling of Downlink Data Notification Requests on the basis of the bearer's ARP priority level and operator policy (i.e. operator's configuration in the SGW of the ARP priority levels to be considered as priority or non- priority traffic). While throttling, the SGW shall throttle the Downlink Data Notification Requests for low and normal priority bearers by their priority. The MME determines whether a Downlink Data Notification request is priority or non-priority traffic on the basis of the ARP priority level that was received from the SGW and operator policy. If ISR is not active for the UE, during the throttling delay, the SGW drops downlink packets received on all its non-priority bearers for UEs known as not user plane connected (i.e. the SGW context data indicates no downlink user plane TEID) served by that MME in proportion to the throttling factor, and sends a Downlink Data Notification message to the MME only for the non throttled bearers. If ISR is active for the UE, during the throttling delay, the SGW does not send DDN to the MME and only sends the DDN to the SGSN. If both MME and SGSN are requesting load reduction, the SGW drops downlink packets received on all its non-priority bearers for UEs known as not user plane connected (i.e. the SGW context data indicates no downlink user plane TEID) in proportion to the throttling factors. The SGW resumes normal operations at the expiry of the throttling delay. The last received value of the throttling factor and throttling delay supersedes any previous values received from that MME. The reception of a throttling delay restarts the SGW timer associated with that MME. | 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.7.4.1a |
3,989 | 5.31.14.3 Small Data Rate Control | The (H-)SMF may consider, e.g. based on operator policy, subscription, DNN, S-NSSAI, RAT type etc. to determine whether to apply Small Data Rate Control or not. The (H-)SMF can send a Small Data Uplink Rate Control command to the UE using the PCO information element. The (H-)SMF informs the UPF or NEF of any Small Data Rate Control that shall be enforced. The Small Data Rate Control applies to data PDUs sent on that PDU Session by either Data Radio Bearers or Signalling Radio Bearers (NAS Data PDUs). The rate control information is separate for uplink and downlink and in the form of: - an integer 'number of packets per time unit', and - an integer 'number of additional allowed exception report packets per time unit' once the rate control limit has been reached. The UE shall comply with this uplink rate control instruction. If the UE exceeds the uplink 'number of packets per time unit', the UE may still send uplink exception reports if allowed and the 'number of additional allowed exception reports per time unit' has not been exceeded. The UE shall consider this rate control instruction as valid until it receives a new one from (H-)SMF. When a PDU Session is first established, the (H-)SMF may provide the configured Small Data Rate Control parameters to the UE and UPF or NEF. When the PDU Session is released, the Small Data Rate Control Status (including the number of packets still allowed in the given time unit, the number of additional exception reports still allowed in the given time unit and the termination time of the current Small Data Rate Control validity period) may be stored in the AMF so that it can be retrieved for a subsequent re-establishment of a new PDU Session. At subsequent establishment of a new PDU Session, the (H-)SMF may receive the previously stored Small Data Rate Control Status and if the validity period has not expired, it provides the parameters to the UE in the PCO and to the UPF/NEF as the initially applied parameters, in addition to the configured Small Data Rate Control parameters. If the initially applied parameters are provided, the UE and UPF or NEF shall apply them and shall use the SMF provided configured Small Data Rate Control parameters once the initially applied Small Data Rate Control validity period expires. NOTE 1: Storage of Small Data Rate Control Status information for very long time intervals can be implementation specific. For the UPF and NEF, Small Data Rate Control is based on a 'maximum allowed rate' per direction. If (H-)SMF provided the 'number of additional allowed exception report packets per time unit', then the 'maximum allowed rate' is equal to the 'number of packets per time unit' plus the 'number of additional allowed exception report packets per time unit', otherwise the 'maximum allowed rate' is equal to the 'number of packets per time unit'. The UPF or NEF may enforce the uplink rate by discarding or delaying packets that exceed the 'maximum allowed rate'. The UPF or NEF shall enforce the downlink rate by discarding or delaying packets that exceed the downlink part of the 'maximum allowed rate'. NOTE 2: It is assumed that the Serving PLMN Rate is sufficiently high to not interfere with the Small Data Rate Control as the Small Data Rate Control, if used, is assumed to allow fewer messages. NAS PDUs related to exception reports are not subject to the Serving PLMN Rate Control. For NB-IoT the AMF maintains an "MO Exception Data Counter" which is incremented when the RRC establishment cause "MO exception data" is received from NG-RAN. The AMF reports whether the UE accessed using "MO exception data" RRC establishment cause, to all (H-)SMFs which have PDU Sessions that are subject to Small Data Rate Control and if the UE is accessing using "MO exception data" then the "MO Exception Data Counter" is also provided by the AMF. The SMF indicates each use of the RRC establishment cause "MO Exception Data" by including the related counter on the charging information. NOTE 3: Since Exception Data PDUs and normal priority PDUs cannot be distinguished within an RRC connection, the AMF is only counting the number of RRC Connection establishments with "MO Exception data" priority. If the UE moves to EPC then the UE and the PGW-U+UPF store the current Small Data Rate Control Status for all PDU Sessions that are not released. If the UE moves back to 5GC the stored Small Data Rate Control Status is restored and continues to apply to PDU Session(s) that are moved from EPC to 5GC, taking into account remaining validity period of the stored Small Data Rate Control Status. When the UE moves to EPC the Small Data Rate Control Status for all PDU Session(s) may also be stored in the AMF if the PDU Session is released while the UE is connected to EPC and re-established when the UE moves to 5GC. The time to store the Small Data Rate Control Status information is implementation specific. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.14.3 |
3,990 | 5.8.9.5 Actions related to PC5-RRC connection release requested by upper layers | The UE initiates the procedure when upper layers request the release of the PC5-RRC connection as specified in TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57] or TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72]. The UE shall not initiate the procedure for power saving purposes. The UE shall: 1> if the PC5-RRC connection release for the specific destination is requested by upper layers: 2> discard the NR sidelink communication related configuration of this destination; 2> release the DRBs of this destination if configured, in according to clause 5.8.9.1a.1; 2> release the SRBs of this destination, in according to clause 5.8.9.1a.3; 2> release the PC5 Relay RLC channels if configured, in according to clause 5.8.9.7.1; 2> reset the sidelink specific MAC of this destination. 2> consider the PC5-RRC connection is released for the destination; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.5 |
3,991 | 17.3 MBMS session start / update/ stop | The MBMS session start shall be used by the BM-SC to trigger the bearer resource establishment and announce the arrival of data for a MBMS bearer service (along with the attributes of the data to be delivered e.g. QoS or MBMS service area) to every GGSN that will deliver the MBMS bearer service. The MBMS session start shall also be used by the BM-SC to indicate to GGSN if IP multicast mechanism should be used for user plane data distribution to UTRAN. The MBMS session update shall be used by the BM-SC to trigger the update of MBMS session attributes in the affected GGSNs. The MBMS session stop shall be used by the BM-SC to indicate the end of the data stream for an MBMS bearer service to every GGSN that has been delivering the MBMS bearer service. | 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 | 17.3 |
3,992 | 5.1.2 Types of 5GMM procedures | Depending on how they can be initiated, three types of 5GMM procedures can be distinguished: a) 5GMM common procedures: 5GMM common procedure can always be initiated when the UE is in 5GMM-CONNECTED mode. The procedures belonging to this type are: 1) Initiated by the network: i) network-initiated NAS transport; ii) primary authentication and key agreement; iii) security mode control; iv) generic UE configuration update; v) identification; and vi) network slice-specific authentication and authorization; 2) Initiated by the UE: UE-initiated NAS transport. 3) Initiated by the UE or the network and used to report certain error conditions detected upon receipt of 5GMM protocol data: 5GMM status. b) 5GMM specific procedures: At any time only one UE initiated 5GMM specific procedure can be running for each of the access network(s) that the UE is camping in. The procedures belonging to this type are: 1) Initiated by the UE and used e.g. to register to the network for 5GS services and establish a 5GMM context, to update the location/parameter(s) of the UE: registration. 2) Initiated by the UE or the network and used to deregister from the network for 5GS services and to release a 5GMM context: de-registration. 3) Initiated by the UE and used to deregister from the network for 5GS services and to release a 5GMM context: eCall inactivity procedure. c) 5GMM connection management procedures: 1) Initiated by the UE and used to establish a secure connection to the network or to request the resource reservation for sending data, or both: service request. The service request procedure can only be initiated if no UE initiated 5GMM specific procedure is ongoing for each of the access network(s) that the UE is camping in. 2) Initiated by the network and used to request the establishment of an N1 NAS signalling connection or to request re-establishment of user-plane resources for the PDU session(s) associated with 3GPP access or to request re-establishment of user-plane resources of the PDU session(s) associated with non-3GPP access over 3GPP access; not applicable for the non-3GPP access network: paging. 3) Initiated by the network and used to request re-establishment of user-plane resources of the PDU session(s) associated with non-3GPP access over 3GPP access or to deliver 5GSM downlink signalling messages associated with non-3GPP access over 3GPP access, when the UE is in 5GMM-CONNECTED mode over 3GPP access and in 5GMM-IDLE mode over non-3GPP access; or Initiated by the network and used to request re-establishment of user-plane resources of the PDU session(s) associated with 3GPP access over 3GPP access or to deliver downlink signalling associated with 3GPP access over 3GPP access, when the UE is in 5GMM-CONNECTED mode over non-3GPP access, and when the UE is in 5GMM-IDLE mode over 3GPP access and not in MICO mode: notification. NOTE 1: In NB-N1 mode, the UE NAS using 5GS services with control plane CIoT 5GS optimization can wait for the lower layers to complete the transmission of the previous UL NAS TRANSPORT messages carrying control plane user data before providing subsequent NAS messages. Other implementations are possible. NOTE 2: When providing NAS messages to the lower layers for transmission, the UE NAS using 5GS services with control plane CIoT 5GS optimization can prioritize sending NAS signalling messages over the UL NAS TRANSPORT messages carrying control plane user data. How the UE performs this prioritization is implementation specific. | 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.1.2 |
3,993 | 10.3.2 MR-DC with 5GC | The SN Modification procedure may be initiated either by the MN or by the SN and be used to modify the current user plane resource configuration (e.g. related to PDU session, QoS flow or DRB) or to modify other properties of the UE context within the same SN. It may also be used to transfer an RRC message from the SN to the UE via the MN and the response from the UE via MN to the SN (e.g. when SRB3 is not used). In NGEN-DC and NR-DC, the RRC message is an NR message (i.e., RRCReconfiguration) whereas in NE-DC it is an E-UTRA message (i.e., RRCConnectionReconfiguration). In case of CPA, inter-SN CPC or inter-SN subsequent CPAC, this procedure is used to modify CPA, inter-SN CPC or inter-SN subsequent CPAC configuration within the same candidate SN. In case of CPA, inter-SN CPC or inter-SN subsequent CPAC, this procedure may also be triggered by the candidate SN to add some prepared PSCells from the suggested list or cancel part of the prepared PSCells. In case of intra-SN CPC or intra-SN subsequent CPAC, this procedure is used to configure, modify or release intra-SN CPC or intra-SN subsequent CPAC configuration. In case of intra-SN SCG LTM, this procedure is used to configure, modify or release intra-SN SCG LTM configuration. This procedure may be initiated by the MN or SN to request the SN or MN to activate or deactivate the SCG. This procedure can also be used to support coordination between the MN and the SN for managing the configuration and reporting of QoE measurements and/or RAN visible QoE measurements in NR-DC. Editor's note: FFS. It's up to RAN3 on how to configure intra-SN subsequent CPAC in MN format and which procedure is to be used, e.g. MN initiated SN modification procedure, SN initiated SN modification with MN involvement procedure, or SN initiated SN change procedure. The SN modification procedure does not necessarily need to involve signalling towards the UE. MN initiated SN Modification Figure 10.3.2-1: SN Modification procedure - MN initiated The MN uses the procedure to initiate configuration changes of the SCG within the same SN, including addition, modification or release of the user plane resource configuration. The MN uses this procedure to perform handover within the same MN while keeping the SN, when the SN needs to be involved (i.e. in NGEN-DC). The MN also uses the procedure to query the current SCG configuration, e.g. when delta configuration is applied in an MN initiated SN change. The MN also uses the procedure to provide the S-RLF related information to the SN or to provide additional available DRB IDs to be used for SN terminated bearers. The MN also uses this procedure to activate or deactivate the SCG. The MN may not use the procedure to initiate the addition, modification or release of SCG SCells. The SN may reject the request, except if it concerns the release of the user plane resource configuration, or if it is used to perform handover within the same MN while keeping the SN. Figure 10.3.2-1 shows an example signalling flow for an MN initiated SN Modification procedure. 1. The MN sends the SN Modification Request message, which may contain user plane resource configuration related or other UE context related information, PDU session level Network Slice info and the requested SCG configuration information, including the UE capabilities coordination result to be used as basis for the reconfiguration by the SN. In case a security key update in the SN is required, a new SN Security Key is included. In case the PDCP data recovery in the SN is required, the PDCP Change Indication is included which indicates that PDCP data recovery is required in SN. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the SN Modification Request message may contain the QMC Coordination Request IE. 2. The SN responds with the SN Modification Request Acknowledge message, which may contain new SCG radio configuration information within an SN RRC reconfiguration message, and data forwarding address information (if applicable). If the MN requested the SCG to be activated or deactivated, the SN indicates whether the SCG is activated or deactivated. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the SN Modification Request Acknowledge message may contain the QMC Coordination Response IE. NOTE 1: For MN terminated bearers to be setup for which PDCP duplication with CA is configured in NR SCG side, the MN allocates up to 4 separate Xn-U bearers and the SN provides a logical channel ID for primary or split secondary path to the MN. For SN terminated bearers to be setup for which PDCP duplication with CA is configured in NR MCG side, the SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the SN via an additional MN-initiated SN modification procedure. 2a. When applicable, the MN provides data forwarding address information to the SN. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 3/4. The MN initiates the RRC reconfiguration procedure, including an SN RRC reconfiguration message. The UE applies the new configuration, synchronizes to the MN (if instructed, in case of intra-MN handover) and replies with MN RRC reconfiguration complete message, including an SN RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. 5. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the SN Reconfiguration Complete message. 6. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN addition procedure. Otherwise, the UE may perform UL transmission after having applied the new configuration. 7. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.2-1 depicts the case where a bearer context is transferred from the MN to the SN). 8. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.2-1 depicts the case where a user plane resource configuration related context is transferred from the MN to the SN). 9. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 2: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. 10. If applicable, a PDU Session path update procedure is performed. SN initiated SN Modification with MN involvement Figure 10.3.2-2: SN Modification procedure - SN initiated with MN involvement The SN uses the procedure to perform configuration changes of the SCG within the same SN, e.g. to trigger the modification/release of the user plane resource configuration, to trigger the release of SCG resources (e.g., release SCG lower layer resources but keep SN), and to trigger PSCell changes (e.g. when a new security key is required or when the MN needs to perform PDCP data recovery). The MN cannot reject the release request of PDU session/QoS flows and the release request of SCG resources. The SN also uses the procedure to request the MN to provide more DRB IDs to be used for SN terminated bearers or to return DRB IDs used for SN terminated bearers that are not needed any longer. The SN also uses this procedure to activate or deactivate the SCG. Figure 10.3.2-2 shows an example signalling flow for SN initiated SN Modification procedure. 1. The SN sends the SN Modification Required message including an SN RRC reconfiguration message, which may contain user plane resource configuration related context, other UE context related information and the new radio resource configuration of SCG. The SN may request the SCG to be activated or deactivated. In case of change of security key, the PDCP Change Indication indicates that an SN security key update is required. In case the MN needs to perform PDCP data recovery, the PDCP Change Indication indicates that PDCP data recovery is required. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the SN Modification Required message may contain the QMC Coordination Request IE. The SN can decide whether the change of security key is required. NOTE 3a: In case that a MN initiated conditional reconfiguration (e.g. CHO, MN initiated inter-SN CPC or MN initiated inter-SN subsequent CPAC) is prepared, and if any execution of a prepared SN initiated intra-SN CPC or SN initiated intra-SN subsequent CPAC without MN involvement procedure or reconfiguration of the SCG, the SN notifies to the MN via the SN Modification Required message. In this case, the steps 2 and 3 are skipped. NOTE 3b: In case of SN initiated inter-SN CPC or SN initiated inter-SN subsequent CPAC and in case that a candidate SN triggered the SN Initiated SN Modification procedure to include some prepared PSCells (within the candidate cells suggested by the source SN in SN initiated inter-SN CPC or SN initiated inter-SN subsequent CPAC) or to remove some prepared PSCells, the MN may decide to trigger the step 2 towards the source SN. 2/3. The MN initiated SN Modification procedure may be triggered by SN Modification Required message, e.g. when an SN security key change needs to be applied. NOTE 3: For SN terminated bearers to be setup for which PDCP duplication with CA is configured in NR MCG side, the SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the SN via the nested MN-initiated SN modification procedure. 4. The MN sends the MN RRC reconfiguration message to the UE including the SN RRC reconfiguration message with the new SCG radio resource configuration. 5. The UE applies the new configuration and sends the MN RRC reconfiguration complete message, including an SN RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. 6. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the SN Modification Confirm message including the SN RRC response message, if received from the UE. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the SN Modification Confirm message may contain the QMC Coordination Response IE. 7. If instructed, the UE performs synchronisation towards the PSCell configured by the SN as described in SN Addition procedure. Otherwise, the UE may perform UL transmission directly after having applied the new configuration. 8. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.2-2 depicts the case where a bearer context is transferred from the SN to the MN). 9. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.2-2 depicts the case where a user plane resource configuration related context is transferred from the SN to the MN). 10. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 4: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. 11. If applicable, a PDU Session path update procedure is performed. SN initiated SN Modification without MN involvement This procedure is not supported for NE-DC. Figure 10.3.2-3: SN Modification – SN initiated without MN involvement The SN initiated SN modification procedure without MN involvement is used to modify the configuration within SN in case no coordination with MN is required, including the addition/modification/release of SCG SCell and PSCell change (e.g. when the security key does not need to be changed and the MN does not need to be involved in PDCP recovery). The SN may initiate the procedure to configure, modify or release intra-SN CPC or intra-SN subsequent CPAC configuration within the same SN. The SN may initiate the procedure to configure, modify or release intra-SN SCG LTM configuration within the same SN. Figure 10.3.2-3 shows an example signalling flow for SN initiated SN modification procedure without MN involvement. The SN can decide whether the Random Access procedure is required. 1. The SN sends the SN RRC reconfiguration message to the UE through SRB3. 2. The UE applies the new configuration and replies with the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. 3. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN Addition procedure. Otherwise the UE may perform UL transmission after having applied the new configuration. SN initiated Conditional SN Modification without MN involvement (SRB3 is used) This procedure is not supported for NE-DC and NGEN-DC. Figure 10.3.2-3a: SN Modification – SN-initiated without MN involvement and SRB3 is used to configure intra-SN CPC or intra-SN subsequent CPAC. The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is used to configure intra-SN CPC or intra-SN subsequent CPAC. 1. The SN sends the SN RRC reconfiguration including CPC configuration or subsequent CPAC configuration to the UE through SRB3. 2. The UE applies the new configuration. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. The UE starts evaluating the execution conditions for the candidate PSCell(s). The UE maintains connection with the source PSCell and replies with the RRCReconfigurationComplete message to the SN via SRB3. 3. If at least one candidate PSCell satisfies the corresponding execution condition, the UE detaches from the source PSCell, applies the stored configuration corresponding to the selected candidate PSCell and synchronises to the candidate PSCell. In subsequent CPAC, the UE keeps the configured subsequent CPAC configuration and evaluates the execution conditions of other candidate PSCells after completion of the subsequent CPAC execution. 4. The UE completes the CPC execution procedure by sending an RRCReconfigurationComplete message to the new PSCell. NOTE 5: For a subsequent CPAC configuration, after a PSCell change, if the execution condition of one candidate PSCell is satisfied, the UE executes steps 3-4, e.g. based on the configuration provided in step 1. SN initiated SCG LTM without MN involvement (SRB3 is used) This procedure is not supported for NE-DC and NGEN-DC. Figure 10.3.2-3b: SN Modification – SN-initiated without MN involvement and SRB3 is used to configure intra-SN SCG LTM The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is used to configure intra-SN SCG LTM. 1. The SN sends the SN RRCReconfiguration including SCG LTM configuration to the UE through SRB3. 2. The UE stores the SCG LTM candidate cell configurations and transmits an RRCReconfigurationComplete message to the SN. 3a. If indicated by the SN, the UE performs DL synchronization with candidate cell(s) before receiving the cell switch command. 3b. If indicated by the SN, the UE performs early TA acquisition with candidate cell(s) before receiving the cell switch command as specified in clause in 9.2.3.5.2 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. 4. The UE performs L1 measurements on the configured candidate cell(s) and transmits L1 measurement reports to the SN, according to the L1 measurement configuration in RRCReconfiguration received in step 1. The UE starts to perform L1 measurements once the L1 measurement configuration is applicable. 5. The SN decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index. 6. The UE performs the random access procedure towards the target cell, if the UE does not have valid TA of the target cell. 7. The UE completes the SCG LTM cell switch procedure by sending RRCReconfigurationComplete message to target cell. If the UE has performed a RA procedure in step 6 the UE considers that LTM execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM execution is successfully completed when the UE determines that the target cell has successfully received its first UL data, as specified in clause in 9.2.3.5.2 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. NOTE 6: The steps 3-7 can be performed multiple times for subsequent SCG LTM using the SCG LTM candidate configuration(s) provided in step 1. Transfer of an NR RRC message to/from the UE (when SRB3 is not used) This procedure is supported for all the MR-DC options. Figure 10.3.2-4: Transfer of an NR RRC message to/from the UE The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used. 1. The SN initiates the procedure by sending the SN Modification Required to the MN including the SN RRC reconfiguration message. 2. The MN forwards the SN RRC reconfiguration message to the UE including it in the RRC reconfiguration message. 3. The UE applies the new configuration and replies with the RRC reconfiguration complete message by including the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. 4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the SN Modification Confirm message. 5. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN Addition procedure. Otherwise the UE may perform UL transmission after having applied the new configuration. SN initiated Conditional SN Modification without MN involvement (SRB3 is not used) This procedure is not supported for NE-DC and NGEN-DC. Figure 10.3.2-5: SN Modification – SN-initiated without MN involvement and SRB3 is not used to configure intra-SN CPC or intra-SN subsequent CPAC The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used to configure intra-SN CPC or intra-SN subsequent CPAC. 1. The SN initiates the procedure by sending the SN Modification Required to the MN including the SN RRC reconfiguration message with CPC configuration or subsequent CPAC configuration. 2. The MN forwards the SN RRC reconfiguration message to the UE including it in the RRCReconfiguration message. 3. The UE replies with the RRCReconfigurationComplete message by including the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. The UE maintains connection with source PSCell after receiving CPC configuration or subsequent CPAC configuration, and starts evaluating the execution conditions for the candidate PSCell(s). 4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the SN Modification Confirm message. 5. If at least one candidate PSCell satisfies the corresponding execution condition, the UE completes the CPC execution procedure by an ULInformationTransferMRDC message to the MN which includes an embedded RRCReconfigurationComplete message to the selected target PSCell. In subsequent CPAC, the UE keeps the configured subsequent CPAC configuration and evaluates the execution conditions of other candidate PSCells after completion of the subsequent CPAC execution. 6. The RRCReconfigurationComplete message is forwarded to the SN embedded in RRC Transfer message. 7. The UE detaches from the source PSCell, applies the stored corresponding configuration and synchronises to the selected candidate PSCell. NOTE 7: For a subsequent CPAC configuration, after a PSCell change, if the execution condition of one candidate PSCell is satisfied, the UE executes steps 5-7, e.g. based on the configuration provided in step 2. SN initiated SCG LTM without MN involvement (SRB3 is not used) This procedure is not supported for NE-DC and NGEN-DC. Figure 10.3.2-6: SN Modification – SN-initiated without MN involvement and SRB3 is not used to configure intra-SN SCG LTM The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used to configure intra-SN SCG LTM. 1. The SN initiates the procedure by sending the SN Modification Required to the MN including the SN RRCReconfiguration message with SCG LTM configuration. 2. The MN forwards the SN RRCReconfiguration message to the UE including it in the RRCReconfiguration message. 3. The UE replies with the RRCReconfigurationComplete message by including the SN RRCReconfigurationComplete message. 4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the SN Modification Confirm message. 5a. If indicated by the SN, the UE performs DL synchronization with candidate cell(s) before receiving the cell switch command. 5b. If indicated by the SN, the UE performs early TA acquisition with candidate cell(s) before receiving the cell switch command as specified in clause in 9.2.3.5.2 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. 6. The UE performs L1 measurements on the configured candidate cell(s) and transmits L1 measurement reports to the SN, according to the L1 measurement configuration in RRCReconfiguration received in step 2. The UE starts to perform L1 measurements once the L1 measurement configuration is applicable. 7. The SN decides to execute cell switch to a target cell and transmits a MAC CE triggering cell switch by including the candidate configuration index of the target cell. The UE switches to the target cell and applies the configuration indicated by candidate configuration index. 8. The UE sends an ULInformationTransferMRDC message to the MN which includes an embedded RRCReconfigurationComplete message to the target cell. 9. The RRCReconfigurationComplete message is forwarded to the SN embedded in RRC Transfer message. 10. The UE performs the random access procedure towards the target cell, if the UE does not have valid TA of the target cell. 11. The UE completes the SCG LTM cell switch procedure by sending an UL transmission to target cell. If the UE has performed a RA procedure in step 10 the UE considers that LTM execution is successfully completed when the random access procedure is successfully completed. For RACH-less LTM, the UE considers that LTM execution is successfully completed when the UE determines that the SN has successfully received its first UL transmission, as specified in clause in 9.2.3.5.2 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. NOTE 8: The steps 5-11 can be performed multiple times for subsequent SCG LTM using the SCG LTM candidate configuration(s) provided in step 2. | 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.3.2 |
3,994 | 5.27 GNSS measurement | The network may request a NB-IoT UE, a BL UE or a UE in enhanced coverage in a non-terrestrial network to perform GNSS measurement or configure a GNSS measurement gap for UE autonomous GNSS measurement by sending the GNSS Measurement Command MAC CE described in clause 6.1.3.22. The MAC entity shall: - if the MAC entity receives a GNSS Measurement Command MAC CE: - indicate the GNSS measurement gap length configuration to upper layers; - if the Type field indicates network-triggered GNSS measurement: - indicate to upper layers a request to perform GNSS measurement. | 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.27 |
3,995 | 5.17.2.4 Mobility between 5GS and GERAN/UTRAN | IP address preservation upon direct mobility between 5GS and GERAN/UTRAN is not supported. Upon mobility from 5GS to GERAN/UTRAN (e.g. upon leaving NG-RAN coverage) the UE shall perform the A/Gb mode GPRS Attach procedure or Iu mode GPRS Attach procedure (see TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [56]). As a UE option, to support IP address preservation at mobility from EPC to 5GS for PDN connections without 5GS related parameters, a 5GS capable UE may: - Following mobility from GERAN/UTRAN to EPS, release those PDN connection(s) and re-establish them as specified in clause 4.11.1.5.4.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] so that they support interworking to 5GS. NOTE 1: It is recommended that a UE using this option does not do this behaviour after every change to EPS in PLMNs that do not support 5GS, nor for APNs that do not support mobility to 5GS; and, that such a UE supports storage of the 5GS related parameters while in GERAN/UTRAN. Whether and how the UE is aware of which PLMNs support 5GS and which APNs do not support mobility to 5GS is out of scope of this specification. To support mobility from EPC to 5GS to EPC to GERAN/UTRAN for PDN connections established in EPC: NOTE 2: For the use of N7 or N40 interfaces while the UE is in GERAN/UTRAN access, the SMF+PGW-C selected by the MME (using the existing selection procedures described in clause 4.11.0a of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and clause 4.3.8 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]) needs to support functionality (e.g. signalling of GERAN/UTRAN cell identification over N7) specified in Annex L. - in signalling sent on the N26 interface, the MME should send the TI and BSS Container in the EPS Bearer Context (see Table 7.3.1-3 of TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [101]), if there is any, of the EPS bearer to the SMF (V-SMF / I-SMF) via the AMF in the Bearer Context within the PDN Connection IE in the Forward Relocation Request and Context Response messages (TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [101]); the SMF (V-SMF / I-SMF) should store the TI and BSS Container and the SMF (V-SMF / I-SMF) should provide the TI and BSS Container to the AMF (as part of a procedure to deliver SM context to AMF) so that the AMF sends the TI and BSS Container of the related EPS bearer in the Bearer Context within the EPS PDN Connection information in any subsequent Forward Relocation Request and Context Response message sent to an MME. NOTE 3: At mobility from EPC, the SMF+PGW-C / V-SMF / I-SMF receives the TI and BSS Container as part of the UE EPS PDN Connection information from the AMF and stores the TI. At mobility to EPC, the SMF+PGW-C / V-SMF / I-SMF provides the AMF with the TI and BSS Container as part of the UE EPS PDN Connection information. The SMF+PGW-C / V-SMF / I-SMF is not meant to understand the TI/BSS Container nor to use it for any other purpose than providing it back to AMF. NOTE 4: GERAN/UTRAN Mobility Management Bearer Synchronisation procedures will release any dedicated QoS Flows established in 5GS. NOTE 5: When the UE access the network via GERAN/UTRAN over Gn/Gp interface, Secondary PDP Context Activation Procedure is not supported. IP address preservation at mobility from EPC to GERAN/UTRAN for PDU sessions established in 5GS is not supported. With regard to interworking between 5GS and the Circuit Switched domain when the GERAN or UTRAN network is operating in NMO II (i.e. no Gs interface between MSC and SGSN): - upon mobility from 5GS to GERAN/UTRAN, the UE shall either: - act as if it is returning after a loss of GERAN/UTRAN coverage (and e.g. only perform a periodic LAU if the periodic LAU timer has expired), or, - perform a Location Update to the MSC. If the UE is registered for IMS voice and is configured, using Device Management or initial provisioning, to perform additional mobility management procedures when it has moved from a RAT that supports IMS voice over PS sessions to one that does not (see TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [56]), it shall follow this option. Upon mobility from GERAN/UTRAN to 5GS (e.g. upon selecting an NG-RAN cell) the UE shall perform the Registration procedure of "initial registration" type as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UE shall indicate a 5G-GUTI as UE identity in the Registration procedure if it has a stored valid native 5G-GUTI (e.g. from an earlier registration in the 5G System). Otherwise the UE shall indicate a SUCI. If a UE in MICO mode moves to GERAN/UTRAN and any of the triggers defined in clause 5.4.1.3 occur, then the UE shall locally disable MICO mode and perform the A/Gb mode GPRS Attach procedure or Iu mode GPRS Attach procedure (see TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [56]). The UE can renegotiate MICO when it returns to 5GS during (re-)registration procedure. In Single Registration mode, expiry of the periodic RAU timer, or, the periodic LAU timer shall not cause the UE to change RAT. The 5G SRVCC from NG-RAN to UTRAN is specified in the TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [88]. After the 5G SRVCC to UTRAN, all the PDU sessions of the UE are released. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.4 |
3,996 | 4.2.5.1.3 Substate, UPDATE-NEEDED | The MS shall: - not send any user data; - not send any signalling information, unless for a routing area update procedure upon request of the upper layers to establish a PDN connection for emergency bearer services (UTRAN Iu mode only); - perform cell selection/reselection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]; and - choose the appropriate new substate depending on the GPRS update status as soon as the access class control allows network contact in the selected cell. | 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.2.5.1.3 |
3,997 | 7.4 Handling of combined MN/SN RRC messages | When both MCG and SCG reconfiguration is required due to the need for coordination with the MN, the SN RRC reconfiguration message is encapsulated in an MN RRC message that also carries the corresponding MCG reconfiguration that ensures that the combined configuration can be jointly processed by the UE. If the MN terminates a bearer using NR PDCP, the NR PDCP configuration is generated by the MN itself. If the SN terminates the bearer, the SN generates the NR PDCP configuration and sends it to the MN as a separate container. The UE uses a joint success/failure procedure for messages in an encapsulating MN RRC message. A failure of the MN RRC messages, including one encapsulated SN RRC message with or without any MCG reconfiguration fields, triggers a re-establishment procedure. Each SN RRC reconfiguration message should have its own RRC response message even when the SN RRC message is encapsulated in an MN RRC message. The SN RRC response message is forwarded over X2/Xn to the SN. If a SN RRC reconfiguration message is contained in a MN RRC message, the UE sends a MN RRC response message that encapsulates the SN RRC response message. NOTE: If the MN RRC message does not encapsulate an SN RRC reconfiguration message (i.e. an SCG configuration) but only information elements generated by the SN (e.g. the PDCP configuration for an SN terminated bearer), the UE will not send an SN RRC response message. | 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 | 7.4 |
3,998 | 5.16.4.5 SMF and UPF selection function for Emergency Services | When a SMF is selected for Emergency Services, the SMF selection function described in clause 6.3.2 for normal services is applied to the Emergency DNN or the AMF selects the SMF directly from the AMF Emergency Configuration Data. If the SMF selection function described in clause 6.3.2 is used it shall always derive a SMF in the Serving PLMN or SNPN, which guarantees that the IP address is also allocated by the Serving PLMN or SNPN. When a UPF is selected for Emergency Services, the UPF selection function described in clause 6.3.3 for normal services is applied to the Emergency DNN or the SMF selects the UPF directly from the SMF Emergency Configuration Data. The information in the AMF Emergency Configuration Data and the SMF Emergency Configuration Data is specified in clause 5.16.4.1. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.4.5 |
3,999 | 4.3.1.7.1 Average quality of the serving cell when HO is triggered | This measurement provides the average quality of the serving cell reported in the UE measurement reports that triggered HO. The average is computed over all measurement reports that triggered HO received during the measurement granularity period. Separate measurement is produced for each measurement quantity {RSRP, RSRQ}. DER (n=1) For each UtranRelation, this measurement is obtained by accumulating the value (linear value converted from dbm unit) of the quality of the serving (source) cell (RSRP and RSRQ) in the UE measurement report causing HO on the UtranRelation, and dividing the accumulated value by the number of HO occurrence on the UtranRelation at the end of granularity period, and converting the value back to dbm unit from linear value. Separate measurement is provided for RSRP and for RSRQ. Each measurement is asingle integer value in dBm (RSRP) or dB (RSRQ) HO.SrcCellQual.RSRP HO.SrcCellQual.RSRQ EUtranRelation Valid for packet switched traffic 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.3.1.7.1 |
4,000 | 8.51.4 Home eNodeB ID | The Target Type is Home eNodeB ID for handover to E-UTRAN Home eNodeB. In this case the coding of the Target ID field shall be coded as depicted in Figure 8.51-3. Figure 8.51-3: Target ID for Type Home eNodeB The Home eNodeB ID consists of 28 bits. See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. Bit 4 of Octet 9 is the most significant bit and bit 1 of Octet 12 is the least significant bit. The coding of the Home eNodeB ID is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. | 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.4 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.