My 3GPP 24.501 notes - Revision history

Paul: /* 4.4.1 General */

2023-07-16T15:24:35Z

4.4.1 General

← Older revision		Revision as of 10:24, 16 July 2023
Line 70:		Line 70:

	=== 4.4.1 General ===		=== 4.4.1 General ===
	This clause describes the principles for the handling of 5G NAS security contexts in the UE and in the AMF, the procedures used for the <span style="color:blue">security protection of NAS messages between the UE and the AMF</span>, and the procedures used for the <span style="color:blue">protection of NAS IEs between the UE and the UDM</span>. Security protection involves integrity protection and ciphering of the 5GMM messages. 5GSM messages are security protected indirectly by being piggybacked by the security protected 5GMM messages (i.e. UL NAS TRANSPORT message and the DL NAS TRANSPORT message).		This clause describes the principles for the handling of 5G NAS security contexts in the UE and in the AMF, the procedures used for the <span style="color:blue">security protection of NAS messages between the UE and the AMF</span>, and the procedures used for the <span style="color:blue">protection of NAS IEs between the UE and the UDM</span>. <span style="color:purple">Security protection involves integrity protection and ciphering of the 5GMM messages. 5GSM messages are security protected indirectly by being piggybacked by the security protected 5GMM messages (i.e. UL NAS TRANSPORT message and the DL NAS TRANSPORT message)</span>.

	The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.		The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.

Paul: /* 4.4.1 General */

2023-07-16T15:16:14Z

4.4.1 General

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

	The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.		The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.
	<span style="color:~~red~~">:NOTE: ''The use of ciphering in a network is an operator option.'' In this subclause, for the ease of description, it is assumed that ciphering is used, unless explicitly indicated otherwise. Operation of a network without ciphering is achieved by configuring the AMF so that it always selects the "null ciphering algorithm", 5G-EA0.</span>
			<span style="color:green">NOTE ''The use of ciphering in a network is an operator option.'' In this subclause, for the ease of description, it is assumed that ciphering is used, unless explicitly indicated otherwise. Operation of a network without ciphering is achieved by configuring the AMF so that it always selects the "null ciphering algorithm", 5G-EA0.</span>

	=== 4.4.2 Handling of 5G NAS security contexts ===		=== 4.4.2 Handling of 5G NAS security contexts ===

Paul: /* 4.4.1 General */

2023-07-16T15:15:37Z

4.4.1 General

← Older revision		Revision as of 10:15, 16 July 2023
Line 73:		Line 73:

	The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.		The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.
	:NOTE: ''The use of ciphering in a network is an operator option.'' In this subclause, for the ease of description, it is assumed that ciphering is used, unless explicitly indicated otherwise. Operation of a network without ciphering is achieved by configuring the AMF so that it always selects the "null ciphering algorithm", 5G-EA0.		<span style="color:red">:NOTE: ''The use of ciphering in a network is an operator option.'' In this subclause, for the ease of description, it is assumed that ciphering is used, unless explicitly indicated otherwise. Operation of a network without ciphering is achieved by configuring the AMF so that it always selects the "null ciphering algorithm", 5G-EA0.</span>

	=== 4.4.2 Handling of 5G NAS security contexts ===		=== 4.4.2 Handling of 5G NAS security contexts ===

Paul: /* 4.4.1 General */

2023-07-16T15:14:57Z

4.4.1 General

← Older revision		Revision as of 10:14, 16 July 2023
Line 70:		Line 70:

	=== 4.4.1 General ===		=== 4.4.1 General ===
	This clause describes the principles for the handling of 5G NAS security contexts in the UE and in the AMF, the procedures used for the security protection of NAS messages between the UE and the AMF, and the procedures used for the protection of NAS IEs between the UE and the UDM. Security protection involves integrity protection and ciphering of the 5GMM messages. 5GSM messages are security protected indirectly by being piggybacked by the security protected 5GMM messages (i.e. UL NAS TRANSPORT message and the DL NAS TRANSPORT message).		This clause describes the principles for the handling of 5G NAS security contexts in the UE and in the AMF, the procedures used for the <span style="color:blue">security protection of NAS messages between the UE and the AMF</span>, and the procedures used for the <span style="color:blue">protection of NAS IEs between the UE and the UDM</span>. Security protection involves integrity protection and ciphering of the 5GMM messages. 5GSM messages are security protected indirectly by being piggybacked by the security protected 5GMM messages (i.e. UL NAS TRANSPORT message and the DL NAS TRANSPORT message).

	The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.		The signalling procedures for the control of NAS security are part of the 5GMM protocol and are described in detail in clause 5.

Paul: /* 5.5.1.2.2 Initial registration initiation */

2023-02-09T21:15:27Z

5.5.1.2.2 Initial registration initiation

← Older revision		Revision as of 16:15, 9 February 2023
Line 1,203:		Line 1,203:
	The UE initiates the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF, starting timer T3510. If timer T3502 is currently running, the UE shall stop timer T3502. If timer T3511 is currently running, the UE shall stop timer T3511.		The UE initiates the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF, starting timer T3510. If timer T3502 is currently running, the UE shall stop timer T3502. If timer T3511 is currently running, the UE shall stop timer T3511.

	During initial registration the UE handles the 5GS mobile identity IE in the following order:		<span style="color:red">During initial registration the UE handles the 5GS mobile identity IE in the following order:</span>
	<ol type="a">		<ol type="a">
	<li>if:		<li>if:

Paul: /* 4.4.5 Ciphering of NAS signalling messages */

2023-01-18T20:15:29Z

4.4.5 Ciphering of NAS signalling messages

← Older revision		Revision as of 15:15, 18 January 2023
Line 147:		Line 147:
	<span style="color:red">'''The use of ciphering in a network is an operator option subject to AMF configuration'''</span>. <span style="color:red">When operation of the network without ciphering is configured, the AMF shall indicate the use of "null ciphering algorithm" 5G-EA0 (see subclause 9.11.3.34) in the current 5G NAS security context for all UEs</span>. For setting the security header type in outbound NAS messages, the UE and the AMF shall apply the same rules irrespective of whether the "null ciphering algorithm" or any other ciphering algorithm is indicated in the 5G NAS security context.		<span style="color:red">'''The use of ciphering in a network is an operator option subject to AMF configuration'''</span>. <span style="color:red">When operation of the network without ciphering is configured, the AMF shall indicate the use of "null ciphering algorithm" 5G-EA0 (see subclause 9.11.3.34) in the current 5G NAS security context for all UEs</span>. For setting the security header type in outbound NAS messages, the UE and the AMF shall apply the same rules irrespective of whether the "null ciphering algorithm" or any other ciphering algorithm is indicated in the 5G NAS security context.

	When the UE establishes a new N1 NAS signalling connection, it shall apply security protection to the initial NAS message as described in subclause 4.4.6.		<span style="color:red">When the UE establishes a new N1 NAS signalling connection, it shall apply security protection to the initial NAS message as described in subclause 4.4.6.
			</span>
	The UE shall start the ciphering and deciphering of NAS messages when the secure exchange of NAS messages has been established for an N1 NAS signalling connection. From this time onward, unless explicitly defined, the UE shall send all NAS messages ciphered until the N1 NAS signalling connection is released, or the UE performs inter-system change to S1 mode.		The UE shall start the ciphering and deciphering of NAS messages when the secure exchange of NAS messages has been established for an N1 NAS signalling connection. From this time onward, unless explicitly defined, the UE shall send all NAS messages ciphered until the N1 NAS signalling connection is released, or the UE performs inter-system change to S1 mode.

Paul: /* 4.4.6 Protection of initial NAS signalling messages */

2023-01-18T19:41:30Z

4.4.6 Protection of initial NAS signalling messages

← Older revision		Revision as of 14:41, 18 January 2023
Line 176:		Line 176:
	</ol>		</ol>
	</ol>		</ol>
	When the initial NAS message is a REGISTRATION REQUEST message, the cleartext IEs are:		<span style="color:red">When the initial NAS message is a REGISTRATION REQUEST message, the cleartext IEs are</span>:
	* Extended protocol discriminator;		* Extended protocol discriminator;
	* Security header type;		* Security header type;
Line 183:		Line 183:
	* 5GS registration type;		* 5GS registration type;
	* ngKSI;		* ngKSI;
	* 5GS mobile identity;		* <span style="color:red">5GS mobile identity</span>;
	* UE security capability;		* UE security capability;
	* Additional GUTI;		* Additional GUTI;

Paul: /* 4.25 Support of MUSIM features */

2023-01-18T19:34:14Z

4.25 Support of MUSIM features

← Older revision		Revision as of 14:34, 18 January 2023
Line 552:		Line 552:

	== 4.25 Support of MUSIM features ==		== 4.25 Support of MUSIM features ==
	<pre>MUSIM UE: A UE with multiple valid USIMs, capable of initiating and maintaining simultaneous separate registration states over 3GPP access with PLMN(s) using identities and credentials associated with those USIMs and supporting one or more of the N1 NAS signalling connection release, the paging indication for voice services, the reject paging request, the paging restriction and the paging timing collision control (see 3GPP TS 23.501).		<pre>MUSIM UE: A UE with multiple valid Universal Subscriber Identity Modules (USIMs), capable of initiating and maintaining simultaneous separate registration states over 3GPP access with PLMN(s) using identities and credentials associated with those USIMs and supporting one or more of the N1 NAS signalling connection release, the paging indication for voice services, the reject paging request, the paging restriction and the paging timing collision control (see 3GPP TS 23.501).

	Source: 3GPP TS 24.501</pre>		Source: 3GPP TS 24.501</pre>

Paul: /* 9.11 Other information elements */

2023-01-18T19:20:33Z

9.11 Other information elements

← Older revision		Revision as of 14:20, 18 January 2023
Line 1,415:		Line 1,415:
	=== 9.11.1 General ===		=== 9.11.1 General ===

	The different formats (V, LV, T, TV, TLV, LV-E, TLV-E) and the five categories of information elements (type 1, 2, 3, 4 and 6) are defined in 3GPP TS 24.007.		<span style="color:red">The different formats (V, LV, T, TV, TLV, LV-E, TLV-E) and the five categories of information elements (type 1, 2, 3, 4 and 6) are defined in 3GPP TS 24.007.</span>

	The first octet of an information element in the non-imperative part contains the IEI of the information element. If this octet does not correspond to an IEI known in the message, the receiver shall determine whether this IE is of type 1 or 2 (i.e., it is an information element of one octet length) or an IE of type 4 (i.e., that the next octet is the length indicator indicating the length of the remaining of the information element) (see 3GPP TS 24.007).		The first octet of an information element in the non-imperative part contains the IEI of the information element. If this octet does not correspond to an IEI known in the message, the receiver shall determine whether this IE is of type 1 or 2 (i.e., it is an information element of one octet length) or an IE of type 4 (i.e., that the next octet is the length indicator indicating the length of the remaining of the information element) (see 3GPP TS 24.007).

Paul: /* 9.11.3 5GS mobility management (5GMM) information elements */

2022-12-06T16:15:09Z

9.11.3 5GS mobility management (5GMM) information elements

← Older revision		Revision as of 11:15, 6 December 2022
Line 1,436:		Line 1,436:

	See spec for details...		See spec for details...

			==== <span style="color:red">9.11.3.4 5GS mobile identity</span> ====

			<span style="color:red">The purpose of the 5GS mobile identity information element is to provide either the SUCI, the 5G-GUTI, the IMEI, the IMEISV, the 5G-S-TMSI, the MAC address or the EUI-64.</span>

			The 5GS mobile identity information element is coded as shown in figures 9.11.3.4.1, 9.11.3.4.2, 9.11.3.4.3, 9.11.3.4.4, 9.11.3.4.5, 9.11.3.4.6, 9.11.3.4.8 and 9.11.3.4.7, and table 9.11.3.4.1.

			The 5GS mobile identity is a type 6 information element with a minimum length of 4.

			See spec for figures and details...


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