Microwave 2020 Report

3G ANR (SHO / IFHO)
Telefonica Venezuela
This presentation constitutes proprietary and confidential information of Cellwize Wireless Technologies PTE Ltd.
This presentation may not be disclosed, used or duplicated, in whole or in part, without the prior written consent of Cellwize Wireless Technologies PTE Ltd.
Customer Journey Spans Multiple RATs and Handovers
Over 40 Mobility Scenarios Supported by SON
CONNECTED IDLE MODE CS FALLBACK PS
LEGEND
& IDLE MODE CONNECTED MODE Vendor Specific
2 G 3 G 4 G
2 G
Inter-PLMN Automatic Whitelists/ Blacklists
SIB11 NBR Prioritization
PSC Collision Minimization

Redirection Blind HO
3 G
Automatic Whitelists/ Blacklists Coverage Relation
Inter-PLMN
4 G
Supported Mobility Scenarios
eNB MME MME
S1
Cell
Cell IntraF HO relation
X2
Cell LTE F1
Same LTE Frequency External Cell
2G HO relation 3G HO relation InterF HO relation
LTE F2 Other LTE Frequency

3G Cell External Cell
UMTS 3G Frequency
2G Cell
GSM 2G Frequency Group
ANR High Level flow
Network and SON Cache: CM loaded periodically, Physical loaded periodically, PM loaded at available frequency
Neighbor Execution Statistics: Neighbors PM

Network Extensions Layer PDR
HO Preparation Attempts Execution
Outgoing HO Execution Success and Attempts Statistics
Geo-Impact
Candidates Incoming HO Execution Success and Attempts
Black/White Lists Optimization Engine

1. Basic Ranking Adaptive RAN Coordinator
2. Select target frequencies
Sector Constraints 3. Locking
4. Deletion/Block: Policies, SR, Black lists, constraints, PCI Collision • Auto Black-Lists
Mobility Policy 5. Addition/Unblock: Policies, Geo-Impact, White lists, constraints
6. Trimming • NBR Performance
7. Replacements • Ping-pong Detection
8. Neighbor SWAP KPI
Analytics,
Optimization Decisions Reporting,
Custom Policies and Vendor-Specific Features Support and Alerts
Online Provisioning Vendor Command

Mobility
Updates of Selected Adaptor Syntax SON Actions
Policy
CM Tables Templates Repository
Plan Vendor
Plan Builder
Processor Adaptor
Vendor
Parameter Adaptor
Design
3G ANR – Intrafrequency HO Optimization
▪ Module Description
• Rank existing neighbors by HO Impact
• Rank candidates by Missing Neighbor Event Impact
• Determine candidates to add
• Determine candidates to delete
• Determine candidates to replace
• Apply protections for add/delete actions
F1 F1
3G ANR – Intrafrequency HO Optimization
Deletions based on KPI
Constraints included to Performance and Distance
A Analyze each Neighbor in
B Configuration E
the network
C
Additions based on Measurements
& GeoImpact
D
Intra-Frequency and Inter-Frequency ANR Concept
• Management of existing neighbors based on KPI counters per neighbor
• Using HO execution attempts, success counters and log information (Nokia uses PM)
• Removing neighbors with low SR or low HO attempts
• Resolving of PSC conflicts and correcting wrong neighbors
• Geo-based identification
• Strictly controlling the neighbor list length
• Removing expired neighbors
• Auto-black listing for neighbors with low HO chances
• Policy enforcement
• Symmetry, co-located policy, add/remove action constraints, add/delete thresholds, …
• Management of external cells RNC 21
22
• Management of Inter-PLMN policy 23
x
7 Proprietary & Confidential

3G ANR – Intrafrequency HO Optimization - Inputs
• Geo-based impact Input to consider:
• Distance between sectors and antenna heights – 30
30
estimates RF propagation loss 31
32
• Azimuth and antenna relative gain – affects RF
propagation loss
• Cells density – automatic detection of Dense
Urban/Urban/Sub Urban environment
• Cell type – Macro/Micro/Indoor behavior
Algorithm 3G SHO
• Measurement Impact Input:

Missing Detected Set
Neighbor (GPEH & PCHR or PM
detection counters)
• Detected Set (DN) :
• The cells detected that are not part of AS or MS
Redundant Per Neighbor Pair HO
• Can then be an Unmonitored or a Missing neighbor Neighbor Statistics (Counters)
Target Sector Neighbor Tier and distance

Recognition algorithm

3G ANR – Interfrequency HO Optimization
Cell A Cell B ➢ A and B are neighbors (SHO)
➢ A and C are neighbors (IFHO or IRAT)
➢ B and C are not neighbors (IFHO or IRAT)
IFHO/IRATHO IFHO/IRATHO
NBR List NBR List 1. UE is in SHO state with cells A&B
Cell A
SHO Cell B 2. A HHO (IFHO or IRAT) happens between A and C
B to C ≠ NBR
A to C = NBR
 B&C can be considered as potential neighbors (IFHO or
IRAT)
HHO Event
Cell C
HHO event from SHO state when Active Set has > 1 cell
provides ability to detect possible candidate for IFHO/IRATHO Neighbor Lists

ANR – Algorithm Logic
CT™
• Rank existing neighbors by HO Impact (combining handover attempts and geo data)
• Determine neighbors to DELETE (Low success rate and hand over attempts)
• Rank candidates by GEO impact (Azimuth and distance score)
• Rank candidates by and Distance Tier
• Apply protections for add/delete actions (List length)
• Determine candidates to ADD
• Resolving PCI conflicts and correcting wrong neighbors
• External cells management

ANR optimization | Geo-based Impact
• Geo-based impacts to consider:
• Cells density – automatic detection of Dense Urban/Urban/Sub Urban environment
• Distance between sectors and antenna heights – estimates RF propagation loss
• Azimuth and antenna relative gain – affects RF propagation loss
• Cell type – Macro/Micro/Indoor behavior
CT™
30
30
31
32
• Geo based impacts are:

• Used for 2G/3G/4G ANR optimization extension
• Used to create pseudo NL or prioritize NL when there is no other way to do it
• Trial & Error method -> convergence

ANR | Mobility Policy
CT™
Powerful scripting engine to

allow flexible operators’
mobility policy
Allow neighbor creation

Don’t allow neighbor creation

ANR | Algorithm Protections
CO-LOCATION SYMMETRY NEIGHBOR LIST MAXIMUM RELIABLE DATA CONSISTENCY
TRIMMING NUMBER OF FOR CHECKS
CHANGES PER OPTIMIZATION
OPTIMIZATION
CYCLE
ANR ANR protects

automatically ANR performs
ANR considers the maximum ANR
creates neighbor consistency
a list of neighbor list minimizes the ANR avoids
relations that checks for cross
co-located length by optimization neighbor list
support active technology
(Co-Sector / reducing the cycles by changes upon
handovers & idle GSM/UMTS/LTE
Co-Site) sectors cell reselection existing number focusing on the recognition of
neighbor
that cannot be for different of neighbors to most significant unreliable data
external table
deleted multi-carrier fit the changes
updates
strategy support limitations

Individual Neighbors Optimization Phase
Serving cell Locking Deletions/ Additions/ Do Nothing

exclusions • White-listed Block Unblock • Keep existing
• Low # of HO • Co-site/ co sector • Manually black listed • Geo-based neighbors with
attempts policy • Inter-MNC forbidden high enough SR &
• Swap by same PCI significant HO
• Inactive • Enforced co sector/co-
• Low backlog site/inter-site policy • Replacement of counts
duration • Small cell low geo impact
• Low HO SR • Do not add
• Inactive serving • Outgoing &/or • Low HO Impact neighbors missing neighbors
• Sectors inside incoming lock by • PCI collision • Symmetry with low geo-
overlapping sector constraints • Trimming (max NL len.) additions impact
polygon • Stub sector • Limit by “max delete #” • Limit by “Max add
constraint
#” constraint

ANR SHO Configuration
3G INTRA: Optimization Task Configuration
CT™
Maximal # NBRs to ADD:

Maximum new neighbors to add per optimization cycle
If more are available, the ones that rank first will be added
CT™
Maximal # NBRs to DELETE:

Maximum neighbors to delete per optimization cycle
If more are available, the ones that rank lowest will

be removed first.
CT™
Absolute Candidate threshold to ADD:

Absolute impact = (HO Impact(1-A)+GEO Impact*A)
A=GEO impact weight
When the calculated absolute impact is above this
threshold the target sector will be a candidate for
addition
3G INTRA : Optimization Task Configuration
CT™
HO impact threshold to DELETE:

HO Impact= Target NBR HO attempts / all NBRs HO attempts
When the HO impact value is below this threshold, the defined

neighbor is a candidate for deletion
CT™
NBR Success rate threshold to DELETE:

Success rate=Successful HO attempts / All HO attempts
A neighbor with success rate below this value will be a

candidate for deletion
CT™
Geo impact weight:

The weight given for Geo Vs. Measurements
Geo calculation is done for neighbors and candidates

CT™
Minimal Distance Co-location to DELETE(m):

Don’t delete a neighbor below this value
If the distance of the neighbor is less than the defined

value, this sector should not be deleted (via policy)
CT™
Maximal Distance Co-location to ADD(m):

Consider candidate below this value
If the distance of the candidate is less than

the defined value, this sector should be
considered for addition (via policy)
CT™
Max Distance Tier:

Consider candidate to add according to distance Tier
A candidate will not be considered for addition if its

distance tier classification is above this value
CT™
Max Neighbor Tier:

Consider candidate to add according to neighbor
Tier

neighbor tier classification is above this value (See
next slide)
▪ NEIGHBOR TIER
ANR – Tier Logic
Tier 5
Tier 4
Tier 3
Tier 2
Tier 1
Cell A
CT™
Optimize data backlog:

Optimization backlog to be optimized
When this value is set to 7200, the optimization will

run on the last 5 days data
CT™
Symmetric Relations:
Symmetrical decision making in additions
Each candidate addition will be checked for the

existence of opposite incoming neighbor relations.
When the opposite incoming neighbor relation does
not exist, additional opposite relation will be added
CT™
Enforce symmetry:
Enforce symmetry policy
Each existing outgoing neighbor relation should be

checked for the existence of opposite incoming
neighbor relations. When the opposite incoming
neighbor relation does not exist, this neighbor relation
will be added
CT™
Trim for symmetry:

Trim full neighbor list to enable symmetry
Each existing outgoing neighbor relation should be checked

for the existence of opposite incoming neighbor relations.
When the opposite incoming neighbor relation does not
exist, and the neighbor list is full. The list will be trimmed.
CT™
Optimize connected mode priority:

Enable / Disable
When enabled connected mode NBR priority

(Ranking) will be optimized for new added
sectors.
CT™
Apply connected mode update to all NBRs:

Enable / Disable
When enabled connected mode ranking update

will be activated for all existing neighbors
CT™
Operate on active target sectors:

Enable / Disable
When enabled only active target sectors

will be considered for addition
CT™
Operate on in-active target sectors for

DELETE:
Enable / Disable
When enabled only in-active target sectors

will be optimized and considered for addition
CT™
Operate on in-active target sectors for ADD:

Enable / Disable
When enabled only in-active target sectors will be

optimized and considered for addition
CT™
Exclude sectors overlapping polygons:

Enable / Disable
When enabled, sectors in overlapping

polygons will not be optimized
CT™
Maximum overall # NBRs (Intra, Inter &

IRAT):
Total list size
CT™
Maximum GEO impact distance

Maximum size for GEO candidates
When set to 10000, only GEO candidates

below 10000m will be considered
CT™
Maximum # of GEO candidates

Top GEO candidates to be considered
When set to 64, the top 64 GEO candidates

will be considered during optimization
CT™
Apply custom policies

Consider customer specific advanced policies
When enabled, customer unique and advanced

policies that are not reflected in the UI will be
considered before candidate addition
Configuration Per Frequency
Neighbors limits and HO policy
3G INTRA – Configuration per frequency
CT™
Min num of neighbors:

The minimum number of neighbors allowed
When the Neighbor list is at this value there

will be no deletions
CT™
Max num of neighbors:

The maximum number of neighbors allowed
When the Neighbor list is at this size, there

will be no more additions
CT™
Enforce neighbors trimming:

Remove low ranked neighbors
If the defined neighbors exceed the

maximum number of neighbors, remove
the excessive neighbors based on ranking.
CT™
Max distance for addition (km):

Only consider candidates below this distance
If a candidate exceeds this distance, it should

not be considered for addition
CT™
Min distance for deletion (km):

Don’t delete a Neighbor below this distance
If the location of a defined neighbor is

closer than this distance, it should not be
considered for deletion
CT™
Consider Femto cells:

Consider small cells in the optimization
When enabled, the Neighbor list will

include small cells (place will be reserved)
CT™
Allow inter site policies:

Allow addition of candidates from other sites
When set to ON, optimization will allow

additions of inter site base on measurements
CT™
Enforce Inter-site policies:

Inter site relation deletion policy
When set to ON, Defined neighbors from

other sites should be candidates for deletion.
(This option is only active when Allow Inter-
Site Policies is off)
CT™
Allow co-site policies:

Allow candidate addition from co-located site
When set to ON, the optimization will allow

addition of candidates from the co-located
site according to measurements
CT™
Enforce co-site policies:

Consider co-site defined neighbors for deletion
When Enforce Co-Site Policies and Allow Co-Site

Policies are both on, all co-located candidates will be
considered for addition and defined neighbors will
not be considered for deletion.
When Enforce Co-Site Policies is on but Allow Co-Site

Policies is off, no qualified candidates can be
considered for addition and defined neighbors should
be considered as candidates for deletion.
CT™
Allow Inter-MNC policies:

Allow Inter-PLMN
When set to ON, the optimization will Allow

addition of candidates that have a different MNC
(Inter PLMN) according to measurements
CT™
Enforce Inter-MNC policies:

Consider deletion on neighbors from other MNCs
When set to ON, defined neighbors from other

MNCs should be candidates for deletion. (This option
is only active when Allow Inter-MNC Policies is off)
CT™
Maximum allowed Inter PLM neighbors
When the inter PLMN neighbors list reaches this

size there will be no more additions
CT™
Minimal allowed Inter PLM neighbors
When the inter PLMN neighbors list reaches this

size there will be no more deletions
ANR IFHO Configuration
3G-INTER (IFHO) – Task Configuration
Maximal # NBRs to ADD:

Maximum new neighbors to add per optimization cycle
If more are available, the ones that rank first will be added
Maximal # NBRs to delete:

Maximum neighbors to delete per optimization cycle
If more are available, the ones that rank lowest will be

removed first.
Absolute candidate threshold to ADD, %:

Target Candidate Measurement / all Measurements
(Candidates are not defined as neighbors)
When the value is above this threshold the target

sector will be a candidate for addition
HO impact threshold to DELETE, %:

Target NBR HO Measurement / all HO Measurements
When the HO impact is below this value the target sector

will be a candidate for deletion
NBR success rate threshold to DELETE, %:

Successful HO attempts / All HO attempts
A neighbor below this value will be a candidate

for deletion
Geo impact weight:

The factor given for Geo Vs. Measurements
Geo calculation is done for neighbors and

candidates
Minimal Distance Co-location to DELETE(m):

Don’t delete a neighbor below this value
If the distance of the neighbor is less than the

defined value, this sector should not be deleted
Maximal Distance Co-location to ADD(m):

Consider candidate below this value
If the distance of the candidate is less than the

defined value, this sector should be considered
for addition (via policy)
Maximal Distance Tier:

Consider candidate to add according to Distance Tier

distance tier (average neighbor distance) classification
is above this value
Enable Even Distribution:

Distribute the quantity of neighbors per frequency by performance
Consider highest ranking neighbors without regard for their

frequencies
Symmetric Relations:
Symmetrical decision making in additions
Each outgoing neighbor relation should be checked for the

existence of opposite incoming neighbor relations. When
the opposite incoming neighbor relation does not exist,
this neighbor relation should be a candidate for addition
Optimize connected mode priority:

Optimize existing neighbors ranking
When this parameter is enabled, the existing

neighbor list will be ranked according to
performance (selection priority)
Apply connected mode update to all

NBRs:
Update priority for all neighbors
When enabled connected mode ranking

update will be activated for all
Operate on active target sector:

Optimize active sectors
When enabled, active target sectors will

also be considered during the optimization
Operate on inactive target sector for DELETE:

Optimize inactive sectors
When enabled, inactive target sectors will also be

considered for deletion during the optimization
Operate on inactive target sector for ADD:

Optimize inactive sectors
When enabled, inactive target sectors will also be

considered for addition during the optimization
Apply custom policy:

Apply advanced customized policy
When enabled, in addition to the policy defined

here in the UI, another custom advanced policy
will take place and prevent candidates addition in
needed cases
Exclude sectors overlapping polygons:

Enable / Disable
When enabled, sectors in overlapping

polygons will not be optimized
Maximum overall # NBRs (Intra, Inter & IRAT):

Total list size for all ANR neighbors
Maximum GEO impact distance:

Maximum distance to be considered
The GEO algorithm will consider only

candidates at distance below this value.
Maximum # GEO impact candidates:

Maximum number for GEO candidates
If more candidates are found, only the top

ranking candidates will be considered
Configuration Per Frequency
▪ Neighbors limits and HO policy

3G-INTER (IFHO) – Neighbor limits per frequency
CT™
Min num of neighbors:

Minimum number of neighbors
allowed
If the list of neighbors is at this size,

neighbors will not be deleted
CT™
Max num of neighbors:

Maximum number of neighbors allowed
If the list of neighbors is at this size,

there will be no additions
CT™
Enforce neighbors trimming:

Delete exceeded number of neighbors
If the parameter is set to ON, exceeded

number of neighbors will be deleted based
on ranking
CT™
Max distance for addition:

Candidates maximum distance
If the candidate distance is above this

value, he will not be considered for
addition
CT™
Min distance for deletion:

Minimum distance for neighbor
deletion
If the neighbor distance is below this

value, he will not be deleted
CT™
Maximal allowed inter PLMN

neighbors:
Max inter-PLMN list size
If the neighbor list will reach this size

there will be no more additions
CT™
Minimal allowed inter PLMN

neighbors:
Min inter-PLMN list size
If the neighbor list will reach this size

there will be no more deletions
CT™
Inter Frequency policy example
✓ Allow F1 to F3 and vice versa NBR

F2 F4
✓ Allow F2 NBR to F1 & F3 only
✓ Allow F4 NBR to F1 & F3 only
▪ Don’t allow any other relation
F1 F3
850Band 2100Band
Inter Frequency policy with co location example
✓ Allow F1 to F3 and Vice Versa NBR

✓ Allow F2 to F3 NBR F2 F4
✓ Allow F4 to F1 NBR
Co-Located
✓ For Co-Located cells Only
▪ Allow F1 to F2 and Vice Versa NBR
▪ Allow F4 to F4 and Vice Versa NBR F1 F3
▪ Don’t allow any other relation

850Band 2100Band
3G-INTER (IFHO) – Task Configuration (Frequency policy)
CT™
Allow neighbor relationship:

Allow or not according to HO policy
When enabled, neighbors to this

frequency will be created
CT™
Consider small cells:

Reserve space for small cells
If the parameter is set, a place in the

neighbor list will be reserved for small cells
CT™
Allow inter site policies:

Allow addition of candidates from other sites
When set to ON, optimization will allow

additions of inter site base on measurements
CT™
Enforce Inter-site policies:

Inter site relation deletion policy
When set to ON, Defined neighbors from other

sites should be candidates for deletion. (This
option is only active when Allow Inter-Site
Policies is off)
CT™
Enforce co-sector policies:

Enforce candidate addition from co-sector site
When set to ON, the optimization will add

candidates from the co-located sector
CT™
Allow co-site policies:

Allow candidate addition from co-located site
When set to ON, the optimization will allow

addition of candidates from the co-located site
according to measurements
CT™
Enforce co-site policies:

Consider co-site defined neighbors for deletion
When Enforce Co-Site Policies and Allow Co-Site

Policies are both on, all co-located candidates will be
considered for addition and defined neighbors will
not be considered for deletion.
When Enforce Co-Site Policies is on but Allow Co-Site

Policies is off, no qualified candidates can be
considered for addition and defined neighbors should
be considered as candidates for deletion.
CT™
Allow Inter-MNC policies:

Allow Inter-PLMN
When set to ON, the optimization will Allow

addition of candidates that have a different MNC
(Inter PLMN) according to measurements
CT™
Enforce Inter-MNC policies:

Consider deletion on neighbors from other MNCs
When set to ON, defined neighbors from other

MNCs should be candidates for deletion. (This
option is only active when Allow Inter-MNC
Policies is off)

Microwave 2020 Report

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Microwave 2020 Report

Загружено:

Авторское право:

Доступные форматы

3G ANR (SHO / IFHO)

Inter-PLMN Automatic Whitelists/ Blacklists

SIB11 NBR Prioritization

PSC Collision Minimization

Automatic Whitelists/ Blacklists Coverage Relation

2G HO relation 3G HO relation InterF HO relation

LTE F2 Other LTE Frequency

Neighbor Execution Statistics: Neighbors PM

Black/White Lists Optimization Engine

Online Provisioning Vendor Command

7 Proprietary & Confidential

• Measurement Impact Input:

Target Sector Neighbor Tier and distance

8 Proprietary & Confidential

9 Proprietary & Confidential

10 Proprietary & Confidential

• Geo based impacts are:

11 Proprietary & Confidential

Powerful scripting engine to

Allow neighbor creation

12 Proprietary & Confidential

ANR ANR protects

13 Proprietary & Confidential

Serving cell Locking Deletions/ Additions/ Do Nothing

14 Proprietary & Confidential

Maximal # NBRs to ADD:

Maximal # NBRs to DELETE:

If more are available, the ones that rank lowest will

Absolute Candidate threshold to ADD:

HO impact threshold to DELETE:

When the HO impact value is below this threshold, the defined

NBR Success rate threshold to DELETE:

A neighbor with success rate below this value will be a

Geo impact weight:

Geo calculation is done for neighbors and candidates

Minimal Distance Co-location to DELETE(m):

If the distance of the neighbor is less than the defined

Maximal Distance Co-location to ADD(m):

If the distance of the candidate is less than

Max Distance Tier:

A candidate will not be considered for addition if its

Max Neighbor Tier:

A candidate will not be considered for addition if its

Optimize data backlog:

When this value is set to 7200, the optimization will

Each candidate addition will be checked for the

Each existing outgoing neighbor relation should be

Trim for symmetry:

Each existing outgoing neighbor relation should be checked

Optimize connected mode priority:

When enabled connected mode NBR priority

Apply connected mode update to all NBRs:

When enabled connected mode ranking update

Operate on active target sectors:

When enabled only active target sectors

Operate on in-active target sectors for

When enabled only in-active target sectors

Operate on in-active target sectors for ADD:

When enabled only in-active target sectors will be

Exclude sectors overlapping polygons:

When enabled, sectors in overlapping

Maximum overall # NBRs (Intra, Inter &

Maximum GEO impact distance

When set to 10000, only GEO candidates