ZTE LTE FDD X2 Self-Configuration Feature Guide

ZTE LTE FDD X2
Self-Configuration Feature
Guide
ZTE LTE FDD X2 Self-Configuration Feature Guide

Version Date Author Reviewer Notes
Update to V3.3.20.20
V1.0 2016-03-30 He Ke Liu Yue Update the function description
Update the configuration
Update to V3.3.20.50
V1.1 2016-09-28 Yin Peng Liu Yue Modify some technical points in Chapter 3
Delete related counters in Chapter 4.2
2016 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential & Proprietary 1

TABLE OF CONTENTS
1 Introduction ....................................................................................................... 6
1.1 Feature Attribute .................................................................................................. 6
1.2 Related Feature List and License Control ............................................................ 7
1.3 Correlation with Other Feature ............................................................................. 7
2 Function Description......................................................................................... 8
3 Technical Descriptions ..................................................................................... 9

3.1 Basic Principle ..................................................................................................... 9
3.1.1 X2 Preference Principle ..................................................................................... 10
3.1.2 X2 Self-Learning ................................................................................................ 11
3.1.3 X2 Black/White List Management ...................................................................... 12
3.1.4 IP Address Update ............................................................................................. 13
3.2 Procedures ........................................................................................................ 13
3.2.1 X2 Self-Setup..................................................................................................... 13
3.2.2 X2 Self-Deletion ................................................................................................. 16
3.2.3 IP Update ........................................................................................................... 17
4 Engineering Guide .......................................................................................... 19

4.1 Related parameters ........................................................................................... 19
4.2 Related Counters, KPI and Alarms .................................................................... 27
4.3 Application Scenarios ........................................................................................ 27
4.3.1 Hardware Requirements .................................................................................... 27
4.3.2 EPC Requirements ............................................................................................ 27
4.3.3 Frequency Band, Frequency and Bandwidth Requirements of Frequency Carrier
28
4.3.4 UE Requirement ................................................................................................ 28
4.3.5 Transmission Bandwidth Requirements ............................................................. 28
4.4 Parameter Configuration Procedure ................................................................... 28
4.4.1 Enabling the Feature.......................................................................................... 28
4.4.2 Data Synchronization ......................................................................................... 38
4.4.3 Deactivate feature .............................................................................................. 39
5 Feature Validation ........................................................................................... 39

5.1 X2 Self-Setup Based on a New Neighbor Relation............................................. 39
5.1.1 Topology ............................................................................................................ 39
5.1.2 Test Specification............................................................................................... 40
5.1.3 Test Result......................................................................................................... 41
5.2 X2 Self-Setup Based on Statistics...................................................................... 41

5.2.1 Topology ............................................................................................................ 41

5.2.3 Test Result......................................................................................................... 44
5.3 X2 Self-Deletion Based on Neighbor Relation .................................................... 44
5.3.1 Topology ............................................................................................................ 44
5.3.3 Test Result......................................................................................................... 46
5.4 X2 Self-Deletion Based on Statistics .................................................................. 46
5.4.1 Topology ............................................................................................................ 46
5.4.3 Test Result......................................................................................................... 48
6 Impact on the Network .................................................................................... 49
7 Abbreviations .................................................................................................. 49

FIGURES
Figure 3-1 X2 Self-Setup Procedure ..................................................................................14

Figure 3-2 X2 Self-Deletion Procedure...............................................................................16
Figure 3-3 X2 re-setup .......................................................................................................18
Figure 4-1 Open the X2 Control Switch ..............................................................................29
Figure 4-2 Set the X2 control switch policy ........................................................................29
Figure 4-3 Distributed X2 control switch successfully .........................................................30
Figure 4-4 Open the X2 Function Switch............................................................................31
Figure 4-5 Set the X2 function policy .................................................................................32
Figure 4-6 X2 Policy Configuration Success ......................................................................32
Figure 4-7 Open the LTE FDD parameters ........................................................................33
Figure 4-8 Open the X2 black/white list parameters ...........................................................34
Figure 4-9 Open the X2 black list parameters ....................................................................34
Figure 4-10 the X2 black/white list parameters...................................................................35
Figure 4-11 Modify the maximum base shift time length for X2 self setup function in first
deploy case ..........................................................................................................................36
Figure 4-12 the global switch parameters windows ............................................................37
Figure 4-13 Modify the switch of x2 self-setup TNL interactive control parameters ............37
Figure 4-14 X2 SCTP Range .............................................................................................38
Figure 5-1 Topology for One Single eNodeB .....................................................................39
Figure 5-2 X2 Self-Setup is Successful by Adding a New Neighbor Relation .....................41
Figure 5-3 X2 Self-Setup test based on statistics ...............................................................42
Figure 5-4 X2 Self-Setup is triggered by statistics ..............................................................44
Figure 5-5 The X2 Self-Deletion Procedure Triggered by Neighbor Relation .....................46
Figure 5-6 The X2 Self-Deletion Procedure Triggered by Statistics....................................49

TABLES
Table 1-1 Related Feature List and License Control ........................................................... 7

Table 1-2 Correlation with Other Feature ............................................................................ 7
Table 4-1 Common Configuration ......................................................................................19
Table 4-2 X2 Self-Setup Parameter ...................................................................................23
Table 4-3 X2 Self-Deletion Parameter ...............................................................................23
Table 4-4 Other Parameters ..............................................................................................24
Table 4-5 Related Alarms ..................................................................................................27
Table 5-1 Test Equipment ..................................................................................................39
Table 5-2 X2 Self-Setup Based on a New Neighbor Relation.............................................40
Table 5-3 Test Equipment ..................................................................................................42
Table 5-4 X2 Self-Setup Based on Statistics ......................................................................42
Table 5-5 X2 Self-Deletion Based on Neighbor Relation ....................................................44
Table 5-6 X2 Self-Deletion Based on Statistics ..................................................................46

1 Introduction
This document provides the introduction, technical descriptions, parameter configuration,
counters, alarms, and validation procedure of the LTE FDD X2 Self-Configuration
feature.
The parameters, alarms and counters in this document are the same as those of the
latest software version when this document is released. To obtain the MO, parameters,
alarms, and KPIs of the existing software version, please refer to the product manuals of
the existing software version.
This document is applicable to LTE FDD mode. "LTE" and "eNodeB" mentioned in this
document respectively refer to "LTE FDD" and "LTE FDDbased eNodeB".
1.1 Feature Attribute
For FDD single-mode eNodeB V3.30.20.50 series:
EMS: V12.15. 30
OMMB: V12.15.30
For GUL multi-mode eNodeB V4.15.10.30 series:
EMS version: V12.15.30
OMMB version: V12.15.30
Note:
FDD single-mode V3.30.20.50 corresponds to GUL multi-mode V4.15.10.30, and LTE

technology description and operation requirements in the corresponding versions are the
same.
Involved NEs:
UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS
- - - - -
Note:

UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS

*-: Not involved
*: involved
1.2 Related Feature List and License Control
Table 1-1 Related Feature List and License Control
No Feature List No. Feature List Name License Control

or not
1 ZLF33-01-007 Transport Self-setup Yes
1.3 Correlation with Other Feature
Table 1-2 Correlation with Other Feature
Feature Feature Name Required Mutually Affected

ID Feature Exclusive Feature
Feature
ZLF31-00-004 None None

E-UTRAN
Interfaces
ZLF31-07-003
Intra-LTE
Intra
ZLF33-01-007 Transport Self-setup Frequency
HO
ZLF31-07-012
Intra-LTE
Inter
Frequency
HO
Note: Transport Self-setup includes S1, X2 and OAM self-setup.
Feature Name
ZLF33-01-007 Transport Self-setup

Required Features
ZLF31-00-004 E-UTRAN Interfaces
Without E-UTRAN Interfaces, Transport Self-setup cannot work.
ZLF31-07-003 Intra-LTE Intra Frequency HO
Without Intra-LTE Intra Frequency HO, the algorithm of X2 Self-Setup and X2

Self-Deletion cannot work properly.
ZLF31-07-012 Intra-LTE Inter Frequency HO
Without Intra-LTE Intra Frequency HO, the algorithm of X2 Self-Setup and X2

Self-Deletion cannot work properly.
Exclusive Features
None
Affected Features
None
2 Function Description
X2 self-Configuration functions include X2 self-setup and X2 self-deletion.
As an inter-site interaction channel, the X2 link provides the inter-site cell collaboration
function (for example, ICIC, LB, MRO, and MLB) and lays a foundation for inter-site
X2-based handover to shorten the time delay of handover. The basic principle of X2
self-configuration is to identify and set up available or high-priority X2 links but delete
unavailable or low-priority X2 links based on the statistical analysis of the neighbor cell
configuration and performance data of the current cell.
X2 self-setup is mainly based on neighbor cell information. The eNodeB obtain the IP
address of the transport layer of the peer eNodeB, in order to add a local X2 link. The
request process of IP address of the transport layer as follows:
The eNodeB sends the eNB CONFIGURATION TRANSFER message to the MME
for requesting the IP address of the corresponding eNodeB ID.
The MME forwards it by sending the MME CONFIGURATION TRANSFER

message to the target eNodeB.

The target eNodeB forwards the IP address of the corresponding SCTP connection
by sending the eNB CONFIGURATION TRANSFER message to the MME.
The MME sends the MME CONFIGURATION TRANSFER message to the source
eNodeB.
X2 self-setup is used in the following two scenarios:
1. If the number of X2 associations is in the low threshold status, X2 self-setup is

triggered when the neighbor relation changes.
2. If the number of X2 associations is in the high threshold status, X2 self-setup is

triggered based on statistics.
X2 self-deletion is used in the following four scenarios:
1. X2 self-deletion is triggered when the neighbor relation is deleted.
2. If the number of X2 associations is in the high threshold status, X2 self-deletion is

triggered based on statistics.
3. X2 self-deletion is triggered based on invalid association detection.
4. The repeated X2 association between two sites is deleted.
3 Technical Descriptions
3.1 Basic Principle
V3 version supports the maximum SCTP association number: 64 CC16, 128 CCE1. For
FDD, one SCTP link needs to be reserved for inter-RAT system. S1AP, X2AP and
reserved SCTP share SCTP associations.
The number of X2 SCTP associations supported by the system cannot meet the
operators requirements. To use X2 link resources more effectively, the system controls
X2 self-setup and self-deletion respectively to achieve X2 preference.

3.1.1 X2 Preference Principle
Two scenarios of X2 self-setup are considered as follows:
1. In the low threshold status, there are enough X2 association resources, an X2

association is set up immediately without considering the usage frequency of this
X2 association.
2. In the high threshold status, few X2 association resources are left free and much X2
associations require to be set up, so the use of high frequency associations will be
set up preferentially. The eNodeB starts collecting the number of S1 handover
success between this eNodeB and the opposite eNodeB for the X2 association to
be set up. When the statistics period expires, if the number of S1 handover success
is greater than the SonPolicyX2.sonS1HoSuccThrd(the threshold of S1 handover
times), the X2 association to be set up will be frequently used, and X2 self-setup is
triggered. If the number of S1 handover success is less than the
SonPolicyX2.sonS1HoSuccThrd(the threshold of S1 handover times), X2 self-setup
is not triggered.
Four scenarios of X2 self-deletion are considered as follows:
1. If no neighbor relation is kept between two eNodeBs, the X2 association will not be
used any more. To save resources, X2 self-deletion is triggered immediately.
2. In the high threshold status, few X2 association resources are left free. To ensure
the use of high frequency association with can be added successfully, the use of
low frequency association should be deleted. The eNodeB triggers X2 self-deletion
statistics about the number of X2 handover success on each X2 association. When
the statistics period expires, if the number of handovers on the association that has
the minimum number of X2 handover success is less than the
SonPolicyX2.sonX2HoSuccThrd(the threshold of X2 handover times), or the
number of X2 association has reach the maximum(When the baseband board is
CC16 the maximum is 46, When the baseband board is CCE1 the maximum is 126,
The maximum is fixed and cant be allocated), or the sum of the number of S1 and
X2 association has reach the maximum(When the baseband board is CC16 the
maximum is 47, When the baseband board is CCE1 the maximum is 127, The
maximum is fixed and cant be allocated), X2 self-deletion is triggered. If the number

of handovers on the association that has the minimum number of X2 handover

success is greater than the SonPolicyX2.sonX2HoSuccThrd(the threshold of X2
handover times), and the number of X2 association is less than the maximum(When
the baseband board is CC16 the maximum is 46, When the baseband board is
CCE1 the maximum is 126, The maximum is fixed and cant be allocated), X2
self-deletion is not triggered.
3. The eNodeB scans all the X2 associations periodically (every 5 minutes) to check
whether the X2 association status is abnormal. If the X2 association status is
abnormal, scan it every minute. If the X2 association status is still abnormal for
continuous 30 minutes, X2 self-deletion is triggered. If the X2 association status
becomes normal in 30 minutes, the scan statistics is cleared and X2 self-deletion is
not triggered. In normal status, the eNodeB scans the X2 associations every five
minutes.
4. The repeated X2 associations will be self-deleted. To ensure that there is only one
valid X2 link, the repeated X2 association will trigger self-deletion if one valid X2 link
has already existed.
5. If an X2 link is added into the X2 black list, and the X2 link exists, the eNodeB
triggers X2 self-deletion immediately.
3.1.2 X2 Self-Learning
In the X2 design solution, X2 self-setup and X2 self-deletion are based on the statistical
results in high threshold status. X2 self-setup needs to determine whether the number of
S1 handovers reaches the required threshold, and X2 self-deletion needs to determine
whether the number of X2 handovers reaches the required threshold.
The X2 self-learning function optimizes the X2 self-setup threshold and the X2

self-deletion threshold in accordance with the requirements for X2 self-setup and
self-deletion. The eNodeB counts the number of S1 handovers or the number of X2
handovers for the X2 statistics instance, and accordingly adjusts the setup and deletion
thresholds of the X2 statistics to make them more reasonable.
After the X2 self-setup period and X2 self-deletion period end, the X2 self-learning
function records the number of S1 handovers or the number of X2 handovers after each

X2 statistics instance expires. After the X2 self-learning statistics expires, the reasonable
X2 self-setup threshold and X2 self-deletion threshold are calculated based on the
statistical data. The execution of the X2 self-setup and self-deletion function provides the
source data for modifying the decision threshold for X2 self-learning, and X2 self-learning
provides the reasonable decision threshold for the X2 function.
The alternative X2 self-learning function is provided. If the X2 self-learning function (Self

Learn Switch) is disabled, the X2 association setup or deletion is determined in
accordance with the threshold configured in the corresponding policy. If an effective
threshold is optimized for X2 self-learning after the X2 self-learning function (X2 Self
Learn Switch) is enabled, X2 association setup or deletion is determined in accordance
with the optimized threshold. If there is no optimized effective threshold, X2 association
setup or deletion is determined in accordance with the configured threshold. The
threshold modification made by X2 self-learning is not shown on the OMC and in the
database, but you can determine the execution result through the function execution log.
In the existing network, the number of eNodeBs adjacent to an eNodeB is uncertain.

Some eNodeB has many neighbor eNodeBs, but some eNodeB has a few neighbor
eNodeBs. It is impossible to set reasonable X2 self-setup and self-deletion thresholds for
each eNodeB, because the surrounding environment varies with each eNodeB. This
leads to unreasonable X2 self-setup and self-deletion. The following two irrational
phenomena exist:
Under an eNodeB with a few users, a few handovers are triggered, but the
self-setup threshold is set too high, resulting in X2 links not being able to be set up
quickly.
Under an eNodeB with many users, many handovers are triggered, but the
self-setup and self-deletion thresholds are set too low, resulting in the X2 link with a
few handovers not being able to be deleted quickly.
To solve this problem, X2 self-learning is introduced.
3.1.3 X2 Black/White List Management
If a neighbor eNodeB that has an X2 association to the local eNodeB is added into the
ENBFunctionFDD.x2BlackList(X2 black list), the local eNB triggers X2 self-deletion

immediately. When the black list changes, the eNodeB triggers X2 association deletion
again according to the new black list.
Once an eNodeB is removed from the black list, its X2 association may be set up when
X2 self-setup is triggered.
If a neighbor eNodeB with an X2 link is in ENBFunctionFDD.x2WhiteList(X2 white list),

the X2 self-deletion function cannot delete the X2 link with the local eNodeB. .
3.1.4 IP Address Update
When the IP address of the peer eNodeB changes, the IP address of X2 SCTP
association of the source eNodeB will be updated automatically. When the IP address of
the peer eNodeB changes, the source eNodeB will detect abnormal link and initiates
transmission IP address request for IP address of the peer eNodeB. If the source
eNodeB detects that the IP address of the peer eNodeB is not consistent with the local
configuration, the source eNodeB will initiate the IP update.
3.2 Procedures
3.2.1 X2 Self-Setup
Figure 3-1 shows the X2 self-setup procedure.

Figure 3-1 X2 Self-Setup Procedure
OMC eNodeB1 MME eNodeB2
Trigger X2 self-setup
1a.R0/R1 break point interaction
2a.eNB CONFIGURATION TRANSFER
2b.MME CONFIGURATION TRANSFER
2c.eNB CONFIGURATION TRANSFER
2d. MME CONFIGURATION TRANSFER
3.X2 association addition request
2'a.eNB CONFIGURATION TRANSFER
2'b.MME CONFIGURATION TRANSFER

2'c.eNB CONFIGURATION TRANSFER
2'd.MME CONFIGURATION TRANSFER
3'.X2 association addition request
4.OMC add X2 association
4a.X2 association configuration synchronization
4b. X2 association configuration synachronization
4c.BR0 breakpoint interworking/monitor report

5.X2 SETUP REQUEST
5a.X2 SETUP RESPONSE
1. Open the SonPolicyX2.x2SelfupSwitch(X2 Self Setup Enable) When X2 self-setup

is enabled, the eNodeB starts a delay timer X2_SETUP_DELAY_TIMER. If the
timer expires, the X2 self-setup detection will be triggered. The eNodeB triggers X2
self-setup in the following scenarios:
i. Scenario A: The eNodeB1 identifies that there is no X2 association to the

eNodeB2 that the neighbor cell belong to, and the current number of X2 link is
less than SonPolicyX2.sonX2DelCheckThreshold (the threshold of X2
self-deletion), the eNodeB1 triggers X2 self-setup.
ii. Scenario B: The eNodeB1 identifies that there is no X2 association to the

eNodeB2 that the neighbor cell belong to, but the number of X2 link is greater

than or equal to SonPolicyX2.sonX2DelCheckThreshold (the threshold of X2

self-deletion), start X2_SETUP_S1HOSTAT_TIMER; if the timer expires, if the
collected number of S1 handover success is greater than or equal to
SonPolicyX2.sonS1HoSuccThrd(the threshold of S1 handover times), the
eNodeB1 triggers X2 self-setup.
In scenario A, the eNodeB1 and EMS perform R0 break point interaction.
In scenario B, the eNodeB1 and EMS perform R1 break point interaction.
2. After break point interaction, X2 self-setup goes on. The eNodeB1 obtains the
transmission address of the opposite eNodeB2 through messages 2a2d.
Meanwhile, the eNodeB2 needs to check the switch of X2 self-setup interactive
control. If disable, eNodeB2 does not process the messages.
3. The eNodeB1 sends an X2 association addition request to the EMS.
4. The EMS adds the X2 association, and synchronizes the data to the eNodeB1. The
EMS performs BR0 reference point interaction, and shows the operator the X2
association configuration result.
5. The local eNodeB1 and peer eNodeB2 perform the X2 SETUP procedure to set up
the X2 link.
After receiving X2 link setup success message, the eNodeB1 judges whether there has
ever existed valid X2 link between the eNodeB 1 and eNodeB 2. If there exists valid X2
link, OMC is informed to delete the latest established X2AP/SCTP to ensure there is only
one valid X2AP between two eNodeBs. If there is no valid X2 link, eNodeB 1 finishes X2
self-setup after waiting for 5 minutes, and indicates X2 link addition success.
If X2 link setup success message is not reported 3 hours later, X2 self-setup will be
finished and indicates X2 link addition failure.
Note: if the peer SCTP reaches the maximum configuration, the peer will not respond the
transmission address request.

3.2.2 X2 Self-Deletion
Figure 3-2 shows the X2 self-deletion procedure.
Figure 3-2 X2 Self-Deletion Procedure
OMC eNodeB1 eNodeB2
Trigger X2 self-deletion
1a.R2/R3/R4 break point interaction
2.X2 SCTP association

deletion request
3. deletes the X2 association
3a. synchronizes the data to

the eNodeB
3b. synchronizes the data to
the eNodeB
3c.BR0 reference point
interaction
1. Open the SonPolicyX2.x2SelfDelSwitch(X2 Self Delete Enable) When X2

self-deletion is enabled, the eNodeB starts a delay timer
X2_DELETE_DELAY_TIMER. If the timer expires, the X2 self-deletion detection will
be triggered.
The eNodeB triggers X2 self-deletion in the following scenarios:
a) When eNodeB1 judges that there is no neighboring cell relationship

between two eNodeBs, the eNodeB1 triggers X2 self-deletion
immediately.
b) If the number of X2 association is larger than or equal to

SonPolicyX2.sonX2DelCheckThreshold (the X2 self-deletion threshold),
start X2_DELETE_X2HOSTAT_TIMER. The X2 self-deletion statistics
period is started to collect the number of X2 handover success on each
X2 link. If the collected number of X2 handover success is less than
SonPolicyX2.sonX2HoSuccThrd(the threshold of X2 handover times), or
the current X2 association number or S1X2 association number reaches
the maximum, the eNodeB1 triggers X2 self-deletion.

c) When eNodeB is powered on, if X2 self-deletion switch is enable, X2

association detection is started after waiting for 3 hours. If X2
self-deletion switch is off, another 1 hour waiting is needed to re-judge
whether to perform detection. And on the premise of enable X2
self-deletion, for newly added X2 link, invalid association detection is
started one hour later, and eNodeB will detect X2 link every 5 minutes to
check whether X2 link is valid or not. If the X2 link is abnormal, the X2 link
will be detected every other minute. After continuous 30 X2 link
detections and all the results are invalid, the X2 link self-deletion will be
triggered. And then, after 5 minutes, X2 self-setup detection will be
started.
d) If an X2 link is added into the X2 black list, and the X2 link exists, the
eNodeB triggers X2 self-deletion immediately.
e) If there has already existed one valid X2 link, and when another X2 link is
added, the repeated X2 link will be deleted, and the former valid X2 link is
kept.
In scenario a) and d), the eNodeB reports to OMC to perform R2 break point interaction.
In scenario b), perform R3 break point interaction.
In scenario c), perform R4 break point interaction.
In scenario e), only deletion message is reported due to no break point interaction.
2. The eNodeB1 sends an X2 SCTP association deletion request to the OMC.
3. The OMC deletes the X2 association, and synchronizes the data to the eNodeB1
and eNodeB2. The OMC performs R31 reference point interaction, and shows the
operator the X2 association deletion result.
3.2.3 IP Update
The figure below shows the X2 re-setup procedure.

Figure 3-3 X2 re-setup
OMC eNodeB1 MME eNodeB2
X2 Link is broken
1.Delay
2a.eNB CONFIGURATION TRANSFER
2b.MME CONFIGURATION TRANSFER
2c.eNB CONFIGURATION TRANSFER
2d. MME CONFIGURATION TRANSFER
3a.R5 Reference point interaction
3b.Notify OMC To update X2 IP
4.Update X2 IP
4a.OMC synchronizes the X2 config
4b.R32 interaction, and displays the result
5.X2 SETUP REQUEST
5a.X2 SETUP RESPONSE
1. When X2 association re-setup is enabled, X2 association has been setup between

eNodeB1 and eNodeB2. Because eNodeB2 updates its local IP address, and X2
association between eNodeB1 and eNodeB2 break up. eNodeB detects the X2
association breaks, start X2 association re-setup timer;
2. If the timer expires, initiate the peer IP obtaining process. eNodeB1 obtains the peer
eNodeB transmission address via 2a-2d. If the X2 association recovers before the
timer expires, the process ends;
3. eNodeB judges whether the peer IP has changed or not. If the peer IP does not
change, the process ends; if the peer IP changes, then:
i. Executes X2 association update reference point interaction (Reference Point

R5)
ii. eNodeB1 reports the peer IP request message

4. OMC updates X2 SCTP association configuration
i. OMC synchronizes the newly added X2 SCTP association to the eNodeB1.
ii. OMC synchronizes the X2 association configuration to eNodeB1.
iii. OMC performs R32 reference point interaction, and displays the result.
iv. eNB1and eNB2 starts X2 Setup, and establish X2 link.
Note: X2 SETUP may be started by peer eNodeB.
4 Engineering Guide
4.1 Related parameters
Table 4-1 Common Configuration
Parameter Parameter Parameter Range Defaul

SN Unit
name panel name explanation value t value
SON Switch
SonControl.So Object ID; [1..999
1 Template ID N/A N/A
nControlId Generated by the 9]
System.
User-Friendly
SonControl.de Template
2 Description of N/A N/A N/A
scription Name
Object
Service
Type(21:PnP
26:SH 43:CS
SonControl.so [[0..25
3 Service Type 46:ANR 47:PCI N/A 26
nFuncId 5]
48:X2 49:MRO
50:CCO 51:RO
52:MLB 57:ES)
0:{Clos
SonControl.so Service This parameter is 0:{Clos
4 e},1:{O N/A
nSwitch Switch the service switch. e}
pen}


SN Unit
SON X2 Policy
SonPolicyX2.S Object ID; [1..999
5 Template ID N/A N/A
onPolicyX2Id Generated by the 9]
System
User-Friendly
SonPolicyX2.d Template
6 Description of N/A N/A N/A
escription Name
Object,
Service
Type(21:PnP
26:SH 43:CS
SonPolicyX2.s
7 Service Type 46:ANR 47:PCI [0..255 N/A 48
onFuncId
48:X2 49:MRO ]
50:CCO 51:RO
52:MLB 57:ES)
Indicate the policy

object executes
operation mode.
0:{Fre
Free Mode:
e
System 0:{Fre
SonPolicyX2.s Mode},
8 Run Mode automatically N/A e
onRunMode 1:{Con
without human Mode}
trolled
intervention
Mode}
Control Mode:
Allow human
intervention


SN Unit
The parameter
indicates the
policy is used for
macro-eNB and
macro-eNB SON
or macro-eNB and 0:
pico-ENB SON. {MAR
"MARCO and CO
0:
MARCO" indicates and
{MAR
Type of the policy is used MARC
SonPolicyX2.p CO
9 Service for SON function O}, N/A
olicyType and
Policy between 1:
MARC
Macro-eNB and {MAR
O}
Macro-eNB. CO
"MARCO and and
PICO" indicates PICO}
the policy is used
for SON function
between
Macro-eNB and
Pico-eNB.
It indicates the
policy report the
Bre
monitoring
Breakp akp
reference point.
oint oint
Whether a
SonPolicyX2.s timeou time
X2 Refer breakpoint,
10 onReferPointP t out 4320
Point Policy breakpoint timeout
olicy length: unit
length and
[1,432 s:
breakpoint timeout
0] min
policy, the setting
ute
only takes effect in
controlled mode.


SN Unit
When the number

of X2 is more than
the threshold
configured by the
OMC, the eNodeB
will start a statistic
X2
timer to count S1
Self-Setup/S
HO success times
SonPolicyX2.s elf-Delete [1..255 Hou
11 for adding X2 link, 24
tatisticTimer Statistic ] r
and to count X2
Timer Length
HO success times
(hr)
for deleting X2
link. This
parameter
indicates the
statistic timer
length, unit: hour.
This parameter
indicates whether
the X2 self-Learn
SonPolicyX2.x function is open or 0:{Clos
X2 Self Learn
12 2SelfLearnSw not. If the value is e},1:{O N/A 0
Switch
ch 'Open', the pen}
function is open;
otherwise, the
function is close.
This parameter
indicates the
number of SCTP
The Number
associations
of SCTP
SonPolicyX2.s reserved for S1.
13 Associations [1..16] N/A 16
1SctpNum These SCTP
Reserved for
associations can't
S1
be used for
X2.(Japanese
custom parameter)

Table 4-2 X2 Self-Setup Parameter

SN Unit
SonPolicyX2.x This parameter is 0:{Clos

X2 Self Setup
14 2SelfSetupSwi a switch for X2 self e},1:{O N/A 0
Enable
tch setup. pen}
The threshold of
S1 HO success.
When the number
of X2 interface is
more than specific
threshold(X2 Self
Delete Detection
Start Threshold)
and a new X2
SonPolicyX2.s S1 HO
interface is need to [0..655
15 onS1HoSuccT Success N/A 48
be added, It's 35]
hrd Threshold
necessary to count
the times of S1 HO
success. Only
when the times of
S1 HO success is
more than this
parameter, the
new X2 is allowed
to be added.
Table 4-3 X2 Self-Deletion Parameter

SN Unit
SonPolicyX2.x X2 Self This parameter is 0:{Clos

16 2SelfDelSwitc Delete a switch for X2 self e},1:{O N/A 0
h Enable -deletion. pen}

This parameter is
used to enable the
X2 Self
self deletion
SonPolicyX2.s Delete
detection
17 onX2DelChec Detection [1..63] N/A 20
algorithm when
kThreshold Start
the X2 self setup
Threshold
number up to the
threshold.
The threshold of
X2 HO success.
When the number
of X2 interface is
more than specific
threshold(X2 Self
Delete Detection
Start Threshold),
the eNodeB will
SonPolicyX2.s X2 HO start an X2
[0..655
18 onX2HoSuccT Success interface N/A 48
35]
hrd Threshold self-delete statistic
timer. After the
timer is timeout, if
the number of X2
HO success via an
X2 interface is less
than this
parameter, the
eNodeB will delete
the X2 interface.
Table 4-4 Other Parameters

SN Unit

This is a List of
DNs of
ENBFunction and
ExternalENBFunct
ion. If the Target
Node DN is a
Member of the
Source Node's
ENBFunction.x2Bl
ackList, the
Source Node Is:
1 Prohibited From
Sending X2
Connection
Request to Target
Node; 2 Forced to
ENBFunctionF
Tear Down
19 DD.x2BlackLis X2 Black List N/A N/A N/A
Established X2
t
Connection to
Target Node 3 not
Allowed to Accept
Incoming X2
Connection
Request From
Target Node.
The Same DN
May Appear Here
and in
ENBFunction.x2W
hiteList. In Such
Case, the DN in
x2WhiteList Shall
be Treated as If It
is Absent.

This is a List of
DNs of
ENBFunction and
Externalenbfunctio
n. If the Target
Node DN is a
Member of the
Source Node's
ENBFunction.X2W
hiteList, the
Source Node is: 1
Allowed to
Request the
Establishment of
ENBFunctionF
X2 Connection
20 DD.x2WhiteLis x2WhiteList N/A N/A N/A
With the Target
t
Node; 2 Not
Allowed to Initiate
the Tear Down of
Established X2
Connection to
Target Node. The
Same DN May
Appear Here and
in
ENBFunction.x2Bl
ackList. In such
case, the DN here
shall be Treated
as if it is absent.
The parameter
The indicates the
Maximum maximum base
Base Shift time length from
ENBFunctionF Time Length X2 policy
[0..255
21 DD.shiftNumb for X2 Self parameters are N/A 100
]
er Setup configured to
Function in used, when X2
First Deploy function is
Case (hr) deployed at first
time.

If the indication is
Open, The passive
The Switch of eNB processes
GlobleSwitchI X2 TNL request for X2
0:{Clos
nformation.x2 Self-Setup self-setup. If the
22 e},1:{O N/A 1
PassProcSwc TNL indication is Close,
pen}
h Interactive The passive eNB
Control doesn't process
TNL request for X2
self-setup
4.2 Related Counters, KPI and Alarms
Table 4-5 Related Alarms
SN Alarm Code Alarm Name
1 198094421 X2 link is broken
4.3 Application Scenarios
4.3.1 Hardware Requirements
No special requirements
4.3.2 EPC Requirements
X2 self-setup needs MME support.
Network elements must be in the same MME. In addition, if MME supports transport
self-setup of E - UTRAN Transparent Container, Inter-MME X2 self-setup needs to be
supported .

4.3.3 Frequency Band, Frequency and Bandwidth Requirements of

Frequency Carrier
4.3.4 UE Requirement
4.3.5 Transmission Bandwidth Requirements
4.4 Parameter Configuration Procedure
4.4.1 Enabling the Feature
To enable X2 self-configuration, open the switch of X2 control and X2 function at the

same time.
4.4.1.1 Configuration the X2 control policy
Objective
To open the X2 Self-Configuration Control Switch of SON function.
Process
1. On the EMS client, click Configuration>SON Management from the menu bar. The
SON Management window is displayed.
2. In the SON Management window, double-click SON Policy Management in the left
SON Management Tree. Double-click Managed Element>LTE FDD>FDD SON
Control, Click Create on the toolbar. The FDD SON Control dialog box is
displayed, Configure the parameters Service Type as X2 and Service Switch as
Open. Then click OK.

Figure 4-1 Open the X2 Control Switch
3. Choose the new switch record, and then click on the toolbar. Or click the right
on the record, and click Set. Set the eNodeB to which the X2 control switch is to be
distributed, and then click OK.
Figure 4-2 Set the X2 control switch policy

4. After the X2 control switch is successfully distributed to the eNodeBs, Succeed is

displayed in the Result column.
Figure 4-3 Distributed X2 control switch successfully
4.4.1.2 Configuration the X2 function policy
Objective
To open the X2 Self-Configuration Function Switch of SON function.
Include X2 Self-Setup and X2 Self-Deletion
Process
1. In the SON Management Tree, Double-click Management Element>LTE

FDD>FDD X2 Policy. Click Create on the toolbar. The FDD X2 Policy dialog box
is displayed. Configure the parameter of X2 Self-Setup and X2 Self-Deletion. Then
click OK.

Figure 4-4 Open the X2 Function Switch
2. Choose the new X2 policy, and then click on the toolbar. The Set dialog box is
displayed. Set the object type as LTE FDD and then select the eNodeB on which
the X2 policy is to take effect, then click OK.

Figure 4-5 Set the X2 function policy
3. After the X2 policy is successfully configured, Succeed is displayed in the Result

column.
Figure 4-6 X2 Policy Configuration Success

4.4.1.3 Configuring Other Parameters (Optional)
4.4.1.3.1 X2 Black/White List Management
1. Click Modify Area->Managed Element->Radio Parameter->LTE FDD, The LTE

FDD tab is displayed ,
Figure 4-7 Open the LTE FDD parameters
1. Choose the record and click the toolbar button, the LTE FDD parameters
is displayed.

Figure 4-8 Open the X2 black/white list parameters
2. In the configuration view,Midify the X2 black list or X2 white list According to actual
needs,and click button to modify the parameters.
Figure 4-9 Open the X2 black list parameters

2. click the OK button to save the parameter.
4. In the configuration view, click the button to modify the X2 white list
parameters,Operation steps are same to the X2 black list. Configuration

complete as shown below.
Figure 4-10 the X2 black/white list parameters
4.4.1.3.2 The Maximum Base Shift Time Length for X2 Self Setup Function in First Deploy
Case (hr)
1. Click Modify Area->Managed Element->Radio Parameter->LTE FDD, The

LTE FDD tab is displayed, Choose the record and click the toolbar button,
and Modify the The Maximum Base Shift Time Length for X2 Self Setup
Function in First Deploy Case (hr) parameter.

Figure 4-11 Modify the maximum base shift time length for X2 self setup function in first
deploy case
3. Click the save button to save the parameter modify.
4.4.1.3.3 The Switch of X2 Self-Setup TNL Interactive Control
1. Click Modify Area->Managed Element->Radio Parameter->LTE

FDD->E-UTRAN Service Configuration->Global Switch. Choose the record
and click the modify button, The Global Switch parameters tab is displayed.

Figure 4-12 the global switch parameters windows
2. In the configuration view, Set the The Switch of X2 Self-Setup TNL Interactive
Control parameter as Open or Close.
Figure 4-13 Modify the switch of x2 self-setup TNL interactive control parameters

3. Click the save button to save the parameter modify.
4.4.1.3.4 X2 SCTP Value Range
Purpose
According to the actual demands, configure the X2 SCTP object ID and SCTP NO value
range. Currently, CC16 supports 64 SCTP at maximum, 128 SCTP for CCE1 at
maximum.
Process
Click SON Management Tree->Global Parameters Management-> Optimization

Parameters Management. Click the modify button and the parameters tab is displayed.
Figure 4-14 X2 SCTP Range
4.4.2 Data Synchronization
Check the configuration and click Data Synchronization button.

4.4.3 Deactivate feature

1. To deactivate X2 configuration ordering, set X2 Control switch to close.
2. To deactivate X2 configuration ordering, set X2 Self Setup Enable switch and X2

Self Delete Enable switch to close (optional).
5 Feature Validation
5.1 X2 Self-Setup Based on a New Neighbor Relation
5.1.1 Topology
Topology is shown below.
Figure 5-1 Topology for One Single eNodeB
E-UTRAN Backhaul EPC Service Application
VoD VoIP Mobile TV
xPON
AAA DHCP DNS
Operator provides
FDD RRU services
MPLS
PSTN
Antenna
eNodeB PDH/SDH HSS

Terminal Firewall
FDD RRU
Enterprise
Metro Ethernet VPN
Antenna
eNodeB
Microwave
NetNumen M31
Internet
Test equipment is shown below.
Table 5-1 Test Equipment
SN Test Equipment Requirement

1 eNodeB 2
2 UE 1
3 MME 1
4 PGW 1
5 PDN server 1
6 PC 3.
5.1.2 Test Specification
Table 5-2 X2 Self-Setup Based on a New Neighbor Relation
Test Item X2 Self-Setup based on a new neighbor relation
Feature ID ZLF33-01-007
To verify the function X2 Self-Setup based on a new neighbor

Test Purpose
relation.
1. EUTRAN works normally;

2. EPC works normally;
Preparations 3. Application server runs normally;
4. OMC works normally;
5. ICM and OMMB are synchronized.
Test Step Expected Result
Established a cell1 on the Cell1 and cell2 are established

eNodeB1, and a cell2 on the successfully.
1
eNodeB2. Cell 1 and cell2 run in the Normal
status.
Configure the X2 service function
switch and X2 policy parameters.
Function Activation and set the
The X2 policy is allocation to
2 policy to eNodeB1. Make sure
eNodeB1 successfully.
the Service Switch is Open, Run
Mode is Free Mode, and X2 Self
Setup Enable is Open.
Configure cell2 as a neighbor cell X2 Self-Setup procedure is triggered
3 of cell1 and add a new neighbor after the configuration data was
relation between cell1 and cell2. synchronized.

Check the X2 Self-Setup result The X2 Self-Setup procedure is

4
on the EMS. successful.
Anticipative 1. The X2 Self-Setup procedure is successful by add a new
Result neighbor relation between two eNodeBs.
5.1.3 Test Result
The X2 Self-Setup is successful on the EMS by adding a new neighbor relation between
two eNodeBs.
Figure 5-2 X2 Self-Setup is Successful by Adding a New Neighbor Relation
5.2 X2 Self-Setup Based on Statistics
5.2.1 Topology
The topology for X2 Self-Setup test based on statistics is shown below.

Figure 5-3 X2 Self-Setup test based on statistics
E-UTRAN Backhaul EPC Service Application
FDD RRU
VoD VoIP Mobile TV
Antenna
eNodeB
FDD RRU xPON
AAA DHCP DNS
Operator provides
services
Antenna MPLS
eNodeB
PSTN
FDD RRU
eNodeB PDH/SDH HSS
Terminal Firewall
Antenna
Enterprise
FDD RRU
Metro Ethernet VPN
Microwave
eNodeB NetNumen M31

Internet
Antenna
Test equipment is shown below.
Table 5-3 Test Equipment
1 eNodeB Number:4
2 UE Number:1
3 MME Number:1
4 PGW Number:1
5 PDN server Number:1
6 PC Number:3
Table 5-4 X2 Self-Setup Based on Statistics
Test Item X2 Self-Setup based on statistics

To verify that X2 Self-Setup procedure is successfully triggered

Test Purpose by the number of S1 handover greater than the threshold of S1
handover.

Established a cell1 on the

Cell1, cell2, cell3 and cell4 are
eNodeB1, a cell2 on the
established successfully.
1 eNodeB2, a cell3 on the
Cell 1, cell2, cell3 and cell4 run in the
eNodeB3 and a cell4 on the
Normal status.
eNodeB4.
switch and X2 policy parameters
according to section 4.3.2
Function Activation and set the The X2 policy is allocation to eNodeB1
2
policy to eNodeB1. Make sure successfully.
Setup Enable is Open.
Add neighbor relation for cell1
without cell2 on the eNodeB2, X2 Self-Setup procedure is triggered
3 and make sure the number of X2 after the configuration data was
associations is equal to the synchronized.
threshold of X2 self-deletion.
Configure cell2 as a neighbor cell
The configuration data was
4 of cell1 and add a new neighbor
synchronized successfully.
relation between cell1 and cell2.
Initiate handover procedure
X2 Self-Setup between eNodeB1 and
between cell1 and cell2, and
eNodeB2 is successful after X2
5 make sure that the number of
Self-Setup/Self-Delete Statistic Timer
handover is greater than S1 HO
Length.
Success Threshold.
The X2 Self-Setup procedure is successful after X2
Anticipative Self-Setup/Self-Delete Statistic Timer Length, because the
Result number of S1 handover is greater than the threshold of S1
handover.

5.2.3 Test Result
The X2 Self-Setup is successful on the EMS after X2 Self-Setup/Self-Delete Statistic

Timer Length, because the number of S1 handover is greater than the threshold of S1
handover.
Figure 5-4 X2 Self-Setup is triggered by statistics
5.3 X2 Self-Deletion Based on Neighbor Relation
5.3.1 Topology
See Section 5.1.1.
Table 5-5 X2 Self-Deletion Based on Neighbor Relation
Test Item X2 Self- Deletion based on neighbor relation

To verify the function X2 Self-Deletion triggered by no neighbor

Test Purpose
relation between two eNodeBs.

Established a cell1 on the Cell1 and cell2 are established

eNodeB1, and a cell2 on the successfully.
1
eNodeB2. Cell 1 and cell2 run in the Normal
status.
Configure cell1 and cell2 as

neighbor cell and configure X2 X2 association between eNodeB1 and
2
association between eNodeB1 eNodeB2 is in normal status.
and eNodeB2.

3
Delete Enable is Open.
X2 Self-Deletion procedure is triggered.

Delete the neighbor relation
Both eNodeB1 and eNodeB2 report X2
between cell1 and cell2 on EMS
4 deletion message, and the X2
and release the mutex right of
association between eNodeB1 and
eNodeB1 and eNodeB2.
eNodeB2 is deleted.
Check the X2 Self-Deletion result The X2 Self-Deletion procedure is

5
on the EMS. successful.
Anticipative 1. The X2 Self-Deletion procedure is successful because
Result there is no neighbor relation between two eNodeBs.

5.3.3 Test Result
The X2 Self-Deletion procedure is successful because there is no neighbor relation

between two eNodeB.
Figure 5-5 The X2 Self-Deletion Procedure Triggered by Neighbor Relation
5.4 X2 Self-Deletion Based on Statistics
5.4.1 Topology
Refer to Section 5.1.1.
Table 5-6 X2 Self-Deletion Based on Statistics
Test Item X2 Self-Deletion based on statistics

To verify that X2 Self-Deletion procedure is successfully triggered

Test Purpose by the number of X2 handover lower than the threshold of X2
handover.

Established a cell1 on the

Cell1, cell2, cell3 and cell4 are
eNodeB1, a cell2 on the
established successfully.
1 eNodeB2, a cell3 on the
Cell 1, cell2, cell3 and cell4 run in the
eNodeB3 and a cell4 on the
Normal status.
eNodeB4.

2
Delete Enable is Open.
Add neighbor relation for cell1

without cell2 on the eNodeB2, X2 Self-Setup procedure is triggered
3 and make sure the number of X2 after the configuration data was
associations is equal to the synchronized.
threshold of X2 self-deletion.
Configure cell2 as a neighbor cell

The configuration data was
4 of cell1 and add a new neighbor
synchronized successfully.
relation between cell1 and cell2.
Initiate handover procedure

X2 Self-Setup between eNodeB1 and
between cell1 and cell2, and
eNodeB2 is successful after X2
5 make sure that the number of
handover is greater than S1 HO
Length.
Success Threshold.
Initiate handover procedure X2 Self-Deletion procedure is triggered

6
between cell1 with other cells because the number of X2 association

Test Item X2 Self-Deletion based on statistics
To verify that X2 Self-Deletion procedure is successfully triggered

Test Purpose by the number of X2 handover lower than the threshold of X2
handover.

except cell2. is greater than the X2 self-deletion

threshold.
The X2 association between eNodeB1
and eNodeB2 is deleted after X2
Length by X2 Self-Deletion procedure
because the number of X2 handover is
the least.
The X2 Self-Deletion procedure is successful after X2

Anticipative
Self-Setup/Self-Delete Statistic Timer Length, because
Result
association is greater than the X2 self-deletion threshold.
5.4.3 Test Result
The X2 Self-Deletion procedure is successful after X2 Self-Setup/Self-Delete Statistic

Timer Length, because association is greater than the X2 self-deletion threshold. See

Figure 5-6 The X2 Self-Deletion Procedure Triggered by Statistics
6 Impact on the Network

Advantages of this feature:
This feature achieves direct connections between network elements and provides X2
handover. At the same time, it can fast update the configuration information of neighbor
cells.
Disadvantages of this feature:
None
7 Abbreviations
For the acronyms and abbreviations, see LTE Glossary.

ZTE LTE FDD X2 Self-Configuration Feature Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ZTE LTE FDD X2 Self-Configuration Feature Guide

Încărcat de

Drepturi de autor:

Formate disponibile

ZTE LTE FDD X2

ZTE LTE FDD X2 Self-Configuration Feature Guide

2016 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

3 Technical Descriptions ..................................................................................... 9

4 Engineering Guide .......................................................................................... 19

5 Feature Validation ........................................................................................... 39

ZTE Confidential & Proprietary 2

5.2.1 Topology ............................................................................................................ 41

6 Impact on the Network .................................................................................... 49

ZTE Confidential & Proprietary 3

Figure 3-1 X2 Self-Setup Procedure ..................................................................................14

ZTE Confidential & Proprietary 4

Table 1-1 Related Feature List and License Control ........................................................... 7

ZTE Confidential & Proprietary 5

1.1 Feature Attribute

For FDD single-mode eNodeB V3.30.20.50 series:

For GUL multi-mode eNodeB V4.15.10.30 series:

EMS version: V12.15.30

OMMB version: V12.15.30

FDD single-mode V3.30.20.50 corresponds to GUL multi-mode V4.15.10.30, and LTE

ZTE Confidential & Proprietary 6

UE eNodeB MME S-GW BSC/RNC SGSN P-GW HSS

1.2 Related Feature List and License Control

Table 1-1 Related Feature List and License Control

No Feature List No. Feature List Name License Control

1 ZLF33-01-007 Transport Self-setup Yes

1.3 Correlation with Other Feature

Table 1-2 Correlation with Other Feature

Feature Feature Name Required Mutually Affected

ZLF31-00-004 None None

Note: Transport Self-setup includes S1, X2 and OAM self-setup.

ZLF33-01-007 Transport Self-setup

ZTE Confidential & Proprietary 7

ZLF31-00-004 E-UTRAN Interfaces

Without E-UTRAN Interfaces, Transport Self-setup cannot work.

ZLF31-07-003 Intra-LTE Intra Frequency HO

Without Intra-LTE Intra Frequency HO, the algorithm of X2 Self-Setup and X2

ZLF31-07-012 Intra-LTE Inter Frequency HO

Without Intra-LTE Intra Frequency HO, the algorithm of X2 Self-Setup and X2

The MME forwards it by sending the MME CONFIGURATION TRANSFER

ZTE Confidential & Proprietary 8

X2 self-setup is used in the following two scenarios:

1. If the number of X2 associations is in the low threshold status, X2 self-setup is

2. If the number of X2 associations is in the high threshold status, X2 self-setup is

X2 self-deletion is used in the following four scenarios:

1. X2 self-deletion is triggered when the neighbor relation is deleted.

2. If the number of X2 associations is in the high threshold status, X2 self-deletion is

3. X2 self-deletion is triggered based on invalid association detection.

4. The repeated X2 association between two sites is deleted.

3.1 Basic Principle

ZTE Confidential & Proprietary 9

3.1.1 X2 Preference Principle

Two scenarios of X2 self-setup are considered as follows:

1. In the low threshold status, there are enough X2 association resources, an X2

Four scenarios of X2 self-deletion are considered as follows:

ZTE Confidential & Proprietary 10

of handovers on the association that has the minimum number of X2 handover

The X2 self-learning function optimizes the X2 self-setup threshold and the X2

ZTE Confidential & Proprietary 11

The alternative X2 self-learning function is provided. If the X2 self-learning function (Self

In the existing network, the number of eNodeBs adjacent to an eNodeB is uncertain.

To solve this problem, X2 self-learning is introduced.

3.1.3 X2 Black/White List Management