My 3GPP 23.501 Notes - Revision history

Paul: /* § 4.2.6 Service-based interfaces */

2023-07-16T16:01:00Z

§ 4.2.6 Service-based interfaces

← Older revision		Revision as of 11:01, 16 July 2023
Line 73:		Line 73:
	* Wireline Access Gateway Function (W-AGF).		* Wireline Access Gateway Function (W-AGF).
	* Trusted WLAN Interworking Function (TWIF).		* Trusted WLAN Interworking Function (TWIF).

			==§ 4.2.3 Non-roaming reference architecture ==

			See spec for diagrams and details.

	==§ 4.2.6 Service-based interfaces ==		==§ 4.2.6 Service-based interfaces ==

Paul: /* 5.3.3 Connection Management */

2023-07-16T15:56:18Z

5.3.3 Connection Management

← Older revision		Revision as of 10:56, 16 July 2023
Line 307:		Line 307:

	=== 5.3.3 Connection Management ===		=== 5.3.3 Connection Management ===

			==== 5.3.3.1 General ====

			Connection management comprises the functions of establishing and releasing a NAS signalling connection between a UE and the AMF over N1. This NAS signalling connection is used to enable NAS signalling exchange between the UE and the core network. It comprises both the AN signalling connection between the UE and the AN (RRC Connection over 3GPP access or UE-N3IWF connection over untrusted N3GPP access or UE-TNGF connection over trusted N3GPP access) and the N2 connection for this UE between the AN and the AMF.

			==== 5.3.3.2 5GS Connection Management states ====

			===== 5.3.3.2.1 General =====
			Two CM states are used to reflect the NAS signalling Connection of the UE with the AMF:
			* CM-IDLE
			* CM-CONNECTED
			The CM state for 3GPP access and Non-3GPP access are independent of each other, i.e. one can be in CM-IDLE state at the same time when the other is in CM-CONNECTED state.

	==§ 5.4.7 NG-RAN location reporting==		==§ 5.4.7 NG-RAN location reporting==

Paul: /* 5.3.2.2.3 RM-REGISTERED state */

2023-07-16T15:53:44Z

5.3.2.2.3 RM-REGISTERED state

← Older revision		Revision as of 10:53, 16 July 2023
Line 305:		Line 305:
	* perform Implicit Deregistration at any time after the Implicit Deregistration timer expires. The AMF shall enter RM-DEREGISTERED state for the UE after Implicit Deregistration;		* perform Implicit Deregistration at any time after the Implicit Deregistration timer expires. The AMF shall enter RM-DEREGISTERED state for the UE after Implicit Deregistration;
	* when applicable, accept or reject Registration Requests or Service Requests from the UE.		* when applicable, accept or reject Registration Requests or Service Requests from the UE.

			=== 5.3.3 Connection Management ===

	==§ 5.4.7 NG-RAN location reporting==		==§ 5.4.7 NG-RAN location reporting==

Paul: /* 5.5.1 Registration Management */

2023-05-16T15:07:12Z

5.5.1 Registration Management

@@ Line 325: / Line 325: @@
 This clause describe the specific aspects for untrusted non-3GPP access, trusted non-3GPP access and W-5GAN access.
-=== 5.5.1	Registration Management ===
+=== 5.5.1 Registration Management ===
 This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN (Wireline 5G Access Network). In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG (5G Residential Gateway) or to the W-AGF (Wireline Access Gateway Function) in the case of FN-RG (Fixed Network Residential Gateway). In the case of N5CW (Non-5G-Capable over WLAN) devices access 5GC (5G Core Network) via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF (Trusted WLAN Interworking Function).
 == 7.2 Network Function Services ==

Paul: /* 5.5 Non-3GPP access specific aspects */

2023-03-02T20:44:03Z

5.5 Non-3GPP access specific aspects

@@ Line 327: / Line 327: @@
 === 5.5.1	Registration Management ===
 This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN (Wireline 5G Access Network). In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG (5G Residential Gateway) or to the W-AGF (Wireline Access Gateway Function) in the case of FN-RG (Fixed Network Residential Gateway). In the case of N5CW (Non-5G-Capable over WLAN) devices access 5GC (5G Core Network) via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF (Trusted WLAN Interworking Function).
 <center>[[Telecommunications_info|To Telecommunications Info]]</center>

Paul: /* 5.3.1 General */

2023-01-19T14:47:31Z

5.3.1 General

← Older revision		Revision as of 09:47, 19 January 2023
Line 253:		Line 253:
	=== 5.3.1 General ===		=== 5.3.1 General ===

	The Registration Management is used to register or deregister a UE/user with the network, and establish the user context in the network. The Connection Management is used to establish and release the signalling connection between the UE and the AMF.		The Registration Management is used to register or deregister a UE/user with the network (via AMF), and establish the user context in the network. The Connection Management is used to establish and release the signalling connection between the UE and the AMF.

	=== 5.3.2 Registration Management ===		=== 5.3.2 Registration Management ===

Paul: /* § 5.2.7 Lawful Interception */

2022-12-06T18:19:31Z

§ 5.2.7 Lawful Interception

@@ Line 248: / Line 248: @@
 ==§ 5.2.7 Lawful Interception ==
 For definition and functionality of Lawful Interception, see TS 33.126.
 ==§ 5.4.7 NG-RAN location reporting==

Paul: /* § 5.2.2 Network Selection */

2022-11-01T17:40:23Z

§ 5.2.2 Network Selection

← Older revision		Revision as of 12:40, 1 November 2022
Line 233:		Line 233:
	==§ 5.2.2 Network Selection==		==§ 5.2.2 Network Selection==

	<span style="color:red">To determine which PLMN to attempt registration, UE performs network selection. The network selection procedure comprises two main parts, PLMN selection and access network (AN) selection. The requirements for PLMN selection are specified in TS 22.011 and the procedures are in TS 23.122.</span> The access network (AN) selection part for the 3GPP access networks is specified in TS 36.300 for E-UTRAN and in TS 38.300 for the NR. The network selection for Disaster Roaming is described in TS 23.122 and TS 24.501.		<span style="color:red">To determine which PLMN to attempt registration, UE performs network selection. The network selection procedure comprises two main parts, PLMN selection and access network (AN) selection. The requirements for PLMN selection are specified in TS 22.011 § 3.2 and the procedures are in TS 23.122.</span> The access network (AN) selection part for the 3GPP access networks is specified in TS 36.300 for E-UTRAN and in TS 38.300 for the NR. The network selection for Disaster Roaming is described in TS 23.122 and TS 24.501.

	==§ 5.2.3 Identification and authentication==		==§ 5.2.3 Identification and authentication==

Paul: /* § 5.2.2 Network Selection */

2022-11-01T15:15:29Z

§ 5.2.2 Network Selection

← Older revision		Revision as of 10:15, 1 November 2022
Line 232:		Line 232:

	==§ 5.2.2 Network Selection==		==§ 5.2.2 Network Selection==
	To determine which PLMN to attempt registration, UE performs network selection. The network selection procedure comprises two main parts, PLMN selection and access network (AN) selection. The requirements for PLMN selection are specified in TS 22.011 and the procedures are in TS 23.122. The access network (AN) selection part for the 3GPP access networks is specified in TS 36.300 for E-UTRAN and in TS 38.300 for the NR. The network selection for Disaster Roaming is described in TS 23.122 and TS 24.501.
			<span style="color:red">To determine which PLMN to attempt registration, UE performs network selection. The network selection procedure comprises two main parts, PLMN selection and access network (AN) selection. The requirements for PLMN selection are specified in TS 22.011 and the procedures are in TS 23.122.</span> The access network (AN) selection part for the 3GPP access networks is specified in TS 36.300 for E-UTRAN and in TS 38.300 for the NR. The network selection for Disaster Roaming is described in TS 23.122 and TS 24.501.

	==§ 5.2.3 Identification and authentication==		==§ 5.2.3 Identification and authentication==

Paul: /* 4.2.8.1 General Concepts to Support Trusted and Untrusted Non-3GPP Access */

2022-10-31T20:41:12Z

4.2.8.1 General Concepts to Support Trusted and Untrusted Non-3GPP Access

← Older revision		Revision as of 15:41, 31 October 2022
Line 197:		Line 197:
	A UE shall establish an IPsec tunnel with the N3IWF or with the TNGF in order to register with the 5G Core Network over non-3GPP access. Further details about the UE registration to 5G Core Network over untrusted non-3GPP access and over trusted non-3GPP access are described in clause 4.12.2 and in clause 4.12.2a of TS 23.502, respectively.		A UE shall establish an IPsec tunnel with the N3IWF or with the TNGF in order to register with the 5G Core Network over non-3GPP access. Further details about the UE registration to 5G Core Network over untrusted non-3GPP access and over trusted non-3GPP access are described in clause 4.12.2 and in clause 4.12.2a of TS 23.502, respectively.

	It shall be possible to maintain the UE NAS signalling connection with the AMF over the non-3GPP access after all the PDU Sessions for the UE over that access have been released or handed over to 3GPP access.		<span style="color:red">It shall be possible to maintain the UE NAS signalling connection with the AMF over the non-3GPP access after all the PDU Sessions for the UE over that access have been released or handed over to 3GPP access.</span>

	N1 NAS signalling over non-3GPP accesses shall be protected with the same security mechanism applied for N1 over a 3GPP access.		<span style="color:red">N1 NAS signalling over non-3GPP accesses shall be protected with the same security mechanism applied for N1 over a 3GPP access.</span>

	User plane QoS differentiation between UE and N3IWF is supported as described in clause 5.7 and clause 4.12.5 of TS 23.502. QoS differentiation between UE and TNGF is supported as described in clause 5.7 and clause 4.12a.5 of TS 23.502.		User plane QoS differentiation between UE and N3IWF is supported as described in clause 5.7 and clause 4.12.5 of TS 23.502. QoS differentiation between UE and TNGF is supported as described in clause 5.7 and clause 4.12a.5 of TS 23.502.