4G/5G BASIC LEVEL

Network
Architecture and
Mapping
Future Potential Use Cases

• Extreme Mobile Broadband that delivers Multi Gigabytes of bandwidth on demand

• Massive machine-type communication that connects billions of sensors and machines
• Critical machine-type communication that allows for the immediate, synchronous eye-hand feedback that enables
remote control over robots

3
5G key technology components

4
5G Challenges
What are 5G Challenges ?
✓ Frequency Band : C-Band Spectrum availability and clean from interference
✓ 5G Devices : Limited and pricy 5G devices
✓ Transmission Capacity : Fiber GPON or E-Band access upgraded to 10G
✓ Tower Load : Massive MIMO 64T64R with heavy load
✓ Clock Synchronization : GPS available or not in legacy network
✓ Limited Use Cases : Focus on eMBB initial deployment, limited use cases. what else ?

Motorola moto z4 LG V50 ThinQ 5G Samsung Galaxy S10 5G Galaxy Note10+ 5G Samsung Galaxy Fold ZTE Axon 10 Pro Huawei Mate X Huawei Mate 20 X 5G

5
Xiaomi Mi MIX 3 5G OPPO Reno 5G OnePlus 7 Pro 5G Energizer Power Max P8100S Alcatel 7 5G
Mobile Communication Evolution

6
5G Starts from 3GPP Release 15

= NR (New Radio)
5G Phase 1
(Release 15)
5G Phase 2
(Release 16)

The 5G air interface, also known as NR (New Radio), is 3GPP’s solution to meet the ITU-R (International Telecommunication Union –
Radiocommunication), and in particular the 5G Working Party, defined minimum requirements for a 5G or IMT (International Mobile
Telecommunications) 2020 network.
3GPP have defined a phased approach to 5G, referred to as 5G Phase 1 and 5G Phase 2. These are defined in 3GPP Release 15 and Release
16 respectively. The early focus for 5G Phase 1 is eMBB (Enhanced Mobile Broadband) data services and some URLLC (Ultra Reliable Low
Latency Communications) support. 5G Phase 2 is planning to complete the IMT-2020 requirements with various enhancements, as well as
support for MIoT (Massive Internet of Things).

5G New Radio
Rel-15 Rel-16

Rel-12 Rel-13 Rel-14 Rel-15 Rel-16

Key Performance Comparison Between 4G and 5G
LTE Network Elements
Main references to architecture in 3GPP specs.: TS23.401,TS23.402,TS36.300
Evolved UTRAN (E-UTRAN) Evolved Packet Core (EPC)

HSS
eNB Mobility
Management
Entity Policy & Charging Rule
S6a Function

MME S10
X2 S7 Rx+
PCRF
S11
S1-U S5/S8 SGi
PDN
LTE-Uu Serving PDN
Evolved Node B
Gateway Gateway
LTE-UE (eNB)
SAE
Gateway

9
LTE Element Function
❑ E-UTRAN / E-NODE B
➢ Function for radio resource management radio bearer control, radio admission control,
connection mobility control, dynamic allocation of resource to UEs in both uplink and downlink.
➢ Selection of an MME at UE attachment.
➢ Routing of user plane data towards serving gateway.
➢ Measurement & measurement reporting configuration for mobility & scheduling.

❑ MME (Mobility Management Entity) ❑ P-GW (PDN Gateway)

➢ NAS signaling security
➢ AS security control
➢ Idle state mobility handling
➢ EPS (evolved packet system) bearer control
➢ Support paging, Handover, authentication
➢ Per-user based packet filtering: UE IP address
allocation, UL and DL service level charging.
❑ S-GW (Serving Gateway)
➢ Packet routing and forwarding

10
LTE Radio Interface & the X2 Interface
LTE-Uu interface
..
(E)-RRC User PDUs User PDUs • Air interface of LTE
PDCP
• Based on OFDMA in DL & SC-FDMA in UL
RLC TS 36.300
• FDD & TDD duplex methods
MAC
LTE-L1 (FDD/TDD-OFDMA/SC-FDMA) eNB • Scalable bandwidth: 1.4MHz - 20 MHz

LTE-Uu
X2 interface
X2-UP
(User Plane)
• Inter eNB interface
X2-CP
(Control Plane) • X2AP: special signaling protocol (Application Part)
User PDUs • Functionalities:
TS 36.423 X2-AP GTP-U
X2 – In inter- eNB HO to facilitate Handover and
SCTP UDP
TS 36.422
TS 36.424 provide data forwarding.
IP IP
– In RRM to provide e.g. load information to
TS 36.421 L1/L2 L1/L2 TS 36.421 neighbouring eNBs to facilitate interference
management.
TS 36.420 – Logical interface: doesn’t need direct site-to-site
connection, i.e. can be routed via CN as well
eNB
11
S1-MME & S1-U Interfaces
S1 interface is divided into two parts: S1-MME
(Control Plane)
S1-MME interface NAS Protocols
MME
• Control Plane interface between eNB & MME TS 36.413 S1-AP
SCTP
• S1AP:S1 Application Protocol TS 36.412
IP
• MME & UE will exchange NAS signaling via eNB through L1/L2 TS 36.411
this interface ( i.e. authentication, tracking area updates) S1-U
S1-U interface (User Plane)
User PDUs
• User plane interface between eNB & Serving Gateway. eNB GTP-U Serving
TS 36.414 Gateway
• Pure user data interface (U=User plane) UDP
IP
TS 36.411 L1/L2

TS 36.410

12
5G network architecture vocabulary

13
5G Network architecture

14
5G Network architecture options in 3GPP Release 15
5G System can be deployed as a standalone solution without LTE. This approach is called Option 2 in 3GPP. 5G
can also use non-standalone solution with dual connectivity to LTE. That approach is called Option 3. The very
first 5G networks must use Option 3 because it is available in 3GPP 6 months before Option 2.

Dual connectivity has also other benefits: it allows to combine LTE and 5G data rates together and it allows to
reuse existing Evolved Packet Core (EPC). Option 2 with 5G core network enables new end-to-end services
including low latency. Option 2 allows lower latency and faster setup time than dual connectivity solution where
LTE protocols are used. 3GPP Standards will bring also the option to connect LTE eNodeB to 5G core network
with Options 7 and 4.

15
Option 3 Varian

Option 3 is a dual connectivity deployment with E-UTRA as the anchor Radio Access Technology (RAT) and NR as
the secondary RAT in a non-standalone configuration based on the existing EPC.
Both 5G base stations (gNodeB) and LTE base stations (eNodeB) are connected to the EPC. The control plane
goes via LTE. There are 3 possible variants as displayed on the slide. The option 3X seems favored by most
operators for enhanced mobile broadband.
16
Data flow in options 3, 3A and 3X
In Option 3a: there is user plane
traffic split at core network: EPC
establishes separate bearers to
LTE and 5G
In Option 3x, the gNodeB is the
data split anchor : The user plane
goes via both eNodeB and gNodeB
with bearer split at gNodeB.
In Option 3, the eNodeB is the data split anchor:
there is a Master Node split: EPC establishes the
bearer to Master LTE eNodeB, then Master LTE
ENodeB splits the bearer for forwarding packets
to LTE radio and/or 5G radio. 17
Terminology and Option
DC (Dual Connectivity)
– A UE in RRC_CONNECTED is configured with Dual Connectivity when
configured with a Master and a Secondary Cell Group
› PCell (Primary Cell)
– The cell, operating on the primary frequency, in which the UE either performs
the initial connection establishment procedure or initiates the connection re-
establishment procedure, or the cell indicated as the primary cell in the
handover procedure
› SCell (Secondary Cell)
– A cell, operating on a secondary frequency, which may be configured once
an RRC connection is established and which may be used to provide
additional radio resources
› MCG (Master Cell Group)
– For a UE not configured with DC, the MCG comprises all serving cells. For a
UE configured with DC, the MCG concerns a subset of the serving cells
comprising of the PCell and zero or more secondary cells
› SCG (Secondary Cell Group)
– For a UE configured with DC, the subset of serving cells not part of the
MCG, i.e. comprising of the PSCell and zero or more other secondary cells
› PSCell (Primary Secondary Cell)
– The SCG cell in which the UE is instructed to perform random access when
performing the SCG change procedure
› SpCell (Special Cell)
– For Dual Connectivity operation the

18
Parameter Setting
Parameter Name Sample Value Nokia Huawei Ericsson

Data Split Policy Selection SCG_SPLIT_BEARER - CellQciPara.NsaDcDefaultBearerMod -

Downlink Data Split Policy in Option 3x Dynamically Transferred - gNBPdcpParamGroup.DlDataPdcpSplitMode -

19
Sample LTE + NR Throughput

PDCP and Application

throughput only visible
NR Throughput in NR which is
aggregated from LTE +
NR lower layer (RLC)

LTE Throughput

20
Stand-Alone Versus Non-Stand Alone

21
 Freq Band &
Multiple Access
FDD & TDD Duplex

23
NR-ARFCN Calculation

List NR Cell
------------ http://niviuk.free.fr/nr_band.php
NR Cell ID = 1
Cell Name = NAA597A1
Cell ID = 1
Frequency Band = n78
Downlink NARFCN = 636666
Duplex Mode = TDD
User Label = Sector-1
Tracking Area ID = 4161
Cell Activate State = Activated
Cell Administration State = Unblock
(Number of results = 1)

24
LTE Different Operating Bands (1/3)
Operating bands defined for FDD in 3GPP
E-UTRA Band Uplink Downlink Duplex Mode
1 1920 MHz – 1980 MHz 2110 MHz – 2170 MHz FDD
2 1850 MHz – 1910 MHz 1930 MHz – 1990 MHz FDD
3 1710 MHz – 1785 MHz 1805 MHz – 1880 MHz FDD
4 1710 MHz – 1755 MHz 2110 MHz – 2155 MHz FDD
5 824 MHz – 849 MHz 869 MHz – 894 MHz FDD
6 830 MHz – 840 MHz 875 MHz – 885 MHz FDD
7 2500 MHz – 2570 MHz 2620 MHz – 2690 MHz FDD
8 880 MHz – 915 MHz 925 MHz – 960 MHz FDD
9 1749.9 MHz – 1784.9 MHz 1844.9 MHz – 1879.9 MHz FDD
10 1710 MHz – 1770 MHz 2110 MHz – 2170 MHz FDD
11 1427.9 MHz – 1452.9 MHz 1475.9 MHz – 1500.9 MHz FDD
12 698 MHz – 716 MHz 728 MHz – 746 MHz FDD
13 777 MHz – 787 MHz 746 MHz – 756 MHz FDD
14 788 MHz – 798 MHz 758 MHz – 768 MHz FDD
17 704 MHz – 716 MHz 734 MHz – 746 MHz FDD

25
LTE Different Operating Bands (2/3)
E-UTRA Band Uplink Downlink Duplex Mode

17 704 MHz – 716 MHz 734 MHz – 746 MHz FDD

18 815 MHz – 830 MHz 860 MHz – 875 MHz FDD

19 830 MHz – 845 MHz 875 MHz – 890 MHz FDD

20 832 MHz – 862 MHz 791 MHz – 821 MHz FDD

21 1447.9 MHz –1462.9 MHz 1495.9 MHz – 1510.9 MHz FDD

22 3410 MHz – 3500 MHz 3510 MHz – 3600 MHz FDD

Bands 18 to 21 are added in 3GPP release 9 and band 22 is added in 3GPP release 10.

26
LTE Different Operating Bands (3/3)
Operating bands defined for TDD in 3GPP
E-UTRA Band Uplink Downlink Duplex Mode

33 1900 MHz – 1920 MHz 1900 MHz – 1920 MHz TDD

34 2010 MHz – 2025 MHz 2010 MHz – 2025 MHz TDD
35 1850 MHz – 1910 MHz 1850 MHz – 1910 MHz TDD
36 1930 MHz – 1990 MHz 1930 MHz – 1990 MHz TDD
37 1910 MHz – 1930 MHz 1910 MHz – 1930 MHz TDD
38 2570 MHz – 2620 MHz 2570 MHz – 2620 MHz TDD
39 1880 MHz – 1920 MHz 1880 MHz – 1920 MHz TDD
40 2300 MHz – 2400 MHz 2300 MHz – 2400 MHz TDD
41 2545 MHz – 2575 MHz 2545 MHz – 2575 MHz TDD
42 3400 MHz – 3600 MHz 3400 MHz – 3600 MHz TDD
43 3600 MHz – 3800 MHz 3600 MHz – 3800 MHz TDD
44 703 MHz – 803 MHz 703 MHz – 803 MHz TDD

➢ 2.3/2.5 GHz: Preferred bands for LTE-TDD. Typical bandwidth > 20 MHz
➢ 1.9/2.0 GHz: Some bands which are applicable to LTE-TDD are mainly used in Europe. Typical bandwidth: 5 MHz and 10 MHz
➢ Bands 42 and 43 are added in 3GPP release 10, which are mainly used in England and Ireland. Bands 42 to 44 have a bandwidth of 100 MHz,
which can be used in eRelay.

27
5G Definition of frequency ranges

28
3GPP-defined 5G Frequency Ranges and Bands

29
Main 5G spectrum options in different markets globally

30
Parameter Mapping

Parameter Name Sample Nokia Huawei Ericsson

Frequency Band n78 NRCELL.freqBandIndicatorNR NRDUCell.FrequencyBand NRSectorCarrier.frequencyDL/NRCellDU.bandListManual

Downlink Bandwidth 100Mhz NRCELL.chBw NRDUCell.DlBandwidth NRSectorCarrier.bSChannelBwDL

Downlink NARFCN 643334 NRCELL.nrarfcn NRDUCell.DlNarfcn NRSectorCarrier.arfcnDL

31
Recourse Block,
BWP and
Numerology
OFDM Frequency and Time Domains

33
OFDM Frequency and Time Domains

34
Cyclic Prefix

A CP (Cyclic Prefix) is utilized in

most OFDM systems to combat
multipath delays. It effectively
provides a guard period for each
OFDM symbol. Notice that the
Cyclic Prefix is effectively a copy
taken from the back of the
original symbol which is then
placed in front of the symbol to
make the OFDM symbol (Ts).

35
LTE Cyclic Prefix (CP)
CP Configuration

36
Multiple Access Technique

37
OFDMA & SC-FDMA
Sample High PAPR (Peak
to Average Power Ratio)

38
Different Duplex Modes

• FDD: Distinguishes uplink and downlink using different

frequencies.
• TDD: Distinguishes uplink and downlink using different
timeslots.

✓ Complex implementation, which requires GPS

synchronization or phase synchronization
✓ Need to control interference between the uplink and
downlink
✓ Long delay
LTE Radio Interface

40
FDD Radio Frame Structure

Subcarrier Spacing ∆f = 15Khz

✓ The LTE-FDD frame format defined in 3GPP is Type 1. Each 10-ms radio frame is
divided into 10 subframes.
✓ Each subframe contains two timeslots and each timeslot is 0.5 ms.
TDD Radio Frame Structure

D = Downlink Subframe
U = Uplink Subframe
S = Special Subframe

✓ The LTE-TDD frame format defined in 3GPP is Type 2.

Each 10 ms radio frame consists of two half-frames of
5 ms each. Each half-frame consists of eight slots of
length 0.5 ms and a special subframe.
✓ The special subframe contains three timeslots: DwPTS,
GP, and UpPTS. The total length of the three timeslots
is 1 ms. The lengths of DwPTS and UpPTS are
configurable.
TDD Special Subframe Structure
Special Subframe Configuration

✓The DwPTS can be considered as a special downlink subframe,

which contains 12 symbols at most and 3 symbols at least. The
DwPTS transmits downlink data and signaling messages.
✓The DwPTS and UpPTS may carry information. For example the
DwPTS can include scheduling information and the UpPTS can
be configured to facilitate random access bursts.
✓The length of the UpPTS is two symbols or one symbol.
➢When the UpPTS contains two symbols, it is used for short
RACH or sounding RS.
➢When the UpPTS contains one symbol, it is used only for
sounding RS.
TDD Special Subframe—GP
Special
Subframe DwPTS GP UpPTS GP (km)
Configuration
0 3 10 1 214.3
1 9 4 1 85.7
2 10 3 1 64.3
3 11 2 1 42.9
4 12 1 1 21.4
5 3 9 2 192.9
6 9 3 2 64.3
7 10 2 2 42.9
8 11 1 2 21.4

✓When signals from a remote eNodeB are transmitted to long distance NodeB, due to the transmission delay the downlink
pilot timeslot (DwPTS) for the eNodeB with interference overlaps the uplink pilot timeslot (UpPTS) for the eNodeB that is
interfered with.
✓GP is a guard period in a special subframe, which ensures downlink-to-uplink switching. The DwPTS must be reliably received
during cell searching to prevent interference to the UL. The UpPTS must be transmitted in advance during random access to
prevent interference to the DL. The GP in a special subframe specifies the minimum distance beyond which DL signals do not
interfered with UL signals.

44
5G New Radio (NR) offers a flexible air interface

45
 Overview-NR Air Interface Resources
Numerology (system parameters): refers to subcarrier spacing (SCS) in an NR system and related
parameters, such as the symbol length and CP length.

Time-domain CP
Basic scheduling unit
resources
Symbol length Slot Subframe Frame

1 slot = 14 symbols 1 subframe = 1 ms 1 frame = 10 ms

The SCS determines
Numerology the symbol length
and slot length.
1 frame = 10 subframes
One or more BWPs can be
1 RB = 12 subcarriers 1 RBG = 2 to 16 RBs 1 BWP = Multiple RBs/RBGs configured in one carrier.

SCS RB RBG BWP Carrier

Frequency-domain Data channel/control channel scheduling unit

resources

REG CCE
Existed in LTE
Unchanged in NR
1 REG = 1 PRB 1 CCE = 6 REGs
Existed in LTE
Enhanced in NR
Space-domain resources Codeword Layer Antenna port
Added in NR

46
NR Multiple access
NR Multiple access

In the 5G, the multiple access scheme for the NR physical layer is a combination of : OFDMA (orthogonal frequency-
division multiple access), TDMA (Time-division multiple access), and SDMA (Space Division Multiple Access).
Remember: The multiple access is about separation of radio resources for users in the cell.
• OFDMA is based on Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) ; the
transmission to/from different UEs uses mutually orthogonal frequency assignments. With granularity in
frequency domain assignment equal to one resource block consisting of 12 subcarriers as illustrated by this grid
given on the slide.
• TDMA is based on the transmission to/from different UEs with separation in time. The granularity in the time
domain is equal one slot consisting of 14 OFDM symbols, or 2, 4, 7 OFDM symbols within one mini-slot. The
physical length of one slot ranges from 0.125ms to 1ms depending on the sub-carrier spacing.
• The SDMA , also known as multi-user MIMO, is referring to the possibility to transmit to/from multiple users
using the same time-frequency resource as part of the advanced-antenna capabilities.
OFDM-based waveforms
OFDM-based waveforms

Briefly, OFDM is block transmission of N symbols in parallel on N orthogonal sinusoidal time-limited waveforms. Each
sinusoidal frequency is called a subcarrier (or tone) since one modulation symbol is mapped to one waveform per
OFDM symbol time.
Each subcarrier is 15 kilo Hertz in bandwidth as in LTE eUTRAN but in NR Multiple sub-carrier spacings are supported
including 15kHz, 30kHz, 60kHz and 120kHz for data. The inter-subcarrier spacing is equally distributed over the
channel. At the center frequency of each subcarrier, all the other subcarriers go to zero amplitude. One can think of
this as all talking at once, but when I want to talk, all the other subcarriers go to zero when I filter it. With the right
filter, I can get the information clearly without interference.

In 3GPP Release 15, CP-OFDM is applied for both downlink and uplink and DFT-spread OFDM can also be configured
for uplink especially for low power device (e.g. IoT)
NR Concepts of Frequency-Domain Resources

⚫ Resource Grid (RG) Resource Grid

– Resource group at the physical layer, defined for the uplink and downlink (for a given One subframe
numerology)
– Time domain: 1 subframe, frequency domain: available RB resources within the transmission
bandwidth
,
subframe
⚫ Resource Element (RE) Nsymb OFDM symbols
max, RB
– Smallest unit of physical-layer resources
k = NRB,
x Nsc −1
– Time domain: 1 OFDM symbol, frequency domain: 1 subcarrier
⚫ Resource Block (RB)
– Basic frequency-domain scheduling unit involved in data channel resource allocation (type 1
resource allocation)

N scRB subcarriers

N scRB subcarriers
– Frequency domain: 12 contiguous subcarriers
⚫ Resource Block Group (RBG)
– Basic scheduling unit for data channel resource allocation (type 0 resource allocation) and
reduced control channel overheads Resource element

N RB

– Frequency domain: {2, 4, 8, 16} RBs (k , l )

Resource block
⚫ Resource Element Group (REG)
– Basic unit involved in control channel resource allocation
– Time domain: 1 OFDM symbol, frequency domain: 12 subcarriers (1 PRB)
⚫ Control Channel Element (CCE)
– Basic scheduling unit involved in control channel resource allocation
– Frequency domain: 1 CCE = 6 REGs = 6 PRBs
– CCE aggregation level: 1, 2, 4, 8, 16 k =0
l =0 l = 14  2  − 1
51
NR SCS

• Numerologies (adjustable SCS) supported by 3GPP Release 15 (TS
38.211) with SCS identified by the parameter µ.
Parameter
• 3GPP TS 38.104 (RAN4) defines SCS for different frequency bands.
 SCS for bands below 1 GHz: 15 kHz, 30 kHz
 SCS for bands between 1 GHz and 6 GHz: 15 kHz, 30 kHz, 60 kHz
SCS for band 24 GHz to 52.6 GHz: 60 kHz, 120 kHz


SCS CP 240 kHz for data is not considered in Release 15.

µ 

0 15 kHz Normal
1 30 kHz Normal
2 60 kHz Normal, extended
3 120 kHz Normal
4 240 kHz Normal

• Application scenarios:

Scalable Numerology
Flexibility Example
Case 1 Different spectrum Sub-6 GHz, mmWave
Case 2 Multiple services eMBB, URLL, mMTC
Case 3 Multiple scenarios Low/high Speed

52
Transmission Bandwidth and Spectrum Utilization
⚫ Transmission bandwidth: depends on the channel bandwidth and data channel SCS.
– Maximum transmission bandwidth on the gNodeB side: See Table 5.3.2-1 and 5.3.2-2 in 3GPP TS 38.104.
5 10 15 30 70 90
20 MHz 25 MHz 40 MHz 50 MHz 60 MHz 80 MHz 100 MHz
SCS (kHz) MHz MHz MHz MHz MHz MHz
NRB and Spectrum Utilization (FR1: 400 MHz to 6000 MHz)
25 52 79 [160] 106 133 216 270 N/A N/A N/A N/A N/A
15
90% 93.6% 94.8% 95.4% 95.8% 97.2% 97.2% \ \ \ \ \
11 24 38 [78] 51 65 106 133 162 [189] 217 [245] 273
30
79.2% 86.4% 91.2% 91.8% 93.6% 95.4% 95.8% 97.2% 97.7% 98.3%
N/A 11 18 [38] 24 31 51 65 79 [93] 107 [121] 135
60
79.2% 86.4% 86.4% 893% 91.8% 93.6% 94.8% 93.6% 97.2%

Channel Bandwidth [MHz]

Transmission Bandwidth Configuration NRB [RB]

50 MHz 100 MHz 200 MHz 400 MHz

Channel Edge
Channel Edge
SCS (kHz) Transmission
NRB and Spectrum Utilization (FR2: 24 GHz to 52 GHz) Bandwidth [RB]
66 132 264 N/A

Resource Block
60
95% 95% 95% \
32 66 132 264
120
92.2% 95% 95% 95% f
Active Resource
Blocks

Guardband, can be asymmetric

– Maximum transmission bandwidth on the UE side: See 3GPP TS 38.101-1 and TS 38.101-2.
– The number of RBs in the 30 MHz bandwidth is to be determined. The 70 MHz and 90 MHz bandwidths are not supported. Other
values are the same as those on the gNodeB side.
53
NR Frame Structure Architecture

54
NR Frame Structure Architecture

55
Mapping Between SCS and Symbol Length

⚫ SCS vs symbol length/ CP length/slot length

SCS = 15 kHz
T_slot = 1 ms (14 symbols)
– Length of OFDM symbols in data: T_data = 1/SCS
– CP length: T_cp = 144/2048* T_data CP data …
– Symbol length (data+CP): T_symbol = T_data +T_cp
T_symbol
– Slot length: T_slot = 1 / 2^(µ)
T_slot = 0.5 ms (14 symbols)

SCS = 30 kHz
Parameter/Numerology (µ) 0 1 2 3 4
SCS (kHz):
15 30 60 120 240 …
SCS = 15 x 2^(µ)

OFDM Symbol Duration (us): T_symbol

66.67 33.33 16.67 8.33 4.17
T_data = 1/SCS
T_slot = 0.125 ms (14 symbols)
CP Duration (µs):
4.69 2.34 1.17 0.59 0.29
T_cp = 144/2048*T_data

SCS = 60 kHz
OFDM Symbol Including CP (µs):
T_symbol = T_data + T_cp
71.35 35.68 17.84 8.92 4.46 …
Slot Length (ms):
1 0.5 0.25 0.125 0.0625
T_slot = 1/2^(µ)
T_symbol
56
NR Cyclic Prefix (CP)
⚫ CP function:
– To eliminate inter-channel interference (ICI) caused by multipath ⚫ CP length for different SCS values:
propagation.
Symbol Period T(s) 512  2 −  extended cyclic prefix
Attitude  
Symbol N Symbol N+1 N CP ,l = 144  2 −  + 16 normal cyclic prefix, l = 0 or l = 7  2 
Cyclic Prefix
Bit Period T(b) 144  2 −  normal cyclic prefix, l  0 and l  7  2 


One OFDM symbol

T(g)
Tcp = Ncp  Tc
Symbol Period T(s)
time

⚫ NR CP design principle: Parameter SCS CP

– Same overhead as that in LTE, ensuring aligned symbols btw different µ (kHz) (µs)
SCS values and the reference numerology (15 kHz). 0 15 TCP: 5.2 µs for l = 0 or 7; 4.69 µs for others

1 30 TCP: 2.86 µs for l = 0 or 14; 2.34 µs for others

TCP: 1.69 µs for l = 0 or 28; 1.17 µs for others

2 60
Extended TCP: 4.17 µs

3 120 TCP: 1.11 µs for l = 0 or 56; 0.59 µs for others

4 240 TCP: 0.81 µs for l = 0 or 112; 0.29 µs for others

57
NR Cyclic Prefix (CP) for SCS 15Khz

58
NR Cyclic Prefix (CP) for SCS 60Khz

59
Slot and Mini-Slot (there is no formal term yet from 3GPP spec)

Each subframe consists of an OFDM sub-carrier spacing dependent number of slots. Each slot consists of 14
OFDM symbols. The Slot is transmitted within a transmission time interval (TTI). Different numerologies lead to
different slot lengths, ranging from 1 msat 15 kHz sub-carrier spacing to 0.125 msat 120 kHz sub-carrier spacing,
enabling shorter TTIs. The slot is the basic transmission unit at which most physical channels and signals repeat;
however, slots can be complemented by mini-slot-based transmissions (referred to as Type B scheduling in NR) to
provide shorter and more agile transmission units than slots. 60
Slot and Mini-Slot

A mini-slot can start at any OFDM symbol and can have a variable length; mini-slot lengths of 2, 4, or 7 symbols
have been defined in the standard so far. This provides fast transmission opportunities, for example, URLLC
traffic that is not restricted by slot boundaries. Thus, mini-slots provide a viable solution to low-latency
transmissions irrespective of sub-carrier spacing. In the example of resource allocation shown on the slide, you
can see a Mini-slot of 4 OFDM symbols allocated to URLLC User Equipment : one symbol in red to carry the
PDCCH and 3 symbols (orange) for data traffic transmission.
61
Bandwidth part definition

62
Bandwidth part definition

63
Bandwidth part definition
A first question that might pop up in your mind from the start: What is a Bandwidth Part ? Well, the answer is given
on this slide. A subset of the total Carrier bandwidth of a cell is referred to as a Bandwidth Part (BWP); It is a subset
of contiguous common resource blocks for a given numerology.

Remember: a Network carrier comprises of common resource blocks (CRB) and Bandwidth Part comprises of
physical resource blocks (PRB). Bandwidth Part is defined by a starting position and a number of resource blocks.
The bandwidth part shown on this Figure contains m PRB numbered from 0 up to m-1.

Within one component carrier, bandwidth part is supported on downlink and uplink. The bandwidth of the
component carrier can be divided into several bandwidth parts. From network perspective, different bandwidth
parts can be associated with different numerologies (subcarrier spacing, cyclic prefix).

From UE’s point of view, Bandwidth parts operation in NR replaces component carrier (CC) used in LTE. Not all NR
devices need to support the full carrier bandwidth (400 MHz bandwidth as shown in this example), which has
implications on the design of, for example, control channels. UEs with smaller bandwidth support capability (20
MHz or 100 MHz for instance) can work within a bandwidth part with an associated numerology. By this means UEs
with different bandwidth support capability can work on large bandwidth component carrier.

64
Motivation

Why NR introduced Bandwidth parts ?

Well, the answer is simple: The main reason for introduction of Bandwidth part concept is optimization
bandwidth that UE needs to monitor. It is used to optimize UE operations in frequency domain. NR allows for
device-side receiver-bandwidth adaptation as a means to reduce the device energy consumption. Hence, NR
defines so-called bandwidth parts that indicate the bandwidth over which a device is currently assumed to
receive transmissions of a certain numerology.
65
BWP Use Cases

66
BWP Use Cases

There are mainly four uses cases of Bandwidth part operation. They are summarized in this Figure:
1. Support of UEs with capability smaller than network carrier : single dedicated Bandwidth part configured on a
serving cell
2. Load balancing on a network carrier : multiple dedicated Bandwidth parts configured on a serving cell, of the
same size and multiplexed in the frequency domain.
3. For power saving : multiple dedicated Bandwidth parts are configured on a serving cell, one wide and one
narrow (properly nested)
4. RRC configuration change : multiple dedicated Bandwidth parts configured on a serving cell, could be of the
same size, each differently configured (e.g. numerology, time-domain resource allocation)

67
BWP Use Cases
How BWP location and bandwidth is specified in RRC ?

The location (starting position and the bandwidth of a BWP is specified in RRC parameter called locationAndBandwidth and this parameter is specified as RIV that can be
calculated according to the following specification.

< 38.213-12 Bandwidth part operation > states as follows :

a first PRB and a number of contiguous PRBs by higher layer parameter locationAndBandwidth that is interpreted as RIV according to TS 38.214, setting , and the
first PRB is a PRB offset relative to the PRB indicated by higher layer parameters offsetToCarrier and subcarrierSpacing

Combining the two specification mentioned above, would

come up with some examples as shown below. All these
examples are based on the assumption that RB_start = 0,
BWP takes up the maximum RB for the specified channel
bandwidth and subcarrierspacing = 30 Khz, FR1

68
BWP Use Cases (DT Result)

Initial BWP
RB number = 48
RB Start = 59

=275 * (48-1) + 59 = 12984

First Active BWP

RB number = 162
RB Start = 0

=275 * (275-162+1) + (275-1-0) = 31624

http://www.sharetechnote.com/html/5G/5G_CarrrierBandwidthPart.html#How_BWP_are_defined 69
BWP Parameter

Parameter Name Sample Value Nokia Huawei Ericsson

BWP Power Saving Switch BWP Power Saving Switch:Off - NRDUCellUePwrSaving. BwpPwrSavingSw -

BWP2_SWITCH: When this option is selected, certain UEs work on the BWP2. In this case, certain RB resources cannot be used because the
UEs cannot be flexibly distributed in the cell, wasting radio resources. To maintain the optimal throughput on the network side, it is
recommended that this option be deselected. When this option is deselected, UEs in the cell cannot enter the BWP2 mode and cannot save
power using BWP.

70
DL-UL Configuration

There are two types of self-contained slots:

• DL-dominant and UL-dominant.DL-dominant slotUplink control

signals or sounding reference signals (SRSs) can still be
transmitted, which shortens the downlink feedback delay.
• UL-dominant slotDownlink control signals can still be
transmitted, which shortens the uplink scheduling delay
DL-UL Configuration

Note:

• GP: indicates the number of GP symbols between uplink and downlink data transmission.

• 4:1 (DDDSU)
• It indicates 3 downlink timeslots, 1 self-contained slot, and 1 uplink timeslot. D, S, and U are
short for downlink timeslot, self-contained slot, and uplink timeslot, respectively. For details on
the self-contained slot, see 6 Self-contained Frame Structure.

• 8:2 (DDDDDDDSUU)
• It indicates 7 downlink timeslots, 1 self-contained slot, and 2 uplink timeslots.

• x or y: (indicating the configuration period)

• Its value range is as follows: {0.5, 0.625, 1, 1.25, 2, 2.5, 5, 10} ms

• The period of 0.625 ms is used only when the subcarrier spacing is 120 kHz. The periods of 1.25
ms and 2.5 ms are used when the subcarrier spacing is higher than 60 kHz and 30 kHz,
respectively.

• x1 or x3 (indicating the number of downlink timeslots)

• Its value range is as follows: {0, 1, ..., number of timeslots within a configuration period}

• y1 or y3 (indicating the number of uplink timeslots)

• Its value range is as follows: {0, 1, ..., number of timeslots within a configuration period}

• x2 or x4 (indicating the number of downlink symbols following downlink timeslots)

• Its value range is as follows: {0, 1, ..., 13}.

• y2 or y4 (indicating the number of uplink symbols before uplink timeslots)

• Its value range is as follows: {0, 1, ..., 13}.
DL-UL Configuration
Example of the Slot Configuration 4_1_DDDSU
If NRDUCell.SlotAssignment is set
to 4_1_DDDSU and NRDUCell.SlotStructure is set to SS2, the
values of parameters x, x1, x2, y2, and y1 for SS2 timeslot format
are 2.5, 3, 10, 2, and 1, respectively, as shown in Figure 7-1.
Example of the Slot Configuration 8_2_DDDDDDDSUU
If NRDUCell.SlotAssignment is set
to 8_2_DDDDDDDSUU and NRDUCell.SlotStructure is set
to SS56, a 5 ms period includes 10 timeslots (the corresponding
subcarrier spacing is 30 kHz). Figure 7-2 shows the 10
timeslots, including 7 downlink timeslots, 1 self-contained slot,
and 2 uplink timeslots.
DL-UL Configuration
Example of the Slot Configuration 4_1_DDDSU
If NRDUCell.SlotAssignment is set
to 4_1_DDDSU and NRDUCell.SlotStructure is set to SS2, the
values of parameters x, x1, x2, y2, and y1 for SS2 timeslot format
are 2.5, 3, 10, 2, and 1, respectively, as shown in Figure 7-1.
Example of the Slot Configuration 8_2_DDDDDDDSUU
If NRDUCell.SlotAssignment is set
to 8_2_DDDDDDDSUU and NRDUCell.SlotStructure is set
to SS56, a 5 ms period includes 10 timeslots (the corresponding
subcarrier spacing is 30 kHz). Figure 7-2 shows the 10
timeslots, including 7 downlink timeslots, 1 self-contained slot,
and 2 uplink timeslots.
Coexistence with TDD

• When NRDUCell.SlotAssignment is set to 8_2_DDDDDDDSUU, the slot configuration can be aligned with
LTE TDD (with a timeslot structure of DSUDD) to avoid adjacent-frequency interference or interference caused
by coexistence.

• To ensure network synchronization, you can reconfigure these

parameters: NRDUCell.SlotAssignment, NRDUCell.SlotStructure, and GNODEBPARAM.FrameOffset on
the NR side; Cell.SubframeAssignment, Cell.SpecialSubframePatterns,
and ENodeBFrameOffset.TddFrameOffset on the LTE side.

• The current version allows the slot assignment of 8:2 (DDDDDDDSUU) and slot structure SS54 supported in
the NR network to map to the uplink-downlink subframe configuration SA2 (DSUDD) and special subframe
configuration SSP7 in the LTE network. 3 ms is delayed for the NR network or is advanced for the LTE network,
as shown in Figure 7-3. In an NR/LTE TDD dual-mode network, the TddFrameOffset parameter can be set to a
value ranging from 0 to 122343 and from 275943 to 307200.

75
 Sample Parameter

%%/*1879683805*/LST NRDUCELL:;%% %%/*1879683823*/LST GNODEBPARAM:;%%

RETCODE = 0 Operation succeeded. RETCODE = 0 Operation succeeded.

List NR DU Cell Display gNodeBParam

--------------- -------------------
NR DU Cell ID = 1 Frame Offset
Frame Offset(Ts) = 92160
NR DU Cell Name = NAA597A1
Duplex Mode = TDD SNR Threshold for AOA Measurement(0.01dB) = -800
Cell ID = 1 X2-U Transmission Type = Through Internal Network
Physical Cell ID = 78
PCI & Band
Frequency Band = n78
Uplink NARFCN Configuration Indicator = Not Configure
Uplink NARFCN = NULL
Downlink NARFCN = 636666
Uplink Bandwidth = 100 MHz Freq & Bandwidth
Downlink Bandwidth = 100 MHz
Cell Radius(m) = 5000
Subcarrier Spacing(KHz) = 30 Subcarrier spacing & CP
Cyclic Prefix Length = Normal Cyclic Prefix
NR DU Cell Activate State = Activated
Slot Assignment = Slot Assignment 8:2 Slot Assignment & Structure
Slot Structure = Slot Structure 54
76
Parameter Mapping

Parameter Name Sample Nokia Huawei Ericsson

Subcarrier Spacing 30 Khz NRCELLGRP.scs NRDUCell.SubcarrierSpacing NRCellDU.subCarrierSpacing/ofdmNumerology

Slot Assignment Slot Assignment 8:2 NRCELL.tddFrameStructure NRDUCell.SlotAssignment NRCellDU.tddUlDlPattern

Slot Structure Slot Structure 54 NRCELL.frameStructureType NRDUCell.SlotStructure NRCellDU.tddSpecialSlotPattern

Cyclic Prefix Length Normal Cyclic Prefix - NRDUCell.CyclicPrefixLength -

Frame Offset 92160 - gNodeBParam.FrameOffset NRCellCU.absFrameStartOffset

77
4G LTE PHYSICAL
CHANNEL
I have found one suitable
cell. What is next?
UE
Physical Channels

79
DL/UL Channel Mapping

http://www.sharetechnote.com/html/FullStack_LTE.html 80
DL Physical Channels
There are no dedicated channels in LTE, neither UL nor DL.

• PDSCH: Physical Downlink Shared Channel

• carries user data, L3 signaling, System Information Blocks & Paging
• PBCH: Physical Broadcast Channel
• for Master Information Block only
• PMCH: Physical Multicast Channel
• for multicast traffic as MBMS services
• PCFICH: Physical Control Format Indicator Channel
• indicates number of OFDM symbols for Control Channels = 1..4
• PDCCH: Physical Downlink Control Channel
• carries resource assignment messages for DL capacity allocations & scheduling grants for UL
allocations
• PHICH: Physical Hybrid ARQ Indicator Channel
• carries ARQ Ack/Nack messages from eNB to UE in respond to UL transmission

81
UL Physical Channels
• PUSCH: Physical Uplink Shared Channel
• Transmission of user data, L3 & L1 signaling (L1 signaling: CQI, ACK/NACKs, etc.)

• PUCCH: Physical Uplink Control Channel

• Carries L1 control information in case that no user data are scheduled in this subframe (e.g. H-ARQ
ACK/NACK indications, UL scheduling request, CQIs & MIMO feedback).
• These control data are multiplexed together with user data on PUSCH, if user data are scheduled in the
subframe

• PRACH: Physical Random Access Channel

• For Random Access attempts; SIBs indicates the PRACH configuration (duration; frequency; repetition;
number of preambles - max. 64)

82
INFORMATION BLOCK

MIB ( Master information Block) Radio Network Temporary identifier

• DL BW information (SI-RNTI) is allocated to SIB1 and
• Configuration PHICH
• System Frame Number another SIB
• broadcast in the Physical
Broadcast Channel (PBCH)
Every 40 ms

System Information Block 1 (SIB1)

• Scheduling info other SIB
• PLMN ID
• TA
• Cell Identifier OTHER SIB
• Cell Usage Restriction
• Frek Information
• Broadcasted via PDSCH

Every 80 ms

83
INFORMATION BLOCK DESCRIPTION
LTE system information
Description
blocks
MIB Carries physical layer information of LTE cell which in turn help receive further SIs, i.e. system bandwidth
Contains information regarding whether or not UE is allowed to access the LTE cell. It also defines the scheduling of the other SIBs.
SIB1
carries cell ID, MCC, MNC, TAC, SIB mapping.
Carries common channel as well as shared channel information. It also carries RRC, uplink power control, preamble power ramping,
SIB2
uplink Cyclic Prefix Length, sub-frame hopping, uplink EARFCN

SIB3 carries cell re-selection information as well as Intra frequency cell re-selection information

carries Intra Frequency Neighbors(on same frequency); carries serving cell and neighbor cell frequencies required for cell reselection as
SIB4 well handover between same RAT base stations(GSM BTS1 to GSM BTS2) and different RAT base stations(GSM to WCDMA or GSM to
LTE or between WCDMA to LTE etc.) . Covers E-UTRA and other RATs as mentioned

Carries Inter Frequency Neighbors(on different frequency); carries E-UTRA LTE frequencies, other neighbor cell frequencies from other
SIB5
RATs. The purpose is cell reselection and handover.

SIB6 carries WCDMA neighbors information i.e. carries serving UTRA and neighbor cell frequencies useful for cell re-selection

carries GSM neighbours information i.e. Carries GERAN frequencies as well as GERAN neighbor cell frequencies. It is used for cell re-
SIB7
selection as well as handover purpose.
SIB8 carries CDMA-2000 EVDO frequencies, CDMA-2000 neighbor cell frequencies.
SIB9 carries HNBID (Home eNodeB Identifier)
SIB10 carries ETWS prim. notification
SIB11 carries ETWS sec. notification

84
DL Physical Channel Allocation

– RS/DTX: Reference Signal

• Occupies at least 8 RE per RB(84 RE for normal CP ) throughout the whole
RB
system bandwidth

– PSS/SSS: Primary/Secondary Synchronisation Signal

• Occupies the central 72 subcarriers across 2 symbols

– PBCH: Physical Broadcast Channel

• Occupies the central 72 subcarriers across 4 symbols

– PCFICH: Physical Control Format Indication Channel

• Occupies up to 16 RE per TTI

– PHICH: Physical HARQ Indication Channel

• Occupies 12 RE, and Tx during 1st symbol of each TTI or alternative during
symbols 1 to 3 of each TTI

– PDCCH: Physical Downlink Control Channel

• Occupies the REs not used by PCFICH and PHICH and Reference Signals
within the first 1, 2 or 3 symbols of each TTI

– PDSCH: Physical Downlink Shared Channel

• Is allocated the RE not used by signals or other physical channels
85
 Mapping DL Physical Channels & Signals
1 radio frame = 20 slots = 10 ms = 10 TTI
72 subcarriers
(1.4 MHz)

one TTI
Controlled Information
➢ PDSCH physical channel used to transfer application data has access to whatever is left over.
86
at start every TTI
Different Designs for Synchronization Signals
TDD

FDD

⚫ For LTE-TDD and LTE-FDD, the primary synchronization signal (PSS) and secondary synchronization signal (SSS) are generated in
the same way and they transfer the same information.
⚫ In the subframe structures of LTE-TDD and LTE-FDD, the relative positions of synchronization signals are different. In the FDD
subframe structure, PSS and SSS are continuous, while in the TDD subframe structure, PSS and SSS are separated by two
symbols.
⚫ In the FDD subframe structure, the PSS is located in the last symbol of the 0/5 subframe, while the SSS is located in the last
but two symbol of the 0/5 subframe.
⚫ In the TDD subframe structure, the PSS is located at the third symbol in the DwPTS, while the SSS is located at the last
symbol in the last symbol of the 0/5 subframe.
⚫ According to the different relative positions of the PSS and SSS, the UE can distinguish between FDD cell and TDD cell at the
initial stage of cell search.
88
PSS and SSS Location for FDD

Extended CP 0 1 2 3 4 5
PSS (Primary
Bandwidth Synchronization
Sequence)

Normal CP 0 1 2 3 4 5 6 72
62 Subcarriers
Subcarriers
Bandwidth

SSS (Secondary
Synchronization
Sequence)

Slots 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

Radio Frame
Repeated in
slots 0 and 10

89
PSS and SSS Location for TDD

Extended CP 0 1 2 3 4 5 0 1 2 3 4 5

Bandwidth

Normal CP 0 1 2 3 4 5 6 0 1 2 3 4 5 6

Bandwidth

Slots 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

Radio Frame

90
PBCH Mapping
Slot 0 Slot 1
PBCH

Frequency
• Using QPSK Modulation
• PBCH carriers essential system information
like:
6 RBs – 72 subcarriers = 1.4 MHz

➢ DL BW configuration
(minimum LTE Bandwidth)

➢ PHICH configuration
➢ System Frame Number (8 MSB bits)

Time
SSS PBCH

PSS Unused RE

First Subframe (1 ms) 91

Reference signals
PCFICH (Physical Control Format Indicator Channel)

PCFICH 2 input bits are enough

to signal the PDCCH
• Using QPSK Modulation size: 1, 2 or 3 symbols 4
• carries information about the
number of OFDM symbols
2 bits Rate 1/16 32 bits 32 bits QPSK 16
used for transmission of block code
Scrambling
modulation symbols
PDCCHs in a subframe 4

72 subcarriers
D.C.

One Resource
4
Element Group (REG)
= 4 RE

4
PCFICH resource elements
Resource elements reserved for
reference symbols Time
92
PDCCH Resource Adjustment from PCFICH
First Subframe (1ms) Second Subframe (1ms)

Occupied subcarriers
Frequency

Time
Control region –
Control region - 3 OFDM symbols
1 OFDM symbol

Indicated by PCFICH
93
Physical Downlink Control Channel
PDCCH
• The PDCCH carries the UL & DL scheduling
assignments
• Using QPSK Modulation
• The PDCCH carries the UL & DL scheduling
assignments
• A PDCCH is transmitted on an aggregation of PDCCH format id Number of CCE's Number of RE groups Number of PDCCH bits
one 1, 2, 4 or 8 control channel elements (CCE). 0 1 9 72
A CCE consists of 9 REG = 36 REG, 1 REG = 4 RE. 1 2 18 144
2 4 36 288
3 8 72 576

94
PDSCH – Physical Downlink Shared Channel
Subframe 4 …..
PDSCH Subframe 0 Subframe 1 Subframe 2 Subframe 3

• carries user data, L3 signalling,

System Information Blocks & Paging

Frequency
SSS
PSS
PBCH
PCFICH
PHICH
PDCCH
Reference signals
PDSCH UE1
PDSCH UE2
Slot No. 0 1 2 3 4 5 6 7 8 9 ….

95
Time
Cell Search (1/2)
Remember?
What are all the steps and the physical
channels involved ?
1. PSS Primary Synchronisation Signal
(Time-slot & Frequency synchronisation
+ Physical cell id (0,1,2) )

2. SSS Secondary Synchronisation Signal

(Frame synchronisation
+ Physical Cell id group (1..168) )

3. DL Reference Signals
(Channel estimation & measurements
UE
eNodeB
4. PBCH – Physical Broadcast Channel
(MIB – DL system bandwidth, PHICH configuration)
MIB = Master Information Block
PHICH = Physical HARQ Indicator Channel

96
Cell Search
Challenge:
➢ The PBCH contains only the MIB (Master Information Block) → the SIBs (System Information
Blocks) are on the PDSCH (Physical Downlink Shared Channel)!
➢ need to read SIBs on PDSCH
➢ Problem: The UE should read PDSCH but it doesn't know which resource blocks are reserved for
it and where are they placed (in time & frequency)

Solution:
➢ PCFICH (Physical Control Format Indicator Channel) indicates the size of PDCCH (Physical
Downlink Control Channel)
➢ the PDCCH is indicating which resource blocks are scheduled and where are located

97
Cell Search (2/2)

5. PCFICH Physical Control Format Indicator Channel

(How many OFDM symbols (1,2,3) in the beginning of
the sub-frame are for PDCCH)

6. PDCCH Physical Downlink Control Channel

(Resource allocation for PDSCH )

7. PDSCH Physical Downlink Shared Channel

(SIBs: Cell global ID, parameters for cell selection / UE
reselection, … )
eNodeB

→ CELL SELECTION & RESELECTION

SIB: System Information Block

98
What are the Next Steps?

➢ The UE has selected one cell → “camping on the cell” procedure

➢ The “camping on the cell” procedure will be explained later

➢ The UE can start the initial access

I have found one suitable

cell. What is next?
UE eNodeB

99
Random Access (1/2)
8. PRACH preamble (A)
(A –1st random preamble*)

.
.
. (C)
8. PRACH preamble
(C –3rd random preamble)
UE
eNodeB
Challenge:
Several UEs may send the same preamble. How to solve the
collision ?
Solution:
→ contention resolution
* 64 Random Access Preamble Signatures available per Cell

100
Random Access (2/2)
response to RACH Preamble on PDSCH

9. PCFICH Physical Control Format Indicator Channel

(How many OFDM symbols (1,2,3) in the beginning of
the sub-frame are for PDCCH)
10. PDCCH Physical Downlink Control Channel
(Resource allocation for PDSCH)

11. PDSCH Physical Downlink Shared Channel

(Random Access response: ID of the received UE
eNodeB preamble, C-RNTI)

C-RNTI: Cell Radio Network Temporary Identity

101
Contention Resolution for the Initial Access
several UE with same RACH
Preamble Signature
 getting same UL grant 8. PRACH Preamble
 collision with RRC
Connection Request

11. PDSCH Physical Downlink Shared Channel

(Random Access response: ID of received preamble, UL
resources for TX*, C-RNTI)

12. PUSCH Physical Uplink Shared Channel

(RRC: RRC Connection Request, *C-RNTI, TMSI or
random number) UE
eNodeB 13. PDSCH Physical Downlink Shared Channel
(Contention Resolution, C-RNTI & TMSI or random
TMSI = Temporary Mobile Subscriber number)
Identity
* UL grant  PUSCH resources All other UEs not receiving correct
answer (TMSI)
→ restart Random Access (8)
102
What are the Next Steps?

➢ The random access procedure is successfully finished

➢ Next steps:
- RRC Connection Establishment
- Registration
- UE-CN signaling (Attach)
➢ Higher layer signaling -> not shown here eNodeB

Now I am connected so I can

download the web page from the
Internet. www.nokia.com
UE

103
 DL Transmission
eNodeB
CQI = Channel Quality Indicator
ACK = Acknowledgment
NACK = Negative ACK
HARQ = Hybrid Automatic
Repeat Request
1. DL Reference signals  Channel Estimate / CQI
2. PUCCH Physical Uplink Control Channel (or PUSCH) Note:
(CQI based on DL reference signals measurements) CQI along with
3. PCFICH Physical Control Format Indicator Channel data  PUSCH
(How many symbols (1,2,3) in the beginning of the
sub-frame are for PDCCH)
4. PDCCH Physical Downlink Control Channel
(DL assignment for PDSCH: Modulation & coding,
resource blocks*)
5. PDSCH Physical Downlink Shared Channel UE
(user data → initial transmission)
6. PUCCH Physical Uplink Control Channel (or PUSCH)
(ACK/ NACK for HARQ)
7. PDSCH Physical Downlink Shared Channel
(user data → eventual re-transmission)
* Physical Resource Allocation
104
 UL Transmission
1. PUCCH Physical Uplink Control Channel (or PUSCH)
(UL scheduling request*)
2. UL Sounding Reference Signal SRS
(used by Node-B for channel dependent scheduling)

3. UL Demodulation Reference Signal

(UL channel estimation, demodulation → like DPCCH in UMTS)
4. PDCCH Physical Downlink Control Channel
(UL grant – capacity allocation)
5. PUSCH Physical Uplink Shared Channel
eNodeB UE
(user data → initial transmission)

DPCCH = Dedicate Physical Control

Channel
ACK = Acknowledgment
NACK = Negative ACK
HARQ = Hybrid Automatic Repeat
Request
6. PHlCH Physical HARQ Indicator Channel
(ACK/ NACK for HARQ)
7. PUSCH Physical Uplink Shared Channel
(user data → eventual re-transmission)
* scheduling request only needed for applications with QoS like best effort
105
RBG
Downlink Resource Allocation
• eNB allocates number of PRBs in the downlink through DCI sent in PDCCH.
• In order to indicate where these PRBs are located, eNB needs a bitmap.
➢ Example: 20MHz system has 100 RBs, UE is allocated 15 RBs in the downlink. eNB needs to send 100 bits in every DCI to
tell UE where the 15 RBs allocated to that UE are located within the 100 RBs.
• In order to reduce overhead for control information (PRB bitmaps), PRBs are translated into Virtual Resource
• Blocks (VRBs) which are then localized in groups, called Resource Block Group (RBG)

106
RBG Allocation Strategy

• With 10 MHz system has 17 RBGs with size 3

RBG 0 RBG 1 RBG 2 RBG 15 RBG 16

VRB 0 VRB 1 VRB 2 VRB 3 VRB 4 VRB 5 VRB 6 VRB 7 VRB 8 ….. VRB 45 VRB 46 VRB 47 VRB 48 VRB 49

• With 15 MHz system has 19 RBGs with size 4

RBG 0 RBG 1 RBG 18 RBG 19

VRB 0 VRB 1 VRB 2 VRB 3 VRB 4 VRB 5 VRB 6 VRB 7 VRB 8 ….. VRB 68 VRB 69 VRB 70 VRB 71 VRB 72 VRB 73 VRB 74

• With 20 MHz system has 25 RBGs with size 4

RBG 0 RBG 1 RBG 23 RBG 24

VRB 0 VRB 1 VRB 2 VRB 3 VRB 4 VRB 5 VRB 6 VRB 7 VRB 8 ….. VRB 92 VRB 93 VRB 94 VRB 95 VRB 96 VRB 97 VRB 98 VRB 99

107
Sample Huawei Parameter

If the number of RB required is not that of an integral number of RBG size, the allocation is defined
according to Huawei Specific parameter RbgAllocStrategy.
Value Notes
If the number of required RBs is less than that of one RBG, the actual number of RBs are allocated to UEs at
the current transmission time interval (TTI)
ROUND_DOWN ADAPTIVE
(Current Settings) If the number of required RBGs is greater than N but less than N+1 (N is greater than or equal to 1), RBs of N RBG allocation provides
RBGs are allocated to UEs in the current TTI and the other required RBs are allocated to UEs in the next TTI. lowers the number of
The number of allocated RBGs is rounded down and an integral number of RBGs are allocated to the consumed CCEs,
scheduled UE. higher DL rates due to
higher number of RBs
In this situation, RBs are efficiently used but the scheduling times also increase and the DL user rates
allocated, while not
decrease.
The number of allocated RBGs is rounded up and an integral number of RBGs are allocated to the scheduled
wasting RB resources
ROUND_UP UE, regardless of whether the number of required RBs is greater or less than that of one RBG. when UE requires RB
below RBG size
In this situation, a few RBs are wasted but the scheduling times also decrease and the DL user rates increase. This function may slightly
If the number of required RBs is less than that of one RBG, the actual number of RBs are allocated to UEs at
decrease the average number
the current transmission time interval (TTI)
ADAPTIVE
of scheduled users per TTI in
(Recommended) the downlink.
If the number of required RBs is greater than that of one RBG, the number of allocated RBGs is rounded up
and an integral number of RBGs are allocated to the scheduled UE.

Compared with RBG round-up, this mode prevents RB waste when the number of required RBs is less than
that of one RBG.

108
Sample Huawei Parameter
Round Down (0) Round Down (0)
PRB 49 PRB 49 PRB 49 PRB 49
RBG 16 RBG 16 RBG 16 RBG 16
PRB 48 PRB 48 PRB 48 PRB 48
PRB 47 PRB 47 PRB 47 PRB 47
RBG 15 PRB 46 RBG 15 PRB 46 RBG 15 PRB 46 RBG 15 PRB 46
PRB 45 PRB 45 PRB 45 PRB 45

PRB 2 PRB 2 PRB 2 PRB 2

RBG 1 PRB 1 RBG 1 PRB 1 RBG 1 PRB 1 RBG 1 PRB 1
PRB 0 PRB 0 PRB 0 PRB 0
PRB 2 PRB 2 PRB 2 PRB 2
RBG 0 PRB 1 RBG 0 PRB 1 RBG 0 PRB 1 RBG 0 PRB 1
PRB 0 PRB 0 PRB 0 PRB 0

Round Up (1) Round Up (1)

N(RBG)<1 N(RBG)+1
PRB 49 PRB 49 PRB 49 PRB 49
RBG 16 RBG 16 RBG 16 RBG 16
PRB 48 PRB 48 PRB 49 PRB 48 PRB 48
PRB 49 RBG 16
RBG 16 PRB 47 PRB 47 PRB 48 PRB 47 PRB 47
PRB 48 RBG 15 PRB 46 RBG 15 PRB 46 RBG 15 PRB 46 RBG 15 PRB 46
PRB 47
PRB 47 PRB 45 PRB 45 PRB 45 PRB 45
RBG 15 PRB 46
RBG 15 PRB 46
PRB 45
PRB 45

PRB 2 PRB 2 PRB 2 PRB 2

RBG 1 PRB 1 RBG 1 PRB 1 PRB 2 RBG 1 PRB 1 RBG 1 PRB 1
PRB 2 PRB 0 PRB 0 PRB 0 PRB 0
RBG 1 PRB 1
RBG 1 PRB 1 PRB 2 PRB 2 PRB 2 PRB 2
PRB 0
PRB 0 RBG 0 PRB 1 RBG 0 PRB 1 RBG 0 PRB 1 RBG 0 PRB 1
PRB 2
PRB 2 PRB 0 PRB 0 PRB 0 PRB 0
RBG 0 PRB 1
RBG 0 PRB 1
PRB 0
PRB 0
Adaptive (2) Adaptive (2)
PRB 49 PRB 49 PRB 49 PRB 49
RBG 16 RBG 16 RBG 16 RBG 16
PRB 48 PRB 48 PRB 48 PRB 48
PRB 47 PRB 47 PRB 47 PRB 47
RBG 15 PRB 46 RBG 15 PRB 46 RBG 15 PRB 46 RBG 15 PRB 46

Ex: with 10 MHz

PRB 45 PRB 45 PRB 45 PRB 45

system, It has 17 PRB 2 PRB 2 PRB 2 PRB 2

RBGs with size 3 RBG 1 PRB 1
PRB 0
RBG 1 PRB 1
PRB 0
RBG 1 PRB 1
PRB 0
RBG 1 PRB 1
PRB 0
PRB 2 PRB 2 PRB 2 PRB 2
RBG 0 PRB 1 RBG 0 PRB 1 RBG 0 PRB 1 RBG 0 PRB 1
PRB 0 PRB 0 PRB 0 PRB 0

109
Sample Improvement from RBG round down to adaptive

Gaining Improvement : 14.2%

Gaining Improvement : 22.0%

110
5G NR PHYSICAL
CHANNEL
I have found one suitable
cell. What is next?
UE
Channel Mapping
Logical to Transport Maping

Transport to Physical Mapping

112
Overview
Downlink Physical Channel/Signal Function

Used for time-frequency synchronization and cell

SS Synchronization Signal
search.
PBCH Physical Broadcast Channel Carries system information to be broadcast.
Downlink Uplink
Transmits control signaling, such as signaling for
PDCCH Physical Downlink Control Channel
uplink and downlink scheduling and power control.
Physical Physical Physical Physical PDSCH Physical Downlink Shared Channel Carries downlink user data.
Channel Signal Channel Signal Used for downlink data demodulation and time-
DMRS Demodulation Reference Signal
frequency synchronization.
PTRS Phase Tracking Reference Signal Tracks and compensates downlink phase noise.
PBCH PSS/SSS PRACH DMRS
Used for downlink channel measurement, beam
Channel State Information
CSI-RS management, RRM/RLM measurement, and refined
Reference Signal
time-frequency tracking.
PDCCH DMRS PUCCH PTRS
Uplink Physical Channel/Signal Function
PRACH Physical Random Access Channel Carries random access request information.
Transmits L1/L2 control signaling, such as signaling
PDSCH PTRS PUSCH SRS PUCCH Physical Uplink Control Channel for HARQ feedback, CQI feedback, and scheduling
request indicator.
PUSCH Physical Uplink Shared Channel Carries uplink user data.
CSI-RS Used for uplink data demodulation and time-frequency
DMRS Demodulation Reference Signal
synchronization.
PTRS Phase Tracking Reference Signal Tracks and compensates uplink phase noise.
Used for uplink channel measurement, time-frequency
SRS Sounding Reference Signal
synchronization, and beam management.
113
Application of NR Physical Channels

⚫ Physical channels involved in cell search gNodeB

Preamble Msg3
– PSS/SSS -> PBCH -> PDCCH -> PDSCH (PRACH) (PUSCH)
RMSI ... RAR Msg4
PSS/SSS MIB (PDCCH, (PDCCH, (PDCCH,
(PBCH) PDSCH) PDSCH) PDSCH)
⚫ Physical channels involved in random access UE
HARQ excluded HARQ included
– PRACH -> PDCCH -> PDSCH -> PUSCH from RAR in Msg4

Cell search Random access

⚫ Physical channels involved in downlink data transmission
– PDCCH -> PDSCH -> PUCCH/PUSCH gNodeB
CSI ACK/NACK
(PUCCH/ (PUCCH/
... PUSCH) Data PUSCH) Data ...(PDCCH,
Paging
⚫ Physical channels involved in uplink data transmission CSI-RS (PDCCH, (PDCCH,
PDSCH) PDSCH) PDSCH)
– PUCCH -> PDCCH -> PUSCH -> PDCCH UE
Downlink data transmission

gNodeB
SRS SR BSR/Data BSR/Data
(PUCCH) (PUSCH) (PUSCH)
... UL Grant ACK/NACK
(PDCCH) (PDCCH)
UE

Uplink data transmission

114
Physical Layer Interaction

115
Physical Layer Interaction

116
Physical Layer Interaction

117
Physical Layer Interaction

118
Physical Layer Interaction

119
Physical Layer Interaction

Detail Flow :: https://www.eventhelix.com/5G/non-standalone-access-en-dc/details/5g-non-standalone-access-en-

dc.htmlhttps://www.eventhelix.com/5G/non-standalone-access-en-dc/details/5g-non-standalone-access-en-dc.html
120
Physical Channel Processing: Downlink
⚫ Downlink channel processing
– Scrambling: Bits are randomized for channel decoding.
– Modulation: Scrambled bits in each codeword are modulated to generate a complex-valued modulation symbol.
– Layer mapping: Complex-valued modulation symbols to be transmitted are mapped onto one or several layers.
– Antenna port mapping: Complex-valued modulation symbols at each transmit layer are mapped to antenna ports.
– RE mapping: Complex-valued modulation symbols on each antenna port are mapped to REs.
– Waveform generation: Signals over each antenna port are generated as OFDM signals.

Codewords Layers Antenna ports

Modulation Resource Element OFDM signal
Scrambling
mapper mapper generation
Antenna Port

...
...
Layer mapper
mapper
Modulation Resource Element OFDM signal
Scrambling
mapper mapper generation

No such procedures on PDCCH and PBCH

Physical Channel Channel Coding Modulation Mode Number of Layers Waveform

PDSCH LDPC QPSK, 16QAM, 64QAM, 256QAM 1 to 8 CP-OFDM

PBCH Polar QPSK 1 CP-OFDM

PDCCH Polar QPSK 1 CP-OFDM

121
Downlink RS Design

LTE RS Function NR RS ⚫ LTE RS design: Focus on the CRS

– All RSs are bound to the cell IDs.
SS
SS Coarse Timing/Frequency Tracking SS (PSS/SSS) SS – CSI-RS was introduced in 3GPP Release 10 but few UEs
(PSS/SSS)
support the CSI-RS.
Fine Timing/Frequency Tracking
CSI-RS (TRS) ⚫ NR RS design: CRS free, RS function reassembly
Digital AGC
CRS – All RSs except for PSSs/SSSs are decoupled from the cell
CRS Demodulation for PBCH DMRS for PBCH DMRS
ID.
Demodulation for PDCCH DMRS for PDCCH – Beamformed PSSs/SSSs are transmitted in a narrow
beam.
DMRS CRS, DMRS Demodulation for PDSCH DMRS for PDSCH – DMRS demodulation applies to both PDCCH and PDSCH.
– Enhancements are made for the DMRS type, port quantity,
CRS RRM CSI-RS, SSB and configuration.
CSI-RS CRS, CSI-RS Channel State Information CSI-RS – CSI-RS pattern and configurations are enhanced for RRM,
CSI-RS CSI acquisition, beam management, and refined time-
\ Beam Management (NR new function) frequency tracking.
– PTRS is added for phase noise tracking on high frequency
\ Phase Noise Tracking (NR new function) PTRS PTRS bands.

122
Time-Frequency Domain Distribution
⚫ Schedulable and configurable resources through flexible physical channel and signal design.
– PDCCH: Occupies the first 1 to 3 symbols in a slot in the time domain. Frequency resources can be configured. PDCCH and PDSCH can share FDM resources in
the same symbol.
– DMRS for PDSCH: Time-domain positions as well as frequency densities and resources can be configured. DMRS and PDSCH can share FDM resources in the
same symbol.
– SSB: Occupies 20 RBs in the frequency domain with a fixed time-domain position and a configurable frequency-domain position. SSB and PDSCH can share FDM
resources in the same symbol.
– CSI-RS: Time-domain positions as well as frequency-domain positions and bandwidths can be configured. CSI-RS and PDSCH can share FDM resources in the
same symbol.
Subframe 0 Subframe 1
Slot 0:DL Slot 1:DL Slot 2:DL Slot 3:Mixed Slot
0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13

UL
PDSCH GP
(SRS)

PDCCH

SSB
BWP

DMRS for CSI-RS

PDSCH

123
PSS/SSS: Introduction
PSS: Primary Synchronization Signal
SSS: Secondary Synchronization Signal ⚫ Differences with LTE
– Different from that in LTE, a PSS/SSS in NR
⚫ Main functions
can be flexibly configured in any position on
– Used by a UE for downlink synchronization, including clock
the carrier and do not need to be positioned at
synchronization, frame synchronization, and symbol
the center frequency.
synchronization.
– Subcarrier spacings for the PSS/SSS vary
– Used for obtaining cell IDs.
PSS SSS
with operating frequency bands and are
⚫ Features specified by 3GPP.
– Both the PSS and the SSS use PN sequences.
– A PSS occupies one symbol in the time domain and 127 REs in
Initial BWP
the frequency domain. Flexible SS/PBCH
position
– The PSS/SSS and the PBCH occupy 4 consecutive symbols in
the time domain and 20 RBs in the frequency domain to form an
Carrier
SS/PBCH (SSB) block. Within an SS/PBCH block, the PSS is center

mapped to symbol 0 while the SSS is mapped to symbol 2.

– Different from that in LTE, Occupies the central 72 subcarriers
across 2 symbols.
124
PSS/SSS: Sequence Generation

LTE NR
PSS = 0,1,2 PSS = 0,1,2
SSS = 0 – 167 (Total 168) SSS = 0 – 335 (Total 336)

PCI = 3*SSS + PSS PCI = 3*SSS + PSS

Start PCI = 3*0+0 = 0 Start PCI = 3*0+0 = 0
Last PCI = 3*167+2 = 503 Last PCI = 3*335+2 = 1007
PCI range = 0 – 503 (Total 504 PCI) PCI range = 0 – 1007 (Total 1008 PCI)

125
PSS/SSS Parameter Mapping

Parameter Name Sample Nokia Huawei Ericsson

GUtranDUCell.physicalLayerCellIdGroup &
Physical Cell ID 155 (0~1007) NRCELL.physCellId NRDUCell.PhysicalCellId
physicalLayerSubCellId

126
PBCH: Introduction
⚫ Main functions
– Used to obtain necessary information for network access, such as the
SFN as well as the position and size of the initial BWP.

⚫ Features
– Different from that in LTE, the PSS/SSS and the PBCH in NR together
form an SS/PBCH block which occupies 4 consecutive symbols in the
time domain and 20 RBs in the frequency domain. Within an SS/PBCH
block, the PBCH is mapped to symbols 1 and 3 and occupies some
REs in symbol 2.

PBCH

127
DMRS for PBCH

Each RB contains 3 REs for DMRS pilot transmission on the PBCH. To avoid inter-cell PBCH DMRS interference,
PBCH DMRSs are staggered in the frequency domain on a Physical cell ID basis.

PCImod4 = 0 PCImod4 = 1 PCImod= 2 PCImod4= 3

PBCH DMRS

128
SS/PBCH: Transmission Mechanism (1)
⚫ Main functions
– The PSS/SSS and the PBCH are combined as an SSB block in 5G to allow for massive MIMO. Each SSB block can be decoded
independently. A UE parses an SSB block to obtain information including the cell ID, SFN, and SSB index (similar to the beam ID).
– At most, 4 SSB blocks, 8 SSB blocks, and 64 SSB blocks can be defined for sub-3 GHz, sub-3 GHz to sub-6 GHz, and above 6 GHz,
respectively.

When a 30 kHz subcarrier spacing is used, CASE C is primary.

129
 SS/PBCH: Transmission Mechanism (2)
⚫ SSB block position within the slot
– SSB blocks support beam scanning which must be completed within 5 ms. A radio frame can transmit an SSB block in the first 5 ms (first half frame) or the last 5 ms (last half
frame). How an SSB block is transmitted in a radio frame can be obtained from the MIB or PBCH pilot.
– Each SSB block has a unique number (SSB index). For low frequencies, this number is directly obtained from the PBCH pilot. For high frequencies, the 3 least significant bits and
the 3 most significant bits of this number are obtained from the PBCH pilot and the MIB, respectively.
– When the actual number of beams in a cell is less than the maximum number of SSB blocks specified by 3GPP, SIB1 or RRC signaling can be used to indicate which positions in the
radio frame are not occupied by SS/PBCH blocks and can be used for PDSCH data transmission.
– SSB block broadcast period is sent to UEs through SIB1 and can be 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, or 160 ms.

⚫ Sample for Case C

130
PDCCH: Introduction
⚫ Main functions ⚫ RNTIs used by DCIs
– Sends DL assignments for downlink scheduling. – P-RNTI (paging message)
– Sends UL grants for uplink scheduling. – SI-RNTI (system message)
– Sends Slot Format Indicators (SFIs) and power control commands. – RA-RNTI (RAR)
⚫ Features – Temporary C-RNTI (Msg3/Msg4)
– In the time domain, the PDCCH occupies the first 1 to 3 OFDM – C-RNTI (UE uplink and downlink data)
symbols in each slot. In the frequency domain, CCEs are aggregated. 1 – SFI-RNTI (slot format)
CCE contains 6 REGs. – INT-RNTI (resource pre-emption)
– Different bit rates can be supported through aggregating different – TPC-PUSCH-RNTI (PUSCH power control command)
number of CCEs.
– TPC-PUCCH-RNTI (PUCCH power control command)
– Each REG has its own DMRS for PDCCH demodulation.
– TPC-SRS-RNTI (SRS power control command)
– Downlink Control Information (DCI) is transmitted on the PDCCH.
Different RNTIs are used by DCIs with different contents for CRC
scrambling.
– UEs perform PDCCH demodulation through blind detection.

131
PDCCH: DCI Format

⚫ PDCCH DCI formats

– See section 7.3.1 in 3GPP TS 38.212 for detailed DCI format descriptions. The number of bits has not been determined yet
and is subject to protocol updates.
Category DCI Format Description Number of Bits
Fallback DCI. Indicates PUSCH scheduling and is used upon waveform
Format 0_0
DCI formats for scheduling of PUSCH change.
Format 0_1 Indicates PUSCH scheduling.
Fallback DCI. Indicates PDSCH scheduling and is used upon public message
Format 1_0 scheduling (such as paging and RMSI scheduling) and status change (such
DCI formats for scheduling of PDSCH as BWP switch).
Format 1_1 Indicates PDSCH scheduling.

Format 2_0 Indicates the SFI (slot format).

Notifies the PRBs and the OFDM symbols where a UE may assume no
Format 2_1 transmission is intended for the UE.
DCI formats for other purposes Indicates which PRBs and OFDM symbols to which UE data is not mapped.
Format 2_2 Indicates power control commands for PUSCH and PUCCH.

Format 2_3 Indicates power control commands for SRS transmission.

132
PDCCH: Time-Frequency Resource Configuration
⚫ Control resource set (CORESET) and search space
– The CCE is the minimum resource unit in PDCCH
transmission. 1 CCE contains 6 REGs, with each
REG corresponding to an RB.
– The CORESET mainly indicates the number of
PDCCH-occupied symbols (in the time domain),
the number of RBs (in the frequency domain),
slot duration, and offset.

RE

CORESET 2

DMRS
REG

CC
CORESET 1 E

133
PDCCH: Time-Frequency Resource Configuration
The PDCCH carries the DCI (Downlink Control Information), i.e. the resource
allocation. It is scheduled based on a RNTI (Radio Network Temporary Identifier).
As illustrated in the DCI is mapped into 1 or more CCE (Control Channel
Elements), with each control channel element consisting of 6 REG (Resource
Element Groups). Each REG equates to 1 PRB (12 subcarriers) x one OFDM
symbol.
In addition to a CCE, 5G NR defines a CORESET (Control-Resource Set) for
the PDCCH. This consists of frequency domain resource blocks, given by
the higher-layer parameter “frequencyDomainResources”. This is a bitmap
for the BWP (Bandwidth Part), with each bit relating to 6REGs. In the time
domain, the higher-layer parameter “duration”, defines 1, 2 or 3 symbols.

frequencyDomainResources = 16 bit x 6RB = 96 RB

MO Parameter Value
duration = 1 Symbol NRDUCellPdcch OccupiedSymbolNum 1SYM, 2SYM
NRDUCellPdcch OccupiedRbNum 0~264, step: 12
134
PDCCH: Type

⚫ There are 3 PDCCH types according to the contents sent on the PDCCH.
– Common PDCCH: Used for transmitting common messages (such as system and paging messages) and data scheduling before UE's RRC connection is
established.
– Group Common PDCCH: Used for scheduling the SFI (slot format) and the PI (resource pre-emption) for a UE group.
– UE-specific PDCCH: Used for scheduling the UE-level data and power control information.

Type Common PDCCH Group Common PDCCH UE-Specific PDCCH

Schedules common messages
Function Indicates the SFI and the PI. Schedules the UE-level data and power control information.
(RMSI/OSI, paging, Msg2/4).

Time domain 1 to 3 symbols (MIB or RRC configuration) 1 to 3 symbols (RRC signaling configuration)

Frequency domain Initial BWP (24/48/96 RBs) BWP (full bandwidth at most)

Aggregation level 4/8/16 1/2/4/8/16

RS DMRS ¼ density

Mapping Time domain preferred interleaving mapping Time domain preferred interleaving mapping/Non-interleaving mapping

CORESET configuration MIB or RRC configuration RRC signaling configuration RRC signaling configuration and DCI signaling configuration

Blind detection space Common Search Space (CSS) UE-Specific Search Space (USS)

RMSI: 4 for AL 4, 2 for AL 8, 1 for AL16

Number of blind detections
Total: 44/36/22/20 for 15/30/60/120 kHz (RRC)

135
PDSCH: Physical Layer Processing

⚫ PDSCH physical layer processing

– Scrambling: Scrambling code IDs are configured on a UE basis by using the higher layer parameter dataScramblingIdentityPDSCH. When this
parameter is not configured, they are the same as cell IDs.
– Modulation: The modulation and coding scheme table is configured on a UE basis by using the higher layer parameter mcs-Table to indicate the highest
order QAM (64QAM or 256QAM).
– Layer mapping: Codewords are mapped onto multiple layers for transmission. Single-codeword is mapped 1 to 4 layers and dual-codeword is mapped
to 5 to 8 layers.
– Weighting: Multi-layer data is mapped to each transmit antenna. Weighting can be implemented through SRS reciprocity-based dynamic rights,
feedback-based PMI rights, and open-loop static rights. Only one transmission mode is available, in which weights are transparent to UEs. To be
specific, DMRS and data are processed using the same weighting method.
– Resource mapping: In the DCI, the "Time domain resource assignment" field indicates the starting symbol and the number of consecutive symbols. Two
methods, Type0 and Type1, are available for frequency domain resource assignment. In the DCI, the "Frequency domain resource assignment" field
indicates the method. During resource mapping, positions configured by using the higher layer parameter rate-match-PDSCH-resource-set indicated
by the "Rate matching indicator" field in the DCI are not mapped to any resources.
– Waveform: CP-OFDM waveforms are supported.

Codewords Layers Antenna ports

Modulation Resource Element OFDM signal
Scrambling
mapper mapper generation
Layer Antenna Port
mapper mapper
Modulation Resource Element OFDM signal
Scrambling
mapper mapper generation

136
PDSCH Resource Allocation
• RBG-based frequency diversity scheduling can be used for PDSCH resource allocation
– Frequency diversity scheduling

Power Sequential allocation 20 MHz RBG size 4 as an example

UE1 UE2 UE3

…
Frequency
System bandwidth
Start RB
Total RB Count RBG Size
1-36 2
37-72 4
73-144 8
145-273 16

137
Downlink Scheduler

Channel status
-PMI/CQI/RI
-Beamforming gain
Processing physical- Scheduler
layer measurement
information
Scheduling in each TTI Scheduled bearer
Data
-Downlink data buffer status
-HARQ feedback status Processing scheduling
Dynamic scheduling MCS for
information scheduled UEs

Priority calculation PRB and TBS

allocation for
Downlink power input scheduled UEs

gNodeB model and MCS selection Rank for

UE capability scheduled UEs
-Downlink BWP Sending weight for
-Synchronization status Resource allocation scheduled UEs
-Number of TRXs

Inputs Outputs

138
MCS Selection and RB Quantity Calculation

CQI validity Beamforming

Out-loop To-be-sent Remaining Remaining
and reliability gain
adjustment data amount RBs power
compensation
CQI and MCS
reported by filtering
the UE Original Adjusted Required Scheduled
CQI
MCS MCS RBs RBs

CQI adjustment
5-bit MCS is obtained based on UE-reported 4-bit CQI for downlink transmission.
MCS is adjusted based on UE-reported ACK/NACK (MCS index is increased if an ACK is reported and
decreased if an NACK is reported).
MCS adjustment helps ensure that the IBLER meets the IBLERtarget requirements (10% generally) to
ensure service quality.

139
CQI Selection
64QAM
MCS Index Modulation CR SE CQI Index MCS Index Modulation CR SE CQI Index
0 2 0.11 0.22 1 0 2 0.11 0.22 1
1 2 0.18 0.36 2 1 2 0.15 0.3 2
2 2 0.3 0.6 - 2 2 0.18 0.36 3
3 2 0.45 0.9 3 3 2 0.25 0.5
4 2 0.58 1.16 - 4 2 0.3 0.6 4
5 4 0.36 1.44 4 5 2 0.38 0.76
6 4 0.42 1.68 - 6 2 0.45 0.9 5
7 4 0.47 1.88 5 7 2 0.5 1
8 4 0.54 2.16 - 8 2 0.58 1.16 6
9 4 0.6 2.4 6 9 2 0.63 1.26
10 4 0.64 2.56 - 10 4 0.36 1.44 7
11 4 0.42 1.68
11 6 0.45 2.7 7
12 4 0.47 1.88 8
12 6 0.5 3 -
13 4 0.54 2.16
13 6 0.55 3.3 8
14 4 0.6 2.4 9
14 6 0.6 3.6 -
15 4 0.64 2.56
15 6 0.65 3.9 9
16 4 0.68 2.72
16 6 0.7 4.2 -
17 6 0.45 2.7 10
17 6 0.75 4.5 10
18 6 0.5 3
18 6 0.8 4.8 19 6 0.55 3.3 11
19 6 0.85 5.1 11 20 6 0.6 3.6
20 8 0.66 5.28 21 6 0.65 3.9 12
21 8 0.69 5.52 12 22 6 0.7 4.2
22 8 0.73 5.84 23 6 0.75 4.5 13
23 8 0.77 6.16 13 24 6 0.8 4.8
24 8 0.82 6.56 25 6 0.85 5.1 14
25 8 0.85 6.8 14 26 6 0.87 5.22
26 8 0.88 7.04 27 6 0.89 5.34
27 8 0.92 7.36 15 28 6 0.92 5.52 15

256QAM

140
PDSCH Resource Allocation Type0

• Several continuous RBs form an RB group (RBG), and RBs to be used are indicated in the unit of RBG.
• The number of RBs that an RB group has is determined by the downlink bandwidth.

Number of Downlink PRBs RBG Size

1 to 36 2
37 to 72 4
73 to 144 8
145 to 273 16

141
PDSCH Resource Allocation Type0

• Take 34 downlink RBs for example. The RBG size is 2 and the 34 RBs can be divided into 17 RBGs
(34/2). If 18 RBs are scheduled for a UE, which are mapped to RBGs 2, 3, 4, 5, 8, 10, 11, 13, and
17. The bitmap of this example is as follows:

34 RBs

RBG 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

Bitmap
(0/1) 0 1 1 1 1 0 0 1 0 1 1 0 1 0 0 0 1

142
DMRS for PDSCH: Introduction
⚫ Function: Channel estimation during PDSCH demodulation
⚫ DMRS category: Different in low-speed and high-speed scenarios
– Front Loaded (FL) DMRS: Occupies 1 to 2 symbols and needs to be configured by default.
– Additional (Add) DMRS: Occupies 1 to 3 symbols. Additional DMRS and its symbol position are configured by
using the higher layer parameter UL-DMRS-add-pos in high-speed scenarios.
Slot
⚫ DMRS type: Different DMRS types allow different maximum numbers of ports. k l 0 1 2 3 4 5 6 7 8 9 10 11 12 13
SCn11
– Type1: Single-symbol: 4, dual-symbol: 8 SCn10
SCn9 FL DMRS
– Type2: Single-symbol: 6, dual-symbol: 12 SCn8
SCn7
– The DMRS type is configured using the higher layer parameter DL-DMRS-Config-Type. SCn6
SCn5 Add DMRS
⚫ DMRS time-frequency mapping position SCn4
SCn3
– Mapping type A: Staring from the third or fourth symbol in the slot. Specific mapping positions are indicated by SCn2
SCn1
the higher layer parameter UL-DMRS-typeA-pos. SCn0

– Mapping type B: Staring from the first symbol on the scheduled PDSCH.

143
DMRS for PDSCH Sample

144
PTRS for PDSCH: Background
Phase rotation of demodulation constellation diagram

⚫ PTRS: Phase-tracking reference signal:

This is a reference signal newly introduced in NR, which is used to trace
the changes of phase noise and is mainly used in high frequency bands.
⚫ Phase noise:
– Generation: A random change of the phase of the system output signal caused by
the noise (random white noise, flicker noise) of the radio-frequency components.
– Impact: The SNR or EVM in the receive segment deteriorates, causing a large
number of bit errors. As a result, the use of high-order constellation modulation is
restricted and the system capacity is severely affected.
– Frequency band difference: There is little impact on the sub-6 GHz band. In the
above 6 GHz frequency band, the phase noise response greatly increases due to
20 dB
the increase of frequency multiplication times of the reference clock and the

PSD: dBC/Hz
deterioration
technical manufacturing and power consumption of the component.
⚫ Solutions:
– The PTRS and the phase estimation compensation algorithm are introduced.
– Increase the subcarrier spacing to reduce the ICI and ISI caused by phase noise.
– Improve the quality of the local oscillator to reduce the phase noise.
Frequency (Unit: MHz)
145
CSI-RS: Main Functions

⚫ The main functions and types of the CSI-RS are as follows:

Function CSI-RS Type Description
NZP-CSI-RS
(Non-Zero Power CSI-RS) Used for channel state information (CSI) measurement. The UE
CSI obtaining reports the following content:
CSI-IM CQI, PMI, rank indicator (RI), layer Indicator (LI)
Channel quality (CSI-RS Interference Measurement)
measurement Beam Used for beam measurement. The UE reports the following content:
NZP-CSI-RS
management L1-RSRP and CSI-RS resource indicator (CRI)
RLM/RRM Used for radio link monitoring (RLM) and radio resource management
NZP-CSI-RS
measurement (handover). The UE reports the following content: L1-RSRP
Time-frequency offset tracing TRS (Tracking RS) Used for precise time-frequency offset tracing.

⚫ Design principles and features of the CSI-RS:

– Sparsity: The density of the time and frequency domains is low and the domain resource consumption is low. The maximum
number of ports is 32.
– Sequence generation and cell ID decoupling: The scrambling code ID is configured by higher layer parameters. UCNC is
supported.
– Flexible resource configuration: UE-specific configurations for time-frequency resources are supported.

146
CSI-RS: Sequence Design

⚫ Pseudo-random sequence ⚫ Mapping to RE resources (For the CSI-RS pattern, refer to

the next page.)
r ( m) =
1
(1 − 2  c(2m)) + j 1
(1 − 2  c(2m + 1)) – Number of time domain symbols: Each CSI-RS resource occupies 1
2 2 to 4 symbols in the time domain.
Pseudo-random sequence initialization – Time domain position: The TRS supports the following symbol
( ( )
cinit = 2  14ns,f + l + 1 (2nID + 1) + nID mod 231
10 
) positions: {4,8}, {5,9}, and {6,10}. The positions of other supported
symbols are {0–13}. The specific positions are configured by higher
layer parameters.
UE-specific scrambling code ID: determined by the higher layer parameter
ScramblingID and is decoupled from the cell ID. The UCNC is supported. – Frequency domain position: It is configured by the CSI-RS-
ResourceMapping parameter.
⚫ Pseudo-random sequence x OCC Matrix multiplication + – Number of supported ports: {1,2,4,8,12,16,24,32}
resource mapping:
– Purpose: Multiple CRS-RS ports are multiplexed on the
same time-frequency resource.
– CDM type: 1, 2, 4 and 8 (FDM 1–2, TDM 1–4)
FDM: 1–2 TDM: 1–4

Power offset
147
 CSI-RS: Pattern
Row Ports Density CDM Type CDM type indicates the number of ports that can be multiplexed by each colored resource.
1 1 3 No CDM
2 1 1, 0.5 No CDM CSI-IM
3 2 1, 0.5 FD-CDM 2
1 port 12 ports Pattern 0
4 4 1 FD-CDM 2
5 4 1 FD-CDM 2
6 8 1 FD-CDM 2
7 8 1 FD-CDM 2
CDM 4
8 8 1 (FD 2, TD 2)
2 ports 16 ports
9 12 1 FD-CDM 2
CDM 4
10 12 1 (FD 2, TD 2)
11 16 1, 0.5 FD-CDM 2 CSI-IM
12 16 1, 0.5
CDM 4 Pattern 1
(FD 2, TD 2)
13 24 1, 0.5 FD-CDM 2 4 ports 24 ports
CDM 4
14 24 1, 0.5 (FD 2, TD 2)
CDM 8
15 24 1, 0.5 (FD 2, TD 4)
16 32 1, 0.5 FD-CDM 2
CDM 4 32 ports
17 32 1, 0.5
(FD 2, TD 2)
8 ports
CDM 8
18 32 1, 0.5
(FD 2, TD 4)

– The row 1 pattern is used only for TRS.

– The row 2–18 patterns can be used for CSI measurement.
– The CSI-RS used for beam management can only use patterns of 1 port and 2 ports (row 2–3).
148
CSI-RS: Resource Configuration
⚫ The CSI-RS of the channel quality measurement and frequency offset measurement is configured by using RRC signaling:
CSI-RS pattern (frequency domain position, time domain position)
CDM-Type
ResourceSetId Density
ResourceSetId Frequency band
Power offset
Resources
(8 sets at most) Scrambling code
ResourceConfig ResourceSets TRS information
(32 sets at most) (64 sets at most)
Repetition (Whether to send repeatedly)
SSB resource Period (supporting periodic, semi-static, and UCI on PUSCH reporting)

Period attribute Non-periodic mode (supporting UCI on PUSCH reporting)

Semi-static mode (supporting semi-static and UCI on PUSCH reporting)

⚫ The CSI-RS used for puncturing resources is configured by using RRC signaling, and DCI triggers corresponding resource set. During
demodulation, the UE performs puncturing on the corresponding resource position (a union set of resource positions corresponding to all
resources) of the resource set.
⚫ Each UE can be configured with multiple sets of CSI-RS resources (a maximum of 64 sets) and multiple sets of ZP-CSI-RS resources (a
maximum of three sets) through RRC signaling.
149
Throughput
Calculation
Data Rate Calculation
1. Maximum channel data rate

The maximum channel data rate is calculated taking into account the total number of the available resource blocks in 1 TTI = 1ms
Max Data Rate = Number of Resource Blocks x 12 subcarriers x (14 symbols/ 1ms)
= Number of Resouce Blocks x (168 symbols/1ms)

2. Impact of the Channel Bandwith: 5, 10, 20 MHz

For BW = 5MHz -> there are 25 Resource Blocks

-> Max Data Rate = 25 x (168 symbols/1ms) = 4,2 * Msymbols/s
BW = 10MHz -> 50 Resource Blocks -> Max Data Rate = 8,4 Msymbols/s
BW = 20MHz -> 100 Resource Blocks -> Max Data Rate =16,8 Msymbols/s

3. Impact of the Modulation: QPSK, 16QAM, 64QAM

For QPSK – 2bits/symbol; 16QAM – 4bits/symbol; 64QAM – 6 bits/symbol

QPSK: Max Data Rate = 16,8 Msymbols/s * 2bits/symbol = 33,2 Mbits/s (bandwith of 20 MHz)
16QAM: Max Data Rate = 16,4 Msymbols/s * 4 bits/symbols = 66,4 Mbits/s
64QAM: Max Data Rate = 16,4 Msymbols/s * 6 bits/symbols = 99,6 Mbits/s

151
Data Rate Calculation
4. Impact of the Channel Coding

In LTE Turbo coding of rate 1/3 will be used. The effective coding rate is dependent on the Modulation and Coding Scheme
selected by the scheduler in the eNodeB. In practice several coding rates can be obtained. Here it is considered 1/2 and 3/4
1/2 coding rate: Max Data rate = 99,6 Mbits/s * 0,5 = 49,8 Mbits/s
3/4 coding rate: Max Data rate = 99,6 Mbits/s * 0,75 = 74,7 Mbits/s

5. Impact of MIMO = Multiple Input Multiple Output

MIMO is discussed in chapter 9. If spatial diversity it is used (2x2 MIMO) then the data rate will be doubled since the data is sent
in parallel in 2 different streams using 2 different antennas
2x2 MIMO: Max Data Rate = 74,7 Mbit/s * 2 = 149,4 Mbits/s

6. Impact of physical layer overhead and higher layers overhead

The real data rate of the user will be further reduced if the physical layer overhead is considered. Also the higher layers may
introduce overhead as shown in chapter number 2. For example IP , PDCP , RLC and MAC are introducing their own headers.
This type of overheads are not discussed here

152
 Throughput Calculation Using 3GPP Table
Condition:
– 20MHz bandwidth, total 100 PRBs allocated
– 2x2 MIMO (2 antennas for TX, 2 Antennas for RX)
– Maximum TB Size in normal DL subframe = 75376 bits
– MCS 28

Downlink Throughput Calculation :

• FDD = 2 x 75376 = 150.752 Mbps

• TDD Config 2 & Special Subframe config 7
2 x 75376 x (0.6 + 0.2 x (10/14) = 111.9872 Mbps
• TDD Config 1 & Special Subframe config 5 ??

153
Data Rate Calculation

For TDD Slot Assignment 8:2 & slot structure 54 Rmax = Value depends on the type of coding from 3GPP 38.212 and 3GPP 38.214
= 8:2 indicated 7 downlink timeslot + SS56 contain 6 symbols -> 0.7 + 0.1(6/14) = 0.742857 (For LDPC code maximum number is 948/1024 = 0.92578125)

So Max Throughput = 2.34 Gbps x 0.74 = 1.738 Gbps http://niviuk.free.fr/nr_capability.php

https://5g-tools.com/5g-nr-throughput-calculator/
154
CSI-RS Periodicity

Parameter Defaul Value

Nokia Huawei Ericsson
Name (N/H/E)

CSI Period 320/80/40 NRCELLGRP.csiReportPeriodicity NRDUCellCsirs.CsiPeriod NRCellDU.csiRsPeriodicity

155
LTE RADIO PLANNING
CONCEPT

1. Frequency planning
2. PCI Planning
3. PRACH Planning
4. TAL/TAC Planning
5. Neighbor Planning
Process for Planning the LTE Network
Information Coverage area, Radio environment
Collection User Number, Traffic Model,
Service QoS
Available frequency and bandwidth

Link Budget
Pre-Planning Network Dimensioning
Output: site number, ideal site location
General Process
Detailed Simulation based on surveyed site parameter
Planning Output: Engineering parameter table,
Coverage prediction, etc

Cell Planning

Frequency ID and TA PCI NB Cell X2 PRACH

Planning Name Planning Planning Planning Planning Planning
Planning
Frequency Planning
1x1 frequency Planning
✓ LTE system works on the same frequency band
✓ Frequency bandwidth utilizing is high
X Interference occurs between the UEs on the edge of a cell
(use same resource)

1x3 frequency Planning

✓ LTE system works on the three frequency band
X Frequency bandwidth utilizing is Low
✓ Interference can be decreased
(the three sector of one site working on three different frequency band)
Frequency Planning

Example at Band 40 TDD

https://www.cellmapper.net/arfcn
NR-ARFCN Calculation
• The relation between the NR-ARFCN NREF and the RF reference frequency FREF in MHz for the downlink and uplink
is given by the following equation:

FREF = FREF-Offs + ΔFraster (NREF – NREF-Offs)

where FREF-Offs and NRef-Offs are given in below (Table 5.4.2.1-1 in 3GPP TS 38.104), and ΔFGlobal could be used as ΔFraster

Frequency range ΔFGlobal FREF-Offs [MHz] NREF-Offs Range of NREF

0 – 3000 MHz 5 kHz 0 MHz 0 0 – 599999

3000 – 24250 MHz 15 kHz 3000 MHz 600000 600000 – 2016666

24250 – 100000 MHz 60 kHz 24250 MHz 2016667 2016667 – 3279167

• ΔFRaster is the channel raster granularity, which may be equal to or larger than ΔFGlobal.
-- The channel raster for each operating band is recommended as below (Section 4.3.1.3 in TR38.817-01)
FR1 FR2
Bands
Sub2.4G 2.6G~6G 24.25G~52.6G
Channel raster 100kHz 15kHz 60kHz

160
 PCI
PCI
Planning
Planning
How to Distinguish Between Different Cells? (1)

• 504 possible reference signals:

• → 3 various orthogonal sequences – mapped to the physical layer cell ID

• → 168 various pseudo-random sequences – mapped to the cell ID groups

• → 168 x 3 = 504 sequences in total

• → subject to network planning

UE
eNodeB eNodeB
PCI Planning - Introduction
Physical Cell identification and Global Cell ID identification

Physical Layer Cell ID (PCI)

– The sequence to generate the Reference Signal depends upon the PCI
– Short repetition cycle of 1 ms
– Limited to 504 values so not unique
– Careful assignment needed because a UE shall never receive the same value from
2 different cells

Global Cell ID (ECGI)

• E-UTRAN Cell Global identifier

• Part of SIB 1
• SIB 1 is sent once every 20ms
• Unique in the network: constructed from MCC, MNC en E-UTRAN Cell Identifier
ECGI ( E-UTRAN Cell Global Identifier) is used to identify cells globally. It can change (if necessary) once every 80ms but then it is
repeated 3 times before it can be changed again
PCI Plan Sample
Sector 1 Sector 2 Sector 3
SSS/PSS 0 1 2 Allocation For Border East

3 4 5
1 - 140 Macro (General)

….

….

….
420 421 422
333 334 335
Border Area
111 - 125
….

….

….
WEST/NORTH
375 376 377 Border West
378 379 380
Border Area
126 - 140
….

….

….
EAST/SOUTH
420 421 422
423 424 425
141 - 160 Indoor (General) Id = 0 Id = 6
….

….

….
480 481 482
Id = 2 Id = 8
483 484 485
161 - 167 Spare
….

….

….

501 502 503

Id = 1 Id = 7
Id = 3 Id = 9
Id = 5 Id = 11

Id = 4 Id = 10
PCI Conflict
PCI conflict is classified into PCI collision and PCI confusion
PCI Collision
• A PCI collision occurs between two or more intra-frequency cells that use an
identical PCI but are insufficiently isolated.

• In this case, UEs in the overlapping area of the two cells cannot implement
signal synchronization or decoding.

A PCI confusion occurs between a detected cell and a neighboring cell if the two cells
have the same frequency and PCI and if the reference signal received power (RSRP) of
PCI Confusion the two cells reaches the handover threshold.
The PCI confusion may lead to UE handover failures or service drops.

Case :
eNodeB mistakenly considers that the detected cell is cell C and then initiates a
handover to cell C. If the spot that the UE is on is not covered by cell C but cell B, a
handover failure may occur.
If two or more neighboring cells of a cell have the same frequency and PCI, there is a PCI
conflict between these neighboring cells
PCI Mod 3 –Reference Signal
1 Antenna Port

RS pattern for different No. of RS per Ant port No. of RS for all Ant
No. of Antenna No. of RS for all Ant ports in
Antenna configuration port
per RB within one ports per RB within
all RBs within one Symbol
Symbol one Symbol

1 2 2 2* Total No. of RB
2 2 4 4* Total No. of RB
4 2 4 4* Total No. of RB
RE
2 Antenna ports

No RS transmit ⚫ For 4*4 MIMO, the RS of Antenna 3, 4 are transmitted on OFDM

for this antenna port
symbols different to that of Antenna 1, 2
RS transmitted
or this antenna port
4 Antenna ports

R1: RS transmitted by ant 1

R2: RS transmitted by ant 2
R3: RS transmitted by ant 3
R4: RS transmitted by ant 4

Antenna Port 0 Antenna Port 1 Antenna Port 2 Antenna Port 3

PCI Mod 3 – RS shift among neighbor cells
• Frequency domain location of the RS is determined by value of PCI mod 3
• If RS is shifted, then it will help for better performance under low load

RS location vs PCI mod 3:

How to Plan PCI manually
Assume there is a new site insert into current LTE
2 0
1
network
It is recommended to plan PCI after neighbor
planning.
Step 1. Mark the PCI Mod 3 results of existing cells
on the map.
0 Step 2. Decide the PCI Mod 3 result for the new site
1 on the map. Try the best to avoid same result cover
2 2
0
same area.
1
1 Step 3. Choose un-used PCI for the new site
3 0
5 2 0 following the PCI mod 3 result. New PCI shall not
2
1 same to any neighbor cell.
4 1 Step 4. Check the PCI mod 30 result with
neighboring cell.
2 0

Note: Please use PowerPoint “Slide Show” mode to see the animation to play the steps.
Conclusion PCI Planning
Automatic PCI allocation process
5G PCI Planning
 Definition of PCI 5G supports 1008 unique PCIs and each NR cell needs to be allocated a PCI:
cell
N ID = 3 N ID
(1)
+ N ID
(2) (1)
N ID = {0 ~ 335} N ID(2)
= {0,1.2}

 Comparison between LTE and 5G PCIs

Sequence LTE 5G NR Differences and Impacts
• LTE uses the ZC sequence. The correlation
is relatively poor. The PCI mod 3 of
(2) (2)
• The main synchronization signal uses N ID • The main synchronization signal uses N ID neighboring cells should be staggered.
Synchronization
based on the ZC sequence. The sequence based on the m sequence. The sequence • 5G uses the m sequence. The correlation
signal
length is 62. length is 127. is relatively good. Whether the PCI mod 3
of neighboring cells is staggered slightly
affects the cell detection time.
• 5G has no CRS.
• 5G has DMRS for PBCH.
• If the PCI Mod 4 of the neighboring cell
• CRS resource locations are determined by
is different, the PBCH DMRS of the
the PCI mode 3. • Resource locations of DMRS for PBCH are
neighboring cell can be staggered, but
Downlink RS determined by the value of the PCI mode 4.
the PBCH DMRS is interfered by the
SSB of the neighboring cell.
• Therefore, whether PCI mod 4 is
staggered does not affect the
performance of PBCH DMRS.
Overall 5G PCI Planning Principles
5G PCI planning mainly complies with the following principles:

Mandatory or
No. Description Remarks
Not
Adjacent intra-frequency cells cannot use the
1 Mandatory The synchronization and handover are affected.
same PCI.
In the neighboring cell list of the source cell,
The handover is affected, especially when the UE does not
2 cells with the same frequency cannot use the Mandatory
support CGI reporting.
same PCI.

The PCI Mod3 of neighboring cells is staggered to give play to

The PCI Mod 3 of neighboring cells should be the performance of the interference randomization algorithm.
3 Best effort
staggered. In NR:LTE=1:1 site deployment with the same azimuth, the PCI
Mod3 of LTE can be used a reference.

The PCI Mod 30 of neighboring cells should

4 Best effort The demodulation performance of uplink signals is improved.
be staggered.
 PRACH
Planning
Intra-Cell Interference
How can multiple terminals perform
random access attempt at the same time
without collision?

eNodeB Solution ?

64 different orthogonal Preambles available in

each cell obtained by cyclic shift of a Zadoff-
UE UE Chu sequence
1 UE 3 If however collision is happening (2 UEs
2 using the same preamble) -> contention
resolution process
Physical Random Acces Channel (PRACH)
PRACH
• UE sends the preamble to the network on PRACH:
• PRACH occupies 6 resource blocks (of 180 kHz) in a
subframe (or set of consecutive subframes) reserved
for sending random access preamble to the network.
• PRACH reserved PRBs cannot be used by PUSCH i.e.
they are out of scope for scheduling for data
transmission
• Within 1 ms subframe, PRACH divided into Cyclic
Prefix, Preamble and Guard that length is depend on
preamble format as below
Multiplexing of PRACH with PUSCH and PUCCH
PRACH Location
PRACH slot
• The location of those resource
Duration( e.g. 1ms)
blocks is dynamically defined by 2
RRC Layer Parameters (PRACH
PUCCH Configuration Index and PRACH
Frequency offset). The UE may
PRACH learn the configuration from the
Total UL Bandwidth

PRACH bandwidth PRACH system information(SIB2)

(6 PRBs)

PUSCH
PRACH slot period

PUCCH
Time

➢ UL PRACH is orthogonal with the data in PUCCH and PUSCH (reserved

resources)
 PRACH Planning
◆ Step 1: Determine Ncs value by the cell radius. (E.g. Assume the cell
radius is 35 km, take Ncs value 279)
◆ Step 2: The value of 839/279 is rounded down to 3, that is each index
should generate 3 preamble sequences. to generate 64 preamble
sequences 22 (64/3) root sequence indexes are required
◆ Step 3: The number of available root sequence indexes is 838/22=38
(0, 22, 44,…,22*n,…, 814)
◆ Step 4: The available root sequence indexes are assigned to cells. The
reuse distance shall be as far as possible
PRACH Planning Exercise

• There are 64 PRACH preambles in each LTE cell for Random Access. It is for users randomly selects a preamble
sequence to establish initial connection.
• Preambles are generated from root sequence (Zadoff-Chu sequence) and its cyclic shift
• 838 root sequences are defined by 3GPP with length 839
– For example: for Cyclic Shift step 76, so-call Ncs = 76
• Each root sequence can generate Rounddown(839/76) = 11 sequences
• To Generate 64 sequences, number of root sequences needed = Roundup(64/11) = 6
• So available root sequences = Rounddown (838/6) = 139 (Index 0, 6, 12, 18, …)
• Root sequence needs to be reuse in the network
• Unlike UMTS, there isn’t Cell ID related scramble code used for PRACH in LTE system, collision may occur if same
root sequence is planned for PRACH among nearby cells.
• Thus, we need to plan PRACH root sequence.
Automatic PRACH RSI Planning
5G PRACH Root Sequence Planning
 Frequency Planning Principles
• Input conditions: timeslot assignment/preamble
format/PUSCH_SCS/RA_SCS • For the short format C2, when the cell radius is relatively large, it is difficult to ensure
that neighboring cells use different ZC root sequences.
• Output: Ncs values with different cell radius, start position of root
• The PRACH frequency-domain start position can be adjusted to stagger the preambles
sequence, start frequency offset of different cells on different frequencies. This avoids preamble false detection and
 Planning Principles access problems caused by the use of the same PRACH ZC root in neighboring cells.

Step 1: Calculate Ncs based on the cell radius. N CS .TS  TRTD + TMD + TAdsch
Preamble RA-SCS TRTD (us) TMD (us)
TS (us） TAdsch (us)
Format （kHz）
C2 15 1000/RA- 20/3*Radius 4.69/SCS*15 0
SCS/139
Format 0 1.25 1000/RA- 20/3*Radius 6.2 2
SCS/839

Step 2: Query the Ncs value (larger than that in step 1) in the table
defined in the 3GPP protocol.
Step 3: Calculate the number of preamble sequences generated using
the Ncs for a root sequence.
Num_Preamble = floor [(139 or 839)/Ncs]  Planning Methods
Step 4: Calculate the number of root sequences required by a cell. • The GenexCLoud supports offline planning of 5G PRACH root sequences. Format 0
Num_root = ceiling (64/Num_Preamble) and format C2 are supported, and frequency planning is selected at the same time.
Step 5: Group the total ZC root sequences based on the number of ZC • The following table lists the preamble and cell radius supported by each frame structure.
root sequences required by NR, and calculate the number of groups of Preamble Format RA-SCS Frequency Band Subframe Configuration PRB Cell Radius
ZC root sequences.
C2 60 kHz Above-6 GHz DDDSU (4:1) 6 ≤ 2.4 km
Num_Group = (138 or 838)/Num_root
Step 6: Allocate a group of PRACH ZC root sequences to NR cells. DDDSU (4:1)
C2 15 kHz Sub-6 GHz DDDSUDDSUU (7:3) 6 ≤ 9.65 km
Ensure that: DDDDDDDSUU (8:2)
• The ZC root sequences of neighboring cells with the same frequency
DDDSUDDSUU (7:3)
and PRACH Scs are different. 0 1.25 kHz Sub-6 GHz 3 ≤ 14.5 km
DDDDDDDSUU (8:2)
• The reuse isolation of the PRACH ZC root is as large as possible.
• Note: In the uplink and downlink decoupling scenario, the PRACH ZC root of the SUL cell
needs to be planned separately.
Neighbor
Planning
Neighbor Cell Planning
• LTE Network require quick hard handover, so the Neighboring cell Planning is very important

• LTE Neighboring cell planning content : Intra-Freq Neighboring cell, Inter-freq neighboring cell, Inter-RAT
neighboring Cell

• LTE neighboring cell Planning principle :

• Geographically adjacent cell are used as neighboring cell
• in common scenario, bidirectional neighboring relationship is configured
• The distance between eNB is small (0.3 – 1km ) in urban areas, and therefore a large number of neighboring cell
are recommended
• If the adjacent cell of a cell in front of a lake, sea, or a wide road is also in front of the lake, sea or a wide road,
the adjacent cell is configured as its neighboring cell.
SON ANR
Delete neighbor
relation
UE measurement

Establish neighbor Add new neighbor

relation relation

Configured site New site Deleted site

◼ There are many functions in LTE SON, ANR （Automatic Neighbour

Relation) is most useful, can reduce the optimization cost.
◼ ANR can detect missing Neighbor, add and delete neighbor
automatically
Neighboring Cell Planning

The method of LTE neighbor cell planning is similar to that of GSM/UMTS

– For L->L Intra-Freq and Inter-Freq scenario, up to 256 neighbors can be configured respectively. For L->U Inter-RAT
scenario, up to 64 neighbors can be configured for all UMTS neighbors.

If all the UE support the ANR, then no need to plan neighbor

ANR is a self-optimization feature that belong to SON. Based on neighbor relations, ANR is classified into intra-RAT ANR
and inter-RAT ANR
ANR function includes automatic missing neighboring cells detection, PCI conflict detection, abnormal neighboring cell
coverage query and analyzes neighbor relations.
Neighbor Cell Planning
• The method of LTE neighbor cell planning is similar to neighbor planning of GSM/WCDMA/CDMA. Currently, the
planning method and tool for LTE are available.
• The configuration is different from GSM/WCDMA/CDMA . There is no BSC/RNC in the LTE system. When an eNB cell
is configured as neighbor cells of other eNBs, external cells must be added first, which is similar to the scenario
where inter-BSC/RNC neighbor cells are configured on the BSC. That is, neighbor cells can be configured only after
the corresponding cell information is added.
Site A
A1 Neighbor Cell List
A3
(NCL)
Site B
B3 B1 Source Target
A2
A B1
A B2
B2
A B3
B A1
Site A B A2
A1 B A3
A3
Site B
B3 B1
A2

B2
Overall 5G Neighboring Cell Planning Principles
⚫ The principle of planning 5G neighboring cells is the same as the principle of planning 4G
neighboring cells——Adjacent cells need to be planned as neighboring cells.
⚫ In NSA and SA networking scenarios of 5G, the following three types of neighboring cell planning
are required.

Source Cell Target Cell Function of Neighboring Cells

• Addition of NR secondary carriers on the LTE network in NSA DC

LTE NR
• LTE redirection to NR

NR (intra-frequency
• NR intra-RAT mobility
NR and inter-
• The PCC and SCC for CA are inter-frequency neighboring cells.
frequency)

In SA networking, when the NR coverage is poor, UEs need to move to

NR LTE
neighboring LTE cells.
Massive MIMO
Introduction
MIMO Concept
4 × 4 MIMO increases the speed by 50% compared to 2 × 2 MIMO
With MIMO

Without MIMO

4x4 MIM is like adding

highway on top of a
highway
How 4x4 MIMO Improve capacity and coverage

189
MIMO Introduction

190
MIMO Techniques Overview

191
Rank Indicator

This attribute gives the Rank Indicator measured by the UE. The UE periodically reports
the Rank Indicator and this information is used by the eNode B to determine how many
transport blocks the UE can receive per transmission time interval.
Transmission Mode
MIMO
MIMO is developed to provide doubled and more spectral efficiency. As an extension of singlei nput
single-output (SISO), MIMO uses multiple antennas at the transmitter and/or receiver in
combination with some signal processing techniques. Generally speaking, single-input multiple output
(SIMO), multiple-input single-output (MISO), and beamforming also belong to the
MIMO category.
MIMO Cont’d
MIMO Concept

• Supported 3GPP Transmission Modes: PDSCH

• TM1, TM2, TM3,TM4, PDCCH
CRS

CQI
DL
PMI*
feedback
Rank 0 1 2 3 4 5 6 0 1 2 3 4 5 6

UL • PDSCH channel estimation based on common reference

feedback signals (CRS) – ports 0..3
CRS

• Closed loop precoding based on CRS, reported by PMI

• CQI report based on CRS

*PMI signaled with MCS Note: This example shows CRS for 2 TX antenna ports. 3GPP specifies CRS for up to
Closed Loop operation PMI* 4 TX antenna ports. See 3GPP 36.211 6.10.1 for details
(TM4) Rank
MIMO Concept

• Supported 3GPP Transmission Modes: PDSCH

• TM7 PDCCH
• Single Stream Beamforming (LTE493) CRS
DRS

DL
feedback
CQI
0 1 2 3 4 5 6 0 1 2 3 4 5 6

• PDSCH channel estimation based on dedicated reference signals (DRS)

– port 5
DRS
CRS
SRS

• CQI report based on CRS

• Open loop, non-codebook precoding (beamforming)
• Channel feedback using sounding reference signals (SRS) and UL/DL
reciprocity in TDD LTE
UL MCS
feedback Note: This example shows CRS for 2 TX antenna ports. 3GPP specifies CRS for up to
4 TX antenna ports. See 3GPP 36.211 6.10.1 for details
MIMO Concept

• Supported 3GPP Transmission Modes: PDSCH

• TM8 PDCCH
• Dual Stream Beamforming (LTE541) CRS
DM-RS

DL
CQI
feedback
PMI
Rank 0 1 2 3 4 5 6 0 1 2 3 4 5 6

• PDSCH channel estimation based on demodulation reference signals

(DM-RS) – ports 7..14 (up to 8 layers)
DM-RS
CRS
SRS

• CQI report based on CRS

• Open loop, non-codebook precoding (beamforming)
• Channel feedback using sounding reference signals (SRS) and UL/DL
MCS reciprocity in TDD LTE
UL PMI
Note: This example shows CRS and DM-RS for 2 TX antenna ports. 3GPP specifies
feedback Rank
CRS for up to 4 TX antenna ports and DM-RS for up to 8 antenna ports. See 3GPP
36.211 6.10.1, 6.10.3.2 for details
MIMO Concept

• Supported 3GPP Transmission Modes: PDSCH

• TM9 PDCCH
CRS
DM-RS
CSI-RS

DL
CQI
feedback
PMI
Rank 0 1 2 3 4 5 6 0 1 2 3 4 5 6

• PDSCH channel estimation based on demodulation reference signals

DM-RS

(DM-RS) – ports 7..14 (up to 8 layers)

CSI-RS
CRS

• CQI report based on Channel State Information Reference Signals

(CSI-RS) – ports 15..22
• Closed loop precoding based on CSI-RS, reported by PMI
MCS • CSI-RS is configured to each Rel10 UE via RRC reconfiguration
UL Rank
Note: This example shows CRS and DM-RS for 2 TX antenna ports. 3GPP specifies
feedback CRS for up to 4 TX antenna ports and DM-RS for up to 8 antenna ports. See 3GPP
36.211 6.10.1, 6.10.3.2 for details
5G Massive MIMO
5G Massive MIMO
5G Massive MIMO
5G Massive MIMO
• Basic MIMO

Downlink Beamforming Procedure

Weighted signals are transmitted in narrow beams
directed towards target UEs. Figure 4-6 shows the overall
beamforming procedure.
1.Channel Calibration
2.Weight Calculation
3.Weighting
4.Beamforming Implementation
5.Demodulation
5G Massive MIMO
➢ Beam Management

Default Scenario
5G Massive MIMO
➢ Beam Management

Non-Default Scenario
5G Massive MIMO
➢ Beam Management
Non-Default Scenario
5G Massive MIMO
➢ Beam Management
Non-Default Scenario
5G Massive MIMO
➢ Beam Management
5G Massive MIMO
➢ Beam Management