NETWORK OPTIMIZATION

CONCEPT
&
PRELIM PROJECT PROPOSAL

Objective
To identify problems in the Network(NW) and recommend
remedies so as to achieve pre-determined performance
benchmarks and improvement in QoS.
Goal
Increase in Airtime Usage
High Revenue Realization
Reduce Churn

Bonsai Networks/En

July, 2001

PURPOSE

Quality Enhancement( Reduce drop calls, easy

accessibility, reliability, good voice quality/
intelligibility)

Increase in NW Efficiency (max. utilization of

resources and minimize NW breakdowns )

Positive perception built up in the market

Bonsai Networks/En

July, 2001

WHY OPTIMISATION ???

It is inevitable that network doesnt perform exactly as planned
due to lack of accuracy in information related to environmental
conditions, terrain conditions, initial inputs, planning
engineers assumption and judgments, error in data entry,
calibration of tools, mal-functioning of equipments ,
implementation errors and overloading in NW , etc.
To identify and correct these impairments is the first step
towards optimisation. Optimisation is done in two scenarios.

Implementation Phase
Post-implementation phase

(we will discuss here post-implementation phase optimisation process)

Bonsai Networks/En

July, 2001

KEY DRIVING FACTORS

The key driving factors are:
Drop calls
HO Success/Failure rate
Congestion & Call set-up time
Network Accessibility
PSTN interconnect availability
Signaling

Bonsai Networks/En

July, 2001

REQUIREMENTS
1.
2.
3.

4.
5.

Skilled Optimisation engineers

Skilled RF planning, OMCR , BSS Maintenance & MSC
engineers
OMCR based cell analysis Tool, DRIVE TEST Tool like
TEMS, engineering mode enabled MS, Laptop/ PC, RF Tool
- Planet / Netplan etc., Protocol Analyzer, Power meter,
Spectrum analyser etc.
Vehicles
Administrative support as necessary

Bonsai Networks/En

July, 2001

SCOPE OF WORK
1.

Monitor NW performance through OMC Report ,

Customers Complaints, conducting Drive Test/walk test
in problematic areas, use of OMC Tool, Planning Tool
2. Obtain Log Files from Drive Test and Analyse
3. Recommend Maint. Team (also OMCR) for changes in
network sw/hw and document with intimation to RF
planning
4. Post Check Up after every SW / HW changes including
during new cell-site integration
5. Emergency / Random check up as it is needed
NB: Network HW audit can be separate exercise

Bonsai Networks/En

July, 2001

DELIVERABLES

Improvement in Drop Call Rate

Improvement in Call success Rate
Improvement in HO success Rate
Improvement in GoS/ congestion
Improvement in voice quality
Identify grey areas in the network

Bonsai Networks/En

July, 2001

STRATEGY
The whole optimisation exercise can be divided into
following parts:

Data validation
Routine network-wide drive test in pre-determined routes
Conduct walk test/ drive test in problematic areas
Based on Inputs from OMC-R performance statistics and
customer complaints
Cell-site visits if necessary

Bonsai Networks/En

July, 2001

DATA VALIDATION
The first step of Optimizaton is to confirm if the database
maintained in BSC/OMC and hw organization in cellsites
are correct according to the RF Planning it should be
undertaken at least once before undertaking any further
steps for the area under study.
Generally the checks consists of cellsite parameters check
such as frequency; site/BTS configuration;various CCH,
DCH allocations;transmit power, power steps; Rx
threshhold; HO parameters; neighbour list;list of
enabled/disabled parameters;cell site co-ordinates, tower/
antenna ht., azimuth, tilt, antenna gain; etc.

Bonsai Networks/En

July, 2001

10

POST-IMPLEMENTATION CHECK

After every database download,/or cell site parameter

change and/or integration of new network element drive
test is carried out to ensure the changes effected desired
result and there is no adverse impact on the network.

Bonsai Networks/En

July, 2001

11

DRIVE TEST

Drive Test is conducted to identify exact nature of problem

and cause on real time and place basis. These are:
Call set up problem,e.g. cell selection / reselection etc.
Coverage problem
Hand Over (HO) process
Interference/noise level
Various system messages (Layer 1,2,3 )
RF Issues relating to traffic problems
Terrain profile like water base, large structures, foliage,
paddy fields etc..
Monitor the performance of a competitors network

Bonsai Networks/En

July, 2001

12

PERFORMANCE ANALYSIS
1.
2.
3.
4.
5.

The performance of a NW can be studied under several

categories :
Call Setup Success/Failure
Call Drop
Congestion & NWAccessibility
PSTN Interconnection
Signaling loading/ processor loading

Bonsai Networks/En

July, 2001

13

Call Setup Success/Failure

It may occur due to several reasons such as :
Poor Coverage
Non availability of Control Channel, TCCH
Interference in SDCCH Freq
Improper Setting of SDCCH Ho
Malfunctioning of MS
Improper Setting mob_max_range
Problem in PSTN Connectivity
Synchronization
----all these points with similar aspects are discussed under
section Congestion, PSTN Interconnection & Signaling Ch.
Bonsai Networks/En

July, 2001

14

Call Drop

Call Drops may be due to :

High BER,
Link Failure,
TCH Killing,
RF Loss
Terrestrial Interface Problem
Equip. Failure
HO Failure
Interference

Bonsai Networks/En

July, 2001

15

Call Drop:
High BER : Engineer will check Tx/Rx Path as suggested by OMCR
Check with OMCR if there is any alarm like VSWR
He will also need to find out if there is any topographical
obstacles or any big building and/ trees affecting wave
propagation
Synchronization Loss : See the Alarm Log : Recalibration of equipment may be
needed
BTS / MS malfunctioning to be checked

Bonsai Networks/En

July, 2001

16

Call Drop:
Link Failure : Transmission Media(Optic Fibre / MW) to be checked
Power Setting of the Transmitter to be checked
Value of Path Bal. 100 - 120 for Motorola Radio
Call Re-establishment:-To be Enabled
RF Loss: Poor Receive Signal Level
- due to obstruction in propagation by trees, big bldg. Etc.
- Low coverage area ; fix rxlev_access_min properly for HO to take place before rxlev
goes to a low level

Bonsai Networks/En

July, 2001

17

Call Drop:
Link Failure : Transmission Media(Optic Fibre / MW) to be checked
Power Setting of the Transmitter to be checked
Value of Path Bal. 100 - 120 for Motorola Radio
Call Re-establishment:-To be Enabled
Interface Problem : High BER OR CKT Problem in MSC, PSTN & Other SWITCHING Elements
- Check at OMCR if any Link on BSC - XCDR - PSTN route is disconnected
and get fixed

Bonsai Networks/En

July, 2001

18

Call Drops:
RF Loss: Poor Receive Signal Level
- due to obstruction in propagation by trees, big bldg. Etc.
- Low coverage area ; fix rxlev_access_min properly for
HO to take place before rxlev goes to a low level
Improper Tilt / Orientation to be rectified
Setting Power of BTS(max_tx_bts) to be done properly
Malfunctioning of MS to be checked
Enable call Re-establishment Feature
Bonsai Networks/En

July, 2001

19

Call Drops:
Equipment Failure : Radio Faulty - Re-calibration or changing of the Unit required
MS unsuccessful in tuning (Assign. Failure)
PCM / Signaling Interface problem at BSC/MSC
Unknown Reasons :- It may be due to 1.Database change 2.
Maint. Activity.

Bonsai Networks/En

July, 2001

20

Call Drop :
Handover Failure :
It consists of several steps ; you have to be very cautious
while doing each step . They can be described as follows :
Defining Type(Rx qual, Rx_lev/ power
budget,interference/BER); Choice of Neighbors/HO
candidates, BSIC Values
Also you need to define if MSC and/ BSC is involved in
the decision process :
Set other parameters : ho_margin, hreqave, rx_lev,
intracell_ho, TA, CRO, rx_lev_access_min, etc.

Bonsai Networks/En

July, 2001

21

 Also, following problems may come up in the HO process

which needs to be rectified :
- Protocol Error in HO messages
- Malfunctioning of MS for Measurement Reports
Enable ho_required_reject_switch to avoid unnecessary
HO attempts repeatedly ( in case of not imperative call )
PBGT Ho - Enabled to redistribute the traffic ( for quality
improvement or congestion relief ); PBGT > ho_margin

Bonsai Networks/En

July, 2001

22

Call Drop

Locate areas of Interference from OMCR

Interference can also be studied by Drive Test
Following actions may be taken for improving quality
Antennae Tilt & Orientation
Space Diversity in uplink
Power Control - MS , BTS
SET max_tx_ms & max_tx_bts as max power for MS and BTS
respectively

- Hopping Frequency , BCCH / NON_BCCH Frequency : they may be

-

changed if there is any interference in those channels

Implementation of Hopping/DTX/DRX also reduces interference
Enable HO parameter for interference ; i.e.
interefer_ho_allowed =1

Bonsai Networks/En

July, 2001

23

CONGESTION & NW ACCESS

Two types : 1. TCCH 2. SDCCH
1.TCCH Congestion : - Actual Valid Calls - Reduced by increasing Capacity of
Channels, Adopting Mixed Cell Structure, Appropriate HO
Parameter Setting and Neighbor Definition
- Congestion is relieved by putting calls in queue
- It may be due to Protocol Error(Assignment Request From
MSC Fail) Non-availability of CCCH (Assign. Blocking)

Bonsai Networks/En

July, 2001

24

 Handover during Congestion :

- Enable the feature ho_exist_congest
- HO for Traffic Redistribution : Enable ho_pbgt=1
2. SDCCH Congestion : The reasons may be 1. Heavy Traffic 2. Frequent
Location Update 3. Vague RACCH 4. SDCCH Ho
Vague RACCHs are analyzed by looking the perf.
Parameter - no. of channel requests for MS fails

Bonsai Networks/En

July, 2001

25

 Optimizing Vague RACCH

- provide proper rxlev
- guard against interference
- avoid more location areas preferably in Heavy Traffic
and High Speed Areas
- set mob max. range ( in BSC ) properly
- appropriate setting in reuse cell (else, it may cause
interference )
- malfunctioning of MS; fails after sending RACCH signal

Bonsai Networks/En

July, 2001

26

Optimizing Location Update

- Re-defining Location Update as per need
- Re-defining multiframe structure( provide more no of non
combined channel)
Dynamic reconfig. which helps to convert TCH to SDCCH
and thus provide more nos. of SDCCH in busy traffic
areas
Appropriate setting of HO parameter will redistribute
SDCCH overloading

Bonsai Networks/En

July, 2001

27

PSTN INTERCONNECTION

It is most likely that a call process may not be successful

because of various problems in MSC & PSTN side . Some
notable problems can be analyzed as follows :Interface Problem -Its been discussed under Call Drop
Congestion - This problem can only be overcome by
increasing capacity of PSTN
Telephone Busy at PSTN End - TCH will not be through
Echo - Because of inherent quality of GSM System; i.e.
two wire to four wire config. from PSTN to MSC side .
Echo Canceller between PSTN & MSC to be checked

Bonsai Networks/En

July, 2001

28

SIGNALLING
For a busy traffic non combined channels must be used
Supplementary services during congestion period to be stopped
Reserving CCCHS for AGCH ; if paging messages are overloaded then
Immediate Assignment may not take place
There should be sufficient no. of RACCH
Non-availability of CCCH will lead to Assignment Blocking - Fix sufficient
nos. of CCCH

Processor Loading:
Uniform distribution of traffic BSC wise is most important to -distribute signaling
loading. Also it is important to
-distribute cell sites among BSCs and assign processors
-accordingly to even out processor loading.
Similarly transcoder assignment for BSCs is also carefully done.

Bonsai Networks/En

July, 2001

29

SUMMARY
Since Optimisation is a continuous process of checking,
rectification and post - rectification checking and further
modification (if necessary); and a particular fault may involve
repeated exercises as discussed above, it is not possible to
categorize all different activities day wise or week wise.
However, marked improvement can be seen during the course
of optimisation. It is practicable to achieve at least 90% of
CSSR with Drop Call Rate <3% - 4% within first half of the
project period leaving sufficient time for Frequency reloading (if required) and further checking of all NW Entities
and fixing various problems in time.

Bonsai Networks/En

July, 2001

30

Project Proposal
It depends upon the size(coverage area) of the NW, its
Capacity, and Fulfillment of various points as noted in
Requirement List
Taking all favorable conditions, we will presume a work_flow
for different capacity of NW as follows :
No. of Sites->

100

200 - 300

500

800

1000

Months
->
Engineers ->

1
2

2
2

2
3

2
4

2
6

Bonsai Networks/En

July, 2001

31

Proposed Schedule of Activities

Week 1 : Assessment of Existing Performance

Prior to the commencement of the optimisation service, the major network

configuration activities need to be stopped so as to have a reliable pre and
post comparison.
Drive testing : On the major routes drive tests can be performed with the
help of tools like TEMS, Buzzard or Q-voice. The voice quality plots /results
can be used subsequently for comparison purposes.
Performance data will be gathered over the whole network over a period of
full billing cycle i.e. minimum one working week, because may not address
cyclic traffic changes. One month previous data will be much more helpful.
A performance report will be submitted using the collected performance
data clearly highlighting the key parameters such as drop call rates for the
whole network for whole week.

Bonsai Networks/En

July, 2001

32

Week 2&3 : The Actual Optimisation activity

The detailed performance analysis will be performed. The problems will be identified and
solutions will be recommended and implemented. Then cross verification will be done for
any improvement.

The problems might include:

Incorrect setting of database parameters

Interworking issues between network elements e.g MSC-->BSC-->BTS
Faulty hardware
Co-channel or adjacent channel interference issues

The solutions might include:

Optimisation of BSS database parameters/timer settings/ parameters related to hand
overs and/or power control processing etc.
Used of Vendor provided advanced feature for network performance improvement.
Replacement of faulty hardware.
Neighbor list optimisation.
Antenna tilt/orientation changes
BCCH frequency changes to reduce co-channel and adjacent channel interference.

Bonsai Networks/En

July, 2001

33

Week 4 : Performance comparisonPre Vs Post Optimization

Performance data will be collected for a billing cycle for the full
network. A comparison status report will be prepared for any
improvement/ deterioration for those observed key parameters
like drop call rate, network congestion, HO loss etc.

Bonsai Networks/En

July, 2001

34