5G - 201905 - HUA - Version - 1.6

5G NR Air Interface with focus on Non-
Standalone Architecture
© Widermind AB Vivacom Sofia 05-19 1

Contents
• Architecture • DL Physical Channels
• EN-DC • Reference Signal Types
• UL Power Limitations and Coverage Extensions • UL Physical Channels
• DL Power Configuration • Transport Network configuration
• Frequency Band • Synchronization
• Bandwidth
• Bandwidth Part
• Numerology, Mixed Numerology
• Frame Structure

5G NR Use Cases

5G NR Use Cases
FWA - Fixed Wireless:
One of the top 5G use cases will be fixed wireless access. Some experts believe that mobile 5G will be
several years out. Fixed wireless will provide Internet access to homes using wireless network
technology rather than fixed lines. It will use 5G concepts such as millimeter wave (mmWave)
spectrum and beamforming to bolster wireless broadband services.
eMBB - Enhanced Mobile Broadband:
The 5G standard promises to usher in the next era of immersive and cloud-connected
experiences with faster, more uniform data rates at lower latency and lower cost per bit. The 5G
standard will take mobile computing performance to the next level with high-speed, always-on,
always-connected Internet links with real-time responsiveness. The goal is to reach up to 10 G/ps
peak throughput and 1 G/ps throughput in high mobility. This category includes virtual reality (VR)
and augmented reality (AR) experiences.
mMTC - Massive IoT (or Massive Machine-Type-Communications):
One of the most anticipated 5G use cases is the ability to seamlessly connect embedded sensors in
virtually everything. The industry foresees huge numbers — as many as 50 billion — of potential IoT
devices in service by 2020. Industrial IoT is one area where 5G will play a major role, from smart cities
to asset tracking, to smart utilities, to agriculture.
URLLC - Ultra-Reliable Low-Latency Communications:
This category includes new services that will transform industries with ultra-reliable/available low-
latency links, such as remote control of critical infrastructure, and (popularly) self-driving vehicles.
The level of reliability and latency will be vital to smart-grid control, industrial automation, robotics,
drone control and coordination, and so on.
Enhanced Event Experience:
The enhanced event aspect of the 5G experience promises to offer close-to-the-action VR videos as
being part of a given performance. This use case takes advantage of 5G to produce an ultra-high-
fidelity media experience. The market potential for this use case is high, including overall increased
revenue for venue owners.
Low Latency in LTE
• 4 features were standardised in LTE for LL:
– Shorter processing time (n+3)
– Short TTI (3 or 4 ODFM symbols)
– Pre-allocation with SPS (semi persistent scheduling)
– No data to UL if pre-allocation applied for UE
• Vendors will have them in 2019-2020
• Chipset manufacturers no announcements

Introduction to New Radio
NR
Frame Control
Coding Waveform Native MIMO Multi-access
Structure Channel
Wide BW CRS-free, use

LDPC CP-OFDM Beam mgmt NOMA
(scalable SCS) DMRS
Short TTI
Polar DFT-S-OFDM Analog beam Grant Free
(latency)
F-OFDM
Flexible TDD Digital beam
(less guard)
Self containing SCS – SubCarrier Spacing

(fast feedback) Hybrid beam
LDPC – Low Density Parity Check
F-OFDM – Filtered OFDM
CP-OFDM – Cyclic Prefix OFDM
DFT-S-OFDM – Discrete Fourier Transform-spread-
OFDM
NOMA – Non Orthogonal Multiple Access

NR Physical Layer Design Principles
Spectrum flexibility:
• Flexible bandwidth support up to 100 MHz (FR1)
Low latency configurations:

• ShorterTTI, shorter symbol time,
• flexible allocation of resources in time domain
Future-proof design:
• Reserved Resources Concept
• Clean subframe structure for future networks
Ultra-lean design:
• Minimize any transmission not directly related to user data transmission, energy saving
• No cell-specific à Cell-less network
Beam-centric design:
• Beam management support
• Interworking across spectrum bands: interworking with LTE
3GPP

Beginnings of 5G NR
Early Drop Main Drop Late Drop
• Despite LTE being a very capable technology,
• Addresses the most urgent • For standalone 5G • For accelerated
there are requirements (mMTC, URLLC) not deployment needs for eMBB migration
• Contains full standalone
possible to meet, neither with LTE Advanced • Uses LTE anchor with 5G NR in
5G support with 5G Core • Contains specs for all
Dual Connectivity configuration
releases potential migration
• Accelerated specification to
options
• In order to meet these new requirements, 3GPP ensure a single global ecosystem
initialed the development of a new radio-access
technology known as New Radio (NR)
• A first workshop setting scope was held in 2015,
and technical work began in the spring of 2016
• The first version of the NR specification was
available at the end of 2017 – Non-Standalone
• Standalone specification was finished in June
2018 with Release 15 (Main Drop).
Built on a top of LTE

network
Some Change Requests (CR) were
introduced in Sep of 2018, which are
not backward compatible with June
specifications

3GPP Rel 16 and beyond
Release 16 started a studies on various 5G NR topics:
• Multimedia priority service
• V2X application layer services
• 5G satellite access
• terminal positioning and localization
• communication in vertical domains
• network automation
• novel radio techniques
• security
• codecs and streaming services
• network slicing and IoT
ASN.1 - Abstract Syntax Notation One

Protocol developers define data structures in ASN.1 modules, which are generally
a section of a broader standards document written in the ASN.1 language. Because
the language is both human-readable and machine-readable, modules can be
automatically turned into libraries that process their data structures, using an
ASN.1 compiler.

Key capabilities of IMT-2020
• Figure illustrates key capabilities of IMT-2020
• Numbers are partly absolute, partly relative to the corresponding capabilities of IMT-Advanced (4G)
• Minimum performance IMT-2020 requirements:
Requirements
Peak data rate DL: 20 Gb/s UL: 10 Gb/s
Peak spectral efficiency DL: 30 b/s/Hz UL: 10 bit/s/Hz
User-experienced data rate DL: 100 Mb/s UL: 50 Mb/s
Fifth percentile user spectral efficiency 3x IMT-Advanced
Area traffic capacity 10Mb/s/m2
User plane latency 4 ms for eMBB, 1 ms for URLLC

Key Capabilities of IMT-2020

3GPP Organization
Dealing with fixed

interfaces, e.g. between
nodes and RAN
dealing with the radio

frequency (RF) and radio
resource management
(RRM) performance
requirements

3GPP Technical Specification Series 37 and Series 38
NR standard can be can be studied from two different series
• Series 37:
– Aspects relating to multiple radio access technologies, i.e. Dual Connectivity à NSA
– TS 37.340 NR; Multi-connectivity; Overall description; Stage-2
– TR 37.863 Dual connectivity (DC) band combinations of LTE 1DL/1UL + one NR band
• Series 38:
– Radio aspects for NR
– TS 38.211 NR; Physical channels and modulation
– TS 38.212 NR; Multiplexing and channel coding
– TS 38.213 NR; Physical layer procedures for control
– TS 38.214 NR; Physical layer procedures for data
– TS 38.331 NR; Radio Resource Control (RRC); Protocol specification

Architecture

Terminology
Radio Access
• E-UTRA – a name of LTE radio access
• NR – a name of New Radio access
Radio Access Network

• E-UTRAN – a RAN that connects to the EPC
• NG-RAN a RAN that connects to 5GC
Core Network
• EPC – Evolved Packet Core for 4G
• 5GC – 5 Generation Core Network

Key Principles and Concept for 5GC
Some key principles and concept are to:
• Separate User Plane (UP) functions from the Control Plane (CP) functions
• Modularize the function design (network slicing)
• Direct interaction of Network Functions
• Support "stateless" NFs
• Minimize dependencies AN – CN, converged access-agnostic core
• Unified authentication framework
• Capability exposure
• Concurrent access to local and centralized services
• Roaming with Home routed traffic as well as Local breakout traffic

Standalone Architecture with 5G CN
• An architecture enables deployment with Network Function Virtualization and Software Defined Networking.
• Separation of User Plane (UP) functions from Control Plane (CP), allows independent scalability, evolution and flexible deployment
• Function design based on Modules, allows flexible and efficient network slicing
• AUSF - Authentication Server Function

Non-roaming architecture
(in service based representation) • AMF - Access and Mobility Management Function
• DN - Data Network, e.g. operator services,
Internet access or 3rd party services
Nnssf Nnef Nnrf Npcf Nudm Naf • NEF - Network Exposure Function
• NRF - Network Repository Function
Nausf Namf Nsmf
• NSSF - Network Slice Selection Function
MME = AMF • PCF - Policy Control Function
PGW-C = SMF
PGW-U = UPF N2 N4
• SMF - Session Management Function
N1
HSS = UDM • UDM - Unified Data Management

N3 N6
• UPF - User Plane Function
N9
3GPP 23.501 Figure 4.2.3-1 • AF - Application Function
• UE - User Equipment
• (R)AN - (Radio) Access Network

5G CN in Reference Point Representation
• A reference point representation, shows the interaction exist between the NF services in the network functions
described by point-to-point reference point (e.g. N11) between any two network functions
Non-roaming architecture
(in reference point representation)
N22 N12 N8 N10
N11 N7 N5
N14 N15
N1 N2 N4
MME = AMF
PGW-C = SMF
PGW-U = UPF N3 N6
HSS = UDM
N9
3GPP 23.501 Figure 4.2.3-2

5G NR SA Architecture and Interfaces
• Similar to LTE
• CU/DU split will be standardized in LTE as well, to enable closer interoperability and common platform deployment.

E2e Mixed Architecture with 5GC
Complex to Integrate
• LTE connected over S1 interface towards EPC
Difficult for maintenance
• NR connected over Nx interfaces to 5GC and inter vendor setup
MME N6a
HSS
N26
S11
N22 N12 N8 N10
SGW S5-C
S1-C
S5-U N11 PGW-C N7 PCRF N5
S1-U
N15
N1 N2 N4
E-UTRAN Uu N3 PGW-U N6
N9
3GPP 23.501
MME = AMF
PGW-C = SMF
PGW-U = UPF
HSS = UDM

E2E Mixed Architecture with 5GC
Complex to Integrate
• LTE connected over S1 interface towards EPC
Difficult for maintenance
• NR connected over Nx interfaces to 5GC and inter vendor setup
HSS +
UDM
N10
PCF
S6a
N8
N7
SMF + N15
S5-C PGW-C
N4
UPF +
N11
PGW-U
S5-U
SGW
S11
N26
MME AMF
S1-MME
S1-U U N3 N2
N1
E-UTRAN NG-RAN
MME = AMF
PGW-C = SMF UE UE
PGW-U = UPF 3GPP TS 23.501 Figure 4.3.1-1
HSS = UDM

QoS for 5G-RAN & Network Slicing

QoS Flow/Rules
• AN – Access Network
• UPF – User Plane Function SDF – Service Data Point
3GPP TS 23.501 Figure 5.7.1.5-1

5G-RAN User Plane and Control Plane Protocol Stack
Service Data Application
Protocol (SDAP)
mapping QoS bearers to
radio bearers according to
their quality-of-service
requirements
Packet Data Convergence

Protocol (PDCP)
performs IP header
compression, ciphering, and
integrity protection. It also
handles retransmissions, in-
sequence delivery, and
duplicate removal
Radio-Link Control (RLC)

responsible for
Physical Layer (PHY) Medium-Access Control
segmentation and
handles coding/decoding, (MAC)
retransmission handling
modulation/demodulation, handles multiplexing of
multi-antenna mapping, and logical channels, hybrid-ARQ
other typical physical-layer retransmissions, and
functions scheduling and scheduling-
© Widermind AB Vivacom Sofia 05-19 25 related functions
From LTE QCI to 5QI
5QI Resource Type Default Packet Delay Packet Error Default Maximum Default Example Services
Value Priority Level Budget Rate Data Burst Volume Averaging Window
1 Conversational Voice
20 100 ms 10-2 N/A 2000 ms
2 Conversational Video (Live Streaming)
40 150 ms 10-3 N/A 2000 ms
Real Time Gaming, V2X messages
3 GBR 30 50 ms 10-3 N/A 2000 ms
Electricity distribution – medium voltage, Process automation - monitoring
4 Non-Conversational Video (Buffered Streaming)
50 300 ms 10-6 N/A 2000 ms
Mission Critical user plane Push To Talk voice (e.g., MCPTT)
65 7 75 ms N/A 2000 ms
10-2
66 Non-Mission-Critical user plane Push To Talk voice
20
100 ms N/A 2000 ms
10-2
67 Mission Critical Video user plane
15 100 ms 10-3 N/A 2000 ms
75
5 Non-GBR 10 100 ms 10-6 N/A N/A IMS Signalling
Video (Buffered Streaming)
6 N/A N/A
60 300 ms 10-6 TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.)
Voice,
7 N/A N/A Video (Live Streaming)
70 100 ms 10-3
Interactive Gaming
Video (Buffered Streaming)

8 TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive
80
300 ms 10-6 N/A N/A
9 90 video, etc.)
69 5 60 ms 10-6 N/A N/A Mission Critical delay sensitive signalling (e.g., MC-PTT signalling)
70 Mission Critical Data (e.g. example services are the same as 5QI 6/8/9)
55 200 ms 10-6 N/A N/A
79 65 50 ms 10-2 N/A N/A V2X messages

80 68 10 ms 10-6 N/A N/A Low Latency eMBB applications Augmented Reality
82 Delay Critical GBR 19 10 ms 10-4 255 bytes 2000 ms Discrete Automation (see TS 22.261 [2])
1354 bytes Discrete Automation (see TS 22.261 [2])
83 22 10 ms 10-4 2000 ms
(NOTE 3)
84 24 30 ms
1354 bytes 2000 ms
Intelligent transport systems (see TS 22.261 [2])
10-5
(NOTE 3)
85 21 5 ms 10-5 255 bytes 2000 ms Electricity Distribution- high voltage (see TS 22.261 [2])
UE Identifiers (SA)
5G Subscription Permanent Identifier (SUPI)
• globally unique, allocated to each subscriber in the 5G System and provisioned in the UDM/UDR (e.g. IMSI)
Subscription Concealed Identifier (SUCI)
• one-time use subscription identifier
contains concealed subscription identifier (e.g., MSIN), and cleartext home network identifiers (e.g., MCC and MNC).
• used to privacy protect the SUPI.
Permanent Equipment Identifier (PEI)
• is defined for the 3GPP UE accessing the 5G System (e.g. IMEI)
5G Globally Unique Temporary Identifier (5G-GUTI)
• allocated to the UE that is common to both 3GPP and non-3GPP access
Generic Public Subscription Identifier (GPSI)
• needed for addressing a 3GPP subscription in different data networks outside of the 3GPP system; public identifiers used
both inside and outside of the 3GPP system;
• either MSISDN or External Identifier

Network Slicing Definition
Definition:
• a specific form of virtualization that allows multiple logical networks to run on top of a shared physical network infrastructure
• it provides an end-to-end virtual network encompassing not just networking but compute and storage functions too
Objective:
• to allow a physical mobile network operator to partition its network resources to allow for very different users – tenants
• in example: sharing of a given physical network to simultaneously run IoT, MBB, URLLC, V2X applications, each of which has very different
transmission characteristics
• is to be able to partition the physical network at an end-to-end level to allow optimum grouping of traffic, isolation from other tenants,
and configuring of resources at a macro level
Difference with LTE QoS:
• QCI, DiffServ, VPN and IP Sec have definitely overlap with functionality of network slicing, however new approach allows us to create
lucrative new business opportunities: Power grid communication, Factory network, Concert streaming (temporary lease)

History of Network Slicing in 3GPP
Release 13 Release 14 Release 15
• Dedicated Core Networks (DECOR) • Enhanced DECOR (eDECOR) à • Brand new 5G core network and system
introduced Introduces UE assisted Dedicated Core architecture
• Selection and Redirection of MME based Network selection • One UE can connect to multiple slices
on subscribed UE usage type • UE provisioned with a default Dedicated • AMF (equivalent of MME) is common to
• MME further selects SGW / PGW based Core Network ID (DCN ID) by HPLMN all slices
on UE usage type • Serving Network provides a DCN ID for • Slice identified by Specific Network Slice
• One UE = one UE usage type that PLMN Selection Assistance Information (S-
• No indicator in RRC to let eNB select • UE stores per PLMN DCN ID NSSAI)
right MME • DCN ID carried in RRC • S-NSSAI contains Slice Type and Slide
• All changes are core network centric • eNB selects right MME based on DCN ID Differentiator
• MME selects SGW / PGW based on UE • NSSAI = Set of S-NSSAI
usage type • UE provisioned with a configured NSSAI
• One UE = one DCN ID per PLMN
• All PDN connections of the UE in same • UE provided with allowed NSSAI by
DCN serving PLMN
• UE can be connected upto 8 S-NSSAls
(slices) simultaneously
• Requested NSSAI carried in RRC during
initial access (when 5G-GUTI not
available)
• Selection of NFs based on S-NSSAI
How to Create a Network Slice - Business
• A customer orders a network slice from mobile operator and provides a network requirements, such as: type, capacity,
performance, coverage. The operator generates the network slice according the requirements.
Customer’s GTS info Mobile Network Operator

1. Slice type: URLLC ① Provides network service requirements GST – General Service Template
Transfer of GST to NST
2. Performance: NST – Network Slice Template
⑤ Expose slice management information
Latency 50ms
③ Triggers network
Reliability:
instantiation process
99.99%
3. Capacity:
1000 connections
Transport
4. Functionality: RAN
Cache
Broadcast
Core ④ End-to-end
Network Slice
Management
Parameters
Customer’s UE RAN Transport Core
EDGE computing AMF/SMF/UPF/PCF

EN-DC
E-UTRAN New Radio – Dual Connectivity

Selected Architecture options from 3GPP
Option 3x/7x preferred in NSA Option 2/5 preferred in SA
Option 3 Option 3a Option 3x Option 4 Option 4a

EPC EPC ♣ EPC 5GC 5GC ♣
S1-C S1-U S1-C S1-U S1-U S1-C S1-U S1-U NG-C NG-U NG-U NG-C NG-U
LTE ♣■ NR LTE ■ NR LTE ■ NR ♣ eLTE NR ♣■ eLTE NR ■
Option 7 Option 7a Option 7x Option 2 Option 5

5GC 5GC ♣ 5GC 5GC 5GC
NG-C NG-U NG-C NG-U NG-U NG-C NG-U NG-U NG-C NG-U NG-C NG-U
eLTE ♣■ NR eLTE ■ NR eLTE ■ NR ♣ NR ■ eLTE■

♣ User Plane Split ■ Control Plane Anchor
Standard eUTRA Option 3x Option 7x Option 4 Option 2 Option 5

Option 1 LTE & NR DC • • •
EPC LTE Upgrade • • • •

5GC Deployment • • • •
S1-C S1-U Service readiness
(eMBB/uRLLC/mMTC) • • •
LTE ■

Option 3x Protocol Stack
Option 3x
EPC
S1-C S1-U S1-U
Xn-U
LTE ■ NR ♣
Xn-C
MCGbearer SCG split bearer
XN-u
PDCP NR-PDCP NR-PDCP
RLC RLC NR-RLC NR-RLC
MAC NR-MAC
LTEeNB gNB

Non-Standalone vs. Standalone Architecture
NSA
• was introduced by 3GPP and finished in December 2017 to accelerate time to market
• Deployment scenario Option 3x strongly preferred
• Best solution for non-contiguous NR coverage as full mobility with LTE is supported, i.e.
mobility is managed by LTE, and mobility to 3G and 2G is also controlled by LTE.
• Avoids high effort of 5G core integration into legacy core (ePC)
• Drawback of 3x is that it has to be supported also in future, as long as terminals
requiring it will be in use.
SA
• is a long-term strategy, however first devices will support only NSA with unlikely SW
update to SA, so the NSA architecture will have to be maintained for some time in the
networks.

EN-DC (E-UTRA NR - Dual Connectivity)
• EN-DC (EUTRA-NR Dual Connectivity)
• Limited coverage of 3.X GHz NR requires UE to anchor in a lower band coverage layer for mobility robustness
• En UE is connected to one eNB that acts as a Master Node (MN/MeNB) and one gNB that acts as a Secondary Node (SN/SGNB)
• Control plane signaling is via eNB
• Higher band is only used for throughput boost (primarily DL, but UL also possible)
• Anchor point is at PDCP layer, as that a point where data slit between LTE and NR starts
MME S-GW
• Control plane signaling is via eNB
DRB
B
DR
eNB provides Master Cell

S1-MME
ated
ed
Group (MGC)
at
in
rmin
rm
• The eNB is connected to EPC via the S1

te
te
N
:M
: SN
interface and to the gNB via X2-C and X2-

-U
S1-U
S1
U interface
• The gNB is connected to EPC via the S1-U
NR Uu interface
X2 (DRB) NR cell
gNB gNB provides the Secondary
LTE cell Cell Group (SGC)
eNB LTE Uu (SRB+DRB)

EN-DC Terminology
DC (Dual Connectivity):
A UE in RRC_CONNECTED is configured with Dual Connectivity when configured with Master and Secondary Cell Group
MN (Master Node)
Typically eNB connected to ePC
SN (Secondary Node)
Typically gNB connected to S-GW and eNB through X2 interface
PCell (Primary Cell):
The cell operating on a primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-
establishment procedure, or a cell indicated as primary cell in the handover procedure.
SCell (Secondary Cell):
A cell operating on a secondary frequency, which may be configured once a 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 MGC, 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 term Special Cell refers to the PCell of the MGC or the PSCell of the SCG, otherwise the term Special Cell refers to the
PCell.

NSA Option 3x
• Minimum impact to legacy LTE for UP data split
Option 3x
• Dynamic UP data split in RAN at packet level provide better
performance EPC
• Solution based on dual connectivity, with common Core S1-C S1-U S1-U
network, will allow:
Xn-U
• Mobility robustness considering spotty NR coverage in 3.x LTE ■ NR ♣
Xn-C
GHz band helps overcome propagation challenges with
Supplemental Uplink. ♣ User Plane Split ■ Control Plane Anchor
• Support co-located and non-co-located sites

• UE can only camp on LTE, RACH is on LTE, NR DRB is added
later
• gNB controls only RLC/MAC/PHY layer
• Each vendor sends VoLTE (QCI1 + QCI5) through eNB only

NR Indicator in SIB2
• Network support for EN-DC can be indicated per PLMN in LTE-SIB2
• The information is used by a UE to e.g. display “NR” on the screen
• EN-DC support in SIB2 is configurable per E-UTRAN cell.
SystemInformationBlockType2 ::= SEQUENCE {
…
PLMN-Info-r15 ::= SEQUENCE {
upperLayerIndication-r15 ENUMERATED {true} OPTIONAL -- Need OR
}
…
}
5G_Ind := I AND II AND (III OR IV) Huawei SRAN 15.1

+-NE
where +-eNodeBFunction
I := EN-DC supported (i.e. 5G capable device) +-Cell
II := DCNR has not been restricted by the network +-NsaDcMgmtConfig
III := "upperLayerIndication" received in SIB2 of the serving cell NSA_DC_CAPABILITY_SWITCH = OFF; [ON, OFF]
(IDLE or CONNECTED mode) - in Huawei the upperLayerIndication-r15 can
IV := at least one cell from an NR Secondary Cell Group (SCG) added be independently configured

UE Categories (UE Capability Information)
• In NR UE Capability message, UE radio category is not signaled anymore. Whole concept of “UE Categories” was removed
from specification.
• Max UE data rate is instead calculated by network based on UE signaled capabilities and related formulas.
• Similarly as in LTE, CA band combinations are reported only for requested frequency bands.
UECapabilityInformation ::= SEQUENCE {

rrc-TransactionIdentifier RRC-TransactionIdentifier,
criticalExtensions CHOICE {
ueCapabilityInformation UECapabilityInformation-IEs,
criticalExtensionsFuture SEQUENCE {}
}
}
UECapabilityInformation-IEs ::= SEQUENCE {

ue-CapabilityRAT-ContainerList UE-CapabilityRAT-ContainerList OPTIONAL,
lateNonCriticalExtension OCTET STRING OPTIONAL,

nonCriticalExtension SEQUENCE{} OPTIONAL
}

Split Bearer & Dual Connectivity Data Aggregation
• DL/UL data can be sent either in single bearer S-GW
(either Master Node or Secondary Node), based on
UL/DL radio channel quality. In good radio
MeNB (LTE) SgNB (NR)
conditions NR is used, in poor conditions LTE is
used. (E// calls it Single Leg transmission). App App
DRB: QCI9 (Data)

• While UL and DL switch operates TCP TCP
DRB: QCI5 (IMS Signaling)

independently
RRC IP IP
DRB: QCI 1 (Voice)

SRB: RRC & NAS Signaling
PDCP PDCP
• Dual Connectivity aggregation transmission mode X2
sends DL data in both LTE and NR for higher RLC RLC
DRB: QCI9 (Data)

DRB: QCI9(Data)
throughput. Flow control in both nodes will MAC MAC
guarantee packet order in UE. UL Packet
aggregation is not supported (E//). PHY PHY
Huawei SRAN 15.1

CellQciPara.NsaDcDefaultBearerMode = SCG_SPLIT_BEARER; Split bearer
SCG_SPLIT_BEARER – Option 3 managed by
MCG_SPLIT_BEARER – Option 3x PDCP layer
MCG_BEARER – data is transmitted only on LTE side 40

Huawei Split Bearer and UL/DL Data Steering per QCI
Huawei SRAN 15.1

CellQciPara.NsaDcDefaultBearerMode = SCG_SPLIT_BEARER;
SCG_SPLIT_BEARER – Option 3
MCG_SPLIT_BEARER – Option 3x
This PDCP
MCG_BEARER – data is transmitted only on LTE side “profile” is
assigned to
5G RAN 2.1 In Option 3X:
specific QCI
DL: gNBPdcpParamGroup.DlDataPdcpSplitMode = [MCG_ONLY, SCG_ONLY, SCG_AND_MCG]
UL: gNBPdcpParamGroup.UlDataSplitPrimaryPath = SCG;[MCG, SCG], gNBPdcpParamGroup.UlDataSplitThreshold = ;[0-INFINITY]
UL Data on MGC only:

gNBPdcpParamGroup.UlDataSplitThreshold = INFINITY, gNBPdcpParamGroup.UlDataSplitPrimaryPath = MCG.
UL data on SGN only:
gNBPdcpParamGroup.UlDataSplitThreshold = INFINITY, gNBPdcpParamGroup.UlDataSplitPrimaryPath = SCG
UL data dynamically distributed:
UE’s PDCP buffer ≥ gNBPdcpParamGroup.UlDataSplitThreshold, UL data are sent on both MCG and SCG
UE’s PDCP buffer < gNBPdcpParamGroup.UlDataSplitThreshold, data is transmitted according to the value of
gNBPdcpParamGroup.UlDataSplitPrimaryPath

SGNB Mobility Management
NR Leg Setup
MN terminated SN terminated
MCG DRB Split DRB
Initial Context Setup Release to Idle Mode
NR Leg Release
Initial Context Setup NR Leg Setup NR Leg Release Release to Idle Mode
§ Bearer is set up as § Bearer is reconfigured § Bearer type is § UE is released to IDLE
MN-terminated MCG to an SN-terminated changed to mode
DRB Split DRB MN-terminated MCG § Any resources for the
§ User plane data over § Change of PDCP DRB Split DRB in the eNB
LTE radio only version and security § Change of PDCP and the gNB are
key version released idle Mode
§ Measurement based and security key
setup (B1) or § Triggered by e.g. NR
configuration based RLF,
setup (blind) NR Cell lock

Secondary node Setup procedure
• In NSA, cell search procedure and initial access is triggered in LTE network. Data bearer is setup towards eNB (MeNB)
• SgNB setup can be based on B1 measurement event (optional).
• The LTE Bearer is reconfigured to a Split Bearer
1: LTE only 2: data forwarding 3. split bearer UE MeNB SgNB EPC

LTE SRB DRB NR LTE SRB DRB NR LTE SRB DRB NR
PDCP PDCP PDCP PDCP PDCP PDCP LTE Initial Context Setup + B1 Measurement
Event configuration (optional)
RLC RLC RLC X2 RLC RLC X2 RLC
MAC MAC MAC MAC MAC MAC B1 Measurement
Report
PHY PHY PHY PHY PHY PHY
NR Secondary Node Setup
• Signaling is handled through LTE SBR Bearer (RRC Signaling)

Different Mobility Scenarios
X2
NR cell
X2
eNB2
NR cell
gNB2 LTE cell
X2
gNB1
eNB1
LTE cell MeNB HO w/o SgNB Release

SgNB change
SgNB Change
LTE Initial Access SgNB Addition

SGNB addition procedure (TS 37.340)
UE MeNB SgNB S-GW MME
LTE eNB sends measurement RRC Conn Procedure in LTE LTE eNB initiate SCG addition
configuration requesting UE to procedure to NR gNB (carrying
measure DL RSRP & Beam ID of
B1 Measurement Configuration
DL RSRP & Beam ID of NR cell),
NR cell according to B1 event and adds NR cell as SCG
B1 Measurement Report
1. SgNB Addition Request
If DL RSRP satisfied the B1
threshold, UE sends
NR Cell selects UL carrier for UE
measurement report of NR cell
by DL RSRP carried from LTE eNB
to LTE eNB
(NR UL or NR SUL), and allocate
preamble for UE by Beam ID
LTE eNB sends NSA DC and UL & 2. SgNB Addition Request ACK
DL decoupling information to UE 3. RRC Connection Reconfiguration
by RRC re-configuration NR gNB addition to LTE eNB
message 4. RRC Conn Recon Complete starts with message SCG
5. SgNB Reconfiguration Complete addition success, and carries
UL carrier selection & UE
6. NR Random Access preamble
Procedure
7. SN Status Transfer
8. Data Forwarding
Path Update Procedure 9. E-RAB Modification Indicator

10. Bearer Modification
11. End Marker
12. E-RAB Modification Confirmation

SGNB Removal Procedure (TS 37.340)
Initiated by MN or SN. It does not necessarily need to involve signalling towards the UE (in case of the RRC connection
re-establishment due to Radio Link Failure in MN)

If also data forwarding is MN initiated
requested, the MN MeNB Release Request
provides data forwarding SN initiated
addresses to the SN MeNB Release Request ACK SgNB Release Required
OR SgNB Release Confirm

RRC Connection Reconfiguration
The SN sends the Secondary
RRC Conn Recon Complete RAT Data Volume Report
SN Status Transfer message to the MN and
includes the data volumes
Data Forwarding delivered to the UE over the
NR radio for the related E-
Secondary RAT Data Volume Report RABs.
Path Update Procedure E-RAB Modification Indicator

Bearer Modification
End Marker
E-RAB Modification Confirmation
UE Context Release

SgNB Change Procedure (TS 37.340)
UE MeNB S-SgNB T-SgNB S-GW MME
SgNB Addition Request
SgNB Addition Request ACK
SgNB Release Request
SgNB Release Request ACK
RRC Conn Reconfig
RRC Conn Reconfig CMP
SgNB Reconfiguration CMP
NR Random Access Procedure
SN Status Transfer
SN Status Transfer
Data Forwarding
Secondary RAT Data Volume

Report
E-RAB Modification Indicator
Bearer Modification
End Marker
New path
E-RAB Modification Confirmation
UE Context Release

MeNB Change Procedure (TS 37.340 10.8)
UE S-MeNB SgNB T-MeNB S-GW MME
1. Handover Request
2. Handover Request ACK
3a. SgNB Release Request
3b. SgNB Release Request ACK
4. RRC Conn Reconfig
5. LTE Random Access
Procedure
6. RRC Conn Reconfig CMP
7a. SN Status Transfer
7b. SN Status Transfer
8. Data Forwarding
9a. Secondary RAT Data Volume

Report
9b. Secondary RAT Report
10. Path Switch Request
11. Bearer Modification
12. End Marker
13. New path

14. Part Switch Request ACK
15. UE Context Release
16. UE Context Release

UE Release to Idle with EN-DC
• Initiated by MeNB upon Inactivity timer expiry or RLF.
UE Context Release Request
UE Context Release Command
MeNB Release Request

MeNB Release Request ACK
The SN sends the
Secondary RAT Data
Suspend DRB Volume Report message to
SN Status Transfer the MN and includes the
data volumes delivered to
Secondary RAT Data Volume the UE over the NR radio
Report for the related E-RABs.
UE Context Release
Release Resources
RRC Connection Release
UE Context Release Confirm
Release Resources

Signaling between SgNB and UE – SRB3
• Decision to establish SRB3 is taken by SN (SgNB), which then provides SRB3 configuration using an SN RRC message. SRB3
establishment and release can be done at Secondary Node Addition and Secondary Node Change
• SRB3 may be used to send
– SN RRC Reconfiguration
– SN RRC Reconfiguration Complete
– SN Measurement Report messages
• SRB3 is used only in the procedures where the MN is not involved

UL Power Limitations

Dynamic UL resource coordination for NSA (MRDC Parameters)
• MRDC-Parameters (signalled per band combination)
• dynamicPowerSharing Multi Radio Dual Connectivity
Indicated wheter the UE supports dynamic EN-DC power sharing or not
If the UE supports this cabability, it will dynamically share the power between NR and LTE if P_LTE+P_NR > Pcmax. Alternatively, if the UE does not
support dynamic power sharing, UE is expected to operate in TDM mode if configured P_LTE + P_NR > Pcmax (TS 38.213 7.6.1)
• singleUL-Transmission
Indicated that the UE does not support simultaneous UL transmission as defined in TS 38.101-3
The UE may only set this bit for certain band combinations defined in TS 30.101-3
• tdm-pattern
Indicates whether the UE supports the tdm-Pattern for single UE transmission associated functionality
Support is conditionally mandatory for UEs that do not support dynamic power sharing and for UEs that indicate single UL fo any band combination
MRDC-Parameters ::= SEQUENCE {

singleUL-Transmission ENUMERATED {supported} OPTIONAL,
dynamicPowerSharing ENUMERATED {supported} OPTIONAL,
tdm-Pattern ENUMERATED {supported} OPTIONAL,
ul-SharingEUTRA-NR ENUMERATED {tdm, fdm, both} OPTIONAL,
ul-SwitchingTimeEUTRA-NR ENUMERATED {type1, type2} OPTIONAL,
simultaneousRxTxInterBandENDC ENUMERATED {supported} OPTIONAL,
asyncIntraBandENDC ENUMERATED {supported} OPTIONAL,
...,
[[
dualPA-Architecture ENUMERATED {supported} OPTIONAL,
intraBandENDC-Support-v1540 ENUMERATED {non-contiguous, both} OPTIONAL,
ul-TimingAlignmentEUTRA-NR ENUMERATED {required} OPTIONAL
]]
}
What terminal report in Capability info?
Number of UL Power Amplifiers in UE
• First 5G chipsets will have dual TX support for
Dual TX capable NO all supported band combinations (but no UL
(for specific band Single TX MIMO)
combination)
• UE typically has one PA per band group, e.g.:
UE needs to report – FDD < 1GHz
YES TDM pattern support – FDD > 1 GHz
Dual TX (LTE conf 2) – FDD 2.6 GHz
– TDD (NR 3.5)
• n1 may not be supported if an anchor is b3
Semi-static power (only if separate PA is fitted – UE price issue).
Dynamic Power NO Hence unlikely to see low/low band
split
sharing combination of LTE anchor and NR.
(e.g. 100 + 100mW)
• Single TX option has negative impact on
YES latency and coverage – TDM pattern
UL power dynamically can be
shared b/w LTE & NR

UE Transmit Power NR
3GPP 38.101-1 f30 Table 6.2.1-1: UE Power Class
Class 1 Toleranc Class 2 Toleranc Class 3 Tolerance
band (dBm) e (dB) (dBm) e (dB) (dBm) (dB)
n1 23 ±2
• Power class 3 is default for NR (same as LTE) n2 23 ± 23
n3 23 ± 23
• Power class 2 for band n78 was defined to boost UE’s UL coverage n5 23 ±2
(Rel 15.3) n7
n8
23
23
± 23
± 23
n12 23 ± 23
• Note: Dual connectivity and SUL may have their own limitation (FFS) n20 23 ± 23
n25 23 ±2
Transmitter power for Dual Connectivity n28 23 +2 / - 2.5
n34 23 ±2
• Defined in 3GPP TS 38.101-1 Chapter 6.2B is in version 15.3 empty n38 23 ±2
n39 23 ±2
• Therefore it is not defined that are the maximum UE power in such n40 23 ±2
n41 26 +2/-33 23 ± 23
operation n50 23 ±2
n51 23 ±2
LTE n66 23 ±2
n70 23 ±2
n71 23 +2 / - 2.5
NR
n74 23 ±2
n77 26 +2/-3 23 +2/-3
n78 26 +2/-3 23 +2/-3
n79 26 +2/-3 23 +2/-3
n80 23 ±2
n81 23 ±2
Transmitter power for SUL n82 23 ±2
n83 23 ± 2/-2.5
• As transmission on 3.5GHz UL and 1.8MHz UL carrier are considered n84 23 ±2
n86 23 ±2
as transmission in the same cell, power configuration is the same on NOTE 1: PPowerClass is the maximum UE power specified without taking into
each carrier account the tolerance
NOTE 2: Power class 3 is default power class unless otherwise stated
NOTE 3: Refers to the transmission bandwidths (Figure 5.3.3-1) confined
within FUL_low and FUL_low + 4 MHz or FUL_high – 4 MHz and FUL_high,
the maximum output power requirement is relaxed by reducing
the lower tolerance limit by 1.5 dB

UE Transmit Power for UL-MIMO
• the maximum output power is measured as the sum of the maximum output power at each UE antenna connector
3GPP 38.101-1 f30 Table 6.2D.1-1: UE Power Class for UL-MIMO in closed loop spatial multiplexing scheme
Class 1 (dBm) Tolerance Class 2 (dBm) Tolerance Class 3 Tolerance (dB) Class 4 Tolerance (dB)
NR band (dB) (dB) (dBm) (dBm)
n41 26 +2/-31 23 +2/-31 LTE

n77 26 +2/-3 23 +2/-3
NR
n78 26 +2/-3 23 +2/-3
n79 26 +2/-3 23 +2/-3
NOTE 1: 1refers to the transmission bandwidths confined within FUL_low and FUL_low + 4 MHz or FUL_high – 4 MHz and FUL_high, the maximum output
power requirement is relaxed by reducing the lower tolerance limit by 1.5 dB

UE Dynamic Power Sharing
There are two types of NSA UEs supported by the specification:
• UE Type 1 capable of dynamic LTE-NR power sharing

– Converged NR and LTE modem with high speed interface capability
– These UEs can operate with PLTE + PNR > Ppowerclass configuration or with no PLTE or PNR configuration
• UE Type 2 not capable of dynamic LTE-NR power sharing

– Separate NR and LTE modem with limited interface capability
– These UEs can only operate in EN-DC when a configuration is received with PLTE + PNR <= Ppowerclass
• Neither type of UEs are allowed to transmit with power above Ppowerclass in FR1
LTE
NR LTE NR
3GPP R1-1800942

LTE TDM configuration for UE
UE MeNB SgNB EPC
LTE Initial Context Setup + B1 Measurement Event configuration (optional)
B1 Measurement Report
SgNB Addition Request
(MeNB Resource Coordination
Info (TDM Pattern))
SgNB Addition Request ACK

(MeNB Resource Coordination
Info (TDM Pattern))
RRC Connection
Reconfiguration
(tdm-PatternConfig-r15)
RRC Connection
Reconfiguration Complete
SgNB Reconfiguration
Complete

EN-DC UL Power Limitation
• Semi-static power sharing is reducing UL link budget by 3dB à negative impact on both LTE & NR coverage.
• Single uplink operation (TDM) à negative impact on throughput
Network power configuration LTE max NR max

UE Capacity
mode power power NR cell LTE
Semi-static power sharing Native support <23dBm <23dBm
LTE cell
𝑃"#$ %&' + 𝑃"#$ )* ≤ 23𝑑𝐵𝑚 (e.g. 20 (e.g. 20
dBm) dBm) Semi-static: NR edge LTE only
Single uplink operation mandatory if UE does 23 dBm 23 dBm LTE = 20dBm TDM power: SgNB released
𝑃"#$ %&' ≤ 23𝑑𝐵𝑚 𝑜𝑟 𝑃"#$ )* ≤ not support dynamic NR = 20dBm LTE = 23 dBm Potentially SUL
23𝑑𝐵𝑚 but in TDM pattern power sharing NR = 23 dBm
ND TDD Frame Structure (3:1) DDSU ND TDD Frame Structure (4:1) DDDSU
offset = 3 Subframe Number offset = 3 Subframe Number
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
TDM-Pattern 1 ms U D D D S U D D D S TDM-Pattern 1 ms U D D D S U D D D S
LTE FDD 1 ms U U LTE FDD 1 ms U U
NR TDD 0.5 ms D D S U D D S U D D S U D D S U D D S U NR TDD 0.5 ms D D D S U D D D S U D D D S U D D D S U
U LTE UL forbidden
Special contains 2 UL OFDM
symbols U UL is available
Solution:
LTE FDD RAT will be configured with • Supplemental Uplink (however negative impacts, especially on throughput needs to be
TDD pattern number 2 and offset 3 investigated)
• Standalone operation (SA) – UE is connected only to one RAT at a time
UL Coverage Extension

UL Coverage Extension Options
• NR in active antenna configuration on 3.5GHz has very good
DL coverage – comparable with 1.8GHz LTE MIMO 2x2
• However, UL coverage is still limited, even more with UL 1800 LTE PUSCH 1Mbps
power split between LTE and NR.
3500 NR PDCCH
• Moreover, indoor penetration losses on 3.5GHz are higher
than on 1.8GHz 3500 NR PDSCH 10Mbps
Three techniques are suggested to boost NR UL coverage: 3500 NR PDSCH
100Mbps Coverage
• UL split bearer with EN-DC gap
• UL Carrier Aggregation with flexible spectrum sharing (on 3500 NR PRACH

1800 or 700) X
X
X
X
X
X
X
X 3500 NR PUCCH
X X X X
• Supplemental Uplink X X X X
3500 NR PUSCH
700 NR PDSCH 10Mbps

Can be deployed and 700 NR PUSCH 1Mbps
utilized for UL coverage
extension

UL Coverage Extension Options
UL fallback to LTE Inter-band Carrier Aggregation Supplemental Uplink
• At the NR UL cell edge (detected by • Promoted by Ericsson • Promoted by Huawei
low QCI or low UL SINR) gNB flow • Dual layer solution, where 1.8GHz • Most advanced solution, however
control will redirect all data bearers or 700MHz layer will be deployed the most complex one
from NR PUSCH to LTE PUSCH. with NR as well. • At the NR UL cell edge (detected by
• NR PUCCH will remain on 3.5GHz, • Lower band layer will be used as low UL SINR) terminal is switched to
so it will become a new UL cell PCell, and 3.5GHz is SCell (DL CA) 1800 or 700, where flexible
border. “capacity extension” spectrum sharing with LTE can be
• UL power split still exercised • However due to low penetration of deployed.
(20+20) NR chipsets, flexible spectrum • With TDM, full power of 23dBm can
• No vendor lock-in sharing (LTE + NR concurrent) is be recover
suggested. • Vendor lock-in
• Some capacity loss expected on DL
• UL power split still exercised
(20+20)
• Vendor lock-in

UL fallback to LTE
• At the end of NR 3500 PDSCH coverage, all NR traffic is
redirected to LTE 1800 PUSCH. X X X X
NR
• Concept of UL split bearer is used
X X X X
X X X X P UCC NR
X X X X
H (H PUSC
ARQ H (A
• 3500 NR PDSCH still stays, therefore also HARQ LTE LTE fe edb
RQ)
UL UL a ck +
feedback must be handled by 3500 NR PUCCH. NR
UL +D N
+D
L (1.8 SR +
&D L (1 RD CQI
.8 G L (3 G Hz )
• 3500 NR PUSCH still defines the new NR coverage edge, L (3
.5 G H z )
.5G
H z)
)
due to the PHY (HARQ) + RLC (ARQ) feedback Hz
)
LTE UL & DL
NR UL NR UL harq, arq & DL
1800 LTE PUSCH (RRC) 1800 LTE PUSCH (rrc+data)
1800 LTE PDSCH (RRC) 1800 LTE PDSCH (RRC)
3500 NR PDSCH (data) 3500 PDSCH (data)
3500 NR PUSCH (data) 3500 NR PUSCH (rlc N/ACKs)
1800 LTE PUCCH (harq) 1800 LTE PUCCH (harq)
3500 NR PUCCH (harq) 3500 NR PUCCH (harq)

Huawei – Uplink fallback to LTE
• Huawei’s name for UL Split bearer with EN-DC.
Huawei 5G RAN 2.1

NRCellNsaDcConfig.NsaDcAlgoSwitch: UL_FALLBACK_TO_LTE_SWITCH = OFF; [ON, OFF]
NRDUCellSrsMeas.NsaUlFackToLteSinrThld = -3dB; [-20 - 20]
NRDUCellSrsMeas.NsaUlFackToLteSinrHyst = 3dB; [0 - 10]
If UL SINR on NR ≤ (NRDUCellSrsMeas.NsaUlFackToLteSinrThld - NRDUCellSrsMeas.NsaUlFackToLteSinrHyst) à UL data are redirected to LTE PUSCH only

If UL SINR on NR > (NRDUCellSrsMeas.NsaUlFackToLteSinrThld + NRDUCellSrsMeas.NsaUlFackToLteSinrHyst) à UL data are redirected back to NR PUSCH
63

Inter-Band Carrier Aggregation
• Conventional Carrier aggregation solution.
X X X X
X X X X
• At the NR 3500 MHz UL cell edge, 1800 (or 700) MHz NR X
X
X
X
X
X
X
X
is configured as PCell, it runs DL + UL data.

LTE
LTE UL+
• 3.5GHz NR PDSCH is configured, either with or without UL
NR N RU
DL (
1.8
+D L G Hz
measurement as Secondary Carrier (SCell) NR
L (1
.8 G
DL
(3.5
G
(70
0M
H
)
UL H z) H z) z )
+D
L (3
• 1.8GHz layer can be running dynamic (or static) spectrum .5 G
Hz
sharing: LTE+NR in UL and DL. )
• It requires to build 2nd NR frequency layer.

• Vendor lock-in, as all spectrum sharing solutions are 1800 LTE PUSCH (rrc) 1800 LTE PUSCH (RRC)
vendor specific, unless 5G low band without spectrum 1800 LTE PDSCH (rrc) 1800 LTE PDSCH (RRC)
sharing is deployed.
3500 NR PDSCH (data) Scell 3500 PDSCH (data)
3500 NR PUSCH (data) Pcell 700MHz NR PUSCH (data+harq)
On 3.5GHz UL border,
1800 LTE PUCCH 1800 LTE PUCCH
PCell SCell swap is
required

UL & DL Decoupling - Supplemental Uplink
• C-band has longer DL coverage due to Massive MIMO
antenna and beamforming than UL.
NR
DL
• UL & DL decoupling enables extending C-band cell radius (3 .5 G
H z)
NR NR
on UL by utilizing lower frequency bands UL& SU L (e
GH DL (3 .g. 8
00
z) .5 MH
z)
• Switching from 3.5GHz to lower frequency is triggered by
LTE UL & DL
network based on UL quality measurements. NR UL NR SUL & DL
• Huawei: decision on SUL activation is based on UL C-band
3GPP 38.101-1 Table 5.2C-1: Operating band combination for SUL in FR1
SINR (measured on SRS) and C-band load. NR Band combination NR Band
Note
for SUL (Table 5.2-1)
• In SA: SUL can be activated even before Random Access SUL_n78-n802 n78, n80 3.5 + 1.8
2
SUL_n78-n81 n78, n81
Procedure to NR starts SUL_n78-n822 n78, n82 3.5 + DD800
2
SUL_n78-n83 n78, n83
• RSRP < thd à random access on non-SUL carrier SUL_n78-n842 n78, n84
2
SUL_n78-n86 n78, n86
2
• RSRP > thd à random access on SUL carrier SUL_n79-n80 n79, n80
SUL_n79-n812 n79, n81
NOTE 1: If a UE is configured with both NR UL and NR SUL
carriers in a cell, the switching time between NR UL
carrier and NR SUL carrier is 0us.
NOTE 2: For UE supporting SUL band combination
simultaneous Rx/Tx capability is mandatory.

Supplemental Uplink – Band Combinations and BW
3GPP 38.101-1 Table 5.5C-1: Supported channel bandwidths per SUL band combination
Subcarrier
SUL 5 10 15 20 25 30 40 50 60 80 90 100
NR Band spacing
configuration MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz
(kHz)
15 Yes Yes Yes Yes Yes
SUL_n78A- n78 30 Yes Yes Yes Yes Yes Yes Yes Yes Yes
n80A 60 Yes Yes Yes Yes Yes Yes Yes Yes Yes
n80 15 Yes Yes Yes Yes Yes Yes
n81 15 Yes Yes Yes Yes
15 Yes Yes
SUL_n79A- n79 30 Yes Yes Yes Yes Yes
n80A 60 Yes Yes Yes Yes Yes
n80 15 Yes Yes Yes Yes Yes Yes
15 Yes Yes
SUL_n79A- n79 30 Yes Yes Yes Yes Yes
n81A 60 Yes Yes Yes Yes Yes

SUL Operation Mechanism
• When SUL in configured for a UE, there are 2 ULs carriers configured for 1 DL carrier of the same cell.
• At any time, each serving cell has at most one PUSCH for transmission for UE
• Dynamic TDM between SUL and non-SUL PUSCH is supported
• UE switching time between LTE and NR shall be defined as UE capability with two options: digital rotator (~0µs), RF shift
(<20µs)

Frequency Spectrum Sharing

LTE Radio Frame Downlink

LTE Radio Frame Uplink
One Radio Frame = 10 ms
1.4 MHz Subframe 0 = 1 ms Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9
Slot 0 = 0.5 ms Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot 9 Slot 10 Slot 11 Slot 12 Slot 13 Slot 14 Slot 15 Slot 16 Slot 17 Slot 18 Slot 19
71
70
69
68
Resource Block 5
67
66
65
64
63
62
61
60
59
58
57
56
Resource Block 4
55
54
53
52
51
50
49
48
47
46
45
44
Resource Block 3
43
42
41
40
Bandwidth = 1.08 MHz
Subcarrier Number
Resource Block 2
31
30
29
28
27
26
25
24
23
22
21
20
Resource Block 1
19
18
17
16
15
14
13
12
11
10
Resource Block 0 = 180 kHz
9
8
7
6
5
4
3
2
1
0
Physical Uplink Control Channel 1 (PUCCH) Physical Uplink Shared Channel (PUSCH) Physical Random Access Channel (PRACH)
PRACH Configuration Index = 4 (every radio frame)
Physical Uplink Control Channel 2 (PUCCH) Not used Uplink (empty)

Frequency Spectrum Sharing (FSS)
• Important part of 5G deployment will be efficient use of low band spectrum and its sharing with legacy technology,
especially LTE
• FSS can be implemented in UL and DL, it implies vendor lock-in – LTE and NR must be from same supplier and Radio
amplifier will be connected to both technologies (initially by 2 optical interfaces)
UL spectrum sharing is not complicated
• each RAT will have it time and frequency resources allocated and controlled by unified LTE/NR scheduler
NR PUCCH NR PUCCH
Relative spectral efficiency compared to a LTE only scenario UL Dynamic

LTE PUCCH LTE PUCCH
Spectrum
2TX configuration 4 TX configuration Sharing NR PRACH
NR PUSCH
Frequency
LTE & NR Co- NR PUSCH
LTE SRS
LTE SRS
10 MHz 20 MHz 10 MHz 20 MHz
existence LTE PUSCH
NR relative 87 % 89 % 80 % 82 % LTE PUSCH
Stationary
LTE PRACH
T-put
Possible also with LTE PUCCH LTE PUCCH
LTE relative 93 % 93 % 93 % 93 % deployment: NR PUCCH NR PUCCH
T-put NR TDD and LTE FDD
Time
TTI TTI+1

Downlink Reserved Resources
In order guarantee backward compatibility with LTE and for forward compatibility with future radio standards, NR support
reserved resources in DL:
• semi-statically configured time-frequency resources around which NR PDSCH can be rate-matched (simply: OFDM symbols
will be punched – left empty)
Reserved resources can be configured by 3 different ways:

a. by referring to LTE configuration (ideal for LTE/NR coexistence)
b. by referring to a CORESET
c. by configuring resource sets using a set of bitmaps (ideal for NR + “6G” coexistence)
In DL sharing is more complicated because LTE contain several “always-on” signals:

• LTE PSS and SSS (middle of BW 72 SC, 5 ms period, 2 OFDM symbols) (reserved by bitmap [c])
• LTE PBCH (10ms period, 6 RBs, 4 OFDM symbols) (reserved by bitmap [c])
• LTE CRS (full BW, every 6th SC, ) (signaled in RRC and rate-matched by NR [a])

Reserved Resources Bitmap to Punch LTE PSS & SSS
• 3GPP allows to define bitmap triplet for NR, which indicated frequency, time and slot period in which NR shall not
transmit
• bitmap-1 length equals to number of NR RBs (for PSS & SSS central 6 RBs)
• bitmap-2 of length 14 (one slot) indicated punched OFDM symbol (for PSS & SSS 5 and 6, numbering from 0)
• bitmap-3 of length 10 indicates the NR subframes (slots) for period (for PSS & SSS bit 0 and 5 are indicated)
SCS = 15 kHz, Slot = 1 ms Subframe 0 Subframe 5 SCS = 15 kHz, Slot = 1 ms Subframe 0

0 1 2 3 4 5 6 7 8 9 10111213 0 1 2 3 4 5 6 7 8 9 10111213 0 1 2 3 4 5 6 7 8 9 10111213
105 0 105 105 0
… 0 … … 0
… … … … …
55 1 55 55 1
Resource Blocks
Resource Blocks
54 1 54 54 1
bitmap-1
bitmap-1
53 1 53 53 1
52 1 52 52 1
51 1 51 51 1
50 1 50 50 1
… … … … …
… 0 … … 0
0 0 0 0 0
0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0 0
bitmap-2 bitmap-2
bitmap-3 10 0 0 0 1 0 0 0 0 LTE SSS

LTE PPP
LTE PBCH

LTE NR Synchronization Signal Coexistence
Scheduling in frequency and time domain RBs that contains LTE PSS, SSS, PBCH cannot be scheduled
PDCCH by LTE and vice versa.
• LTE PDCCH and NR PDCCH scheduled by coordinated scheduler PBCH/PSS/SSS Coexistence
slots = subframe = 1 ms (if SCS=15
in TDM kHz)
0 1 2 3 4 5 6 7 8 9 101112131415161718192021222324
• LTE PDCCH reduced to 1-2 OFDM symbols, full BW, NR PDCCH 10
allocated into half BW by CORESET configuration 5
PDSCH LTE PSS, SSS, PBCH

Period 5ms, BW center
• coordinated scheduler may be configured with priority toward
…
LTE or NR, or equal priority. …
Resource Blocks
55
• RBs containing CORESET can be scheduled by NR PDSCH only, 54
CORESET change only possible through RRC signaling 53
52
51
PDCCH/PDSCH LTE/NR 50
… NR SSB (PSS, SSS, PBCH)
scheduling Dynamic LTE PDCCH size … Period 20ms (4 slots
0 1 2 3 4 5 6 7 8 9 10111213 0 1 2 3 4 5 6 7 8 9 10111213
105
includes beam
105
… … Out of LTE band, sweeping), 20 RBs in
20
… … allocated for NR PDSCH freq domain, BW
…
55 55 NR RBs: 0-2 and 103-105 0
bottom
54 54
53 53
52 52
51 51
50 50
… … LTE PDCCH
LTE SSS
… … LTE PDSCH
LTE PSS
0 0 NR CORESET
LTE PBCH
NR PDSCH
NR SSB
Reserved Resources for LTE CRS
• NR PDCCH must avoid LTE CRS from antenna port 2 and 3
in symbol #1. It is not 3GPP standardizes therefore high
PDCCH/PDSCH LTE/NR
risk of unsuccessful demodulation. NR CEE aggregation scheduling
level may increase to compensate, so to PDCCH capacity 0 1 2 3 4 5 6 7 8 9 10111213
12
will be reduced. 11
10
9
• NR PDSCH will be rate-matched around LTE CRS. It is 8
Subcarrier
7
standardized procedure by 3GPP, no performance 6
reduction. 5
4
3
2
• NR PDSCH DMRS can be configured in symbol #2 or #3, 1
where there is no LTE CRS
LTE PDCCH
LTE CRS 4x4
NR CORESET
NR PDSCH

Huawei: LTE-NR Spectrum Sharing
• DL+UL spectrum sharing already on the roadmaps (expected in 5G RAN 3.1)
• First spectrum sharing introduced in 5G RAN 2.1 or SRAN 15.1 but UL only, therefore only for SUL
76

DL Power Configuration & Power
Saving

DL Power Allocation
Typical active antenna product: Huawei DL Power Setting
• 64TRX NRDUCellTRP.MaxTransmitPower – maximum transmit power of a single
• Output power 200W antenna
• IBW/OBW 100MHz Total transmit power = MaxTransmitPower + 10*log10(NTX)
• Band 42/43 (3.X GHz) NTX = NRDUCellTRP.TxRxMode
• Power consumption 1200W Reference Power (power of “Reference” Subcarrier)
• Spectral density: ReferencePwr = maxTransitPower – 10*log10(RB*12)
– Typical deployment configuration will be with PBCH, SS, PDCCH, PDSCH (per Subcarrier, or Resource Element))
100MHz BW and full power setting:
– 200W/100MHz à 40W/20MHz à same as LTE All PHY channels power is calculated from ReferencePrw + specific offset:
MIMO 2x2 20MHz BW, 20W/port PRE_PBCH = ReferencePwr + MaxSsPbchPwrOffset +
10*log10(RFChannelNum)
RFChannelNumber = No of Physical FR Channels
NR LTE Example
Spectral 200W 40W 200W; 100MHz = 273 RBs; 64 TX; SCS=30kHz; MaxSsPbchPwrOffset = 3dB:
density
100 MHz 20 MHz MaxTransmitPower = (10*log10(200/64)+30 = 34.95 dBm
ReferencePwr = MaxTransmitPower - 10*log10(12*273) = -0.205 dBm
Same Spectral Density as LTE PRE_PBCH = ReferencePwr + 3dB + 10*log10(64) = 20.86 dBm

Power and Heat Dissipation
• 2G + 3G + LTE configuration meets ETSI EN 300 019-1-3 Class 3.1only • 5G NR will add:
consumes: and are sensitive to keep req. humidity! – Maximum (64TRX, 3 sectors): 4000W
– Average (-48V DC): 2500W (temperature-controlled locations): – 5G BB cards more sensitive to
– Maximum (-48V): 8000W humidity than previous generation
• Often existing cabinets are already

nearly ETSI specification
Solutions:
• New or second cabinet installation
• Installation of heat exchanger to decrease humidity (lower efficiency than free cooling, higher power
consumption and noise)
• Installation of AC (decreases humidity too)

Power Saving Features
Most of the principles originated in LTE:
• PA shutdown for Symbol Level (Micro DTX)
• Bias Voltage adjustment of PA into lower level
• MIMO/Massive MIMO beam shutdown (negative: may have impact on coverage)
• Carrier Shutdown on multi-carrier site (designed into NR from beginning)
Innovative (NR only) power saving features:

• NR introduces new signaling mechanism and bandwidth definitions which further reduces power consumption:
• Ultra lean design (reduced broadcast information, SSB not on every carrier)
• Bandwidth part (reduced BW for UEs)
• RRC Inactive (RRC suspend and resume, to quickly resume RRC connection without excessive signaling)

Cell and Ultra-Lean Design
• 5G-NR was designed with respect to ultra-lean design and CU-DU split
• Ultra-lean Design: minimize transmissions not related to user data
• Hence NR cell scales with control signaling load (Paging, RAR, RACH) and not user plane load.
Frequency Silent Frequency Carriers

[GHz] Nothing broadcasted unless there are active users
mmWave
•
Power saving advantage

50 •
• Still possible to perform paging, RACH
6 6 GHz
Example: Band 78 (3.5 GHz)
• SCS = 30kHz
3.5 GHz • NR IDLE Cell Broadcast Active
1 2.6 GHz
Radius

Radio Interface

5G-NR Radio Interface
• Frequency bands
• Bandwidth, bandwidth part, NR-ARFCN
• F-FDMA
• Numerology
• Coding: LDPC & Polar Codes
• DL Physical Channels
• PDSCH, PDCCH, CORESET
• UL Physical Channels
• PUSCH, PUCCH, PRACH
• Massive MIMO

5G-NR Frequency Bands 3GPP 38.101-1 Table 5.2-1 NR operating bands for FR1
NR
Downlink (DL)
• Use prefix “n” to differentiate from E-UTRA bands ope Uplink (UL) operating
Tota operating band Tota
rati band Duplex
l BS transmit / UE l Note
• To simplify RF specification requirements, two separate ng BS receive / UE transmit
BW receive BW
Mode
ban FUL_low – FUL_high
frequency ranges were defined in 3GPP for 5G-NR: d
FDL_low – FDL_high
3GPP 38.101-1 Table 5.1-1 n1 1920 MHz – 1980 MHz 60 2110 MHz – 2170 MHz 60 FDD UMTS
n2 1850 MHz – 1910 MHz 60 1930 MHz – 1990 MHz 60 FDD
Frequency range Correspon/ding Comment n3 1710 MHz – 1785 MHz 75 1805 MHz – 1880 MHz 75 FDD PCS
designation frequency range n5 824 MHz – 849 MHz 25 869 MHz – 894 MHz 25 FDD
n7 2500 MHz – 2570 MHz 70 2620 MHz – 2690 MHz 70 FDD 2.6 GHz FDD
FR1 450 MHz – 6000 MHz Sub 6 GHz n8 880 MHz – 915 MHz 35 925 MHz – 960 MHz 35 FDD GSM
n20 832 MHz – 862 MHz 30 791 MHz – 821 MHz 30 FDD DD800
FR2 24250 MHz – 52600 MHz mmWave n28 703 MHz – 748 MHz 45 758 MHz – 803 MHz 45 FDD DD700
n38 2570 MHz – 2620 MHz 50 2570 MHz – 2620 MHz 50 TDD 2.6 GHz TDD
n41 2496 MHz – 2690 MHz 194 2496 MHz – 2690 MHz 194 TDD
• All relevant frequency bands used in Europe has been n50
n51
1432 MHz – 1517 MHz
1427 MHz – 1432 MHz
85
5
1432 MHz – 1517 MHz
1427 MHz – 1432 MHz
85
5
TDD
TDD
also standardized for 5G-NR n66 1710 MHz – 1780 MHz 70 2110 MHz – 2200 MHz 90 FDD
3GPP 38.101-2 Table 5.2-1 NR operating bands for FR2 n70 1695 MHz – 1710 MHz 15 1995 MHz – 2020 MHz 25 FDD
NR FR1 new bands

n71 663 MHz – 698 MHz 35 617 MHz – 652 MHz 35 FDD
Downlink (DL) operating
NR Uplink (UL) operating band n74 1427 MHz – 1470 MHz 43 1475 MHz – 1518 MHz 43 FDD
band Duple
Operati BS receive Total Total n75 N/A 1432 MHz – 1517 MHz 85 SDL
BS transmit x
ng UE transmit BW BW n76 N/A 1427 MHz – 1432 MHz 5 SDL
NR FR2 new bands
UE receive Mode
Band n77 3300 MHz – 4200 MHz 900 3300 MHz – 4200 MHz 900 TDD 3.5 GHz TDD
FUL_low – FUL_high FDL_low – FDL_high
n78 3300 MHz – 3800 MHz 500 3300 MHz – 3800 MHz 500 TDD 3.5 GHz TDD
n80 1710 MHz – 1785 MHz 75 N/A SUL PCS UL
n81 880 MHz – 915 MHz 35 N/A SUL GSM UL
Huawei 5G RAN 2.1 n82 832 MHz – 862 MHz 30 N/A SUL DD800 UL
n83 703 MHz – 748 MHz 45 N/A SUL DD700 UL
NRDUCell.FrequencyBand = ; [N3, N28, N41, N77, N78, n84 1920 MHz – 1980 MHz 60 N/A SUL UMTS UL
N79, N80, N82, N83, N84, N86, N257, N258, N260] n86 1710 MHz – 1780 MHz 70 N/A SUL
NRDUCell.DuplexMode = ; [CELL_FDD, CELL_TDD, CELL_SUL] Supplemental Uplink

Often European Selection
New Coding: Low Density Parity Code & Polar Codes
• Turbo Coding is relatively simple at Encoding phase but complex in decoding phase. This complexity gets higher as the size
of code block gets larger.
• LDPC is not as simple as turbo coding at Encoding phase, but much simpler in decoding phase à improvement for large
block size. Further, it allows lower coding rate than 1/3 (Turbo Codes in LTE with lower than 1/3 rate relies on repetition),
and therefore allowing higher coding gains and high reliability in bad radio conditions
• Fast decoding allows for short processing time at a receiver, therefore opens way for low latency services
• Polar Coding is to replace TBCC (Tail Bit Convolution Code) and LDPC is to replace Turbo Coding.
• Polar codes are relatively new (2008) invention, and first class of codes shown to achieve the Shannon capacity limit with
reasonable complexity especially for short block lengths à suitable for control channels
Channel Coding Algorithm Reference

BCH Polar Coding 38.212 - 7.1.4
DCI Polar Coding 38.212 - 7.3.3
38.212 - 6.3.1.3,
UCI Polar Coding
6.3.2.3
DL-SCH LDPC 38.212 - 7.2.4
UL-SCH LDPC 38.212 - 6.2.4

DL Waveform: Filtered-OFDM
• leverages all the benefits of OFDM technique. In
addition it helps in efficient spectrum utilization
LTE
by meeting OOBE requirements.
Max 2048
• the entire assigned bandwidth is first divided
subcarriers
into several sub-bands. The different types of
services are accommodated in these different (1200 in use)
sub-bands using most suitable
waveform/numerology
• offers significant reductions on usage of guard
band. This leads to more efficient spectrum
utilization. 5G
Max 4096
subcarriers
(3276 in use)
F-OFDM – Filtered OFDM

CP-OFDM – Cyclic Prefix OFDM
DFT-S-OFDM – Discrete Fourier Transform-spread-OFDM
Numerology

Numerology (1)
• LTE supports only one type to Subcarrier Spacing (SCS) , that is 15 kHz (alternatively 7.5 kHz to MBMS and 1.25 kHz prof
PRACH). That defines (and also limits) maximum carrier BW, Round Trip Time, Delay Spread (indirectly cell radius)
• For 5G-NR 5 different SCS were standardized, denoted by letter µ (Greek mu) listed in the table below:
3GPP 38.211 Table 4.2-1

µ Δ𝑓 = 26 7 15[𝑘𝐻𝑧] Cyclic prefix
0 15 Normal
1 30 Normal Note: only 𝜇 = 2 has a support
2 60 Normal, Extended for Extended Cyclic Prefix
3 120 Normal
4 240 Normal
• Reason is a wide operational frequency range of NR (sub 3GHz to 39GHz), and maximum bandwidth of NR – 100 MHz (FR
= 1) or 400MHz (FR = 2).
• Typically BWs of up to 20MHz are configured with 15 kHz SCS, while wider BWs may have 100 MHz (3.x GHz) or even
higher – FR2 = 400 MHz
Huawei 5G RAN 2.1
NRDUCell. SubcarrierSpacing = 30KHZ; [15KHZ, 30KHZ, 120KHZ]

Numerology (2)
µ=0 µ=1 µ=2
• In OFDM there is inversely proportional relation between
SCS and OFDM symbol duration. cyclic prefix duration = 4.69 πs
ODFM symbol
cyclic prefix duration = 2.34 πs
33.3 µs
cyclic prefix duration = 1.17 πs
16.67 µs
66.6 µs
• Narrow SCS of 15 kHz is more suitable for narrower BWs
of up to 20 MHz, as it can accommodate quite many
subcarriers, while having quite long OFDM symbol
subcarrier
duration – 66.6 µs. It is consequently less prone to inter
symbol interference, i.e., suitable for long cell radius 1 slot = 1 ms
(large delay spread). subframe
1 slot = 0.5 ms
M M
𝑂𝐹𝐷𝑀 𝑠𝑦𝑚𝑏𝑜𝑙 𝑑𝑢𝑟𝑎𝑡𝑖𝑜𝑛 = NON
= MP QRS
= 66.6𝜇𝑠
subframe
1 slot = 0.25 ms
subframe

Numerology (3) – Use Cases
• SCS has a great impact on Round Trip Time (Latency), therefore values as high as 120 kHz enables low latency services
Cell radius [km] SCS = 15kHz

Use Case = eMBB, mMTC
BW < 20 MHz
>5 km
TOFDM = 1 ms
SCS = 30kHz
≈ 2 km Use Case = eMBB, URLLC
BW < 100 MHz
TOFDM = 0.5 ms SCS = 120kHz
Use Case = URLLC, eMBB, indoor
indoor BW < 400 MHz
TOFDM < 0.125 ms
0.7 3 20 30 Frequency [GHz]

Numerology (4)
SCS (∆f) 15 kHz 30 kHz 60 kHz 120 kHz 240 kHz
Expected FFT-size ≤ 4096 ≤ 4096 ≤ 2048 ≤ 2048 ≤ 2048

[\]\ ^_àbc M
OFDM Symbol data duration 𝑇WXYZ = de 66.67 µs 33.34 µs 16.67 µs 8.3 µs 4.16 µs
Cyclic prefix
Mgg [\]\ ^_àbc hjj [\]\ ^_àbc 4.69 µs 2.34 µs 1.17 µs 0.59 µs 0.29 µs
𝑇Of = higj ∗ 𝑇WXYZ or 𝑇Of = gilm ∗ 𝑇WXYZ
Cyclic prefix extended no no yes no no
^_àbc [\]\ ^_àbc

OFDM Symbol duration 𝑇WXYZ = 𝑇Of + 𝑇WXYZ 71.35 µs 35.68 µs 17.84 µs 8.92 µs 4.46 µs
Slot length 1 ms 0.5 ms 0.25 ms 0.125 ms 0.0625 ms
Subframe duration 1 ms 1 ms 1 ms 1 ms 1 ms

Mixed Numerology
• Mixed numerology allows combination of use cases with different numerology requirements into one cell.
• Each numerology is separated by own Bandwidth Part configuration

Frequency Bands & Bandwidth

NR Channel Bandwidth
3GPP 38.101-1 Table 5.3.2-1: Maximum transmission bandwidth configuration for FR1
• Maximum BW for some selected bands were SCS 5MHz 10MHz 15MHz 20 MHz 25 MHz 30 MHz 40 MHz 50MHz 60 MHz 80 MHz 100 MHz
boosted to 100 MHz (FR1) of 400 MHz (FR2), (kHz) NRB NRB NRB NRB NRB NRB NRB NRB NRB NRB NRB
15 25 52 79 106 133 [160] 216 270 N/A N/A N/A
respectively. 30 11 24 38 51 65 [78] 106 133 162 217 273
60 N/A 11 18 24 31 [38] 51 65 79 107 135
• Maximum number of Resource Blocks in 20
MHz BW was increased to 106 (LTE has 100) 3GPP 38.101-1 Table 5.3.3-1: Minimum gruadband for each UE channel bandwidth and SCS (kHz) for FR1
due to narrower guardband specification SCS (kHz) 5 MHz 10 MHz 15 MHz 20 MHz 25 MHz 30 MHz 40 MHz 50MHz 60 MHz 80 MHz 100 MHz
(452.5 kHz in each side, LTE has 1000 kHz) 15 242.5 312.5 382.5 452.5 522.5 [592.5] 552.5 692.5 N/A N/A N/A
30 505 665 645 805 785 [945] 905 1045 825 925 845
60 N/A 1010 990 1330 1310 [1290] 1610 1570 1530 1450 1370
• Maximum channel BW is shall not exceed 3300
subcarriers and 4096 FFT size 3GPP 38.101-2 Table 5.3.2-1: Maximum transmission bandwidth configuration for FR2
50MHz 100MHz 200MHz 400 MHz
SCS (kHz)
• UE can operate in asymmetric UL and DL NRB NRB NRB NRB
60 66 132 264 N.A
bandwidths 120 32 66 132 264
Channel Bandwidth [MHz]
Transmission Bandwidth Configuration NRB [RB]

Minimum guard-band =
Channel Edge
Channel Edge
Transmission
Bandwidth [RB] (CHBW – SCS*12*NRB)/2- SCS/2
Resource Block
f
Active Resource
Blocks
© Widermind AB Vivacom Sofia 05-19 94 Guardband, can be asymmetric

NR Spectrum Utilization
• Maximum achieved spectrum utilization is 98.3% for FR1 and 95% for FR2
Not efficient to use SCS 30 kHz for
narrower bandwidths, additionally
delay spread problem may arise
RF1 NR UE and BS spectrum utilization for CP-OFDM (DL & UL with MIMO)
Channel Bandwidth Huawei 5G RAN 2.1
SCS 100
5MHz 10MHz 15MHz 20 MHz 25 MHz 30 MHz 40 MHz 50MHz 60 MHz 80 MHz NRDUCell.DLBandwidth = ; [CELL_BW_10M,
(kHz) MHz
CELL_BW_15M, CELL_BW_20M, CELL_BW_40M,
15 90.0% 93.6% 94.8% 95.4% 95.8% N/A 97.2% 97.2% N/A N/A N/A
30 79.2% 86.4% 91.2% 91.8% 93.6% N/A 95.4% 95.8% 97.2% 97.7% 98.3%
60 N/A 79.2% 86.4% 86.4% 89.3% N/A 91.8% 93.6% 94.8% 96.3% 97.2%
CELL_BW_70M, CELL_BW_90M]
FR1 NR UE spectrum utilization for DFT-s-OFDM (UL without MIMO) NRDUCell.ULBandwidth = ; [CELL_BW_10M,
Channel Bandwidth CELL_BW_15M, CELL_BW_20M, CELL_BW_40M,
SCS (kHz) 5 MHz 10 MHz 15 MHz 20 MHz 25 MHz 30 MHz 40 MHz 50MHz 60 MHz 80 MHz 100 MHz
15 90% 90.0% 90.0% 90.0% 92.2% N/A 97.2% 97.2% N/A N/A N/A CELL_BW_70M, CELL_BW_90M]
30 72.0% 86.4% 86.4% 90.0% 92.2% N/A 90.0% 92.2% 97.2% 97.2% 97.2%
N/A
60 N/A 72.0% 86.4% 86.4% 86.4% 90.0% 92.2% 90.0% 90.0% 97.2% For TDD = 40 MHz, 60 MHz, 80 MHz, 100 MHz
Same as in LTE, means only NR UE

with CP-OFDM (UL MIMO) support in
UL will use upper table (higher
spectral efficiency)
NR Bandwidth & SCS Combination
3GPP 38.101-1 Table 5.3.5-1: Channel Bandwidths for selected NR band
Not any combination of SCS and BW size is NR band / SCS / UE Channel bandwidth
SCS 101,2 100
allowed NR Band
kHz
5 MHz
MHz
152 MHz 202 MHz 252 MHz 30 MHz 40 MHz 50 MHz 60 MHz 80 MHz
MHz
15 Yes Yes Yes Yes
For example Band n38 (2.6 GHz TDD): n1 30 Yes Yes Yes
60 Yes Yes Yes
• was standardized to SCS 15, 30, 60 and n3 15 Yes Yes Yes Yes Yes Yes
maximum BW of 20MHz. 30 Yes Yes Yes Yes Yes
• in case of 30-40 MHz license, Carrier n7 15 Yes Yes Yes Yes
30 Yes Yes Yes
Aggregation have to be used to fully utilize 60 Yes Yes Yes
the spectrum. n20 15
30
Yes Yes
Yes
Yes
Yes
Yes
Yes
60
30 Yes Yes Yes
60
3GPP 38.101-2 Table 5.3.5-1: Channel Bandwidths for each NR band 30 Yes Yes Yes
NR band / SCS / UE Channel bandwidth 60 Yes Yes Yes
SCS 200 15 Yes Yes Yes Yes Yes
NR Band 50 MHz 100 MHz 400 MHz n78 30 Yes Yes Yes Yes Yes Yes Yes Yes
kHz MHz
60 Yes Yes Yes 60 Yes Yes Yes Yes Yes Yes Yes Yes
n257 NOTE 1: 90% spectrum utilization may not be achieved for 30kHz SCS.
120 Yes Yes Yes Yes
60 Yes Yes Yes NOTE 2: 90% spectrum utilization may not be achieved for 60kHz SCS.
n258
120 Yes Yes Yes Yes NOTE 3: This UE channel bandwidth is applicable only to downlink.
60 Yes Yes Yes
n260
120 Yes Yes Yes Yes

NR-ARFCN – Reference Location NR
Operati
ΔFRaster
[kHz]
Uplink
Range of NREF
Downlink
Range of NREF
ng Band (First – <Step size> – Last) (First – <Step size> – Last)
n1 100 384000 – <20> – 396000 422000 – <20> – 434000
• The relation between the NR-ARFCN 𝑁*'X and the RF Reference n2 100 370000 – <20> – 382000 386000 – <20> – 398000
frequency 𝐹*'X in MHz for the downlink and uplink is given by n3 100 342000 – <20> – 357000 361000 – <20> – 376000
n5 100 164800 – <20> – 169800 173800 – <20> – 178800
the following equation: n7 100 500000 – <20> – 514000 524000 – <20> – 538000
n8 100 176000 – <20> – 183000 185000 – <20> – 192000
𝐹*'X = 𝐹*'XoWee^ + Δ𝐹p\^]qp 𝑁*'X −𝑁*'XoWee^ n12 100 139800 – <20> – 143200 145800 – <20> – 149200
n20 100 166400 – <20> – 172400 158200 – <20> – 164200
Reference location from n25 100 370000 – <20> – 383000 386000 – <20> – 399000
previous slide n28 100 140600 – <20> – 149600 151600 – <20> – 160600
n34 100 402000 – <20> – 405000 402000 – <20> – 405000
n38 100 514000 – <20> – 524000 514000 – <20> – 524000
• Where 𝐹*'XoWee^ and 𝑁*'XoWee^ are given in the table below n39 100 376000 – <20> – 384000 376000 – <20> – 384000
n40 100 460000 – <20> – 480000 460000 – <20> – 480000
3GPP 38.104 Table 5.4.2.1-1 15 499200 – <3> – 537999 499200 – <3> – 537999
n41
30 499200 – <6> – 537996 499200 – <6> – 537996
Frequency range [MHz] ΔFGlobal [kHz] FREF-Offs [MHz] NREF-Offs Range of NREF
n51 100 285400 – <20> – 286400 285400 – <20> – 286400
0 – 3000 5 0 0 0 – 599999 n66 100 342000 – <20> – 356000 422000 – <20> – 440000
n70 100 339000 – <20> – 342000 399000 – <20> – 404000
3000 – 24250 15 3000 600000 600000 – 2016666
n71 100 132600 – <20> – 139600 123400 – <20> – 130400
24250 – 100000 60 24250.08 2016667 2016667 – 3279165 n75 100 N/A 286400 – <20> – 303400
n76 100 N/A 285400 – <20> – 286400
15 620000 – <1> – 680000 620000 – <1> – 680000
LTE uses ∆F (frequency raster/step) n77
30 620000 – <2> – 680000 620000 – <2> – 680000
100kHz on all frequency bands. n78
15 620000 – <1> – 653333 620000 – <1> – 653333
30 620000 – <2> – 653332 620000 – <2> – 653332
Huawei 5G RAN 2.1 n79
15 693334 – <1> – 733333 693334 – <1> – 733333
30 693334 – <2> – 733332 693334 – <2> – 733332
NRDUCell.DlNarfcn = ; [151600~160600,361000~376000,499200~537999, n80 100 342000 – <20> – 357000 N/A
620000~680000,693333~733333,2016667~2104166,2229167~2279166] n81 100 176000 – <20> – 183000 N/A
n82 100 166400 – <20> – 172400 N/A
NRDUCell.UlNarfcn = ; [140600~149600,166400~172400,342000~357000, n83 100 140600 – <20> –149600 N/A
384000~396000,499200~537999,620000~680000,693333~733333, n84 100 384000 – <20> – 396000 N/A
2016667~2104166,2229167~2279166] n86 100 342000 – <20> – 356000 N/A

5G-NR Bandwidth part
• New feature in 5G-NR, however Downlink:
similar to LTE-M Narrowband • A BW of each BWP should be ≥ than SS PRB N2
(6PRB) concept Block BW ⋮
• Mandatory configuration for 5G Carrier
• UE is not expected to receive PDSCH, bandwidt
services PRB 1
PDCCH, CSI-RS outside BWP h part 1
• Maximum 4 BWP can be ^wSq
𝑁tuf,M
specified in UL and DL per UE • Each BWP includes at least one CORESET PRB 0
with RRC signaling, but only one with UE specific search space
can be active at a given time. Uplink:
Resource Grid (RG)

However dynamically switchable. • UL BWP can be configured also in PRB N1
Supplementary Uplink
⋮
• UE shall not transmit PUSCH and PUCCH Carrier
outside of BWP ^]\p]
PRB 1 bandwidt
𝑁tuf,M h part 0
Synchronization Signal Block ⋮ PRB 0 ^wSq
𝑁tuf,i
• Resource Grid (RG): Carrier Bandwidth
• Point A: basic reference point in RG PSS
PBCH
CRB 3
SSS
Reference
• Defined for UL, DL, PCell, SCell and SUL separately
locaton CRB 2
offsetToPointA
^]\p]
• Point A = Reference location + offset 𝑁tuf,i
• Common RB (CRB): index in the RG CRB 1
• Start point is aligned with Point A
• Physical RB (PRB): index in the BWP
CRB 0
• Start point is aligned with the BWP start point
^]\p] ^]\p] Called Point A of Common RB
• Defined in CRB by 𝑁tuf , 𝑁O*t = 𝑁f*t + 𝑁tuf
In Resource block unit (FR1
SCS=15kHz, FR2 SCS=60kHz) in MIB

5G-NR Bandwidth Part Application Scenarios
BWP may have different application scenarios: Several types of BWP are used
1. UE with small instantaneous BW can connect to • Initial BWP – used in initial access procedure, UE
network of wide BW. For M2M, less capable terminal receives DL signaling and send UL signaling and
(low complexity) Preamble in it
Initial
BWP1 BWP
Carrier Bandwidth Carrier Bandwidth
2. UE can switch between small and large BWP to save • Dedicated BWP – configured to UE in RRC_CONNECTED
energy. Demodulation of wide BW PDCCH increases mode, maximum of 4 dedicated BWP can be configured
battery consumption. per UE
• Active BWP – one out of four which is active
BWP2
BWP1
Carrier Bandwidth
• Default BWP – one of the Dedicated BWPs, configured
to UE in RRC_CONNECTED mode after BWP inactivity
timer expires
3. A numerology can be unique per BWP. Allows different
service coexistence in one cell UE1 dedicated 1
UE1 dedicated 2
UE1 dedicated 4
BWP1 BWP2 (DEFAULT)
SCS=15kHz SCS=30kHz
UE1 ACTIVE
Carrier Bandwidth UE2 active
dedicated 3
Carrier Bandwidth
Radio Frame Structure

LTE TDD Configuration
LTE has only 7 frame formats and 10 subframe configurations
Downlink Pilot Time Slot Uplink Pilot Time Slot
Subframe Number (36.211) Format 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Max radius
Configuration 0 1 2 3 4 5 6 7 8 9
0 D S U U U D S U U U
0 DwPTS DwPTS DwPTS GP GP GP GP GP GP GP GP GP GP UpPTS 107,1
1 D S U U D D S U U D 1 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP GP GP GP UpPTS 42,8
2 D S U D D D S U D D 2 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP GP GP UpPTS 32,1
3 D S U U U D D D D D
4 D S U U D D D D D D
3 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP GP UpPTS 21,4
5 D S U D D D D D D D 4 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP UpPTS 10,7
6 D S U U U D S U U D 5 DwPTS DwPTS DwPTS GP GP GP GP GP GP GP GP GP UpPTS UpPTS 96,4
6 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP GP GP UpPTS UpPTS 32,1
7 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP GP UpPTS UpPTS 21,4
S filled with DwPTS, GP, UpPTS 10,7

8 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP UpPTS UpPTS
9 DwPTS DwPTS DwPTS DwPTS DwPTS DwPTS GP GP GP GP GP GP UpPTS UpPTS 64,3
DwPTS UpPTS
1 Subframe = 2 Slots
Short Distance DwPTS UpPTS
Long Distance
Max Cell Radius = (GP * Speed_of_Light)/2

= (((Cyclic_Prefix+OFDM_Symbol)*No_of_Symbols_for_GP)-3us-2.5us)*c)/2
= ((4.68e-6+66.66e-6)*2)*3e5)/2 = 21.4 km
Guard periods defines the maximum cell radius. As
UE moves away from eNB, Timing Advance
Final radius will be smaller, calculation excludes NLOS, Sync deviation, UE DL>UL becomes larger (UpPTS moves left) and similarly DL
switch time. Hence vendors values will be lower. signal becomes more delayed (DwPTS shifts right)

5G-NR Frame Structure
• Radio frame length fixed to 10 ms and subframe fixed to 1 ms
• Slot has always 14 OFDM symbol, but number of slots in subframe changes:
1 radio frame = 10 subframes = 10 slots = 10 ms
3GPP 38.211 Table 4.3.2-1

^cb] ep\`q,6 ^xaep\`q,6
µ 𝑁^_àbc 𝑁^cb] 𝑁^cb]
15 kHz
0 14 10 1
1 subframe = 1 slot = 14 OFDM symbols = 1 ms
1 14 20 2
2 14 40 4
3 14 80 8
OFDM symbol
4 14 160 16
20 slots = 10 ms
1 radio frame = 10 subframes = 10
3GPP 38.211 Table 4.3.2-2
^cb] ep\`q,6 ^xaep\`q,6
30 kHz
µ 𝑁^_àbc 𝑁^cb] 𝑁^cb]
2 12 40 4
1 subframe = 2 slots
Huawei 5G RAN 2.1

NRDUCell.CyclicPrefixLength = NCP(Normal Cyclic Prefix)
OFDM symbol

Self-Contained Slot
• It is not defined in 3GPP specification, however general • Enables faster HARQ feedback or a UL scheduling,
assumption is that it contains DL part, Guard Period and therefore reducing RTT à low latency
UL part: Challenges:
• Downlink self-contained slot includes DL data and • Short Guard Period reduces max cell radius
corresponding HARQ feedback • High requirements on UE and gNB processing
Slot
• Frequent DL/UL switching increases overhead created by
D X U Guard Periods
• In DL self-contained slot only retransmission delay is
ACK/NACK reduced, hence not contributing profoundly to low
for PDSCH (DL data)
latency
• Uplink self-contained slot includes uplink scheduling
information and uplink data
Timing Definition of HARQ
Slot In DCI signaling, parameter K1 = 0
• K1: offset between DL data (PDSCH)
D X U
reception and corresponding N/ACK
UL Data
UL Scheduling Grant transmission on UL
on PDCCH

UL/DL Slot configuration hierarchy
5G-NR allows for hierarchical configuration (TS 38.211 Chapter 11.1)
TDD-UL-DL-ConfigCommon
1. Semi-static configuration through cell-specific RRC Signaling
D D X X X X X X X U
2. Semi-static configuration through UE-specific RRC Signaling TDD-UL-DL-ConfigDedicated
D D D D X X X X U U
3. Dynamic configuration through UE-group SFI SFI-PDCCH & SFI-RNTI
D D D D D D D D X U U
4. Dynamic configuration through UE-specific DCI
DCI
• Hierarchical structure allows flexible configuration with D D D D D D D D X U U U
unlimited configuration options, unlike in LTE which allows only

7 UL/DL configurations.

Semi-static Configuration (Cell-Specific)
UE acquires an IE from SIB 1 when accessing the cell from the IDLE state
TDD DL/UL COMMON CONFIGURATION
dl-UL-TransmissionPeriodicity = {0.5, 0.625, 1, 1.25, 2, 2.5, 5, 10 ms}
Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot 9
1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14
nroDowlinkSlots = nroUplinkSlots = {0..maxNrofSlots}

{0..maxNrofSlots}
<6GHz: 15, 30 or 60 kHz
nroDownlinkSymbols nroUplinkSymbols >6GHz: 60 or 120 kHz
3GPP 38.213-Chaper 11.1:
TDD-UL-DL-ConfigCommon ::= SEQUENCE {
Number of Slots in a P referenceSubcarrierSpacing SubcarrierSpacing
P(ms) u_ref (scs Khz) Applicable µ P/20
0 1 2 3 4 dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5,
ms5, ms10} OPTIONAL,
0.5 Not described 40 1 2 4 8
nrofDownlinkSlots INTEGER (0..maxNrofSlots) OPTIONAL,
0.625 3(120) 3,4 32 5 10 nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1) OPTIONAL,
1 Not described 1 2 4 8 16 nrofUplinkSlots INTEGER (0..maxNrofSlots)
nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1) OPTIONAL
1.25 2(60), 3(120) 2,3,4 16 5 10 20
}
2 Not described 2 4 8 16 32 UL-DL-configuration-common-Set2 ::= TDD-UL-DL-ConfigCommon
2.5 1(15), 2(60), 3(120) 1,2,3,4 8 5 10 20 40
5.0 Not described 4 5 10 20 40 80
10.0 Not described 2 10 20 40 80 160

Allows two different consecutive periods to be
configured. For example: DDDSU+DDSUU
Semi-static Configuration (UE specific)
UE acquires an Information Element (IE) from RRC signaling.
TDD DL/UL DEDICATED CONFIGURATION
dl-UL-TransmissionPeriodicity = {0.5, 0.625, 1, 1.25, 2, 2.5, 5, 10 ms}
1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14
nroDownlinkSymbols nroUplinkSymbols
SlotIndex
TDD-UL-DL-ConfigDedicated ::= SEQUENCE {
slotSpecificConfigurationsToAddModList SEQUENCE (SIZE (1..maxNrofSlots))
OF TDD-UL-DL-SlotConfig OPTIONAL
slotSpecificConfigurationsToreleaseList SEQUENCE (SIZE (1..maxNrofSlots))
OF TDD-UL-DL-SlotIndex OPTIONAL
}
TDD-UL-DL-SlotConfig ::= SEQUENCE {

slotIndex TDD-UL-DL-SlotIndex,
symbols CHOICE {
allDownlink NULL,
allUplink NULL,
explicit SEQUENCE {
nrofDownlinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL,
nrofUplinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL
}
}
}
TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrofSlots-1)

UE group dynamic configuration with SFI Format
0
0
D
1
D
2
D
3
D
4
D
5
D
Symbol number in a slot
6
D
7
D
8
D
9
D
10
D
11
D
12
D
13
D
1 U U U U U U U U U U U U U U
2 X X X X X X X X X X X X X X
3 D D D D D D D D D D D D D X
• SFI (Slot Format Indicator) is transmitted in group- 4
5
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
X
X
X
X
X
common PDCCH 6
7
8
D
D
X
D
D
X
D
D
X
D
D
X
D
D
X
D
D
X
D
D
X
D
D
X
D
D
X
D
X
X
X
X
X
X
X
X
X
X
X
X
X
U
• can be UE specific, different in every TTI, 9

10
11
X
X
X
X
U
X
X
U
U
X
U
U
X
U
U
X
U
U
U
U
X X
U
U
X
U
U
X
U
U
X
U
U
X
U
U
U
U
U
U
U
U
• mechanism to enable Dynamic TDD

12 X X X U U U U U U U U U U U
13 X X X X U U U U U U U U U U
14 X X X X X U U U U U U U U U
3GPP 38.211 Table 4.3.2-3

• Can be group of UE specific: Details in 3GPP 38.213 f40
15 X X X X X X U U U U U U U U
16 D X X X X X X X X X X X X X
17 D D X X X X X X X X X X X X
Chapter 11.1.1 18
19
D
D
D
X
D
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
U
20 D D X X X X X X X X X X X U
21
22
D
D
D
X
D
X
X
X
X
X
X
X
X = unspecified
X
X
X
X
X
X
X
X
X
X
X
X
X
U
U
U
23 D D X X X X X X X X X X U U
24 D D D X X X X X X X X X U U
25 D X X X X X X X X X X U U U
26 D D X X X X X X X X X U U U
27 D D D X X X X X X X X U U U
28 D D D D D D D D D D D D X U
29 D D D D D D D D D D D X X U
30 D D D D D D D D D D X X X U
31 D D D D D D D D D D D X U U
32 D D D D D D D D D D X X U U
33 D D D D D D D D D X X X U U
34 D X U U U U U U U U U U U U
35 D D X U U U U U U U U U U U
36 D D D X U U U U U U U U U U
37 D X X U U U U U U U U U U U
38 D D X X U U U U U U U U U U
39 D D D X X U U U U U U U U U
40 D X X X U U U U U U U U U U
41 D D X X X U U U U U U U U U
42 D D D X X X U U U U U U U U
43 D D D D D D D D D X X X X U
44 D D D D D D X X X X X X U U
45 D D D D D D X X U U U U U U
46 D D D D D X U D D D D D X U
47 D D X U U U U D D X U U U U
48 D X U U U U U D X U U U U U
49 D D D D X X U D D D D X X U
50 D D X X U U U D D X X U U U
51 D X X U U U U D X X U U U U
52 D X X X X X U D X X X X X U
53 D D X X X X U D D X X X X U
54 X X X X X X X D D D D D D D
55 D D X X X U U U D D D D D D
56 – 255 Reserved

Frame Structure Candidates
1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Case 1: 2.5 ms (DDDSU), Special Slot = 10DL:2GP:2UL

DDDSU Asia promotes
DL UL
Case 2: 2.5 ms + 2.5 ms (DDDSU+DDSUU), Special Slot = 10DL:2GP:2UL
DL UL UL UL
Case 3: 2.5 ms (DDSUU), Special Slot = 12DL:2GP
DL UL UL UL UL
Case 4: 2 ms (DDSU), Special Slot = 12DL:2GP
DDSU E// promotes
DL UL
Case 5: 2.5 ms self contained slot (DDDUU), Special Slot = 12DL:1GP:1UL and Compatible with LTE
1DL:1GP:12UL Nokia initial configuration 2
DL UL
Case 6: 5 ms (DDDDDDDSUU), Special Slot = 6DL:4GP:4UL
DL UL UL
DL/UL switching Max number of SSB Relative DL peak T-

Frame Structure Latency
period beam sweepings put
DDDSU 2.5 ms ms ~4 7 ~0.9
DDSU 2 ms ~3 ms 6 ~0.8
DDDDDDDSUU 5 ms 5 to 10 ms 8 1

Inter Vendor Switching Coordination
• Vendor A • Vendor B • Vendor C
Huawei 5G RAN 2.1

NRDUCell.SlotAssignment = 4_1_DDDSU; [4_1_DDDSU, 8_2_DDDDDDDSUU, 7_3_DDDSUDDSUU]
§ Negotiation will be required, to align TDD frame structure between operators and between countries.
§ Future change in switching patterns or UL/DL ratios will be a challenge as new negotiations must take place.
§ Initial use case for 5G-NR is eMBB, which is not “compatible” with low latency services (URLLC)
Frame Structure Ericsson Huawei Nokia

TDD pattern DDDSU (4:1) DL:UL 5G NR 19.Q1 5G RAN2.0 5G19 Nokia is not the
TDD pattern DDSU (3:1) DL:UL 5G NR 18.Q4 same structure as
TDD pattern DDDDDDDSUU (4:1) DL:UL 5G NR 19.Q1 5G RAN2.0 5G19 others

Huawei 5G RAN 2.1 parameters
Huawei 5G RAN 2.1

NRDUCell.SlotAssignment = 4_1_DDDSU; [4_1_DDDSU, 8_2_DDDDDDDSUU, 7_3_DDDSUDDSUU]
NRDUCell.SlotStructure = ; [SS1, SS2, SS3, SS4, SS5, SS6, SS51, SS52, SS53, SS54, SS55, SS56, SS101,
SS102, SS103, SS104, SS105, SS106, SS201, SS202, SS203, SS204, SS205, SS206
Slot Structure Frequency Slot Assignment # of DL symbols GP # of UL symbols

SS1 Sub6 DDDSU 11 1 2
SS51 Sub12 DDDDDDSUU 9 1 4
SS101 Sub18 DDDSUDDSUU 11 1 2
SS201 mmWave DDDSU 12 1 1
LTE TDD Compatible Frame Structure
TDD frame structure DDDDDDDSUU (or alternatively called DDDSUUDDDD) , SCS 30 kHz
• Required for co-deployment of LTE and NR in adjacent frequency bands
• For example in Band 42/43 some mobile operators may be running LTE or Wimax and new-coming NR will need to adapt
to existing networks
LTE Subframe = 1 ms
Frame Configuration = 2 Special subframe = 4
5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
D S U D D D S U D D D S U D D
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
D D D D D D D S U U D D D D D D D S U U
Offset = 3 LTE
subframes NR Slot for 30kHz = 0.5 ms
Time Offset needs to be

configured to align UL/DL
between NR and LTE

Slot Configuration and Cell Radius
• Number of unspecific symbols also defines max cell radius. Numerology effects the symbol duration:
or Delay Spread
MaxRadius =
(NumberOfSymbs*OFDMSymbDuration-NLOS-SyncErr-DL_ULSwitch)*SpeedOfLight/2
Numerology 0 1 2 3
SCS [kHz] 15 30 60 120
OFDM
duration 71,35 35,68 17,84 8,92
1 8,6 3,3 0,6 -0,8
No of undefined OFDM sym. (guard period)
2 19,3 8,6 3,3 0,6
3 30,0 14,0 5,9 1,9
4 40,8 19,3 8,6 3,3
Max cell radius [km]
5 51,5 24,7 11,3 4,6

6 62,2 30,0 14,0 5,9
7 72,9 35,4 16,7 7,3
8 83,6 40,7 19,3 8,6
9 94,3 46,1 22,0 10,0
10 105,0 51,4 24,7 11,3
11 115,8 56,8 27,4 12,6
12 126,5 62,1 30,0 14,0
13 137,2 67,5 32,7 15,3
14 147,9 72,8 35,4 16,7
=(2 * 35.68µs-1µs-3µs-10µs)*c/2 = 8.6 km (Huawei calculation 7.25km)

Without Synchronization in 5G-NR TDD
No Time Synch:
• to avoid interference, guard bands between
operators are required
• Operator specific receiver filter design required
(expensive) Operator A Operator B Operator C
Sub-band 1 Sub-band 2 Sub-band 3
With Time Synch: 85MHz 85MHz 85MHz
• Global eco-system (common HW) 3400 MHz GB ≥25MHz GB ≥25MHz 3700 MHz
• Band specific receiver and filter design Spurious emission
requirements <-43dBm/5MHz
Operator A Operator B Operator C

Sub-band 1 Sub-band 2 Sub-band 3
100MHz 100MHz 100MHz
3400 MHz 3700 MHz

Synchronization in 5G-NR TDD
• General requirement on 5G-NR synchronization accuracy are the same as in LTE.
All gNBs must be time synchronized within:
(IEEE1588v2 or GPS can be used)
±1.5µs
• However also synchronization among all operators using the same frequency band is necessary (otherwise PIM and
spurious emissions may cause UL-DL interference.
• Achieved by standardizing beginning of the radio frame (specifically SFN) to epoch (known point in time).
• International cooperation also required.
Operator A DL DL DL GP UL UL DL DL
<1.5µs
Operator B DL DL DL GP UL UL DL DL
Operator A DL DL DL GP UL UL DL DL
>1.5µs
Operator B DL DL DL GP UL UL DL DL
UL-DL Interference 11
5

DDDSU vs DDSU
10:2:2 vs 12:2:0
Examples DL MAC T-put (FR1; BW=100MHz, 4 layers; 30kHz SCS; 256QAM;PDCCH=1 sym):
DDSU
S=12:2:0
1867,924 Mbps MAC layer T-put calculation shows
DDSU (excluding PDCCH OFDM symbols) 1614,156 Mbps 8.46% drop between DDDSU and
DDSU 1712,284 Mbps -8,46% DDSU
S=10:2:2
DDSU (excluding PDCCH OFDM symbols) 1614,156 Mbps
DDDSU 2005,536 Mbps -8,46% DDSU/DDDSU
S=12:2:0
DDDSU (excluding PDCCH OFDM symbols) 1763,27 Mbps
DDDSU 1881,024 Mbps Ericsson claims, to fully utilize DL T-put, UL
S=10:2:2 TCP ACKs will need between 5 to 10% of DL
DDDSU (excluding PDCCH OFDM symbols) 1763,27 Mbps capacity. With DDDSU configuration, we are
7,24% UL/DL ratio
on an edge.
Examples UL MAC T-put (FR1; BW=100MHz, 1 layers; 30kHz SCS; 64QAM;PUCCH=4PRBs): 5,30% UL/DL ratio
DDSU (excluding PUCCH PRBs) 116,804 Mbps
S=10:2:2
DDDSU (excluding PUCCH PRBs) 93,4432 Mbps +25,00% DDSU/DDDSU
DDSU has 25% better T-put than DDDSU

NR Physical Channels

5G-NR Physical Channels and signals
Primary and Secondary Synchronization Signal
• Similar design as in LTE: PSS/SSS
- used for time/frequency synchronization and cell search procedure
Physical Broadcast Channel
PBCH
- Carries cell/network specific system information
Physical Downlink Control Channel
Downlink Uplink PDCCH - Transmits DL control signaling: Uplink scheduling grants, Downlink scheduling allocations,
power control commands
Downlink
Physical Downlink Shared Channel
PDSCH
- contains DL user data
Physical Physical Demodulation Reference Signals
Channels Channels DMRS - Used for downlink data demodulation (channel adaptation) and time-frequency
synchronization
• PBCH • PRACH Phase Tracking Reference Signals
• PDCCH • PUCCH PTRS
- tracks and compensate downlink phase noise
• PDSCH • PUSCH Channel State Information – Reference Signal
CSI-RS
- Used for DL channel measurement, beam management, enhanced time-frequency tracking
Physical Random Access Channel
PRACH
Physical Physical - carries random access preambles for IDLE users
Signals Signals Physical Uplink Control Channel
PUCCH
• DM-RS - transmits UL control signaling: HARQ feedback, CQI feedback, Scheduling Requests
• PSS
Physical Uplink Shared Channel
• SSS • PTRS PUSCH
Uplink - contains UL user data
• DM-RS • SRS Demodulation Reference Signals
• PTRS DMRS
- used for UL data demodulation, time-frequency synchronization
• CSI-RS Phase Tracking Reference Signals
PTRS
- Tracks and compensates uplink phase noise
Sounding Reference Signals
SRS
-used for uplink measurement and beam management

5G-NR Channel Mapping
Broadcast Paging DL User DL User DL User UL User

Information Requests Signaling Data Signaling Data
PDCP Layer SRB 0 SRB 1 DRB SRB 0 SRB 1 DRB
Logical RRC Signaling RRC Signaling
Channel BCCH PCCH CCCH DCCH DTCH CCCH DCCH DTCH
SIB
RLC Layer MIB
Transport
Channel BCH PCH D-SCH U-SCH RACH
MAC Layer DCI
Physical
Channel PBCH PDCCH PDSCH PUCCH PUSCH PRACH
PHY Layer
Physical DM -
PTRS SRS
DM -
PTRS
PSS SSS CSI -RS
Signals RS RS
DL UL

DL Physical Channels

PSS & SSS – Synchronization signal block
Frequency domain:
• Can have an arbitrary frequency position in carrier bandwidth (unlike LTE, where it is 239
Zero power P
always center position). New concept of Synchronization Signal Block which combines B
PSS, SSS and PBCH and transmitted together. C
20 Resource blocks = 240 subcarriers

• The quantity 𝑘NNt is the subcarrier offset from subcarrier 0 in common resource block H
NNt 192
𝑁O*t to subcarrier 0 of the SS/PBCH block. 𝑘NNt is broadcasted in PBCH.
PSS & SSS characteristics: 182 P P
P B S B
• Mapped to 127 subcarriers around a lower end of the bandwidth (subcarrier 80 – S S
206) C C
S S
H H
• Used for UEs downlink synchronization 56
47
P
Huawei 5G RAN 2.1 B
NRDUCell.SSBPeriod =20ms; [20MS, 40MS, 80MS, 160MS] C
NRDUCell.SsbDescMethod = SSB_DESC_TYPE_NARFCN; [SSB_DESC_TYPE_NARFCN, H
0
SSB_DESC_TYPE_GSCN] Subcarrier 0
0 1 2 3
- Absolute Frequency, or Global Synchronization Channel Number
OFDM Symbol
NRDUCell.SsbFreqPos = ; [2~26639,151600~160600, 361000~376000, 499200~537999, 620000~680000,
693334~733333, 2016667~2104165, 2229167~2279165]

Synchronization Signal Block - Time Domain 3GPP 38.213 Chapter 4.1
Time domain: Transmission pattern more complicated than LTE (period for PBCH 10ms, PSS/SSS 5ms). SSB period depends on SCS, frequency
range and some other parameters. SCS OFDM f ≤ 2.4
2.4 GHz < f ≤ 6 GHz f ≤ 3 GHz 3 GHz < f ≤ 6 GHz 6 GHz < f
Symbol (s) GHz
n = 0,1 n = 0,1,2,3
Case A: 15
{2,8}+14n s= s = 2,8,16,22,30,
kHz
2,8,16,22 36,44,50
All these combinations are More beam sweeping for
n=0 n = 0,1
Case B: 30 {4,8,16,20}+ higher SCS à higher
there to help UE to identify a kHz 28n s= s = 4,8,16,20,32,
2,8,16,20 36,44,48 frequencies and TRX
cell during Cell Search n = 0,1 n = 0,1,2,3
number
Case C: 30 s=
procedure and to enable kHz (TDD) 2,8,16,2
s=
2,8,16,22,30,36,44,50
2
Massive MIMO and Beam {2,8}+14n
n = 0,1 n = 0,1,2,3
Case C: 30
Sweeping technique. kHz (FDD) s= s = 2,8,16,22,30,
2,8,16,22 36,44,50
n = 0,1,2,3,5,6,7,8,10,11,12,13,15,16,17,18
SSB set duration is half frame Case D: {4,8,16,20}+ s = 4,8,16,20,32,36,44,48,60,64,72,76,88,92,100,104,144,148,156,160,172,
(5 ms) and it repeats every 20 120 kHz 28n 176,184,188,200,204,212,216,228,232,240,244,284,288,296,300,312,316,324,328,340

,344,352,356,368,372,380,384,424,428,436,440,452,456,464,468,480,484,492,496,50
8,512,520,524
ms n = 0,1,2,3,5,6,7,8
{8,12,16,20,
Example: Case B, 3 GHz < f ≤ 6 Case E: s = 8,12,16,20,32,36,40,44,64,68,72,76,88,92,96,100,120,124,128,132,144,
32,36,40,44 148,152,156,176,180,184,188,200,204,208,212,288,292,296,300,312,316,320,324,344
240 kHz
GHz, SCS = 30 kHz }+56n ,348,352,356,368,372,376,380,400,404,408,412,424,428,432,436,456,460,464,468,48
0,484,488,492
Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139
PP SP PP SP PP SP PP SP PP SP PP SP PP SP PP SP
S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H
SC SC SC SC SC SC SC SC SC SC SC SC SC SC SC SC
Beam 0 1 2 3 4 5 6 7 ß Beam Sweeping

NR Beam Sweeping, one beam at a
DL DL DL S UL time gives better coverage
LTE
Beam Sweeping and User Measurements
Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4
Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 1001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321
Beams in time
PP SP PP SP PP SP PP SP PP SP PP SP PP SP PP SP
S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H S B HS B H
SC SC SC SC SC SC SC SC SC SC SC SC SC SC SC SC
Beam 0 1 2 3 4 5 6 7
à In 20 ms again
Beam Sweeping Patterns (Nokia)

Beams in space 0 7
elevation
1 6
2 5
1 3 4
UEs measurements 2 azimuth
RSRP of UE1
RSRP of UE2

System Information Broadcast - Beam Sweeping
• Beam sweeping is used to broadcast basic system information.
• Beam sweeping guarantees similar coverage for system information broadcast as for a beam formed PDSCH.
• There are 8 sweeps for 8 different beams (FR1), then the sweeps repeats.
• Massive MIMO antenna (32/64TRX) can create various beam shapes: wide or narrow, for wider coverage or for further
coverage.
Wider horizontal coverage Narrower vertical and horizontal Very narrow beam for
• Public squares beam for longer cell range large distances
• For example: Horizontal • High-rise building • Low-rise building
beamwidth 110° (0 horizontal • For example: Horizontal • For example: Horizontal beamwidth
sweep) & Vertical beamwidth beamwidth 45° (+6°) & Vertical 45° (-32° to +32°) & Vertical
6° (-2° to +9°) beamwidth 25° (-42° to +42°) beamwidth 12° (0° to +6°)
Huawei Default Sweeping Pattern

• For 3 sector site scenario, applicable for 32/64TRX
• Horizontal beamwidth 105° (azimuth 0°) & Vertical beamwidth 6° (tilt -2° to +9°)
Broadcast Beam Patterns (Non-Default in Huawei)
Coverage Coverage Scenario Description Horizontal 3 Vertical 3 dB Tilt Azimuth Adjustment Range
Scenario ID Scenario dB Beamwidth Adjustment
Beamwidth Range
SCENARIO_1 Square Non-standard 3-sector networking is used to provide wide horizontal coverage. This type of configuration 110° 6° –2° to +9° 0°
is suitable for public squares or large buildings. The horizontal coverage in this scenario is better than that
in scenario 2. The coverage near the cell center in this scenario is slightly poorer than that in scenario 2.
SCENARIO_2 Interference Non-standard 3-sector networking is used. When there are strong interference sources in neighboring 90° 6° –2° to +9° –10° to +10°
cells, the horizontal coverage of a cell can be reduced to mitigate the interference from neighboring cells.
This configuration is suitable for low-rise coverage as the vertical coverage angle is the smallest.
SCENARIO_3 Interference Non-standard 3-sector networking is used. When there are strong interference sources in neighboring 65° 6° –2° to +9° •64T (AAU5612 and AAU5613): –
cells, the horizontal coverage of a cell can be reduced to mitigate the interference from neighboring cells. 22° to +22°
This configuration is suitable for low-rise coverage as the vertical coverage angle is the smallest. •32T 16H2V (AAU5313): –22° to
+22°
SCENARIO_4 Building This configuration is for low-rise buildings and hotspot coverage. 45° 6° –2° to +9° –32° to +32°
SCENARIO_5 Building This configuration is for low-rise buildings and hotspot coverage. 25° 6° –2° to +9° –42° to +42°
SCENARIO_6 Mid-rise coverage Non-standard 3-sector networking is used to provide coverage for mid-rise buildings. This configuration 110° 12° 0° to 6° 0°
and public square provides the best horizontal coverage.
SCENARIO_7 Mid-rise coverage Non-standard 3-sector networking is used. When there are strong interference sources in neighboring 90° 12° 0° to 6° –10° to +10°
with interference cells, the horizontal coverage of a cell can be reduced to mitigate the interference from neighboring cells.
This configuration is suitable for covering mid-rise buildings as the vertical coverage angle is larger than
that in SCENARIO_1 to SCENARIO_5.
SCENARIO_8 Mid-rise coverage Non-standard 3-sector networking is used. When there are strong interference sources in neighboring 65° 12° 0° to 6° –22° to +22°
with interference cells, the horizontal coverage of a cell can be reduced to mitigate the interference from neighboring cells.
This configuration is suitable for covering mid-rise buildings as the vertical coverage angle is larger than
that in SCENARIO_1 to SCENARIO_5.
SCENARIO_9 Mid-rise building This configuration is for mid-rise buildings and hotspot coverage. 45° 12° 0° to 6° –32° to +32°
SCENARIO_12 Public square and Non-standard 3-sector networking is used to provide coverage for high-rise buildings and the best 110° 25° 6° 0°
high-rise building horizontal coverage. This configuration is recommended when broadcast channels are required to reflect
the coverage of data channels.
SCENARIO_13 High-rise Non-standard 3-sector networking is used. When there are strong interference sources in neighboring 65° 25° 6° •64T (AAU5612 and AAU5613): –
coverage with cells, the horizontal coverage of a cell can be reduced to mitigate the interference from neighboring cells. 22° to +22°
interference This configuration is suitable for high-rise coverage as the vertical coverage angle is the largest. •32T 16H2V (AAU5313): –22° to
+22°
SCENARIO_14 High-rise building This configuration is for high-rise buildings and hotspot coverage. 45° 25° 6° –32° to +32°

PSS & SSS – PCI and Cell Definition
• Cell and Cell ID concept is still maintained in NR
• PSS & SSS is used for DL synchronization and cell ID (PCI)
• NR PCIs are numbered from 0 to 1007 and divided into 3 groups, with each containing 336 cell IDs
}qcc (M) (h)

𝑃𝐶𝐼: 𝑁|Y = 3 7 𝑁|Y +𝑁|Y = {0, … , 1007}
(h)
𝑃𝑆𝑆: 𝑁|Y ∈ {0,1,2}
(M) }qcc
𝑆𝑆𝑆: 𝑁|Y ∈ {0,1, … , 335} 𝑁|Y 𝑚𝑜𝑑3
Cells with equal “PCI mod 3” will transmit the same PSS,
means UE views PSS transmission from different cells as multipath
and assume that the PSS is received from a single cell.
PCI mod 3 planning still recommended. (Nokia)

PCI mod 3 has little impact on user experience. (Huawei)

NR Cell Flexible Options
• 5G-NR was designed with respect to lean design and CU-DU split
• Hence NR cell scales with control signaling load (Paging, RAR, RACH) and not user plane load.
Independent cells
SS1 SS2 • Different SSBs
UE in RRC Idle or RRC INACTIVE camps on SSB
• No synchronization needed • Different SSB index can have exactly same Access
Configuration (e.g. PRACH config)
TRxPs
• Any cell size, improved coverage • Multiple SS Block indexes can be transmitted from
SS3 Synchronization needed
•
the same antenna
• One NR cell – one SSB
Independent cells
SS1 SS2 • One common SIB area (magenta)
• SFN
SSB4,0 Beam sweeping of same SSB

SS One NR cell
SS SSB B4,1
•
Massive MIMO deployment

B4
•
4, 2
,3

Physical Broadcast Channel
• Physical Broadcast Channel carrier Master Information Block (MIB)
• MIB contains the basic set of parameters which are needed to be able to read DL signal including and demodulate PDCCH
3GPP 38.331 Section 6.2.2 6 most significant bits out of 10 bits. The 4 LSB are conveyed in the PBCH transport block as
MIB ::= SEQUENCE { part of channel coding
systemFrameNumber BIT STRING (SIZE (6)),
For <6GHz the value are either 15 or 30kHz, other values are for mmWaves
subCarrierSpacingCommon ENUMERATED {scs15or60,
scs30or120},
Corresponds to 𝑘NNt (TS 38.213 sec. 4.1, 13) which is a frequency domain offset between
ssb-SubcarrierOffset INTEGER (0..15),
SSB and overall resource block grid in number of subcarriers.
dmrs-TypeA-Position ENUMERATED {pos2, pos3},
pdcch-ConfigSIB1 INTEGER (0..255), Signals common ControlResourceSet (CORESET) a common search space and necessary
cellBarred ENUMERATED {barred, notBarred}, PDCCH parameters
intraFreqReselection ENUMERATED {allowed, 4 MSB: controlResourceSetZero - Defines CORESET of initial DL BWP (i.e. Type0-PDCCH)
notAllowed},
spare BIT STRING (SIZE (1))
4 LSB: searchSpaceZero - Determines PDCCH Monitoring Occasion (i.e. common search
} space)
MIB field descriptions (3GPP 38.331 Section 6.2.2)

cellBarred: Indicates whether the cell allows UEs to camp on this cell, as specified in TS 38.304 [20].
dmrs-TypeA-Position: Position of (first) DL DM-RS. Corresponds to L1 parameter 'DL-DMRS-typeA-pos' (see 38.211, section 7.4.1.1.1)
intraFreqReselection: Controls cell reselection to intra-frequency cells when the highest ranked cell is barred, or treated as barred by the UE, as specified in TS 38.304 [20}.
pdcch-ConfigSIB1: 4LSB: Corresponds to RMSI-PDCCH-Config in TS 38.213, section 4.1 13 - Determines a common search space of initial DL BWP. 4MSB: Determines a bandwidth for PDCCH/SIB, a common ControlResourceSet
(CORESET) a common search space and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that SIB1 is not present, the field pdcch-ConfigSIB1 indicate the frequency positions where the UE may find SS/PBCH
block with SIB1 or the frequency range where the network does not provide SS/PBCH block with SIB1 (see TS 38.213 [13], section 13).
ssb-SubcarrierOffset: Corresponds to (see TS 38.213, section 4.1), which is the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. (See 38.211, section 7.4.3.1).
The value range of this field may be extended by an additional most significant bit encoded within PBCH as specified in 38.213 [13].
This field may indicate that this cell does not provide SIB1 and that there is hence no common CORESET (see TS 38.213 [13], section 13). In this case, the field pdcch-ConfigSIB1 may indicate the frequency positions where the UE
may (not) find a SS/PBCH with a control resource set and search space for SIB1 (see 38.213 [13], section 13).
12and the value
subCarrierSpacingCommon: Subcarrier spacing for SIB1, Msg.2/4 for initial access and broadcast SI-messages. If the UE acquires this MIB on a carrier frequency <6GHz, the value scs15or60 corresponds to 15 Khz
scs30or120 corresponds to 30 kHz. If the UE acquires this MIB on a carrier frequency >6GHz, the value scs15or60 corresponds to 60 Khz and the value scs30or120 corresponds to 120 kHz. 8
systemFrameNumber: The 6 most significant bit (MSB) of the 10 bit System Frame Number. The 4 LSB of the SFN are conveyed in the PBCH transport block as part of channel coding (i.e. outside the MIB encoding).
DM-RS for PBCH (SSB)
The picture on right side is drawn from this table: 239
3GPP 38.211 f40 Table 7.4.3.1-1: Resources within an SS/PBCH
P 𝑃𝐶𝐼𝑚𝑜𝑑4 = 0 𝑃𝐶𝐼𝑚𝑜𝑑4 = 1
Zero power
block for PSS, SSS, PBCH, and DM-RS for PBCH B
Channel or signal OFDM symbol number 𝑙 Subcarrier number 𝑘 12 12
C
20 Resource blocks = 240 subcarriers

relative to the start of an relative to the start of an SS/PBCH
SS/PBCH block block 11 11
PSS
SSS
0
2
56, 57, …, 182
56, 57, …, 182
192 H 10 10
Set to 0 0 0, 1, …, 55, 183, 184, …, 239
2 48, 49, …, 55, 183, 184, …, 191 182 P P 9 9
PBCH
1, 3
2
0, 1, …, 239
0, 1, …, 47, 192, 193, …, 239
PB SB 8 8
DM-RS for PBCH

1, 3 0 + 𝑣, 4 + 𝑣, 8 + 𝑣, … . , 236 + 𝑣
0 + 𝑣, 4 + 𝑣, 8 + 𝑣, … , 44 + 𝑣
SC SC 7 7
2
192 + 𝑣, 196 + 𝑣, … , 236 + 𝑣 56 SHSH 6 6
47 5 5
Frequency position of PBCH DM-RS P 4 4
is determined by PCI mod 4. 𝑣= }qcc
𝑁|Y 𝑚𝑜𝑑4 B 3 3
Separation can be achieved by PCI i.e.

0
C 2 2
mod 4 planning, however there is still 𝑣 = 𝑃𝐶𝐼 𝑚𝑜𝑑4 H 1 1
DM-RS to PBCH or vice versa Subcarrier 0 0 1 2 3 0 0

interference. Therefore no planning OFDM Symbol
0 1 2 3 0 1 2 3
is required. PBCH DM-RS PBCH DM-RS

SIB 1 Location Definition
• MIB > pdcch-ConfigSIB1 (8bits) > (4 MSB)common controlResourceSetZero (CORESET) of initial DL BWP > 4 bits in table
below:
3GPP 38.213 Table 13-1: Set of resource blocks and slot symbols of control resource set for Type0- This is a first table out of 15. So many for various combinations
PDCCH search space when {SS/PBCH block, PDCCH} subcarrier spacing is {15, 15} kHz for frequency of SSB and PDCCH subcarrier spacing and BWs.
bands with minimum channel bandwidth 5 MHz or 10 MHz
SS/PBCH block and control resource set Number of RBs Number of Symbols Yes: SSB and PDCCH may have different SCS, on a top of that
Index Offset (RBs)
multiplexing pattern 𝑵𝑪𝑶𝑹𝑬𝑺𝑬𝑻
𝑹𝑩 𝑵𝑪𝑶𝑹𝑬𝑺𝑬𝑻
𝒔𝒚𝒎𝒃 carrier BW also may change (5,10,40)
0 1 24 2 0
1 1 24 2 2
2 1 24 2 4
3 1 24 3 0
4 1 24 3 2
5 1 24 3 4
6 1 48 1 12
7 1 48 1 16
8 1 48 2 12 Huawei 5G RAN 2.1
9 1 48 2 16
10 1 48 3 12 NRDUCell.Sib1Period =20ms; [20MS, 40MS, 80MS, 160MS]
11 1 48 3 16
12 1 96 1 38
13 1 96 2 38
14 1 96 3 38
15 Reserved
From the Common CORESET monitoring, UE reads SI-RNTI and eventually reads SIB1.

SIB 1 Freq Location Definition for 3,5GHz and SCS=30Khz
• MIB à pdcch-ConfigSIB1 (8bits) à (4 MSB)common controlResourceSetZero (CORESET) of initial DL BWP à 4

bits in table below:
3GPP 38.213 Table 13-6: Set of resource blocks and slot symbols of control resource set for
Type0-PDCCH search space when {SS/PBCH block, PDCCH} subcarrier spacing is {30, 30} kHz for
frequency bands with minimum channel bandwidth 40MHz Table number 6, for Early Deployment: Band 78,
SS/PBCH block and control Number of Number of BW=100MHz, SCS= 30kHz
Index resource set multiplexing RBs Symbols Offset (RBs)
pattern 𝑪𝑶𝑹𝑬𝑺𝑬𝑻
𝑵𝑹𝑩 𝑵𝑪𝑶𝑹𝑬𝑺𝑬𝑻
𝒔𝒚𝒎𝒃
0 1 24 2 0
1 1 24 2 4
2 1 24 3 0
3 1 24 3 4
4 1 48 1 0
5 1 48 1 28
6 1 48 2 0
7 1 48 2 28
8 1 48 3 0
9 1 48 3 28
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
From the Common CORESET monitoring, UE reads SI-RNTI and eventually reads SIB1.
SIB 1 Time Location Definition for 3,5GHz and SCS=30Khz
• MIB à pdcch-ConfigSIB1 (8bits) à (4 LSB) Type0-PDCCH Common Search Space à 4 bits in table below:
ep\`q,6
For SS/PBCH block with index 𝑖, the UE determines an index of slot 𝑛i as 𝑛i = 𝑂 7 26 + 𝑖 7 𝑀 𝑚𝑜𝑑𝑁^cb] located in a frame
ep\`q,6
with system frame number (SFN) 𝑆𝐹𝑁O satisfying 𝑆𝐹𝑁O 𝑚𝑜𝑑 2 = 0 if 𝑂 7 26 + 𝑖 7 𝑀 /𝑁^cb] 𝑚𝑜𝑑2 = 0 of in a frame with
ep\`q,6
SFN satisfying 𝑆𝐹𝑁O satisfying 𝑆𝐹𝑁O 𝑚𝑜𝑑 2 = 1 if 𝑂 7 26 + 𝑖 7 𝑀 /𝑁^cb] 𝑚𝑜𝑑2 = 1. The index for the first symbol of the
CORESET in slot 𝑛O is the first symbol index provided by Table 13-11 and 13-12
ep\`q,6 3GPP 38.213 Table 13-11: Parameters for PDCCH monitoring occasions for
Slot index: 𝑛i = 𝑂 7 26 + 𝑖 7 𝑀 𝑚𝑜𝑑𝑁^cb] Type0-PDCCH CSS set - SS/PBCH block and CORESET multiplexing pattern 1
0 ≫ 𝑆𝐹𝑁O 𝑚𝑜𝑑 2 = 0 Number of and FR1
ep\`q,6
In which SFN 𝑂 7 26 + 𝑖 7 𝑀 /𝑁^cb] 𝑚𝑜𝑑2 = ™ Index 𝑶 search space 𝑴 First symbol index
1 ≫ 𝑆𝐹𝑁O 𝑚𝑜𝑑 2 = 1 sets per slot
0 0 1 1 0
OW*'N'&
1 0 2 1/2 {0, if 𝑖 is even}, {𝑁^_à , if is odd}
Example: Type0-PDCCH CSS (4LSB of pdcch-ConfigSIB1) = 0, received Beam ID by UE 𝑖 = 2 2 1 1 0
2, 𝜇 = 1 3 2 2 1/2 OW*'N'&
{0, if 𝑖 is even}, {𝑁^_à , if is odd}
ep\`q,6 4 5 1 1 0
Slot index 𝑛i = 𝑂 7 26 + 𝑖 7 𝑀 𝑚𝑜𝑑𝑁^cb] = 0 7 2 + 𝑖 7 1 𝑚𝑜𝑑20 = 2 OW*'N'&
5 5 2 1/2 {0, if 𝑖 is even}, {𝑁^_à , if is odd}
6 ep\`q,6
SFN: 𝑂 7 2 + 𝑖 7 𝑀 /𝑁^cb] 𝑚𝑜𝑑2 = 0 7 2 + 2 7 1 /20 𝑚𝑜𝑑2 = 0 à 6 7 1 1 0
OW*'N'&
𝑆𝐹𝑁O 𝑚𝑜𝑑 2 = 0 7 7 2 1/2 {0, if 𝑖 is even}, {𝑁^_à , if is odd}
8 0 1 2 0
4LSB of pdcch-
Beam ID slot index (n0) SFN_C 9 5 1 2 0
ConfigSIB1
10 0 1 1 1
0 0 0 even
1 0 1 even
11 0 1 1 2
2 0 2 even 12 2 1 1 1
3 0 3 even 13 2 1 1 2
4 0 4 even 14 5 1 1 1
5 0 5 even 15 5 1 1 2
6 0 6 even
7 0 7 even

SIB 1 Time Domain Allocation for SIB1 on PDSCH
• SIB1 is signaled on CORESET 0, with a help of DCI Format 1_0 with CRC scrambled by SI_RNTI:
38.212 Chapter 7.3.1.2.1 Format 1_0
Field (Item) Bits Reference
Frequency domain resource Y%,tuf Y%,tuf Y%,tuf
assignment 𝑙𝑜𝑔h 𝑁*t 𝑁*t + 1 /2 𝑁*t is a size of CORESET 0
Potentially SIB1 may have shorter than one slot time
defined in Subclause 5.1.2.1 of [6, allocation
Time domain resource assignment 4
TS38.214]
According to 38.212 Table 38.214 Table 5.1.2.1.1-2: Default PDSCH time domain resource allocation A for normal CP
7.3.1.1.2-33 Row index dmrs-TypeA- PDSCH K0 S L
VRB-to-PRB mapping 1 Position mapping type
0 : Non-Interleaved
1 2 Type A 0 2 12
1 : Interleaved
3 Type A 0 3 11
Subclause 5.1.3 of (TS38.214), 2 2 Type A 0 2 10
Modulation and coding scheme 5 3 Type A 0 3 9
using Table 5.1.3.1-1
3 2 Type A 0 2 9
defined in Table 7.3.1.1.1-2 3 Type A 0 3 8
Redundancy version 2
(TS38.212) 4 2 Type A 0 2 7
3 Type A 0 3 6
defined in Table 7.3.1.2.1-2 5 2 Type A 0 2 5
System information indicator 1
(TS38.212) 3 Type A 0 3 4
Reserved bits 15 6 2 Type B 0 9 4
3 Type B 0 10 4
7 2 Type B 0 4 4
38.214 Table 5.1.2.1.1-1: Applicable PDSCH time domain resource allocation 3 Type B 0 6 4
RNTI PDCCH SS/PBCH block pdsch-ConfigCommon pdsch-Config PDSCH time domain resource 8 2,3 Type B 0 5 7
search and CORESET includes pdsch- includes pdsch- allocation to apply 9 2,3 Type B 0 5 2
space multiplexing TimeDomainAllocation TimeDomainAllocati 10 2,3 Type B 0 9 2
pattern List onList 11 2,3 Type B 0 12 2
SI-RNTI Type0 1 - - Default A for normal CP 12 2,3 Type A 0 1 13
common 2 - - Default B 13 2,3 Type A 0 1 6
3 - - Default C 14 2,3 Type A 0 2 4
SI-RNTI Type0A 1 No - Default A 15 2,3 Type B 0 4 7
common 2 No - Default B 16 2,3 Type B 0 8 4
3 No - Default C
1,2,3 Yes - pdsch-
TimeDomainAllocationList Start Length
provided in pdsch-
ConfigCommon
For 100MHz cell BW, PDSCH SCS=30kHz, SSB SCS=30kHz, see: 3GPP 38.213 Table 13-6
Reading System Information
Case 1: No stored info in UE, No OnDemand SI indication
The reading of SI varies depending of two cases: 1. Power on
PDCCH: 2. Search Cell and Decode MIB
• Paging indicator 3. Store the decoded MIB
• Transport format of
4. Check if CellBarred = barred, stop there and if not,
PDSCH
move to next step.
5. Using the parameters in MIB, try decoding SIB1.
PDCCH
PDCCH
PSS PSS PSS PSS
SSS
PBCH PDSCH
SSS
PBCH
SSS
PBCH PDSCH
SSS
PBCH
6. [if SIB1 decoding is successful] store the information
and then move to next step.
7. [assuming that SIB1 indicate No On-Demand SI] Decode
PDSCH:
MIB: Other SIBs (SI)
• Broadcasted minimum SI (e.g. SIB1 and Case 2: No stored info in UE, OnDemand SI indication
• SFN SIB2)
• PDCCH • Broadcasted additional SIBs if indicated in 1. Power On
configuration SIB1 2. Search Cell and Decode MIB
• On-demand transmission pf other SIBs 3. Store the decoded MIB
• Paging messages
4. Check if CellBarred = barred, stop there and if not, move to next step.
5. Using the parameters in MIB, try decoding SIB1.
6. [if SIB1 decoding is successful] store the information and then move to next step.
7. [assuming that SIB1 indicate On-Demand SI] Check the RRC Status (NOTE : Based on
38.331-5.2.2.3.3]
a) if RRC Status is in RRC_IDLE or RRC_INACTIVE
• Trigger lower layer to initiate preamble transmission procedure
• Acquire the requested SI messages when Acknowledgement for SI request is
received
a) if RRC Status is in RRC_CONNECTED
• [Process is not defined yet.]
SIB 1 SA (in rel15.3 still not fully completed) 3GPP 38.331 Section 6.2.2
• System Information Block 1 contains SSB related parameters, DL/UL frame configuration common and SUL related
parameters. Currently does not contain Parameters as we know it from LTE, e.g. PLMN ID, cell selection parameters.
SIB1 ::=SEQUENCE { ServingCellConfigCommonSIB
CellAccessRelatedInfo ::=
ConnEstFailureControl ::=::=
SEQUENCESEQUENCE
{ {
-- FFS / TODO: Add other parameters. downlinkConfigCommon
plmn-IdentityList
connEstFailCount DownlinkConfigCommonSIB,
PLMN-IdentityInfoList,
ENUMERATED {n1, n2, n3, n4},
uplinkConfigCommon
cellReservedForOtherUse UplinkConfigCommonSIB
ENUMERATED {s30,
{true}s60,
OPTIONAL,
s120, s240, s300, -- Need R OPTIONA
frequencyOffsetSSB ENUMERATED {khz-5, khz5} OPTIONAL, connEstFailOffsetValidity
-- Need R ENUMERATED s420, s600, s900},
supplementaryUplink
...
connEstFailOffset UplinkConfigCommonSIB
INTEGER (0..15) OPTIONA
ssb-PositionsInBurst SEQUENCE {
}
} n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 } OPTIONA
inOneGroup BIT STRING (SIZE (8)), ssb-PositionsInBurst SEQUENCE {
groupPresence BIT STRING (SIZE (8)) OPTIONAL -- Cond above6GHzOnly
inOneGroup BIT STRING (SIZE (8)),
}, groupPresence BIT STRING (SIZE (8)) OPTIONA
ssb-PeriodicityServingCell ENUMERATED },
{ms5, ms10, ms20, ms40, ms80, ms160, spare1, spare2},
ss-PBCH-BlockPower INTEGER (-60..50), ssb-PeriodicityServingCell ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160},
tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONA

uplinkConfigCommon UplinkConfigCommon OPTIONAL,
ss-PBCH-BlockPower INTEGER (-60..50),
supplementaryUplink SEQUENCE {
...
uplinkConfigCommon UplinkConfigCommon OPTIONAL
}
-- FFS: Add additional (selection) criteria determining when/whether the UE shall use the SUL frequency
} OPTIONAL, -- Cond SUL
tdd-UL-DL-Configuration TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD

tdd-UL-DL-configurationCommon2 TDD-UL-DL-ConfigCommon UplinkConfigCommonSIB
OPTIONAL, -- Cond TDD ::= SEQUENCE {
frequencyInfoUL FrequencyInfoUL-SIB,
initialUplinkBWP BWP-UplinkCommon,
pdcch-ConfigCommon PDCCH-ConfigCommon OPTIONAL,
timeAlignmentTimerCommon TimeAlignmentTimer
pucch-ConfigCommon PUCCH-ConfigCommon OPTIONAL, }
lateNonCriticalExtension OCTET STRING OPTIONAL,

nonCriticalExtension SEQUENCE{} OPTIONAL
}
BWP-UplinkCommon ::= SEQUENCE {
genericParameters BWP,
rach-ConfigCommon SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need M
pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon } OPTIONAL, -- Need M
pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon } OPTIONAL, -- Need M
... 13
} 5

Other SIBs
SIB2 - cell re-selection information common for intra-frequency, inter-frequency and/ or inter-RAT cell re-selection
SIB3 - neighbouring cell related information relevant only for intra-frequency cell re-selection
SIB4 - information relevant only for inter-frequency cell re-selection i.e. information about other NR frequencies and inter-
frequency neighbouring cells
SIB5 - information relevant only for inter-RAT cell re-selection i.e. information about E-UTRA frequencies and E-UTRAs
neighbouring cells
SIB6 - contains an ETWS primary notification
SIB7 - contains an ETWS secondary notification
SIB8 - CMAS notification
SIB9 - information related to GPS time and Coordinated Universal Time (UTC). NOTE: The UE may use the time
information for numerous purposes, possibly involving upper layers e.g. to assist GPS initialisation, to synchronise the UE
clock

SIB 2 (SA)
SIB2 ::= SEQUENCE {
cellReselectionInfoCommon SEQUENCE {
nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need R
absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R
rangeToBestCell RangeToBestCell OPTIONAL, -- Need R
q-Hyst ENUMERATED {
dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10,
dB12, dB14, dB16, dB18, dB20, dB22, dB24}, intraFreqCellReselectionInfo SEQUENCE {
speedStateReselectionPars SEQUENCE { q-RxLevMin Q-RxLevMin,
mobilityStateParameters MobilityStateParameters, q-RxLevMinSUL Q-RxLevMin OPTIONAL
q-HystSF SEQUENCE { q-QualMin Q-QualMin OPTIONAL
sf-Medium ENUMERATED { s-IntraSearchP ReselectionThreshold,
dB-6, dB-4, dB-2, dB0}, s-IntraSearchQ ReselectionThresholdQ OPTIONAL
sf-High ENUMERATED { t-ReselectionNR T-Reselection,
dB-6, dB-4, dB-2, dB0}
frequencyBandList MultiFrequencyBandListNR-SIB OPTIO
}
frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIO
} OPTIONAL,
p-Max P-Max OPTIONAL
},
smtc SSB-MTC OPTIONAL
cellReselectionServingFreqInfo SEQUENCE {
ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL
s-NonIntraSearchP ReselectionThreshold OPTIONAL, -- Need R
s-NonIntraSearchQ ReselectionThresholdQ OPTIONAL, -- Need R ssb-ToMeasure SSB-ToMeasure OPTIONAL
threshServingLowP ReselectionThreshold, deriveSSB-IndexFromCell BOOLEAN,
threshServingLowQ ReselectionThresholdQ OPTIONAL, -- Need R ...
cellReselectionPriority CellReselectionPriority, },
cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R ...
... }
},
RangeToBestCell ::= Q-OffsetRange

CORESET (Control Resource Set)
PDCCH 2
• CORESET is made up of multiple resource blocks in frequency domain and 1, 2 or 3 OFDM with 8 CCEs
Symbols in time domain. Called also Control Region it has a similar function as PDCCH in LTE,
12 Subcarriers = 1RB
however in NR the frequency domain size is not fixed and there may be several of them.
CORESET #1
Parameter Description
OW*'N'& Number of RBs in frequency domain in a CORESET. Determined by RRC Parameter CORESET-freq-dom
𝑁*t
(step 6 PRBs)
OW*'N'& Number of symbols in time domain in a CORESET. Determined by RRC Parameter CORESET-time-dur. This
𝑁^_à
can be 1 or 2 or 3, but 3 is possible only when DL-DMRS-typeA-pos = 3
OW*'N'&
𝑁*'œ Number of REGs in a CORESET
L REG Bundle Size, set by CORESET-REG-bundle-size
Value 0 identifies the common CORESET configured in MIB

ControlResourceSet ::= SEQUENCE { Values 1..maxNrofControlResourceSets-1 identify CORESETs configured by dedicated signaling
controlResourceSetId ControlResourceSetId, The controlResourceSetId is unique among the BWPs of a ServingCell.
frequencyDomainResources BIT STRING (SIZE (45)),
duration INTEGER (1..maxCoReSetDuration),//maxCoReSetDuration = 3
cce-REG-MappingType CHOICE { Should be within BWP assigned to UE
interleaved SEQUENCE { Each bit corresponds a group of 6 RBs, with grouping starting from PRB 0,
reg-BundleSize ENUMERATED {n2, n3, n6}, which is fully contained in the BWP within which the CORESET is configured.
interleaverSize ENUMERATED {n2, n3, n6},
shiftIndex INTEGER(0..maxNrofPhysicalResourceBlocks-1)
}, 1, 2, 3 OFDM Symbols
nonInterleaved NULL
},,
precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs},
tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId
tci-PresentInDCI ENUMERATED {enabled} OPTIONAL CORESET is UE specific,
}
pdcch-DMRS-ScramblingID BIT STRING (SIZE (16)) OPTIONAL
multiple can be
configured to one UE
From CORESET to CCE CORESET
Frequency span in
1 OFDM Symbol = 1 Resource Element multiples of 6 RBs
12 Resource Elements = 1 Resource Element Group (REG) = 1 Common Control Element (CCE) PDCCH 2
with 8 CCEs
• Aggregation Levels serve to encode signaling 1
information into several CCEs to increase 5
1 CCE = 1 RB
1
robustness, therefore coverage. 4 CORESET #1
1
3
• Reference signals located in PDCCH are UE 1
12 Subcarriers = 1RB
2
specific, i.e., DCI dedicated to a certain UE 1
1
will have UE’s DM-RS configuration from PDSCH. 1 PDSCH
0
9
• Into a CCE a DCI is placed. 8
NR supports one more
7
aggregation level than LTE
6
5 CORESET #2
4
3 PDCCH 1
2 with 10
1 CCEs
AGG Level 16
AGG Level 1
AGG Level 8
AGG Level 4
AGG Level 2
0
1 OFDM Symbol
PDCCH
• Physical Downlink Control Channel has a similar concept as in LTE – it carries Downlink Control Information (DCI)
namely: Dl Allocation, UL Scheduling grants and UL Power control commands.
• However the resource allocation for PDCCH has couple of now units: REG Bundle and CORESET
Search Space
A set of CCEs upon which
the UE tried to blindly
detect PDCCH
Type 0: transmission
SI-RNTI
SIB decoding
Type 1: Not necessarily spanning Possibility for
RA-RNTI, TC-RNTI, C-RNTI
Msg2, Msg4 decoding
full carrier bandwidth beamforming
Common
Search Space Type 2:
P-RNTI P-RNTI (paging message)
Paging decoding SI-RNTI (system message)
Type 3:
RA-RNTI (RAR)
PDCCH Temporary C-RNTI (Msg3/Msg4)
INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI,
TPC-SRS-RNTI, C-RNTI, CS-RNTI(s), SP-CSI-RNTI C-RNTI (UE uplink and downlink data)
SFI-RNTI (slot format)
UL Scheduling
Grant INT-RNTI (resource pre-emption)
UE Specific Configured through RRC signaling:
Search Space TPC-PUSCH-RNTI (PUSCH power control command)
C-RNTI, or CS-RNTI(s), or SP-CSI-RNTI
DL Allocations TPC-PUCCH-RNTI (PUCCH power control command)
TPC-SRS-RNTI (SRS power control command)
PDCCH in Huawei (5G ran 2.1)
• PDCCH may span on 1-2 symbols - fixed configuration

• PDCCH Aggregation Level is based on CQI reports and BLER
• PDCCH Aggregation Level 1 is not supported in the current version
SCS = 30 kHz, Slot = 0.5 ms

0 1 2 3 4 5 6 7 8 9 10111213
11 DM-RS Huawei parameters
10
9 PDCCH NRDUCellPdcch.OccupiedSymbolNum = 1SYM; [1SYM, 2SYM]
8
Resource Block
7
6
5
NRDUCellPdcch.UlMaxCcePct = 50%; [1~100]
4 - Distribution of CCE resources between UL scheduling grants and DL allocations
3
2
1
0 NRDUCellRsvdParam.RsvdU8Param15 = 3%
- Target PDCCH BLER

Downlink Control Information (DCI)
• L1 signaling is done by DCI. DCI has various formats for the information sent to define resource allocations.
• Blind decoding using search space and DCI formats Field (Item) Bits Reference
Identifier for DCI formats 1
Frequency domain resource Variable with UL BWP N_RB.
N
assignment Indicate PRB location within the BWP.
3GPP 38.212 Chapter 7.3.1
Carries the row index of the items in pusch_allocationList
Time domain resource assignment X
DCI Format Usage in RRC
Frequency Hopping Flag 1
Format 0_0 Scheduling of PUSCH in one cell (fallback format)
Modulation and coding scheme 5 38.214 - 6.1.4
Format 0_1 Scheduling of PUSCH in one cell New data indicator 1
Redundancy version 2 0,1,2,3
Scheduling of PDSCH in one cell (fallback format)
HARQ process number 4
DCI format 1_0 with CRC scrambled by C-RNTI
Format 1_0 TPC command for scheduled PUSCH 2 38.213 - Table 7.1.1-1
DCI format 1_0 with CRC scrambled by RA-RNTI
0 bit : SUL not figured
DCI format 1_0 with CRC scrambled by TC-RNTI UL/SUL indicator 0 or 1
1 bit : SUL configured
Format 1_1 Scheduling of PDSCH in one cell
Format 2_0 Notifying a group of UEs of the slot format Field (Item) Bits Reference
Identifier for DCI formats 1 Always set to 1, meaning this is for DL
Notifying a group of UEs of the PRB(s) and OFDM Frequency domain resource Variable with DL BWP N_RB
Format 2_1 symbol(s) where UE may assume no transmission is Variable
assignment
intended for the UE (preemption indicator) Carries the row index of the items in pdsch_allocationList
Time domain resource assignment X
Format 2_2 Transmission of TPC commands for PUCCH and PUSCH in RRC
According to 38.212 Table 7.3.1.1.2-33
Transmission of a group of TPC commands for SRS VRB-to-PRB mapping 1 0 : Non-Interleaved
Format 2_3
transmissions by one or more UEs 1 : Interleaved
38.214 - Table 5.1.3.1-1: MCS index table 1 for PDSCH
Modulation and coding scheme 5
38.214 - Table 5.1.3.1-2: MCS index table 2 for PDSCH
New data indicator 1
Redundancy version 2
HARQ process number 4
Downlink assignment index 2
TPC command for scheduled PUCCH 2
PUCCH resource indicator 3
PDSCH-to-HARQ_feedback timing
3 Row number(index) of K1
indicator

Resource Allocation
• means allocation of PDSCH resources (RBs) by PDCCH in both frequency and time domain.
• Frequency: Number of resource blocks
• Time: Number of OFDM Symbols

PDSCH PUSCH
Start symbol 0, 1, 2, 3 0
Type A
Length 3-14 symbols 4-14 symbols
Start symbol any
Type B
Length 2, 4, 7 2-14 symbols
• Resource allocation can be for UL or DL:

• PDCCH DCI à PDSCH (DL allocation)
• PDCCH DCI à PUSCH (UL Scheduling Grant)

• In LTE the time domain resource allocation was fixed to 4 subframe later (delay of n+4, LTE’s low latency feature allows n+3) and the
duration was always 1 subframe = 1 ms
• In NR the time domain resource allocation can start in almost any OFDM symbol and can last up to 14 OFDM symbols, however cannot
span multiple slots.

Time Domain Resource Allocation Introduction
• means allocation of PDSCH resources (RBs) by PDCCH
in both frequency and time domain.
• Frequency: Number of resource blocks HARQ Timing Definition
Kx defines time offset in slot units between
• Time: Number of OFDM Symbols various procedures
• Resource allocation can be for UL or DL: K0,1,2 are indicated in DCI
• K0: offset between DL grant and
• PDCCH DCI à PDSCH (DL allocation)
corresponding DL data (PDSCH) reception
• PDCCH DCI à PUSCH (UL Scheduling Grant) • K1: offset between DL data (PDSCH) reception
and corresponding N/ACK transmission on UL
• In LTE the time domain resource allocation was fixed
to 4 subframe later (delay of n+4, LTE’s low latency • K2: offset between UL grant (PDCCH)
feature allows n+3) and the duration was always 1 reception in DL and UL data (PUSCH)
transmission
subframe = 1 ms
• K3: offset between N/ACK reception in UL and
• In NR the time domain resource allocation can start corresponding retransmission of data (PDSCH)
in almost any OFDM symbol and can last up to 14 in DL.
OFDM symbols, however cannot span multiple slots.

Time Domain Resource Allocation DL
ACK/NACK Timing on PUCCH?
Example for time domain resource allocation for K0 = 0 PUCCH-Config ::= SEQUENCE {
...
dl-DataToUL-ACK SEQUENCE (SIZE (8)) OF INTEGER
Remaining PDSCH can be scheduled to another UE (0..15) OPTIONAL, --
PDCCH PDSCH Need M
...
Slot n Slot n+1 ACK/NACK on PUCCH
}
CORESET 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
Duration:
2 symbols K0 = 0 à same slot as PDCCH is in K1 = dl-DataToUL-ACK
DCI Format 1_0 or 1_1

Time domain resource assignment [field] carriers row index of previously configured pdsch-Allocation list == 0, 1
Example: pdsch-Allocation list {
Start and duration? SLIV
PDSCH-TimeDomainResourceAllocation { Called SLIV, defines the start symbol and the
k0 omit //if omitted value is 0 number of consecutive symbols for PDSCH
In which slot? mappingType typeA
Row 0 allocation. Standardized in 3GPP 38.214 5.1.2:
𝐾i ∈ 0,1,2 startSymbolAndLength ‘00111010’B => 58 DEC And next slide S = Start Symbol Index, L = Number of Consecutive Symbols
} if (L-1) <= 7 then
PDSCH-TimeDomainResourceAllocation { SLIV = 14 x (L-1) + S
k0 1 K0 = 1 à next slot as DCI Row 1 else
mappingType typeA SLIV = 14 x (14-L+1) + (14-1-S), where 0 < L <= 14 – S
startSymbolAndLength ‘00011011’B => 27 DEC PDSCH Normal Cyclic Prefix
} mapping type S L S+L
Type A {0,1,2,3} {0,…,14} {3,…,14}
Type B {0,…,12} {2,4,7} {2,…,14}

SLIV – Start Symbol and Length Value
Valid Mapping Valid Mapping Valid Mapping
Valid Mapping Type Valid Mapping Type Valid Mapping Type
Type Type Type
S L L-1 S+L SLIV (Normal CP) S L L-1 S+L SLIV (Normal CP) S L L-1 S+L SLIV (Normal CP)
(Normal CP) (Normal CP) (Normal CP)
PDSCH PDSCH PDSCH
PUSCH PUSCH PUSCH
1 0 1 0 Type B 1 0 4 3 Type B 1 0 8 7 Type B
2 1 2 14 Type B Type B 2 1 5 17 Type B Type B 2 1 9 21 Type B Type B
3 2 3 28 Type A Type B 3 2 6 31 Type A Type B 3 2 10 35 Type B
4 3 4 42 Type A,Type B Type A,Type B 4 3 7 45 Type A,Type B Type B 7 4 3 11 49 Type B Type B
5 4 5 56 Type A Type A,Type B 5 4 8 59 Type A Type B 5 4 12 63 Type B
6 5 6 70 Type A Type A,Type B 3 6 5 9 73 Type A Type B 6 5 13 77 Type B
7 6 7 84 Type A,Type B Type A,Type B 7 6 10 87 Type A,Type B Type B 7 6 14 91 Type B Type B
0
9 8 9 97 Type A Type A,Type B 9 8 12 94 Type A Type B 2 1 10 22 Type B Type B
8
11 10 11 69 Type A Type A,Type B 11 10 14 66 Type A Type B 4 3 12 50 Type B Type B
12 11 12 55 Type A Type A,Type B 1 0 5 4 Type B 5 4 13 64 Type B
13 12 13 41 Type A Type A,Type B 2 1 6 18 Type B Type B 6 5 14 78 Type B
14 13 14 27 Type A Type A,Type B 3 2 7 32 Type B 1 0 10 9 Type B
1 0 2 1 Type B 4 3 8 46 Type B Type B 2 1 11 23 Type B Type B
2 1 3 15 Type B Type B 5 4 9 60 Type B 9 3 2 12 37 Type B
4
3 2 4 29 Type A Type B 6 5 10 74 Type B 4 3 13 51 Type B
4 3 5 43 Type A,Type B Type B 7 6 11 88 Type B 5 4 14 65 Type B
5 4 6 57 Type A Type B 8 7 12 102 Type B Type B 1 0 11 10 Type B
6 5 7 71 Type A Type B 9 8 13 93 Type B 2 1 12 24 Type B Type B
10
1 7 6 8 85 Type A,Type B Type B 10 9 14 79 Type B 3 2 13 38 Type B
8 7 9 99 Type A Type B 1 0 6 5 Type B 4 3 14 52 Type B
10 9 11 82 Type A Type B 3 2 8 33 Type B 11 2 1 13 25 Type B Type B
12 11 13 54 Type A Type B 5 5 4 10 61 Type B 1 0 13 12 Type B
12
13 12 14 40 Type A Type B 6 5 11 75 Type B 2 1 14 26 Type B Type B
1 0 3 2 Type B 7 6 12 89 Type B Type B 13 1 0 14 13 Type B
2 1 4 16 Type B Type B 8 7 13 103 Type B
3 2 5 30 Type A Type B 9 8 14 92 Type B
4 3 6 44 Type A,Type B Type B 1 0 7 6 Type B
5 4 7 58 Type A Type B 2 1 8 20 Type B Type B
2
7 6 9 86 Type A,Type B Type B 4 3 10 48 Type B Type B
6
10 9 12 81 Type A Type B 7 6 13 90 Type B Type B
12 11 14 53 Type A Type B

Time Domain Resource Allocation UL
Example for time domain resource allocation for K0 = 0
PDCCH PUSCH
Slot n Slot n+1
CORESET 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
Duration:
2 symbols K2 = 0 à same slot as PDCCH is in
DCI Format 0_0 or 0_1
Time domain resource assignment [field] carriers row index of previously configured pusch-Allocation list == 0,1
Example: pusch-Allocation list {
PUSCH-TimeDomainResourceAllocation {
k2 omit //if omitted value is 0 Start and duration? SLIV
In which slot? mappingType typeA Row 0 Called SLIV, defines the start symbol and the
𝐾h ∈ 0, … , 7 startSymbolAndLength ‘01011100’B => 92 DEC number of consecutive symbols for PUSCH
} allocation. Standardized in 3GPP 38.214 6.1.2.1:
PUSCH-TimeDomainResourceAllocation { S = Start Symbol Index, L = Number of Consecutive Symbols
k2 1 K2 = 1 à next slot as DCI Row 1
if (L-1) <= 7 then
mappingType typeA SLIV = 14 x (L-1) + S
startSymbolAndLength ‘01010011’B => 83 DEC else
} SLIV = 14 x (14-L+1) + (14-1-S), where 0 < L <= 14 – S
PUSCH Normal Cyclic Prefix

mapping type S L S+L
DCI Format 0_0 (short) à w/o BWP detail
Type A 0 {4,…,14} {4,…,14}
0_1 (long) à w/ BWP details
Type B {0,…,13} {1,…,14} {1,…,14}
0_1 used especially if several BWP configured to UE
Frequency Domain Allocation 38.214 - Table 5.1.2.2.1-1: Nominal RBG size P, Table 6.1.2.2.1-1: Nominal RBG size P
Bandwidth Size Bandwidth Size Bandwidth Size Bandwidth Size
(1-35) (37-72) (73-144) (145-275)
PRB # Config 1 Config 2 Config 1 Config 2 Config 1 Config 2 Config 1 Config 2
• Ideally each resource block shall be addressable by individual bit in a bitmap, 0
1
RBG 00
RBG 00 RBG 00
however such an approach would create too much signaling data for PDCCH (e.g. 2
RBG 01
3
BW=100MHz, SCS = 30kHz, would need 273 bits, as it contains 273 RBs). 4
RBG 02
RBG 00 RBG 00
5
RBG 01 RBG 01
6
• Signaling which RB belong to which UE must be simplified, either through 7
RBG 03
RGB 00 RGB 00 RGB 00
8
Resource Block Group (RBG) or Start position and length. LTE knows 3 9
RBG 04
RBG 02 RBG 02
10
approaches, how to simplify addressing of RBs, NR specifies 2 so far: 11
RBG 05
RBG 01 RBG 01
12
RBG 06
13
RBG 03 RBG 03
NR Resource Allocation Type Allocation Method 14
RBG 07
15
Type 0 Bitmap 16
RBG 08
17
RBG 04 RBG 04
18
Type 1 Start RB and Number consecutive of RB 19
RBG 09
RBG 02 RBG 02
20
RBG 10
21
RBG 05 RBG 05
22
• Type 0: Bundles multiple RBs together to create RBG, size of RBG depends on 23
RBG 11
24
BWP size. Configuration 1 or 2 is determined by PDSCH-Config à rgb-size field 25
RBG 12
RBG 06 RBG 06
{config 1, config 2} 26
27
RBG 13
RBG 03 RBG 03
28
RBG 14
29
• Type 1: Start RB and Number of RBs is combined into single Resource Indicator 30
RBG 07 RBG 07
RBG 15
Value (RIV) within a specific BWP, based on formula from 3 GPP 38.214 Chapter 31
32
RBG 16
5.1.2.2.2. The RIV is calculated in following formula: 33
34
RBG 08 RBG 08
RBG 17
35
RBG 04 RBG 04
36
37
RBG 09
38
39
40
41
RBG 10
42
43
RBG 05 RBG 05
44
45
RBG 11
46
47
247 RBG 17 RBG 17
NR Reference Signals

Reference Signals in NR
• Several types of Reference Signal is used, however Cell Specific Reference Signal (CRS) as we know them from LTE
(wideband) are not.
• CRS as we know them from LTE were replaced by PDSCH DM-RS, and they are transmitted only in RBs which is scheduled
to the UE. This concept is known as a lean design and profoundly reduces inter cell interference.
• NR Reference signals are tailored for specific roles and can be flexibly adapted for different deployment scenarios and
spectrum
In LTE “one size fits all” DL reference signal design - CRS
Reference Signals in NR Functionality Reference

CSI-RS (Channel State Information) CSI aquisition, Beam Management 38.211-7.4.1.5
PDSCH DM-RS (Demodulation Reference Signals) Required for PDSCH Demodulation 38.211-7.4.1.1
Downlink
PDCCH DM-RS Required for PDCCH Demodulation 38.211-7.4.1.3

PBCH DM-RS Required for PBCH Demodulation 38.211-7.4.1.4
PT-RS (Phase Tracking ) Used for Phase Noise Compensation for PDSCH 38.211-7.4.1.2
T-RS (Time/Frequency Tracking) Used for Time Tracking (synchronization) 38.211-7.4.1.6
PUSCH DM-RS Required for PUSCH Demodulation 38.211-6.4.1.1
Uplink
PUSCH PT-RS Used for Phase Noise Compensation for PUSCH 38.211-6.4.1.2
PUCCH DM-RS Required for PUCCH Demodulation 38.211-6.4.1.3
SRS (Sounding Reference Signals) For uplink channel quality evaluation 38.211-6.4.1.4

PDSCH/PUSCH DMRS SCS = 30 kHz, Slot = 0.5 ms
0 1 2 3 4 5 6 7 8 9 10111213
Front
11
loaded
Used for decoding PDSCH. They can be divided into: 10
9 Additional
Resource Block
8
• Front Loaded (FL) DMRS: Occupies 1 to 2 symbols 7 dmrs-AdditionalPosition ENUMERATED {pos0,
6 pos1, pos3} OPTIONAL, -- Need R
5
• Additional (Add) DRMS: Occupies 1 to 3 symbols, 4
pos0 = 1+0
pos1 = 1+1
used in high-speed scenarios (latter part of a slot) 3
2 pos2 = default 1+1+1 (when field empty)
1
pos3 = 1+1+1+1 (as on the picture)
Different DMRS types allow different maximum 0
Type 1, dual symbol Type 2, dual symbol
number of ports: 0 1 2 3 4 5 6 7 8 9 10111213 0 1 2 3 4 5 6 7 8 9 10111213
11 1000 11 1000
10 1001 10 1001
• Type 1: Single-symbol: 4, dual-symbol: up to 8 9 1004 9 1006
8 8
orthogonal ports (used for SU-MIMO) 1005 1007
Resource Block
7 7 1002
6 1002 6 1003
• Type 2: Single-symbol: 6, dual-symbol: up to 12 5
4
1003
1006
5
4
1008
1009
orthogonal ports (used for MU-MIMO) 3
2
1007 3
2
1004
1005
1 1 1010
DMRS time-frequency mapping position: 0 0 1011
0 1 2 3 4 5 6 7 8 9 10111213 0 1 2 3 4 5 6 7 8 9 10111213
• Type A: starting from the 3rd of 4th symbol in the slot 11 11 Type A
10 10
9 9 Suitable for Type B
• Type B: starting from 1st symbol on scheduled Resource Block
8
Suitable for
8 PUSCH
7 7
PDSCH (practical only for cases there is no CORESET 6 PDSCH 6
5 5 Located in 1st
on 1st OFDM symbol) 4 4 symbol of time
3 3 allocation (not a
2 2 1st symbol of slot)
1 1
© Widermind AB Vivacom Sofia 05-19 151 0 0
PUSCH Demodulation reference signals
• NR supports a common DMRS structure for UL and DL (PDSCH and PUSCH), so the exact time location, DMRS pattern, and
scrambling sequence can be used, or it can be also configured differently.
• Typically Type B is configured (DM-RS starts in OFMD symbol #0)
• Only type 1 DM-RS supports DFT-S-OFDM (UL) – transmission without UL MIMO

CSI Reference Signals / TRS
CSI-RS
• designed for downlink measurement à reporting channel status info
• Three different types of CSI-RS are supported:
Periodic CSI-RS Aperiodic CSI-RS Semi-Persistent CSI-RS

Orthogonal Ports Up to 32 Up to 32 Up to 32
Time domain behavior Periodic transmission Single transmission Periodic transmission
once configured when triggered once activated until
deactivated
Activation/Deactivation RRC signaling L1 signaling MAC CE
Characteristics No L1 overhead Low latency Hybrid of periodic and
aperiodic CSI-RS
TRS (Tracking)
• Designed for time/frequency tracking and estimation for delay/Doppler spread
• Configured as a CSI-RS with specific parameter restriction (time/freq location, RE pattern/ etc)

Phase Tracking Reference Signals (PT-RS)
Optional
• Designed for UL/DL phase noise compensation on PDSCH and PUSCH
• Associated with DM-RS so the receiver can compensate for phase noise during demodulation
• If a UE is configured with the higher layer parameter in DMRS-DownlinkConfig: phaseTrackingRS (Optional). Parameters
timeDensity and frequencyDensity in PTRS-DownlinkConfig indicate the threshold values ptrs-MCSi, i=1,2,3 and NRB,i ,
i=0,1, from table below. If the time and frequency parameters are not configured, LPR-RS=1 and KPT_RS=2. For QPSK
modulations PT-RS is not used.
3GPP 38.214 Table 5.1.6.3-1: Time density of PT-RS as a function of scheduled MCS 3GPP 38.214 Table 5.1.6.3-2: Frequency density of PT-RS as a function of scheduled bandwidth
Scheduled MCS Time density (LPT-RS) Scheduled bandwidth Frequency density (KPT-RS)
IMCS < ptrs-MCS1 PT-RS is not present NRB < NRB0 PT-RS is not present
ptrs-MCS1 ≤ IMCS < ptrs-MCS2 4 NRB0 ≤ NRB < NRB1 2
ptrs-MCS2 ≤ IMCS < ptrs-MCS3 2 NRB1 ≤ NRB 4
ptrs-MCS3 ≤ IMCS < ptrs-MCS4 1
Scheduled BW
0 1 2 3 4 5 6 7 8 9 10111213 0 1 2 3 4 5 6 7 8 9 10111213 0 1 2 3 4 5 6 7 8 9 10111213
11
10
9 X X X X
8 Every 2nd RB
7
Subcarrier
6
5
Scheduled BW
4
3
2 X X
1 Every 4th RB
0
Every OFDM Symbol Every 2nd OFDM Symbol Every 4th OFDM Symbol

Sounding Reference Signals (SRS)
Optional
• Designed for evaluation of uplink quality and timing
• Can also be used for DL channel information when channel reciprocity is applicable (TDD)
• Three different types are standardized: Periodic, aperiodic, and semi-persistent
• SRS carrier switching is supported for transmitting SRS over more than one carrier using single uplink transmitter
• Up to 6 OFDM symbols can be used for transmission to increase SRS capacity. LTE supports only last OFDM symbol.
0 1 2 3 4 5 6 7 8 9 10111213
UE1
UE2
Resource allocation to UE
0 1 2 3 4 5 6 7 8 9 10111213
Time Domain:
• It spans 1, 2, or 4 consecutive OFDM symbols, located

somewhere with last 6 symbols of a slot
Frequency domain
• is has a “comb” structure, transmitted on every Nth

subcarrier (N =<2,4>)
6 Symbols Max

UL Physical Channels

Uplink Channels
Uplink channels:
• PUSCH
• PUCCH
• PRACH
Simultaneous transmission on PUSCH and PUCCH supported
Uplink signals:
• DM-RS
• PT-RS
• SRS

Physical Uplink Shared Channel (PUSCH)
Carrier user data and optionally Uplink Control Information (UCI) RB(n)
Simultaneous transmission of PUSCH and PUCCH possible DFT-s-OFDM – Discrete Fourier RB(n-1)
Transform spread OFDM
Two waveforms possible: RB(n-2)
• CP-OFDM (Cyclic Prefix): intended for MIMO Commonly known as SC-FDMA
PUSCH
Adopted by uplink RB(n-3)
• DFT-s-OFDM (used with single layer transmission, intra-slot frequency
hopping supported) Lower PAPR than OFDMA
Modulations: No changes compared to LTE
⋮
Transform precoding disabled (CP-OFDM) Transform precoding enabled (DFT-s-

OFDM)
Modulation scheme Modulation order Modulation Modulation order
Qm scheme Qm 0 1 2 3 4 5 6 7 8 9 10111213
11
π/2-BPSK 1
10
QPSK 2 QPSK 2 9
16QAM 4 16QAM 4 8 RB3
Resource Block
64QAM 6 64QAM 6 7
256QAM 8 256QAM 8 6
5
RB2
PUCCH
4
3 RB1
Front-loaded DM-RS are located at first OFDM symbol assigned for 2
PUSCH (additional can be configured for high speed) 1

0
RB0
Front loaded

Physical Uplink Shared Channel
CP-OFDM
Resource
Modulation OFDM Signal
Scrambling Element
Mapper Generator
Mapper
codewords
antenna
Layer
layers
.....
.....
ports
Precoding
Mapper
Resource
Modulation OFDM Signal
Scrambling Element
Mapper Generator
Mapper
DMRS
Resource
Transform OFDM Signal
DFT-s-OFDM Precoding
Element
Generator
Mapper
antenna
Modulation Modulation
layers
.....
.....
ports
Scrambling Precoding
Mapper Mapper
codeword
Resource
Transform OFDM Signal
Element
Precoding Generator
Mapper
DMRS

Physical Uplink Control Channel
Carries
• Uplink Control Information (UCI): Channel State Information (CSI) reports
• HARQ feedback
• Scheduling Requests (SR)
Two types of PUCCHs:
• Short PUCCH: BPSK and QPSK
• Long PUCCH:
3GPP 38.211 Table 6.3.2.1-1
PUCCH Formats:
Length in
PUCCH Number
OFDM From 38.300 5.3.3 Modulation
format of bits
symbols
0 1–2 ≤2 Short PUCCH with small UCI payloads of up to two bits with UE multiplexing
capacity of up to 6 UEs with 1-bit payload in the same PRB
1 4 – 14 ≤2 Long PUCCH with small UCI payloads of up to two bits with UE multiplexing BPSK and QPSK
capacity of up to 84 UEs without frequency hopping and 36 UEs with frequency
hopping in the same PRB
2 1–2 >2 Short PUCCH with large UCI payloads of more than two bits with no UE QPSK
multiplexing capability in the same PRBs
3 4 – 14 >2 Long PUCCH with large UCI payloads with no UE multiplexing capability in the µ/2 BPSK and QPSK
same PRBs
4 4 – 14 >2 Long PUCCH with moderate UCI payloads with multiplexing capacity of up to 4 UEs µ/2 BPSK and QPSK
in the same PRBs

PUCCH Resource Set
PUCCH resource can be dedicated (UE specific) configured by RRC parameter PUCCH-ResourceSet in PUCCH-Config.
If UE is not configured with dedicated resource set, it uses common PUCCH configured by pucch-ResourceCommon in SIB1
PUCCH location:
PUCCH-ResourceSetId ::= INTEGER (0..maxNrofPUCCH-ResourceSets-1)
PUCCH-Resource ::= SEQUENCE {
pucch-ResourceId PUCCH-ResourceId,
startingPRB PRB-Id,
274 intraSlotFrequencyHopping ENUMERATED {enabled} OPTIONAL, -- Need R
273 secondHopPRB PRB-Id OPTIONAL, -- Need R
272
⋮ PUCCH-ResourceId ::= INTEGER (0..maxNrofPUCCH-Resources-1)
11 PUCCH-format0 ::= SEQUENCE {
10
9
PUSCH initialCyclicShift
nrofSymbols
INTEGER(0..11),
INTEGER (1..2),
8 startingSymbolIndex INTEGER(0..13)
7 }
PUCCH-format1 ::= SEQUENCE {
6
PUCCH Number 5 initialCyclicShift INTEGER(0..11),
nrofSymbols INTEGER (4..14),
H
of PRBs 4
CC
startingSymbolIndex INTEGER(0..10),
(only for F2 and F3) 3
PU
timeDomainOCC INTEGER(0..6)
2
}
PUCCH Starting 1 PUCCH-format2 ::= SEQUENCE {
0
PRB (same for all) nrofPRBs INTEGER (1..16),
0 1 2 3 4 5 6 7 8 9 10111213 nrofSymbols INTEGER (1..2),
startingSymbolIndex INTEGER(0..13)
PUCCH number
of symbols
PUCCH Starting
symbol
}
nrofPRBs INTEGER (1..16),
}
occ-Length ENUMERATED {n2,n4},
occ-Index ENUMERATED {n0,n1,n2,n3},
}

PUCCH IN Huawei 5g RAN 2.1
• In Sub6 frequency bands, Huawei uses only LONG_STRUCTURE type of PUCCH. Long Structures can contain Formats: 1, 3, 4.
• However Huawei currently supports only PUCCH Formats: 1, 3. Both with 1 RB allocation in frequency domain per UE.
PUCCH Format 1 (1RB allocation)

0 1 2 3 4 5 6 7 8 9 10 11 12 13 3GPP defined PUCCH Resource Allocation:
11 DM-RS
10 Scheduling Request resources can be only statically configured
9 PUCCH
8
CSI resources can be statically configured or semi-persistently scheduled
Resource Block
7 HARQ resources can be scheduled dynamically

6
5 Huawei in current version PUCCH allocation supports:
4
3 SRs can be statically configured (in RRC: OFDM sym# + start symbol, RB# + start RB, period)
2
1
CSI are dynamically scheduled on PUSCH
0 HARQ are dynamically scheduled (in RRC: OFDM sym# + start symbol, RB# + start RB, period)
PUCCH Format 3 (1RB allocation)
0 1 2 3 4 5 6 7 8 9 10111213
11 DM-RS
10
9 PUCCH
8 Huawei parameters
Resource Block
7
6
NRDUCellPucch.Format1RbNum = RB4; [RB2, RB4, RB6, RB8, RB10]
5 - Number of Resource Block for PUCCH Format 1
4
3 NRDUCellPucch.Format3RbNum = RB16; [RB2, RB4, RB6, RB8, RB10, RB12, RB14, RB16, RB18, RB20]
2 162
1
- Number of Resource Blocks for PUCCH Format 3
0 NRDUCellPucch. SrPeriod = 40 slots; [1, 2, 4, 5, 8, 10, 16, 20, 40, 80, 160, 320, 640]
Physical Random Access Channel (PRACH)
Parameter (IE) Description Reference
Random Access procedure similar to LTE
prach-ConfigurationIndex 0-255 38.321-5.1
Number of Preamble Formats increased to 13! prach-RootSequenceIndex 0-837 38.211-6.3.3
Beam Establishment zeroCorrelationZoneConfig 0-15 38.211-6.3.3
restrictedSetConfig 38.211-6.3.3
• Different SS block time indices are associated with PreambleInitialReceivedTargetPo initial preamble power -200
38.321-5.1.3
different RACH wer ~-70
time/frequency occasions rsrp-ThresholdSSB
csirs-dedicatedRACH-Threshold
• SIB1 provides “number of SS-block time indices per sul-RSRP-Threshold
RACH time/frequency occasion” ssb-Threshold
• SSB time indices associated with RACH occasions, powerRampingStep 0, 2, 4, 6 38.321-5.1
ra-PreambleIndex
first in frequency, then in time within a slot, and last in
PreambleTransMax 38.321-5.1
time between slots ra-Msg3SizeGroupA 38.321-5.1
messagePowerOffsetGroupB
ra-ResponseWindowSize 38.321-5.1
ra-ContentionResolutionTimer 38.321-5.1
PreambleStartIndex 38.321-5.1
NumberofRA-Preambles
zeroCorrelationZoneConfig 38.211-6.3.3
ra-ResponseWindow
rach-ControlResourceSet
msg3-transformPrecoding Msg3 Transform Precoding 38.213-8.3
msg3-SubcarrierSpacing Msg3 Subcarrier Spacing 38.213-8.3

UE Initial Access
SgNB UE
Beam sweeping transmission
The UE identifies
SSB: PSS+SSS+PBCH the best SSB
Beam sweeping reception The UE transmits

PRACH on a set of
Random Access Preamble resources
depending on a
the best SSB time
UE-specific beam selected index
Random Access Response & System Information
RRC Connection Procedure
Reference signals used for beam management:

• IDLE mode: PSS, SSS and PBCH DMRS (i.e. SSB)
• CONNECTED mode: CSI-RS (DL) and SRS (UL)

5G-NR Preamble Formats
Format 0
103.2 µs 800.6 µs 96.9 µs
TCP TSEQ TSEQ GP GP = T_PRACH-Nu-TCP
Two different length (L_RA) of T_PRACH [µs]

PRACH preamble is used
depending on subcarrier spacing Defines max cell radius
Long Sequence
of the preamble.
3GPP 38.211 Table 6.3.3.1-1: Preamble formats for LRA = 839 and ∆fRA = {1.25,5} kHz
Support for Rmax = 0,0969ms*c/2 –
Format LRA ∆fRA Nu *ž
𝑁Of T_PRACH [µs]
• When the subcarrier spacing restricted sets 14 km
0 839 1.25 kHz 2457κ 3168κ Type A, Type B 1000
of PRACH preamble is 1.25 or 1 839 1.25 kHz 2*2457κ 21024κ Type A, Type B 3000
Rmax = 0,7162ms*c/2 –
5 KHz, long sequence (L_RA = 2 839 1.25 kHz 4*2457κ 4688κ Type A, Type B 3500
107 km
3 839 5 kHz 4*6144κ 3168κ Type A, Type B 1000
839) is used as in the
following tableà
3GPP 38.211 Table 6.3.3.1-2: Preamble formats for LRA = 139 and ∆fRA = 15*2µ kHz where µ = {0,1,2,3}
Support for
• When the subcarrier spacing Format LRA ∆fRA Nu *ž
𝑁Of T_PRACH [µs]
restricted sets
of PRACH preamble is 15, 30, A1 139 15*2µ kHz 2*2048κ*2-µ 288κ*2-µ -
A2 139 15*2µ kHz 4*2048κ*2-µ 576κ*2-µ -
60 or 120 KHz, A3 139 15*2µ kHz 6*2048κ*2-µ 864κ*2-µ - 285,4
short sequence (L_RA = 139) B1 139 15*2µ kHz 2*2048κ*2-µ 216κ*2-µ - 428,1
B2 139 15*2µ kHz 4*2048κ*2-µ 360κ*2-µ - 285,4
is used as in the following B3 139 15*2µ kHz 6*2048κ*2-µ 504κ*2-µ - 428,1
B4 139 15*2µ kHz 12*2048κ*2-µ 936κ*2-µ - 856,3
table à C0 139 15*2µ kHz 2048κ*2-µ 1240κ*2-µ - 107,1
C2 139 15*2µ kHz 4*2048κ*2-µ 2048κ*2-µ 428,3
Short Sequence
𝑇^ 1 1
𝐾𝑎𝑝𝑝𝑎: 𝜅 = = 64 𝑆𝑎𝑚𝑝𝑙𝑖𝑛𝑔 𝑡𝑖𝑚𝑒: 𝑇O = = = 0,509𝑛𝑠
165
𝑇O ∆𝑓`\£ 7 𝑁e 480𝑘𝐻𝑧 7 4096
© Widermind AB Vivacom Sofia 05-19
5G-NR Preamble formats suitable for DDDSU
3GPP 38.211 Table 6.3.3.1-2: Preamble formats for LRA = 139
and ∆fRA = 15*2µ kHz where µ = {0,1,2,3}
Forma *ž Support for
LRA ∆fRA Nu [Tc] 𝑁Of [Tc]
t restricted sets
A1 139 15*2µ kHz 2*2048κ*2-µ 288κ*2-µ
A2 139 µ
15*2 kHz 4*2048κ*2 -µ 576κ*2-µ
A3 139 15*2µ kHz 6*2048κ*2-µ 864κ*2-µ
B1 139 15*2µ kHz 2*2048κ*2-µ 216κ*2-µ
B2 139 µ
15*2 kHz 4*2048κ*2 -µ 360κ*2-µ
B3 139 15*2µ kHz 6*2048κ*2-µ 504κ*2-µ
12*2048κ*2 -
B4 139 15*2µ kHz µ 936κ*2-µ
C0 139 15*2µ kHz 2048κ*2-µ 1240κ*2-µ Duration [ms]
C2 139 µ
15*2 kHz 4*2048κ*2 -µ 2048κ*2-µ 0 0,05 0,1 0,15 0,2 0,25 0,3 0,35 0,4 0,45 0,5
Preamble formats for LRA = 139 and ∆fRA = 30 kHz
A1 2 OFDM symbols
*ž Cell radius
Format 𝑁Of [ms] Nu [ms] TGP (ms) total time [ms] A2
(Nokia) [km] 4 OFDM symbols
A1 0,0046875 0,066667 0 0,071354167 0,4664 A3
A2 0,009375 0,133333 0 0,142708333 1,0494 6 OFDM symbols
Preamble Format
B1
A3 0,0140625 0,2 0 0,2140625 1,7491
B1 0,003515625 0,066667 0,002344 0,072526042 0,1860 B2 Guard period
B2 0,005859375 0,133333 0,007031 0,146223958 0,5247 B3
B3 0,008203125 0,2 0,011719 0,219921875 0,8745
B4 0,015234375 0,4 0,025781 0,441015625 1,9240 B4
C0 0,020182292 0,033333 0,035677 0,089192708 2,6625 C0

C2 0,033333333 0,133333 0,094792 0,261458333 4,7128
C2
N_CP^RA [ms] N_u [ms] T_GP (ms)
𝑇^ 1 1
3GPP 38.211-4.1 𝐾𝑎𝑝𝑝𝑎: 𝜅 = = 64 𝑆𝑎𝑚𝑝𝑙𝑖𝑛𝑔 𝑡𝑖𝑚𝑒: 𝑇O = = = 0,509𝑛𝑠
𝑇O ∆𝑓`\£ 7 𝑁e 480𝑘𝐻𝑧 7 4096
Huawei RACH configuration from traces (30kHz)
Radio Frame
Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9
Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot 9 Slot 0 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot 9
1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111
0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 56789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789
0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123
rame
bf
su
SFN mod 1 = 0 ß every radio frame t in
nd slo
ns
2 ce
• rach-ConfigCommon
a on
•
•
..setup-NRRACH-ConfigCommon
....rach-ConfigGeneric
Me
• ......prach-ConfigurationIndex --- 0xca(202)
PRACH Preambl n_SFN mode Subframe Starting *ž
Number of 𝑁]*',^cb] number of time – 𝑁[xp
• ......msg1-FDM --- one(0)
• ......msg1-FrequencyStart --- 0x2(2) Configuratio e x= y number Symbol PRACH slots domain PRACH occasions PRACH
• ......zeroCorrelationZoneConfig --- 0xa(10) n Format x y within a within a RACH slots duration
• ......preambleReceivedTargetPower --- -100(-100) Index subframe
• ......preambleTransMax --- n10(6) 202 C2 1 0 9 8 1 1 6
Huawei does not have a PRACH Configuration Index parameter accessible in

• ......powerRampingStep --- dB4(2)
• ......ra-ResponseWindow --- sl20(5)
SW yet (5G RAN 2.1), supports only format C2

• ....ssb-perRACH-OccasionAndCB-PreamblesPerSSB
• ......four --- 0xd(13)
• ....ra-ContentionResolutionTimer --- sf64(7)
• ....rsrp-ThresholdSSB --- 0x0(0)
• ....prach-RootSequenceIndex ZeroCorrelationZoneConfig = 10 (not available to configure), means cell
• ......l139 --- 0x0(0)
• ....msg1-SubcarrierSpacing --- kHz15(0) access radius of 0.260km. Number of preambles per root sequence 139/19=7,
• ....restrictedSetConfig --- unrestrictedSet(0)
167
root sequences consumed per cell 64/7=10. Number of unique cell
configuration 138/10=13.
PRACH Preamble
Nokia RACH configuration index example (30kHz)
Configuratio Format
n
Index
91 A2
92 A2 Radio Frame
93
Subframe 0 A2 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9
94 A2
Slot
95 01 1 1 1 Slot
A2 11 1 1 1 Slot 21 1 1 1 Slot 31 1 1 1 Slot 41 1 1 1 Slot 51 1 1 1 Slot 61 1 1 1 Slot 71 1 1 1 Slot 81 1 1 1 Slot 91 1 1 1 Slot 01 1 1 1 Slot 11 1 1 1 Slot 21 1 1 1 Slot 31 1 1 1 Slot 41 1 1 1 Slot 51 1 1 1 Slot 61 1 1 1 Slot 71 1 1 1 Slot 81 1 1 1 Slot 91 1 1 1
0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 56789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789 0123456789
96 0123
A2 0 1 2 3 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123 0123
97 A2
98 A2
99 A2
100 A2
101 A2
102 A2
103 A2
104 A2
105 A2
106 A2
SFN mod 2 = 1 ß every odd radio frame
107 A2
Means every slot in SF
e
108 A2
thre
109 A2
110 A3
PRACH Preambl n_SFN mod x= Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp *ž
151 B4
152
153
B4
B4 • Nokia support following PRACH Configuratio
n
e
Format x
y
y
number Symbol PRACH slots domain PRACH occasions PRACH
within a within a RACH slots duration
154
155
B4
B4
formats: Index
91 A2 2 1 8,9 0
subframe
2 3 4
• Format A2 TDD in 5G18

156 B4
157 B4
158 B4
159 B4 • Format B4 TDD in 5G19
160 B4
161 B4
162 B4
163 B4
164 B4
165 B4 168
166 B4
167 B4
168 B4
PRACH formats 0, 1, 2, 3 (TDD) *ž *ž
PRACH Preamble n_SFN mod x= y Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp PRACH Preamble n_SFN mod x= y Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp
Configuration Format number Symbol PRACH slots domain PRACH occasions PRACH Configuration Format number Symbol PRACH slots domain PRACH occasions PRACH
Index x y within a within a RACH slots duration Index x y within a within a RACH slots duration
subframe subframe
0 0 16 1 9 0 - - 0 40 2 2 1 6 7 - - 0
1 0 8 1 9 0 - - 0 41 2 1 0 6 7 - - 0
2 0 4 1 9 0 - - 0 42 3 16 1 9 0 - - 0
3 0 2 0 9 0 - - 0 43 3 8 1 9 0 - - 0
4 0 2 1 9 0 - - 0 44 3 4 1 9 0 - - 0
5 0 2 0 4 0 - - 0 45 3 2 0 9 0 - - 0
6 0 2 1 4 0 - - 0 46 3 2 1 9 0 - - 0
7 0 1 0 9 0 - - 0 47 3 2 0 4 0 - - 0
8 0 1 0 8 0 - - 0 48 3 2 1 4 0 - - 0
9 0 1 0 7 0 - - 0 49 3 1 0 9 0 - - 0
10 0 1 0 6 0 - - 0 50 3 1 0 8 0 - - 0
11 0 1 0 5 0 - - 0 51 3 1 0 7 0 - - 0
12 0 1 0 4 0 - - 0 52 3 1 0 6 0 - - 0
13 0 1 0 3 0 - - 0 53 3 1 0 5 0 - - 0
14 0 1 0 2 0 - - 0 54 3 1 0 4 0 - - 0
15 0 1 0 1 0 - - 0 55 3 1 0 3 0 - - 0
16 0 1 0 4,9 0 - - 0 56 3 1 0 2 0 - - 0
17 0 1 0 3,8 0 - - 0 57 3 1 0 1 0 - - 0
18 0 1 0 2,7 0 - - 0 58 3 1 0 1,6 0 - - 0
19 0 1 0 8,9 0 - - 0 59 3 1 0 1,6 7 - - 0
20 0 1 0 4,8,9 0 - - 0 60 3 1 0 4,9 0 - - 0
21 0 1 0 3,4,9 0 - - 0 61 3 1 0 3,8 0 - - 0
22 0 1 0 3,4,8 0 - - 0 62 3 1 0 2,7 0 - - 0
23 0 1 0 7,8,9 0 - - 0 63 3 1 0 8,9 0 - - 0
24 0 1 0 3,4,8,9 0 - - 0 64 3 1 0 4,8,9 0 - - 0
25 0 1 0 6,7,8,9 0 - - 0 65 3 1 0 3,4,9 0 - - 0
26 0 1 0 1,4,6,9 0 - - 0 66 3 1 0 7,8,9 0 - - 0
27 0 1 0 1,6 0 0 67 3 1 0 3,4,8,9 0 - - 0
28 0 1 0 1,6 7 - - 0 68 3 1 0 6,7,8,9 0 - - 0
29 0 1 0 1,3,5,7,9 0 - - 0 69 3 1 0 1,4,6,9 0 - - 0
30 1 16 1 7 0 - - 0 70 3 1 0 1,3,5,7,9 0 - - 0
31 1 8 1 7 0 - - 0
32 1 4 1 7 0 - - 0
33 1 2 0 7 0 - - 0
34 1 2 1 7 0 - - 0
35 1 1 0 7 0 - - 0 169
36 2 16 1 6 0 - - 0
37 2 8 1 6 0 - - 0
38 2 4 1 6 0 - - 0
39 2 2 0 6 7 - - 0
Prach formats A1, A2, A3, B1 (TDD) 3GPP 38.211 f40 Table 6.3.3.2-3: Random access configurations for FR1 and unpaired spectrum.
*ž *ž
PRACH Preamble n_SFN mod x= Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp PRACH Preamble n_SFN mod x= Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp
Configuration Format y number Symbol PRACH slots domain PRACH occasions PRACH Configuration Format y number Symbol PRACH slots domain PRACH occasions PRACH
subframe subframe
71 A1 2 1 4,9 7 1 3 2 111 A3 8 1 9 0 2 2 6
72 A1 2 1 7,9 7 1 3 2 112 A3 4 1 9 0 1 2 6
73 A1 2 1 7,9 0 1 6 2 113 A3 2 1 4,9 7 1 1 6
74 A1 2 1 8,9 0 2 6 2 114 A3 2 1 7,9 7 1 1 6
75 A1 2 1 4,9 0 2 6 2 115 A3 2 1 7,9 0 1 2 6
76 A1 2 1 2,3,4,7,8,9 0 1 6 2 116 A3 2 1 4,9 0 2 2 6
77 A1 1 0 9 0 2 6 2 117 A3 2 1 8,9 0 2 2 6
78 A1 1 0 9 7 1 3 2 118 A3 2 1 2,3,4,7,8,9 0 1 2 6
79 A1 1 0 9 0 1 6 2 119 A3 1 0 2 0 1 2 6
80 A1 1 0 8,9 0 2 6 2 120 A3 1 0 7 0 1 2 6
81 A1 1 0 4,9 0 1 6 2 121 A3 2 1 9 0 1 2 6
82 A1 1 0 7,9 7 1 3 2 122 A3 1 0 9 0 2 2 6
83 A1 1 0 3,4,8,9 0 1 6 2 123 A3 1 0 9 7 1 1 6
84 A1 1 0 3,4,8,9 0 2 6 2 124 A3 1 0 9 0 1 2 6
85 A1 1 0 1,3,5,7,9 0 1 6 2 125 A3 1 0 2,7 0 1 2 6
86 0,1,2,3,4,5,6,7,8, 2 126 A3 1 0 8,9 0 2 2 6
A1 1 0 7 1 3
9 127 A3 1 0 4,9 0 1 2 6
87 A2 16 1 9 0 2 3 4 128 A3 1 0 7,9 7 1 1 6
88 A2 8 1 9 0 2 3 4 129 A3 1 0 3,4,8,9 0 1 2 6
89 A2 4 1 9 0 1 3 4 130 A3 1 0 3,4,8,9 0 2 2 6
90 A2 2 1 7,9 0 1 3 4 131 A3 1 0 1,3,5,7,9 0 1 2 6
91 A2 2 1 8,9 0 2 3 4 132 A3 0,1,2,3,4,5,6,7,8, 6
1 0 7 1 1
92 A2 2 1 7,9 9 1 1 4 9
93 A2 2 1 4,9 9 1 1 4 133 B1 4 1 9 2 1 6 2
94 A2 2 1 4,9 0 2 3 4 134 B1 2 1 9 2 1 6 2
95 A2 2 1 2,3,4,7,8,9 0 1 3 4 135 B1 2 1 7,9 2 1 6 2
96 A2 1 0 2 0 1 3 4 136 B1 2 1 4,9 8 1 3 2
97 A2 1 0 7 0 1 3 4 137 B1 2 1 4,9 2 2 6 2
98 A2 2 1 9 0 1 3 4 138 B1 1 0 9 2 2 6 2
99 A2 1 0 9 0 2 3 4 139 B1 1 0 9 8 1 3 2
100 A2 1 0 9 9 1 1 4 140 B1 1 0 9 2 1 6 2
101 A2 1 0 9 0 1 3 4 141 B1 1 0 8,9 2 2 6 2
102 A2 1 0 2,7 0 1 3 4 142 B1 1 0 4,9 2 1 6 2
103 A2 1 0 8,9 0 2 3 4 143 B1 1 0 7,9 8 1 3 2
104 A2 1 0 4,9 0 1 3 4 144 B1 1 0 1,3,5,7,9 2 1 6 2
170
105 A2 1 0 7,9 9 1 1 4 145 B4 16 1 9 0 2 1 12
106 A2 1 0 3,4,8,9 0 1 3 4 146 B4 8 1 9 0 2 1 12
107 A2 1 0 3,4,8,9 0 2 3 4 147 B4 4 1 9 2 1 1 12
108 A2 1 0 1,3,5,7,9 0 1 3 4 148 B4 2 1 9 0 1 1 12
© Widermind AB
A2 Vivacom Sofia 05-19 170
0,1,2,3,4,5,6,7,8, 4 149 B4 2 1 9 2 1 1 12
Prach formats A1, A2, A3, B1 (TDD) 3GPP 38.211 Table 6.3.3.2-3: Random access configurations for FR1 and unpaired spectrum.
*ž *ž
PRACH Preamble n_SFN mod x= y Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp PRACH Preamble n_SFN mod x= y Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp
Configuration Format number Symbol PRACH slots domain PRACH occasions PRACH Configuration Format number Symbol PRACH slots domain PRACH occasions PRACH
subframe subframe
151 B4 2 1 4,9 2 1 1 12 187 C0 1 0 1,3,5,7,9 2 1 6 2
152 B4 2 1 4,9 0 2 1 12 188 C0 0,1,2,3,4,5,6, 2
1 0 8 1 3
153 B4 2 1 8,9 0 2 1 12 7,8,9
154 B4 2 1 2,3,4,7,8,9 0 1 1 12 189 C2 16 1 9 2 2 2 6
155 B4 1 0 1 0 1 1 12 190 C2 8 1 9 2 2 2 6
156 B4 1 0 2 0 1 1 12 191 C2 4 1 9 2 1 2 6
157 B4 1 0 4 0 1 1 12 192 C2 2 1 9 2 1 2 6
158 B4 1 0 7 0 1 1 12 193 C2 2 1 8,9 2 2 2 6
159 B4 1 0 9 0 1 1 12 194 C2 2 1 7,9 2 1 2 6
160 B4 1 0 9 2 1 1 12 195 C2 2 1 7,9 8 1 1 6
161 B4 1 0 9 0 2 1 12 196 C2 2 1 4,9 8 1 1 6
162 B4 1 0 4,9 2 1 1 12 197 C2 2 1 4,9 2 2 2 6
Huawei
163 B4 1 0 7,9 2 1 1 12 198 C2 2 1 2,3,4,7,8,9 2 1 2 6
164 B4 1 0 8,9 0 2 1 12 199 C2 8 1 9 8 2 1 6
165 B4 1 0 3,4,8,9 2 1 1 12 200 C2 4 1 9 8 1 1 6
166 B4 1 0 1,3,5,7,9 2 1 1 12 201 C2 1 0 9 2 2 2 6
167 B4 0,1,2,3,4,5,6, 0 2 1 12 202 C2 1 0 9 8 1 1 6
1 0
7,8,9 203 C2 1 0 9 2 1 2 6
168 B4 0,1,2,3,4,5,6, 1 12 204 C2 1 0 8,9 2 2 2 6
1 0 2 1
7,8,9 205 C2 1 0 4,9 2 1 2 6
169 C0 16 1 9 2 2 6 2 206 C2 1 0 7,9 8 1 1 6
170 C0 8 1 9 2 2 6 2 207 C2 1 0 3,4,8,9 2 1 2 6
171 C0 4 1 9 2 1 6 2 208 C2 1 0 3,4,8,9 2 2 2 6
172 C0 2 1 9 2 1 6 2 209 C2 1 0 1,3,5,7,9 2 1 2 6
173 C0 2 1 8,9 2 2 6 2 210 C2 0,1,2,3,4,5,6, 6
1 0 8 1 1
174 C0 2 1 7,9 2 1 6 2 7,8,9
175 C0 2 1 7,9 8 1 3 2 211 A1/B1 2 1 9 2 1 6 2
176 C0 2 1 4,9 8 1 3 2 212 A1/B1 2 1 4,9 8 1 3 2
177 C0 2 1 4,9 2 2 6 2 213 A1/B1 2 1 7,9 8 1 3 2
178 C0 2 1 2,3,4,7,8,9 2 1 6 2 214 A1/B1 2 1 7,9 2 1 6 2
179 C0 1 0 9 2 2 6 2 215 A1/B1 2 1 4,9 2 2 6 2
180 C0 1 0 9 8 1 3 2 216 A1/B1 2 1 8,9 2 2 6 2
181 C0 1 0 9 2 1 6 2 217 A1/B1 1 0 9 2 2 6 2
182 C0 1 0 8,9 2 2 6 2 218 A1/B1 1 0 9 8 1 3 2
183 C0 1 0 4,9 2 1 6 2 219 A1/B1 1 0 9 2 1 6 2
171
184 C0 1 0 7,9 8 1 3 2 220 A1/B1 1 0 8,9 2 2 6 2
185 C0 1 0 3,4,8,9 2 1 6 2 221 A1/B1 1 0 4,9 2 1 6 2
186 C0 1 0 3,4,8,9 2 2 6 2 222 A1/B1 1 0 7,9 8 1 3 2

Prach formats A1, A2, A3, B1 (TDD) 3GPP 38.211 Table 6.3.3.2-3: Random access configurations for FR1 and unpaired spectrum.
*ž
PRACH Preamble n_SFN mod x= y Subframe Starting Number of 𝑁]*',^cb] number of time – 𝑁[xp
Configuration Format number Symbol PRACH slots domain PRACH occasions PRACH
Index x y within a within a RACH slots duration
subframe
223 A1/B1 1 0 3,4,8,9 2 2 6 2
224 A1/B1 1 0 1,3,5,7,9 2 1 6 2
225 A1/B1 0,1,2,3,4,5,6, 2
1 0 8 1 3
7,8,9
226 A2/B2 2 1 9 0 1 3 4
227 A2/B2 2 1 4,9 6 1 2 4
228 A2/B2 2 1 7,9 6 1 2 4
229 A2/B2 2 1 4,9 0 2 3 4
230 A2/B2 2 1 8,9 0 2 3 4
231 A2/B2 1 0 9 0 2 3 4
232 A2/B2 1 0 9 6 1 2 4
233 A2/B2 1 0 9 0 1 3 4
234 A2/B2 1 0 8,9 0 2 3 4
235 A2/B2 1 0 4,9 0 1 3 4
236 A2/B2 1 0 7,9 6 1 2 4
237 A2/B2 1 0 3,4,8,9 0 1 3 4
238 A2/B2 1 0 3,4,8,9 0 2 3 4
239 A2/B2 1 0 1,3,5,7,9 0 1 3 4
240 A2/B2 0,1,2,3,4,5,6, 4
1 0 6 1 2
7,8,9
241 A3/B3 2 1 9 0 1 2 6
242 A3/B3 2 1 4,9 2 1 2 6
243 A3/B3 2 1 7,9 0 1 2 6
244 A3/B3 2 1 7,9 2 1 2 6
245 A3/B3 2 1 4,9 0 2 2 6
246 A3/B3 2 1 8,9 0 2 2 6
247 A3/B3 1 0 9 0 2 2 6
248 A3/B3 1 0 9 2 1 2 6
249 A3/B3 1 0 9 0 1 2 6
250 A3/B3 1 0 8,9 0 2 2 6
251 A3/B3 1 0 4,9 0 1 2 6
252 A3/B3 1 0 7,9 2 1 2 6
253 A3/B3 1 0 3,4,8,9 0 2 2 6
254 A3/B3 1 0 1,3,5,7,9 0 1 2 6
255 A3/B3 0,1,2,3,4,5,6, 6 172
1 0 2 1 2
7,8,9
223 A1/B1 1 0 3,4,8,9 2 2 6 2

Root Sequence index planning (for TDD 30kHz, short seq)
3GPP 38.211 f40 Table 6.3.3.1-4: Mapping from logical index 𝑖 to sequence number 𝑢
for preamble formats with 𝐿*ž = 139
𝒊 Sequence number 𝑢 in increasing order of 𝑖
0 – 19 1 138 2 137 3 136 4 135 5 134 6 133 7 132 8 131 9 130 10 129
20 – 39 11 128 12 127 13 126 14 125 15 124 16 123 17 122 18 121 19 120 20 119
40 – 59 21 118 22 117 23 116 24 115 25 114 26 113 27 112 28 111 29 110 30 109
60 – 79 31 108 32 107 33 106 34 105 35 104 36 103 37 102 38 101 39 100 40 99
80 – 99 41 98 42 97 43 96 44 95 45 94 46 93 47 92 48 91 49 90 50 89
100 – 119 51 88 52 87 53 86 54 85 55 84 56 83 57 82 58 81 59 80 60 79
120 – 137
138 – 837
61 78 62 77 63 76 64 75 65 74
N/A
66 73 67 72 68 71 69 70 - - 32 root sequences per cell, means we can create
138/32=4 unique cell configurations only, while cell
Short sequences has only 138 root sequences, each of length 139 bits! radius is only 2km. Maximum configuration!
As in LTE, 5G cell must be configured with 64 unique preambles.
Preambles can be generated by cyclic shift from root sequences. Number
of consumed root sequences per cell depends on cyclic shift size.
Cyclic shift size
173
3GPP 38.211-4.1
Massive MIMO

Basic Facts about Massive-MIMO
Works better in TDD ¡ TDD can use reciprocal channel with TM8 (UL & DL on the same frequency)
than FDD ¡ In FDD, UL capacity gain is limited due to inefficient Channel State Information reporting, supported only
by Rel10/13/14 UEs.
Practical in high freq. ¡ Antenna size becomes smaller with increasing frequency, which allows for installation more antenna
bands >1,7…3 GHz elements into one body
Works better in 5G-NR ¡ Beamforming in integrated into 5G-NR from the very beginning
than LTE ¡ Support for modern transmission techniques from very beginning in 5G-NR, unlike in LTE which gain them
in Rel 13
Improves capacity and ¡ Can work as capacity solution (higher SINR à higher MCS), or coverage solution (narrower beam à
coverage smaller pathloss)
Feasible on eCPRI ¡ Beamforming requires powerful data processing, which is not practical to transmit on CPRI interface.
interface ¡ eCPRI interface, which keeps beamforming processing in active antenna, lowers the bandwidth
requirement, between antenna and baseband

Antenna Element Terminology
±45°
One subarray of dual-polarized antenna elements
One dual cross polarized antenna elements,
consisting of two antenna elements
TX1 TX2 4 vertical x 2 vertical x
1 horizontal 1 horizontal
subarray subarray
8TRX 1x4_8x1 16TRX 1x8_8x1 32TRX 2x8_4x1 64TRX 4x8_2x1

2TRX 4TRX Horizontal +4° +8° +15°
1x1_10x1 1x2_10x1 beamforming only
-60° +60° -60° +60° -60° +60°
Beam width is inversely

proportional to antenna -4° -8° -15°
subarray
No Elevation Beam Coarse Elevation beam Fine Elevation Beam

Comparison of NR-MIMO vs. LTE MIMO

Elevation (Vertical) Beamwidth - Dense Urban Environment 16TRX vs 64TRX
Using 16TRX does not bring any vertical

beams, solution is limited in capacity
16TRX
No vertical beamforming, due
to missing vertical sub arrays
Correct usage of 64TRX antenna, due to
high rise skyscraper environment
Area with high rise

buildings is the most
suitable environment
for 64TRX M-MIMO
antenna 64TRX
Vertical beamforming, due to
4 vertical sub arrays
Elevation (Vertical) Beamwidth - Suburban Environment 64TRX
f ve rti ca l b e am
64TRX
u se d p o tential o
normal An un
64TRX
downtilted
Stil
la nu Deployment of 64TRX M-
nus MIMO antenna in suburban
ed
p ot environment may lead to
ent
ial unused vertical beams,
of v
ert therefore inefficient
ical
b ea utilization.
m

Potential Product Positioning (Economical Viability)
64TRX
Dense Urban (64TRX)
mostly seen in SE Asia and N
America
V = 30° ISD ≈ 200-500m
32TRX Urban/Suburban (32TRX)

specific in medium rise buildings,
i.e. majority of European cities
V = 15° ISD ≈ 500-1000m
16TRX
V = 8°
Rural (16TRX & 8TRX)
8TRX specific in low rise buildings,
ISD >1000m
V = 8°

What is a Dense Urban? Where 64TRX?
• 64 TRX allows fast 5G deployment without expensive DAS

64TRX candidate ! systems in skyscraper environment
• Europe has only limited number of skyscrapers districts:
London: Canary Wharf, City
Paris: La Défense
Frankfurt: Bankenviertel
64TRX candidate !
Guangzhou
64TRX candidate ?
Chicago
Munich

Introduction to Single user MIMO (SU-MIMO)
5G-NR
introduces 12 orthogonal
ß DMRS ports to support up
UE1 SR to 12 layers per UE
So ßS
UE2 rP RS o
M r PM I
I fe feed
ed back DL l a
UE3 ba yer 1
ck DL
UE4 lay DL
er lay
DL 1 er 2
lay
er
2
• One user is allocated on time frequency resource through all

layers
• User specific beamforming provides array gain SRS or PMI feedback
is selected based on UE radio conditions, cell edge
• SINR increases as # on antennas increase (improves coverage) UEs are configured with PMI, due to SRS short
• Does not bring higher capacity coverage. However SRS brings better
performance.
• SRS coverage is shorter than PMI coverage (PUCCH)
SRS feedback PMI feedback

Introduction to Multi User MIMO (MU-MIMO)
UE1 UE specific beams
UE2
UE3
UE pairs UE 1
UE4
UE
2
Multiple users are using same time-
UE UE
frequency resources 3
4
• beneficial in BW limited scenarios, or in
high load situation, due to high capacity
gain
• Prerequisite is to find the UE pair, which is
spatially separated, and combined bitrate
of such UE pair is greater than single UE 5G-NR
can get introduces 12 orthogonal
UE1 and UE3 (UE2+UE4 DMRS ports to support up
• Higher antenna # will guarantees
respectively) use the same to 12 layers per UE
successful UE pairing
resources
à capacity increase • 16TRX, 32TRX, 64TRX needed for better
performance, 8TRX only with a limited
gain
Multi-beam Operation
• Beam measurement/reporting
– UE measures different combination of TX-RX beams for initial selection end further refinement
• Beam indication
– Network indicates beam direction for reference signals, and control/data transmission on DL/UL
• Beam failure recovery

– A low latency procedure for recovering from beam failure
– due to the narrow beam width when multi-beam operation is in place, the link between the network and terminal is prone to beam failures
– beam failure recovery allows for prompt beam recovery using L1 procedures

Beamforming Antennas – Summary
¡ 64TRX M-MIMO antennas are overdone for Europe (buildings height)

Summary ¡ There is a considerable risk to overinvest and run into an underutilization of assets
¡ The drawbacks from 32/16TRX antennas are acceptable taking the benefits into
account
¡ 32TRX as standard antenna type for early rollout in urban areas – 16TRX to be
evaluated
Recommendation
¡ Start with available system – 64TRX and change to 32TRX as soon as available, but
depends on mutual scoring (Price x Power consumption x EMF aspects…)
¡ Push for 16TRX for later rollout in sparse urban and suburban areas, (8x8 to
evaluate)

Standalone Topics

RRC States (SA)
Release 13 introduced new state RRC_INACTIVE, it was also standardized for NR
Huawei 5G RAN 2.1
RRC_INACTIVE: NRDUCell.RanNotificationAreaId =; [0~255,65535]
• RRC context is stored in both UE and gNB, and later resumed by ResumeIdentity.
• in Core Network UE’s state is kept CN_CONNECTED, hence the transition to RRC_CONNECTED is fast (no CN signaling is needed)
• gNB initiates RRC Suspend Procedure with signaling message to UE. gNB stores UE’s RRC context
• Last serving gNB keeps UE context, UE freely moves within RNA without updating the gNB. gNB pages UE in RNA, UE initiates RNA update
procedure upon RNA change
RRC Connection Establishment
RRC_IDLE RRC_INACTIVE RRC_CONNECTED

RRC
• No data transfer possible • No data transfer possible • Data transfer possible
Resume
• No RRC context • RRC context established • RRC context established
• No core network connection • Core network connection • Core network connection
• Device-controlled mobility established established
(reselection) • Device-controlled mobility RRC • Network-controlled mobility
(reselection) Suspend (handover)
RRC Connection Release
187
RNA: RAN-based notification area
© Widermind AB Vivacom Sofia 05-19
UE Initial Access
UE gNB-DU gNB-CU-CP gNB-CU-UP AMF
1.RRC Connection Request

2.Initial UL RRC message
3. DL RRC message transfer

4.RRC Connection Setup
5.RRC Connection Setup Complete
6.UL RRC Message Transfer

7.Initial UE message
8.Initial UE Context Setup request
9.Bearer Context Setup Request

gNB
10.Bearer Context Setup Response
gNB-DU gNB-CU-UP gNB-CU-CP
11.UE Context Setup Request
12.RRC Security Mode Command
0. Bearer context setup is
13.UE Context Setup Response
triggered
14.Bearer Context Modification Request
1. Bearer Context Setup Request
15.Bearer Context Modification Response
16.RRC Security Mode Complete
2. Bearer Context Setup Response
17.UL RRC Message Transfer

3. F1 UE context setup procedure
18.DL RRC Message Transfer

4. Bearer Context Modification Request
19.RRC Connection Reconfiguration Uplink user data
20.RRC Connection Reconfiguration 5. Bearer Context Modification Response

Complete 21.UL RRC Message Transfer
Downlink user data
22.Initial UE Context Setup Response

THANK YOU

5G - 201905 - HUA - Version - 1.6

Uploaded by

Copyright:

Available Formats

5G - 201905 - HUA - Version - 1.6

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5G - 201905 - HUA - Version - 1.6

Uploaded by

Copyright:

Available Formats

5G NR Air Interface with focus on Non-

© Widermind AB Vivacom Sofia 05-19 1

© Widermind AB Vivacom Sofia 05-19 2

© Widermind AB Vivacom Sofia 05-19 3

© Widermind AB Vivacom Sofia 05-19 5

Wide BW CRS-free, use

Self containing SCS – SubCarrier Spacing

© Widermind AB Vivacom Sofia 05-19 6

Low latency configurations:

© Widermind AB Vivacom Sofia 05-19 8

Built on a top of LTE

© Widermind AB Vivacom Sofia 05-19 9

ASN.1 - Abstract Syntax Notation One

© Widermind AB Vivacom Sofia 05-19 10

Peak data rate DL: 20 Gb/s UL: 10 Gb/s

Peak spectral efficiency DL: 30 b/s/Hz UL: 10 bit/s/Hz

User-experienced data rate DL: 100 Mb/s UL: 50 Mb/s

Fifth percentile user spectral efficiency 3x IMT-Advanced

Area traffic capacity 10Mb/s/m2

User plane latency 4 ms for eMBB, 1 ms for URLLC

© Widermind AB Vivacom Sofia 05-19 11

© Widermind AB Vivacom Sofia 05-19 12

Dealing with fixed

dealing with the radio

© Widermind AB Vivacom Sofia 05-19 13

© Widermind AB Vivacom Sofia 05-19 14

© Widermind AB Vivacom Sofia 05-19 15

Radio Access Network

© Widermind AB Vivacom Sofia 05-19 16

© Widermind AB Vivacom Sofia 05-19 17

• AUSF - Authentication Server Function

HSS = UDM • UDM - Unified Data Management

© Widermind AB Vivacom Sofia 05-19 18

N22 N12 N8 N10

© Widermind AB Vivacom Sofia 05-19 19

© Widermind AB Vivacom Sofia 05-19 20

© Widermind AB Vivacom Sofia 05-19 21

© Widermind AB Vivacom Sofia 05-19 22

© Widermind AB Vivacom Sofia 05-19 23

3GPP TS 23.501 Figure 5.7.1.5-1

© Widermind AB Vivacom Sofia 05-19 24

Packet Data Convergence

Radio-Link Control (RLC)

Video (Buffered Streaming)

79 65 50 ms 10-2 N/A N/A V2X messages

© Widermind AB Vivacom Sofia 05-19 27

© Widermind AB Vivacom Sofia 05-19 28

Customer’s GTS info Mobile Network Operator

© Widermind AB Vivacom Sofia 05-19 30

© Widermind AB Vivacom Sofia 05-19 31

Option 3 Option 3a Option 3x Option 4 Option 4a

LTE ♣■ NR LTE ■ NR LTE ■ NR ♣ eLTE NR ♣■ eLTE NR ■

Option 7 Option 7a Option 7x Option 2 Option 5

eLTE ♣■ NR eLTE ■ NR eLTE ■ NR ♣ NR ■ eLTE■

Standard eUTRA Option 3x Option 7x Option 4 Option 2 Option 5

EPC LTE Upgrade • • • •

© Widermind AB Vivacom Sofia 05-19 32

S1-C S1-U S1-U

MCGbearer SCG split bearer