BSS Performance

Troubleshooting Instructions
GPRS Attach
Version 0.1

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

DOCUMENT DESCRIPTION
Title and version
Reference
Target Group
Technology and
SW release
Related Service
Items
Service Item
number
Author
Date
Approver

Performance troubleshooting instructions - BSS

NPO engineers (working in NOA projects)
2G, 2.5G
Radio network optimization / Capacity Extension Management

Karri Sunila
Eric Kroon

CHANGE RECORD
This section provides a history of changes made to this document
VERSION

DATE

EDITED BY

SECTION/S

COMMENTS

0.1

12.03.2010

Karri Sunila

ALL

First draft:

Copyright Nokia Siemens Networks. This material, including documentation and any
related computer programs, is protected by copyright controlled by Nokia Siemens Networks.
All rights are reserved. Copying, including reproducing, storing, adapting or translating, any
or all of this material requires the prior written consent of Nokia Siemens Networks. This
material also contains confidential information which may not be disclosed to others without
the prior written consent of Nokia Siemens Networks.

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

Table of Contents
Table of Contents..............................................................................................
1.

Purpose and Scope............................................................................

2.

GPRS Mobility management..............................................................

2.1
2.2
2.3

GPRS Attach...................................................................................................................
GPRS Attach KPIs...........................................................................................................
Referencing KPIs to be checked.....................................................................................

3.

Troubleshooting..................................................................................

3.1
3.2
3.3
3.4
3.5

Alarms.............................................................................................................................
Quality / Interference.......................................................................................................
Coverage.......................................................................................................................
GPRS Attach Failure Causes Descriptions and Analysis...............................................
SGSN/GGSN.................................................................................................................

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

1. Purpose and Scope

Purpose:
This document is an optimization guideline with the purpose to instruct NPO
engineers working in NOA projects to deliver performance troubleshooting.
This document is meant for INTERNAL USE ONLY
Scope:
The scope of the document is the following:
To show how to troubleshoot cells to improve certain KPIs.
Note! All the networks are different and thus is heavily recommended to analyze
network properly before optimization. Also properly optimization strategy should
be created, will it be better to use special cell level optimized parameter values
and loose control of the network or use some general (not cell level optimized)
values.

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

2. GPRS Mobility management

GPRS Mobility Management (GMM) handles the subscribers' requests for
attaching to or detaching from the General Packet Radio Service (GPRS)
network. GMM updates the location of the subscriber to the Home Location
Register (HLR) and to the Visitor Location Register (VLR) if the Mobile Station
(MS) is also attached to the circuit-switched (CS) services.
MM transfers the necessary information from another SGSN/Packet Processing
Unit (PAPU) when the subscriber moves from one routing area to another. MM
also handles the subscriber's authentication functions.
It is important to monitor the performance of GMM in a GPRS network as the
functions of GMM procedures are to control the accessibility and retainability.
GPRS attach success ratio is one of the most important GMM related KPIs to be
monitored.

2.1 GPRS Attach

The GPRS Attach is a process during which the mobile device informs the
network about its presence in the network. The device usually initiates the GPRS
attach after power on. Mobile state is changing from idle to ready, as can be seen
from figure below. Detach means that mobile state is changing back to idle.

2.2 GPRS Attach KPIs

A MS shall perform a GPRS Attach to the SGSN in order to obtain access to the
GPRS services. If Gs interface available and the network operates in Network
Operation Mode I, the Combined GPRS/IMSI Attach procedure will be performed,
else, a normal GPRS Attach procedure shall be performed.

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

The start of a GPRS attach procedure is defined as when the MS sends a GPRS
Attach Request message to the SGSN. This procedure ends when the MS sends
Attach Complete message to the SGSN or the SGSN sends Attach Reject
message to the MS.
The optimal GSM network from PSW services point of view has:
o

o
o

As high signal level as possible

It means that even the indoor signal level should be high enough to
have MCS9 for getting the highest data rate on RLC/MAC layer.
As low interference as possible
The aim of having high C/I is to avoid throughput reduction based on
interference.
Enough capacity
Enough hardware capacity is needed to provide the required capacity
for PSW services in time. Both CSW and PSW traffic management
should be harmonized with the layer structure and long term plans.
As few cell-reselection as possible
The dominant cell coverage is important to avoid unnecessary cellreselections in mobility. The prudent PCU allocation can help to reduce
the inter PCU cell reselections.
Dominant cell structure can help to maximize the signal level and
reduce the interference, too.
Features
All the features should be used which can improve the PSW service coverage,
capacity and quality in general.

With following KPIs GPRS attach success ratio can be monitored:

o

Gb GPRS Attach Success Ratio, E2E (sgsn_507a), [%]

Gb GPRS Attach Success Ratio (sgsn_569c), [%]

Gb Combined Attach Success Ratio, E2E (sgsn_509a), [%]

o Gb Combined Attach Success Ratio (sgsn_580c), [%]

Note! All the GPRS attach related counters and counter related reject causes can
be seen from chapter 2.7

Typical reasons for GPRS Attach problems are

o

Some Service is not allowed / provisioned

Poor radio conditions

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

2.3 Referencing KPIs to be checked

In following chapters some KPIs, which should be monitored when analyzing
GPRS attach problems are mentioned
There are many times several reasons for KPI degradation, so all step should be
checked to be sure that reasons for GPRS attach problems will be found.

2.3.1 Quality (ulq_2a,dlq_2a, Rx_Level_Statistics table)

Bad quality is typically measured as BER (bit error rate) or as FER (frame erasure
rate). The FER Measurement provides the uplink frame erasure rate (UL FER)
from each codec of each TRX in the BTS.. In this document quality (DL and UL) is
measured using BER measurements.
Bad quality is effecting heavily on PS KPis. In this chapter it is shown how quality
can be measured and how to analyze if quality is on reason which is causing PS
KPI decreasing in the network. In Troubleshooting chapter more detailed
information, how to analyze bad quality is described
RX level quality distribution can be seen below. The distribution (lowest picture)
shows that there are quite a lot bad quality samples which will cause problems in
the network.
o
o
o
o

Voice quality will be decreased

PS quality (throughput ) will be decreased
Dominance areas are not working properly
Drops + HO failures will be increased

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

2.3.2 Coverage (Rx_Level_Statistics table)

Bad coverage means that received signal level is near the (MS/BS) sensitivity
level. Here the quality will be decreased due to bad signal level and like bad
quality, this bad quality will cause user perceived problems.
Bad coverage, like bad quality, is effecting heavily on PS KPIs. If there are bad
coverage dips in the cell, quality will be decreased and call will be dropped. In
troubleshooting chapter more detailed information how to analyze bad coverage
is described.
See picture below, bad coverage samples are due to bad coverage.

Note! It should be checked that there is no imbalance problems between UL and

DL. Many times UL is the weaker one, so UL coverage should be also checked.

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

2.3.3 GPRS Attach Failure Causes Descriptions and Analysis

The purpose of the Reject Cause information element is to indicate the reason
why a request from the mobile station is rejected by the network.
More detailed information can be seen from chapter 2.7

Troubleshooting
There are many times several reasons for KPI degradation, so all step should be
checked to be sure that reasons for dropped calls will be found.
In chapter Error: Reference source not found and Error: Reference source not
found some cause values with examples are given. These cause values are
strongly recommended when analyzing GPRS attach problems

2.4 Alarms
Check that there are no any ** or *** active alarms. Connection to NetAct is
needed.

2.5 Quality / Interference

Bad quality is the most common reason for KPI decreasing. Some
troubleshooting steps to reduce interference are mentioned below.
If there are bad quality (q4q7) samples more than 5%, there are bad quality
problems. Also fewer samples can cause bad drop problems in the network.
Accurate threshold level is difficult to set, because networks are so different.
o

Rx_Level_satistics table can be used for quality/interference analysis

If bad quality in good signal level,(>-75dB)

Frequency changes (new frequency plan) should be done. This is the

worst situation, because no better cell available to make interference
HO.
Interference HO threshold can be adjusted to for example -75dB to
make the difference between quality HO and interference HO more
clear

If bad quality in signal level,(-75dB..-100dB)

Frequency changes can be done to reduce interference

10

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

Handover Threshold Parameters, level, quality, interference. Threshold

values and Px,Nx values can be adjusted
Normally some overlapping exists, so HOs to adjacency, reasons
quality/Interference will happen.
Checked that no missing adjacency cells. Missing neighbors can be
one reason for bad quality, serving areas are not working properly.
If AMR feature can be used, Handover Threshold Parameters, level,
quality, interference. Threshold values and Px,Nx values can be
adjusted little more loose.

If bad quality in bad signal level,(<-100dB)

Bad quality due to bad coverage.
Improve coverage, see 2.6
Check also imbalance between UL and DL. Which coverage UL or DL
is more important to improve
Parameters (Rx Lev Min Cell (SL), Rx Lev Access Min (RXP)) can be
adjusted to avoid call setups / HOs in very bad coverage.

Broken components, quality results are strange, see picture below

Q4 samples are strange, no typical interference. More quality4

samples than quality3 samples. HW problem, after TRX reset TRX
started to work properly.

If AMR feature available and if lots of quality samples in quality5, but not in
quality6 or quality7,

2.6 Coverage
Bad coverage problems are usually indoor problems due to increased losses
(walls etc). These can be outdoor problems also. When cell level coverage
problems are analyzed, it is good to check from planning tool or map, what kind of
area it is (urban, suburban etc)
Bad coverage like bad interference is causing lots of dropped calls. Some
troubleshooting step, how to monitor / improve bad coverage are mentioned
below.
If there are more than 5% bad coverage samples, these can cause lots of drops
in the network. Accurate threshold for bad coverage is difficult to set, networks are
so different.
o

Rx_Level_satistics table can be used for coverage analysis

11

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

If bad UL signal level,(<-100dB) samples .

Check imbalance between UL and DL. If lots of UL imbalance, UL
coverage improvement can improve network performance.
o Add MHA to improve UL coverage
o Check that receiver is working properly, no broken components

If bad DL signal level,(<-100dB) samples .

Check imbalance between UL and DL. If lots of DL imbalance, DL
coverage improvement can improve network performance.
o Check that transmitter is working properly, no broken
components
o Check that power parameter (PMAX) is correct

If no imbalance and bad coverage

Improve coverage by adding RF components
o Add more gain antennas
o Use Flexi BTS
o Add new sector
o Add new site
Parameters (Rx Lev Min Cell (SL), Rx Lev Access Min (RXP)) can be
adjusted to avoid call setups / HOs in very bad coverage.

Broken components (lots of sample <-100dB), see picture below

Almost all UL samples in bad coverage. DL is working fine => HW

problems, broken combiner, TRX etc. No alarms.

2.7 GPRS Attach Failure Causes Descriptions and Analysis

The purpose of the Reject Cause information element is to indicate the reason
why a request from the mobile station is rejected by the network.
All the GPRS attach related counters (Excel) and counter related reject causes
(3GPP specific cause values, Word) are mentioned below, see attached files

GPRS mobility
3GPP specific Cause
management - counters and cause
values.doc
values.xls

Following document is collected from 3GPP document:

12

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

Mobile radio interface Layer 3 specification; Core network protocols; Stage 3

(3GPP TS 24.008 version 9.1.0 Release 9)

http://www.3gpp.org/ftp/Specs/html-info/24008.htm

2.7.1 Cause values - Some troubleshooting examples

o

For user subscription related failures (for example causes 15 and 7), we may
need the support from other parties to improve the success rate, e.g.
customer services to offer service upgrade to those 2G subscribers who are
using 3G phones, etc.

For network related failures (for example cause 17), we can do further
analysis with protocol analyzers, there are a number of information that we
have to know before the troubleshooting starts, i.e.

IMSI check whether the failures are from home subscribers or

roaming subscribers

Signalling flow check the attach failures occurs at which stage of the
procedure

For roaming subscribers with failure cause code 17, request the support from
operation team to verify the connectivity to the roaming partnerss network

For home subscribers with failure cause code 17, check the signaling flow of
the attach procedure, some examples of the failures are:

Attach Reject sent immediately after Attach Request message from UE

o

Attach Reject sent after RANAP Security Mode Command (Security

Mode Complete message not received)
o

check the connectivity to HLR

Further troubleshoot at the RAN

Protocol errors (Cause codes 96,99,100,111) might happen due to poor radio
conditions (Bad quality, bad coverage)

2.8 SGSN/GGSN
SGSG / GGSN related documents can be checked from IMS.
KPI guidline for SGSN
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/358507056
PS core optimization guildleline

13

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D395591264
PS core optimization training material.
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/411075236