5G NR PROTOCOLS
Rahul kaundal
www.itelcotech.com
AGENDA
Layer 1 - Physical Layer
Physical channels and signals
Simulation
Layer 2
Layer 2 data flow
RLC (Radio Link control) protocol
MAC (Medium Access control) protocol
POCP (Packet data convergence protocol)
SDAP (Service data adaptation protocol)
Layer 3 functional blocks
RRC (Radio resource contro!) protocol5G RAN Protocol Stackrato ra
Layer 4
Layer 1 fitactional blocks =
a, POCCH - Physical Common Control Channel ree arean
b. PDSCH - Physical Downlink Shared Channel
¢. DL Reference Signals,
d. PUCCH - itysical Uplink Control Chasinel
e, PUSCH - Physical Uplink Shared Channel
f, UL Reference Signals
ve
SS Cec
signals =arele
A aa
Downiink
5 fica eon eva)
Physical downlink control channel (PDCCH.
Physical Downlink Control Channel - conveys Downlink Control Information (DCI. It carries information such
2s scheduling information and resource grant to UE. =
The PDCCH includes one or more control channel elements
(CCE, consists of 6 resource element group) and have
different aggregation levels as shown in table.
PDCCH use Polar codes, which combine many instances (bits)
to get a useful information (noiseless bits)
CORESET (Control Resource Set) is a set of physical Roy
resources within a specific area in Downlink Resource
Grid and carry POCCH (DCI). NR POCCHs are specifically jeoraanr
designed to transmit in a configurable CORSET. unaaeoad
POCCH can also be used to for -
‘Notifying UEs of the siot format
+ Notifying UES of the PRB(s) and OFDM symbols) where
ro transmission is intended
+ Transmission of TPC commands for PUCCH and PUSCH
+ Transmission af one or more TPC commands for SRS
{transmissions by one or more UES —
+ Switching a UE’ active bandwidth part ‘Slot with CORESET i st symbot
+ Iniiating a randam-access procedure ° itelcotech
anova patitelcotech
k Shared Channel- User bit stream (Transport block or Payload) received from MAC sublayer over
transport channels are sent to the L1 PDSCH physical channels and output generated as IQ data (Quadrature
signals). Seteetemertcatarene
‘There are multiple steps performed while processing TBs ~ |
+ CRC- Cyclic redundancy check - error detection =
+ Segmentation of TBs - two TBs are used in spatial multiplexing
+ LDPC Encoder - error correction (after CRC and parity check) moe neai
+ Rate Matching - match radio frame size with TB size (number of code bits to schedule) i
+ Scrambler - use of different scrambling codes reduces interference & improve processing gain (___ sme
+ Modulation mapper - transforms biock of scrambled bits into modulation symbols
+ Layer Mapper distribute modulation symbols across different transmission layers co
RE Mapper - modulation symbols are transmitted on antenna ports and map to available REs_ +
Downlink Reference Signals - The downlink reference signals are used to estimate channel and yaaa
retrieve data in broadcast, common and shared channels. en
+ Demodulation Reference Signal (OMRS) for PDSCH, POCCH and PBCH (to demodulate them) _sstmsemne
+ Phase Tracking Reference Signal (PTRS) - phase noise compensation (occurs with DMRS) =
+ Channel State Information Reference Signal (CSI-RS) - CSI-RS received by UE is used for |
interference estimation and provide support for beam management and mobility ————
Physical uplink control channel
Conveys Uplink Control Information i —
(UCI.
=
<==
PUCCH Formats- depends upon OFDM Symbols, UE multiplexing and no. of bits
Format 0, 2
+ Reduce feedback time
Format 1,34
* Better coverage and stability
‘e itelcotechitelcotech
Physical uplink shared channel (PUSCH
Physical Uplink Shared Channel - The frequency domain IQ data (Quadrature signals) received by the fronthaul
module are sent to the Li PUSCH processing functions here and the output of the PUSCH is the user bit
stream/payload/transport block.
“septs reference
Signal resource
‘ements (IRS-RE)
Fromuser da resource
‘lemons for channel
menor
There are multiple steps performed while processing this IQ data -
sto match the radio
frames th
Tansporeblock sae
‘efile channel ending
des tht allow
trancision eros to
becerreced
Layer 2 ~ Data Flow
Layer 2 Data Flows from al four layers as depicted in the figure below. IP packets coming from layer 3 travelled as SOUS (service
ddata units) to layer 2 and are encapsulated in radio bearers for SDAP, POCP, RLC layers and within MAC layer converted into a
transport block by concatenating two RLC POUS from RBx and one RLC POU from RBy.
‘The two RLC POUS from RBx each corresponds to one IP packet (n and n+1) while the RLC POU from RBY sa segment of an IP
packet (my.
eB =| aor 7 soar Tara
mCP [rename oo & oo
ruc =] acaoo [meso oe |
‘Layer 2 data Now (Ret SGP)
43
itelcotechitelcotech
RLC Protocol ~
RLC segments the SDUs depending upon the size
requested from MAC and sends the RLC PDUs to MAC.
Transmissicn Modes -
ER ansparent Mode
* For SRBO, paging, broadcast Si
(UIE "acknowledged mode
* For DBRS.
* Acknowledged! mode - For other SRBS and ORB:
Layer 2strctre DI. (Ret GFP)
46
yer 2 funetions - MAC
MAC Protocol modules - MAC modules include RACH management, HARQ Management, DL and UL Data,
BCCH/PCCHICCCH processing, MAC Transport Block formation, etc. Major tasks are -
+ UE and Bearer Context Management: Stores the semi-static information on air interface resources for the UE (QoS info)
HARQ Management: By keeping track of HARQ feedback, timer and provide free HARQ processes information to the scheduler
RACH Manager: RACH (Preamble) resource management, CRNTI assignment, Message-2.34 resource allocation and handling.
CCH Manager: Handles the OL and UL CCCH message and corresponding HARQ.
Resource Assign: POCCH, POSCH, PUCCH and PUSCH Resource Assignment based on resource allocation from the schedule.
MAC Encoder: It creates MAC Transport block based on input from the scheduler. It interfaces with RLC to get RLC POUS.
‘Demultiplexer: Demultiplexing UL Transport block containing MAC CE and RLC PDUs
CSI Manager: Configuration of ‘Channel State information” and informing the CSI feedback from UE to the scheduler,
MAC Scheduler - NR Scheduler functional block has been further expanded into smaller functional sub-blocks to
capture the scheduler functionality as mentioned below -
+ DUUL Resource Scheduler: This corresponds to functionality of time-domain and frequency domain scheduling in DL and UL.
Resource scheduling is performed per scheduling period and fora single slot or multipie sits. t may include functions such as.
beam selection, selecting of UEs and associated bearers per scheduling period, allocation of radio resources different channels,
+ DUULLink Adaptation (LA Link Adaptation may be performed based on channel quality reported by UE or estimated at gNB,
corrected by BLER. LA would return effective MCS to be used for channel allocation to the UE.
+ ULTxPower Control: Performs Closed loop UL power control for PUSCH, SRS and PUCCH. It may estimate the UL Tx power
based on UE feedback (e..: Power Headroom Report) or measured UL channels.
+ DUULMIMO Mode Control: Determines per UE the MIMO mode, in DL and UL, respectively, to be used along with the
corresponding precoding matrix.
+ TAManager: Estimating the TA Command for UE based on feedback from Lt using PUSCH, PUCCH and SRS.
+ Performance metrics (Capacity, throughput etc) will be dependent on software implementation and underiying hardware
” itelcotechitelcotech
Layer 2 - PDCP
PDCP (Packet data convergence protocol) layer 2 protocol provides its services to both control plane (RRC) and user plane
(SDAP) upper layers. The following services are provided by PDCP to upper layers:
stransfer of user plane & control plane data a en
sheader compression
sciphering
‘integrity protection
DCP entities defined for UES in PDCP sub layer, and each entity is
carrying the data of one radio bearer. This entity is associated either
{0 the control plane or the user plane depending on which radio
bearer itis carrying data for. Each radio bearer (except for SRBO) is
associated with enty.
Each POCP entity is associated with one, two, or four RLC entities
depending on the RB characteristic (eg, uni-directional/bi
directional or splivnon-split) or RLC mode.
rote t
a 4
= cg
oe FE +
~ on itelcotech
Layer 2- SDAP.
SDAP (Service data adaptation protocol is responsible for QoS Flow handling across the 5G air interface.
itis a user plane protocol at layer 2. SDAP will map a specific QoS Flow
within a PU Session to a corresponding Data Radio Bearer (which has been
established with the appropriate level of Qos). = ee
inadition SOAP witmarktewarsmiveapaces win recorecart lamar) | | Laon
(Qo5 Flow 10}, ensuring that the packet receives the correct forwarding, < > < o cor
treatment. orem oon
For each PDU (protocol data units) Session, a single protocol entity
of SDAP will be configured. The exception to this is Oual Connectivity
‘whereby the Master Cell Group and Secondary Cell Group will each
have a separate SDAP configuration on the device.
SDAP structure- The SOAP sublayer is configured by RRC.
“The SOAP sublayer maps QoS flows to ORBS. One or more QoS flows may = —
bbe mapped onto one DRB. One QoS flow is mapped onto only one DRB at with hint
atime in UL, aT ES"
‘The SDAP entities are in the SDAP sublayer. Several SDAP entities may be G gee]
defined for a UE. There isan SDAP entity configured for each individual PDU
session. An SDAP entity receivesidelivers SDAP SDUS (service data units)
from/to upper layers and submits/receives SOAP data PDUS to/from its
peer SDAP entity via lower layers.
48itelcotech
Layer 2 ~ SDAP - QoS
wa) - ‘iowston & ‘Standardized 50 to QoS Characteristics Mapping (GBR — Pant 1)
56.005 lente Retention Proty
1 GBR | 20. ime | 10% «NA 20008 | Comer oe
‘Non ~ GBR G08 Flows — Contling bandwith 5 ee ee A 2000ms ive Seong)
+ 6 3 GBR 90 S0ms 10° ‘NA 2000ns eal Time Gaming. V2X.
Reflective QoS: —
veseminnuon | [i eer
— Ll) S 20008 Nis an)
ce) GbR | 20 toons | 10% NA | 200mm | maton crac,
67 «GBR 15 100ms 10” NA 2000m= Mision Citic Video
‘GBR G95 Fows ~ Contain bandwath
Bitrate QUUL} rato (ULL)
9
Radio Protocol architecture
With the overall network architecture in mind, the RAN protocol architecture for the user and control planes is
illustrated below ( AMF is, not a part of the RAN but is included in the figure for completeness).
In user plarie, majority of protocols are same in LTE and SG NF
but one of few differences is QoS handling in NR for which cow
SDAP is introduced to define QoS at more granular level (IP
Packets level).
Uplink protocol stack is similar.to downlink except transport
format selection and control of logical channel multiplexing
‘Uso an contr plare protec stack Re IPF) ‘Use plane proce aretecture-DL. (Ret 3GPP)
2 itelcotechitelcotech
Layer 3-RRC
RRC - Radio resource control protocol exists at IP level (layer 3) between UE and gNB.
‘The major functions of the RRC protacol include corneetion establishment and release functions, broadces: of system
information, radio bearer establishment, reccrifiguration and release. FiiC connection mobility pro