Professional Documents
Culture Documents
RL10/RL15TD/RL20/RL25TD/RL30
Version 1.41 – 10-May-2011
Daiju C A
Bangalore
1..N
1..N
MRBTS
1..1
1..1
SITE LNBTS
0..98 1..2
1..1
ADJLL LCAL ANTE
PLMN
If there are imported
PLMN (s) , then there will 1..1
be 1 OMS per PLMN
OMS In an Optimizer plan, this additionally
represents an item in
1..N adjEnbIpAddressMap present in CM
ADIPNO; Also valid for RL10 starting
SITE MRBTS from Optimizer 3.0 CD1
1..N 1..1
0..32
LNRC LNBTS LNADJ
0..200
1..3
Models an item present Relevant TDD
in pciIpAdrMap LNCEL parameters are
parameter of CM MOC supported
LNBTS
0..98 1..2
1..1
ADJLL LCAL ANTE
1..1
OMS
1..N
SITE MRBTS
1..N 1..1
0..64
LNRC LNBTS LNADJ
0..200
1..6
0..16
Sum of number of instances LNCEL LNHOIF
of LNREL and ADJLL can’t be
more than 389
1..3
1..1
LNCEL LCEL ANTL
1..2
lcrId antlIdList latitude
longitude
bearing
1..2
userDefinedState
1..1 1..1
LCAL ANTE
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
LNBTS
Sum of number of instances
0..64 of LNREL and ADJLL can’t be
X2
1..6 more than 389
LNADJ
LNCEL
Target eNB
When X2 link cannot be
for S1 successfully established, LNADJ LNADJ and LNADJL used for both
is used for S1 HO. X2 and S1 HO. Operator can
LNBTS create LNADJ and LNADJL.
S1 Information in LNADJ X2 Link
Status parameter that is set by
LTE724: ADIPNO no longer used.
system.
MME But operator can create via plan
LNCEL PLMN LNADJ and LNADJL. adjCellInfoL
no longer supported.
S1
LTE782: New object LNREL.
Target eNB
MRBTS
for X2
1..1 Source
X2 eNB
LNBTS LNBTS
1..1 0..16
LNCEL 0..64
ADIPNO LNADLP
LNADJ 1..6
adj eNB list
LNCEL
1..6
0..130
adjCellnfoL
LNADJL LTE Neighbor Relation
A new MOC LNREL is introduced
which represents properties of
LTE neighbour relations. Max:
0…389
6*64 + 5 = 389.
LNREL
Target eNB
for S1 External ENodeB
LNBTS
Function
S1
LNCEL
PLMN
EXENBF S1
Target eNB
for X2 EXEUCE MRBTS
1..1
X2 X2
LNBTS EXENBF LNBTS Source eNB
EXEUCE
LNCEL 0..64
LNADJ 1..6
External
EUtran Cell
LNCEL
1..6
LNADJL
0…389
LNREL
PLMN
External Collection of
ENodeB Function
EXCENBF
EXEUCE
LNBTS
How the
blacklisted cell
information is
brought to
Optimizer will set only the non- Optimizer?
1..6
network parameter “target cell
DN” while creating LNRELW LNCEL
(s). LNRELW is a non-network
MOC and CM plan prepare
takes care of creating/updating
adjWInf parameter and Nu of LNADJW
0..32
LNADJW needs to be
derived from
LNRELW LNRELW
Present only in CM
CM will create LNRELW
Present in CM and in Optimizer instance for every LNADJW
id present in adjWInfL.
Present only in Optimizer
LNBTS
How the
blacklisted cell
information is
brought to
Optimizer will set only the non- Optimizer?
1..6
network parameter “target cell
DN” while creating LNRELG (s). LNCEL
LNRELG is a non-network MOC
and CM plan prepare takes care
of creating/updating adjGInf
parameter and LNADJG Nu of LNADJG
0..32
needs to be
derived from
LNRELG LNRELG
Present only in CM
CM will create LNRELG
Present in CM and in Optimizer instance for every LNADJG
id present in adjGInfL.
Present only in Optimizer
• 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.