Professional Documents
Culture Documents
GSM KPI Optimization
GSM KPI Optimization
3. Release Indication
When the BTS received a layer 2 DISC frame from the mobile it replies with a Layer 2
UA frame to the mobile station and a Release Indication to the BSC. The system does
only react on Release Indication if it is received during a normal disconnection
situation. If such a message is received unexpectedly this will usually cause radio link
time-out or timer T200 expiration as the mobile station stops the transmitting of
measurement reports. It is also possible that the release will be normal depending on
when the Release Indication is received.
4. MSC Time-Out
Normal Release:
If the MSC never received a response on a message (e.g. Identity Request) and there is
no radio link time-out or layer 2 time-out, the MSC will send a Clear Command to the
BSC. The time-out is depending on the message. When receiving Clear Command, the
BSC will send a Channel Release (cause: normal release) and then deactivates the
SACCH.
Reject (only SDCCH):
If the MSC never receives a response on the first message after Establish Indication,
the MSC will send a reject message. If the connection was a Location Update it will be
a Location Update Reject (cause: network failure) and if the connection was a mobile
originating call (CM Service Request) a CM Service Reject (cause: network failure) will
be sent. The MSC will then send a Clear Command to the BSC and the call is cleared by
Channel Release (cause: normal release).
5. Assignment to TCH
Before sending an Assignment Command from the BSC at TCH assignment, the
following two criterions have to be fulfilled:
When a subscriber runs out of battery during a conversation, the call will be registered
as dropped call due to low signal strength or others.
Action: Check if MS power regulation is used. Check if DTX uplink is used.
Congestion on TCH
The SDCCH is dropped when congestion on TCH.
Action: Check TCH congestion
Solution: Increase capacity on TCH or using features like Assignment to another cell,
Cell Load Sharing, HCS, Dynamic Half-Rate Allocation and FR-HR Mode Adaptation etc
frequencies mean few samples per frequency and problem for mobiles to decode the
BSIC. Action: Check number of definitions.
---Delayed Handover Decision
A delayed handover decision can be due to congestion in the target cell.
Action: Check handover parameters.
---Wrong Locating Parameter Setting
Action: Check locating parameters.
---Bad Radio Coverage
Action: Check coverage plots.
---High Interference, Co-Channel or Adjacent
The potential handover candidate is disturbed by interference. Outgoing handover due
to bad uplink quality may indicate interference from co-channel another MS. On the
border, the quality may be rather bad and the signal strength low. Bad downlink
quality may indicate interference from another co-channel base station.
Action: Check interference. Check if many handovers are performed due to downlink
or uplink bad quality.
---Receiver Antenna Problem or RBS HW problems (in candidate cell)
Action: Check antenna installation. Check RBS HW and Error log of the target cell
---Poor Inter-MSC/BSC Handover Performance
For outer or external cell, wrong definitions in either MSC or BSC may be reason for
the problem.
Action: Check inter-MSC/BSC handover performance.
---Incorrect Down Tilt
Action: Perform site survey and check antenna installation.
Solution: Correct antenna tilting.
---Low Availability
Action: Check SDCCH Availability. Check if the channels are manual, control or
automatic blocked.
---Increasing Traffic Demand
The high traffic could be related to an occasional event or due to a long term growth.
Action: Check if short term traffic growth. Make trend comparisons. Check if
combined SDCCH is used. Check SDCCH dimensioning.
---Bad use of Adaptive configuration of Logical Channels
By using the Adaptive configuration of logical channels feature, the basic SDCCH
configuration in a cell will be under-dimensioned. If this feature is not used correctly,
it will cause SDCCH congestion.
Action: Check if ACSTATE is on. Check parameters related to Adaptive configuration of
logical channels
---Long Mean Holding Time
If the mean holding time is long, this generates a higher traffic load.
Action: Check SDCCH Mean Holding Time
---Too Frequent Periodic Registration
Action: Check Random Access Distribution. Check the timer T3212 in the BSC and the
parameters
---BTDM and GTDM in the MSC
1. The PSTN subscriber dials the MSs telephone number (MSISDN), the MSISDN is
analyzed in the PSTN, which identifies that this is a call to a mobile network
subscriber. A connection is established to the MSs home GMSC. The PSTN sends
an Initial Address message (IAM) to the GMSC.
2. The GMSC analyzes the MSISDN to find out which HLR, the MS is registered in,
and queries the HLR for information about how to route the call to the serving
MSC/VLR. The HLR looks up the MSISDN and determines the IMSI and
the SS7 address for the MSC/VLR that is servicing the MS. The HLR also checks if
theservice, call forwarding to C-number is activated, if so, the call is
rerouted by the GMSC to that number.
3. The HLR then contacts the servicing MSC/VLR and asks it to assign a MSRN to
the call. [MSRN - Mobile Station Routing Number].The MSC/VLR returns an
MSRN via HLR to the GMSC.
4. The GMSC sends an Initial Addressing message (IAM) to the servicing MSC/VLR
and uses the MSRN to route the call to the MSC/VLR. Once the servicing
MSC/VLR receives the call, the MSRN can be released and may be made
available for reassignment.
5. The MSC/VLR then orders all of its BSCs and BTSs to page the MS. Since the
MSC/VLR does not know exactly which BSC and BTS the MS is monitoring, the
page will be sent out across the entireLocation Area(LA).
6. When the MS detects the paging message to the BTSs in the desired LA. The
BTSs transmit the message over the air interface using PCH. To page the MS,
the network uses an IMSI or TMSI valid only in the current MSC/VLR service
area.
7. When the MS detects the paging message, it sends a request on RACH for a
SDCCH.
8. The BSC provides a SDCCH, using AGCH.
9. SDCCH is used for the call set-up procedures. Over SDCCH all signaling
preceding a call takes place. This includes: Marking the MS as active in the
VLR. Authentication procedure (Start ciphering, Equipment identification).
10. The MSC/VLR instructs the BSC/TRC to allocate an idle TCH. The BTS and MS
are told to tune to the TCH. The mobile phone rings. If the subscriber answers,
the connection is established.
GSM identities
The GSM network is complex and consists of the Switching System (SS) and the Base
Station System (BSS). The switching system, which consists of HLR, MSC, VLR, AUC and
EIR, interfaces both the Base Station System and also other networks like PSTN/ISDN,
data networks or other PLMNs.
In order to switch a call to a mobile subscriber, the right entities need to be involved.
It is therefore important to address them correctly. The numbers used to identify the
identities in a GSM/PLMN network is described in this chapter. See also Figure 56.
Numbering plans are used to identify different networks. For a telephone number in
the PSTN/ISDN network, numbering plans E.164 is used.
Mobile Station ISDN Number (MSISDN)
The MSISDN is a number which uniquely identifies a mobile telephone subscription in
the public switched telephone network numbering plan. According to the CCITT
recommendations, the mobile telephone number or catalogue number to be dialled is
composed in the following way:
MSISDN = CC + NDC + SN
CC = Country Code
NDC = National Destination Code
SN = Subscriber Number
A National Destination Code is allocated to each GSM PLMN. In some countries, more
than one NDC may be required for each GSM PLMN. The international MSISDN number
may be of variable length. The maximum length shall be 15 digits, prefixes not
included.
Each subscription is connected to one Home Location Register (HLR).
The length of the MSISDN depends on the structure and numbering plan of each
operator, as an application of CCITT recommendation E.164.
The following is an example of dialling a GSM subscriber.
The Mobile Station Roaming Number (MSRN), according to the GSM recommendations,
consists of three parts:
MSRN = CC + NDC + SN
CC = Country Code
NDC = National Destination Code
SN = Subscriber Number
Note: In this case, SN is the address to the serving MSC.
after
dialing
number
&
pressing
SEND
key,
sends Channel
Drive Testing
Layer 1 Messages
Other Layer 1 criteria that is useful for field measurements include:
C1 criteria
ARFCN of Serving Cell - (TCH in dedicated mode, BCCH in idle mode))
Time Slot (TS)
Layer 3 Messages
All Layer 3 messages should be collected where possible. Layer 3 Messages are used by
Analysts to determine more accurately the cause of a problem within the network.
Some field test equipment can perform basic analysis of particular Layer 3 messages
during data collection. This enables certain conditions such as call classification or
handovers to be flagged to the survey technician.
Call Classification
In principle there are five call classifications, some of which can be sub-divided
further.
Good Calls: These are calls that are successfully placed on the network and
maintained
for the required duration.
Dropped Calls: These are calls that are successfully placed on to the network but are
terminated without authorisation. Using Layer 3 Messages, these calls can be subdivided
into:
End User Hang-up
System Hang-up
Other
Blocked Calls: These are calls that cannot be placed on to the network. Again, using
Layer 3 messages, these can be sub-divided as follows:
System Busy
End User Engaged
No Service
Other
Roamed Calls: These are calls that are successfully placed on another network.
Roamed
calls may also be good calls or dropped calls.
Noisy Calls: These are calls which have been successfully completed for the duration
of
the call but which experienced a number of noise bursts that a subscriber may find
intolerable. The threshold for determining the level of poor audio is programmed
during
the set-up of the test.
In GSM, this particular classification is very difficult to determine with great accuracy.
It
should be noted that it is not enough to monitor just the RxLEV and the RxQUAL.
Troubleshooting
No Data Collected
Occasionally, the equipment fails to trigger the collection device to save the data to
file.
Check all cables
Ensure the Processing Unit is powered
Re-start the laptop computer
Re-start the equipment
Re-drive the test.
No Positional Information Collected
If data is collected using GPS only, it may be possible that satellite reception was lost
during a drive through a tunnel etc. It is important that back-up equipment is used,
such as
a Dead-Reckoning device, since a GPS receiver will re-transmit the last known position
until it receives an update. If the vehicle moves without GPS cover, the data will be
inaccurate and cannot be analysed.
Check the GPS antenna cable to the receiver
Drive to an open area and ensure that the GPS system is working correctly
If required, install a back-up positional device to safeguard against lost GPS
Coverage Holes
If there are patches of poor coverage in unexpected areas, it may indicate the fringes
of a
coverage hole. It is important to re-drive this particular area.
Complete a route plan using secondary roads as far as possible
Make notes of any buildings / obstructions that may cause shadowing
Take note of pedestrian / vehicular habits in the area
Dropped Calls
Dropped calls can be caused by either RF environments or incorrect system
parameters.
The following data should be checked to ensure that it has been collected properly.
Layer 3 Messages
Neighbour Cell List (BA Table)
RxLEV (Server & Neighbour)
RxQUAL (Server & Neighbour)
Finally, ensure that the automatic setting for the call length is not shorter than that
for the
timer monitoring for unauthorised call drop-outs. The setting should be a minimum of
30 seconds.
Handover Problems
Handover problems are generally caused by inaccurate settings of the handover
boundary.
This can cause ping-ponging, where the server will keep changing, and congestion at
the
IMMEDIATE ASSIGNMENT EXTENDED message. At its expiry, the packet access procedure
is aborted. The minimum value of this timer is equal to the time taken by T+2S slots of
the mobile station's RACH. S and T are defined in section 3.3.1.2. The maximum value
of this timer is 5 seconds.
T3164:This timer is used during packet access using CCCH. It is started at the receipt
of an IMMEDIATE ASSIGNMENT message. It is stopped at the transmission of a RLC/MAC
block on the assigned temporary block flow, see GSM 04.60. At expire, the mobile
station returns to the packet idle mode. The value of the timer is 5 seconds.
T3190:The timer is used during packet downlink assignment on CCCH. It is started at
the receipt of an IMMEDIATE ASSIGNMENT message or of an PDCH ASSIGNMENT
COMMAND message when in dedicated mode.It is stopped at the receipt of a RLC/MAC
block on the assigned temporary block flow, see GSM 04.60. At expiry, the mobile
station returns to the packet idle mode. The value of the timer is 5 seconds.
Timers on the network side
T3101:This timer is started when a channel is allocated with an IMMEDIATE
ASSIGNMENT message. It is stopped when the MS has correctly seized the channels. Its
value is network dependent. NOTE: It could be higher than the maximum time for a L2
establishment attempt.
T3103:This timer is started by the sending of a HANDOVER message and is normally
stopped when the MS has correctly seized the new channel. Its purpose is to keep the
old channels sufficiently long for the MS to be able to return to the old channels, and
to release the channels if the MS is lost. Its value is network dependent. NOTE: It
could be higher than the maximum transmission time of the HANDOVER COMMAND,
plus the value of T3124, plus the maximum duration of an attempt to establish a data
link in multiframe mode.)
T3105:This timer is used for the repetition of the PHYSICAL INFORMATION message
during the hand-over procedure. Its value is network dependent. NOTE: This timer may
be set to such a low value that the message is in fact continuously transmitted.
T3107:This timer is started by the sending of an ASSIGNMENT COMMAND message and
is normally stopped when the MS has correctly seized the new channels. Its purpose is
to keep the old channel sufficiently long for the MS to be able to return to the old
channels, and to release the channels if the MS is lost. Its value is network dependent.
NOTE: It could be higher than the maximum transmission time of the ASSIGNMENT
COMMAND message plus twice the maximum duration of an attempt to establish a data
link multiframe mode.
T3109:This timer is started when a lower layer failure is detected by the network,
when it is not engaged in a RF procedure. It is also used in the channel release
procedure. Its purpose is to release the channels in case of loss of communication. Its
value is network dependent. NOTE: Its value should be large enough to ensure that the
MS detects a radio link failure.
T3111:This timer is used to delay the channel deactivation after disconnection of the
main signalling link. Its purpose is to let some time for possible repetition of the
disconnection. Its value is equal to the value of T3110.
T3113:This timer is started when the network has sent a PAGING REQUEST message
and is stopped when the network has received the PAGING RESPONSE message. Its
value is network dependent. NOTE: The value could allow for repetitions of the
Channel Request message and the requirements associated with T3101.
T3115:This timer is used for the repetition of the VGCS UPLINK GRANT message during
the uplink access procedure. Its value is network dependent. NOTE: This timer may be
set to such a low value that the message is in fact continuously transmitted.
T3117:This timer is started by the sending of a PDCH ASSIGNMENT COMMAND message
and is normally stopped when the MS has correctly accessed the target TBF. Its purpose
is to keep the old channel sufficiently long for the MS to be able to return to the old
channels, and to release the channels if the MS is lost. Its value is network dependent.
NOTE: It could be higher than the maximum transmission time of the PDCH
ASSIGNMENT COMMAND message plus T3132 plus the maximum duration of an attempt
to establish a data link in multiframe mode.
T3119:This timer is started by the sending of a RR-CELL CHANGE ORDER message and
is normally stopped when the MS has correctly accessed the new cell. Its purpose is to
keep the old channels sufficiently long for the MS to be able to return to the old
channels, and to release the channels if the MS is lost. Its value is network
dependent.NOTE: It could be higher than the maximum transmission time of the
RR_CELL CHANGE ORDER, plus T3134, plus the maximum duration of an attempt to
establish a data link in multiframe mode.
T3141:This timer is started when a temporary block flow is allocated with an
IMMEDIATE ASSIGNMENT message during a packet access procedure. It is stopped when
the mobile station has correctly seized the temporary block flow. Its value is network
dependent.
KPI Introduction
1. CSSR (CALL SETUP SUCCESS RATE)
Definition: Rate of calls going until TCH successful assignment
2. SCR (SUCCESSFULL CALL RATE)
Definition: Rate of calls going until normal release that is not interrupted by SDCCH DROP,
neither by assignment failures, and neither by CALL DROP.
3. CALL DROP RATE (CDR)
Definition: Rate of all losses of TCH connections during a call in relation to the number of
successful Call Setups
4. HOSR (HAND OVER SUCCESS RATE)
Definition: Successful internal and external outgoing handovers of total number of internal and
external outgoing handover attempts
5. PSR (PAGING SUCCESS RATE)
Definition: Rate of successful paging attempts of total number of paging attempts.The formula
is based on NSS point of view (based on MSC or LAC)
6. LOCATION UPDATE SUCCESS RATE
Definition: Successful location update
attempts of total number of location update attempts. The formula is based on NSS point of
view.
7. SDCCH BLOCK RATE
Definition: SDCCH congestion of total number of SDCCH seizure attempts
8. SDCCH DROP RATE
Definition: Dropped SDCCH connections of total number of SDCCH connections without TCH
congestion.
9. TCH ASSIGNMENT BLOCK RATE
Definition: Rate of TCH unsuccessful seizures during assignment procedure due to congestion
10. TCH Assignment Failure Rate (exclude blocking)
Definition: Rate of RTCH seizure failed (system + radio) during normal assignment procedure
over the total amount of RTCH request for normal assignment procedure
11. EMD (Erlang Minute per Drop)
Definition: Total of Erlang minutes (TCH occupation) in one period measurement per drop call
(after TCH Assignment).
12. TCH Availability
Definition: Available TCH of total number of defined TCH
13. RACH Success Rate
Definition : Rate of Successful RACH over the total number of channel required message
received