5G19 PERFORMANCES OPTIMISATION GUIDELINES
GS/CS/RSD QoE
Editor : Priscille Cochois
Contributors : Priscille Cochois, Soukaina El Moussi, Stanislav Dulovic, Nicolas Palumbo, Jose Gomes,
Pierre Richard, Eliza Wong, Florent Crespel, Dominique Chauvière, Raja Hasni
Ed 1.0
Acknowledgement to NetEng WebNEI authors for their slides partly reused in this package
1
© Nokia 2019
Nokia internal use
Revision history and Metadata
Document location : here
Organization: GS/CS
2
Version
Description of Changes
Date
Doc Owner
Doc Status
0.1
Initial version based on 5G19 Parameters &
KPI for trials document, version 0.5
05-09-2019
Priscille Cochois
draft
0.2
Draft version for internal QoE review
14-10-2019
Priscille Cochois
draft
1.0
Version after internal review
24-10-2019
Priscille Cochois
preliminary
© Nokia 2019
Nokia internal use
Reviewed
by
GS CS RSD
NPS 1/2/3
Approver
Approval Date
3
Scope
Accessibility/Ret
ainability
Mobility
4G-5G
interactions
Usage :
Throughput
Design Specific
Parameters
© Nokia 2019
Nokia internal use
Usage : Packet
Delay
Scope
The purpose of this document is :
• To identify the main NSA 5G19 mmW & cmW (Cloud & Classical configuration) parameters per
Performance Domains and Sub-domains, in particular :
•
•
•
•
•
Accessibility/Retainability
Usage (Throughput, Packet Delay)
Mobility
4G-5G interactions
Design specific parameters
• To give a brief technical description of the parameters and their associated features/procedures.
Special thanks to NetEng colleagues for WebNEI slides that were partly reused for these descriptions.
• To provide generic recommendations on the way to optimize these parameters and their impact on
performances
• To collect feedback from 5G trials/NPI projects, on parameters changes, optimisations, and liaise
with NetEng MIND & NIDD in case default values or recommendations should be modified
Repository : Sharepoint QoE AEF > Project Libraries > 5G > 5G Deliverables > 5G Performance
Optimisation Guidelines
4
© Nokia 2019
Nokia internal use
Positioning of document within 5G community
GS/NPO
5G Parameters Guidelines
GS/NPO CO
Networks Deployment
MN/5G/T&P
Trials Activities
GS/CS
NPI Projects
Consistency Alignment
Parameters classification per KPI domain
GS/CS/RSD
5G Performance Optimisation
Guidelines
Feedback on
parameters changes
and KPI impacts
5
Recos per profile
Proposals for new parameters
recommendations or default
values
PAKS tool & models
PAKS usage in projects
to analyse KPIs and
related parameters
GS/CS/NetEng
MIND
Export of parameters
models, recos, KPI domain
(not yet available)
MN/5G/A&S
NIDD
Default settings
GMC Templates
Prontos to change default values
for parameters
Change recos in GMC templates
GS/CS/NetEng
GRASP
Features Gains
© Nokia 2019
Nokia internal use
Parameters Management
References
References on parameters knowledge are described in MIND database
This document identifies important parameters for optimisation, and their impact on performance, but
makes link to MIND for any official description/recommendation
Parameters are classified by performance domain/sub-domain as defined in MIND
6
© Nokia 2019
Nokia internal use
Parameters Management
Recommendations
Many parameters have a default value defined in NIDD which is set at creation. This is usually also the recommended
value, so that there is no need for change at site/cell creation
However, in some cases, either the default value is not defined or not (yet) equal to the recommended value, or several
recommended values need to be defined, depending on environment/scenario
These specific recommendations are described in the « deployment know-how » within MIND (see example below)
This document provides such type of recommendation and indicates them in the parameters tables when appropriate
MRBTS.NRBTS.drbRlcAmDefProf.dlMaxRetxThreshold
7
© Nokia 2019
Nokia internal use
Parameters Management
Parameters tables
Parameters tables are defined for each domain as follows :
Domain
Usage
Sub-domain
Packet Delay
Parameter Name
CSI Reporting Periodicity
Performance domain/sub-domain
as defined in MIND
Useful to filter parameters per KPI domain
Abbreviation
csiReportPeriodicity
Parameter name and
position in object
model
MIND Reference
MRBTS.NRBTS.NRCELLGRP.csiReportPeriodicity
Link to MIND where to
find description, range,
and all detailed info
on parameter
Default value reco if not list of use cases in MIND
(GUI)
same as
default
slots320
slots40 High Throughput : slots80
slots80 Low latency : slots40
slots320 High Traffic Load : slots320
Default value as
defined in MIND
Indicates whether reco
is in line with default
Reco per profile/use
are also indicated
when applicable
Please refer to MIND
for latest reco
Initial use cases for optimisation : GMC 5G19, High Throughput, Low Latency, High Traffic Load
8
© Nokia 2019
Nokia internal use
5G KPIs process
KPIs are in defined in 2 NOKIA databases
NIDD database: (here)
- Contains all BM (BenchMark) KPIs.
- Defined with reference ID format:
- NR_5XYZv (X, Y, Z = 0 to 9; v = version a or b or c…)
- The customers can follow the benchmark specification documents and create the KPIs in NetAct by themselves.
JUMP database: (here)
- Contains all KPIs defined for 5G.
- NIDD database is synchronized with JUMP database and so the BM KPIs are also visible in JUMP database.
- Remark: for a KPI already defined in JUMP database, if it is decided to tag it as BM KPI:
- A new BM KPI (equal to this KPI) is created with BM KPI reference ID format.
- The JUMP ID version is no longer updated and has an indication that the BM KPI ID must be used.
- Warning on filter because we have JUMP reference ID NR_5a, NR_50a to NR_59a.
NetAct:
- Several KPIs are used by PM (Performance Monitoring) reports  System Reports.
- Nearly all JUMP KPIs (most recent version) are included in the Reporting Suites package (some KPIs are created for
specific purposes and not suitable for generic customers).
- The Reporting Suites package (PM reports + KPIs) must be purchased by the client to have it installed on NetAct.
This document is using KPI definitions extracted from NIDD/JUMP, within an 5G19_KPIs&Counters_ed01 file
located here. Please refer to it for any detail on KPI description, formulas and counters
9
© Nokia 2019
Nokia internal use
10
Scope
Accessibility/Ret
ainability
Mobility
4G-5G
interactions
Usage :
Throughput
Design Specific
Parameters
© Nokia 2019
Nokia internal use
Usage : Packet
Delay
Accessibility
Synchronization Signals & System Information Broadcast
PSS
SSS
PSS, SSS and PBCH
(carrying MIB) are time
and frequency
multiplexed
SS Block
PSS
PBCH
SSS
PBCH
SS Burst Set
PBCH
PBCH
SS block burst set is repeated
periodically using :
SS Burst
Below
6GHz
2x
PSS
Above
6GHz
4x
PSS
PBCH
PBCH
NRCELLGRP:ssBurstSetPeriod
SSS
PBCH
SSS
PBCH
PBCH
PBCH
SS Blocks form SS Burst that is a
set of consecutive SS blocks
That set compose SS
Block in four consecutive
OFDM symbols
8 x*
PSS
PBCH
64 x*
PSS
PBCH
3 to
6GHz
Above
6GHz
SSS
PBCH
SSS
PBCH
PBCH
PBCH
SS Bursts compose SS Burst set
used for multi beam sweeping
*NRCELLGRP:numberOfTransmittedSsBlocks* parameter
*1 beam
Relationship with number of transmitted SS blocks:
‒ If NRCELLGRP:numberOfTransmittedSsBlocks is not equal to 1 (corresponding to 1 beam), then NRCELLGRP:ssBurstSetPeriod
11 © Nokia 2019
parameter must be equal to 20, 40, 80 or 160 ms, else this parameter must be equal to 10, 20, 40, 80 or 160ms
Nokia internal use
NRCELLGRP:numberOfTransmittedSsBlocks is directly
linked to the number of beams configured using
NRCELL:beamSet:basicBeamSet.
NRCELLGRP:numberOfTransmittedSsBlocks must be equal
to the sum of all the values in the selected
NRCELL.beamSet.basicBeamSet.
Accessibility
Number of SSB and BEAMS
NRCELLGRP:
numberOfTransmittedSsBlocks
Value
1
2
4
6
8
9
12
15
18
21
24
32
12
Name
1 beam
2 beams
4 beams
6 beams
8 beams
9 beams
12 beams
15 beams
18 beams
21 beams
24 beams
32 beams
NRCELL:beamSet:basicBeamSet
default
Recommended (cmW)
Value
1
2
3
4
5
6
7
8
9
16
100
101
102
103
Name
beamSet_1
beamSet_2
beamSet_4
beamSet_8
beamSet_4_4
beamSet_5_3
beamSet_6_2
beamSet_3_3_2
beamSet_2_2_2_2
beamSet_6
beamSetAbf_1A
beamSetAbf_32A
beamSetAbf_32B
beamSetAbf_32C
© Nokia 2019
Nokia internal use
# of beams
1
2
3
8
8
8
8
8
8
6
1
32
32
32
Accessibility
Position of SS/PBCH
NRCELL:gscn (Global Synchronization Channel Number)
defines the frequency position of the SS Block.
NRCELL:gscn
Value
0
1
2
[3-26639]
Name
bottom of the carrier bandwidth
middle of the carrier bandwidth
top of the carrier bandwidth
See 3GPP 38.104
gscn must be selected to ensure subcarrier alignment
between SS/PBCH and the channel (NR-ARFCN)
default
recommended
By default, the parameter is set to “1” i.e. gscn is
placed in the middle of the channel. However, it is
recommended to determine gscn value explicitely,
using NR Frequencies Tool:
http://5gtables.eecloud.dynamic.nsnnet.net/NRFreq.php
13
Note : for system “above 6GHz” ARFCNs need to fulfil a L1
SW design restriction.
The SW design restriction limits the value to ones that fulfil
(NRARFCN-2016667) mod 4 = 0
With this condition fulfilled, the PRACH success rate greatly
improved.
© Nokia 2019
Nokia internal use
Accessibility
RACH – MSG1 – Preamble Format
•
•
•
3gpp 38.211
Table 6.3.3.1-1: PRACH preamble formats for 𝐿𝑅𝐴 = 839 and Δ𝑓 𝑅𝐴 𝜖 1.25,5 𝑘𝐻𝑧
Two preamble formats are defined by 3GPP:
•
Short → Sequence length LRA = 139
•
Long → Sequence length LRA = 839
LRA
0
1
2
3
839
839
839
839
Supported
Nokia 5G19 release supports:
•
A2 format
•
B4 format
•
Format 0
Preamble format determines duration of
cyclic prefix and sequence (thus cell range)
Supported
Nu – preamble sequence length
𝛥𝑓 𝑅𝐴 - Subcarrier spacing
Supported
𝑅𝐴
𝑁𝐶𝑃
− 𝑐𝑦𝑐𝑙𝑖𝑐 𝑝𝑟𝑒𝑓𝑖𝑥 𝑙𝑒𝑛𝑔𝑡ℎ
14
Format
Nu
Δ𝑓 𝑅𝐴
1.25 kHz
5 kHz
24576𝜅
2 ∙ 24576𝜅
4 ∙ 24576𝜅
4 ∙ 6144𝜅
𝑅𝐴
𝑁𝐶𝑃
3168𝜅
21024𝜅
4688𝜅
3168𝜅
Support for
restricted sets
Type A, Type B
Type A, Type B
Type A, Type B
Type A, Type B
3gpp 38.211
Table 6.3.3.1-2: PRACH preamble formats for 𝐿𝑅𝐴 = 139 and
Δ𝑓 𝑅𝐴 = 15 ∙ 2𝜇 kHz where 𝜇𝜖 0,1,2,3
Format
A1
A2
A3
B1
B2
B3
B4
C0
C2
LRA
139
139
139
139
139
139
139
139
139
© Nokia 2019
Nokia internal use
Δ𝑓 𝑅𝐴
Nu
2 ∙ 2048𝜅 ∙ 2−𝜇
4 ∙ 2048𝜅 ∙ 2−𝜇
6 ∙ 2048𝜅 ∙ 2−𝜇
2 ∙ 2048𝜅 ∙ 2−𝜇
−𝜇
15 ∙ 2 kHz 4 ∙ 2048𝜅 ∙ 2−𝜇
6 ∙ 2048𝜅 ∙ 2−𝜇
12 ∙ 2048𝜅 ∙ 2−𝜇
2048𝜅 ∙ 2−𝜇
4 ∙ 2048𝜅 ∙ 2−𝜇
Support for
restricted sets
288𝜅 ∙ 2−𝜇
576𝜅 ∙ 2−𝜇
864𝜅 ∙ 2−𝜇
216𝜅 ∙ 2−𝜇
360𝜅 ∙ 2−𝜇
504𝜅 ∙ 2−𝜇
936𝜅 ∙ 2−𝜇
1240𝜅 ∙ 2−𝜇
2048𝜅 ∙ 2−𝜇
𝑅𝐴
𝑁𝐶𝑃
Max cell range [m]
for SCS = 30 kHz
469
1055
1758
176
528
879
1934
2650
4600
Accessibility
3gpp 38.211
Table 6.3.3.1-7: NCS for preamble formats
with Δ𝑓 𝑅𝐴 = 15 ∙ 2𝜇 where 𝜇𝜖 0,1,2,3
RACH – MSG1 – Zero Correlation Zone Config
•
A parameter obtained by the UE from RRC Connection Reconfiguration (RACHConfigCommonGeneric) is zeroCorrelationZoneConfig (all values supported)
•
zeroCorrelationZoneConfig INTEGER(0..15)
•
Depending on SCS, sligthly different table is given by 3GPP (3 variants)
•
It is configurable on NRCELL level → NRCELL/zeroCorrelationZoneConfig
•
Table provides mapping between zeroCorrelationZoneConfig and NCS value
(Cyclic Shift Interval)
-
NCS determines how many cyclic shifts per root is available
(the higher NCS the lower number of cyclic shifts per root)
-
The relation between Ncs and cell radius is :
Value for example
cell radius = [c/2]*[(NCS - 1)*(TSEQ/LRA)-Delay spread]
Number of Cyclic shifts per root assuming
zeroCorrelationZoneCOnfig = 13 ➔ NCS = 34
Root #x
0
…
33
34
…
67
68
…
101
NCS = 34
15
© Nokia 2019
LRA=139
Nokia internal use
102
…
135
zeroCorrelation
ZoneConfig
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
NCS value
0
2
4
6
8
10
12
13
15
17
19
23
27
34
46
69
Ncs = 0 means that no
cyclic shifts applicable
for root
Accessibility
RACH – MSG1 – Zero Correlation Zone Config
zeroCorrelationZoneConfig parameter should be adjusted between 1 and 15 according to expected cell size, as shown in
table below :
•
In cmW, values 14-15 should be used as typical cell size is between 1 and 2 kms
•
In mmW, values 14-15 should be used as typical cell size is between 300 and 600 m
zeroCorrelationZoneConfig
16
© Nokia 2019
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
N CS value
for unrestricted set
0
2
4
6
8
10
12
13
15
17
19
23
27
34
46
69
Nokia internal use
Cell size
(m, 30kHz) cmW
Cell size (m, 120kHz)
mmW
4648
NA
NA
NA
NA
8
80
116
188
260
332
476
620
871
1303
2130
1162
NA
NA
NA
NA
2
20
29
47
65
83
119
155
218
326
533
Accessibility
RACH – MSG1 – PRACH Configuration Index
• FDD – below 6GHz
- FR1 (according to 38.211 Table 6.3.3.2-2: Random access configurations for FR1 and paired
spectrum/supplementary uplink)
• Format 0 (1.25kHz): 12, 13, 14
• TDD
- FR1 (according to 38.211 Table 6.3.3.2-3: Random access configurations for FR1 and
unpaired spectrum)
• Format A2 (30kHz): 90, 91, 92, 93, 94, 96, 97, 98, 102
• Format B4 (30kHz): 148, 149, 151, 152, 156-162
- FR2 (according to 38.211 Table 6.3.3.2-4: Random access configurations for FR2 and
unpaired spectrum)
• Format A2 (120kHz): 34, 38, 41 or 43
17
© Nokia 2019
Nokia internal use
Accessibility
RACH – MSG1 – PRACH Configuration Index
•
Below is presented how to translate values given in 3gpp related to PRACH configuration Index for FR2 (bands >
6GHz)
•
In principle, e.g. slot4 of SCS=60kHz is mapped onto slot 9 of SCS=120kHz and so on
-
Following rule can be applied (slot# of SCS60kHz * 2 + 1)
PRACH configuration Preamble
index (FR2 unpaired)
format
38
Frame
A2
Odd
Slot number
(converted to
SCS=120kHz)
9,19,29,39,49,
59,69,79
Starting
symbol
Number of PRACH Number of time-domain
slots within a
PRACH occasions
60kHz* slot
withing a RACH slot
0
1
3
Odd frame
Slots 120kHz
Slots number (60kHz)
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
DL slot
UL slot
18
© Nokia 2019
Nokia internal use
PRACH
duration
# occasions
within 20ms
4
24
PRACH
Slot
configuration
Frame number
index (FR2
(60kHz*)
unpaired)
4,9,14,19
38
Odd ,24,29,34
,39
Accessibility
RACH – MSG1 – PRACH Configuration Index
• Example with frameStructureType = tdLte and lteToNrFrameShift = 3 ms, change from A2 to B4
A2 = 1km cell range with prachConfigurationIndex = 98
B4 = 1.7km cell range with
prachConfigurationIndex = 148 or 159 but
prachConfigurationIndex 148 defines RA
only every 2 radio frames (nSFN mod 2 = 1)
while prachConfigurationIndex 159 has RA
every radio frame ➔ compromise between
latency and UL overhead
19
© Nokia 2019
(values not compatible with frameStructureType = tdLte and
lteToNrFrameShift = 3 ms)
Nokia internal use
Accessibility
SSB to PRACH occasion mapping example
with PRACH Conf. Index = 100*
RACH – MSG1 – Occasion Selection
Occasion to use for preamble transmission
SFN Subframe Slot
1
3
5
9
9
9
19
19
19
(example with PRACH Configuration Index = 100* and 8 beams configured)
7
9
19
#SSB1
rsrpThresholdSSB is recommended to
be set to 37 (i.e. -156+37 =-119dBm)
for cmW and to 53 (i.e. -156+53=103dBm) for mmW
#SSB2
#SSB3
#SSB4
9
19
1
1
2
2
3
3
1
4
2
5
3
6
1
7
2
8
3
1
1
2
2
3
3
4
1
5
2
6
3
7
#SSB5
#SSB6
#SSB7
20
9
SSB
Index
~ 40 ms
• Before UE starts RA procedure, it looks for SS/PBCH
blocks (SSB)
• If it happen that RSRP of certain beam transmitting SSB is
higher than configured threshold
(NRCELL/rsrpThresholdSSB) this beam can be used to
transmit preamble (up to UE implementation which beam exactly)
• Mapping between SSB index and Occasion (in frame and
slot) to be used is shown in following table
Occassion in Slot
#SSB8
© Nokia 2019
Nokia internal use
*PRACH Config. Index 100 assumes 1 PRACH
subframe and slot per 20ms
and is used for sake of simplicity
Accessibility
RACH – MSG1 – Power for Preamble (Msg1) Transmission
preambleReceivedTargetPower
From RRC Connection Reconfiguration message
(RACH-ConfigCommonGeneric) UE receives two
important parameters for Msg1 transmission:
mmW)
NRCELL/powerRampingStep – parameter used to
increase power by UE in each preamble retransmission
RRC Conn. Reconfig.
(parameters)
NRCELL/initialPreambleReceivedTargetPower - parameter
indicating initial RA preamble signal level (in dBm) required
(targeted) at gNB (-96dBm by default, -80dBm for Verizon in
RX power:
-96 dBm
RX power:
-94 dBm
RX power:
-92 dBm
Msg1
(pathloss
assumed to
be 116 dB)
(2dB by default)
PPRACH – power used for transmission
PUE_max – Highest power that can be used by the UE
21
PUE_max = 23 dBm
PUE_max = 23 dBm
PUE_max = 23 dBm
PPRACH= 20 dBm
PPRACH= 22 dBm
PPRACH= 23 dBm
1st Tx
2nd Tx
(if needed)
TX power selected
for transmission
+ powerRampingStep
© Nokia 2019
Nokia internal use
3rd Tx
(if needed)
Accessibility
RACH – MSG2 – Random Access Response (RAR)
RAR grant :
• Upon receipt of Msg1 gNB will create temporary UE context and schedules a
grant for Random Access Response (RAR)
• The UE uses the beam to receive as it used for the transmission of PRACH
• If the RAR grant is not received within a specific time window, the UE will
retransmit preamble with same power ramped up by a value specified in the
RRC Reconfiguration Complete message
RAR grant timing
PRACH: Msg1 - Preamble transmission
(Zadoff-Chu sequence)
PDCCH - (RAR Grant)
PDSCH: Msg2 Random Access Response
(temp. C-RNTI, UL Grant, TA)
If RAR not received within
(3TTI+ raResponseWindow)
• Earliest: 3 slots after the PRACH slot when the preamble has been received
• Latest: 3 + NRCELL/ raResponseWindow slots after this PRACH slot
PRACH: Msg1 - Preamble transmission
(Zadoff-Chu sequence)
Radio Frame 1
Radio Frame 0
Slots
0
19 0 1 2 3 4 5 6 7 8 9 10 11
RAR window
PRACH
slot
n+3
22
© Nokia 2019
Nokia internal use
(n+3) +
RAR window
Create Temp.
UE Context
19
Accessibility
RACH – MSG3
RACH Msg3 transmission:
• UE receives the UL grant in RAR Msg2 received from the gNB. Distance
between Msg2 TX and Msg3 RX must be within 6-9 slots
• The UE sends the RACH Msg3 containing its C-RNTI
• Msg3 occupies whole initial active UL BWP (48PRBs for 100MHz)
PRACH: Msg1 - Preamble
(Zadoff-Chu sequence)
PDSCH: Msg2 - RAR (RA-RNTI)
(Temp. C-RNTI, UL Grant, TA)
MAC contention resolution timer:
PUSCH: Tx1- Msg3 (temp-CRNTI)
(C-RNTI)
• After transmission of Msg3, UE starts the MAC contention Resolution timer
(NRCELL/raContentionResolutionTmr)
• The MAC contention Resolution timer monitors the reception of Contention
Resolution
• The UE restarts the MAC Contention Resolution Timer at each HARQ reTx
• If the CRC is NOK a retransmission of Msg3 is scheduled with HARQ ID set to '0'
and NDI set to '0' . If the maximum number of RA Msg3 transmissions
(NRCELLGRP/maxHarqMsg3Tx default value is 5) has been reached and still the
CRC is NOK then gNB releases the UE context and the temporary C-RNTI
23
© Nokia 2019
Nokia internal use
Make UE Context
permanent
MAC Contention
Resolution Timer
PUSCH: Tx2- Msg3 (temp-CRNTI)
(C-RNTI)
Optional
• At the successful reception of RACH Msg3 gNB schedules Contention
Resolution Grant for the UE addressing it to C-RNTI. Temp. C-RNTI is released.
OK
Restart Contention
Resolution Timer
NRCELL/maxHarqMsg3Tx reached
PRACH: Msg1 - Preamble
(Zadoff-Chu sequence)
NOK
Accessibility
•
• After transmission of Msg3, UE starts the MAC contention Resolution timer
(NRCELL/raContentionResolutionTmr)
• The MAC contention Resolution timer monitors the reception of Contention
Resolution Grant
• After successful reception of RACH Msg3, gNB resolves RACH Contention by
transmission UL Grant addressed to certain C-RNTI
PDSCH: Msg2 - RAR (RA-RNTI)
(Temp. C-RNTI, UL Grant, TA)
MAC Contention
Resolution Timer
- If MAC contention
resolution timer expires
PUSCH: Msg3 (temp. C-RNTI)
(C-RNTI)
PDCCH: Contention Resolution (CRNTI)
(UL Grant)
If the UE receives Contention Resolution Grant before MAC contention resolution
timer expiry AND the C-RNTI matches, the UE considers the Random Access
procedure as successfully completed
• The UE considers the
contention resolution
unsuccessful
24
PRACH: Msg1 - Preamble
(Zadoff-Chu sequence)
• Following the contention resolution failure,
the UE
- Increments
PREAMBLE_TRANSMISSION_COUNTER by 1
- If PREAMBLE_TRANSMISSION_COUNTER
exceeds NRCELL/preambleTransMax declare
Random Access failure
- Starts the Random Access procedure
© Nokia 2019
Nokia internal use
Optional
AT gNB
AT UE
RACH – MSG4
Contention Resolution timer expires
PRACH: Msg1 - Preamble transmission
(Zadoff-Chu sequence)
Accessibility
RACH – Call Flow
Contention Resolution
Random Access
UE Synchronization
25
•1
•2
•3
•4
The UE randomly selects a preamble and transmits it in resources reserved
for PRACH channel (cbPreamblesPerSsb, prachConfigurationIndex, rsrpThresholdSSB, preambleReceivedTargetPower, powerRampingStep)
1
Upon reception of preamble, gNB prepares Response containing
information to align timing of UE, assigns a Temporary C-RNTI and
schedules an UL Grant to send Msg3 (raResponseWindow )
UE sends first scheduled transmission containing MAC CE with UE CRNTI (CRNTI is provided to UE in RRC Connection Reconfiguration)
(raContentionResolutionTmr, maxHarqMsg3Tx)
Contention resolution corresponds to a UL Grant that is addressed to UE CRNTI (preambleTransMax)
© Nokia 2019
Nokia internal use
Msg1 - Preamble transmission
(Zadoff-Chu sequence)
Msg2 Random Access Response
(Temp. C-RNTI, UL Grant, TA)
3
Msg3
(UE CRNTI)
2
NACK
NACK
Msg4 - Contention resolution
(UL Grant)
4
Accessibility
Parameters
Domain
Sub-domain
Accessibility Call Setup
Success Rate
Accessibility Call Setup
Success Rate
Accessibility Call Setup
Success Rate
Accessibility Call Setup
Success Rate
Accessibility Call Setup
Success Rate
Accessibility Call Setup
Success Rate
Accessibility Call Setup
Success Rate
Accessibility Call Setup
Success Rate
26
Parameter Name
Abbreviation
MIND Reference
Default
value
(GUI)
Global synchronization channel gscn
number
CBRA preambles per SSB
cbraPreamblesPerSsb
MRBTS.NRBTS.NRCELL.gscn
1
MRBTS.NRBTS.NRCELL.cbraPreamblesPerSsb
64
Duration of random access
response window
Initial preamble power
MRBTS.NRBTS.NRCELL.raResponseWindow
0
Maximum number of Msg3
transmissions
Maximum number of preamble
transmission
Number of SSBs per RACH
occasion
Power ramping factor
raResponseWindow
initialPreambleReceivedT MRBTS.NRBTS.NRCELL.initialPreambleReceiv
argetPower
edTargetPower
maxHarqMsg3Tx
MRBTS.NRBTS.NRCELLGRP.maxHarqMsg3Tx
preambleTransMax
MRBTS.NRBTS.NRCELL.preambleTransMax
nbrOfSsbPerRachOccasio MRBTS.NRBTS.NRCELL.nbrOfSsbPerRachOcc
n
asion
powerRampingStep
MRBTS.NRBTS.NRCELL.powerRampingStep
© Nokia 2019
Nokia internal use
-104
5
6
3
1
reco if not list of use cases in MIND
same as
default
(GUI)
Explicit
gscn value
-96
GMC 5G19 - classical cmW
Accessibility
Parameters
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
(GUI)
Accessibility
Call Setup Success Rate
PRACH configuration index
prachConfigurationIndex
MRBTS.NRBTS.NRCELL.prachConfigurationIndex
38
Accessibility
Call Setup Success Rate
PRACH Frequency start
msg1FrequencyStart
MRBTS.NRBTS.NRCELL.msg1FrequencyStart
0
Accessibility
Call Setup Success Rate
PRACH root sequence index
prachRootSequenceIndex
MRBTS.NRBTS.NRCELL.prachRootSequenceIndex
0
Accessibility
Call Setup Success Rate
PRACH sequence type
prachSequenceType
MRBTS.NRBTS.NRCELL.prachSequenceType
0
Accessibility
Call Setup Success Rate
RSRP threshold for SSB block selection
rsrpThresholdSSB
MRBTS.NRBTS.NRCELL.rsrpThresholdSSB
0
Accessibility
Call Setup Success Rate
Timer for contention resolution
raContentionResolutionTmr
MRBTS.NRBTS.NRCELL.raContentionResolutionTmr
7
Accessibility
Call Setup Success Rate
Total number of Ra preambles
totalNumberOfRAPreambles
MRBTS.NRBTS.NRCELL.totalNumberOfRAPreambles
64
Accessibility
Call Setup Success Rate
Zero correlation zone config
zeroCorrelationZoneConfig
MRBTS.NRBTS.NRCELL.zeroCorrelationZoneConfig
13
27
© Nokia 2019
Nokia internal use
reco if not same as
default (GUI)
list of use cases in MIND
depending on
depending on expected cell size /
expected cell size /
frame structure
frame structure
cell planning required
37(cmW)
53(mmW)
GMC 5G19 - classical cmW: 37
GMC 5G19 - mmW: 53 to be added
14 or 15
depending on expected cell size
Accessibility
Radio Admission Control (NSA Option 3x)
Feature « 5GC000480 - Radio Admission Control for NSA Mode 3x Operation » introduces Radio
Admission Control for Non-Standalone operation 3x.
• The 5G NodeB checks for each procedure which tries to add an active UE, i.e. a UE with at least one
data radio bearer established, or procedures which try to add data radio bearer(s) :
• an operator configurable number of active UEs operating in NSA mode 3x per 5G cell, maxNumOfUsersPerCell
• an operator configurable number of active UEs operating in NSA mode 3x per NR Cell Group, maxNumOfUsers
• an operator configurable number of data radio bearers of active UEs operating in NSA mode 3x per NR Cell
Group, maxNumOfNonGBRBearers
• The related request is rejected if one of the above conditions is fulfilled. An all-or-nothing approach
is applied by the radio admission control if not stated otherwise.
• Operator configurable radio admission control offsets are introduced with mobility or carrier
aggregation functions :
• addNumOfHoUsers indicates the threshold for the additional number of UEs in addition to maxNumOfUsers
for handovers for NSA operation
• addNumOfNonGBRBearersHo indicates the additional number of non-GBR data radio bearers in addition to
maxNumOfNonGBRBearers for handovers for NSA operation
• maxNumOfSCellAlloc indicates the maximum total number of S-Cell allocations for UEs in the cell
28
© Nokia 2019
Nokia internal use
Accessibility
Parameters
Domain
Sub-domain
Accessibility Call Blocking
Rate
Accessibility Call Blocking
Rate
Accessibility Call Blocking
Rate
Accessibility Call Blocking
Rate
Accessibility Call Blocking
Rate
Accessibility Call Blocking
Rate
29
Parameter Name
Abbreviation
Additional number of non-GBR
addNumOfNonGBRBearers
capacity for handovers
Ho
Additional number of user capacity addNumOfHoUsers
for handovers
Maximum number of non-GBR data maxNumOfNonGBRBearers
radio bearers
Maximum number of S-Cell
maxNumOfSCellAlloc
allocations in a cell for NSA
operation
Maximum number of users in a NR maxNumOfUsersPerCell
cell for NSA operation
Maximum number of users in a NR maxNumOfUsers
Cell Group for NSA operation
MIND Reference
Default
value
(GUI)
MRBTS.NRBTS.NRCELLGRP.addNumOf
NonGBRBearersHo
MRBTS.NRBTS.NRCELLGRP.addNumOf
HoUsers
MRBTS.NRBTS.NRCELLGRP.maxNumO
fNonGBRBearers
MRBTS.NRBTS.NRCELL.maxNumOfSCe
llAlloc
0
MRBTS.NRBTS.NRCELL.maxNumOfUse
rsPerCell
MRBTS.NRBTS.NRCELLGRP.maxNumO
fUsers
© Nokia 2019
Nokia internal use
0
500
250
250
500
reco if not
same as
default
(GUI)
list of use cases in
MIND
Retainability
Radio Link Failure
Call drop ratio is one of the most important metrics used to assess network performance
• Radio Link Failure (RLF) is one of the most often reasons of call drops
Whenever call (voice or data) is cut off before parties had finished, Radio Link Failure is in place
3 kinds of RLF:
• UE Initiated RLF Handling
• SgNB Initiated RLF Handling
• UE Inactivity Handling
In RRC Connection Reconfiguration message SgNB provides a set of operator configurable parameters
like:
• NRBTS: T310, NRBTS: N310 , NRBTS: N311
• NRCELL: preambleTransMax
• NRBTS: maxRetxThreshold (recommended t32)
Those parameters are used by the UE to detect and declare Radio Link Failure on 5G link
30
© Nokia 2019
Nokia internal use
Retainability
Radio Link Failure – UE Initiated RLF
There are three reasons for UE initiated Radio Link Failure on 5G side:
• Random Access Procedure Failure (please refer to RACH Chapter)
• DL out-of-sync (OOS)
• Radio Link Control (RLC) failure – maximum number of retransmissions is reached
Upon RLF detection UE informs MeNB which passes information to SgNB
Data is switched to LTE leg and if 5G radio link will not recover itself or via PSCell change then MeNB
initiates SgNB release
• conditions for PSCell change must be fulfilled in order to trigger PSCell change
31
© Nokia 2019
Nokia internal use
Retainability
Radio Link Failure – UE Initiated RLF – DL Out of Sync
• UE monitors "out-of-sync" and "in-sync" indications
from layer 1
• Upon receiving NRBTS: N310 (default :10)
consecutive "out-of-sync" indications, UE starts timer
NRBTS: T310 (default :2000 ms)
• NRBTS: T310 is stopped upon receiving NRBTS: N311
(default :1) consecutive "in-sync" indications
-
as a result connection is continued without any dedicated
signaling exchange
Note: for subfeature, B T313 instead of T310 is used
Radio Link Recovery
N310 Out of Sync
indications
Connection
ongoing
t
T310 started
Radio Link Failure
N310 Out of Sync
indications
RLF
indication
• If NRBTS: T310 expiries (no or less than N311 "in-sync"
indications), radio link failure is detected and
SCGFailureInformation is sent by UE to MeNB
t
T310 started
32
© Nokia 2019
Nokia Internal Use
Nokia internal use
T310 stopped
T310 expired
Retainability
Radio Link Failure – UE Initiated RLF – RLC Failure
• Radio link failure can be triggered by UE if
maximum number of RLC retransmissions is
reached
Radio Link Failure
x RLC Retransmissions
RLF
indication
• This number is defined by configurable
parameter NRBTS: maxRetxThreshold and
passed to UE via
RRCConnectionReconfiguration message
- This parameter is used by the transmitting side of
each AM RLC entity to limit the number of
retransmissions corresponding to an RLC SDU,
including its segments
• In case of RLC failure UE reports radio link
failure to the MeNB via SCGFailureInformation
33
© Nokia 2019
Nokia Internal Use
Nokia internal use
t
x = maxRetxThreshold
Note:
maxRetxThreshold is set in rlcProfile.
In 5G19 for NSA 3x option
NRBTS:qciTabXNsa3x:rlcProfIdx can
be set only to 4.
Retainability
Radio Link Failure – UE Initiated RLF – PSCell Change
When a SgNB receives 5G measurements within SgNB
Modification Request PSCell change might be started
and Radio Link (RL) control timer is set (NRBTS:
tWaitingRlRecover, by default 500ms)
•
•
During the waiting RL recover timer, the UE data is
switched to LTE leg
•
The SgNB sends in SgNB Modification Request
Acknowledge message
-
MeNB
UE
SgNB- CU
SgNB- DU
UE connected to 5G cell
SCGFailureInformation
LTE SRB
tWaitingRlRecover
X2: SgNB Modification Request
X2: SgNB Modification Request Ack
SgNB-CU confirms that it is aware UE detected RLF
5GC000572
5GC000572 Network based intra-SgNB change of the serving PSCell procedure
• SgNB- CU identifies target SgNB-DU and performs Admission Control check
• If admission control thresholds are not reached UE context setup is performed on Target SgNB-DU
and additionally X2AP: SgNB Modification Required message is sent to MeNB (see call flow in the next
slide)
34
All information necessary for PSCell change are incorporated within Modification Required message
© Nokia 2019
Nokia Internal Use
Nokia internal use
Retainability
Radio Link Failure – SgNB Initiated RLF
• SgNB detects RLF for 5G link based on:
-
DTX detection for requested DL HARQ feedback on PUCCH
-
DTX detection of CSI reports on PUCCH
-
Radio Link Control (RLC) failure – maximum numer of retransmissions is reached
• When a SgNB declares an RLF on the PSCell a control timer is set
•
During the waiting time, the data is switched to LTE leg of the split bearer
-
Scope of 5GC000570 5G - LTE flow control at X2
• After timer expiry, SgNB will release the UE context by sending an SgNB
initiated SgNB release with the cause: ‘Radio Connection with UE lost’ to
MeNB
35
© Nokia 2019
Nokia internal use
SgNB
MeNB
Retainability
Radio Link Failure – SgNB Initiated RLF – DTX For DL HARQ Feedback
• SgNB counts number of consecutive DTX detection for
requested DL HARQ feedback reports
-
Radio link problem detection is done per carrier, so only DL
HARQ feedback received for the current carrier is evaluated
(even if DL HARQ feedback is sent jointly for several DL
carriers via single PUCCH)
• If number of conscutive DTX exceeds 100, SgNB starts
RLF guard timer NRBTS: tRLFindForDU (default: 300ms)
• If RLF guard timer will expire, gNB-DU will inform gNBCU about RLF by sending UE Context Modification
Required over F1 link
• If the number of consecutively received nonDTX for DL
HARQ feedback exceeds 5 the radio link is assumed to
be recovered
36
© Nokia 2019
Nokia internal use
SgNB- CU
SgNB- DU
Number of detected
DL HARQ DTX ≥ 100
F1: UE Context Modification
Required
Number of detected
DL HARQ feedbacks
≥5
NRBTS: tRLFindForDU
Retainability
Radio Link Failure – SgNB Initiated RLF – DTX For CSI
• For each UE, CSI reports are evaluated to detect radio link
problems
-
•
Radio link problem detection is done per carrier, only CSI reports for the
current carrier are evaluated even if they are received in other carrier
If the number of consecutively received DTX for CSI reports
exceeds 10, radio link problem is detected
• SgNB starts RLF guard timer NRBTS: tRLFindForDU (default:
300ms)
• If RLF guard timer will expire, SgNB DU will inform gNB CU
about RLF by sending UE Context Modification Required over
F1 link
• If the number of consecutively received nonDTX for CSI
reports exceeds 2 a radio link is recovered
37
© Nokia 2019
Nokia internal use
SgNB- CU
SgNB- DU
Number of detected
CSI DTX ≥ 10
F1: UE Context Modification
Required
Number of detected
CSI feedbacks ≥ 2
Retainability
Radio Link Failure – SgNB Initiated RLF – RLC Failure
• Radio link failure can be triggered by SgNB if
maximum number of RLC retransmissions is
reached
Radio Link Failure
x RLC Retransmissions
RLF
indication
• This number is defined by configurable
parameter NRBTS: maxRetxThreshold
- This parameter is used by the transmitting side of
each AM RLC entity to limit the number of
retransmissions corresponding to an RLC SDU,
including its segments
• In case of RLC failure SgNB-DU informs SgNBCU via : UE Context Modification Required
message with Cause set to ’RLC Failure’
38
© Nokia 2019
Nokia internal use
t
x = maxRetxThreshold
Note:
maxRetxThreshold is set in rlcProfile.
In 5G19 for NSA 3x option
NRBTS:qciTabXNsa3x:rlcProfIdx can
be set only to 4.
Retainability
Radio Link Failure – SgNB Initiated RLF Execution
• Having received UE Context Modification Required, gNB-CU
checks if no other procedure is ongoing for this UE
-
SgNB- CU
In case of ongoing PSCell change gNB-CU ignores RLF indication
from DU and proceeds with handover
• If there is no other procedure, gNB-CU starts Radio Link (RL)
control timer (NRBTS: tWaitingRlRecover)
-
MeNB
RLF due to DTX of
DL HARQ or CSI
tWaitingRlRecover F1: UE Context Modification
Required
As long as timer is running, gNB-CU will not start procedure of UE
context release with MeNB unless tWaitingRlRecover>3s
GTP-U PDU (F1-U DDDS)
Cause: Radio Link Outage
• In addition to RL control timer start, gNB-CU starts Data
switching (on PDCP) towards LTE
-
Data on PDCP will be forwarded to LTE Leg until Radio link is either
recovered or tWaitingRlRecover timer expires
• When timer expires gNB-CU sensds to MeNB SgNB Release
Required with the Cause: ‘Radio Connection with UE lost’
39
© Nokia 2019
Nokia internal use
SgNB- DU
UE data transmission and UE
scheduling stopped. Bearer is
suspended
PDCP transmission switch to X2-U
X2: SgNB Release Required
Retainability
Radio Link Failure – SgNB Initiated RLF Execution – UE Context Release
-
-
Counter M55112C00502: SGNB_REL_SN_REQ_UE_LOST is
updated when X2AP: SGNB RELEASE REQUIRED message sent
with cause equal to Radio Connection With UE lost
Counter M55112C00501: SGNB_REL_SN_SUCC_UE_LOST is
incremented when X2AP: SGNB RELEASE CONFIRM message
received as procedure completion
• Two timers supervise SgNB release and UE context
cleaning on 5G:
-
40
MeNB
5GC000509 5GC000475
• Having received SgNB Release Required message
from gNB-CU, Master eNB starts procedure of UE
Context Release procedure on 5G side
SgNB- CU
SgNB- DU
X2: SgNB Release Required
X2: SgNB Release Confirm
X2: UE Context Release
timerF1ProcGuard
TimerX2UeProcGuard
F1: UE Context Release
Command
F1: UE Context Release
Complete
X2AP: SgNB Release Required message with
RLF cause set to 'Radio Network Layer’ will
increment M55116C00004
RLF_INITIATED_RNL counter
NRBTS: timerX2UeProcGuard (default 2s)
NRBTS: timerF1UeProcGuard (default 500ms)
© Nokia 2019
Nokia internal use
Retainability
Radio Link Failure – UE Inactivity Handling
•
•
UE inactivity can be detected by SgNB only if NRBTS: actInactDetNSAUe is
set to true
SgNB will treat UE as inactive if there is no DL/UL data received and no
data in the buffer for a given time period:
-
nsaInactivityTimer + 1s; at the time of bearer set up
nsaInactivityTimer after the reception of the first DL PDCP SDU or UL PDCP
PDU
Please note that if DL or UL packet will be received when nsaInactivityTimer timer
is running then timer is stopped/restarted.
•
The UL and DL inactivity timers are independent, however both of them
must be terminated in order to declare UE inactivity
-
•
•
41
PDCP DL determines and internally reports DL status (active / inactive) to
PDCP UL which stores it
PDCP UL determines UL inactive status by expiry of inactivity timer and if DL
status is inactive then UE is considered inactive on 5G leg
The SgNB sends after the inactivity detection SgNB Release Required
message to the MeNBs with the cause value ‘User Inactivity’
Note: LTE and NR inactivity timers are independent, however both of them
must be terminated in order to declare UE RRC IDLE
© Nokia 2019
Nokia internal use
MeNB
SgNB- CU
SgNB- DU
nsaInactivityTimer
Default:10s
X2: SgNB Release Required
TimerX2UeProcGuard
X2: SgNB Release Confirm
X2: UE Context Release
timerF1ProcGuard
F1: UE Context Release
Command
F1: UE Context Release
Complete
SgNB Release Required message with
cause set to ‘User Inactivity’ increments
M55112C02001
SGNB_RELEASE_REQ_UE_INACT counter,
whereas SgNB Releas Confirm will
increment M55112C02002
SGNB_RELEASE_SUCC_UE_INACT.
Retainability
Parameters
Domain
Sub-domain
Retainability Capacity
Retainability Capacity
Retainability Handover
Success Rate
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
Retainability Radio Link
Failure
42
Parameter Name
Abbreviation
MIND Reference
Default
value
(GUI)
Activate inactivity detection for NSAactInactDetNSAUe
UE
Non Stand Alone inactivity timer
nsaInactivityTimer
Dual Connectivity overall timer
tDCoverall
MRBTS.NRBTS.actInactDetNSAUe
0
MRBTS.NRBTS.nsaInactivityTimer
MRBTS.NRBTS.tDCoverall
10
2000
Activate gNB initiated RLF
actGnbInitRlf
MRBTS.NRBTS.actGnbInitRlf
1
Activate UE initiated RLF
actUeInitRlf
MRBTS.NRBTS.actUeInitRlf
1
F1AP UE Proc Guard Timer
timerF1UeProcGuard
MRBTS.NRBTS.timerF1UeProcGuard
2500
Guard timer for X2-C UE related
timerX2UeProcGuard
signaling
Maximum retransmission threshold maxRetxThreshold
MRBTS.NRBTS.timerX2UeProcGuard
2000
MRBTS.NRBTS.rlcProf4.maxRetxThreshold
16
Number n310
n310
MRBTS.NRBTS.n310
10
Number n311
n311
MRBTS.NRBTS.n311
1
RLF indication timer for DU
tRLFindForDU
MRBTS.NRBTS.tRLFindForDU
0
Timer t310
t310
MRBTS.NRBTS.t310
6
Waiting RL Recovery timer
tWaitingRlRecover
MRBTS.NRBTS.tWaitingRlRecover
3
© Nokia 2019
Nokia internal use
reco if not
same as
default
(GUI)
1
32
list of use cases in
MIND
GMC 5G19 - classical
cmW: 1
GMC 5G19 - classical
cmW: 32
Coverage : BF parameters
Description ; Analog Beamforming
[Before 5GC000535-A and
5GC000535-B]
One active beam.
Possibility by script to activate
another beam than the default
one.
actBeamforming and other BFrelated parameters are not
meaningful.
43
[5GC000535-A] and
[5GC000535-B]
actBeamforming = False => one
sector beam
actBeamforming = True =>one
64 beams GoB (not
configurable).
[5GC000535-F]
actBeamforming = False => one sector beam
actBeamforming = True => GoB made of 32
directions, selected by basicBeamSet
(beamSetAbf_1A, beamSetAbf_32A,
beamSetAbf_32B, beamSetAbf_32C)
To provide the best coverage, the basicBeamSet shall
be chosen according to the geographical topology.
The beamSetAbf_1A provides one narrow beam. The
beamSetAbf_32A (left below) provides narrower beams to the celledge user compared to near-cell user so well designed for long-cell.
The beamSetAbf_32B (right) is well designed for tall and narrow cell.
© Nokia 2019
Nokia internal use
• left edge angle φl
Coverage : BF parameters
• right edge angle φr
Description ; Digital Beamforming
[5GC000533-A]
SSB Beamforming :
Up to 8 SSB beams (coarse beams) used
for synchro (sweeping principle) and for
traffic
actBeamforming = TRUE
numberOfTransmittedSsBlocks
basicBeamSet, leftEdgeAngle,
rightEdgeAngle
Narrow SSB beams provides better coverage
versus sector-wide SSB beam.
Much higher antenna gain
Much higher total EIRP
The following default basic beam
sets and respective valid opening
angles in azimuth direction shall
be available for selection by
operator.
SSB beams corresponds to the
parameter
numberOfTransmittedSsBlocks.
Beam set corresponds to the
parameter basicBeamSet
Azimuth opening angles
corresponds to the parameters
leftEdgeAngle/rightEdgeAngle
MIMO 2x2 : 1 SSB x-pol beam
MIMO 4x4 : 2 SSB x-pol beam
44
© Nokia 2019
Nokia internal use
Coverage : BF parameters
Description ; Digital Beamforming ; Antenna performances
The coverage depends on the caracteristics of the Digital BF antenna, in particular :
•
Nominal total TX RF power and Nominal total TX power per beam
•
Antenna gain power
The main caracteristics can be found in the related CFAMs.
5GC000664 - AEQD AirScale MAA 64T64R 128AE B43 200W
5GC000562 AEQA AirScale MAA 64T64R 192AE B42 200W (extract below)
=200W
53(total Tx RF power) -10xLog16beams = 41
Lower when BF is off
41+25.5 = 66.5
calculated as (Pnom per beam -10log10(number of
carriers)) - (-18.2dBFs)); for configuration of 8
beams = 41-0 - -18.2=59.2
45
© Nokia 2019
Nokia internal use
Coverage: BF parameters
Parameters
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
(GUI)
reco if not same as default
(GUI)
list of use cases in MIND
Accessibility
Cell Coverage
Activate Beamforming
actBeamforming
MRBTS.NRBTS.NRCELL.actBeamforming
0
1
GMC 5G19 - classical cmW
Accessibility
Cell Coverage
Basic Beam Set
basicBeamSet
MRBTS.NRBTS.NRCELL.beamSet.basicBeamSet
1
beamset_2 (cmW)
beamSet_5_3 (cmW)
beamset_6 (cmW)
General: beamset_6 or beamset_5_3
(depending on coverage type)
High throughput (low SSB overhead):
beamset_2
Accessibility
Cell Coverage
BTS Beam Refinement P2
nrBtsBeamRefinementP2
MRBTS.NRBTS.NRCELL.beamSet.nrBtsBeamRefinementP2
0
Accessibility
Cell Coverage
Left Cell Edge Angle
leftEdgeAngle
MRBTS.NRBTS.NRCELL.beamSet.leftEdgeAngle
60
General: 60
4-sector based: 45
Accessibility
Cell Coverage
Right Cell Edge Angle
rightEdgeAngle
MRBTS.NRBTS.NRCELL.beamSet.rightEdgeAngle
60
General: 60
4-sector based: 45
Accessibility
Cell Coverage
Number of transmitted Synchronization Signal Blocks numberOfTransmittedSsBlocks
MRBTS.NRBTS.NRCELLGRP.numberOfTransmittedSsBlocks
1
46
© Nokia 2019
Nokia internal use
2 (cmW)
6 (cmW)
8 (cmW)
depending on basicBeamSet
Coverage: Power parameters
Based on Parameter
NRCELL.beamSet.basicBeamSet
TX
Array 1
(-45°)
.
.
.
32 TX/RX
are forming
8 polar
beams (-45°)
to consider max no of beams
where the common case in FR1 is
to have 8 beams
SS/PBCH Power Setting
SS/PBCH block power setting is managed by
NRCELL:ssPbchBlockPower parameter that should follow this
rule:
NRCELL:ssPbchBlockPower ≤ NRCELL:pMax + 10 log (no.
TRX per polarization) – 10*log (nb_re)
For calculation, see Golden SCF
Cross beam ±45°
at UE side
NRCELL.pMax is the
max o/p Power of one
TX
TX
Array 2
(+45°)
.
.
.
Digital BF for FR1
32 TX/RX
are forming
8 polar
beams (+45°)
In Digital BF, 1cc/RU:
Pwrcc [dBm] = 10 log (RU o/p DL Power
in milliwatts)
pMax = Pwrcc [dBm} – 10 log (no of
TXs)
Pwrcc2019
-10 log (64)
47pMax©=Nokia
PMax is the max o/p power per 1 TX
channel/signal REs
Max o/p DL power per all polar beams = PMax + 10 log (no of TXs/2)
Max o/p power per all polar beams = PMax + 10 log (32)
Nokia internal use
Power per all polar beam is distributed over the
currently transmitted channel/signal REs
Max o/p DL power per RE per polar beam = PMax
+ 10 log (32) - 10 log (no of REs)
Coverage : Power parameters
Major power parameters related with Coverage
•
•
•
•
pMax is the power per Trx
min and max range of pMax depends on Radio Unit.
Note : in early trials it was unused by the system in certain software for cmWave.
Total output power can be derived with the following formula:
• Total output power is = Pmax + 10*LOG(#TRX). [#TRX is 64 for AEQD, 2 for AEUA.]
• Maximum output power per cross beam = Pmax + 10*LOG(#TRX)
• Maximum output power per polarization beam = Pmax + 10*LOG(#TRX/2)
•
•
•
•
ssPbchBlockPower defines the SS and PBCH powers in terms of EPRE.
To increase the Cell Coverage this parameter can be increased.
E.g when set to 10 dBm (instead of default 0 dBm), the RSRP measured by the UE is 10dB higher.
However it must satisfy some rules w.r.t to pMax. See MIND and Golden SCF, and must be carefully
increased such that it does not interfer that much with DL data.
48
© Nokia 2019
Nokia internal use
Coverage : Power parameters
Internal tuning for indoor trials/demo
•
Scripts at RU (for indoor trials/demo) or ABIL Loner: some RU are not suitable for indoor trials
(even with pMax set at min value). However it is possible, in the scope of an indoor demo, by
applying R&D scripts at RU or ABIL Loner, to decrease the TX output power and the gains. Both
contributes to significantly reduce the RF-EMF.
Example : AEQD tuned with script reducing the power to <2W) (Prated set to 0.5dBm instead of default 35dBm).
Cell on-air without traffic:
Front 0° (LoS) @7m
3 V/m = ambient value
Cell on-air with high traffic: (400 Mbps DL), and AEQD scripts (PRated= 0.5) & Gain volatile RU devmem DL 0x2000 (default)
Front 0° (LoS) @1m
46 V/m
Front 0° (LoS) @3m
25 V/m
Front 0° (LoS) @7m
15 V/m
Back
@0,5m >2 V/m
Side
@0m
6 V/m
Front 15°
@7m
4 V/m
Cell on-air with high traffic: (400 Mbps DL), and AEQD scripts (PRated= 0.5) & Gain volatile RU devmem DL 0x1200
Front 0° (LoS) @7m
7 V/m
Cell on-air with medium traffic: (100 Mbps DL), and AEQD scripts (PRated= 0.5) & Gain volatile RU devmem DL 0x1200
Front 0° (LoS)
@7m
3 V/m
49
© Nokia 2019
Nokia internal use
Coverage : Power parameters
Domain
Sub-domain
Accessibili Cell Coverage
ty
Accessibili Cell Coverage
ty
50
Parameter Name
Abbreviation
MIND Reference
SS PBCH Block Power
ssPbchBlockPower
MRBTS.NRBTS.NRCELL.ssPbchBlockPower
Maximum output power
pMax
MRBTS.NRBTS.NRCELL.pMax
© Nokia 2019
Nokia internal use
Default
value
(GUI)
reco if not
same as
default
(GUI)
Depending
on pMax
Depending
on RF
module and
local
regulations
list of use cases in
MIND
Coverage : miscellaneous parameters impacting the coverage
When DL 256QAM is used, the maximum DL transmission power needs to be restricted in order to guarantee that
the PA operates in its linear region. This decreases the coverage of the cell.
Domain
Sub-domain
Accessibili Cell Coverage
ty
Accessibili Cell Coverage
ty
51
Parameter Name
Abbreviation
MIND Reference
PDSCH Power Back-off for 256QAM dlQam256PowerBackoffSub MRBTS.NRBTS.NRCELL.dlQam256PowerBac
6
koffSub6
PDSCH Power Back-off for 256QAM dlQam256PowerBackoffAboMRBTS.NRBTS.NRCELL.dlQam256PowerBac
(mmWave)
ve6
koffAbove6
© Nokia 2019
Nokia internal use
Default
value
(GUI)
1.5
4.5
reco if not
same as
default
(GUI)
list of use cases in
MIND
ACCESSIBILITY&X2 KPIs
KPI ID
LTE_6420a
LTE_6419a
LTE_6429a
LTE_6430a
LTE_6434a
LTE_6435a
LTE_6431a
LTE_6432a
LTE_6433a
LTE_1894a
MRBTS_238a
MRBTS_49a
NR_5014a
NR_5015a
52
KPI NAME
E-UTRAN EN-DC X2 Setup Attempts
E-UTRAN EN-DC X2 Setup Success Ratio
E-UTRAN Initial E-RAB Setup Attempts for MCG bearer with NR PDCP
E-UTRAN Initial E-RAB Setup Success Ratio for MCG bearer with NR PDCP
Maximum number of UEs capable for EN-DC
Average number of UEs capable for EN-DC
SCG Addition Preparation Attempts
SCG Addition Preparation Failure Ratio due to SgNB Rejection
SCG Addition Preparation Failure Ratio due to timer expiry (T_DC_Prep)
LTE X2-U GTP payload UL and DL
IP Data Traffic Volume Discard
IP Data Traffic Volume
AC SR NSA user
Nr AC req NSA user
© Nokia 2019
Nokia internal use
UNIT
No unit
%
No unit
%
No unit
No unit
No unit
%
%
byte
MB
MB
%
No unit
RETAINABILITY KPIs
KPI ID
NR_6a
NR_7a
NR_5035a
NR_18a
NR_5036a
NR_19a
NR_5030a
53
KPI NAME
5G Number of SgNB initiated releases due to user inactivity
5G SgNB release success ratio due to user inactivity
5G Number of MeNB initiated SgNB releases
5G MeNB initiated SgNB release success ratio
5G Number of UE radio link failures
5G SgNB initiated SgNB release requests
5G SgNB triggered normal release ratio
© Nokia 2019
Nokia internal use
UNIT
No unit
%
No unit
%
No unit
No unit
%
COVERAGE&QUALITY KPIs
KPI ID
NR_5062a
NR_5063a
NR_5065a
NR_5064a
NR_5066a
NR_106a
NR_226a
NR_227a
NR_292a
NR_293a
NR_294a
NR_295a
NR_296a
NR_297a
NR_298a
NR_299a
NR_85a
NR_86a
NR_87a
NR_88a
54
KPI NAME
5G Average UE related SINR for PUSCH in Rank 1
5G Average UE related SINR for PUSCH in Rank 2
5G Average UE related SINR for PUCCH
5G Average UE related RSSI for PUSCH
5G Average UE related RSSI for PUCCH
5G Average received UE signal pow er for PUSCH
5G Average Timing Advance index in RACH setup
5G Average Timing Advance index during RRC connected
5G Average MCS used for PUSCH CP-OFDMA Rank1 w ith 64QAM table
5G Average MCS used for PUSCH CP-OFDMA Rank2 w ith 64QAM table
5G Ratio of PUSCH transmissions in Rank 1 (w ith 64QAM MCS)
5G Ratio of PUSCH transmissions in Rank 2 (w ith 64QAM MCS)
5G Average MCS used for PDSCH Rank1 w ith 64QAM table
5G Average MCS used for PDSCH Rank2 w ith 64QAM table
5G Average MCS used for PDSCH Rank3 w ith 64QAM table
5G Average MCS used for PDSCH Rank4 w ith 64QAM table
5G Ratio of PDSCH transmissions in Rank 1 (w ith 64QAM MCS table)
5G Ratio of PDSCH transmissions in Rank 2 (w ith 64QAM MCS table)
5G Ratio of PDSCH transmissions in Rank 3 (w ith 64QAM MCS table)
5G Ratio of PDSCH transmissions in Rank 4 (w ith 64QAM MCS table)
© Nokia 2019
Nokia internal use
UNIT
dB
dB
dB
dBm
dBm
dBm
No unit
No unit
No unit
No unit
%
%
No unit
No unit
No unit
No unit
%
%
%
%
COVERAGE&QUALITY KPIs
KPI ID
NR_300a
NR_301a
NR_302a
NR_303a
NR_304a
NR_305a
NR_306a
NR_307a
NR_5060a
NR_5061a
NR_89a
NR_90a
NR_184a
NR_185a
NR_289a
NR_176a
NR_5056a
NR_5057a
55
KPI NAME
5G Average MCS used for PDSCH Rank1 w ith 256QAM table
5G Average MCS used for PDSCH Rank2 w ith 256QAM table
5G Average MCS used for PDSCH Rank3 w ith 256QAM table
5G Average MCS used for PDSCH Rank4 w ith 256QAM table
5G Ratio of PDSCH transmissions in Rank 1 w ith 256QAM MCS
5G Ratio of PDSCH transmissions in Rank 2 w ith 256QAM MCS
5G Ratio of PDSCH transmissions in Rank 3 w ith 256QAM MCS
5G Ratio of PDSCH transmissions in Rank 4 w ith 256QAM MCS
5G Average w ideband CQI, 64QAM table
5G Average w ideband CQI, 256QAM table
5G Usage of 2Tx transmission in PDSCH
5G Usage of 4Tx transmission in PDSCH
5G Initial BLER in dow nlink transmissions using 64QAM MCS table
5G Residual BLER in dow nlink transmissions using 64QAM MCS table
5G Initial BLER in dow nlink transmissions using 256QAM MCS table
5G Residual Block Error Ratio (BLER) for PDSCH using 256QAM MCS table
5G Initial BLER in PUSCH using 64QAM MCS table
5G Residual BLER in PUSCH using 64QAM MCS table
© Nokia 2019
Nokia internal use
UNIT
No unit
No unit
No unit
No unit
%
%
%
%
No unit
No unit
%
%
%
%
%
%
%
%
56
Scope
Accessibility/Ret
ainability
Usage :
Throughput
Mobility
4G-5G
interactions
Design Specific
Parameters
© Nokia 2019
Nokia internal use
Usage : Packet
Delay
Main aspects influencing the throughput
•
Split bearer :
•
Data forwarding at split bearer setup and release
•
X2 Flow control for established split bearer
•
PDCP / RLC / HARQ configuration
•
Fixed MCS versus Link Adaptation
•
Modulation 256Qam
•
SU-MIMO
•
Carrier Aggregation
•
UL:DL ratio & Frame Structure
57
© Nokia 2019
Nokia internal use
Throughput : LTE-NR interworking Data forwarding
Description (1/2) ; Data forwarding (4G<->5G) at Split Bearer setup/release
(4G->5G) data forwarding at Split Bearer setup : the Data Forwarding over X2 is activated through the parameter
actDlDataForwardingX2 on 5G gNB (5G gNB indicates it to the 4G enb in the X2AP: SGNB ADDITION REQUEST
ACKNOWLEDGE)
•
If actDlDataForwardingX2 = False, there isn’t “continuous DL data transmission”: UL/DL data transmission over 5G
radio starts when data is received from SGW or UE.
•
If actDlDataForwardingX2 = True, there is “continuous DL data transmission”, using X2-U. The 4G NB forwards DL
data over X2-U, indicates end of forwarding over X2-U interface. UL/DL data transmission over 5G radio continues
when data is received from SGW or UE.
•
The best setting for throughput performance is actDlDataForwardingX2 = True
(5G->4G) data forwarding at Split Bearer release : upon reception of the X2AP: SGNB RELEASE REQUEST (whatever the
trigger), the 5G gNB suspends the transmission over 5G radio and forwards the data to 4G eNb. The parameter
actDlDataForwardingX2Limit activates/deactivates DL data forwarding limitation over X2 towards the MeNB to protect
LTE's PDCP buffer overrun. It can only be set to true if actDlDataForwardingX2 = True.
• actDlDataForwardingX2Limit should only be set to True in case of Nokia 4G equipment:
• Due to current lower 4G throughput observed in case of EN-DC, it is recommended however to keep the
parameter to False.
58
• actDlDataForwardingX2Limit should be set to False in case of other vendor 4G equipment.
© Nokia 2019
Nokia internal use
Throughput : LTE-NR interworking X2 Flow Control
Description (2/2) ; X2 Flow Control parameters for Established Split Bearer
When the split bearer is up and running between the S-GW and the 5G gNB, the X2 Flow Control takes place.
DL : DL data path is based on dlDataSplitMode,
0:dlOverF1U : DL Data is all sent to 5G DU
1:dlOverX2U : DL Data is all sent to 4G eNb
2:dlOverF1UX2U : DL Data is sent on both depending on flow control output
The flow control is Nokia prioprietary or 3GPP, based on dlFlowControlAlgo. It is recommended
to use 3ggp (the validation team said it give better results).
Choose dlOverF1UX2U for (increased throughput) and DL traffic continuity.
The flow control is tuned with :
dlDataSplitGainThreshold : 5 -> 3 and can even be set to 1 to make sure X2U PDU are in
anyway forwarded.
minThFlowCtrlX2 : 1Mbps -> 20Mbps to make sure no low throughput during calibration phase
though this period is quite small based on the dddsPeriodX2 10ms
maxTransferDelayX2 : 20ms -> 100ms to be above the QCI delay, can be optimized later to
lower values 80ms/60ms
See more here.
59
© Nokia 2019
UL : UL data path is based on ulDataPath, 0:ulOverLte; 1:ulOverNr; 2:ulOverLteNr.
If ulOverLteNr, then UE performs the split based on ulDataSplitThreshold (amount of bits in its
buffer above which it starts sending data on the second path.)
Choose ulOverLte if you want to favor UL coverage
Choose ulOverNr or ulOverLteNr if you want to favor UL peak throughput.
Note that UE may not be capable of 'ulOverLteNr', in such case the gNb forces
ulDataSplitThreshold to infinity
Nokia internal use
Throughput : Data Forwarding and X2 Flow Control parameters
List
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
(GUI)
Usage
Throughput - Average in
DL
Activate DL data forwarding over X2
actDlDataForwardingX2
MRBTS.NRBTS.actDlDataForwardingX2
DL data forwarding
over X2 is activated
Usage
Throughput - Average in
DL
Activate DL data forwarding limitation over X2
actDlDataForwardingX2Limit
MRBTS.NRBTS.actDlDataForwardingX2Limit
DL data forwarding
limitation over X2 is
deactivated
Usage
Throughput - Average in
DL
DL Data split gain threshold
dlDataSplitGainThreshold
MRBTS.NRBTS.qciTab9Nsa3x.dlDataSplitGainThreshold
Usage
Throughput - Average in
DL
DL Data Split Mode
dlDataSplitMode
MRBTS.NRBTS.qciTab9Nsa3x.dlDataSplitMode
dlOverF1UX2U
Usage
Throughput - Average in
DL
DL flow control algorithm
dlFlowControlAlgo
MRBTS.NRBTS.fiveQiTab9.dlFlowControlAlgo
nokiaFlowControl
Usage
Throughput - Average in
DL
Max Transfer Delay
maxTransferDelayX2
MRBTS.NRBTS.x2FlowControlProfForCu.maxTransferDelayX2
20
Usage
Throughput - Average in
DL
Minimum throughput for flow control
minThFlowCtrlX2
MRBTS.NRBTS.x2FlowControlProfForCu.minThFlowCtrlX2
1
Usage
Throughput - Average in
DL
Periodicity of X2-U Downlink Data Delivery Status
Indication messsage
dddsPeriodX2
MRBTS.NRBTS.x2FlowControlProfForCu.dddsPeriodX2
10
Usage
Throughput - Average in
UL
UL data path
ulDataPath
MRBTS.NRBTS.qciTab9Nsa3x.ulDataPath
Usage
Throughput - Average in
UL
UL Data Split threshold
ulDataSplitThreshold
MRBTS.NRBTS.qciTab9Nsa3x.ulDataSplitThreshold
60
© Nokia 2019
Nokia internal use
5
ulOverNr
infinity
reco if not same as
default (GUI)
list of use cases in MIND
5
1
General : 5
Demo - Peak Throughput : 1
3gppFlowControl
GMC 5G19 - classical cmW
Throughput : PDCP/ RLC / HARQ parameters
Description
•
•
•
61
For L1 HARQ, consider in particular :
• maxDlHarqTx (default = 5)
• maxUlHarqTx (default = 5)
For RLC, consider in particular :
• MRBTS.NRBTS.rlcProf4.maxRetxThreshold (default t16)
• It might be beneficial to increase to max value t32 for NSA call retainability.
• RLC timers have also been optimized to following shorter values:
• MRBTS.NRBTS.rlcProf4.tReassembly = 15ms
• MRBTS.NRBTS.rlcProf4.tStatusProhibit = 15ms
• MRBTS.NRBTS.rlcProf4.tPollRetr = 45ms
For PDCP, consider in particular :
• MRBTS.NRBTS.pdcpProf2.tReordering (default ms100).
• Trying a very short value (ms1) had dramatic negative impact on FTP throughput.
© Nokia 2019
Nokia internal use
Throughput : PDCP/RLC/HARQ parameters
List
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
Usage
Block Error Rate
Maximum number of DL HARQ transmissions
maxDlHarqTx
MRBTS.NRBTS.NRCELLGRP.maxDlHarqTx
5
Usage
Block Error Rate
Maximum number of UL HARQ transmissions
maxUlHarqTx
MRBTS.NRBTS.NRCELLGRP.maxUlHarqTx
5
Usage
Block Error Rate
Maximum retransmission threshold
maxRetxThreshold
MRBTS.NRBTS.rlcProf4.maxRetxThreshold
t16
Usage
Throughput - Average in DL Timer reordering
tReordering
MRBTS.NRBTS.drbPdcpDefProf.tReordering
100
62
© Nokia 2019
Nokia internal use
reco if not same as
default
list of use cases in MIND
Throughput : MCS and Link Adaptation parameters
Description (1/4)
Link Adaptation activation:
•
The DL/UL Link adaptation is a mandatory feature, which is always active (except some R&D
tests)
The L1 measurements, which are the basis for the DL/UL MCS selection, are :
•
•
63
For DL MCS : the CQI reports provided by the UE
For UL MCS : the UL SINR measurements evaluated by the gNB.
© Nokia 2019
Nokia internal use
Throughput : MCS and Link Adaptation parameters
Description (2/4)
Behaviour
Feature activation
Always active
MCS
MCS is dynamically selected based on CQI for DL and UL SINR for UL.
dllaIniMcs : this parameter defines the default MCS for DL transmissions.
The default MCS is applied as long as CQI reports are missing or when the CQI reports
are outdated.
ullaIniMcs : this parameter indicates the default MCS for UL transmissions
The default MCS is applied as long as SINR reports are missing or when the SINR
reports are outdated
Rank
DL Rank is dynamically adjusted based on RI reported by the UE.
MCS tables
DL 64QAM MCS table / DL 256QAM MCS table selection depends on UE capabilities
and actDl256Qam.
64
© Nokia 2019
Nokia internal use
Throughput : MCS and Link Adaptation parameters
Description (3/4)
DL MCS selection
•
•
•
•
65
DL MCS is taken from a CQI-To-MCS mapping table.
Separate mapping tables are implemented depending on the MCS index table (64QAM MCS index table
/256QAM MCS index table), the applied rank (Rank1 / Rank2 / Rank3 / Rank4), and the band (below 6GHz / above
6GHz).
A CQI correction based on UE’s HARQ feedback may be applied in order to stay close to the configured DL bler
target dllaBlerTarget (default: 10%).
•
The CQI correction is bounded by dllaDeltaCqiMin (default: -15.0) and dllaDeltaCqiMax (default: 15.0)
•
The CQI step down (in case of UE’s NACK) is configured through dllaDeltaCqiStepDown.
•
The CQI step up (in case of UE’s ACK) is dllaDeltaCqiStepDown x [dllaBlerTarget/(1- dllaBlerTarget)].
The default MCS dllaIniMcs is applied as long as CQI reports are missing or when the CQI reports are outdated,
or if DL Link Adaptation is not implemented.
© Nokia 2019
Nokia internal use
Throughput : MCS and Link Adaptation parameters
Description (4/4)
UL MCS Selection
•
•
•
•
•
•
•
•
66
UL MCS is taken from a SINR-To-MCS mapping table.
Separate SINR-to-MCS mapping tables depending on the number of layers used for spatial multiplexing (Rank1 /
Rank2), the supported slot types (10 PUSCH symbols / 11 PUSCH symbols), and the band (below 6GHz / above
6GHz)
The measured SINR is eventually corrected based on the received power headroom reports (PHR) to eliminate
any bias influencing the measured SINR due to restricted UL transmission power.
A SINR correction based on gNB HARQ may be applied in order to stay close to the configured UL bler target
ullaBlerTarget.
The SINR correction is bounded by ullaDeltaSinrMin and ullaDeltaSinrMax.
•
The SINR step down (in case of gNB’s NACK) is configured through ullaDeltaSinrStepdown.
•
The SINR step up (in case of gNb’s ACK) is ullaDeltaSinrStepDown x [ullaBlerTarget/(1- ullaBlerTarget)].
The default MCS ullaIniMcs is applied as long as long as SINR reports are missing or when the SINR reports are
outdated or when the UL LA is not implemented.
In order to reach highest UL throughputs in very good radio conditions, the recommendation is to
use ullaBlerTarget = 3%. ullaDeltaSinrMin and ullaDeltaSinrMax could be set respectively to –15.0 and 10.0.
However, in a commercial network, higher values of ullaBlerTarget could be used, such as 5% or even 10%,
© Nokia 2019
depending on the results of the field tests.
Nokia internal use
Throughput : MCS and Link Adaptation parameters
List
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
Usage
MCS Usage
BLER Target for DL Transmission
dllaBlerTarget
MRBTS.NRBTS.NRCELL.dllaBlerTarget
0.1
Usage
MCS Usage
BLER target for UL transmission
ullablertarget
MRBTS.NRBTS.NRCELL.ullablertarget
0.1
Usage
MCS Usage
Delta CQI maximum of DL OLLA
dllaDeltaCqiMax
MRBTS.NRBTS.NRCELL.dllaDeltaCqiMax
15
Usage
MCS Usage
Delta CQI minimum of DL OLLA
dllaDeltaCqiMin
MRBTS.NRBTS.NRCELL.dllaDeltaCqiMin
-15
Usage
MCS Usage
Delta CQI stepdown of DL OLLA
dllaDeltaCqiStepDown
MRBTS.NRBTS.NRCELL.dllaDeltaCqiStepDown
0.25
Usage
MCS Usage
Delta SINR maximum of UL OLLA
ullaDeltaSinrMax
MRBTS.NRBTS.NRCELL.ullaDeltaSinrMax
15
Usage
MCS Usage
Delta SINR minimum of UL OLLA
ullaDeltaSinrMin
MRBTS.NRBTS.NRCELL.ullaDeltaSinrMin
-15
Usage
MCS Usage
Delta SINR Stepdown of UL OLLA
ullaDeltaSinrStepdown
MRBTS.NRBTS.NRCELL.ullaDeltaSinrStepdown
0.25
Usage
MCS Usage
Initial MCS for DL transmission
dllaIniMcs
MRBTS.NRBTS.NRCELL.dllaIniMcs
3
Usage
MCS Usage
Initial MCS for UL Transmission
ullaIniMcs
MRBTS.NRBTS.NRCELL.ullaIniMcs
0
67
© Nokia 2019
Nokia internal use
reco if not same as
default
list of use cases in MIND
0.03
GMC 5G19 - classical cmW
10
GMC 5G19 - classical cmW
0
GMC 5G19 - classical cmW
Throughput : DL 256QAM parameters
Description (1/2)
DL 256QAM, based on 3GPP, is available in 5G19:
•
It is based on 3GPP standard a.k.a L1 Release 5.
•
It handles the full set of MCS as described by the 3GPP.
•
Two MCS tables, table1 and table2, are defined (see next slide). The scheduler will use one or the other
depending on the UE capabilities and the feature activation.
actDl256Qam=False : the scheduler always uses the table1
actDl256Qam=True :
the scheduler uses the table1 if the UE is not 256QAM capable
the scheduler uses the table2 if the UE is 256QAM capable
•
It is not recommended to activate DL256QAM in the field, in 5G19, if DL MIMO4x4 is also to be activated, as
it leads to worst performance than with DL64QAM + DL MIMO4x4.
•
The 3GPP TBS values are given by following R&D link: http://5gtables.eecloud.dynamic.nsn-net.net/
•
Finally, a power back-off is implemented with 256QAM in order to comply with 3GPP Error Vector Magnitude
(EVM) at transmitter side: amount of back-off is a trade-off between the overall throughput and the coverage
at cell edge.
•
68
© Nokia 2019
Current recommendation is to use 1.5dB of back-off (dlQam256PowerBackoffSub6 = 1.5) for all RUs,
although slightly smaller amount could be used in the case of AEQA, AEQD & AEQN (with these RUs, with
1.5dB, EVM is at 2.5% while 3GPP requirement is 3.5%).
Nokia internal use
Throughput : DL 256QAM parameters
Description (2/2)
MCS Index
IMCS
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
Modulation Order
Qm
2
2
2
2
2
2
2
2
2
2
4
4
4
4
4
4
4
6
6
6
6
6
6
6
6
6
6
6
6
2
4
6
Target code Rate x [1024]
R
120
157
193
251
308
379
449
526
602
679
340
378
434
490
553
616
658
438
466
517
567
616
666
719
772
822
873
910
948
reserved
reserved
reserved
Spectral
efficiency
0.2344
0.3066
0.3770
0.4902
0.6016
0.7402
0.8770
1.0273
1.1758
1.3262
1.3281
1.4766
1.6953
1.9141
2.1602
2.4063
2.5703
2.5664
2.7305
3.0293
3.3223
3.6094
3.9023
4.2129
4.5234
4.8164
5.1152
5.3320
5.5547
MCS Index
IMCS
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
3GPP TS 38.214 Table 5.1.3.1-1: MCS index table 1 for PDSCH
69
Modulation Order
Qm
2
2
2
2
2
4
4
4
4
4
4
6
6
6
6
6
6
6
6
6
8
8
8
8
8
8
8
8
2
4
6
8
Target code Rate x [1024]
R
120
193
308
449
602
378
434
490
553
616
658
466
517
567
616
666
719
772
822
873
682.5
711
754
797
841
885
916.5
948
reserved
reserved
reserved
reserved
Spectral
efficiency
0.2344
0.3770
0.6016
0.8770
1.1758
1.4766
1.6953
1.9141
2.1602
2.4063
2.5703
2.7305
3.0293
3.3223
3.6094
3.9023
4.2129
4.5234
4.8164
5.1152
5.3320
5.5547
5.8906
6.2266
6.5703
6.9141
7.1602
7.4063
3GPP TS 38.214 Table 5.1.3.1-2: MCS index table 2 for PDSCH
© Nokia 2019
Nokia internal use
Throughput : DL 256QAM parameters
List
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Usage
Throughput - Average in DL Activate 256QAM in DL
actDl256Qam
MRBTS.NRBTS.NRCELL.actDl256Qam
Usage
Throughput - Average in DL PDSCH Power Back-off for 256QAM
dlQam256PowerBackoffSub6
MRBTS.NRBTS.NRCELL.dlQam256PowerBackoffSub6
70
© Nokia 2019
Nokia internal use
Default value
FALSE
1.5
reco if not same as
default
list of use cases in MIND
Throughput : DL SU-MIMO
Description
DL SU-MIMO 2x2 and 4x4 principles :
2 streams per user in case of DL 2x2 MIMO : 1 beam, made of 2 polarizations, per user
4 streams per user in case of DL 4x4 MIMO : 2 beams, each made of 2 polarizations, per user
4x4 MIMO
2x2 MIMO
71
© Nokia 2019
Nokia internal use
Throughput : DL SU-MIMO
Description (2/4)
Beams selection for DL SU MIMO operation :
Analog beamforming :
use the SSB-beam available from PRACH procedure.
Digital beamforming :
•
For MIMO 2x2 : Use the SSB beam available from the PRACH procedure
•
For MIMO 4x4 : Use in addition the second best SSB beam reported by the UE.
•
Highest peak throughput is achieved if the streams are orthogonal with each other.
•
The cross-pol beam by nature offers two streams perfectly orthogonal (MIMO 2x2)
•
But it is much more difficult to achieve orthogonality with two cross-pol beams (MIMO 4x4). Reflexion
(multipath) may help (urban area). Ideally it is better if the second best SSB beam is not contiguous with the
best SSB beam (less interferences between them), but it is hard to have control on this !
Note :
In 5G19 the 'refined beams' are not available (only the SSB-beams are available).
In Analog BF, MIMO 4x4 is not available.
72
© Nokia 2019
Nokia internal use
Throughput : DL SU-MIMO
Description (3/4)
The DL MIMO mode is configured with dlMimoMode
•
30 : 2x2 Closed Loop Spatial Multiplexing (DEFAULT VALUE, is introduced by 5GC000425-O)
•
40: 4x4 or 4x2 Closed Loop Spatial Multiplexing (is introduced by 5GC000605-E)
•
50: 2x2 Open Loop Spatial Multiplexing (is introduced by 5GC000531-C)
•
60: 4x4 or 4x2 Open Loop Spatial Multiplexing (is introduced by 5GC000605-G)
Layer mapping : Only one codeword shall be considered and will be mapped from 1 to 4 layers. A 2nd
codeword is defined only for more than 4 layers, which is out of scope in 5G19.
Layer mapping up to 4 layers
73
© Nokia 2019
Nokia internal use
Throughput : DL SU-MIMO
Description (4/4)
Closed Loop mode :
This modes uses the UE’s feedback Rank, PMI, CQI. This mode requires that the gNB transmits the CSIRS (Channel State Information Reference Signal) and that the UE measures it and sends feedback
accordingly.
Open Loop :
In this mode, gNB uses only UE's feedback Rank and CQI.
It is recommended to use Closed Loop mode when available. However, in 5G19, Closed Loop mode is
only available for MIMO 2x2. Therefore, for MIMO 4x4, Open Loop mode shall be used.
Moreover, there is a restriction in 5G19, when using RU AZQL. In this case, only CL MIMO 2x2 shall be
used. MIMO 4x4 is not available in 5G19 for this type of RU.
74
© Nokia 2019
Nokia internal use
Throughput : SU-MIMO parameters
List
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
Usage
Throughput - Average in UL Uplink MIMO mode
ulMimoMode
MRBTS.NRBTS.NRCELL.ulMimoMode
Closed loop Spatial
Multiplexing (2x2)
Usage
Throughput - Peak in DL
dlMimoMode
MRBTS.NRBTS.NRCELL.dlMimoMode
2x2 Closed Loop
Spatial Multiplexing
75
Downlink MIMO Mode
© Nokia 2019
Nokia internal use
reco if not same as
default
list of use cases in MIND
4x4 or 4x2 Open
Loop Spatial
Multiplexing
GMC 5G19 - classical cmW
Throughput : UL:DL Ratio Parameters & Frame Structure
Description (1/4)
Parameter ulDlDataSlotRatio is introduced by feature 5GC000542-B.
With new frame structure types (5GC001116 ad 5GC001208) available :
• The parameter frameStructureType is used to set the frame structure :
• semiStatic = standardized by 3gpp, supported ulDlDataSlotRatio = 1/4, 3/7, supported
guardPeriodLength = 2, 4, 6 OFDM symbols
• tdLte = standardized by 3gpp and compatible with LTE TDD frame structure.
ulDlDataSlotRatio is not configurable. lteToNrFrameShift can be 0ms or 3ms.
• flexible = vendor specific, supported ulDlDataSlotRatio = 1/9, 2/8, 3/7, 5/5. Not recommended
for use as no longer maintained by R&D
76
© Nokia 2019
Nokia internal use
Throughput : UL:DL Ratio Parameters & Frame Structure
Description (2/4)
The same UL:DL ratio shall be configured in all cells of the network to avoid interference, probably
also need to coordinate with other networks in same region. That is why it is likely that the operators
will not use ‘flexible’ for deployment, but rather 'semiStatic' or 'tdLte'. Anyway, value 'flexible' should not
be used any more as it is not maintained.
• Regarding the guardPeriodLength:
• Only value 2 and 4 are supported for semiStatic frame structure (recommendation is to use 4
symbols of GP with more than 7km of cell range).
• Only value 4 and 6 are supported for tdLte frame structure. However, since traffic is not
possible in the special slots in tdLte in 5G19, it does not matter which value is used in that
case.
• Regarding lteToNrFrameShift:
• 0ms can be used if numberOfTransmittedSsBlocks ≤ 6 beams (and if no alignment with any
other network is required)
• 3ms is to be used if numberOfTransmittedSsBlocks > 6 beams
• If this case, note that manualFrameTimingAdjustment needs to be set to 3000µs. See
Yammer post and slides for more details
77
© Nokia 2019
Nokia internal use
Throughput : UL:DL Ratio Parameters & Frame Structure
Description (3/4)
The peak throughput depends on the chosen frame structure and UL:DL ratio. Refer to the 5G
throughput tool for detailed computation: http://5gtables.eecloud.dynamic.nsn-net.net/nrTput.php.
• Although tdLte frame structure should lead to higher DL throughput compared to semiStatic
due to lower number of special slots in tdLte, it is the contrary in 5G19, since traffic is not
possible in special slots in tdLTE. Therefore, ceteris paribus, we should expect about 3% lower
throughput with tdLte.
• The statement above is however not always true (and therefore, DL throughput provided by
the 5gtables tool is not correct in that case) and depends on the value of csiReportPeriodicity
and the size of the CSI report in the UL.
csiReportPeriodicity impacts not only latency & capacity (see section "Usage: Packet Delay"), but also
throughput.
• In 5G19, by default, CSI reports sent by the UE cannot be multiplexed with UL ACK/NACK: the gNB
avoids scheduling in DL if the corresponding UL ACK/NACK would fall in the same slot as a CSI
report.
• This may have a high impact (up to 8-9%) on DL throughput, depending on the value
of csiReportPeriodicity (i.e. on the number of times CSI reports need to be sent).
78
© Nokia 2019
Nokia internal use
Throughput : UL:DL Ratio Parameters & Frame Structure
Description (4/4)
However, FGCR-2650 - Support of mux-SR-HARQ-ACK-CSI-PUCCH-sameSymbol was added in late
5G19, and allows now the multiplexing of SR, ACK/NACK and CSI report on the same PUCCH
symbol.
•
It needs to be enabled by swconfig.txt file with following flag: 0x10003E=1 (and possibly 0x460181=1)
Even if FGCR-2650 is enabled, DL scheduling can still be impacted, due to “PR474594 : New Problem
Reported (5G19,, B - Major,[5G19][classical][AEQD]DL Throughput falls down by around 8% when
csiReportPeriodicity = slots40)”.
• FGCR-2650 was not correctly coded, and multiplexing of SR, ACK/NACK and CSI report is possible
only if the number of bits is below 11 (in case of 1 beam and/or MIMO 2x2 - i.e. small size of CSI
report - , it should be fine). Correction to PR474594 will not be added in 5G19 as it is not a TOP
BLOCKER.
In 5G19A, FGCR-2650 will not be needed any more since other format of PUCCH will be available.
79
© Nokia 2019
Nokia internal use
Throughput : UL:DL ratio parameters
List
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
reco if not same as
default
list of use cases in MIND
Usage
Throughput - Peak in DL
Frame Structure Type
frameStructureType
MRBTS.NRBTS.NRCELL.tddFrameStructure.frameStructureType
flexible
tdLte
GMC 5G19 - classical cmW
Usage
Throughput - Peak in DL
Guard Period length
guardPeriodLength
MRBTS.NRBTS.NRCELL.tddFrameStructure.guardPeriodLength
-
4Symbols
GMC 5G19 - classical cmW
Usage
Throughput - Peak in DL
LTE to NR frame shift
lteToNrFrameShift
MRBTS.NRBTS.NRCELL.tddFrameStructure.lteToNrFrameShift
0
3
GMC 5G19 - classical cmW
Usage
Throughput - Peak in DL
UL to DL logical data slot ratio
ulDlDataSlotRatio
MRBTS.NRBTS.NRCELL.tddFrameStructure.ulDlDataSlotRatio
2/8 split
Usage
Throughput - Peak in DL
Manual frame timing adjustment
manualFrameTimingAdjustmen MRBTS.MNL.MNLENT.SYNC.manualFrameTimingAdjustment
t
3000
to be added in GMC19
80
© Nokia 2019
Nokia internal use
0
Throughput : UL MIMO1x1 versus UL MMO2x2 with Single UE Tx
Description
•
•
81
Note that most (if not all) of the UEs currently available in the market, as of October 2019, have only one single 5G Tx,
meaning that they have only one transmitted antenna for 5G (and usually another common one for 4G/3G/2G).
•
These UEs cannot perform UL MIMO2x2, and will be limited to UL MIMO1x2 (1 Tx at UE side + 2 Rx at gNB side)
Be careful though not to confuse single UE Tx and UL MIMO1x1.
•
It is possible at gNB side to configure the UE to perform only UL MIMO 1x1 via swconfig.txt file (rdULRank:
0x460019=1).
•
The corresponding UL throughput is then given in the 5Gtables tool (http://5gtables.eecloud.dynamic.nsnnet.net/nrTput.php), selecting the option: Uplink Layers = 1x1 MIMO (5GC000532).
•
However, this is not optimal, since we lose, among other things, the Rx diversity at gNB side.
•
Therefore, the recommendation is still to use UL MIMO 2x2, even if the UE is limited to 1 single 5G Tx.
•
The corresponding UL throughput is obtained by dividing by two the UL throughput obtained in the
5Gtables tool, selecting the option: Uplink Layers = 2x2 MIMO.
© Nokia 2019
Nokia internal use
Throughput : SSB burst & CSI RS Tracking periodicities
Description
•
SSB burst periodicity is configured with parameter ssBurstSetPeriod.
•
The lower the SSB burst periodicity, the higher the number of SSB slots and thus the lower the number of slots which
can be used for DL scheduling, leading to lower throughput (below an example of scheduling with 10ms periodicity on
the left and 20ms on the right).
•
The higher the SSB burst periodicity, the slowlier will be the acquisition of the 5G signal and/or the detection of the
best 5G beam.
•
CSI RS Tracking period is configured with parameter csirsTrackingPeriod.
•
The lower the CSI RS Tracking period, the higher the number of CSI RS Tracking slots (see the two green colored slots
above with csirsTrackingPeriod = 80ms, i.e. 160 slots).
•
The higher the CSI RS Tracking period, the less updated the CSI information available to UE (and indirectly to gNB).
Current recommendation is to use csirsTrackingPeriod = 80ms and ssBurstSetPeriod = 20ms.
•
82
© Nokia 2019
Nokia internal use
Throughput : SSB burst & CSI RS Tracking periodicities
List
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
reco if not same as
default
list of use cases in MIND
20
GMC 5G19 - classical cmW
Usage
Throughput - Peak in DL
SS Burst Set Period
ssBurstSetPeriod
MRBTS.NRBTS.NRCELLGRP.ssBurstSetPeriod
10
Usage
Throughput - Peak in DL
CSI-RS Tracking Period
csirsTrackingPeriod
MRBTS.NRBTS.NRCELL.csirsForTracking.csirsTrackingPeriod
80
83
© Nokia 2019
Nokia internal use
Throughput KPIs
THROUGHPUT INDICATORS vs TIME CONSIDERED
Average throughput based on the duration of the period selected (in blue below)
•
•
Formula contains in denominator the counter MEAS_PERIOD_XXX_YYY_REPORT (in second, millisecond,
microsecond) corresponding to the duration of the GP (Granularity Period).
•
The GP is the period defined to send the PM XML file (e.g: in LTE, GP = 15mn = 900s).
• The throughput is depending on the volume of data traffic. Low data volume means low
throughput. Higher is the data volume, higher is the throughput. If cell loaded (e.g: Busy Hour)
the throughput reported by the KPI is very close to the real throughput.
Average throughput based on the duration of the data slots used (in green below)
•
•
Indicators with formula using the counters « DATA_SLOT_PDSCH » and/or « DATA_SLOT_PUSCH » in the
denominator.
• The throughput is not depending on the volume of data traffic (only a minimum traffic is
needed). But the throughput is higher than the reality. Knowing the frame structure, it is
possible to deduce the average number of PDSCH or PUSCH per frame and so to introduce a
correction to have a better throughput.
84
© Nokia 2019
Nokia internal use
THROUGHPUT KPIs
THROUGHPUT INDICATORS vs TIME CONSIDERED
Average throughput based on the duration of the data OFDM symbols used (in purple below)
•
•
Indicators with formula using the counters « PDSCH_OFDM_SYMBOLS » and/or « PUSCH_OFDM_SYMBOLS » in the
denominator.
• The throughput is not depending on the volume of data traffic (only a minimum traffic is
needed). But the throughput is much higher than the reality. Comparing to the throughput
based on the duration of the data slots, it permits to quantify the impact of the control part
used in the slots.
Average throughput based on the duration of the L2 Scheduler buffer not empty (in brown below)
•
•
Indicators with formula using the counters « ACC_UE_DL_DRB_DATA » and/or « ACC_UE_UL_DRB_DATA » in the
denominator.
• The throughput is not depending on the volume of data traffic. It is the current most accurate
throughput when making big DL or UL transfer. The sampling period is 20 slots. When there is
an amount of data that can be sent on less than 20 slots, there is a probability that the counter
is not incremented. The side effect is that in this case, the throughput can be very high. (ex: Big
UDP file DL transfer the DL KPI returns a throughput very close to user throughput but the UL
KPI returns a very high throughput because only small amount of data are sent in UL).
85
© Nokia 2019
Nokia internal use
THROUGHPUT KPIs
KPI ID
NR_5084a
NR_308a to NR_327a
NR_5085a
NR_328a to NR_347a
NR_175a
NR_370a
NR_371a
NR_372a to NR_391a
NR_392a
NR_393a to NR_412a
NR_413a
NR_415a
NR_416a
NR_108a
NR_112a
86
KPI NAME TO CHECK
NSA PDCP SDU thp tx w/o rep DL
5G NSA Maximum PDCP SDU throughput in DL for QoS group 01
NSA PDCP SDU thp tx w/o rep UL
5G NSA Maximum PDCP SDU throughput in UL for QoS group 01
5G Average estimated throughput over F1-U
5G Average estimated DL throughput over X2-U
5G PDCP SDU throughput received over F1-U in DL at gNB-DU
5G Maximum PDCP SDU throughput over F1-U in DL for QoS group 01
5G PDCP SDU throughput in uplink over F1-U at gNB-DU
5G Maximum PDCP SDU throughput over F1-U in UL for QoS group 01
5G RLC PDU throughput retransmitted in DL by High RLC
5G RLC PDU throughput transmitted in DL by Low RLC
5G RLC PDU throughput received in UL by Low RLC
5G MAC PDU transmitted throughput on PDSCH with 64QAM MCS table
5G MAC PDU throughput including retransmissions on PDSCH with 256QAM MCS table
© Nokia 2019
Nokia internal use
UNIT
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
Mbit/s
THROUGHPUT KPIs
KPI ID
NR_5088a
NR_248a
NR_5090a
NR_419a
NR_110a
NR_5089a
NR_249a
NR_5091a
NR_420a
NR_417a
NR_239a
NR_421a
NR_418a
NR_240a
NR_422a
NR_62a
NR_423a
NR_424a
NR_63a
NR_425a
NR_426a
NR_5100a
NR_5101a
87
KPI NAME TO CHECK
UNIT
5G Active cell MAC PDU throughput on PDSCH data slots on initial HARQ transmissions
Mbit/s
5G Average MAC PDU efficient data throughput in downlink
Mbit/s
5G Active cell MAC PDU throughput on PDSCH on initial HARQ transmissions
Mbit/s
5G Average NR MAC PDU ultra efficient data throughput in downlink at DU
Mbit/s
5G MAC PDU transmitted throughput on PUSCH
Mbit/s
5G Active cell MAC PDU throughput on PUSCH data slots using 64QAM table on initial HARQ transmissions
Mbit/s
5G Average MAC PDU efficient data throughput in uplink
Mbit/s
5G Active cell MAC PDU throughput on PUSCH on initial HARQ transmissions
Mbit/s
5G Average NR MAC PDU ultra efficient data throughput in uplink at DU
Mbit/s
5G MAC SDU throughput in DL transmitted to MAC PDU
Mbit/s
5G Average MAC SDU efficient throughput in downlink
Mbit/s
5G Average NR MAC SDU ultra efficient data throughput in downlink on DU
Mbit/s
5G MAC SDU throughput in UL received from MAC PDU
Mbit/s
5G Average MAC SDU efficient throughput in uplink
Mbit/s
5G Average NR MAC SDU ultra efficient data throughput in uplink on DU
Mbit/s
5G DL RLC PDU throughput transmitted without repetitions by High RLC
Mbit/s
5G Average High RLC efficient data throughput in downlink without retransmissions on DU
Mbit/s
5G Average High RLC ultra efficient data throughput in downlink without retransmissions on DU
Mbit/s
5G UL RLC SDU throughput received without repetitions by High RLC
Mbit/s
5G Average High RLC efficient data throughput in uplink without retransmissions on DU
Mbit/s
5G Average High RLC ultra efficient data throughput in uplink without retransmissions on DU
Mbit/s
5G Average MAC layer user throughput in downlink
Mbit/s
5G Average MAC layer user throughput in uplink
Mbit/s
© Nokia 2019
Nokia internal use
Throughput KPIs
•
A frame can be composed of slots SSB, slots PDSCH, slots PUSCH, slots CSI, slots GUARD PERIOD and
slots RACH.
•
A pattern of n (depending on the configuration) frames is repeated.
•
KPIs NR_5088a, NR_248a, NR_5089a, NR_249a, NR_239a, NR_240a, NR_423a and NR_425a are based
on slots PxSCH used (x=D nor U).
•
In use case studied below, it is highlighted that a correction factor must be added to have a cell
throughput closer to the real throughput.
•
A KPI improvement is to multiply these KPIs by this corrected factor. It is the average percentage of
PxSCH slots used in the pattern:
In DL : dl_data_slots/(MEAS_PERIOD_NR_MAC_PDU_TPUT (µs)/(DATA_SLOT_PDSCH_TIME (µs)/
DATA_SLOT_PDSCH))
•
•
•
•
88
Rem: dl_data_slot is also counting the CSI slots but logically low compared to PDSCH slots
In UL : ul_data_slots/(MEAS_PERIOD_NR_MAC_PDU_TPUT (µs)/(DATA_SLOT_PDSCH_TIME (µs)/
DATA_SLOT_PDSCH))
New throughput KPIs will be created in next release including these factor corrections. Higher will be
the traffic, closer to real cell throughput will be these new KPIs.
© Nokia 2019
Nokia internal use
Throughput KPIs
Warning about the KPIs NR_5100a and NR_5101a (based on counter ACC_UE_xL_DRB_DATA).
The use case studied below (1 UE) has permitted to conclude that during:
DL UDP transfer, NR_5100a provides a throughput aligned with the one measured on UE side.
DL TCP transfer, NR_5100a provides a throughput far from the one measured on UE side.
The reason is the « sampling period » used by counters ACC_UE_DL_DRB_DATA and
ACC_UE_UL_DRB_DATA. Currently it is 20 slots in cm wave and it is too high.
Each 20 slots, the L2 PS buffer is checked. If buffer not empty, ACC_UE_xL_DRB_DATA (x=D or U) is
incremented. Small quantities of data in the buffer can be flushed in 1 slot and so there is a big
probability to have an empty buffer when checked after 20 slots.
It also explains why when performing DL Transfer (UPD or TCP), you can see incoherent NR_5101a values
(several Gbps). Idem for UL transfer with NR_5100a incoherent.
CR has been created to request a sampling period of 1slot, under analysis in R&R
Warning on the fact that NR_5100a and NR_5101a are per DBR. Currently, 1 UE has only 1 DRB. But when
multi-RAB will be present (in 5G19A), need to know the average number of DRB per UE to have the
average thpt per UE. With enough traffic (several UEs), these KPIs should provide correct throughput
values.
89
© Nokia 2019
Nokia internal use
Throughput FTP vs UDP – Conditions & end user (xCAL) results
Tests performed on ORANGE FRANCE network in NANTES on gNB BD_DES_MARTYRS (5G19 MP 1.1 5G19_5.4835.229 ) with only 1 UE
on 1 cell and no UE on others cells of the gNB.
Only group 08 is used and only 64QAM in DL/UL. UL is done on LTE leg and so 5G UL throughput not present here.
Frame structure configuration used by Orange:
Frame structure pattern over 8 frames = 160 slots:
•
TDLTE 3ms; DL Data slot = 92/160 ; UL Data slot = 24/160 ; RACH slot = 8/160; CSI slot = 4/160
•
GUARD PERIOD slot = 16/160; SSB slot = 16/160; SCS = 30kHz so slot duration=500µs.
Theoretical values are very close to values observed on NetAct counters. So counters are correctly working in this scenario
CSI slots are also counted by counter DL_DATA_SLOTS(M55308C00001)
90
ZZZ_NANTES_BD_DES_MARTYRS_5G_NR
Values read on NetAct
UL_DATA_SLOTS(M55308C00002)(#)
PRACH_SLOTS(M55308C00004)(#)
DL_DATA_SLOTS(M55308C00001)(#)
SSB_SLOTS(M55308C00003)(#)
GUARD
PERIOD
© Nokia
2019
18/09/2019 18/09/2019 18/09/2019 18/09/2019
20:00:00
20:15:00
20:30:00
20:45:00
810,086
810,085
810,088
810,088
270,028
270,029
270,030
270,028
3,240,345 3,240,343 3,240,348 3,240,347
540,060
540,060
540,052
540,056
539,481
539,483
539,482
539,481
GUARD PERIOD: We don’t have counter for guard period but it can be
deduced doing the difference between 5 400 000 (number of slots
during 15mn on 3 cells) and the slots counters values.
Nokia internal use
Throughput FTP vs UDP – Conditions & end user (xCAL) results
FTP Transfer in DL
• Transfer done in mono thread (file transmitted in one queue only)
• Average 5G PDCP throughput = 210 Mbps; Transfer duration = 540 seconds (measured on the XCAL (END USER) graphs
provided)
• FTP download size deduced = 210.008*540/8 = 14 175 MB
UDP Transfer in DL
• S1U link throughput (10Gbit/s) much higher than gNB throughput
• Average 5G PDCP throughput = 231 Mbps; Transfer duration = 540 seconds (measured on the XCAL graphs provided)
• FTP download size deduced = 231.209*540/8 = 15 607 MB
FTP Transfer
91
UDP Transfer
© Nokia 2019
Nokia internal use
Throughput FTP vs UDP – OSS KPI (Netact) results
ZZZ_NANTES_BD_DES_MARTYRS_5G_NR_T1 (kB)
DL_PDCP_VOL_RCV_S1U_QOS_GRP_08(M55315C01008)(kB)
DL_DATA_VOL_DISCARD_S1U(M55315C06001)(kB)
DL_VOL_TX_NSA_QOS_GRP_08(M55319C02008)(kB)
DL_MAC_SDU_VOL_DTCH(M55309C01001)(kB)
DL_PDCP_VOL_RCV_F1_QoS_GRP_08(M55314C03008)(kB)
DL_PDCP_VOL_SNT_X2_QOS_GRP_08(M55313C08008)(kB)
18/09/2019 20:00:00 18/09/2019 20:15:00
FTP
UDP
15,221,959.00
53,358,081.00
0.00
34,077,978,884.00
15,222,018.00
19,477,153.00
14,509,320.519
15,997,214.898
14,439,911.000
15,848,566.000
813,819.00
3,669,506.00
ZZZ_NANTES_BD_DES_MARTYRS_5G_NR_T1 (Packets)
DL_PDCP_SDU_RCV_S1U_QOS_GRP_08(M55315C00008)(#)
DL_DATA_NUM_DISCARD_S1U(M55315C05001)(#)
DL_NUM_LOST_QoS_GRP_08(M55323C04008)(#)
DL_SDU_TX_NSA_QOS_GRP_08(M55319C01008)(#)
DL_NUM_SNT_F1_QoS_GRP_08(M55323C00008)(#)
DL_PDCP_NUM_RCV_F1_QoS_GRP_08(M55314C02008)(#)
DL_PDCP_NUM_SNT_X2_QOS_GRP_08(M55313C13008)(#)
18/09/2019 20:00:00 18/09/2019 20:15:00
FTP
UDP
10,570,813
37,365,608
0
23,731,185
0
20,136
10,570,854
13,639,466
10,006,872
11,075,171
10,006,872
11,075,171
563,982
2,564,295
DL_DATA_VOL_DISCARD_S1U(M55315C06001)(kB) unit is incorrect. It must be byte . Ticket CAS-264281-K2K2
created.
On FTP, packet size = 14439911000/10006872 = 1443 bytes;
On UDP, packet size = 15848566000/11075171 = 1431 bytes
FTP: DL_MAC_SDU_VOL_DTCH (kB) = 14 509 320 = 14 509 MB.
➢ On XCAL, at PDCP level we measure 14 175MB, we have an average header size around 2.3%
UDP: DL_MAC_SDU_VOL_DTCH (kB) = 15 997 214 = 15 997 MB.
On
XCAL, at PDCP level we measure 15 607MB, we have an average header size around 2.4%
92
©➢
Nokia
2019
Nokia internal use
Throughput FTP vs UDP – OSS KPI (Netact) results
The UE is alone on the gNB. It
permits to use the gNB
counters at cell level
AVE_NSA_USER_HOLDING_TIME = 568 seconds in FTP and 563 seconds in UDP.
➢ These counters are incremented since the CAC admission and so include the time before/after DL transfer
➢ The results are in line with the transfer duration of 540s.
93
© Nokia 2019
Nokia internal use
Throughput FTP vs UDP – OSS KPI (Netact) results
In UDP ACC_UE_DL_DRB_DATA = 53717. It is incremented each 20 slots (= 10ms as SCS = 30 kHz)
•
•
•
•
It corresponds to 537.17 seconds. It is in line with the transfer duration.
5G Average MAC layer user throughput in downlink (NR_5100a) = 238Mbit/s. We have seen that it includes 2.3% overhead.
Adding this correction, it is 233.5Mbit/s, thus very close to 231 Mbit/s measured on XCAL.
Reason: as S1U thpt >> gNB thpt and no flow control, the L2 PS buffer is never empty and ACC_UE_DL_DRB_DATA is
incremented each 20 slots during the DL transfer.
Side effect is that 63% of S1U packets/bytes are discarded at PDCP level. (DL_DATA_VOL_DISCARD_S1U (byte) and
DL_DATA_NUM_DISCARD_S1U (packet))
In FTP ACC_UE_DL_DRB_DATA = 39764. It is incremented each 20 slots = 10ms
•
•
•
•
It corresponds to 397.64 seconds. It is not at all in line with the transfer duration.
5G Average MAC layer user throughput in downlink (NR_5100a) = 293Mbit/s. We have seen that it includes 2.4% overhead.
Even with this correction, it is 286Mbit/s very far from 210 Mbit/s measured on XCAL.
Reason: due to TCP retransmissions, L2 PS buffer can be occasionally flushed in less than 20 slots and ACC_UE_DL_DRB_DATA
is NOT SYSTEMATICALLY incremented because buffer checked each 20 slots.
Meaning that in better radio conditions, we will have less retransmissions and the NetAct throughput will be more realistic.
Also transmission has been done in mono-thread. Doing transmission in multi-thread will improve the throughput and the
NetAct measures as all the threads will be not simultaneously in retransmission.
CNI-49919 has been created: ACC_UE_DL_DRB_DATA and ACC_UE_UL_DRB_DATA must be incrementation each slot. It has
been rejected and CR must be created.
94
© Nokia 2019
Nokia internal use
Throughput FTP vs UDP – OSS KPI (Netact) results
Based on the frame structure (see slide 2), with the pattern of 8 frames (160 slots), DL Data slot = 92/160.
In UDP, DATA_SLOT_PDSCH_TIME (µs) = 309 226 000. Supposing that all PDSCH slots are used:
•
The real time spent is 309 226 000 / (92/160) = 537 784 347 µs = 537.8 seconds
•
It is in line with 540 seconds measured on XCAL graph.
In FTP, DATA_SLOT_PDSCH_TIME (µs) = 262 158 500. Supposing that all PDSCH slots are used:
•
The real time spent is 309 226 000 / (92/160) = 455 927 826 µs = 455.9 seconds
•
It is NOT in line with 540 seconds measured on XCAL graph.
•
It is neither in line with ACC_UE_DL_DRB_DATA = 397.64 seconds.
•
So many DATA slots are not used to send data and it highlights the fact that ACC_UE_DL_DRB_DATA is not always incremented
when needed
For information:
•
•
95
DATA_SLOT_PDSCH(M55308C00005)(#) and DATA_SLOT_PDSCH_TIME(M55308C00008)(us) DON’T CONTAIN slots CSI.
DL_DATA_SLOTS(M55308C00001)(#) counts slots PDSCH and slots CSI.
© Nokia 2019
Nokia internal use
96
Scope
Accessibility/Ret
ainability
Usage :
Throughput
Mobility
4G-5G
interactions
Design Specific
Parameters
© Nokia 2019
Nokia internal use
Usage : Packet
Delay
Latency : Proactive scheduling parameters
Description
Proactive scheduling functionality shall be controlled by feature activation flag actProactUlScheduling.
Proactive UL Resource Assignment provides the possibility to demonstrate very low ping response times in lab and low
load field environments.
NB: with DRX feature activated (actCDrx set to “True”), proactive scheduling can be not or less efficient if occurring
during DRX active state.
REM: DRX feature (5GC000772) is released for a UE when all DRBs are released or a voice DRB is setup or a measurement
gap is setup.
actProactUlScheduling: activation flag for proactive xPUSCH scheduling (“TRUE” to activate the feature, “FALSE” to deactivate).
Two timers shall be handled for each 5GUE :
➢ ulSchedTimeInterval: target time interval for proactive UL resource assignment for each connected user
• Default value: 4 ; unit is ms; value range: 0.2…1000; stepsize = 0.2.
Recommendation : Activate the proactive scheduling (actProactUlScheduling = TRUE). Consider deactivate it when the
live network becomes loaded. Choose a proactive scheduling interval consistent with your need: use a medium interval
for live networks (ulSchedTimeInterval = 20ms), use small interval for special events requiring low latency (e.g gaming).
97
© Nokia 2019
Nokia internal use
Latency : CSI Report Periodicity parameters
Description
The CSI report periodicity:
• also drives the Scheduling Request opportunities (a unic parameter for both : csiReportPeriodicity). So a low value
improves the Latency for network without proactive scheduling.
• it is directly related with the capacity as the CSI reports are sent over PUCCH, the ‘dimensioning’ channel in term of
capacity. So a high value improves the capacity, a low value significantly degrades the capacity.
• a high value may have side effects on the downlink throughput stability by changing the behavior of Link Adaptation
and Beam tracking as reports from UE come less often
Recommendation : Set the CSI report periodicity to its maximum value if you need capacity
(csiReportPeriodicity = slot320). Set it to an intermediate value if you don’t need maximal capacity.
98
© Nokia 2019
Nokia internal use
csiReportPeriodicity : Latency versus Capacity
For non-pre-scheduled Ues (actProactUlScheduling = False), the latency mainly depends on the occasions for Scheduling
Requests (SR) (csiReportPeriodicity).
Lab test : example for Ping RTT (ms) in cmW, with csiReportPeriodicity =
slots320
There is big variation from one ping to the other:
•
short RTT if it happens to be close to the SR occasion,
•
large RTT if the SR occasion has been missed and UE is waiting for the next one.
The more frequent are the SR occasions, the best is the latency. But the capacity is dramatically reduced.
Field test - Ping (active state, without pre-scheduling) – cmW
.
.
csiReportPeriodicity
slots40
slots80
slots320
50 ping 32 bytes (min/max/avg) (ms)
Min 24 ms
Max 54 ms
Avg 37 ms
Min 29 ms
Max 71 ms
Avg 46 ms
Min 31 ms
Max 179 ms
Avg 108 ms
5
11
44
#RRC connected UEs
Field test : example for Ping RTT (ms) in cmW as a function of
SR periodicity
The capacity figures are extracted from the capacity tool located here,
considering the following configuration :
Frame structure 5GC001116_3ms
numberOfTransmittedSsBlocks = 8
ssBurstSetPeriod [ms] = 20ms
prachConfigurationIndex = 98
csirsTrackingPeriod [ms] = 80
Those figures should be taken for illustration only; use the ones
corresponding to your configuration.
99
© Nokia 2019
Nokia internal use
Proactive scheduling : Latency versus uplink throughput (1/2)
The Proactive Scheduling (actProactUlScheduling = True) significantely improves the latency
Lab test – cmW – PING – mono-UE – csiReportPeriodicity = slots320
Scenario
SINGLE_UE
Pro-Active Scheduler TRUE
ulSchedTimeInterval
Pro-Active Scheduler FALSE
Avg 93 ms
4ms
10ms
20ms
Min 8 ms
Max 23 ms
Avg 13 ms
Min 8 ms
Max 26 ms
Avg 15 ms
Min 8 ms
Max 43 ms
Avg 20 ms
Lab test – cmW – PING
Pro-Active Scheduler FALSE
Pro-Active Scheduler TRUE
Scenario
Avg [ms]
Min [ms]
Max [ms]
Avg [ms]
Min [ms]
Max [ms]
SINGLE_UE
74
22
153
34
12
193
1+8connected
79
20
167
43
13
115
1+8traffic
106
18
480
61
13
139
100
© Nokia 2019
Nokia internal use
Lab test : example for Ping RTT in cmW, single UE, as a
function of proactive scheduling Time Interval
Lab test : example for Ping RTT in cmW, without and
with proactive scheduling.
Single UE, or single UE + 8 UEs connected inactive, or single
UE + 8 Ues connected active : the proactive scheduling
improves the latency in all cases.
Proactive scheduling : Latency versus uplink throughput (2/2)
The Proactive Scheduling (actProactUlScheduling = True) does not impact the multi-UE user
throughput, at the condition all UEs are actively transmitting.
Lab test – cmW – UL Throughput
UL UDP
Pro-active scheduling FALSE
Pro-active scheduling TRUE
Single UE (Mbps)
35
36
Multi UE (1+ 8 traffic) (Mbps)
3.5
4.3
If some UEs are connected but not doing traffic, they consume Uplink slots as they are mandated to send useless packets
(padding), impacting the uplink throughput of those UEs doing effectively traffic.
.
.
Example of the impact of the uplink throughput. Field test. mmW
The active UE’s uplink throughput is degraded when one inactive UE
remains connected and consumes ul data slots each time it is
proactively scheduled.
101
© Nokia 2019
Nokia internal use
Recommendations
The following recommendations are proposed for 3 different use cases :
Default
High Traffic
Load
Full name
NRCELLGRP:actProac
tUlScheduling
Activate UL
proactive scheduling
1:True; 0:false
0 (false)
1 (true)
False
True
NRCELLGRP:ulSchedT
imeInterval
UL scheduling time
interval
0.2...1000, step 0.2 [ms]
4
20 ms
n/a
4
NRCELLGRP:csiRepor
tPeriodicity
CSI Reporting
Periodicity
Slots20, slots40, slots80,
slots160, slots320
slots320
slots320
slots320
slots40
NRBTS.actInactDetN
SAUe
Activate inactivity
detection for NSA
UE
1:True; 0:false
0 (false)
1 (true)
true
false
NRBTS.nsaInactivityTi
mer
Non Stand Alone
inactivity timer
1… 7200 [s]
10 s
10 s
5s
n/a
102
Range and step
High
Throughput
Abbreviated name
© Nokia 2019
Nokia internal use
Low Latency
Latency : parameters
List
103 © Nokia 2019
Nokia internal use
Latency : KPIs
Comment
In 5G19, there is no counter (and so no KPI) to measure the latency of each PDCP packet:
- starting when the gNB receives the PDCP packet from S1U
- ending when the PDCP packet is fully sent over the air with success (HARQ ACK)
➢
The reason is that it would cost a lot in term of process time.
The KPIs in next slide provide the latency (duration) for PDCP packets received by gNB from S1U until first segment ready
to be sent over the air by MAC gNB part or by MAC eNB part.
104 © Nokia 2019
Nokia internal use
LATENCY KPIs INSIDE gNB / eNB
KPI ID
NR_427a
NR_428a
NR_429a
NR_70a
NR_71a
NR_5050a
NR_5051a
KPI NAME
5G Average DL estimated delivery delay over X2-U until packet to be transmitted on air
5G Average DL estimated latency over X2-U until High RLC
5G Average DL estimated latency over X2-U from High RLC until packet transmitted on air
5G NSA average PDCP SDU delay in DL
5G NSA average PDCP SDU delay in UL
5G Average estimated F1 round trip delay betw een CU and MAC DU
5G Average estimated X2 round trip delay betw een CU and MAC eNB
105 © Nokia 2019
Nokia internal use
UNIT
ms
ms
ms
µs
µs
ms
ms
Scope
Accessibility/Ret
ainability
Usage :
Throughput
Mobility
4G-5G
interactions
Design Specific
Parameters
106 © Nokia 2019
Nokia internal use
Usage : Packet
Delay
Mobility
Features support
In 5G19, only intra-gNB inter-sector mobility is supported through feature “5GC000572 Intra-Frequency
Intra gNB mobility (NSA option 3x)”
This feature supports a network based intra-frequency change of the serving PSCell within a gNB (the
same CU, between different DUs)
SgNB triggers and manages PSCell change
SgNB configures Intra-frequency measurements on UE by tunneling RRC signaling via MeNB over X2 AP
messages
A3/A5 event is triggered based on SS-RSRP/SS-RSRQ measurements .
The neighbor relations are operator configurable per PSCell.
EPC
SgNB
DU1
CU#1
DU2
107
© Nokia 2019
Nokia internal use
DC
UE
Mobility scenarios
SgNB-DU#2.2
Inter-DU HO
The same CU, different DUs
SgNB-DU#1.1  sGNB-DU#1.2
SgNB-DU#2.1
Inter-CU HO
The same MeNB, different SgNB-CU,
different SgNB-DUs
SgNB-DU#1.2  sGNB-DU#2.1
SgNB-CU#2
X2
(to MeNB#1)
SgNB-DU#1.2
Intra-MeNB LTE handover
without en-gNB change
SgNB-CU#1
SgNB-DU#1.1
S1-U
X2
S1-U
S1-C
MeNB#1
The same MeNB (but different LTE
cells),the same SgNB-CU and SgNB-DU
DC UE
Inter-MeNB LTE handover
without en-gNB change
different MeNB,the same SgNB-CU
and SgNB-DU
EPC
108
© Nokia 2019
DU equivalent to sector/cell
CU eq to gNB in classical conf
Nokia Internal Use
Nokia internal use
Intra-frequency mobility
Feature overview
Intra-Frequency Intra gNB mobility (NSA option 3x)
MeNB
This feature supports a network based intrafrequency change of the serving PSCell within a
gNB (the same CU, between different DUs)
• SgNB triggers and manages PSCell change
EPC
X2-U
X2-C
SgNB
DC UE
DU1
• A3/A5* event is triggered based on SS-RSRP/SS-RSRQ
measurements (combined decision supported as well)
CU#1
• The neighbor relations are operator configurable per
PSCell
DU2
Note: only intra-CU inter-DU mobility is covered within the
scope of this feature
109
© Nokia 2019
• SgNB configures Intra-frequency measurements on UE
by tunneling RRC signaling via MeNB over X2 AP
messages (or directly via SRB3)
*)- Event A3: "Neighbour becomes offset better than PSCell"
Event A5: "PSCell becomes worse than „threshold1” and neighbour becomes
better than „threshold2”
Nokia Internal Use
Nokia internal use
Mobility Measurements
Mobility measurements are based on RSRP/RSRQ like in LTE. However, there is no Cell Reference Signal
(CRS) like in LTE, but several reference signals (SS, CSI, SRS) with different measurements.
In 5G19, RSRP, RSRQ and SINR are based based on Synchronisation Signal (SS) only
Category
Physical Signal for Measurement
Synchronization Signal Reference Signal Received Power (SS-RSRP)
RSRP
CSI reference signal received power (CSI-RSRP) (not supported in 5G19)
SRS reference signal received power (SRS-RSRP) (not supported in 5G19)
RSRQ
SINR
110
Synchronization Signal Reference Signal Received Quality (SS-RSRQ)
CSI reference signal received quality (CSI-RSRQ) (not supported in 5G19)
Synchronization Signal Signal-To-Noise and Interference Ratio (SS-SINR)
CSI signal-to-noise and interference ratio (CSI-SINR) (not supported in 5G19)
© Nokia 2019
Nokia internal use
Mobility Measurements
RSRP
SS-RSRP is defined as the linear average over the power contributions (in [W]) of the resource elements that carry
Secondary Synchronization Signal (SSS).
Reference points:
• For frequency range below 6 GHz - antenna connector of the UE
• For frequency range above 6 GHz - SS-RSRP is measured based on the combined signal from antenna elements
corresponding to a given receiver branch
239
SS-RSRP mapping:
111
Reported
Value [dBm]
0
RSRP < -156
1
-156  RSRP < -155
…
…
126
-31  RSRP < -30
127
-30  RSRP
frequency
192
182
Subcarrier
number
56
47
0
© Nokia 2019
Nokia internal use
P
B
C
H
P P S P
S B S B
S C S C
H
H
P
B
C
H
0 1 2
3
OFDM
symbol time
number
127 REs in total
Mobility Measurements
RSRQ
SS-RSRQ is specified as the ratio:
SS-RSRQ mapping
N×
SS−RSRP
NR carrier RSSI
Where: N - the number of resource blocks in the NR carrier RSSI measurement
bandwidth.
NR carrier Received Signal Strength Indicator (NR carrier RSSI), comprises the linear
average of the total received power (in [W]) observed only in certain OFDM symbols of
measurement time resource(s) (confined within SS/PBCH Block (SSB) Measurement Time
Configuration (SMTC) window duration), in the measurement bandwidth, over N number of
resource blocks from all sources (including co-channel serving and non-serving cells, adjacent
channel interference, thermal noise etc.)
Reported
Value [dB]
0
RSRQ < -34
1
-34  RSRQ < -33.5
…
…
126
28.5  RSRQ < 29
127
29  RSRQ
OFDM symbol
indication
SS-RSSIMeasurementSymbolC
onfig
Symbol indexes
Reference points:
0
{0,1}
• For frequency range below 6 GHz - antenna connector of the UE
1
{0,1,2,3,4,5,6,7,8,9,10,11}
• For frequency range above 6 GHz - SS-RSRQ is measured based on the combined signal
from antenna elements corresponding to a given receiver branch
2
{0,1,2,3,4,5}
3
{0,1,2,3,4,5,6,7}
For a half-frame with SS/PBCH blocks the NR Carrier RSSI is measured from OFDM
symbols of the indicated slots and the OFDM symbols are given in table
112
© Nokia 2019
Nokia internal use
Mobility Measurements
SINR
SS signal-to-noise and interference ratio (SS-SINR), is defined as the linear average over the power contribution (in [W])
of the resource elements carrying secondary synchronisation signals divided by the linear average of the noise and
interference power contribution (in [W]) over the resource elements carrying secondary synchronisation signals within the
same frequency bandwidth. The measurement time resource(s) for SS-SINR are confined within SS/PBCH Block
Measurement Time Configuration (SMTC) window duration.
If higher-layers indicate certain SS/PBCH blocks for performing SS-SINR measurements, then SS-SINR is measured only
from the indicated set of SS/PBCH block(s).
Reference points:
• For frequency range below 6 GHz - antenna connector of the UE
• For frequency range above 6 GHz - SS-RSRQ is measured based on the combined signal from antenna elements
corresponding to a given receiver branch
113
© Nokia 2019
Nokia internal use
Measurement configuration procedure
MeNB
UE
When 5GC000572 Intra-Frequency Intra gNB mobility is
activated (NRBTS/actIntraFreqIntraGnbMobilityNSA = true) UE
measurement can be configured either during SgNB Addition
Preparation procedure (within the X2AP: SgNB Addition Request
Acknowledge message) or PSCell change procedure (within
X2AP: SgNB Modification Required)
• It is performed via RRC: RRC Connection Reconfiguration message
containing a measConfig IE
• Measurement object is serving carrier frequency
• A3 or/and A5 event based measurement can be configured on UE
(activated via NRCELL/a3MeasEnabled, NRCELL/a5MeasEnabled
respectively)
• UE confirms to MeNB via RRC: RRC Connection Reconfiguration
Complete that measurement configuration is applied – delivered to
SgNB inside the X2AP: SgNB Reconfiguration Complete message
114
© Nokia 2019
Nokia Internal Use
Nokia internal use
SgNB
X2AP:SgNB Addition
Request
X2AP:SgNB Addition Request
Acknowledge
RRC:RRC Connection
Reconfiguration
RRC:RRC Connection
Reconfiguration Complete
X2AP:SgNB Reconfiguration
Complete
Measurement configuration – content of reportConfigNR IE
Partial view on important parameters for optimisation
IE/Group Name
reportType
>eventTriggered
>> eventId
>>> eventA3
>>>> a3-Offset
>>>>> rsrp
>>>>> rsrq
>>>> reportOnLeave
>>>> hysteresis
>>>> timeToTrigger
>>> eventA5
>>>> a5-Threshold1
>>>>> rsrp
>>>>> rsrq
>>>> a5-Threshold2
>>>>> rsrp
>>>>> rsrq
115
© Nokia 2019
Setup
IE/Group Name
>>>> reportOnLeave
Hardcoded as eventTriggered
>>>> hysteresis
NRCELL/a3MeasEnabled
>>>> timeToTrigger
NRCELL/a3OffsetSsbRsrp
NRCELL/a3OffsetSsbRsrq
>> rsType
>> reportInterval
>> reportAmount
>> reportQuantityCell
>>> rsrp
>>> rsrq
>>> sinr
>> maxReportCells
>> reportQuantityRsIndexes
>>> rsrp
>>> rsrq
>>> sinr
>> maxNrofIndexesToReport
>> includeBeamMeasurements
Hardcoded to TRUE
NRCELL/a3HysteresisSsbRsrp
NRCELL/a3HysteresisSsbRsrq
NRCELL/a3TimeToTriggerSsbRsrp
NRCELL/a3TimeToTriggerSsbRsrq
NRCELL/a5MeasEnabled
NRCELL/a5Threshold1SsbRsrp
NRCELL/a5Threshold1SsbRsrq
NRCELL/a5Threshold2SsbRsrp
NRCELL/a5Threshold2SsbRsrq
Nokia Internal Use
Nokia internal use
Setup
Hardcoded to TRUE
NRCELL/a5HysteresisSsbRsrp
NRCELL/a5HysteresisSsbRsrq
NRCELL/a5TimeToTriggerSsbRsrp
NRCELL/a5TimeToTriggerSsbRsrq
Hardcoded to ssb
Hardcoded to ms240
Hardcoded to r1
Hardcoded to TRUE
Hardcoded to TRUE
Hardcoded to TRUE
Hardcoded to 8
Hardcoded to TRUE
Hardcoded to TRUE
Hardcoded to TRUE
Hardcoded to 8
Hardcoded to TRUE
Measurement configuration - content of measConfig IE
Partial view on important parameters for optimisation
NR RRC: RRCReconfiguration -> measConfig IE A3 and/or A5
IE/Group Name
measConfig
> measObjectToAddModList
> reportConfigToAddModList
> measIdToAddModList
> s-MeasureConfig
>> ssb-rsrp
> quantityConfig
• quantityConfig - specifies filter coefficient value for RS type SS/PBCH blocks and
measurement quantities RSRP/RSRQ. This value is defined within FilterCoefficient
IE via:
− NRCELL/filterCoeffSsbRsrp for RSRP
− NRCELL/filterCoeffSsbRsrq for RSRQ
IE/Group Name
quantityConfigNR-list
> QuantityConfigNR
>> quantityConfigCell
>>> QuantityConfigRS
>>>> ssb-FilterConfig
>>>>> FilterConfig
>>>>>> FilterCoefficient
116
© Nokia 2019
Nokia Internal Use
Nokia internal use
Mobility events
Handovers between 5G cells are possible based on event A3 or event A5 radio conditions measured in
RSRP/RSRQ domain
Which measurement option is effectively in use depends not only on configured thresholds (RSRP/RSRQ
based) but also on the setting of two parameters:
• NRCELL:a3MeasEnabled = none (0), rsrp (1), rsrq (2), rsrpAndRsrq (3), rsrpCombined (4),
rsrqCombined (5)
• NRCELL:a5MeasEnabled = none (0), rsrp (1), rsrq (2), rsrpAndRsrq (3), rsrpCombined (4),
rsrqCombined (5)
It is recommended to configure only event A3 for intra-frequency handover, in order to trigger handover
as soon as a neighbor cell becomes better than serving cell. Event A5 is not useful for intra-frequency
handover, so not recommended for activation
117
© Nokia 2019
Nokia internal use
Mobility events
For both parameters, possible values mean:
•
none (0) even the thresholds for RSRP and RSRQ are configured in SgNB database no measurement configuration is provided to the UE
terminal
•
rsrp (1) even the thresholds for RSRP and RSRQ are configured in SgNB database, only RSRP based measurement configuration is
provided to the UE terminal; HO preparation phase is triggered after receiving Measurement Report for this RSRP based event
•
rsrq (2) even the thresholds for RSRP and RSRQ are configured in SgNB database, only RSRQ based measurement configuration is
provided to the UE terminal; HO preparation phase is triggered after receiving Measurement Report for this RSRQ based event
rsrpAndRsrq (3) thresholds for RSRP and RSRQ are configured and both measurement configuration are provided to the UE terminal as
separate measurements; HO preparation phase is triggered after receiving Measurement Report for this event either RSRP or RSRQ
based
•
rsrpCombined (4) even the thresholds for RSRP and RSRQ are configured only RSRP based measurement configuration is provided to
the UE terminal; after detection by the UE terminal radio conditions for event A3/A5 in RSRP domain and reporting it by Measurement
Report, the SgNB takes into account also reported RSRQ levels of serving and target cell; HO preparation phase may be triggered if
also reported RSRQ levels meet the radio conditions for event A3/A5 defined in SgNB database by RSRQ related thresholds.
•
rsrqCombined (5) even the thresholds for RSRP and RSRQ are configured only RSRQ based measurement configuration is provided to
the UE terminal; after detection by the UE terminal radio conditions for event A3/A5 in RSRQ domain and reporting it by Measurement
Report the SgNB takes into account also reported RSRP levels of serving and target cell; HO preparation phase may be triggered if also
reported RSRP levels meet the radio conditions for event A3/A5 defined in SgNB database by RSRP related thresholds.
It is recommended to set « rsrp » for intra-frequency handover, or « rsrpCombined » for loaded networks
118
© Nokia 2019
Nokia internal use
Handover trigger conditions
Handover based on A3 event RSRP
Intra-frequency better cell handover (event A3 based radio conditions) is triggered by RSRP measurement
NRCELL:a3MeasEnabled = 1 (RSRP) or 4 (RSRP combined)
RSRP
PSCell
(serving)
RSRP based Event A3
conditions met
RSRP
neighbor
RSRP combined means that RSRP quantity
is the dominating quantity, but RSRQ quantity
is also checked before PSCell change
decision
Event triggered when the following condition is met
during a3TimeToTriggerSsbRsrp:
NRCELL: a3HysteresisSsbRsrp
RSRPneigh > RSRPserv + a3OffsetSsbRsrp + a3HysteresisSsbRsrp
NRCELL:a3OffsetSsbRsrp
NRCELL:a3TimeToTriggerSsbRsrp
UE sends RRC:MeasurementReport for event
A3 (only one report is transmitted)
TimeToTrigger and Offset/Hysteresis need to be optimized according to radio environment : low values are good for fast
moving UEs but can create too many ping-pong HO.
119
© Nokia 2019
Nokia internal use
Handover trigger conditions
Handover based on A3 event RSRQ
Intra-frequency better cell handover (event A3 based radio conditions) is triggered by RSRQ measurement
NRCELL:a3MeasEnabled = 2 (RSRQ) or 5 (RSRQ combined)
RSRQ
PSCell
(serving)
RSRQ based Event A3
conditions met
RSRQ
neighbor
RSRQ combined means that RSRQ quantity
is the dominating quantity, but RSRP quantity
is also checked before PSCell change
decision
Event triggered when the following condition is met
during a3TimeToTriggerSsbRsrq:
NRCELL: a3HysteresisSsbRsrq
RSRQneigh > RSRQserv + a3OffsetSsbRsrq + a3HysteresisSsbRsrq
NRCELL:a3OffsetSsbRsrq
NRCELL:a3TimeToTriggerSsbRsrq
UE sends RRC:MeasurementReport for event
A3 (only one report is transmitted)
TimeToTrigger and Offset/Hysteresis need to be optimized according to radio environment : low values are good for fast
moving UEs but can create too many ping-pong HO
120
© Nokia 2019
Nokia internal use
Mobility parameters optimisation
In 5G19, as only intra-gNB mobility is supported, it is not really possible to perform fine tuning of
mobility parameters to get good handover succes rate, not too much ping-pong between cells and best
throughput measurements in drive tests.
First networks tend to use quite high values of a3OffsetSsbRsrp + a3HysteresisSsbRsrp in order to
delay handover. Current recommendations are proposed in table below :
Parameter name
Default
Reco
MRBTS.NRBTS.NRCELL.a3MeasEnabled
0
1
MRBTS.NRBTS.NRCELL.a3MeasSsbRsrp.a3HysteresisSsbRsrp
-
4
MRBTS.NRBTS.NRCELL.a3MeasSsbRsrp.a3OffsetSsbRsrp
-
8
MRBTS.NRBTS.NRCELL.a3MeasSsbRsrp.a3TimeToTriggerSsbRsrp
-
ms320
Note that a3HysteresisSsbRsrp and a3OffsetSsbRsrp are defined as signalled to the UE, so real value in dB is half of GUI
value (eg 8 means 4 dB)
More optimisation will be performed in 5G19A once inter-gNB mobility is supported.
121
© Nokia 2019
Nokia internal use
Neighbour Cell declaration
NRREL objects for 5G neighbor relations
Neighbor relations between 5G cells are using NRREL object class (MRBTS/NRBTS/NRCELL)
•
The neighbor relations from a given 5G cell are possible only for cells for which the NRREL objects are defined in
the NRCELL object relevant to the source cell
•
Up to 256 NRREL objects can be created per 5G NRCELL object (1 radio cell – can be multiple NRCELLs per DU)
MRBTS/NRBTS/NRCELL/NRREL/nrRelId
MRBTS/NRBTS/NRCELL/NRREL/nrRelId
MRBTS/NRBTS/NRCELL/NRREL/physCellId
MRBTS/NRBTS/NRCELL/NRREL/nrRelId
MRBTS/NRBTS/NRCELL/NRREL/physCellId
MRBTS/NRBTS/NRCELL/NRREL/nrarfcn
MRBTS/NRBTS/NRCELL/NRREL/nrRelId
MRBTS/NRBTS/NRCELL/NRREL/physCellId
MRBTS/NRBTS/NRCELL/NRREL/nrarfcn
NRCELL:
MRBTS/NRBTS/NRCELL/NRREL/nrarfcn
MRBTS/NRBTS/NRCELL/NRREL/physCellId
MRBTS/NRBTS/NRCELL/NRREL/gNbId
source cell
MRBTS/NRBTS/NRCELL/NRREL/nrarfcn
MRBTS/NRBTS/NRCELL/NRREL/gNbId
MRBTS/NRBTS/NRCELL/NRREL/gNbIdLength
for PSCell
MRBTS/NRBTS/NRCELL/NRREL/gNbId
MRBTS/NRBTS/NRCELL/NRREL/gNbIdLength
MRBTS/NRBTS/NRCELL/NRREL/lcrId
change
MRBTS/NRBTS/NRCELL/NRREL/gNbIdLength
MRBTS/NRBTS/NRCELL/NRREL/lcrId
MRBTS/NRBTS/NRCELL/NRREL/fiveGsTac
MRBTS/NRBTS/NRCELL/NRREL/gNbId
MRBTS/NRBTS/NRCELL/NRREL/lcrId
MRBTS/NRBTS/NRCELL/NRREL/fiveGsTac
MRBTS/NRBTS/NRCELL/NRREL/gNbIdLength
MRBTS/NRBTS/NRCELL/NRREL/fiveGsTac
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn
Up to
MRBTS/NRBTS/NRCELL/NRREL/lcrId
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mcc
256
MRBTS/NRBTS/NRCELL/NRREL/fiveGsTac
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mcc
NRREL MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mnc
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mcc
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mnc
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mncLength
per
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mnc
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mncLength
NRCELL
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mncLength
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mcc
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrpOffset
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mnc
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrpOffset
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrqOffset
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrpOffset
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrqOffset
MRBTS/NRBTS/NRCELL/NRREL/gnbPlmn::mncLength
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrqOffset
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrpOffset
MRBTS/NRBTS/NRCELL/NRREL/cellIndividualSsbRsrqOffset
122
© Nokia 2019
Nokia Internal Use
Nokia internal use
ID of the
neighbor
relationship
PCI + ARFCN
info for the
neighbor cell
gNB id of the
neighbor cell
PLMN of the
neighbor cell
Indvidual
offsets of the
neighbor cell
for A3 event
NRREL
objects are
used for all
kinds of 5G5G NSA
neighbor
relationships:
5GC000572,
5GC000573,
5GC001094
Neighbour Cell declaration
5G Network planning for NSA architecture in 5G19
Single 5G cell can have relations toward up to 256 cells.
Each CU can have up to 1024 cells configured.
up to
relations to 5G cells allowed
Currently no dedicated tool or application available
for 5G - 5G relations planning
up to
Manual databuild allowed with 5G Offline
Configuration tool
123
© Nokia 2019
Nokia Internal Use
Nokia internal use
256
1024
cells allowed per CU
Neighbour Cell declaration
5G Network planning for NSA architecture in 5G19
NRBTS-1
(CU-VNF)
All 5G cells within at least 2x cell
range (overlapping coverage) should
be considered as candidate for
neighbour relations planning rules
NRDU-4
NRCELL-4
NRDU-3
NRCELL-3
© Nokia 2019
NRDU-8
NRCELL-8
NRDU-9
NRCELL-9
NRDU-10
NRCELL-10
Cell 2 range
All cells located within the 700m
distance to be considered as
neighbour candidate
124
NRDU-6
NRCELL-6
NRDU-5
NRCELL-5
5G Link budget tool should be used
for calculation of neighbouring cells
candidate.
Example:
- 350m – 5G cell 1 coverage
- 350m – 5G cell 2 coverage
NRDU-7
NRCELL-7
Cell 1 range
5G – 5G ISD (Inter Site Distance)
cells with overlapping coverage as candidate
Cell is candidate for neighbour if located within the ISD
where ISD = 2 x 5G cell range
Nokia Internal Use
Nokia internal use
Mobility Parameters
Domain
Mobility
Sub-domain
Parameter Name
Abbreviation
Mobility
Handover Success Rate a3 Measurement Configuration a3MeasEnabled
Enabled
Handover Success Rate a3 Hysteresis Ssb Rsrp
a3HysteresisSsbRsrp
Mobility
Handover Success Rate
Mobility
Handover Success Rate
Mobility
Handover Success Rate
Mobility
Handover Success Rate
Mobility
Handover Success Rate
Mobility
Handover Success Rate
Mobility
Handover Success Rate
Mobility
Handover Success Rate
Mobility
Mobility
Mobility
Handover Success Rate
Handover Success Rate
Handover Success Rate
Mobility
Handover Success Rate
125
MIND Reference
MRBTS.NRBTS.NRCELL.a3MeasEnabled
MRBTS.NRBTS.NRCELL.a3MeasSsbRsrp.a3Hyst
eresisSsbRsrp
a3 Offset Ssb Rsrp
a3OffsetSsbRsrp
MRBTS.NRBTS.NRCELL.a3MeasSsbRsrp.a3Offse
tSsbRsrp
a3 Time To Trigger Ssb Rsrp
a3TimeToTriggerSsbRsrp MRBTS.NRBTS.NRCELL.a3MeasSsbRsrp.a3Time
ToTriggerSsbRsrp
a3 Hysteresis Ssb Rsrq
a3HysteresisSsbRsrq
MRBTS.NRBTS.NRCELL.a3MeasSsbRsrq.a3Hyst
eresisSsbRsrq
a3 Offset Ssb Rsrq
a3OffsetSsbRsrq
MRBTS.NRBTS.NRCELL.a3MeasSsbRsrq.a3Offse
tSsbRsrq
a3 Time To Trigger Ssb Rsrq
a3TimeToTriggerSsbRsrq MRBTS.NRBTS.NRCELL.a3MeasSsbRsrq.a3Time
ToTriggerSsbRsrq
a5 Measurement Configuration a5MeasEnabled
MRBTS.NRBTS.NRCELL.a5MeasEnabled
Enabled
Cell Individual SSB RSRP Offset cellIndividualSsbRsrpOff MRBTS.NRBTS.NRCELL.cellIndividualSsbRsrpOf
set
fset
Cell Individual SSB RSRQ Offset cellIndividualSsbRsrqOff MRBTS.NRBTS.NRCELL.cellIndividualSsbRsrqOf
set
fset
Filter Coefficient Ssb Rsrp
filterCoeffSsbRsrp
MRBTS.NRBTS.NRCELL.filterCoeffSsbRsrp
Filter Coefficient Ssb Rsrq
filterCoeffSsbRsrq
MRBTS.NRBTS.NRCELL.filterCoeffSsbRsrq
Activate intra-frequency intra- actIntraFreqIntraGnbMo MRBTS.NRBTS.actIntraFreqIntraGnbMobilityN
gNB mobility NSA
bilityNSA
SA
Activate data duplication for
actDataDuplicationForM MRBTS.NRBTS.actDataDuplicationForMobility
mobility
obility
© Nokia 2019
Nokia internal use
Default
value
0
-
reco if not list of use cases
same as
in MIND
default
1
to be added
(GMC19)
4
to be added
(GMC19)
8
to be added
(GMC19)
ms320
to be added
(GMC19)
0
0dB
0dB
fc4
fc4
FALSE
TRUE
FALSE
TRUE
to be added
(GMC19)
to be added
(GMC19)
Mobility Counters
5GC000572 Intra-Frequency Intra gNB mobility (NSA option 3x)
ID
Network element abbreviation
Name
Updated
M55120C00001 INT_FR_PSCEL_CHA_ATT
The number of intra gNB intra
frequency PSCell change
attempts
X2AP: SgNB Modification Required
message is sent to MeNB with the SCG
Change Indication set as
"PSCellChange"
M55120C00002 INT_FR_PSCEL_CHA_FAIL_TDC_EXP
The number of intra gNB intra
frequency PSCell change failures
due to TDCoverall timer expiry
When the TDCoverall timer has
elapsed before gNB receives the
X2AP: SgNB Modification Confirm
message
M55120C00003 INT_FR_PSCEL_CHA_FAIL_MENB_REF
The number of intra gNB intra
frequency PSCell change failures
due to MeNB refusal
When MeNB replies to X2AP: SgNB
Modification Required message with
the X2AP: SgNB Modification Refuse
message
M55120C00004 INT_FR_PSCEL_CHA_FAIL_RES_ALLO
The number of intra gNB intra
frequency PSCell change failures
due to target cell resource
allocation failure
When AC fails for PSCell change
126
© Nokia 2019
Nokia internal use
MOBILITY KPIs
KPI ID
NR_5043a
NR_284a
NR_5040a
NR_5041a
NR_5042a
KPI NAME
5G Intra gNB intra frequency PSCell change total failure ratio
5G Average duration of executed intra gNB intra frequency PSCell changes
5G Intra gNB intra frequency PSCell change preparation attempts
5G Intra gNB intra frequency PSCell change preparation success ratio
5G Intra gNB intra frequency PSCell change total Success ratio
127 © Nokia 2019
Nokia internal use
UNIT
%
ms
No unit
%
%
Scope
Accessibility/Ret
ainability
Usage :
Throughput
Mobility
4G-5G
interactions
Design Specific
Parameters
128 © Nokia 2019
Nokia internal use
Usage : Packet
Delay
4G-5G Interactions : Overview
Sub-domains
The purpose of this section is to present:
• The parameters, both 4G and 5G, which need to be consistently set between the two technologies
• The most important parameters for the NSA mode 3x operations
The main objective is to ease the configuration of the NSA mode 3x and to smoothe the introduction of the 5G in the
network.
Parameter wise, the main interactions between 4G and 5G, in NSA mode 3x operations, can be split into the following
sub-domains:
•
•
•
•
X2 Setup & Management
Dual Connectivity
UE Inactivity Handling
Radio Admission Control
The coming slides will detail the parameters involved in 4G-5G interactions in each of these sub-domains.
129 © Nokia 2019
Nokia internal use
4G-5G Interactions : X2 Setup & Management
Related Features
On the 4G side:
• Feature « LTE4087 - X2 interface with NR gNB » delivers support by eNB of X2 link to NR en-gNB (pre-requisite for the
SGW
support of EN-DC).
•
Only X2(gNB) manually configured by operator in eNB, i.e. not by ANR, are supported
in LTE4087.
MME
S1U
(legacy)
On the 5G side:
S1C
(legacy)
• Feature « 5GC000474 - X2 Management for NSA Mode 3x Operation » is
the equivalent 5G feature for LTE4087 and introduces the establishment and
X2-C X2-U
maintenance of X2-C interface between a 5G gNB and an LTE NodeB
LTE
(only the support of X2-C is needed for NSA 3x operation).
NodeB
• Feature « 5GC000577 - TRS Support of NSA Interfaces X2 and S1-U
over Ipv4 Ipv6 », which introduces the S1-U, X2-U, X2-C interfaces
over IPv4/IPv6 for the 5G gNB.
RAC: Radio Access Cloud; CU
RAU: Radio Access Unit ; DU
RU: Radio Unit
130 © Nokia 2019
Nokia internal use
S1U
5G
gNodeB
5G RAC
F1
5G RAU
5G RU
4G-5G Interactions : X2 Setup & Management
4G Parameters Description
X2 connection between eNB and en-gNB is configured via LNADJGNB MOC instance in the eNB, since the EN-DC X2
SETUP is always triggered by the eNB:
• Up to 32 LNADJGNB object instances
• To set up the X2 connection, it is necessary to provide valid IP address, cPlaneIpAddr, which corresponds to the X2
CP (i.e. backhaul of CP-IF VNF) IP address in the gNB: MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV4/localIpAddr or
MRBTS/TNLSVC/TNL/IPNO/IPIF/IPADDRESSV6/localIpAddr (depending if IPv4 or IPv6 is used in the gNB).
o IP address must be unique amongst LNADJGNB
• To have the link operational, LNADJGNB MOC must be set to administrativeState = ‘unlocked’
• All other parameters under LNADJGNB MOC are not modifiable:
o adjGnbIdLength, adjGnbId, mncLength, mnc, mcc are automatically retrieved from the EN-DC X2 SETUP RESPONSE message from gNB
o x2ToGnbLinkStatus is automatically changed from ‘unavailable’ to ‘available’ status as soon as the X2 is established
en-gNB
eNB
X2 SETUP REQUEST
X2 SETUP RESPONSE
The eNB raises an alarm if there are MRBTS/LNBTS/maxX2gNBRetry consecutive unsuccessful X2 establishment
attempts towards the en-gNB.
131 © Nokia 2019
Nokia internal use
4G-5G Interactions : X2 Setup & Management
5G Parameters Description (1/3)
enDcX2SetupReqTmr timer specifies the amount of time a gNB should wait
for an X2AP:EN-DC X2 SETUP REQUEST message from the LTE eNB after the
SCTP association is established. The gNB stops the timer (if started and not
expired) when the first X2 message is received.
shutdownNoX2TrafficTmr timer is started when there is no more traffic on
the X2 link (no gNB UE X2AP ID allocated and no X2-C message), i.e.:
o when the last X2-C message is sent and there is no more gNB UE X2AP ID
allocated for the X2-C link
o when the last gNB UE X2AP ID for an X2C link is deleted
This timer shall also be started when EN-DC X2 Setup Request message is not received (at enDcX2SetupReqTmr expiry).
This timer is stopped when at least one gNB UE X2AP ID is allocated for the neighboring LTE eNB.
At timer expiry, the SCTP association is shutdown to autonomously close the X2-C link. Value 0 means “no shutdown”.
x2LinkReestabTmr timer (managed per LTEENB instance) specifies the amount of time the gNB should wait for an X2
link reestablishment before removing the associated LTEENB instance. The timer is started:
o at gNB startup, as an X2 link reestablishment associated to an LTEENB object instance is being attempted
o at an LTEENB object instance unlock
o when an SCTP association is no more available for an X2 link
At timer expiry, the gNB will delete the associated LTEENB object instance if it is not locked and without SCTP
association.
132 © Nokia 2019
Nokia internal use
4G-5G Interactions : X2 Setup & Management
5G Parameters Description (2/3)
x2LinkSupervisionTmr timer specifies the amount of time the gNB should wait before sending an alarm indicating there
is no X2-C link available. The timer is started when there is no X2-C link available (at gNB startup or when there is no
more X2-C link available). At timer expiry, the gNB raises a BASE STATION CONNECTIVITY PROBLEM fault alarm due to no
X2 link available. If the timer is set to value ‘0’, no timer is started and there is no X2-C link supervision.
The default NIDD value of this timer is 1min. However, since the value of enDcX2SetupReqTmr is 1min (namely 60s), the
default value of x2LinkSupervisionTmr could be higher, all the more that on the LTE eNB side, the supervision timer of
the establishment attempts for X2 links towards gNB is set typically to 255s:
− MRBTS/LNBTS/SCTP/maxTimeSctpSetup = 100 s
− MRBTS/LNBTS/x2SetupRspTmr = 5 s
− MRBTS/LNBTS/waitTimeEstCtrlX2Lnk = 150 s
133 © Nokia 2019
Nokia internal use
4G-5G Interactions : X2 Setup & Management
5G Parameters Description (3/3)
Note that on successful X2 link activation initiated by LTE eNB (i.e. upon successfully receiving the X2 SETUP REQUEST
message from the eNB and transmitting the X2 SETUP RESPONSE message to the same eNB), an instance of LTE eNB
object (MRBTS/NRBTS/LTEENB) is created/updated in the gNB with the information received in the X2 SETUP REQUEST
message. Therefore, the following NR parameters under LTEENB are not modifiable:
o eNodeBId, ipAddr, mncLength, mnc, mcc are automatically retrieved from the EN-DC X2 SETUP REQUEST message from the LTE eNB
o x2LinkStatus is automatically changed from ‘unavailable’ to ‘available’ status, once the X2 is established and up
Note also that parameter x2LinkLock, under the same LTEENB instance, allows the customer to lock the X2-C link from a
specific LTE eNB (in that case, parameter x2LinkStatus will be automatically updated to ‘unavailable’). By default, this
parameter is set to ‘unlocked’ (0) at LTEENB creation, and it should be kept at the same value if the X2 link is to be used.
134 © Nokia 2019
Nokia internal use
4G-5G Interactions : X2 Setup & Management
Parameters List
Domain
Sub-domain
Parameter Name
EN-DC - LTE part Call Setup Success Rate Supervision timer to indicate no X2 link are
available
Abbreviation
x2LinkSupervisionTmr
MIND Reference
MRBTS.NRBTS.x2LinkSupervisionTmr
135 © Nokia 2019
Nokia internal use
Default value reco if not same
(GUI)
as default (GUI)
1
list of use cases in
MIND
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Related Features
On the 4G side:
• Feature « LTE4088 - LTE-NR Dual Connectivity Option 3X » provides the blind SgNB addition and SgNB release.
Feature « LTE4193 - Dynamic Trigger for LTE-NR DC Option 3X » provides traffic-based (effective with LTE5003) and
measurement-based SgNB addition.
On the 5G side:
• Feature « 5GC000475 - SgNB Addition and Release for NSA mode 3x operation » is the equivalent 5G feature for
LTE4088, and allows for Non-Standalone Dual Connectivity handling for a gNB connected via X2 to an eNB:
• MeNB can, for one non-GBR bearer (SCG split bearer), perform SgNB Addition, either without 5G carrier
measurement (requires LTE4088), or based on the 5G carrier measurements (requires LTE4193).
• Feature « 5GC000570 5G - LTE flow control at X2 » introduces the flow control over the X2 interface and the data
split in both UL and DL direction for the SCG split bearer (NSA mode Option 3x) between the 5G SgNB and LTE eNB.
• Feature « 5GC000630 - F1-U Interface » introduces:
• F1-U interface between gNB CU and gNB DU.
• 3GPP Flow control over F1-U interface.
• Nokia proprietary flow control over F1-U interface.
136 © Nokia 2019
Nokia internal use
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Parameters Description (1/6)
Once X2 link is established between eNB and gNB, Dual Connectivity (i.e. SgNB addition) may be triggered by the eNB only if
actLteNrDualConnectivity = ‘true’.
LTE4193 introduces the capability for eNB to trigger E-UTRA NR Dual connectivity (EN-DC) based on NR coverage. In that case,
actDynTrigLteNrDualConnectivity = must be set to ‘true’.
• For NR coverage detection, eNB uses B1 measurements of NR frequencies. UE triggers measurement report for B1 event when candidate
cell strength is above configured threshold: EN-DC procedure to perform SCG split bearer is then triggered. At EN-DC establishment, B1
measurement is de-configured.
•
•
MRBTS/LNBTS/NRDCDPR/dynTriggerLteNrDcConfList structure defines the cells of the LTE BTS for which dynamic B1 measurements are enabled: each LTE
cell is defined by its lcrId and the kind of measurement, method, to be used for this particular cell instance (only ‘coverageBased’ is supported until FL19B
at the earliest, with the availability of LTE5003).
If the functionality shall be applied to all cells of the eNB, lcrId shall be configured to value '-1’. In this case, the method value shall be identical for all cells.
• The NR cell used for SgNB addition is chosen as the strongest cell from B1 NR measurement report from the UE (MeNB sends all reported
NR cells corresponding to the selected SgNB, in the SgNB Addition Request). If SgNB addition procedure fails for the selected SgNB, MeNB
will re-try SgNB addition procedure for the next SgNB based on next strongest B1 NR measurement result until there is no more NR cells in
B1 NR measurement report.
• If actDynTrigLteNrDualConnectivity = ‘false’, EN-DC is triggered blindly immediately after Initial Context Setup, the target of the SgNB
addition being the LNRELGNBCELL instance pointed by MRBTS/LNBTS/LNCEL/defaultLnRelGnbCellId.
• If actDynTrigLteNrDualConnectivity = ‘True’, the eNB always configure measurement gap for the UE to perform its 5G measurements. An
optimisation is available to force eNB never configure the measurement gap during 5G measurements, this greatly help to maintain 4G
optimal throughput while the Ue is searching for a 5G cell (with measurement gap, 4G peak throughput may be reduced by e.g -20% (on
10MHz B/W) due to meas gap). This optimisation is activated by setting MRBTS.LNBTS.NR(D)CDPR.dataVolThreshold to 1. Note that this has
nothing to do with a data volume measurement activation, this is just a place where to activate a lately introduced optimisation. Do not
activate it if the Ues need measurement gap for its 5G measurement.
137 © Nokia 2019
Nokia internal use
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Parameters Description (2/6)
To enable measurement gaps for B1 measurements of NR, all target neighboring NR cells shall have the same overlapping SSB
timing configuration (ssbSubcarrierSpacing, ssbPeriodicity, ssbOffset, ssbDuration), and for capacity reason, SSB periodicity shall
be 20ms or less. SSB duration of 5 subframes is not supported.
MRBTS/LNBTS/NRDCDPR/nrDcMeasConfig holds all the parameters for B1 measurement configuration for NR Dual Connectivity:
• freqBandIndicatorNR: NR operating band.
• carrierFreqNrCell: NR carrier frequency for which this configuration is valid (this is the SSB-nrarfcn, corresponding to the GSCN
value configured on the 5G site).
• b1TriggerQuantity: Quantity (RSRP or RSRQ) the UE has to use for B1 measurement for EN-DC (default: RSRP).
• quantityConfigId: Index to MRBTS/LNBTS/NRDCDPR/nrDcQuantityConfig, where both RSRP and RSRQ filtering coefficients,
filterCoefficientRsrp & filterCoefficientRsrq, are defined.
• b1ThresholdNrRsrp: RSRP threshold of neighbor NR cell for triggering of B1 event.
• In lab, high value such as –100dBm can be used in order to impose ourselves and to ensure high quality level 5G.
• In customer field, much lower value such as –125dBm could be used to stretch the 5G coverage as much as possible.
• b1ThresholdNrRsrq: RSRQ threshold of neighbor NR cell for triggering of B1 event (N/A, if b1TriggerQuantity=RSRP)
• hysB1ThresholdRsrp: Hysteresis for RSRP triggered B1 event for NR measurements for dual connectivity (IE value x 2)
• hysB1ThresholdRsrq: Hysteresis for RSRQ triggered B1 event for NR measurements for dual connectivity (IE value x 2)
• b1TimeToTriggerRsrp: Time for which the specific criteria for the NR measurement RSRP triggered event B1 must be met in
order to trigger a measurement report.
• Since 5G candidates for SgNB Addition are relatively limited in 5G19, it is recommended to use the smallest value
possible in order to speed up 5G attach. Since value '0' may lead to unwanted effects, 40ms is recommended instead.
• b1TimeToTriggerRsrq: Time for which the specific criteria for the NR measurement RSRQ triggered event B1 must be met in
order to trigger a measurement report.
138 © Nokia 2019
Nokia internal use
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Parameters Description (3/6)
The SgNB Addition is performed towards one of the neighboring NR cells configured via LNRELGNBCELL MOC instance in
the eNB.
• MRBTS/LNBTS/LNCEL/LNRELGNBCELL/nrCellId corresponds to the MRBTS/NRBTS/NRCELL/nrCellIdentity in the
neighboring gNB (only present in WebUI, not in the SCF, since it is automatically computed), and is composed of two
elements:
•
•
•
•
•
The MRBTS/LNBTS/LNCEL/LNRELGNBCELL/gNbIdLength corresponds to MRBTS/NRBTS/gNbIdLength in the gNB
The gNbIdLength leftmost bits corresponds to MRBTS/NRBTS/nrBtsId
The (36 - gNbIdLength) rightmost bits corresponds to MRBTS/NRBTS/NRCELL/lcrId
For example, with gNbIdLength = 22 & nrBtsId = 1 & lcrId = 1, nrCellIdentity = 1 x 2^14 + 1 = 16385
More information can be found in 3GPP 38.413 and 38.300.
• Parameters mcc, mnclength, mnc in MRBTS/LNBTS/LNCEL/LNRELGNBCELL/nrCgiPlmnId, must have the same values
as for mcc, mnclength, mnc in MRBTS/NRBTS in the related neighbor NR-cell.
• MRBTS/LNBTS/LNCEL/LNRELGNBCELL/lteNrDualConnectAllowed controls if LTE-NR Dual Connectivity (EN-DC) is
allowed for the NR neighbor cell.
• MRBTS/LNBTS/LNCEL/LNRELGNBCELL/nrStatus is automatically set and Indicates the status of the NR neighbour
relation:
• unavailable: Indicates that the neighbour relation is not available for LTE-NR Dual Connectivity (EN-DC). E.g. because X2
links to gNB or neighbour cell information is not available.
• available: Indicates that the neighbour relation is available for LTE-NR Dual Connectivity (EN-DC), i.e. X2 link to gNB is
available and neighbor cell information is available.
139 © Nokia 2019
Nokia internal use
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Parameters Description (4/6)
After reception of S1AP: INITIAL CONTEXT SETUP REQUEST, eNB checks for each bearer if:
o QCI[x] with x=6..9 is used
o qciTab[x] has lteNrDualConnectSupport enabled
o qciTab[x] has nrPdcpProfIdx pointing to pdcpProf1001 (in order to restrict the EN-DC support to PDCP Sequence Number size of 18
bits: pdcpProf1001/snSizeDL = pdcpProf1001/snSizeUL = ‘18bit’, which is the only value supported for pdcpProf1001)
o NR Restriction is not contained within handover restriction list HRL
o UE EUTRA capabilities – including support of EN-DC (irat-ParametersNR-r15::en-DC-r15 == ‘supported’, which includes support for
18bits of PDCP SN Size) and NR support (in irat-ParametersNR-r15::supportedBandListNR-r15) – is contained in S1AP: INITIAL
CONTEXT SETUP REQUEST
o NR and EUTRA-NR capabilities are contained in S1AP: INITIAL CONTEXT SETUP REQUEST
If MRBTS/LNBTS/LNCEL/LNRELGNBCELL/nrStatus is ‘available’ and no other bearer has already been identified as EN-DC
eligible (since only one unique bearer can be EN-DC eligible, in 5G19, based on ARP priority) and all above checks are
positive, the corresponding bearer is EN-DC eligible and hence configured with NR PDCP.
For qciTab[x] with x=6..9, qciTab[x]/resType & qciTab[x]/rlcMode are hardcoded to ‘NON-GBR’ and ‘RLC_AM’,
respectively. However, if an operator-specific QCI is to be created, those two parameters shall also be set to ‘NON-GBR’
and ‘RLC_AM’ in order for the bearer to be eligible for EN-DC Dual Connectivity.
ARP priority level may optionally be configured:
• in MRBTS/LNBTS, for qciTab[x] (x=6...9, Operator), the parameters startArpEnDc and/or stopArpEnDc shall be
configured according to required ARP priority level support (default setting refer to all).
Note that if VoLTE is used (with QCI5 as IMS bearer), and if QCI5 is the first established default bearer, 4G
parameter actNonGbrServiceDiff needs to be set to 'true' in order to avoid the SgNB Addition attempt on QCI5, which
would
fail2019
and which would prevent the 5G attach since no other attempt will be performed on any other default bearer.
140
© Nokia
Nokia internal use
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
MeNB
SgNB
Parameters Description (5/6)
• This timer supervises the MeNB initiated SgNB addition procedure, the MeNB
initiated SgNB modification procedure, the MeNB initiated SgNB release
procedure as well as the reception of the SN STATUS TRANSFER following the
request from the SgNB to release the SGNB.
• During the MeNB initiated SgNB Addition procedure, this timer plays the role of
TDCPrep, as defined in 3GPP.
X2 connection existing
tLteNrDualConnectPrep
MRBTS/LNBTS/tLteNrDualConnectPrep specifies the maximum time that the MeNB
will wait for the en-gNB message in response to a message sent by the MeNB to
the en-gNB.
SGNB ADDITION REQUEST
SGNB ADDITION REQUEST ACKNOWLEDGE
X2 connection existing
SGNB RELEASE REQUEST
MRBTS/NRBTS/tDCoverall timer guards the SgNB against missing confirmation from the MeNB during the SgNB Addition
procedure or the SgNB Change procedure.
MRBTS/NRBTS/timerX2UeProcGuard timer guards X2-C UE related signaling.
MRBTS/NRBTS/x2EndMarkerTimer timer guards the SgNB against missing X2-U DL End Marker from the MeNB during
the SgNB Addition procedure (value ‘0’ indicates this timer is disabled).
141 © Nokia 2019
Nokia internal use
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Parameters Description (6/6)
Parameter MRBTS/LNBTS/actCAggrLteNrDualConnectivity activates Carrier Aggregation in LTE-NR Dual Connectivity
scenarios in the LTE BTS. Note that only blind LTE CA is possible in FL19 with feature LTE4575. Therefore, the only
possible value to enable the feature is actCAggrLteNrDualConnectivity = 'blind_CA_LTE_NR'.
Parameter MRBTS/LNBTS/NRDCDPR/cAggrLteNrDcCellList defines the cells of the LTE BTS for which Carrier
Aggregation in an LTE-NR Dual Connectivity scenario is enabled. The 'lcrId' of the own LNCEL instances shall be added.
• If set to value '-1', carrier aggregation for all cells of the BTS are enabled. In this case, no dedicated cells are allowed to be
configured, i.e. the list is allowed to include only one item.
142 © Nokia 2019
Nokia internal use
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Parameters List (1/2)
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
(GUI)
reco if not same
as default (GUI)
list of use cases in
MIND
EN-DC - LTE part Call Setup Success Rate Activation LTE-NR Dual-Connectivity
actLteNrDualConnectivity
EN-DC - LTE part Call Setup Success Rate Activation of dynamic trigger for LTE-NR Dual
Connectivity
actDynTrigLteNrDualConnectivity
MRBTS.LNBTS.actLteNrDualConnectivity
FALSE
TRUE
EN-DC - LTE part
MRBTS.LNBTS.actDynTrigLteNrDualConnectivity
FALSE
TRUE
EN-DC - LTE part
EN-DC - LTE part Call Setup Success Rate B1 NR DC RSRP Time to trigger
b1TimeToTriggerRsrp
EN-DC - LTE part Call Setup Success Rate B1 NR DC RSRQ Time to trigger
b1TimeToTriggerRsrq
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.b1TimeToTriggerRsrp
256
40
EN-DC - LTE part
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.b1TimeToTriggerRsrq
256
40
EN-DC - LTE part Call Setup Success Rate B1 RSRP treshold for NR DC
b1ThresholdNrRsrp
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.b1ThresholdNrRsrp
EN-DC - LTE part
-120
EN-DC - LTE part Call Setup Success Rate B1 RSRQ treshold for NR DC
b1ThresholdNrRsrq
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.b1ThresholdNrRsrq
EN-DC - LTE part
EN-DC - LTE part Call Setup Success Rate B1 Trigger Quantity for NR DC
b1TriggerQuantity
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.b1TriggerQuantity
EN-DC - LTE part Call Setup Success Rate Filtering coefficient used for RSRP for NR DC
filterCoefficientRsrp
EN-DC - LTE part Call Setup Success Rate Filtering coefficient used for RSRQ for NR DC
filterCoefficientRsrq
EN-DC - LTE part Call Setup Success Rate Guard timer for X2-C UE related signaling
timerX2UeProcGuard
MRBTS.LNBTS.NRDCPR.nrDcQuantityConfig.filterCoefficientRsr
p
MRBTS.LNBTS.NRDCPR.nrDcQuantityConfig.filterCoefficientRsr
q
MRBTS.NRBTS.timerX2UeProcGuard
RSRP
EN-DC - LTE part
5000
EN-DC - LTE part Call Setup Success Rate Guard timer for X2-U DL End Marker reception
x2EndMarkerTimer
MRBTS.NRBTS.x2EndMarkerTimer
2000
143 © Nokia 2019
Nokia internal use
fc4
fc4
4G-5G Interactions : Dual Connectivity (NSA Option 3x)
Parameters List (2/2)
Domain
Sub-domain
Parameter Name
Abbreviation
MIND Reference
Default value
(GUI)
EN-DC - LTE part Call Setup Success Rate Hysteresis RSRP for B1 NR DC
hysB1ThresholdRsrp
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.hysB1ThresholdRsrp
2
EN-DC - LTE part Call Setup Success Rate Hysteresis RSRQ for B1 NR DC
hysB1ThresholdRsrq
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.hysB1ThresholdRsrq
2
EN-DC - LTE part Call Setup Success Rate Starting ARP for EN-DC eligible bearer
startArpEnDc
MRBTS.LNBTS.qciTabOperator.startArpEnDc
1
EN-DC - LTE part Call Setup Success Rate Stop ARP for EN-DC eligible bearer
stopArpEnDc
MRBTS.LNBTS.qciTabOperator.stopArpEnDc
EN-DC - LTE part Call Setup Success Rate Activate nonGBR service differentiation
actNonGbrServiceDiff
MRBTS.LNBTS.actNonGbrServiceDiff
MRBTS.LNBTS.tLteNrDualConnectPrep
EN-DC - LTE part Call Setup Success Rate LTE-NR Dual Connectivity (EN-DC) allowed
lteNrDualConnectAllowed
MRBTS.LNBTS.LNCEL.LNRELGNBCELL.lteNrDualConnectAllowed
allowed
EN-DC - LTE part Call Setup Success Rate LTE-NR Dual connectivity support
lteNrDualConnectSupport
MRBTS.LNBTS.qciTabOperator.lteNrDualConnectSupport
disabled
Retainability
Handover Success Rate Dual Connectivity overall timer
tDCoverall
MRBTS.NRBTS.tDCoverall
Usage
Throughput - Peak in DL Activation of CA in LTE-NR Dual Connectivity
actCAggrLteNrDualConnectivity
MRBTS.LNBTS.actCAggrLteNrDualConnectivity
Nokia internal use
list of use cases in
MIND
TRUE
EN-DC - LTE part
EN-DC
EN-DC - LTE part
15
FALSE
EN-DC - LTE part Call Setup Success Rate Supervision timer for LTE-NR Dual Connectivity over tLteNrDualConnectPrep
X2 interface (EN-DC)
144 © Nokia 2019
reco if not same
as default (GUI)
500
2000
disabled
blind_CA_LTE_NR
4G – 5G Interactions KPIs
KPI ID
LTE_6420a
LTE_6419a
LTE_6431a
LTE_6432a
LTE_6433a
KPI NAME
E-UTRAN EN-DC X2 Setup Attempts
E-UTRAN EN-DC X2 Setup Success Ratio
SCG Addition Preparation Attempts
SCG Addition Preparation Failure Ratio due to SgNB Rejection
SCG Addition Preparation Failure Ratio due to timer expiry (T_DC_Prep)
145 © Nokia 2019
Nokia internal use
UNIT
No unit
%
No unit
%
%
Scope
Accessibility/Ret
ainability
Usage :
Throughput
Mobility
4G-5G
interactions
Design Specific
Parameters
146 © Nokia 2019
Nokia internal use
Usage : Packet
Delay
Design Specific Parameters
This section describes parameters which need to be customised on each network, depending on design
provided by customer.
These are parameters to be set during commissioning phase to allow site/cell setup.
147
© Nokia 2019
Nokia internal use
Site Commissioning SCF File Parameters Configuration
EQM design parameters :
•
MRBTS.EQM.APEQM.Location
•
MRBTS.EQM.APEQM.rapProfile : This parameter must be tuned with each delivery, see next slide for details
•
MRBTS.EQM.APEQM.RMOD.cableLength : Cable length between ABIL and RU in meters
MNL design parameters :
•
MRBTS.MNL.MNLENT.targetDN : This attribute must be linked to APEQM Object.
•
MRBTS.MNL. MNLENT.SYNC.CLOCK.sModDN : This attribute must be linked to MRBTS.EQM.APEQM.CABINET.SMOD” object
•
MRBTS.MNL.MNLENT.SYNC.CLOCK.GNSSE.gnssCableLength : Cable lenght between ASIK and GPS antenna in meters
•
MRBTS.MNL.MNLENT.SYNC.CLOCK.TIME.timeZone : Network time zone
NRBTS design parameters :
•
MRBTS.NRBTS.gNbCuType : This attribute must be set to NSA
•
MRBTS.NRBTS.mcc : To be set according to network PLMN
•
MRBTS.NRBTS.mnc : To be set according to network PLMN
•
MRBTS.NRBTS.mncLength : To be set according to network PLMN
•
MRBTS.NRBTS.LTEENB.x2LinkLock : This attribute must be set to unlock to allow X2 setup.
148 © Nokia 2019
Nokia internal use
5G19 RAP Profile Configuration
ID meaning
List of available reference configurations (RAP profiles) here
149
© Nokia 2019
Nokia internal use
Site Commissioning SCF File Parameters Configuration
NRCELL design parameters :
•
MRBTS.NRBTS.NRCELL.cellTechnology : TDD or FDD according to network design
•
MRBTS.NRBTS.NRCELL.expectedCellSize: useful for counters histogram definition
•
MRBTS.NRBTS.NRCELL.freqBandIndicatorNR : to be set according to 3GPP band definition, and network design
•
MRBTS.NRBTS.NRCELL.chBw : to be set according to network bandwidth for TDD networks
•
MRBTS.NRBTS.NRCELL.NRCELL_FDD.chBwDl : to be set according to network bandwidth for FDD networks
•
MRBTS.NRBTS.NRCELL.NRCELL_FDD.chBwUl : to be set according to network bandwidth for FDD networks
•
MRBTS.NRBTS.NRCELL.nrARFCN : to be set according to network band allocation
•
MRBTS.NRBTS.NRCELL.nrCellIdentity : to be set according to cell id provided by customer for each cell
•
MRBTS.NRBTS.NRCELL.lcrId : to be set according to cell identity
•
MRBTS.NRBTS.NRCELL.physCellId : to be set according to PCI plan provided by RNP study
•
MRBTS.NRBTS.NRCELL.tddFrameStructure.ulDlDataSlotRatio : This attribute must be set to the same value for all NRCELL
•
MRBTS.NRBTS.NRCELL.ssbScs : This attribute must be set to 30 KHz for below 6GHz and 240 KHz for above 28GHz
•
MRBTS.NRBTS.NRCELLGRP.scs : This attribute should be set to 30 KHz for below 6GHz and 120 KHz for above 6GHz
150 © Nokia 2019
Nokia internal use
Site Commissioning SCF File Parameters Configuration
NRDU design parameters :
•
MRBTS.NRBTS.NRDU.gNbDuId
•
MRBTS.NRBTS.NRDU.targetDN : This attribute must be linked to MRBTS.EQM.APEQM
•
MRBTS.NRBTS.NRDU.NRDU_f1Cplane.ipV4AddressDN1 or .ipV6AddressDN1
•
MRBTS.NRBTS.NRDU.NRDU_f1Mplane.ipV4AddressDN1 or .ipV6AddressDN1
•
MRBTS.NRBTS.NRDU.NRDU_f1Uplane.ipV4AddressDN1 or .ipV6AddressDN1
151 © Nokia 2019
Nokia internal use
Site Commissioning SCF File Parameters Configuration
TNL design parameters :
•
MRBTS.TNLSVC.TNL/1.neType : This attribute is set to OAM-VNFC
•
MRBTS.TNLSVC.TNL/2.neType : This attribute is set to CNCP
•
MRBTS.TNLSVC.TNL/3.neType : This attribute is set to UE-UP
•
MRBTS.TNLSVC.TNL/4.neType : This attribute is set to FSM
•
MRBTS.TNLSVC.ETHSVC.ETHIF.linkSelectorDN
•
MRBTS.TNLSVC.ETHSVC.ETHLK.connectorLabel
•
MRBTS.TNLSVC.ETHSVC.ETHLK.modDN
•
MRBTS.TNLSVC.IPNO.IPIF.interfaceDN
•
MRBTS.TNLSVC.IPNO.IPIF.IPADDRESSV
152 © Nokia 2019
Nokia internal use
LTE Design parameters
Domain
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Design
Subdomain
Parameter Name
Abbreviation
MIND Reference
Administrative state
administrativeState
C-Plane IP address of neighbor gNB cPlaneIpAddr
Default NR cell for dual connectivity defaultLnRelGnbCellI
d
Duration for SS/PBCH blocks
ssbDuration
Dynamic trigger method
method
MRBTS.LNBTS.LNADJGNB.administrativeState
MRBTS.LNBTS.LNADJGNB.cPlaneIpAddr
MRBTS.LNBTS.LNCEL.defaultLnRelGnbCellId
Length of gnbId within nrCellId
Local cell resource ID
Local IPv4 address
Local IPv6 address
MCC in primary PLMN identity
MNC in primary PLMN identity
MNC length in primary PLMN
identity
New Radio global cell identifier
NR DC carrier frequency
NR PDCP profile index
Offset for SS/PBCH blocks
Periodicity of SS/PBCH blocks
Quantity configuration index for NR
Resource type
RLC mode
Sequence number size DL
Sequence number size UL
Subcarrier spacing of NR carrier
X2C link lock
gnbIdLength
lcrId
localIpAddr
localIpAddr
mcc
mnc
mncLength
MRBTS.LNBTS.LNCEL.LNRELGNBCELL.gnbIdLength
MRBTS.LNBTS.NRDCPR.dynTriggerLteNrDcConfList.lcrId
MRBTS.TNLSVC.TNL.IPNO.IPIF.IPADDRESSV4.localIpAddr
MRBTS.TNLSVC.TNL.IPNO.IPIF.IPADDRESSV6.localIpAddr
MRBTS.LNBTS.LNCEL.LNRELGNBCELL.nrCgiPlmnId.mcc
MRBTS.LNBTS.LNCEL.LNRELGNBCELL.nrCgiPlmnId.mnc
MRBTS.LNBTS.LNCEL.LNRELGNBCELL.nrCgiPlmnId.mncLength
nrCellId
carrierFreqNrCell
nrPdcpProfIdx
ssbOffset
ssbPeriodicity
quantityConfigId
resType
rlcMode
snSizeDl
snSizeUl
ssbSubcarrierSpacing
x2LinkLock
MRBTS.LNBTS.LNCEL.LNRELGNBCELL.nrCellId
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.carrierFreqNrCell
MRBTS.LNBTS.qciTabOperator.nrPdcpProfIdx
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.ssbOffset
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.ssbPeriodicity
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.quantityConfigId
MRBTS.LNBTS.qciTabOperator.resType
MRBTS.LNBTS.qciTabOperator.rlcMode
MRBTS.LNBTS.pdcpProf1001.snSizeDl
MRBTS.LNBTS.pdcpProf1001.snSizeUl
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.ssbSubcarrierSpacing
MRBTS.NRBTS.LTEENB.x2LinkLock
Default value reco if not
list of use
(GUI)
same as cases in MIND
default
unlocked
MRBTS.LNBTS.NRDCPR.nrDcMeasConfig.ssbDuration
MRBTS.LNBTS.NRDCPR.dynTriggerLteNrDcConfList.method
153 © Nokia 2019
Nokia internal use
coverageBas
ed
1001
nonGBR
RLC_AM
18bit
18bit
unlocked
15
4
© Nokia 2019
Nokia internal use
Copyright and confidentiality
The contents of this document are proprietary and
confidential property of Nokia. This document is
provided subject to confidentiality obligations of the
applicable agreement(s).
This document is intended for use of Nokia’s
customers and collaborators only for the purpose for
which this document is submitted by Nokia. No part of
this document may be reproduced or made available to
the public or to any third party in any form or means
without the prior written permission of Nokia. This
document is to be used by properly trained
professional personnel. Any use of the contents in this
document is limited strictly to the use(s) specifically
created in the applicable agreement(s) under which the
document is submitted. The user of this document may
voluntarily provide suggestions, comments or other
feedback to Nokia in respect of the contents of this
document ("Feedback"). Such Feedback may be used in
Nokia products and related specifications or other
documentation. Accordingly, if the user of this
document gives Nokia Feedback on the contents of this
document, Nokia may freely use, disclose, reproduce,
license, distribute and otherwise commercialize the
feedback in any Nokia product, technology, service,
specification or other documentation.
Nokia operates a policy of ongoing development. Nokia
reserves the right to make changes and improvements
to any of the products and/or services described in this
document or withdraw this document at any time
without prior notice.
The contents of this document are provided "as is".
Except as required by applicable law, no warranties of
any kind, either express or implied, including, but not
limited to, the implied warranties of merchantability
and fitness for a particular purpose, are made in
relation to the accuracy, reliability or contents of this
document. NOKIA SHALL NOT BE RESPONSIBLE IN ANY
EVENT FOR ERRORS IN THIS DOCUMENT or for any loss
of data or income or any special, incidental,
155 © Nokia 2019
Nokia internal use
consequential, indirect or direct damages howsoever
caused, that might arise from the use of this document
or any contents of this document.
This document and the product(s) it describes are
protected
by
copyright
according
to
the
applicable laws.
Nokia is a registered trademark of Nokia Corporation.
Other product and company names mentioned herein
may be trademarks or trade names of their respective
owners.
© Nokia 2016