EdenNet 21

EdenNet deployment with and without

AC: Differences in data representation,
visualization, and behavior
DN09273754
Issue: 1-0
EdenNet deployment with and without DN09273754 1-0 Disclaimer
AC: Differences in data representation,
visualization, and behavior

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.
EdenNet deployment with and without DN09273754 1-0 Table of Contents
AC: Differences in data representation,
visualization, and behavior

Contents
1 Summary of changes...................................................................................................................................... 5

2 Overview........................................................................................................................................................... 6

3 CM interfaces................................................................................................................................................... 8

4 Storage of CM MOs and parameters.............................................................................................................9

5 Changes in CM parameter name and type................................................................................................. 10

6 UI parameter value support......................................................................................................................... 12

6.1 Data representation changes in AC based and direct OSS integration................................................. 12

7 SDK (new APIs for AC based integration)................................................................................................. 14

7.1 Handling of empty or null parameter values.......................................................................................... 14

8 DN (Distinguished Name) format change................................................................................................... 16

9 CM topology hierarchy changes..................................................................................................................19

10 Cell RET mapping file................................................................................................................................. 20

11 Plan provisioning functionalities in direct OSS and AC integration...................................................... 22

11.1 Plan name change in direct OSS and AC integration.......................................................................... 22
11.2 Plan validation status............................................................................................................................ 22
11.3 Split plan at OSS level..........................................................................................................................23

12 KPI chart per OSS....................................................................................................................................... 24

13 Configuring user label................................................................................................................................ 25

14 Online metadata retrieval........................................................................................................................... 26

15 CM MO filtering and scheduling................................................................................................................ 27

16 External cell handling................................................................................................................................. 28

16.1 Global external cells..............................................................................................................................28

17 Handling of special characters in DN....................................................................................................... 29

18 3GPP MO names of reference DN parameters.........................................................................................30

19 PLMN identity...............................................................................................................................................31

EdenNet 21 © 2021 Nokia 3

EdenNet deployment with and without DN09273754 1-0 Table of Contents
AC: Differences in data representation,
visualization, and behavior

20 CM Operation logs...................................................................................................................................... 32

21 NE version compatibility............................................................................................................................ 33

22 Glossary........................................................................................................................................................34

EdenNet 21 © 2021 Nokia 4

EdenNet deployment with and without DN09273754 1-0 Summary of changes
AC: Differences in data representation,
visualization, and behavior

1 Summary of changes

Release Change description

EdenNet 21 Updated sections:

• Overview - A note is added about the deprecation of direct CM in-

tegration.
• Table 2: Supported vendor and technology - updated with Eden-
Net support for AC based CM integration to the ZTE UME EMS.

EdenNet 20 FP 2011 No change.

EdenNet 20 FP 2010 No change.

EdenNet 20 FP 2009 No change.

EdenNet 20 FP 2008 No change.

EdenNet 20 FP 2007 Updated sections:

• Changes in CM parameter name and type: PCE migration tool

support is revoked.
• Data representation changes in AC based and direct OSS inte-
gration: PCE migration tool support is revoked.

EdenNet 20 Updated sections:

• Overview: Configuration of retainNativeDNFormat parameter

is supported for Ericsson 2G and 5G.
• Changes in CM parameter name and type: Structure parameter is
supported for Ericsson 2G and 5G.

Deleted sections:

• Plan format change visible in EdenNet GUI

• Viewing the plan
• MO count statistics

The behavioral differences in direct OSS and AC based integration

described in the deleted sections are resolved in EdenNet 20.

EdenNet 19A FP 2004 This is a document that describes the differences in data represen-
tation, visualization, and behavior in EdenNet deployment with direct
OSS and AC based integrations.

Table 1: Summary of changes

EdenNet 21 © 2021 Nokia 5

EdenNet deployment with and without DN09273754 1-0 Overview
AC: Differences in data representation,
visualization, and behavior

2 Overview
EdenNet is evolving by introducing a new CM framework utilizing Nokia’s existing CM product called
Advanced Configurator (AC/NAdC). EdenNet is integrated to EMS/OSS through an AC mediation lay-
er (for Configuration Management (CM)) and it is directly integrated to the EMS (for Performance Man-
agement (PM)). AC mediation layer supports multi-vendor, multi-technology, and multi-OSS network.

This document provides an overview of EdenNet deployment with and without AC. The differences in
data representation, visualization, and behavior between AC and direct OSS integration is described,
so that, the operators can enhance their adapted modules and improve the user experience with
EdenNet.

With the AC based solution, there are some changes in terms of how CM data is represented and
stored in EdenNet when compared to direct OSS integration.

While some changes are specific to the vendor and technology, some are common. It covers the major
differences for the adapted modules (new as well as pre-existing) and configuration files (which takes
CM managed objects and parameter names as input).

In EdenNet, CM data is available in:

• Module reports, logs, configuration, and customer documentation

• Database
• UI (including views)
• KPI reports and graphs
• Adapted modules implemented using SDK
• Offline files such as RET files, module configuration files, LMS files, and blacklisting files

The operator who uses EdenNet without AC based solution will experience some differences in CM
data representation. Also, the adapted modules developed by the operator might be impacted.

Table 2: Supported vendor and technology lists the EMS, vendor, and technology support with AC
based integration.

Vendor Technology

Huawei 2G, 3G, and 4G

Nokia 2G, 3G, 4G, and 5G

Ericsson OSS ENM 2G, 3G, 4G, and 5G

Note: 2G support is under piloting.

5G support can be delivered subject to NDA.

Ericsson OSSRC 2G, 3G, and 4G

ZTE UME 4G

EdenNet 21 © 2021 Nokia 6

EdenNet deployment with and without DN09273754 1-0 Overview
AC: Differences in data representation,
visualization, and behavior

Table 2: Supported vendor and technology

Note:

• AC based solution does not support Alcatel-Lucent.

• In AC based integration, the operator has the flexibility to view the CM data
representation as in direct integration by setting a one time configurable property -
retainNativeDNFormat as True in EdenNet. This is applicable only for Ericsson 2G,
3G, 4G, and 5G. For more information, contact Nokia technical support team.

Note: Nokia only supports the use of AC based integration for Nokia, Ericsson, and Huawei
vendors as direct CM integration is deprecated from EdenNet 21 release onwards for these
vendors.

EdenNet 21 © 2021 Nokia 7

EdenNet deployment with and without DN09273754 1-0 CM interfaces
AC: Differences in data representation,
visualization, and behavior

3 CM interfaces
Table 3: CM Interfaces lists the CM interfaces used in AC and direct OSS integration for Nokia,
Huawei, and Ericsson.

Vendor AC interface Direct OSS interface

Nokia NE3S Webservice interface racclimx CLI

Huawei 3GPP Bulk CM CORBA Interface MML interface is used for 2G

and 3G.
3GPP Bulk CM CORBA
Interface is used for 4G.

Ericsson BULK CM Interface (CNAI and BCG with Per MO based CM interface
OSSRC/REST with ENM) (CNAI, BCG, and REST)

Table 3: CM Interfaces

EdenNet 21 © 2021 Nokia 8

EdenNet deployment with and without DN09273754 1-0 Storage of CM MOs and parameters
AC: Differences in data representation,
visualization, and behavior

4 Storage of CM MOs and parameters

Table 4: CM MOs and parameter storage describes the storage of CM MOs and parameters in AC
based and direct OSS integration.

Vendor and technology AC based integration Direct OSS integration

All All CM MOs and parameters (including Only a few chosen CM MOs and
radio and transport) supported by the parameters are stored in the
OSS/EMS are stored in the AC data- EdenNet database.
base.

Table 4: CM MOs and parameter storage

EdenNet 21 © 2021 Nokia 9

EdenNet deployment with and without DN09273754 1-0 Changes in CM parameter name and
AC: Differences in data representation, type
visualization, and behavior

5 Changes in CM parameter name and type

Table 5: CM parameter name and type describes the changes in CM parameter name and type for
various vendors.

Direct OSS parameter name

Vendor and technology AC parameter name and type
and type

Huawei LTE Parameter name: uppercase Parameter name: lowercase

Note: This will im- For example, EARFCNDL For example, earfcndl
pact the PCE con- parameter of CELL MO is in parameter of CELL MO is in

figuration files that uppercase. lowercase.

are already de-

fined.

Huawei (all RATs) Parameter type: Bit String (where Parameter type: Bit String
one parameter consists of multiple
Note: PCE configu- Note: In direct OSS
bits having bit name, index, and
ration files might be integration, the PCE
values). The PCE module supports
changed. module supports bit
bit level auditing and enforcement.
level auditing and en-
For more information, see Pa-
Note: Supported for all forcement only for
rameter Consistency Check
Huawei RATs. Huawei 2G and 3G.
and Enforcement (PCE)
Guide. This is not applicable
for Huawei 4G.

Nokia (all RATs) Parameter type: Bit String (where Parameter type: Bit String
one parameter consists of multiple
For more information, see Pa- Operator should specify the col-
bits having bit name, index, and
rameter Consistency Check lated integer value of all the bits
values)
and Enforcement (PCE) mentioned in the parameter.
Guide. Operator should specify the col-
lated integer value of all the bits
mentioned in the parameter. Be-
havior is same as in direct OSS in-
tegration.

Note: Valid from AC 19

SPAC1908 onwards.

Ericsson 2G, 3G, 4G, and 5G Parameter type: Structure para- Parameter type: Structure pa-
meter rameter

EdenNet 21 © 2021 Nokia 10

EdenNet deployment with and without DN09273754 1-0 Changes in CM parameter name and
AC: Differences in data representation, type
visualization, and behavior

Direct OSS parameter name

Vendor and technology AC parameter name and type
and type

The fields in a structure parameter The structure parameter is not

are flattened into independent split and EdenNet considers it
parameters in the form of as a single parameter.
paramName_FieldName.

With the
retainNativeDNFormat flag
set to False, the plain structure
parameters are split into multiple
parameters with an underscore
( _ ) as a delimiter between
the parameter name and sub
parameter name.

For example:

Plmnid (structure parameter

name) has mcc, mnc, and
mnclength as internal sub
parameters. This Plmnid will
be split into three parameters as
follows:

• Plmnid_mcc
• Plmnid_mnc
• Plmnid_mnclength

With the
retainNativeDNFormat flag set
to True, the structure parameter
representation is the same as
direct integration solution.

Table 5: CM parameter name and type

Note: The PCE migration tool is no longer supported. This tool is used only by the Nokia
technical support team.

EdenNet 21 © 2021 Nokia 11

EdenNet deployment with and without DN09273754 1-0 UI parameter value support
AC: Differences in data representation,
visualization, and behavior

6 UI parameter value support

Generally, some CM parameters have two kinds of representations:

• UI (symbolic name)
• Internal values

For example:

• Enumerated parameter name - Link (ENUM type)

– UI values - {IubLink, IuCsLink, IuPsLink}

– Internal values - {0, 1, 2}
• Boolean parameter name isHOAllowed

– UI values {true, false}

– Internal values {0, 1}
• Interval type parameter name primaryCpichPower

– Internal values {-99 … 500}

default 330
– UI values {-9.9.. 50.0}
default 33.0

Note: In AC based integration:

• Adapted modules should fetch and provision the parameter values in UI format using
SDK interfaces. The configuration files should contain the UI format for the parameter
values. It is valid for all parameter types, vendors, and technologies.
• EdenNet stores and accepts only the UI values of the CM parameters.
• In the EMS/OSS, for few parameter types, the value can be in internal format and some
can be in UI format.
• EdenNet recommended UI values can be different from the native values present in the
EMS/OSS.
• There are some parameters with a special value. Generally, there is a number and de-
scription attached to that value. EdenNet will always return and accept the number irre-
spective of UI or internal value being asked for. This is valid from 19 SPAC1912 AC re-
lease. Prior to this release, the associated number was returned as the internal value
and description as UI value.
• By default, EdenNet accepts and provision the plan with UI values.

EdenNet 21 © 2021 Nokia 12

EdenNet deployment with and without DN09273754 1-0 UI parameter value support
AC: Differences in data representation,
visualization, and behavior

6.1 Data representation changes in AC based and direct OSS

integration
Table 6: Data representation changes lists the changes in data representation between AC based inte-
gration and direct OSS integration.

Vendor AC based integration Direct OSS integration

Huawei LTE UI values Internal values

Note: In EdenNet
GUI, DB, and reports
the internal values will
change to the UI val-
ues for adapted mod-
ules.

Table 6: Data representation changes

Note: For Nokia, Ericsson, and Huawei (2G and 3G), the parameter behavior is consistent in
AC based and direct OSS integration.

The PCE migration tool is no longer supported. This tool is used only by the Nokia technical
support team.

EdenNet 21 © 2021 Nokia 13

EdenNet deployment with and without DN09273754 1-0 SDK (new APIs for AC based integration)
AC: Differences in data representation,
visualization, and behavior

7 SDK (new APIs for AC based integration)

SDK is enhanced with new APIs for AC based multiple OSS integration. Nokia recommends using
these new APIs. For more information, see EdenNet Software Development Kit (SDK) section in SON
Module Development and Maintenance Guide.

AC based integration does not support:

• forced sync and validation from EdenNet module to OSS

• MO based CM upload

AC based EdenNet solution supports only bulkCM upload.

7.1 Handling of empty or null parameter values

From AC19 onwards, if parameter values are set to empty in the EMS, the values in the CM database
in AC will also be empty.

For example, for cell XXXXX, the oss value for spectrumEmissionReqMapping is []

Request:

ems.getEMSAttributes({'SubNetwork=ONRM_ROOT_MO,SubNetwork=ABCD,
MeContext=YYYY,ManagedElement=1,ENodeBFunction=1,EUtranCellFDD= XXXXX:
['spectrumEmissionReqMapping']})

Response:

{'SubNetwork=ONRM_ROOT_MO,SubNetwork=ABCD,MeContext=YYYY,
ManagedElement=1,ENodeBFunction=1,EUtranCellFDD= XXXXX ':
{u'spectrumEmissionReqMapping': []}}

From AC19 onwards, if the parameter is not present or the parameter value is set to null in the EMS,
then the parameter will not be stored in the database, unlike direct OSS integration where the parame-
ter is stored in the database.

For example, for cell XXXXX, the oss value for spectrumEmissionReqMapping is null.

Request:

ems.getEMSAttributes({'SubNetwork=ONRM_ROOT_MO,SubNetwork=ABCD,
MeContext=YYYY,ManagedElement=1,ENodeBFunction=1,EUtranCellFDD= XXXXX ':
['spectrumEmissionReqMapping']})

EdenNet 21 © 2021 Nokia 14

EdenNet deployment with and without DN09273754 1-0 SDK (new APIs for AC based integration)
AC: Differences in data representation,
visualization, and behavior

Response:

{'SubNetwork=ONRM_ROOT_MO,SubNetwork=ABCD,MeContext=YYYY,
ManagedElement=1,ENodeBFunction=1,EUtranCellFDD= XXXXX ': {}}

Table 7: GetChildAttribute API usage describes the usage of GetChildAttribute API in direct OSS
and AC based integration.

Direct OSS integration AC based integration

The GetChildAttribute API can be used to The GetChildAttribute API is used to query
fetch MO parameters, by passing the parent DN only the child CM MOs and parameters.
and parent MO type in a query to fetch parame-
ters. Ideally, this API should be used to get MO
parameters of the child MOs of the parent and
not its own.

Table 7: GetChildAttribute API usage

EdenNet 21 © 2021 Nokia 15

EdenNet deployment with and without DN09273754 1-0 DN (Distinguished Name) format change
AC: Differences in data representation,
visualization, and behavior

8 DN (Distinguished Name) format change

Table 8: DN format change describes the DN format change in direct OSS and AC based integration
for various vendors.

Vendor Change

Nokia (all RATs) In AC based integration, the change is in the root element of DN. Second
PLMN is replaced with actual region name.

For example:

Direct integration:

PLMN-PLMN/MRBTS-12/LNBTS-34/LNCELL-123

AC based integration:

PLMN-Bangalore/MRBTS-12/LNBTS-34/LNCELL-123

Ericsson (all RATs) with In AC based integration, the delimiters between Managed Objects (MOs)
retainNativeDNFor- and their values are changed.
mat set to False
Root prefix is changed from:

• Subnetwork-ONRM_ROOT to ENM-<RegionName> for ENM

• E3SUB in case of OSSRC 3G/4G
• E2SUB in case of OSSRC 2G

Root element will contain the sub-region name.

For example:

Direct integration OSS ENM:

SubNetwork=SysRegion,MeContext=ABC001,ManagedElement=1,

ENodeBFunction=1,EUtranCellFDD=BBK0400AQW

AC based integration OSS ENM:

ENM-Mysore/SubNetwork-SysRegion/MeContext-ABC001/

ManagedElement-1/ENodeBFunction-1/EUtranCellFDD-BBK0400AQW

Direct Integration OSSRC 3G and 4G:

SubNetwork=SysRegion,MeContext=ABC001,

ManagedElement=1,
ENodeBFunction=1,EUtranCellFDD=BBK0400AQW

AC based integration OSSRC 3G and 4G:

EdenNet 21 © 2021 Nokia 16

EdenNet deployment with and without DN09273754 1-0 DN (Distinguished Name) format change
AC: Differences in data representation,
visualization, and behavior

Vendor Change

E3SUB-Mysore/SubNetwork-SysRegion/MeContext-ABC001/
ManagedElement-1/ENodeBFunction-1/EUtranCellFDD-BBK0400AQW

Direct Integration OSSRC 2G:

SubNetwork=SysRegion,BSC=1,INTERNAL_CELL=BBK0400AQW

AC based integration OSSRC 2G:

E2SUB-Mysore/SubNetwork-SysRegion/BSC-ABC001/INTERNAL_
CELL-BBK0400AQW

Ericsson 2G, 3G, 4G, In AC based integration, root prefix is changed from:
and 5G with retainNa-
• Subnetwork=ONRM_ROOT to ENM=<RegionName> for OSS ENM
tiveDNFormat set to
• E3SUB in case of OSSRC 3G/4G
True
• E2SUB in case of OSSRC 2G

Root element will contain the sub-region name.

For example:

Direct integration OSS ENM:

SubNetwork=SysRegion,MeContext=ABC001,

ManagedElement=1,ENodeBFunction=1,EUtranCellFDD=BBK0400AQW

AC based integration OSS ENM:

ENM=Mysore,SubNetwork=SysRegion,MeContext=ABC001,

ManagedElement=1,ENodeBFunction=1,EUtranCellFDD=BBK0400AQW

Direct Integration OSSRC 3G and 4G:

SubNetwork=SysRegion,MeContext=ABC001,ManagedElement=1,

ENodeBFunction=1,EUtranCellFDD=BBK0400AQW

AC based integration OSSRC 3G and 4G:

E3SUB=Mysore,SubNetwork=SysRegion,MeContext=ABC001,

ManagedElement=1,ENodeBFunction=1,EUtranCellFDD=BBK0400AQW

Huawei (LTE) The root prefix is changed from H4GN to HNCGN. Root element con-
tains the sub-region name.

ENODEB and RADIO MOs are removed from the DN hierarchy.

For example:

Direct Integration:

H4GN-1/ENODEB30-12/ENODEB-1/RADIO-1/CELL-123

EdenNet 21 © 2021 Nokia 17

EdenNet deployment with and without DN09273754 1-0 DN (Distinguished Name) format change
AC: Differences in data representation,
visualization, and behavior

Vendor Change

AC based integration:

HNCGN-<Regionname>/ENODEB-12/CELL-123

Huawei 2G and 3G In AC based integration:

• Flat hierarchy is changed to actual hierarchy

• Delimiters between MOs and instance ids are changed
• Value of instance id is changed
• Root element with region name is introduced in DN.

For example:

Direct integration:

BSC6900UMTSNE=RNCNAME,CELL=CELLID_123

AC based integration:

HNCGN-<Regionname>/RNC-123/UCELL-123

Table 8: DN format change

Note: There are MOs that contain parameters with reference DN. These reference parame-
ter DNs takes the new DN format.

EdenNet 21 © 2021 Nokia 18

EdenNet deployment with and without DN09273754 1-0 CM topology hierarchy changes
AC: Differences in data representation,
visualization, and behavior

9 CM topology hierarchy changes

Ericsson LTE (for all type of LTE MO relations)

In AC based solution, all the relation objects are represented directly under cell objects. In direct
integration, all the relations are available under FreqRelation MOs.

For example:

Direct Integration → eNodebFunction → EutranCellFDD → EUtranFreqRelation → EUtranCell-

Relation

AC based Integration → eNodebFunction → EutranCellFDD → EUtranCellRelation

Ericsson 2G, 3G, 4G and 5G

With retainNativeDNFormat set as True, the CM topology hierarchy change is:

ENM=Mysore,SubNetwork=SysRegion,MeContext=ABC001,ManagedElement=1,ENodeBFunction=

1,EUtranCellFDD=BBK0400AQW,EUtranFreqRelation=345,EUtranCellRelation=AB56XO

With retainNativeDNFormat set as False, the CM topology hierarchy change is:

ENM-Mysore/SubNetwork-SysRegion/MeContext-ABC001/ManagedElement-1/

ENodeBFunction-1/EUtranCellFDD-BBK0400AQW/EUtranCellRelation-AB56XO

EdenNet 21 © 2021 Nokia 19

EdenNet deployment with and without DN09273754 1-0 Cell RET mapping file
AC: Differences in data representation,
visualization, and behavior

10 Cell RET mapping file

Cell RET mapping is an input file available offline in which the operators store the cell and associated
RET information. This file contains the RET DN which has the new DN format because of the DN
representation changes. Operators needs to manually change the existing cell_plan and cell-
ret mapping files.

In Direct integration, the cell name is taken as input from the cell-ret mapping file, but in AC based in-
tegration, operators need to define the cell DN instead of cell name.

For Nokia, cell name can be accepted, but the cell name must be unique in the network. For more in-
formation, contact Nokia technical support team.

RET mapping file examples for Nokia, Huawei, and Ericsson in the new format are as follows:

cell dn ret dn

HNCGN-NORTH/RAN-BA0441_RNC_BAC/ HNCGN-NORTH/NODEB-CL0934_1_U/
UCELL-12652 RETSUBUNIT-0+1

HNCGN-SOUTH/ENODEB-BA0WER0_GUL/ HNCGN-SOUTH/ENODEB-BA053098_GUL/
CELL-1 RETSUBUNIT-0+1

Table 9: Huawei

cell dn ret dn

E3SUB-Bangalore/SubNetwork-RREN1/MeCon- E3SUB-Bangalore/SubNetwork-RREN1/MeCon-
text-RREN1/ManagedElement-1/RncFunction-1/ text-UARBCO/ManagedElement-UARBCO/
UtranCell-2004AGKOSK Equipment-1/AntennaUnitGroup-2/AntennaN-
earUnit-2100/RetSubUnit-1

Table 10: Ericsson

cell dn ret dn

SubNetwork=RREN1,MeContext=RREN1, SubNetwork=RREN1,MeContext=UARBCO,

ManagedElement=1,RncFunction=1, ManagedElement=UARBCO,

UtranCell=2004AGKOSK Equipment=1,

AntennaUnitGroup=2,AntennaNearUnit=2100,

RetSubUnit=1

EdenNet 21 © 2021 Nokia 20

EdenNet deployment with and without DN09273754 1-0 Cell RET mapping file
AC: Differences in data representation,
visualization, and behavior

Table 11: Ericsson 3G and 4G with retainNativeDNFormat as True

Cell dn RET DN

PLMN-Bangalore/MRBTS-26009/LNBTS-123/LN- PLMN-Bangalore/MRBTS-26009/RET-2
CEL-234

Table 12: Nokia

EdenNet 21 © 2021 Nokia 21

EdenNet deployment with and without DN09273754 1-0 Plan provisioning functionalities in direct
AC: Differences in data representation, OSS and AC integration
visualization, and behavior

11 Plan provisioning functionalities in direct OSS and

AC integration
This chapter lists the difference in plan provisioning functionalities in direct OSS and AC based inte-
gration.

11.1 Plan name change in direct OSS and AC integration

Table 13: Plan name change describes the plan name change between direct OSS and AC integra-
tion.

Direct OSS integration AC integration

The plan name generated in EdenNet and The plan name generated in EdenNet is different from
pushed to OSS are the same. what is pushed to the OSS through AC mediation.

EdenNet generates only one plan across the inte-

grated OSSs and AC splits the plan according to the
OSS. The plan file name containing the OSS name is
changed to distinguish them per OSS in its file system.

For example:

EdenNet plan name: en_ac_ANR_Blacklisting_

and_Cleanup_LTE_2019_08_05_04_59_32_
408930.json

AC generated plan name: cluster_pol5enm_

GlobalDownload_e3gpp_1565006374079.xml

Table 13: Plan name change

11.2 Plan validation status

Table 14: Plan validation status describes how EdenNet checks the plan validity in direct OSS and AC
integrations.

Direct OSS integration AC integration

In EdenNet, Adapted modules and EdenNet In AC integration, EdenNet and AC check the validi-
modules creates plan, which may contain in- ty of plans generated by the modules. If the entry for
valid parameter information. EdenNet pushes any MO is not correct in the plan file, EdenNet will
the plan to the OSS and let it fail with valida- filter out those invalid entries. EdenNet then contin-
tion failure step at the OSS.

EdenNet 21 © 2021 Nokia 22

EdenNet deployment with and without DN09273754 1-0 Plan provisioning functionalities in direct
AC: Differences in data representation, OSS and AC integration
visualization, and behavior

Direct OSS integration AC integration

ues to activate the plan with validated entries at the

OSS.

The operator can control this behavior using the

settings in EdenNet. For more information, contact
Nokia technical support team.

Table 14: Plan validation status

11.3 Split plan at OSS level

Table 15: Split plan at OSS level describes the splitting of plan at OSS level in direct OSS and AC inte-
gration.

Direct OSS integration AC integration

EdenNet creates the plan per OSS level and EdenNet creates one plan per module execution
these plans are visible in the EdenNet Provi- containing all the changes belonging to all OSS
sioning Logs tab in GUI. (regions) integrated in the AC mediation layer. AC
splits the combined plan per OSS level.

Table 15: Split plan at OSS level

EdenNet 21 © 2021 Nokia 23

EdenNet deployment with and without DN09273754 1-0 KPI chart per OSS
AC: Differences in data representation,
visualization, and behavior

12 KPI chart per OSS

Table 16: KPI chart per OSS describes the viewing of KPI chart per OSS in direct OSS and AC inte-
grations.

Direct OSS integration AC integration

The operator can view the KPI chart per OSS The operator cannot view the KPI chart per OSS
(region level) integrated in EdenNet. level. The operator can view one chart for all re-
gions that belong to same the vendor (aggregated
data) in one single graph.

Table 16: KPI chart per OSS

EdenNet 21 © 2021 Nokia 24

EdenNet deployment with and without DN09273754 1-0 Configuring user label
AC: Differences in data representation,
visualization, and behavior

13 Configuring user label

Table 17: Configuring user label describes the support for user label configuration in direct OSS and
AC integrations.

Direct OSS integration AC integration

EdenNet supports the configuration of user la- Configuration of user label is not supported.
bel for the cells.

Table 17: Configuring user label

Note: Valid for Ericsson.

EdenNet 21 © 2021 Nokia 25

EdenNet deployment with and without DN09273754 1-0 Online metadata retrieval
AC: Differences in data representation,
visualization, and behavior

14 Online metadata retrieval

Table 18: Online metadata retrieval describes the online metadata retrieval in direct OSS and AC inte-
gration.

Direct OSS integration AC integration

EdenNet fetches and stores the CM metadata EdenNet does not fetch the CM metadata online
directly from the OSS system. from the OSS. It builds and stores the information
based on the offline CM metadata available in AC.
Note: Valid for Nokia and Ericsson
(3G and 4G).

Table 18: Online metadata retrieval

EdenNet 21 © 2021 Nokia 26

EdenNet deployment with and without DN09273754 1-0 CM MO filtering and scheduling
AC: Differences in data representation,
visualization, and behavior

15 CM MO filtering and scheduling

Table 19: CM MO filtering and scheduling describes the MO specific CM filtering and scheduling in di-
rect OSS and AC integrations.

Direct OSS integration AC integration

EdenNet does the MO based CM upload at EdenNet does the CM upload for the whole region
defined intervals. (not MO level) at every defined interval (default is 6
hours). To change the CM upload frequency, contact
For example:
Nokia technical support team. This is valid for Erics-
• eNodeBs and RNCs - every 6 hours son and Huawei.
• Cell - every 4hours
Nokia data is always in real time synch with AC lay-
• Relation - every 2 hours
er through notifications and with bulk CM upload
once in a day.

Table 19: CM MO filtering and scheduling

Note: Nokia NetAct sends the notification for every create, update, and delete operation of
CM managed objects, even if the change is triggered by an EdenNet user or not. In this way,
EdenNet and AC is always in sync with NetAct. EdenNet triggers full CM upload from NetAct
with the help of AC once in 24 hours. This will benefit the operators and each instance of the
module will run with up to date data. There is no need to parse the complex feedback logs
generated during plan provisioning that is initiated via raccli interface in direct OSS integra-
tion.

EdenNet 21 © 2021 Nokia 27

EdenNet deployment with and without DN09273754 1-0 External cell handling
AC: Differences in data representation,
visualization, and behavior

16 External cell handling

AC based EdenNet integration is more network aware and smart. It has the functionality of Border
Area Management (BAM) that enables the management of neighbors and external cells across node
level and region level boundaries.

The EdenNet and Adapted modules need not create or modify regional external cells and add the
cell information while creating or modifying relations. These modules have to put the actual target
or neighbor cell dn in the adjacentCell parameter or targetCelldn parameter (non-network),
while creating or modifying relations. There is no need for any other mandatory parameters unless the
operator specifically asks for it.

Note: The adjacentCell parameter is used for non-Nokia vendors and targetCelldn
parameter for Nokia.

Hence, the regional external cells are not stored in the EdenNet database directly. If any module wants
to fetch the regional external cells from the AC CM layer, they can query using SDK APIs.

Table 20: External cell handling describes the external cell handling in direct OSS and AC integration.

Direct OSS integration AC integration

In EdenNet, only ANR module creates external EdenNet modules deal with changes in the cell and
cells that belong to the same OSS region. creates or modifies the relation MOs but not the ex-
ternal cells.

EdenNet sends the plan to AC layer and AC adds

the external cell handling, identifies the exact neigh-
bor cell reference, and sends to the OSS. The exter-
nal cell with BAM functionality is moved from Eden-
Net to AC mediation layer.

Table 20: External cell handling

16.1 Global external cells

For all the neighbor relations pointing to cells that are not available in the AC layer across integrated
regions, AC creates global external cells (SUBNM-VIM layer) and the association between relations
and these external cells under SUBNM-VIM.

EdenNet directly stores all the global external cells in it's database. For example, EXUCE is the MO
type to represent 3G global external cells.

EdenNet 21 © 2021 Nokia 28

EdenNet deployment with and without DN09273754 1-0 Handling of special characters in DN
AC: Differences in data representation,
visualization, and behavior

17 Handling of special characters in DN

Table 21: DN special characters describes the handling of special characters in DN for direct OSS and
AC integrations.

Direct OSS integration AC integration

There is no specific handling of the special In AC integration, forward slash '/ ' has a special
character, forward slash '/' in DN. meaning and it can be present as the MO instance
identifier value. EdenNet replaces '/ ' with '|\\' value.

Table 21: DN special characters

EdenNet 21 © 2021 Nokia 29

EdenNet deployment with and without DN09273754 1-0 3GPP MO names of reference DN
AC: Differences in data representation, parameters
visualization, and behavior

18 3GPP MO names of reference DN parameters

Table 22: 3GPP MO names describes how the reference DN parameters values are used in direct
OSS and AC integrations.

Direct OSS integration AC integration

EdenNet does not change the reference DN The reference DN parameters values will contain
parameter values. the 3GPP MO names instead of vsData prefixes.

Table 22: 3GPP MO names

Note: Valid for Ericsson (2G, 3G, 4G, and 5G).

EdenNet 21 © 2021 Nokia 30

EdenNet deployment with and without DN09273754 1-0 PLMN identity
AC: Differences in data representation,
visualization, and behavior

19 PLMN identity
As per the 3GPP specification, MCC and MNC (as part of PLMN identity) are represented in string, but
EdenNet treats them as integer. If an operator or nearby regions have MNC as both 001 and 01, then
EdenNet treats them as 1. This is the existing behavior in EdenNet with direct OSS and AC based in-
tegrations. However, the new CM AC layer of EdenNet treats MNC and MCC as string.

EdenNet 21 © 2021 Nokia 31

EdenNet deployment with and without DN09273754 1-0 CM Operation logs
AC: Differences in data representation,
visualization, and behavior

20 CM Operation logs
CM Operation logs describes the difference in the CM operation log process for direct OSS and AC
based integrations.

Direct OSS integration AC integration

The CM upload and download provision opera- The CM operations towards OSS can be viewed
tions that directly interface with the EMS/OSS are in the AC CM Operation Manager UI.
available in the region specific cm.cache and cm.
main logs present in the EdenNet VMs. So, the
operator knows about the steps of the operation
and can troubleshoot in case of failure.

Table 23: CM Operation logs

EdenNet 21 © 2021 Nokia 32

EdenNet deployment with and without DN09273754 1-0 NE version compatibility
AC: Differences in data representation,
visualization, and behavior

21 NE version compatibility
Table 24: NE version compatibility describes EdenNet's support for non-compatible NE versions in di-
rect OSS and AC based integrations.

Direct OSS integration AC based integration

In direct OSS integration, if the operator has up- In AC based integration, the support for non-com-
graded to a non-compatible NE version, but there patible NE version is possible by mapping to the
are no changes related to EdenNet modules and latest EdenNet version to avoid any functionality
functionality, then EdenNet will continue to sup- breaks. Contact Nokia technical support team to
port the non-compatible NE version till the official configure this mapping.
compatible EdenNet version is available. This is
because the CM metadata is fetched online from
Ericsson and Nokia EMS/OSS.

Table 24: NE version compatibility

EdenNet 21 © 2021 Nokia 33

EdenNet deployment with and without DN09273754 1-0 Glossary
AC: Differences in data representation,
visualization, and behavior

22 Glossary
Table 25: Glossary describes the common terms used in EdenNet AC integrations.

Term Description

AC Advanced Configurator

BAM Border Area Management

CM Configuration Management

DB EdenNet Database

DN Distinguished Name

EMS Element Management System

KPI Key Performance Indicator

LMS Layer Management Strategy

MO Managed Object

NDA Non-Disclosure Agreement

OSS Operations Support System

PCE Parameter Consistency and Enforcement

RET Remote Electrical Tilt

RAT Radio Access Technology

SDK Software Development Kit

UI User Interface

Table 25: Glossary

EdenNet 21 © 2021 Nokia 34