Specification of Location Data Record File Structure

Specification of Location Data Record File Structure
TABLE OF CONTENTS
1 INTRODUCTION ......................................................................................................................................... 3
2 2G RECORD STRUCTURE ........................................................................................................................ 3
2.1 2G RECORD FORMAT ................................................................................................................................... 3
2.2 2G RECORD ATTRIBUTE DESCRIPTION ......................................................................................................... 6
3 3G RECORD STRUCTURE ...................................................................................................................... 21
3.1 3G RECORD FORMAT ................................................................................................................................. 21
3.2 3G RECORD ATTRIBUTE DESCRIPTION ....................................................................................................... 26
4 RM (ROAMING) RECORD STRUCTURE ............................................................................................. 32
4.1 RM RECORD FORMAT ................................................................................................................................ 32
4.2 RM RECORD ATTRIBUTES DESCRIPTION .................................................................................................... 34
4.2.1 Scenario ............................................................................................................................................. 34
4.2.2 Start Date and time ............................................................................................................................ 35
4.2.3 End Date and time ............................................................................................................................. 35
4.2.4 OPC ................................................................................................................................................... 35
4.2.5 DPC ................................................................................................................................................... 35
4.2.6 Calling no. ......................................................................................................................................... 35
4.2.7 Called no. .......................................................................................................................................... 35
4.2.8 MSISDN ............................................................................................................................................. 35
4.2.9 Serving MSC ...................................................................................................................................... 35
4.2.10 Backward calling number: ................................................................................................................ 36
4.2.11 IMSI ................................................................................................................................................... 36
4.2.12 IMEI...................................................................................................... Error! Bookmark not defined.
4.2.13 ODB General Data ............................................................................................................................ 36
4.2.14 SSCode Set ......................................................................................................................................... 36
4.2.15 Service Key ........................................................................................... Error! Bookmark not defined.
4.2.16 Supported Camel Phases ................................................................................................................... 36
4.2.17 Error code ......................................................................................................................................... 37
4.2.18 TCAP Abort Cause ............................................................................................................................ 37
4.2.19 SCCP Return Cause .......................................................................................................................... 37
4.2.20 Violation ............................................................................................................................................ 37
4.2.21 Number of dialogues.......................................................................................................................... 37
4.2.22 PC0- PC1-… PCN ............................................................................................................................. 37
4.2.23 User Error Reason ............................................................................................................................ 37
4.2.24 NoOfSCCPMsg .................................................................................................................................. 37
4.2.25 SccpMsgLength.................................................................................................................................. 37
4.2.26 Linkset Id ........................................................................................................................................... 38
2
1 INTRODUCTION
This document specifies the Location Data Record File Structure.
2 2G RECORD STRUCTURE
A 2G record describes a 2G Transaction and consists of an ASCII line of comma-separated attributes.
The date and time attribute of 2G records within the file refers to the completion time of the transaction
and it is always in the interval [start time, end time].
2.1 2G Record Format

The table below describes the attributes of 2G record fields with regards to length and format. If
applicable it also includes a sample.
In the 2G record, the parameters are “,” separated. If a parameter is unavailable and no meaningfully
default value can be applied to it, the undefined value is represented by the special character “_”.
2G record fields whose mandatory parameters have value "_" can be admitted due to various
protocol/network errors.
Since ‘,’ in the contents of the fields can cause ambiguity with the field separator and might be not
supported, it is guaranteed that the ‘,’ chars are replaced by a default char (e.g. blank char ‘ ‘).
Parameter values can have fixed or variable length. Variable-length values are described with the term
“Up to” in the column “Field Format”. Fixed-length numerical values are to be padded with leading 0’s.
# Name Field Format (ASCII) Opti Sample Record field Default

onal name (Record Value
field No in
[2G_RECORD])
1 Type 2G N 2G TYPE
2 Scenario Up to 2 chars, hex N 05 SEQTYPE
3 Start Date and 12 chars, hex N 00ED1FE133F3 StartTimeStmpSec +
time StartmsPart
4 End Date and 12 chars, hex N 00ED1FE13416 EndTimeStmpSec +
time EndmsPart
5 OPC 6 chars, hex N 001234 LABEL_OPC
6 DPC 6 chars, hex N 001235 LABEL_DPC
7 Call Type Up to 2 char, hex Y 01 CALL_TYPE _
8 Called no.1 Up to 28 digit (hex) Y 4540590017 CALLED_NO _
9 Called NAI 2 char, hex Y 04 DTAP_CALLED_NO _
A
10 Calling number1 Up to 28 digit (hex) Y 4540620234 CALLING_NO _
11 Calling NAI 2 chars, hex Y 01 DTAP_CALLING_N _
OA
12 CIC 4 chars, hex Y 0234 LABEL_CIC _
13 Speech/Data 1 char, hex Y 1 SPEECH_DATA_IN _
Indicator D
14 Assigned Up to 2 char, hex Y 01 CHANNEL_TYPE _
Channel Type
1Each number digit is output as one hexadecimal digit. So, number digits from 0 to 9 are output as they
are in decimal format. The hexadecimal format is used to include non-numerical info in the call number,
e.g. an "F", which indicates the number termination in some cases.
3
field No in
[2G_RECORD])
15 Speech Up to 2 char, hex Y 02 SPEECH_TYPE _
Version/Data
Rate
16 IMEI1 Up to 16 digit (hex Y 2380273387206 IMEI _
ending with F) 571F
17 IMSI1 Up to 16 digit (hex Y 2380203001206 IMSI _
ending with F) 571F
18 TMSI 8 chars, hex Y 34F2EE01 TMSI _
19 1st LAC 4 chars, hex Y 0453 LAC_1 _
20 1’st cell id 4 chars, hex Y 0453 CELL_ID1 _
21 2nd LAC 4 chars, hex Y 0453 LAC_2 _
22 2’nd cell id 4 chars, hex Y 0413 CELL_ID2 _
23 Set-up time 8 chars, hex Y 00006A89 RESP_TIME _
24 Holding time 8 chars, hex Y 00006A89 HOLD_TIME _
25 Ringing time 8 chars, hex Y 00003449 WAIT_TIME _
26 Conversation 8 chars, hex Y 00006A89 CONV_TIME _
Time
27 Complete Time 8 chars, hex N 00006A89 COMPL_TIME _
28 Assignment Time 8 chars, hex Y 00006A89 ASSIGNMENT_TIM _
E
29 TCH Assignment 8 chars, hex Y 00006A89 TCH_ASSIGN_TIME _
Time
30 Paging Time 8 chars, hex Y 00006A89 PAGING_TIME _
31 --- --- - - - _
32 No of Handover Up to 2 chars, hex Y 02 NO_OF_HNDOPER 0
Performed F
33 RR Cause Up to 2 chars, hex Y 34 BSSRM _
(BSSRM RECORD_RR_CAU
RECORD) SE
34 Cause (BSSRM Up to 4 chars, hex Y 73 BSSRM _
RECORD) RECORD_CLEAR_
CAUSE
35 --- --- - - - _
36 --- --- - - - _
37 Reject Cause Up to 2 chars, hex Y 12 MM_REJ_CAUSE _
(DTAP MM)
38 Cause (DTAP Up to 2 chars, hex Y 23 CC_RELEASE_CAU _
CC) SE
39 --- - - - - _
40 --- - - - - _
41 3rd LAC 4 chars, hex Y 0453 LAC_3 _
42 3’rd cell id 4 chars, hex Y 0453 CELL_ID3 _
43 HO Required Up to 4 chars, hex Y 2 HO_REQUIRED_CA _
Cause USE
44 HO Failure Up to 4 chars, hex Y 5 HO_FAIL_CAUSE _
Cause
45 Old_MCC1 Up to 3 chars, hex Y 39 OLD_MCC _
46 Old_MNC1 Up to 3 chars, hex Y 335 OLD_MNC _
47 Old_Lac 4 chars, hex Y 0453 LAC_OLD (89) _
48 Assig_CipherMo Up to 4 chars, hex Y 1 BSSRM _
de Reject Cause RECORD_ASSIGN_
CIPHER_REJ_CAU
SE
49 No_Handover_F Up to 2 chars, hex Y 1 NO_OF_HNDO_FAI _
ailure L
50 Disconnection Up to 2 chars, hex Y 3 DISCONNECTION_ _
Cause CAUSE
51 1st_HandoverRef 2 char, hex Y e1 HANDOVER_REF1 _
erenceNo
52 2nd_HandoverRe 2 char, hex Y e2 HANDOVER_REF2 _
ferenceNo
4
field No in
[2G_RECORD])
53 TransactionId 2 char hex Y 03 TRANSACTION_ID _
54 IMEISV1 Up to 16 char, hex Y 1234567890123 IMEISV _
45
55 Old TMSI Up to 8 char, hex Y b80123aa TMSI_OLD _
56 IMSI detach 2 char, hex Y 1 IMSI_DETACH_STA _
status TUS
57 Location update Up to 1 char, hex Y 2 LOC_UPD_TYPE _
type
58 Cause Location Up to 2 char, hex Y 0 CAUSE_LOCATION _
59 End message Up to 2 char, hex Y a END_MSG _
60 End message Up to 2 char, hex Y c END_MSG_CAUSE _
cause
61 Sequence Up to 2 digits, dec N 2 SEQUENCE_TERMI _
Terminate Cause NATION_CAUSE
62 SCCP Release Up to 3 digits, dec Y 1 REL_CAUSE _
Cause
63 Called SSN Up to 3 digits, dec Y 3 CALLED_SSN _
64 HO Complete 8 chars, hex Y 00006A89 HO_COMPLETE_TI _
Time ME
65 HO Request Up to 4 chars, hex Y 0002 HO_REQUEST_CA _
Cause USE
66 HO Required Up to 4 chars, hex Y 0002 HO_REQUIRED_RE _
Reject Cause JECT_CAUSE
67 Assignment Up to 4 chars, hex Y 0001 ASSIGN_FAIL_CAU _
Failure Cause SE
68 CM Service Up to 2 digits, dec Y 21 CM_SERV_REQ_TY _
Request Type PE
69 Authentication Up to 4 chars, hex Y AUTH_FAIL_CAUSE _
Failure Cause
70 --- --- - - - _
71 --- --- - - - _
72 --- --- - - - _
73 No of DTMF bits Up to 2 chars, hex 01 NUM_OF_DTMF_BI _
TS
74 --- --- - - - _
75 --- - - - - _
76 --- - - - - _
77 --- - - - - _
78 --- - - - - _
79 --- - - - - _
80 --- --- - - - _
81 1st Channel Type Up to 2 char, hex Y 01 CHAN_TYP1 _
2nd Channel Up to 2 char, hex Y 01 CHAN_TYP2 _
82 Type
1st Radio Up to 2 char, hex Y 01 TIME_SLOT1 _
83 Timeslot
2nd Radio Up to 2 char, hex Y 01 TIME_SLOT2 _
84 Timeslot
85 1st ARFCN Up to 4 chars, hex Y 0001 ARFCN1 _
86 2nd ARFCN Up to 4 chars, hex Y 0001 ARFCN2 _
87 S-RNTI Up to 8 char, hex Y F34 SRNTI _
88 --- --- - - - _
89 --- --- - - - _
90 --- --- - - - _
BSSRM Up to 8 char, hex Y 1 BSSRM _
RECORD RECORD_MESSAG
91 Message Flag E_FLAG
MM Message Up to 8 char, hex Y 1 MM_MESSAGE_FL _
92 Flag AG
CC Message Up to 8 char, hex Y 1 CC_MESSAGE_FLA _
93 Flag G
5
field No in
[2G_RECORD])
94 --- - - - - _
SS Message Flag Up to 8 char, hex Y 1 SS_MESSAGE_FLA _
95 G
CC Operation Up to 6 digits, dec Y 12 CC_OPER_CODE_1 _
96 Code 1
CC Operation Up to 6 digits, dec Y 12 CC_OPER_CODE_2 _
97 Code 2
SS Operation Up to 6 digits, dec Y 12 SS_OPER_CODE_1 _
98 Code 1
SS Operation Up to 6 digits, dec Y 12 SS_OPER_CODE_2 _
99 Code 2
100 SS error code Up to 4 char, hex Y A64C SS_ERR_CODE _
Major or Minor 2 binary digits N 00 MAJOR_OR_MINO _
101 R
102 New Lac 4 chars, hex Y 0453 LAC_NEW _
103 Serving Lac 4 chars, hex Y 0453 SERVING_LAC_ID _
104 Serving Cell id 4 chars, hex Y 0453 SERVING_CELL_ID _
105 Serving RNC id 4 chars, hex Y 0453 SERVING_RNC_ID _
106 Call Setup Time 8 chars, hex Y 00006A89 CALL_SETUP_TIME _
107 PCM Usage Time 8 chars, hex Y 00006A89 PCM_USAGE_TIME _
MS Power Class Up to 4 chars, hex Y 1 MS_POWER_CLAS _
108 S
Paging Response Up to 4 chars, hex Y 1 PAGING_RESPONS _
109 E
PCM Multiplex Up to 3 chars, hex Y 043 LABEL_CIC (bits a- _
110 Number k)
PCM Active Up to 2 chars, hex Y 01 LABEL_CIC (last 5 _
111 Timeslot least significant bits)
112 MSISDN Up to 22 digits Y 393331111111 MSISDN _
Is Inter System Up to 2 chars, hex Y 01 IS_INTERSYS_HO_ _
Handover OCCURED
113 Occurred
SDCCH Drop Up to 4 chars, hex Y 1 SDCCH_DROP_FLA _
114 Flag G
Frequency band Up to 4 chars, hex Y 1 FREQENCY_BAND _
used _USED
115
116 PagingCause Up to 2 digits, dec Y 1 PAGING_CAU SE _
Voice Service Up to 8 char, hex Y 56f1 VOICE_SERVIC _
Time E_END_TIME -
VOICE_SERVIC
117 E_START_TIME
Table 1 – Attributes of 2G records
2.2 2G Record Attribute Description

Scenario:
This is the 2G Transaction Type record field. This parameter determines the communication procedure
type.
It can be LDR file:

4 - Location Update
19 – IMSI Detach
Start Date and time: Starting time of the procedure in milliseconds
6
This is the time stamp for start of the transaction2. The time stamp is UTC time milliseconds since 1 Jan
1970 0:00. This field is computed using the StartTimeStmpSec and StartmsPart RECORD fields.
End Date and time:

This is the time stamp for completion of the transaction2. The time stamp is UTC time milli seconds since
1 Jan 1970 0:00. This field is computed using EndTimeStmpSec and EndmsPart RECORD fields and
the kind of timeout violation.
OPC:
Originating Point Code field is filled from the first SCCP message in the sequence (Ref Q704, 2.2.3).
DPC:
Destination Point Code field is filled from the first SCCP message in the sequence (Ref Q704, 2.2.3).
Call Type
The field indicates the Bearer Information Transfer Capability. This field will be filled from the first ‘Call
confirm’ or ‘Call proceeding’ or ‘Emergency Set-up or Modify’ or ‘Modify complete’ or ‘Modify Refect’ or
‘CC establishment confirm’ or ‘Setup’ ( 3GPP TS 24.008 V 4.12.0, 10.5.4.5)
Called number
This field represents the called number.
CC
If scenario is MO/MT Call then this field represents address filled from the first Setup message in the
sequence.
Called NAI
Nature of Address Indicator i.e. international number, national number, network specific number etc.
CC
sequence.
Calling number
This field represents the calling number.
CC
sequence.
Calling NAI
Nature of Address Indicator i.e. international number, national number, network specific number etc.
CC
If sequence type is MO/MT Call then this field represents address filled from the first Setup message in
the sequence.
CIC
Circuit Identification Code.
This field is filled from the last Assignment request or Assignment complete or Handover request or
Handover request ack Reset circuit or Reset circuit ack or Circuit group block or Circuit group blocking
ack or Circuit group unblock or Circuit group unblocking ack or VGCS/VBS assignment request or
VGCS/VBS assignment result or Channel circuit ack or Change circuit ack message in the sequence.
3GPP TS 48.008 V 4.10.0, 3.2.2.2
Speech/Data Indicator
Indicates the type of call 3GPP TS 48.008 V 4.10.0 v7.16.0 Section 3.2.2.11 (octet 3)
Indicates the type of call that the BSS requires from MSC to determine the required radio resources.
This field will be filled from the first Assignment request or Handover Request or VGCS/VBS assignment
request or VGCS/VBS assignment result message in the sequence.
The list of values this field can assume is:
2 (End Time – Start Time) gives the total length (or duration) of the dialogue.
7
1 - Speech
2 - Data
3 - Signalling
Assigned Channel Type

Channel Type. Indicates the channel type proposed by the MSC in the Assignment Request or assigned
by BSS in the Assignment Complete if the assignment is successful.
If the message Assignment complete or Handover request acknowledge or VGCS/VBS assignment
result, Complete Layer 3 information contains a Chosen channel field then this field over writes the value
previously filled. If the sub field Channel mode is 0000, it is changed to 1111 in the record value.
3GPP TS 48.008 V 4.10.0 Section 3.2.2.11 (octet 4) or 3GPP TS 48.008 V 4.10.0 Section 3.2.2.33 (octet
2)
0 SDCCH or Full rate TCH channel Bm or Half rate TCH channel Lm

1 SDCCH
2 SDCCH or Full rate TCH channel Bm
3 SDCCH or Half rate TCH channel Lm
8 Full rate TCH channel Bm
9 Half rate TCH channel Lm
10 Full rate preferred, changes allowed
11 Half rate preferred, changes allowed
26 Full rate preferred, changes not allowed
27 Half rate preferred, changes not allowed
15 Preference between the permitted speech versions, changes allowed
31 Preference between the permitted speech versions, changes not allowed
32 Full rate TCH channels in a multislot configuration, changes allowed; 1 TCHs
48 Full rate TCH channels in a multislot configuration, changes not allowed;1 TCHs
49 Full rate TCH channels in a multislot configuration, changes not allowed; 2 TCHs
248 Full rate TCH channel Bm
Speech Version/Data Rate

Indicates a description of the speech coder or Data rate with Transparency Indicator.
3GPP TS 48.008 V 4.10.0 Section 3.2.2.11 (Octet 5) or 3GPP TS 48.008 V 4.10.0 Section 3.2.2.51
(octet 2)
Indicates the type of call that the BSS requires from MSC to determine the required radio resources.
If the message Assignment complete or Handover request acknowledge or contains a Speech version
field then the value previous filled is over written by this field.
1 GSM speech full rate version 1

5 GSM speech half rate version 1
8
IMEI
IMEI Number
This field is filled from the Location updating request or Location updating accept or Identity response
or CM service request or or CM re-establishment or IMSI detach indication or TMSI reallocation
command or Notification response message whichever is received last in the sequence.
(Reference 3GPP TS 24.008 V 4.12.0 5.6.2.3)
IMSI
International Mobile Subscriber Identity (Reference 3GPP 24.008, par.10.5.1.4).
or CM service request or Paging or CM re-establishment or IMSI detach indication or TMSI reallocation
command*3 or Notification response message or Handover Request message whichever is received
last in the sequence.
TMSI
Temporary Mobile Subscriber Identity (Reference 3GPP 24.008, par.10.5.1.3, 3GPP 48.008,
par.3.2.2.17). This field will be used by the TMSI_IMSI Server.
or CM service request or CM re-establishment or IMSI detach indication or TMSI reallocation command
or Notification response message whichever is received last in the sequence.
If new TMSI value received in message is not equal to TMSI_OLD field value then only this field will be
filled.
1st Location Area Code

Location Area Code (LAC) of the MS where it is detected the first time in a sequence. This field can be
filled from the first Assignment complete or Complete Layer3 Information or VGCS/VBS assignment
request or VGCS/VBS assignment result or Uplink request confirm or Perform location request
messages in the sequence of the call. In case of sequences starting with Handover Request - this field
is filled from the Target LAC. This field will not be overwritten once filled. (Ref. 3GPP TS 24.008,
3.2.2.17)
1’st cell id
Cell id of the MS where it is detected the first time in a sequence. This field can be filled from the first
Assignment complete or Complete Layer3 Information or VGCS/VBS assignment request or VGCS/VBS
assignment result or Uplink request confirm or Perform location request messages in the sequence of
the call. In case of sequences starting with Handover Request - this field is filled from the Target CI.
This field will not be overwritten once filled. (Ref. 3GPP TS 24.008, 3.2.2.17)
2nd Location Area Code

Location Area Code (LAC) where the MS wants to move to. This field is filled from the last received
Handover Required or Handover Command messages in the sequence of call. (Ref. 3GPP TS 24.008,
3.2.2.17)
2’nd cell id
Cell id where the MS wants to move to. This field is filled from the last received Handover Required or
Handover Command messages in the sequence of call. (Ref. 3GPP TS 24.008, 3.2.2.17)
Set-up time
This field indicates time difference between first Setup and first Alerting messages in the sequence of
the call. When Alerting is absent, it denotes the time between the first Setup message and the first
Disconnect/Release/Release Complete/ BSSRM RECORD Clear Command/BSSRM RECORD Clear
Request/SCCP RLSD/RLC/IMSI Detach Indication/ timeout, whichever occurs first in the sequence.
Holding time
This field indicates how much time CC/SS session remained active in the sequence
CC
It’s the time between the First CC (i.e. setup) or Handover Complete ( which ever is received last in the
sequence ) AND which ever is received first in the sequence within CC-Release Complete, BSSRM
9
RECORD-Clear Request, BSSRM RECORD-Clear Command, SCCP-REL, SCCP-RLSD, Any event
which has terminated sequence
Ringing time
This field denotes the time for which the mobile was ringing and hence it is also called as “Ringing time”.
This field indicates time difference between first Alerting and first Connect/Connect
Ack/Disconnect/Release/Release Complete/BSSRM RECORD Clear Command/BSSRM RECORD
Clear Request/SCCP RLSD/SCCP RLC/IMSI Detach Indication/Timeout whichever occurs first in the
sequence of the call.
Conversation Time
This field indicates the total Talk time for a call.
Time from Connect Acknowledge or Handover Complete (Which ever is received last in the sequence)
and Disconnect, Release, Release Complete, BSSRM RECORD-Clear Request, BSSRM RECORD-
Clear Command, REL, RLSD, IMSI DETACH INDICATION carried in DT1 message or Any event which
has terminated sequence
Complete Time
The total session time, i.e. the time from Handover Required, CM Service Request, Paging Response
or Location Update Request to Release Complete in msec’s. It’s the difference between first CR and
last RLC message received in the sequence.
Assignment Time
This field indicates time difference between last Assignment Request and First Assignment Complete
or Assignment Failure message in the sequence of the call.
TCH Assignment Time

This field indicates time difference between first CM service request message or Paging Response and
First Assignment Complete or Assignment Failure message in the sequence of the call.
Paging Time
Time from initial Paging message to the Paging Response message in msec’s
No of Handover Performed
The number of Handover Performed messages.
This field is incremented by one when Handover performed message is received in the sequence. The
count will give number of Intra BSC handovers performed in sequence.
RR Cause (BSSRM RECORD)

Reporting of Radio Resource problem.
This field is filled from the last Assignment complete or Assignment failure or Handover complete or
Handover failure message in the sequence.
(3GPP TS 48.008 V 4.10.0 Section 3.2.2.22)
Cause (BSSRM RECORD)

Indicates the reason for a particular event to have occurred.
This field is filled from the first Clear Command or Clear Request message in the sequence.
(3GPP TS 48.008 V 4.10.0 Section 3.2.2.5). The list the values that this cause can assume are the
same of the field HO Required Cause.
Reject Cause (DTAP MM)

Indicate the reason why a request from the mobile station is rejected by the network.
This field is filled from last Location Updating reject or MM status or Abort or CM service reject message
in the sequence.
(3GPP TS 24.008 V 4.10.0 Section 10.5.3.6)
Cause (DTAP CC)

Provide the reason for generating certain messages, or diagnostic information in the event of procedural
errors or indication of the location of the cause originator.
10
This field will be filled from the first received Release or Release complete message in the sequence of
the call.
(3GPP TS 24.008 V 4.12.0 Section 10.5.4.11). Main values (specified in decimal) are:
1 Unassigned (unallocated) number

3 No route to destination
6 Channel unacceptable
8 Operator determined barring
16 Normal call clearing
17 User busy
18 No user responding
19 User alerting, no answer
21 Call rejected
22 Number changed
25 Pre-emption
26 Non selected user clearing
27 Destination out of order
28 Invalid number format (incomplete number)
29 Facility rejected
30 Response to STATUS ENQUIRY
31 Normal, unspecified
34 No circuit/channel available
38 Network out of order
41 Temporary failure
42 Switching equipment congestion
43 Access information discarded
44 requested circuit/channel not available
47 Resources unavailable, unspecified
49 Quality of service unavailable
50 Requested facility not subscribed
55 Incoming calls barred within the CUG
57 Bearer capability not authorized
58 Bearer capability not presently available
63 Service or option not available, unspecified
65 Bearer service not implemented
68 ACM equal to or greater than ACMmax
69 Requested facility not implemented
70 Only restricted digital information bearer capability is available
79 Service or option not implemented, unspecified
81 Invalid transaction identifier value
87 User not member of CUG
88 Incompatible destination
91 Invalid transit network selection
95 Semantically incorrect message
96 Invalid mandatory information
97 Message type non-existent or not implemented
98 Message type not compatible with protocol state
99 Information element non-existent or not implemented
100 Conditional IE error
101 Message not compatible with protocol state
102 Recovery on timer expiry
111 Protocol error, unspecified
127 Interworking, unspecified
3st Location Area Code

Location Area Code (LAC) from the latest observed Location Area in a single SCCP connection. That
means this field will be over written from the last observed LAC.
This field can be filled from the last Assignment complete or Complete Layer3 Information or VGCS/VBS
assignment request or VGCS/VBS assignment result or Uplink request confirm or Perform location
request and Handover performed messages in the sequence of the call. In case of sequences starting
with Handover Request - this field is filled from the Target LAC.
(Ref. 3GPP TS 24.008, 3.2.2.17)
3’st cell id
11
Cell id of the from the latest observed Location Area in a single SCCP connection. That means this field
will be over written from the last observed CI.
This field can be filled from the last Assignment complete or Complete Layer3 Information or VGCS/VBS
assignment request or VGCS/VBS assignment result or Uplink request confirm or Perform location
request or Handover performed messages in the sequence of the call. In case of sequences starting
with Handover Request - this field is filled from the Target CI (Ref. 3GPP TS 24.008, 3.2.2.17)
HO Required Cause
This field is filled from the last received Handover Required message in the sequence
(3GPP TS 48.008, 3.2.2.5).
Cause values (specified in decimal) for this fields are:
0 Radio interface message failure/National Normal event

1 Radio interface failure
2 Uplink quality
3 Uplink strength
4 Downlink quality
5 Downlink strength
6 Distance
7 O and M intervention
8 Response to MSC invocation
9 Call control
10 Radio interface failure, reversion to old channel
11 Handover successful
12 Better cell
13 Directed retry
14 Joined group call channel
15 Traffic
16 Reduce load in serving cell
17 Traffic load in target cell higher than in source cell
18 Relocation triggered
32 Equipment failure/National
33 No radio resource available
34 Requested terrestrial resource unavailable
35 CCCH overload
36 Processor overload
37 BSS not equipped
38 MS not equipped
39 Invalid cell
40 Traffic load
41 Preemption
48 Requested transcoding/rate adaption unavailable
49 Circuit pool mismatch
50 Switch circuit pool
51 Requested speech version unavailable
64 Ciphering algorithm not supported/National Service or option not implemented
80 Terrestrial circuit already allocated/National Invalid message (eg. parameter out of range)
81 Invalid message contents
82 IE or field missing
83 Incorrect value
84 Unknown message type
85 Unknown information element
96 Protocol Error between BSS and MSC/National Protocol error
97 VGCS/VBS call non existent
112 National Interworking
HO Failure Cause
This field is filled from the last received Handover failure message in the sequence.
(3GPP TS 48.008, 3.2.2.5).
The possible value are the same listed for HO Required Case, but typical Cause values (specified in
decimal) for this fields are:
0, radio interface message failure;

7, O and M intervention;
32, Equipment failure;
12
33, no radio resource available;
34, requested terrestrial resource unavailable;
48, requested transcoding/rate adaption unavailable;
80 terrestrial circuit already allocated;
81, invalid message contents;
10, radio interface failure - reversion to old channel;
64, ciphering algorithm not supported;
49, circuit pool mismatch;
50, switch circuit pool;
51, requested speech version unavailable;
17, traffic load in the target cell higher than in the source cell.
Old_MCC
This field is the mobile Country Code and it is filled from Location Update Request message Location
Area Identified IE
(Ref 3GPP TS 24.008, par 10.5.3.5)
Old_MNC
This field is the mobile Network Code and it is filled from Location Update Request message Location
Area Identified IE
(Ref 3GPP TS 24.008, par 10.5.3.5)
Old_LAC
This field is the Location Area Code filled from the first received ‘Location Updating Request’ (Serving
LAC) or ‘Handover Request’ or ‘Assignment complete’ or ‘Complete Layer 3 Info’ or ‘Change Circuit’ or
‘ Uplink Circuit Confirmation ‘ or ‘ Perform location Request’ messages in the sequence
(Ref 3GPP TS 49.008, par 3.2.2.17). This field is used in the IMSI/TMSI server
Assig_CipherMode Reject Cause

This field is filled from the last received Assignement Failure or Cipher Mode Failure message in the
sequence (Ref 3GPP TS 48.008, par 3.2.2.5). The possible value are the same listed for HO Required
Case.
NO_Handover_Failure
This field indicates the number of handover failures in a sequence.
This field is incremented by one when HO Required/Request message is received and decremented by
one when HO command/Request ackowledge is received. This count results in the number of inter BSC
or Inter MSC handover failures.
Disconnection_Cause
This field is filled from the first Disconnect message received.
(Ref 3GPP TS 24.008, par 10.5.4.11)
Main cause values (specified in decimal) are:
1 unassigned number
3 no route to destination
6 channel unacceptable
8 operator determined
16 normal call clearing
17 user busy
18 no user responding
19 user alerting, no answer
21 call rejected
22 number changed
25 pre-emption
26 non selected user clearing
27 destination out of order
28 invalid number format
29 facility rejected
30 response to STATUS ENQUIRY
31 normal, unspecified
34 no circuit / channel available
38 network out of order
13
41 temporary failure
42 switching equipment congestion
43 access information discarded
44 requested circuit/channel not available
47 resources unavailable, unspecified
49 quality of service unavailable
50 requested facility not subscribed
55 incoming calls barred within the CUG
57 bearer capability not authorized
58 bearer capability not presently available
48 service or option not available, unspecified
65 bearer service not implemented
68 ACM equal to or greater than ACMmax
69 requested facility not implemented
70 Only restricted digital information bearer capability is available
64 service/option not impl.
81 invalid mandatory information
87 User not member of CUG
88 incompatible destination
91 invalid transit n/w selection
80 semantically incorrect message
96 invalid mandatory information
97 msg type non-existent/not impl
98 Message type not compatible with protocol state
99 Information element or field missing
100 conditional IE error
101 Message not compatible with protocol state
102 recovery on timer expiry
111 protocol error, unspecified
127 interworking, unspecified
1nd_HandoverReferenceNo
This field is filled from the last Handover Request Acknowledge message in the sequence. If this field is
filled then it can be considered that Intra/Inter MSC handover is performed
(3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.2.15).
2nd_HandoverReferenceNo
This field is filled from the last Handover Command message in the sequence. If this field is filled then
it can be considered that Intra/Inter MSC handover is performed.
(3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.2.15).
TransactionId
- CC - In case of CC call this field is filled from first Setup or Call proceeding or Alerting or Progress
or Call confirmed or Congestion control or Facility or Notify or Release or Release complete or Start
DTMF or Start DTMF reject or Status or Status enquiry or Stop DTMF or Stop DTMF ack or User
information or SM status or Connect or Connect acknowledge or Emergency Setup or Start CC or
Disconnect or CC-Establishment or CC-Establishment confirm or Recall or Hold or Hold ack or Hold
Reject or Retrieve or Retrieve ack or Retrieve Reject or Modify or Modify complete or Modify reject
message received in the sequence.
- SS - In case of SS this field is filled from the first Register or Facility or Release complete message
in the sequence.
(3GPP TS 24.007 V4.2.0 Section 11.2.3.1.3)
IMEISV
This field is filled from the Location updation request or Location updating accept or Identity response
or CM service request or CM re-establishment or IMSI detach indication or TMSI reallocation command
or Cipher Mode Complete or Notification response message whichever is received last in the sequence
(3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.4).
Old TMSI
It is a randomly allocated number that is given to the mobile, the moment it is switched on. The number
is local to a location area, and so it has to be updated, each time the mobile moves to a new geographical
area. It is filled from Location updation request or Identity response or CM service request or Paging or
14
CM re-establishment or IMSI detach indication or Notification response message whichever is received
first in the sequence.
(3GPP 24.008 V7.8.0 (2007-06) (Release 7) section 10.5.1.3)
IMSI detach status

It indicates whether the MS is switched ON/OFF. It denotes the presence of IMSI Detach Indication
message in the sequence. It is filled from occurrence of IMSI Detach Indication MM message.
0 not received
1 received
Location update type

Indicate whether a normal updating, a periodic updating or an IMSI attach is wanted. Also indicate that
a follow-on request has been received from the mobile station CM layer. It is filled from the first Location
Update Request Message in the Call.

0 normal location updating
1 periodic updating
2 IMSI attach
Cause Location
It indicates the location of the cause originator. It is filled from the first Disconnect message in the
sequence. If there is no Disconnect message, then from the first Release message or first Release
complete message.

0 user
1 private network serving the local user
2 public network serving the local user
3 transit network
4 public network serving the remote user
5 private network serving the remote user
7 international network
10 network beyond interworking point
End message
It indicates the message type that leads to the actual termination of the sequence/call. It is filled with the
message type that actually leads to the termination of the sequence/call.
This field will be filled only for the call/sequence failure scenarios. For successful call/scenario, this field
will not be filled.

1 Connection Refusal (SCCP)
2 Assignment Failure (BSSRM RECORD)
3 Handover Failure (BSSRM RECORD)
4 Clear Request (BSSRM RECORD)
5 Clear Command (BSSRM RECORD)
6 Handover Required Reject (BSSRM RECORD)
7 Confusion (BSSRM RECORD)
8 Cipher Mode Reject (BSSRM RECORD)
9 Location Updating Reject (MM)
10 Authentication Reject (MM)
11 Authentication Failure (MM)
12 CM Service Reject (MM)
13 CM Service Abort (MM)
14 Abort (MM)
15 Release (CC)
16 Release Complete (CC)
17 Disconnect (CC)
15
22 Release Complete (SS)
23 Facility (SS)
End message cause

It indicates the cause that leads to the actual termination of the sequence/call. It is filled f with the cause
value present in the message that actually led to the termination of the sequence/call.
This field will be filled only for the call/sequence failure scenarios. For successful call/scenario, this field
will not be filled.
Sequence Terminate Cause

It indicates the cause, which has terminated the sequence. It is filled from the Sequence terminating
message. In case of Major sequence, the terminating message will be part of sequence. In case of Minor
sequence cause value will be updated from the Major sequence.
Timeout Value Timer

0 SCCP Release message received
1 RP-Ack Received (for minor sequence)
2 CP-Err Received (for minor sequence)
3 Release complete received (for minor sequence)
4 Sequence Handed Over *a(for minor)
5 Major Sequence terminated with unknown reason
6 Major sequence User defined Timer expired
7 Minor sequence User defined Timer expired
8 SS Terminate (for Minor)
9 Minor Sequence terminated due to Major Sequence
10 LU accept received and Seq terminated due to following CM Service
Request **
11 SCCP CREF Received
SCCP Release Cause

It indicates indicate the reason of the SCCP connection release. It is filled from SCCP “Release Cause”
IE of SCCP present in the last RLSD message.
(ITU-T Q.713 (03/01) Section 3.11)
Called SSN
It indicates the called subsystem number, which serves to simplify message reformatting following
global title translation. Called Party Subsystem Number identifies the SCCP User when provided. It is
filled from the Called Party Address IE of the first SCCP message in the sequence.
(ITU-T Q.713 (03/01) Section 3.4)
HO Complete Time
It indicates time difference between last Handover required and last Handover command messages.
This field shows time taken for actual handover resource allocation. It is filled from sequences
containing Handover Required and Handover Command.
HO Request Cause
It is filled from the first received Handover request message in the sequence. The cause list is the
same specified for HO Required Cause.
(3GPP TS 48.008 V6.7.0 (2004-11) section 3.2.2.5)
HO Required Reject Cause

It is filled from the first received Handover required reject message in the sequence. The cause list is
the same specified for HO Required Cause.
(3GPP TS 48.008 V6.7.0 (2004-11) section 3.2.2.5)
Assignment Failure Cause
16
It indicates the reason for an occurred Assignment Failure. It is filled from the last Assignment failure
message.
The cause list is the same specified for HO Required Cause.
(3GPP TS 48.008 V6.7.0 (2004-11) section 3.2.2.5)
CM Service Request Type

It indicates which service the MS is requesting. It is filled from last CM-Service request message in the
sequence.
(3GPP 24.008 V7.8.0 (2007-06) section 10.5.3.3)
Values (specified in decimal) are:
1 Mobile originating call establishment or packet mode connection establishment

2 Emergency call establishment
4 Short message service
8 Supplementary service activation
9 Voice group call establishment
10 Voice broadcast call establishment
11 Location Services
Authentication Failure Cause

It indicates the reason why a request (authentication) from the mobile station is rejected by the
network. It is filled from the Reject Cause IE of the last Authentication Failure MM Message in a
sequence.
Cause values are:
2 IMSI unknown in HLR
3 Illegal MS
4 IMSI unknown in VLR
5 IMEI not accepted
6 Illegal ME
11 PLMN not allowed
12 Location Area not allowed
13 Roaming not allowed in this location area
15 No Suitable Cells In Location Area
17 Network failure
20 MAC failure
21 Synch failure
22 Congestion
23 GSM authentication unacceptable
32 Service option not supported
33 Request service option not subscribed
34 Service option temporarily out of order
38 Call not be identified
From 48 to 63 retry upon entry into a new cell
95 semantically incorrect message
96 Invalid mandatory information
97 Message type non-existent or not implemented
98 Message type not compatible with the protocol state
99 Information element non-existent or not implemented
100 Conditional IE error
101 Message not compatible with the protocol state
111 Protocol error, unspecified
No of DTMF bits
It indicates the number of DTMF messages present in the sequence. It is incremented for each Start
DTMF message.
1st Channel Type

It indicates the type of channel allocated. It is filled from the Channel Type sub-IE of Channel
DescriptionIE of the last RR-Handover Command message over BSSRM RECORD -Handover
17
Request Acknowledge message in the sequence. If this field is filled then it can be considered that
Intra/Inter MSC handover is performed.
(3GPP TS 44.018 V6.21.0 section 10.5.2.5)
The list of values this field can assume is the same specified for Assigned Channel Type.
2nd Channel Type

Same as above.
1st Radio Timeslot

It represents the number of the timeslot used within a TDMA frame. It is filled from the TimeSlot
Number (TN) sub-IE of Channel Description IE of the last RR-Handover Command message over
BSSRM RECORD -Handover Request Acknowledge message in the sequence. If this field is filled
then it can be considered that Intra/Inter MSC handover is performed
(3GPP TS 44.018 V6.21.0 section 10.5.2.5)
2nd Radio Timeslot

Same as above.
1st ARFCN
It is a binary representation of the BCCH carriers absolute RF channel number. It is filled from the
BCCH ARFCN sub-IE in CellDescription IE of the last RR-Handover Command message over BSSRM
RECORD -Handover Request Acknowledge message in the sequence. If this field is filled then it can
be considered that Intra/Inter MSC handover is performed.
(3GPP TS 44.018 V6.21.0 section 10.5.2.5)
2nd ARFCN
Same as above.
S-RNTI
It identifies the mobile station in the area of its serving BSC. In case of Intersystem HO to UTRAN this
field is filled from SRNTI present in RRC’s u-RNTI IE present in the RRC container "Handover To
UTRAN command” over BSSRM RECORD HANDOVER REQUEST ACKNOWLEDGE message.
(3GPP TS 25.331 V4.11.0 section 10.3.3.48)
CC Operation Code 1
It indicates the operation code value of CC Message. It is filled with Operation code value present in the
FACILITY IE of the First received Alerting or Call proceeding or Connect or Disconnect or Facility or
Release or Recall or Release Complete or Setup messages
(3GPP 24.008 V7.8.0 section 10.5.4.15)
CC Operation Code 2
Same as above. It is filled if CC Operation Code 1 is already filled.
SS Operation Code 1
It indicates the operation code value of SS Message. It is filled with the Operation Code of the Facility
IE of the 1st received message.
(3GPP TS 24.080 V6.3.0 section 4.2)
SS Operation Code 2
Same as above. It is filled if SS Operation Code 1 is already filled.
SS error code
It indicates the error code value of SS Facility. It is filled with the Error Code IE of SS Facility.
(3GPP TS 24.080 V6.3.0 section 4.3)
Major or Minor
18
It indicates if the sequence is Major Full Sequence, Minor Full Sequence, Major Half Sequence.
If Major sequence is having both CR and CC messages then it is considered as Full sequence and
respective Minor sequences will be considered as Half sequences.
If Major sequence is not having CR or CC present then it will be considered as half sequence and
respective Minor sequences will also considered as Half sequences.
Value Interpretation
0 Major Full Sequence
1 Minor Full Sequence
2 Major Half Sequence
New LAC
It uniquely identifies the location area of a GSM/UMTS cell. It indicates the new location area the MS
is going to enter. It is filled from the LAC sub-IE of Location updating accept or Handover request
(Target LAC) or Handover Performed or Handover command Assignment Complete or Complete
Layer 3 Information or Change Circuit or Uplink circuit confirmation or Perform Location Request or
TMSIReallocationCommand messages in the sequence.
(3GPP TS 48.008 V6.7.0 section 3.2.2.17 - 3GPP TS 24.080 V6.3.0 section 10.5.1.3)
Serving LAC
It uniquely identifies the location area of a GSM/UMTS cell. It indicates the location area the MS is
going to leave in case of Inter BSC/MSC handover, i.e. the LAC which is requiring the Handover. It is
filled from the LAC sub-IE of Handover request message in the sequence.
(3GPP TS 48.008 V6.7.0 section 3.2.2.17 - 3GPP TS 24.080 V6.3.0 section 10.5.1.3)
Serving cell id
It uniquely identifies the Cell id which is requiring the Handover. This field is filled from the Handover
Request message in the sequence.
(3GPP TS 48.008 V6.7.0 section 3.2.2.17)
Serving RNC id
It contains RNC ID in case of intersystem HO to GSM, i.e. The RNC that is requiring the handover. It is
filled from RNC-ID sub-IE of Handover Request in case of Intersystem HO to GSM.
(3GPP TS 48.008 V6.7.0 section 3.2.2.17)
Call Setup Time

For MO calls:
Time difference between CM service request and Alerting (or) Connect message whichever comes first
in the sequence.
For MT calls:
Time difference between Paging and Alerting (or) Connect message whichever comes first in the
sequence.
For Handover Calls:
In case of Handover calls, this field will not be filled.
PCM Usage Time

This field indicates the time difference between ASSIGNMENT REQUEST and CLEAR COMMAND
message.
This field will not be filled if ASSIGNMENT REQUEST or CLEAR COMMAND messages are not present
in the sequence. In Handover case, this field indicates the time difference between HANDOVER
REQUEST and CLEAR COMMAND message. This field will not be filled if HANDOVER REQUEST or
CLEAR COMMAND messages are not present in the sequence.
MS Power Class
It indicates the RF power class of the MS. There are five power classes. Class 1 is the class with the
highest RF power capability.
19
This field is filled from Complete layer 3 Information message or Handover Request message which
ever comes first.
Paging Response
This field indicates if a paging response is present in the sequence or not.
BYTE 1(MSB) BYTE 2 (LSB)

WORD
BIT
Pattern
Position
BIT 7 (MSB) Paging Response For Future Use
Present
BIT 6 For Future Use For Future Use
BIT 0 (LSB) For Future Use For Future Use
(3GPP TS 44.018 V6.21.0 section 3.3.2.2)
PCM Multiplex Number

The PCM Multiplex number identifies the terrestrial channel over which the call is passed. Bits 15-5 of
the CIC (LABEL_CIC in the RECORD) identifies the PCM Multiplex number in use.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bits in LABEL_CIC
a b c d e f g h i j k X X X X X Bits and octets in standard
Octet 2 Octet 1
(3GPP TS 48.008 V6.7.0 section 3.2.2.2)
PCM Active Timeslot

Every PCM multiplexed trunk is divided into 32 timeslots on which calls are passed. Bits 4-0 of the CIC
(LABEL_CIC in the RECORD) indentify the PCM active timeslot in use.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bits in LABEL_CIC
a b c d e f g h i j k X X X X X Bits and octets in standard
Octet 2 Octet 1
(3GPP TS 48.008 V6.7.0 section 3.2.2.2)
Is Inter System Handover Occurred

This field will be filled in case of Intersystem HO. It indicates if an Intersystem HO has occurred and if
it has been successful.
Interpretation Bit Set
Intersystem HO not Occured 0 (LSB)

Intersystem HO occurred from GSM to UTRAN 1
20
Interpretation Bit Set
Intersystem HO occurred from UTRAN to GSM 2
Intersystem HO from GSM to UTRAN failed 3
Intersystem HO from UTRAN to GSM failed 4
SDCCH Drop Flag

This field indicates SDCCH DROP when CLEAR REQUEST message is received before
ASSIGNMENT REQUEST message or CLEAR REQUEST message with a release cause other than
normal.
Value SDCCH Drop field
0 Mobile is not in SDCCH state
1 Mobile is in SDCCH state
Frequency Band Used

This field indicates the GSM frequency band used. It will be filled by Handover To cdma2000
Command IE in the Handover To cdma2000 Command.
Value Frequency Band
0 P-GSM 900
1 E-GSM 900
2 R-GSM 900
3 DCS 1800
4 PCS 1900
(3GPP TS 44.118 V6.4.1 section 9.2.18)
Paging Cause
This field indicates the reason for paging. This field is filled from the first Paging message. (3GPP TS 48.008
V8.9.0 section 9.46)
Voice Service Time
Voice Service Time indicates the time difference between CM Service Request message in case of MO Call or
Paging Response in case of MT Call and CC Alerting Message. Filling rule: VOICE_SERVICE_END_TIME -
VOICE_SERVICE_START_TIME
3 3G RECORD STRUCTURE
A 3G record describes a 3G Transaction and consists of an ASCII line of comma-separated attributes.
The date and time attribute of 3G records within the file refers to the completion time of the transaction
3.1 3G Record Format

The table below describes the attributes of 3G records with regards to length and format. If applicable it
also includes a sample.
In the 3G record, the parameters are “,” separated. If a parameter is unavailable and no meaningfully
3G record fields whose mandatory parameters have value "_" can be admitted due to various
21
“Up to” in the column “Field Format”. Fixed-length numerical values are to be padded with leading 0’s.
# Name Field Option Sample 3G Record Field Protocol

Format al Dialogue Field
(ASCII) name
1 Type 3G N 3G TYPE N.A.
2 Dialogue Up to 3 char, N 2 for UMTS 3G N.A. N.A.
indicator hex 3.0
3 IU dialogue type 2 digits, dec N 01 SequenceType SEQTYPE
4 Start Date and 12 chars, N 00ED1FE133F3 StartTimeStmcsec N.A.

time hex + StartmsPart
5 End Date and 12 chars, N 00ED1FE13416 EndTimeStmcsec, N.A.
time hex EndmsPart,
Timeout (see
Section 3.2 for
details)
6 SequenceTermi Up to 2 N 2 SequenceTerminat SEQUENCE_TER
nateCause digits, dec eCause MINATION_CAUS
E
7 Violation Up to 2 N 0 Violation VIOLATION
digits, dec
8 Timeout Up to 2 N 0 Timeout TIMEOUT
digits, dec
9 Major OR Minor 1 binary digit N 1 MajorORMinor MAJOR_OR_MIN
OR
10 OPC Up to 6 N 24 OPC LABEL_OPC
chars, hex
11 DPC Up to 6 char, N F2 DPC LABEL_DPC
hex
12 SLR Up to 12 Y 24 SLR SLR
digits, dec
13 DLR Up to 12 Y F2 DLR DLR
digits, dec
14 Complete Time Up to 8 char, Y 627 CompleteTime COMPL_TIME
hex
15 SIO Up to 3 Y 3 SIO SIO
digits, dec
16 Called SSN Up to 3 Y 3 Called SSN CALLED_SSN
digits, dec
17 TransportAssoc Up to 8 char, Y 2 TransportAssociati TRANSPORT_AS
iation hex on SOCIATION
18 --- --- - - - _
19 Target Cell Id Up to 8 char, Y 67 Target_Cell_Id TARGET_CELL_I
hex D
20 Requested Up to 12 Y 1200 RequestedDownlin REQ_DL_MAX_BI
Downlink digits, dec kMaximumBitRate T_RATE
Maximum Bit
Rate
21 Requested Up to 12 Y 1200 RequestedDownlin REQ_DL_GURAN
Downlink digits, dec kGuranteedBitRate TEED_BIT_RATE
Guranteed Bit
Rate
22
(ASCII) name
22 Requested Up to 12 Y 1200 RequestedUplinMa REQ_UL_MAX_BI
Uplink digits, dec ximumBitRate T_RATE
Maximum Bit
Rate
23 Requested Up to 12 Y 1200 RequestedUplinkG REQ_UL_GURAN
Uplink digits, dec uranteedBitRate TEED_ BIT_RATE
Guranteed Bit
Rate
24 --- --- - - - _
25 --- --- - - - _
26 RAB ID Up to 16 Y 1001 RAB_ID RAB_ID
Binary Digit
27 1st LAC Up to 4 char, Y 123 1st LAC LAC_1
hex
hex
hex
30 Transport Layer Up to 40 Y 3e0da0f9000000 TransportLayerAd TRANSPORT_LA
Address char, hex 0000000000000 dress YER_ADDRESS
0000000000000
31 --- --- - - - _
32 --- --- - - - _
33 --- --- - - - _
34 IuReleaseCaus Up to 3 Y 2 IuReleaseCause IU_RELEASE_CA
e digits, dec USE
35 Security Reject Up to 3 Y 2 SecurityRejec SECURITY_MOD
Cause digits, dec Cause E_REJ_CAUSE
36 PagingCause Up to 3 Y 22 PagingCause PAGING_CAUSE
digits, dec
37 Relocation Up to 3 Y 24 RelocationCause RELOC_CAUSE
Cause digits, dec
38 Relocation Type Up to 3 Y 24 RelocationType RELOC_TYPE
digits, dec
39 RelocationFailu Up to 3 Y 24 RelocationFailureC RELOC_FAIL_CA
reCause digits, dec ause USE
40 Relocation Up to 3 Y 2 RelocationCancel RELOC_CANCEL
Cancel Cause digits, dec Cause _CAUSE
41 RAB Release Up to 3 Y 2 RABReleaseCaus RAB_REL_CAUS
Cause digits, dec e E
42 Traffic Class Up to 3 Y 2 TrafficClass TRAFFIC_CLASS
digits, dec
43 Mcc Up to 3 Y 222 Mcc OLD_MCC
digits, dec
44 Mnc Up to 3 Y 16 Mnc OLD_MNC
digits, dec
45 Location Up to 3 Y 2 LocationUpdateTy LOC_UPD_TYPE
Update Type digits, dec pe
46 MM Reject Up to 3 Y 21 MMRejectCause MM_REJ_CAUSE
Cause digits, dec
47 CM Service Up to 3 Y 21 CMServiceReques CM_SERV_REQ_
Request Type digits, dec tType TYPE
48 Response time Up to 8 char, Y 23f43 Response time RESP_TIME
hex
23
(ASCII) name
49 Waiting time Up to 8 char, Y 23f43 Waiting time WAIT_TIME
hex
50 Call On Hold Up to 8 char, Y 23f43 CallOnHoldTime CALL_ON_HOLD_
Time hex TIME
51 CC Operation Up to 6 Y 12 CCOperationCode CC_OPER_CODE
Code1 digits, dec 1 _1
52 CC Operation Up to 6 Y 12 CCOperationCode CC_OPER_CODE
53 Call type Up to 3 Y 2 Call type CALL_TYPE
digits, dec
54 Disconnection Up to 3 Y 2 DisconnectionCau DISCONNECTION
Cause digits, dec se _CAUSE
55 --- --- - - - _
56 CC Release Up to 3 Y 2 CCReleaseCause CC_RELEASE
Cause digits, dec
57 --- --- - - - _
58 --- --- - - - _
59 DTMF Number Up to 4 char, Y 2 DTMFNumberOfD NUM_OF_DTMF_
Of DTMF Bits hex TMFBits BITS
60 --- - - - - _
61 --- - - - - _
62 --- - - - - _
63 --- - - - - _
64 --- - - - - _
65 --- - - - - _
66 --- - - - - _
67 --- - - - - _
68 SS Operation Up to 6 Y 4 SSOperationCode SS_OPER_CODE
69 SS Operation Up to 6 Y 4 SSOperationCode SS_OPER_CODE
Code 2 digits, dec 2 _2
70 IMSI3 Up to 16 Y 4453783012345 Imsi IMSI
digit, hex 610
71 IMEI4 Up to 16 Y 4905203012345 Imei IMEI
digit, hex 610
72 IMEISV5 Up to 16 Y 8745203012345 IMEISV IMEISV
digit, hex 610
73 Tmsi Up to 8 char, Y 4 Tmsi TMSI
hex
74 TMSI_OLD Up to 8 char, Y 4 TMSI_OLD TMSI_OLD
hex
75 Called number6 Up to 22 Y 332265484 Called number CALLED_NO
digits, hex
3 Each number digit is output as one hexadecimal digit. So, number digits from 0 to 9 are output as
they are in decimal format. The hexadecimal format is used to include non-numerical info in the call
number, as "F" which indicates the number termination in some cases.
24
(ASCII) name
76 Calling number7 Up to 22 Y 332265484 Calling Number CALLING_NO
digits, hex
77 --- --- - - - _
78 Holding time Up to 8 char, Y 98e3 Holding time HOLD_TIME
hex
79 Conversation Up to 8 char, Y 56f1 Conversation Time CONV_TIME
Time hex
80 Called Noa Up to 2 char, Y 2 Called Noa CALLED_NOA
hex
81 Calling Noa Up to 2 char, Y 2 Calling Noa CALLING_NOA
hex
82 --- --- - - - _
83 Transaction Id Up to 2 char, Y 2 TransactionId TRANSACTION_I
hex D
84 LacOld Up to 4 char, Y 26f3 LacOld LAC_OLD
hex
85 LacNew Up to 4 char, Y 22fe LacNew LAC_NEW
hex
86 1st SAC Up to 4 char, Y 1 1st SAC SAC_1
hex
87 2st SAC Up to 4 char, Y 1 2st SAC SAC_2
hex
88 RANAP Up to 8 char, Y 1 RANAP Message RANAP_MESSAG
Message Flag hex Flag 1 E_FLAG1
89 RAB ASS Up to 3 Y 2 RAB ASS Failure RAB_ASSIGNME
Failure Cause digits, dec Cause NT_FAILURE_CA
USE
90 Paging Area ID Up to 4 char, Y 123 Paging Area ID PAGING_AREA_I
hex D
91 Transfer Delay Up to 4 char, Y 56f1 Transfer Delay TRANSFER_DEL
hex AY
92 RAB Setup- Up to 8 char, Y 56f1 RAB Setup-Time RAB_SETUP_TIM
Time hex E
93 CM Service Up to 8 char, Y 56f1 CM Service Accept CM_SERVICE_AC
Accept Time hex Time CEPT_TIME
94 CC Message Up to 8 char, Y 1 CC Message Flag CC_MESSAGE_F
Flag hex 1 LAG1
95 Paging Up to 4 char, Y 10 Paging Repetition PAGING_REPETI
Repetition hex Count TION_COUNT
96 Global Rnc Id Up to 8 char, Y 12 Global RNC ID/ GLOBAL_RNC_ID
hex Serving RNC ID / SRNC_ID
97 Target Rnc Id Up to 8 char, Y 32 Target RNC-ID TARGET_RNC_ID

hex
98 Qos Flag 2 char hex Y 10 Qos Flag QOS_FLAG
99 No.RABSubFlo Up to 2 char, Y 3 No.RABSubFlows NO_RAB_SUBFL

ws hex OWS
100 MM Message Up to 8 char, Y 1 MM Message Flag MM_MESSAGE_F
Flag hex LAG
101 SMS Message Up to 8 Y 1 SMS Message SMS_MESSAGE_
Flag char, hex Flag FLAG
25
(ASCII) name
102 3rd SAC Up to 4 Y 1 3rd SAC SAC_3
char, hex
103 Tgt Cell ID Up to 4 Y 2431 Tgt Cell ID TGT_C_ID
char, hex
104 IsHandoverOcc Up to 16 Y 00100000 IsHandoverOccure IS_HANDOVER_O
ured Binary Digit d CCURRED
105 RABinRequest Up to 3 Y 1 RABinRequest RAB_IN_REQUES
Digit, dec T
106 RABinRespons Up to 3 Y 1 RABinResponse RAB_IN_RESPON
e Digit, dec SE
107 RABinFailure Up to 3 Y 1 RABinFailure RAB_IN_FAILURE
Digit, dec
108 CompleteCallS Up to 8 Y 56f1 CompleteCallSetu CPL_CALL_SET_
e tupTime char, hex pTime TIME
109 Cause_Authenti Up to 3 Y 2 Cause_Authenticat AUTH_FAIL_CAU
cationFailure Digit, dec ionFailure SE
110 Relocation Up to 3 Y 2 Relocation RELOC_PREP_F
Preparation Digit, dec Preparation Failure AIL_ CAUSE
Failure Cause Cause
111 CS Up to 1 Y 1 CS Fallback CS_FALLBACK_I
Fallback Digit, dec indicator ND
indicator
112 Target eNB Id Up to 8 Y 32 Outgoing HO – TARGET_ENB_ID
char, hex Target eNB ID
113 Voice Service Up to 8 Y 56f1 Voice Service End VOICE_SERVICE
Time char, hex Time/Voice _END_TIME –
Service Start Time VOICE_SERVICE
_START_TIME
114 MSISDN Up to 22 Y 393331111111 MSISDN MSISDN =
digits MSISDNCSDR
if present and filled
Else
MSISDN =
MicsLookup(IMSI)
Lookup feature
has to be optional
115 CC Message Up to 8 Y 1 CC Message Flag CC_MESSAGE_F
Flag2 char, hex 2 LAG2
116 Incoming HO - Up to 8 Y 32 Incoming HO - TGT_RNC_ID
Target RNC ID char, hex Target RNC ID
117 Number of HO
performed
118 Cause location
Table 2 Attributes of 3G records
3.2 3G Record Attribute Description
Dialogue Indicator:
This value, fixed to 2, identifies the 3G record.
Iu dialogue Type:
26
This is the Sequence Type record field. This parameter determines the communication procedure
type. It can be in LDR file:
Value Sequence Type

4 Location Update
19 IMSI Detach
Start Date and time:

This is the time stamp for start of the transaction8. The time stamp is UTC time milliseconds since 1 Jan
1970 0:00. This field is computed using the StartTimeStmcsec and StartmsPart record fields.
End Date and time:

This is the time stamp for completion of the transaction 2. The time stamp is UTC time milliseconds since
1 Jan 1970 0:00. This field is computed using EndTimeStmcsec, EndmsPart and Timeout record fields
as well as follows:
1. If in the sequence No violation and No Timeout occurs, the End Date and time is filled from
EndTimeStmcsec + EndmsPart;
2. If in the sequence there was a violation but not a Timeout occurs the End Date and time is filled
from EndTimeStmcsec + EndmsPart;
3. If there was a violation for Timeout, the End Date and Time field is filled from: EndTimeStmcsec
+ EndmsPart – Timeout.
SequenceTerminateCause:
Value Sequence Termination Type

0 SCCP RLSD message received
1 RP-Ack Received (for minor sequence)
2 CP-Err Received (for minor sequence)
3 Release complete received (for minor sequence)
4 Sequence Handed Over *1(for minor)
5 Major Sequence terminated with unknown
reason
6 Major sequence User defined Timer expired
7 Minor sequence User defined Timer expired
8 SS Terminate(for Minor)
Violation:
Violation Name Bit Discription

Set
No Violation 0 No violation
(LS
B)
Too Many 1 Set 1 if Too Many Messages Violation
Messages
Decode Error 2 Set 1 if Decode Error Violation
Timer Timeout 3 Set 1 if Timer Timeout Violation
Second Start 4 Set 1 if Second Start message received in sequence
message received For Major Sequence the CR will be Second start message
For Minor CC Sequence Setup is Second start message
8 (End Time – Start Time) gives the total length (or duration) of the dialogue.
27
Termination of 5 Termination of Major sequence
Major sequence E.g. If sequence is started with SCCP CR (major) and MO call is part this
sequence and if MT call procedure is received over same SCCP
connection the second sequence (minor) sequence is started. If BSSRM
RECORD clear procedure is received or SCCP REL or RLSD messages
are received in the major sequence, the minor sequence has to be
terminated with the ‘Termination of Major sequence’ violation.
Unexpected 6 Unexpected message received
message received
Message 7 Message retransmission number reached Maximum possible
retransmission
number reached
Maximum possible
Timeout:
ID (enumeration) Timeout Name Timeout Value

0 No timeout 0
1 Inactivity Timer expiry 3600
Major or Minor:
If Major sequence is having both CR and CC messages then it is considered as Full sequence and respective
Minor sequences will also be considered as Full sequences.
Value Sequence Type
0 Major Full Sequence
1 Minor Full Sequence
Ranap Fields:
RANAP Field name Reference

OPC Q704, 2.2.3
DPC Q704, 2.2.3
SLR Q713, 3.3
DLR Q713, 3.3

CompleteTime This field indicates time difference between first CR and last
RLC message received in the sequence in ms.
SIO Q704, 14.2
Called SSN Q713 Section 2.1

TransportAssociation RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.2.2
Target_Cell_Id RANAP
3GPP TS 25.413 v4.2.0
Section
9.2.1.28
RequestedDownlinkMaximumBitRate RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.3 and 9.2.1.45
RequestedDownlinkGuranteedBitRate RANAP
3GPP TS 25.413 v4.2.0
28
Section 9.2.1.3 and 9.2.1.45
RequestedUplinMaximumBitRate RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.3 and 9.2.1.45
RequestedUplinkGuranteedBitRate RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.3 and 9.2.1.45
RAB_ID RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.2.
1st LAC RANAP
3GPP TS 25.413 v4.2.0
Section 9.1.33
2nd LAC RANAP
3GPP TS 25.413 v4.2.0
Section 9.1.33
3rd LAC RANAP
3GPP TS 25.413 v4.2.0
Section 9.1.33
TransportLayerAddress RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.2.1
IuReleaseCause RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.4
SecurityRejectCause RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.4
PagingCause RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.3.3
RelocationCause RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.4
RelocationType RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.23
RelocationFailureCause RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.4
RelocationCancelCause RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.4
RABReleaseCause RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.4
TrafficClass RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.3
MM Fields:
MM Field name Reference

Mcc 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.3.5
Mnc 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.3.5
LocationUpdateType 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.3.5
MMRejectCause 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.3.6
CMServiceRequestType 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.3.3
29
CC Fields:
CC Field name Reference

Response time Time in ms from Setup to Alerting
Waiting time Time in ms from Alerting to Connect
CallOnHoldTime Time in ms from Hold to Retrieve Acknowledge
CCOperationCode1 3GPP TS 24.080 V3.7.0 (2002-06)
Section 4.2
CCOperationCode2 3GPP TS 24.080 V3.7.0 (2002-06)
Section 4.2
Call type 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.4.5
DisconnectionCause 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.4.11
CCReleaseCause 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.4.11
DTMFNumberOfDTMFBits This field is incremented from each Start DTMF message
SS Fields:
SS Field Name Reference

SSOperationCode1 3GPP TS 24.080 V4.3.0 (2002-06) Section 4.2
SSOperationCode2 3GPP TS 24.080 V4.3.0 (2002-06) Section 4.2
Common Fields:
Common Field name Reference

Imsi 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.4
Imei 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.4
IMEISV 3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.4
Tmsi 3GPP TS 48.008 V4.10.0 (2003-09) Section 3.2.2.17
3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.3
TMSI_OLD 3GPP TS 48.008 V4.10.0 (2003-09) Section 3.2.2.17
3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.3
Called number 3GPP TS 23.040 V4.8.0 Section 9.2.3.8
Calling number 3GPP TS 23.040 V4.8.0 Section 9.2.3.7
Holding time This field indicates how much time in ms session remained
active in the sequence
Conversation Time This field will not be filled in 3G interface
Called Noa 3GPP TS 23.040 V4.8.0 Section 9.2.3.8
Calling Noa 3GPP TS 23.040 V4.8.0 Section 9.2.3.7
TransactionId 3GPP TS 24.007 V4.2.0 Section 11.2.3.1.3
LacOld 3GPP TS 48.008 V4.10.0 (2003-09) Section 3.2.2.17
3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.3
LacNew 3GPP TS 48.008 V4.10.0 (2003-09) Section 3.2.2.17
3GPP TS 24.008 V4.12.0 (2003-09) Section 10.5.1.3
General Fields:
Field name Reference

1st SAC RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.3.9
2nd SAC RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.3.9
30
RANAP Message Flag See Appendix A
RAB ASS Failure Cause RANAP
3GPP TS 25.413 v4.2.0
Section 9.1.4
Paging Area ID RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.21
Transfer Delay Transfer delay in ms as specified in RANAP
3GPP TS 25.413 v4.2.0
Section 9.2.1.3
RAB Setup-Time time duration between RANAP: “RAB ASS REQUEST” to
“RAB ASS RESPONSE”.
Attach Complete Time time duration between GMM: “ATTACH REQUEST” to
“ATTACH COMPLETE”.
CM Service Accept Time time duration between CM: “CM SERVICE REQUEST ” to
“CM SERVICE ACCEPT”.
CC Message Flag TBD
Paging Repetition Counter of Paging PDUs
Global Rnc Id Global RNC Id:
If Sequence Type = RELOC_REQ then GlobalRNC Id =
SRNC_ID
else GlobalRNC Id = GLOBAL_RNC_ID
Global RNC ID:

3GPP TS 25.413 ref 9.1.33
PLMN Identity + RNC Id.
Filled ONLY RNC Id value from this as Global RNC Id.
Serving RNC ID:

3GPP TS 25.331
Section 10.3.3.47 & 10.3.3.48
SRNC identity IE
Target Rnc Id 3GPP TS 25.413 ref 9.1.9
Target RNC-ID = LAI + RAC + RNC-Id
Filled ONLY RNC-Id value from this as Target RNC Id.
Qos Flag
Bit7:- Rab Queued(1) or not(0)
The Flag is set with the condition the RAB has been
mentioned as queued in one of previous RANAP RAB
ASSIGNMENT RESPONSE. This Flag could be included
also in the RANAP MESSAGE FLAG field
Bit6:- reuse of RAB(1) or not(0)
For each service ( either CS CC call or SM: PS session), if

we have RAB-ID from RANAP: RAB Assignment Request +
associated Stream ID/NSAPI from NAS. then we will fill our
layout as accordingly specific to that RAB + QOS params.
ELSE
(i.e second call doesn't have specific RAB ID signaled during
the sccp connection), then we will treat this as " same
bearer is reused for this second call also".
31
so we will fill the SAME ( as first call filled info) RAB + QOS
info in the Second CSDR layout also. In this case I propose
to have also another flag indicating the reuse of RAB.
Bit5:- Paging Response (1) or not (0)

Sequence has Paging response.
No.RABSubFlows The N. of subflows in RAB Assignent Request
4 RM (ROAMING) RECORD STRUCTURE

A RM record describes a RM Transaction and consists of an ASCII line of comma-separated attributes.
The date and time attribute of RM record within the file refers to the completion time of the transaction
4.1 RM Record Format

The table below describes the attributes of RM records with regards to length and format. If applicable
it also includes a sample.
In the RM record, the parameters are “,” separated. If a parameter is unavailable and no meaningfully
RM record fields whose mandatory parameters have value "_" can be admitted due to various
“Up to” in the column “RM Record Field Format”. Fixed-length numerical values are to be padded with
leading 0’s.
# Name Field Optional Sample Protocol Dialogue

Format Field name
(ASCII)
1 Type RM N RM TYPE
2 Scenario 2 char, N 01 Calculated from
hex OperationCode
3 Start Date and Up to N ED1FE133F3 Calculated from
time 12 StartTimeStmpSec
chars, and StartmsPart
hex
4 End Date and time Up to N ED1FE13416 Calculated from
12 EndTimeStmpSec
chars, and EndmsPart
hex
5 OPC 6 N 001234 LabelOPC
chars,
hex
32
Format Field name
(ASCII)
6 DPC 6 N 001234 LabelDPC
chars,
hex
7 Calling no.9 Up to Y10 4540590017 CallingNo or GT
28 CallingNo11
digit,
hex
8 Called no.9 Up to Y10 4540634520 CalledNo or
28 GTCalled No11
digit,
hex
9 MSISDN9 Up to Y12 4540504577 MSISDN
28
digit,
hex
10 Serving MSC Up to Y 4540504222 MSC
28
digit,
hex
11 Backward calling Up to Y13 4540504632 BackCallingNo
number 28digit,
hex
12 --- - - - _
13 IMSI9 Up to Y14 2380203001206571F IMSI
16
digit,
hex
14 --- - - - _
15 ODB General 8 Y 00011800 ODB General Data
Data chars,
hex
16 SS CodeSet 24 Y 000400430004004300040043 SSCodeSet
chars,
hex
17 --- - - - _
18 Supported 1 char, Y 1 Supported Camel
CAMEL Phases hex Phase
19 --- - - - _
20 Error code 2 Y 34 ErrorCode
chars,
hex
9 Each digit has to be considered as one hexadecimal digit. Some network nodes can add an F digit at
the end of the field, but it's a vendor specific issue. So, if last digit is equal to F, the application will
remove it and will fill the field with the remained hexadecimal digits.
10 These fields are optional in general but they are mandatory for scenarios 00, 01,02 ,03 ,08 ,09, 0a,
0b, 0c, 0d, 0e, 0f, 10, 11, 12, 13, 14, 15
11 In some RM FID (i.e. FID 118) the CallingNo and CalledNo are redefined in GTCallingNo and
GTCalledNo.
12 This field is optional in general but one between IMSI and MSISDN is mandatory for scenarios 0c
and 0d.
13 This field is optional in general but is mandatory for scenarios 00, 01,02 ,03 ,08 ,09, 0a, 0b, 0c, 0d,
0e, 0f, 10, 11, 12, 13, 14, 15 with Violation 00 and 01 while for scenarios with Violation 02 is empty.
14 This field is optional in general but one between IMSI and MSISDN is mandatory for scenarios 0c
and 0d. Furthermore, IMSI is mandatory for scenarios 0e and 0f.
33
Format Field name
(ASCII)
21 TCAP Abort 2 Y FD TCAPAbortCause
Cause chars,
hex
22 SCCP Return 2 Y 01 SCCPReturnCause
Cause chars,
hex
23 Violation 2 Y 01 _
chars,
hex
24 Number of 1 char, N 2 _
dialogues hex
25 PC0- PC1-… PCN 6 chars N 00013F Calculated from
each, LabelOPC from
hex LabelDPC
26 --- - - - _
27 User Error Reason 2 Y 04 UserErrorReason
chars,
hex
28 NoOfSCCPMsg Up to 2 N 1 Calculated from
chars, NumOfSCCPMsg
hex
29 SccpMsgLength Up to 4 N 4 Calculated from
chars, SCCPMsgLength
hex
30 --- - - - _
31 --- - - - _
32 Linkset Id Up to 8 N 321 _
chars,
hex
33 --- - - - _
34 --- - - - _
35 --- - - - _
36 --- - - - _
37 gsmSCF GT
Table 3 Attributes of RM records
4.2 RM Record Attributes Description

4.2.1 Scenario
This is the type ID of the RM record scenario/transaction. The following types are defined for LDR file:
Type Type RM Record Scenario/ Description Filling Rule

ID Code Transaction
00 0 Outbound Roaming The Location Operation Code
Update procedure = 2 and link
is initiated by the direction is
visiting VLR (in the backward (PDU
foreign network) is going in
towards the Home downlink
HLR in order to direction)
update the
subscriber location
information.
34
4.2.2 Start Date and time
This is the time stamp for start of the call. The time stamp is UTC time milliseconds since 1 Jan 1970
0:00.
4.2.3 End Date and time

This is the time stamp for completion of the call. The time stamp is UTC time milliseconds since 1 Jan
1970 0:00.
4.2.4 OPC
Originating Point Code (Reference Q704, 2.2.3) of the first CSDR in the dialogue.
4.2.5 DPC
Destination Point Code (Reference Q704, 2.2.3) of the first CSDR in the dialogue.
4.2.6 Calling no.

SCCP calling party number (Reference Q713, 3.4.23).
4.2.7 Called no.

SCCP called party number (Reference Q713, 3.4.23).
The Called Number corresponds to a number by mean to reach the HLR, i.e. a number that identifies
the HLR that may not be the same of the Backward Calling Number which when is present is equal to
the E.164 number of the node.
The following RM record traffic example should clarify the previous statement.
GMSC2_IXLJ1_5 fwd 08:38:56.575 MSU SCCP 0-160-1 2-145-3 5

UDT HLR 919810010187338 VLR 38641002111 BEGIN OTID: 58000187
INVOKE INVOKE ID: 1 updateLocation IMSI: 404100101873388F
GMSC1_IXLJ1_4 bwd 08:38:57.568 MSU SCCP 2-145-2 0-160-1 4

UDT VLR 38641002111 HLR 919810051912 END DEST TID: 58000187
RETURN ERROR INVOKE ID: 1 roamingNotAllowed operatorDeterminedBarring
Here the Called Number is 919810010187338 while Backward calling Number is

919810051912, both indicates HLR from Indian (CC=91) operator Airtel (NDC=
981) but the Called Number contains the “10010187338” digits from IMSI ( this
is because the Calling Node does not know the HLR number but only the IMSI
of the subscriber) while the Backward calling Number is the real E.164 HLR
number.
4.2.8 MSISDN
MSISDN number (Reference GSM 09.02 V4.6.0, 5.6.2.17)
This field is mandatory only in successful cases because it is contained in the Insert Subscriber Data
from HLR that follow the GSM Update Location only in case of success.
4.2.9 Serving MSC

Serving MSC Address (Reference GSM 09.02, 5.6.2.11).
35
4.2.10 Backward calling number:
Backward calling number (for HLR number) (Reference Q713, 3.4)
4.2.11 IMSI
IMSI Number (Reference GSM 09.02 V4.6.0, 5.6.2.1)
This field is mandatory, both in successful and unsuccessful cases. It is always present and it is the
subscriber identifier for network operations.
4.2.12 ODB General Data

ODB General Data (Reference GSM 09.02 7.6.3.9)
4.2.13 SSCode Set

A bit field of SS-CODEs (Reference GSM 09.02, 5.6.4.1)
4.2.14 Supported Camel Phases

The Supported CAMEL Phases (Reference GSM 09.02 7.6.3.36) field is a bit mask field exporting the
supported CAMEL phases and it is filled as in the following tables:
Bit Position in Supported Camel Phase Definition

0 (LSB) Phase 1
1 Phase 2
2 Phase 3
3 Phase 4
4-15 Not defined
The following table reports the valid values and their interpretation:
CSDR Supported Camel Phase field TDR Supported Camel Phase field
Definition
BIN HEX DEC
0000000000000000 0000 0 No phases supported
0000000000000001 0001 1 Phase 1
0000000000000010 0002 2 Phase 2
0000000000000011 0003 3 Phase 1 + Phase 2
0000000000000100 0004 4 Phase 3
0000000000000101 0005 5 Phase 3 + Phase 1
0000000000000110 0006 6 Phase 3 + Phase 2
0000000000000111 0007 7 Phase 3 + Phase 2 + Phase 1
0000000000001000 0008 8 Phase 4
0000000000001001 0009 9 Phase 4 + Phase 1
0000000000001010 000A 10 Phase 4 + Phase 2
0000000000001011 000B 11 Phase 4 + Phase 2 + Phase 1
0000000000001100 000C 12 Phase 4 + Phase 3
0000000000001101 000D 13 Phase 4 + Phase 3 + Phase 1
36
0000000000001110 000E 14 Phase 4 + Phase 3 + Phase 2
0000000000001111 000F 15 Phase 4 + Phase 3 + Phase 2 + Phase 1
4.2.15 Error code

RM record error code (ETSI TS 129 002 V4.6.0 (2002-01)) of the last CSDR of the transaction.
4.2.16 TCAP Abort Cause

TCAP abort cause (Reference Q772, 2.3)
4.2.17 SCCP Return Cause

Reason for message return (Reference Q-713 section 3.12)
4.2.18 Violation
TDR Violation (see Error! Reference source not found. )
TDR Description
Violation
00 No Violation
01 Missing End
02 Begin Only
4.2.19 Number of dialogues

This is the number of dialogues of the transaction.
4.2.20 PC0- PC1-… PCN

A sequence of Point Codes is indicated to represent the transaction path. The transaction path contains
N + 1 Point Codes, where N is the number of dialogues. PC0 is the OPC and PCN is the DPC.
4.2.21 User Error Reason

Specifies the subclassification of the error identified by ‘ErrorCode’ field. (Reference GSM 09.02 5.6.1.4)
4.2.22 NoOfSCCPMsg
Total number of class 0 and 1 SCCP messages (UDT /UDTS / XUDT / XUDTS / LUDT / LUDTS) used
in creating the TDR.
The SCCP messages will be measured as specified below:
 Without respect to the crossed links.
 Backward messages not correlated to any forward will be ignored.
If partial dialogs are disabled, forward messages not correlated to any backward will be ignored.
4.2.23 SccpMsgLength
The total length of class 0 and 1 all SCCP messages in the sequence (UDT / UDTS / XUDT / XUDTS /
LUDT / LUDTS) used in creating the TDR.
The SCCP messages will be measured as specified below:
 Without respect to the crossed links.
 Backward messages not correlated to any forward will be ignored.
If partial dialogs are disabled, forward messages not correlated to any backward will be ignored.
37
4.2.24 Linkset Id
The Linkset Id is retrieved from the MasterQuest Configuration database CDB. This is the Linkset Id of
the BEGIN PDU of the transaction.
38

Specification of Location Data Record File Structure

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Specification of Location Data Record File Structure

Transféré par

Droits d'auteur :

Formats disponibles

Specification of Location Data Record File Structure

2.1 2G Record Format

# Name Field Format (ASCII) Opti Sample Record field Default

2.2 2G Record Attribute Description

It can be LDR file:

Start Date and time: Starting time of the procedure in milliseconds

End Date and time:

Assigned Channel Type

0 SDCCH or Full rate TCH channel Bm or Half rate TCH channel Lm

Speech Version/Data Rate

1 GSM speech full rate version 1

1st Location Area Code

2nd Location Area Code

TCH Assignment Time

RR Cause (BSSRM RECORD)

Cause (BSSRM RECORD)

Reject Cause (DTAP MM)

Cause (DTAP CC)

1 Unassigned (unallocated) number

3st Location Area Code

0 Radio interface message failure/National Normal event

0, radio interface message failure;

Assig_CipherMode Reject Cause

IMSI detach status

Location update type

Main cause values (specified in decimal) are:

Main cause values (specified in decimal) are:

Main cause values (specified in decimal) are:

End message cause

Sequence Terminate Cause

Timeout Value Timer

SCCP Release Cause

HO Required Reject Cause

Assignment Failure Cause

CM Service Request Type

Values (specified in decimal) are:

1 Mobile originating call establishment or packet mode connection establishment

Authentication Failure Cause

1st Channel Type

2nd Channel Type

1st Radio Timeslot

2nd Radio Timeslot

Call Setup Time

PCM Usage Time

BYTE 1(MSB) BYTE 2 (LSB)

BIT 5 For Future Use For Future Use

BIT 4 For Future Use For Future Use

BIT 3 For Future Use For Future Use

BIT 2 For Future Use For Future Use

BIT 1 For Future Use For Future Use

BIT 0 (LSB) For Future Use For Future Use

(3GPP TS 44.018 V6.21.0 section 3.3.2.2)

PCM Multiplex Number

PCM Active Timeslot

Is Inter System Handover Occurred

Intersystem HO not Occured 0 (LSB)

SDCCH Drop Flag

Frequency Band Used

Voice Service Time

3.1 3G Record Format

# Name Field Option Sample 3G Record Field Protocol

4 Start Date and 12 chars, N 00ED1FE133F3 StartTimeStmcsec N.A.