Documente Academic
Documente Profesional
Documente Cultură
RA41129EN08GLA0
RA41129EN08GLA0
RA41129EN08GLA0
RA41129EN08GLA0
RA41129EN08GLA0
RA41129EN08GLA0
RA41129EN08GLA0
RA41129EN08GLA0
RA41129EN08GLA0
10
NOTE:
Central ANR and Automated Neighbor Relation (using PCI / IP mapping table)
are NSN proprietary solutions based on NSN configuration management and
NetAct.
3GPP Automated Neighbor Relation is a standardized solution that does not
rely on vendor OAM, but does require UE and MME to assist eNB in identifying
X2 interface of target eNB.
RL20 and RL30 ANR features may coexist and any or all may be used to
discover adjacent eNB X2 interfaces if UE reports a PCI that is not found in
the eNB adjacencies.
RA41129EN08GLA0
11
NOTE:
Central ANR and Automated Neighbor Relation (using PCI / IP mapping table)
are NSN proprietary solutions based on NSN configuration management and
NetAct.
3GPP Automated Neighbor Relation is a standardized solution that does not
rely on vendor OAM, but does require UE and MME to assist eNB in identifying
X2 interface of target eNB.
RL20 and RL30 ANR features may coexist and any or all may be used to
discover adjacent eNB X2 interfaces if UE reports a PCI that is not found in
the eNB adjacencies.
RA41129EN08GLA0
12
NOTE:
Central ANR and Automated Neighbor Relation (using PCI / IP mapping table)
are NSN proprietary solutions based on NSN configuration management and
NetAct.
3GPP Automated Neighbor Relation is a standardized solution that does not
rely on vendor OAM, but does require UE and MME to assist eNB in identifying
X2 interface of target eNB.
RL20 and RL30 ANR features may coexist and any or all may be used to
discover adjacent eNB X2 interfaces if UE reports a PCI that is not found in
the eNB adjacencies.
RA41129EN08GLA0
13
NOTE:
Central ANR and Automated Neighbor Relation (using PCI / IP mapping table)
are NSN proprietary solutions based on NSN configuration management and
NetAct.
3GPP Automated Neighbor Relation is a standardized solution that does not
rely on vendor OAM, but does require UE and MME to assist eNB in identifying
X2 interface of target eNB.
RL20 and RL30 ANR features may coexist and any or all may be used to
discover adjacent eNB X2 interfaces if UE reports a PCI that is not found in
the eNB adjacencies.
RA41129EN08GLA0
14
no RACH access
no RRC connection setup
no DRB setup
no traffic
Cell Outage Triggered Reset:
Only those conditions are evaluated, which indicate a problem with nearly
absolute certainty:
Failed RACH Access
Failed RRC Connection Setup
Failed DRB Setup
The related alarms are raised only if we have, during one PM data upload
interval, a 100% failure rate of the associated telecom procedures. A BTS
reset is attempted to correct the condition. As long as the alarm stays active,
no further resets are initiated.
The operator can get information about the currently performed recoveries
by viewing a log file.
RA41129EN08GLA0
15
RA41129EN08GLA0
16
RA41129EN08GLA0
17
RA41129EN08GLA0
18
In NSN SON Plug and Play SON Plug and Play removes the need for on site
Notebook / Site Manager
RA41129EN08GLA0
19
RA41129EN08GLA0
20
SON PlugnPlay divided into two features: auto connection and auto
configuration
RA41129EN08GLA0
21
RA41129EN08GLA0
22
At least one dedicated iOMS is required, this is the node that identifies the eNB (based on Site ID, HW ID, or GPS
coordinates) and maps to the eNB object within the Netact Topology DB. Final iOMS may be the same as the
dedicated iOMS.
eNB identification during auto connection
Operator can choose from three different alternative eNB identification mechanisms. All three require that the
temporary eNB identification parameter(s) are beforehand configured by user into dedicated iOMS. When eNB
auto connects the dedicated iOMS and provides the same temporary identification, the dedicated iOMS is then
able to identify the eNB. After this identification using temporary ID, the eNB is linked with its final BTS ID, which
is used from this phase onwards to identify the eNB.
Three alternative eNB identification mechanisms can be choosed from:
1)Site ID based identification. In practice this is a string value defined at planning phase by planner user. That
string value must be made available for installer user who is working at site and he needs to enter this value into
eNB using BTS EM (which should be avoided).
When operator user wants to use ste ID based identification, he defines value in eNB conf plan for
MRBTS: Auto Connection Site ID (non-nw) parameter. If no value is defined in plan, then this mechanism
is not used
2) HW ID based identification. When eNB connects dedicated iOMS it provides the HW ID (installer user at site
does not need to use BTS EM for this). The drawback is that information logistic may be problematic, that how to
get eNB HW ID easily available also for planner user/Configurator user so that he can set HW ID into dedicated
iOMS:
One possibility is that installer user working at site reads the HW ID from the eNB (system module) and
provides it to Configurator user, who can then configure dedicated iOMS. Or this same is done
somehow earlier before taking eNB equipment into site
When operator user wants to use HW ID based identification, he defines value in eNB conf plan for
MRBTS: Auto Connection Hardware ID (non-nw) parameter. If no value is defined in plan, then this
mechanism is not used
3) GPS location based identification. eNB can have GPS equipment installed (optional). When eNB auto connects
to dedicated iOMS it includes GPS location information and then eNBs geographical position is used in
identification. Installer user at site does not need to use BTS EM for this.
Using GPS location based identification is controlled with GPS Tolerance parameter, see Defining eNB AC
functionality in Configurator. In case GPS mechanism is wanted to be used, the GPS Tolerance needs to have
value (in meters).
In case there are several eNBs at the same site (two eNBs inside tolerance) and the dedicated iOMS can not
identify the eNB, then either site ID or HW ID needs to be used in addition to distinguish eNBs from each other.
Operator user must use at least one identification mechanism. In case he uses more than one mechanism then all
those must match in the dedicated iOMS for succesfull eNB identification during auto connection.
RA41129EN08GLA0
23
At least one dedicated iOMS is required, this is the node that identifies the eNB (based on Site ID, HW ID, or GPS
coordinates) and maps to the eNB object within the Netact Topology DB. Final iOMS may be the same as the
dedicated iOMS.
eNB identification during auto connection
Operator can choose from three different alternative eNB identification mechanisms. All three require that the
temporary eNB identification parameter(s) are beforehand configured by user into dedicated iOMS. When eNB
auto connects the dedicated iOMS and provides the same temporary identification, the dedicated iOMS is then
able to identify the eNB. After this identification using temporary ID, the eNB is linked with its final BTS ID, which
is used from this phase onwards to identify the eNB.
Three alternative eNB identification mechanisms can be choosed from:
1)Site ID based identification. In practice this is a string value defined at planning phase by planner user. That
string value must be made available for installer user who is working at site and he needs to enter this value into
eNB using BTS EM (which should be avoided).
When operator user wants to use ste ID based identification, he defines value in eNB conf plan for
MRBTS: Auto Connection Site ID (non-nw) parameter. If no value is defined in plan, then this mechanism
is not used
2) HW ID based identification. When eNB connects dedicated iOMS it provides the HW ID (installer user at site
does not need to use BTS EM for this). The drawback is that information logistic may be problematic, that how to
get eNB HW ID easily available also for planner user/Configurator user so that he can set HW ID into dedicated
iOMS:
One possibility is that installer user working at site reads the HW ID from the eNB (system module) and
provides it to Configurator user, who can then configure dedicated iOMS. Or this same is done
somehow earlier before taking eNB equipment into site
When operator user wants to use HW ID based identification, he defines value in eNB conf plan for
MRBTS: Auto Connection Hardware ID (non-nw) parameter. If no value is defined in plan, then this
mechanism is not used
3) GPS location based identification. eNB can have GPS equipment installed (optional). When eNB auto connects
to dedicated iOMS it includes GPS location information and then eNBs geographical position is used in
identification. Installer user at site does not need to use BTS EM for this.
Using GPS location based identification is controlled with GPS Tolerance parameter, see Defining eNB AC
functionality in Configurator. In case GPS mechanism is wanted to be used, the GPS Tolerance needs to have
value (in meters).
In case there are several eNBs at the same site (two eNBs inside tolerance) and the dedicated iOMS can not
identify the eNB, then either site ID or HW ID needs to be used in addition to distinguish eNBs from each other.
Operator user must use at least one identification mechanism. In case he uses more than one mechanism then all
those must match in the dedicated iOMS for succesfull eNB identification during auto connection.
RA41129EN08GLA0
24
RA41129EN08GLA0
25
RA41129EN08GLA0
26
RA41129EN08GLA0
27
SITEs can be mass created into NetAct by importing XML RAML plan file (does
.CSV file import support site objects -> should be checked). Customer
documentation needs to explain/refer to instructions that how to populate
SITE objects into NetAct if operator does not yet have SITEs there.
eNB assigning to SITE can be done at when importing new eNB plan file
(RAML) into Configurator, or manually if creating eNB configuration plan in
Configurator using CM Editor.
It is possible by using the same RAML plan file import to get the new SITE,
new eNB configuration and eNB assignment with that SITE.
RA41129EN08GLA0
28
RA41129EN08GLA0
29
RA41129EN08GLA0
30
RA41129EN08GLA0
31
Operational eNB is managed and mediated via one iOMS this mediating
iOMS is said to have final iOMS role. eNBs final iOMS is determined as part of
eNB configuration plan. However during new eNB auto connection only
certain iOMS is used this is called dedicated iOMS. Dedicated iOMS identifies
the new eNB during auto connection and tells to eNB that what is the final
iOMS to connect.
Dedicated iOMS identifies the new eNB during auto connection and tells to
eNB that what is the final iOMS to connect. To enable dedicated iOMS to
identify eNB, it needs to have configured the auto identification parameters.
There must be at least one dedicated iOMS for AC to work, but it is not
prevented to have more dedicated iOMS under NetAct. In that case Activate
auto identication operation then activates auto identification to all those
iOMS similarly.
RA41129EN08GLA0
32
RA41129EN08GLA0
33
RA41129EN08GLA0
34
RA41129EN08GLA0
35
RA41129EN08GLA0
36
RA41129EN08GLA0
37