hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.15 BSF Services | The following NF services are specified for BSF as described in TS 23.503 [45]:
Table 7.2.15-1: NF Services provided by BSF
Service Name
Description
Reference in TS 23.502 [3]
Nbsf_Management
Allows a PCF to register/deregister itself and to be discoverable by NF service consumers (NOTE 1).
5.2.13.2
NOTE 1: There may be both, a PCF for the PDU Session and a PCF for the UE. Each of them may separately and independently register itself at the BSF. Each of them may separately and independently be discovered by a consumer of the BSF. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.16 LMF Services | The following NF services are specified for LMF:
Table 7.2.16-1: NF Services provided by LMF
Service Name
Description
Reference in TS 23.273 [87]
Nlmf_Location
This service enables an NF to request location determination for a target UE for the Immediate Location Request and to subscribe / get notified of the location determination for a Deferred Location Request. It allow NFs to request or subscribe the current geodetic and optionally civic location of a target UE.
8.3.2
Nlmf_Broadcast
This service enables an NF to receive information related to broadcast of location assistance by an LMF.
8.3.3
Nlmf_DataExposure
This service enables an NF to request the LMF to collect and provision location related training data or monitoring data for an ML model and to receive related input data for ML Model training or ML Model performance monitoring. The ML Model can be used to calculate UE position.
8.3.4
7.2.16A GMLC Services
The following NF services are specified for GMLC:
Table 7.2.16A-1: NF Services provided by GMLC
Service Name
Description
Reference in TS 23.273 [87]
Ngmlc_Location
This service enables an NF to request location determination for a target UE.
8.4 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.17 CHF Services | The following NF services for spending limits and charging are specified for CHF.
Table 7.2.17-1: NF Services provided by CHF
Service Name
Description
Reference in TS 23.502 [3] or other TS
Nchf_SpendingLimitControl
This service enables transfer of policy counter status information relating to subscriber spending limits from CHF to NF consumer and described in TS 23.503 [45].
5.2.17
Nchf_Converged_Charging
This service enables converged online and offline charging.
TS 32.290 [67]
Nchf_OfflineOnlyCharging
This service enables only offline charging.
TS 32.290 [67] |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.18 UCMF Services | The following NF services are specified for UCMF:
Table 7.2.18-1: NF Services provided by UCMF
Service Name
Description
Reference in TS 23.502 [3]
Nucmf_Provisioning
Allows the NF consumer to provision a dictionary entry in the UCMF consisting of a Manufacturer-assigned UE Radio Capability ID, the corresponding UE Radio Capability for Paging and the corresponding UE radio capabilities and the (list of) associated IMEI/TAC value(s). The UE radio capabilities the NEF provides for a UE radio Capability ID can be in TS 36.331 [51] format, TS 38.331 [28] format or both formats. Also used for deletion (e.g. as no longer used) or update (e.g. to add or remove a (list of) IMEI/TAC value(s) associated to an entry) of dictionary entries in the UCMF.
5.2.18.2
Nucmf_UECapabilityManagement
Allows the NF consumer to resolve UE Radio Capability ID (either Manufacturer-assigned or PLMN-assigned) into the corresponding UE radio capabilities and the corresponding UE Radio Capability for Paging. The consumer shall indicate whether it requests a TS 36.331 [51] format or a TS 38.331 [28] format to be provided.
Allows the NF consumer to obtain a PLMN-assigned UE Radio Capability ID for a specific UE radio capabilities. The consumer shall indicate whether the UE radio capabilities sent to UCMF are in TS 36.331 [51] format, TS 38.331 [28], or both.
Allows the NF consumer to subscribe or unsubscribe for notifications of UCMF dictionary entries.
Allows the NF consumer to be notified about creation and deletion of UCMF dictionary entries.
5.2.18.3 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.19 AF Services | The following NF services are specified for AF:
Table 7.2.19-1: NF Services provided by AF
Service Name
Description
Reference in TS 23.502 [3] or other TS
Naf_EventExposure
This service enables consumer NF(s) to subscribe or get notified of the event as described in TS 23.288 [86].
5.2.19.2
Naf_ProSe
This service is for ProSe services as described in TS 23.304 [128].
TS 23.304 [128]
Naf_Authentication
This service enables the consumer to authenticate and authorize the Service Level Device Identity as described in TS 23.256 [136].
TS 23.256 [136] |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.20 NSSAAF Services | The following NF services are specified for NSSAAF:
Table 7.2.20 -1: NF Services provided by NSSAAF
Service Name
Description
Reference in TS 23.502 [3]
Nnssaaf_NSSAA
The NSSAAF provides NSSAA service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed. It also provides notification to the current AMF where the UE is of the need to re-authenticate and re-authorize the UE or to revoke the UE authorization.
5.2.20.2
Nnssaaf_AIW
The NSSAAF provides AIW (AAA interworking) service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed.
5.2.20.3 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.21 DCCF Services | The following NF services are specified for DCCF:
Table 7.2.21-1: NF Services provided by DCCF
Service Name
Description
Reference in TS 23.288 [86]
Ndccf_DataManagement
This service enables a Data Consumer to request data and have it delivered via a messaging framework or via the DCCF, while avoiding redundant requests to data sources.
8.2
Ndccf_ContextManagement
This service allows a network function to register/deregister the availability of data with the DCCF.
8.3 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.22 MFAF Services | The following NF services are specified for MFAF:
Table 7.2.22-1: NF Services provided by MFAF
Service Name
Description
Reference in TS 23.288 [86]
Nmfaf_3daDataManagement
This service allows a DCCF to request a messaging framework to provide collected data to consumers or notification endpoints according to processing and formatting instructions.
9.2
Nmfaf_3caDataManagement
This service allows a messaging framework to provide data to consumers or notification endpoints according to instructions received via the Nmfaf_3da_DataManagement service.
9.3
Nmfaf_ContextManagement
This service allows the transfer of an MFAF UE context to a consumer (e.g. a target MFAF).
9.4 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.23 ADRF Services | The following NF services are specified for ADRF:
Table 7.2.23-1: NF Services provided by ADRF
Service Name
Description
Reference in TS 23.288 [86]
Nadrf_DataManagement
This service allows consumers to store, retrieve and delete data or analytics in an ADRF.
10.2
Nadrf_MLModelManagement
This service allows consumers to store, retrieve and delete ML model(s) in an ADRF.
10.3 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.24 5G DDNMF Services | The 5G DDNMF supports the N5g-ddnmf service defined in clause 7.1 of TS 23.304 [128]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.25 EASDF Services | The following NF services are specified for EASDF.
Table 7.2.25-1: NF Services provided by EASDF
Service Name
Description
Reference in TS 23.548 [130]
Neasdf_DNSContext
This service enables the consumer to create, update and delete DNS context in EASDF, or subscribe to DNS message reporting from EASDF and receives the DNS security information of EASDF.
DNS contexts in EASDF include rules on how EASDF is to handle DNS messages.
7.1.2
Neasdf_BaselineDNSPattern
This service enables the consumer to create, update and delete BaselineDNSPattern in EASDF.
7.1.3 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.26 TSCTSF Services | The following NF services are specified for TSCTSF.
Table 7.2.26-1: NF Services provided by TSCTSF
Service Name
Description
Reference in TS 23.502 [3]
Ntsctsf_TimeSynchronization
Provides support for time synchronization service based on (g)PTP or 5G access stratum time distribution method as described in clause 5.27.1.8. Allows the NF consumer to subscribe for the UE and 5GC capabilities for (g)PTP or 5G access stratum based time synchronization service or time synchronization status information updates. Allows the NF consumer to configure the UEs and the 5GC for the (g)PTP based time synchronization service.
5.2.27.2
Ntsctsf_QoSand TSCAssistance
Allows the NF consumer to provide QoS parameters and information to create TSC Assistance Container.
5.2.27.3
Ntsctsf_ASTI
Provides support for time synchronization service based on 5G access stratum time distribution method as described in clause 5.27.1.8. Allows the NF consumer to configure the 5GC and RAN for 5G access stratum based time synchronization service for the UEs and subscribe to time synchronization status information updates.
5.2.27.4 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.27 NSACF Services | The following NF services are specified for NSACF:
Table 7.2.27-1: NF Services provided by NSACF
Service Name
Description
Reference in TS 23.502 [3]
Nnsacf_NSAC
This service enables consumer NF to check the availability per network slice and update the number of UEs registered with a network slice, or the number of UEs with at least one PDU Session/PDN Connection established on a network slice in the case of EPC interworking, or the number of PDU Sessions established on a network slice.
5.2.21.2
Nnsacf_SliceEventExposure
This service enables consumer NF(s) to subscribe and get notified of the event as described in clause 5.15.11.4.
5.2.21.4 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.28 MB-SMF Services | The following NF service is specified for MB-SMF.
Table 7.2.28-1: NF Services provided by MB-SMF
Service Name
Description
Reference in TS 23.247 [129]
Nmbsmf_TMGI
This service enables NF service consumer to allocate, refresh and deallocate TMGI(s).
9.1.2
Nmbsmf_MBSSession
This service enables the consumer to create, update and delete the MBS Session.
9.1.3 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.29 UPF Services | The following NF service is specified for UPF.
Table 7.2.29-1: NF Services provided by UPF
Service Name
Description
Reference in TS 23.502 [3]
Nupf_EventExposure
This service exposes UPF related information to the consumer NFs.
5.2.26.2
Nupf_GetUEPrivateIPaddrAndIdentifiers
This service exposes UPF information related to NAT information and SUPI.
5.2.26.3 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.30 SCP Services | The following NF service is specified for SCP.
Table 7.2.30-1: NF Services provided by SCP
Service Name
Description
Reference in TS 23.502 [3]
Nscp_EventExposure
This service exposes SCP related information to the consumer NFs.
5.2.28.2 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.2.31 EIF Services | The following NF service is specified for EIF.
Table 7.2.31-1: NF Services provided by EIF
Service Name
Description
Reference in TS 23.502 [3]
Neif_EventExposure
Enables other NF consumers to subscribe of the energy consumption information as described in clause 5.51.
5.2.28 |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 7.3 Exposure | Network exposure is described in clauses 5.20, 5.20d and in clause 4.15 of TS 23.502 [3]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8 Control and User Plane Protocol Stacks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.1 General | Clause 8 specifies the overall protocol stacks between 5GS entities, e.g. between the UE and the 5GC Network Functions, between the 5G-AN and the 5GC Network Functions, or between the 5GC Network Functions. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2 Control Plane Protocol Stacks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1 Control Plane Protocol Stacks between the 5G-AN and the 5G Core: N2 | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1.1 General | NOTE 1: N2 maps to NG-C as defined in TS 38.413 [34].
Following procedures are defined over N2:
- Procedures related with N2 Interface Management and that are not related to an individual UE, such as for Configuration or Reset of the N2 interface. These procedures are intended to be applicable to any access but may correspond to messages that carry some information only on some access (such as information on the default Paging DRX used only for 3GPP access).
- Procedures related with an individual UE:
- Procedures related with NAS Transport. These procedures are intended to be applicable to any access but may correspond to messages that for UL NAS transport carry some access dependent information such as User Location Information (e.g. Cell-Id over 3GPP access or other kind of User Location Information for Non-3GPP access).
- Procedures related with UE context management. These procedures are intended to be applicable to any access. The corresponding messages may carry:
- some information only on some access (such as Mobility Restriction List used only for 3GPP access).
- some information (related e.g. with N3 addressing and with QoS requirements) that is to be transparently forwarded by AMF between the 5G-AN and the SMF.
- Procedures related with resources for PDU Sessions. These procedures are intended to be applicable to any access. They may correspond to messages that carry information (related e.g. with N3 addressing and with QoS requirements) that is to be transparently forwarded by AMF between the 5G-AN and the SMF.
- Procedures related with Hand-Over management. These procedures are intended for 3GPP access only.
The Control Plane interface between the 5G-AN and the 5G Core supports:
- The connection of multiple different kinds of 5G-AN (e.g. 3GPP RAN, N3IWF for Un-trusted access to 5GC) to the 5GC via a unique Control Plane protocol: A single NGAP protocol is used for both the 3GPP access and non-3GPP access;
- There is a unique N2 termination point in AMF per access for a given UE regardless of the number (possibly zero) of PDU Sessions of the UE;
- The decoupling between AMF and other functions such as SMF that may need to control the services supported by 5G-AN(s) (e.g. control of the UP resources in the 5G-AN for a PDU Session). For this purpose, NGAP may support information that the AMF is just responsible to relay between the 5G-AN and the SMF. The information can be referred as N2 SM information in TS 23.502 [3] and this specification.
NOTE 2: The N2 SM information is exchanged between the SMF and the 5G-AN transparently to the AMF. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1.2 5G-AN - AMF | Legend:
- NG Application Protocol (NG-AP): Application Layer Protocol between the 5G-AN node and the AMF. NG-AP is defined in TS 38.413 [34].
- Stream Control Transmission Protocol (SCTP): This protocol guarantees delivery of signalling messages between AMF and 5G-AN node (N2). SCTP is defined in RFC 4960 [44].
Figure 8.2.1.2-1: Control Plane between the 5G-AN and the AMF |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.1.3 5G-AN - SMF | Legend:
- N2 SM information: This is the subset of NG-AP information that the AMF transparently relays between the 5G-AN and the SMF and is included in the NG-AP messages and the N11 related messages.
Figure 8.2.1.3-1: Control Plane between the 5G-AN and the SMF
NOTE 1: From the 5G-AN perspective, there is a single termination of N2 i.e. the AMF.
NOTE 2: For the protocol stack between the AMF and the SMF, see clause 8.2.3. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2 Control Plane Protocol Stacks between the UE and the 5GC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2.1 General | A single N1 NAS signalling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signalling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE.
The NAS protocol on N1 comprises a NAS-MM and a NAS-SM components.
There are multiple cases of protocols between the UE and a core network function (excluding the AMF) that need to be transported over N1 via NAS-MM protocol. Such cases include:
- Session Management Signalling.
- SMS.
- UE Policy.
- LCS.
RM/CM NAS messages in NAS-MM and other types of NAS messages (e.g. SM), as well as the corresponding procedures, are decoupled.
The NAS-MM supports generic capabilities:
- NAS procedures that terminate at the AMF. This includes:
- Handles Registration Management and Connection Management state machines and procedures with the UE, including NAS transport; the AMF supports following capabilities:
- Decide whether to accept the RM/CM part of N1 signalling during the RM/CM procedures without considering possibly combined other non NAS-MM messages (e.g. SM) in the same NAS signalling contents;
- Know if one NAS message should be routed to another NF (e.g. SMF), or locally processed with the NAS routing capabilities inside during the RM/CM procedures;
- Provide a secure NAS signalling connection (integrity protection, ciphering) between the UE and the AMF, including for the transport of payload;
- Provide access control if it applies;
- It is possible to transmit the other type of NAS message (e.g. NAS SM) together with an RM/CM NAS message by supporting NAS transport of different types of payload or messages that do not terminate at the AMF, i.e. NAS-SM, SMS, UE Policy and LCS between the UE and the AMF. This includes:
- Information about the Payload type;
- Additional Information for forwarding purposes
- The Payload (e.g. the SM message in the case of SM signalling);
- There is a Single NAS protocol that applies on both 3GPP and non-3GPP access. When an UE is served by a single AMF while the UE is connected over multiple (3GPP/Non 3GPP) accesses, there is a N1 NAS signalling connection per access.
Security of the NAS messages is provided based on the security context established between the UE and the AMF.
Figure 8.2.2.1-1 depicts NAS transport of SM signalling, SMS, UE Policy and LCS.
Figure 8.2.2.1-1 NAS transport for SM, SMS, UE Policy and LCS |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2.2 UE - AMF | Legend:
- NAS-MM: The NAS protocol for MM functionality supports registration management functionality, connection management functionality and user plane connection activation and deactivation. It is also responsible of ciphering and integrity protection of NAS signalling. 5G NAS protocol is defined in TS 24.501 [47]
- 5G-AN Protocol layer: This set of protocols/layers depends on the 5G-AN. In the case of NG-RAN, the radio protocol between the UE and the NG-RAN node (eNodeB or gNodeB) is specified in TS 36.300 [30] and TS 38.300 [27]. In the case of non-3GPP access, see clause 8.2.4.
Figure 8.2.2.2-1: Control Plane between the UE and the AMF |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.2.3 UE – SMF | The NAS-SM supports the handling of Session Management between the UE and the SMF.
The SM signalling message is handled, i.e. created and processed, in the NAS-SM layer of UE and the SMF. The content of the SM signalling message is not interpreted by the AMF.
The NAS-MM layer handles the SM signalling is as follows:
- For transmission of SM signalling:
- The NAS-MM layer creates a NAS-MM message, including security header, indicating NAS transport of SM signalling, additional information for the receiving NAS-MM to derive how and where to forward the SM signalling message.
- For reception of SM signalling:
- The receiving NAS-MM processes the NAS-MM part of the message, i.e. performs integrity check and interprets the additional information to derive how and where to derive the SM signalling message.
The SM message part shall include the PDU Session ID.
Legend:
- NAS-SM: The NAS protocol for SM functionality supports user plane PDU Session Establishment, modification and release. It is transferred via the AMF and transparent to the AMF. 5G NAS protocol is defined in TS 24.501 [47]
Figure 8.2.2.3-1: Control Plane protocol stack between the UE and the SMF |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.3 Control Plane Protocol Stacks between the network functions in 5GC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.3.1 The Control Plane Protocol Stack for the service based interface | The control plane protocol(s) for the service-based interfaces listed in clause 4.2.6 is defined in the TS 29.500 [49] |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.3.2 The Control Plane protocol stack for the N4 interface between SMF and UPF | The control plane protocol for SMF-UPF (i.e. N4 reference point) is defined in TS 29.244 [65]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.4 Control Plane for untrusted non 3GPP Access | Figure 8.2.4-1: Control Plane before the signalling IPsec SA is established between UE and N3IWF
Figure 8.2.4-2: Control Plane after the signalling IPsec SA is established between UE and N3IWF
Large NAS messages may be fragmented by the "inner IP" layer or by TCP.
Figure 8.2.4-3: Control Plane for establishment of user-plane via N3IWF
In the above figures 8.2.4-1, 8.2.4-2 and 8.2.4-3, the UDP protocol may be used between the UE and N3IWF to enable NAT traversal for IKEv2 and IPsec traffic.
The "signalling IPsec SA" is defined in clause 4.12.2 of TS 23.502 [3]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.5 Control Plane for trusted non-3GPP Access | Figure 8.2.5-1: Control Plane before the NWt connection is established between UE and TNGF
Figure 8.2.5-2: Control Plane after the NWt connection is established between UE and TNGF
Large NAS messages may be fragmented by the "inner IP" layer or by TCP.
Figure 8.2.5-3: Control Plane for establishment of user-plane via TNGF
In the above figures 8.2.5-2 and 8.2.5-3, the UDP protocol may be used between the UE and TNGF to enable NAT traversal for IKEv2 and IPsec traffic.
The NWt connection is defined in clause 4.2.8.3 and in clause 4.12a.2.2 of TS 23.502 [3]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.6 Control Plane for W-5GAN Access | The control plane for W-5GAN is defined in clause 6 of TS 23.316 [84]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.2.7 Control Plane for Trusted WLAN Access for N5CW Device | Figure 8.2.7-1: Control Plane for trusted WLAN access for N5CW device
The EAP protocol applies only for performing EAP-based access authentication procedure to connect to a trusted WLAN access network. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3 User Plane Protocol Stacks | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.1 User Plane Protocol Stack for a PDU Session | This clause illustrates the protocol stack for the User plane transport related with a PDU Session.
Legend:
- PDU layer: This layer corresponds to the PDU carried between the UE and the DN over the PDU Session. When the PDU Session Type is IPv4 or IPv6 or IPv4v6, it corresponds to IPv4 packets or IPv6 packets or both of them; When the PDU Session Type is Ethernet, it corresponds to Ethernet frames; etc.
- GPRS Tunnelling Protocol for the user plane (GTP‑U): This protocol supports tunnelling user data over N3 (i.e. between the 5G-AN node and the UPF) and N9 (i.e. between different UPFs of the 5GC) in the backbone network, details see TS 29.281 [75]. GTP shall encapsulate all end user PDUs. It provides encapsulation on a per PDU Session level. This layer carries also the marking associated with a QoS Flow defined in clause 5.7. This protocol is also used on N4 interface as defined in TS 29.244 [65].
Figure 8.3.1-1: User Plane Protocol Stack
- 5G-AN protocol stack: This set of protocols/layers depends on the AN:
- When the 5G-AN is a 3GPP NG-RAN, these protocols/layers are defined in TS 38.401 [42]. The radio protocol between the UE and the 5G-AN node (eNodeB or gNodeB) is specified in TS 36.300 [30] and TS 38.300 [27].
- When the AN is an Untrusted non 3GPP access to 5GC the 5G-AN interfaces with the 5GC at a N3IWF defined in clause 4.3.2 and the 5G-AN protocol stack is defined in clause 8.3.2.
- UDP/IP: These are the backbone network protocols.
NOTE 1: The number of UPF in the data path is not constrained by 3GPP specifications: there may be in the data path of a PDU Session 0, 1 or multiple UPF that do not support a PDU Session Anchor functionality for this PDU Session.
NOTE 2: The "non PDU Session Anchor" UPF depicted in the Figure 8.3.1-1 is optional.
NOTE 3: The N9 interface may be intra-PLMN or inter PLMN (in the case of Home Routed deployment).
If there is an UL CL (Uplink Classifier) or a Branching Point (both defined in clause 5.6.4) in the data path of a PDU Session, the UL CL or Branching Point acts as the non PDU Session Anchor UPF of Figure 8.3.1-1. In that case there are multiple N9 interfaces branching out of the UL CL / Branching Point each leading to different PDU Session anchors.
NOTE 4: Co-location of the UL CL or Branching Point with a PDU Session Anchor is a deployment option. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.2 User Plane for untrusted non-3GPP Access | Figure 8.3.2-1: User Plane via N3IWF
Large GRE packets may be fragmented by the "inner IP" layer.
Details about the PDU Layer, the N3 stack and the N9 stack are included in clause 8.3.1. The UDP protocol may be used below the IPsec layer to enable NAT traversal. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.3 User Plane for trusted non-3GPP Access | Figure 8.3.3-1: User Plane via TNGF
Large GRE packets may be fragmented by the "inner IP" layer.
Details about the PDU Layer, the N3 stack and the N9 stack are included in clause 8.3.1. The UDP protocol may be used below the IPsec layer to enable NAT traversal. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.4 User Plane for W-5GAN Access | The user plane for W-5GAN is defined in clause 6 of TS 23.316 [84]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.5 User Plane for N19-based forwarding of a 5G VN group | Figure 8.3.5-1: User Plane for N19-based forwarding
Details about the PDU Layer, PDU Session User Plane Protocol Stack are included in clause 8.3.1 and clause 8.3.2. The N19 is based on a shared User Plane tunnel connecting two PSA UPFs of a single 5G VN group. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 8.3.6 User Plane for Trusted WLAN Access for N5CW Device | Legend: - Transport: this layer refers to the transport of PDUs between the N5CW device and TWIF (see clause 4.2.8.5.4). In this Release of the specification, Trusted WLAN Access for N5CW Device only supports IP PDU Session type. Figure 8.2.8-1: User Plane for trusted WLAN access for N5CW device Annex A (informative): Relationship between Service-Based Interfaces and Reference Points Service-Based Interfaces and Reference Points are two different ways to model interactions between architectural entities. A Reference Point is a conceptual point at the conjunction of two non-overlapping functional groups (see TR 21.905 [1]). In figure A-1 the functional groups are equivalent to Network Functions. A reference point can be replaced by one or more service-based interfaces which provide equivalent functionality. Figure A-1: Example show a Reference Point replaced by two Service based Interfaces Figure A-2: Example showing a Reference Point replaced by a single Service based Interface Reference points exist between two specific Network Functions. Even if the functionality is equal on two reference points between different Network Functions there has to be a different reference point name. Using the service-based interface representation it is immediately visible that it is the same service-based interface and that the functionality is equal on each interface. Figure A-3: Reference Points vs. Service-based Interfaces representation of equal functionality on the interfaces A NF may expose one or more services through Service based interfaces. Figure A-4: One or more Services exposed by one Network Function Annex B (normative): Mapping between temporary identities When interworking procedures with N26 are used and the UE performs idle mode mobility from 5GC to EPC the following mapping from 5G GUTI to EPS GUTI applies: - 5G <MCC> maps to EPS <MCC> - 5G <MNC> maps to EPS <MNC> - 5G <AMF Region ID> and 5G <AMF Set ID> maps to EPS <MMEGI> and part of EPS <MMEC> - 5G <AMF Pointer> map to part of EPS <MMEC> - 5G <5G-TMSI> maps to EPS <M-TMSI> NOTE 1: The mapping described above does not necessarily imply the same size for the 5G GUTI and EPS GUTI fields that are mapped. The size of 5G GUTI fields and other mapping details will be defined in TS 23.003 [19]. NOTE 2: To support interworking with the legacy EPC core network entity (i.e. when MME is not updated to support interworking with 5GS), it is assumed that the 5G <AMF Region ID> and EPS <MMEGI> is partitioned to avoid overlapping values in order to enable discovery of source node (i.e. MME or AMF) without ambiguity. Once the EPS in the PLMN has been updated to support interworking with 5GS, the full address space of the AMF Region ID can be used for 5GS. Annex C (informative): Guidelines and Principles for Compute-Storage Separation 5G System Architecture allows any NF/NF Service to store and retrieve its unstructured data (e.g. UE contexts) into/from a Storage entity (e.g. UDSF) as stated in clause 4.2.5 in this release of the specification. This clause highlights some assumptions, principles regarding NF/NF services that use this Storage entity for storing unstructured data: 1. It is up to the Network Function implementation to determine whether the Storage entity is used as a Primary Storage (in which case the corresponding context stored within the NF/NF Service is deleted after storage in the Storage entity) or the Storage entity is used as a Secondary Storage (in which case the corresponding context within the NF/NF Service is stored). 2. It is up to the NF/NF Service implementation to determine the trigger (e.g. at the end of Registration procedure, Service Request procedure etc) for storing unstructured data (e.g. UE contexts) in the Storage entity but it is a good practice for NF/NF service to store stable state in the Storage entity. 3. Multiple NF/NF service instances may require to access the same stored data in the Storage entity (e.g. UE context), around the same time, then the resolution the race condition is implementation specific. 4. All NFs within the same NF Set are assumed to have access to the same unstructured data stored within the Storage entity. 5. AMF planned removal with UDSF (clause 5.21.2.2.1) and AMF auto-recovery (with UDSF option in clause 5.21.2.3) assume that a storage entity/UDSF is used either as a primary storage or secondary storage by the AMF for storing UE contexts. 6. It is up to implementation of the Storage entity to make sure that only NFs that are authorized for a certain data record can access this data record. Annex D (informative): 5GS support for Non-Public Network deployment options D.1 Introduction This annex provides guidance on how 5GS features and capabilities can be used to support various Non-Public Network deployment options. Overlay network: When UE is accessing SNPN service via NWu using user plane established in PLMN, SNPN is the overlay network. When UE is accessing PLMN services via NWu using user plane established in SNPN, PLMN is the overlay network. Underlay network: When UE is accessing SNPN service via NWu using user plane established in PLMN, PLMN is the underlay network. When UE is accessing PLMN services via NWu using user plane established in SNPN, SNPN is the underlay network D.2 Support of Non-Public Network as a network slice of a PLMN The PLMN operator can provide access to an NPN by using network slicing mechanisms. NOTE: Access to PLMN services can be supported in addition to PNI-NPN services, e.g. based on different S-NSSAI/DNN for different services. The following are some considerations in such a PNI-NPN case: 1. The UE has subscription and credentials for the PLMN; 2. The PLMN and NPN service provider have an agreement of where the NPN Network Slice is to be deployed (i.e. in which TAs of the PLMN and optionally including support for roaming PLMNs); 3. The PLMN subscription includes support for Subscribed S-NSSAI to be used for the NPN (see clause 5.15.3); 4. The PLMN operator can offer possibilities for the NPN service provider to manage the NPN Network Slice according to TS 28.533 [79]. 5. When the UE registers the first time to the PLMN, the PLMN can configure the UE with URSP including NSSP associating Applications to the NPN S-NSSAI (if the UE also is able to access other PLMN services); 6. The PLMN can configure the UE with Configured NSSAI for the Serving PLMN (see clause 5.15.4); 7. The PLMN and NPN can perform a Network Slice specific authentication and authorization using additional NPN credentials; 8. The UE follows the logic as defined for Network Slicing, see clause 5.15; 9. The network selection logic, access control etc are following the principles for PLMN selection; and 10. The PLMN may indicate to the UE that the NPN S-NSSAI is rejected for the RA when the UE moves out of the coverage of the NPN Network Slice. However, limiting the availability of the NPN S-NSSAI would imply that the NPN is not available outside of the area agreed for the NPN S-NSSAI, e.g. resulting in the NPN PDU Sessions being terminated when the UE moves out of the coverage of the NPN Network Slice. Similarly access to NPN DNNs would not be available via non-NPN cells. 11. In order to prevent access to NPNs for authorized UE(s) in the case of network congestion/overload and if a dedicated S-NSSAI has been allocated for an NPN, the Unified Access Control can be used using the operator-defined access categories with access category criteria type (as defined in TS 24.501 [47]) set to the S-NSSAI used for an NPN. 12. If NPN isolation is desired, it is assumed that a dedicated S-NSSAI is configured for the NPN and that the UE is configured to operate in Access Stratum Connection Establishment NSSAI Inclusion Mode a, b or c, see clause 5.15.9, such that NG-RAN receives Requested NSSAI from the UE and it can use the S-NSSAI for AMF selection. D.3 Support for access to PLMN services via Stand-alone Non-Public Network and access to Stand-alone Non Public Network services via PLMN Figure D.3-1: Access to PLMN services via Stand-alone Non-Public Network NOTE 1: The reference architecture in Figure D.3-1 and Figure D.3-2 only shows the network functions directly connected to the UPF or N3IWF and other parts of the architecture are same as defined in clause 4.2. In order to obtain access to PLMN services when the UE is camping in NG-RAN of Stand-alone Non-Public Network, the UE obtains IP connectivity, discovers and establishes connectivity to an N3IWF in the PLMN. In the Figure D.3-1, the N1 (for NPN) represents the reference point between UE and the AMF in Stand-alone Non-Public Network. The NWu (for PLMN) represents the reference point between the UE and the N3IWF in the PLMN for establishing secure tunnel between UE and the N3IWF over the Stand-alone Non-Public Network. N1 (for PLMN) represents the reference point between UE and the AMF in PLMN. Figure D.3-2: Access to Stand-alone Non-Public Network services via PLMN In order to obtain access to Non-Public Network services when the UE is camping in NG-RAN of a PLMN, the UE obtains IP connectivity, discovers and establishes connectivity to an N3IWF in the Stand-alone Non-Public Network. In Figure D.3-2, the N1 (for PLMN) represents the reference point between UE and the AMF in the PLMN. The NWu (for NPN) represents the reference point between the UE and the N3IWF in the stand-alone Non-Public Network for establishing a secure tunnel between UE and the N3IWF over the PLMN. The N1 (for NPN) represents the reference point between UE and the AMF in NPN. When using the mechanism described above to access overlay network via underlay network, the overlay network can act as authorized 3rd party with AF to interact with NEF in the underlay network, to use the existing network exposure capabilities provided by the underlay network defined in clause 4.15 of TS 23.502 [3]. This interaction is subject of agreements between the overlay and the underlay network. D.4 Support for UE capable of simultaneously connecting to an SNPN and a PLMN When a UE capable of simultaneously connecting to an SNPN and a PLMN and the UE is not set to operate in SNPN access mode for any of the Uu/Yt/NWu interfaces, the UE only performs PLMN selection procedures using the corresponding interface for connection to the PLMN. A UE supporting simultaneous connectivity to an SNPN and a PLMN applies the network selection as applicable for the access and network for SNPN and PLMN respectively. Whether the UE uses SNPN or PLMN for its services is implementation dependent. A UE supporting simultaneous connectivity to an SNPN and a PLMN applies the cell (re-)selection as applicable for the access and network for SNPN and PLMN respectively. Whether the UE uses SNPN or PLMN for its services is implementation dependent. D.5 Support for keeping UE in CM-CONNECTED state in overlay network when accessing services via NWu When UE is accessing the overlay network via the underlay network as described in clause D.3, it is possible to keep the UE in CM-CONNECTED state in the overlay network: - UE maintains at least one PDU Session in underlay network, from where the N3IWF of the overlay network is reachable via the DN of the PDU Session in underlay network. In this case, the UE is considered as successfully connected to the non-3GPP access of the overlay network, thus UE always attempts to transit to CM-CONNECTED state from CM-IDLE, as described in NOTE 3 in clause 5.5.2. - IKEv2 liveness check procedure initiated either by UE or N3IWF as defined in clause 7.8 and clause 7.9 of TS 24.502 [48] can be utilized to ensure the signalling connection between UE and N3IWF is still valid when UE stays in CM-CONNECTED state. Adjusting the time interval of the liveness check to avoid the deletion of the IKEv2 SA due to inactivity, on both endpoints of the SA. - If NAT is used, so as to avoid a timeout of the NAT entries between the UPF in the underlay network and the N3IWF in the overlay network, NAT-Traversal mechanisms described in RFC 7296 [60] and NAT-Keepalive described in RFC 3948 [138] are recommended. - AMF in overlay network keeps the UE in CM-CONNECTED state unless UE or N3IWF triggers the release. - The NG-RAN node in the underlay network can use the existing information to decide an appropriate RRC state for the UE (e.g. whether release a UE to RRC_INACTIVE). D.6 Support for session/service continuity between SNPN and PLMN when using N3IWF Depending on the UE's radio capability and implementation, the following existing mechanisms can be used to allow session/service continuity between SNPN and PLMN: - For Single Radio UE which includes single Rx/Tx and dual Rx/single Tx UE, seamless service continuity is not supported in this release when the UE is moving between the 3GPP access networks of SNPN and PLMN because of the single radio limitation. But the PDU session continuity between SNPN and PLMN can be realized by utilizing the existing handover procedure between non-3GPP access and 3GPP access as defined in clause 4.9.2 of TS 23.502 [3], where one network is acting as non-3GPP access of the other network. - For Dual Radio (Dual Rx/Dual Tx) UE, the service continuity can be achieved by utilizing the existing handover procedure between non-3GPP access and 3GPP access for PDU session on a single access and the existing user plane resource addition procedure for MA PDU session, where one network is acting as non-3GPP access of the other network - For PDU session on a single access, UE can register to the same 5GC via both Uu and NWu interfaces from two networks when it is possible, by following the procedure defined in clause 4.2.2 of TS 23.502 [3] if the registration is via Uu, or in clause 4.12.2 of TS 23.502 [3] if the registration is via NWu. The registration via NWu utilizes the user plane which is established in another 5GC using another network's Uu interface. For example, if UE is moving out of its SNPN 3GPP access coverage and would like to continue its SNPN service in PLMN, UE can register to its SNPN 5GC via PLMN's 3GPP access network using NWu interface with SNPN's 5GC before moving out SNPN NG-RAN coverage. Upon mobility, the existing handover procedure between non-3GPP access and 3GPP access defined in clause 4.9.2 of TS 23.502 [3] can be utilized. - For MA PDU session, if supported by UE and network, UE can register to the same 5GC via Uu and NWu interfaces and establish MA PDU session with ATSSS support to be anchored in the 5GC as defined in clause 4.22.2.2 of TS 23.502 [3], where one network is acting as non-3GPP access of the other network (Figure D.6-1 shows the example of UE with MA PDU session anchored in SNPN UPF when connected to SNPN via Uu and NWu interfaces). Upon mobility, UE can add/activate the user plane resource to the corresponding access type basing on the procedures defined in clause 4.22.7 of TS 23.502 [3]. Figure D.6-1: MA PDU session with ATSSS support for dual radio UE accessing to Stand-alone Non-Public Network services via Uu and NWu interfaces D.7 Guidance for underlay network to support QoS differentiation for User Plane IPsec Child SA D.7.1 Network initiated QoS When UE is accessing an overlay network via an underlay network as described in clause D.3, in order to ensure the underlay network to support the QoS required by the overlay network User Plane IPsec Child SA, the QoS differentiation mechanism based on network-initiated QoS modification as described in clause 5.30.2.7 and clause 5.30.2.8 can be used with the following considerations: - An overlay network service can have specific QoS requirement that needs to be fulfilled by the underlay network, based on SLA between the two networks. - The SLA covers selective services of the overlay network which require QoS support in underlay network. The rest of the overlay network traffic could be handled in best efforts basis by underlay network. - The SLA between the overlay network and the underlay network includes a mapping between DSCP values of the User Plane IPsec Child SAs and the QoS requirement of the overlay network services. The QoS requirement includes the QoS parameters described in clause 5.7.2 that are necessary (e.g. 5QI, ARP, etc.) during the network-initiated QoS modification in underlay network. In order to facilitate the SLA, a guidance for details of the mapping between DSCP values of the User Plane IPSec Child SAs and QoS requirement of the overlay network services is described of TS 29.513 [133]. The SLA also includes the N3IWF IP address of the overlay network. - The mapping agreed in SLA is configured at N3IWF of the overlay network and at the SMF/PCF of the underlay network. If a dedicated DNN/S-NSSAI is used in the underlay network for providing access to the N3IWF in the overlay network, the SMF/PCF in the underlay network can be configured to enable packet detection (based on N3IWF IP address and DSCP value) for PDU sessions associated with the dedicated DNN/S-NSSAI. - When UE establishes a PDU Session in underlay network, the PCF in the underlay network determines PCC rules based on UE subscription information and local configuration which takes into account the SLA described above and installs the PCC rules on the SMF which generates and installs PDR/URR on UPF. The PCC rules indicate N3IWF IP address and the DSCP values of the User Plane IPsec Child SAs of the overlay network which require QoS differentiation by the underlay network. So, the UPF in the underlay network can detect packets of the User Plane IPsec Child SAs corresponding to the overlay network services which require QoS support by the underlay network. - UE registers and establishes PDU Session in the overlay network via the User Plane connectivity established in the underlay network. When UE is accessing a specific service of overlay network, a QoS Flow can be created by the overlay network, then N3IWF creates dedicated User Plane IPsec Child SA for each overlay network QoS Flow that requires underlay network QoS support. - N3IWF uses the QoS profile and the Session-AMBR it receives from SMF in overlay network along with the mapping agreed in the SLA to derive a specific DSCP value for the User Plane IPsec Child SA. N3IWF assigns a specific DSCP value only to one User Plane IPsec Child SA for a UE at the same time. UE (for UL) and N3IWF (for DL) will set the DSCP marking in the outer IP header of the User Plane IPsec Child SA accordingly. - The overlay network traffic between UE and N3IWF using the specific DSCP marking will be detected by the UPF in the underlay network, based on previous installed PDR/URR. The SMF/PCF in underlay network will be informed when the overlay network traffic is detected. Then the PCF installs new PCC rules on the SMF including the QoS parameters for handling of packets corresponding to the specific User Plane IPsec Child SA based on the N3IWF IP address and the DSCP value of the User Plane IPsec Child SA and the SMF generates a QoS profile that triggers the PDU Session Modification procedure as described in clause 4.3.3 of TS 23.502 [3]. The QoS parameters are derived from the mapping agreed in SLA based on the detected DSCP value. D.7.2 UE initiated QoS When UE is accessing an overlay network via an underlay network as described in clause D.3, if UE-initiated QoS modification in clause 5.30.2.7 and clause 5.30.2.8 is used, the following principles can be considered to enable consistent QoS for User Plane IPsec Child SAs between the two networks: - UE registers and establishes PDU Session in the overlay network via the User Plane connectivity established in the underlay network. When UE is accessing a specific service of overlay network, a QoS Flow in overlay network can be created according to clause 4.3.3 of TS 23.502 [3]. UE receives the QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR, as specified in TS 24.501 [47]) from SMF/PCF in overlay network for the QoS Flow which is created for the specific overlay network service. - N3IWF in overlay network creates dedicated User Plane IPsec Child SA for each overlay network QoS Flow that requires underlay network QoS support. - In order to ensure the traffic of the overlay network service is handled with the desired QoS in underlay network, UE can request new QoS Flow for the PDU session in the underlay network, by PDU Session Modification procedure described in clause 4.3.3 of TS 23.502 [3]. The requested QoS can be derived from the QoS Flow level QoS parameters which the UE has received from the overlay network. The Packet Filter in the QoS rule of the request includes overlay network N3IWF IP address and SPI associated with the User Plane IPsec Child SA. - SMF in the underlay network notifies the PCF that the UE has initiated resource modification, after receiving the PDU Session Modification Request. PCF in the underlay network determines if the request can be authorized based on UE subscription and local policy which can take into account the SLA between overlay network and underlay network. If the request is authorized, PCF generates new PCC rule and installs on SMF in order to create new QoS Flow in underlay network using the QoS Flow level QoS parameters from the overlay network. The PDR/FAR generated refers to the N3IWF IP address and the SPI (provided by the UE in Traffic filter in PDU Session Modification request) to enable filtering and mapping of DL traffic towards the right PDU Session/QoS Flow within the underlay network. - If SLA exists, it can include a mapping between the DSCP values of the User Plane IPsec Child SAs and the QoS requirement of the overlay network services. The SLA is configured at N3IWF in overlay network and at SMF/PCF in underlay network. N3IWF can provide DSCP value to UE for the User Plane IPsec Child SA at PDU Session Establishment (clause 4.12.5, step 4a and 4c of TS 23.502 [3]). UE can include the DSCP value as an addition in the Packet Filter by initiating the PDU Session Modification procedure in the underlay network. PCF in the underlay network performs QoS authorization of UE QoS request considering the UE subscription and local configuration which takes into account the mapping in the SLA. Details of the mapping between DSCP values of the User Plane IPSec Child SAs and QoS requirement of the overlay network services is described in TS 29.513 [133]. Annex E (informative): Communication models for NF/NF services interaction E.1 General This annex provides a high level description of the different communication models that NF and NF services can use to interact which each other. Table E.1-1 summarizes the communication models, their usage and how they relate to the usage of an SCP. Table E.1-1: Communication models for NF/NF services interaction summary Communication between consumer and producer Service discovery and request routing Communication model Direct communication No NRF or SCP; direct routing A Discovery using NRF services; no SCP; direct routing B Indirect communication Discovery using NRF services; selection for specific instance from the Set can be delegated to SCP. Routing via SCP C Discovery and associated selection delegated to an SCP using discovery and selection parameters in service request; routing via SCP D Model A - Direct communication without NRF interaction: Neither NRF nor SCP are used. Consumers are configured with producers' "NF profiles" and directly communicate with a producer of their choice. Model B - Direct communication with NRF interaction: Consumers do discovery by querying the NRF. Based on the discovery result, the consumer does the selection. The consumer sends the request to the selected producer. Model C - Indirect communication without delegated discovery: Consumers do discovery by querying the NRF. Based on discovery result, the consumer does the selection of an NF Set or a specific NF instance of NF set. The consumer sends the request to the SCP containing the address of the selected service producer pointing to a NF service instance or a set of NF service instances. In the latter case, the SCP selects an NF Service instance. If possible, the SCP interacts with NRF to get selection parameters such as location, capacity, etc. The SCP routes the request to the selected NF service producer instance. Model D - Indirect communication with delegated discovery: Consumers do not do any discovery or selection. The consumer adds any necessary discovery and selection parameters required to find a suitable producer to the service request. The SCP uses the request address and the discovery and selection parameters in the request message to route the request to a suitable producer instance. The SCP can perform discovery with an NRF and obtain a discovery result. Figure E.1-1 depicts the different communication models. Figure E.1-1: Communication models for NF/NF services interaction Annex F (informative): Redundant user plane paths based on multiple UEs per device This clause describes an approach to realize multiple user plane paths in the system based on a device having multiple UEs and specific network deployments. The approach assumes a RAN deployment where redundant coverage by multiple gNBs (in the case of NR) is generally available. Upper layer protocols, such as the IEEE 802.1 TSN (Time Sensitive Networking), can make use of the multiple user plane paths. The UEs belonging to the same terminal device request the establishment of PDU Sessions that use independent RAN and CN network resources using the mechanisms outlined below. This deployment option has a number of preconditions: - The redundancy framework uses separate gNBs to achieve user plane redundancy over the 3GPP system. It is however up to operator deployment and configuration whether separate gNBs are available and used. If separate gNBs are not available for a device, the redundancy framework may still be applied to provide user plane redundancy in the rest of the network as well as between the device and the gNB using multiple UEs. - Terminal devices integrate multiple UEs which can connect to different gNBs independently. - RAN coverage is redundant in the target area: it is possible to connect to multiple gNBs from the same location. To ensure that the two UEs connect to different gNBs, the gNBs need to operate such that the selection of gNBs can be distinct from each other (e.g. gNB frequency allocation allows the UE to connect to multiple gNBs). - The core network UPF deployment is aligned with RAN deployment and supports redundant user plane paths. - The underlying transport topology is aligned with the RAN and UPF deployment and supports redundant user plane paths. - The physical network topology and geographical distribution of functions also supports the redundant user plane paths to the extent deemed necessary by the operator. - The operation of the redundant user plane paths is made sufficiently independent, to the extent deemed necessary by the operator, e.g. independent power supplies. Figure F-1 illustrates the architecture view. UE1 and UE2 are connected to gNB1 and gNB2, respectively and UE1 sets up a PDU Session via gNB1 to UPF1, while UE2 sets up a PDU Session via gNB2 to UPF2. UPF1 and UPF2 connect to the same Data Network (DN), but the traffic via UPF1 and UPF2 might be routed via different user plane nodes within the DN. UPF1 and UPF2 are controlled by SMF1 and SMF2, respectively. Figure F-1: Architecture with redundancy based on multiple UEs in the device The approach comprises the following main components shown as example using NR in figure F-2. - gNB selection: The selection of different gNBs for the UEs in the same device is realized by the concept of UE Reliability Groups for the UEs and also for the cells of gNBs. By grouping the UEs in the device and cells of gNBs in the network into more than one reliability group and preferably selecting cells in the same reliability group as the UE, it is ensured that UEs in the same device can be assigned different gNBs for redundancy as illustrated in Figure F-2, where UE1 and the cells of gNB1 belong to reliability group A and UE2 and the cells of gNB2 belong to reliability group B. Figure F-2: Reliability group-based redundancy concept in RAN For determining the reliability grouping of a UE, one of the following methods or a combination of them can be used: - It could be configured explicitly to the UE and sent in a Registration Request message to the network using an existing parameter (such as an S-NSSAI in the Requested NSSAI where the SST is URLLC; the Reliability Group can be decided by the SD part). - It could also be derived from existing system parameters (e.g. SUPI, PEI, S-NSSAI, RFSP) based on operator configuration. The Reliability Group of each UE is represented via existing parameters and sent from the AMF to the RAN when the RAN context is established, so each gNB has knowledge about the reliability group of the connected UEs. NOTE: An example realisation can be as follows: the UE's Allowed NSSAI can be used as input to select the RFSP index value for the UE. The RAN node uses the RFSP for RRM purposes and can based on local configuration determine the UE's Reliability Group based on the S-NSSAI in Allowed NSSAI and/or S-NSSAI for the PDU Session(s). The reliability group of the RAN (cells of gNBs) entities are pre-configured by the O&M system in RAN. It is possible for gNBs to learn the reliability group neighbouring cells as the Xn connectivity is set up, or the reliability group of neighbouring cells are also configured into the gNBs. In the case of connected mode mobility, the serving gNB prioritizes candidate target cells that belong to different reliability group than the UE. It follows that normally the UE is handed over only to cells in the same reliability group. If cells in the same reliability group are not available (UE is out of the coverage of cells of its own reliability group or link quality is below a given threshold) the UE may be handed over to a cell in another reliability group as well. If the UE connects to a cell whose reliability group is different from the UE's reliability group, the gNB initiates a handover to a cell in the appropriate reliability group whenever such a suitable cell is available. In the case of an Idle UE, it is possible to use the existing cell (re-)selection priority mechanism, with a priori UE config using dedicated signalling (in the RRCConnectionRelease message during transition from connected to idle mode) to configure the UE to reselect the cells of the appropriate reliability group for camping in deployments where the cell reliability groups use different sets of frequencies. - UPF selection. UPF selection mechanisms as described in clause 6.3.3 can be used to select different UPFs for the UEs within the device. The selection may be based either on UE configuration or network configuration of different DNNs leading to the same DN, or different slices for the two UEs. It is possible to use the UE's Reliability Group, described above for gNB selection, as an input to the UPF selection. The proper operator configuration of the UPF selection can ensure that the path of the PDU Sessions of UE1 and UE2 are independent. - Control plane. The approach can optionally apply different control plane entities for the individual UEs within the device. This may be achieved by using: - different DNNs for the individual UEs within the device to select different SMFs, - or applying different slices for the individual UEs within the device either based on UE configuration or network subscription, to select different AMFs and/or SMFs. Annex G (informative): SCP Deployment Examples G.1 General This Annex provides deployment examples for the SCP but is not meant to be an exhaustive list of deployment options for the SCP. The first example G.1 is based on an SCP implement using (network wide) service mesh technology, while the second example builds on SCP and 5GC functions as independent deployment units. G.2 An SCP based on service mesh G.2.1 Introduction This clause describes an SCP deployment based on a distributed model in which SCP endpoints are co-located with 5GC functionality (e.g. an NF, an NF Service, a subset thereof such as a microservice implementing part of an NF/NF service or a superset thereof such as a group of NFs, NF Services or microservices). This example makes no assumptions as to the internal composition of each 5GC functionality (e.g. whether they are internally composed of multiple elements or whether such internal elements communicate with means other than the service mesh depicted in this example). In this deployment example, Service Agent(s) implementing necessary peripheral tasks (e.g. an SCP endpoint) are co-located with 5GC functionality, as depicted in Figure G.2.1-1. In this example, Service Agents and 5GC functionality, although co-located, are separate components. Figure G.2.1-1: Deployment unit: 5GC functionality and co-located Service Agent(s) implementing peripheral tasks In this deployment example, an SCP Service Agent, i.e. a service communication proxy, is co-located in the same deployment unit with 5GC functionality and provides each deployed unit (e.g. a container-based VNFC) with indirect communication and delegated discovery. Figure G.2.1-2 shows an overview of this deployment scenario. For SBI-based interactions with other 5GC functionalities, a consumer (5GC functionality A) communicates through its Service Agent via SBI. Its Service Agent selects a target producer based on the request and routes the request to the producer's (5GC functionality B) Service Agent. What routing and selection policies a Service Agent applies for a given request is determined by routing and selection policies pushed by the service mesh controller. Information required by the service mesh controller is pushed by the Service Agents to the service mesh controller. In this deployment, the SCP manages registration and discovery for communication within the service mesh and it interacts with an external NRF for service exposure and communication across service mesh boundaries. Operator-defined policies are additionally employed to generate the routing and selection policies to be used by the Service Agents. This example depicts only SBI-based communication via a service mesh, but it does not preclude the simultaneous use of the service mesh for protocols other than SBI supported by the service mesh or that the depicted 5GC functionality additionally communicates via other means. Figure G.2.1-2: SCP Service mesh co-location with 5GC functionality From a 3GPP perspective, in this deployment example a deployment unit thus contains NF functionality and SCP functionality. Figure G.2.1-3 depicts the boundary between both 3GPP entities. In the depicted example, two NF Services part of the same NF and each exposing an SBI interface are deployed each in a container-based VNFC. A co-located Service Agent provides each NF Service with indirect communication and delegated discovery. Figure G.2.1-3: Detail of the NF-SCP boundary G.2.2 Communication across service mesh boundaries It is a deployment where a single service mesh covers all functionality within a given deployment or not. In cases of communication across the boundaries of a service mesh, the service mesh routing the outbound message knows neither whether the selected producer is in a service mesh nor the internal topology of the potential service mesh where the producer resides. In such a deployment, as shown in Figure G.2.2.-1, after producer selection is performed, routing policies on the outgoing service mesh are only aware of the next hop. Given a request sent by A, A's Service Agent will perform producer selection based on the received request. If the selected producer endpoint (e.g. D) is determined to be outside of Service Mesh 1, A's Service Agent routes the request to the Egress Proxy. For a successful routing, the Egress Proxy needs to be able to determine the next hop of the request. In this case, this is the Ingress Proxy of Service Mesh 2. The Ingress Proxy of Service Mesh 2 is, based on the information in the received request and its routing policies, able to determine the route for the request. Subsequently, D receives the request. No topology information needs to be exchanged between Service Mesh 1 and Service Mesh 2 besides a general routing rule towards Service Mesh 2 (e.g. a FQDN prefix) and an Ingress Proxy destination for requests targeting endpoints in Service Mesh 2. Figure G.2.2-1: Message routing across service mesh boundaries G.3 An SCP based on independent deployment units This clause shows an overview of SCP deployment based on the 5GC functionality and SCP being deployed in independent deployment units. Figure G.3-1: Independent deployment units for SCP and 5GC functionality The SCP deployment unit can internally make use of microservices, however these microservices are up to vendors implementation and can be for example SCP agents and SCP controller as used in this example. The SCP agents implement the http intermediaries between service consumers and service producers. The SCP agents are controlled by the SCP controller. Communication between SCP controller and SCP agents is via SCP internal interface (4) and up to vendors implementation. In this model it is a deployment choice to co-locate SCP and other 5GC functions or not. The SCP interfaces (1), (2) and (3) are service based interfaces. SCP itself is not a service producer itself, however acting as http proxy it registers services on behave of the producers in NRF. Interface (2) represents same services as (1) however using SCP proxy addresses. Interface (3) is interfacing NRF e.g. for service registration on behalf of the 5GC functions or service discovery. Figure G.3-2: 5GC functionality and SCP co-location choices For SBI-based interactions with other 5GC functions, a consumer communicates through a SCP agent via SBI (1). SCP agent selects a target based on the request and routes the request to the target SCP agent (2). What routing and selection policies each SCP agent applies for a given request is determined by routing and selection policies determined by the SCP controller using for example information provided via NRF (3) or locally configured in the SCP controller. The routing and selection information is provided by the SCP controller to the SCP agents via SCP internal interface (4). Direct communication can coexist in the same deployment based on 3GPP specified mechanisms. Figure G.3-3: Overview of SCP deployment G.4 An SCP deployment example based on name-based routing G.4.0 General Information This clause provides a deployment example for the SCP which is based on a name-based routing mechanism that provides IP over ICN capabilities such as those described in Xylomenos, George, et al. [G1]. The scenario describes an SCP offering based on an SBA-platform to interconnect 5GC Services (or a subset of the respective services). The Name-based Routing mechanism, described in this deployment example, is realized through a Path Computation Element which is the core part of the SCP. The 5GC Services are running as microservices on cloud/deployment units (clusters). A Service Router is the communication node (access node/gateway) between the SCP and the 5GC Services and resides as a single unit within a Service Deployment Cluster. The Service Router acts as communication proxy and it is responsible for mapping IP based messages onto ICN publication and subscriptions. The Service Router serves multiple 5GC Service Endpoints within that cluster. For direct communication the Service Router is not used. 5GC Functionalities communicate with the Service Router using standardized 3GPP SBIs. The Functionalities within the Service Deployment Cluster are containerized Service Functions. Depicted in Figure G.4-1, the Service Router act as SCP termination point and offer the SBI to the respective 5GC Service Functionalities. In this example, Service Routers and 5GC functionality, although co-located, are separate components within the Service Deployment Cluster. Multiple Functionalities can exist within the Service Deployment Cluster, all served by the respective Service Router when needed to communicate to other Service Functionalities within different clusters. Figure G.4-1: Deployment unit: 5GC functionality and co-located Service Agent(s) implementing peripheral tasks In Figure G.4-1, the two depicted 5GC Service Functionalities (realized as Network Function Service Instances) may communicate in two ways. However, before the communication can be established between two 5GC Functionalities, Service Registration and Service Discovery need to take place, as described in Figure G.4.1-1. Service Registration and Service Discovery are provided in a standardized manner using 3GPP Service Based Interfaces. G.4.1 Service Registration and Service Discovery Service registration can be done in several ways. One option is that ready 5GC Service Functions may register themselves with their service profile via the Nnrf interface. The registration request is forwarded to the internal Registry as well as forwarded to the operator's NRF. The internal registration is used to store the address to identifier relationship and the Service Deployment Cluster location. The external registration (NRF) is used to expose the Service Functionality to Services outside the depicted SCP. Service discovery entails Function A requesting a resolvable identifier for Functionality B. This resolve request is received by the Service Router which performs the task with the help of the SCP. After the resolve is done, the 5GC Functionalities may communicate either directly without any further interaction through the SCP, when the targeted address is resolved within the same Service Deployment Cluster; or via the Service Router when the Functionality resides outside of the originator's Service Deployment Cluster. The Service Router then acts as gateway towards the underlying SCP platform. Figure G.4.1-1: Registering 5GC Functionalities in the SCP G.4.2 Overview of Deployment Scenario Figure G.4.2-1 shows an overview of this deployment scenario. For SBI-based interactions with other 5GC functionalities, a consumer entity (e.g. 5GC functionality B in the cluster on the left side) communicates through the cluster's Service Router with other entities in other clusters (e.g. 5GC Functionality D in the cluster on the right side). The target selection is performed through the platform's Discovery Service. From the client's perspective, the Service Router is the first and only contact point to the SCP. The platform resolves the requested Service identifier and aligns the results with the platform's policies. The Path Computation Element calculates a path between the consumer and the producer (e.g. the shortest path between the nodes). Figure G.4.2-1: (NbR-) SCP interconnects multiple deployment clusters with external NRF G.4.3 References [G1] Xylomenos, George, et al.: "IP over ICN goes live", 2018 European Conference on Networks and Communications (EuCNC). IEEE, 2018. Annex H (normative): PTP usage guidelines H.1 General This Annex provides guidelines on the use of certain specific IEEE parameters and protocol messages in the case of TSN as described in clause 5.27. H.2 Signalling of ingress time for time synchronization The ingress timestamp (TSi) of the PTP event (e.g. Sync) message is provided from the ingress TT (NW-TT/UPF or DS-TT/UE) to the egress TT, if supported in the PTP messages as described in clauses 5.27.1.2.2.1 and 5.27.1.2.2.2 using the Suffix field defined in clause 13.4 of IEEE Std 1588 [126]. The structure of the Suffix field follows the recommendation of clause 14.3 of IEEE Std 1588 [126], with an organizationId specific to 3GPP, an organizationSubType referring to an ingress timestamp and data field that carries the ingress timestamp encoded as specified in clause 5.3.3 of IEEE Std 1588 [126]. TS 24.535 [117] specifies the coding of the ingress timestamp in the (g)PTP messages between a DS-TT and a NW-TT. H.3 Void H.4 Path and Link delay measurements The procedure described in this clause is applicable if DS-TT and NW-TT support operating as a boundary clock or as a time-aware system or as peer to peer Transparent Clock or end to end Transparent Clock and when the PTP instance in 5GS is configured to operate as a time-aware system or as a Boundary Clock or as peer to peer Transparent Clock or as end to end Transparent Clock. Whether DS-TT/NW-TT support operating as a boundary clock or peer to peer Transparent Clock or end to end Transparent Clock or as a time-aware system (support of the IEEE Std 802.1AS [104] PTP profile) may be determined as described in clause K.2.1. PTP ports in DS-TT and NW-TT may support the following delay measurement mechanisms: - Delay request-response mechanism as described in clause 11.3 of IEEE Std 1588 [126]; - Peer-to-peer delay mechanism as defined in clause 11.4 of IEEE Std 1588 [126]; - Common Mean Link Delay Service. Depending on the measurement mechanisms supported by DS-TT and NW-TT as well as the configured clock mode of 5GS, the PTP ports in DS-TT and NW-TT are configured as follows: - PTP ports configured to operate as a time-aware system according to IEEE Std 802.1AS [104] may be configured to use the peer-to-peer delay mechanism or Common Mean Link Delay Service; - PTP ports configured to operate as a Boundary Clock according to IEEE Std 1588 [126] may be configured to use the delay request-response mechanism, the peer-to-peer delay mechanism or Common Mean Link Delay Service. - PTP ports in 5GS configured to operate as a peer-to-peer Transparent Clock according to IEEE Std 1588 [126] shall use the peer-to-peer delay mechanism. - PTP ports in 5GS configured to operate as an end-to-end Transparent Clock according to IEEE Std 1588 [126] do not actively participate in path and link measurements mechanisms but shall calculate and add residence time and delay asymmetry information to PTP messages as defined in clause 10.2.2 of IEEE Std 1588 [126]. If DS-TT and NW-TT support operating as an end-to-end Transparent Clock, then the residence time for one-step operation as an end-to-end Transparent Clock for the path and link measurements is calculated as follows: - Upon reception of a PTP Delay_Req/Pdelay_Req/Pdely_Resp message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for the message. - The ingress timestamp is conveyed to the egress TT via the PDU Session as described in clause H.2. - The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP message for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. If needed, the PTP port in the egress TT convert the calculated resident time in 5GS into the residence time expressed in PTP GM time e.g. by means of the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126]. - The PTP port in the egress TT modifies the payload of the PTP Delay_Req/Pdelay_Req/Pdelay_Resp message that it sends towards the downstream PTP instance as follows: - Adds the calculated residence time to the correction field. - Removes Suffix field that contains TSi. If DS-TT and NW-TT support operating as an end-to-end Transparent Clock, then the residence time for two-step operation as an end-to-end Transparent Clock for the path and link measurements is calculated as follows: - Upon reception of a PTP Delay_Req/Pdelay_Req/Pdelay_Resp message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for the message. - If the ingress TT receives a Pdelay_Resp message with the twoStepFlag set to FALSE, then the ingress TT modifies the twoStepFlag to TRUE and creates a PTP Pdelay_Resp_Follow_Up message. - The ingress timestamp is conveyed to the egress TT via the PDU Session as described in clause H.2. - The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP message for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. If needed, the PTP port in the egress TT converts the calculated residence time in 5GS into the residence time expressed in PTP GM time, e.g. by means of the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126]. The egress TT then stores the calculated residence time expressed in PTP GM time and removes Suffix field that contains TSi before sending the PTP Delay_Req/Pdelay_Req/Pdelay_Resp message towards the downstream PTP instance. - Upon reception of the PTP Delay_Resp message associated with the PTP Delay_Req, the egress TT for the PTP Delay_Req message (i.e. the ingress TT for the PTP Delay_Resp message) modifies the payload of the PTP Delay_Resp message that it sends towards the ingress TT of the PTP Delay_Req message (i.e. egress TT for the PTP Delay_Resp message) as follows: - Adds the (previously stored) calculated residence time to the correction field. - Upon reception (or local creation) of the PTP Pdelay_Resp_Follow_Up message associated with the previously received PTP Pdelay_Resp message, the ingress TT for the PTP Pdelay_Resp_Follow_Up message modifies the payload of the PTP Pdelay_Resp_Follow_Up message that it sends towards the egress TT for the PTP Pdelay_Resp_Follow_Up message as follows: - Adds the (previously stored) calculated residence time of the associated PTP Pdelay_Req message to the correction field. - Upon reception of the PTP Pdelay_Resp_Follow_Up message associated with the PTP Pdelay_Resp, the egress TT for PTP Pdelay_Resp_Follow_Up message modifies the payload of the PTP Pdelay_Resp_Follow_Up message that it sends towards the downstream PTP instance as follows: - Adds the (previously stored) calculated residence time of the associated PTP Pdelay_Resp messages to the correction field. Annex I (normative): TSN usage guidelines I.1 Determination of traffic pattern information As described in clause 5.27.2, the calculation of the TSCAI relies upon mapping of information for the TSN stream(s) based upon certain IEEE standard information. Additional traffic pattern parameters such as maximum burst size and maximum flow bitrate can be mapped to MDBV and GFBR. The traffic pattern parameter determination based on PSFP (IEEE Std 802.1Q [98]), when available, is as follows: - Periodicity of a TSN stream is set equal to StreamGateAdminCycleTime if there is only one StreamGateControlEntry with a StreamGateStatesValue set to Open in the StreamGateAdminControlList. If there is more than one StreamGateGateControlEntry with a StreamGateStatesValue set to Open in the StreamGateAdminControlList, then the Periodicity of the TSN Stream is set equal to sum of the timeIntervalValues from the first gate open instance to a next gate open instance in the StreamGateAdminControlList. For aggregated TSN streams with same periodicity and compatible Burst Arrival Times, the periodicity of the aggregated flow of these TSN Streams is set equal to StreamGateAdminCycleTime received from CNC for one of the TSN streams that are aggregated. NOTE 1: Given that only TSN streams that have the same periodicity and compatible Burst Arrival Time can be aggregated, the StreamGateAdminCycleTime for those TSN streams is assumed to be the same. - Burst Arrival time of a TSN stream at the ingress port is determined based on the following conditions: - The Burst Arrival Time of a TSN Stream should be set to StreamGateAdminBaseTime plus the sum of the timeIntervalValues for which the StreamGateStatesValue is Closed in the StreamGateAdminControlList until the first gate open time (i.e. until StreamGateStatesValue set to Open is found). If the StreamGateStatesValue is Open for the first timeIntervalValue, then the Burst Arrival time is set to StreamGateAdminBaseTime. For aggregated TSN streams, the arrival time is calculated similarly, but using the time interval to the first StreamGateStatesValue that is Open from the aggregated TSN streams. - Burst Size of a TSN stream at the ingress port (which is useful to map to MDBV) is determined based on the following conditions: - The Burst Size may be determined from TSN Stream gate control operations in the StreamGateAdminControlList. If in the StreamGateAdminControlList, IntervalOctetMax is provided for a StreamGateControlEntry with an "open" StreamGateStatesValue, the Burst Size is set to the IntervalOctetMax for that control list entry. If IntervalOctetMax is not provided, the Burst Size is set to the timeIntervalValue (converted from ns to s) of the StreamGateControlEntry with an "open" StreamGateStatesValue multiplied by the port bitrate. - When multiple compatible TSN Streams are aggregated, the Burst Size is set to the sum of the Burst Sizes for each TSN stream as determined above. - Maximum Flow Bitrate of a TSN stream (which is useful to map to GBR) is determined as follows: - The Maximum Flow Bitrate of a TSN Stream is equal to the summation of all timeIntervalValue (converted from ns to s) with StreamGateStatesValue = Open, multiplied by the bitrate of the corresponding port and divided by StreamGateAdminCycleTime. For aggregated TSN streams, the same calculation is performed over the burst of aggregated streams (calculated using superposition, i.e. timeIntervalValue with StreamGateStatesValue = Open of every stream is summed up, as they are assumed to have same periodicity, compatible Burst arrival time and same traffic class if they are to be aggregated. When CNC configures the PSFP information to the TSN AF, the TSN AF may use local information (e.g. local configuration) to map the PSFP information to an ingress port and/or egress port of the 5GS bridge. NOTE 2: As an example, for the local configuration, the PSFP can use either the destination MAC address and VLAN identifier, or the source MAC address and VLAN identifier for stream identification. The TSN AF is pre-configured with either the MAC address of Ethernet hosts behind a given DS-TT port (identified by the DS-TT port MAC address), or the VLAN identifier used over a given DS-TT port, or both. When the TSN AF determines that one of the known Ethernet host's MAC address appears as a source or destination MAC address, it can identify that the ingress or egress port is the associated DS-TT port. Annex J (informative): Link MTU considerations According to clause 5.6.10.4 networks can provide link MTU size for UEs. A purpose of the link MTU size provisioning is to limit the size of the packets sent by the UE to avoid packet fragmentation in the backbone network between the UE and the UPF acting as PSA (and/or across the N6 reference point). Fragmentation within the backbone network creates a significant overhead. Therefore operators might desire to avoid it. This Annex presents an overhead calculation that can be used by operators to set the link MTU size provided by the network. A UE might not employ the provided link MTU size, e.g. when the MT and TE are separated, as discussed in clause 5.6.10.4. Therefore, providing an MTU size does not guarantee that there will be no packets larger than the provided value. However, if UEs follow the provided link MTU value operators will benefit from reduced transmission overhead within backbone networks. One of the worst-case scenarios is when GTP packets, e.g. between a NG-RAN node and the 5GC, are transferred over IPSec tunnel in an IPv6 deployment. In that case the user packet first encapsulated in a GTP tunnel which results in the following overhead: - IPv6 header, which is 40 octets; - UDP overhead, which is 8 octets; - Extended GTP-U header, which is 16 octets. NOTE 1: The sending of a Reflective QoS Indicator within a GTP-U header extension, or the use of Long PDCP PDU numbers at handover , or the use of some other features specified in Release 17 or later Releases will further increase the GTP-U header size (see TS 29.281 [75] and TS 38.415 [116]). NOTE 2: For UEs that start their PDN connection in EPS and can be subject to mobility to 5GS, the operator can use this smaller 5GS link MTU in EPS, rather than the EPS link MTU suggested by Annex C of TS 23.060 [56]. In this scenario the GTP packet then further encapsulated into an IPSec tunnel. The actual IPSec tunnel overhead depends on the used encryption and integrity protection algorithms. TS 33.210 [115] mandates the support of AES-GMAC with a key length of 128 bits and the use of HMAC_SHA-1 for integrity protection. Therefore, the overhead with those algorithms is calculated as: - IPv6 header, which is 40 octets; - IPSec Security Parameter Index and Sequence Number overhead, which is 4+4 octets; - Initialization Vector for the encryption algorithm, which is 16 octets; - Padding to make the size of the encrypted payload a multiple of 16; - Padding Length and Next Header octets (2 octets); - Integrity Check Value, which is 12 octets. In order to make the user packet size as large as possible a padding of 0 octet is assumed. With this zero padding assumption the total overhead is 142 octets, which results a maximum user packet size of transport MTU minus 142 octets. Note that in the case of transport MTU=1500, this user packet size will result in a 1424 octets payload length to be ciphered, which is a multiple of 16, thus the assumption that no padding is needed is correct (see Figure J.1). Similar calculations can be done for networks with transport that supports larger MTU sizes. Figure J-1: Overhead calculation for transport MTU=1500 octet The link MTU value that can prevent fragmentation in the backbone network between the UE and the UPF acting as PSA depends on the actual deployment. Based on the above calculation a link MTU value of 1358 is small enough in most of the network deployments. However for network deployments where the transport uniformly supports for example ethernet jumbo frames, transport MTU<=9216 octets can provide a much larger UE MTU and hence more efficient transfer of user data. One example of when it can be ensured that all links support larger packet sizes, is when the UE uses a specific Network Slice with a limited coverage area. Note that using a link MTU value smaller than necessary would decrease the efficiency in the network. Moreover, a UE might also apply some tunnelling (e.g. VPN). It is desirable to use a link MTU size that assures at least MTU minus 220 octets within the UE tunnel to avoid the fragmentation of the user packets within the tunnel applied in the UE. In the case transport MTU is 1500 octets, this results a link MTU of 1280 octets (for the transport), which is the minimum MTU size in the case of IPv6. The above methodology can be modified for calculation of the UE's link MTU when a UPF has MTU limits on the N6 reference point and is offering a PDU Session with Ethernet or Unstructured PDU Session type between the UPF and the UE. Annex K (normative): Port and user plane node management information exchange K.1 Standardized port and user plane node management information Table K.1-1 and Table K.1-2 list standardized port management information and user plane node management information, respectively. Table K.1-1: Standardized port management information Port management information Applicability (see NOTE 6) Supported operations by TSN AF Supported operations by TSCTSF Reference DS-TT NW-TT (see NOTE 1) (see NOTE 1) General Port management capabilities (see NOTE 2) X X R R Bridge delay related information txPropagationDelay X X R - IEEE Std 802.1Q [98] clause 12.32.2.1 txPropagationDelayDeltaThreshold (see NOTE 23) X X RW Traffic class related information Traffic class table X X RW - IEEE Std 802.1Q [98] clause 12.6.3 and clause 8.6.6. Gate control information queueMaxSDUTable IEEE Std 802.1Q [98], clause 12.29.1 > queueMaxSDU X X RW IEEE Std 802.1Q [98], clause 12.29.1 > TransmissionOverrun (see NOTE 3) X X R IEEE Std 802.1Q [98], clause 12.29.1 GateEnabled X X RW - IEEE Std 802.1Q [98] Table 12-32 AdminGateStates X X RW IEEE Std 802.1Q [98] Table 12-32 AdminBaseTime X X RW - IEEE Std 802.1Q [98] Table 12-32 AdminControlList X X RW - IEEE Std 802.1Q [98] Table 12-32 AdminCycleTime (see NOTE 3) X X RW - IEEE Std 802.1Q [98] Table 12-32 AdminControlListLength (see NOTE 3) X X RW - IEEE Std 802.1Q [98] Table 12-32 AdminCycleTimeExtension X X RW - IEEE Std 802.1Q [98] Table 12-32 Tick granularity X X R - IEEE Std 802.1Q [98] Table 12-32 SupportedListMax X X R - IEEE Std 802.1Q [98] Table 12-32 General Neighbor discovery configuration (NOTE 4) adminStatus D X RW - IEEE Std 802.1AB [97] clause 9.2.5.1 lldpV2LocChassisIdSubtype D X RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2LocChassisId D X RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2MessageTxInterval D X RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2MessageTxHoldMultiplier D X RW - IEEE Std 802.1AB [97] Table 11-2 NW-TT port neighbor discovery configuration lldpV2LocPortIdSubtype X RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2LocPortId X RW - IEEE Std 802.1AB [97] Table 11-2 OtlvSet X RW - IEC/IEEE 60802 [216], clause 6.5.2.4.5 and clause 6.5.2.4.6. DS-TT port neighbor discovery configuration lldpV2LocPortIdSubtype D RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2LocPortId D RW - IEEE Std 802.1AB [97] Table 11-2 OtlvSet D RW - IEC/IEEE 60802 [216], clause 6.5.2.4.5 and clause 6.5.2.4.6. Neighbor discovery information for each discovered neighbor of NW-TT (NOTE 26) lldpV2RemChassisIdSubtype X R - IEEE Std 802.1AB [97] Table 11-2 lldpV2RemChassisId X R - IEEE Std 802.1AB [97] Table 11-2 lldpV2RemPortIdSubtype X R - IEEE Std 802.1AB [97] Table 11-2 lldpV2RemPortId X R - IEEE Std 802.1AB [97] Table 11-2 TTL X R - IEEE Std 802.1AB [97] clause 8.5.4 OtlvSet X R - IEC/IEEE 60802 [216], clause 6.5.2.4.5 and clause 6.5.2.4.6. Neighbor discovery information for each discovered neighbor of DS-TT (NOTE 5) lldpV2RemChassisIdSubtype D R - IEEE Std 802.1AB [97] Table 11-2 lldpV2RemChassisId D R - IEEE Std 802.1AB [97] Table 11-2 lldpV2RemPortIdSubtype D R - IEEE Std 802.1AB [97] Table 11-2 lldpV2RemPortId D R - IEEE Std 802.1AB [97] Table 11-2 TTL D R - IEEE Std 802.1AB [97] clause 8.5.4.1 OtlvSet D R - IEC/IEEE 60802 [216], clause 6.5.2.4.5 and clause 6.5.2.4.6. Information for deterministic networking for each NW-TT port (NOTE 27) Interface information Interface type X R IETF RFC 8343 [151] Interface enabled status X R IETF RFC 8343 [151] phys-address X R IETF RFC 8343 [151] IPv4 information IPv4 enabled status X R IETF RFC 8344 [152] IPv4 forwarding status X R IETF RFC 8344 [152] IPv4 MTU X R IETF RFC 8344 [152] Information for each IPv4 address IPv4 address X R IETF RFC 8344 [152] prefix-length X R IETF RFC 8344 [152] netmask X R IETF RFC 8344 [152] origin X R IETF RFC 8344 [152] Information for each IPv4 neighbor IPv4 address X R IETF RFC 8344 [152] link-layer-address X R IETF RFC 8344 [152] origin X R IETF RFC 8344 [152] IPv6 information IPv6 enabled status X R IETF RFC 8344 [152] IPv6 forwarding status X R IETF RFC 8344 [152] IPv6 MTU X R IETF RFC 8344 [152] Information for each IPv6 address IPv6 address X R IETF RFC 8344 [152] prefix-length X R IETF RFC 8344 [152] origin X R IETF RFC 8344 [152] status X R IETF RFC 8344 [152] Information for each IPv6 neighbor IPv6 address X R IETF RFC 8344 [152] link-layer-address X R IETF RFC 8344 [152] origin X R IETF RFC 8344 [152] is-router X R IETF RFC 8344 [152] state X R IETF RFC 8344 [152] Stream Parameters (NOTE 11) MaxStreamFilterInstances X R - IEEE Std 802.1Q [98] clause 12.31.1.1 MaxStreamGateInstances X R - IEEE Std 802.1Q [98] clause 12.31.1.2 MaxFlowMeterInstances X R - IEEE Std 802.1Q [98] clause 12.31.1.3 SupportedListMax X R - IEEE Std 802.1Q [98] clause 12.31.1.4 Per-Stream Filtering and Policing information (NOTE 10) Stream Filter Instance Table (NOTE 8) - IEEE Std 802.1Q [98] Table 12-35 > StreamFilterInstanceIndex X X RW - IEEE Std 802.1Q [98] Table 12-35 > Stream Identification type X X RW - IEEE 802.1CB [83] clause 9.1.1.6 > Stream Identification Controlling Parameters X X RW - IEEE 802.1CB [83] clauses 9.1.2, 9.1.3, 9.1.4 (NOTE 12) > PrioritySpec X X RW - IEEE Std 802.1Q [98] Table 12-35 > StreamGateInstanceID X X RW - IEEE Std 802.1Q [98] Table 12-35 Stream Gate Instance Table (NOTE 9) IEEE Std 802.1Q [98] Table 12-33 StreamGateInstanceIndex X X RW - IEEE Std 802.1Q [98] Table 12-36 StreamGateAdminBaseTime X X RW - IEEE Std 802.1Q [98] Table 12-36 StreamGateAdminControlList X X RW - IEEE Std 802.1Q [98] Table 12-36 StreamGateAdminCycleTime X X RW - IEEE Std 802.1Q [98] Table 12-36 StreamGateTickGranularity X X R - IEEE Std 802.1Q [98] Table 12-36 StreamGateAdminCycleTimeExtension X X R - IEEE Std 802.1Q [98] Table 12-36 Time Synchronization Information TSN Time domain number (NOTE 24) X X RW Supported PTP instance types (NOTE 13) X R R IEEE Std 1588 [126] clause 8.2.1.5.5 Supported transport types (NOTE 14) X R R Supported delay mechanisms (NOTE 15) X R R IEEE Std 1588 [126] clause 8.2.15.4.4 PTP grandmaster capable (NOTE 16) X R R gPTP grandmaster capable (NOTE 17) X R R Supported PTP profiles (NOTE 18) X R R Number of supported PTP instances X R R PTP instance specification PTP Instance ID (NOTE 25) X X RW RW > PTP profile (NOTE 19) X RW RW > Transport type (NOTE 20) X RW RW > Grandmaster enabled (NOTE 21) X RW RW IEEE Std 1588 [126] data sets (NOTE 22) > defaultDS.clockIdentity X RW RW IEEE Std 1588 [126] clause 8.2.1.2.2 > defaultDS.clockQuality.clockClass X RW RW IEEE Std 1588 [126] clause 8.2.1.3.1.2 > defaultDS.clockQuality.clockAccuracy X RW RW IEEE Std 1588 [126] clause 8.2.1.3.1.3 > defaultDS.clockQuality.offsetScaledLogVariance X RW RW IEEE Std 1588 [126] clause 8.2.1.3.1.4 > defaultDS.priority1 X RW RW IEEE Std 1588 [126] clause 8.2.1.4.1 > defaultDS.priority2 X RW RW IEEE Std 1588 [126] clause 8.2.1.4.2 > defaultDS.domainNumber X RW RW IEEE Std 1588 [126] clause 8.2.1.4.3 > defaultDS.sdoId X RW RW IEEE Std 1588 [126] clause 8.2.1.4.5 > defaultDS.instanceEnable X RW RW IEEE Std 1588 [126] clause 8.2.1.5.2 > defaultDS.instanceType X RW RW IEEE Std 1588 [126] clause 8.2.1.5.5 > portDS.portIdentity X X RW RW IEEE Std 1588 [126] clause 8.2.15.2.1 > portDS.portState X X R R IEEE Std 1588 [126] clause 8.2.15.3.1 > portDS.logMinDelayReqInterval X X RW RW IEEE Std 1588 [126] clause 8.2.15.3.2 > portDS.logAnnounceInterval X X RW RW IEEE Std 1588 [126] clause 8.2.15.4.1 > portDS.announceReceiptTimeout X RW RW IEEE Std 1588 [126] clause 8.2.15.4.2 > portDS.logSyncInterval X X RW RW IEEE Std 1588 [126] clause 8.2.15.4.3 > portDS.delayMechanism X X RW RW IEEE Std 1588 [126] clause 8.2.15.4.4 > portDS.logMinPdelayReqInterval X X RW RW IEEE Std 1588 [126] clause 8.2.15.4.5 > portDS.versionNumber X X RW RW IEEE Std 1588 [126] clause 8.2.15.4.6 > portDS.minorVersionNumber X X RW RW IEEE Std 1588 [126] clause 8.2.15.4.7 > portDS.delayAsymmetry X X RW RW IEEE Std 1588 [126] clause 8.2.15.4.8 > portDS.portEnable X X RW RW IEEE Std 1588 [126] clause 8.2.15.5.1 > timePropertiesDS.currentUtcOffset X RW RW IEEE Std 1588 [126] clause 8.2.4.2 > timePropertiesDS.timeSource X RW RW IEEE Std 1588 [126] clause 8.2.4.9 > externalPortConfigurationPortDS.desiredState RW RW IEEE Std 1588 [126] clause 15.5.3.7.15.1 IEEE Std 802.1AS [104] data sets (NOTE 22) > defaultDS.clockIdentity X RW RW IEEE Std 802.1AS [104] clause 14.2.2 > defaultDS.clockQuality.clockClass X RW RW IEEE Std 802.1AS [104] clause 14.2.4.2 > defaultDS.clockQuality.clockAccuracy X RW RW IEEE Std 802.1AS [104] clause 14.2.4.3 > defaultDS.clockQuality.offsetScaledLogVariance X RW RW IEEE Std 802.1AS [104] clause 14.2.4.4 > defaultDS.priority1 X RW RW IEEE Std 802.1AS [104] clause 14.2.5 > defaultDS.priority2 X RW RW IEEE Std 802.1AS [104] clause 14.2.6 > defaultDS.timeSource X RW RW IEEE Std 802.1AS [104] clause 14.2.15 > defaultDS.domainNumber X RW RW IEEE Std 802.1AS [104] clause 14.2.16 > defaultDS.sdoId X RW RW IEEE Std 802.1AS [104] clause 14.2.4.3 > defaultDS.instanceEnable X RW RW IEEE Std 802.1AS [104] clause 14.2.19 > portDS.portIdentity X RW RW IEEE Std 802.1AS [104] clause 14.8.2 > portDS.portState X R R IEEE Std 802.1AS [104] clause 14.8.3 > portDS.ptpPortEnabled X X RW RW IEEE Std 802.1AS [104] clause 14.8.4 > portDS.delayMechanism X X RW RW IEEE Std 802.1AS [104] clause 14.8.5 > portDS.isMeasuringDelay X X R R IEEE Std 802.1AS [104] clause 14.8.6 > portDS.asCapable X X R R IEEE Std 802.1AS [104] clause 14.8.7 > portDS.meanLinkDelay X X R R IEEE Std 802.1AS [104] clause 14.8.8 > portDS.meanLinkDelayThresh X X RW RW IEEE Std 802.1AS [104] clause 14.8.9 > portDS.delayAsymmetry X X RW RW IEEE Std 802.1AS [104] clause 14.8.10 > portDS.neighborRateRatio X X R R IEEE Std 802.1AS [104] clause 14.8.11 > portDS.initialLogAnnounceInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.12 > portDS.currentLogAnnounceInterval X X R R IEEE Std 802.1AS [104] clause 14.8.13 > portDS.useMgtSettableLogAnnounceInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.14 > portDS.mgtSettableLogAnnounceInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.15 > portDS.announceReceiptTimeout X RW RW IEEE Std 802.1AS [104] clause 14.8.16 > portDS.initialLogSyncInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.17 > portDS.currentLogSyncInterval X X R R IEEE Std 802.1AS [104] clause 14.8.18 > portDS.useMgtSettableLogSyncInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.19 > portDS.mgtSettableLogSyncInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.20 > portDS.syncReceiptTimeout X RW RW IEEE Std 802.1AS [104] clause 14.8.21 > portDS.syncReceiptTimeoutTimeInterval X RW RW IEEE Std 802.1AS [104] clause 14.8.22 > portDS.initialLogPdelayReqInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.23 > portDS.currentLogPdelayReqInterval X X R R IEEE Std 802.1AS [104] clause 14.8.24 > portDS.useMgtSettableLogPdelayReqInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.25 > portDS.mgtSettableLogPdelayReqInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.26 > portDS.initialLogGptpCapableMessageInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.27 > portDS.currentLogGptpCapableMessageInterval X X R R IEEE Std 802.1AS [104] clause 14.8.28 > portDS.useMgtSettableLogGptpCapableMessageInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.29 > portDS.mgtSettableLogGptpCapableMessageInterval X X RW RW IEEE Std 802.1AS [104] clause 14.8.30 > portDS.initialComputeNeighborRateRatio X X RW RW IEEE Std 802.1AS [104] clause 14.8.31 > portDS.currentComputeNeighborRateRatio X X R R IEEE Std 802.1AS [104] clause 14.8.32 > portDS.useMgtSettableComputeNeighborRateRatio X X RW RW IEEE Std 802.1AS [104] clause 14.8.33 > portDS.mgtSettableComputeNeighborRateRatio X X RW RW IEEE Std 802.1AS [104] clause 14.8.34 > portDS.initialComputeMeanLinkDelay X X RW RW IEEE Std 802.1AS [104] clause 14.8.35 > portDS.currentComputeMeanLinkDelay X X R R IEEE Std 802.1AS [104] clause 14.8.36 > portDS.useMgtSettableComputeMeanLinkDelay X X RW RW IEEE Std 802.1AS [104] clause 14.8.37 > portDS.mgtSettableComputeMeanLinkDelay X X RW RW IEEE Std 802.1AS [104] clause 14.8.38 > portDS.allowedLostResponses X X RW RW IEEE Std 802.1AS [104] clause 14.8.39 > portDS.allowedFaults X X RW RW IEEE Std 802.1AS [104] clause 14.8.40 > portDS.gPtpCapableReceiptTimeout X X RW RW IEEE Std 802.1AS [104] clause 14.8.41 > portDS.versionNumber X X RW RW IEEE Std 802.1AS [104] clause 14.8.42 > portDS.nup X X RW RW IEEE Std 802.1AS [104] clause 14.8.43 > portDS.ndown X X RW RW IEEE Std 802.1AS [104] clause 14.8.44 > portDS.oneStepTxOper X X R R IEEE Std 802.1AS [104] clause 14.8.45 > portDS.oneStepReceive X X R R IEEE Std 802.1AS [104] clause 14.8.46 > portDS.oneStepTransmit X X R R IEEE Std 802.1AS [104] clause 14.8.47 > portDS.initialOneStepTxOper X X RW RW IEEE Std 802.1AS [104] clause 14.8.48 > portDS.currentOneStepTxOper X X RW RW IEEE Std 802.1AS [104] clause 14.8.49 > portDS.useMgtSettableOneStepTxOper X X RW RW IEEE Std 802.1AS [104] clause 14.8.50 > portDS.mgtSettableOneStepTxOper X X RW RW IEEE Std 802.1AS [104] clause 14.8.51 > portDS.syncLocked X X R R IEEE Std 802.1AS [104] clause 14.8.52 > portDS.pdelayTruncatedTimestampsArray X X RW RW IEEE Std 802.1AS [104] clause 14.8.53 > portDS.minorVersionNumber X X RW RW IEEE Std 802.1AS [104] clause 14.8.54 > timePropertiesDS.currentUtcOffset X RW RW IEEE Std 802.1AS [104] clause 14.5.2 > externalPortConfigurationPortDS.desiredState X RW RW IEEE Std 802.1AS [104] clause 14.12.2 NOTE 1: R = Read only access; RW = Read/Write access; ― = not supported. NOTE 2: Indicates which standardized and deployment-specific port management information is supported by DS-TT or NW-TT. NOTE 3: AdminCycleTime, AdminControlListLength and TransmissionOverrun are optional for gate control information. NOTE 4: If DS-TT supports neighbor discovery, then TSN AF sends the general neighbor discovery configuration for DS-TT Ethernet ports to DS-TT. If DS-TT does not support neighbor discovery, then TSN AF sends the general neighbor discovery configuration for DS-TT Ethernet ports to NW-TT using the User Plane Node Management Information Container (refer to Table K.1-2) and NW-TT performs neighbor discovery on behalf on DS-TT. When a parameter in this group is changed, it is necessary to provide the change to every DS-TT and the NW-TT that belongs to the 5GS TSN bridge. It is mandatory that the general neighbor discovery configuration is identical for all DS-TTs and the NW-TTs that belongs to the bridge. NOTE 5: If DS-TT supports neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from DS-TT. TSN AF indicates the neighbor discovery information for each discovered neighbor of DS-TT port to CNC. If DS-TT does not support neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from NW-TT, using the User Plane Node Management Information Container (refer to Table K.1-2), the NW-TT performing neighbor discovery on behalf on DS-TT. NOTE 6: X = applicable; D = applicable when validation and generation of LLDP frames is processed at the DS-TT. NOTE 7: Void. NOTE 8: There is a Stream Filter Instance Table per Stream. NOTE 9: There is a Stream Gate Instance Table per Gate. NOTE 10: TSN AF indicates the support for PSFP to the CNC only if each DS-TT and NW-TT of the 5GS bridge has indicated support of PSFP. DS-TT indicates support of PSFP using port management capabilities, i.e. by indicating support for the Per-Stream Filtering and Policing information and by setting higher than zero values for MaxStreamFilterInstances, MaxStreamGateInstances, MaxFlowMeterInstances, SupportedListMax parameters. When available, TSN AF uses the PSFP information for determination of the traffic pattern information as described in Annex I. The PSFP information can be used at the DS-TT (if supported) and at the NW-TT (if supported) for the purpose of per-stream filtering and policing as defined in clause 8.6.5.2.1 of IEEE Std 802.1Q [98]. NOTE 11: TSN AF composes a Stream Parameter Table towards the CNC. It is up to TSN AF how it composes the Stream Parameter Table based on the numerical values as received from DS-TT and NW-TT port(s) and for the bridge for each individual parameter. NOTE 12: The set of Stream Identification Controlling Parameters depends on the Stream Identification type value as defined in IEEE Std 802.1CB [83] Table 9-1 and clauses 9.1.2, 9.1.3, 9.1.4. NOTE 13: Enumeration of supported PTP instance types. Allowed values as defined in clause 8.2.1.5.5 of IEEE Std 1588 [126]. NOTE 14: Enumeration of supported transport types. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 15: Enumeration of supported PTP delay mechanisms. Allowed values as defined in clause 8.2.15.4.4 of IEEE Std 1588 [126]. NOTE 16: Indicates whether DS-TT supports acting as a PTP grandmaster. NOTE 17: Indicates whether DS-TT supports acting as a gPTP grandmaster. NOTE 18: Enumeration of supported PTP profiles, each identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 19: PTP profile to apply, identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 20: Transport type to use. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 21: Indicates whether to act as grandmaster or not, i.e. whether to send Announce, Sync and optionally Follow_Up messages. NOTE 22: The IEEE Std 802.1AS [104] data sets apply if the IEEE 802.1AS PTP profile is used; otherwise the IEEE Std 1588 [126] data sets apply. NOTE 23: Indicates how much the txPropagationDelay needs to change so that DS-TT/NW-TT report a change in txPropagationDelay to TSN AF. This is optional for NW-TT. NOTE 24: Indicates the gPTP domain (identified by a domain number) that is assumed by the CNC as the reference clock for time information in the scheduled traffic (gate control) information, PSFP information and bridge delay related information. This is optional for NW-TT. NOTE 25: PTP Instance ID uniquely identifies a PTP instance within the user plane node. NOTE 26: TSN AF indicates the neighbor discovery information for each discovered neighbor of NW-TT port to CNC. NOTE 27: Applicable in case of interworking with IETF Deterministic Networking. Table K.1-2: Standardized user plane node management information User plane node management information Supported operations by TSN AF Supported operations by TSCTSF Reference (see NOTE 1) (see NOTE 1) Information for 5GS Bridge/Router User plane node Address R R User plane node ID R R NW-TT port numbers R R Traffic forwarding information Static Filtering Entry (NOTE 3) RW - IEEE Std 802.1Q [98] clause 8.8.1 General Neighbor discovery configuration (NOTE 2) adminStatus RW - IEEE Std 802.1AB [97] clause 9.2.5.1 lldpV2LocChassisIdSubtype RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2LocChassisId RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2MessageTxInterval RW - IEEE Std 802.1AB [97] Table 11-2 lldpV2MessageTxHoldMultiplier RW - IEEE Std 802.1AB [97] Table 11-2 DS-TT port neighbor discovery configuration for DS-TT ports (NOTE 4) >DS-TT port neighbor discovery configuration for each DS-TT port >> DS-TT port number RW - >> lldpV2LocPortIdSubtype RW - IEEE Std 802.1AB [97] Table 11-2 >> lldpV2LocPortId RW - IEEE Std 802.1AB [97] Table 11-2 >> OtlvSet RW - IEC/IEEE 60802 [216], clause 6.5.2.4.5 and clause 6.5.2.4.6. Discovered neighbor information for DS-TT ports (NOTE 4) >Discovered neighbor information for each DS-TT port (NOTE 4) >> DS-TT port number R - >> lldpV2RemChassisIdSubtype R - IEEE Std 802.1AB [97] Table 11-2 >> lldpV2RemChassisId R - IEEE Std 802.1AB [97] Table 11-2 >> lldpV2RemPortIdSubtype R - IEEE Std 802.1AB [97] Table 11-2 >> lldpV2RemPortId R - IEEE Std 802.1AB [97] Table 11-2 >> TTL R - IEEE Std 802.1AB [97] clause 8.5.4.1 >> OtlvSet R - IEC/IEEE 60802 [216], clause 6.5.2.4.5 and clause 6.5.2.4.6. Stream Parameters (NOTE 5) MaxStreamFilterInstances R - IEEE Std 802.1Q [98] Table 12-34 MaxStreamGateInstances R - IEEE Std 802.1Q [98] Table 12-34 MaxFlowMeterInstances R - IEEE Std 802.1Q [98] Table 12-34 SupportedListMax R - IEEE Std 802.1Q [98] Table 12-34 Time synchronization information Supported PTP instance types (NOTE 6) R R Supported transport types (NOTE 7) R R Supported delay mechanisms (NOTE 8) R R PTP grandmaster capable (NOTE 9) R R gPTP grandmaster capable (NOTE 10) R R Supported PTP profiles (NOTE 11) R R Number of supported PTP instances R R Time synchronization information for PTP instances (NOTE 16) > PTP instance specification >> PTP Instance ID (NOTE 17) RW RW >> PTP profile (NOTE 12) RW RW >> Transport type (NOTE 13) RW RW >> Grandmaster candidate enabled RW RW IEEE Std 1588 [126] data sets (NOTE 15) >> defaultDS.clockIdentity RW RW IEEE Std 1588 [126] clause 8.2.1.2.2 >> defaultDS.clockQuality.clockClass RW RW IEEE Std 1588 [126] clause 8.2.1.3.1.2 >> defaultDS.clockQuality.clockAccuracy RW RW IEEE Std 1588 [126] clause 8.2.1.3.1.3 >> defaultDS.clockQuality.offsetScaledLogVariance RW RW IEEE Std 1588 [126] clause 8.2.1.3.1.4 >> defaultDS.priority1 RW RW IEEE Std 1588 [126] clause 8.2.1.4.1 >> defaultDS.priority2 RW RW IEEE Std 1588 [126] clause 8.2.1.4.2 >> defaultDS.domainNumber RW RW IEEE Std 1588 [126] clause 8.2.1.4.3 >> defaultDS.sdoId RW RW IEEE Std 1588 [126] clause 8.2.1.4.5 >> defaultDS.instanceEnable RW RW IEEE Std 1588 [126] clause 8.2.1.5.2 >> defaultDS.externalPortConfigurationEnabled RW RW IEEE Std 1588 [126] clause 8.2.1.5.3 >> defaultDS.instanceType RW RW IEEE Std 1588 [126] clause 8.2.1.5.5 >> timePropertiesDS.currentUtcOffset RW RW IEEE Std 1588 [126] clause 8.2.4.2 >> timePropertiesDS.timeSource RW RW IEEE Std 1588 [126] clause 8.2.4.9 IEEE Std 802.1AS [104] data sets (NOTE 15) >> defaultDS.clockIdentity RW RW IEEE Std 802.1AS [104] clause 14.2.2 >> defaultDS.clockQuality.clockClass RW RW IEEE Std 802.1AS [104] clause 14.2.4.2 >> defaultDS.clockQuality.clockAccuracy RW RW IEEE Std 802.1AS [104] clause 14.2.4.3 >> defaultDS.clockQuality.offsetScaledLogVariance RW RW IEEE Std 802.1AS [104] clause 14.2.4.4 >> defaultDS.priority1 RW RW IEEE Std 802.1AS [104] clause 14.2.5 >> defaultDS.priority2 RW RW IEEE Std 802.1AS [104] clause 14.2.6 >> defaultDS.timeSource RW RW IEEE Std 802.1AS [104] clause 14.2.15 >> defaultDS.domainNumber RW RW IEEE Std 802.1AS [104] clause 14.2.16 >> defaultDS.sdoId RW RW IEEE Std 802.1AS [104] clause 14.2.18 >> defaultDS.externalPortConfigurationEnabled RW RW IEEE Std 802.1AS [104] clause 14.2.4.3 >> defaultDS.instanceEnable RW RW IEEE Std 802.1AS [104] clause 14.2.19 >> timePropertiesDS.currentUtcOffset RW RW IEEE Std 802.1AS [104] clause 14.5.2 Time synchronization information for DS-TT ports > Time synchronization information for each DS-TT port > DS-TT port number RW RW >> Time synchronization information for each PTP Instance >> PTP Instance ID (NOTE 17) RW RW >> Grandmaster on behalf of DS-TT enabled (NOTE 14) RW RW IEEE Std 1588 [126] data sets (NOTE 15) >> portDS.portIdentity RW RW IEEE Std 1588 [126] clause 8.2.15.2.1 >> portDS.portState R R IEEE Std 1588 [126] clause 8.2.15.3.1 >> portDS.logMinDelayReqInterval RW RW IEEE Std 1588 [126] clause 8.2.15.3.2 >> portDS.logAnnounceInterval RW RW IEEE Std 1588 [126] clause 8.2.15.4.1 >> portDS.announceReceiptTimeout RW RW IEEE Std 1588 [126] clause 8.2.15.4.2 >> portDS.logSyncInterval RW RW IEEE Std 1588 [126] clause 8.2.15.4.3 >> portDS.delayMechanism RW RW IEEE Std 1588 [126] clause 8.2.15.4.4 >> portDS.logMinPdelayReqInterval RW RW IEEE Std 1588 [126] clause 8.2.15.4.5 >> portDS.versionNumber RW RW IEEE Std 1588 [126] clause 8.2.15.4.6 >> portDS.minorVersionNumber RW RW IEEE Std 1588 [126] clause 8.2.15.4.7 >> portDS.delayAsymmetry RW RW IEEE Std 1588 [126] clause 8.2.15.4.8 >> portDS.portEnable RW RW IEEE Std 1588 [126] clause 8.2.15.5.1 >> externalPortConfigurationPortDS.desiredState RW RW IEEE Std 1588 [126] clause 15.5.3.7.15.1 IEEE Std 802.1AS [104] data sets (NOTE 15) >> portDS.portIdentity RW RW IEEE Std 802.1AS [104] clause 14.8.2 >> portDS.portState R R IEEE Std 802.1AS [104] clause 14.8.3 >> portDS.ptpPortEnabled RW RW IEEE Std 802.1AS [104] clause 14.8.4 >> portDS.delayMechanism RW RW IEEE Std 802.1AS [104] clause 14.8.5 >> portDS.isMeasuringDelay R R IEEE Std 802.1AS [104] clause 14.8.6 >> portDS.asCapable R R IEEE Std 802.1AS [104] clause 14.8.7 >> portDS.meanLinkDelay R R IEEE Std 802.1AS [104] clause 14.8.8 >> portDS.meanLinkDelayThresh RW RW IEEE Std 802.1AS [104] clause 14.8.9 >> portDS.delayAsymmetry RW RW IEEE Std 802.1AS [104] clause 14.8.10 >> portDS.neighborRateRatio R R IEEE Std 802.1AS [104] clause 14.8.11 >> portDS.initialLogAnnounceInterval RW RW IEEE Std 802.1AS [104] clause 14.8.12 >> portDS.currentLogAnnounceInterval R R IEEE Std 802.1AS [104] clause 14.8.13 >> portDS.useMgtSettableLogAnnounceInterval RW RW IEEE Std 802.1AS [104] clause 14.8.14 >> portDS.mgtSettableLogAnnounceInterval RW RW IEEE Std 802.1AS [104] clause 14.8.15 >> portDS.announceReceiptTimeout RW RW IEEE Std 802.1AS [104] clause 14.8.16 >> portDS.initialLogSyncInterval RW RW IEEE Std 802.1AS [104] clause 14.8.17 >> portDS.currentLogSyncInterval R R IEEE Std 802.1AS [104] clause 14.8.18 >> portDS.useMgtSettableLogSyncInterval RW RW IEEE Std 802.1AS [104] clause 14.8.19 >> portDS.mgtSettableLogSyncInterval RW RW IEEE Std 802.1AS [104] clause 14.8.20 >> portDS.syncReceiptTimeout RW RW IEEE Std 802.1AS [104] clause 14.8.21 >> portDS.syncReceiptTimeoutTimeInterval RW RW IEEE Std 802.1AS [104] clause 14.8.22 >> portDS.initialLogPdelayReqInterval RW RW IEEE Std 802.1AS [104] clause 14.8.23 >> portDS.currentLogPdelayReqInterval R R IEEE Std 802.1AS [104] clause 14.8.24 >> portDS.useMgtSettableLogPdelayReqInterval RW RW IEEE Std 802.1AS [104] clause 14.8.25 >> portDS.mgtSettableLogPdelayReqInterval RW RW IEEE Std 802.1AS [104] clause 14.8.26 >> portDS.initialLogGptpCapableMessageInterval RW RW IEEE Std 802.1AS [104] clause 14.8.27 >> portDS.currentLogGptpCapableMessageInterval R R IEEE Std 802.1AS [104] clause 14.8.28 >> portDS.useMgtSettableLogGptpCapableMessageInterval RW RW IEEE Std 802.1AS [104] clause 14.8.29 >> portDS.mgtSettableLogGptpCapableMessageInterval RW RW IEEE Std 802.1AS [104] clause 14.8.30 >> portDS.initialComputeNeighborRateRatio RW RW IEEE Std 802.1AS [104] clause 14.8.31 >> portDS.currentComputeNeighborRateRatio R R IEEE Std 802.1AS [104] clause 14.8.32 >> portDS.useMgtSettableComputeNeighborRateRatio RW RW IEEE Std 802.1AS [104] clause 14.8.33 >> portDS.mgtSettableComputeNeighborRateRatio RW RW IEEE Std 802.1AS [104] clause 14.8.34 >> portDS.initialComputeMeanLinkDelay RW RW IEEE Std 802.1AS [104] clause 14.8.35 >> portDS.currentComputeMeanLinkDelay R R IEEE Std 802.1AS [104] clause 14.8.36 >> portDS.useMgtSettableComputeMeanLinkDelay RW RW IEEE Std 802.1AS [104] clause 14.8.37 >> portDS.mgtSettableComputeMeanLinkDelay RW RW IEEE Std 802.1AS [104] clause 14.8.38 >> portDS.allowedLostResponses RW RW IEEE Std 802.1AS [104] clause 14.8.39 >> portDS.allowedFaults RW RW IEEE Std 802.1AS [104] clause 14.8.40 >> portDS.gPtpCapableReceiptTimeout RW RW IEEE Std 802.1AS [104] clause 14.8.41 >> portDS.versionNumber RW RW IEEE Std 802.1AS [104] clause 14.8.42 >> portDS.nup RW RW IEEE Std 802.1AS [104] clause 14.8.43 >> portDS.ndown RW RW IEEE Std 802.1AS [104] clause 14.8.44 >> portDS.oneStepTxOper R R IEEE Std 802.1AS [104] clause 14.8.45 >> portDS.oneStepReceive R R IEEE Std 802.1AS [104] clause 14.8.46 >> portDS.oneStepTransmit R R IEEE Std 802.1AS [104] clause 14.8.47 >> portDS.initialOneStepTxOper RW RW IEEE Std 802.1AS [104] clause 14.8.48 >> portDS.currentOneStepTxOper RW RW IEEE Std 802.1AS [104] clause 14.8.49 >> portDS.useMgtSettableOneStepTxOper RW RW IEEE Std 802.1AS [104] clause 14.8.50 >> portDS.mgtSettableOneStepTxOper RW RW IEEE Std 802.1AS [104] clause 14.8.51 >> portDS.syncLocked R R IEEE Std 802.1AS [104] clause 14.8.52 >> portDS.pdelayTruncatedTimestampsArray RW RW IEEE Std 802.1AS [104] clause 14.8.53 >> portDS.minorVersionNumber RW RW IEEE Std 802.1AS [104] clause 14.8.54 >> externalPortConfigurationPortDS.desiredState RW RW IEEE Std 802.1AS [104] clause 14.12.2 Time synchronization status (TSS) information > Synchronization state - R Table 5.27.1.12-1 > Clock quality - R Table 5.27.1.12-1 >> Traceable to UTC - R Table 5.27.1.12-1 >> Traceable to GNSS - R Table 5.27.1.12-1 >> Frequency stability - R Table 5.27.1.12-1 >> Clock accuracy - R Table 5.27.1.12-1 > Parent time source - R Table 5.27.1.12-1 NOTE 1: R = Read only access; RW = Read/Write access; ― = not supported. NOTE 2: General neighbor discovery information is included only when NW-TT performs neighbor discovery on behalf of DS-TT. When a parameter in this group is changed, it is necessary to provide the change to every DS-TT and the NW-TT that belongs to the 5GS TSN bridge. NOTE 3: If the Static Filtering Entry information is present, UPF/NW-TT can use Static Filtering Entry information for forwarding TSC traffic, as specified in clause 5.8.2.5.3. NOTE 4: DS-TT discovery configuration and DS-TT discovery information are used only when DS-TT does not support LLDP and NW-TT performs neighbor discovery on behalf of DS-TT. TSN AF indicates the discovered neighbor information for each DS-TT port to CNC. NOTE 5: TSN AF indicates the support for PSFP to the CNC only if each DS-TT and NW-TT of the 5GS bridge have indicated support of PSFP. The support of PSFP at the NW-TT ports is expressed by setting higher than zero values for MaxStreamFilterInstances, MaxStreamGateInstances, MaxFlowMeterInstances, SupportedListMax parameters. NOTE 6: Enumeration of supported PTP instance types. Allowed values as defined in clause 8.2.1.5.5 of IEEE Std 1588 [126]. NOTE 7: Enumeration of supported transport types. Allowed values: IPv4 (as defined in IEEE Std 1588 [126] Annex C), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 8: Enumeration of supported PTP delay mechanisms. Allowed values as defined in clause 8.2.15.4.4 of IEEE Std 1588 [126]. NOTE 9: Indicates whether NW-TT supports acting as a PTP grandmaster. NOTE 10: Indicates whether NW-TT supports acting as a gPTP grandmaster. NOTE 11: Enumeration of supported PTP profiles, each identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 12: PTP profile to apply, identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 13: Transport type to use. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 14: Indicates whether to act as grandmaster on behalf of a DS-TT port or not if 5GS is determined to be the grandmaster clock, i.e. whether to send Announce, Sync and optionally Follow_Up messages on behalf of DS-TT. NOTE 15: The IEEE Std 802.1AS [104] data sets apply if the IEEE 802.1AS PTP profile is used; otherwise, the IEEE Std 1588 [126] data sets apply. NOTE 16: Specifies the default data set for each PTP instance identified by PTP instance ID within the user plane node. NOTE 17: PTP Instance ID uniquely identifies a PTP instance within the user plane node. K.2 Port and user plane node management information exchange for time synchronization K.2.1 Capability exchange DS-TT and NW-TT indicate time synchronization information they support inside the Port management capabilities (see Table K.1-1). TSN AF and TSCTSF may determine the PTP functionalities supported by DS-TT and NW-TT by retrieving the following port management information or user plane node management information, respectively: - Supported PTP instance types; - Supported transport types; - Supported PTP delay mechanisms; - Grandmaster capability; - Supported PTP profiles; - Number of supported PTP instances. NOTE: If NW-TT or DS-TT do not indicate support for any of the PTP profiles and PTP instance types, then TSN AF or TSCTSF assume that the NW-TT or DS-TT only support acting as a PTP Relay instance with the gPTP GM connected on N6. If DS-TT and NW-TT support the PTP Relay instance type as defined by IEEE 802.1AS [104] then DS-TT and NW-TT shall include the IEEE 802.1AS [104] PTP profile in the "Supported PTP profiles" in PMIC and UMIC, respectively. The TSN AF or TSCTSF may retrieve the "Number of supported PTP instances" from NW-TT via UMIC and from DS-TT via PMIC. K.2.2 PTP Instance configuration K.2.2.1 General Based on input received from external applications (CNC in case of TSN AF or any AF in case of TSCTSF), TSN AF or TSCTSF may configure PTP instances (identified by PTP Instance ID) in a DS-TT or NW-TT by sending port management information (PMIC, see Table K.1-1) and user plane node management information (UMIC, see Table K.1-2) to DS-TT or NW-TT as described below: - use PMIC "PTP instance specification" for configuring DS-TT(s) for PTP instance data sets common for all PTP ports (i.e. defaultDS and TimePropertiesDS) and PTP instance data sets specific for each PTP port (i.e. portDS data set); - use UMIC "PTP instance specification" for configuring NW-TT for PTP instance data sets common for all PTP ports; - use PMIC "PTP instance specification" for configuring NW-TT for PTP instance data sets specific for each PTP port; - use UMIC "Time synchronization information for DS-TT ports" for configuring NW-TT for PTP instance data sets specific for each PTP port for the PTP ports in DS-TT(s). TSN AF or TSCTSF may also configure PTP instances for DS-TT ports in NW-TT by sending UMIC (see Table K.1-2) to NW-TT to enable NW-TT to operate as a grandmaster on behalf of DS-TT (see clause K.2.2.4 for more details). For each PTP instance the TSN AF or TSCTSF may provide individual PTP configuration parameters or may provide a PTP profile ID to DS-TT or NW-TT. The DS-TT and NW-TT use the default values as defined in the corresponding PTP Profile, if individual PTP configuration parameters that are covered by the PTP profile are not provided. NOTE 1: Even if PTP profiles are used to configure DS-TT or NW-TT, individual PTP parameters can still be configured in addition, e.g. domain numbers, transport to use, etc. To configure DS-TT and NW-TT to operate as a PTP relay instance, TSN AF or TSCTSF shall set the PTP profile (see Table K.1-1) to IEEE Std 802.1AS [104]. DS-TT may operate as a PTP relay instance with the gPTP GM connected on N6 until the first PTP instance is configured in the DS-TT by TSN AF or TSCTSF. To initialize a PTP instance in 5GS, TSN AF or TSCTSF creates a new PTP instance in NW-TT by assigning a new PTP Instance ID and indicating it to the NW-TT in "PTP instance specification" in UMIC and PMIC(s) for each NW-TT port that is part of the PTP instance. TSN AF or TSCTSF then retrieves the "defaultDS.clockIdentity" of the PTP instance in NW-TT via UMIC. NW-TT ensures that the clockIdentity in defaultDS in UMIC matches with the clockIdentity in the portDS.portIdentity in PMIC(s) for a particular PTP Instance ID. To add a DS-TT port into an existent PTP instance in 5GS, the TSN AF or TSCTSF indicates the PTP Instance ID (to which the DS-TT port is being added) to the DS-TT in "PTP instance specification" in PMIC and indicating the PTP Instance ID to the NW-TT in "Time synchronization information for DS-TT ports" in UMIC for the corresponding DS-TT port. For a particular PTP instance in NW-TT, the same PTP Instance ID shall be used in "PTP instance specification" in PMIC, in "PTP instance specification" in UMIC and in "Time synchronization information for DS-TT ports" in UMIC. NOTE 2: The TSN AF or TSCTSF creates a PTP Instance in the NW-TT or DS-TT by using the "Set parameter" operation code as described in TS 24.539 [139]. The NW-TT or DS-TT determines that this "Set parameter" operation creates a new PTP Instance based on the PTP Instance ID that does not correspond to any of the configured PTP Instances in the "PTP instance specification" and "Time synchronization information for DS-TT ports" (for NW-TT) or in the "PTP instance specification" (for DS-TT). The TSN AF or TSCTSF then initializes the PTP instance in the DS-TT by setting the applicable PTP instance data sets common for all PTP ports (i.e. defaultDS and TimePropertiesDS), (including"defaultDS.clockIdentity") via "PTP instance specification" in PMIC to the same value as retrieved from the NW-TT via "PTP instance specification" in UMIC. The TSN AF or TSCTSF also enables the PTP instance by setting the defaultDS.instanceEnable = TRUE to DS-TT via PMIC and to NW-TT via UMIC (if applicable). The TSN AF or TSCTSF can initialize any number of PTP instances: a) among the DS-TT(s) and NW-TT that are part of the same set of PTP instances in 5GS; up to the maximum number of supported PTP instances by the NW-TT or DS-TT that supports the lowest number of supported PTP instances; and b) in the NW-TT; up to the maximum number of supported PTP instances by the NW-TT. NOTE 3: How the TSN AF or TSCTSF assign NW-TT port(s) of one NW-TT to different PTP instances is up to implementation. To remove a DS-TT port from a PTP instance in 5GS, the TSN AF or TSCTSF deletes the PTP instance in DS-TT using PMIC and in NW-TT using UMIC as specified in TS 24.539 [139]. To remove a NW-TT port from a PTP instance in 5GS, the TSN AF or TSCTSF deletes the PTP instance in NW-TT using PMIC as specified in TS 24.539 [139]. If a PTP instance in 5GS is no more needed the TSN AF or TSCTSF may delete the PTP instance in NW-TT using UMIC as specified in TS 24.539 [139]. K.2.2.2 Configuration for Sync and Announce reception timeouts The NW-TT shall be able to determine the timeout of the reception of (g)PTP Announce (when the 5GS operates as a time-aware system or Boundary Clock) and gPTP Sync messages (when the 5GS operates as time-aware system). To enable this, the TSCTSF or TSN AF shall configure the NW-TT for the following information via PMIC for each PTP port in NW-TT and "Time synchronization information for each DS-TT port" element in UMIC for each PTP port in DS-TT: portDS.announceReceiptTimeout (for time-aware system and Boundary Clock); portDS.syncReceiptTimeout (for time-aware system); portDS.logAnnounceInterval (for Boundary Clock). portDS.initialLogAnnounceInterval, portDS.useMgtSettableLogAnnounceInterval and portDS.mgtSettableLogAnnounceInterval (for time-aware system). K.2.2.3 Configuration for PTP port states The PTP port states may be determined by NW-TT either via: - Method a), BMCA procedure. - Method b), local configuration. When Method b) is used, the TSN AF or TSCTSF sets the defaultDS.externalPortConfigurationEnabled (per PTP instance) in UMIC to TRUE and sets the value of externalPortConfigurationPortDS.desiredState (per PTP port) in UMIC for each DS-TT port and in PMIC for each NW-TT port for the (g)PTP domain. K.2.2.4 Configuration for PTP grandmaster function The following options may be supported (per DS-TT) for the 5GS to generate the Sync, Follow_Up and Announce messages for the Leader ports on the DS-TT: a) NW-TT generates the Sync, Follow_Up and Announce messages on behalf of DS-TT (e.g. if DS-TT does not support this). b) DS-TT generates the Sync, Follow_Up and Announce messages in this DS-TT. TSN AF and TSCTSF may use the elements in port and user plane node management information container to determine the PTP grandmaster functionality supported by DS-TT and NW-TT and may configure the DS-TT and NW-TT ports to operate as in option a) or b) as follows: - The "PTP grandmaster capable" element and the "gPTP grandmaster capable" element in PMIC are used to indicate the support for PTP or gPTP grandmaster capability, respectively, in each DS-TT. If the TSN AF or TSCTSF determines the DS-TT supports grandmaster capability (PTP or gPTP grandmaster capable is TRUE), then either option a) or b) can be used for the PTP instance(s) in the DS-TT. Otherwise, only option a) can be used for the PTP instance(s) in the DS-TT. - To enable option a) for PTP ports in DS-TT, the TSN AF or TSCTSF sets the element "Grandmaster on behalf of DS-TT enabled" TRUE (per PTP instance per DS-TT) in UMIC for the respective DS-TT port and the TSN AF or TSCTSF sets the element "Grandmaster enabled" FALSE (per PTP instance per DS-TT) in PMIC to the respective DS-TT port. - To enable option b) for PTP ports in DS-TT, the TSN AF or TSCTSF sets the element "Grandmaster on behalf of DS-TT enabled" FALSE in UMIC (per PTP instance per DS-TT) for the respective port and the TSN AF or TSCTSF sets the element "Grandmaster enabled" TRUE (per PTP instance per DS-TT) in PMIC to the respective DS-TT port. - To enable either option a) or option b) for a PTP instance, the TSN AF or TSCTSF sets the element "Grandmaster candidate enabled" TRUE (per PTP instance) in UMIC. - When option b) is used for one or more PTP ports in DS-TT(s), the TSN AF or TSCTSF shall use the elements in defaultDS in PMIC for the respective DS-TT(s) and in UMIC for NW-TT to ensure that all PTP ports in the DS-TT(s) and NW-TT in particular PTP instance are distributing the same values of grandmasterPriority1, grandmasterClockQuality, grandmasterPriority2, grandmasterIdentity and timeSource message fields in Announce messages. K.2.2.5 Configuration for Sync and Announce intervals The TSN AF or TSCTSF uses the values in portDS.logSyncInterval (for Boundary Clock) or portDS.initialLogSyncInterval, portDS.useMgtSettableLogSyncInterval and portDS.mgtSettableLogSyncInterval (for time-aware system) to configure the interval for the Sync messages (per PTP port) as described in IEEE Std 1588 [126] or IEEE Std 802.1AS [104], respectively. The TSCTSF or TSN AF configures those values as follows: - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in NW-TT. - TSCTSF or TSN AF use the "Time synchronization information for each DS-TT port" element in UMIC to configure the values for PTP ports in DS-TT(s) if NW-TT acts as GM on behalf of those DS-TTs. - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in DS-TT if the DS-TT is capable of acting as a GM. When the NW-TT generates the (g)PTP Sync messages on behalf of the DS-TT, the NW-TT uses the values in the element "Time synchronization information for each DS-TT port" in UMIC to determine the Sync interval for the PTP ports the respective DS-TT. When DS-TT generates the (g)PTP Sync messages, the DS-TT uses the values in PMIC to determine the Sync interval for the PTP ports in this DS-TT. The TSN AF or TSCTSF uses the values in portDS.logAnnounceInterval (for Boundary Clock) or portDS.initialLogAnnounceInterval, portDS.useMgtSettableLogAnnounceInterval and portDS.mgtSettableLogAnnounceInterval (for time-aware system) to configure the interval for the Announce messages (per PTP port) as described in IEEE Std 1588 [126] and IEEE Std 802.1AS [104], respectively. The TSCTSF or TSN AF configures those values as follows: - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in NW-TT. - TSCTSF or TSN AF use the "Time synchronization information for each DS-TT port" element in UMIC to configure the values for PTP ports in DS-TT(s) if NW-TT acts as GM on behalf of those DS-TTs. - TSCTSF or TSN AF use PMIC to configure the values for the PTP ports in DS-TT if the DS-TT is capable of acting as a GM. When the NW-TT generates the (g)PTP Announce messages on behalf of the DS-TT, the NW-TT uses the values in the element "Time synchronization information for each DS-TT port" in UMIC to determine the Announce interval for the PTP ports the respective DS-TT. When DS-TT generates the (g)PTP Announce messages, the DS-TT uses the values in PMIC to determine the Announce interval for the PTP ports in this DS-TT. K.2.2.6 Configuration for transport protocols The procedure described in this clause is applicable when the PTP Profile that is used for the PTP instance in 5GS defines multiple permitted transport protocols. TSN AF or TSCTSF may use the element "Supported transport types" in port management information container (per DS-TT) to determine the supported transport types in the DS-TT. TSN AF or TSCTSF may use the element "Supported transport types" in UMIC (per NW-TT) to determine the supported transport types in the NW-TT. The TSN AF or TSCTSF may use the element "Transport type" (per PTP instance) in PMIC to configure the transport protocol in use for the PTP instance in DS-TT. The TSN AF or TSCTSF may use the element "Transport type" (per PTP instance) in UMIC to configure the transport protocol in use for the PTP instance in NW-TT. The PTP instance shall be configured to use one of the following transport protocols: 1) Ethernet as described in Annex E of IEEE Std 1588 [126]. The Ethertype as defined for PTP shall be used. The related Ethernet frames carry the PTP multicast Ethernet destination MAC address. 2) UDP over IPv4 as described in Annex C of IEEE Std 1588 [126], 3) UDP over IPv6 as described in Annex D of IEEE Std 1588 [126]. Option 1 applies to Ethernet PDU Session type. Options 2 and 3 apply to IP PDU Session type or Ethernet PDU Session type with IP payload. Annex L (normative): Support of GERAN/UTRAN access This annex applies when the SMF+PGW-C is enhanced to support UE accessing the network via GERAN/UTRAN over Gn/Gp interface. For this scenario, the SMF+PGW-C uses N7 interface to interact with PCF and the N40 interface to interact with CHF. NOTE 1: For the interface with the serving node of the UE, the SMF+PGW-C is assumed to behave as the Control Plane of the PGW described in Annex D of TS 23.401 [26]. SMF+PGW-C selection by SGSN is specified in Annex G of TS 23.502 [3]. The SMF+PGW-C interacting with PCF for GERAN/UTRAN access is specified in Annex G of TS 23.502 [3]. The functional description for SMF+PGW-C interacting with PCF to support GERAN/UTRAN access is specified in TS 23.503 [45]. NOTE 2: Support for IP address preservation upon mobility between 5GS and GERAN/UTRAN for PDN sessions established in EPC is described in clause 5.17.2.4. IP address preservation is not supported for direct mobility between 5GS and GERAN/UTRAN, nor for indirect mobility cases when the PDN session is established in 5GS or in GERAN/UTRAN. The charging services on SMF+PGW-C interactions with CHF for GERAN/UTRAN access are specified in TS 32.255 [68]. Annex M (normative): Interworking with TSN deployed in the Transport Network M.1 Mapping of the parameters between 5GS and TSN UNI The details of the parameters in the TSN UNI are specified in IEEE Std 802.1Q [98] and IEEE Std 802.1Qdj [146]. Stream identification is further specified in IEEE Std 802.1CB [83] and IEEE Std 802.1CBdb [178]. The SMF/CUC derives the End Station related information for the stream requirements towards the TN CNC for the QoS Flow as follows: a) For the Talker group: ‐ StreamID: can be generated by the SMF/CUC based on the End Station MAC address acting as Talker and a UniqueID. SUPI, PDU Session ID and QFI may be used to derive the UniqueID. The MAC address is either pre-configured at the SMF/CUC or provided by the AN-TL or CN-TL to the SMF/CUC (e.g. as part of the EndStationInterfaces information). - StreamRank: set to zero for ARP priority values 1-8; set to one for other ARP values. ‐ EndStationInterfaces: If the AN-TL and CN-TL are supported, the SMF/CUC receives the EndStationInterfaces (MacAddress, InterfaceName) from the AN-TL and CN-TL via TL-Container. If the AN-TL and CN-TL are not supported the SMF/CUC sets the information based on pre-configuration. - DataFrameSpecification (optional): When it is present it specifies how the TN can identify packets of the TN stream using Ethernet, IP and transport protocol header fields in order to apply the required TSN configuration. The SMF/CUC may derive the DataFrameSpecification based on: - N3 tunnel end point addresses that are used for the QoS Flow. The SMF/CUC may instruct the UPF and NG-RAN to assign a separate N3 tunnel end point address for each QoS Flow that may carry TSC streams so that the TN can distinguish the QoS Flows based on the N3 tunnel destination IP addresses. NOTE 1: IPv6 can be used in the N3 tunnel end point addresses to provide sufficient address space in case separate N3 tunnel end point addresses are used for each QoS flow that can carry time sensitive streams. - Mask-and-match stream identification parameters (IEEE 802.1CBdb [178] clause 9.1.6) (optional). The SMF/CUC may indicate mask-and-match configuration based on the TEID and QFI of the given QoS flow and the destination IP address to the TN CNC, when the deployment supports mask-and-match stream identification function as defined in clause 6.8 in IEEE Std 802.1CBdb [178]. This functionality can be used for example to check for the TEID and QFI in the GTP header and the destination IP address to distinguish the QoS Flows. This enables the TN CNC to configure the mask-and-match stream identification function in the transport network. This is an option that allows to use a single GTP-U tunnel as defined for non-TSN Transport networks. The DataFrameSpecification or mask-and-match stream identification parameters may be provided to the AN-TL and CN-TL to configure stream identification. In that case, the AN-TL and CN-TL can perform the stream identification without relying on additional information from the upper layers of the AN or CN node. When AN-TL and CN-TL are not supported the TN CNC configures the edge bridge to perform the stream transformation based on the provided the DataFrameSpecification or mask-and-match parameters when applicable. ‐ TrafficSpecification elements: ‐ Interval: derived from the Periodicity of the traffic as indicated in the TSCAI. ‐ MaxFramesPerInterval: specifies the maximum number of frames that the Talker transmits in one Interval. NOTE 2: How the SMF/CUC derives MaxFramesPerInterval is up to implementation. ‐ MaxFrameSize: derived from the MDBV of the QoS Flow. If the PCF determines interworking with a TSN network deployed in the transport network is supported based on the DNN/S-NSSAI of the PDU Session, the PCF generates MDBV based on the Burst Size as described in clause 5.27.3 and the PCF transfers the MDBV to the SMF/CUC. The SMF/CUC sets MaxFrameSize based on the following formula: MDBV of the QoS Flow - the framing bits which is not used for transferring in 5GS, (e.g. CRC + the GTP-U tunnel overhead). - TransmissionSelection: specifies the algorithm that the Talker uses to transmit the Stream's traffic class. If no algorithm is known, the value zero (strict priority) is used. ‐ TSpecTimeAware group (optional, present only if the traffic in the QoS Flow is time-synchronized): ‐ EarliestTransmitOffset: the earliest offset within the Interval. For uplink, EarliestTransmitOffset should be set based on the following formula: Packet arrival time at the Talker (UL) - M x Interval, where M is the largest integer for which the relation: Packet arrival time at the Talker (UL) > M x Interval duration. would be true. Packet arrival time at the Talker (UL) should be: The corrected TSCAC BAT in UL direction (presented in TAI time) as specified in clause 5.27.2.4 for the QoS flow+5G-AN PDB+UE-DS-TT Residence Time. For downlink, EarliestTransmitOffset should be set based on the following formula: Packet arrival time at the Talker (DL) - M x Interval, where M is the largest integer for which the relation: Packet arrival time at the Talker (DL) > M x Interval duration. would be true. Packet arrival time at the Talker (DL) should be: The corrected TSCAC BAT in DL direction (presented in TAI time) as specified in clause 5.27.2.4. ‐ LatestTransmitOffset: the last chance within an interval should leave enough time to transfer a packet with MaxFrameSize. Derived from the end of the interval, the time to transfer a packet with MaxFrameSize. The LatestTransmitOffset shall be set to the Buffer Capability when the value of LatestTransmitOffset subtracted by the packet arrival time at the Talker (either UL or DL respectively as described in EarliestTransmitOffset) exceeds the Buffer capability. The value of LatestTransmitOffset shall be larger or equal than EarliestTransmitOffset. ‐ Jitter: derived in SMF/CUC based on local information on Jitter in AN-TL and CN-TL and respective stream and traffic interference. Annex U, clauses U.1.1, U.1.2 and U.1.3 of IEEE Std 802.1Q [98] provide some examples. ‐ UserToNetworkRequirements: ‐ NumSeamlessTrees: set to one (no redundancy) or other value (if redundancy is required). ‐ MaxLatency: set to CN PDB subtracted by maximum possible buffer duration in Talker. Maximum possible buffer duration is set to LatestTransmitOffset subtracted by EarliestTransmitOffset. - InterfaceCapabilities (optional): If the AN-TL and CN-TL are supported, the SMF/CUC collects InterfaceCapabilities from AN-TL and CN-TL via TL-Container. If the AN-TL and CN-TL are not supported, the SMF/CUC leaves the InterfaceCapabilities empty. b) For the Listener group: - Stream ID and Stream Rank: that were generated for the Talker of the TN stream are also used by the SMF/CUC for the Listener. - EndStationInterfaces: derived as with the corresponding information for the Talker group. - UserToNetworkRequirements: ‐ NumSeamlessTrees: set to one. ‐ MaxLatency: derived as with the corresponding information for the Talker group. - InterfaceCapabilities: derived as with the corresponding information for the Talker group. c) For the Status group: The Status group contains the end station communication-configuration provided by TN CNC to the SMF/CUC: ‐ Stream ID. ‐ StatusInfo. ‐ AccumulatedLatency: If the AccumulatedLatency is included from TN CNC to SMF/CUC for a stream in DL direction, the SMF/CUC may use the AccumulatedLatency to update the TSCAI BAT to the NG-RAN; the SMF sets the TSCAI Burst Arrival Time in downlink direction as the sum of the TSCAC BAT value in downlink direction and AccumulatedLatency and the buffer duration in Talker in CN-TL. The buffer duration in CN-TL is zero if TimeAwareOffset for the Talker group is not present and TimeAwareOffset - EarliestTransmitOffset if the TimeAwareOffset is present for the Talker group. ‐ InterfaceConfiguration (optional): ‐ MAC Addresses (optional, present only if the respective InterfaceCapability contains a value for Active Destination MAC and VLAN Stream identification in CB-StreamIdenTypeList and stream transformation is performed in AN-TL and CN-TL). ‐ VLAN Tag (optional, present only if VlanTagCapable is True in the respective InterfaceCapability and the stream transformation is performed in AN-TL and CN-TL). ‐ IPv4/IPv6 Tuples (optional, but not supported in this release of the specification). ‐ TimeAwareOffset (optional, present only if the traffic is time-synchronized, AN-TL and CN-TL is supported and TSpecTimeAware elements were provided in the stream requirements). If the InterfaceConfiguration is included and if the AL-TL/CN-TL acting as Talker End Station support the Stream Transformation as described in IEEE Std 802.1Q [98], the SMF/CUC can instruct the UPF and NG-RAN to assign an individual TSN Transport address by providing the InterfaceConfiguration to the AN-TL/CN-TL via TL-Container. The Talker in AN-TL/CN-TL shall use the indicated InterfaceConfiguration, e.g. source MAC address, multicast destination MAC address, VLAN ID, as assigned by the TN CNC for the data stream in a QoS Flow. The TN can identify the streams based on the Stream Transformation that is applied in the AN-TL/CN-TL acting as Taker End Station. This allows to use a single GTP-U tunnel as defined for non-TSN Transport networks. If the TimeAwareOffset is included from TN CNC to SMF/CUC, the SMF/CUC should send the TimeAwareOffset to the AN-TL (for streams in UL direction) or the CN-TL port (for streams in the DL direction). The AL-TL/CN-TL derive Gate Control information (i.e. AdminBaseTime, AdminCycleTime, AdminControlListLength and AdminControlList) based on the TimeAwareOffset as defined in IEEE Std 802.1Q [98] at the AN-TL (for streams in UL direction) and the CN-TL port (for streams in the DL direction). The AN-TL or CN-TL acting as Talker buffers the data burst until the time indicated in the TimeAwareOffset is reached. If the SMF/CUC receives a TimeAwareOffset from TN CNC for a downlink stream (i.e. for a Talker in the UPF/CN-TL), the SMF/CUC adds the received TimeAwareOffset value to the TSCAI BAT in the DL direction in the TSCAI and updates the NG-RAN for the new TSCAI. ‐ FailedInterfaces (optional) provides a list of one or more physical ports of failed end stations or bridges to locate the interfaces in the physical topology that caused the failure. It is up to implementation how the SMF reacts when it receives FailedInterfaces. NOTE 3: It is assumed that the end station communication-configuration will contain at least the same information as defined for the status. NOTE 4: If Jitter value needs to be considered, EarliestTransmitOffset for UL and DL and LatestTransmitOffset shall be Jitter corrected. How Jitter correction is carried out is up to implementation. M.2 TL-Container Information Table M.2-1: TL-Container Information TL-Container information Supported Operations - AN-TL/CN-TL (see NOTE 1) Reference Talker Listener End Station Parameters of AN-TL/CN-TL List of InterfaceID group(s) >Mac Address Get Get IEEE Std 802.1Q [98], Table 46-3 >InterfaceName (see NOTE 2) Get Get IEEE Std 802.1Q [98], Table 46-3 InterfaceCapabilities (see NOTE 3) >VlanTagCapable (see NOTE 4) Get Get IEEE Std 802.1Q [98], Table 46-11 >BufferCapability (see NOTE 5) Get - Annex M.1 TN Stream Parameters TN Stream Identification Information for mask-and-match (see NOTE 7, NOTE 14) >tsnCpeMmIdMsduMaskLength Set Set IEEE Std 802.1CBdb [178], clause 9.1.6.5 >tsnCpeMmIdMsduMask Set Set IEEE Std 802.1CBdb [178], clause 9.1.6.6 >tsnCpeMmIdMsduMatch Set Set IEEE Std 802.1CBdb [178], clause 9.1.6.7 TN Stream Identification Information for DataFrameSpecification (See NOTE 13, NOTE 14) >DataFrameSpecification Set Set IEEE Std 802.1Q [98], Clause 46.2.3.4 Configuration of End Station Interface >Interface ID group >>InterfaceName (see NOTE 8) Set Set IEEE Std 802.1Q [98],Table 46-3 >>Mac Address Set Set IEEE Std 802.1Q [98],Table 46-3 >InterfaceConfiguration (See NOTE 9, NOTE 10, NOTE 12) >>IEEE802-MacAddresses Set Set IEEE Std 802.1Q [98], Clause 46.2.5.3.1 >>IEEE802-VlanTag Set Set IEEE Std 802.1Q [98], Clause 46.2.5.3.2 >>IPv4-tuple Set Set IEEE Std 802.1Q [98], Clause 46.2.5.3.3 >>IPv6-tuple Set Set IEEE Std 802.1Q [98], Clause 46.2.5.3.4 >>TimeAwareOffset (see NOTE 12) Set - IEEE Std 802.1Q [98], clause 46.2.5.3.5 >Other parameters to Calculate Gate Control Information (See NOTE 6) >>Interval Set - IEEE Std 802.1Q [98], Table 46-8 >>MaxFrameSize (see NOTE 11) Set - IEEE Std 802.1Q [98], Table 46-8 NOTE 1: Get = Get Response; Set = Set Request; - = not supported. NOTE 2: This parameter is optional and only required if End Station has more than one Interface/Port. It identifies the Interface/Port at the End Station. NOTE 3 Interface Capabilities are identical for all Interfaces/Ports of the End Station. NOTE 4: Possible values are TRUE or FALSE. NOTE 5: Maximum possible buffer duration for a packet with the maximum size of an Ethernet packet (1522 Bytes). NOTE 6: SMF/CUC enables the TL to calculate Gate Control Information. Port(s) of the Talker TL may create jitter due to implementation of the TL. How the jitter behaviour is identified and the correction is carried out is up to implementation. NOTE 7: The parameters are provided if mask-and-match stream identification is supported. NOTE 8: The parameter is provided if End Station supports multiple Interfaces/Ports. SMF/CUC guarantees that the End Station MAC address + InterfaceName, which is provided from TN-CNC as InterfaceConfiguration is conveyed with respect to the LLDP information sent via each interface at the user plane. NOTE 9: IEEE802-MacAddresses and IEEE802-VlanTag are provided if Stream Transformation is performed at AN-TL/CN-TL and if Active Destination MAC and VLAN stream identification is signalled from SMF/CUC to TN CNC and if TN CNC provides it in the status group for the Interface/Port. NOTE 10: Vlanid in IEEE802-VlanTag is provided if Stream Transformation is performed at AN-TL/CN-TL and if Active Destination MAC and VLAN stream identification is signalled from SMF/CUC to TN CNC and if TN CNC provides it in the status group for the Interface/Port and End Station VlanTagCapable is TRUE. NOTE 11: Message Length of the Stream including the GTP-U header size. NOTE 12: TimeAwareOffset is provided if TN Stream is scheduled. NOTE 13: The TL indicates a respective FailureCode if it detects a mismatch between the DataFrameSpecification and the GTP-U information received outside of the TL-Container. NOTE 14: Mask-and-match and DataFrameSpecification shall not be supported at the same time. Annex N (informative): Support for access to Localized Services N.1 General A Localized Service is a service, which is provided at specific/limited area and/or can be bounded in time. The service can be realized via applications (e.g. live or on-demand audio/video stream, electric game, IMS, etc.), or connectivity (e.g. UE to UE, UE to Data Network, etc.). A Localized Service provider is an application provider or network operator who make their services localized and that are offered to the end user via a network. A network providing Localized Services can be an SNPN or a PNI-NPN. N.2 Enabling access to Localized Services N.2.1 General To enable a PNI-NPN or SNPN to provide access to Localized Services, the PNI-NPN or SNPN operator configures the network with information enabling the UEs to access the Localized Services using the PNI-NPN or SNPN according to any validity of the Localized Services and the information is determined in agreement with the Localized Service Provider e.g.: a. Identification of each Localized Service, e.g. to be used in URSP rules. b. validity restriction for each Localized Service, e.g. the validity of time and/or location. c. service parameters for each Localized Service, e.g. DNN, S-NSSAI and QoS requirements. d. service authorization methods, e.g. NSSAA or Secondary authentication/authorization during PDU Session establishment. To allow the UE to access the PNI-NPN providing access to Localized Services using credentials of the HPLMN, the PNI-NPN can be configured based on the Localized Service agreements between the PNI-NPN and the HPLMN, to allow primary authentication towards the HPLMN. To allow the UE to access the SNPN providing access to Localized Services using credentials of the Credentials Holder, the SNPN can be configured based on Localized Service agreements between the SNPN and the Credentials Holder, to allow primary authentication towards the Credentials Holder. To allow the UE to access the SNPN providing access to Localized Services when new credential is required, the SNPN can provide UE onboarding function as specified in clause 5.30.2.10 for the UE to obtain credential and necessary information to access the SNPN, or the UE can leverage existing credential and network connection to get access to a PVS via User Plane to obtain new credential. To allow the UE to access the PNI-NPN providing access to the Localized Services where NSSAA or secondary authentication/authorization during PDU session establishment is required, the UE can obtain new credential using remote provisioning functionality as defined in clause 5.39. To allow the UE to access the HPLMN or subscribed SNPN services while being registered in the PNI-NPN or SNPN, the PNI-NPN or SNPN can establish service agreements and configure inter-connect with the HPLMN or subscribed SNPN operator. If a PNI-NPN is providing access to the Localized Services, the existing roaming architecture with home-routed PDU Sessions are used. If an SNPN is providing access to the Localized Services, then the UE can access HPLMN or subscribed SNPN as described in Annex D, clauses D.3, D.6 and D.7. N.2.2 Configuration of network to provide access to Localized Services For configuring the PNI-NPN or SNPN (e.g. creation of network slice/DNN for carrying Localized Service traffic), existing OAM mechanisms can be re-used as per TS 28.557 [148] clause 6.3.1, that provides a solution for NPN provisioning by a network slice of a PLMN and for exposure of management capability of PNI-NPN (clause 6.3.2). The attributes to support this management is further documented in TS 28.541 [149]. N.2.3 Session Management aspects For session management level information and interactions such as monitoring the PNI-NPN or SNPN performance and enabling suitable QoS for UE in the PNI-NPN or SNPN for Localized Service, the following non-exhaustive options can be used: - Covered by the SLA between the PNI-NPN or SNPN operator and the Localized Service Provider. - Reuse the existing network exposure procedures as specified in TS 23.502 [3] clause 4.15, where the Localized Service Provider is taking the AF role and utilizing the exposure capability provided by the PNI-NPN or SNPN. - Enable NEF/PCF in the PNI-NPN or SNPN providing access to the Localized Services (via AF of the Localized Service Provider) to receive and forward the validity conditions and QoS requirements of the Localized Services to the AMF/SMF by reusing the existing PCF initiated AM/SM policy association procedures described in TS 23.502 [3] clause 4.16. N.3 Selection of network providing access to Localized Services The UE selects an SNPN providing access for Localized Services as described in clause 5.30.2.4.2, clause 5.30.2.4.3 and in TS 23.122 [17]. N.4 Enabling the UE access to Localized Services The access to a Localized Service is made available in a specific area and/or a specific period of time. After the UE has successfully registered to a PNI-NPN/SNPN providing access to the Localized Service, the UE can be configured with URSP rules using existing principles (see clause 6.6.2.2 of TS 23.503 [45]). The URSP rules can include an association between the UE application and the DNN/S-NSSAI which is meant for a particular Localized Service. The URSP rules can also include "Route Selection Validation Criteria" as described in Table 6.6.2.1-3 of TS 23.503 [45], with the time/location defined for the particular Localized Service. The existing LADN feature described in clause 5.6.5 can also be used for enabling the UE access to Localized Service which is defined by a LADN DNN. The S-NSSAI used for a Localized Service can be restricted to a specific area and time as described in clause 5.15. N.5 Support for leaving network that provides access to Localized Services When Localized Services in a network are completed, all UEs that are registered with the network are expected to be transferred to other network or to other network resources (e.g. other cells) within the same network, potentially within a relatively short timeframe. The other network can be HPLMN, VPLMN or another SNPN. UE can stop using the network resources for Localized Services for numerous reasons, e.g. when one or more of the following conditions apply: - Localized Services in a network are completed. - Validity conditions of network selection information are no longer met. - The user decides to stop using the Localized Services before they are completed. - A policy decision is taken by the network, with the effect that the UE is deregistered before the Localized Services are completed. NOTE: The list is not an exhaustive list and UE can stop using the network resources for Localized Services due to other reasons e.g. UE loses coverage, power off. When large number of UEs move to other network (i.e. HPLMN, VPLMN or another SNPN) or other network resources within a relatively short timeframe, the total signalling involved can cause signalling overload in the target network. Existing mechanisms for Control Plane Load Control, Congestion and Overload Control described in clause 5.19 and access control and barring described in clause 5.2.5 can be used to mitigate the signalling overload caused by returning UEs. For further enhancement of mitigation of signalling overload, additional mechanisms can be implemented to ensure spreading of the load that returning UEs cause. Such mechanisms are implementation-specific, but some guidelines that can be considered are described below: - The time validity of the network selection information given to a UE can be set somewhat longer than the actual duration of the service, e.g. users will by themselves disable Localized Service and the UE then stops using the connectivity to access the Localized Service, thus causing the UE to be moved, e.g. by performing normal network selection. - The time validity of the network selection information given to a UE can be different for each UE so that each UE performs network selection at a different time to distribute returning UEs. - When the AMF after end of Localized Services triggers deregistration of UEs, the deregistration requests can be sent at a certain rate in an adaptive and distributed manner, with the effect that the signalling load on both the source network and the target network is limited. - When the AMF after end of Localized Services triggers UE configuration update procedure, e.g. to remove S-NSSAI from the Allowed NSSAI (if dedicated S-NSSAI is used for the Localized Service), the requests can be sent at a certain rate, with the effect that the signalling load in the network is limited. When the NAS level congestion control is activated at AMF as specified in clause 5.19.7.2, to prevent a UE staying in an SNPN for accessing for Localized Services but not able to get services from the SNPN due to the congestion, additional mechanism can be implemented. Such mechanisms are implementation-specific but some guidelines that can be considered are described below: - the AMF can determine whether to reject the UE with a proper cause without Mobility Management back-off timer to allow the UE to reselect another SNPN for Localized Services. N.6 Configuration of Credentials Holder for determining SNPN selection information To enable the HPLMN or the subscribed SNPN acting as Credentials Holder to generate and provision UEs with SNPN selection information for discovery and selection of SNPNs providing Localized Services, based on Localized Service agreements between the Localized Service Provider or the SNPN providing Localized Services and the HPLMN or the subscribed SNPN acting as Credentials Holder, the Localized Service Provider or the SNPN providing access to Localized Services can provide configuration information for SNPN selection to the HPLMN or the subscribed SNPN acting as Credentials Holder. The configuration information for SNPN selection may contain at least one of the following parameters: a. SNPN ID or GIN of the SNPN providing access to one or more Localized Services; b. Identification of each Localized Service; c. validity information (e.g. time validity information and optionally location validity information) for each Localized Service and/or location assistance information; and/or d. List of UE IDs (e.g. GPSIs or External Group ID) identifying the UEs subscribed with a Localized Service. NOTE: How HPLMN or subscribed SNPN obtains the information above as part of the Localized Service agreements is out of 3GPP scope. The operator of the HPLMN or the subscribed SNPN acting as Credentials Holder then may use the information received from the SNPN providing Localized Services and/or Localized Service Provider to create or update the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services and provision the UEs using the Steering of Roaming procedure as defined in TS 23.122 [17]. Annex O (informative): Allowing UE to simultaneously send data to different groups with different QoS policy This Annex provides deployment examples allowing a UE to simultaneously send data to different groups (i.e. IP or Ethernet multicast groups) with different QoS policy as in clause 6.13.2 of TS 22.261 [2]. O.1 A PDU Session with multiple QoS Flows for different groups In case the UE Application sends individual copies of data to different receivers, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: - If different groups (IP or Ethernet multicast groups) are associated to the same DNN and S-NSSAI combination used for a 5G VN group, then different QoS Flows of a single PDU Session may be used to transfer the data copy sent to different groups. Figure O.1-1 shows a PDU Session with multiple QoS Flows for different groups as an example. - Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with 5GVN.A group. The QoS for multicast address 1 is set to QoS1. For G1, its members, multicast address 1 and corresponding QoS1 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. - Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with 5GVN.A group. The QoS for multicast address 2 is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. - During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.A group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.A group to set up the QoS flow in respective member's PDU Session. As a result: - There will have two QoS flows in UE1's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, one QoS flow (QoS Flow 1.1) is used to carry data destined to multicast address 1 with QoS1, the other one (QoS Flow 1.2) is used to carry data destined to multicast address 2 with QoS2. - There will have one QoS flow (QoS Flow 2) in UE2's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, this QoS flow is used to carry data destined to multicast address 1 with QoS1. - There will have one QoS flow (QoS Flow 3) in UE3's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, this QoS flow is used to carry data destined to multicast address 2 with QoS2. - UE1 sends data with multicast address 1 (MA.1) to a UPF via QoS Flow 1.1 of UE1's PDU session for 5GVN.A group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address 1 via QoS Flow 2 of UE2's PDU Session for 5GVN.A group. - UE1 also sends the same data with multicast address 2 (MA.2) to the UPF via QoS Flow 1.2 of the same PDU Session for 5GVN.A group. The UPF forwards the packet to UE3 as it is a member of multicast group represented by multicast address 2 via QoS Flow 3 of UE3'sPDU Session for 5GVN.A group. Figure O.1-1: A PDU Session with multiple QoS Flows for different groups O.2 Multiple PDU Sessions for different groups In the case that the UE Application sends individual copies of data to different receivers, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: - If different groups (IP or Ethernet multicast groups) are associated to different DNN and S-NSSAI combinations used for different 5G VN groups, then different PDU Sessions are used to transfer the data copy sent to different groups. As a result, the UE sends the same data to different groups using the QoS Flow of the respective PDU Sessions. Figure O.2-1 shows multiple PDU sessions used for different groups as an example. - Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with 5GVN.1 group. The QoS for multicast address 1 is set to QoS1. For G1, its members, multicast address 1 and corresponding QoS1 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. - Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with 5GVN.2 group. The QoS for multicast address 2 is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. - During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.1 group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.1 group to set up the QoS flow in respective member's PDU Session. During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.2 group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.2 group to set up the QoS flow in respective member's PDU Session. As a result: - There will have two PDU Sessions for UE1: one PDU Session is targeting to DNN and S-NSSAI for 5GVN.1 group and there will have one QoS flow setup to carry data destined to multicast address 1 with QoS1; the other PDU Session is targeting to DNN and S-NSSAI for 5GVN.2 group and there will have one QoS flow setup to carry data destined to multicast address 2 with QoS2. - There will have one PDU Session for UE2: this PDU Session is targeting to DNN and S-NSSAI for 5GVN.1 group and there will have one QoS flow setup to carry data destined to multicast address 1 with QoS1. - There will have one PDU Session for UE3: this PDU Session is targeting to DNN and S-NSSAI for 5GVN.2 group and there will have one QoS flow setup to carry data destined to multicast address 2 with QoS2. - UE1 sends data with multicast address 1 (MA.1) to a UPF via the QoS Flow of UE1's PDU session for 5GVN.1 group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address 1 via the QoS Flow of UE2's PDU Session for 5GVN.1 group. - UE1 also sends the same data with multicast address 2 (MA.2) to the UPF via the QoS Flow of UE1's PDU Session for 5GVN.2 group. The UPF forwards the packet to UE3 as it is a member of multicast group represented by multicast address 2 via the QoS Flow of UE3's PDU Session for 5GVN.2 group. Figure O.2-1: Multiple PDU Sessions for different groups O.3 A PDU Session targeting a predefined group formed of multiple sub-groups In the case when the UE Application uses IP or Ethernet multicast, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: - UE establishes a PDU Session to a DNN and S-NSSAI, which can be a special DNN and S-NSSAI configured by the operator for e.g. an electrical system. The DNN and S-NSSAI is associated with a 5GVN group, which is defined as a combination of multiple sub-groups (IP or Ethernet multicast groups). - The 5G VN group and each sub-group is associated with a separate multicast address and QoS, the QoS for a 5G VN group is set to refer to the QoS of the sub-group that has the strictest QoS requirements among all the sub-group groups. When a UE belongs to multiple groups, the QoS provisioning for the groups needs to be done in the order that enables the the strictest QoS profile to be selected for the UE. For each group, its members, multicast address, corresponding QoS information, associated DNN and S-NSSAI are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503 [45]. - The application sends traffic to a multicast address depending on which group(s) it wants to target. For example, an application sends traffic to the multicast address associated with the 5G VN group. This allows an application to send a single packet reaching multiple destinations and also multiple groups. Figure O.3-1 shows a PDU Session targeting a predefined group formed of multiple sub-groups as an example. - Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with / mapped to 5GVN.1 group. The QoS for the group is set to QoS1. For G1, its members, multicast address 1, corresponding QoS1, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.1 group as described in clause 6.1.3.28 of TS 23.503 [45]. - Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with / mapped to 5GVN.2 group. The QoS for the group is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.2 group as described in clause 6.1.3.28 of TS 23.503 [45]. - GroupA (GA): a group of multicast address A with members UE1, UE2 and UE3 is associated with 5GVN.A group. G1 and G2 are combined to form the GA. The QoS for the 5GVN.A group is indicated to refer to the strictest QoS among other groups the UE belongs to. For GA, its members, multicast address A and corresponding QoS indication, DNN and S-NSSAI are provisioned as part of the AF requested QoS information for 5GVN.A group as described in clause 6.1.3.28 of TS 23.503 [45]. - During establishment or modification procedure for PDU Sessions targeting to the DNN and S-NSSAI, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information to set up the QoS flow in respective member's PDU Session. As a result: - There will have two QoS flows in UE1's PDU Session targeting to DNN and S-NSSAI, one QoS flow is used to carry data destined to multicast address 1 with QoS1, the other one is used to carry data destined to multicast address 2 with QoS2. With the QoS indication for GA, the higher QoS between QoS1 of G1 and QoS2 of G2 is selected for UE1 since the UE1 belongs to both the G1 and G2, then the QoS flow with higher QoS requirements (QoS Flow 1) is also used to carry data destined to multicast address A. - There will have one QoS flow in UE2's PDU Session targeting to DNN and S-NSSAI, this QoS flow (QoS Flow 2) is used to carry data destined to multicast address 1 with QoS1. With the QoS indication for GA, the QoS1 of G1 is selected for UE1 since the UE2 only belongs to G1, then the same QoS flow is also used to carry data destined to multicast address A. - There will have one QoS flow in UE3's PDU Session targeting to DNN and S-NSSAI, this QoS flow (QoS Flow 3) is used to carry data destined to multicast address 2 with QoS2. With the QoS indication for GA, the QoS2 of G2 is selected for UE3 since the UE3 only belongs to G2, then the same QoS flow is also used to carry data destined to multicast address A. - UE1 sends data with multicast address A (MA.A) to a UPF via QoS Flow 1 of UE1's PDU Session for 5GVN.A group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address A (MA.A) via the QoS Flow 2 of UE2's PDU Session and forwards the packet to UE3 as it is a member of the multicast group represented by multicast address A (MA.A) via the QoS Flow 3 of UE3's PDU Session. Figure O.3-1: A PDU Session targeting a predefined group formed of multiple sub-groups Annex P (informative): Personal IoT Networks P.1 PIN Reference Architecture Figure P.1-1 shows the logical Personal IoT Network (PIN) reference architecture. Figure P.1-1: PIN reference architecture A PIN consists of one or more devices providing gateway/routing functionality known as the PEGC to route the traffic towards the 5G network and one or more devices providing PIN management functionality known as the PEMC to manage the PIN; and device(s) enabling communication within the PIN called the PINE. A PINE and PEMC can be a non-3GPP device. The PIN can also have an AF for PIN (see TS 23.542 [181]). The AF for PIN can be deployed by mobile operator or by an authorized third party. When the AF for PIN is deployed by third party, the interworking with 5GC is performed via the NEF. With PIN-DN communication, the PEMC and PEGC communicates with the AF for PIN at the application layer over the user plane. The PEGC and PEMC can communicate with each other via PIN direct communication using 3GPP access (e.g. PC5) or non-3GPP access (e.g. WiFi, BT) or via PIN indirect communication using a PDU Session in the 5GS. P.2 Session management and traffic routing for PIN The general session management principles as described in clause 5.6, the QoS model as defined in clause 5.7 and the User Plane management for 5GS as defined in clause 5.8 are applicable to PIN-DN communication and PIN indirect communication. If a PIN has multiple PEGCs, 5G VN group communication mechanisms can be used for PIN indirect communication. In this case a dedicated SMF set is used for managing the PIN related PDU Sessions from all the PEGCs of that PIN and the PDU session management principles for 5G VN-LAN-type services as specified in clause 5.29.3 are applicable. The user plane handling for 5G LAN-type services as specified in 5.29.4 are applicable with following differences: - For PIN indirect communication N19-based traffic forwarding is not used i.e. the PIN traffic is forwarded using: - N6-based traffic forwarding method, where the UL/DL traffic for the PIN communication is forwarded to/from the DN; - local switching as depicted in Figure P.2-1 below, following the principles of local switching of traffic for 5G VN LAN-type service. Figure P.2-1: Local-switch based user plane architecture for PIN NOTE: Figure P.2-1 does not show traffic from a PEMC. The SMF configures the UPF(s) to apply N6-based traffic forwarding to route traffic between PDU Sessions of different PEGCs of a PIN as specified in clause 5.8.2.13. The SMF can apply local switching as specified in clause 5.8.2.13 in order to enable UPF locally forward uplink stream from one PDU session of one PEGC of a PIN as downlink stream of PDU session of one or more PEGC(s) of the same PIN. For local switching of PIN traffic between PIN related PDU sessions from different PEGCs of a single PIN, based on the (DNN, S-NSSAI) combination that is used for the PDU session related to PIN, the SMF provides a Network Instance to the UPF in FAR and/or PDR via N4 Session Establishment/Modification procedures. Annex Q (informative): Satellite coverage availability information The protocol and format of satellite coverage availability information to be provisioned to the UE via PDU session or SMS is not defined in this release of the specification, but this annex provides some examples on the information that constitutes input to the source of satellite coverage availability information e.g. external server and the output it provides to the UE. Satellite coverage availability information can be indicated to the UE by indications corresponding to whether or not coverage is available for a specific satellite RAT Type for a particular location and time, where: - These indications can be Boolean "True" (e.g. coverage available) and "False" (coverage not available); - locations can correspond to grid points in a fixed array (e.g. rectangular, hexagonal); - Coverage availability times may occur at fixed periodic intervals; and - Coverage availability information is per RAT Type. The information provisioned to the UE can include coverage information on only one PLMN or multiple PLMNs. If Satellite coverage availability information indicates coverage is available then additional information on whether PLMN is allowed to operate in that location can be provided to the UE. In order for the source of satellite coverage availability information to provide accurate information to the UE, a UE might indicate for example the following information to a source of satellite coverage availability information (e.g. an external server): - Serving PLMN ID (if not already known or implied). - One or more satellite RAT Types (where satellite coverage availability information is then expected for these one or more RAT Types). - List of supported satellite frequency bands (if not implied by the particular RAT Types). - Present UE location (e.g. latitude and longitude) for a reference grid point (e.g. the most Southerly and then most Westerly grid point). - Type of Array (e.g. rectangular or hexagonal). - Minimum elevation angle. Based on the above information provided by the UE, satellite coverage availability information could be delivered to the UE as a sequence of time durations for each grid point where each time duration includes an indication of coverage availability or unavailability one example of many alternatives as illustrated below for a particular grid point with N different durations: Satellite coverage availability information at a given grid point = <N> <Binary 0 or 1><Duration 1> <Binary 0 or 1><Duration 2> . . . . <Binary 0 or 1><Duration N> The above would be concatenated for all of the grid points to produce the satellite coverage availability information. When SMS is used to deliver the satellite coverage availability information, the UE input and satellite coverage availability information output can be delivered in a series of concatenated SMS messages using possibly the same format. Annex R (Informative): 5GS support for Indirect Network Sharing deployment R.1 General This annex provides guidance on how 5GS features and capabilities can be used to support Indirect Network Sharing deployment option which is specified in clause 6.21 of TS 22.261 [2]. The Indirect Network Sharing deployment option is described in clause 5.18 and further illustrated in the Figure 5.18.1-2. In the geographical areas with Indirect Network Sharing deployment, the existing mobility restriction mechanisms specified in clause 5.3.4.1 can be applied. This can be controlled by the UE subscription data related to mobility restriction and Indirect Network Sharing policies in the serving AMF. For the mobility management, the related procedures (e.g. handover, mobility registration update) specified in clause 4.23 of TS 23.502 [3] can be reused. Annex S (informative): Architecture examples and protocol stacks for MWAB support S.1 General This Annex provides system architecture examples for MWAB operations in PLMN cases and NPN cases. The example protocol stacks for the MWAB support are also provided. S.2 System architecture for MWAB operation in PLMNs Figures S.2-1 and S.2-2 present an example architecture for the MWAB operation when no roaming was involved for the MWAB-UE. In this case, there may be one or two PLMNs involved, i.e. the BH PLMN that serves the MWAB-UE and the MWAB Broadcasted PLMN that serves the UE connected to the MWAB can be the same or different. The MWAB-gNB logically belongs to MWAB Broadcasted PLMN and announces the PLMN IDs of the MWAB Broadcasted PLMN. The MWAB-gNB establishes N2 and N3 connection with the UE AMF and UE UPF in the MWAB Broadcasted PLMN via the PDU session of the MWAB-UE established with BH PLMN. The BH UPF in the BH PLMN serves the MWAB-UE and provides the connection via a N6 interface towards the MWAB Broadcasted PLMN, to carry the N2 and N3 traffic from MWAB-gNB. The BH UPF also supports the access to the OAM servers in the MWAB Broadcasted PLMN by the MWAB-gNB. NOTE: Depending on deployment requirement, a security gateway may be required between the BH UPF and the MWAB Broadcasted PLMN network. In that case, the MWAB-gNB need to connect to the security gateway based on pre-configured security credentials. The traffic between MWAB-gNB and the MWAB Broadcasted PLMN goes inside the security tunnel established via the security gateway. UE connected to the MWAB-gNB can access the 5GS services offered by MWAB Broadcasted PLMN. No MWAB specific enhancement to the UE is required. The UE connected to the MWAB-gNB is not aware of the BH PLMN and thus does not need any roaming agreement between its HPLMN and the BH PLMN. Figure S.2-1: Architecture for MWAB operation support - non-roaming with one PLMN Figure S.2-2: Architecture for MWAB operation support - non-roaming with two PLMNs Figure S.2-3 presents an example architecture for the MWAB operation when MWAB-UE is roaming with a Local Breakout PDU Session for its operation. In this case, there may be three PLMNs involved, i.e. the BH PLMN that serves the MWAB-UE and the MWAB Broadcasted PLMN that serves the UE connected to the MWAB and the HPLMN of the MWAB-UE. The use of the Local Breakout PDU Session by the MWAB-UE can be configured by its HPLMN, e.g. with some VPLMN specific URSP rules. In some cases, the BH PLMN and MWAB Broadcasted PLMN can be the same PLMN as illustrated in figure S.2-1. The BH PLMN can access the MWAB-UE's HPLMN UDM for the subscription information. The rest of the operations are similar to that shown in figure S.2-1 and figure S.2-2. Figure S.2-3: Architecture for MWAB operation support - MWAB-UE roaming with Local Breakout Figure S.2-4 presents an example architecture for the MWAB operation when MWAB-UE is roaming with a Home Routed PDU session for its operation. In this case, PDU session of the MWAB-UE is routed by BH PLMN to the HPLMN of the MWAB-UE. The rest of the operations are similar to that shown in figure S.2-3. In some cases, the BH PLMN and MWAB Broadcasted PLMN can be the same PLMN as illustrated in figure S.2-1. Figure S.2-4: Architecture for MWAB operation support - MWAB-UE roaming with Home Routed In figure S.2-1, figure S.2-2, figure S.2-3 and figure S.2-4, if the UE served by the MWAB is roaming, there can be another PLMN (not shown in the figures), i.e. the HPLMN of the UE served by the MWAB, involved. The interaction of the HPLMN of the UE and the MWAB Broadcasted PLMN follows that described in clause 4.2.4 for the roaming case. The UE served by the MWAB-gNB is not aware of BH PLMN and thus does not need any roaming agreement between its HPLMN and the BH PLMN. S.3 Architectures to support MWAB in SNPN case The MWAB operation also supports SNPN and the corresponding architectures are presented in figures S.3-1, S.3-2 and S.3-3. The MWAB operation also supports mixed PLMN and SNPN operation, i.e. in the architecture presented in figures S.3-1, S.3-2 and S.3-3, the BH SNPN can be replaced by a PLMN and MWAB Broadcasted SNPN remains a SNPN. The SNPN operations as described in clause 5.30 apply to the MWAB-UE and the UE served by the MWAB-gNB. Figures S.3-1 and S.3-2 present example architectures for the MWAB operation when the serving SNPN of the MWAB-UE is the same as subscribed SNPN of MWAB-UE. In this case, there may be two SNPNs involved, i.e. the BH SNPN that serves the MWAB-UE and the MWAB Broadcasted SNPN that serves the UE connected to the MWAB-gNB. The MWAB-gNB establishes N2 and N3 connection with the UE AMF and UE UPF via the PDU session of the MWAB-UE established with BH SNPN. MWAB-gNB announces SNPN ID of MWAB Broadcasted SNPN. Figure S.3-1: Architecture for MWAB operation support for SNPN - with MWAB-UE served by the subscribed SNPN (BH SNPN) and MWAB-gNB in the same SNPN Figure S.3-2: Architecture for MWAB operation support for SNPN - with MWAB-UE served by the subscribed SNPN (BH SNPN) and MWAB-gNB in different SNPN Figure S.3-3 presents an example architecture for the MWAB operation when the MWAB-UE accesses its serving SNPN using credentials owned by a Credential Holder. In this case, besides the two SNPNs, i.e. the BH SNPN that serves the MWAB-UE and the MWAB Broadcasted SNPN that serves the UE connected to the MWAB-gNB, the Credential Holder of MWAB-UE is also involved. The MWAB-gNB establishes N2 and N3 connection with the UE AMF and UE UPF via the PDU session of the MWAB-UE established with BH SNPN. MWAB-gNB announces SNPN ID of the MWAB Broadcasted SNPN. Figure S.3-3: Architecture for MWAB operation support for SNPN - with MWAB-UE accesses BH-SNPN with credentials from a CH S.4 Protocol Stacks for MWAB node S.4.1 Control Plane Protocol Stacks to support N2 interface for MWAB node Figure S.4.1-1: Control Plane Protocol Stacks to support the N2 interface Figure S.4.1-1 illustrates the Control Plane Protocol Stacks to support the N2 interface. A PDU session between MWAB-UE and MWAB-UPF is established as a backhaul link to support the overlayed N2 interface. The N2 interface terminates at MWAB-gNB and UE-AMF respectively, which includes NGAP and SCTP/IP layer protocols between them. S.4.2 User Plane Protocol Stacks to support N3 interface for MWAB node Figure S.4.2-1: User Plane Protocol Stacks to support the N3 interface Figure S.4.2-1 illustrates the User Plane Protocol Stacks to support the N3 interface. A PDU session between MWAB-UE and MWAB-UPF is established as a backhaul link to support the overlayed N3 interface. The N3 interface terminates at MWAB-gNB and UE-UPF, which includes GTP-U and UDP/IP layer protocols between them. A PDU session between UE and UE-UPF is realized by: 1) the Uu between UE and MWAB-gNB; and 2) the N3 between MWAB-gNB and UE-UPF on top of the backhauling PDU session between MWAB-UE and MWAB-UPF. Annex T (informative): Network Energy consumption information calculation T.1 General This Annex provides examples on how EIF calculate the energy consumption for required granularities. T.2 Calculation of Energy Consumption parameters The energy consumed at a UPF (EUPF) or a gNB (EgNB) is known over a time interval T. And the EIF is aware of the data volume (DV) consumed at a UPF by a UE (DVUE,UPF), UE S-NSSAI (DVS-NSSAI,UPF), UE PDU session (DVSession,UPF) and UE QoS flow (DVFlow,UPF) over the time interval T. The EIF is aware of the overall data volume at a gNB (DVgNB), as well as at a UPF (DVUPF) which serving the UE. Then based on the below example formulas, the required granularities Energy consumption information can be obtained. To derive the of energy consumed at a gNB over a time interval T by a UE, S-NSSAI, PDU session, QoS flow, the formulas are: To derive the energy consumed at a UPF over a time interval T by a UE, S-NSSAI, PDU session, QoS flow the formulas are: It should be noted that the values and are coefficients that are common across all granularities, within the time interval T, for the respective network entities and are values that related to the energy consumption per bit of the gNB, and, respectively, the UPF. To derive the energy consumed in the network in the time interval T by a UE (EUE), S-NSSAI (ES-NSSAI), PDU Session (ESession), QoS flow (EFlow), the formula is: where are all gNBs used by the UE in an interval T, are all UPFs used by the UE in an interval T. where are all gNBs used by the S-NSSAI in an interval T, are all UPFs used by the S-NSSAI in an interval T. where are all gNBs used by the PDU Session in an interval T, are all UPFs used by the PDU Session in an interval T. where are all gNBs used by the QoS Flow in an interval T, are all UPFs used by the QoS Flow in an interval T. can also be obtained as the sum of for the given UE: Annex U (informative): Support of traffic offloading at the H-UPF deployed nearby VPLMN for HR PDU Session U.1 General The Home PLMN operator can deploy H-UPFs on sites located physically close to the VPLMN (e.g. visited region) for the support of the local traffic routing at the H-UPF, i.e. home session breakout performed at the H-UPF controlled by H-SMF. Figure U.1-1: Deployment scenario for traffic offloading at the H-UPF deployed nearby VPLMN region for HR PDU Session Figure U.1-1 depicts the deployment scenario of H-UPF nearby VPLMN for HR PDU Session for traffic offloading at the H-UPF. For simplicity, other network functions are not shown. U.2 PDU Session establishment for supporting traffic offloading at the H-UPF This clause describes the HR PDU Session establishment for the roaming traffic offloading at the H-UPF deployed nearby VPLMN. The following are some considerations: 1. The H-SMF decides to support roaming traffic offloading at the H-UPF for HR PDU Session based on the configured operator policy 2. When performing H-UPF selection as described in clause 6.3.3.3, UE location information (e.g. MNC and MCC of the VPLMN) can be considered in order to select a H-UPF nearby VPLMN for a given HR PDU Session, based on the HPLMN operator policy. 3. Based on the operator policy, the selected H-UPF deployed nearby VPLMN can provide the H-SMF with the DNS server information, if it is locally configured, as described in clause 5.8.2.2. U.3 Re-establishment of PDU Session due to UP Path failure For the deployment scenario where the H-UPF of HR PDU Session is deployed nearby VPLMN, if the H-SMF receives from H-UPF the UP Path failure report for the path between the H-UPF (PSA) and V-UPF, the H-SMF acts as described in TS 23.527 [210]. If the H-SMF decides to delete the PDU session contexts associated with the path in failure as described in TS 23.527 [210], the H-SMF can trigger release of the HR PDU Session as described in clause 4.3.4.3 of TS 23.502 [3] and include an existing cause value indicating that a PDU Session re-establishment is requested. During the new HR PDU Session re-establishment, a new H-UPF and possibly new DNS server information (and DNS security information) are selected based on operator policy. Annex V (informative): NR Femto V.0 General This annex provides information on how the NR Femto can be deployed and used by means of functionalities defined in clause 5.50 and existing functionalities. V.1 NR Femto Deployment Options Figure V.1-1 depicts the deployment options of NR Femto with a locally deployed UPF close to the location of NR Femto node(s). The locally deployed UPF is a 5GC entity, has a direct N4/N9 interface with the 5GC and can be selected based on the edge computing functionality specified in clause 5.13. The NR Femto GW is optionally used as a concentrator for N2 interface. N3 interface directly goes to a centrally deployed UPF (behind the NR Femto GW) or to a locally deployed UPF (close to NR Femto node location). N3 interface may also go via the NR Femto GW where in this case, the NR Femto GW only performs routing at IP layer. Figure V.1-1: NR Femto deployment options for 5GS NOTE: The SeGW is out of the scope of this specification. Annex W (normative): UDP-Option carrying media related information over UDP tunnel tunnel When the DL traffic is end-to end encrypted and transported from the AS proxy through a UDP tunnel established using connect-udp between the AS proxy and the PSA UPF as described in clause 5.37.9.2, the AS proxy generates a XRM packet which inner UDP datagram contains the DL UDP media packets, i.e. QUIC packet between AS proxy and UE and the outer UDP datagram between AS proxy and UPF contains UDP-Option carrying encrypted media related information. Figure W-1 shows XRM packet structure. Figure W-1: XRM packet structure After the UPF establishes a QUIC connection to the AS proxy using connect-udp according to clause 5.37.9.2, the AS proxy and the PSA UPF negotiates security keys using connect-udp upgrade token in tunnelled mode. Then the AS proxy encodes media related information into the UDP-Option in outer UDP datagram and uses security keys for encrypting media related information carried in the UDP-Option. Annex X (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 06-2017 SP#76 SP-170384 - - - MCC Editorial Update for presentation to TSG SA#76 for Information 1.0.0 12-2017 SP#78 - - - - MCC Editorial Update 2.0.0 12-2017 SP#78 SP-170931 - - - Correction of Annex A figure numbers for presentation to TSG SA#78 for Approval 2.0.1 12-2017 SP#78 - - - - MCC Editorial Update after TSG SA#78 Approval 15.0.0 03-2018 SP#79 SP-180090 0002 2 F Using NRF for UPF discovery 15.1.0 03-2018 SP#79 SP-180097 0003 2 F Configuration information the UE may exchange with the SMF during the lifetime of a PDU Session 15.1.0 03-2018 SP#79 SP-180097 0004 - F Handling of MM back-off timer for N3GPP Access 15.1.0 03-2018 SP#79 SP-180097 0005 - F Correction of the definitions of Allowed NSSAI and Configured NSSAI 15.1.0 03-2018 SP#79 SP-180097 0006 4 F Allowed NSSAI and Access Type 15.1.0 03-2018 SP#79 SP-180097 0007 1 F Correction to rejected S-NSSAI 15.1.0 03-2018 SP#79 SP-180097 0008 2 F Corrections to Emergency Services 15.1.0 03-2018 SP#79 SP-180096 0009 - D Clarification of SUCI 15.1.0 03-2018 SP#79 SP-180096 0010 - D Miscellaneous editorial corrections (capitalization, messages, procedures etc.) 15.1.0 03-2018 SP#79 SP-180097 0011 - F Corrections to RQoS logic when receiving DL packet with RQI 15.1.0 03-2018 SP#79 SP-180097 0013 - F Paging Policy Differentiation correction 15.1.0 03-2018 SP#79 SP-180097 0014 - F Clarification on UE specific DRX parameter from old AMF to new AMF 15.1.0 03-2018 SP#79 SP-180097 0015 - F Clarification on PCF selection 15.1.0 03-2018 SP#79 SP-180093 0016 - F Adding the new clause about SMSF selection 15.1.0 03-2018 SP#79 SP-180090 0017 - F Use of identifiers for mobility between GERAN/UTRAN and 5GS 15.1.0 03-2018 SP#79 SP-180090 0018 1 F Remaining IP address/prefix lifetime with SSC mode 3 15.1.0 03-2018 SP#79 SP-180097 0020 1 F Correction to handling of S-NSSAI mapping information 15.1.0 03-2018 SP#79 SP-180090 0021 3 F Wildcard DNN subscription 15.1.0 03-2018 SP#79 SP-180097 0022 4 F Clarification in LADN clause 5.6.5 - TS 23.501 15.1.0 03-2018 SP#79 SP-180097 0023 - F Clean up on the interworking without 26 indication 15.1.0 03-2018 SP#79 SP-180097 0024 - F TS 23.501 mobility from EPC to 5GC 15.1.0 03-2018 SP#79 SP-18009 0025 2 F AMF Load Re-Balancing For CONNECTED mode UE 15.1.0 03-2018 SP#79 SP-180097 0026 - F Update on Traffic Detection Information 15.1.0 03-2018 SP#79 SP-180097 0027 - F Proposal of Specifying Packet Detection Rule 15.1.0 03-2018 SP#79 SP-180097 0028 1 F Relation between the SSC mode 3 and the PDU type 15.1.0 03-2018 SP#79 SP-180091 0031 - F UE-specific DRX parameter negotiation between UE and AMF 15.1.0 03-2018 SP#79 SP-180091 0033 - F Control of the Messages triggering Paging at AMF 15.1.0 03-2018 SP#79 SP-180091 0034 2 F Alignment with TS 23.502 on Service Request procedure 15.1.0 03-2018 SP#79 SP-180097 0035 - F Corrections and clarifications for the usage of Packet Filter Set 15.1.0 03-2018 SP#79 SP-180091 0036 - F Update Paging Policy Differentiation 15.1.0 03-2018 SP#79 SP-180097 0037 1 F Correction to AF influence on traffic routing 15.1.0 03-2018 SP#79 SP-180097 0038 - F Clarifications to AF influence on traffic routing 15.1.0 03-2018 SP#79 SP-180097 0039 - F Clarify NSSF discovery 15.1.0 03-2018 SP#79 SP-180090 0040 1 F Change subscribed S-NSSAI in UE to configured NSSAI of HPLMN 15.1.0 03-2018 SP#79 SP-180097 0041 1 F UDM discovery clarifications 15.1.0 03-2018 SP#79 SP-180097 0044 - F Corrections to UPF selection and resolution of related Editor's Note 15.1.0 03-2018 SP#79 SP-180097 0045 1 F Updates to the Security Edge Protection Proxy description 15.1.0 03-2018 SP#79 SP-180098 0046 - F Homogeneous support for IMS voice over PS Session supported indication 15.1.0 03-2018 SP#79 SP-180098 0047 1 F Slice selection cleanup 15.1.0 03-2018 SP#79 SP-180091 0048 - F Resource reservation for services sharing priority 15.1.0 03-2018 SP#79 SP-180098 0049 - F Replace PUI with GPSI 15.1.0 03-2018 SP#79 SP-180091 0050 - F Idle and connected state terminology cleanup 15.1.0 03-2018 SP#79 SP-180098 0051 - F NAS congestion control update 15.1.0 03-2018 SP#79 SP-180098 0052 - F Complete of IMS Emergency support in 5G including slice and local numbers 15.1.0 03-2018 SP#79 SP-180098 0053 1 F Traffic mapping information that disallows UL packets 15.1.0 03-2018 SP#79 SP-180098 0054 1 F Clean-up of Characteristics signalling 15.1.0 03-2018 SP#79 SP-180093 0055 - F EPS Fallback for voice 15.1.0 03-2018 SP#79 SP-180098 0056 1 F Network sharing prioritised PLMN handling 15.1.0 03-2018 SP#79 SP-180098 0057 2 F Corrections to Combined N3IWF/ePDG Selection 15.1.0 03-2018 SP#79 SP-180091 0058 1 F Moving Network Analytics functionality into 23.501 15.1.0 03-2018 SP#79 SP-180098 0061 1 F Clarification on UDR 15.1.0 03-2018 SP#79 SP-180098 0062 - F QFI in N9 15.1.0 03-2018 SP#79 SP-180098 0063 1 F NF Service Discovery Corrections 15.1.0 03-2018 SP#79 SP-180098 0064 3 F UE mobility event notification 15.1.0 03-2018 SP#79 SP-180092 0066 4 C Architectural solution for User Plane (UP) Security policy and User Plane Integrity Protection 15.1.0 03-2018 SP#79 SP-180098 0068 - F CN assistance information enhancement 15.1.0 03-2018 SP#79 SP-180098 0070 - F Inter-PLMN mobility when N26 is not used 15.1.0 03-2018 SP#79 SP-180093 0071 3 F Interworking without N26 corrections 15.1.0 03-2018 SP#79 SP-180098 0072 1 F Clarification for S-NSSAI based congestion Control 15.1.0 03-2018 SP#79 SP-180098 0073 - F Non-roaming Architecture for Network Exposure Function in reference point representation 15.1.0 03-2018 SP#79 SP-180098 0074 1 F NSSF service update 15.1.0 03-2018 SP#79 SP-180092 0075 1 F Correcting the support of charging Characteristics 15.1.0 03-2018 SP#79 SP-180098 0076 - F Non-Allowed Area as criterion for Cell Reselection or trigger for PLMN Selection 15.1.0 03-2018 SP#79 SP-180098 0077 1 F Correction to the use of Redirection in EPS fallback for emergency services 15.1.0 03-2018 SP#79 SP-180098 0078 2 F Network Provided Location for non-3GPP access 15.1.0 03-2018 SP#79 SP-180098 0082 1 F Updates to TS 23.501 Scope 15.1.0 03-2018 SP#79 SP-180098 0083 1 F Fixes for CP protocol stack 15.1.0 03-2018 SP#79 SP-180098 0084 1 F EPC to 5GC Migration fixes for Option 7 15.1.0 03-2018 SP#79 SP-180098 0085 1 F EPS Interworking: 5G-S-TMSI derivation and context retrieval 15.1.0 03-2018 SP#79 SP-180099 0086 1 F Fixes for Emergency Services and Emergency Services using Fallback 15.1.0 03-2018 SP#79 SP-180099 0087 2 F 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI 15.1.0 03-2018 SP#79 SP-180099 0088 4 F QoS Notification control and Release 15.1.0 03-2018 SP#79 SP-180095 0089 4 C GUTI unique across AMFs in an AMF SET 15.1.0 03-2018 SP#79 SP-180099 0090 1 F Partitioning of Identifier space to ensure success of Context retrieval for EPS Interworking 15.1.0 03-2018 SP#79 SP-180099 0091 1 F UDM Discovery with SUPI as input 15.1.0 03-2018 SP#79 SP-180099 0095 5 F Clarifications of Subscribed and Configured S-NSSAI update 15.1.0 03-2018 SP#79 SP-180099 0102 4 F Sending of congested S-NSSAI during AN signalling connection Establishment 15.1.0 03-2018 SP#79 SP-180099 0104 3 F Clarification on modification of the set of network slices for a UE 15.1.0 03-2018 SP#79 SP-180092 0105 1 F UE support for Multi-homed IPv6 PDU Session 15.1.0 03-2018 SP#79 SP-180099 0106 1 F 5GS support for network slicing 15.1.0 03-2018 SP#79 SP-180093 0107 2 F UE Core Network Capability handling 15.1.0 03-2018 SP#79 SP-180099 0108 - F eCall over IMS supported over E-UTRA only 15.1.0 03-2018 SP#79 SP-180090 0109 2 F Domain selection for UE in Dual Registration mode 15.1.0 03-2018 SP#79 SP-180099 0110 2 F MICO and interworking with EPC 15.1.0 03-2018 SP#79 SP-180099 0115 2 F Correction of NSSAI handling 15.1.0 03-2018 SP#79 SP-180099 0116 1 F Slice Availability update 15.1.0 03-2018 SP#79 SP-180099 0122 2 F User Plane management to support interworking with EPS 15.1.0 03-2018 SP#79 SP-180099 0124 3 F Supporting Common API framework for NEF 15.1.0 03-2018 SP#79 SP-180099 0126 1 F Clarification on NAS recovery procedure in RRC Inactive 15.1.0 03-2018 SP#79 SP-180099 0129 2 F Correction for congestion control 15.1.0 03-2018 SP#79 SP-180096 0133 - D Correction for the usage of RQI bit 15.1.0 03-2018 SP#79 SP-180099 0134 5 F Clarifications for QoS Framework 15.1.0 03-2018 SP#79 SP-180099 0135 2 F DL signalling handling for non-3GPP PDU Session 15.1.0 03-2018 SP#79 SP-180099 0136 1 F Clarification on location reporting for LADN in RRC Inactive clause 5.3.3.2.5 - TS 23.501 15.1.0 03-2018 SP#79 SP-180099 0137 2 F Network Sharing and Interworking with EPS- TS 23.501 15.1.0 03-2018 SP#79 SP-180099 0138 - F Edge Computing Clarification 15.1.0 03-2018 SP#79 SP-180095 0141 1 B Supporting 3GPP PS Data Off in 5GS 15.1.0 03-2018 SP#79 SP-180099 0144 2 F Management of service area restriction information 15.1.0 03-2018 SP#79 SP-180099 0145 2 F Clarification on TAI list assignment for different 5G RATs 15.1.0 03-2018 SP#79 SP-180099 0146 - F Network sharing for supporting RRC redirection procedure 15.1.0 03-2018 SP#79 SP-180095 0147 2 C Selection of NAS procedures for E-UTRA connected to both EPC and 5GC 15.1.0 03-2018 SP#79 SP-180100 0149 1 F Clarification of SM congestion control 15.1.0 03-2018 SP#79 SP-180100 0150 1 F Updates to AF influence on traffic routing 15.1.0 03-2018 SP#79 SP-180100 0151 2 F Updates to description of CN Tunnel Info 15.1.0 03-2018 SP#79 SP-180100 0152 - F Clarification on RRM desciption 15.1.0 03-2018 SP#79 SP-180100 0153 1 F Editorial corrections in clause 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access 15.1.0 03-2018 SP#79 SP-180100 0154 2 F Clarification on the association of an S-NSSAI to a given application 15.1.0 03-2018 SP#79 SP-180100 0155 2 F Update of UE Network slicing configuration 15.1.0 03-2018 SP#79 SP-180100 0157 2 F SBA Scope Clarification 15.1.0 03-2018 SP#79 SP-180092 0158 2 F Clean up for BSF 15.1.0 03-2018 SP#79 SP-180092 0160 3 F Clarification on Area of Interest for Presence Area Reporting 15.1.0 03-2018 SP#79 SP-180100 0161 3 F Correction to Providing AF request to multiple PCFs 15.1.0 03-2018 SP#79 SP-180100 0165 1 F Usage of Unified access control in priority mechanisms 15.1.0 03-2018 SP#79 SP-180100 0166 - F Update Roaming reference architectures 15.1.0 03-2018 SP#79 SP-180100 0168 5 F Clarification of UE Requested NSSAI 15.1.0 03-2018 SP#79 SP-180100 0170 1 F Emergency Services Support indication per RAT 15.1.0 03-2018 SP#79 SP-180100 0171 2 F N4 User Plane Path 15.1.0 03-2018 SP#79 SP-180100 0173 1 F SSC Mode Selection 15.1.0 03-2018 SP#79 SP-180100 0174 2 F Proposal of QER, URR and FAR 15.1.0 03-2018 SP#79 SP-180100 0177 1 F UE specific DRX parameters for CM-CONNECTED with Inactive state 15.1.0 03-2018 SP#79 SP-180100 0179 6 F Slicing configuration update 15.1.0 03-2018 SP#79 SP-180100 0180 1 F Update of Mobility Restrictions 15.1.0 03-2018 SP#79 SP-180125 0181 1 B Addition of PDU Session type IPv4v6 15.1.0 03-2018 SP#79 SP-180100 0183 1 F Mapping of Requested NSSAI clarification 15.1.0 03-2018 SP#79 SP-180100 0184 2 F Clarification of the interworking between 5G and GERAN/UTRAN/E-UTRAN when UE is in RRC-inactive state 15.1.0 03-2018 SP#79 SP-180100 0187 5 F Select the same SMF+UPF for PDU sessions of the same DNN within one slice 15.1.0 03-2018 SP#79 SP-180100 0189 2 F Subscription Permanent Identifier 15.1.0 03-2018 SP#79 SP-180100 0192 1 F Clarification of interworking procedures without N26 interface 15.1.0 03-2018 SP#79 SP-180100 0194 1 F Clarification on the use of the indicator for the support of interworking without N26 15.1.0 06-2018 SP#80 SP-180482 0067 6 F Controlled support of (AF) session binding for Ethernet PDU Session Type 15.2.0 06-2018 SP#80 SP-180491 0117 7 F Use of Priority parameters for scheduling 15.2.0 06-2018 SP#80 SP-180489 0169 8 F Temporary restriction of Reflective QoS 15.2.0 06-2018 SP#80 SP-180478 0196 1 F 5_16_6_Mission Critical Services - Reference Update 15.2.0 06-2018 SP#80 SP-180478 0197 1 F 5_16_6_Mission Critical Services - Editorial Changes 15.2.0 06-2018 SP#80 SP-180477 0198 - D Fixing Incorrect References to the Service Request Procedures 15.2.0 06-2018 SP#80 SP-180489 0199 2 F SUPI based paging 15.2.0 06-2018 SP#80 SP-180486 0201 2 F Mobile Terminated SMS over NAS: 5GS Access Selection 15.2.0 06-2018 SP#80 SP-180483 0203 1 F Discovery and Topology Hiding 15.2.0 06-2018 SP#80 SP-180479 0206 3 F Changed length and mapping of 5GS Temporary Identifiers 15.2.0 06-2018 SP#80 SP-180488 0207 5 F Slice configuration change 15.2.0 06-2018 SP#80 SP-180483 0209 1 F Defining NWDAF in 23.501 15.2.0 06-2018 SP#80 SP-180484 0210 3 F Corrections to PFD management 15.2.0 06-2018 SP#80 SP-180491 0212 2 F Update on UE mobility event notification 15.2.0 06-2018 SP#80 SP-180485 0214 1 F Identification and update of UE derived QoS rule 15.2.0 06-2018 SP#80 SP-180479 0216 2 F Clarification of traffic steering control in the case of interworking 15.2.0 06-2018 SP#80 SP-180491 0217 2 F Updates to System Enablers for Priority Mechanism 15.2.0 06-2018 SP#80 SP-180478 0219 2 F AMF Selection aspects 15.2.0 06-2018 SP#80 SP-180478 0220 1 F AMF functionality clarification - to add SUCI 15.2.0 06-2018 SP#80 SP-180484 0222 1 F EPS Interworking Principles - SR mode with N26 15.2.0 06-2018 SP#80 SP-180490 0224 1 F UDM services - addition to Nudm_UEAuthentication 15.2.0 06-2018 SP#80 SP-180490 0225 0 F UDM functionality support for SUCI 15.2.0 06-2018 SP#80 SP-180486 0226 3 F MFBR Enforcement for GBR QoS Flows 15.2.0 06-2018 SP#80 SP-180486 0227 1 F NF Registration via the NRF 15.2.0 06-2018 SP#80 SP-180478 0229 - F Abbreviations supplement 15.2.0 06-2018 SP#80 SP-180478 0231 1 F 3GPP PS Data Off Clarification 15.2.0 06-2018 SP#80 SP-180477 0232 - D Network Sharing and Interworking Clarification 15.2.0 06-2018 SP#80 SP-180480 0237 3 F Clarification on MT SMS domain selection by SMSF 15.2.0 06-2018 SP#80 SP-180489 0239 1 F TS 23.501: Clean-up for the RRC Inactive related procedure 15.2.0 06-2018 SP#80 SP-180489 0240 - F Correction on Control Plane protocol stacks 15.2.0 06-2018 SP#80 SP-180480 0241 2 F Clarification on NSSAI related functionality in 5G RAN 15.2.0 06-2018 SP#80 SP-180489 0242 2 F Clarification on Application data 15.2.0 06-2018 SP#80 SP-180479 0244 3 F AMF UE area of interest reporting in RRC inactive state 15.2.0 06-2018 SP#80 SP-180480 0245 - F Clarification on RAT fallback 15.2.0 06-2018 SP#80 SP-180480 0248 1 F Clarification on notification message 15.2.0 06-2018 SP#80 SP-180477 0250 - D Editorial correction in clause 5.9.2 Subscription Permanent Identifier 15.2.0 06-2018 SP#80 SP-180481 0251 8 F Correction to DNN subscription 15.2.0 06-2018 SP#80 SP-180481 0254 4 F Clarification on the support of Delay Critical resource type 15.2.0 06-2018 SP#80 SP-180486 0255 7 F Network slicing clause cleanup 15.2.0 06-2018 SP#80 SP-180490 0261 1 F UE and network shall override the Core Network type restriction for regulatory prioritized services 15.2.0 06-2018 SP#80 SP-180481 0262 1 F Clarification to the usage of Internal-Group Identifier 15.2.0 06-2018 SP#80 SP-180484 0264 5 F Different types of Ethernet services and N4 15.2.0 06-2018 SP#80 SP-180487 0265 3 F Providing AF with information on the N6 User Plane tunnelling information 15.2.0 06-2018 SP#80 SP-180488 0266 4 F SMF getting UE location from the AMF for NPLI when no QoS Flow to create/Update/modify 15.2.0 06-2018 SP#80 SP-180487 0267 - F Removal of network restriction for eight concurrent S-NSSAIs when serving a UE 15.2.0 06-2018 SP#80 SP-180487 0268 - F Removal of duplicated requirements for Allowed/Configured NSSAI 15.2.0 06-2018 SP#80 SP-180482 0269 2 F Correction to AMF and S-NSSAI overload control 15.2.0 06-2018 SP#80 SP-180478 0270 - F AMF Name and AMF N2AP UE ID 15.2.0 06-2018 SP#80 SP-180482 0271 2 F Correction for support of the Ethernet Type PDU Session 15.2.0 06-2018 SP#80 SP-180484 0272 1 F Correction on aspects for LADN 15.2.0 06-2018 SP#80 SP-180489 0273 1 F Subscription status notification for Event Exposure service 15.2.0 06-2018 SP#80 SP-180480 0275 1 F Clarification on SMF selection 15.2.0 06-2018 SP#80 SP-180480 0276 2 F Clarification on SMSF selection 15.2.0 06-2018 SP#80 SP-180490 0280 1 F Update for providing policy requirements to multiple UEs 15.2.0 06-2018 SP#80 SP-180481 0282 2 F Clarifying handling of reachability state 15.2.0 06-2018 SP#80 SP-180484 0283 6 F Dual Registration mode of operation from E-UTRA cell connecting to both EPC and 5GC 15.2.0 06-2018 SP#80 SP-180482 0284 2 F Consolidation of UE Network Capabilities 15.2.0 06-2018 SP#80 SP-180486 0285 1 F NAS level congestion control for emergency and high priority access 15.2.0 06-2018 SP#80 SP-180476 0286 1 C Coexistence of RRC Inactive and Dual Connectivity 15.2.0 06-2018 SP#80 SP-180486 0287 3 F Mapped parameters in case of No N26 15.2.0 06-2018 SP#80 SP-180481 0289 2 F Clarification on the use of shared AMF Pointer value 15.2.0 06-2018 SP#80 SP-180488 0290 1 F ReAuthentication by an external DN-AAA server 15.2.0 06-2018 SP#80 SP-180484 0292 6 F LADN configuration of UE 15.2.0 06-2018 SP#80 SP-180479 0295 1 F Clarification of S-NSSAI based congestion control 15.2.0 06-2018 SP#80 SP-180478 0296 4 F Add indication of Notification Control to QoS rules sent to UE 15.2.0 06-2018 SP#80 SP-180485 0297 1 F Local deactivate MICO for emergency service 15.2.0 06-2018 SP#80 SP-180484 0298 4 F How the SMF validates UE location when requested for LADN PDU Session establishment 15.2.0 06-2018 SP#80 SP-180479 0302 1 F AUSF clarification and alignment 15.2.0 06-2018 SP#80 SP-180477 0303 - D Correction to references 15.2.0 06-2018 SP#80 SP-180480 0304 3 F Clarification on N3GPP TAI 15.2.0 06-2018 SP#80 SP-180482 0305 6 F Correction on capability negotiation on "SMS over NAS" 15.2.0 06-2018 SP#80 SP-180478 0306 1 F Alignment of the name of the network function 15.2.0 06-2018 SP#80 SP-180482 0308 3 F Correction on NAS level congestion control 15.2.0 06-2018 SP#80 SP-180479 0310 2 F Clarification on AMF management 15.2.0 06-2018 SP#80 SP-180488 0311 4 F S-NSSAI check for activation of UP connection of PDU Session 15.2.0 06-2018 SP#80 SP-180481 0313 3 F Clarifications required resulting from 6-bit QFI limit 15.2.0 06-2018 SP#80 SP-180486 0314 1 F Missing "redirection" to E-UTRA connected to 5GC 15.2.0 06-2018 SP#80 SP-180479 0319 1 F Clarification of high priority access 15.2.0 06-2018 SP#80 SP-180476 0323 3 F Dual connectivity support for network slices 15.2.0 06-2018 SP#80 SP-180481 0325 - F Clarification to the NRF Roaming architecture 15.2.0 06-2018 SP#80 SP-180488 0326 2 F Slicing information and RFSP 15.2.0 06-2018 SP#80 SP-180490 0327 - F TS 23.501: UE DL Signalling handling in RRC Inactive State 15.2.0 06-2018 SP#80 SP-180489 0331 1 F Some TADs fix's 15.2.0 06-2018 SP#80 SP-180485 0334 1 F Handling of maximum supported data rate per UE for integrity protection 15.2.0 06-2018 SP#80 SP-180486 0335 - F NF/NF service registration and status subscribe/notify description updates 15.2.0 06-2018 SP#80 SP-180491 0336 1 F Use of results of NF/NF service discovery for NF/NF service selection 15.2.0 06-2018 SP#80 SP-180489 0338 4 F Subscribed SMSF address 15.2.0 06-2018 SP#80 SP-180488 0339 - F SEPP fully redundant and next-hop IPX proxy 15.2.0 06-2018 SP#80 SP-180488 0342 1 F SMF selection factor 15.2.0 06-2018 SP#80 SP-180485 0344 - F IPsec SAs in tunnel mode 15.2.0 06-2018 SP#80 SP-180484 0345 1 F Determining interworking support for PDU sessions in case of interworking without N26 15.2.0 06-2018 SP#80 SP-180485 0346 1 F Fixing the definition of signalled QoS rule 15.2.0 06-2018 SP#80 SP-180481 0349 2 F Clarify GUTI aspects for single-registration mode UEs for interworking without N26 15.2.0 06-2018 SP#80 SP-180486 0351 - F N9 missing in some figures 15.2.0 06-2018 SP#80 SP-180486 0352 2 F NF instance and NF service instance definitions 15.2.0 06-2018 SP#80 SP-180483 0353 2 F Correction to UE Radio Capability handling 15.2.0 06-2018 SP#80 SP-180485 0355 1 F Further QoS clean-up 15.2.0 06-2018 SP#80 SP-180482 0356 1 F Coordination of reference point allocation 15.2.0 06-2018 SP#80 SP-180485 0359 2 F Handling of Configured NSSAIs in Roaming Scenarios - 23.501 15.2.0 06-2018 SP#80 SP-180490 0363 1 F Update and correction of table for AMF, UDM, UDR, NSSF, UDSF and BSF services 15.2.0 06-2018 SP#80 SP-180490 0365 1 F Update of FAR 15.2.0 06-2018 SP#80 SP-180486 0367 1 F NEF Services 15.2.0 06-2018 SP#80 SP-180477 0368 2 D Editor's note clean-up 15.2.0 06-2018 SP#80 SP-180482 0370 3 F Compute - Storage split principles 15.2.0 06-2018 SP#80 SP-180484 0371 - F Emergency Services Fallback Support indicator validity in the Registration Area 15.2.0 06-2018 SP#80 SP-180485 0372 - F LMF Services 15.2.0 06-2018 SP#80 SP-180490 0375 2 F UDM-AUSF Discovery 15.2.0 06-2018 SP#80 SP-180481 0383 2 F Clarification on usage of PLMN ID received via PCO during PDN connection establishment 15.2.0 06-2018 SP#80 SP-180483 0385 - F Correction to the mapping to the Subscribed S-NSSAI(s) 15.2.0 06-2018 SP#80 SP-180487 0386 2 F Provisioning NSSP 15.2.0 06-2018 SP#80 SP-180489 0389 1 F Tracking Area in 5GS 15.2.0 06-2018 SP#80 SP-180483 0390 1 F Correction to S-NSSAI congestion 15.2.0 06-2018 SP#80 SP-180481 0391 1 F Clarification to PDU Session Types: MTU 15.2.0 06-2018 SP#80 SP-180478 0394 3 F Alignment of radio capabilities procedure 15.2.0 06-2018 SP#80 SP-180482 0396 2 F CN type indicator in AS signalling 15.2.0 06-2018 SP#80 SP-180483 0397 1 F Correction to eCall Support by NR 15.2.0 06-2018 SP#80 SP-180479 0398 1 F Bit rate enforcement 15.2.0 06-2018 SP#80 SP-180480 0399 - F Clarification on TAC format at inter-system handover 15.2.0 06-2018 SP#80 SP-180478 0401 1 F Add table of CHF Spending Limit Control service in 7.2.x 15.2.0 06-2018 SP#80 SP-180488 0402 2 F S-NSSAI of VPLMN when HO from 4G to 5G 15.2.0 06-2018 SP#80 SP-180489 0403 - F SSC Mode Selection clarification 15.2.0 06-2018 SP#80 SP-180485 0404 1 F How Peer CP NF sends notification to target/new AMF after AMF planned removal 15.2.0 06-2018 SP#80 SP-180478 0405 1 F AF influence on traffic routing for Ethernet type PDU Session 15.2.0 06-2018 SP#80 SP-180479 0406 2 F Avoid the case the one UE MAC shared by multiple Ethernet PDU Sessions 15.2.0 06-2018 SP#80 SP-180485 0407 1 F How AMF provides LADN Information to UE 15.2.0 06-2018 SP#80 SP-180477 0410 - D Non-3GPP access node selection information 15.2.0 06-2018 SP#80 SP-180496 0411 - F Clarify RAT restrictions are not provided to the UE 15.2.0 06-2018 SP#80 SP-180485 0414 1 F Including GUAMI in RRC message of related procedures 15.2.0 06-2018 SP#80 SP-180479 0415 1 F Clarification on CN assistance information 15.2.0 06-2018 SP#80 SP-180481 0416 2 F Clarify the relationship between GFBR and MDBV 15.2.0 06-2018 SP#80 SP-180480 0417 2 F Clarification on support of MFBR greater than GFBR 15.2.0 06-2018 SP#80 SP-180480 0418 1 F Clarification on requested NSSAI usage by RAN 15.2.0 06-2018 SP#80 SP-180480 0422 - F Clarification on SMSF checking subscription data 15.2.0 06-2018 SP#80 SP-180488 0423 - F S-NSSAI back off timer for UE requested PDU session release 15.2.0 06-2018 SP#80 SP-180479 0424 2 F Clarification on AF influence on traffic routing 15.2.0 06-2018 SP#80 SP-180482 0425 2 F Combined SMF+PGW-C Selection 15.2.0 06-2018 SP#80 SP-180488 0430 - F Resume procedure in the equivalent PLMN 15.2.0 06-2018 SP#80 SP-180478 0433 - F Alignment of selective activation of UP connection of existing PDU Session 15.2.0 06-2018 SP#80 SP-180478 0435 1 F Alignment of PCF selection description 15.2.0 06-2018 SP#80 SP-180487 0436 4 F QNC during Handover 15.2.0 06-2018 SP#80 SP-180487 0437 3 F Reflective QoS in interworking 15.2.0 06-2018 SP#80 SP-180491 0438 2 F Use of Network Instance 15.2.0 06-2018 SP#80 SP-180490 0439 3 F Update of N4 Parameter Descriptions and Tables 15.2.0 06-2018 SP#80 SP-180480 0441 3 F Clarification on LADN 5.6.5 15.2.0 06-2018 SP#80 SP-180486 0444 3 F Network slicing subsription change and update of UE configuration 15.2.0 06-2018 SP#80 SP-180479 0446 2 F Clarification note on Network Slice limitation 15.2.0 06-2018 SP#80 SP-180478 0447 1 F Adding default value for Averaging Window 15.2.0 06-2018 SP#80 SP-180486 0448 1 F Mobility restrictions 15.2.0 06-2018 SP#80 SP-180479 0451 2 F Capturing subsequent mobility to and from GERAN/UTRAN 15.2.0 06-2018 SP#80 SP-180485 0453 - F GFBR is applicable only for GBR QoS Flows 15.2.0 06-2018 SP#80 SP-180556 0454 2 F NSSAI handling in PDU Session Establishment procedures in roaming 15.2.0 06-2018 SP#80 SP-180483 0456 1 F Correction to identifiers in Registration procedure 15.2.0 06-2018 SP#80 SP-180487 0459 1 F Radio capabilities after 5GS registration 15.2.0 09-2018 SP#81 SP-180713 0455 3 F Storage of structured proprietory data in UDSF 15.3.0 09-2018 SP#81 SP-180713 0460 3 F Missing TADs behaviour 15.3.0 09-2018 SP#81 SP-180713 0463 - F Correcting handling of RAT restriction and Forbidden Areas 15.3.0 09-2018 SP#81 SP-180713 0464 3 F Clarification on LADN 15.3.0 09-2018 SP#81 SP-180713 0465 3 F Clarification on a wildcard DNN 15.3.0 09-2018 SP#81 SP-180713 0466 3 F Correcting use of identifiers during registration in equivalent PLMNs 15.3.0 09-2018 SP#81 SP-180713 0470 1 F Clarification on UE context exchanged on N26 interface 15.3.0 09-2018 SP#81 SP-180713 0471 1 F Correction to AF influence on traffic routing 15.3.0 09-2018 SP#81 SP-180713 0472 2 F Clarification on UE Registration type with only PDU Session for Emergency Services 15.3.0 09-2018 SP#81 SP-180713 0473 7 F The resource type of QoS Flow associated with the default QoS rule 15.3.0 09-2018 SP#81 SP-180724 0474 5 B Support of tracing in 5GS signalling: overview 15.3.0 09-2018 SP#81 SP-180713 0475 - F MCC implementation correction of 23.501 CR0255R7 15.3.0 09-2018 SP#81 SP-180713 0480 3 F 5QI-QCI alignment 15.3.0 09-2018 SP#81 SP-180713 0481 2 F Number of packet filters supported by UE 15.3.0 09-2018 SP#81 SP-180713 0482 2 F Paging policy differentiation for RRC inactive 15.3.0 09-2018 SP#81 SP-180713 0485 4 F Application detection report when the PFDs are removed 15.3.0 09-2018 SP#81 SP-180713 0487 5 F Correction to Configured NSSAI for the HPLMN 15.3.0 09-2018 SP#81 SP-180713 0488 1 F Correction to TAI list generation 15.3.0 09-2018 SP#81 SP-180713 0493 1 F Network Exposure in Roaming Situations 15.3.0 09-2018 SP#81 SP-180713 0494 1 F Handling of UP Security Policy when IWK with EPS 15.3.0 09-2018 SP#81 SP-180713 0497 2 F Clarification on handling of Ethernet frames at UPF 15.3.0 09-2018 SP#81 SP-180713 0498 4 F Completion of description on Configured NSSAIs 15.3.0 09-2018 SP#81 SP-180713 0499 - F LADN Clarification 15.3.0 09-2018 SP#81 SP-180713 0500 1 F DNN Usage Clarification 15.3.0 09-2018 SP#81 SP-180713 0501 4 F Clarification for pre-configured QoS rule 15.3.0 09-2018 SP#81 SP-180714 0502 1 F Clarification for QoS handling at UPF 15.3.0 09-2018 SP#81 SP-180714 0504 3 F DL signalling handling for non-3GPP PDU Session 15.3.0 09-2018 SP#81 SP-180714 0508 2 F Emergency call and eCall support when the ng-eNode is connected to EPC and 5GC 15.3.0 09-2018 SP#81 SP-180714 0509 1 F Mobility Restriction List clean up 15.3.0 09-2018 SP#81 SP-180714 0515 1 F Subscription of selecting the same SMF and UPF 15.3.0 09-2018 SP#81 SP-180714 0516 3 F GUAMI Definition Correction 15.3.0 09-2018 SP#81 SP-180714 0518 1 F Merging Network Slice with regular EPS Interworking 15.3.0 09-2018 SP#81 SP-180714 0520 2 F Notification Control applicability 15.3.0 09-2018 SP#81 SP-180714 0521 1 F 23.501: 5G AN Parameters sent during Service Request 15.3.0 09-2018 SP#81 SP-180714 0524 - F Null interworking with GERAN/UTRAN CS domain 15.3.0 09-2018 SP#81 SP-180714 0525 - F Correction on mobility management back-off timer 15.3.0 09-2018 SP#81 SP-180714 0527 - F 5G-TMSI should map to M-TMSI 15.3.0 09-2018 SP#81 SP-180714 0529 1 F Clarification on Homogeneous Support of IMS Voice over PS Sessions indication 15.3.0 09-2018 SP#81 SP-180714 0530 3 F Clarification on the non-IP PDU session type for EPS to 5GS interworking 15.3.0 09-2018 SP#81 SP-180714 0531 2 F Clarification on the PDU session handling in EPS to 5GS handover with N26 15.3.0 09-2018 SP#81 SP-180714 0532 1 F Incorrect text implying slicing is optional 15.3.0 09-2018 SP#81 SP-180714 0533 - F Update of SMSF selection function 15.3.0 09-2018 SP#81 SP-180714 0534 1 F Corrections to NF profile description 15.3.0 09-2018 SP#81 SP-180714 0535 1 F Corrections to NF services names and references 15.3.0 09-2018 SP#81 SP-180714 0536 - F Update on AUSF service operation to support Steering of Roaming 15.3.0 09-2018 SP#81 SP-180714 0538 3 F Correction to interworking with EPC with N3GPP PDU Sessions 15.3.0 09-2018 SP#81 SP-180714 0539 3 F Emergency Services Support indicator for non-3GPP access 15.3.0 09-2018 SP#81 SP-180714 0540 1 F Clarification of the AMF Set definition 15.3.0 09-2018 SP#81 SP-180714 0542 1 F Clarification on priority service 15.3.0 09-2018 SP#81 SP-180715 0543 1 F Unified Access Control for UE configured for EAB 15.3.0 09-2018 SP#81 SP-180715 0544 2 F UE configuration of NSSAI and associated mapping 15.3.0 09-2018 SP#81 SP-180715 0545 - F Corrections to NEF functionalities description 15.3.0 09-2018 SP#81 SP-180715 0546 2 F Update of N4 Parameter Descriptions and Tables/ Ethernet PDU Session Type 15.3.0 09-2018 SP#81 SP-180715 0547 1 F Miscellaneous Corrections to SM specifications (SSC mode, PCFP reference, etc.) 15.3.0 09-2018 SP#81 SP-180715 0548 2 F Specify AUSF selection by UDM 15.3.0 09-2018 SP#81 SP-180715 0551 - F Obsolete reference to Lawful Interception specifications 15.3.0 09-2018 SP#81 SP-180715 0555 2 F Clearification on UE's configuraiton update 15.3.0 09-2018 SP#81 SP-180715 0558 2 F Corrections to AF influence (5.6.7) based on CT WG3 LS on AF influence on traffic routing 15.3.0 09-2018 SP#81 SP-180715 0559 2 F Alignment with CT WG1 on the QoS Flow Description 15.3.0 09-2018 SP#81 SP-180715 0562 - F UDM procedures in EPS-5GS interworking without N26 15.3.0 09-2018 SP#81 SP-180715 0563 - F Update of NEF service table (7.2.8) for Chargeable party and AFsessionWithQoS 15.3.0 09-2018 SP#81 SP-180715 0564 1 F Radio Capabilities for DRM in emergency services 15.3.0 09-2018 SP#81 SP-180715 0565 3 F Selection of S-NSSAIs used in the Requested NSSAI 15.3.0 09-2018 SP#81 SP-180715 0566 3 F Temporary identifier usage at interworking 15.3.0 09-2018 SP#81 SP-180715 0567 1 F Temporary identifier coordination 15.3.0 09-2018 SP#81 SP-180715 0569 1 F Updating radio capabilities from RRC_Inactive 15.3.0 09-2018 SP#81 SP-180715 0573 1 F SMS support used in different meanings 15.3.0 09-2018 SP#81 SP-180715 0575 - F Exposure function reference correction 15.3.0 09-2018 SP#81 SP-180715 0583 3 F Consistent Description of 5QI 15.3.0 09-2018 SP#81 SP-180715 0584 - F Corrections to N4 and UP tunnel protocol descriptions 15.3.0 09-2018 SP#81 SP-180715 0585 1 F Handling of pending DL NAS signalling (related to LS In S2-187632) 15.3.0 09-2018 SP#81 SP-180715 0586 - F Alignment of Slice Selection logic in the AMF and NSSF 15.3.0 09-2018 SP#81 SP-180715 0587 3 F Missing requirements to trigger Notification Control 15.3.0 09-2018 SP#81 SP-180716 0588 2 F OAuth2 Authorization Service 15.3.0 09-2018 SP#81 SP-180716 0589 2 F Clarification of the service area restriction and NSSAIs to EPLMNs 15.3.0 09-2018 SP#81 SP-180716 0591 1 F 23.501: Reference Point and Services correction 15.3.0 09-2018 SP#81 SP-180716 0592 1 F 23.501: UDM Services 15.3.0 09-2018 SP#81 SP-180716 0593 2 F 23.501: Subscription for EPS IWK 15.3.0 09-2018 SP#81 SP-180716 0594 - F 23.501: AUSF, UDM, UDR Discovery 15.3.0 09-2018 SP#81 SP-180716 0595 2 F Voice centric UE behaviour in non-allowed area 15.3.0 09-2018 SP#81 SP-180716 0597 5 F Update to PCF discovery and selection 15.3.0 09-2018 SP#81 SP-180716 0598 3 F Clarification to IMS emergency procedure 15.3.0 09-2018 SP#81 SP-180716 0604 1 F Clarification on reporting of PS Data Off status change 15.3.0 09-2018 SP#81 SP-180716 0605 4 F TAI List provision to RAN by AMF for RRC Inactive UE 15.3.0 09-2018 SP#81 SP-180716 0606 2 F Clarifications for signalled QoS characteristics 15.3.0 09-2018 SP#81 SP-180716 0608 1 F IPv6 multi-homed routing rule 15.3.0 09-2018 SP#81 SP-180716 0609 1 F Clarification on priority of URSP and configuration of association between application and LADN DNN 15.3.0 09-2018 SP#81 SP-180716 0616 2 F Update N4 principles and parameters 15.3.0 09-2018 SP#81 SP-180716 0617 - F Clarification on NF profile parameters 15.3.0 09-2018 SP#81 SP-180716 0618 - F Update to service area restriction 15.3.0 09-2018 SP#81 SP-180791 0611 3 F Clarification on the AMF store the DNN and PGW-C+SMF to UDM/HSS without N26. 15.3.0 2018-12 SP#82 SP-181084 0576 6 F CHF discovery and selection 15.4.0 2018-12 SP#82 SP-181085 0590 2 F Clarification to the slice based congestion control handling at NG-RAN 15.4.0 2018-12 SP#82 SP-181085 0607 11 F Clarifications for 5QI priority level 15.4.0 2018-12 SP#82 SP-181090 0621 2 F Using preconfigured 5QI for QoS Flow associated with the default QoS rule 15.4.0 2018-12 SP#82 SP-181090 0622 3 F Update of Default Configured NSSAI 15.4.0 2018-12 SP#82 SP-181086 0625 2 F Clarifying the boundaries of an NF instance 15.4.0 2018-12 SP#82 SP-181086 0626 - F Correcting discovery and selection 15.4.0 2018-12 SP#82 SP-181089 0628 3 F Reporting PS Data Off status change when SM back off timer is running 15.4.0 2018-12 SP#82 SP-181086 0629 1 F Correction of the indication of UE 5GSM capabilities after intersystem change 15.4.0 2018-12 SP#82 SP-181090 0630 1 F UE unable to use N3IWF identifier configuration in stand-alone N3IWF selection 15.4.0 2018-12 SP#82 SP-181089 0633 2 F Removal of Editor's Note re mandatoriness of RRC_Inactive 15.4.0 2018-12 SP#82 SP-181084 0634 3 F Avoiding mandatory MME impacts from 3-byte TAC 15.4.0 2018-12 SP#82 SP-181084 0637 1 F Alignment of NF Profile with adding priority parameter 15.4.0 2018-12 SP#82 SP-181084 0638 2 F Clarification on RQ Timer 15.4.0 2018-12 SP#82 SP-181088 0639 2 F Interactions with PCF - Updates to reference architecure for interworking 15.4.0 2018-12 SP#82 SP-181089 0641 1 F Registration Area and Service Restriction Area in relation to multiple PLMNs 15.4.0 2018-12 SP#82 SP-181086 0645 1 F Correcting the interaction needed for the NSSF service 15.4.0 2018-12 SP#82 SP-181086 0648 - F Connections on Default Configured NSSAI 15.4.0 2018-12 SP#82 SP-181086 0651 1 F Correction and clarification for CM-CONNECTED with RRC Inactive state 15.4.0 2018-12 SP#82 SP-181089 0653 2 F SUPI definition and NAI format 15.4.0 2018-12 SP#82 SP-181084 0655 1 F Addition of abbreviations 15.4.0 2018-12 SP#82 SP-181088 0656 8 F Network controlled NSSAI for SR-related Access Stratum connection establishment 15.4.0 2018-12 SP#82 SP-181195 0660 8 F Unified Access Control clarification and triggers 15.4.0 2018-12 SP#82 SP-181087 0661 3 B Data Volume Reporting for Option 4/7 15.4.0 2018-12 SP#82 SP-181086 0662 4 F Configuration Transfer Procedure 15.4.0 2018-12 SP#82 SP-181084 0666 3 F Avoiding overloading the target of AMF Load Re-Balancing 15.4.0 2018-12 SP#82 SP-181090 0667 1 F UE storage of NSSAI and associated mapping 15.4.0 2018-12 SP#82 SP-181085 0668 1 F Clarification of PS Voice Support for 3GPP and non-3GPP 15.4.0 2018-12 SP#82 SP-181089 0669 1 F Secondary authentication update 15.4.0 2018-12 SP#82 SP-181087 0671 1 F Emergency registration in a normally camped cell 15.4.0 2018-12 SP#82 SP-181088 0672 1 F Priority indication over SBA interfaces via Message Priority header 15.4.0 2018-12 SP#82 SP-181088 0675 3 F MME/AMF registration in HSS+UDM 15.4.0 2018-12 SP#82 SP-181086 0676 1 F Completion of 5QI characteristics table 15.4.0 2018-12 SP#82 SP-181086 0677 - F Consistent usage of terminology in QoS notification control description 15.4.0 2018-12 SP#82 SP-181084 0679 3 F Alignment for always-on PDU sessions 15.4.0 2018-12 SP#82 SP-181089 0680 1 C PS Data Off supporting non-IP data packet 15.4.0 2018-12 SP#82 SP-181089 0682 3 F Clarification on the PDU Session handover procedure with the User Plane Security Enforcement 15.4.0 2018-12 SP#82 SP-181089 0683 1 F Clean up congestion control 15.4.0 2018-12 SP#82 SP-181089 0685 3 F Correction on SSCMSP 15.4.0 2018-12 SP#82 SP-181089 0686 4 F Clarification on the AMF store the DNN and PGW-C+SMF to UDM+HSS 15.4.0 2018-12 SP#82 SP-181085 0687 1 F Clarification on NPLI for EPS Fallback 15.4.0 2018-12 SP#82 SP-181087 0688 1 F Correction on UE inclusion of UE's usage setting 15.4.0 2018-12 SP#82 SP-181090 0690 3 F UE radio capability for paging information with NR and eLTE connected to the CN 15.4.0 2018-12 SP#82 SP-181087 0691 2 F Correction to traffic steering control 15.4.0 2018-12 SP#82 SP-181090 0692 - F Using TCP for reliable NAS transport between UE and N3IWF 15.4.0 2018-12 SP#82 SP-181084 0693 1 C 5GS Support for MCS Subscription 15.4.0 2018-12 SP#82 SP-181091 0695 1 F UE sending UE Integrity Protection Data Rate capability over any access 15.4.0 2018-12 SP#82 SP-181087 0696 1 F Correction on Subscribed 5QI 15.4.0 2018-12 SP#82 SP-181089 0699 - F Selective deactivation for always-on PDU sessions 15.4.0 2018-12 SP#82 SP-181091 0701 1 F Use of emergency DNN when Emergency Registered 15.4.0 2018-12 SP#82 SP-181090 0703 3 F Requirements on 5G-TMSI randomness 15.4.0 2018-12 SP#82 SP-181087 0707 1 F Emergency registration over two accesses 15.4.0 2018-12 SP#82 SP-181090 0708 1 F Registration procedure with different Registration types 15.4.0 2018-12 SP#82 SP-181088 0709 2 F EPS to 5GS with network slices 15.4.0 2018-12 SP#82 SP-181084 0710 2 F AUSF and UDM selection 15.4.0 2018-12 SP#82 SP-181089 0712 2 F Providing a threshold to UPF while waiting for quota 15.4.0 2018-12 SP#82 SP-181088 0713 1 F Corrections to usage of IP index 15.4.0 2018-12 SP#82 SP-181085 0716 2 F Clarification on OVERLOAD behaviour for the EUTRA connected to 5GC 15.4.0 2018-12 SP#82 SP-181085 0719 2 F Clarification on Registration with AMF re-allocation 15.4.0 2018-12 SP#82 SP-181089 0720 1 F PDN Disconnection handling 15.4.0 2018-12 SP#82 SP-181084 0721 3 F Always on Setting for the EBI allocated PDU Session 15.4.0 2018-12 SP#82 SP-181085 0722 2 F Clarification on packet filter handling 15.4.0 2018-12 SP#82 SP-181086 0723 4 F Clarify for PDB of dynamically assigned 5QI 15.4.0 2018-12 SP#82 SP-181091 0724 2 F Update the UCU procedure with operator-defined access category definitions 15.4.0 2018-12 SP#82 SP-181087 0725 - F Correction of VLAN ID 15.4.0 2018-12 SP#82 SP-181085 0726 1 F Clarification on DN authorization data between PCF and SMF 15.4.0 2018-12 SP#82 SP-181084 0730 2 F Addition of URRP-AMF definition 15.4.0 2019-03 SP#83 SP-190154 0700 3 F Use of S-NSSAI at interworking from EPS to 5GS 15.5.0 2019-03 SP#83 SP-190154 0733 2 F Slice interworking HR mode update 15.5.0 2019-03 SP#83 SP-190154 0741 1 F UDR selection 15.5.0 2019-03 SP#83 SP-190154 0742 2 F Fixing text related to discovery and selection 15.5.0 2019-03 SP#83 SP-190154 0743 1 F Change of the term confidence level 15.5.0 2019-03 SP#83 SP-190154 0756 2 F Correction to NSSAI logic 15.5.0 2019-03 SP#83 SP-190154 0758 2 F UL Session-AMBR enforcement in UPF 15.5.0 2019-03 SP#83 SP-190154 0759 1 F Alignment with stage 3 for EPS interworking indications 15.5.0 2019-03 SP#83 SP-190154 0762 2 F Clarification of user plane security enforcement between NG-RAN and SMF in Dual Connectivity scenario 15.5.0 2019-03 SP#83 SP-190154 0767 2 F QoS Notification Control during handover 15.5.0 2019-03 SP#83 SP-190154 0773 1 F Correction to traffic steering control 15.5.0 2019-03 SP#83 SP-190154 0774 3 F Configurable time for subsequent notification that the GFBR cannot be fulfilled 15.5.0 2019-03 SP#83 SP-190154 0775 1 F Clarification for default values 15.5.0 2019-03 SP#83 SP-190154 0784 4 F 5GC emergency calls over non-3GPP 15.5.0 2019-03 SP#83 SP-190154 0786 1 F Adding UE Local Configuration as an additional option to the URSP 15.5.0 2019-03 SP#83 SP-190154 0789 - F Update of network slicing text on NSSAI inclusion in RRC 15.5.0 2019-03 SP#83 SP-190154 0791 3 C Supporting early trace in AUSF 15.5.0 2019-03 SP#83 SP-190154 0792 1 F IMS voice over PS Session Supported Indication in roaming cases. 15.5.0 2019-03 SP#83 SP-190154 0793 2 F Introduce Charging Function in overall architecture 15.5.0 2019-03 SP#83 SP-190155 0797 2 F Update of configured NSSAI handling 15.5.0 2019-03 SP#83 SP-190155 0806 3 F Corrections to AMF overlad control procedure 15.5.0 2019-03 SP#83 SP-190155 0808 - F TS 23.501 Update to Network Slice availability 15.5.0 2019-03 SP#83 SP-190155 0818 - F No services defined for Ngmlc 15.5.0 2019-03 SP#83 SP-190155 0824 6 F Clarification on DN authorization data 15.5.0 2019-03 SP#83 SP-190155 0833 - F Clarification on Establishing a PDU Session in a Network Slice 15.5.0 2019-03 SP#83 SP-190155 0834 8 F Clarification on NAS level congestion control 15.5.0 2019-03 SP#83 SP-190155 0853 6 F PS Data Off status update when congestion control is applied in AMF 15.5.0 2019-03 SP#83 SP-190155 0857 1 F Correction to Mobility Restrictions (for non-3GPP access) 15.5.0 2019-03 SP#83 SP-190155 0860 3 F Clarification on the UE behaviours under NAS level congestion control 15.5.0 2019-03 SP#83 SP-190155 0875 - F Permanent identifier with IMEISV format 15.5.0 2019-03 SP#83 SP-190155 0876 2 F Removing a superfluous NOTE about the need for ultra-low latency QCI/5Qis 15.5.0 2019-03 SP#83 SP-190155 0877 7 F Allowed Area and Non-Allowed Area encoding 15.5.0 2019-03 SP#83 SP-190155 0901 2 F Alignment of Emergency Registered definition with Stage 3 15.5.0 2019-03 SP#83 SP-190155 0904 - F Addition of PCF services Npcf_UEPolicyControl and Npcf_EventExposure 15.5.0 2019-03 SP#83 SP-190155 0910 3 F Clarification on ARP Proxy 15.5.0 2019-03 SP#83 SP-190155 0913 2 F PS Data Off status update when UE in non-allowed area or out of LADN area 15.5.0 2019-03 SP#83 SP-190155 0915 2 F Non-roaming reference architecture correction 15.5.0 2019-03 SP#83 SP-190155 0922 2 F TS 23.501: correction for enforcement of user plane integrity protection 15.5.0 2019-03 SP#83 SP-190156 0932 2 F Clarification on the PDU Session parameter 15.5.0 2019-03 SP#83 SP-190156 0942 2 F Transport Level Packet Marking 15.5.0 2019-03 SP#83 SP-190156 0943 2 F Support of baseline Frame Routing feature 15.5.0 2019-03 SP#83 SP-190156 0945 1 F Disabling E-UTRA connected to EPC radio capability 15.5.0 2019-03 SP#83 SP-190156 0949 2 F Correction of slicing terminology 15.5.0 2019-03 SP#83 SP-190156 0958 1 F Adding a new 5G-GUTI allocation condition 15.5.0 2019-03 SP#83 SP-190156 0968 2 F Clarify on Network Slice availability change 15.5.0 2019-03 SP#83 SP-190156 0969 2 F Correction the terms on Secondary authentication/authorization of the PDU Session Establishment 15.5.0 2019-03 SP#83 SP-190156 0975 1 F Clarificaiton on Core Network type Restriction 15.5.0 2019-03 SP#83 SP-190156 0976 3 F Clarification on AMF planned removal 15.5.0 2019-03 SP#83 SP-190156 0979 1 F Correction of UE 5GSM Core Network Capability 15.5.0 2019-03 SP#83 SP-190156 0982 2 F Clarification on QoS Notification control 15.5.0 2019-03 SP#83 SP-190156 0988 0 F Correction on reference 15.5.0 2019-03 SP#83 SP-190156 0992 3 F Slice interworking HR mode update 15.5.0 2019-03 SP#83 SP-190156 0996 2 F Clarification on PCF selection 15.5.0 2019-03 SP#83 SP-190156 1006 - F Corrections on routing rule 15.5.0 2019-03 SP#83 SP-190156 1012 2 F Clarification on GTP-u protocol 15.5.0 2019-03 SP#83 SP-190175 0704 4 C New 5QIs for Enhanced Framework for Uplink Streaming 16.0.0 2019-03 SP#83 SP-190169 0734 8 B TS 23.501: Introducing Non-public network 16.0.0 2019-03 SP#83 SP-190169 0747 12 B Support for 5G LAN 16.0.0 2019-03 SP#83 SP-190194 0757 8 B Introducing support for Non-Public Networks 16.0.0 2019-03 SP#83 SP-190169 0903 2 B Introduction of 5G LAN-type service 16.0.0 2019-03 SP#83 SP-190169 1007 2 B Introducing support TSC Deterministic QoS 16.0.0 2019-03 SP#83 SP-190169 1008 2 B Introducing support Hold and Forward Buffers for TSC Deterministic QoS 16.0.0 2019-03 SP#83 SP-190169 1002 3 B 5GS Logical TSN bridge management 16.0.0 2019-03 SP#83 SP-190165 0748 3 B CIoT High Level Description in 23.501 16.0.0 2019-03 SP#83 SP-190165 0751 3 B High Latency Overall Description 16.0.0 2019-03 SP#83 SP-190165 0752 4 B Introducing Rate Control for 5G CIoT 16.0.0 2019-03 SP#83 SP-190165 0768 6 B Introduction of eDRX in 5GS 16.0.0 2019-03 SP#83 SP-190165 0819 1 B CIoT Monitoring Events 16.0.0 2019-03 SP#83 SP-190165 0820 4 B Restriction of use of Enhanced Coverage in 5GC 16.0.0 2019-03 SP#83 SP-190165 0825 2 B Introduction to Reliable Data Service 16.0.0 2019-03 SP#83 SP-190165 0889 7 B Introduction of data transfer in Control Plane CIoT 5GS Optimisation 16.0.0 2019-03 SP#83 SP-190165 0890 6 B Introduction of NEF based infrequent small data transfer via NAS 16.0.0 2019-03 SP#83 SP-190165 0893 7 B Introduction of Power Saving Functions for CIoT 16.0.0 2019-03 SP#83 SP-190165 0894 5 B CIoT Introduction of Overload Control 16.0.0 2019-03 SP#83 SP-190165 0895 2 B Introduction of Inter-RAT mobility support to and from NB-IoT 16.0.0 2019-03 SP#83 SP-190165 0896 2 B CIoT Introduction of CN Selection and Steering 16.0.0 2019-03 SP#83 SP-190165 1014 2 B Introduction of Service Gap Control 16.0.0 2019-03 SP#83 SP-190173 0735 11 B Introduction of ATSSS Support 16.0.0 2019-03 SP#83 SP-190173 0740 7 B Support of Steering Functions for ATSSS 16.0.0 2019-03 SP#83 SP-190173 0770 4 B QoS for Multi-Access PDU Session 16.0.0 2019-03 SP#83 SP-190173 0921 3 B Access Network Performance Measurements 16.0.0 2019-03 SP#83 SP-190171 0810 2 B New clause for URLLC supporting 16.0.0 2019-03 SP#83 SP-190171 0753 8 B General description of solution 1 in 23.725 for user plane redundancy 16.0.0 2019-03 SP#83 SP-190171 0811 6 B Add description of solution 4 in 23.725 to 23.501 16.0.0 2019-03 SP#83 SP-190171 0872 3 B Description of solution 7 in 23.725 as replication framework 16.0.0 2019-03 SP#83 SP-190164 0732 2 B ETSUN - Architecture conclusion 16.0.0 2019-03 SP#83 SP-190164 0848 5 B UL CL/BP controlled by I-SMF 16.0.0 2019-03 SP#83 SP-190175 0704 4 C New 5QIs for Enhanced Framework for Uplink Streaming 16.0.0 2019-03 SP#83 SP-190171 0755 2 B Description of solution 11 in 23.725 for Ethernet anchor relocation 16.0.0 2019-03 SP#83 SP-190169 0734 8 B Introducing Non-public network 16.0.0 2019-03 SP#83 SP-190215 0736 10 B Introduction of indirect communication between NF services and implicit discovery 16.0.0 2019-03 SP#83 SP-190167 0744 4 B SUPI and SUCI for wireline access 16.0.0 2019-03 SP#83 SP-190167 0745 6 B Mobility restrictions for wireline access 16.0.0 2019-03 SP#83 SP-190167 0746 2 B IP addressing enhancements 16.0.0 2019-03 SP#83 SP-190169 0747 12 B Support for 5G LAN 16.0.0 2019-03 SP#83 SP-190171 0754 2 B Description of solution 2 in 23.725 for redundancy as an informational annex 16.0.0 2019-03 SP#83 SP-190173 0761 1 B ATSSS-SMF and UPF selection 16.0.0 2019-03 SP#83 SP-190165 0776 3 B CIoT Introduction of extended DRX in CM-CONNECTED with RRC Inactive state 16.0.0 2019-03 SP#83 SP-190167 0781 2 B Support of Trusted non-3GPP access 16.0.0 2019-03 SP#83 SP-190167 0783 2 B Trusted non-3GPP Access Network Selection 16.0.0 2019-03 SP#83 SP-190173 0785 5 B Updating 5.8.2.11 for N4 Rules to support ATSSS 16.0.0 2019-03 SP#83 SP-190174 0799 10 B eSBA communication schemas related to general discovery and selection 16.0.0 2019-03 SP#83 SP-190174 0800 3 B eSBA communication schemas related to UDM and UDR discovery and selection 16.0.0 2019-03 SP#83 SP-190172 0940 3 B Use of analytics for SMF selection 16.0.0 2019-03 SP#83 SP-190174 0801 7 B eSBA communication schemas related to SMF discovery and selection 16.0.0 2019-03 SP#83 SP-190174 0802 3 B eSBA communication schemas related to PCF discovery and selection 16.0.0 2019-03 SP#83 SP-190174 0803 5 B eSBA communication schemas related to AUSF discovery and selection 16.0.0 2019-03 SP#83 SP-190174 0804 4 B eSBA communication schemas related to AMF discovery and selection 16.0.0 2019-03 SP#83 SP-190165 0826 2 B Introduction of the MSISDN-less MO SMS Service 16.0.0 2019-03 SP#83 SP-190165 0828 1 B Introduction of the SCEF+NEF 16.0.0 2019-03 SP#83 SP-190172 0831 6 B CR for TS 23.501 based on conclusion of eNA TR 23.791 16.0.0 2019-03 SP#83 SP-190172 0837 3 B Use of NWDAF analytics for decision of MICO mode parameters 16.0.0 2019-03 SP#83 SP-190169 0841 2 B FQDN format of N3IWF in a standalone non-public network 16.0.0 2019-03 SP#83 SP-190168 0843 2 F Update to LCS related definitions 16.0.0 2019-03 SP#83 SP-190238 0844 8 B Network reliability support with Sets 16.0.0 2019-03 SP#83 SP-190199 0850 1 B Enhancement on slice interworking--501 16.0.0 2019-03 SP#83 SP-190162 0859 2 B Adding 5G SRVCC description to 23.501 16.0.0 2019-03 SP#83 SP-190167 0862 7 B UPF Selection influenced by the indication of the identity/identities of 5G AN N3 User Plane capability 16.0.0 2019-03 SP#83 SP-190167 0863 8 B Architecture and reference points for Wireline AN 16.0.0 2019-03 SP#83 SP-190167 0866 8 B Clarification of RM and CM for 5G-RG 16.0.0 2019-03 SP#83 SP-190169 0870 3 B TSC definitions 16.0.0 2019-03 SP#83 SP-190169 0871 4 B TSC Architecture 16.0.0 2019-03 SP#83 SP-190174 0873 8 B eSBA communication schema co-existence 16.0.0 2019-03 SP#83 SP-190170 0878 2 B NEF service for service specific parameter provisioning 16.0.0 2019-03 SP#83 SP-190165 0886 5 B Introduction for solution 14 to key issue 9 16.0.0 2019-03 SP#83 SP-190171 0897 7 B Sol#6 specific updates to 5.6.4.2 16.0.0 2019-03 SP#83 SP-190165 0898 6 B External parameters provisioning to the 5GS 16.0.0 2019-03 SP#83 SP-190172 0899 1 B Use of analytics for user plane function selection 16.0.0 2019-03 SP#83 SP-190172 0900 1 B Use of analytics for UE mobility procedures 16.0.0 2019-03 SP#83 SP-190169 0909 3 B Control of traffic forwarding in 5G-LAN 16.0.0 2019-03 SP#83 SP-190165 0916 1 B User Plane Forwarding with Control Plane CIoT 5GS Optimisation 16.0.0 2019-03 SP#83 SP-190174 0926 2 B Update the support of virtualized deployment with SCP distribution and the NF/NF service instance Set 16.0.0 2019-03 SP#83 SP-190174 0927 1 C Update of NRF functionalities 16.0.0 2019-03 SP#83 SP-190164 0931 2 B UE IP address Allocation by UPF: N4 impacts 16.0.0 2019-03 SP#83 SP-190164 0933 1 B ETSUN - Conclusion alignment 16.0.0 2019-03 SP#83 SP-190167 0934 2 B Support of full Frame Routing feature 16.0.0 2019-03 SP#83 SP-190174 0941 4 B Location information 16.0.0 2019-03 SP#83 SP-190164 0954 2 B Addition of UE IP address Allocation by UPF 16.0.0 2019-03 SP#83 SP-190167 0961 1 B Protocol stack for W-5GAN support 16.0.0 2019-03 SP#83 SP-190167 0962 3 C Session Management of 5G-RG/FN-RG connection to 5GC in the Wireline ANs 16.0.0 2019-03 SP#83 SP-190172 0964 2 B NEF service for NWDAF analytics 16.0.0 2019-03 SP#83 SP-190171 0972 3 B Add description of solution 13 in 23.725 to TS 23.501 16.0.0 2019-03 SP#83 SP-190167 0981 2 B Extension of the QoS model for wireline access 16.0.0 2019-03 SP#83 SP-190172 0983 2 B Update of TS 23.501 for Rel.16 BDT Notification 16.0.0 2019-03 SP#83 SP-190168 0984 2 F Update the description and the reference of LMF service 16.0.0 2019-03 SP#83 SP-190172 0987 3 B CR for TS 23.501 Clarifications NWDAF Discovery and Selection 16.0.0 2019-03 SP#83 SP-190171 0989 2 B Introduction of E2E PDB Division 16.0.0 2019-03 SP#83 SP-190169 1003 2 B QoS parameters mapping between TSN characters and 5G QoS 16.0.0 2019-03 SP#83 SP-190174 1010 3 B Introducing NF Set and NF Service Set 16.0.0 2019-03 SP#83 SP-190175 1022 2 B Introduction of Dedicated Bearer for Ethernet support in EPC 16.0.0 2019-04 - - - - - MCC correction of clause 5.29.3 (to 5.30.3) and position of clause 5.31.7.2. Editorial style and formatting corrections 16.0.1 2019-04 - - - - - MCC correction swapping clause 5.28 to 5.29 and clause 5.29 to 5.28 for readability purposes 16.0.2 2019-06 SP#84 SP-190407 0892 4 B Introduction of inter-UE QoS differentiation for NB-IoT using NB-IoT UE Priority 16.1.0 2019-06 SP#84 SP-190407 1019 3 B Support of EPC interworking for CIoT Monitoring Events 16.1.0 2019-06 SP#84 SP-190428 1028 1 D Proper naming of the reference point between two UPFs for direct routing 16.1.0 2019-06 SP#84 SP-190416 1033 2 B Clarification on MA PDU session 16.1.0 2019-06 SP#84 SP-190416 1034 5 B Determination of access availability 16.1.0 2019-06 SP#84 SP-190419 1035 4 B NRF based P-CSCF discovery 16.1.0 2019-06 SP#84 SP-190425 1037 3 B Introduction of RACS: UCMF services 16.1.0 2019-06 SP#84 SP-190514 1042 6 A Correcting factors to consider for PCF selection 16.1.0 2019-06 SP#84 SP-190399 1044 2 A QoS Notification Control 16.1.0 2019-06 SP#84 SP-190407 1047 3 F MICO mode and Periodic Registration Timer Control 16.1.0 2019-06 SP#84 SP-190422 1050 4 B Transfer of N4 information for local traffic switching from SMF to I-SMF 16.1.0 2019-06 SP#84 SP-190428 1015 2 B Proposed update to 5G LAN terminology 16.1.0 2019-06 SP#84 SP-190428 1052 8 B Further detailing of 5G LAN group management 16.1.0 2019-06 SP#84 SP-190413 1055 2 F Correction of SMF selecting UPF for a particular PDU Session supporting EPS IWK 16.1.0 2019-06 SP#84 SP-190410 1056 2 F Network Slicing and delegated discovery 16.1.0 2019-06 SP#84 SP-190407 1059 1 F UE specific DRX parameter use for NB-IOT 16.1.0 2019-06 SP#84 SP-190399 1062 1 A Congestion control exception for reporting 5GSM Core Network Capability and Always-on PDU Session Requested indication 16.1.0 2019-06 SP#84 SP-190399 1064 1 A Data volume reporting granularity 16.1.0 2019-06 SP#84 SP-190399 1066 - A Removal of restriction of using UE requested PDU modification request for Emergency PDU 16.1.0 2019-06 SP#84 SP-190427 1067 6 F Return to NR from EPS/RAT fallback 16.1.0 2019-06 SP#84 SP-190427 1068 2 F Clarification on PRA 16.1.0 2019-06 SP#84 SP-190412 1070 3 F Clarification to support associating URLLC traffic to redundant PDU sessions 16.1.0 2019-06 SP#84 SP-190425 1071 5 B Introduction of Radio Capabilities Signalling Optimisation feature 16.1.0 2019-06 SP#84 SP-190428 1073 4 B Support of emergency services in public network integrated NPNs 16.1.0 2019-06 SP#84 SP-190407 1075 3 F Clarification on MICO and eDRX during CN node changes 16.1.0 2019-06 SP#84 SP-190416 1078 1 F Correction and clarifications for QoS Flow in MA PDU Session 16.1.0 2019-06 SP#84 SP-190416 1079 2 F Correction related to ATSSS Rule 16.1.0 2019-06 SP#84 SP-190416 1080 2 F Clear ENs about Measurement Assistance Information for ATSSS 16.1.0 2019-06 SP#84 SP-190428 1083 6 B Clarification of Inserting and Removing VLAN tags for 5G-VN 16.1.0 2019-06 SP#84 SP-190410 1091 2 F Update of the NF/NF service discovery result 16.1.0 2019-06 SP#84 SP-190410 1092 3 C Update of NRF function and services 16.1.0 2019-06 SP#84 SP-190410 1093 2 F Update of network reliability support 16.1.0 2019-06 SP#84 SP-190420 1094 1 C Back-off timers handling for scheduled communication 16.1.0 2019-06 SP#84 SP-190428 1095 5 C Addressing Editor's notes on TSN 16.1.0 2019-06 SP#84 SP-190428 1098 1 F Access Control for PLMN Integrated NPN 16.1.0 2019-06 SP#84 SP-190407 1101 9 B Establishing UP connection during CP Data Transfer 16.1.0 2019-06 SP#84 SP-190416 1103 1 F Corrections for SMF, UPF and PCF selection for an MA PDU session 16.1.0 2019-06 SP#84 SP-190416 1104 1 F Corrections for N4 rules for ATSSS 16.1.0 2019-06 SP#84 SP-190407 1109 2 B Service Gap corrections 16.1.0 2019-06 SP#84 SP-190399 1116 2 F Local cache information for ARP proxy 16.1.0 2019-06 SP#84 SP-190416 1118 1 F UE Requested PDU Session Establishment with Network Modification to MA PDU Session 16.1.0 2019-06 SP#84 SP-190428 1119 2 C Granularity of TSN bridge 16.1.0 2019-06 SP#84 SP-190412 1120 1 C Filtering own address for Ethernet PDU Sessions 16.1.0 2019-06 SP#84 SP-190428 1123 3 B TSN QoS mapping and 802.1Qbv parameters 16.1.0 2019-06 SP#84 SP-190415 1128 3 B Access to 5GC from UEs not supporting NAS over non-3GPP access 16.1.0 2019-06 SP#84 SP-190399 1130 1 A Validity of LADN information and LADN discovery/storage in the UE per-PLMN 16.1.0 2019-06 SP#84 SP-190399 1131 3 A Conclusions on applicability of Allowed NSSAI to E-PLMNs 16.1.0 2019-06 SP#84 SP-190399 1132 1 A Correction to the provisioning of the UE Integrity Protection Data Rate capability 16.1.0 2019-06 SP#84 SP-190419 1134 3 B Allowing IMS to use N5 interface to interact with PCF 16.1.0 2019-06 SP#84 SP-190428 1135 3 F Correction regarding legacy UE and non-NPN UE 16.1.0 2019-06 SP#84 SP-190427 1139 3 F AMF selection during inter PLMN mobility 16.1.0 2019-06 SP#84 SP-190412 1142 6 C Update description for E2E PDB division 16.1.0 2019-06 SP#84 SP-190412 1144 2 C Explicit indication of AF response to be expected for runtime coordination with AF 16.1.0 2019-06 SP#84 SP-190407 1149 9 B Roaming support for service exposure 16.1.0 2019-06 SP#84 SP-190399 1152 1 A Corrections for the activation of usage reporting in the UPF 16.1.0 2019-06 SP#84 SP-190399 1159 2 A Clarification on NAS level congestion control 16.1.0 2019-06 SP#84 SP-190399 1161 3 A Correction of UE 5GSM Core Network Capability 16.1.0 2019-06 SP#84 SP-190423 1162 1 B Introduce a new standardized SST value dedicated for V2X services 16.1.0 2019-06 SP#84 SP-190412 1163 1 F Clarification on the CN PDB configured in each NG-RAN node 16.1.0 2019-06 SP#84 SP-190416 1164 2 B Clarification on GBR QoS Flow establishment 16.1.0 2019-06 SP#84 SP-190416 1168 5 C RTT measurements with TCP 16.1.0 2019-06 SP#84 SP-190416 1169 2 F MA PDU QoS Aspects On Link-Specific Multipath and MPTCP Proxy Addresses 16.1.0 2019-06 SP#84 SP-190422 1170 1 F ETSUN Architecture Update 16.1.0 2019-06 SP#84 SP-190410 1171 4 F SCP Function Update 16.1.0 2019-06 SP#84 SP-190412 1173 2 F Redundant PDU session handling 16.1.0 2019-06 SP#84 SP-190421 1174 6 B Introduction of Slice-Specific Authentication and Authorisation 16.1.0 2019-06 SP#84 SP-190399 1176 1 A Association between the GUAMI and AMF instance 16.1.0 2019-06 SP#84 SP-190422 1177 5 B LADN handling in ETSUN scenario 16.1.0 2019-06 SP#84 SP-190422 1179 7 B Traffic offload by UPF controlled by the I-SMF 16.1.0 2019-06 SP#84 SP-190422 1180 1 B UE IP address Allocation by AAA/DHCP 16.1.0 2019-06 SP#84 SP-190428 1183 3 C SNPN deployment scenarios 16.1.0 2019-06 SP#84 SP-190407 1186 8 B Introducing 5GS UP optimization 16.1.0 2019-06 SP#84 SP-190420 1187 1 B Adding NF load information inside NFprofile 16.1.0 2019-06 SP#84 SP-190428 1190 2 C Resolving editor's note on eSBA 16.1.0 2019-06 SP#84 SP-190416 1191 3 F ATSSS support for Unstructured Data 16.1.0 2019-06 SP#84 SP-190428 1194 3 F Removing the EN on the DNN and 5G LAN group mapping 16.1.0 2019-06 SP#84 SP-190428 1198 8 C Resolving the EN on traffic pattern to the TT 16.1.0 2019-06 SP#84 SP-190428 1199 3 F Clarification on the CAG ID and slicing 16.1.0 2019-06 SP#84 SP-190420 1201 2 B CR for adding Naf_EventExposure services 16.1.0 2019-06 SP#84 SP-190428 1202 2 F Clarification on PDU Session management for 5G-LAN multicast 16.1.0 2019-06 SP#84 SP-190409 1205 - B Add new Reference points 16.1.0 2019-06 SP#84 SP-190428 1207 3 F 5G-LAN Service continuity 16.1.0 2019-06 SP#84 SP-190428 1212 1 B Update to Support TSAI for TSC Deterministic QoS 16.1.0 2019-06 SP#84 SP-190428 1214 10 B Introducing support for UE and UPF Residence Time for TSC Deterministic QoS 16.1.0 2019-06 SP#84 SP-190412 1217 4 C 5G URLLC: Optimizing Redundancy 16.1.0 2019-06 SP#84 SP-190428 1218 2 F Standalone NPN - NID Management 16.1.0 2019-06 SP#84 SP-190428 1219 1 F Standalone NPN - EPS Interworking support 16.1.0 2019-06 SP#84 SP-190410 1222 12 B NF Set and NF Service Set - Open items resolution 16.1.0 2019-06 SP#84 SP-190413 1226 - F AMF Failure - Other CP NF Behaviour 16.1.0 2019-06 SP#84 SP-190399 1228 1 A Correction on home-routed roaming architecture for EPC interworking 16.1.0 2019-06 SP#84 SP-190428 1230 4 C Dedicated SMF selection for a 5G LAN group 16.1.0 2019-06 SP#84 SP-190415 1233 4 F Requirements on the Ta interface 16.1.0 2019-06 SP#84 SP-190399 1235 2 A Configuration transfer between NG-RAN and eNodeB 16.1.0 2019-06 SP#84 SP-190399 1237 1 A Cleanup of NAS Congestion Control 16.1.0 2019-06 SP#84 SP-190415 1239 4 B Removal of roaming support from Rel-16 for W-5GAN 16.1.0 2019-06 SP#84 SP-190407 1243 - B Update to NEF description by adding NIDD support 16.1.0 2019-06 SP#84 SP-190399 1249 2 A Correction of SM congestion control override 16.1.0 2019-06 SP#84 SP-190407 1250 2 B Corrections to MICO mode with Active Time 16.1.0 2019-06 SP#84 SP-190407 1251 1 B Subscription Information Influence on PDU Session Rate Control 16.1.0 2019-06 SP#84 SP-190407 1252 2 B Handling of Stored Small Data Rate Control Status at Subsequent PDU Session Establishment 16.1.0 2019-06 SP#84 SP-190407 1256 4 F Corrections to CN assisted RAN parameters tuning 16.1.0 2019-06 SP#84 SP-190413 1257 3 F Corrections to Network Slice Registration 16.1.0 2019-06 SP#84 SP-190420 1258 2 B CR for TS 23.501 Clarifications NWDAF Discovery and Selection 16.1.0 2019-06 SP#84 SP-190407 1262 1 F RRC Inactive information for eDRX 16.1.0 2019-06 SP#84 SP-190427 1263 2 F AMF utilizes NRF to discover NSSF 16.1.0 2019-06 SP#84 SP-190428 1264 3 F QoS differentiation for access to SNPN (PLMN) services via PLMN (SNPN) 16.1.0 2019-06 SP#84 SP-190422 1265 - D Fixing clause number reference 16.1.0 2019-06 SP#84 SP-190427 1266 2 F Correction of description of the IMS voice over PS Session Supported Indication 16.1.0 2019-06 SP#84 SP-190410 1271 13 D SCP: Service-mesh-based deployment options 16.1.0 2019-06 SP#84 SP-190427 1274 2 F Clarification on the UE operates in SR mode in case the NW does not support IWK 16.1.0 2019-06 SP#84 SP-190399 1275 - A Removing unnecessary PDU release during inter-system handover 16.1.0 2019-06 SP#84 SP-190399 1277 1 A Definition of LPP 16.1.0 2019-06 SP#84 SP-190399 1278 2 A UE's usage setting indicating UE capability of supporting voice over E-UTRA 16.1.0 2019-06 SP#84 SP-190399 1279 - A Clarification for interface identifier allocation in IPv6 Multi-homing 16.1.0 2019-06 SP#84 SP-190407 1283 3 F Interaction between MICO mode with active time and eDRX 16.1.0 2019-06 SP#84 SP-190407 1287 - F Update reference to TS 24.250 16.1.0 2019-06 SP#84 SP-190426 1291 1 B Introduction of UDICOM 16.1.0 2019-06 SP#84 SP-190417 1296 2 C Adding Support for Indicating Serialization Format in RDS 16.1.0 2019-06 SP#84 SP-190428 1297 2 F CAG and Network Slice Selection 16.1.0 2019-06 SP#84 SP-190428 1298 3 F Unified Access Control with NPN 16.1.0 2019-06 SP#84 SP-190399 1301 1 A Configuring Transport Level Marking values 16.1.0 2019-06 SP#84 SP-190427 1303 1 F Alignment of Network Slice selection logic 16.1.0 2019-06 SP#84 SP-190413 1305 2 F Enforcement of UP integrity protection 16.1.0 2019-06 SP#84 SP-190429 1306 2 F Ethernet support clarification 16.1.0 2019-06 SP#84 SP-190412 1307 2 F Generalized text for redundant user planes in RAN 16.1.0 2019-06 SP#84 SP-190413 1308 3 C DNN replacement in 5GC 16.1.0 2019-06 SP#84 SP-190410 1312 1 B Extending the significance of the locality parameter 16.1.0 2019-06 SP#84 SP-190399 1315 2 A Correcting AMF selection 16.1.0 2019-06 SP#84 SP-190422 1316 1 C Clarify which parameters are (not) applicable for I-SMF selection. 16.1.0 2019-06 SP#84 SP-190412 1320 3 F Clarification on redundant N3 tunnel solution 16.1.0 2019-06 SP#84 SP-190427 1321 - F Clarification on IWK without N26 16.1.0 2019-06 SP#84 SP-190418 1323 1 C S6b optional for ePDG connected to 5GS 16.1.0 2019-06 SP#84 SP-190429 1328 2 F Data forwarding for 5G-LAN multicast 16.1.0 2019-06 SP#84 SP-190410 1331 3 B Support of Service Context Transfer in TS23.501 16.1.0 2019-06 SP#84 SP-190413 1333 1 B Alignment of IMS Voice Service via EPS Fallback with RAN specifications 16.1.0 2019-06 SP#84 SP-190407 1337 1 B Update to High Latency Overall Description 16.1.0 2019-06 SP#84 SP-190429 1338 2 F NPN: Corrections to handling of Allowed CAG list and CAG-only indication 16.1.0 2019-06 SP#84 SP-190429 1339 2 F NPN: Correction to CAG-only indication 16.1.0 2019-06 SP#84 SP-190429 1341 2 F NPN: Update and enforcement of new Allowed CAG list and CAG-only indication 16.1.0 2019-06 SP#84 SP-190407 1346 2 F CIoT scope clarification 16.1.0 2019-06 SP#84 SP-190404 1350 2 A Location Reporting of secondary cell 16.1.0 2019-06 SP#84 SP-190416 1351 2 B Network request re-activation of user-plane resources 16.1.0 2019-06 SP#84 SP-190416 1352 2 B Clarification on Access Network Performance Measurements 16.1.0 2019-06 SP#84 SP-190399 1358 1 A Emergency Fallback from non-3GPP/ePDG 16.1.0 2019-06 SP#84 SP-190407 1360 1 F NIDD related indications 16.1.0 2019-06 SP#84 SP-190420 1362 2 B Description regarding NEF support of data retrieval from external party 16.1.0 2019-06 SP#84 SP-190427 1366 3 F Subscription Segmentation in PCF and UDR 16.1.0 2019-06 SP#84 SP-190427 1367 2 C Serving PLMN UE-AMBR control 16.1.0 2019-06 SP#84 SP-190415 1372 1 B Access network selection for devices that do not support NAS over WLAN 16.1.0 2019-06 SP#84 SP-190415 1374 - B AMF overload control for trusted non-3GPP access 16.1.0 2019-06 SP#84 SP-190413 1375 2 B 23.501 part of PCF selection for PDU sessions with same DNN and S-NSSAI 16.1.0 2019-06 SP#84 SP-190407 1376 1 B Support for Enhanced Coverage Restriction Control via NEF 16.1.0 2019-06 SP#84 SP-190413 1378 1 F Support for Dynamic Port Management in RDS 16.1.0 2019-06 SP#84 SP-190429 1381 2 B Introduction of TSN Sync soln #28A 16.1.0 2019-06 SP#84 SP-190429 1382 1 F Update to Survival time EN 16.1.0 2019-06 SP#84 SP-190419 1384 3 B Adding UDR NF Group ID association functionality 16.1.0 2019-06 SP#84 SP-190413 1390 2 F Correction of use of PEI/IMEI for non-3GPP only UEs 16.1.0 2019-06 SP#84 SP-190416 1395 1 F Clarifications on Reflective QoS for MPTCP 16.1.0 2019-06 SP#84 SP-190429 1396 1 B NW selection considering RAN sharing for SNPNs 16.1.0 2019-06 SP#84 SP-190421 1404 1 F Target AMF Selection during mobility from EPS to 5GS 16.1.0 2019-06 SP#84 SP-190420 1405 - F Corrections to analytics used by AMF for MICO mode and SMF for UPF selection 16.1.0 2019-06 SP#84 SP-190420 1406 1 B Update NRF descriptions to support AF Available Data Registration as described in TS23.288 16.1.0 2019-06 SP#84 SP-190427 1408 2 F Corrections and alignments for the 5QI characteristics table 16.1.0 2019-06 SP#84 SP-190410 1413 2 B NF Set concept for SMF 16.1.0 2019-06 SP#84 SP-190407 1417 2 B Stateless IPv6 Address Autoconfiguration for Control Plane CIoT 5GS Optimisation 16.1.0 2019-06 SP#84 SP-190407 1418 2 B Introduction of Small Data Rate Control Interworking with APN Rate Control 16.1.0 2019-06 SP#84 SP-190415 1420 2 B Location information for trusted N3GPP 16.1.0 2019-06 SP#84 SP-190429 1423 2 B TSC Burst Arrival Time usage and Clock Reference 16.1.0 2019-06 SP#84 SP-190413 1424 2 F Correction on Location reporting procedure 16.1.0 2019-06 SP#84 SP-190429 1425 3 C Address editor's notes for 5GS Bridge management and QoS mapping 16.1.0 2019-06 SP#84 SP-190429 1426 4 C clarifications on SNPN 16.1.0 2019-06 SP#84 SP-190429 1427 2 C Support for unicast traffic forwarding within a 5G VN group 16.1.0 2019-06 SP#84 SP-190429 1430 2 C implementation of 5G-VN related interfaces 16.1.0 2019-06 SP#84 SP-190407 1431 1 B Support of User Plane Optimisations in Preferred and Supported Network Behaviour 16.1.0 2019-06 SP#84 SP-190429 1432 1 B Ingress timestamp signalling 16.1.0 2019-06 SP#84 SP-190413 1436 - F Align CHF service for offline only charging 16.1.0 2019-06 SP#84 SP-190419 1438 2 B HSS discovery via NRF 16.1.0 2019-06 SP#84 SP-190429 1443 1 B AF influence for traffic forwarding in 5G-VN 16.1.0 2019-06 SP#84 SP-190431 1445 2 B Update of TS23.501 to finalize xBDT feature 16.1.0 2019-06 SP#84 SP-190429 1448 - D Vertical_LAN - Editorial clean up 16.1.0 2019-06 SP#84 SP-190399 1449 1 A Applicability of Allowed NSSAI to PLMNs whose TAIs are in the RA TAI list 16.1.0 2019-06 SP#84 SP-190399 1451 - A Clarification on S-NSSAI for PDU session in Requested NSSAI 16.1.0 2019-09 SP#85 SP-190608 0990 6 B Introduction of QoS Monitoring to assist URLLC Service 16.2.0 2019-09 SP#85 SP-190618 1097 3 F Support of Standalone Non-Public Networks 16.2.0 2019-09 SP#85 SP-190618 1240 5 F Clarification of support of dual radio UE 16.2.0 2019-09 SP#85 SP-190610 1329 3 F IP Address Accessibility for MA PDU Session 16.2.0 2019-09 SP#85 SP-190610 1330 2 F N3/N9 Tunnels for the MA-PDU Session 16.2.0 2019-09 SP#85 SP-190605 1347 6 F Introducing of UP CIoT 5GS Optimisation capability 16.2.0 2019-09 SP#85 SP-190605 1364 1 F NIDD Description Update for Maximum Packet Size 16.2.0 2019-09 SP#85 SP-190618 1371 3 F Clarification for the related CAG identifier 16.2.0 2019-09 SP#85 SP-190618 1379 2 F Support for access to PLMN services via SNPN and SNPN services via PLMN 16.2.0 2019-09 SP#85 SP-190608 1414 3 B QoS monitoring based on GTP-U paths 16.2.0 2019-09 SP#85 SP-190615 1440 8 B Enhancements to QoS Handling for V2X Communication Over Uu Reference Point 16.2.0 2019-09 SP#85 SP-190607 1453 4 F Completion of the PCF Group 16.2.0 2019-09 SP#85 SP-190622 1454 2 F Inter Core Network Roaming 16.2.0 2019-09 SP#85 SP-190609 1455 3 F Align PLMN selection with service requirements 16.2.0 2019-09 SP#85 SP-190605 1457 2 F NAS RAI corrections 16.2.0 2019-09 SP#85 SP-190605 1461 2 F Clarifications to QoS support for NB-IoT 16.2.0 2019-09 SP#85 SP-190617 1463 3 F Correction on support of RACS 16.2.0 2019-09 SP#85 SP-190618 1464 3 C Completing Ethernet port management 16.2.0 2019-09 SP#85 SP-190605 1465 2 F Adding N4 Notification about buffered packets being dropped 16.2.0 2019-09 SP#85 SP-190609 1466 - F PEI for 5G-RG and FN-RG 16.2.0 2019-09 SP#85 SP-190618 1467 1 F Corrections to general 5G LAN description 16.2.0 2019-09 SP#85 SP-190618 1468 3 F 5G LAN user plane corrections 16.2.0 2019-09 SP#85 SP-190610 1469 4 F Awareness of UE PMF port number and MAC address in UPF 16.2.0 2019-09 SP#85 SP-190607 1470 4 F Clarification of the Locality of a NF Instance 16.2.0 2019-09 SP#85 SP-190621 1476 2 F Replacement of VPLMN by serving PLMN where appropriate 16.2.0 2019-09 SP#85 SP-190621 1477 1 F Clarification on the misalignment of service area restriction between UE and Network 16.2.0 2019-09 SP#85 SP-190611 1478 1 F Correction of P-CSCF selection to consider proximity to UPF 16.2.0 2019-09 SP#85 SP-190605 1479 1 F Aligning Terminology referring to the CIoT 5GS Optimisations 16.2.0 2019-09 SP#85 SP-190617 1480 1 F Corrections of PLMN assigned Capability signalling 16.2.0 2019-09 SP#85 SP-190621 1483 1 F Correction of Network Slice selection with NSSF 16.2.0 2019-09 SP#85 SP-190621 1487 3 C DNN replacement in 5GC 16.2.0 2019-09 SP#85 SP-190608 1489 1 F Failure handling for redundancy based on dual connectivity 16.2.0 2019-09 SP#85 SP-190608 1490 1 F Clarification on reordering requirement with GTP-U redundancy 16.2.0 2019-09 SP#85 SP-190601 1494 1 A Discrepancy with TS 33.501 with respect to Secondary Authentication 16.2.0 2019-09 SP#85 SP-190610 1500 2 F Clarification of traffic switching for GBR QoS Flow in MA PDU session 16.2.0 2019-09 SP#85 SP-190618 1501 3 F N19 Tunnel management 16.2.0 2019-09 SP#85 SP-190618 1504 3 C TSN Time Synchronization Traffic Handling 16.2.0 2019-09 SP#85 SP-190618 1507 3 F TSC Assistance Information update 16.2.0 2019-09 SP#85 SP-190605 1509 1 F Handling of CIoT optimisations not supported over NR 16.2.0 2019-09 SP#85 SP-190617 1517 2 C Handling of NB-IOT radio capabilities and RACS in 5GS 16.2.0 2019-09 SP#85 SP-190601 1519 2 A Allowed NSSAI and TAI list from (previous) UE Configuration Update 16.2.0 2019-09 SP#85 SP-190622 1521 1 F Use of the URSP rules when UE attaches to EPS 16.2.0 2019-09 SP#85 SP-190624 1522 1 B Introduction of the IAB support in 5GS 16.2.0 2019-09 SP#85 SP-190621 1540 2 F Clarification on the meaning of Emergency Services Support indicator 16.2.0 2019-09 SP#85 SP-190605 1541 2 F Addition of missing CIoT services 16.2.0 2019-09 SP#85 SP-190606 1543 1 F Addition of missing GMLC and its service 16.2.0 2019-09 SP#85 SP-190614 1544 3 F Mobility event management 16.2.0 2019-09 SP#85 SP-190608 1547 - F Improvement for support of redundant transmission on N3/N9 interfaces 16.2.0 2019-09 SP#85 SP-190621 1548 1 F Clarification on S-NSSAI(s) for PDU session 16.2.0 2019-09 SP#85 SP-190622 1556 2 D Adding Policy Charging and Control related reference points 16.2.0 2019-09 SP#85 SP-190621 1557 2 F Update to NEF related reference points 16.2.0 2019-09 SP#85 SP-190611 1563 1 F NF Group resolution by SCP 16.2.0 2019-09 SP#85 SP-190610 1570 1 F Corrections about default QoS rule 16.2.0 2019-09 SP#85 SP-190610 1571 3 B Interworking for MA PDU Session 16.2.0 2019-09 SP#85 SP-190605 1573 2 F Conditions to use CP or UP CIoT 16.2.0 2019-09 SP#85 SP-190621 1578 1 F Correction of NAS transport for LCS 16.2.0 2019-09 SP#85 SP-190605 1580 2 F Corrections to Control Plane CIoT 5GS Optimisation description 16.2.0 2019-09 SP#85 SP-190605 1581 - F Alignment of the term Early Data Transmission 16.2.0 2019-09 SP#85 SP-190610 1586 3 B Network request re-activation of user-plane resources 16.2.0 2019-09 SP#85 SP-190610 1587 1 F PMF message delivery 16.2.0 2019-09 SP#85 SP-190613 1588 3 F AMF capability of Network Slice-Specific Authentication and Authorization 16.2.0 2019-09 SP#85 SP-190622 1589 3 F Priority of CHF selection 16.2.0 2019-09 SP#85 SP-190605 1596 1 B Clarify short DRX cycle length CM-CONNECTED with RRC inactive for eMTC 16.2.0 2019-09 SP#85 SP-190605 1598 3 F Clarification on NEF discovery by an AF 16.2.0 2019-09 SP#85 SP-190618 1604 - F Exclusive Gating Mechanism 16.2.0 2019-09 SP#85 SP-190611 1607 1 F Update P-CSCF Discovery using NRF 16.2.0 2019-09 SP#85 SP-190618 1608 1 F GUAMI allocation for standalone non-public network 16.2.0 2019-09 SP#85 SP-190607 1622 - F Relation between Group and Set 16.2.0 2019-09 SP#85 SP-190607 1624 3 F Network Function/NF Service Context 16.2.0 2019-09 SP#85 SP-190605 1632 3 F Clarification on strictly periodic timer in relation to MICO mode. 16.2.0 2019-09 SP#85 SP-190610 1636 2 F Mandatory support of ATSSS-LL for PDU Sessions of type Ethernet 16.2.0 2019-09 SP#85 SP-190618 1637 3 F Update of 5G LAN-type service feature description 16.2.0 2019-09 SP#85 SP-190608 1643 2 C Clarifications on URLLC support 16.2.0 2019-09 SP#85 SP-190608 1644 1 F Clarification and correction to AF response 16.2.0 2019-09 SP#85 SP-190610 1646 1 F MA PDU IP Address/Prefix Handling in UPF 16.2.0 2019-09 SP#85 SP-190618 1647 1 F Use of NW instance for N19 interface 16.2.0 2019-09 SP#85 SP-190609 1650 1 F Corrections for devices that do not support 5GC NAS over WLAN access 16.2.0 2019-09 SP#85 SP-190610 1652 - F Correction to protocol stacks for RTT measurements 16.2.0 2019-09 SP#85 SP-190610 1653 3 F Clarification about an MA PDU Session using only MPTCP functionality 16.2.0 2019-09 SP#85 SP-190618 1659 2 C Support of forwarding of broadcast and multicast packets 16.2.0 2019-09 SP#85 SP-190618 1660 2 C Address editor's notes for TSN 16.2.0 2019-09 SP#85 SP-190607 1664 4 F eSBA SMF and PCF selection-option 2 16.2.0 2019-09 SP#85 SP-190605 1665 1 F Clarification on Preferred Network Behaviour for CIoT 5GS Optimisations 16.2.0 2019-09 SP#85 SP-190605 1669 1 F Removal of eDRX support with RRC_INACTIVE for NB-IoT 16.2.0 2019-09 SP#85 SP-190605 1670 2 F UPF Service Area awareness for keeping UL N3 Tunnel available 16.2.0 2019-09 SP#85 SP-190612 1671 3 F Correction on data collection from an AF 16.2.0 2019-09 SP#85 SP-190618 1675 2 C Modification to the QoS parameters mapping for 5GS Bridge configuration 16.2.0 2019-09 SP#85 SP-190612 1677 1 F Updating the stored information in NRF to support BSF discovery 16.2.0 2019-09 SP#85 SP-190622 1678 5 C On the usage of rateRatio, one-step vs two-step sync operation and dedicated QoS Flow 16.2.0 2019-12 SP#86 SP-191068 1363 3 B Identification of LTE-M (eMTC) traffic 16.3.0 2019-12 SP#86 SP-191076 1373 2 F Corrections to Trusted Non-3GPP Access Network selection 16.3.0 2019-12 SP#86 SP-191090 1459 3 F Correcting AMF selection 16.3.0 2019-12 SP#86 SP-191071 1472 2 F Correcting behavior if binding indication is not provided 16.3.0 2019-12 SP#86 SP-191071 1473 4 F Correcting delegated discovery and selection and the use of IDs in binding 16.3.0 2019-12 SP#86 SP-191068 1485 3 F Service Gap Control at IWK 16.3.0 2019-12 SP#86 SP-191068 1486 1 F Serving PLMN rate control parameters in modification procedure 16.3.0 2019-12 SP#86 SP-191071 1527 3 F SMF Set and UPF 16.3.0 2019-12 SP#86 SP-191076 1553 2 F Completing the introduction of TNGF in 23.501 16.3.0 2019-12 SP#86 SP-191088 1564 3 F Correction to deletion of PLMN-assigned UE Radio Capability ID 16.3.0 2019-12 SP#86 SP-191090 1576 2 F Correction of UE Radio Capability Update IE encoding 16.3.0 2019-12 SP#86 SP-191088 1592 10 F Resolution of Editor's Note on UCMF-AMF interaction 16.3.0 2019-12 SP#86 SP-191068 1594 3 F I-NEF in Interworking Scenarios 16.3.0 2019-12 SP#86 SP-191071 1623 2 F NRF use of UDR Group ID Mapping service 16.3.0 2019-12 SP#86 SP-191080 1654 2 F UE related analytics for UPF selection 16.3.0 2019-12 SP#86 SP-191068 1666 8 F Corrections to Small Data Rate Control and Exception Reporting 16.3.0 2019-12 SP#86 SP-191068 1667 4 B Introduction of RRC Connection Re-Establishment for CP 16.3.0 2019-12 SP#86 SP-191071 1679 2 F Clarification on target address in service request message 16.3.0 2019-12 SP#86 SP-191074 1687 1 A Condition for the UE to provide a Requested NSSAI 16.3.0 2019-12 SP#86 SP-191076 1688 - F Network slicing impacts of Wireless and Wireline Convergence 16.3.0 2019-12 SP#86 SP-191068 1689 2 F Support of TAs with heterogeneous support of eDRX 16.3.0 2019-12 SP#86 SP-191068 1690 2 F Control Plane CIoT 5GS Optimisations restriction on NR 16.3.0 2019-12 SP#86 SP-191068 1692 1 F Addition of I-NEF to Network Functions 16.3.0 2019-12 SP#86 SP-191068 1693 1 F Service Exposure in Interworking Scenarios 16.3.0 2019-12 SP#86 SP-191090 1695 2 F Correction to PPI setting control over N4 16.3.0 2019-12 SP#86 SP-191082 1697 - F Interaction between ETSUN and CIoT. 16.3.0 2019-12 SP#86 SP-191082 1698 1 F Clarifications to ETSUN specification 16.3.0 2019-12 SP#86 SP-191077 1702 3 F Clarification on QoS Support for ATSSS 16.3.0 2019-12 SP#86 SP-191090 1703 3 F Clarification on DNN replacement 16.3.0 2019-12 SP#86 SP-191090 1710 4 F Clarification on N6 traffic routing information for Ethernet type PDU Session 16.3.0 2019-12 SP#86 SP-191092 1711 1 F clarification on N6-based traffic forwarding of 5G-VN 16.3.0 2019-12 SP#86 SP-191077 1714 2 F MA PDU Upgrade in modification procedure 16.3.0 2019-12 SP#86 SP-191071 1715 1 F Delegated discovery and selection in SCP for CHF and SMSF 16.3.0 2019-12 SP#86 SP-191073 1716 1 C Update N4 rules for QoS Monitoring 16.3.0 2019-12 SP#86 SP-191088 1717 2 F Clarification on UE capability update 16.3.0 2019-12 SP#86 SP-191068 1721 2 F Removal of ENs for control plane congestion control 16.3.0 2019-12 SP#86 SP-191090 1722 2 F Multicast forwarding for Ethernet type PDU Session 16.3.0 2019-12 SP#86 SP-191081 1723 2 F Alignments to support Network Slice-Specific Authentication and Authorization 16.3.0 2019-12 SP#86 SP-191082 1726 2 F Clarification on IPv6 Router Advertisement message in ETSUN 16.3.0 2019-12 SP#86 SP-191090 1728 1 F SMF selection clarification 16.3.0 2019-12 SP#86 SP-191071 1729 4 F Group ID and Set ID 16.3.0 2019-12 SP#86 SP-191081 1730 1 F AMF redirection at handover from 4G to 5G 16.3.0 2019-12 SP#86 SP-191077 1733 1 F Clarification of Access Availability report via N4 16.3.0 2019-12 SP#86 SP-191090 1734 1 F Clarification of terms in secondary authentication 16.3.0 2019-12 SP#86 SP-191084 1735 1 B Extension of standardized 5QI to QoS characteristics mapping table to accommodate enhanced V2X requirements 16.3.0 2019-12 SP#86 SP-191090 1736 2 F Determination of Emergency Services Fallback support in the AMF 16.3.0 2019-12 SP#86 SP-191080 1737 - F UDM Discovery by Internal Group ID 16.3.0 2019-12 SP#86 SP-191074 1738 3 F UE may provide NSSAI in AS for initial registration 16.3.0 2019-12 SP#86 SP-191090 1739 5 F No impact on IMS voice session by a change of the IMS voice over PS session indicator during fallback 16.3.0 2019-12 SP#86 SP-191090 1740 1 F Clarification of Homogeneous Support of IMS Voice over PS Sessions 16.3.0 2019-12 SP#86 SP-191073 1742 1 F Enhancement of UP path management based on the coordination with AFs 16.3.0 2019-12 SP#86 SP-191090 1743 2 F PCF selection for multiple PDU Sessions to the same DNN and S-NSSAI 16.3.0 2019-12 SP#86 SP-191068 1745 - F Extended NAS timers for CE mode B 16.3.0 2019-12 SP#86 SP-191068 1746 1 F Correcting AMF decision to set CP only indicator 16.3.0 2019-12 SP#86 SP-191092 1747 7 F 5GS Bridge Management 16.3.0 2019-12 SP#86 SP-191092 1750 3 F Completing QoS and TSCAI mapping 16.3.0 2019-12 SP#86 SP-191092 1751 3 F Clarifying N3IWF access to SNPN 16.3.0 2019-12 SP#86 SP-191092 1752 3 F Clarifying CAG handling during RRC resume procedure 16.3.0 2019-12 SP#86 SP-191090 1754 1 F Update to Clause 4.2.7 Reference Points 16.3.0 2019-12 SP#86 SP-191090 1755 3 F Corrections on Session-AMBR setting and enforcement 16.3.0 2019-12 SP#86 SP-191074 1757 1 A Correction on PCF selection and discovery 16.3.0 2019-12 SP#86 SP-191078 1759 - F UDR service for mapping IMS Public Identity to HSS Group ID for HSS selection 16.3.0 2019-12 SP#86 SP-191071 1765 3 F Notification receiver information in a subscription 16.3.0 2019-12 SP#86 SP-191071 1766 3 F Correcting delegated discovery for PCF 16.3.0 2019-12 SP#86 SP-191090 1767 2 F 23.501:PCF provides PCC rule to SMF based on Local routing indication in subscription information 16.3.0 2019-12 SP#86 SP-191073 1768 2 F Delivery of SMF waiting time to AF for session continuity 16.3.0 2019-12 SP#86 SP-191077 1769 3 F Corrections for performance measurements 16.3.0 2019-12 SP#86 SP-191074 1770 2 F Correction on TNLA binding 16.3.0 2019-12 SP#86 SP-191077 1771 3 F General corrections for MA PDU sessions 16.3.0 2019-12 SP#86 SP-191077 1772 2 F Corrections to interworking with EPS for ATSSS 16.3.0 2019-12 SP#86 SP-191077 1773 2 F N4 impacts due to ATSSS 16.3.0 2019-12 SP#86 SP-191077 1774 3 F Corrections to steering functionalities description 16.3.0 2019-12 SP#86 SP-191090 1775 2 F PCF selection for DNN replacement 16.3.0 2019-12 SP#86 SP-191074 1778 2 F Remote Interference Management support 16.3.0 2019-12 SP#86 SP-191084 1785 2 F Corrections to handling of Alternative QoS Profiles 16.3.0 2019-12 SP#86 SP-191080 1787 7 F Consistency on Definitions related to NWDAF 16.3.0 2019-12 SP#86 SP-191068 1792 2 F EDT support for UP CIoT Optimisation 16.3.0 2019-12 SP#86 SP-191092 1797 3 F Support of PLMN managed NIDs 16.3.0 2019-12 SP#86 SP-191092 1798 2 F Support of NG-RAN sharing options for NPN 16.3.0 2019-12 SP#86 SP-191074 1801 2 F TS 23.501: PEI format for non-3GPP devices 16.3.0 2019-12 SP#86 SP-191092 1802 2 F TSN 5QI clarification and static TSC QoS Flow establishment 16.3.0 2019-12 SP#86 SP-191092 1804 3 F 5GS bridge model interpretation 16.3.0 2019-12 SP#86 SP-191092 1806 5 F Revision on MDBV mapping 16.3.0 2019-12 SP#86 SP-191092 1815 2 F clarification on the Qos parameters mapping and TSCAI creation 16.3.0 2019-12 SP#86 SP-191073 1816 - F Clarification on the Standardized or pre-configured 5QI parameters modification 16.3.0 2019-12 SP#86 SP-191068 1817 1 F Expected UE behaviour data contents 16.3.0 2019-12 SP#86 SP-191068 1818 2 F Correction of Small Data Rate Control interworking 16.3.0 2019-12 SP#86 SP-191090 1819 1 F Network selection correction 16.3.0 2019-12 SP#86 SP-191092 1821 3 F Clarification of SMF management of 5G-VN PDU sessions 16.3.0 2019-12 SP#86 SP-191092 1822 3 F Clarification of UPF selection for 5G-VN communication 16.3.0 2019-12 SP#86 SP-191092 1823 1 F Clarification of use of AF influence in 5G-VN 16.3.0 2019-12 SP#86 SP-191088 1828 3 F Misleading RACS architecture pictures 16.3.0 2019-12 SP#86 SP-191088 1829 6 F removing requirement that TAC+SV is used to identify UE model in manufacturer assigned ID 16.3.0 2019-12 SP#86 SP-191086 1833 3 F changing IAB-MT to IAB-UE 16.3.0 2019-12 SP#86 SP-191074 1837 2 F Correction on applicability of slicing to more than 3GPP access 16.3.0 2019-12 SP#86 SP-191074 1839 2 F Incorrect reference to clause in specification 16.3.0 2019-12 SP#86 SP-191090 1840 1 F Alignment with SA5 on Charging for 5G connection and mobility domain 16.3.0 2019-12 SP#86 SP-191082 1842 3 F PDU Session with SSC mode 2/3 16.3.0 2019-12 SP#86 SP-191090 1845 3 C General description and data volume reporting for NR in unlicensed bands 16.3.0 2019-12 SP#86 SP-191090 1847 2 B Access restrictions for primary and secondary RAT 16.3.0 2019-12 SP#86 SP-191090 1849 1 B Introduction of UE specific DRX for NB-IOT 16.3.0 2019-12 SP#86 SP-191074 1853 1 A Correction of QFI value in QER 16.3.0 2019-12 SP#86 SP-191073 1854 5 F Management of GBR QoS Flows at handover 16.3.0 2019-12 SP#86 SP-191092 1857 5 F Updates to the 5G VN broadcast solution 16.3.0 2019-12 SP#86 SP-191090 1859 4 F PDU session anchor terminology clarification 16.3.0 2019-12 SP#86 SP-191074 1860 4 F Remove incorrect reasoning of default MDBV value setting 16.3.0 2019-12 SP#86 SP-191077 1868 5 F ATSSS Link-Specific Multipath IP Address Configuration 16.3.0 2019-12 SP#86 SP-191077 1869 10 F ATSSS Steering of non-MPTCP Traffic 16.3.0 2019-12 SP#86 SP-191077 1870 3 F ATSSS PMF Protocol over UDP 16.3.0 2019-12 SP#86 SP-191077 1875 2 F Interworking with EPS for the MA PDU Session 16.3.0 2019-12 SP#86 SP-191073 1878 2 F 5G URLLC Handling PDU Session Failure 16.3.0 2019-12 SP#86 SP-191092 1879 2 F UPF selection for 5G URLLC PDU Sessions 16.3.0 2019-12 SP#86 SP-191092 1881 3 F UE identifier for SNPN 16.3.0 2019-12 SP#86 SP-191092 1887 2 F N4 Impacts - Bridge Management 16.3.0 2019-12 SP#86 SP-191092 1888 5 F Clarification for TSC QoS Mapping clause 16.3.0 2019-12 SP#86 SP-191092 1889 2 F TSC PDU Session Restrictions 16.3.0 2019-12 SP#86 SP-191092 1890 7 F TSCAI granularity 16.3.0 2019-12 SP#86 SP-191092 1893 3 F UPF functional update for TSC 16.3.0 2019-12 SP#86 SP-191071 1895 - F Clarification on SMF identifier in HR roaming 16.3.0 2019-12 SP#86 SP-191068 1899 2 F Clarifications on CN assistance information sent to the RAN 16.3.0 2019-12 SP#86 SP-191086 1901 1 B Handling of IAB-indication to 5GC 16.3.0 2019-12 SP#86 SP-191086 1902 1 B Handling of OAM traffic for IAB-node 16.3.0 2019-12 SP#86 SP-191086 1903 1 B Support of IAB operation in EN-DC mode 16.3.0 2019-12 SP#86 SP-191086 1905 1 F Mobility support limitation for IAB 16.3.0 2019-12 SP#86 SP-191078 1912 - F Including IMS related interfaces in list of 5G interfaces 16.3.0 2019-12 SP#86 SP-191090 1918 - F Clarification on UE mobility event notification 16.3.0 2019-12 SP#86 SP-191076 1920 1 F Avoid specifying SUPI / SUCI and PEI used for FN RG both in 23.501 and 23.316 16.3.0 2019-12 SP#86 SP-191077 1923 2 F Corrections to ATSSS capabilities of a MA PDU Session 16.3.0 2019-12 SP#86 SP-191077 1924 1 F Applicability of UP Security Policy to a MA PDU Session 16.3.0 2019-12 SP#86 SP-191082 1929 3 F (I)SMF notifications: which SMF events need to be supported by ISMF 16.3.0 2019-12 SP#86 SP-191092 1932 2 F Clarification on the PDU session management for VN 16.3.0 2019-12 SP#86 SP-191074 1934 1 F Correction on SMSF change 16.3.0 2019-12 SP#86 SP-191074 1935 2 F Correction on UE context handling during inter system mobility 16.3.0 2019-12 SP#86 SP-191088 1936 2 F Inclusion of Version Identifier in PLMN assigned ID 16.3.0 2019-12 SP#86 SP-191077 1937 1 F Corrections for link-specific multipath address/prefix and MPTCP proxy IP address 16.3.0 2019-12 SP#86 SP-191074 1940 3 F Selecting SMF that support static IP address 16.3.0 2019-12 SP#86 SP-191090 1941 4 F Number of EBIs 16.3.0 2019-12 SP#86 SP-191071 1942 2 F Notification URI 16.3.0 2019-12 SP#86 SP-191082 1943 2 F I-SMF handling of N4 Information 16.3.0 2019-12 SP#86 SP-191090 1945 - F Correction of implementation of CR #1321 16.3.0 2019-12 SP#86 SP-191074 1949 1 F Clarification on the PCF selection 16.3.0 2019-12 SP#86 SP-191074 1956 - A Removal of wrongly implemented Network Slicing CR #1031 and mirror CR #1131 16.3.0 2019-12 SP#86 SP-191073 1971 - F Correction on support of redundant transmission on N3/N9 interfaces 16.3.0 2019-12 SP#86 SP-191068 1972 - F Clarification on Control Plane Only Indicator 16.3.0 2019-12 SP#86 SP-191073 1973 1 F Correction and clarification to AF influence in URLLC 16.3.0 2019-12 SP#86 SP-191074 1976 2 F ULCL/BP based on the local routing policy 16.3.0 2019-12 SP#86 SP-191081 1979 2 F On NSSAA Services 16.3.0 2019-12 SP#86 SP-191092 1981 5 F Applying Per-Stream Filtering and Policing 16.3.0 2019-12 SP#86 SP-191074 1985 1 A S-NSSAI setting for emergency service 16.3.0 2019-12 SP#86 SP-191074 1986 2 B Solution on support of NAT in 5GS 16.3.0 2019-12 SP#86 SP-191080 1992 1 F Corrections to NWDAF discovery and selection 16.3.0 2019-12 SP#86 SP-191068 1993 - F UE support of CP optimization over NB-IoT 16.3.0 2019-12 SP#86 SP-191071 1994 1 F Correction of CHF discovery to consider eSBA binding principles 16.3.0 2019-12 SP#86 SP-191092 1997 3 F PNI-NPN - Reusing NSSAI for AMF selection when NPN isolation is needed 16.3.0 2019-12 SP#86 SP-191084 2001 - F Correction on the support of V2X in 5GS 16.3.0 2019-12 SP#86 SP-191086 2003 - F Remove protocol stack diagrams for IAB 16.3.0 2019-12 SP#86 SP-191086 2004 1 F Remove Editor's Notes for IAB related clauses 16.3.0 2019-12 SP#86 SP-191081 2005 1 F Correction on pending NSSAA indication to UE 16.3.0 2019-12 SP#86 SP-191082 2006 - F ETSUN: correction for I-SMF trace 16.3.0 2020-03 SP#87E SP-200075 1482 7 F Alignments and corrections to Non-Public Network functionality 16.4.0 2020-03 SP#87E SP-200075 1520 4 F PLMN+CAG information - minimum, maximum storage and survival of power cycle 16.4.0 2020-03 SP#87E SP-200075 1595 2 F 23.501 Supporting for AF providing UE IP address(es) for 5G VN group PDU sessions 16.4.0 2020-03 SP#87E SP-200062 1668 4 F Clarification to MICO mode and Periodic Registration Timer Control 16.4.0 2020-03 SP#87E SP-200062 1691 3 F Alignment with TS 23.502 and clarification on Extended Buffering 16.4.0 2020-03 SP#87E SP-200075 1749 7 F Item#4: Apply StaticFilteringEntry information in 5GS 16.4.0 2020-03 SP#87E SP-200069 1782 4 F Applicability of PS data off to ATSSS and MA PDU sessions 16.4.0 2020-03 SP#87E SP-200078 1783 6 F UE IDLE over N3GPP responding to indication of DL data when access is available 16.4.0 2020-03 SP#87E SP-200075 1799 7 F Support of CAG ID privacy 16.4.0 2020-03 SP#87E SP-200078 1848 14 F Introduction of the Inter PLMN UP functionality in the architecture 16.4.0 2020-03 SP#87E SP-200075 1882 4 F UDM - AUSF Discovery & Selection in an SNPN 16.4.0 2020-03 SP#87E SP-200069 1947 3 F Corrections to general MA PDU session handling 16.4.0 2020-03 SP#87E SP-200075 1951 4 F Clarifying gPTP message forwarding for multiple TSN PDU sessions 16.4.0 2020-03 SP#87E SP-200069 1957 2 F Adding ATSSS functionality into the UPF 16.4.0 2020-03 SP#87E SP-200075 1980 3 F MDBV mapping and configuration for TSC QoS Flow 16.4.0 2020-03 SP#87E SP-200075 2007 1 F Correction on TSCAI: TSN open issue #1 16.4.0 2020-03 SP#87E SP-200075 2009 1 F Correct errors in Port Management information table 16.4.0 2020-03 SP#87E SP-200071 2011 1 F Re-allowing UE for services after the NSSAA revocation 16.4.0 2020-03 SP#87E SP-200078 2015 2 F CN component of the PDB is configured per UL and DL 16.4.0 2020-03 SP#87E SP-200078 2017 1 F Correcting AMF selection 16.4.0 2020-03 SP#87E SP-200075 2019 2 F Procedures for handover between SNPN and PLMN 16.4.0 2020-03 SP#87E SP-200078 2020 3 F MTU size considerations 16.4.0 2020-03 SP#87E SP-200065 2021 4 F Binding for notification reselection corrections 16.4.0 2020-03 SP#87E SP-200065 2022 3 F Correcting delegated discovery for PCF 16.4.0 2020-03 SP#87E SP-200075 2026 1 F Correction of current context and using 5GS bridge to refer to 5GS functions act as TSN bridge 16.4.0 2020-03 SP#87E SP-200068 2027 2 F Support of Wireline access requires both N1 signalling and N2 signalling 16.4.0 2020-03 SP#87E SP-200075 2028 3 F Clarification on the 5G VN usage of IP Multicast mechanisms from TS 23.316 16.4.0 2020-03 SP#87E SP-200075 2029 4 F Usage of Ethernet PDU Session Information to support 5G VN Group point to point Ethernet traffic 16.4.0 2020-03 SP#87E SP-200072 2030 1 F Criteria for I-SMF (and V-SMF) selection and change including also ATSSS cases 16.4.0 2020-03 SP#87E SP-200078 2031 1 F Support of TNAP identifier when the Trusted Access does not correspond to WLAN 16.4.0 2020-03 SP#87E SP-200069 2032 3 F ATSSS capabilities cooperation between the UE and UPF 16.4.0 2020-03 SP#87E SP-200068 2033 4 F Access type and RAT type per Non-3GPP accesses 16.4.0 2020-03 SP#87E SP-200062 2035 - F Service Gap Control handling at UE side during IWK 16.4.0 2020-03 SP#87E SP-200069 2036 2 F Corrections for handling of serving networks not supporting ATSSS 16.4.0 2020-03 SP#87E SP-200078 2038 2 F Requested NSSAI provided at the AS layer 16.4.0 2020-03 SP#87E SP-200071 2040 1 F Clarification on pending NSSAI in Network Slice-Specific Authentication and Authorization 16.4.0 2020-03 SP#87E SP-200075 2042 4 F Item #5 Support of emergency services for Rel-16 UE not supporting CAG in CAG cells 16.4.0 2020-03 SP#87E SP-200069 2044 1 F Clarification the deregistration in single access 16.4.0 2020-03 SP#87E SP-200075 2046 2 F Clarification of N2 based handover considering CAG IDs supported by the target NG-RAN node 16.4.0 2020-03 SP#87E SP-200068 2047 1 F TS23.501 - Correction on User Location Information 16.4.0 2020-03 SP#87E SP-200072 2048 - F Paging Policy Differentiation 16.4.0 2020-03 SP#87E SP-200075 2050 2 F TSN CN PDB 16.4.0 2020-03 SP#87E SP-200069 2051 - F Access availability report configuration in the UPF 16.4.0 2020-03 SP#87E SP-200062 2053 3 B Assistance indication for WUS grouping 16.4.0 2020-03 SP#87E SP-200078 2054 2 F Correction on MDBV and CN PDB 16.4.0 2020-03 SP#87E SP-200078 2056 2 F Default ARP values for dedicated QoS Flows 16.4.0 2020-03 SP#87E SP-200078 2057 1 F Correction of ARP description 16.4.0 2020-03 SP#87E SP-200078 2060 4 F Clarification on the EBI context if target MME does not support EBI extension during 5GS to EPS mobility 16.4.0 2020-03 SP#87E SP-200075 2064 3 F Item#4: Clarification on the PSFP and Qbv for TSC traffic 16.4.0 2020-03 SP#87E SP-200075 2067 1 F Clarifying TSCAI based on TSN clock used by PSFP gate operation 16.4.0 2020-03 SP#87E SP-200075 2069 5 F Clarifying UL configuration issue 16.4.0 2020-03 SP#87E SP-200075 2070 2 F Traffic Forwarding issue at UPF side 16.4.0 2020-03 SP#87E SP-200075 2073 2 F #1_Clarification for supporting 5G VN group communication 16.4.0 2020-03 SP#87E SP-200076 2074 3 F #2_clarification on N6-based traffic forwarding of 5G-VN 16.4.0 2020-03 SP#87E SP-200069 2079 1 F Clarification on multiple PDU Session anchors for a MA PDU Session 16.4.0 2020-03 SP#87E SP-200076 2084 3 F Correction to Emergency services support by SNPN 16.4.0 2020-03 SP#87E SP-200076 2085 4 F Correction to TSN stream aggregation and QoS parameter mapping guidelines 16.4.0 2020-03 SP#87E SP-200078 2087 1 F Clarification on the use of reference points N14 and N26 16.4.0 2020-03 SP#87E SP-200062 2088 1 F NAS signalling of CP Relocation Indication Truncated 5G-S-TMSI Parameters 16.4.0 2020-03 SP#87E SP-200062 2089 3 F Correction for MO Exception Data Rate and its inclusion in charging information 16.4.0 2020-03 SP#87E SP-200076 2097 2 F Correction to Access SNPN via PLMN 16.4.0 2020-03 SP#87E SP-200060 2100 1 A Alignment with SA5 on Charging for SMS over NAS 16.4.0 2020-03 SP#87E SP-200064 2102 1 F NEF service to support location transfer 16.4.0 2020-03 SP#87E SP-200074 2106 2 F UCMF provisioning correction 16.4.0 2020-03 SP#87E SP-200078 2108 3 F Clarification on the CN tunnel info allocation and release 16.4.0 2020-03 SP#87E SP-200078 2109 2 F Clarification on internal group ID usage 16.4.0 2020-03 SP#87E SP-200065 2111 2 F Update of the binding related descriptions 16.4.0 2020-03 SP#87E SP-200074 2116 1 F On UCMF discovery 16.4.0 2020-03 SP#87E SP-200074 2117 - F RACS and NB-IoT corrections 16.4.0 2020-03 SP#87E SP-200067 2122 2 F Correction for the wrongly implemented CR1785r8 16.4.0 2020-03 SP#87E SP-200067 2123 5 F Corrections of Alternative QoS Profiles - proper TS version 16.4.0 2020-03 SP#87E SP-200062 2128 1 F Sending EPS APN rate control information during PDU session establishment 16.4.0 2020-03 SP#87E SP-200078 2132 - F Correction to Reference Points for Non-3GPP Access 16.4.0 2020-03 SP#87E SP-200076 2133 1 F Clarification of TSN stream and traffic class 16.4.0 2020-03 SP#87E SP-200078 2136 1 F Correction to UE configuration update procedure conditions for re-registration 16.4.0 2020-03 SP#87E SP-200076 2137 1 F Selecting network for Emergency services 16.4.0 2020-03 SP#87E SP-200070 2140 1 F Corrections to UE mobility event notification 16.4.0 2020-03 SP#87E SP-200069 2141 - F QoS handling of MA PDU Session for interworking with N26 16.4.0 2020-03 SP#87E SP-200076 2143 1 F Correct the transfer and determination of the bridge delay related parameters 16.4.0 2020-03 SP#87E SP-200062 2147 1 F PDU Session release when Control Plane Only indication becomes not applicable 16.4.0 2020-03 SP#87E SP-200062 2148 1 F Correction on PTW determincation 16.4.0 2020-03 SP#87E SP-200069 2150 - F Correction on MA PDU Session request indication 16.4.0 2020-03 SP#87E SP-200067 2154 1 F Update N4 rules to support QoS Monitoring and ATSSS 16.4.0 2020-03 SP#87E SP-200081 2157 - F Subscription based access restriction for E-UTRA in unlicensed 16.4.0 2020-03 SP#87E SP-200062 2158 1 F Subscription based access restriction for LTE-M 16.4.0 2020-03 SP#87E SP-200070 2159 1 F Clarification on NWDAF information maintained in NRF 16.4.0 2020-03 SP#87E SP-200062 2160 1 F Missing capabilities in 5GMM Capability IE 16.4.0 2020-03 SP#87E SP-200074 2161 - D Editorial updates in RACS clauses 16.4.0 2020-03 SP#87E SP-200062 2163 - D Mega CR on editorial corrections for 5G_CIoT 16.4.0 2020-03 SP#87E SP-200076 2164 1 F Correction to network selection with multiple subscribed SNPNs 16.4.0 2020-03 SP#87E SP-200076 2165 1 F Clarification for Support for multiple TSN working domains 16.4.0 2020-03 SP#87E SP-200072 2169 1 F ETSUN related CR for non-FASMO corrections 16.4.0 2020-03 SP#87E SP-200076 2171 - F Adding reference points in the Architecture to support Time Sensitive Communication 16.4.0 2020-03 SP#87E SP-200076 2172 1 F UPF selection based on traffic classes and VLAN 16.4.0 2020-03 SP#87E SP-200060 2175 1 A UE capability match request during the registration procedure 16.4.0 2020-03 SP#87E SP-200076 2178 - F Replace IEEE802.1Qbv with IEEE802.1Q 16.4.0 2020-03 SP#87E SP-200076 2183 1 F Correction on QoS Flow Binding about TSN 16.4.0 2020-03 SP#87E SP-200068 2186 - F Correction for support of N5CW devices to access 5GC via trusted WLAN access networks 16.4.0 2020-03 SP#87E SP-200065 2190 1 F Endpoint Address correction 16.4.0 2020-03 SP#87E SP-200078 2191 1 F Clarification on PS Data Off for non-3GPP access PDU Session 16.4.0 2020-03 SP#87E SP-200071 2192 1 F Handling of NSSAA during N2 handover procedure 16.4.0 2020-03 SP#87E SP-200076 2194 1 F Clear description of Access to an SNPN 16.4.0 2020-03 SP#87E SP-200078 2195 1 F AMF Management 16.4.0 2020-03 SP#87E SP-200076 2197 1 F Vertical_LAN 5G-VN related CR for non-FASMO corrections 16.4.0 2020-03 SP#87E SP-200076 2198 1 F Vertical_LAN TSN related CR for non-FASMO corrections 16.4.0 2020-03 SP#87E SP-200076 2199 - F Vertical_LAN NPN related CR for non-FASMO corrections 16.4.0 2020-03 SP#87E SP-200078 2201 1 F Correction on area of interest used by SMF 16.4.0 2020-03 SP#87E SP-200076 2202 1 F TSN working domain and aggregation 16.4.0 2020-03 SP#87E SP-200076 2204 1 F Updates for Bridge Delay information reporting and QoS mapping 16.4.0 2020-03 SP#87E SP-200076 2205 - F Incorrect reference to IEEE 1588 Timestamp data type in normative Annex H.2 16.4.0 2020-03 SP#87E SP-200078 2209 1 F Clarification on network instance determination 16.4.0 2020-03 SP#87E SP-200076 2212 1 F UPF selection based on TSN parameters and context correction 16.4.0 2020-03 SP#87E SP-200068 2214 1 F Inclusion of Requested NSSAI in AN Parameters for non-3GPP access 16.4.0 2020-03 SP#87E SP-200068 2216 1 F 5WWC related CR for non-FASMO corrections 16.4.0 2020-03 SP#87E SP-200293 2179 3 F Change of the restriction of enhanced coverage 16.4.0 2020-07 SP#88E SP-200433 2131 2 F Support of ETSUN and ATSSS 16.5.0 2020-07 SP#88E SP-200424 2138 2 F Selection of direct vs indirect communication 16.5.0 2020-07 SP#88E SP-200428 2153 1 F Steering modes for GBR traffic 16.5.0 2020-07 SP#88E SP-200438 2170 2 F QoS container vs. TSCAI input container 16.5.0 2020-07 SP#88E SP-200438 2217 1 F Fix terminology on maximum number of CAGs per cell instead of per NG-RAN node 16.5.0 2020-07 SP#88E SP-200425 2222 1 F Update of QoS monitoring for URLLC based on RAN WG3 decision 16.5.0 2020-07 SP#88E SP-200438 2223 1 F Clarification on the supported and non-supported features and services for SNPN 16.5.0 2020-07 SP#88E SP-200438 2224 1 F SMF to request the UE IP address from the DN-AAA server based on subscription information 16.5.0 2020-07 SP#88E SP-200433 2225 1 F Support of ETSUN within and between PLMN(s) 16.5.0 2020-07 SP#88E SP-200438 2227 1 F TSN QoS information for DL traffic 16.5.0 2020-07 SP#88E SP-200437 2232 - F Common Network Exposure 16.5.0 2020-07 SP#88E SP-200438 2234 1 F Alignment of traffic forwarding information 16.5.0 2020-07 SP#88E SP-200436 2236 1 F Missing the Radio Capability Filtering linkage to the UE Radio Capability ID 16.5.0 2020-07 SP#88E SP-200552 2238 1 F ARP values for additional QoS Flows 16.5.0 2020-07 SP#88E SP-200428 2240 - F Handling of mobility when target does not support ATSSS 16.5.0 2020-07 SP#88E SP-200420 2242 - A UE radio capability retrieval 16.5.0 2020-07 SP#88E SP-200438 2246 1 F QoS parameters mapping: GFBR, ARP 16.5.0 2020-07 SP#88E SP-200438 2247 1 F UPF selection criteria 16.5.0 2020-07 SP#88E SP-200438 2248 - F Missing change in Annex I 16.5.0 2020-07 SP#88E SP-200438 2251 1 F Correction on the derived MDBV 16.5.0 2020-07 SP#88E SP-200436 2254 - F Correction on the interface N58 b/w NEF and AF 16.5.0 2020-07 SP#88E SP-200436 2255 1 F Support of multiple radio capability formats 16.5.0 2020-07 SP#88E SP-200436 2257 1 F Clarification on Version ID 16.5.0 2020-07 SP#88E SP-200428 2258 1 F Corrections to steering modes 16.5.0 2020-07 SP#88E SP-200438 2263 1 F NF selection in SNPN 5GC 16.5.0 2020-07 SP#88E SP-200432 2268 1 F Handling of pending NSSAI 16.5.0 2020-07 SP#88E SP-200424 2269 2 F Enablers for multiple SCPs (23.501) 16.5.0 2020-07 SP#88E SP-200432 2270 1 F Removal of service area for UE registration with empty Allowed NSSAI due to pending NSSAA 16.5.0 2020-07 SP#88E SP-200424 2271 1 F Corrections to Principles for Binding, Selection and Reselection 16.5.0 2020-07 SP#88E SP-200432 2274 1 F Clarification for the NSSAI in NSSAA procedure of roaming scenario 16.5.0 2020-07 SP#88E SP-200428 2276 1 F MA-PDU Session establishment in Non-allowed Area 16.5.0 2020-07 SP#88E SP-200422 2277 1 F Small data rate control enforcement of normal and exception data 16.5.0 2020-07 SP#88E SP-200438 2278 1 F Correcting 5GS TSN bridge delays 16.5.0 2020-07 SP#88E SP-200430 2279 1 F Corrections to HSS Discovery 16.5.0 2020-07 SP#88E SP-200438 2285 - F Annex I Clarification 16.5.0 2020-07 SP#88E SP-200438 2287 1 F Bridge Management Clarification 16.5.0 2020-07 SP#88E SP-200428 2292 1 F Correction on ATSSS rule generation 16.5.0 2020-07 SP#88E SP-200425 2293 1 F Correction of RAN part of packet delay for QoS monitoring 16.5.0 2020-07 SP#88E SP-200420 2299 1 A Incorrect NOTE 14 for 5QI 3 16.5.0 2020-07 SP#88E SP-200422 2302 1 F Corrections to restriction of use of Enhanced Coverage 16.5.0 2020-07 SP#88E SP-200428 2303 1 F Corrections related to UPF support of RTT measurements without PMF 16.5.0 2020-07 SP#88E SP-200438 2305 1 F Correction on RAN sharing for NPN networks 16.5.0 2020-07 SP#88E SP-200427 2308 1 F Correction on RAT type 16.5.0 2020-07 SP#88E SP-200427 2309 - F Correction on wireline access and reference point between N5CW device and TWAP 16.5.0 2020-07 SP#88E SP-200552 2311 1 C Remove restriction for support of eCall over NR 16.5.0 2020-07 SP#88E SP-200433 2315 1 F Pause of Charging 16.5.0 2020-07 SP#88E SP-200438 2319 1 F Alignment on Identifying PDU session in TSN AF 16.5.0 2020-07 SP#88E SP-200438 2321 1 F Clarification on the bridge delay 16.5.0 2020-07 SP#88E SP-200428 2327 - F Correction of reference to mptcp RFC8684 16.5.0 2020-07 SP#88E SP-200438 2334 1 F Clarify the 5GS Bridge ID 16.5.0 2020-07 SP#88E SP-200432 2336 - F Correction on the value of S-NSSAIs for NSSAA 16.5.0 2020-07 SP#88E SP-200551 2338 1 F Correction on description about area of interest 16.5.0 2020-07 SP#88E SP-200551 2339 1 F Reordering DL data during SR procedure 16.5.0 2020-07 SP#88E SP-200438 2340 1 F Correction for TSCAI Calculation 16.5.0 2020-07 SP#88E SP-200551 2341 - F Correction on QoS handling for priority sessions 16.5.0 2020-07 SP#88E SP-200438 2344 1 F Correction of the gPTP domain and the selection of UPF 16.5.0 2020-07 SP#88E SP-200438 2346 1 F Update on 5G VN group subscription data retrieval 16.5.0 2020-07 SP#88E SP-200551 2347 1 F Update on IPUPS functionality 16.5.0 2020-07 SP#88E SP-200438 2348 1 F Support of 5G LAN-type service under ETSUN architecture 16.5.0 2020-07 SP#88E SP-200551 2350 - F Correction on AF influence on traffic routing 16.5.0 2020-07 SP#88E SP-200551 2351 1 F Correction on Control and User Plane Protocol Stacks 16.5.0 2020-07 SP#88E SP-200438 2352 1 F Support of emergency services for Rel-15 UE in CAG cells 16.5.0 2020-07 SP#88E SP-200424 2353 1 F Update of NF profile 16.5.0 2020-07 SP#88E SP-200438 2363 1 F VLAN Information configuration and information exchange 16.5.0 2020-07 SP#88E SP-200433 2365 1 F MA PDU Session not supported in ETSUN case 16.5.0 2020-07 SP#88E SP-200515 2230 2 F Splitting port management information into port- and bridge-specific information 16.5.0 2020-07 SP#88E SP-200438 2135 5 F Updating the UE with new CAG information 16.5.0 2020-07 SP#88E SP-200588 2370 2 F Alignment on Alternative QoS Profile (This CR was noted, corrected to implement CR2730R1 in v16.5.1) 16.5.0 2020-07 SP#88E SP-200420 1732 5 A Reflective QoS 16.5.0 2020-07 SP#88E SP-200422 2243 3 F Service Area Restriction clarification 16.5.0 2020-07 SP#88E SP-200610 2361 3 F PDU Session release when Control Plane Only indication is not available 16.5.0 2020-07 SP#88E SP-200432 2368 1 F PCO support for DNS over (D)TLS (avoiding attacks against DNS traffic) 16.5.0 2020-07 SP#88E SP-200427 2369 1 F Clarification of the Support of the Frame Routing Feature 16.5.0 2020-07 SP#88E SP-200433 2371 1 F URLLC - TSN interworking with ETSUN 16.5.0 2020-07 SP#88E SP-200432 2372 - F Replacing AUSF by NSSAAF to support NSSAA 16.5.0 2020-07 SP#88E SP-200422 2374 - F Removal of I-NEF 16.5.0 2020-07 SP#88E SP-200422 2378 1 F UE specific DRX for NB-IoT RAN support clarification based on LS R2-2004057 16.5.0 2020-07 SP#88E SP-200434 2379 1 F Capability for HPLMN to understand whether or not the NG-RAN node supports Alternative QoS Profiles 16.5.0 2020-07 SP#88E SP-200438 2380 2 F Handling manipulation of CAG by VPLMN -Sol 1 16.5.0 2020-07 SP#88E SP-200435 2382 1 F IAB support in NPN deployment 16.5.0 2020-08 SP#88E SP-200434 2370 1 F Alignment on Alternative QoS Profile (Correction to implementation of CR2730R2 from v16.5.0) 16.5.1 2020-09 SP#89E SP-200688 2266 2 F Human readable name for SNPN 16.6.0 2020-09 SP#89E SP-200685 2387 - F Correction for URLLC GTP-U Path Monitoring 16.6.0 2020-09 SP#89E SP-200687 2390 - F HSS NF profile Update 16.6.0 2020-09 SP#89E SP-200678 2391 1 F HSS Selection Update 16.6.0 2020-09 SP#89E SP-200688 2392 1 F PSFP clarifications including IEEE LS response on TSN support 16.6.0 2020-09 SP#89E SP-200688 2393 1 F Addressing technical comments from IEEE LS response on TSN support 16.6.0 2020-09 SP#89E SP-200688 2394 1 F Addressing wording comments from IEEE LS response on TSN support 16.6.0 2020-09 SP#89E SP-200688 2395 2 F Delay clarifications including IEEE LS input clarifications 16.6.0 2020-09 SP#89E SP-200688 2396 1 F Solving Synchronization issues, addressing IEEE LS response 16.6.0 2020-09 SP#89E SP-200688 2398 1 F Mapping GBR and Averaging Window 16.6.0 2020-09 SP#89E SP-200686 2400 1 C UE user plane integrity protection mandatory at full rate 16.6.0 2020-09 SP#89E SP-200688 2403 1 F Correction to TSN stream identification in PSFP information 16.6.0 2020-09 SP#89E SP-200688 2404 1 F Correction and clarification related to the choice of PDU Session when exchanging BMIC or PMIC between TSN AF and NW-TT 16.6.0 2020-09 SP#89E SP-200688 2405 1 F 5GS BMCA support and PTP port state configuration 16.6.0 2020-09 SP#89E SP-200686 2407 1 F WUS system support for 5GC 16.6.0 2020-09 SP#89E SP-200674 2409 1 F Routing Binding indication without delegated discovery 16.6.0 2020-09 SP#89E SP-200688 2410 1 F Clarify the Announce message handling 16.6.0 2020-09 SP#89E SP-200671 2420 - A Clarification on concurrency of AS rekeying handling and Emergency Fallback procedure for R16 16.6.0 2020-09 SP#89E SP-200688 2421 1 F correction on the bridge model and NW-TT ports 16.6.0 2020-09 SP#89E SP-200673 2424 - F Overview Clarifications for multiple UP resource support for an NB-IoT UE 16.6.0 2020-09 SP#89E SP-200673 2425 - F Overview Clarifications about the CIoT optimisations during mobility to and from non-3GPP access 16.6.0 2020-09 SP#89E SP-200673 2426 - F Overview Clarifications for handling Control Plane CIoT optimisation during interworking between EPS and 5GS 16.6.0 2020-09 SP#89E SP-200673 2427 1 F Drop downlink packets with notification of the discarded downlink packet 16.6.0 2020-09 SP#89E SP-200673 2428 - F Overview of redirecting UE via service reject to align with CT1 16.6.0 2020-09 SP#89E SP-200688 2430 1 F 23.501: Revision on PNI-NPN CAG Configuration Update 16.6.0 2020-09 SP#89E SP-200674 2431 1 F Correction for NF instance set 16.6.0 2020-09 SP#89E SP-200688 2435 - F remove bridge name to align with CT3 16.6.0 2020-09 SP#89E SP-200688 2437 1 F Clarify Ethernet Frames handling for Ethernet PDU session 16.6.0 2020-09 SP#89E SP-200688 2438 1 F dedicated SMF selection clarification 16.6.0 2020-09 SP#89E SP-200688 2439 1 F 5G-VN clarifications 16.6.0 2020-09 SP#89E SP-200688 2440 1 F Clarification on the 5G VN usage of IP Multicast mechanisms 16.6.0 2020-09 SP#89E SP-200686 2442 1 F Support for DTLS 16.6.0 2020-09 SP#89E SP-200673 2443 1 F Extended Connected Timer in mobility messages 16.6.0 2020-09 SP#89E SP-200674 2444 1 F Clarifications on SCP registration and discovery procedures 16.6.0 2020-09 SP#89E SP-200688 2446 1 F Resolution of open items related to IEEE LS 16.6.0 2020-09 SP#89E SP-200674 2447 1 F Clarification on SCP selection to support multi-SCPs 16.6.0 2020-09 SP#89E SP-200688 2449 - F Change the Default QoS Flow to the QoS Flow with the default QoS rule 16.6.0 2020-09 SP#89E SP-200688 2451 1 F Moving NW-TT ports from BMI into BMIC 16.6.0 2020-09 SP#89E SP-200683 2452 1 C New 5QIs for OAM traffic over IAB 16.6.0 2020-09 SP#89E SP-200677 2453 - F RFC for draft-ietf-tcpm-converters 16.6.0 2020-09 SP#89E SP-200688 2455 1 F Clarification of network sharing for NPN 16.6.0 2020-09 SP#89E SP-200802 2383 2 F Signalling of UE Radio Capability ID in Registration procedure 16.6.0 2020-12 SP#90E SP-200950 2228 4 F Correction of Alternative QoS Profile handling 16.7.0 2020-12 SP#90E SP-200946 2389 1 F Handling of AAA-S address in NSSAA 16.7.0 2020-12 SP#90E SP-200951 2408 2 F Indication of redundancy transmission 16.7.0 2020-12 SP#90E SP-200953 2416 1 F TSCAI update during Handover procedure 16.7.0 2020-12 SP#90E SP-200949 2456 1 F Correction on SMF change with eSBA 16.7.0 2020-12 SP#90E SP-200953 2465 1 F Reject UE access to SNPN service via a PLMN to align with CT1 16.7.0 2020-12 SP#90E SP-200953 2466 1 F Clarification on gPTP handling at NW-TT acting as the GM 16.7.0 2020-12 SP#90E SP-200953 2468 1 F 5G-VN clarifications 16.7.0 2020-12 SP#90E SP-200953 2470 - F Correction to inaccurate and misleading NOTE4 in the BMIC table 16.7.0 2020-12 SP#90E SP-200953 2472 - F Clarification of TSN AF role 16.7.0 2020-12 SP#90E SP-200945 2474 1 A Correcting Xn handover at network sharing 16.7.0 2020-12 SP#90E SP-200951 2475 1 F Correction to QoS monitoring for URLLC on GTP-U 16.7.0 2020-12 SP#90E SP-200947 2476 - F Exception data reporting and connected state 16.7.0 2020-12 SP#90E SP-200959 2477 - F V-SMF selection 16.7.0 2020-12 SP#90E SP-200947 2481 - F Correction on Enhanced Coverage Restriction 16.7.0 2020-12 SP#90E SP-200947 2482 - F Event Configuration Synchronization between 4G&5G 16.7.0 2020-12 SP#90E SP-200949 2483 1 F Group Id from AMF to SMF removal when SCP is responsible for reselection 16.7.0 2020-12 SP#90E SP-200959 2485 1 F Continuation of PDU sessions upon mobility to a target PLMN 16.7.0 2020-12 SP#90E SP-200953 2486 1 F Clarification of CAG information 16.7.0 2020-12 SP#90E SP-200958 2487 - F Removal of NSSAA related statements 16.7.0 2020-12 SP#90E SP-200953 2488 1 F Alignment with CT specification on updating the UE with new CAG information 16.7.0 2020-12 SP#90E SP-200959 2490 1 F Correction on AMF discovery and selection 16.7.0 2020-12 SP#90E SP-200959 2499 1 F S-NSSAI handling at the Inter PLMN mobility 16.7.0 2020-12 SP#90E SP-200959 2500 - F Correction on mobility restriction 16.7.0 2020-12 SP#90E SP-200959 2502 1 F Correction of AF use of Internal Group Identifier 16.7.0 2020-12 SP#90E SP-200953 2504 1 F Clarification on UPF report Bridge ID 16.7.0 2020-12 SP#90E SP-200954 2510 - F Clarification on the construction of prioritized list of WLAN access networks for trusted access network selection 16.7.0 2020-12 SP#90E SP-200953 2511 1 F Updates to N4 for NW-TT port number reporting 16.7.0 2020-12 SP#90E SP-200953 2512 1 F TSN QoS determination 16.7.0 2020-12 SP#90E SP-200953 2521 1 F N3IWF selection procedure when accessing SNPN via PLMN 16.7.0 2020-12 SP#90E SP-200959 2523 1 F Mega CR to clean up 16.7.0 2021-03 SP#91E SP-210243 2463 2 F Correction on Ethernet Type PDU session and MAC address association 16.8.0 2021-03 SP#91E SP-210245 2531 1 F Clarification on LADN support for an MA PDU Session 16.8.0 2021-03 SP#91E SP-210242 2532 1 F Correction of packet delay calculation for QoS monitoring 16.8.0 2021-03 SP#91E SP-210081 2534 1 F Correction on the determination of S-NSSAI for interworking 16.8.0 2021-03 SP#91E SP-210055 2535 - F Correction on UE Radio Capability Handling during suspend 16.8.0 2021-03 SP#91E SP-210243 2540 2 F Correction on gap analysis on charging for 5G service based architecture 16.8.0 2021-03 SP#91E SP-210081 2546 1 F Correction of UE radio capability handling 16.8.0 2021-03 SP#91E SP-210243 2555 1 F 5G-EIR Discovery and Selection 16.8.0 2021-03 SP#91E SP-210242 2557 1 F Removal of erroneous RAN requirements 16.8.0 2021-03 SP#91E SP-210081 2559 1 F Correction to Mobility Restrictions and Access Restrictions 16.8.0 2021-03 SP#91E SP-210054 2569 1 F Support for IMS emergency from CAG non-supporting UE 16.8.0 2021-03 SP#91E SP-210080 2570 1 F Handling of UTRAN UE radio capabilities 16.8.0 2021-03 SP#91E SP-210244 2589 - F Correction on reference to BBF 16.8.0 2021-03 SP#91E SP-210243 2600 1 F IMS voice over PS Session Supported Indication taking into account UE S1 mode status 16.8.0 2021-03 SP#91E SP-210054 2603 1 F clarification on the determination of the egress port for DL traffic 16.8.0 2021-03 SP#91E SP-210054 2604 - F Correction for reporting of 5GS Bridge information 16.8.0 2021-03 SP#91E SP-210054 2605 - F Clarification for the stream filter instance 16.8.0 2021-03 SP#91E SP-210081 2622 1 F S-NSSAI for emergency services 16.8.0 2021-03 SP#91E SP-210081 2623 1 F Inter PLMN mobility for emergency services 16.8.0 2021-03 SP#91E SP-210081 2632 1 F NGAP UE-TNLA-binding update 16.8.0 2021-03 SP#91E SP-210081 2636 1 F AMF reallocation during EPS to 5GS handover using N26 16.8.0 2021-03 SP#91E SP-210055 2641 - F Clarification on support of QoS for Control Plane CIoT 5GS Optimisation 16.8.0 2021-03 SP#91E SP-210242 2655 1 F Correction on QoS monitoring for URLLC 16.8.0 2021-03 SP#91E SP-210055 2657 1 F Downlink data report by UPF 16.8.0 2021-03 SP#91E SP-210081 2664 - F Provide recommended cells for paging information in NGAP UE CONTEXT RESUME REQUEST message 16.8.0 2021-03 SP#91E SP-210078 2665 - F Remove the remaining editor's note for IAB descriptions 16.8.0 2021-03 SP#91E SP-210077 2683 1 F Alternative QoS Profiles and Handover to Congested Cells 16.8.0 2021-03 SP#91E SP-210067 2457 1 B Introduction of AKMA into the reference architecture 17.0.0 2021-03 SP#91E SP-210088 2525 1 B Support of different slices over different Non 3GPP access 17.0.0 2021-03 SP#91E SP-210068 2527 1 B MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC 17.0.0 2021-03 SP#91E SP-210072 2530 1 B Enchantments for supporting Supported Analytics Delay mechanism 17.0.0 2021-03 SP#91E SP-210085 2536 1 B Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service 17.0.0 2021-03 SP#91E SP-210065 2537 - C Selection of CN node by NG-RAN node providing satellite access across multiple countries 17.0.0 2021-03 SP#91E SP-210065 2538 1 C Identification and mobility restrictions for satellite access 17.0.0 2021-03 SP#91E SP-210084 2542 1 B KI#2-1: Capturing the FS_IIoT conclusions on static filtering entries 17.0.0 2021-03 SP#91E SP-210088 2544 1 C IP index from UDM 17.0.0 2021-03 SP#91E SP-210084 2549 1 C KI#1-4: Control of PTP functionality in DS-TT and NW-TT 17.0.0 2021-03 SP#91E SP-210074 2550 1 C SNPN selection for access to SNPNs using credentials from an entity separate from the SNPN 17.0.0 2021-03 SP#91E SP-210074 2551 1 D Informative guideline on how to keep the UE in CM-CONNECTED state in overlay network using existing release 16 mechanisms. 17.0.0 2021-03 SP#91E SP-210088 2560 1 B 5G system architecture updates to support Dynamically Changing Policies in the 5GC 17.0.0 2021-03 SP#91E SP-210088 2561 - B DCAMP related update of BSF services (23.501) 17.0.0 2021-03 SP#91E SP-210074 2563 1 B Informative guideline on supporting session/service continuity between SNPN and PLMN when using N3IWF 17.0.0 2021-03 SP#91E SP-210072 2567 1 B Network Slice restriction based on NWDAF analytics 17.0.0 2021-03 SP#91E SP-210087 2571 1 C New SST for High-Performance Machine-Type Communications (HMTC) 17.0.0 2021-03 SP#91E SP-210084 2573 1 B Introduction of the architectures for Time Sensing Communication other than TSN. 17.0.0 2021-03 SP#91E SP-210086 2574 1 B Introduction of Paging Cause feature 17.0.0 2021-03 SP#91E SP-210072 2575 1 B NWDAF discovery and selection 17.0.0 2021-03 SP#91E SP-210072 2576 1 B DCCF Discovery 17.0.0 2021-03 SP#91E SP-210072 2577 1 B NWDAF Discovery 17.0.0 2021-03 SP#91E SP-210072 2581 1 B Adding the usage of Redundant Transmission Experience analytics for URLLC service 17.0.0 2021-03 SP#91E SP-210072 2582 1 B Adding the usage of extended UE Mobility analytics for LADN service 17.0.0 2021-03 SP#91E SP-210068 2583 1 B PMF enhancements to support per QoS Flow measurements 17.0.0 2021-03 SP#91E SP-210072 2584 1 B Extensions of NWDAF services 17.0.0 2021-03 SP#91E SP-210072 2585 1 B NWDAF discovery and selection based on provided ML models 17.0.0 2021-03 SP#91E SP-210072 2586 1 B UP path selection enhancement based on analytics info provided by NWDAF 17.0.0 2021-03 SP#91E SP-210068 2587 1 B Packet Loss Rate measurements 17.0.0 2021-03 SP#91E SP-210068 2590 1 B Applying thresholds to Load-Balancing steering mode in ATSSS 17.0.0 2021-03 SP#91E SP-210064 2596 1 B AF Services for 5G ProSe 17.0.0 2021-03 SP#91E SP-210084 2606 1 B KI#2 Supporting UE-UE TSC 17.0.0 2021-03 SP#91E SP-210074 2611 1 B SNPN support AAA Server for primary authentication and authorization 17.0.0 2021-03 SP#91E SP-210072 2614 1 B NWDAF discovery and selection for model sharing 17.0.0 2021-03 SP#91E SP-210072 2615 1 B Triggers for network analytics 17.0.0 2021-03 SP#91E SP-210084 2618 1 B KI#2 BMIC and PMIC for TSC without IEEE TSN network 17.0.0 2021-03 SP#91E SP-210084 2619 1 B KI#3A - TSC Assistance container determined by NEF 17.0.0 2021-03 SP#91E SP-210084 2620 1 B KI#1-3, UL Sync including New QoS Flow establishment for the gPTP 17.0.0 2021-03 SP#91E SP-210084 2621 1 C KI#3 Updating AF functional description 17.0.0 2021-03 SP#91E SP-210087 2624 1 D 23.501 Inclusive language review 17.0.0 2021-03 SP#91E SP-210074 2625 1 B SNPN with separate entity hosting subscription 17.0.0 2021-03 SP#91E SP-210084 2627 1 C Generalizing TSC clause 5.27 17.0.0 2021-03 SP#91E SP-210084 2628 1 C TSCAI applicability 17.0.0 2021-03 SP#91E SP-210084 2629 1 B KI#3B-1: Exposure of Time synchronization as a service 17.0.0 2021-03 SP#91E SP-210069 2634 1 B KI #1-1, I-SMF selection 17.0.0 2021-03 SP#91E SP-210064 2637 1 B 5G Architecture reference model for ProSe 17.0.0 2021-03 SP#91E SP-210072 2642 1 B Architectural changes to increasing efficiency of data collection 17.0.0 2021-03 SP#91E SP-210088 2644 1 B Selecting the same PCF for AMF and SMF 17.0.0 2021-03 SP#91E SP-210069 2646 1 B EC KI2 Target PSA buffering 17.0.0 2021-03 SP#91E SP-210074 2648 1 C Support for normal IMS voice over SNPN 17.0.0 2021-03 SP#91E SP-210065 2651 1 C 5QIs for satellite access 17.0.0 2021-03 SP#91E SP-210089 2653 1 B Service Assistance Information for 3GPP Advanced Interactive Service 17.0.0 2021-03 SP#91E SP-210068 2654 1 B Introduction of steering mode indicator 17.0.0 2021-03 SP#91E SP-210069 2656 1 B Adding some parameters for local NEF selection 17.0.0 2021-03 SP#91E SP-210072 2659 1 B Principle for logical decomposition of NWDAF 17.0.0 2021-03 SP#91E SP-210088 2662 1 B Update to N3IWF selection for N3SLICE 17.0.0 2021-03 SP#91E SP-210084 2668 1 B Support for PTP in time synchronization service and BMCA 17.0.0 2021-03 SP#91E SP-210072 2670 1 B NWDAF new abbreviation 17.0.0 2021-03 SP#91E SP-210069 2672 1 B AF Influence enhancement for EAS IP replacement 17.0.0 2021-03 SP#91E SP-210064 2673 - B Add general 5G ProSe support to 5GS 17.0.0 2021-03 SP#91E SP-210065 2674 1 C Detection of satellite backhaul based on configuration information 17.0.0 2021-03 SP#91E SP-210072 2677 1 C NWDAF discovery and selection for KI#2 NWDAF Reselection 17.0.0 2021-03 SP#91E SP-210064 2678 - B Introducing 5G DDNMF services for ProSe support 17.0.0 2021-03 SP#91E SP-210083 2679 1 B TS23.501 KI#1 Network Slice Admission Control Function (NSACF) definition 17.0.0 2021-03 SP#91E SP-210074 2684 1 B General introduction of Enhancements to Support SNPN along with credentials owned by an entity separate from the SNPN 17.0.0 2021-03 SP#91E SP-210271 0254 3 B Network selection for NR satellite access 17.0.0 2021-06 SP#92E SP-210323 2553 5 B Function Description for Multi-SIM devices 17.1.0 2021-06 SP#92E SP-210353 2562 7 B UE onboarding 17.1.0 2021-06 SP#92E SP-210359 2635 2 B KI #1-1, Update for supporting UL time sync with gPTP message 17.1.0 2021-06 SP#92E SP-210345 2647 2 B PMF extensions for sending UE-assistance data to UPF 17.1.0 2021-06 SP#92E SP-210354 2649 3 C Support for IMS emergency services over SNPN 17.1.0 2021-06 SP#92E SP-210355 2680 3 B TS23.501 KI#2 Network Slice Admission Control Function (NSACF) definition 17.1.0 2021-06 SP#92E SP-210344 2689 2 B 5MBS architecture 17.1.0 2021-06 SP#92E SP-210359 2690 3 B Support for IEEE 1588 Boundary Clocks in time synchronization service 17.1.0 2021-06 SP#92E SP-210346 2691 1 B Support for L2TP on N6 17.1.0 2021-06 SP#92E SP-210342 2693 1 C UE location verification for NR satellite access 17.1.0 2021-06 SP#92E SP-210344 2696 4 B N4 extensions for 5MBS 17.1.0 2021-06 SP#92E SP-210345 2697 1 C Handling of Ethernet PDU Session type for MA PDU Session with a 3GPP EPC leg 17.1.0 2021-06 SP#92E SP-210337 2701 2 B New 5QI values to support Advance Interactive Services (AIS) in 5G 17.1.0 2021-06 SP#92E SP-210351 2702 2 B Discover NWDAF for UE related Analytics using UDM 17.1.0 2021-06 SP#92E SP-210351 2705 1 B CR to update NWDAF discovery and selection for MTLF 17.1.0 2021-06 SP#92E SP-210355 2706 3 B Support for UE-Slice-MBR 17.1.0 2021-06 SP#92E SP-210347 2707 1 B EASDF discovery and selection and update of edge computing description 17.1.0 2021-06 SP#92E SP-210351 2708 1 B Adding the usage of Session Management Congestion Control Experience analytics 17.1.0 2021-06 SP#92E SP-210353 2709 1 B Enabling restricted PDU Session for remote provisioning of UE via User Plane 17.1.0 2021-06 SP#92E SP-210572 2714 4 B Remote provisioning of credentials for NSSAA or secondary authentication/authorisation 17.1.0 2021-06 SP#92E SP-210353 2717 1 B Network access control by Credential Holder 17.1.0 2021-06 SP#92E SP-210353 2718 4 B KI#2 T2: Informative guideline for mapping QoS parameters and DSCP marking 17.1.0 2021-06 SP#92E SP-210355 2719 2 B Support of 5GC assisted cell selection to access network slice 17.1.0 2021-06 SP#92E SP-210345 2720 1 B Decision to apply measurements per QoS Flow 17.1.0 2021-06 SP#92E SP-210345 2721 5 B Send PMF messages to a target QoS Flow 17.1.0 2021-06 SP#92E SP-210330 2723 - A Correction to the N3IWF selection procedure 17.1.0 2021-06 SP#92E SP-210355 2727 2 B NSACF functional descriptions 17.1.0 2021-06 SP#92E SP-210355 2728 4 B Updates of NSACF discovery and selection 17.1.0 2021-06 SP#92E SP-210355 2729 1 B NSAC support in roaming 17.1.0 2021-06 SP#92E SP-210363 2736 4 B Clarification on UE provides PDU Session Pair ID based on URSP rules 17.1.0 2021-06 SP#92E SP-210337 2740 2 B New standardized 5QI values for Advanced Interactive Services 17.1.0 2021-06 SP#92E SP-210345 2743 3 B Introduction of UE-assistance operation 17.1.0 2021-06 SP#92E SP-210345 2744 1 B Thresholds for Priority-based mode 17.1.0 2021-06 SP#92E SP-210345 2746 3 B QoS Flow recognition for per QoS Flow measurements 17.1.0 2021-06 SP#92E SP-210353 2755 3 B De-registration for onboarding registered UE 17.1.0 2021-06 SP#92E SP-210347 2757 4 B AF Influence enhancement for EAS IP replacement 17.1.0 2021-06 SP#92E SP-210351 2758 1 B Updating AMF exposed events in TS 23.501. 17.1.0 2021-06 SP#92E SP-210351 2759 1 B Alignment of NWDAF discovery of data exposure capability in TS 23.501. 17.1.0 2021-06 SP#92E SP-210351 2760 1 F Clarify the Supported Analytics Delay 17.1.0 2021-06 SP#92E SP-210351 2761 4 B Update the NWDAF profile for ML Model 17.1.0 2021-06 SP#92E SP-210347 2762 1 B SMF function update to support Edge computing enhancement 17.1.0 2021-06 SP#92E SP-210347 2763 1 B Update of Edge Computing 17.1.0 2021-06 SP#92E SP-210347 2765 1 B Adding EASDF services 17.1.0 2021-06 SP#92E SP-210359 2768 1 B Update for support of TSC other than TSN 17.1.0 2021-06 SP#92E SP-210359 2769 2 B Correction for Survival Time 17.1.0 2021-06 SP#92E SP-210359 2773 3 B Update for PTP in time synchronization service and BMCA 17.1.0 2021-06 SP#92E SP-210342 2781 1 B Support of new RATs in 5GS integrating satellite access 17.1.0 2021-06 SP#92E SP-210363 2783 2 F (Mirror)Correct the NOTE for N6 17.1.0 2021-06 SP#92E SP-210355 2789 5 B Roaming support for NSAC 17.1.0 2021-06 SP#92E SP-210363 2790 1 B Support GERAN/UTRAN access in SMF+PGW-C 17.1.0 2021-06 SP#92E SP-210359 2791 1 B KI#3B, Resolving EN for Future PDU Session 17.1.0 2021-06 SP#92E SP-210351 2795 1 C Add a use case for network slice load analytics 17.1.0 2021-06 SP#92E SP-210353 2799 1 B Homogeneously support SNPN connectivity for UEs with credentials owned by Credentials Holder 17.1.0 2021-06 SP#92E SP-210354 2801 2 D Correction to UE identifier sent to AMF by UE 17.1.0 2021-06 SP#92E SP-210353 2802 1 B User Plane Remote Provisioning of UEs if PLMN as ON 17.1.0 2021-06 SP#92E SP-210347 2804 3 B Edge relocation considering user plane lantecy requirement 17.1.0 2021-06 SP#92E SP-210351 2805 1 C Use of TAI(s) for slice restriction based on analytics 17.1.0 2021-06 SP#92E SP-210337 2806 1 F Packet size for PDB 17.1.0 2021-06 SP#92E SP-210351 2807 - F Corrections for ADRF services 17.1.0 2021-06 SP#92E SP-210351 2808 - F Reference to DCCF and MFAF Services description clause 17.1.0 2021-06 SP#92E SP-210337 2809 1 F TSC Assistance Container Determination by PCF 17.1.0 2021-06 SP#92E SP-210345 2811 2 C Introducing threshold conditions for priority-based steering mode in TS 23.501 17.1.0 2021-06 SP#92E SP-210355 2813 4 B Introduction of support of NG.116 attribute Simultaneous Use of a Network Slice 17.1.0 2021-06 SP#92E SP-210341 2814 3 F The impact of UE N1 mode change in EPS 17.1.0 2021-06 SP#92E SP-210353 2815 3 B KI#1 - T5, Enable mobility between networks 17.1.0 2021-06 SP#92E SP-210359 2817 1 B Terminology on the TSC MIC and Bridge ID 17.1.0 2021-06 SP#92E SP-210359 2820 - B Fix the description on the ethernet port 17.1.0 2021-06 SP#92E SP-210355 2822 4 B Introduction of support of GSMA NG.116 attributes Maximum DL/UL throughput per slice/UE 17.1.0 2021-06 SP#92E SP-210353 2826 1 B Mobility support between SNPNs and between SNPN and PLMN 17.1.0 2021-06 SP#92E SP-210353 2832 1 B UE configuration for remote provisioning 17.1.0 2021-06 SP#92E SP-210359 2833 2 B Introduction of architecture for AF requested support of Time Sensitive Communication and Time Synchronization 17.1.0 2021-06 SP#92E SP-210355 2837 3 B Support of Emergency and Priority Services in Network Slice Admission Control 17.1.0 2021-06 SP#92E SP-210355 2838 2 B TS23.501 KI#4 NSACF event notification definition 17.1.0 2021-06 SP#92E SP-210345 2840 1 F Packet Loss Rate Measurements 17.1.0 2021-06 SP#92E SP-210363 2848 1 F FQDNs for N3IWF selection for emergency services 17.1.0 2021-06 SP#92E SP-210347 2856 3 B Newly added parameters for Local NEF discovery 17.1.0 2021-06 SP#92E SP-210341 2858 1 F Consistent handling of NF documentation 17.1.0 2021-06 SP#92E SP-210340 2861 1 B ProSe related functional description 17.1.0 2021-06 SP#92E SP-210347 2862 - B EASDF functional description 17.1.0 2021-06 SP#92E SP-210330 2865 1 A UE radio capability clarification 17.1.0 2021-06 SP#92E SP-210358 2870 1 B UAV support feature inclusion 17.1.0 2021-06 SP#92E SP-210341 2874 1 F Correction to the reference document for charging related reference points 17.1.0 2021-06 SP#92E SP-210344 2880 1 B PCF impacts of 5MBS 17.1.0 2021-06 SP#92E SP-210351 2881 1 B KI#8 - AF discovery and selection 17.1.0 2021-06 SP#92E SP-210345 2886 1 B Partial ATSSS rule update by using ATSSS rule ID 17.1.0 2021-06 SP#92E SP-210330 2888 1 A Subscription data updates for EPS/5GS interworking 17.1.0 2021-06 SP#92E SP-210329 2889 - A Updates on PCC rule triggered GTP-U path monitoring 17.1.0 2021-06 SP#92E SP-210354 2892 1 F SNPN UE configuration and subscription aspects 17.1.0 2021-06 SP#92E SP-210353 2893 1 B SNPN - SNPN Mobility - AMF selection impacts 17.1.0 2021-06 SP#92E SP-210354 2894 1 F SNPN GIN Encoding 17.1.0 2021-06 SP#92E SP-210359 2896 1 C Exposure of Time synchronization as a service - description 17.1.0 2021-06 SP#92E SP-210347 2899 1 B N4 interface enhancement for local notification 17.1.0 2021-06 SP#92E SP-210347 2900 1 B UPF function update to support network information exposure 17.1.0 2021-06 SP#92E SP-210354 2902 1 F Simultaneous data service from PNI-NPN and PLMN 17.1.0 2021-06 SP#92E SP-210354 2903 1 F IMS voice over overlay network 17.1.0 2021-06 SP#92E SP-210359 2904 1 F KI#3A Support QoS mapping based on priority for TSC exposure 17.1.0 2021-06 SP#92E SP-210359 2905 1 F Clarification on support of PTP GM function in TT 17.1.0 2021-06 SP#92E SP-210359 2908 1 F Resolving EN for Hold and Forward mechanism 17.1.0 2021-06 SP#92E SP-210355 2909 1 B Support multiple NSACFs for one S-NSSAI during UE mobility 17.1.0 2021-06 SP#92E SP-210340 2910 1 B Update of reference points for 5G ProSe 17.1.0 2021-06 SP#92E SP-210359 2911 1 B KI#3B, Temporal Validity Condition Description 17.1.0 2021-06 SP#92E SP-210347 2913 1 B Updates to AF requests to influence traffic routing 17.1.0 2021-06 SP#92E SP-210347 2914 - F Update on I-SMF selection per DNAI 17.1.0 2021-06 SP#92E SP-210353 2918 1 B KI#2 T1: Informative guideline for QoS Notification between overlay network and underlay network 17.1.0 2021-06 SP#92E SP-210545 2923 2 F Allowed NSSAI when NSSAA fails 17.1.0 2021-06 SP#92E SP-210355 2924 1 B Network Slice Admission Control in EPC 17.1.0 2021-06 SP#92E SP-210354 2926 1 C Interaction between AUSF and AAA Server 17.1.0 2021-06 SP#92E SP-210362 2927 1 B Introduction of MUSIM capability exchange 17.1.0 2021-06 SP#92E SP-210330 2931 1 A Support for UPIP for other than NR 17.1.0 2021-06 SP#92E SP-210347 2934 1 F Update on uplink traffic buffering 17.1.0 2021-06 SP#92E SP-210347 2935 1 F AF Influence enhancement for EAS Rediscovery at Edge Relocation 17.1.0 2021-06 SP#92E SP-210355 2937 1 B NSAC with consideration of access type 17.1.0 2021-06 SP#92E SP-210351 2938 1 C NWDAF assisted DNAI and UPF selection at SMF 17.1.0 2021-06 SP#92E SP-210354 2939 1 F Correction to scenarios of external authentication 17.1.0 2021-06 SP#92E SP-210353 2940 1 B Clarification on NID 17.1.0 2021-06 SP#92E SP-210341 2945 1 F Clarification on the number of Subscribed S-NSSAIs 17.1.0 2021-06 SP#92E SP-210359 2946 - C Definition of the UE-DS-TT residence time 17.1.0 2021-06 SP#92E SP-210327 2947 1 A NIDD configuration correction 17.1.0 2021-06 SP#92E SP-210342 2948 1 C Removal of UPF indication of backhaul QoS to SMF 17.1.0 2021-06 SP#92E SP-210353 2952 1 B HRNN in manual network selection for SNPNs 17.1.0 2021-06 SP#92E SP-210341 2953 1 F Clarification on the Standardized SST values 17.1.0 2021-06 SP#92E SP-210353 2955 1 B AMF selection to support UE onboarding SNPN 17.1.0 2021-06 SP#92E SP-210359 2959 - F Grandmaster candidate enabled management information per PTP instance 17.1.0 2021-06 SP#92E SP-210359 2960 1 C Time Synchronization service exposure 17.1.0 2021-06 SP#92E SP-210371 2962 2 F Clarification of applicability of port/bridge management information 17.1.0 2021-06 SP#92E SP-210336 2963 1 A Clarification for Visited Country FQDN DNS query for SNPNs with locally assigned NIDs 17.1.0 2021-06 SP#92E SP-210354 2965 1 C AUSF selection for an Onboarding UE 17.1.0 2021-06 SP#92E SP-210353 2969 1 B Definition of SNPN-related terms 17.1.0 2021-06 SP#92E SP-210341 2970 1 B 4G <-> 5GS mobility corrections to cope with areas of GERAN/UTRAN-only coverage 17.1.0 2021-06 SP#92E SP-210361 2971 1 B Additional authorization functionality in support of MPS for Data Transport Service 17.1.0 2021-06 SP#92E SP-210346 2973 1 B L2TP information provision 17.1.0 2021-06 SP#92E SP-210359 2977 1 B Clarification on TSCAI for the non TSC service 17.1.0 2021-06 SP#92E SP-210330 2982 1 A AMF to consider S1 mode capability into account when setting EMF and EMC 17.1.0 2021-06 SP#92E SP-210335 2984 1 A Correction to trigger for UE Radio Capability Update procedure 17.1.0 2021-06 SP#92E SP-210331 2990 - A Correction on non-3GPP access type 17.1.0 2021-06 SP#92E SP-210331 2991 1 F Adding PDU session limitation and protocol stacks for trusted WLAN access for N5CW device 17.1.0 2021-06 SP#92E SP-210354 2992 - F UE configuration for remote provisioning 17.1.0 2021-06 SP#92E - - - - MCC Correction to move 5.15.11.14 to 5.15.11.5 17.1.1 2021-09 SP#93E SP-210916 2748 3 C Support of Mobility Registration Update for 5G Satellite Access 17.2.0 2021-09 SP#93E SP-210923 2919 2 B IMSI based SUPI support when access an SNPN using credentials owned by CH 17.2.0 2021-09 SP#93E SP-210923 2921 2 B UE onboarding architecture 17.2.0 2021-09 SP#93E SP-210915 2993 1 F Clarifying that at least one default S-NSSAI is mandatory 17.2.0 2021-09 SP#93E SP-210925 2994 1 F correction to the re-configuration requirements for NSSRG non-supporting UEs 17.2.0 2021-09 SP#93E SP-210925 2995 - F clarification on obtaining the Configured NSSAI from NSSF when NSSRG for UE changes 17.2.0 2021-09 SP#93E SP-210911 2998 1 A Enforcing CAG restrictions during E-UTRAN to NG-RAN connected mode mobility 17.2.0 2021-09 SP#93E SP-210923 2999 1 F Update of Credentials Holder controlled prioritized lists of preferred SNPNs and GINs using SoR 17.2.0 2021-09 SP#93E SP-210922 3001 1 F TS 23.288 reference update for ADRF services 17.2.0 2021-09 SP#93E SP-210922 3002 1 F Resolving editor's note for ADRF discovery and selection 17.2.0 2021-09 SP#93E SP-210910 3003 1 A Handling of UE Radio Capability for Paging 17.2.0 2021-09 SP#93E SP-210925 3004 1 F Missing Definition of Target NSSAI 17.2.0 2021-09 SP#93E SP-210935 3009 1 B EPS User Plane Integrity Protection using SMF+PGW-C 17.2.0 2021-09 SP#93E SP-210919 3010 1 C Allowing usage of S-NSSAI and Network Instance for internal UPF resource allocation 17.2.0 2021-09 SP#93E SP-210937 3011 - F BSF related update of NRF services (23.501) 17.2.0 2021-09 SP#93E SP-210928 3018 1 F NEF discovery and selection based on AF address 17.2.0 2021-09 SP#93E SP-210931 3019 1 B Adding the functionality on MINT 17.2.0 2021-09 SP#93E SP-210920 3025 1 B NEF service to support EAS deployment info 17.2.0 2021-09 SP#93E SP-210920 3026 - F AF Request for Simultaneous Connectivity over Source and Target PSA at Edge Relocation 17.2.0 2021-09 SP#93E SP-210918 3027 1 F UE-assistance operation on traffic aggregate granularity 17.2.0 2021-09 SP#93E SP-210916 3029 1 C PDB value for 5QI 10 17.2.0 2021-09 SP#93E SP-210906 3033 1 F ATSSS Rule ID 17.2.0 2021-09 SP#93E SP-210914 3034 1 F Update the naming convention for the reference points for 5G ProSe 17.2.0 2021-09 SP#93E SP-210937 3035 1 F 5G URLLC Redundant PDU Session correction for NGAP parameters 17.2.0 2021-09 SP#93E SP-210923 3036 1 F GIN Encoding 17.2.0 2021-09 SP#93E SP-210929 3038 1 F TSN AF functional description and reference point 17.2.0 2021-09 SP#93E SP-210929 3039 1 F Updates for time synchronization text - description 17.2.0 2021-09 SP#93E SP-210929 3040 1 F Architecture to enable Time Sensitive Communication and Time Synchronization 17.2.0 2021-09 SP#93E SP-210929 3041 1 F Updates for TSCTSF text - description 17.2.0 2021-09 SP#93E SP-210929 3042 1 C Exposure of Time synchronization as a service - description 17.2.0 2021-09 SP#93E SP-210937 3043 - F Correction on Redundant PDU Session 17.2.0 2021-09 SP#93E SP-210915 3044 1 F Updates to enable mobility between GERAN/UTRAN and E-UTRAN in 5GS 17.2.0 2021-09 SP#93E SP-210923 3045 1 F Handling of SUPI/SUCI format when accessing to a SNPN 17.2.0 2021-09 SP#93E SP-210932 3048 - F Update Paging Cause Feature in 5GS 17.2.0 2021-09 SP#93E SP-210923 3049 1 F KI#4-SNPN UE Onboarding using existing DNN 17.2.0 2021-09 SP#93E SP-210929 3051 1 D Correcting the usage of Survival Time 17.2.0 2021-09 SP#93E SP-210923 3052 1 B Informative guidelines for usage of QoS related exposure capabilities to leverage between underlay network and overlay network 17.2.0 2021-09 SP#93E SP-210915 3054 1 F Correction on Charging 17.2.0 2021-09 SP#93E SP-210903 3057 1 A Derivation of UL Packet Filter from DL encapsulated IPsec protected packet 17.2.0 2021-09 SP#93E SP-210936 3062 1 C Explicit indication for ATC 17.2.0 2021-09 SP#93E SP-210936 3064 - F Corrections on the AF related identifier 17.2.0 2021-09 SP#93E SP-210937 3065 1 F Corrections on geographical area 17.2.0 2021-09 SP#93E SP-210925 3066 1 F Addition of NSACF services 17.2.0 2021-09 SP#93E SP-210925 3067 1 F Redirection to dedicated frequency band(s) at the end of NSSAA 17.2.0 2021-09 SP#93E SP-210925 3072 1 F KI#5 UE-Slice-MBR enforcement in PCF 17.2.0 2021-09 SP#93E SP-210925 3074 1 B Roaming support for NSAC in VPLMN 17.2.0 2021-09 SP#93E SP-210925 3077 1 F Support of multiple NSACF instance 17.2.0 2021-09 SP#93E SP-210922 3079 - F Update to AF Discovery and Selection 17.2.0 2021-09 SP#93E SP-210923 3084 - F Interaction between PVS and SO-SNPN 17.2.0 2021-09 SP#93E SP-210923 3085 - C DCS providing PVS address to ONN 17.2.0 2021-09 SP#93E SP-210932 3088 1 B 5GS Connection release support for 5GC/NR 17.2.0 2021-09 SP#93E SP-210917 3091 - D Update clause number for MB-UPF, MBSF and MBSTF in clause 6.2 17.2.0 2021-09 SP#93E SP-210923 3095 - B Reference point AUSF - NSSAAF 17.2.0 2021-09 SP#93E SP-210923 3097 1 B Format of SUCI/SUPI used for Onboarding 17.2.0 2021-09 SP#93E SP-210923 3098 - C SNPN support for emergency 17.2.0 2021-09 SP#93E SP-210922 3101 1 F Resolve Editor's Note on analytics metadata provisioning capability 17.2.0 2021-09 SP#93E SP-210937 3108 - F Update BSF NF profile to support SUPI and GPSI 17.2.0 2021-09 SP#93E SP-210918 3111 1 F Termination on UE assistance mode 17.2.0 2021-09 SP#93E SP-210929 3112 - F Classification of NEF or TSCTSF 17.2.0 2021-09 SP#93E SP-210918 3114 - F Removal of 5G-RG limitation on 3GPP access leg support in EPC 17.2.0 2021-09 SP#93E SP-210918 3116 1 F Clarification on source and destination addresses setting for PMF messages 17.2.0 2021-09 SP#93E SP-210916 3119 1 F Remove Editor's note in clause 5.4.11.1 in TS 23.501 17.2.0 2021-09 SP#93E SP-210920 3124 1 F Update of ECS address in External Exposure of Network Capability 17.2.0 2021-09 SP#93E SP-211133 3126 3 B Resolve ENs in NSAC support for EPC interworking 17.2.0 2021-09 SP#93E SP-210923 3136 - F Terminology correction for UE onboarding 17.2.0 2021-09 SP#93E SP-210923 3137 1 F AMF relocation for UE registered for onboarding 17.2.0 2021-09 SP#93E SP-210923 3139 - F selection of AUSF supporting primary authentication towards AAA server 17.2.0 2021-09 SP#93E SP-210929 3142 - F Clarify distribution of Announce message 17.2.0 2021-09 SP#93E SP-210929 3143 - F Clarify interworking with EPS is not supported for TSC or time synchronization 17.2.0 2021-09 SP#93E SP-210929 3144 1 F Granularity of TSCTSF 17.2.0 2021-09 SP#93E SP-210923 3146 1 F Correction on remote provisioning of credentials for NSSAA or secondary authentication/authorization 17.2.0 2021-09 SP#93E SP-210920 3149 1 F Updates on edge computing 17.2.0 2021-09 SP#93E SP-210929 3150 1 F Updates on PTP instance type 17.2.0 2021-09 SP#93E SP-210933 3155 1 B Support RedCap UEs differentiation in 5GC 17.2.0 2021-09 SP#93E SP-210911 3157 1 A Clarification on the Bridge delay calculating 17.2.0 2021-09 SP#93E SP-210929 3160 1 F KI#3, clarification on the TSCTSF functionality and configuration for transport protocols 17.2.0 2021-09 SP#93E SP-210929 3161 1 B KI#3, clarification on the exposure of time sync service 17.2.0 2021-09 SP#93E SP-210929 3162 1 F Clean up on the BMIC and bridge Management Information Container 17.2.0 2021-09 SP#93E SP-210923 3165 - F Clarification of the AMF Onboarding Configuration Data 17.2.0 2021-09 SP#93E SP-210904 3169 A 5GS Idle Status Indication 17.2.0 2021-09 SP#93E SP-210915 3170 1 B AUSF/UDM discovery based SUCI information 17.2.0 2021-09 SP#93E SP-210923 3173 1 F Clarification on NF profile in case of SNPN 17.2.0 2021-09 SP#93E SP-210923 3175 1 F Clarification on functionality of NF in SNPN 17.2.0 2021-09 SP#93E SP-210912 3178 - A Emergency services for non-3GPP access 17.2.0 2021-09 SP#93E SP-210918 3179 1 F Clarification on threshold values 17.2.0 2021-09 SP#93E SP-210920 3186 - B Use UPF to transfer DNS message between EASDF and DNS server 17.2.0 2021-09 SP#93E SP-210920 3187 - F Add Nudm_ServiceSpecificAuthorisation service 17.2.0 2021-09 SP#93E SP-210929 3189 1 F Update for (g)PTP messages forwarding in UPF/NW-TT 17.2.0 2021-09 SP#93E SP-210908 3190 2 A No empty allowed NSSAI at REGISTRATION ACCEPT 17.2.0 2021-09 SP#93E SP-210932 3192 1 F MUSIM Terminology Alignment 17.2.0 2021-09 SP#93E SP-210932 3196 - F Terminology correction 17.2.0 2021-09 SP#93E SP-210929 3198 1 C Correcting the residence time calculation for the delay measurements 17.2.0 2021-09 SP#93E SP-210916 3199 1 F SMF subscribes Satellite backhaul category backhaul change from AMF 17.2.0 2021-09 SP#93E SP-210925 3201 1 B Completion of NSAC per access type 17.2.0 2021-09 SP#93E SP-210911 3204 2 A Mapping scheduled traffic information, PSFP information and propagation delays between TSN GM clock and 5GS clock 17.2.0 2021-09 SP#93E SP-210903 3208 - A Correction of N26 message relaying between S1 and N26 messages 17.2.0 2021-09 SP#93E SP-210933 3209 1 C Extended DRX for NR (RedCap) 17.2.0 2021-09 SP#93E SP-210915 3213 1 F Update Reference architecture with UPF SBI 17.2.0 2021-09 SP#93E SP-210925 3220 1 F NSAC procedure in EPS when APN maps to more than one S-NSSAI. 17.2.0 2021-09 SP#93E SP-210915 3222 - F Indicate the number of supported packet filters for signalled QoS rules only if the UE supports more than 16 packet filters for the PDU session 17.2.0 2021-09 SP#93E SP-210932 3228 - F Clarification related to access type 17.2.0 2021-09 SP#93E SP-210915 3230 1 F Overlapping LADN Service area 17.2.0 2021-09 SP#93E SP-210911 3231 - A Clarification on support of CAG in SNPN 17.2.0 2021-09 SP#93E SP-210925 3232 - F clarification on S-NSSAI mapping 17.2.0 2021-12 SP#94E SP-211289 2385 8 C Support of the mapping from IP addressing information provided to an AF to the user identity 17.3.0 2021-12 SP#94E SP-211284 3030 4 F UE location verification handling 17.3.0 2021-12 SP#94E SP-211286 3055 3 F MBS Packet detection and forwarding 17.3.0 2021-12 SP#94E SP-211286 3092 3 F Add NF services for 5G MBS 17.3.0 2021-12 SP#94E SP-211302 3094 2 F MUSIM support for SNPN access mode 17.3.0 2021-12 SP#94E SP-211299 3107 4 F QoS parameter handling for TSC 17.3.0 2021-12 SP#94E SP-211288 3110 2 F PMF information transported via N4 17.3.0 2021-12 SP#94E SP-211304 3172 5 C NSSAAF Discovery and Selection based on S-NSSAI or UE ID Range 17.3.0 2021-12 SP#94E SP-211295 3205 2 F Update to NSSRG procedure 17.3.0 2021-12 SP#94E SP-211302 3229 2 F Deleting PRs in non allowed area 17.3.0 2021-12 SP#94E SP-211302 3235 4 F Enabling of paging reception for 5GS 17.3.0 2021-12 SP#94E SP-211550 3237 3 F MUSIM capabilities in Emergency Registration 17.3.0 2021-12 SP#94E SP-211295 3240 2 F Network Slicing scope in relation to SNPNs 17.3.0 2021-12 SP#94E SP-211294 3241 1 F Network slice admission control for SNPN onboarding 17.3.0 2021-12 SP#94E SP-211299 3242 3 F Improved PTP instance configuration management 17.3.0 2021-12 SP#94E SP-211299 3243 - F Correction of the TSCTSF functionality description 17.3.0 2021-12 SP#94E SP-211299 3244 1 F Revisions related Time Synchronization 17.3.0 2021-12 SP#94E SP-211299 3245 1 F Clarifications on TSN AF and TSCTSF parameter handling 17.3.0 2021-12 SP#94E SP-211304 3246 - C Update of clause 6.3.1.0 related to binding 17.3.0 2021-12 SP#94E SP-211288 3247 1 F Access performance measurements applicability to QoS Flows 17.3.0 2021-12 SP#94E SP-211288 3248 1 F Corrections to UE assistance operation 17.3.0 2021-12 SP#94E SP-211288 3250 1 F Clarification on threshold condition 17.3.0 2021-12 SP#94E SP-211301 3251 1 B Authentication and Subscription information checking for Disaster Roaming service 17.3.0 2021-12 SP#94E SP-211301 3252 - F Clarification for Disaster Roaming service 17.3.0 2021-12 SP#94E SP-211304 3253 1 F Reserving some reference point numbers 17.3.0 2021-12 SP#94E SP-211294 3254 1 F Clarification on Remote provisioning of credentials - User Plane 17.3.0 2021-12 SP#94E SP-211294 3255 1 F UE Configuration Data for UP Remote Provisioning provided by ONN 17.3.0 2021-12 SP#94E SP-211627 3256 6 F UE onboarding architecture 17.3.0 2021-12 SP#94E SP-211294 3257 3 D Rapporteur's editorial cleanup for eNPN 17.3.0 2021-12 SP#94E SP-211299 3260 1 F Link delay measurement for the end-to-end Transparent Clock 17.3.0 2021-12 SP#94E SP-211295 3261 2 F NSAC clarification 17.3.0 2021-12 SP#94E SP-211301 3264 3 F MINT Updates 17.3.0 2021-12 SP#94E SP-211287 3265 - C NR RedCap Indication during IRAT handover procedure 17.3.0 2021-12 SP#94E SP-211304 3267 - F GBA Reference points 17.3.0 2021-12 SP#94E SP-211295 3268 1 D Editorial Changes on eNS_Ph2 17.3.0 2021-12 SP#94E SP-211295 3269 2 F Clarification on Access Type for NSAC 17.3.0 2021-12 SP#94E SP-211294 3274 3 F eNPN corrections to clarify use of DNN and S-NSSAI for onboarding, AUSF discovery 17.3.0 2021-12 SP#94E SP-211299 3275 1 F Time synchronization - description review 17.3.0 2021-12 SP#94E SP-211299 3276 1 D Rapporteur CR for editorial fixes 17.3.0 2021-12 SP#94E SP-211294 3277 1 F Correction on remote provisioning of credentials for NSSAA or secondary authentication/authorization 17.3.0 2021-12 SP#94E SP-211298 3280 - F UAS NF selection based on the NEF capability 17.3.0 2021-12 SP#94E SP-211294 3281 1 F KI#4- Restricted Onboarding PDU session when PLMN is ON 17.3.0 2021-12 SP#94E SP-211284 3284 3 F Editorial correction in TS 23.501 17.3.0 2021-12 SP#94E SP-211299 3285 1 F Clarify the interaction between AF and TSCTSF 17.3.0 2021-12 SP#94E SP-211301 3287 1 F Clarification on MINT 17.3.0 2021-12 SP#94E SP-211284 3290 1 D Clarification on RTD and Terminology Alignment 17.3.0 2021-12 SP#94E SP-211290 3293 - F Corrections on DNAI based I-SMF selection and removal 17.3.0 2021-12 SP#94E SP-211301 3294 1 F Applicability of states of non-3GPPA and clarifications. 17.3.0 2021-12 SP#94E SP-211295 3295 1 F Update of the Early Admission Control (EAC) mode 17.3.0 2021-12 SP#94E SP-211295 3296 - F Update of the Functional Description Related to NSAC 17.3.0 2021-12 SP#94E SP-211294 3297 1 F Clarification for UE onboarding and UE access with CH credentials 17.3.0 2021-12 SP#94E SP-211290 3299 2 F 501 EASDF Service correction 17.3.0 2021-12 SP#94E SP-211295 3300 1 F The decision of target NSSAI based on NSSRG 17.3.0 2021-12 SP#94E SP-211624 3302 2 A Correction on PMF protocol stack for non-3GPP access 17.3.0 2021-12 SP#94E SP-211294 3303 1 F 23.501 clarification on eNPN 17.3.0 2021-12 SP#94E SP-211301 3311 1 F Deregistration for UE not eligible for disaster roaming service 17.3.0 2021-12 SP#94E SP-211299 3312 1 F Update for Time Synchronization Information in PMIC and UMIC 17.3.0 2021-12 SP#94E SP-211299 3313 2 F Corrections on TSCTSF selection and residence time calculation 17.3.0 2021-12 SP#94E SP-211592 3314 3 F Support for emergency calls in limited service state 17.3.0 2021-12 SP#94E SP-211287 3316 2 B eDRX enhancement for 10.24s cycle for RedCap 17.3.0 2021-12 SP#94E SP-211284 3318 2 F Limited service PLMN selection for emergency 17.3.0 2021-12 SP#94E SP-211628 3319 6 B Support for Paging Early Indication 17.3.0 2021-12 SP#94E SP-211293 3320 4 F Miscellaneous correction for eNA_Ph2 17.3.0 2021-12 SP#94E SP-211299 3321 1 F Multiple TSCTSFs associated with a single UPF 17.3.0 2021-12 SP#94E SP-211299 3322 2 F Processing (g)PTP messages for domain numbers and while in Disabled state 17.3.0 2021-12 SP#94E SP-211284 3323 2 C Support multiple TACs for satellite access 17.3.0 2021-12 SP#94E SP-211287 3324 2 B Capabilities for NR RedCap UE 17.3.0 2021-12 SP#94E SP-211303 3327 - F EPS User Plane Integrity Protection corrections for Service Request and mixed eNB UPIP support; etc in TS 23.501. 17.3.0 2021-12 SP#94E SP-211294 3328 1 F Clarification on the UE remote provisioning. 17.3.0 2021-12 SP#94E SP-211299 3330 1 F Clarification on the time synchronization 17.3.0 2021-12 SP#94E SP-211416 3331 2 F clarification on definition of NSSRG 17.3.0 2021-12 SP#94E SP-211302 3334 1 F On Paging restrictions handling 17.3.0 2021-12 SP#94E SP-211536 3335 3 F On Connection Release and Paging Restriction during a Mobility Registration Update in a TA outside the current Registration Area 17.3.0 2021-12 SP#94E SP-211288 3338 1 F Change term default QoS Flow to the QoS Flow associated with default QoS rule in TS 23.501 17.3.0 2021-12 SP#94E SP-211293 3339 - F Update to NEF Discovery and Selection 17.3.0 2021-12 SP#94E SP-211294 3340 1 F Clarification on roaming description for SNPN 17.3.0 2021-12 SP#94E SP-211294 3342 1 Release: Clarification on network selection for ON-SNPN 17.3.0 2021-12 SP#94E SP-211626 3345 4 F Clarifications of NSAC and NSAC for roaming cases 17.3.0 2021-12 SP#94E SP-211287 3346 - F Correction on Paging for extended idle mode DRX in E-UTRA and NR connected to 5GC 17.3.0 2021-12 SP#94E SP-211287 3349 - B Support of Access Restriction for RedCap 17.3.0 2021-12 SP#94E SP-211299 3351 1 D Rapporteur CR for editorial fixes - Inclusive terminology 17.3.0 2021-12 SP#94E SP-211299 3352 1 F Addressing Rel-17 DS-TT backwards incompatibility for time synchronization 17.3.0 2021-12 SP#94E SP-211299 3357 1 F Deletion of selected enrties in UMIC/PMIC data structures 17.3.0 2021-12 SP#94E SP-211300 3358 1 F Clarification on Static Filtering Entries 17.3.0 2021-12 SP#94E SP-211305 3362 - F Align BSF NF profile in NRF (23.501) with BSF related information in NRF services (23.502) 17.3.0 2021-12 SP#94E SP-211284 3364 1 F TA handling for moving cells in satellite access 17.3.0 2021-12 SP#94E SP-211276 3366 - A V-SMF change at inter-PLMN mobility 17.3.0 2021-12 SP#94E SP-211283 3367 - F NG-RAN location report clarification in RRC Inactive 17.3.0 2021-12 SP#94E SP-211294 3373 1 F Corrections for CH using AUSF/UDM 17.3.0 2021-12 SP#94E SP-211294 3374 1 F Correction to AMF Onboarding Configuration Data 17.3.0 2021-12 SP#94E SP-211299 3375 2 F 23.501: TSCTSF Discovery and Selection 17.3.0 2021-12 SP#94E SP-211284 3376 - F Clarification on IAB support for NR satellite access 17.3.0 2021-12 SP#94E SP-211282 3378 1 F Fix reference for Naf_ProSe 17.3.0 2021-12 SP#94E SP-211284 3379 - B Indicating a last visited TAI in a Registration for NR Satellite Access 17.3.0 2021-12 SP#94E SP-211304 3382 1 F Supplementation of L2TP tunnel applicable scenario 17.3.0 2021-12 SP#94E SP-211299 3386 1 F Update the correction field for the end-to-end Transparent Clock 17.3.0 2021-12 SP#94E SP-211301 3389 1 F Handling of DC is no longer applicable 17.3.0 2021-12 SP#94E SP-211278 3393 1 A correction for CAG restrictions with emergency services 17.3.0 2021-12 SP#94E SP-211294 3394 1 F clarification for QoS differentiation for User Plane IPsec Child SA in underlay network 17.3.0 2021-12 SP#94E SP-211295 3400 - F Removal of Editor's Note on Configured NSSAI 17.3.0 2021-12 SP#94E SP-211295 3401 1 F Clarification on Multiple NSACFs for S-NSSAI 17.3.0 2021-12 SP#94E SP-211299 3405 1 F Relationship between Sync Exposure and Time Distribution 17.3.0 2021-12 SP#94E SP-211299 3406 1 F Correction on 5G access stratum time distribution 17.3.0 2021-12 SP#94E SP-211301 3407 1 F Alignment on system information extensions for minimization of service interruption 17.3.0 2021-12 SP#94E SP-211301 3408 1 F Emergency Services for Disaster Inbound Roamers 17.3.0 2021-12 SP#94E SP-211295 3410 - F Corrections on Nnsacf_SliceStatus and Nnef_SliceStatus services 17.3.0 2021-12 SP#94E SP-211284 3415 1 C Mobility Registration Update trigger clarification 17.3.0 2021-12 SP#94E SP-211298 3416 1 F Correction on UAS NF discovery and update UAS related AF and NEF service 17.3.0 2021-12 SP#94E SP-211290 3418 1 F I-SMF removal triggered by removal of target DNAI 17.3.0 2021-12 SP#94E SP-211288 3421 1 F Clarification on threshold values 17.3.0 2021-12 SP#94E SP-211305 3422 1 F Clarification on support of slicing in TWIF scenario 17.3.0 2021-12 SP#94E SP-211295 3428 - F Correction for External Exposure of Network Capability 17.3.0 2021-12 SP#94E SP-211302 3430 1 F Adding Paging Cause Indication for Voice Service Supported in the RRC Inactive AI 17.3.0 2021-12 SP#94E SP-211294 3431 1 F Correction for switching 3GPP access between SNPN and PLMN 17.3.0 2021-12 SP#94E SP-211299 3438 1 F Multiple PTP instances supported in 5GS 17.3.0 2021-12 SP#94E SP-211300 3439 - F Update on configuration for Sync and Announce reception timeouts 17.3.0 2021-12 SP#94E SP-211305 3440 1 F Removal of a now obsolete sentence about non-3GPP Access being forbidden in a PLMN 17.3.0 2021-12 SP#94E SP-211279 3442 1 A Layer below IPsec to enable NAT traversal for TNGF/N3IWF access 17.3.0 2021-12 SP#94E SP-211278 3443 - A Adding AdminCycleTimeExtension and PSFPAdminCycleTimeExtension to PMIC 17.3.0 2021-12 SP#94E SP-211278 3447 1 A Bridge delay calculation and TSCAI calculation if UE-DS-TT residence time has not been provided 17.3.0 2021-12 SP#94E SP-211302 3449 1 F Clarification on paging restrictions 17.3.0 2021-12 SP#94E SP-211287 3454 - F RAT type determination on AMF for NR Redcap 17.3.0 2021-12 SP#94E SP-211305 3455 1 F Support of GERAN/UTRAN access: Annex L alignment to CR 2970r1 to TS 23.501 17.3.0 2021-12 SP#94E SP-211279 3462 1 F Clarifications on SEPP 17.3.0 2022-03 SP#95E SP-220047 3414 2 F Mapping TSCAI between TSN GM clock and 5GS clock 17.4.0 2022-03 SP#95E SP-220055 3464 1 F Aligning 23.501 and 23.548 wording about the DN accessed via a L-UPF 17.4.0 2022-03 SP#95E SP-220065 3465 1 F Adding NSWO NF in the architecture 17.4.0 2022-03 SP#95E SP-220057 3466 1 F Remove the CP based remote provisioning 17.4.0 2022-03 SP#95E SP-220064 3467 1 F Correct the MUSIM Connection Release feature 17.4.0 2022-03 SP#95E SP-220064 3468 1 F Correction on MUSIM Paging Cause feature 17.4.0 2022-03 SP#95E SP-220064 3469 1 F Correct PEI used for MUSIM and network subscriptions 17.4.0 2022-03 SP#95E SP-220057 3470 1 F DN-AAA server selection when the DCS is not involved during primary authentication 17.4.0 2022-03 SP#95E SP-220056 3471 - F Cleanup for NWDAF, DCCF, MFAF and ADRF services 17.4.0 2022-03 SP#95E SP-220055 3472 1 F Clarify FQDN in Traffic Influence 17.4.0 2022-03 SP#95E SP-220066 3473 1 F 5G-EIR clarification 17.4.0 2022-03 SP#95E SP-220062 3474 1 F Clarification on Authentication and Subscription information checking 17.4.0 2022-03 SP#95E SP-220062 3479 - F Delete the EN on disaster roaming revoking 17.4.0 2022-03 SP#95E SP-220060 3480 1 F Correction on 5G access stratum time distribution 17.4.0 2022-03 SP#95E SP-220068 3481 1 F Correction on the MME handling for UPIP during interworking 17.4.0 2022-03 SP#95E SP-220047 3487 1 A Scheduled Traffic not used for TSCAI 17.4.0 2022-03 SP#95E SP-220282 3489 2 F Clarifications on NSAC for Emergency and Priority Services 17.4.0 2022-03 SP#95E SP-220066 3491 - F Number of CN paging subgroups 17.4.0 2022-03 SP#95E SP-220066 3492 - F Reference Architecture Editorial Correction 17.4.0 2022-03 SP#95E SP-220066 3495 1 F Correction for Restriction of use of Enhanced Coverage 17.4.0 2022-03 SP#95E SP-220051 3498 1 F NR NTN: Correction to TA Handling 17.4.0 2022-03 SP#95E SP-220053 3501 1 F MA PDU sessions with connectivity over E-UTRAN/EPC and non-3GPP access to 5GC 17.4.0 2022-03 SP#95E SP-220042 3505 1 A SSC mode support by the UEs 17.4.0 2022-03 SP#95E SP-220066 3507 1 F Handling of VPLMN QoS constraints during mobility 17.4.0 2022-03 SP#95E SP-220058 3508 1 F Clarification on the Registration area when Target NSSAI is indicated 17.4.0 2022-03 SP#95E SP-220057 3510 1 F Correction for remote provisioning 17.4.0 2022-03 SP#95E SP-220057 3511 1 F CH architecture update 17.4.0 2022-03 SP#95E SP-220057 3512 1 F Correction for UE onboarding 17.4.0 2022-03 SP#95E SP-220057 3514 1 F Correction in AAA selection procedure 17.4.0 2022-03 SP#95E SP-220057 3515 - F Support for emergency calls when no PLMN acceptable cell is available 17.4.0 2022-03 SP#95E SP-220056 3517 1 F Clarifications for NWDAF profile and NWDAF discovery 17.4.0 2022-03 SP#95E SP-220067 3518 - F Clarification on non-3gpp AN selection 17.4.0 2022-03 SP#95E SP-220047 3522 1 F Clarification for Routing Indicator on SNPN-enabled UE 17.4.0 2022-03 SP#95E SP-220060 3523 1 F Multiple NW-TTs associated with a single UPF 17.4.0 2022-03 SP#95E SP-220060 3524 1 F Clarifications and clean-ups for TSC 17.4.0 2022-03 SP#95E SP-220057 3525 1 F Clarifications for SNPN onboarding service 17.4.0 2022-03 SP#95E SP-220057 3526 1 F Corrections for UE access with CH credentials 17.4.0 2022-03 SP#95E SP-220057 3527 1 D terms alignments and clean-ups for eNPN 17.4.0 2022-03 SP#95E SP-220062 3530 1 F Disaster roaming disable handling 17.4.0 2022-03 SP#95E SP-220060 3534 1 F Time Synchronization of the 5GS as IEEE 1588 Boundary Clock 17.4.0 2022-03 SP#95E SP-220060 3535 1 F Correction for the end-to-end Transparent Clock 17.4.0 2022-03 SP#95E SP-220059 3537 1 F Correction on UAS NF discovery 17.4.0 2022-03 SP#95E SP-220045 3538 1 A Corrections to combined N3IWF/ePDG Selection 17.4.0 2022-03 SP#95E SP-220058 3540 1 F Registration with AMF re-allocation in connected state 17.4.0 2022-03 SP#95E SP-220062 3543 - F Disaster roaming registration type 17.4.0 2022-03 SP#95E SP-220055 3548 1 F Add missing EASDF descriptions 17.4.0 2022-03 SP#95E SP-220051 3549 1 F TAIs reporting corresponding to the Selected PLMN 17.4.0 2022-03 SP#95E SP-220056 3552 1 F Removal of Nnssf_NSRestriction service 17.4.0 2022-03 SP#95E SP-220281 3553 2 F Correction of Subscription-related Priority Mechanism 17.4.0 2022-03 SP#95E SP-220066 3554 1 F Inter-system configuration transfer 17.4.0 2022-03 SP#95E SP-220051 3555 1 F Correction of Mobility Restrictions handling for emergency calls 17.4.0 2022-03 SP#95E SP-220067 3556 1 F Clarification on TAI configured for Non 3GPP access 17.4.0 2022-03 SP#95E SP-220048 3558 1 A LLDP neighbour discovery information fixes 17.4.0 2022-03 SP#95E SP-220057 3559 1 F Clarification of ProSe support in SNPN 17.4.0 2022-03 SP#95E SP-220062 3563 1 F Alignment with use of Disaster Roaming Enabled Configuration 17.4.0 2022-03 SP#95E SP-220057 3567 1 F Clean-up the clause on UP onboarding via ON-SNPN 17.4.0 2022-03 SP#95E SP-220047 3568 1 A Handling of untagged frames in TSN scenarios 17.4.0 2022-03 SP#95E SP-220047 3570 1 A Add missing SupportedListMax for gate control information in PMIC and UMIC 17.4.0 2022-03 SP#95E SP-220058 3571 1 F Clarification on support of multiple NSACFs 17.4.0 2022-03 SP#95E SP-220066 3577 1 F Completing description of NF profile 17.4.0 2022-03 SP#95E SP-220066 3578 1 F Paging Early Indication: Removal of Editor's notes 17.4.0 2022-06 SP#96 SP-220412 3317 7 B Enabling slice priority and slice groups for RRM purposes 17.5.0 2022-06 SP#96 SP-220404 3485 2 F Correcting the 5G AS time distribution procedure 17.5.0 2022-06 SP#96 SP-220412 3539 4 B Enabling configuration of Network Slice AS Groups 17.5.0 2022-06 SP#96 SP-220406 3580 3 F Disaster Roaming service indication 17.5.0 2022-06 SP#96 SP-220400 3581 1 F Role of Credential Holder 17.5.0 2022-06 SP#96 SP-220401 3582 1 F Removal of NSACF from HPLMN in LBO Model 17.5.0 2022-06 SP#96 SP-220401 3584 1 F Clarification on determination of Registration Area 17.5.0 2022-06 SP#96 SP-220400 3589 1 F Network Slicing Support in SNPN 17.5.0 2022-06 SP#96 SP-220411 3591 1 F Alignment to BBF LS 512 (Frame route, BBF references) 17.5.0 2022-06 SP#96 SP-220411 3593 1 F Handling of ARP for IMS voice service in home routed roaming 17.5.0 2022-06 SP#96 SP-220407 3596 - F Correction of message name for paging restriction information 17.5.0 2022-06 SP#96 SP-220406 3599 1 F Session related subscription information 17.5.0 2022-06 SP#96 SP-220406 3600 2 F Clarification on UE 5GMM Capability 17.5.0 2022-06 SP#96 SP-220406 3601 - F Removing the editor's note related to CT1 17.5.0 2022-06 SP#96 SP-220394 3604 1 F Criterion of Verification of UE location for UE registering via 5G Satellite Access 17.5.0 2022-06 SP#96 SP-220404 3605 1 F Corrections to Survival Time description 17.5.0 2022-06 SP#96 SP-220404 3606 1 F Corrections to time synchronization description 17.5.0 2022-06 SP#96 SP-220394 3607 1 F Clarification on AMF obtaining the satellite-related information 17.5.0 2022-06 SP#96 SP-220400 3609 1 F SMF UP remote provisioning capability 17.5.0 2022-06 SP#96 SP-220396 3612 2 F AMF selection to support HLcom feaure for RedCap using power saving function 17.5.0 2022-06 SP#96 SP-220400 3613 - F DCS supporting AUSF/UDM and AAA server functionality 17.5.0 2022-06 SP#96 SP-220408 3617 4 F 23.501: NSWO and N3GPP access support 17.5.0 2022-06 SP#96 SP-220394 3621 1 F RAN Initiated UE Context Release for UE using NR satellite access 17.5.0 2022-06 SP#96 SP-220400 3623 2 F Clarification on the FQDN(s) and IP address(es) of PVS for remote provisioning 17.5.0 2022-06 SP#96 SP-220404 3624 1 F Clarification on how the TSFTSF assign the NW-TT port to PPT instance 17.5.0 2022-06 SP#96 SP-220404 3625 2 F Clarification on 5G access stratum distribution in mobility 17.5.0 2022-06 SP#96 SP-220406 3626 - F End of disaster condition 17.5.0 2022-06 SP#96 SP-220406 3628 1 C UE capabilities indication for UPU with Disaster Roaming information 17.5.0 2022-06 SP#96 SP-220688 3633 3 F RFSP Index authorized by PCF and subscribed RFSP Index 17.5.0 2022-06 SP#96 SP-220410 3635 1 F NRF discovery and selection 17.5.0 2022-06 SP#96 SP-220391 3642 1 A clarifications for CAG access control for a UE without mobility restrictions 17.5.0 2022-06 SP#96 SP-220410 3645 1 F Correction of UE behaviour upon mobility between GERAN/UTRAN and 5GS 17.5.0 2022-06 SP#96 SP-220391 3649 1 A Correction of the Signalling Based Tracing support 17.5.0 2022-06 SP#96 SP-220410 3650 1 F UDR storing of non-subscriber related data 17.5.0 2022-06 SP#96 SP-220401 3652 1 F Clarification on roaming for NSAC procedure 17.5.0 2022-06 SP#96 SP-220394 3653 1 F Remove country of UE location from clause 5.16.4.1 in TS23.501 17.5.0 2022-06 SP#96 SP-220411 3654 1 F Correction of NSSF involvement in Registration procedure when NSSAA is used 17.5.0 2022-06 SP#96 SP-220410 3655 1 F Correction of UE Configuration Update procedure conditions for Registration Required and NAS Release 17.5.0 2022-09 SP#97E SP-220783 3603 4 F Defining the time distribution methods 17.6.0 2022-09 SP#97E SP-220780 3616 2 F Clarification on UE-Slice-MBR 17.6.0 2022-09 SP#97E SP-220779 3629 2 F DN-AAA server selection during UE onboarding 17.6.0 2022-09 SP#97E SP-220771 3647 2 A Clarification of UE egress terminology 17.6.0 2022-09 SP#97E SP-220789 3659 1 F Handling of PDU Sessions for Emergency services 17.6.0 2022-09 SP#97E SP-220788 3660 1 B Alignment of SBI-based SMS 17.6.0 2022-09 SP#97E SP-220789 3661 - F Correction on Reference Architecture 17.6.0 2022-09 SP#97E SP-220785 3664 1 F UCU procedure for MINT update 17.6.0 2022-09 SP#97E SP-220789 3665 1 F ULI provision with PScell information 17.6.0 2022-09 SP#97E SP-220769 3666 1 C Periodic update time from UE 17.6.0 2022-09 SP#97E SP-220789 3674 1 F Handover capability detection 17.6.0 2022-09 SP#97E SP-220789 3676 1 F Closing open issues on RAN slicing 17.6.0 2022-09 SP#97E SP-220789 3677 1 F Missing UDSF timer service 17.6.0 2022-09 SP#97E SP-220776 3678 1 F PMF UAD and UAT message handling clarifications 17.6.0 2022-09 SP#97E SP-220786 3683 1 F Clarifications on Priority Subscription 17.6.0 2022-09 SP#97E SP-220783 3685 - F Clarification on 5G access stratum distribution in mobility and AM policy modification 17.6.0 2022-09 SP#97E SP-220774 3687 1 F AMF sends forbidden TAI(s) to UE 17.6.0 2022-09 SP#97E SP-220771 3689 1 A Correction on 5G VN group management 17.6.0 2022-09 SP#97E SP-220789 3697 1 B Access Network selection for 5G NSWO 17.6.0 2022-09 SP#97E SP-220787 3698 1 F Clarification related to Inactive state 17.6.0 2022-09 SP#97E SP-220785 3700 1 F Clarification related to emergency service 17.6.0 2022-12 SP#98E - - - - MCC Correction to add missing N1 line to Figure 4.2.10-1 17.7.0 2022-12 SP#98E SP-221079 3583 4 F Clarification on Mapped NSSAI 17.7.0 2022-12 SP#98E SP-221069 3634 2 F Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF 17.7.0 2022-12 SP#98E SP-221080 3663 2 F Correction related to traffic correlation in PCC rule 17.7.0 2022-12 SP#98E SP-221079 3673 2 F Mapped NSSAI alignment with stage-3 17.7.0 2022-12 SP#98E SP-221071 3675 2 F Alignment with SA3 agreement on usage of SUCI when CH is legacy AAA 17.7.0 2022-12 SP#98E SP-221072 3693 2 F Pending NSSAI and NSSRG 17.7.0 2022-12 SP#98E SP-221080 3704 1 F ULI with TAI for non-3GPP access 17.7.0 2022-12 SP#98E SP-221062 3709 - A R17 Correction on TNGF functionality 17.7.0 2022-12 SP#98E SP-221079 3711 1 F Emergency PDU session transfer 17.7.0 2022-12 SP#98E SP-221079 3712 1 F Monitoring event in 5GS to EPS mobility 17.7.0 2022-12 SP#98E SP-221071 3731 1 F Clarification when access SNPN using CH with AAA-S 17.7.0 2022-12 SP#98E SP-221080 3742 1 F Correction of reference for RedCap indication from UE 17.7.0 2022-12 SP#98E SP-221079 3747 1 F Correction on conditions for using SPI for UE derived QoS rules 17.7.0 2022-12 SP#98E SP-221066 3801 2 F NSAG Information validation in Equivalent PLMN 17.7.0 2022-12 SP#98E SP-221094 3701 4 B Secondary DN authentication and authorization in EPS IWK case 18.0.0 2022-12 SP#98E SP-221090 3705 1 B Support of RRC_INACTIVE with long eDRX 18.0.0 2022-12 SP#98E SP-221084 3707 1 B N3IWF selection enhancement for support of S-NSSAI needed by UE 18.0.0 2022-12 SP#98E SP-221085 3710 1 C RFSP index in use at 5GS to EPS mobility 18.0.0 2022-12 SP#98E SP-221085 3713 1 B RFSP index during interworking 18.0.0 2022-12 SP#98E SP-221087 3714 5 B Support of Non-3GPP access for SNPN 18.0.0 2022-12 SP#98E SP-221089 3715 1 B TS 23.501 Enhancing External Exposure of Network Capability 18.0.0 2022-12 SP#98E SP-221093 3723 1 B Update for UPF registration and event exposure related context concluded in FS_UPEAS 18.0.0 2022-12 SP#98E SP-221087 3730 - B Equivalent SNPN support 18.0.0 2022-12 SP#98E SP-221094 3733 F De-activation timer for eCall only mode UE in RRC_INACTIVE 18.0.0 2022-12 SP#98E SP-221092 3734 5 B RAN feedback for burst sending time adjustment 18.0.0 2022-12 SP#98E SP-221093 3737 1 B Introduction of UPEAS 18.0.0 2022-12 SP#98E SP-221091 3749 1 B Support of unavailability period 18.0.0 2022-12 SP#98E SP-221094 3752 1 B Reference point numbers for charging 18.0.0 2022-12 SP#98E SP-221092 3762 3 B Adding time synchronization service based on subscription 18.0.0 2022-12 SP#98E SP-221092 3767 2 B Support for coverage area filters for time synchronization service 18.0.0 2022-12 SP#98E SP-221139 3772 3 B Discovery and Selection of the NWDAF Supporting Federated Learning in 5GC 18.0.0 2022-12 SP#98E SP-221139 3783 2 B NWDAF discovery principle enhancements for enhanced model sharing 18.0.0 2022-12 SP#98E SP-221140 3785 2 B Multiple NSACF architecture enhancement 18.0.0 2022-12 SP#98E SP-221086 3788 2 B KI#4 23.501 AF traffic influence for common EAS, DNAI selection 18.0.0 2022-12 SP#98E SP-221081 3790 2 B Verification of UE location update in 23.501 18.0.0 2022-12 SP#98E SP-221083 3793 2 B Support of Satellite Edge Computing via UPF deployed on satellite 18.0.0 2022-12 SP#98E SP-221083 3794 4 B Support of local switch via UPF deployed on satellite for GEO backhaul case 18.0.0 2022-12 SP#98E SP-221096 3796 2 B Enhancements of PCF Services and NEF Services 18.0.0 2022-12 SP#98E SP-221083 3803 2 B QoS Monitoring for Dynamic Satellite Backhaul 18.0.0 2022-12 SP#98E SP-221092 3811 2 B Interworking with TSN network deployed in the transport network 18.0.0 2022-12 SP#98E SP-221141 3813 3 B Introduction of Mobile Base Station Relay 18.0.0 2023-03 SP#99 SP-230080 3594 1 D RRC state and CM state terminology alignment 18.1.0 2023-03 SP#99 SP-230077 3720 2 B UPF event exposure service for TSC management 18.1.0 2023-03 SP#99 SP-230070 3745 2 B MPS when access to 5GC is WLAN 18.1.0 2023-03 SP#99 SP-230051 3755 1 C Group Message Delivery 18.1.0 2023-03 SP#99 SP-230247 3759 7 B Support of XR and Media Services 18.1.0 2023-03 SP#99 SP-230058 3761 4 C Introducing selection of more granular set of UEs 18.1.0 2023-03 SP#99 SP-230058 3789 2 B Common EAS/DNAI selection by AF 18.1.0 2023-03 SP#99 SP-230247 3792 7 B PCF support of 5GS Packet Delay Variation monitoring based on QoS monitoring mechanism and exposed to AF 18.1.0 2023-03 SP#99 SP-230052 3807 1 B Reporting the RAN timing synchronization status change from AMF to TSCTSF 18.1.0 2023-03 SP#99 SP-230058 3820 5 B Edge Relocation within the same hosting PLMN's EHEs 18.1.0 2023-03 SP#99 SP-230063 3821 2 B N5CW device access to SNPN services 18.1.0 2023-03 SP#99 SP-230169 3822 7 B KI#4: Support for Centralized NSACF in a PLMN with multi-service areas 18.1.0 2023-03 SP#99 SP-230064 3823 6 B KI#4: Support for HPLMN admission mode while Roaming 18.1.0 2023-03 SP#99 SP-230077 3825 1 B Support of NAT exposure in 23.501 according to the conclusion in UPEAS 18.1.0 2023-03 SP#99 SP-230058 3830 1 B The support of Home Routed PDU Session supporting Session Breakout in VPLMN (HR-SBO) 18.1.0 2023-03 SP#99 SP-230080 3831 1 F Impacts of CH architecture in N3IWF selection 18.1.0 2023-03 SP#99 SP-230051 3834 1 B MBS service for UE using power saving functions 18.1.0 2023-03 SP#99 SP-230063 3835 3 C Support for NSWO with CH 18.1.0 2023-03 SP#99 SP-230055 3837 1 F Resolving EN on PCF's awareness of modified RFSP index indicating a change of priority from 5GC to EPC 18.1.0 2023-03 SP#99 SP-230034 3840 1 A PDU Session Type Selection in the URSP Rule 18.1.0 2023-03 SP#99 SP-230063 3841 - B Clarification of SNPN access mode 18.1.0 2023-03 SP#99 SP-230063 3842 3 B Introduction to Localized Services 18.1.0 2023-03 SP#99 SP-230063 3992 3 B Enabling Access to Localized Services 18.1.0 2023-03 SP#99 SP-230063 3843 1 B Support for leaving network that provides access to localized services 18.1.0 2023-03 SP#99 SP-230057 3844 9 B Support of integration with IETF Deterministic Networking 18.1.0 2023-03 SP#99 SP-230044 3848 - A Emergency configuration data update 18.1.0 2023-03 SP#99 SP-230078 3850 - F Update for the support of mobile IAB 18.1.0 2023-03 SP#99 SP-230073 3854 4 B PIN support in 5GC 18.1.0 2023-03 SP#99 SP-230247 3855 11 B Introduction of support for L4S 18.1.0 2023-03 SP#99 SP-230048 3858 1 B Introducing 5G ProSe ph2 function for KI#7 (Support of Emergency for UE-to-Network Relaying) 18.1.0 2023-03 SP#99 SP-230081 3859 1 B IPv6 prefix delegation in 5GS 18.1.0 2023-03 SP#99 SP-230075 3860 1 B SFC CR 23.501 18.1.0 2023-03 SP#99 SP-230247 3864 5 B Policy control enhancements to support multi-modal flows 18.1.0 2023-03 SP#99 SP-230064 3867 5 B Change of Network Slice instance for PDU sessions 18.1.0 2023-03 SP#99 SP-230052 3870 1 B Removing ENs for TSN TN integration 18.1.0 2023-03 SP#99 SP-230052 3871 1 F Clarification on for TSN TN integration 18.1.0 2023-03 SP#99 SP-230052 3872 - B Removing EN on UL scenario of Reactive RAN feedback for burst sending time adjustment 18.1.0 2023-03 SP#99 SP-230247 3875 14 B Introduction of support for Jitter Measurement and End of Data Burst reporting to the NG-RAN 18.1.0 2023-03 SP#99 SP-230056 3878 1 B Support for non-3GPP access path switching 18.1.0 2023-03 SP#99 SP-230081 3881 2 B 5QI for V2X message delivery via MBS 18.1.0 2023-03 SP#99 SP-230063 3883 7 B UE discover, select and access to a Hosting network for Localized services 18.1.0 2023-03 SP#99 SP-230081 3886 - B 23.501 - Spending Limits for AM and UE Policies in the 5GC 18.1.0 2023-03 SP#99 SP-230247 3887 6 B Introduction of 5GS Information Exposure 18.1.0 2023-03 SP#99 SP-230052 3892 6 B Support for network timing synchronization status and reporting KI1 - description 18.1.0 2023-03 SP#99 SP-230052 3895 4 C The support for Periodicity feedback in Enablers for Time Sensitive Communications and Time Synchronization feature KI6. 18.1.0 2023-03 SP#99 SP-230247 3896 12 B Update TS23.501 to reflect conclusion of KI#4 for XRM in TR23.700-60 18.1.0 2023-03 SP#99 SP-230073 3897 12 B PIN communication configuration 18.1.0 2023-03 SP#99 SP-230073 3898 3 B PIN policy configuration 18.1.0 2023-03 SP#99 SP-230054 3910 5 B Assistance to Member Selection Functionality for Application Operation 18.1.0 2023-03 SP#99 SP-230073 3912 1 B Non-3GPP QoS and delay budget - 23.501 18.1.0 2023-03 SP#99 SP-230068 3914 1 B Service area provisioning and LADN aspects for enhanced group management 18.1.0 2023-03 SP#99 SP-230247 3919 7 B Introduction of KI#6 conclusion: uplink-downlink transmission coordination 18.1.0 2023-03 SP#99 SP-230247 3923 10 B Network exposure support for XR services 18.1.0 2023-03 SP#99 SP-230065 3924 1 B Support URSP provisioning in EPS 18.1.0 2023-03 SP#99 SP-230062 3925 1 B TS 23.501 enhancements for federated learining. 18.1.0 2023-03 SP#99 SP-230062 3926 1 B TS 23.501 enhancements for model sharing. 18.1.0 2023-03 SP#99 SP-230063 3927 6 B Clarifications on Onboarding in SNPN supporting localized services 18.1.0 2023-03 SP#99 SP-230080 3928 1 F TS 23.501: Clarification of handling of the non-3GPP PDU session in Non-allowed service area 18.1.0 2023-03 SP#99 SP-230062 3929 4 B Considering ML model management capability during ADRF discovery and selection 18.1.0 2023-03 SP#99 SP-230078 3933 1 B Providing cell ID/TAC of MBSR for services 18.1.0 2023-03 SP#99 SP-230040 3935 1 A Clarification on NSSRG enforcement when a UE registered to different PLMNs over 3GPP access and non-3GPP access 18.1.0 2023-03 SP#99 SP-230056 3937 1 B Support non-3GPP access leg of MA-PDU Session with PDN connection in EPC 18.1.0 2023-03 SP#99 SP-230064 3939 7 B Improved network control of the UE beahviour for a network slice 18.1.0 2023-03 SP#99 SP-230043 3948 1 A 5G NSWO clarifications and corrections 18.1.0 2023-03 SP#99 SP-230077 3949 1 C User Plane Function Selection for UPEAS 18.1.0 2023-03 SP#99 SP-230053 3953 1 B TNGF selection enhancement for support of S-NSSAI needed by UE 18.1.0 2023-03 SP#99 SP-230387 3956 13 B Transfer of Satellite Coverage Data to a UE and AMF 18.1.0 2023-03 SP#99 SP-230064 3959 7 B Hierarchical NSAC architecture enhancement 18.1.0 2023-03 SP#99 SP-230077 3962 1 F Direct Exposure from UPF and UPF selection 18.1.0 2023-03 SP#99 SP-230068 3964 1 B KI#3, NEF exposure for handling PDU Session Type change and managing temporal invalidity/validity condition for a group of UEs 18.1.0 2023-03 SP#99 SP-230049 3966 3 B Paging enhancement during satellite discontinuous coverage 18.1.0 2023-03 SP#99 SP-230054 3968 4 B 5GS Assistance for Application AI/ML operation: General clause 18.1.0 2023-03 SP#99 SP-230056 3973 1 B Introduction of the MPQUIC Steering Functionality 18.1.0 2023-03 SP#99 SP-230052 3981 1 F Update for controlling time synchronization service based on Subscription 18.1.0 2023-03 SP#99 SP-230068 3982 1 B Group MBR 18.1.0 2023-03 SP#99 SP-230068 3984 1 B UE-to-UE QoS for a group 18.1.0 2023-03 SP#99 SP-230050 3985 - B Add description for PSA UPF selection 18.1.0 2023-03 SP#99 SP-230068 3986 1 B Allowing UE to simultaneously send data to different groups with different QoS policy 18.1.0 2023-03 SP#99 SP-230058 3987 5 B KI#4 AF traffic influence for common EAS, DNAI selection 18.1.0 2023-03 SP#99 SP-230055 3991 1 B Clarification of AMF behaviour when it receives RFSP Index in Use Validity Time from MME during UE mobility from EPS to 5GS 18.1.0 2023-03 SP#99 SP-230040 3998 1 A Pending NSSAI and AMF Relocation in Connected mode 23.501. 18.1.0 2023-03 SP#99 SP-230050 3999 1 B Clarification of N19 forwarding for local switch via PSA UPF on GEO 18.1.0 2023-03 SP#99 SP-230064 4004 5 B Optimizations for the support of time vality policies for a network slice and graceful network slice PDU sessions release. 18.1.0 2023-03 SP#99 SP-230068 4010 1 B Add the default QoS parameters for 5G VN group data 18.1.0 2023-03 SP#99 SP-230038 4018 1 A Correction of supported services in UPF 18.1.0 2023-03 SP#99 SP-230056 4019 1 B Introducing Redundant Steering Mode 18.1.0 2023-03 SP#99 SP-230049 4020 6 B Wait range during discontinuous coverage. 18.1.0 2023-03 SP#99 SP-230073 4028 5 B Informative Annex on PIN Architecture 18.1.0 2023-03 SP#99 SP-230386 4033 13 B Support of discontinuous coverage 18.1.0 2023-03 SP#99 SP-230064 4035 7 B Introduction of partially Allowed NSSAI and Partially Rejected S-NSSAI 18.1.0 2023-03 SP#99 SP-230315 4036 4 B Introduction of Alternative S-NSSAI replacement determined by NSSF 18.1.0 2023-03 SP#99 SP-230078 4039 1 F Resolving EN on emergency services. 18.1.0 2023-03 SP#99 SP-230373 4040 3 F Not allowed to act as MBSR handling 18.1.0 2023-03 SP#99 SP-230058 4042 3 B Edge relocation with common DNAI 18.1.0 2023-03 SP#99 SP-230247 4046 12 B Support of PDU Set based handling 18.1.0 2023-03 SP#99 SP-230080 4049 F Corrections of Nudm service operations list 18.1.0 2023-03 SP#99 SP-230058 4054 - B AF obtaining DNAI associated to EAS 18.1.0 2023-03 SP#99 SP-230080 4056 1 F Generalization of QoS monitoring control description 18.1.0 2023-03 SP#99 SP-230080 4057 1 F Clarifications for GTP-U Path Monitoring 18.1.0 2023-03 SP#99 SP-230080 4058 1 F Restructuring of user plane management clause 18.1.0 2023-03 SP#99 SP-230075 4069 1 B Support for Service Function Chaining in 5GS 18.1.0 2023-03 SP#99 SP-230062 4070 - B Discovery and selection of NWDAF with FL support - Resolve EN 18.1.0 2023-03 SP#99 SP-230044 4076 1 A Mapped NSSAI when UE is roaming 18.1.0 2023-03 SP#99 SP-230064 4077 6 B Support of reduced network slice availability 18.1.0 2023-03 SP#99 SP-230064 4078 2 B Support of graceful/gradual termination of PDU sessions during network slice decommissioning 18.1.0 2023-03 SP#99 SP-230062 4080 1 B Using network analytics for roaming scenarios 18.1.0 2023-03 SP#99 SP-230115 4081 1 B CN based MT communication capability indication 18.1.0 2023-03 SP#99 SP-230064 4083 10 B Support of network slice replacement 18.1.0 2023-03 SP#99 SP-230068 4086 1 B KI#1: Support the enhancement of group attribute management 18.1.0 2023-03 SP#99 SP-230068 4087 1 B KI#3: provisioning of traffic characteristics and monitoring of performance characteristics 18.1.0 2023-03 SP#99 SP-230052 4088 4 B Clarify on periodicity adaption on Proactive feedback 18.1.0 2023-03 SP#99 SP-230052 4089 4 F Clarification for Controlling time synchronization service based on the Subscription 18.1.0 2023-03 SP#99 SP-230073 4092 6 B PIN definition and architecture 18.1.0 2023-03 SP#99 SP-230063 4095 1 B SNPN broadcast system information and manual network selection for localized service 18.1.0 2023-03 SP#99 SP-230044 4101 1 A UDM determination Internal Group ID values for 5G VN group management 18.1.0 2023-03 SP#99 SP-230062 4105 1 B Update NEF to support NWDAF-assisted application detection 18.1.0 2023-03 SP#99 SP-230078 4107 1 C UE mobility when moving together with a MBSR cell 18.1.0 2023-03 SP#99 SP-230078 4108 1 B Configuration of the MBSR node 18.1.0 2023-03 SP#99 SP-230063 4118 3 B Support of non-3GPP access to SNPN 18.1.0 2023-03 SP#99 SP-230063 4119 3 B Support of allowed CAG list with validity condition 18.1.0 2023-03 SP#99 SP-230063 4124 3 B Support of wireline access as access to SNPN 18.1.0 2023-03 SP#99 SP-230054 4128 4 B Support of Group AF Sessions for QoS Resource Allocation and QoS monitoring operation 18.1.0 2023-03 SP#99 SP-230052 4133 2 B Ensuring that a geographical area requested for a time sync service coincides with a RA 18.1.0 2023-03 SP#99 SP-230040 4137 1 A UE-Slice-MBR clarifications including for priority services 18.1.0 2023-03 SP#99 SP-230058 4144 - B Common EAS re-discovery initiated by SMF 18.1.0 2023-03 SP#99 SP-230170 4156 2 B Event exposure enhancement for enhanced NSAC architecture 18.1.0 2023-03 SP#99 SP-230058 4160 2 B Delivery of Traffic Influence information for Home Routed-Session Breakout (HR-SBO) support 18.1.0 2023-03 SP#99 SP-230052 4180 1 C Corrections for the description of coverage area support for time synchronization service KI2 18.1.0 2023-06 SP#100 SP-230490 3748 2 F Support for 5QI Priority Level in QoS constraints 18.2.0 2023-06 SP#100 SP-230469 3764 6 B Extension of NWDAF registration information to reflect new accuracy checking capability 18.2.0 2023-06 SP#100 SP-230495 3922 2 F Update for the description of the Nupf interface in 5G reference architecture 18.2.0 2023-06 SP#100 SP-230490 4037 2 F NWDAF discovery with overlapping Serving Areas 18.2.0 2023-06 SP#100 SP-230463 4155 5 A Rewording of NOTE on AF Specific UE identifier 18.2.0 2023-06 SP#100 SP-230497 4183 3 B Support of extra traffic characteristics for alternative QoS profile 18.2.0 2023-06 SP#100 SP-230491 4189 - B Dymically changing AM policies for inbound roamers using LBO 18.2.0 2023-06 SP#100 SP-230476 4190 - F KI#3 -5GS to EPS mobility 18.2.0 2023-06 SP#100 SP-230457 4191 1 F Translation of Internal-External Information for Assisting Application Layer AI/ML Operations 18.2.0 2023-06 SP#100 SP-230457 4192 6 F High level feature description for AIMLsys 18.2.0 2023-06 SP#100 SP-230493 4196 1 C Resolving (Removing) ENs for TSN TN integration 18.2.0 2023-06 SP#100 SP-230471 4202 1 C Clarify the allowed CAG list with validity condition 18.2.0 2023-06 SP#100 SP-230471 4205 1 C SNPN selection for access to localized services 18.2.0 2023-06 SP#100 SP-230459 4210 1 C Updates to non-3GPP access path switching 18.2.0 2023-06 SP#100 SP-230478 4211 1 C Corrections to handling of LADN area per DNN and S-NSSAI 18.2.0 2023-06 SP#100 SP-230493 4216 9 C Revision on the support of network timing synchronization status and reporting 18.2.0 2023-06 SP#100 SP-230483 4218 1 C Co-existence of Small Data Transmission and CN based MT communication handling for UE in RRC_INACTIVE 18.2.0 2023-06 SP#100 SP-230497 4219 6 C Resolution of EN for L4S 18.2.0 2023-06 SP#100 SP-230484 4224 1 F PDU session sharing among PINs 18.2.0 2023-06 SP#100 SP-230496 4228 6 C Additional User Location Information 18.2.0 2023-06 SP#100 SP-230490 4229 1 F IAB node release handling 18.2.0 2023-06 SP#100 SP-230483 4231 1 F N2 release handling for RRC_INACTIVE 18.2.0 2023-06 SP#100 SP-230473 4234 1 F Resolving open issues related to Alternative S-NSSAI 18.2.0 2023-06 SP#100 SP-230473 4235 - F Resolving open issues for temporarily available network slices 18.2.0 2023-06 SP#100 SP-230473 4236 1 C Resolving open issues for Network Slices with Network Slice Area of Service not matching deployed TAs 18.2.0 2023-06 SP#100 SP-230471 4238 - F Additional requirements for N3IWF selection for onboarding 18.2.0 2023-06 SP#100 SP-230451 4240 4 C Closing ENs for the procedures for discontinuous coverage reporting 18.2.0 2023-06 SP#100 SP-230452 4246 1 B Optimization consideration for satellite backhaul QoS monitoring 18.2.0 2023-06 SP#100 SP-230494 4249 - B 5QI for A2X message delivery via MBS 18.2.0 2023-06 SP#100 SP-230476 4253 1 B Support URSP provisioning in EPS 18.2.0 2023-06 SP#100 SP-230457 4255 1 F R18 AIMLsys_General_23501 CR_EN on AIML traffic 18.2.0 2023-06 SP#100 SP-230457 4257 - F R18 AIMLsys_KI1_23501 CR_SingleSO_for_QoS 18.2.0 2023-06 SP#100 SP-230472 4259 1 A Number of PDU session slice availability check during EPC IWK 18.2.0 2023-06 SP#100 SP-230471 4270 1 B Network access control when the UE accesse an SNPN that provides access for Localized Services 18.2.0 2023-06 SP#100 SP-230461 4271 4 F Selection of Common DNAI 18.2.0 2023-06 SP#100 SP-230497 4278 1 F KI#6 text alignment text 18.2.0 2023-06 SP#100 SP-230460 4280 1 F Architectural diagram change for DetNet 18.2.0 2023-06 SP#100 SP-230460 4281 1 B UPF discovery and Selection for DetNet 18.2.0 2023-06 SP#100 SP-230484 4284 7 C Clarifying SMF behaviour for non-3GPP delay budget 18.2.0 2023-06 SP#100 SP-230484 4287 6 B PIN identifiers 18.2.0 2023-06 SP#100 SP-230471 4288 1 B Configuration of Credentials Holder for determining SNPN selection information (Annex N.x) 18.2.0 2023-06 SP#100 SP-230452 4293 1 B Update the descriptions for supporting Edge Computing on satellite 18.2.0 2023-06 SP#100 SP-230497 4294 3 C QoS Monitoring and 5GS information exposure update 18.2.0 2023-06 SP#100 SP-230471 4300 1 F N3IWF selection for emergency services for UE not equipped with valid SNPN credentials 18.2.0 2023-06 SP#100 SP-230451 4302 1 B Provisioning Satellite Coverage Availability to the AMF 18.2.0 2023-06 SP#100 SP-230478 4306 1 B Support for 5G VN group with multiple SMF(Set)s 18.2.0 2023-06 SP#100 SP-230478 4313 1 B KI#4 implementation of cross-SMF VN group communication 18.2.0 2023-06 SP#100 SP-230478 4314 1 F KI#5 correction on the QoS support for UE with multiple groups 18.2.0 2023-06 SP#100 SP-230469 4318 1 B DCCF Discovery principle enhancements for DCCF relocation in TS 23.501 18.2.0 2023-06 SP#100 SP-230497 4322 9 B EN resolving for KI#8 Except TSCAC and clarifications on AF inputs 18.2.0 2023-06 SP#100 SP-230484 4326 - F Solve the EN about handling of the PEMC in 5GC in relation with PIN 18.2.0 2023-06 SP#100 SP-230484 4327 1 F Solve the EN about PIN deletion, activation and deactivation 18.2.0 2023-06 SP#100 SP-230459 4330 1 F Clarification on Redundant Steering Mode 18.2.0 2023-06 SP#100 SP-230459 4342 - F Clarification of RTT measurement for RSM 18.2.0 2023-06 SP#100 SP-230456 4351 5 F Clarification on N3IWF/TNGF selection to support of S-NSSAI needed by UE 18.2.0 2023-06 SP#100 SP-230473 4354 3 C Explicit subscription to NSSF for network slice instance replacement 18.2.0 2023-06 SP#100 SP-230496 4367 1 B Open issue resolutions for MBSR support 18.2.0 2023-06 SP#100 SP-230493 4370 1 C Support of provisioning periodicity set 18.2.0 2023-06 SP#100 SP-230469 4372 C Updates for registration and discovery for FL entity 18.2.0 2023-06 SP#100 SP-230461 4376 3 B Update supporting Edge Computing 18.2.0 2023-06 SP#100 SP-230490 4377 1 F Add FQDN in Traffic Detection Information 18.2.0 2023-06 SP#100 SP-230495 4378 1 B Considering capability of UPF event exposure during UPF discovery 18.2.0 2023-06 SP#100 SP-230461 4381 1 B KI#1 V-SMF selection enhancement to support HR-SBO 18.2.0 2023-06 SP#100 SP-230497 4383 11 B Resolve ENs for support of PDU Set handling 18.2.0 2023-06 SP#100 SP-230479 4390 2 A Clarification on IAB Authorization 18.2.0 2023-06 SP#100 SP-230496 4391 3 B Update of MBSR Configuration 18.2.0 2023-06 SP#100 SP-230495 4404 1 B Updates on TSC management information 18.2.0 2023-06 SP#100 SP-230457 4408 4 B NEF capability for the new AIML service 18.2.0 2023-06 SP#100 SP-230478 4410 1 B KI#1: Other Group Attributes 18.2.0 2023-06 SP#100 SP-230478 4411 1 B KI#1: QoS for a group 18.2.0 2023-06 SP#100 SP-230478 4413 1 B KI#5: Reference Correction for Group QoS 18.2.0 2023-06 SP#100 SP-230486 4415 1 F Corrections and alignments of SFC terminology 18.2.0 2023-06 SP#100 SP-230452 4422 - F Clarification of local switch via UPF on GEO satellites 18.2.0 2023-06 SP#100 SP-230471 4424 - F Clarification on the onboarding indication 18.2.0 2023-06 SP#100 SP-230457 4427 3 F Clarifications on the UE member selection assistance functionality 18.2.0 2023-06 SP#100 SP-230469 4428 1 B Add NWDAF services and Reference point between two NWDAFs for roaming case 18.2.0 2023-06 SP#100 SP-230469 4430 - B Update of ADRF services 18.2.0 2023-06 SP#100 SP-230459 4431 1 B Clarifications the Redundant Steering Mode for GBR SDF 18.2.0 2023-06 SP#100 SP-230473 4442 1 B Hierarchical NSAC Architecture for EPS counting 18.2.0 2023-06 SP#100 SP-230473 4443 3 B Network control of the slice usage 18.2.0 2023-06 SP#100 SP-230495 4445 1 B Support of NAT exposure aligned with TS 23.502 18.2.0 2023-06 SP#100 SP-230461 4447 - D Support fo Edge Computing DNAI mapping update 18.2.0 2023-06 SP#100 SP-230484 4450 4 B Support QoS management for PIN 18.2.0 2023-06 SP#100 SP-230459 4457 1 B Determining the ATSSS capabilities of a MA PDU Session when the UE supports MPQUIC 18.2.0 2023-06 SP#100 SP-230459 4459 1 B Associating a QUIC connection with a QoS flow 18.2.0 2023-06 SP#100 SP-230470 4461 1 A Correction on maximum number of PVS IP address(es) and/or PVS FQDN(s) allowed to be provided to the UE 18.2.0 2023-06 SP#100 SP-230476 4470 1 B UE Policy Association handling during EPS to 5GS mobility with N26 18.2.0 2023-06 SP#100 SP-230457 4473 4 F 5QI for AIML services 18.2.0 2023-06 SP#100 SP-230493 4475 1 B Remove the EN on supporting TSN TN 18.2.0 2023-06 SP#100 SP-230490 4476 1 F Clarification related to LADN PDU session. 18.2.0 2023-06 SP#100 SP-230452 4478 1 B Remove ENs for QoS monitoring on dynamic satellite backhaul 18.2.0 2023-06 SP#100 SP-230497 4486 1 F PDU Set Importance spanning across QoS Flows 18.2.0 2023-06 SP#100 SP-230473 4487 1 B Updates on S-NSSAI Location Availability information 18.2.0 2023-06 SP#100 SP-230473 4488 3 B Storage of S-NSSAI validity time information 18.2.0 2023-06 SP#100 SP-230495 4490 3 F Update the description of reporting suggestion information 18.2.0 2023-06 SP#100 SP-230481 4491 1 F MPS when access to 5GC is WLAN corrections 18.2.0 2023-06 SP#100 SP-230484 4492 7 F PIN communication definition 18.2.0 2023-06 SP#100 SP-230497 4493 3 B Introduction of a new standard SST for Extended Reality and Media Services 18.2.0 2023-06 SP#100 SP-230483 4499 4 F CN based MT communication capability 18.2.0 2023-06 SP#100 SP-230475 4500 7 B Introduction of the Support of Counting of UEs with at least one PDU sessions in the 5GS option 1 18.2.0 2023-06 SP#100 SP-230497 4503 1 C Update for network exposure for XR services 18.2.0 2023-06 SP#100 SP-230497 4506 1 B Update about the Packet Delay Variation description and add PDV in QoS monitoring parameters 18.2.0 2023-06 SP#100 SP-230478 4510 1 F Resolving the ENs on the Provisioning and monitoring for a group 18.2.0 2023-06 SP#100 SP-230478 4511 1 F Clarification on the group-MBR 18.2.0 2023-06 SP#100 SP-230493 4514 4 F Clarification on the TSCTSF handling when it receives the time sync request from AF and time sync subscription from UDM 18.2.0 2023-06 SP#100 SP-230497 4516 1 C The update of Policy control enhancements to support multi-modal services 18.2.0 2023-06 SP#100 SP-230497 4527 8 B Update TS23.501 for PDU Set and PDU Handling 18.2.0 2023-06 SP#100 SP-230497 4529 4 B PCF provides the Periodicity to SMF via PCC rules for resolving the EN for KI#8 18.2.0 2023-06 SP#100 SP-230457 4530 - B Service Experience filtering criteria in assistance to UE member selection 18.2.0 2023-06 SP#100 SP-230484 4535 1 F Editorial change for the PIN 18.2.0 2023-06 SP#100 SP-230478 4541 1 B Update to Annex O to correct referenced clause number and add an optional condition for setup of the QoS flow 18.2.0 2023-06 SP#100 SP-230719 4553 5 C Creating an RA when a Slice is Partially Supported in the RA 18.2.0 2023-06 SP#100 SP-230485 4555 - B Support of SL Positioning 18.2.0 2023-06 SP#100 SP-230457 4565 1 F 23.501 - Member UE terminology update 18.2.0 2023-06 SP#100 SP-230483 4569 2 F Correction for Asynchronous Type Communication for CN based MT communication handling 18.2.0 2023-06 SP#100 SP-230476 4570 2 B Handling UE policy association when UE registered over both 3GPP and Non-3GPP access 18.2.0 2023-06 SP#100 SP-230461 4571 2 B NEF function update 18.2.0 2023-06 SP#100 SP-230484 4572 2 B PIN traffic routing support 18.2.0 2023-06 SP#100 SP-230484 4573 3 B PIN general principles 18.2.0 2023-06 SP#100 SP-230493 4580 - F Clarifying the use of TSS information in UMIC 18.2.0 2023-06 SP#100 SP-230493 4581 1 F Parameters for AF Request Authorization 18.2.0 2023-06 SP#100 SP-230473 4584 2 C Resolving open issues for Network Slice Area of Service 18.2.0 2023-06 SP#100 SP-230473 4585 2 C Target NSSAI configuration considering Partial Network Slice support in a Registration Area 18.2.0 2023-06 SP#100 SP-230473 4586 2 C Number of S-NSSAIs in Partially Allowed NSSAI 18.2.0 2023-06 SP#100 SP-230497 4587 2 F Clarification on the usage of TSCAI for XRM services 18.2.0 2023-06 SP#100 SP-230469 4589 1 C Clarification for NWDAF in roaming architecture 18.2.0 2023-06 SP#100 SP-230469 4590 2 C Clarification of RE-NWDAF discovery 18.2.0 2023-06 SP#100 SP-230457 4591 2 B NEF capability for the new AIML service 18.2.0 2023-06 SP#100 SP-230493 4592 2 B Definition of TL Containers 18.2.0 2023-06 SP#100 SP-230497 4604 2 B QNC Direct Exposure by UPF 18.2.0 2023-06 SP#100 SP-230498 4605 2 B Exposure of RAN measured data rates 18.2.0 2023-06 SP#100 SP-230498 4611 3 B PDU Set QoS handling: non-homogenous support (Alternative 2) 18.2.0 2023-06 SP#100 SP-230484 4614 1 C Resolve ENs on one PIN Served by multiple PDU Sessions 18.2.0 2023-06 SP#100 SP-230484 4621 1 B Informative annex on PIN traffic routing 18.2.0 2023-06 SP#100 SP-230457 4622 - B Update to UE member selection assistance functionality for application operation 18.2.0 2023-06 SP#100 SP-230493 4636 3 C Update on Periodicity Range 18.2.0 2023-06 SP#100 SP-230461 4638 2 F Nnef service update on multiple SMF coordination 18.2.0 2023-06 SP#100 SP-230473 4651 1 B Support of network slice replacement for handover 18.2.0 2023-06 SP#100 SP-230451 4658 2 B Completion of Support discontinuous coverage 18.2.0 2023-06 SP#100 SP-230490 4659 2 F Transfer of emergency PDU session from non-3GPP to 3GPP access 18.2.0 2023-06 SP#100 SP-230492 4666 1 B 23.501 - Spending Limits for AM and UE Policies in the 5GC 18.2.0 2023-06 SP#100 SP-230496 4669 1 B Open issue resolutions for MBSR support 18.2.0 2023-06 SP#100 SP-230496 4670 3 B MBSR registration and authorization support 18.2.0 2023-06 SP#100 SP-230451 4685 3 B Discontinuous coverage reporting 18.2.0 2023-06 SP#100 SP-230461 4686 2 B Common EAS/DNAI determination for a set of UEs 18.2.0 2023-06 SP#100 SP-230461 4688 - F SMF determining target AF ID 18.2.0 2023-06 SP#100 - - - - MCC correction to table 7.2.8-1 for reference to Nnef_TrafficCorrelation_Notify clause in 23.502 18.2.1 2023-07 SP#100 - 4238 - F MCC correction to add missing bullet and Editor's note in clause 5.30.2.12 18.2.2 2023-09 SP#101 SP-230849 4582 5 F NG-RAN resource usage for Alternative S-NSSAI 18.3.0 2023-09 SP#101 SP-230859 4647 3 F Capability signalling limitation for Reflective QoS 18.3.0 2023-09 SP#101 SP-230831 4695 1 A Update of subscribed NSSAI when UE is not registered in network 18.3.0 2023-09 SP#101 SP-230844 4696 3 D Updates to application AI/ML assistance functionality descriptions related to Member UE selection 18.3.0 2023-09 SP#101 SP-230847 4699 1 F Corrections on NEF(PFDF) support NWDAF-assisted application detection 18.3.0 2023-09 SP#101 SP-230858 4700 2 F Add support for UPF selection criteria in context of XRM 18.3.0 2023-09 SP#101 SP-230838 4702 - A Replacing obsoleted RFC related to DHCPv6 with RFC 8415 18.3.0 2023-09 SP#101 SP-230859 4709 1 F Relaxation of 5QI delay requirements for first packets should also apply for RRC-INACTIVE mode. 18.3.0 2023-09 SP#101 SP-230849 4717 4 F Resolving open issues related to RAN resoruces handling in KI#1 18.3.0 2023-09 SP#101 SP-230850 4719 3 F Clarification of the discovery and seletion of NSACF 18.3.0 2023-09 SP#101 SP-230836 4721 - F Move PMIC and UMIC into Annex 18.3.0 2023-09 SP#101 SP-230858 4723 3 F PCC support for ECN marking for L4S 18.3.0 2023-09 SP#101 SP-230856 4727 2 F Clarification on the support for TSCTSF subscribing to AMF notifications for TRS 18.3.0 2023-09 SP#101 SP-230854 4733 2 F Correction on description about PEGC 18.3.0 2023-09 SP#101 SP-230849 4741 2 F UP resource deactivation when the UE moves outside the area of slice availability 18.3.0 2023-09 SP#101 SP-230858 4747 3 F Clarification for GBR and non-GBR support of PDU set QoS Parameters 18.3.0 2023-09 SP#101 SP-230859 4748 1 F General corrections and alignment for TS23.501 18.3.0 2023-09 SP#101 SP-230848 4750 2 F Alt. 1 for the equivalent SNPN used by the UE for Localized Services 18.3.0 2023-09 SP#101 SP-230854 4755 3 F PIN direct and indirect communication definition correction 18.3.0 2023-09 SP#101 SP-230854 4761 2 F Make PIN ID unique in PLMN 18.3.0 2023-09 SP#101 SP-230845 4767 3 F Meaning of availability for 3GPP access 18.3.0 2023-09 SP#101 SP-230846 4769 1 F Service correction related to traffic correlation 18.3.0 2023-09 SP#101 SP-230853 4770 1 F Provision of eDRX for RRC_INACTIVE with PTW 18.3.0 2023-09 SP#101 SP-230857 4772 2 F CAG application for MBSR 18.3.0 2023-09 SP#101 SP-230854 4773 3 F PIN description correction 18.3.0 2023-09 SP#101 SP-230833 4775 - A Removal of Editor's note for NTN tracking area handling 18.3.0 2023-09 SP#101 SP-230845 4777 2 F ATSSS_Ph3 Enhanced Considerations of MPQUIC Multi-layer Stack Parameter Settings & Logics 18.3.0 2023-09 SP#101 SP-230848 4784 1 F Method for exchange info to determine SNPN selection 18.3.0 2023-09 SP#101 SP-230845 4791 - F Clarification on non-3GPP path switching capability when a UE is registered to different PLMNs over 3GPP and non-3GPP accesses 18.3.0 2023-09 SP#101 SP-230847 4798 2 F Interoperability Indicator for NWDAF discovery and selection 18.3.0 2023-09 SP#101 SP-230837 4817 1 A PLMN list for NSWO in roaming scenario 18.3.0 2023-09 SP#101 SP-230846 4819 - F clarification on Subscriber category in AF request 18.3.0 2023-09 SP#101 SP-230859 4829 3 F Update to Network Triggered Service Request for UE in CM_IDLE with Connection Suspend 18.3.0 2023-09 SP#101 SP-230854 4832 3 F Terminology and specification of functinalties not applicable to PIN. 18.3.0 2023-09 SP#101 SP-230856 4836 - F Adjust AoI 18.3.0 2023-09 SP#101 SP-230850 4839 2 F Clarifications on NSAC for maximum number of UEs with at least one PDU SessionPDN Connection 18.3.0 2023-09 SP#101 SP-230858 4844 3 F Corrections on Protocol Description 18.3.0 2023-09 SP#101 SP-230859 4848 1 F UE Mobility Reference 18.3.0 2023-09 SP#101 SP-230846 4849 1 F Selection of Common DNAI 18.3.0 2023-09 SP#101 SP-230835 4852 1 A Clarification on eDRX support for power saving enhancement 18.3.0 2023-09 SP#101 SP-230841 4854 4 F Clarify on Discontinuous Coverage Support negotiation 18.3.0 2023-09 SP#101 SP-230845 4856 1 F Editorial correction on ATSSS architecture 18.3.0 2023-09 SP#101 SP-230849 4857 4 F Downlink packet handling for UE when outside of slice support area 18.3.0 2023-09 SP#101 SP-230846 4858 - F Update on NEF functionality 18.3.0 2023-09 SP#101 SP-230856 4859 2 F Updates on timing synchronization status reporting 18.3.0 2023-09 SP#101 SP-230842 4861 1 F QoS monitoring 18.3.0 2023-09 SP#101 SP-230846 4862 3 F Clarification and editorial on the AF request influence on traffic routing for set of UEs 18.3.0 2023-09 SP#101 SP-230845 4864 - F Clarifications to the Redundant Steering Mode 18.3.0 2023-09 SP#101 SP-230858 4869 2 F Update on support of PDU Set handling 18.3.0 2023-09 SP#101 SP-230847 4876 2 F Clarification on NWDAF functionalities and NF profile in TS 23.501 18.3.0 2023-09 SP#101 SP-230856 4887 2 F Clarification for time synchronization service monitoring 18.3.0 2023-09 SP#101 SP-230859 4891 2 F Further clarification on transfer of emergency PDU session from non-3GPP to 3GPP access 18.3.0 2023-09 SP#101 SP-230838 4893 2 A Aligning secure DNS with SA3 specifications 18.3.0 2023-09 SP#101 SP-230858 4907 4 F PDU Set QoS handling: Race conditions at mobility from supporting to non-supporting gNB 18.3.0 2023-09 SP#101 SP-230859 4920 1 F NSAC back-off timer correction 18.3.0 2023-12 SP#102 SP-231260 4350 4 F Clarification on the list of TAs associated with S-NSSAI partially rejected in the RA 18.4.0 2023-12 SP#102 SP-231260 4480 5 F PDU session inactivity timer for MAPDU session 18.4.0 2023-12 SP#102 SP-231260 4631 8 F Handling of rejected S-NSSAI from the NSSF by AMF:KI#5 18.4.0 2023-12 SP#102 SP-231362 4649 6 F Clean Up of Hierarchical NSAC Architecture 18.4.0 2023-12 SP#102 SP-231249 4689 3 F Unavailability period EPC interworking aspects 18.4.0 2023-12 SP#102 SP-231263 4724 3 F Adding 'URSP delivery over EPS' capability in PCF profile in NRF (23.501) 18.4.0 2023-12 SP#102 SP-231260 4740 4 F PDU Session management when the UE is outside the area of slice support or availability 18.4.0 2023-12 SP#102 SP-231234 4744 7 B PDU Set based QoS Handling for uplink transmission 18.4.0 2023-12 SP#102 SP-231769 4749 8 F Network Slice usage control clarification 18.4.0 2023-12 SP#102 SP-231269 4760 4 F Enabling PEMC manage PIN via UPF local switch 18.4.0 2023-12 SP#102 SP-231269 4762 3 F Correction to SMF behaviour for non-3GPP delay budget 18.4.0 2023-12 SP#102 SP-231267 4771 4 B Support of RRC_INACTIVE with MT-SDT 18.4.0 2023-12 SP#102 SP-231248 4781 4 F Handling of EPS interworking due to NS-AoS 18.4.0 2023-12 SP#102 SP-231260 4783 2 F Partially Allowed NSSAI and S-NSSAIs used to determine RFSP 18.4.0 2023-12 SP#102 SP-231259 4785 2 D eNPN_Ph2 general clean up 18.4.0 2023-12 SP#102 SP-231259 4786 3 F SNPN N3WIF FQDN terminology alignment with stage 3 18.4.0 2023-12 SP#102 SP-231258 4788 3 F Add FL capability and ML model training related services 18.4.0 2023-12 SP#102 SP-231259 4803 2 F Clarification on NAI format in NSWO scenario 18.4.0 2023-12 SP#102 SP-231277 4807 3 F RT latency control and RT delay exposure for XR data flow 18.4.0 2023-12 SP#102 SP-231254 4813 3 F Clarifications on redundant steering mode for GBR QoS Flow 18.4.0 2023-12 SP#102 SP-231259 4818 1 F Clarification on SNPN list for NSWO in CH scenario 18.4.0 2023-12 SP#102 SP-231260 4850 4 F Clarification for temporary slices having validity time information 18.4.0 2023-12 SP#102 SP-231259 4865 2 F Correction to AMF selection for SNPN onboarding 18.4.0 2023-12 SP#102 SP-231277 4871 3 F Clarifications of policy control enhancements for multi-modal services 18.4.0 2023-12 SP#102 SP-231238 4910 2 A Add missing gate control information 18.4.0 2023-12 SP#102 SP-231248 4921 1 F QoS Monitoring Report clarification 18.4.0 2023-12 SP#102 SP-231248 4922 1 F Dual Connectivity terminology fixes and removal of obsolete Editor's Note 18.4.0 2023-12 SP#102 SP-231259 4933 2 D Clarification on Stand-alone Non-Public Networks 18.4.0 2023-12 SP#102 SP-231275 4935 2 F Clarification on Data exposure via SBI 18.4.0 2023-12 SP#102 SP-231275 4937 3 F Update Architecture for UPF SBI interface 18.4.0 2023-12 SP#102 SP-231275 4942 4 F Clarification on SMF and UPF functional description for UPF event exposure services 18.4.0 2023-12 SP#102 SP-231277 4943 1 F Correction on network exposure of estimated bandwidth 18.4.0 2023-12 SP#102 SP-231259 4947 2 F Clarifications for Enabling Access to Localized Services 18.4.0 2023-12 SP#102 SP-231616 4949 5 F Removing the Editor's Note about the interaction between NAS and AS 18.4.0 2023-12 SP#102 SP-231276 4950 1 F Providing both ULI and Additional ULI to other NFs 18.4.0 2023-12 SP#102 SP-231273 4955 4 F Correction on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN) 18.4.0 2023-12 SP#102 SP-231277 4957 3 F Correcting the Description of the N6 Traffic Parameter Measurement Report 18.4.0 2023-12 SP#102 SP-231267 4960 1 F NGAP DL Data Notification Message update 18.4.0 2023-12 SP#102 SP-231269 4961 3 F PIN ID clarification 18.4.0 2023-12 SP#102 SP-231276 4962 2 F MBSR authorization handling update 18.4.0 2023-12 SP#102 SP-231265 4964 2 F IAB authorization handling correction 18.4.0 2023-12 SP#102 SP-231264 4965 2 F Corrections to QoS provisioning for a group 18.4.0 2023-12 SP#102 SP-231250 4969 2 F Updates of functional description for 5G Satellite Backhaul 18.4.0 2023-12 SP#102 SP-231264 4970 1 F Updates of functional description for LADN per DNN and S-NSSAI 18.4.0 2023-12 SP#102 SP-231250 4975 1 F Clarifications to local switching via UPF deployed on satellite 18.4.0 2023-12 SP#102 SP-231250 4976 2 F Correction to Edge Computing via UPF deployed on satellite 18.4.0 2023-12 SP#102 SP-231258 4980 1 F Updates for registration and discovery for FL entity 18.4.0 2023-12 SP#102 SP-231259 4981 3 F Congestion handling when a UE accesses an SNPN for Localized Services 18.4.0 2023-12 SP#102 SP-231259 4987 3 F Adding architectures on supporting authentication for NSWO using CH with AAA Server via 5GC 18.4.0 2023-12 SP#102 SP-231259 4988 - F Correction the interface in the NSWO architecture for SNPN 18.4.0 2023-12 SP#102 SP-231264 4989 1 F LADN (DNN+S-NSSAI) provisioning for individual subscriber and SMF behaviour 18.4.0 2023-12 SP#102 SP-231264 4993 2 F Change of PDU Session Type correction 18.4.0 2023-12 SP#102 SP-231275 5001 3 F Corrections to UPF Services 18.4.0 2023-12 SP#102 SP-231275 5002 3 F UPF Data Collection with QoS Monitoring event 18.4.0 2023-12 SP#102 SP-231277 5012 5 F Clarification on scenarios for enabling/disabling downlink PDU Set based Handling 18.4.0 2023-12 SP#102 SP-231255 5016 1 F UPF behaviour alignment for DetNet 18.4.0 2023-12 SP#102 SP-231273 5024 7 F Clarification on the support for AMF discovery at the TSCTSF 18.4.0 2023-12 SP#102 SP-231277 5026 2 F Corrections of XRM-specific clauses 18.4.0 2023-12 SP#102 SP-231264 5034 2 F Provisioning of LADN information 18.4.0 2023-12 SP#102 SP-231260 5036 5 F Addressing EN on Downlink packet handling for UE with CM-IDLE mode when outside of slice support area 18.4.0 2023-12 SP#102 SP-231273 5039 4 F Clarifications of Event ID broadcast in SIB9 18.4.0 2023-12 SP#102 SP-231248 5041 3 F Support of NR coverage enhancements 18.4.0 2023-12 SP#102 SP-231248 5043 2 F Relaxation of 5QI delay requirements for first packets should also apply for RRC-INACTIVE mode and for other best effort 5QIs 18.4.0 2023-12 SP#102 SP-231239 5054 1 A Addressing packet loss and first packet delay for public safety UEs 18.4.0 2023-12 SP#102 SP-231248 5062 1 F Move text on providing a back-off timer to the UE during NSAC for maximum number of PDU Sessions 18.4.0 2023-12 SP#102 SP-231259 5063 2 F ESNPN during registration for onboarding 18.4.0 2023-12 SP#102 SP-231259 5064 2 F Correction on automatic SNPN selection for localized service 18.4.0 2023-12 SP#102 SP-231259 5065 - F Clarification on LADN support in SNPN 18.4.0 2023-12 SP#102 SP-231276 5067 1 F Clarification on delay in deregistration procedure 18.4.0 2023-12 SP#102 SP-231263 5070 3 F URSP delivery via EPS 18.4.0 2023-12 SP#102 SP-231253 5073 2 F Removal of Editor's Note on charging of AI/ML traffic 18.4.0 2023-12 SP#102 SP-231277 5080 4 F Support of PDU Set handling on a per direction basis 18.4.0 2023-12 SP#102 SP-231269 5083 1 F AF for PIN description update 18.4.0 2023-12 SP#102 SP-231269 5084 - F Non-3GPP Delay clarification 18.4.0 2023-12 SP#102 SP-231276 5085 3 F MBSR authorization area restriction 18.4.0 2023-12 SP#102 SP-231253 5087 - F R18 AIMLsys_KI7_23501 CR for clarifying AF filtering criteria 18.4.0 2023-12 SP#102 SP-231254 5091 1 F Clarification on Suspend and Resume Traffic Duplication 18.4.0 2023-12 SP#102 SP-231263 5096 - F Clarification on URSP delivery in EPS 18.4.0 2023-12 SP#102 SP-231253 5103 1 F Clarification on the Member UE selection 18.4.0 2023-12 SP#102 SP-231248 5104 1 F Spending Limits for AM and UE Policies in the 5GC 18.4.0 2023-12 SP#102 SP-231258 5105 2 F Correct NWDAF discovery principles 18.4.0 2023-12 SP#102 SP-231260 5109 3 F Further clarification of NSAC 18.4.0 2023-12 SP#102 SP-231263 5110 2 F Providing URSP support indication in EPS in PDN connectivity request 18.4.0 2023-12 SP#102 SP-231263 5111 2 F Clarification on PCO support 18.4.0 2023-12 SP#102 SP-231273 5115 3 F Alignment with RAN3 on the network timing synchronization status information 18.4.0 2023-12 SP#102 SP-231237 5121 1 A Alignment of how Allowed NSSAI can be determined 18.4.0 2023-12 SP#102 SP-231254 5123 3 F Clarify MRU handling for non-3GPP access path switching 18.4.0 2023-12 SP#102 SP-231258 5125 2 F Correction for alignment with TS 23.288 regarding ML Model interoperability per Analytics ID 18.4.0 2023-12 SP#102 SP-231512 5126 5 F Handling of Alternative S-NSSAI 18.4.0 2023-12 SP#102 SP-231239 5128 1 A Requesting Configured NSSAI from NSSF 18.4.0 2023-12 SP#102 SP-231260 5137 1 F Clarification on slice replacement from Alternative S-NSSAI to original S-NSSAI 18.4.0 2023-12 SP#102 SP-231249 5141 2 F Corrections to Support of Unavailability Period and Overload control 18.4.0 2023-12 SP#102 SP-231253 5142 1 F Clarification on the Member UE selection assistance functionality for application operation 18.4.0 2023-12 SP#102 SP-231260 5156 4 F Clarification on Network Slice Replacement 18.4.0 2023-12 SP#102 SP-231262 5162 3 F Clarification on eNSAC Option 1 18.4.0 2023-12 SP#102 SP-231249 5163 2 F Update on support of discontinuous coverage for satellite access 18.4.0 2023-12 SP#102 SP-231249 5164 - F Discontinuous coverage overload control priority users term alignment 18.4.0 2023-12 SP#102 SP-231260 5170 4 F Clarifications about the Alternative S-NSSAI subject to NSSAA 18.4.0 2023-12 SP#102 SP-231260 5172 3 F Update of definition of NSAC Service area. 18.4.0 2023-12 SP#102 SP-231248 5185 1 F UE 5GSM capability indication for supporting secondary auth over EPC 18.4.0 2023-12 SP#102 SP-231249 5187 - F Satellite RAT Types in TS 23.501 18.4.0 2023-12 SP#102 SP-231239 5195 2 A Correction to Notification Endpoint 18.4.0 2023-12 SP#102 SP-231256 5203 3 F KI#1 Alignment and correction on PLMN IDs in AF request 18.4.0 2023-12 SP#102 SP-231248 5207 2 F Clarifying the ownership of data in UDSF 18.4.0 2023-12 SP#102 SP-231276 5208 1 F Remove the editor's note for MBSR authorization indication 18.4.0 2023-12 SP#102 SP-231767 4736 9 F Update for QoS monitoring and network exposure 18.4.0 2023-12 SP#102 SP-231763 5008 7 F Correction and clarification of the Protocol Description definition 18.4.0 2023-12 SP#102 SP-231765 5014 6 F Clarification on QoS flow mapping and service data flow 18.4.0 2023-12 SP#102 SP-231766 5175 6 F Clarification of the Unmarked PDUs with SN Offset and PSI Value 18.4.0 2023-12 SP#102 SP-231762 5186 3 F Incorrect reference in clause 5.15.17 for procedure for RAN initiated PDU session release 18.4.0 2024-03 SP#103 SP-240101 4489 8 F Registration status after S-NSSAI removal based on S-NSSAI validity time information 18.5.0 2024-03 SP#103 SP-240101 4583 5 F Congestion handling with Alternative S-NSSAI 18.5.0 2024-03 SP#103 SP-240086 4660 6 A Non-Allowed areas clarifications related to MPS 18.5.0 2024-03 SP#103 SP-240113 4812 7 F Corrections for traffic characteristics parameters in Alternative QoS Profile 18.5.0 2024-03 SP#103 SP-240093 4929 1 F Removing editor's note on Prefixed N3IWF FQDN format 18.5.0 2024-03 SP#103 SP-240085 4992 5 A Support of QMC configuration information 18.5.0 2024-03 SP#103 SP-240115 5011 8 F Corrections to remove Nnef_UEId Service restrictions 18.5.0 2024-03 SP#103 SP-240089 5032 4 F Updated description of UE Location verification for NTN 18.5.0 2024-03 SP#103 SP-240113 5081 2 F Correction on Congestion Information Exposure 18.5.0 2024-03 SP#103 SP-240077 5082 3 F Correction of UPF reporting of QoS Monitoring packet delay 18.5.0 2024-03 SP#103 SP-240098 5095 2 F Clarification on DL Session AMBR for Offloading in HR-SBO sessions 18.5.0 2024-03 SP#103 SP-240110 5106 2 F Clarification on AoI of time synchronization service 18.5.0 2024-03 SP#103 SP-240110 5122 1 F Correction of additional parameters inside AF Request Authorization 18.5.0 2024-03 SP#103 SP-240191 5145 1 F Corrections for NWDAF functionality description 18.5.0 2024-03 SP#103 SP-240102 5179 5 F Clarifications related to the scenario when the PDN connection handlig the UE Policy Container is released. 18.5.0 2024-03 SP#103 SP-240110 5181 2 F KI#5 Corrections on Proactive RAN Feedback and TSN enabled TN 18.5.0 2024-03 SP#103 SP-240107 5182 2 F Mega CR for editorial modification 18.5.0 2024-03 SP#103 SP-240089 5202 2 F UE capability for network verified location 18.5.0 2024-03 SP#103 SP-240090 5214 1 F Correction for multiple broadcast TA reporting in NR Satellite access 18.5.0 2024-03 SP#103 SP-240113 5215 1 F Clarification on periodicity change from AF 18.5.0 2024-03 SP#103 SP-240102 5217 1 F PDN Selection for URSP delivery in EPS 18.5.0 2024-03 SP#103 SP-240112 5220 7 F MBSR mobility 18.5.0 2024-03 SP#103 SP-240101 5221 1 F Clarification on Slice Replacement 18.5.0 2024-03 SP#103 SP-240113 5222 1 F Packet filter with DSCP and ECN 18.5.0 2024-03 SP#103 SP-240113 5224 3 F PSER and PSDB supersede the PER and PDB per direction 18.5.0 2024-03 SP#103 SP-240110 5225 4 F Correction on CN PDB configured in NG-RAN 18.5.0 2024-03 SP#103 SP-240091 5226 1 F Clarification on satellite backhaul category change indication 18.5.0 2024-03 SP#103 SP-240113 5228 3 F Protocol Descriptions for UL and DL traffic 18.5.0 2024-03 SP#103 SP-240136 5229 1 F Spending Limits for AM and UE Policies in the 5GC 18.5.0 2024-03 SP#103 SP-240096 5230 1 F Clarify MRU handling for non-3GPP access path switching when UE has only one PDU Session 18.5.0 2024-03 SP#103 SP-240101 5233 6 F Clarifications on PDU Sessions due to Network Slice Replacement 18.5.0 2024-03 SP#103 SP-240095 5235 1 D Cleaning up the term of RFSP Index in Use Validity Time 18.5.0 2024-03 SP#103 SP-240104 5237 1 F LADN provisioning when there is existing PDU session 18.5.0 2024-03 SP#103 SP-240104 5238 1 F Clarification on the temporal invalidity conditions 18.5.0 2024-03 SP#103 SP-240110 5239 2 F CQRCI check issue when there are both AF requests and subscriptions 18.5.0 2024-03 SP#103 SP-240110 5240 1 F Clarification on the UE capability and re-connection indication 18.5.0 2024-03 SP#103 SP-240110 5241 1 F Correction on InterfaceConfiguration and InterfaceCapability 18.5.0 2024-03 SP#103 SP-240101 5243 5 F Clarification on subscription retrieval during slice replacement 18.5.0 2024-03 SP#103 SP-240113 5245 3 F Corrections of XRM related clauses 18.5.0 2024-03 SP#103 SP-240110 5246 5 F TSCTSF subscribing to RAN TSS based on list of TAs, correction to ASTI without AF request 18.5.0 2024-03 SP#103 SP-240110 5248 1 F Updating TSCAI and TSCAC to Traffic Assistance Information 18.5.0 2024-03 SP#103 SP-240112 5250 1 F Corrections on mobile IAB-DU's TAC provisioning 18.5.0 2024-03 SP#103 SP-240100 5252 1 F Clarification/Alignment on usage of Decorated NAI for 5G-NSWO in case of SNPNs. 18.5.0 2024-03 SP#103 SP-240100 5253 - F Correction on NSSAAF Selection in case of SNPN 18.5.0 2024-03 SP#103 SP-240096 5261 1 F Clarifications on interworking with EPS 18.5.0 2024-03 SP#103 SP-240100 5262 1 F Clarifications on network re-selection for SNPN for accessing Localized Services 18.5.0 2024-03 SP#103 SP-240100 5263 1 F Correction on validity information for SNPN 18.5.0 2024-03 SP#103 SP-240100 5264 1 F Correction on validity information for CAG 18.5.0 2024-03 SP#103 SP-240101 5265 7 F Clarification on Network Slice usage control timer 18.5.0 2024-03 SP#103 SP-240113 5267 1 F Modification to the Packet delay variation monitoring 18.5.0 2024-03 SP#103 SP-240115 5273 1 B Update to Support Network Controlled Repeater 18.5.0 2024-03 SP#103 SP-240101 5277 8 F Support of Network Slice Replacement and area restrictions at UE mobility 18.5.0 2024-03 SP#103 SP-240101 5278 1 F Determination of release or deactivation of PDU Session due to S-NSSAI not supported 18.5.0 2024-03 SP#103 SP-240113 5281 1 F Clarifications on non-homogeneous support of PDU set based handling in NG-RAN 18.5.0 2024-03 SP#103 SP-240113 5282 1 F Clarifications on ECN marking for L4S 18.5.0 2024-03 SP#103 SP-240101 5286 3 F Clarification on Allowed NSSAI for network slice replacement 18.5.0 2024-03 SP#103 SP-240101 5291 1 F Network Slice usage control for emergency service 18.5.0 2024-03 SP#103 SP-240101 5292 4 F Clarification on Network based monitoring and enforcement for NS-AoS and partially Allowed NSSAI 18.5.0 2024-03 SP#103 SP-240113 5295 3 F Clarifications on applicability of Protocol Description in PDR for EoDB identification in DL 18.5.0 2024-03 SP#103 SP-240081 5297 1 F Access control for users with eRedcap/Redcap subscriptions 18.5.0 2024-03 SP#103 SP-240096 5299 - F MPQUIC support related corrections 18.5.0 2024-03 SP#103 SP-240084 5301 1 A Handover control for NR-terrestrial to LTE satellite access 18.5.0 2024-03 SP#103 SP-240112 5302 1 F Clarification on mobile IAB indication when establishing RRC connection 18.5.0 2024-03 SP#103 SP-240112 5303 1 F Indication to AMF for MBSR connection release 18.5.0 2024-03 SP#103 SP-240090 5304 1 F Clarification on unavailability period 18.5.0 2024-03 SP#103 SP-240112 5305 - F Clarification on AMF selection 18.5.0 2024-03 SP#103 SP-240098 5310 2 F KI#4 Clarifications on common EAS/DNAI procedure 18.5.0 2024-03 SP#103 SP-240110 5311 3 F Update TSCAI at SMF based on proactive RAN feedback on BAT and periodicity 18.5.0 2024-03 SP#103 SP-240113 5313 2 F Correct the misalignment for congestion exposure and L4S 18.5.0 2024-03 SP#103 SP-240098 5319 1 F Update Network function update of SMF and UPF selection for HR-SBO 18.5.0 2024-03 SP#103 SP-240191 5320 2 F Correction to the FL capability type 18.5.0 2024-03 SP#103 SP-240101 5321 3 F DNN selection for Alternative S-NSSAI 18.5.0 2024-03 SP#103 SP-240110 5327 2 F Corrections to timing synchronization status reporting 18.5.0 2024-03 SP#103 SP-240113 5328 1 F Correction of ECN Marking for L4S by UPF 18.5.0 2024-03 SP#103 SP-240113 5331 4 F Clarification on support of PDU Set based QoS 18.5.0 2024-03 SP#103 SP-240094 5332 2 F Support of 5GC UE level measurements collection 18.5.0 2024-03 SP#103 SP-240191 5334 1 F Alignments for the Accuracy checking capability in TS 23.501 18.5.0 2024-03 SP#103 SP-240113 5339 2 F Incorrect Protocol Description options including SRTP together with RTP Payload Format 18.5.0 2024-03 SP#103 SP-240114 5342 2 F DSCP and ECN within the IP Header 18.5.0 2024-03 SP#103 SP-240114 5343 1 F Max MTU for XR and, for PDU sessions subject to handover from EPS to 5GC 18.5.0 2024-03 SP#103 SP-240110 5344 2 F Clock status indication from RAN to TSCTSF 18.5.0 2024-06 SP#104 SP-240597 4926 5 F Clarification on access dependency of Alternative S-NSSAI 18.6.0 2024-06 SP#104 SP-240591 4951 2 F Clarification on TNGF identifiers 18.6.0 2024-06 SP#104 SP-240602 5204 6 F Operator specific QoS and handling at inter-PLMN mobility 18.6.0 2024-06 SP#104 SP-240600 5254 6 F Clarification on (e)RedCap UE 18.6.0 2024-06 SP#104 SP-240604 5258 3 F Clarification on providing the additional location and time restrictions information to the MBSR IAB-UE 18.6.0 2024-06 SP#104 SP-240593 5322 1 F Corrections on supported Steering Modes for a MA PDU Session 18.6.0 2024-06 SP#104 SP-240597 5326 5 F Distinction between network slice supported and available in an area 18.6.0 2024-06 SP#104 SP-240597 5346 5 F Slice deregistration inactvity timer clarification 18.6.0 2024-06 SP#104 SP-240602 5355 1 F Alignment of NWDAF discovery parameters 18.6.0 2024-06 SP#104 SP-240582 5359 1 A Correction on TSCAI calculation 18.6.0 2024-06 SP#104 SP-240594 5361 3 F Security for EAS discovery procedure via (V-)EASDF 18.6.0 2024-06 SP#104 SP-240602 5362 - F Adding a missing Nudm service (Nudm_UEIdentifier used in 33.503) 18.6.0 2024-06 SP#104 SP-240602 5366 2 F RAT type change impact to AM Policy association 18.6.0 2024-06 SP#104 SP-240598 5368 1 F Corrections on the clause reference and ID mapping 18.6.0 2024-06 SP#104 SP-240602 5369 1 F Clarification on UEs accessing to GERAN/UTRAN over Gn/Gp 18.6.0 2024-06 SP#104 SP-240600 5371 3 F RedCap/eRedCap UE differentiation upon change of radio capabilities 18.6.0 2024-06 SP#104 SP-240589 5372 3 F Unavailability period during initial Registration procedure 18.6.0 2024-06 SP#104 SP-240589 5379 2 F Clarification on Discontinuous coverage for satellite access 18.6.0 2024-06 SP#104 SP-240596 5381 2 F Clarification on location validity information. 18.6.0 2024-06 SP#104 SP-240603 5385 2 F Clarifications for UPF selection 18.6.0 2024-06 SP#104 SP-240602 5386 2 F Update description of UE location verification for NTN 18.6.0 2024-06 SP#104 SP-240600 5388 1 F Activation of DL data size reporting for support of MT-SDT 18.6.0 2024-06 SP#104 SP-240605 5391 1 F Clarification on the TSCAI parameters for XR 18.6.0 2024-06 SP#104 SP-240597 5394 2 F Temporary slice expiry 18.6.0 2024-06 SP#104 SP-240597 5396 2 F Slice area restriction in case of ETSUN or roaming 18.6.0 2024-06 SP#104 SP-240602 5404 2 D 23.501 Cleanup CR 18.6.0 2024-06 SP#104 SP-240607 5356 6 B Network Slicing for Indirect Network Sharing 19.0.0 2024-06 SP#104 SP-240607 5360 2 B The enhanced function in Indirect Network Sharing 19.0.0 2024-06 SP#104 SP-240607 5364 5 B RVAS with target NF selection enhancement. 19.0.0 2024-06 SP#104 SP-240607 5365 2 B Indirect Network Sharing 19.0.0 2024-06 SP#104 SP-240607 5367 2 B ProSe support for NPNs 19.0.0 2024-06 SP#104 SP-240607 5380 6 B Subscription-based routing to a target core network 19.0.0 2024-06 SP#104 SP-240607 5398 2 B Spending Limits for UE Policies in Roaming scenario 19.0.0 2024-06 SP#104 SP-240607 5399 1 B NF discovery and selection by target PLMN 19.0.0 2024-06 SP#104 SP-240607 5402 2 C Support of QoS monitoring capability configuration and transfer within 5GC 19.0.0 2024-09 SP#105 SP-241251 5411 1 A KI#5 correction to reference of IEEE 19.1.0 2024-09 SP#105 SP-241261 5417 1 A Support for NAS SMS over in Disaster Roaming 19.1.0 2024-09 SP#105 SP-241269 5420 2 B Adding the NAT information exposure and Packet Inspection functionality in the UPF NF profile 19.1.0 2024-09 SP#105 SP-241271 5425 1 F Clarification on MFAF Serving area 19.1.0 2024-09 SP#105 SP-241259 5429 1 A Removal of Editor's note on the use of TLS with MPQUIC 19.1.0 2024-09 SP#105 SP-241272 5430 1 F Corrections for NF selection by target PLMN 19.1.0 2024-09 SP#105 SP-241261 5433 3 A Align H-PCF selection with H-SMF selection in 23.501 R19 19.1.0 2024-09 SP#105 SP-241261 5435 1 A Support of a UE registered over both 3GPP and Non-3GPP access 19.1.0 2024-09 SP#105 SP-241417 5441 4 B Support of UPF selection according to the conclusion in FS_UPEAS_Ph2 19.1.0 2024-09 SP#105 SP-241305 5445 4 B Enhancement of getting public UE IP address and port number 19.1.0 2024-09 SP#105 SP-241261 5459 - A Correction on MSISDN exposure 19.1.0 2024-09 SP#105 SP-241265 5463 4 B Local Offloading Policy provisioning 19.1.0 2024-09 SP#105 SP-241272 5465 3 F The correction for Indirect Network Sharing 19.1.0 2024-09 SP#105 SP-241270 5467 3 B MWAB configuration 19.1.0 2024-09 SP#105 SP-241270 5469 2 B Mobility of UEs served by MWAB 19.1.0 2024-09 SP#105 SP-241271 5472 5 F Correction about Default Configured NSSAI 19.1.0 2024-09 SP#105 SP-241252 5474 2 A Subscription of UPF event via I-SMF 19.1.0 2024-09 SP#105 SP-241251 5478 - A Correct to align with RAN for reactive RAN feedback for Burst Arrival Time adaptation 19.1.0 2024-09 SP#105 SP-241251 5480 - A Correction on mapping of the parameters between 5GS and TSN UNI 19.1.0 2024-09 SP#105 SP-241243 5482 3 A Correction NWDAF discovery and selection 19.1.0 2024-09 SP#105 SP-241253 5487 1 A Correction of the reference clause and duplicate description 19.1.0 2024-09 SP#105 SP-241262 5488 2 B Adding 5G Femto support description 19.1.0 2024-09 SP#105 SP-241272 5492 2 B Exposure enhancements for static UE IP address assignment and 5G VN group's User Plane Security Policy 19.1.0 2024-09 SP#105 SP-241247 5495 1 A Access restrictions for satellite access in the context of 5GC-EPC interworking 19.1.0 2024-09 SP#105 SP-241261 5496 1 A Session level priority realization in AMF 19.1.0 2024-09 SP#105 SP-241266 5499 2 B MPS support for Messaging 19.1.0 2024-09 SP#105 SP-241253 5510 - A Clarification on CAG related UE access restriction 19.1.0 2024-09 SP#105 SP-241254 5512 - A Clarification on End of Data Burst Indication 19.1.0 2024-09 SP#105 SP-241270 5521 2 B MWAB definitions and abbreviations 19.1.0 2024-09 SP#105 SP-241244 5531 1 A Handling of the slice deregistration inactivity timer in the inter AMF mobility 19.1.0 2024-09 SP#105 SP-241258 5536 - A Correction on N3IWF selection 19.1.0 2024-09 SP#105 SP-241269 5540 3 B Supporting direct subscription of UPF event exposure using UE's IP address 19.1.0 2024-09 SP#105 SP-241270 5544 2 B Support for Location Service Support of UEs served by MWAB 19.1.0 2024-09 SP#105 SP-241241 5559 2 A Network Slicing handling for EHPLMN case 19.1.0 2024-09 SP#105 SP-241272 5560 3 F Clarification on network slice handling for Indirect Network Sharing 19.1.0 2024-09 SP#105 SP-241270 5561 2 B Control Plane and User Plane Protocol stacks involving the MWAB node 19.1.0 2024-09 SP#105 SP-241269 5565 2 B UPF event exposure during UPF relocation 19.1.0 2024-09 SP#105 SP-241261 5567 - A Correction of PCF related terminology 19.1.0 2024-09 SP#105 SP-241256 5570 1 A Clarification on PRU timer considering start of unavailability period 19.1.0 2024-09 SP#105 SP-241259 5577 1 A Correction of MPQUIC Datagram mode 1 19.1.0 2024-09 SP#105 SP-241272 5580 3 B AMF event exposure for supporting on-demand broadcast of LCS assistant data 19.1.0 2024-09 SP#105 SP-241261 5596 3 B Adding support of Mobile Wireless Access Backhaul in 5GS 19.1.0 2024-09 SP#105 SP-241254 5600 2 A Clarification on Congestion Event Triggered Reporting 19.1.0 2024-09 SP#105 SP-241256 5615 2 A Applying AMF determined unavailability values 19.1.0 2024-09 SP#105 SP-241260 5623 - A Alignment action of EAS IP replacement in SMF and UPF 19.1.0 2024-09 SP#105 SP-241244 5624 1 A PDU Session clarification when the slice is associated with slice restricted area 19.1.0 2024-09 SP#105 SP-241254 5625 - F Corrections of Traffic Detection Information related descriptions 19.1.0 2024-09 SP#105 SP-241244 5626 - A Handling for UE when present in overlapping of non-allowed area and slice location availability area 19.1.0 2024-09 SP#105 SP-241304 5419 2 A Lack of indication of Emergency Service Support over NG 19.1.0 2024-09 SP#105 SP-241308 5627 - A Clarifications on NWDAF serving area 19.1.0 2024-12 SP#106 SP-241488 5636 7 B Introduction of new network function for energy related information, its definition and corresponding Architecture Reference Model 19.2.0 2024-12 SP#106 SP-241485 5622 5 B Support of Regenerative Payload with NG-RAN Node Onboard Satellite 19.2.0 2024-12 SP#106 SP-241485 5583 7 B Support of UE-Satellite-UE communication 19.2.0 2024-12 SP#106 SP-241495 5454 8 B Support of Handling of Headers 19.2.0 2024-12 SP#106 SP-241487 5604 11 B I-SMF selection/insertion based on local offloading allowed indication 19.2.0 2024-12 SP#106 SP-241497 5422 5 B XRM_Ph2 KI#6 L4S support in non-3GPP access 19.2.0 2024-12 SP#106 SP-241497 5711 10 B General description of relaying media related information over N6 using an encapsulation protocol 19.2.0 2024-12 SP#106 SP-241497 5632 10 B Support PDU Set information identification based on MoQ for encrypted XRM traffic 19.2.0 2024-12 SP#106 SP-241497 5728 10 B PDU Set Information Identification for end-to-end encrypted traffic using connect-UDP - architecture part 19.2.0 2024-12 SP#106 SP-241497 5746 10 B Usage of UDP-Option carrying XRM metadata over UDP tunnel for end-to-end encrypted XRM flows 19.2.0 2024-12 SP#106 SP-241497 5784 4 B Support of Data Burst Size provisioning to NG-RAN 19.2.0 2024-12 SP#106 SP-241497 5785 4 B Support of Time to Next Burst provisioning to NG-RAN 19.2.0 2024-12 SP#106 SP-241497 5783 12 B Update for Support differentiated QoS handling for multiplexed media flows 19.2.0 2024-12 SP#106 SP-241496 5685 3 B Support of UE served by a MWAB: QoS aspects 19.2.0 2024-12 SP#106 SP-241486 5661 4 B New analytics for signalling storm mitigation (TS 23.501) 19.2.0 2024-12 SP#106 SP-241496 5686 4 B Support of UE served by a MWAB: network slicing support 19.2.0 2024-12 SP#106 SP-241488 5628 16 B Support of Energy Efficiency and Energy Saving 19.2.0 2024-12 SP#106 SP-241488 5713 3 B KI#3: Enhancement for AF influence on traffic routing with Energy related information 19.2.0 2024-12 SP#106 SP-241488 5714 3 B KI#2: Enhancement for BDT with Energy related information 19.2.0 2024-12 SP#106 SP-241488 5739 11 B KI#2: UE subscription and policy control for energy efficiency and energy saving 19.2.0 2024-12 SP#106 SP-241494 5750 6 B Support of N3GPP device behind UE/5G-RG as concluded in TS 23.700-34 KI#4 19.2.0 2024-12 SP#106 SP-241488 5740 10 B Functional Description of Energy Efficiency Control Functionality 19.2.0 2024-12 SP#106 SP-241503 5764 7 B Support of Slice change based on AF request 19.2.0 2024-12 SP#106 SP-241484 5778 2 C NSSF selection 19.2.0 2024-12 SP#106 SP-241492 5748 6 B HSBO_roaming traffic offloading via session breakout in HPLMN 19.2.0 2024-12 SP#106 SP-241864 5807 10 B NR Femto architecture definition 19.2.0 2024-12 SP#106 SP-241484 5824 2 B Support of LP-WUS Assistance 19.2.0 2024-12 SP#106 SP-241496 5828 1 B MWAB BH PDU session clarification 19.2.0 2024-12 SP#106 SP-241488 5870 2 B KI#1: Energy related information exposure and EIF services 19.2.0 2024-12 SP#106 SP-241497 5407 5 B Leveraging PDU Set QoS information for DSCP marking over N3/N9 in the transport network 19.2.0 2024-12 SP#106 SP-241475 5409 5 A URSP provisioning in EPS support indication at PDU Session Establishment 19.2.0 2024-12 SP#106 SP-241487 5437 10 B Support of L-PSA UPF Selection Considering N6 Delay 19.2.0 2024-12 SP#106 SP-241487 5443 15 B AF request and functionalities enhancement to support N6 delay measurement 19.2.0 2024-12 SP#106 SP-241495 5452 3 B Updates to UPF data exposure for KI#2 direct subscription 19.2.0 2024-12 SP#106 SP-241496 5468 6 B Control of UE access to MWAB 19.2.0 2024-12 SP#106 SP-241496 5471 6 B Emergency services for UEs via a MWAB 19.2.0 2024-12 SP#106 SP-241489 5493 11 B Support for MPQUIC-IP and MPQUIC-E steering functionalities 19.2.0 2024-12 SP#106 SP-241489 5527 5 B Support QoS of proxying IP and Ethernet in HTTP over MPQUIC 19.2.0 2024-12 SP#106 SP-241494 5547 7 B UDR enhancement supporting Device Identifier of non-3GPP Devices connecting behind a UE/5G-RG 19.2.0 2024-12 SP#106 SP-241497 5608 4 B PDU Set handling in non-3GPP accesses 19.2.0 2024-12 SP#106 SP-241486 5630 2 B VFL support during the discovery of NWDAF, NEF, and AF instances 19.2.0 2024-12 SP#106 SP-241468 5648 1 A Correction on PDU Session supporting CIoT 19.2.0 2024-12 SP#106 SP-241496 5650 1 B NAT functionality in the UPF of BH PDU Session 19.2.0 2024-12 SP#106 SP-241495 5657 4 F Corrections of UPF selection 19.2.0 2024-12 SP#106 SP-241471 5664 1 A Add missing MFAF Services 19.2.0 2024-12 SP#106 SP-241482 5667 1 F 5G Femto Hosting Party acting as a CAG owner 19.2.0 2024-12 SP#106 SP-241497 5668 4 B KI#1, Support QoS Notification and AQP 19.2.0 2024-12 SP#106 SP-241496 5687 5 B Support of UE served by a MWAB: Additional ULI 19.2.0 2024-12 SP#106 SP-241969 5683 7 A Clarification on network slice handling for EHPLMN 19.2.0 2024-12 SP#106 SP-241496 5688 5 B Support of UE served by a MWAB: authorization aspects 19.2.0 2024-12 SP#106 SP-241492 5693 2 C Support of VLAN handling information in SM subscription data and DN-AAA 19.2.0 2024-12 SP#106 SP-241482 5694 8 B NR Femto architecture introduction 19.2.0 2024-12 SP#106 SP-241496 5695 3 F MWAB principles and functional entities updates 19.2.0 2024-12 SP#106 SP-241478 5702 - A Non-3GPP QoS Assistance information update 19.2.0 2024-12 SP#106 SP-241468 5705 1 A Missing NRF NF instances for CHF and correction 19.2.0 2024-12 SP#106 SP-241496 5708 1 F Clarification on MWAB architecture figure 19.2.0 2024-12 SP#106 SP-241487 5744 3 B Local Offloading handling at I-SMF 19.2.0 2024-12 SP#106 SP-241494 5749 3 B Definition of identifiers of N3GPP device behind UE/5G-RG 19.2.0 2024-12 SP#106 SP-241487 5752 2 B KI#1 Architecture for Local Offloading Management 19.2.0 2024-12 SP#106 SP-241484 5763 1 F Clarification on congestion control 19.2.0 2024-12 SP#106 SP-241468 5780 - A UDR Discovery/Selection for Group ID Mapping 19.2.0 2024-12 SP#106 SP-241495 5782 2 B UPF event exposure at N4 Session release 19.2.0 2024-12 SP#106 SP-241482 5808 3 B CAG information provisioning 19.2.0 2024-12 SP#106 SP-241482 5809 3 F Terminology alignment for 5G_Femto 19.2.0 2024-12 SP#106 SP-241499 5816 - B Adding MSISDN verification operation support to Nnef_UEId Service 19.2.0 2024-12 SP#106 SP-241487 5825 1 B Local Offloading handling at I-SMF 19.2.0 2024-12 SP#106 SP-241496 5827 1 F MWAB Mobility handling improvement 19.2.0 2024-12 SP#106 SP-241492 5830 2 F Indirect Network Sharing clarification 19.2.0 2024-12 SP#106 SP-241487 5833 2 B PCF's awareness of I-SMF insertion for Local Offloading Management 19.2.0 2024-12 SP#106 SP-241490 5834 2 F MPS for Messaging RAN Paging for SMS over NAS 19.2.0 2024-12 SP#106 SP-241489 5844 2 B Handling of UE capability for MPQUIC-IP and MPQUIC-E steering functionalities 19.2.0 2024-12 SP#106 SP-241496 5845 2 B MWAB-gNB configuration during MWAB mobility 19.2.0 2024-12 SP#106 SP-241482 5856 2 B CAG information Provisioning clarification of roaming support 19.2.0 2024-12 SP#106 SP-241484 5866 3 C S-NSSAI selection while in EPS 19.2.0 2024-12 SP#106 SP-241487 5871 2 B I-SMF selection/insertion based on local offloading allowed indication 19.2.0 2025-01 SP#106 - - - - MCC Implementation correction: Removal of noted 23.501 CR5713R3 19.2.1 2025-03 SP#107 SP-250040 5518 14 B Support of UE-satellite-UE communications when serving satellite changes 19.3.0 2025-03 SP#107 SP-250064 5524 16 B Support Alternative QoS profile with PDU Set QoS and Notification Control 19.3.0 2025-03 SP#107 SP-250042 5635 3 B NWDAF model provision for AI positioning 19.3.0 2025-03 SP#107 SP-250064 5651 12 B Corrections for 23.501 Data boosting triggered by AS/AF 19.3.0 2025-03 SP#107 SP-250064 5670 6 B KI#9, Support of Available Data Rate 19.3.0 2025-03 SP#107 SP-250064 5673 6 B KI#1, Support the PDU Set Information Marking Support Indication 19.3.0 2025-03 SP#107 SP-250037 5820 2 F Correction on network function service framework 19.3.0 2025-03 SP#107 SP-250064 5867 13 B KI#9, Support of Rate limitation 19.3.0 2025-03 SP#107 SP-250042 5882 1 B KI#2 alignment 19.3.0 2025-03 SP#107 SP-250053 5891 1 A XRM services support in Roaming scenarios-Mirror 19.3.0 2025-03 SP#107 SP-250054 5897 1 F Parameters for EIF selection 19.3.0 2025-03 SP#107 SP-250045 5899 2 A Prioritization between UDM, OAM and NSSF based slice validity time 19.3.0 2025-03 SP#107 SP-250054 5900 2 F Clean up the architecture and interface for energysys 19.3.0 2025-03 SP#107 SP-250063 5902 1 F On MWAB mobility 19.3.0 2025-03 SP#107 SP-250062 5904 1 F Handling of Headers corrections 19.3.0 2025-03 SP#107 SP-250055 5906 1 F Updates to the ATSSS capability handling 19.3.0 2025-03 SP#107 SP-250040 5908 2 F AMF selection for regenerative payload 19.3.0 2025-03 SP#107 SP-250043 5909 1 F Correction and improvements related to EDGE_Ph3 KI#1 19.3.0 2025-03 SP#107 SP-250043 5914 1 F AMF functional description of supporting local offload 19.3.0 2025-03 SP#107 SP-250062 5916 1 F Update on QoS monitoring and reporting during UPF relocation and PDU session release 19.3.0 2025-03 SP#107 SP-250064 5917 1 F Corrections for KI#2 Support of transferring media related information over N6 19.3.0 2025-03 SP#107 SP-250064 5922 1 F KI#5, Update to data burst related 19.3.0 2025-03 SP#107 SP-250059 5925 5 F Non 3GPP access of HPLMN in the area of Indirect Network Sharing deployment 19.3.0 2025-03 SP#107 SP-250059 5926 1 F Clarification on network slice in the case of Indirect Network Sharing 19.3.0 2025-03 SP#107 SP-250054 5927 3 F Resolution of editor's note on whether the Energy Saving indicator is one value or multiple values 19.3.0 2025-03 SP#107 SP-250054 5928 3 F Resolution of editor's note on PCF taking EIF information into account 19.3.0 2025-03 SP#107 SP-250033 5932 1 A VPLMN QoS constraint clarification 19.3.0 2025-03 SP#107 SP-250063 5933 6 F MWAB configuration and Additional ULI Clarification 19.3.0 2025-03 SP#107 SP-250063 5934 1 F MWAB Mobility handling clarification 19.3.0 2025-03 SP#107 SP-250054 5935 1 F Compliance to regional legislation concerning user privacy 19.3.0 2025-03 SP#107 SP-250059 5939 - F Clarification on UPSec Policy provisioning 19.3.0 2025-03 SP#107 SP-250052 5948 1 A Addition of missing LLDP TLVs 19.3.0 2025-03 SP#107 SP-250035 5950 - A Updated reference for DetNet RFC 19.3.0 2025-03 SP#107 SP-250054 5956 3 C Support for S-NSSAI granularity energy consumption exposure 19.3.0 2025-03 SP#107 SP-250064 5958 1 F KI#4: Correct the RTCP 'MID' for IP packet filter set 19.3.0 2025-03 SP#107 SP-250055 5959 1 F Some corrections in MPQUIC steering functionalities 19.3.0 2025-03 SP#107 SP-250061 5960 1 F Clarification on UE triggering request for change of QoS 19.3.0 2025-03 SP#107 SP-250061 5963 1 F Definition of non-3GPP device connection information 19.3.0 2025-03 SP#107 SP-250043 5964 1 F Update general description of support for edge computing 19.3.0 2025-03 SP#107 SP-250036 5966 3 F SMF failure notification to AF on simultaneous connectivity during edge relocation 19.3.0 2025-03 SP#107 SP-250063 5968 1 F Solve the Editor's Note related to the Additional ULI 19.3.0 2025-03 SP#107 SP-250061 5970 1 F Clarification on roaming support for Non-3GPP Device Identifier 19.3.0 2025-03 SP#107 SP-250042 5978 1 B NWDAF discovery and selection parameters 19.3.0 2025-03 SP#107 SP-250062 5980 1 F Updates of UPF event exposure during N4 session release 19.3.0 2025-03 SP#107 SP-250055 5984 - D Clarification on steering functionalities description 19.3.0 2025-03 SP#107 SP-250055 5992 2 F Clarification on UPF Selection for ATSSS feature 19.3.0 2025-03 SP#107 SP-250055 5993 1 F Correction on QoS Support 19.3.0 2025-03 SP#107 SP-250054 5997 1 F Update on NF function descriptions and EIF selection factors 19.3.0 2025-03 SP#107 SP-250063 5998 1 B MWAB-UE Mobility Restriction 19.3.0 2025-03 SP#107 SP-250059 6004 4 F Clarification on the Qos monitoring capability 19.3.0 2025-03 SP#107 SP-250061 6005 - F Clarification on AF provisioning 19.3.0 2025-03 SP#107 SP-250061 6006 - F Resolve the EN on the PDU session establishment and Reference correction 19.3.0 2025-03 SP#107 SP-250061 6007 1 F Clarification on session management enhancement 19.3.0 2025-03 SP#107 SP-250054 6010 5 F Clarification on the EventExposure service operation of SMF 19.3.0 2025-03 SP#107 SP-250059 6020 7 F Resolution of EN in AF Requested modification of the Set of Network Slice(s) for a UE 19.3.0 2025-03 SP#107 SP-250043 6024 - F N6 delay measurement triggered by SMF 19.3.0 2025-03 SP#107 SP-250043 6025 1 F N6 delay measurement for I-SMF case 19.3.0 2025-03 SP#107 SP-250043 6026 1 F Clarification on the local offloading management service area 19.3.0 2025-03 SP#107 SP-250054 6028 5 F Adding per UE per Application level Energy consumption exposure 19.3.0 2025-03 SP#107 SP-250054 6031 2 F Clarification on the BDT based on network energy related information 19.3.0 2025-03 SP#107 SP-250045 6033 1 A Slice deregistration inactivity timer for Alternative S-NSSAI 19.3.0 2025-03 SP#107 SP-250064 6042 4 B Support Differentiated QoS handling for encrypted multiplexed media flows 19.3.0 2025-03 SP#107 SP-250059 6043 1 F Correction to when and how the UPF can provide the SMF with DNS server information 19.3.0 2025-03 SP#107 SP-250064 6050 1 B XRM_Ph2_KI3 Leveraging PDU Set QoS information for DSCP marking over N3/N9 in the transport network 19.3.0 2025-03 SP#107 SP-250061 6053 1 F further details for QoS information 19.3.0 2025-03 SP#107 SP-250062 6056 1 F Clarification to UPF selection based on specific UPF functionalities 19.3.0 2025-03 SP#107 SP-250043 6058 1 F Correction on I-SMF insertion/removal for local offloading management 19.3.0 2025-03 SP#107 SP-250043 6059 1 F Clarification on NF profile for (I-)SMF regarding local offloading management 19.3.0 2025-03 SP#107 SP-250043 6060 1 F Alignment on L-PSA UPF re-selection and/or an edge relocation 19.3.0 2025-03 SP#107 SP-250055 6061 3 F Terminology alignment 19.3.0 2025-03 SP#107 SP-250051 6063 1 A Alignment of Subscription of UPF event via I-SMF 19.3.0 2025-03 SP#107 SP-250063 6064 2 F Clarification of regulatory services support 19.3.0 2025-03 SP#107 SP-250063 6065 1 F Clarification of mobility clause 19.3.0 2025-03 SP#107 SP-250054 6071 2 F Update of the Energy consumption calculation formulae 19.3.0 2025-03 SP#107 SP-250059 6073 2 F Clarification about VLAN handling in 5GS 19.3.0 2025-03 SP#107 SP-250037 6075 1 F Add Nnef_UeAddress Service to NEF services 19.3.0 2025-03 SP#107 SP-250038 6080 - F Clarification on CAG information provisioning 19.3.0 2025-03 SP#107 SP-250037 6083 1 F Removing unnecessary restrictions for emergency PDU sessions 19.3.0 2025-03 SP#107 SP-250063 6090 1 F Corrections to remove EN on QoS handling for Xn interface over BH PDU session 19.3.0 2025-03 SP#107 SP-250037 6092 2 F MPS-subscribed UE definition correction 19.3.0 2025-03 SP#107 SP-250037 6094 3 F RAN Paging Priority corrections 19.3.0 2025-03 SP#107 SP-250063 6097 1 F Clarification on MWAB mobility 19.3.0 2025-03 SP#107 SP-250054 6100 3 F Update on energy consumption information collection and exposure to solve the Editor's notes 19.3.0 2025-03 SP#107 SP-250038 6103 2 F Term alignment and roaming clarification 19.3.0 2025-03 SP#107 SP-250038 6109 1 F Fix NR Femto architecture description 19.3.0 2025-03 SP#107 SP-250059 6114 2 F Clarification on Configured NSSAI in AF Requested modification of the Set of Network Slice(s) for a UE 19.3.0 2025-03 SP#107 SP-250059 6121 3 F UCMF discovery in case of Indirect Network Service (INS) deployment-23.501. 19.3.0 2025-03 SP#107 SP-250051 6124 2 A Clarification on the UPF Event Exposure 19.3.0 2025-03 SP#107 SP-250063 6126 2 F Determination of UE served by a MWAB cell 19.3.0 2025-03 SP#107 SP-250037 6139 - F Clarification on NAS LP-WUS Subgroup Support Indication meaning 19.3.0 2025-03 SP#107 SP-250054 6142 3 F Resolve the EN in the architecture clause 19.3.0 2025-03 SP#107 SP-250040 6144 2 B Update for support of UE-Satellite-UE communication 19.3.0 2025-03 SP#107 SP-250058 6148 3 C Provisioning Multi-modal Service ID to NG-RAN 19.3.0 2025-03 SP#107 SP-250038 6155 - F CAG Information provisioning functionality 19.3.0 2025-03 SP#107 SP-250037 6156 - C New SST for Guaranteed Bit Rate Streaming Services 19.3.0 2025-03 SP#107 SP-250037 6163 2 F MPS Resume Cause alignment 19.3.0 |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 1 Scope | The present document defines the Stage 2 procedures and Network Function Services for the 5G system architecture which is described in the TS 23.501 [2] and for the policy and charging control framework which is described in TS 23.503 [20]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[3] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2)".
[4] Void.
[5] Void.
[6] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)".
[7] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[8] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[9] 3GPP TS 38.300: "NR and NG-RAN Overall Description; Stage 2".
[10] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[11] Void.
[12] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification".
[13] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[14] Void.
[15] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System".
[16] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[17] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[18] 3GPP TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[19] Void.
[20] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System ".
[21] IETF RFC 4191: "Default Router Preferences and More-Specific Routes".
[22] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode".
[23] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[24] 3GPP TS 23.203: "Policy and charging control architecture".
[25] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[26] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses".
[27] Void.
[28] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[29] Void.
[30] Void.
[31] Void.
[32] 3GPP TS 29.507: "Access and Mobility Policy Control Service; Stage 3".
[33] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[34] Void.
[35] 3GPP TS 23.251: "Network sharing; Architecture and functional description".
[36] 3GPP TS 29.502: "5G System; Session Management Services; Stage 3".
[37] 3GPP TS 29.510: "5G System; Network function repository services; Stage 3".
[38] 3GPP TS 23.380: "IMS Restoration Procedures".
[39] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
[40] IETF RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)".
[41] 3GPP TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access Networks (N3AN); Stage 3".
[42] 3GPP TS 32.290: "Services, operations and procedures of charging using Service Based Interface (SBI)".
[43] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
[44] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in idle mode".
[45] 3GPP TS 32.255: "5G system; 5G data connectivity domain charging; Stage 2".
[46] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[47] 3GPP TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3".
[48] IEEE Std 802.11-2016 (Revision of IEEE Std 802.11-2012): "IEEE Standard for Information technology - Telecommunications and information exchange between systems Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[49] IETF RFC 2410: "The NULL Encryption Algorithm and its use with IPsec".
[50] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services; Stage 2".
[51] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[52] 3GPP TS 29.503: "5G System; Unified Data Management Services; Stage 3".
[53] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[54] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[55] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[56] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[57] 3GPP TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[58] 3GPP TS 29.525: "5G System; UE Policy Control Service; Stage 3".
[59] IETF RFC 6696: "EAP Extensions for the EAP Re-authentication Protocol (ERP)", July 2012.
[60] IETF RFC 5295: "Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)", Aug. 2008.
[61] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[62] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[63] 3GPP TS 29.561: "5G System; Interworking between 5G Network and external Data Networks; Stage 3".
[64] 3GPP TS 29.413: "Application of the NG Application Protocol (NGAP) to non-3GPP access".
[65] Void.
[66] IEEE Std 802.1Q-2022: "IEEE Standard for Local and Metropolitan Area Networks-Bridges and Bridged Networks".
[67] Void.
[68] 3GPP TS 23.632: "User Data Interworking, Coexistence and Migration".
[69] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane nodes".
[70] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[71] 3GPP TS 32.256: "Charging Management; 5G connection and mobility domain charging; Stage 2".
[72] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
[73] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[74] 3GPP TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
[75] IEEE Std 802.1AS-2020: "IEEE Standard for Local and metropolitan area networks--Timing and Synchronization for Time-Sensitive Applications".
[76] IEEE Std 1588-2019: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control".
[77] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[78] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services".
[79] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[80] 3GPP TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
[81] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
[82] 3GPP TS 29.519: "5G System; Usage of the Unified Data Repository service for Policy Data, Application Data and Structure Data for Exposure; Stage 3".
[83] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[84] 3GPP TS 23.540: "Technical realization of Service Based Short Message Service; Stage 2".
[85] 3GPP TS 29.598: "Unstructured data storage services".
[86] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[87] 3GPP TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[88] 3GPP TS 23.586: "Architectural Enhancements to support Ranging based services and Sidelink Positioning".
[89] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point".
[90] 3GPP TS 23.015: "Technical realization of Operator Determined Barring (ODB)".
[91] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository service for Subscription Data".
[92] 3GPP TS 28.405: "Quality of Experience (QoE) measurement collection; Control and configuration".
[93] 3GPP TS 29.564: "User Plane Function Services; Stage 3".
[94] 3GPP TS 33.533: "Security aspects of ranging based services and sidelink positioning".
[95] 3GPP TS 33.122: "Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs".
[96] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
[97] IETF RFC 9298: "Proxying UDP in HTTP".
[98] IETF draft-ietf-masque-quic-proxy: "QUIC-Aware Proxying Using HTTP".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.
[99] IETF draft-ietf-tsvwg-udp-options: "Transport Options for UDP".
Editor's note: The above reference will be revised to RFC when finalized by IETF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 3 Definitions, symbols and abbreviations | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 23.501 [2] and TS 23.503 [20] apply. A term defined in TS 23.501 [2] or TS 23.503 [20] takes precedence over the definition of the same term, if any, in any other specifications.
Multi-member AF session: A type of AF session (see definition in TS 29.214 [89]) in which the AF establishes an application level session with a set of UEs. A Multi-member AF session can only be established via a supporting NEF (even for the trusted AF scenario). Such NEF associates the Multi-member AF session with one or more AF sessions (one AF session per UE in the set), in order to interact with each UE's serving PCF on a per AF session basis. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2] and TS 23.503 [20] apply. An abbreviation defined in TS 23.501 [2] or TS 23.503 [20] takes precedence over the definition of the same abbreviation, if any, in any other specifications. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4 System procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.1 General | The clause 4 describes the procedures and Network Function services for the 5GS by end-to-end information flows and these information flows make use of NF service operations, defined in clause 5, for the communication within the 5GC Control Plane. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2 Connection, Registration and Mobility Management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.1 General | The Connection Management is used to establish and release the Control Plane signalling connection between the UE and the AMF. The Registration Management is used to register or deregister a UE/user with the 5GS and establish the user context in the 5GS. The Mobility Management functions are used to keep track of the current location of a UE. The procedures in clause 4.2 provides Connection, Registration and Mobility Management functionality. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2 Registration Management procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.1 General | The Registration and Deregistration procedures in clause 4.2.2 provides the required functionality to register or deregister a UE/user with the 5GS. Additional functionality to support Registration Management for non-3GPP access is defined in clause 4.12. Additional functionality to support Registration Management for specific services such as SMS over NAS is defined in clause 4.13. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2 Registration procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2.1 General | A UE needs to register with the network to get authorized to receive services, to enable mobility tracking and to enable reachability. The UE initiates the Registration procedure using one of the following Registration types:
- Initial Registration to the 5GS;
- Mobility Registration Update upon changing to a new Tracking Area (TA) outside the UE's Registration Area in both CM-CONNECTED and CM-IDLE state, or when the UE needs to update its capabilities or protocol parameters that are negotiated in Registration procedure with or without changing to a new TA, or a change in the UE's Preferred Network Behaviour that would create an incompatibility with the Supported Network Behaviour provided by the serving AMF, or when the UE intends to retrieve LADN Information, or with NR satellite access upon changing to a suitable cell indicating multiple TAs for the RPLMN all of which are outside the UE's Registration Area in both CM-CONNECTED and CM-IDLE state, or when the Multi-USIM UE needs a new 5G-GUTI assignment, or when the UE needs to indicate or returns from an Unavailability Period (see clause 5.4.1.4 of TS 23.501 [2]), or when the UE using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage) is about to leave the satellite network coverage as described in clause 5.4.13.1 of TS 23.501 [2], or when the UE has informed the network it is unreachable and now returns to coverage using either satellite or terrestrial access as described in clause 5.4.1.4 of TS 23.501 [2]; or
- Periodic Registration Update (due to a predefined time period of inactivity); or
- Emergency Registration; or
- Disaster Roaming Initial Registration, as specified in clause 5.40 of TS 23.501 [2]; or
- Disaster Roaming Mobility Registration Update, as specified in clause 5.40 of TS 23.501 [2]; or
- SNPN Onboarding Registration allows the UE to access an ON-SNPN for the purpose of provisioning the UE with SO-SNPN credentials to enable SO-SNPN access. SNPN Onboarding Registration is only applicable for registration with ON-SNPN i.e. when the UE uses PLMN credentials for accessing an ONN the UE initiates an Initial Registration. The SNPN Onboarding Registration is specified in clause 4.2.2.2.4.
NOTE 1: With NR satellite access, more than one TAC can be indicated to a UE for each PLMN in any cell.
The General Registration call flow in clause 4.2.2.2.2 applies on all these Registration procedures, but the periodic registration need not include all parameters that are used in other registration cases.
The following are the cleartext IEs, as defined in TS 24.501 [25] that can be sent by the UE in the Registration Request message if the UE has no NAS security context:
- Registration type;
- SUCI or 5G-GUTI or PEI;
- Security parameters;
- additional GUTI;
- 4G Tracking Area Update;
- the indication that the UE is moving from EPS;
- PLMN with Disaster Condition;
- if the UE is registering with an SNPN, the NID of the SNPN that assigned the 5G-GUTI.
NOTE 2: The NID is provided when the 5G-GUTI is assigned by another SNPN than the selected SNPN.
Aspects related to dual registration in 3GPP and non-3GPP access are described in clause 4.12. The general Registration call flow in clause 4.2.2.2.2 is also used for the case of registration in 3GPP access when the UE is already registered in a non-3GPP access and vice versa. Registration in 3GPP access when the UE is already registered in a non-3GPP access scenario may require an AMF change, as further detailed in clause 4.12.8.
The general Registration call flow in clause 4.2.2.2.2 is also used by UEs in limited service state (see TS 23.122 [22]) registering for emergency services only (referred to as Emergency Registration), see clause 5.16.4 of TS 23.501 [2].
During the initial registration the PEI is obtained from the UE. If the PEI is needed (e.g. for EIR check), the AMF shall retrieve the PEI when it establishes the NAS security context with a Security Mode Command during initial registration. The AMF operator may check the PEI with an EIR. If the PEI was retrieved by the AMF (either from the UE or another AMF), AMF shall provide it to the UDM using Nudm_UECM_Registration in order to ensure that the UDM always has the latest PEI available e.g. for reporting event Change of SUPI-PEI association. The AMF passes the PEI to the UDM, to the SMF and the PCF. The UDM may store this data in UDR by Nudr_SDM_Update.
NOTE 3: The use of NSI ID in the 5GC is optional and depends on the deployment choices of the operator.
During the registration the Home Network (or Credentials Holder in case of access to an SNPN) can provide Steering of Roaming information to the UE via the AMF (i.e. a list of preferred PLMN/access technology combinations and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services or HPLMN/Credentials Holder indication that 'no change of the above list(s) stored in the UE is needed'). The Home Network can include an indication for the UE to send an acknowledgement of the reception of this information. Details regarding the handling of Steering of Roaming information including how this information is managed between the AMF and the UE are defined in TS 23.122 [22].
The AMF determines Access Type and RAT Type as defined in clause 5.3.2.3 of TS 23.501 [2]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 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], [LP-WUS 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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [2]. The UE provides Requested NSSAI (as described in clause 5.15.5.2.1 of TS 23.501 [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 [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. If the Network Slice Replacement is used and the UE is configured with Mapping Of Alternative NSSAI, the Requested NSSAI may include Alternative S-NSSAI(s). If the AMF determines that S-NSSAI(s) that the UE requests are not Alternative S-NSSAI(s) in the UE context and not Subscribed S-NSSAIs, the AMF determines to update the UE configuration as described in clause 5.15.19 of TS 23.501 [2]. 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 [2]. If the UEs supports reconnection to the network due to RAN timing synchronization status change as described in TS 23.501 [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 [2].
The UE includes the Default Configured NSSAI Indication if the UE is using a Default Configured NSSAI, as defined in TS 23.501 [2].
The UE may include UE paging probability information if it supports the assignment of WUS Assistance Information, AMF PEIPS Assistance Information from the AMF or AMF LP-WUSPS Assistance Information from AMF (see TS 23.501 [2]).
The UE may include Paging Subgrouping Support Indication or LP-WUS Subgrouping Support Indication as defined in TS 23.501 [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 [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 [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 [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 [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 [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 [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 [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 [2].
The Security parameters are used for Authentication and integrity protection, see TS 33.501 [15]. Requested NSSAI indicates the Network Slice Selection Assistance Information (as defined in clause 5.15 of TS 23.501 [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 [2]. The UE may provide the extended idle mode DRX parameters as defined in clause 5.31.7.2 of TS 23.501 [2] to request extended idle mode DRX.
The UE provides UE Radio Capability Update indication as described in TS 23.501 [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 or an event is triggered in the UE that would make the UE unavailable for a certain period of time, 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 [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 [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 [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 [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 [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 [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 [25].
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 [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 [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 [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 [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 [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 [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 [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 [50].
During inter PLMN mobility, the handling of the UE Radio Capability ID in the new AMF is as defined in TS 23.501 [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 [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 [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 [15]. The AUSF selects a UDM as described in clause 6.3.8 of TS 23.501 [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 [2] and in TS 33.501 [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 [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 [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 [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 [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 [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. If QMC Configuration information is available at the AMF, the AMF provides the 5G-AN with QMC Configuration information 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 [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 [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 [2].
The AMF selects a UDM as described in clause 6.3.8 of TS 23.501 [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 [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 [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 [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 [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 [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" (and optionally, the MPS priority for Messaging indication if it is set (enabled) in the UDM) 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 to a single AF, the UDM may provide a Slice Usage Policy information including whether a network slice is on demand and a slice deregistration inactivity timer value for the Subscribed S-NSSAIs as described in clause 5.15.15 of TS 23.501 [2].
The UDM may provide the NCR-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 of NCR-MT authorization information.
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 [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 [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. (including messages related to SMS delivery as specified in clause 4.13 if the MPS for Messaging indication is included in subscription data) Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500 [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 [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.
The subscription data may contain an Energy Saving Indicator defined in clause 5.51.5 of TS 23.501 [2]. If received from the UDM, the AMF stores the Energy Saving Indicator in the UE Context.
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 [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 [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 [2] and according to the V-NRF to H-NRF interaction described in clause 4.3.2.2.3.3.
As described in clause 6.3.7.1 of TS 23.501 [2], if the AMF receives PCF Selection Assistance info from the UDM, the AMF checks if a list of DNN, S-NSSAI combinations are provided in the PCF Selection Assistance Info then the AMF checks local configuration to determine which DNN, S-NSSAI to use then selects the PCF ID included in the corresponding UE Context in the SMF data. If no PCF ID is received, the AMF select the PCF by considering other criteria, defined in clause 6.3.7.1 of TS 23.501 [2].
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 inactivity timer value, for the Subscribed S-NSSAIs as described in clause 5.15.15 of TS 23.501 [2].
17. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext () or Nsmf_PDUSession_ReleaseSMContext ().
For an Emergency Registered UE (see TS 23.501 [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.
NOTE 13: In the case of Indirect Network Sharing, when UE of participating operator moves between the shared network area and an area of its home network, a V-SMF can be inserted or removed. In this case, the related procedure of mobility registration update with V-SMF insertion/removal described in clause 4.23.3 is applied.
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 UE has moved into a TA not supporting the S-NSSAI associated with the PDU Session, and the AMF determines to release the PDU Session, and no N2 interaction is needed (i.e. UP connection of the PDU Session is not active), the AMF sets the PDU Session status indicating that the PDU Session is released in the network and the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF.
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 [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], [AMF LP-WUSPS 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 [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 [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 [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 [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 [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 [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 [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 Usage 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 [2]. In the Slice Usage Policy, the AMF indicates if an S-NSSAI is on demand slice and optionally slice deregistration inactivity timer value. If the AMF includes slice deregistration inactivity 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 [2]. If the AMF includes updated slice deregistration timer value(s), the UE uses the updated slice deregistration inactivity timer value(s) next time the slice deregistration inactivity timer(s) starts.
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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [25].
The Accepted DRX parameters are defined in clause 5.4.5 of TS 23.501 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [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 [2]).
If the network supports WUS grouping (see TS 23.501 [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 [2].
If the UE provided LP-WUS Subgrouping Support Indication in step 1, a supporting AMF may provide the AMF LP-WUSPS Assistance Information, including the LP-WUS Subgroup ID as defined in TS 23.501 [2].
When the UE and the AMF supports RACS as defined in clause 5.4.4.1a of TS 23.501 [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 [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 both the UE and the AMF support the Unavailability Period, the AMF may provide an Unavailability Period Duration and/or Start of Unavailability Period determined due to NR satellite access discontinuous coverage during initial registration procedure as described in clause 5.4.1.4 of TS 23.501 [2]. 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 [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 [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 [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 [2].
For the authorization of MWAB-UE as specified in clause 5.49.3 of TS 23.501 [2], the AMF determines the Allowed NSSAI for MWAB-UE which includes the S-NSSAI(s) which is (are) used to establish the BH PDU session(s).
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 [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 [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 [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 [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 [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 [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 [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 [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 [2].
If the AMF received an Energy Saving Indicator in steps 14a-14c, the AMF includes the Energy Saving Indicator in the N2 message carrying the Registration Accept message.
Editor's note: Whether the Energy Saving Indicator is provided to the NG-RAN is FFS.
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 14: 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 [44] and TS 36.304 [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 AMF provided updated slice deregistration timer value(s) to the UE in step 21, the AMF uses the corresponding slice deregistration inactivity timer value(s) next time the slice deregistration inactivity timer(s) starts.
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 [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 [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 [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. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2.3 Registration with AMF re-allocation | When an AMF receives a Registration request, the AMF may need to reroute the Registration request to another AMF, e.g. when the initial AMF is not the appropriate AMF to serve the UE. The Registration with AMF re-allocation procedure, described in figure 4.2.2.2.3-1, is used to reroute the NAS message of the UE to the target AMF during a Registration procedure.
Figure 4.2.2.2.3-1: Registration with AMF re-allocation procedure
The initial AMF and the target AMF register their capability at the NRF.
1. If the UE is in CM-IDLE State, steps 1 and 2 of figure 4.2.2.2.2-1 have occurred and the (R)AN sends the Registration request message within an Initial UE message to the initial AMF. If the UE is in CM-CONNECTED state and triggers registration procedure, the NG-RAN sends Registration request message in the Uplink NAS Transport message to the serving AMF which is initial AMF. The AMF may skip step 2-3.
2. If the AMF needs the SUPI and/or UE's subscription information to decide whether to reroute the Registration Request or if the Registration Request was not sent integrity protected or integrity protection is indicated as failed, then AMF performs steps 4 to 9a or to 9b of figure 4.2.2.2.2-1.
3a. [Conditional] If the initial AMF needs UE's subscription information to decide whether to reroute the Registration Request and UE's slice selection subscription information was not provided by old AMF, the AMF selects a UDM as described in clause 6.3.8 of TS 23.501 [2].
3b. Initial AMF to UDM: Nudm_SDM_Get (SUPI, Slice Selection Subscription data).
The initial AMF request UE's Slice Selection Subscription data from UDM by invoking the Nudm_SDM_Get (see clause 5.2.3.3.1) service operation. UDM may get this information from UDR by Nudr_DM_Query(SUPI, Slice Selection Subscription data).
For a Disaster Roaming Registration, the AMF may provide the indication of Disaster Roaming service to the UDM.
3c. UDM to initial AMF: Response to Nudm_SDM_Get. The AMF gets the Slice Selection Subscription data including Subscribed S-NSSAIs.
UDM responds with slice selection subscription data to initial AMF.
For a Disaster Roaming Registration, the UDM responds with the slice selection subscription data for a Disaster Roaming service to initial AMF based on the local policy and/or the local configuration as specified in clause 5.40.4 of TS 23.501 [2].
4a. [Conditional] Initial AMF to NSSF: Nnssf_NSSelection_Get (Requested NSSAI, [Mapping Of Requested NSSAI], Subscribed S-NSSAI(s) with the default S-NSSAI indication, [NSSRG Information], TAI, Allowed NSSAI for the other access type (if any), [Mapping of Allowed NSSAI], PLMN ID of the SUPI).
If there is a need for slice selection, (see clause 5.15.5.2.1 of TS 23.501 [2]), e.g. the initial AMF cannot serve all the S-NSSAI(s) from the Requested NSSAI permitted by the subscription information, the initial AMF invokes the Nnssf_NSSelection_Get service operation from the NSSF by including Requested NSSAI, optionally Mapping Of Requested NSSAI, Subscribed S-NSSAIs with the default S-NSSAI indication, [NSSRG Information], Allowed NSSAI for the other access type (if any), Mapping of Allowed NSSAI, PLMN ID of the SUPI and the TAI of the UE. If the AMF needs to indicate the NSSF to return the Configured NSSAI to obtain network slice configuration when it receives from the UDM an indication that subscription has changed for the UE (see step 14b of clause 4.2.2.2.2) to ensure that the information returned by the NSSF includes the new Configured NSSAI for the UE which can be used to update UE network slicing configuration (see step 21 of clause 4.2.2.2.2), the AMF indicates to the NSSF that the AMF needs a Configured NSSAI by providing the Default Configured NSSAI Indication as described in clause 5.15.5.2.1 of TS 23.501 [2].
The AMF includes, if available, the NSSRG Information for the S-NSSAIs of the HPLMN, defined in clause 5.15.12 of TS 23.501 [2], including information whether the UE has indicated support of the subscription-based restrictions to simultaneous registration of network slices and whether the UDM has indicated to provide all subscribed S-NSSAIs for non-supporting UEs.
If the UE context includes Partially Allowed NSSAI, then the AMF includes the S-NSSAIs of the Partially Allowed NSSAI in the Allowed NSSAI and includes the corresponding HPLMN S-NSSAI in the Mapping Of Allowed NSSAI.
4b. [Conditional] NSSF to Initial AMF: Response to Nnssf_NSSelection_Get (AMF Set or list of AMF addresses, Allowed NSSAI for the first access type, [Mapping Of Allowed NSSAI], [Allowed NSSAI for the second access type], [Mapping of Allowed NSSAI], [NSI ID(s)], [NRF(s)], [List of rejected (S-NSSAI(s), cause value(s))], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI]).
The NSSF performs the steps specified in point (B) in clause 5.15.5.2.1 of TS 23.501 [2]. The NSSF returns to initial AMF the Allowed NSSAI for the first access type, optionally the Mapping Of Allowed NSSAI, the Allowed NSSAI for the second access type (if any), optionally the Mapping of Allowed NSSAI and the target AMF Set or, based on configuration, the list of candidate AMF(s). The NSSF may return NSI ID(s) associated to the Network Slice instance(s) corresponding to certain S-NSSAI(s). The NSSF may return the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s). It may return also information regarding rejection causes for S-NSSAI(s) not included in the Allowed NSSAI. The NSSF may return Configured NSSAI for the Serving PLMN and possibly the associated mapping of the Configured NSSAI. If the NSSRG information was included in the request, the NSSF provides the Configured NSSAI as described in clause 5.15.12 of TS 23.501 [2].
NOTE 1: The NRF(s) returned by the NSSF, if any, belong to any level of NRF (see clause 6.2.6 of TS 23.501 [2]) according to the deployment decision of the operator.
5. [Conditional] Initial AMF to old AMF: Namf_Communication_RegistrationStatusUpdate (failure cause ).
If the UE was in CM-IDLE and another AMF is selected, the initial AMF sends a reject indication to the old AMF telling that the UE Registration procedure did not fully complete at the initial AMF. The old AMF continues as if the Namf_Communication_UEContextTransfer had never been received.
6a. [Conditional] Initial AMF to NRF: Nnrf_NFDiscovery_Request (NF type, AMF Set).
If the initial AMF does not locally store the target AMF address and if the initial AMF intends to use direct reroute to target AMF or the reroute via (NG-R)AN message needs to include AMF address, then the initial AMF invokes the Nnrf_NFDiscovery_Request service operation from the NRF to find a proper target AMF which has required NF capabilities to serve the UE. The NF type is set to AMF. The AMF Set is included in the Nnrf_NFDiscovery_Request.
6b. [Conditional] NRF to AMF: Response to Nnrf_NFDiscovery_Request (list of (AMF pointer, AMF address, plus additional selection rules and NF capabilities)).
The NRF replies with the list of potential target AMF(s). The NRF may also provide the details of the services offered by the candidate AMF(s) along with the notification end-point for each type of notification service that the selected AMF had registered with the NRF, if available. As an alternative, it provides a list of potential target AMFs and their capabilities and optionally, additional selection rules. Based on the information about registered NFs and required capabilities, a target AMF is selected by the initial AMF.
If the security association has been established between the UE and initial AMF, to avoid a registration failure, the initial AMF shall forward the NAS message to the target AMF by executing step 7(A).
NOTE 2: The security context in the initial AMF is not transferred to the target AMF if initial AMF forward the NAS message to the target AMF via (R)AN. In this case the UE rejects the NAS message sent from target AMF as the security context in the UE and target AMF are not synchronized.
NOTE 3: Network slice isolation cannot be completely maintained in case the AMF reallocation is executed by step 7(A).
If the initial AMF is not part of the target AMF Set and is not able to get a list of candidate AMF(s) by querying the NRF with the target AMF Set (e.g. the NRF locally pre-configured on AMF does not provide the requested information, the query to the appropriate NRF provided by the NSSF is not successful, or the initial AMF has knowledge that the initial AMF is not authorized as serving AMF etc.) then the initial AMF shall forward the NAS message to the target AMF via (R)AN executing step 7(B) unless the security association has been established between the UE and initial AMF; the Allowed NSSAI, optionally the Partially Allowed NSSAI and the AMF Set are included to enable the (R)AN to select the target AMF as described in clause 6.3.5 of TS 23.501 [2].
7(A). If the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF directly, the initial AMF invokes the Namf_Communication_N1MessageNotify to the target AMF, carrying the rerouted NAS message. The Namf_Communication_N1MessageNotify service operation includes AN access information (e.g. the information enabling (R)AN to identify the N2 terminating point, CAG Identifier(s) of the CAG cell) and the complete Registration Request message in clear text as specified in TS 33.501 [15] and the UE's SUPI and MM Context if available. If the initial AMF has obtained the information from the NSSF as described at step 4b, that information except the AMF Set or list of AMF addresses is included. The target AMF then updates the (R)AN with a new updated N2 termination point for the UE in the first message from target AMF to RAN in step 8.
7(B). [Conditional] if the UE was in CM-IDLE, if the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF via (R)AN unless the target AMF(s) are returned from the NSSF and identified by a list of candidate AMF(s), the initial AMF sends a NGAP Reroute NAS Request message to the (R)AN (step 7a). The NGAP Reroute Request NAS message includes the information about the target AMF and the complete Registration Request message. If the initial AMF has obtained the information as described at step 4b, that information is included. The (R)AN sends the Initial UE message to the target AMF (step 7b) indicating reroute due to slicing including the information from step 4b that the NSSF provided.
NOTE 4: Step 7B is not supported if the UE was in CM-CONNECTED i.e. the NGAP Uplink NAS Transport message was received at step 1.
8. After receiving the Registration Request message transmitted at step 7(A)a or step 7(B)b, the target AMF continues with the Registration procedure from step 4 until 22 of figure 4.2.2.2.2-1 (with the target AMF corresponding to the new AMF), which includes the UE context retrieved from old AMF. If the 5G security context is received from the initial AMF, the target AMF continue using that one instead of the 5G security context the target AMF may have retrieved from the old AMF. If the initial AMF decides to forward the NAS message to the target AMF (step 7(A), the first message from the target AMF to (R)AN (either Initial Context Setup Request, or Downlink NAS Transport) contain the AMF name of the initial AMF and target AMF UE NGAP ID. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.2.4 Registration with Onboarding SNPN | This clause specifies how a UE can register to an ON-SNPN for provisioning the UE with SO-SNPN credentials and other information to enable SNPN access as defined in clause 5.30.2.10 of TS 23.501 [2].
The Registration procedure for Onboarding SNPN over 3GPP access shall be supported as specified in clause 4.2.2.2.2 with the following changes compared to the steps in the call flow represented in Figure 4.2.2.2.2-1, covering three cases, i.e. when DCS is hosting AAA Server and when DCS is hosting AUSF/UDM and when DCS is not involved, as shown in Figure 4.2.2.2.4-1.
The Registration procedure for Onboarding SNPN over untrusted non-3GPP access shall be supported as specified in clause 4.12.2.2. The Registration procedure for Onboarding SNPN over trusted non-3GPP access shall be supported as specified in clause 4.12a.2.2.
Figure 4.2.2.2.4-1: UE Registration with ON-SNPN
1. UE to NG-RAN: AN parameters shall include Onboarding indication if the UE is accessing 5GS for Onboarding. The Registration Type "SNPN Onboarding" indicates that the UE wants to perform SNPN Onboarding Registration (i.e. allows the UE to access an ON-SNPN for the purpose of provisioning the UE with SO-SNPN credentials). For SNPN Onboarding Registration, a SUCI generated from a SUPI derived from Default UE Credentials shall be included as described in clause 5.30.2.10.2.6 of TS 23.501 [2].
If the UE has registered in the ON-SNPN for onboarding, the UE can perform a Mobility Registration Update, or a Periodic Registration Update as specified in clause 4.2.2.2.2. If the onboarding registered UE wants to perform a Mobility Registration Update the AN parameters shall also include an Onboarding indication that the UE is registered for onboarding.
NOTE: When the UE is performing Registration for Onboarding to an ON-SNPN, the UE does not include a Requested NSSAI as the UE is not pre-configured with a S-NSSAI for the purpose of UE onboarding in the ON-SNPN.
2. Based on the Onboarding indication in step 1, the NG-RAN selects an AMF as described in clause 6.3.5 of TS 23.501 [2].
3. NG-RAN to AMF: The N2 message contains the Registration Request as described in step 1.
4. [Conditional] new AMF to old AMF: Namf_Communication_UEContextTransfer (complete Registration Request).
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)). Once the registration is completed successfully, the new AMF may start an implementation specific deregistration timer for when to deregister the onboarding registered UE if the UE context contains the indication that the UE is registered for onboarding.
6-7. Skipped.
8. When the AMF receives a NAS Registration Request with the 5GS Registration Type set to "SNPN Onboarding", the AMF applies locally configured AMF Configuration Data for Onboarding in order to restrict UE network usage to only onboarding and stores in the UE Context in AMF an indication that the UE is registered for onboarding. The AMF selects an AUSF as described in clause 5.30.2.10.2.6 of TS 23.501 [2]. Based on ON-SNPN policies, the AMF may start an implementation specific deregistration timer configured for UE Onboarding as described in TS 23.501 [2].
9. The authentication is performed as described in TS 33.501 [15].
For DCS hosting AAA Server as shown in step 9-1, based on local configuration (e.g. using the realm part of the SUCI), the AUSF sends the SUPI towards the AAA Server in the DCS domain via the NSSAAF, then the AAA Server in the DCS domain authenticates the UE based on received data from AUSF. During authentication procedure the AAA Server in the DCS domain may provide PVS FQDN(s) and/or PVS IP address(es) for the UE to the AUSF via the NSSAAF, the AUSF then provides PVS FQDN(s) and/or PVS IP address(es) to the AMF.
For DCS hosting AUSF/UDM as shown in step 9-2, the AUSF in DCS domain performs UDM selection. The AMF sends the SUCI and Default UE credentials received from the UE towards the AUSF in DCS domain, which authenticates the UE based on received data from AMF and subscription data from the UDM in DCS domain. During authentication procedure, the AUSF in the DCS domain provides PVS FQDN(s) and/or PVS IP address(es) to the AMF.
When DCS is not involved during primary authentication as shown in step 9-3, the AMF selects a local AUSF as defined in clause 6.3.4 of TS 23.501 [2] and performs primary authentication towards the local AUSF using Default UE credentials as described in TS 33.501 [15].
10. [Conditional] new AMF to old AMF: Namf_Communication_RegistrationStatusUpdate.
11. [Conditional] AMF to UE: Identity Request/Response (PEI).
If the PEI was not provided by the UE, the Identity Request procedure is initiated by AMF sending an Identity Request message to the UE to retrieve the PEI.
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.
13-20. Skipped.
21. AMF to UE: The AMF sends a Registration Accept message to the UE indicating that the Registration Request for Onboarding SNPN has been accepted. The Allowed NSSAI containing the S-NSSAI from the AMF Onboarding Configuration Data is included in the N2 message to NG-RAN.
21b. Skipped.
22. UE to AMF: The UE sends a Registration Complete message to the AMF.
23-25. Skipped. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3 Deregistration procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3.1 General | The Deregistration procedure allows:
- the UE to inform the network that it does not want to access the 5GS any longer; and
- the network to inform the UE that it does not have access to the 5GS any longer; or
- the network to inform the UE that the UE's Registered PLMN is not allowed to operate at the UE location.
The Deregistration request by the UE and Deregistration request by the network include whether the Deregistration applies to the 3GPP access, to the non-3GPP access, or to both. When the UE is registered to both accesses in the same PLMN, the Deregistration message can be sent over any access regardless of the access the Deregistration is applied to.
Network-initiated Deregistration may be initiated if the UE's registered PLMN is not allowed to operate in the present UE location. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3.2 UE-initiated Deregistration | The UE uses this procedure to deregister from the registered PLMN as shown in Figure 4.2.2.3.2-1.
Figure 4.2.2.3.2-1: UE-initiated Deregistration
1. The UE sends NAS message Deregistration Request (5G-GUTI, Deregistration type (e.g. Switch off), Access Type, [Unavailability Period Duration], [NAS message container]) to the AMF.
Access type indicates whether the Deregistration procedure applies to the 3GPP access, to the non-3GPP access, or to both if the 3GPP access and non-3GPP access of the UE are served by the same AMF (refer to TS 23.501 [2]). The AMF shall invoke the Deregistration procedure for the target access indicated by the UE.
If the UE and network support Unavailability Period and an event is triggered in the UE that would make the UE unavailable for a period of time, the UE includes Unavailability Period Duration as described in clause 5.4.1.4 of TS 23.501 [2].
The NAS message container shall be included if the UE is sending a Deregistration 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 [25]. If the UE does not need to send non-cleartext IEs, the UE shall send a Deregistration Request message without including the NAS message container.
1a. [Conditional] If the Deregistration Request message was not sent integrity protected or integrity protection verification failed, the NAS security initiation is performed as described in TS 33.501 [15], the UE includes the full Deregistration Request message as defined in TS 24.501 [25].
2. [Conditional] AMF to SMF (or V-SMF): Nsmf_PDUSession_ReleaseSMContext (SM Context ID).
If the UE has no established PDU Session over the target access indicated in step 1, then steps 2 to 5 are not executed. All PDU Sessions over the target access(es), which belong to the UE are released by the AMF sending Nsmf_PDUSession_ReleaseSMContext Request (SM Context ID) message to the SMF (or V-SMF) for each PDU Session. If the AMF determines that the secondary RAT usage reporting is required for the PDU Session, the AMF shall execute step 7 and 8 and then wait for the completion of step 8 to receive the secondary RAT usage data from the NG-RAN. After that, steps 2 to 6 in this procedure are performed to e.g. release the PDU Session(s).
For home routed roaming case, the V-SMF initiates the release of the PDU Session at the H-SMF by invoking the Nsmf_PDUSession_Release request.
3. [Conditional] The SMF (or H-SMF) releases all resources e.g. the IP address / Prefix(es) that were allocated to the PDU Session and releases the corresponding User Plane resources:
3a. [Conditional] The SMF (or H-SMF) sends N4 Session Release Request (N4 Session ID) message to the UPF(s) of the PDU Session. The UPF(s) shall drop any remaining packets of the PDU Session and release all tunnel resource and contexts associated with the N4 Session.
3b. [Conditional] The UPF(s) acknowledges the N4 Session Release Request by the transmission of an N4 Session Release Response (N4 Session ID) message to the SMF.
4. [Conditional] The SMF (or V-SMF) responds with Nsmf_PDUSession_ReleaseSMContext Response message.
For home routed roaming case, the H-SMF responds to the V-SMF with a Nsmf_PDUSession_Release response. The V-SMF releases the corresponding User Plane resources. The V-SMF responds to AMF with Nsmf_PDUSession_ReleaseSMContext Response message.
5a. [Conditional] If dynamic PCC applied to this session the SMF performs an SM Policy Association Termination procedure as defined in clause 4.16.6.
5b-c. [Conditional] If it is the last PDU Session the SMF is handling for the UE for the associated (DNN, S-NSSAI), the SMF unsubscribes from Session Management Subscription data changes notification with the UDM by means of the Nudm_SDM_Unsubscribe service operation. The SMF invokes the Nudm_UECM_Deregistration service operation so that the UDM removes the association it had stored between the SMF identity and the associated DNN and PDU Session ID.
6. [Conditional] If there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated AM Policy Association Termination procedure as defined in clause 4.16.3.2 delete the association with the PCF.
6a. [Conditional] If there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated UE Policy Association Termination procedure as defined in clause 4.16.13.1 delete the association with the PCF.
7. [Conditional] The AMF sends NAS message Deregistration Accept to UE depending on the Deregistration type i.e. if Deregistration type is switch-off, AMF does not send Deregistration Accept message.
7a [Conditional] 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 value of the Unavailability Period Duration.
8. [Conditional] AMF to AN: N2 UE Context Release Request (Cause)
If the target access for Deregistration procedure is 3GPP access or both 3GPP access and non-3GPP access and there is N2 signalling connection to NG-RAN, the AMF sends N2 UE Release command to NG-RAN with Cause set to Deregistration to release N2 signalling connection. The details of this step are covered by steps 2 to 4 in the AN Release procedure, as described in clause 4.2.6.
If the target access for Deregistration procedure is non-3GPP access or both 3GPP access and non-3GPP access and there is N2 signalling connection to the N3IWF/TNGF/W-AGF, the AMF sends N2 UE Release command to N3IWF/TNGF/W-AGF with Cause set to Deregistration to release N2 signalling connection. The details of this step are covered by steps 2 to 5 in the "Deregistration procedure for (un)trusted non-3gpp access", as described in clauses 4.12.3 / 4.12a.3 and in clause 7.2.1 of TS 23.316 [53] for W-5GAN access. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.2.3.3 Network-initiated Deregistration | The procedure depicted in Figure 4.2.2.3.3-1 shows Network-initiated Deregistration procedure. The AMF can initiate this procedure for either explicit (e.g. by O&M intervention or if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE or the UE's registered PLMN is not allowed to operate in the present UE location or if a disaster condition is no longer being applicable, the AMF initiates Network-initiated Deregistration to trigger the return of UEs to the PLMN that had a Disaster Condition) or implicit (e.g. expiring of Implicit Deregistration timer). The UDM can trigger this procedure for operator-determined purposes (e.g. if a disaster condition is no longer being applicable as specified in clause 5.40.5 of TS 23.501 [2]) to request the removal of a subscriber's RM context and PDU Session(s) of the UE.
If the Network-initiated Deregistration procedure is triggered for MBSR IAB-UE that is registered with authorization to act as MBSR, the AMF behaves as described in clause 5.35A.4 of TS 23.501 [2].
Figure 4.2.2.3.3-1: Network-initiated Deregistration
1. [Conditional] If the UDM wants to request the immediate deletion of a subscriber's RM contexts and PDU Sessions, the UDM shall send a Nudm_UECM_DeregistrationNotification (SUPI, Access Type, Removal Reason) message with Removal Reason set to Subscription Withdrawn to the registered AMF. The Access Type may indicate 3GPP Access, non-3GPP Access or both.
2. If the AMF receives Nudm_UECM_DeregistrationNotification in Step 1 with Removal Reason as Subscription Withdrawn, the AMF executes Deregistration procedure over the access(es) the Access Type indicates.
The AMF-initiated Deregistration procedure is either explicit (e.g. by O&M intervention or if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE) or implicit. The AMF does not send the Deregistration Request message to the UE for Implicit Deregistration. If the UE is in CM-CONNECTED state, the AMF may explicitly deregister the UE by sending a Deregistration Request message (Deregistration type, Access Type, [list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value]) to the UE. The Deregistration type may be set to Re-registration in which case the UE should re-register at the end of the Deregistration procedure. Access Type indicates whether Deregistration procedure applies to the 3GPP access or non-3GPP access, or both. If the Deregistration Request message is sent over 3GPP access and the UE is in CM-IDLE state in 3GPP access, the AMF pages the UE. The list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value, is provided if the AMF determines that no S-NSSAI can be provided to the UE in the Allowed NSSAI.
If the UE has established PDU Session associated with emergency service, the AMF shall not initiate Deregistration procedure. In this case, the AMF performs network requested PDU Session Release for any PDU session associated with non-emergency service as described in clause 4.3.4.
For NR satellite access, the AMF initiates Network-initiated Deregistration if it detects that the UE's registered PLMN is not allowed to operate in the present UE location. In this case, the AMF shall provide the appropriate cause value indicating the PLMN is not allowed to operate in the present UE location, see clause 5.4.11.4 of TS 23.501 [2].
If the network de-registration is triggered for a UE registered for Disaster Roaming due to a disaster condition no longer being applicable, the Deregistration Request shall contain the cause value "PLMN not allowed" and include a disaster return wait range as described in clause 5.5.2.3.1 of TS 24.501 [25] and as specified in clause 5.40.5 of TS 23.501 [2], the network, shall organise the return of the Disaster Roaming UEs in a manner that does not cause overload (e.g. of signalling) in the PLMN that previously had the Disaster Condition.
If the MBSR authorization state changes for a MBSR (IAB-UE) registered in network as specified in clause 5.35A.4 of TS 23.501 [2], based on operator configuration, the AMF triggers Deregistration procedure.
3. [Conditional] If the Deregistration procedure is triggered by UDM (Step 1), the AMF acknowledges the Nudm_UECM_DeRegistrationNotification to the UDM.
If Access Type indicates 3GPP Access or non-3GPP Access and AMF does not have UE context for another access type, or if Access Type indicates both, the AMF unsubscribes with the UDM using Nudm_SDM_Unsubscribe service operation.
4. [Conditional] If the UE has any established PDU Session over the target access for deregistration indicated in step 2, then step 2 ~ step 5 of UE-initiated Deregistration procedure in clause 4.2.2.3.2 is performed.
5. [Conditional] As in step 6 of Figure 4.2.2.3.2-1.
5a. [Conditional] As in step 6a of Figure 4.2.2.3.2-1.
6. [Conditional] If the UE receives the Deregistration Request message from the AMF in step 2, the UE sends a Deregistration Accept message to the AMF any time after step 2. The NG-RAN forwards this NAS message to the AMF along with the TAI+ Cell identity of the cell which the UE is using.
7. [Conditional] AMF to AN: N2 UE Context Release Request (Cause): as in step 8 of Figure 4.2.2.3.2.
If the UE is deregistered over only 3GPP access or non-3GPP access and the AMF does not have UE context for the other, or if the procedure applies to both access types, then at any time, AMF can unsubscribe from the UDM, otherwise the AMF can deregister from UDM using Nudm_UECM_Deregistration request by indicating its associating access type. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3 Service Request procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3.1 General | The Service Request procedure is used by a UE in CM-IDLE state or the 5GC to request the establishment of a secure connection to an AMF. The Service Request procedure is also used both when the UE is in CM-IDLE and in CM-CONNECTED to activate a User Plane connection for an established PDU Session. The Service Request procedure is also used to release the connection to an AMF.
For Home routed PDU sessions, by replacing the I-SMF with V-SMF and SMF with H-SMF the same procedure as defined in clause 4.23.4 is reused.
The UE shall not initiate a Service Request procedure if there is an ongoing Service Request procedure. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3.2 UE Triggered Service Request | The UE in CM-IDLE state initiates the Service Request procedure in order to send uplink signalling messages, user data, to request emergency services fallback, or as a response to a network paging request. The UE shall not initiate UE Triggered Service Request from CM-IDLE if there is a Service Gap timer running. After receiving the Service Request message, the AMF may perform authentication. After the establishment of the signalling connection to an AMF, the UE or network may send signalling messages, e.g. PDU Session establishment from UE to the SMF, via the AMF.
The Service Request procedure is used by a UE in CM-CONNECTED to request activation of a User Plane connection for PDU Sessions and to respond to a NAS Notification message from the AMF. When a User Plane connection for a PDU Session is activated, the AS layer in the UE indicates it to the NAS layer.
The Service Request procedure is used by the Multi-USIM UE over 3GPP access, in:
a) CM-CONNECTED state to request release of the UE connection, stop data transmission, discard of any pending data and optionally, store Paging Restriction Information; or
b) CM-IDLE state to request removal of Paging Restriction Information.
The Multi-USIM UE shall not execute UE triggered Service Request procedure with Release Request indication if regulatory prioritized services (e.g. emergency service, emergency callback waiting) are ongoing. After an emergency call, the UE shall not execute a UE triggered Service Request procedure with Release Request indication for a duration which is sufficient for emergency call back.
c) CM-IDLE state to respond to paging with a Reject Paging Indication that indicates that N1 connection shall be released and no user plane connection shall be established. The UE optionally provides the Paging Restriction Information. The UE may be unable to respond to paging with a Reject Paging Indication, e.g. due to UE implementation constraints.
NOTE 1: A Multi-USIM UE in RRC_INACTIVE/CM-CONNECTED state that decides to reject the RAN paging, requests the release of the UE connection as in bullet a) above. The UE can discard, by implementation, any data or NAS PDUs that it receives before it is released.
For any Service Request, the AMF responds with a Service Accept message to synchronize PDU Session status between UE and network, if necessary. The AMF responds with a Service Reject message to UE, if the Service Request cannot be accepted by network. The AMF may steer the UE from 5GC by rejecting the Service Request. The AMF should take into account the Preferred and Supported Network Behaviour (see clause 5.31.2 of TS 23.501 [2]) and availability of EPC to the UE before steering the UE from 5GC. The Service Reject message may include an indication or cause code requesting the UE to perform Registration procedure.
For this procedure, the impacted SMF and UPF, if any, are all under control of the PLMN serving the UE, e.g. in Home Routed roaming case the SMF and UPF in HPLMN are not involved if V-SMF relocation is not triggered.
For Service Request due to user data, network may take further actions if User Plane connection activation is not successful.
The procedure in this clause 4.2.3.2 is applicable to the scenarios with or without intermediate UPF and with or without intermediate UPF reselection.
If the UE initiates Service Request procedures via non-3GPP Access, functions defined in clause 4.12.4.1 are applied.
The User Plane of all PDU Sessions with redundant I-UPFs or with redundant N3/N9 tunnels for URLLC shall be activated during the Service Request procedure if the UE in CM-IDLE state initiates the Service Request procedure from 3GPP access. If the redundant I-UPFs are to be added/replaced/removed, the N4 Session procedure to manage the I-UPF is done for each I-UPF in steps 6c, 6d,7a, 7b, 8a, 8b, 9, 10, 17a,17b, 20a, 20b, 21a,21b, 22a and 22b of the figure 4.2.3.2-1. If the redundant N3/N9 tunnels are used for URLLC and the I-UPF is to be added/replaced/removed, the N4 Session procedure to update the tunnel is done for each N3/N9 tunnel in steps 6c, 6d, 7a, 7b, 8a, 8b, 9, 10, 17a, 17b. 20a, 20b, 21a and 21b of the figure 4.2.3.2-1.
Figure 4.2.3.2-1: UE Triggered Service Request procedure
1. UE to (R)AN: AN message (AN parameters, Service Request (List Of PDU Sessions To Be Activated, List Of Allowed PDU Sessions, security parameters, PDU Session status, 5G-S-TMSI, [NAS message container], Exempt Indication, [Release Request indication], [Paging Restriction Information], [Reject Paging Indication])).
The NAS message container shall be included if the UE is sending a Service Request message as an Initial NAS message and the UE needs to send non-cleartext IEs, see clause 4.4.6 of TS 24.501 [25].
The Multi-USIM UE in CM-CONNECTED state may include the Release Request indication and optionally Paging Restriction Information in the Service Request message over 3GPP access, if the UE intends to leave CM-CONNECTED state.
The Multi-USIM UE in CM-IDLE state may include the Release Request indication and not include Paging Restriction Information in the Service Request message over 3GPP access, if the UE intends to delete the Paging Restriction Information.
If the Multi-USIM UE in CM-IDLE state decides not to accept the paging, it may send a Service Request message including a Reject Paging Indication and optionally Paging Restriction Information, unless it is not able to send this message e.g. due to UE implementation constraints.
The List Of PDU Sessions To Be Activated is provided by UE when the UE wants to re-activate the PDU Session(s). The List Of Allowed PDU Sessions is provided by the UE when the Service Request is a response of a Paging or a NAS Notification for a PDU Session associated with non-3GPP access and identifies the PDU Sessions that can be transferred to 3GPP access.
In the case of NG-RAN:
- The AN parameters include 5G-S-TMSI, Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501 [2]), Establishment cause and may also include NSSAI information. 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 [2].
- The UE sends Service Request message towards the AMF encapsulated in an RRC message to the NG-RAN. The RRC message(s) that can be used to carry the 5G-S-TMSI and this NAS message are described in TS 38.331 [12] and TS 36.331 [16].
If the Service Request is triggered by the UE for user data, the UE identifies, using the List Of PDU Sessions To Be Activated, the PDU Session(s) for which the UP connections are to be activated in Service Request message. When the UE includes the List Of PDU Sessions To Be Activated, the UE shall indicate PDU Sessions only associated with the access the Service Request is related to. If the Service Request is triggered by the UE for signalling only, the UE doesn't identify any List Of PDU Sessions To Be Activated. If this procedure is triggered for paging response and the UE has at the same time some user data to be transferred, the UE identifies the PDU Session(s) whose UP connections are to be activated in Service Request message, by the List Of PDU Sessions To Be Activated. Otherwise the UE does not identify any PDU Session(s) in the Service Request message for paging response. As defined in TS 24.501 [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 or when the Service Request is triggered for signalling only or when the Service Request is triggered for paging response.
If the Service Request over 3GPP access is triggered in response to the paging or NAS Notification indicating non-3GPP access, the Service Request message shall identify the list of PDU Sessions associated with the non-3GPP access that can be re-activated over 3GPP access in the List Of Allowed PDU Sessions, as described in clause 4.2.3.3 (step 6) of this specification and in clause 5.6.8 of TS 23.501 [2]. When the UE over 3GPP access is in NB-N1 mode and the resulting number of PDU Sessions with user plane resources activated for the UE does not exceed the maximum number of supported user plane resources (0, 1 or 2), based on whether the UE supports UP data transfer and the UE's 5GMM Core Network Capability as described in clause 5.31.19 of TS 23.501 [2], the AMF shall notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed as defined in TS 24.501 [25].
If the Service Request is triggered to report PS Data Off status change and the UE is in Non-Allowed Area, the UE shall send Service Request message with an indication that the message is exempted from restriction (e.g. Non-Allowed Area). In this case, if the UE is in Non-Allowed Area, the UE shall not include the List Of PDU Sessions To Be Activated and as a result the always-on PDU Session is not re-activated during the Service Request procedure.
The PDU Session status indicates the PDU Sessions available in the UE.
The UE shall not trigger a Service Request procedure for a PDU Session corresponding to a LADN when the UE is outside the area of availability of the LADN.
NOTE 2: 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.
For UE in CM-CONNECTED state, only the List Of PDU Sessions To Be Activated and List Of Allowed PDU Sessions need to be included in the Service Request.
The UE shall not trigger a Service Request procedure for a PDU Session associated to an S-NSSAI if the S-NSSAI is not valid as per the S-NSSAI location availability information.
NOTE 3: A PDU Session associated to an S-NSSAI is not included in the List Of PDU Sessions To Be Activated when the S-NSSAI is not valid as per the S-NSSAI location availability information.
2. (R)AN to AMF: N2 Message (N2 parameters, Service Request).
Details of this step are described in TS 38.413 [10]. If the AMF can't handle the Service Request it will reject it.
When NG-RAN is used, the N2 parameters include the 5G-S-TMSI, Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501 [2]), Location information and Establishment cause, UE Context Request.
If the UE is in CM-IDLE state, the NG-RAN obtains the 5G-S-TMSI in RRC procedure. NG-RAN selects the AMF according to 5G-S-TMSI. The Location Information relates to the cell in which the UE is camping.
Based on the PDU Session status, the AMF may initiate PDU Session Release procedure in the network for the PDU Sessions whose PDU Session ID(s) were indicated by the UE as not available.
When the Establishment cause is associated with priority services (e.g. MPS, MCX), or when the AMF determines that the UE has priority subscription (e.g. MPS, MCX) in the UDM, 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 [17].
The AMF enforces the Mobility Restrictions as specified in clause 5.3.4.1.1 of TS 23.501 [2].
If there is a Service Gap timer running in AMF for the UE and the AMF is not waiting for a MT paging response from the UE and the Service Request is not for regulatory prioritized services like Emergency services or not for exception reporting, the AMF rejects the Service Request with an appropriate cause. In addition, AMF may also provide a UE with a Mobility Management Back-off timer set to the remaining value of the Service Gap timer.
If the AMF supports RACS and the AMF detects that the selected PLMN is different from the currently registered PLMN for the UE, the AMF determines the UE Radio Capability ID of the newly selected PLMN to the gNB as described in clause 5.4.4.1a of TS 23.501 [2].
For NR satellite access, the AMF may decide to 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 [2]. If the UE receives a Service Reject message with cause value indicating that the PLMN is not allowed to operate in the present UE location, the UE shall attempt to select a PLMN, as specified in TS 23.122 [22].
3a) AMF to (R)AN: N2 Request (security context, Mobility Restriction List, list of recommended cells / TAs / NG-RAN node identifiers).
If the 5G-AN had requested for UE Context or there is a requirement for AMF to provide this e.g. the AMF needs to initiate fallback procedure as in clause 4.13.4.2 for Emergency services, AMF initiates NGAP procedure as specified in TS 38.413 [10]. The AMF may provide the indication of NCR-MT authorization information in the UE Context. For UE in CM-IDLE state, 5G-AN stores the Security Context in the UE AN context. Mobility Restriction List is described in clause 5.3.4.1 of TS 23.501 [2].
The 5G-AN uses the Security Context to protect the messages exchanged with the UE as described in TS 33.501 [15].
If the NG-RAN node had provided the list of recommended cells / TAs / NG-RAN node identifiers during the AN Release procedure (see clause 4.2.6), the AMF shall include it in the N2 Request. The RAN may use this information to allocate the RAN Notification Area when the RAN decides to enable RRC_INACTIVE state for the UE.
3. If the Service Request was not sent integrity protected or integrity protection verification failed, the AMF shall reject the Service Request as stated in TS 24.501 [25].
If the UE in CM-IDLE state triggered the Service Request to establish a signalling connection only, after successful establishment of the signalling connection the UE and the network can exchange NAS signalling and steps 4 to 11 and 15 to 22 are skipped.
If the UE in Non-Allowed Area triggered the Service Request with an indication that the message is exempted from restriction (e.g. Non-Allowed Area), the AMF should accept the Service Request. In this case, if the UE is in Non-Allowed Area, the AMF rejects user plane setup request from the SMF except for emergency services.
If the procedure was triggered in response to paging or NAS notification indicating non-3GPP access and the AMF received N1 SM Container only from the SMF in step 3a of clause 4.2.3.3, the AMF sends the NAS signalling including the N1 SM Container to the UE in step 7 of clause 4.2.3.3 without updating the access associated to the PDU Session.
If the Service Request message is received over 3GPP access without a Release Request indication or a Reject Paging Indication, the AMF shall delete any stored Paging Restriction Information for this UE and stop restricting paging accordingly.
If the Service Request message over 3GPP access includes a Release Request indication or a Reject Paging Indication, then:
- the AMF may accept or reject the received 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.
- If no Paging Restriction Information is provided, no paging restrictions apply and the AMF removes any stored Paging Restriction Information from the UE context.
- no User Plane resources are established and instead the AMF triggers the AN Release procedure as described in clause 4.2.6.
NOTE 4: If AMF does not perform steps 5-7 before step 2 then some DL data might not be delivered to the UE.
If the procedure was triggered in response to paging and the Service Request message includes a Reject Paging Indication, the AMF initiates the UCU procedure as described in step 7 of clause 4.2.3.3 before the triggering of the AN Release procedure.
4. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID(s), Operation Type, UE location information, Access Type, RAT Type, UE presence in LADN service area, Indication of Access Type can be changed, [MO Exception Data Counter], [Satellite backhaul category], [GEO Satellite ID]).
The Nsmf_PDUSession_UpdateSMContext Request is invoked:
- If the UE identifies List Of PDU Sessions To Be Activated in the Service Request message;
- This procedure is triggered by the SMF but the PDU Session(s) identified by the UE correlates to other PDU Session ID(s) than the one triggering the procedure; or
- If this procedure is triggered by the SMF in response to paging or NAS notification indicating 3GPP access or if this step onwards is invoked following step 4a of clause 4.2.3.3 and the current UE location is outside the "Area of validity for the N2 SM information" provided by the SMF in step 3a of clause 4.2.3.3 or the "Area of validity for the N2 SM information" was not provided by the SMF in step 3a of clause 4.2.3.3, the AMF shall not send the N2 information provided by the SMF in step 3a of clause 4.2.3.3. Otherwise, if the current UE location is in the "Area of validity for the N2 SM information", steps 4 to 11 are skipped; or
- If this procedure is triggered by the SMF in response to paging or NAS notification indicating non-3GPP access and the AMF received N2 SM Information only, or both N1 SM Container and N2 SM Information in step 3a of clause 4.2.3.3.
If the DNN corresponds to an LADN then the "UE presence in LADN service area" indicates if the UE is IN or OUT of the LADN service area. If the AMF does not provide the "UE presence in LADN service area" indication and the SMF determines that the DNN corresponds to a LADN, then the SMF considers that the UE is OUT of the LADN service area.
The AMF determines the PDU Session(s) for which the UP connection(s) shall be activated and sends an Nsmf_PDUSession_UpdateSMContext Request to SMF(s) associated with the PDU Session(s) with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s). The AMF determines Access Type and RAT Type, see clause 4.2.2.2.1. If the RAT type is NB-IoT, the AMF shall ensure that the number of PDU session(s) for which UP connection(s) are active does not exceed this UE's maximum number of supported user plane resources (0, 1 or 2) based on whether the UE supports UP data transfer and the UE 5GMM Core Network Capability as described in clause 5.31.19 of TS 23.501 [2].
If the procedure was triggered in response to paging or NAS Notification indicating non-3GPP access, the AMF received N2 SM Information in step 3a of clause 4.2.3.3 and the PDU Session for which the UE was paged or notified is not in the List Of Allowed PDU Sessions provided by the UE, the AMF notifies the SMF that the UE is not reachable. For other PDU Sessions in the List Of Allowed PDU Sessions the Service Request Procedure succeeds without re-activating the User Plane of any PDU Sessions, unless they have also been included by the UE in the List Of PDU Sessions To Be Activated.
If the procedure was triggered in response to paging or NAS notification indicating non-3GPP access and the PDU Session for which the UE was paged or notified is in the List Of Allowed PDU Sessions provided by the UE and the AMF received N2 SM Information only or N1 SM Container and N2 SM Information from the SMF in step 3a of clause 4.2.3.3, the AMF notifies the SMF that the access type of the PDU session can be changed. The AMF discards any already received N1 SM Container and N2 SM Information. In Home Routed roaming case, the V-SMF triggers Nsmf_PDUSession_Update service operation towards the H-SMF to notify the access type of the PDU Session can be changed and the procedure continues as specified in clause 4.3.3.3 from step 1a to step 10.
If the UE is accessing via the NB-IoT RAT, the AMF may inform all (H-)SMFs whether the RRC establishment cause is set to "MO exception data", as described in clause 5.31.14.3 of TS 23.501 [2]. The AMF may immediately send the MO Exception Data Counter to the (H-)SMF.
If the AMF, based on configuration, as described in clauses 5.43.4 and 5.43.2 of TS 23.501 [2], is aware that satellite backhaul category and/or GEO Satellite ID has changed and needs to be updated to the SMF, the AMF includes the new Satellite backhaul category or new GEO Satellite ID or both as described in clauses 5.43.4 and 5.43.2 of TS 23.501 [2].
The AMF may receive a Service Request to establish another NAS signalling connection via a new NG-RAN while it has maintained an old NAS signalling connection for UE still via an old NG-RAN. The new NG-RAN and the old NG-RAN can be the same NG-RAN node. In this case, AMF shall trigger the AN release procedure toward the old NG-RAN to release the old NAS signalling connection as defined in clause 4.2.6 and:
- For the PDU Sessions indicated by the UE in the List Of PDU Sessions To Be Activated, the AMF requests the SMF to activate the PDU Session(s) immediately by performing this step 4; and
NOTE 5: This activates the UP of PDU Session(s) using resources of the new NG-RAN.
- For the PDU Sessions indicated by the old NG-RAN in the "List of PDU Session ID(s) with active N3 user plane" but not in the List Of PDU Sessions To Be Activated sent by the UE, the AMF requests the SMF to deactivate the PDU Session(s).
NOTE 6: This deactivates the UP of PDU Session(s) that are no more needed by the UE.
5a. Void.
5b. If the PDU Session ID corresponds to a LADN and the SMF determines that the UE is outside the area of availability of the LADN based on the "UE presence in LADN service area" from the AMF, the SMF decides to (based on local policies) either:
- keep the PDU Session, but reject the activation of User Plane connection for the PDU Session and inform the AMF about it. If the procedure has been triggered by a Network Triggered Service Request as described in clause 4.3.2.3, the SMF may notify the UPF that originated the Data Notification to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages; or
- to release the PDU Session: the SMF releases the PDU Session and informs the AMF that the PDU Session is released.
In any case of the two cases above the SMF answers to the AMF (step10) with an appropriate reject cause and the User Plane Activation of PDU Session is stopped.
Otherwise, based on the location info received from the AMF, the SMF checks the UPF Selection Criteria according to clause 6.3.3 of TS 23.501 [2] and determines to perform one of the following:
- accepts the activation of UP connection and continue using the current UPF(s);
- accepts the activation of UP connection and selects a new intermediate UPF (or add/remove an intermediate UPF), if the UE has moved out of the service area of the UPF that was previously connecting to the AN, while maintaining the UPF(s) acting as PDU Session Anchor. The steps to perform I-UPF addition/change/removal are described as conditional steps in the following of the current procedure; or
NOTE 7: If the old and/or new I-UPF implements an UL CL or BP functionality and a PDU Session Anchor for connectivity to the local access to the Data Network as described in clause 5.6.4.2 of TS 23.501 [2], the signalling described in the current clause is intended as the signalling to add, remove or change the PDU Session Anchor and must be complemented by the signalling to add, release or change the UL CL or BP as described respectively in clauses 4.3.5.4, 4.3.5.5 and 4.3.5.7.
- rejects the activation of UP connection of a PDU Session of SSC mode 2 and trigger re-establishment of the PDU Session after Service Request procedure to perform the allocation of a new UPF to act as PDU Session Anchor, e.g. the UE has moved out of the service area of the anchor UPF which is connecting to NG-RAN.
In the case that the SMF fails to find suitable I-UPF, the SMF decides to (based on local policies) either:
- trigger re-establishment of PDU Session. After Service Request procedure, SMF sends N1 SM message to the UE via the AMF by invoking Namf_Communication_N1N2MessageTransfer containing the cause indicating PDU Session re-establishment is required for the UE; or
- keep the PDU Session, but reject the activation request of User Plane connection for the PDU Session and inform the AMF about it; or
- release the PDU Session after Service Request procedure.
If the SMF has determined that the UE is performing Inter-RAT mobility to or from the NB-IoT RAT then the SMF uses the "PDU Session continuity at inter RAT mobility" to determine how to handle the PDU Session.
6a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request.
Depending on the network deployment, the CN Tunnel Info of UPF (PSA) allocated for N3 or N9 interface may be changed during the Service Request procedure, e.g. UPF connected to different IP domains. If different CN Tunnel Info need be used, the SMF sends N4 Session Modification Request message to UPF (PSA) and requests CN Tunnel Info providing the target Network Instance.
6b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response.
The UPF (PSA) sends an N4 Session Establishment Response message to the SMF. The UPF provides CN Tunnel Info to the SMF. The UPF (PSA) associate the CN Tunnel Info with UL Packet detection rules provided by the SMF.
If the redundant I-UPFs are used for URLLC, each I-UPF provides UL CN Tunnel Info for N3 interface to the SMF in the N4 Session Establishment Response message.
If the redundant N3 tunnels are used for URLLC, the UPF (PSA) provides redundant UL CN Tunnel Info for N3 interface to the SMF in N4 Session Establishment Response message.
6c. [Conditional] SMF to new UPF (intermediate): N4 Session Establishment Request.
If the SMF selects a new UPF to act as intermediate UPF for the PDU Session, or if the SMF selects to insert an intermediate UPF for a PDU Session which did not have an intermediate UPF, an N4 Session Establishment Request message is sent to the new UPF, providing Packet detection, Data forwarding, enforcement and reporting rules to be installed on the intermediate UPF. The CN Tunnel Info (on N9) of PSA, i.e. which is used to establish the N9 tunnel, for this PDU Session is also provided to the intermediate UPF.
If a new UPF is selected by the SMF to replace the old (intermediate) UPF, the SMF may also include a request for the new UPF to allocate a second tunnel endpoint for buffered DL data from the old I-UPF and to indicate via usage reporting end marker reception on this second tunnel. In this case, the UPF is instructed by the SMF to buffer the DL data it may receive at the same time from the UPF (PSA).
6d. New UPF (intermediate) to SMF: N4 Session Establishment Response.
The new intermediate UPF sends an N4 Session Establishment Response message to the SMF. The UPF provides DL CN Tunnel Info as requested by SMF in step 6c. The SMF starts a timer, to be used in step 22a to release the resource in old intermediate UPF if there is one.
7a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request.
If the SMF selects a new UPF to act as intermediate UPF for the PDU Session, the SMF sends N4 Session Modification Request message to PDU Session Anchor UPF, providing DL Tunnel Info from new intermediate UPF. If the new intermediate UPF was added for the PDU Session, the UPF (PSA) begins to send the DL data to the new I-UPF as indicated in the DL CN Tunnel Info. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to new I-UPF.
If the Service Request is triggered by the network and the SMF removes the old I-UPF but does not replace it with a new I-UPF, the SMF may also include a request for the UPF to allocate a second tunnel endpoint for buffered DL data from the old I-UPF and to indicate end marker reception on this second tunnel via usage reporting. In this case, the UPF (PSA) begins to buffer the DL data it may receive at the same time from the N6 interface. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to (R)AN.
7b. The UPF (PSA) sends N4 Session Modification Response message to SMF.
If requested by SMF, the UPF (PSA) sends DL CN tunnel info for the old (intermediate) UPF to the SMF. The SMF starts a timer, to be used in step 22a to release the resource in old intermediate UPF if there is one.
If the UPF that connects to RAN is the UPF (PSA) and if the SMF finds that the PDU Session is activated when receiving the Nsmf_PDUSession_UpdateSMContext Request in step 4 with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s), it deletes the AN Tunnel Info and initiates an N4 Session Modification procedure to remove Tunnel Info of AN in the UPF.
8a. [Conditional] SMF to old UPF (intermediate): N4 Session Modification Request (New UPF address, New UPF DL Tunnel ID)
If the service request is triggered by the network and the SMF removes the old (intermediate) UPF, the SMF sends the N4 Session Modification Request message to the old (intermediate) UPF, providing the DL Tunnel Info for the buffered DL data. If the SMF allocated new I-UPF, the DL Tunnel Info is from the new (intermediate) UPF acting as N3 terminating point. If the SMF did not allocate a new I-UPF, the DL Tunnel Info is from the new UPF (PSA) acting as N3 terminating point. The SMF starts a timer to monitor the forwarding tunnel as step 6d or 7b.
If the old I-UPF receives end marker packets and there is no associated tunnel to forward these packets, the old I-UPF discards the received end marker packets and does not send any Data Notification to SMF.
If the SMF find the PDU Session is activated when receiving the Nsmf_PDUSession_UpdateSMContext Request in step 4 with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s), it deletes the AN Tunnel Info and initiates an N4 Session Modification procedure to remove Tunnel Info of AN in the UPF.
8b. old UPF (intermediate) to SMF: N4 Session Modification Response
The old (intermediate) UPF sends N4 Session Modification Response message to SMF.
9. [Conditional] old UPF (intermediate) to new UPF (intermediate): buffered downlink data forwarding
If the I-UPF is changed and forwarding tunnel was established to the new I-UPF, the old (intermediate) UPF forwards its buffered data to the new (intermediate) UPF acting as N3 terminating point. If indicated by SMF in step 6c, the new I-UPF reports to SMF when end marker packet is received. Then the SMF initiates N4 Session Modification procedure to indicate the new I-UPF to send the buffered downlink packet(s) received from the UPF (PSA).
10. [Conditional] old UPF (intermediate) to UPF (PSA): buffered downlink data forwarding
If the old I-UPF is removed and no new I-UPF is assigned for the PDU Session and forwarding tunnel was established to the UPF (PSA), the old (intermediate) UPF forwards its buffered data to the UPF (PSA) acting as N3 Terminating Point. If indicated by SMF in step 7a, the UPF (PSA) reports to SMF when the end marker packet has been received. Then the SMF initiates N4 Session Modification procedure to request the UPF (PSA) to send the buffered DL data received from the N6 interface.
11. [Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM information (PDU Session ID, QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI, User Plane Security Enforcement, UE Integrity Protection Maximum Data Rate, RSN, PDU Session Pair ID), N1 SM Container, Cause) to the AMF. If the UPF that connects to RAN is the UPF (PSA), the N3 CN Tunnel Info is the UL CN Tunnel Info of the UPF (PSA). If the UPF that connects to RAN is the new intermediate UPF, the CN N3 Tunnel Info is the UL Tunnel Info of the intermediate UPF.
For the PDU Session with redundant I-UPFs or with redundant N3 tunnels for URLLC, the two UL N3 CN Tunnel Info are included, the SMF also indicates the NG-RAN that one of the CN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501 [2].
The SMF shall send N1 SM Container and/or N2 SM Information to the AMF when applicable. (e.g. when the SMF was notified from the AMF that the access type of the PDU Session can be changed in step 4).
For a PDU Session that the SMF has determined to accept the activation of UP connection in step 5a or 5b, the SMF generates only N2 SM information and sends Nsmf_PDUSession_UpdateSMContext Response to the AMF to establish the User Plane(s). The N2 SM information contains information that the AMF shall provide to the NG-RAN. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decided to change the PSA UPF for the SSC mode 3 PDU Session, the SMF triggers the change of SSC mode 3 PDU Session anchor as an independent procedure described in clause 4.3.5.2 or clause 4.3.5.3 after accepting the activation of UP of the PDU Session.
For each QoS Flow, the SMF may at most request one of the following to the NG-RAN:
- ECN marking for L4S at NG-RAN in the case of ECN marking for L4S in RAN as described in clause 5.37.3 of TS 23.501 [2]; or,
- Congestion information monitoring as described in clauses 5.45.3 and 5.37.4 of TS 23.501 [2]; or,
- provide information for ECN marking for L4S at UPF in the case of ECN marking for L4S by PSA UPF as described in clause 5.37.3 of TS 23.501 [2].
In the case of non-3GPP access, where the 5G-AN corresponds to an N3IWF or TNGF:
- For each QoS Flow, the SMF may request the following to the N3IWF or TNGF:
- ECN marking for L4S at N3IWF or TNGF in the case of ECN marking for L4S in non-3GPP access as described in clause 5.37.3 of TS 23.501 [2].
The SMF can reject the activation of UP of the PDU Session by including a cause in the Nsmf_PDUSession_UpdateSMContext Response. Following are some of the cases:
- If the PDU Session corresponds to a LADN and the UE is outside the area of availability of the LADN as described in step 5b;
- If the AMF notified the SMF that the UE is reachable only for regulatory prioritized service and the PDU Session to be activated is not for a regulatory prioritized service; or
- If the SMF decided to change the PSA UPF for the requested PDU Session as described in step 5b. In this case, after sending Nsmf_PDUSession_UpdateSMContext Response, the SMF triggers another procedure to instruct UE to re-establish the PDU Session as described in clause 4.3.5.1 for SSC mode 2.
- If the SMF received negative response in Step 6b due to UPF resource unavailability.
If the PDU Session has been assigned any EPS bearer ID, the SMF also includes the mapping between EPS bearer ID(s) and QFI(s) into the N2 SM information to be sent to the NG-RAN.
The User Plane Security Enforcement information is determined by the SMF upon PDU session establishment as described in clause 5.10.3 of TS 23.501 [2]. If the User Plane Security Enforcement information indicates that Integrity Protection is "Preferred" or "Required", the SMF also includes the UE Integrity Protection Maximum Data Rate.
The RSN and PDU Session Pair ID are included when applicable, as determined by the SMF during PDU Session establishment as described in clause 5.33.2.1 of TS 23.501 [2].
12. AMF to (R)AN: N2 Request (N2 SM information received from SMF, security context, Mobility Restriction List, UE-AMBR, List of UE-Slice-MBR(s) (optional and for 3GPP access type only), MM NAS Service Accept, list of recommended cells / TAs / NG-RAN node identifiers, UE Radio Capability, Core Network Assistance Information, Tracing Requirements, UE Radio Capability ID, QMC Configuration information). The Allowed NSSAI for the Access Type for the UE and if available, Partially Allowed NSSAI (as described in clause 5.15.17 of TS 23.501 [2]), are included in the N2 message. If the subscription information includes Tracing Requirements, the AMF includes Tracing Requirements in the N2 Request. If the subscription information includes QMC Configuration information, the AMF includes QMC Configuration information in the N2 Request. If the subscription information includes an Energy Saving Indicator as defined in clause 5.51.5 of TS 23.501 [2], the AMF includes the Energy Saving Indicator in the N2 Request.
Editor's note: Whether the Energy Saving Indicator is provided to the NG-RAN is FFS.
If the UE triggered the Service Request while in CM-CONNECTED state, only N2 SM information received from SMF and MM NAS Service Accept are included in the N2 Request.
If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-CONNECTED state, only N2 SM information received from SMF is included in the N2 Request.
If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-IDLE state, only N2 SM information received from SMF and MM NAS Service Accept is included in the N2 Request.
For a UE that was in CM-IDLE state when the Service Request was triggered, the NG-RAN stores the Security Context. If the Service Request is not triggered by UE for a signalling connection only, RAN also stores QoS Information for the QoS Flows of the PDU Sessions that are activated and N3 Tunnel IDs in the UE RAN context and Mobility Restriction List (as described in clause 5.3.4.1 of TS 23.501 [2]).
MM NAS Service Accept includes PDU Session status in AMF. Any local PDU Session Release during the Session Request procedure is indicated to the UE via the Session Status. PDU Session Reactivation Result is provided in Service Accept for the PDU sessions in the List Of PDU Sessions To Be Activated and the PDU Session in the List of Allowed PDU Sessions which has caused paging or NAS notification. If the PDU Session Reactivation Result of a PDU Session is failure, the cause of the failure is also provided. One of the possible causes of failure for a PDU Session reactivation is when the AMF determines that the UE is not inside the NS-AoS of the network slice of the PDU Session.
If the AMF accepts the Paging Restriction Information sent from the UE, the AMF informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the MM NAS Service Accept message.
If AMF receives multiple TAIs from the NG-RAN in step 2 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 MM NAS Service Accept message.
If there are multiple PDU Sessions that involves multiple SMFs, AMF does not need to wait for responses from all SMFs in step 11 before it sends N2 SM information to the RAN. However, the AMF shall wait for all responses from the SMFs before it sends MM NAS Service Accept message to the UE.
AMF shall include at least one N2 SM information from SMF if this step is triggered for PDU Session User Plane activation. AMF may send additional N2 SM information from SMFs in separate N2 message(s) (e.g. N2 tunnel setup request), if there is any. Alternatively, if multiple SMFs are involved, the AMF may send one N2 Request message to (R)AN after all the Nsmf_PDUSession_UpdateSMContext Response service operations from all the SMFs associated with the UE are received.
If the NG-RAN node had provided the list of recommended cells / TAs / NG-RAN node identifiers during the AN Release procedure (see clause 4.2.6), the AMF shall include it in the N2 Request. The NG-RAN may use this information to allocate the RAN Notification Area when the NG-RAN decides to enable RRC_INACTIVE state for the UE.
The AMF includes the UE's "RRC Inactive Assistance Information" as defined in clause 5.3.3.2.5 of TS 23.501 [2].
If the NG-RAN node does not support RACS and the AMF have UE Radio Capability ID but not the UE Radio Capability information, then AMF will use Nucmf_UECapabilityManagement_Resolve to try to retrieve the corresponding UE Radio Capability information.
If the NG-RAN node does not support RACS, or the AMF does not have UE Radio Capability ID in UE context, the AMF shall include the UE Radio Capability information, if available, to the NG-RAN node as described in TS 23.501 [2]. If the RAT Type is NB-IoT then NB-IoT specific UE Radio Access Capability Information is included instead, if available.
If AMF has UE Radio Capability ID in UE context valid for the PLMN the UE is currently in and the NG-RAN supports RACS, the AMF signals the UE Radio Capability ID. If the NG-RAN node does not have mapping between the UE Radio Capability ID and the corresponding UE radio capabilities, it shall use the non-UE associated procedure described in TS 38.413 [10] to retrieve the mapping from the AMF.
The AMF may include the Core Network Assistance Information which includes Core Network assisted RAN parameters tuning and Core Network assisted RAN paging information as defined in TS 23.501 [2].
If the UE included support for restriction of use of Enhanced Coverage, the AMF sends Enhanced Coverage Restricted information to the (R)AN in the N2 message.
If the UE and the AMF have negotiated to enable MICO mode 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 [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.
If the AMF accepted MICO mode in the last registration procedure 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 [2] and provides the Extended Connected Time value to the RAN in N2 message with Service Accept message. The RAN should keep the UE in RRC_CONNECTED state for an Extended Connected Time period in order to ensure the downlink data and/or signalling is delivered to the UE.
If the RAN receives two CN Tunnel Info for a PDU session in step 11 for redundant transmission, RAN also allocates two AN Tunnel Info correspondingly and indicate to SMF one of the AN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501 [2].
13. (R)AN to UE: The NG-RAN performs RRC Connection Reconfiguration with the UE depending on the QoS Information for all the QoS Flows of the PDU Sessions whose UP connections are activated and Data Radio Bearers. For a UE that was in CM-IDLE state, if the Service Request is not triggered by UE for a signalling connection only, the User Plane security is established at this step, which is described in detail in TS 38.331 [12] and TS 36.331 [16]. For a UE that was in CM-IDLE state, if the Service Request is triggered by UE for a signalling connection only, AS security context may be established in this step, which is described in detail in TS 38.331 [12] and TS 36.331 [16].
If the N2 Request includes a NAS message, the NG-RAN forwards the NAS message to the UE. The UE locally deletes context of PDU Sessions that are not available in 5GC.
NOTE 8: The reception of the Service Accept message does not imply the successful activation of the User Plane radio resources.
NOTE 9: If not all the requested User Plane AN resources are successfully activated, see TS 38.413 [10].
After the User Plane radio resources are setup, the uplink data from the UE can now be forwarded to NG-RAN. The NG-RAN sends the uplink data to the UPF address and Tunnel ID provided in the step 11.
If the NG-RAN can not establish redundant user plane for the PDU Session as indicated by the RSN parameter and PDU Session Pair ID, the NG-RAN takes the decision on how to proceed with the PDU Session as described in TS 23.501 [2].
14. [Conditional] (R)AN to AMF: N2 Request Ack (List of PDU Sessions To Be Established with N2 SM information (AN Tunnel Info, List of accepted QoS Flows for the PDU Sessions whose UP connections are activated, List of rejected QoS Flows for the PDU Sessions whose UP connections are activated, PDU Set Based Handling Support Indication), established QoS Flows status (active/not active) (for one of the following: congestion information monitoring, ECN marking for L4S at PSA UPF, ECN marking for L4S at NG-RAN, ECN marking for L4S at N3IWF or TNGF), List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element).
The message may include N2 SM information(s), e.g. AN Tunnel Info. NG-RAN may respond N2 SM information with separate N2 message (e.g. N2 tunnel setup response) if AMF sends separate N2 message in step 11.
If multiple N2 SM information are included in the N2 Request message in step 12, the N2 Request Ack includes multiple N2 SM information and information to enable the AMF to associate the responses to relevant SMF.
For List of PDU Sessions To Be Established, if the N2 SM information received from SMF included PDU Set QoS Parameters or DL PDU Set Information Marking Support Indication, 5G-AN includes the PDU Set Based Handling Support Indication in N2 SM information for the PDU Session that enables PDU Set based handling in 5G-AN as described in clause 5.37.5.3 of TS 23.501 [2].
15. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (N2 SM information, RAT Type, Access Type) per PDU Session to the SMF. The AMF determines Access Type and RAT Type, see clause 4.2.2.2.1.
If the AMF received N2 SM information (one or multiple) in step 14, then the AMF shall forward the N2 SM information to the relevant SMF per PDU Session ID. If the UE Time Zone has changed compared to the last reported UE Time Zone then the AMF shall include the UE Time Zone IE in this message.
If the PDU Session is moved from the non-3GPP access to 3GPP access (i.e. N3 tunnel for the PDU Session is established successfully), the SMF and AMF update associated access of the PDU Session. The UE updates associated access of the PDU Session when the user plane resource for the PDU Session is successfully established.
Procedure for unpausing a charging pause initiated earlier is specified in clause 4.4.4.
If a PDU Session is rejected by the serving NG-RAN with an indication that the PDU Session was rejected because User Plane Security Enforcement is not supported in the serving NG-RAN and the User Plane Enforcement Policy indicates "Required" as described in clause 5.10.3 of TS 23.501 [2], the SMF shall trigger the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session or to deactivate the UP connection of this PDU Session.
If some of the QoS Flows of a PDU Session are not accepted by the serving NG-RAN, the SMF shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session after this procedure is completed.
16. [Optional] SMF to PCF: If dynamic PCC is deployed and if Policy Control Request Trigger condition(s) have been met (e.g. change of Access Type, change of UE location), performs SMF initiated SM Policy Modification procedure as defined in clause 4.16.5.1. The PCF may provide updated policies.
17a. [Conditional] SMF to new intermediate UPF: N4 Session Modification Request (AN Tunnel Info and List of accepted QFI(s)).
If the SMF selected a new UPF to act as intermediate UPF for the PDU Session in step 5b, the SMF initiates a N4 Session Modification procedure to the new I-UPF and provides AN Tunnel Info. The Downlink Data from the new I-UPF can now be forwarded to NG-RAN and UE.
17b. [Conditional] UPF to SMF: N4 Session Modification Response.
18a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request (AN Tunnel Info, List of rejected QoS Flows).
If a User Plane is to be setup or modified and after the modification there is no I-UPF, the SMF initiates a N4 Session Modification procedure to UPF (PSA) and provides AN Tunnel Info. The Downlink Data from the UPF (PSA) can now be forwarded to NG-RAN and UE.
For QoS Flows in the List of rejected QoS Flows, the SMF shall instruct the UPF to remove the rules (e.g. Packet Detection Rules etc.) which are associated with the QoS Flows.
If SMF decides to perform redundant transmission for one or more QoS Flows of the PDU, the SMF also indicates the UPF (PSA) to perform packet duplication for the QoS Flow(s) in downlink direction by forwarding rules.
If the PCC rule(s) are updated in step 16, the SMF may initiate a N4 Session Modification procedure to UPF (PSA) based on the updated PCC rule(s).
18b. [Conditional] UPF to SMF: N4 Session Modification Response.
19. [Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response.
20a. [Conditional] SMF to new UPF (intermediate): N4 Session Modification Request.
If forwarding tunnel has been established to the new I-UPF and if the timer SMF set for forwarding tunnel at step 8a has expired, SMF sends N4 Session modification request to new (intermediate) UPF acting as N3 terminating point to release the forwarding tunnel.
20b. [Conditional] new UPF (intermediate) to SMF: N4 Session modification response.
New (intermediate) UPF acting as N3 terminating point sends N4 Session Modification response to SMF.
21a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request.
If forwarding tunnel has been established to the UPF (PSA) and if the timer SMF set for forwarding tunnel at step 7b has expired, SMF sends N4 Session modification request to UPF (PSA) acting as N3 Terminating Point to release the forwarding tunnel.
21b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response.
UPF (PSA) acting as N3 Terminating Point sends N4 Session Modification Response to SMF.
22a. [Conditional] SMF to old UPF: N4 Session Modification Request or N4 Session Release Request.
If the SMF decided to continue using the old UPF in step 5b, the SMF sends an N4 Session Modification Request, providing AN Tunnel Info.
If the SMF decided to select a new UPF to act as intermediate UPF in step 5b and the old UPF is not PSA UPF, the SMF initiates resource release, after timer in step 6b or 7b expires, by sending an N4 Session Release Request (Release Cause) to the old intermediate UPF.
22b. [Conditional] Old intermediate UPF to SMF: N4 Session Modification Response or N4 Session Release Response.
The old UPF acknowledges with an N4 Session Modification Response or N4 Session Release Response message to confirm the modification or release of resources.
For the mobility related events described in clause 4.15.4, the AMF invokes the Namf_EventExposure_Notify service operation after step 4.
Upon reception of the Namf_EventExposure_Notify with an indication that the UE is reachable, if the SMF has pending DL data the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to establish the User Plane(s) for the PDU Sessions, otherwise the SMF resumes sending DL data notifications to the AMF in the case of DL data.
Upon reception of the Namf_EventExposure_Notify with an indication that UE is reachable only for regulatory prioritized service, the SMF deactivates the PDU Session if the service of the PDU Session is not regulatory prioritized. For home routed roaming case, the V-SMF triggers the deactivation of the PDU Session, in addition, the H-SMF refrains from sending downlink signalling if the signalling is not related to regulatory prioritized service upon receiving the notification. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.3.3 Network Triggered Service Request | This procedure is used when the network needs to signal (e.g. N1 signalling to UE, Mobile-terminated SMS, User Plane connection activation for PDU Session(s) to deliver mobile terminating user data) with a UE. When the procedure is triggered by SMSF, PCF, LMF, GMLC, NEF, AMF or UDM, the SMF (and UPF, if applicable) in the following figure should be replaced by the respective NF. 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. If the UE is in CM-IDLE state or CM-CONNECTED state in 3GPP access, the network initiates a Network Triggered Service Request procedure. If the UE is in CM-IDLE state and asynchronous type communication is not activated, the network sends a Paging Request to (R)AN/UE. The Paging Request triggers the UE Triggered Service Request procedure in the UE. If asynchronous type communication is activated, the network stores the received message and forward the message to the (R)AN and/or the UE (i.e. synchronizes the context with the (R)AN and/or the UE) when the UE enters CM-CONNECTED state.
If the UE is in CM-IDLE state in non-3GPP access and if the UE is simultaneously registered over 3GPP and non-3GPP accesses in a PLMN, the network shall initiate a Network Triggered Service Request procedure over 3GPP access.
If the UE is in CM-IDLE state in 3GPP access and in CM-CONNECTED state in non-3GPP access and if the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN, the network may initiate a Network Triggered Service Request procedure for 3GPP access via non-3GPP access.
For this procedure, the impacted SMF and UPF are all under control of the PLMN serving the UE, e.g. in Home Routed roaming case the SMF and UPF in HPLMN are not involved.
The procedure below covers the following non exhaustive list of use-cases for 3GPP access (detailed conditions of when the steps apply are stated in the procedure below):
- The SMF needs to setup N3 tunnel to deliver downlink packet to the UE for a PDU Session and the UE is in CM-IDLE state: Step 3a contains an N2 message and Step 4b (paging) is performed.
- The SMF needs to setup N3 tunnel to deliver downlink packet to the UE for a PDU Session and the UE is in CM-CONNECTED state: Step 3a contains an N2 message and Step 4a (UP reactivation) is performed.
- NF (e.g. SMF, SMSF, PCF or LMF) needs to send an N1 message to the UE, using the Namf_Communication_N1N2MessageTransfer service operation and the UE is in CM-IDLE state: Step 3a contains an N1 message, Step 3b contains cause "Attempting to reach UE" and Step 4b (paging) occurs.
- The LMF triggers AMF, using the Namf_Communication_N1N2MessageTransfer service operation, to setup a NAS connection with the UE and the UE is in CM-IDLE state: Step 3b contains cause "Attempting to reach UE" and step 4b (paging) occurs.
- The GMLC triggers AMF, using the Namf_Location_ProvideLocation service operation, to setup a NAS connection with the UE and the UE is in CM-IDLE state: Step 4b (paging) occurs.
- The PCF needs to send a message to the UE, using the Npcf_AMPolicyControl_Create Response service operation, or the Npcf_AMPolicyControl_UpdateNotify service operation and the UE is in CM-IDLE state: Step 3a contains a message and step 4b (paging) occurs.
- NF (e.g. SMSF or SMF) triggers AMF, using the Namf_MT_EnableUEReachability service operation, to setup a NAS connection with the UE and the UE is in CM-IDLE state: The trigger is specific to the procedure and Step 4b (paging) occurs.
As described in clause 4.2.4.2, the AMF may also trigger the Network Triggered Service Request before the AMF sends a UE Configuration Update.
Figure 4.2.3.3-1: Network Triggered Service Request
1. When a UPF receives downlink data for a PDU Session and there is no AN Tunnel Info stored in UPF for the PDU Session, based on the instruction from the SMF (as described in clause 5.8.3 of TS 23.501 [2]), the UPF may buffer the downlink data (steps 2a and 2b), or forward the downlink data to the SMF (step 2c).
2a. UPF to SMF: Data Notification (N4 Session ID, Information to identify the QoS Flow for the DL data packet, DSCP).
- On arrival of the first downlink data packet for any QoS Flow, the UPF shall send Data Notification message to the SMF, if the SMF has not previously notified the UPF to not send the Data Notification to the SMF (in which case the next steps are skipped).
- If the UPF receives downlink data packets for another QoS Flow in the same PDU Session, the UPF shall send another Data Notification message to the SMF.
- If the Paging Policy Differentiation feature (as specified in clause 5.4.3 of TS 23.501 [2]) is supported by the UPF and if the PDU Session type is IP, the UPF shall also include the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the downlink data packet and the information to identify the QoS Flow for the DL data packet.
2b. SMF to UPF: Data Notification Ack.
2c. The UPF forwards the downlink data packets towards the SMF if the SMF instructed the UPF to do so (i.e. the SMF will buffer the data packets).
- If the Paging Policy Differentiation feature is supported by the SMF and if the PDU Session type is IP, the SMF determines the Paging Policy Indicator based on the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the received downlink data packet and identifies the corresponding QoS Flow from the QFI of the received DL data packet.
3a. [Conditional] SMF to AMF: Namf_Communication_N1N2MessageTransfer (SUPI, PDU Session ID, N1 SM container (SM message), N2 SM information (QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI), Area of validity for N2 SM information, ARP, Paging Policy Indicator, 5QI, N1N2TransferFailure Notification Target Address, Extended Buffering support), or NF to AMF: Namf_Communication_N1N2MessageTransfer (SUPI, N1 message).
The SMF shall not include both N1 SM Container and N2 SM Information in Namf_Communication_N1N2MessageTransfer unless the N1 SM Container is related to the N2 SM Information.
If this step is triggered by a notification from UPF, upon reception of a Data Notification message, for a PDU Session corresponding to a LADN, the SMF takes actions as specified in clause 5.6.5 of TS 23.501 [2]. The SMF may notify the UPF that originated the Data Notification to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages.
Otherwise, the SMF determines whether to contact the AMF. The SMF does not contact the AMF:
- if the SMF had previously been notified that the UE is unreachable; or
- if the UE is reachable only for regulatory prioritized service and the PDU Session is not for regulatory prioritized service.
The SMF determines the AMF and invokes the Namf_Communication_N1N2MessageTransfer to the AMF including the PDU Session ID of the PDU Session. If this step is triggered by a notification from the UPF in step 2a, the SMF determines the PDU Session ID based on the N4 Session ID received in step 2a.
The SMF determines whether Extended Buffering applies based on local policy and the capability of the SMF (for SMF-based buffering) or the capability of the UPF (for UPF-based buffering). If Extended Buffering applies, the SMF includes "Extended Buffering support" indication in Namf_Communication_N1N2MessageTransfer.
If the SMF, while waiting for the User Plane Connection to be activated, receives any additional Data Notification message or, in the case that the SMF buffers the data packets, additional data packets for a QoS Flow associated with a higher priority (i.e. ARP priority level) than the priority indicated to the AMF in the previous Namf_Communication_N1N2MessageTransfer, or the SMF derive a different Paging Policy Indicator according to the additional Data Notification or the DSCP of the data packet, the SMF invokes a new Namf_Communication_N1N2MessageTransfer indicating the higher priority or different Paging Policy Indicator to the AMF.
If the SMF, while waiting for the User Plane to be activated, receives a message from a new AMF other than the one to which the SMF invoked theNamf_Communication_N1N2MessageTransfer, the SMF re-invokes the Namf_Communication_N1N2MessageTransfer towards the new AMF.
When supporting Paging Policy Differentiation, the SMF determines the Paging Policy Indicator related to the downlink data that has been received from the UPF or triggered the Data Notification message, based on the DSCP as described in clause 5.4.3 of TS 23.501 [2] and indicates the Paging Policy Indicator in the Namf_Communication_N1N2MessageTransfer.
NOTE 1: AMF may receive request message(s) from other network functions which leads to signalling towards UE/RAN, e.g. Network-initiated Deregistration, SMF initiated PDU Session Modification. If the UE is in CM-CONNECTED state and the AMF only delivers N1 message towards UE, the flow continues in step 6 below.
The N2 SM information is optional and is not provided e.g. in the case that the SMF only wants to send an N1 message such as PDU Session Modification Command with only updating the UE with a PCO.
For PDU session with user plane in Suspend mode (i.e. applying User Plane CIoT 5GS Optimisation as specified in clause 5.31.8 of TS 23.501 [2]) for 3GPP access, the SMF uses Namf_MT_EnableUEReachability service operation if there is neither N1 SM container nor N2 SM information to be delivered by SMF.
3b. [conditional] The AMF responds to the SMF.
If the UE is in CM-IDLE state at the AMF and the AMF is able to page the UE the AMF sends a Namf_Communication_N1N2MessageTransfer response to the SMF immediately to indicate to the SMF that AMF is attempting to reach UE and the N2 SM information provided in step 3a, may be ignored by the AMF once the UE is reachable and the SMF may be asked to provide the N2 SM information again.
While waiting for the UE to respond to a previous paging request, if the AMF receives an Namf_Communication_N1N2MessageTransfer Request message with the same or a lower priority than the previous message triggering the paging, or if the AMF has determined not to trigger additional paging requests for this UE based on local policy, the AMF rejects the Namf_Communication_N1N2MessageTransfer Request message.
If the UE is in CM-CONNECTED state at the AMF then the AMF sends a Namf_Communication_N1N2MessageTransfer response to the SMF immediately to indicate that the N1/N2 message has been sent out.
If the UE is in CM-IDLE state and the AMF determines that the UE is not reachable for paging, the AMF shall send an Namf_Communication_N1N2MessageTransfer response to the NF from which AMF received the request message in step 3a to indicate that the UE is not reachable, or the AMF performs asynchronous type communication and stores the UE context based on the received message, it shall send an Namf_Communication_N1N2MessageTransfer response to indicate that asynchronous type communication is invoked. If asynchronous type communication is invoked, the AMF initiates communication with the UE and (R)AN when the UE is reachable e.g. when the UE enters CM-CONNECTED state.
If the AMF detects that the UE context contains Paging Restriction Information, the AMF may block the paging for this UE, based on local policy and the stored Paging Restriction Information (see clause 5.38.1 of TS 23.501 [2]). If the AMF blocks paging, the AMF sends Namf_Communication_N1N2MessageTransfer response with an indication that its request has been rejected due to restricted paging to the NF from which AMF received the request message in step 3a.
If the AMF has determined the UE is unreachable for the SMF (e.g. due to the UE in MICO mode, the UE using extended idle mode DRX or the UE is only registered over non-3GPP access and its state is CM-IDLE), then the AMF rejects the request from the SMF. The AMF may include in the reject message an indication that the SMF need not trigger the Namf_Communication_N1N2MessageTransfer Request to the AMF, if the SMF has not subscribed to the event of the UE reachability. If the SMF included the Extended Buffering Support indication, the AMF indicates the Estimated Maximum Wait time, in the reject message, for the SMF to determine the Extended Buffering time. If the UE is in MICO mode, the AMF determines the Estimated Maximum Wait time based on the next expected periodic registration by the UE or by implementation. If the UE is using extended idle mode DRX, the AMF determines the Estimated Maximum Wait time based on the start of the next Paging Time Window. The AMF stores an indication that the SMF has been informed that the UE is unreachable.
If the AMF has determined the UE is reachable and the AMF detects the UE is in a Non-Allowed Area unless the request from the SMF is for regulatory prioritized service, the AMF rejects the request from the SMF and notifies the SMF that the UE is reachable only for regulatory prioritized service. The AMF stores an indication that the SMF has been informed that the UE is reachable only for regulatory prioritized service. If the AMF cannot determine whether the UE is in a Non-Allowed Area (e.g. due to UE's Registration Area containing both Allowed area and Non-Allowed Area), the procedure continues in step 4.
If the Registration procedure with AMF change is in progress when the old AMF receives the Namf_Communication_N1N2MessageTransfer, the old AMF may reject the request with an indication that the Namf_Communication_N1N2MessageTransfer has been temporarily rejected.
Upon reception of an Namf_Communication_N1N2MessageTransfer response with an indication that its request has been temporarily rejected, the SMF shall start a locally configured guard timer and wait for any message to come from an AMF. Upon reception of a message from an AMF, the SMF shall re-invoke the Namf_Communication_N1N2MessageTransfer (with N2 SM info and/or N1 SM info) to the AMF from which it received the message. Otherwise the SMF takes the step 3c at expiry of the guard timer. If the SMF decides that the control plane buffering applies, the SMF shall request UPF to start forwarding the downlink data PDU towards the SMF.
3c. [Conditional] SMF responds to the UPF
SMF may notify the UPF about the User Plane setup failure.
If the SMF receives an indication from the AMF that the UE is unreachable or reachable only for regulatory prioritized service and the SMF determines that Extended Buffering does not apply, the SMF may, based on network policies, either:
- indicate to the UPF to stop sending Data Notifications;
- indicate to the UPF to stop buffering DL data and discard the buffered data;
- indicate to the UPF to stop sending Data Notifications and stop buffering DL data and discard the buffered data; or
- refrains from sending further Namf_Communication_N1N2MessageTransfer message for DL data to the AMF while the UE is unreachable.
Then the SMF subscribes to the AMF for UE reachability event notifications.
Based on operator policies, the SMF applies the pause of charging procedure as specified in clause 4.4.4.
If the SMF receives an indication from the AMF that the Namf_Communication_N1N2MessageTransfer message requested from an SMF has been temporarily rejected, the SMF may, based on network policies, indicate to the UPF to apply temporary buffering.
If the SMF receives an "Estimated Maximum Wait time" from the AMF and Extended Buffering applies, the SMF may either:
- If the DL data buffering in the SMF applies, store the DL Data for an Extended Buffering time. The SMF does not send any additional Namf_Communication_N1N2MessageTransfer message if subsequent downlink data packets are received. If the Extended Buffering timer expires, the SMF discards the buffered downlink data.
- If the DL data buffering in the UPF applies, send a Failure indication with an indication to the UPF to buffer the DL data with an Extended Buffering time and optionally a DL Buffering Suggested Packet Count. The Suggested Number of Downlink Packets network configuration parameter (if available) may be used to derive the value for DL Buffering Suggested Packet Count. The SMF may also indicate to the UPF to stop sending Data Notifications.
The Extended Buffering time is determined by the SMF and should be larger or equal to the Estimated Maximum Wait time received from the AMF.
If the UPF receives an Extended Buffering indication from the SMF, the UPF initiates Extended Buffering of the downlink data and starts an Extended Buffering timer. If the Extended Buffering timer expires, the UPF discards the buffered downlink data.
4a. [Conditional] If the UE is in CM-CONNECTED state in the access associated with the PDU Session ID received from the SMF in step 3a, the steps 4 to 22 in UE Triggered Service Request procedure (see clause 4.2.3.2) are performed for this PDU Session (i.e. establish the radio resources and in the case that the User Plane is to be activated, to establish the N3 tunnel) without sending a Paging message to the (R)AN node and the UE. In step 12 of clause 4.2.3.2, the AMF does not send the NAS Service Accept message to the UE. The rest of this procedure is omitted.
4b. [Conditional] If the UE is in CM-IDLE state in 3GPP access and the PDU Session ID received from the SMF in step 3a has been associated with 3GPP access and based on local policy the AMF decides to notify the UE through 3GPP access even when UE is in CM-CONNECTED state for non-3GPP access, the AMF may send a Paging message to NG-RAN node(s) via 3GPP access.
If the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN, the UE is in CM-IDLE state in both 3GPP access and non-3GPP access and the PDU Session ID in step 3a is associated with non-3GPP access, the AMF sends a Paging message with associated access "non-3GPP" to NG-RAN node(s) via 3GPP access.
If the UE is in RM-REGISTERED state and CM-IDLE and reachable in 3GPP access, the AMF sends a Paging message (NAS ID for paging, Registration Area list, Paging DRX length, Paging Priority, access associated to the PDU Session, Enhanced Coverage Restricted information, WUS Assistance Information) to (R)AN node(s) belonging to the Registration Area(s) in which the UE is registered, then the NG-RAN node pages the UE, including the access associated to the PDU Session in the paging message if received from the AMF, see TS 38.331 [12]. If extended idle mode DRX was accepted by the AMF in the last registration procedure, the AMF includes extended idle mode DRX cycle length and Paging Time Window in the Paging message. The AMF shall ensure that the correct Paging DRX length is provided based on the accepted UE Specific DRX of the current RAT.
NOTE 2: The usage of the Access associated with a PDU Session when paging an UE is defined in clause 5.6.8 of TS 23.501 [2].
NOTE 3: This step is performed also when the UE and the network support User Plane CIoT 5GS Optimisation and the previous RRC connection has been suspended. For PDU session in Suspend mode, the SMF uses the service operation as described in step 3a.
Different paging strategies may be configured in the AMF for different combinations of DNN, Paging Policy Indicator (if supported), ARP and 5QI.
For RRC_INACTIVE state, the paging strategies may be configured in the (R)AN for different combinations of Paging Policy Indicator, ARP and 5QI.
Paging Priority is included only:
- if the AMF receives an Namf_Communication_N1N2MessageTransfer message with an ARP value associated with priority services (e.g. MPS, MCS), as configured by the operator.
- if the AMF receives an Nudm_SDM_Notification message for a change in priority subscription (e.g. MPS), with a priority value as configured by the operator.
- One Paging Priority level can be used for multiple ARP values. The mapping of ARP values to Paging Priority level (or levels) is configured by operator policy in the AMF and in NG-RAN.
The (R)AN may prioritise the paging of UEs according to the Paging Priority.
NOTE 4: Paging priority indication is also included for MT-SMS related requests from the SMS-GMSC as in clause 4.13.3.6.
If the AMF, while waiting for a UE response to the Paging Request message sent without Paging Priority, receives an Namf_Communication_N1N2MessageTransfer message, which indicates an ARP value associated with priority services (e.g. MPS, MCS), as configured by the operator, the AMF shall send another paging message with the suitable Paging Priority. For subsequent received Namf_Communication_N1N2MessageTransfer messages with the same or higher priority, the AMF may determine whether to send the Paging message with suitable Paging Priority based on local policy.
If the AMF has assigned PEIPS Assistance Information or LP-WUSPS Assistance Information, the AMF shall provide the information. The NG-RAN uses this information as described in TS 23.501 [2].
Paging strategies may include:
- paging retransmission scheme (e.g. how frequently the paging is repeated or with what time interval);
- determining whether to send the Paging message to the (R)AN nodes during certain AMF high load conditions;
- whether to apply sub-area based paging (e.g. first page in the last known cell-id or TA and retransmission in all registered TAs).
NOTE 5: Setting of Paging Priority in the Paging message is independent from any paging strategy.
The AMF and the (R)AN may support further paging optimisations in order to reduce the signalling load and the network resources used to successfully page a UE by one or several of the following means:
- by the AMF implementing specific paging strategies (e.g. the N2 Paging message is sent to the (R)AN nodes that served the UE last);
- by the AMF considering Information On Recommended Cells And NG-RAN nodes provided by the (R)AN at transition to CM-IDLE state. The AMF takes the (R)AN nodes related part of this information into account to determine the (R)AN nodes to be paged and provides the information on recommended cells within the N2 Paging message to each of these (R)AN nodes;
- by the (R)AN considering the Paging Attempt Count Information provided by the AMF at paging.
If the UE Radio Capability for Paging Information is available in the AMF, the AMF adds the UE Radio Capability for Paging Information in the N2 Paging message to the (R)AN nodes.
If the Information On Recommended Cells And (R)AN nodes For Paging is available in the AMF, the AMF shall take that information into account to determine the (R)AN nodes for paging and when paging a (R)AN node, the AMF may transparently convey the information on recommended cells to the (R)AN node.
The AMF may include in the N2 Paging message(s) the paging attempt count information. The paging attempt count information shall be the same for all (R)AN nodes selected by the AMF for paging.
If the AMF has Paging Assistance Data for CE capable UE stored in the UE Context in AMF and Enhanced Coverage is not restricted for the UE then the AMF shall include Paging Assistance Data for CE capable UE in the N2 paging message for all NG-RAN nodes selected by the AMF for paging.
The AMF may include in the N2 Paging message(s) the WUS Assistance Information, if available. If the WUS Assistance Information is included by the N2 Paging message, the NG-eNB takes it into account when paging the UE (see TS 36.300 [46]).
The AMF may include in the N2 paging message the PLMN ID(s) of Serving PLMN and equivalent PLMN(s) supported by NG-RAN and corresponding CAG information per PLMN ID which including an Allowed CAG list and optionally an indication whether the UE is only allowed to access 5GS via CAG cells, if available. If the above information is included in N2 paging message, the NG-RAN node may take it into account when determining the cells where paging will be performed (see TS 38.413 [10]).
If the UE and NG-eNB support WUS, then:
- if the NGAP Paging message contains the Assistance Data for Recommended Cells IE (see TS 38.413 [10]), the NG-eNB shall only broadcast the UE's Wake Up Signal in the last used cell;
- else (i.e. the Assistance Data for Recommended Cells IE is not included in the NGAP Paging message) the eNodeB should not broadcast the UE's Wake Up Signal.
If the network supports the Paging Cause Indication for Voice Service feature and if the UE context in the AMF indicates that the UE supports the Paging Cause Indication for Voice Service feature, the AMF should provide the Voice Service Indication in the NGAP Paging message only when the AMF detects that the downlink data which triggers the Paging message is related to voice service, as specified in clause 5.38.3 of TS 23.501 [2]. If the NG RAN supporting the Paging Cause Indication for Voice Service feature receives the Voice Service Indication, it provides the Voice Service Indication in the Paging message and sends the Paging message to the UE.
4c. [Conditional] If the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN and the UE is in CM-CONNECTED state in 3GPP access and the PDU Session ID in step 3a is associated with non-3GPP access, the AMF sends a NAS Notification message containing the non-3GPP Access Type to the UE over 3GPP access and sets a Notification timer. Step 5 is omitted.
If the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN and the UE is in CM-CONNECTED state for non-3GPP access and in CM-IDLE for 3GPP access and if the PDU Session ID in step 3a is associated with 3GPP access and based on local policy the AMF decides to notify the UE through non-3GPP access, the AMF may send a NAS Notification message containing the 3GPP Access Type to the UE over non-3GPP access and sets a Notification timer. If the network supports the Paging Cause Indication for Voice Service feature and if the UE context in the AMF indicates that the UE supports the Paging Cause Indication for Voice Service feature and the AMF detects that the downlink data is related to voice service, as specified in clause 5.38.3 of TS 23.501 [2], the AMF shall send Paging message over 3GPP access as specified in step 4b.
NOTE 6: This step is performed also when the UE and the network support User Plane CIoT 5GS Optimisation in 3GPP access and the previous RRC connection has been suspended.
5. [Conditional] AMF to SMF: Namf_Communication_N1N2Transfer Failure Notification.
The AMF supervises the paging procedure with a timer. If the AMF receives no response from the UE to the Paging Request message, the AMF may apply further paging according to any applicable paging strategy described in step 4b.
The AMF notifies the SMF by sending Namf_Communications_N1N2MessageTransfer Failure Notification to the Notification Target Address provided by the SMF in step 3a if the UE does not respond to paging, unless the AMF is aware of an ongoing MM procedure that prevents the UE from responding, i.e. the AMF receives an N14 Context Request message indicating that the UE performs Registration procedure with another AMF.
When a Namf_Communication_N1N2Transfer Failure Notification is received, SMF informs the UPF (if applicable).
Procedure for pause of charging at SMF is specified in clause 4.4.4.
6. If the UE is in CM-IDLE state in 3GPP access, upon reception of paging request for a PDU Session associated to 3GPP access, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2) or, if the UE is enabled to use User Plane CIoT 5GS Optimisation and there is suspended access stratum context stored in the UE, the UE initiates the Connection Resume in CM-IDLE with Suspend procedure (clause 4.8.2.3). To support the buffered data forwarding, the SMF instruct the UPF to establish a Data forwarding tunnel between the old UPF and the new UPF or to the PSA as described at steps 6a, 7a, 8a of clause 4.2.3.2.
If the UE is in CM-IDLE state in 3GPP access and is using the Multi-USIM Paging Rejection feature (see clause 5.38 of TS 23.501 [2]), upon reception of paging request and if the UE determines not to accept the paging, the UE attempts to send a Reject Paging Indication via the UE Triggered Service Request procedure (clause 4.2.3.2) unless it is unable to do so e.g. due to UE implementation constraints.
If the UE is in CM-IDLE state in both non-3GPP and 3GPP accesses, upon reception of paging request for a PDU Session associated to non-3GPP access, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2) which shall contain the List Of Allowed PDU Sessions that, according to UE policies and whether the S-NSSAIs of these PDU Sessions are within the Allowed NSSAI or Partially Allowed NSSAI, if the serving cell is in a TA where the S-NSSAIs are supported or in a serving cell where the S-NSSAIs are available (according to clause 5.15.18 of TS 23.501 [2]) for 3GPP access, can be re-activated over the 3GPP access. If there is no PDU Session that can be re-activated over the 3GPP access, the UE includes an empty List Of Allowed PDU Sessions. If the AMF receives a Service Request message from the UE via non-3GPP access as described in clause 4.12.4.1 (e.g. because the UE successfully connects to a non-3GPP access), the AMF stops the paging procedure and processes the received Service Request procedure. If the AMF receives the Service Request message and the List Of Allowed PDU Sessions provided by the UE does not include the PDU Session for which the UE was paged, the AMF notifies the SMF that the UE was reachable but did not accept to re-activate the PDU Session by invoking Namf_EventExposure_Notify service as described in step 4 of clause 4.2.3.2.
If the UE is in CM-IDLE state in non-3GPP access and in CM-CONNECTED state in 3GPP access, upon reception of NAS Notification message over 3GPP access containing the non-3GPP Access Type, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2) with the List Of Allowed PDU Sessions that, according to UE policies and whether the S-NSSAIs of these PDU Sessions are within the Allowed NSSAI or Partially Allowed NSSAI, if the serving cell is in a TA where the S-NSSAIs are supported or in a serving cell where the S-NSSAIs are available (according to clause 5.15.18 of TS 23.501 [2]) for 3GPP access, can be re-activated over the 3GPP access. If there is no PDU Session that can be re-activated over the 3GPP access, the UE include an empty List Of Allowed PDU Sessions. When the AMF receives the Service Request message and the List of Allowed PDU Sessions provided by the UE does not include the PDU Session for which the UE was notified, the AMF notifies the SMF that the UE was reachable but did not accept to re-activate the PDU Session by invoking Namf_EventExposure_Notify service. If the AMF receives a Service Request message from the UE via non-3GPP access as described in clause 4.12.4.1 (e.g. because the UE successfully connects to a non-3GPP access), the AMF stops the Notification timer and processes the received Service Request procedure.
- Alternatively, if the UE is in CM-IDLE state in non-3GPP access with the Mobility Management back-off timer running, upon reception of Paging Message over 3GPP access containing the non-3GPP Access Type, the UE on stopping the back-off timer (for both accesses), shall initiate the UE Triggered Service Request procedure (clause 4.12.4.1) over non-3GPP access if non-3GPP access is available. When the AMF receives a Service Request message from the UE via non-3GPP access, the AMF stops the Paging timer and processes the received Service Request.
NOTE 7: A scenario where the UE is CM-IDLE over non-3GPP access and yet non-3GPP access is available, is when the UE over the non-3GPP access is running the Mobility Management back-off timer and network has released the NAS signalling connection upon service reject.
If the UE is in CM-IDLE state in 3GPP access and in CM-CONNECTED state in non-3GPP access, upon reception of NAS Notification message over non-3GPP access identifying the 3GPP access type, the UE shall initiate the UE triggered Service Request procedure (clause 4.2.3.2) over the 3GPP access when 3GPP access is available. The Multi-USIM UE may not be able to trigger Service Request procedure (clause 4.2.3.2) over the 3GPP access to response the NAS Notification, e.g. due to UE implementation constraints. If the AMF does not receive the Service Request message before Notification timer expires, the AMF may either page the UE through 3GPP access or notify the SMF that the UE was not able to re-activate the PDU Session.
The User Plane of all PDU Sessions for URLLC shall be activated during the Service Request procedure if the UE initiates the Service Request from 3GPP access in CM-IDLE state as described in clause 4.2.3.2.
6a. After receiving the Reject Paging Indication, the AMF notifies the SMF using the Namf_Communication_N1N2MessageTransfer Failure Notification that the UE rejected the page and no user plane connection will be established. The UE remains reachable for future paging attempts.
If the AMF detects the UE is in a Non-Allowed Area unless the request from the SMF is for regulatory prioritized service, the AMF rejects the request from the SMF and notifies the SMF that the UE is reachable only for regulatory prioritized service. The AMF stores an indication that the SMF has been informed that the UE is reachable only for regulatory prioritized service.
7. If the AMF has paged the UE to trigger the Service Request Procedure, the AMF shall initiate the UE configuration update procedure as defined in clause 4.2.4.2 to assign a new 5G-GUTI. If the UE response in the Service Request includes a Reject Paging Indication, the AMF triggers the release of the UE as specified in clause 4.2.3.2.
8. The UPF transmits the buffered downlink data toward UE via (R)AN node which performed the Service Request procedure. If data is buffered in the SMF, the SMF delivers buffered downlink data to the UPF.
The network also sends downlink signalling to the UE if the procedure is triggered due to request from other NFs, as described in step 3a. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4 UE Configuration Update | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4.1 General | UE configuration may be updated by the network at any time using UE Configuration Update procedure. UE configuration includes:
- Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI (including the S-NSSAI(s) which allows the MWAB-UE to establish BH PDU session(s) as described in clause 5.49.3 of TS 23.501 [2]) and its mapping to Subscribed S-NSSAIs, the Partially Allowed NSSAI and its mapping to Subscribed S-NSSAIs, the list of S-NSSAI(s) rejected partially in the RA, the Service Gap time, the list of Rejected NSSAIs if the UE Configuration Update procedure is triggered by the AMF after Network Slice-Specific Authentication and Authorization of S-NSSAIs, the Truncated 5G-S-TMSI Configuration and a priority subscription indication (e.g. MPS). If the UE and the AMF support RACS, this may also include a PLMN-assigned UE Radio Capability ID or alternatively a PLMN-assigned UE Radio Capability ID deletion indication. If the UE and AMF supports Disaster Roaming service, this may also include the "list of PLMN(s) to be used in Disaster Condition", Disaster Roaming wait range information, Disaster Return wait range information and notifying UE that the disaster condition is no longer applicable, as specified in TS 23.501 [2]. The AMF may also update MBSR (IAB-UE) with MBSR authorization information as specified in clause 5.35A.4 of TS 23.501 [2], S-NSSAI location availability information. The AMF may determine a Maximum Time Offset controlling when UEs are allowed to initiate NAS signalling with the network as specified in clause 5.4.13.5 of TS 23.501 [2]. The AMF may update the AMF PEIPS Assistance Information as specified in clause 5.4.12 of TS 23.501 [2] or AMF LP-WUSPS Assistance Information as specified in clause 5.4.12a of TS 23.501 [2].
- UE Policy provided by the PCF.
When AMF wants to change the UE configuration for access and mobility management related parameters the AMF initiates the procedure defined in clause 4.2.4.2. When the PCF wants to change or provide new UE Policies in the UE, the PCF initiates the procedure defined in clause 4.2.4.3.
If the UE Configuration Update procedure requires the UE to initiate a Registration procedure, the AMF indicates this to the UE explicitly.
The procedure in clause 4.2.4.2 may be triggered also when the AAA Server that performed Network Slice-Specific Authentication and Authorization for an S-NSSAI revokes the authorization. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4.2 UE Configuration Update procedure for access and mobility management related parameters | This procedure is initiated by the AMF when the AMF wants to update access and mobility management related parameters in the UE configuration.
This procedure is also used to trigger UE to perform, based on network indication, either Mobility Registration Update procedure while the UE is in CM-CONNECTED state to modify NAS parameters that require negotiation (e.g. MICO mode) or to steer the UE towards EPC as specified in clause 5.31.3 of TS 23.501 [2], or Mobility Registration Update procedure after the UE enters CM-IDLE state (e.g. for changes to Allowed NSSAI that require re-registration) or to update the UE with the Alternative S-NSSAI. If a Registration procedure is needed, the AMF provides an indication to the UE to initiate a Registration procedure.
UE Configuration Update shall be sent over the Access Type (i.e. 3GPP access or non-3GPP access) the UE Configuration Update is applied to, when applicable. If the AMF wants to update NAS parameters in the UE which require UE acknowledgement, then the AMF provides an indication to the UE of whether the UE shall acknowledge the command or not. The AMF should not request acknowledgement of the NITZ command. The AMF shall request acknowledgement for NSSAI information (e.g. Allowed NSSAI, Partially Allowed NSSAI, S-NSSAI rejected partially in the RA), 5G-GUTI, TAI List, [TAI List for S-NSSAIs in Partially Allowed NSSAI], [TAI List for S-NSSAI(s) rejected partially in RA] and Mobility Restrictions, LADN Information, MICO, Operator-defined access category definitions, PLMN-assigned UE Radio Capability ID, S-NSSAI location availability information and SMS subscription.
Figure 4.2.4.2-1: UE Configuration Update procedure for access and mobility management related parameters
0. AMF determines the necessity of UE configuration change due to various reasons (e.g. UE mobility change, NW policy, reception of Subscriber Data Update Notification from UDM, change of Network Slice configuration (including due to change of the NSSRG information in subscription information as specified in clause 5.15.12 of TS 23.501 [2], or due to change of NSAG Information as specified in clause 5.15.14 of TS 23.501 [2]), or to remove S-NSSAI from the Allowed NSSAI due to expiry of slice deregistration inactivity timer or to provide the UE with updated Slice Usage Policy as specified in clause 5.15.15 of TS 23.501 [2], need to assign PLMN-assigned UE Radio Capability ID, change of Enhanced Coverage Restriction information in the UE context, informing MBSR (IAB-UE) authorization state changes as specified in clause 5.35A.4 of TS 23.501 [2] based on operator configuration, a change related to discontinuous coverage (e.g. out-of-coverage period change), need to notify the UE to reconnect to the network due to NG-RAN timing synchronization status change as specified in clause 4.15.9.4) or that the UE needs to perform a Registration Procedure. If a UE is in CM-IDLE, the AMF can wait until the UE is in CM-CONNECTED state or triggers Network Triggered Service Request (in clause 4.2.3.3).
NOTE 1: It is up to the network implementation whether the AMF can wait until the UE is in CM-CONNECTED state or trigger the Network Triggered Service Request.
NOTE 2: The AMF can check whether Network Slice configuration needs to be updated by using the Nnssf_NSSelection_Get service operation and in such case the AMF compares the stored information with the output from the NSSF to decide whether an update of the UE is required.
The AMF may include Mobility Restriction List in N2 message that delivers UE Configuration Update Command to the UE if the service area restriction for the UE is updated.
1. The AMF sends UE Configuration Update Command containing one or more UE parameters (Configuration Update Indication, 5G-GUTI, TAI List, 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], rejected S-NSSAIs, [TAI List for S-NSSAI(s) rejected partially in RA], NITZ, Mobility Restrictions, LADN Information, MICO, Operator-defined access category definitions, SMS Subscribed Indication, [PLMN-assigned UE Radio Capability ID], [PLMN-assigned UE Radio Capability ID deletion indication], ["List of PLMN(s) to be used in Disaster Condition"], [Disaster Roaming wait range information], [Disaster Return wait range information], [MPS priority], [MCX priority], [UAS services Indication], MBSR authorization information, [S-NSSAI location availability information], [Mapping Of Alternative NSSAI], UE reconnection indication, [Slice Usage Policy], [Maximum Time Offset]) to the UE. Optionally, the AMF may update the rejected S-NSSAIs in the UE Configuration Update command.
The AMF includes one or more of 5G-GUTI, TAI List, 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, rejected S-NSSAIs, [TAI List for S-NSSAI(s) rejected partially in RA], NITZ (Network Identity and Time Zone), Mobility Restrictions parameters, LADN Information, Operator-defined access category definitions, PLMN-assigned UE Radio Capability ID, or SMS Subscribed Indication if the AMF wants to update these NAS parameters without triggering a UE Registration procedure.
The AMF may include in the UE Configuration Update Command also Configuration Update Indication parameters indicating whether:
- Network Slicing Subscription Change has occurred;
- the UE shall acknowledge the command; and
- whether a Registration procedure is requested.
If the AMF indicates Network Slicing Subscription Change, 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. If the AMF indicates Network Slicing Subscription Change, the UE shall also be requested to acknowledge in step 2.
If the AMF also includes in the UE Configuration Update Command message a new Configured NSSAI for the Serving PLMN, then the AMF should also include a new Allowed NSSAI and any new Partially Allowed NSSAI with, if available, the associated Mapping Of Allowed NSSAI and any Mapping Of Partially Allowed NSSAI, unless the AMF cannot determine the new Allowed NSSAI after the Subscribed S-NSSAI(s) are updated, in which case the AMF does not include in the UE Configuration Update Command message any Allowed NSSAI/Partially allowed NSSAI. 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 [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 [2]. For a non-roaming UE, if the UE has indicated its support of Slice Usage Policy in the UE 5GMM Core Network Capability, the AMF may include Slice Usage Policies for slices in the Configured NSSAI as described in clause 5.15.15 of TS 23.501 [2]. In the Slice Usage Policy, the AMF indicates 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 [2].
If the UE has indicated its support of NSAG feature in 5GMM Core Network Capability, the AMF includes, if available, the NSAG Information, defined in clause 5.15.14 of TS 23.501 [2] when providing a new Configured NSSAI which includes S-NSSAIs with associated NSAG Value(s) or when the NSAG Information changes for some S-NSSAI in the Configured NSSAI. When NSAG Information is provided to the UE, the AMF requests the UE to acknowledge the UE Configuration Command message.
When the UE and the AMF supports RACS as defined in clause 5.4.4.1a of TS 23.501 [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 and 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.
If the UE is needed to be redirected to the dedicated frequency band(s) for S-NSSAI(s), the AMF may determine a Target NSSAI, as described in clause 5.3.4.3.3 of TS 23.501 [2], itself or by interacting with the NSSF using Nnssf_NSSelection_Get which includes e.g. the Rejected S-NSSAI(s) for RA and Allowed NSSAI. The AMF may determine RFSP index associated to the Target NSSAI by interacting with the PCF using Npcf_AMPolicyControl_Update which includes the Target NSSAI to retrieve a corresponding RFSP index or based on local configuration in case PCF is not deployed. The Target NSSAI and the RFSP index associated with the Target NSSAI are provided to the NG-RAN within the N2 message carrying the UE Configuration Update Command message.
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 [2]. When the disaster condition is no longer applicable, the serving AMF that provides Disaster Roaming service may notify the UE as specified in clause 5.40.5 of TS 23.501 [2].
If the AMF receives a Subscriber Data Update Notification from the UDM that includes MPS priority or MCX priority, the AMF includes MPS priority or MCX priority in the UE Configuration Update Command, respectively, as specified in clause 5.22.2 of TS 23.501 [2].
If UAS service becomes enabled or disabled (e.g. because the aerial subscription is part of the UE subscription data retrieved from UDM changes), the AMF may include an Indication of UAS services being enabled or disabled in the UE Configuration Update Command.
If the UE indicates its support of LADN per DNN and S-NSSAI in the UE MM Core Network Capability during the Registration procedure as specified in clause 4.2.2.2.2, the AMF may include LADN Information per DNN and S-NSSAI.
For MBSR (IAB-UE) registered in AMF, the AMF may update the MBSR authorization information as specified in clause 5.35A.4 of TS 23.501 [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 [2]), the AMF includes the Mapping Of Alternative NSSAI within the UE Configuration Update Command to the UE and also adds the Alternative S-NSSAI to the Allowed NSSAI and/or Configured NSSAI, if not already included.
If both the UE and the network support unavailability due to discontinuous coverage, the AMF determines this Maximum Time Offset as described in clause 5.4.13.5 of TS 23.501 [2]. The AMF includes the Maximum Time Offset within the UE Configuration Update Command to the UE.
2a. If the UE Configuration Update Indication requires acknowledgement of the UE Configuration Update Command, then the UE shall send a UE Configuration Update complete message to the AMF. The AMF should request acknowledgement for all UE Configuration Updates, except when only NITZ is provided. If Registration procedure is not required, steps 3a, 3b, 3c and step 4 are skipped. If the Configuration Update Indication is included in the UE Configuration Update Command message and it requires a Registration procedure, depending on the other NAS parameters included in the UE Configuration Update command, the UE shall execute steps 3a or 3b or 3c+4 as applicable.
If the PLMN-assigned UE Radio Capability ID is included in step1, the AMF stores the UE Radio Capability ID in UE context if receiving UE Configuration Update complete message.
If the UE receives PLMN-assigned UE Radio Capability ID deletion indication in step 1, the UE shall delete the PLMN-assigned UE Radio Capability ID(s) for this PLMN. If UE Configuration Update is only for this purpose, the following steps are skipped.
2b. [Conditional] The AMF also uses the Nudm_SDM_Info service operation to provide an acknowledgment to UDM that the UE received CAG information as part of the Mobility Restrictions (if the CAG information was updated), or the Network Slicing Subscription Change Indication (if this was indicated in step 1) and acted upon it.
2c. [Conditional] If the AMF has reconfigured the 5G-GUTI over 3GPP access, the AMF informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI) when the AMF receives the acknowledgement from the UE in step 2a.
[Conditional] If the UE is registered to the same PLMN via both 3GPP and non-3GPP access and if the AMF has reconfigured the 5G-GUTI over non-3GPP access and the UE is in CM-CONNECTED state over 3GPP access, then the AMF informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI) when the AMF receives the acknowledgement from the UE in step 2a.
[Conditional] If the AMF has configured the UE with a PLMN-assigned UE Radio Capability ID, the AMF informs NG-RAN of the UE Radio Capability ID, when it receives the acknowledgement from the UE in step 2a.
[Conditional] If the Mobility Restrictions for the UE were updated and the Mobility Restrictions were not provided in the N2 message that delivers the UE Configuration Update Command, the AMF provides the NG-RAN with updated Mobility Restrictions unless the AMF releases the UE in this step (see below).
[Conditional] If the AMF provides an Allowed NSSAI/Partially Allowed NSSAI to the UE, the Allowed NSSAI/Partially Allowed NSSAI is provided to the NG-RAN within the N2 message carrying the UE Configuration Update Command message for UEs.
If the AMF initiated the UE Configuration Update procedure due to receiving Nudm_SDM_Notification and the CAG information has changed such that a CAG Identifier has been removed from the Allowed CAG list or the UE is only allowed to access CAG cells, the AMF shall release the NAS signalling connection by triggering the AN Release procedure for UEs that are not receiving Emergency Services as defined in TS 23.501 [2].
If the AMF need to update Allowed CAG list to the NG-RAN due to change of validity condition as described in TS 23.501 [2], the AMF may either update NG-RAN and keep the NAS signalling connection or release the NAS signalling connection by triggering the AN Release procedure, without updating Allowed CAG list to the NG-RAN, for the UEs that are not receiving Emergency Services as defined in TS 23.501 [2].
NOTE 3: If validity condition needs to be applied immediately before the NG-RAN enforces Allowed CAG list, the AMF can trigger AN Release without sending updated Allowed CAG list to the NG-RAN.
NOTE 4: When the UE is accessing the network for emergency service the conditions in clause 5.16.4.3 of TS 23.501 [2] apply.
2d [Conditional] If the UE is configured with a new 5G-GUTI in step 2a via non-3GPP access and the UE is registered to the same PLMN via both 3GPP and non-3GPP access, then the UE passes the new 5G-GUTI to its 3GPP access' lower layers.
If the UE is configured with a new 5G-GUTI in step 2a over the 3GPP access, the UE passes the new 5G-GUTI to its 3GPP access' lower layers.
NOTE 5: Steps 2c and 2d are 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 [44] and TS 36.304 [43]). It is assumed that the UE Configuration Update Complete is reliably delivered to the AMF after the 5G-AN has acknowledged its receipt to the UE.
3a. [Conditional] If only NAS parameters that can be updated without transition from CM-IDLE are included (e.g. MICO mode, Enhanced Coverage Restricted information) the UE shall initiate a Registration procedure immediately after the acknowledgement to re-negotiate the updated NAS parameter(s) with the network. Steps 3b, 3c and step 4 are skipped.
3b. [Conditional] If a new Allowed NSSAI and/or a new Mapping Of Allowed NSSAI and/or Partially Allowed NSSAI and/or Mapping Of Partially Allowed NSSAI and/or a new Configured NSSAI provided by the AMF to the UE in step 1 does not affect the existing connectivity to AMF, the AMF needs not release the NAS signalling connection for the UE after receiving the acknowledgement in step 2 and immediate registration is not required. The UE can start immediately using the new Allowed NSSAI and/or the new Mapping Of Allowed NSSAI and/or Partially Allowed NSSAI and/or Mapping Of Partially Allowed NSSAI. If one or more PDU Sessions use a S-NSSAI that is not part of the new Allowed NSSAI or Partially Allowed NSSAI, the AMF indicates to the SMF(s) the corresponding PDU Session ID(s) and each SMF releases the PDU Session(s) according to clause 4.3.4.2. The UE cannot connect to an S-NSSAI included in the new Configured NSSAI for the Serving PLMN but not included in the new Allowed NSSAI or Partially Allowed NSSAI until the UE performs a Registration procedure and includes a Requested NSSAI based on the new Configured NSSAI, following the requirements described in clause 5.15.5.2 of TS 23.501 [2]. Steps 3c and 4 are skipped.
The AMF may, based on its policy, provide anyway an indication that a Registration procedure is required even though the UE Configuration Update Command in step 1 does not affect the existing connectivity to Network Slices: in such a case only step 3c is skipped.
3c. [Conditional] If a new Allowed NSSAI and/or a new Mapping Of Allowed NSSAI and/or Partially Allowed NSSAI and/or Mapping Of Partially Allowed NSSAI and/or a new Configured NSSAI provided by the AMF to the UE in step 1 affects ongoing existing connectivity to AMF, then the AMF shall provide an indication that the UE shall initiate a Registration procedure.
4. [Conditional] After receiving the acknowledgement in step 2, the AMF shall release the NAS signalling connection for the UE by triggering the AN Release procedure, unless there is one established PDU Sessions associated with regulatory prioritized services. If there is one established PDU Session associated with regulatory prioritized services, the AMF informs SMFs to release the PDU Session(s) associated with non regulatory prioritized services for this UE (see clause 4.3.4).
The AMF shall reject any NAS Message from the UE carrying PDU Session Establishment Request for a non-emergency PDU Session before the required Registration procedure has been successfully completed by the UE.
The UE initiates a Registration procedure (see clauses 4.2.2.2.2 and 4.13.3.1) with registration type Mobility Registration Update after the UE enters CM-IDLE state and shall not include the 5G-S-TMSI or GUAMI in Access Stratum signalling and shall include, subject to the conditions set out in clause 5.15.9 of TS 23.501 [2], a Requested NSSAI in access stratum signalling. If there is an established PDU Session associated with emergency service and the UE has received an indication to perform the Registration procedure, the UE shall initiate the Registration procedure only after the PDU Session associated with emergency service is released.
NOTE 6: Receiving UE Configuration Update command without an indication requesting to perform re-registration, can still trigger Registration procedure by the UE for other reasons. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.4.3 UE Configuration Update procedure for transparent UE Policy delivery | This procedure is initiated when the PCF wants to update UE policy information (i.e. UE policy) in the UE configuration. 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 V-PCF interacts with the AMF and the H-PCF interacts with the V-PCF.
For the purpose of URSP delivery via EPS, the delivery procedure of UE Policy Containers from the SMF+PGW-C to the UE is specified in clause 4.11.0a.2a.10.
Figure 4.2.4.3-1: UE Configuration Update procedure for transparent UE Policy delivery
0. PCF decides to update UE policy based on triggering conditions such as an initial registration, registration with 5GS when the UE moves from EPS to 5GS, or need for updating UE policy as follows:
- For the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503 [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message; and
- For the network triggered UE policy update case (e.g. the change of UE location, the change of Subscribed S-NSSAIs as described in clause 6.1.2.2.2 of TS 23.503 [20]), the PCF checks the latest list of PSIs to decide which UE policies have to be sent to the UE.
The PCF checks if the size of the resulting UE policy information exceeds a predefined limit:
- If the size is under the limit, then UE policy information are included in a single Namf_Communication_N1N2MessageTransfer service operation as described below.
- If the size exceeds the predefined limit, the PCF splits the UE policy information in smaller, logically independent UE policy information ensuring the size of each is under the predefined limit. Each UE policy information will be then sent in separated Namf_Communication_N1N2MessageTransfer service operations as described below.
NOTE 1: NAS messages from AMF to UE do not exceed the maximum size limit allowed in NG-RAN (PDCP layer), so the predefined size limit in PCF is related to that limitation.
NOTE 2: The mechanism used to split the UE policy information is described in TS 29.507 [32].
0a. If the PCF has not subscribed to be notified by the AMF about the UE response to an update of UE policy information, the PCF subscribes to the AMF to be notified about the UE response to an update of UE policy information.
1. PCF invokes Namf_Communication_N1N2MessageTransfer service operation provided by the AMF. The message includes SUPI, UE Policy Container.
2. If the UE is registered and reachable by AMF in either 3GPP access or non-3GPP access, AMF shall transfers transparently the UE Policy container to the UE via the registered and reachable access.
If the UE is registered in both 3GPP and non-3GPP accesses and reachable on both access and served by the same AMF, the AMF transfers transparently the UE Policy container to the UE via one of the accesses based on the AMF local policy.
If the UE is not reachable by AMF over both 3GPP access and non-3GPP access, the AMF reports to the PCF that the UE Policy container could not be delivered to the UE using Namf_Communication_N1N2TransferFailureNotification as in the step 5 in clause 4.2.3.3.
If AMF decides to transfer transparently the UE Policy container to the UE via 3GPP access, e.g. the UE is registered and reachable by AMF in 3GPP access only, or if the UE is registered and reachable by AMF in both 3GPP and non-3GPP accesses served by the same AMF and the AMF decides to transfer transparently the UE Policy container to the UE via 3GPP access based on local policy and the UE is in CM-IDLE and reachable by AMF in 3GPP access, the AMF starts the paging procedure by sending a Paging message described in the step 4b of Network Triggered Service Request (in clause 4.2.3.3). Upon reception of paging request, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2).
3. If the UE is in CM-CONNECTED over 3GPP access or non-3GPP access, the AMF transfers transparently the UE Policy container (UE policy information) received from the PCF to the UE. The UE Policy container includes the list of Policy Sections as described in TS 23.503 [20].
4. The UE updates the UE policy provided by the PCF and sends the result to the AMF.
5. The AMF forwards the response of the UE to the PCF using Namf_Communication_N1MessageNotify.
The PCF maintains the latest list of PSIs delivered to the UE and updates the latest list of PSIs in the UDR by invoking Nudr_DM_Update (SUPI, Policy Data, Policy Set Entry, updated PSI data) service operation.
If the PCF is notified about UE Policy delivery failure from the AMF, the PCF may initiate UE Policy Association Modification procedure to provide a new trigger "Connectivity state changes" in Policy Control Request Trigger of UE Policy Association to AMF as defined in clause 4.16.12.2. The PCF may re-initiate the UE Configuration Update procedure for transparent UE Policy delivery as in step 1 when the PCF is notified of the UE connectivity state changed to CONNECTED.
NOTE 3: For backward compatibility the PCF may subscribe the "Connectivity state changes (IDLE or CONNECTED)" event in Rel-15 AMF as defined in clause 5.2.2.3. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5 Reachability procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5.1 General | Elements of this procedure are used for UDM/NF initiated UE Reachability Notification requests, e.g. for "SMS over NAS".
The procedure applies to UEs that are in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED states.
There are two procedures necessary for any service related entity that would need to be notified by the reachability of the UE:
- UE Reachability Notification Request procedure; and
- UE Activity Notification procedure. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5.2 UE Reachability Notification Request procedure | The UE Reachability Notification Request procedure is illustrated in figure 4.2.5.2-1.
Figure 4.2.5.2-1: UE Reachability Notification Request Procedure
1a. [Conditional] When a service-related entity requests the UDM to provide an indication regarding UE reachability, the UDM checks whether that service-related entity is authorized to perform this request on this subscriber. The service-related entity may subscribe in UDM to receive notifications about UE Reachability or UE Reachability for SMS delivery events as defined in clause 4.15.3.
NOTE 1: This request for UE Reachability Notification is received in UDM using different interfaces/services depending on the service-related entity. For example, an SBI capable service-related entity can use the Nudm_EventExposure_Subscribe service while an SMS-GMSC using non-SBI interfaces triggers this procedure as described in TS 23.040 [7].
The UDM may retrieve from the UDR the list of NF IDs for Network Functions authorized by the HPLMN to request notifications on this UE's reachability.
If the entity is not authorized, the UDM may reject the request (e.g. if the requesting entity is recognized as being a valid entity, but not authorized for that subscriber) or discard it silently (e.g. if the requesting entity is not recognized). Appropriate O&M reports are generated.
1b. [Conditional] The UDM stores the identity of the service-related entity.
In the case that the service-related entity is an SMS-GMSC using non-SBI interfaces, the UDM stores the SC address within the MWD list. Otherwise, if the service-related entity is an SBI capable service-related entity, the UDM stores the address of the SBI capable service-related entity in the form of a subscription to the Nudm_EventExposure service.
If the UE Reachability Notification Request is for SMS over NAS and no SMSF is registered for the target UE, steps 2 to 4 are skipped.
Otherwise the UDM sets the URRP-AMF flag parameter and continues with step 2.
1c. [Conditional] An NF (e.g. SMF) may subscribe event of UE reachability status change by using the Namf_EventExposure_Subscribe service operation. Steps 2 to 4 are skipped.
The AMF invokes the Namf_EventExposure_Notify service operation to report the current reachability state of a UE to the NF if requested by the consumer NF.
2. [Conditional] If the value of URRP-AMF flag parameter changes from "not set" to "set" and an AMF is registered in the UDM for the target UE, the UDM initiates Namf_EventExposure_Subscribe service operation for UE reachability for UE reachable for DL traffic (SUPI, UE Reachability) towards the AMF. The UDM may indicate if direct notification to NF shall be used by the AMF. When direct notification to NF is indicated to the AMF, the URRP-AMF is not set in the UDM in step 1a for NF initiated requests. If the service-related entity requested UDM to receive notifications about UE Reachability for SMS delivery, the UDM shall not indicate direct notification to NF.
NOTE 2: The UDM can trigger UE Reachability Notification Request procedure with two different AMFs for a UE which is connected to 5G Core Network over 3GPP access and non-3GPP access simultaneously. Also, for interworking with EPC, the UDM/HSS can trigger UE Reachability Notification Request procedure with MME as described in TS 23.401 [13].
3. The AMF checks that the requesting entity is authorized to perform this request on this subscriber.
If the AMF has an MM Context for that user, the AMF stores the NF ID in the URRP-AMF information, associated with URRP-AMF information flag to indicate the need to report to the UDM or directly to the NF with a UE Activity Notification (see clause 4.2.5.3).
4. [Conditional] For UE reachability for UE reachable for DL traffic, if the UE state in AMF is in CM-CONNECTED state and the Access Type is 3GPP access, the AMF initiates N2 Notification procedure (see clause 4.8.3) with reporting type set to Single RRC_CONNECTED state notification. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.5.3 UE Activity Notification procedure | The UE Activity Notification procedure is illustrated in figure 4.2.5.3-1.
Figure 4.2.5.3-1: UE Activity Procedure
0. Event has been subscribed in the AMF for UE reachability for DL traffic or for UE reachability status change.
1a. For a UE in CM-IDLE, the AMF receives (N1) NAS signalling implying UE is reachable for DL traffic, e.g. a Registration Request or Service Request message from the UE, the AMF performs step 2;
1b. For a UE in CM-CONNECTED, if the AMF has initiated the N2 Notification procedure in Step 4 of clause 4.2.5.2 and when the AMF receives a (N2) UE Notification (see clause 4.8.3) or a (N2) Path Switch Request (see clause 4.9.1.2) implying UE is reachable for DL traffic from the NG-RAN, the AMF performs step 2. Otherwise, i.e. UE is in CM-CONNECTED and AMF has not initiated N2 Notification procedure, the AMF performs step 2; or
1c. The UE's reachability state changes from reachable to unreachable, then AMF performs step 2.
2a. For event subscription of "UE reachable for DL traffic", if the AMF has an MM context for the UE and the URRP-AMF information flag associated with the subscribing NF is set to report once that the UE is reachable for DL traffic, the AMF initiates the Namf_EventExposure_Notify service operation (SUPI, UE Reachable) message (or Nudm_UECM_Registration service operation when applicable) to the UDM following step 1a or step 1b. The AMF clears the corresponding URRP-AMF information if applicable for the UE.
2a1. When the UDM receives the Namf_EventExposure_Notify service operation (SUPI, UE-Reachable) message or Nudm_UECM_Registration service from AMF for a UE that has URRP-AMF information flag set in the UDM, it triggers appropriate notifications to the service-related entities associated with the URRP-AMF information flag that have subscribed to the UDM for UE Reachability notifications.
If SMSF is registered, it also triggers appropriate notifications to the service-related entities associated with the URRP-AMF information flag that have subscribed to the UDM for UE reachability for SMS delivery notification (e.g. SMS-GMSC, HSS). UDM clears the URRP-AMF information for the UE.
If no SMSF is registered and there are service-related entities subscribed to the UDM for the UE reachability for SMS delivery notification, the UDM clears the URRP-AMF information for the UE but does not notify any service-related entity.
When the UDM receives the Nudm_UECM_Registration service from SMSF for a UE that has service-related entities subscribed to the UDM for the UE reachability for SMS delivery notification and no URRP-AMF flag set in the UDM, the UDM triggers appropriate notifications to the service-related entities that have subscribed to the UDM for UE reachability for SMS delivery notification).
NOTE: The UE Reachability Notification is sent by the UDM using different interfaces/services depending on the service-related entity. For example, an SBI capable service-related entity can receive the notification using the Nudm_EventExposure_Notify service operation (if previously subscribed) while an SMS-SC can get the notification as described in TS 23.040 [7] based on the SC address stored in the MWD list.
2b. If in step 0 the AMF received Namf_EventExposure_Subscribe_service operation directly from an NF authorised to receive direct notifications in the case of UE reachability status change, or the UDM indicated that the notification needs to be sent directly to the NF in the case of UE reachability for DL traffic, the AMF initiates the Namf_EventExposure_Notify service operation (SUPI, UE reachability state) message directly to the NF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.6 AN Release | This procedure is used to release the logical NG-AP signalling connection for the UE between the (R)AN and the AMF and the associated N3 User Plane connections and (R)AN signalling connection between the UE and the (R)AN and the associated (R)AN resources.
When the NG-AP signalling connection is lost due to (R)AN or AMF failure, the AN release is performed locally by the AMF or the (R)AN as described in the procedure flow below without using or relying on any of the signalling shown between (R)AN and AMF. The AN release causes all UP connections of the UE to be deactivated.
The initiation of AN release may be due to:
- (R)AN-initiated with cause e.g. O&M Intervention, Unspecified Failure, (R)AN (e.g. Radio) Link Failure, User Inactivity, Inter-System Redirection, request for establishment of QoS Flow for IMS voice, Release due to UE generated signalling connection release, mobility restriction, Release Assistance Information (RAI) from the UE, UE using satellite access moved out of PLMN serving area, etc.; or
- AMF-initiated with cause e.g. Unspecified Failure, etc.
Both (R)AN-initiated and AMF-initiated AN Release procedures are shown in Figure 4.2.6-1.
If Service Gap Control shall be applied for the UE (see clause 5.31.16 of TS 23.501 [2]) and the Service Gap timer is not already running, the Service Gap timer shall be started in AMF and UE when entering CM-IDLE, unless the connection was initiated after a paging of an MT event, or after a Registration procedure without Uplink data status or after a Registration procedure for regulatory prioritized services like Emergency services or exception reporting.
For this procedure, the impacted SMF and UPF are all under control of the PLMN serving the UE, e.g. in Home Routed roaming case the SMF and UPF in HPLMN are not involved.
Figure 4.2.6-1: AN Release procedure
1. If there is some confirmed (R)AN conditions (e.g. Radio Link Failure) or for other (R)AN internal reason, the (R)AN may decide to initiate the UE context release in the (R)AN. In this case, the (R)AN sends an N2 UE Context Release Request (Cause, List of PDU Session ID(s) with active N3 user plane) message to the AMF. Cause indicates the reason for the release (e.g. AN Link Failure, O&M intervention, unspecified failure, etc.). The List of PDU Session ID(s) indicates the PDU Sessions served by (R)AN of the UE. If the (R)AN is NG-RAN, this step is described in clause 8.3.2 of TS 38.413 [10]. If the (R)AN is an N3IWF this step is described in clause 4.12.4.2.
If the reason for the release is the NG-RAN received an AS Release Assistance Indicator as defined in TS 36.331 [16], NG-RAN should not immediately release the RRC connection but instead send an N2 UE Context Release Request message to the AMF. If the AS RAI indicates only a single downlink transmission is expected then NG-RAN should only send the N2 UE Context Release Request after a single downlink NAS PDU or N3 data PDU has been transferred.
If N2 Context Release Request cause indicates the release is requested due to user inactivity or AS RAI then the AMF continues with the AN Release procedure unless the AMF is aware of pending MT traffic or signalling.
If N2 Context Release Request cause indicates the release is requested due to a UE using satellite access moved out of PLMN serving area, the AMF may deregister the UE as described in clause 4.2.2.3.3 before continuing with the AN Release procedure.
If N2 Context Release Request cause indicates the release is requested due to MBSR not authorized as described in clause 5.35A.4 of TS 23.501 [2], the AMF may deregister the MBSR as described in clause 4.2.2.3.3 before continuing with the AN Release procedure.
2. AMF to (R)AN: If the AMF receives the N2 UE Context Release Request message or due to an internal AMF event, including the reception of Service Request or Registration Request to establish another NAS signalling connection still via (R)AN, the AMF sends an N2 UE Context Release Command (Cause) to the (R)AN. The Cause indicates either the Cause from (R)AN in step 1 or the Cause due to an AMF event. If the (R)AN is a NG-RAN this step is described in detail in clause 8.3.3 of TS 38.413 [10]. If the (R)AN is an N3IWF/TNGF/W-AGF this step is described in clauses 4.12.4.2 / 4.12a and in clause 7.2.5 of TS 23.316 [53] for W-5GAN access.
If the AMF receives Service Request or Registration Request to establish another NAS signalling connection still via (R)AN, after successfully authenticating the UE, the AMF releases the old NAS signalling connection and then continues the Service Request or Registration Request procedure.
3. [Conditional] If the (R)AN connection (e.g. RRC connection or NWu connection) with the UE is not already released (step 1), either:
a) the (R)AN requests the UE to release the (R)AN connection. Upon receiving (R)AN connection release confirmation from the UE, the (R)AN deletes the UE's context, or
b) if the Cause in the N2 UE Context Release Command indicates that the UE has already locally released the RRC connection, the (R)AN locally releases the RRC connection.
4. The (R)AN confirms the N2 Release by returning an N2 UE Context Release Complete (List of PDU Session ID(s) with active N3 user plane, User Location Information, Age of Location Information) message to the AMF. The List of PDU Session ID(s) indicates the PDU Sessions served by (R)AN of the UE. The AMF stores always the latest UE Radio Capability information or NB-IoT specific UE Radio Access Capability Information received from the NG-RAN node received as described in TS 38.413 [10]. The N2 signalling connection between the AMF and the (R)AN for that UE is released. If the UE is served by an NG-eNB that supports WUS, then the NG-eNB should include the Information On Recommended Cells And RAN nodes For Paging; otherwise the (R)AN may provide the list of recommended cells / TAs / NG-RAN node identifiers for paging to the AMF.
If the PLMN has configured secondary RAT usage reporting, the NG-RAN node may provide RAN usage data Report.
This step shall be performed promptly after step 2, i.e. it shall not be delayed, for example, in situations where the UE does not acknowledge the RRC Connection Release.
The NG-RAN includes Paging Assistance Data for CE capable UE, if available, in the N2 UE Context Release Complete message. The AMF stores the received Paging Assistance Data for CE capable UE in the UE context for subsequent Paging procedure.
5. [Conditional] AMF to SMF: For each of the PDU Sessions in the N2 UE Context Release Complete, the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, PDU Session Deactivation, Cause, Operation Type, User Location Information, Age of Location Information, N2 SM Information (Secondary RAT usage data)). The Cause in step 5 is the same Cause in step 2. If List of PDU Session ID(s) with active N3 user plane is included in step 1b, the step 5 to 7 are performed before step 2. The Operation Type is set to "UP deactivate" to indicate deactivation of user plane resources for the PDU Session.
For PDU Sessions using Control Plane CIoT 5GS Optimisation and if the UE has negotiated the use of extended Idle mode DRX, the AMF informs the SMF immediately that the UE is not reachable for downlink data. For PDU Sessions using Control Plane CIoT 5GS Optimisation and if the UE has negotiated the use of MICO mode with Active Time, the AMF informs the SMF that the UE is not reachable for downlink data once the Active Time has expired.
6a [Conditional] SMF to UPF: N4 Session Modification Request (AN or N3 UPF Tunnel Info to be removed, Buffering on/off).
For PDU Sessions not using Control Plane CIoT 5GS Optimisation, the SMF initiates an N4 Session Modification procedure indicating the need to remove Tunnel Info of AN or UPF terminating N3. Buffering on/off indicates whether the UPF shall buffer incoming DL PDU or not.
If the SMF has received an indication from the AMF that the UE is not reachable for downlink data for PDU Sessions using Control Plane CIoT 5GS Optimisation, the SMF may initiate an N4 Session Modification procedure to activate buffering in the UPF.
If multiple UPFs are used in the PDU Session and the SMF determines to release the UPF terminating N3, step 6a is performed towards the UPF (e.g. PSA) terminating N9 towards the current N3 UPF. The SMF then releases the N4 session towards the N3 UPF (the N4 release is not shown on the call flow).
See clause 4.4 for more details.
If the cause of AN Release is because of User Inactivity, or UE Redirection, the SMF shall preserve the GBR QoS Flows. If the AN Release is due to the reception of Service Request or Registration Request to establish another NAS signalling connection via (R)AN as described in step 2, the SMF also preserves the GBR QoS Flows. In any other case, the SMF shall trigger the PDU Session Modification procedure (see clause 4.3.3) for the GBR QoS Flows of the UE after the AN Release procedure is completed.
If the redundant I-UPFs are used for URLLC, the N4 Session Modification Request procedure is done for each I-UPF. In this case, SMF selects both the redundant I-UPFs to buffer the DL packets for this PDU Session or drop the DL packets for this PDU session or forward the DL packets for this PDU session to the SMF, based on buffering instruction provided by the SMF as described in clause 5.8.3.2 or 5.8.3.3 of TS 23.501 [2].
If the redundant N3 tunnels are used for URLLC, the N4 Session Modification Request procedure to the UPF of N3 terminating point is to remove the dual AN Tunnel Info for N3 tunnel of the corresponding PDU Session.
6b. [Conditional] UPF to SMF: N4 Session Modification Response acknowledging the SMF request.
See clause 4.4 for more details.
7. [Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response for step 5.
Upon completion of the procedure, the AMF considers the N2 and N3 as released and enters CM-IDLE state.
After completion of the procedure, the AMF reports towards the NF consumers are triggered for cases in clause 4.15.4.
After completion of the procedure, if steps 5 to 7 were performed before step 2 and the AMF received N2 SM information from NG-RAN in step 4 (e.g. Secondary RAT usage data report), the AMF initiates a Nsmf_PDUSession_UpdateSMContext towards SMF to deliver the N2 SM information. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7 N2 procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.1 N2 Configuration | At power up, restart and when modifications are applied, the 5G-AN node and AMF use non-UE related N2 signalling to exchange configuration data. Full details of this configuration data are specified in TS 38.413 [10], but the following highlights some aspects.
The AMF supplies the 5G-AN node with information about:
a) the AMF Name and the GUAMI(s) configured on that AMF Name;
b) the set of TNL associations to be established between the NG-RAN node and the AMF;
c) weight factor associated with each of the TNL association within the AMF; and
d) weight factor for each AMF Name within the AMF Set; and
e) (optional) for each GUAMI(s) configured on that AMF the corresponding backup AMF Name.
The weight factors are used for load distribution of the initial N2 messages. The AMF chooses whether or not to use the same TNL association for the initial N2 message and subsequent messages for that UE. TNL associations configured with a weight factor set to zero are not permitted for the initial N2 message, but can be used for subsequent N2 messages.
Deployments that rely solely on 5GC-based load balancing can set the weight factors associated with TNL associations that are permitted for the initial N2 message to the same value.
The 5G-AN supplies over N2 the AMF with information about the Tracking Area(s) it serves and the S-NSSAI(s) it supports in each of these Tracking Areas. See clause 5.3.2.3 of TS 23.501 [2]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2 NGAP UE-TNLA-binding related procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.1 Creating NGAP UE-TNLA-bindings during Registration and Service Request | When a UE connects to the 5GC via a 5G-AN node without providing any UE identities (i.e. a GUAMI or a 5G-S-TMSI), or the UE provides a GUAMI or a 5G-S-TMSI but the 5G-AN node cannot associate to any of its connected AMFs, the following steps are performed:
1. The 5G-AN node selects an AMF as defined in clause 6.3.5 of TS 23.501 [2].
2. The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial message e.g. N2 INITIAL UE MESSAGE for the selected AMF, as defined in clause 5.21.1.3 of TS 23.501 [2] and forwards the UE message to the AMF via the selected TNL association.
3. The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.
NOTE 1: This process could take place during the Registration procedure (for Initial Registration, Mobility Registration Update).
4. The AMF may decide to modify the NGAP UE-TNLA-binding toward other 5G-AN nodes such as N3IWF. This is done if the AMF is changed and old AMF have existing NGAP UE-TNLA-bindings toward other 5G-AN nodes.
When a UE connects to the 5GC via a 5G-AN node with a 5G-S-TMSI or GUAMI associated with the AMF usable by the 5G-AN node, the following steps are performed:
1. The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message for the AMF identified by the UE's 5G-S-TMSI or GUAMI.
2. The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.
NOTE 2: This process could take place during the Registration procedure or Service Request procedure. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.2 Creating NGAP UE-TNLA-bindings during handovers | During an Xn-based inter NG-RAN node handover, the following applies
- If an NGAP UE-TNLA-binding exists for a UE, the source 5G-AN node supplies the target 5G-AN node with the corresponding TNL address of the AMF for the currently used TNL association.
- If the target 5G-AN does not have a TNL association towards the TNL address of the AMF received from the source 5G-AN node, the target 5G-AN node establishes a TNL association towards the TNL address received from the source 5G-AN node, creates an NGAP UE-TNLA-binding to this TNL association and sends the N2 Path Switch Request via this TNL association.
- Otherwise, the target 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations towards the TNL address, permitted for the initial N2 message for the AMF identified by the UE's GUAMI.
- The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.
During an inter NG-RAN node handover without Xn interface (i.e. during an N2 handover) the following applies:
- If an NGAP UE-TNLA-binding exists for a UE, the source 5G-AN node sends the N2 Handover Required message using the corresponding TNL address of the AMF.
- Otherwise the 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message for the AMF identified by the UE's GUAMI.
- The target AMF selects a TNL association from the available TNL associations for the target 5G-AN node and sends the N2 Handover Request message via this TNL association. The target 5G-AN node creates an NGAP UE-TNLA-binding for the UE based on the TNL association selected by the target AMF. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.3 Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release | If the AMF has released the NGAP UE-TNLA-binding in the 5G-AN node for a UE and the 5G-AN node needs to send an N2 message for this UE, the following applies:
- The 5G-AN node checks the GUAMI stored in the UE context and the associated AMF:
- If the GUAMI is available, 5G-AN selects the AMF which owns that GUAMI.
- If GUAMI has been marked as unavailable (i.e. based on AMF unavailable status indication received from AMF) but one corresponding target AMF has been indicated, 5G-AN selects that target AMF even if the GUAMI has not been updated as available by the target AMF.
- If GUAMI has been marked as unavailable (i.e. based on AMF unavailable status indication received from AMF) and no corresponding target AMF has been indicated, the 5G-AN selects an AMF from the AMF Set based on AMF Set ID of the GUAMI, as defined in clause 6.3.5 of TS 23.501 [2].
- The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message with the selected AMF, as defined in clause 5.21.1.3 of TS 23.501 [2],and sends the N2 message to the AMF via the selected TNL association.
- The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection.
If the NGAP UE-TNLA-binding has been released for a UE and the AMF needs to send an N2 message for this UE, the following applies:
- The AMF selects a TNL association from the available TNL associations for the target 5G-AN node and sends the N2 message via this TNL association. The target 5G-AN node creates an NGAP UE-TNLA-binding for the UE based on the TNL association selected by the AMF.
The TNL association chosen by the AMF always takes precedence.
NOTE: This addresses situations where 5G-AN node and AMF select a TNL association for a UE concurrently. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.4 NGAP UE-TNLA-binding update procedure | At any time the AMF may decide to re-bind the NGAP UE association to a new TNL association:
- by sending a UE-specific NGAP message on a new TNL association (triangular redirection), if:
- AMF responds to the 5G-AN node initiated NGAP message (i.e. triangular redirection) as described in clauses 4.2.7.2.1, 4.2.7.2.2 and 4.2.7.2.3; or
- AMF initiated UE-specific NGAP message needs to be sent to 5G-AN node;
- by sending a UE-specific NGAP UE-TNLA binding release message to 5G-AN and the 5G-AN node updates the NGAP UE-TNLA binding with the new TNL association. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.2.5 NGAP UE-TNLA-binding per UE Release procedure | At any time the AMF may decide to release the NGAP UE-TNLA binding while keeping the UE in CM-CONNECTED state while keeping the corresponding N3 interface. The AMF releases the NGAP UE-TNLA binding by sending a UE-specific NGAP UE-TNLA binding release message on the current TNL association.
If the AMF releases the NGAP UE-TNLA-binding without sending AMF unavailable status indication, then the AN may immediately trigger creation of a new NGAP-UE-TNLA-binding with the same AMF for subsequent N2 messages or may leave the NGAP UE association without NGAP UE-TNLA-binding. In the latter case the new NGAP UE-TNLA-binding is re-created upon the subsequent AN-initiated or AMF-initiated UE-specific N2 signalling as specified in clause 4.2.7.2.3.
If the AMF releases the NGAP UE-TNLA-binding after AMF unavailable status indication, then the AN has to re-create the NGAP-UE-TNLA-binding with a different AMF. The 5G-AN re-creates N2AP UE-TNLA-binding for subsequent N2 messages for the given UE as specified in clause 4.2.7.2.3. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.3 AMF Failure or Planned Maintenance handling procedure | For UE(s) in CM-CONNECTED state:
- If AMF failure is detected by 5G-AN, all NGAP UE TNLA binding for UEs served by that AMF are released.
- If AMF becomes unavailable due to planned maintenance, the AMF notifies the 5G-AN about the unavailable GUAMI(s) and provides optionally a target AMF Name corresponding to each unavailable GUAMI. The 5G-AN releases all NGAP UE TNLA binding of the UEs related to the indicated unavailable GUAMI(s) unless the notification from the AMF includes an indicator that the AMF will rebind or release the NGAP UE TNLA binding on a per UE-basis. In that case, if 5G-AN supports, the 5G-AN waits the release until the timer expires so that the AMF may release or rebind the N2AP UE-TNLA binding on per UE-basis.
- For the release NGAP TNLA binding, the affected UE is kept in CM-CONNECTED state and the corresponding N3 interface is also kept.
For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI, the 5G-AN uses 5G S-TMSI or GUAMI to select the target AMF, the 5G-AN forwards N2 message. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.4 Additional User Location Information with Mobile Base Station Relay (MBSR) | As described in clause 5.35A of TS 23.501 [2], when a UE is being served by an MBSR, for any N2 messages sent by NG-RAN to AMF, if the User Location Information is included, the N2 parameters shall also include the additional ULI of this MBSR.
When the AMF provides user location information to other NFs (e.g. LMF as specified in clause 5.9 of TS 23.273 [51]) for a UE connected via MBSR, the AMF may also send the Additional ULI received via N2 messages. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.7.5 Additional User Location Information with Mobile gNB with wireless access backhauling (MWAB) | When a UE is being served by an MWAB-gNB cell, for any N2 messages sent by NG-RAN to AMF, if the User Location Information is included, the N2 message shall also include the Additional ULI as described in clause 5.49.4 of TS 23.501 [2]. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.8 Void | 4.2.8a UE Capability Match Request procedure
If the AMF requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.16.3 of TS 23.501 [2]), then the AMF may send a UE Radio Capability Match Request message to the NG-RAN. This procedure is typically used during the registration procedure or when AMF has not received the Voice Support Match Indicator (as part of the 5GMM Context).
Figure 4.2.8a-1: UE Capability Match Request
1. The AMF indicates whether the AMF wants to receive Voice support match indicator. The AMF may include the UE radio capability information it has previously received from NG-RAN.
2. Upon receiving the UE Capability Match Request message, if the NG-RAN has not already received the UE radio capabilities from the UE or from AMF in step 1, the NG-RAN requests the UE to upload the UE radio capability information.
3. The UE provides the NG-RAN with its UE radio capabilities sending the RRC UE Capability Information.
4. The NG-RAN checks whether the UE radio capabilities are compatible with the network configuration for ensuring voice service continuity of voice calls initiated in IMS.
For determining the appropriate UE Radio Capability Match Response, the NG-RAN is configured by the operator to check whether the UE supports certain capabilities required for Voice continuity of voice calls using IMS PS. In a shared network, the NG-RAN keeps a configuration separately per PLMN.
NOTE 1: What checks to perform depends on network configuration, i.e. following are some examples of UE capabilities to be taken into account:
- E-UTRAN/NG-RAN Voice over PS capabilities;
- the Radio capabilities for E-UTRAN/NG-RAN FDD and/or TDD; and/or
- the support of E-UTRAN/NG-RAN frequency bands;
- the SRVCC from NG-RAN to UTRAN capabilities and the support of UTRAN frequency bands.
NOTE 2: The network configuration considered in the decision for the Voice Support Match Indicator is homogenous within a certain area (e.g. AMF Set) in order to guarantee that the Voice Support Match Indicator from the NG-RAN is valid within such area.
The NG-RAN provides a Voice Support Match Indicator to the AMF to indicate whether the UE capabilities and networks configuration are compatible for ensuring voice service continuity of voice calls initiated in IMS.
The AMF stores the received Voice support match indicator in the 5GMM Context and uses it as an input for setting the IMS voice over PS Session Supported Indication.
5. If NG-RAN requested radio capabilities from UE in step 2 and 3, the NG-RAN also sends the UE radio capabilities to the AMF. The AMF stores the UE radio capabilities without interpreting them for further provision to the NG-RAN according to clause 5.4.4.1 of TS 23.501 [2].
NOTE 3: Steps 4 and 5 could be received by the AMF in any order. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9 Network Slice-Specific Authentication and Authorization procedure | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.1 General | The Network Slice-Specific Authentication and Authorization procedure is triggered for an S-NSSAI requiring Network Slice-Specific Authentication and Authorization with an AAA Server (AAA-S) which may be hosted by the H-PLMN operator or by a third party which has a business relationship with the H-PLMN, using the EAP framework as described in TS 33.501 [15]. An AAA Proxy (AAA-P) in the HPLMN may be involved e.g. if the AAA Server belongs to a third party.
This procedure is triggered by the AMF during a Registration procedure when some Network Slices require Slice-Specific Authentication and Authorization, when AMF determines that Network Slice-Specific Authentication and Authorization is requires for an S-NSSAI in the current Allowed NSSAI or Partially Allowed NSSAI (e.g. subscription change), or when the AAA Server that authenticated the Network Slice triggers a re-authentication.
NOTE 1: The S-NSSAI in the procedure can be part of Allowed NSSAI, Mapping Of Allowed NSSAI, Partially Allowed NSSAI or Mapping Of Partially Allowed NSSAI.
The AMF performs the role of the EAP Authenticator and communicates with the AAA-S via the Network Slice specific and SNPN Authentication and Authorization Function (NSSAAF). The NSSAAF undertakes any AAA protocol interworking with the AAA protocol supported by the AAA-S.
The Network Slice-Specific Authentication and Authorization procedure requires the use of a GPSI. In other words, a subscription that contains S-NSSAIs subject to Network Slice-Specific Authentication and Authorization shall include at least one GPSI.
After a successful or unsuccessful UE Network Slice-Specific Authentication and Authorization, the AMF store the NSSAA result status for the related S-NSSAI in the UE context.
NOTE 2: If an S-NSSAI subject to the NSSAA is rejected due to Network Slice Admission Control (e.g. the maximum number of UEs per network slice has been reached), the NSSAA result status stored in the UE context is not impacted. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.2 Network Slice-Specific Authentication and Authorization | Figure 4.2.9.2-1: Network Slice-Specific Authentication and Authorization procedure
1. For S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization, based on change of subscription information, or triggered by the AAA-S, the AMF may trigger the start of the Network Slice Specific Authentication and Authorization procedure.
If Network Slice Specific Authentication and Authorization is triggered as a result of Registration procedure, the AMF may determine, based on UE Context in the AMF, that for some or all S-NSSAI(s) subject to Network Slice Specific Authentication and Authorization, the UE has already been authenticated following a Registration procedure on a first access. Depending on Network Slice Specific Authentication and Authorization result (e.g. success/failure) from the previous Registration, the AMF may decide, based on Network policies, to skip Network Slice Specific Authentication and Authorization for these S-NSSAIs during the Registration on a second access.
If the Network Slice Specific Authentication and Authorization procedure corresponds to a re-authentication and re-authorization procedure triggered as a result of AAA Server-triggered UE re-authentication and re-authorization for one or more S-NSSAIs, as described in 4.2.9.2, or triggered by the AMF based on operator policy or a subscription change and if S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization are included in the Allowed NSSAI for each Access Type, the AMF selects an Access Type to be used to perform the Network Slice Specific Authentication and Authorization procedure based on network policies.
2. The AMF may send an EAP Identity Request for the S-NSSAI in a NAS MM Transport message including the S-NSSAI. This is the S-NSSAI of the H-PLMN, not the locally mapped S-NSSAI value.
3. The UE provides the EAP Identity Response for the S-NSSAI alongside the S-NSSAI in an NAS MM Transport message towards the AMF.
4. The AMF sends the EAP Identity Response to the NSSAAF in a Nnssaaf_NSSAA_Authenticate Request (EAP Identity Response, GPSI, S-NSSAI).
NOTE: If the UE subscription includes multiple GPSIs, the AMF uses any GPSI in the list provided by the UDM for NSSAA procedures.
5. If the AAA-P is present (e.g. because the AAA-S belongs to a third party and the operator deploys a proxy towards third parties), the NSSAAF forwards the EAP ID Response message to the AAA-P, otherwise the NSSAAF forwards the message directly to the AAA-S. The NSSAAF is responsible to send the NSSAA requests to the appropriate AAA-S based on local configuration of AAA-S address per S-NSSAI. The NSSAAF uses towards the AAA-P or the AAA-S an AAA protocol message of the same protocol supported by the AAA-S.
6. The AAA-P forwards the EAP Identity message to the AAA-S addressable by the AAA-S address together with S-NSSAI and GPSI. The AAA-S stores the GPSI to create an association with the EAP Identity in the EAP ID response message, so the AAA-S can later use it to revoke authorization or to trigger reauthentication.
7-14. EAP-messages are exchanged with the UE. One or more than one iteration of these steps may occur.
15. EAP authentication completes. The AAA-S stores the S-NSSAI for which the authorisation has been granted, so it may decide to trigger reauthentication and reauthorization based on its local policies. An EAP-Success/Failure message is delivered to the AAA-P (or if the AAA-P is not present, directly to the NSSAAF) with GPSI and S-NSSAI.
16. If the AAA-P is used, the AAA-P sends an AAA Protocol message including (EAP-Success/Failure, S-NSSAI, GPSI) to the NSSAAF.
17. The NSSAAF sends the Nnssaaf_NSSAA_Authenticate Response (EAP-Success/Failure, S-NSSAI, GPSI) to the AMF.
18. The AMF transmits a NAS MM Transport message (EAP-Success/Failure) to the UE. The AMF shall store the EAP result for each S-NSSAI for which the NSSAA procedure in steps 1-17 was executed.
19a. [Conditional] If a new Allowed NSSAI (i.e. including any new S-NSSAIs in a Requested NSSAI for which the NSSAA procedure succeeded and/or excluding any S-NSSAI(s) in the existing Allowed NSSAI for the UE for which the procedure has failed, or including default S-NSSAI(s) if all S-NSSAIs in a Requested NSSAI or in the existing Allowed NSSAI are subject to NSSAA and due to failure of the NSSAA procedures, they cannot be in the Allowed NSSAI)) and/or new Rejected S-NSSAIs (i.e. including any S-NSSAI(s) in the existing Allowed NSSAI for the UE for which the procedure has failed, or any new requested S-NSSAI(s) for which the NSSAA procedure failed) need to be delivered to the UE, or if the AMF re-allocation is required, the AMF initiates the UE Configuration Update procedure, for each Access Type, as described in clause 4.2.4.2. If the Network Slice-Specific Re-Authentication and Re-Authorization fails and there are PDU session(s) established that are associated with the S-NSSAI for which the NSSAA procedure failed, the AMF shall initiate the PDU Session Release procedure as specified in clause 4.3.4 to release the PDU sessions with the appropriate cause value.
19b. [Conditional] If the Network Slice-Specific Authentication and Authorization fails for all S-NSSAIs (if any) in the existing Allowed NSSAI for the UE and (if any) for all S-NSSAIs in the Requested NSSAI and no default S-NSSAI could be added in the Allowed NSSAI, the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 and it shall include in the explicit De-Registration Request the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.3 AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure | Figure 4.2.9.3-1: AAA Server initiated Network Slice-Specific Re-authentication and Re-authorization procedure
1. The AAA-S requests the re-authentication and re-authorization for the Network Slice specified by the S-NSSAI in the AAA protocol Re-Auth Request message, for the UE identified by the GPSI in this message. This message is sent to a AAA-P, if the AAA-P is used (e.g. the AAA Server belongs to a third party), otherwise it is sent directly to the NSSAAF.
2. The AAA-P, if present, relays the request to the NSSAAF.
3a-3b. NSSAAF gets AMF ID from UDM using Nudm_UECM_Get with the GPSI in the received AAA message. If NSSAAF receives two different AMF address then the NSSAAF either decide to notify both AMFs or the NSSAF may decide to notify one AMF first and if NSSAA fails also notify the other AMF.
3c. The NSSAAF provides an acknowledgement to the AAA protocol Re-Auth Request message. If the AMF is not registered in UDM the procedure is stopped here.
4. If the AMF is registered in UDM, the NSSAAF notifies the AMF to re-authenticate/re-authorize the S-NSSAI for the UE using Nnssaaf_NSSAA_Re-AuthNotification with the GPSI and S-NSSAI in the received AAA message. The callback URI of the notification for the AMF is derived via NRF as specified in TS 29.501 [62].
5. If the UE is registered with the S-NSSAI in the Mapping Of Allowed NSSAI, the AMF triggers the Network Slice-Specific Authentication and Authorization procedure defined in clause 4.2.9.1. If the S-NSSAI is included in the Allowed NSSAI for 3GPP access and non-3GPP access, AMF selects an access type to perform NSSAA based on network policies. If the S-NSSAI is only included in the Allowed NSSAI of non-3GPP access and UE is CM-IDLE in non-3GPP access, the AMF marks the S-NSSAI as pending. In this case, when UE becomes CM-CONNECTED in non-3GPP access, the AMF initiates NSSAA if needed.
If the UE is registered but the S-NSSAI is not in the Mapping Of Allowed NSSAI, the AMF removes any status of the corresponding S-NSSAI subject to Network Slice-Specific Authentication and Authorization in the UE context it may have kept, so that an NSSAA is executed next time the UE requests to register with the S-NSSAI. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.9.4 AAA Server triggered Slice-Specific Authorization Revocation | Figure 4.2.9.4-1: AAA Server-initiated Network Slice-Specific Authorization Revocation procedure
1. The AAA-S requests the revocation of authorization for the Network Slice specified by the S-NSSAI in the AAA protocol Revoke Auth Request message, for the UE identified by the GPSI in this message. This message is sent to AAA-P if it is used.
2. The AAA-P, if present, relays the request to the NSSAAF.
3a-3b. The NSSAAF gets AMF ID from UDM using Nudm_UECM_Get with the GPSI in the received AAA message. If two different AMF addresses are received, the NSSAAF initiates the step 4 towards both AMFs.
3c. The NSSAAF provides an acknowledgement to the AAA protocol Re-Auth Request message. If the AMF is not registered in UDM the procedure is stopped here.
4. If the AMF is registered in UDM, the NSSAAF notifies the AMF to revoke the S-NSSAI authorization for the UE using Nnssaaf_NSSAA_RevocationNotification with the GPSI and S-NSSAI in the received AAA message. The callback URI of the notification for the AMF is derived via NRF as specified in TS 29.501 [62].
5. If the UE is registered with the S-NSSAI in the Mapping Of Allowed NSSAI, the AMF updates the UE configuration to revoke the S-NSSAI from the current Allowed NSSAI, for any Access Type for which Network Slice Specific Authentication and Authorization had been successfully run on this S-NSSAI. The UE Configuration Update may include a request to Register if the AMF needs to be re-allocated. The AMF provides a new Allowed NSSAI to the UE by removing the S-NSSAI for which authorization has been revoked. The AMF provides new rejected NSSAIs to the UE including the S-NSSAI for which authorization has been revoked. If no S-NSSAI is left in Allowed NSSAI for an access after the revocation and a Default NSSAI exists that requires no Network Slice Specific Authentication or for which a Network Slice Specific Authentication did not previously fail over this access, then the AMF may provide a new Allowed NSSAI to the UE containing the Default NSSAI. If no S-NSSAI is left in Allowed NSSAI for an access after the revocation and no Default NSSAI can be provided to the UE in the Allowed NSSAI or a previous Network Slice Specific Authentication failed for the Default NSSAI over this access, then the AMF shall execute the Network-initiated Deregistration procedure for the access as described in clause 4.2.2.3.3 and it 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 there are PDU session(s) established that are associated with the revoked S-NSSAI, the AMF shall initiate the PDU Session Release procedure as specified in clause 4.3.4 to release the PDU sessions with the appropriate cause value.
If the UE is registered but the S-NSSAI is not in the Mapping Of Allowed NSSAI, the AMF removes any status it may have kept of the corresponding S-NSSAI subject to Network Slice-Specific Authentication and Authorization in the UE context. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.10 N3 data transfer establishment procedure when Control Plane CIoT 5GS Optimisation is enabled | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.10.1 UE triggered N3 data transfer establishment procedure | If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2 of TS 23.501 [2], then the UE may, e.g. based on the amount of data to be transferred in uplink, initiate N3 data transfer establishment procedure for any PDU session for which Control Plane Only Indicator was not included.
The UE triggered N3 data transfer establishment procedure may be initiated by the UE in CM-IDLE or CM-CONNECTED state and follows the UE triggered Service Request procedure as defined in clause 4.2.3.2 with the following differences.
Step 1.
The UE includes in the AN message a Service Request for Control Plane CIoT 5GS Optimisation (List Of PDU Sessions To Be Activated, List Of Allowed PDU Sessions, security parameters, PDU Session status, [NAS message container])).
The List Of PDU Sessions To Be Activated is provided by UE when the UE wants to activate user plane resources for the PDU Session(s). The UE shall not include PDU sessions for which Control Plane Only Indicator was received in the List Of PDU Sessions To Be Activated. If the UE is camping on NB-IoT, the UE shall construct the List of PDU Sessions To Be Activated to not exceed 2 PDU session(s) with active user plane resources.
If this procedure is triggered for paging response and the UE has at the same time some user data to be transferred, the UE may decide to request N3 data transfer establishment for one of more PDU sessions. The UE indicates this in the List Of PDU Sessions To Be Activated. Otherwise the UE does not identify any PDU Session in the List Of PDU Sessions To Be Activated.
Step 4 or 5a.
Upon reception of Nsmf_PDUSession_UpdateSMContext Request or after SMF initiated SM Policy Association Modification, based on UE request and local policies, the SMF decides whether to establish N3 data transfer for the PDU session. The SMF shall not decide to establish N3 data transfer for a PDU session for which Control Plane Only Indicator was received.
Step 11.
The SMF indicates in Nsmf_PDUSession_UpdateSMContext Response whether to establish N3 data transfer, i.e. activate Data Radio Bearer and N3 tunnel, for the PDU session.
Step 12.
If the RAT type is NB-IoT, the AMF shall ensure that number of PDU Sessions with active user plane resources does not exceed 2. If the AMF decides to not include a PDU Session to be activated in the N2 message, the AMF indicates this to the SMF in step 15 Nsmf_PDUSession_UpdateSMContext Request in the List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element.
The AMF includes a NAS service accept for Control Plane CIoT 5GS Optimisation containing information on the PDU sessions with established N3 data transfer, based on the request(s) from the SMF(s) in step 11.
The network starts using N3 bearers for all DL data on this PDU session. Control Plane CIoT 5GS Optimisation is considered enabled for data transfer for all PDU sessions without established N3 data transfer.
Step 13.
The UE starts using N3 bearers for all UL data on this PDU session. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.10.2 SMF triggered N3 data transfer establishment procedure | If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the SMF may, e.g. based on the amount of data to be transferred or due to congestion, initiate N3 data transfer establishment procedure for any PDU session for which Control Plane Only Indicator was not included.
The SMF triggered N3 data transfer establishment procedure may be initiated by the SMF while the UE is in CM-IDLE or CM-CONNECTED state and follows the Network Triggered Service Request procedure defined in clause 4.2.3.3 with the following differences:
Step 3a.
The SMF request the activation of Data Radio Bearer and N3 tunnel for the PDU session in Namf_Communication_N1N2MessageTransfer.
Step 3b.
If the RAT type is NB-IoT and the UE already has 2 PDU Sessions with active user plane resources, the AMF shall not proceed with the rest of the procedure and instead the AMF shall respond with Namf_Communication_N1N2MessageTransfer Response with appropriate failure message.
Step 6.
The UE triggered N3 data transfer establishment procedure defined in clause 4.2.10.1 is applied instead of Service Request procedure from clause 4.2.3.2.
Step 7.
When the N3 data transfer is set up for a PDU session, the UE and the network shall only use user plane radio bearers to transfer data PDUs on that PDU Session. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11 Network Slice Admission Control Function (NSACF) procedures | |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.1 General | The Network Slice Admission Control Function procedures are performed for an S-NSSAI which is subject to Network Slice Admission Control (NSAC) as described in TS 23.501 [2]. If charging needs to be enabled, the NSACF may act as a NF (CTF) and interact with the CHF to support the Event based charging as defined in TS 32.290 [42].
Depending on the NSAC architecture deployed in the network, three options of NSAC procedures are defined:
- Option 1: The NSAC procedure for number of UEs or PDU sessions for an S-NSSAI is based on non-Hierarchal NSAC architecture. The corresponding procedures are described in clause 4.2.11.2 and clause 4.2.11.4 respectively.
- Option 2: The NSAC procedure for number of UEs or PDU sessions for an S-NSSAI is based on centralized NSAC architecture. The corresponding procedures are described in clause 4.2.11.2 and clause 4.2.11.4 respectively.
- Option 3: The NSAC procedure for number of UEs or PDU sessions for an S-NSSAI is based on hierarchical NSAC architecture. The corresponding procedures are described in clause 4.2.11.2a and clause 4.2.11.4a respectively. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.2 Number of UEs per network slice availability check and update procedure | This clause applies to Non-Hierarchical and centralized NSAC architectures. The difference between the two architectures for the various steps, where applicable, is described at the end of the clause.
The number of UEs per network slice availability check and update procedure is to update (i.e. increase or decrease) the number of UEs registered with an S-NSSAI which is subject to NSAC. The AMF is configured with the information indicating which network slice is subject to NSAC.
Figure 4.2.11.2-1: Number of UEs per network slice availability check and update procedure
1. If the AMF is not aware of which NSACF to communicate, the AMF performs NSACF discovery as described in clause 6.3.22 of TS 23.501 [2] and in clause 5.2.7.3.2. The AMF triggers the Number of UEs per network slice availability check and update procedure to update the number of UEs registered with a network slice when a network slice subject to NSAC is included in the Allowed NSSAI or Partially Allowed NSSAI (i.e. the AMF requests to register the UE with the S-NSSAI) or removed from the Allowed NSSAI or Partially Allowed NSSAI (i.e. the AMF requests to de-register the UE from the S-NSSAI) for a UE. The trigger event at the AMF also includes the change of Allowed NSSAI or Partially Allowed NSSAI in the case of inter-AMF mobility. The procedure is triggered in the following cases:
- At UE Registration procedure, according to clause 4.2.2.2.2 (including Registration types of Initial Registration or Mobility Registration Update in inter-AMF mobility in CM-CONNECTED or CM-IDLE state):
- before the Registration Accept in step 21 if the EAC mode is active; or
- after the Registration Accept message if the EAC mode is not active;
- At UE Deregistration procedure, as per clause 4.2.2.3, after the Deregistration procedure is completed;
- At UE Configuration Update procedure (which may result from NSSAA procedure or subscribed S-NSSAI change):
- before the UE Configuration Update message if the EAC mode is active and the update flag is to increase; or
- after the UE Configuration Update message if the EAC mode is active and the update flag is to decrease; or
- after the UE Configuration Update message if the EAC mode is not active.
NOTE 1: Depending on the deployment, there may be different NSACF for different S-NSSAI subject to NSAC and hence, during the registration, AMF triggers the Number of UEs per network slice availability check and update procedure to multiple NSACFs.
2. The AMF sends Nnsacf_NSAC_NumOfUEsUpdate_Request message to the NSACF. The AMF includes in the message the UE ID, Access Type to which the Allowed NSSAI or Partially Allowed NSSAI is applied, the S-NSSAI(s), the NF ID and the update flag which indicates whether the number of UEs registered with the S-NSSAI(s) is to be increased when the UE has gained registration to network slice(s) subject to NSAC or the number of UEs registered with the S-NSSAI(s) is to be decreased when the UE has deregistered from S-NSSAI(s) or could not renew its registration to an S-NSSAI subject to NSAC.
If this is the first time to perform NSAC procedure for the S-NSSAI towards the NSACF, the AMF includes notification endpoint for EAC Notification to implicitly subscribe the EAC notification for the S-NSSAI from the NSACF.
3. The NSACF determines whether the Access Type provided by the AMF is configured for the NSAC based on its configuration. If the Access Type is not configured for the NSAC, the NSACF always accepts the request from the AMF without increasing or decreasing the number of UEs. If the Access Type is configured for the NSAC, the NSACF updates the current number of UEs registered for the S-NSSAI, i.e. increases or decrease the number of UEs registered per network slice based on the information provided by the AMF in the update flag parameter.
If the update flag parameter from the AMF indicates increase, the following applies:
- If the UE ID is already in the list of UEs registered with the network slice, the current number of UEs is not increased as the UE has already been counted as registered with the network slice. The NSACF creates a new entry associated with this new update and shall also maintain the old entry associated with previous update. The multiple entries for the same UE ID in the NSACF are differentiated based on the NF ID of the NF sending the update request. The NSACF removes the entry associated with the NF ID upon reception of a request having update flag indicating decrease.
NOTE 2: The use case of having two or more entries in the NSACF for the same UE can happen during (a) inter-AMF mobility when the new AMF request update to the NSACF before the old AMF sends request to deregister the UE; or (b) PDN connections establishment in the EPC when multiple SMF +PGW-Cs (i.e. used for different PDN Connections associated with the same S-NSSAI) send update requests for maximum number of UEs to the NSACF.
NOTE 3: To handle AMF graceful removal, the NSACF can subscribe for unavailability notifications with the AMF (directly or via NRF) as described in clause 5.21.2.2 and act accordingly, e.g. update the NF ID with the target AMF ID.
- If the UE ID is not in the list of UE IDs registered with the network slice and the maximum number of UEs registered with the network slice has not been reached yet, the NSACF adds the UE ID in the list of UEs registered with the network slice as a new entry associated with this new update and increases the current number of the UEs registered with the network slice. If the UE ID is not in the list of UEs registered with that S-NSSAI and the maximum number of UEs for that S-NSSAI has already been reached, then the NSACF returns a result parameter indicating that the maximum number of UEs registered with the network slice has been reached.
If the update flag parameter from the AMF indicates decrease and if there is only one entry associated with the UE ID, the NSACF removes the UE ID from the list of UEs registered with the network slice for each of the S-NSSAI(s) indicated in the request from the AMF and also the NSACF decreases the number of UEs per network slice that is maintained by the NSACF for each of these network slices. If there are multiple entries associated with the UE ID, the NSACF removes the entry associated with the NF ID but the UE ID is kept in the list of UEs registered with the S-NSSAI.
The NSACF takes access type into account for increasing and decreasing the number of UEs per network slice as described in clause 5.15.11.1 of TS 23.501 [2].
The NSACF stores the notification endpoint for EAC Notification associated with the S-NSSAI if it is received from the AMF. The NSACF can use this AMF notification endpoint to update the EAC mode as described in clause 4.2.11.3.
NOTE 4: This enables the NSACF to maintain up-to-date information about the AMFs serving the S-NSSAIs.
4. The NSACF returns the Nnsacf_NSAC_NumOfUEsUpdate_Response message including Result indication per S-NSSAI. The Result indication includes either 'maximum number of UEs registered with the network slice reached' or 'maximum number of UEs registered with the network slice not reached'.
At UE Registration procedure, if only some of the S-NSSAIs reached the maximum number of UEs per S-NSSAI, the AMF sends a Registration Accept message to the UE in which the AMF includes the rejected S-NSSAI(s) in the rejected NSSAI list for which the NSACF has indicated that the maximum number of UEs per network slice has been reached and for each rejected S-NSSAI the AMF includes a reject cause set to 'maximum number of UEs per network slice reached' and optionally a back-off timer.
When for all the Requested S-NSSAI(s) provided in step 2 the NSACF returned the maximum number of UEs per network slice has been reached and if one or more subscribed S-NSSAIs are marked as default in the subscription data and not subject to NSAC, the AMF can decide to include these Default Subscribed S-NSSAIs in the Allowed NSSAI. Otherwise, the AMF rejects the UE request for registration. In the Registration Reject message, the AMF includes the rejected S-NSSAI(s) in the rejected NSSAI parameter and for each rejected S-NSSAI the AMF includes a reject cause to indicate that the maximum number of UEs per network slice has been reached and optionally a back-off timer.
NOTE 5: If the use case requires the UE to remain reachable at all times with at least one slice, it is recommended that at least one of the Subscribed S-NSSAIs is marked as the default S-NSSAI which is not subject to NSAC. This will ensure the UE is able to access to services even when maximum number of UEs per network slice has been reached.
For a centralized architecture the following differences apply:
- In step 2, the AMF additionally includes the NSAC service area the AMF belongs to, if available, as an additional parameter in the Nnsacf_NSAC_NumOfUEsUpdate_Request.
- In step 3, based on operator configuration, the NSACF performs the validation against the maximum number of Registered UEs registered per NSAC service area defined for the network slice if applicable and available, or the maximum number of Registered UEs in the entire PLMN for the network slice. Additionally the NSACF stores the NSAC service area of AMF if available.
NOTE 6: When a centralized NSAC architecture is deployed, NSACF does not perform any readmission at inter-AMF mobility since the UE is already admitted if the validation of maximum number of Registered UEs against the entire PLMN.
4.2.11.2a Hierarchical NSACF-based number of UEs per network slice availability check and update procedure
Figure 4.2.11.2a-1: Hierarchical NSACF-based number of UEs per network slice availability check and update procedure
For an S-NSSAIs subject to counting of the number of registered UEs, if hierarchical NSACF architecture is deployed in the network the enforcement of maximum number of UEs registered for an S-NSSAI is performed as follows:
1. Same as the step 1 defined in clause 4.2.11.2.
2. In addition to the information included in the Nnsacf_NSAC_NumOfUEsUpdate_Request as described in the step 2 of clause 4.2.11.2, the AMF may provide UE already registered indication to the NSACF if the UE has been registered with the S-NSSAI in another NSAC service area before. The AMF determines the 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).
3. The NSACF performs NSAC for the indicated S-NSSAI.
If the update flag parameter from the AMF indicates increase, the following applies:
- For NSACF which support UE admission quota based control:
- If the local maximum number of UEs is not reached yet, the NSACF executes the same action as specified in the step 3 in clause 4.2.11.2. The steps 4-8 are skipped.
- If the local maximum number of UEs is reached, the NSACF sends a delegation request to the Primary NSACF. Steps 4-9 are executed.
- For NSACF which supports UE admission threshold-based control, as defined in clause 5.15.11.1.2 of TS 23.501 [2]:
- If the UE admission is below the threshold level, the NSACF executes the same action as the step 3 defined in clause 4.2.11.2. Steps 4-8 are skipped.
- If the UE admission is at or above the threshold level and the local maximum number of UEs has not been reached, the NSACF checks whether the UE already registered indication is present.
- If the UE already registered indication is not present then the NSACF immediately rejects the NSAC request. Steps 4-8 are skipped.
- If the UE already registered indication is present the NSACF executes the same action as the step 3 defined in clause 4.2.11.2 in order to allow for service continuity. Steps 4-8 are skipped.
- If the local maximum number has been reached and the UE already registered indication is present then the NSACF sends a delegation request of NSAC to the Primary NSACF in order to allow for service continuity. Steps 4-9 are executed.
If the update flag parameter from the AMF indicates decrease, the following applies:
- If the UE entry to be deleted is stored at the NSACF, the NSACF executes the same action as the step 3 defined in clause 4.2.11.2. Steps 4-8 are skipped.
- If the UE entry to be deleted is not stored at the NSACF, the NSACF sends a delegation request of NSAC to the Primary NSACF. Steps 4-9 are executed.
4. If the Primary NSACF has not been discovered before, the NSACF discovers and selects the Primary NSACF which manages the entire PLMN NSAC service area according to clause 6.3.22 of TS 23.501 [2].
5. The NSACF invokes Nnsacf_NSAC_NumOfUEsUpdate_Request service operation to the Primary NSACF. The request includes the NSAC request information received from AMF, which may include the UE already Registered indication only if it is received from AMF and the UE admission type is quota-based.
6. The Primary NSACF performs NSAC for the indicated S-NSSAI.
If the update flag parameter from the NSACF indicates increase, the following applies:
- If the Primary NSACF decided to delegate the NSAC update request to the NSACF, per the applied UE admission type of the network, the Primary NSACF adjusts the local maximum number for UE quota-based admission or the UE admission threshold for UE admission-threshold in its response to the NSACF. The Primary NSACF does not create a new entry associated with the UE ID in the received NSAC request.
NOTE 1: When NSACF sends a delegation request to the Primary NSACF, the Primary NSACF either increases local maximum number at NSACF or rejects the NSAC request.
- For quota-based admission type and if the Primary NSACF decided not to delegate the request to the NSACF and the UE already Registered indication is not included, the Primary NSACF rejects the NSAC request. If the UE already Registered indication is included and if the Primary NSACF decided to store the UE entry, it creates a new entry associated with the UE ID within the received NSAC. If the Primary NSACF is not able to store the UE entry, the Primary NSACF rejects the request. The Primary NSACF respond accordingly the NSACF as in step 7.
- For threshold-based admission and if the Primary NSACF decided not to delegate the request to the NSACF, the same action as for step 3 in clause 4.2.11.2 is executed with the replacement of NSACF with Primary NSACF.
NOTE 2: To support the session continuity across different NSAC service area, the Primary NSACF always reserves part of the global maximum number for its own use, i.e. the whole global maximum number is not distributed to all contacted NSACF(s).
If the update flag parameter from the NSACF indicates decrease and the UE entry is managed by the Primary NSACF, the same action as step 3 in clause 4.2.11.2 is executed with the replacement of NSACF with Primary NSAC. This applies to both admission types.
7. The Primary NSACF returns the Nnsacf_NSAC_NumOfUEsUpdate_Response message to the NSACF. The response may include the Result indication as described in step 4 in clause 4.2.11.2.
If the Primary NSACF determines to adjust the configured value stored at the NSACF, the updated local maximum number of UEs or UE admission threshold is also included in the response respectively.
8. The NSACF checks the response from Primary NSACF.
If the response includes the updated configured value,
- The NSACF, which supports UE admission quota based control, replaces the existing local maximum number of UEs with the received updated value. The same action is executed as for step 3 in clause 4.2.11.2 based on the updated configured value.
- The NSACF, which supports UE admission threshold based control, replaces the existing UE admission threshold with the received updated value. The same action is executed as for step 3 in clause 4.2.11.2 based on the updated configured value.
If the response does not include the updated configured value, the NSACF returns the response to AMF based on the received NSAC response from Primary NSACF.
9. Same as for step 4 defined in clause 4.2.11.2. |
fe7d56f8e2b5a29b90140ea988c1e8a1 | 23.502 | 4.2.11.3 Configuration for Early Admission Control (EAC) update procedure | The configuration for Early Admission Control (EAC) update procedure indicates to the AMF the activation or the deactivation of the EAC mode for the S-NSSAI subject to NSAC. EAC mode means that the AMF is required to perform the number of UEs per network slice availability check and update procedure before the S-NSSAI subject to NSAC is included in the Allowed NSSAI or Partially Allowed NSSAI and sent to the UE. EAC mode is only applicable in the AMF when the update flag is set to increase.
The AMF implicitly subscribes to the EAC notification for the S-NSSAI when it performs the first network slice availability check and update procedure for the S-NSSAI with the NSACF. The NSACF sends the EAC mode notification towards all notification endpoints associated with the S-NSSAI.
Figure 4.2.11.3-1: Early Admission Control (EAC) update procedure
1. The number of UEs registered with a network slice subject to NSAC crosses a certain operator defined threshold. The NSACF determines whether to activate or deactivate the EAC mode.
2. The NSACF triggers Nnsacf_NSAC_EACNotify operation including the S-NSSAI(s) for which the EAC mode is to be activated or deactivated and a EAC flag(s) set to activated if the number of UEs registered with the network slice is above certain threshold or set to deactivated if the number of the UEs registered with the network slice is below certain threshold which may be same or different with respect to the activation threshold.
NOTE 1: When the operator set the EAC inactive threshold, the Denial-of-Service issue due to a potential burst of registration request needs to be taken into account.
3. The AMF uses the EAC flag to decide when to trigger the number of UEs per network slice availability check and update procedure so that delays to the registration procedure and impact to the already allowed network slices are avoided.
If the EAC flag indicates EAC mode activated, the AMF triggers the number of UEs per network slice availability check and update procedure before the Registration Accept step of the registration procedure or before the UE Configuration Update message.
If the EAC flag indicates EAC mode deactivated, the AMF triggers the number of UEs per network slice availability check and update procedure after Registration Accept step of the registration procedure or after the UE Configuration Update.
NOTE 2: When the S-NSSAI subject to NSAC and NSSAA, with EAC mode activated or deactivated, the AMF performs them as described in clause 4.2.11.2. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.