LTE Object modeling in Optimizer
RL10/RL15TD/RL20/RL25TD/RL30
Version 1.41 – 10-May-2011
Daiju C A
Bangalore
For internal use
1
© Nokia Siemens Networks
LTE Object Modelling in Optimizer / Daiju C A / 28-02-2011
Introduction
• Modelling is inline with implementation for RL10/RL15TD/RL20
• Modelling for RL25TD/RL30 is ready for implementation
For internal use
2
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
RL10 LTE model (Optimizer 3.0)
PLMN
MRBTS is a child of PLMN in the
network modeling. But in
Optimizer, we have grouped all
MRBTS in one PLMN under the
corresponding OMS for better
visualization
1..1
OMS
1..N
1..N
MRBTS
1..1
SITE
1..1
LNBTS
LTE ANTE instances
are present only in
Optimizer unlike 2G
and 3G
1..3
LNCEL
0..98
1..2
LCAL
ADJLL
Present in CM and in Optimizer
For internal use
3
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
1..1
Present only in Optimizer
ANTE
RL15TD/RL20 LTE model (Optimizer 3.0 CD1)
PLMN
If there are imported
PLMN (s) , then there will
be 1 OMS per PLMN
1..1
OMS
1..N
MRBTS
SITE
1..N
LNRC
0..200
In an Optimizer plan, this additionally
represents an item in
adjEnbIpAddressMap present in CM
ADIPNO; Also valid for RL10 starting
from Optimizer 3.0 CD1
1..1
0..32
LNBTS
LNADJ
1..3
Models an item present
in pciIpAdrMap
parameter of CM MOC
LNBTS
LNCEL
0..98
1..2
LCAL
ADJLL
Present in CM and in Optimizer
For internal use
4
© Nokia Siemens Networks
Relevant TDD
parameters are
supported
Present only in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
1..1
ANTE
Impacted in Optimizer 3.0CD1
RL25TD/RL30 LTE model
PLMN
1..1
OMS
1..N
SITE
MRBTS
1..N
LNRC
1..1
0..64
LNBTS
0..200
LNADJ
1..6
0..32
0..16
LNCEL
Sum of number of instances
of LNREL and ADJLL can’t be
more than 389
0..389
0..32
0..389
LNHOIF
1..2
1..1
LNRELW
LNRELG
LNREL
Present in CM and in Optimizer
For internal use
5
© Nokia Siemens Networks
ADJLL
Present only in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
LCAL
ANTE
Impacted in Optimizer 3.0CD3
LTE Antenna – Optimizer Modelling details (RL10)
MRBTS
ANTE instances are created
for every ANTL instance. Also
ANTL parameters longitude,
latitude, bearing and
userDefinedState are copied
to the corresponding ANTE
instance.
1..1
1..1
LNBTS
BTSSC
1..3
LNCEL
lcrId
1..1
LCEL
ANTL
1..2
antlIdList
1..2
latitude
longitude
bearing
userDefinedState
1..1
LCAL
LCAL instances are created for every
relation between LNCEL and ANTL
fulfilling the condition : LNCEL.lcrId ==
LCEL.$instance && LCEL.antlIdList
contains ANTL.$instance
For internal use
6
© Nokia Siemens Networks
ANTE
1..1
These elements are present ONLY in CM but used for
deriving LCAL and ANTE as part of CM Refresh
Present in CM and in Optimizer
Present only in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
LTE Antenna – Optimizer Modelling details (RL15TD and
above)
ANTE instances are
created for every ANTL
instance. Also ANTL
parameters longitude,
latitude, bearing and
userDefinedState are
copied to the
corresponding ANTE
instance.
MRBTS
1..1
1..1
LNBTS
BTSSCL
1..3
LNCEL
1..1
lcrId
LCELL
1..2
ANTL
latitude
longitude
bearing
userDefinedState
resourceIdList
1..2
1..1
LCAL
LCAL instances are created for
every relation between LNCEL and
ANTL fulfilling the condition :
LNCEL.lcrId == LCEL.$instance
&& LCEL.resourceIdList contains
ANTL.$instance
For internal use
7
© Nokia Siemens Networks
ANTE
1..1
These elements are present ONLY in CM but used for
deriving LCAL and ANTE as part of CM Refresh
Present in CM and in Optimizer
Present only in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Optimizer Modelling : Intra LTE adjacency for
RL10/RL15TD/RL20
Neighbouring eNB
object contains information
about Global eNB ID of
Neighbouring eNB and other
Neighbouring eNB related
parameters.
LNBTS
1..3
0..32
Neighbouring LTE cell
object represents Neighbouring
LTE cell which is served by its
parent LNADJ instance. This
MOC contains served cell
information of Neighbouring
cell received during X2
establishment.
LNCEL
adjCelInfoL
LNADJ
1..3
0..98
LNADJL
Intra LTE adjacency
ADJLL instance is created for
every LNADJL instance + other
cells under the same LNBTS.
multiplicity: 98 (=32*3+2).
Neighboring Cell Information
(adjCelInfoL in PDDB)
Parameter for List of
neighboring cell’s Unique EUtran cell identifiers, multiplicity:
98 (=32*3+2).
Read only for NetAct
0..98
ADJLL
Object/parameter created/modified/deleted by eNB. These elements are not present in Optimizer but used for
deriving ADJLL as part of CM Refresh
Present in CM and in Optimizer
Present only in Optimizer
For internal use
8
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Optimizer Modelling : Central ANR support (RL10)
To support central ANR,
adjEnbIpAddressMap parameter of
ADIPNO is populated with details of
neighbouring eNB (s) corresponding to
different entries in neighbouringeNBDNs
LNBTS
neighbouringeNBDNs
1..3
LNCEL
adjCelInfoL
0..1
ADIPNO
adjEnbIpAddressMap
Adjacent eNB configuration
map (adjEnbIpAddressMap)
multiplicity: 32
-Adjacent eNB IP address (not
populated by Optimizer)
-Macro eNB Id Of Adjacent ENB
-MCC Of Adjacent ENB
-MNC Of Adjacent ENB
0..98
ADJLL
LNADJ creation is started when SCTP is established.
Global eNB ID information is copied to LNADJ instance from ADIPNO
instance, where it is specified together with IP address of
neighbouring eNB.
Present only in CM
Present in CM and in Optimizer
Establishment of SCTP will trigger also X2 setup procedures and
when X2 is setup successfully and neighbour cell information has
been received, then for each of LTE cells served by neighbouring
eNB an instance of LNADJL shall be created to represent one
neighbouring LTE cell.
Present only in Optimizer
For internal use
9
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Optimizer Modelling : Central ANR support
(RL15TD/RL20)
Target eNB.
To support central ANR,
adjEnbIpAddressMap parameter of
ADIPNO is populated with details of
neighbouring eNB (s) corresponding to
different entries in neighbouringeNBDNs
LNBTS
neighbouringeNBDNs
LNBTS
0..32
1..3
LNCEL
adjCelInfoL
LNADJ
0..1
ADIPNO
adjEnbIpAddressMap
0..98
Actual LNADJ (s) are
present in both CM &
Optimizer. While purely
planned LNADJ (s) are
present only in Optimizer
ADJLL
LNADJ creation is started when SCTP is established.
Global eNB ID information is copied to LNADJ instance from ADIPNO
instance, where it is specified together with IP address of
neighbouring eNB.
Present only in CM
Present in CM and in Optimizer
Establishment of SCTP will trigger also X2 setup procedures and
when X2 is setup successfully and neighbour cell information has
been received, then for each of LTE cells served by neighbouring
eNB an instance of LNADJL shall be created to represent one
neighbouring LTE cell.
Present only in Optimizer
For internal use
10
© Nokia Siemens Networks
Adjacent eNB configuration
map (adjEnbIpAddressMap)
multiplicity: 32
-Adjacent eNB IP address (not
populated by Optimizer)
-Macro eNB Id Of Adjacent ENB
-MCC Of Adjacent ENB
-MNC Of Adjacent ENB
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Optimizer Modelling : Central ANR support
(RL25TD/RL30)
LNBTS
Target eNB.
LNBTS
0..64
X2
1..6
LNADJ
Optimizer will set only the non-network
parameter “target BTS DN” while
creating LNADJ (s). Maximum of 32
LNADJ (s) can be created for X2 while
maximum of 64 LNADJ (s) can be
created for S1
Present only in CM
Present in CM and in Optimizer
LNCEL
0..389
ADJLL
ADJLL instances are created
corresponding to LNADJL (s) +
other cells under the same eNB for
which there is NO corresponding
LNREL present.
Present only in Optimizer
For internal use
11
© Nokia Siemens Networks
Sum of number of instances
of LNREL and ADJLL can’t be
more than 389
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
0..389
LNREL
LNREL and ADJLL will be
derived from
EutranRelation so that
algorithms can rely on
EutranRelation.
LTE Intra system adjacency : Modelling in Configurator
(RL25TD/RL30)
new
Target eNB
When X2 link cannot be
successfully established, LNADJ
is used for S1 HO.
for S1
LNBTS
Information in LNADJ X2 Link
Status parameter that is set by
system.
S1
MME
LNCEL
LNADJ and LNADJL used for both
X2 and S1 HO. Operator can
create LNADJ and LNADJL.
LTE724: ADIPNO no longer used.
But operator can create via plan
LNADJ and LNADJL. adjCellInfoL
no longer supported.
PLMN
S1
LTE782: New object LNREL.
Target eNB
MRBTS
for X2
1..1
X2
LNBTS
LNBTS
LNCEL
0..64
1..6
LNADJ
1..6
LNADJL
Source
eNB
1..1
0..16
ADIPNO
LNADLP
adj eNB list
LNCEL
0..130
adjCellnfoL
0…389
LTE Neighbor Relation
A new MOC LNREL is introduced
which represents properties of
LTE neighbour relations. Max:
6*64 + 5 = 389.
LNREL
For internal
source
: use
CM LTE Adjacencies slide set from Maija Kaare
12
© Nokia Siemens Networks
Object/parameter created/modified/deleted by user
Presentation
/ Author /inDate
LTE
Object Modelling
Optimizer/ Daiju C A / 28-02-2011
Object/parameter created/modified/deleted by eNB
LTE Intra system adjacency : Border area support in
Configurator (RL25TD/RL30)
NetAct region
border
Target eNB
for S1
External ENodeB
Function
LNBTS
S1
LNCEL
PLMN
EXENBF
Target eNB
for X2
S1
MRBTS
EXEUCE
1..1
X2
LNBTS
EXENBF
X2
LNBTS
EXEUCE
LNCEL
0..64
LNADJ
External
EUtran Cell
1..6
1..6
LNCEL
LNADJL
0…389
LNREL
For internal
source
: use
CM LTE Adjacencies slide set from Maija Kaare
13
© Nokia Siemens Networks
Object/parameter created/modified/deleted by user
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Object/parameter created/modified/deleted by eNB
Source eNB
LTE Intra system adjacency : Border area support in
Optimizer
PLMN
EXCENBF
0..n
External Collection of
ENodeB Function
External ENodeB
Function
EXENBF
0..6
External EUtran Cell
EXEUCE
Creation of EXENBF/EXEUCE is done when there is a LNADJ/LNADJL present
in the CM plan (imported by user for S1 HO) with corresponding target eNB/cell not known.
For internal use
14
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Optimizer Modelling : inter RAT HO support to WCDMA
(RL25TD/RL30)
LNBTS
Optimizer will set only the nonnetwork parameter “target cell
DN” while creating LNRELW
(s). LNRELW is a non-network
MOC and CM plan prepare
takes care of creating/updating
adjWInf parameter and
LNADJW
1..6
LNCEL
0..32
LNRELW
Present only in CM
Present in CM and in Optimizer
CM will create LNRELW
instance for every LNADJW
id present in adjWInfL.
Present only in Optimizer
For internal use
15
© Nokia Siemens Networks
How the
blacklisted cell
information is
brought to
Optimizer?
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Nu of LNADJW
needs to be
derived from
LNRELW
Optimizer Modelling : inter RAT HO support to GSM
(RL25TD/RL30)
LNBTS
Optimizer will set only the nonnetwork parameter “target cell
DN” while creating LNRELG (s).
LNRELG is a non-network MOC
and CM plan prepare takes care
of creating/updating adjGInf
parameter and LNADJG
1..6
LNCEL
0..32
LNRELG
Present only in CM
Present in CM and in Optimizer
CM will create LNRELG
instance for every LNADJG
id present in adjGInfL.
Present only in Optimizer
For internal use
16
© Nokia Siemens Networks
How the
blacklisted cell
information is
brought to
Optimizer?
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Nu of LNADJG
needs to be
derived from
LNRELG
PLMN
• PLMN acronym stands for Public Land Mobile Network.
• In real network, PLMN is identified using it’s MCC and
MNC.
• In NetAct, PLMN represents the NetAct cluster and
typically acts as a root MOC for all network elements
directly connected to this NetAct Cluster.
• Default value of PLMN for the same regional NetAct
cluster is PLMN-PLMN
– Note: The PLMN for directly integrated NWI3 elements is
configurable (see /etc/opt/nokia/oss/umanw3/conf/n3tuplmx.cf).
• Value for imported PLMN (s) typically follow the name
format : PLMN-<Imported cluster name>
• PLMN is imported to Optimizer as part of CM Refresh.
For internal use
17
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
OMS
• OMS models a pseudo controller to provide a grouping of
all eNB(s) present under one PLMN (or NetAct cluster).
• This MOC is modelled ONLY in a optimizer.
• Parent MOC for OMS is PLMN.
• UI name for this MOC is “LTE-NW”
• OMS is created automatically as part of CM Refresh.
• Optimizer user can’t create new OMS instance manually.
• There is only one OMS instance present in Optimizer 3.0
and this corresponds to PLMN-PLMN.
• In Optimizer 3.0 CD1, OMS will be created for each PLMN
instance present in the network.
For internal use
18
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
MRBTS
• MRBTS acronym stands for Multi Radio BTS Site.
• In network model, parent for this MOC is PLMN.
• In Optimizer model, MRBTS will be a child of OMS.
• There can be any number of MRBTS under one PLMN
• MRBTS is created by operator using CM Editor or by importing RAML
plan file.
• MRBTS present in CM plan can be imported to Optimizer plan.
• MRBTS present in CM actual configuration is imported to Optimizer
actual configuration as part of CM Refresh.
• Optimizer allows the modification of MRBTS parameters but does not
support the creation/deletion of MRBTS.
• Modifications in MRBTS can be exported or merged back to CM Plan.
For internal use
19
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNBTS
• LNBTS models an eNB.
• Parent MOC for LNBTS is MRBTS.
• LNBTS objects are created by operator using CM Editor of by
importing RAML plan file.
• Cardinality of MOC LNBTS is 1 per MRBTS.
• SITE associated with LNBTS is used for visualization of LTE cells in
eNB.
• eNB global ID == MCC + MNC + (macro) eNB ID
• LNBTS present in CM plan can be imported to Optimizer plan.
• LNBTS present in CM actual configuration is imported to Optimizer
actual configuration as part of CM Refresh.
• Optimizer allows the modification of LNBTS parameters but does not
support the creation/deletion of LNBTS.
• Modifications in LNBTS can be exported or merged back to CM Plan.
• Currently LNBTS id is same as MRBTS id.
For internal use
20
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNBTS – Activation parameters
• Activation of “Inter frequency HO“ feature
– Operator needs to set the feature activation flag actIFHO to enable
the intra LTE inter frequency HO. This is taken care by the
Configurator plan-prepare.
• Activation of "HO to WCDMA" feature
– Operator needs to set the feature activation flag actHOtoWcdma to
enable the HO to WCDMA cells. This is taken care by Configurator
plan-prepare.
For internal use
21
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNCEL
• LNCEL models a LTE cell.
• Parent MOC for LNCEL is LNBTS.
• LNCEL objects are created by operator using CM Editor or by
importing RAML plan file.
• Cardinality of MOC LNCEL is up to
– 3 per LNBTS (for RL10/RL15TD/RL20)
– 6 per LNBTS (from versions RL25TD/RL30 onwards)
• LNCEL present in CM plan can be imported to Optimizer plan.
• LNCEL present in CM actual configuration is imported to Optimizer
actual configuration as part of CM Refresh.
• Optimizer allows the modification of LNCEL parameters but does not
support the creation of LNCEL.
• Modifications in LNCEL can be exported or merged back to CM Plan.
For internal use
22
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNADJ (RL10/RL15TD/RL20)
• LNADJ models a target eNB corresponding to X2 HO.
• Parent MOC for LNADJ is LNBTS.
• Contains information about Global eNB ID of neighbouring eNB.
• LNADJ objects are created and maintained by eNB
• Read-only in NetAct and BTS SM
• LNADJ present in actual configuration is imported to Optimizer actual
configuration as part of CM Refresh.
• Optimizer internally supports MOC LNADJ in plan Configuration.
• Each Item in the adjEnbIPAddressMap parameter of ADIPNO can be
imported to Optimizer Plan as LNADJ.
• Optimizer creates LNADJ (s) automatically as part of central ANR.
• Cardinality is up to 32 per LNBTS
• LNADJ instances are NOT persisted in eNB.
For internal use
23
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNADJ (RL25TD/RL30)
• LNADJ models a target eNB for both X2 and S1 HO
• Contains information about Global eNB ID of neighbouring eNB.
• LNADJ parameter C-Plane IP Address Control indicates whether the
LNADJ created is for X2 HO or S1 HO
– [Default] oamControlled (0) means X2
– 1 means S1
• LNADJ present in actual configuration is imported to Optimizer actual
configuration as part of CM Refresh.
• LNADJ objects can be created by both eNB as well as operator.
• eNB will also create LNADJ corresponding to PCI (s) reported by UE.
• LNADJ present in CM plan can be imported to Optimizer plan.
• Optimizer creates LNADJ (s) automatically as part of central ANR.
• LNADJ (s) in Optimizer plan can be exported or merged back to
Configurator plan.
• Optimizer needs to set ONLY the non-network parameter Target BTS
DN and the rest of the parameters will be set by CM plan prepare.
• Cardinality is up to 64 per LNBTS
• LNADJ instances are persisted in eNB.
For internal use
24
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNADJL
• Models a target LTE cell which is served by its parent LNADJ instance
• Parent MOC for LNADJL is LNADJ
• Optimizer does not model LNADJL
• In RL10/RL15TD/RL20 :
– This MOC contains served cell information of neighbouring cell received
during X2 establishment
– LNADJL objects are created and maintained by eNB
– Read-only in NetAct and BTS SM
– Cardinality is up to 3 per LNADJ
• In RL25TD/RL30 :
– This MOC can corresponds to both X2 HO as well as S1 HO.
– Cardinality is up to 6 per LNADJ (Note: If eNB is connected to non NSN
eNB (s), then the cardinality can be higher)
– LNADJL corresponding to X2 HO is created by eNB.
– LNADJL corresponding to S1 HO needs to be created by operator
– eNB will also create LNADJL corresponding to PCI (s) reported by UE.
For internal use
25
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
LNCEL - Neighbouring Cell Information
(RL10/RL15TD/RL20)
• In the Radio Network modelling,
– adjCellInfoL Parameter holds the neighbouring LNCEL information
– This parameter is created/modified by system
– Each element of the list will correspond to one neighbouring cell, and shall
contain only information to identify cell in database in unique way
– A list of neighbouring cells represented by pointer to LNADJL object or to
the other LNCEL(s) under the same LNBTS
– Maximum number of neighbouring LTE cells is 32*3+2 =98
• In Optimizer
– MOC ADJLL models the intra LTE adjacencies between two LTE cells.
Currently there is no restriction made between intra LTE intra frequency
adjacencies and intra LTE inter frequency adjacencies.
For internal use
26
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
ADJLL (RL10/RL15TD/RL20)
• ADJLL models an intra LTE adjacency.
• ADJLL is an Optimizer internal MOC.
• Parent MOC for ADJLL is LNCEL.
• In Optimizer, there is no restriction made between intra
LTE intra frequency adjacencies and intra LTE inter
frequency adjacencies.
• As part of CM Refresh, ADJLL instances are created
under the LNCEL corresponding to every LNADJL
instances and other cells present under the corresponding
parent LNBTS.
• Optimizer does not support the exchange of ADJLL (s)
present in plan configuration.
For internal use
27
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNREL (RL25TD/RL30)
• LNREL models the intra LTE neighbour relation.
• Unlike ADJLL, LNREL is present in both Radio Network model as well as in
the Optimizer model
• LNREL can get created in two ways in the eNB:
– eNB creates LNREL for every PCI (s) reported by UE.
– Operator can create LNREL using CM Editor or by importing RAML plan file.
• It is possible that there is NO LNREL instance corresponding to LNADL or
corresponding to other cells under the same eNB till the UE reports the
corresponding PCI.
– Note : Optimizer will create ADJLL corresponding to the above mentioned LNADL
(s) and other cells under the same eNB
• eNB will not create LNREL if the corresponding PCI is blacklisted using the
•
•
•
•
•
blackListHOL parameter of LNCEL.
LNREL will have HO KPI (s) corresponding to it.
LNREL present in CM plan can be imported to Optimizer plan.
LNREL present in CM actual configuration is imported to Optimizer actual
configuration as part of CM Refresh.
Optimizer allows the modification of LNREL parameters but does not support
the creation/deletion of LNREL.
Modifications in LNREL can be exported or merged back to CM Plan.
For internal use
28
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
ADJLL (RL25TD/RL30)
• ADJLL models an intra LTE adjacency.
• ADJLL is an Optimizer internal MOC.
• Parent MOC for ADJLL is LNCEL.
• As part of CM Refresh, ADJLL instances are created
under the LNCEL corresponding to LNADJL (s) and other
cells for which there is NO corresponding LNREL.
• Optimizer does not support the exchange of ADJLL (s)
present in plan configuration.
For internal use
29
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LCAL
• LCAL is an Optimizer internal MOC
• LCAL is similar to GCAL/WCAL in 2G/3G
• LCAL models the relation between LNCEL and ANTE fulfilling the condition:
(RL10)
LNCEL.lcrId == LCEL.$instance &&
LCEL.antlIdList contains ANTL.$instance
• LCAL models the relation between LNCEL and ANTE fulfilling the condition:
(>RL10)
LNCEL.lcrId == LCEL.$instance &&
LCEL.resourceIdList contains ANTL.$instance
• During CM Refresh or plan import,
– Optimizer derives a LCAL instance out of the relation between LNCEL
and ANTL instance (associated to a LCEL/LNCEL instance) and stores it
in optimizer database. Please note that derived LCAL instance is present
only in optimizer database and not in Configurator database.
For internal use
30
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LCEL
• LCEL models local cell corresponding to one LTE cell
• Optimizer does not model this MOC
• LCEL contains parameters related to
– Associated ANTL id list
• LCEL instances are created by operator using CM Editor
of by importing RAML plan file.
• There is one to one relation between LNCEL and LCEL
LNCEL.lcrId == LCEL.$instance
For internal use
31
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
ANTL/ANTE
• ANTL models an ANTenna Line object.
• ANTL holds the following Optimizer relevant non-network
parameters:
– Antenna Latitude
– Antenna Longitude
– Antenna Bearing
– UserDefinedState
• During CMRefresh, optimizer derives an ANTE instance
out of ANTL instance (associated to a LCEL/LNCEL
instance) and stores it in optimizer database. Please note
that derived ANTE instance is present only in optimizer
database and not in Configurator database.
ANTE with lowest id is considered as the main antenna
For internal use
32
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
EXCENBF (RL25TD/RL30)
• EXCENBF models the collection of all external ENodeB
function (s).
• EXCENBF present in CM plan can be imported to
Optimizer plan.
• EXCENBF present in CM actual configuration is imported
to Optimizer actual configuration as part of CM Refresh.
For internal use
33
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
EXENBF (RL25TD/RL30)
• EXENBF models the external ENodeB function.
• EXENBF is created by Configurator in the following case:
– When LNADJ points to a target eNB which is not present in CM.
• EXENBF present in CM plan can be imported to Optimizer
plan.
• EXENBF present in CM actual configuration is imported to
Optimizer actual configuration as part of CM Refresh.
• Parameters present in EXENBF:
– MCC
– MNC
– C-Plane IP address
– C-Plane IP address control
– Name
– Optional enum parameter xxx: FDD (0), TDD (1), no default
For internal use
34
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
EXEUCE (RL25TD/RL30)
• EXEUCE models the external EUtran Cell.
• EXEUCE is created by Configurator in the following case:
– When LNADJL points to a target EUtran Cell which is not present in CM.
• EXEUCE present in CM plan can be imported to Optimizer plan.
• EXEUCE present in CM actual configuration is imported to Optimizer
actual configuration as part of CM Refresh.
• Parameters present in EXEUCE:
– cell identity
– PLMN list
– EARFCN DL
– PCI
– TAC
– LCR ID
For internal use
35
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNRELW (RL25TD/RL30)
• LNRELW models the neighbour relation from LTE cell to
WCDMA cell.
• LNRELW is modelled in Optimizer and in Configurator.
• LNRELW is part of the Radio network modelling starting
from RL35TD/RL40
• LNRELW present in CM plan can be imported to
Optimizer plan.
• LNRELW present in CM actual configuration is imported to
Optimizer actual configuration as part of CM Refresh.
• Optimizer supports the creation of LNRELW.
• LNRELW can be exported or merged back to CM Plan.
For internal use
36
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNRELG (RL25TD/RL30)
• LNRELG models the neighbour relation from LTE cell to
GSM cell.
• LNRELG is modelled in Optimizer and in Configurator.
• LNRELG is part of the Radio network modelling starting
from RL35TD/RL40
• LNRELG present in CM plan can be imported to Optimizer
plan.
• LNRELG present in CM actual configuration is imported to
Optimizer actual configuration as part of CM Refresh.
• Optimizer supports the creation of LNRELG.
• LNRELG can be exported or merged back to CM Plan.
For internal use
37
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
LNHOIF (RL25TD/RL30)
• LNHOIF models the inter-frequency HO related parameters.
• Parent MOC for LNHOIF is LNCEL.
• LNHOIF objects are created by operator using CM Editor or by
importing RAML plan file or by Optimization Algorithms.
• Cardinality of MOC LNHOIF is up to 16 per LNCEL.
• LNHOIF present in CM plan can be imported to Optimizer plan.
• LNHOIF present in CM actual configuration is imported to Optimizer
actual configuration as part of CM Refresh.
• Optimizer creates LNHOIF instances automatically as part of LNRC
creation (ANR-OAM Extension). This needs to be done if LNHOIF is
not present already and when the LNRC points to a target LNCEL with
different frequency from that of source LNCEL.
• LNHOIF created can be exported or merged back to CM Plan.
For internal use
38
© Nokia Siemens Networks
Present only in CM
Present in CM and in Optimizer
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
Present only in Optimizer
For internal use
39
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011
source : 3GPP TS 36.300
Version History
Date
11-Feb-2011
Version
1.0
Remarks
• 1st version of Optimizer LTE model for RL25TD/RL30.
• Slides are updated to reflect the implementation status of
RL10/RL15TD/RL20 model in Optimizer.
14-Feb-2011
1.1
• Initial review comments are incorporated.
21-Feb-2011
1.2
• LTE external cell support added (VIM based)
28-Feb-2011
1.3
• Support for MOC LNHOIF is introduced
28-Apr-2011
1.4
• Renamed the MOC Names for ADJLW/ADJLG to LNRELW/LNRELG
10-May-2011
1.41
• Added a picture to show the composition of ECGI
For internal use
40
© Nokia Siemens Networks
LTE Object Modelling in Optimizer/ Daiju C A / 28-02-2011