GNodeB/Protocol Stacks 5G NR

gNodeB: is a 3GPP-compliant implementation of the 5G-NR base station.

Independent Network Functions which implement NR RAN protocols: PHY

/MAC/RLC/PDCP/SDAP/RRC.

Deploy: it can deploy either Physical or Virtual resources (e.g dedicated COTS server or shared
cloud Resources)

Functionality: Perform functions on through Control Plane /User plane Protocol Stacks.

Image 1.1

 For gNode B software are implemented in a manner that enables the protocol stack
cutting option defined as per the 3GPP .
 Stack cuts in gNodeB, options 7 (between RU and DU) and 2 (between DU and CU). Refer
Below Image 1.2
 Image 1.3

 Virtualization Component (VC) directly enables gNodeB modularization and execution

either on physical or virtual resources.
Image: Control Plane Protocol Stacks

Control plane (C-plane): If the type of data is signalling or controlling message, then it is
sent/forwarded through the control plane is further divided into two categories:
 first C-plane category: that runs between the Core Network (5GC) and the user device.
 second C-plane functionality: runs between gNB and the device and is known as RRC
(RRC = Radio Resource Control)

NAS (Non-Access Stratum Layer)

1.1 First C-plane category: NAS Layer: (Non- Access Stratum)- This layer is responsible for
authentication Security, Mobility Management, Call control Management, Session, and Identity
Management, Idle Mode Enabling (Paging).

Communication: NAS layer communicates to AMF NAS layer through N1 Interface / NAS
messages are also sent via RRC, but gNB cannot read them. NAS messages are solely between
the core and the device.

Single NAS protocol that applies on both 3GPP and non-3GPP access.

NAS protocol on N1 comprises a NAS-MM and a NAS-SM components.

UE and a core network function that need to be transported over N1 via NAS-MM protocol.

 Session Management Signalling.

 SMS.
 UE Policy.
 LCS.

NAS -NAS MM procedures that terminate at the AMF.

 Handles Registration Management and Connection Management.

 Provide a secure NAS signalling connection (integrity protection, ciphering)
 Provide access control.
NAS -NAS SM: Supports the handling of Session Management between the UE and the SMF.
NAS protocol for SM functionality supports user plane PDU Session Establishment, modification,
and release.

 SM signalling message is handled, i.e., created and processed, in the NAS-SM layer of UE
and the SMF
 Content of the SM signalling message is not interpreted by the AMF.

RRC (Radio Resource Control Protocol Layer)

1.2 Second C-plane functionality runs between gNB and the device and is known as RRC (RRC =
Radio Resource Control): It terminates at the gNB and has no direct link with the core.

 RRC is responsible for handling RAN-related C-plane procedures like:

 Broadcasting System Information (SI): It is necessary for the device to be able to
communicate with the cell.
 Transmission of paging messages to notify the device about incoming connection
requests.
 Connection management.
 Handling of device capabilities: When a device establishes a connection, the network
request device’s capabilities (e.g., if it supports Dual connectivity or massive MIMO etc.)
 Measurement configuration and reporting

1.2.1 Process: RRC messages Transmitted.

RRC messages are transmitted to the device using Signalling Radio Bearers (SRBs). (SRB is a C-

plane tunnel created between gNB and UE for control signalling, i.e., RRC or NAS messages are

sent over SRBs.)

As shown in the figure above, the messages follow the following protocol stack: PDCP, RLC,

MAC, and PHY (same as U-plane, except for the SDAP).

During the connection establishment phase, the SRBs are mapped to the CCCH

logical channel. Once the connection is established between gNB and the device, SRBs are

mapped to DCCH logical channel. In terms of PHY layer mapping, RRC messages are always

mapped over PDSCH or PUSCH (depending on DL or UL transmission).

C-plane and U-plane data follow the same protocol stack from the PDCP layer which are

multiplexed at the MAC layer and transmitted over PDSCH/PUSCH in the same TTI.
Thus, In the downlink direction, logical to physical channel mapping of RRC message is (UL is

similar with the UL channel counterparts):

CCCH/DCCH →DL-SCH → PDSCH.

Now, a device is always in some sort of state depending on its activity. These states are the RRC
states.

1.2.2 RRC States: There are there RRC states.

 RRC_IDLE: This is the sleep state where the device is not receiving any data.

 Reconnected: This state is used for data transfer between the device and gNB. All

parameters necessary for communication are known to both entities. The device is

assigned an identity, i.e., C-RNTI, for signalling purposes with the network.

 RRC_Inactive: This is the new state in NR. In this state, the RRC context is kept both at

the device and the gNB level. The device-to-core level connection is also kept.

1.2.3 RRC Configuration NR:

1.2.4 Functionality of RRC Configuration:

 Radio Bearer
 Measurement
 Scells or Cell Group
 Radio Bearer
o Establish
o Modify
o Release
 Measurement
o Setup
o Modify
o Release
 Scells or Cell Group
o Add
o Modify
o Release

1.2.5 Information Elements IN RRC Reconfiguration:

 secondaryCellGroup
 radioBearerConfig
 measConfig
 nr-SecondaryCellGroupConfig
 spCellConfig->reconfigurationWithSync

1.2.5 Timers with RRC Configuration:

  Drx-onDurationTimer: milliSeconds: ms10, ms20, ms30,
 ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600,
ms800, ms1000, ms1200, ms1600.

 Drx-InactivityTimer: milliSeconds: ms0, ms1, ms2, ms3, ms4, ms5,

ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200,
ms300, ms500, ms750, ms1280, ms1920, ms2560.

 Drx-RetransmissionTimerDL: sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24,

sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320.

 Drx-RetransmissionTimerUL: sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24,

sl33, sl40, sl64,
 sl80, sl96, sl112, sl128, sl160, sl320.

 Drx-LongCycleStartOffset: ms10 ms20 ms32 ms40 ms60 ms64 ms70 ms80

ms128 ms160 ms256 ms320 ms512 ms640 ms1024 ms1280 ms2048
ms2560 ms5120 ms10240

 Drx-ShortCycle: ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16,
ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160,
ms256, ms320, ms512, ms640

 PHR-Config: sf10, sf20, sf50, sf100, sf200, sf500, sf1000, infinity

 Phr-ProhibitTimer: sf0, sf10, sf20, sf50, sf100, sf200, sf500,
sf1000

RLC (Radio Link Protocol)

NR RLC is almost same as LTE RLC

Modes of NR RLC: TM(Transparent Mode), UM(Unacknowledge Mode) and

AM(Acknowledge mode)