IMSI MSC Call Trace

(Invoke Trace)

Motorola Jordan
December 11, 2003

Global Telecommunications Solutions Sector

Table of contents
Summary...............................................................................................................................3
Description............................................................................................................................3
Trace Data Display ................................................................................................................5
K1205 Trace ...........................................................................................................................5
Database Parameters..............................................................................................................6
Standards ..............................................................................................................................6

2/7

Global Telecommunications Solutions Sector

Summary
The MSC Initiated IMSI & IMEI Call Trace feature allows a Mobile Station (MS) to be tracked as it
moves across the network. The MSC invokes call tracing at the BSS over the A interface. The BSS
collects call trace data for either subscriber (IMSI) or equipment (IMEI) based upon the invoking
message. Call Trace data is then forwarded to the OMC via an event interface and stored in a file,
with the data formatted as per GSM 12.08 recommendations.
This document explains the feature as seen from the BSS side. The usage from MSC side is not
within the scope of this document.

NMC
(OSS)

CALL TRACE EVENTs

(GSM 12.08 format)
forwarded from OMC

MS

CALL TRACE EVENTs

(ASN.1 format) forwarded
from NEs

OMC
RXCDR
OMC Core
Services

GSM NETWORK

Call trace triggered

from MSC

Q3 Interface
(CMIP over OSI)

Q3 Agent
(Mediation
Device)

CALL TRACE
EVENT LOGS

CALL TRACE EVENTs

converted to GSM 12.08 format.
Stored in unique logfile at the
OMC for further analysis.

MSC

Description
Call trace feature at the BSS collects both A-interface and Air interface call data and place it at the
OMC. However, the trigger event that instructs the BSC to start a trace is limited to the
information available at the BSS.
As IMSI or EMEI may not be visible by the BSS, MSC trace provides a good solution to tracing
specific call or user related call information.
On the required event, the MSC sends an Invoke Trace (Phase 2) or a Trace Invocation (Phase 1)
request to the BSS. A call trace invoked by a MSC request always continues when it leaves the
BSS (its current scope).
Once an Invoke Trace message is received from the MSC, the trace is started at the BSS. The trace
stops when the call is terminated or when it leaves the BSS. The trace data is stored at the OMC
under ct_logs directory and can be easily distinguished from BSS traces from the file name. The
file name has the format ct_MSC_xxxxxxxxxx_xxxxx_xxxxxxx.xxxxxxxx.
At the BSS, disp_trace command shows a trace has been started as in the sample below:

3/7

Global Telecommunications Solutions Sector

MMI-RAM 0118 -> disp_trace

Start of Trace Report
Trace Reference:
Scope:
Trigger Event:
any call)
Trace Data:
MS Power
Data during handover only:
Interval (x480ms):
Mode:
Trigger enabled time:
Total calls to be traced:
Trace beyond scope:
Destination of trace data:
Triggering enabled:

270001h
416 01
555 (022Bh) 6789 (1A85h)
All (call origination, handover, or
Basic, RSS, BSSMAP, DTAP, Abis, RR,
No
1
SCCP number=033a40h
Not specified
1
Yes
OMC
Yes

Total calls currently traced

---------------------------Trace Reference
Count
------------------270001h
1
Call Trace Flow Control Status
-----------------------------Automatic Flow Control: Not Halted for this BSS.
Automatic Flow Control: De-activated by BSS.
Automatic Flow Control: De-activated by OMC.
End of Report
MMI-RAM 0118 ->
The trace call event message sent to the OMC from the BSS contains the following data:

The time that the last trace call record in the event was generated.
Cause field which identifies whether the event is due to a RF loss trace or a trace call.
In the case of an RF loss trace event, the value of the cause field will contain the reason for
the RF Loss.
Multiple RSS and/or BSSMAP/DTAP data records.
The BSS buffers 9 RSS data records and 12 BSSMAP/DTAP data records before sending a
notification event.
Device instance - the carrier (RTF) that the call was on when the trace call data was
generated.
MS ID.
Current cell id (the cell that the call was in when the trace call data was generated).
SCCP number assigned to the call being traced.
Circuit identification code (CIC) used to connect to the MSC.
Destination local reference (DLR).
Current interference band.
Requested interference band.
Channel description.

4/7

Global Telecommunications Solutions Sector

Trace Data Display

Trace data can be displayed using Motorola Call Trace Product, CTP. Both Air interface and Ainterface data can be displayed using CTP. A sample screen is shown below. All messages can be
exported to a text file.

K1205 Trace
The following call has been captured by K1205 protocol analyser. Notice the Invoke Trace, MSIT
message that followed the CR message.
3:59:13
3:59:14
3:59:14
3:59:14
3:59:14
3:59:14
3:59:14
3:59:15
3:59:19
3:59:22
3:59:22
4:00:13
4:00:13
4:00:13
4:00:13
4:00:13
4:00:13

PM,910,300
PM,008,762
PM,020,257
PM,392,799
PM,609,423
PM,705,380
PM,725,373
PM,691,908
PM,946,064
PM,007,791
PM,355,705
PM,184,303
PM,533,839
PM,595,798
PM,697,465
PM,747,668
PM,756,834

1:G
1:H
1:H
1:G
1:G
1:H
1:H
1:G
1:H
1:H
1:G
1:H
1:G
1:H
1:G
1:H
1:G

(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16
(Rx):16

MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2
MTP-L2

MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU
MSU

5/7

SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP
SCCP

CR
CC
DT1
DT1
DT1
DT1
DT1
DT1
DT1
DT1
DT1
DT1
DT1
DT1
DT1
RLSD
RLC

BSSM
BSSM
BSSM
BSSM
DTAP
DTAP
BSSM
BSSM
DTAP
DTAP
DTAP
DTAP
DTAP
BSSM
BSSM

CL3I
MSIT
CICMD
CICMP
SETUP
CPROC
ASREQ
ASCMP
ALERT
CONNECT
CONACK
RELEAS
RELCMP
CLCMD
CLCMP

Global Telecommunications Solutions Sector

Database Parameters
The following database parameters impact MSC trace call:

call_trace_options - Enables, reserves space for, or disables Phase 1 and Phase 2 MSC
trace calls for the entire BSS.
Valid range:
0 to 100, and 255
0 to 100
The percentage of traces reserved for
MSC initiated traces on a per LCF basis.
255
MSC invoked call traces disabled.
Recommended value 20

ct_flow_control_hi_level - Specifies the percentage of trace call OML buffer space that
may be used before trace call flow control is enabled. When this limit is reached, the BSS
parameter ct_flow_control_bss_enabled is set to 1. (This level is not used to disable flow
control.)
Valid range:
20 to 100
Recommended value: 60

ct_flow_control_lo_level - Specifies the percentage of trace call OML buffer space that
may be used before flow control is enabled. When this limit is reached, the BSS
parameter ct_flow_control_bss_enabled is set to 0 (this level is not used to disable flow
control).
Valid range:
0 to 80
Recommended value: 20

ct_flow_control_msc_trace - Specifies whether or not MSC traces are allowed when flow
control is enabled.
Valid range
0 or 1
0
MSC traces are allowed while flow is restricted.
1
MSC traces are not allowed while flow is restricted.
Recommended value 0

ct_flow_control_bss_enabled - Specifies whether the BSS has enabled or disabled flow

control.
Valid range
0 to 80
Recommended value 20

Suggested Usage of the Feature

The feature can be used for different purposes as:

QVoice problems tracking

Drive test call setup and handover failures tracking
Specific customer complaints tracking

6/7

Global Telecommunications Solutions Sector

Standards

GSM 4.08:
GSM 8.08:
GSM 8.58:
GSM12.08:
Data).

Mobile Radio Interface Layer 3 Specification.

BSS-MSC Layer 3 Specification.
BSC-BTS Layer 3 Specification.
Subscriber and Equipment Trace Specification (less Handover type Trace

****************

7/7