My 3GPP 38.300 Notes - Revision history

Paul: /* 4.1 Overall Architecture */

2023-01-18T19:07:37Z

4.1 Overall Architecture

← Older revision		Revision as of 14:07, 18 January 2023
Line 1:		Line 1:
			== Scope ==

			The 38.300 document provides an overview and overall description of the NG-RAN and focuses on the radio interface protocol architecture of NR connected to 5GC (E-UTRA connected to 5GC is covered in the 36 series). Details of the radio interface protocols are specified in companion specifications of the 38 series.

	== 4.1 Overall Architecture ==		== 4.1 Overall Architecture ==

Paul: /* 5.2.5.3 Cell search */

2022-11-27T21:57:41Z

5.2.5.3 Cell search

← Older revision		Revision as of 16:57, 27 November 2022
Line 105:		Line 105:

	==== 5.2.5.3 Cell search ====		==== 5.2.5.3 Cell search ====
	Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the Cell ID of that cell. NR cell search is based on the primary and secondary synchronization signals, and Physical Broadcast Channel (PBCH) Demodulation Reference Signal (DMRS), located on the synchronization raster.		<span style="color:red">Cell search is the procedure by which a UE acquires time and frequency synchronization with a cell and detects the Cell ID of that cell. NR cell search is based on the primary and secondary synchronization signals, and Physical Broadcast Channel (PBCH) Demodulation Reference Signal (DMRS), located on the synchronization raster.</span>

	==== 5.2.5.4 HARQ ====		==== 5.2.5.4 HARQ ====

Paul: /* Section 9 Mobility and State Transitions */

2022-11-21T22:06:06Z

Section 9 Mobility and State Transitions

← Older revision		Revision as of 17:06, 21 November 2022
Line 252:		Line 252:

	== Section 9 Mobility and State Transitions ==		== Section 9 Mobility and State Transitions ==
			=== 9.1 Overview ===
	~~'''~~9.1 Overview~~'''~~

	Load balancing is achieved in New Radio (NR) with handover, redirection mechanisms upon Radio Resource Controller (RRC) release and through the usage of inter-frequency and inter-RAT (Radio Access Type) absolute priorities and inter-frequency Qoffset parameters.		Load balancing is achieved in New Radio (NR) with handover, redirection mechanisms upon Radio Resource Controller (RRC) release and through the usage of inter-frequency and inter-RAT (Radio Access Type) absolute priorities and inter-frequency Qoffset parameters.

Paul: /* 8.2 Network Identities */

2022-11-21T22:05:43Z

8.2 Network Identities

← Older revision		Revision as of 17:05, 21 November 2022
Line 234:		Line 234:

	The following identities are used in NG-RAN for identifying a specific network entity:		The following identities are used in NG-RAN for identifying a specific network entity:
	* AMF Name: used to identify an AMF.		* <span style="color:red">AMF Name</span>: used to identify an AMF.
	* NR Cell Global Identifier (NCGI): used to identify NR cells globally. The NCGI is constructed from the PLMN identity the cell belongs to and the NR Cell Identity (NCI) of the cell. The PLMN ID included in the NCGI should be the first PLMN ID within the set of PLMN IDs associated to the NR Cell Identity in SIB1, following the order of broadcast.		* <span style="color:red">NR Cell Global Identifier (NCGI)</span>: used to identify NR cells globally. The NCGI is constructed from the PLMN identity the cell belongs to and the NR Cell Identity (NCI) of the cell. The PLMN ID included in the NCGI should be the first PLMN ID within the set of PLMN IDs associated to the NR Cell Identity in SIB1, following the order of broadcast.

	:NOTE 1: How to manage the scenario where a different PLMN ID has been allocated by the operator for an NCGI is left to OAM and/or implementation.		:NOTE 1: How to manage the scenario where a different PLMN ID has been allocated by the operator for an NCGI is left to OAM and/or implementation.

	* gNB Identifier (gNB ID): used to identify gNBs within a PLMN. The gNB ID is contained within the NCI of its cells.		* <span style="color:red">gNB Identifier (gNB ID)</span>: used to identify gNBs within a PLMN. The gNB ID is contained within the NCI of its cells.
	* Global gNB ID: used to identify gNBs globally. The Global gNB ID is constructed from the PLMN identity the gNB belongs to and the gNB ID. The MCC and MNC are the same as included in the NCGI.		* Global gNB ID: used to identify gNBs globally. The Global gNB ID is constructed from the PLMN identity the gNB belongs to and the gNB ID. The MCC and MNC are the same as included in the NCGI.

Paul: /* Section 8 Next Generation (NG) Identities */

2022-11-21T22:04:42Z

Section 8 Next Generation (NG) Identities

Paul: /* 7.6 Transport of NAS Messages */

2022-11-21T22:02:20Z

7.6 Transport of NAS Messages

← Older revision		Revision as of 17:02, 21 November 2022
Line 182:		Line 182:
	=== 7.6 Transport of NAS Messages ===		=== 7.6 Transport of NAS Messages ===

	New Radio (NR) provides reliable in-sequence delivery of Non-Access Stratum (NAS) messages over Signalling Radio Bearers (SRBs) in Radio Resource Controller (RRC), except at handover where losses or duplication can occur when Packet Data Convergence Protocol (PDCP) is re-established. In RRC, NAS messages are sent in transparent containers. Piggybacking of NAS messages can occur in the following scenarios:		<span style="color:red">New Radio (NR) provides reliable in-sequence delivery of Non-Access Stratum (NAS) messages over Signalling Radio Bearers (SRBs) in Radio Resource Controller (RRC), except at handover where losses or duplication can occur when Packet Data Convergence Protocol (PDCP) is re-established.</span> In RRC, NAS messages are sent in transparent containers. Piggybacking of NAS messages can occur in the following scenarios:
	* At bearer establishment/modification/release in the Downlink (DL);		* At bearer establishment/modification/release in the Downlink (DL);
	* For transferring the initial NAS message during connection setup and connection resume in the Uplink (UL).		* For transferring the initial NAS message during connection setup and connection resume in the Uplink (UL).

Paul: /* 4.4.2 Control Plane (CP) */

2022-11-21T22:00:13Z

4.4.2 Control Plane (CP)

← Older revision		Revision as of 17:00, 21 November 2022
Line 88:		Line 88:
	* PDCP, RLC and MAC sublayers (terminated in gNB on the network side) perform the functions listed in clause 6;		* PDCP, RLC and MAC sublayers (terminated in gNB on the network side) perform the functions listed in clause 6;
	* RRC (terminated in gNB on the network side) performs the functions listed in clause 7;		* RRC (terminated in gNB on the network side) performs the functions listed in clause 7;
	* NAS control protocol (terminated in AMF on the network side) performs the functions listed in TS 23.501, for instance: authentication, mobility management, security control…		* <span style="color:red">NAS control protocol</span> (terminated in AMF on the network side) performs the functions listed in TS 23.501, for instance: authentication, mobility management, security control…

	[[File:Protocol stack Radio CP.png\|center\|Protocol stack Radio CP]]		[[File:Protocol stack Radio CP.png\|center\|Protocol stack Radio CP]]

Paul: /* 4.4.2 Control Plane (CP) */

2022-11-21T21:59:28Z

4.4.2 Control Plane (CP)

← Older revision		Revision as of 16:59, 21 November 2022
Line 88:		Line 88:
	* PDCP, RLC and MAC sublayers (terminated in gNB on the network side) perform the functions listed in clause 6;		* PDCP, RLC and MAC sublayers (terminated in gNB on the network side) perform the functions listed in clause 6;
	* RRC (terminated in gNB on the network side) performs the functions listed in clause 7;		* RRC (terminated in gNB on the network side) performs the functions listed in clause 7;
	* NAS control protocol (terminated in AMF on the network side) performs the functions listed in TS 23.501), for instance: authentication, mobility management, security control…		* NAS control protocol (terminated in AMF on the network side) performs the functions listed in TS 23.501, for instance: authentication, mobility management, security control…

	[[File:Protocol stack Radio CP.png\|center\|Protocol stack Radio CP]]		[[File:Protocol stack Radio CP.png\|center\|Protocol stack Radio CP]]

Paul: /* 4.2 Functional Split */

2022-11-21T21:51:40Z

4.2 Functional Split

← Older revision		Revision as of 16:51, 21 November 2022
Line 1:		Line 1:
			== 4.1 Overall Architecture ==

			An NG-RAN node is either:
			* a gNB, providing NR user plane and control plane protocol terminations towards the UE; or
			* an ng-eNB, providing E-UTRA user plane and control plane protocol terminations towards the UE.

			The gNBs and ng-eNBs are interconnected with each other by means of the Xn interface. The gNBs and ng-eNBs are also connected by means of the NG interfaces to the 5GC, more specifically to the AMF (Access and Mobility Management Function) by means of the NG-C interface and to the UPF (User Plane Function) by means of the NG-U interface (see TS 23.501).
			:NOTE: The architecture and the F1 interface for a functional split are defined in TS 38.401.

	== 4.2 Functional Split ==		== 4.2 Functional Split ==

Paul: /* 4.3.1.2 NG Control Plane */

2022-11-21T21:48:57Z

4.3.1.2 NG Control Plane

← Older revision		Revision as of 16:48, 21 November 2022
Line 21:		Line 21:
	==== 4.3.1.2 NG Control Plane ====		==== 4.3.1.2 NG Control Plane ====

	The NG control plane interface (NG-C) is defined between the NG-RAN node and the AMF. The control plane protocol stack of the NG interface is shown on following figure. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as NGAP (NG Application Protocol). The SCTP layer provides guaranteed delivery of application layer messages. In the transport, IP layer point-to-point transmission is used to deliver the signalling PDUs.		<span style="color:red">The NG control plane interface (NG-C) is defined between the NG-RAN node and the AMF.</span> The control plane protocol stack of the NG interface is shown on following figure. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as NGAP (NG Application Protocol). The SCTP layer provides guaranteed delivery of application layer messages. In the transport, IP layer point-to-point transmission is used to deliver the signalling PDUs.

	<center>[[File:Protocol stack NG-C.png\|Protocol stack NG-C]]</center>		<center>[[File:Protocol stack NG-C.png\|Protocol stack NG-C]]</center>
Line 29:		Line 29:
	* UE context management;		* UE context management;
	* UE mobility management;		* UE mobility management;
	* Transport of NAS messages;		* <span style="color:red">Transport of NAS messages</span>;
	* Paging;		* Paging;
	* PDU Session Management;		* PDU Session Management;

← Older revision		Revision as of 17:04, 21 November 2022
Line 194:		Line 194:
	== Section 8 Next Generation (NG) Identities ==		== Section 8 Next Generation (NG) Identities ==

	~~'''~~8.1 UE Identities~~'''~~		=== 8.1 UE Identities ===

	In this clause, the identities used by NR connected to 5GC are listed. For scheduling at cell level, the following identities are used:		In this clause, the identities used by NR connected to 5GC are listed. For scheduling at cell level, the following identities are used:
Line 231:		Line 231:
	* MCCH-RNTI: Identifies transmissions of MCCH and MCCH change notification.		* MCCH-RNTI: Identifies transmissions of MCCH and MCCH change notification.

	~~'''~~8.2 Network Identities~~'''~~		=== 8.2 Network Identities ===

	The following identities are used in NG-RAN for identifying a specific network entity:		The following identities are used in NG-RAN for identifying a specific network entity:
Line 237:		Line 237:
	* NR Cell Global Identifier (NCGI): used to identify NR cells globally. The NCGI is constructed from the PLMN identity the cell belongs to and the NR Cell Identity (NCI) of the cell. The PLMN ID included in the NCGI should be the first PLMN ID within the set of PLMN IDs associated to the NR Cell Identity in SIB1, following the order of broadcast.		* NR Cell Global Identifier (NCGI): used to identify NR cells globally. The NCGI is constructed from the PLMN identity the cell belongs to and the NR Cell Identity (NCI) of the cell. The PLMN ID included in the NCGI should be the first PLMN ID within the set of PLMN IDs associated to the NR Cell Identity in SIB1, following the order of broadcast.

	NOTE 1: How to manage the scenario where a different PLMN ID has been allocated by the operator for an NCGI is left to OAM and/or implementation.		:NOTE 1: How to manage the scenario where a different PLMN ID has been allocated by the operator for an NCGI is left to OAM and/or implementation.

	* gNB Identifier (gNB ID): used to identify gNBs within a PLMN. The gNB ID is contained within the NCI of its cells.		* gNB Identifier (gNB ID): used to identify gNBs within a PLMN. The gNB ID is contained within the NCI of its cells.
	* Global gNB ID: used to identify gNBs globally. The Global gNB ID is constructed from the PLMN identity the gNB belongs to and the gNB ID. The MCC and MNC are the same as included in the NCGI.		* Global gNB ID: used to identify gNBs globally. The Global gNB ID is constructed from the PLMN identity the gNB belongs to and the gNB ID. The MCC and MNC are the same as included in the NCGI.

	NOTE 2: It is not precluded that a cell served by a gNB does not broadcast the PLMN ID included in the Global gNB ID.		:NOTE 2: It is not precluded that a cell served by a gNB does not broadcast the PLMN ID included in the Global gNB ID.

	* Tracking Area identity (TAI): used to identify tracking areas. The TAI is constructed from the PLMN identity the tracking area belongs to and the TAC (Tracking Area Code) of the Tracking Area.		* Tracking Area identity (TAI): used to identify tracking areas. The TAI is constructed from the PLMN identity the tracking area belongs to and the TAC (Tracking Area Code) of the Tracking Area.