Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.502  Word version:   16.4.0

Top   None   None   Next
1…   4.2.2.2.2   4.2.2.2.3…   4.2.3…   4.2.3.3   4.2.4…   4.2.6   4.2.7…   4.2.9…   4.3…   4.3.2.2…   4.3.2.2.2   4.3.2.2.3…   4.3.3   4.3.4   4.3.5…   4.3.5.2…   4.3.5.4…   4.3.5.6…   4.3.6…   4.4…   4.5…   4.9…   4.9.1.3…   4.9.2…   4.11…   4.11.1.2.2…   4.11.1.3…   4.11.1.4…   4.11.1.5…   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.16…   4.16.4…   4.16.8…   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…   A…   E…   F…

 

1  ScopeWord-p. 20
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  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]  IETF RFC 5998: "An Extension for EAP-Only Authentication in IKEv2".
[5]  IETF RFC 4282: "The Network Access Identifier".
[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]  3GPP TS 23.335"User Data Convergence (UDC); Technical realization and information flows; Stage 2".
[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]  3GPP TS 23.221 "Architectural requirements ".
[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]  3GPP TS 29.519 "5G System; Usage of the Unified Data Repository service for Policy Control Data and Structured Data; Stage 3".
[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]  OMA-TS-ULP-V2_0_3: "UserPlane Location Protocol".
[28]  3GPP TS 23.167 "IP Multimedia Subsystem (IMS) emergency sessions".
[29]  3GPP TS 23.271 "Functional stage 2 description of Location Services (LCS)".
[30]  3GPP TS 36.355 "LTE Positioning Protocol (LPP)".
[31]  3GPP TS 38.455 "NR Positioning Protocol A (NRPPa)".
[32]  3GPP TS 29.507 "Access and Mobility Policy Control Service; Stage 3".
[33]  3GPP TS 23.003 "Numbering, Addressing and Identification".
[34]  3GPP TS 32.240 "Charging management; Charging architecture and principles".
[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]  IEEE P802.1Qcc: "Standard for Local and metropolitan area networks - Bridges and Bridged Networks - Amendment: Stream Reservation Protocol (SRP) Enhancements and Performance Improvements".
[66]  IEEE 802.1Q-2018: "IEEE Standard for Local and Metropolitan Area Networks-Bridges and Bridged Networks".
[67]  IEEE 802.1Qbv-2015: "IEEE Standard for Local and metropolitan area networks -- Bridges and Bridged Networks - Amendment 25: Enhancements for Scheduled Traffic".
[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".
Up
3  Definitions, symbols and abbreviationsWord-p. 22
3.1  Definitions
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.
Up
3.2  AbbreviationsWord-p. 23
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.
Up
4  System procedures
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.
4.2  Connection, Registration and Mobility Management procedures
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.
Up
4.2.2  Registration Management procedures
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.
Up
4.2.2.2  Registration procedures
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, 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
  • Periodic Registration Update (due to a predefined time period of inactivity); or
  • Emergency Registration.
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 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.
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) registering for emergency services only (referred to as Emergency Registration), see TS 23.501, clause 5.16.4.
During the initial registration the PEI is obtained from the UE. If the AMF needs the PEI in the initial registration, it should retrieve the PEI as it establishes the NAS security context with a Security Mode Command. The AMF operator may check the PEI with an EIR. The AMF passes the PEI to the UDM, to the SMF and the PCF, then UDM may store this data in UDR by Nudr_SDM_Update.
NOTE 1:
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 can provide Steering of Roaming information to the UE via the AMF (i.e. a list of preferred PLMN/access technology combinations or HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list 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 TS 23.501, clause 5.3.2.3.
Up

Up   Top   ToC