Network Optimization

NETWORK OPTIMIZATION
MobiNil, The Egyptian Company for Mobile Services February 2004

1
1
COURSE OUTLINES
OPTIMIZATION CONCEPTS
OPTIMIZATION ACTIVITIES PARAMETERS OPTIMIZATION CAPACITY ENHANCING TECHNIQUES TYPICAL PROBLEMS & SOLUTIONS
2
2
3
3
INTRODUCTION OPTIMIZATION PROCESS KEY INDICATORS REPORTS & ACTION PLANS OPTIMIZATION TOOLS INPUT DATA
4
4
Introduction
Subscriber Perception
To setup or receive a call everywhere, with a good voice quality without interruption + Value added services.
Availability (Access, Capacity)

Audibility (Voice quality) Mobility (Call Drop) Roaming (Coverage bars display)
5
5
Introduction
Why Network Optimization?
Changes in subscriber distribution Changes in subscriber traffic behaviour Changes in subscriber mobility profiles
Changes in subscriber growth

Uneven network expansion in various regions Limitations in frequency resources
6
6
Introduction
Objectives of Network Optimization Team
Providing the best Quality of Service and voice quality, the
minimum call drop and blocking rates in the covered area using the available resources. Manage and track the process of Radio Optimization Daily monitoring of network performance Ensure the targeted Quality of Service
7
7
Introduction
Optimization Engineer Tasks

Minimize dropped calls and handover failures. Reduce TCH/SDCCH blocking rate and congestion time. Maximize coverage service area.
Support good audio quality.

Minimize transmission power level to reduce interference and increase MS battery life.
8
8
Introduction
Note
Quality of radio design is the base of efficient optimization. The terrain constraints may lead, radio designers, not to
respect the grid giving the optimization engineer the

opportunity to express his optimization skills.
9
9
Optimization Process
System optimization & performance involves applying a set of techniques : Identifying objectives Isolate system components Test plan Taking actions
Conduct post analysis
10
10
Key Indicators
The most familiar key indicators for any operator are: Drop call rate Call setup success rate Call setup blocking rate TCH/SDCCH access failure HO causes HO failures
When operating with multiple vendor system, it is important to cross map the indicators reported from one vendor and find a corollary to it with the other vendor.
11
11
Key Indicators
Setting Thresholds for Key Indicators
The threshold and the objective of the different key indicators must be set in a realistic way.
The objectives should be driven to improve the overall performance of the network factoring into it : - The growth rate expected - Budget constraints
It is important to set aggressive goals to work for, but it is equally important to involve members of the staff whose job is to ensure that the mission statement is met.
12
12
Reports and Action Plans
Reports
It is very important to produce regular summary reports for various levels of management so that they know how the system is operating. When delivering a report, take care to whom it is generated and include only the data needed to be seen.
13
13
Action Plans
An action plan is the right consequence to the reports. Establishing a quarterly and monthly action plan for improving the network is essential in ensuring its health. Each quarter (long term plan), you should identify the worst 10% of your system following the KPIs.
14
14
The quarterly action plan should be used as the deriving force for establishing the monthly plans. The short-term action plans coupled with the long term action plans will help derive the success or failure of the overall mission.
15
15
Optimization Tools
Radio Planning Tool

Coverage prediction Interference calculation Frequency Planning Traffic analysis Network database management
16
16
Optimization Tools
GIS Tools
MapInfo Used for drive test measurement analysis & presentation. GIMS Advanced import and analysis tool built upon MapInfo. Its use is based on the output data from TEMS.
17
17
Optimization Tools
OMC Statistics Monitoring

MARS Motorola Analysis & Reporting System METRICA OMC statistics and KPIs for Alcatel Network RNO Parameters check & modifications, OMC statistics, KPIs for Alcatel.
18
18
Optimization Tools
Actix Analyzer
Drive test analysis Q-voice measurements analysis A & Abis traces analysis
19
19
Optimization Tools
Measurement Tools
TEMS Drive test tools and field problems investigation. TEMS:- drive test tool, check field problems. TEMS Investigation:- advanced drive test tool, problem investigation and analysis in field.
TEMS Light :- indoor measurements.
20
20
Optimization Tools
Q-Voice Drive test tool used for benchmarking & field detection of the voice quality problems. Also it is used to test new features and releases. Spectrum Analyzer Measurement for external interference.
21
21
Input Data
Data gathering is an important issue that facilitate the work of the optimizer. Data could be : - Raw data (Coverage maps, frequency plan, sites database ..etc). - Measurements data (Drive test, A-bis /A captures, call traces, statistics etc ).
Handling these data in optimum way will lead to better performance and output.
22
22
Input Data
Plots/Maps
Coverage (Global region and specific area) Best server map Frequency planning [Site location (X,Y), BCCH, channels)]
Sites Database
Radio parameters Neighbors list Channel configuration
23
23
Input Data
Statistics and Indicators
Identify occasional faults on a subsystem (BSS, BTS) and establish corrective actions.
Detect and identify radio problem on a cell. Statistics can be used to trace and verify big changes in the network (FP, parameters changes, implementations of problem solutions). Predict network behavior according to traffic evolution. Cant reveal the cause of a problem, additional analysis via traces and/or drive test should be used.
24
24
Input Data
Drive Tests
Present the real network performance experienced by subscribers. Provide field information which is often very useful to solve specific problems.
25
25
Input Data
Routes of drive tests must be specified to have valuable outputs: - All sites and sectors should be tested within the route at least once. - All major roads & highways should be tested. - All cells should be tested for handout and hand-in within the routes if possible. - The routes should be approximately 2-3 hours in duration.
26
26
Input Data
Abis Interface Measurements
Drive tests give a snapshot view of the network. Drive tests provide detailed information on the downlink only. Not recommended to adjust cell and HO parameters based on a specific drive test. Abis is the ideal source for level, quality and interference analysis. Abis provides synchronized information on uplink and downlink.
27
27
Input Data
A-Interface Measurements
This interface is standardized by ETSI and its implementation is mandatory. Network optimization based on A-interface analysis makes the process objective and independent of vendor infrastructure. Collecting data is usually easier (because of the reduced number of link connections) than for Abis or Drive Test data. Analysis can be run at BSC level, then at cell and even at individual call level, with the same unique dataset.
28
28
Keep in Mind!!
Rules when solving a problem: Change one thing at a time and test it. If it does not work change it back before you do anything else.
Change the minimum number of parameters possible.

Go to the field and test it. Problems occur in the real world not on your PC. Be as familiar as possible with the radio interface processes.
29
29
OPTIMIZATION ACTIVITIES
30
30
OPTIMIZATION ACTIVITIES
INTRODUCTION STATISTICS MONITORING
FREQUENCY PLANNING
MEASUREMENTS ANALYSIS TRAFFIC HANDLING NEW SITES INTEGRATION SOLVING COMPLAINTS SITES REDESIGN EVOLUTION REPORTS
31
31
Introduction
The radio optimization is built around three main tasks: Detection of the problems Analysis of the problems Solving the problems
32
32
Statistics Monitoring
Operation & Maintenance Center (OMC)
OMC reports Network Performance through statistics. Statistics are pegged based on call states detection by the BTS and BSC. Some Statistics are also based on Signaling Messages. OMC Vendors use their own terminology's and calculation methods to generate statistics.
33
33
In general more or less all statistics indicate the same meaning. It is essential to understand how statistics are pegged to derive conclusion on network performance. Statistics should be used as a proactive approach to detect problems in the network.
34
34
OMC - Report Types
Periodic Reports Per cell basis every measurement period (30/60 minutes) Indicate the trend in statistical measurement Daily Averages
Per cell basis

Snapshot of cells performance and problems
35
35
SDCCH Performance
SDCCH Congestion No. of times all SDCCH's found busy, and a Channel Request received.
RACH
Channel Request
Immediate Assign Reject
SDCCH CONGESTION
36
36
SDCCH Failure
No. of times MS did not respond to Immediate Assignment within T3101 timer period.
RACH
Channel Request T3120 Re-transmission
T3120 Immediate Assignment

T3101
AGCH Reserves SDCCH
No Response from MS - T3101 Expires
SDCCH FAILURE
37
37
TCH Performance
TCH Holding Time - Time (in secs) spent on TCH. - Reported as Min, Max and Mean during the measurement period and also as daily average on per cell basis. TCH Attempts
No of Channel Requests with cause as MOC & MTC

+ Channel Activation Requests for Handover.
38
38
TCH Congestion
BSC
RACH Channel Request
Immediate Assignment MM/CC Signaling on SDCCH
Assign Request
MSC
No TCH
Assign Failure
TCH Congestion =
No of Times TCH not available No of Assignment Requests from MSC + Handover Requests
39
39
TCH Failure
BSC
RACH Channel Request Immediate Assignment MM/CC Signaling on SDCCH
Assignment Command Assignment Failure
Assign Request Assign Failure
MSC
TCH Failure =
No of Assignment Failures from MS Total No of TCH Assignments
40
40
TCH Drops
BTS detects RF fink failure in the Uplink on TCH.

RF link failure generally based on SACCH reports. Also Known as TCH_RF_Loss. Reported on periodic and daily average basis for each carrier and timeslot configured for TCH.
41
41
BSS Counters
Combined into significant formulas: indicators Used to monitor BSS network quality Over complete network, with breakdown per cell/BSC Drawbacks: NSS/PSTN/MS/User problems are not seen
42
42
Call Drop Radio Handovers BSS
Call drop
4500 4000 3500 1 3000 2500 2000 1500 0.4 1000 500 0 Aug/ 01/ 2020 Aug/ 02/ 2020 Aug/ 03/ 2020 Aug/ 04/ 2020 Aug/ 05/ 2020 Aug/ 06/ 2020 Aug/ 07/ 2020 Aug/ 08/ 2020 Aug/ 09/ 2020 Aug/ 10/ 2020 0.2 0 0.8 0.6 Dr op - BSS Dr op - HO Dr op - Radi o % RT CH dr op % Cal l Dr op 1.4 1.2
43
43
Call Setup Success SDCCH Drop TCH Assignment Failure
Call success
16000 14000 100 12000 80 10000 8000 6000 40 4000 2000 0 Aug/ 01/ 2020 Aug/ 02/ 2020 Aug/ 03/ 2020 Aug/ 04/ 2020 Aug/ 05/ 2020 Aug/ 06/ 2020 Aug/ 07/ 2020 Aug/ 08/ 2020 Aug/ 09/ 2020 Aug/ 10/ 2020 20 0 60 Cal l dr op Assi gn f ai l SDCCH dr op % Cal l success % Cal l setup 120
44
44
Incoming Handovers Radio BSS Congestion
Intra + inter BSC incoming handovers
250000 6
200000
5 Fai l - BSS 4 Fai l - Radi o Congesti on 3 Success
150000
100000 2 50000 % Fai l % Cong 1 0 Aug/ 01/ 2020 Aug/ 02/ 2020 Aug/ 03/ 2020 Aug/ 04/ 2020 Aug/ 05/ 2020 Aug/ 06/ 2020 Aug/ 07/ 2020 Aug/ 08/ 2020 Aug/ 09/ 2020 Aug/ 10/ 2020
45
45
Outgoing Handovers Failure Drop Congestion
Intra + inter BSC outgoing handovers
250000 3
200000
2.5 Success 2 ROC Dr op - Radi o 1.5 Dr op - BSS
150000
100000 1 50000 % Dr op % ROC 0.5 0 Aug/ 01/ 2020 Aug/ 02/ 2020 Aug/ 03/ 2020 Aug/ 04/ 2020 Aug/ 05/ 2020 Aug/ 06/ 2020 Aug/ 07/ 2020 Aug/ 08/ 2020 Aug/ 09/ 2020 Aug/ 10/ 2020
46
46
Frequency Planning
Objective
Optimum use of resources to flow a target traffic
Reduce Interference to reach the required quality
47
47
Frequency Planning
Theoretical Frequency Planning Automatic Frequency Planning
48
48
Theoretical Frequency Planning

Frequency Reuse
GSM uses concept of cells One cell covers small part of the network
Network has many cells

Frequency used in one cell can be used in another cells This is known as Frequency Reuse
49
49

Clusters
F=2
F=7
F=1 F=6,10 F=2 F=7 F=1 F=5,9
F=3
F=4,8
F=3
F=7
F=2
F=3 F=1 F=6,10 F=5,9 F=4,8
Co-Channel (Reuse) Cells
F=6,10
F=4,8 F=5,9
F= 1,2,3,4,5,6,7,8,9,10
50
50
The hexagonal model is used to simplify the planning.

Hypothesis Flat earth (No Relief, no obstacle..) Omni directional antennas Equal powers Uniform traffic (One group per cell)
51
51
Pattern Choice
Targeted traffic (Number of TRx per cell) Targeted C/I between reused frequencies (QOS) Number of available frequencies Number and density of sites (Radius of cells)
52
52

Co Channel Reuse
Q = D/R
C / I > 9 dB R
53
53

Adjacent Channel Reuse
Adjacent ARFCN's should not be used in the same cell. Adjacent ARFCN's can be used in adjacent cells, but as far as possible this should be avoided. Taking into consideration the propagation effects, a factor of protection of 600 Khz should be used (Practically not possible in most of the networks due to tight reuse).
In the worst case, adjacent ARFCN's can be used in adjacent cells by setting appropriate handover parameters.
54
54

Cell Configuration
BTS
BTS
Omnidirectional Cell Low gain antennas Lesser penetration/directivity Receives interference from all directions Lower implementation cost
Sectorial Cell High gain antennas Higher penetration/directivity Receives interference from lesser directions Higher implementation cost
55
55

Interference in Omni Cells
B A
3,6,9 C
3,6,9 B
3,6,9 A
Receives interference from all directions
56
56

Sectored Cells
C3 6
3
9 C2 A3
C1
B3 6
3
9
B1
6 A2
3 9
A1
B2
Receives interference from lesser directions. 57
57

Reuse Patterns
Reuse Patterns ensures the optimum separation between co-channels.
Reuse pattern is a formation of a cluster with a pattern of frequency distribution in each cell of the cluster. Same cluster pattern is then reused. Reuse Patterns examples Omni - Cells : 3 cell, 7 cell, 12 cell, 14 cell, 19 cells etc.. Sector - Cells : 3/9 , 4/12, 7/21.
58
58

3/9 Reuse Pattern
A1 C2 B1 A3 A1 C3 A2 B1 B2 A1 A2 C1 C2
59
59
C3
C2 B1 A3
C3 A2
C2
B3 A1
B2
C1
B3 C2
B2 A1
C3 A2 C1 B3 C2
C1
B3 C2
C3
A2 B1
A3
C1 C3
A3 B2
B1
A3 B2
B3
C2 A1
C3
A1
C3

3/9 Reuse Pattern Frequency Allocation
4
3
7 5 9
Adjacent channel interference is very difficult to avoid within the cluster itself.
60
60

4/12 Reuse Patterns
B3 D1 D3 B1 B3 C1 C3
B2 A3 D2 C3 B2 A3 C2
A1
D3
A2 B1
D2 C3 B2 D1 A3 D2 B1 C3 B2
C1
B3
B2
C2
A1 D3 A2 C1 B3
D1
D2 B1 B2 D1 D2
61
C1
B3 C2
A1
D3 A2
C2
A1
61
C1
B3
D3

4/12 Reuse Pattern Frequency Allocation
1 5 12 4 3 9 7 11 2 10 8
62
4/12 pattern avoids adjacent channels in adjacent cells

62

Conclusion
Larger reuse patterns give reduction in interference. Reuse patterns become more effective with sectorial cell configurations. To implement large patterns (like 4/12, 7/21) , more channels are required. So with less resources, the best way to plan is : 1. Use optimum no. of channels per cell. 2. Thus, increase the pattern size.
63
63
Keep in Mind!!
Make a better frequency planning for BCCH than for TCH channels. In the same region, to avoid the mobile to confuse two same BCCH frequencies, use different BSICs. Keep some joker frequencies when possible.
64
64
Automatic Frequency Planning
Goal
Build a frequency plan fast with the required quality, and even when the grid is not respected.
Tools
AGORA RECSIM
65
65

Advantages
Can be used with or without frequency groups Better interference rate than with manual planning
Can include existing frequency planning

Time saving Easy integration of sites
66
66

Process
Computing the reuse matrix The reuse matrix computes the minimal inter channel protection between two stations.
Frequency allocation Done from the reuse matrix as to have a minimal global interference.
Computing the interferences to evaluate the quality of the frequency plan
67
67
Measurements Analysis
Drive Tests Speech Quality
Abis Interface
A Interface
68
68
Drive Tests
Drive tests present the real network performance experienced by subscribers. Processing of drive tests generates statistical analysis of the reported measurements. Plot of drive tests presents network real coverage. Network optimization and redesign is highly dependant on drive tests.
69
69
Drive Tests
Tools
TEMS for drive test and integration
Actix Analyzer for post processing
70
70
Drive Tests
TEMS is used for new site integration and live network optimization. TEMS log files need to be analyzed on a map to filter problems such bad quality, handover failures, call drops, etc Post processing is done using MapInfo/GIMS and Actix Analyzer.
71
71
Drive Tests
Quality Analysis
Spot poor quality areas Check neighbor cells levels Check neighbor frequencies Determine the interferer
72
72
Drive Tests
Call Drop
Check Radio condition before call drop.
Check for missing neighbor relations.

HO parameters may need to be re-tuned.
73
73
Drive Tests
Statistics
Histogram - RxQual (count) 25000
Histogram - RxQual (CDF)
100 5000 90 4500
Histogram - RxLev (count)
Histogram - RxLev (CDF)
100 90 80
20000
80 4000 70 3500
70
CDF (percent)
CDF (percent)
15000
60 50 40 30
3000
60 50 40 30 20 10 0 -107.5 -102.5 -97.5 -92.5 -87.5 -82.5 -77.5 -72.5 dBm -67.5 -62.5 -57.5 -52.5 -47.5 -42.5
Count
10000
5000
20 10
Count
2500 2000 1500 1000 500 0
0 0.0 1.0 2.0 3.0 dBm 4.0 5.0 6.0 7.0
Rx-Qual Distribution
Rx-Lev Distribution
74
74
Speech Quality
Q-Voice
Q-Voice is one of the most advanced measurement tools in evaluating the voice quality in a cellular network as seen by network subscribers. Data Collection Part: - QVM( Mobile part fixed in the measurement car). - QVS (Stationary part located at office).
75
75
Speech Quality
Operation
Communication is setup between two parties; QVM and QVS, through a play button on the QVM. A prerecorded speech sample (5 sec duration) is transmitted through the communication between previously mentioned parties . The speech sample is evaluated in both direction; UL (from the QVM to the QVS) and DL (from the QVS to the QVM) and each sample is given a score called PACE (The speech Quality indicator). Measurement data are saved on both the QVM and the QVS.
76
76
Speech Quality
Post Processing
Represented in the QVP with access to the measurement data imported on a database server. Graphical tools are available for analysis and reporting.
77
77
Speech Quality
Analysis and results of Measurements
Measured Zone / Objective Date of mesurement / hour
P2
16 Nov 2003
1.1Voice Quality (Mobiles1+2&3+4): PACE excellent good fair poor bad total MOBINIL UPLINK 2022 94 67 31 7 2221 MOBINIL DOWNLINK 2038 93 71 13 9 2224 Vodafone UPLINK 1493 64 63 17 6 1643 Vodafone DOWNLINK 1973 116 112 18 4 2223 Voice quality of last campaign Voice quality of the last three campaigns TVOC UPLINK DOWNLINK GLOBAL TVOC 1 Jun 2003 14 Sep 2003 16 Nov 2003 MOBINIL 95.3% 95.8% 93.2% MOBINIL 93.3% 93.5% 93.2% Vodafone 94.8% 94.0% 91.4% Vodafone 89.1% 91.9% 91.4%
TVOC (Voice Quality indicator) 100.0% 95.0% 90.0% 85.0% 80.0% 75.0% 70.0% 65.0% UPLINK DOWNLINK GLOBAL MOBINIL Vodafone 100.0% 95.0% 90.0% 85.0% 80.0% 75.0% 70.0% 65.0% 1 Jun 2003 14 Sep 2003 16 Nov 2003 MOBINIL Vodafone TVOC (Voice Quality indicator)
Output Report
78
78
Abis Interface
Abis is the ideal source for level, quality and interference analysis. Abis provides synchronized information on uplink and downlink. Measurements must be carried around the network traffic busy hour. K1205 protocol analyzer is used to record Abis data.
Abis data are carried on the RSL timeslots on the Abis PCM.
Recorded Abis data are further processed using Actix Analyzer.
79
79
Abis Interface
Analysis of Level Distribution
Shows the amount of traffic at particular RxLev values Validates proper neighbor declaration and HO settings Validates power control settings
80
80
Abis Interface
Level versus TA
Level plotted against TA can help identifying areas with high indoor traffic served by an outdoor cell.
81
81
Abis Interface
Quality Analysis
Quality distribution can validate frequency planning. Filtering poor quality samples and plotting against Level and TA identifies whether interference or coverage problems.
25% 20% 15% 10% 5% 2% 0% 0 1 2 3 Quality Dow nLink Quality Uplink Quality 4 5 6 7 92%88.4%
Count
2.6%
2% 1.9%
2% 2.0%
1% 1.4%
1% 1.2%
1%
1.9%
0% 0.5%
82
82
Abis Interface
Quality Analysis
Plotting quality against Rx-Lev identifies interference problems.
83
83
Abis Interface
Space Distribution
Provides an indication of geographical location of traffic. Space distribution of Rx-Lev samples is valuable when adjusting antenna tilts.
84
84
Abis Interface
Handover Analysis
More powerful compared to BSS statistics and A-Interface measurements. Provides details about incoming and outgoing HO attempts on a TRX level. Incoming HO failures due to TRX problems can be spotted directly.
INCOMING HO
TRX 1100003 1110004 Grand Total Attempt 163 191 354 TCH Attempt Success 151 92.6% 0 163 85.3% 0 314 88.7% 0 SDCCH Success 0 0.0% 0 0.0% 0 0.0%
OUTGOING HO
TRX 1100003 1110004 Grand Total Attempt 138 142 280
TCH Attempt Success 138 100.0% 0 139 97.9% 0 277 98.9% 0
SDCCH Success 0 0.0% 0 0.0% 0 0.0%
85
85
Abis Interface
Handover Analysis
HO attempts and success towards neighbor cells are processed. HO causes per target cell cannot be analyzed. HO failures are further analyzed to identify cause and radio conditions prior to handover.
Cell Summary Stats (HO Matrix - Abis Analysis of Outgoing Handovers) #HO #HO Target BCCH 4 11 14 19 21 22 Target BSIC 11 4 2 17 16 30 tch#HO 2 2 2 9 3 4 %HO 5% 5% 5% 20% 7% 9% tch 2 2 2 9 3 4 sdcchsdcch 0 0 0 0 0 0 #HO sdcchtch 0 0 0 0 0 0
86
86
A-Interface
Collecting data is usually easier (because of the reduced number of link connections) than for Abis or Drive Test data. Analysis can be run at BSC level, then at cell and even at individual call level, with the same unique dataset.
Measurements must be carried around the network traffic busy hour.

K1205 protocol analyzer is used to record A data.
Recorded A-interface data are further processed using Cigale or Actix Analyzer.
87
87
A-Interface
Call Drop
Radio Handover BSS
88
88
A-Interface
Handover Statistics
Ho Causes per neighbor Ho Failure per neighbor
89
89
A-Interface
Handover Statistics
TRX upgrades Frequency addition
90
90
A-Interface
Handover Statistics
Ping Pong Handovers
91
91
A-Interface
Handover Statistics
Incoming vs Outgoing HO Uni-directional neighbor relations
92
92
A-Interface
Call Duration
Faulty CICs Transcoder problems
93
93
Traffic Handling
Busy Hour
1 Hour of the day in which Traffic is maximum. Also referred to as Peak Hour. Busy Hour is not a fixed hour, its timing will vary in different locations. Busy Hour may also be different for different resources
SDCCH busy hour:
typically morning hours (frequent on/offs and updates)

heavy call traffic hour (could be back home hours)
94
94
TCH busy hour:
Traffic Handling
Set Up Time
Average time spent on a resource before getting response from the called end.
Holding Time Blocked Call
Average time spent on any dedicated resource.
A call request rejected due to unavailability of resource.
95
95
Traffic Handling
Sites should be designed to support busy hour traffic. Call Setup Blocking & SDCCH Setup Blocking should satisfy the required Grade of Service. Special events should have special treatment to handle expected traffic (Mobile Shelters).
96
96
New Sites Integration
Delivering the frequency plan and the neighbor files of the new site. Site should be integrated before putting it on air.
During integration, each sector must be checked for call setup and handover.
Each TRx must be checked to detect any faulty hardware. The counters should be closely checked the first few days after the site is on air to detect any problem.
97
97
Solving Complaints
Quality of Service is a measure of Network Quality. Quality of Service is judged by the customer. Customer expects same quality as PSTN.
Increase in mobile penetration led to increase the demand for excellent quality.
98
98
Solving Complaints
Customer Complaints
I am getting "No Service. My handset regularly displays Network Search. I get a 3 beep tone, when I dial a number. My friends call me, but I keep on missing calls. Speech quality is bad. I can never keep up with my call on this street, it DROPS ! My friend has competitor's phone, that works well .
Can you get something out of this ? Can you figure out the technical problems ?
99
99
Solving Complaints
Access Quality
Speech Quality
Retaining Quality
Categories of user quality
100
100
Solving Complaints
Parameters tuning Site redesign New site if needed
101
101
Sites Redesign
Minimizing the bad effect of overlapping and overshooting which have very bad influence on the performance of the network. Enhancing the coverage of poor covered areas.
Solving customers complaints.

Overshooting
Hole
Overlap
102
102
Evolution Reports
Each optimizer has to deliver a weekly/monthly evolution report showing the evolution of his zone according to the following indicators: Call drop rate BH call setup TCH blocking rate BH call setup success rate BH TCH traffic carried Uplink quality HO rate Downlink quality HO rate
103
103
Other Activities
Regular Consistency Checks
Defined template for BSS parameters.
Inconsistency checks. One of the most common problems with networks is that database is incorrectly specified on the OMC-R or/and the BSCs. It is essential to verify that database is correctly specified. It only needs a small error to cause many problems.
104
104
Other Activities
Alarms Monitoring
Failures and faults can not be considered as optimization operations. However, we can not make any optimization without solving network faults.
105
105
PARAMETERS OPTIMIZATION
106
106
PARAMETERS OPTIMIZATION
POWER CONTROL OPTIMIZATION HANDOVER OPTIMIZATION CALL DROP OPTIMIZATION TRAFFIC OPTIMIZATION
107
107
Power Control Optimization
Power Control Window Fast Power Control
108
108

Power Control Thresholds
Upper and lower limits Power increase step size Power decrease step size
Normal step Size -47 dBm u_rxlev_ul_p
l_rxlev_ul_p av_rxlev_ul -110 dBm
Normal Power Control

109
109

Power Control Window
Analysis done on the Uplink power control window. Use Abis measurements to plot quality vs level. Determine the optimum power control window. The optimum window will depend on the frequency reuse pattern and noise floor.
110
110

UL PC Window [-90,-80] [0,2+1]
UL PC Window [-96,-86] [0,2+1]
8000
5000
Nb of Samples
6000
4000
4000 2000 0
-110 -105
3000 2000
7 6
-100
1000 0
-110 -105
7 6
-100
5
-95 -90
-85
-95
4
-80
5
-90
-75
-70
-80
2
-65 -60
UL RxQual
-85
4 3
-75 -70
UL Level
1
-55
2
-65 -60
UL RxQual
0
-50 -45
UL Level
1
-55
0
-50 -45
111
111
Fast Power Control
This feature causes the mobile and BSS to respond more effectively to changing power level and quality conditions. The range of power steps is modified so that the step size will be changed dynamically based on the average received level. The target received level is the middle between U_RXLEV_UL_P and L_RXLEV_UL_P.
112
112
Fast Power Control

Fast Power Control versus Normal Power Control
-47dBm u_rxlev_ul_p Target Received Level l_rxlev_ul_p av_rxlev_ul -110dBm
-47dBm u_rxlev_ul_p
Adaptive step size
Normal step Size
l_rxlev_ul_p av_rxlev_ul -110dBm
Fast Power Control
Normal Power Control

113
113
Fast Power Control

Adaptive Power Increase
Adaptive Power Inc_Step_Size = min [MS_P_INC, Max_POW_INC, (power max- MS_TXPWR)]
Where: Max_POW_INC : max power increase power max : max power of the MS MS_TXPWR : actual power of the MS MS_P_INC is evaluated by the following algorithm
114
114
Fast Power Control

MS_P_INC
Av_RXLEV_UL< L_RXLEV_UL_P
Yes NO Bad Quality only MS_P_INC = POW_INC_STEP_SIZE
Av_RXQUAL_UL<= L_RXQUAL_UL_P +OFFSET_RXQUAL_FH
NO
Bad level only MS_P_INC = roundup [ POW_INC_FACTOR* (TARGET_RXLEV_UL - AV_RXLEV_UL)]
Yes
Bad level and quality MS_P_INC = roundup { MAX [POW_INC_FACTOR*(TARGET_RXLEV_UL - AV_RXLEV_UL), POW_INC_STEP_SIZE]}
115
115
Fast Power Control

Adaptive Power Reduction
Adaptive Power Red_Step_Size = MIN [MS_P_RED, Max_POW_RED, (MS_TXPWR - power min)] Where; Max_POW_RED : max power reduction power min : min power of the MS MS_TXPWR : actual power of the MS MS_P_RED is evaluated by the following algorithm
116
116
Fast Power Control

MS_P_RED
Av_RXLEV_UL> U_RXLEV_UL_P Yes Av_RXQUAL_UL>= U_RXQUAL_UL_P Good level only MS_P_RED = roundup{MAX [ POW_RED_FACTOR* (AV_RXLEV_UL TARGET_RXLEV_UL )] ,2 dB} Good Quality only MS_P_RED = POW_RED_STEP_SIZE
NO
NO
Yes
Good level and quality MS_P_RED = roundup { MAX [POW_RED_FACTOR*(AV_RXLEV_UL - TARGET_RXLEV_UL), POW_RED_STEP_SIZE]}
117
117
Fast Power Control
118
118
Fast Power Control

The average level and quality used are averaged with window size A_QUAL_PC and A_LEV_PC. To disable fast power control and use the fixed power control step size, set the parameters max_pow_inc = inc_step_size max_pow_red = red_step_size pow_inc_factor =1 pow_red_factor =1
119
119
Fast Power Control

Field Trial
The following parameters were set
Parameter
POW_INC_FACTOR POW_RED_FACTOR MAX_POW_INC MAX_POW_RED POW_RED_STEP_SIZE
Per
Cell Cell Cell Cell Cell
Definition
Weighting factor for power increase Weighting factor for power reduction Maximum Power increase in one power command Maximum Power reduction in one power command Power reduction step size in case of power command triggered on quality criterion Power increase step size in case of power command triggered on quality criterion Upper uplink level threshold for power control Lower uplink level threshold for power control Upper uplink quality threshold for power control Lower uplink quality threshold for power control
120
Stage 1 Stage 2
0.8 0.5 8 6 2 4 -86 -96 0 2 0.8 0.5 16 6 2 4 -86 -96 0 2
120
POW_INC_STEP_SIZE Cell U_RXLEV_UL_P L_RXLEV_UL_P U_RXQUAL_UL_P L_RXQUAL_UL_P Cell Cell Cell Cell
Fast Power Control

To highlight the change in the MS power distribution, the MS_TX_PWR was classified into 3 categories: high, medium, low.
El_Khatib_MSTXPWR
70% 60% 50% 40% 30% 20% 10% 0% High(33dBm-29dBm) Medium(27dBm-21dBm) Low(19dBm-13dBm)
Before After1 After2
121
121
Fast Power Control
El_Mounira_MSTXPWR
90% 80% 70% 60% 50% 40% 30% 20% 10% 0% High(33dBm-29dBm) Medium(27dBm-21dBm) Low(19dBm-13dBm) Before After1 After2
122
122
Fast Power Control

Conclusion
The MS_TXPWR was decreased obviously, this was noticed from Abis traces and drive tests. This saves the battery of the mobiles and can decrease the uplink interference in the area. The effect of dynamic power increase was not noticed in the Abis traces. No obvious change in the counters or the QVoice.
123
123
Handover Optimization
Quality Handover Average Window Optimization

HO Margin Optimization Power Budget Limitation
124
124
Bad Pace Analysis
Factors affecting speech quality Handovers are the major cause for bad pace
Bad PACE Repartition
80.00% 70.00% 60.00% 50.00% 40.00% 30.00% 20.00% 10.00% 0.00% Bad Level (Coverage) Poor Quality Poor Level and Quality HO event HO w ith Level HO w ith quality HO w ith quality and Level
DL
UL
125
125
Quality Handover Average Window Optimization

Determine optimum length for quality HO window Determine value based on speech quality analysis Measure HO/Call
126
126
Abis measurements show a degradation of average DL quality after changing the window from 4 to 6 SACCHs Speech quality also degraded in DL
Avg DL Qual before HO (4SACCHs) 35 30

Nb of HOs
Avg DL Qual before HO (6SACCHs)

120% 100%
Nb of HOs
25 20 15 10 5 0 0 1 2 3 4 5 6 7 RxQual DL
80% 60% 40% 20% 0%
18 16 14 12 10 8 6 4 2 0 0 1 2 3 4 5 6 7 Rx Qual DL
120% 100% 80% 60% 40% 20% 0%
127
127
UL Quality has been slightly impacted .
Avg UL Qual before HO (4SACCHs) 30 25

Nb of HOs
Avg UL Qual before HO (6SACCHs)
120% 100%
Nb of HOs
25 20 15
120% 100% 80% 60%
20 15 10 5 0 0 1 2 3 4 5 6 (blank) Rx Qual UL
80% 60% 40% 20% 0%
10 40% 5 0 0 1 2 3 4 5 6 (blank) Rx Qual UL 20% 0%
128
128
Measure the qualtiy Handovers decrease on the tested cell(s). Determine the optimum quality HO decrease versus speech quality.
129
129
Results on Suez City
Sue z HO Pe rforma nce
120000 100000 80000 60000 40000 20000 0 20/08/01
27/08/01 UL Level
03/09/01 UL Quality DL Level
10/09/01 DL Quality
17/09/01
1.4 1.2 1 0.8 0.6 0.4 0.2 0 20/08/01
Suez City
27/08/01
03/09/01 Cal Drop %
10/09/01 HO P er Call
17/09/01
130
130
HO Margin Optimization
HO_margin increase from 5 to 6.
PBGT Volume
40000 35000 30000 25000 20000 8/24/01
16000 14000 12000 10000 8000 6000 4000 2000 0 8/25/01 9/1/01 9/8/01 9/15/01 DL_LEV DL_QUAL UL_LEV UL_QUAL
8/31/01
9/7/01
9/14/01
131
131
HO/Call decreased Speech quality improved
Handovers Per Call 0.49 0.47 0.45 0.43 0.41 0.39 0.37 0.35
25 -Au 27 g-0 1 -Au 29 g-0 1 -Au g-0 31 -Au 1 g 2- S -0 1 ep 4- S -01 ep 6- S 01 ep 8- S -01 e 10 p-01 -Se p-0 12 -Se 1 14 p-0 1 -Se 16 p-0 1 -Se p-0 1
TVOC (Voice Quality indicator)
100.0% 95.0% MOBINIL 90.0% 85.0% Jul 11 Aug 23 Sep 22 2001 2001 2001
TVOC
MOBINIL CLICK
CLICK
Jul 11 2001 Aug 23 2001 Sep 22 2001 93.4% 95.0% 93.4% 95.6% 95.9% 95.8%
132
132
Power Budget Limitation
The parameter RXLEV_LIMIT_PBGT_HO is a threshold on the downlink received level, above which it is not necessary to trigger a handover on power budget.
This adds limitation to the PBGT HO, which can be used in dense areas to decrease the number of Handovers.
Cause = 12 (Power Budget HO) EN_PBGT_HO = ENABLE PBGT(n) > HO_MARGIN(0,n) And AV_RXLEV_PBGT_HO <= RXLEV_LIMIT_PBGT_HO
133
133
Field Trial
The parameter RXLEV_LIMIT_PBGT_HO was generalized on a dense area.
Cell Type Parameter Value Micro cells -55 Macro cells -65
134
134
Ho per Call Decreased
Handover_Per_Call_on_Area
0. 7 0. 68 0. 66 0. 64 0. 62 0. 6 0. 58 0. 56 0. 54
TOT_TMHOCO
15 /0 3 18 /02 /0 3 21 /02 /0 3 24 /02 /0 3 27 /02 /0 3 30 /02 02 / 03 / 0 /02 4 05 /20 / 0 02 4 08 /20 / 0 02 4 11 /20 / 0 02 4/ 2 14 002 /0 4/ 02
135
135
400000 350000 300000 250000 200000 150000 100000 50000 0
500000 450000 400000 350000 300000 250000 200000
Better_cell_HO_Area
Imperative_HO_Area
15 /0 3/ 18 20 /0 02 3 21 /20 /0 02 3/ 24 20 /0 02 3 27 /20 /0 02 3/ 30 20 /0 02 3 02 /20 /0 02 4/ 05 20 /0 02 4 08 /20 /0 02 4/ 11 20 /0 02 4 14 /20 /0 02 4/ 20 02

15 /0 3 18 /20 /0 02 3 21 /20 /0 02 3 24 /20 /0 02 3 27 /20 /0 02 3 30 /20 /0 02 3 02 /20 /0 02 4 05 /20 /0 02 4 08 /20 /0 02 4 11 /20 /0 02 4 14 /20 /0 02 4/ 20 02
136
Better cell
Interf
Level
Quality
136
137
137
Cell Analysis
HO/Call decreased Traffic Increased TCH congestion may result
Oum_Kalthoum_S3
0.9 0.85 0.8 0.75 0.7 0.65 0.6 0.55 0.5 0.45 0.4
15 / 03 18 /02 /0 21 3/02 / 03 24 /02 /0 27 3/02 / 03 30 /02 02 / 03/ / 04 02 05 /20 02 /0 08 4/20 / 04 02 11 /20 / 04 02 /2 14 002 / 04 /02
TOT_TMHOCO
138
138
The parameter RXLEV_LIMIT_PBGT_HO can be used on cell basis for the following objectives: Decreasing number of unneeded handovers. Increasing coverage area of serving cell thus keeping the traffic inside for longer time. Tuning the parameter is based on the required cell radius. Great care must be taken to avoid any impact.
139
139
Call Drop Optimization
RxLev_Access_Min Optimization Radio Link Timeout Optimization
140
140
RxLev_Access_Min Optimization
Measure call drop versus gain in coverage Determine optimum value for RxLev_Access_Min Identify poor coverage spots where traffic can be generated
141
141

Changing RxLev_Access_Min from -102dBm to -108dBm
RxLevAccessMin - MNasr1 BSC

350 300 250 200 150 100 50 0 20-Aug-01 1.6 1.4 1.2 1 0.8 0.6 0.4 0.2 0 03-Sep-01
27-Aug-01
TCH Traffic Carried (Erlangs)
Drop Call Rate (%)
142
142

Radio Link Timeout Optimization
Radio Link Failure is based on SACCH messages It is controlled by the Radio Link Counter ( S ) The max value of ' S ' is broadcasted on BCCH If MS is not able to decode SACCH message, ' S ' decreases by 1 If MS is able to decode SACCH message, ' S ' increases by 2 If ' S ' reaches 0, Radio Link failure is declared
143
143

Radio Link Timeout Optimization
Test different radio link timeout values Measure Call Drop and Call Duration Determine optimum value High values of radio link timeout may result in TCH congestion
144
144
Changing RLT from 10 to 14 seconds
46.5 46 45.5 45 44.5 44 43.5 43 42.5 42 41.5
RLT - Higaz2 BSC
1.4 1.2 1 0.8 0.6 0.4 0.2 0
01/08/01
08/08/01
15/08/01
22/08/01
29/08/01
TCH Mean Holding Time (s)
Drop Call Rate (%)
145
145
Traffic Optimization
Traffic Handover
This feature provides smooth traffic distribution among the cells according to the traffic situation of each cell.
The parameter EN_TRAFFIC_HO(0,n) when enabled has two effects: It adds modifications to the standard PBGT handovers. It enables a new kind of handovers which is Traffic Handover (cause 23).
146
146
If EN_TRAFFIC_HO(0,n) = Enable, then Cause 12: Power Budget HO PBGT(n) > HO_MARGIN(0,N) + max(0, DELTA_HO_MARGIN(0,n))
Cause 23: Traffic HO If DELTA_HO_MARGIN(0,n) < 0dB PBGT(n) > HO MARGIN(N)+ DELTA_HO_MARGIN(0,n)
147
147
DELTA_HO_MARGIN(0,n) Evaluation If Traffic_load(0)= High and Traffic_load(n)=low DELTA_HO_MARGIN(0,n) = - DELTA_DEC_HO_MARGIN If Traffic_load(0)=Low and Traffic_load(n)=high DELTA_HO_MARGIN(0,n) = DELTA_INC_HO_MARGIN If Traffic_load(0)= Traffic_load(n) DELTA_HO_MARGIN(0,n) = 0 Where: DELTA_DEC_HO_MARGIN, DELTA_INC_HO_MARGIN are two cell parameters.
148
148
Traffic Load Evaluation Process
A_Traffic_Load: Cell parameter that defines the averaging window of load samples. N_Traffic_Load: Cell parameter that defines the number of averages to be compared with the thresholds. Thresholds are: High_Traffic_Load, Low_Traffic_Load, Ind_traffic_Load. Load Samples
Averaging A_Traffic_Load Av_Traffic_Load Thresholds Comparison with N_Traffic_Load averages
Traffic_Load
149
149
150
150
Field Trial
The trial was on Hares_S1 which suffers from congestion 28%. The best neighbors are chosen from A traces. Their traffic conditions were checked to ensure there will be enough resources to handle incoming traffic.
151
151
Parameter Settings for Hares_S1

Name A_Traffic_Load N_Traffic_Load Cell Cell Per Definition Averaging window size for traffic load. Proposed Value 8 3 70% 65% 60% Enable 5 5
Number of consecutive load averages used in traffic load evaluation process. High_Traffic_Load Cell Load threshold used to determine when traffic load is high. IND_Traffic_Load Cell Load threshold used to determine when traffic load is indefinite. LOW_Traffic_Load Cell Load threshold used to determine when traffic load is low. En_Traffic_HO Per neighbour This flag enables/disables the detection of traffic handover cause. Delta_INC_HO_Margin Cell Correction factor penalizing handover cause Power Budget when traffic is low in the serving cell and high in the neighbour cells Delta_DEC_HO_Margin Cell Correction factor favouring handover cause Traffic HO when traffic is high in the serving cell and low in the neighbor cells
152
152
Parameters Settings for Neighbor Cells
Name A_Traffic_Load N_Traffic_Load Cell Cell Per Definition Averaging window size for traffic load. Proposed Value 8 3 90% 85% 80% Enable 5 5
153
153
Number of consecutive load averages used in traffic load evaluation process. High_Traffic_Load Cell Load threshold used to determine when traffic load is high. IND_Traffic_Load Cell Load threshold used to determine when traffic load is indefinite. LOW_Traffic_Load Cell Load threshold used to determine when traffic load is low. En_Traffic_HO Per neighbour This flag enables/disables the detection of traffic handover cause. Delta_INC_HO_Margin Cell Correction factor favouring handover cause Power Budget when traffic is high in the serving cell and low in the neighbour cells Delta_DEC_HO_Margin Cell Correction factor penalizing handover cause Power Budget when traffic is high in the serving cell and low in the neighbor cells
100. 00% 95. 00% 90. 00% 85. 00% 80. 00% 75. 00% 70. 00% 65. 00% 60. 00%
Hares_S1
% Call setup
01 /0 3 04 /20 /0 02 3 07 /20 /0 02 3 10 /20 /0 02 3 13 /20 /0 02 3 16 /20 /0 02 3 19 /20 /0 02 3 22 /20 /0 02 3 25 /20 /0 02 3 28 /20 /0 02 3 31 /20 /0 02 3/ 20 02
154
% Call setup
154
155
155
Handover Causes
10000 9000 8000 7000 6000 5000 4000 3000 2000 1000 0
01 /0 3/ 20 02 04 /0 3/ 20 02 07 /0 3/ 20 02 10 /0 3/ 20 02 13 /0 3/ 20 02 16 /0 3/ 20 02 19 /0 3/ 20 02 22 /0 3/ 20 02 25 /0 3/ 20 02 28 /0 3/ 20 02 31 /0 3/ 20 02
Better Cell Level Quality Interf Traffic
156
156
Neighbor Cells
Handover Causes
45000 40000 35000 30000 25000 20000 15000 10000 5000 0
Better Cell Lev el Quality Interf Distance Gen Capt Traffic
01 /0 3/ 04 20 /0 02 3/ 07 20 /0 02 3/ 10 20 /0 02 3/ 13 20 /0 02 3/ 16 20 /0 02 3/ 19 20 /0 02 3/ 22 20 /0 02 3/ 25 20 /0 02 3/ 28 20 /0 02 3/ 31 20 /0 02 3/ 20 02
157
157
Difference Between FDR & Traffic HO
Forced Directed Retry 1 FDR is triggered when the cell resources are unavailable 2 FDR is dependent on the target cell Traffic Handover Traffic HO is triggered after High_traffic_load is fulfilled which can be adjusted.
Taffic HO depends on difference between DL_RXLEV serving and neighbors DL_LEV 3 No limitation on incoming PBGT_HO Incoming PBGT_ HO is penalized if the cell load is high 4 FDR is triggered only on call setup Traffic HO is triggered on both call setup & HO 5 FDR can be triggered to external Traffic Ho can not be triggered to external neighbor ( no restrictions on available neighbor resources)
158
158
CAPACITY ENHANCING TECHNIQUES
159
159
CAPACITY ENHANCING TECHNIQUES
INTRODUCTION FREQUENCY HOPPING CONCENTRIC CELLS MICRO CELLULAR TECHNOLOGY HALF RATE
160
160
Introduction
Capacity enhancing solutions include:
Macro cellular technology Frequency hopping Micro cellular technology In-building solutions Dual band technology Directed retry Concentric cells Half Rate
161
161
Introduction
Basic considerations in choosing the best solution: Available frequency spectrum Capacity requirements Mobile handset availability
Network environment
Ease of future expansion
162
162
Frequency Hopping
A technique adopted in GSM specifications as it is able to overcome two specific problems:
- Multipath Fading
- Interference This allows a tighter frequency reuse thus carrier upgrading can be performed, resulting in an increased capacity while maintaining network quality. If no carrier upgrading is performed, frequency hopping allows quality to be improved while maintaining capacity.
163
163
Frequency Hopping
Multipath Fading
Considering urban environments, radio signals reach the receiver due to reflections and diffraction on different paths resulting in fading effects. The received signal levels are varying dependent on the applied frequency and on the receiver location. Slow MS may stay in a fading notch for a long period of time and suffer from a severe loss of information.
164
164
Frequency Hopping
Frequency hopping introduces frequency diversity and combats multipath fading.

Fast moving mobiles do not stay in long and deep fading holes, so they do not suffer severely from this type of fading. The improvement results in an increased receiver sensitivity under fading conditions and therefore in improved quality in uplink and downlink directions compared to a non-hopping configuration.
165
165
Frequency Hopping
Interference
Without hopping, some receivers (MS or BTS) are not interfered, while others, receiving on another frequency, will experience strong interference. This interference can be permanent such as BCCH frequencies in downlink direction or some fixed interferers incorrectly radiating in the GSM band.
166
166
Frequency Hopping
With frequency hopping, the interfering scenario will change from TS to TS, due to hopping. Thus all receivers (MS and BTS) experience an averaged level of interference.
This will lead to calls having an average quality rather than extreme situations of either good or bad quality (all the calls will suffer from a controlled interference but only for short and distant periods of time, not for all the duration of the call).
167
167
Frequency Hopping
From the BTS point of view one distinguishes: Baseband Hopping (BBH) Synthesizer frequency hopping(SFH)
Baseband Hopping (BBH)

Each transceiver (TRx) is transmitting on one fixed frequency. Hopping is performed by switching the mobiles from burst to burst to different TRXs.
The amount of hopping frequencies N(hop) is determined by the number of TRXs N(TRx): N(hop) <= N(TRx).
168
168
Frequency Hopping
Baseband Hopping
Frame 0
Carrier A
Frame 1
Frame 2
Frame .
Carrier B
Carrier C
Carrier D
8 TS / 8x577s
169
169
Frequency Hopping
Synthesizer Frequency Hopping (SFH)

the TRXs do not get fixed frequency assignments, they may change their frequency from TS to TS according to a predefined hopping sequence. The number of applicable hopping frequencies may be larger than the number of equipped TRxs: N(hop) >= N(TRx). Since no hopping on the BCCH frequency is allowed, synthesizer frequency hopping must not be performed on the BCCH TRx.
170
170
Frequency Hopping
Synthesizer Frequency Hopping
TRX 1 TRX 2 TRX 3 TRX 4 TRX 5
Frame 0 Frequency A Frequency B Frequency C Frequency D Frequency E Frequency F Frequency G Frequency I
Frame 1
Frame 2
Frame .
8 TS / 8x577s
171
171
Frequency Hopping
Hopping Modes
Frequency hopping can be performed in two modes:
Cyclic hopping mode Random hopping mode While in cyclic hopping mode the same hopping sequence will be used periodically, in random hopping mode a pseudo random sequence will be used in order to achieve uncorrelated hopping sequences.
172
172
Frequency Hopping
Hopping Parameters
Mobile Allocation List (MA List)
List of frequencies to be used in a hopping sequence. MA List is limited by GSM recommendations to 64. Hopping Sequence Number (HSN) Parameter determining how the frequencies within the MA List are arranged. Range: 0...63 Cyclic: HSN = 0 Random: HSN = 1...63
173
173
Frequency Hopping
Mobile Allocation Index Offset (MAIO)

Hopping sequence starting point in the MA List. If there are N frequencies in the MA List: then MAIO = {0,1,,N-1}.
174
174
Concentric Cells
A concentric cell is made of two concentrically arranged zones within the same cell: The inner zone and the outer zone.
F2 F1
MS1
BS1
MS2
175
175
Concentric Cells
Two ways of using concentric cells : Capacity Oriented By using it on an interfered cell and guaranteeing a high received level in the inner zone. This allows an additional TRX in the inner zone with a reduced reuse cluster size.
F2 I1 F1 C1 MS1 BS1
F1 I2 C2 MS2
F2
176
176
Concentric Cells
QoS Oriented By using it on an interfering cell to bring down the level of interference by powering down the inner zone carriers. If a frequency is interfered, it is possible to convert it to an inner zone frequency. F1 F1 Interference F1
MS1 BS1 MS2 BS2
177
177
Micro Cellular Technology
Mounted below roof top level. Radius of 300m or smaller. Propagation is primarily line of sight. Improved propagation properties, experience less severe fading and require lower transmitter powers than conventional macrocells. Frequency planning management. Bandwidth division. Handover and access management. New HO power budget types.
178
178
Half Rate
Twice the TCH capacity with the same number of TRXs (using 2 TCH/HR on one timeslot). Equal voice quality in good radio conditions.
Less resistant to errors.

HR impossible for data.
The MS as well as the MSC must support half rate coding.
179
179
TYPICAL PROBLEMS & SOLUTIONS
180
180
TYPICAL PROBLEMS & SOLUTIONS
COVERAGE INTERFERENCE UNBALANCED POWER BUDGET CONGESTION (TCH & SDCCH) CALL DROP QUALITY CALL SETUP SUCCESS
181
181
Coverage
Definition
A network facing coverage problems presents bad Rx-Lev and Rx-Qual at the same time in some areas.
Symptoms
- High drop call rate - High rate of DL quality and level handovers - Low proportion of better cell handover
182
182
Coverage
1. If actual coverage is not the one predicted by radio network planning tools then: - Check antenna system. - Check the parameter bs_txpwr_max (max_tx_bts) to be increased if value is different from planned power budget. 2. If actual coverage is the one predicted then: - Indoor traffic. - If black spot close to cell border, ease outgoing HO.
183
183
Interference
Definition
Interference is the presence of good RxLev and bad RxQual at the same time in the same area.
Symptoms
- SDCCH/TCH Drop - Low proportion of better cell HO - High rate of DL/UL quality HO and interference HO
184
184
Interference
Typical Causes
1. GSM interference - Co-channel - Adjacent Channel 2. External interference - Other mobile network - Other RF sources
185
185
Interference
GSM Interferences
1. Co-channel interference
Interference occurs if the neighbor level is lower than the serving by <= 9dB Level (C/I<9dB)
serving
-9dB
neighbor
F(BTS1)=F(BTS2)
186
Frequency
186
Interference
2. Adjacent channel interference
Interference occurs if the neighbor level is higher than the serving by >= 9dB ( C/I <-9dB) Level
neighbor
9dB
serving
F(BTS1)=F(BTS2)+1
187
Frequency
187
Interference
Symptoms of GSM Interference

High rate of quality HO (specially downlink quality) High rate of call drop High rate of call failure
Solution
Change of frequency Down-tilt of interferer, or even change of antenna orientation Reduction of BS power Concentric cell implementation
188
188
Interference
Non GSM Interference
Other RF interferer : Radar, medical device, army communication devices ...
Symptoms of External Interference

High rate of quality HO (specially uplink quality) High rate of call drop High rate of call failure High rate of interference on idle
Solution
Change of interfered frequency
189
189
Unbalanced Power Budget

Definition
A cell facing unbalanced power budget problems presents a too high path loss difference between UL and DL. Always try to have delta as small as possible.
Symptoms
High ratio of uplink quality HO Low incoming HO success rate High ratio of call drop rate
Typical Causes
Mainly hardware problems
190
190
TCH Congestion
Definition
TCH congestion rate is too high
Symptoms
High TCH congestion rate High directed retry rate if activated Low incoming intra/inter BSC HO success rate
Typical Causes
Special events (football match, car crash..). Cell not correctly dimensioned to support daily peak hour traffic.
191
191
TCH Congestion
Solution
Hardware solution: add new TRxs Software solution : half rate/ forced directed retry/ concentric cells
192
192
TCH Congestion
TCH_Congestion_rate >threshold Check if there is DRI out of service
Yes
High Traffic?
No
Traffic decreases?
Yes
Yes
Contact BSS
Yes
Any site out of service?
Yes
Contact BSS
NO
Special Event?
Yes
- Activate some installed TRXs - Use Moving BTS
No
SDCCH_Congestio n >threshold
YES
NO
Number of Available SDCCH >>needed according to erlang table Choose neighbor with Enough overlapping
Yes
Configure 1 SDCCH to TCH
-HR -Upgrade one more TRX -micro cell solution
Yes
Best neighbors congested ?
No
Congestion Relief or directed retry
193
193
SDCCH Congestion
SD_congestion>thr eshold
Yes Avail_sdcch_max Busy_sdcch_max > 1 Yes Check for DRI out of service Yes Contact BSS
No
Cell on LAC border??
Yes
Increase Cell_reselect_hystersis To 12 db
No
SD_RF_LOSS >10
Yes
Check for interfered carrier and change the SD slot to the other one or change the interfered freq
NO
TCH_congestion> threshold
Yes
SolveTCH congestion problem
No
No
(Motorola)
Avail_tch_max max(Busy_tch_max) >3
Yes
Configure one TCH to SDCCH
No No Upgrade No
Avail_tch_max avg(Busy_tch_max) >1
Yes
Avg (Time No TC available) / Time interval < 0.1 %
Yes
Apply Sdcch reconfiguration
194
194
High Drop Call Rate
Drop_Call_Rate>Threshold
Yes
Yes Is there any site out of service near by? Contact BSS
No Yes Is it a border cell? Check if there is a need for a new site
No Yes TCH_RF_LOSS> threshold Go to TCH_RF_LOSS problem
No Yes
Handover_Failures > threshold

195
Go to Ho_Failure problem
195
Radio Dropped Calls

Check RTF status to know if DRI is not functioning Use CTP to check if there is path-loss in downlink>uplink Contact BSS to determine the interfered frequency Proceed with CTP to determine the interfered carrier ( Disable base band hopping) Use CTP to check if there is path-loss in downlink>uplink Proceed with CTP to determine the interfered carrier ( Disable base band hopping)
TCH_RF_LOSS> threshold
Yes
TCH _assignment _failure> threshold
Yes
No
Path Balance
Contact with BSS
UL_quality>threshold
External_interfere nce
Change the interefered frequency
No Interference
Check frequency plan and try to determine possible interferers
DL_quality>threshold
Path Balance
Contact with BSS
No
Interference
Check frequency plan and try to determine possible interferers
For all neighbors TCH_Congestion>threshold
Yes
Try to solve neighbor TCH congestion Problems
196
196
HO Dropped Calls
Check HO relations between serving cells and neighbors Use A traces to determine target cells with majority of handovers
Handover Failures> threshold
Yes
Check BCCH and BSIC of neighbors May be neighbors of same BCCH and BSIC are defined.
If one of the neighbors is not declared ,consult drive test to make sure if we need to declare it to the serving cell.
197
197
UL Quality HO
UL_quality>threshold
Overshoot
Dist_HO > threshold
yes
-Use drive test to determine the overshoot spot -Change antenna orientation(down tilt) -change MS_max range
No
Level_HO >30
yes
Coverage
-Investigate for the need of new site -Up tilt antenna
No
Use traces to check path losses in UL??
yes
Hardware problem Contact BSS
No
TRX_Duration<18s
yes
Interference_on_idle(Motorola) or interference_bands(Alcatel) >threshold ?? Peaks of interference not proportional to traffic??
yes
External interference Change the interfered freq GSM interference Change one of the interfered freq.
Check for Adjacent or Co channel frequency
yes
198
198
DL Quality HO
DL_quality>threshold
Overshoot
Dist_HO > threshold
yes
-Use drive test to determine the overshoot spot -Change antenna orientation(down tilt) -change MS_max range
No yes
Level_HO >30
Coverage
-Investigate for the need of new site -Up tilt antenna
No
Use traces to check path losses in DL??
yes
Hardware problem Contact BSS
No
TCH_Duration<18s
yes
For any carrier BER >1.12%
yes
Check for Adjacent or Co channel frequency
Interference
Change the interfered freq
199
199
HO Failures
Handover_Success_Rate < threshold or < average of week + margin
Check BCCH/BSIC of neighbors and serving
BTS_fail_rate>xx
Out__BSC_Success_rate<
Out_MSC_Success_rate<
-point neighbors with same BCCH/ BSIC -point neighbors with same BCCH/ BSIC as serving
Check the parameter EN_INTRA_REPEATED=0
For all neighbors in same BSC Check In_BSC_Success_rate<XX
For all external neighbors Check In_MSC_Success_rate<XX
yes
Change interfered freq For these neighbors Check:
Check neighbor parameters
UL/DL quality handover >xx yes Change interfered frequency
200
200
Call Setup Success
Call_setup_success_rate<threshold
TCH_access_failure>thr
SD_Drop_rate>thr
TCH_blk_rate>thr
Hardware problem Reset
SD_drop_radio / SD_drop>xx
SD_drop_BSS_pb / SD_drop>XX
TCH congestion Pb
For the interfered carrier: Change the frequency
BSS pbm
201
201

Network Optimization

Загружено:

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

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

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

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

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

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

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

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

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

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

Network Optimization

Загружено:

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

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

NETWORK OPTIMIZATION

MobiNil, The Egyptian Company for Mobile Services February 2004

Availability (Access, Capacity)

Changes in subscriber growth

Optimization Engineer Tasks

Support good audio quality.

respect the grid giving the optimization engineer the

Conduct post analysis

Reports and Action Plans

Reports and Action Plans

Reports and Action Plans

Radio Planning Tool

OMC Statistics Monitoring

TEMS Light :- indoor measurements.

Change the minimum number of parameters possible.

Per cell basis

Immediate Assign Reject

Channel Request T3120 Re-transmission

T3120 Immediate Assignment

AGCH Reserves SDCCH

No Response from MS - T3101 Expires

No of Channel Requests with cause as MOC & MTC

Immediate Assignment MM/CC Signaling on SDCCH

Assignment Command Assignment Failure

Assign Request Assign Failure

No of Assignment Failures from MS Total No of TCH Assignments

BTS detects RF fink failure in the Uplink on TCH.

5 Fai l - BSS 4 Fai l - Radi o Congesti on 3 Success

2.5 Success 2 ROC Dr op - Radi o 1.5 Dr op - BSS

Reduce Interference to reach the required quality

Theoretical Frequency Planning Automatic Frequency Planning

Theoretical Frequency Planning

Network has many cells

Theoretical Frequency Planning

Co-Channel (Reuse) Cells

Theoretical Frequency Planning

The hexagonal model is used to simplify the planning.

Theoretical Frequency Planning

Theoretical Frequency Planning

Theoretical Frequency Planning

Theoretical Frequency Planning

Theoretical Frequency Planning

Theoretical Frequency Planning

Receives interference from lesser directions. 57

Theoretical Frequency Planning

Theoretical Frequency Planning

Theoretical Frequency Planning

Theoretical Frequency Planning

Theoretical Frequency Planning

4/12 pattern avoids adjacent channels in adjacent cells

Theoretical Frequency Planning

Theoretical Frequency Planning

Automatic Frequency Planning

Automatic Frequency Planning

Can include existing frequency planning

Automatic Frequency Planning

Drive Tests Speech Quality

TEMS for drive test and integration

Actix Analyzer for post processing

Check for missing neighbor relations.

Histogram - RxQual (count) 25000

Histogram - RxQual (CDF)

100 5000 90 4500

Histogram - RxLev (count)