En-DC Enhancement (UniRAN22.2) 1112791

EN-DC Enhancement
Product Version: NR22.2
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P. R. China
Postcode:518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright ©2020 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties.
Any reproduction or distribution of this document or any portion of this document, in any
form by any means, without the prior written consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by contractual conﬁdentiality
obligations.
All company, brand and product names are trade or service marks, or registered trade or
service marks, of ZTE CORPORATION or of their respective owners.
This document is provided“as is”, and all express, implied, or statutory warranties,
representations or conditions are disclaimed, including without limitation any implied
warranty of merchantability, ﬁtness for a particular purpose, title or non-infringement. ZTE
CORPORATION and its licensors shall not be liable for damages resulting from the use of or
reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights
or applications covering the subject matter of this document. Except as expressly provided
in any written license between ZTE CORPORATION and its licensee, the user of this
document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product
without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire

related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Serial Number:2023-03-27
EN-DC Enhancement
EN-DC Enhancement
1 Introduction
This document is applicable to LTE FDD and TDD modes.
This document is applicable to 5G products. Both the "5G NR" and "gNodeB" mentioned in this document refer to 5G base stations, and
related network management system for 5G products is UME.
The NSA terminals mentioned in this document are all terminals that specifically refer to EN-DC capabilities.
1.1 Involve NEs
Involved NEs:
UE eNodeB MME S-GW gNodeB SGSN P-GW HSS
√ √ √ √ √ - - -
Note:
*-: Not involved
*√: involved
1.2 Change History
This section describes the changes between versions of the product, including two types of changes:
Technical changes: technical and related parameter changes between two versions.
Other changes: description and structure changes between versions, including content optimization and supplementation.
Compared with the previous versoin, LR21+ has the following changes:
Table 1-1 Technical and parameter changes
SN Section Technical Point Related Parameters
1 3.1.10 added counter Check. Add the alarm Add：

4.1.10 associated with Counter Check Switch for Counter Check Reporting
5.3 Reporting Threshold for Counter Check
Switch of PDCP COUNT check
PDCP COUNT check bit
2 3.1.11 Added NSA inter-frequency PSCell Add:

4.1.11 change based on uplink channel Switch of PSCell data quality‒based migration
quality. Waiting timer for migration measurement based on PSCell quality(s)
Maximum number of retries for PSCell quality‒based migration
Timer for retrying migration based on PSCell quality(s)
Reference for the NR measurement object index Index of inter-frequency
handover measurement configuration for PSCell quality‒based migration
Quality detection configuration purpose
Table 1-2 Other changes
SN Section Change Description
1 3.1.11 The description of the application scenarios of Counter Check is adjusted.
Flow control and data split is split from this document
Table 1-3 Parameter changes
Change Type Before change After change
1.3 Related Feature List and License Control
Table 1-4 LTE &5G Related Feature List
3 - 89
EN-DC Enhancement
No 4G Feature No. 4G Feature List Name License C Chapter 5G Feature List

ontrol No.
1 ZLF40-05-010 LTE 1CC+NR 1 band Downlink Dual NO 3.1.2 ZNR03-13-031

ZLT45-05-010 Connectivity LTE DL 1CC+NR DL 1CC Dual Connectivity
ZNR03-13-032
LTE DL 1CC+NR DL 4CC Dual Connectivity
ZNR03-13-038
LTE DL 1CC+NR DL 8CC Dual Connectivity

ZLT45-05-012 Connectivity LTE DL 2CC CA+NR DL 1CC Dual
Connectivity

Connectivity

Connectivity
5 ZLF40-05-015 Inter-site EUTRAN-NR Downlink Dual NO 3.1.3 N/A

ZLT45-05-015 Connectivity
6 ZLF40-05-016 LTE UL 1CC+NR UL 1 band Dual NO 3.1.2 ZNR03-13-036 LTE UL 1CC+NR UL 1CC
ZLT45-05-016 Connectivity Dual Connectivity
7 ZLF40-06-014 Flexible SN Configuration Strategy YES 3.1.4.1 N/A

ZLT45-06-014 based on the Traffic Requirement 3.1.4.3
8 ZLF40-04-010 Multi Factor Joint awared SN Handling YES 3.1.8 N/A

ZLT45-04-010 Enhancement for NSA
9 ZLF40-08-012 Uplink Power Control between EUTRAN NO 3.2. ZNR03-08-310 Uplink Power Control
ZLT45-08-012 and NR Between EUTRAN and NR
10 ZLF40-08-014 Dynamic Uplink Power Sharing for YES 3.2. ZNR03-08-165 Dynamic power sharing
ZLT45-08-014 EUTRAN and NR for EUTRAN and NR
11 ZLF40-08-013 Interference Suppressed Under No 3.3 ZNR03-20-011 Intermodulation and

EUTRAN-NR Dual Connectivity (Trial) harmonics interference avoidance (Trial)
1.4 Correlation with Other Feature
Table 1-5 Correlation with Other Feature
Feature ID Feature Name Required Feature Exclusive Fe Impacted Fe

ature ature
ZLF40-05-010 LTE 1CC+NR 1 band Downlink Dual Connectivity YES None None
ZLT45-05-010
ZLT45-05-012
ZLT45-05-013
ZLT45-05-014
ZLF40-05-015 Inter-site EUTRAN-NR Downlink Dual YES None None

ZLT45-05-015 Connectivity
ZLF40-05-016 LTE UL 1CC+NR UL 1 band Dual Connectivity YES None None

ZLT45-05-016
ZLF40-06-014 Flexible SN Configuration Strategy based on the ZLF40-03-009 Secondary Node None None
ZLT45-06-014 Traffic Requirement Handling Aspects
ZLF40-03-013 Inter-Frequency SN Change Procedure in NSA None None None

ZLT45-03-013
4 - 89
EN-DC Enhancement
ZLF40-03-017 Multi Factor Joint awared SN Handling ZLF40-03-009 Secondary Node None None
ZLT45-03-017 Enhancement for NSA Handling Aspects
ZLF40-08-012 Uplink Power Control between EUTRAN and NR None None None
ZLF45-08-012
ZLF40-08-014 Dynamic Uplink Power Sharing for EUTRAN and None None None
ZLT45-08-014 NR
ZLF40-08-013 Interference Suppressed Under EUTRAN-NR Dual None None None

Connectivity (Trial)
Note:
Dynamic Uplink Power Sharing for EUTRAN and NR is mutually exclusive with UL CA because if there are too many connections in the uplink,
the uplink coverage of the UE will be affected. Moreover, there are no terminals supporting NSA and UL CA at the same time.
1.4.1 ZLF40-05 LTE CA+NR Dual Connectivity
Required Feature:
■ ZLF34-00-015 Carrier Aggregation(Intra-Band, DL 2CC)
■ ZLF34-00-013 Carrier Aggregation (Inter-Band, DL 2CC)
■ ZLF34-00-017 Carrier Aggregation(DL 3CC)
■ ZLF34-00-055 Carrier Aggregation(DL 4CC of FDD)
■ ZLF40-01-010 EUTRAN-NR Dual Connectivity for Option3x
■ ZLF34-00-016 Carrier Aggregation(UL 2CC)
The LTE CA (Carrier Aggregation) and DC (Dual Connectivity) functions are uncoupled, and the DC features can superimpose the CA features to
increase the peak rate of the user.
Exclusive Feature:
None
Impacted Feature:
None
1.5 Technical Differences between FDD and TDD
Table 1-6 Technical differences between FDD and TDD
SN Technical Point FDD TDD Section
1 Interference Suppressed Under EUTRAN-NR Dual Connectivity (Trial) Support Not support 3.3
2 Function Description
Refer to LTE EN-DC Basic Function Feature Guide.
3 Technical Description
3.1 Part of Services
3.1.1 Technical Definitions
En-gNB: node providing NR user plane and control plane protocol terminations towards the UE, and acting as Secondary Node in EN-DC.
SN terminated bearer: in MR-DC, a radio bearer for which PDCP is located in the SN.
3.1.2 DC and CA Combination
DC (Dual Connectivity) and CA (Carrier Aggregation) can superimpose the peak traffic of the UE air interface. DC is processed at a PDCP
aggregation layer, the CA is at a MAC layer, the convergence point does not conflict, and the function implementation is not coupled.
5 - 89
EN-DC Enhancement
The current version supports five scenarios of LTE maximum 4CC + NR 1CC and LTE maximum 3CC + NR 2CC dual connectivity, including
1 LTE maximum 4CC + TDD NR 1CC,
2 LTE maximum 4CC + FDD NR 1CC,
3 LTE maximum 3CC + TDD NR 2CC,
4 LTE maximum 3CC + FDD NR 2CC,
5 LTE maximum 3CC + FDD NR 1CC(PSCell) + TDD NR 1CC.
The CA related policy for the NSA terminal is the same as that of the LTE terminal. For more details, refer to LTE Carrier Aggregation and NR
Carrier Aggregation Feature Guide.
■ After SN is added, eNodeB configures each carrier by using the MRDC capability information reported by UE.
■ After SN is deleted, eNodeB configures each carrier by using the LTE capability information reported by UE.
Figure 3-1 DC and CA combination
In the NSA scenario, the UE can obtain the traffic gain of the EN-DC first, and secondly, obtain the traffic gain through the CA to improve the
user experience. Therefore, it is necessary to coordinate the primary carrier frequency priority of the EN-DC function and the primary carrier
priority function of the CA. The CA primary carrier handover function includes Specify Pcell of UE According to Frequency Priority and CA
Spectrum Coordination.
NSA UE sends the NSA B1 measurement to UE, when the measurement timer is expired, the network can’t add the SN, and network should
be restore the CA switching function to obtain the traffic gain.
■ The NSA terminal does not take effect of the primary carrier switching function of the CA in the following scenarios:
■ The UE has configured the SN or performs the handover function with the SN.
■ The UE has issued the EN-DC anchor function measurement and Delay Start Timer for CA Anchoring Relative to EN-DC Anchoring
is started.
■ The network has sent the measurement of SN addition and Delay Start Timer for CA Anchoring Relative to SN Addition is started.
■ The NSA terminal needs to restore the primary carrier switching function of the CA in the following scenarios:
■ Delay Start Timer for CA Anchoring Relative to EN-DC Anchoring expired.
■ Delay Start Timer for CA Anchoring Relative to SN Addition expired.
Table 3-1 NSA Anchor handover Related Parameter
NO Parameter Name FDD Parameter TDD Parameter
1 Delay Start Timer for CA Anchoring Relative to ControlPlaneTimerLTE.cA4ENDCAnch ControlPlaneTimerLTE.cA4ENDCAnch

EN-DC Anchoring orDelayTimer orDelayTimer
2 Delay Start Timer for CA Anchoring Relative to ControlPlaneTimerLTE.cA4SNAddDela ControlPlaneTimerLTE.cA4SNAddDela

SN Addition yTimer yTimer
Note:
■ For the strategy of CA primary carrier handover function measurement delivery, see 3.7.3 Specify Pcell of UE According to Frequency
Priority and 3.7.7 CA Spectrum Coordination in LTE Carrier Aggregation Feature Guide.
6 - 89
EN-DC Enhancement
3.1.3 SN Change Penalty Suppression
3.1.3.1 gNB-level Penalty
The SN initiates the SN change flow. The SN sends the SgNB Change Required message to the MN to trigger the SN change. After receiving the
message, the MN judges that the X2 link between the MN and the target SN is not good or the X2 configuration is missing. The MN returns to
the SN an SgNB Change Refuse message, which carries cause as Transport Resource Unavailable. After receiving the message, the SN enables
the snChangePunishSwitch , and puts the MN+SN in the penalty blacklist. Before the Timer for SnChange becoming unavailable on the target
SN side expires, the MN+SN cannot be selected for change. After the timer expires, the penalty blacklist will be deleted. The MN+SN can be
selected normally.
For MN+SN, SN is represented by PLMN,gNBId,gNBIdLength 3-tuple, so this function needs to fully implement 3-tuple matching for penalty
suppression.
3.1.3.2 Cell-level Penalty
Cell-level penalty suppression includes penalty suppression due to navigation reasons and penalty suppression due to hardware load
reasons. The SN initiates the SN change flow. The SN sends the SgNB Change Required message to the MN to trigger the SN change. After
receiving the message, the MN sends the SgNB Addition Request message to the target SN. If the candidate cell of target SN is in the service
navigation status or high hardware load state, the target SN returns the SgNB Addition Request Reject message to the MN, carrying the
rejected cause. Then, the MN returns the SgNB Change Refuse message to the SN, carrying the rejected cause. After receiving the message, if
the first element of the Switch of SNChange cell-level punishment is enabled, put the NCGI of the target cell into the cell-level penalty
blacklist. Before the SNChange cell-level punishment timer expires, the cell cannot be selected. After the timer expires, delete the cell-level
penalty blacklist and normally select the cell as SN Change target cell.
Table 3-2 Parameters related to NR-side penalty suppression
No. Parameter Name FDD Parameter TDD Parameter
1 Timer for SnChange becoming unavailable on ControlPlaneTimer.snChangeTargetNo ControlPlaneTimer.snChangeTargetNo

the target SN side tAllowedTimer tAllowedTimer
2 snChangePunishSwitch GlobalSwitchInformation.snChangePu GlobalSwitchInformation.snChangePu

nishSwitch nishSwitch
3 SNChange cell-level punishment timer ControlPlaneTimer.snChangeCellPunis ControlPlaneTimer.snChangeCellPunis

hTimer hTimer
4 Switch of SNChange cell-level punishment GlobalSwitchInformation.snChangeCel GlobalSwitchInformation.snChangeCel

lPunishSwitch lPunishSwitch
3.1.4 Flexible SN Configuration Strategy based on the Traffic
3.1.4.1 SN Addition/Release Strategy
PDCP detection includes congestion-based load detection and traffic speed-based load detection.
The congestion-based policy only supports SN addition, but does not support SN release.
■ Before SN addition
If the congestion condition is met when an SN is not added, SN addition is triggered. If the service does not meet the congestion conditions,
SN addition is not triggered. If the eNB determines to add an SN, it can add SN based on measurement or blind SN addition.
The traffic speed-based policy supports SN addition and SN release.
■ Before SN addition
If the high traffic speed conditions are met, SN addition is triggered. If the service does not meet the high traffic speed conditions, SN addition
is not triggered. If the eNB determines to add an SN, it can add SN based on measurement or blind SN addition.
7 - 89
EN-DC Enhancement
■ After SN addition
If the low traffic speed conditions are met, SN deletion is triggered. If the service does not meet the low traffic speed conditions, SN deletion is
not triggered.
If the B1 measurement is delivered but the measurement report is not sent, and if the current decongestion/low traffic speed is detected, the
B1 measurement should also be deleted and the SN should not be added.
3.1.4.1.1 SN Addition Strategy Based on Scenarios
The load-based SN configuration policy varies in different scenarios:
1 In the access, handover-in and re-establishment scenarios, when configuring the traffic speed-based SN addition strategy, andRate-
Based Threshold Switch is closed, the UE is in high load state by default. And it can add SN based on measurement or blind SN addition
by PSCell Addition Strategy Indicator.
2 If the eNB detects that the UE is in the low load state before SN addition, SN is not added.
3 If the SN is deleted based on the traffic speed after the SN is added, EN-DC SN Configuration Mode is set to “Traffic Speed Based”,
the SN can be added again by PSCell Addition Strategy Indicator, only after the UE is detected to be overloaded.
4 If the SN is deleted based on the coverage after the SN is added, the SN will be added immediately as soon as the coverage
condition is satisfied (the default load is always satisfied because the low load is not detected during this process).
Table 3-3 LTE Parameters related to Rate-Based Threshold Switch
1 Rate-Based Threshold Switch ENDCPolicyFDDLTE.baseRateThresholdSwch ENDCPolicyTDDLTE.baseRateThresholdSwch
2 EN-DC SN Configuration Mode ENDCPolicyFDDLTE.enDcSnConfigMod ENDCPolicyTDDLTE.enDcSnConfigMod
3 PSCell Addition Strategy ENDCPolicyFDDLTE.pSCellAddStgyInd ENDCPolicyTDDLTE.pSCellAddStgyInd

Indicator
3.1.4.2 Congestion-Based PDCP Detection (Only for Test)
PDCP congestion identification mainly determines by the PDCP status, providing the basis for subsequent service functions, for example, SN
addition based on services. NSA UE is configured as a non-MCG bearer. When the congestion of this bearer occurs, the traffic speed of this
bearer is considered large, and the network can configure dual connectivity for this UE.
PDCP congestion identification includes: PDCP waiting delay and PDCP buffer percentage-based congestion identification. If one of the
conditions is congested, the congestion is marked. If all the conditions are cleared, the congestion is removed.
Figure 3-2 PDCP congestion identification
■ Congestion identification based on PDCP waiting delay
■ When the number of PDCP packets waiting delay is consecutive N times greater than A, the state will be marked as congested.
■ When the number of PDCP packets waiting delay is consecutive N times less than B, the state will be marked as decongested.
8 - 89
EN-DC Enhancement
N: Number of Consecutive Packet-Based Congestion Decisions(4G)/ Threshold number of congestion decisions based on the PDCP packet
waiting time (5G)
A:PDCP Delay Threshold for Congestion Occurrence(ms)(4G)/PDCP delay threshold in the case of bearer congestion (5G)
B: PDCP Delay Threshold for Triggering Decongestion(ms)(4G)/PDCP delay threshold in the case of bearer decongestion (5G)
■ Congestion based on PDCP buffer ratio
■ When the number of PDCP buffer ratio is consecutive N times greater than the A，the state will be marked as congested.
■ When the number of PDCP buffer ratio is consecutive N times less than B， the state will be marked as uncongested.
N: Number of Congestion Decisions Based on the Cache Occupancy Ratio(4G)/Threshold number of congestion decisions based on the PDCP
cache occupation ratio (5G)
A: PDCP Cache Occupancy Ratio Threshold for Congestion Occurrence(4G)/ PDCP layer cache occupation ratio threshold in the case of bearer
congestion (5G)
B: PDCP Cache Occupancy Ratio Threshold for Triggering Decongestion(4G)/ PDCP layer cache occupation ratio threshold in the case of
bearer decongestion (5G)
Table 3-4 LTE Parameters related to PDCP Congest Detection
No. Parameter Name Parameter
1 PDCP Delay Threshold for Congestion Occurrence(ms) PdcpStatusLTE.congestDelayThr
2 PDCP Delay Threshold for Triggering Decongestion(ms) PdcpStatusLTE.uncongestDelayThr
3 PDCP Cache Occupancy Ratio Threshold for Congestion Occurrence PdcpStatusLTE.congestCacheThr
4 PDCP Cache Occupancy Ratio Threshold for Triggering Decongestion PdcpStatusLTE.uncongestCacheThr
5 Number of Consecutive Packet-Based Congestion Decisions PdcpStatusLTE.pktCongestDecisionTimes
6 Number of Congestion Decisions Based on the Cache Occupancy Ratio PdcpStatusLTE.cacheRatioCongesTimes
7 PDCP Status Identification Index PdcpStatusLTE.pdcpStatusIdentifyIndex
Table 3-5 NR Parameters related to PDCP Congest Detection
1 PDCP delay threshold in the case of bearer congestion PDCPStatusCfg.congestDelayThr
2 PDCP delay threshold in the case of bearer decongestion PDCPStatusCfg.uncongestDelayThr
3 PDCP layer cache occupation ratio threshold in the case of bearer congestion PDCPStatusCfg.congestCacheThr
4 PDCP layer cache occupation ratio threshold in the case of bearer PDCPStatusCfg.uncongestCacheThr
decongestion
5 Threshold number of congestion decisions based on the PDCP packet waiting PDCPStatusCfg.pktCongestDecisionTimes
time
6 Threshold number of congestion decisions based on the PDCP cache PDCPStatusCfg.cacheRatioCongestDecisionTi

occupation ratio mes
7 PDCP status index PDCPStatus.pdcpIndex
3.1.4.3 Traffic Speed-Based PDCP Detection
The TrafficSpeed-based PDCP identification determines by the uplink and downlink PDCP incoming packet rates.
When the uplink PDCP packet rate is higher than A for consecutive N times, or the downlink PDCP packet rate is higher than B for consecutive
N times, the PDCP packet rate is determined as the high service load state.
N: Number of High-Speed Decisions(4G)/ Number of high-speed decisions (5G)
A:Upper Threshold of the UL Traffic Speed(4G)/Upper threshold of uplink speed(Bps)(5G)
B:High Threshold of the DL Traffic Speed(4G)/Upper threshold of downlink speed(Bps)(5G)
When the uplink PDCP packet rate is lower than A for consecutive N times, and the downlink PDCP packet rate is lower than B for consecutive
9 - 89
EN-DC Enhancement
N times, the PDCP packet rate is determined as the low service load state.
N: Number of Low-Speed Decisions (4G)/ Number of high-speed decisions (5G)
A: Lower Threshold of the UL Traffic Speed(4G)/ Lower threshold of uplink speed(Bps) (5G)
B:Lower Threshold of the DL Traffic Speed (4G)/ Lower threshold of downlink speed(Bps)(5G)
Table 3-6 LTE Parameters related to PDCP Traffic Detection
1 Number of High-Speed Decisions PdcpStatusLTE.highTrafficSpeedDesTime
2 High Threshold of the DL Traffic Speed PdcpStatusLTE.dlTrafficSpeedHighThrd
3 Upper Threshold of the UL Traffic Speed PdcpStatusLTE.ulTrafficSpeedHighThrd
4 Number of Low-Speed Decisions PdcpStatusLTE.lowTrafficSpeedDesTime
5 Lower Threshold of the DL Traffic Speed PdcpStatusLTE.dlTrafficSpeedLowThrd
6 Lower Threshold of the UL Traffic Speed PdcpStatusLTE.ulTrafficSpeedLowThrd
7 PDCP Status Identification Index PdcpStatusLTE.pdcpStatusIdentifyIndex
Table 3-7 NR Parameters related to PDCP Traffic Detection
1 Number of high-speed decisions PDCPStatusCfg.highTrafficSpeedDecisionTimes
2 Upper threshold of downlink speed(Bps) PDCPStatusCfg.dlTrafficSpeedHighThrd
3 Upper threshold of uplink speed(Bps) PDCPStatusCfg.ulTrafficSpeedHighThrd
4 Number of low-speed decisions PDCPStatusCfg.lowTrafficSpeedDecisionTimes
5 Lower threshold of downlink speed(Bps) PDCPStatusCfg.dlTrafficSpeedLowThrd
6 Lower threshold of uplink speed(Bps) PDCPStatusCfg.ulTrafficSpeedLowThrd
7 PDCP status index PDCPStatus.pdcpIndex
Table 3-8 NR Parameters related to rate-based SN deletion switch
1 Rate-based SN deletion switch EnDCCtrl.ratebasedSnDelSwitch
3.1.5 Ping-Pong Prevention Policy for PSCell Change
In the NSA scenario, the UE will be handed over back and forth between two PSCells or SNs in a short time due to improper network coverage
or handover threshold setting. In order to suppress such Ping-Pong handover, the UE will not be allowed to return to the latest resided PSCell
during a certain period of time.
That is to say, when the Switch of the Ping-Pong prevention policy for PSCell change is open, and the PSCell or SN changes, if the cell that the
UE camps on for the latest time within the Timer for Ping-Pong prevention in PSCell change is the target cell for handover, the eNodeB does
not select this cell as the target cell for handover. In this way, Ping-Pong handover can be suppressed.
Table 3-9 NR Parameters related to Ping-Pong Handover Prevention
1 Switch of the ping-pong prevention policy for PSCell change EnDCCtrl.pscellChangePrePingPongSwch
2 Timer for ping-pong prevention in PSCell change EnDCCtrl.pscellChangePrePingPongTimer
3.1.6 SN Addition Punishment
3.1.6.1 SN Addition Punishment Triggered by SCG Failure
To reduce the influence of the UE that occurs SCG Failure frequently after SN addition on the network KPI, the eNodeB will punish this type of
10 - 89
EN-DC Enhancement
abnormal UEs not to add SN.

When SCG Failure Punishment Switch is Open, after the UE SN is added, the UE will be punished when the UE SCG Failure times reaches
Threshold Number of SCG Failure Detections within SCG Failure Detection Duration(s). The UE cannot perform SN addition within theSCG
Failure Punishment Duration(s). When SCG Failure Punishment Duration(s) expires, if the PSCell Addition Strategy Indicator is set to “Based
Measurement”, the UE can perform SN addition in measurement mode. If the PSCell Addition Strategy Indicator is set to “Based Blind and
Measurement”, the UE can perform SN addition in blind mode, if the SN addition fails in blind mode, the UE perform SN addition in
measurement mode.
Table 3-10 SN addition Punishment Triggered by SCG Failure related Parameters
1 SCG Failure Punishment Switch ENDCPolicyFDDLTE.sCGFailurePunishSw ENDCPolicyTDDLTE.sCGFailurePunishSwc

ch h
2 SCG Failure Detection Duration(s) ENDCPolicyFDDLTE.sCGFailureDetectDur ENDCPolicyTDDLTE.sCGFailureDetectDur

ation ation
3 Threshold Number of SCG Failure ENDCPolicyFDDLTE.sCGFailureDetectTim ENDCPolicyTDDLTE.sCGFailureDetectTim

Detections es es
4 SCG Failure Punishment Duration(s) ENDCPolicyFDDLTE.sCGFailurePunishDur ENDCPolicyTDDLTE.sCGFailurePunishDur

ation ation
3.1.6.2 Punishment for SN Configuration Failure
During SN configuration procedure, when the SN addition is rejected due to reasons such as unavailable resources and RRC user number
limitation, then SN configuration success rate is low. To solve this problem, we can punish NR cells which fail to be added as SN to improve
the SN configuration success rate and reduce invalid signaling overheads.
This function is controlled by Punishment Switch for SN Configuration Failures. If this switch is configured to “Open”, the corresponding
punishment strategy will be started based on the failure cause if an SN configuration failure cell is detected.
The parameter of Punishment Strategy for Special Cause Values of SN Configuration Failures indicate the punishment strategies for special
cause values of SN configuration failures.
The parameter of Punishment Strategy for Ordinary Cause Value of SN Configuration Failures indicate the punishment strategy for the
ordinary cause values of SN configuration failures.
If the SN configuration fails and the failure cause punishment strategy is set to time punishment strategy in the parameter ofPunishment
Strategy for Special Cause Values of SN Configuration Failures or Punishment Strategy for Ordinary Cause Value of SN Configuration Failures,
the punishment will be started for NR cell.
The specific punishment measures are as follows:
1 Once SN configuration failure is detected and the failure cause punishment strategy is set to “time punishment strategy” in the
parameter of Punishment Strategy for Special Cause Values of SN Configuration Failures or Punishment Strategy for Ordinary Cause
Value of SN Configuration Failures, the Level-1 Punishment Timer for SN Configuration Failures will be started for the NR cell. During the
execution of the Level-1 Punishment Timer for SN Configuration Failures, any UE in the eNB cannot trigger the SN addition procedure of
the NR cell. If the Level-1 Punishment Timer for SN Configuration Failures expires, the Level-2 Detection Timer for SN Configuration
Failures will be started for the NR cell, and allow every UE in the eNodeB to trigger the procedure of adding the NR cell as an SN.
2 Once SN configuration failure is detected during the execution of Level-2 Detection Timer for SN Configuration Failures and the
failure cause punishment strategy is set to “time punishment strategy” in the parameter of Punishment Strategy for Special Cause
Values of SN Configuration Failures or Punishment Strategy for Ordinary Cause Value of SN Configuration Failures, the Level-2
Punishment Timer for SN Configuration Failures will be started for the NR cell. During the execution of the Level-2 Punishment Timer for
SN Configuration Failures, any UE in the eNB cannot trigger the SN addition procedure of the NR cell. If theLevel-2 Punishment Timer for
SN Configuration Failures expires, the Level-3 Detection Timer for SN Configuration Failures will be started for the NR cell, and every UE in
the eNodeB can trigger the procedure of adding the NR cell as an SN.
3 Once SN configuration failure is detected during the execution of Level-3 Detection Timer for SN Configuration Failures and the
11 - 89
EN-DC Enhancement
failure cause punishment strategy is set to time punishment strategy in the parameter of Punishment Strategy for Special Cause Values of
SN Configuration Failures or Punishment Strategy for Ordinary Cause Value of SN Configuration Failures, the Level-3 Punishment Timer
for SN Configuration Failures will be started for the NR cell. During the execution of the Level-3 Punishment Timer for SN Configuration
Failures, any UE in the eNB cannot trigger the SN addition procedure of the NR cell. If theLevel-3 Punishment Timer for SN Configuration
Failures expires, the Level-3 Detection Timer for SN Configuration Failures will be started for the NR cell, and every UE in the eNodeB can
trigger the procedure of adding the NR cell as an SN.
Note:
1 If the NR cell does not be detected any SN addition failure with the failure cause punishment strategy is set to time punishment
strategy in the parameter of Punishment Strategy for Special Cause Values of SN Configuration Failures or Punishment Strategy for
Ordinary Cause Value of SN Configuration Failures during the detection timer, SN configuration failure detection will be performed for the
upper-level detection duration, and the punishment duration of the corresponding level will be executed.
Table 3-11 SN Configuration Failure Punishment related parameters
1 Punishment Switch for SN Configuration Failures GlobalPunishLTE.sNConfigFailPunishSwch
2 Punishment Strategy for Special Cause Values of SN Configuration Failures GlobalPunishLTE.specCauseSNPunishStgy
3 Punishment Strategy for Ordinary Cause Value of SN Configuration Failures GlobalPunishLTE.normCauseSNPunishStgy
4 Level-1 Punishment Timer for SN Configuration Failures GlobalPunishLTE.level1SNPunishTimer
5 Level-2 Detection Timer for SN Configuration Failures GlobalPunishLTE.level2SNDetectTimer
7 Level-3 Detection Timer for SN Configuration Failures GlobalPunishLTE.level3SNDetectTimer
3.1.7 SN Coverage-Based SPID Policy
The coverage-based SPID policy can provide customized services based on the SPID of a user.
When the EN-DC SPID switch is open, the SPID of the UE will be compared with the SPID configured in the Label number of SPID list. If the
SPID of the UE exists in the list, the EN-DC Inter-frequency PSCell Change Switch will be used to judge whether the current UE supports inter-
frequency replacement.
■ When the EN-DC Inter-frequency PSCell Change Switch is open, this UE supports inter-frequency change.
■ When the EN-DC Inter-frequency PSCell Change Switch is close, this UE does not support inter-frequency change.
For inter-frequency replacement, please refer to LTE EN-DC Basic Function s.

Table 3-12 Parameters Related To Coverage-Based SPID Management Policy
1 EN-DC SPID switch EnDcCoverage.endcCoverageSpidSwch
2 EN-DC Inter-frequency PSCell Change Switch EnDcCoverageSPIDProfiles.endcPSCellInterFChangeSwch
3 Label number of SPID list EnDcCoverageSPIDProfiles.spidList
3.1.8 Multi Factor Joint awared SN Handling Enhancement for NSA
In the NSA/SA border area, if there exists interference in the NSA and SA cells, the signal strength and interference strength should be
considered during SN addition. Therefore, the SN addition strategy based on joint decision is provided, so that the eNodeB can select good
NR neighbor cells for the UE to perform dual connections to improve user experience.
The eNodeB processes the measurement reports in the following procedures, filters out the NR neighbor cells that do not meet the joint
12 - 89
EN-DC Enhancement
decision threshold, and does not initiate the SN addition procedure for the neighbor cells.
■ The measurement report of SN addition reported by UE
■ During the handover with SN, the measurement report carried from the handover source side to the target side.
The joint decision supports RSRP+RSRQ joint decision and RSRP+SINR joint decision. The following describes the two joint decision policies.
3.1.8.1 RSRP+RSRQ Joint Decision
1 When the Measurement Quantity of the NR System configured in the measurement report corresponding to the NR Inter-RAT
Measurement Index for SN Addition in ENDC is set to "rsrp", if the following conditions should be met at the same time, the joint decision
policy takes effect:
■ The first element of the Joint Decision Switch for EN-DC SN Addition is configured as "RSRP+RSRQ joint judgment".
■ The first(RSRP) and second(RSRQ) elements of the Measurement Report Quantity of the NR System in the measurement report
configuration corresponding to the NR Inter-RAT Measurement Index for SN Addition in ENDC are selected.
The NR neighbor cells meeting the following conditions are filtered by joint decision policy:
■ The neighbor cell in the UE measurement report contains the RSRQ measurement result, and the RSRQ is less thanRSRQ Threshold for
NR Neighbor Cells in Joint Decision for EN-DC SN Addition.
1 When the Measurement Quantity of the NR System configured in the measurement report corresponding to the NR Inter-RAT
Measurement Index for SN Addition in ENDC is set to "rsrq", if the following conditions should be met at the same time, the joint decision
policy takes effect:
■ The second element of the Joint Decision Switch for EN-DC SN Addition is configured as "RSRP+RSRQ joint judgment".
■ The first(RSRP) and second(RSRQ) elements of the Measurement Report Quantity of the NR System in the measurement report
■ The neighbor cell in the UE measurement report contains the RSRP measurement result, and the RSRP is less thanRSRP Threshold for
3.1.8.2 RSRP+SINR Joint Decision
When the Measurement Quantity of the NR System configured in the measurement report corresponding to the NR Inter-RAT Measurement
Index for SN Addition in ENDC is set to "rsrp", if the following conditions should be met at the same time, the joint decision policy takes effect:
■ The first element of the Joint Decision Switch for EN-DC SN Addition is configured as "RSRP+SINR joint judgment".
■ The first(RSRP) and third(SINR) elements of the Measurement Report Quantity of the NR System in the measurement report
■ The neighbor cell in the UE measurement report contains the SINR measurement result, and the SINR is less thanSINR Threshold for
Note:
■ Joint decision of SN addition for which the Measurement Quantity of the NR System is SINR is not supported.
■ The 4G and 5G joint decision functions need to be enabled at the same time. If only the 5G function is enabled but the 4G function is
not enabled or the 4G version does not support the joint decision, the related indicators will fluctuate.
13 - 89
EN-DC Enhancement
■ The RSRP+SINR joint decision policy cannot take effect for the terminals that do not support measuring NR SINR in LTE.
Table 3-13 Parameters Related To SN addition Policy based on Joint Decision
1 NR Inter-RAT Measurement Index for SN Addition in CellMeasGroupLTE.nRSNRatAddMeasCfg

ENDC
2 Measurement Quantity of the NR System NrRatMeasCfgLTE.quantityNR
3 Measurement Report Quantity of the NR System NrRatMeasCfgLTE.rpQuantityNRbitmap
4 Joint Decision Switch for EN-DC SN Addition ENDCPolicyFDDLTE.endcJointJu ENDCPolicyTDDLTE.endcJointJud

dgeSwch geSwch
5 RSRP Threshold for NR Neighbor Cells in Joint Decision NRFreqParaFDDLTE.snAddJointJ NRFreqParaTDDLTE.snAddJointJ

for EN-DC SN Addition udgeRsrpThrd udgeRsrpThrd
6 RSRQ Threshold for NR Neighbor Cells in Joint Decision NRFreqParaFDDLTE.snAddJointJ NRFreqParaTDDLTE.snAddJointJ

for EN-DC SN Addition udgeRsrqThrd udgeRsrqThrd
7 SINR Threshold for NR Neighbor Cells in Joint Decision NRFreqParaFDDLTE.snAddJointJ NRFreqParaTDDLTE.snAddJointJ

for EN-DC SN Addition udgeSinrThrd udgeSinrThrd
3.1.9 NR Multi-Measurement and Joint Decision Strategy
3.1.9.1 NR Multi-Measurement Strategy
The gNodeB supports multiple measurements at the same time. Where, RSRP is the basic measurement, and then an RSRQ or SINR
measurement is added. After receiving any measurement report message, the gNodeB can trigger the corresponding NSA procedure. The
functions are controlled by the EN-DC multi-measurement strategy.
■ If the policy is set to "Close", the function is disabled.
■ When the policy is set to "RsrpAndRsrq", the RSRQ measurement will be delivered while the RSRP measurement is delivered.
■ When the policy is set to "RsrpAndSinr", the SINR measurement will be delivered while the RSRP measurement is delivered.
Both SN release and intra-frequency and inter-frequency change support multiple measurement policies.
Note:
■ If the multi-measurement policy is enabled, the event trigger quantity configured in the default measurement report must be RSRP.
■ The multi-measurement policy and the joint decision function must be enabled at the same time. Otherwise, Ping-Pong handovers
may occur, affecting user experience.
Table 3-14 Parameters Related To NR multi-measurement strategy
1 EN-DC multi-measurement strategy EnDcCoverage.endcMultMeasStgy
2 Index of the A2 measurement configuration for SN cell release based on RSRQ EnDcCoverageIntraFMeasConfig.refNRDcR
elPSCellA2RSRQ
3 Index of the A2 measurement configuration for SN cell release based on SINR EnDcCoverageIntraFMeasConfig.refNRDcR
elPSCellA2SINR
4 Index of the event A measurement configuration for triggering intra-frequency EnDcCoverageIntraFMeasConfig.refNRPSC

PSCell change based on RSRQ in EN-DC scenarios ellChangeIntraFRSRQ
5 Index of the event A measurement configuration for triggering intra-frequency EnDcCoverageIntraFMeasConfig.refNRPSC

PSCell change based on SINR in EN-DC scenarios ellChangeIntraFSINR
6 Index of the A1/A2 measurement configuration for inter-frequency PSCell change EnDcCoverageIntraFMeasConfig.refInterFP
based on RSRQ in EN-DC scenarios SCellChangeA1A2RSRQ
14 - 89
EN-DC Enhancement
7 Index of the A1/A2 measurement configuration for inter-frequency PSCell change EnDcCoverageIntraFMeasConfig.refInterFP
based on SINR in EN-DC scenarios SCellChangeA1A2SINR
8 Index of the event A measurement configuration for triggering inter-frequency EnDcCoverageInterFMeasConfig.refNRPSC

PSCell change based on RSRQ in EN-DC scenarios ellChangeInterFRSRQ
9 Index of the event A measurement configuration for triggering inter-frequency EnDcCoverageInterFMeasConfig.refNRPSC

PSCell change based on SINR in EN-DC scenarios ellChangeInterFSINR
3.1.9.2 NR Joint Decision Policy
The gNodeB can use the joint decision policy to ensure that the signal strength and channel interference are considered during the mobility
decision procedure to improve user experience. This function is controlled by the Joint decision strategy in EN-DC. It supports RSRP+RSRQ
joint decision and RSRP+SINR joint decision.
In the case of joint decision, the number of reported times of measurement reports must be greater than one. If the number of reported times
of measurement reports is one, the gNodeB does not execute the joint decision policy, but initiates the mobility procedure in accordance with
the non-joint decision procedure.
During the joint decision process, the MR reordering function is supported. If Switch for Measurement Report Reordering is set to Open, the
gNodeB preferentially initiates a change to a cell with a better SINR, and initiates a change to a cell with a better RSRQ when the SINR is the
same. If this parameter is set to "Close," the gNodeB will make a decision based on the reporting sequence of the UE.
3.1.9.2.1 RSRP+RSRQ Joint Decision
When the first left element of the Joint decision strategy in EN-DC is set to "RSRP+RSRQ", it indicates that the measurement report with the
triggered quantity of RSRP will make joint decision according to the RSRP+RSRQ strategy. When the second element is set to "RSRP+RSRQ", it
indicates that the measurement report with the triggered quantity of RSRQ will make joint decision according to the RSRP+RSRQ strategy.
The joint decision policy of RSRP+RSRQ is as follows:
■ When the triggering quantity is RSRP, SN Change or Pscell Change can be initiated when the RSRQ value of the neighbor cell is greater
than the RSRQ threshold for joint decision on NR neighbor cells in EN-DC scenarios. When the best RSRQ value of the neighbor cell is
smaller than the RSRQ threshold for joint decision on NR neighbor cells in EN-DC scenarios, and the RSRP of the serving cell is smaller
than the RSRP threshold for joint decision on the NR serving cell in EN-DC scenarios or the RSRQ of the serving cell is smaller than the
RSRQ threshold for joint decision on the NR serving cell in EN-DC scenarios, SN Change or Pscell Change can also be initiated.
■ When the triggering quantity is RSRQ, SN Change or Pscell Change can be initiated when the RSRP value of the neighbor cell is greater
than the RSRP threshold for joint decision on NR neighbor cells in EN-DC scenarios. When the best RSRP value of the neighbor cell is
smaller than the RSRP threshold for joint decision on NR neighbor cells in EN-DC scenarios, and the RSRP of the serving cell is smaller
than the RSRP threshold for joint decision on the NR serving cell in EN-DC scenarios or the RSRQ of the serving cell is smaller than the
RSRQ threshold for joint decision on the NR serving cell in EN-DC scenarios, SN Change or Pscell Change can also be initiated.
3.1.9.2.2 RSRP+SINR joint decision
When the first left element of the Joint decision strategy in EN-DC is set to "RSRP+SINR", it indicates that the measurement report with the
triggered quantity of RSRP will make joint decision according to the RSRP+SINR strategy. When the third element is set to "RSRP+SINR", it
indicates that the measurement report with the triggered quantity of SINR will make joint decision according to the RSRP+SINR strategy.
The joint decision policy of RSRP+SINR is as follows:
■ When the triggering quantity is RSRP, SN Change or Pscell Change can be initiated when the SINR value of the neighbor cell is greater
than the SINR threshold for joint decision on NR neighbor cells in EN-DC scenarios. When the best SINR value of the neighbor cell is
smaller than the SINR threshold for joint decision on NR neighbor cells in EN-DC scenarios, and the RSRP of the serving cell is smaller
than the RSRP threshold for joint decision on the NR serving cell in EN-DC scenarios or the SINR of the serving cell is smaller than theSINR
threshold for joint decision on the NR serving cell in EN-DC scenarios, SN Change or Pscell Change can also be initiated.
15 - 89
EN-DC Enhancement
■ When the triggering quantity is SINR, SN Change or Pscell Change can be initiated when the RSRP value of the neighbor cell is greater
than the RSRP threshold for joint decision on NR neighbor cells in EN-DC scenarios. When the best RSRP value of the neighbor cell is
smaller than the RSRP threshold for joint decision on NR neighbor cells in EN-DC scenarios, and the RSRP of the serving cell is smaller
than the RSRP threshold for joint decision on the NR serving cell in EN-DC scenarios or the SINR of the serving cell is smaller than theSINR
threshold for joint decision on the NR serving cell in EN-DC scenarios, SN Change or Pscell Change can also be initiated.
Table 3-15 Parameters Related To NR Joint Decision Policy
1 Joint decision strategy in EN-DC EnDcCoverage.endcUnitJudgStgy
2 RSRP threshold for joint decision on NR neighbor cells in EN-DC EnDcCoverageIntraFMeasConfig.endcUnitJudgNbRSRPT

scenarios hrd
3 RSRQ threshold for joint decision on NR neighbor cells in EN-DC EnDcCoverageIntraFMeasConfig.endcUnitJudgNbRSRQT

scenarios hrd
4 SINR threshold for joint decision on NR neighbor cells in EN-DC EnDcCoverageIntraFMeasConfig.endcUnitJudgNbSINRT

scenarios hrd
5 RSRP threshold for joint decision on the NR serving cell in EN-DC EnDcCoverageIntraFMeasConfig.endcUnitJudgSrvRSRPT
scenarios hrd
6 RSRQ threshold for joint decision on the NR serving cell in EN-DC EnDcCoverageIntraFMeasConfig.endcUnitJudgSrvRSRQ
scenarios Thrd
7 SINR threshold for joint decision on the NR serving cell in EN-DC EnDcCoverageIntraFMeasConfig.endcUnitJudgSrvSINRT
scenarios hrd
8 RSRP threshold for joint decision on NR neighbor cells in EN-DC EnDcCoverageInterFMeasConfig.endcUnitJudgNbRSRPT

scenarios hrd
9 RSRQ threshold for joint decision on NR neighbor cells in EN-DC EnDcCoverageInterFMeasConfig.endcUnitJudgNbRSRQT

scenarios hrd
10 SINR threshold for joint decision on NR neighbor cells in EN-DC EnDcCoverageInterFMeasConfig.endcUnitJudgNbSINRT

scenarios hrd
11 Switch for Measurement Report Reordering MobilityCtrl.measReportReorderSwch
3.1.10 Counter Check
The counter check process can be used to detect the attack of maliciously inserting uplink and downlink packets during radio transmission,
which is helpful to guarantee network security. The eNB determines whether there is the risk of air interface attack by confirming with the UE
the difference of the uplink and downlink COUNT values of the PDCP.
In the EN-DC scenario, the counter check process of SCG bearer or SCG Split bearer is triggered by SgNB, and interaction is completed
between MeNB and UE.
Figure 3-3 EN-DC Counter Check flow
After the SN is added, if Switch of PDCP COUNT check of the SgNB is open, when the PDCP of the SCG bearer or SCG Split bearer detects that
PDCP COUNT check bit of the uplink or downlink COUNT value changes from 0 to 1, the SgNB sends the SgNBCounterCheckRequest message
to the MeNB, carrying the uplink and downlink COUNT value of the PDCP of this bearer.
Upon receiving the SgNBCounterCheckRequest message, the MeNB sends the CounterCheck message to the UE. After receiving the
CounterCheck message, the UE compares the PDCP COUNT value in the message with the local PDCP COUNT value of the corresponding DRB.
If the high bit bits of the two values are different, the different PDCP COUNT values will be contained in the CounterCheckResponse message
and returned to the MeNB.
16 - 89
EN-DC Enhancement
If the CounterCheckResponse received by the MeNB does not contain the PDCP COUNT value or the bearers containing the PDCP COUNT
value are not bearers that send CounterCheck, the process ends. If the bearers containing the PDCP COUNT value returned by the UE include
bearers that send CounterCheck, compare the difference between the PDCP uplink/downlink COUNT value returned by the UE and the PDCP
uplink/downlink COUNT value at the SgNB side. If the difference exceeds Reporting Threshold for Counter Check, and Switch for Counter
Check Reporting is open, the MeNB reports an alarm to the UME.
Note:
■ MCG bearer does not serve as Counter Check; SCG bearer and SCG Split bearer do not serve as Counter Check before or after SN
addition and SN deletion

■ Only threshold-based detection is performed, and the periodical detection is not performed.
■ CounterCheck is triggered by a single DRB. The drb-CountMSB-InfoList carried by the UE each time contains only one DRB. Before the
Counter Check procedure of a DRB ends, the Counter Check messages originated by other DRBs of the UE will be discarded inside MeNB.
Table 3-16 Counter Check related parameters
1 Switch for Counter Check Reporting GlobalQoSLTE.counterCheckRptSwch
2 Reporting Threshold for Counter Check GlobalQoSLTE.counterCheckRptThrd
3 Switch of PDCP COUNT check EnDCPDCP.pdcpCounterCheckSwitch
4 PDCP COUNT check bit EnDCPDCP.pdcpCounterCheckBit
3.1.11 NSA Inter-Frequency PSCell Change based on Uplink Channel Quality
NSA multi-frequency networking supports inter-frequency PSCell change based on uplink channel quality, also supports intra-SgNB PScell
change and Inter-SgNB SN change. For example, in the dual frequency point networking of NSA N78 + N28, the uplink coverage of 3.5G
frequency band is limited, but the downlink coverage of 3.5G frequency band still has spare power. Therefore, the inter-frequency PSCell
change from N78 to N28 based on uplink channel quality is triggered to turn N28 into the primary carrier, and the N78 downlink coverage is
extended with the help of N28 uplink feedback. For the UE not supporting CA function, the inter-frequency PSCell change from N78 to N28
based on uplink channel quality also can be triggered.
When Switch of PSCell data quality‒based migration is open and Quality detection configuration purpose is configured as
“PSCellChangeBaseDataQual”, if NR detects that the uplink channel quality becomes worse (the measurement quantity of uplink channel
quality is SingleRbSinr), it will deliver inter-frequency measurement based on uplink channel quality and start Waiting timer for migration
measurement based on PSCell quality(s). If the UE reports the measurement report within waiting timer for migration measurement, it will
trigger inter-frequency PSCell change.. Otherwise, if the timer times out, delete the inter-frequency measurement based on uplink channel
quality.
If number of retries for migration dose not reach Maximum number of retries for PSCell quality‒based migration, start Timer for retrying
migration based on PSCell quality(s). If the retry timer times out, redeliver the measurement.
Table 3-17 NSA inter-frequency PSCell change based on uplink channel quality related parameters
1 Switch of PSCell data quality‒based migration PSCellDataQualMig.pscellDataQualMigSwch
2 Waiting timer for migration measurement based on PSCell quality(s) PSCellDataQualMig.pscellDataQualMigMeasTimer
3 Maximum number of retries for PSCell quality‒based migration PSCellDataQualMig.pscellDataQualMigMaxRetryNu

m
4 Timer for retrying migration based on PSCell quality(s) PSCellDataQualMig.pscellDataQualMigRetryTimer
5 Reference for the NR measurement object index PSCellDataQualMigInterFMeasCfg.refInterFMeasOb

ject
17 - 89
EN-DC Enhancement
6 Index of inter-frequency handover measurement configuration for PSCell PSCellDataQualMigInterFMeasCfg.refPSCellDataQ

quality‒based migration ualMigRptCfg
7 Inter-frequency frequency point priority for PSCell quality‒based migration PSCellDataQualMigInterFMeasCfg.pscellDataQual

MigInterFreqPrio
8 Quality detection configuration purpose DataQualDetect.dataQualDetectUtility
3.2 Uplink Power Control for EUTRAN and NR
In EUTRAN-NR Dual Connectivity, the uplink power control on LTE side is independent from NR when an NSA UE initially accesses an NSA
anchoring cell. The uplink power control over EN-DC UE is the same as LTE UE, and UE maximum uplink transmission power is 23 dBm.
3.2.1 High Power of NSA Cells
Generally, the maximum uplink transmit power of the UE is 23 dBm.

As stipulated in the protocol, when the powerClass-V1530 field in the BandCombinationList of the UE capability IE reports pc2, it indicates that
the UE capability supports PowerClass 2. For details, see 3GPP TS 38.331 Section 6.3.3.
For the LTE+NR band combination that supports high power(1A+78A,1A+41A, 3A+41A, 3A+78A, 7A+78A, and 28A+78A), if the UE capability
supports PowerClass 2 and the High Power Switch of NSA cells is configured to Open, the maximum uplink transmit power of the UE is 26
dBm.
It should be noted that the maximum transmit power at the LTE side is 23 dBm. If the UE does not support PowerClass 2 or theHigh Power
Switch of NSA cells is disabled, the maximum uplink transmit power of the UE is 23 dBm.
Table 3-20 High Power of NSA Cells related parameter
NO Parameter Name Parameter
1 High Power Switch of NSA cells PowerControlULFDDLTE.nsaHighPowerSwch

PowerControlULTDDLTE.nsaHighPowerSwch
3.2.2 Uplink Power Control between EUTRAN and NR
■ Static power sharing
After an UE accesses the network and an SN is added, if the eNodeB does not enable Switch for UL Power Adaptive Allocation for NSA UEs, the
UE is configured with the maximum transmission power, where LTE side uses Maximum Tx Power Allocated to the LTE UEs Not Supporting
Power Sharing and NR side uses the remaining available power. Uplink power control is implemented independently on both sides in
accordance with respective power control.
■ Semi-Static Power Sharing
When an UE accesses the network and an SN is added, if Switch for UL Power Adaptive Allocation for NSA Ues is turned on , on LTE side, the
UE is configured with Maximum Tx Power Allocated to the LTE UEs Not Supporting Power Sharing used as its initial power upper limit. On NR
side, the UE is configured with UE maximum transmission power minus Maximum Tx Power Allocated to the LTE UEs Not Supporting Power
Sharing. In the subsequent service phase, the LTE eNodeB calculates the remaining power based on the power usage at the LTE side, and UE
uses the remaining power as maximum available power on NR side. UE maximum transmission power on both sides are configured through
RRC reconfiguration procedure, where LTE upper limit should not exceed the upper limit at the NSA terminal uplink LTE transmit power.
Uplink power control is implemented independently on both sides.
Table 3-18 Uplink power allocation related parameter
1 Maximum Tx Power Allocated to the LTE UEs Not PowerControlULFDDLTE.pmaxOfLte PowerControlULTDDLTE.pmaxOfLte

Supporting Power Sharing 4NonSharingPwrUE 4NonSharingPwrUE
2 Switch for UL Power Adaptive Allocation for NSA PowerControlULFDDLTE.adpAllocNs PowerControlULTDDLTE.adpAllocNs

Ues aUlPwrSwch aUlPwrSwch
18 - 89
EN-DC Enhancement
3 Upper Limit of UL LTE Tx Power for NSA UEs PowerControlULFDDLTE.maxAdpUlL PowerControlULTDDLTE.maxAdpUlL

tePwrOfNsa tePwrOfNsa
3.2.3 Dynamic Uplink Power Sharing for EUTRAN and NR
■ Dynamic power sharing (by the UE)
After an UE accesses the network and an SN is added, if the UE supports dynamic power sharing and Power Allocation Type in Dynamic Power
Sharing for NSA UEs is set to “UE distribute LTE/NR power”, the UE decides the power scaling mechanism on the NR side by itself. The
LTE/NR performs independent power control according to their respective maximum transmission power.
■ Dynamic power sharing (assisted by eNodeBs)
After the UE accesses the network and SN is added, if the UE supports dynamic power sharing andPower Allocation Type in Dynamic Power
Sharing for NSA UEs is set to “eNodeB distribute LTE/NR power”, the eNB-assisted dynamic power sharing will be enabled. The LTE informs
NR side about the remaining available uplink power in accordance with its power usage. The NR side controls the number of RBs to be
scheduled so that UE transmission power at NR side will not exceed the remaining power.
Specifically:
1 Power configuration: if Optimization Switch for Assistant NSA eNodeB Schedulers is set to be ‘Open’ , p-maxEUTRA-r15 can be
configured by Maximum Tx Power on the LTE Side in the Case of Assistant-Scheduler Optimization for NSA eNodeBs. Otherwise, p-
maxEUTRA-r15 is fixed to be 23dBm.
2 LTE Power statistics: if Optimization Switch for Assistant NSA eNodeB Schedulers is set to be ‘Open’, the statistics demand for
LTE resource block is not limited by maximum uplink power. Otherwise the statistics demand is limited by maximum uplink power.
3 LTE resource block allocation: if Optimization Switch for Assistant NSA eNodeB Schedulers is set to be ‘Open’, maximum
allocation resource block number is not limited by uplink maximum power. Otherwise maximum allocation resource block number is
limited by uplink maximum power.
Table 3-19 Dynamic Uplink Power Sharing related parameter
1 Power Allocation Type in Dynamic Power Sharing for NSA PowerControlULFDDLTE.opt4 PowerControlULTDDLTE.opt4
UEs DynSharingPwrNsaUE DynSharingPwrNsaUE
2 Optimization Switch for Assistant NSA eNodeB Schedulers PowerControlULFDDLTE.nSAP PowerControlULTDDLTE.nSAP

owAlloOptiSwch owAlloOptiSwch
3 Maximum Tx Power on the LTE Side in the Case of Assistant- PowerControlULFDDLTE.nSAL PowerControlULTDDLTE.nSAL
Scheduler Optimization for NSA eNodeBs TEPmax TEPmax
3.3 Interference Suppressed Under EUTRAN-NR Dual Connectivity (Trial) (FDD)
The self-interference of NSA terminal includes harmonic interference and intermodulation interference. As shown in the figure below,
harmonic interference refers to the scenario that the NR downlink carrier is received when NSA terminal is in the LTE uplink carrier sending
process. The multiple harmonic components generated by the LTE uplink carrier pass internal circuit, shared components and antennas,
unfortunately becomes the useless strong interference signals to NR downlink receiving, thus the NR downlink receiving performance is
affected. Intermodulation interference refers to the scenario that the NR uplink carrier is transmitted and LTE downlink carrier is received
when NSA terminal is in the LTE uplink carrier sending process. The intermodulation components generated by the non-linear circuit will
become the useless strong interference signals to LTE downlink receiving, thus, LTE downlink receiving performance is affected.
Figure 3-4 A sketch of harmonic & intermodulation interference
19 - 89
EN-DC Enhancement
The solution strategy for harmonic interference and intermodulation interference includes the following four steps:
1 The bandwidth of harmonic & intermodulation interference is determined according to the uplink and downlink frequencies and
bandwidth configuration of LTE and NR.
2 The interference types of sub-frames are determined according to the sub-frame ratio of LTE and NR.
3 Identify non-NSA UEs and NSA UEs.
4 TTI-level scheduling interference avoidance.
For the subframes with harmonic interference, static avoidance strategy or semi-static avoidance strategy can be used. The static avoidance
strategy includes LTE uplink avoidance strategy and NR downlink avoidance strategy. The semi-static avoidance strategy distinguishes NSA
near-point UEs and NSA far-point UEs, where NSA near-point UEs adopt LTE uplink avoidance strategy, and NSA far-point UEs adopt NR
downlink avoidance strategy. For the subframes with intermodulation interference, only NR uplink avoidance strategy can be used.
3.3.1 Harmonic Interference Avoidance Strategy
For the subframes with harmonic interference, TTI-level scheduling interference avoidance for NSA UEs can be implemented through static
avoidance strategy or semi-static avoidance strategy, which are controlled by Harmonic-Interference Avoidance Mode and Harmonic-
Interference Coordination Switch as shown in the table below:
Table 3-20 Harmonic interference avoidance strategy switch
Harmonic-Interference Avoidance Mode Harmonic-Interference Coordination Switch
static avoidance strategy(LTE The value of the switch is 1, indicating that the The value of the switch is 1, indicating that the LTE
uplink avoidance strategy) static avoidance strategy is used uplink avoidance strategy is used
static avoidance strategy(NR The value of the switch is 1, indicating that the The value of the switch is 0, indicating that the NR
downlink avoidance strategy) static avoidance strategy is used downlink avoidance strategy is used
semi-static avoidance strategy The value of the switch is 2, indicating that the semi-static avoidance strategy has nothing to do
semi-static avoidance strategy is used with this item
The following configuration needs to be adjusted under static avoidance strategy (LTE uplink avoidance strategy) and semi-static avoidance
strategy:
As shown in the figure below, enable the PUCCH Blanking, the PUCCH position is moved inwards according to the Numbers of Blanked RB of
PUCCH, here the movement offset determines how many RBs are available for NSA UEs. And set the CDMA LTE CSS Switch to “Only UL
Support CDMA LTE CSS”. For LTE UE, the intermediate PUSCH is preferred. PUCCH Blanking is used only after the intermediate PUSCH is
used. The parameter UL Buffer Mode of CSS is configured as high-frequency multiplexing. For NSA UE, only low-frequency PUCCH Blanking RB
is used. The impacts are as follows:
■ Since the system bandwidth is divided into three segments, the maximum number of RBs allocated to LTE UE is reduced;
■ Note that the location of LTE PUCCH changes. If the PUCCH location of neighbor cell is different, the PUSCH of neighbor cell will cause
interference to the PUCCH of this cell, and the PUCCH Blanking of this cell will cause interference to the PUCCH of neighbor cell.
Figure 3-5 LTE uplink avoidance strategy
20 - 89
EN-DC Enhancement
■ Static avoidance strategy(LTE uplink avoidance strategy): eNodeB avoids scheduling the resource in LTE uplink frequency location for
it generates interference.
■ Static avoidance strategy(NR downlink avoidance strategy): eNodeB avoids scheduling the resource in NR downlink frequency location
for it has strong interference.

■ Semi-static avoidance strategy: distinguish NSA near-point UEs from NSA far-point UEs. NSA near-point UEs adopt LTE uplink
avoidance strategy, and NSA far-point UEs adopt NR downlink avoidance strategy. At NR side, NSA users are identified with near-point
type or far-point type. Once the type changes, NR will notify LTE of this change. The detection threshold of near-/far-point type is decided
upon semi-static coordination. First, LTE periodically counts the uplink resource utilization rate of NSA near-point UEs. Then LTE notifies
the cell load identification to NR. Finally, the NR decides whether to adjust the threshold according to the cell load identification.
Note:
1 Semi-static avoidance strategy does not support MN handover with SN.
2 CA does not support this function.
Table 3-21 Parameters in harmonic interference avoidance
No. Parameter Name FDD Parameter
1 Harmonic-Interference Avoidance Mode PhyChannelFDDLTE.harmInterferAvoidMode
2 Harmonic-Interference Coordination Switch PhyChannelFDDLTE.harmonicSwitch
3 PUCCH Blanking PhyChannelFDDLTE.pucchBlankFlag
4 Numbers of Blanked RB of PUCCH PhyChannelFDDLTE.pucchBlankNum
5 CDMA LTE CSS Switch PhyChannelFDDLTE.cDMALTECSSSwch
6 UL Buffer Mode of CSS PhyChannelFDDLTE.bufferCSSModeUl
3.3.2 Intermodulation Interference Avoidance Strategy
For the subframes with intermodulation interference, TTI-level scheduling interference avoidance for NSA UEs can be implemented through
NR uplink avoidance strategy, eNodeB avoids scheduling the resource in NR uplink frequency location for it generates interference.
For the FDD macrocell (excluding BPL1), when The Switch of SRS Configuration is open, if the Inter-modulation Interference Switch is open
and the Percentage of Reserved SRS Time Domain Resources is not zero, UE is not allocated SRS resources; otherwise, UE is allocated SRS
resources.
Table 3-22 Parameters in intermodulation interference avoidance
No. Parameter Name FDD Parameter
1 The Switch of SRS Configuration PhyChannelFDDLTE.srsEnable
2 Inter-modulation Interference Switch PhyChannelFDDLTE.iMDSwitch
3 Percentage of Reserved SRS Time Domain Resources PhyChannelFDDLTE.srsReserveRatio
4 Engineering Guide
4.1 Part of Services
4.1.1 Requirements
4.1.1.1 Hardware Requirements
21 - 89
EN-DC Enhancement
E-UTRAN:
BBU Type: V9200
Board Type: VBPc,VBPd
Main control board: VSWc,VSWd
NR:
BBU Type: V9200
Board Type: VSWc, VSWd, VBPc, VBPd
4.1.1.2 EPC Requirements
EPC supports EN-DC, and support Secondary RAT Data Volume Report.
4.1.1.3 Frequency Band, Frequency and Bandwidth Requirements
No special requirements
4.1.1.4 UE Requirement
Terminals support R15, and has capability of E-UTRAN, NR and EN-DC.
4.1.1.5 Transmission Requirements
4.1.1.6 Restrictions
The RLC mode and PDCP SN length of the per QCI on the LTE and NR sides must be configured same value.
The x2PlmnMode parameter configured in the NR UME needs to be used together with the PLMN encoding method parameter configured in
the LTE UME.
4.1.1.7 License Requirement
Table 4-1 FDD License requirement
NO FL FL Name License File No. License Control name Control le

vel
1 ZLF40- DL Data Split flow control based on LTE LTE- LTE FDD DL Data Split flow control based eNB level
06-013 high-load cell FDD_ENB_F267 on high-load cell
2 ZLF40- DL Data Split flow control based on LTE LTE- LTE FDD DL Data Split flow control of eNB level
13-016 high-load cell for NSA Sharing FDD_ENB_F274 RAN Sharing
3 ZLF40- Multi Factor Joint awared SN Handling SDR_F161_L LTE FDD Multi Factor Joint awared SN Network
04-010 Enhancement for NSA Handling enhancement for NSA level
Table 4-2 TDD License requirement
NO FL FL Name License File No. License Control name Control le

vel
1 ZLT45- DL Data Split flow control based on LTE LTE- TD LTE DL Data Split flow control based eNB level
06-013 high-load cell TDD_ENB_F267 on high-load cell
2 ZLT40- DL Data Split flow control based on LTE LTE- LTE TDD DL Data Split flow control of eNB level
13-016 high-load cell for NSA Sharing TDD_ENB_F274 RAN Sharing
3 ZLT45- Multi Factor Joint awared SN Handling SDR_F161_TDL LTE TDD Multi Factor Joint awared SN Network
04-010 Enhancement for NSA Handling enhancement for NSA level
22 - 89
EN-DC Enhancement
4.1.2 DC and CA Combination
For carrier aggregation, refer to LTE Carrier Aggregation Feature Guide.
4.1.2.1 LTE Parameters
4.1.2.1.1 LTE Related Parameters
Table 4-3 LTE parameters of CA MR Delay Start policy
NO Parameter Parameter name Parameter explanation Range Default

value value
1 ControlPlaneTi Delay Start Timer This parameter sets the delay start timer for CA anchoring [0..1800000] 4000
merLTE.cA4EN for CA Anchoring relative to EN-DC anchoring. For NSA UEs, the eNodeB
DCAnchorDela Relative to EN-DC preferentially triggers EN-DC anchoring and CA anchoring is
yTimer Anchoring started after the period of time specified by this parameter.
2 ControlPlaneTi Delay Start Timer This parameter sets the delay start timer for CA anchoring [0..1800000] 4000
merLTE.cA4SN for CA Anchoring relative to SN addition. For NSA UEs, the eNodeB preferentially
AddDelayTime Relative to SN triggers SN addition and CA anchoring is started after the period
r Addition of time specified by this parameter.
4.1.2.1.2 LTE parameters configuration
In the NSA scenario, the UE can obtain the traffic gain of the EN-DC first, and secondly, obtain the traffic gain through the CA to improve the
user experience.
To configure the parameters of CA MR Delay Start policy.
Select[Managed Element ->eNodeB CU -> LTE -> RRC timer -> Control Plane Timer ], double click to get the modify table, then we can find
Delay Start Timer for CA Anchoring Relative to EN-DC Anchoring and Delay Start Timer for CA Anchoring Relative to SN Addition parameter.
Change it and click to save configuration then click to synchronize the data to eNodeBs.
Figure 4-1 CA MR Delay Start policy
4.1.3 SN Change Penalty Suppression
4.1.3.1 NR Related Parameters
Table 4-4 Penalty suppression parameter on the NR side
NO Paramete Parameter name Parameter explanation Range Default value

r value
23 - 89
EN-DC Enhancement
1 GlobalSw snChangePunishSwitch During the SnChange procedure, when the source SN receives [0..3] 0
itchInfor an Sgnb Change Refuse message from the MN, if the message
mation.s carries the cause of 'Transport Resource Unavailable' and if
nChange bit0 of the parameter value is 1, the punishment and
PunishS suppression function is started on the SN side.If the message
witch carries the cause of 'No Radio Resources Available' and if bit1
of the parameter value is 1, the punishment and suppression
function is started on the SN side.
2 ControlPl Timer for SnChange During the SnChange procedure, if the [10..65535] 60
aneTimer becoming unavailable snChangePunishSwitch parameter is set to Open, the source
.snChang on the target SN side SN receives an Sgnb Change Refuse message from the MN
eTargetN and the rejection message carries the cause of Transport
otAllowe Resource Unavailable, the SN starts this timer (the timer is not
dTimer restarted when the same message is received again). Before
the timer expires, the SnChange penalty strategy takes effect
and the corresponding MN and SN pairs cannot be selected
for change. After the timer expires, if the SnChange penalty
strategy of the UE fails, the SnChange penalty list of the UE is
cleared.
3 GlobalSw Switch of SNChange During the snchange process, the source SN receives the Sgnb [0, 1] 0;0;0;0;0;0;0;0
itchInfor cell-level punishment Change Refuse message from the MN. If the rejection message
mation.s carries a navigation reason and the first element of this
nChange parameter is 1, the cell-level penalty suppression function is
CellPunis enabled on the SN side.
hSwitch
4 ControlPl SNChange cell-level During the snchange process, the source SN receives the Sgnb [1..65535] 60
aneTimer punishment timer Change Refuse message from the MN side. If the failure cause
.snChang in this rejection message is navigation reason and the
eCellPuni function switch is turned on, the corresponding cell cannot be
shTimer selected for change before the timer expires.
4.1.3.2 NR Parameters Configuration
1 snChangePunishSwitch:
select [ManagedElement-> gNB CU-CP function configuration -> Global Switch -> snChangePunishSwitch]. Click for data
synchronization to the gNB.
Figure 4-2 snChangePunishSwitch
24 - 89
EN-DC Enhancement
1 Timer for SnChange becoming unavailable on the target SN side :
select [ManagedElement-> gNB CU-CP function configuration -> ControlPlaneTimer -> Timer for SnChange becoming unavailable on the
target SN side ]. Click for data synchronization to the gNB.

Figure 4-3 Timer for SnChange becoming unavailable on the target SN side
1 Switch of SNChange cell-level punishment:
select [ManagedElement-> GNBCUCPFunction-> Global Switch -> Switch of SNChange cell-level punishment]. Click for data
Figure 4-4 Switch of SNChange cell-level punishment
25 - 89
EN-DC Enhancement
1 SNChange cell-level punishment timer:
select [ManagedElement-> GNBCUCPFunction->ControlPlaneTimer -> SNChange cell-level punishment timer]. Click for data
Figure 4-5 SNChange cell-level punishment timer
26 - 89
EN-DC Enhancement
4.1.4 PSCell Change Preventing Ping-Pong Handover
4.1.4.1 NR Related Parameters
Table 4-5 Parameters of prevent ping-pong on NR Side
NO Parameter Parameter Parameter explanation Range Default

name value value
1 EnDCCtrl.p Switch of the This parameter sets whether to enable the ping-pong prevention policy {0: Close, Close
scellChang ping-pong for PSCell change. When the function is enabled, after a UE performs 1: Open}
ePrePingP prevention PSCell change, the policy for preventing the ping-pong effect becomes
ongSwch policy for valid to prevent the UE from performing PSCell change to return to the
PSCell change source NR cell.
2 EnDCCtrl.p Timer for ping- This parameter sets the timer for preventing the ping-pong effect when [1..65535] 3
scellChang pong the PSCell changes. This timer is started after a UE performs PSCell
ePrePingP prevention in change, and the ping-pong prevention policy takes effect before the timer
ongTimer PSCell change expires.
4.1.4.2 NR Parameters Configuration
1 Prevent ping-pong parameters:
Select [ManagedElement-> gNB CU-CP function configuration -> CU cell configuration->Enhanced dual connection], set the following
parameters:
27 - 89
EN-DC Enhancement
■ Switch of the ping-pong prevention policy for PSCell change
■ Timer for ping-pong prevention in PSCell change.
Click for data synchronization to the gNB.

Figure 4-6 NR prevent ping-pong switch Parameters
4.1.5 Flexible SN Configuration Strategy based on the Traffic
Table 4-6 Parameters of Load based SN Addtion/Release on LTE Side
NO Parameter Parameter Parameter explanation Range value Default value

name
1 FDD: EN-DC SN This parameter sets the configuration mode of EN-DC SNs. If 0:Unconditional, 0
ENDCPoli Configuration it is set to Unconditional, the eNodeB configures SNs for all 1:CongestionBased,
cyFDDLTE Mode the NSA UEs. If it is set to CongestionBased or 2:TrafficSpeedBased
.enDcSnC TrafficSpeedBased, the eNodeB configures SNs only for the
onfigMod NSA UEs that need to be configured with SNs.
TDD:
ENDCPoli
cyTDDLTE
.enDcSnC
onfigMod
2 FDD: EN-DC This parameter sets identification indexes for EN-DC. An [0..10] 0
ENDCPoli Identification parameter value corresponds to an NR PDCP identification
cyFDDLTE Index index. If the services of a UE satisfy the requirements
.enDcIden corresponding to an index, the UE can be identified to
tifyIndex support a certain function. For example, an SN can be added
TDD: for the UE.
ENDCPoli
cyTDDLTE
.enDcIden
tifyIndex
28 - 89
EN-DC Enhancement
3 FDD: Rate-Based If this parameter is set to Close and the EN-DC SN 0:Close, 0
ENDCPoli Threshold configuration mode is set to 2 (TrafficSpeedBased), the 1:Open
cyFDDLTE Switch measurement event B1 can be unconditionally delivered in
.baseRate the initial access, incoming handover, re-establishment,
Threshold initial SCG setup, and SCG split scenarios. If this parameter is
Swch set to Open and the EN-DC SN configuration mode is set to 2
TDD: (TrafficSpeedBased), SNs can be added based on rates in any
ENDCPoli scenario.
cyTDDLTE
.baseRate
Threshold
Swch
4 FDD: PSCell This parameter controls the PSCell addition strategy. If it is 0:Based Based
ENDCPoli Addition set to "measurement-based" strategy, PSCell is added in a Measurement, Measurement
cyFDDLTE Strategy measurement-based manner; If it is set to "blind and 1:Based Blind and
.pSCellAd Indicator measurement-based" strategy, PSCell is added in a blind and Measurement
dStgyInd measurement-based manner;
TDD:
ENDCPoli
cyTDDLTE
.pSCellAd
dStgyInd
5 PdcpStatu PDCP Delay This parameter sets the PDCP delay threshold for [0..65535] 10
sLTE.cong Threshold for determining whether congestion occurs. When the PDCP
estDelayT Congestion delay exceeds the threshold, it is considered that congestion
hr Occurrence occurs.
(ms)
PdcpStatu PDCP Delay This parameter sets the PDCP delay threshold for triggering [0..65535] 5
sLTE.unco Threshold for decongestion. If the PDCP delay is shorter than the
ngestDela Triggering threshold, it is considered that no congestion occurs.
yThr Decongestion
(ms)
6 PdcpStatu PDCP Cache This parameter sets the PDCP cache occupancy ratio [0..100] 80
sLTE.cong Occupancy threshold for determining whether congestion occurs. If the
estCacheT Ratio PDCP cache occupancy ratio exceeds the threshold, it is
hr Threshold for considered that congestion occurs.
Congestion
Occurrence
7 PdcpStatu PDCP Cache This parameter sets the PDCP cache occupancy ratio [0..100] 60
sLTE.unco Occupancy threshold for triggering decongestion. If the PDCP cache
ngestCach Ratio occupancy ratio is lower than the threshold, it is considered
eThr Threshold for that no congestion occurs.
Triggering
Decongestion
8 PdcpStatu Number of This parameter sets the number of times that the system [1..65535] 10
sLTE.pktC Consecutive consecutively determines whether the PDCP waiting time of
ongestDec Packet-Based a packet exceeds the PDCP delay threshold for congestion
isionTime Congestion occurrence or PDCP delay threshold for triggering
s Decisions decongestion. When the eNodeB determines whether
congestion occurs based on the PDCP delay, the eNodeB
uses this parameter value, the PDCP delay threshold for
congestion occurrence, and the PDCP delay threshold for
triggering decongestion to determine whether congestion or
decongestion occurs.
29 - 89
EN-DC Enhancement
9 PdcpStatu Number of This parameter sets the number of times that the system [1..65535] 10
sLTE.cach Congestion consecutively determines whether the PDCP cache
eRatioCon Decisions occupancy ratio exceeds the PDCP cache occupancy ratio
gesTimes Based on the threshold for determining whether congestion occurs or the
Cache PDCP cache occupancy ratio threshold for triggering
Occupancy decongestion. When the eNodeB determines whether
Ratio congestion occurs based on the PDCP cache occupancy
ratio, the eNodeB uses this parameter value, the PDCP cache
occupancy ratio threshold for congestion occurrence, and
the PDCP cache occupancy ratio threshold for triggering
decongestion to determine whether congestion or
decongestion occurs.
10 PdcpStatu PDCP Status This parameter sets the index for identifying the PDCP status. [0..10] N/A
sLTE.pdcp Identification It corresponds to service load determination parameters. If
StatusIde Index the services of a UE satisfy the requirements corresponding
ntifyIndex to the index, the UE can be identified to support a certain
function. For example, an SN can be added for the UE.
11 PdcpStatu Number of This parameter sets the number of times that the speed of a [1..255] 2
sLTE.high High-Speed UE configured with speed-based SN addition is
TrafficSpe Decisions consecutively detected to be high. The detection is
edDesTim performed once in every determination period. When speed-
e based SN addition is enabled, the eNodeB uses this
parameter to detect whether the speed of a UE is high in the
uplink and downlink. If the number of times that the speed of
a UE configured with speed-based SN addition is
consecutively detected to be high reaches the parameter
value, the eNodeB sends a high-load indication to the
control plane, delivers a B1 measurement result, and triggers
the SN addition procedure.
12 PdcpStatu High This parameter sets the upper threshold of the downlink [0..4294967295] 200000
sLTE.dlTra Threshold of traffic speed of UEs to add SNs based on the speed. If the
fficSpeed the DL Traffic speed-based SN addition is enabled and the downlink speed
HighThrd Speed of a UE is higher than the parameter value, the eNodeB
considers the UE as a downlink high-speed UE.
13 PdcpStatu Upper This parameter sets the upper threshold of the uplink traffic [0..4294967295] 100000
sLTE.ulTra Threshold of speed of UEs to add SNs based on the speed. If speed-based
fficSpeed the UL Traffic SN addition is enabled and the uplink speed of a UE is higher
HighThrd Speed than the parameter value, the eNodeB considers the UE as
an uplink high-speed UE.
14 PdcpStatu Number of This parameter sets the number of times that the speed of a [1..255] 2
sLTE.lowT Low-Speed UE configured with speed-based SN addition is
rafficSpee Decisions consecutively detected to be low. The detection is
dDesTime performed once in every determination period. If speed-
based SN addition is enabled, the eNodeB uses this
parameter to detect whether the speed of a UE is low in the
uplink and downlink. After a UE is consecutively determined
as a low-speed UE, its low-speed status is reported to the
upper layer, and the SN addition procedure is not triggered
later.
15 PdcpStatu Lower This parameter sets the upper threshold of the uplink traffic [0..4294967295] 100000
sLTE.dlTra Threshold of speed of UEs to add SNs based on the speed. If speed-based
fficSpeedL the DL Traffic SN addition is enabled and the downlink speed of a UE is
owThrd Speed lower than the parameter value, the eNodeB considers the
UE to be a downlink low-speed UE.
16 PdcpStatu Lower This parameter sets the lower threshold of the uplink traffic [0..4294967295] 50000
sLTE.ulTra Threshold of speed of UEs to add SNs based on the speed. If speed-based
fficSpeedL the UL Traffic SN addition is enabled and the uplink speed of a UE is lower
owThrd Speed than the parameter value, the eNodeB considers the UE as
an uplink low-speed UE.
4.1.5.1.2 LTE Parameters Configuration
30 - 89
EN-DC Enhancement
1 Rate Based parameters
FDD: Select[Managed Element ->eNodeB CU -> LTE -> E-UTRAN FDD Cell -> LTE FDD EN-DC policy],
TDD: Select[Managed Element ->eNodeB CU -> LTE -> E-UTRAN TDD Cell -> LTE TDD EN-DC policy],
double click to get the modify table, then we can find EN-DC SN Configuration Mode/EN-DC Identification Index/Rate-Based Threshold Switch
parameter. Change it and click OK to save configuration. and then click to synchronize the data to eNodeBs.
Figure 4-7 EN-DC SN config Mode and EN-DC Identification Index
Figure 4-8 Rate-Based Threshold Switch
1 PDCP Status parameters:
Select[Managed Element->eNodeB CU ->LTE ‒>QoS->Global QoS Parameter -> Pdcp Load Status], double click the table to set the followring
parameters
■ PDCP Delay Threshold for Triggering Decongestion (ms)
■ PDCP Cache Occupancy Ratio Threshold for Congestion Occurrence
■ Number of Consecutive Packet-Based Congestion Decisions
■ PDCP Delay Threshold for Congestion Occurrence (ms)
■ PDCP Cache Occupancy Ratio Threshold for Triggering Decongestion
■ Number of Congestion Decisions Based on the Cache Occupancy Ratio
■ Number of High-Speed Decisions
■ High Threshold of the DL Traffic Speed
■ Upper Threshold of the UL Traffic Speed
■ Number of Low-Speed Decisions
■ Lower Threshold of the DL Traffic Speed
■ Lower Threshold of the UL Traffic Speed
Change them and click save configuration then click Synchronize the data to eNodeBs.
Figure 4-9 LTE PDCP Status Parameters
31 - 89
EN-DC Enhancement
4.1.5.2 NR Parameters
4.1.5.2.1 NR Related Parameters
Table 4-7 Parameters of Load based SN Addtion/Release on NR Side
NO Parameter Parameter Parameter explanation Range value Default

name value
1 PDCPStat PDCP delay This parameter sets the PDCP layer delay threshold at which bearer [1..65535] step 10
usCfg.con threshold in congestion occurs on a UE. When the number of times that the PDCP 1
gestDelay the case of delay of the bearer of a UE exceeds this threshold reaches the value of
Thr bearer the pktCongestDecisionTimes parameter (number of packet
congestion congestion decisions), it is considered that the bearer of the UE is
congested and the gNodeB adds an SN for the UE.
2 PDCPStat PDCP delay This parameter sets the PDCP layer delay threshold at which bearer [1..65535] step 5
usCfg.unc threshold in congestion is relieved. When the number of times that the PDCP layer 1
ongestDel the case of delay of the bearer of a UE is smaller than this threshold reaches the
ayThr bearer value of the pktCongestDecisionTimes parameter (number of packet
decongestion congestion decisions), it is considered that the bearer of the UE is not
congested and the gNodeB does not add any SN for the UE.
3 PDCPStat PDCP layer This parameter sets the PDCP layer cache occupation ratio threshold [0..100] step 1 80
usCfg.con cache at which bearer congestion occurs on a UE. When the number of times
gestCache occupation that the PDCP layer cache occupation ratio of the bearer of a UE
Thr ratio exceeds this threshold reaches the value of the
threshold in cacheRatioCongestDecisionTimes parameter (number of cache
the case of occupation ratio congestion decisions), it is considered that the
bearer bearer of the UE is congested and the gNodeB adds an SN for the UE.
congestion
32 - 89
EN-DC Enhancement
4 PDCPStat PDCP layer This parameter sets the PDCP layer cache occupation ratio threshold [0..100] step 1 60
usCfg.unc cache at which bearer congestion is relieved. When the number of times that
ongestCac occupation the PDCP layer cache occupation ratio of the bearer of a UE is lower
heThr ratio than this threshold reaches the value of the
threshold in cacheRatioCongestDecisionTimes parameter (number of cache
the case of occupation ratio congestion decisions), it is considered that the
bearer bearer of the UE is not congested and the gNodeB does not add any
decongestion SN for the UE.
5 PDCPStat Threshold This parameter sets the threshold number of consecutive congestion [1..65535] step 10
usCfg.pkt number of decisions based on the PDCP packet waiting time. When the gNodeB 1
CongestD congestion determines whether congestion occurs on the bearer of a UE based on
ecisionTi decisions the PDCP packet waiting time, it is considered that congestion occurs
mes based on the on the UE if the number of times that PDCP congestion occurs exceeds
PDCP packet this threshold. If the number of times that no congestion occurs on the
waiting time PDCP layer exceeds this threshold, it is considered that the bearer
congestion of the UE is relieved. If congestion occurs, the gNodeB
adds an SN for the UE.
6 PDCPStat Threshold This parameter sets the threshold number of consecutive congestion [1..65535] step 10
usCfg.cac number of decisions based on the PDCP cache occupation ratio. When the 1
heRatioCo congestion gNodeB determines whether congestion occurs on the bearer of a UE
ngestDeci decisions based on the PDCP cache occupation ratio, it is considered that
sionTimes based on the congestion occurs on the UE if the number of times that PDCP
PDCP cache congestion occurs exceeds this threshold. If the number of times that
occupation no congestion occurs on the PDCP layer exceeds this threshold, it is
ratio considered that the bearer congestion of the UE is relieved. If
congestion occurs, the gNodeB adds an SN for the UE.
7 PDCPStat PDCP status This parameter sets the index of the PDCP status. It can be used in [0..10] step 1 0
us.pdcpIn index combination with the QoS class ID (QCI) to uniquely index a PDCP
dex status configuration.
8 PDCPStat Number of This parameter sets the number of times for consecutively detecting [1..255] step 1 2
usCfg.high high-speed whether a UE is in high-speed status according to the speed-based SN
TrafficSpe decisions configuration. The detection is performed once in every judgment
edDecisio period. The gNodeB uses this parameter to detect the high speed of a
nTimes UE in the uplink and downlink.
9 PDCPStat Upper This parameter sets the upper threshold of the downlink traffic speed [0..4294967295] 200000
usCfg.dlTr threshold of of UEs to add SNs based on the speed. If the downlink speed of a UE is step 1
afficSpeed downlink higher than the parameter value, the gNodeB considers the UE to be a
HighThrd speed(Bps) downlink high-speed UE.
10 PDCPStat Upper This parameter sets the upper threshold of the uplink traffic speed of [0..4294967295] 100000
usCfg.ulTr threshold of UEs to add SNs based on the speed. If the uplink speed of a UE is step 1
afficSpeed uplink higher than the parameter value, the gNodeB considers the UE to be
HighThrd speed(Bps) an uplink high-speed UE.
11 PDCPStat Number of This parameter sets the number of times for consecutively detecting [1..255] step 1 2
usCfg.low low-speed whether a UE is in low-speed status according to the speed-based SN
TrafficSpe decisions configuration. The detection is performed once in every judgment
edDecisio period. The gNodeB uses this parameter to detect the low speed of a
nTimes UE in the uplink and downlink.
12 PDCPStat Lower This parameter sets the lower threshold of the downlink speed for UEs [0..4294967295] 100000
usCfg.dlTr threshold of with the speed-based SN configuration function. If the downlink step 1
afficSpeed downlink speed of a UE is lower than the parameter value, the gNodeB
LowThrd speed(Bps) considers the UE to be a downlink low-speed UE.
13 PDCPStat Lower This parameter sets the lower threshold of the uplink speed for UEs [0..4294967295] 50000
usCfg.ulTr threshold of with the speed-based SN configuration function. If the uplink speed of step 1
afficSpeed uplink a UE is lower than the parameter value, the gNodeB considers the UE
LowThrd speed(Bps) to be an uplink low-speed UE.
14 EnDCCtrl.r Rate-based In NSA scenarios, this parameter sets whether to enable the function [false, true] false
atebasedS SN deletion of deleting the SN for a UE configured with an SN based on the UE
nDelSwitc switch rate. If this parameter is set to True, when the uplink rate and
h downlink rate of the UE are lower than the set threshold, the SgNB
actively triggers SN deletion.
33 - 89
EN-DC Enhancement
4.1.5.2.2 NR Parameters Configuration
1 PDCP Status parameters:
Select [Managed Element-> RCS-> PCE ->PDCPStatus], set PDCP status index. Click for data synchronization to the gNB.
Figure 4-10 NR PdcpStatus Parameters
1 PDCP StatusCfg parameters
Select [Managed Element-> RCS-> PCE ->PDCPStatus ->PDCPStatusCfg], set the followring parameters. Click for data synchronization
to the gNB.
■ PDCP delay threshold in the case of bearer congestion
■ PDCP delay threshold in the case of bearer decongestion
■ PDCP layer cache occupation ratio threshold in the case of bearer congestion
■ PDCP layer cache occupation ratio threshold in the case of bearer decongestion
■ Threshold number of congestion decisions based on the PDCP packet waiting time
■ Threshold number of congestion decisions based on the PDCP cache occupation ratio
■ Number of high-speed decisions
■ Upper threshold of downlink speed(Bps)
■ Upper threshold of uplink speed(Bps)
■ Number of low-speed decisions
■ Lower threshold of downlink speed(Bps)
■ Lower threshold of uplink speed(Bps)
Figure 4-11 NR Pdcp StatusCfg Parameters-1
34 - 89
EN-DC Enhancement
Figure 4-12 NR Pdcp StatusCfg Parameters-2
35 - 89
EN-DC Enhancement
1 Rate-based SN deletion switch parameters:
Select [ManagedElement-> gNB CU-CP function configuration -> CU cell configuration->Enhanced dual connection], set Rate-based SN
deletion switch. Click for data synchronization to the gNB.
Figure 4-13 NR Rate-based SN deletion switch Parameters
4.1.6 SN Addition Punishment
4.1.6.1 Related Parameters
Table 4-8 SN Addition Punishment Related Parameter
NO Paramete Paramete Parameter explanation Range val Default v

r r name ue alue
1 [FDD] SCG Failu This parameter enables or disables SCG failure punishment. If it is set to Open, n 0:Close, 0
ENDCPoli re Punish o SN can be added for a UE if the number of SCG failures of the UE reaches this th 1:Open
cyFDDLT ment Swi reshold within a certain period of time.
E.sCGFail tch
urePunis
hSwch
[TDD]
ENDCPoli
cyTDDLT
E.sCGFail
urePunis
hSwch
2 [FDD] SCG Failu This parameter sets the duration for SCG failure detection. If the number of SCG f [1..36000] 2
ENDCPoli re Detecti ailures of a UE reaches the specified threshold within the period specified by this
cyFDDLT on Durati parameter, no SN can be added for the UE.
E.sCGFail on(s)
ureDetec
tDuration
[TDD]
ENDCPoli
cyTDDLT
E.sCGFail
ureDetec
tDuration
36 - 89
EN-DC Enhancement
3 [FDD] Threshol This parameter sets the threshold number of SCG failure detections. If the numbe [1..20] 2
ENDCPoli d Numbe r of SCG failures of the UE reaches this threshold within the period specified by th
cyFDDLT r of SCG F e detection timer, no SN can be added for a UE.
E.sCGFail ailure Det
ureDetec ections
tTimes
[TDD]
ENDCPoli
cyTDDLT
E.sCGFail
ureDetec
tTimes
4 [FDD] SCG Failu This parameter sets the punishment duration for SCG failures. If the number of S 1..36000:, 65535
ENDCPoli re Punish CG failures of a UE reaches this threshold within the period specified by the detec 65535:
cyFDDLT ment Dur tion timer, the timer starts and no SN can be added for the UE before the timer ti
E.sCGFail ation(s) mes out. If this parameter is set to 65535, it indicates that no SN can be added for
urePunis the UE even when the punishment conditions of SCG failures are satisfied.
hDuratio
n
[TDD]
ENDCPoli
cyTDDLT
E.sCGFail
urePunis
hDuratio
n
5 GlobalPu Punishm This parameter enables or disables the punishment for SN configuration failures. 0:Close, 0
nishLTE.s ent Switc For the cells where an SN configuration failure is detected, if this parameter is set 1:Open
NConfigF h for SN to Open, a punishment strategy is triggered based on the failure cause value.
ailPunish Configura
Swch tion Failu
res
6 GlobalPu Punishm This parameter defines a one-dimensional array with the size of 32 to indicate the 0:No puni 1;0;0;1;0;
nishLTE.s ent Strat punishment strategies for special cause values of SN configuration failures. The f shment, 1;1;1;0;0;
pecCause egy for S irst array element represents the cause value "No Radio Resources Available," th 1:Time P 0;0;0;0;0;
SNPunish pecial Ca e second represents "Not supported QCI value," the third represents "unspecified unishme 0;0;0;0;0;
Stgy use Value ," the fourth represents "No Radio Resources Available in Target Cell," the fifth re nt Strate 0;0;0;0;0;
s of SN C presents "Cell not available," the sixth represents "Transport resource unavailabl gy 0;0;0;0;0;
onfigurati e," the seventh represents "Not enough User Plane Processing Resources," and t 0;0
on Failur he eighth represents "Control Processing Overload." The ninth to thirty-second ar
es ray elements are reserved. There are three punishment strategies available for th
e failure cause value corresponding to one array element.
7 GlobalPu Punishm This parameter sets the punishment strategy for the ordinary cause values of SN 0:No puni 0
nishLTE. ent Strat configuration failures. Two punishment strategies are available. shment,
normCau egy for Or 1:Time P
seSNPuni dinary Ca unishme
shStgy use Value nt Strate
of SN Co gy
nfiguratio
n Failures
8 GlobalPu Level-1 P This parameter sets the level-1 punishment timer for SN configuration failures. T [0, 42949 60
nishLTE.l unishme he timer is enabled when the SN configuration failure punishment switch is set t 67295]
evel1SNP nt Timer f o Open. unit s
unishTim or SN Co
er nfiguratio
n Failures
(s)
9 GlobalPu Level-2 D This parameter sets the level-2 detection timer for SN configuration failures. The [0, 65535] 30
nishLTE.l etection timer is enabled when the SN configuration failure punishment switch is set to O unit s
evel2SND Timer for pen.
etectTim SN Config
er uration F
ailures(s)
37 - 89
EN-DC Enhancement
unishTim or SN Co
er nfiguratio
n Failures
(s)
11 GlobalPu Level-3 D This parameter sets the level-3 detection timer for SN configuration failures. The [0, 65535] 30
nishLTE.l etection timer is enabled when the SN configuration failure punishment switch is set to O unit s
evel3SND Timer for pen.
etectTim SN Config
er uration F
ailures(s)
unishTim or SN Co
er nfiguratio
n Failures
(s)
4.1.6.2 Parameter Configuration
1 SCG Failure related paramters
FDD: Select[Managed Element -> eNodeB CU -> LTE -> E-UTRAN FDD Cell -> EN-DC policy],
TDD: Select[Managed Element -> eNodeB CU -> LTE -> E-UTRAN TDD Cell -> EN-DC policy],
set the following parameters:
■ SCG Failure Punishment Switch,
■ SCG Failure Detection Duration,
■ Threshold Number of SCG Failure Detections
■ SCG Failure Punishment Duration
Figure 4-14 SN Addition Punishment triggered by SCG Failure Related Parameters
1 Configure Punishment Switch for SN Configuration Failures.
FDD:Select[Managed Element -> eNodeB CU -> LTE -> Handover Policy -> punishment Global parameters],
TDD: Select[Managed Element -> eNodeB CU -> LTE -> Handover Policy -> punishment Global parameters],
set Punishment Switch for SN Configuration Failures, save configuration, Synchronize the data to eNodeBs.
Figure 4-15 Punishment Switch for SN Configuration Failures
38 - 89
EN-DC Enhancement
1 Configure Punishment Strategy for Special Cause Values of SN Configuration Failures.
set Punishment Strategy for Special Cause Values of SN Configuration Failures save configuration, Synchronize the data to eNodeBs.
Figure 4-16 Punishment Strategy for Special Cause Values of SN Configuration Failures
1 Configure Punishment Strategy for Ordinary Cause Value of SN Configuration Failures.
set Punishment Strategy for Ordinary Cause Value of SN Configuration Failures, save configuration, Synchronize the data to eNodeBs.
Figure 4-17 Punishment Strategy for Ordinary Cause Value of SN Configuration Failures
1 Configure Level 1-3 Detection and Punishment Timer for SN Configuration Failures
39 - 89
EN-DC Enhancement
Set the following parameters:
■ Level-1 Punishment Timer for SN Configuration Failures,
■ Level-2 Detection Timer for SN Configuration Failures
■ Level-2 Punishment Timer for SN Configuration Failures
■ Level-3 Detection Timer for SN Configuration Failures
■ Level-3 Punishment Timer for SN Configuration Failures
save configuration, Synchronize the data to eNodeBs.

Figure 4-18 Punishment and Detection Timer for SN Configuration Failures
4.1.7 SN SPID-based Policy
4.1.7.1 Related Parameter
Table 4-9 SN SPID-based policy Related Parameter
NO Parameter Parameter Parameter explanation Range val Default v

name ue alue
1 EnDcCoverage.e EN-DC SPI This parameter indicates whether SPID function is supported in ENDC sc {Close[Cl Close[Clo
ndcCoverageSpi D switch enarios. ose] se]
dSwch Open[Op
en]}
2 EnDcCoverageS EN-DC Inte This parameter sets whether to enable inter-frequency PSCell change in {Close[Cl Close[Clo
PIDProfiles.endc r-frequenc EN-DC scenarios. If the parameter is set to On, the UE can perform inter-f ose] se]
PSCellInterFCha y PSCell C requency PSCell changes. If the parameter is set to Off, the UE cannot Open[Op
ngeSwch hange perform inter-frequency PSCell changes. en]}
3 EnDcCoverageS Label num This parameter indicates the operator's custom SPID list. [1..256] Null
PIDProfiles.spid ber of SPID
List list
1 SN SPID-based policy parameters:
Select [ManagedElement-> gNB CU-CP function configuration -> CU cell configuration-> ENDC coverage based mobility strategy], Click
for data synchronization to the gNB.
Figure 4-19 SN SPID-based policy Related Parameters
40 - 89
EN-DC Enhancement
1 Coverage-based SPID mobility policy in the EN-DC scenario parameters:
Select [ManagedElement-> gNB CU-CP function configuration -> CU cell configuration-> ENDC coverage based mobility strategy-> ENDC
coverage based spid profiles], Click for data synchronization to the gNB.
Figure 4-20 Coverage-based SPID mobility policy in EN-DC Related Parameters
4.1.8 Multi Factor Joint awared SN Handling Enhancement for NSA
41 - 89
EN-DC Enhancement
Table 4-10 SN addition Policy based on Joint Decision Related Parameter

r r name ue alue
1 CellMeas NR Inter- This parameter indicates the inter-RAT measurement configuration index for SN [1..65535] 2100;210
GroupLT RAT Meas addition by the EN-DC function. 0;2100;21
E.nRSNR urement I 00;2100;2
atAddMe ndex for S 100;2100;
asCfg N Additio 2100
n in ENDC
2 NrRatMe Measure This parameter sets the measurement quantity used by UEs during NR system m 0:rsrp{rsr 0
asCfgLTE. ment Qua easurement, 0 for RSRP, 1 for RSRQ, and 2 for SINR. p},1:rsrq{
quantity ntity of th rsrq},2:si
NR e NR Syst nr{sinr}
em
3 NrRatMe Measure This parameter sets the measurement reporting quantity with which a UE report [0..1] step 1;0;0
asCfgLTE. ment Rep s measured values during NR cell measurement. It is a three-dimensional array. 1
rpQuantit ort Quant The first element represents the reported RSRP measurement quantity, the seco
yNRbitm ity of the nd element represents the reported RSRQ measurement quantity, and the third
ap NR Syste element represents the reported SINR measurement quantity. If an element valu
m e is set to 1, it indicates that the UE needs to report the measured value. If an ele
ment value is set to 0, it indicates that the UE does not need to report the measur
ed value.
4 [FDD] Joint Deci This parameter enables or disables the joint decision for SN addition in an EN-D 0: {Close}, 0;0;0
ENDCPoli sion Swit C scenario. If it is set to RSRP and RSRQ Joint Judge, the base station determines 1: {RSRP
cyFDDLT ch for EN- whether the RSRP and the RSRQ meet the conditions while performing the B1 m and RSR
E.endcJoi DC SN Ad easurement for SN addition. If this parameter is set to RSRP and SINR Joint Judg Q Joint J
ntJudgeS dition e, the base station determines whether the RSRP and the SINR meet the conditio udge},2: {
wch ns while performing the B1 measurement for SN addition. RSRP and
[TDD] SINR Join
ENDCPoli t Judge}
cyTDDLT
E.endcJoi
ntJudgeS
wch
5 [FDD] RSRP Thr This parameter sets the RSRP threshold for NR neighbor cells in the joint decisio [-156..-29 -105
NRFreqP eshold for n of SN addition in an EN-DC scenario. If the RSRP of an NR neighbor cell is lower ]
araFDDL NR Neigh than this threshold, this neighbor cell cannot be added as a PSCell of the SN.
TE.snAdd bor Cells i
JointJud n Joint De
geRsrpTh cision for
rd EN-DC SN
[TDD] Addition
NRFreqP
araTDDL
TE.snAdd
JointJud
geRsrpTh
rd
42 - 89
EN-DC Enhancement
6 [FDD] RSRQ Thr This parameter sets the RSRQ threshold for NR neighbor cells in the joint decisio [-43.5..20] -12.5
NRFreqP eshold for n of SN addition in an EN-DC scenario. If the RSRQ of an NR neighbor cell is lower
araFDDL NR Neigh than this threshold, this neighbor cell cannot be added as a PSCell of the SN.
JointJud n Joint De
geRsrqTh cision for
rd EN-DC SN
[TDD] Addition
NRFreqP
araTDDL
TE.snAdd
JointJud
geRsrqTh
rd
7 [FDD] SINR Thre This parameter sets the SINR threshold for NR neighbor cells in the joint decision [-23..40.5] 5.0
NRFreqP shold for of SN addition in an EN-DC scenario. If the SINR of an NR neighbor cell is lower th
araFDDL NR Neigh an this threshold, this neighbor cell cannot be added as a PSCell of the SN.
JointJud n Joint De
geSinrThr cision for
d EN-DC SN
[TDD] Addition
NRFreqP
araTDDL
TE.snAdd
JointJud
geSinrThr
d
1 Configure NR Inter-RAT Measurement Index for SN Addition in ENDC.
FDD:Select[Managed Element -> eNodeB CU -> LTE -> UE measurement-> Meaurement Config Group],
TDD: Select[Managed Element -> eNodeB CU -> LTE -> UE measurement-> Meaurement Config Group],
set NR Inter-RAT Measurement Index for SN Addition in ENDC, save configuration, Synchronize the data to eNodeBs.
Figure 4-21 NR Inter-RAT Measurement Index for SN Addition in ENDC
43 - 89
EN-DC Enhancement
1 Configure Measurement Quantity of the NR System and Measurement Report Quantity of the NR System.
FDD:Select[Managed Element -> eNodeB CU -> LTE -> UE measurement-> UE NR RAT Meaurement],
TDD: Select[Managed Element -> eNodeB CU -> LTE -> UE measurement-> UE NR RAT Meaurement],
set Measurement Quantity of the NR System and Measurement Report Quantity of the NR System, save configuration, Synchronize the data to
eNodeBs.
Figure 4-22 Measurement Quantity of the NR System and Measurement Report Quantity of the NR System
44 - 89
EN-DC Enhancement
1 Configure Joint Decision Switch for EN-DC SN Addition.
FDD:Select[Managed Element -> eNodeB CU -> LTE -> E-UTRAN FDD Cell-> LTE FDD EN-DC policy],
TDD: Select[Managed Element -> eNodeB CU -> LTE -> E-UTRAN TDD Cell-> LTE TDD EN-DC policy],
set Joint Decision Switch for EN-DC SN Addition, save configuration, Synchronize the data to eNodeBs.
Figure 4-23 Joint Decision Switch for EN-DC SN Addition
45 - 89
EN-DC Enhancement
1 RSRP Threshold for NR Neighbor Cells in Joint Decision for EN-DC SN Addition, RSRQ Threshold for NR Neighbor Cells in Joint
Decision for EN-DC SN Addition and SINR Threshold for NR Neighbor Cells in Joint Decision for EN-DC SN Addition.
FDD:Select[Managed Element -> eNodeB CU -> LTE -> E-UTRAN FDD Cell-> LTE FDD Measurement Parameter->NR Frequency Related
Configuration],
TDD: Select[Managed Element -> eNodeB CU -> LTE -> E-UTRAN TDD Cell-> LTE TDD Measurement Parameter->NR Frequency Related
Configuration],
set RSRP Threshold for NR Neighbor Cells in Joint Decision for EN-DC SN Addition, RSRQ Threshold for NR Neighbor Cells in Joint Decision for
EN-DC SN Addition and SINR Threshold for NR Neighbor Cells in Joint Decision for EN-DC SN Addition, save configuration, Synchronize the
data to eNodeBs.
Figure 4-24 RSRP/RSRQ Threshold for NR Neighbor Cells in Joint Decision for EN-DC SN Addition
46 - 89
EN-DC Enhancement
4.1.9 NR Multi-Measurement and Joint Decision Strategy
Table 4-11 NR multi-measurement and joint decision strategy related parameter
NO Parameter Parameter Parameter explanation Range value Default

name value
1 EnDcCove EN-DC multi- This parameter sets the multi- {Close[Close], Close[Close]
rage.endc measurement measurement strategy for SN deletion RsrpAndRsrq[RsrpAndRsrq],
MultMeas strategy and change in EN-DC scenarios. If this RsrpAndSinr[RsrpAndSinr]}
Stgy parameter is set to Close, the gNodeB
delivers only one set of measurement
configuration. If this parameter is set to
RsrpAndRsrq, the gNodeB delivers two
sets of measurement configuration (RSRP
+ RSRQ) to the SN side. If this parameter
is set to RsrpAndSinr, the gNodeB delivers
two sets of measurement configuration
(RSRP + SINR) to the SN side.
2 EnDcCove Index of the A2 This parameter sets the index of an event Null Null
rageIntraF measurement A2 measurement report of the SN cell
MeasConfi configuration released in EN-DC scenarios based on
g.refNRDc for SN cell RSRQ. It is used to select a measurement
RelPSCell release based report configuration for the event A2
A2RSRQ on RSRQ measurement of the SN cell released in
EN-DC scenarios.
47 - 89
EN-DC Enhancement
3 EnDcCove Index of the A2 This parameter sets the index of the event Null Null
rageIntraF measurement A2 measurement report of the SN cell
MeasConfi configuration released EN-DC scenarios based on SINR.
g.refNRDc for SN cell It is used to select a measurement report
RelPSCell release based configuration for the event A2
A2SINR on SINR measurement of the SN cell released in
EN-DC scenarios.
4 EnDcCove Index of the This parameter sets the index of the Null Null
rageIntraF event A measurement report for PSCell intra-
MeasConfi measurement frequency changes based on RSRQ in EN-
g.refNRPS configuration DC scenarios. It is used to select a
CellChang for triggering measurement report configuration for
eIntraFRS intra-frequency measuring SN cell changes.
RQ PSCell change
based on RSRQ
in EN-DC
scenarios
5 EnDcCove Index of the This parameter sets the index of the Null Null
rageIntraF event A measurement report for PSCell intra-
MeasConfi measurement frequency changes based on SINR in EN-
g.refNRPS configuration DC scenarios. It is used to select a
CellChang for triggering measurement report configuration for
eIntraFSIN intra-frequency measuring SN cell intra-frequency
R PSCell change changes.
based on SINR
in EN-DC
scenarios
6 EnDcCove Index of the This parameter sets the measurement Null Null
rageIntraF A1/A2 configuration index of "event A1
MeasConfi measurement measurement configuration for enabling
g.refInterF configuration PSCell inter-frequency change based on
PSCellCha for inter- RSRQ and event A2 measurement
ngeA1A2R frequency configuration for disabling PSCell inter-
SRQ PSCell change frequency change based on RSRQ" in EN-
based on RSRQ DC scenarios. It is used to select a
in EN-DC measurement configuration for "event A1
scenarios measurement for enabling PSCell inter-
frequency change based on RSRQ and
event A2 measurement for disabling
PSCell inter-frequency change based on
RSRQ" in EN-DC scenarios.
7 EnDcCove Index of the This parameter sets the measurement Null Null
rageIntraF A1/A2 configuration index of "event A1
MeasConfi measurement measurement configuration for enabling
g.refInterF configuration PSCell inter-frequency change based on
PSCellCha for inter- SINR and event A2 measurement
ngeA1A2SI frequency configuration for disabling PSCell inter-
NR PSCell change frequency change based on SINR" in EN-
based on SINR DC scenarios. It is used to select a
in EN-DC measurement configuration for "event A1
scenarios measurement for enabling PSCell inter-
frequency change based on SINR and
event A2 measurement for disabling
PSCell inter-frequency change based on
SINR" in EN-DC scenarios.
48 - 89
EN-DC Enhancement
8 EnDcCove Index of the This parameter sets the index of a Null Null
rageInterF event A measurement report for PSCell inter-
MeasConfi measurement frequency change based on RSRQ in EN-
g.refNRPS configuration DC scenarios. It is used to select an SN
CellChang for triggering change measurement report
eInterFRS inter-frequency configuration for the frequency point at
RQ PSCell change which SN change is executed.
based on RSRQ
in EN-DC
scenarios
9 EnDcCove Index of the This parameter sets the index of a Null Null
rageInterF event A measurement report for PSCell inter-
MeasConfi measurement frequency change based on SINR in EN-
g.refNRPS configuration DC scenarios. It is used to select an SN
CellChang for triggering change measurement report
eInterFSIN inter-frequency configuration for the frequency point at
R PSCell change which SN change is executed.
based on SINR
in EN-DC
scenarios
10 EnDcCove Joint decision This parameter sets the joint decision {Close[0],RSRP+RSRQ[1],RSRP+SINR[2]} Close[0];
rage.endc strategy in EN- strategy for SN change in EN-DC Close[0];
UnitJudgS DC scenarios. If this parameter is not set to Close[0]
tgy Close, the gNodeB needs to consider to
replace the SN of the UE by multiple
measurement values.
11 EnDcCove RSRP threshold This parameter sets the RSRP threshold [-156..-31] -105
rageIntraF for joint for replacing the SN with a neighbor cell
MeasConfi decision on NR in EN-DC scenarios. If the value of the EN-
g.endcUni neighbor cells DC joint judgment policy
tJudgNbR in EN-DC (endcUnitJudgStgy) is not Disabled, the
SRPThrd scenarios gNodeB will select a neighbor cell whose
RSRP is larger than this threshold when
changing SN.
12 EnDcCove RSRQ This parameter sets the RSRQ threshold [-43..20] -12.0
rageIntraF threshold for for replacing the SN with a neighbor cell
MeasConfi joint decision in EN-DC scenarios. If the value of the EN-
g.endcUni on NR neighbor DC joint judgment policy
tJudgNbR cells in EN-DC (endcUnitJudgStgy) is not Disabled, the
SRQThrd scenarios gNodeB will select a neighbor cell whose
RSRQ is larger than this threshold when
changing SN.
13 EnDcCove SINR threshold This parameter sets the SINR threshold [-23..40.5] 5.0
rageIntraF for joint for replacing the SN with a neighbor cell
tJudgNbSI in EN-DC (endcUnitJudgStgy) is not Disabled, the
NRThrd scenarios gNodeB will select a neighbor cell whose
SINR is larger than this threshold when
changing SN.
rageIntraF for joint for replacing the SN with a serving cell in
MeasConfi decision on the EN-DC scenarios. If the value of the EN-DC
g.endcUni NR serving cell joint judgment policy
tJudgSrvR in EN-DC (endcUnitJudgStgy) is not Disabled and
SRPThrd scenarios the RSRP of the serving cell is lower than
this threshold, the gNodeB may replace
the SN with the neighbor cell that does
not meet the joint judgment conditions.
49 - 89
EN-DC Enhancement
rageIntraF threshold for for replacing the SN with a serving cell in
MeasConfi joint decision EN-DC scenarios. If the value of the EN-DC
g.endcUni on the NR joint judgment policy
tJudgSrvR serving cell in (endcUnitJudgStgy) is not Disabled and
SRQThrd EN-DC the RSRQ of the serving cell is lower than
scenarios this threshold, the gNodeB may replace
the SN with a neighbor cell that does not
meet the joint judgment conditions.
rageIntraF for joint for replacing the SN with a serving cell in
MeasConfi decision on the EN-DC scenarios. If the value of the EN-DC
g.endcUni NR serving cell joint judgment policy
tJudgSrvS in EN-DC (endcUnitJudgStgy) is not Disabled and
INRThrd scenarios the SINR of the serving cell is lower than
this threshold, the gNodeB may replace
the SN with a neighbor cell that does not
meet the joint judgment conditions.
rageInterF for joint for replacing the SN with a neighbor cell
tJudgNbR in EN-DC (endcUnitJudgStgy) is not Disabled, the
SRPThrd scenarios gNodeB will select a neighbor cell whose
RSRP is larger than this threshold when
changing SN.
rageInterF threshold for for replacing the SN with a neighbor cell
MeasConfi joint decision in EN-DC scenarios. If the value of the EN-
g.endcUni on NR neighbor DC joint judgment policy
tJudgNbR cells in EN-DC (endcUnitJudgStgy) is not Disabled, the
SRQThrd scenarios gNodeB will select a neighbor cell whose
RSRQ is larger than this threshold when
changing SN.
rageInterF for joint for replacing the SN with a neighbor cell
tJudgNbSI in EN-DC (endcUnitJudgStgy) is not Disabled, the
NRThrd scenarios gNodeB will select a neighbor cell whose
SINR is larger than this threshold when
changing SN.
20 MobilityCt Switch for This parameter sets whether to enable {Close[Close],Open[Open]} Close[Close]
rl.measRe Measurement measurement report reordering. If this
portReord Report parameter is set to Open, the gNodeB
erSwch Reordering reorders the neighbor cells in accordance
with the SINR and RSRQ measurement
result for NSA and SA measurement
reports triggered by RSRP, and SINR-
based reordering takes precedence. The
NSA and SA measurement reports
triggered by RSRQ are reordered based
on the SINR measurement result.
1 Configure EN-DC multi-measurement strategy and ENDC united-decision strategy.
Select[Managed Element -> gNB CU-CP function configuration -> CU cell configuration -> ENDC coverage based mobility strategy],
set EN-DC multi-measurement strategy and Joint decision strategy in EN-DC, save configuration, Synchronize the data to gNodeBs.
Figure 4-25 EN-DC multi-measurement strategy and Joint decision strategy in EN-DC
50 - 89
EN-DC Enhancement
1 Configure Intra-frequency measurement report configuration index.
Select[Managed Element -> gNB CU-CP function configuration -> CU cell configuration -> ENDC coverage based mobility strategy -> ENDC
coverage based measure config -> ENDC coverage based intra-frequency measure config],
set Intra-frequency measurement report configuration index, save configuration, Synchronize the data to gNodeBs.
Figure 4-26 Intra-frequency measurement report configuration index
51 - 89
EN-DC Enhancement
1 Configure Inter-frequency measurement report configuration index.
coverage based measure config -> ENDC coverage based inter-frequency measure config],
set Inter-frequency measurement report configuration index, save configuration, Synchronize the data to gNodeBs.
Figure 4-27 Inter-frequency measurement report configuration index
52 - 89
EN-DC Enhancement
1 Configure Intra-frequency joint decision parameters.
coverage based measure config -> ENDC coverage based intra-frequency measure config],
set Intra-frequency joint decision parameters, save configuration, Synchronize the data to gNodeBs.
Figure 4-28 Intra-frequency joint decision parameters
53 - 89
EN-DC Enhancement
1 Configure Inter-frequency joint decision parameters.
coverage based measure config -> ENDC coverage based inter-frequency measure config],
set Inter-frequency joint decision parameters, save configuration, Synchronize the data to gNodeBs.
Figure 4-29 Inter-frequency joint decision parameters
54 - 89
EN-DC Enhancement
1 Configure Switch for Measurement Report Reordering.
Select[Managed Element -> gNB CU-CP function configuration -> CU cell configuration -> Mobility Control],
set Switch for Measurement Report Reordering, Synchronize the data to gNodeBs.
Figure 4-30 Switch for Measurement Report Reordering
4.1.10 Counter Check
55 - 89
EN-DC Enhancement
Table 4-12 LTE Counter Check parameters

r r name ue alue
1 GlobalQo Switch fo This parameter enables or disables counter check reporting. It is used to control {0:Close, Close
SLTE.cou r Counter whether the eNodeB reports count value differences to the EMS. If it is set to Ope 1:Open}
nterChec Check Re n, the eNodeB reports count value differences to the EMS, informing whether the
kRptSwc porting re are external packet attacks. If it is set to Close, the notifications of count value
h differences are not reported.
2 GlobalQo Reportin Both packet attack and network delay cause the difference between count value {0:128, 512
SLTE.cou g Thresh s. This parameter sets the threshold for the counter check function to report the c 1:256,
nterChec old for Co ount value differences to the EMS. If the network delay is longer, a higher thresho 2:512,
kRptThrd unter Che ld can prevent the difference between the count values that are falsely reported. I 3:1024,
ck f the network delay is shorter, a lower threshold can prevent packet attacks from 4:2048,
not being reporting. 5:4096,
6:8192,
7:16384}
4.1.10.1.2 LTE Parameters Configuration
Purpose
Both the packet attack and the network delay will cause the PDCP COUNT value difference. It is necessary to configure proper PDCP Counter
Check parameters and the report switch to prevent potential malicious packet attack risks while misreporting.
Procedure
1 Select[Managed Element -> eNodeB CU -> LTE->Qos->Global Qos Parameter], set Switch for Counter Check Reporting and Reporting
Threshold for Counter Check, save configuration, and then ynchronize the data to eNodeBs.
Figure 4-31 Counter Check parameters configuration at LTE side
56 - 89
EN-DC Enhancement
4.1.10.2 NR Parameters
4.1.10.2.1 NR Related Parameters
Table 4-13 NR Counter Check parameters
NO Parameter Parameter Parameter explanation Range val Default v

name ue alue
1 EnDCPDCP.p Switch of This parameter sets whether to enable the PDCP COUNT check function. Wh {0:Close, Close
dcpCounterC PDCP COU en this parameter is set to 1 (Open), the system can detect the attacks of mal 1:Open}
heckSwitch NT check icious packets in radio transmission to guarantee network security.
2 EnDCPDCP.p PDCP COU This parameter sets the bit that triggers a PDCP COUNT check flow when the [16..31] 31
dcpCounterC NT check bit changes from 0 to 1. The smaller the parameter value is, the easier it is to
heckBit bit trigger the PDCP COUNT check flow.
4.1.10.2.2 NR Parameters Configuration
Purpose
In the EN-DC scenario, enable the PDCP Counter Check function and set the frequency at which PDCP Count is triggered to detect potential
risks of malicious packet attacks on the air interface.
Procedure
1 Select[Managed Element -> gNB CU-CP function configuration -> EnDCConfigCU->PDCP parameter for dual-connection between
LTE and NR], set Switch of PDCP COUNT check and PDCP COUNT check bit, save configuration, and then synchronize the data to
gNodeBs.
Figure 4-32 Counter Check parameters configuration at NR side
57 - 89
EN-DC Enhancement
4.1.11 NSA Inter-frequency PSCell Change based on Uplink Channel Quality
4.1.11.1 Related Paramete
Table 4-14 NSA inter-frequency PSChange based on uplink channel quality related parameter
NO Parameter Parameter Parameter Range value Default value

name explanation
1 PSCellDataQualMig.pscellDataQualMi Switch of This {0:Close:(), 1:Open:()} Close[0]

gSwch PSCell data parameter
quality‒ sets whether
based to enable the
migration function of
migration
based on
PSCell data
quality. When
this parameter
is set to Open,
it indicates
that the
gNodeB
actively
changes the
PSCell of the
UE to another
frequency
point when
the uplink
quality in the
PSCell is poor.
58 - 89
EN-DC Enhancement
2 PSCellDataQualMig.pscellDataQualMi Waiting timer This [1,1800] 4

gMeasTimer for migration parameter
measurement sets the timer
based on for the
PSCell migration
quality(s) measurement
based on
PSCell quality.
After the
configuration
of migration
measurement
based on
PSCell quality
is delivered,
this timer is
started for
waiting for the
measurement
report. If no
measurement
report is
submitted
after the timer
expires, the
measurement
configuration
of the PSCell
quality‒based
migration
function is
changed.
3 PSCellDataQualMig.pscellDataQualMi Index of the Maximum [0,60],65535 0

gMaxRetryNum A2 number of
measurement retries for
configuration PSCell
for SN cell quality‒based
release based migration
on SINR
4 PSCellDataQualMig.pscellDataQualMi Timer for This [1,1800] 30

gRetryTimer retrying parameter
migration sets the timer
based on for retrying
PSCell migration
quality(s) based on
PSCell quality.
If a UE fails to
trigger
migration
based on
PSCell quality,
the PSCell
quality‒based
migration
procedure can
be triggered
again in
accordance
with the
parameter
setting.
59 - 89
EN-DC Enhancement
5 PSCellDataQualMigInterFMeasCfg.refI Reference for This [1..400] Null

nterFMeasObject the NR parameter
measurement sets the
object index reference of
the index of
an inter-
frequency
measurement
object for
PSCell
quality‒based
migration.
6 PSCellDataQualMigInterFMeasCfg.refP Index of inter- This [1..400] Null

SCellDataQualMigRptCfg frequency parameter
handover sets the index
measurement of LTE inter-
configuration frequency
for PSCell migration
quality‒ measurement
based configuration
migration for PSCell
quality‒based
migration.
7 PSCellDataQualMigInterFMeasCfg.psc Inter- This [0..255] 255

ellDataQualMigInterFreqPrio frequency parameter
frequency sets the Inter-
point priority frequency
for PSCell frequency
quality‒ point priority
based for PSCell
migration quality‒based
migration.
When the
priority is 0, it
indicates that
the
corresponding
frequency
point does not
support
migration
based on
PSCell quality.
When the
priority is a
non-zero
value, it
indicates that
the
corresponding
frequency
point
supports
migration
based on
PSCell quality.
The larger the
parameter
value is, the
higher the
priority is.
60 - 89
EN-DC Enhancement
8 DataQualDetect.dataQualDetectUtility Quality This [DataQualMig, DataQualMig[DataQualMig]

detection parameter is SNReleaseBaseDataQual,
configuration used for data PSCellChangeBaseDataQual]
purpose quality
detection.
This
parameter can
be set to
different
values for the
gNodeB for
different
quality
detection
functions.
1 Configure quality detection configuration purpose.
Select[Managed Element -> gNB DU function configuration -> Cell DU ->DU Quality Detect],
set Quality detection configuration purpose, save configuration, Synchronize the data to gNodeBs.
The default value of Quality detection configuration purpose is DataQualMig[DataQualMig], used to SA inter-frequence migration based-on
Uplink Channed Quality.NSA inter-frequence PSCell Change based-on Uplink Channed Quality configuration for Quality detection
configuration purpose is required as PSCellChangeBaseDataQual[PSCellChangeBaseDataQual].
Figure 4-33 Configure quality detection configuration purpose
1 Configure PSCell change based on data quality strategy.
Select[Managed Element -> gNB CU-CP function configuration -> CU cell configuration -> PSCell data quality‒based migration configuration],
set Switch of PSCell data quality‒based migration, Waiting timer for migration measurement based on PSCell quality(s) , Maximum number of
retries for PSCell quality‒based migration and Timer for retrying migration based on PSCell quality(s), save configuration, Synchronize the
data to gNodeBs.
61 - 89
EN-DC Enhancement
Figure 4-34 Configure PSCell change based on data quality strategy
1 Configure measurement report configuration index for PSCell change based on data quality.
Select[Managed Element -> gNB CU-CP function configuration -> CU cell configuration -> PSCell data quality‒based migration configuration -
> PSCell data quality‒based migration measurement configuration],
set Index of inter-frequency handover measurement configuration for PSCell quality‒based migratio, save configuration, Synchronize the data
to gNodeBs.
Figure 4-35 Configure measurement report configuration index for PSCell change based on data quality
62 - 89
EN-DC Enhancement
1 Configure measurement object index for PSChange based on data quality.
Select [Managed Element -> gNB CU-CP function configuration -> CU cell configuration -> PSCell data quality‒based migration configuration -
> PSCell data quality‒based migration measurement configuration],
set Reference for the NR measurement object index, save configuration, and synchronize the data to gNodeBs.
Figure 4-36 Configure measurement object index for PSCell change based on data quality
4.1.12 Activation Observation
4.1.12.1 Uplink Data Split
If you observe the following signaling in the signaling, uplink data split parameters are configured for UE(If ul_DataSplitThreshold is not infinit,
uplink data split is enabled).
Figure 4-37 Uplink Data split
4.1.13 Network Impact
1 Impact on performance
Null
1 Impact on KPIs
63 - 89
EN-DC Enhancement
The EN-DC feature can use dual connectivity technology between LTE and NR to improve throughput and latency. In a hotspot or large-
capacity coverage scenario, UEs can use the multi-cell radio resources to transfer data, therefore, user throughput can be improved.
After NSA is enabled, there are 4G users and NSA users in the system. This will affect traditional KPIs. And 4G load will increase.
4.2 Uplink Power Control for EUTRAN and NR
4.2.1 Requirements
E-UTRAN:
BBU Type: V9200
Board Type: VBPc, VBPd
Main control board: VSWc, VSWd
NR:
BBU Type: V9200
Board Type: VGC, VBPc5
EPC supports R15, QoS extension, EN-DC and Secondary RAT Data Volume Report.
UE supports R15, and has capability of E-UTRAN, NR and EN-DC.
Table 4-15 FDD License requirement
NO FL FL Name License File No. License Control name Control lev

el
1 ZLF40-08- Dynamic power sharing for EUTRAN LTE- LTE FDD NSA ue support dynamic power eNB level
014 and NR FDD_ENB_F270 sharing
Table 4-16 TDD License requirement
NO FL FL Name License File No. License Control name Control lev

el
1 ZLT45-08- Dynamic power sharing for EUTRAN LTE- TD LTE NSA ue support dynamic power eNB level
014 and NR TDD_ENB_F270 sharing
4.2.2 Function Activation
4.2.2.1 Uplink Power Control between EUTRAN and NR
64 - 89
EN-DC Enhancement
Table 4-17 Related parameter of Uplink Power Control between EUTRAN and NR
NO Paramete Parameter Parameter explanation Range val Default v

r name ue alue
1 FDD: Maximum Tx In an NSA scenario, this parameter is used to allocate the maximum Tx [-30..33] 20
PowerCo Power power to the LTE UEs that do not support power sharing. step 1
ntrolULF Allocated to
DDLTE.p the LTE UEs
maxOfLte Not
4NonShar Supporting
ingPwrUE Power
TDD: Sharing
PowerCo
ntrolULT
DDLTE.p
maxOfLte
4NonShar
ingPwrUE
2 FDD: Switch for UL This parameter is used to configure whether the NSA UE enables semi-static {0:Close, Close
PowerCo Power configuration of the maximum transmit power at the LTE/NR side. 1:Open}
ntrolULF Adaptive
DDLTE.ad Allocation for
pAllocNsa NSA Ues
UlPwrSw
ch
TDD:
PowerCo
ntrolULT
DDLTE.ad
pAllocNsa
UlPwrSw
ch
3 FDD: Upper Limit This parameter controls the allocation of the power of NSA UEs on both the [-30..33] 22
PowerCo of UL LTE Tx LTE and NR sides in a semi-static way. With the current power sharing step 1
ntrolULF Power for solution in an NSA scenario, LTE cells and NR cells occupy 20 dBm of the
DDLTE.m NSA UEs power by default, and therefore the coverage of far points is limited due to
axAdpUlL insufficient uplink power. This parameter can be used to solve this problem.
tePwrOfN If the power of an LTE cell is restricted, higher power can be reconfigured to
sa the LTE cell.
TDD:
PowerCo
ntrolULT
DDLTE.m
axAdpUlL
tePwrOfN
sa
4.2.2.1.2 LTE Parameter Configuration
1 Maximum Tx Power Allocated to the LTE UEs Not Supporting Power Sharing.
FDD: Select [Managed Element -> eNodeB CU -> LTE -> E-UTRAN FDD Cell -> LTE FDD UL Power Control],
TDD: Select [Managed Element -> eNodeB CU -> LTE -> E-UTRAN TDD Cell -> LTE TDD UL Power Control],
Set Maximum Tx Power Allocated to the LTE UEs Not Supporting Power Sharing.Synchronize the data to eNodeB.
Figure 4-38 Maximum Tx Power Allocated to the LTE UEs Not Supporting Power Sharing
65 - 89
EN-DC Enhancement
1 Semi-Static Power Sharing for NSA UEs
set Switch for UL Power Adaptive Allocation for NSA UEs to Open[1] and Upper Limit of UL LTE Tx Power for NSA UEs. Synchronize the data to
eNodeB.
Figure 4-39 Switch for UL Power Adaptive Allocation for NSA UEs and Upper Limit of UL LTE Tx Power for NSA UEs
4.2.2.2 Dynamic Uplink Power Sharing for EUTRAN and NR
66 - 89
EN-DC Enhancement
Table 4-18 Related parameter of Dynamic Uplink Power Sharing for EUTRAN and NR
NO Paramete Parameter nam Parameter explanation Range val Default v

r e ue alue
1 FDD: Power This parameter sets the power allocation type for the UE that supports and 0: Shut 0: Shut
PowerCo Allocation Type enables dynamic power sharing. If it is set to EnodeB distribute LTE/NR Down Down
ntrolULF in Dynamic power, the total transmit power of the UE in both the LTE and NR systems Dynamic Dynamic
DDLTE.o Power Sharing does not exceed the maximum transmit power of the UE. If it is set to UE Sharing Sharing
pt4DynSh for NSA UEs distribute LTE/NR power, the transmit power of the NR system is reduced Power, Power
aringPwr when the total transmit power of the UE in both the LTE and NR systems 1:
NsaUE exceeds the maximum transmit power of the UE. EnodeB
TDD: distribute
PowerCo LTE/NR
ntrolULT power,
DDLTE.o 2: UE
pt4DynSh distribute
aringPwr LTE/NR
NsaUE power
2 FDD: Optimization This parameter enables or disables the optimization for the assistant 0:Close, 0:Close
PowerCo Switch for scheduler of the NSA eNodeB. If it is set to Open, the uplink traffic on the 1:Open
ntrolULF Assistant NSA LTE side increases in the case of power restriction.
DDLTE.n eNodeB
SAPowAll Schedulers
oOptiSwc
h
TDD:
PowerCo
ntrolULT
DDLTE.n
SAPowAll
oOptiSwc
h
3 FDD: Maximum Tx This parameter sets the maximum transmit power on the LTE side when [-30..33] 22
PowerCo Power on the the optimization for the assistant scheduler of the NSA eNodeB is enabled. step 1
ntrolULF LTE Side in the The maximum uplink transmit power of a UE on the LTE side cannot
DDLTE.n Case of exceed this parameter value.
SALTEPm Assistant-
ax Scheduler
TDD: Optimization
PowerCo for NSA
ntrolULT eNodeBs
DDLTE.n
SALTEPm
ax
1 Configure Power Allocation Type in Dynamic Power Sharing for NSA UEs
set Power Allocation Type in Dynamic Power Sharing for NSA UEs to EnodeB distribute LTE/NR power[1] or UE distribute LTE/NR power[2].
Synchronize the data to eNodeB.
Figure 4-40 Power Allocation Type in Dynamic Power Sharing for NSA UEs
67 - 89
EN-DC Enhancement
1 Configure Optimization Switch for Assistant NSA eNodeB Schedulers and Maximum Tx Power on the LTE Side in the Case of
Assistant-Scheduler Optimization for NSA eNodeBs
set Optimization Switch for Assistant NSA eNodeB Schedulers to close[0] and Maximum Tx Power on the LTE Side in the Case of Assistant-
Scheduler Optimization for NSA eNodeBs to 22. Synchronize the data to eNodeB.
Figure 4-41 Configure Optimization Switch for Assistant NSA eNodeB Schedulers and Maximum Tx Power on the LTE Side in the Case of
Assistant-Scheduler Optimization for NSA eNodeBs
68 - 89
EN-DC Enhancement
4.2.3 Functional Deactivation
4.2.3.1 Uplink Power Control between EUTRAN and NR
set Switch for UL Power Adaptive Allocation for NSA UEs to Close[0]. Synchronize the data to eNodeB.
Figure 4-42 Semi-Static Power Sharing for NSA UEs Deactivation Configuration
4.2.3.2 Dynamic Uplink Power Sharing for EUTRAN and NR
set Power Allocation Type in Dynamic Power Sharing for NSA UEs to Shut Down Dynamic Sharing Power[0]. Synchronize the data to eNodeB.
Figure 4-43 Dynamic Power Sharing for NSA UEs Deactivation Configuration
69 - 89
EN-DC Enhancement
4.2.4 Network Monitoring
None.
4.2.5.1 Gain Analysis
After semi-static power sharing function is enabled, for NSA UEs that do not support dynamic power sharing, uplink traffic gains may occur on
the LTE side at far points.
After dynamic power sharing function is enabled, for NSA UEs that support dynamic power sharing, uplink spectrum efficiency gains may
occur on the LTE side at far points. If optimization switch for assistant NSA eNodeB schedulers is turned on at the same time, uplink traffic
gains may occur on the LTE side at far points, but the uplink spectrum efficiency gain may be reduced.
4.2.5.2 Impact Analysis
None.
4.3 Interference Suppressed Under EUTRAN-NR Dual Connectivity (Trial)
4.3.1 Requirements
E-UTRAN:
BBU Type: V9200
Board Type: VBPc,VBPd
Main control board: VSWc,VSWd
NR:
BBU Type: V9200
Board Type: VGC, VBPc5
70 - 89
EN-DC Enhancement
EPC supports R15, QoS extension, EN-DC and Secondary RAT Data Volume Report.
UE supports R15, and has capability of E-UTRAN, NR and EN-DC.
No special requirements.
None.
4.3.2 Function Activation
4.3.2.1 Harmonic Interference Avoidance Function Activation
4.3.2.1.1 LTE Parameters
Table 4-19 Related Parameters of the Harmonic Interference Avoidance Function
NO Paramete Parameter n Parameter explanation Range value Default value

r ame
1 FDD: Harmonic- This parameter is used to set harmonic-interference 0: Close harmonic 0: Close harmonic
PhyChan Interference avoidance mode. If it is set to 0, it indicates that harmonic- interference interference
nelFDDLT Avoidance interference avoidance is disabled. If it is set to 1, it avoidance avoidance
E.harmIn Mode indicates that static harmonic-interference avoidance is 1: Open static
terferAvoi enabled and UE location information is not exchanged harmonic
dMode between LTE and NR. If it is set to 2, it indicates that semi- interference
static-harmonic interference avoidance is enabled, the avoidance
near-/far-point location information of harmonic UEs is 2: Open Semi-Static
considered, and UE location information is exchanged Harmonic
between LTE and NR. Interference
Avoidance
2 FDD: Harmonic- This is harmonic-interference coordination switch. If it is 0: NR downlink for 0: NR downlink

PhyChan Interference set to 0, harmonic-interference avoidance is performed in harmonic for harmonic
nelFDDLT Coordination the downlink of NR cells. This strategy is used to ensure interference interference
E.harmon Switch the traffic on the LTE side. If it is set to 1, harmonic- avoidance avoidance
icSwitch interference avoidance is performed in the downlink of 1: LTE uplink for
LTE cells. This strategy is used to ensure the traffic on the harmonic
NR side. interference
avoidance
3 FDD: PUCCH The parameter is a switch for PUCCH blanking, 0: close 1: 0:Close 0:Close
PhyChan Blanking open 1:Open
nelFDDLT
E.pucchB
lankFlag
71 - 89
EN-DC Enhancement
4 FDD: Numbers of The parameter defines the number of RBs for PUCCH [0..98] 0
PhyChan Blanked RB Blanking
nelFDDLT of PUCCH
E.pucchB
lankNum
5 FDD: CDMA LTE This parameter enables or disables CDMA-LTE CSS. If this 0: Close, 0: Close
PhyChan CSS Switch parameter is set to “1: UL/DL Support CDMA LTE CSS”, 1: UL/DL Support
nelFDDLT LTE can use the overlapped frequency resources by the CDMA LTE CSS,
E.cDMAL CDMA system in both the uplink and downlink directions. 2: Only UL Support
TECSSSw If it is set to “2: Only UL Support CDMA LTE CSS”, LTE CDMA LTE CSS,
ch can use the overlapped frequency resources by the CDMA 3: Only DL Support
system only in the uplink direction. CDMA LTE CSS
If it is set to “3: Only DL Support CDMA LTE CSS”, LTE
can use the overlapped frequency resources by the CDMA
system only in downlink direction.
If it is set to “0: Close”, LTE cells can use only the
dedicated frequency resources.
6 FDD: UL Buffer This parameter is used to select uplink buffer mode when 0:BothSidesReuse, 0:BothSidesReuse
PhyChan Mode of CSS the MagicRadio co-spectrum scheduling buffer switch is 1:LowFreSideReuse,
nelFDDLT turned on. If it is configured as "BothSides Reuse", the 2:HighFreSideReuse
E.bufferC buffer of the uplink shared spectrum is bilaterally
SSModeU multiplexed; if it is configured as "LowFreSideReuse", the
l buffer of the uplink shared spectrum is multiplexed by low
frequency; if it is configured as "HighFreSideReuse", the
buffer of the uplink shared spectrum is multiplexed by
high frequency.
1 Configure Harmonic-Interference Avoidance Mode and Harmonic-Interference Coordination Switch,
FDD: Select [Managed Element -> eNodeB CU -> LTE -> E-UTRAN FDD Cell -> LTE FDD PUCH and PDCH],
set Harmonic-Interference Avoidance Mode and Harmonic-Interference Coordination Switch. Synchronize the data to eNodeB.
Figure 4-44 Configure Harmonic-Interference Avoidance Mode and Harmonic-Interference Coordination Switch
1 Configure PUCCH Blanking and Numbers of Blanked RB of PUCCH,
72 - 89
EN-DC Enhancement
set PUCCH Blanking and Numbers of Blanked RB of PUCCH. Synchronize the data to eNodeB.
Figure 4-45 Configure PUCCH Blanking and Numbers of Blanked RB of PUCCH
1 Configure CDMA LTE CSS Switch and UL Buffer Mode of CSS,
set CDMA LTE CSS Switch and UL Buffer Mode of CSS. Synchronize the data to eNodeB.
Figure 4-46 Configure CDMA LTE CSS Switch and UL Buffer Mode of CSS
73 - 89
EN-DC Enhancement
4.3.2.2 Intermodulation Interference Avoidance Function Activation
4.3.2.2.1 LTE Parameters
Table 4-20 Related Parameters of the Intermodulation Interference Avoidance Function
NO Paramete Parameter na Parameter explanation Range value Default valu

r me e
1 FDD: The Switch of The parameter indicates the switch of SRS Configuration. 0:Close, 0:Close
PhyChan SRS 1:Open
nelFDDLT Configuration
E.srsEna
ble
2 FDD: Inter- This parameter enables or disables intermodulation interference. If it is 0: Close 0: Close
#PhyCha modulation set to 0, it indicates that intermodulation interference is disabled. If it is Inter- Inter-
nnelFDDL Interference set to 1, it indicates that intermodulation interference is enabled. modulation modulation
TE.iMDS Switch interference interference
witch avoidance, avoidance
1: Open
Inter-
modulation
interference
avoidance
3 FDD: Percentage of This parameter sets the percentage of the SRS subframe resources 0:0, 0:0
PhyChan Reserved SRS reserved by the LTE network. A larger parameter value indicates that 1:25,
nelFDDLT Time Domain less SRS resources can be configured on the LTE network and more SRS 2:50,
E.srsRese Resources resources can be configured on the SRS subframes reserved by the LTE 3:75,
rveRatio network for the NR network. 4:100
4.3.2.2.2 LTE parameter configuration
1 Configure The Switch of SRS Configuration,
74 - 89
EN-DC Enhancement
set The Switch of SRS Configuration. Synchronize the data to eNodeB.

Figure 4-47 Configure The Switch of SRS Configuration
1 Configure Inter-modulation Interference Switch,
set Inter-modulation Interference Switch. Synchronize the data to eNodeB.
Figure 4-48 Configure Inter-modulation Interference Switch
1 Configure Percentage of Reserved SRS Time Domain Resources,
75 - 89
EN-DC Enhancement
set Percentage of Reserved SRS Time Domain Resources. Synchronize the data to eNodeB.
Figure 4-49 Configure Percentage of Reserved SRS Time Domain Resources
4.3.3 Functional Deactivation
4.3.3.1 Harmonic Interference Avoidance Function Deactivation
1. Configure Harmonic-Interference Avoidance Mode,

set Harmonic-Interference Avoidance Mode. Synchronize the data to eNodeB.
Figure 4-50 Configure Harmonic-Interference Avoidance Mode
76 - 89
EN-DC Enhancement
2. Configure PUCCH Blanking,

set PUCCH Blanking. Synchronize the data to eNodeB.
Figure 4-51 Configure PUCCH Blanking
3. Configure CDMA LTE CSS Switch,

set CDMA LTE CSS Switch. Synchronize the data to eNodeB.
Figure 4-52 Configure CDMA LTE CSS Switch
4.3.3.2 Intermodulation Interference Avoidance Function Deactivation
77 - 89
EN-DC Enhancement
1. Configure The Switch of SRS Configuration,

set The Switch of SRS Configuration. Synchronize the data to eNodeB.
Figure 4-53 Configure The Switch of SRS Configuration
2. Configure Inter-modulation Interference Switch,

set Inter-modulation Interference Switch. Synchronize the data to eNodeB.
Figure 4-54 Configure Inter-modulation Interference Switch
4.3.4 Network Monitoring
78 - 89
EN-DC Enhancement
None.
4.3.5.1 Gain Analysis
None.
4.3.5.2 Impact Analysis
If the function of Harmonic Interference Avoidance is enabled, the impacts are as follows:
■ Since the system bandwidth is divided into three segments, the maximum number of RBs allocated to LTE UE is reduced;
■ Note that the location of LTE PUCCH changes. If the PUCCH location of neighbor cell is different, the PUSCH of neighbor cell will cause
interference on the PUCCH of this cell, and the PUCCH Blanking of this cell will cause interference on the PUCCH of neighbor cell.
5 Related KPIs, Counters and Alarms
5.1 Counters
Table 5-1 Related counters of SN addition/deletion/modification/release
SN Counter ID Counter name
1 C374420000 Number of Times that the MeNB Adds an SgNB Successfully
2 C374420001 Number of Times that the MeNB Fails to Add an SgNB due to SgNB Response Timeout
3 C374420002 Number of Times that the MeNB Fails to Add an SgNB due to SgNB Rejection
4 C374420003 Number of Times that the MeNB Fails to Add an SgNB due to Reconfiguration Timeout
5 C374420004 Number of Times that the MeNB Fails to Add an SgNB due to E-RAB Modification Failure
6 C374420005 Number of Times that the MeNB Fails to Add an SgNB due to Other Causes
7 C374420006 Number of SgNB Releases Initiated by SgNB
8 C374420007 Number of Times that the MeNB Adds an SgNB Request
9 C374420008 Number of SgNB Releases Initiated by MeNB due to SCG Failure
10 C374420009 Number of Times that the MeNB Initiates an SgNB Release due to UE Release Initiated by MME
11 C374420010 Number of Times that the MeNB Initiates an SgNB Release due to UE AbNormal Release Initiated by eNB
12 C374420011 Number of SgNB Releases Initiated by MeNB due to Other Causes
13 C374420012 Number of Times that the MeNB Initiates an SgNB Release due to UE Normal Release Initiated by eNB
14 C374420013 Number of Times that the MeNB Initiates an SgNB Release due to E-RAB Release Initiated by MME
15 C374420014 Number of Times that the MeNB Initiates an SgNB Release due to E-RAB Release Initiated by eNB
16 C374420015 Number of Times that the MeNB Initiates an SgNB Release due to Handover Success
17 C374420016 Number of Times that the MeNB Initiates an SgNB Release due to Reestablish Success
18 C374420017 Number of SgNB Modify Requests Initiated by the SgNB
19 C374420018 Number of SgNB Modify Requests Initiated by the MeNB
20 C374420019 Number of SgNB Modify Requests Successfully Initiated by the SgNB
21 C374420020 Number of SgNB Modify Requests Successfully Initiated by the MeNB
22 C374420039 Number of Times that the MeNB Fails to Add an SgNB Due to Handover Failure
23 C374420040 Maximum Duration of SgNB Addition
24 C374420041 Total Duration of SgNB Addition
79 - 89
EN-DC Enhancement
25 C374420042 Maximum Duration of SgNB Addition in Non-Handover Scenarios
26 C374420043 Total Duration of SgNB Addition in Non-Handover Scenarios
27 C374420046 Number of SgNB Change Procedures Initiated by the SgNB
28 C374420047 Number of Successful Preparations for SgNB Change Procedures Initiated by the SgNB
29 C374420048 Number of SgNB Change Procedures Successfully Initiated by the SgNB
30 C374420049 Number of Normal SgNB Releases Initiated by the SgNB
31 C374420055 Number of Attempts to Release an SgNB Initiated by the MeNB
32 C374420056 Number of Attempts to Release an SgNB Initiated by the SgNB
33 C374440038 Number of Attempted RRC Connection Reconfig for NSA UEs
34 C374440039 Number of Successful RRC Connection Reconfig for NSA UEs
35 C374420072 Number of SgNB Releases Initiated by the MeNB Due to Redirection
36 C374420073 Number of SgNB Releases Initiated by the MeNB Due to CSFB
37 C374420074 Number of SgNB Releases Initiated by the MeNB Due to UserInactive
38 C374420075 Number of SgNB Releases Initiated by the MeNB Due to the eNodeB Detecting a UE Not Online
39 C374420076 Number of SgNB Releases Initiated by the MeNB Due to VoLTE Quality Assurance
40 C374420077 Number of SgNB Releases Initiated by the MeNB Due to Handover Failure
41 C374420078 Number of SgNB Releases Initiated by the MeNB Due to Reestablishment Failure
42 C374420079 Number of SgNB Releases Initiated by the MeNB Due to Inter-eNodeB Reestablishment Failure
43 C374420080 Number of SgNB Releases Initiated by the MeNB Due to the Cell Being Blocked or Reset
44 C374420081 Number of SgNB Releases Initiated by the MeNB Due to Radio Link Failure
45 C374420082 Number of SgNB Releases Initiated by the MeNB Due to S1 Link Fault
46 C374420083 Number of SgNB Releases Initiated by the MeNB Due to eNodeB Overload Control or Congestion
47 C373760023 Number of Times that the MeNB Initiates an SgNB Release Request due to User Inactive
48 C374420086 Number of Times that the MeNB Requests to Add an SgNB Blindly
49 C374420087 Number of Times that the MeNB Blindly Adds an SgNB Successfully
Table 5-2 Related counters of NSA user plane
1 C374360071 Maximum Number of Activated NR UEs
2 C374360072 Average Number of Activated NR UEs
3 C374360073 Maximum Number of DL Activated NR UEs on the User Plane
4 C374360074 Maximum Number of UL Activated NR UEs on the User Plane
5 C374360075 Average Number of DL Activated NR UEs on the User Plane
6 C374360076 Average Number of UL Activated NR UEs on the User Plane
7 C374360077 Maximum Number of Activated NR E-RABs
8 C374360078 Average Number of Activated NR E-RABs
9 C374360079 Average Number of DL Activated NR E-RABs
10 C374360080 Average Number of UL Activated NR E-RABs
11 C374360081 Maximum Number of DL Activated NR E-RABs
12 C374360082 Maximum Number of UL Activated NR E-RABs
13 C374360000 DL Aggregated Volume (High) of NR UEs Through Uu
80 - 89
EN-DC Enhancement
14 C374360001 DL Aggregated Volume (Low) of NR UEs Through Uu
15 C374360002 UL Aggregated Volume (High) of NR UEs
16 C374360003 UL Aggregated Volume (Low) of NR UEs
17 C374360004 UL Aggregated IP Throughput (High) of NR UEs
18 C374360005 UL Aggregated IP Throughput (Low) of NR UEs
19 C374360006 DL Aggregated IP Throughput (High) of NR UEs
20 C374360007 DL Aggregated IP Throughput (Low) of NR UEs
21 C374360008 Time for UL Aggregated IP Throughput of NR UEs
22 C374360009 Time for DL Aggregated IP Throughput of NR UEs
23 C374360010 Number of Lost UL PDCP SDUs of NR UEs
24 C374360011 Number of Lost DL PDCP SDUs of NR UEs
25 C374360012 Number of Discarded DL PDCP SDUs of NR UEs
26 C374360013 Total Number of UL PDCP SDUs of NR UEs
27 C374360014 Total Number of DL PDCP SDUs of NR UEs
28 C374360015 Number of DL PDCP SDUs With Successful HARQ Responses Received by NR UEs
29 C374360016 DL PDCP SDU Delay of NR UEs
30 C374420027 Maximum Number of Activated Dual-Connectivity UEs
31 C374420028 Average Number of Activated Dual-Connectivity UEs
32 C374420029 Maximum Number of UL Activated Dual-Connectivity UEs
33 C374420030 Maximum Number of DL Activated Dual-Connectivity UEs
34 C374420031 Average Number of UL Activated Dual-Connectivity UEs
35 C374420032 Average Number of DL Activated Dual-Connectivity UEs
36 C374360085 Number of DL RLC SDUs Transmitted Successfully on the Split Bearers of NR UEs
37 C374360086 DL RLC SDU Delay on the Split Bearers of NR UEs
38 C374360087 DL RLC SDU Feedback Delay on the Split Bearers of NR UEs
39 C374360017 DL Aggregated IP Throughput (High) of NR UEs (QCI = 1)
40 C374360018 DL Aggregated IP Throughput (Low) of NR UEs (QCI = 1)
41 C374360019 Time for DL Aggregated IP Throughput of NR UEs (QCI = 1)
81 - 89
EN-DC Enhancement
66 C374360044 UL Aggregated IP Throughput (High) of NR UEs (QCI = 1)
67 C374360045 UL Aggregated IP Throughput (Low) of NR UEs (QCI = 1)
68 C374360046 Time for UL Aggregated IP Throughput of NR UEs (QCI = 1)
93 C374360088 Time for DL Data Transmission of NR UEs
94 C374360089 Time for UL Data Transmission of NR UEs
82 - 89
EN-DC Enhancement
95 C374480000 DL Data Volume (High) of RLC SDUs with MCG E-RABs Transmitted over Uu in a Cell
96 C374480001 DL Data Volume (Low) of RLC SDUs with MCG E-RABs Transmitted over Uu in a Cell
97 C374480002 DL Data Volume (High) of RLC SDUs with SCG Split E-RABs Transmitted over Uu in a Cell
98 C374480003 DL Data Volume (Low) of RLC SDUs with SCG Split E-RABs Transmitted over Uu in a Cell
99 C374480004 UL Data Volume (High) of RLC SDUs with MCG E-RABs in a Cell
100 C374480005 UL Data Volume (Low) of RLC SDUs with MCG E-RABs in a Cell
101 C374480006 UL Data Volume (High) of RLC SDUs with SCG Split E-RABs in a Cell
102 C374480007 UL Data Volume (Low) of RLC SDUs with SCG Split E-RABs in a Cell
103 C374480008 DL Aggregated RLC Throughput (High) on MCG E-RABs of NSA UEs
104 C374480009 DL Aggregated RLC Throughput (Low) on MCG E-RABs of NSA UEs
105 C374480010 DL Aggregated RLC Throughput (High) on SCG Split E-RABs of NSA UEs
106 C374480011 DL Aggregated RLC Throughput (Low) on SCG Split E-RABs of NSA UEs
107 C374480012 Time of DL RLC Throughput on MCG E-RABs of NSA UEs
108 C374480013 Time of DL RLC Throughput on SCG Split E-RABs of NSA UEs
109 C374480014 Time of DL RLC Data Transmission on MCG E-RABs of NSA UEs
110 C374480015 Time of DL RLC Data Transmission on SCG Split E-RABs of NSA UEs
111 C374480016 Number of Transmitted UL RLC SDUs on MCG E-RABs of NSA UEs
112 C374480017 Number of Transmitted DL RLC SDUs on MCG E-RABs of NSA UEs
113 C374480018 Number of Lost DL RLC SDUs on MCG E-RABs of NSA UEs
114 C374480019 Number of Transmitted UL RLC SDUs on SCG Split E-RABs of NSA UEs
115 C374480020 Number of Transmitted DL RLC SDUs on SCG Split E-RABs of NSA UEs
116 C374480021 Number of Lost DL RLC SDUs on SCG Split E-RABs of NSA UEs
Table 5-3 Related counters of NSA UE E-RAB
SN Counter No Counter name
1 C374350000 Number of NR User Initial E-RAB Successful Setup
2 C374350001 Number of NR User Additional E-RAB Successful Setup
3 C374350002 Number of NR User Initial E-RAB Setup Attempt
4 C374350003 Number of NR User Additional E-RAB Setup Attempt
5 C374350004 Number of NR User E-RAB Release by MME Normal Release
6 C374350005 Number of NR User E-RAB Release by Inter eNB Reestablish Failure
7 C374350006 Number of NR User E-RAB Release by MME due to Other Reason
8 C374350007 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to Overload Control
9 C374350008 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to Other Abnormal Reason
10 C374350009 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to Cell Congestion
11 C374350010 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to HO Fail
12 C374350011 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to Radio Link Failure
13 C374350012 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to Reestablish Fail
14 C374350013 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to UserInactive
15 C374350014 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to Shut Down or Reset Cell
16 C374350015 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to Redirection
83 - 89
EN-DC Enhancement
17 C374350016 Number of NR User E-RAB Release by ENB due to UE Off-line
18 C374350017 Number of NR User E-RAB Release due to RRC Resource Preemption
19 C374350018 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to CCO Cause
20 C374350019 Number of NR User E-RAB Release by ENB Through E-RAB Release Procedure due to S1 Link Error
21 C374440020 Number of SCG E-RABs Requested to Be Set Up
22 C374440021 Number of SCG E-RABs Set Up Successfully
23 C374440022 Number of SCG Split E-RABs Requested to Be Set Up
24 C374440023 Number of SCG Split E-RABs Set Up Successfully
25 C374440024 Number of SCG E-RABs Normally Released by the eNB
26 C374440025 Number of SCG E-RABs Abnormally Released by the eNB
27 C374440026 Number of SCG E-RABs Normally Released by the MME
28 C374440027 Number of SCG E-RABs Abnormally Released by the MME
29 C374440028 Number of SCG Split E-RABs Normally Released by the eNB
30 C374440029 Number of SCG Split E-RABs Abnormally Released by the eNB
31 C374440030 Number of SCG Split E-RABs Normally Released by the MME
32 C374440031 Number of SCG Split E-RABs Abnormally Released by the MME
33 C374440042 Number of Online SCG E-RABs
34 C374440043 Number of Online SCG Split E-RABs
35 C374440032 Number of SCG E-RABs Successfully Changing to MCG E-RABs
36 C374440033 Number of SCG SPLIT E-RABs Successfully Changing to MCG E-RABs
Table 5-4 Related counters of NSA UE statistics
1 C374350020 Maximum E-RAB Number of LTE User
2 C374350021 Maximum Number of LTE User
3 C374350022 Average Number of LTE User
4 C374350023 Average Number of MCG E-RABs of NR User
5 C374350024 Average Number of NR User
6 C374350025 Maximum Number of NR User
7 C374350085 Average Number of SCG E-RABs of an NR User
8 C374350086 Average Number of SCG Split E-RABs of an NR User
9 C374350087 Maximum Number of SCG E-RABs of NR UEs
10 C374350088 Maximum Number of MCG E-RABs of NR UEs
11 C374350089 Maximum Number of SCG Split E-RABs of NR UEs
12 C374350090 Maximum Number of E-RABs of NR UEs
13 C374440034 Average Number of NSA Users with 5G Subscriptions
14 C374440035 Maximum Number of NSA Users with 5G Subscriptions
15 C374420021 Average Number of RRC Connections in Dual-Connectivity
16 C374420022 Maximum Number of RRC Connections in Dual-Connectivity
17 C374420084 Average number of RRC connections in Dual-connectivity with VoLTE service
18 C374440048 Average Number of RRC Connections of NSA User with VoLTE service
84 - 89
EN-DC Enhancement
Table 5-5 NSA Related counters of gNB
1 C600000034 Maximum number of NSA UEs with RRC connections
2 C600000035 Average number of NSA UEs with RRC connections
3 C600600000 Number of successful SN addition attempts
4 C600600001 Number of failed SN addition attempts due to radio resources unavailable
5 C600600002 Number of failed SN addition attempts due to X2 interface reconfiguration timeout
6 C600600003 Number of failed SN addition attempts due to other reasons
7 C600600004 Number of successful SRB3 addition attempts
8 C600600005 Number of failed SRB3 addition attempts due to radio resources unavailable
9 C600600006 Number of failed SRB3 addition attempts due to X2 interface reconfiguration timeout
10 C600600007 Number of failed SRB3 addition attempts due to other reasons
11 C600600008 Time of SN addition total delay
12 C600600009 Number of SN change requests
13 C600600010 Number of SN change confirmations
14 C600600011 Number of times that an SN is released by the MeNB due to Uu interface reasons
15 C600600012 Number of times that an SN is released by the MeNB due to user inactivity
16 C600600013 Number of times that an SN is released by the MeNB due to other normal reasons
17 C600600014 Number of times that an SN is released by the SN due to measurement
18 C600600015 Number of times that an SN is released by the SN due to other causes
19 C600600016 Number of successful PSCell changes intra SN trigged by measurement reports
20 C600600017 Number of failed PSCell changes intra SN due to F1 context setup fail
21 C600600018 Number of failed PSCell changes intra SN due to reconfiguration complete timeout
22 C600600019 Number of failed PSCell changes intra SN due to other reasons
23 C600600020 Number of successful SN modify
24 C600600021 Number of failed SN modify due to F1 context modify fail
25 C600600022 Number of failed SN modify due to X2 reconfiguration timeout
26 C600600023 Number of failed SN modify due to other reasons
27 C600600038 Number of times that an SN is released by the SN due to radion link Fail
28 C600600046 Number of E-RAB addition attempts
29 C600600047 Number of times that an SN is released by the MeNB due to radio reasons
30 C600600048 Number of times that an SN is released by the MeNB due to handover
31 C600600050 Number of times that an SN is released by the SN due to rrm
32 C600600053 Number of times that an SN is released by the MeNB due to other abnormal causes
33 C600600054 Number of SN release requests triggered by the SN due to enhancement of user inactivity reliability
34 C600690000 Number of SN add requests
35 C600690001 Number of PSCell change requests intra SN
36 C600690004 Number of times that an SN is added successfully
37 C600690005 Number of times that an SN fails to be added due to radio resources unavailable
38 C600690006 Number of times that an SN fails to be added due to X2 interface reconfiguration timeout
85 - 89
EN-DC Enhancement
39 C600690007 Number of times that an SN fails to be added due to other causes
40 C600690008 Total SN addition delay
41 C600690009 Number of inter-frequency PS cell change requests triggered by the SN
42 C600690010 Number of successful inter-frequency PS cell changes triggered by the SN
43 C600690011 Number of inter-frequency SN change requests
44 C600690015 Number of times that an SN modification triggered by the MeNB succeeds
45 C600690016 Number of times that an SN modification triggered by the MeNB fails due to F1 context modification failure
46 C600690017 Number of times that an SN modification triggered by the MeNB fails due to X2 interface reconfiguration timeout
47 C600690018 Number of times that an SN modification triggered by the MeNB fails due to other causes
48 C600690019 Number of times that the MeNB triggers an SN release due to an air interface failure
49 C600690020 Number of times that the MeNB triggers an SN release due to user inactivity
50 C600690021 Number of times that the MeNB triggers an SN release due to other normal causes
51 C600690022 Number of times that the MeNB triggers an SN release due to normal radio-side reasons
52 C600690023 Number of times that the MeNB triggers an SN release due to MeNB handover
53 C600690024 Number of times that the MeNB triggers an SN release due to other abnormal causes
54 C600690025 Number of times that the SN triggers an SN release due to measurement
55 C600690026 Number of times that the SN triggers an SN release due to other causes
56 C600690027 Number of times that the SN triggers an SN release due to an RLF
57 C600690028 Number of times that the SN triggers an SN release for service load balancing
58 C600690029 Number of times that an E-RAB is added successfully
59 C600690030 Number of times that an E-RAB fails to be added due to radio resources unavailable
60 C600690031 Number of times that an E-RAB fails to be added due to X2 interface reconfiguration timeout
61 C600690032 Number of times that an E-RAB fails to be added due to other causes
62 C600690033 Number of times that an E-RAB is released by the MeNB due to normal radio-side reasons
63 C600690034 Number of times that an E-RAB is released by the MeNB due to user inactivity
64 C600690035 Number of times that an E-RAB is released by the MeNB due to handover
65 C600690036 Number of times that an E-RAB is released by the MeNB due to other normal causes
66 C600690037 Number of times that an E-RAB is released by the MeNB due to other abnormal causes
67 C600690038 Number of times that an E-RAB is released by the MeNB due to an air interface failure
68 C600690039 Number of times that an E-RAB is released by the SN due to measurement
69 C600690040 Number of times that an E-RAB is released by the SN due to an RLF
70 C600690041 Number of times that an E-RAB is released by the SN due to other causes
71 C600690042 Number of times that an E-RAB is released by the SN for service load balancing
72 C600690043 Number of times that an SN modification request is triggered by the SN
73 C600690044 Number of times that an SN modification request triggered by the SN succeeds
74 C600690045 Number of SN release requests triggered by the SN due to enhancement of user inactivity reliability
75 C600690046 Number of RAB releases triggered due to enhancement of user inactivity reliability
76 C600850020 Average number of SCG DRBs in a cell
77 C600850021 Maximum number of SCG DRBs in a cell
78 C605030000 Number of SN addition attempts meet flexible configuration conditions
86 - 89
EN-DC Enhancement
79 C605030001 Number of successful SN addition attempts meet flexible configuration conditions
80 C605030002 Number of SN change requests meet flexible configuration conditions
81 C605030003 Number of SN change confirmations meet flexible configuration conditions
82 C605030004 Number of SN releases triggered by the MN in the flexibly configurable PLMN
83 C605030005 Number of normal SN releases triggered by the MN in the flexibly configurable PLMN
84 C605030006 Number of SN releases triggerd by the SN in the flexibly configurable PLMN
85 C605030007 Number of normal SN releases triggered by the SN in the flexibly configurable PLMN
86 C605030008 Maximum number of Nsa UEs meet flexible configuration conditions
87 C605030009 Average number of Nsa UEs meet flexible configuration conditions
88 C374440034 Average Number of NSA Users with 5G Subscriptions
89 C374440035 Maximum Number of NSA Users with 5G Subscriptions
90 C374420084 Average Number of Dual-Connectivity UEs with the VoLTE Service
91 C374440048 Average Number of NSA UEs with the VoLTE Service
92 C600690049 Number of inter-frequency PS cell change requests triggered by the SN
93 C600690050 Number of successful inter-frequency PS cell changes triggered by the SN
94 C600690051 Number of inter-frequency SN change requests
95 C600690052 Number of inter-frequency SN change confirmations
Table 5-6 NSA Anchor Attribute counters of LTE
SN Counter No Counter name
1 C374420071 NSA Anchor Cell Attribute
2 C373941030 NSA Anchor eNodeB Attribute
5.2 KPIs
Table 5-7 LTE NSA-Related KPIs
SN KPIs No KPIs name
1 P348912 Number of Times that the MeNB Adds an SgNB Failed
2 P348913 Number of the Normal SgNB Releases Initiated by MeNB
3 P348914 Number of the SgNB Releases Initiated by MeNB
4 P348915 Average E-RAB Number Of NR Users
5 P348916 NR Users E-RAB Setup Success Rate
6 P348917 NR Users E-RAB Abnormal Release rate
7 P348935 Average Duration of SgNB Addition
8 P348979 SCG E-RAB Abnormal Release Rate
9 P348980 SCG E-RAB Setup Success Rate
10 P348981 SCG Split E-RAB Abnormal Release Rate
11 P348982 SCG Split E-RAB Setup Success Rate
12 P348983 Number of Abnormal SgNB Releases Initiated by the SgNB
13 P341130 Proportion of NSA UEs in RRC Dual-Connectivity Status
14 P341132 SgNB Addition Success Rate
15 P341134 Number of Bytes of UL RLC SDUs on MCG E-RABs in a Cell
87 - 89
EN-DC Enhancement
16 P341135 Number of Bytes of UL RLC SDUs on SCG Split E-RABs in a Cell
17 P341136 Number of Bytes of DL RLC SDUs on MCG E-RABs in a Cell
18 P341137 Number of Bytes of DL RLC SDUs on SCG Split E-RABs in a Cell
19 P341142 SCG E-RAB Dropped-Call Rate
20 P341143 SCG Split E-RAB Dropped-Call Rate
21 P341150 Average Number of RRC Connections of NSA UEs in Dual-Connection Status (Excluding VoLTE Services) = Average
Number of RRC Connections in Dual-Connectivity - Average Number of Dual-Connectivity UEs with the VoLTE Service
22 P341151 Average Number of RRC Connections of NSA UEs (Excluding VoLTE Services) = Average Number of NR User - Average
Number of NSA UEs with the VoLTE Service
23 P341152 Number of Attempts to Add DRBs for an SgNB = Number of SCG E-RABs Requested to Be Set Up + Number of SCG
Split E-RABs Requested to Be Set Up
24 P341153 Number of Times that DRBs Are Added for an SgNB Successfully = Number of SCG E-RABs Set Up Successfully +
Number of SCG Split E-RABs Set Up Successfully
25 P341154 Number of DRB Releases of an SgNB = Number of SCG E-RABs Normally Released by the eNB + Number of SCG E-
RABs Abnormally Released by the eNB + Number of SCG E-RABs Normally Released by the MME + Number of SCG E-
RABs Abnormally Released by the MME + Number of SCG Split E-RABs Normally Released by the eNB + Number of
SCG Split E-RABs Abnormally Released by the eNB + Number of SCG Split E-RABs Normally Released by the MME +
Number of SCG Split E-RABs Abnormally Released by the MME
26 P341155 Number of Normal DRB Releases of an SgNB = Number of SCG E-RABs Normally Released by the eNB + Number of
SCG E-RABs Normally Released by the MME + Number of SCG Split E-RABs Normally Released by the eNB + Number
of SCG Split E-RABs Normally Released by the MME
5.3 Alarms
Table 5-8 LTE side EN-DC X2AP broken link related alarm description
SN Alarm Alarm name

code
1 198200015 ENDC X2 link is broken

Note: This alarm is reported when the SCTP referenced by EN-DC X2 has a broken link. This alarm is controlled by
Switch for Reporting EN-DC X2 Link Alarms. By default, the alarm is not reported.
2 198200017 PDCP Counter Check inconsistency

Note: This notification is reported when the data volume sent or received on the DRB is inconsistent between the
network side and the UE side. This alarm is controlled by Switch for Counter Check Reporting. By default, the alarm
is not reported.
Abbreviations
EN-DC E-UTRA-NR Dual Connectivity
E-UTRA Evolved Universal Terrestrial Radio Access
E-UTRAN Evolved Universal Terrestrial Radio Access Network
FDD Frequency Division Duplex
NAS Non-Access Stratum
NR New Radio
NSA Non-Standalone
PDCCH Physical Downlink Control Channel
PUCCH Physical Uplink Control Channel
TDD Time Division Duplex
6 Related Documents
1 3GPP TS 36.331.
2 LTE EN-DC Basic Function Feature Guide
88 - 89
EN-DC Enhancement
3 LTE EN-DC Mobility Management Feature Guide
89 - 89

En-DC Enhancement (UniRAN22.2) 1112791

Uploaded by

Copyright:

Available Formats

En-DC Enhancement (UniRAN22.2) 1112791

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

En-DC Enhancement (UniRAN22.2) 1112791

Uploaded by

Copyright:

Available Formats

EN-DC Enhancement

Product Version: NR22.2

Copyright ©2020 ZTE CORPORATION.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire

The ultimate right to interpret this product resides in ZTE CORPORATION.

1.1 Involve NEs

UE eNodeB MME S-GW gNodeB SGSN P-GW HSS

1.2 Change History

SN Section Technical Point Related Parameters

1 3.1.10 added counter Check. Add the alarm Add：

2 3.1.11 Added NSA inter-frequency PSCell Add:

Table 1-2 Other changes

SN Section Change Description

1 3.1.11 The description of the application scenarios of Counter Check is adjusted.

Flow control and data split is split from this document

Table 1-3 Parameter changes

Change Type Before change After change

1.3 Related Feature List and License Control

Table 1-4 LTE &5G Related Feature List

No 4G Feature No. 4G Feature List Name License C Chapter 5G Feature List

1 ZLF40-05-010 LTE 1CC+NR 1 band Downlink Dual NO 3.1.2 ZNR03-13-031

2 ZLF40-05-012 LTE 2CC+NR 1 band Downlink Dual NO 3.1.2 ZNR03-13-033

3 ZLF40-05-013 LTE 3CC+NR 1 band Downlink Dual NO 3.1.2 ZNR03-13-034

4 ZLF40-05-014 LTE 4CC+NR 1 band Downlink Dual NO 3.1.2 ZNR03-13-035

5 ZLF40-05-015 Inter-site EUTRAN-NR Downlink Dual NO 3.1.3 N/A

7 ZLF40-06-014 Flexible SN Configuration Strategy YES 3.1.4.1 N/A

8 ZLF40-04-010 Multi Factor Joint awared SN Handling YES 3.1.8 N/A

11 ZLF40-08-013 Interference Suppressed Under No 3.3 ZNR03-20-011 Intermodulation and

1.4 Correlation with Other Feature

Table 1-5 Correlation with Other Feature

Feature ID Feature Name Required Feature Exclusive Fe Impacted Fe

ZLF40-05-015 Inter-site EUTRAN-NR Downlink Dual YES None None

ZLF40-05-016 LTE UL 1CC+NR UL 1 band Dual Connectivity YES None None

ZLF40-03-013 Inter-Frequency SN Change Procedure in NSA None None None

ZLF40-08-013 Interference Suppressed Under EUTRAN-NR Dual None None None

1.4.1 ZLF40-05 LTE CA+NR Dual Connectivity

■ ZLF34-00-015 Carrier Aggregation(Intra-Band, DL 2CC)

■ ZLF34-00-013 Carrier Aggregation (Inter-Band, DL 2CC)

■ ZLF34-00-017 Carrier Aggregation(DL 3CC)

■ ZLF34-00-055 Carrier Aggregation(DL 4CC of FDD)

■ ZLF40-01-010 EUTRAN-NR Dual Connectivity for Option3x

■ ZLF34-00-016 Carrier Aggregation(UL 2CC)

1.5 Technical Differences between FDD and TDD

Table 1-6 Technical differences between FDD and TDD

SN Technical Point FDD TDD Section

3.1 Part of Services

3.1.1 Technical Definitions

3.1.2 DC and CA Combination

1 LTE maximum 4CC + TDD NR 1CC,

2 LTE maximum 4CC + FDD NR 1CC,

3 LTE maximum 3CC + TDD NR 2CC,

4 LTE maximum 3CC + FDD NR 2CC,

5 LTE maximum 3CC + FDD NR 1CC(PSCell) + TDD NR 1CC.

Figure 3-1 DC and CA combination

■ Delay Start Timer for CA Anchoring Relative to EN-DC Anchoring expired.

■ Delay Start Timer for CA Anchoring Relative to SN Addition expired.

Table 3-1 NSA Anchor handover Related Parameter

NO Parameter Name FDD Parameter TDD Parameter

1 Delay Start Timer for CA Anchoring Relative to ControlPlaneTimerLTE.cA4ENDCAnch ControlPlaneTimerLTE.cA4ENDCAnch