Eden Net Lte NR Dual Connectivity Guide

EdenNet 21 FP 2103
LTE NR Dual Connectivity Activation Guide

DN1000025281
Issue: 1-1
LTE NR Dual Connectivity Activation Guide DN1000025281 1-1 Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.
This document is intended for use by Nokia' customers (“You”) only, and it may not be used except for the purposes defined in the agreement
between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced,
modified or transmitted in any form or means without the prior written permission of Nokia. If you have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You
are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using
it. Nokia welcome Your comments as part of the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity,
fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves
the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of
this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. But,
Nokia' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of
the software in the Product will be uninterrupted or error-free.
N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

WARR ANT Y OF AVA IL ABI LI T Y, AC CU RAC Y, R EL I A B I L IT Y, T I T L E , N O N - I N F R I N G E M E N T, M E R C H A N TA B I L I TY
OR F IT NE SS FO R A PA RT ICU LAR PU RPO SE, I S M A D E IN R E L AT I O N TO T H E C O N T E N T O F T H I S D O C U M E N T.
IN NO EVEN T WI L L NOK IA B E LI ABLE F OR AN Y DA M A G E S , I N C L U D I N G B U T N O T L I M I T E D TO S P E C I A L ,
D IRE CT, IN D IRECT, I NCI DE NTAL OR C ON SEQ UE N T IA L OR A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D TO LO SS
OF PRO F IT, REVE NU E, B US IN ESS IN T ER RU PT I ON , B U S I NE S S O P P O RT U N I T Y O R D ATA T H AT M AY A R I S E
FRO M T HE USE O F TH IS DO CU M EN T O R T HE IN F OR M AT IO N I N I T, E V E N I N T H E C A S E O F E R R O R S I N O R
OM IS SI O NS FRO M T HI S DOC UM EN T O R IT S CO NT E N T.
This document is Nokia’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the
prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright © 2021 Nokia. All rights reserved.
Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the
safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this
document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for
any additional information.
LTE NR Dual Connectivity Activation DN1000025281 1-1 Table of Contents
Guide
Contents
1 Summary of changes...................................................................................................................................... 4
2 Overview of LTE NR Dual Connectivity Activation module........................................................................ 7
3 LTE NR Dual Connectivity Activation functional description and guidelines........................................... 8

3.1 Operational modes of LTE NR Dual Connectivity Activation module....................................................... 8
3.1.1 Open loop mode............................................................................................................................... 8
3.1.2 Closed loop mode.............................................................................................................................8
4 LTE NR Dual Connectivity Activation algorithm.......................................................................................... 9
5 LTE NR Dual Connectivity Activation execution........................................................................................10

5.1 LTE NR Dual Connectivity Activation prerequisites................................................................................10
5.1.1 License details................................................................................................................................ 10
5.1.2 CM data.......................................................................................................................................... 10
5.2 Configuring and executing LTE NR Dual Connectivity Activation module.............................................. 10
6 LTE NR Dual Connectivity Activation configuration parameters............................................................. 14

6.1 LTE NR Dual Connectivity Activation GUI parameters...........................................................................14
6.2 LTE NR Dual Connectivity Activation INI parameters............................................................................ 16
6.2.1 Exclusion list in the INI configuration file....................................................................................... 39
6.2.2 Using User Defined Functions (UDFs) to determine parameter value........................................... 40
6.2.3 Global list in INI file........................................................................................................................ 40
6.2.4 Example of LTE NR Dual Connectivity Activation configuration file............................................... 40
6.3 Importing INI parameters........................................................................................................................ 44
7 Viewing LTE NR Dual Connectivity Activation report............................................................................... 46

7.1 LTE NR Dual Connectivity Activation reports......................................................................................... 46
8 Viewing LTE NR Dual Connectivity Activation events.............................................................................. 49

8.1 LTE NR Dual Connectivity Activation events..........................................................................................50
9 Monitoring LTE NR Dual Connectivity Activation......................................................................................51

9.1 LTE NR Dual Connectivity Activation impact on the network................................................................. 51
10 Appendix A: Description of INI parameter relationships........................................................................ 52
11 Appendix B: Sample python file with user defined functions................................................................ 57
12 Appendix C: Sample user defined management module file................................................................. 58
EdenNet 21 FP 2103 © 2021 Nokia 3

LTE NR Dual Connectivity Activation DN1000025281 1-1 Summary of changes
Guide
1 Summary of changes
Release Change description
EdenNet 21 FP 2103 Updated section:
• LTE NR Dual Connectivity Activation INI parameters is updated with the

following parameters:
– LNBTS_actEndcSpidFwd
– LNBTS_actUL256QamForEnDc
– LNBTS_actUeTrigEnDcTakeBack
– LNBTS_actMfbiNr
– LNBTS_actVoLteNoEnDcDrop
EdenNet 21 No change.
EdenNet 20 FP 2011 Updated sections:
• Table 5: LTE NR Dual Connectivity Activation INI parameters is updated

with the following parameters:
– LNBTS/NRDCDPR_mrWaitTimer
– LNCEL_maxNrIfFreqs
– LNBTS_actEndcDropMonitor
– LNBTS_endcSchedWeightBoostDl
– LNBTS_endcSchedWeightBoostUl
– LNBTS_actB1ExtMeasNR
– LNBTS/NRDCDPR_dynTriggerLteNrDcConfList.actB1NrBeamMeas
– LNBTS_actEnDcLteDlMimoOptBcSel
– LNBTS_actULCaForEnDc
– LNBTS_actEnDcLteDlTputBcSel
• Example of LTE NR Dual Connectivity Activation configuration file
• LTE NR Dual Connectivity Activation INI parameterssection is updated
by providing additional details on the ENDC attributes in a excel file that
can be downloaded to your system.
Deleted section:
• LTE NR Dual Connectivity interactions
EdenNet 20 FP 2010 Added sections:
• Using User Defined Functions (UDFs) to determine parameter value

• Global list in INI file
• Appendix B: Sample python file with user defined functions

Guide
• Appendix C: Sample user defined management module file
Updated sections:
• Table 5: LTE NR Dual Connectivity Activation INI parameters is updated

with the following parameter:
– qciTab5arpEnDcMask
qciTab6arpEnDcMask
qciTab7arpEnDcMask
qciTab8arpEnDcMask
qciTab9arpEnDcMask
qciTab69arpEnDcMask
qciTab70arpEnDcMask
EdenNet 20 FP 2009 Updated sections:
• LTE NR Dual Connectivity Activation GUI parameters - The Activate

Dynamic Trigger for Dual connectivity parameter is re-
moved and the corresponding parameter LNBTS.actDynTrigLteNr-
DualConnectivity value can be set in the INI configuration file.
• LTE NR Dual Connectivity Activation INI parameters - For LNBTS.
actLteNrDualConnectivity parameter, the following note is re-
moved. The value for this parameter in now set via the INI file.
Note: The module enables actLteNrDualConnectivity

flag by default.
EdenNet 20 FP 2008 Updated section:
• LTE NR Dual Connectivity Activation INI parameters section is updated

with the following parameters:
– LNBTS. actPeriodicB1NR
– LNBTS.nrRestrictionOverride
– NRDCDPR.retryTimerB1NR
– NRDCDPR. supervisionTimerB1NR
EdenNet 20 FP 2007 No change.
EdenNet 20 No change.
EdenNet 19A FP 2004 Added section:

Guide
• Exclusion list in the INI configuration file
Updated sections:
• LTE NR Dual Connectivity Activation INI parameters is updated with

LTE19B parameter changes
• Appendix A: Description of INI parameter relationships
EdenNet 19A FP 2003 No change
EdenNet 19A FP 2002 No change.
EdenNet 19A FP 1912 Updated sections:
• LTE NR Dual Connectivity Activation INI parameters

• LTE NR Dual Connectivity Activation algorithm
EdenNet 19A This document provides information about the LTE NR Dual Connectivi-
ty Activation (EN-DC) module which configures the LTE parameters that
are required for eUTRA-New Radio Dual Connectivity in Non Stand Alone
(NSA) configurations.
Table 1: Summary of changes

LTE NR Dual Connectivity Activation DN1000025281 1-1 Overview of LTE NR Dual Connectivity
Guide Activation module
2 Overview of LTE NR Dual Connectivity Activation

module
The LTE NR Dual Connectivity Activation (EN-DC) module configures the LTE parameters which are
required for eUTRA-New Radio Dual Connectivity in Non Stand Alone (NSA) configurations. All the
eUTRA-New Radio Dual Connectivity attributes are static and can be configured prior to:
• 5G deployment in the NSA option

• Establishing the LTE cell to NR cell relation
The LTE NR Dual Connectivity Activation module activates the dual connectivity feature on LTE BTS
and configures all the required eUTRA-New Radio Dual Connectivity attributes.
Note: The LTE NR Dual Connectivity Activation module supports Network Element (NE) ver-
sions of LTE 18A and above.
Table 2: Supported vendor and technology lists the supported vendor and technology for the LTE NR
Dual Connectivity Activation module.
Vendor Technology
Nokia LTE
Table 2: Supported vendor and technology

LTE NR Dual Connectivity Activation DN1000025281 1-1 LTE NR Dual Connectivity Activation
Guide functional description and guidelines
3 LTE NR Dual Connectivity Activation functional

description and guidelines
The LTE NR Dual Connectivity Activation module must be executed in the following use cases:
• Deployment of a new eNodeB or LTE cell.

• Activation of eUTRA-New Radio Dual Connectivity on the existing LTE cell.
• Reconfiguration of eUTRA-New Radio Dual Connectivity parameters on the LTE cells where eU-
TRA-New Radio Dual Connectivity attributes are already configured.
The values for the eUTRA-New Radio Dual Connectivity configuration attributes must be provided in
an INI file. For more information, see the LTE NR Dual Connectivity Activation INI parameters. The INI
file can only have GUI values.
The module supports the following functionalities:
• Dynamic scopes
• Scheduling capability
• Open loop with plan generation
• Closed loop
• Exclusion of the cells defined in the SON exclusion list
• NAdC Cross OSS integration
3.1 Operational modes of LTE NR Dual Connectivity Activation module

The LTE NR Dual Connectivity Activation module supports the following operational modes:
• Open loop mode

• Closed loop mode
3.1.1 Open loop mode

In the open loop mode, the changes that the LTE NR Dual Connectivity Activation module performs
are not applied to the network. You can manually provision the changes to be pushed to network.
3.1.2 Closed loop mode

In the closed loop mode, changes are applied to the network. The LTE NR Dual Connectivity Activa-
tion module generates a plan file for the proposed changes to the parameters which need to be sent to
the OSS.

Guide algorithm
4 LTE NR Dual Connectivity Activation algorithm

This chapter describes the LTE NR Dual Connectivity Activation module algorithm. The LTE NR Dual
Connectivity Activation module configures the eUTRA-New Radio Dual Connectivity parameters on
the LTE network.
The LTE NR Dual Connectivity Activation module:
• Reads the values for the eUTRA-New Radio Dual Connectivity attributes from the INI file.
• Validates the values provided in the configuration file using the metadata.
• Stops the module in case of any validation violations.
• Reads the values from the OSS if eUTRA-New Radio Dual Connectivity attributes are already de-
fined.
• Detects the discrepancies between the INI file and OSS and overrides with the INI file value.
• Detects the missing parameters from the INI file and OSS.
• Reads default values for the missing parameters from the metadata and adds these parameters
and values to the config.ini dictionary.
• Stops the module in case no default values are available for the missing parameters.
• Verifies parameter relationship rules for each parameter that is modified.
• Generates reports.
• Verifies the provisioning status and updates the module report file when the LTE NR Dual Connec-
tivity Activation module is run in closed loop, and the required eUTRA-New Radio Dual Connectivi-
ty parameters are pushed to the OSS.
• The module rejects the complete changes for a LNBTS in case of any validation or dependency
failures.

Guide execution
5 LTE NR Dual Connectivity Activation execution

This chapter describes how to access the LTE NR Dual Connectivity Activation module, select scope,
configure GUI and INI parameters, and schedule module execution.
5.1 LTE NR Dual Connectivity Activation prerequisites

To execute the LTE NR Dual Connectivity Activation module, the following prerequisites must be met:
• Google Chrome or Mozilla Firefox Web browser must be installed on your computer.
• LTE NR Dual Connectivity Activation module license must be activated. For more information, see
License details.
• LTE NR Dual Connectivity Activation module must be imported and integrated with the respective
Element Management System (EMS) or Network Management System (NMS).
• The CM data must be available. For more information, see CM data.
• Import and activate the required configuration files. For more details, see Configuring a module
section in the EdenNet User and Administration Guide.
5.1.1 License details

Table 3: EdenNet Licenses lists the license required to access the LTE NR Dual Connectivity Activa-
tion module.
Licensed feature Licensed feature compo-

LK item code LK item object name
component code nent name
ENSW0040CLK 5G Dual Connectivity Opti- 0000054308 5G Dual Connectivity Opti-

mization CLK mization
Table 3: EdenNet Licenses
5.1.2 CM data
For details about the Configuration Management (CM) of the LTE NR Dual Connectivity Activation
module, see EdenNet module specific data for Nokia document.
5.2 Configuring and executing LTE NR Dual Connectivity Activation

module
This section describes how to configure and execute the LTE NR Dual Connectivity Activation module.

Guide execution
Prerequisites
• All the prerequisites mentioned in the LTE NR Dual Connectivity Activation prerequisites section
must be met.
1. Log in to the EdenNet application by doing the following:

a) In the address field of your Internet browser, type the following URL for 2 VM, 5 VM, and
Cross-OSS:
https://<EdenNet GUI_SERVERS IP>
where <EdenNet GUI_SERVERS IP> is the IP address of the GUI server.
The EdenNet login page appears.

b) In the Username field, type the user name/username.
c) In the Password field, type the password.
d) Click Log In.
The EdenNet application opens displaying the SON Activity page.
2. Click the Configure tab.
The following module categories appear in the left pane:
• EdenNet modules: Lists the modules provided by Nokia.

• Adapted modules: Lists the modules developed by users.
• Helper modules: Lists the modules used for troubleshooting by Nokia support teams.
3. Click Helper modules → LTE_NR_Dual_Connectivity_Activation.
The Configure Targets page appears.
4. To select the LTE target cells for configuration, do one of the following:
• Based on the Topology Filter or Center Frequency Filter, select the target cells on the map.
Or
• Based on the Topology Filter or Center Frequency Filter, select all filtered items by clicking
the Select all Filtered Items icon.
Or
• Based on the following options, select the existing clusters or create a new cluster:
• From selected cells

• Based on rules
For more information about creating a new cluster, see the Cells Clusterssection in the
EdenNet User and Administration Guide.
Or
• Based on the cell ID search or selection tools from the map toolbar.

Guide execution
The target cells are selected on the map and are listed in the Selections pane.
Note: For more information about selecting cells, see the Selecting cells section in the
EdenNet User and Administration Guide document.
5. Click Next.
The Configure Parameters page appears.
6. In the Parameter Value column, define the values of the GUI configuration parameters. For the list
of GUI parameters, see LTE NR Dual Connectivity Activation GUI parameters.
Note: Click the Default Value icon, to revert to the default parameter value.
7. Click Next.
The Select Configuration File page appears.
8. In the Module Global Configuration category, select the required configuration file.
Note: In each category, you can select only one configuration file.
9. Verify the configuration in the right pane and click Next.
The Execution Type page appears.
10. To schedule the module execution, do one of the following:
• Execute Now: Select to execute or activate the module immediately.

• Execute Later: Select to execute or activate the module at a later time.
• Schedule Execution: Select to schedule the module for execution during a certain date and
time.
For more information, see the Configuring execution type section in the EdenNet User and Admin-
istration Guide.
11. Click Next.
The Confirm Execution page appears.
12. Verify the configuration summary and click Finish.

Guide execution
Expected outcome
The LTE NR Dual Connectivity Activation module is configured and executed as per the defined
schedule.
Note: You can monitor the LTE NR Dual Connectivity Activation module activities, status,
and so on. For more information, see Monitoring LTE NR Dual Connectivity Activation.

Guide configuration parameters
6 LTE NR Dual Connectivity Activation configuration

parameters
The configuration parameters required to execute the LTE NR Dual Connectivity Activation module are
as follows:
• Graphical user interface (GUI)

• INI file
6.1 LTE NR Dual Connectivity Activation GUI parameters

Table 4: LTE NR Dual Connectivity Activation GUI configuration parameters describes the parameters
configured in EdenNet GUI.
De-
Range (Min,
Parameter Description Step fault
Max)
value
Start hour of mainte- Indicates the start time for provisioning 0 - 23 hours N/A 0
nance window the changes to the network when the
module is run in the closed loop mode.
Changes are not provisioned before this

time.
End hour of mainte- Indicates the end time for provisioning the 0 - 23 hours N/A 0
nance window changes to the network when the module
is run in the closed loop mode.
Changes are not provisioned after this

time.
Dynamic trigger LTE- This parameter defines the cells of the default, lcrid N/A de-
NR DC configuration list LTE BTS for which dynamic measure- fault
ments in an LTE NR Dual Connectivity
scenario are enabled.
This parameter is required to configure

Dynamic trigger LTE NR Dual Connec-
tivity configuration list (MRBTS.LNBTS.
NRDCDPR.dynTriggerLteNrDcConfList).
The following values are supported:
• default: One structure item is created

and a value of -1 is configured for

De-
Range (Min,
Max)
value
dynTriggerLteNrDcConfList.
lcrid under MRBTS/LNBTS/
NRDCDPR. If the default value is
set to value -1, the dynamic trigger
based LTE NR Dual Connectivity for
all the cells of the BTS are enabled.
In this case, no dedicated cells can
be configured. The list is allowed to
include only one item.
• lcrid: The lcrid of the own LNCEL
instances that are part of the selected
scope cells will be configured for
dynTriggerLteNrDcConfList.
lcrid under MRBTS/LNBTS/
NRDCDPR. The module will
overwrite the list of LCRIDs present
on the OSS with the list of LCRIDs
detected by the module.
Carrier aggregation This parameter defines the cells of the default, lcrid N/A de-
LTE-NR DC cell list LTE BTS for which carrier aggregation in fault
an LTE NR Dual Connectivity scenario
is enabled. This parameter is required
to configure carrier aggregation LTE NR
DC cell list (MRBTS.LNBTS.NRDCDPR.
cAggrLteNrDcCellList).
The following values are supported:
• default - A value of -1 will be config-

ured for cAggrLteNrDcCellList
under MRBTS/LNBTS/NRDCDPR. If
the value is set to -1, carrier aggrega-
tion for all the cells of the BTS are en-
abled. In this case no dedicated cells
should be configured. The list is al-
lowed to include only one item.
• lcrid - The lcrid of the own LNCEL
instances which are part of the se-
lected scope cells will be configured
for cAggrLteNrDcCellList under

De-
Range (Min,
Max)
value
MRBTS/LNBTS/NRDCDPR. The mod-

ule will overwrite the list of LCRIDs
present on the OSS with the list of
LCRIDs detected by the module.
Email address (Option- Indicates the Email addresses to which N/A N/A email
al) the parameter consistency check reports ad-
must be sent. Separate the email address
dresses with a semi-colon or comma.
SON_Operation_Mode Set to Open Loop to run the module in • Open Loop N/A Open
open loop mode. Set to Closed Loop to • Closed loop
run the module in closed loop mode. In loop
Closed Loop mode, changes are auto-
matically pushed to the network without
user intervention. In Open Loop mode,
the module does not automatically push
parameter changes to the network. The
user has to manually provision plans to
push changes to the network.
Plan Name Tag Indicates the text is added to the names N/A N/A N/A
of all plans that are generated by this
module. If the target of the module is a
whole specific cluster (and name of this
cluster also matches requirements spec-
ified in Range column), then the clus-
ter name will also be added to the plan
name.
Table 4: LTE NR Dual Connectivity Activation GUI configuration parameters
6.2 LTE NR Dual Connectivity Activation INI parameters

The INI parameters must be set when the LTE NR Dual Connectivity Activation module is first config-
ured. The INI parameters must be changed only by users with appropriate privileges (for example, Ad-
ministrator, SON Module Manager).

The configuration file must contain the required eUTRA-New Radio Dual Connectivity CM attributes.
The list of required parameters have to be defined separately in the configuration file for each required
NE version. For more information, see CM data.
Note:
• To activate the LNBTS_actDynTrigLteNrDualConnectivity parameter,

the MRBTS.LNBTS.LNCEL.LNCEL_FDD.actAutoPucchAlloc parameter or
MRBTS.LNBTS.LNCEL.LNCEL_TDD.actAutoPucchAlloc parameter must be activat-
ed on the required LNCEL instances present under the LNBTS.
• To activate the LNBTS_actCAggrLteNrDualConnectivity parameter, the
MRBTS.LNBTS.actDLCAggr parameter must be set to true.
• The actPeriodicB1NR parameter value can be set to true if all the following conditions
are fulfilled:
– The actDynTrigLteNrDualConnectivity parameter value is set to true.

– At least one of the following conditions must be fulfilled:
• The supervisionTimerB1NR parameter value is set to a value other than 0 in

NRDCDPR.
• The retryTimerB1NR parameter must be set to a value other than 0 such that
the retryTimerB1NR - supervisionTimerB1NR is greater than one sec-
ond.
• To activate the actPeriodicB1NR parameter, the actDynTrigLteNrDualConnec-
tivity parameter must be set to true.
• From xL20B/FLF20B/TLF20B version and above, if the actLteNRDualConnectivity
parameter is set to true, then the nrRestrictionOverride parameter must be con-
figured.
• From xL20C/FLF20C/TLF20C version and above, if the actLteNrDualConnectivity
parameter is set to true, then the following conditions must be fulfilled, else the plan exe-
cution will fail.
– Configure the endcSchedWeightBoostDl parameter.

– Configure the endcSchedWeightBoostUl parameter.
– If the supportedCellTechnology parameter is set to TDD or mixed_FDD_TDD,
then the endcSchedWeightBoostDl parameter value must be equal to end-
cSchedWeightBoostUl parameter value.
• From xL20A/FLF20A/TLF20A version and above, all the supported feature flags can be
deactivated using the EN-DC module. Like the activation case, the module will check the
parameter dependencies while deactivating the feature flags. For example, the actDyn-
TrigLteNrDualConnectivity parameter can be set to false in the module INI file to
deactivate measurement based dynamic triggering of LTE NR Dual Connectivity.
• The User Defined Functions (UDFs) can be used in the INI file to determine the value of
the parameter.

• To activate the actEndcDropMonitor parameter, the actDynTrigLteNrDualCon-

nectivity parameter value must be set to true.
• If the actB1ExtMeasNR parameter value is set to true, then all the following conditions
must be fulfilled:
– The actDynTrigLteNrDualConnectivity parameter value must be set to true.

– In the NRDCDPR or at least one NRDCPR, the dynTriggerLteNrDc-
ConfList-actB1NrBeamMeas parameter value must be set to true for at least one
lcrId (including special value -1).
• The actEnDcLteDlMimoOptBcSel parameter value can be set to true if the following
condition is fulfilled:
– The actCAggrLteNrDualConnectivity parameter value must be set to

enhanced_CA_LTE_NR.
Table 5: LTE NR Dual Connectivity Activation INI parameters describes the parameters configured in
the INI file.
Supported
Parameter name Description Range Step Default LTE ver-
sion
LNBTS_actLteNr Indicates that this parame- • false N/A false Greater

DualConnectivity ter activates the LTE NR Dual • true than or
Connectivity (EN-DC) function- equal to
ality. It is mandatory for object LTE18A,
creation. FLF18A,
and
TLF18A.
LNBTS_actDynTrigLte Indicates that this parameter • false N/A false Greater

NrDualConnectivity activates the measurement • true than or
based dynamic triggering of equal to
LTE NR Dual Connectivity in LTE18A,
LTE BTS. It is mandatory for FLF18A,
object creation. and
TLF18A.
LNBTS_actCAggrLte Indicates that this parameter • disabled N/A disabled Greater

NrDualConnectivity activates carrier aggregation in • blind_ than or
LTE NR Dual Connectivity sce- CA equal to
narios in the LTE BTS. _LTE_ LTE18A,
NR FLF18A,
Note:
and
• If actCAggrL- TLF18A.
teNrDualCon-
nectivity has

Supported
sion
to be config- • en- But en-

ured, then en- hanced_ hanced_
sure to select CA CA
the required val- _LTE_
_LTE_NR
ue for Carri- NR
is support-
er aggrega-
ed from
tion LTE-NR
xL19B,
DC cell list
FLF19B,
GUI parameter.
and
• If actCAggrL- TLF19B
teNrDual- onwards.
Connectivi-
ty is set to en-
hanced_CA_
LTE_NR for
xL19B NEs, the
following para-
meters must be
configured in the
INI file:
– LNBTS/
NRDCD-
PR_dyn-
TriggerL-
teNrDc-
ConfList.
method
must be set
to coverage-
AndBuffer-
Based . This
is set for all
the lcrIds,
which are
part of dyn-
TriggerL-
teNrDc-
ConfList.

Supported
sion
– LNBTS/
NRDCDPR_
allowed-
BcSelect-
Method
LNBTS_ Indicates that this parameter N/A N/A 18 bit Valid from
pdcpProf1001snSizeDl configures the size of the SN LTE18A,
field in the PDCP header for FLF18A,
DL. It is only used during bear- and
er setup and is not allowed to TLF18A.
modify the PDCP SN size, for
example, at handover.
LNBTS_ Indicates that this parameter N/A N/A 18 bit Valid from
pdcpProf1001snSizeUl configures the size of the SN LTE18A,
field in the PDCP header for FLF18A,
UL. and
TLF18A.
It is only used during bearer
setup and is not allowed to
modify the PDCP SN size, for
example, at handover.
LNBTS_pdcpProf1001 Indicates that this parameter • 00 - no N/A • eNB Valid from

determines whether a PDCP Status Sta- LTE18A,
statusRepReq
status report is sent from PDCP Report tus FLF18A,
receiver to PDCP transmitter. • 01 - Re- and
The PDCP status report is sent eNB port: TLF18A.

from eNB to UE (eNB PDCP Status OFF
Status Report) or from User Report • UE
Equipment (UE) to eNB (UE Sta-
PDCP Status Report). tus
Re-
port:
OFF
LNBTS_ Specifies the parameter discard • 10ms N/A 300ms Valid from
pdcpProf1001tDiscard timer of [36.331]. • 20ms LTE18A,
FLF18A,
It indicates that the delay be- • 30ms
fore a PDCP PDU along with • 40ms

Supported
sion
the corresponding PDCP SDU • 50ms and

is discarded from the buffer. • 60ms TLF18A.
This timer will be set in a way • 75ms
that the packet delay defined by • 100ms
the QCI characteristics is kept.
• 150ms
The timer can be disabled by
• 200ms
setting the parameter to infinity.
• 250ms
• 300ms
• 500ms
• 750ms
• 1500ms
• infinity
LNBTS_ The parameter specifies • disabled N/A disabled Valid from

qciTab5lteNrDual whether or not the QCI is eligi- • EN-DC LTE18A,
ConnectSupport ble for LTE NR Dual Connectiv- FLF18A,
ity (EN-DC). and
LNBTS_ TLF18A.
If the parameter is configured
qciTab6lteNrDual qciTab5,
as EN-DC, the QCI definition is
ConnectSupport qciTab69,
eligible for eUTRA-New Radio
LNBTS_ and qc-
Dual Connectivity.
qciTab7lteNrDual iTab70 are
ConnectSupport valid from
xL19B,
LNBTS_ FLF19B,
qciTab8lteNrDual and
ConnectSupport TLF19B
LNBTS_ onwards
qciTab9lteNrDual only.
ConnectSupport
LNBTS_
qciTab69lteNrDual
ConnectSupport

Supported
sion
LNBTS_
qciTab70lteNrDual
ConnectSupport
LNBTS_ The parameter specifies the 1 to 15 N/A 1 Valid from

qciTab5startArpEnDc starting ARP value for the LTE18A,
range of ARP values for which FLF18A,
LNBTS_
the QCI is eligible for LTE NR and
qciTab6startArpEnDc
Dual Connectivity (EN-DC). TLF18A.
LNBTS_ qciTab5,
qciTab7startArpEnDc qciTab69,
and qc-
LNBTS_
iTab70 are
qciTab8startArpEnDc
valid from
LNBTS_ xL19B,
qciTab9startArpEnDc FLF19B,
and
LNBTS_
TLF19B
qciTab69startArpEnDc
onwards
LNBTS_ only.
qciTab70startArpEnDc
LNBTS_ The parameter specifies the 1 to 15 N/A 15 Valid from

qciTab5stopArpEnDc stop ARP value for the range of LTE18A,
ARP values for which the QCI FLF18A,
LNBTS_
is eligible for LTE NR Dual Con- and
qciTab6stopArpEnDc
nectivity (EN-DC). TLF18A.
LNBTS_ qciTab5,
qciTab7stopArpEnDc qciTab69,
and qc-
LNBTS_
iTab70 are
qciTab8stopArpEnDc
valid from
LNBTS_ xL19B,
qciTab9stopArpEnDc FLF19B,
and
LNBTS_
TLF19B
qciTab69stopArpEnDc
onwards
LNBTS_ only.
qciTab70stopArpEnDc

Supported
sion
LNBTS/NRDCDPR Indicates the NR Dual Connec- N/A N/A N/A Valid from
tivity default profile. LTE18A,
FLF18A,
and
TLF18A.
LNBTS/NRDCDPR_dl- Indicates the trigger condition • 1 db N/A 3 db Valid from

PathlossChg for power headroom submis- • 3 db LTE18A,
sion due to path loss change FLF18A,
• 6 db
for LTE NR Dual Connectivity and
• infinite
(EN-DC). TLF18A.
LNBTS/NRDCD- Indicates the power reduc- 0 to 7 N/A 0 Valid from

PR_enDCpMaxEU- tion applied by the eNB to the LTE18A,
TRApowerOffset UE maximum transmit pow- FLF18A,
er (maxUEtxPower) to derive and
the maximum power value (p- TLF18A.
MaxEUTRA) that the UE can
transmit to the EUTRA when in
EN-DC as follows:
p-maxEUTRA [dBm] =
maxUEtxPower[dBm] -
enDCpMaxEUTRApowerOffset
[dB]
where:
- maxUEtxPower is the
maximum UE transmit power
per corresponding EN-DC
power class.
- p-maxEUTRA is the value

configured by the eNB to the
UE .
LNBTS/NRDCD- The parameter specifies the 0 to 7 N/A 0 Valid from

PR_enDCpMaxNR- power reduction applied by the LTE18A,
powerOffset eNB to the UE maximum trans- FLF18A,
mit power (maxUEtxPower) to and
derive the maximum power val- TLF18A.
ue (p-MaxNR) that the UE can

Supported
sion
transmit to the NR when in EN-

DC as follows:
p-maxNR [dBm] =
maxUEtxPower[dBm] -
enDCpMaxNRpowerOffset
[dB]
where:
- maxUEtxPower is the UE
maximum UE transmit power
per corresponding EN-DC
power class.
- p-maxNR is the value

configured by the en-gNB to
the UE, based on indication
received from the eNB.
LNBTS/NRDCDPR_ The parameter indicates the UE • 10sf N/A 20sf Valid from
tPeriodicPhr configuration for sending peri- • 20sf LTE18A,
odic power headroom reports FLF18A,
• 50sf
• 100sf
(EN-DC). TLF18A.
• 200sf
• 500sf
• 1000sf
LNBTS/NRDCDPR_ Indicates the minimum interme- • 10sf N/A 0sf Valid from
tProhibitPhr diate time between two consec- • 20sf LTE18A,
utive power headroom reports FLF18A,
• 50sf
• 100sf
(EN-DC). TLF18A.
• 200sf
• 500sf
• 1000sf
LNBTS/NRDCDPR_al- Indicates the method that the • no pref- N/A N/A Valid from
lowedBcSelectMethod MeNB follows in the selection erence xL19B,
of the allowed band Combina- • max MI- FLF19B,
tion List for MRDC and relat- MO lay- and
ed feature sets to use in the ers TLF19B
SgNB Addition or MeNB initi- onwards.

Supported
sion
ated SgNB Modification for in- • max

tra-eNB mobility procedure. MIMO
layers
Note: This parameter
with min
has to be configured
CCs
in the module INI file
• max MI-
if actCAggrLteNr-
MO lay-
DualConnecitiv-
ers with
ity parameter is set
max
to enhanced_CA_
CCs
LTE_NR
LNBTS/NRDCDPR_ This parameter is used to en- • true N/A N/A Valid from
measGapEnableB1NR able or disable measurement • false xL19B,
gaps for B1 measurements for FLF20A,
NR. and
TLF20A
onwards.
LNBTS/NRDCDPR_ This parameter defines the • 10: cov- N/A N/A Valid for
dynTriggerLteNrDc- method for dynamic triggering erage- LTE18A,
ConfList.method of LTE NR Dual Connectivity. Based FLF18A,
• 50: cov- and

• coverageBased: EN-DC
erage- TLF18A
is set up on reception of a
And- onwards.
valid (pointing to a candi-
Buffer- But cover-
date NR PSCell) B1 mea-
Based ageAnd-
surement report.
Buffer-
• coverageAndBuffer-
Based
Based: EN-DC is set up
value is
when the layer2 buffer
support-
has overflown and a valid
ed from
(pointing to a candidate NR
xL19B,
PSCell) B1 measurement
FLF19B,
report is received from the
and
UE.
TLF19B
onwards.
LNBTS_tLte The parameter specifies the 10 to 10000 10 N/A Valid from

NrDualConnectPrep maximum time that the MeNB ms LTE18A,
will wait for the en-gNB mes- FLF18A,

Supported
sion
sage in response to a mes- and

sage sent by the MeNB to the TLF18A.
en-gNB. This timer supervis-
es the MeNB initiated SgNB
addition procedure, the MeNB
initiated SgNB modification
procedure, the MeNB initiat-
ed SgNB release procedure as
well as the reception of the SN
STATUS TRANSFER follow-
ing the request from the SgNB
to release the SGNB or for SN
change. During the MeNB initi-
ated SgNB Addition procedure,
this timer plays the role of TD-
CPrep, as defined in 3GPP.
LNBTS/PMRNL_mt The parameter indicates the • 0 - dis- N/A 15 min- Valid from
X2gNBperCell configuration of measurement abled utes LTE18A,
type - LTE X2 (gNB) per cell. • 15 min- FLF18A,
utes and
TLF18A.
• 30 min-
utes
• 60 min-
utes
• 360
minutes
• 720
minutes
• 1440
minutes
LNCEL_upper Indicates that the LTE NR Dual 0 to 7 1 N/A Valid from

LayerIndicationR15 Connectivity Activation module LTE18A,
will not create the further- FLF18A,
PlmnIdL structure. The mod- and
ule will only set the value for TLF18A.
all the elements in the defined
structure.

Supported
sion
LNCEL/SIB_primPlmn Indicates that the LTE NR Dual 0 to 7 1 N/A Valid from

Connectivity Activation module LTE18A,
UpperLayerIndica-
will not create the SIB object. FLF18A,
tionR15
The parameter is modified on- and
ly if the object is defined under TLF18A.
LNCEL.
LNBTS_ This parameter specifies the 1001 N/A 1001 Valid from
qciTab5nrPdcpProfIdx identifier of the corresponding LTE18A,
PDCP profile used for LTE NR FLF18A,
LNBTS_
Dual Connectivity. and
qciTab6nrPdcpProfIdx
TLF18A.
LNBTS_ qciTab5,
qciTab7nrPdcpProfIdx qciTab69,
and qc-
LNBTS_
iTab70 are
valid from
LNBTS_ xL19B,
qciTab9nrPdcpProfIdx FLF19B,
and
LNBTS_
TLF19B,
onwards
LNBTS_ only.
LNBTS_ This parameter enables the pe- • false N/A false Valid for
actPeriodicB1NR riodic activation or deactivation • true xL20B,
of B1-NR measurements which FLF20B,
is used for dynamic triggering TLF20B
of the LTE NR Dual Connec- and above
tivity module in the LTE BTS.
The timing of this functionali-
ty is controlled via configurable
supervision and retry timers.
The configured timers are valid
for all LNCEL which are listed
in the dynTriggerLteNrDc-
ConfList of the related NRD-
CDPR/NRDCPR.

Supported
sion
LNBTS_nrRestric- Indicates if the NR restriction • 0: dis- N/A 0 Valid for

tionOverride flag in the handover restriction abled xL20B,
list can be overridden. • 1: FR1 FLF20B,
TLF20B
When the LNBTS_nr- • 2: FR2
and above
RestrictionOverride para-
meter is set to FR1 or FR2, the
UE is allowed to setup sgNB
on FR1 or FR2 bands even if
its Handover Restriction List in-
cludes NR Restrict in EPS as
Secondary RAT' IE and is set
to NRrestrictedinEPSasSe-
condaryRAT.
• FR1 is defined as the NR

frequencies in the range of
450 MHz to 6000 MHz.
• FR2 is defined as the NR
frequencies in the range of
24250 MHz to 52600 MHz.
Note: When the

actLteNrDualCon-
nectivity para-
meter is set to false,
the BTS ignores
the setting of the
LNBTS_nrRestric-
tionOverride pa-
rameter.
LNBTS/NRDCDPR_ Signifies the retry timer for B1- [20 to 120] s 10 s 30 s Valid for
retryTimerB1NR NR measurements activation. xL20B,
It is the timer between subse- FLF20B,
quent activations of the B1-NR TLF20B
measurements which is used and above
as dynamic trigger for EN-DC
establishment. Its expiration
triggers B1-NR measurements
reactivation if the measure-

Supported
sion
ments were deactivated be-

cause of supervision timer ex-
piry. It starts at each activation
of B1-NR measurements which
indicates the time in which
measurements are not active
at the UE (retryTimerB1NR
- supervisionTimerB1NR). It
stops at the reception of the
first RRC:MeasurementReport
for B1-NR measurements.
LNBTS/NRDCDPR_ Indicates the supervision [1 to 10] s 1s 3s Valid for

supervisionTimerB1NR timer for B1-NR measure- xL20B,
ments. It is the timer guard- FLF20B,
ing reception of the first TLF20B
RRC:MeasurementReport for and above
B1-NR measurements that is
used as a dynamic trigger for
EN-DC establishment. Its ex-
piration triggers B1-NR mea-
surements deactivation. The
timer is started each time the
B1-NR measurements are ac-
tivated for the UE and stopped
at the reception of the first
RRC:MeasurementReport for
B1-NR measurements.
LNBTS_ Indicates the range(s) of ARP • Bit 0:not N/A 65534 Valid for
qciTab5arpEnDcMask values for which this QCI is eli- used:0: xL20B,
gible for LTE NR Dual Connec- • Bit FLF20B,
LNBTS_
tivity (EN-DC). 1:ARP TLF20B
qciTab6arpEnDcMask
1:1: and above.
Each bit of this parameter
LNBTS_
stands for one ARP value from • Bit
qciTab7arpEnDcMask
1 to 15. Bit number 0 is not 2:ARP
LNBTS_ used. 2:1:
qciTab8arpEnDcMask • Bit
If a bit is set to value '1', for the
LNBTS_ 3:ARP
corresponding ARP value this
qciTab9arpEnDcMask 3:1:

Supported
sion
LNBTS_ QCI is eligible for LTE NR Dual • Bit

qciTab69arpEnDcMask Connectivity (EN-DC). 4:ARP
4:1:
LNBTS_ If a bit is set to value '0', for the
qciTab70arpEnDcMask corresponding ARP value this • Bit
QCI cannot be used for LTE NR 5:ARP
Dual Connectivity (EN-DC). 5:1:

• Bit
6:ARP
6:1:
• Bit
7:ARP
7:1:
• Bit
8:ARP
8:1:
• Bit
9:ARP
9:1:
• Bit
10:ARP
10:1:
• Bit
11:ARP
11:1:
• Bit
12:ARP
12:1:
• Bit
13:ARP
13:1:
• Bit
14:ARP
14:1:
• Bit
15:ARP
15:1:
LNBTS/NRDCDPR_ Indicates the duration the 300 to 2000 100 N/A xL20C,
mrWaitTimer MeNB waits for a B1-NR MR FLF20C,

Supported
sion
for a high priority NR carrier af- and

ter a B1-NR Measurement Re- TLF20C
port (MR) is received from a onwards.
User equipment (UE) for a low
priority NR carrier.
LNCEL_maxNrIfFreqs Indicates the optional limit for 1 to 7 1 N/A xL20C on-

the maximum number of NR wards
carriers, which can be activated
Not applic-
by the en-gNB in the UE that is
able for
operating in the EN-DC mode
FLF and
for NR inter-frequency mea-
TLF ver-
surements.
sions.
If the limit is not provided, then
it is assigned internally by the
eNB and passed to the en-gNB.
Otherwise, the configured value
is assigned to the en-gNB.
Note: The minimal

requirement for the
UE operating in the
EN-DC mode in
terms of supported
number of monitored
frequency layers are
provided in 3GPP
TS 36.133, chapter
8.1.2.1.1b Monitor-
ing of multiple lay-
ers using gaps (E-
UTRA-NR dual con-
nectivity) / 8.1.2.1.
1b.1 Maximum al-
lowed layers for mul-
tiple monitoring for
UE in NSA operation.
Those shall not be
crossed in planned
deployments, unless

Supported
sion
the UEs operating in

the given market sup-
port higher limits.
In the intra- or inter-eNB

HO scenario with EN-DC
connectivity, when different
values of maxNrIfFreqs
parameter are set on the
source and target LTE cells, en-
gNB supports the functionality
of dynamic update of the
maximum allowed number of
inter-frequency NR carriers
during handover.
LNBTS_actEndcDrop- The LNBTS_actEndcDrop- • true false N/A xL20C,

Monitor Monitor parameter activates • false FLF20C,
the blocking of B1-NR mea- and
surements for an EN-DC capa- TLF20C
ble UE. onwards.
If the LNBTS_
actEndcDropMonitor
parameter is enabled, eNB
starts monitoring the number
of 5G drops (reception of
X2AP:SgNBReleaseRequired
with cause code Radio
connection with UE lost) and if
the number of drops per carrier
meets the configurable value
within a certain time window,
then that frequency is not
eligible for EN-DC service for a
specific amount of time.
LNBTS_endcSched- Specifies the DL scheduling 1 to 10 0.5 1 xL20C,

WeightBoostDlDCDPR weight scaling factor of a non- FLF20C,
GBR bearer if NR PDCP is and
configured on the bearer.

Supported
sion
If the value of the LNBTS_ TLF20C

endcSchedWeightBoostDl onwards.
parameter is set to 1, then the
EN-DC DL scheduling weight
boost is deactivated.
Note: If the actL-

teNrDualConnec-
tivity parameter is
set to true, then the
following conditions
must be fulfilled:
• Configure the
endcSched-
WeightBoost-
Dl parameter.
• If the value of
the support-
edCellTech-
nology para-
meter is set to
TDD or mixed_
FDD_TDD, then
the endcSched-
WeightBoost-
Dl parameter
value must be
equal to the
endcSched-
WeightBoos-
tUl parameter
value.
LNBTS_endcSched- Specifies the UL scheduling 1 to 10 0.5 1 xL20C,

WeightBoostUl weight scaling factor of a non- FLF20C,
GBR bearer if NR PDCP is and
configured on the bearer. TLF20C
If the value of the LNBTS_ onwards.
endcSchedWeightBoostUl
parameter is set to 1, then the

Supported
sion
EN-DC UL scheduling weight

boost is deactivated.
Note: If the value of

the actLteNrDu-
alConnectivity
parameter is set to
true, then the follow-
ing conditions must
be fulfilled:
• Configure the
endcSched-
WeightBoost-
Dl parameter.
• If the value of
the support-
edCellTech-
nology para-
meter is set to
TDD or mixed_
FDD_TDD, then
the endcSched-
WeightBoost-
Dl parameter
value must be
equal to the
endcSched-
WeightBoos-
tUl parameter
value.
LNBTS_ Signifies that the LNBTS_ • true false N/A xL20C,

actB1ExtMeasNR actB1ExtMeasNR parameter • false FLF20C,
activates the B1 extended mea- and
surement report for NR. TLF20C
onwards.
LNBTS/NRDCD- Signifies that the LNBTS/ • true false N/A xL20C,

PR_dynTriggerL- NRDCDPR_dynTrig- • false FLF20C,
gerLteNrDcConfList. and

Supported
sion
teNrDcConfList. actB1NrBeamMeas parame- TLF20C

actB1NrBeamMeas ter activates B1-NR beam lev- onwards.
el measurements in the LNCEL
indicated by the lcrId para-
meter.
LNBTS_actEnDcLt- Signifies that the LNBTS_ • true false N/A xL20C,

eDlMimoOptBcSel actEnDcLteDlMimoOptBcSel • false FLF20C,
parameter enhances the and
creation of the allowedBC- TLF20C
ListMRDC parameter provided onwards.
to the target en-gNB during
the SgNB Addition or SgNB
Modification procedure by
taking into account the DL
MIMO mode configuration of
the UE's PCell and serving/
candidate SCells.
If the value of the LNBTS_

actEnDcLteDlMimoOptBcSel
parameter is set to true and
the MRBTS/LNBTS/NRDCDPR-
allowedBcSelectMethod
parameter values are different
from no preference, eNB
acting as MeNB enhances the
creation of the allowedBC-
ListMRDC parameter provided
to the target en-gNB during
the SgNB Addition or SgNB
Modification procedure.
eNB takes into account the DL

MIMO mode configuration of
the UE's PCell and serving/can-
didate SCells to find out the
maximum potential number of
DL MIMO layers that an LTE
CA configuration within a UE
supported MRDC band combi-

Supported
sion
nation can provide. This is used

for selecting the MRDC band
combinations per each different
MRDC band combination group
which can maximize the num-
ber of configurable MIMO lay-
ers in the LTE leg at the UE in
EN-DC mode.
If the value of the LNBTS_

actEnDcLteDlMimoOptBcSel
parameter is set to true
and the value of the
MRBTS/LNBTS/NRDCDPR-
allowedBcSelectMethod
parameter is set to no
preference or this parameter is
set to false, no enhancement
takes place in the creation of
the allowedBC-ListMRDC .
LNBTS_actUL- The LNBTS_actULCaForEnDc • true false N/A xL20C,

CaForEnDc parameter activates the UL CA • false FLF20C,
configuration of EN-DC capable and
UEs. A value of nonConcur- TLF20C
rentULCaAndEnDc activates onwards.
the configuration of UL CA for
the UEs, which are EN-DC ca-
pable but not in EN-DC mode.
LNBTS_actEnDcLt- When the value of the ac- • true false N/A xL20C,
eDlTputBcSel tEnDcLteDlTputBcSel pa- • false FLF20C,
rameter is set to true and the and
MRBTS/LNBTS/NRDCDPR_al- TLF20C
lowedBcSelectMethod para- onwards.
meter values are different from
no preference, eNB acting as
MeNB enhances the creation
of the allowedBC-ListMRDC
IE by taking into account, be-
sides the DL MIMO mode as

Supported
sion
per legacy LTE5761 feature. Al-

so, the channel bandwidth of
the UE's PCell and serving/can-
didate LTE SCells for selecting
the MRDC band combinations
to provide to the en-gNB. This
allows to maximize DL through-
put in LTE leg. If LTE5515 is al-
so active (that is, enableBw-
ComSetChkEnDc parameter
value is set to true), eNB con-
siders only cell channel band-
widths, which are also support-
ed by the UE in the respective
frequency band sub-blocks.
LNBTS_actEndcSpid- This parameter activates SPID N/A N/A 0 xL21A and

Fwd forwarding in EN-DC greater on-
ly
LNBTS_ This parameter activates UL 0:disabled; 0:dis- 0 xL21A and

actUL256QamForEnDc 256 QAM for EN-DC capable 1:nonCon- abled; greater on-
UEs in the following way: current 1:non- ly
Con-
• 0: disabled
cur-
• 1: nonConcurrent - EN-DC
rent
capable UEs may get UL
256QAM on PCell/SCell
with UL carrier configured
when not in EN-DC mode.
If the feature is active,

it is applicable on the
LNCELs with actModula-
tionSchemeUL set to 256QAM
or 256QAMand16QAMHighMCS.
LNBTS_actUeTri- This parameter activates UE 0:disabled; 0 0 xL21A and

gEnDcTakeBack triggered EN-DC take-back. If 1:ignore; greater on-
activated, the MeNB detects 2:release ly
SCGFailureInformationNR
from the UE with the

Supported
sion
specific settings of particular

information elements
(measResultFreqListNR-
r15, failure type).
The following options are avail-

able:
• Disabled
• Ignore
• Release
Depending on the setting of this

parameter, eNB will:
• 0: disabled - Send 'X2AP:

SGNB MODIFICATION
REQUEST' to gNB.
• 1: ignore - Ignore this SCG
failure indication and not
forward it to gNB.
• 2: release - Trigger EN-DC
take-back
LNBTS_actMfbiNr This parameter activates MFBI N/A N/A 0 xL21A and

support in NR frequencies for greater on-
EN-DC. ly
LNBTS_actVoLte- This parameter activates along N/A N/A 0 xL21A and

NoEnDcDrop with the ongoing EN-DC, dur- greater on-
ing VoLTe setup. It works on ly
top of the feature, VoLTE with-
out EN-DC actVoLteNoEnDc
which triggers SgNB release in
case of VoLTe establishment. If
this parameter is set to true,
eNB will not trigger SgNB re-
lease in case of VoLte estab-
lishment, but block EN-DC set-
up during ongoing VoLTe (QCI1
and QCI65/66).

Table 5: LTE NR Dual Connectivity Activation INI parameters
Note:
• For description of INI parameter relationships, see Appendix A: Description of INI para-
meter relationships.
• The value for LNBTS_qciTab<x>nrPdcpProfIdx can always be 1001. So, the value
is set by the LTE NR Dual Connectivity module directly and is not present in the configu-
ration file.
• To activate dynamic trigger dual connectivity feature, MRBTS/LNBTS/
NRDCDPR_dynTriggerLteNrDcConfList structure has to be defined. The dyn-
TriggerLteNrDcConfList structure has two parameters which are, lcrid and
method. See Dynamic trigger LTE-NR DC configuration list GUI pa-
rameter to understand how dynTriggerLteNrDcConfList.lcrid is filled. The
dynTriggerLteNrDcConfList.method can only be set to coverageBased value.
If method is set to coverageBased, then at least one instance of nrDcMeasConfig
structure and one instance of nrDcQuantityConfig structure must be defined. The
module defines nrDcQuantityConfig as shown below. The nrDcQuantityConfig
structure with quantityConfigId=1 is configured by the ANR 5G module.
<list name="nrDcQuantityConfig">
<item>
fc4
fc4
1
</item>
• For xL21A and above, nrDCMeasConfig is replaced with ENDCDMEASCONF managed
object under MRBTS/LNBTS/NRDCDPR. The EN-DC module creates a dummy
ENDCDMEASCONF managed object, if not present already. The same managed object is
later modified by ANR module as required.
• For more information on the EN-DC feature activation parameters, see EN-
DC_Attributes.xlsx
• For more information on the EN-DC feature activation parameters, see the attached EN-
DC_Attributes.xlsx file. To view the attachment, you must save the attached file to your
system. To save the file, do the following:
1. In the PDF, from the menu items on the left, click the Attachments: View file attach-
ments icon.
2. Select the EN-DC_Attributes.xlsx file.
3. Click the Options icon and select Save Attachment to save the file in your sys-
tem.

6.2.1 Exclusion list in the INI configuration file
The INI configuration file consists of an exclusion list called Global Exclusions that:
• excludes parameter names if it is not defined in a particular version configuration.

• persists excluded parameters in EN-DC configuration to skip when required from an initial change
set.
• considers exclusion even in dependency checks.
6.2.2 Using User Defined Functions (UDFs) to determine parameter value
The LTE NR Dual Connectivity Activation (EN-DC) module provides User Defined Functions (UDFs)
capability to determine the values of the eUTRA-New Radio Dual Connectivity parameters. By using
UDF, the value of the parameter is not fixed and the operator has the flexibility to decide the value of
the parameter based on other conditions.
For example, the actLteNrDualConnectivity parameter must be set to false if the site is
operating on frequency sync mode. The operator can then set audit rules similar to the PCE module to
decide the value of the actLteNrDualConnectivity parameter.
Note: The UDF path must be set in the LTE NR Dual Connectivity Activation (EN-DC)
configuration file.
6.2.3 Global list in INI file
The INI configuration file consists of a global parameter list called Global, which is associated to the
user defined functions. The parameters are:
• UserDefined_management_module_file_name: Signifies the complete path including the

filename, which has the UserDefined_management_class_name class defined.
Note: For more information, see Appendix C: Sample user defined management module
file.
• UserDefined_management_class_name: Signifies the class name in the user defined

management module file. If the parameter is present, then it is instantiated by the EN-DC module.
This class has access to the script_data and the operator can use this data by writing their logic. It
is mainly used for caching mechanism.
• UserDefined_function_file_path: Signifies the complete path (folder path containing files
having UDF functions defined) of the python files containing user defined functions.
Note: For more information, see Appendix B: Sample python file with user defined
functions.

6.2.4 Example of LTE NR Dual Connectivity Activation configuration file
The following is an example of the LTE NR Dual Connectivity Activation module configuration file:
[Global]
UserDefined_management_module_file_name = /home/vson/udf/endc_custom_
cache.py
UserDefined_management_class_name = UDFCustomHandler
UserDefined_function_file_path = /home/vson/udf/py_files
[NE Version=*]
LNBTS_actLteNrDualConnectivity=true
LNBTS_actDynTrigLteNrDualConnectivity=true
[NE Version=xL20C]
LNCEL_maxNrIfFreqs=5
LNBTS_actEndcDropMonitor=true
LNBTS_endcSchedWeightBoostDl=2
LNBTS_endcSchedWeightBoostUl=10
LNBTS_actB1ExtMeasNR=true
LNBTS_actEnDcLteDlMimoOptBcSel=true
LNBTS_actEnDcLteDlTputBcSel=true
LNBTS_actULCaForEnDc=nonConcurrentULCaAndEnDc
LNBTS/NRDCDPR_dynTriggerLteNrDcConfList.actB1NrBeamMeas=true
LNBTS/PMRNL_mtX2gNBperCell=15min
LNBTS/NRDCDPR_dlPathlossChg=3 db
LNBTS/NRDCDPR_enDCpMaxEUTRApowerOffset=0 db
LNBTS/NRDCDPR_enDCpMaxNRpowerOffset=0 db
LNBTS/NRDCDPR_tPeriodicPhr=20sf
LNBTS/NRDCDPR_tProhibitPhr=0sf
LNBTS/NRDCDPR_retryTimerB1NR=0
LNBTS/NRDCDPR_supervisionTimerB1NR=5
LNBTS/NRDCDPR_dynTriggerLteNrDcConfList.method=coverageAndBufferBased
LNCEL/SIB_primPlmnUpperLayerIndicationR15=0
LNBTS_qciTab5lteNrDualConnectSupport=EN-DC
LNBTS_qciTab5nrPdcpProfIdx=1001
LNBTS_actCAggrLteNrDualConnectivity=disabled
LNBTS_actPeriodicB1NR=true
LNBTS_nrRestrictionOverride=FR1
LNBTS_qciTab5arpEnDcMask=65500

[NE Version=FLF20C]
LNBTS/NRDCDPR_dynTriggerLteNrDcConfList.method=coverageAndBufferBased
[NE Version=TLF20C]

LNBTS/NRDCDPR_dynTriggerLteNrDcConfList.method=coverageBased
[Global Exclusions]
LNBTS_qciTab5startArpEnDc:
LNBTS_qciTab5stopArpEnDc:
LNBTS_qciTabOperator.startArpEnDc:
LNBTS_qciTabOperator.stopArpEnDc:
Note: The required set of parameters and values must be configured for each LTE version in
the configuration file. Otherwise, the latest parameter list for the corresponding LTE version
will be picked up.
For example,
• If xL20A section is not present, the module will refer to xL19B section.

• If FLF19B section is not present, the module will refer to FLF19A section.
• If FLF19A section is not present, the module will refer to FLF19 section.
6.3 Importing INI parameters

In EdenNet, you can import and activate the configuration files. You can also edit, export, delete, activate, and deactivate the
configuration files.
Prerequisites
• Only users with Administrator privileges can modify the INI parameters.
• The INI file must be available. For the list of INI file parameters, see LTE NR Dual Connectivity
Activation INI parameters.

Cross-OSS:

d) Click Log In.
2. Click Administration → Modules.
The following module categories appear in the left pane:
• EdenNet modules: Lists the modules provided by Nokia.

• Adapted modules: Lists the modules developed by users.
• Helper modules: Lists the modules used for troubleshooting by Nokia support teams.
3. Click Helper modules → LTE_NR_Dual_Connectivity_Activation.
4. Click Configure → Module Configuration.
The LTE_NR_Dual_Connectivity_Activation Configuration Manager dialog box appears.
5. Click the Module Global Configuration category and then do one of the following:
• Import And Activate: Click to import a file and activate it immediately.

• Import: Click to import a configuration file.
• Activate: Click to activate the selected file.

Note: Multiple configuration files can be activated.
Expected outcome
The LTE NR Dual Connectivity Activation configuration file is imported and activated.
Note: In the LTE_NR_Dual_Connectivity_Activation Configuration Manager dialog box,

you can do one of the following:
• Export: Click to export the selected file to your system.

• Delete: Click to delete the selected file from the list.
Note: Users with Administrator or SON Module Manager permission can

delete the configuration files. The configuration files are deleted if they are not
used by other modules.
• Deactivate - Click to deactivate an activated file.
Note: If a configuration file is not used by other modules listed in the Active
SON Modules or Module History area, you can deactivate the configuration
file.
• Set As Default - Click to set the selected file as the default configuration.
• Reset - Click to reset the edited parameter values in the selected INI file.
• Save - Click to save the new version of the configuration file after editing the parameter
values in the selected INI file.
• Save As - Click to save the configuration file with a different name.
For more information, see the Configuring a module section in the EdenNet User and Admin-
istration Guide.

LTE NR Dual Connectivity Activation DN1000025281 1-1 Viewing LTE NR Dual Connectivity
Guide Activation report
7 Viewing LTE NR Dual Connectivity Activation report

For every module instance, the LTE NR Dual Connectivity Activation module generates a report in an Excel file. You can view
the report and take appropriate actions, if required.

Cross-OSS:

d) Click Log In.
2. Click the Status tab.
The Status page appears.
3. In the Active SON Modules or Module History area, select the

LTE_NR_Dual_Connectivity_Activation module.
The LTE NR Dual Connectivity Activation module status appears in the Execution Status tab.
4. Click the Logs tab.
5. In the User Outputs option, click the username. For example, admin.
The Directory Listing For dialog box appears listing the module filename.
6. Click the LTE_NR_Dual_Connectivity_Activation filename.
A list of Excel file appears.
7. Click the required Excel file.
Expected outcome
The Excel file is saved to your local system. You can open and view the report. For more
information, see LTE NR Dual Connectivity Activation reports.

7.1 LTE NR Dual Connectivity Activation reports

The LTE NR Dual Connectivity Activation module generates a report in an Excel file. Each worksheet
in the Excel is a report.
Table 6: LTE NR Dual Connectivity Activation module report describes each report available in the Ex-
cel file.
Worksheet name Description
Logs Displays the module execution logs which includes warning mes-
sages or errors, if any.
GUI Parameters Displays information regarding the GUI parameters defined for the
module.
Configuration Changes Displays the configuration changes proposed to the network and
their push status.
Summary Report Displays the module summary.
Table 6: LTE NR Dual Connectivity Activation module report
Table 7: Logs sheet describes the columns present in the Logs sheet.
Tab Description
Time Indicates the time of the log.
Type Indicates the type of the log. For example, error, or warning.
Message Indicates the message of the log.
Table 7: Logs sheet
Table 8: GUI Parameters sheet describes the columns present in the Parameters sheet.
Tab Description
UI Parameter Lists all the GUI parameters.
Value Indicates the value of the parameter used for executing the module.
Table 8: GUI Parameters sheet
Table 9: Configuration changes sheet describes the columns present in the Configuration sheet
sheet.
Tab Description
Target cell/eNodeB dn Indicates the target cell name.
Vendor Indicates the cell vendor name.

Tab Description
OSS Indicates the name of the OSS.
Configuration changes (dictio- Indicates the LTE NR Dual Connectivity Activation parameters and
nary with parameter:value values for which the module is proposing the change.
Push status (valid only in Indicates the push status, such as, success or failure.
closed loop)
Table 9: Configuration changes sheet
Table 10: Summary Report sheet describes the columns present in the Summary sheet.
Tab Description
Summary Provides a summary of the module operation.
Number of cells Indicates the number of cells modified the module.
Table 10: Summary Report sheet

Guide Activation events
8 Viewing LTE NR Dual Connectivity Activation events

In addition to the generic events that the EdenNet framework generates (for example, module started, module idling, and
module finished), you can view events that are specific to the LTE NR Dual Connectivity Activation module.

Cross-OSS:

d) Click Log In.
2. Click the Events tab.
A list of filters appears in the left pane.
3. From the Module/Service drop-down list, select the LTE NR Dual Connectivity Activation instance.
You can view the event logs using the following filters:
• Name: Indicates the event name.

• Category: Indicates the category of the event.
• Level: Indicates the level of the event.
• Source Type: Indicates from where the event originated.
• Target Type: Indicates to where the event is targeted.
• Target: Indicates the target of the event (cell name can be selected).
Note: The common event levels are information and warning. By default, the warning
and error filters are selected. To view all levels of events, remove the warning and error
filters.
4. In the Time Range are, set the required time range.
5. Optional: In the Saved Filters field, enter a name for the event filter and save it using the Save As
New Filter option.
6. Click Filter.

Guide Activation events
Expected outcome
The events are listed based on the selected filter. For more information about the LTE NR Dual
Connectivity Activation module events, see LTE NR Dual Connectivity Activation events.
8.1 LTE NR Dual Connectivity Activation events

Table 11: LTE NR Dual Connectivity Activation module events describes the LTE NR Dual Connectivity
Activation module events.
Name Level Description
Mandatory parameters warning Indicates the:

missing for EN-DC configu-
• Source cell name or eNodeB DN
ration
• List of missing parameters
LTE-NR dual connectivity info Indicates the:

changes done
• Source cell name or eNodeB DN
• LTE-NR dual connectivity parameter changes
Table 11: LTE NR Dual Connectivity Activation module events

LTE NR Dual Connectivity Activation DN1000025281 1-1 Monitoring LTE NR Dual Connectivity
Guide Activation
9 Monitoring LTE NR Dual Connectivity Activation

You can monitor:
• SON activities: The SON Activity page enables you to view and monitor SON activities. For more
information, see the View and monitor SON activities section in the EdenNet User and Administra-
tion Guide.
• Status: The Status page enables you to view the status of SON modules. For more information,
see the View status of SON modules section in the EdenNet User and Administration Guide.
• Events: The Events page enables you to view SON events. For more information, see the Monitor
SON events section in the EdenNet User and Administration Guide.
9.1 LTE NR Dual Connectivity Activation impact on the network

For each vendor, the managed objects (created, deleted, or modified in a network) are listed in the Ac-
tions column of the CM objects or parameters section in the following document:
• EdenNet Module Specific Data for Nokia

LTE NR Dual Connectivity Activation DN1000025281 1-1 Appendix A: Description of INI parameter
Guide relationships
10 Appendix A: Description of INI parameter

relationships
Table 12: INI parameter relationship description describes the INI parameters relationships.
Parameter name Description of parameter relationships
LNBTS.actLteNrDualConnectivity (1) If supportedCellTechnology is configured

to FDD or TDD ormixed_FDD_TDD, the following
conditions must be fulfilled:
(1.1) actLteNrDualConnectivity can only be

configured to true if actSatBackhaul is set to false.
The feature is mutually exclusive.
(1.2) If actLteNrDualConnectivity is set to true, all

of the following conditions must be fulfilled:
- tLteNrDualConnectPrep must be configured.
- the NRDCDPR instance must exist.
(1.2.1) If (actLteNrDualConnectivity is set to

true) and (qciTab[x]-lteNrDualConnectSupport
is configured to EN-DC), then qciTab[x]-
nrPdcpProfIdx must be configured, where, x=5...9 or
x=69...70 or x=Operator.
(2) If the supportedCellTechnology is configured to

FDD or mixed_FDD_TDD the following conditions must
be fulfilled in addition to (1):
(2.1) If actLteNrDualConnectivity is set to true,

then all of the following conditions are fulfilled in addition
to (1.2):
- actProSeComm must be configured to false.
LNBTS.actDynTrigLteNrDualConnectivity (1) If supportedCellTechnology is configured

to FDD or TDD or mixed_FDD_TDD, the following
(1.1) actDynTrigLteNrDualConnectivity is
allowed to be set to true if all of the following conditions
are fulfilled:
(1.1.1) actLteNrDualConnectivity is set to true.

Guide relationships

(1.1.2) actEicic must be set to false in all the cells
of the eNB for which any of the following conditions are
satisfied:
(1.1.2.1) lcrId of the cell is configured in

dynTriggerLteNrDcConfList (NRDCDPR) or
(1.1.2.2) lcrId of the cell is configured in

dynTriggerLteNrDcConfList (NRDCPR) or
(1.1.2.3) lcrId is set to -1 in

dynTriggerLteNrDcConfList (NRDCDPR)
(1.2) If actDynTrigLteNrDualConnectivity is set

to true, all of the following conditions must be fulfilled:
(1.2.1) In NRDCDPR, dynTriggerLteNrDcConfList

must be configured with at least one item.
(1.2.2) For each NRDCPR instance that exists,

dynTriggerLteNrDcConfList must be configured
with at least one item per NRDCPR instance.
(1.2.3) In LNCEL_TDD, measGapPattern must be set

to gap0.
LNBTS.actCAggrLteNrDualConnectivity (1) If supportedCellTechnology is configured

to FDD or TDD or mixed_FDD_TDD, the following
(1.1) actCAggrLteNrDualConnectivity is allowed

to be set to blind_CA_LTE_NR or enhanced_CA_LTE_
NR if all of the following conditions are fulfilled:
- actLteNrDualConnectivity is set to true.
- actDLCAggr is set to true.
- cAggrLteNrDcCellList must be configured with at

least one item.
(2) If actCAggrLteNrDualConnecitivity
is not set to enhanced_CA_LTE_NR,
dynTriggerLteNrDcConfList-method is not
allowed to be set to coverageAndBufferBased in
NRDCDPR or any configured NRDCPR.

Guide relationships

(3) If actCAggrLteNrDualConnecitivity is set
to enhanced_CA_LTE_NR,allowedBcSelectMethod
must be configured.
LNBTS.qciTab5lteNrDualConnectSupport If (actLteNrDualConnectivity is set to true)

and (qciTab<x>-lteNrDualConnectSupport is
LNBTS.qciTab6lteNrDualConnectSupport
configured to EN-DC), qciTab<x>-nrPdcpProfIdx
LNBTS.qciTab7lteNrDualConnectSupport must be configured.
LNBTS.qciTab8lteNrDualConnectSupport <x> = 6 to 9
LNBTS.qciTab9lteNrDualConnectSupport
LNBTS.
qciTab69lteNrDualConnectSupport
LNBTS.
qciTab70lteNrDualConnectSupport
LNBTS.qciTab5startArpEnDc If (actLteNrDualConnectivity is set to true)

LNBTS.qciTab6startArpEnDc
configured to EN-DC), qciTab<x>-nrPdcpProfIdx
LNBTS.qciTab7startArpEnDc must be configured.
LNBTS.qciTab8startArpEnDc <x> = 6 to 9
LNBTS.qciTab5stopArpEnDc If (actLteNrDualConnectivity is set to true)

LNBTS.qciTab6stopArpEnDc
configured to EN-DC), qciTab<x>-nrPdcpProfIdx must
LNBTS.qciTab7stopArpEnDc be configured.
LNBTS.qciTab8stopArpEnDc <x> = 6 to 9
NRDCDPR.enDCp-MaxEUTRApowerOff- The value of enDCpMaxNRpowerOffset depends on

set the value of enDCpMaxEUTRApowerOffset in the
NRDCDPR instance as follows:
- if enDCpMaxEUTRApowerOffset has the value 0

[dB], enDCpMaxNRpowerOffset must be 0 [dB]

Guide relationships

[dB], enDCpMaxNRpowerOffset must be 7 [dB]

[dB], enDCpMaxNRpowerOffset must be greater than
or equal to 5 [dB]
- if enDCpMaxEUTRApowerOffset has the value (3 OR

4) [dB], enDCpMaxNRpowerOffset must be greater
than or equal to 3 [dB]
- if enDCpMaxEUTRApowerOffset has the value (5 OR

6) [dB], enDCpMaxNRpowerOffset must be greater than
or equal to 2 [dB]

[dB], enDCpMaxNRpowerOffset must be greater than
or equal to 1 [dB].
NRDCDPR.enDCpMaxNRpowerOffset The value of enDCpMaxEUTRApowerOffset depends

on the value of enDCpMaxNRpowerOffset in the
NRDCDPR instance as follows:
- if enDCpMaxNRpowerOffset has the value 0 [dB],

enDCpMaxEUTRApowerOffset must be 0 [dB].

enDCpMaxEUTRApowerOffset must be 7 [dB].

enDCpMaxEUTRApowerOffset must be greater than or
equal to 5 [dB].
- if enDCpMaxNRpowerOffset has the value (3 OR 4)

[dB], enDCpMaxEUTRApowerOffset must be greater
than or equal to 3 [dB].
- if enDCpMaxNRpowerOffset has the value (5 OR 6)

[dB], enDCpMaxEUTRApowerOffset must be greater
than or equal to 2 [dB].

enDCpMaxEUTRApowerOffset must be greater than or
equal to 1 [dB].
NRDCDPR.dynTriggerLteNrDcConfList. (1) If method is set to coverageBased or

method coverageAndBufferBased then at least one instance
of nrDcMeasConfig structure and one instance of
nrDcQuantityConfig structure must be defined.

Guide relationships

(2) in addition to (1):
(2.1) if method is set to coverageAndBufferBased

in at least one item of NRDCDPR-
dynTriggerLteNrDcConfList, then
- numTxWithHighNonGbr must not be set to 0 in

LNBTS_FDD or LNBTS_TDD
- actCAggrLteNrDualConnectivity must be set to

enhanced_CA_LTE_NR
(2.2) method cannot be set to coverageAndBuffer-

Based
LNBTS.tLteNrDualConnectPrep If actLteNrDualConnectivity is set to true,

tLteNrDualConnectPrep must be configured.
Table 12: INI parameter relationship description

LTE NR Dual Connectivity Activation DN1000025281 1-1 Appendix B: Sample python file with user
Guide defined functions
11 Appendix B: Sample python file with user defined

functions
sample_udf.py is a sample python file that contains user defined functions. The file must be present
in a location specified by the UserDefined_function_file_path parameter.
sample_udf.py
def get_sycn_instance_param_under_mrbts(key1, key2):

return "PhaseSync" #return FreqSync depending upon key1 and key2
def get_actDynTrigLteNrDualConnectivity_value(**kwargs):
# kwargs contain the below parameters which will be sent internally by
ENDC to the function:
#– kwargs['udf_cache_obj']: Management class instance where script data
is accessible
#– kwargs['dn']: complete MO DN of the parameter. For example: PLMN-
B016VF/MRBTS-182470/LNBTS-182470 for a LNBTS parameter.
#– kwargs['parameter_name']: Parameter name for which the value is being
determined. For example, "actDynTrigLteNrDualConnectivity"
#– kwargs['value_read_from_oss']: Holds current EMS value read from OSS
cache_obj = kwargs['udf_cache_obj']
script_data = cache_obj.get_script_data()
lnbts_dn = kwargs['dn']
param_name = kwargs['param_name']
ems_value = kwargs['value_read_from_oss']
key1 = "MRBTS/MNL/MNLENT/SYNC", "btsSyncMode"

key2 = "btsSyncMode"
if ems_value is None:
audit_value = "true"
elif ems_value =="false":
audit_value = "false"
elif get_sycn_instance_param_under_mrbts(key1, key2) == "PhaseSync":
audit_value = "true"
else:
audit_value = "false"
return audit_value

LTE NR Dual Connectivity Activation DN1000025281 1-1 Appendix C: Sample user defined
Guide management module file
12 Appendix C: Sample user defined management

module file
udf_custom_cls.py is a sample user defined management module file that specifies the
management class defined by the UserDefined_management_class_name parameter. The
UserDefined_management_module_file_name parameter must specify the complete path of this
file.
udf_custom_cls.py
class UDFCustomHandler(object):
def __init__(self, script_data):
self.script_data = script_data
def add(self, a, b):

return a+b
def get_script_data(self):
return self.script_data

Eden Net Lte NR Dual Connectivity Guide

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

Eden Net Lte NR Dual Connectivity Guide

Uploaded by

Copyright:

Available Formats

EdenNet 21 FP 2103

LTE NR Dual Connectivity Activation Guide

N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

Copyright © 2021 Nokia. All rights reserved.

Important Notice on Product Safety

2 Overview of LTE NR Dual Connectivity Activation module........................................................................ 7

3 LTE NR Dual Connectivity Activation functional description and guidelines........................................... 8

4 LTE NR Dual Connectivity Activation algorithm.......................................................................................... 9

5 LTE NR Dual Connectivity Activation execution........................................................................................10

6 LTE NR Dual Connectivity Activation configuration parameters............................................................. 14

7 Viewing LTE NR Dual Connectivity Activation report............................................................................... 46

8 Viewing LTE NR Dual Connectivity Activation events.............................................................................. 49

9 Monitoring LTE NR Dual Connectivity Activation......................................................................................51

10 Appendix A: Description of INI parameter relationships........................................................................ 52

11 Appendix B: Sample python file with user defined functions................................................................ 57

12 Appendix C: Sample user defined management module file................................................................. 58

EdenNet 21 FP 2103 © 2021 Nokia 3

Release Change description

EdenNet 21 FP 2103 Updated section:

• LTE NR Dual Connectivity Activation INI parameters is updated with the

EdenNet 20 FP 2011 Updated sections:

• Table 5: LTE NR Dual Connectivity Activation INI parameters is updated

• LTE NR Dual Connectivity interactions

EdenNet 20 FP 2010 Added sections:

• Using User Defined Functions (UDFs) to determine parameter value

EdenNet 21 FP 2103 © 2021 Nokia 4

Release Change description

• Appendix C: Sample user defined management module file

• Table 5: LTE NR Dual Connectivity Activation INI parameters is updated

• Example of LTE NR Dual Connectivity Activation configuration file

EdenNet 20 FP 2009 Updated sections:

• LTE NR Dual Connectivity Activation GUI parameters - The Activate

Note: The module enables actLteNrDualConnectivity

EdenNet 20 FP 2008 Updated section:

• LTE NR Dual Connectivity Activation INI parameters section is updated

EdenNet 20 FP 2007 No change.

EdenNet 19A FP 2004 Added section:

EdenNet 21 FP 2103 © 2021 Nokia 5

Release Change description

• Exclusion list in the INI configuration file

• LTE NR Dual Connectivity Activation INI parameters is updated with

EdenNet 19A FP 2003 No change

EdenNet 19A FP 2002 No change.

EdenNet 19A FP 2001 No change.

EdenNet 19A FP 1912 Updated sections:

• LTE NR Dual Connectivity Activation INI parameters

EdenNet 19A FP 1911 No change.

Table 1: Summary of changes

EdenNet 21 FP 2103 © 2021 Nokia 6

2 Overview of LTE NR Dual Connectivity Activation

• 5G deployment in the NSA option

Table 2: Supported vendor and technology

EdenNet 21 FP 2103 © 2021 Nokia 7

3 LTE NR Dual Connectivity Activation functional

• Deployment of a new eNodeB or LTE cell.

The module supports the following functionalities:

3.1 Operational modes of LTE NR Dual Connectivity Activation module

• Open loop mode

3.1.1 Open loop mode

3.1.2 Closed loop mode

EdenNet 21 FP 2103 © 2021 Nokia 8

4 LTE NR Dual Connectivity Activation algorithm

The LTE NR Dual Connectivity Activation module: