Tech-invite3GPPspaceIETF RFCsSIP

Content for  TS 23.502  Word version:  17.5.0

Top   Top   None   None   Next
1……   4.2.3…   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3……   4.3.3…   4.3.4…   4.3.5…………   4.3.6…   4.4…   4.5…   4.9……   4.9.2…   4.11……………   4.11.2…   4.11.3…   4.12…   4.12.6…   4.12a…   4.12b…   4.13…   4.13.4…   4.13.6…   4.14…   4.15……   4.15.4……   4.15.7…   4.16…   4.16.4…   4.16.8…   4.16.11…   4.17…   4.17.9…   4.18…   4.19…   4.23…   4.23.7…   4.23.9…   4.23.11…   4.24…   4.25…   4.26…   5…   5.2.3…   5.2.5…   5.2.6…   5.2.7…   5.2.8…   5.2.9…   5.2.12…   5.2.18…   A…   E…   F…


1  ScopeWord‑p. 24

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 and for the policy and charging control framework which is described in TS 23.503.

2  ReferencesWord‑p. 24

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.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 23.501: "System Architecture for the 5G System; Stage 2".
RFC 7296:  "Internet Key Exchange Protocol Version 2 (IKEv2)".
[4]  Void.
[5]  Void.
RFC 4861:  "Neighbor Discovery for IP version 6 (IPv6)".
TS 23.040: "Technical realization of the Short Message Service (SMS)".
RFC 4862:  "IPv6 Stateless Address Autoconfiguration".
TS 38.300: "NR and NG-RAN Overall Description; Stage 2".
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[11]  Void.
TS 38.331: "NR; Radio Resource Control (RRC); Protocol Specification".
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[14]  Void.
TS 33.501: "Security Architecture and Procedures for 5G System".
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[19]  Void.
TS 23.503: "Policy and Charging Control Framework for the 5G System ".
RFC 4191:  "Default Router Preferences and More-Specific Routes".
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station in idle mode".
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
TS 23.203: "Policy and charging control architecture".
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
TS 23.402: "Architecture enhancements for non-3GPP accesses".
[27]  Void.
TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[29]  Void.
[30]  Void.
[31]  Void.
TS 29.507: "Access and Mobility Policy Control Service; Stage 3".
TS 23.003: "Numbering, Addressing and Identification".
[34]  Void.
TS 23.251: "Network sharing; Architecture and functional description".
TS 29.502: "5G System; Session Management Services; Stage 3".
TS 29.510: "5G System; Network function repository services; Stage 3".
TS 23.380: "IMS Restoration Procedures".
TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
RFC 4555:  "IKEv2 Mobility and Multihoming Protocol (MOBIKE)".
TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via Non-3GPP Access Networks (N3AN); Stage 3".
TS 32.290: "Services, operations and procedures of charging using Service Based Interface (SBI)".
TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
TS 38.304: "NR; User Equipment (UE) procedures in idle mode".
TS 32.255: "5G system; 5G data connectivity domain charging; Stage 2".
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
TS 29.513: "5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3".
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".
RFC 2410:  "The NULL Encryption Algorithm and its use with IPsec".
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services; Stage 2".
TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
TS 29.503: "5G System; Unified Data Management Services; Stage 3".
TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
TS 29.525: "5G System; UE Policy Control Service; Stage 3".
RFC 6696:  "EAP Extensions for the EAP Re-authentication Protocol (ERP)", July 2012.
RFC 5295:  "Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)", Aug. 2008.
TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
TS 29.561: "5G System; Interworking between 5G Network and external Data Networks; Stage 3".
TS 29.413: "Application of the NG Application Protocol (NGAP) to non-3GPP access".
IEEE Std 802.1Qcc-2018: "Standard for Local and metropolitan area networks - Bridges and Bridged Networks - Amendment: Stream Reservation Protocol (SRP) Enhancements and Performance Improvements".
IEEE Std 802.1Q-2018: "IEEE Standard for Local and Metropolitan Area Networks-Bridges and Bridged Networks".
[67]  Void.
TS 23.632: "User Data Interworking, Coexistence and Migration".
TS 29.244: "Interface between the Control Plane and the User Plane nodes".
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
TS 32.256: "Charging Management; 5G connection and mobility domain charging; Stage 2".
TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".
IEEE Std 802.1AS-2020: "IEEE Standard for Local and metropolitan area networks--Timing and Synchronization for Time-Sensitive Applications".
IEEE Std 1588-2019: "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control".
TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
TS 23.247: "Architectural enhancements for 5G multicast-broadcast services".
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2".
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
TS 29.519: "5G System; Usage of the Unified Data Repository service for Policy Data, Application Data and Structure Data for Exposure; Stage 3".
TS 23.558: "Architecture for enabling Edge Applications".

3  Definitions, symbols and abbreviationsWord‑p. 27

3.1  DefinitionsWord‑p. 27

For the purposes of the present document, the terms and definitions given in TR 21.905, TS 23.501 and TS 23.503 apply. A term defined in TS 23.501 or TS 23.503 takes precedence over the definition of the same term, if any, in any other specifications.

3.2  AbbreviationsWord‑p. 27

For the purposes of the present document, the abbreviations given in TR 21.905, TS 23.501 and TS 23.503 apply. An abbreviation defined in TS 23.501 or TS 23.503 takes precedence over the definition of the same abbreviation, if any, in any other specifications.

4  System proceduresWord‑p. 27

4.1  GeneralWord‑p. 27

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.

4.2  Connection, Registration and Mobility Management proceduresWord‑p. 27

4.2.1  GeneralWord‑p. 27

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.

4.2.2  Registration Management proceduresWord‑p. 27  GeneralWord‑p. 27

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.
Up  Registration proceduresWord‑p. 28  GeneralWord‑p. 28
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, 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
  • 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; or
  • Disaster Roaming Mobility Registration Update, as specified in clause 5.40 of TS 23.501; 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
The General Registration call flow in clause 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 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.
Aspects related to dual registration in 3GPP and non-3GPP access are described in clause 4.12. The general Registration call flow in clause 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 is also used by UEs in limited service state (see TS 23.122) registering for emergency services only (referred to as Emergency Registration), see clause 5.16.4 of TS 23.501.
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.
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 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.
The AMF determines Access Type and RAT Type as defined in clause of TS 23.501.

Up   Top   ToC