You are on page 1of 66

NetAct 8 EP1 EFP1

Managing Adjacencies
DN03317837
Issue: 1-1

The information in this document is subject to change without notice and describes only the product
defined in the introduction of this documentation. This documentation is intended for the use of
Nokia Solutions and Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Solutions and Networks. The
documentation has been prepared to be used by professional and properly trained personnel, and
the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given as is and all liability arising
in connection with such hardware or software products shall be defined conclusively and finally in
a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia
Solutions and Networks has made all reasonable efforts to ensure that the instructions contained
in the document are adequate and free of material errors and omissions. Nokia Solutions and
Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not
be covered by the document.
Nokia Solutions and Networks will correct errors in this documentation as soon as possible. I N N O
E V EN T WI LL N OKI A S O L UT I ON S A N D N E T W O R K S B E L I A B L E F O R E R R O R S
I N T H IS DO CU M EN TAT IO N OR F O R A N Y D A M A G E S , I N C L U D I N G B U T N O T
L IM I T ED TO SPEC IAL, D IR E C T, IN D I R E C T, I N C I D E N TA L O R C O N S E Q U E N T I A L
O R AN Y LOSSES, SU CH A S B U T N O T L I M I T E D TO L O S S O F P R O F I T, R E V E N U E,
B USI NESS IN T ER RU P T I ON , B U S I N E S S O P P O RT U N I T Y O R D ATA , T H AT M AY
A RI SE F RO M T H E USE OF T HI S D O C U M E N T O R T H E I N F O R M AT I O N I N I T.
NSN is a trademark of Nokia Solutions and Networks. 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 Nokia Solutions and Networks 2014/10/22. All rights reserved.

Nokia Solutions and Networks 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 Solutions and Networks for additional information.

Managing Adjacencies

Contents
1 Adjacency management overview................................................................................................................. 5
2 Adjacency types.............................................................................................................................................. 8
2.1 GSM and WCDMA adjacencies................................................................................................................8
2.1.1 Inter-RAT WCDMA -> LTE adjacencies......................................................................................... 11
2.2 LTE adjacencies...................................................................................................................................... 11
2.2.1 Intra-system adjacencies (LTE LTE)..........................................................................................13
2.2.2 Inter-RAT LTE -> WCDMA / Flexi Direct adjacencies.................................................................... 17
2.2.3 Inter-RAT LTE -> GSM adjacencies............................................................................................... 21
2.3 Inter-regional adjacencies....................................................................................................................... 24
3 Adjacency templates..................................................................................................................................... 27
3.1 Automatic template assignment based on cell template........................................................................ 27
3.2 Automatic template assignment based on cell type............................................................................... 27
4 Managing adjacencies using plans............................................................................................................. 28
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9

Prerequisites for the operation................................................................................................................29


Uploading actual configuration................................................................................................................30
Creating the adjacency plan in a planning tool...................................................................................... 30
Creating the adjacency plan in CM Editor or Optimizer......................................................................... 31
Completing the adjacency plan...............................................................................................................31
Checking the adjacency plan..................................................................................................................32
Approving the adjacency plan.................................................................................................................33
Provisioning the adjacency plan to the network..................................................................................... 33
Deleting adjacency plans from the database......................................................................................... 33

5 Managing adjacencies using Send to Network..........................................................................................35


6 Managing adjacencies using local management tools............................................................................. 36
7 Managing inter-regional adjacencies.......................................................................................................... 38
8 Verifying and maintaining adjacencies....................................................................................................... 41
8.1 Checking the actual configuration consistency.......................................................................................41
8.2 Managing measurements........................................................................................................................42
8.2.1 To manage measurements............................................................................................................. 42
8.3 Managing handover reports.................................................................................................................... 42
8.4 Analyzing network performance..............................................................................................................43
9 Adjacency parameters fetched from the target cell.................................................................................. 44
10 Importing user templates required for the LTE Inter-RAT UTRAN / GERAN automatic management
features........................................................................................................................................................ 63

Managing Adjacencies

10.1 ANR inter RAT UTRAN user templates................................................................................................64


10.2 ANR inter RAT GERAN user templates............................................................................................... 65

Managing Adjacencies

Adjacency management overview

1 Adjacency management overview


Note:
Only adjacency types related to supported radio network technologies / network elements
are supported. For information on the supported network element releases, see Supported
network element releases in Release Changes.
NetAct Configurator offers tools for managing adjacencies using mass-scale operations (plan-based
approach) and small-scale operations (using Send to Network functionality).
The following figure describes the concept of adjacency management using NetAct tools.

Figure 1: Adjacency management concept

This chapter gives you an overview of the adjacency management process, explains different adjacency management use cases, and lists tools that are used in the process.
Three different network management cases and related adjacency management aspects are briefly
described below:

Issue: 1-1

DN03317837

Managing Adjacencies

Adjacency management overview

Initial planning
The initial set of adjacencies is defined in BTS site creation. Templates can be used in adjacency creation and less manual parameter input is needed. The adjacencies can be added to the site creation
plan using NetAct Configurator (CM Editor), Optimizer, or an external planning tool.
It is also possible to use Optimizer for creating GSM, WCDMA, and LTE adjacencies based on distance and antenna direction.
If plans are not used, GSM, GSM-R, WCDMA, and Flexi Direct adjacencies can be created directly to
the network using Send to Network functionality of CM Editor or using local management tools. LTE
adjacencies can be created directly to the network only using local management tools.
Optimization
After initial creation the adjacencies in the network can be optimized to improve the performance of the
network. Plans can be used for tuning of handover related parameters or the changes can be implemented directly to the network.
Optimizer can utilise mobile measurements collected and reported by a BSC in adjacency optimization. By analyzing the KPIs, the unused adjacent cells can be identified and removed from the adjacency list. Mobiles measure the whole BCCH segment of the frequency band and report the received
power levels of the serving and surrounding cells. Based on this, promising cells are added to the adjacency list of each cell. The new adjacency plan can be visualized, modified, if necessary, and scheduled for implementation. The DSR (Detected Set Reporting) can also be used for adjacency creation in
Optimizer.
Measurement-based adjacency optimization uses handover measurements collected by BSCs and
RNCs. By analyzing the reports generated based on the measurements, the unused adjacent cells
can be identified and removed from the adjacency list.
To decide which existing adjacencies are good ones and which ones are not needed, handover (HO)
statistics are collected for the existing adjacencies. Furthermore, in WCDMA, the concept of knowing beforehand which adjacencies are missing does not exist yet and therefore, handover statistics
are used for finding new good adjacencies. Candidate adjacencies need to be provisioned to the network before handover statistics can be collected for them. For this reason, Optimizer can make rotation plans for testing adjacencies in the network. Each rotation plan can be visualized and modified.
Furthermore, the final list can also be visualized and modified.
Maintenance
You can troubleshoot the network by checking inconsistencies in adjacencies in the actual configuration and correct adjacencies of one region at a time (CM Analyzer). You can visualize problematic adjacencies, for example, those with low handover success rate values, on top of map and check/modify adjacency parameters (Optimizer). In order for you to see cells and adjacencies on the map, the site
and antenna data must be up to date.

Issue: 1-1

DN03317837

Managing Adjacencies

Adjacency management overview

The measurements and handover reports can be used for maintaining an optimal set of adjacencies in
the network.

Issue: 1-1

DN03317837

Managing Adjacencies

Adjacency types

2 Adjacency types
This chapter gives you an overview of the different adjacency types.
The following adjacency types are supported in NetAct Configurator:
GSM adjacencies
GSM-R adjacencies
WCDMA adjacencies
Flexi Direct adjacencies
LTE adjacencies
For more information on handling different adjacency types in XML and CSV interfaces, see XML Interface for Configuration Management Data and CSV Interface for Configuration Management Data
documents.

2.1 GSM and WCDMA adjacencies


The following figures describe the GSM and WCDMA adjacency types that can be managed using the
processes described in this document. Region in the picture below refers to a radio network managed
by one network management system.

Figure 2: GSM and WCDMA adjacency types

Issue: 1-1

DN03317837

Managing Adjacencies

Adjacency types

Figure 3: GSM and WCDMA inter-regional adjacency types

The following table introduces GSM and WCDMA adjacency types:


Adjacency

Adjacency

Source Target

Source Cell Iden- Target Cell

Handover

type

ID

Cell

Cell

tification

Identification

types

ADCE

LAC + Cell

BTS

BTS / Ex-

Cell Global Identi-

Cell Glob-

Hard

ternal

fier (MCC, MNC,

al Identifier

GSM cell

LAC, CI)

(MCC, MNC,

(GSM <->
GSM)

Issue: 1-1

ID
(0-31)

LAC, CI)

DN03317837

Managing Adjacencies

Adjacency types

Adjacency

Adjacency

Source Target

Source Cell Iden- Target Cell

Handover

type

ID

Cell

Cell

tification

Identification

types

ADJW

ADJW ID

BTS

WCEL /

Cell Global Identi-

Global Utran

Hard, in-

external

fier (MCC, MNC,

Cell Identifier

ter-system

UTRAN

LAC, CI)

(MCC, MNC,

(GSM -> WCD- (0-31)


MA)

cell

inter-system
ADJS

ADJS ID

(WCDMA <->

(1-31)

WCEL

WCDMA)

RNC ID, CI)

WCEL /

Global Utran Cell

Global Utran

Soft, soft-

external

Identifier (MCC,

Cell Identifier

er, hard (in-

UTRAN

MNC, RNC ID, CI) (MCC, MNC,

cell

intra-frequency
ADJD

ADJD ID

(WCDMA <->

(0-31)

WCEL

WCDMA)

RNC ID, CI)

WCEL /

Global Utran Cell

Global Utran

Soft Han-

external

Identifier (MCC,

Cell Identifier

dover Based

UTRAN

MNC, RNC ID, CI) (MCC, MNC,

on Detected

cell

intra-frequency

ter-RNC)

RNC ID, CI)

Set Reporting (optional


3

feature)
ADJI

ADJI ID

(WCDMA <->

(0-47)

WCEL

WCDMA)

WCEL /

Global Utran Cell

Global Utran

Hard, in-

external

Identifier (MCC,

Cell Identifier

ter-frequen-

UTRAN

MNC, RNC ID, CI) (MCC, MNC,

cell

inter-frequency
ADJG

ADJG ID

(WCDMA ->

(0-31)

WCEL

GSM)

RNC ID, CI)

BTS / Ex-

Global Utran Cell

Cell Glob-

Hard, in-

ternal

Identifier (MCC,

al Identifier

ter-system

GSM cell

MNC, RNC ID, CI) (MCC, MNC,


LAC, CI)

inter-system
ADJE

ADJE ID

(WCDMA ->

(0-63)

LTE)

cy

WCEL

LNCEL /

Global Utran Cell

Global eNB ID

Hard, in-

external

Identifier (MCC,

(LNBTS ID +

ter-system

LTE cell

MNC, RNC ID, CI) MCC + MNC)

inter-system
Table 1: GSM and WCDMA adjacency and handover types
1

Some BSC features, for example, GSM-WCDMA Inter-System handover, Common BCCH Control

and Dual band, limit the maximum amount of adjacencies. You can find more information about these
limitations in the BSC documents describing these features.

Issue: 1-1

DN03317837

10

Managing Adjacencies

Adjacency types

RNC/IADA sends information on the neighbor cells for the MS to measure. The messages contain

32 neighbor cells. The MS can only measure 32 neighbors at a time both in the idle and in the active mode, but in the active mode after the neighbors have been measured, the RNC can send a new
list of neighbors to be measured. When the MS is in idle mode, it can perform cell-reselection only
to those measured 32 neighbors. When the MS is in active mode, it can perform handover to all 48
neighbors. 32 of the neighbor definitions should be on the same frequency. The rest 16 can be on different frequencies. At the same time, the measurements can be done on two frequencies.
3

Detected Set Reporting makes it possible to increase the maximum number of intra-frequency neigh-

bor cell definitions significantly so that the RNC can always include all potential target cells in the active set. The feature increases the maximum number of intra-frequency neighbor cells from 31 to 63
neighbor cells per WCDMA cell. The total number of intra-frequency neighbor cells increases further
during soft handover, up to 126 or 189 cells, as the RNC integrates the intra-frequency neighbor cell
definitions of the active set cells.

2.1.1 Inter-RAT WCDMA -> LTE adjacencies


With NetAct8 EP1 release new ADJE adjacency type is introduced for RN8.0 IPA-RNC controllers.
This adjacency enables creating inter-system adjacencies from WCDMA to both FDD and TDD LTE
systems, enabling thus inter-RAT WCDMA-LTE handovers.
WCDMA-LTE ADJE adjacencies can be created/deleted in CM Editor under WCEL object as unidirectional adjacencies pointing to LNCEL or to external LTE cell (EXEUCE). Also, a plan containing ADJE
adjacencies can be imported using XML or CSV northbound interface.
Note:
Parameters defining the ADJE adjacency are divided between ADJE and ADJL managed objects.
With the Plan Prepare functionality of NetAct Configurator, the adjacency plan is kept consistent and
required/missing objects and parameters are created/deleted based on the plan content.

2.2 LTE adjacencies


The following figure describes the LTE adjacency types that can be managed using the processes described in this document. Region in the picture below refers to a radio network managed by one network management system.

Issue: 1-1

DN03317837

11

Managing Adjacencies

Adjacency types

Figure 4: LTE adjacency types

The following table introduces LTE adjacency types:


Adjacency type

Source

Target

Source Cell Iden- Target Cell Identi-

Cell

Cell

tification

fication

Handover types

LTE LTE INTRA-SYSTEM ADJACENCIES AND HANDOVERS

Issue: 1-1

DN03317837

12

Managing Adjacencies

Adjacency type
LNADJ (eNB)

Adjacency types

Source

Target

Source Cell Iden- Target Cell Identi-

Cell

Cell

tification

fication

LNBTS

LNBTS

Global eNB ID

Global eNB ID

EXENBF

(LNBTS ID +

(LNBTS ID + MCC via X2/S1 inter-

MCC + MNC)

+ MNC)

LNCEL

Global eNB ID +

Global eNB ID +

EXEUCE

LCR ID

LCR ID

LNADJL (cell)
(LTE <-> LTE)
intra-frequency

LNCEL

(via X2/S1)

Handover types
Hard handover
face

inter-frequency
(via S1 only)
LTE WCDMA / FLEXI DIRECT INTER-RAT ADJACENCIES AND HANDOVERS
LNADJW

LNBTS

(LTE -> WCDMA)

WCEL

Global eNB ID

Global Utran Cell

EXUCE

(LNBTS ID +

Identifier (MCC,

MCC + MNC)

MNC, RNC ID, CI)

WCEL

Global eNB ID +

Global Utran Cell

EXUCE

LCR ID

Identifier (MCC,

LNADJW

Hard handover

(LTE -> Flexi Direct)


LNRELW

LNCEL

(LTE -> WCDMA)

MNC, RNC ID, CI)

LNRELW
(LTE -> Flexi Direct)
LTE GSM INTER-RAT ADJACENCIES AND HANDOVERS
LNADJG

LNBTS

(LTE -> GSM)

LNRELG
(LTE -> GSM)

LNCEL

BTS

Global eNB ID

Cell Global Identi-

EXGCE

(LNBTS ID +

fier (MCC, MNC,

MCC + MNC)

LAC, CI)

BTS

Global eNB ID +

Cell Global Identi-

EXGCE

LCR ID

fier (MCC, MNC,

Hard handover

LAC, CI)

Table 2: LTE adjacency and handover types


The following sections describe different LTE adjacency types in more details.

Issue: 1-1

DN03317837

13

Managing Adjacencies

Adjacency types

2.2.1 Intra-system adjacencies (LTE LTE)


Note:
Special procedure needs to be performed in order to be able to create bidirectional X2-based
LNADJ adjacencies when the ANR feature is in use. For more information, see section Creating bidirectional, oamControlled, X2-based LNADJ when ANR feature is in use.
LNADJ adjacency is used to manage LTE intra-system (eNB <-> eNB) adjacencies and handovers. It
can be used for both X2-based and S1-based handovers.
Bidirectional and unidirectional LNADJ adjacencies can be created in CM Editor by selecting source
and target LNBTSs and clicking Create Bidirectional Adjacency or Create Unidirectional Adjacency.
When LNADJ adjacency between two eNBs is created, it is X2-based by default (C-Plane IP
address control parameter set to oamControlled). LNADJ adjacencies can be also created
during plan import.
As a result of the unidirectional LNADJ adjacency creation in the plan (X2-based by default), the
LNADJ outgoing adjacency object is created in source LNBTS (pointing to target LNBTS) and the
LNADJ incoming adjacency object is created in target LNBTS.
In case of bidirectional LNADJ adjacency creation in the plan, the same adjacency objects are created
as in case of unidirectional adjacency creation, but additionally, the same adjacency objects (with different DNs) are created in both LNBTSs in the opposite direction to cover the opposite direction of the
adjacency.
If you want LNADJ adjacency to be S1-based, you have to modify the C-Plane IP Address
Control parameter of LNADJ objects in the plan to enbControlled value after adjacency is
created.
When the LNADJ object is created, the target BTS distinguished name is copied to this object, and
later when running Plan Prepare, several other parameters are also copied from target LNBTS to
LNADJ.
LNADJ adjacency handling is different for X2- and S1- based adjacency:
X2-based LNADJ adjacency
After the LNADJ creation plan has been activated in eNBs and the X2-based link has been successfully established between eNBs, source eNB creates LNADJL objects (LNADJ child object)
for each LNCEL of adjacent target LNBTS. NetAct Configurator gets event notifications when
LNADJL objects are created by eNB.
S1-based LNADJ adjacency
After the LNADJ adjacency is created for S1-based link (LNADJ C-Plane IP Address
Control parameter modified to value enbControlled), the Plan Prepare functionality copies
several target LNBTS parameters to LNADJ object, creates LNADJL object (LNADJ child object)
for each LNCEL of adjacent target LNBTS, and copies parameters from target LNCELs to
corresponding LNADJL objects. LNADJL is the read-only object in NetAct Configurator.

Issue: 1-1

DN03317837

14

Managing Adjacencies

Adjacency types

When LNADJ adjacencies already exist in the network either for X2- based or S1-based links, the Plan
Prepare functionality performs the following operations automatically to facilitate consistent LTE intra-system adjacency configuration in the network:
updates incoming LNADJ in the plan when the target LNBTS is modified
updates incoming LNADJ in the plan when the target LNBTS Name is modified
updates incoming LNADJ in the plan for OAM controlled X2-based link, when the target LNBTS
IP Address is modified. IP address is copied from the IPNO Control plane IP address
parameter or if Feature Activation Flag IPv6 for U/C-Plane is having value true then IPNO
Control plane IPv6 address is copied.
updates incoming LNADJL in the plan when target LNCEL is modified (S1 only)
creates incoming LNADJL in the plan when the new LNCEL is created in the target LNBTS (S1
only)
deletes incoming LNADJL in the plan when the corresponding target LNCEL is deleted (S1 only)
updates incoming LNADJL in the plan when target LNCEL is modified and LNADJ X2 link status is
unavailable
updates LNADJ and deletes child LNADJLs in the plan when OAM controlled X2-based link is
redirected by modifying LNADJ Target BTS DN to a plan
LNREL(s) can be created through plan and provisioning for existing LNADJL(s). When unidirectional or bidirectional LNADJ(s) are deleted in the plan, Plan prepare deletes child LNADJL(s) and
related existing LNREL(s) in the same eNB as the deleted LNADJ.
Existing enbControlled LNADJ(s) can be redirected by modifying it to oamControlled and
defining new Target BTS DN to a plan. Run Plan prepare when provisioning the plan. Plan import
also supports this.
Existing oamControlled LNADJ(s) can be redirected by modifying Target BTS DN to a plan.
Run Plan prepare when provisioning the plan. Plan import also supports this.
You can import and export the LTE intra-system adjacency configuration to/from NetAct Configurator
using the XML and CSV northbound interface. For more information, see the XML Interface for Configuration Management Data and CSV Interface for Configuration Management Data documents.
The following figure explains the intra-system adjacencies handling:

Issue: 1-1

DN03317837

15

Managing Adjacencies

Adjacency types

Figure 5: Intra-system LTE adjacency handling

Inter-regional intra-system LTE adjacencies


Inter-regional intra-system LTE adjacencies can be managed using NetAct Configurator. For that purpose, the following objects representing external eNB and external LTE cell are introduced:
EXENBF - External ENodeB function
EXEUCE - External EUtran cell
EXENBF object represents (is mapped to) an external LNBTS in other Network Management System
(NMS) region, when EXEUCE represents (is mapped to) LNCELs of this LNBTS.
LTE inter-system adjacencies pointing to an external eNB and its cells are managed in the similar way
as normal LTE inter-system adjacencies.
For more information about inter-regional adjacencies handling, see Managing inter-regional adjacencies section.
Creating bidirectional, oamControlled, X2-based LNADJ when ANR feature is in use
This procedure needs to be performed in order to be able to create bidirectional oam-Controlled X2based LNADJ adjacencies when an ANR feature is in use.
The ANR feature is in use when both following LNBTS parameters are set to value true:

Issue: 1-1

DN03317837

16

Managing Adjacencies

Adjacency types

Activate ANR support for LTE with OAM extension (anrOmExtEnable) for feature LTE492
Activate UE-based ANR for intra-Frequency LTE (actUeBasedAnrIntraFreqLte) for feature
LTE782
To create bidirectional, oamControlled, X2-based LNADJ when ANR feature is in use
1. Create unidirectional, oamControlled X2-based LNADJ adjacency from the source LNBTS to the
target LNBTS. Create a new plan for this purpose.
2. Run the Plan Prepare operation for the plan where the LNADJ adjacency has been created.
After the operation the C-Plane IP address of neighbor eNB parameter of the LNADJ is filled in, but
the adjacency is still unidirectional.
3. Provision the adjacency plan to the network and wait until events are received from the network.
As a result, the oamControlled X2-based LNADJ is created from the source LNBTS to the target
LNBTS (content of the plan), and additionally the eNodeB has automatically created the enbControlled X2-based LNADJ from the target LNBTS to the source LNBTS.
4. Modify the C-Plane IP address control parameter of the LNADJ adjacency created
automatically by the eNodeB to the oamControlled value, so that adjacency is oamControlled
X2-based instead of enbControlled X2-based. Create a new plan for this purpose.
5. Provision above plan to the network with the Plan Prepare option enabled.
As a result, the bidirectional, oamControlled X2-based LNADJ adjacency exists between the source
LNBTS and the target LNBTS.

2.2.2 Inter-RAT LTE -> WCDMA / Flexi Direct adjacencies


You need to perform the following steps in order to be able to start using the Inter-RAT UTRAN auto
management functionalities. Inter-RAT UTRAN auto management operations are performed by Plan
Prepare to complete the LTE Inter-RAT adjacency plan and help to keep the adjacency relations consistent.
The anrInterRatUtranEnabled property of the configurator.properties property file
has to be set to true (anrInterRatUtranEnabled=true).
For instructions, see Enabling Inter-RAT UTRAN and Inter-RAT GERAN features auto management in Plan Prepare in Administering NetAct Configurator document.
The user templates for the LNHOW, REDRT, and UFFIM managed object classes, which are
stored in the /etc/opt/nokia/oss/rac/conf/profiles/ directory, have to be manually
imported to NetAct Configurator. The name of the user template after importing each of above
managed object class is ANR inter RAT UTRAN.
For more information, see Importing user templates required for the LTE Inter-RAT UTRAN / GERAN automatic management features.
Note:

Issue: 1-1

DN03317837

17

Managing Adjacencies

Adjacency types

The Inter-RAT UTRAN auto management functionality does not support the case when the
type of the target UTRAN cell is TD-SCDMA.
LTE WCDMA / Flexi Direct inter-RAT (inter Radio Access Technology) adjacencies are used to manage relationships and handovers between LTE and WCDMA / Flexi Direct cells. Adjacencies to external WCDMA / Flexi Direct cells (managed by another network management system) are also supported. There are two adjacency types to manage LTE - WCDMA / Flexi Direct inter-RAT adjacencies:
LNADJW and LNRELW. Each of them plays a different role:
LNRELW is used for adjacencies between one LNCEL (LTE cell) and one WCEL / EXUCE (WCDMA / Flexi Direct cell or external WCDMA / Flexi Direct cell).
LNADJW is used for adjacencies between all LNBTSs (eNB) cells and one WCEL / EXUCE
(WCDMA / Flexi Direct cell or external WCDMA / Flexi Direct cell).
Inter-RAT adjacencies between LTE and WCDMA cells are unidirectional only. The adjacency direction
is LTE -> WCDMA.
LTE WCDMA adjacencies can be managed in the following ways:
Manually by the NetAct Configurator operator:
LNRELW and LNADJW adjacencies can be created / deleted using CM Editor and also imported to NetAct Configurator using XML or CSV northbound interface
Note:
Creation of Inter-RAT UTRAN LNADJW/ LNRELW is not supported for LNT3.1.
LNRELW adjacency can be blacklisted if wanted in CM Editor
By Plan Prepare functionality of NetAct Configurator to complete the adjacency plan and help to
keep the adjacencies consistent:
required / missing LNADJW and LNRELW objects are created / deleted based on the plan
content
LNHOW, REDRT, UFFIM, and LNCEL objects are configured based on the plan content
LNADJW adjacency planning
LNADJW adjacency (between all LNBTSs cells and WCEL / EXUCE) can be created in CM Editor by
selecting desired source LNBTS and target WCEL (or EXUCE) and clicking Create Unidirectional Adjacency. As a result the LNADJW is created in source LNBTS (outgoing) and target WCEL / EXUCE
(incoming).
Note:
LNADJW adjacencies can be also planned (created/modified/removed) by importing a plan
to NetAct Configurator using the XML or CSV northbound interface.
Creation of Inter-RAT UTRAN LNADJW / LNRELW is not supported for LNT3.1.
After planning (creating) LNADJW adjacency in the plan, the Plan Prepare functionality:

Issue: 1-1

DN03317837

18

Managing Adjacencies

Adjacency types

creates LNRELW outgoing adjacency object in all LNCELs of source LNBTS


creates LNRELW incoming adjacency objects in the target WCEL / EXUCE coming from each LNCEL in the source LNBTS
configures LNHOW, REDRT, and UFFIM objects of all LNCELs in the source LNBTS
The following figure explains the LNADJW inter-RAT adjacency handling:

Figure 6: LNADJW adjacency handling

LNRELW adjacency planning


LNRELW adjacency (between one LNCEL and one WCEL / EXUCE) can be created in CM Editor by
selecting desired source LNCEL and target WCEL (or EXUCE) and clicking Create Unidirectional Adjacency. As a result the LNRELW is created in source LNCEL (outgoing) and target WCEL / EXUCE
(incoming).
Note:
LNRELW adjacencies can be also planned (created/modified/removed) by importing a plan
to NetAct Configurator using the XML or CSV northbound interface.
Creation of Inter-RAT UTRAN LNADJW / LNRELW is not supported for LNT3.1.
After planning LNRELW adjacency in the plan, the Plan Prepare functionality:
creates LNADJW outgoing adjacency object in the LNBTS of the source LNCEL

Issue: 1-1

DN03317837

19

Managing Adjacencies

Adjacency types

creates LNADJW incoming adjacency objects in the target WCEL / EXUCE coming from the
source LNBTS
configures LNHOW, REDRT, and UFFIM objects of the source LNCEL
The following figure explains the LNRELW inter-RAT adjacency handling:

Figure 7: LNRELW adjacency handling

When using BTS Site Manager to create Inter-RAT UTRAN/GERAN adjacencies, LNADJW/LNADJG
must be created before creating LNRELW/LNRELG in order to have LNRELW/LNRELG non-network
parameters correctly defined. In case target cell does not exist, EXUCE/EXGCE has to be created with
more parameters than in case it has been created first as a target for LNRELW/LNRELG.
Creation of Inter-RAT UTRAN LNADJW/ LNRELW is not supported for LNT3.1.
Also in case when EXGCE/EXUCE has been created as target for Inter-RAT GERAN/UTRAN adjacency, and later it will be used as target for adjacency creation from WCDMA/Flexi Direct or GSM networks, then EXGCE/EXUCE might be missing some mandatory parameters and cause adjacency creation failing.
To correct incomplete EXGCEs/EXUCEs, the following steps need to be performed:
1. Change the incomplete EXGCE/EXUCE to delete in a plan.
2. Provision the EXGCE/EXUCE deletion plan without doing Plan prepare (unselect the Prepare plan
check-box in the Provision dialog).
3. When the provisioning operation is finished, upload RNC/IADA, BSC or MRBTS (in this order) depending on the incoming adjacencies that deleted EXGCE/EXUCE had.
Expected result

Issue: 1-1

DN03317837

20

Managing Adjacencies

Adjacency types

The correct and complete EXGCE/EXUCE is created and corresponding incoming adjacencies are retargeted.

2.2.3 Inter-RAT LTE -> GSM adjacencies


You need to perform the following steps in order to be able to start using the Inter-RAT GERAN auto
management functionalities. Inter-RAT GERAN auto management operations are performed by Plan
Prepare to complete the LTE Inter-RAT adjacency plan and help to keep the adjacency relations consistent.
The anrInterRatGeranEnabled property of the configurator.properties property file
has to be set to true (anrInterRatGeranEnabled=true).
For more information, see Configurator Technical Reference document.
The user templates for the LNHOG, REDRT, GFIM, and GNFL managed object classes, which are
stored in the /etc/opt/nokia/oss/rac/conf/profiles/ directory, have to be manually
imported to NetAct Configurator. The name of the user template after importing each of above
managed object class is ANR inter RAT GERAN.
For more information, see Importing user templates required for the LTE Inter-RAT UTRAN / GERAN automatic management features.
LTE GSM inter-RAT (inter Radio Access Technology) adjacencies are used to manage relationships
and handovers between LTE and GSM cells. Adjacencies to external GSM cells (managed by another network management system) are also supported. There are two adjacency types to manage LTE GSM inter-RAT adjacencies: LNADJG and LNRELG. Each of them plays a different role:
LNRELG is used for adjacencies between one LNCEL (LTE cell) and one GSM cell (BTS /
EXGCE)
LNADJG is used for adjacencies between all LNBTSs (eNB) cells and one GSM cell (BTS /
EXGCE)
Inter-RAT adjacencies between LTE and GSM cells are unidirectional only. The adjacency direction is
LTE -> GSM.
LTE GSM adjacencies can be managed in the following ways:
Manually by the NetAct Configurator operator:
LNRELG and LNADJG adjacencies can be created / deleted using CM Editor and also imported to NetAct Configurator using XML or CSV northbound interface
LNRELG adjacency can be blacklisted if wanted in CM Editor
By Plan Prepare functionality of NetAct Configurator to complete the adjacency plan and help to
keep the adjacencies consistent:
required / missing LNADJG and LNRELG objects are created / deleted based on the plan content

Issue: 1-1

DN03317837

21

Managing Adjacencies

Adjacency types

entries to LNCELs List of pointer to LNADJG instance (adjGInfList) parameter


are added / deleted based on the plan content
LNHOG, GFIM, GNFL, REDRT, and LNCEL objects are configured based on the plan content
LNADJG adjacency planning
LNADJG adjacency (between all LNBTSs cells and BTS / EXGCE) can be created in CM Editor by selecting desired source LNBTS and target BTS / EXGCE and clicking Create Unidirectional Adjacency.
As a result the LNADJG is created in source LNBTS (outgoing) and target BTS / EXGCE (incoming).
Note:
LNADJG adjacencies can be also planned (created/modified/removed) by importing a plan to
NetAct Configurator using the XML or CSV northbound interface.
After planning (creating) LNADJG adjacency in the plan, the Plan Prepare functionality:
creates LNRELG outgoing adjacency object in all LNCELs of source LNBTS
creates LNRELG incoming adjacency objects in the target BTS coming from each LNCEL in the
source LNBTS
adds new entry to the List of pointer to LNADJG instance (adjGInfList) parameter
of all LNCELs in the source LNBTS
configures LNHOG, GFIM, GNFL, and REDRT objects of all LNCELs in the source LNBTS
The following figure explains the LNADJG inter-RAT adjacency handling:

Issue: 1-1

DN03317837

22

Managing Adjacencies

Adjacency types

Figure 8: LNADJG adjacency handling

LNRELG adjacency planning


LNRELG adjacency (between one LNCEL and one BTS / EXGCE) can be created in CM Editor by selecting desired source LNCEL and target BTS (or EXGCE) and clicking Create Unidirectional Adjacency. As a result the LNRELG is created in source LNCEL (outgoing) and target BTS / EXGCE (incoming).
Note:
LNRELG adjacencies can be also planned (created/modified/removed) by importing a plan to
NetAct Configurator using the XML or CSV northbound interface.
After planning LNRELG adjacency in the plan, the Plan Prepare functionality:
creates LNADJG outgoing adjacency object in the LNBTS of the source LNCEL
creates LNADJG incoming adjacency objects in the target BTS coming from the source LNBTS
adds new entry to the List of pointer to LNADJG instance (adjGInfList) list
parameter of the source LNCEL
configures LNHOG, GFIM, GNFL, and REDRT objects of the source LNCEL
The following figure explains the LNRELG inter-RAT adjacency handling:

Issue: 1-1

DN03317837

23

Managing Adjacencies

Adjacency types

Figure 9: LNRELG adjacency handling

When using BTS Site Manager to create Inter-RAT UTRAN/GERAN adjacencies, LNADJW/LNADJG
must be created before creating LNRELW/LNRELG in order to have LNRELW/LNRELG non-network
parameters correctly defined. In case target cell does not exist, EXUCE/EXGCE has to be created with
more parameters than in case it has been created first as a target for LNRELW/LNRELG.
Also in case when EXGCE/EXUCE has been created as target for Inter-RAT GERAN/UTRAN adjacency, and later it will be used as target for adjacency creation from WCDMA/Flexi Direct or GSM networks, then EXGCE/EXUCE might be missing some mandatory parameters and cause adjacency creation failing.
To correct incomplete EXGCEs/EXUCEs, the following steps need to be performed:
1. Change the incomplete EXGCE/EXUCE to delete in a plan.
2. Provision the EXGCE/EXUCE deletion plan without doing Plan prepare (unselect the Prepare plan
check-box in the Provision dialog).
3. When the provisioning operation is finished, upload RNC/IADA, BSC or MRBTS (in this order) depending on the incoming adjacencies that deleted EXGCE/EXUCE had.
Expected result
The correct and complete EXGCE/EXUCE is created and corresponding incoming adjacencies are retargeted.

Issue: 1-1

DN03317837

24

Managing Adjacencies

Adjacency types

2.3 Inter-regional adjacencies


External GSM / UTRAN / E-UTRAN cell objects are non-network objects used for managing adjacencies between regions. External cell objects represent the cells managed by another network management system.
External cells are modelled by the following objects:
External GSM cell = PLMN-<subnetwork>/EXCCG-1/EXGCE-xx
External UTRAN cell = PLMN-<subnetwork>/EXCCU-1/EXUCE-xx
External E- UTRAN cell = PLMN-<subnetwork>/EXCENBF-1/EXENBF-1/EXEUCE-xx
External cell objects are available in the nsn.com.vimext adaptation.
Adjacencies pointing to external cells are managed in the same way as other adjacencies, either using
plans, or Send to Network functionality of CM Editor. External cell objects can be managed only using
plans.
See the following table for definitions of the objects:
External GSM cell (EXGCE)
Identifica-

EXGCE ID

(EXUCE)

External EUTRAN cell


(EXEUCE)

EXUCE ID

EXEUCE ID

External UTRAN cell

tion
Parame-

External GSM cell contains pa- External UTRAN cell con-

ters

rameters that are needed for

tains the following para-

defining incoming adjacencies: meters that are needed


for defining incoming adja-

LAC

cencies:

CI
MCC

Cell Identifier

MNC

Location Area
Code

RAC

Maximum UE

BSIC BCC
BSIC NCC

Transmission

Ms Tx Pwr Max CCH

Power on DPCH

MS Tx Pwr Max CCH


1x00 (GSM 1800/
Ms Tx Power Max GSM
MS Tx Pwr Max GSM
1x00 (GSM 1800/1900)
HCS Priority Class
GPRS Enabled
Issue: 1-1

Transmission
Power on RACH

GSM1900)

HCS Threshold

Maximum UE

Mobile Country
Code
Mobile Network
Code
Primary CPICH Tx
Power (dBm)

DN03317837

25

Managing Adjacencies

Adjacency types

External GSM cell (EXGCE)


DTM Enabled

External UTRAN cell


(EXUCE)

External EUTRAN cell


(EXEUCE)

Primary

GPRS MS Tx Pwr Max

Scrambling Code
RNC Id

CCH
GPRS MS Tx Pwr Max
CCH 1x00 (GSM 1800/

Routing Area
Code
Service Area

GSM1900)
Initial Frequency
(BCCH TRX parameter)
In CM Editor, you can define

Code
UARFCN DL
UARFCN UL

the same parameters for external GSM cell as for real BTSs.
Location

Location information is need-

Location information is

information ed for SITE object attached to

needed for SITE object at-

external GSM cell for visualiz-

tached to external UTRAN

ing external GSM cell in Opti-

cell for visualizing external

mizer. Location information can UTRAN cell in Optimizer.


be defined using Antenna Data Location information can
Editor tool provided with Opti-

be defined using Anten-

mizer. Location information can na Data Editor tool providalso be defined in CM Editor

ed with Optimizer. Loca-

(SITE object assignment).

tion information can also


be defined in CM Editor
(SITE object assignment).

Table 3: Inter-regional adjacencies

Issue: 1-1

DN03317837

26

Managing Adjacencies

Adjacency templates

3 Adjacency templates
Adjacency parameters can be defined with adjacency templates, and the templates can be automatically assigned to adjacencies during adjacency creation.
Automatic template assignment based on cell type or cell template can be used for ADCEs. For all
other adjacencies, only the cell template based method can be used.
System template is assigned to the adjacency during adjacency creation if template assignment based
on cell type or cell template cannot be done.
Automatic template assignment for adjacencies is supported in CM Editor, CM Operations Manager (plan import), and Optimizer. For more information, see Templates in Configuration Management
Overview and Operations.

3.1 Automatic template assignment based on cell template


To use the cell template based automatic adjacency template assignment, the following preconditions
have to be met:
Source and target cell objects have templates assigned.
The corresponding adjacency template exists in the Configurator database. Name the adjacency
template in the following way: <sourceTemplateName>_<targetTemplateName>. For
example, if the source cell has the Pico template assigned and the target cell Micro template,
the name of the corresponding adjacency template should be Pico_Micro.
If the above preconditions are met, corresponding adjacency template is assigned to adjacency based
on the cell template name. It happens during adjacency creation.
If the above preconditions are not met, the System template is assigned to the adjacency during
adjacency creation.
In addition to the above, special template rules can be created in Optimizer for GSM and WCDMA adjacencies.

3.2 Automatic template assignment based on cell type


To use cell type based automatic template management for ADCE, the following preconditions have to
be met:
Cell type is defined for both source and target cell of adjacency.
vrfceltypemx configuration file defines the adjacency template for the cell types in source and
target cells.
Adjacency template exists in the NetAct Configurator database.

Issue: 1-1

DN03317837

27

Managing Adjacencies

Managing adjacencies using plans

4 Managing adjacencies using plans


This chapter describes how to prepare the adjacency modification plans and activate them to the network.
You can plan adjacency changes with any available network planning tool, if the plans are provided in
XML (RAML/CM2.0) or CSV format defined by Nokia Solutions and Networks. For more information on
the interfaces and for example files, see XML Interface for Configuration Management Data and CSV
Interface for Configuration Management Data documents.
You can create new adjacencies, redirect existing adjacencies, modify adjacency parameters, and
delete adjacencies using CM Editor and Optimizer.
If you are optimizing existing adjacencies, by creating performance reports such as Drop call rate, HO
drop call ratio, HO failure ratio and interference, you can analyze whether the performance of the network has improved after the implementation of your plan by comparing the pre-event and post-event
reports. For more information, see Verifying and maintaining adjacencies.
The following flowchart illustrates how to manage adjacencies in the network using plans. Click a
process in a figure for more information.

Issue: 1-1

DN03317837

28

Managing Adjacencies

Managing adjacencies using plans

4.1 Prerequisites for the operation


NetAct Configurator is operational.
NetAct Optimizer is operational (if Optimizer is used).
If using Optimizer, site and antenna data must be ready.

Issue: 1-1

DN03317837

29

Managing Adjacencies

Managing adjacencies using plans

Templates for adjacencies exist and templates for cells have been assigned.

4.2 Uploading actual configuration


The purpose of this operation is to upload the actual network configurations to NetAct database.
Upload the actual network configuration to the NetAct database using CM Operations Manager to
make sure that the information in NetAct and network element databases is consistent.
For instructions, see CM Operations Manager Help.
Note:
You can use cron to schedule the upload to occur periodically.

4.3 Creating the adjacency plan in a planning tool


You can plan changes in your adjacencies using planning tool. The changes in adjacencies may cover
several NetAct regions.
1. Export the actual configuration to an XML (RAML2.0), or a CSV file with CM Operations Manager.
2. Import the actual configuration file to the planning tool.
3. Create the adjacency plan with the planning tool. You can create new adjacencies, redirect existing
adjacencies, modify adjacency parameters and delete adjacencies.
Adjacency redirecting can be done by modifying the Target Cell DN parameter. The target cell dependent parameters are updated to the adjacency in plan preparation operation when the plan is
provisioned to network. Template of the adjacency is not changed when redirecting.
The adjacency plan may cover several NetAct regions. Ensure that the external cells are correctly
defined in all the regions.
4. Export the adjacency plan created in the planning tool to an XML or CSV file. The exported file can
be then imported to NetAct Configurator for further operations.
Export the adjacency changes planned in each region to the separate files.
5. Import the adjacency plan to NetAct Configurator.
If the changes planned for adjacencies cover more than one region, import the adjacency plan for
each region.
For examples of adjacency plan files that can be imported with CM Operations Manager, see XML
Interface for Configuration Management Data and CSV Interface for Configuration Management
Data documents.
Note:

Issue: 1-1

DN03317837

30

Managing Adjacencies

Managing adjacencies using plans

It is recommended that external cells for adjacencies are included in the border-area adjacency plan. This way you can ensure that the external cells have a full set of parameters when they are created in NetAct.
To import adjacency plan file using CM Operations Manager
a. Import the adjacency plan using CM Operations Manager. You can merge the plan to an
existing plan if the two plans do not contain changes to the same object.
IDs are allocated to the ADJS/ADJD/ADJI/ADJG/ADJW objects that are defined with source
and target cell parameters. The system checks which IDs are not reserved in NetAct topology.
Adjacency templates are automatically assigned to imported adjacencies if preconditions explained in section Adjacency templates are met.
If the adjacency target cell is not found, external GSM cell / external UTRAN cell objects in the
plan file are mapped to existing external GSM cell / external UTRAN cell objects, or new external GSM cell / external UTRAN cell objects are created to the NetAct Configurator database. If
the external GSM cell / external UTRAN cell is the first one of its kind, the system automatically
creates parent objects for them.
For a redirected adjacency, import finds the new target cell.
b. Check the log. If there are errors, delete the plan that was imported, correct the original plan
and import it again.
c. Repeat steps 1-2 for each region.

4.4 Creating the adjacency plan in CM Editor or Optimizer


You can plan adjacencies using CM Editor or Optimizer instead of using external planning tools. CM
Editor and Optimizer support all plan operations for adjacencies.
CM Editor requires that external GSM cell / external UTRAN cell objects exist in the NetAct Configurator database before adjacencies can be created. Templates can be used for defining adjacency parameters for new adjacencies. For more information on templates and foreign cells, see section Adjacency templates and Inter-regional adjacencies.
To create adjacencies in CM Editor, select the adjacency source and target cell and create either bi-directional or unidirectional adjacency.
For instructions on creating adjacencies using CM Editor, see CM Editor Help.

4.5 Completing the adjacency plan


If you were planning adjacencies using external planning tool, you can still make some additional
changes to the plan using CM Editor before activating the adjacency plan to the network.

Issue: 1-1

DN03317837

31

Managing Adjacencies

Managing adjacencies using plans

In CM Editor, adjacency parameters from target cells are read-only and can only be updated by updating the target cells.
To complete the adjacency plan
1. If needed, check that the template definitions for the new adjacencies are correct.
2. In CM Editor, if new external GSM cell / external UTRAN cell objects were created during the import, define the missing parameters and templates for the objects. For this you need to have the information on the real BTSs and WCELs available.
Note:
Check that the external cells are up-to-date with the corresponding real cells.
3. If needed, create new adjacencies using CM Editor or Optimizer. Templates for the new adjacencies are assigned according to the rules explained in section Adjacency templates. IDs for new adjacencies are allocated automatically at the creation.
4. If needed, delete adjacencies using CM Editor or Optimizer.
5. If needed, make modifications to the adjacency parameters using CM Editor or Optimizer.
Note:
Using CM Editor it is possible to redirect an adjacency by modifying the Target Cell DN parameter. The target cell dependent parameters are updated to the adjacency in plan preparation operation. Template of the adjacency is not changed when redirecting.
For more information, see CM Editor Help.

4.6 Checking the adjacency plan


This step is optional.
Note:
Checks to update target cell data of the adjacency need not be run in this phase because the
target cell parameters are filled in and updated in plan preparation.
1. Check the consistency of radio network parameters in the plan with CM Analyzer. Use auto
correction for the plan in CM Analyzer if the rule that you are using supports it. For more details,
see rule descriptions in CM Analyzer user interface. For instructions, see CM Analyzer Help.
For a list of available rule sets, see Rules and Rule Syntax for NetAct Configurator.
2. If auto correction was used, missing, extra, or inconsistent objects and parameters are updated to
the plan. If auto correction was not used, correct the errors with CM Editor.
3. Repeat the checks until no errors are found.
For more information on CM Analyzer, see CM Analyzer Help.

Issue: 1-1

DN03317837

32

Managing Adjacencies

Managing adjacencies using plans

4.7 Approving the adjacency plan


Approving the plan is an optional phase of the operation.
To approve the adjacency plan, change the state of the plan to Approved using CM Operations Manager.
For more information, see CM Operations Manager Help.

4.8 Provisioning the adjacency plan to the network


Activating the changes to the network may cause downtime in the network depending on the contents
of your plan. If your plan contains only changes to the adjacencies, activating does not cause any
downtime in the network.
The parameter plan can contain changes related to all networks described in this document. In the
provisioning phase you can pre-activate and activate the plan separately for each controller.
Before starting to provision your plan:
If the measurement data transfer from the network elements to NetAct causes heavy load on the
system, the operation may proceed slower than usual. To speed up the operation, you can try
stopping the measurement data transfer for the activation period. You can stop the measurement
data collection from the BSCs using Administration of Measurements. However, stopping the
measurement data collection does not buffer the measurement information. There will be no
measurement data for the stopped time period.
For more information, see Administration of Measurements Help.
Concurrent uploads may slow down the activation process. Check cron for scheduled uploads.
Plan provisioning is performed using CM Operations Manager or command line interface.
If you have not prepared the plan before, you must also select the prepare plan option.
As an outcome of the plan provisioning operation, the plan is activated in the network and the actual
configuration is updated in NetAct.
For more detailed information, see Managing the Network with NetAct Configurator Radio.
Note:
You can use Optimizer to create adjacency modifications directly to the network. In Optimizer you can use the Instant adjacency provisioning functionality in order to provision adjacency changes to the network.

Issue: 1-1

DN03317837

33

Managing Adjacencies

Managing adjacencies using plans

4.9 Deleting adjacency plans from the database


If you used plans to plan adjacencies, you can delete them from the NetAct Configurator database
once they are provisioned to the network. You can delete plans using CM Operations Manager or CM
Editor.
Note:
It is recommended that you always delete old adjacency plans.
For more information on plan deletion, see CM Operations Manager Help or CM Editor Help.

Issue: 1-1

DN03317837

34

Managing Adjacencies

Managing adjacencies using Send to Network

5 Managing adjacencies using Send to Network


This chapter describes how to manage GSM, GSM-R, WCDMA, and Flexi Direct adjacencies one by
one, directly to the network, using Send to Network functionality in CM Editor.
The following adjacencies can be created, redirected, modified, and deleted using Send to Network
funtionality:
ADCE (GSM - GSM, GSM-R - GSM-R)
ADJW (GSM - WCDMA/Flexi Direct)
ADJS (WCDMA/Flexi Direct - WCDMA/Flexi Direct)
ADJI (WCDMA/Flexi Direct - WCDMA/Flexi Direct)
ADJD (WCDMA/Flexi Direct - WCDMA/Flexi Direct)
ADJG (WCDMA/Flexi Direct - GSM)
ADJE (WCDMA - LTE)
Note:
After modifying target cell objects (LNCEL or LNBTS), you have to provision a temporary
plan for ADJE.
The target cell can be a real cell managed by the NetAct region, an external cell within another NetAct
region, or another vendor cell. For more information on external cells, see section Managing inter-regional adjacencies.
When a GSM, GSM-R, WCDMA or Flexi Direct cell is modified using Send to Network functionality,
Configurator updates the incoming adjacencies automatically in the network. In case of incoming LTE
adjacencies (LNRELG, LNADJG, LNRELW, LNADJW and ADJE), CM Editor adds the required adjacency changes to a plan that needs to be provisioned manually to the network.
Dedicated CM Activation Options for WCDMA license is required for managing WCDMA
objects using Send to Network.
For more information on managing adjacencies using Send to Network functionality of CM Editor, see
CM Editor Help document.

Issue: 1-1

DN03317837

35

Managing Adjacencies

Managing adjacencies using local management tools

6 Managing adjacencies using local management tools


You can manage GSM, GSM-R, WCDMA, Flexi Direct, and LTE adjacencies using local management
tools (MML, element managers). The functionality of the tools depends on the technology and the
release. The configuration changes are updated to the Configurator actual configuration via events.
However, it is recommended to use Configurator to manage adjacencies, as the local management
tools do not guarantee the parameter consistency across elements and different technologies, but additional consistency checks are required to be performed at network level.
The following adjacencies can be created, redirected, modified, and deleted using local management
tools:
ADCE (GSM - GSM, GSM-R - GSM-R)
ADJW (GSM WCDMA)
ADJS (WCDMA/Flexi Direct - WCDMA/Flexi Direct)
ADJD (WCDMA/Flexi Direct WCDMA/Flexi Direct)
ADJI (WCDMA/Flexi Direct - WCDMA/Flexi Direct)
ADJG (WCDMA/Flexi Direct - GSM)
ADJE (WCDMA LTE)
LNADJ (LTE - LTE)
LNADJL (LTE - LTE)
LNADJW and LNRELW (LTE WCDMA/Flexi Direct)
LNADJG and LNRELG (LTE GSM)
The target cell can be a real cell managed by the NetAct region, an external cell within another NetAct
region, or another vendor cell. For more information on external cells, see the Managing inter-regional
adjacencies section.
For more information on the local management tools, see the RAN documentation set of the respective technology.
When a GSM or GSM-R cell is modified or deleted using a local management tool, BSC takes care of
updating or deleting the BSC internal incoming adjacencies, but all other incoming adjacencies, including BSC external ADCE and ADJG, LNRELG and LNADJG are not updated or deleted accordingly.
You need to run consistency checks in NetAct Configurator to correct incoming adjacency parameters
and to remove adjacencies for which the target cell does not exist anymore.
In WCDMA and Flexi Direct the local management tool functionality is the same as in GSM and GSMR. The incoming adjacencies including ADJS, ADJI, ADJW, LNRELW and LNADJW need to updated
or deleted manually. CM Analyzer consistency checks can be used to detect the inconsistent parameters and adjacencies without target cell.
When an LTE cell is modified or deleted using a local management tool, all X2 adjacencies that are
having X2 link status available are updated automatically. For enbControlled adjacencies that are having X2 link status unavailable and cell is modified, you need to run consistency checks in Configura-

Issue: 1-1

DN03317837

36

Managing Adjacencies

Managing adjacencies using local management tools

tor to correct incoming adjacency parameters. When LTE eNB IP address is modified a local management tool, all enbControlled X2 adjacencies that are having X2 link status available are updated automatically. For enbControlled adjacencies that are having X2 link status unavailable and oamControlled
adjacencies, you need to run consistency checks in NetAct Configurator to correct incoming adjacency parameters. When eNB is deleted, you need to manually delete the adjacencies that have not been
automatically deleted.
The following rule sets are meant to detect the adjacency inconsistencies in the network:
Nokia.ActualAdjacencyChecking_2G (ADCE, ADJW)
Nokia.ActualAdjacencyChecking_3G (ADJS, ADJI, ADJD, ADJG, ADJE)
Nokia.ActualAdjacencyCheking_LTE (LNADJ, LNADJL, LNADJG, LNRELG, LNRELW,
LNADJW)
For more information on rules and consistency checks, see CM Analyzer Help and Rules and Rule
Syntax for NetAct Configurator.

Issue: 1-1

DN03317837

37

Managing Adjacencies

Managing inter-regional adjacencies

7 Managing inter-regional adjacencies


External GSM cell (EXGCE), External WCDMA/Flexi Direct cell (EXUCE), and External ENodeB Function (EXENBF) together with child External EUtran cell (EXEUCE) are non-network objects used for
managing adjacencies between regions. EXGCE, EXUCE, and EXENBF together with EXEUCE represent the cells managed by another network management system.
The following object hierarchy is used for modelling external cell objects:
External GSM cell = PLMN-<subnetwork>/EXCCG-1/EXGCE-xx
External UTRAN cell = PLMN-<subnetwork>/EXCCU-1/EXUCE-xx
External E- UTRAN cell = PLMN-<subnetwork>/EXCENBF-1/EXENBF-1/EXEUCE-xx
External cell objects are available in the nsn.com.vimext adaptation.
Adjacencies pointing to external cells are managed in the same way as other adjacencies, either using
plans, or directly in the network using Send to Network functionality. External cell objects can be managed only using plans.
Multi-region adjacency management
In NetAct, an adjacency must always have both source and target cell objects although the target cell
itself does not exist in the region. Therefore external cells are needed for representing the real cells.
However, Configurator does not check the correspondence between external BTS and the real BTS,
between external WCEL and the real WCEL, or between the EXENBF and EXEUCE pair and the real LNBTS and LNCEL. Changes in the real cells need to be updated manually in the related EXGCE /
EXUCE/ EXENBF and EXEUCE objects in each region. For example, in case LAC, BCCH, or primary
scrambling code of a cell in neighboring region changes, you need to update manually the corresponding external objects in your region. When creating a border-area adjacency plan, check that the external cell definitions in both regions are up-to-date, and implement the changes in both regions to ensure the handovers in the border area.
You can also use the Advanced Configurator product for automatic management of the border area
adjacency relations, for example, for keeping external cells updated when the real cell is modified (in
another region).
Plan import
EXGCE, EXUCE, and EXENBF together with EXEUCE in a plan can be imported to NetAct Configurator database via XML/CSV planning interface. The above objects are automatically created in plan
import if the target cell does not exist for the imported adjacency. The EXGCE, EXUCE, and EXENBF
with EXEUCE objects are filled with the parameters defined in the first imported adjacency pointing to
the cell. Therefore mandatory parameters for target cell creation are required to be present in the adjacency object. The final set of parameters required for an external cell depends on the type of the incoming adjacencies.

Issue: 1-1

DN03317837

38

Managing Adjacencies

Managing inter-regional adjacencies

Plan modification
You can create, delete, and modify EXGCE / EXUCE / EXENBF and EXEUCE, and unidirectional adjacencies pointing to them in CM Editor. The target cell dependant parameters in an adjacency are always modified only in the target cell. The modifications are then reflected in the incoming adjacencies.
Therefore, the target EXGCE / EXUCE / EXENBF together with EXEUCE has to exist in the plan (new
object) or in actual configuration, otherwise adjacency creation is not possible using Optimizer or CM
Editor. For more information, see Creating the adjacency plan in CM Editor or Optimizer.
EXGCE / EXUCE/ EXENBF and EXEUCE can have templates, and automatic template assignment is
possible for their adjacencies. For more information on templates, see section Adjacency templates.
Plan provisioning
Configurator takes care of updating the incoming adjacencies pointing to the new or modified EXGCE /
EXUCE / EXENBF together with EXEUCE. Plan prepare operation automatically updates/fills in the
values in the incoming adjacencies based on the values in the target EXGCE / EXUCE / EXENBF and
EXEUCE. The changed parameters are updated to the actual configuration during the plan provisioning.
For more details, see section Provisioning the adjacency plan to the network.
Send to Network for GSM, GSM-R, WCDMA and Flexi Direct
In CM Editor, you can create GSM (ADCE, ADJW), GSM-R (ADCE) and WCDMA/ Flexi Direct (ADJS,
ADJD, ADJI, ADJG) objects towards EXGCE and EXUCE directly to the network.
Automatic update of WCDMA and Flexi Direct adjacencies (ADJG/ADJS/ADJI/ADJW) is available only
if the 'CM Activation Options for WCDMA' license is available.
Local management tools
Using local management tools, you can create inter-regional GSM, GSM-R, WCDMA, Flexi Direct, and
LTE adjacencies directly in the network by defining the parameters of the target cell.
Upload and events
When an inter-regional adjacency is created with local management tools, NetAct checks for the existence of the target cell in connection with the events and configuration upload.
In case target cell does not exist in NetAct database actual configuration, a EXGCE / EXUCE /
EXENBF with EXEUCE is automatically created. When EXENBF is created, the division
parameter is empty. After receiving event creating LNADJL or performing upload, the division
parameter is set based on the following values:
if fDlEarfcn has value 035999, then the the division parameter under EXENBF is set
to FDD;

Issue: 1-1

DN03317837

39

Managing Adjacencies

Managing inter-regional adjacencies

if fDlEarfcn has value 3600065535, then the the division parameter under EXENBF is
set to TDD;
if fDlEarfcn is out of range, then the the division parameter under EXENBF is left empty.
In case the target cell exists in NetAct database actual configuration, the EXGCE / EXUCE / EXENBF with EXEUCE is not updated with new parameters provided by the new adjacency.
The external cell is not deleted automatically even though all its incoming adjacencies are deleted or
redirected to another cell. The external cell is deleted automatically only when a corresponding real
cell (matching identification parameters) arrives to NetAct database actual configuration via events or
upload.
Support of the Cell Global Identity feature in BSC
With Support of Cell Global Identity (CGI) feature, the operator can configure and use multiple PLMN
areas within a BSS. The CGI is based on the MCC, MNC, LAC and Cell ID parameters. BSC has also
adjacency index parameter which is a read-only parameter in NetAct. In NetAct, the ADCE instance in
the distinguished name (DN) is created from the LAC and Cell ID parameter values. To avoid having
duplicate ADCE instances, the ADCEs under one BTS must have unique LAC + Cell ID combinations.
For more information on the configurability of the EXGCE instance in DN, see EXGCE identification in
Configurator.
For more information, see Support of Cell Global Identity, dn03282778, in GSM/EDGE RG(BSS) and
GSM-R Railway RGR operating documentation sets.

Issue: 1-1

DN03317837

40

Managing Adjacencies

Verifying and maintaining adjacencies

8 Verifying and maintaining adjacencies


After initial creation of the adjacencies, the performance of the network can be verified and optimized.
The following flowchart illustrates how to maintain and optimize adjacencies. Click a process in a figure for more information. The technologies supported by the tools are specified for each process.

8.1 Checking the actual configuration consistency


It is recommended to start optimizing the adjacencies by checking the actual adjacency parameter
consistency. You can use the CM Analyzer to check adjacencies.
Using CM Analyzer, check the consistency of adjacency data in the actual configuration. Select the actual configuration as the check target. Use auto correction in CM Analyzer if the rule that you are using
supports it.
Note:
Use cron, if you want to schedule the consistency checks.
For instructions on running the consistency checks, see CM Analyzer Help.

Issue: 1-1

DN03317837

41

Managing Adjacencies

Verifying and maintaining adjacencies

For a list of available rule sets, see Rules and Rule Syntax for NetAct Configurator. You can also create your own rules.

8.2 Managing measurements


After checking that the configuration parameters are correct, you can monitor handovers to see the
network performance. Before doing this, you should verify that the necessary measurements are running to get the required PM (performance management) data.

8.2.1 To manage measurements


1. Using Administration of Measurements, ensure that the correct BSC and RNC measurements are
running on each NE. The following measurements should be activated:
Handover measurement (BSC)
Soft handover measurement (RNC)
Inter-system hard handover measurement (RNC)
For more information, see Administration of Measurements Help.
Note:
Turning on this measurement in addition to the other measurements already running, can
cause a considerable load on the NetAct platform. You should therefore consult the system administrator before turning new measurements on. Otherwise, you may overload
the system with network data.
2. Using Thresholder, set up thresholds for HO failure ratio. To concentrate on handover (HO) quality,
you can create an alarm rule that generates an alarm when the HO failure ratio exceeds the target
level (15%).
Note:
The thresholds can only be set for GSM. For WCDMA, the thresholds can be set in OMS.
3. Using NetAct Monitor tools, set your monitoring criteria to include only the threshold alarm. For
more information, see Alarm Filter Editor Help and Rule Editor Help.
Monitoring criteria in NetAct Monitor are used to limit the scope of monitoring, which allows you to
focus on a certain alarm, instead of viewing all incoming alarms. If you want to specifically monitor
a KPI such as the HO success, you can configure NetAct Monitor to only show the threshold alarm
(after you have set the threshold for the HO measurements).

Issue: 1-1

DN03317837

42

Managing Adjacencies

Verifying and maintaining adjacencies

8.3 Managing handover reports


After the measurements required to get the handover related performance data are activated, you can
create / generate handover performance reports.
Before starting to generate reports, check that there is enough statistical fault and performance data in
the database.
In Performance Manager, use existing handover performance reports or create your own handover
performance reports to analyze network performance after implementing adjacency plans to the network.
For more information, see Performance Management Overview.

8.4 Analyzing network performance


Analyze network performance using Performance Manager
To analyze the performance of the network, you can create the same measurement reports that were
run before the implementation of the adjacency changes. When the post-event measurement reports
are ready, compare the pre-event and post-event reports to analyze the effects that the implementation of the new plan had on the quality of the network.
For more information on analyzing network performance in Performance Manager, see Performance
Management Overview.
Analyze network performance in Optimizer
You can analyze network performance in Optimizer. You can visualize key performance indicators
(KPIs) on map and statistics and histograms in Browser.

Issue: 1-1

DN03317837

43

Managing Adjacencies

Adjacency parameters fetched from the target cell

9 Adjacency parameters fetched from the target cell


Adjacency parameters fetched from the target cell are listed in the table below. The adjacency parameters are updated/filled during the Plan Prepare operation.
Only adjacency parameters are read-only in CM Editor.
Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

CI

CI

BTS (NOKBSC)

LAC

LAC

MCC

MCC

MNC

MNC

BSIC BCC

BSIC BCC

BSIC NCC

BSIC NCC

MS Tx Pwr Max GSM

MS Tx Pwr Max GSM

MS Tx Pwr Max GSM 1x00

MS Tx Pwr Max GSM 1x00

IDR Cell Type

IDR Cell Type

DTM Enabled

DTM Enabled

GPRS Enabled

GPRS Enabled

GPRS MS Tx Pwr Max CCH

GPRS MS Txpwr Max CCH

GPRS MS Tx Pwr Max CCH 1x00

GPRS MS Txpwr Max CCH 1x00

RAC

RAC

Name

Name

Priority Class

Priority Class

HCS Threshold

HCS Threshold

Frequency Band in Use

Frequency Band In Use

type
ADCE (NOKBSC)
ADCE (NOKBSCR)

Issue: 1-1

DN03317837

BTS (NOKBSCR)

44

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

BCCH Frequency

Frequency

TRX (NOKBSC)

type
ADCE (NOKBSC)

TRX (NOKBSCR)

ADCE (NOKBSCR)
ADCE (NOKBSC)
ADCE (NOKBSCR)

Issue: 1-1

CI

Cell identity

LAC

LAC

MCC

MCC

MNC

MNC

BSIC BCC

BCC

BSIC NCC

NCC

MS Tx Pwr Max GSM

MS tx pwr max GSM

MS Tx Pwr Max GSM 1x00

MS tx pwr max GSM 1x00

IDR Cell Type

IDR cell type

DTM Enabled

DTM capability

BCCH Frequency

BCCH Frequency

Name

Name

GPRS Enabled

GPRS enabled

GPRS MS Tx Pwr Max CCH

GPRS MS tx pwr max CCH

GPRS Ms Tx Pwr Max CCH 1x00

GPRS Ms tx pwr max CCH 1x00

RAC

RAC

Priority Class

Priority class

HCS Threshold

HCS threshold

Frequency Band in Use

SYS id

DN03317837

EXGCE (com.nsn.
vimext)

45

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

type
Frequency Band In Use is
set based on the EXGCE Sys id
value the following way:
When Sys id equal to GSM
850, then Frequency Band
in Use is set to GSM800
When Sys id equal to
EXT900, then Frequency
Band in Use is set to
GSM900
When Sys id equal to DCS
1800, then Frequency
Band in Use is set to
GSM1800
When Sys id equal to PCS
1900, then Frequency
Band in Use is set to
GSM1900
When Sys id equal to GSMR,
then Frequency Band in
Use is set to GSMR.
If SYS id is empty in EXGCE,
then Frequency Band In
Use is set on the basis of
BCCH frequency in EXGCE.
For overlapping frequencies,
Frequency Band In Use is set
based on configurator properties
(ossRacFrequencyBandInUse)
settings.
ADJW (NOKBSC)

RNC ID

RNC Identifier

MCC

Common MCC

MNC

Common MNC

RNC (NOKRNC)
RNC (com.nsn.
mcrnc)
IADA (NOKIHIADA)

Issue: 1-1

DN03317837

46

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

Cell identification

Cell identifier

WCEL (NOKRNC)

LAC

Location area code

Service Area Code

Service Area Code

Name

Name

Scrambling Code

Primary downlink scrambling code

type
ADJW (NOKBSC)

WCEL (com.nsn.
mcrnc)
WCEL (NOKIHIADA)

WCDMA Downlink Carrier Frequen- UTRA Absolute Radio Frequency

ADJW (NOKBSC)

cy

Channel Number

RNC ID

RNC id

MCC

MCC

MNC

MNC

Cell ID

Cell identifier

Name

Name

LAC

LAC

Service Area Code

SAC

Scrambling Code

Primary scrambling code

EXUCE (com.nsn.
vimext)

WCDMA Downlink Carrier Frequen- UARFCN downlink


cy
ADJS
(NOKRNC)
ADJS (com.
nsn.mcrnc)

RNC Identifier

RNC Identifier

Mobile Country Code

Common MCC

Mobile Network Code

Common MNC

ADJS

RNC (NOKRNC)
RNC (com.nsn.
mcrnc)
IADA (NOKIHIADA)

(NOKIHIADA)
ADJS

Cell Identifier

Cell identifier

WCEL (NOKRNC)

(NOKRNC)

Issue: 1-1

DN03317837

47

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Name

Name

Location Area Code

Location area code

Routing Area Code

Routing Area Code

Primary Scrambling Code

Primary downlink scrambling code

Primary CPICH Power

Transmission power of the primary

Object class

type
ADJS (com.
nsn.mcrnc)
ADJS
(NOKIHIADA)

WCEL (com.nsn.
mcrnc)
WCEL (NOKIHIADA)

CPICH channel
Maximum UE TX Power on RACH

Maximum UE transmission power


on PRACH

ADJS
(NOKRNC)
ADJS (com.
nsn.mcrnc)

RNC Identifier

RNC id

Mobile Country Code

MCC

Mobile Network Code

MNC

ADJS

(NOKIHIADA) Cell Identifier

EXUCE (com.nsn.
vimext)

Cell identifier

Name

Name

Location Area Code

LAC

Routing Area Code

RAC

Primary Scrambling Code

Primary scrambling code

Primary CPICH Power

Primary CPICH tx power

Maximum UE TX Power on RACH

Maximum UE transmission power


on RACH

ADJI
(NOKRNC)
ADJI (com.
nsn.mcrnc)

RNC Identifier

RNC Identifier

Mobile Country Code

Common MCC

Mobile Network Code

Common MNC

ADJI

RNC (NOKRNC)
RNC (com.nsn.
mcrnc)
IADA (NOKIHIADA)

(NOKIHIADA)

Issue: 1-1

DN03317837

48

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

Cell Identifier

Cell identifier

WCEL (NOKRNC)

Name

Name

Location Area Code

Location area code

type
ADJI
(NOKRNC)
ADJI (com.
nsn.mcrnc)
ADJI

(NOKIHIADA) Routing Area Code

Routing Area Code

Primary Scrambling Code

Primary downlink scrambling code

UTRA Absolute Radio Frequency

UTRA Absolute Radio Frequency

Channel Number

Channel Number

Primary CPICH Power

Transmission power of the primary

WCEL (com.nsn.
mcrnc)
WCEL (NOKIHIADA)

CPICH channel
Maximum UE TX Power on DPCH

Maximum UE transmission power


on DPCH

Maximum UE TX Power on RACH

Maximum UE transmission power


on RACH

ADJI
(NOKRNC)
ADJI (com.
nsn.mcrnc)

RNC Identifier

RNC id

Mobile Country Code

MCC

Mobile Network Code

MNC

ADJI

(NOKIHIADA) Cell Identifier

EXUCE (com.nsn.
vimext)

Cell identifier

Name

Name

Location Area Code

LAC

Routing Area Code

RAC

Primary Scrambling Code

Primary scrambling code

UTRA Absolute Radio Frequency

UARFCN downlink

Channel Number
Primary CPICH Power

Issue: 1-1

Primary CPICH tx power

DN03317837

49

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Maximum UE TX Power on DPCH

Maximum UE transmission power

Object class

type

on DPCH
Maximum UE TX Power on RACH

Maximum UE transmission power


on RACH

ADJD
(NOKRNC)
ADJD (com.
nsn.mcrnc)

RNC Identifier

RNC Identifier

Mobile Country Code

Common MCC

Mobile Network Code

Common MNC

ADJD

RNC (NOKRNC)
RNC (com.nsn.
mcrnc)
IADA (NOKIHIADA)

(NOKIHIADA)
ADJD
(NOKRNC)
ADJD (com.
nsn.mcrnc)

Cell Identifier

Cell identifier

Name

Name

Location Area Code

Location area code

ADJD

(NOKIHIADA) Routing Area Code

Routing Area Code

Primary Scrambling Code

WCEL (NOKRNC)
WCEL (com.nsn.
mcrnc)
WCEL (NOKIHIADA)

Primary Downlink Scrambling


Code

Primary CPICH Power

Transmission power of the primary


CPICH channel

ADJD

RNC Identifier

RNC id

Name

Name

Mobile Country Code

MCC

(NOKIHIADA) Mobile Network Code

MNC

(NOKRNC)
ADJD (com.
nsn.mcrnc)
ADJD

Issue: 1-1

Cell Identifier

Cell identifier

Location Area Code

LAC

Routing Area Code

RAC

DN03317837

EXUCE (com.nsn.
vimext)

50

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Primary Scrambling Code

Primary scrambling code

Primary CPICH Power

Primary CPICH tx power

Cell Identifier

CI

Location Area Code

LAC

Mobile Country Code

MCC

(NOKIHIADA) Mobile Network Code

MNC

Name

Name

Base Station Colour Code

BSIC BCC

Network Colour Code

BSIC NCC

Band Indicator

Frequency Band In Use

Maximum UE TX Power on RACH

GSM 800/900:

Object class

type

ADJG
(NOKRNC)
ADJG (com.
nsn.mcrnc)
ADJG

BTS (NOKBSC)

MS Tx Pwr Max CCH when MS


Tx Pwr Max CCH > GPRS MS Txpwr Max CCH
GPRS MS Txpwr Max CCH when
MS Tx Pwr Max CCH <= GPRS
MS Txpwr Max CCH
GSM 1800/1900:
MS Tx Pwr Max CCH 1x00 when
MS Tx Pwr Max CCH 1x00 >
GPRS MS Txpwr Max CCH 1x00
GPRS MS Txpwr Max CCH 1x00
when MS Tx Pwr Max CCH 1x00
<= GPRS MS Txpwr Max CCH
1x00
Maximum UE TX Power on TCH

GSM 800/900: msTxPwrMaxGSM


(GSM 800/900)

Issue: 1-1

DN03317837

51

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

type
GSM 1800/1900:
msTxPwrMaxGSM1x00
BCCH ARFCN

Frequency

TRX - BCCH
(NOKBSC)

ADJG
(NOKRNC)
ADJG (com.
nsn.mcrnc)

Base Station Colour Code

BCC

BCCH ARFCN

BCCH frequency

Band Indicator

SYS id

ADJG

EXGCE (com.nsn.
vimext)

Band Indicator is set based

(NOKIHIADA)

on the EXGCE Sys id value in


the following way:
When Sys id equal
to GSM850, then Band
Indicator is set to 900,
850 and 1800.
When Sys id equal
to EXT900, then Band
Indicator is set to 900,
850 and 1800.
When Sys id equal to
DCS1800, then Band
Indicator is set to 900,
850 and 1800.
When Sys id equal to
PCS1900, then Band
Indicator is set to 1900.
If SYS id is empty in EXGCE,
then Band Indicator is
set on the basis of BCCH
frequency in EXGCE. For
overlapping frequencies
frequencyBandInUse is set
based on configurator properties
(ossRacFrequencyBandInUse)
settings.

Issue: 1-1

DN03317837

52

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Cell Identifier

Cell identity

Location Area Code

LAC

Mobile Country Code

MCC

Mobile Network Code

MNC

Network Colour Code

NCC

Maximum UE TX Power on RACH

GSM 800/900:

Object class

type

MS tx pwr max CCH when MS txpwr max CCH > GPRS MS tx pwr
max CCH
GPRS MS tx pwr max CCH when
MS tx pwr max CCH <= GPRS
MS tx pwr max CCH
GSM 1800/1900:
MS tx pwr max CCH 1x00 when
MS tx pwr max CCH 1x00 >
GPRS MS tx pwr max CCH 1x00
GPRS MS tx pwr max CCH 1x00
when MS tx pwr max CCH 1x00
<= GPRS MS tx pwr max CCH
1x00
Maximum UE TX Power on TCH

GSM 800/900:
Ms tx pwr max GSM
GSM 1800/1900:
Ms tx pwr max GSM 1x00

Name

Name

ADJE

Inter-RAT LTE adjacent physical cell Physical layer cell identity

(NOKRNC)

identifier
Cell ID

Issue: 1-1

LNCEL (NOKLTE)

Local cell resource ID

DN03317837

53

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Tracking Area Code

Tracking Area Code

Name

Name

Mobile Country Code

Mobile Country Code

Mobile Network Code

Mobile Network Code

Macro eNB ID

Macro eNB identifier (LNBTS in-

Object class

type

ADJE
(NOKRNC)

LNBTS (NOKLTE)

stance)
ADJE

Inter-RAT LTE adjacent physical cell Physical cell identity

EXEUCE (com.

(NOKRNC)

identifier

nsn.vimext)

Cell ID

Local cell resource ID

Tracking Area Code

Tracking Area Code

Name

Name

Mobile Country Code

MCC

Mobile Network Code

MNC

Macro eNB ID

Macro eNB ID

LNADJ

C-Plane IP address of neighbor

Control plane IP address

IPNO (NOKLTE)

(NOKLTE)

eNB (X2 only)

LNADJ

Identity of neighbor eNB within

Macro eNB identifier

LNBTS (NOKLTE)

(NOKLTE)

PLMN (S1 only)

ADJE
(NOKRNC)

Primary PLMN identity of neighbor

EXENBF (com.
nsn.vimext)

MCC in PLMN

eNB - MCC in primary PLMN identity of neighbor eNB (S1 only)


Primary PLMN identity of neighbor

MNC in PLMN

eNB - MNC in primary PLMN identity of neighbor eNB (S1 only)


Name

Issue: 1-1

Name

DN03317837

54

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

LNADJ

C-Plane IP address of neighbor

C-plane IP address

EXENBF (com.

(NOKLTE)

eNB (X2 only)

type

nsn.vimext)

Identity of neighbor eNB within

Macro eNB identifier

PLMN (S1 only)


Primary PLMN identity of neighbor

MCC

eNB - MCC In Primary PLMN Identity Of Neighbour ENB (S1 only)


Primary PLMN identity of neighbor

MNC

eNB - MNC In Primary PLMN Identity Of Neighbour ENB (S1 only)


Name

Name

LNADJL

Local cell resource ID of related

Local cell resource ID

(NOKLTE)

neighbor cell

- S1-based
link only; for
X2-based link
LNADJL is
created and
configured by
eNB

MCC in broadcast PLMN identity

LNCEL (NOKLTE)

Mobile country code

(Broadcast PLMN identity list )


MNC in broadcast PLMN identity

Mobile network code

(Broadcast PLMN identity list )


Downlink EARFCN of LTE cell

EARFCN downlink

served by neighbor eNB


Physical cell ID of cell served by

Physical layer cell identity

neighbor eNB
Tracking area code of cell served by Tracking area code
neighbor eNB
LNADJL
(NOKLTE)
- S1-based
link only; for
X2-based link
LNADJL is

Identity of neighbor eNB in ECGI

Macro eNB identifier

Primary PLMN identity of neighbor

MCC in PLMN

LNBTS (NOKLTE)

LTE cell in ECGI - MCC in primary


PLMN identity of neighbour ENB in
ECGI

created and

Issue: 1-1

DN03317837

55

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Primary PLMN identity of neighbor

MNC in PLMN

Object class

type
configured by
eNB

LTE cell in ECGI - MNC in primary


PLMN identity of neighbour ENB in
ECGI

LNADJL

Local cell resource ID of related

(NOKLTE)

neighbor cell

- S1-based
link only; for
X2-based link
LNADJL is
created and
configured by
eNB

Local cell resource identifier

EXEUCE (com.
nsn.vimext)

MCC in broadcast PLMN identity

MCC

(Broadcast PLMN identity list )


MNC in broadcast PLMN identity

MNC

(Broadcast PLMN identity list )


Downlink EARFCN of LTE cell

EARFCN downlink

served by neighbor eNB


Physical cell ID of cell served by

Physical cell identity

neighbor eNB
Tracking area code of cell served by Tracking area code
neighbor eNB
LNADJL
(NOKLTE)
- S1-based
link only; for
X2-based link
LNADJL is
created and
configured by
eNB

Identity of neighbor eNB in ECGI


Primary PLMN identity of neighbor

Macro eNB identifier


MCC

EXENBF (com.
nsn.vimext)

LTE cell in ECGI - MCC in primary


PLMN identity of neighbour ENB in
ECGI
Primary PLMN identity of neighbor

MNC

LTE cell in ECGI - MNC in primary


PLMN identity of neighbour ENB in
ECGI

LNADJW

Target RNC id

RNC Identifier

(NOKLTE)

RNC (NOKRNC)
RNC (com.nsn.
mcrnc)
IADA (NOKIHIADA)

Issue: 1-1

DN03317837

56

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

type
LNADJW
(NOKLTE)

Target primary PLMN identity - MCC Mobile Country Code


Target primary PLMN identity - MNC Mobile Network Code
Target cell id

Cell identifier

Target frequency

UTRA Absolute Radio Frequency

WCEL (NOKRNC)
WCEL (com.nsn.
mcrnc)
WCEL (NOKIHIADA)

Channel Number

LNADJW
(NOKLTE)

Target location area code

Location area code

Target routing area code

Routing Area Code

Primary scrambling code (FDD)

Primary downlink scrambling code

Name

Name

Target RNC id

RNC id

Target primary PLMN identity - MCC MCC

EXUCE (com.nsn.
vimext)

Target primary PLMN identity - MNC MNC

LNRELW

Target cell id

Cell identifier

Target frequency

UARFCN downlink

Target location area code

LAC

Primary scrambling code (FDD)

Primary scrambling code

Name

Name

Target RNC Id

RNC Identifier

(NOKLTE)

RNC (NOKRNC)
RNC (com.nsn.
mcrnc)
IADA (NOKIHIADA)

LNRELW

Target cell Id in UTRAN CGI of re-

(NOKLTE)

lated neighbor cell

Issue: 1-1

DN03317837

Cell identifier

WCEL (NOKRNC)

57

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Primary PLMN identity in CGI of

Mobile Country Code

Object class

type

UTRAN neighbor cell - MCC


Primary PLMN identity in CGI of

Mobile Network Code

UTRAN neighbor cell - MNC


Target frequency

WCEL (com.nsn.
mcrnc)
WCEL (NOKIHIADA)

UTRA Absolute Radio Frequency


Channel Number

LNRELW
(NOKLTE)

Target location area code

Location area code

Target routing area code

Routing Area Code

Primary scrambling code (FDD)

Primary downlink scrambling code

Name

Name

Target RNC Id

RNC id

Target cell Id in UTRAN CGI of re-

Cell identifier

EXUCE (com.nsn.
vimext)

lated neighbor cell


Primary PLMN identity in CGI of

MCC

UTRAN neighbor cell - MCC


Primary PLMN identity in CGI of

MNC

UTRAN neighbor cell - MNC

LNADJG

Target frequency

UARFCN downlink

Target location area code

LAC

Target routing area code

RAC

Primary scrambling code (FDD)

Primary scrambling code

Name

Name

ARFCN value geran

Frequency

TRX (NOKBSC)

(NOKLTE)

Issue: 1-1

DN03317837

58

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

Band indicator geran

Band indicator geran is set based

BTS (NOKBSC)

type
LNADJG
(NOKLTE)

on the BTS Frequency Band


In Use value in the following
way:
When BTS Frequency Band
In Use is equal to GSM800,
then Band indicator
geran is set to dcs1800.
When BTS Frequency
Band In Use is equal
to GSM900, then Band
indicator geran is set to
dcs1800.
When BTS Frequency
Band In Use is equal
to GSM1800, then Band
indicator geran is set to
dcs1800.
When BTS Frequency
Band In Use is equal
to GSM1900, then Band
indicator geran is set to
pcs1900.

Issue: 1-1

Basestation colour code

BSIC BCC

DTM capability

DTM Enabled

CI GERAN

CI

LAC GERAN

LAC

RAC GERAN

RAC

MCC GERAN

MCC

MNC GERAN

MNC

Network colour code

BSIC NCC

DN03317837

59

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Name

Name

ARFCN value geran

BCCH frequency

Band indicator geran

SYS id

Object class

type

LNADJG
(NOKLTE)

EXGCE (com.nsn.
vimext)

Band indicator geran is set


based on the EXGCE Sys id
value in the following way:
When Sys id is equal
to GSM850, then Band
indicator geran is set to
dcs1800.
When Sys id is equal
to EXT900, then Band
indicator geran is set to
dcs1800.
When Sys id is equal
to DCS1800, then Band
indicator geran is set to
dcs1800.
When Sys id is equal
to PCS1900, then Band
indicator geran is set to
pcs1900.
When SYS id is empty in
EXGCE, then Band indicator
geran is set on the basis of
BCCH frequency in EXGCE.
For overlapping frequencies
Band indicator geran is set
based on configurator properties
(ossRacFrequencyBandInUse)
settings.

Issue: 1-1

Basestation colour code

BCC

DTM capability

DTM capability

DN03317837

60

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

Object class

CI GERAN

Cell identity

LAC GERAN

LAC

RAC GERAN

RAC

MCC GERAN

MCC

MNC GERAN

MNC

Network colour code

NCC

Name

Name

ARFCN value geran

Frequency

TRX (NOKBSC)

Cell identity

CI

BTS (NOKBSC)

Location Area Code

LAC

PLMN Identity in CGI of GERAN

MCC

type

LNRELG
(NOKLTE)
LNRELG
(NOKLTE)

neighbor cell - MCC


PLMN Identity in CGI of GERAN

MNC

neighbor cell - MNC

LNRELG
(NOKLTE)

Issue: 1-1

Basestation colour code

BSIC BCC

DTM capability

DTM Enabled

Network colour code

BSIC NCC

RAC GERAN

RAC

Name

Name

ARFCN value geran

BCCH frequency

Cell identity

Cell identity

Location Area Code

LAC

DN03317837

EXGCE (com.nsn.
vimext)

61

Managing Adjacencies

Adjacency parameters fetched from the target cell

Object class
- adjacency

Adjacency parameter

Target cell parameter

PLMN Identity in CGI of GERAN

MCC

Object class

type

neighbor cell - MCC


PLMN Identity in CGI of GERAN

MNC

neighbor cell - MNC


Basestation colour code

BCC

DTM capability

DTM capability

Network colour code

NCC

RAC GERAN

RAC

Name

Name

Table 4: Adjacency parameters fetched from the target cell or target BTS

Issue: 1-1

DN03317837

62

Managing Adjacencies

Importing user templates required for the LTE Inter-RAT


UTRAN / GERAN automatic management features

10 Importing user templates required for the LTE


Inter-RAT UTRAN / GERAN automatic management
features
In order to be able to use the automatic management of the LTE Inter-RAT UTRAN/GERAN relations,
which is automatically performed by the Plan Prepare functionality, user templates for the certain managed object classes have to exist in NetAct Configurator.
User templates for the following managed object classes are required:
For ANR Inter-RAT UTRAN:
LNHOW
REDRT
UFFIM
For ANR Inter-RAT GERAN:
LNHOG
REDRT
GFIM
GNFL
Required user templates for above managed object classes are available in NetAct environment as
XML files, but they need to be manually imported to NetAct Configurator template database before using the ANR Inter-RAT UTRAN/GERAN automatic management features.
Required user templates are originally stored as XML files in the following location:
/etc/opt/nokia/oss/rac/conf/profiles
To import required user templates into NetAct Configurator template database:
1. Log in to the Connectivity Server as the omc user.
2. Copy all the user template XML files from the /etc/opt/nokia/oss/rac/conf/profiles/
directory to the /var/opt/nokia/oss/global/racops/import/ directory.
There are the following files to be copied from this directory:
ANR_inter_RAT_UTRAN_LNHOW_user_template.xml
ANR_inter_RAT_UTRAN_UFFIM_user_template.xml
ANR_inter_RAT_UTRAN_REDRT_user_template.xml
ANR_inter_RAT_GERAN_LNHOG_user_template.xml
ANR_inter_RAT_GERAN_REDRT_user_template.xml
ANR_inter_RAT_GERAN_GNFL_user_template.xml
ANR_inter_RAT_GERAN_GFIM_user_template.xml

Issue: 1-1

DN03317837

63

Managing Adjacencies

Importing user templates required for the LTE Inter-RAT


UTRAN / GERAN automatic management features

3. Run the following command to import template files and to get the user templates created into
NetAct Configurator template database:
racclimx.sh -op Import_Export -importExportOperation templateImport fileName <file name> v
where <file name> is the name of template file to be imported.
Note:
You have to repeat the import command for all the required user template XML files.
After all the user templates required for ANR Inter-RAT UTRAN/GERAN auto management features
are imported to NetAct Configurator you have to check their parameter values and modify them according to your requirements. This is needed because provided ready-made user templates contain
only examplary values.
You can preview and modify imported user templates using CM Editor the same way as any other user
templates.
The names of imported user templates are:
ANR inter RAT UTRAN - for managed object classes required for Inter-RAT UTRAN relations
management (LNHOW, REDRT, UFFIM)
ANR inter RAT GERAN - - for managed object classes required for Inter-RAT UTRAN relations
management (LNHOG, REDRT, GFIM, GNFL)
Note:
There are certain mandatory user template parameters that must not be changed after the
template is imported to NetAct Configurator. See below sections for a guidance for user template parameters.

10.1 ANR inter RAT UTRAN user templates


LNHOW user template parameter values:
Utran carrier frequency (utraCarrierFreq) - no parameter value needed in template;
parameter value set automatically by the auto management feature (Plan Prepare)
all other parameter values defined in the template, but they can be modified as needed
REDRT user template parameter values:
UTRA frequency (redirFreqUtra) - no parameter value needed in template; parameter value
set automatically by the auto management feature (Plan Prepare)
Redirection priority for CS fallback with redirection (csFallBPrio) = 1
Redirection priority for emergency call (emerCallPrio) = 1
Redirection priority for UE context release (redirectPrio) = 3

Issue: 1-1

DN03317837

64

Managing Adjacencies

Importing user templates required for the LTE Inter-RAT


UTRAN / GERAN automatic management features

RAT for redirect (redirRat) = 2 - utraFDD - this is mandatory value for correct UE
behavior, you must not set other value
GERAN band indicator (redirGeranBandIndicator) = 2 - notUsed - this is
mandatory value in UTRAN case, you must not set other value
CDMA band (redirBandCdma) = 18 - notUsed
CDMA frequency (redirFreqCdma) = 65535 - notUsed
eUTRA frequency (redirFreqEutra) = 100000 - notUsed
UFFIM user template parameter values:
utrResTiFHM, utrResTiFMM, tResUtra - values can be defined as needed
one structure (Structure 1) has to be created for the structured parameter UTRA carrier
frequencies list (utrFddCarFrqL)
UTRA Downlink Frequency Value (dlCarFrqUtra) - no parameter value needed in
template; parameter value set automatically by the auto management feature (Plan Prepare)
all other Structure 1 parameter values can be defined as needed
Note:
You should not create more structures into template.

10.2 ANR inter RAT GERAN user templates


LNHOG user template parameter values:
ARFCN frequency band indicator and ARFCN value list - no parameter value needed
in template; parameter value set automatically by the auto management feature (Plan Prepare)
all other parameter values defined in the template, but they can be modified as needed
REDRT user template parameter values:
GERAN band indicator and GERAN ARFCN values list - no parameter value needed in
template; parameter value set automatically by the auto management feature (Plan Prepare)
RAT for redirect (redirRat) = 1 - geran - this is mandatory value for correct UE
behavior, you must not set other value
Redirection priority for CS fallback with redirection (csFallBPrio) = 3
Redirection priority for emergency call (emerCallPrio) = 3
Redirection priority for UE context release (redirectPrio) = 4
all other parameter values = not used
GFIM user template parameter values:
all parameter values defined in the template, but they can be modified as needed
GNFL user template parameter values:

Issue: 1-1

DN03317837

65

Managing Adjacencies

Importing user templates required for the LTE Inter-RAT


UTRAN / GERAN automatic management features

ARFCN value list and GERAN frequency band indicator - no parameter value needed
in template; parameter value set automatically by the auto management feature (Plan Prepare)
all other parameter values defined in the template, but they can be modified as needed

Issue: 1-1

DN03317837

66