Call Trace Engineering Guide LR13.3

Call Trace Engineering Guide (LR13)
Grace Sserunkuuma ( Adapted from Renato Nascimento )

Wireless PU / MGR TIS / ONE’S / KPI & Engineering Support
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
AGENDA
1. Introduction
2. Call Trace Operations Overview
3. Sessions Manager Operations Overview
4. Call Trace Specifications
A. Geographical Call Trace (CTg)
B. Access Invoked Call Trace (CTb)
C. Real Time Call Trace (RTCT)
D. Call Trace Neighbouring (CTn)
E. Object Trace (OT)
5. Manage Call Trace Templates

6. Call Trace Analysis
7. Performance Aspects
8. References
2
1. Introduction
3
Introduction
Call Trace User Guide
• The purpose of this document is to describe the different Call Trace (CT)
options and to provide the means to operationally launch and post-
process these traces.
 Call Trace, if used improperly, can have impact in the operator’s network performance,
so it is important to understand which trace to collect and how to complete the
procedures successfully.
• CT Engineering Guide specifies a collection of traces which can be collected:
 Geographical Call Trace (CTg);
 Access Invoked Call Trace (CTb);
 Real Time Call Trace (RTCT);
 Neighbouring Call Trace (CTn);
 Object Trace (OT) – Cell, IuCS, IuPS, IuR, IuBC.
• 3 steps will be discussed under the CT procedure:
 To activate the CT through the OMC GUI;
 To download the CT from the WMS server ;
 To post-process the CT.
4
Introduction
Call Trace Configuration Wizard
• Under the WMS, 3 main applications can

be used to manage the Call Trace:
1. Call Trace Configuration Wizard can be used to:
• Manage Call Trace Session (Create, Delete, List Call
Trace Sessions, List Traced UEs);
• Manage the Trace Session Template (Create, Delete,
List Trace Session Templates).
Introduction
Sessions Manager
2. Sessions Manager can be used to activate/de-activate Call Trace Sessions

created/deleted in the Call Trace Configuration Wizard.
Introduction
Command Manager
3. Command Manager can be used to check relevant commands launched in the
WMS and information related to their Status, Progression and further to Save and
Print Logs, View Reports, etc.
2. Call Trace
Operations
Overview
8
Call Trace Operations Overview 1 Under the WMS, select
Create – Trace Sessions Performance > Radio
Access > Call Trace
Wizard for UMTS > Next >
2 Click Manage the Call

Trace Session > Next >
1
3 Click Create Call Trace
Sessions
2 Caution: Further actions are needed to create and

activate the call trace. Confirm specificities under each
Call trace and Session Manager sections, respectively.
Note: basic WICL

commands can also be
used to create a call trace,
however this is not the 3
purpose of this document.
Call Trace Operations Overview 1 Click Manage the Call
Delete– Trace Session
Trace Session > Next >
2 Click Delete Call Trace

Sessions > Next >
3 Select the correct Session

2 ID > Next > Delete >
1
4 Confirm the Session
Deletion > Finish.
Caution: Further actions are needed to de-activate

the session. Confirm specificities under the Session 4
Manager section (next section – slide 15).
Call Trace Operations Overview 1 Select Manage the Call
List – Call Trace Sessions and Traced UEs
Trace Session.
2 Click List Call Trace

Sessions (or List Traced
Ues) > Next >
3 Confirm the activated call

1 trace sessions in the list of
Session Ids.
3
3. Sessions
Manager
Operations
Overview
12
Call Trace 1 Open the Sessions
Activation – Session Manager
Manager. In Active
Sessions and Summary &
Action, select the session
created.
1 2 Under the Actions window,

select Activation.
3 Select Launch.
1 Confirm the successfull
4
launch of the trace
(Progress 100%).
3
2
4
Call Trace
De-activation – Session Manager 1 Open the Session
Manager > Active
Sessions > select
ct_delete_UserLabel_...
4 2 Select Summary and

Action & Activation
3 Select Launch and wait for

the Progress to show
100%.
1
2
4 You can terminate the
3 sessions selecting Active
Sessions > Session List >
<session_name>.
14
4. Call Trace
Specifications
15
Call Trace Specifications
Description
Geographical Call Trace
• For tracing calls over a defined geographical area;
CTg • Geographical area can be one, several or all cells of one or more RNCs;
• Calls are traced as soon as the RNC remains as the SRNC and session is active.
Access Invoked Call Trace

• For tracing calls related to specific UE identities (IMSI, TMSI, P-TMSI, IMEI);
CTb • One CTb session can be activated for one UE in several RNCs;
• Several CTb sessions can be activated for several UEs on one RNC.
Real Time Call Trace

• Similar as CTb still can be used for tracing and follow the call flow “real-time”;
RTCT • Up to 2 RTCT can be launched;
• Not possible to have RTCT and “regular” CTb coexisting together.
Neighbouring Call Trace

• Used to monitor and optimise neighboring relations;
CTn • For tracing all calls moving inside the defined area;
• Calls are traced as soon as the RNC remains as the SRNC and session is active.
Object Trace
• Used to trace events related to network elements or interfaces (not to calls);
OT • Several type of OT: Cell, IuCS, IuPS, IuR, IuBC;
• Call flows can not be rebuilt using OT data.
16
4A. Geographical
Call Trace (CTg)
17
1 Select Geographical
Geographical Call Trace (CTg) session and Next >
Creation – Trace Session 2 Select the RNC(s) /

NodeB(s) / FDDCell(s)
to trace under Available
Equipments
3 Click Select ->

1
4 Click Next.>
2
3
Available Equipments:
 displays the list of available equipments (RNCs, NodeBs, FDDCells) which are available for the call trace.
Selected Equipments:
 displays the list of selected equipments to be traced.
18
Geographical Call Trace (CTg) 1 Select (only if required)
Creation – RRC and NBAP dedicated measurements
RRC or NBAP dedicated
measurements
2 Select Update
3 Click Next >
Caution:
 If not required, both
RRC and NBAP dedicated
1 measurements should not
be set since they create
additional load in the RNC.
2
3
With RRC dedicated meas, UEs will report periodically: NBAP dedicated meas will include:
 IntraFreq Required: PSC, DL RSCP, DL EcNo  SIR: RLSetId, SIR
 Quality Required: DL BLER  TCP (Transmit Code Power): Rlid, TxCodePwr
 ueInternal Required: UE Tx Power  RTT (Round Trip Time): Rlid, RTT
RRC meas. interval specifies the UE reporting time (ms). SIR, TCP and RTT Period must be up to 10000 (exclusive).
19
Geographical Call Trace (CTg) 1 Select Call Type List
Creation - Session Parameters 2 Enter a unique User Label
3 Select Session Template
4 Give it a Duration (min)
5 Enter a Session Note
Session parameters:
1
 Call Type List: used to confine to tracing to the RRC
Establishment Cause as specified in this field;
2
 User Label: uniquely identifies the session;
4  Session Template: By default, StandardTroubleshooting

is used, but other templates can be selected;
5  Duration (min): identifies the session duration (0
corresponds to infinite). A positive value must be introduced.
 Session Note: used to associate notes to the session
(can be filled identical to the Session Template description);
 Start Time (min): indicates the waiting time before the
creation of the session and its activation (0 means that the
3 session starts immediately);
 File Upload Size (kb): maximum size of trace file to be
uploaded;
File Upload Size (kb): waiting time before the trace file is
closed and made available.
Note: UEcallFailureFull (for CFT) is captured for all the Call Types (not the only the ones selected for CT).
Geographical Call Trace (CTg)
Creation – Last checks
1 Confirm the created
session attributes.
2 Select Create
3 Select Finish
4 Select Close.
4
5 Activate the session as
described in the Session
1
Manager section (slide
14).
3
Caution:
 After these steps, the session has been created but not yet activated. Activation is done as presented in slide 14.
 If there are warnings, confirm in the Command Manager that there is no negative impact from the session activation.
4B. Access Invoked
Call Trace (CTb)
22
Access Invoked Call Trace (CTb) 1 Select Access Session >
Creation – Trace Session Next >
2 Select one of the two:

- Create one or more Access
sessions on single RNC
1 - Creat single Access session
on one or more RNCs.
 Create one or more Access sessions on single RNC: select this option to create N CTb sessions to trace N mobiles
simultaneously.
 Create single Access session on one or more RNCs: select this option to trace one mobile (one CTb session) on
several RNCs.
23
Access Invoked Call Trace (CTb) 1 If required, select RRC
and NBAP dedicated
Creation – Dedicated Measurements & KPI Monitoring measurements.
2 If required, select
Advanced
configurations… >
1
2
 Realtime reporting triggers Real Time Call Trace
as demonstrated in the coming slides.
 Advanced configurations can be used to trigger
KPI monitoring (limited to 6 cells), however this
feature is only for internal troubleshooting.
24
Access Invoked Call Trace (CTb) 1 Select the Mobile
Identification (IMSI,
Creation – UE identification TMSI, IMEI, P-TMSI)
Enter the value

2
corresponding to the
selected identifier
3 Enter the Ctb session

parameters.
1 2
4 Click Add.
 The RNC memorizes the IMSI and

3
associated TMSI/P-TMSI and is able
4 to start log the messages/events
including the ones occurred before the
RANAP Common ID message (where
IMSI is retrieved)
Session parameters:
 UE Identification: IMSI, TMSI, IMEI, P-TMSI can be used for the UE dedicated session.
 User Label, Session Template, Duration (min), Session Note, Start Time (min), File
Upload Size (kb), File Upload Period (min): same as described for CTg (see slide 21).
25
Access Invoked Call Trace (CTb) 1 Confirm the created session
attributes.
2 Select Create
3 Select Finish
4 Select Close.

4 Manager section (slide 14).
1
3
2
5
Caution:
 After these steps, the session has been created but not yet activated.
26
4C. Real Time
Call Trace (RTCT)
27
Real Time Call Trace (RTCT) 1 Execute the same procedure as
for the CTb creation
Creation
2 Select Realtime reporting
1 3 Insert Reporting IP address (IP

address of the computer
hosting the Real Time Call
Trace Analyzer Tool) > Next.
4 Select RealTimeCallTrace
under Session Template.
5 Insert the UE identifier, and

3 other Session parameters >
Add > Next.
2
 Real Time reporting is available with

CTb. It is similar to CTb except that the
5
traced data is stored and displayed in a
specific real-time CT analyzer (through UDP
session). It allows to follow a UE “real-time”. 4
 CTb can not be activated simulaneously
with RTCT.
Real Time Call Trace (RTCT) 1 Confirm the created
Creation – Last Checks
session attributes
2 Select Create
3 Select Finish
4 Select Close.
3
2
29
Real Time Call Trace (RTCT) 1 For the session activation,
follow the procedure as
Activation – Session Manager described in the Session
Manager section (slide 14).
2 The RTCT window

automatically open.
 Note that you can also open the RTCT window under:
Performance > Radio Access > Realtime Call Trace
30
Real Time Call Trace (RTCT) 1 Observe the RTCT for the
given UE in the window.
Trace Session – RT Capture
 Maximum 2 UEs can be traced

simultaneously.
 Collection, storage and
1 analysis of messaging can be
done with the dedicated GUI on
WMS client.
 For each UE, the following information is retrieved from the RNC:
Timestamp: message timestamp (date hh:mm:ss.ms)  RNC: Message Header
 Failure: marked if containing a failure cause ASN.1: marked if field is present and not empty
 Message Name: recorded message name  IMSI: UE identifier
 Function: retrieved from callPHeader Tracekey: Call identifier
 Active Set / Services: set of active cellId + psc (calculated) / current active services
31
Real Time Call Trace (RTCT) 1 Select the intended message
(Message Name).
Trace Session – RT Capture Analysis
2 Search specific Field Name
inside the Message.
4
3 Confirm the Current Active
Set & Services currently
used.
1 4 Save the RT trace.
 Under the Current Active Set & Services

window, the following information is gathered:
 UTRAN cellId: active cell Id is
displayed. If the active set cannot be
computed, “UNKNOWN” is displayed.
 Psc: is the active set cell’s primary
3 scrambling code.
 Ref: shows a checkmark on the call’s
2 reference cell.
 in bold green the services allocated
are shown and the grayed out diplay the
unallocated.
 The Message Details panel shows several fields (protocol/bytes/decoded contents/etc.) for each Message gathered.
32
Real Time Call Trace (RTCT)
Trace Session – RT Recording Tips
Under File:
 Save capture: saves the RTCT displayed in the current panel, overwriting the current capture file. RTCT is saved in XML format.
 Save capture as: allows the possibility to save the RTCT in the WMS machine or local machine in case of remote connection.
 Open capture: loads a capture file, adding the content recorded to the current captured message list. (attached one RTCT)
 Clear capture : deletes current captured CT records, deleting the current panel and removing the CT records captured in it.
Under View:
 Show measurement results: measurements (e.g. RRCMeasReport) are presented under gray colour.
Under Configuration:
 Enable /Disable auto save: enables/disables auto-saving periodically.
4D. Neighbouring
Call Trace (CTn)
34
Neighbouring Call Trace (CTn) 1 Select Neighbouring
session and Next >
Creation – Trace Session
2 Select the RNC / NodeB /
FDDCell under Available
Equipments
3 Click Select ->
4 Click Next.>
1
2
3
35
Neighbouring Call Trace (CTn)
Select Call Type List
Creation - Session Parameters 1
2 Enter a unique User Label
3 Set theSession Template to

NeighbouringOptimization
4 Give it a Duration (min)
5 Enter a Session Note

1
2
3
4
5
Session parameters:
 User Label, Session Template, Duration (min), Session Note, Start Time (min), File
Upload Size (kb), File Upload Period (min): same as described for CTg (see slide 21).
36
Neighbouring Call Trace (CTn) 1 Confirm the created session
attributes
2 Select Create
3 Select Finish
4 Select Close.

4
1
3
2
Caution:
 After these steps, the session has been created but not yet activated.
37
4E. Object Trace
(OT)
38
Object Trace Specifications
Description
Object Trace Cell
• The OTCell session provides trace data related to the management of one or
OTCell several cells. The trace collection is not done per call (so, no tracekey is
recorded). The RNC supports only one OTCell session.
Object Trace IuCS

• The OTIuCs session provides records related to common (i.e. not linked to a
OTIuCS given call) RANAP messages on IuCs interface.
• The RNC supports only one OTIuCs session at a time.
Object Trace IuPS

• The OTIuPs session provides records related to common RANAP messages on
OTIuPS IuPs interface.
• The RNC supports only one OTIuPs session at a time.
Object Trace IuR

• The OTIuR session provides records related to common (i.e. not linked to a
OTIuR given call) RNSAP messages on Iur interface.
• The RNC supports only one OTIuR session at a time.
Object Trace IuBC

• The OTIuBc session provides records related to common (i.e. not linked to a
OTIuBC given call) SABP messages on IuBc interface.
• The RNC supports only one OTIuBc session at a time.
39
1 Select Cell session and
Object Trace Cell (OTCell) Next >
Creation – Trace Session 2 Select the RNC(s) /

NodeB(s) / FDDCell(s) to
trace under Available
Equipments
3 Click Select ->
4 Click Next.>
1
2
3
40
Object Trace Cell (OTCell) 1 Select (only if required) NBAP
Common measurements
Creation – NBAP common measurements (RTWP/TCP) and select Update.
2 Click Next >
3 Set the session parameters (see

slide 31 for description) > Next >.
NBAP common measurements include:

 TCP : Transmit Code Power
 RTWP: Received Total Wide Band Power
Note: NBAP Common measurements are not supported into CTb & CTg sessions but are available for OTCell.
Important: When the objectif is tracing Nbap Common Measurement, it is recommended to create a template including:
NBAPCommonMeasurementCallP and NBAPCommonMeasurementCallTrace
41
Object Trace Cell (OTCell) 1 Confirm the created session
Creation – Last checks attributes.
2 Select Create
3
3 Confirm the operation was
sucessfull created.

Caution:
 After these steps, the session has been created but not yet activated. Activation is done as presented in slide 14.
RNC supports only one OTCell session. Only Control Plane traces are available in OTCell.
42
Object Trace Iu (OTIuCS, OTIuPS, OTIuR, OTIubBC)
Creation – Trace Session
1 Select Iu session
and Next >
2 Select the interfaces

/equipments to trace
and Session
Parameters > Next.>
3 Select > Create.

1
2
3
 In case of CBS services usage, the CBC, located in the Core Network, is
connected to the RNC through the IuBC interface that uses the same possible
backhauling solutions as Iu interfaces over ATM.
43
5. Manage
Call Trace
Templates
44
Managing Call Trace Templates
Pre-defined templates
• Session templates are used to ease session configurations in the WMS.

The session template contains a list of record types.
• Pre-defined templates are built for optimization or troubleshooting,
still a specific template may be created with its own record list.
• A given number of pre-defined templates are delivered with the Call
Trace Configuration Wizard. The pre-defined session templates are:
• Standard Troubleshooting: For basic troubleshooting operations and “standard”
investigations. Typically used for Ctb or CTg.
• Heavy Troubleshooting: For “deep” investigations. This template is very impacting
for the system.
• Call Monitoring: Used typically to monitor a given area of the network, e.g. after
optimization or maintenance operations. Provides basic traces related to call
management (establishment, release, failure).
• Optimization: Used mainly for network and radio optimization.
• Neighbouring Optimization: dedicated for CTn session.
• Real Time Troubleshooting: dedicated for “real-time” CTb session.
45
Pre-defined templates – StandardTroubleshooting+CFT
TraceFilter id List of associated traceRecord ids (22 ids) TraceModeList

RRCDedicatedTraffic
RRCCommonTraffic (*)
RRCDedicatedMeasurementCallP
RRCCommonMeasurement (*)
RRCDedicatedMeasurementReportAsn1
RRCDedicatedMeasurementReportDecoded
UEFull
NBAPDedicatedTraffic
NBAPCommonTraffic (*)
NBAPCommonMeasurementCallP (*)
NBAPDedicatedMeasurementCallP
StandardTroubleShooting ctxFull + asn1
NBAPDedicatedMeasurementCallTrace
QAAL2IubDedicated
RANAPFull
DTAPFull
ErrorFull
CommunicationFull
RNSAPFull
QoSFull
IUPCGPSDataAssistance
UlSirSetPoint
UlDecision
(*) Traced only in OTx sessions.
Note: UECallFailureFull is not standard is this template.

Pre-defined templates – HeavyTroubleshooting
RRCDedicatedTraffic
RRCCommonTraffic (*)
RRCDedicatedMeasurementCallP
RRCCommonMeasurement (*)
RRCDedicatedMeasurementReportAsn1
RRCDedicatedMeasurementReportDecoded
UEFull
NBAPCommonMeasurementCallTrace (*)
HeavyTroubleShooting QAAL2IubCommon (*) ctxFull + asn1
QAAL2IubDedicated
RANAPFull
DTAPFull
ErrorFull
CommunicationFull
RNSAPFull
QoSFull
IUPCGPSDataAssistance
SABPFull
RLCFull
PowerControlFull
RRCTFCControl
IubFPTADch

Note: UECallFailureFull is not standard is this template.
Pre-defined templates – CallMonitoring and (Neighbouring) Optimization
TraceFilter id List of associated traceRecord ids TraceModeList

QoSFull
CallMonitoring CommunicationFull ctxFull
UEFull
RRCFull
UEFull
NBAPCommonMeasurementCallTrace (*)
RANAPDedicatedCS
Optimization ctxFull + asn1
RANAPCommonCS (*)
RANAPDedicatedPS
RANAPCommonPS (*)
DTAPFull
CommunicationFull
RNSAPFull
QoSFull
RLCFull
PowerControlFull
Neighbouring
CTnFull ctxFull
Optimization

Pre-defined templates – RealTimeTroubleshooting
RRCDedicatedTraffic CommunicationStartRRCConnection
RRCDedicatedMeasurementCallP CommunicationStartSCCPConnection
RRCDedicatedMeasurementCallTrace CommunicationStartRadioAccessBearer
RRCDedicatedMeasurementReportAsn1 CommunicationStartRLServingRNC
RRCDedicatedMeasurementReportDecoded CommunicationStartRLDriftRNC
UEActiveSetManagement CommunicationEndRRCConnection
UEHSDPAManagement CommunicationEndSCCPConnection
UEEDCHManagement CommunicationEndRadioAccessBearer
UEDCHManagement CommunicationEndRLServingRNC
UEFDPCHManagement CommunicationEndRLDriftRNC
UESupervisionTimers CommunicationDropSCCPConnection
UEStateChangeNotification CommunicationDropRadioBearer
Real Time NBAPDedicatedTraffic CommunicationDropRadioLink
ctxFull + asn1
TroubleShooting NBAPDedicatedMeasurementCallP RNSAPServingDedicated
NBAPDedicatedMeasurementCallTrace QAAL2IurServingDedicated
QAAL2IubDedicated RNSAPServingDedicatedMeasurement
RANAPDedicatedCS AlwaysOn
RANAPDedicatedPS RlcMacIrmSchedulingDowngrading
QAAL2IuDedicated QoSiRMPreemption
DTAPRRCDedicated iRMSchedulingUpgrade
DTAPRANAPDedicatedCS iRMSchedulingDowngrade
DTAPRANAPDedicatedPS RadioBearerRateAdapatation
NBAPError Preemption
RANAPError
RNSAPError
RRCError
49
Save and import template
• Besides the pre-defined templates, other Call Trace templates can be imported
and saved under the WMS path (see attachments):
• opt/nortel/data/utran/CTSessionTemplates
Note:
 It is not possible to modify a template. If some changes are needed it is required to create a
new template.
50
Managing Call Trace Templates 1 Select Manage the Trace
Session Template > Next >
Create a template
2 Select Create a Trace
3 Enter a Template Name
4 Selec the Mode List

3 1
5 Select the Trace Record Ids
to be used > Next >
4
6 Confirm the template and
select Create.
2
6
 CtxFull implicitly includes/contains the CT tracing mode asn1 and therefore

also implicitly includes/contains the CT tracing mode eventOnly.
Delete a template
2 Select Delete a Trace
3 3 Select the Template Name to

delete > Next
1 4 Confirm with Delete
5 Click Finish and confirm

Operation Successfull.
2
5
List templates
2 Select List Trace Session
Templates > Next >
3 Check the list of Templates

available. Select one if you
3 want to print a report.
1 4
Select Print.
 Each Call Trace template is made of a single traceFilterList which can contain up to 96 trace records (traceRecordList).
6. Call Trace
Analysis
54
Call Trace Analysis
Retrieve traces recorded from WMS server
• The Call Trace files can be obtained under the following WMS paths:
/opt/nortel/data/utran/callTrace/originatedFromGeographicalArea/<sessionId>/
CTg <date>/
CTb /opt/nortel/data/utran/callTrace/onOAMdemand/<sessionid>/<date>/<UEid>/
CFT /opt/nortel/data/utran/callTrace/callFailure/<date>/<RNCuserlabel>/
CTn /opt/nortel/data/utran/callTrace/NeighboringTrace/<RNCuserlabel>/<date>/
OTCell /opt/nortel/data/utran/objectTrace/Cell/<sessionId>/<date>/
OTIuCS /opt/nortel/data/utran/objectTrace/Iu-CS/<sessionId>/<date>/
OTIuPS /opt/nortel/data/utran/objectTrace/Iu-PS/<sessionId>/<date>/
IuR /opt/nortel/data/utran/objectTrace/Iur/<sessionId>/<date>/
IuBC /opt/nortel/data/utran/objectTrace/Iubc/<sessionId>/<date>/
 The traces need to be retrieved via FTP from the OMC and55afterwards cleaned from the server.
 RTCT can be saved and further copied to the—laptop.
ALCATEL-LUCENT INTERNAL PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
Call Trace Analysis
Post-processing tools and user guides mostly available to TAC Teams with
License keys for the Analysis Software
• The CFT can be processed with eDAT/WTA and CFT reader.
• The Call and Object Trace files can be processed with eDAT/WTA.
• The CTn+CFT can be processed with WCT/WQA:
• CFT reader: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=58185459&objAction=browse&sort=name&vi
ewType=1
• eDAT: http://navigator.web.lucent.com/
• WTA: https://download.support.alcatel-lucent.com/cgi-bin/Download.pl?hier_id=132831
• CTA: http://mlgsz.uk.lucent.com/~radsweb/az4/qscan/CTA/CTA.html
• CFT presentations: https://wcdma-ll.app.alcatel-
lucent.com/livelink/livelink.exe?func=ll&objId=57344700&objAction=browse&sort=name&vi
ewType=1
• CFT/WCT user guide: (TBC)
• WQA: (TBC)
56
Note: Without disregarding the other tools, next section will focus on the WTA product, due to the fact that this is a new tool
intended for the customer. eDAT and WTA are similar,
ALCATEL-LUCENT stillPROPRIETARY
— INTERNAL for internal use, TOeDAT
— USE PURSUANT COMPANYis more complete than WTA.
INSTRUCTION
7. Performance
limitations
57
Performance Limitations
Limitations by session, Cnode, Inode & Restrictions NDM: NBAP Dedicated Measurements
RDM: RRC Dedicated Measurements
Number of
LIMITATIONS simultaneous
CNode INode Restrictions
(*) sessions (per
RNC)
2 or 3 CTb calls processed in CTb and RTCT
1 call/CTb
CTb 1 (CTb Debug PMC-RAB (rest are are mutually
10 calls/TMU
Session) ignored). exclusive.
RTCT 2 - - -
8-12 calls/TMU CTb, CTg, CTn,

3 calls processed in PMC-
120 calls/RNC OTCell are
RAB, approximately 80 in
CTg (*) 1 3 calls/NDM and 5 calls/RDM exclusive with
total (out of 120 calls
(depending on reporting debug CTb/CTg
from CNode).
intervals). sessions.
CTg and CTn
CTn 1 300 calls/TMU Not supported. are mutually
exclusive.
Individual cell ids or all. Some OTCell and CTn
OTCell (*) 1 of the configured cells can be N/A. are mutually
enabled with NDM. exclusive.
OTIuCS,
Individual IuCS, IuPS or
OTIuPS, 1 N/A. -
neighbouring RNC ids or all.
OTIuR (*)
OTIuBC (*) 1 By the TRLA instance OMU N/A. -
(*) More information related to TCP/RSSI can be found in [FN]. 58


Call Trace Engineering Guide LR13.3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Call Trace Engineering Guide LR13.3

Uploaded by

Copyright:

Available Formats

Call Trace Engineering Guide (LR13)

Grace Sserunkuuma ( Adapted from Renato Nascimento )

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

5. Manage Call Trace Templates

• Under the WMS, 3 main applications can

2. Sessions Manager can be used to activate/de-activate Call Trace Sessions

2 Click Manage the Call

2 Caution: Further actions are needed to create and

Note: basic WICL

2 Click Delete Call Trace

3 Select the correct Session

Caution: Further actions are needed to de-activate

2 Click List Call Trace

3 Confirm the activated call

1 2 Under the Actions window,

4 2 Select Summary and

3 Select Launch and wait for

Access Invoked Call Trace

Real Time Call Trace

Neighbouring Call Trace

Creation – Trace Session 2 Select the RNC(s) /

3 Click Select ->

3 Click Next >

Creation - Session Parameters 2 Enter a unique User Label

3 Select Session Template

4 Give it a Duration (min)

5 Enter a Session Note

4  Session Template: By default, StandardTroubleshooting

2 Select one of the two:

Enter the value

3 Enter the Ctb session

 The RNC memorizes the IMSI and

5 Activate the session as

1 3 Insert Reporting IP address (IP

5 Insert the UE identifier, and

 Real Time reporting is available with

2 The RTCT window

 Maximum 2 UEs can be traced

1 4 Save the RT trace.

 Under the Current Active Set & Services

3 Click Select ->

2 Enter a unique User Label

3 Set theSession Template to

4 Give it a Duration (min)

5 Enter a Session Note

5 Activate the session as

Object Trace IuCS

Object Trace IuPS

Object Trace IuR

Object Trace IuBC

Creation – Trace Session 2 Select the RNC(s) /

3 Click Select ->

2 Click Next >

3 Set the session parameters (see

NBAP common measurements include:

4 Activate the session as

2 Select the interfaces

3 Select > Create.

• Session templates are used to ease session configurations in the WMS.

TraceFilter id List of associated traceRecord ids (22 ids) TraceModeList

(*) Traced only in OTx sessions.

Note: UECallFailureFull is not standard is this template.

(*) Traced only in OTx sessions.

TraceFilter id List of associated traceRecord ids TraceModeList