NETWORK

ENGINEERING

5G Scheduler
5GC000523 TDD scheduler for Multi-UE support
5GC000542 Support of UL/DL ratios

Network Engineering Information

• 5af2b0e5c8658e001239155b
• 1.1
• Maciej Pol
• Approved
• 17.05.2018
earlyBird
Please, always check the latest version of NEI slides.
1 © Nokia 2018 Nokia Internal Use
Agenda

1 2
Introduction Technical
Details
3
Configuration
Management
4
Performance
Management

7 © Nokia 2018 Nokia Internal Use

Agenda

1 2
Introduction Technical
Details
3
Configuration
Management
4
Performance
Management

8 © Nokia 2018 Nokia Internal Use

Introduction
Features and sub-features covered in this material

5GC000542 Support of UL DL ratios 5GC000523 TDD Scheduler for Multi-UE support

• 5GC000542-A:
• Adaptation to cell configuration
• UL/DL ratio 2:8
• 5GC000542-B:
• UL/DL ratio 3:7
• 5GC000542-C:
• UL/DL ratio 1:9
• 5GC000542-D:
• UL/DL ratio 5:5
• 5GC000523-A:
• Pre-scheduling
• TD scheduling (including beam selection)
• FD scheduling (resource allocation and TBS
determination)
• Pro-active UL scheduling
• 5GC000523-B:
• PUCCH format 2 up to 11 bits
• 5GC000523-C:
• CSI-RS in SSB slots and data slots
• PUCCH format 2 more than 22 bits
• 5GC000523-D:
• CSI handling (CSI-RS transmission / CSI reporting,
CSI and PUCCH resource configuration)
• 5GC000523-F:
• User Plane PM counters

9 © Nokia 2018
Introduction
Features and sub-features covered in this material

• Some of sub-features from 5GC000523 are not yet covered in this material due to not available
CFAM:
• 5GC000523-E (Advanced scheduling procedures):
• SR handling
• RACH procedure for multi UE
• MCS reduction in DL due to low amount of data in the buffer
• MCS and PRB reduction in UL due to low amount of data in the buffer
• Multi-carrier testing
• Exploiting unpaired UL subcells for PUCCH resource multiplexing in < 6GHz
• Combining CSI reports for beam management and channel aquisition on same PUCCH
resource
• 5GC000523-G and 5GC000523-H:
• Aperiodic UCI on PUSCH

10 © Nokia 2018
Introduction
Dual Connectivity NSA mode 3x operation

• First Nokia implementation of 5G relays on Dual Connectivity NSA mode 3x operation

• Dual Connectivity NSA mode 3x operation requires interworking of LTE eNB and NR 5GNB as well as legacy EPC as Core
Network part

C-Plane connectivity towards U-Plane connectivity towards EPC/S-GW

P-GW/ EPC is realized by 5GNB, playing the role of
EPC/MME is realized by LTE MME S-GW
eNB, playing a role of MeNB SgNB (Secondary gNB)
(Master eNB)

C-Plane
U-Plane
MeNB provides the MeNB SgNB
connectivity for both C-
Plane and U-Plane data SgNB provides the
4G 5G
connectivity for U-Plane
data only
Dual Connectivity
• On air interface the Dual Connectivity capable UE terminal is connected with both LTE and 5G cell simultaneously

11 © Nokia 2018 Nokia Internal Use

Introduction
Dual Connectivity NSA mode 3x operation

• In Dual Connectivity NSA mode 3x operation:

• DL User data sent by S-GW fall into NR PDCP entity of SgNB and based on X2-
U Downlink Data Delivery Status (DDDS) message exchanged between the
MeNB and SgNB, the SgNB evaluates the share of these DL data to be sent over P-GW/ EPC
two paths MME S-GW

• the first paths for DL data goes over NR RLC and NR MAC of SgNB and
directs these data towards physical layer of 5G cell
• the second paths for DL data goes over X2-U interface towards RLC and
MAC of MeNB and directs these data towards physical layer of LTE cell MeNB SgNB

• For UL User data, based on configuration provided by SgNB, the UE terminal 4G 5G

takes the decision about the share of UL data sent over 5G and LTE air interface Dual Connectivity
C-Plane

• Split of the DL and UL data to be sent over two paths in Dual Connectivity NSA mode 3x U-Plane

operation is the scope of 5GC000570 5G-LTE flow control at X2 feature

Scope of this presentation

(Scheduling of user data over
5G air interface)

12 © Nokia 2018 Nokia Internal Use

Introduction
5G18A Carrier / Sector definitions Sector
• The set of cells on different carrier
frequencies using the same physical
Example with analog beamforming configuration: antennas and the same beam forming
• 2TRX RF HW, hardware.
One scheduler entity per sector.
• 4 Carrier Components (100 MHz BW)  4 Cells
Single scheduler can handle
multiple carriers

Cell = Component Carrier

Carrier Components = Cell • The cell has a single physical-layer cell identity
and a single global cell ID
CC1 CC2 CC3 CC4  100 MHz
• The cell is mapped to one component carrier
TRX1

Beam1
Sector • Each Cell belongs to a sector
Antenna
RF

Beam2
Beam
TRX2

CC1 CC2 CC3 CC4  100 MHz

• Single Entity of a directed Signal from Beamforming capable Antenna
Carrier Components = Cell • In Analog Beamforming Single Beam is Generated per antenna array for
each polarization, in Digital Beamforming the Antenna Array can be
split to smaller entities resulting in multiple Beams (Directed TRX
signals)

13 © Nokia 2018 Nokia Internal Use

 Above 6GHz (analog beamforming)
Introduction • Up to 8x100MHz cells per
sector
Scheduler in 5G • Up to 8 CC CA
• Up to 1 UE 2x2 MIMO is
• Packet scheduler is one of core functionalities in 5G scheduled per slot per cell
• Up to 8 UEs 2x2 MIMO is
• There are separate schedulers in each Sector scheduled per slot, each
• Single scheduler can handle multiple carriers user in separate cell
• 1 CA UE with 8CC can be
• The scheduler is responsible for allocation of radio resources on scheduled per slot
PDSCH, PUSCH, PDCCH and PUCCH for different 5G UEs
• Separate allocations in downlink and uplink

Multi User MIMO Single User MIMO

• Up to 2x100MHz cells per sector

Below 6GHz (digital beamforming)

• New set of decisions every data slot (slot duration depends on • Up to 1 UE 2x2 MIMO (DL) is
selected numerology) scheduled per slot per cell
• Up to 1 UE 4x4 MIMO (DL) is
• Handling transmission / reception of CSI-RS / CSI reports in scheduled per slot per cell
• 1 CA UE with 2CC can be
appropriate slots
scheduled per slot
• Handling of SRS reception
• Up to 1x100MHz cells per sector
• Handling of Scheduling Requests (SR) and HARQ process • 16 MIMO streams DL and UL MU-
• MIMO
Maximum number of UEs which can be scheduled in single slot
One beam

• Up to 8 UEs 2x2 MIMO is

per carrier/sector depends on Radio Access Point (RAP) scheduled per slot per cell
configuration (see on the left) • Up to 4 UEs 4x4 MIMO (DL) is
scheduled per slot per cell
14 © Nokia 2018 Nokia Internal Use
Agenda

1 2
Introduction Technical
Details
3
Configuration
Management
4
Performance
Management

15 © Nokia 2018 Nokia Internal Use

 Resource Element (RE)
Technical Details frequency Resource Block (RB)
Physical layer (multiple numerologies)

12 subcarriers
One of new 5G functionalities compared to LTE is support of multiple
numerologies – multiple subcarrier spacings
Subcarrier spacing (SCS) is based on common 15kHz base.
Subcarrier spacing: Δf = 2µ * 15kHz where µ defines the numerology.
Nokia in 5G18A supports following numerologies: time
14 OFDM symbols
- Frequencies below 6GHz:
1 slot (basic scheduling unit)
• µ = 1  Δf = 30kHz  1PRB = 360kHz
- Frequencies above 6GHz: 1 subframe (1ms) = 2 slots = 28 OFDM symbols
• µ = 3  Δf = 120kHz  1PRB = 1.44MHz (for PDSCH, PUSCH and PRACH) Δf = 30kHz
• µ = 4  Δf = 240kHz  1PRB = 2.88MHz (for PSS, SSS and PBCH – SS Blocks) 1 subframe (1ms) = 8 slots = 112 OFDM symbols

Δf = 120kHz
1 frame (10ms) = 10 subframes
1 subframe (1ms) = 16 slots = 224 OFDM symbols

Δf = 240kHz
16 © Nokia 2018 Nokia Internal Use
 Technical Details
Multiple numerologies – time and frequency domain PRB (14 x 12 REs) for
numerology µ = 1
freq.
The basic PRB structure is the 12 x
same – 12 subcarriers and 14 30kHz
OFDM symbols.

PRB (14 x 12 REs) for

The numerology defines the numerology µ = 3
frequency/time span of an
12 x
individual Resource Element, and 120kHz
in consequence, PRB.

2 Supported by Nokia
numerologies in 5G18A*

0ms 0.125ms 0.5ms 1ms time

*for SSB slots in freq. above 6GHz also numerology µ=4 is supported
1 subframe = 1ms
17 © Nokia 2018 Nokia Internal Use
Technical Details
Supported slot types

There are 4 slot types (containing user data) that are supported by the scheduler in 5G18A and there are also
specific downlink and uplink slot types for System Synchronization Blocks (SSB) and PRACH transmission

Symbol index
Slot Type
0 1 2 3 4 5 6 7 8 9 10 11 12 13

B1 Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd GP Uc
DL
B3 Dc Dd Dd Dd Dd Dd Dd Dd Dd Dd Dd C.RS GP Uc
UL
C2 Dc GP Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud Uc

C3 Dc GP Ud Ud Ud Ud Ud Ud Ud Ud Ud Ud SRS Uc
Dc DL control Ud UL data SRS Sounding Reference Signals

Dd DL data GP Guard period

Uc UL control C.RS Channel State Information reference signal (CSI-RS)

18 © Nokia 2018 Nokia Internal Use

Technical Details
Slot patterns (1/4)

Slots are composed into slot patterns. Slot patterns can have different length and structure
depending on:
Numerology UL/DL ratio SS burst set periodicity PRACH periodicity Number of beams

Scheduler calculates length of slot pattern according to following equation:

𝑆𝑙𝑜𝑡𝑃𝑎𝑡𝑡𝑒𝑟𝑛𝐿𝑒𝑛𝑔𝑡h =2𝜇 ∗max (max ( 𝑆𝑆 𝐵𝑝𝑒𝑟𝑖𝑜𝑑𝑖𝑐𝑖𝑡𝑦 , 𝑃𝑅𝐴𝐶 𝐻 𝑝𝑒𝑟𝑖𝑜𝑑𝑖𝑐𝑖𝑡𝑦 ) , 10)

Frequencies below 6 GHz Frequencies above 6 GHz

• µ=1 • µ=3
• SSB periodicity = 10ms (1 beam) or 20ms (>1 beam) • SSB periodicity = 10ms (1 beam) or 20ms (>1 beam)
• PRACH periodicity: 20ms (configuration 0)* • PRACH periodicity: 40ms (configuration 1)*

SlotPatternLength = 40 slots (20ms) SlotPatternLength = 320 slots (40ms)

19 © Nokia 2018 Nokia Internal Use

*PRACH configuration are based on Shadow spec. V6 – a subject to change
Technical Details
Slot patterns (2/4)

To assure proper scheduling of all data and control channels, slot pattern is created and used by scheduler based on cell
configuration.
Following slot types needs to be present within slot pattern:
- SSB slots (slot with Synchronization Signals / PBCH):
• Periodicity of SSB slots can ne set to 10ms (when only 1 beam is configured) or 20ms (when more than 1 beam is configured)
• With digital beamforming (f < 6GHz) different number of beams can be configured which occupy different number of slots, details in
below table: # of beams 1 2 4 6 8 2 beams can fit into 1
# of SSB slots 1 1 2 3 4 SSB slot

• With analog beamforming ( f > 6GHz) 1 or 32 beams can be configured which occupy 1 or 8 slots. For SSB slots in f > 6GHz, µ=4
numerology is used (240kHz SCS) to be able to squeeze 32 synchronization signals into number of slots
- PRACH slots: DL:UL ratio 9:1 8:2 7:3 5:5

• for f < 6GHz, PRACH configuration 0 should be used Slotindex mod 10

4 4, 8 0, 4, 8 0, 2, 4, 6, 8
with PUSCH
• For f > 6GHz, PRACH configuration 1 should be used
- Uplink and downlink data slots:
In slots presented in table are UL data
• There are 4 DL:UL ratios supported in both frequency ranges slots, rest of free slots (except SSB and
PRACH slots) are DL data slots
20 © Nokia 2018 Nokia Internal Use
Technical Details
Slot patterns (3/4)

Below are slot pattern examples for frequencies below 6GHz, 8 beams configured, PRACH config
0 and different DL:UL ratios:
SlotPatternLength = 40slots
Slot number 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

9:1 ratio

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

8:2 ratio

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

7:3 ratio

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

5:5 ratio

1 frame (10ms) 1 frame (10ms)

Downlink slot
Uplink slot

SSB slot
21 © Nokia 2018 Nokia Internal Use
PRACH slot
Technical Details
Slot patterns (4/4)

Below are slot pattern examples for frequencies above 6GHz, 32 beams configured (analog
beamforming on), PRACH config 1 and different DL:UL ratios:
SlotPatternLength = 320slots
9:1 ratio

8:2 ratio

7:3 ratio

5:5 ratio

1 frame (10ms) 1 frame (10ms) 1 frame (10ms) 1 frame (10ms)

Downlink slot
SSB slots for frequencies above 6 GHz
are using numerology µ = 4 (240kHz 2 slots with 240kHz SCS (each Uplink slot
Subcarrier spacing), to squeeze 32 SS containing 2 beams info.) can SSB slot
Blocks containing information about 32 fit into one 120kHz SCS slot,
therefore 32 beams can be send PRACH slot
beams into smaller number of 120kHz
SCS slots. within 8 120kHz slots (1ms)
22 © Nokia 2018 Nokia Internal Use
Technical Details
Overall UE scheduling process overview

All of presented steps are done in every slot containing user data (PDSCH or PUSCH)

Pre-scheduling: schedulability Which 5G UEs are qualified to be scheduled in upcoming slot

check of 5G UEs

Selection of beam which will be used for scheduling (only for

analog beamforming)
Time domain scheduling

Selection of 5G UEs which will be scheduled in given slot

Frequency domain scheduling

Selection of resources which will be allocated to selected 5G UEs

Besides those steps related to user scheduling there is also PDCCH and PUCCH scheduling performed.

23 © Nokia 2018 Nokia Internal Use

Technical Details
User scheduling overview
Digital beamforming Analog beamforming
1 1
Schedulability check. Green UEs are qualified to be scheduled. Schedulability check. Green UEs are qualified to be scheduled.

Beam
1 8

2 1
Time domain scheduling. All Green UEs are taken into account for Beam selection. One beam among all 32 analog beams is selected based
time domain scheduling, therefore can be selected to be scheduled on corresponding UEs metrics
in given slot
2
3
Time domain scheduling. Only green UEs from area of selected beam
Frequency domain scheduling. User with highest metric is selected are taken into account for time domain scheduling, therefore can be
to be scheduled (using all PRBs) in each carrier using beam which selected to be scheduled in given slot
is covering its location (different beams on different carriers can be 3 Frequency domain scheduling. User with highest metric is selected to be
used)
scheduled (using all PRBs) in each carrier using beam which was
previously selected (users on all carriers are scheduled with the same
24 © Nokia 2018 Nokia Internal Use
beam)
Technical Details
Traffic prioritization concept

Scheduling steps in both downlink and uplink are based on traffic

prioritization concept RACH msg2
The concept is based on following principles:

…
- UEs are grouped into resource request classes (depending on type of resources that has HARQ ret. DRB
to be scheduled) which are ordered according to their request class priority

…
- UEs in higher request classes are prioritized over UEs in lower request classes. Some
request classes like for example Rach msg2 need to have higher priority due to time
DRB traffic
constraints (RAR response window)
- UEs within the same request class are ordered according to different class sub-
priorities (sub-priorities depend on request class)
- Resource request classes can be component carrier specific or not component carrier
specific
- UE can be member of zero, one or more request classes per slot

25 © Nokia 2018 Nokia Internal Use

Technical Details
Traffic prioritization concept – request classes priorities

Downlink request classes Uplink request classes

Request Request
Request class Carrier specific Request class Carrier specific
class prio. class prio.
Component carrier Component carrier
RACH msg2 99 specific
RACH msg3 90 specific
Component carrier Component carrier
HARQ retransmission SRB3 92 specific
UL grant for Contention resolution 85 specific
Component carrier Component carrier
HARQ retransmission DRB 80 specific
HARQ retransmission for msg3 80 specific
DL MAC CE: TAC and Scell Not Component Component carrier
Activation/Deactivation 70 carrier specific
HARQ retransmission DRB 60 specific
Not Component Component carrier
SRB3 traffic 55 carrier specific
DRB traffic 30 specific
Component carrier Not Component
DRB traffic 40 specific
UL proactive scheduling 20 carrier specific

26 © Nokia 2018 Nokia Internal Use

Technical Details
Traffic prioritization concept – DL sub-priorities calculation

UEs within the same request class are ordered according to different class sub-priorities
Sub-priorities calculation depend on request class
DL Request class DL Sub-priority calculation
Sub-priorities based on time to the end of RAR response window and reported power of PRACH.
RACH msg2
, where x increases as UE approaches end of RAR window
HARQ retransmission SRB3 Sub-priorities are based on reached number of SRB3 retransmissions (higher prio. with more retransmissions performed)
HARQ retransmission DRB Sub-priorities are based on reached number of DRB retransmissions (higher prio. with more retransmissions performed)
DL MAC CE: TAC and SCell Sub-priorities are based on the time since the MAC CE transmission request was received by the scheduler: oldest MAC
Activation/Deactivation CE trigger received will be sent first
SRB3 traffic Sub-priorities are based on the time passed since SRB3 data arrived in the buffer. Older request will have higher priority
Sub-priorities are based on the proportional fair metric calculated for the UE which I based on immediate and past
DRB traffic
averaged throughput (more details on slide xx).

27 © Nokia 2018 Nokia Internal Use

Technical Details
Traffic prioritization concept – UL sub-priorities calculation

UL Request class UL Sub-priority calculation

There is no sub-priority here, Msg3 transmission is prioritized over all other request classes as the Msg3 transmission was
RACH msg3
already selected in a previous downlink TD scheduler step
UL Grant for contention Sub-priorities are based on the time passed since the UE was added to this class (more time spent in the class, higher the
resolution sub-priority)
HARQ retransmission for Sub-priorities are based on reached number of msg3 HARQ retransmissions (higher prio. with more retransmissions
msg3 performed)
HARQ retransmission DRB Sub-priorities are based on reached number of retransmissions (higher prio. with more retransmissions performed)
Sub-priorities are based on the proportional fair metric calculated for the UE which I based on immediate and past
DRB traffic
averaged throughput (more details on slide xx).
UL proactive scheduling Sub-priorities are based on the time passed since the last UL PUSCH scheduling for the UE on any carrier

In case sub-priorities of UEs are equal, those UEs will be ordered randomly.

28 © Nokia 2018 Nokia Internal Use

Technical Details
Pre-scheduling Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

All RRC_CONNECTED UEs are evaluated if they are eligible for scheduling. All UEs which can be scheduled are
added to so called Pre-scheduler Candidate Set.
The table below presents which conditions need to be fulfilled by UEs to be added to Pre-scheduler Candidate Set:

Downlink Uplink UE with pending RACH msg3 transmission

UE has data in the buffer UE has data in the buffer

UE has pending RACH msg2
UE has pending retransmission
UE has pending RACH msg3 transmission
or retransmission
UE has pending HARQ retransmission UE with no data
UE is eligible for PUSCH proactive UE with data in the buffer
scheduling
UE has successfully send Msg3 and an UL
UE eligible for scheduling (In
grant is needed for contention resolution Pre-scheduler Candidate Set)

If UE is out-of-sync it will not be added into Pre-scheduler Candidate Set UE not eligible for scheduling

29 © Nokia 2018 Nokia Internal Use

Technical Details
Pre-scheduling Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Time domain scheduling Frequency domain scheduling

From all UEs which are in Pre-scheduler Candidate Set, scheduler selects 50 UEs which will form Candidate Set 1 and will serve as an
input for time domain scheduling
Each UE from Pre-scheduler Candidate Set is assigned to one priority class (as defined in slide xx)
In case UE is candidate for several priority classes, it will be assigned to only one class with highest priority out of them
If current slot does not allow the transmission of Msg2, the UEs from that class are not put in the Candidate Set 1
Candidate Set 1 = max 50 UEs In case number of UEs in Pre-scheduler
Candidate Set is lower than 50, all of them can
be put into Candidate Set 1

…
priority

UEs with Pending UEs with HARQ UEs with DRB traffic
RACH msg2 retransmission

New UEs in each slot are added to the end of

the queue of respective priority class
30 © Nokia 2018
Technical Details
Beam selection Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

• For each UE in Candidate Set 1 the highest priority resource request is determined and its metric is calculated
according to request class priorities and sub-priorities. Therefore beam is selected based on needs of the most urgent
user
UEs (Candidate Set 1) UE0 UE1 UE2 UE3 UE4 UE5
HARQ
Highest request class rachMsg2 rachMsg2
retransmission
drbTraffic drbTraffic drbTraffic

Metric 99.20 99.12 80.45 40.3568 40.2594 40.3147

• If request class with highest metric is other than drbTraffic, the beam of UE with highest metric is
chosen, otherwise beam is selected according to procedure on next slides.
Highest metric is for UE0 which is in
area of beam 29, therefore this beam
is chosen
Beam
29

UE0
31 © Nokia 2018 Nokia Internal Use
Technical Details
Beam selection Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

• In case request class with highest metric among all UEs is drbTraffic, beam selection is done according to Proportional Fair
metrics calculated per UE and carrier as follows (this metric is also used for calculation of sub-priorities in drbTraffic request
class) :
  UE0 UE1 UE2 UE3 UE4 UE5
1. For each UE of Candidate Set 1 which belongs to drbTraffic request class and each
carrier0 478 733 282 888 634 954
carrier configured to a UE there is a Proportional Fair metric calculated which is
carrier1 647 72 152 88 386 813
based on
• immediate throughput (which can be achieved on carrier using 66 PRBs (100MHz carrier2 436 221 590 487 790 457
Bandwidth with 120KHz SCS), MCS from link adaptation and rank information) carrier3 340 363 197 985 675 878
• past averaged throughput (which was achieved by the UE including slots in which it carrier4 219 346 528 339 124 905
was not scheduled but present in Pre-scheduler Candidate Set):
carrier5 891 55 401 511 832 757
immediate _ throughput
PFmetric  carrier6 256 386 846 73 177 581
past _ averaged _ throughput carrier7 21 980 630 203 435 95
beam1 beam12 beam1 beam9 beam12 beam18

32 © Nokia 2018 Nokia Internal Use

Technical Details
Beam selection Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

2. For each beam and each carrier the maximum of the PF metrics from   UE0 UE1 UE2 UE3 UE4 UE5
previous step among all UEs assigned to the same beam is chosen: carrier0 478 733 282 888 634 954
carrier1 647 72 152 88 386 813
There are 2 UEs covered by beam 1 There is only one UE covered by carrier2 436 221 590 487 790 457
therefore for each carrier maximum beam18 therefore its metrics are carrier3 340 363 197 985 675 878
metric among those 2 UEs is chosen used in next step carrier4 219 346 528 339 124 905
for next step carrier5 891 55 401 511 832 757
carrier6 256 386 846 73 177 581
carrier7 21 980 630 203 435 95
beam1 beam12 beam1 beam9 beam12 beam18

…
  beam0 beam1 beam2 beam3 beam4 beam5 beam6 beam7 beam8 beam9 beam10 beam11 beam12 beam13 beam14 beam15 beam16 beam17 beam18 beam19 beam20 beam21 beam22 beam23 beam24 beam25 beam26 beam31
carrier0 0 478 0 0 0 0 0 0 0 888 0 0 733 0 0 0 0 0 954 0 0 0 0 0 0 0 0 0
carrier1 0 647 0 0 0 0 0 0 0 88 0 0 386 0 0 0 0 0 813 0 0 0 0 0 0 0 0 0
carrier2 0 590 0 0 0 0 0 0 0 487 0 0 790 0 0 0 0 0 457 0 0 0 0 0 0 0 0 0
carrier3 0 340 0 0 0 0 0 0 0 985 0 0 675 0 0 0 0 0 878 0 0 0 0 0 0 0 0 0
carrier4 0 528 0 0 0 0 0 0 0 339 0 0 346 0 0 0 0 0 905 0 0 0 0 0 0 0 0 0
carrier5 0 891 0 0 0 0 0 0 0 511 0 0 832 0 0 0 0 0 757 0 0 0 0 0 0 0 0 0
carrier6 0 846 0 0 0 0 0 0 0 73 0 0 386 0 0 0 0 0 581 0 0 0 0 0 0 0 0 0
carrier7 0 630 0 0 0 0 0 0 0 203 0 0 980 0 0 0 0 0 95 0 0 0 0 0 0 0 0 0

33 © Nokia 2018 Nokia Internal Use

Technical Details
Beam selection Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

3.
 
Single metric per beam is determined as the sum of PF metrics per carrier of each beam: …
beam0 beam1 beam2 beam3 beam4 beam5 beam6 beam7 beam8 beam9 beam10 beam11 beam12 beam13 beam14 beam15 beam16 beam17 beam18 beam19 beam20 beam21 beam22 beam23 beam24 beam25 beam26 beam31
carrier0 0 478 0 0 0 0 0 0 0 888 0 0 733 0 0 0 0 0 954 0 0 0 0 0 0 0 0 0
carrier1 0 647 0 0 0 0 0 0 0 88 0 0 386 0 0 0 0 0 813 0 0 0 0 0 0 0 0 0
carrier2 0 590 0 0 0 0 0 0 0 487 0 0 790 0 0 0 0 0 457 0 0 0 0 0 0 0 0 0
carrier3 0 340 0 0 0 0 0 0 0 985 0 0 675 0 0 0 0 0 878 0 0 0 0 0 0 0 0 0
carrier4 0 528 0 0 0 0 0 0 0 339 0 0 346 0 0 0 0 0 905 0 0 0 0 0 0 0 0 0
carrier5 0 891 0 0 0 0 0 0 0 511 0 0 832 0 0 0 0 0 757 0 0 0 0 0 0 0 0 0
carrier6 0 846 0 0 0 0 0 0 0 73 0 0 386 0 0 0 0 0 581 0 0 0 0 0 0 0 0 0
carrier7 0 630 0 0 0 0 0 0 0 203 0 0 980 0 0 0 0 0 95 0 0 0 0 0 0 0 0 0

∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑ ∑
  beam0 beam1 beam2 beam3 beam4 beam5 beam6 beam7 beam8 beam9 beam10 beam11 beam12 beam13 beam14 beam15 beam16 beam17 beam18 beam19 beam20 beam21 beam22 beam23 beam24 beam25 beam26 beam27
metric 0 4950 0 0 0 0 0 0 0 3574 0 0 5128 0 0 0 0 0 5440 0 0 0 0 0 0 0 0 0

4. Beam with maximum value of metric is chosen for scheduling

Beam
18

34 © Nokia 2018 Nokia Internal Use

Technical Details
Users selection Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

• Scheduler creates a list of UEs (so called Candidate Set 2 list) to be scheduled per carrier and sends it for frequency
domain scheduling
• Type of UEs from which Candidate Set 2 list is created depends on beamforming type:
Analog beamforming Digital beamforming
Only UEs assigned to selected beam are taken All UEs which are in Candidate Set 1 are
to the account taken into account

Beam
1 8

Only those users are taken

into account for CS2 list All UEs from Candidate Set 1
creation are taken into account for CS2
list creation
35 © Nokia 2018 Nokia Internal Use
Technical Details
Users selection Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

• Selection of users which will be assigned to carriers is done

in steps:
Carrier 1
1. Highest priority resource request (according to traffic
prioritization concept) among all considered UEs is Carrier 2
determined

FD Scheduling
2. UE with highest priority from this resource request is Carrier 3
selected and assigned to CS2 of corresponding carrier Carrier 4
3. All UEs which have primary cell on the same carrier as
allocated UE are removed from list of considered UEs. Carrier 5
4. All resource requests corresponding to carrier of
Carrier 6
allocated UE are removed from UEs (they will be no
longer considered for resource allocation on this carrier) Carrier 7
5. Procedure is repeated from step 1 until all carriers or UEs
are evaluated. Carrier 8

Candidate Set 2 list

36 © Nokia 2018 Nokia Internal Use
Technical Details
Frequency domain scheduling Time domain scheduling
Pre-scheduling Beam selection (analog beamforming) Users selection Frequency domain scheduling

> 6Ghz < 6Ghz

• As there can be only one UE scheduled per carrier Frequency domain
scheduling is a simple mechanism where UEs from CS2 list are selected
according to their priority (traffic prioritization concept)
• Whole carriers are allocated to single user
• Transport Block Size calculation for a UE is done based on following input
parameters (more details will be available in link adaptation materials):

66 PRBs
17RBGs
• MCS
Bandwidth size (PRBs) RBG size

273 PRBs
• Rank information

18RBGs
1-36 2
• Number of PRBs: 37-72 4
• Freq. below 6GHz: 273PRBs 73-144 8
• Freq. above 6GHz: 66PRBs 145-275 16

• In both downlink and uplink scheduler allocate resources with the granularity
of Resource Block Group (RBG). Size of RBG depends on number of PRBs
that considered bandwidth has

37 © Nokia 2018 Nokia Internal Use

 Technical Details PDCCH is located in first symbol of
all slots except PRACH slots. Only 1
PDCCH scheduling (DL DCI) UE can be scheduled within one PDCCH DL DCI PDCCH DL DCI
PDCCH symbol Format 1_1 content Format 1_0 content
Field name Field name
• Each PDSCH resource allocation on a certain carrier is provided Identifier for DCI format Identifier for DCI format
with separate DCI over the PDCCH of the same carrier (there is Bandwidth part indicator Frequency domain resource
one DL DCI per PDCCH symbol per carrier) Frequency domain resource assignment
assignment Time domain resource assigmnent
• PDSCH allocation is in the same slot as corresponding DL DCI Time domain resource assignment VRB to PRB mapping
(timing k0 = 0) Modulation and coding scheme
Modulation and coding scheme
• There are 2 possible DL DCI formats: New data indicator
New data indicator
Redundancy version
• DCI Format 1_0 – grant issues on common search space (used for Redundancy version
HARQ process number
RACH msg2) Downlink assignment index HARQ process number
• DCI Format 1_1 – grant issued on UE specific search space (used TPC command for scheduled Downlink assignment index
for DL transmission other than RACH msg2) PUCCH TPC command for scheduled
PUCCH resource indicator PUCCH
• If the DCI is sent at slot n, the corresponding UCI transmission on PUCCH resource indicator
PDSCH HARQ feedback timing
PUCCH carrying ACK/NACK feedback for PDSCH transmission Antenna port PDSCH HARQ feedback timing
related to this DCI should happen at slot n + k1 SRS request
• Transmission timing of PUCCH for UCI report (variable k1: DMRS sequence initialization

{0..15}) is set to smallest value higher or equal to k1min such that

subframe n + k1 is a data subframe with PUCCH resources that have
not been allocated to any UE Example for frequency <6GHz
• Freq. below 6GHz: k1min = 1*
• Freq. above 6GHz: k1min = 2*
k1 = 2 k1 = 4
Uplink slot Downlink slot SSB slot PRACH slot
38 © Nokia 2018 Nokia Internal Use
* Configurable via r&d parameter for non 3GPP compliant UEs. Airphone needs k1min = 2 for f. < 6GH and k1min = 4 for f. > 6GHz
 Technical Details PDCCH is located in first symbol of
all slots except PRACH slots. Only 1
PDCCH scheduling (UL DCI) UE can be scheduled within one PDCCH UL DCI PDCCH UL DCI
PDCCH symbol Format 0_1 content Format 0_0 content
Field name Field name
• There can be only one UL DCI allocated per carrier in given slot. Identifier for DCI format Identifier for DCI format
Resource allocation for configured carrier is provided using DCI on the Bandwidth part indicator Frequency domain resource
same carrier Frequency domain resource assignment
• There are 2 possible UL DCI formats: assignment Time domain resource assigmnent
• DCI Format 0_0 – grant issues on common search space (used for Time domain resource assignment Frequency hopping flag
Modulation and coding scheme
RACH msg3 HARQ retransmission granted by TC-RNTI) New data indicator
Modulation and coding scheme
• DCI Format 0_1 – grant issued on UE specific search space (used for Redundancy version
New data indicator
other UL transmissions) HARQ process number Redundancy version
1st downlink assignment index HARQ process number
• Transmission timings of PUSCH (variable k2: {2, 4, 6, 8, 10}) for SRS resource indicator Downlink assignment index
corresponding UL DCIs are calculated at the cell setup. This calculation Precoding information and number TPC command for scheduled
of layers PUSCH
takes into account selected UL/DL ratio and all control related slots
Antenna port
which are inserted between UL and DL data slots SRS request
• Minimum values of such timing (k2) is presented below: PTRS-DMRS
DMRS sequence initialization
UL:DL data slot ratio Freq. below 6GHz Freq. above 6GHz Example:
1:9 10 10 • frequency <6GHz
2:8 4 4 • UL:DL = 2:8
3:7 2 4
5:5 2 4
k2 = 4 k2 = 6 k2 = 4
Uplink slot Downlink slot SSB slot PRACH slot
39 © Nokia 2018 Nokia Internal Use
Technical Details
PUCCH scheduling

PUCCH is located in the 14th symbol of all slots except PRACH slots. One UE can use one PUCCH symbol
Each DL transmission has corresponding UCI transmission on PUCCH carrying ACK/NACK feedback. Timing
of this feedback (k2) is described on previous slide
In case of Carrier aggregation PUCCH is send only over primary cell therefore HARQ feedback for secondary
cells is sent using Joint-UCI (for UEs configured with CA only Format 2 is supported)
Supported PUCCH formats:
- PUCCH short format 0: transmission is over 1 symbol and number of UCI bits is 1 or 2. It can be used for:
• HARQ ACK/NACK and SR detection
• SR only detection
- PUCCH short format 2: transmission is over 1 symbol (over 1 to 16 PRBs) and number of UCI bits is in range [3..50]. It can be
used for: HARQ ACK/NACK, SR detection and CSI reports
PUCCH format is chosen depending on number of bits needed for UCI, if number of bits is less of equal to 2
PUCCH format 0 will be chosen, otherwise PUCCH format 2 will be chosen

40 © Nokia 2018 Nokia Internal Use

Technical Details
HARQ handling

DL HARQ Scheduling of retransmission

New transmission (Tx) or Retransmission (ReTx) need is signaled by UEs over PUCCH by ACK
(transmission was successful) or NACK, if last transmission failed and retransmission is needed.
Timing for HARQ feedback is defined by variable k1 (details shown on slide 36)
k1=2
• The same TBS and Rank is used as for initial transmission
• The same HARQ process is used as for initial transmission
• NDI value of that HARQ process is not toggled
• The same number of PDSCH symbols is used as for the
initial transmission. If there are less PDSCH symbols
available in a slot a retransmission is blocked

Tx ACK/NACK Tx/ReTx
In case of NACK or DTX
UL HARQ If the maximum number of HARQ retransmissions has
been reached:
New transmission (Tx) or Retransmission (ReTx) need is signaled on PDCCH [DCI: New Data • Retransmission scheduling of related TB is stopped
Indicator (NDI)  0 or 1]. If the value is the same as the previously transmitted one, UL
• HARQ process is freed
retransmission is expected. In turn, toggled value indicates new transmission request. Timing for
PUSCH transmission is defined by variable k2 (details shown on slide 37) Otherwise:
k2=4 k2=10 • Scheduler will consider UE as a candidate to retransmission
in the same carrier

In case of ACK
UL Grant Tx Tx UL Grant Tx/ReTx Tx/ReTx HARQ process can be freed

Uplink slot Downlink slot SSB slot PRACH slot

41 © Nokia 2018 Nokia Internal Use

Technical Details
CSI framework

CSI-RS (Channel State Information Reference Signals) can be divided into following categories:

CSI-RS for channel measurements

• Used to get information like Rank Indicator
CSI-RS for beam management
(RI), PMI and CQI
• Used to send RSRP information of all refined
• Each CSI-RS transmission is associated with
beams
CSI reports from UEs
• Sent periodically on SSB slots
• Configured for each UE separately
• Configured for multiple UEs
• Divided into periodic and aperiodic
• Supported only in frequencies below 6 GHz
• Can be send in SSB slots and in DL data slots
• Associated CSI reports sent on PUCCH
(periodic) or PUSCH (aperiodic) channel

42 © Nokia 2018 Nokia Internal Use

Technical Details
CSI-RS for channel measurements (periodic CSI-RS)

Periodic CSI-RS transmission and CSI report reception is started for each UE after successfully finished
random access procedure
Resources allocated for CSI-RS are placed in free symbols of SSB slots (up to 3 CSI-RS per slot) or in 11th
symbol of DL data (B3) slots
Even SSB slot Odd SSB slot B3 DL data slot
0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13 0 1 2 3 4 5 6 7 8 9 10 11 12 13

C C C C C C C
P P PP P P PP P P P P
S S S P P S P P S S S
D D DD D D DD DDD U
I I I P BS P S
B I P B S P S
B I I I G
C S SS S S SS S S S C
- - - S CS S S
C - S C S S S
C - - - P
C C CCC C CC CCC C
R R R S HS S S
H R S H S S S
H R R R
H H HH H H HH HHH H
S S S S S S S

To avoid throughput degradation first of all resources from SSB slots are used, only when they are exhausted
CSI-RS are sent also in DL data slots

43 © Nokia 2018 Nokia Internal Use

 Technical Details
CSI-RS for channel measurements (periodic CSI reports)

Periodicity of CSI reports depends on number of RRC connected UEs in the cell and possible values are: 5, 10, 20,
40, 80, 160 and 320 slots. With CSI reports periodicity maximum number of RRC connected UEs in the cell can
be determined.
CSI reports are sent on PUCCH channel. PUCCH resources to be used for CSI reports are determined after
reserving those to be used for HARQ feedback. <6GHz example with 8
beams configured
k1 = 2 k1 = 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

Slot pattern length = 40slots (20ms)

With 320 slots periodicity there can fit 8 Slot
1 pattern length. Within one Slot pattern
PUCCH resources needed 2 length there could be 10 PUCCH resources
for HARQ feedback (marked PUCCH symbols which are free after HARQ
used for CSI reports, which gives 80 CSI
in orange color) are reservation can be used for CSI reports
reports within 320 slots periodicity.
determined (marked in red color). Additionally CSI reports
Therefore maximum 80 connected UEs can
can be sent also in SSB slots
be present in the cell

Uplink slot Downlink slot SSB slot PRACH slot

44 © Nokia 2018 Nokia Internal Use
Technical Details
CSI-RS for channel measurements (aperiodic CSI reports)

In some cases reporting periodicity of CSI reports is forced to be high (large number of UEs in the cell) and saved reports can get
old and do not reflect channel state anymore
In order to have up-to-date reports, aperiodic CSI reporting on PUSCH is triggered for already scheduled UEs
Conditions that need to be fulfilled to trigger aperiodic CSI report for a UE:
-
Time needed by the UE to
UE is scheduled for a PUSCH transmission in slot n + k2
generate CSI report
- Age of last CSI report for this UE is greater than CsiAgeThreshold
- DL slot with offset in range 0..4 is available with free 11th symbol such that: k2-offset > UeCsiComputationTime (in case of more that one slot is
available, slot with smallest offset should be chosen)
k2 = 6

UeCsiComputationTime

UL
… UL DL DL DL UL DL DL DL DL DL + DL …
slot n CSI rep.
slot n+k2
Symbol reserved for
offset = 2 k2 – offset > UeCsiComputationTime
periodic CSI-RS for
different UE Aperiodic CSI-RS can be
45 © Nokia 2018 Nokia Internal Use
scheduled here
Technical Details
CSI-RS for beam management

In case of beam refinement (available only on freq. < 6GHz), CSI-RS for beam management are needed for each refined beam
Those CSI-RS are placed in SS slots with corresponding synchronization beam
CSI-RS for beam management are scheduled for all UEs served by the corresponding synchronization beam

… …

Placement of CSI-RS for beam

0 1 2 3 4 5 6 7 8 9 10 11 12 13
management is controlled via

frequency
csirsBmMgmtSubband
CSI-RS
parameter. So far setting of this
parameter is limited to value
P P aboveSSPBCHBlock. This means
Refined beam 1 P S P S
B B that CSI-RS for beam
Synchronization beam 1 S S S S management are placed above
Refined beam 2 C C
S S S S PSS/SSS/PBCH symbols related
H H
Synchronization beam 2 Refined beam 3 to corresponding synchronization
beams
Refined beam 4
46 © Nokia 2018 Nokia Internal Use time
More info about CSI-RS for beam refinement are in 5G Beamforming presentation under following link
Technical Details
SRS scheduling

Sounding Reference Signals are placed in 12th symbol of C3 type UL data slot
C3 UL data slot
PDCCH GP PUSCH PUSCH PUSCH PUSCH PUSCH PUSCH PUSCH PUSCH PUSCH PUSCH SRS PUCCH

SRS transmission request is done by UL scheduler per each carrier

SRS transmission is requested when:
- UE selected for scheduling on given carrier is using rank 1 transmission
- Current slot timing k2 == srsSlotOffset parameter

Setting of srsSlotOffset parameter depend on selected UL:DL ratio.

UL:DL Slots when SRS transmission can be Example:
srsSlotOffset setting requested. Actual SRS transmission • frequency <6GHz
ratio
will take place after k2 slots • UL:DL = 2:8
1:9 10
2:8 4 C3 C2 C3

3:7 4 (f < 6GHz), 6 (f > 6GHz)

k2 = 4 k2 = 6 k2 = 4
5:5 2 (f < 6GHz), 4 (f > 6GHz) Uplink slot Downlink slot SSB slot PRACH slot
48 © Nokia 2018 Nokia Internal Use
 Technical Details
Proactive UL Resource Assignment

• There is a possibility to enable additional functionality in uplink scheduler called Proactive UL Resource
Assignment. It can be activated using actProactUlScheduling parameter.
• This functionality puts UEs into Candidate Set 1 and periodically schedules dummy grants for them, even
if they don’t have any data to send. This will allow to achieve very low ping response times.
• Functionality is based on timer controlled by ulSchedTimeInterval parameter (default: 4ms), which are started
after user setup completion and restarted when UE is granted for initial transmission

Proactive UL resource assignment can be

used for demo purposes to show very low
Restart of timers ping response times

ulSchedTimeInterval
UL transmission

time
Dummy grant
(60bytes) UE
UEadded
addedtotoCandidate
CandidateSet
Set1as a member
1 as ofof
a member
UL ulProactSched
proactive scheduling
requestrequest
class class
49 © Nokia 2018 Nokia Internal Use
Agenda

1 2
Introduction Technical
Details
3
Configuration
Management
4
Performance
Management

50 © Nokia 2018 Nokia Internal Use

Configuration Management
Definition of terms and rules for parameter classification*
The ‘Basic Parameters’ category contains primary
parameters which should be considered during cell
deployment and must be adjusted to a particular
scenario:
• Network Element (NE) identifiers
• Planning parameters, e.g. neighbour definitions, frequency, scrambling
codes, PCI, RA preambles
• Parameters that are the outcome from dimensioning, i.e. basic
parameters defining amount of resources
• Basic parameters activating basic functionalities, e.g. power control,
admission control, handovers
• Parameters defining operators’ strategy, e.g. traffic steering, thresholds
for power control, handovers, cell reselections, basic parameters defining
feature behaviour
The ‘Advanced Parameters’ category contains the
parameters for network optimisation and fine tuning:
• Decent network performance should be achieved without tuning these
parameters
• Universal defaults ensuring decent network performance need to be
defined for all parameters of this category. If this is not possible for a
given parameter it must be put to the ‘Basic Parameters’ category
• Parameters requiring detailed system knowledge and broad experience
unless rules for the ‘Basic Parameters’ category are violated
• All parameters (even without defaults, e.g. optional structures) related
to advanced and very complex features

The ‘Obsolete parameters’ category is intended for parameters that are candidates to be removed from the
product in a future release: * - purpose: Categories of parameters have been defined to simplify network
• Parameters always used with default value parametrization. Parameterization effort shall be focused mainly on Basic ones.
• Parameters that are not used by operators Categorization is reflected in a ‘view’ definition in NetAct CM Editor.
• Parameters that are not relevant anymore

51 © Nokia 2018 Nokia Internal Use

Configuration Management
New parameters
Abbreviated name Full name Description Range and step Default
NRBTS:ulDlDataSlotRatio UL to DL logical data slot This parameter defines the ratio of the UL / DL 1:1/9; 2:2/8; 3:3/7; 4:5/5 2 (2/8 split)
ratio logical data slots used in the dynamic slot selection
algorithm by the 5G-L2-PS

NRCELLGRP:actProactUl Activate UL proactive This parameter activates/deactivates the UL

Scheduling scheduling proactive scheduling 1:True; 0:false 0 (false)

NRCELLGRP:ulSchedTim UL scheduling time This parameter indicates the targeted time interval
eInterval interval for proactive UL resource assignment for each 0.2...1000, step 0.2 [ms] 4
connected user.

NRCELLGRP: Number of transmitted This parameter defines the number of transmitted 1:1 beam;2:2 beams; 4:4 beams; 6:6 1
numberOfTransmittedSsBl Synchronization Signal Synchronization Signal Blocks. beams; 8:8 beams; 9:9 beams; 12:12
ocks Blocks beams; 15:15 beams; 18:18 beams;
21:21 beams; 24:24 beams; 32:32
beams

NRCELLGRP:ssBurstSetP SS Burst Set Period This parameter indicates the synchronization signal 10...20, step 10 [ms] 10
eriod burst set transmission period

52 © Nokia 2018 Customer Confidential

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRCELL:csirsBeamMgmt CSI-RS for Beam CSI-RS configuration for Beam Management
- -
Management structure
NRCELL:csirsBeamMgmt: CSI-RS BmMgmt Density This parameter defines the density of CSI-RS 3 (3RE per
1:density1; 3:density3
csirsBmMgmtDensity allocation for L1 RSRP Measurement PRB)
NRCELL:csirsBeamMgmt: CSI-RS BmMgmt RE Index This parameter defines the first RE to be allocated 0..11, step 1 0 (lowest
csirsBmMgmtReIndex for CSI-RS for L1-RSRP. Different RE allocation RE in PRB)
can mitigate intercell interference of these signals.
NRCELL:csirsBeamMgmt:csi CSI-RS BmMgmt subband This parameter defines whether the subband below or 2:aboveSSPBCHBlock 2
rsBmMgmtSubband above the SS/PBCH block allocation shall be used for
transmission of CSI-RS for L1 RSRP measurement.

53 © Nokia 2018 Customer Confidential

Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRCELLGRP:belowAbov Below or Above 6GHz flag This parameter indicates whether the cell is 0:below6Ghz; 0
e6GhzFlag configured for below6GHz or above 6GHz (below6GH
1:above6GHz
z)
NRCELLGRP:scs SCS This parameter indicates the subcarrier spacing 30:30 KHz;
30
value 120:120 KHz
NRCELLGRP:dlBandwidt DL Bandwidth This parameter defines the maximum number of 5:32 PRBs; 8
h downlink resource blocks associated to a given 6:64 PRBs;
bandwidth and subcarrier spacing configuration. 7:128 PRBs;
The current assumption for spectrum below 8:256 PRBs
6GHz: - the bandwidth value is set to 100MHz -
the subcarrier spacing is equal to 30KHz. The
current assumption for spectrum above 6GHz:-
The bandwidth value is set to 50MHz or 100
MHz- The subcarrier spacing is equal to 120 KHz

54 © Nokia 2018 Customer Confidential

 Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRBTS:prioDlDrbTraffic DL TD scheduler priority for Priority of the resource request class used in the DL TD
Hidde
n DRB first transmissions scheduler for DL first transmissions of DRB in the beam 1...99, step 1 40
selection and UE selection algorithm
NRBTS:prioDlHarqRetrans DL TD scheduler priority for Priority of the resource request class used in the DL TD
Hidde
n scheduler for DL HARQ retransmissions of DRB in the beam 1...99, step 1 80
Drb HARQ DRB retransmissions
selection and UE selection algorithm
NRBTS:prioDlMacCe DL TD scheduler priority for Priority of the resource request class used in the DL TD 1...99, step 1 70
Hidde scheduler for MAC CE transmission in the beam selection
n any MAC CE transmission
and UE selection algorithm
NRBTS:prioDlRachMsg2 DL TD scheduler priority for Priority of the resource request class used in the DL TD 1...99, step 1 99
RACH Msg2 scheduler for DL RACH Msg2 transmission in the beam
Hidde
n selection and UE selection algorithm

55 © Nokia 2018 Customer Confidential

 Configuration Management
New parameters

Abbreviated name Full name Description Range and step Default

NRBTS:prioUlContentRes Priority of the resource request class used in UL TD scheduler 1...99, step 1 85
UL TD scheduler priority for UL for UL grants for contention resolution, i.e., first UL grant
Hidde Grant
n grant for contention resolution after Msg3 reception in NSA mode, in the beam selection and
UE selection algorithm
NRBTS:prioUlDrbTraffic Priority of the resource request class used in the UL TD 1...99, step 1 30
UL TD scheduler priority for DRB
Hidde scheduler for UL first transmissions of DRB only in the beam
n only first transmissions
selection and UE selection algorithm
NRBTS:prioUlHarqRetrans Priority of the resource request class used in the UL TD 1...99, step 1 60
UL TD scheduler priority for HARQ
Hidde scheduler for DL HARQ retransmissions of pure DRB in the
n Drb DRB retransmission
beam selection and UE selection algorithm
NRBTS:prioUlHarqRetrans Priority of the resource request class used in the UL TD 1...99, step 1 80
UL TD scheduler priority for HARQ
scheduler for UL HARQ retransmissions of Msg3 in the beam
Hidde Rach RACH retransmissions (Msg3)
n selection and UE selection algorithm
NRBTS:prioUlProactSched Priority of the resource request class used in the UL TD 1...99, step 1 20
UL TD scheduler priority for UL
scheduler for UL proactive scheduling in the beam selection
proactive scheduling
Hidde and UE selection algorithm
n
NRBTS:prioUlRachMsg3 Priority of the resource request class used in the UL TD 1...99, step 1 90
UL TD scheduler priority for RACH
scheduler for UL HARQ first transmissions of Msg3 in the
first transmissions (Msg3)
Hidde
n beam selection and UE selection algorithm

56 © Nokia 2018 Customer Confidential

Agenda

1 2
Introduction Technical
Details
3
Configuration
Management
4
Performance
Management

57 © Nokia 2018 Nokia Internal Use

Performance Management Detailed counter information
can be found in following excel
New counters file:
Microsoft Excel
Worksheet
Following counters are introduced with these features:
Counter ID Counter name
M55303C07001…
Received UE related RSSI for PUSCH Level xx
M55303C07044
M55303C08001…
M55303C08022 Received UE related SINR for PUCCH Level xx

M55303C09001…
Received UE related RSSI for PUCCH Level xx
M55303C09044
M55303C10001…
Received UE related Signal Power for PUSCH Level xx
M55303C10044
M55303C11001 PUCCH Format0 DTX detections
M55303C12001 PUCCH Format0 non-DTX detections
M55303C15001 PUCCH Format2 DTX detections
M55303C16001 PUCCH Format2 non-DTX detections

58 © Nokia 2018 Nokia Internal Use

Performance Management
New counters

Following counters are introduced with these features:

Counter ID Counter name
M55307C02001… Timing Advance sent to RRC connected UE - BIN xx
M55307C02032
M55308C00000 DL Data slots
M55308C00001 UL Data slots
M55308C00002 SS Burst slots
M55308C00003 Random Access Channel slot
M55308C00004 Data slot with PDSCH
M55308C00005 Data slot with PUSCH
M55316C01000 Sample count for DL UE amount counters
M55316C01001 Sample count for UL UE amount counters

59 © Nokia 2018 Nokia Internal Use

Performance Management
New counters

Following counters are introduced with these features:

Counter ID Counter name
M55308C01000 Sample count for NR Cell Utilization DL counters
M55308C01001 Sample count for NR Cell Utilization UL counters
M55308C02000 Accumulated number of UEs with DL DRB data buffered
M55308C02001 Maximum number of UEs with DL DRB data buffered
M55308C02002 Accumulated number of UEs with UL DRB data buffered
M55308C02003 Maximum number of UEs with UL DRB data buffered
M55308C03001 PDSCH OFDM symbols
M55308C03002 PDCCH OFDM symbols
M55308C03003 PUSCH OFDM symbols
M55308C03004 PUCCH OFDM symbols

60 © Nokia 2018 Nokia Internal Use