You are on page 1of 32

OSSW1274

NetAct OSS4.2

Tracing Subscribers and


Equipment

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

1 (32)

Tracing Subscribers and Equipment

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity, or
performance of the mentioned hardware or software products are given as is and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,
DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT
NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of
Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners,
and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2008. All rights reserved.

2 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Contents

Contents
Contents 3
List of tables 4
List of figures 5
1
1.1
1.2

About this document 7


NetAct compatibility and capacity information
Prerequisites 7

Nokia NetAct Tracing functionality 9

3
3.1
3.1.1
3.2
3.3
3.3.1
3.3.2
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.5
3.6
3.7
3.8
3.9

Tracing subscribers and equipment 11


Preconditions 11
Defining trace activation permissions in the trcpermx.cf file
Overview of the operation 14
Activating a trace 16
Creating a new trace 16
Creating a trace based on an existing trace 17
Analysing the trace data 18
TraceViewer reports 18
Viewing the reports 22
Example: Investigating dropped calls 23
Example: Locating a subscriber or mobile equipment 24
Example: Verifying optimisation 24
Example: Investigating customer complaints 25
Stopping the trace 26
Investigating data further 26
Optimising the network performance 27
Verifying the changes 28
Deleting the trace 28

Where to find more information 31

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

12

3 (32)

Tracing Subscribers and Equipment

List of tables
Table 1.

4 (32)

Explanation of the entries in the trcpermx.cf file

# Nokia Siemens Networks

14

DN01124734
Issue 6-2 en

List of figures

List of figures
Figure 1.

Example of the trcpermx.cf file

Figure 2.

Tracing subscribers and equipment

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

14
15

5 (32)

Tracing Subscribers and Equipment

6 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

About this document

About this document


This document introduces an example procedure on how to use Nokias
Tracing functionality. The document provides you with instructions on how
to monitor mobile equipment or subscriber activity in the network to isolate
problems, to determine the quality of your network as a basis for an
optimisation process, and to verify the planned changes.
This document also briefly introduces, as an example, how other NetAct
functionalities could be used to further investigate the network and
implement the required changes.
For information on related documentation, see section 4 Where to find
more information.

1.1

NetAct compatibility and capacity information


For information on NetAct system and capacity, and the compatibility
between NetAct and network element releases, see the NetAct
Compatibility and Capacity Information document.

1.2

Prerequisites
This section lists the software and functionality requirements that enable
you to perform the operations described in this document. Read this
section carefully to avoid unnecessary troubleshooting later.
Functionality used in this operation
The following NetAct functionalities are required in tracing subscribers and
equipment:
.

DN01124734
Issue 6-2 en

NetAct Tracing (optional)

# Nokia Siemens Networks

7 (32)

Tracing Subscribers and Equipment

The following NetAct Reporter functionalities can be used (according to


your needs) to complement Tracing:

8 (32)

Report Builder

Report Set for BSS

Report Set for GPRS

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Nokia NetAct Tracing functionality

Nokia NetAct Tracing functionality


The Nokia NetAct Tracing functionality enables online and offline GSM,
GPRS and 3G tracing and trace management, either regionally or globally
(within the management scope of several NetAct Regional Clusters).
Tracing gives detailed information on calls that are related to the defined
IMSI/MSISDN or IMEI numbers.
TraceViewer receives trace data from the Nokia network elements HLR,
MSC, BSC, SGSN, GGSN, MGW and RNC.
The most common way to use Tracing is to send a test mobile phone into a
certain area and make observations on the performance, either of certain
network elements or in a certain area. Tracing can be used, for example, to
troubleshoot customer complaints or to support network planning and
optimisation.
For an overview of Tracing, see the Tracing Principles document. For more
detailed technical information, see the Tracing Technical Reference Guide
document.

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

9 (32)

Tracing Subscribers and Equipment

10 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

Tracing subscribers and equipment


This section introduces the basic tasks to be carried out in locating and
correcting faults in the network when the TraceViewer application is in use.
The supported releases and the functionalities used in this operation are
presented in section 1.2 Prerequisites in this document. Note that optional
functionalities are also listed.

3.1

DN01124734
Issue 6-2 en

Preconditions
.

If you have more than one region in your network, it is important that
the connections between the regions exist. This way, if the mobile
user moves between regional areas, the trace events are sent to the
original region from all the other regions included in the trace. For
more information, see section 1 Preliminary tasks in the Configuring
Trace Data Flow document.

TraceViewer has to be integrated to the relevant clusters in your


network. For instructions, see the Configuring Trace Data Flow
document.

The user group roles for GUI actions in the TraceViewer have to be
defined. For an overview of user management, see the Managing
Users document. For a list of roles in TraceViewer, see appendix
Roles, permissions and operations in OSS4.1 in the Managing
Users document. For instructions on how to manage groups, roles
and permissions, see the NetAct Permission Manager Help
document. If you have problems, please contact your system
administrator.

# Nokia Siemens Networks

11 (32)

Tracing Subscribers and Equipment

3.1.1

The permissions for user groups to activate traces for certain IMSI,
IMEI and MSISDN numbers must be defined in the trcpermx.cf
file. For instructions on editing this file, see section 3.1.1 Defining
trace activation permissions in the trcpermx.cf file.

If you want to receive trace data from 3G SGSN network elements,


you will have to configure the 3G SGSN. For instructions, see
section Configuring and checking the settings of 3G SGSN in the
Configuring Trace Data Flow document.

Defining trace activation permissions in the trcpermx.cf file


The IMSI, IMEI and MSISDN numbers that TraceViewer user groups can
trace are defined in the permission configuration file trcpermx.cf. This
enables the authorisation or restriction of tracing according to the
subscribers and equipment.
This section describes the trcpermx.cf file and gives instructions on how
to edit the trace activation permissions.
For more information about the trcpermx.cf file, see section 1 trcpermx.
cf in the Tracing Technical Reference Guide document.

Note
If you get the following error message when trying to activate a trace, it
means that you have not been given permission to activate a trace for
the particular IMEI, IMSI or MSISDN number:
Error occurred during trace activation. User access rights
prevents the current operation.

To define trace activation permissions in the trcpermx.cf file


1.

Copy the default file to the correct location:

omc>% cp $PRODUCTROOT/monitor/trc/trccor/conf/default/trcpermx.cf \$ETCROOT/monitor/


trc/trccor/conf

2.

12 (32)

Edit the file located in the $ETCROOT/monitor/trc/trccor/conf


directory according to your TraceViewer tracing permissions
scheme. For more information, see figure 1 Example of the
trcpermx.cf file and table 1 Explanation of the entries in the
trcpermx.cf file below.

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

3.

Find out the trcdasmx and trcactmx PIDs by giving the following
commands:
omc>% mx grep trcdasmx
omc>% mx grep trcactmx

4.

Send a USR2 signal to trcdasmx and trcactmx by giving the


following commands:
omc>% kill -USR2 <trcdasmx_pid>
omc>% kill -USR2 <trcactmx_pid>

The trcdasmx process will restart after the supervision time has
passed. Please note that the supervision time is defined during
installation, and can be found from the $PRODUCTROOT/monitor/
trc/trccor/conf/default/wpmtrccormx.cf file. For more
information, see section 1 wpmtrccormx.cf in the Tracing Technical
Reference Guide document.
The changes to the trcpermx.cf configuration file are now applied.
5.

Close and restart each TraceViewer GUI.


This is needed to re-establish the connection between the
TraceViewer GUIs and trcdasmx.

Example of the trcpermx.cf file


(IdType

IMSI
(User
)
(User
)
(User

usrgrp1
(Section
PermittedIMSI )
usrgrp2
(Section
PermittedIMSI )
usrgrp3
(Section
RestrictedIMEI)

)
)
(IdType

(Section

)
(Section

IMEI
.
.
.
PermittedIMSI
(NotFound
false)
(IdValue
14326533)
(IdValue
13226533)
RestrictedIMEI
(NotFound
true)
(IdValue
6533763)
(IdValue
7258268)

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

13 (32)

Tracing Subscribers and Equipment

Figure 1.

Example of the trcpermx.cf file

Entries in the trcpermx.cf file

Table 1.

Explanation of the entries in the trcpermx.cf file

Parameter

Description

IdType

The type of the traced object. The possible values are "IMSI",
"IMEI" or "MSISDN".
There can be an unlimited number of IdType records, but it is
recommended that there is exactly one record for each
possible value. If one type is missing, the tracing of that type is
not allowed at all.

User

The user group for which the permission rules in the section
apply to.
There can be an unlimited number of user fields but it is
recommended that the number is kept low.

Section

The name of the section record from where the permission for
this special user group and IdType is fetched.
There is only one section for each user group.

NotFound

The default permission if the asked ID value is not explicitly


listed in this section. The possible values are "true" and "false".
If the value is "true", the IdValue list is a list of unallowed
targets, and any target not found in the list is an allowed trace
target.
If the value is "false", the IdValue list is a list of allowed targets,
and any target found in the list is an allowed trace target.

IdValue

3.2

The IMSI, IMEI or MSISDN numbers that the user group has
been authorised to trace. There can be an unlimited number of
ID values.

Overview of the operation


The following flowchart gives you an overview of the tasks involved in
tracing a subscriber or equipment.
If you are already familiar with the basic procedure, you can use the
flowchart as a reference, and when you need more detailed information on
how to perform a particular task, you can access the instructions by
clicking the relevant step.

14 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

Start
Activate trace

Analyse tracing data

Trace
still active?

No

Yes
Stop trace

Investigate
more?

No

Yes
Investigate data further

No

Optimise
NW?
Yes
Verify changes

Delete trace
Stop

Figure 2.

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

# Nokia Siemens Networks

15 (32)

Tracing Subscribers and Equipment

3.3

Activating a trace
A trace can be activated by creating a completely new trace (see section
3.3.1 Creating a new trace) or by copying the trace parameters from an
existing trace (see section 3.3.2 Creating a trace based on an existing
trace).
The network elements and network types included in the trace depend on
your tracing needs. For example, if you wish to troubleshoot a problem in a
particular network element (for example PDP activation failure in an
SGSN), you can select only this particular element to be traced.

3.3.1

Creating a new trace


For subscriber tracing (that is, IMSI/MSISDN tracing), you can activate the
trace in an HLR, MSC, SGSN, 3G SGSN or RNC. For mobile equipment
tracing (that is, IMEI tracing), the elements to be activated are an MSC or
SGSN. Trace events can also be received from a BSC, GGSN or MGW. A
trace can be virtual or an online trace. For more information on virtual
tracing for the multi-vendor case, see section 1 Using virtual tracing in a
multi-vendor network element environment in the Tracing Principles
document.

To start a new trace


1.

Start TraceViewer.

2.

Create a new trace (for example, by selecting File New...).


For more ways of creating new traces, see the TraceViewer Help
document.

3.

In the Trace Info pane, check the Virtual Trace check box if you want
to create a virtual trace.
Traces created with TraceViewer can only be activated in Nokias
NEs. However, in TraceViewer, you can create a virtual trace for the
traces activated manually in the other vendor MSC/HLR. The trace
events coming from the network will then be attached to these virtual
traces in TraceViewer.
For more information on virtual tracing for the multi-vendor case, see
section 1 Using virtual tracing in a multi-vendor network element
environment in the Tracing Principles document. For instructions on
creating a virtual trace, see section Creating a virtual trace in a multivendor network element environment in the TraceViewer Help
document.

16 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

4.

For a virtual trace, type a trace reference number in the Trace


Reference field.
With this number, the trace events can be attached to the correct
trace. For more information on how to set the trace reference
number, see section 1 Setting trace reference values in the Tracing
Principles document.

5.

Select the trace target from theTraced Target drop-down list (IMSI
or MSISDN for a subscriber trace or IMEI for an equipment trace).

6.

Type the traced number (IMSI, MSISDN or IMEI number) in the


Traced Number field.

7.

Enter the tracing parameters according to your tracing needs. The


following parameters are used:
.
tracing time
.
cluster
.
element type
.
traced network (if it can be selected)
.
trace level
.
template
The tracing parameters available depend on the trace type.

8.

In the Network Elements pane, select the network elements you


want to trace (if they can be selected).

9.

Click Activate to start the trace.

For instructions, see section Creating a new trace in the TraceViewer Help
document.

3.3.2

Creating a trace based on an existing trace


Instead of creating a completely new trace, you can use an existing trace
as a basis for a new tracing event. This option can also be used if you want
to activate a similar trace, first to locate a problem and then to verify
whether it was fixed.

To create a new trace by copying the parameters from an


existing trace

DN01124734
Issue 6-2 en

1.

Start the TraceViewer application. If the application is already open,


it is advisable to refresh the view (select Trace Refresh).

2.

Select the trace you want to use as the basis of a new trace. (If you
wish to check the trace properties, select Trace Properties).

# Nokia Siemens Networks

17 (32)

Tracing Subscribers and Equipment

3.

Copy the trace information (File Copy).

4.

Modify the existing parameters if necessary. At least the tracing start


and stop times should be changed.

5.

Click Activate to start the trace.

For instructions, see section Creating a new trace by copying an existing


trace in the TraceViewer Help document.

3.4

Analysing the trace data


After receiving the trace data, you should analyse the results. Data can be
analysed for the purposes of network troubleshooting, to find out what was
the cause for degraded performance. Trace data can also be analysed to
determine the needs and the extent of the possible changes in network
configuration.
Trace data is presented in TraceViewer in the form of reports. There are
four report sets available: GSM, GPRS, 3G Uplink and Radio
Performance, and the 3G Downlink Performance. See section 3.4.1
TraceViewer reports for a list of reports. For instructions on how to view the
reports, see section 3.4.2 Viewing the reports.
Examples of how trace data can be analysed to check problems in the
network, to investigate customer complaints, or to locate a subscriber/
mobile equipment are provided in the following sections.

Note
The examples given in these sections only provide a simplified idea of
how Tracing might be used. They are not intended to be used as
instructions.

3.4.1

TraceViewer reports
For a description of the reports and the counters used, see the
TraceViewer Report Descriptions for GSM document, the TraceViewer
Report Descriptions for GPRS document, the TraceViewer Report
Descriptions for 3G Uplink and Radio Performance document, and the
TraceViewer Report Descriptions for Downlink Performance document.

18 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

GSM reports
With a licence for TraceViewer GSM reports, the following reports are
available for analysis:
.

GSM textual reports (MSC, HLR, BSC, MGW):


.
BSC SDCCH seizures
.
BSC TCH seizures
.
BSC handovers
.
BSC online radio measurement
.
HLR subscribers
.
MSC observations
.
MSC handovers
.
MSC location updates
.
MSC SMS sent/received
.
MGW observations
.
MSC SIP observations
.
MSC authentication observations

GSM graphical reports (BSC):


.
GSM signal quality
.
GSM signal levels
.
GSM adjacent cells
.
GSM timing advance
.
GSM frame error rate (FER)
.
GSM AMR report

GSM report tree


The GSM report tree is a management tree structure that can be
used to navigate within all the GSM textual and graphical reports.

GPRS reports
With a licence for TraceViewer GPRS reports, the following reports are
available for analysis:
.

DN01124734
Issue 6-2 en

GPRS textual reports (SGSN, GGSN):


.
TBF allocation
.
TBF reallocation
.
TBF release
.
PDP context activation
.
PDP context modification

# Nokia Siemens Networks

19 (32)

Tracing Subscribers and Equipment

.
.
.
.
.
.
.
.
.

PDP context deactivation


routing area update
GPRS attach
GPRS detach
SMS received
SMS sent
3G packet-switched core
cell reselection
GPRS radio measurement

GPRS graphical reports (SGSN, GGSN):


.
GPRS flow control
.
GPRS number of TCHs (uplink/downlink)
.
GPRS data transferred per MCS (uplink/downlink)
.
GPRS PFC change
.
GPRS signal level
.
GPRS signal quality
.
GPRS adjacent cells
.
PDP result overview

GPRS textual and graphical trees


The GPRS textual and graphical report trees are management tree
structures for navigating within the textual and graphical GPRS
reports.

3G Uplink and Radio performance reports


With a licence for 3G Uplink and Radio performance reports, the following
reports are available for analysis:

20 (32)

3G HLR report

3G circuit-switched core reports:


.
location update
.
handover
.
MSC observation
.
SMS
.
MGW observation
.
MSC SIP observation
.
MSC authentication observation

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

DN01124734
Issue 6-2 en

3G RAN reports:
.
UE RRC state
.
UE capability
.
cell update
.
radio access bearer
.
radio access bearer uplink bit rate
.
radio access bearer downlink bit rate
.
radio bearer
.
radio bearer uplink traffic volume
.
radio bearer downlink traffic volume
.
cell and radio link
.
cell and radio link downlink power
.
outer loop power control uplink SIR
.
dedicated transport channel
.
dedicated transport channel uplink bit rate
.
dedicated transport channel uplink bit rate of all DCHs
.
dedicated transport channel downlink bit rate
.
uplink performance uplink BLER
.
uplink performance uplink Eb/No
.
handover based information UE transmission power
.
handover based information UE Rx Tx time difference
.
handover based information intra frequency measurement
neighbouring cell list
.
handover based information intra frequency measurement
control message
.
handover based information intra frequency measurement
measurement report
.
handover based information intra frequency measurement
measurement report CPICH Ec/No
.
handover based information inter frequency measurement
neighbouring cell list
.
handover based information inter frequency measurement
control message
.
handover based information inter frequency measurement
measurement report
.
handover based information inter frequency measurement
measurement report CPICH Ec/No
.
handover based information inter system measurement
neighbouring cell list
.
handover based information inter system measurement
control message

# Nokia Siemens Networks

21 (32)

Tracing Subscribers and Equipment

handover based information inter system measurement


measurement report
handover based information inter system measurement
measurement report RSSI

3G trace tree
The 3G trace tree is a management tree structure for navigating
through the 3G reports.

3G Downlink performance reports


With a licence for 3G Downlink performance reports, the following reports
are available for analysis:

3.4.2

3G downlink textual reports:


.
downlink AM RLC
.
downlink performance

3G downlink graphical reports:


.
buffer occupancy
.
PDU throughput
.
PDU/SDU error ratio
.
SDU transfer delay
.
downlink BLER

Viewing the reports


You can view the trace data in the form of reports in TraceViewer.

To view the TraceViewer reports


1.

Start the TraceViewer application.

2.

To list the traces activated in a particular region, select the correct


region from the Cluster drop-down box.

3.

Select the trace from the table in the TraceViewer main window by
double-clicking the trace.
The trace report opens in the View Trace window.

4.

22 (32)

Analyse the reports to identify the problem. If you detect


performance degradation, inform your network planning and
optimisation personnel about the required changes in the network.

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

5.

Print the trace information if necessary (in the View Trace window,
select File Print).

6.

If you wish to investigate the tracing data later or send it to someone


else, export the trace data to a file (in the View Trace window, select
File Export).
It may be helpful to print the trace report or export it to a file so that
you can compare it with a trace report created after the problem has
been fixed. For more information, see section 3.8 Verifying the
changes.

3.4.3

Example: Investigating dropped calls


Note
This example only provides a simplified idea of how Tracing might be
used. It is not intended to be used as an instruction.

If it is noticed that calls are dropping, a test trace can be activated to collect
trace data.
The clear code (call release reason) can be checked from the GSM text
report. For information about the GSM text report, see section 1 Interrupts
in the TraceViewer Report Descriptions for GSM document.
The reason for calls being released may be due to problems in the radio
network. In that case, measurements from the network can be checked
from the GSM signal level and signal quality reports. For more information
about these reports, see section 1 Signal quality and section 1 Signal
levels in the TraceViewer Report Descriptions for GSM document.
The GSM adjacent cells report can also be checked to investigate why a
handover was not made before the call was dropped and whether there
were any suitable targets for a handover. For more information about the
report, see section 1 Adjacent cells in the TraceViewer Report
Descriptions for GSM document.

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

23 (32)

Tracing Subscribers and Equipment

3.4.4

Example: Locating a subscriber or mobile equipment


Note
This example only provides a simplified idea of how Tracing might be
used. It is not intended to be used as an instruction.

If the police want to locate a subscriber or stolen mobile equipment, for


example, a trace can be activated in TraceViewer with the subscriber
number (IMSI or MSISDN) or mobile equipment IMEI as the trace target
and HLR as the activating network element.
The location area code and cell ID gives the location of the traced
subscriber or equipment. This data can be found from the GSM text report.
For more information about the report, see section 1 Location updates in
the TraceViewer Report Descriptions for GSM document.
The location can also be obtained from a combination of location area
code, cell ID and timing advance, which can be found from the BSC online
radio measurement report. For more information about the report, see
section 1 GSM online radio measurement report in the TraceViewer
Report Descriptions for GSM document.

3.4.5

Example: Verifying optimisation


This section gives examples of how tracing might be used to verify
optimisation after modifying parameters or adding new sites.

Note
These examples only provide a simplified idea of how Tracing might be
used. They are not intended to be used as instructions.

Verifying modified parameters


As part of a plan for network optimisation, parameters have been modified
so that handovers occur under certain conditions. Tracing can be used to
test whether the modifications have worked. In TraceViewer, a trace is
activated with the GSM tree report selected as the report template. The
data on handovers can then be checked to verify that the handover results
and routes are working as planned.

24 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

For more information about the reports, see section 1 Handover reports in
the TraceViewer Report Descriptions for GSM document.
Verifying new sites
As part of a plan for network optimisation, new sites have been added.
Tracing can be used to verify the adjacent cell definition. In TraceViewer, a
trace is activated for a test phone with the GSM adjacent cells report
selected as the report template. The signal strength of the new adjacent
cells for the serving cell (the traced mobile equipment) can then be
checked from this report.
For more information about the report, see section 1 Adjacent cells in the
TraceViewer Report Descriptions for GSM document.

3.4.6

Example: Investigating customer complaints


This section gives examples of how tracing might be used to investigate
customer complaints of failed connections or insufficient QoS levels.

Note
These examples only provide a simplified idea of how Tracing might be
used. They are not intended to be used as instructions.

GPRS connection fails


A user wants to use a GPRS phone to check the e-mail, but is unable to
set up a GPRS connection. The operator does not know which SGSN is
being used, so they activate an MSISDN trace in the HLR, with the GPRS
textual report tree as the report template. Once the trace is activated, the
user is asked to try to make the GPRS connection again. Trace data from
the SGSN and BSC is received.
The GPRS textual report tree shows that the PDP context creation has
failed, and the failure cause shows that the APN is unknown. The
customer may have specified an incorrect APN on the phone, or there
could be a problem with the configuration of the packet-switched core
network (an incorrect GGSN IP address or incorrectly defined APN).
For more information about the GPRS textual reports, see section 1 GPRS
textual report tree in the TraceViewer Report Descriptions for GPRS
document.

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

25 (32)

Tracing Subscribers and Equipment

QoS level insufficient


A customer using video streaming does not get the negotiated quality of
service level when using 3G services. A trace is activated in TraceViewer
via the HLR and the 3G tree report is selected as the report template. The
requested and negotiated QoS parameters can be checked from the
3GSGSN PDP created event in the 3G PS core report. The QoS
properties that are acceptable for RAN can be monitored from the 3G RAN
radio access bearer report. A comparison of data from the two reports may
indicate that the RAN subsystem cannot provide the requested radio
access bearer services. In this case it may be necessary to optimise RAN
parameters.
For more information about the 3G PS core report, see section 1 3G PS
core report in the TraceViewer Report Descriptions for GPRS document.
For more information about the radio access bearer report, see section 1
Radio access bearer report in the TraceViewer Report Descriptions for 3G
document.

3.5

Stopping the trace


If the tracing period has not yet expired, you can stop the active trace
manually.

To stop an active trace

3.6

1.

Start TraceViewer if it is not open.

2.

Select the trace(s) you want to deactivate in the TraceViewer main


window.

3.

Select File Stop.

Investigating data further


If you want to investigate the problematic areas or network elements
further with other Nokia applications or were not able to identify the
problem clearly enough just by analysing the trace reports, you can use,
for example, the NetAct Reporter functionalities to create reports on a
more detailed level. With Reporter you can investigate traffic, resource and
mobility-related problems, such as the reason for TCH drop ratio or
degraded UL/DL signal strength and quality.
You can use the following functionalities:

26 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

Report Builder (for example BSS, NSS and GPRS reports)

Report Set for BSS

Report Set for GPRS

For more information on NetAct Reporter functionality, see the Reporter


and Performance Management Principles document.
For more information about Report Builder and reports on handovers, see
section 1 Checking adjacencies in the Managing Adjacencies document.
If the corrections require changes in the network configuration, inform your
planning and optimisation personnel.

3.7

Optimising the network performance


NetAct Optimizer provides detailed visualisation and analysis methods as
well as effective algorithms for optimising the performance and capacity in
the network. NetAct Optimizer can be used from network element level
optimisation to network level optimisation. The tool analyses the measured
network performance and proposes changes to the actual element
configurations for achieving the given performance target. Optimizers
solution uses the actual configuration data and measurement reports
available in NetAct. Optimizer can be used for the following purposes:

DN01124734
Issue 6-2 en

Manual adjacency management (adjacency generation and


deletion) for optimising the adjacency definitions of the GSM and 3G
networks and inter-system adjacencies. This functionality is also
available in a graphical user interface based on a map.

Mobile measurement-based frequency allocation for computing a


new frequency plan for a GSM network.

Automated (mobile measurement-based) adjacency creation for


automatically optimising the adjacencies in a network.

WCDMA early phase optimisation for analysing current WCDMA


performance and configuration in special task-oriented views and for
making changes to critical parameters. The functionality is also used
for managing all WCDMA and joint GSM and WCDMA adjacency
types, either manually on map or automatically using location
information.

Service Optimizer is a new module designed for QoS analysis per


traffic class and for automated, measurement-based capacity
optimisation for GPRS services.

# Nokia Siemens Networks

27 (32)

Tracing Subscribers and Equipment

For more information on the Optimisation functionality, see the Optimizer


Principles document.
For more information on the process of optimising a network using
Optimizer, see the Optimising a Network Using Optimizer document.
If the network requires that new network elements are integrated or that
other changes are made in the current NW configuration, the following
NetAct user documents provide you with example procedures on how to
plan and implement the changes:
.

Creating BTS Sites

Rehosting GSM BTS Sites

For more example procedures, see the Optimise and Expand category in
NetAct user documentation.

3.8

Verifying the changes


After the problem has been corrected in the network, you can use
TraceViewers textual and graphical presentations to verify that all sites
and network elements are working as planned and that all the changes
have been implemented successfully. This is done by activating a similar
trace again and checking the tracing results.

To verify the corrections


1.

Start the TraceViewer application.

2.

Select the trace to be used as a basis for a new trace.


For instructions, see section 3.3.2 Creating a trace based on an
existing trace.

3.9

3.

Go through the observation reports to see if the changes had the


desired effect on the network performance.

4.

Stop the trace and export the trace data, if necessary.

Deleting the trace


If you decide not to store the tracing information to the database for later
analysis or for offline tracing, you can delete the data from the database.
Otherwise the data will be stored in the database for two weeks.

28 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Tracing subscribers and equipment

To delete the tracing information

DN01124734
Issue 6-2 en

1.

Start the TraceViewer application if it is not already open.

2.

Select the trace(s) you wish to delete.

3.

Select File Delete.

# Nokia Siemens Networks

29 (32)

Tracing Subscribers and Equipment

30 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en

Where to find more information

Where to find more information


General
For NetAct terminology, see the Glossary.
Tracing documentation
For information on changes in Tracing functionality and TraceViewer, see
the Functionality Changes in Tracing document.
For an overview of Tracing, see the Tracing Principles document.
For information on Tracing processes, configuration files and data flow,
see the Tracing Technical Reference Guide document.
For instructions on using the TraceViewer application, see the
TraceViewer Help document.
For information on the reports available with TraceViewer, see the
following documents:
.

TraceViewer Report Descriptions for GSM

TraceViewer Report Descriptions for GPRS

TraceViewer Report Descriptions for 3G Uplink and Radio


Performance

TraceViewer Report Descriptions for 3G Downlink Performance

For descriptions of the counters used in TraceViewer reports, see the


Database Description for Trace Observations document.
For information about inter-cluster communication, see the Configuring
Trace Data Flow document.

DN01124734
Issue 6-2 en

# Nokia Siemens Networks

31 (32)

Tracing Subscribers and Equipment

User management
For information about user management, see the Managing Users
document.
For instructions on managing groups, roles and permissions, see the
NetAct Permission Manager Help document.
For information about creating a maintenance region service user, see
section 1 Creating a maintenance region service user or a local service
user in the Managing Users document.
For instructions on creating a maintenance region service user, see
section Creating a maintenance region service user in the Service User
Management Help document.
Other functionalities
Reporter and Performance Management Principles
1 Checking adjacencies in the Managing Adjacencies document.
Optimizer Principles
Optimising a Network Using Optimizer
Radio Access Configurator Principles
Creating BTS Sites
Rehosting GSM BTS Sites

32 (32)

# Nokia Siemens Networks

DN01124734
Issue 6-2 en