5 GSM Radio Network Planning and Optimization - Influence Factors + Troubleshooting Methods and Tools + Deliverables 20121031

2012-10-31 Security Level:
GSM Radio Network Planning and

Optimization:
Influence Factors + Troubleshooting
Methods and Tools + Deliverables
Prepared by: Wang Xi/Tang Xiaoli, Shi Yuan, Wan
Yin/Chen Zhe, Chen Juan, Li Xiaomeng, Huang
Xizhu, Li Yan, and Niu Shaobo
Reviewed by: Qi Haofeng www.huawei.com
October 31, 2012
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Abstract
This document describes principles for GSM network planning and optimization, how
to identify and resolve KPI problems caused by inappropriate planning or incorrect
data configuration.
GSM network planning and optimization involve a broad range of issues. This
document focuses on the following subtopics:
Subtopic Link
1. Capacity Contents
2. Coverage Contents
3. Interference Contents
4. CoBCCH Contents
5. Dual-Band Networking Policies Contents
6. Location Area Contents
7. Neighboring Cell Optimization Contents
8. Frequency Replanning Contents
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Change History
Date Issue Change Description Reviewer Author
Wang Xi, Tang

Xiaoli, Shi Yuan,
1. Added the following
topics: capacity, coverage, Wan Yin, Chen
October interference, and location Zhe, Chen Juan,
2012-10-31 2012 area (LA) planning. Li Xiaomeng,
edition 2. Integrated neighboring Huang Xizhu, Li
cell optimization and
Yan, Niu Shaobo,
frequency replanning.
and Xu Binbin

R&D Technical Support
Around the clock technical support is available.
The following table lists technical support engineers:
Subtopic Name Employee ID Tel
Capacity Wang Xi, Tang Xiaoli 61537, 49854 See the phone book.
Coverage Shi Yuan, Xu Binbin 146349, 232322 See the phone book.
Interference Wan Yin, Chen Zhe 181609, 182362 See the phone book.
CoBCCH Chen Juan 128551 See the phone book.
Networking policies Li Xiaomeng 135755 See the phone book.
Location area Huang Xizhu 128686 See the phone book.
Neighboring cell optimization Li Yan 139128 See the phone book.
Frequency replanning Niu Shaobo 166264 See the phone book.

Contents
 Capacity
 Coverage
 Interference
 Dual-Band Networking Policies
 CoBCCH
 Location Area
 Neighboring Cell Optimization
 Frequency Replanning
 Deliverables

Page 5
Contents
 Capacity
 X Measures for Capacity Planning and Optimization
 Principles for Capacity Evaluation and Optimization
 Equipment
 Um Interface
 Transmission
 Cases
 How to Use the Capacity Evaluation Tool
 Standard Operating Procedure and Deliverables

Background
Wireless networks change dynamically. With the wider use of smart phones, explosive
growth of PS services, and refarming in multi-RAT (GUL) scenarios, capacity has become
a major factor that influences the quality of experience (QoE) and the revenues of
operators.
To ensure the QoE and improve the return on investment (ROI) of operators, network
resources and capacities must be configured optimally and timely adjusted and expanded.
MBB traffic is growing quickly Smartphone penetration keeps fast growing

Exabytes/Month Source: Leading Vendor Millions Source: BI Intelligence
Smart phones
are the key drive

Overview of Capacity Optimization
Capacity = Capacity evaluation and + Feature
optimization services
Solution applications
Develop
customized
Feature
Capacity expansion and
Network capacity evaluation optimization solutions capacity
and forecast
1. To increase the dual-band optimization
1. Improvement of the utilization
network capacity:
of resources (UR) solutions based on
• Dynamic adjustment of the half- • CoBCCH
1. Traffic forecast rate threshold (HR/AMR).
• Linear forecast 2. When the frequency spectrum live network
• Adjust dynamic PS thresholds
• Secondary index regression and the soft capacity are
limited:
evaluation and
prediction 2. Inter-cell load sharing
• Traffic model-based prediction • Adjustment of dual-band network • IBCA development
thresholds 3. When capacity expansion is
2. E2E network resource • Parameter adjustment for inter- forecast.
cell reselection limited:
evaluation
• VAMOS
• Um resource evaluation
3. Accurate capacity expansion Develop dedicated feature
• Equipment resource evaluation
guidance
• Transmission resource • TRX expansion solutions.
evaluation • Site addition
Formulate optimization
Identify network capacity solutions.
bottlenecks.

X Measures for Capacity Planning and
Optimization
X measures for capacity planning and GSM RF Transmission
BSC Resource
Resource Resource
optimization are used to identify problems Audit
Audit
Audit
caused by capacity overload, evaluate
and analyze capacity problems, and A
perform corresponding optimization. PCH Audit XPU Audit Bandwidth
Audit
Resource capacity problems are as
follows: service access failure, low PS Gb
SDCCH DPU Audit
service rate, and poor user experience. To Audit
Bandwidth
resolve these problems, you need to Audit
perform E2E analysis of Um, transmission, Inter-rack Abis
and equipment resources based on TCH Audit Audit Bandwidth
problem symptoms to locate resource Audit
bottlenecks. License Ater
PDCH Audit Bandwidth
1. Are there any Um resource bottlenecks? Audit Audit
2. Are there any transmission resource Interface
bottlenecks? Frequency Board Audit
3. Are there any equipment resource Resource
bottlenecks?

Contents
 Capacity
 Equipment
 Um interface
 Transmission
 Cases

Equipment Resources — Overview
Resource Type Capacity Monitoring Capacity Expansion

Counter Threshold
Average CPU Usage of the 70%
XPU XPU
CS DPU Load 0.7 ERL/CIC
DPU (CS)
PS DPU Load 70%
DPU (PS)
Average Forwarding Ratio of 70%
Interface board Interface Boards
Inter-Rack Resource 60%
Utilization During Traffic Peak
Average Inter-Rack Resource 40%
Inter-rack communication Utilization Rate
resources
Inter-Rack Packet Loss Rate 0.01%

Equipment Capacity
Impact of Insufficient Capacity Evaluation Method KPI Optimization Scheme
XPU overload:
Optimize the XPU load
When CPU overload occurs, the BSC starts
AR9780: Average CPU Usage of the XPU > sharing parameters.
the flow control mechanism and discards
70%
paging messages and channel request Adjust the homing of
messages, directly affecting the access of Paging Success sites to balance the
Possible causes of XPU overload are as follows:
mobile stations (MSs). When serious CPU Ratio load between XPUs.
1. Insufficient XPU capacity
overload occurs, large number of MSs CSSR
2. Special local traffic model, such as too short
cannot access the network and the system
call duration or too high SMS message Expand the capacity of
automatically prohibits certain maintenance
percentage XPUs.
functions, such as log collection or
acquisition of traffic statistics.
To acquire the load of CS DPUs, evaluate the

average traffic of DPU circuits during busy hours.
The definition of the counter is as follows:

CS DSP: CS DPU load = [ZK3014: Traffic Volume on Assignment Success
CS DPUs process voice codec. If CS DPUs TCH (Traffic Channel) per BSC]/[CS DPU Rate Expand the capacity of
are insufficient, CS services cannot access specification x Number of CS DPUs] CSSR CS DPUs.
the network.
Capacity expansion threshold:
[CS DPU load] > 0.7 ERL/CIC
Note: CS DPUs include DPUa, DPUc, and DPUf.
To acquire the PS DPU load, you can evaluate

the percentage of busy PDCHs.
PS DSP: The definition of the counter is as follows:
If PS DPUs are insufficient, some packet PS DPU load = [AS9204: Average Number of PDCH Channel Expand the capacity of
data channels (PDCHs) cannot be activated, PDCHs Occupied per BSC]/ [PS DPU Activation Rate PS DPUs.
and PS services cannot access the network. specification x Number of PS DPUs]
Capacity expansion threshold: [PS DPU load] >
70%

Equipment Capacity (Continued)
Impact of Insufficient Optimization
Evaluation Method KPI
Capacity Scheme
The following counters are used to monitor the user plane load of interface
boards:
[AR9705a: Average Forwarding Ratio of Interface Boards]: This counter
measures the average forwarding load of interface boards within the current Balance the site
Interface board load: load between
statistical period. Forwarding load refers to the ratio of the actual forwarding rate
When the interface different interface
to the maximum designed forwarding rate for the interface board. It reflects the
board load is too high, boards.
operational load and quality of the interface board within a statistical period. Assignment
messages may be
[AR9700: Average CPU Usage of the INT]: This counter measures the average Success Rate
discarded and the
CPU usage of the INT subsystem within the current statistical period. It reflects CSSR
quality of PS and CS
the CPU load and operational quality of the INT subsystem within a statistical
services may be
period.
affected. Expand the
AR9705a: Average Forwarding Ratio of Interface Boards > 70% capacity of
or interface boards.
AR9700: Average CPU Usage of the INT > 70%
The following counters are used to monitor the inter-rack communication load on
a BSC:
Inter-rack Inter-Rack Resource Utilization During Traffic Peak
communication Inter-Rack Resource Utilization During Traffic Peak = [HR9732a]/Inter-Rack
resources: When the Bandwidth x 100%
inter-rack Average Inter-Rack Resource Utilization
Assignment Balance site load
communication Average Inter-Rack Resource Utilization = [AR9732a]/Inter-Rack Bandwidth x
Success Rate between
capacity is close to the 100%
CSSR subracks and
overload threshold, the Inter-Rack Packet Loss Rate
PDCH Bearer reduce inter-rack
quality of PS and CS Inter-Rack Packet Loss Rate = [R9732a]/[R9732b] x 100%
Rate message
services is affected, Capacity expansion threshold:
forwarding.
network KPIs When the value of Inter-Rack Resource Utilization During Traffic Peak exceeds
deteriorate, and the 60%, an alarm should be triggered and analysis should be started.
system performance When the value of Average Inter-Rack Resource Utilization exceeds 40%, an
becomes unstable. alarm should be triggered and analysis should be started.
When the value of Inter-Subrack Packet Loss Rate exceeds 0.01%, an alarm
should be triggered and analysis should be started.

Contents
 Capacity
 Equipment
 Um Interface
 Transmission
 Cases

Um Interface — Overview
Resource Type Capacity Monitoring Counter Capacity Expansion

Threshold
The value of Reuse Rate of
Frequency must be larger
than 9.
Frequency Reuse Rate of Frequency
If the value is below 9,
serious network interference
will occur.
PCH Overload Rate of Paging 2%
SDCCH Congestion Rate on SDCCH 2%
TCH Congestion Rate on TCH 2%
PDCH Congestion Rate on TBF 3%

Frequency
Impact of Insufficient
Evaluation Method KPI Optimization Scheme
Capacity
GSM frequency resources are
Increase the half-rate
evaluated based on the
channel percentage and
frequency reuse rate.
the capacity to address
voice quality
Formula:
Frequency: deterioration.
Reuse Rate of Frequency
Insufficient frequency Enable the VAMOS
= Total number of available Interference
resources lead to function (depending on
ARFCNs/Number of TRXs of Band
serious network the penetration rate of
the cell Measurement
interference, which VAMOS terminals).
makes capacity Deploy the 1800 MHz
expansion impossible. band to build a dual-
An appropriate value of Reuse
band network and
Rate of Frequency must be
expand the frequency
larger than 9.
capacity.

PCHs
Capacity Scheme
The following counters are used to monitor the
PCH load:
[RL3188: Overload Rate of Paging]: This counter Optimize PCH
measures the paging overload rate. It reflects the parameter settings.
PCHs:
percentage of PCH overload times on the Abis
PCHs are used for paging
interface (including CS and PS services) to the
MSs that are being called.
total number of paging times (including CS and
MSs on a GSM network are Enable the multi-
PS services).
paged by location area CCCH function.
[RL3188: Overload rate of paging]: This counter
code (LAC). In an LA, the
reflects the percentage of the current number of
following problems occur Paging Success
paging times to the total PCH paging capability.
when the actual paging Ratio
When the value of [RL3188: Overload rate of
volume exceeds the Overload Rate of
paging] is below 2% and the network is growing,
theoretical PCH paging Paging
monitor the counter in a long period of time.
capacity:
Formula:
1. PCH congestion
PCH overload = ([A330: Delivered Paging
2. Paging overload
Messages for CS Service] + [A331: Delivered
3. Low paging success Split LAs.
Paging Messages for PS Service])/PCH capability
rate
x 100%
4. Poor user experience
during service access
[RL3188: Overload Rate of Paging] > 2% or [PCH
Overload > 70% and the network is growing.

SDCCHs
Optimization
Impact of Insufficient Capacity Evaluation Method KPI
Scheme
The [RR370: Congestion Rate on

SDCCH per CELL (due to Busy)] counter Enable dynamic
SDCCHs:
is used for monitoring SDCCHs. SDCCH adjustment.
When SDCCHs are insufficient,
[RR370: Congestion Rate on SDCCH per If SDCCHs remain
SMS services are unavailable,
Cell (due to Busy)]: This counter congested when the
MSs cannot access the network [Congestion
measures the percentage of SDCCH dynamic SDCCH
when initiating calls, or the called Rate on
application failures due to unavailability adjustment function is
MSs do not respond. SDCCHs are SDCCH per Cell
to the total number of SDCCH application enabled or SDCCHs,
most important to services and (due to Busy)]
attempts. It reflects SDCCH conflicts TCHs, and PDCHs
therefore their capacity must be CSSR
caused by insufficient SDCCH resources are simultaneously
guaranteed with the highest priority.
due to various factors. congested, expand
To this effect, dynamic SDCCH
Capacity expansion threshold: the capacity of TRXs.
adjustment must be enabled.
[RR370: Congestion Rate on SDCCH per
Cell (due to Busy)] > 2%

TCHs
Capacity Scheme
Enable the half-rate
[K3045: Congestion Rate on TCH
channel function and
(All Channels Busy)] is used for
decrease the
monitoring the TCH load.
threshold for enabling
the half-rate channel
K3045: Congestion Rate on TCH
TCHs: function (half-rate
(All Channels Busy): This counter
Insufficient TCHs lead to CS voice quality is
measures the TCH congestion rate. Congestion Rate on TCH
service access failures, slightly poorer than
It reflects the percentage of TCH (All Channels Busy)
which has a serious negative full-rate voice quality).
application failures due to CSSR
impact on user experience.
unavailability to the total number of
Expand the capacity
TCH application attempts.
of TRXs.
Deploy new sites.
[K3045: Congestion Rate on TCH
(All Channels Busy)] > 2%

PDCHs
Capacity
Possible causes of insufficient PDCHs are as
follows:
1. Too low PDCH percentage threshold in the
cell: Only a few TCHs can be converted into
PDCHs. As a result, PDCHs are insufficient,
The TBF congestion rate is while many TCHs are idle. In this case, you
used to monitor the PDCH load. Percentage of PDCH can increase the PDCH percentage
TBFs are data blocks Application Failures threshold to resolve the problem.
transmitted on PDCHs for PS (PDCH Percentage 2. Total channel resources in the cell are
services. TBF congestion rates Threshold) = [R9395: insufficient. During busy hours, both TCHs
are classified into uplink and Number of PDCH and PDCHs cannot meet service
downlink TBF congestion rates. Application Failures for requirements. In this case, you need to
PDCHs: Generally, the downlink traffic Cell PDCH Ratio Thresh]/ optimize other parameters or expand the
[R9393: Number of PDCH capacity of TRXs. To differentiate the cause
Insufficient PDCH of PS services is larger than
Application Attempts]
affects GPRS/EDGE the uplink traffic. Therefore, the of insufficient PDCHs, check the following
service rates and lead to downlink TBF congestion rate Percentage of PDCH counters:
PS service access is the focus of PDCH Application Failures (TCH
Percentage of PDCH Application Failures
failures of some MSs. monitoring. Unavailable) = [R9394: (PDCH Percentage Threshold) = [R9395:
Number of PDCH Number of PDCH Application Failures for Cell
Capacity expansion threshold: Application Failures Due PDCH Ratio Thresh]/ [R9393: Number of PDCH
Uplink TBF congestion rate > to No Convertable TCHs]/ Application Attempts]
3% R9393: Number of PDCH Percentage of PDCH Application Failures (TCH
or Application Attempts Unavailable) = [R9394: Number of PDCH
Downlink TBF congestion rate Application Failures Due to No Convertable
> 3% TCHs]/ R9393: Number of PDCH Application
Attempts
If the PDCH percentage threshold is too low,
increase the PDCH percentage threshold. If both
TCHs and PDCHs are insufficient, expand the
capacity of TRXs.

Contents
 Capacity
 Equipment
 Um Interface
 Transmission
 Cases

Transmission — Overview
Capacity
Resource Type Capacity Monitoring Counter Expansion
Threshold
RL9808: Transmission Bandwidth Usage of the MTP2 Link
TDM transmission resources
or 40%
on the A interface (signaling)
RL9809: Receiving Bandwidth Usage of the MTP2 Link
Percentage of Busy Circuits on the A Interface 70%
on the A interface (service)
Percentage of Busy Circuits on the Ater Interface 70%
on the Ater interface
RL9608: Uplink Bandwidth Usage of the BC
Transmission resources on
or 80%
the Gb interface
RL9610: Downlink Bandwidth Usage of the BC
Flex Abis mode:
RR2752: Congestion Rate of Dynamic Resource
Assignment (16 kbit/s)
3%
or
TDM transmission resources RR2751: Congestion Rate of Dynamic Resource

on the Abis interface Assignment (8 kbit/s)
Non-Flex Abis mode:
Idle Abis Timeslot Application Failure Rate (Non-Flex Abis 3%
Mode)

Transmission — Overview
Capacity Expansion
Resource Type Capacity Monitoring Counter
Threshold
Receiving Bandwidth Requirement/Allocated
Transmission Bearer Bandwidth
Bearer or 70%
bandwidth Transmission Bandwidth/Allocated Transmission Bearer
Bandwidth
[T7414: Mean Receive Rate of an IP Path at the IP Layer]

/Configured IP Path Receiving Bandwidth
IP path or 70%
bandwidth [T7411: Mean Transmit Rate of an IP Path at the IP
Layer] /Configured IP Path Transmission Bandwidth
Interface
[Bandwidth Sum of All Physical Interfaces of Interface
board 70%
Boards]/[Physical Interface Bandwidth]
bandwidth

Transmission (TDM)
Capacity Scheme
MTP2 link bandwidth usage counters are used to monitor the SS7 load
on the A interface.
Signaling System 7 RL9808: Transmission Bandwidth Usage of the MTP2 Link: This RL9808:
(SS7) bandwidth: counter measures the percentage of the actually used bandwidth of Transmission
Too heavy SS7 load the MTP2 link to the configured bandwidth within a measurement Bandwidth Usage of
leads to congestion, period. The value of this counter reflects the MTP2 link usage. the MTP2 Link
Expand the SS7
packet loss, and RL9809: Receiving Bandwidth Usage of the MTP2 Link: This counter
bandwidth.
abnormal signaling measures the percentage of actually used bandwidth of the MTP2 link RL9809: Receiving
procedures and affects to the configured bandwidth. The value of this counter indicates the Bandwidth Usage of
the connection of CS MTP link usage. the MTP2 Link
services. RL9808: Transmission Bandwidth Usage of the MTP2 Link > 40%
or
RL9809: Receiving Bandwidth Usage of the MTP2 Link > 40%
CICs on the A The percentage of busy circuits on the A interface is used for
interface: monitoring the traffic load on the A interface.
Insufficient circuits on Percentage of Busy Circuits on the A Interface = [AL0055: Mean
Expand the
the A interface lead to Number of Busy Circuits on the A Interface]/[AL0055: Mean Number of A Interface
transmission
circuit assignment Busy Circuits on the A Interface + AL0054: Mean Number of Idle Assignment Success
resources on the
failures and voice call Circuits on the A Interface] Rate
A interface.
setup failures,
seriously affecting Capacity expansion threshold:
user experience. Percentage of Busy Circuits on the A Interface > 70%
The percentage of busy circuits on the Ater interface is used for
CICs on the Ater
monitoring the traffic load on the Ater interface.
interface:
Percentage of Busy Circuits on the Ater Interface = [AL125A: Mean
Insufficient circuits on
Number of Busy Circuits on the Ater Interface]/[AL1259: Mean Number Expand the
the Ater interface lead A Interface
of Idle Circuits on the Ater Interface + AL125A: Mean Number of Busy transmission
to circuit assignment Assignment Success
Circuits on the Ater Interface] resources on the
failures and voice call Rate
Capacity expansion threshold: Ater interface.
setup failures,
Percentage of Busy Circuits on the Ater Interface > 70%
seriously affecting
No counters are available for monitoring OMLs/RSLs on the Ater
user experience.
interface.

Transmission (TDM)
Capacity Scheme
Transmission resources on
In Gb over FR mode, the bandwidth usage of the BC is used for
the Gb interface:
monitoring the traffic load on transmission resources on the Gb
The Gb interface is between Expand Gb
interface.
the BSC and SGSN. transmission
Capacity expansion threshold: Average PDCH Rate
Insufficient Gb transmission resources and add
[RL9608: Uplink Bandwidth Usage of the BC] > 80%
resources lead to low licenses.
or
GPRS/EDGE service rates or
[RL9610: Downlink Bandwidth Usage of the BC] > 80%
even access failures.
In Flex Abis mode, all Abis TMD timeslots of each BTS are
dynamically assigned. When a PS or CS service request is
Transmission resources on Average PDCH rate:
initiated, Abis timeslots are assigned in real time according to
the Abis interface (Flex RR2752: Congestion
actual requirements. In this mode, Congestion Rate of Dynamic
mode): Rate of Dynamic
Resource Assignment is used for monitoring the traffic load on
The Abis interface is between Resource Assignment Expand Abis
transmission resources of the Abis interface.
the BTS and BSC. (16 kbit/s) transmission
Insufficient Abis transmission RR2751: Congestion resources.
RR2752: Congestion Rate of Dynamic Resource Assignment (16
resources lead to poor user Rate of Dynamic
kbit/s) > 3%
experience and access Resource Assignment
or
failures. (8 kbit/s)
RR2751: Congestion Rate of Dynamic Resource Assignment (8
kbit/s) > 3%
In non-Flex Abis mode, Abis timeslots, except idle timeslots,
always map TCHs and PDCHs of the BTS one to one. When the
Transmission resources on capacity of TCHs and PDCHs is expanded, the capacity of Abis
the Abis interface (non-Flex timeslots is expanded simultaneously. Therefore, you can use the
mode): idle Abis timeslot application failure rate to monitor the usage of
Average PDCH rate: Expand Abis
In non-Flex mode, insufficient idle timeslots in non-Flex Abis mode.
The percentage of high transmission
Abis transmission resources Idle Abis Timeslot Application Failure Rate (Non-Flex Abis Mode)
coding rates for EDGE resources.
lead to low PS service rates = [R9109: Number of Unsuccessful Application Attempts of Abis
services is low.
and difficulty in improving the Timeslot Because of No Idle Timeslot]/[R9101: Number of
coding rate. Some MSs even Application Attempts of Abis Timeslot]
cannot access the network. Capacity expansion threshold:
Idle Abis Timeslot Application Failure Rate (Non-Flex Abis Mode)
> 3%

Transmission (IP)
Capacity
IP path bandwidth:
The receiving and transmission rates of IP paths are used to
Insufficient IP path bandwidth 1. Analyze whether the
monitor bandwidth resources.
leads to tight control over configured IP path
service access, PS service bandwidth is too small.
[T7414: Mean Receive Rate of an IP Path at the IP
access failures, low CS rate, N/A If the configuration is
Layer/Configured Receiving Rate of the IP Path] > 70%
and poor voice quality. inappropriate, increase
[T7411: Mean Transmit Rate of an IP Path at the IP
Layer/Configured Transmission Rate of the IP Path] > 70% the IP path bandwidth.
2. Analyze whether the

interface board is
overloaded. If the load
Physical bandwidth of
is too heavy, adjust the
interface boards:
IP path configuration of
Insufficient bandwidth leads Capacity expansion threshold:
the interface or balance
to tight control over service [Bandwidth sum of all paths to the physical interface of the
N/A the load between the
access, PS service access interface board]/[Physical interface bandwidth] > 70%
interface board and
failures, low CS service rate,
other interface boards.
and poor voice quality.
3. Analyze whether the
bandwidth requirement
and the actually
assigned bandwidth for
Transmission bearer the transmission bearer
bandwidth: are appropriate. If the
[Transmission bandwidth of interfaces]/[Bandwidth assigned
Insufficient bandwidth leads bandwidth assigned to
to the bearer network] > 70%
tight control over service the transmission bearer
or N/A
access, low PS service rate, is insufficient, apply for
[Receiving bandwidth of interfaces]/[Bandwidth assigned to
CS service access failures, expansion of the
the bearer network] > 70%
and poor voice quality. capacity of the bearer
network.

Contents
 Capacity
 Capacity Evaluation and Optimization
 Equipment
 Um Interface
 Transmission
 Cases

Equipment Capacity Expansion: XPU Overload in Office M
Avg Max Qty of Qty Adjust SS7 links or
Symptom: Board CPU CPU Qty of Qty in SS7 Qty of of TRXs depending on
Subrack Type CPU Usage Usage TRXs Excess Links Sites TRXs actual situations.
3 BMs + 2 TCs were configured for Office M. During
XPUM 0 34.469 54 0 0 1. Adjust SS7
the peak hour (06:00–07:00), the traffic reached 8400
XPUM 1 58.089 88 66 0 1 signaling links:
Erl/h. During the period between 06:38 and 06:55, 47
Shift some SS7
CPU overload alarms were triggered. XPUM 2 57.808 91 69 3 1
signaling links of
XPUT 0 49.227 78 70 4 0
Analysis: subracks 0 and 2
XPUT 1 49.631 77 70 4 0
to CPU0s of
Analyze the average usage of each CPU and adjust XPUT 2 46.306 73 67 1 0
subracks 0 and 2.
the distribution of LAPD links and SS7 links within
0 XPUT 3 46.945 73 68 2 0 25 410 2. Adjust TRXs:
each subrack and between subracks to balance the
XPUM 0 28.365 47 0 0 Select the sites to
load between CPUs. If the adjustment does not work,
XPUM 1 38.059 65 61 -5 0 which TRXs under
expand the capacity.
XPUM 2 43.363 72 66 0 0 CPU1 and CPU2
Conclusion: of XPUMs in
XPUT 0 43.533 72 62 -4 0
According to the configuration data analysis, the XPUT 1 36.749 60 65 -1 0
subracks 0 and 2
number of TRXs carried by each CPU is nearly the XPUT 2 45.239 71 61 -5 0

belong. The
same. CPU1 and CPU2 of XPUMs in subracks 0 and 2 1 XPUT 3 31.138 56 64 -2 0 25 379
system assigns
carry SS7 signaling links at the same time. As a result, TRXs of the sites
XPUM 0 36.633 57 0 0
their load is rather heavy. The maximum CPU usage to CPU1/CPU2 of
XPUM 1 62.828 94 71 5 1
hit around 90%. the XPUM in
XPUM 2 60.902 92 63 -3 1 subrack 1 and
Solution: CPU0/CPU1/CPU
XPUT 0 49.355 80 64 -2 0
Adjust the homing of sites to balance the XPU load. XPUT 1 50.15 78 69 3 0 2/CPU3 of the
XPUT.
Adjust the homing of SS7 signaling links to balance the XPUT 2 51.186 80 73 7 0
Select sites according
XPU load.
to the following criterion:
Add XPUs. Reduce 10% CPU
usage by adjusting
2 XPUT 3 50.723 83 67 1 0 27 407 every 100 Erl traffic.

Equipment Capacity Expansion: CS DSP
Insufficiency in Office T
Symptom:
The call setup success rate fell in Office XXX of Country XXX. Large number of assignment
failures due to equipment failures occur on the A interface.
Analysis:
1. Check whether boards and equipment are faulty by analyzing alarms.
2. Check the cable connection of the interface and whether any crossed pair connections exist.
3. Analyze whether resources for voice calls are sufficient.
Conclusion:
According to the detailed analysis, no equipment fault alarm occurred. No crossed pair connection
existed. Circuits of all interfaces were sufficient. Generally DSPs were sufficient. However, DPUa
boards configured for different TC subracks were uneven. Some DSPs were seriously overloaded.
As inter-subrack DSP sharing was not supported, assignment failures occurred when DSP
resources were unavailable for calls assigned to the second TC subrack.
Solution:
Balance the configured number of DPUa boards between TC subracks.

Equipment Capacity Expansion: Large Number of Assignment
Failures Due to Insufficient Inter-Rack Resources
Symptom:
Large number of assignment failures occurred occasionally on the BSC of an office during busy hours. During idle
hours, however, the BSC worked properly. During busy hours, the traffic increased drastically on occasion.
Analysis:
Assignment failures are usually caused by equipment faults.
Check whether circuits of the A and Ater interfaces are faulty.
Check whether the A interface, Ater interface, and DSPs are overloaded.
Check the inter-subrack TNU switching resource utilization.
Conclusion:
The switching capacity of the inter-subrack TNU is as follows: Each TNU cable consists of 4096 64 kbit/s links.
Among the 4096 64 kbit/s links, eight are used for system monitoring and 4088 are used for service switching,
which are generally sufficient for use. According to the detailed analysis, the service volume of the BSC was large.
CS services used lots of inter-subrack resources. PS cells were assigned disorderly. Many PS cells of subrack 2
were assigned to DPUs of subrack 0, which also used inter-subrack switching resources. Many services adopt high
coding rates, which used much more inter-subrack resources. When the switching volume of CS and PS services
in subrack 2 exceeded 8176 (2 x 4088), no inter-subrack resources were available for subsequent calls and
assignment failures occurred.
Solution:
Adjust the inter-subrack site configuration to reduce inter-subrack switching.
Add Ater interfaces for subrack 2 to reduce inter-subrack switching.

Transmission Capacity Expansion: Low PS Service
Rate and Poor User Experience Due to Insufficient
Transmission Resources in Office V
Symptom:
To adapt to the fast development of PS services and the fast growth of traffic, the customer added PDCHs. A large
quantity of users still complained about the low service rate and poor experience. As a result, the customer thought
that Huawei equipment had performance defects.
Analysis:
Check usage of Um interfaces, transmission resources, interface boards, and DSPs for PS services.
Conclusion:
According to the comprehensive analysis, Um interfaces were sufficient, network interference was at a normal level,
the coding rate of PS services was properly set, and no PDCH congestion occurred. Transmission resources on
the Abis interface, however, were seriously congested. During busy hours, the congestion of Abis TDM timeslots
exceeded 15%, which seriously affected the service rate of PDCHs. Most PDCHs carried services at a low coding
rate due to insufficient Abis resources.
Solution:
Expand Abis transmission resources and increase the number of idle timeslots for the Abis interface.

Network Assurance During Major Events: Olympics,
UEFA Euro 2012, and HJJ
Network security and quality assurance during major events is one of the most important concerns of operators.
Huawei provides professional network assurance services during major events. It has successfully served operators
during the World Cup 2010, Saudi Arabia HJJ, UEFA Euro 2012, and 2012 Olympics, helping operators improve their
brand quality and increase their operation revenue. In addition, Huawei earned USD XXX thousand for offering related
professional services.
Resource capacity evaluation and optimization is key to network assurance during major events. Before each event,
the resource capacity is evaluated, predicted, and expanded based on the evaluation and prediction results, and the
load is balanced. This ensures network security, enhances the service absorption capability of the network, improves
user experience, and increases the operator's revenue.

Contents
 Capacity

Tool and Data Sources
Resource capacity evaluation is performed using the OMStar. Data sources
for evaluation of each type of resources are as follows:
Capacity Type Item Sub-item Data Sources

XPU BSC traffic statistics
Equipment DPU BSC traffic statistics
BSC
capacity Interface board BSC traffic statistics
Switching board BSC traffic statistics
Common PCH Traffic statistics and configuration data of the BSC
channel PCH Traffic statistics and configuration data of the BSC
Um interface
SDCCH Traffic statistics and configuration data of the BSC
capacity
Resource TCH Traffic statistics and configuration data of the BSC
PDCH Traffic statistics and configuration data of the BSC
Signaling Traffic statistics and configuration data of the BSC
TDM
Transmission Services Traffic statistics and configuration data of the BSC
capacity Signaling Traffic statistics and configuration data of the BSC
IP
Services Traffic statistics and configuration data of the BSC

How to Use the Capacity Evaluation Tool
The procedure for using the tool is as follows:

1. Create a project.
2. Import traffic statistics and configuration data.
3. Select the resource capacity evaluation and optimization module.
4. Select the target BSC and resource items and execute the report.
For details about the method of using the tool, see the related OMStar guide.

Report Generation Formats
Service
Sub-function Evaluation Item Remarks
Module XPU planning
XPU evaluation
Board Board planning DPUX planning
DPUX evaluation
evaluation
DPUP evaluation DPUP planning
Abis interface evaluation Abis interface planning
(TDM)
This module
Abis interface evaluation A interface planning (TDM) evaluates the
(IP_over_E1) This
Interface current
Abis interface evaluation module A interface planning (IP)
Resource planning resource
Resource Interface (IP_over_FE) evaluates
planning Gb interface planning requirements
evaluation evaluation A interface evaluation (TDM) the current
and future
load of
A interface evaluation (IP) Ater interface planning resource
resources.
requirements.
Gb interface evaluation As-is RF planning
Ater interface evaluation RF planning
To-be RF planning
RF load evaluation
RF evaluation LAC planning LAC planning
Cell channel evaluation
Planning
LAC evaluation LAC evaluation Planning result summary
summary
Click the evaluation item link in the resource capacity evaluation report generated by the OMStar.
Detailed analysis results of each item are displayed. In the resource capacity planning part, the
OMStar automatically generates the corresponding capacity expansion and adjustment solution. It
provides guidance for the planning and optimization of network resource capacities.

Contents
 Capacity

Standard Operating Procedure
 Operation 1 Check whether the problem is related to resources and identify the possible related
resource.
 Operation 2 Collect data for evaluation of the target resource.
 Operation 3 Analyze data and generate an evaluation report using the OMStar.
 Operation 4 Check whether the capacity is restricted. If yes, generate the list of restricted cells. If
the problem is caused by restricted capacity, go to operation 5. Otherwise, submit the problem to
the R&D department for analysis.
 Operation 5 Provide optimization means or capacity expansion means according to the
configurations on the live network.
 Operation 6 Implement the optimization solution and evaluate the optimization effect. If the
congestion is mitigated or eliminated, promote the related service or sell related products.
Otherwise, submit the problem to the R&D department for analysis.

Where to Obtain the Tool
Tool Function Link R&D

Contact
Person
OMStar Resource http://support.huawei.com/support/p Zheng Ke
capacity ages/editionctrl/catalog/ShowVersio (employee
evaluation nDetail.do?actionFlag=clickNode&n ID:
and ode=000001556049&colID=ROOT 00213016)
optimization WEB|CO0000000065

Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Page 40
Contents
 Coverage
 Principles
 Troubleshooting Process
 Cases

Page 41
Overview
 Definition: In wireless communication systems, coverage is a statistical concept.
That a service has coverage in a position means that the strength and quality of
signals received by MSs in the position meet service requirements in 99% of time.
 Coverage is divided into uplink coverage and downlink coverage.

 Uplink coverage: MSs transmit and BTSs receive signals. Ensure that the transmit power
of an MS can be detected by a BTS and the signal quality meets service requirements. In
terms of quality difference, attention is usually paid to RXQUAL_ 6 and RXQUAL_7
generated by the low uplink level (less than -90 dBm).
 Downlink coverage: BTSs transmit and MSs receive signals. Ensure that the transmit
power of a BTS can be received by an MS and the signal quality meets service
requirements. In terms of quality difference, attention is usually paid to RXQUAL_ 6 and
RXQUAL_7 generated by the low uplink level (less than -90 dBm).

Typical Coverage Scenarios
By service distribution
By wireless propagation environments
Scenario Characteristics Service Distribution
Scenario Description
The terrain is flat, with densely distributed buildings. Lots of high-rises Such areas are in the center of 1. Densely populated
(over 30 floors) exist in the area, whose average height exceeds 50 m. super large cities, with a small areas, constituting hot
Dense urban area and densely distributed spots
The spacing between buildings is small and irregular. Most streets in
area (CBD) buildings. Many business 2. High requirements on
the area are narrow. The population is very large and the majority of
people are in buildings within certain periods. A activities of the regions take the PS service rate
place here. Users frequently use 3. Key areas for PS
The terrain is flat, with densely distributed buildings. The average mobile communications and service development
Dense urban
height of buildings ranges from 25 m to 30 m. The spacing between have high requirements on the 4. High requirement on
area (residential
buildings is small and irregular, averaging 10 m to 20 m. Many streets quality of PS services. service quality
area)
(not arteries) in the areas are narrow with a dense population.
Such areas are in the center of cities. The height of buildings is Such areas feature prosperous 1. Densely populated
High-density industries and businesses, all areas, with a high traffic
moderate, averaging about 20 m. The average spacing between
common urban necessary transport facilities and volume
buildings is the same as the height of buildings. There is open and
area infrastructure, and many arteries, 2. PS services with a
green space within the area. B
with a high urbanization level, moderate rate
Such areas are on the edge of cities. Buildings are low and scattered, dense populations, fast 3. High requirement on
Low-density
with an average height of 15 m – 20 m. The average spacing between economic development, and high service quality
common urban
buildings exceeds the average height of buildings. Streets in the areas income per capita.
area
are wide. There are parks and large green space.
Such areas are on the border between cities and rural areas. Such areas feature well 1. Small service volume
Buildings are scattered, with an average height of 10 m and an developed businesses and quite 2. Only low-rate PS
Suburban area a high level of urbanization, with services provided
average building interval of 30 m – 50 m. Streets in the area are wide,
with lots of plants or open space. C many enterprises, convenient
transportation, and middle-level
In such areas, buildings are very scattered. Most buildings are economic development and
Rural area bungalows, with an average height of about 5 m. There are large income per capita.
areas of open space, farmlands, plants, and roads.
Straight road Straight roads and highways. Two types of areas are included: 1. The traffic volume is
1. Main roads and railways very small.
Sea/lake Sea or lake surface, characterized by vast open space and no D 2. Less developed rural and 2. The purpose of site
surface obstacles within the line of sight. mountainous areas deployment is to provide
network coverage.

Page 43
Coverage Level Requirements
 Outdoor coverage
 Indoor coverage
 Vehicle coverage
–90 dBm –70 dBm

Building penetration loss: 20 dB Vehicle penetration loss: 8 dB
Clutter Type Description

Outdoor Select this clutter model for rural and open coverage.
Indoor Select this clutter model for dense urban, urban, or suburban area coverage.
In a vehicle Select this clutter model for road coverage.
Dense wood Select this clutter model for special areas, such as forests and parks with vast forests.
Water surface Select this clutter model for special areas, such as lakes and rivers.

Coverage Probability
 Area coverage probability: percentage of areas
where the received signal strength (RSS) exceeds
the RSS threshold to the total area.
 Edge coverage probability: percentage of the period
when the RSS exceeds the RSS threshold on the
edge of the coverage area.
Recommended values for service rates and area

Mapping between area coverage probabilities and edge coverage coverage probabilities in various typical scenarios
probabilities in various typical scenarios
Outdoor Indoor
Area Type Service
Coverage Coverage
Area Coverage DUA A High-speed PS services 98% 88%
50% 60% 75% 80% 85% 90% 91% 92% 93% 94% 95% 96% 97% 98% 99% 100%
Probability DUA B High-speed PS services 98% 85%
DUA 20% 30% 49% 57% 66% 75% 77% 79% 81% 84% 86% 89% 91% 94% 97% 100% DUA C CS services 90% 75%
Urban area B Low-speed PS services 95% 85%
Urban 20% 30% 49% 57% 66% 75% 77% 79% 81% 84% 86% 89% 91% 94% 97% 100%
Urban area C CS services 95% 80%
Edge
Coverage Suburban 20% 30% 49% 57% 66% 75% 77% 79% 81% 84% 86% 89% 91% 94% 97% 100% Suburban area C CS services 90% 75%
Probability Rural area C CS services 90% 75%
Rural 17% 27% 46% 54% 63% 73% 76% 78% 80% 82% 85% 88% 90% 93% 96% 100% Rural area D CS services 75% N/A
Highway or national road CS services 98% N/A
Highway 6% 14% 32% 50% 51% 64% 66% 69% 72% 75% 79% 82% 86% 90% 95% 100% Provincial road, key
passenger railway, or main CS services 90% N/A
fairways
Common roads, railways,
CS services 80% N/A
or fairways

Page 45
Receiver Sensitivity
 Receiver sensitivity refers to the minimum required strength of

signals received by a device. The receiver sensitivity may vary
from device to device.
Transmitters of different BTSs vary with vendors.
Receiver sensitivity of an MS: –102 dBm Receiver sensitivity of a vehicle-mounted

station: –105 dBm

Page 46
Uplink/Downlink Balance
Uplink/downlink balance means that the maximum loss allowed on the downlink equals that allowed on
the uplink.
Transmit power at the top of the BTS cabinet (TOC) – Receiver sensitivity of the MS = Power of the MS +
Diversity gain – Receiver sensitivity of the BTS (+ Gain generated by the TMA)
When the difference between the uplink loss and downlink loss is 2 dB – 3 dB, it is deemed that the
uplink and downlink balance is achieved.
No received
signals
The uplink loss is bigger than the The downlink loss is bigger than
downlink loss. the uplink loss. Uplink access
is impossible.
The coverage scope is determined by the party whose signal strength is poorer.

Page 47
Impacts of Coverage Changes on Network
Performance
 When the coverage becomes worse, the counter of coverage level (idle state) deteriorates significantly, which has a direct
impact on the level coverage percentage during drive tests (DTs).
 According to the uniform requirements on the edge coverage level, the volumes of coverage deterioration and reduction
map the traffic decrease within the area (especially users under intensive coverage).
 Coverage shrinking changes the trigger time of some handover types and has an impact on the quantity and quality of
available neighboring cells. Therefore, this coverage change has a direct impact on handover counters and an indirect
impact on other counters, such as the call drop rate.
 Coverage holes increase when the coverage shrinks. In coverage holes, calls cannot be originated. This has little impact
on traffic statistics but affects the actual user experience. As a result, user complaints increase.
 Coverage shrinking also reduces the strength of wanted signals. As a result, the C/I deteriorates (C/I = Strength of wanted
signals/Strength of interference signals). It also has an indirect impact on other performance counters.
 Coverage shrinking has an impact on the counters that are sensitive to coverage + C/I changes, such as the PS
throughput.
The figure shows the mapping
between the percentage of poor
downlink coverage areas and call
DL Poor Cover Rate VS CDR
1.20%
drop statistics at a few offices. When
the percentage of poor coverage
1.00%
areas exceeds a certain threshold,
the call drop rate in the statistics no
0.80%
longer deteriorates. That is because
MSs cannot originate calls in this
0.60%
case. It has little impact on the traffic
statistics, but the actual user
0.40%
experience is poor. As a result,
more complaints are received.
0.20%
Only a few sampling points are used.
Therefore, this figure serves only as
Zone One Zone Two
0.00%
a reference for trend analysis. The 0.00% 5.00% 10.00% 15.00% 20.00% 25.00% 30.00% 35.00% 40.00%
actual threshold of each office may
be different. Downlink coverage < Percentage of –90 dBm coverage areas vs. CDR

Coverage Influencing Factors
Equipment Service
capability rate
Coverage quality
C I
Signal Network
strength interference
Transmit power Path loss Handover timeliness Internal interference External interference
Parameter Parameter problems

problems (handover)
Site Engineering Terrain Band Equipment CCI and ACI External interference,
(transmit Missing neighboring
density parameter interference such as CDMA
power and cells
network interference
power control Insufficient Congestion Frequency
Engineering or invalid equipment
parameters) Inappropria sites. When "Islands" caused by Equipment inter-
Insufficient parameter planning …
Equipment te the coverage overlaps modulation problems,
number of problems
faults networking coverage is interference coverage
sites (inappropriat
Uplink/downlin scheme, constant, Repeater overlap, and
e site height,
k imbalance such as 1800 GHz interference traffic increase
downtilt,
Antenna poor indoor supports
azimuth,
system coverage more sites
antenna gain
or poor than 900
and loss, or
highway MHz.
antenna type)
coverage
Possible root causes of coverage problems are as follows: equipment, parameter settings, handover,
networking solution, and interference.

Contents
 Coverage
 Principles
 Cases

Page 50
Troubleshooting Process
 Step 1 Confirm coverage information.
 Confirm the scenario: swap, expansion, upgrade, or existing site optimization.
 Focus on power, parameter mapping, and engineering quality for site swapping.
 Pay attention to the combiner loss for capacity expansion.
 Check whether parameters are changed for site upgrade.
 Analyze factors that influence network coverage for site optimization.
 Confirm the symptom: Coverage problems can be detected through customers' complaints,
traffic statistics, and DT data.
 Confirm the object: top cells of the object whose coverage is abnormal or an NE.
 Step 2 Perform required operations.
 Perform the following required operations for site swapping: power mapping, handover
configuration/alarms, antenna/channel quality, parameter mapping check, comparative
traffic analysis, and DT analysis.
 Perform the following required operations for site optimization: missing neighboring cells,
"islands" caused by coverage overlaps, handover timeliness or power control, intensive
coverage, MR-based geographic analysis, and DT analysis.
 Step 3 Perform issue closure and export the summary report.

Troubleshooting Trigger Conditions(1)
1. Identifying coverage problems on the entire network or a network segment
 In general scenarios
Coverage in an area or a cell is weak if the uplink or downlink level is low and the
percentage of low quality links is equal to or greater than 3%. Perform actions
required to identify coverage problems.
Counter Traffic Measurement Formula

Low downlink level (level 100% X ([S4106B] + [S4107B] + [S4116B] + [S4117B] + [S4126B] + [S4127B] + [S4106D] + [S4107D]
0 to 2)and percentage of + [S4116D] + [S4117D] + [S4126D] + [S4127D])/ [CS410B] + [CS411B] + [CS412B] + [CS413B] +
low quality links (level 6 [CS414B] + [CS415B] + [CS416B] + [CS417B] + [CS410D] + [CS411D] + [CS412D] + [CS413D] +
to 7) [CS414D] + [CS415D] + [CS416D] + [CS417D] )
Low uplink level (level 0 100% X ([S4106A] + [S4107A] + [S4116A] + [S4117A] + [S4126A] + [S4127A] + [S4106C] + [S4107C]
to 2)and percentage of low + [S4116C] + [S4117C] + [S4126C] + [S4127C])/([CS410A] + [CS411A] + [CS412A] + [CS413A] +
quality links (level 6 to [CS414A] + [CS415A] + [CS416A] + [CS417A] + [CS410C] + [CS411C] + [CS412C] + [CS413C] +
7) [CS414C] + [CS415C] + [CS416C] + [CS417C])
 In replacement (or project restructuring) scenarios，

1) Compare the distribution of low uplink and downlink levels and the distribution of low
quality links before and after replacement or project restructuring. If levels and links
deteriorate, a coverage problem may occur. Perform actions required to identify coverage
problems.
2) Compare CS/PS traffic volume before and after replacement or project restructuring. If the volume
decreases considerably, perform actions required to identify coverage problems after other possible causes
are eliminated. Traffic
9000
Traffic 8000
Counter 7000
Volume 6000
5000
CS K3014：Traffic Volume on TCH 4000
3000
2000
AR9311:Average Number of 1000
PS 0
Occupied PDCHs
17:00
21:00
17:00
21:00
13:00
17:00
21:00
13:00
21:00
13:00
17:00
21:00
13:00
17:00
21:00
13:00
17:00
13:00
17:00
21:00
13:00
17:00
21:00
13:00
17:00
1:00
5:00
9:00
1:00
5:00
9:00
1:00
5:00
9:00
1:00
5:00
9:00
1:00
5:00
9:00
1:00
5:00
9:00
1:00
5:00
9:00
1:00
5:00
9:00
11/07/201111/08/2011 11/08/2012 11/08/2013 11/08/2014 11/08/2015 11/08/2016 11/08/2017 11/08/2018
求和项:K3014:TCH话务量求和项:K3034:半速率话务量求和项:全速率话务量

3) For weak coverage problems in the drive tests(DT), compare DT levels before and after replacement or
project restructuring. If levels deteriorate considerably, perform actions required to identify coverage
problems. Conduct DT in idle hours and service hours.
a) If both DTs in idle hours and service hours detect weak coverage, the weak coverage problem occurs. Note
that use Scanner to conduct a DT in idle hours to eliminate impact of reselection parameters for idle
hours.
b) If only the DT in service hours detects weak coverage, false weak coverage occurs due to improper
parameter configuration.
Comparison of
DT results in
idle hours
before and
after
replacement or
network
restructuring.
Figures on the
right shows
deteriorating
coverage.

2. The identification methods described in the previous two pages do not apply to
weak coverage on a single spot. For example, if call drops due to weak coverage
occur in a single spot, the weak coverage problem cannot be identified in level
distribution at the cell level. Therefore, when call drops occur, perform actions
required to identify weak coverage problems after other possible causes are
eliminated.

Required Actions for Troubleshooting Coverage Problems
Required Implementatio
No. Purpose and Requirements Output
Action n Condition
(1) Check whether any fault alarms are generated due to VSWR exceptions, unstable clock, intermittent
transmission, or TRX communication/wireless link faults. These alarms affect the transmission and reception
List of equipment fault alarms
performance. Check whether any cells with low TRX/channel usage exist. When such cells exist, traffic is
shifted to surrounding cells, which affects the performance of surrounding cells.
(2) Check whether the main and diversity receive levels of channels are normal and whether the List of cells with abnormal main and
configuration and performance of repeaters and TMAs meet corresponding requirements. diversity signals
Hardware/cha
Required (3) Check whether the antenna and jumper connectors are correctly connected, whether combiners function List of cells with incorrectly connected
nnel/antenna Mandatory.
Action 1 normally, whether the SWR is normal, and whether the antenna is aged. antennas
system check
(4) Check for uplink and downlink imbalance: When the path loss on the uplink varies greatly from that on Percentage of problematic cells with
the downlink (≥ 12 dB), the receive level is abnormal. unbalanced uplink and downlink traffic
(5) Check the transmit power:
(a) List of power mapping outputs
(a) Check whether the coverage shrinks due to not mapping power before the swap in swap scenarios or
(b) List of cells with abnormal power
combiner loss in capacity expansion scenarios.
configurations
(b) Check whether the power configuration is obviously abnormal in optimization scenarios.
Parameter/co
Required Check parameters, especially coverage parameters, such as static power level, access, maximum transmit List of parameters for network-wide
nfiguration Mandatory.
Action 2 power level of the MS, transceiving mode, and handover thresholds. check
check
(1) Find out cells whose neighboring cells are missing. When neighboring cells are missing, MSs cannot be
(1) List of missing neighboring cells of
handed over to the neighboring cells. As a result, MSs suffer quality deterioration caused by the low level in
problematic cells
the serving cell.
Handover
(2) Find out cells with poor coverage due to no handovers or delayed handovers. When the handover
Required exception and (2) List of parameters of problematic
Mandatory. algorithm or parameters are inappropriately configured, handovers will be delayed. As a result, MSs suffer
Action 3 coverage cells
quality deterioration caused by the low level in the serving cell.
overlap check
(3) Find out "island" cells caused by coverage overlaps. Cells become islands when coverage overlaps (3) List of "island" cells caused by
occur. In this case, handovers cannot be triggered and the quality deteriorates due to the low level. As a coverage overlaps and list of TA
result, call drops occur. samples
Optional. Service geographic observation of
Geographic Implemented when Locate the areas or scenarios where the coverage is abnormal accurately using the MR or DT data, analyze coverage quality deterioration
Required
coverage operations 1 to 4 fail poor-coverage areas by grid on a map, perform dedicated DTs or dial-up tests, and confirm the scope, corresponding to problematic cells
Action 4
analysis to resolve the symptom, and cause of the problem. Test and optimization results of areas
problem. with coverage quality deterioration
(1) Check the areas where the network coverage is abnormal and RF parameters, such as site density, site
Optional. RF check list
height, downtilt, and azimuth. Check whether the number of sites is abnormal or inappropriate.
RF and Implemented when
(2) Identify the scenarios to which the areas with abnormal coverage belong and check whether the
Required coverage operations 1 to 4 fail
coverage networking solution is obviously inappropriate.
Action 5 solution to resolve the Coverage scenario and scheme
Scenarios: dense urban areas, urban areas, suburban areas, rural areas, and special scenarios (indoor,
check problem. analysis
tunnel, sea surface, and high-speed railway)
Solutions: macro cell, macro + micro cell, repeater, and RRU.
Optional.
If the engineering adjustment workload is huge, the network coverage solution is complicated, or the
Required System Implemented for Coverage simulation results for
customer raises high requirements, use the simulation tool to formulate the adjustment solution and verify
Action 6 simulation engineering engineering adjustment
the effect.
adjustment.

Action1: Hardware/Channel/Antenna System Check
 Implementation condition: mandatory.
 Purpose: This is the basic check operation. It is used to check and rectify the basic faults that affect network coverage,
such as hardware faults, RF channel faults, or incorrect power configuration.
 Principles: Check the configuration of alarms, traffic statistics, and power to detect hardware and channel faults.
 Data sources, tools, and outputs:
Tools and Issue
Check Item Output Data Sources
Guides Closure
(1) Check whether any fault alarms are generated due to VSWR exceptions, unstable
clock, intermittent transmission, or TRX communication/wireless link faults. These alarms
List of equipment fault
affect the transmission and reception performance. Check whether any cells with low
alarms OMStar/FMA/
TRX/channel usage exist. When such cells exist, traffic is shifted to surrounding cells,
M2000
which affects the performance of surrounding cells.
(2) Check whether the main and diversity receive levels of channels are normal and Detection and
List of cells with abnormal Troubleshooti Exclude
whether the configuration and performance of repeaters and TMAs meet corresponding
main and diversity signals (1) Alarm logs ng of GSM the
requirements. RF Tunnel possibility
(2) Raw traffic statistics
(3) Check whether the antenna and jumper connectors are correctly connected, whether Faults： of
List of cells with incorrectly Principle + equipment
combiners function normally, whether the SWR is normal, and whether the antenna is
connected antennas Tools + faults and
aged.
Cases + power
Percentage of problematic Deliverables.p exceptions
(4) Check for uplink and downlink imbalance: When the path loss on the uplink varies pt and export
cells with unbalanced the
greatly from that on the downlink (≥ 12 dB), the receive level is abnormal. summary
uplink and downlink traffic
report.
(1) Power configuration before the
(5) Check the transmit power: (a) List of power mapping swap
(a) Check whether the coverage shrinks due to not mapping power before the swap in outputs (2) Actual TRXs, TOC, and combiner Power
swap scenarios or combiner loss in capacity expansion scenarios. (b) List of cells with and duplexer loss of typical sites mapping tool
(b) Check whether the power configuration is obviously abnormal in optimization abnormal power before the swap and OMStar
scenarios. configurations (3) Power configurations on the live
network
 Detailed procedure:
For details, see the Detection and Troubleshooting of GSM RF Tunnel Faults: Principle + Tools + Cases + Deliverables.

Action 2: Parameter Check (1)
 Purpose: Check parameters, especially coverage parameters, such as static power level, access, maximum
transmit power level of the MS, transceiving mode, and handover thresholds.
 Principles: Check whether parameter settings are appropriate by comparing the parameters with the baselines
and comparing parameter values before and after the swap. The parameters include 12 core parameters, 25
handover parameters, and 25 other parameters.
Data Sources Tools and Guides Output Issue Closure
List of parameter
(1) MML configuration file OMStar and PFMStudio Adjust
check results. This
(2) Intelligent parameter inappropriate
list contains cell
baselines, user-defined GSM Parameters Check: Check parameter
parameters that do
parameter baselines, or Rules + Tools + Cases + settings and
not meet baselines
parameter settings before the Deliverables.ppt generate the
and corresponding
swap (in swap scenarios) List of coverage parameters (focus) summary case.
causes.
 Detailed procedure
For details, see the GSM Parameters Check: Check Rules + Tools + Cases + Deliverables.

Action 2: Parameter Check (2) — Core Coverage Parameters
Baseline Baseline
Parameter ID Comments Parameter ID Comments
Value Value
ULEDGETHRES 10 Handover delay leads to poor coverage. DATASTRFLTLEN 6 Handover delay leads to poor coverage.
DLEDGETHRES 20 Handover delay leads to poor coverage.
DATAQUAFLTLEN 6 Handover delay leads to poor coverage.
HOTHRES 25 Handover delay leads to poor coverage.
SIGSTRFLTLEN 2 Handover delay leads to poor coverage.
LEVHOHYST 2 Handover delay leads to poor coverage.
HOCDCMINUPPWR 0 Handover delay leads to poor coverage. SIGQUAFLTLEN 2 Handover delay leads to poor coverage.
HOCDCMINDWPWR 10 Handover delay leads to poor coverage. NCELLFLTLEN 4 Handover delay leads to poor coverage.
BQHOEN YES Handover delay leads to poor coverage.
DLQUALIMIT 50 Handover delay leads to poor coverage. SndRcvMode DOUBLE_A
Abnormal link.
ULQUALIMIT 50 Handover delay leads to poor coverage. NTENNA
ULQUALIMITAMRHR 55 Handover delay leads to poor coverage. SndRcvMode1 DOUBLE_A
Abnormal link.
DLQUALIMITAMRHR 55 Handover delay leads to poor coverage. NTENNA
ULQUALIMITAMRFR 60 Handover delay leads to poor coverage. SndRcvMode2 DOUBLE_A
Abnormal link.
DLQUALIMITAMRFR 60 Handover delay leads to poor coverage. NTENNA
INTERCELLHYST 68 Handover delay leads to poor coverage. SndRcvMode3 DOUBLE_A
BQMARGIN 69 Handover delay leads to poor coverage. Abnormal link.
NTENNA
INTELEVHOHYST 67 Handover delay leads to poor coverage. SndRcvMode4 SGL_ANTE
EDGEADJSTATTIME 6 Handover delay leads to poor coverage. Abnormal link.
NNA
EDGEADJLASTTIME 4 Handover delay leads to poor coverage.
HAVETT1 NO Abnormal link.
LEVSTAT 8 Handover delay leads to poor coverage.
LEVLAST 6 Handover delay leads to poor coverage. ATTENFACTOR1 0 Abnormal link.
PBGTSTAT 8 Handover delay leads to poor coverage. MRRUATTENFACTO
4 Abnormal link.
PBGTLAST 6 Handover delay leads to poor coverage. R1
HAVETT2 NO Abnormal link.
ATTENFACTOR2 0 Abnormal link.
MRRUATTENFACTO
4 Abnormal link.
R2
FMSMAXOPCC 5 Abnormal link.
PBGTHOEN YES Handover delay leads to poor coverage.
FRINGEHOEN YES Handover delay leads to poor coverage.

Action 3: Handover Exception Check and Coverage
Overlap Check (1)
 Purpose: Poor coverage caused by the following problems is not real poor coverage and must
be handled by performing this operation: missing neighboring cells, failure to trigger handovers,
handover delay, handover failure, and coverage overlap.
 Principles: Check whether parameter settings are appropriate by comparing the parameters with
the baselines and comparing parameter values before and after the swap. The parameters
include 12 core parameters, 25 handover parameters, and 25 other parameters.
Purpose and Requirements Outputs Data Sources Tools and Guides Issue Closure
(1) Find out cells whose neighboring cells are missing. (1) GIS software, such as Nastar, Mapinfo,
When neighboring cells are missing, MSs cannot be (1) List of missing and Google Earth
handed over to the neighboring cells. As a result, MSs neighboring cells of (2) Signaling analysis tools, such as
(1) Add missing neighboring
suffer quality deterioration caused by the low level in the problematic cells PFMStudio
cells according to their
serving cell. (1) Engineering (3) DT analysis tools, such as the Probe
priorities.
(2) Find out cells with poor coverage due to no handovers parameters, MML TEMS
(2) Adjust and optimize
or delayed handovers. When the handover algorithm or configuration file, and e- (4) Parameter query and browsing tools,
(2) List of parameters of parameters that cause
parameters are inappropriately configured, handovers will map such as PFMStudio, OMStar, and LMT
problematic cells handover delay.
be delayed. As a result, MSs suffer quality deterioration (2) Top cell signaling Note: A prototype tool is being developed
(3) Locate "island" cells
caused by the low level in the serving cell. tracing for automatically analyzing missing
based on engineering
(3) DT data neighboring cells, coverage overlaps, poor
(3) Find out "island" cells caused by coverage overlaps. parameters and adjust the
(3) List of "island" cells (4) MR tracing data coverage, and unbalanced uplink
Cells become islands when coverage overlaps occur. In downtilt or add neighboring
caused by coverage /downlink traffic using MR tracing data.
this case, handovers cannot be triggered and the quality cells.
overlaps and list of TA Currently, the tool is undergoing the Beta
deteriorates due to the low level. As a result, call drops
samples test. It is scheduled to be launched in early
occur.
2013.

Overlap Check (2)
 Detailed procedure
1. Common methods for analyzing missing
neighboring cells are as follows:
(1) Locate possible missing neighboring cells manually
based on the map and configure missing neighboring
cells to check whether neighboring cells are actually
missing.
(2) Analyze signaling tracing data to check whether the
receive level of the neighboring cell reported by the MS
in the poor-coverage area is low and whether the MS
accesses the network from another cell when the call is
originated again. Check whether any neighboring cells According to the
signaling
fail to be reported because they are not configured in analysis, the
advance. level of the
neighboring cell
(3) Use the neighboring cell optimization functions of the reported before
the call drop is
Nastar to analyze missing neighboring cells. For details very low. When
about the method, see the related part in this document. the call is
originated again,
the MS
accesses the
network from
another cell. As
shown on the
map, a
neighboring cell
fails to be
configured.

Overlap Check (3)
2. Common methods for analyzing handover originating failures or handover delay are as follows:
(1) Analyze the outgoing handover success rate of the source cell and the incoming handover success rate of the target cell based
on traffic statistics and locate cells whose handover success rate is abnormal to perform detailed analysis.
(2) Analyze the number of outgoing handover requests in the source cell and the number of incoming handover requests in the
target cell based on traffic statistics and locate cells where the number of handover requests is significantly small (50% smaller
than the network-wide average value) to perform detailed analysis.
(3) Analyze whether a neighboring cell with a good receive level exists when the call is originated from a poor-coverage area but the
MS is not handed over to the neighboring cell and the MS camps on the low-level serving cell or even call drops occur based on
the signaling tracing data on the system side or DT signaling.
If the handover is delayed or no handover occurs, perform the following checks:
(1) Check whether the handover delay or handover originating failure is due to inappropriate parameter settings.
(2) Check whether channels cannot be assigned or handover exceptions occur due to congestion or other problems (such as link or
hardware faults) in the target cell.
For the detailed method, see the GPSS V100R003C00 GSM Technical Guide for HO Troubleshooting.
Two neighboring
cells with a high
receive level are
The cause detected before the
of low call drop. The cal
incoming drop happened
handover when the handover
rate in this is not yet initiated.
cell is
resource
congestion.

Overlap Check (4)
The serving range of this
cell is too large. As a
result, calls cannot be
3. Analysis of islands caused by coverage overlaps:
handed over to
(1) Analyze the possible islands caused by coverage surrounding neighboring
cells in time and call
overlaps manually based on DT data.
drops occur.
(2) Use GIS software (such as Nastar) to check whether
the detected missing neighboring cells are "island" cells The network structure index
caused by coverage overlaps. If the detected missing is used for assessing the
health of the network
neighboring cells and the problematic cell span two structure in an area. It
layers of sites, islands exist. indicates the number of
overlapping TRXs of cells
with strong signals in the
area. If the value of this
(3) Analyze the network structure index and overlapping index is large, the network
Network structure is complicated,
coverage. structure making frequency planning
index difficult.
The overlapping coverage indicates the number of cells
Avg. number f Overlapping
with strong signals that cover a cell. A larger value TRXs coverage
indicates a more complicated network structure.
% of high,
% of high,
medium, Avg.
The actual overlapping coverage reflects the overall Traffic density
Avg. site Redundant
coverage
Coverage
overlap %
medium,
and low
and low
Avg. site
height
downtilt of
spacing interfering sites
coverage overlap conditions. Coverage overlaps lead to sites
sites
poor coverage only in some cases and cause internal

interference in most cases. As it is a problem rooted in Assume that cell A is the serving cell (Server) and cell B is the interfering cell (Interference).
Co-frequency correlation factor: indicates the overlapping coverage of two cells. If both Overlapping
the network structure, it can be resolved only using 3- the capacity (numbers of TRXs of Server and Interference) and frequency are the same, the higher coverage and
dimensional network structure solutions, such as overlapping coverage indicates stronger interference between the cells.
network
Number of MRs involving cell A that may be structure index
underlying network solutions. For details, see the affected by the intra-frequency cell B formulas
professional service solutions, such as the GSM Number of MRs involving cell A adopted by
Network Structure Assessment and Optimization Number of MRs involving cell A that may be affected by the intra-frequency cell B China Mobile
=∑Number of MRs in each C/I interval x Corresponding interference probability
Solution or 3-Dimensional Networking.
overlapping coverage =
Network structure index =

Detailed Cause Analysis Based on Raw MR Data (a Professional
Service Under Development by the OMStar Team) Locate root
causes of
The OMStar provides the functions of locating root causes of coverage exceptions based on MR data and coverage
generating the list of root causes of coverage exceptions for all cells or top cells in one-click mode. problems in
batches.
Analysis of downlink poor-coverage
cells
Poor DL
UL and DL Imbalance with Limited Islands Caused by Downlink Poor
Coverage_Missing Excessive DL Power control Insufficient DL Coverage
DL Rate Coverage Overlaps Coverage_HO Exceptions
Neighboring Cells
Avg. Level
Avg. DL Number of Number of
Number of of Strongest % of MRs
Percentage of Avg. TA Level of MRs % of MRs Number of Avg. MRs Percentage
Total MRs Neighboring Related to Number of Number of
MRs Related of Poor Poor- Related to Related to MRs % of MRs Adjustment Related to % of MRs of MRs Number of % of MRs Number of % of MRs
CI Number of Related to Cells of Poor DL MRs MRs Related Avg. DB for
to Poor DL DL Coverage Poor Poor DL Related to Related to DB Due to Poor DL Related to Related to MRs Related Related to MRs Related Related to
MRs Poor DL Cells with Coverage Related to to HO Excessive
Coverage Coverage Serving Downlink Quality UL and DL UL and DL UL and DL Coverage Islands Due HO to Excessive Excessive to Deep DL Deep DL
Coverage Poor DL Due to Islands Due Exceptions Power
Cells Quality Imbalance with Limited Imbalance Due to to Coverage Exceptions DL Power DL Power Poor Poor
Coverage Missing to Coverage Due to Poor Control
with Limited DL Rate with Limited Missing Overlaps Due to Poor Control Control Coverage Coverage
Neighboring Overlaps DL Coverage
DL Rate DL Rate Neighboring DL Coverage
Cells
Cells
32772 151811 5581 3.68 2.63 -97.16 -92.03 10069 6.63 253 4.53 5.21 - - 82 1.47 623 11.16 32 0.57 0.94 253 4.53
34976 194311 6005 3.09 2.01 -94.83 -90.84 18763 9.66 33 0.55 5.36 - - 19 0.32 346 5.76 - - - 33 0.55
34277 287167 8676 3.02 1.98 -96.08 -90.38 18648 6.49 100 1.15 5.83 - - 18 0.21 834 9.61 908 10.47 2.09 100 1.15
34914 224361 6538 2.91 2.35 -96.57 -91.77 14895 6.64 200 3.06 4.97 367 5.61 117 1.79 387 5.92 106 1.62 1.12 200 3.06
48099 71659 2049 2.86 3.86 -96.61 -90.86 3151 4.40 48 2.34 5.52 - - 30 1.46 81 3.95 25 1.22 1.88 48 2.34
32211 657863 18232 2.77 3.17 -96.60 -94.10 31906 4.85 312 1.71 5.42 - - 11 0.06 123 0.67 351 1.93 1.71 312 1.71
34916 492300 13634 2.77 2.25 -97.09 -89.18 23637 4.80 493 3.62 4.85 160 1.17 - - 377 2.77 310 2.27 1.56 493 3.62
Tool: OMStar V500R006

(prototype tool)
Output: Query 01-Suggestions on handling the UL and DL imbalance_Cell
Configuration Suggestions on
automatic problem Automatical
associated (1) Rectify exceptions caused by RF channels. resolution ly associate
(2) Check whether any alarms are generated for the RF module (TRX or combiner) coverage
parameters in light (3) Check performance of repeaters and indoor trunk amplifiers and adjust the gains of repeaters according to the interference. parameters
(4) Check related parameters and correct abnormal parameters. and
of root causes and baselines.
MS_TXPWR_MAX_CCH Power Level Power Type
ci btsid
automatically (0.5) 0.0 DEFAULT
30034 7 5 0 10 W
provide solutions
30035 7 5 0 40 W
using the OMStar. 30036 7 5 0 15 W
30131 20 5 0 20 W
30132 20 5 0 15 W

Coverage — Required Actions for MR-Based Coverage Optimization
(Professional Service)
Required Action Purpose and Requirements Output Issue Closure
The path loss on the uplink is
Check whether the in-building trunk amplifiers or
MR-based UL and DL significantly different from that on the Percentage of problematic cells with
repeaters are abnormal.
analysis downlink (≥ 12 dB), leading to the unbalanced uplink and downlink paths
Export the summary report.
abnormal receive level.
MSs cannot be handed over to
neighboring cells with a strong receive
Add missing neighboring cells according to their
MR-based missing level as they are not configured in Percentage of problematic cells whose
priorities.
neighboring cell analysis advance. As a result, MRs suffer poor neighboring cells fail to be configured
service quality due to poor coverage in
the serving cells.
Some cells become islands due to
After the cells affected by islands are confirmed
coverage overlaps. Handovers cannot Percentage of problematic cells
MR-based coverage based on the engineering parameter data, adjust
be initiated in these cells, leading to low affected by islands caused by coverage
overlap analysis the downtilt or add neighboring cells.
level and poor service quality. As a overlaps
result, call drops occur.
To adjust the conservative power control
adjustment, optimize the corresponding filter factor.
Power control adjustment is insufficient
To adjust conservative handover settings, optimize
or settings of handover parameters are Percentage of problematic cells
MR-based HO/power RXQUAL, edge handover threshold, inter-cell
too conservative, leading to handover affected by handover/power control
control timeliness analysis hysteresis, and P/N. If no MR containing downlink
delay. As a result, MSs suffer poor delay
information is available, enable the corresponding
service quality due to poor coverage.
parameter switch.
Adjust the downtilt and azimuth of the cell or
This operation is aimed at analyzing
MR-based intensive Percentage of problematic cells surrounding cells if the coverage depth is
the poor service quality due to poor
coverage analysis affected by insufficient coverage depth insufficient.
coverage when the TA is small.
This operation is aimed at identifying Service geographic observation of Perform coverage optimization in light of the
Geographic coverage
areas affected by poor coverage and problematic cells when the service specific scenario.
analysis
special coverage. quality is poor due to poor coverage Export the summary report.
Actual DT can be performed to verify
Perform coverage optimization in light of the
DT-based poor coverage the grid-based geographic poor DT-based optimization results of areas
specific scenario.
analysis coverage analysis on a map to identify affected by poor coverage
the cause of the problem.

Action 4: Geographic Coverage Analysis (1)
 Implementation condition: optional. Implemented when operations 1 to 4 fail to resolve the problem or areas
affected by abnormal coverage need to be accurately located after the swap or engineering adjustment.
 Purpose: Accurately locate areas affected by abnormal coverage by service geographic observation. Perform DT or
dial-up test if necessary. Confirm the impact scope and symptom of the problem.
 Principles: Accurately locate areas affected by abnormal coverage by using the MR-based service geographic
observation functions of the Nastar and service geographic observation functions of the DT software.
Data Sources Tools and Guides Outputs Issue Closure
(1) Engineering parameters,

MML configuration file, and e- Nastar, Mapinfo, and Google Earth
Service
map
geographic Perform
Nastar (MR-based service geographic
(2) MR tracing data observation of operation 5 RF
observation function)
the problematic and coverage
DT analysis software (Probe and
(3) DT data cell with poor solution check.
TEMS)
coverage
Select data source (2) or (3) or both according to actual situations.

The MR-based service geographic observation
function has the following advantages:
 No DT is required. You only need to collect MR
data on the system side, observe coverage
conditions in each area on the map. Areas that
can be analyzed include but are not limited to
roads.
The function has the following limitations:
 It requires the support from the Nastar server.
 To ensure the positioning accuracy, a
geographic characteristics database must be
provided. As the input of database
construction is huge, it is usually implemented
along with professional services.
The service geographic observation

function of DT software has the following
advantages:
 High positioning accuracy. Only DT
analysis software is required, which
can run in standalone mode.
The function has the following limitations:
 The DT cost is high. The DT device
and test method may impact on DT
results.
 DT can test only road coverage.
Manual dial-up testing is required for
testing indoor or special areas.

(3) Action 4: Geographic Coverage Analysis
 Common methods for DT-based comparative service geographic observation:
If poor coverage is detected in the DT after the swap or engineering adjustment, we usually use the
following service geographic observation methods:
(1) Direct analysis method: If the coverage changes significantly in continuous areas, areas and serving
cells where the network coverage becomes poor can be located directly from the geographic distribution
of levels.

(2) Delta analysis method: If areas where the network coverage
changes are scattered, it is difficult to locate all areas by direct
observation. In this case, you can use the delta analysis method.
The procedure is as follows:
(a) Combine DT data by location before and after the coverage
change.
(b) Use the longitude and latitude as indexes to locate and test
the level at each location, and calculate the level difference: delta.
(c) Display the level value of each location on the map to observe
sections where the network coverage changes significantly.
(d) Calculate changes in the number of sampling points, average
receive level, and number of compliant sampling points in each
cell before and after the coverage change and arrange the
sequence of cells based on the preceding data to locate
problematic cells.
PRE (Standard: –62 dB) POST POST – PRE
Number Total Number Total

ServCI Number of Number Number of Number of
Total Number of Number of Number Average
NC Average of NC Average NC Compliant Calculate the
of Sampling Compliant of Compliant of Level
Sampling Level (dBm) Sampling Level (dBm) Sampling Sampling level difference
Points Sampling Sampling Sampling Sampling (dBm)
Points Points Points Points
Points Points Points Points (delta) before
and after the
5533 99 49 50 -59.76 15 19 34 -59.59 -34 -31 -65 0.17 coverage
Calculate the change, and
number of 7837 147 83 64 -64.80 9 44 53 -56.34 -74 -20 -94 8.46 display the data
sampling points on the map.
and the average7839 98 63 35 -64.59 64 20 84 -71.20 1 -15 -14 -6.61
Then areas
level before and8093 58 48 10 -68.19 231 9 240 -78.13 183 -1 182 -9.94 affected by
after the coverage
coverage 11421 61 13 48 -54.90 26 34 60 -59.13 13 -14 -1 -4.23
problems can be
change, located.
12429 81 29 52 -56.27 29 41 70 -58.24 0 -11 -11 -1.97
sequence cells
according to the17039 83 22 61 -56.24 4 34 38 -54.71 -18 -27 -45 1.53
number and the
average receive18317 148 61 87 -61.36 46 45 91 -63.13 -15 -42 -57 -1.77
level, and locate19342 13 13 0 -67.77 3 2 5 -76.00 -10 2 -8 -8.23
problematic cells.
19614 184 59 125 -56.42 63 113 176 -59.30 4 -12 -8 -2.88
19615 62 25 37 -53.79 16 27 43 -58.02 -9 -10 -19 -4.23
30351 66 34 32 -61.56 47 21 68 -65.60 13 -11 2 -4.04

Action 5: RF and Coverage Solution Check
 Implementation condition: optional. Implemented when operations 1 to 4 fail to resolve the problem.
 Purpose: (1) Check RF parameters, such as areas affected by abnormal coverage, site density, and site height/downtilt/azimuth. Check
whether the number of sites is obviously abnormal or inappropriate. (2) Identify the scenario to which the area affected by abnormal
coverage belongs and check whether the corresponding coverage networking solution is obviously inappropriate.
 Principles: Present network coverage of an office in terms of terrain, site density, and mobility density. Compare coverage information
about multiple sites, determine the coverage level on the live network, and check whether KPIs on the live network are appropriate based
on traffic information. Perform a field survey for the areas affected by poor coverage if necessary. Focus the field survey on the following
coverage scenarios: buildings, indoor, high-rises, and corners.
Purpose and Requirements Data Sources Tools and Guides Output Issue Closure
(1) Check the areas where the network coverage is abnormal
and RF parameters, such as site density, site height, downtilt, Adjust RF parameters
RF check list
and azimuth. Check whether the number of sites is abnormal or GIS software, such or add sites.
inappropriate. (1) Engineering as Nastar and
(2) Check whether the antenna type is appropriate. parameters, MML Mapinfo
If the problem cannot be resolved by adjusting RF parameters configuration file, MR analysis Antenna
(such as the height, downtilt, and azimuth) after operation 1 is and e-map software, such as selection Replace antennas.
performed, analyze whether the antenna type is suitable for the (2) MR tracing data Nastar analysis
scenario. DT analysis
(3) Perform checks for special networking scenarios. If no (3) DT data and dial- software
exception is detected after operations 1 and 2 are performed or up tracing data Adjust the coverage
if the coverage problem persists after RF parameters and Networking networking solution.
Coverage
antenna are adjusted, analyze whether the networking solution Select operation (2) solution for the Note: For details about
scenario and
is suitable for the scenario. or (3) or both to special scenario the service
solution
Scenarios: DUA, urban area, suburban area, rural area, and perform the analysis. and corresponding opportunities, see the
analysis
special coverage scenarios (indoor, tunnel, sea surface, and guide service solution
high-speed railway) package.
Solutions: macro, macro + micro, repeater, and RRU

Action 5: RF and Coverage Solution Check — RF
Parameter Check
 Detailed procedure:
1. Routine RF parameter check:
Check whether RF parameter settings of the cell where the coverage is abnormal are appropriate and
whether the problem can be resolved by adjusting RF parameters, including the antenna height, downtilt,
azimuth, and site spacing.
The following table lists principles for setting RF parameters of antennas in urban areas. For details, see
the Principles for Checking the RF Parameters of Radio Networks.
Scenario Principles for Setting Antenna Height Principles for Setting Site Spacing Principles for Setting the Downtilt Principles for Setting the Azimuth
(1) BTSs are usually densely distributed in urban areas, which may impact on each
other. To ensure that most energy is radiated within their own scope of coverage and
(1) Generally, the ideal antenna height in
reduce the interference to neighboring cells, align the vertical upper half power point
DUAs ranges from 25 m to 30 m. To adapt to
of the major lobe of the antenna to the edge of the coverage when you set the initial
tactual conditions, some may range from 30 (1) Generally, set consistent azimuths for
Two factors influence the BTS downtilt of the antenna. The formula is as follows:
m to 40 m. the antennas of all sites in urban areas to
distribution most in urban areas: traffic a = arctg(2H/L) x 180/∏ + B/2 – Downtilt
(2) Buildings six stories higher than the prevent complicated network planning
density distribution and site a indicates the initial mechanical downtilt of the antenna in degrees. H indicates the
average height of surrounding buildings are issues arising later when cells are split.
deployment conditions. Site density valid height of the site, that is, the difference between the antenna height and the
not recommended. The most ideal site for an (2) Avoid clutters, such as buildings,
maps traffic density and the even user average height of the covered area in meters. L indicates the distance of the antenna
antenna should be two to three stories higher nearby (within 100 m) and make
distribution must be taken into to the edge of the coverage of the sector, in meters. B indicates the vertical lobe width
than the average height of surrounding appropriate adjustments according to the
account. in degrees. Downtilt indicates the angle of the electrical downtilt in degrees. The
buildings. coverage focus of the sector.
(1) The site spacing in CBDs and mechanical downtilt calculated by the preceding formula is only an initial value. It is
(3) If sites for antennas are located among (3) Avoid setting the major lobe of the
areas where hotels, office buildings, used for setting the downtilt in simulation projects or setting the initial downtilt for an
buildings in urban areas, you can make use antenna dead against a straight street in
and entertainment venues are antenna. You can adjust the value based on the simulation results or the DT results
of varying building heights to deploy a DUAs to prevent coverage overlaps.
Urban area densely distributed usually ranges after the actual network goes live.
hierarchical network. Sites for antennas of (4) Set the major lobe of the antenna to
from 0.6 km to 1.6 km. (2) In DUAs, RET antennas with the preset downtilt of 6 degrees – 7 degrees is
primary BTSs should be slightly higher than the direction of the area with dense traffic.
(2) The site spacing in economic and recommended. It can provide 15 degrees – 20 degrees downtilt in network expansion
the average height of buildings. Usually, the The strength of signals in this area can be
technological development zones and optimization scenarios in cooperation with the mechanical downtilt.
height of a BTS in DUAs should range from enhanced to improve the call quality.
usually ranges from 1.6 km to 3 km. (3) When the distance between the BTS and the target of coverage exceeds 800 m,
25 m to 30 m. (5) Set the major lobe of the antenna
(3) The site spacing in common urban large-area coverage remains the focus. When estimating the downtilt of the antenna,
(4) Hills at high altitudes in the urban or deviated from intra-frequency cells to
areas ranges from 3 km to 5 km. you do not need to take the vertical half-power angle into account. In this case, the
suburban areas of cities (200 m – 300 m effectively avoid interference.
(4) If BTSs are located on the edge of general downtilt ranges from 1 degree to 4 degrees. If the site is located at a high
higher than the common urban areas) are not (6) Ensure that the cross coverage depth
cities or in suburban areas and the position in special scenarios, you can set a larger downtilt for the antenna.
recommended for the following reasons: of antennas of neighboring sectors in
site spacing exceeds 5 km, use (4) The mechanical downtilt of the antenna cannot exceed 10 degrees – 15 degrees
a. Prevent CCI and poor signals within the urban areas does not exceed 10%.
omnidirectional BTSs. during initial installation.
network coverage.
(5) When the cell needs to cover an area higher than the position of the antenna, you
b. Reduce the engineering construction
can install the antenna reversely or set the downtilt of the antenna to a negative value.
difficulty and facilitate maintenance.
In this case, you need to ensure that proper waterproof measures are taken for the
antenna.

Action 5: RF and Coverage Solution Check – Special
Networking Scenarios
2. Antenna selection appropriateness check:
If the coverage problem persists after RF parameters are adjusted in operation 1, analyze whether the antenna
type is suitable for the scenario. The following table lists principles for selecting antennas in urban areas. For
details, see the Principles for Checking the RF Parameters of Radio Networks.
Scenario Antenna Selection
Recommended antenna type:

Horizontal lobe width: 65 degrees (33 degrees is recommended for 4-sector to 6-sector BTSs)
Medium gain: 15 dBi – 18 dBi
Dual-polarized antennas with fixed electrical mechanical downtilt (6 degrees – 9 degrees) or adjustable electrical downtilt plus mechanical downtilt
Notes:
(1) If the mechanical downtilt is large, pay attention to the front-to-back ratio. Antennas with a small front-to-back ratio cause huge interference to high-
rises in the back. Therefore, use antennas with a huge front-to-back ratio (30 dB – 40 dB) in DUAs to reduce the indoor interference of the rear lobe to
high-rises.
Urban area (2) In the case of directional 2-sector or single-sector sites, use antennas with the horizontal lobe of 90 degrees if actual situations permit but antennas
with a horizontal lobe exceeding 90 degrees are not recommended.
(3) Use micro cellular antennas with a low gain (such as 10 dB – 12 dBi) to fill coverage holes in urban areas.
(4) If the coverage distance is small in urban areas, null-fill is not required. If sites are at high positions in urban areas, however, select antennas that
perform better in first upper side lobe suppression and first lower null-fill with huge electrical downtilt or adjustable electrical downtilt to prevent
interference on neighboring cells or coverage holes under the tower. Antennas with small vertical lobes are recommended, to control the coverage area.
(5) In scenarios where frequencies are densely reused, large downtilt is set sometimes to reduce interference caused by coverage overlaps. If the downtilt
exceeds a half of the vertical half-power beamwidth, the impact of the upper side lobe needs to be taken into account. Therefore, the adaptive beam
forming (ABF) antennas that provide restricted first upper side lobes (the level of the first upper side lobe must not exceed –18 dB) are recommended.
3. Networking solution check in special scenarios:

If the coverage problem persists after operations 1 and 2 are performed, analyze whether the networking solution is suitable for the scenario.
Special scenarios include indoor coverage, high-speed coverage, large stadium coverage, and sea surface coverage. In this case, find
opportunities for selling Huawei's professional networking services. GPSS V100R003 will provide a series of networking solutions, including the
underlying network solution, solutions for large business and commercial districts, high-speed areas, and campus, and 6-sector solution. For
details, consult the contact person of the corresponding service.

Action 6: Coverage Simulation
 Implementation condition: optional. Implemented for engineering adjustment and optimization.
 Purpose: In scenarios where the engineering adjustment workload is huge, networking solutions are complicated, and
the customer's requirements are strict, you can formulate the network adjustment solution based on simulation results
provided by a simulation tool and verify the adjustment effect.
 Principles: Simulate the network coverage based on the link budget and engineering parameters.
 Data sources: engineering parameters, MML configuration file, and e-map
 Tools: U_NET
 Output: Coverage simulation results before and after the engineering adjustment, including geographic distribution
diagram and the distribution percentages of the coverage level, quality, and C/I counters in each interval.
Formulate
the RF
adjustment
solution
based on
simulation
results.

Deliverable of Coverage Analysis

Contents
 Coverage
 Principles
 Cases

Page 74
Case 1: Network Coverage Confirmed to Be Below the
Standard Due to Incorrect Power Mapping
 Step 1 Confirm coverage information.
 Swap the network.
 The level detected by the scanner during the DT after the network swap was lower than that on the original
network.
 Step 2 Perform Required Actions.
Required Action Analysis and Symptom Conclusion Next Operation Effect
comparative
Compare DT results and locate top sites Locate the cause of the
analysis of Perform operation 2.
affected most significantly by poor coverage. problem for top sites.
coverage & traffic
Identify the reason
Measure the TOC on the
Check the power mapping of top sites. The why the receive
TRX information provided by original network, check dump
power configuration of a site after the level detected in
Action1: the customer is incorrect, files and configuration
network swap is significantly different from the DT after the
hardware/channel/a and the TOC on the original information on the live network,
that on the original network, and the actual network swap is
ntenna check network is not actually and confirm the TRX
power configuration is different from that lower than that on
measured on the site. configuration to map the
provided by the customer. the original
power.
network.
Step 3 Perform issue closure and export the summary report.

Adjustment suggestion:
Measure the TOC on the original network, check dump files and configuration information on the live network, and
confirm the TRX configuration.
Adjustment result:
The level in the second measurement is consistent with that on the original network and the network KPIs become
normal.

Case 2: Poor Network Quality Caused by Incorrect
Parameter Settings
 Swap the network.
 Customers complained that the uplink HQI became abnormal in GSM1800 MHz cells covered by the BSC in the
area.

(1) Check equipment alarms: No
alarm is generated, the availability of The hardware is not Perform the next
N/A
TRXs/channels is normal, and the faulty. operation.
Action1: activation failure rate is 0.
hardware/chann The antenna is
(2) Check RF channels: RF channels
el/antenna correctly connected Perform the next
are abnormal and the antenna is not N/A
check and the main and operation.
reversely connected.
diversities are normal.
(3) Check the power mapping of No exception is Perform the next
N/A
1800 MHz cells. detected. operation.
The Maximum Change the transmit Identify the cause

Action2: Check parameter settings. A key
transmit power level power level of the MS of the abnormal
parameter coverage parameter (Maximum
of the MS is for 1800 MHz sites from uplink coverage
check transmit power level of the MS) is
incorrectly set. 5 to 0. quality.
incorrectly set.

Case 3: Poor Network Quality in an Area
Problem analysis:
 Check key parameters of the cells with coverage problems. The parameter Maximum transmit
power level of the MS for 1800 MHz cells is incorrectly set. On the live network, the parameter
value is set to 5 (level 1 equals to 2 dB gain).
 According to the traffic statistics on the uplink and downlink balance, the uplink quality of the
abnormal cells is rather poor.
Adjustment suggestion: Change the Maximum transmit power level of the MS on the live
network from 5 to 0.
Maximum Transmit Power Level
Cell ID Recommended Value
of the MS
142 5 0
80 5 0
232 5 0
153 5 0
48 5 0
Adjustment result:
Percentage of MRs Involving Poor Percentage of MRs Involving Percentage of
Percentage of
Service Quality Due to Uplink Poor Service Quality Due to Unbalanced UL
Cell ID Unbalanced UL and DL
Poor Coverage (Before Uplink Poor Coverage (After and DL Paths
Paths (Poor DL Quality)
Adjustment) Adjustment) (Poor UL Quality)
142 10% 2% 50% 5%
80 15% 1% 45% 3%
232 20% 1% 60% 10%
153 5% 0% 35% 7%
48 9% 0% 40% 8%

Case 4: Poor Coverage Because TMA Fading Factor
Is Not Configured
 Optimize the network.
 The service quality became poor due to poor coverage after TMAs were installed in an area.

(1) Check equipment alarms: No alarm is

generated, the TRX/channel usage is normal,The hardware is not faulty. Perform the next operation. N/A
and the operation failure rate is 0.
Action1:
hardware/channel/a (2) Check RF channels of the antenna: RF The antenna is not
ntenna check reversely connected, and
channels are normal and the antenna is not Perform the next operation. N/A
the main and diversities are
reversely connected.
normal.
The uplink and downlink
(3) Check the uplink and downlink balance:
are unbalanced. The uplink Analyze the cause of uplink
The level difference between the uplink and N/A
level is strong, while the and downlink imbalance.
downlink exceeds 12 dB.
downlink level is poor.
TMA Fading Factor is not
configured. As a result, the
uplink level after network The uplink and
Action2: parameter Configure TMA Fading
Check parameters: TMA Fading Factor is swap is a lot stronger than downlink become
check Factor.
not configured. the downlink level, and the balanced.
uplink and downlink is
seriously unbalanced.

Case 4: Poor Coverage Because TMA Fading Factor Is
Not Configured
Problem analysis:
• During TMA configuration, TMA Fading Factor is not configured. As a result, the uplink level after the
network swap is a lot stronger than the downlink level, and the uplink and downlink are seriously
unbalanced (see the traffic statistics on June 30).
 Step 3 Perform issue closure and export the summary report.

Adjustment suggestion: Configure TMA Fading Factor.
Adjustment result: The uplink and downlink become balanced (see the traffic statistics on July 1).

Case 5: Poor Coverage Due to Missing Neighboring
Cells
 Two top cells (SB3 Xiashangoutou 3 and SB3 Shangdongpusanpian 2) were affected by poor service quality due to
downlink poor coverage.
Total Number of Total Number of MRs Involving
Serving Cell ID Serving Cell Name MRs Involving the the Serving Cell Affected by
Serving Cell Poor DL Coverage
254 SB3 Xiashangoutou 50497 5517
173 SB3 Shangdongpusanpian 2 12053 1317

Action1: Perform the next

No exception is detected. N/A
hardware/channel/antenna check operation.
Perform the next

Action2: parameter check N/A
No exception is detected. operation.
Analyze the problem

Some neighboring cells are missing,
Action3: handover exception symptom. Some Configure missing The problem is
leading to high percentage of poor
check and coverage overlap check neighboring cells are neighboring cells. properly resolved.
coverage.
missing.

Case 5: Poor Coverage Due to Missing Neighboring
Cells
• Use the Nastar to further locate the cause. SB3 Xiadian 1 and S99 Qigoucun 3 are neighboring cells of
SB2 Xiadongpu 2 is a neighboring cell of SB3 SB3 Qishangoutou 3 but are not configured as neighboring
Shangdongpusanpian 2 but is not configured as a cells of SB3 Xiashangoutou 3.
neighboring cell of SB3 Shangdongpusanpian 2.

 Adjustment suggestion: Add the missing neighboring cells.
 Adjustment result:
Phase Cell Name % of Poor Coverage Due to Missing Neighboring Cells
SB3 Xiadian 1 20.82

Before handling SB3 Xiashangoutou 3
S99 Qigoucun 3 30.77
SB3 Xiadian 1 5.75
After handling SB3 Xiashangoutou 3
S99 Qigoucun 3 5.08
SB2 Xixin 1 50.83
Before handling SB3 Shangdongpusanpian 2
SB2 Xiadongpu 2 20.38
After handling SB3 Shangdongpusanpian 2 SB2 Xixin 1 2.47

Case 6: Call Drops Caused by Low Level as a Result
of Coverage Overlap
 The call drop rate in a top cell was high, and most call drops were caused by the low level.
Comparative analysis Skip this operation if the area is

of coverage & traffic located.
Action1:
Perform the next
hardware/channel/ant No exception is detected. N/A
operation.
enna check
Action2: parameter Perform the next
No exception is detected. N/A
check operation.
(1) Some neighboring cells are Perform the next
N/A
missing. operation.
Perform the next
(2) No handover is delayed. N/A
Action3: handover operation.
exception check and (3) Analyze island cells due to
coverage overlap coverage overlap. Locate the The serving range of this cell
Adjust the downtilt and The call drop rate
check missing neighboring cells is too large. As a result, calls
azimuth of the top cell and becomes normal
whose high level exceeds the cannot be handed over
limit its coverage along after the
TA based on the uplink and quickly to nearby neighboring
the roads and streets. adjustment.
downlink level information in the cells, and call drops occur.
MRs involving poor coverage.

Case 6: Call Drops Caused by Low Level as a Result
of Coverage Overlap
The serving
range of this
cell is too large.
As a result,
calls cannot be
handed over to
surrounding
neighboring
cells in time and
call drops occur.

Adjustment suggestion: Adjust the downtilt and azimuth of the antenna of the top cell.
Adjustment result: The call drop rate in the top cell becomes abnormal.

Case 7: High Call Drop Rate Due to Poor Coverage

 Large number of call drops due to low level caused by poor coverage were detected during the DT of
a cluster.
Required Action Analysis and Symptom Conclusion Issue Closure
Comparative analysis of
Skip this operation if the area is located.
coverage & traffic
Action1:
hardware/channel/antenna No exception is detected. Perform the next operation.
check
Action2: parameter check No exception is detected. Perform the next operation.
Action3: handover exception
check and coverage overlap No exception is detected. Perform the next operation.
check
Compare level distribution information in the
The percentage of low levels
DT results before and after the network swap:
Action4: geographic increases after the network swap
The percentage of low levels increases 0.5%. Perform the next operation.
coverage analysis and continuous areas affected by
In terms of geographic distribution, the level
poor coverage exist.
deteriorates significantly.
According to the site survey, the area is As the problem is caused by the
Action5: RF and coverage Add sites to make up
mountainous and coverage holes exist at high terrain, antenna adjusting is not a
solution check coverage holes.
altitudes. solution.

Case 7: High Call Drop Rate Due to Poor Coverage
Problem analysis:
• Compare level distribution information in the DT results before and after the network swap.
The percentage of low levels increased 0.5%. In terms of geographic distribution, the level
deteriorates significantly.

Adjustment suggestion: Adjust the downtilt and azimuth of the antennas and add sites to make
up coverage holes.
Adjustment result: The call drop rate in the DT results becomes normal.

Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Page 86
Contents
 Interference
 Principles
 Cases

Overview
 Definition
Interference is the disturbance that unwanted signals cause to wanted signals.
 Methods for detecting interference

 Detect interference based on the following traffic statistics in the operation and
maintenance center (OMC):
 Interference band counters
 Voice quality statistics
 Frequency scanning performance statistics
 Signal received quality and level performance statistics
 Detect interference based on alarms generated in the OMC and customer

complaints.
 Detect interference based on drive test (DT) and circuit quality test (CQT) results.

Interference Sources
Interference is classified into internal interference and external interference by source or uplink
interference and downlink interference by direction.
 Internal interference  External interference

 Intermodulation interference  Interference from the CDMA
 Co-channel interference (CCI) and network
adjacent-channel interference (ACI)  Interference from repeaters
 Coverage overlap interference due to  Interference from other radio
improper network planning systems
 CCI and ACI due to improper frequency
planning

Impacts of Interference
Strong interference
Many complaints from subscribers Poor network performance
 Call failure, poor voice quality, or  Unsatisfactory KPI measurement

even call drop results
 Dial-up access failure, low speed, or  Unsatisfactory DT and CQT results
network disconnection  High percentage of MRs involving high
level and low quality

Interference Determination
 1. Interference band measurement
 The interference band refers to the uplink interference level ranking of idle channels carried in
the RF RESOURCE INDICATION message sent from the BTS to the BSC. Level rankings can
be classified into five grades. The interference band threshold of each grade can be set on the
local maintenance terminal (LMT). A higher grade indicates a higher interference level.
Generally, when an idle channel falls in interference band 4 or interference band 5, it is
deemed that interference exists.
 Note: Interference band algorithm I must be used during interference detection
Interference Band Interference Interference Band
Algorithm Band Algorithm I Algorithm II HW I HW II
Interference band threshold
110 110 Interference
0 (–dBm) [–110, –105) [–110, –105)
band 1
105 105 Interference
1 (–dBm) [–105, –98) [–105, –100)
band 2
98 100 Interference
2 (–dBm) [–98, –92) [–100, –95)
Interference band threshold band 3
92 95 Interference
3 (–dBm) [–92, –87) [–95, –85)
87 85 Interference
4 (–dBm) [87, –47) [–85, –47)
85 75
5 (–dBm)

 2. HQI measurement
 The high quality index (HQI) measures the uplink and downlink signal quality in the MR. The
HQI reflects the equivalent bit error rate (BER) before channel decoding. Generally, if the
percentage of MRs involving RXQUAL_6 and RXQUAL_7 is greater than 3%, there is a high
probability that interference exists.
Measurement Data Range Voice Quality Level (Reported

C/I [DB] Relationship with KPIs
(%) Value Specified by 3GPP)
23 BER < 0.2% RXQUAL_0

19 0.2% < BER < 0.4% RXQUAL_1
17 RXQUAL_2
0.4% < BER < 0.8%
Better C/I  smaller
15 0.8% < BER < 1.6% RXQUAL_3
BER  better RXQUAL
13
1.6% < BER < 3.2%
RXQUAL_4  better network KPI
measurement results
11 RXQUAL_5
3.2% < BER < 6.4%
8 6.4% < BER < 12.8% RXQUAL_6
4 12.8% < BER RXQUAL_7

 3. Uplink frequency scanning by using the LMT
 Taking statistics by means of uplink frequency scanning is similar to measuring interference
bands. It measures the uplink interference level ranking of idle channels. Uplink frequency can
be scanned by manual operation or by using the LMT.

 Frequency scanning by using the frequency scanner
The frequency scanner (such as Tektronix YBT250 and Agilent 9340 A), which is
connected to a yagi antenna, is used to locate the interference source onsite.
1. The interference strength and interference characteristics in the frequency domain
can be obtained by using the frequency scanner.
2. The interference source can be roughly located by using cross-connected lines.
Possible zone of the

interference source Maximum interference
direction 1
Affected cell 2
Maximum
interference
direction 2 Affected cell 1

Contents
 Interference
 Principles
 Cases

Page 95
Troubleshooting Trigger Conditions
 Trigger conditions for troubleshooting uplink interference

 The percentage of MRs involving interference bands 4 and 5 is greater than
5% or the percentage of MRs involving interference bands 3, 4, and 5 is
greater than 20%.
 The percentage of MRs involving high level (greater than –98 dBm) and low
quality (RXQUAL_6 and RXQUAL_7) is greater than 3%.
 Trigger conditions for troubleshooting downlink interference
 The percentage of MRs involving high level (greater than –98 dBm) and low
quality (RXQUAL_6 and RXQUAL_7) is greater than 3%.

Page 96
 Step 1 Confirm that the problems are caused by interference.
 Scenarios: swap, capacity expansion, and upgrade
 In the swap scenario, focus the check on power matching, parameter mapping, and parameter
configuration mapping.
 In the capacity expansion scenario, focus the check on frequency planning.
 In the upgrade scenario, check the compatibility of version features and whether parameters are
changed.
 When the following conditions are met, it is deemed that the problems are
caused by interference:
 1. Troubleshooting trigger conditions are met.
 2. The interference band threshold and measurement algorithm are set correctly.
 Step 2 Perform the following operations:

 RF channel check, equipment fault and alarm check, power matching check, parameter
configuration check, analysis of live network data, uplink interference check, and downlink
interference check.

Mapping Between Huawei's Interference
Band Counters and Peer Vendors'
 The algorithm for measuring the interference band varies with vendors. Before comparing peer
vendors' interference band counters, check whether Huawei's algorithm for measuring the
interference band is different from peer vendors', to rule out exceptions caused by differences
between measurement algorithms.
Interference
HW MOTO ERICSSON NOKIA
Band
[interference Averaging Process Boundary
1 < Interference band threshold 1 0 to [interfer_bands[0]] (0, [LIMIT1]] 0](Fixed value -110 dBm) to [interference
Averaging Process Boundary 1]
[Interference band threshold 1, [interfer_bands[0]] to [interference Averaging Process Boundary 1] to

2 ([LIMIT1], [LIMIT2]]
Interference band threshold 2) [interfer_bands[1]] [interference Averaging Process Boundary 2]


[interference Averaging Process Boundary 4] to

[interfer_bands[3]] to
5 ≥ Interference band threshold 4 ([LIMIT4], 63] [interference Averaging Process Boundary
[interfer_bands[4]]
5](Fixed value -47 dBm)
1. It is unknown whether the upper and
Mapping lower threshold values are included.
1. It is unknown whether the upper and lower
between 2. Interference band 5 fails to be
threshold values are included.
Huawei's mapped.
2. Parameter names in documents are
and peer 3. Parameter names in documents are
inconsistent with those on the live network.
vendors' inconsistent with those on the live
network.

Differences Between Interference Band
Algorithms
 Differences between interference band algorithms lead to the fluctuation of interference band counter values.
Currently, Huawei uses interference band algorithm I and interference band algorithm II to measure
interference band counters.
 Interference band algorithm I

 The BTS calculates the uplink received signal strength indicator (RSSI) as follows: When the MS sends a
burst, the BTS obtains two (I^2 + Q^2) values (diversity power and main power). Then the BTS converts the
two values into RSSI values expressed in dBm and uses the larger value as the uplink RSSI. The reported
uplink level (dBm) is obtained by averaging RSSIs in a measurement period.
 Interference band algorithm II

 The BTS calculates the uplink RSSI as follows: When the MS sends a burst, the BTS obtains two (I^2 + Q^2)
values (diversity power and main power). Then the BTS uses the larger value to calculate the uplink RSSI. The
uplink level power is obtained by averaging power values (in mW) in a measurement period. Then the BTS
converts the uplink level power to the dBm value and reports the uplink level (dBm).
 Note 1: In the case of multipath or burst interference, the measurement result obtained by using
algorithm II is higher than that obtained by using algorithm I due to different calculating methods.
 Note 2: Interference band algorithm I must be used for interference detection on the live network.

Required Actions for Troubleshooting
Interference Problems
No. Required Action Implementation Condition Purpose and Requirements Deliverables
(1) Check whether any fault alarms are generated due to VSWR exceptions, unstable clock,
intermittent transmission, or TRX communication/wireless link faults. These alarms affect the
transmission and reception performance. Check whether any cells with low TRX/channel List of equipment fault alarms
usage exist. When such cells exist, traffic is shifted to surrounding cells, which affects the
performance of surrounding cells.
Check of (2) Check whether the main and diversity receive levels of channels are normal and whether List of cells with abnormal main
hardware, the configuration and performance of repeaters and TMAs meet corresponding requirements. and diversity signals
1 channels, and Mandatory (3) Check whether the antenna and jumper connectors are correctly connected, whether List of cells with incorrectly
the antenna combiners function normally, whether the SWR is normal, and whether the antenna is aged. connected antennas
system List of cells with abnormal
(4) Check whether intermodulation interference exists.
intermodulation
(5) Check the transmit power: List of power mapping
(a) In swap scenarios, check whether coverage overlaps exist because the power after swap deliverables
is not matched with that before swap. List of cells with abnormal
(b) Check whether the power configuration is obviously abnormal in optimization scenarios. power configurations
Check of Check whether the configurations of the following parameters are proper: power control
Mandatory List of parameters for network-
2 parameters and parameters, PS service-related parameters, interference reduction parameters, and
wide check
configurations parameters regarding the feature of immunity to interference.
(1) Analyze interference characteristics in the frequency domain by using the LMT to scan
Check of uplink
Implemented when uplink uplink frequencies. Uplink external interference
3 external
interference exists. (2) Analyze interference characteristics in the time domain based on raw statistics on the analysis report
interference
interference band.
(1) Interference caused by the increase of CS and PS traffic: Analyze the relationship
between CS traffic, TCHH/TCHF ratio, as well as the number of channels occupied by PS HQI, interference band, and
services and the HQI, to determine whether the increase of traffic aggravates internal traffic trend analysis
interference.
(2) Coverage overlap: Analyze whether coverage overlaps exist, causing interference to Coverage overlap cell list
Implemented when uplink intra-frequency cells and adjacent-frequency cells; analyze the network structure index to Network structure index
Check of internal check whether internal interference is caused by the improper network structure. analysis report
4 and downlink interference
interference
exist. Intra-frequency and adjacent-
(3) Internal CCI and ACI: Check whether frequency planning is proper, whether intra- and
frequency analysis report
adjacent-frequency planning is proper, or whether it is necessary to perform frequency
Frequency replanning analysis
replanning across the network.
deliverable
(4) Frequency resource restriction: By analyzing Reuse Rate of Frequency, check whether Network frequency planning
network frequency resources are restricted, increasing internal interference. analysis report
Check of Implemented when downlink
It is difficult to judge whether a problem is caused by downlink external interference.
downlink interference exists and Frequency scanning analysis
5 Therefore, the frequency scanner is used to scan frequencies to analyze whether downlink
external internal interference is not report
external interference exists.
interference the primary reason.

Action 1: Hardware, Channel, and Antenna
System Check
 Purpose: Check and rectify hardware faults, RF channel faults, intermodulation interference, and incorrect power
configuration that affects transmit and reception of the BTS.
 Principle: Carefully check alarms, traffic statistics, and power configuration to locate hardware faults and channel
faults.
Check Item Outputs Data Sources Tools and Guides Issue Closure
(1) Check whether any fault alarms are generated due to VSWR
exceptions, unstable clock, intermittent transmission, or TRX
communication/wireless link faults. These alarms affect the
transmission and reception performance. Check whether any cells List of equipment fault alarms
with low TRX/channel usage exist. When such cells exist, traffic is
shifted to surrounding cells, which affects the performance of OMStar, FMA, and M2000
surrounding cells. (1) Alarm log Detection and
(2) Raw traffic statistics Troubleshooting of GSM
(2) Check whether the main and diversity receive levels of channels
List of cells with abnormal (3) Intermodulation data obtained RF Tunnel Faults:
are normal and whether the configuration and performance of
main and diversity signals through the burst test in idle state Principle + Tools + Cases
repeaters and TMAs meet corresponding requirements. Rectify equipment
+ Deliverables.PPT
(3) Check whether the antenna and jumper connectors are correctly exceptions and power
List of cells with incorrectly
connected, whether combiners function normally, whether the SWR exceptions, and then
connected antennas
is normal, and whether the antenna is aged. export cases.
List of cells with abnormal
(4) Check whether intermodulation interference exists.
intermodulation
(1) Power configuration before swap
(5) Check the transmit power:
(2) Power of the TRXs, transmit
(a) Check whether the coverage shrinks due to not mapping (a) List of power mapping
power at the top of the BTS cabinet
power before the swap in swap scenarios or combiner loss in deliverables Power mapping tool and
(TOC), combiner loss, and duplexer
capacity expansion scenarios. (b) List of cells with abnormal OMStar
loss on a typical site before swap
(b) Check whether the power configuration is obviously abnormal power configurations
(3) Power configuration on the live
in optimization scenarios.
network
 Procedure
See the Detection and Troubleshooting of GSM RF Tunnel Faults: Principle + Tools + Cases + Deliverables.

 Purpose: Check whether the configurations of the following parameters are proper: power control parameters,
PS service-related parameters, interference reduction parameters, and parameters regarding the feature of
immunity to interference.
 Principle: Compare parameters with the baselines and before and after the swap to check whether parameters
are properly configured. Check the configurations of 17 core parameters and 66 power control parameters.

Parameter check
(1) MML configuration file
OMStar and PFMStudio result list (list of cells
(2) Intelligent parameter
whose parameters Adjust improper
baseline, user-defined
GSM Parameters Check: Check do not comply with parameter
comparison baselines, or
Rules + Tools + Cases + baselines or the configurations and
parameter configurations before
Deliverables.ppt and coverage network before the export cases.
the swap (applicable to the
parameter list (focus) swap, with reasons
swap scenario)
provided)
 Procedure
See the GSM Parameters Check: Check Rules + Tools + Cases + Deliverables.

Interference-related core parameter list
Feature and
Introduction to Features and Parameters Version Requirements Impact
Parameter
The algorithm for measuring the interference band varies with vendors. Before comparing peer vendors'
Interference
interference band counters, check whether Huawei's algorithm for measuring the interference band is
band thresholds R8+ Statistics
different from peer vendors', to rule out exceptions caused by differences between measurement algorithms.
0 to 5
The BTS calculates the uplink received signal strength indicator (RSSI) as follows: When the MS sends a
burst, the BTS obtains two (I^2 + Q^2) values (diversity power and main power). Then the BTS converts the
Interference
two values into RSSI values expressed in dBm and uses the larger value as the uplink RSSI. The reported R8+ Statistics
band algorithm
uplink level (dBm) is obtained by averaging RSSIs in a measurement period.
Note 2: Interference band algorithm I must be used for interference detection on the live network.
The DTX function permits the transmitter to stop power transmission when there is no voice input, to achieve BSC6900 V900R011 and later
Uplink and the following improvements: For uplink, the power consumption of the MS is decreased, reducing intra-
Uplink and
downlink DTX system interference; for downlink, the power consumption of the BTS is decreased, reducing intra-system (The downlink DTX is enabled and the
downlink
function interference and intra-BTS crossmodulation; for the entire network, frequency interference is reduced and the cooperation of the CN is required.)
network quality is improved.
The transmit power of radio links is controlled to reduce the transmit power with good transmission quality
Uplink and
ensured even if the transmit power does not reach the maximum value. In this way, the transmission quality is Uplink and
downlink CS BSC6900 V900R011 and later
better than the predefined threshold, the average transmit power of the MS and the BTS is decreased, and downlink
power control
interference in other channels is reduced.
Version requirements in phase 2
Outside China
GBTS9.0 BTS3000V100R009C00SPC090
GBTS12.0 BTS3000V100R012C00SPC046
GBSS13.0 BTS3000V100R013C00SPC015
When PS DTX is enabled, power transmission stops when PDCHs are idle or not occupied by TBFs, to In China
PS downlink
reduce network interference, improve the performance of CS and PS services, improve the network quality, GBSS9.0 BTS3000V300R009C00SPC050 Downlink
DTX phase 2
and reduce the power consumption of the BTS. GBSS9.1 BTS3000V300R009C01SPC033
GBSS13.0 BTS3000 V300R013C00SPC011
MBTS:
SRAN3.0 BTS3900 V100R002C00SPC340
SRAN5.0 BTS3900 V100R003C00SPC360
SRAN6.0 BTS3900 V100R004C00SPC121
The BSC determines PS power control after preprocessing the downlink measurement quality. If power
adjustment is required, the BSC calculates the power attenuation value by using the PS power control
PS downlink BSC: R013 and later
algorithm and delivers the value to the BTS. The BTS adjusts the transmit power on the current radio block Downlink
power control BTS: R013 and later
based on the power attenuation value. In this way, the transmit power of the BTS is decreased and the
network quality is improved.

Feature and Version
Description Impact
Parameter Requirements
PS uplink power The MS adjusts the uplink output power based on the downlink receive level and decreases the
R8+ Uplink
control transmit power, reducing interference in other channels.
Interference cancellation combining (ICC) is a technology that combines multiple antennas to

suppress interference. The ICC is developed based on maximal ratio combining (MRC) and
eliminates interference using only the space relevancy of interference. The EICC (also STIRC)
eliminates interference based on both the space relevancy and time relevancy.
BSC6900
EICC function It is recommended the EICC function be enabled only for top cells where strong interference V900R011 and Uplink
exists. later
It is deemed that strong interference exists in a cell in either of the following cases:
1. Percentage of MRs involving uplink interference bands 4 and 5 > 15%
2. Percentage of MRs involving uplink RXQUAL_6 and RXQUAL_7 > 5%
This feature is
When PS uplink DTX is enabled, uplink dummy blocks are not sent during the inactive period of recommended
PS uplink DTX Uplink
extended uplink TBFs, to decrease the transmit power and reduce network interference. for
R014SPC510
If the MS supports extended uplink TBFs but does not support the uplink DTX, or the MS
supports the uplink DTX, which, however, is not enabled, the uplink slow scheduling function is
PS uplink slow enabled to reduce interference. If the current MS supports inactive period of extended uplink
R014 Uplink
scheduling TBFs when the network side schedules the uplink MS, the network side reduces the MS
scheduling frequency to reduce the MS' attempts to send uplink dummy blocks, reducing uplink
interference and reserving Um interfaces for other MSs transmitting data.
If the PS downlink DTX phase 2 is enabled, the power is not transmitted for dummy blocks that do
not carry effective USFs. During data transmission, if no NACK block or new block is sent, the
network side sends PACK blocks. If PACK retransmission optimization is enabled, the network
PS downlink slow side sends PACK blocks repeatedly, to increase the data reception probability (controlled by
R014 Downlink
scheduling SptDlTbfSchedOptimize) and decrease the dummy block sending probability (reducing PS DTX
activations and associated gains). Therefore, downlink slow scheduling is used, which is
controlled by DlPACKSENDPERIOD. The network side sends PACK blocks periodically based
on the parameter value, increasing gains resulting from the downlink DTX.

Action 3: Uplink External Interference
Analysis
 Implementation condition: optional. Implemented when uplink interference exists.
 Purpose: Check whether the interference is caused by external factors by analyzing its time- and frequency-domain
characteristics. If yes, identify the external interference type.
 Principle: differences between external interference and internal interference

 Frequency-domain characteristics: Compared with internal interference, the frequency spectrum of external interference differs greatly from
that on the GSM network. For example, interference on the CDMA network decreases with the increase of frequencies; the interference unit
has strong interference across the frequency band or irregular bursts occur. Frequency domain analysis is aimed to measure the interference
level of different frequencies using the uplink frequency scanning function of the LMT, to obtain frequency-domain characteristics of the
interference spectrum. For details about the uplink frequency scanning function, see the Detection and Troubleshooting of GSM RF Tunnel
Faults: Principle + Tools + Cases + Deliverables.
Time-domain characteristics: External interference does not change with traffic, but varies with time periods. For example, interference
caused by a repeater is always strong, or interference occurs only in a fixed time period.

Purpose and
Requirements
Uplink frequency scanning of the
(1) Analyze the frequency-
LMT, data playback tool,
domain characteristics of
M2000, PRS, OMStar traffic
interference by using the uplink
(1) Uplink frequency statistics analysis software Uplink external Confirm external
frequency scanning of the LMT.
scanning data Notification: The OMStar interference interference and clear
(2) Analyze time-domain
(2) Raw traffic statistics automatic interference analysis analysis report interference.
characteristics of interference
prototype tool has been developed.
based on raw interference band
The formal tool will be launched
statistics.
with the profession service.

Confirmation
 Procedure
1. Analyze time-domain characteristics of
interference.
Analyze the change trend of interference bands and the HQI based
on traffic statistics and then conduct a comprehensive analysis
based on the change trend of traffic. Generally, external interference
does not change with traffic. Some external interference is strong in
the whole period, for example, interference caused by the repeater,
and some interference occurs suddenly in a short duration.
Tools: traffic statistics analysis tools, such as the PRS

and M2000
Input: raw traffic statistics

Output: interference time change trend analysis
Figures on the right show that the percentage of MRs
involving interference bands 3, 4, and 5 is high all day.
Internal interference hardly exists in wee hours (idle
time). Therefore, you can determine the interference is
caused by external factors.

Analysis
2. Analyze frequency-domain characteristics of interference
Analyze characteristics of uplink interference frequency spectra after uplink interference frequency scanning.
Different interference sources lead to different uplink frequency-domain characteristics. For example,
intermodulation causes the level of affected frequencies to increase; interference from the CDMA network becomes
weaker with the increase of frequencies; the wideband repeater causes uplink frequency bands or certain frequency
bands to improve when the traffic is heavy; the communication blocking device causes continuous increase in the
level; an indoor distributed system causes high level of operating frequencies but low level of noise floor.
Tools: LMT (uplink frequency scanning)
Input: uplink frequency scanning result
Output: interference frequency analysis
The figure on the right shows that

interference becomes weaker with the
increase of frequency.
This shows that interference is caused by
the CDMA network.

Analysis of Uplink Interference Detection on
the GSM Network (Professional Service)
Detection of interference caused by Detection of interference caused by
a wideband repeater and active an indoor distributed system and
devices traffic
CDMA interference detection Intermodulation interference detection

Action 4: Internal Interference Analysis
 Implementation condition: optional. This Operation is implemented when uplink and downlink interference
exists.
 Purpose: Check whether internal interference exists and find out the cause of internal interference.
 Principle: Check whether internal interference exists based on two-dimensional level quality distribution in
the case of swap, upgrade, or a network with the installed base.
Internal interference may be caused by traffic increase, coverage overlap, intra-network CCI and ACI, or restricted
frequency resources.
Purpose and Requirements Data Sources Tools and Guides Outputs Issue Closure
(1) Interference caused by the increase of CS and
PS traffic: Analyze the relationship between CS
Traffic statistics analysis HQI and interference Reduce internal interference based on the analysis
traffic, TCHH/TCHF ratio, as well as the number of (1) MML configuration file
software, such as the M2000, band traffic trend result, including CS interference reduction and PS
channels occupied by PS services and the HQI, to (2) Raw traffic statistics
PRS, and OMStar analysis interference reduction.
determine whether the increase of traffic aggravates
internal interference.
(2) Coverage overlap: Analyze whether coverage
(1) Engineering parameters, (1) Geographic software,
overlaps exist, causing interference to intra-
MML configuration file, and e- such as Nastar and Mapinfo Overlap cell list (1) Adjust RF parameters (tilt and height) and the
frequency cells and adjacent-frequency cells;
map (2) Signaling analysis toll Network structure index power to solve the overlap problem.
analyze the network structure index to check
(2) Top cell signaling tracing such as the PFMStudio analysis report (2) Provide the underlying network solution of
whether internal interference is caused by the
(3) DT data (3) DT analysis software, (professional service) professional service.
improper network structure.
(4) MR tracing data such as the Probe and Tems
(3) Internal CCI and ACI: Check whether frequency Co- and adjacent-
Intra- and adjacent-frequency: Adjust partial
planning is proper, whether intra- and adjacent- Engineering parameters and Nastar, MapInfo, and channel interference
frequencies or adjust cell coverage.
frequency planning is proper, or whether it is MML configuration file (frequency frequency replanning in this analysis report
CCI and ACI caused by improper frequency planning
necessary to perform frequency replanning across configuration) document Frequency replanning
across the network: Perform frequency replanning.
the network. analysis deliverable
Network frequency resource restriction:
(4) Frequency resource restriction: By analyzing (1) Optimize frequency resources in important areas.
Engineering parameters and
Reuse Rate of Frequency, check whether network Network frequency (2) Communicate with the customer on the analysis
MML configuration file (frequency Nastar and MapInfo
frequency resources are restricted, increasing planning analysis report result, and prepare the solution together (including
configuration)
internal interference. frequency replanning, antenna replacement, and
traffic migration).

Action 4: Analysis of Internal Interference
Caused by Traffic Increase
 Procedure
1. Interference caused by traffic increase: In the swap or installed base scenario, when the HQI deteriorates, analyze
whether the coupling relationship exists between the change of CS and PS services and the change in the HQI.
Principle: Analyze the relationship between CS traffic,

TCHH/TCHF ratio, as well as the number of channels
occupied by PS services and the HQI to check whether
internal interference becomes stronger due to the traffic
increase.
1. In the case of network swapping, focus the check on
the change trend of CS and PS traffic, TCHH/TCHF
ratio, average number of occupied PDCHs, and the
HQI before and after the swap.
2. In the case of a network with the installed base, focus
the check on whether the CS and PS traffic and the
average number of occupied PDCHs are consistent
with the HQI change trend. The figure above shows the change trend of the uplink HQI,
Tool: traffic statistics analysis tool downlink HQI, and PS traffic. The figure shows that HQI
Input: raw traffic measurement deterioration coincides with PS traffic increase.
Output: traffic and HQI change trend

Action 4: Internal Interference Confirmation —
Evaluating the Service Type Causing
Interference
 Principle: For a network with the installed base, evaluate the power emitted from the PS service and CS
service to locate the source of internal interference (CS service or PS service). The BCCH TRX and TCH TRX
use different frequency sets. Therefore, interference in the BCCH TRX is separated from interference in a
common TCH TRX and 900 MHz interference and 1800 MHz interference are separate.
 Tool: traffic statistics analysis tool and PFMStudio
 Input: raw traffic statistics and MML configuration
 Output: CS and PS interference analysis
Interference
Influence Factor
Source
When GSM channels are in service, non-BCCH
CS DTX (percentage of power
TRXs do not require full power transmission.
CS traffic transmission timeslots)
Different interference reduction measures
volume CS power control
should be developed for different services Percentage of TCHHs
during the calculation of total network Number of PS DTX (percentage of dummy
interference to correctly quantify interference. activated blocks)
channels for
PS power control
PS services

Action 4: Internal Interference Confirmation —
Evaluating the Service Type Causing Interference
The total amount of interference is calculated as follows:
(K3014: Traffic Volume on TCH – K3034: TCHH Traffic Volume) x Interference of per Erlang traffic (TCHF) +
K3034: TCHH Traffic Volume x Interference of per Erlang traffic (TCHH) + (R9207: Total Number of Downlink
PDTCH/PACCH Blocks /3600/50 – Number of static PDCHs configured on the BCCH TRX) x (1 – Average power control
amplitude of each PS channel)

Amount of interference from CS services = (((S4525 + S4527 + S4529 + S4531 + S4533 + S4535 + S4537 + S4539) +
(S4541 + S4543 + S4545 + S4547 + S4549)/2)/(50 x 3600)) x Power of the BCCH TRX x Power (10, AS3241A x 2/10) +
(S4551 + S4553 + S4555/2)/(50 x 3600)) x Power of the BCCH TRX x Power (10, AS3241NA x 2/10)
Amount of interference from PS services = (R9207/(50 x 3600) – Number of static PDCHs configured on the BCCH TRX)
x (1 – (R9218 + R9219 + R9220)/(R9207 x 100)) x Power of the BCCH TRX

Action 4: Internal Interference Analysis — Coverage
Overlap
2. Interference caused by coverage overlap
 Principle: Coverage overlap means that the serving range of certain cells on the live network is far larger than the
actual serving range due to improper configuration of the power, orientation, downtilt, and site height, causing
interference to intra- or adjacent-frequency cells.
For how to judge the coverage overlap, see the section about coverage analysis in this document.
Coverage overlap can be determined from the following aspects:

1. Check whether TA traffic is heavy based on TA traffic
statistics.
2. Locate coverage overlap by means of DT.
3. Determine coverage overlap using the remote frequency lock
test.
Tool: DT tool, such as the Tems and Probe
Input: engineering parameters and DT logs
Output: DT analysis report
The figure on the right shows that three intra-
frequency cells exist near the area where the call
quality deteriorates. Disable intra-frequency TRXs in
the background. After intra-frequency TRXs in cell B
are disabled, call quality is resumed to the normal
level. Therefore, it is concluded that the coverage
overlap of cell B leads to poor call quality.

Network Structure Index Evaluation
(Professional Service) The network structure
index is used for
assessing the health of
the network structure in an
Network structure: distribution and configuration of BTSs on area. It indicates the
the network, as well as the configuration of antenna number of overlapping
TRXs of cells with strong
parameters, including the distance between two sites, site signals in the area. If the
height, antenna direction and downtilt, cell TRX configuration, value of this index is large,
Network the network structure is
and the distribution of indoor and outdoor sites, repeaters,
structure complicated, making
900 MHz sites, and 1800 MHz sites. frequency planning
index
difficult.
Network structure index: Considering the capacity on the
basis of the CCI index indicates that in the case of the same Avg. TRX Overlapping
frequency resources, the more complex the network structure configuration coverage
index is, the more difficult frequency planning is, and the
stronger the interference is.
In the case of a larger network structure index, generally the % of high-,
% of high-,
low-, and
underlying network solution for professional services is used Avg. site
Redundant
coverage
Coverage
overlap
low-, and
medium-
middle
Avg. BTS
height
Avg. BTS downtilt
Traffic density distance interference
to solve the problem. percentage height sites
sites
Assume that cell A is the serving cell (Server) and cell B is the interfering cell
(Interference).
Co-frequency correlation factor: indicates the overlapping coverage of two cells. If
both the capacity (numbers of TRXs of Server and Interference) and frequency are the Network
same, the higher overlapping coverage indicates stronger interference between the cells. structure
Number of MRs involving cell A that may be index
affected by the intra-frequency cell B
formulas
Number of MRs involving cell A adopted
Number of MRs involving cell A that may be affected by the intra- by China
frequency cell B =∑Number of MRs in each C/I interval x Corresponding Mobile
interference probability
Overlapping coverage =
Network structure index =

Action 4: Internal Interference Analysis — CCI
and ACI
3. CCI and ACI analysis
Most internal interference on the live network is CCI or ACI between different BTSs or MSs. Frequency planning on
the network affects the overall network performance. Therefore, analysis should be conducted around current
frequency planning (check whether frequency planning is proper and whether frequency replanning is necessary).
Internal CCI or ACI on the live network is classified by range into partial frequency problem and network-wide
frequency problem.
Partial frequency problem

CCI or ACI occurs in certain areas because
frequency is modified improperly in certain cells
during capacity expansion or optimization.
Therefore, partial frequency adjustment is
required.
Manually adjust frequencies

using engineering parameters
and geographic display tools,
such as the Nastar, Mapinfo, and
OMStar.

Action 4: Internal Interference Analysis — CCI
and ACI
Network-wide frequency problem

Network-wide frequency planning requires evaluation
in the following aspects:
1. Whether frequency usage of BCCHs and TCHs is
proper
2. Whether the network structure is changed greatly
(deployment, capacity expansion, capacity
reduction, and traffic increase)
3. KPIs on the live network
4. Frequency replanning gains on the live network
based on the interference matrix
Output: frequency replanning evaluation report
For details, see the GBSS R13 Frequency Planning Solution and the section about
frequency replanning in this document.

Action 4: Analysis of Internal Interference
Caused by Frequency Resource Restriction
4. Interference caused by frequency resource restriction
 Network frequency resources are limited. If network frequency resources are insufficient, the Reuse Rate of
Frequency on the entire network is decreased (Reuse Rate of Frequency = Total number of available
ARFCNs/Number of TRXs in a cell) and internal interference in the network becomes stronger, leading to
capacity expansion failure. Evaluation of network frequency resource restriction is mainly based on the Reuse
Rate of Frequency.
 Evaluation method
 Proper Reuse Rate of Frequency > 9
 Optimization solution
 Increase the TCHH percentage and the capacity (voice quality deteriorates).
 Enable the VAMOS function (depending on the percentage of MSs supporting the VAMOS function).
 Expand the capacity by enabling 1800 MHz.
 Reduce the capacity of large-capacity cells on the live network.
 Enable load sharing, for example, migrate traffic between the GSM and 3G networks or between the GSM and
4G networks.
 Replace antennas, for example, use antennas that perform better in terms of immunity to interference.

Action 5: Downlink External Interference
Confirmation
 Implementation condition: optional. Implemented when downlink interference exists and internal
interference is not the primary reason.
 Purpose: Check whether downlink external interference exists. If downlink external interference exists,
identify the interference type.
 Principle: If internal CCI or ACI does not exist, and the percentage of MRs involving high level (greater
than –90 dBm) and low quality (RXQUAL_6 and RXQUAL_7) is greater than 5%, downlink external
interference may exist. The source of downlink external interference is determined only by frequency
scanning using the frequency scanner, not the HQI.
 Data sources and tools: frequency scanner (such as Tektronix YBT250 and Agilent 9340 A) and yagi
antenna
 Output: Interference source location
Purpose and Tools and Issue

Data Sources Outputs
Requirements Guides Closure
It is difficult to
confirm whether
downlink external
interference exists.
Frequency Confirm external
Therefore, scan Downlink Frequency
scanning interference and
frequencies and frequency scanner and data
analysis clear
analyze frequency scanning data playback tool
report interference.
scanning results to
check whether
downlink external The scanning method varies with the frequency
interference exists. scanner.

Root Cause Location Based on Raw MRs (Professional
Service, Being Developed on the OMStar)
 The tool can be used to display root causes located based on raw MRs and export the coverage
root causes for all cells and top cells in one-click mode.
Interference
Interfering Interfering Interfering Structure direction
cell service frequency interference analysis
location location location location
Interference output table
ACI
CS ACI
PS ARFCN on Number of
Interference Interference ARFCN on Average
Total Interference CCI ARFCN ACI ARFCN CCI ARFCN the Non- Distance Coverage MRs with the
Poor-Quality Interferen Interference Interference Traffic on Traffic on the Non- Average Azimuth Level of
Server CI Interference % Interference Traffic on on the on the on the Non- BCCH Between Overlap High-Level
Signals % ce CI BCCH BSIC the BCCH the Non- BCCH TA Relationship Affected
Traffic the Non- BCCH TRX BCCH TRX BCCH TRX TRX Sites Type Neighboring
TRX BCCH TRX TRX Signals
BCCH TRX (Interferen Cell
(Server)
ce)
49199 6.72% 0.58% 49178 17 61 1058.52 203.59 92.80 762.12 [17] [13, 17] 1.14 4328.97 no Opposite 500 -77.40
Neighboring
49198 5.15% 0.09% 48138 3 62 62.88 61.02 0.05 0.80 [4] 1.56 1580.77 no cell including 350 -79.71
the Server
49198 0.15% 0.09% 32752 5 60 0 0 0 0 [4] [16] [15] 3.10 1671.89 no Parallel 10 -79.71
Automatic location of frequency

optimization suggestions
 Tool: OMStar V5R6 (prototype

Frequency optimization suggestions
tool) CI First Optimization Second Optimization Third Optimization
34816 61---->26 65---->85 24---->77

 Output: frequency optimization 48128 64---->20 63---->28
suggestions obtained with the tool 32772 57---->35 22---->11 28---->30

32773 89---->79 6---->22 17---->14

Interference-Related Deliverable

Contents
 Interference
 Principles
 Cases

Page 121
Case 1: Call Drop Due to Internal Interference
 Overview
Project for MTN in Country S: After the peer vendor's equipment was swapped, the call drop rate remained high.
The swapped network, which consists of 900 MHz cells and CoBCCH cells, is located in the urban area. The
analysis result shows that the problem occurred because the call quality in 900 MHz cells deteriorated. To reduce
the call drop rate to the required level, interference reduction measures, such as TCHH rate improvement and
PDCH ratio control, were adopted.
 Step 1 Confirm that the high call drop rate is caused by interference.
 After the swap, the downlink HQI in 900 MHz cells deteriorated, which led to high call drop rates.
Required Action Analysis Data Analysis and Data Analysis Next Issue Closure Result
Symptom Conclusion Operation
Action1: RF channel check No exception Normal N/A N/A
Action2: parameter configuration

No exception Normal N/A N/A
check
Action3: uplink external

interference check
The number of occupied
PDCHs was greater than
More PDCHs were occupied, Adjust parameter
Action4: internal interference that before the swap and The call drop
leading to negative gains of configurations to restrict
check the interference trend is rate is improved.
interference. the usage of PDCHs.
consistent with the PS
traffic trend.

Case 1: Call Drop Due to Internal Interference
 Analysis
PS algorithm differences led

the number of occupied
PDCHs after the swap to be
greater than that before the
swap. Then interference
became strong and the call
drop rate of underlaid subcells
increased.

Case 2: Intermodulation Interference Check
 Overview
After the swap of an office, the percentage of MRs involving interference bands 4 and 5 increased in some cells.
 Step 1 Confirm that the increase in the percentage of MRs involving interference bands 4 and 5 is
caused by interference.
 After the swap, the percentage of MRs involving interference bands 4 and 5 significantly increased.

Check basic items.
A few problems were found during the RF channel check.

Case 2: Intermodulation Interference Check
 Check
Cell Name Troubleshooting Method and Conclusion

Metal scraps were found at the connector of the cable between the combiner
Cell 1 and the splitter, causing passive intermodulation. After metal scraps were
cleared, the problem was resolved.
Passive intermodulation was caused by jumpers. After jumpers were replaced,
Cell 2
the problem was resolved.
Passive intermodulation was caused by a 30 dB coupler. The coupler was
Cell 3
removed after the engineers' confirmation. The problem was resolved.
Passive intermodulation was caused by an antenna. The antenna may be
Cell 4
damaged by a lightning strike. Replacing the antenna may resolve the problem.
Intermodulation was caused by a jumper. The jumper at the top of the BTS
Cell 5
cabinet must be replaced.

A few problems were found during the RF channel check. After problems were resolved, the percentage of MRs involving
interference bands 4 and 5 was resumed to the normal level. Then issue closure was performed and the summary report
was exported.

Case 3: High Percentage of MRs Involving Interference
Bands Due to Incorrect Connection of the Antenna System
 Overview
After the BTS in an office was activated, interference bands 4 and 5 frequently occurred in traffic statistics, the
success rate of inter-cell handovers was low, and the congestion rate was greater than 5%. No alarm was generated
in the OMC.
 Step 1 Confirm that the problems are caused by interference.

 Interference bands 4 and 5 frequently occurred in traffic statistics and the success rate of inter-cell
handovers was low.

 Check RF channels.
 According to inter-cell handover performance statistics of the BTS, handover failures occurred between cell
1 and cell 3.
 Analysis of the high congestion rate found that the uplink and downlink balance levels were in most cases
Rank 1 and Rank 11. This indicates that the uplink and downlink traffic was unbalanced.
 The percentage of MRs involving interference bands 4 and 5 was high and the success rate of inter-cell
handovers was low. This may be caused by incorrect connection of the antenna system.

The onsite check found that the antenna system was incorrectly connected. Crossed pair connection was adopted for
the antenna systems of cell 1, cell 2, and cell 3. As a result, transmitting antennas of cell 1 and cell 3 were
respectively located in the same cell, but their receiving antennas were respectively located in another cell. After
antennas were connected correctly, interference bands 4 and 5 disappeared, leading to normal handovers and no
congestion.

Case 4: Interference Between the CDMA and the
GSM Networks
 Overview
In an office, uplink interference was strong in certain cells and the percentage of MRs involving interference bands
4 and 5 was greater than 30%. Poor call quality, call drops, or call connection failures frequently occurred, causing
large number of customer complaints. The BTSs could hardly provide normal communications services.

 The percentage of MRs involving interference bands 4 and 5 was greater than 30% in certain cells.

 Check RF channels.
It was found that RF channels worked properly.
 Check where there are alarms about equipment faults.
No exception was found.
 Check the coverage and the power.
It was found that the percentage of MRs involving uplink high level and low quality was abnormal.
 Check parameter configurations.
No exception was found.
 Check uplink interference.
It was found that problematic frequencies were in the adjacent frequency band of the CDMA network.
Therefore, the problems may be caused by interference from the CDMA network. For further analysis, onsite
check was performed.

Case 4: Interference Between the CDMA and the
GSM Networks
 Check result
The CDMA antenna was about 1.7 meters from the GSM antenna. In the figure above, the CDMA antenna is on the
left, facing the GSM antenna. The CDMA antenna was about 0.5 meters lower than the GSM antenna. When the
CDMA BTS and the GSM BTS were enabled, strong GSM uplink interference was caused by spurious CDMA signals
because no filter was configured on the two sides.
Step 3 Perform issue closure and export the summary report.
 Configure the CDMA stop filter on the GSM side. Then perform issue closure and export the summary
report.

Case 5: External Interference on the xxx BTS (from
the MS Interference Unit)
 Overview
Interference at a site occurred from 07:00 to 08:00 every day except Sunday, or in afternoons occasionally. The traffic
statistics showed that the percentage of MRs involving interference band 5 was high and the signal received quality
deteriorated, causing a large number of handovers. In the actual test, the uplink noise floor was high and metallic
noise occurred when the MS was used to make a call.

 The percentage of MRs involving interference band 5 was high in certain periods.

 The check of basic items found no problem. The periods during which interference occurred were not
strongly related to network services. The problems may be caused by external interference.
 The interference source was located with an instrument. The onsite check found that the interference was
from an MS interference unit in the meeting room of the office building, Steelworks of Tianjin Tiantie
Metallurgical Group. The MS interference unit was enabled at about 07:30 and disabled at about 08:00
every morning. Sometimes, it was enabled at 15:00 or 16:00. The interference unit was installed by Handan
110 and had been in use for about one month.

 Locate the problems and export the summary report.

Case 6: Interference Due to Improper
Configuration of Frequency Hopping Parameters
 Overview
 In an office, the uplink and downlink HQI on non-BCCH TRXs of a site was abnormally low.
 The HQI on the BCCH TRXs and that on non-BCCH TRXs varied greatly and the uplink interference on
non-BCCH TRXs was strong.

Case 6: Interference Due to Improper
Configuration of Frequency Hopping
Parameters
 The parameter check found that the HSN configurations of co-site cells were different. The HSN of cell
1270 was set to 27, and that of cell 1272 was set to 26. The frequency hopping set include the same
ARFCNs, causing frequency conflicts between co-site cells, hence the interference.


Case 7: CCI and ACI
 Overview
In an office, the uplink and downlink quality of ARFCN 1008 was poor and the voice quality was poor
in a certain cell.

 The DT showed that the downlink quality level fluctuated between 5 and 7 near the cell.

Case 7: CCI and ACI
 From engineering parameters, it was found that quite a few intra-frequency ARFCNs existed and the distance between
sites was short. Therefore, CCI may exist. After ARFCN 1008 of cell 2 at SOLANA was blocked, interference
disappeared.


Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Contents
 Introduction
 Cases

Introduction
 What are the dual-band networking policies?
 Networking policies are polices developed for controlling the distribution of
subscribers and services on TRXs for different network types to balance resource
usage and ensure user experience. For the GSM network, the dual-band networking
policy between GSM900 and DCS1800 is considered.
 Networking policies consist of the following:

 Idle state: subscriber camping policy (cell selection and reselection)
 Access state: service bearer policy (directed retry)
 Connected state: mobility management policy (handover)
 Typical networking policies for GSM900 & GSM1800 are as follows:

 Common dual-band network: 900 MHz cells and 1800 MHz cells at different
layers/ 900 MHz cells and 1800 MHz cells at the same layer
 Enhanced dual-band network
 Concentric circle: CoBCCH networking

Typical Networking Policies for GSM900 and
GSM1800 — Common Dual-Band Network
900 MHz: extensive and
intensive coverage
1800 MHz: hotspot area
 900 MHz cells and 1800 MHz cells at different layers coverage
Idle state: Set RXMIN and

CRO to proper values to
control whether the MS is
camped in a 900 MHz cell or
an 1800 MHz cell.
Connected state: Set layer-

related parameters, inter-layer
handover thresholds, and
hysteresis-related parameters
to proper values to control the
handover between a 900 MHz
cell and an 1800 MHz cell and
control traffic distribution.

Typical Networking Policies for GSM
900&1800 — Common Dual-Band Network
 900 MHz cells and 1800 MHz cells at the same layer
Idle state: Set RXMIN and CRO to proper values to control

whether the MS is camped in a 900 MHz cell or an 1800 MHz cell.
Connected state: Enable 1800 MHz cells to share traffic by using
Negative PBGT HO. Set Inter-layer HO Threshold and
Adjacent Cell Inter-layer HO Hysteresis to proper values for
900 MHz cells and 1800 MHz cells, to influence the 16-bit
sequencing result and trigger the intra-layer negative PBGT
handover when the level of 1800 MHz cells is lower than that of
900 MHz cells. In this manner, traffic is absorbed.

Typical Networking Policies for GSM900 and
GSM1800 — Enhanced Dual-Band Network
900 MHz and 1800 MHz are used for different cells.
Requirements: 900 MHz cells and 1800 MHz cells at
Enhanced dual-band network the same layer, continuous coverage for underlaid
subcells, and continuous or discontinuous coverage
for overlaid subcells
Idle state: Set CBQ, CBA, and CRO to proper

values to control whether the MS is camped in a 900
MHz cell or an 1800 MHz cell.
Connected state: Underlaid subcells and overlaid
subcells can obtain each other's information about
channels and load. The enhanced dual-band
network algorithm is used to share traffic channels
and balance cell load. UL Subcell Lower Load
Threshold and UL Subcell General Overload
Threshold determine whether to perform handovers
between underlaid subcells and overlaid subcells,
balancing traffic between underlaid subcells and
overlaid subcells.

Typical Networking Policies for
GSM900 and GSM1800 — Concentric
Circle
 Concentric circle (CoBCCH)
900 MHz and 1800 MHz are used for the same
cell.
Idle state: same cell
Access state: Determine whether to access the

network from an underlaid subcell or an overlaid
subcell based on the MS location and the
algorithm.
Connected state: Share traffic of 900 MHz cells

and 1800 MHz cells based on the algorithm for
handovers between underlaid subcells and
overlaid subcells.

Advantages and Disadvantages of Typical
Networking Policies for GSM900 and GSM1800
GSM900 and GSM1800
No. Application Scenario Advantages Disadvantages Office
Networking Solution
Common dual-band Recommended. Adopted for Use low-layer 1800 MHz Cell-based layering makes it Most offices
network — 900 MHz cells network deployment and coverage for specified high- difficult to adjust traffic between
and 1800 MHz cells at swapping traffic areas, improving the two cells.
1
different layers network quality and call quality.
Common dual-band Not recommended. Adopted The negative PBGT is a It is complex to set the negative Mobistar and OL in
network — 900 MHz cells when required by the customer neighboring cell-level PBGT. Belgium
2 and 1800 MHz cells at the and for network swapping parameter and can be
same layer adjusted flexibly.
Enhanced dual-band Not recommended. 1. Resource and hardware 1. Heavy maintenance workload FOA site in Iran
network sharing 2. Small capacity (compared
2. Tight frequency reuse with CoBCCH)
3
3. Traffic balancing
4. Compatibility of PS services
Concentric circle (CoBCCH) See the section about the 1. Capacity improvement: One 1. CoBCCH is demanding on VDF in South Africa
CoBCCH in this document. BCCH is shared and TCHs are application scenarios. If MTN in Nigeria
Not recommended. Adopted added. CoBCCH is enabled in a Warid in Pakistan
when required by the customer.2. Network quality scenario that does not meet the
improvement: The number of requirements, network
inter-cell handovers and the performance will be worse than
number of BCCH TRXs are that of a dual-band network.
decreased. The interference 2. It is difficult to optimize
4
becomes weaker. 1800 MHz CoBCCH cells because
BCCH frequency interference parameter configurations vary
is weaker. with scenarios.
3. Convenience for
maintenance: The number of
cells and neighboring cells is
decreased. The maintenance
workload is reduced.

Contents
 Networking Policies
 Introduction
 Cases

 Step 1 Identify the networking policy problem.
 Locate the source and area of the networking policy problem. Check whether the network was swapped
or networking policies were adjusted. Causes of a networking policy problem include abnormal KPIs and
the change of customer requirements.
 For problems with the access, call drop, voice, PS data transmission, and interoperation, attach the
related X measures for resolving the problems.
 Step 2 Perform Required Actions.
 Check the consistency between configurations and networking policies and the consistency between
networking policies and customer requirements.

Required Actions for Networking Policy
Problems
To handle networking policy problems, check the consistency between networking policies and customer
requirements and the consistency between configurations and networking policies.
 Perform this Operation when the configuration is correct but the network
Check the consistency between networking
1 performance cannot meet customer requirements.
policies and customer requirements
 Identify customer requirements and export the current networking policies
and effects.
 Mandatory
Check the consistency between
2  Check whether networking parameters map or comply with the baselines
configurations and networking policies
and whether configurations are correct.
Generally, you are advised to clarify networking policies rather than adjust them. If networking policies need to
be adjusted, learn about customer requirements and provide networking policy deliverables. After confirmation,
jointly replan networking policies with the customer.

Action 1: Check of Consistency Between Networking
Policies and Customer Requirements
 Role: Identify customer requirements and export the current networking policies and effects.
 Tool: OMStar, PRS, and KPI mapping tool
 Input: traffic statistics and counters
 Output: networking policy evaluation table, including the key counter requirement table, networking policy
effect table, and networking policy materials. Counter formulas are defined by frontline engineers and should
be provided together with related information.
 Key counter requirement table
Key Counter Current Value (or Expected Value (or

Situation) Situation)
CS Call Setup Success Ratio
CS Handover Success Ratio
CS Call Drop Ratio
PS Call Setup Success Ratio
PS Call Drop Ratio
Voice Quality
PS Throughput
Other counters

Action 1: Check of Consistency Between
Networking Policies and Customer
Requirements
 Networking policy materials
Provide schematic drawings in each phase mentioned in the networking policy
introduction and materials that require the customer's confirmation. For details, see
the attached document below:

Action 2: Check of Consistency Between Co
nfigurations and Networking Policies
 Role: Identify incorrect networking parameter configurations, such as incorrect reselection configuration and
handover configuration. (For details about the CoBCCH networking check, see the section about X measures
for resolving CoBCCH problems in this document.)
 Tool: PFMStudio and OMStar
 Input: configuration scripts (cfgmml)
 Output: Modify and then check parameter baselines based on networking policy rules in operation 1 and
export the networking parameter check result.

Networking Policy Deliverable

Contents
 Networking Policies
 Introduction
 Cases

Case 1: Handover Success Rate After the Swap
Lower Than That Before the Swap
 Operation 1: Check the consistency between networking policies and customer requirements.
Check networking policies before the swap.

The result showed that some networking parameters, which require mapping, were not mapped. This led to handover
relationships between certain cells to be changed, affecting the handover success rate. After parameter mapping upon
communication with the customer, the handover success rate was resumed to the original level.
Huawei Parameter
N Parameter Name Mapping Relationship
Name
The layer of 1800 MHz cells is one level lower
Layer of The Cell /
than that of 900 MHz cells.
Inter-layer HO
/ Mapping failure. It is set to 30.
Threshold
Adjacent Cell
HO_LEVEL_UMBRELL
Inter-layer HO Huawei=[HO_LEVEL_UMBRELLA] – 30 + 64
A
Hysteresis
Edge HO UL RX_LEV HO_T_L_UL_RX_LEVE
Huawei=HO_T_L_UL_RX_LEVEL
Threshold L
Edge HO DL RX_LEV HO_T_L_DL_RX_LEVE
Huawei=HO_T_L_DL_RX_LEVEL
Threshold L
PBGT HO
HO_MARGIN_PBGT Huawei=[HO_MARGIN_PBGT] + 64
Threshold
Inter-cell HO
HO_MARGIN_LEV Huawei=HO_MARGIN_LEV
Hysteresis
Huawei=HO_MARGIN_LEV–
BQ HO Margin HO_MARGIN_QUAL
HO_MARGIN_QUAL + 64
Notes: (1) Parameters of 900 MHz cells and 1800 MHz cells are set following the preceding table.
(2) Other parameters are set based on parameter review comments.

Case 1: Handover Success Rate After the Swap
Lower Than That Before the Swap
 Operation 2: Check the consistency between configurations and networking policies.
The check result showed that some networking parameters did not meet the requirements because they
were not configured based on mapping relationships.

Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Page 152
Overview on Co-BCCH Performance Problems
Co-BCCH Problem Analysis Actions and Deliverable
Cases
References
HUAWEI TECHNOLOGIES CO., LTD. Page 153

Co-BCCH Application Policy
 Application scenarios of Co-BCCH
• TRXs cannot be added during capacity expansion because 1800 MHz frequency resources
are limited. In this case, you are advised to reconstruct the dual-band network to a Co-
BCCH network.
• Co-BCCH swap. In this case, you are advised to inherit parameters from the original
network.
 Precautions for applying Co-BCCH

• To minimize KPI deterioration risks, ensure that the 900 MHz and 1800 MHz networks share
the same antenna and cover the same areas.
Adjustment for same coverage
 Transmit power and antenna downtilt of 1800 MHz and 900 MHz networks
 Co-BCCH enabled in areas with small inter-site distance (ISD)
• After reconstruction, you are advised to activate Co-BCCH for all neighboring cells
simultaneously.
• Congestion may easily occur in case of fewer TRXs in the underlaid subcell. Therefore,
ensure that there are at least two TRXs in the underlaid subcell.

Prerequisites for Activating Co-BCCH
The following condition must be met for activating Co-BCCH:
The 1800 MHz and 900 MHz networks share the same antenna and
cover the same area.
The following problems may occur if 900 MHz and 1800 MHz networks
cover different areas after Co-BCCH is activated:
 The overlaid subcell fails to absorb traffic to the maximum, leading to congestion in the underlaid
subcell.
 KPI deterioration resulting from blind assignment and handover becomes severer with a larger ISD.

Effects Caused by Coverage Difference:
Features of Co-BCCH network:
KPI Deterioration (1)  Increasing the ISD increases enlarges
Difference in signal strength the level discrepancy between two
between the overlaid subcell and the underlaid subcells.
subcell changes depending on wireless scenarios.  MSs in the underlaid subcell cannot
measure data of the overlaid subcell,
Underlayer: GSM900
and blind assignment and handover
Signal Strength (dBm)
MSs failing to measure the level of the overlaid subcell Overlayer: DCS1800 lead to an increase in the call drop rate
and a decrease in the handover
-75
success rate and assignment success
rate.
 KPI deterioration resulting from blind
-95
assignment and handover becomes
severer if a the coverage difference
Short and medium- Long distance
long distance (larger ISD) increases between the
overlaid subcell and the underlaid
subcell.
Handover command
RxLev, RxQual…..
DCS1800
Overlay
? As good as 900
MHz?
Risk1: Call drops

GSM900 Underlay
Risk2: Handover failures
Risk3: Assignment failures

Effects Caused by Coverage Difference:
Congestion in Underlaid Subcell (2)
Compared with a dual-band network, a Co-BCCH network has fewer SDCCHs. However, because
more SDCCHs need to be configured for the underlaid subcell (900 MHz network), available TCHs are
reduced, leading to a decrease in capacity of the underlaid subcell (in spite of an increase in total
capacity). TRX BCCH SDCCH PDCH Available TCH Erl Total Erl
Dual _band 900 M:3 1 2 1 20 13.2
network 26.4
1800 M:3 1 2 1 20 13.2
Co-BCCH UL:3 1 3 1 19 12.3
28.9
OL:3 0 0 0 24 16.6
The Erl is from ERL-B table.
If the traffic corresponding to reduced capacity of the underlaid subcell cannot be
absorbed by the overlaid subcell, congestion may occur in the underlaid subcell.
If the two subcells cover different areas, traffic of the underlaid
subcell cannot be absorbed by the overlaid subcell due to
coverage holes (the yellow area in the right figure) of the
overlaid subcell. In this case, the capacity of the underlaid
subcell may become a bottleneck and therefore congestion
may occur.
More TRXs in the overlaid subcell require more SDCCHs
in the underlaid subcell, leading to a greater decrease in
capacity of the underlaid subcell. The larger the ISD is, the larger coverage holes of the overlaid
subcell are, and the more possible that congestion occurs in
the underlaid subcell.

Considering feature limitations of Co-BCCH, Co-BCCH reconstruction can be implemented
only in areas to which Co-BCCH is applicable. Co-BCCH reconstruction in areas where
Co-BCCH is infeasible may lead to KPI deterioration beyond control. For Co-BCCH swap,
the parameters of the original network can be directly inherited. Therefore, there is no
limitation on the scenario.
Factors affecting performance after Co-BCCH reconstruction
Overlaid and
NE Antenna Power Channel Parameter
Device RF underlaid
Scenario version coverage matching configuration
configuration fault channel traffic
distribution
Factors affecting performance after Co-BCCH swap
NE Antenna Power Channel Parameter Device fault Overlaid and

coverage matching RF
version configuration configuration underlaid CS
channel
and PS
traffic
distribution
After Co-BCCH reconstruction or swap, if KPIs are deteriorated and fail to meet the
expectation, check each factor listed above as described in following sections.

Co-BCCH KPI Baseline
 Expected KPIs after reconstruction from a dual-band network to a Co-BCCH network
under all circumstances
Before reconstruction, inform customers of effects on KPIs after reconstruction from a dual-band
network to a Co-BCCH network and obtain their consents. Expected KPIs after Co-BCCH
reconstruction in all scenarios are listed in the following table.
Scenario ISD (km) Expected KPI Remarks
Basically unchanged after reconstruction. Both the handover Examples:
success rate and access success rate dropping by 15% and 5%, 1. If the handover success rate is 98% before
1 <1
respectively, while the congestion rate unchanged. For calculation reconstruction, it is 97% after reconstruction.
methods, see remarks. The calculation formula is as follows: 1 – (1 –
Deteriorated slightly after reconstruction. Both the handover 98%) x (1 + 50%) = 97%.
success rate and access success rate dropping by 50%, and both 2. If the call drop rate is 0.8% before
2 (1,3]
the call drop rate and congestion rate on TCH in the underlaid reconstruction, it is 0.9% after reconstruction.
subcell increasing by 15%. For calculation methods, see remarks. The calculation formula is as follows: 0.8% x (1
Deteriorated largely after reconstruction. Both the handover + 15%) = 0.9%.
success rate and access success rate dropping by 80%, and both 3. Congestion rate on TCH in underlaid subcell:
the call drop rate and congestion rate on TCH in the underlaid Because SDCCHs of the underlaid subcell are
subcell increasing by 25%. For calculation methods, see remarks. increased after Co-BCCH reconstruction, the
3 (3,12] capability of absorbing TCH traffic is reduced.
In addition, in case of a larger ISD, the overlaid
subcell cannot absorb traffic to the maximum,
which may lead to congestion in the underlaid
subcell.
Deteriorated severely after reconstruction. KPI risks may be
minimized by adding more BTSs or capacity expansion. For more
4 > 12 details on countermeasures, see section 3.4 of GPSS None
For delivery guide forV100R003C00
from
Technical Guide for the Solution on Reconstruction
reconstruction
a Dual-Band Network from a dual-band
to a Co-BCCH Network. network to
a Co-BCCH network, see GPSS
V100R003C00 Technical Guide for the Solution on Reconstruction from a Dual-Band Network to a Co-
BCCH Network.
 KPIs after Co-BCCH swap cannot be worse than those of the original network and must
meet the expectation.

Cases
References

Page 160
Checklist for Co-BCCH Performance
Problems
Application Entry Implementation
Required Action Purpose
Scenario Condition Time
1: Scenario check Reconstruction None Before reconstruction To check whether the reconstruction scenario meets applicable requirements.
Before swap or
2: Version verification Swap or reconstruction None To verify the current version, functions not supported by the version and impacts on KPIs.
reconstruction
To check whether the antenna azimuth and downtilt of the 900 MHz and 1800 MHz
During the
3: Antenna check Reconstruction None networks to be reconstructed are consistent and adjust the azimuth and downtilt (if
reconstruction
necessary) two weeks before commencement of reconstruction.
To configure the TRX output power of the Co-BCCH cell: For the underlaid subcell, keep
During swap or
4: Power configuration Swap or reconstruction None the TRX output power unchanged. For the overlaid subcell, configure the TRXs to make
reconstruction
the output power close to the TRX output power of the underlaid subcell to the maximum.
During swap or To configure channels and attributes according to applicable swap/reconstruction
5: Channel configuration Swap or reconstruction None
reconstruction requirements.
During swap or To check parameters in strict accordance with parameter mapping rules (from dual-band
6: Parameter check Swap or reconstruction None
reconstruction network to Co-BCCH network or from a vendor's network to Huawei network).
1. Device fault alarm check

7: Regular action (device
After swap or 2. RF channel check
fault and RF channel Swap or reconstruction TOP cells
reconstruction 3. Neighboring cell check
check)
4. Statistics of counters in a long term
1. After swap: To analyze whether the total traffic volume and traffic distribution in the
8: Analysis on voice and overlaid and underlaid subcells after Co-BCCH swap are consistent with the original
data services (including network, which decides directly whether KPIs are worsened compared with those of
After swap or
the ratio and changes) of Swap or reconstruction None the original network.
reconstruction
the overlaid and 2. After swap/reconstruction: To check the PS traffic volume and number of activated
underlaid subcells PDCHs in addition to the CS traffic volume and traffic proportions of the overlaid and
underlaid subcells in consideration of interference of PDCHs in CS services.
1. To check whether the power before and after swap is matched with each other by
comparing the level of the overlaid and underlaid subcells before and after swap.
Before and after 2. To verify whether the triggering time for handover from the underlaid subcell to
9: Drive test Swap None
swap overlaid subcell and from overlaid subcell to underlaid subcell is consistent with that
of the original network and whether the coverage of the overlaid subcell is the same
as that of the original 1800 MHz network.

Required Action 1: Scenario Check
Triggering condition of the action: Mandatory before reconstruction from a
dual-band network to a Co-BCCH network
Check items listed in the following table one by one. Do not start the reconstruction from a dual-
band network to a Co-BCCH network if any item fails to meet applicable requirements.
Requirements for Direct Co-BCCH

No. Check Item Solution If Requirements Are Not Met
Reconstruction
Implement network reconstruction by adding
more BTSs and expanding the capacity. For
details, see Appendix 1 in GPSS V100R003C00
1 ISD ISD ≤ 12 km
Technical Guide for the Solution on
Reconstruction from a Dual-Band Network to a
Co-BCCH Network.
Implement network reconstruction first. For
details, see Appendix 2 in GPSS V100R003C00
Whether there
2 No repeater Technical Guide for the Solution on
are repeaters
Reconstruction from a Dual-Band Network to a
Co-BCCH Network.
Number of
TRXs in the Increase the number of TRXs or do not implement
3 Two or more TRXs in the underlaid subcell
underlaid Co-BCCH reconstruction.
subcell
BTSs sharing the same antenna account for no
If BTSs sharing the same antenna account for
Percentage of less than 70% of the total (Check the antenna
BTSs sharing less than 70% of the total, implement antenna
4 type in the reconstructed area. If BTSs sharing
the same reconstruction to achieve antenna sharing by the
antenna the same antenna account for less than 70%, do
900 MHz and 1800 MHz networks.
not implement Co-BCCH reconstruction.)

Required Action 2: Version Check
Triggering condition of the action: mandatory before Co-BCCH reconstruction
and swap
Limitations on features of various versions are stated below:
 Multicarrier power amplifier (MCPA) may be enabled before Co-BCCH reconstruction or swap
while Co-BCCH and MCPA are not compatible with each other. This problem is resolved in R011
and later versions.
 The function PS DTX which can significantly reduce data service interference is supported in
R013 and later versions.
 Data services being initially assigned to the overlaid subcell is supported in R013C00SPH566
and later versions.
 During Co-BCCH swap or in case of excessive data service interference in the underlaid
subcell, data services need to be balanced between two subcells, which is supported in
R014SPC510 and later versions.
The following NE versions are recommended for Co-BCCH reconstruction and swap.
Scenario Recommended BSC Versions Recommended BTS
Versions
Reconstruction BSC R013C00SPH566 and later BTS R013 and later
versions versions
Swap BSC R014SPC510 and later versions BTS R013 and later
versions

Attachment: Optimization measures in various versions for Co-BCCH swap
Optimization Measures Expected
Scenario Problem Current Optimization Improvement in Improvement in Results After
Effects R013 Improvement
Measure R014
Call drop rate not
Interference HO Allowed Interference handover deteriorated with
disabled Call drop rate reduced - Interference HO Allowed
enabled, no negative gain
Call drop rate enabled
increased due to
intra-cell Problems of call drop Call drop rate not
handover Intracell F-H HO Allowed Call drop rate reduced to a resulting from full-rate and deteriorated with
disabled - half-rate handover solved; Intracell F-H HO
certain degree and percentage of half- Allowed enabled
rate channels reduced
Load handover
unavailable; not Load Handover Support - - Problems of load ping- Congestion rate
matched with disabled pong handover rectified reduced
Ericsson network
PS DTX/DL EGPRS Closed-
Loop Power Control Support Call drop rate reduced - - -
enabled
T3103A match No significant effects - - -
Bad quality handover threshold Call drop rate reduced slightly - - -

reduced and handover success rate
reduced by 0.39%
CS traffic distribution in overlaid
subcell and underlaid subcell Call drop rate reduced (10%) - - -
Co-BCCH matching with the original
Swap network
Versions earlier than
R13C00SPH556: PDCH
being limited Problem of a large number PS traffic matching
PS traffic match (main reason) Call drop rate reduced of PDCHs solved (510 in more efficient (within a
R13C00SPH556: PS traffic R14) week)
Optimization initially assigned to the
efficiency overlaid subcell
Matching with Ericsson
Percentage of half-rate channels Call drop rate reduced - network regarding the -
percentage of half-rate
channels enhanced
Allocate OL Channel Based on Call drop rate reduced slightly - - -
RX Level enabled
SDCCH HO Allowed enabled Call drop rate unchanged and - - -
handover success rate reduced
Call drop rate unchanged and
Assigning Better Cell Allowed assignment success rate - - -
showing a reduction trend
No Dl Mr.HO Allowed and P/N No effects - - -
verification
Neighboring cells missed to be Handover success rate - - -
configured increased and call drop rate
reduced

Required Action 3: Antenna Check
and swap
Check the antenna using one of the following methods (depending on the antenna
type) and make adjustments if necessary:
 Co-antenna between 900 MHz and 1800 MHz networks
Check whether the antenna is a remote electrical tilt (RET) antenna. If the antenna
is an RET antenna, check whether the downtilt of 900 MHz network and that of
1800 MHz network are consistent. If not, adjust the antenna.
 The 900 MHz and 1800 MHz networks using independent antennas
BTSs sharing the same antenna are preferred for reconstruction from a dual-band
network to a Co-BCCH network. If some BTSs use independent antennas, check
whether the antenna azimuth and downtilt of 900 MHz and 1800 MHz networks are
consistent. If not, adjust antennas.

Required Action 4: Power Check
and swap
Scenario Power Match Rules and Solutions
Co-BCCH 1. TRX power of the Co-BCCH overlaid subcell and underlaid subcell is inherited from the original
reconstruction
1800 MHz and 900 MHz networks, respectively. In addition, the power of each TRX in the same
frequency band must be equal. If not, adjust the TRX power.
2. If the ISD exceeds 5 km, the coverage discrepancy between the overlaid and the underlaid
subcells is great. The coverage discrepancy can be decreased by enabling MCPA and
configuring the maximum power for TRXs in the 1800 MHz frequency band.
Co-BCCH swap 1. Data for power match and actually measured data need to be provided. To ensure accurate
power match, the BTSs to be measured must be representative and the number is determined
depending on the number of cells to be swapped.
2. For complete power match requirements, see GSM BTS Power Match.
3. In case of incorrect data of the original network or other problems relating to power match, drive
tests for some BTSs are required both before and after swap. For drive test requirements and
methods before and after Co-BCCH swap, see section "Required Action 9: Drive Test" in this
document.
Power here refers to the actual output power, which is calculated using the following formula: Actual
output power = Value of power type – Value of power class + Fine-tuning value.

Required Action 5: Channel Configuration
Check
and swap
Scenario Channel Configuration Rules Solution
Co-BCCH 1. One static PDCH is configured for the overlaid subcell and underlaid subcell each. The Check whether channel
reconstruction
PDCH of the underlaid subcell is configured on the BCCH TRX. configuration complies
2. No SDCCH is configured in the overlaid subcell. The number of SDCCHs configured in with channel
the underlaid subcell is calculated using the following formula: (Total number of TRXs of configuration rules.
the original 900 MHz and 1800 MHz networks)/1.5 (rounded up to the next integer). Make adjustments if
3. Maximum Rate Threshold of PDCHs in a Cell is set to a value calculated using the necessary.
following formula: Sum of the value of R9316: MAX.OCCU.PDCH of the original 900 MHz and
1800 MHz networks x 100/(Number of TCHFs in the Co-BCCH cell + 1 + 1) (rounded up to the
next integer).
Co-BCCH swap For more details, see

The following uses the Ericsson network as an example for illustration (For other vendors'
networks, adopt the existing swap policies): Guide for Channel
Configuration and
1. Identify frequency hopping settings of TRXs in various channel groups based on
Frequency Hopping Mode
engineering parameters and frequency hopping settings of channel groups on the
Match During Swap from
original network.
Ericsson Network to
2. Identify the total number of static channels, that is, FPDCHs and SPDCHs.
Huawei Network.
3. Identify the number of EPDCHs and GPDCHs, respectively, in each channel group.
Identify the number of EGPRS common channels to be configured on the live network
by calculating the value of NUMREQCS3CS4BPC+NUMREQEGPRSBPC.
4. Set Maximum Rate Threshold of PDCHs in a Cell to 30% of the baseline (it is not
mapped from the original network).

Required Action 6: Parameter Check
and swap
 Reconstruction from a dual-band network to a Co-BCCH network
Check parameter mapping and recommended configurations of the Co-BCCH cell by referring to
iConvert Co-BCCH Mapping Rule Normal. Parameters concerning cell selection, cell reselection,
assignment, handover between overlaid and underlaid subcells, and F-H handover threshold need
to be checked.
Attachment: The figure below shows core parameter mapping rules. For mapping rules for other
parameters, see iConvert Co-BCCH Mapping Rule Normal.

Required Action 6: Parameter Check
 Co-BCCH swap
Check whether parameters, in particular, parameters listed in the following table, are set correctly
according to new parameter mapping rules. The following table lists parameter mapping rules
used during swap of Ericsson networks (obtain other vendors' mapping rules using the standard
procedure).
Parameter ID Parameter Name Mapping Rule Method
SysOpt; if SCLD is ON, huawei (R14) = Default or
OPTILAYER Assign Optimum Layer
Ericsson mapping
OPTILEVTHRES=BSTXPWR – (LOL –
OPTILEVTHRES Assign-optimum-level Threshold Mapping
LOLHYST) + 110 – 8
UTOORECTH = BSTXPWR – (LOL –
UTOORECTH UtoO HO Received Level Threshold Mapping
LOLHYST) + 110
OTOURECEIVETH = BSTXPWR –(LOL +
OTOURECEIVETH OtoU HO Received Level Threshold Mapping
LOLHYST + FBOFFS) +110
SysOpt; if SCLD is ON, huawei (R14) = Default or
HOALGOPERMLAY Pref. Subcell in HO of Intra-BSC
Ericsson mapping
Allocate OL Channel Based on RX
LOWRXLEVOLFORBIDSWITCH ON Default
Level
ASSOLRXLEVOFFSET Assign to Overlayer RxLev Offset 31 Default
IUOHOSTATIME UO HO Watch Time 3 Default
IUOHODURATIME UO HO Valid Time 2 Default
HOCDCMINUPPWR Min UL Level on Candidate Cell 0 Default
HOCDCMINDWPWR Min DL Level on Candidate Cell/Min
Min Access Level Offset + Min DL Level
Access Level Offset Mapping
MINOFFSET on Candidate Cell = 110 – MSRXMIN

Required Action 7: Regular Action
Triggering condition of the action: TOP cells whose KPIs deteriorate after Co-
BCCH reconstruction and swap
If KPIs deteriorate after reconstruction from a dual-band network to a Co-BCCH
network or Co-BCCH swap, analyze related counters to identify absolute TOP cells
and relative TOP cells. Specified activities, including device alarm, tests on
neighboring cells and RF channels and analysis of the traffic trend over seasons and
with increase in users, are the same as those in other networking modes. These
specified activities must be performed in strict accordance with applicable
requirements on handling GSM problems, and deliverables must be submitted.

Required Action 8: Analysis on Voice and Data
Services of the Overlaid and Underlaid Subcells
Triggering condition of the action: TOP cells after Co-BCCH reconstruction and
swap
 Reconstruction from a dual-band network to a Co-BCCH network
1. After Co-BCCH reconstruction, the number of TCHs in the underlaid subcell changes compared
with that on the original 900 MHz network, leading to changes in traffic distribution. To achieve
better KPIs, mapping rules from the dual-band network to the Co-BCCH network tend to allocate
more traffic to the overlaid subcell. It is not required to keep the traffic proportions of the 900 MHz
and 1800 MHz networks unchanged after Co-BCCH reconstruction.
2. The focus need be put on the total traffic volume after Co-BCCH reconstruction. If the total traffic
volume reduces after Co-BCCH reconstruction, adopt common measures to optimize KPIs first.
These measures are described in detail in section 3.5 of GPSS V100R003C00 Technical Guide for
the Solution on Reconstruction from a Dual-Band Network to a Co-BCCH Network. The figure below
shows the traffic optimization process after Co-BCCH reconstruction in an office.

Required Action 8: Analysis on Voice and Data
Services of the Overlaid and Underlaid Subcells
Co-BCCH swap
Analyze whether the total traffic volume and traffic distribution in the overlaid and underlaid subcells after Co-BCCH swap
are consistent with that of the original network. This helps decide whether KPIs deteriorate compared with those of the
original network. Specific impacts and adjustment methods in case of inconsistency are stated below.
Issues and effects Adjustment method Methods for increasing the traffic of the
1. CS service overlaid subcell
1. For significant difference in traffic 1. If Cell Optimized Reserved Parameter
distribution not Analyze whether the total traffic volume and
traffic distribution in the overlaid and
distribution, check whether required 9 is set to 65535, decrease the value of
actions 1–7 are all performed. Assign-optimum-level Threshold.
matched with the underlaid subcells after Co-BCCH swap are
2. When checking the traffic ratio of the 2. Decrease the values of UtoO HO
consistent with that of the original network.
overlaid subcell to the underlaid
original network This helps decide whether KPIs deteriorate
subcell, adjust (if necessary) the
Received Level Threshold and OtoU
compared with those of the original network. HO Received Level Threshold.
traffic of the overlaid subcell as 3. Decrease the values of UO HO Watch
described on the right to increase the Time and UO HO Valid Time and set
traffic (make reverse adjustments to Edge HO UL RX_LEV Threshold to 0.
reduce the traffic distributed to the 4. Set Incoming-to-BSC HO optimum
overlaid subcell). Layer to overlayer (this may lead to an
increase in the handover success rate
Issues and effects Adjustment method and a decrease in the call drop rate).
2. PS services not
matched with the Measures for reducing impacts of PS services on CS services
1. In consideration of interference of PDCHs in CS
original network services, the PS traffic volume and number of 1. Enable downlink PS DTX by setting PS DTX.
activated PDCHs must be checked in addition to 2. Enable downlink PS power control by setting DL EGPRS Closed-Loop
the CS traffic volume and traffic percentages of Power Control Support.
the overlaid and underlaid subcells. 3. Enable load sharing optimization for PDCHs in overlaid subcell and
2. If, after Co-BCCH swap, high quality indicator
underlaid subcell and CS/PS channel allocation optimization by setting
(HQI) and call drop rate deteriorate and activated
PDCH Separate Management for UL and OL Subcells and Channel
PDCHs increase, pay attention to impacts of
Allocation Algorithm Optimization, respectively.
PDCHs on CS services.
4. Decrease the value of Maximum Rate Threshold of PDCHs in a Cell to
reduce the number of occupied PDCHs.
Note: Data services are not distributed to the overlaid subcell in versions earlier than R014. The methods for adjusting the
traffic of both the overlaid and underlaid subcells will be supplemented after being verified in R014.
Required Action 9: Drive Test
Triggering condition of the action: mandatory before and after Co-BCCH swap
A Co-BCCH cell is under the coverage of both the 900 MHz and 1800 MHz frequency bands. Therefore,
drive tests must be performed with caution as described in Drive Test Methods and Precautions issued
by the R&D department before and after Co-BCCH swap.
Test Item Purpose Method Remarks
Power match None

To check whether the power before Test on coverage by the underlaid subcell:
and after swap is matched with each 1. Tests must be performed under the same conditions before and after Co-
other by comparing the level of the BCCH swap.
overlaid and underlaid subcells 2. Tests must be performed in idle state to exclude impacts of power control.
before and after swap. 3. Make statistics of level measured in idle state by segment.
4. Compare the level before and after the swap to check whether the
coverage of the underlaid subcell after swap is consistent with that of the
original 900 MHz network.
Handover Because BCCHs are configured in

To verify whether the triggering time 1. Select the BTS to be tested, initiate a call which occupies channels of the
between the
overlaid and for handover from the underlaid overlaid subcell on the BTS, and perform DT tests before Co-BCCH swap. the underlaid subcell, the coverage of
underlaid the overlaid subcell cannot be
subcell to overlaid subcell and from 2. Record the time and level when the call is handed over from the overlaid
subcells and
coverage of the overlaid subcell to underlaid subcell is subcell to the underlaid subcell. measured directly. The only way is to
overlaid subcell identify the handover triggering time
consistent with that of the original 3. Initiate a call which occupies channels of the underlaid subcell, and record
on the original
network network and whether the coverage of the level when the call is handed over from the underlaid subcell to the to determine whether the coverage of
the overlaid subcell is the same as overlaid subcell. the overlaid subcell remains
that of the original 1800 MHz network. 4. Upon completion of Co-BCCH swap, map parameters relating to handover unchanged.
between underlaid and overlaid subcells and power control from the
original network according to parameter mapping rules.
5. Repeat operations 1–3. If the level when the handover is triggered is close
to that before Co-BCCH swap, the handover triggering time and coverage
of the overlaid subcell are basically same as those of the original network.

Deliverable: Co-BCCH Problem
Analysis Report
Provide information about both common problems and critical problems solved jointly by many parties
in a complete and symmetrical manner.
Provide a Co-BCCH problem analysis report template that applies to all problems based on required
actions and analysis on actual call drop problems. Provide a standardized information platform for
participants in problem handling, standardize all required actions, and ensure all problems are handled
and closed as easily as possible.

Cases
References

Case 1: Call Drop Rate Increased After Co-BCCH Swap
 Background information
After Co-BCCH swap in an office in country X, the call drop rate in busy hours is increased
significantly compared with that before swap.
Call drops mainly occur in the underlaid subcell while for the overlaid subcell, the call drop rate
basically remains unchanged.
 Cause analysis
The number of PDCHs in the underlaid subcell is increased by 9% after swap, leading to
greater interference in the underlaid subcell.

Case 1: Call Drop Rate Increased After Co-BCCH
Swap (continued)
Required actions and check results
Required Action Data Analysis and Phenomenon Conclusion
The BSC version is earlier than R013C00SPH556.
In the current version, PDCHs cannot be initially
allocated to the overlaid subcell. Therefore, the
A key factor affecting the
1: Version check number of PDCHs in the overlaid and underlaid
performance
subcells cannot match with that of the original
network, leading to greater interference in the
underlaid subcell.
2: Power match check Matched with the original network Normal
3: Channel configuration Normal

Matched with the original network
check
4: Parameter configuration Normal
Complying with parameter mapping rules
check
Conclusions
In the current version (earlier than R013C00SPH556), PDCHs cannot be initially allocated to the
overlaid subcell, leading to great difference in PS traffic distribution between the live network and the
original network. Because PDCHs which are in the overlaid subcell before swap are allocated to the
underlaid subcell after swap, the PDCHs in the underlaid subcell are increased by 9% after swap,
leading to greater difference in the underlaid subcell.

Swap (continued)
 This problem can be prevented by limiting the number of PDCHs and reducing
interference in the underlaid subcell
Details:
1. Export channel configuration according to configuration files of the live network.
2. Make statistics of counters of the original network.
DLEPDCH Number of active EG PDCHs on the original network
DLBPDCH Number of active GPRS PDCHs on the original network

Number of active PDCHs on the original 1800 MHz
ACTIVE_PDCH_O
network
ACTIVE_PDCH Number of active PDCHs on the original network
DLBGGDATA GPRS throughput of the original network
DLBGEGDATA EG throughput of the live network
3. Identify factors relating to the target number of PDCHs, including the number of PDCHs inherited
from the original 900 MHz network (The total number of PDCHs – The number of PDCHs in the
overlaid subcell), and service growth rate (taken as 0.85).
PDCH maximum rate threshold = (ACTIVE_PDCH – ACTIVE_PDCH_O) x 0.85/Total number of
channels
Changes in the PDCH services after swap:
1. Services are increased (GPRS services have doubled or even tripled), resulting in more active channels and
poorer PS DTX effects. (This problem can be solved by limiting the number of PDCHs).
2. The PDCHs on the original 1800 MHz network are allocated to the underlaid subcell after swap (This problem
is resolved in R013C00SPH556).
3. Due to lower channel bearing efficiency, more PDCHs are occupied in spite of the same traffic volume (This
problem is resolved in R014).

Swap (continued)
 Effects with the number of PDCHs limited
Reduce Reduce
DL PS PC
PDCHs PDCHs
Before Activated
on NG3 on NG2
SWAP
Easter
Holiday
With PDCHs being limited, the call drop rate is significantly reduced, almost close to that before swap.
R014 versions support PDCH allocation optimization and therefore reduce the number of PDCHs and improve the
PDCH bearing efficiency.

Case 2: Traffic Volume Reduced After Co-BCCH
Reconstruction
 Background information
In an office in country X, the ISD is 800 m and all BTSs share the same antenna. After
scattered reconstruction, the traffic volume within the entire BSC is increased slightly (data
after the reconstruction completion date, that is, August 30, was lost. Here, data after
December 15 was used), the traffic volume in areas without Co-BCCH activated is
increased, while in areas with Co-BCCH activated, the traffic volume is reduced by 123 Erl
with other KPIs almost remaining unchanged. KPIs before and after reconstruction are
shown in the following table.

Reconstruction (continued)
 Cause analysis
900 M 900 M
Layer 1
Layer 2 1800 M 1800 M
The 1800 MHz cell has a higher priority and a wider logical
area (by means of CRO configuration) than the 900 MHz
cell; therefore, MSs are more likely to reside in the
neighboring 1800 MHz cell.
After scattered reconstruction, the traffic volume of the Co-BCCH network is

decreased while that of neighboring dual-band networks increased and the traffic
distribution pattern is changed, causing impacts beyond control.
You are advised to activate Co-BCCH in all neighboring cells

simultaneously.

Required actions and check results
Required Action Data Analysis and Phenomenon Conclusion
ISD, antenna, and number of TRXs meeting requirements for

1: Scenario check Normal
implementing Co-BCCH reconstruction
BSC version: V900R013ENGC00SPH500 and later versions
2: Version check Normal
BTS version: BTS3000V100R013C00SP019
Normal
3: Antenna check Co-antenna and same downtilt
Modified, but the problem
4: Power match check Power not matched with the original network in some cells
still existing
5: Channel Modified, but the problem
Power not matched with the original network in some cells
configuration check still existing
6: Parameter Parameter mapping not complying with the parameter Modified, but the problem
configuration check mapping rules in some cells still existing
Conclusions
Analysis by performing required actions fails to identify any factor that affects traffic distribution.
According to previous theoretical analysis, scattered reconstruction results in failure of traffic
distribution match with the original network, which can be rectified by optimizing configurations of
parameters.

 KPI optimization process
Operations
Effects and KPIs after optimization

Thanks to these optimization measures, in the Co-BCCH cell, the traffic volume is higher and other
KPIs (except the congestion rate, which is worsened slightly) are better than those of the original
dual-band network. The figure below shows the changes of KPIs, indicating that they meet the
expectation.
Note: For other performance optimization measures required after reconstruction from a dual-band
network to a Co-BCCH network, see section 3.5 in GPSS V100R003C00 Technical Guide for the
Solution on Reconstruction from a Dual-Band Network to a Co-BCCH Network.

Cases
References

References

Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Page 186
Contents
 Location Area
 Overview
 Paging Principles and Relevant Parameters
 Calculation of Paging Capacity on the Um Interface
 LAC Boundary Dividing Principles
 LAC Planning and Optimization Procedure
 Cases

Page 187
Overview
 This chapter provides a method of calculating the capacity of GSM

paging channels (PCHs), based on which you can calculate the
paging capacities allowed by and the traffic volumes and TRX
number supported by each LAC under different traffic models.
Around the calculation method, this chapter provides guidance in
LAC planning in the network planning phase and LAC splitting and
optimization in the network optimization phase.

Paging Principles and Relevant Parameters
 Paging principles:
When an MS under an LAC is paged, the MSC sends a paging request to all cells within the LAC scope by means of the BSC. (The
BSC sends the paging message to the BTS, and then the BTS sends it to all cells under the LAC using the Um interface.) At present,
GSM paging modes include TMSI paging and IMSI paging. According to section 9.1.22 of GSM0408, each paging block consists of 23
bytes for two IMSI paging messages, four TMSI paging messages, or the combination of IMSI paging messages and TMSI paging
messages. CCCH Configuration for a Cell CCCH-CONF
Number of CCCH Blocks in a BCCH Multi-
Frame
The CCCH uses one physical channel
000 9
and does not share it with the SDCCH.
The CCCH uses one physical channel
001 3
and shares it with the SDCCH.
The CCCH uses two physical channels
010 18
and do not share them with the SDCCH.
The CCCH uses three physical channels
100 27
 PCH parameters: The CCCH uses four physical channels
110 36
a. Number of CCCH Blocks (CCCH BLKS)
The number of CCCH blocks in a cell reflects the number of resources reserved for AGCHs and PCHs in the cell.
b. CCCH Blocks Reserved for AGCH (BSAGBLKSRES)
It indicates the number of CCCH blocks reserved for the AGCH. After CCCH BLKS is configured, BSAGBLKSRES indicates the
proportion of CCCH blocks occupied by the AGCH and PCH respectively.
c. Multi-Frames in a Cycle on the PCH (BSPAMFRAMS)
It indicates the number of multi-frames that are used as a cycle of paging sub-channels. This parameter determines the number of
paging sub-channels into which the PCH in a cell is divided. The number of paging groups in the cell increases with the value of this
parameter.
d. Number of Paging Groups
Number of paging sub-channels = Number of configured CCCHs x (9 – BSAGBLKSRES) x BSPAMFRAMS
e. Paging mechanism-related parameters (configured on the core network)
Two-time paging, for example, TMSI for the first paging and IMSI for the second paging, is supported.

Calculation of Paging Capacity on the Um Interface
 Safe paging capacity = [(CCCH BLKS – BSAGBLKSRES) x Paging combined efficiency x Um interface utilization ratio for paging x
Period (second)]/0.2354
Note: When there are too many immediate assignment messages, PCHs may be occupied if AGCHs are inadequate. As a result, the safe
paging capacity is reduced.
 Paging Combined Efficiency (average number of paging messages that can be sent by each CCCH block)
Assume that the CS paging policy is that TMSI is used for the first paging and IMSI for the second paging. The PS paging policy is that P-
TMSI is used for the first paging and IMSI for the second paging. The first paging proportion is 87% and the second paging proportion is 13%.
The percentage of CS paging messages is 60%. Assume that the total number of paging messages is 100 (60 CS paging messages and 40
PS paging messages).
Paging combined efficiency = Total number of paging messages/Number of CCCH blocks required = 100/[(60 x 87%/4) + (60 x 13%/2) + (40
x 87%/4) + (40 x 13%/2)] = 3.54
 Um Interface Utilization Ratio for Paging
The imbalance between paging groups and the service imbalance in terms of time result in the low utilization ratio of the Um interface and the
actual efficiency of combining paging messages failing to reach the theoretical value. In this case, the paging capacity of the live network
cannot reach the maximum theoretical paging capacity. Therefore, the Um interface utilization ratio for paging is considered in paging
capacity calculation.
 Traffic Volume Allowed per LA (ERL) = [Safe paging capacity x Proportion of paging messages (CS) x First paging proportion (CS)
x SMS correction proportion/MTC proportion] x [Average holding time (s)/3600]
 Number of TRXs Allowed per LA = Traffic volume allowed per LA (ERL)/[Average traffic volume per TRX x (1 + TCHH proportion)]
A prototype tool is available for calculating the paging

capacity (obtain the latest version from the NIS contact
person when you need to use the tool). The U-Net
Delivery 2.0 for LA planning is under development.
Please keep yourself updated on the release 8
information.

LAC Boundary Dividing Principles
 The upper limit of the size of an LA depends on the paging capacity of each cell, and the
lower limit depends on the LA update frequency. An excessively large LA may cause
considerable increase in the paging times across the network and even network
congestion, which will reduce the network paging success rate. An excessively small LA
may cause excessively frequent LA updates, which will add the signaling load in the
network. Therefore, you must determine the LA size by taking both aspects into
consideration and in light of the actual network situation.
 The LAC size of areas may vary with traffic characteristics. Usually, sizes of different LAs
are suggested as follows: LA in dense urban areas < LA in common urban areas < LA in
suburban areas < LA in rural areas
 When determining the LAC boundary, you must consider geographic features and the
distribution of MSs to reduce the LA update frequency. Usually, the area with fewer users or
handover possibility is selected as the boundary. Avoid selecting an area with a dense
population as the boundary, such as roads and shopping malls.
 Avoid selecting an area where high-end users are located as the LA boundary, such as
group users and VIP users.
 BTSs that use the multicarrier system must be located in the same LA.
 Areas where BTSs of the same LAC are located must be continuous. Avoid and reduce the
possibility of BTS overlapping in adjacent LAs.

LAC Planning and Optimization Procedure
 LAC/RAC planning for a  LAC splitting for paging  LAC combination planning
new network: optimization
01
of the live network: for the MOCN:
Obtain the paging policy and traffic
model of the network: paging
01 mechanism and policy, number of
Obtain the paging policy and traffic
CCCH blocks, and CCCH blocks 01 Obtain the paging policy and
model of the network: paging
mechanism and policy, number of
reserved for AGCH traffic model of the network:
CCCH blocks, CCCH blocks paging mechanism and policy,
reserved for AGCH, SMS correction number of CCCH blocks,
Calculate the number of CCCH blocks reserved for
proportion, MTC proportion, average Calculate the safe paging
holding time (s), and the TCHH 02 03 delivered paging messages AGCH, SMS correction
capacity of each cell under of each cell under the RAC Circle the LAC scope after the
proportion
the LAC or RAC proportion, MTC proportion, 03
or LAC in the live network implementation of the MOCN.
average holding time (s), and
the TCHH proportion.
04
04 Evaluate the cell-level paging overload
02 Calculate the safe paging (evaluate CCCH expansion) and the necessity
Estimate the number of delivered
Circle the LAC scope Calculate the safe paging capacity
capacity
of LAC or RAC splitting 02 of the new LAC, the traffic volume 04 paging messages of the LAC and
supported by the new LAC, and the calculate the traffic volume and
number of TRXs after the number of TRXs after the
06 05 implementation of the MOCN. implementation of the MOCN.
CCCH expansion Y Is the number of BCHs that need to be expanded in the cell
Calculate the traffic volume smaller than the number of BCHs that the customer allows to
03 05 Calculate the designed and optimization expand?
allowed per LA and the Evaluate the risk of paging
traffic volume and TRXs in
number of TRXs allowed per overload after the implementation
an LAC
LA N 05 of the MOCN (evaluate the
reasonableness of the LAC
07 Need to split or adjust the new LAC or RAC (the scope).
customer circles the rough scope of the new LAC
or RAC based on the geological position)
Evaluate the reasonableness of the LAC
06 scope and provide the evaluation result Is the LAC so large as to cause Y
(compare the traffic volume and TRX 06
Calculate the safe paging the paging overload? Does the
09 Estimate the number of delivered
number allowed per LA with those of the 08 capacity of the new LAC or paging messages of the new LAC
LAC scope need to be
circled area.) RAC or RAC in the live network adjusted?
N
End
Is the LAC so large as to Evaluate the reasonableness of LAC or RAC
cause paging overload? Does
Y 10 splitting (compare the estimated paging
07 the LAC scope need to be capacity of the live network with the safe
adjusted? paging capability)
N
The U-Net Delivery 2.0 can automatically
11 Is the new LAC or RAC too large Y
End and does it needs to be adjusted support the three scenarios. The tool is
or re-split?
under development. Please keep
N
yourself updated on the release
End
information.

Cases
Maturity:
 Service content: Calculation of the paging combined efficiency, verification of the Um interface utilization ratio for paging,
calculation of the paging support capability of the Um interface (safe paging times, traffic volume, and TRX number), LAC planning
in the site deployment scenario, risk evaluation for paging overload in a cell and LAC splitting planning in the live network, and
LAC combination planning in the network combination scenario.
 Application scenario: LAC planning during network deployment, LAC splitting and optimization during network swap, LAC
combination during network convergence
 Verification of LAC planning for the YYY1 site in Country XXX1
Each LAC supports about 220,000 times of paging and the traffic allowable is 2018.7 Erl according to the GSM LAC Planning Tool.
The total traffic volume of the YYY1 site in 2009 was about 79,029 Erl. Therefore, 39 LACs were needed. The original LAC
boundaries were used as much as possible during actual LAC division. The improper boundaries were adjusted. A total number of 40
LACs were planned.
Verification of LAC combination for YYY2 site during The paging capacity of the Um interface under the existing
MOCN reconstruction in Country XXX2 parameter configurations and traffic model was about 110,000. The
The MOCN involves two operators, TELENOR and TELE2. The LAC was divided as follows before maximum total paging capacity of LACs involved in the combination
and after reconstitution of the MOCN:
was 48,000, which was far smaller than the paging capacity.
Therefore, LAC combination will not incur the risk of paging
overload.

Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Page 194
Contents
 Solutions
 Preliminary Preparations
 Neighboring Cell Optimization Based on MR and Cell-Cell
Handover Data
 Redundant Neighboring Cell Optimization Based on Cell-Cell
Handover Data
 Other Methods for Optimization
 Suggestions for Neighboring Cell Optimization
 Delivery Guide

Optimizing Neighboring Cells
Objectives:
To disable redundant neighboring cells:

 Disable redundant neighboring cells to improve handover rate.
 Reserve the space of the BA2 table to collect MR data.
To add missing neighboring cells:
 Minimize the interference between neighboring cells during frequency replanning.
 Improve the handover success rate.
 Reduce the call drop rate.
Application scenarios:
 Neighboring cell optimization after network adjustment: The neighboring cell relationships change
because of the addition, swap and capacity expansion of the cells.
 Periodically neighboring cell optimization on the entire network: For network adjustment because of
changes to the network scale and subscriber distribution, you need to check and optimize neighboring
cells periodically on the entire network.
 Neighboring cell optimization in certain areas: Centrally perform neighboring cell optimization for the cell
clusters or VIP areas with low KPI performance.

Optimizing Neighboring Cells
Methods for optimizing redundant neighboring cells:
 Perform the optimization based on MR data and GCell-GCell handover data, including the following MR-
and handover-related counters:
 S371: CELL.NCELL.SCELL.LEV.GT.RTHRES.MR.NUM
 S372: CELL.NCELL.LEV.GT.ABS.THRES.MR.NUM
 S3013: CELL.SCELL.MR.NUM
 H370c: CELLCELL_OUTCELL_HO_REQ
 H380: CELLCELL_INCELL_HO_REQ
 Perform the optimization based on GCell-GCell handover traffic statistics, including the following counters:
 H370c: CELLCELL_OUTCELL_HO_REQ
 H380: CELLCELL_INCELL_HO_REQ
 H375B: CELLCELL_OUT_CELL_HO_FAIL_RECONN_FAIL_TIMES
Methods for optimizing missing neighboring cells:

 Perform the optimization based on MR data, including the following counters:
 S371: CELL_NCELL_SCELL_LEV_GT_RTHRES_MR_NUM
 S372: CELL_NCELL_LEV_GT_ABS_THRES_MR_NUM
 S3013: CELL_SCELL_MR_NUM
 Perform neighboring cell optimization based on topology structures.
 Perform the optimization based on prediction results.
 Perform neighboring cell optimization based on drive tests.

Contents
 Solutions
Handover Data
Handover Data
 Delivery Guide

Preliminary Preparations for Neighboring
Cell Optimization
1. Locate faulty cells and solve problems before neighboring cell optimization.
Check the following items to locate faulty cells and solve problems so that cells are not falsely optimized due to
antenna reversion:
 RF channels
 Alarms
 Device faults
 Cells experiencing strong interference and congestion
2. Check consistency between information about cells under the source BSC and information about the inter-BSC
neighboring cells before neighboring cell optimization.
Import configuration data of to-be-optimized areas and frozen areas to the CME, and choose Advanced > Check
Consistency > External Cell to check the information consistency.

Preliminary Preparations for Neighboring Cell
Optimization
3. Collect and verify engineering parameters.
 Collect the following cell information:
BSC name, cell name, LAC, CI, BCCH, BSIC, longitude, latitude, azimuth, BTS model (indoor, macro, high-speed
railway, trestle, and tunnel BTSs, used to verify the optimization result), and engineering parameters of repeaters and
RRUs.
 Verify accuracy of engineering parameters by checking the following items:
 Completeness of engineering parameters: Verify that engineering parameters of all to-be-optimized cells and frozen
cells are collected. (If cells served by other vendors are covered in the to-be-optimized areas and frozen areas,
ensure that the engineering parameters of the vendors are collected.)
 Longitude and latitude: Verify that longitude and latitude information of all cells is collected; no invalid character is
contained; different cells served by the same macro BTS have the same longitude and latitude (otherwise, obtain
the maximum or minimum value.)
 Verify that different cells have different LACs and CIs (identical LAC and CI for different cells may be resulted from
service migration) and different cell names. Modify the identical LAC, CI, or cell name for different cells.
 Verify that MNCs are in text cell format.
 Verify that BSICs are in octal and text cell format.
 Verify that no special character is contained in azimuths or tilt angles. If the Nastar or Cellopt is used, the middle
value must be obtained for the azimuths and tilt angles of multi-antenna cells. If the U-Net is used for planning
neighboring cells and checking missing neighboring cells, consolidate multi-antenna cell data according to the tool
template.
 Verify that engineering parameters of repeaters and RRUs are complete and accurate.
Verify accuracy of engineering parameters before neighboring cell optimization to ensure reliable optimization results.

Contents
 Solutions
Handover Data
 Basic Principles
 Problems to Be Noted
Handover Data
 Delivery Guide

Principle of GSM > Neighboring GSM Cell
Optimization
Basic principles:
On the existing network, handover has two requirements for the neighboring cell level:
 Neighboring cell level - Serving cell level > Relative level threshold 68 (the actual value is 68 – 64 = 4 dB)
 Neighboring cell level > Absolute level threshold 30 (the actual value is 30 – 110 = –80 dBm)
Algorithm principles:
 The integrated priority is calculated as follows: (S371 x 50% + S372 x 50%)/S3013.
 Rank neighboring cells in the descending order of integrated priorities. The vertical coordinate indicates the integrated priority;
the horizontal coordinate indicates the rank of neighboring cells.
Method for identifying redundant or missing neighboring cells:
 If the ranking of an undefined neighboring cell is within the ranking range specified for missing neighboring cells (which is
set when a task is created for neighboring GSM cell analysis), the cell is a missing neighboring cell.
 A defined, deemed missing neighboring cell is a redundant neighboring cell if it meets any of the following conditions:
(1) The ratio of handover attempts to handover times is 0 or no handover data is available.
(2) The total ranks of neighboring cells exceed the threshold of the number of neighboring cells in the neighboring cell table
or the number of neighboring cell frequencies exceeds threshold of the frequency number in the BA2 table, and the number
of handover attempts is less than the threshold.
(3) The total ranks of neighboring cells exceed the threshold of the number of neighboring cells in the neighboring cell table
or the number of neighboring cell frequencies exceeds threshold of the frequency number in the BA2 table, and the ratio of
handover attempts to handover times is less than the threshold.

Principle of GSM > UMTS Neighboring Cell
Optimization
The basic principle of GSM->UMTS Neighboring Cell optimization is:
1. Measurement Items:
MRs of Serving Cells, Number of MRs with WCDMA Cell From Another Operator Ranking First, Number of
GSM-WCDMA Outgoing Inter-RAT Inter-Cell Handover Requests and Number of Successful GSM-WCDMA
Outgoing Inter-RAT Inter-Cell Handovers
2. Sort the measured WCDMA Cell in descending order of the normalized [Number of MRs
with WCDMA Cell from Another Operator Ranking First]
3. Divide all WCDMA cells into three areas with
No1 and No2:
 Area1: the undefined neighboring cell is missing neighboring cell
 Area3: the defined neighboring cell is redundant neighboring cell
 Area2: no operation
Reference: GSM WCDMA Auto Neighboring Cell Optimization Guide

Notes: [Number of MRs with WCDMA Cell from Another Operator Ranking First] is an inner
counter.

Optimizing Missing and Redundant
Neighboring Cells Based on MR Data
The KPIs required in the neighboring cell optimization and those required in the frequency replanning
are all under Neighbor Cell Level Measurement per Cell. The software parameter configurations and
NE restriction related to the data collection are the same as that in the frequency replanning.
1. Server –version Nastar platform/Stand-alone OMStar Platform
For details about the operation procedure see the Guide to Optimizing GSM Neighboring Cells and
Frequencies Through Nastar.
The version of OMStar is V500R007SPC300. Reference OMStar V500R007 installation manual for
installation. Please refer to the part of neighborhood analysis in the OMStar's online help to execute the
optimization. Taking into account the performance, it is recommended to adopt OMStar if the optimized
range is less than or equal to 4 BSC, else the server -version Nastar.
After suggestions on neighboring cell optimization are exported using Nastar, you can refer to additional
information (for example, distance and the number of MRs for neighboring cells) exported for further
verification.

Contents
 Solutions
Handover Data
 Basic Principles
 Problems to Be Noted
Handover Data
 Delivery Guide

Conducting Verification During MR Data Collection
Verify the following items when collecting MR data to ensure reliable neighboring cell optimization:
 Parameter settings
 Absolute level threshold and Relative level threshold are correctly set.
 BTSMESRPTPREPROC is changed to BSC_Preprocessing.
 Neighbor Cell Measurement Optimization Allowed is disabled (if V 8.1 is used).
 Polling scripts of the BA2 table are delivered.
 Measurement objects
 All to-be-optimized cells are added to the measurement object list.
 Polling measurement is conducted on all BCCH frequency.
 Verify that the time of data collection is reasonable. (It is recommended that performance data for seven
consecutive days be collected.)
 Network changes occurring during data collection
 Check whether any to-be-optimized cells and frozen cells are activated or deactivated during data collection,
or any new BTS accesses the network during data collection.
 Check whether any BCCH frequencies or BSICs are adjusted during data collection. (The adjustment affects
accuracy of the mapping of neighboring cell names and the final sequence of neighboring cells.)
Theoretically, to-be-optimized areas and frozen areas must be blocked from networks during data collection to
ensure accuracy and consistency of collected information. Operations that do not affect MR data collection,
however, can be performed. If any of the preceding network changes occurs during data collection, check the
final optimization results manually.

Collecting MR Data in MOCN Scenarios
 The MOCN feature is widely applied on networks as operators set up joint ventures to reduce costs
and enhance their competitive strengths.
 The MOCN scenario is the same as common scenarios after network transformation. However,
during the MOCN transformation, single-operator cells exist on border areas of the MOCN, which
enlarges the BA2 table and requires vendors to filter the BA2 table by operators.
 To perform neighboring cell optimization in MOCN scenarios, especially where 64 frequencies are
supported, you need to run MML commands to disable automatic filtering of the BA2 table. In
addition, some neighboring cells need to be deleted to ensure that the BA2 table has a sufficient
space for the polling of BCCH frequencies.
 The MML command for disabling the automatic filtering of the BA2 table is as follows:
SET OTHSOFTPARA: CSScnIdHoFilter=NO, PSScnIdHoFilter=NO;
In MOCN scenarios, especially where 64 frequencies are supported, the trimming of the BA2
table is difficult. KPIs may decrease when excessive neighboring cells are deleted; if the
automatic filtering of the BA2 table is disabled and automatic level measurement of
neighboring cells is enabled, frequencies measured by users of operator A may, in extreme
situations, belong to operator B, causing an increase in the measured call drop rate. You are
advised to negotiate this scenario with the operator before data collection.

Conducting Verification Before Performing
Neighboring Cell Optimization Based on MR Data
Before performing neighboring cell optimization based on MR data, conduct the following verification:
 Verify consistency between engineering parameters and configurations.
Synchronize engineering parameters with configurations and verify the consistency between them
to check the reasons. First, check whether some cell information is available in the configuration
table but are unavailable in the engineering parameters. Collect the inconsistent cell information.
Then, check whether some cell information is available in the engineering parameters but are
unavailable in the configuration table. Collect the inconsistent cell information. Finally,
synchronize engineering parameters with the configuration table. Nastar has this function but
OMStar has not.
 Verify accuracy of performance data.
Verify that collected data is accurate, all to-be-optimized cells have reported MR data, and each
traffic packet is in normal size.

Conducting Verification on Suggestions on
Neighboring Cell Optimization Exported from
the Nastar
Verify that neighboring cell optimization results are valid based on the following information:
possible neighboring cells, distance, number of MRs, topology structure diagram, and accurate
black-lists and white-lists. (Black-lists include neighbor relationship that cannot be added, and
white-lists include neighbor relationship that cannot be deleted. Both black-list and white-list
information must include the source and destination BSC names, source and destination cell
names, and the reason why the cell is black-listed or white-listed.) Pay special attention to the
neighbor relationship in special scenarios, such as indoor, high-speed railway, trestle, tunnel, and
large building BTSs. Update black-lists and white-lists in special scenarios to accumulate
experience.

Optimizing Redundant Neighboring Cells
Based on Hanover Measurement
Collect handover measurement data under GSM cell –GSM cell for one week and check the data as follows:
1. If the sum of H370c: CELLCELL_OUTCELL_HO_REQ and H380: CELLCELL_INCELL_HO_REQ is
smaller than 10, the related neighboring cell may be redundant.
2. If the ratio of H375B: CELLCELL_OUT_CELL_HO_FAIL_RECONN_FAIL_TIMES to H370c:
CELLCELL_OUTCELL_HO_REQ is greater than 10%, the related neighboring cell may be redundant.
3. Determine the redundant neighboring cell based on geographical position. If the neighboring cell is far
from the serving cell, or the neighboring cell is near the serving cell but the azimuths of the two cells are
opposite to each other, you need to disable the redundant neighboring cell. Otherwise, you need to check
whether the handover parameters are set properly.
 If the software for optimizing neighboring cells is not installed onsite, use the preceding algorithm and
geographical display software to optimize redundant neighboring cells.

Contents
 Solutions
Handover Data
Handover Data
 Delivery Guide

Optimizing Redundant Neighboring Cells
Based on Hanover Measurement
Collect handover measurement data under GSM cell –GSM cell for one week and check the data as follows:
1. If the sum of H370c: CELLCELL_OUTCELL_HO_REQ and H380: CELLCELL_INCELL_HO_REQ is
smaller than 10, the related neighboring cell may be redundant.
2. If the ratio of H375B: CELLCELL_OUT_CELL_HO_FAIL_RECONN_FAIL_TIMES to H370c:
CELLCELL_OUTCELL_HO_REQ is greater than 10%, the related neighboring cell may be redundant.
3. Determine the redundant neighboring cell based on geographical position. If the neighboring cell is far
from the serving cell, or the neighboring cell is near the serving cell but the azimuths of the two cells are
opposite to each other, you need to disable the redundant neighboring cell. Otherwise, you need to check
whether the handover parameters are set properly.
 If the software for optimizing neighboring cells is not installed onsite, use the preceding algorithm and
geographical display software to optimize redundant neighboring cells.

Contents
 Subject of Neighboring Cell Optimization
 Solutions
Handover Data
Handover Data
 Based on Topology and Prediction
 Based on DT
 Delivery Guide

Optimizing Missing Neighboring Cells
Based on Topology Structures
Stand-alone Nastar
1. Start the stand-alone Nastar and choose Neighbors Analysis > Auto Neighbor Planning. Compare the
exported result of neighboring cell planning with the actual neighboring cell relationships configured on the
existing network and add the missing neighboring cells.

Old Nastar platform
2. Choose Neighboring Analysis > Neighbor Display. Check all neighboring cells. Add the neighboring cell whose
azimuth faces the azimuth of the serving cell or neighboring cells close to the serving cell as missing neighboring cells.
The azimuth of the neighboring cell

(SJGH0489_0) faces that of the serving
cell SJGH0371_0. Add SJGH0489_0 as
the missing neighboring cell.

OMStar
Choose GSM Neighbor Analysis > Neighbor Info Query on Omstar to present neighboring cells in the
GIS interface. Different colors represent different relationship: one-way neighboring cell, two-way
neighboring cell, external cell, and added neighboring cell by user. Check the current neighboring cell and
adjacent cells, and add adjacent cells whose azimuth faces the azimuth of the serving cell or adjacent cells
close to the serving cell but not in the neighboring cell list as missing neighboring cells. Users can add and
delete neighboring cells in the GIS interface directly.
Note: The version of OMStar is V500R007SPC300.

Optimizing Missing Neighboring Cells Based
on Topology Structures
Self developed U-Net
On the U-Net, choose Neighbor Planning > Neighbor Automatic Allocation, set Methods Select to Topology and set
other parameters. Compare the exported neighboring cell planning results with the actual neighbor relationship configured
on the existing network, and add the missing neighboring cell.

Optimizing Missing Neighboring Cell Based on
Emulation Prediction
On the U-Net, choose Neighbor Planning > Neighbor Automatic Allocation, set Methods Select to Prediction and
set other parameters. The tool automatically performs scale prediction and plans neighboring cells. Compare the exported
neighboring cell planning results with the actual neighbor relationship configured on the existing network, and add the
missing neighboring cell.

Optimizing Missing Neighboring Cell Based on
Topology and Emulation Prediction
On the U-Net, choose Neighbor Planning > Neighbor Automatic Allocation, set Methods Select to Topology +
Prediction and set other parameters. The tool first plans neighboring cells based on the geographic relationship, and then
optimizes the neighboring cell planning based on the emulation prediction. Compare the exported neighboring cell
planning results with the actual neighbor relationship configured on the existing network, and add the missing neighboring
cell.

Optimizing Missing Neighboring Cells Based
on Drive Tests
Optimize missing neighboring cells based on call situations.
The results of drive tests show that call drop occurs because the level decreases. The neighboring cell RxLev
is higher than the serving cell RxLev by more than 10 dB (if the MS use TCH carrier, the serving cell RxLev is after
a Power Control. However, because before Call-drop the serving cell RxLev has been relatively poor, indicating
that the MS has to the edge of the cell, the power control level is not too large, and can be approximated by
comparing serving the RxLev and the neighboring cell the RxLev.), but handover does not occur. The serving cell
SJGH0244_2 does not configure SJGH0354_0 as its neighboring cell. Call drop occurs due to the missing
neighboring cell.

Contents
 Subject of Neighboring Cell Optimization
 Solutions
Handover Data
Handover Data
 Based on DT
 Delivery Guide

Verifying the Accurate Delivery of
Neighboring Cell Optimization Results
After neighboring cell optimization results are delivered, perform the following steps
to verify that optimization results for all neighboring cells are delivered:
1. Collect the up-to-date configuration data, and check whether each neighboring
cell optimization result is configured.
2. If any neighboring cell optimization results are not delivered, deliver
optimization results of the neighboring cells again, and conduct verification
again until optimization results of all neighboring cells are delivered.

KPIs Assessed After Neighboring Cell Optimization
1. Click Outgoing Handover Measurement and Outgoing Handover Measurement under

GSM Cell to GSM Cell. Check the following KPIs of the pair of the serving cell and the added
missing neighboring cell: H370c: CELLCELL_OUTCELL_HO_REQ, H380:
CELLCELL_INCELL_HO_REQ, and RH373: CELLCELL_OUTCELL_HO_SUCC_RATE. If
there are many occurrences of H370c: CELLCELL_OUTCELL_HO_REQ and H380:
CELLCELL_INCELL_HO_REQ, and CELL_HO_SUCC_RATE is high, you can determine the
missing neighboring cell.
2. Check ZTR304: CELL_RATE_TCH_CALL_DROP_INCLUDE_HO and
CELL_HO_SUCC_RATE in the area of neighboring cell optimization. If the KPIs increase or
fluctuate, the neighboring cell optimization is proper; if the KPIs decrease evidently, the
missing neighboring cells are added or redundant neighboring cells are disabled improperly.

Contents
 Solutions
Handover Data
Handover Data
 Based on DT
 Delivery Guide

Appendix — Collections of Check Items
For the list of Required Actions for neighboring cell optimization, see the
template of Analysis Report of Neighboring Cell Optimization:

Appendix — Analysis Time of Neighboring
Cell on the New Nastar Platform
The analysis function of the new Nastar platform is not restricted by

analysis time when it is used on common-sized networks.
Assuming that a BTS serves 20 BSCs, a data analysis report is

exported within 30 minutes after the data is imported.
Manual check of analysis results requires 1 to 3 minutes additionally

for each cell in general.

Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Page 227
Huawei Frequency Replanning Development
 Traditional Mode
The traditional mode relies on massive drive tests, emulations, and engineer experience,
requires a large cost, and takes a long time.
 Current Mode
A network interference model is set up according to a large amount of accurate MR data reported
through MSs. The analysis results of automatic frequency planning are provided through the AFP
software platform. Compared with the traditional mode, the current mode has the following
advantages:
 Free: The required data is obtained in equipment rooms.
 Convenient: After the MR data for about a week is obtained, a network interference model is
set up in two hours. The software searches for appropriate frequencies according to the
interference model.
 Accurate: Call measurement records collected from the entire network are used to simulate
the true user behaviors and experiences, while in the traditional mode an estimation is
made according to the information from DTs.

Frequency Replanning Principle

Frequency Replanning Process
 The necessity of each step in the process will be described in detail subsequently.

Frequency Replanning Process
 BCCH frequency replanning (optional): For large frequency replanning

projects or projects with special significance, BCCH frequency
replanning must be implemented first. While for other projects, the
BCCH+TCH frequency replanning can be directly performed. For
details about an AFP project, refer to instructions from the AFP Center.
 Detailed descriptions about the necessity of each step in the process
are given in the rest of the document.

Preparations
1. Collecting basic data
2. Detecting problematic cells
3. Optimizing cells sharing BCCHs and BSICs
4. Optimizing neighboring cells
5. Optimizing the RF
6. Qualitative Evaluation of the Gain of Frequency Replanning
Note: The frequency replanning only adjusts frequencies based on the existing network
architecture. It cannot solve severe problems in the structure, parameters, and
equipment of the network and external interference. To achieve the optimum effects, you
need to prepare for the frequency replanning.
Any mistake may affect the frequency replanning result. Therefore, make
sufficient and subtle preparations according to the requirements.

Preparations
1. Basic Data Collection
Serial No. Item Description
1. Determine frequency bands of the replanning and the number of BSCs;
Determining the
2. Freeze peripheral areas. If other sites exist around, you are recommended to obtain all engineering parameters of
areas of frequency
1 these sites. The engineering parameters must include information about two-layer neighboring cells.
replanning and
3. Frozen areas need to be the peripheral areas round the frequency replanning areas, with the radius 5 times of the
frozen areas
average distance between sites.
1. All available frequencies of cells involved in frequency replanning;
Determining 2. Principles of using BCCH and TCH frequencies;
principles of using 3. Principles of using frequencies in indoor and outdoor cells;
2
the frequencies 4. Whether the frequencies of edge TRXs are specifically used;
that are replanned 5. Other principles.
Available frequency range of each TRX needs to be determined.
1. Cell names, LACs, CIs, BCCHs, and BSICs in engineering parameters must be consistent with those in the BSC
Verifying basic
Phase: Preparation
3 configuration files generated in MR data collection.

information
2. Ensure the accuracy of the longitudes, latitudes, and azimuths in engineering parameters.
Verifying sites and

4 The number of base stations, cells, and TRXs must be accurate. Otherwise, the planning will be greatly affected.
configurations
1. The frequencies of frequency selective repeaters need to be adjusted manually.

2. If the planning uses the EGSM, you need to check whether repeaters served by a cell support the EGSM. If not, the
planning of the cell cannot use the EGSM.
Collecting repeater
5 3. If repeaters are in or near the donor cell, the planning that is conducted by collecting measurement reports is not
information
greatly affected.
4. If repeaters are far from the donor cell, planning results are affected. You need to specify the longitudes and latitudes
of such repeaters and information about the donor cell.
Verifying SVIP and VIP users can be specified in engineering parameters. In frequency replanning, VIP cells should be given the highest
6
VIP cells priority.
1. Supported frequency bands: For example, whether the GSM900 supports the EGSM and the bandwidth supported by
Collecting the GSM1800.
information about 2. Cavity restriction: The differences between frequencies in a single cavity combiner must be greater than or equals to
7
hardware 600 KHz.
restrictions 3. Multi-carrier module information to be collected: module type, module version, number of TRXs in each module, and
the module where BCCH TRXs are.

Preparations
1. Basic Data Collection
 Precautions for collecting repeater information

 Some indoor BTSs and repeaters cannot adjust frequencies after frequency
replanning due to admission problems. Collect this information during basic
data collection and notify the frequency replanning center of locking
frequencies in case that, when the frequency replanning is issued, the
frequencies must be adjusted manually, the frequency replanning gain is
decreased, and the workload is increased.
 If the azimuth of a repeater is opposite to the antenna direction in a serving
cell, the interference caused by frequency allocation is large. Emphasizes
these repeaters during communication with the frequency replanning center.

Preparations
2. Detecting Abnormal Cells

The abnormal cells are classified into the following types:
(1) Cells with abnormal channels
For details, see the Channel Fault Detection and Troubleshooting of GSM RF: Principles, Tools, and
Deliverables prepared by Zhang Xianghua (employee ID: 51668) and Xu Jing (employee ID: 102265).
(2) Cells with top poor uplink and downlink receiving quality due to high interference;
(3) Cells that are severely congested.
You need to focus on cells that are out of service in collecting MR data and report such cells to
the frequency replanning center.
After the planning of frequencies, you need to check the frequencies around the cells that are
out of service by using the Nastar. In this way, you can check whether improper intra-
frequencies and inter-frequencies exist.

Preparations
3. Optimization of Cells Sharing BCCHs and BSICs
Optimization of Cells Sharing BCCHs and BSICs
Tool BSIC planning tool Old Nastar platform
1. Download the installation software from

http://support.huawei.com.
Obtaining method
2. Apply for a license.
Nastar > Analysis Report > Engineering

Instruction
Parameter Check
Notes:
(1) The tool for frequency replanning determines cell names according to the BCCH_BSIC in the MR data. If
many cells that share BCCHs and BSICs and near each other exist on the existing network, the
interference source matching may be incorrect and the planning results are affected.
(2) The tool for BSIC planning is used to replan BSICs of the whole network and maximize the distances
between cells that share BCCHs and BSICs.
(3) The old Nastar platform is used for partial adjustment. The Nastar selects pairs of cells (two cells in a pair
share BCCHs and BSICs and the distance between the two cells is less than 5 km). The BSICs need to be
optimized manually. The Nastar is applicable to the situation where few such pair of cells exists.

Preparations
4. Optimizing Neighboring Cells

Disabling redundant neighboring cells:
 Disable redundant neighboring cells to improve handover efficiency;
 Reserve enough space of the BA2 table for collecting MR data.
Adding missing neighboring cell:
 Minimize the interference between neighboring cells during frequency replanning.
 Improve the handover success rate.
 Reduce the call drop rate.
For information about the optimization of the neighboring cells, see the Neighboring
GSM Cell Optimization: Principles, Tools, and Deliverables.

Preparations
5. Optimizing Radio Frequencies
Two types of cells are involved in the optimization:
(1) High-rise residential buildings
Impact: Uplink interference is generated, resulting in poor uplink receiving quality of other cells.
Selection method: Collect MR data. Check the KPIs under Neighbor Cell Level Measurement per
Cell in the busy-hour MR data for one hour. Count the number of signals received by each serving cell
from neighboring cells. If the number exceeds 800 and the cell is covered by macro base stations, you
need to adjust the coverage range of the cell.
(2) Cross-coverage sites
Impact: 1. The co-channel or adjacent-channel interference caused by downlink signals to
neighboring cells affects downlink C/I and frequency planning effects; 2. The uplink interference of
users in neighboring cells to ultra-high sites occurs easily.
Selection method: 1. Collect MR data for one day to generate the interference matrix; 2. Count how
many times a cell is detected by neighboring cells in the interference matrix. Rank the cells in
descending order of the number; 3. Select 10% cells with worst uplink HQI from the result of 2 and
adjust the coverage range of the cells.

Preparations
6. Qualitative Evaluation of the Gain of Frequency Replanning
Before starting a frequency replanning project, evaluate the project according to a
qualitative evaluation scheme for the gain of the frequency replanning. If one of steps
0010, 0120, and 0030 suggests a frequency planning, check whether step 0040 or 0050
suggests an AFP. If step 0040 or 0050 also suggests an AFP, it is recommended to
perform an AFP; otherwise, an AFP is not required
For detailed evaluation methods, see the Qualitative Evaluation Scheme for the Gain of a
GBSS Auto Frequency Plan.
Case 1
Determining Principles of Frequency Replanning
Determine the frequency use principles of each TRX before frequency replanning. The principles have great impact on
planning results.
Taking sites in City X in Country X as an example: GSM900 indoor and outdoor sites use different frequency bands.
The indoor sites use frequencies 1, 4, 7, 10, 13, and 16.
Solution 1: TRXs of indoor cells with more than six frequencies use outdoor frequencies without authorization.
Solution 2:
1. TRXs of indoor cells with more than six frequencies use outdoor frequencies without authorization.
2. In a pair of cells that have handover relationship and the total number of TRXs of which is greater than 6, the
BCCH TRX and two TCH TRXs use indoor frequencies; other TRXs use outdoor frequencies without authorization.
Co-channel Interference Traffic of the Entire Network Adjacent-channel Interference Traffic of the Entire Network
Original network 41925568 6057995
Solution 1 27146042 (reduced by 35.25%) 4309443.5 (reduced by 28.86%)
Solution 2 20675346 (reduced by 50.69%) 4375462 (reduced by 27.77%)
Note: The co-channel and adjacent-channel interference traffic of the entire network reflects the actual traffic interference.
The co-channel interference traffic is greatly reduced in solution 2 as compared with that in solution 1. This is because solution 1 cannot
distribute enough indoor frequencies to two indoor cells with many TRXs in a building. As a result, the two cells share frequencies and
greatly interfere with each other.

Case 2
Interference in a High-rise Residential Building
Symptom: A serving cell detects 1,228 signals from neighboring cells, including 212 signals where the number of
measurement reports of neighboring cells exceeds 100 and 445 signals where the number exceeds 10.
Cause: On the existing network, the users at a high floor (23rd floor) are covered with a macro base station at a low
floor (5th floor) macro base stations. The users at a high floor receive more cell signals without obstructions around.
Impact: The free space signal transmission of the users at a high floor affects the deep coverage on users with low
uplink levels in other cells. The users cannot make a call due to uplink interference.
Solution: Cover users at a high floor with indoor sites (independent indoor frequencies).
The uplink level of

users at a low floor
is low due to
obstructions.
Free space transmission

The uplink level of
downlink users that
are covered deeply
is low.

Case 3
Cross Coverage
Take Cell X in City X of Country X as an
example. The interference with the cell
is intranet interference. The uplink noise
floor is about –95 dBm.
Main mean Diversity mean

After the RF optimization, the down
tilt angle of the antenna is changed
from four degrees to seven degrees
on July 26. The TCH traffic decreases
significantly (the traffic in busy hours
of Tuesday is lower than that in busy
hours of Sunday).
The uplink HQI0-3 increases
significantly.

Collecting Frequency Replanning Data
Software parameter configuration on the NE
Modify Interference Disable Neighbor Cell
Disable Measurement Modify the BA1 and BA2
Level Thresholds of Measurement Optimization
Report Preprocessing tables
Neighbor Cells Allowed
Register measurements of
neighboring cell levels on the
M2000
Finish collecting MR data
Disable measurements on the

M2000
Restore Interference Restore Neighbor Cell

Enable Measurement Restore the BA1 and
Level Thresholds of Measurement
Report Preprocessing BA2 tables
Neighbor Cells Optimization Allowed
Restore software parameters on the NE

For detailed operations, see the Guide to Collecting GBSS Frequency Replanning Data. Verify the
verification items carefully.

1. Software Parameter Configuration on the NE — Disabling
Measurement Report Preprocessing
The interference matrix must reflect the actual interference on the existing network. The NE measures the C/I
between two cells according to the original measurement report. Therefore, you need to disable Measurement
Report Preprocessing.

2. Software Parameter Configuration on the NE — Modifying Interference
Level Thresholds of Neighbor Cells
In BSC6900V9R11C00, the following threshold configuration is recommended: Interference level

thresholds 0-7: –6, –4, 0, 4, 8, 10, 12, and 16 (the actual thresholds). Set value = Actual
threshold + 64

3. Software Parameter Configuration on the NE — Disabling Neighbor Cell
Measurement Optimization Allowed
To reduce the CPU load, this parameter is enabled
by default to optimize configurable measurement
objects, that is, measuring cells under a BSC in
packet polling mode. Assume that there are 300
cells under a BSC that are divided into six groups
(each group contains 50 cells) and the six cell
groups are measured in the polling mode every
10s in an hour. In this case, the measurement of
each cell takes only ten minutes. Such
measurement does not affect the interference
matrix between cells in the BSC. For two BSCs
with different numbers of cell groups, the
measurement time is different and the generated
interference matrix is inaccurate.
Therefore, you need to disable Neighbor Cell
Measurement Optimization Allowed before
frequency replanning. When collecting data, you
can determine the number of cells where the
measurement is enabled according to the CPU
occupancy (if the occupancy exceeds 70%, you
need to reduce the number).
BSC V9.0 does not support Neighbor Cell
Measurement Optimization Allowed. Therefore,
this step can be skipped.

4. Software Parameter Configuration on the NE — Modifying the BA1 and BA2 tables
Generally, the frequencies in the BA2 or BA1 tables are the BCCH frequencies of neighboring cells of the serving cell.
However, frequencies of all cells that interfere with the serving are required for frequency replanning. Therefore, you need
to add all BCCH frequencies on the network to the BA2 and BA1 tables for measurement.
Method to Upgrade BA2 Table
Tool AFP Nastar
BCCH frequency Add all BCCH frequencies to the BA2 table by running MML Add all BCCH frequencies to the BA2 table by
< = 32 commands. running MML commands.
1. Conduct the measurement in batch. If there are 40 BCCH
Assign a task of neighboring cell
frequencies, you can delete redundant neighboring cells.
measurement to the M2000. The M2000
In this case, the number of neighboring cells of each
automatically modify the BA2 table according
serving cell is reduced to 24. Then you can modify the
BCCH frequency to the measurement period and step and adds
BA1 and BA2 tables twice and add eight frequencies each
> 32 all frequencies to the table for measurement.
time for the measurement.
In this case, the measurement period needs to
2. Modify certain BCCH frequencies with few frequencies to
be prolonged to ensure that all frequencies
ensure that the total number of BCCH frequencies does
are measured in idle and busy hours.
not exceed 32.
Note:1. The GSM900 and GSM1800 cells add BCCH frequencies respectively.
2. For a site on the hybrid network of 2G and 3G, you need to reserve space in the BA2 table to add 3G frequencies. At most 31
frequencies can be added to the BA2 table.
Use the "Tool for modifying the BA2 table" to output MML commands for BA2 table modifications. The tools are applicable to
V8.1 and V9.0.
The upgrade of the BA2 table has a great impact on an interference matrix; therefore, you need to check whether all
frequencies are measured.

5. M2000 — Registering Measurements of Neighboring Cell Levels
1. Frequency replanning uses the indexes S363 to S370 under Neighbor Cell Level
Measurement per Cell. It is recommended that you select the indexes under the whole
measurement set.
2. When enabling the performance measurement of neighboring cell levels, check the CPU
usage of the BSC XPUM. Stop the operation, if the average CPU usage of XPUM CPUs
0 to 3 reaches 70%. Enable flow control if the average CPU usage reaches 80%.
 The accuracy of collected data is vital for frequency replanning;

therefore, check carefully whether all parameters are set properly.
 During the data collection, check whether any performance
measurement data is lost or any data of measurement cells is not
collected.
 Do not collect and deliver frequency replanning data when there are
important examinations or activities which may change traffic models
and therefore affect the result of frequency replanning.

Case 4
After frequency replanning is performed in the subsidiary of China Mobile in a provincial capital, the busy-hour
counters in the morning improve greatly.
Ratio
TCH Congestion TCH Successful SD Successful
Between SDCCH SDCCH
TCH Wireless TCH Call Rate (Not Successful Wireless Assignment SD
Date the Traffic Call Drop Congesti
Traffic Access Drop Rate Including the Allocation Handover of Circuit Allocation
and Call Rate on Rate
Handover) Rate Rate Service Rate
Drop
November 13 4858.68 323.01 99.75% 0.58% 0.00% 99.76% 0.33% 0.00% 98.56% 99.98% 100.00%
November 14 5004.63 305.63 99.74% 0.63% 0.01% 99.76% 0.33% 0.00% 98.48% 99.99% 100.00%
November 15 5160.03 283.65 99.65% 0.65% 0.02% 99.70% 0.36% 0.02% 98.27% 99.97% 99.98%
November 16 5051.13 298.19 99.71% 0.62% 0.01% 99.74% 0.37% 0.01% 98.30% 99.98% 99.99%
November 17 5109.93 298.9 99.67% 0.62% 0.01% 99.71% 0.38% 0.02% 98.26% 99.97% 99.98%
November 18 5107.35 290.29 99.68% 0.64% 0.01% 99.72% 0.38% 0.01% 98.21% 99.97% 99.98%
November 19 5017.66 304.14 99.68% 0.58% 0.01% 99.74% 0.37% 0.03% 98.38% 99.95% 99.96%
Average value 5044.2 300.54 99.70% 0.62% 0.01% 99.73% 0.36% 0.01% 98.35% 99.97% 99.98%
Morning on
3534.24 91.32 99.08% 1.35% 0.00% 99.12% 0.57% 0.03% 96.72% 99.96% 99.97%
November 20
It is found that the civil service examination was held on November 20. Exam centers in universities started jammers, which greatly
affected the counters of the entire network. It is found that 5 cells with the poorest counters, 34 in total, are in or near universities.

6. Restore Software Parameters on the NE
1. Disable M2000 measurements.

2. Restore switch and measurement thresholds on the NE.
3. Restore the BA2 table: Clear User input 2G on the local maintenance terminal (LMT) to restore
the original settings.
 After frequency replanning, the BCCH frequency of each cell is changed. If BCCH
frequencies of neighboring cells are not in the BA2 table, the handover fails and the
handover success rate is reduced.

Verification Tasks During Collection of
Frequency Replanning Data
 The accuracy of collected data is vital for frequency replanning; therefore, check
carefully during collection of frequency replanning data.
1. Before collecting data for frequency replanning, field engineers need to verify the BSC data
configuration to ensure that all MR collection switches for the BSC are enabled, preventing
information loss.
Deliverable: verification results of the mapping relationship between the cell list and the
frequency replanning cell list after all MR collection switches are enabled
2. During data collection, ensure that all frequency replanning cells report MR data properly.
Deliverable: verification results of mapping relationship between the cell list and the
frequency replanning cell list when BSCs performing frequency replanning report MR data
during peak hours

According to the protocol, BCCH frequency levels in the BA2 table are measured during a call and the
information about six neighboring cells with the strongest levels are reported. During the measurement and
reporting, the factors affecting the accuracy of an interference matrix are as follows:
1. A serving cell shares a BCCH frequency with its neighboring cells. Usually, the serving cell level is stronger
than the levels of neighboring cells. In this case, neighboring cell signals cannot be reported.
2. A serving cell shares a BCCH frequency with two neighboring cells. Two signals of the neighboring cells
interfere with each other and cannot be reported.
3. A serving cell shares a BCCH frequency with two neighboring cells. The weak signal is covered by the strong
one. In this case, the interference traffic of the neighboring cell with the weak signal is less than the true value.
4. The BCCH frequency is modified during data collection. This leads to mis-match of neighboring cell names.
5. MR data cannot be reported due to cells with large interference.
6. A serving cell is out of service. The interference data of the serving cell does not exist in the interference
matrix. In addition, other cells cannot detect signals of the serving cell.
7. In RF adjustment and parameter modification, the coverage scope of cells are changed. In this case, the
interference traffic in the matrix is inaccurate.

Case 5
A serving cell shares a BCCH frequency with its neighboring cells.
Adult Education College

of Southwest Jiaotong
University 3
Senior Citizen Association

in Jinniu District 2
The distance between the two sites is 1,022 m. Senior Citizen Association in Jinniu District 2 (serving cell) shares a BCCH frequency with Adult
Education College of Southwest Jiaotong University 3. The interference traffic for an hour is 644, ranking 32nd. After the frequency replanning,
the BCCH frequencies of the two cells are different. In this case, the interference traffic for an hour is 17,467, ranking fourth.

Case 6 Case 7
Two neighboring cells share a BCCH Strong interference leads to report failures.
frequency. Strong signals inhibit weak
signals.
No.44 Middle School 2

Jinfeng Branch 1
QQ Business
Hotel 1
Grand Southwest Building
Material Market 2
Xuefu Tea
House 1
No.44 Middle School 2 is

Grand Southeast the serving cell which
Building Material Market occupies a BCCH and five
2 is the serving cell. The TCHs (without frequency
BCCH frequency 41 of hopping). The connection
QQ Business Hotel 1 is the serving cell. Its neighboring cells (Xuefu
No.44 Middle School 2 between an MS and the
Tea Art 1 and Jinfeng Branch 1) use frequency 41. The interference
can be detected, but the network may be disturbed
traffic before frequency replanning is 60, ranking 127th and that after
BSIC cannot be decoded due to high downlink
frequency replanning is 928, ranking 24th.
due to high interference interference.
with the cell.

Case 8
Modifying BCCH Frequency During MR Data Collection
In a certain site, data on March 15 and 16 are collected. During daytime of March 15, the BCCH frequency
of a certain cell A is changed from 46 to 52. In this case, interference matrix of cells disturbed by cell A is
incorrect.
 Affecting the interference matrix: On March 15, cell B detects that the BCCH_BSIC of cell A is 46_19. On March 16, the
BCCH_BSIC is changed into 52_19. The tool generates the interference matrix and matches neighboring cell names
according to the engineering parameters of March 15. In this case, 52_19 is decoded to another cell rather than cell A.
 Affecting co-BCCH interference replacement: On March 15, the BCCH frequency of cell A is 46. The tool detects
neighboring cells using frequency 46 and conducts co-channel interference replacement. On March 16, the frequency is
changed to 52, which has impact on the measurement of other cells using frequency 52. No measure is taken to handle
the impact.
Workaround: In principle, the networks in frequency replanning areas and frozen areas need to be
blocked during data collection.
1. Do not change BCCHs, BSICs, reference numbers of cells, and cell names.
2. Notify modifications on longitudes, latitudes or and azimuths to the frequency replanning center.
3. Do not modify parameters that affect base station coverage and access thresholds. Other parameters are negotiable.
4. Modifications of TCH frequencies, capacity expansion, and neighboring cell optimization are negotiable.
The network is blocked to ensure the accuracy and consistency of collected information. Operations that do not affect the
collection of measurement reports are negotiable.

Case 9
A cell is out of service in data collection.

In a certain site, data on March 15 and 16 are collected. On these two days, a certain
cell is out of service, which affects the accuracy of the interference matrix. The
interference traffic of the cell is zero. In this case, the impact of the cell is not considered
when the tool assigns frequencies. The same frequency or frequencies that are adjacent
to each other are assigned.
Workaround: detecting and handling hardware faults before data collection.

Case 10
The BA2 table is not restored after frequency replanning.
VCDB303: Sweet Osmanthus Garden 3 has GSM1800 neighboring cells that are in the same
site and direction, but there are not handover requests.
Sweet Osmanthus Garden 4 Outdoor site


H370c: Number H371: Number H373: Times

of Outgoing of Outgoing of Outgoing
Target Handover Handover Handover
Date Time Serving Cell Target Cell CI Target Cell
Cell CGI Requests Commands Success
Sweet Osmanthus Garden 3 Sweet Osmanthus Garden 6

Case 10
The BA2 table is not restored after frequency replanning.
Cause: In frequency replanning, only the GSM1800 BCCH frequencies with most handover times are kept to
add all GSM900 BCCH frequencies to the BA2 table for measurement at the same time. The BA2 table is not
restored after frequency replanning. In this case, the MS does not measure the levels of GSM1800 neighboring
cell in the same site and direction. Therefore, handover cannot be conducted.

Verification Tasks After Collecting
Frequency Replanning Data
 After collecting frequency replanning data, field engineers need to verify

the frequency replanning data again before transferring data. The key
verification items are as follows:
1. Check whether all frequency replanning cells report MRs.
2. Check whether certain BSC information or traffic statistics collected during a
period is lost.
3. Check whether the size of each traffic statistics packet is normal.
4. Check whether a new BTS is connected to the network during the period from
completing data collection to issuing the frequency scheme, if any, add the
engineering parameters of the new BTS to the engineering parameter table,
and mark the BTS as a new one.

Frequency Replanning Tool
After data collections, configuration data (.xml), original performance measurement (mrf), and engineering parameters
are imported into the NASTAR tool.
The tool generates the interference matrix and automatically output the frequency planning scheme.
AFP assignment principle: Automatically

search the frequency with minimum
interference according to the interference
Frequency 1 relationship between the cell to be planned
and its neighboring cells. Assign the Frequency 7
frequency to the cell. According to the
principle, frequency 3 should be assigned to
the cell in this case.
Interference cell
Interference cell
Frequency 3
Cell to be assigned with a frequency

(Frequencies 1, 3, 5, and 7 are Frequency 5
available.)
Interference cell
Factors affecting the effects of frequency replanning: interference matrix Interference cell
and search algorithm

Principles — Form of the Interference Matrix
 The following table describes an interference matrix. The matrix describes the interference relationship
between the serving cell and interference cells. High traffic of co-channel interference or adjacent-channel
interference indicates a close relationship between two cells. If two cells are assigned with a same frequency
or adjacent frequencies, high interference occurs and user call experience is adversely affected.
 According to the interference matrix, two cells with high traffic of co-channel or adjacent-channel interference
cannot be assigned with a same frequency or adjacent frequencies. This is because high interference traffic of
the entire network indicates high interference.
Serving Cell Name Neighboring Cell Name Co-channel Interference Traffic Adjacent-channel Interference
Traffic
QQ Business Hotel 1 QQ Business Hotel 2
QQ Business Hotel 1 Grand Southwest Building Material Market 2

QQ Business Hotel 1 QQ Business Hotel 3
QQ Business Hotel 1 SCDB331: Jiulidi North Road 1
QQ Business Hotel 1 Blue Harbor 1
QQ Business Hotel 1 Adult Education College of Southwest Jiaotong University 1
QQ Business Hotel 1 Jiulidi North Road 2
QQ Business Hotel 1 Trade & Commerce Road 2
QQ Business Hotel 1 Xuefu Tea House 1
QQ Business Hotel 1 Chuanguang Building 3
QQ Business Hotel 1 Shuangshuinian Post Office 3

Principles — Interference Traffic
The traffic of interference of neighboring cells with a serving cell indicates the following information:
1. Level strength of the neighboring cells
2. The cross traffic of the serving and neighboring cells
Cross Traffic of the Serving and Impact of Neighboring Cells

Level Strength
Neighboring Cells on the Serving Cell
High High Heavy
High Low Medium
Low High Medium
Low Low Slight
Frequency resources are insufficient. Therefore, you can assign the same frequency to two cells with
small interference traffic but not two cells with high interference traffic.

Frequency Planning for Newly Deployed BTSs
 During frequency planning for newly deployed BTSs or when a large number of newly
deployed BTSs access the network during frequency replanning, the U-Net is required
for generating interference matrix based on coverage prediction.
 Data sources
 Electronic map and engineering parameters
 Principles
 Based on the difference of prediction signal level of serving cells and prediction signal level of neighboring
cells, we calculate the co-frequency or adjacent-frequency interference traffic volume for the cell-cell.
 Interference matrix based on coverage prediction
 If all BTSs or cells on the network are newly deployed, import the interference matrix generated according
to coverage prediction into the AFP tool, and then perform frequency replanning calculation.
 If certain BTSs are newly deployed, compare, normalize, or combine various interference matrices
provided by the AFP and then add the interference relationship of newly deployed BTSs to the
interference matrix generated based on the MR. Then, use the combined interference matrix to perform
frequency replanning calculation.
The precision of the interference matrix based on coverage prediction depends on the precision of electric
maps, engineering parameters, simulation performed on the U-Net.

Principles — Search Algorithm
In theory, the frequency plan algorithm of the AFP does not have time limit. It can always be executed to detect better
frequency scheme.
In the actual application, if the algorithm is executed for a certain period of time and the frequency scheme does not
change during the period, the existing scheme is optimum. In this case, you can stop executing the algorithm and
output the result.
The duration of the algorithm execution is related to network complexity and condition restriction. Generally, the
duration is three to five days on a network with 10,000 TRXs.
Frequency Fine Control
The outputted frequency scheme needs to be imported to the old Nastar platform for manual check. Generally, you are not
recommended to greatly adjust the frequency scheme output by the AFP if the interference matrix is accurate. For two cells
whose azimuths are opposite to each other, conduct the following analysis according to the interference matrix:
(1) If the interference traffic of the two cells is low, you do not need to adjust the frequencies.
(2) If the interference matrix is incorrect, you need to analyze which step is abnormal.
(3) If the tool assigns same frequencies to the two cells in consideration of interference traffic on the whole network, you
need to adjust the frequencies manually by using the old Nastar platform.

Frequency Fine Control
Finely control frequencies of a single cell by using the old Nastar platform.
1. Choose Nastar > Frequency Analyze > Frequency Optimization Check.
2. Set the distance and frequency ranges of the check.
3. On the Nastar interface, click the cell whose frequencies need to be optimized to display information about
neighboring cell frequencies and idle frequencies.
Select proper frequencies from idle frequencies for the optimization.

Frequency Scheme Assessment
You need to check whether the performance of the network after frequency replanning (using the
frequency scheme that is output by the AFP is more powerful than that of the original network. The
existing assessment methods are as follows:
 Total interference traffic of the entire network: If the total interference traffic reduces after
frequency replanning, it indicates that the frequency replanning is feasible. If the interference
matrix is accurate, this assessment method is most effective.
 Number of co-channel and adjacent-channel collisions: Compare the numbers within a range
that is 1.5 times greater than the cell distance before and after frequency replanning. If the
number reduces after frequency replanning, it indicates that the frequency replanning is feasible.
This assessment method is based on geographical locations and therefore cannot reflect the
actual condition of the existing network.
 Emulation: Compare the percentages of different ranges of C/I before and after frequency
replanning. If the percentage of C/I values that are greater than 9 increases, it indicates that the
frequency replanning is feasible. Closely related to electric maps, engineering parameters, and
parameter configurations, the emulation is hard to control.
 Co-channel handover proportion: Count how many times two cells that have handover
relationship share frequencies or the frequencies of the two cells are adjacent before and after
frequency replanning. If the times reduce after frequency replanning, it indicates that the
frequency replanning is feasible.

Cases 11
Frequency Scheme Assessment(Comparison Between
Co-frequency and Adjacent-frequency Handovers)
New frequency solution evaluation performed by an operator at a provincial capital of China
Number of < 100 100 to 500 500 to 1000 1000 to 2000 2000 to 3000 > 3000
handovers
Interference type Live Live Live Live Live Live
Planning Planning Planning Planning Planning Planning
network network network network network network
BCCH 3031 2861 1323 1155 300 182 83 56 19 6 11 3
UL Adj-1 1414 1419 639 573 140 84 41 28 11 4 3 2
Co-frequency 208 38 45 1 15 5 1 3
DL Adj-1 1409 1404 639 581 145 98 37 28 7 2 5 1
TCH 26571 26252 15019 14574 4950 4305 2908 2271 935 551 785 386
Uplink adjacent-
10105 10462 6334 7024 2191 2141 1284 1111 428 282 359 199
frequency
Co-frequency 6214 4940 2232 438 588 30 319 17 84 3 71 3

Downlink
adjacent- 10252 10850 6453 7112 2171 2134 1305 1143 423 266 355 184
frequency
According to the preceding figure:

1. The number of adjacent-frequency and co-frequency times in a cell-cell performing handovers decreases.
2. The more the number of handover times in a cell-cell, the less the percentage of adjacent-frequency and co-frequency
times after the new solution is implemented.
3. The number of co-frequency times decreases obviously regardless of the handover times.
4. For cell-cell with small number of handover times (< 500), the number of adjacent-frequency times increases, but the
number of co-frequency times decreases obviously. Therefore, the performance of the new solution is not affected.
In conclusion, according to the evaluation on handover times, the new solution brings gains.

Cases 11
Frequency Scheme Assessment
(Interference Traffic Volume on the Entire Network)
New frequency solution evaluation performed at a provincial capital of China
Int Co Int Adj
Live network 295445152.000 36486664.000
After planning 91582536.000 31869444.000
After the planning, the co-frequency interference value (Int Co) and adjacent-frequency value (Int
Adj) decrease at different extent. The decrease in the interference value helps to improve the
network quality. The co-frequency and adjacent-frequency interference traffic volumes on the entire
network reflect the actual traffic interference status on the live network. After the optimization, the co-
frequency traffic decreases by 69% and the adjacent-frequency traffic volume decreases by 12.6%.
This method is mainly used for selecting a proper solution among multiple sets of frequency options.

Cases 11
Frequency Scheme Assessment(CI Simulation)
New frequency solution evaluation performed by an operator at a provincial capital of China

Surface (km2) % Focus Zone
Max C/I Level (dB)
Live network After planning Live network After planning
Max C/I Level (dB) ≥18 162.205 180.01 36.3 40.3
Max C/I Level (dB) ≥ 15 235.535 259.37 52.8 58.1
Max C/I Level (dB) ≥ 12 311.27 336.353 69.7 75.4
Max C/I Level (dB) ≥ 9 374.21 392.375 83.8 87.9
Max C/I Level (dB) ≥ 6 415.36 424.538 93.1 95.1
Max C/I Level (dB) ≥ 3 436.44 439.66 97.8 98.5
Max C/I Level (dB) ≥ 0 445.585 445.745 99.8 99.9
Max C/I Level (dB) ≥ -3 446.283 446.283 100 100

1. The percentage of Max C/I level that is greater than 9 dB increases.
2. The percentage of Max C/I level that is larger 12 dB, 15 dB, and 18 dB also increases obviously.
In conclusion, according to the CI simulation evaluation, the new solution brings gains.

Cases 11
Frequency Solution Evaluation Conclusion)
Frequency replanning evaluation performed by an operator at a provincial capital of China
 After obtaining the MR data, use the Nastar to generate an interference matrix, import the
interference matrix into the AFP tool, and then perform frequency replanning calculation.
According to the comparison of the interference traffic volume, co-frequency and adjacent-
frequency handover, and CI simulation evaluation, the new frequency solution can bring gains.

Generating and Delivering Frequency
Replanning Data
 Generate frequency replanning data.

 After determining the frequency replanning solution, generate frequency
replanning data according to the Guide for Loading Frequency
Replanning Solutions delivered with BSC versions.
 Check the frequency replanning data before delivering it.
 Before delivering the frequency replanning data, you must check the
transmission quality of the maintenance link between the CME and the
OMU to avoid data delivering failures.
 Deliver frequency replanning data.
 After the checking operations, deliver the frequency replanning data
according to the Guide for Loading Frequency Replanning Solutions
delivered with BSC versions.

After Frequency Replanning
After the frequency scheme is implemented on the network, you need to wait for one or two
days until the scheme is stable. In the waiting, you need to pay attention to top poor cells.
Process the cells where the ratio of the sum of the third to fifth values of Interference area
in measurement report (TRX) to the sum of the first to fifth values and the ratio of the sixth
and seventh values of Receiving quality allocation in measurement report (TRX) to the
sum of the first to seventh values are abnormal as follows:
 Disable frequency hopping to determine interference frequencies, and modify the

frequencies by using the old Nastar platform.
 You are advised to restore the TRXs of certain cells without obvious interference.

Items after Frequency Replanning
1. Pay attention to the proportion of the frequency values in the "0 to 3"group and
the "0 to 5"group of the MR. RecvQualOrig. TRX.
2. Pay attention to the proportion of the frequency values in the "3 to 5" group of
the MR. Iterf. TRX.
3. Pay attention to the KPIs required by customers.
4. Use the counters in the following template to evaluate the frequency replanning
result. Add or delete counters and change the calculation formulas according to
onsite situations and customers' requirements.
Note: Frequency replanning is designed to reduce the frequency interference and improve the speech
quality of current networks. It can also reduce call drops and handover failures caused by poor network
quality due to interference. Frequency replanning, however, cannot reduce call drops and handover failures
caused by coverage problems or other reasons.

Cases 12
Frequency Replanning Evaluation
 Frequency replanning evaluation performed by an operator at a provincial

capital of China
Increase After
Counter Name May 21 to May 27 May 30 to June 5
Frequency Replanning
UL HQI (0~5) 99.08% 99.14% 0.06%
DL HQI(0~5) 99.29% 99.43% 0.14%
Proportion of interference
93.83% 95.05% 1.23%
bands from 1 to 3
UL HQI (0~3) 96.74% 97.21% 0.48%
DL HQI (0~3) 96.07% 97.03% 0.96%
 According to the preceding table, the UL HQI (0–3) increases by 0.48%, the DL
HQI (0–3) increases by 0.96%, and the interference bands from 1 to 3 increases by
1.23%. Other KPIs increase steadily. For details, see the Frequency Replanning
Evaluation Performed by an Operator at a Provincial Capital of China.

FAQ
Q1: Does the upgrade of the BA2 table have impact on the handover?
A1: In principle, the upgrade has impact on the handover because it affects the accuracy of MR data. However, the
impact is insignificant according to the indexes of each site.
Q2: How to measure the interference of neighboring cell TCHs with the serving cell?
A2: An MS can measure only the BCCH frequencies of neighboring cells. The TCHs are measured as BCCHs.
Q3: How to conduct frequency replanning of Huawei equipment if other sites exist around?
A3: You need to obtain engineering parameters of other sites around (the parameters must include cell names, BCCHs,
BSICs, and longitudes and latitudes of TCHs).
In this case, you can measure the interference of other sites with the cell and freeze the frequencies of other sites in
frequency replanning. If you cannot obtain engineering parameters of other sites,
freeze the frequencies of the neighboring cells around other sites (that form a circle). Frequency replanning only
covers cells within the circle.
Q4: How to conduct frequency replanning when customers require to replan frequencies of several other sites around for
regular frequency use?
A4: You cannot obtain MR-based interference matrices of other sites, but you can obtain the traffic of interference of
other sites with Huawei equipment. You can freeze Huawei's sites and replan the frequencies of other sites based on
the predicted interference matrices to regulate frequencies.
Then you can freeze other sites to replan the frequencies
of Huawei equipment.
Q5: How to ensure the effects of frequency replanning of key roads and areas?
A5: In the AFP and Nastar, configure the cells that require attentions as VIP cells to add weights.
Q6: What other data needs to be input to the AFP other than interference matrices?
A6: Engineering parameters (that must include names of base stations and cells and number of TRXs) is required for the
AFP to determine the number of frequencies that are assigned to a cell.

FAQ
Q7: The frequencies of a third vendor's RRU indoor cells cannot be replanned on site due to the lack of human resources. How to handle this problem?
A7: Freeze these indoor cells and replan frequencies of other cells. When human resources are sufficient, freeze other cells in the AFP
and replan the frequencies of these indoor cells.
Q8: A cell is disabled in data collection and enabled after the collection. How to handle this problem?
A8: Freeze planned cells and re-enable the cell based on the predicted interference matrix.
When the frequency scheme is enabled on the network, focus on the indexes and adjust the frequencies of the cell.
Q9: The indoor and outdoor sites use different frequency bands, for example, the indoor sites in Chengdu use frequencies 1, 4, 7, 10, 13, and 16. Many
indoor cells have more than six TRXs and these cells may be located in the same building (such as an exposition hall). In this case, the indoor cells
share frequencies due to limited frequency resources. How to handle this problem?
A9: Select the following cells before using the AFP to calculate the frequency scheme:
1. Cells with more than six TRXs that use outdoor frequencies without authorization;
2. Pairs of cells that are top 50 in interference traffic ranking. The number of TRXs of two cells is greater than 6.
3. Pairs of cells that near each other. The number of TRXs of two cells is greater than 6.
4. Pairs of cells that have handover relationship. The number of TRXs of two cells is greater than 6.
The BCCH TRX and two TCH TRXs use indoor frequencies and other TRXs use outdoor frequencies without authorization.
Q10: The BCCH and BSIC in the frequency replanning area are modified in data collection. How to handle this problem?
A10: The network needs to be blocked in data collection. In case of modification on the BICC and BSIC, on-site personnel need to record the related cell
name and reports the name to the frequency replanning center. After the frequency replanning scheme is determined, check the situation of frequency
planning of the cell and areas around by using the stand-alone Nastar and make adjustment manually.
Q11: What is the proper duration for MR data collection?
A11: It is recommended that you collect MR data for one week, covering the traffic models on the workday and two-day weekend.

Case 13
First Frequency Replanning Performed by Operator 1 in Europe
Background: After Huawei performs a non-Like-to-Like swap for an operator 1 in Europe, the call drop rate in certain clusters
fails to meet the operator's requirement, and Huawei faces penalty by the operator.
Troubleshooting:
1. Analysis on the causes of the cluster-level call drops:
Check through DT whether intranet interference causes the call drops.
2. Analysis on the causes for BTSs with the highest call drop rates:
(1) It is found that the high call drop rates in these BTSs are due to poor quality
(2) Through frequency scanning, it is found that the poor quality results from intranet interference
Through frequency scanning, it is found that the poor quality results from intranet interference. It is predicted that the call drop
rate can be optimized after frequency replanning.
The output is as follows:
After the BCCH frequency replanning is performed in about 40 cells in a cluster,
counters recover (see the following figure).
Note
1. Frequency replanning is a paid service project. In principle, the frequency
replanning cannot be provided for free to improve network quality during the
migration; otherwise, the subsequent professional service sales are affected.
Unless in special projects, the frequency replanning center is entitled to reject
the application for offering free frequency replanning.
2. Before the frequency replanning, a specific analysis conclusion must be given:
The unreasonable intranet frequency plan causes the poor network
performance.

Case 14
Frequency Replanning Performed by Operator 2 in Europe
Background: After operator 2 in Europe performs a non-Like-to-Like swap, certain BSC call drop rate fails to reach the standard when
acceptance is approaching.
Troubleshooting:
Steps 1 and 2 are the same as that in the case of operator 1.
3. Two policies are used to plan the frequency scheme as the customer insists on using the MRP mode:
Policy 1: 900 M 18(BCCH)+22(TCH), 1800 M 14(BCCH)+16(TCH)
Policy 2: 900 M 16(BCCH)+24(TCH), 1800 M 12(BCCH)+18(TCH)
Policy analysis: According to configurations of TRXs on the live network, for policy 1, some BTSs inevitably confront the problem that adjacent-
channels occur in a BTS;
In policy 2, the BCCH reuse is small. Handover KPIs may be affected or may not cause a handover and call drop.
Evaluation result: It is found that Policy 2 precedes policy 1 by verifying

interference traffics and the number of times of the conflicts between co-channel
0.9 AFP 100000
and adjacent-channel. The expert review conference decides to use policy 2. 0.8 90000
0.7 80000
Perform frequency replanning to the BSC. Then the counters recover (see the right figure). 0.6
70000
60000
0.5
Note: 0.4
50000
40000
0.3
30000
1. Formulate the frequency planning policy with caution. Identify risks as many as 0.2 20000
0.1
possible before the frequency replanning and continue to optimize the project after the 0
10000
0
frequency replanning to stabilize the gain.

2. Frequency replanning is a paid service project. In principle, the frequency replanning Traffic CDR CDR - without equipmant failure
cannot be provided freely to improve network quality during the migration, or the
following professional service sales are affected.

Appendix1: Procedure for Frequency Planning
New functions in the GSM effective network swap solution (V0.5):

1. Generate the interference matrix based on prediction results of topology or coverage; frequency, BSIC, HSN, and MAIO planning
during GSM swap; frequency and BSIC check during GSM swap (by using the U-NET).
2. Engineering parameter management (by using the iSwap).
3. Seamless interconnection between the iSwap and U-NET for analysis of engineering parameters and frequency planning results.

Appendix2
Tools Used to Frequency Replanning

Serial No. Tool Name Tool Function
Tool for modifying the

1 Adds all BCCH frequencies to the BA2 table for measurement.
BA2 table
2 AFP Plans the frequencies.
Emulates the frequency schemes before and after the frequency replanning and
3 U_Net
compares the values of C/I.
Counts the number of co-channel cell-cell in handover relationships. Compares the
Tool for calculating co-
4 advantages and disadvantages of the frequency schemes before and after the
channel handover rate
frequency replanning.
Tool for counting the
Counts the number of co-channel or adjacent-channel cell-cell in the frequency
number of collisions of
5 scheme base on engineering parameters. Compares the advantages and
intra-frequencies or
disadvantages of the frequency schemes before and after the frequency replanning.
adjacent frequencies
1. Optimizes the BSIC.
6 Stand-alone Nastar
2. Checks whether the frequency scheme is proper after the frequency replanning.

Appendix 3 — Collections of Check Items
1. Frequency Replanning CheckList
2. Required Actions for Frequency Replan
3. Template of Frequency Replanning Report

Appendix 4: Recommendations on Time Reserved
for Frequency Replanning Related Operations
Base data check
Troubleshooting This is a routine network optimization operation. Field engineers need to perform estimation according to the network scale.
problem cells
Co-BCCH and co-
(1) BSIC planning: one person/day (2) Script preparation: one person/day (3) Delivery implementation: one person/day
Preparation BSIC optimization
Deletion of redundant neighboring cells: one person/day
Neighboring cell
Addition of missing neighboring cells is a routine network optimization operation. Field engineers need to perform estimation
optimization
according to the network scale.
RF optimization This is a routine network optimization operation. Field engineers need to perform estimation according to the network scale.
1. The following operations can be performed in batches by BSC: disabling MR preprocessing, modifying the neighboring cell
interference level, disabling neighboring cell measurement optimization allowed, and modifying M2000 traffic measurement
Modification of registration. Batch operations take a small workload.
parameters on the 2. Modification of the BA1/2 table. (This table assumes that there are 10 BSCs. The required duration varies accordingly with
NE side the number of BSCs.)
(1) Exporting and arranging configuration data in the BA table on the live network: 0.5 person/day (2) Modifying BA table
Collection of configuration data and generating scripts: 0.5 person/day (3) Scripts delivering: 0.5 person/day.
frequency 1. Registration operations can be performed in batches by BSC, which takes a small workload.
Measurement task
replanning data 2. Measurement time: The recommended measurement period is one week. Perform the measurement multiple times and
registration
ensure that each round of measurement lasts at least 3 days. There is no additional workload during the measurement.
1. The following operations can be performed in batches by BSC: recovering MR preprocessing, recovering neighboring cell
Recovery of measurement optimization allowed, and disabling the function of modifying M2000 traffic measurement registration. Batch
parameters on the operations take a small workload.
NE side 2. Recovering the BA1/2 table (This table assumes that there are 10 BSCs. The required duration increases accordingly with
the number of BSCs.) (1) Script preparation: 0.5 person/day (2) Scripts delivering: 0.5 person/day.
Output of new solutions and related This operation is performed by the frequency replanning center. Field engineers can negotiate with engineers from the
deliverables frequency replanning center about the completion period based on the project details.
Script preparation for frequency
Based on the frequency replanning scale, three BSCs/one person day
replanning data delivery
Performance assurance after
It is recommended that the assurance period is one week.
frequency replanning

Contents
 Capacity
 Coverage
 Interference
 CoBCCH
 Location Area
 Deliverables

Page 283
List of Deliverables
Subtopic Link
1. Capacity Contents
2. Coverage Contents
3. Interference Contents
4. CoBCCH Contents
5. Dual-Band Networking Policies Contents
6. Location Area Contents
7. Neighboring Cell Optimization Contents
8. Frequency Replanning Contents

Thank you
www.huawei.com
Copyright©2011 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation,
statements regarding the future financial and operating results, future product portfolio, new technology,
etc. There are a number of factors that could cause actual results and developments to differ materially
from those expressed or implied in the predictive statements. Therefore, such information is provided for
reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the
information at any time without notice.

5 GSM Radio Network Planning and Optimization - Influence Factors + Troubleshooting Methods and Tools + Deliverables 20121031

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

5 GSM Radio Network Planning and Optimization - Influence Factors + Troubleshooting Methods and Tools + Deliverables 20121031

Transféré par

Droits d'auteur :

Formats disponibles

2012-10-31 Security Level:

GSM Radio Network Planning and

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2

Wang Xi, Tang

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Subtopic Name Employee ID Tel

CoBCCH Chen Juan 128551 See the phone book.

Networking policies Li Xiaomeng 135755 See the phone book.

Location area Huang Xizhu 128686 See the phone book.

Neighboring cell optimization Li Yan 139128 See the phone book.

Frequency replanning Niu Shaobo 166264 See the phone book.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

MBB traffic is growing quickly Smartphone penetration keeps fast growing

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

Resource Type Capacity Monitoring Capacity Expansion

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

To acquire the load of CS DPUs, evaluate the

The definition of the counter is as follows:

Note: CS DPUs include DPUa, DPUc, and DPUf.

To acquire the PS DPU load, you can evaluate

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

Resource Type Capacity Monitoring Counter Capacity Expansion

SDCCH Congestion Rate on SDCCH 2%

TCH Congestion Rate on TCH 2%

PDCH Congestion Rate on TBF 3%

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

The [RR370: Congestion Rate on

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

TDM transmission resources RR2751: Congestion Rate of Dynamic Resource

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

[T7414: Mean Receive Rate of an IP Path at the IP Layer]

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25

2. Analyze whether the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 27

number of TRXs carried by each CPU is nearly the XPUT 2 45.239 71 61 -5 0

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 28

1. Check whether boards and equipment are faulty by analyzing alarms.

3. Analyze whether resources for voice calls are sufficient.

Balance the configured number of DPUa boards between TC subracks.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 29

Assignment failures are usually caused by equipment faults.

Check whether circuits of the A and Ater interfaces are faulty.

Check the inter-subrack TNU switching resource utilization.

Adjust the inter-subrack site configuration to reduce inter-subrack switching.

Add Ater interfaces for subrack 2 to reduce inter-subrack switching.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 30

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 31

求和项:K3014:TCH话务量求和项:K3034:半速率话务量求和项:全速率话务量