POS-Payload Improvement

in V project after swap HW eNodeB the

payload a little degrade, the payload means the
incoming of operater,its very important KPI,
need to improve ASAP. from average 66000Gb
degrade to 65000Gb,about 1.5% degrade.
Networking Environment

Problem Cause Analysis

The mainly ways to improve Payload is to
analyze the users numbers site alarms radio
conditions transmission bandwidth/quality and
interworking strategy.

1.users analyze

get the user number form VLR, after swap the

user number decreas from 2nd May for all
province, and we get the info that another
operator has some sale promotions,that lead to
the deacrease of users,need our oprators to
have some actions to aviod the deacreas of
users

2.alarm clearance

check the alarm and push ran team to clear

the alarms which can impact the payload

Alarm
Quantity
name

Insufficie
nt
Ethernet
bandwidt
h 32
Link
down 11

Optical
port
receiving
link
failure 2
 Optical
interface
reception
link
degrade
d 1

S1 The
SCTP
associati
on is
broken 2
RRU link
broken 3
license 1
VSWR 1

3.RF optimization

after swap and Consolidation some site has

been changed the location lead to poor
coverage overshooting overlapping,it make
some area poor PSRP or poor SINR,also can
decrease the payload,

we made RF optimaztions base on the netmax

and test log analyze,

RSRP improvement

SINR improvement

Throughput improvement

4.transmission analyze

check the packet loss of all eNodeB and find 41

sites has high packet loss，push the
transmission teams to troubleshooting
 packet
OMMB loss
site
Mangal
22
ore
Hospet 4
Belgau
3
m
Bellary 3
Gadag 2
Hassan 3
Bidar 4

5.power optimization

based on TA and PRB usage，select the low

load site to modifythe PA PB and RS to to
improve the eage coverage to let more user
camping on LTE

parame suggest
ters exist ion
paForDT
CH 0 1
cpSpeRef
SigPwr 0 1
pb 18.2 21.2

6.modify the schedule method

select some non VIP sites which also has low

payload modify the schedule method for PF to
Max C/I

before after
alpha 1 1
beta 1 0
pFWeig
1 1
ht

7.modify the interworking strategy

 check the PS redirection and reselection
parameters modify to the suggested value to
force user camp on 4G easyer

functio parame Quantit suggest

n ters y existing ion
A2 267 -125
A2 284 -120 -125
B2
rsrpSrv
Trd 221 -110
B2
rsrpSrv
Trd 186 -114
PS B2
redirectio rsrpSrv
n Trd 144 -118 -120

B2
rscpSys
NbrTrd 335 -100

B2
rscpSys
NbrTrd 216 -105 -100
selQrxL
evMin 1539 -124
selQrxL
evMin 97 -120
selQrxL
evMin 12 -128 -124
snonint
rasearc
h 3 14
snonint
rasearc
h 1498 4

IDEL snonint
rasearc
h 40 40
snonint
rasearc
h 132 50 4
threshS
vrLow 1498 2
threshS
vrLow 15 20
threshS
vrLow 132 6

2
 threshS
vrLow 3 8 2

Solution

after optimization and troubleshooting the

payload improved，from average 65000Gb to
71000Gb，about 9.23%improvement

Summary and Notes

HSDPA Drop optimization
The target value of the HSDPA call
drop rate of a project is 0.16%. After
continuous optimization, the current
value has reached 0.18%, and it
needs to reach the standard quickly.
Networking Environment

Problem Cause Analysis

The site load of this project is high,
and the transmission packet loss is
very serious. It is difficult to promote
capacity expansion and transmission
solutions in a short period of time. It
needs to be quickly improved through
parameter optimization.
Solution

1. HSDPA dropped calls can be

quickly increased by reducing the
numerator or increasing the
denominator, and at the same time
the site load is relatively high,
consider optimizing DRBC
parameters to quickly increase
HSDPA dropped calls. The current
DRBC conversion times DtoP,
DtoIdle, DtoF are all already 1, there
is no room for optimization;

2. Check the DRBC trigger timer,

there is still room for optimization, so
I decided to modify the DRBC trigger
timer and increase the denominator
to improve HSDPA dropped calls;

3. Considering that this operation

may affect the user experience, it is
necessary to modify this parameter
as small as possible. Select one
RNC with better HSDPA call drop to
improve the denominator, thereby
pulling the network's hsdpa call drop
indicator;
4. After the modification, HSDPA
dropped calls across the entire
network to meet the standard. The
RNCHsdpa Rab increased slightly by
0.03%, HSDPA drop increased
significantly by 0.04%, the number of
HSDPA dropped calls decreased
slightly, the denominator of HSDPA
dropped calls increased significantly,
PS traffic was basically stable, fast
return The number of times to LTE
has increased significantly;
LTE FDD Network Planning & Optimization System-Demo Cluster Area Optimization Report
The target value of the HSDPA call
drop rate of a project is 0.16%. After
continuous optimization, the current
value has reached 0.18%, and it
needs to reach the standard quickly.
Networking Environment

Problem Cause Analysis

The site load of this project is high,
and the transmission packet loss is
very serious. It is difficult to promote
capacity expansion and transmission
solutions in a short period of time. It
needs to be quickly improved through
parameter optimization.
Solution

1. HSDPA dropped calls can be

quickly increased by reducing the
numerator or increasing the
denominator, and at the same time
the site load is relatively high,
consider optimizing DRBC
parameters to quickly increase
HSDPA dropped calls. The current
DRBC conversion times DtoP,
DtoIdle, DtoF are all already 1, there
is no room for optimization;

2. Check the DRBC trigger timer,

there is still room for optimization, so
I decided to modify the DRBC trigger
timer and increase the denominator
to improve HSDPA dropped calls;

3. Considering that this operation

may affect the user experience, it is
necessary to modify this parameter
as small as possible. Select one
RNC with better HSDPA call drop to
improve the denominator, thereby
pulling the network's hsdpa call drop
indicator;
4. After the modification, HSDPA
dropped calls across the entire
network to meet the standard. The
RNCHsdpa Rab increased slightly by
0.03%, HSDPA drop increased
significantly by 0.04%, the number of
HSDPA dropped calls decreased
slightly, the denominator of HSDPA
dropped calls increased significantly,
PS traffic was basically stable, fast
return The number of times to LTE
has increased significantly;
a Optimization Report
LTE FDD Network Planning & Optimization System-access

One FDD-LTE network，from

5th June,there are many
complain form the region
about the signal,the customer
said that they don’t have any
signal but existing before.And
we found that the online
number of RRC connection
user reduced obviously from
the statistics of KPI.

Networking Environment

Problem Cause Analysis

The PCI and PRACH are not

the same NCS between phase
1 and phase 2,if we don’t keep
synchronization,there will be
much interference from each
other after more new sites on
air. But the operator gave us
little PCI and PRACH
resource,so we decide to
change the NCS of all the sites
to 6.the corresponding
coverage distance is
3.5KM.otherwise,some
existing user is out of
3.5KM,so they can’t access the
network after parameters
modification.
From the TA value statistics of
the whole network,the
proportion of the TA value
more than 51(3.8KM) was
6.57 before the parameters
modification.after the NCS
was change to 6,this part of
users couldn’t access.

Solution

Because the complain start

from 5th June,we check the
parameters modification
record on 4th June.we found
that the PCI and PRACH of the
whole network have been
modified.according to the
description of user,there
should be some parameters
affecting the coverage
distance change.between
those parameters,just NCS will
change the coverage distance
of eNodeB.in order to prove
that,we do a statistics of TA
value of the whole
network and compare them.

From the results,the coverage

distance is about 10218
meters(131*0.52us*3*100m/
us/2=10218) before
parameters modification.
 But the coverage distance is
about 3978
meters(51*0.52us*3*100m/u
s/2=3978) after parameters
modification.

Then we recover the

parameters on 8th June,the KPI
statistics is as below:

LTE FDD Network Planning & Optimization System-Analysis Report on RRC&Erab high dro
One serving LTE SDR
(eNodeBID=275) had significant
degradation on RRC and eRAB drop
rates on 5th and 6th June.

[FDD]R
Manag RC
Start Subnet
edElem Drop
Time work
ent Rate(p
ercent)
### 502 275 0.74%
### 502 275 0.30%
### 502 275 1.20%
### 502 275 0.44%

### 502 275 42.52%

### 502 275 18.22%

### 502 275 4.00%

### 502 275 0.45%
### 502 275 0.58%
### 502 275 4.76%
Networking Environment

Problem Cause Analysis

First analyzing the cell KPI, we found
that the high RRC drop rate
happened on the cell2 on 5th and 6th
June as the following table:

2.Analyzing hourly kpi data, we found

that abnormal period of 0605,0606
was from 19: 00 to 23: 00.

3.Confirmed with custom, we know

that there had one local festival on
these two days,and there had a lot of
users connecting to this cell on that
day. then we check the following
capacity parameters .

CFI parameter: reasonable

The maximum number of users

parameters: reasonable

PRACH parameter: reasonable

tUserInac parameters: reasonable

CQI capacity parameters: reasonable

CQI
capacity=(4*6/2)*10*(20/20)+(4*6/2)*
10*(80/20) = 600

SR capacity parameters

SR capacity=(10*18/12)*12=180 It
can be used for 180 users,so it’s not
enough for the festival.
Solution
We suggest to adjust the SR relation
parameters according to the following
table.

Modify
parame the
sheet
rs descript
ion
PhyCh pucchS
18->36
annel rNum
12;0;0;
PhyCh srTrCH 0-
annel Num >8;2;2;
0

After the parameters modified, SR

capacity=
(10*36/12)*8+(20*36/12)*2+(40*36/1
2)*2=600

After modifying these parameters, we

monitor the KPI again，the
RRC&Erab drop rate turn to normal.

Why RRC connection user reduces?

After modifying the SR parameters,

the RRC connection user count
decreased, the reason is the
following:
 The RRC Establishment Success Rate
counts while the eNodeB receives
response of the “RRC
Connection Setup”. Due to the lack of
SR resource, the user who has task
can’t be released。Because less
users are released after finishing
Scheduling task，the users become
more and more.

After modifying the SR parameters,

the SR resource is enough. The users
are scheduled in a reasonable time,
then the users that have been
Scheduled completely are released
by the “user-inactivate”. It means
that enough SR resources reduce the
RRC Re-connection numbers, then
lead to the RRC connection user turn
to real level.
Summary and Notes
The configuration of SR parameters
is not reasonable during the high
traffic, and it results that the SR
resource is not enough, then leads to
the high drop rate.Solution: Adjusting
the SR parameters according to the actual
users. Specially festival day, the users
increase so many.

LTE FDD Network Planning & Optimization System-Analysis of Access Failure Caused by a
A newly commissioned indoor site KSH (one cell)
could not access the network normally. The air-
interface data on the TEMS showed that after the
UE sent an RRC Connection Setup
Complete message and an Attach
Request message, the eNodeB and the CN did not
send any relevant message, so the RRC
connection was released and the cause was
“other.” The messages traced on the air interface
were as shown in the following figure.

Networking Environment

Problem Cause Analysis

After the UE received the RRC Connection
Setup Complete message, the access failed.
Usually this was because an SCTP
parameter between the base station and the
CN was wrongly configured. The engineer
should check the SCTP parameter
configuration.

Solution

Later the engineer checked the SCTP parameters

and found a parameter was wrongly configured.
After it was corrected, the traced messages were
as shown in the following figure.
n RRC&Erab high drop rate
s Failure Caused by a Wrong SCTP Parameter Configuration
LTE-FDD LTE Inter-Freq/IRAT Optimization Summary
The customer requires that the
data service on LTE
should be account for 85%. But
only 70% before optimization.
Networking Environment

Problem Cause Analysis

We analysis the issue be the
following steps:

1) This function analyzes the

inter-frequency parameters in the
LTE system to ensure that UE can
stay on the carrier frequency with
a higher bandwidth and improve
user experience.
2) This feature analyzes the inter-
operability parameters between
LTE and UMTS networks to
ensure that UE can stay in the
LTE network without affecting
KPIs.
3) The priority configuration
between inter-frequency and
inter-system still uses the
configuration:
LTE2.6>LTE1.8>UMTS. The inter-
operability with GSM is not
configured in the field.
Optimize the parameters in IDLE
and ATIVE states.

Comparison of parameters before

and after optimization in IDLE
state:

Comparison of parameters in
ACTIVE status:

Solution

[Optimization result]:
 [Optimization result]:

Summary and Notes

[Conclusion]:

1) An inter-frequency and inter-

system priority configuration is
required for the inter-operability
policy. The inter-operability
parameters are configured based
on the priority configuration.
3) To adjust interoperability
parameters, you need to make
more attempts. For example, if
the parameter is set too early, the
ping-pong effect will be caused,
which greatly reduces user
experience. If the parameter is
set too late, the KPIs will fluctuate
greatly, especially the LTE call
drop rate.
3) Too many inter-frequency and
inter-RAT measurements are
avoided for UEs. Because UEs
cannot use services during
measurement, too many inter-
frequency and inter-RAT
measurements reduce the number
of times that UEs are scheduled
and affect user experience.
4) In addition, the UMTS should
return to the LTE network as soon
as possible after the user
performs UMTS services such as
voice service, for example, fast
return to LTE Function.

Interoperability optimization to increase DL Throughput

Congo-Brazzaville’s current network has newly expanded 300
L800M cells. Due to load unbalance and bandwidth issues, the
overall DL Throughput is lower than expected. The user
experience is mainly improved through optimization between
different frequency bands.

After 100 LTE 800 sites were opened, the rate was 7.9M, which
was not up to the 11M expected by customers. So plans to
optimize the LTE800 rate.
The network speed and traffic volume are as follows

problem analysis
1) 256QAM function is not activated;
2) The flagSwiMode parameter setting is unreasonable;
3) The setting of the CA threshold is unreasonable, causing the
Feature to fail to activate;
4) QCI distribution impact, focusing on protecting high-priority
users and affecting low-priority users;
5) AMBR speed limit;
6) Interference / high cell load
7) The interoperability threshold setting in the system is
unreasonable, resulting in uneven load.
Solution
1) 256QAM verification

There are two parameters relation with 256QAM. Through

inspection, it is found that there are 100 newly opened L800
sites. There are 35 sites whose qamSwch is 0, 256Q is not
enabled, and the 256QAM has been enabled for 65 sites. The
256QAMCATLimitSwch parameter is set to 2. Parameter
adjustment: qamSwch=1, the256QAMCATLimitSwch=0.

Parameter
No. Parameter Name on the Meaning Value Range Default
GUI

256QAM is a
new high-
order
#@EUtranCell 256QAM modulation
1 FDD.qamSwc function mode newly 0:Close,1:Ope 0
h@# switch added in the n
protocol. By
default, the
parameter is
disabled.
 When the
switch is set
to 0, the UE is
considered to
support
256QAM only
when dl-
256qam-r12
meets the
requirement.
There is no
protocol
version or
CAT level
restriction.
When the 0:Unlimited
switch is set conditions{Cl
to 1, the UE is ose},
considered to
#@EUtranCell Cat capability
support
FDD.the256Q restriction
2
AMCATLimitS switch of 256QAM only
2
when both
wch@# 256QAM
the protocol
version and
CAT level
meet the
requirement
except the dl-
256qam-r12
field. When
the switch is
set to 2, the
CAT level
shall meet
the
requirement
except the dl-
256qam-r12
field. This UE
supports
256QAM.

1:Limit
Release
Version and
CAT

2:Limit CAT
Only

2) FlagSwiMode parameter check

Check the flagSwiMode parameter settings of 100 L800 sites. It is
found that there are 35 sites corresponding to 256QAM. Set this
parameter to Tm3 internal switching mode [3]. Then, adjust the
parameters of these 35 sites to Tm4 internal switching mode [6].

3) Improper CA threshold setting causes the Feature to fail to be

activated.
Check the CA activation and deactivation thresholds of 100 L800
sites. The settings are as follows:
Short Name Value
 pcellPRBRati
5
oActThrDl

scellPRBRati
95
oActThrDl

pcellPRBRati
oDeActThrD 4
l

scellPRBRati
oDeActThrD 5
l

4) QCI distribution affects high-priority users, and affects low-

priority users.
Check the distribution of QCIs in the entire network. The
distribution of QCIs is as follows:

According to the background KPI statistics, there are QCI=7/8/9

users in the network. Find the three sites with more QCI=7/8/9
users.
Map QCI=7/8/9 to the same EPLM (QCI=6)

5) AMBR limit

According to the background KPI statistics, on February 20, the

customer optimized and adjusted AMBR for about 1.5% users.
Less users with AMBR greater than 100 M accounted for
1.5%.AMBR[50100] user ratio increased by about 0.3%, while
AMBR[10 and 50] user ratio increased by about 1.2%. In this
case, we adjusted type B parameters.

ParameterDefault Memory
Recommended Value
ucAMBRNoLimitSwch0 1
 6) Interference/High cell load
According to the background indicator RSSI, the interference of
the whole network is checked. The RSSI of the newly
commissioned sites is within -95 ~ -100. There is no L800
interference in the network.
To query the cell load, query the DL PRB Utilization
Rate/Maximum RRC-Connected User Number. To optimize the
RF of the cells of DL PRB Utilization Rate>70% and Maximum
RRC-Connected User Number>60 in busy hours, adjust 22 cells in
total.

7) The intra-system interworking threshold is not properly set,

resulting in unbalanced load.
Sort out the interoperability parameters inside the LTE system in
the existing network.

L1800 ->
L1800

L800 ->
L800 L800 -> L2100

L2100
-> L2100

Intra-Freq
HO: Inter-Freq Close-Freq Inter-Freq
Short Name
A3, 3dB Measure: Measure: HO:
better
measCfgIdx 50(A3) 20020(A2) 20010(A1) 20908(A4)
measCfgFunc
4:Intra Frequency
1: Open
HOInter
Measure
0:
Frequent
Close Inter
Measure
5:
Frequent
Inter Frequency
Measure HO Measure
triggerQuantity 0: RSRP 0: RSRP 0: RSRP 0: RSRP
reportCriteria
0:Event Triggered
0:Event
Reporting
Triggered
0:Event
Reporting
Triggered
0:Event
Reporting
Triggered Reporting
eventId 2:A3 1: A2 0: A1 3:A4
thresholdOfRSRP -50 -85 -80 1.05263158
hysteresis 1.5 0 0 0
timeToTrigger 8: 320ms 8: 320ms 8: 320ms 8: 320ms
a3Offset 1.5 3 3 3
a5Threshold2OfRSRP

According to the frequency band-based rate statistics, from the

site commissioning of L800, the L1800 rate increases obviously
due to the sharing of L1800 traffic, but the L800 rate does not
increase obviously. The A5 thresholds of the four TACs and 120
sites in the existing network are modified so that more
subscribers stay at L1800, thus achieving traffic balance and
increasing the L800 rate.

Conclusion
Through this round of rate optimization and improvement, the
rate of L800 is increased from 7.9Mbps to 9.57Mbps. Considering
the growth of users and traffic in the existing network, the
customer is very satisfied with the clarification materials.

Through this round of optimization and adjustment, some

problems are also found in rate increase:
1. To access the network at a new site, it is necessary to check
the key parameters of Baseline, the commissioning of Feature
and the reasonableness of the threshold setting.
2. Investigate the network, including interference
troubleshooting, AMBR rate limit and QCI distribution.
3. To access the network from a large number of sites, you need
to re-configure the intra-system and inter-system interoperability
thresholds, and optimize key areas.
Load Balance by Optimizing the reselection and Handover Parameters

In Seatel network, there are two different

bandwidth spectrums:

850MHz, 5MHz bandwidth, entire

network site configuration, as a
continuous spectrum for
coverage.
2600MHz, 10MHz bandwidth,
individual site configuration, high
load as a hot spot.

But the individual high load site is not

very good use of advantages of 2600MHz
frequency, 850MHz PRB utilization is
much higher than that of 2600MHz, that
need to be optimized the uneven load site.

Solution
1 Load Balancing Strategy

Load balancing strategy has the

following ways. According to the
current Seatel LTE version
License, it has to choose the first
kind of strategy, by setting up
reasonable reselection and
handover parameters to achieve
load balancing.

2 The Existing Network Capacity

Analysis

2.1 Extraction of high

throughput sites

[LTE]Maximum of S1 Throughput
on Downlink(Mbps)>=60Mbps.

2.2 Extraction of high load cell

Condition：One week &900290: DL

PRB Utilization Rate
(Seatel)>=70% per 30 min &Count
>50
2.3 Select the optimization goal

Site 210 with 2 carriers was

selected as a pilot of the load
balancing optimization.

3 Reselection Parameters
Optimization

The goal is to make the user camp

in the 2600MHz cell as much as
possible.

3.1 Reselection Priority

850MHz reselection priority was

set to 6, 2600MHz reselection
priority to 7

3.2 Start Threshold for Inter-

frequency Reselection
Measurement

The redirection threshold from

850MHz to 2600MHz:

sNintraSrchPre=1,snonintrasearch/
r9SNintraSrchP =40dB, selQrxLevMin =-
120dBm, RSRP<(-120+40)=-80dBm

The redirection threshold from 2600MHz to

850MHz:

sNintraSrchPre=1,snonintrasearch/
r9SNintraSrchP =10dB, selQrxLevMin =-
120dBm, RSRP<(-120+10)=-110dBm

3.3 Decision Threshold for Inter-

frequency Reselection Measurement

The redirection threshold from 850MHz to

2600MHz (High Priority Reselection):
For neighbor cell,
ThrdXHigh=4，interQrxLevMin =-120, so
the threshold is -116dBm

The redirection threshold from 2600MHz

to 850MHz (Low Priority Reselection):

For serving
cell, threshSvrLow=4，selQrxLevMin =-
120, so the threshold is -116dBm

For neighbor
cell, ThrdXHigh=10，interQrxLevMin =-
120, so the threshold is -110dBm

4 Handover Parameters Optimization

The goal is to make users handover

from 850MHz cell to 2600MHz cell as soon
as possible.

4.1 Measurement Configuration

Group

Current Configuration:

Only 1 measurement configuration

group CellMeasGroup=1, shared
by 850MHz and 2600MHz

Optimized Configuration:

New added measurement

configuration
group CellMeasGroup=2 for
2600MHz cell, CellMeasGroup=1
for 850MHz

cell.

4.2 Measurement configuration

index

Current Configuration:
Measurement configuration index
10 and 20 of close and open inter-
frequency measurement, shared
by 850MHz

and 2600MHz.

Measurement configuration index

70 of inter-frequency handover
measurement, shared by 850MHz
and 2600MHz.

Optimized Configuration:

Measurement configuration index

10 and 20 of close and open inter-
frequency measurement for

850MHz.Measurement
configuration index 102 and 22 of
close and open inter-frequency
measurement, for

2600MHz.

New added measurement

configuration index 804 of inter-
frequency handover measurement
for 850MHz. New

added measurement configuration

index 80 of inter-frequency
handover measurement for
2600MHz.

4.3 Inter frequency handover

parameters optimization

Measurement configuration index

10 and 20 of close and open inter-
frequency measurement for
850MHz, the
thresholds are -70dBm and-
80dBm, which increase in order
early to handover to 2600MHz cell.

Measurement configuration index

102 and 22 of close and open
inter-frequency measurement for
2600MHz, the

thresholds are -100dBm and-

110dBm, which decrease in order
to keep in 2600MHz cell.

The A4 event threshold is -

116dBm of handover from 850MHz
and 2600MHz

The A5 event threshold 1 is -

116dBm and threshold 2 is -
110dBm of handover from
2600MHz and 850MHz. The

optimized specific parameter

Settings in the following table:

5 The optimization effect

The Optimization execution time:

2017/5/12 12:00:00

Cell 1 is 850MHz cell (Red), Cell 11

is 2600MHz cell (Blue), and they
have same project parameters.

Maximum Number of RRC

Connection User:
Users significantly increased in
2600MHz cell
PDSCH PRB Utilization Rate is
almost same in 850MHz and
2600MHz cell

DL Cell PDCP SDU Volume

increased in the 2600MHz cell.

After reselection and handover

parameter optimization, PRB
utilization increased in 2600MHz
cell, but dropped in 800MHz cell,
the 2600MHz cell attracted more
users and traffic, and achieve the
desired purpose.

6. Summary and Notes

If handover threshold was set

too low in the 2600MHz cell, the
weak signal easily caused
handover failure when outgoing,
it is need to monitor handover
KPI after optimization.

If 850MHz UE was too early to

measure the other frequency that
will affect the traffic in 850MHz
cell, and it is necessary to
monitor volume KPI in 850MHz
cell after optimization.

The measurement start and

decision thresholds must
synchronously modify and pay
attention to logically consistent,
to avoid ping-pong handover and
reselection.
Manually handover and
reselection parameters were
optimized to achieve Load
balance, that threshold is fixed,
be unable to do the flexible
dynamic adjustment according to
the different coverage. Suggest
guiding customers to buy
the Load Balance feature License
to implement Load balance
based on algorithm.
FDD-POS-FDD LTE Qos Optimization for QCI7 and QCI9
There are two types of QCI ERAB in Current LTE network : QCI7 and QCI9 , The ratio of
these two type ERAB as below:

The QCI7 user's perception is better than QCI9 user's perception.

Networking Environment

Problem Cause Analysis

1.The source of QCI7 ERAB
As current EPC configuration the LTE default bearer should be QCI9, So check the 3GPP protocol
we found the QCI7 ERAB setup when the user handover from 3G to LTE. Currently 3G Qos
is Interactive and Traffic Handling Priority 2

【3GPP TS 23.401】Mapping between standardized QCIs and Release 99 QoS parameter values:

Source
Traffic Signalli
Statistic
Traffic Handlin ng
QCI s
Class g Indicati
Descript
Priority on
or

Convers
1 N/A N/A Speech
ational

Unknow
Convers n
2 N/A N/A
ational (NOTE
1)
Unknow
Convers n
3 N/A N/A
ational (NOTE
2)
Unknow
Streami n
4 N/A N/A
ng (NOTE
3)
Interacti
5 1 Yes N/A
ve
Interacti
6 1 No N/A
ve
Interacti
7 2 No N/A
ve
Interacti
8 3 No N/A
ve
 Backgro
9 N/A N/A N/A
und

2.The influence of QCI7

As we know LTE have 9 types of QCI. Due to different priority and packet delay and loss rate, QCI7
ERAB will get the schedule priority and more radio resource, at the end will impact the QCI9 ERAB
users. Especially currently users and traffic have huge growth (Table 1.3.2)

Table1.3.1: QCI classification

Packet
Packet
Resource Error Example
QCI Priority Delay
Type Loss Services
Budget
Rate
Convers
1 2 100ms 10−2 ational
Voice

Convers
ational
Video
2 4 150ms 10−3
(Live
Streami
ng)

Real
Time
Gaming,
3 3 50ms 10−3
GBR V2X
message
s

Non-
Convers
ational
Video
4 5 300ms 10−6
(Buffere
d
Streami
ng)

5 1 100ms 10−6 IMS Signalling

 Video
(Buffere
d
Streami
ng)
TCP-
Based
6 6 300ms 10−6 (for
example
, www,
email,
chat,
ftp, p2p
and the
like)

Voice,
Video
(Live
Streami
7 7 100ms 10−3
ng),
Interacti
ve
Gaming

Video
(Buffere
d
Streami
Non- ng)
GBR TCP-
Based
8 8 300ms 10−6 (for
example
, www,
email,
chat,
ftp, p2p
and the
like)
 Video
(Buffere
d
Streami
ng)
TCP-
Based
(for
example
, www,
9 9 300ms 10−6
email,
chat,
ftp, p2p
and the
like).
Typicall
y used
as
default
bearer

Table1.3.2：User and RRC Users huge growth.

Solution
1.Optimization solution

(1)Put the QCI7 and QCI9 in the same EMLP to make the QCI7 priority the same as QCI9

(2)Open QCI weight and set the QCI factor 1:1 to make QCI7 and QCI9 radio resource occupy in same
priority

2.Related parameters

3.Verification

Take high user cells XXX004L-5 for example,(Remark：XXX004L-5 connect to indoor system,
the antenna of the indoor system is 1x1 MIMO, and it is B1 15MHz cell)

We did the FTP CQT download test at the same location and try our best to finish the test in 15
minutes, then we found the throughput have gain

First Time:
 Avg.RSR Avg.SIN
P R Avg.DL QCI9 QCI7
XXX004 RRC user
Throughp ERAB ERAB Time
L-5 number
ut(Mbps) number number
(dBm) (dB)
Before
Qos 10/8/2018
-69.858 23.454 12.773
modificati
on
100 10 102
After Qos
modificati -71.232 24.109 18.141 14:45-15:00
on

Second Time:

Avg.RSR Avg.SIN
P R Avg.DL QCI9 QCI7
XXX004 RRC user
Throughp ERAB ERAB Time
L-5 number
ut(Mbps) number number
(dBm) (dB)
Before
Qos 10/8/2018
-69.962 23.892 38.625
modificati
on
51 7 51
After Qos
modificati -68.096 24.182 39.306 15:15-15:30
on

For KPI :

Summary and Notes

When the network have different QCI user ,shoud be check every months, to avoid the impact
from high priority QCI user.
Planning & Optimization Solution for TDD-LTE-How to turn RIM function
RIM（RAN information manager）R9 is a
characteristic feature of , 3G side can obtain the
configuration of the LTE network in advance, then
released when the 3G LTE -side configuration
distributed UE, UE avoid searching , decoding
overhead message 3G thereby shorten CSFB fall
delay . By assessing the existing commercial
network , the calling side reduced by an average
delay of about 1s. This article covers only the
UMTS LTE drop process.

Networking Environment

Problem Cause Analysis

1、Parameter modification

Enabling RIM feature requires eNodeB, MME and

3G wireless side modify the parameters ,
parameters and modify specific methods involved
are as follows .

Recomme
The main system
Parameter Defaults nded
parameter parameter
s path values configurat
s involved s
ions

Wireless
Service
UTRAN
Configura
RIM
tion - > Close Open Open
process
Mobility
switch
Managem
ent

The parameters in the network optimization

template name and explain :

switchUtr
anRim

UTRAN
RIM proc
ess switch
long:0:clo
se,1:open;
default:0

UTRAN
RIM proc
ess switch

R-W-I
1

Meanwhile , RIM feature requires configuration

data in UMTS LTE side neighborhood , the general
neighborhood amount not more than 16 , due to the
presence V3.10.20.30P53 BUG, more than 11 when
the eNodeB release message will not be sent , it is
recommended to configure 10 neighborhood .

2、Core network side

MME section :

SGSN section :

3、RNC side

In URncFunction table, you need to open UTRA SI

function switch .

Solution

Effect and takes effect confirmed

The following is based on the test data ,
Zhengzhou , randomly selected twice CSFB process
, the first based on R9 (RIM hit ) to redirect the
flow , and the second based on the R8 's ordinary
redirection process (RIM misses ) , the first drop
delay (LTE RRCConnectionRelease->
RRCConnectionSetup) for 389ms, while the second
drop latency (LTE RRCConnectionRelease->
RRCConnectionSetup) is 774ms. Therefore , with
respect to the success of the first RIM RIM
unsuccessful second save 385ms, the effect is
significant .

RIM Success:

Second call : RIM hit failure , take regular R8

processes.
Optimization System-ZTE_SON Feature Implementation Plan and Details

Problem Cause Analysis

MobilityRobust Optimization Feature

Introduction :

and based on HO related issue syste

m can adopts the parameter to resolv
e mentioned HO problem.

Policy for MRO and current setting

s:

Common criteria and current trial sett

ings

1 Total HO times should be >100 tim

es in 24 hour, between one Nbr. Rela
tion ie.(A->B)

2 Max and Min value adjusted by MR

O +6 to -6 dB

3 The Maximum 3 neighbor Cells can

be Optimize at a time

Scenario

1 Pingpong handover issue: >10%

2 Too early handover issue: (the % of
too early HO - the % of too late HO)
> 2%

3 Too later handover issue: (the % of

too late HO - the % of too early HO)
> 2%

Roll back condition

After Ping-
Pong HO optimization, if Too late H
O % becomes > 10% of total HO, th
an MRO parameter will be rolled bac
k

Recommendation:
FDD-POS-LTE-Enable LTE FDD inter-RAT ANR(LTE-

When this function is not enabled in the network,

1 In ZTE “Monitoring duration” is 24 h
ours and recommended to 48 hours
the neighbor cells of the LTE-UMTS rely on manual
optimization. The optimization effect will be limited
by the accuracy of the engineering parameters of
the cell. In order to improve the handover of the
LTE-UMTS result, this function needs to be enabled.

Networking Environment
2 In ZTE Min/
Max CIO range is +6 to -
6 dB and recommended +3 to -3 dB
Problem Cause Analysis
There are some issue which affected the ANR
optimization result as below:
Nokia use control mode

1. When the SON policy is not configured, the inter-

system LTE-UMTS ANR is not started.

2. The inter-system LTE-UMTS ANR function needs

Nokia monitoring manually
to support SON monitoring and control.

3. When there is no handover attempts from LTE to

UTRAN, the inter-system LTE-UMTS ANR can still
work, but it may affect the accuracy of the ANR
optimization result due to there is no handover
attempts.
 4. When the SRVCC process from LTE to UTRAN is
not supported, the inter-system LTE-UMTS ANR can
still work, but the accuracy of ANR optimization may
be affected.

1 In Nokia to prioritize problem (too e
arly, too late and Ping-
Pong) using “Cost Factor”.
But in ZTE priority is based on numb
er of failures rather than weightage.
5. When there is no CSFB from LTE to UTRAN, the
inter-system LTE-UMTS ANR can still work, but it
may affect the accuracy of ANR optimization results.
Solution
[Relate Parameter]:

2 Too early and too late both are hav Defau

Parameter Value
e RLF failure and considered as a H lt Unit
O failure. Name Range
Value
enum(
sonEnableUtraA
Close, Close
NR
Open)
As per ZTE R&D need to handle suc
utranStatisticTi [1,255
h issues on the basis of failure severi 24
ty mer ]
enum(
staticTimerGrad Hour,M
hour
e inute,S
econd)
PCI Correction Policy – current settin lteUtranPciSrvRs [-140,-
-100 dBm
gs: rpThrd 43]
utranPciRscpThr [-120,-
-105 dBm
d 24]

1 For PCI correction Centralized met

hod is used, and decison has been ta maxUtranNbrNu [1,128
64
ken by EMS, which is having project m ]
parameters for all the neighbors.

[0,100
utranHoSuccRat
] step 95 %
eThrd
0.01
2 PCI Correction is done by “ Control
Mode” nbrAddCnt [1,64] 4

utranNbrRptThr [0,655
10
d 35]
3 Appointed time for PCI correction is utranHoSuccThr [0,655
5
2 : 00 AM, Everyday. d 35]
 [1,255
redNclDelPrd 15 Day
]

enum(
utranRedNrDelS
Rules for PCI Correction: Close, close
wch
Open)

utranHoRequest [0,655
5
Thrd 35]

1 Re-
use distance criteria = 5000 Meters ( [0,655
utraNbrHys 5
urban clutter) & 10000 Meters (rural 35]
clutter)

enum(
HandoverFailDet
Close, close
ectSwch
Open)

HandoverFailNu [0,655
2 PCI chosen from defined range 20
mThrd 35]

utranCarriFreqN
0-32 3
um

Recommendation: PCI collision/

confusion detection will be enabled w utranMeasParas. enum(
ith ANR feature in separate cluster, b
ecause our PCI parameters are woki utranFreqANRIn Close, close
ng with ANR. If ANR enabled than w d Open)
e can have more observation.

utranMeasParas. enum(
utranFreqANRDe Close, close
lInd Open)

i.e. If 21 too late HO failure and 100 t

oo early HO failure, so as per Nokia
will address too late HO(21*1=21, 10
[Optimization Result]:
0*0.2=20) after resolving too late HO
failure there is more possibility to get
increased too early HO failure.
but as per ZTE too early will be resol
ved first.

Mobility Robust Optimization Feature –

Cluster Level Analysis
Summary and Notes
Remark: After open LTE-UMTS ANR, LTE to UMTS
handover success rate and SRVCC success rate gap
improvement much.
MRO enabled on 5th,Feb. Total HOSR of clust
er SMG_20 improved

Mobility Robust Optimization Feat

ure – Cell Level Analysis (Case Stu
dy 1 - Too late HO)

Case : Too late HO

HOSR intra improved and HO Failed

decreased cell level

Case : Too late HO

Intra HOSR improved

Case : Too late HO

Inter HO SR.

Case : Too late HO

Intra HO SR improved.
Case : Too early HO

Inter HO SR

Case : Too early HO

HOSR inter improved and HO Failed

decreased

Case : Too early HO

Ping Pong HO was decreased

and HOSR intra improved

Case: Too late and Too late HO

Too late and Too early HO event

decreased

ANR Feature

"Automatic Neighbor Relation" is a tool

to add the missing neighbor relations as
well as deletion & blacklisting of unwan
ted neighbor relations.

ANR is having two types of Neighbor list

:

Temporary Neighbor List : When first ti

me neighbor added through ANR functio
n, it goes to Temporary Neighbor list.

Formal Neighbor List : Added neighbor f

rom temporary list if pass the shifting cr
iteria.
ANR Addition Policy – current setting
s:

1 If temporary cell HOSR > 98% , th

en Neighbor shift to formal list

2 Time window for Shifting from Tem

porary list to Formal list:

24
hrs for ( Dense urban and urban)

48 hrs (for Sub urban and rural).

3 Appointed time for Addition : 00:00

to 06:00 AM

4 Maximum No. of neighbor Addition

limit:

Intra frequency neighbor addition li

mit : 50 (dense urban & Urban) & 40
( Sub urban & Rural)

Inter frequency neighbor addition li

mit : 60 (dense urban & Urban) & 40
( Sub urban & Rural)

5 If HOSR is <98% & > 90% ; Then

removed from the temporary list after
(24, 48hrs) and will be added later t
hrough ANR functions and If HOSR i
mproves and becomes >98% then m
ove to formal list in next shifting wind
ow.

6 If HOSR < 90% ; than neighbor will

be black listed.

ANR Deletion Policy : Deletion is only

happened from Formal Neighbor list
– current settings.

1 If HOSR < 90% & No. of HO attem

pts > 50

2 If Continuous HO failure > 10

3 If low HO attempts <5 ( 72 Hrs for
Dense Urban & Urban ; 120Hrs for S
ub-urban & Rural)

4 Deletion Through Replacement of

Neighbors ,in formal neighbor list.

5 Time window for delete Neighbor fr

om Formal list:

24
hrs for ( Dense urban and urban)

48 hrs (for Sub urban and rural).

ANR BlackListing Policy: Black listin

g of neighbors is happened from only
Temporary neighbor list.

If HOSR <90% & No. of HO attempts

>50

Recovery from Blacklisting :

1 Automatic Recovery Criteria : HOS

R >91%

2 Manual Recovery Criteria :

Through Parameter change, From “

NO HO Allowed” to “ HO Allowed”,

But after chaning the parameter, neig

hbor cell still will be in blacklist, and it
will only remove from BL once HOS
R is improved >91%, That’s why BL
monitoring & optimization is importan
t.

Recommendation:Time window for a

ddition/
deletion and blacklisting detection an
d recovery keep as ZTE policy sugge
sted by R&D.

For example:
Nokia will not add NBR(<-100dBm) based on
policy, which is not acceptable in some
condition

ZTE will add this NBR based on mobi

lity strategy
FDD to FDD or TDD to TDD HO at 3
dB.So it will help to resolve the HO/
drop issue.

ANR Performance

After ANR function activated, there ar

e 2561 neighbor relation added and 8
359 neighbor relation deleted.

For Long Period No Handover Detect

ion parameter was set 120 hrs., whic
h means 5 days after we activate the
ANR, change policy will take effect fo
r this function. The pie show the 5 da
ys different after and before 12th,Feb
.

Redundancy: If in external Nbr list A-

√ ->B(have)but from B-x-
>A (don’t have) it means redundancy
relation.

Invalid: Neighbor cell added but not e

xits in NBR relation table.

Long Time No Handover Analysis

Actually most of the Long Time No H

andover deletion is caused by the ha
ndover attempt times less than 5 tim
es during continuous 5 days (120 ho
urs), same as the policy we set:
Below is statistics to show long time
no handover:

Black List Analysis

The neighbor relation distance less

than 2,000 m and which we want to
modify the NoHO attribute shown as
below:

Basic KPI (Handover Success Rate

)

After ANR function activated, averag

e HOSR for cluster DPR_05 improve
d from 97% to0.81% after ANR activ
ation.

ANR Performance –
Cells Level Analysis

Observed improvement in HOSR (Intra)

Observed improvement in HOSR (Int

er)

Automatic Inventory Feature

Introduction :

Automatic Inventory is a feature by e

nables operator to get equipment info
rmation of inventory automatically.

Policy for Automatic inventory:

eNodeB will deliver the inventory info
rmation to OMC after eNodeB startup
.

By this function we can find the inventory

type, serial number and so on, below is the
screenshot :

PCI Detection and Correction Feat

ure

Introduction:

"PCIDetection and Correction Featur

e” is a tool to find out the PCI Collisio
n and Confusion cases and their corr
ection automatically.

PCI Collision: If serving cell and Neig

hbor cell have the same PCI for sam
e frequency.

PCI Confusion : If two neighbor cell o

f one serving cell is having the same
PCI.

PCI Detection Policy :

There are two type of methods for P

CI detection.

Method 1: Common detection for kno

wn and unknown neighbors based on
UE measurement and information th
rough X2 interface.

Method2: PCI Collision/

Confusion detection for known neigh
bors by UE, This method is used cas
e by case basis depends on the Issu
e’s.

PCI Correction Policy – current settin

gs:
For PCI correction Centralized meth
od is used, and decison has been tak
en by EMS, which is having project p
arameters for all the neighbors.

PCI Correction is done by “ Control M

ode”

Appointed time for PCI correction is 2

: 00 AM, Everyday.

Rules for PCI Correction:

Re-
use distance criteria = 5000 Meters (
urban clutter) & 10000 Meters (rural
clutter)

PCI chosen from defined range

Recommendation: PCI collision/

confusion detection will be enabled w
ith ANR feature in separate cluster, b
ecause our PCI parameters are woki
ng with ANR. If ANR enabled than w
e can have more observation.

Recommendation:

ZTE PCI policy we keep as ZTE R&D

proposal

PCI re-
use distance based on clutter urban=
5000m, suburban/
rural=10000m. It can be modified bas
ed on requirement.

For example:

As per Nokia policy above cases will

not be address first(>1000 and <500
HOSR)
But in ZTE all deteced PCI confusion
and collision can be resolved
(currently in "contral mode")

There are totally 4 PCI confusion and

no collision detected in cluster
SBY_15:

Due to small area, less result was

observed. Recommended SBY_12 to
evaluate this feature.

There are totally 8 PCI confusion

detected in cluster SBY_12:

Solution
Self Healing Feature

Introduction :

Self healing is a feature by which sys

tem can detect the syestem related (
Software & Hardware) issue and can
be healed automatically as per policy
.

Self Healing Policy:

SH overall time window: 8:00-22:00

SH observation window = 3 hours

KPI criteria:

1. No RRC connected user

2. No RRC request times

3. No Incoming HO
Compare last 7 days KPI for same ti
me frame

1. RRC request >100 times (defaul

t)

RRC request >50 times (recom

mended)

&

2. Incoming HO >200 (default)

Incoming HO >50 (recommend

ed)

System is using same time frame to

check the real user behavior continuo
usly last 7 days. Below are the two p
ossibilities:

a. If found traffic in any of the time

window in last 7 days that means H
W is normal before and need to resta
rt.

b. If found no traffic than 2 possib

ilities:

1. No genuine traffic –
need to do call testing on site

2. HW issue – will be handled

by COD feature.

To avoid the unnecessary restart on

weekends we are doing traffic study
and will not implement SH policy on c
ells which is not carrying traffic during
weekends.

There are 5 sleeping cell observed b

elow, as example cell MLG_0101_32
Cell Outage Detection Feature

Introduction :

Cell Outage Detection is a feature by

which system can detect the alarm &
Hardware issue and can be recovere
d automatically as per policy.

Policy for Cell Outage Detection :

After activate SH&COD function in M

alang city, there are totally 76 times o
utage detection. The worst cell is ZM
LG_0067_32 which has 53

After checking historical alarm, we ca

n see the reason distribution

Energy Saving Feature

Introduction :

“Energy Saving feature ” is a tool to r

educe the power consumption while t
here is very less traffic Or No traffic d
uring the non busy hours.

Energy Saving Policy – current settin

gs:
There are three type of Energy savin
gs are possible.

Cell Shutdown :

For energy saving (cell shutdown

) we have selected TDD10 layer as a
case study. Below mentioned the Cri
teria for cell shutdown.

Energy saving time Window : 00:00 t

o 05:00 ( Working day)

01:00 to 07:00 ( Weekend)

TDD10 UL & DL PRB Load < 10%

No. of RCC connected user < 20

Compensation Cell TDD 20 should h

ave

UL & DL PRB available No. = >5

+ Total Utilized PRB in TDD10

Shortest time allowed for Energy savi

ng = 2 Hrs

Minimum time required to re-

enter in energy saving mode = 15 mi
n.

ES Cell Wake Up Criteria – for energ

y saving cell - current settings:

There are three type of wake up crite

ria;

expiry of energy saving windows – (a

fter 5 am for working day and 7 am fo
r weekend)
major service affecting alarms on con
figured compensating cell (TDD 20M
hz)

compensation cell (TDD 20Mhz) utiliz

ation

current setting is 90% utilized

Smartfren recommended value is 60

% utilized but the current software ve
rsion only supports up to 90%. ZTE w
ill feedback on the feature upgrade th
at will support lower utilization.

After activating the ES function on 20

16/01/29, the number of cells enter E
S mode is shown as below.

With current version of ES feature, w

e are able to provide how many cells
entering to ES mode. In Q2 we will s
how exact calculation of power consu
mption during ES mode.

Below is the comparison of before an

d after enable energy saving function
, we can see power is reduced from 1
60w to 120w during the appoint time
after ES is activated from 2016/01/29

Summary and Notes

Capacity and Coverage Optimizati
on Feature

Introduction :

CCO is a feature by which system ca

n detect the coverage holes.
Policy for CCO:

If Serving cell and Neighbor cell RSR

P <-
118dBm System records measureme
nt reporting.

After CCO function activated, 121 co

verage holes were detected in 54 cell
s, top 10 cell as following

This function just show which cell has

weak coverage and give the coverag
e hole times. But it doesn’t provide th
e detail location and next solution.

1. Coverage hole identification is disp

layed in NETMAX, now it is ready

2. Coverage solution is provided by C

SON (ZTE will update on this feature
s availability)

Mobility Load Balancing

Introduction :

In ZTE MLB is having 2 types:

1. Camping Load Balancing(CLB)

CLB is the idle mode load balancing,

it is for same coverage cells such as
TDD20 ->TDD10

2. Traffic Load Balancing(TLB)

 TLB is the connected mode load bala
ncing, it is for all Nbr Cells(intra-
inter eNB and intra-inter frequency),

But not possible for same coverage

Parameters which will be changed ba

sed on policy:

CLB: Qoffset, ThreshXhigh, ThreshXl

ow

TLB: Ocn (Cell specific offset of Nbr

cell)

Parameters Details for MLB Featur

e:

Parameter Recovering Criteria:

1. Normal recovery after 30 min. (as

per Valid timer)

2. Suppose Serving cell PRB util. X

Neighbor cell PRB util. Y

If X - Y <10% parameter will be rolle

d back any time in the window of 30
min(valid timer)

Planning & Optimization Solution for TDD-LTE-TDD LTE 4*4 MIMO Feature Deployment
Liquid is one of the TDD customers
in Sale Division II and want to know
the progress of
4*4MIMO function deployment
and then to evaluate the
performance of our equipment.

so it’s important to achieve a good

speedtest result in
our testbed with 4*4 MIMO
function.
Networking Environment

Problem Cause Analysis

To achieve the target need check
both the license and Configuration
of e-NodeB and modify some
important parameters.
Solution
【1】Baseband Resource
Configuration

【2】Cell Parameters Configuration

【3】Transmission Mode
Configuration

【4】4x4MIMO Switch

【5】SRS and Ack/Nack Feedback

Mode Configuration

【6】PUCCH Format Configuration

FDD-POS-Case of SA MTN CSFB RIM success rate optimization
Through RIM hit rate optimization can shorten the LTE network CSFB delay,
significantly enhance the user perception. This paper presents an
optimization method and has been tested in the field to enhance the user
perception.

[Principle of CSFB]

CSFB principle is 3GPP developed LTE voice solution, that is, the user
needs voice, the phone back to 3G to call; hang up, the phone back to the
LTE network for data services.

From the fall mode, CSFB is divided into R8 and R92 species, the main
difference is that the system issued by the RRCConnectionRelease message
whether to carry 3G neighbors cell system messages. From the CSFB down
the whole process can be seen, down the delay of the constraints mainly in
the "read system messages 1,3,13" on. In order to save the time to read the
system message, in 3GPPR9, RIM (RANInfor⁃mationManagement) solution
is proposed. That is, through the MME and SGSN RNC and eNodeB
between the opening, so that eNodeB can be issued to the target 3G cell
system messages, thus omitting the process, but the RIM function requires
network element support.

At present, South Africa MTN Catapult project LTE network in the CSFB
network delay optimization found RIM hit rate is not high, the whole network
pull RIM hit rate of about 75%.

Networking Environment

Problem Cause Analysis

At present, the number of RIM neighbors is 8, and the RIM hit rate is
improved by optimizing the RIM neighborhood and then modifying the
number of RIM neighbors.
2.1 to enhance the RIM hit rate optimization ideas:
2.1.1 RIM neighborhood based on LTE to UMTS neighborhood switching
distance, number of handover and handover success rate, optimization of
RIM neighborhood;
2.1.2 will be the original number of RIM neighbors set from 8 to 16, to
enhance the hit rate;
2.2 Determine RIM Neighborhood Privilege Rules:
2.2.1 If the site has U900, we will configure eight U900 3G RIM neighbors,
while the LTE side of the CSFB U900 carrier has a high priority.
2.2.2. If there is no U900 carrier in the field, we will configure 8 U2100 RIM
neighbors, while the LTE side of the CSFB U2100 carrier has a high priority.
2.2.3. If the on-site U900 carrier has a high RTWP problem, we will configure
8 U2100 RIM neighbors and the LTE side CSFB U2100 carrier with high
priority.
2.3 CSFB analysis tools based on QCAT software, test terminal is Samsung
S5;
Solution
3.1 RIM neighborhood optimization:
3.1.1 80 sites (275 cells) due to UtranRelation for 64 can not add new
planning RIM neighborhood of the site for the 42, need to delete neighbors
208 (strategy: by distance to delete the furthest and most relevant neighbors
District relationship);
3.1.2 There are 264 neighborhoods with non-RIM Neighborhood Switch 1,
and the adjacent area RIM switch needs to be adjusted to 0;
3.1.3 Pinelands CSFB area test 80 sites, 275 cells, planning a total of 2,200
RIM neighbors, of which 1745 existing RIM neighbors (356 adjacent RIM
switch is 0 exception, 1389 neighbors RIM switch is 1 normal), 455 RIM
neighborhoods are added;
3.1.4 Implementation of Trail District Verification:
Trial area deployment test route is as follows:

DT Result:

In the Pinelands Cluster to do the RIM neighborhood to optimize the re-

planning of the eight RIM neighbors, RIM hit rate from about 79% to 85%,
Trial verification area RIM hit ratio before and after:

3.2 increase the number of RIM neighbors to enhance RIM hit rate
verification;
The number of RIM neighbors in the current network is modified from the
current 8 to 16, and the selection of 16 RIM neighbors is not simply added to
the previous 8 neighborhoods, but the number of times the system is
switched , The same system to switch the success rate of comprehensive
consideration, and constantly filter the filter, and finally determine the 16
neighbors, the production of a good script to verify the implementation of the
implementation of the hit rate has improved significantly, trail area from the
previous 89% to 94%, and finally Carried out a whole network deployment.
Add

16 RIM neighbors after the road test found 44 times missed: 7 failure tools
everywhere data can not identify the specific cell, 13 neighborhood
relationship is not Pinelands area of the district, 10 is already exists RIM
neighborhood but failed, 2 is 1800-2100 lead to failure (policy problem);
Added 5 RIM neighborhoods (RIM misses because neighborhoods are not
added); 7 neighborhoods exist but non-RIMs cause misses and have been
optimized for RIM neighbors.

3.3 Fine processing of RIM failure problems

Combined with the road test net verification results, continue to focus on
individual sites to optimize the RIM neighborhood, to enhance the network
RIM hit rate.

3.4 verify RIM parameters to ensure that RIM function is activated;

Check the entire network switchUtranRim switch parameters, found
1503/18815/23382/572/18832 this switch is not open, modified to confirm the
entire network RIM function all activated;
3.5 Optimization Note:
3.5.1 When adding RIM neighbors, check the number of existing neighbors
(the default number of neighbors is 64).
3.5.2 When deleting the RIM neighborhood, please delete the deleted area to
delete it;
Summary and Notes
4, optimization summary
Pinelands Cluster and the entire network for RIM validation RIM hit rate
statistics are as follows:

Total RIM hit

Action Area Date Site NO. RIM hit fail times
Times suc rate
8RIM Pineland
### 80 sites 160 34 78.75%
Trial s

8RIM Pineland
### 80 sites 201 32 84.08%
DT Test s

8RIM whole 2017/6/ 966

1522 239 84.30%
Deploy Network 9 -14 sites

16RIM Pineland
### 80 sites 961 44 95.42%
Trial s

16RIM whole 2017/7/ 966

728 66 90.93%
Deploy Network 8 -12 sites

By optimizing the RIM neighborhood by selecting the distance between the

neighborhood of the heterogeneous system, the number of switching
systems and the switching success rate, 8 of the RIM neighbors are selected
as the RIM neighborhood, Of the 78.75% to 84.08%; and then modify the
number of RIM neighborhood increased from 8 to 16, RIM trail area hit rate
from the original 84.08% to 95.42%, the whole network in accordance with 16
RIM neighbors deployed RIM hit Rate to 90.93, follow-up targeted RIM
optimization is still ongoing.
How to Configure ROHC Parameters of VoLTE
Configuring ROHC Parameters of
VoLTE as below.
Solution
1 Opening the Depth ROHC Switch.
The depth ROHC switch indicates
whether the ROHC feature is enabled
on the eNodeB. If the switch is
opened, the ROHC feature is
enabled; otherwise, it is disabled.

Purpose:
The purpose of the operations here is
to open the depth ROHC switch.

Procedure:
To open the depth ROHC switch,
follow the steps below:
(1) In the Managed Element pane of
the desired eNodeB, find and double-
click E-UTRAN FDD Cell (path: Radio
Parameter -> LTE FDD -> E-UTRAN
FDD Cell) to open the E-UTRAN FDD
Cell-List tab page on the right (see
Figure 5 1Figure 5 1 E-UTRAN FDD
Cell-List Tab Page).
(2) In the E-UTRAN FDD Cell-List tab
page, select one cell record and
click on the tool bar to open the E-
UTRAN FDD Cell tab page.
(3) In the E-UTRAN FDD Cell tab
page, find the parameter Depth
ROHC Switch and set it to be Open.

(4) Click save button to save the

configuration. The depth ROHC
switch of one cell is then configured.
(5) Repeat Steps 2 - 4 to configure
the depth ROHC switches of other
cells.

2 Configuring ROHC Profiles for

QCI1.
Among all the QCIs, it is required to
configure the ROHC profiles for QCI1
only.
Purpose:
The purpose of the operations here is
to configure the ROHC profiles for
QCI1 based on the UE’s capabilities.

Procedure:
To configure the ROHC profiles for
QCI1, follow the steps below:
(1) In the Managed Element pane of
the desired eNodeB, find and double-
click PDCP Parameters (path: Radio
Parameter -> LTE FDD -> E-UTRAN
Service Configuration -> PDCP
Parameters) to open the PDCP
Parameters-List tab page on the
right.

(2) In the PDCP Parameters-List tab

page, select the record whose label
number of service class is 1 (i.e.
QCI1) and click on the tool bar to
open the PDCP Parameters tab page.

(3) In the PDCP Parameters tab

page, set the profiles according to
the description in Table below.

(4) Click save button to save the

configuration.
D inter-RAT ANR(LTE-UMTS) to improve LTE to UMTS handover Success Rate

in the network,
S rely on manual
ct will be limited
parameters of
andover of the
ds to be enabled.

ed the ANR

figured, the inter-

ed.

R function needs
ntrol.

mpts from LTE to

S ANR can still
cy of the ANR
no handover
LTE to UTRAN is
TE-UMTS ANR can
optimization may

E to UTRAN, the
till work, but it
timization results.

Reco
mmen
d
Value
Open

24

hour

-105

-105

64

90

10

3
3

Open

Open

15

Open

Open
R, LTE to UMTS
success rate gap
ature Deployment
UMTS-No RRC access and traffic cell troubleshooting
Check the cell no alarm no issue,find that two cells in same slot 7,reconfigure the cell in slot 8,issue clear.
UMTS-Access failures solution case
1 ) terminal problem

problem caused by mobile phones, data cards , SIM cards and other problems caused
by the failure of the terminal .

2 ) Network Cause

The signal coverage blind spots , too much interference and cell load and other issues
can cause access failure .

3 ) radio parameters set incorrectly

The access threshold set unreasonable, the leading power ramp step size and the
number of retransmissions set unreasonable , uplink and downlink dedicated channel
such as a low initial power failure caused the access.

4 ) base stations
insufficient resources caused access to equipment failure ect.

5 ) the base station and the RNC side data configuration issues
6) CN side issue

Solution

1) coverage: The test found that the average cell RSCP -68dBm, Ec / Io average -4dB,
signal quality is very good.
2) Check the load cell: the role of access control mechanisms, the UE may make access
to the load cell exceeds the threshold, RNC UE will refuse the access.So get back in the
RNC cell total bandwidth uplink received power (RTWP) and downlink cell total transmit
power (TCP), observe these two values far below the pre-set system access threshold,
excluding cell overload caused by access the failure.

3) Interference troubleshooting:

We logged in NodeB 1835 with DMS tools,finding the problem cell digital transmitter
carrier power 35.9 dbm, Rtwp -106.6db, which all was within normal scale so we exclude
interference cause.

4) verification of radio parameters

We checked the parameters of NodeB with BASELINE by CNO and found all parameters
are matched, so we exclude the cause.

5)device hardware troubleshooter

General hardware problems on the network will produce a corresponding alarm. This site
without any warning, the area of the channel was normally established,and physical
channels and common transmission channels are also normal. So we exclude the
hardware cause.

5) RNC side data configuration troubleshooting

Checking parameters in RNC side and Nodeb site: NodeB ID, cell ID, PI, CI,NodeB IP
address and other parameters,we found that the NodeB IP address in RNC was not
matched with it configured on the Nodeb site. Correction NodeB IP address of the base
station after the test site, CS services and PS services are normal.

Summary and Notes

Access procedure is the first step to for UE interact with network.A successful access
involves many aspects of factors.In the analysis of the access issue,we should set off
from easy to difficult to save human and material resources as less as possible. Through
call and signaling systems analysis we can quickly narrow the problem spot,to exclude
the equipement and external cause as early as possible.
ot 8,issue clear.
LTE FDD Network Planning & Optimization System-GL Refarming—Traffic Evaluation
xxx operator needs to divide the frequency band in the 1800MHz for LTE, which they in DCS
1800MHz downlink bands has 1851.2-1860MHz before refarming, occupy the 8.8MHz bandwidth, downlink
bands turn to 1844-1862MHz after adjust and allocation, distribution of GL frequency using sandwich
method, GSM occupancy 4MHz of both sides, LTE accounted for the middle 10MHz. Since the present 73
sites with the old equipment RSU60, RSU60 can only support up to 1860MHz and could not support 1860-
1862MHz band, considering need to decrease the carrier frequency after refarming ,

Operator wants to assess specific numbers of RSU60 site cannot meet the existing network traffic after
lowering the carrier frequency. Note: The specific refarming has been outsourced to Aircom, ZTE just needs
to analyze the number of RSU60 sites need to change.

Networking Environment

Problem Cause Analysis

As RSU60 bought from ZTE, GUL network equipments are also from ZTE, now old equipments cannot
support new band, Algeria office worried OPERATOR let ZTE to replace them for free or part free, that will
increase the budget, after two exchanges with OPERATOR that OPERATOR do not have the meaning that
let ZTE replace for free, because RSU60 perfect support before band, OPERATOR also actively looking for
the best solution.

RSU60 sites support from the original 8.8MHz bandwidth reduced to 6MHz, some high equipped sites will
certainly decrease carried frequency, according to minimum BCCH 4 x 3 reuse, TCH by radio frequency
hopping 1x1, configuration up to S443 after adjust, single sites with less than 11 carrier frequency and 11
carrier frequency can meet the current traffic don’t need to change, sites more than 11 carrier frequency
need to change. Because many sites with 900M were co-BCCH, sites configured to S666; if continue co-
BCCH with 900M single site can upon to S555, but need to check the sites around whether the BCCH
frequency point is occupied, avoid BCCH and TCH frequency points interference.
According to BCCH frequency point number size can distinguish 900M and 1800M cells.

Due to 900m and 1800m BCCH, district named the same, for cell BCCH, according to district extraction of
CS and PS traffic is containing the 900m and 1800m, extraction of the corresponding counter 1800m station
flow; for non BCCH, according to district traffic can be extracted.

Because 900M and 1800M co-BCCH cells have the same names, for co-BCCH cell, according to the cell
name extracting CS and PS traffic contain 900M and 1800M cell, so need to extract the corresponding
counter of 1800M; for non co-BCCH, just extract traffic according to the cell name.

Solution

1. Extract the current network reference parameters of all sites, including the BCCH, TCH frequency
hopping sequence, the 900M and 1800M cell level classification, extraction half rate threshold of each cell,
and BCCH, static PDCH, SDCCH configuration of carrier frequency;

2. To extract RSU60 and RSU60E sites three months of every day CS and PS traffic of busy hour,
combined with CS and PS traffic equivalent to ERL. Due to the many cells open CS half rate threshold,
corresponding half rate ERL table get corresponding traffic need the number of carrier frequencies, and then
compare carrier frequency requirements with the current network configuration.
3. Extract RSU60 sites of carrier frequency can't meet the current network traffic, extract RSU60E sites
traffic demand less than 36Erl as candidate replacement site list.

4. Later after the exchange with OPERATOR, RSU60 sites in urban area all replace by RSU60E, for the
isolated island sites of high traffic are also replaced by RSU60E.

Summary and Notes

1. At the beginning did not pay attention to the co-BCCH cells of the same name, found that
extracted traffic from the network beyond cell carrier frequency capacity, then I noticed that contains the
900MHz cell traffic, need to find out the special counter aimed at co-BCCH cell capacity. Now network of
GSM 900M and 1800M cell in order to improve the carrier frequency configuration, many sites use the co-
BCCH and 900M use as long-term coverage and 1800M as a supplement of capacity.

2. To the cell open half rate threshold, different thresholds and TCH channels numbers correspond to
the corresponding CS traffic, the number of TCH channels has been ruled out the static PDCH channel. If
the CS plus PS to the overall equivalent Erl contrast to the needed numbers of channels, a bit inaccurate.

3. Because the difference of extracted cell PS traffic is big, to renounce the use of it; the final
conclusion just based on CS traffic of past three months, not comprehensive enough as some tourist
attractions places are not in that time period.
on System-GL Refarming—Traffic Evaluation
n the 1800MHz for LTE, which they in DCS
efore refarming, occupy the 8.8MHz bandwidth, downlink
cation, distribution of GL frequency using sandwich
E accounted for the middle 10MHz. Since the present 73
only support up to 1860MHz and could not support 1860-
carrier frequency after refarming ,

U60 site cannot meet the existing network traffic after

refarming has been outsourced to Aircom, ZTE just needs
ange.

ments are also from ZTE, now old equipments cannot

OR let ZTE to replace them for free or part free, that will
ERATOR that OPERATOR do not have the meaning that
upport before band, OPERATOR also actively looking for

dwidth reduced to 6MHz, some high equipped sites will

minimum BCCH 4 x 3 reuse, TCH by radio frequency
single sites with less than 11 carrier frequency and 11
need to change, sites more than 11 carrier frequency
ere co-BCCH, sites configured to S666; if continue co-
t need to check the sites around whether the BCCH
H frequency points interference.
 an distinguish 900M and 1800M cells.

e same, for cell BCCH, according to district extraction of

0m, extraction of the corresponding counter 1800m station
n be extracted.

e same names, for co-BCCH cell, according to the cell

nd 1800M cell, so need to extract the corresponding
affic according to the cell name.

rs of all sites, including the BCCH, TCH frequency

classification, extraction half rate threshold of each cell,
carrier frequency;

ths of every day CS and PS traffic of busy hour,

L. Due to the many cells open CS half rate threshold,
ng traffic need the number of carrier frequencies, and then
urrent network configuration.
meet the current network traffic, extract RSU60E sites
ement site list.

U60 sites in urban area all replace by RSU60E, for the

d by RSU60E.

co-BCCH cells of the same name, found that

er frequency capacity, then I noticed that contains the
unter aimed at co-BCCH cell capacity. Now network of
e carrier frequency configuration, many sites use the co-
1800M as a supplement of capacity.

nt thresholds and TCH channels numbers correspond to

channels has been ruled out the static PDCH channel. If
ast to the needed numbers of channels, a bit inaccurate.

S traffic is big, to renounce the use of it; the final

months, not comprehensive enough as some tourist
FDD LTE PA&PB parameter optimization

Region 1: The DT test averages RSRP-82 and SINR+16. After basic

optimization such as antenna feeder adjustment, the download rate reaches
39.64Mbps.

Region 2: Shopping center division; CQT DT test average RSRP-69, SINR+25,

and download rate 56Mbps. In the above cases, there is room for further
improvement of the download rate. Now we try to optimize the parameters.
We find that the default setting of "/1" is set for PA/PB of the surrounding
eNodeB cells. This parameter has a great impact on the download rate and
can be optimized.

Networking Environment

Problem Cause Analysis

The RS power, PA, and PB parameters determine the power of each

subcarrier and the total power.

1. Common types of macro station: 2PORT logic antenna, bandwidth 15 M

cell, PA=-3 dB RS=15.2dBm PB=1. The power calculation is as follows:

1.1 RE power

Suppose the RS transmission power is configured as 15.2dbm. PA is

configured with -3 dB, while PB is configured with 1.

For TypeA:, the RE transmission power for transmitting data is 15.2dbm-

3db=12.2dBm.

For TypeB:, the RE transmission power for transmitting data is

12.2dbm/1=12.2dbm.

Maximum transmit power of the 1.2 TypeA symbol

Maximum transmit power (mW) configured on one TypeA symbol = power of
each data RE on the TypeA configured on the interface * number of data REs
on one TypeA symbol

Analysis:
The 15 M bandwidth consists of 75 RBs. One RB contains 12 REs, all of which
are used to transmit data.
Calculation:

Pmaxout_A=TYPEA*RE number =TYPEA+10lg (RE number) = (RS+PA)

+10lg(RE number) = (15.2-3) +10lg (12*75) =41.74dBm, that is, 15 W.

Calculate the maximum transmit power of the 1.3 TypeB symbol

Maximum transmit power (mW) configured on one TypeB symbol = pilot

transmit power configured on the interface (mW) * number of pilots under
one TypeB symbol + power of each data RE on the TypeB symbol calculated
according to the interface configuration * number of data REs under one
TypeB symbol.

Analysis:

The 15 M bandwidth consists of 75 RBs. One RB contains 12 REs, of which 8

are used to transmit data and 4 are used to transmit reference signal RSs
(also called pilot signals). For each antenna, only two of them are used, and
the other two are reserved for other antennas. Therefore, two of them are
not counted.

Calculation:
Part of power without RS: 12.2+10lg (8*75) =39.98dBm

Part of power with RS: 15.2+10lg (2*75) =36.96dBm

Pmaxout_B=TypeB* number of REs without RS +RS*RS =10lg
(103.998+103. 696) = 41.74dBm, that is, 15 W.

1.4 cell RS and PA/PB configuration in the existing network

The PA/PB of the existing network is set to -3/1 by default, and the RS power
of different cells in the existing network is set to 18.2, 15.2 and 12.2.

Solution

The RRU of the macro station in the existing network is 2T4R, and the
maximum transmission power of a single channel is 40 W. Without changing
the reference signal power, the symbol power of the data domain is increased
to maximize the downlink output power and increase the downlink rate.

Select area 1 for modification and optimization. By default, (PA and PB) of the
existing network are (-3, 1). Modify (PA and PB) according to the bandwidth
15 M and RRU output power 40 W to improve the power of data domain
symbols.

Summary and Notes

This optimization is based on two scenarios: Macro site cluster area and
indoor distribution system. The PA/PB parameters are optimized according to
the factors such as RRU power, bandwidth and RRU single/dual-channel
transmission to increase the symbol power of the data domain, maximize the
downlink output rate and increase the download rate by about 5M.
LTE FDD Network Planning & Optimization System-UE cannot connect to Network in one si
When doing SSV test, we found one
site cannot be connected by UE.
Networking Environment
Beside this site there is no other site
and the other site is far away from
this site.
Problem Cause Analysis
And we check SCTP, they are ok. do
a PING from eNodB to MME, there is
no missing data packet. Then we
check the other parameters of
this site, They are all right. And the
TAC is the same with our plan
table.But why the UE canot build E-
RAB connection ?

We found that the RRC can connect

successful but it will be released right
away.so we capture some signal. We
can see the signal said that "Unknow
or missing APN", but the APN in UE
is ok.We think that has strong
relation with core net.

Solution
Even if we found the TAC is the
same with our plan table, but we
doubt if core net has right
configuration. So we change the TAC
of this site to the same with the other
sites beside of it. Then we check the
signal in Netnumen and go there to
do a test again, we found the signal
is ok and UE can connect
successfully.
Summary and Notes
This issue is because of the wrong
configuration of TAC, and we should
be careful with some single site that
has single TAC in our project.
How to configure Carrier Aggregation
his document provide the guidance of
configuration for CA(Carrier
Aggregation)
Solution
The key parameters for CA are Intra-
LTE Neighbor Relation,Switch for
Removing Neighbor Cell,Cooperative
Relationship Type,and The Switch of
Coper Type Change. And the
fieldname for these parameters are
shareCover,isRemoveAllowed,coper
Type, and coperModSwch.

In order to open CA function,

parameter value should be set
as :shareCover=Same
Coverage[1],isRemoveAllowed=No[0]
,coperType=Only DL CA
Support[8],coperModSwch=Not
allowed to modify[1].

step[1], you need to check the NR

for cell pairs from.

if NR for cell pairs exist, execute

step[2] the update commands to set
key parameters above to correct
value. if NR does not exist, then to
create NR with correct parameter
value.

step[2]example:

update commands:

UPDATE:MOC="EUtranRelationFDD
LTE",MOI="SubNetwork=101,MEID=
534927,ENBFunction=534927,EUtra
nCellFDDLTE=40,EUtranRelationFD
DLTE=0",ATTRIBUTES="isRemoveA
llowed=0,coperModSwch=1,shareCo
ver=1,coperType=8",EXTENDS="";
UPDATE:MOC="EUtranRelationFDD
LTE",MOI="SubNetwork=101,MEID=
534927,ENBFunction=534927,EUtra
nCellFDDLTE=49,EUtranRelationFD
DLTE=49",ATTRIBUTES="isRemove
Allowed=0,coperModSwch=1,shareC
over=1,coperType=8",EXTENDS="";

create commands:

CREATE:MOC="EUtranRelationTDD
LTE",MOI="SubNetwork=13,MEID=6
56577,ENBFunction=656577,EUtran
CellTDDLTE=136,EUtranRelationTD
DLTE=250",ATTRIBUTES="coperTy
pe=0,isRemoveAllowed=0,switchonTi
meWindow=1,isESCoveredBy=0,s1D
ataFwdFlag=1,isHOAllowed=1,cover
ESCell=0,refEUtranCellTDDLTE=\"S
ubNetwork=13,MEID=656577,Config
Set=0,ENBFunction=656577,EUtran
CellTDDLTE=101\",userLabel=\"\",E
UtranRelationTDDLTE=250,overlapC
overage=50,shareCover=1,qofStCell
=15,isAnrCreated=0,resPRBDown=5,
isX2HOAllowed=1,resPRBUp=5,refE
xternalEUtranCellTDDLTE=null,refE
UtranCellFDDLTE=null,lbIntraMeasur
eOffset=-
3,stateInd=2,refExternalEUtranCellF
DDLTE=null,cellIndivOffset=15,coper
ModSwch=1,supportMRO=1,hSpeed
RailCellInd=0,noSupMobilitySwch=0,
numRRCCntNumCov=700,coperTyp
e=8",EXTENDS="";
CREATE:MOC="EUtranRelationTDD
LTE",MOI="SubNetwork=13,MEID=6
56577,ENBFunction=656577,EUtran
CellTDDLTE=136,EUtranRelationTD
DLTE=251",ATTRIBUTES="coperTy
pe=0,isRemoveAllowed=0,switchonTi
meWindow=1,isESCoveredBy=0,s1D
ataFwdFlag=1,isHOAllowed=1,cover
ESCell=0,refEUtranCellTDDLTE=\"S
ubNetwork=13,MEID=656577,Config
Set=0,ENBFunction=656577,EUtran
CellTDDLTE=131\",userLabel=\"\",E
UtranRelationTDDLTE=251,overlapC
overage=50,shareCover=1,qofStCell
=15,isAnrCreated=0,resPRBDown=5,
isX2HOAllowed=1,resPRBUp=5,refE
xternalEUtranCellTDDLTE=null,refE
UtranCellFDDLTE=null,lbIntraMeasur
eOffset=-
3,stateInd=2,refExternalEUtranCellF
DDLTE=null,cellIndivOffset=15,coper
ModSwch=1,supportMRO=1,hSpeed
RailCellInd=0,noSupMobilitySwch=0,
numRRCCntNumCov=700,coperTyp
e=8",EXTENDS="";
ct to Network in one site
FDD-FL-Optimization of CIO Parameters in LTE to Improve the Intra-Frequency Handover Su
In recent routine monitoring statistics
and analysis, it is found that the ratio
of intra-frequency handover success
rates in network-wide KPIs is low,
affecting user experience.
Networking Environment

Problem Cause Analysis

According to the statistics, the
number of failed outgoing handovers
is very large, which is mainly caused
by unstable signals of the target cell.
As a result, the handover fails due to
the pinpoint or corner effect.
Solution
Optimize the individual offset of the
CIO cell in the Top cell pair that fails
to be handed over. For the failure
caused by too early handover,
reduce the individual offset value to
15 (0db) to 12 (-3db).

After the parameters are modified,

the success rate (cell pair) of
outgoing intra-frequency handover
between the X2 interfaces of eNBs is
increased significantly.
Summary and Notes

The key to analyze the abnormal

problems with daily data is to locate
the problem points, especially the
hidden problems. By comparing
continuous data statistics, you can
find the rule of the problem and
eliminate some simple and direct
reasons (for example, site
breakdown and RSSI problems).
Then, you can analyze the
parameters that may affect the
indicator in accordance with the
corresponding algorithm and
explanation, and adjust the related
parameters and compare them with
those before and after monitoring to
solve the problem.
requency Handover Success Rate