5G Feature Application &

Parameter Optimization

Copyright © Huawei Technologies Co., Ltd. All rights reserved.

 Objectives

 Upon completion of this course, you will be able to:

 Master the configuration principles and optimization methods of 5G NSA networking
features
 Master the optimization parameters for 5G access/mobility/retainability performance
 Master the optimization parameters for 5G data transfer

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 2

 Contents

1. 5G Parameters Overview

2. NSA 4G/5G Coordination Parameters Optimization

3. 5G Control Plane Related Parameters Optimization

4. 5G Data Transfer Related Parameters Optimization

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

5G Performance Parameters Optimization Overview
 When perform parameters optimization?
 Parameters optimization is performed after RF optimization
 Why perform parameters optimization?
 After the RF optimization is complete, we can optimize the parameters to improve the network quality
 On the live network, traffic models and service requirements vary with scenarios, such as high-speed
railways, highways, and residential areas. Therefore, customized parameter optimization is required for
special scenarios
 Some enhanced features can be enabled in some special scenarios to meet service requirements
 Classification of performance parameters: there are many performance related parameters for 5G,
this courser is focus on following:
 NSA networking related parameters: Involve eNodeB and gNodeB, used for MCG and SCG management
 NR control plane performance related: Include accessibility, mobility and retainability
 NR user plane performance related: Include throughput and latency

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 4

 Contents

1. 5G Parameters Overview

2. NSA 4G/5G Coordination Parameters Optimization

3. 5G Control Plane Related Parameters Optimization

4. 5G Data Transfer Related Parameters Optimization

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 5

NSA Networking Key Parameters
Group Functionality
MCG management PCC flexible anchoring
NSA user decoupling related parameters
SCG Management SCG periodic addition
Volume based SCG management
MFBI configuration
Service related SCG policy for VoLTE user
Mobility policy for NSA user

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 6

 MCG Management Related Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 7

Flexible PCC Anchoring – Periodic PCC Anchoring
[Description]
 In a business hall, the user report that it is difficult to access the NSA 5G cell. Anchor
selection is triggered only after the airplane mode is set to 1.

[Analysis]
 NSA PCC anchoring feature review: This feature is used to anchor the NSA user to the
highest priority LTE frequency. The default trigger is event based (After UE access or
handover into a low priority LTE frequency)
 Possible problem: When event-triggered anchoring is triggered, the current high-priority
anchoring coverage does not meet the requirements. Therefore, anchoring cannot be
triggered even if the coverage of the anchoring cells meets the requirements.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 8

Flexible PCC Anchoring – Periodic PCC Anchoring

5G cell 5G cell

1 Non-anchor F1 1 Non-anchor F1
2 After optimization 2
cell cell
Anchor cell Anchor cell 3

[Solution]
 Optimization solution: The PERIODIC_PCC_ANCHORING_SW parameter is introduced
to enable the eNodeB to periodically trigger PCC anchoring
 Impact: After this function is enabled, the proportion of online 5G UEs increases.
However, periodic PCC anchoring causes more measurement gaps, affecting user
experience

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 9

Flexible PCC Anchoring – NR Coverage Based Anchoring

[Description]
 After NSA PCC anchoring, if the NR coverage is poor, the SCG can’t be added, if the
current LTE cell is not the highest priority LTE cell, it may affect user experience.

[Analysis]
 When PCC anchoring is enabled, the eNodeB does not check the NR coverage and
therefore cannot determine whether the anchored LTE cell can complete SCG
addition procedure.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 10

 Flexible PCC Anchoring – NR Coverage Based Anchoring
5G cell
5G cell

F1 Non-anchor cell（NSA
Non-anchor cell（NSA After optimization anchoring priority is 0，
anchoring priority is 0， Normal priority is 7）
Normal priority is 7）
No need NSA Anchor cell(NSA
SCG can’t be Anchor cell(NSA PCC anchoring if anchoring priority is 7,
configured due to no anchoring priority is 7, there is no NR Normal priority is 5)
Normal priority is 5)
NR coverage coverage

[Solution]
 Optimization solution: Enable NR coverage based PCC anchoring, NR B1 measurement report is
required as well during the anchoring, if no B1 report, the anchoring function is not performed.
 Feature enable suggestion: If NR coverage is not consecutive and the NSA anchoring cell is not
the high priority cell for normal LTE user, we suggest to enable this function.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 11

NSA PCC Anchoring Threshold
 During PCC anchoring, event A5 is used by default. Threshold 1 for event A5 is fixed
to -43dBm. Therefore, only threshold 2 for event A5 (NSADCPCCA4RsrpThd) needs
to be configured
 Parameter setting suggestion:
 This A4 threshold in source cell should be larger than the A2 threshold in the target
anchoring cell, avoid pingpong handover between them
 Recommended value: -105dBm ~ -107dBm

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 12

gNodeB NSA Capability and PCC Anchoring Function
Decoupling
 Feature description: In versions earlier than RAN3.0, the NSA PCC anchoring function
is coupled with the NSA capability. The NSA PCC anchoring function takes effect
only after the NSA_DC_CAPABILITY_SWITCH option is selected. These two functions
are decoupled in the new version:
 If the current LTE cell does not support NSA_DC, but NSA PCC anchoring can still be
performed
 If the current LTE cell supports NSA_DC, NSA access can be initiated even if the anchor
priority is not configured

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 13

 SCG Management Related Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 14

Periodic SCG Addition
[Description]
 In most cases, an NSA DC UE attempts to add SCG during initial access, handover, or RRC
connection reestablishment. If the initial SCG configuration fails or the SCG configuration is
deleted, the SCG configuration cannot be triggered.

[Analysis]
 To prevent this problem, the eNodeB starts a timer for periodic SCG addition each time the
eNodeB attempts to add an SCG. After the timer expires, the eNodeB will trigger SCG addition
again.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 15

Periodic SCG Addition(Cont.)

[Solution] SCG removal

Scenario 1:
After the SCG addition complete, the timer SCG interval SCG interval
starts. If SCG is removed before timer expires,
the SCG addition attempt will be triggered
after timer expires. Timer start SCG removal

Timer expire SCG configured

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 16

Periodic SCG Addition(Cont.)

[Solution] SCG removal

Scenario 2:
SCG addition complete, the timer starts. If
SCG is removed after timer expires, the SCG SCG interval SCG interval
add attempt will be triggered immediately
Timer start SCG removal

Timer expire SCG configured

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 17

Periodic SCG Addition(Cont.)

[Solution]
SCG addition
failure
Scenario 3:
If SCG addition failure, after timer expires,
eNodeB will try the addition attempt again
and restart the timer. SCG interval SCG interval

Timer start SCG removal

Timer expire SCG configured

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 18

Periodic SCG Addition (Cont.)
 Parameter setting recommendation:
 General rule: The SCG addition interval should be larger than UE inactive timer on
gNodeB side, to avoid that the SCG addition is periodic triggered if there is no traffic at
all.
 Suggested value based on scenario
 Default value: 60s, it is too large
 Normal scenario: 10~20s, consider UE inactive timer
 If we need to increase 5G user online ratio, we can reduce value

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 19

MFBI Configuration
 MFBI: Muti-Frequency Band Indicator
 Similar as LTE, some NR frequency range belong to different frequency band. During
NSA access, eNodeB will deliver NR SSB frequency number and band to UE, in order
to compatible with different UE capability, we can configure MFBI in eNodeB side.
 The following frequency number belong to multiple bands:
 158200-160600，285400-303400，386000-398000，402000-404000，442000-434000，
514000-537999，620000-653333，2054166-2084999

 Suggestion: If the actual SSB frequency number belong to above range, we can
consider to configure MFBI consider the UE band capability

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 20

NSA S1 Procedure Conflict Compatibility Switch
[Description]
 During the transient process of SCG addition or deletion, the eNodeB needs to interact with the MME. If
the MME triggers the dedicated bearer setup, modification, or release process, the conflict may occur
[Solution]
 Enable the conflict compatibility switch. After this switch is turned on, the network side preferentially performs
dedicated bearer-related procedures and processes SCG-related procedures only after the dedicated bearer-
related procedures are complete

[Suggestion]
 Enable this function to improve the performance for SCG management and VoLTE setup

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 21

 Service Related Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 22

VoLTE User SCG Management Strategy
 If VoLTE call is setup, the SCG management procedure is as following:
Policy SCG is configured SCG is not configured
VOLTE_PREFERRED the eNodeB releases the SgNB immediately eNodeB will not trigger an SgNB addition
before the VoLTE service is released
ADAPTIVE SINR of a UE that initiates a VoLTE service is the eNodeB will not trigger an SgNB
smaller than the value of addition before the VoLTE service is
NsaDcMgmtConfig.UlQualityThldForScgRelease released
or the uplink/downlink packet loss rate of the
VoLTE service of QCI 1 is greater than the value
of
NSADCMGMTCONFIG.VoltePlrThldForScgReleas
e, the eNodeB immediately releases the SgNB
VOLTE_SCG_COEXIS No action If VOLTE_NSA_DC_IF_NR_MEAS_SW is ON,
TENCE eNdoeB will trigger the NR measurement;
if it is off, eNodeB will not trigger NR
measurement

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 23

NSA UE LTE Mobility Strategy Decoupling
[Description]
 Special inter-frequency handovers are introduced to LTE networks, such as service-based,
frequency-priority-based, and load balancing-based inter-frequency handovers.
 To prevent conflicts between these handover principles and NSA anchoring policies, these
policies can be separately configured for NSA DC UEs
[Suggestion]
 Priority based inter-frequency handover：If the frequency priorities configured for frequency-
priority-based handovers are different from the NSA DC PCC priorities, it is recommended
that the FREQ_PRI_HO_SW option of the NsaDcMgmtConfig.NsaDcUeLteFunActivationSw
parameter be deselected. In this case, frequency-priority-based inter-frequency handover
does not take effect on NSA DC UEs

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 24

NSA UE LTE Mobility Strategy Decoupling(Cont.)
[Suggestion]
 Service based inter-frequency handover: When service-based inter-frequency
handover is enabled on the LTE side, UEs may be handed over to LTE frequencies
that do not support NSA. Therefore, it is recommended that this function not be
enabled for NSA DC UEs, if the SERV_BASED_INTER_FREQ_HO_SW option of the
CellQciPara.NsaDcOptSwitch parameter is deselected for a specific QCI, service-
based inter-frequency handovers cannot be triggered for the QCI

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 25

NSA UE MLB Strategy
[Description]
 MLB (Mobility Load Balance) is often used in LTE network, if NSA-DC UEs are transferred
during MLB, 5G user experience may be affected. Therefore, the MLB target of NSA UEs is
controlled independently

[Solution]
 After MLB is triggered in an LTE cell, if the transferred UEs are NSA DC UEs, the target
frequencies must meet the following requirements:
 The target frequency to which an NSA DC UE is handed over must be an NSA anchor cell (that is,
the PCC priority is not 0). If not, the handover will not be triggered.
 In addition, to prevent SCG abnormal remove, inter-RAT load balancing does not take effect for
NSA DC UEs.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 26

 Contents

1. 5G Parameters Overview

2. NSA 4G/5G Coordination Parameters Optimization

3. 5G Control Plane Related Parameters Optimization

4. 5G Data Transfer Related Parameters Optimization

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 27

 NR Standard Radio Timer & Constant

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 28

Summary of NR Major Timer & Constant Summary

Timer NE Delivery method Network type Usage

T300 UE SIB1 SA only Control RRC setup procedure
T301 UE SIB1 SA only Control RRC reestablishment
procedure
T310 UE SA network: SIB1 NSA&SA Control DL link recovery
T311 UE NSA network: RRC SA only procedure
reconfiguration
N310 UE NSA&SA DL in-sync detection
N311 UE NSA&SA DL out-of-sync detection
TA timer gNodeB & UE NSA&SA UL time aliment detection
T304 UE RRC reconfiguration NSA & SA NSA: Control the SCG addition
and change procedure
SA: Control handover procedure
UE inactive timer gNodeB NA NSA & SA Control UE radio release
procedure

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 29

Access Performance Timer: T300 UE gNB

 Timer description: Start

RRC Setup Request
T300
 Used to control RRC setup procedure in SA network
Stop RRC Setup /RRC Reject
T300
 Working principle:
 Start: UE send “RRC setup request” message to gNodeB
 Stop: UE receive “RRC setup” or “RRC setup reject” message
 Expire: UE enter RRC idle mode

 Timer setting impact & suggestion: A larger value of this parameter can improve
RRC connection setup success rate in weak coverage scenarios, but may increase the
access duration. Generally, the value 1s is recommended

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 30

Access Performance Timer: T301 gNB
UE

 Timer description:
 Used to control RRC reestablishment procedure RRC Reestablishment Request
Start
T301
 Working principle: RRC Reestablishement/Reject
Stop
 Start: UE send “RRC reestablishment request” T301

 Stop: UE receive “RRC reestablishment “ or “ RRC reestablishment reject”

 Expire: UE enter RRC idle mode

 Timer setting impact & suggestion: A larger value of this parameter can improve
RRC connection reestablishment success rate in weak coverage scenarios, but may
increase the reestablishment duration. Generally, the recommended value is 200 ms

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 31

Radio Link Failure Detection Constraint – N310
 Downlink radio link failure detection in NR: UE monitor physical link and measure PDCCH
BLER on physical layer periodically, and compare the result with Qin and Qout threshold.
According to the result, UE physical layer send relevant indicator to RRC layer
 If the result is large than Qout(10%) threshold , L1 send “out-of-sync” indicator
 If the result is less than Qin (2%) threshold, L1 send “in-sync” indicator
 If UE RRC receive the “out-of-sync” indicator, UE start countdown N310. Before it reaches 0, if
RRC can receive “in-sync” indicator, the N310 will be stopped and reset. If the counter reach 0,
UE detects the radio link failure happen

 N310 is used for consecutive countdown of “out-of-sync”

 Setting suggestion: Increase this parameter to reduce RLF probability, the recommendation is
10 times.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 32

Radio Link Recovery Timer: T310/N311/T311
 T310: Used to control the link failure recovery
 Start: If UE detects radio link failure, UE starts T310
 Stop: UE detects radio link recovery on physical layer, or UE receive “a RRC reconfiguration
message containing the reconfigurationWithSync, or UE receive RRC reconfiguration message
with SCG release
 Expire:
 NSA network: UE send “SCG failure” message to eNodeB
 SA network: UE initial RRC reestablishment procedure

 T310 setting suggestion:

 larger value of this parameter results in a higher probability of physical link recovery and a
lower probability of SCG failure or RRC connection reestablishment. However, if the fault
persists, services are interrupted and the delay increases. Generally, the recommended value is
1s

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 33

Radio Link Recovery Timer: T310/N311/T311 (Cont.)
 Link recovery mechanism: After UE starts gNodeB
UE
T310, UE will continue to monitor radio link
 Before T310 expire, if UE L3 could receive T310 start

consecutive in-sync indicator with the counter N311 countdown

Link monitor with in sync

N311, UE recover the radio link Reset N311

Link monitor with out-of-sync

Link monitor with in sync

 N311 setting suggestion: reduce this N311 countdown
Link monitor with in sync
constant as low as possible to fast link Link monitor with in sync

recovery procedure Link monitor with in sync

N311 countdown to 0, Link monitor with in sync
stop T310, link recover

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 34

Radio Link Recovery Timer: T310/N311/T311 (Cont.)
 If T310 expires:
UE gNodeB
 NSA network: UE send “SCG failure info”,
and eNodeB will release gNdoeB connection Radio link failure
detected, start T310
 SA network: UE initials RRC reestablishment
procedure to recover link by RRC layer, T311 Random access preamble
Stop T310,
will be used to control the whole procedure Start T311
Random access response
 Timer start: UE initials RRC reestablishment
RRC reestablishment request
procedure, including cell search Start T301 RRC connection
 Timer stop: UE complete the procedure and Stop T301 reestablishment
RRC connection
camp on suitable cell
Stop T311 reestablishment completet
 Timer expirer: UE enter idle mode

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 35

 UE eNodeB gNodeB

Mobility Performance Timer – T304 Start

RRC CONN RECFG
(T304)
T304 RRC CONN RECFG CMP
Preamble
RA responese

Stop Msg3
 This timer is used in following scenarios: T304

 NSA network：This timer is used to control the SCG addition and change procedure
 SA network: This timer is used to control handover procedure

 Working principle
 Timer start: After receiving the RRC reconfiguration message containing the reconfigurationWithSync
IE, the UE starts the timer immediately
 Timer stop: UE complete random access proecedre
 Timer expire:
 NSA network: UE send “SCG failure info”, indicate relevant failure cause
 SA network: UE initial RRC reestablishment procedure

 Timer setting suggestion： Increase this timer value to improve the access and mobility
performance, but it will also increase the latency of procedure, the recommended value is 1s
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 36
Retainbility Performance Timer – TA Timer
 TA timer working principle on UE: After UE receive TA command, TA start or restart
the TA timer; If timer expires, UE detect that uplink is out of sync
 TA timer working principle on gNdoeB: After gNodeB receive ACK feedback from UE
for TA command, gNodeB start or restart TA timer; If timer expires, gNodeB detect
that uplink is out of sync
 Suggestion: Increase this timer can reduce probability of uplink out-of-sync; But it
will increase the link recovery time in poor radio environment
 Normal scenario: recommended value is infinity
 High speed scenario: recommended value is 1280 subframe

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 37

Retainbility Performance Timer – UE Inactive Timer
 Working principle
 Timer start: gNdoeB detect that there is no traffic on DRB
 Timer stop: gNodeB detect the traffic on DRB and reset the timer
 Timer expire:
 NSA network: gNodeB trigger SgNodeB release procedure
 SA network: gNodeB trigger RRC release procedure

 Suggestion: Less value could reduce the UE power consumption but cause more
signaling interaction. For most of scenarios, the recommended value is 10s

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 38

 Networking Related Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 39

5G Networking Related Optimization Parameters
 5G networking related optimization parameters:

Parameters Functions Effects

NrNetworkingOption Indicates the architecture option of an operator. Affect the access
The value SA indicates that the operator supports KPIs
standalone networking. The value NSA indicates that
the operator supports non-standalone networking.
The value SA_NSA indicates that the operator
supports standalone and non-standalone networking.
gNBIdLength Indicates the length of the gNodeB ID. The Affect the access
gNBIdLength parameter specifies the number of bits and handover KPIs
occupied by the gNBId in the NR cell identity (NCI),
which uniquely identifies the NCI.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 40

Access/Mobility Performance Parameter - Networking
Option
 Parameter name: NrNetworkingOption
 This parameter is used to define the supported network mode, includes: NSA
only/SA only/NSA&SA, if the network mode is not compatible with UE capability, the
UE can not access to network. Configure the correct networking option according to
current situation
 Configuration command

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 41

Access/Mobility Performance Parameters – gNodeB ID
length
 Parameter name: gNBIdLength
 NCGI: NR cell global ID, consists of gNodeB ID and cell ID
 Different as LTE, gNodeB ID length is not fixed value, the length is from 22bit to 32bit

gNodeB ID （22~32bit） cell ID （4~14bit）

36bit
 The gNodeB length should be configured to verify the exact gNodeB ID and cell ID
 Configuration rules:
 The length depends on the number of gNodeB, the larger value, more gNodeB number can be
support
 The gNodeB lenth should be the same for all gNodeB in one PLMN, otherwise it may cause
handover problem

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 42

 Feature Related Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 43

5G Features Related Parameters
 5G features related parameters:

Parameters Effects
PDCP/RLC SN Size Affect the access and handover KPIs
SSB Selection Threshold Affect the access KPIs
A3 Event Related Parameters Affect the handover KPIs
SSB Consolidation Related Parameter Affect the handover KPIs
SMTC Period and Duration Measurement related parameters
TA Offset Affect the access and handover KPIs

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 44

Access/Mobility Performance Parameters – PDCP/RLC SN
Size
 Parameter description: It is standard Uu interface
parameter
 Indicate the SN size in PDCP and RLC header. PDCP SN
support long size(18bit) and short size (12bit). AM RLC
support 18bit and 12bit; UM RLC support 12bit and 6bit

 Performance impact:
 Large SN size, less packet loss ratio, but it causes more
overhead.
 Configuration suggestion：Prefer to choose long size; Ensure
that all gNodeB keep the same value avoid handover issue;
Ensure eNodeB PDCP SN size the same as gNodeB PDCP SN
size avoid SCG additional issue

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 45

Access Performance Parameter – SSB Selection Threshold
 Parameter description: It is standard Uu interface parameter
 This threshold is used for SSB selection, during the cell search, the SSB RSRP should be
more than this threshold
 Configuration impact:
 A smaller value of this parameter results in a lower RSRP of the SSB selected by the UE
and a lower access success probability. However, the time for searching for a proper SSB is
shorter, which shortens the access delay. A larger value of this parameter results in the
opposite effects
 Suggestion: For normal case, the recommended value is 0, that means the minimal
threshold -156dbm

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 46

Mobility Performance Parameters – A3 Event Related
Parameters
 A3 related parameters includes: IntraFreqHoA3Offset / IntraFreqHoA3TimeToTrig/
IntraFreqHoA3Hyst/ CellIndividualOffset (Uu standard parameters)
 Parameter description: Used for event MR trigger for intra-frequency mobility
 A3 event: Mn+Ofn+Ocn(CellIndividualOffset)-
Hys(/IntraFreqHoA3Hyst )>Ms+Ofs+Ocs+Off(IntraFreqHoA3Hyst

 Parameter configuration suggestions

 Default value is recommend for typical scenario
 If there is pingpong handover issue, we can increase hysteresis
 For high speed environment, time to trigger should be reduced
 For specific neighbor handover issue, the cell individual offset should be optimized

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 47

Mobility Performance Parameters – SSB Consolidation
Related Parameter
 SSB consolidation includes following two parameters:
 “SSB consolidation threshold” and “SSB number to average”
 Parameter description: The SSB consolidation parameters are used
for neighbor cell SSB measurement result consolidation if multiple
SSB beams can be measured. The consolidation rules are following:
 If the neighbor best SSB beam RSRP result is less than the SSB
consolidation threshold, then UE choose the best beam result as
consolidation result
 If neighbor SSB beams result is larger than then consolidation
threshold, then UE will choose these beams (the maximum beam
number should no more than SSB number to average), calculate
the average RSRP result as consolidation result

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 48

Mobility Performance Parameters – SSB Consolidation
Related Parameter (Cont.)
 Parameter suggestion
 SSB consolidation threshold: A smaller value of this parameter leads to smaller RSRP
during cell-level SSB measurement and higher probability of triggering cell handover in
the same channel environment. A larger value of this parameter leads to the opposite
effects. The recommended value is 70 (-156dBm)
 SSB number to average: A smaller value of this parameter leads to a smaller number of
SSB beams used by the UE to calculate the cell-level RSRP, higher cell-level RSRP, and a
higher difficulty that the UE is handed over from the serving cell. A larger value of this
parameter leads to the opposite effects. The recommended value is 8

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 49

Mobility Performance Parameter – SMTC Period and
Duration
 SMTC： SSB-based Measurement Time Configuration, includes SMTC period and
SMTC duration. These two parameters are used to control UE measurement
 SMTC period configuration rule: To ensure that in the period UE can measure SSB, the
SMTC period should be equal or larger the SSB period. Larger value will cause the
measurement latency, that affect handover performance, so the SMTC period is
recommended the same value as SSB period (default 20ms)
 SMTC duration configuration rule: The duration should cover SSB beam broadcast time,
for 8 or less SSB beams scenarios, 2ms is enough

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 50

Access/Mobility Performance Parameter – TA Offset
 Parameter description: TA offset is used to set the offset of the TA value used by the
UE to send uplink data relative to the TA value measured by the network side
 TA offset configuration rules: It is based on frequency band and RF networking
mode
 If NR RF module is separate deployed, TA offset is 25600Tc
 If NR RF module is coexistent with LTE
 If it is TDD band, TA offset is 39936Tc
 If it is FDD band, TA offset is 0 Tc

 Parameter setting impact: If TA offset is wrong configured, it may cause the access
or handover issue

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 51

 Contents

1. 5G Parameters Overview

2. NSA 4G/5G Coordination Parameters Optimization

3. 5G Control Plane Related Parameters Optimization

4. 5G Data Transfer Related Parameters Optimization

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 52

Downlink Throughput Related Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 53

5G Downlink Throughput Related Optimization Parameters
 5G downlink throughput related optimization parameters:

Parameters Effects
SSB Rate Match, PDCCH Rate Match, CSI-RS Resource related parameters
Rate Match, TRS Rate Match
SSB period, SIB1 period, CSI-RS period and TRS Resource related parameters
period
PDSCH DMRS related parameters Radio Parameters
Downlink Beamforming related parameters Radio Parameters
Initial MCS and RANK Radio Parameters
PDSCH IBLER threshold Radio Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 54

PDSCH Rate Match Function
 PDSCH rate match introduction: PDSCH rate match indicate whether the other
downlink channel can be coexistent with PDSCH or not. PDSCH rate match consists
of following type:
 SSB rate match: Indicate whether SSB and PDSCH can be coexistent with in the same
symbol in each SSB RB
 PDCCH rate match: Indicate whether PDCCH and PDSCH can be coexistent within the
same symbol
 CSI-RS rate match: Indicate whether CSI-RS and PDSCH can be coexistent within the
same symbol in each RB
 TRS rate match: Indicate whether TRS and PDSCH can be coexistent within the same
symbol in each RB

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 55

SSB Rate Match

 Description: SSB occupies 20RB, but if type0 scheduling is used, SSB will occupy at least
2RBG, sometimes even 3RBG. If no rate match function, the rest of RB in theses RBG
can’t be used by PDSCH as well

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 56

SSB Rate Match (Cont.)
 Suggestion:
 Recommend to enable this function to increase the DL throughput, the gain is related
with SSB period configuration (5%~10% improvement); After activation, PDSCH may
cause interference to SSB, but the impact is not too much

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 57

PDCCH Rate Match

 Description: NR PDCCH bandwidth is configurable, if PDCCH doesn’t occupy the

whole bandwidth, then the rest of resource can be used by PDSCH if PDCCH rate
match is enabled

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 58

PDCCH Rate Match (Cont.)
 Suggestion:
 If PDCCH bandwidth if full configured, the rate match function doesn’t work
 If PDCCH bandwidth is not full configured, we can enable PDCCH rate match to improve
downlink throughput. The gain depends on PDCCH bandwidth, the less bandwidth, the
larger throughput improvement. The minimal PDCCH bandwidth is 12RB

 PDCCH bandwidth configuration

The step is
12 RB

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 59

CSI-RS Rate Match

 Description: CSI-RS only occupy several RE on particular symbols, after CSI-RS rate match is
enabled, the rest of RE on the symbol can be used by PDSCH
 Suggestion:
 Enabling the function can improve DL throughput, but it may cause additional interference to
CSI-RS; So it is recommended to enable this function for peak throughput test scenario. For
other scenario, recommend to disable it
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 60
TRS Rate Match

 Description: TRS only occupy several RE on particular symbols, after TRS rate match
is disabled, the rest of RE on the symbol can be used by PDSCH
 Suggestion:
 For peak throughput test scenario, we can disable this function to improve peak
throughput; In the other scenario, we should enable it to avoid the interference to TRS

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 61

SSB Period
 Parameter description:
 This parameter defines the SSB delivery period on Uu
interface physical layer

 Parameter configuration suggestion:

 SSB period should not be larger than SMTC period
 For above 6G scenario, SSB period should be larger
than 20ms
 Increase the period could reduce the overhead and
improve DL throughput, but it will cause large cell
search latency. The recommended value is 20ms, and
for peak throughput test scenario, we can increase
this period
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 62
SIB1 Period
 Description:
 This parameter indicate the SIB1 delivery period on Uu physical layer

 Parameter configuration suggestion:

 For NSA network, if ANR feature is not used, we can disable SIB1 delivery to improve DL
throughput
 For SA network, we can increase the period to achieve higher throughput, but it will also
increase cell search latency; The recommended value is 20ms for normal scenario; For
peak throughput test scenario, we can increase the period

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 63

CSI-RS/TRS Period
 Description: It indicates the CSI-RS and TRS period on physical layer
 Configuration impact
 CSI-RS period: Larger period, less overhead, the peak throughput can be improved; But it will
impact CSI report, that cause MCS selection is not accurate
 Suggestion: In normal case, the recommended value is 80slot; For peak throughput test scenario, we
can increase this period
 Note: If CSI-RS is set to non-periodic mode, then this parameter is not valid

 TRS period: Larger period, less overhead, the peak throughput can be improved; But it will
impact phase tracing performance which could worse the performance for mobility scenario
 Suggestion: For typical scenario, the recommend value is 20ms; For peak throughput test scenario,
we can increase the period; For high mobility scenario, we should reduce this period

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 64

PDSCH DMRS Related Parameters
 PDSCH DMRS includes following parameters:
 DMRS symbol number: single symbol or two symbols
 DMRS type: type1 or type2
 Addition DMRS: null/Pos1/Pos2
 Configuration impact: If less DMRS resource is configured, it can get higher peak throughput, but it will affect
demodulation performance and increase IBLER
 Configuration rules:
 Ensure that DMRS port number should reach maximum PDSCH layer number
 If demodulation performance can be ensured, configure DMRS resource as less as possible
 Configuration suggestion:
 Peak throughput test scenario: single symbol/type2/No addition DRMS
 Normal scenario: single symbol/type2/Pos1 addition DMRS
 High speed scenario: single symbol/type2/Pos2 addition DMRS
 If UE support 8 layers: two symbols must be used, other rules are the same as above

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 65

Downlink Beamforming Weighting Algorithm
 Downlink beamforming weighting can be obtained from PMI report or SRS, we call
it PMI weighting and SRS weighting
 If SRS SINR is good, SRS weighting performance is better
 If SRS SINR is poor, PMI weighting performance is better

 Configuration suggestion:
 Suggest to enable adaptive weighing algorithm, let gNodeB select the best weighting
algorithm
 For initial accessed UE, gNodeB use default weighting, the recommended is SRS
weighting

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 66

Initial MCS and RANK
 Parameter description: After UE initial access or handover in, before UE send CSI
report, gNodeB will use the initial MCS and RANK for scheduling
 Configuration suggestion
 Default value: initial MCS is 4 and initial RANK is 1
 During drive test, if the coverage is good for whole route, if the throughput drops sharply
after handover, then we can increase initial MCS and RANK, recommended value:
 Initial MCS: 5~8 Test result in live network
1000.0 81.62% 90.12% 100.00%
 Initial RANK: 2 565.3 609.2
500.0 16.67% 20.2 50.00%
9.26%
1.71% 0.62% 21.3
0.0 0.00%
Initial MCS 4,RANK1
初始MCS4,Rank1 Initial MCS8, RANK2
初始MCS8,Rank2

PDCP DL MCS RANK1 RANK2 RANK3

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 67

PDSCH IBLER Target
 Parameter description: IBLER target is used for MCS adjustment algorithm
 Configuration impact:
 The larger IBLER target, MCS selection result will be larger, the theoretical throughput
can be improved, but retransmission ratio is also increased

 Configuration suggestion:
 For normal scenario, 10% is recommended to balance the MCS and retransmission ratio
 For peak throughput test scenario, if the radio environment is very good, we can try to
increase IBLER target to achieve higher throughput

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 68

Uplink Throughput Related Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 69

5G Uplink Throughput Related Optimization Parameters
 5G uplink throughput related optimization parameters:

Parameters Effects
PUCCH Related Parameters Resource related parameters
PUSCH DMRS Parameter Resource related parameters
Uplink Inconsecutive Scheduling Function Scheduling Parameters
PUSCH IBLER Target Radio Parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 70

PUCCH Related Parameters

 PUCCH resource impact: PUCCH resource decides the maximum user number, more PUCCH
resource, more online user, and less uplink throughput; We should set proper PUCCH
resource to balance user number and throughput
 Related parameters:
 If use long format PUCCH (Sub6G scenario), we should configure RB number for format1, format3
 If use short format PUCCH (Above6G scenario), we should configure PUCCH symbol number

 Configuration suggestion:
 For normal scenario: Adopt default value (see below figure)
 For peak throughput test scenario: We can reduce PUCCH resource accordingly
 For large user density scenario: We can increase PUCCH resource accordingly

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 71

PUSCH DMRS Parameter
 PUSCH DMRS includes following parameters:
 DMRS symbol number: single symbol or two symbols （Configuration not
support, default is 1 symbol)
 DMRS type: type1 or type2
 Addition DMRS: Not_CONFIG/Pos1/Pos2
 Configuration impact: If less DMRS resource is configured, it can get
higher peak throughput, but it will affect demodulation performance
and increase IBLER
 Configuration rules:
 Ensure that DMRS port number should reach maximum PDSCH layer number
 If demodulation performance can be ensured, configure DMRS resource as less
as possible
 Configuration suggestion:
 Peak throughput test scenario: single symbol/type2/No addition DRMS
 Normal scenario: single symbol/type2/Pos1 addition DMRS

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 72

Uplink Inconsecutive Scheduling Function
 Background: Usually, the initial BWP is not located on
the side of band, which will cause the PUSCH RB is not
consecutive
 Function description:
Cell
 After this function is enabled, gNodeB can schedule
Bandwidth PRACH
inconsecutive PRB to UE, so that the whole PRB can be
used

 This function is also related with UE capability, if UE

support this feature, it is recommended to enable it to
improve uplink throughput

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 73

PUSCH IBLER Target

 Parameter description: IBLER target is used for SINR adjustment algorithm, which will affect
PUSCH MCS calculation
 Configuration impact:
 The larger IBLER target, MCS selection result will be larger, the theoretical throughput can be
improved, but retransmission ratio is also increased

 Configuration suggestion:
 For normal scenario, 10% is recommended to balance the MCS and retransmission ratio
 For peak throughput test scenario, if the radio environment is very good, we can try to increase
IBLER target to achieve higher throughput

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 74

 Summary

 NSA network related parameters optimization:

 MCG enhanced anchoring parameters
 SCG addition procedure related parameters optimization
 NSA UE VoLTE strategy
 NSA UE special mobility strategy

 Control plane performance optimization

 Radio timer optimization
 Access/mobility/retainablity related parameters optimization

 User plane performance optimization

 Downlink throughput related parameters
 Uplink throughput related parameters

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 75

Thank You
www.huawei.com