NetAct 8 EP1 Managing_adjacencies (2)

8/10/2019 NetAct 8 EP1 Managing_adjacencies (2)

http://slidepdf.com/reader/full/netact-8-ep1-managingadjacencies-2 1/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 whichthe 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. IN NO

EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS

IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT

LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL

OR ANY LOSSES, SUCH A S BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE,

BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY

ARISE FRO M THE USE OF THI S DO CU MENT OR THE INFORMATION IN IT.

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.




3

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 Prerequisites for the operation................................................................................................................29

4.2 Uploading actual configuration................................................................................................................30

4.3 Creating the adjacency plan in a planning tool...................................................................................... 30

4.4 Creating the adjacency plan in CM Editor or Optimizer.........................................................................31

4.5 Completing the adjacency plan...............................................................................................................31

4.6 Checking the adjacency plan..................................................................................................................32

4.7 Approving the adjacency plan.................................................................................................................33

4.8 Provisioning the adjacency plan to the network..................................................................................... 33

4.9 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 par ameters fetched from the target cell.................................................................................. 44

10 Importing user templates required for the LTE Inter-RAT UTRAN / GERAN automatic management

features........................................................................................................................................................ 63




4

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

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



Managing Adjacencies Adjacency management overview

Issue: 1-1 DN03317837 5

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 adjacen-

cy 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:

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/release_changes/common/supported_network_element_changes.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/release_changes/common/supported_network_element_changes.html




Issue: 1-1 DN03317837 6

Initial planning

The initial set of adjacencies is defined in BTS site creation. Templates can be used in adjacency cre-

ation and less manual parameter input is needed. The adjacencies can be added to the site creationplan 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 dis-

tance 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 imple-

mented directly to the network.

Optimizer can utilise mobile measurements collected and reported by a BSC in adjacency optimiza-

tion. By analyzing the KPIs, the unused adjacent cells can be identified and removed from the adja-

cency 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 ad-

jacency list of each cell. The new adjacency plan can be visualized, modified, if necessary, and sched-

uled 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 know-

ing 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 net-

work before handover statistics can be collected for them. For this reason, Optimizer can make rota-

tion 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 configura-

tion and correct adjacencies of one region at a time (CM Analyzer). You can visualize problematic ad-

jacencies, for example, those with low handover success rate values, on top of map and check/modi-

fy adjacency parameters (Optimizer). In order for you to see cells and adjacencies on the map, the siteand antenna data must be up to date.




Issue: 1-1 DN03317837 7

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

the network.



Managing Adjacencies Adjacency types

Issue: 1-1 DN03317837 8

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 In-

terface 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

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/csv_interface_for_configuration_management_data/common/concepts/csv_file_format_overview-d14e74.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/xml_interface_for_configuration_management_data/common/concepts/xml_interface_overview-d14e185.html





Issue: 1-1 DN03317837 9

Figure 3: GSM and WCDMA inter-regional adjacency types

The following table introduces GSM and WCDMA adjacency types:

Adjacency

type

Adjacency

ID

Source

Cell

Target

Cell

Source Cell Iden-

tification

Target Cell

Identification

Handover

types

ADCE

(GSM <->

GSM)

LAC + Cell

ID

(0-31)

BTS BTS / Ex-

ternal

GSM cell

Cell Global Identi-

fier (MCC, MNC,

LAC, CI)

Cell Glob-

al Identifier

(MCC, MNC,

LAC, CI)

Hard




Issue: 1-1 DN03317837 10

Adjacency

type

Adjacency

ID

Source

Cell

Target

Cell

Source Cell Iden-

tification

Target Cell

Identification

Handover

types

ADJW

(GSM -> WCD-

MA)

inter-system

ADJW ID

(0-31)

BTS WCEL /external

UTRAN

cell

Cell Global Identi-fier (MCC, MNC,

LAC, CI)

Global UtranCell Identifier

(MCC, MNC,

RNC ID, CI)

Hard, in-ter-system

ADJS

(WCDMA <->

WCDMA)

intra-frequency

ADJS ID

(1-31)

WCEL WCEL /

external

UTRAN

cell

Global Utran Cell

Identifier (MCC,

MNC, RNC ID, CI)

Global Utran

Cell Identifier

(MCC, MNC,

RNC ID, CI)

Soft, soft-

er, hard (in-

ter-RNC)

ADJD

(WCDMA <->

WCDMA)

intra-frequency

ADJD ID

(0-31)

WCEL WCEL /

external

UTRAN

cell

Global Utran Cell

Identifier (MCC,

MNC, RNC ID, CI)

Global Utran

Cell Identifier

(MCC, MNC,

RNC ID, CI)

Soft Han-

dover Based

on Detected

Set Report-

ing (optional

feature)3

ADJI

(WCDMA <->

WCDMA)

inter-frequency

ADJI ID

(0-47)

WCEL WCEL /

external

UTRAN

cell

Global Utran Cell

Identifier (MCC,

MNC, RNC ID, CI)

Global Utran

Cell Identifier

(MCC, MNC,

RNC ID, CI)

Hard, in-

ter-frequen-

cy

ADJG

(WCDMA ->

GSM)

inter-system

ADJG ID

(0-31)

WCEL BTS / Ex-

ternal

GSM cell

Global Utran Cell

Identifier (MCC,

MNC, RNC ID, CI)

Cell Glob-

al Identifier

(MCC, MNC,

LAC, CI)

Hard, in-

ter-system

ADJE

(WCDMA ->

LTE)

inter-system

ADJE ID

(0-63)

WCEL LNCEL /

external

LTE cell

Global Utran Cell

Identifier (MCC,

MNC, RNC ID, CI)

Global eNB ID

(LNBTS ID +

MCC + MNC)

Hard, in-

ter-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 11

2 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 ac-

tive 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 dif-

ferent 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 ac-

tive 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 unidirec-

tional 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 ob-

jects.

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 de-

scribed in this document. Region in the picture below refers to a radio network managed by one net-

work management system.




Issue: 1-1 DN03317837 12

Figure 4: LTE adjacency types

The following table introduces LTE adjacency types:

Adjacency typeSource

Cell

Target

Cell

Source Cell Iden-

tification

Target Cell Identi-

ficationHandover types

LTE ↔ LTE INTRA-SYSTEM ADJACENCIES AND HANDOVERS




Issue: 1-1 DN03317837 13

Adjacency typeSource

Cell

Target

Cell

Source Cell Iden-

tification

Target Cell Identi-

ficationHandover types

LNBTS LNBTSEXENBF

Global eNB ID(LNBTS ID +

MCC + MNC)

Global eNB ID(LNBTS ID + MCC

+ MNC)

LNADJ (eNB)

LNADJL (cell)

(LTE <-> LTE)

intra-frequency

(via X2/S1)

inter-frequency

(via S1 only)

LNCEL LNCEL

EXEUCE

Global eNB ID +

LCR ID

Global eNB ID +

LCR ID

Hard handover via X2/S1 inter-

face

LTE → WCDMA / FLEXI DIRECT INTER-RAT ADJACENCIES AND HANDOVERS

LNADJW

(LTE -> WCDMA)

LNADJW

(LTE -> Flexi Di-

rect)

LNBTS WCEL

EXUCE

Global eNB ID

(LNBTS ID +

MCC + MNC)

Global Utran Cell

Identifier (MCC,

MNC, RNC ID, CI)

LNRELW

(LTE -> WCDMA)

LNRELW

(LTE -> Flexi Di-

rect)

LNCEL WCEL

EXUCE

Global eNB ID +

LCR ID

Global Utran Cell

Identifier (MCC,MNC, RNC ID, CI)

Hard handover

LTE → GSM INTER-RAT ADJACENCIES AND HANDOVERS

LNADJG

(LTE -> GSM)

LNBTS BTS

EXGCE

Global eNB ID

(LNBTS ID +

MCC + MNC)

Cell Global Identi-

fier (MCC, MNC,

LAC, CI)

LNRELG

(LTE -> GSM)

LNCEL BTS

EXGCE

Global eNB ID +

LCR ID

Cell Global Identi-

fier (MCC, MNC,

LAC, CI)

Hard handover

Table 2: LTE adjacency and handover types

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




Issue: 1-1 DN03317837 14

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 Cre-

ating 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 dif-

ferent 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 suc-

cessfully 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 tocorresponding LNADJL objects. LNADJL is the read-only object in NetAct Configurator.




Issue: 1-1 DN03317837 15

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 in-

tra-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 unidirec-

tional 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 Config-

uration Management Data and CSV Interface for Configuration Management Data documents.

The following figure explains the intra-system adjacencies handling:




Issue: 1-1 DN03317837 16

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 pur-

pose, 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 adjacen-

cies 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 X2-

based 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 17

• 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 enbCon-trolled 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 con-

sistent.

• 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 manage-

ment 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 / GER-

AN automatic management features.

Note:




Issue: 1-1 DN03317837 18

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 man-

age relationships and handovers between LTE and WCDMA / Flexi Direct cells. Adjacencies to ex-

ternal WCDMA / Flexi Direct cells (managed by another network management system) are also sup-

ported. 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 (WCD-

MA / Flexi Direct cell or external WCDMA / Flexi Direct cell).

• LNADJW is used for adjacencies between all LNBTS’s (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 im-

ported 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 LNBTS’s cells and WCEL / EXUCE) can be created in CM Editor by

selecting desired source LNBTS and target WCEL (or EXUCE) and clicking ‘Create Unidirectional Ad-

jacency’. 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 19

• creates LNRELW outgoing adjacency object in all LNCELs of source LNBTS

• creates LNRELW incoming adjacency objects in the target WCEL / EXUCE coming from each LN-

CEL 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 Ad- jacency’. 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 20

• 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 adja-cency, and later it will be used as target for adjacency creation from WCDMA/Flexi Direct or GSM net-

works, then EXGCE/EXUCE might be missing some mandatory parameters and cause adjacency cre-

ation 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) de-

pending on the incoming adjacencies that deleted EXGCE/EXUCE had.

Expected result




Issue: 1-1 DN03317837 21

The correct and complete EXGCE/EXUCE is created and corresponding incoming adjacencies are re-

targeted.

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 con-

sistent.

• 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 / GER-

AN 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 anoth-

er 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 LNBTS’s (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 import-

ed 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 con-

tent

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/configurator_technical_reference/Common/reference/configuration_data_directories.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/configurator_technical_reference/Common/reference/configuration_data_directories.html




Issue: 1-1 DN03317837 22

– 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 LNBTS’s cells and BTS / EXGCE) can be created in CM Editor by se-

lecting 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 23

Figure 8: LNADJG adjacency handling

LNRELG adjacency planning

LNRELG adjacency (between one LNCEL and one BTS / EXGCE) can be created in CM Editor by se-

lecting desired source LNCEL and target BTS (or EXGCE) and clicking ‘Create Unidirectional Adja-

cency’. As a result the LNRELG is created in source LNCEL (outgoing) and target BTS / EXGCE (in-

coming).

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 26

External GSM cell (EXGCE)External UTRAN cell

(EXUCE)

External E-

UTRAN cell

(EXEUCE)

• DTM Enabled

• GPRS MS Tx Pwr Max

CCH

• GPRS MS Tx Pwr Max

CCH 1x00 (GSM 1800/

GSM1900)

• Initial Frequency

(BCCH TRX parameter)

In CM Editor, you can define

the same parameters for exter-nal GSM cell as for real BTSs.

• Primary

Scrambling Code

• RNC Id

• Routing Area

Code

• Service Area

Code

• UARFCN DL

• UARFCN UL

Location

information

Location information is need-

ed for SITE object attached to

external GSM cell for visualiz-

ing external GSM cell in Opti-

mizer. Location information can

be defined using Antenna Data

Editor tool provided with Opti-

mizer. Location information can

also be defined in CM Editor

(SITE object assignment).

Location information is

needed for SITE object at-

tached to external UTRAN

cell for visualizing external

UTRAN cell in Optimizer.

Location information can

be defined using Anten-

na Data Editor tool provid-

ed with Optimizer. Loca-

tion information can also

be defined in CM Editor

(SITE object assignment).

Table 3: Inter-regional adjacencies



Managing Adjacencies Adjacency templates

Issue: 1-1 DN03317837 27

3 Adjacency templates

Adjacency parameters can be defined with adjacency templates, and the templates can be automati-cally 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 Manag-

er (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 ad-

jacencies.

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.

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/configuration_management_overview_and_operations/configuration_management_overview_and_operations.html



Managing Adjacencies Managing adjacencies using plans

Issue: 1-1 DN03317837 28

4 Managing adjacencies using plans

This chapter describes how to prepare the adjacency modification plans and activate them to the net-work.

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, HOdrop call ratio, HO failure ratio and interference, you can analyze whether the performance of the net-

work 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 29

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 31

It is recommended that external cells for adjacencies are included in the border-area ad-

jacency plan. This way you can ensure that the external cells have a full set of parame-

ters 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 ex-

plained 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 exter-

nal GSM cell / external UTRAN cell objects are created to the NetAct Configurator database. If

the external GSM cell / external UTRAN cell is the f irst 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 Configu-

rator database before adjacencies can be created. Templates can be used for defining adjacency pa-

rameters for new adjacencies. For more information on templates and foreign cells, see section Adja-

cency templates and Inter-regional adjacencies.

To create adjacencies in CM Editor, select the adjacency source and target cell and create either bi-di-

rectional 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.

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/cm_editor_help/Common/concepts/about_cm_editor.html




Issue: 1-1 DN03317837 32

In CM Editor, adjacency parameters from target cells are read-only and can only be updated by updat-

ing 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 im-

port, define the missing parameters and templates for the objects. For this you need to have the in-

formation 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 adjacen-

cies 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 para-

meter. The target cell dependent parameters are updated to the adjacency in plan prepara-

tion 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.

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/cm_analyzer_help/Common/concepts/AboutCMAnalyser.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/rules_and_rule_syntax_for_netact_configurator/concepts/consistency_checking_rules-d14e437.html






Issue: 1-1 DN03317837 33

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 Man-

ager.

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 Optimiz-

er you can use the Instant adjacency provisioning functionality in order to provision adjacen-

cy changes to the network.

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/managing_the_network_with_netact_configurator/Common/concepts/start.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/administration_of_measurements_help/concept/about_aom.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/cm_operations_manager_help/Common/concepts/about_cm_operations_manager.html




Issue: 1-1 DN03317837 34

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.


http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/cm_operations_manager_help/Common/concepts/about_cm_operations_manager.html



Managing Adjacencies Managing adjacencies using Send to Network

Issue: 1-1 DN03317837 35

5 Managing adjacencies using Send to Network

This chapter describes how to manage GSM, GSM-R, WCDMA, and Flexi Direct adjacencies one byone, 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-re-

gional 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 incom ing LTE

adjacencies (LNRELG, LNADJG, LNRELW, LNADJW and ADJE), CM Editor adds the required adja-

cency 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.





Managing Adjacencies Managing adjacencies using local management tools

Issue: 1-1 DN03317837 36

6 Managing adjacencies using local management tools

You can manage GSM, GSM-R, WCDMA, Flexi Direct, and LTE adjacencies using local managementtools (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 ad-

ditional 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 respec-

tive 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, includ-ing 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 GSM-

R. 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 parame-

ters 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 hav-

ing X2 link status unavailable and cell is modified, you need to run consistency checks in Configura-





Managing Adjacencies Managing inter-regional adjacencies

Issue: 1-1 DN03317837 38

7 Managing inter-regional adjacencies

External GSM cell (EXGCE), External WCDMA/Flexi Direct cell (EXUCE), and External ENodeB Func-tion (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 rep-

resent 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 man-

aged 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 re-

al 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 correspond-

ing external objects in your region. When creating a border-area adjacency plan, check that the exter-

nal cell definitions in both regions are up-to-date, and implement the changes in both regions to en-

sure 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 Configu-

rator 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 ad-

jacency object. The final set of parameters required for an external cell depends on the type of the in-coming adjacencies.




Issue: 1-1 DN03317837 39

Plan modification

You can create, delete, and modify EXGCE / EXUCE / EXENBF and EXEUCE, and unidirectional ad-

jacencies pointing to them in CM Editor. The target cell dependant parameters in an adjacency are al-ways 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 provision-

ing.

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 exis-

tence 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 0–35999, then the the division parameter under EXENBF is setto FDD;




Issue: 1-1 DN03317837 40

– if fDlEarfcn has value 36000–65535, 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 / EX-ENBF 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.



Managing Adjacencies Verifying and maintaining adjacencies

Issue: 1-1 DN03317837 41

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 fig-

ure 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 ac-

tual 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 42

For a list of available rule sets, see Rules and Rule Syntax for NetAct Configurator . You can also cre-

ate 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 run-

ning 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 sys-tem 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).

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/dn7056527/concepts/about_alarm_filter_editor.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/dn70429608/concepts/about_rule_editor.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/dn70429608/concepts/about_rule_editor.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/dn7056527/concepts/about_alarm_filter_editor.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/administration_of_measurements_help/concept/about_aom.html

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/rules_and_rule_syntax_for_netact_configurator/concepts/consistency_checking_rules-d14e437.html




Issue: 1-1 DN03317837 43

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 net-

work.

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 implementa-

tion 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.

http://localhost/var/www/apps/conversion/tmp/scratch_6/PLUGINS_ROOT/DN09140649/about_this_document-d36e12.html





Managing Adjacencies Adjacency parameters fetched from the target cell

Issue: 1-1 DN03317837 44

9 Adjacency parameters fetched from the target cell

Adjacency parameters fetched from the target cell are listed in the table below. The adjacency para-meters are updated/filled during the Plan Prepare operation.

Only adjacency parameters are read-only in CM Editor.

Object class

- adjacency

type

Adjacency parameter Target cell parameter Object class

CI CI

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

ADCE (NOK-

BSC)

ADCE (NOK-

BSCR)

Frequency Band in Use Frequency Band In Use

BTS (NOKBSC)

BTS (NOKBSCR)




Issue: 1-1 DN03317837 45

Object class

- adjacency

type


ADCE (NOK-

BSC)

ADCE (NOK-

BSCR)

BCCH Frequency Frequency TRX (NOKBSC)

TRX (NOKBSCR)

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

ADCE (NOK-

BSC)

ADCE (NOK-

BSCR)

Frequency Band in Use SYS id

EXGCE (com.nsn.

vimext)




Issue: 1-1 DN03317837 46

Object class

- adjacency

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


GSM1800

• When Sys id equal to PCS

1900, then Frequency


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.

RNC ID RNC Identifier

MCC Common MCC

ADJW (NOK-

BSC)

MNC Common MNC

RNC (NOKRNC)

RNC (com.nsn.

mcrnc)

IADA (NOKIHIA-

DA)




Issue: 1-1 DN03317837 47

Object class

- adjacency

type


Cell identification Cell identifier

LAC Location area code

Service Area Code Service Area Code

Name Name

Scrambling Code Primary downlink scrambling code

ADJW (NOK-

BSC)

WCDMA Downlink Carrier Frequen-

cy

UTRA Absolute Radio Frequency

Channel Number

WCEL (NOKRNC)

WCEL (com.nsn.

mcrnc)

WCEL (NOKIHIA-

DA)

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

ADJW (NOK-

BSC)

WCDMA Downlink Carrier Frequen-

cy

UARFCN downlink

EXUCE (com.nsn.

vimext)

RNC Identifier RNC Identifier

Mobile Country Code Common MCC

ADJS

(NOKRNC)

ADJS (com.

nsn.mcrnc)

ADJS

(NOKIHIADA)

Mobile Network Code Common MNC

RNC (NOKRNC)

RNC (com.nsn.

mcrnc)

IADA (NOKIHIA-

DA)

ADJS

(NOKRNC)

Cell Identifier Cell identifier WCEL (NOKRNC)




Issue: 1-1 DN03317837 48

Object class

- adjacency

type


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

CPICH channel

ADJS (com.

nsn.mcrnc)

ADJS

(NOKIHIADA)

Maximum UE TX Power on RACH Maximum UE transmission power

on PRACH

WCEL (com.nsn.

mcrnc)

WCEL (NOKIHIA-

DA)

RNC Identifier RNC id

Mobile Country Code MCC

Mobile Network Code MNC

Cell Identifier 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

ADJS

(NOKRNC)

ADJS (com.

nsn.mcrnc)

ADJS(NOKIHIADA)


on RACH

EXUCE (com.nsn.

vimext)



ADJI

(NOKRNC)

ADJI (com.

nsn.mcrnc)

ADJI

(NOKIHIADA)


RNC (NOKRNC)

RNC (com.nsn.

mcrnc)

IADA (NOKIHIA-

DA)




Issue: 1-1 DN03317837 49

Object class

- adjacency

type



Name Name



Primary Scrambling Code Primary downlink scrambling code


Channel Number


Channel Number


CPICH channel

Maximum UE TX Power on DPCH Maximum UE transmission power

on DPCH

ADJI

(NOKRNC)

ADJI (com.

nsn.mcrnc)

ADJI

(NOKIHIADA)

Maximum UE TX Power on RACH Maximum UE transmission power on RACH

WCEL (NOKRNC)

WCEL (com.nsn.

mcrnc)

WCEL (NOKIHIA-

DA)





Name Name





Channel Number

UARFCN downlink

ADJI

(NOKRNC)

ADJI (com.

nsn.mcrnc)

ADJI

(NOKIHIADA)


EXUCE (com.nsn.

vimext)




Issue: 1-1 DN03317837 50

Object class

- adjacency

type


Maximum UE TX Power on DPCH Maximum UE transmission power

on DPCH


on RACH



ADJD

(NOKRNC)

ADJD (com.

nsn.mcrnc)

ADJD

(NOKIHIADA)


RNC (NOKRNC)

RNC (com.nsn.

mcrnc)

IADA (NOKIHIA-

DA)


Name Name



Primary Scrambling Code Primary Downlink Scrambling

Code

ADJD

(NOKRNC)

ADJD (com.

nsn.mcrnc)

ADJD

(NOKIHIADA)


CPICH channel

WCEL (NOKRNC)

WCEL (com.nsn.

mcrnc)

WCEL (NOKIHIA-

DA)


Name Name





ADJD

(NOKRNC)

ADJD (com.

nsn.mcrnc)

ADJD

(NOKIHIADA)


EXUCE (com.nsn.

vimext)




Issue: 1-1 DN03317837 51

Object class

- adjacency

type




Cell Identifier CI




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:

MS Tx Pwr Max CCH when MS

Tx Pwr Max CCH > GPRS MS Tx-

pwr 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

ADJG

(NOKRNC)

ADJG (com.

nsn.mcrnc)

ADJG(NOKIHIADA)

Maximum UE TX Power on TCH GSM 800/900: msTxPwrMaxGSM

(GSM 800/900)

BTS (NOKBSC)




Issue: 1-1 DN03317837 52

Object class

- adjacency

type


GSM 1800/1900:

msTxPwrMaxGSM1x00

BCCH ARFCN Frequency TRX - BCCH

(NOKBSC)

Base Station Colour Code BCC

BCCH ARFCN BCCH frequency

ADJG

(NOKRNC)

ADJG (com.

nsn.mcrnc)

ADJG

(NOKIHIADA)

Band Indicator SYS id

Band Indicator is set based

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


850 and 1800.


DCS1800, then Band


850 and 1800.


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



settings.

EXGCE (com.nsn.

vimext)




Issue: 1-1 DN03317837 53

Object class

- adjacency

type


Cell Identifier Cell identity




Network Colour Code NCC

Maximum UE TX Power on RACH GSM 800/900:

MS tx pwr max CCH when MS tx-

pwr 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

Inter-RAT LTE adjacent physical cell

identifier

Physical layer cell identity ADJE

(NOKRNC)

Cell ID Local cell resource ID

LNCEL (NOKLTE)




Issue: 1-1 DN03317837 54

Object class

- adjacency

type


Tracking Area Code Tracking Area Code

Name Name

Mobile Country Code Mobile Country Code

Mobile Network Code Mobile Network Code

ADJE

(NOKRNC)

Macro eNB ID Macro eNB identifier (LNBTS in-

stance)

LNBTS (NOKLTE)

Inter-RAT LTE adjacent physical cell

identifier

Physical cell identity

Cell ID Local cell resource ID

Tracking Area Code Tracking Area Code

ADJE

(NOKRNC)

Name Name

EXEUCE (com.

nsn.vimext)



ADJE

(NOKRNC)

Macro eNB ID Macro eNB ID

EXENBF (com.

nsn.vimext)

LNADJ

(NOKLTE)

C-Plane IP address of neighbor

eNB (X2 only)

Control plane IP address IPNO (NOKLTE)

Identity of neighbor eNB within

PLMN (S1 only)

Macro eNB identifier

Primary PLMN identity of neighbor

eNB - MCC in primary PLMN identi-

ty of neighbor eNB (S1 only)

MCC in PLMN


eNB - MNC in primary PLMN identi-

ty of neighbor eNB (S1 only)

MNC in PLMN

LNADJ

(NOKLTE)

Name Name

LNBTS (NOKLTE)




Issue: 1-1 DN03317837 55

Object class

- adjacency

type


C-Plane IP address of neighbor

eNB (X2 only)

C-plane IP address

Identity of neighbor eNB within

PLMN (S1 only)

Macro eNB identifier


eNB - MCC In Primary PLMN Identi-

ty Of Neighbour ENB (S1 only)

MCC


eNB - MNC In Primary PLMN Identi-

ty Of Neighbour ENB (S1 only)

MNC

LNADJ

(NOKLTE)

Name Name

EXENBF (com.

nsn.vimext)

Local cell resource ID of related

neighbor cell

Local cell resource ID

MCC in broadcast PLMN identity

(Broadcast PLMN identity list )

Mobile country code

MNC in broadcast PLMN identity


Mobile network code

Downlink EARFCN of LTE cell

served by neighbor eNB

EARFCN downlink

Physical cell ID of cell served by

neighbor eNB

Physical layer cell identity

LNADJL

(NOKLTE)

- S1-based

link only; for

X2-based link

LNADJL is

created and

configured by

eNB

Tracking area code of cell served by

neighbor eNB

Tracking area code

LNCEL (NOKLTE)

Identity of neighbor eNB in ECGI Macro eNB identifier LNADJL

(NOKLTE)

- S1-based

link only; for

X2-based link

LNADJL is

created and


LTE cell in ECGI - MCC in primary

PLMN identity of neighbour ENB in

ECGI

MCC in PLMN

LNBTS (NOKLTE)




Issue: 1-1 DN03317837 56

Object class

- adjacency

type


configured by

eNBPrimary PLMN identity of neighbor

LTE cell in ECGI - MNC in primary


ECGI

MNC in PLMN

Local cell resource ID of related

neighbor cell

Local cell resource identifier

MCC in broadcast PLMN identity


MCC

MNC in broadcast PLMN identity


MNC

Downlink EARFCN of LTE cell

served by neighbor eNB

EARFCN downlink

Physical cell ID of cell served by

neighbor eNB

Physical cell identity

LNADJL

(NOKLTE)

- S1-based

link only; for

X2-based link

LNADJL is

created and

configured by

eNB

Tracking area code of cell served by

neighbor eNB

Tracking area code

EXEUCE (com.

nsn.vimext)

Identity of neighbor eNB in ECGI Macro eNB identifier


LTE cell in ECGI - MCC in primary


ECGI

MCC

LNADJL

(NOKLTE)

- S1-based

link only; for

X2-based link

LNADJL is

created and

configured by

eNB


LTE cell in ECGI - MNC in primary


ECGI

MNC

EXENBF (com.

nsn.vimext)

LNADJW

(NOKLTE)

Target RNC id RNC Identifier RNC (NOKRNC)

RNC (com.nsn.

mcrnc)

IADA (NOKIHIA-

DA)




Issue: 1-1 DN03317837 57

Object class

- adjacency

type


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

Channel Number

Target location area code Location area code

Target routing area code Routing Area Code

Primary scrambling code (FDD) Primary downlink scrambling code

LNADJW

(NOKLTE)

Name Name

WCEL (NOKRNC)

WCEL (com.nsn.

mcrnc)

WCEL (NOKIHIA-

DA)

Target RNC id RNC id

Target primary PLMN identity - MCC MCC

Target primary PLMN identity - MNC MNC

Target cell id Cell identifier

Target frequency UARFCN downlink

Target location area code LAC

Primary scrambling code (FDD) Primary scrambling code

LNADJW

(NOKLTE)

Name Name

EXUCE (com.nsn.

vimext)

LNRELW

(NOKLTE)

Target RNC Id RNC Identifier RNC (NOKRNC)

RNC (com.nsn.

mcrnc)

IADA (NOKIHIA-

DA)

LNRELW

(NOKLTE)

Target cell Id in UTRAN CGI of re-

lated neighbor cell

Cell identifier WCEL (NOKRNC)




Issue: 1-1 DN03317837 58

Object class

- adjacency

type


Primary PLMN identity in CGI of

UTRAN neighbor cell - MCC

Mobile Country Code


UTRAN neighbor cell - MNC

Mobile Network Code

Target frequency UTRA Absolute Radio Frequency

Channel Number

Target location area code Location area code

Target routing area code Routing Area Code

Primary scrambling code (FDD) Primary downlink scrambling code

Name Name

WCEL (com.nsn.

mcrnc)

WCEL (NOKIHIA-

DA)

Target RNC Id RNC id

Target cell Id in UTRAN CGI of re-lated neighbor cell

Cell identifier


UTRAN neighbor cell - MCC

MCC


UTRAN neighbor cell - MNC

MNC

Target frequency UARFCN downlink

Target location area code LAC

Target routing area code RAC

Primary scrambling code (FDD) Primary scrambling code

LNRELW

(NOKLTE)

Name Name

EXUCE (com.nsn.

vimext)

LNADJG

(NOKLTE)

ARFCN value geran Frequency TRX (NOKBSC)




Issue: 1-1 DN03317837 59

Object class

- adjacency

type


Band indicator geran Band indicator geran is set based

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


indicator geran is set to

dcs1800.





dcs1800.





pcs1900.

Basestation colour code BSIC BCC

DTM capability DTM Enabled

CI GERAN CI

LAC GERAN LAC

RAC GERAN RAC

MCC GERAN MCC

MNC GERAN MNC

LNADJG

(NOKLTE)

Network colour code BSIC NCC

BTS (NOKBSC)




Issue: 1-1 DN03317837 60

Object class

- adjacency

type


Name Name

ARFCN value geran BCCH frequency

Band indicator geran SYS id

Band indicator geran is set

based on the EXGCE Sys id

value in the following way:

• When Sys id is equalto GSM850, then Band


dcs1800.

• When Sys id is equal

to EXT900, then Band


dcs1800.


to DCS1800, then Band


dcs1800.


to PCS1900, then Band


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



settings.

Basestation colour code BCC

LNADJG

(NOKLTE)

DTM capability DTM capability

EXGCE (com.nsn.

vimext)






Issue: 1-1 DN03317837 62

Object class

- adjacency

type


PLMN Identity in CGI of GERAN

neighbor cell - MCC

MCC

PLMN Identity in CGI of GERAN

neighbor cell - MNC

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



Managing Adjacencies Importing user templates required for the LTE Inter-RAT

UTRAN / GERAN automatic management features

Issue: 1-1 DN03317837 63

10 Importing user templates required for the LTEInter-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 man-

aged 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 us-

ing 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 64

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 ac-

cording to your requirements. This is needed because provided ready-made user templates containonly 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 tem-

plate 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 65

• 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 intemplate; 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 templatesLNHOG 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)


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:





• 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)


Documents

NetAct 8 EP1 Managing_adjacencies (2)