Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   5…   5.2…   5.3   5.4…   5.5…   5.6…   6…   6.2…   6.3…   6.4…   7…   8…   8.2.9…   8.3…   9…   A…   D…

 

4.9  Disabling and re-enabling of UE's N1 mode capabilityWord‑p. 92

4.9.1  General

The UE shall re-enable the N1 mode capability when the UE powers off and powers on again, the USIM is removed or an entry of the "list of subscriber data" with the SNPN identity of the SNPN is updated.

4.9.2  Disabling and re-enabling of UE's N1 mode capability for 3GPP access

The UE shall only disable the N1 mode capability for 3GPP access when in 5GMM-IDLE mode.
When the UE is disabling the N1 mode capability for 3GPP access for a PLMN not due to redirection to EPC, it should proceed as follows:
  1. select an E-UTRA cell connected to EPC of the registered PLMN or a PLMN from the list of equivalent PLMNs, if the UE supports S1 mode and the UE has not disabled its E-UTRA capability as specified in TS 24.301;
  2. if an E-UTRA cell connected to EPC of the registered PLMN or a PLMN from the list of equivalent PLMNs cannot be found, the UE does not support S1 mode or the UE has disabled its E-UTRA capability as specified in TS 24.301, the UE may select another RAT of the registered PLMN or a PLMN from the list of equivalent PLMNs that the UE supports;
  3. if another RAT of the registered PLMN or a PLMN from the list of equivalent PLMNs cannot be found, or the UE does not have a registered PLMN, then enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform PLMN selection as specified in TS 23.122. If disabling of the N1 mode capability for 3GPP access was not due to a UE-initiated de-registration procedure for 5GS services over 3GPP access not due to switch-off, the UE may re-enable the N1 capability for this PLMN selection. As an implementation option, if the UE does not have a registered PLMN, instead of performing PLMN selection, the UE may select another RAT of the selected PLMN if the UE has chosen a PLMN and the RAT is supported by the UE; or
  4. if no other allowed PLMN and RAT combinations are available, then the UE may re-enable the N1 mode capability for 3GPP access and indicate to lower layers to remain camped in NG-RAN of the registered PLMN, and may periodically scan for another PLMN and RAT combination which can provide EPS services or non-EPS services (if the UE supports EPS services or non-EPS services). How this periodic scanning is done, is UE implementation dependent.
When the UE is disabling the N1 mode capability for 3GPP access for an SNPN, it should proceed as follows:
  1. enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform SNPN selection as specified in TS 23.122. If disabling of the N1 mode capability for 3GPP access was not due to a UE-initiated de-registration procedure for 5GS services over 3GPP access not due to switch-off, the UE may re-enable the N1 capability for this SNPN selection; or
  2. if no other SNPN is available, then the UE may re-enable the N1 mode capability for 3GPP access and indicate to lower layers to remain camped in NG-RAN of the registered SNPN.
When the UE is disabling the N1 mode capability upon receiving reject cause #31 "Redirection to EPC required" as specified in subclauses 5.5.1.2.5, 5.5.1.3.5 and 5.6.1.5, it should proceed as follows:
  1. If the UE is in NB-N1 mode:
    1. if lower layers do not provide an indication that the current E-UTRA cell is connected to EPC or lower layers do not provide an indication that the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, search for a suitable NB-IoT cell connected to EPC according to TS 36.304;
    2. if lower layers provide an indication that the current E-UTRA cell is connected to EPC and the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, perform a core network selection to select EPC as specified in subclause 4.8.4A.1; or
    3. if lower layers cannot find a suitable NB-IoT cell connected to EPC or there is no suitable NB-IoT cell connected to EPC which supports CIoT EPS optimizations that are supported by the UE, the UE may re-enable the N1 mode capability for 3GPP access, and indicate to lower layers to remain camped in E-UTRA connected to 5GCN of the previously registered PLMN and proceed with the appropriate 5GMM procedure.
  2. If the UE is in WB-N1 mode:
    1. if lower layers do not provide an indication that the current E-UTRA cell is connected to EPC or lower layers do not provide an indication that the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, search for a suitable E-UTRA cell connected to EPC according to TS 36.304;
    2. if lower layers provide an indication that the current E-UTRA cell is connected to EPC and the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, then perform a core network selection to select EPC as specified in subclause 4.8.4A.1; or
    3. if lower layers cannot find a suitable E-UTRA cell connected to EPC or there is no suitable E-UTRA cell connected to EPC which supports CIoT EPS optimizations that are supported by the UE, the UE may re-enable the N1 mode capability for 3GPP access, and indicate to lower layers to remain camped in E-UTRA connected to 5GCN of the previously registered PLMN and proceed with the appropriate 5GMM procedure.
When the UE supporting both N1 mode and S1 mode needs to stay in E-UTRA connected to EPC (e.g. due to the domain selection for UE originating sessions as specified in subclause 4.3.2), in order to prevent unintentional handover or cell reselection from E-UTRA connected to EPC to NG-RAN connected to 5GCN, the UE operating in single-registration mode shall disable the N1 mode capability for 3GPP access and:
  1. shall set the N1mode bit to "N1 mode not supported" in the UE network capability IE (see TS 24.301) of the ATTACH REQUEST message and the TRACKING AREA UPDATE REQUEST message in EPC; and
  2. the UE NAS layer shall indicate the access stratum layer(s) of disabling of the N1 mode capability for 3GPP access.
If the UE is required to disable the N1 mode capability for 3GPP access and select E-UTRA or another RAT, and the UE is in the 5GMM-CONNECTED mode,
  • if the UE has a persistent PDU session, then the UE waits until the radio bearer associated with the persistent PDU session has been released;
  • otherwise the UE shall locally release the established NAS signalling connection;
and enter the 5GMM-IDLE mode before selecting E-UTRA or another RAT.
If the UE is disabling its N1 mode capability for 3GPP access before selecting E-UTRA or another RAT, the UE shall not perform the UE-initiated de-registration procedure of subclause 5.5.2.2.
The UE shall re-enable the N1 mode capability for 3GPP access when the UE performs PLMN or SNPN selection over 3GPP access, unless
  • disabling of the N1 mode capability for 3GPP access was due to a UE-initiated de-registration procedure for 5GS services over 3GPP access not due to switch-off; or
  • the UE has already re-enabled the N1 mode capability for 3GPP access when performing items c) or d) above.
If the disabling of N1 mode capability for 3GPP access was due to IMS voice is not available over 3GPP access and the UE's usage setting is "voice centric", the UE shall re-enable the N1 mode capability for 3GPP access when the UE's usage setting is changed from "voice centric" to "data centric", as specified in subclauses 4.3.3.
The UE should memorize the identity of the PLMN or SNPN where N1 mode capability for 3GPP access was disabled and should use that stored information in subsequent PLMN or SNPN selections as specified in TS 23.122.
If the disabling of N1 mode capability for 3GPP access was due to successful completion of an emergency services fallback, the criteria to enable the N1 mode capability again are UE implementation specific.
If the N1 mode capability for 3GPP access was disabled due to the UE initiated de-registration procedure for 3GPP access or for 3GPP access and non-3GPP access and the UE is operating in single-registration mode (see subclause 5.5.2.2.3), upon request of the upper layers to re-register for 5GS services over 3GPP access the UE shall enable the N1 mode capability for 3GPP access again.
As an implementation option, the UE may start a timer for enabling the N1 mode capability for 3GPP access when the UE's registration attempt counter reaches 5 and the UE disables the N1 mode capability for 3GPP access for cases described in subclauses 5.5.1.2.7 and 5.5.1.3.7. The UE should memorize the identity of the PLMNs where N1 mode capability for 3GPP access was disabled. On expiry of this timer:
  • if the UE is in Iu mode or A/Gb mode and is in idle mode as specified in TS 24.008 on expiry of the timer, the UE should enable the N1 mode capability for 3GPP access;
  • if the UE is in Iu mode or A/Gb mode and an RR connection exists, the UE shall delay enabling the N1 mode capability for 3GPP access until the RR connection is released;
  • if the UE is in Iu mode and a PS signalling connection exists, but no RR connection exists, the UE may abort the PS signalling connection before enabling the N1 mode capability for 3GPP access;
  • if the UE is in S1 mode and is in EMM-IDLE mode as specified in TS 24.301, on expiry of the timer, the UE should enable the N1 mode capability for 3GPP access; and
  • if the UE is in S1 mode and is in EMM-CONNECTED mode as specified in TS 24.301, on expiry of the timer, the UE shall delay enabling the N1 mode capability for 3GPP access until the NAS signalling connection in S1 mode is released.
The UE may disable the N1 mode capability for currently camped PLMN or SNPN over 3GPP access (see TS 23.122) if no network slice is available for the camped PLMN.
If the UE attempts to establish an emergency PDU session in a PLMN where N1 mode capability was disabled due to the UE's registration attempt counter have reached 5, the UE may enable N1 mode capability for that PLMN memorized by the UE.
Up

4.9.3  Disabling and re-enabling of UE's N1 mode capability for non-3GPP accessWord‑p. 94
When the UE disables the N1 mode capability for non-3GPP access, the UE NAS layer shall not initiate any 5GS NAS procedures towards the network over non-3GPP access.
When the UE supporting both N1 mode and S1 mode needs to stay in non-3GPP access connected to EPC (e.g. due to the domain selection for UE originating sessions as specified in subclause 4.3.2), in order to prevent unintentional selection of a non-3GPP access network connected to 5GCN, the UE operating in single-registration mode shall not transfer any PDN connection to a non-3GPP access network connected to the 5GCN.
If the disabling of N1 mode capability for non-3GPP access was due to IMS voice is not available over non-3GPP access in 5GS and the UE's usage setting is "voice centric", the UE shall re-enable the N1 mode capability for non-3GPP access when the UE's usage setting is changed from "voice centric" to "data centric" as specified in subclauses 4.3.3.
The UE shall re-enable the N1 mode capability for non-3GPP access when a new PLMN or SNPN is selected over non-3GPP access.
The UE may disable the N1 mode capability for the currently camped PLMN or SNPN over non-3GPP access if no network slice is available for the camped PLMN.
As an implementation option, the UE may start a timer for re-enabling the N1 mode capability for non-3GPP access, after the the N1 mode capability for non-3GPP access was disabled. On the expiry of this timer, the UE should re-enable the the N1 mode capability for non-3GPP access.
Up

4.10  Interworking with ePDG connected to EPCWord‑p. 95
In order to interwork with ePDG connected to EPC, the UE shall operate as specified in either subclause 4.8.2.3 or subclause 4.8.3. Which subclause the UE follows is chosen by the UE irrespective of the interworking without N26 interface indicator.
The UE shall not attempt to transfer PDU sessions with PDU session type "Ethernet" or "Unstructured" to an ePDG connected to EPC.
Up

4.11  UE configuration parameter updates

The 5GS in a PLMN supports updating UE parameters via NAS signalling. The feature enables the HPLMN to securely and dynamically re-configure the UE configuration parameters stored on the USIM and the ME.
In this release of the specification, updates of the following USIM configuration parameters are supported:
  • routing indicator.
In this release of specification, updates of the following ME configuration parameters are supported:
  • default configured NSSAI.
The 5GS in an SNPN supports updating UE parameters via NAS signalling. The feature enables the SNPN to securely and dynamically re-configure the UE configuration parameter stored on the USIM if the UE used the USIM for registration to the SNPN.
In this release of the specification, updates of the following USIM configuration parameters are supported:
  • routing indicator.
The update of UE configuration parameters is initiated by the network using the network-initiated downlink NAS transport procedure as described in subclause 5.4.5.3. The ME acknowledgement of successful reception of the updated UE configuration parameter information is sent back to the network using the UE-initiated uplink NAS transport procedure as described in subclause 5.4.5.2.
Up

4.12  Access traffic steering, switching and splitting (ATSSS) |R16|

The ATSSS feature is an optional feature that may be supported by the UE and the 5GCN.
The ATSSS feature enables a multi-access PDU connectivity service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network. The multi-access PDU connectivity service is realized by establishing a multi-access PDU session, i.e. a PDU session that can have user-plane resources on two access networks.
The UE can request an MA PDU session when the UE is registered via both 3GPP and non-3GPP accesses, or when the UE is registered via one access only. The MA PDU session management is performed based on the PDU session management procedures.
The detailed description of the procedures for ATSSS between the UE and the network across one 3GPP access network and one non-3GPP access network are specified in TS 24.193.
Up

4.13  Support of NAS signalling using wireline access network |R16|Word‑p. 96
A 5G-RG, a W-AGF acting on behalf of an FN-RG or a W-AGF acting on behalf of an N5GC device can use wireline access network to access the 5GCN by using NAS signalling procedures as described in TS 23.501, TS 23.502 and TS 23.316.
Wireline access is a type of non-3GPP access.
A 5G-RG simultaneously connected to the same 5GCN of a PLMN over a 3GPP access and a wireline access is connected to a single AMF.
5G-RG maintains the N1 NAS signalling connection with the AMF over the wireline access network after all the PDU sessions for the 5G-RG over that access have been released or handed over to 3GPP access.
The 5G-RG connected to 5GCN via NG-RAN is specified in TS 23.316.
When accessing the 5GCN over 3GPP access, in addition to requirements specified for the 5G-RG in the present document, the 5G-RG shall also perform requirements specified in the present document for a UE accessing 5GCN over 3GPP access. When accessing the 5GCN over wireline access, in addition to requirements specified for the 5G-RG in the present document, the 5G-RG shall also perform requirements specified in the present document for a UE accessing 5GCN over non-3GPP access. If a requirement specified for the 5G-RG in the present document contradicts a requirement specified for the UE in the present document, the 5G-RG shall perform the requirement specified in the present document for the 5G-RG.
For the scenario of FN-RG, which does not support N1 mode, the W-AGF acting on behalf of the FN-RG exchanges NAS signalling messages with an AMF.
For the scenario of N5GC device, which does not support N1 mode, the W-AGF acting on behalf of the N5GC device exchanges NAS signalling messages with an AMF.
In addition to requirements specified for the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) in the present document, the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall also perform requirements specified in the present document for a UE accessing 5GCN over non-3GPP access. If a requirement specified for the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) in the present document contradicts a requirement specified for the UE in the present document, the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall perform requirement specified in the present document for the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device).
The PDU session authentication and authorization procedure is not supported in a PDU session established by the W-AGF acting on behalf of the FN-RG or on behalf of the N5GC device.
The W-AGF acting on behalf of the N5GC device requests the establishment of a PDU Session on behalf of the N5GC device upon registration. Only one PDU session per N5GC device is supported.
A 5G-RG or an FN-RG provide a non-3GPP access network to UEs. A UE connected to a non-3GPP access network provided by the 5G-RG or the FN-RG can access to the 5GCN via the N3IWF or via the TNGF as described in TS 23.316.
The 5G-RG or the W-AGF acting on behalf of the FN-RG shall indicate "ANDSP not supported by the UE" in the UE policy classmask IE during the the UE-initiated UE state indication procedure as specified in subclause D.2.2.
Up

4.14  Non-public network |R16|Word‑p. 97

4.14.1  General

Two types of NPN can be deployed using 5GS: SNPN (see subclause 4.14.2) and PNI-NPN (see subclause 4.14.3).

4.14.2  Stand-alone non-public network

If the UE is not SNPN enabled, the UE is always considered to be not operating in SNPN access mode. If the UE is SNPN enabled, the UE can operate in SNPN access mode. Details of activation and deactivation of SNPN access mode at the SNPN enabled UE are up to UE implementation.
The functions and procedures of NAS described in the present document are applicable to an SNPN and an SNPN enabled UE unless indicated otherwise. The key differences brought by the SNPN to the NAS layer are as follows:
  1. instead of the PLMN selection process, the SNPN selection process is performed by a UE operating in SNPN access mode (see TS 23.122 for further details on the SNPN selection);
  2. a "permanently forbidden SNPNs" list and a "temporarily forbidden SNPNs" list are managed per access type independently (i.e. 3GPP access or non-3GPP access) by a UE operating in SNPN access mode instead of forbidden PLMN lists;
  3. inter-system change to and from S1 mode is not supported;
  4. emergency services are not supported in SNPN access mode;
  5. CAG is not supported in SNPN access mode;
  6. with respect to the 5GMM cause values:
    1. 5GMM cause values #74 "Temporarily not authorized for this SNPN" and #75 "Permanently not authorized for this SNPN" are supported whereas these 5GMM cause values cannot be used in a PLMN; and
    2. 5GMM cause values #11 "PLMN not allowed", #31 "Redirection to EPC required", #73 "Serving network not authorized", and #76 "Not authorized for this CAG or authorized for CAG cells only" are not supported whereas these 5GMM cause values can be used in a PLMN;
  7. a list of "5GS forbidden tracking areas for roaming" and a list of "5GS forbidden tracking areas for regional provision of service" are managed per SNPN (see TS 23.122);
  8. when accessing SNPN services via a PLMN using 3GPP access, access to 5GCN of the SNPN is performed using 5GMM procedures for non-3GPP access and 5GMM parameter for non-3GPP access. In this case, the UE is operating in SNPN access mode over non-3GPP access. When accessing PLMN services via a SNPN using 3GPP access, access to 5GCN of the PLMN is performed using 5GMM procedures for non-3GPP access and 5GMM parameter for non-3GPP access. In this case, the UE is not operating in SNPN access mode over non-3GPP access. From the UE's NAS perspective, accessing PLMN services via an SNPN and accessing SNPN services via a PLMN are treated as untrusted non-3GPP access. If the UE is accessing the PLMN using non-3GPP access, the access to 5GCN of the SNPN via PLMN is not specified in this release of the specification;
  9. when registered to an SNPN, the UE shall use only the UE policies provided by the registered SNPN;
  10. equivalent SNPN is not supported;
  11. neither the default configured NSSAI nor the network slicing indication is supported in SNPNs;
  12. roaming is not supported in SNPN access mode;
  13. handover between SNPNs and handover between an SNPN and a PLMN are not supported;
  14. CIoT 5GS optimizations are not supported;
  15. accessing SNPN services using non-3GPP access is not supported, except when accessing SNPN services via a PLMN using 3GPP access as specified in item h;
  16. when registering or registered to an SNPN, the UE shall only consider a 5G-GUTI previously assigned by the same SNPN as a valid 5G-GUTI; and
  17. when registering or registered to an SNPN, the UE shall only consider a last visited registered TAI visited in the same SNPN as an available last visited registered TAI.
Up

4.14.3  Public network integrated non-public network (PNI-NPN)Word‑p. 98
A PNI-NPN is made available by means of e.g. dedicated DNNs or by one or more S-NSSAIs allocated for it. A CAG can be optionally used in order to prevent UEs not allowed to access a PNI-NPN from accessing the PNI-NPN. The key enablers for the CAG in the NAS layer are as follows:
  1. CAG selection (see TS 23.122); and
  2. provisioning of a "CAG information list" as specified in TS 23.122, from network to UE via the generic UE configuration update procedure, the registration procedure, and the service request procedure.
The "CAG information list" stored in the UE is kept when the UE enters 5GMM-DEREGISTERED state. The "CAG information list", if available, is stored in the non-volatile memory in the ME as specified in annex C. This "CAG information list" is deleted when the USIM is changed or removed.
The UE supporting CAG may perform the initial registration for emergency services via a non-CAG cell in a PLMN for which the UE has an "indication that the UE is only allowed to access 5GS via CAG cells" or via a CAG cell that is not included in the "Allowed CAG list" (see TS 23.122) for the selected PLMN. If a UE supporting CAG having an emergency PDU session is camping on:
  1. a CAG cell and none of the CAG-IDs of the CAG cell are included in the "Allowed CAG list" for the current PLMN in the UE's subscription; or
  2. a non-CAG cell in a PLMN for which the UE's subscription contains an "indication that the UE is only allowed to access 5GS via CAG cells";
the AMF shall release all non-emergency PDU sessions associated with 3GPP access, if any. The AMF shall not release the emergency PDU session.
Up

4.15  Time sensitive communication |R16|

4.15.1  General

A 5GS can support TSC (see TS 23.501, TS 23.502, and TS 23.503). The clause describes NAS-specific aspects of the 5GS features to support TSC.

4.15.2  Integration with TSN network

4.15.2.1  General

A 5GS can be integrated as a bridge in a TSN network (i.e. a TSN bridge). A DS-TT is deployed at the UE-side edge in order to interface with a TSN network while achieving transparency.

4.15.2.2  Time synchronization

If a 5GS functions as a TSN bridge, the 5GS is modelled as an IEEE 802.1AS [43A] compliant entity for the purpose of time synchronization. Two types of synchronization processes are supported by the 5GS: 5GS synchronization and TSN domain synchronization.
For 5GS synchronization, the lower layers provide the 5G internal system clock signalled via an NG-RAN (see TS 38.331) and the UE forwards the 5G internal system clock to the DS-TT(s).
For TSN domain synchronization, the UE supports forwarding generalized precision time protocol (gPTP) messages. For all TSN working domains associated with a PDU session, a UE forwards gPTP messages received via the PDU session to the DS-TT associated with the PDU session (see TS 23.501 and TS 23.502). See TS 24.535 for the details on gPTP messages within a 5GS.
Up

4.15.2.3  TSN bridge managementWord‑p. 99
For TSN bridge management, information available at a UE is provided to a TSN AF and port management information containers are exchanged between a DS-TT and a TSN AF (see TS 24.519).
During a UE-requested PDU session establishment procedure, if the UE supports transfer of port management information containers, then the UE indicates that transfer of port management information container is supported and the UE provides a DS-TT Ethernet port MAC address, Port management information container, and a UE-DS-TT residence time, if available, to the network (see subclause 6.4.1.2).
Once the UE has successfully established a PDU session and the UE has indicated that transfer of port management information container is supported during the UE-requested PDU session establishment procedure (see subclause 6.4.1.2), then port management information containers are exchanged via a UE-requested PDU session modification procedure and a network-requested PDU session modification procedure (see subclauses 6.3.2 and 6.4.2). The UE receiving a port management information container from the network shall forward the port management information container to the DS-TT.
Up

4.16  UE radio capability signalling optimisation |R16|

UE radio capability signalling optimisation (RACS) is a feature that is optional at both the UE and the network and which aims to optimise the transmission of UE radio capability over the radio interface (see TS 23.501). RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called the UE radio capability ID. A UE radio capability ID can be either manufacturer-assigned or network-assigned. The UE radio capability ID is an alternative to the signalling of the radio capabilities container over the radio interface.
In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access.
If the UE supports RACS:
  1. the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message;
  2. if the UE performs a registration procedure for initial registration and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID in the UE radio capability ID IE as a non-cleartext IE in the REGISTRATION REQUEST message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message;
  3. if the radio configuration at the UE changes (for instance because the UE has disabled a specific radio capability) then:
    1. if the UE has an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a registration procedure for mobility and periodic registration update. The UE shall include the applicable UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message and shall include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed". If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message; and
    2. if the UE does not have an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a registration procedure for mobility and periodic registration update and include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed";
  4. upon receiving a network-assigned UE radio capability ID in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall store the network-assigned UE radio capability ID and the PLMN ID or SNPN identity of the serving network along with a mapping to the current UE radio configuration in its non-volatile memory as specified in annex C. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs with the associated PLMN ID or SNPN identity and the mapping to the corresponding UE radio configuration;
  5. the UE shall not use a network-assigned UE radio capability ID assigned by a PLMN in PLMNs equivalent to the PLMN which assigned it;
  6. upon receiving a UE radio capability ID deletion indication IE set to "delete network-assigned UE radio capability IDs" in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall delete all network-assigned UE radio capability IDs stored at the UE for the serving network, initiate a registration procedure for mobility and periodic registration update and include an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, if available at the UE, in the UE radio capability ID IE of the REGISTRATION REQUEST message; and
  7. if the UE performs a registration procedure for mobility and periodic registration update due to entering a tracking area that is not in the list of tracking areas that the UE previously registered in the AMF and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID in the UE radio capability ID IE as a non-cleartext IE in the REGISTRATION REQUEST message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message.
If the network supports RACS:
  1. the network may assign a network-assigned UE radio capability ID to a UE which supports RACS by including a UE radio capability ID IE in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message;
  2. the network may trigger the UE to delete all network-assigned UE radio capability IDs stored at the UE for the serving network by including a UE radio capability ID deletion indication IE set to "delete network-assigned UE radio capability IDs" in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message; and
  3. the network may send an IDENTITY REQUEST message to the UE that supports RACS to retrieve the PEI, if not available in the network.
Up

4.17  5GS mobility management in NB-N1 mode |R16|Word‑p. 100
A UE in NB-N1 mode (see TS 36.331) shall calculate the value of the applicable NAS timer indicated in table 10.2.1 plus 240s.
The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted.
When an AMF that supports NB-N1 mode performs NAS signalling with a UE, which is using NB-N1 mode, the AMF shall calculate the value of the applicable NAS timer indicated in table 10.2.2 plus 240s.
The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted.
Up

4.18  5GS session management in NB-N1 mode |R16|Word‑p. 101
A UE in NB-N1 mode (see TS 36.331) shall calculate the value of the applicable NAS timer indicated in table 10.2.1 plus 180s.
The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted.
When an SMF that supports NB-N1 mode performs NAS signalling with a UE, which is using NB-N1 mode, the SMF shall calculate the value of the applicable NAS timer indicated in table 10.3.2 plus 180s.
The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted.
Up

4.19  5GS mobility management in WB-N1 mode for IoT |R16|

In WB-N1 mode, a UE operating in category CE can operate in either CE mode A or CE mode B (see TS 36.306). If a UE that supports CE mode B and operates in WB-N1 mode, the UE's usage setting is not set to "voice centric" (see TS 23.501), and:
  1. the use of enhanced coverage is not restricted by the network; or
  2. CE mode B is not restricted by the network (see TS 23.501);
the UE shall apply the value of the applicable NAS timer indicated in table 10.2.1 for WB-N1/CE mode.
A UE that supports CE mode B and operates in WB-N1 mode shall not apply the value of the applicable NAS timer indicated in table 10.2.1 for WB-N1/CE mode before receiving an indication from the network that the use of enhanced coverage is not restricted, or CE mode B is not restricted, as described in this subclause.
The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.
The support of CE mode B by a UE is indicated to the AMF by lower layers and shall be stored by the AMF. When an AMF that supports WB-N1 mode performs NAS signalling with a UE, which supports CE mode B and operates in WB-N1 mode, the UE's usage setting is not set to "voice centric" (see TS 23.501) and the AMF determines that:
  1. the use of enhanced coverage is not restricted for the UE; or
  2. CE mode B is not restricted for the UE (see TS 23.501);
the AMF shall calculate the value of the applicable NAS timer indicated in table 10.2.2 for WB-N1/CE mode.
The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.
Up

4.20  5GS session management in WB-N1 mode for IoT |R16|

In WB-N1 mode, a UE operating in category CE can operate in either CE mode A or CE mode B (see TS 36.306). If a UE that supports CE mode B and operates in WB-N1 mode and the UE's usage setting is not set to "voice centric" (see TS 23.501), and:
  1. the use of enhanced coverage is not restricted by the network; or
  2. CE mode B is not restricted by the network (see TS 23.501);
the UE shall apply the value of the applicable NAS timer indicated in table 10.3.1 for WB-N1/CE mode.
A UE that supports CE mode B and operates in WB-N1 mode shall not apply the value of the applicable NAS timer indicated in table 10.3.1 for WB-N1/CE mode before receiving an indication from the network that the use of enhanced coverage is not restricted, or CE mode B is not restricted, as described in this subclause.
The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.
If the use of extended NAS timer is indicated by the AMF (see TS 23.501 and TS 23.502), the SMF shall calculate the value of the applicable NAS timer indicated in table 10.3.2 for WB-N1/CE mode.
The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.
Up

Up   Top   ToC