2.GSM Network Optimization

GSM NETWORK OPTIMIZATION 1
PDF Created with deskPDF PDF Writer - Trial :: http://www.docudesk.com
MobileComm Technologies India Pvt. Ltd.
Dallas . Atlanta . Washington . LA . Sao Paulo . New Delhi . Toronto . Muscat. Sydney
Ritesh Karan
2
GSM NETWORK OPTIMIZATION
Ritesh Karan

3
Copyright 2010 MobileComm Technologies India Pvt. Ltd.

All rights reserved
MobileComm is committed to providing our customers with quality instructor led

Telecommunications Training.
This documentation is protected by copyright. No part of the contents of this
documentation may be reproduced in any form, or by any means, without the prior written consent of
MobileComm Technologies .
Document Number: RK/CT/5/2010
This manual prepared by: MobileComm Technologies
MobileComm Technologies(India)Pvt. Ltd.

424, First Floor, Udyog Vihar Phase -4,
Gurgaon-122002
Headquarter:
MobileComm Professionals Inc.
1255 West 15th Street, Suite 440
Plano, TX, 75075
Tel: (972) 633-5100
Fax: (972) 633-5106
www.mcpsinc.com
Ritesh Karan
Module Objectives 4
Give an overview about the Call Signalling

Describe the call phases and causes.
Demonstrate, the signalling of basic calls .
Give an overview about the DX cause
Describe the purpose of the Network Optimization
Explain the various performance monitioring KPI’S and discuss how to
overcome these problems.
Discuss the Timers setting in Nework
Ritesh Karan
GSM NETWORK OPTIMIZATION 5
•Call signalling
•Call Phases
•Overview of Basic Call
•DX cause
•Network Optimization
SDCCH Traffic (trf_11b
SDCCH access probability
TCH traffic
TCH blocking
TCH drop call ratio
Ho failure
•Timers
•Alarms
Signalling (Mobile Originating Call) 6
MS Channel request (RACH) NETWORK

Immediate assignment (AGCH) Immediate assignment
Service request (SDCCH)

Service request
Authentication request (SDCCH)
Authentication response (SDCCH) Authentication
Ciphering mode command (SDCCH)
Ciphering mode complete (SDCCH) Ciphering mode setting
Setup (SDCCH)
Call proceeding (SDCCH) Call initiation
Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel
Alert (FACCH)
Call confirmation
Connect (FACCH)
Connect acknowledged (FACCH) Call accepted
Signalling (Mobile Terminating Call) 7
MS Page request (PCH) NETWORK

Channel request (RACH) Immediate assignment
Immediate assignment (AGCH)
Page response (SDCCH)
Service request
Authentication request (SDCCH)
Authentication response (SDCCH) Authentication
Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting
Setup (SDCCH)
Call confirmation (SDCCH) Call initiation
Assignment command (SDCCH)

Assignment complete (FACCH) Assignment of traffic channel
Alert (FACCH)
Call confirmation
Connect (FACCH)
Connect acknowledged (FACCH) Call accepted
Signalling (Call Release) 8
Network initiated
MS Disconnect NETWORK
Release Call clearing
Release complete
Channel release
Release
MS initiated
MS Disconnect NETWORK
Release Call clearing
Release complete
Channel release
Release
Overview of Basic Call 9
Basic Call provides speech or data services to the

mobile subscriber by offering the means for
establishing speech or data calls with half or full rate.
.
10
Overview of Basic Call

•Paging Procedure
•Channel Required Procedure
•Channel reservation procedure
•Immediate assignment procedure
•SCCP connection establishment procedure
•Ciphering procedure
•Assignment procedure
•Channel release procedure
Paging procedure 11
The paging procedure offers the network the means to start the establishment of a
mobile terminating call with a given MS.
Figure: Paging procedure when paging comes from MSC
If the MS does not answer within a given time limit, the MSC repeats the PAGING
COMMAND message.
Paging Procedure 12
•Paging messages sent on PCH which MS continually listens to (TSL0 on BCCH TRX)
•Limited to geographical sub-group of BSCs using LACs
•Paging sub-groups are used to save MS battery-life since MS only needs to listen to its own
sub-channel and not to the entire PCH
•MS can be paged using IMSI or TMSI (determines number of MSs that can be paged per
message (IMSI = 2 MSs : TMSI = 4 MSs)
•Split between PCH and AGCH determined by numberOfBlocksForAccessGrant and the type
of channel configuration used (i.e. combined or non-combined)
Non
Combined • PCH can be used for AGCH if
Combined no paging messages are to be
Blocks for PCH & AGCH 3 sent, but AGCH can not be used
9 for PCH
No. Blocks Res AGCH 0-2 0-7 • Three types of paging
messages (type 1, 2 and 3)
No. Blocks Res PCH 3-1 depending on no. of MSs paged
9-2
PAGING message 13
If the BSC receives the PAGING message from the MSC (a), the PAGING message includes
the following data:
•message type
•MS identity IE (IMSI)
•temporary MS identity (TMSI) (optional)
•cell identifier list (optional)
•channel needed (optional). MSC BSC
Paging Message
Figure: Channel needed information element
The Channel Field (bits 1-2 of octet 2) indicates the further combination of channel which will be needed. It is
coded as follows:
Figure: Values of Channel Field bits

PAGING COMMAND message 14
The PAGING COMMAND message from BSC to BTS

includes the following data: BSC BTS
message header
Paging Command
paging group
MS identity
channel needed (optional).
Paging Group 15
In combined Mode :- BCCH + CCCH in a 51-frame multiframe- (9 CCCH block)
In Non-Combined Mode:- BCCH + CCCH + 4 SDCCH (stand-alone dedicated control channel)! (3 CCCH block)
Paging Gp= ((IMSI mod 1000) mod (BS_CC_CHANSx N)) mod N

Where N =No of Paging Groups = No of PCH x BS_PA_MFRMS
IMSI =International Mobile Subscriber Identity
Mod =MODULUS (see additional notes on modulus at the end)
BS_CC_CHANS = CCCH (COMBINED (3) or NONCOMBINED (9))
HOW TO WORK OUT WHICH PAGING GROUP AN MS IS ASSIGNED TO 16
Example
Assuming that the relevant parameters for the calculation are as follows:
IMSI= 460003811319045
N = Number of Paging Groups (For this we will assume there are 28 Paging Groups)
Mod = Scientific calculation. Full notes at end explaining mod.
BS_CC_CHANS = 9 (As we will assume for this that NON-COMBINED Signaling is in use)
So the calculation {(IMSI mod 1000) mod [BS_CC_CHANS*N]} mod N based on the information in the previous slide
would be as follows:
{(460003811319045 mod 1000) mod [ 9 * 28 ]} mod 28
STEP1.
(IMSI mod 1000) = (460003811319045 mod 1000)
460003811319045 / 1000 = 460003811319.045
mod then requires removing the whole number and multiplying the remainder by the original mod number.
This would give 0.045 *1000 = (45)
STEP2.
From previous slide, (BS_CC_CHANS*N)
BS_CC_CHANS = 9
Number of Paging Groups (N) = 28
(9 * 28) = (252)
CALCULATION 17
STEP3.
{(IMSI mod 100)mod[BS_CC_CHANS*N]} = {(45) mod [252] }
45 / 252 =0.1785
mod requires removing the whole number however as there is no whole number in this case then the
remainder is multiplied by 252.
This would give 0.1785 * 252 = 44.982 (Round up to 45)
STEP4.
Result obtained in Step 3, mod 28, therefore: (45) mod 28
45 / 28 = 1.6071
mod requires removing the whole number and multiplying the remainder by the original mod number.
This would give 0.6071 * 28 = 17
Therefore we conclude that IMSI 460003811319045 belongs to Paging Group 17.
For More information on Paging Groups see GSM Specification 05.02.

NSN-PCH Parameters 18
BSC parameters
noOfMultiframesBetweenPaging 2..9 multi frames Defines how often

MS listens to paging
MSC parameters
Repaging Interval 50..100 ms Time between

consecutive paging
attempts
Repaging Attempts 0..5 Number of paging

repetitions Buffering
BTS stores up to 8 paging messages of the MSC in page group buffer

Channel required procedure 19
The channel required procedure offers the MS the means to start the establishment of a
mobile originating call or to answer the PAGING REQUEST message.
The channel required procedure is presented in the following figure.
Figure: Channel required procedure

CHANNEL REQUEST message 20
The MS uses the CHANNEL REQUEST message to request for a dedicated signalling
channel SDCCH. It sends the CHANNEL REQUEST message (a) to the BTS on the RACH.
The message is sent in random mode and it consists of two different information elements that
are coded as follows:
Figure: CHANNEL REQUEST message, only one octet long

Establishment causes 21
The following establishment causes are supported (the random reference field is
marked with xs):
Figure: NECI parameter is set to OFF

22
Figure: NECI parameter is set to ON

Establishment causes

CHANNEL REQUEST MESSAGE 23
•The network uses the random reference and the MS access slot number to
identify and to address the MS.
•The MS starts the GSM timer T3120 and waits for its access acceptance,
which is an IMMEDIATE ASSIGNMENT message on the AGCH.
•If the MS access is not granted within the time limit defined by T3120, the
MS makes a second attempt and sends another CHANNEL REQUEST
message with a new random reference on the next time slot. A new value of
the GSM timer T3120 is computed and used.
•The MS repeats this procedure either until it is granted access or until the
number of repetitions reaches the set maximum
After receiving the proper CHANNEL REQUIRED message from the

BTS, the BSC starts to allocate an SDCCH channel.
NSN-RACH Parameters 24
Mobile sends channel requests to BTS seperated by random time intervals in case of no answer!
Parameters
maxNumberRetransmission 1,2,4,7 Defines maximum allowed number of

retransmissions
numberOfSlotsSpreadTrans 3..12,14,16,20,25,32,50 Defines time interval between
consecutive retransmissions
Random time interval between consecutive retransmissions
t = S + random [0,.. numberOfSlotsSpreadTrans – 1] RACH slots
S depends on numberOfSlotsSpreadTrans signalling channel mapping (CCCH + SDCCH combined or not

in one multi frame)
numberOfSlotsSp S (CCCH combined S (CCCH not combined
readTrans with SDCCH) with SDCCH)
3,8,14,50 55 41
4,9,16 76 52
5,10,20 109 58
6,11,25 163 86
7,12,32 217 115
numberOfSlotsSpreadTrans = 10
signalling channel mapping = not
combined -> S = 58
-> t = 58..67
time channel
requests
Channel reservation procedure 25
After receiving the CHANNEL REQUIRED message from the BTS

or the
ASSIGNMENT REQUEST message from the MSC, the BSC starts
searching for a relevant channel
Channel activation procedure 26
•After a successful reservation of a new SDCCH channel, the BSC activates

it by sending the CHANNEL ACTIVATION message to the BTS.
•The GSM timer T9103 is used to supervise the channel activation
procedure.
•The BTS acknowledges a successful channel activation or unsuccessful
with the CHANNEL ACTIVATION ACK or NACK message respectively.
Immediate assignment procedure 27
The immediate assignment procedure is presented in the following figure:
•The IMMEDIATE ASSIGN message facilitates the assignment of the MS onto an SDCCH channel.
•The IMMEDIATE ASSIGN REJECT message facilitates the refusal of the access
•If the SDCCH channel reservation or activation fails, the BSC sends the IMMEDIATE ASSIGN REJECT
message to the MS
•The GSM timer T3101 supervises the immediate assignment procedure.
The BSC can reject up to four mobiles with one IMMEDIATE ASSIGNMENT REJECT message
assuming that the CHANNEL REQUEST messages have arrived within a fixed time limit
NSN AGCH Parameters 28
Downlink CCCH blocks
PCH can be used for AGCH messages

AGCH cannot be used for PCH messages
Reservation of CCCH blocks for AGCH
noOfBlocksForAccessGrant 0..7 possible number, if CCCH and SDCCH are not

combined
1..7 possible number, if CBCH is used in non
combined configuration
0..2 possible number, if CCCH and SDCCH are
combined
Preference of AGCH messages on PCH
noOfBlocksForAccessGrant ≠0 PCH can be used only, if no paging messages

have to be send
=0 AGCH messages have higher priority than PCH
ones
SCCP connection establishment procedure 29
The BSC starts to initiate the SCCP connection for the MS after receiving the
ESTABLISH INDICATION message for the SDCCH establishment
from the BTS. The GSM timer T9105 is used to supervise this procedure. If
the SCCP link establishment fails, the BSC releases all resources related to
this transaction.
T9105 start T9105 End

Ciphering procedure 30
Ciphering is one of the security procedures designed to protect the

subscriber identity and data. It is an optional procedure in GSM. When
ciphering is active, all information exchanged between the mobile and the
network on the dedicated radio channels is encrypted. The key previously
set between the network and the MS is used to encipher and to decipher
the encrypted information.
Assignment procedure 31
The assignment
procedure is used to
assign the MS to the
correct TCH channel.
The selection of the

TCH channel is based
on the information
received from the
MSC
Assignment procedure 32
•The MSC sends an ASSIGNMENT REQUEST message to the BSC for the assignment of
channels on the A interface and the radio interface.
•The MSC also runs a supervisory timer i.e T10 for the assignment procedure.
•The BSS responds by sending the MSC the ASSIGNMENT COMPLETE,ASSIGNMENT

FAILURE or the QUEUEING INDICATION message(T10 stop)
•If the MSC fails to receive any of the messages within the time limit defined by the timer,
it clears the call with a CLEAR COMMAND message after that the BSS releases the MS
connection with the channel release procedure.
Channel release procedure 33
The channel release

procedure is used for
releasing a dedicated radio
channel. The channel
release procedure is
started either by the BSC
or the MSC
Figure 16. Channel release procedure by MSC
a. If the MSC starts the channel release procedure, it sends the CLEAR COMMAND message to the
BSC
b. If the BSC starts the channel release procedure, it sends the CLEAR REQUEST message to the
MSC, which then sends the CLEARCOMMAND message to the BSC.
34
Fig. Channel release started by the BSC

Channel release procedure

35
GSM Causes and DX Causes

Levels of information 36
Performance
Reports KPI's
BSS
Measurements Counters
Observations DX-causes
GSM Causes and DX Causes 37
Successful
DX CAUSE
N
DX CAUSE
1←
Unsuccessful = CLEAR CODES
1
GSM CAUSE
MSC BSC BTS
N
1←
COUNTERS
Netact
Nokia BSS counters: numbering 38
Counter = XXXYYY where

XXX = measurement table
YYY = counter number in measurement
table
Example: counter 001000 or c1000

XXX = 001 = c1 = traffic measurement
YYY = 000 = SDCCH requests
39
DX-CAUSE
SDCCH
DX-cause cause mapping
TCH
CHANNEL TYPE
CAUSE VALUE
COUNTER
PHASE
KPI

Counter pegging example 40
NMS2000 Counter 1003 1004 1005 1013 1014 1015
CAUSE VALUE 315 - conn_fail
PHASE 1-8 9-11 12-14 15
CHANNEL TYPE SDCCH TCH

DX Cause
Note that there are no counters that are incremented by the same DX Cause, so
if you have the channel, phase and cause value you are able to know which is
the counter incremented!
Concept of Optimization 41
• Radio network optimization means network performance improvement utilizing

existing network resources.
– Steps in general
• Data collection and verification
• Data analysis
• Parameter and hardware adjustment
• Optimization result confirm and reporting
• The purpose is increasing the utilization of network resources and solving the
existing and potential problem on the network, identifying solutions for future
network planning.
42
Coverage
Optimize
Capacity
Concept of Optimization
Quality

• Due to the mobility of subscribers and complexity of radio wave propagation, most
of network problems are caused by increasing subscribers and the changing
environments.
• Radio Network Optimization is a continuous process that is required as the network
evolves
• In the following case, the network should be optimized

– New network or expansion on existing network
– The network quality decreased seriously and there are many complaints from
subscribers.
– An event occurs suddenly which affects the network performance seriously.
– The number of subscribers increased and affects the network performance
gradually.
Input for Optimization
CUSTOMER
COMPLAINTS
OPTIMIZE
TRAFFIC DRIVE
STATISTICS TEST
KPI of Radio Network 46
– KPI (KEY PERFORMANCE INDICATORS)

Indicates overall performance of network over a period of time
Good way to monitor network trends and anticipate future problems
Data obtained from drive test and traffic statistics
47
Flow Chart of Network Optimization

Parameter Adjustment Principles 48
Parameter adjustment procedure
MONITOR IDENTIFY
EFFECT PROBLEM
MAKE
MAKE
CHANGES
CHANGES
Adjustment of cell data parameters

– Adjust the cell parameters according to the features of actual radio channel traffic
and signaling load. The parameters are for cell select, cell reselect, call setup,
handover etc, so as to improve the overall network performance and service quality
to the end user.
– Another basic principle of radio parameter adjustment is to maximize the current
network resource, traffic sharing in the whole network, increase the utilization of the
equipment, so as to increase the profit-investment ratio.
According to the feature of problem to be solved, there are two types of radio
parameter adjustment.
– Solve static problems: Analyze the average traffic and signaling flows of the
network and solve the network problems that existed long time
– Solve traffic overload and congestion problems during some special period caused
by special events.
Driving Test Tools 51
Drive test Tool application

Identify specific problems in the network
Attend to customer complaints
Perform network benchmarking with other operators
Collect periodic network data for reporting
Check coverage in new areas
52
RECOMMENDATIONION

Synchronised handover 53
• Non-synchronised Handover
• MS sends access bursts (HO_ACCESS) (with varying TA) until it receives
PHYSICAL_INFO
• Synchronised Handover
• MS sends a few access bursts (HO_ACCESS) and then starts transmission
with previous TA
• Non-synchronised handover leads to a longer communication interruption than

synchronised handover (200ms vs. 100ms)
• Synchronized HO should be activated between sectors of the same site. If
activated on inter-site adjacencies the handover can fail
Synchronized HO
Non- Synchronized HO
Site A
Site B
54
Examples of wrong parameter set with impact on network
operation/performance – call setup, qual, bands
1. No calls happening in a cell

– Cell Barred
– Non existent (LAC, Cell ID) in MSC
– DMAX = 0
2. Very low traffic in a cell

– msTxPwrMax = 0, bsTxPwrMax = 30
3. Bad quality in UL after rehoming

4. Few traffic in 1800 layer of a dual band 900/1800 network
Example 1a 55
No calls happening in a cell:

The cell has been barred
Handover

SY
Call Setup

(C S IN
ell FO
Ba
r 3
ye rAcc (BC
s) es CH
s= )
Example 1b 56

CI different between MSC and BSC or non existent (LAC, Cell ID) in MSC
MSC does not find

(LAC, CI) in its
database
Example 1c 57

MsMaxDistanceInCallSetup (DMAX) = 0
Despite the coverage

of the cell, no calls
will be established!
Call Setup
DMAX = 0

RxLevel = -70
dBm
Example 2 58
Parameter Value_______Default
• Very low traffic in a cell: value

msTxPwrMax = 0, bsTxPwrMax = 30 bsTxPwrMax 0 … 30 dB 0 dB
bsTxPwrMin 0 … 30 dB 30 dB
minMsTxPower 0 … 36 dBm 0 dB
msTxPwrMax 0 … 36 dBm
elta Attenuation Values (dB)

∆ D
BTS Max Power = BTS Power – (bsTxPwrMax = 0 dB)
BTS Min Power = BTS Power – (bsTxPwrMin = 30 dB)
lu te Power Values (dBm)

so
Ab
MS Max Power = (msTxPwrMax = 33 dB)
MS Min Power = (minMsTxPower = 13 dB)
Example 3 59
Bad quality in UL after rehoming:

DiversityUsed parameter not set to yes anymore
After rehoming
RDIV RDIV = Y
parameter
was set to
default value
(No) and UL
quality was
affected. Uplink Diversity
improves quality of
signal received.
Example 4 60
Few traffic in 1800 layer of a dual band 900/1800 network:

Idle Mode: C2 parameters not set properly (temporaryOffset,

penaltyTime)
BCCH
BCCH
slow moving mobile fast moving mobile
1800: micro-Layer 900: macro-layer

61
operation/performance – frequencies
1. Drop call rate increase after new frequency plan implementation

– Double BA List activated
2. Impossibility to unlock some BTS after a RF-frequency hopping implementation
3. Impossibility to unlock some BTS after a frequency retune

– NON-EDGE TRX, with GTRX = Y
– TRX, with GTRX = Y, not attached to any EDAP pool
4. No handover happening after frequency retune between 2 cells from different BSCs
– ADCE table has not been updated for other BSC
Example 1 62
• Drop call rate increase after new frequency plan implementation:

In the meantime, measurementBcchAllocation has been changed to idle and
MA list defined with old BCCH frequency band
OLD MA List
BCCH TCH OLD FREQUENCY PLAN
TCH BCCH TCH

NEW FREQUENCY PLAN
These BCCH frequencies will not be measured by old MA List
These TCH frequencies will be wrongly measured

Example 4 63
• No handover happening after frequency retune between 2 cells from different BSCs:
Frequency retune has been done with MML command. ADCE table has not been updated for
incoming adjacencies belonging to other BSCs
TRX
BSC id BTS id TRX id FREQ

fA
N-Neighbour
fAB ADCE
Cell A Cell B BSC id BTS id N-LAC N-Cell id N-BCCH
fA fAB
64
operation/performance – Handover
1. No handover from a cell towards all its neighbours

– PLMN permitted = No
2. High Handover failures after implementation of new adjacency plan

– SYNC = YES
3. No handover happening from an interfered cell

– hoMarginQual set to 0
4. 100% of handover failures in an adjacency relation

– Co-BSIC co-BCCH declaration
5. High number of handovers

– hoThresholdsLevUL = hoThresholdsLevDL
6. Handover not happening when DL signal level of neighbour much greater

than serving cell
– POC DL activated
Graphical Summary of Formulas
65
TCH Successful
SDCCH Successful Call
Assigned SDCCH Assigned
TCH Seizure
SDCCH
Attempts
Seizure
SDCCH TCH
Attempts
Blocked Blocked
SDCCH Dropped TCH Dropped
SDCCH TCH
SDCCH Traffic, TCH Traffic,

Availability, Availability,
Congestion, Congestion,
Access Access
probability probability or
Blocking
66
Random Access Success Rate

67
Random Access Success Rate

68
RACH REJECTIONS –ND 134

Description of the root causes for poor RASR 69
•Poor BCCH & BSIC Plan

Excess levels of interference (co and adjacent) on the BCCH carrier can cause
poor RASR
Change BCCH & BSIC Plan
•Poor Radio Network coverage
Poor signal strength coverage within a cell can cause poor RA success Rate
especially from across the rapid fading (received signal strength on UL) cell
boundaries.
work to improve coverage in hot spot areas (antenna tilts, azimuth, height,
transmit power setting revisions for both MS and BS, power control setting revision
for both MS and BS, use of TMA etc).
70
•Phantom Rach
When the traffic in a cell is low, there will not be many access burst coming to
the BTS. In such cases most of the received signal will be noise and if the receiver
at the BTS is sensitive, some of this received noise will be interpreted as an access
burst (cases where certain bit pattern in the noise matching the 8 bit checks
sequence). This is called as Phantom RACH .
introduce powerful filtering function in the signal processor by optimizing the
type of filtering that is used in the BTS or increase traffic.
•Wrong Value of RX level Access Min.(RXP)
Value for RXP is -110 can cause poor RASR.

Higher settings for RXP (-104) will ensure that the MS will camp on a cell if the
received signal strength on the downlink is good enough
71
BCSU Overloaded
when BCSU overload lower limit occurs, all calls except emergency, MOC
and MTC calls are refused
When the overload upper limit occurs, all calls are refused.
Decrease the no. of cells in BCSU.
Faulty Antenna / Cable

If the other root causes are not fitting the profile check for faulty antenna,
loose /damaged jumper/feeder cables, VSWR alarms etc
72
PAGING SUCCESS RATE

PAGING SUCCESS RATE 73
Factors affecting Paging success rate;-

Successful Paging response on SDCCH received by network cause
successful paging.PSR can affected by any of following reason:-
Poor RF: Interference on the BCCH / SDCCH carrier & or poor

coverage.
Check BCCH Plan
Poor Paging Strategy: Using Location Area based first page is
usually recommended to bring down the amount of paging needed (as
compared to global first page).
If “paging discard rate” at the BSC is too high use TMSI based paging
strategies. Also check for too short page response timers.
Recommended value of MFRS=4 and Re-paging interval=100ms
74
SDCCH Congestion Rate: High SDCCH congestion rate at cell level can
cause high page response failures and hence low paging success rate. In these
cases
Re-dimension the number of SDCCH.
Combined BCCH :Combined BCCH consists max. only 3-CCCH for paging.
Check if combined signaling is existing. If it is existing, it should be removed

Check if TRXSIG is big enough, default value for TRXSIG is 32k.If lots of SMS
traffic + HR is used 64k should be used.
Use combined BCCH (SDCCH/4) only in remote BSCs carrying very little
traffic
Incorrect LAC dimensioning:

Check if location areas are optimized
•Sizes
•Borders
Check PER (T3212),it not should be too large. Recommended 4hrs
75
SDCCH BLOCKING

76
SDCCH Blocking

77
BLOCKING—ND Report-182

SDCCH Blocking 78
SDCCH avalability-Unavailability of SDCCH cause SDCCH blocking

Check alarms (are TRXs & TSLs in Working State? ), check
availability report and RxQuality report to verify whether there is a
badly functioning TRX. Fix hardware problem.
Redimensioning of SDCCH capacity

Check actual SDCCH configuration ( e.g. Combined BCCH/SDCCH,
Number of SDCCH channels). If there is insuficient SDCCH capacity
and enough TCH capacity, add SDCCH TSL.
SDCCH Blocking 79
Add hardware or Software capacity

Other solution e.g. are to add TRX, activate Dynamic SDCCH,
activate FACCH Call Setup.
High SDCCH traffic due to Location updates

Bad location area setting
(Check MCC, MNC and LAC parameters)
Bad Location area geographical configuration. Too small LA
definition will cause many LA updates. Border of LA in a busy
avenue will cause many LUs in both location areas!
Change Location area boundary
Low value for CellReselectHysteresis
Change HYS parameter value
Low value of periodicTimerLU
Change value of PRAU timer(not too small)
SDCCH blocking 80
If none of the other root cause/s are responsible for sdcch

Blocking, then try to
Look into the A-ter status and also the site fluctuations or
neighbor site not taking call, escalate the same to OMC and O&M
team
Look into the coverage foot print and over shooting of the site
thro TA report , optimize.
Look into the A-bis signaling load if possible for a high

configuration site go for 64K PCM slot for LAP-D signaling thro OMC
Engineer.
Disable Direct retry in that cell and enable Traffic reason HO.
81
SDCCH DROP

82
SDCCH DROP

83
KPI- Rules, SDCCH Drop

SDCCH Drop 84
•Ghost SDCCH
Double-Access /Multiple reservations due to co-Bsic, co-BCCH.
Check and improve frequency plan.
RACH retransmissions/Multiple reservations due to bad coverage or
interference and high numberOfRachRetransmissions.
Lower RACH retransmission parameter value. Check and improve
frequency plan and/or downtilt.
•Radio Fails
Check alarms and RxQuality report to verify whether there is a badly
functioning TRX. Fix hardware problem. Check antenna line.
SDCCH Drop 85
•Radio Fails (cont.)

Coverage. Verify TA report and planning tool.
Interference. Check Frequency Plan. Solution e.g. add sites,
down tilt antennas, increase RxLevAccessMin.
Extended coverage of cells in location area borders. Check LU
parameters and/or downtilt
•100% ABIS Fails

Failure in BTS software (BCSU reset in BSC).
•100% AIF Fails

BTS connected to other BSC or BTS is not declared in MSC.
86
ND REPORT__SD DROP--166

87
TCH BLOCKING

TCH BLOCKING 88
One TDMA frame has 8 timeslots (one radio) and each timeslot
can act as TCH channel (traffic channel carrying the payload).
There are three types of TCHs:
Full rate channel, which is used for full rate speech at 13 kbps
or for data rate up to 14.4 kbps.
Half rate channel, which is used for half rate speech at 6.5 kbps
or for data rate up to 4.8 kbps.
AMR Channel
TCH call blocking (blck_8i) 89
sum of (TCH channel requests for a call –

successful TCH channel seizures for a call)
blck_8i = 100 x
sum of TCH channel requests for a call
sum(a. tch_requests_call_attempt – a.succ_tch_seiz_call_attempt)

blck_8i = 100 x
sum(a.tch_requests_call_attempt)
sum(c1192 – c1193)
blck_8i = 100 x
sum(c1192)
Counters from:
a = p_nbsc_traffic (001xxx)
TCH call blocking counters 90
Obs: These
counters can also
trigger in other
points not
detailed in this
diagram
91
TCH BLOCKING—182-ND REPORT

TCH blocking 92
•TCH availability
Check alarms (are TRXs & TSLs in Working State? ), check
availability report and RxQuality report to verify whether there
is a badly functioning TRX. Make Loop Tests on TRX. Fix
hardware problem.
•TCH capacity
Bad TCH capacity dimensioning. Check number of TRXs.
TCH blocking 93
•TCH traffic
Cell is covering a region greater than planned. Verify TA statistics. Change
DMAX, or downtilt.
High traffic in some cells. Solution .eg.:
Quality degradation
Add Macrocells no
Add Microcells no
Add TRXs with new freq no
Add TRXs without new freq no/yes (IUO, FH)
Activate Directed Retry no/yes
Activate Queuing yes
Activate HR yes
Activate AMR-HR no
Activate DADL/B no/yes
Activate AMH no/yes
Activate C2 parameter yes
Modify hoMarginPBGT yes
Decongestion and TCH blocking Issues 94
•Check the BBH KPI report and find out the cells having utilization more than 90% .
•Check the blocked TRX report 111 and if TRX blocked found, follow up with O&M team to
rectify the same as soon as possible.
•Look into the A-ter /TRAU status of the BSC in which the congested cell is integrated
•Look into the GPRS and SD configuration and their usages in the congested cell ,Try to
reduce the same and obtain more TS for TCH.
•Check the site location along with any site nearby to share the traffic and look into the TA
report 232 for the coverage foot print of the congested cell, if possible reduce the coverage foot
print and let the neighbour cell to share the traffic thro proper optimization
SUGGESTIONS 95
•Suggestion ,in multiple site areas first go for nearest low utilized sites optimization to
share the traffic from the congested cells and after doing the optimization introduce the
Traffic reason HO or Direct Retry between the neighbours .
•Change FRL & FRU parameters to overcome blocking issue.
•If SD block is there in cells never go for Direct Retry between the neighbours better go
for Traffic reason HO with the neighbouring cells of the congested cell.
•For single site areas if there is spectrum issue we should look for the customized MA list
by adding some BCCH carriers carefully looking into BCCH reuse pattern in
neighbouring cells and their presence close to the site
•If we are unable to add TRX due to Spectrum limitation propose for a new capacity site
to share the traffic .
96
TCH ASSIGNMENT SUCCESS RATE

97
TCH ASSIGNMENT SUCCESS RATE

ASSIGNMENT FAILURES 98
•Look into the BSS BBH KPI reports for High Assignment failure cells
•Mostly due to HW issues like : TRX faulty, TS issues , Wrong Combiner ,Antenna
connections, Wrong Air combing antenna positions , TRX cable loose, VSWR issues
,Wrong PCM mapping ,TRAU issue, Site Fluctuations, A-bis link BER .
•Escalate to O&M and OMC team to rectify the same and follow up till got rectified
•RF issues : High Coverage foot print of the site , High Dense clutter ,Wrong Antenna
positioning . Needs optimization and site visit
•IMPACT ; High assignment failures in cells contributes to Call drop , HOSR failures,
SD drops in dynamic SD , Low call volume etc etc .
99
DROP CALL RATE

TCH drop call ratio - formulas 100
Dcr_3j
TCH DROPS AFTER SEIZURE

TCH_RADIO_FAIL /c1013
+TCH_RF_OLD_HO /c1014
+TCH_ABIS_FAIL_CALL /c1084 Dcr_8h
+TCH_ABIS_FAIL_OLD /c1085
+TCH_A_IF_FAIL_CALL /c1087 Dcr_5a
+TCH_A_IF_FAIL_OLD /c1088
+TCH_TR_FAIL /c1029
+TCH_TR_FAIL_OLD /c1030 TCH DROPS AFTER ASSIGNMENT
+TCH_LAPD_FAIL /c1046 tch_new_call_assign /c57033 CONVERSATION DROPS
+TCH_BTS_FAIL /c1047 +tch_ho_assign /c57034 dropped_calls /c57007
+TCH_USER_ACT /c1048
+TCH_BCSU_RESET /c1049 -tch_norm_release /c57035
+TCH_NETW_ACT /c1050 -tch_ho_release /c57036
+TCH_ACT_FAIL_CALL /c1081
-tch_re_est_assign /c57032
-tch_re_est_assign /c57032 (S7)
DROPS
100 * %
CALLS
TCH SEIZURES FOR NEW CALL TCH ASSIGNMENTS FOR NEW CALL
tch_norm_seiz /c1009 tch_new_call_assign /c57033
+tch_seiz_due_sdcch_con /c1099 (S5)
+msc_i_sdcch_tch /c4044 STARTED CONVERSATIONS
+bsc_i_sdcch_tch /c4057 -tch_re_est_assign /c57032 conver_started /c57015
+cell_sdcch_tch /c4074 - msc_i_tch_tch /c4043
-tch_succ_seiz_for_dir_acc /c1165 (S7)
TCH RELEASE
-tch_re_est_assign /c57032 (S7) CONVERSATION STARTED Disconnect from MS
conn_ack to BTS
TCH SEIZED
BSC allocates a TCH as a response to TCH ASSIGNED
TCH request (Channel Activation) Assignment_complete from BTS
RF CHN RELEASE
Rf_channel_release_ack
from BTS
TCH drop call ratio (dcr_32a)
101
sum of TCH failures

dcr_32a = 100 x
sum of new calls
sum(tch_radio_fail+tch_rf_old_ho+(tch_abis_fail_call
- facch call setup fail paging)+tch_abis_fail_old
+ tch_a_if_fail_call+tch_a_if_fail_old+ tch_tr_fail
+tch_tr_fail_old+tch_lapd_fail+tch_bts_fail
+ tch_user_act+tch_bcsu_reset+tch_netw_act+tch_act_fail_call)
- sum(b.tch_re_est_assign); call re-establishments
dcr_32a = 100 x
sum(a.tch_norm_seiz)
+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch
+ c.cell_sdcch_tch); DR calls
- sum(a.tch_succ_seiz_for_dir_acc) ; ref. 1
+ sum(a.tch_seiz_due_sdcch_con); FACCH call setup calls
- sum(b.tch_re_est_assign); call re-establishments
Ref.1. Compensation needed since in case of Direct Access to super reuse TRX the
tch_norm_seiz is triggered in parallel with cell_sdcch_tch.
TCH drop call ratio (dcr_32a) - reasons 102
tch_abis_fail_new tch_radio_fail_new
tch_radio_fail_old tch_radio_fail
tch_abis_fail_call
tch_a_if_fail_new
tch_abis_fail_old
tch_a_if_fail_call tch_a_if_fail_old
tch_abis_fail
tch_a_if_fail BSC
TC
BTS
tch_tr_fail tch_bcsu_reset tch_bts_fail

tch_tr_fail_old tch_user_act tch_lapd_fail
tch_netw_act
tch_act_fail_call
tch_tr_fail_new
TCH drop call ratio (dcr_32a) 103
Obs1: These
counters can
also trigger in
other points
not detailed in
this diagram
Obs2: Other
counters that
compose this
formula are
not detailed in
the diagram
TCH drop call ratio, after TCH assignment (dcr_5a) 104
number of failures during a call in progress after the

CONNECT_ACK message on TCH
dcr_5a = 100 x
number of the conversation phases started (CONNECT_ACK) -
number of successful incoming TCH-TCH HOs (MSC controlled)
sum(b.dropped_calls)
dcr_5a = 100 x
sum(b.conver_started) – sum (a.msc_i_tch_tch)
sum(c57007)
dcr_5a = 100 x
sum(c57015-c4043)
Counters from:
a = p_nbsc_service (057xxx)
b = p_nbsc_ho (004xxx)
105
TCH DROP-ND REPORT—(163)

106
UL AND DL QUALITY, UL INTERFERENCE PER TRX,ND-196

107
KPI- Rules, TCH Drop

TCH Drop and Corrective action 108
Non RF drops :
•Check the TCH drop reason in BBH stats report.
•Non RF drops may have two reasons one is TR drop and other A-bis fail . If you
find such issues in a site/cell then escalate to O&M team and do continuous follow
up till the same got corrected.
Hint : If all cells or a single cell in a site is having TR drops then check the PCM
mapping and the link stability . If most of the cells /sites in a BSC is having TR
drops High then escalate the same to OMC to check TRAU block . For A-bis drop,
it is the link or the E1/T1 card which may have issues or any issue in the internal
wiring of the BTS .
RF Drops :
• If RF drop is high in cells first step is to check the Air interface clearance (BCCH reuse pattern
and C/I, and the database for Hopping.
• Over shooting sites, neighbor missing and neighbor definitions , call dragging due to congestion
in neighbor cells, border cells.
Optimize your neighbor sited and Adjancy definition.
•VSWR issues or TRX wrong connections. See the path balance reports (208) to find out the
VSWR issues. Escalate issue to BSS team.
• Minimize the Hand Over attempts between cells by minimizing the overlapping of source and
target cells and also setting the margins and Ping pong rejection timers .
•check the Hopping pool MA List and MAIO and try to have best offset to avoid co.and adj.
interference. Check Fractional Frequency loading in the cell ,restrict over shooting cells( This can
be checked thro the report (196) which will give you a clear indication of bad samples and
confirms if all TRXs are having bad samples during BBH )
• Another reason for RF drop may be due to HW faults in BTS ,like TRX having poor
quality TS , wrong antenna connections ,VSWR Issues in sites
• Corrective action : Check the assignment success rates in those cells where drop rate
is high this will give you hint about the wrong connections of the devices ,Antennas .
Look into the TRX Quality reports (196) where you can look into the poor quality
samples per TRX if some TRX is having high poor UL/DL quality samples and others
in the same cells are having good samples then the particular TRX is having some issue
,replace the same thro O&M team
• Ensure the RLT and ARLT (in AMR environment ) is properly set .(Bharti
guidelines we can set RLT 24 Frames and ARLT 38 Frames )
• If all above you are finding ok still there is high RF drops then have a drive test and
site audit to find out any external interference or Antenna issues in field ,check the
VSWR thro O&M team .
• Following the procedures defined above and taking corrective action in time will
result into a Quality network with Drop KPI maintained .
Handover 111
Handover
The inputs that the BSC uses for making a handover decision, from the received
MRs from the MS is the DL signal strength, DL quality, and the signal strength of
the six best reported neighbours. From the serving BTS, for the same MS the BSC
will use UL signal strength, UL quality and TA
Total Ho failure ratio (hfr_2a) 112
(ho attempts – successful ho)

hfr_2a =100 x
ho attempts
sum(a.msc_o_succ_ho + a.bsc_o_succ_ho + a.cell_succ_ho)

hfr_2a =100 x
sum(b.msc_o_ho_cmd + b.bsc_o_ho_cmd_assgn + b.bts_ho_assgn)
sum(c4004 + c4014 + c4018)

hfr_2a =100 x
sum(c1195 + c1196 + c1197)
Counters from table(s):

p_nbsc_ho (04xxx)
p_nbsc_traffic (01xxx)
Excluding ISHO
113
HO FAILURE REPORT—ND (153)

114
HANDOVER ANALYSIS
Presentation / Author /
Date

115
HO CAUSES –BSC WISE

116
HO CAUSES—CELL WISE--154

ADJACENCY DISCREPANCIES-ND-60 117
This report lists the discrepancies of various parameters between the source
cell adjacency parameters and target cell parameters
BCCH
DISCREPANCIES
IN NBR LIST
NON-SYMMETRICAL ADJACENCIES,ND-61 118
This report shows all missing adjacencies assuming that all adjacencies
should be symmetrical (bidirectional).
DEFINED FROM
27661 TO 1712 BUT
NOT VICE-VERSA
HANDOVER SYNCHRONISATION,ND-67 119
This report lists all adjacencies

- that are in the same BS site but are not synchronous

. This is serious and may result in call failures and decrease
. voice quality
- that are not in the same BS site but are synchronous
. This is serious and can result in call failures
A synchronous HO means that the MS uses the old value of timing advance.
A non-synchronous HO means that the MS finds the new value of timing advance.
Normally only adjacent cells in the same site are synchronous for HO.
TO BE YES
TO BE NO
POOR HOSR 120
•Look into the 153 report for HOSR between source and target cells
•List all the neighbours where there is poor HOSR

•See the sites are performing well and there is no assignment failure issues and TRX HW issues
•Look into the BCCH and BSIC reuse pattern of the neighbours to ensure good C/I of the BCCH carrier and
their definition in neighbour.
•Do the neighbour audit and check all the neighbours defined with proper database and LAC etc etc
(Chedk60,61,67etc.)
•Define Sync neighbours between cells in a single site
•Check the Signaling load on A-bis and A-ter
•Thro Neighbour audit remove all neighbours which are not with level to retain the call and add all missing
neighbours.
•Check the HO parameters and margins ,rescue hand over settings ,penalty timers from ZEAO and ZEHO logs
to ensure less attempts and enhnace the success rate
•
•Check the whether Clock shift !DAC ( 1800-2400 )
•Check Software miss match( BSC and BTS end)
POOR HOSR 121
•Optimize the Overlap areas between cells to have minimum HO requests in each call .
•Decongest the target cells to ensure TCH resource availability for a HO request .
•Try to introduce more Ho margin between cells inter BSC to have less attempts for Inter BSC
HO .
•Allow RX Lev HO between single sites and minimum overlapping neighbours , with a very less
HO Margin and penalty timer
•In an AMR scenario to minimize the quality HO ensure the Threshold level for Quality HO is
set RX qual 5 or 6 .
•Poor HOSR Impact: Enhances TCH drop, TCH Block due to poor mobility management
between sites.
•Concentrating on reports and following the procedures defined above and taking corrective
action in time will result into a Quality network with all KPIs maintained
122
TIMERS

123
TIMERS

T10 Supervision of the assignment procedure 124
•Interpretation: The timer T10 supervises the assignment procedure.

•Timer start condition: The timer T10 starts before the BSC sends a
PHYSICAL_CONTEXT_REQUEST message to the BTS.

•Timer stop condition: The timer T10 stops when the MS sends either an
ASSIGNMENT_COMPLETE or an ASSIGNMENT_FAILURE message to the BSC.
•Action performed on timer expiry: When the timer T10 expires, the BSC sends an
ASSIGNMENT_FAILURE message to the MSC.
•Appropriate value:
1.Min. = 4 s.Max. = 14 s.Def. = 8 s.Rule = T10 > T3103, T10 > T3107
NOTE: It is recommended that T10 be at least 2 seconds longer than T3107.
Figure: T10 timer activation

T3101 Supervision of the immediate assignment procedure
125
•Interpretation: The timer T3101 supervises the immediate assignment procedure.

•Timer start condition: The timer T3101 starts when the BSC sends an
IMMEDIATE_ASSIGNMENT_CMD message to the BTS.
•Timer stop condition: The timer T3101 stops when an ESTABLISH_IND message
is received from the MS.
•Action performed on timer expiry: When the timer T3101 expires, the BSC sends
an RF_CHANNEL_REL message to the BTS.
•Min. = 1 s.Max. = 5 s.Def. = 3 s.Rule = -
Signalling diagram:
Figure: T3101 timer expiry

T3103 Supervision of the internal handover procedure 126
•Interpretation: The timer T3103 supervises the internal handover procedure.

•Timer start condition: The timer T3103 starts when the BSC sends a
HANDOVER_CMD message is sent to the MS (via a BTS).

•Timer stop condition: The timer T3103 stops when the BSC receives either a
HANDOVER_CMPL message on the new channel or HANDOVER_FAILURE
message on the old channel from the MS.
•Action performed on timer expiry: When the timer T3103 expires, a
CLEAR_REQ message is sent to the MSC and the new channel is released.
•Min. = 3,5 s.Max. = 10 s.Def. = 6 s.Rule = T3103 < T10
•Signalling diagram:
Figure: Successful handover with T3103 timer activation

127
Figure: Unsuccessful handover

T3107 Supervision of the assignment procedure 128
•Interpretation: The timer T3107 supervises the assignment procedure

and the internal intracell handover.
•Timer start condition: The timer T3107 starts when the BSC sends
an ASSIGNMENT_CMD message to the MS (via a BTS).

•Timer stop condition: The timer T3107 stops when the BSC receives
either an ASSIGNMENT_CMPL or ASSIGNMENT_FAILURE message
from the MS.
•Action performed on timer expiry: When the timer T3107 expires,
the new and the old channel are released, all the appropriate MS
connections are cleared, and an ASSIGNMENT_FAILURE message is
sent to the MSC. In the case of the internal intracell handover, a
CLEAR_REQUEST message is sent to the MSC.
1.Min. = 3.5 s.Max. = 10 s.Def. = 6 s.Rule = T3107 < T10
NOTE: It is recommended that T10 be at least 2 seconds longer than
T3107.
Signalling diagram:
Figure: Successful
assignment with T3107
timer activation
129
Figure: Unsuccessful assignment

T3109 Supervision of the channel release procedure 130
•Interpretation: The timer T3109 supervises the channel release procedure.
•Timer start condition: The timer T3109 starts when the BSC sends a
CHANNEL_REL message to the MS (via a BTS).
•Timer stop condition: The timer T3109 stops when the BTS sends a
RELEASE_INDICATION message. This is done after the BTS has received a
DISC-frame from the MS.
•Action performed on timer expiry: When the timer T3109 expires, the BSC
sends an RF_CHANNEL_REL message to the BTS.
•Min. = 8 s.Max. = 15 s.Def. = 12 s.
•Signalling diagram:

131

2.GSM Network Optimization

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2.GSM Network Optimization

Uploaded by

Copyright:

Available Formats

GSM NETWORK OPTIMIZATION 1

PDF Created with deskPDF PDF Writer - Trial :: http://www.docudesk.com

MobileComm Technologies India Pvt. Ltd.

GSM NETWORK OPTIMIZATION

PDF Created with deskPDF PDF Writer - Trial :: http://www.docudesk.com

Copyright 2010 MobileComm Technologies India Pvt. Ltd.

MobileComm is committed to providing our customers with quality instructor led

MobileComm Technologies(India)Pvt. Ltd.

Give an overview about the Call Signalling

MS Channel request (RACH) NETWORK

Service request (SDCCH)

Authentication response (SDCCH) Authentication

Ciphering mode command (SDCCH)

Ciphering mode complete (SDCCH) Ciphering mode setting

Assignment command (SDCCH)

MS Page request (PCH) NETWORK

Authentication response (SDCCH) Authentication

Ciphering mode command (SDCCH)

Assignment command (SDCCH)

Basic Call provides speech or data services to the

Overview of Basic Call

mobile terminating call with a given MS.

Figure: Paging procedure when paging comes from MSC

•Limited to geographical sub-group of BSCs using LACs

Figure: Channel needed information element

Figure: Values of Channel Field bits

The PAGING COMMAND message from BSC to BTS

In combined Mode :- BCCH + CCCH in a 51-frame multiframe- (9 CCCH block)

Paging Gp= ((IMSI mod 1000) mod (BS_CC_CHANSx N)) mod N

For More information on Paging Groups see GSM Specification 05.02.

noOfMultiframesBetweenPaging 2..9 multi frames Defines how often

Repaging Interval 50..100 ms Time between

Repaging Attempts 0..5 Number of paging

BTS stores up to 8 paging messages of the MSC in page group buffer

Figure: Channel required procedure

Figure: CHANNEL REQUEST message, only one octet long

marked with xs):

Figure: NECI parameter is set to OFF

Figure: NECI parameter is set to ON

PDF Created with deskPDF PDF Writer - Trial :: http://www.docudesk.com

After receiving the proper CHANNEL REQUIRED message from the

maxNumberRetransmission 1,2,4,7 Defines maximum allowed number of

S depends on numberOfSlotsSpreadTrans signalling channel mapping (CCCH + SDCCH combined or not

After receiving the CHANNEL REQUIRED message from the BTS

•After a successful reservation of a new SDCCH channel, the BSC activates

Downlink CCCH blocks

PCH can be used for AGCH messages

Reservation of CCCH blocks for AGCH

noOfBlocksForAccessGrant 0..7 possible number, if CCCH and SDCCH are not

Preference of AGCH messages on PCH

noOfBlocksForAccessGrant ≠0 PCH can be used only, if no paging messages

T9105 start T9105 End

Ciphering is one of the security procedures designed to protect the

The selection of the

•The BSS responds by sending the MSC the ASSIGNMENT COMPLETE,ASSIGNMENT

The channel release

Figure 16. Channel release procedure by MSC

Fig. Channel release started by the BSC

PDF Created with deskPDF PDF Writer - Trial :: http://www.docudesk.com

GSM Causes and DX Causes

PDF Created with deskPDF PDF Writer - Trial :: http://www.docudesk.com

MSC BSC BTS

Counter = XXXYYY where

Example: counter 001000 or c1000