100% found this document useful (4 votes)
2K views109 pages

5G Tuning and Optimization - Day4

5G uses time, frequency and space-domain resources for data transmission. In the time domain, resources are allocated in symbols, slots, subframes and frames. Frequency resources are allocated in resource blocks and resource block groups. Bandwidth parts allow configuration of multiple frequency resources. Space-domain resources include codewords, layers, antenna ports and quasi-co-location relationships.

Uploaded by

rahul mathur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
100% found this document useful (4 votes)
2K views109 pages

5G Tuning and Optimization - Day4

5G uses time, frequency and space-domain resources for data transmission. In the time domain, resources are allocated in symbols, slots, subframes and frames. Frequency resources are allocated in resource blocks and resource block groups. Bandwidth parts allow configuration of multiple frequency resources. Space-domain resources include codewords, layers, antenna ports and quasi-co-location relationships.

Uploaded by

rahul mathur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 109

5G Optimization and use

cases.
5G NSA KPI Counter

ALLPPT.com _ Free PowerPoint Templates, Diagrams and Charts


5G High level requirements
• Massive Connectivity

• High Data Rates

• Ultra Low Latency Communication

• Ultra High Reliability and Availability

• Very Low Device Cost and Energy Consumption

• Energy Efficient Networks

70
5G Service Requirements
• Support for fixed, mobile, wireless and satellite access technologies

• A scalable and customizable network that can be tailored to requirements from multiple services and
vertical markets (e.g., network slicing, Network Function Virtualization)

• Resource efficiency for services ranging from low data IoT services to high bitrate multimedia services

• Energy efficiency and battery power optimization

• Network capability exposure to allow 3rd party Internet Service Providers and Internet Content
Providers to e.g. manage network slices, and deploy applications in the operator’s Service Hosting
Environment

• Indirect connectivity from a Remote UE via a Relay UE to the network, and service continuity
between indirect connections and direct connections.
71
What is 5G?
• 5G is deemed as a new Radio technology that enables massive connectivity & Interoperability of devices
whilst also providing higher Data rates and sub 1 ms Latency

• The Moto of 5G is “ Connect any device that would benefit from being connected!”

Implementation Approaches to 5G:

eMBB (enhanced Mobile BroadBand)


• Data Rates in the order of >1Gbps (UL & DL)

mMTC (massive Machine Type Communications)


• IOT Enabler -Seamless connectivity of almost anything that can be connected!

URLLC (Ultra-Reliable and Low Latency Communications)


• Communication requiring low packet loss and sub 1ms latency.(Ex. Health Care)

FFS, TBD, TBC 72


Evolution of 3GPP Technologies

73
Need for 5G - Application and Use Cases
Use Cases
• A very important aspect of the 5G network development is the use cases. These are the services built
on top of the technology, how different networks integrate with one another, and the topology of the
networks.

Third Party Services:


Operator Services: Applications:
• TV Broadcast • Cloud computing
• Proximity Services • Over the Top • Massive
• Public Safety Communication connections
• IoT
• Vehicle communication Radio:
• Faster (+20Gbps)
• Densification (Small Cells)
Networks: • More Capacity
• Wi-Fi Offload • Less Delay
• LTE-Wi-Fi Aggregation • Low cost
• LTE Unlicensed Bands • Low Power
• Relays • Centralization (Cloud RAN)
• Device to Device • More spectrum (mmWave)
74
5G Drivers
• There are two major factors driving the development of 5G:

• A need to support increasing demand for broadband services of many kinds delivered
over mobile networks.
• A desire to support or create services for the Internet of Things (IoT) including for
machine-to-machine (M2M) applications. Two classes of IoT-based applications (massive
IoT and critical IoT) can be distinguished.

• The 3GPP is developing specifications towards 5G. The first 5G specification is expected in
early 2018, enabling the first standards-based networks to be deployed in the 2019-2020
timeframe.

Enhance
Mobile
Broadband

Support Support
Massive IoT Critical IoT
75
IMT-2020 Use Cases

76
5G New Requirement
Summary of Key 5G Requirements in 3GPP 38.913

5G target in 3GPP LTE in practise


Data rates DL 20 Gbps, UL 10 Gbps DL 1 Gbps, UL 0.5 Gbps
Peak spectral efficiency DL 30 bps/Hz, UL 15 bps DL 30 bps/Hz, UL 15 bps
Latency User 1 ms, control 10 ms User 10 ms, control 50 ms
Reliability 10-5 = 99.999% Not defined
Network virtualization New open interfaces Not flexible
Connection density 1M/km2 Not defined
Mobility 500 km/h 350 km/h
Coverage 164 dB 164 dB (NB-IoT)
5G Working Standards Groups
• EU project METIS which stands for Mobile and wireless
communications Enablers for the Twenty-twenty Information
Society. The main objective of the project is lay the foundation of 5G,
the next generation mobile and wireless communications system.
•"
Challenges and Scenarios of the fifth Generation (5G) Wireless Communicatio
ns System
" (made by Dr. Afif Osseiran on November 15, 2013 at KTH, Stockholm)
• "Mobile and Wireless Communications system for 2020 and beyond (5G)"
(made by Dr. Afif Osseiran at the WP5D workshop on “Research views on IMT
beyond 2020” on February 12, 2014, Vietnam)
5G Working Standards Groups
• The 5G Infrastructure Public Private
Partnership (5G PPP) is a joint initiative
between the European Commission and
European ICT industry (ICT
manufacturers, telecommunications
operators, service providers, SMEs and
researcher Institutions). The 5G-PPP is
now in its third phase where many new
projects were launched in Brussels in June
2018.
5G SYSTEM
• High level 5G Architecture consist of 5G Core
and 5G Access Network
• Unlike pervious 3GPP technologies – 5G Core
is compliant , proficient to work seamlessly
with more than one access technology

• The possibility of E-UTRA & NR connecting to 5GC


creates several connectivity scenarios which have
listed and studied in TR23.799

81
5G Training Course

NR FRAME STRUCTURE AND


AIR INTERFACE RESOURCES

82
Contents

1 Numerology

2 Time-Domain Resources

3 Frequency-Domain Resources

4 Space-Domain Resources

83
OVERVIEW OF NR AIR INTERFACE RESOURCES (TIME-,
FREQUENCY-, AND SPACE-DOMAIN RESOURCES)
Numerology (system parameter): refers to subcarrier spacing (SCS) in New Ra-
dio (NR) and related parameters, such as the symbol length and cyclic prefix
(CP) length.Time-domain
resources
CP Basic scheduling unit

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

SCS RB RBG Bandwidth part Carrier


(BWP)
Frequency-domain Data channel/control channel scheduling unit
resources
Existed in LTE
REG CCE Unchanged in NR
1 REG = 1 1 CCE = 6 REGs Existed in LTE
PRB Modified in NR
Space-domain resources Codeword Layer Antenna port
Added in NR
QCL

NR uses orthogonal frequency division multiple access (OFDMA), same as LTE does.
The main description dimensions of air interface resources are similar between LTE and NR except that BWP is added to NR in the frequency domain.

84
SCS–BACKGROUND AND PROTOCOL-PROVIDED
DEFINITION
• Background
• Numerologies defined in 3GPP Release 15 (TS
38.211) with SCS identified by the parameter µ.
– Service types supported by NR: eMBB, URLLC, mMTC,
Parameter
etc. SCS CP
µ
– Frequency bands supported by NR: C-band, mmWave, 0 15 kHz Normal
1 30 kHz Normal
etc. 2 60 kHz Normal, extended
– Moving speed supported by NR: up to 500 km/h 3 120 kHz Normal
4 240 kHz Normal
• Requirements for SCS vary with service types, fre-
*(LTE supports only 15 kHz SCS.)
quency bands, and moving speeds.
• Available SCS for data channels and synchroniza-
– URLLC service (short latency): large SCS
tion channels in 3GPP Release 15
– Low frequency band (wide coverage): small SCS Supported for Data
Parameter Supported for Sync
SCS (PDSCH, PUSCH
– High frequency band (large bandwidth, phase noise): µ (PSS, SSS, PBCH)
etc)
large SCS 0 15 kHz Yes Yes
1 30 kHz Yes Yes
– Ultra high speed mobility: large SCS
2 60 kHz Yes No
• NR SCS design principle 3 120 kHz Yes Yes
– NR supports a series of SCS values. 4 240 kHz No Yes
Based on LTE SCS of 15 kHz, a series of numerologies (mainly different SCS values) are supported to adapt to different requirements and channel characteristics.

85
SCS: APPLICATION SCENARIOS AND
SUGGESTIONS
• Impact of SCS on coverage, latency, mobility, and phase • Coexistence of different SCS values and FDM
noise – The eMBB and URLLC data channels use different SCS
– Coverage: The smaller the SCS, the longer the symbol length/CP, and the values and coexist through FDM.
better the coverage.
– Mobility: The larger the SCS, the smaller the impact of Doppler shift, and
the better the performance.
– Latency: The larger the SCS, the shorter the symbol length/latency.
– Phase noise: The larger the SCS, the smaller the impact of phase noise,
and the better the performance.
• SCS application suggestions for different frequency bands
SCS (kHz)
(eMBB service 15
data channel):30 60 120 240
– The PBCH and PDSCH/PUSCH use different SCS values
good bad
Coverage
good and coexist through FDM.
bad
3.5 GHz Mobility
bad good
Latency

good bad
Coverage
bad good
Mobility
28 GHz bad good
Phase Noise
bad good
Latency

It is recommended that the SCS be 30 kHz for C-band and 120 kHz for 28 GHz. Different SCS values and coexistence through FDM are supported.
86
SCS CONFIGURATION FOR PHYSICAL
CHANNELS AND SIGNALS gNodeB UE
SS/PBCH
Channel SCS Defined in 3GPP Release 15 Configuration Scheme SCS: protocol-defined default
value
RAN4 defines the RMSI (SIB1)
default SCS for each SCS: configured in MIB
Sub-6 GHz: 15/30 kHz
SS/PBCH frequency band (see
Above-6 GHz: 120/240 kHz
Table 5.4.3.3-1 in 3GPP PRACH
TS 38.104). SCS: configured in RMSI

Sub-6 GHz: 15/30 kHz


Initial RMSI, Msg2/4 (PDSCH) MIB
Above-6 GHz: 60/120 kHz Msg2 (random access response)
access SCS: same as RMSI

Long PRACH: SCS = {1.25 5} kHz Msg3 (transmitted over PUSCH)


Msg1 (PRACH), Msg3 SCS: configured in RMSI
Short PRACH: SCS = {15, 30, 60,
(PUSCH) RMSI
120} kHz, where: sub-6 GHz: 15/30
Msg4 (transmitted over PDSCH)
kHz, above-6 GHz: 60/120 kHz SCS: same as RMSI

Sub-1 GHz: 15/30 kHz


PDSCH/PDCCH/CSI-RS 1 GHz to 6 GHz: 15/30/60 kHz RRC signaling DL: PDSCH/PDCCH/CSI-RS
RRC Above-6 GHz: 60/120 kHz SCS: configured in RRC signaling
connected
mode Sub-1 GHz: 15/30 kHz
PUSCH/PUCCH/SRS 1 GHz to 6 GHz: 15/30/60 kHz RRC signaling UL: PUSCH/PUCCH/SRS
Above-6 GHz: 60/120 kHz SCS: configured in RRC signaling

The protocol-defined SCS is used by the synchronization and broadcast channels involved in initial access. The SCS for other chan -
nels is configured in the MIB, RMSI, and RRC signaling.
87
Contents

1 Numerology

2 Time-Domain Resources: CP, Symbol, Slot, Frame Struc-


ture
3 Frequency-Domain Resources

4 Space-Domain Resources

88
TIME-DOMAIN RESOURCES: RADIO FRAME,
SUBFRAME, SLOT, SYMBOL
Radio frame Inherited from LTE and
has a fixed value of 10
ms
Subframe Subframe... Subframe Inherited from LTE and has
a fixed value of 1 ms

Slot Slot ... Slot Minimum unit for data schedul-


ing

Symbol Symbol Symbol .. Symbol Basic unit for modulation


.

Sampling Sampling
point point
...
Sampling
point
Basic time unit at the physical layer
In the time domain, slot is a basic scheduling unit for data channels. The concepts of radio frames and subframes are the
same as those in LTE.
89
SYMBOL LENGTH–DETERMINED BY SCS

SCS = 15 kHz
 Symbol = CP + Data T_slot = 1 ms (14 symbols)
 SCS vs CP length/symbol length/slot length
– Length of OFDM symbols in data: T_data = 1/SCS
CP data …
– CP length: T_cp = 144/2048 x T_data T_symbol
– Symbol length (data+CP): T_symbol = T_data +T_cp T_slot = 0.5 ms (14 symbols)

SCS = 30 kHz
– Slot length: T_slot = 1 / 2^(µ)

Parameter/Numerology (µ) 0 1 2 3 4
SCS (kHz):

15 30 60 120 240
SCS = 15 x 2^(µ)
T_symbol
OFDM Symbol Duration (µs):
66.67 33.33 16.67 8.33 4.17 T_slot = 0.125 ms (14 symbols)
T_data = 1/SCS
CP Duration (µs):
4.69 2.34 1.17 0.59 0.29
T_cp = 144/2048 x T_data

SCS = 120
OFDM Symbol Including CP (µs):

kHz
T_symbol = T_data + T_cp
71.35 35.68 17.84 8.92 4.46 …
Slot Length (ms):
1 0.5 0.25 0.125 0.0625
T_slot = 1/2^(µ)
T_symbol
A symbol consists of a CP and data. The length of the data is the reciprocal of SCS. The larger the SCS, the smaller the symbol length and the slot length.
90
CP: BACKGROUND AND PRINCIPLES
 Multipath latency extension
– The width extension of the received signal pulse caused by multipath is the dif-
ference between the maximum transmission latency and the minimum transmis-
sion latency. The latency extension varies with the environment, terrain, and clut-
ter, and does not have an absolute mapping relationship with the cell radius.

 Impact
– Inter-Symbol Interference (ISI) is generated, which severely affects the transmis-
sion quality of digital signals.
– Inter-Channel Interference (ICI) is generated. The orthogonality of the subcarriers
in the OFDM system is damaged, which affects the demodulation on the receive
side.

 Solution: CP for reduced ISI and ICI


– Guard intervals reduce ISI. A guard interval is inserted between OFDM symbols,
where the length (Tg) of the guard interval is generally greater than the maximum
latency extension over the radio channel.
– CP is inserted in the guard interval to reduce ICI. Replicating a sampling point fol-
lowing each OFDM symbol to the front of the OFDM symbol. This ensures that
the number of waveform periods included in a latency copy of the OFDM symbol
is an integer in an FFT period, which guarantees subcarrier orthogonality.

CPs between OFDM symbols resolve ISI and ICI caused by multipath propagation.
91
FRAME STRUCTURE: ARCHITECTURE
 Frame structure architecture:
 Frame length: 10 ms  Example: SCS = 30 kHz/120 kHz
– SFN range: 0 to 1023
1 frame = 10 ms = 10 subframes = 20 slots
 Subframe length: 1 ms
– Subframe index per system frame: 0 to 9

SCS = 30
1 subframe = 1 ms = 2 slots
 Slot length: 14 symbols

kHz
Slot Configuration (NCP)
SCS 1 slot = 0.5 ms = 14 sym-
(kHz) Number of Number of Number of Slots bols
Symbols/Slot Slots/Subframe /Frame
1 frame = 10 ms = 10 subframes = 80 slots
15 14 1 10
30 14 2 20
60 14 4 40

SCS = 120
120 14 8 80 1 subframe = 1 ms = 8 slots

kHz
240 14 16 160
480 14 32 320

Slot Configuration (ECP) 1 slot = 0.125 ms = 14 symbols


60 12 4 40

The lengths of a radio frame and a subframe in NR are consistent with those in LTE. The number of slots in each subframe is deter -
mined by the subcarrier width.
92
SLOT FORMAT AND TYPE
 Slot structure (section 4.3.2 of 3GPP TS 38.211)  Compared with LTE, NR has the following slot format fea-
– Downlink, denoted as D, for downlink transmis- tures:
sion – Flexibility: symbol-level uplink/downlink adaptation in NR and
– Flexible, denoted as X, for uplink or downlink subframe-level in LTE
transmission, GP, or reserved. – Diversity: More slots are supported in the NR system to cope
– Uplink, denoted as U, for uplink transmission with more scenarios and service types.
 Main slot types  Examples of application scenarios of different slots:
– Case 1: DL-only slot
– Case 2: UL-only slot Slot Type Application Scenario Example

– Case 3: flexible-only slot Case 1 DL-heavy transmission


– Case 4: mixed slot (at least one downlink slot Case 2 UL-heavy transmission
and/or one uplink slot) 1. Forward compatibility: Resources are reserved for future services.
Case 3 2. Adaptive adjustment of uplink and downlink resources: such as dynamic
D U X TDD

Case 1: DL-only slot Case 2: UL-only slot Case 3: flexible-only slot Case 4-1 1. Forward compatibility: Resources are reserved for future services.
2. Flexible data transmission start and end locations: such as unlicensed
D X X U Case 4-2 frequency bands and dynamic TDD

Case 4-1 Case 4-2 Case 4-3 Downlink self-contained transmission

D XU DX U D XU D XU Case 4-4 Uplink self-contained transmission

Case 4-3 Case 4-4 Case 4-5 Case 4-5 Mini-slot (seven symbols) for URLLC services

The number of uplink and downlink symbols in a slot can be flexibly configured. In Release 15, a mini-slot contains 2, 4, or 7 symbols
for data scheduling in a short latency or a high frequency band scenario.
93
SELF-CONTAINED SLOTS/SUBFRAMES
 The self-contained slots or sub-  Self-contained slot/subframe design
frames discussed in the industry objectives
and literature are featured as fol- –

Faster downlink HARQ feedback and uplink data scheduling: reduced RTT
Shorter SRS transmission period: to cope with fast channel changes for
lows: improved MIMO performance

 Problems in application Air interface


round-trip la-
tency

D U Downlink data processing time:


Part of the GP needs to be reserved for
The small GP limits cell coverage. demodulating downlink data and generat-
– One slot or subframe contains uplink part, downlink part, and GP. ing ACK/NACK feedback.
– Downlink self-contained slot or subframe: includes downlink data and
corresponding HARQ feedback.
ACK/NACK
D U
UL control or SRS – High requirements on UE hardware processing:
• Release 15 defines two types of UE processing capabilities. The baseline capa-
DL control bility is 10 to 13 symbols if the SCS is 30 kHz and self-contained transmission
is not supported.
– Frequent uplink/downlink switching increases the GP overhead.
D U UL grant
– In the downlink, only the retransmission latency can be reduced.
• E2E latency depends on many factors, including the core network and air inter-
face.
–Uplink self-contained slot or subframe: includes uplink scheduling information
• The latency on the air interface side is also limited by the uplink/downlink frame
Self-contained
and uplink data .
subframes reduce the RTT latency on the RAN side but limits cell
configuration, coverage.
and the Therefore,
processing latency on the gNodeB high requirements
and UE.
are posed on hardware processing capabilities of UEs.
94
MINI-SLOT: SUPPORT FOR THE LENGTH OF 2, 4, OR 7
SYMBOLS IN RELEASE 15
 Mini-slot: fewer than 14 symbols in the time  Application scenario
domain – Short-latency scenario: reduces the scheduling wait-
ing latency and transmission latency.
 Basic scheduling units are classified into
– Unlicensed frequency band: Data can be transmitted
the following types: immediately after listen before talk (LBT).
– Slot-based: The basic scheduling unit is slot, and the – mmWave scenario: TDM is applied for different UEs
time-domain length is 14 symbols. in a slot.
– Non-slot-based: The basic scheduling unit is mini-slot. In 1. URLLC for low latency
Release 15, the time-domain length is 2, 4, or 7 symbols.

2. eMBB in unlicensed band

Slot-based PD- PDSCH


CCH
3. mmWave
PDSCH (mini-slot)
Non-slot-based PDSCH
(mini-slot)

Release 15 supports mini-slots with the length of 2, 4, or 7 symbols, which can be applied in short latency and mmWave
scenarios.
95
Contents

1 Numerology

2 Time-Domain Resources

3 Frequency-Domain Resources: RB, RBG, REG, CCE, BWP

4 Space-Domain Resources

96
BASIC CONCEPTS OF FREQUENCY-DOMAIN
RESOURCES One subframe

 Resource Grid (RG)


– Physical-layer resource group, which is defined separately for ,
subframe
Nsymb OFDM symbols
the uplink and downlink (RGs are defined for each numerol- max, RB
k  NRB,
x Nsc 1
ogy).
– Frequency domain: available RB resources within the trans-
mission bandwidth
– Time domain: 1 subframe

subcarriers

subcarriers
N scRB
 Resource Block (RB)

RB
N RB

sc

N
– Basic scheduling unit for data channel resource allocation in Resource Ele-
Resource element
the frequency domain ment
(k , l )

Resource Block
block
– Frequency domain: 12 consecutive subcarriers

Resource Grid
 Resource Element (RE)

Resource
– Minimum granularity of physical-layer resources
– Frequency domain: 1 subcarrier
– Time domain: 1 OFDM symbol k 0
l 0 l  14  2   1

In NR, an RB corresponds to 12 subcarriers (same as LTE) in the frequency domain. The frequency-domain width is related
to SCS and is calculated using 2µ x 180 kHz.
97
PRB/RBG AND CCE: FREQUENCY-DOMAIN BASIC
SCHEDULING UNITS
 Basic scheduling unit for data channels: PRB/  Basic scheduling unit for control
RBG channels: CCE
– Physical RB (PRB): Indicates the physical resource block in the – RE Group (REG): basic unit for control channel re-
BWP. source allocation
– Frequency domain: 12 subcarriers – Frequency domain: 1 REG = 1 PRB (12 subcarri-
ers)
– Resource Block Group (RBG): a set of physical resource blocks
– Time domain: 1 OFDM symbol
– Frequency domain: The size depends on the number of RBs
– Control Channel Element (CCE): basic scheduling
in the BWP. unit for control channel resource allocation
RBG Size – Frequency domain: 1 CCE = 6 REGs = 6 PRBs
BWP Size (RBs)
Config 1 Config 2
1–36 2 4 – CCE aggregation level: 1, 2, 4, 8, 16
37–72 4 8
73–144 8 16 REG DMRS
145–275 16 16
4 RBs CC
DMRS PRB
E
RB RB0 RB1 RB2 RB3 RB4 RB5 RB6 RB7 RB8 RB9 RB10 RB11 RB12 …

DMRS
RBG RBG0 RBG1 RBG2 …

In the frequency domain, the PRB or an RBG is a basic scheduling unit for data channels, and the CCE is a basic schedul -
ing unit for control channels.
98
CHANNEL BANDWIDTH AND TRANSMISSION
BANDWIDTH
 Channel bandwidth
– Channel bandwidth supported by the FR1 frequency
band (450 MHz to 6000 MHz): 5 MHz (minimum),
100 MHz (maximum)
– Channel bandwidth supported by the FR2 frequency
band (24 GHz to 52 GHz): 50 MHz (minimum), 400
MHz (maximum).
 Maximum transmission bandwidth (max-
imum number of available RBs)
– Determined by the channel bandwidth and data
channel SCS.
– Defined on the gNodeB side and UE side sepa-
rately. For details about the protocol-configuration of Active RBs
the UE side, see the figure on the right.
Guard band
 Guard bandwidth
– With F-OFDM, the guard bandwidth decreases to
about 2% in NR (corresponding to 30 kHz SCS, 100
MHz channel bandwidth).

Compared with the guard bandwidth (10%) in LTE, NR uses F-OFDM to reduce the guard bandwidth to about 2%.
99
MAXIMUM NUMBER OF AVAILABLE RBS AND SPECTRUM
UTILIZATION
 Spectrum utilization = Maximum transmission bandwidth/Channel bandwidth
– Maximum transmission bandwidth on the gNodeB side: See Table 5.3.2-1 and 5.3.2-2 in 3GPP TS 38.104.
5 10 15 30 20 25 40 50 60 70 80 90 100
SCS MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz MHz
[kHz]
NRB and Spectrum Utilization (FR1:400 MHz to 6000 MHz)

25 52 79 [160] 106 133 216 270 N/A N/A N/A N/A N/A
15
90% 93.6% 94.8% [96%] 95.4% 95.8% 97.2% 97.2% \ \ \ \ \
11 24 38 [78] 51 65 106 133 162 [189] 217 [245] 273
30
79.2% 86.4% 91.2% 91.8% 93.6% 95.4% 95.8% 97.2% 97.7% 98.3%
N/A 11 18 [38] 24 31 51 65 79 [93] 107 [121] 135
60
79.2% 86.4% 86.4% 893% 91.8% 93.6% 94.8% 93.6% 97.2%

50 MHz 100 MHz 200 MHz 400 MHz


SCS
NRB and Spectrum Utilization (FR2: 24
[kHz]
GHz to 52 GHz)
66 132 264 N/A
60
95% 95% 95% \
32 66 132 264
120
92.2% 95% 95% 95%

– Maximum transmission bandwidth on the UE side: See 3GPP TS 38.101-1 and TS 38.101-2.

Spectrum utilization is related to the channel bandwidth. The higher the bandwidth, the higher the spectral efficiency.
100
RB LOCATION INDEX AND INDICATION
 BWP is introduced to the NR system, which causes Reference
0 CRB Index in
Location
differences in the RB location index and indication Offset RG
0 PRB Index in
from LTE. BWP
RG
 Related concepts (section 4.4 of 3GPP TS 38.211)
– RG: In the frequency domain, an RG includes all available 0 1 2 3 … 0 1 2 3 … Freq.
RBs within the transmission bandwidth.
– BWP: new concept introduced in the NR system. It refers Point A BWP

to some RBs in the transmission bandwidth and is config- Point A Reference Location Offset

ured by the gNodeB. PCell DL SSB start location UEs are informed of this information through the RMSI.
(TDD/ UEs perform blind detection to obtain this Parameter:
– Point A: basic reference point of the RG FDD) information. PRB-index-DL-common
– Defined for the uplink, downlink, PCell, SCell, and SUL separately PCell UL
UEs are informed of this information through the RMSI.
Same as Point A for the PCell downlink Parameter:
– Point A = Reference Location + Offset (TDD)
PRB-index-UL-common
– For details about the reference location and offset for different ref- Frequency-domain location of the ARFCN UEs are informed of this information through the RMSI.
erence points, see the figure on the right. PCell UL
UEs are informed of this information Parameter:
(FDD)
through the RMSI (SIB1). PRB-index-UL-common
– Common RB (CRB): index in the RG
UEs are informed of this information through RRC
– The center of 0# subcarrier of CRB#0 is aligned with that of Point Frequency-domain location of the ARFCN signaling.
SCell
A. DL/UL
UEs are informed of this information Parameter:
through the SCell configuration message. PRB-index-DL-Dedicated
– Physical RB N(PRB):
size
BWP,i  1
index in the BWP PRB-index-UL-Dedicated
start
– Index: 0 to nCRB  n PRB  N BWP, i UEs are informed of this information through RRC
start Frequency-domain location of the ARFCN
–N BWP,i
Relationship between PRB and CRB: SUL UEs are informed of this information
signaling.
Parameter:
is the number of CRBs between the BWP start position and through the SCell configuration message.
PRB-index-SUL-common
CRB#0.
Point A is the basic reference point in the RG. CRB is the RB index in the RG, and PRB is the RB index in the BWP.
101
BWP DEFINITION AND APPLICATION SCENARIOS
 Definition and characteristics
– The Bandwidth Part (BWP) is introduced in NR. It is a set of contiguous bandwidth resources configured by the gNodeB for UEs to
achieve flexible transmission bandwidth configuration on the gNodeB side and UE side. Each BWP corresponds to a specific nu-
merology.
– BWP is specific to UEs (BWP configurations vary with UEs). UEs do not need to know the transmission bandwidth on the gNodeB
side but only needs to support the configured BWP bandwidth.

 Application scenarios
– Scenario#1: UEs with a small bandwidth access a large-bandwidth network.
– Scenario#2: UEs switch between small and large BWPs to save battery power.
– Scenario#3: The numerology is unique for each BWP and service-specific.
BWP 1

#1 #2
BWP

BWP 2
BWP Bandwidth

Carrier Bandwidth Carrier Bandwidth

#3
Numerology Numerology 2
1
BWP1 BWP 2

Carrier Bandwidth

BWP is a set of contiguous bandwidth resources configured by the gNodeB for UEs. The application scenario examples are as follows: UEs supporting small band-
widths, power saving, and support for FDM on services of different numerologies.
102
BWP TYPES
 BWP types
– Initial BWP: configured in the initial access phase. Signals and channels are transmitted in the initial BWP during initial access.
– Dedicated BWP: configured for UEs in RRC_CONNECTED mode. A maximum of four dedicated BWPs can be configured for a
UE.
– Active BWP: one of the dedicated BWPs activated by a UE in RRC_CONNECTED mode. According to Release 15, a UE in
RRC_CONNECTED mode can have only one active BWP at a given time.
– Default BWP: It is one of the dedicated BWPs and is indicated by RRC signaling. A fter the BWP inactivity timer expires, the UE
in RRC_CONNECTED mode switches to the default BWP.
Random Access Procedure RRC Connected Procedure
PDCCH indicating downlink assignment
Default
Default UE2 BWP inactivity
timer
UE1 Dedi- UE2 Dedi-
UE1 UE2 cated cated UE2 switches to the de-
BWPs BWPs fault BWP.
Active
Active
Switch
Initial BWP
default
Carrier Bandwidth
UE1 Active BWP UE2 Active BWP UE1 Active BWP UE2 Active BWP
Carrier Bandwidth Carrier Bandwidth

103
INITIAL BWP CONFIGURATION
 Initial DL BWP definition and configu-  Initial UL BWP definition and
ration configuration
– Function: The PDSCH used to transmit RMSI, Msg2, and Msg4 must be – Function: The PUSCH used to transmit Msg3, PUCCH used to
transmitted in the initial active DL BWP. transmit Msg4 HARQ feedback, and PRACH resources during
– Definition of the initial DL BWP: frequency-domain location and bandwidth of initial access must be transmitted in the initial active UL BWP.
RMSI CORESET (control channel resource set) and a numerology correspond- – The initial DL BWP and initial UL BWP are separately configured.
ing to the RMSI – Numerology: same as that of Msg3 (configured in RMSI).
– Fre-
The frequency-domain location and bandwidth of the RMSI CORESET are in- – Frequency-domain location:
quency
dicated in the PBCH (MIB). The default bandwidth is {24,48,96} RBs. – FDD (paired spectrum), SUL: configured in RMSI
CORESET – TDD (unpaired spectrum): same as the center frequency
PDSCH band of the initial DL BWP
SSB

Initial DL BWP – Bandwidth


– Configured in RMSI and no default bandwidth option is avail-
Frequency offset able.
Time
The frequency offset in PRB level which is between RMSI CORESET
and SS/PBCH block is defined as the frequency difference from the
lowest PRB of RMSI to the lowest PRB of SS/PBCH block.
Procedure for UEs to determine the initial BWP

UEs search for the SSB UEs demodulate the PBCH to obtain UEs receive the RMSI to obtain the
to obtain the frequency- the frequency offset and bandwidth in- frequency-domain location, band-
domain location of the formation of the RMSI CORESET and width, and numerology information of
SSB. determine the initial DL BWP. the initial UL BWP.
104
DEDICATED BWP CONFIGURATION
 Dedicated BWP configuration  UE Dedicated PRB Location
– Sent to UEs through RRC signaling – Dedicated BWP locations of all UEs in a cell are based on the same
– FDD (paired spectrum): Up to four downlink common reference point (Point A).
dedicated BWPs and four uplink dedicated – UEs determine the start location of the dedicated BWP based on the
BWPs can be configured. offset relative to Point A.
– TDD (unpaired spectrum): A total of four up- – Based on the dedicated BWP bandwidth, UEs obtain the end loca-
link/downlink BWP pairs can be configured. tion of the dedicated BWP.
– SUL: 4 uplink dedicated BWPs – UEs obtain the frequency-domain location and size of the dedicated
– The smallest unit is one PRB. The dedicated BWP.
BWP is equal to or smaller than the maximum UE2 Offset
bandwidth supported by a UE.
– Each dedicated BWP can be configured with UE1 Offset
the following attributes through RRC signal-
ing:
– Numerology (SCS, CP type) UE2 Active BWP
UE1 Active BWP
– Bandwidth (a group of contiguous PRBs)
Point A Cell Carrier Bandwidth
– Frequency location (start location)

Offset: UEs can obtain the offset for each dedicated BWP from
– UEs can activate only one dedicated BWP at RRC signaling.
a given time as the active BWP.
After a UE accesses the network, the dedicated BWP is configured through RRC signaling. A maximum of four dedi -
cated BWPs can be configured.
105
BWP ADAPTATION
 BWP Adaptation  BWP Adaptation application scenarios
 UEs in RRC_CONNECTED mode switch between dedi-
– The BWP bandwidth changes: e.g. switching to the
cated BWPs (only one dedicated BWP can be activated
at a given time). power saving state.
 BWP Adaptation is completed through switchovers and – BWP location movement in the frequency domain:
involves the following: e.g. to increase scheduling flexibility.
– DCI – The BWP numerology changes: e.g. to allow differ-
 FDD: downlink: downlink DCI, uplink: uplink DCI ent services.
 TDD: If the uplink or downlink DCI includes a
switchover indication, BWP switchovers are per-
formed in the uplink and downlink.
 RF conversion time (defined in RAN4,
– Timer mechanism sub-6 GHz)
 If the BWP inactivity timer expires, UEs switch to
the default BWP (one of the dedicated BWPs).
Intra-Band
 Timer granularity: 1 ms for sub-6 GHz, 0.5 ms for Relationship
mmWave Between
PDCCH indicating downlink assign- Same Different Inter-Band
ment timer
UE BWP inactivity BWP1 and Center Center
BWP2 Frequency Frequency
The UE switches to the de-
fault BWP.
Time ≤ 20µs 50–200 µs ≤ 900 µs

In RRC connected mode, switching between BWPs is realized through DCI or timer mechanisms.
106
Contents

1 Numerology

2 Time-Domain Resources

3 Frequency-Domain Resources

4 Space-Domain Resources: Layer, Antenna Port, QCL

107
CODEWORDS AND ANTENNA PORTS
 Basic concepts  Protocol-defined number of
– Codeword codewords
– Upper-layer service data on which channel coding applies.
– 1 to 4 layers: 1 codeword
– Codewords uniquely identify data flow. By transmitting different data, MIMO
implements spatial multiplexing. The number of codewords depends on the – 5 to 8 layers: 2 codewords
rank of the channel matrix.
– Layer  Protocol-defined number of
– The number of codewords is different from the number of transmit antennas.
Therefore, codewords need to be mapped to transmit antenna.
layers
– Antenna port – DL: up to eight layers for a single user and four lay-
– Logical ports used for transmission. Antenna ports do not have a one-to-one ers for multiple users
Maximum
Channel/Signal Number of Antenna Port#
relationship with physical antennas. They can be mapped to one or more – UL: up to four layers for a single user or multiple
Ports
physical antennas. users {0,1,2,…,7} DMRS type 1
– Antennas ports are defined based on reference signals. PUSCH with DMRS 8 or 12
{0,1,2,…,11} DMRS type 2

Codewords Layers
 ULProtocol-defined
PUCCH 1 number of an-
{2000}
Antenna ports PRACH 1 {4000}
Scrambling
Modulation
mapper Antenna
RE mapper
OFDM signal
generation
tennaSRSports4 {1000,1001,1002,1003}
Layer
mapper
Port {1000, 1001,…,1007} DMRS type 1
mapper PDSCH with DMRS 8 or 12
Scrambling
Modulation OFDM signal {1000, 1001,…,1011} DMRS type 2
mapper RE mapper
generation
DL PDCCH 1 {2000}
CSI-RS 32 {3000,3001,3002,…,3031}
Number of codewords ≤ Number of layers ≤ Number of antenna ports SSB 1 {4000}

In NR, a maximum of two codewords are supported. The maximum number of DMRS antenna ports is increased to 12.
108
109

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy