ANR Mobility

User Guide

183/1553-HSD 101 02/1 Uen N

Copyright

© Ericsson AB 2017. 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.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Contents

Contents

1 Introduction 1
1.1 Basic Characteristics 1
1.2 Benefits 1
1.3 Additional Information 2

2 Feature Operational Description 3

2.1 Network Requirements 3
2.2 Feature Operation Sequence Diagram 3
2.3 Process Steps 4

3 Parameters 11
3.1 Introduced Parameters 11
3.2 Affected Parameters 12

4 Network Impact 13
4.1 Subscriber Capacity 13
4.2 Network Performance 13
4.3 Hardware 14
4.4 Inter-Node Interface 14
4.5 Other Network Elements 14

5 Associated Features and Affected Functions 15

5.1 Prerequisite Features 15
5.2 Affected Features 15
5.3 Related Features 15
5.4 Affected System Functions 16

6 Performance 17
6.1 KPIs 17
6.2 Counters 17
6.3 Events 19

7 Operation and Maintenance 21

7.1 Activate the Feature 21
7.2 Deactivate the Feature 21
7.3 Engineering Guidelines 22

183/1553-HSD 101 02/1 Uen N | 2018-11-05

ANR Mobility

183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Introduction

1 Introduction

This document describes the optional feature Automatic Neighbor Relations

(ANR) Mobility and its main benefits and impacts in the WCDMA RAN.

1.1 Basic Characteristics

This section describes the basic characteristics of the feature.

Feature identity:
FAJ 121 2551: ANR Mobility

Release: Introduced in W14.1, enhanced in W15.1, W16A, W16B

and W18.Q4.

Dependencies

— This feature has no prerequisite features.

— This feature affects the following OSS features:

— Neighbor Cell Support

— Radio Network Optimization

— Automatic Scrambling Code Selection and Conflict Resolution

1.2 Benefits
ANR Mobility is a Self-Organizing Network (SON) feature for the RNC.
The feature automatically detects missing neighbor definitions, identifies the
neighboring cells and optionally creates UtranRelation MOs. It improves the
Active Set (AS), which contributes to improved retainability, visible as lower
dropped calls ratio and improved mobility visible as increased number of IAF
handovers and reduced number of IRAT handovers.

The ANR Mobility feature is license controlled and activated on the RNC and cell
level. It is not based on the ANR specification in 3GPP and does not require any
optional UE capabilities.

The feature increases the probability of maintaining UE connection, when a

neighbor relation is missing.

With ANR Mobility, the neighbors, both manually-created and ANR-discovered,

are periodically sorted. Internally, RNC can store up to 128 intra-frequency
neighbors per cell.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 1

 ANR Mobility

Neighbors most probable to be reported by UE are used to:

— build Neighbor Cell Lists (NCL) in the SRNC

— build RNSAP IE Neighboring UMTS Cell Information, sent from DRNC

— build System Information Block 11 (SIB11)

1.3 Additional Information

References to other documents containing information related to the feature.
— System Description

— Handover

— General Performance Event Handling

— Idle Mode and Common Channel Behavior

2 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Feature Operational Description

2 Feature Operational Description

This section describes the ANR Mobility feature in more detail, including network
configuration requirements and operation flows.

2.1 Network Requirements

The following must be fulfilled at feature activation:

— The license for ANR Mobility feature, CXC 403 0136 is enabled.

2.2 Feature Operation Sequence Diagram

Figure 1 gives a high-level overview of signaling in which ANR Mobility is
involved.

Radio
UE SRNC
Nodes

RRC: Measurement Report

(ANR Mobility triggers on Events 1a or 1c)

ANR initiated HO,

NBAP: RADIO LINK SETUP
or ADDITION procedures
ANR Mobility
ANR initiated HO, RRC:
feature
ACTIVE SET UPDATE procedure

NBAP: RADIO LINK

RESTORE INDICATION

U0001028B

Figure 1 ANR Mobility Diagram

ANR Mobility identifies the missing intra-frequency neighbor relations from a

source cell in the SRNC, represented by the UtranCell MO, towards:

— another cell in the SRNC, represented by UtranCell.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 3

 ANR Mobility

— a DRNC cell, represented by ExternalUtranCell in the SRNC.

— a different cluster member cell in the RNC in Pool configuration, represented

by RemoteUtranCell in the SRNC.

In an RNC in Pool configuration, if Iub Redundancy is configured between two

cluster member RNCs, the ANR Mobility feature can create UtranCell relations
to cells with the Iub Redundancy configuration. For more information on Iub
Redundancy refer to RNC in Pool.

If activated, ANR Mobility creates UtranRelation MOs representing ANR-

discovered neighbor relations. Internally, the feature can store 128 intra-
frequency neighbors, compared to a maximum of 31 IAF UtranRelation MOs per
cell.ANR Mobility activated in the SRNC does not create neighbor relations from a
DRNC cell to any other cells.

2.3 Process Steps

This section describes the process steps initiated by the main trigger for ANR
Mobility, that is, a reception of an Undefined cell DS measurement report. See
Table 1 for the different types of measurement reports that the UE sends in this
context.

Table 1 UE Measurement Report Types

UE Measurement Report Types Report Receiver in SRNC
Monitored Set measurement report, Handover Evaluation (legacy
which contains one or more RNC functionality)
defined Primary Scrambling Codes,
representing neighbor cell relations.
Unmonitored Set DS report where at Handover Evaluation (legacy
least one cell is Defined. Issued if a DS functionality)
report contains one or more target
cells Primary Scrambling Codes where
at least one matches the Primary
Scrambling Code of minimum one of
the neighbors of the AS cells.
Unmonitored Set DS report where all ANR Mobility (when activated,
cells are Undefined. Issued when a DS otherwise the DS report is discarded)
report contains one or more target
cells Primary Scrambling Codes which
does not match the Primary
Scrambling Code of any of the
neighbors to the AS cells.

Figure 2 gives an overview of the process steps and involved operator

parameters in the SRNC.

4 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Feature Operational Description

Check ANR Mobility License (CXC 403 0136), RNC

RRC: Measurement Report, Event 1a or 1c feature activation (anrEnabled) and cell activation
(anrIafUtranCellConfig). If OK, the Undefined Cell DS
report is handled by ANR, otherwise it is discarded.

Undefined Cell DS report

Check CPICH Filter (anrDsReportFilterEnabled) with its

thresholds for Ec/No (anrDsReportFilterEcno) and
RSCP (anrDsReportFilterRscp). Use or discard the DS.

Undefined Cell DS report

Based on ANR internal statistics for the reported

Primary Scrambling Code, do the cell selection among
the target cell candidates.
When creating a CRS table, no entries for the blacklisted
cells are included in the CRS table.

ANR HO Proposal

Perform HO Evaluation and Admission control.

If OK, an ANR-initiated Soft or Softer HO is done with
ANR HO Attempt.

ANR HO Attempt

In case of Soft HO, detect Uplink sync in the added

cell, that is the reception of NBAP/RNSAP Radio Link
Restore Indication. If Uplink sync is achieved within 2 s,
the handover attempt is judged successful. If Uplink sync
Discard
is not achieved within 2 s, the cell is removed from the
AS again.
In case of Softer HO, UE is already synchronized with
RBS, thus ANR has to assume successful HO.

ANR HO Result

A successful/unsuccessful ANR initiated HO results in

finding a good target cell candidate in the ANR internal
statistics.

U0001025C

Figure 2 ANR Mobility Handling of Undefined Cell DS Report

2.3.1 Reception of Undefined Cell DS Report

The reception of an Undefined cell DS measurement report is the real-time
trigger for ANR Mobility. The trigger activates ANR Mobility if the license is
enabled and the feature is activated in the RNC and in the best AS cell.
Otherwise, the DS report is discarded in the same way as when ANR Mobility is
deactivated or not supported.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 5

 ANR Mobility

2.3.2 ANR CPICH Filter

The CPICH filter can be used by the operator to control ANR Mobility sensitivity
to CPICH measured values that are reported in Undefined cell DS reports. The
filter is enabled with the anrDsReportFilterEnabled parameter and uses two
parameters:

— Ec/No threshold (anrDsReportFilterEcNo)

— Received Signal Code Power (RSCP) threshold (anrDsReportFilterRscp)

When the filter is enabled, Undefined cell DS reports are compared with the
thresholds. If the corresponding thresholds are fulfilled, or if the filter is disabled,
the DS report is used by ANR Mobility. Otherwise, it is discarded.

2.3.3 Cell Selection and ANR Handover Proposal

A received Undefined cell DS report triggers cell selection among the candidates
in the ANR Mobility internal statistics having the same Primary Scrambling Code
and frequency. An ANR-initiated handover is proposed to the selected cell.

2.3.4 New ANR Handover Attempt

If the selected cell passes admission check, an ANR handover is attempted and
the internal statistics is updated.

2.3.5 ANR Handover Success Result

In case of soft handover, a successful ANR-initiated handover is based on
detecting Uplink Synchronization in the candidate target cell. That is, the NBAP
message "RADIO LINK RESTORE INDICATION" is received. This information is
used in ANR Mobility internal statistics in the source cell. If Uplink
Synchronization is achieved within 2 seconds, the handover attempt is judged
successful (correct candidate selected) and ANR Mobility updates the internal
statistics accordingly. If Uplink Synchronization is not achieved within 2 seconds,
the cell is removed from the active set again.

In case of softer handover, all ANR handover attempts are assumed to be

successful, as the UE is already synchronized with the radio node of a cell from
the AS.

2.3.6 Bad CRS

A successful or unsuccessful ANR-initiated handover results in the update of

internally stored Cell Relation Statistics (CRS) tables.
A CRS table containing one or more candidates with low attempt ratio is
classified by ANR as "bad CRS". For such CRS, no relation is configured in the MO

6 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Feature Operational Description

database. The threshold for the detection of "bad CRS" is defined by the
AnrIafUtran::anrAttRatioBadCrs parameter. The attempt ratio in this
document refers to the number of attempts divided by the number of proposals
for a cell to be added to the AS by the ANR Mobility.

2.3.7 Black List Cell

A list of blacklisted cells can be defined for each UtranCell MO.

A blacklisted cell is not added to CRS table as a possible neighbor and no ANR-
based handovers are triggered towards such cell. Blacklisting a cell which is
already present in CRS table or ANCL table results in removal of this cell from the
table.The ANR black list is defined by the anrBlackTargetCells parameter. The
list contains target cells to which no handovers can be performed, including ANR-
based handovers when searching a relation.

If a cell is added to a black list, it is removed from CRS or IAF ANCL.

2.3.8 IAF ANCL

IAF Automatic Neighbor Cell Lists (ANCLs) are internal data structures that are
used to store, evaluate and sort cells which are already identified as neighbors.
Each cell with the ANR Mobility feature enabled has an IAF ANCL. The ANCL
contains both the manually-defined neighbors and the neighbors discovered by
the feature. Maximum of 128 neighbors can be stored in the ANCL. Up to 31
neighbors present in the ANCL can have corresponding IAF UtranRelation MOs.

IAF neighbors found by Neighbors configured

ANR Mobility as UtranRelation MOs

IAF ANCLs
(Sorted IAF neighbor cell lists)

Build IAF Build IAF

DRNC neighbor cells
monitored set SIB 11

Figure 3 IAF ANCL Interaction with Other Functions

During the handover evaluation, the UE receives a list of IAF neighbors to

measure, that is an IAF monitored set. The IAF monitored set is created based on
the IAF ANCLs and the neighbors received from DRNCs.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 7

 ANR Mobility

Note: The ANCLs are stored in the volatile memory. Their content is cleared at
RNC or board restart. After restart, the relations represented by
UtranRelation MOs are imported to ANCLs. Other neighbors must be
rediscovered by the ANR.

CRS tables containing possible neighbors or neighbor candidates are

backed up in persistent storage and are restored after restart.

Neighbors configured as IAF UtranRelation MOs are added to ANCL in any of

the following cases:
— after RNC restart, board restart, RncLmCell restart, or feature activation,

— when an IAF UtranRelation MO is created,

— when frequencyRelationType changes from INTER_FREQ to

INTRA_FREQ as a result of changing frequency of the neighbor cell.

When adding a target cell to an existing IAF ANCL:

— the target cell must not exist in the IAF ANCL,

— the target cells must have unique Primary Scrambling Codes (PSC).

Note: Target cells defined by UtranRelation MOs have precedence

before candidates discovered by CRS.

The average number of neighbors in an IAF ANCL can be calculated by:

pmSumAnrIafRelation
pmSamplesAnrIafRelation

— pmSumAnrIafRelation gives the total number of neighbors in the samples of

an IAF ANCL during a Result Output Period (ROP)

— pmSamplesAnrIafRelation gives the number of samples within the ROP for

pmSumAnrIafRelation.

The neighbors are evaluated and sorted periodically in the ANCL. There are three
evaluation periods: short, medium and long. The neighbors, which are not
reported during longest evaluation period of two weeks are removed from the
ANCL. The IAF ANCL content and MOM is periodically synchronized.
UtranRelation MOs are created for relations that are frequently used, unless they
already exist.

UtranRelation MOs are removed for relations that are rarely used. Creation and
removal of UtranRelation MOs can be controlled independently at RNC and at
UtranCell level:

8 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Feature Operational Description

— UtranCell.anrIafUtrancellConfig.relationAddEnabled and
UtranCell.anrIafUtrancellConfig.relationRemoveEnabled
parameters at UtranCell level,

— AnrIafUtran.anrAddRelationEnabled and
AnrIafUtran.anrRemoveRelationEnabled parameters at RNC level.

If ANR Mobility and the use of IAF ANCL are activated in a DRNC, the neighbors
to be reported in RNSAP messages are taken from IAF ANCLs of the DRNC.

SRNC DRNC

RNSAP Radio Link Setup/Addition Request

Neighbors taken
RNSAP Radio Link Setup/Addition Response from the IAF
ANCL in DRNC

Figure 5 Reporting Neighbors from DRNC

The IAF ANCL list exists only in the internal memory of the RNC and is not kept
after the RNC restart. Only relations that were stored in MOM remain.

2.3.8.1 ANR-discovered Neighbors in SIB11

By default, IAF ANCL is used as input for building SIB11 IAF list . If this option is
deactivated, only the UtranRelation MOs are used to build the list.
If the value of the
UtranCell::anrIafUtranCellConfig.sib11IafAnclEnabled attribute is set
to TRUE, the neighbors, discovered by ANR and stored in the IAF ANCL are
included when building SIB11. ANR-discovered neighbors are used as input by
SIB11 only after a periodical evaluation and sorting of ANCL.

Note: Some neighbors may not be included, if the length limit of SIB11 is
reached.

SIB11 updates are limited to four updates every six hours. Updates, which
exceed the limit are delayed. The limit follows the following rules:

— Updates triggered both by ANR-defined, and MO-defined neighbors count

towards the limit.

— MO-defined neighbor updates are not delayed.

— ANR-defined neighbor updates are delayed, if the limit is exceeded.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 9

 ANR Mobility

— If a SIB11 update is triggered by a change in an MO, while an ANR-triggered

update is pending, the SIB11 update combines both the ANCL and the MO
changes.

The limit prevents the situation in which the UE is unaware of changed System
Information, because of wraparound of MIB value tag or cell value tag. The limit
also reduces the UE battery consumption.

2.3.9 Persistent Storage of CRS Tables

For identifying new neighbors, ANR Mobility is collecting and evaluating

statistical data in CRS tables
The statistics are kept in volatile RAM memory which is lost in case of RNC
restart, board restart or Iub remoduling. To prevent complete loss of CRSs, the
most valuable parts of statistics in RAM are, by default, periodically saved into
persistent storage, in the form of files on flash drive. The files (CRS files) have
the .crs extension and are located on module boards under the ANR directory,
for example: /p000500/ANR/ on board 5 in the Main Subrack. The saved
statistics are recovered from .crs files after the RNC restart, board restart or Iub
remoduling. As a result, the ANR Mobility does not start with empty CRS tables
after restart or remoduling.

The periodical saving of CRS tables can be deactivated by setting the

anrPersistentStorageEnabled attribute to FALSE. If ANR is activated but
persistent storage is deactivated, the contents of CRS tables are lost after each
restart or Iub remoduling and later the tables are built from scratch, based on
new handover statistics. The other aspects of ANR Mobility are not affected by
deactivation of persistent storage.

At the moment of setting attribute anrPersistentStorageEnabled to FALSE,

the .crs files are deleted, regardless of the activation state of the ANR Mobility
feature.

ANR Mobility can be deactivated without setting the

anrPersistentStorageEnabled attribute to FALSE. In that case, the .crs files
are kept on flash drive and used to read their content into CRS tables when ANR
Mobility is activated again. Such procedure can be used, for example, when
temporary modifications in the network configuration are not intended to be
reflected in CRS tables.

Persistent storage of CRS tables (anrPersistentStorageEnabled) is specially

beneficial when auto-creating of neighbor relations (anrAddRelationEnabled)
is deactivated, because, in this situation, CRS tables are the only form of
preserving statistics gathered from handover attempts. It is also possible to test
ANR in easy and safe way. With auto-create disabled the feature finds any
possible relations that have been missed. In this state ANR does not create new
UtranRelations, therefore there is no need to remove them.

Persistent storage of CRS tables is activated by default. The ANCL tables are not
stored in persistent storage.

10 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Parameters

3 Parameters

This section describes parameters introduced by the ANR Mobility feature and
parameters affected by activating the feature.

3.1 Introduced Parameters

parameters introduced by the ANR Mobility feature.

Table 2 Introduced Parameters

Parameter Description
Anr::anrCellAddRelationMax Defines the maximum number of relations per source
cell that can be added by ANR Mobility during each
evaluation period. This limit on the rate of instance
creation can be used to limit the amount of O&M load
caused by the feature.
AnrIafUtran::anrAddRelationEnabled Enables or disables the ANR UTRAN intra-frequency
feature ability to create intra-frequency neighbor
relations in the RNC configuration database.
AnrIafUtran::anrCandidateAbsPropThresh Defines the threshold for the absolute number of ANR-
initiated handover proposals needed for a target cell
candidate to reach reliable statistics. Reliable statistics is
required for determining a good intra-frequency
neighbor relation.
AnrIafUtran::anrCandidateExpirePeriod Defines the expiry period for candidate cells in ANR
internal statistics. After this time, if a good neighbor
relation has not been found before, the ANR statistics is
removed.
AnrIafUtran::anrCandidateLowerThresh Defines the threshold to determine if the degree of
successful ANR handovers is too low. When the degree
is too low, ANR Mobility is prevented from performing
handover to such candidates.
AnrIafUtran::anrCandidateUpperThresh Defines the threshold to determine if the degree of
successful ANR handovers is high enough. When equal
or higher than the threshold, the ANR candidate is used
for evaluation of a new intra-frequency neighbor
relation.
AnrIafUtran::anrDsReportFilterEcno Defines the Ec/No threshold used by the ANR CPICH
filter. DS reports having a CPICH Ec/No value lower than
the threshold are not considered by the ANR UTRAN
intra-frequency feature.
AnrIafUtran::anrDsReportFilterEnabled Enables or disables the ANR CPICH filter, which is used
only when ANR Mobility is activated, to filter the
required certain levels of Ec/No and RSCP in Detected
Set measurement reports.
AnrIafUtran::anrDsReportFilterRscp Defines the RSCP threshold used by the ANR CPICH
filter. DS reports having a CPICH RSCP value lower than
the threshold are not considered by the ANR UTRAN
intra-frequency feature.
UtranCell::anrIafUtranCellConfig Enables or disables the ANR Mobility function in this cell
for intra-frequency relations.
UtranCell::anrIafUtranCellConfig::anrEnabl Enables or disables the ANR Mobility function in a cell.
ed
UtranCell::anrIafUtranCellConfig::relation Enables or disables the creation of UtranRelation MOs
AddEnabled by ANR Mobility at UtranCell level.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 11

 ANR Mobility

Parameter Description
UtranCell::anrIafUtranCellConfig.sib11IafA Enables or disables ANR IAF ANCL as input for building
nclEnabled SIB11. This parameter also activates limiting the
frequency of ANR-triggered SIB11 updates to four
updates for every six hours.
UtranCell::AnrBlackList::anrBlackTargetCel Lists the references to target cells which ANR Mobility is
ls not allowed to use when performing handovers or
creating relations.
UtranRelation::createdBy Indicates if the instance of UtranRelation is created by
the operator or ANR Mobility. Read-only attribute.
UtranRelation::creationTime Indicates the date and time when the neighbor relation
is created. Read-only attribute.
AnrIafUtran::anrAttRatioBadCrs Indicates the attempt ratio threshold value of a cell for
detection of a "bad CRS". If the attempt ratio is below
the configured value for any of the candidate cells in a
CRS, the CRS is considered to be bad and no relation can
be written to the database for this CRS.
Anr::anrPersistentStorageEnabled Enables or disables the ANR persistent storage.
AnrIafUtran.anrAddRelationEnabled Enables creating UtranRelation MOs by ANR Mobility
at RNC level.
UtranRelation::hcsSib11Config.penaltyTime
UtranRelation::hcsSib11Config.qHcs
UtranRelation::hcsSib11Config.temporaryOff
set1
The parameters take on effect if sib11IafAnclEnabled
UtranRelation::hcsSib11Config.temporaryOff is set to TRUE, ANR Mobility is activated and ANR IAF
set2 ANCL is enabled.
UtranRelation::qOffset1sn
UtranRelation::qOffset2sn
UtranRelation::hcsSib11Config.hcsPrio

3.2 Affected Parameters

Table 3 Parameters Affecting the Feature

Parameter Description
UtranRelation::hcsSib11Config.h
csPrio
UtranRelation::hcsSib11Config.p
enaltyTime
UtranRelation::hcsSib11Config.q
Hcs The parameters take no effect if
sib11IafAnclEnabled is set to TRUE,
UtranRelation::hcsSib11Config.t ANR Mobility is activated and ANR
emporaryOffset1 IAF ANCL is enabled.
UtranRelation::hcsSib11Config.t
emporaryOffset2
UtranRelation::qOffset1sn
UtranRelation::qOffset2sn

12 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Network Impact

4 Network Impact

This section describes how the ANR Mobility feature impacts the network
functions and capabilities.

4.1 Subscriber Capacity

No feature-specific information is identified.

4.2 Network Performance

This section provides information on the impact of the feature on network
performance.

ANR Mobility is based on ANR internal statistics where target cell candidates are
populated and evaluated with handover attempts to the candidates. To evaluate
neighbor relation, a number of handover attempts is required.

The time needed to detect a neighbor cell relation depends on:

— The network configuration.

— The degree of scrambling code reuse on a frequency.

— ANR configuration (see Performing Candidate Cell Evaluation on page 22).

— Intensity of the UE mobility in the cell area.

After the evaluation phase (the phase when unknown neighbors are being
identified), ANR Mobility improves retainability. This is seen in the decreased
dropped call ratio.

Handover attempts to cell candidates are intended as a neighbor relation

evaluation mechanism. The ANR evaluation phase when this mechanism is used
can be referred to as handover on-the-fly. This mechanism is less precise than a
properly defined Utran Relation to target cell, as handover on-the-fly is based on
the unmonitored DS report from an UE. Due to this, a far-sighted cell may be
picked up as an SHO neighbor. It is expected that during the ANR evaluation
phase there will be a slight increase in speech drop KPIs.

In networks with multiple WCDMA carriers, the number of Inter-Frequency

Handovers is expected to decrease. Similarly, the number of IRAT handovers to
GSM is expected to decrease if the external GSM network is defined.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 13

 ANR Mobility

4.3 Hardware
This section provides information on the impact of the feature on hardware.

This feature is supported for all RNC types.

4.4 Inter-Node Interface

This section provides information on the impact on inter-node interfaces.

The following interfaces are affected when the ANR Mobility feature is activated:

— NBAP: signaling intensity can increase with ANR-initiated handovers and UL

Synchronization results (with the following messages: "RADIO LINK SETUP",
"RADIO LINK ADDITION" and "RL RESTORE INDICATION"). Signalling
intensity can increase when ANR performs handover evaluation to candidate
cells.

— RRC: signaling intensity increases with ANR-initiated handover (with the "AS
UPDATE" message).

4.5 Other Network Elements

No feature-specific information is identified.

14 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Associated Features and Affected Functions

5 Associated Features and Affected Functions

This section describes how the ANR Mobility feature affects other features and
functions.

5.1 Prerequisite Features

This feature has no prerequisite features.

5.2 Affected Features

Table 4 describes the dependencies for ANR Mobility on other features.

Table 4 Feature Dependencies

Feature Relationship Description
Shared RAN (MOCN) Multiple PLMN Support (FAJ Conflicting The Shared RAN (MOCN) multiple PLMN support
121 2530) feature captures soft handover triggers and does
not forward them to ANR feature, thus ANR
statistics are not gathered and UtranRelations are
not created.
Hierarchical Cell Structures (FAJ 121 1055) Conflicting If the attribute sib11lafAnclEnabled is set to
TRUE, the HSC-related parameters defined in
UtranRelation:hcsSib11Config are not broadcast
in SIB11.
The parameters UtranRelation::qOffset1sn and
UtranRelation::qOffset2sn are not broadcast in
SIB11 if attribute sib11lafAnclEnabled is set to
TRUE.

5.3 Related Features

Note: The use of OSS or ENM features Neighbor Cell Support, Radio Network
Optimization, and Automatic Scrambling Code Selection and Conflict
Resolution is not recommended as these features do not have access to
ANR internal data and risk taking decision based on incomplete data

Table 5
Feature Relationship Description
OSS-RC feature Related The feature facilitates
Automatic Neighbor controlling AND Mobility
Relation Management, parameters.
WCDMA (ANRM-W)
(FAJ) 121 3261

183/1553-HSD 101 02/1 Uen N | 2018-11-05 15

 ANR Mobility

Feature Relationship Description

ANR Inter-Frequency Related The feature enables
(FAJ 121 4564) automatic detection of
IEF relations.

5.4 Affected System Functions

Table 6 lists functions affected by the ANR Mobility feature.

Table 6 Affected System Functions

Function Description
Handover ANR-triggered handover is performed on many of the received Undefined cell DS
reports. When the ANR Mobility feature is deactivated or not installed, the
reports are discarded.
Idle Mode and Common SIB11 can be configured to include ANR-discovered neighbors in Intra-
Channel Behavior Frequency list.

16 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Performance

6 Performance

This section describes performance indicators, counters, and events associated

with the ANR Mobility feature.

6.1 KPIs
Table 7 lists the main Key Performance Indicators (KPIs) associated with the
ANR Mobility feature.

Table 7 KPIs
KPI Description
Sp_R_D It is expected to improve in the long term, after the ANR Mobility evaluation
phase.

6.2 Counters
More information about counters can be found in Managed Object Model RNC
and Managed Object Model RBS.

6.2.1 Introduced Counters

Table 8 lists the counters introduced by the ANR Mobility feature.

Table 8 Counters Introduced by ANR Mobility Feature

Counter Description
UtranCell::pmAnrRelationAdd Incremented by one when ANR Mobility adds a neighbor relation in
the configuration database, regardless of the neighbor frequency or
IRAT relation type.
UtranCell.pmSumAnrIafRelation Sum of all sample values recorded during a ROP for the number of
cells in the IAF ANCL on UtranCell level.
UtranCell.pmSamplesAnrIafRelatio Number of samples recorded within the ROP for
n pmSumAnrIafRelation.

6.2.2 Associated Counters

ANR Mobility feature allows handover without the existence of UtranRelation

MO instance. As a result, such handovers cannot be observed by handover-
related PM counters on UtranRelation MOs. Instead, the PM counters on
UtranCell MOs should be used, if ANR Mobility feature is activated. These
counters are incremented, regardless of whether UtranRelation MO is defined
or not.

Table 9 lists PM counters which can be used for observing SOHO when ANR
Mobility feature is activated.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 17

 ANR Mobility

Table 9 Counters Associated with ANR Mobility Feature

Counter Description
UtranCell::pmAttRlAddPreAdmSpeech
UtranCell::pmAttRlAddPostAdmSpeech
UtranCell::pmAttRlAddPreRrcSpeech
UtranCell::pmSuccRlAddSpeech
UtranCell::pmAttRlAddPreAdmSpeechHs
UtranCell::pmAttRlAddPostAdmSpeechHs
Handover-related counters, incremented on
UtranCell::pmAttRlAddPreRrcSpeechHs UtranCell MO instance which is representing
UtranCell::pmSuccRlAddSpeechHs originating best cell in Active Set (best cell before
UtranCell::pmAttRlAddPreAdmHs handover). Listed counters are incremented at
UtranCell::pmAttRlAddPostAdmHs different handover phases and for different RAB
UtranCell::pmAttRlAddPreRrcHs types.
UtranCell::pmSuccRlAddHs
UtranCell::pmAttRlAddPreAdmAll
UtranCell::pmAttRlAddPostAdmAll
UtranCell::pmAttRlAddPreRrcAll
UtranCell::pmSuccRlAddAll

6.2.3 Affected Counters

When the ANR Mobility feature is activated, Undefined cell DS reports received
by the SRNC are handled by ANR Mobility instead of being discarded. The feature
uses ANR internal statistics where target cell candidates are evaluated by
handover attempts. As a result, some PM counters listed in Table 10 can be
affected, especially during the ANR Mobility candidates evaluation phase.

Table 10 lists a number of existing counters that the ANR Mobility feature can
affect. Definitions of counters do not change. However, the counter values can
change since ANR Mobility performs handover to Undefined cells during its
evaluation of target cell candidates.

Table 10 Counters Affected by ANR Mobility Feature

Counter Description
IurLink::pmNoOfRlForDriftingUesPerDrnc
UtranCell::pmNoOfRlForDriftingUes
UtranCell::pmNoOfRlForNonDriftingUes
UtranCell::pmNoSysRelSpeechNeighbr
UtranCell::pmNoTimesRlAddToActSet
UtranCell::pmNoTimesRlDelFrActSet
UtranCell::pmNoTimesRlRepInActSet
UtranCell::pmRlAddAttemptsBestCellCsConvers
The PM counters are affected by ANR Mobility as
UtranCell::pmRlAddAttemptsBestCellPacketHigh handover is done to Undefined cells.
UtranCell::pmRlAddAttemptsBestCellPacketLow
UtranCell::pmRlAddAttemptsBestCellSpeech
UtranCell::pmRlAddAttemptsBestCellStandAlone
UtranCell::pmRlAddAttemptsBestCellStream
UtranCell::pmRlAddSuccessBestCellCsConvers
UtranCell::pmRlAddSuccessBestCellPacketHigh
UtranCell::pmRlAddSuccessBestCellPacketLow

18 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Performance

Counter Description
UtranCell::pmRlAddSuccessBestCellSpeech
UtranCell::pmRlAddSuccessBestCellStandAlone
UtranCell::pmRlAddSuccessBestCellStream
Handover::pmSofterHoAttemptNonIur
Handover::pmSofterHoSuccessNonIur
Handover::pmSoftHoAttemptNonIur
Handover::pmSoftHoSuccessNonIur
Handover::pmSoftSofterHoAttemptIur
Handover::pmSoftSofterHoSuccessIur

6.3 Events
Table 11 provides the events introduced by the ANR Mobility feature, Table 12
lists the events that are modified, and Table 13 lists events that are affected.

Table 11 Events Introduced by ANR Mobility

Event Event Parameter Description
INTERNAL_ANR_ADD_REL EVENT_PARAM_PREVENTED_RELA When ANR Mobility is prevented
ATION_PREVENTED TION_TYPE, from creating an intra-frequency
EVENT_PARAM_PREVENTED_RELA neighbor relation, the GPEH event
TION_REASON indicates the relation and reason.
This event is reported when:

— Neighbor Cell List (NCL) is full in a

source cell,

— Writing of detected relations is

deactivated either on RNC or
source cell level,

— IAF ANCL is disabled.

Table 12 Events Modified by ANR Mobility

Event Event Parameter Description
INTERNAL_SOFT_HANDOV EVENT_PARAM_ANR_INITIATED, The GPEH event with the indicated
ER_EXECUTION EVENT_VALUE_ANR_ADD_CELL_AT parameter is generated when ANR
TEMPT Mobility triggers an ANR handover
attempt.
This event value indicates that the
handover execution is caused by an
Undefined cell DS report, which
triggers the addition of ANR-initiated
Radio Link (RL).
The GPEH event, triggered by
Defined cell DS reports is not
affected.
EVENT_PARAM_ANR_INITIATED, The GPEH event with the indicated
EVENT_VALUE_ANR_REPLACE_CEL parameter is generated when ANR
L_ATTEMPT Mobility triggers an ANR handover
attempt.
This event value indicates that the
handover execution is caused by an
Undefined cell DS report, which
triggers the addition of ANR-initiated
RL and the removal of an existing RL
from the AS.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 19

 ANR Mobility

Event Event Parameter Description

The GPEH event, triggered by
Defined cell DS reports is not
affected.
EVENT_PARAM_ANR_INITIATED, The GPEH event with the indicated
EVENT_VALUE_ANR_ADDED_CELL_ parameter is generated when ANR
REMOVED_NO_UL_SYNCH Mobility triggers an ANR handover
attempt.
This event value indicates that the
handover execution is caused by an
Undefined cell DS report, which
triggers the removal of ANR-initiated
RL, when no Uplink Synchronization
is achieved before timer expiry.
The GPEH event, triggered by
Defined cell DS reports is not
affected.

Table 13 Events Affected by ANR Mobility

Event Event Parameter Description
INTERNAL_SOHO_DS_MIS No specific event parameter. Captured at the reception of a
SING_NEIGHBOUR measurement report for event 1a,
event 1c, or event 1d where the
triggering cell is not included in
Neighbor Set.
When ANR Mobility is activated, the
event can be less frequently reported.
INTERNAL_SOHO_DS_UNM No specific event parameter. Captured when handover proposal is
ONITORED_NEIGHBOUR received, where the proposed cell is
included in the neighbor set, but not
included in the monitored set.
When ANR Mobility is activated, non-
full neighbor cell lists can increase in
size, which can increase the
frequency of this event.

Note: More GPEH events applicable during Soft Handover procedures can be
generated. The GPEH data can be mitigated by not activating the events
that are frequently generated. The
INTERNAL_SOFT_HANDOVER_EXECUTION event is recommended to
be activated to verify the behavior of the ANR Mobility feature, which
can reflect if a Soft Handover is executed because of the ANR Mobility.
Another way to mitigate high GPEH data volumes is to activate the ANR
Mobility in clusters rather than in a whole RNC directly.

More information about events can be found in General Performance Event

Handling RBS and General Performance Event Handling RNC.

20 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Operation and Maintenance

7 Operation and Maintenance

This section provides Operation and Maintenance (O&M) information for the
ANR Mobility feature.

7.1 Activate the Feature

7.1.1 Preconditions
This feature has no preconditions for activating.

7.1.2 Activate the Feature

The feature is license-controlled for each RNC (CXC 403 0136). The operator can
activate ANR in the chosen cells and then gradually increase the number of ANR-
activated cells.

To activate the feature, do the following:

Steps

1. Set the featureState attribute to ACTIVATED for RncFeature instance MO

AnrMobility.

2. Activate the feature on cell level by setting the

anrIafUtranCellConfig.anrEnabled attribute in a specific UtranCell MO
instance to TRUE.
For more information about licenses, refer to Licenses and Hardware
Activation Codes in Ericsson Software Model.
Optional:

3. Activate the automatic removal of UtranRelation MOs by setting attributes

UtranCell.anrIafUtrancellConfig.relationRemoveEnabled and
AnrIafUtran.anrRemoveRelationEnabled to TRUE.

7.2 Deactivate the Feature

7.2.1 Preconditions
This feature has no preconditions for deactivating.

183/1553-HSD 101 02/1 Uen N | 2018-11-05 21

 ANR Mobility

7.2.2 Deactivate the Feature

The ANR feature can be deactivated on cell level by setting the
anrIafUtranCellConfig.anrEnabled attribute in a specific UtranCell MO
instance to FALSE

ANR Mobility can also be deactivated partially, by disabling the following:

— creating neighbor relations in the configuration database

(anrAddRelationEnabled).

— using persistent storage (anrPersistentStorageEnabled).

Note: The ANR Mobility feature deactivation does not remove the CRS
files.

— considering Undefined Cell DS reports with poor received signal strength

(anrDsReportFilterEnabled).

— using ANCL (AnrIafUtran.anrAnclEnabled)

— building SIB 11 based on IAF ANCL

(UtranCell::anrIafUtranCellConfig.sib11IafAnclEnabled)

For more information about licenses, refer to Licenses and Hardware Activation
Codes in Ericsson Software Model.

7.3 Engineering Guidelines

The purpose of this section is to provide additional information on practical
engineering aspects about how to use parameters to achieve certain behaviors.

To enable the feature in limited sets of cells, before activating the feature on RNC
set the anrIafUtranCellConfig.anrEnabled attribute to FALSE in all cells
except for the designated area.

7.3.1 Setting the DS Report CPICH Filter

The DS report CPICH filter is used to filter the Undefined Cell DS reports
regarding Ec/No or RSCP, or both. The operator can, for example, use this filter to
avoid triggering ANR Mobility by too weak DS reported cells.

Both thresholds are checked by ANR Mobility independently. If only one is

required to be checked by ANR Mobility, the other one must be set to the lowest
possible value: -24.0 dB (-240 * 0.1 dB) for Ec/No and -120 dBm for RSCP.

7.3.2 Performing Candidate Cell Evaluation

As a detected cell Primary Scrambling Code can be used by many cells on the
same frequency, ANR Mobility handles a number of Detected Set Reports to

22 183/1553-HSD 101 02/1 Uen N | 2018-11-05

 Operation and Maintenance

identify a correct target cell to create a UtranRelation in the RNC. Because the
DS report contains only a scrambling code of the detected cell, ANR Mobility tries
out all cells using the same scrambling code and the same uarfcnDl and uarfcnUl.
These cells are used as candidates for handover. At each DS report, ANR Mobility
chooses the next candidate cell and a handover to that cell is performed. If the
correct cell was chosen (assessed on the basis of detected Uplink
Synchronization), ANR Mobility updates the internal statistics.

Four parameters control detecting the good cell candidate:

anrCandidateAbsPropThresh, anrCandidateLowerThresh,
anrCandidateUpperThresh, and anrCandidateExpirePeriod, see Parameters
on page 11.

The anrCandidateAbsPropThresh controls the number of handover attempts

per each candidate cell which are required by ANR Mobility to perform evaluation
of the statistics. Until that requirement is fulfilled, ANR Mobility tries all candidate
cells in a round-robin manner. Once all candidates have been proposed required
number of times, ANR Mobility performs the initial evaluation of candidate cells
statistics.

Candidate cells for which a successful handover ratio is lower than

anrCandidateLowerThresh are excluded from further evaluation (the number of
unnecessary handover attempts to the wrong candidate is limited). If other
candidate cells handover success ratio is above anrCandidateLowerThresh but
still below anrCandidateUpperThresh, the selection of candidate cells for
handover continues until there is a candidate cell showing a handover success
ratio above anrCandidateUpperThresh. When such a cell is detected, the cell
relation is ready to be written into the RNC configuration database.

If a cell relation is not detected within anrCandidateExpirePeriod time, the

ANR statistics for this Primary Scrambling Code is removed from the source cell.

7.3.3 Assessing Candidate Cells in Neighbor RNCs and Cluster Member RNCs
A potential candidate target cell belonging to a neighbor RNC or cluster member
RNC is also populated in ANR Mobility internal statistics if the reported cell is
defined in the SRNC as ExternalUtranCell for neighbor RNC cells or as
RemoteUtranCell for cluster member RNC cells.

If the Undefined Cell which the UE reported belongs to a neighbor RNC but is not
configured as ExternalUtranCell or as RemoteUtranCell in the SRNC, then
ANR Mobility cannot perform handover attempts to that cell.

7.3.4 Downgrading RNC with ANR Persistent Storage Enhancement

When downgrading from release W16A or later to release W15.1 or earlier, the
CRS files (if created by ANR Mobility feature) is left on disks. It is recommended
to manually remove these files (together with the ANR directory) to prevent
unnecessary disk space use. The ANR directory (if created by ANR Mobility

183/1553-HSD 101 02/1 Uen N | 2018-11-05 23

 ANR Mobility

feature) is located on each module board, for example /p000500/ANR/ on board

5 in the Main Subrack.

7.3.5 Synchronizing MO Database with ANCL

ANR Mobility can be configured to create and delete UtranRelation MOs. By

default, creating MOs is activated and deleting is deactivated.
Content of ANCL is lost at restart. ANR-created UtranRelation MOs allow to
permanently save the ANR-discovered neighbors.

The number of IAF UtranRelation Mos is limited to 31 per cell. Defining

unnecessary MOs is not recommended.

ANR Mobility can be configured to automatically delete UtranRelation MOs

which represent neighbors not reported by the UEs for two weeks.

24 183/1553-HSD 101 02/1 Uen N | 2018-11-05