ANR Function

DESCRIPTION

12/1551-LZA 701 6004 Uen C

Copyright

© Ericsson AB 2009–2010. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

12/1551-LZA 701 6004 Uen C | 2010-06-21

 Contents

Contents

1 Introduction 1

2 Functions and Concepts 3

2.1 External Cell 3
2.2 Cell Relation 3
2.3 Frequency Relation 3
2.4 Protocols 3

3 Managed Object Model 5

3.1 Managed Object Overview 5

4 Configuration Management 7
4.1 Configuration Overview 7
4.2 Defining Blacklist and Whitelist 7
4.3 Creating ANR MOs 8
4.4 Removing ANR MOs 9
4.5 Storing ANR Created Configuration 10

5 Fault Management 11

6 Performance Management 13

12/1551-LZA 701 6004 Uen C | 2010-06-21

ANR Function

12/1551-LZA 701 6004 Uen C | 2010-06-21

 Introduction

1 Introduction

This document describes the management model and concepts for the
managed area Automated Neighbor Relations (ANR).

The document provides an understanding of how the area is modeled, including

the functions related to the area and how they are managed.

A managed area represents a group of functions and Managed Objects (MO)

within the node, where each area is relatively independent of other areas.

ANR enables the RBS to set neighbor cells dynamically and make handover to
those cells.

ANR is a licensed feature that enables the RBS to automatically detect and:

• Add external RBSs

• Add external cells

• Add frequency relations

• Add cell neighbor relations used for handover

• Automatically set up X2, if allowed

12/1551-LZA 701 6004 Uen C | 2010-06-21 1

ANR Function

2 12/1551-LZA 701 6004 Uen C | 2010-06-21

 Functions and Concepts

2 Functions and Concepts

This section describes the functions and concepts that apply to operation and
maintenance of the ANR managed area.

2.1 External Cell

External cells are:

• Defined by an operator through OSS-RC

• Detected by UE measurements

0 In best cell evaluation (handover measurements)

0 Initiated by ANR

• Sent over X2 from a neighbor RBS

2.2 Cell Relation

Relations are made between cells and used for handover, either S1 or X2.
Handover over X2 requires an X2 connection that is set up manually by the
operator or automatically by ANR.

2.3 Frequency Relation

The frequency relation points to frequencies on which the cell can have
neighbor cells.

2.4 Protocols
The following protocols apply to this managed area:

• S1, used for communication between RBS and MME

• X2, used for communication between RBSs

12/1551-LZA 701 6004 Uen C | 2010-06-21 3

ANR Function

4 12/1551-LZA 701 6004 Uen C | 2010-06-21

 Managed Object Model

3 Managed Object Model

This section describes the management model defined for this area.

For information about the managed object model concept, refer to Managed
Object Model (MOM) User Guide.

Note: Setting an unsupported value may affect traffic. A few MOs,

parameters, counters, and value ranges may be visible in the MOM
even though they are not yet supported. This is because system design
considers future aspects. Refer to Parameter and Counter Limitations
for a list of limitations to the MOM included in this library.

3.1 Managed Object Overview

The ANR function represents a subset of the MOM.

Other parameters for ANR are available on other MOs that do not belong to
the managed area ANR Function. For information on these parameters, see
Automated Neighbor Relations.

For information about all MO classes, refer to Managed Object Model RBS.

The following figure shows the MOs for the ANR Function managed area:

MOClass
ENodeBFunction

MOClass
AnrFunction

L0000227A

Figure 1 MO ANR Function

12/1551-LZA 701 6004 Uen C | 2010-06-21 5

ANR Function

6 12/1551-LZA 701 6004 Uen C | 2010-06-21

 Configuration Management

4 Configuration Management

This section describes the configuration management defined for this managed
area.

4.1 Configuration Overview

The ANR function can create and delete instances of the following MOs:

• ExternalENodeBFunction

• ExternalEUtranCellFDD

• EUtranCellRelation

• TermPointToENB

The ANR function also creates instances of EUtranFreqRelation to its own

cell’s frequencies in the cases where the relations are missing, but the MO is
not removed by ANR

The maximum number of intra-LTE cell relations per internal cell is 64. There
are no cell relation priorities.

ANR access to the different MOs is controlled by the following parameters:

• EUtranCellRelation.isRemoveAllowed

• ExternalEUtranCellFDD.isRemoveAllowed

• ExternalENodeBFunction.ctrlMode

• ExternalEUtranCellFDD.ctrlMode

• EUtranCellRelation.ctrlMode

• TermPointToENB.ctrlModectrlMode

ANR cannot remove MOs where isRemoveAllowed is set to false by the

operator, or where the parameter ctrlMode is equal to manual.

4.2 Defining Blacklist and Whitelist

According to 3GPP standards the control of the ANR function is partly specified
by blacklists and whitelists. Table 1 shows lists in an RBS controlling to which
other RBSs ANR can set up and remove X2 connections. The lists are defined
by the operator.

12/1551-LZA 701 6004 Uen C | 2010-06-21 7

ANR Function

Table 1 Lists to Control X2 Connections

List Function for ANR
x2BlackList ANR cannot set up X2 connections to RBSs in this list.
x2WhiteList ANR cannot remove X2 connections to RBSs in this list.

When an ANR-triggered X2 setup is unsuccessful, the first retry is performed

after max (X2RetryTimer, TimeToWait) seconds.

TimeToWait=0 if not received from neighbor RBSs. X2RetryTimer is

doubled for every new retry, until maximum x2retryTimerMaxAuto.

When an X2 connection setup by ANR breaks a first retry is made after

random (0-x2retryTimerStart) seconds. Following retries are made after X
seconds, where X starts at x2retryTimerStart, doubles every retry until
max x2retryTimerMaxAuto.

4.3 Creating ANR MOs

Cells may be added due to UEs reporting new neighbor cells, or new external
cell configurations being reported over X2. When a UE reports a new neighbor
cell with a Physical Cell Identity (PCI) not tied to any present neighbor relation:

• If the PCI does not correspond to any known cells, the neighbor cell is
unknown in the RBS (is not listed in the RBS existing cell neighbor list)

• The UE is asked to report the Cell Global Identity (CGI) of the neighbor cell

• If the CGI report is received and the new neighbor cell belongs to an
unknown RBS (The RBS is not listed in existing neighbor list), an external
RBS is created

• A new external cell is created

• A new neighbor relation is created

• If the new neighbor cell belongs to an external RBS and there is no X2 to

the external RBS and the external RBS is not in the X2 Blacklist, X2 is set
up to the external RBS. When a new cell configuration is reported from an
external RBS over X2, the new reported cell is created as an external cell.
To set up the X2, the X2Policy is checked.

Table 2 shows the values for event based ANR measurements. Handover
triggered measurements uses the values of the handover evaluation function.

8 12/1551-LZA 701 6004 Uen C | 2010-06-21

 Configuration Management

Table 2 Threshold Value for Automatically Adding Cells

Parameter Name Description
cellAddRankLimitEutran Threshold value for reported rank for
a cell to be automatically added as
neighbor
MO: AnrFunction
cellAddRsrpOffsetEutran Threshold offset value for reported
power for a cell to be automatically
added as neighbor
MO: AnrFunction
cellAddRsrpThresholdEutran Threshold value for reported power
for a cell to be automatically added
as neighbor
MO: AnrFunction
cellAddRsrqOffsetEutran Threshold offset value for reported
quality for a cell to be automatically
added as neighbor
MO: AnrFunction
cellAddRsrqThresholdEutran Threshold value for reported quality
for a cell to be automatically added
as neighbor
MO: AnrFunction

4.4 Removing ANR MOs

A neighbor relation is removed by the following events:

• Ordered by O&M

• A certain time (removeNrelTime) has elapsed with no communication

to the neighbor cell

• Neighboring cell is removed

A neighbor cell is removed by the following events:

• Ordered by O&M

• A certain time (removeNcellTime) has elapsed with no neighbor relation

to the neighbor cell

A neighbor RBS is removed by the following causes:

• Removal ordered by O&M

12/1551-LZA 701 6004 Uen C | 2010-06-21 9

ANR Function

• A certain time (removeNenbTime) has elapsed with no neighbor cells

in the neighbor RBS

To delete a relation automatically, the ANR feature must be activated. The

parameter isRemovedAllowed must be equal to true and the parameter
ctrlMode must be set to auto. The parameter setting of the MOM parameter
removeNrelTime which can be defined by the operator is specified as follows:

Table 3 Parameters Specifying the Length of the Relation without any Communication
Parameters Name Description
removeNrelTime This parameter specifies how long neighbor relations without any
communication to the neighbor cell must remain in the RBS. 1000
means no automatic removal is performed. If set to 0, the MO is
removed within 5 minutes.
removeNcellTime This parameter specifies how long neighbor cells without any neighbor
relations must remain in the RBS. 1000 means no automatic removal
is performed. If set to 0, the MO is removed within 1 minute.
removeNenbTime This parameter specifies how long neighbor RBSs without any
neighbor cells must remain in the RBS. 1000 means no automatic
removal is performed. If set to 0, the MO is removed within 5 minutes

4.5 Storing ANR Created Configuration

To persistently store the configuration created by ANR a CV needs to be created
manually. See Software Management for information about how to create a CV.

10 12/1551-LZA 701 6004 Uen C | 2010-06-21

 Fault Management

5 Fault Management

See the specification in Alarm and Event List.

12/1551-LZA 701 6004 Uen C | 2010-06-21 11

ANR Function

12 12/1551-LZA 701 6004 Uen C | 2010-06-21

 Performance Management

6 Performance Management

See the specifications of the PM counters in Managed Object Model RBS.

Note: Setting an unsupported value may affect traffic. A few MOs,

parameters, counters, and value ranges may be visible in the MOM
even though they are not yet supported. This is because system design
considers future aspects. Refer to Parameter and Counter Limitations
for a list of limitations to the MOM included in this library.

12/1551-LZA 701 6004 Uen C | 2010-06-21 13