Call Trace User Guide V3.0

Call Trace User Guide
Document number: UMT/IRC/APP/022962

Document issue: 03.00 / EN
Document status: Standard
Date: 28/Jan/2009
Passing on or copying of this document, use and communication of its contents not permitted without
AlcatelLucent written authorization
Internal document

Copyright
2007 Alcatel-Lucent, All Rights Reserved

Printed in France

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write
protected; it may be altered only by authorized persons. While copies may be printed, it is not recommended.
Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded
as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-
Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information
contained herein confidential, shall disclose the information only to its employees with a need to know, and shall
protect the information from disclosure and dissemination to third parties. Except as expressly authorized in
writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have
received this document in error, please notify the sender and destroy it immediately.

UMT/IRC/APP/022962 03.00 / EN Page 3/3

PUBLICATION HISTORY
28/01/2009
Issue 3.0 EN, Standard
Update for OAM 6.0
Increase of maximum Number of CTb Sessions
Tracing session exclusion removal
Additional periodic UE Measurements
Introduction of call failure trace as part of CTg
Addition of EcNo Values of detected cells in CTn Records

10/01/2008
Issue 2.0 EN, Standard
Update for OAM 5.2

27/07/2007
Issue 1.0 EN, preliminary
Creation

CONTENTS
1. INTRODUCTION............................................................................................................................6
1.1 OBJECT ......................................................................................................................................6
1.2 SCOPE OF THIS DOCUMENT..........................................................................................................6
1.3 AUDIENCE FOR THIS DOCUMENT...................................................................................................6
2 RELATED DOCUMENTS..............................................................................................................7
2.1 APPLICABLE DOCUMENTS.............................................................................................................7
2.2 REFERENCE DOCUMENTS.............................................................................................................7
3 OVERVIEW....................................................................................................................................8
3.1 CORE NETWORK INVOKED CALL TRACE (CTA) ...............................................................................9
3.1.1 Description ......................................................................................................................9
3.1.2 Activation / Calls selection ..............................................................................................9
3.1.3 Start/Stop tracing ............................................................................................................9
3.1.4 Traced information ........................................................................................................10
3.2 ACCESS INVOKED CALL TRACE (CTB) .........................................................................................10
3.2.1 Description ....................................................................................................................10
3.2.2 Activation/Calls selection ..............................................................................................10
3.2.3 Start/Stop tracing ..........................................................................................................10
3.3 GEOGRAPHICAL CALL TRACE (CTG)............................................................................................12
3.3.1 Description ....................................................................................................................12
3.4 OBJECT TRACE (OT) .................................................................................................................13
3.4.1 Description ....................................................................................................................13
3.5 CALL TRACE NEIGHBORING (CTN) ..............................................................................................14
3.5.1 Description ....................................................................................................................14
4 FUNCTIONAL DESCRIPTION....................................................................................................16
4.1 RNC PERFORMANCES ...............................................................................................................16
4.1.1 CTa performances ........................................................................................................16
4.1.2 CTb performances ........................................................................................................16
4.1.3 CTg performances ........................................................................................................16
4.1.4 CTn performances ........................................................................................................17
4.1.5 OTCell performances....................................................................................................17
4.1.6 OTIu-CS performances.................................................................................................18
4.1.7 OTIu-PS performances .................................................................................................18
4.1.8 OTIuR performances.....................................................................................................18
4.1.9 OTIu-BC performances.................................................................................................18
4.1.10 OVERLOAD MANAGEMENT ...........................................................................................18
5 CALL TRACE ACTIVATION/DEACTIVATION...........................................................................20
5.1 CALL TRACE WIZARD .................................................................................................................20
5.1.1 Launching CallTrace wizard..........................................................................................20
5.2 HOW TO CREATE AN ACCESS SESSION (CTB) ...............................................................................22
5.2.1 Creating one or more Access sessions on one RNC ...................................................22
5.2.2 Creating an access session multiple RNCs ..................................................................30
5.3 HOW TO CREATE A GEOGRAPHICAL SESSION...............................................................................33
5.4 HOW TO CREATE A CELL SESSION...............................................................................................37
5.5 HOW TO CREATE AN OBJECT SESSION .....................................................................................38
5.6 HOW TO CREATE A CTN SESSION...............................................................................................39
5.7 HOW TO DELETE A SESSION .......................................................................................................41
6 CALL TRACE TEMPLATE MANAGEMENT ..............................................................................46
6.1 CREATE A TRACE SESSION TEMPLATE........................................................................................47
6.2 HOW TO DELETE A TRACE SESSION TEMPLATE.............................................................................49
7 CALL TRACE POST-PROCESSING TOOLS.............................................................................50
7.1 CALL TRACE FILES COLLECTION .................................................................................................50
7.2 POST-PROCESSING TOOLS ........................................................................................................51
RFO..............................................................................................................................................51
WQA.............................................................................................................................................51
8 ABBREVIATIONS AND DEFINITIONS.......................................................................................53
8.1 ABREVIATIONS ..........................................................................................................................53
9 ANNEX.........................................................................................................................................54
9.1 CN FUNCTIONS AND SUB-FUNCTIONS TRACEABLE PER SESSION TYPE........................................54
9.2 IN FUNCTIONS AND SUB-FUNCTIONS TRACEABLE PER SESSION TYPE..........................................58
9.3 TEMPLATES AND THEIR PRE-DEFINED LIST OF RECORD TYPES AND ASSOCIATED MODES ................59

1. INTRODUCTION
1.1 OBJECT
The object of this document is to describe and explain the method to launch the Call Trace from the
WMS Configuration Wizard.

1.2 SCOPE OF THIS DOCUMENT
The scope of this document is UA6.0 / OAM06.0 .

1.3 AUDIENCE FOR THIS DOCUMENT
This document is meant for Engineering teams, Product teams
2 RELATED DOCUMENTS
2.1 APPLICABLE DOCUMENTS
[A1] Mobility Optimization Guidelines

2.2 REFERENCE DOCUMENTS
[R1] 411-8111-534 06.08 UMTS Access Network Performance Management

[R2] UMT/SYS/DD/000077 UTRAN Call Trace Specification

[R3] UMT/RNS/DD/0006 SIE RNC Tracing Data Format

[R4] UMT/OMC/DD/020726 WQA Post-Processing for UTRAN Neighbouring Tuning

[R5] NN-20500-128 WQA User Guide (Ctn part)

[R6] UMTS/HSxPA RF Optimizer Feature Requirements Specification for UTRAN 4.2 5.0

[R7] NN-20500-033 UMTS Access Network Performance Management

3 OVERVIEW
Call Trace is a valuable feature that enables users to track a specific call and analyze its behaviour
over time. All protocol messages and RF measurements relative to the call will be stored, correlated,
and analyzed.
Call Trace is the whole of the following types of Call Trace sessions:
Core Network Invoked Call Trace, usually referred to as CTa
Access Invoked Call Trace, usually referred to as CTb
Geographic Call Trace, usually referred to as CTg
Neighboring Call Trace, usually referred to as CTn
Object Trace on the cell object, usually referred to as OTCell
Object Trace on IuCs object, usually referred to as OTIuCs
Object Trace on IuPs object, usually referred to as OTIuPs
Object Trace on IuR object, usually referred to as OTIuR
Object Trace on IuBC object, usually referred to as OTIuBC

3.1 CORE NETWORK INVOKED CALL TRACE (CTA)
Used to trace one or several UE calls.
UEs selection based the IMSI or the IMEI.
Activation on Core Network.
Neither RRC dedicated measurements nor NBAP dedicated measurements
are traced.
3.1.1 DESCRIPTION
This type of session allows tracing:
one or several UE calls selected by the Core Network using either their IMSI
or IMEI.
one or several UE emergency calls
and one or several CallAbnormalityTraceDetectedCellInfo
3.1.2 ACTIVATION / CALLS SELECTION
A CTa session is permanently activated by an OMC with each RNC it controls. No
user action is needed for this at the OAM level; nevertheless the user has to access
the Core Network to enter the identifier (IMSI or IMEI) of the UE(s) that needs to be
traced.
3.1.3 START/STOP TRACING
The RNC starts tracing a UE call when it receives a RANAP CN INVOKE TRACE
message on the Iu SCCP connection dedicated to the UE.
A call is traced by a RNC:
as long as the considered RNC is the SRNS of the UE,
up to the reception of a RANAP CN DEACTIVATE TRACE message on the Iu
SCCP connection dedicated to the UE (see remark below),
as long as the session is activated and exists.
Remark: If Call Trace is activated for a same UE by both Core Network domains, then
the first received RANAP CN DEACTIVATE TRACE message deactivates
any CTa activity related to the UE.
Regarding Emergency calls, any RRC connection request received in the RNC with
the cause Emergency Call will be traced by the RNC as a CTa session, without
waiting the Core Network trigger: a UE emergency call is systematically traced in a
RNS even if a RANAP CN INVOKE TRACE message is not received.
Tracing for this RRC connection will end when the RRC connection is released by the
RNC
3.1.4 TRACED INFORMATION
It has to be noticed that only 3GPP R5 format is supported for these messages.
To prevent CTa from capturing too much trace data, the RRC dedicated
measurements and NBAP dedicated measurements are not traced.
See Annex 9.1 & 9.2

3.2 ACCESS INVOKED CALL TRACE (CTB)
Used to trace the calls related to only one UE. Possible to trace several UEs
by activating several CTb sessions.
UEs selection is based: on the IMSI or TMSI or P-TMSI or IMEI.
Activation at the OAM.
3.2.1 DESCRIPTION
A Call Trace B session provides data related to all calls initiated for a specified UE
during the session activation.
There is one and only one UE traced in a CTb session.
Therefore if n mobiles are to be traced simultaneously, then n sessions are created
(see Performances for details on the maximum number of CTb sessions that could
activated).
3.2.2 ACTIVATION/CALLS SELECTION
The UE identity specified at the OMC-R when creating a CTb session may be one of
all choices of the Initial UE identity IE supported by the RRC protocol listed below:
an IMSI
a TMSI
a P-TMSI
an IMEI
A call is traced by CTb as soon as the required UE identity is checked during a call
establishment.
The UE identification can occur on the receipt of one of the following signaling
messages:
the RRC message RRC CONNECTION REQUEST in which all four Initial
UE identities are possible
the RANAP message COMMON ID which supports only the IMSI
the RANAP message "UTRAN Relocation Request" which supports only the
IMSI
As soon as a positive check of the UE Id is completed, subsequent messages or
events related to the call may be recorded.
The RNC traces the UE call as long as:
the considered RNC is the SRNS of the UE,
the session is activated and exists.
Since most of the time, the first message of a call that carries the IMSI is the RANAP
COMMON ID, when a CTb session is activated with an IMSI, every
messages/events received/sent before the RANAP COMMON ID can not be traced.
In order to be able to record all the messages/events including the ones that occurred
before the RANAP COMMON ID the Call Trace initial UE identity learning
feature has been implemented.
For this feature the RNC memorizes every IMSI and associated TMSI (or P-TMSI) and
is then able start logging the data related to a specific UE as soon as it has positively
checked its TMSI.
In UA6.0, it is possible to configure UEs to report periodically the following
measurements in the call trace:
Intra-frequency measurement ( DL RSCP, DL EcNo)
Quality measurement (DL BLER)
UE internal measurement (UE Transmitted power, UE Rx-Tx time difference)
In order to get these measurements:
A new object RrcDedicatedMeasConfigForCallTrace has been created
under radioAccessService with the following parameters:
o qualityTypeMeasurementReportingRequired: set to TRUE
o intraFreqTypeMeasurementReportingRequired: set to TRUE
o ueInternalTypeMeasurementReportingRequired: set to TRUE
o reportingInterval: set to a valid value
The applied template must contain the following subfunctions:
o RRCDedicatedMeasurementCallTrace
o RRCDedicatedMeasurementReportAsn1
o RRCDedicatedMeasurementReportDecoded
These three subfunctions have been added in the following predefined templates:
standardTroubleShooting and heavyTroubleShooting.

See Annex 9.1 and 9.2

3.3 GEOGRAPHICAL CALL TRACE (CTG)
Used to trace calls established within a certain geographical area (one,
several or all the cells of a RNC).
Calls are traced even if moving outside the defined area.
Calls to be traced can be filtered according to their RRC establishment
cause.
The RNC is able to trace up to N calls per TMU (see Performances).
No UE identity is required.
3.3.1 DESCRIPTION
A Geographic Call Trace (CTg) session allows tracing calls established within a
geographical area.
Once established and traced, the calls may be traced even if the related UE move into
areas which do not belong to the defined geographical area.
When creating a CTg session, the user has to specify:
A geographic area; the geographic area may be a cell, a set of cells or all the
cells in the RNS.
The types of calls that will be traced within the session (based on the RRC
establishment cause).
Call Failure Trace is introduced in UA6.0 as part of CTg trace. It will provide a call
drop snapshot containing a set of information that helps to understand the drop
context. To have this drop snapshot, UE call failure trace function should be added
to the template.
Calls may be traced within a CTg session as soon as the trace session is activated
and exists.
The RNC starts tracing a call when:
The call has been established on a cell belonging to the defined area,
The call has been established with one of the selected RRC established
causes,
The RNC currently traces less than N calls on the TMU that carries the cell on
which the call has been established.
The call is then traced as long as:
The RNC remains as the SRNC of related call.
The session is active.
In UA6.0, it is possible to configure UEs to report periodically the following
measurements in the call trace as described for CTb session. Please, refer to chapter
3.2.3.


3.4 OBJECT TRACE (OT)

Used to trace events related network elements or interfaces and not to calls.
Call flows can not be rebuilt using Object Trace data.

3.4.1 DESCRIPTION
Object Trace sessions are used to provide Trace data related to a network elements
(cell/RNC) or network interfaces. Events are traced because they are attached to a
given cell or interface and not because they are attached to a call.

Depending on the OT session type, the session can be activated:
On a NE or a list of NEs
On a network interface or a list of network interfaces.

Events may be traced within an OT session as soon as the trace session is activated
and exists.
The events are traced on the specific NE or interface as long as the session remains
active


3.5 CALL TRACE NEIGHBORING (CTN)

Used to trace events related to calls mobility
Events related to traced calls are only logged when the mobile is inside the
defined area.
Calls to be traced can be filtered according to their RRC establishment
cause.
The RNC is able to trace up to N calls per TMU (see Performances).
No UE identity is required.

3.5.1 DESCRIPTION
Neighboring Call Trace (CTn) is used to monitor and optimize neighboring relations by
tracing information related to calls mobility. The RNC logs events related to a traced
call only when the call is inside the configured area (when the call leaves the area the
RNC stops tracing, and when the call comes back into the configured area, the RNC
resumes the tracing).

When creating a CTn session, the user has to specify:
A geographic area; the geographic area may be a cell, a set of cells or all the
cells in the RNS.
The types of calls that will be traced within the session (based on the RRC
establishment cause).

Calls may be traced within a CTn session as soon as the trace session is activated
and exists.
The RNC starts tracing a call when:
The call has been established on a cell belonging to the defined area,
The call has been established with one of the selected RRC established
causes,
The RNC currently traces less than N calls on the TMU that carries the cell on
which the call has been established.

The call is then traced as long as:
The RNC remains as the SRNC of related call.
The session is active.

4 FUNCTIONAL DESCRIPTION
4.1 RNC PERFORMANCES
Maximum number of filtering criteria (traceFilterList) in a trace session template: 1
Maximum number of trace records (traceRecordList) in a trace filter: 48
The RNC CNode trace capacity is limited on a TMU basis (see below).
Additionally, following rules apply to concurrent sessions:
RNC only allows simultaneously: 20 CTb, 1CTa, 1 CTg, 1CTn, 1 OTCell, 1
OTIuCs, 1 OTIuPs, OTIur and 1 OTIuBc sessions
At most 3 simultaneous calls can be traced on a PMC-RAB in a CTb session
At most 3 simultaneous calls can be traced on a PMC-RAB in a CTg session
CTb, CTg, CTn and OTCell are exclusive with debug CTb/CTg sessions.

4.1.1 CTA PERFORMANCES
There is exactly 1 CTa session per RNC at a time, automatically started (no user
action requested to create the session)
Number of templates associated to a CTa session: 3
Maximum number of calls (except emergency calls) traced in CTa in a RNC, per TMU
= 5
4.1.2 CTB PERFORMANCES
One and at the most only one "call debug" CTb session or 10 simultaneous "regular"
CTb sessions are accepted.
4.1.3 CTG PERFORMANCES
There is up to 1 CTg session per RNC at a time.
Maximum number of calls traced in CTg in a RNC, per TMU = 10.
Max_Ctg_Ndm_Comm_per_Tmu = 3 ((within the previous 10) calls that can be
selected for NDM (NBAP Dedicated Measurements) if required in Ctg session (based
on 1 session max Ctg per RNC as today).


4.1.4 CTN PERFORMANCES
Only 1 CTn session per RNC is allowed at a time.
Maximum number of calls simultaneously traced in CTn in a RNC, per TMU = 300.

4.1.5 OTCELL PERFORMANCES
There is only 1 Object Trace Cell session per RNC at a time. One, n or all cells of a
RNC can be simultaneously traced.
RNC shall have another limit on the maximum number of cells allowed per TMU. In
case that the number of cells which are configured in OTCELL are allocated and
handled on the same TMU is more than the maximum number of cells which are
allowed (as shown the in table below), RNC will not reject the session because it is too
late for it to do so. Instead, the TMU only initiates measurements for the maximum
number of cells allowed and ignores the rest of them at random. In this case, RNC will
not notify the user the list of cells which are ignored.

4.1.6 OTIU-CS PERFORMANCES
Only 1 OTIuCs session per RNC is allowed at a time.
Maximum number of RANAP PAGING messages traced by OTIuCs session = 8
messages/s per TMU.
4.1.7 OTIU-PS PERFORMANCES
Only 1 OTIuPs session per RNC is allowed at a time.
4.1.8 OTIUR PERFORMANCES
Only 1 OTIur session per RNC is allowed at a time.
4.1.9 OTIU-BC PERFORMANCES
Only 1 OTIuBc session per RNC is allowed at a time.
4.1.10 OVERLOAD MANAGEMENT
A CTa session is suspended when the RNC overload level reaches
OAM_OV_LEVEL_ MAJOR and is resumed when overload level goes below this
value.
A CTb session is suspended when the RNC overload level reaches
OAM_OV_LEVEL_ MAJOR and is resumed when overload level goes below this
value.
A CTg session is suspended when the RNC overload level reaches
OAM_OV_LEVEL_MAJOR without impact of the NDM configuration and is resumed
when overload level goes below this value.
A CTn session is suspended when the RNC overload level reaches
OAM_OV_LEVEL_ MINOR and is resumed when overload level goes below this
value.
An OTCell session is suspended when the RNC overload level reaches
OAM_OV_LEVEL_MAJOR and is resumed when overload level goes below this
value.
An OTIuCs, OTIuPs, OTIur or OTIuBc session is suspended when the RNC overload
level reaches OAMOV_LEVEL_MINOR and is resumed when overload level goes
below this value.


5 CALL TRACE ACTIVATION/DEACTIVATION
5.1 CALL TRACE WIZARD
The Call Trace Configuration Wizard application allows you to manage call trace sessions and trace
session templates.
The following types of trace sessions are managed by the Wizard:
Access Session
Cell Session
Geographical Session
Neighboring Session
Object Trace Session
Using the Wizard, you can create, delete and/or print records of trace sessions and trace session
templates. You can also create your own templates, based on predefined trace records.

5.1.1 LAUNCHING CALLTRACE WIZARD
You can reach the Call Trace Wizard application from the Performance menu of the NSP main
window (Performance/Radio Access/ Call Trace Configuration Wizard)
The following figure shows how to access the Call Trace Configuration Wizard command.

Figure 1 Call Trace Configuration Wizard command

The Call Trace Configuration Wizard option of the Radio Access command allows you to:
Create, delete and print reports of trace sessions
Create, delete and print reports of trace session templates
The following figures show the Call Trace Configuration Wizard window when the Call Trace Wizard
command is launched.

Figure 2 Call Trace Configuration Wizard window

Next button.

Next button.


.
5.2 HOW TO CREATE AN ACCESS SESSION (CTB)
5.2.1 CREATING ONE OR MORE ACCESS SESSIONS ON ONE RNC
1. Launch the Call Trace Configuration Wizard procedure.
2. Enable the Access session option and click the Next button
3. Enable the Create one or more Access sessions on single RNC option and click the Next
button.

A window appears with the "RNC and NBAP parameters" fields. The following figure is an example of
equipment and NBAP parameters selection:


4. Select in the "Equipment Identification" field the RNC to trace.
5. Enter a value (ms) in the NBAP Parameters fields. The values of SIR, TCP and RTT periods (ms)
must be:
Between 500 and 10000,
Multiplier of 500 (or "modulo" 500).
Click the Next button.

A window appears with the "Mobile identification and session parameters" fields. The following figure
is an example of user equipment and session parameters selection:


6. Select in the "Mobile identification" field, one of the following traceUeidType identities:
IMSI (6 to 15 decimal digits) Most used
IMEI (15 decimal digits)
TMSI (8 hexadecimal digits)
P-TMSI (8 hexadecimal digits)
7. Fill in the identifier according to the selected type. You can only type valid digits for mobile
identification.
8. Select or enter in the "Session Parameters" field:
Session Template: select a session template. By default, the template named
StandardTroubleShooting" is selected.
User Label: you have to enter a unique label.
Duration (min): you have to fill-in the session duration.
Note: 0 minute = infinite session duration
Session Note: you can write some personal information about the session.
Start Time: enter the lapse of time (in minutes) between the creation of the session
and its first activation. The default value 0 means that the session will start
immediately.
File Upload Size: enter the maximum size of the trace file. The maximum value is
1024. The default value is 512kb.
File Upload Period: enter the lapse of time before the trace file is closed and made
available. The default value is 15mn.

9. Click the Add button.
The parameters selected are verified. An error message is returned if:
The user label entered is already used.
No template has been selected.
The UE identifier is not typed correctly.
The UE equipment is already used in another trace session.
The session note exceeds the maximal number of characters.
The duration exceeds the maximum authorized value.
The file upload size value exceeds the maximum authorized value.
If the parameters are correct, the selected equipment appears in the list with session parameters.

10. Repeat steps 6 to 9 to add more mobiles to the trace session. You can create up to 10
simultaneous sessions on the selected RNC.
11. When you have finished your selection, click the Next button. A window appears with a summary
of the session parameters selected.

Figure 3 Summary of the session parameters

12. Click the Create button to confirm the access session creation.
Depending on the OAM version, there is two different ways to terminate the activation:
In OAM 5.1:
The "Call Trace Configuration Wizard" window appears with a summary result in the "Wizard status"
field.


Figure 4 Summary result in the "Wizard status" field.

13. Click the Finish button.
If an error occurs during the creation, a confirmation window is displayed which describes the error.
You can proceed with the creation in spite of the error or cancel the operation. If you select "Cancel",
all the objects already created are deleted (but no synchronization is performed after that). If the
operation is successful and the Launch report window on close option is enabled, the following
window appears with the results:

Figure 5 Launch report window

14. Click the Close button to close the window.

From OAM 5.2

The "Call Trace Configuration Wizard" window appears with a summary result and the session name
to activate in the "Wizard status" field.

The session Manager window appears also.

In the session manager window, choose the correct session name in the session list at left. Then in
the Actions click on the activation button and then launch. The progress and status of the activation
can be checked in bottom part of the right window.

After a successful activation, the session can be terminated by clicking the middle icon in the upper
left part.

13. Click the Finish button in the "Call Trace Configuration Wizard


Figure 6 Launch report window


5.2.2 CREATING AN ACCESS SESSION MULTIPLE RNCS

2. Enable the Access session option and click the Next button
3. Enable the Create single Access session on one or more RNCs option and click the Next
button.
A window appears with the RNCs and NBAP parameters fields. The following figure is an example of
equipment and NBAP parameters selection:

4. Enter a value (ms) in the NBAP Parameters fields.The values of SIR, TCP and RTT periods (ms)
must be:
Between 500 and 10000,
Multiplier of 500 (or "modulo" 500).

5. Click the Add button. The selected RNC appears in the list with the associated NBAP parameters.
6. Repeat steps 4 and 5 to add more RNCs to the trace session.
7. If you want to remove a RNC, select it in the list and click the Remove button.
8. When you have finished your selection, click the Next button.
A window appears with the "Mobile identification and session parameters" fields.


9. Select one of the following traceUeidType identities in the "Mobile Identification" field:
IMSI (6 to 15 decimal digits)
IMEI (15 decimal digits)
TMSI (8 hexadecimal digits)
P-TMSI (8 hexadecimal digits)
10. Enter the identifier, according to the selected type.
11. Select or enter in the "Session Parameters" field:
"TroubleShooting Light" is selected.
User Label: you have to enter a unique label.
Duration (min): you have to fill-in the session duration.
Note: 0 minute = infinite session duration
Session Note: you can write some personal information about the session.
and its first activation. The default value 0 means that the session will start
immediately.
1024. The default value is 512kb.
available. The default value is 15mn.

12. Click the Next button.
The UE identifier is not typed correctly.
The UE equipment is already used in another trace session.
The file upload size value exceeds the maximum authorized value.
If the parameters are correct, the selected equipment appears in the list with session parameters.
13. When you have finished your selection, click the Next button. A window appears with a summary
of the session parameters selected.
14.
In OAM 5.1: Click the Create button to confirm the access session creation.
From OAM 5.2: Click the Create button and Activate the session from the session manager
(See 5.1 for more details)


5.3 HOW TO CREATE A GEOGRAPHICAL SESSION
2. Enable the Geographical session option and click the Next button
A window appears with an "Equipment Selection" field

3. The "Call Trace Configuration Wizard" window appears with the following parts in the "Equipment
Selection" field:
"Available Equipments" displays the list of available targets in a Tree View or in a Flat View. The
view type is selected by the combo box at the top.
"Selected Equipments" displays the selected FDDCells.
Command buttons are located in the middle:
- Select ->: used to add the target(s) in the selected target list. If you select a non
terminal object (RNC or NodeB) in the Tree View, all FDDCells attached to this object
are also added.
- Select All ->: used to add all FDDCells
- Remove: used to remove the target(s) from the Equipment List
- Remove All: used to remove all FDDCells from the Equipment List
4. When you have selected the required equipment, click the Next button.
A window appears with the "RNC and NBAP parameters" fields. The following figure is an example of
equipment and parameters selection:


5. The "RNC and NBAP parameters" list displays the list of selected RNCs and RNCs containing
selected objects (CNodes or FDDCells).You can update the NBAP parameters of the RNCs displayed
in the list:
a. Select in the list the RNC that you want to update.
b. Modify the value of the "SIR Period", "TCP Period" and "RTT Period" fields. The
value must meet the following requirements:
it must be between 500 and 10000,
it must be a multiplier of 500 (or "modulo" 500).
You cannot modify the NBAP parameters of a RNC if you have not selected all the
objects contained in this RNC for the trace session.
c. Click the Update button.
d. Repeat steps a to c to update other RNCs.

6. When you have done the required modifications, click the Next button.


7. Enter the following information in the "Session Parameters" fields:
Call Type List: Types of call that will be traced within the session. Any combination of
call types above can be chosen, without any restrictions
"StandardTroubleShooting" is selected.
User Label: enter a unique label.
Duration (mn): enter the session duration. The maximum duration is 65535.
The default value 0 corresponds to infinite session duration.
Session Note: enter additional information about the session. The maximum number
of characters is 32.
and its first activation.
1024.
available.
8. Click the Next button. The parameters selected are verified. An error message is returned if:
A window appears with a summary of the session parameters selected
9.
10. Click the Finish button. If the Launch report window on close option is enabled, a new window
appears with the results.

5.4 HOW TO CREATE A CELL SESSION

2. Enable the Cell session option and click the Next button
3. Steps 3 to 5 from the Geographical session steps

"StandardTroubleShooting" is selected.
1024.
available.
6.
From OAM 5.2: Click the Create button and Activate the session from the session
manager (See 5.1 for more details)
7. Click the Finish button. If the Launch report window on close option is enabled, a new
window appears with the results.
8. Click the Close button to close the window

5.5 HOW TO CREATE AN OBJECT SESSION
2. Enable the IuCS or IuPS or IuR or IuBC session and click the Next button. The example
below is for a IuCS session.
A window appears with the "IuCs equipment identification and session parameters" fields.

Equipment Identification: displays the list of available equipments where the traces
will be taken.
"StandardTroubleShooting" is selected. When the objectif is tracing Nbap Common
Measurement, it is recommended to create a template including:
NBAPCommonMeasurementCallP and NBAPCommonMeasurementCallTrace
1024.
available.
5.

6. Click the Finish button. If the Launch report window on close option is enabled, a new
window appears with the results.
7. Click the Close button to close the window

5.6 HOW TO CREATE A CTN SESSION

2. Enable the Neighboring session option and click the Next button
A window appears with an "Equipment Selection" field

4. When you have selected the required equipment, click the Next button.

Call Type List: Types of call that will be traced within the session. Any combination of
call types above can be chosen, without any restrictions
Session Template: select NeighboringOptimization template.
1024.
available.
8. Click the Next button. A window appears with a summary of the session parameters selected
9.
10. Click the Finish button. If the Launch report window on close option is enabled, a new window
appears with the results.

5.7 HOW TO DELETE A SESSION
2. Enable the Delete a Trace Session option and click the Next button.
A window appears with the Trace Sessions and "Note" fields. This window displays all the existing
Call Traces with the following information:
External Session Id
User Label
Type
Date
RNC list
Duration (mn)
.

3. Select the Trace session(s) to delete. To delete several trace sessions at the same time, press the
"Ctrl" tab while selecting the trace sessions to be deleted.
4. Click the Next button

A window appears with information on the traces to be deleted in the "Trace Sessions" field.
The following figure is an example of confirmation of the trace session to be deleted:

5. Click the Delete button to confirm the access session deletion.

Depending on the OAM version, there is two different ways to terminate the activation:
In OAM 5.1:

The "Call Trace Configuration Wizard" window appears with a summary result in the Wizard status
field.
The following figure is an example with a summary result of the trace session to be deleted.


6.Click the Finish button.

The "Call Trace Configuration Wizard" window appears with the results if the "Launch report window
on close" option is enabled.
The following figure is an example with a summary result of the trace session to be deleted.

7. Click the Close button to close the "Call Trace Configuration Wizard: results" window.

In OAM 5.2

The "Call Trace Configuration Wizard" window appears with a summary result and the session name
to activate in the "Wizard status" field.


The session Manager window appears also.

In the session manager window, choose the correct session name in the session list at left. Then in
the Actions click on the activation button and then launch. The progress and status of the activation
can be checked in the bottom part of the right window.


After a successful activation, the session can be terminated by clicking the middle icon in the upper
left part.
6 CALL TRACE TEMPLATE MANAGEMENT
Session templates are proposed to ease session configuration by the OMC users who do not
need to specify the record types they want and the associated modes, anytime they create a
session.
A session template contains a trace type and a pre-defined list of record types with the associated
modes
W-NMS Call Trace Configuration Wizard is the tool to be used for templates management. It allows
to create (or delete) templates that will make only requested traces types to be provided by the
system. Typically, templates will be dedicated to troubleshooting or network design optimization,
but some custom templates may be defined for every specific usage.
A given number of pre-defined templates are delivered with the Call Trace Configuration Wizard.
They are dedicated to some typical usages that are described hereafter. The most used templates
are the following ones (See Annex 9.3 for more details):

1. "Heavy troubleshooting":
This template has to be used only in case of advanced investigations and associated session
should be activated only for a given period of time. Indeed, this template is very impacting for the
system as it requires almost all the possible traces. It will be typically used for CTb or CTg sessions
(with limited scope in terms of number of cells).

2. "Standard troubleshooting":
This template is the default one proposed by the Call Trace Wizard. It is intended to be used for
basic troubleshooting operations. It should provide all needed traces for "standard" investigations.
It will be typically used for CTb or CTg sessions (with limited scope in terms of number of cells).

3. "Call Monitoring":
This template is intended to be used to monitor a given area of the network, for example after some
optimization or maintenance operations have been performed. It will provide only basic traces
related to call management (establishment, release, failure). It will be typically used for CTb or
CTg sessions (with limited scope in terms of number of cells).

4. "Optimization":
This template is dedicated to engineering operations in order to obtain traces that can be used for
network or radio optimization. It will be typically used for CTb or CTg sessions (with limited scope in
terms of number of cells).

5. "Neighboring Optimization":
This template is dedicated to CTn session and contains all traces managed in this session. It can
be only associated to CTn session.
6.1 CREATE A TRACE SESSION TEMPLATE
1. Perform the How to launch the Call Trace Configuration Wizard procedure.
2. Enable the Manage the Trace Session Template option and click the Next button.
3. Enable the Create a Trace Session Template option and click the Next button.
A window appears with "Trace Session Template Parameters" fields. The following figure is an
example of template parameters selection:

4. Enter a unique name in the "Template Name" field.
5. The "Trace Record List" displays the list of available trace filters:
Select one or more records in the "Trace Record" list.
6. Select one of the following filter modes in the "Mode" field:
eventOnly
This mode provides the header including in particular: the traced sub-function, a record name, a
time-stamp, the related cell Id (if relevant), the related RNC Id.
ASN.1
This mode provides the header and the full record information, coded in ASN.1; this mode
applies only to UTRAN protocols PDUs (available for rrc, Iu, Iub, Iur 3GPP messages) and does
not apply to I-node
ctxfull
This mode provides a specific set of data in XDR format associated to the event not available
for event linked to Iu/Iur/iub/rrc ASN.1 messages, except for RRC Dedicated Measurements.
A window appears with the "Trace Filter Parameters" fields. The following figure is an example of trace
filter parameters selection

The list of trace records is verified. An error message is returned if:
The filter name entered is already used or no name has been entered.
The filter name exceeds the maximal number of characters or it contains the character ",".
No trace record has been retrieved by the system.

A window appears with a summary of the trace session template parameters selected:

11. Click the Create button to confirm the trace session template creation.



If the Launch report window on close option is enabled, a new window appears with the
results.


6.2 HOW TO DELETE A TRACE SESSION TEMPLATE
1. Perform the How to launch the Call Trace Configuration Wizard procedure.
2. Enable the Manage the Trace Session Template option and click the Next button.
3. Enable the Delete a Trace Session Template option and click the Next button.
4. Follow steps 4-8 from how to delete a session

7 CALL TRACE POST-PROCESSING TOOLS

7.1 CALL TRACE FILES COLLECTION

The XML CallTrace AccessSession (CTa) files are generated on PerfServer in the following directory:
/opt/nortel/data/utran/callTrace/onOAMdemand/<sessionId>

The XML geographical trace (CTg) files are generated on PerfServer in the following directory:
/opt/nortel/data/utran/callTrace/originatedFromGeographicalArea/<sessionId>

The XML neighboring trace (CTn) files are generated on PerfServer in the following directory:
/opt/nortel/data/utran/callTrace/ NeighboringTrace /<sessionId>

The XML ObjectTrace CellSession (OTCell) files are generated on PerfServer in the following
directory:
/opt/nortel/data/utran/objectTrace/cell/<sessionId>/<YYYYMMDD>/*

Example:

To retrieve the output files of an AccessSession (CTa) from the PerfServer:

1. Go to the directory: /opt/nortel/data/utran/callTrace/onOAMdemand

2. Here is the file hierarchy under the previous directory:

3. All the xml files of interest should be ftp-ed

4. Cleaning the files on the perf server needs to be done

<Session Number>
<date: yyyymmdd>
IMSI-<imsi #>
<tracekey #>
7.2 POST-PROCESSING TOOLS
In UA5.0, there are two engineering tools that post-process the Call trace files:
RFO (Radio Frequency Optimization): internal tool for engineering
WQA (Wireless Quality Analysis): product tool

RFO
UMTS/HSDPA RF Optimizer is an internal software tool used to analyze and optimize Alcatel
Lucents UMTS/HSDPA wireless networks. UMTS/HSDPA RFO analyzes:
Log files collected from mobiles,
Call Traces collected at RNC through WMS
NodeB logs collected at base stations.

It analyses the data from those different physical files to create various statistics, charts and
views of the data.

The Call Trace files types supported are:
Control Node (CN) & Interface Node (IN) (xml) from UTRAN 3.2, 4.1, 4.2,
5.0 and 6.0
CTa, CTb, CTg, CTn, OTCell
For more information about the tool, you can refer to:
RFO UMTS/HSxPA Overview & Training
WQA
Wireless Quality Analysis is the tool to be used for CTn traces post-processing.
It offers a web-based interface with a server running on PC hardware. Two different steps are part
of the post-processing activity:
data collection and parsing
data reporting

Reporting is performed on data organized in WQA database. Both pre-defined reports and custom
reports can be run.
Following reports are available with the tool:
Summary
o Summary report (data and statistics per cell)
Soft handovers
o Soft handovers report
o Soft handover failures report

o Detected cells report
o HSXPA relations report
Inter-frequency
o Inter-frequency handovers report
3G to 2G handovers
o 3G2G CS inter-RAT handovers report
o 3G2G PS inter-RAT handovers report
2G to 3G handovers
o 2G3G CS inter-RAT handovers report
o 2G3G PS inter-RAT handovers report

WQA is also the tool to post-process the call failure trace snapshots. It produces reports built from
Call Failure Trace data block content issued from one or several CTg sessions.
It is possible to customise the report by using filters like: cell id, failure cause value, call type

For more information about the tool, you can refer to:
WQA User Guide (Ctn part) (NN-20500-128)

8 ABBREVIATIONS AND DEFINITIONS
8.1 ABREVIATIONS
ALCAP Access Link Control Application Protocol
ASN.1 Abstract Syntax Notation 1
ATM Asynchronous Transfer Mode
CN Control Node
CM XML Configuration Management XML
CP Control Processor (in the Interface Node)
CT Call Trace
CTa Call Trace a
CTb Call Trace b
CTg Call Trace g (Geographic Call Trace)
CTn Call Trace n (Neighboring Call Trace)
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
IN Interface Node
NBAP Node B Application Part
OMU Operation and Maintenance Unit
OT Object Trace
RANAP Radio Access Network Application Part
RL Radio Link
RNC Radio Network Controller
RNS Radio Network Subsystem
RNSAP Radio Network Subsystem Application part
RRC Radio Resource Control
SRNC Serving RNC
TMSI Temporary Mobile Subscriber Identity
TMU Traffic Management Unit
UE User Equipment
UTRAN Universal Terrestrial Radio Access Network
XDR eXternal Data Representation standard (IETF RFC 1832)
WQA Wireless Quality Analyzer
XML Extensible Markup Language

9 ANNEX
9.1 CN FUNCTIONS AND SUB-FUNCTIONS TRACEABLE PER
SESSION TYPE
CTa CTb CTg CTn OT-
Cell
OT-IU
CS/PS
OT-
IUbc
OT-
IUR
RRC
RRCDedicatedTraffic x X X
RRCCommonTraffic X
RRCDedicatedMeasurement
CallP
X X
RRCCommonMeasurement X
ReportAsn1
X X
RRCDedicatedMeasurementRep
ortDecoded
X X
CallTrace

X X

UE
UEActiveSetManagement X X X

UEHSDPAManagement X X X
UEEDCHManagement X X X
IUb
NBAPDedicatedTraffic X X X
NBAPCommonTraffic X
NBAPDedicatedMeasurementCallP X X X
NBAPCommonMeasurementCallP X
NBAPDedicatedMeasurementCallTrace
NBAPCommonMeasurementCallTrace
QAAL2IubDedicated X X X
Iu
RANAPDedicatedCS X X X
RANAPCommonCS X
RANAPDedicatedPS X X X
CTa CTb CTg CTn OT-
Cell
OT-IU
CS/PS
OT-
IUbc
OT-
IUR
RANAPCommonPS x
QAAL2IuDedicated X X X
DTAP
DTAPRRCDedicated X X X
DTAPRANAPDedicatedCS X X X
DTAPRANAPDedicatedPS X X X
Error Sig Plane
NBAPError X X X X
RANAPError X X X X
RNSAPError X X X x
RRCError X X X x
SABPError X
PCAPError
Snapshot

CommunicationStartSCCPConnection X X X
CommunicationStartRRCConnection x X X
CommunicationStartRadioAccessBearer x X X
CommunicationStartRLServingRNC X X X
CommunicationStartRLDriftRNC X X X
CommunicationEndRRCConnection X X X
CommunicationEndSCCPConnection X X X
CommunicationEndRadioAccessBearer X X X
CommunicationEndRLServingRNC X X X
CommunicationEndRLDriftRNC X X X
CommunicationDropSCCPConnection X X X
CommunicationDropRadioBearer X X X
CommunicationDropRadioLink X X X
IUr
RNSAPDriftDedicated
RNSAPServingDedicated X x X
QAAL2IurServingDedicated X X X
RNSAPServingCommon x
CTa CTb CTg CTn OT-
Cell
OT-IU
CS/PS
OT-
IUbc
OT-
IUR
RNSAPDriftCommon X
RNSAPServingDedicatedMeasurement X X X
QOS
AlwaysOn X X X
RlcMacIrmSchedulingDowngrading X X X
QoSiRMPreemption X X X
iRMSchedulingDowngrade
x X X
iRMSchedulingUpgrade
X X X
RadioBearerRateAdapatation X x X
IuPC
UPCGPSDataAssistance x x X X
SABP
CBMessageOperation X
BroadcastServiceAreaLevelOperation x
CTn
CTnIntraRNCHO X
CTnInterRNCHO X
CTnRRC X
CTnInterFrequencyHO X
CTn2g3gHO X
CTnInterRATHO X
CTnSRNSRelocationIncoming X
CTnSRNSRelocationOutgoing X
CTnDetectedCellReport X
Call Debug
CallDebug_SWES_ All_Events X
CallDebug_SWES_ALL_Received_Interna
l_Messages
X
CallDebug_SWES_ALL_Step0_Messages X
CTa CTb CTg CTn OT-
Cell
OT-IU
CS/PS
OT-
IUbc
OT-
IUR
CallDebug_UE_CALL_All_Messages X
CallDebug_UE_CALL_Step0_Messages X
CallDebug_UE_RRC_ALL_Messages X
CallDebug_UE_RRC_Step0_Messages X
CallDebug_UE_RRC_Step1_Messages X
CallDebug_UE_RRM_ALL_Messages X
CallDebug_UE_RRM_Step0_Messages X
CallDebug_UE_RRM_Step1_Messages X
CallDebug_IU_CALL_All_Messages X
CallDebug_IU_CALL_Step0_Messages X
CallDebug_IU_CALL_Step1_Messages X
CallDebug_NOB_CALL_All_Messages X
CallDebug_NOB_CALL_Step0_Messages X
CallDebug_RNC_CALL_All_Messages X
CallDebug_RNC_CALL_Step0_Messages X
CallDebug_RNC_CALL_Step1_Messages X
CallDebug_IUR_CALL_All_Messages X
CallDebug_IUR_CALL_Step0_Messages X
CallDebug_IUR_CALL_Step1_Messages X
CallDebug_IUPC_All_Messages X
CallDebug_IUPC_Step0_Messages X
CallDebug_IUPC_Step1_Messages X


9.2 IN FUNCTIONS AND SUB-FUNCTIONS TRACEABLE PER
SESSION TYPE
CTa CTb CTg CTn OT-Cell OT-IU
CS/PS
OT-
IUbc
OT-
IUR
Power ctrl.
RlcDchUlCrci X
UlSirSetPoint X
UlDecision X
RRC User Plane
RRCTFCControl X X
FP
IubFPTADch x X
UserPlane Binary
CtblCfgCallP
CtblCfgMobility
CtblCfgDataPath
CtblCfgRadioLink
CtblCfgMeasurement
CtblCfgCallPDump
CtblCfgDataPathDump
RLC
DlRlcDch x x
UlRlcDch x x

9.3 TEMPLATES AND THEIR PRE-DEFINED LIST OF RECORD
TYPES AND ASSOCIATED MODES
traceFilter id List of associated traceRecord ids traceModeList
HeavyTroubleShooting RRCDedicatedTraffic
RRCCommonTraffic (*)
RRCDedicatedMeasurementCallP
RRCDedicatedMeasurementCallTrace
RRCDedicatedMeasurementReportAsn1
RRCDedicatedMeasurementReportDecoded
RRCCommonMeasurement (*)
UEFull
NBAPDedicatedTraffic
NBAPCommonTraffic (*)
NBAPCommonMeasurementCallP (*)
NBAPDedicatedMeasurementCallP
NBAPCommonMeasurementCallTrace (*)
QAAL2IubCommon (*)
QAAL2IubDedicated
RANAPFull
DTAPFull
ErrorFull
CommunicationFull
RNSAPFull
QoSFull
IUPCGPSDataAssistance
SABPFull
RLCFull
PowerControlFull
RRCTFCControl
IubFPTADch
ctxFull + asn1
StandardTroubleShooting RRCDedicatedTraffic
RRCCommonTraffic (*)
RRCDedicatedMeasurementCallP
RRCDedicatedMeasurementCallTrace
RRCDedicatedMeasurementReportAsn1
RRCDedicatedMeasurementReportDecoded
RRCCommonMeasurement (*)
UEFull
QAAL2IubDedicated
RANAPFull
DTAPFull
ErrorFull
CommunicationFull
RNSAPFull
QoSFull
IUPCGPSDataAssistance
UlSirSetPoint
UlDecision
ctxFull + asn1
CallMonitoring QoSFull
CommunicationFull
UEFull
ctxFull
traceFilter id List of associated traceRecord ids traceModeList
Optimization RRCFull
UEFull
NBAPCommonMeasurementCallTrace (*)
NBAPDedicatedMeasurementCallTrace
RANAPDedicatedCS
RANAPCommonCS (*)
RANAPDedicatedPS
RANAPCommonPS (*)
DTAPFull
CommunicationFull
RNSAPFull
QoSFull
RLCFull
PowerControlFull
ctxFull + asn1
Neighboring optimization CTnFull ctxFull

END OF DOCUMENT

Call Trace User Guide V3.0

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Call Trace User Guide V3.0

Caricato da

Copyright:

Formati disponibili

Call Trace User Guide

Document number: UMT/IRC/APP/022962

2007 Alcatel-Lucent, All Rights Reserved

Potrebbero piacerti anche