My 3GPP 23.502 Notes - Revision history

Paul: /* 4.2.2.2 Registration procedures */

2022-12-06T18:58:31Z

4.2.2.2 Registration procedures

← Older revision		Revision as of 13:58, 6 December 2022
Line 15:		Line 15:
	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 Short Message Service (SMS) over Non-Access Stratum (NAS) is defined in clause 4.13.		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 Short Message Service (SMS) over Non-Access Stratum (NAS) is defined in clause 4.13.

	==== 4.2.2.2 Registration procedures ====		==== 4.2.2.2 <span style="color:red">Registration procedures</span> ====

	===== 4.2.2.2.1 General =====		===== 4.2.2.2.1 General =====

Paul: /* 4.2 Connection, Registration and Mobility Management procedures */

2022-12-06T18:57:54Z

4.2 Connection, Registration and Mobility Management procedures

← Older revision		Revision as of 13:57, 6 December 2022
Line 8:		Line 8:

	=== 4.2.1 General ===		=== 4.2.1 General ===
	The Connection Management is used to establish and release the Control Plane signalling connection between the User Equipment (UE) and the Access & Mobility Function (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.		The Connection Management is used to establish and release the Control Plane signalling connection between the User Equipment (UE) and the Access & Mobility Function (AMF). <span style="color:red">The Registration Management is used to register or deregister a UE/user with the 5GS and establish the user context in the 5GS</span>. 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 procedures ===		=== 4.2.2 Registration Management procedures ===

Paul: /* 4.2.2.2.1 General */

2022-12-06T17:23:46Z

4.2.2.2.1 General

← Older revision		Revision as of 12:23, 6 December 2022
Line 31:		Line 31:
	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 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 Information Elements (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:		The following are the <span style=blue"color:">cleartext Information Elements (IEs)</span>, as defined in TS 24.501 that <span style="color:red">can be sent by the UE in the Registration Request message if the UE has no NAS security context</span>:
	* Registration type;		* Registration type;
	* SUCI or 5G-GUTI or PEI;		* <span style="color:red">SUCI or 5G-GUTI or PEI</span>;
	* Security parameters;		* Security parameters;
	* additional GUTI;		* additional GUTI;

Paul: /* 4.2.2.2.1 General */

2022-12-06T17:22:36Z

4.2.2.2.1 General

← Older revision		Revision as of 12:22, 6 December 2022
Line 20:		Line 20:

	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:		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;		* <span style="color:red">Initial Registration to the 5GS</span>;
	* 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 Local Area Data Network (LADN) Information, or with NR satellite access upon changing to a suitable cell indicating multiple TAs for the Registered Public Land Mobile Network (RPLMN) all of which are outside the UE's Registration Area in both CM-CONNECTED and CM-IDLE state, or when the Multi-USIM (Universal Subscriber Identity Module) UE needs a new 5G Globally Unique Temporary Identifier (5G-GUTI) assignment; or		* 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 Local Area Data Network (LADN) Information, or with NR satellite access upon changing to a suitable cell indicating multiple TAs for the Registered Public Land Mobile Network (RPLMN) all of which are outside the UE's Registration Area in both CM-CONNECTED and CM-IDLE state, or when the Multi-USIM (Universal Subscriber Identity Module) UE needs a new 5G Globally Unique Temporary Identifier (5G-GUTI) assignment; or
	* Periodic Registration Update (due to a predefined time period of inactivity); or		* Periodic Registration Update (due to a predefined time period of inactivity); or

Paul: initial page creation

2022-10-17T16:16:35Z

initial page creation

New page

3GPP TS 23.502 document defines 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. There are different versions of 23.502, see

== 4.1 General ==

Section 4 describes the procedures and Network Function services for the 5G System (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 User Equipment (UE) and the Access & Mobility Function (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 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 Short Message Service (SMS) over Non-Access Stratum (NAS) is defined in clause 4.13.

==== 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 Local Area Data Network (LADN) Information, or with NR satellite access upon changing to a suitable cell indicating multiple TAs for the Registered Public Land Mobile Network (RPLMN) all of which are outside the UE's Registration Area in both CM-CONNECTED and CM-IDLE state, or when the Multi-USIM (Universal Subscriber Identity Module) UE needs a new 5G Globally Unique Temporary Identifier (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
* Standalone Non-Public Network (SNPN) Onboarding Registration allows the UE to access an Onboarding Standalone Non-Public Network (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 Onboarding Network (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 Information Elements (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.
: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) 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.
: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 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 5.3.2.3 of TS 23.501.

===== 4.2.2.2.2 General Registration =====

<center>[[Telecommunications info|To Telecommunications info]]</center>