BSS Performance

Troubleshooting Instructions
PDP Context Activations
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

15.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 Session management..............................................................

2.1
2.2
2.3

PDP Context activation....................................................................................................

PDP Context activation KPIs...........................................................................................
Referencing KPIs to be checked.....................................................................................

3.

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

3.1
3.2
3.3
3.4
3.5

Alarms.............................................................................................................................
Quality / Interference.......................................................................................................
Coverage.........................................................................................................................
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 Session management

The main function of Session Management (SM) is to support the PDP context
handling of the MS/UE. GPRS SM procedures comprise of PDP Context
Activation, PDP Context Modification and PDP context Deactivation. These
procedures can only be performed if a GMM context has already been
established between MS/UE and the network.
It is important to monitor the performance of SM procedures in any network
because failure of SM procedures (e.g. PDP Context Activation) for an MS/UE will
mean data service inaccessible for the subscriber..
PDP context activation success ratio is one of the most important Session
management related KPIs to be monitored.

2.1 PDP Context activation

The purpose of PDP Context Activation is to establish a session between the
MS/UE and the network for a specific QoS on a specific NSAPI. The Secondary
PDP Context Activation procedure may be used to activate a PDP context while
reusing the PDP context address and other information from an already active
PDP context, but with a different QoS profile. In SGSN SG6 implementation, only
the MS/UE can initiate the PDP Context Activation.
The start of a PDP Context Activation procedure is defined as when the MS/UE
sends an Activate PDP Context Request message to the SGSN. This procedure
ends when the SGSN sends Activate PDP Context Accept or Activate PDP
Context Reject message to the MS/UE.

2.2 PDP Context activation KPIs

The optimal GSM network from PSW services point of view has:
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.

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

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.

Following KPIs can be used when monitoring PDP context activation:

o

Gb MS Originated PDP Activation Success Ratio, E2E (sgsn_535a), [%]

Gb MS Originated PDP Context Activation Success Ratio (res_sgsn334c), [%]

Gb Secondary PDP Activation Success Ratio, E2E (sgsn_537a), [%]

Secondary Gb PDP Context Activation Success Ratio (sgsn_613b), [%]

Typical reasons for GPRS Attach problems are

o

Some Service is not allowed / provisioned

HLR problems

APN problems

Poor radio conditions

2.3 Referencing KPIs to be checked

In following chapters some KPIs, which should be monitored when analyzing PDP
Context activation problems are mentioned
There are many times several reasons for KPI degradation, so all step should be
checked to be sure that reasons for PDP Context activation 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

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

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

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.

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

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.

2.3.3 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 2.7 and 2.7.1 some cause values with examples are given. These
cause values are strongly recommended when analyzing PDP context activation
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.

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

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

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)

10

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

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

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 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.

11

Copyright 2007 Nokia Siemens Networks.

All rights reserved.

All the PDP Context activation related counters (Excel) and counter related reject
causes (3GPP specific cause values, Word) are mentioned below, see attached
files

Session
3GPP specific Cause
management - counters and
values_SM.doc
cause values.xls

Following cause value document is collected from 3GPP document:

o

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 28,33), we may
need the support from other parties to improve the success rate, e.g.
customer services to assist 3G users in configuring the correct setting in their
phones, implement OTA to send configuration settings to users, etc.

For network or signaling related failures for example causes 38,96), we can
do further analysis with protocol analyzers, i.e. check::

signaling flow
o

to make sure the signaling flow is correct

for cause code 96 (invalid Mandatory Information), check if the

information sent by the UE is correct

Connectivity of network elements

o

For Network Failure, check the connectivity between SGSN

and GGSN

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
https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D395591264
PS core optimization training material.
https://sharenet-ims.inside.nokiasiemensnetworks.com/Open/411075236:

12

Copyright 2007 Nokia Siemens Networks.

All rights reserved.