03-Msoftx3000 v100r006c05 Asn.1 CDR Description

03-MSOFTX3000 V100R006C05 ASN.
1
CDR Description
MSOFTX3000
V100R006C05
Issue
1.00
Date
2008-02-25
CONFIDENTIAL
CONFIDENTIAL
MSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1
CDR Description
HUAWEI TECHNOLOGIES CO., LTD.
Issue 1.00 (2008-02-25)
Huawei Technologies Proprietary
Page ii of 173
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.
Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address:
Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, 518129, Peoples Republic of China
Website:
http://www.huawei.com
Email:
support@huawei.com
Copyright Huawei Technologies Co., Ltd. 2007. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Issue 1.00 (2008-02-25)
Page 3 of 173
CONFIDENTIAL
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
About This Document

Author
Prepared by
Guo Jin, Li Chunlin
Date
2004-8-9
Reviewed by
Gao Yue, Jia Yongli
Date
2005-3-14
Approved by
Yang Jun
Date
2005-3-14
Summary
This document introduces HUAWEI CDR structure.
Issue 1.00 (2008-02-25)
Page 5 of 173
CONFIDENTIAL
03-MSOFTX3000 V100R006C05 ASN.1
CDR Description
History
Issue
Issue 1.00 (2008-02-25)
Details
Date
Author
Approved by
Page 6 of 173
CONFIDENTIAL
Contents
1 ASN.1 Encoding Format..............................................................................................................16
1.1 ASN.1 Encoding Format........................................................................................................................................16
1.2 ASN.1 Encoding Format........................................................................................................................................16
1.2.1 Encoding Rules of Identifier Octets................................................................................................................16
1.2.2 Encoding Rules of Length Octets....................................................................................................................18
1.2.3 Encoding Rules of Contents Octets.................................................................................................................19
1.2.4 Encoding Rules of End-of-Contents Octets.....................................................................................................21
1.2.5 Structure of CDR Files....................................................................................................................................21
2 Record Contents...........................................................................................................................25
2.1 Mobile Originated Call Attempt............................................................................................................................25
2.2 Mobile Originated Emergency Call Attempt.........................................................................................................36
2.3 Mobile Originated Call Forwarding Attempt........................................................................................................46
2.4 Mobile Terminated Call Attempt...........................................................................................................................57
2.5 Roaming Call Attempt...........................................................................................................................................67
2.6 Incoming Gateway Call Attempt...........................................................................................................................72
2.7 Outgoing Gateway Call Attempt...........................................................................................................................76
2.8 Transit Call Attempt...............................................................................................................................................80
2.9 Short Message Service, Mobile Originated...........................................................................................................84
2.10 Short Message Service, Mobile Terminated........................................................................................................87
2.11 Mobile Terminated Location Request (MT-LR)..................................................................................................90
2.12 Mobile Originated Location Request (MO-LR)..................................................................................................93
2.13 Network Induced Location Request (NI-LR)......................................................................................................95
2.14 Supplementary Service Actions...........................................................................................................................98
2.15 HLR Interrogation.............................................................................................................................................100
2.16 Common Equipment Usage Record..................................................................................................................101
2.17 Terminating CAMEL Call Attempt...................................................................................................................104
2.18 IMEI Observation Ticket...................................................................................................................................109
2.19 Location Update (VLR).....................................................................................................................................110
3 Description of Record Fields......................................................................................................112

3.1 Additional Charging Information.........................................................................................................................112
3.2 aiurRequested.......................................................................................................................................................112
3.3 AoC parameters / change of AoC parameters......................................................................................................113
Issue 1.00 (2008-02-25)
Page 7 of 173
CONFIDENTIAL
03-MSOFTX3000 V100R006C05 ASN.1
CDR Description
3.4 audioDataType.....................................................................................................................................................113
3.5 basicService/changeOfService/isdnBasicService................................................................................................114
3.6 bCategory.............................................................................................................................................................118
3.7 callDuration.........................................................................................................................................................118
3.8 calling Number/called Number / connected Number/translated Number...........................................................120
3.9 callReference.......................................................................................................................................................121
3.10 CallType.............................................................................................................................................................121
3.11 cAMELCallLegInformation..............................................................................................................................121
3.12 cAMELDestinationNumber...............................................................................................................................122
3.13 cAMELInitCFIndicator.....................................................................................................................................122
3.14 cAMELSMSInformation...................................................................................................................................123
3.15 chargeAreaCode................................................................................................................................................123
3.16 calledChargeAreaCode......................................................................................................................................124
3.17 callEmlppPriority/ callerDefaultEmlppPriority/calledEmlppPriority...............................................................124
3.18 camelphase.........................................................................................................................................................124
3.19 cARP..................................................................................................................................................................124
3.20 Category.............................................................................................................................................................125
3.21 chargedParty......................................................................................................................................................125
3.22 classmark3.........................................................................................................................................................125
3.23 concatenatedSMSReferenceNumber.................................................................................................................125
3.24 csReference........................................................................................................................................................126
3.25 csaReference......................................................................................................................................................126
3.26 cUGIndex...........................................................................................................................................................127
3.27 cUGOutgoingAccessIndicator...........................................................................................................................127
3.28 cUGInterlockCode.............................................................................................................................................127
3.29 cUGOutgoingAccessUsed/ cUGIncomingAccessUsed.....................................................................................127
3.30 causeForTerm....................................................................................................................................................127
3.31 cmnFlag.............................................................................................................................................................128
3.32 defaultCallHandling /defaultSMSHandling.......................................................................................................129
3.33 destinationNumber.............................................................................................................................................129
3.34 destinationRoutingAddress................................................................................................................................129
3.35 Diagnostics........................................................................................................................................................129
3.36 disconnectParty..................................................................................................................................................131
3.37 eaSubscriberInfo................................................................................................................................................131
3.38 eCategory...........................................................................................................................................................131
3.39 emsDigits...........................................................................................................................................................131
3.40 emsKey..............................................................................................................................................................132
3.41 equipmentId.......................................................................................................................................................132
3.42 equipmentType..................................................................................................................................................132
3.43 eventTimeStamps...............................................................................................................................................132
3.44 firstmccmnc/intermediatemccmnc/lastmccmnc................................................................................................133
3.45 fnur.....................................................................................................................................................................133
Issue 1.00 (2008-02-25)
Page 8 of 173
CONFIDENTIAL
3.46 freeFormatData..................................................................................................................................................134
3.47 freeFormatDataAppend.....................................................................................................................................134
3.48 globalAreaID / changeOfglobalAreaID.............................................................................................................135
3.49 guaranteedBitRate..............................................................................................................................................135
3.50 gsm-SCFAddress...............................................................................................................................................136
3.51 groupCallType...................................................................................................................................................136
3.52 groupCallReference...........................................................................................................................................136
3.53 hLC....................................................................................................................................................................136
3.54 hotbillingTag......................................................................................................................................................137
3.55 interrogationResult............................................................................................................................................137
3.56 imeiCheckEvent.................................................................................................................................................137
3.57 imeiStatus..........................................................................................................................................................137
3.58 initialCallAttemptFlag.......................................................................................................................................138
3.59 interactionWithIP...............................................................................................................................................138
3.60 iSDN-BC............................................................................................................................................................138
3.61 lcsCause.............................................................................................................................................................138
3.62 lcsClientIdentity.................................................................................................................................................138
3.63 lcsClientType.....................................................................................................................................................139
3.64 lcsPriority...........................................................................................................................................................139
3.65 lcsQos................................................................................................................................................................139
3.66 levelOfCAMELService.....................................................................................................................................140
3.67 lLC.....................................................................................................................................................................140
3.68 location / changeOfLocation..............................................................................................................................140
3.69 locationEstimate................................................................................................................................................141
3.70 locationType......................................................................................................................................................141
3.71 maximumBitRate...............................................................................................................................................142
3.72 maximumNumberOfSMSInTheConcatenatedSMS..........................................................................................142
3.73 MCTType...........................................................................................................................................................142
3.74 measureDuration................................................................................................................................................143
3.75 messageReference..............................................................................................................................................143
3.76 mlc-Number.......................................................................................................................................................143
3.77 msClassmark / changeOfClassmark..................................................................................................................143
3.78 modemType.......................................................................................................................................................144
3.79 molr-Type...........................................................................................................................................................144
3.80 mSCAddress......................................................................................................................................................144
3.81 mscIncomingCircuit / mscOutgoingCircuit......................................................................................................144
3.82 mscIncomingROUTE / mscOutgoingROUTE..................................................................................................145
3.83 mscIncomingRouteAttribute / mscOutgoingRouteAttribute.............................................................................145
3.84 mscServerIndication..........................................................................................................................................145
3.85 networkCallReference.......................................................................................................................................145
3.86 networkOperatorId.............................................................................................................................................146
3.87 notificationToMSUser.......................................................................................................................................146
Issue 1.00 (2008-02-25)
Page 9 of 173
CONFIDENTIAL
03-MSOFTX3000 V100R006C05 ASN.1
CDR Description
3.88 numberOfDPEncountered..................................................................................................................................146
3.89 numberOfForwarding........................................................................................................................................146
3.90 originalCalledNumber.......................................................................................................................................146
3.91 origination..........................................................................................................................................................147
3.92 orgMSCId..........................................................................................................................................................147
3.93 orgRNCorBSCId................................................................................................................................................147
3.94 partialRecordType..............................................................................................................................................147
3.95 partyRelCause....................................................................................................................................................148
3.96 portedflag...........................................................................................................................................................148
3.97 positioningData..................................................................................................................................................148
3.98 privacyOverride.................................................................................................................................................149
3.99 radioChanRequested/ radioChanUsed / changeOfRadioChan..........................................................................149
3.100 rateIndication...................................................................................................................................................150
3.101 recordingEntity................................................................................................................................................150
3.102 recordExtensions..............................................................................................................................................150
3.103 recordNumber..................................................................................................................................................151
3.104 recordType.......................................................................................................................................................151
3.105 redirectingnumber............................................................................................................................................151
3.106 redirectingcounter............................................................................................................................................152
3.107 resourceChargeIPnumber................................................................................................................................152
3.108 Roaming number.............................................................................................................................................152
3.109 routingNumber.................................................................................................................................................152
3.110 sequenceNumber..............................................................................................................................................152
3.111 servedIMEI......................................................................................................................................................153
3.112 servedIMSI/calledIMSI...................................................................................................................................153
3.113 servedMSISDN................................................................................................................................................154
3.114 serviceCentre...................................................................................................................................................155
3.115 serviceKey.......................................................................................................................................................155
3.116 smsResult.........................................................................................................................................................155
3.117 speechVersionSupported/speechVersionUsed.................................................................................................155
3.118 systemType......................................................................................................................................................156
3.119 supplServiceUsed/supplService.......................................................................................................................156
3.120 ssAction...........................................................................................................................................................159
3.121 ssActionResult.................................................................................................................................................160
3.122 ssParameters....................................................................................................................................................160
3.123 smstext.............................................................................................................................................................160
3.124 smsUserDataType............................................................................................................................................160
3.125 selectedCIC......................................................................................................................................................161
3.126 sequenceNumberOfTheCurrentSMS...............................................................................................................161
3.127 subscriberCategory..........................................................................................................................................162
3.128 tariffCode.........................................................................................................................................................162
3.129 transparencyIndicator......................................................................................................................................162
Issue 1.00 (2008-02-25)
Page 10 of 173
CONFIDENTIAL
3.130 typeOfSubscribers............................................................................................................................................163
3.131 Usertype...........................................................................................................................................................163
3.132 ussdCodingScheme..........................................................................................................................................163
3.133 ussdString........................................................................................................................................................163
3.134 ussdNotifyCounter...........................................................................................................................................163
3.135 ussdRequestCounter........................................................................................................................................164
3.136 ussdCallBackFlag............................................................................................................................................164
3.137 uuslType...........................................................................................................................................................164
3.138 voiceIndicator..................................................................................................................................................164
3.139 zoneCode.........................................................................................................................................................164
4 ASN.1 Description of the CDR File...........................................................................................166

5 Examples of CDRs......................................................................................................................167
6 Revision History..........................................................................................................................170
Issue 1.00 (2008-02-25)
Page 11 of 173
CONFIDENTIAL
Figures
Encoding diagram when the value of tag ranges from 0 to 30 (inclusive)...................................17
Encoding diagram when the value of tag is equal to or more than 31.........................................17
Structure of a CDR file....................................................................................................................22
Binary code stream of the ASN.1 CDR file....................................................................................23
Call duration...................................................................................................................................119
Method of splitting the short message..........................................................................................126
Structure of the IMEI.....................................................................................................................153
Structure of the IMSI.....................................................................................................................154
Structure of the MSISDN...............................................................................................................154
Issue 1.00 (2008-02-25)
Page 13 of 173
CONFIDENTIAL
Tables
MOC record......................................................................................................................................25
MOC emergency record...................................................................................................................36
MOC, call forwarding record..........................................................................................................46
MTC record.......................................................................................................................................57
Roaming record................................................................................................................................68
Incoming gateway record.................................................................................................................72
Outgoing gateway record.................................................................................................................76
Transit record....................................................................................................................................80
SMS-MO record...............................................................................................................................84
SMS-MT record................................................................................................................................87
LCS-MT record................................................................................................................................90
LCS-MO record................................................................................................................................93
LCS-NI record..................................................................................................................................95
SS-action record................................................................................................................................98
HLR interrogation record..............................................................................................................100
Common equipment usage record................................................................................................102
Terminating CAMEL call attempt record....................................................................................104
IMEI ticket......................................................................................................................................109
Location update (VLR) record......................................................................................................110
Description of the time information..............................................................................................119
The correlation between CDRs and examples.............................................................................167
Issue 1.00 (2008-02-25)
Page 15 of 173
CONFIDENTIAL
ASN.1 Encoding Format
1.1 ASN.1 Encoding Format

ASN.1 is short for Abstract Syntax Notation One.
ASN.1 is regarded as a high-level protocol language. It can be used to clearly describe the
complex data structures, and it is widely accepted as the syntax standard for the application
layer protocols.
ASN.1 provides protocol designers with simple types, for instance, integer, Boolean, and octet
string. Based on these simple types, the protocol designer can construct more complex data
types.
More complex data types can be built from a set of simple types by using the unique Tags.
For example, a CDR can be structured with a serial of combinations of data fields. Each data
field can be an encoding unit or a combination of several encoding units.
An encoding unit consists of 4 components at most:
Identifier octets (also called Tag)
For details, see section 1.2.1"Encoding Rules of Identifier Octets."
Length octets
For details, see section 1.2.2"Encoding Rules of Length Octets."
Contents octets
For details, see section 1.2.3"Encoding Rules of Contents Octets."
End-of-contents octets
They are used only in indefinite length encoding mode. For details, see section
1.2.4"Encoding Rules of End-of-Contents Octets."
1.2 ASN.1 Encoding Format

This section describes the encoding rules of each ASN.1 unit and the CDR file structure.
1.2.1 Encoding Rules of Identifier Octets

The identifier octet identifies the protocol data type corresponding to this encoding unit. The
encoding is classified into the following cases:
Case 1
A single octet is used when the value of tag ranges from 0 to 30 (inclusive). The meaning of
each bit is as follows:
Issue 1.00 (2008-02-25)
Page 16 of 173
CONFIDENTIAL
Bits 8 and 7 specify the class identifiers of the data. The values are Universal-00,
Application-01, Context-Specific-10, and Private-11.
Bit 6 specifies whether the data unit is primitive or constructed. The values are Primitive0 and Construct-1.
Bits 5-1 specify the class numbers, that is, number of tag.
Universal is a basic class defined in the ASN.1 specifications. It is used to allocate tags for the basic
class. For example, Boolean is used when the value of Tag is 1.
Application is seldom used, and therefore it is not described here.
Context-Specific is used to define the class types.
Private can be negotiated based on the actual conditions.
Primitive indicates that the minimum ASN encoding unit is applied for the field.
Construct indicates that the field is composed of multiple ASN encoding units.
Figure 1.1 Encoding diagram when the value of tag ranges from 0 to 30 (inclusive)
8
7
6
5
4
3
2
1
+-------+---+------------------+
1 CLASS P/C TAG NUMBER
+------------------------------+
Bits 8-7: Class identifier:
+----------------------------+
Bit: 8
7
+----------------------------
Universal
0
0
Application
0
1
Context-specific
1
0
Private
1
1
+----------------------------+
Bit 6 : Primitive (0) or
Constructed (1)
Bits 5-1: binary integer with bit 5 as msb
Case 2
A leading octet together with several subsequent octets is used when the value of the tag is
equal to or more than 31.
Bits 8, 7, and 6 of the leading octet are the same as those of the single octet; bits 5-1 of
the leading octet are 11111.
The subsequent octets comply with the following rules:
Bit 8 of all the subsequent octets, except for the last one, is 1.
The value of bits 7-1 from the first subsequent octet to the last subsequent octet is
equal to the tag number.
Bits 7-1 of the first subsequent octet cannot be all 0s.
For details, see Figure 1.2.

Figure 1.2 Encoding diagram when the value of tag is equal to or more than 31
8
7
6
5
4
3
2
1
+-------+---+---+---+---+---+---
1 CLASS P/C 1 1 1 1 1
Issue 1.00 (2008-02-25)
Page 17 of 173
CONFIDENTIAL
+-------------------------------+
Bits 8-7: Class identifier as for single octet id
Bit 6 : Primitive (0) or
Constructed (1)
Bits 5-1: all bits set to 1
Subsequent octets are encoded as follows:

8
7
6
5
4
3
2
1
+---+--------------------------- first
2 1 NUMBER of TAG (msb)
subsequent
+-------------------------------
.
.
.
.
+------------------------------- last
0 NUMBER of TAG (lsb)
subsequent
+-------------------------------+
Bits 8 : set to 1 in all non-last subsequent
octets
Bits 7-1: Bits 7-1 of all subsequent octets
encoded as a binary integer equal to
the tag number with bit 7 of the first
subsequent octet as most significant
bit.
1.2.2 Encoding Rules of Length Octets

The length octets identify the length of the content fields, without the length of other fields.
There are three modes for encoding length octets: short, long, and indefinite. The indefinite
encoding mode is not applied in ASN.1 CDRs; therefore, it is not described in the subsequent
sections.
Short Encoding Mode

A single octet is used when the value of the length octets is equal to or less than 127.
Bit 8 is 0.
Bits 7-1 specify the length.
If L is equal to 26H, the length is encoded as 0010,0110.

8
7
6
5
4
3
2
1
+----------------------------
1 0
L
L
L
L
L
L
L
+----------------------------+
LLLLLLL represents the length of the content
Long Encoding Mode

More octets are used when the value of the length octets is more than 127.
8
7
6
5
4
3
2
1
+---+-------------------------
1 1
0 < n < 127
+-----------------------------+
+-----------------------------
Issue 1.00 (2008-02-25)
Page 18 of 173
CONFIDENTIAL
2 L
L
L
L
L
L
L
L
+-----------------------------+
...
+-----------------------------
n+1 L
L
L
L
L
L
L
L
+-----------------------------+
LLLLLLL represents the length of the content
Bit 8 of the first octet is 1 fixedly and bits 1-7 specify the number of octets occupied by
the length.
The second octet to the n+1 octet specify the value of the length.
1.2.3 Encoding Rules of Contents Octets

The content octets can be null, or a single octet, or more octets. The value of the content
octets depends on the data class it stands for.
The content octets are encoded as follows:
8
7
6
5
4
3
2
1
+------------------------------
most significant byte
octet 1
+------------------------------
octet 2
+------------------------------
.
.
.
.
+------------------------------
least significant byte
octet n
+------------------------------+
The following describes different data classes:
BOOLEAN
This class can be encoded only in primitive mode.
The false encoding is as follows:
Tag
Length
Value
+------------------------------
01H
01H 0000, 0000
+------------------------------
The true encoding is as follows (with any of bits is not 0):

Tag
Length
Value
+------------------------------
01H
01H 1111, 1011
+------------------------------
NULL
This class can be encoded only in primitive mode and has only one value. Therefore, if
you do not fill the value, it does not consume the space.
Tag
Length
Value
+------------------------------
05H
00H
Issue 1.00 (2008-02-25)
Page 19 of 173
CONFIDENTIAL
+------------------------------
INTEGER
This class can be encoded only in primitive mode. It is classified into the positive and the
negative. The negative number is not applied in the ASN.1 CDRs; therefore, it is not
described in the subsequent sections.
For the positive number, if the highest bit is 0, this class is encoded directly; if the
highest bit is 1, an octet with all 0s is added before the highest bit, that is, the code-filling
mode is adopted. For example, 250 is encoded as follows:
Tag
Length
Value
+-------------------------------------
02H
02H 0000,0000 1111,1010

+-------------------------------------
ENUMERATED
The encoding mode of this class is the same as that of the INTEGER class.
BIT STRING
This class can be encoded in primitive mode or in structured mode. The following takes
the bit string 1011011101011'B as an example to describe the two modes for encoding.
Primitive
Tag
Length
Value
+------------------------------------------
03H
03H
03H
10110111 01011xxx
+------------------------------------------
Note: An octet is added before the bit string '1011011101011'B and its value ranges from
0 to 7. This octet indicates the number of bits filled after the bit string and is mainly
applied when the bit string is not the multiple of number 8.
Constructed
The constructed mode is used when certain encodings are still unsure. The bit string
'1011011101011'B is encoded as follows:
Tag
Length
Value
+----------------------------------------------
03H
80H
T
L
V
03H
02H 00H 10110111
03H
02H 03H 01011xxx
00H
00H
+-----------------------------------------------
Note: In this case, the length of the whole bit string uses the indefinite encoding mode
OCTET STRING
The encoding rule of this class is the same as that of the BIT STRING class. This class
takes an octet as a unit; therefore, you need not fill any bit any more.
SET
This class can be encoded only in constructed mode. Each member is encoded in the
TLV format.
The following takes MOC {recordType ENUMERATED, callDuration
INTEGER }:={ recordType 0,callDuration 11} as an example:
Tag
Length
Value
+--------------------------------------------
Issue 1.00 (2008-02-25)
Page 20 of 173
CONFIDENTIAL
16H
80H
T
L
V
02H
01H 0000 0000
02H
01H 0000 1011
+--------------------------------------------
SEQUENCE
The encoding mode of this class is the same as that of the SET class. The sequence of
members of this class must be consistent with the defined sequence, but this requirement
does not apply to the SET class.
SET OF
The encoding mode of this class is the same as that of the SET class.
SEQUENCE OF
The encoding mode of this class is the same as that of the SEQUENCE class.
Other types are not common; therefore, they are not described in the subsequent sections.
1.2.4 Encoding Rules of End-of-Contents Octets

The end-of-contents octets exist only in the indefinite mode; therefore, they are not described
in the subsequent sections.
1.2.5 Structure of CDR Files

If a CDR file is of the SEQUENCE type and uses the TLV format, its value is composed of
following parts:
Header: It is the header of the CDR file and the TAG value is A0.
Event Record: It is the content of the CDR file. SEQUENCE OF indicates that the event
record can be composed of many CDRs and the TAG value of the callEventRecords is
A1.
Trailer: It is the trailer of the CDR file and the TAG value is A2.
Extensions: The TAG value is A3, without contents. The length is 0.
For details, see Figure 1.1.
Issue 1.00 (2008-02-25)
Page 21 of 173
CONFIDENTIAL
Figure 1.1 Structure of a CDR file
Figure 1.2 takes the ASN.1 CDR file as an example to show its binary code stream.
Issue 1.00 (2008-02-25)
Page 22 of 173
CONFIDENTIAL
Figure 1.2 Binary code stream of the ASN.1 CDR file
The following shows the ASN.1 files corresponding to the figure above:
ASN.1 BER
moCal l Record. dat
Decoded files
record no.: 0
recordType: moCallRecord
servedIMSI: 460007001002000
servedMSISDN: (91)8613720012000
callingNumber: (91)8613720012000
calledNumber: (A1)13720012010
roamingNumber: (A1)136755002201
recordingEntity: (91)86136755002
mscIncomingROUTE: TO_BSC1
mscOutgoingROUTE: TO_BSC2
location: LAC-3001. CellID-0001
Issue 1.00 (2008-02-25)
Page 23 of 173
CONFIDENTIAL
basicService: teleService(11)
msClassmark: 021C00
answerTime: 070809141502
releaseTime: 070809141513
callDuration: 11
radioChanRequested: fullRateChannel
radioChanUsed: halfRate
causeForTerm: normalRelease
diagnostics: gsm0408Cause(90)
callReference: 16 00 00 00 ED
additionalChgInfo: chargeIndicator-charge
networkcallReference: 16 05 A2 30 1B
mSCAddress: (91)86136755002
speechVersionSupported: 1
speechVersionUsed: 1
systemType: gERAN
chargedParty: callingParty
mscOutgoingCircuit: 1
orgRNCorBSCId:
orgMSCId:
01 0B
00 0B
callerDefaultEmlppPriority: EMLPP_CallPriorityLevel4(1)
globalAreaID:
64 F0 00 30 01 00 01
subscriberCategory: Common(A)
firstmccmnc: 64F000
lastmccmnc: 64F000
calledIMSI: 460007001002010
typeOfSubscribers:visiting
audioDataType:audio
disconnectparty:unknown
Issue 1.00 (2008-02-25)
Page 24 of 173
CONFIDENTIAL
Record Contents
The following tables describe the contents of each of the call and event records defined in the
present document. Each table contains the name of the field, a key indicating whether or not
the field is mandatory, and a description of the contents.
The key fields have the following meanings:
M: This field is mandatory and always present in this CDR.
O: This field is optional in this CDR.
C: This field is only available under certain conditions. This field is present if it is
available.
-: This field need not be encoded in this CDR.
2G: The MSOFTX3000functions as an MSC in a 2G network.
3G: The MSOFTX3000 functions as an MSC in a 3G network.
n: It specifies the number of "sequence" or "set".
The numbers in the brackets after field types specify the value range of this field length.
2.1 Mobile Originated Call Attempt

If the generation of these records is enabled, an MOC record shall be created for each
outgoing call attempt made by a mobile station. These MOC records shall be produced in the
originating MSC. Figure 1.1 lists the formats of MOC records.
Figure 1.1 MOC record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
Mobile originated.
CallEventRecordType =
0x00
(1)
servedIMSI
0x81
TBCD(3..8)
The IMSI of the calling

party.
servedIMEI
0x82
TBCD(8)
The IMEI of the calling

ME, if available.
servedMSISDN
0x83
ADRESS(2..9)
The primary MSISDN of

the calling party.
callingNumber
0x84
ADRESS (2..17)
The address of the calling

party.
Issue 1.00 (2008-02-25)
Page 25 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
calledNumber
0x85
ADRESS (2..17)
The address of the called

party, for example, the
number dialed by the
calling subscriber.
translatedNumber
0x86
ADRESS (2..17)
The called number after

digit translation within the
MSC (if applicable).
connectedNumber
0x87
ADRESS (2..17)
The number of the

connected party if it is
different from the Called
Number.
roamingNumber
0x88
ADRESS (2..17)
The Mobile Station

Roaming Number
employed to route this
connection, if applicable.
recordingEntity
0x89
ADRESS (2..9)
The E.164 number of the

visited MSC producing the
record (MSC/VLR
number: TON+NPI+MSC
identifier number).
mscIncomingROUTE
0xAA
IA5(1..32)
The MSC route on which

the call is originated,
usually from the BSC or
RNC.
mscOutgoingROUTE
0xAB
IA5(1..32)
The route on which the

call left the MSC.
location
0xAC
OCTET(8)
The identity of the cell or

the SAC at the time of
CDR creation, including
the location area code.
changeOfLocation
0xAD
SEQUENCE OF
( 23 * n )
A list of changes in
Location Area Code / Cell
Identifier each timestamped.
basicService
0xAE
OCTET(3)
The bearer or teleservice

employed.
transparencyIndicator
0x8F
ENUMERATED
Indicates whether the basic

service was used in
transparent or nontransparent mode. This
parameter is provided only
for those basic services
which may be employed in
both transparent and nontransparent mode.
(1)
Issue 1.00 (2008-02-25)
Page 26 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
changeOfService
0xB0
SEQUENCE OF
( (18..27) * n)
A list of changes of basic

service during a
connection each timestamped.
supplServicesUsed
0xB1
SEQUENCE OF
Supplementary services
invoked as a result of this
connection. This field shall
be present when one or
more supplementary
services have been
invoked.
(16 * n)
aocParameters
0xB2
OCTET(4..28)
The charge advice

parameters sent to the MS
on call setup.
changeOfAOCParms
0xB3
SEQUENCE OF
( 43 * n)
The new AOC parameters

sent to the MS, for
example, as a result of a
tariff switchover, including
the time at which the new
set was applied.
msClassmark
0x94
OCTET(2..3)
The mobile station

classmark employed on
call setup.
changeOfClassmark
0xB5
OCTET (16 )
A list of changes to the

classmark during the
setupTime
0x9F 81
49
OCTET(9)
The time stamp when the

Setup message or IAM
message is received from
the calling party side.
seizureTime
0x96
OCTET(9)

assignment at the calling
party side is completed.
alertingTime
0x9F 81
4A
OCTET(9)

Alerting message or ACM
the called party side.
answerTime
0x97
OCTET(9)

call is answered during a
successful connection.
releaseTime
0x98
OCTET(9)
The time stamp when

either of the calling or
called party releases the
traffic channel.
Issue 1.00 (2008-02-25)
Page 27 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
callDuration
0x99
INTEGER(1..2)
The chargeable duration of

the connection for
successful calls, the
holding time for call
attempts.
radioChanRequested
0x9B
ENUMERATED
The type of radio traffic

channel (full-rate or halfrate) requested by the MS.
(1)
radioChanUsed
0x9C
ENUMERATED
(1)
The type of radio channel

actually used (full-rate or
half-rate).
changeOfRadioChan
0xBD
OCTET (14..17 )

types of radio traffic
channels each timestamped.
causeForTerm
0x9E
INTEGER (1)
The reason for the release

of the connection.
diagnostics
0xBF 1F
INTEGER(4)
A more detailed reason for

the release of the
connection.
callReference
0x9F 20
OCTET(1..8)
A local identifier
distinguishing between
transactions on the same
MS.
sequenceNumber
0x9F 21
INTEGER(1)
The partial record

sequence number, only
present in case of partial
records.
additionalChgInfo
0xBF 22
SEQUENCE(3)
Charge/no charge indicator

and additional charging
parameters, when
available.
recordExtensions
0xBF 23
SET OF (11 * n)
A set of network or
manufacturer specific
extensions to the record.
Reserved for future use.
gsm-SCFAddress
0x9F 24
ADRESS(2..9)
The CAMEL server

serving the subscriber.
Shall be present only if
CAMEL is applied.
Issue 1.00 (2008-02-25)
Page 28 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
serviceKey
0x9F 25
INTEGER(1..4)
The CAMEL service logic

to be applied. Shall be
present only if CAMEL is
applied.
networkCallReference
0x9F 26
OCTET(1..8)
An identifier to correlate
call taking place in
different network nodes.
CAMEL is applied.
mSCAddress
0x9F 27
ADRESS(2..9)
The E.164 number

assigned to the MSC that
generated the network call
reference.
cAMELInitCFIndicator
0x9F 28
BOOLEAN(1)
Indicates that the CAMEL

server initiates call
forwarding in the CFW
record.
defaultCallHandling
0x9F 29
ENUMERATED
Indicates whether a
CAMEL call encounters
default call handling. This
field shall be present only
if default call handling has
been applied.
(1)
fnur
0x9F 2D
ENUMERATED
(1)
aiurRequested
0x9F 2E
ENUMERATED
(1)
The user data rate applied

for the connection in the
fixed network. Shall only
be present for 2G HSCSD
connections and for
UMTS data connections.
The total Air Interface
User Rate Requested by
the MS at call setup. Shall
only be present for nontransparent HSCSD
connections.
speechVersionSupported
0x9F 31
OCTET(1)
The speech version

supported by the MS with
highest priority indicated
by MS.
speechVersionUsed
0x9F 32
OCTET(1)
The speech version used

for that call.
Issue 1.00 (2008-02-25)
Page 29 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
numberOfDPEncountered
0x9F 33
INTEGER(1)
Number that counts how

often armed detection
points (TDP and EDP)
were encountered. Shall be
applied.
levelOfCAMELService
0x9F 34
BIT STRING(2)
The indicator for the

complexity of the CAMEL
feature used. Shall be
applied.
freeFormatData
0x9F 35
OCTET(1..160)
This field contains data

sent by the gsmSCF in the
FCI messages. The data
can be sent either in one
FCI message or several
FCI messages with append
indicator. Shall be present
only if CAMEL is applied.
cAMELCallLegInformation
0xBF 36
SEQUENCE OF
A set of CAMEL
information IEs. Each of
these IEs contains
information related to one
outgoing CAMEL call leg.
CAMEL is applied.
((104..124) * n)
freeFormatDataAppend
0x9F 37
BOOLEAN (1)
Indicates that free format

data from this CDR is to
be appended to free format
data in previous partial
CDR.
defaultCallHandling-2
0x9F 38
ENUMERATED
Indicates whether a
CAMEL call encountered
default call handling for
the second service such as
the dialed service. This
field shall be present only
if default call handling has
been applied.
(1)
gsm-SCFAddress-2
Issue 1.00 (2008-02-25)
0x9F 39
ADRESS (2..9)
Indicates the CAMEL

server serving the
subscriber for the second
service such as the dialed
service. Shall be present
only if CAMEL is applied
for the second service.
Page 30 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
serviceKey-2
0x9F 3A
INTEGER (1..4)
Indicates the CAMEL

service logic to be applied
for the second service such
as the dialed service. Shall
be present only if CAMEL
is applied for the second
service.
freeFormatData-2
0x9F 3B
OCTET(1..160)
Indicates the data sent by

the gsmSCF in the FCI
message(s) for the second
service. The data can be
sent either in one FCI
message or several FCI
messages with append
CAMEL is applied for the
second service.
freeFormatDataAppend-2
0x9F 3C
BOOLEAN (1)

data for the second service
such as the dialed service
from this CDR is to be
appended to free format
CDR. Shall be present
systemType
0x9F 3D
ENUMERATED
This field indicates the use

of GERAN, UTRAN (or a
value of unknown). This
field is present when either
the UTRAN or GERAN
air-interface is used on call
setup.
(1)
rateIndication
0x9F 3E
OCTET(1)
Present if "rate adaptation"

parameters for the basic
service were signaled
between the MS/UE and
the network, see TS
24.008.
partialRecordType
0x9F 45
ENUMERATED
The event that caused the

generation of a partial
record. This field is
mandatory in case of
partial records.
(1)
Issue 1.00 (2008-02-25)
Page 31 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
guaranteedBitrate
0x9F 46
ENUMERATED
The bit-rate the UMTS

bearer service shall
guarantee to the user or
application. This field may
be used to facilitate
admission control based
on available resources, and
for resource allocation
within UMTS.
(1)
maximumBitrate
0x9F 47
ENUMERATED
(1)
modemType
0x9F 81
0B
ENUMERATED
The maximum bit-rate that

can be used to make code
reservations in the
downlink of the radio
interface. Its purpose is: 1)
to limit the delivered bitrate to applications or
external networks with
such limitations, 2) to
allow maximum wanted
user bit-rate to be defined
for applications able to
operate with different rates
(e.g. applications with
adapting codecs). Shall
only be present for UMTS
data connections.
The type of Modem used.
(1)
classmark3
0x9F 81
0C
OCTET(2)
The mobile station

classmark 3.
chargedParty
0x9F 81
0D
ENUMERATED
Indicates whether the

calling party or the called
party is charged for the
call.
(1)
originalCalledNumber
0x9F 81
0E
ADRESS (2..17)
The address of original

called party in CFW
record. It is invalid in the
MOC record.
chargeAreaCode
0x9F 81
11
OCTET(1..3)
The subscriber logical area

for distance charge.
calledChargeAreaCode
0x9F 81
12
OCTET(1..3)
The called party logical

area for distance charge.
mscOutgoingCircuit
0x9F 81
26
INTEGER (1..2)
The CIC, only present in

case of outgoing bear type
being TDM.
Issue 1.00 (2008-02-25)
Page 32 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
orgRNCorBSCId
0x9F 81
27
OCTET(3)
The SPC of f the RNC or

the BSC.
orgMSCId
0x9F 81
28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F 81
2A
OCTET(1)
The EMLPP priority of the

call. See 29.002.
callerDefaultEmlppPriority
0x9F 81
2B
OCTET(1)
The priority of the EMLPP

service registered by the
calling party. See 29.002.
eaSubscriberInfo
0x9F 81
2E
OCTET(3)
The calling subscriber's

information of Equal
Access.
selectedCIC
0x9F 81
2F
OCTET(3)
The selected code of

Carrier identification.
optimalRoutingFlag
0x9F 81
31
NULL
Shall be present when the

optimal routing function is
applied. Reserved for
future use.
optimalRoutingLateForwardFlag
0x9F 81
32
NULL

applied in the case of the
late forward. Reserved for
future use.
optimalRoutingEarlyForwardFlag
0x9F 81
33
NULL

early forward. Reserved
for future use.
portedflag
0x9F 81
34
ENUMERATED
Indicates whether the user

is ported. Reserved for
future use.
(1)
calledIMSI
0x9F 81
35
TBCD(3..8)
The IMSI of the called

party.
globalAreaID
0x9F 81
3C
OCTET(7)
The GCI of the GSM

network or the SAI of the
WCDMA network.
changeOfglobalAreaID
0xBF 81
3D
SEQUENCE OF
A list of changes in the

GCI / SAI each timestamped.
0x9F 81
3E
OCTET(1)
subscriberCategory
Issue 1.00 (2008-02-25)
(22 * n)
The category of
subscribers.
Page 33 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
firstmccmnc
0x9F 81
40
OCTET(3)
The MCC and MNC of the

network when the call is
initiated.
intermediatemccmnc
0x9F 81
41
OCTET(3)
lastmccmnc
0x9F 81
42
OCTET(3)

served. Only present after
handover.
cUGOutgoingAccessIndicator
0x9F 81
43
ENUMERATED
The access indicator of the

CUG call.
(1)
cUGInterlockCode
0x9F 81
44
OCTET(4)
Network code + CUG

interlock
cUGOutgoingAccessUsed
0x9F 81
45
ENUMERATED

calling party and called
party are in the same CUG
group.
(1)
cUGIndex
0x9F 81
46
OCTET(2)
The index of the CUG

subscribers.
interactionWithIP
0x9F 81
47
NULL (0)
In the case of interaction

between SSP and IP,
GsmSCF play
announcement to SSP and
start charging.
hotBillingTag
0x9F 81
48
INTEGER(1)
Indicates that the charged

party is a subscriber who
subscribes to the hot
billing service. Shall be
present only if the hot
charging function is
applied.
voiceIndicator
0x9F 81
4B
ENUMERATED
Indicates that the

announcement is played
for the local office or other
offices when the call is
released.
0x9F 81
4C
ENUMERATED
0x9F 81
4D
ENUMERATED
bCategory
callType
Issue 1.00 (2008-02-25)
C
C
C
C
(1)
(1)
(1)

called party is busy or idle.
Indicates the call type,
such as the intra-office,
incoming, outgoing,
tandem, or unknown.
Page 34 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
resourceChargeIPnumber
0x9F 81
4E
ADRESS (2..17)
The address of the IP

equipment that plays the
announcement in the case
of resource charging.
groupCallType
0x9F 81
50
ENUMERATED(1)
The type of a group call.
groupCallReference
0x9F 81
51
OCTET(4)
The reference number of a

group call.
uus1Type
0x9F 81
52
ENUMERATED(1)
The type of UUS1.
eCategory
0x9F 81
57
INTEGER(1..2)
The enhanced subscriber

category.
tariffCode
0x9F 81
59
INTEGER(1)
The tariff code.
disconnectparty
0x9F 81
5A
ENUMERATED(1)
The party who releases the

call first.
csReference
0x9F 81
5C
OCTET(1..8)
The call segment reference

number.
csaReference
0x9F 81
5D
INTEGER (1..4)
The call segment

association reference
number.
camelphase
0x9F 81
5E
ENUMERATED(1)
The CAMEL version

number.
networkOperatorId
0x9F 81
5F
OCTET(1)
The ID of virtual
operators.
typeOfSubscribers
0x9F 81
60
ENUMERATED(1)
The type of roaming

subscriber.
audioDataType
0x9F 81
61
ENUMERATED(1)
Indicates whether the data

service or speech service is
employed by a subscriber.
usertype
0x9F 81
63
ENUMERATED(1)
Indicates the user type.
recordNumber
0x9F 81
68
INTEGER
The serial number of a

CDR.
partyRelCause
0xBF 81
6C
PartyRelCause
Indicates the cause of call

release.
zoneCode
0x9F 81
70
OCTET (2)
The zone code of a cell.
MCTType
0x9F 81
75
ENUMERATED(1)
The MCT record type.
Issue 1.00 (2008-02-25)
Page 35 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
cARP
0x9F 81
76
INTEGER(1)
The CARP value

registered by the
subscriber.
2.2 Mobile Originated Emergency Call Attempt

If the generation of MOC records is enabled, an MOC emergency record shall be created for
each outgoing emergency call attempt made by a mobile station. These records shall be
produced in the originating MSC. Figure 1.2 lists the formats of MOC emergency records.
Figure 1.2 MOC emergency record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
Mobile originated.
CallEventRecordType = 0x00
(1)
servedIMSI
0x81
TBCD(3..8)
The IMSI of the calling party

in case of an emergency call
with a SIM card.
servedIMEI
0x82
TBCD(8)
The IMEI of the calling

mobile equipment if
available.
servedMSISDN
0x83
ADRESS(2..9)
The primary MSISDN of the

calling party.
callingNumber
0x84
ADRESS (2..17)

party.
calledNumber
0x85
ADRESS (2..17)

party e.g. the number dialed
by the calling subscriber.
translatedNumber
0x86
ADRESS (2..17)
The called number after digit

translation within the MSC
(if applicable).
connectedNumber
0x87
ADRESS (2..17)
The number of the connected

party if it is different from
the Called Number.
roamingNumber
0x88
ADRESS (2..17)
The Mobile Station Roaming

Number employed to route
this connection.
Issue 1.00 (2008-02-25)
Page 36 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
recordingEntity
0x89
ADRESS(2..9)

record (MSC/VLR number:
TON+NPI+MSC identifier
number).
mscIncomingROUTE
0xAA
IA5(1..32)
The MSC route on which the

call is originated, usually
from the BSC or RNC.
mscOutgoingROUTE
0xAB
IA5(1..32)
The route on which the call

left the MSC.
location
0xAC
OCTET(8)
The identity of the cell or the

SAC at the time of CDR
creation, including the
location area code.
changeOfLocation
0xAD
SEQUENCE OF
A list of changes in Location

Area Code / Cell Identifier
each time-stamped.
( 23 * n )
basicService
0xAE
OCTET(3)

employed. Teleservice
'emergency call' in the case
of the MOC emergency
record.
0x8F
ENUMERATED

service was used in
both transparent and nontransparent modes.
(1)
changeOfService
0xB0
SEQUENCE OF
( (18..27) * n)

service during a connection
each time-stamped.
supplServicesUsed
0xB1
SEQUENCE OF
be present when one or more
supplementary services have
been invoked.
(16 * n)
aocParameters
Issue 1.00 (2008-02-25)
0xB2
OCTET(4..28)
The charge advice parameters

sent to the MS on call setup.
Page 37 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
changeOfAOCParms
0xB3
SEQUENCE OF

sent to the MS e.g. as a result
of a tariff switchover,
including the time at which
the new set was applied.
( 43 * n)
msClassmark
0x94
OCTET(2..3)
The mobile station classmark

employed on call setup.
changeOfClassmark
0xB5
OCTET (16 )

connection each timestamped
setupTime
0x9F
81 49
OCTET(9)

message is received from the
calling party side.
seizureTime
0x96
OCTET(9)

party side is completed.
alertingTime
0x9F
81 4A
OCTET(9)

called party side.
answerTime
0x97
OCTET(9)
The time stamp when the call

is answered during a
releaseTime
0x98
OCTET(9)
The time stamp when either

the calling or the called party
releases the traffic channel.
callDuration
0x99
INTEGER(1..2)

the connection for successful
calls, the holding time for
call attempts.
radioChanRequested
0x9B
ENUMERATED

channel (full-rate or half-rate)
requested by the MS.
(1)
radioChanUsed
0x9C
ENUMERATED
(1)

half-rate).
changeOfRadioChan
0xBD
OCTET (14..17 )
A list of changes to the types

of radio traffic channels each
time-stamped.
causeForTerm
0x9E
INTEGER(1)
The reason for the release of

the connection.
Issue 1.00 (2008-02-25)
Page 38 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
diagnostics
0xBF
1F
INTEGER(4)

the release of the connection.
callReference
0x9F
20
OCTET(1..8)
A local identifier
transactions on the same MS.
It is also used to identify all
partial records and
transactions belonging to the
same connection.
sequenceNumber
0x9F
21
INTEGER(1)
The partial record sequence

number, only present in case
of partial records.
additionalChgInfo
0xBF
22
SEQUENCE(3)

parameters, when available.
recordExtensions
0xBF
23
SET OF (11 * n)
A set of network or
gsm-SCFAddress
0x9F
24
ADRESS(2..9)
The CAMEL server serving

the subscriber. Shall be
applied.
serviceKey
0x9F
25
INTEGER(1..4)
The CAMEL service logic to

be applied. Shall be present
only if CAMEL is applied. It
is not available in the
emergency call.
0x9F
26
OCTET(1..8)
transactions on the same call
taking place in different
network nodes.
mSCAddress
0x9F
27
ADRESS(2..9)
The E.164 number assigned

to the MSC that generated
the network call reference.
0x9F
28
BOOLEAN(1)

record.
Issue 1.00 (2008-02-25)
Page 39 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
defaultCallHandling
0x9F
29
ENUMERATED
Indicates whether a CAMEL

call encounters default call
handling. This field shall be
present only if default call
handling has been applied. It
emergency call.
0x9F
2D
ENUMERATED
0x9F
2E
ENUMERATED
fnur
aiurRequested
(1)
(1)
(1)
The user data rate applied for

the connection in the fixed
network. Shall only be
present for 2G HSCSD
connections and for UMTS
data connections.
The total Air Interface User
Rate Requested by the MS at
call setup. Shall only be
present for non-transparent
HSCSD connections.
0x9F
31
OCTET(1)
The speech version supported

by the MS with highest
priority indicated by MS.
speechVersionUsed
0x9F
32
OCTET(1)
The speech version used for

that call.
0x9F
33
INTEGER(1)

often armed detection points
(TDP and EDP) were
encountered. Shall be present
emergency call.
levelOfCAMELService
0x9F
34
BIT STRING(2)

feature used. Shall be present
emergency call.
Issue 1.00 (2008-02-25)
Page 40 of 173
CONFIDENTIAL
Field
freeFormatData
2G
3G
TAG
TYPE
Description
0x9F
35
OCTET(1..160)
This field contains data sent

by the gsmSCF in the FCI
messages. The data can be
only if CAMEL is applied for
the second service. Shall be
applied. It is not available in
the emergency call.
0xBF
36
SEQUENCE OF
A set of CAMEL information

IEs. Each of these IEs
contains information related
to one outgoing CAMEL call
leg. Shall be present only if
CAMEL is applied. It is not
available in the emergency
call.
((104..124) * n)
0x9F
37
BOOLEAN (1)

data from this CDR is to be
appended to free format data
in previous partial CDR.
CAMEL is applied. It is not
call.
0x9F
38
ENUMERATED
Indicates whether a CAMEL

call encountered default call
handling for the second
service. This field shall be
present only if default call
handling has been applied. It
emergency call.
0x9F
39
ADRESS (2..9)
gsm-SCFAddress-2
Issue 1.00 (2008-02-25)
(1)
Indicates the CAMEL server

serving the subscriber for the
second service such as the
dialed service. Shall be
applied for the second
service. It is not available in
the emergency call.
Page 41 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
serviceKey-2
0x9F
3A
INTEGER (1..4)
Indicates the CAMEL service

logic to be applied for the
service. It is not available in
the emergency call.
freeFormatData-2
0x9F
3B
OCTET(1..160)
Indicates the data sent by the

gsmSCF in the FCI
service. The data can be sent
either in one FCI message or
several FCI messages with
append indicator. Shall be
service. Shall be present only
if CAMEL is applied for the
second service. It is not
call.
0x9F
3C
BOOLEAN (1)

data for the second service
such as the dialed service
appended to free format data
in previous partial CDR.
CAMEL is applied for the
second service. It is not
call.
0x9F
3D
ENUMERATED
This field indicates the use of

GERAN, UTRAN (or a value
of unknown). This field is
present when either the
UTRAN or GERAN airinterface is used on call
setup.
0x9F
3E
OCTET(1)
systemType
rateIndication
Issue 1.00 (2008-02-25)
(1)

between the MS/UE and the
network, see TS 24.008.
Page 42 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
partialRecordType
0x9F
45
ENUMERATED

generation of a partial record.
This field is mandatory in
case of partial records.
0x9F
46
ENUMERATED
0x9F
47
ENUMERATED
0x9F
81 0B
ENUMERATED
guaranteedBitrate
maximumBitrate
modemType
(1)
(1)
(1)
The bit-rate the UMTS bearer

service shall guarantee to the
user or application. This field
may be used to facilitate
admission control based on
available resources, and for
resource allocation within
UMTS. Shall only be present
for UMTS data connections.
reservations in the downlink
of the radio interface. Its
purpose is: 1) to limit the
delivered bit-rate to
applications or external
networks with such
limitations, 2) to allow
maximum wanted user bitrate to be defined for
applications able to operate
with different rates (e.g.
applications with adapting
codecs). Shall only be
present for UMTS data
connections.
The type of Modem used.
(1)
classmark3
0x9F
81 0C
OCTET(2)
The mobile station classmark

3.
chargedParty
0x9F
81 0D
ENUMERATED
Indicates whether the calling

party or the called party is
charged for the call.
(1)
0x9F
81 0E
ADRESS (2..17)
The address of original called

party in CFW record. It is not
call.
chargeAreaCode
0x9F
81 11
OCTET(1..3)

0x9F
81 12
OCTET(1..3)
The called party logical area

Issue 1.00 (2008-02-25)
Page 43 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
mscOutgoingCircuit
0x9F
81 26
INTEGER (1..2)
The CIC, only present in case

of outgoing bear type being
TDM.
orgRNCorBSCId
0x9F
81 27
OCTET(3)
The SPC of the RNC or the

BSC.
orgMSCId
0x9F
81 28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F
81 2A
OCTET(1)

call. See 29.002.
0x9F
81 2B
OCTET(1)

eaSubscriberInfo
0x9F
81 2E
OCTET(3)

information of Equal Access.
selectedCIC
0x9F
81 2F
OCTET(3)
The selected code of Carrier

identification.
optimalRoutingFlag
0x9F
81 31
NULL

applied. Reserved for future
use.
optimalRoutingLateForwardFlag
0x9F
81 32
NULL

applied in the case of the late
forward. Reserved for future
use.
optimalRoutingEarlyForwardFla
g
0x9F
81 33
NULL

early forward. Reserved for
future use.
portedflag
0x9F
81 34
ENUMERATED
(1)
Indicates whether the user is

ported. Reserved for future
use.
calledIMSI
0x9F
81 35
TBCD(3..8)
The IMSI of the called party.
globalAreaID
0x9F
81 3C
OCTET(7)
The GCI of the GSM

WCDMA network.
0xBF
81 3D
SEQUENCE OF
(22 * n)
A list of changes in the GCI /

SAI each time-stamped.
0x9F
81 3E
OCTET(1)
The category of subscribers.
subscriberCategory
Issue 1.00 (2008-02-25)
Page 44 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
firstmccmnc
0x9F
81 40
OCTET(3)

initiated.
intermediatemccmnc
0x9F
81 41
OCTET(3)
lastmccmnc
0x9F
81 42
OCTET(3)

handover.
0x9F
81 43
ENUMERATED

CUG call.
(1)
cUGInterlockCode
0x9F
81 44
OCTET(4)
Network code + CUG

interlock
0x9F
81 45
ENUMERATED

party and called party are in
the same CUG group.
(1)
cUGIndex
0x9F
81 46
OCTET(2)

subscribers.
interactionWithIP
0x9F
81 47
NULL (0)

between SSP and IP,
GsmSCF play announcement
to SSP and start charging.
hotBillingTag
0x9F
81 48
INTEGER(1)

subscribes to the hot billing
service. Shall be present only
if the hot charging function is
applied.
voiceIndicator
0x9F
81 4B
ENUMERATED
Indicates that the

announcement is played for
the local office or other
released.
0x9F
81 4C
ENUMERATED
0x9F
81 4D
ENUMERATED
0x9F
81 4E
ADRESS (2..17)
bCategory
callType
Issue 1.00 (2008-02-25)
C
C
C
C
(1)
(1)
(1)
Indicates whether the called

party is busy or idle.
Indicates the call type, such
as the intra-office, incoming,
outgoing, tandem, or
unknown.
announcement in the case of
resource charging.
Page 45 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
groupCallType
0x9F
81 50
ENUMERATED(1)
groupCallReference
0x9F
81 51
OCTET(4)

group call.
uus1Type
0x9F
81 52
ENUMERATED(1)
The type of UUS1.
eCategory
0x9F
81 57
INTEGER(1..2)

category.
disconnectparty
0x9F
81 5A
ENUMERATED(1)

call first.
csReference
0x9F
81 5C
OCTET(1..8)

number.
csaReference
0x9F
81 5D
INTEGER (1..4)
The call segment association

reference number.
camelphase
0x9F
81 5E
ENUMERATED(1)
The CAMEL version number.
networkOperatorId
0x9F
81 5F
OCTET(1)
The ID of virtual operators.
typeOfSubscribers
0x9F
81 60
ENUMERATED(1)
The type of roaming

subscriber.
usertype
0x9F
81 63
ENUMERATED(1)
The user type.
recordNumber
0x9F
81 68
INTEGER
The serial number of a CDR.
partyRelCause
0xBF
81 6C
PartyRelCause

release.
2.3 Mobile Originated Call Forwarding Attempt

If the generation of MOC records is enabled in case of call forwarding, the forwarded-leg of
the call shall also result in the production of an MOC record in the MSC that forwards the
call. Figure 1.3 lists the formats of MOC call forwarding records.
Figure 1.3 MOC, call forwarding record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
Call forwarding.
0x64
(1)
Issue 1.00 (2008-02-25)
Page 46 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
servedIMSI
0x81
TBCD(3..8)
The IMSI of the forwarding

party.
servedIMEI
0x82
TBCD(8)
The IMEI of the

forwarding mobile
equipment if available.
servedMSISDN
0x83
ADRESS (2..9)
The MSISDN of the

forwarding party.
callingNumber
0x84
ADRESS (2..17)
The number of the calling

party if available at this
node.
calledNumber
0x85
ADRESS (2..17)
The address of the

"forwarded-to" party.
translatedNumber
0x86
ADRESS (2..17)

connectedNumber
0x87
ADRESS (2..17)
The number of the

connected party if it is
different from the Called
Number.
roamingNumber
0x88
ADRESS (2..17)
The Mobile Station

Roaming Number
connection, if applicable.
recordingEntity
0x89
ADRESS (2..9)

number).
mscIncomingROUTE
0xAA
IA5(1..32)
The MSC route on which

the call is originated at the
forwarding MSC.
mscOutgoingROUTE
0xAB
IA5(1..32)

left the forwarding MSC.
location
0xAC
OCTET(8)
The identity of the cell or

the SAC in which the call
is forwarded including the
location area code.
changeOfLocation
0xAD
SEQUENCE OF
Location Area Code / Cell
Identifier each timestamped.
( 23 * n )
Issue 1.00 (2008-02-25)
Page 47 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
basicService
0xAE
OCTET(3)

employed. It is not
available in the forwarding
record.
0x8F
ENUMERATED

service was used in
(1)
changeOfService
0xB0
SEQUENCE OF
( (18..27) * n)
supplServicesUsed
0xB1
SEQUENCE OF
(16 * n)

each time-stamped.
more supplementary
services have been
invoked.
aocParameters
0xB2
OCTET(4..28)
The charge advice

parameters sent to the MS
on call setup.
changeOfAOCParms
0xB3
SEQUENCE OF

sent to the MS e.g. as a
result of a tariff switchover,
including the time at which
the new set was applied.
( 43 * n)
msClassmark
0x94
OCTET(2..3)
The mobile station

classmark employed on call
setup.
changeOfClassmark
0xB5
OCTET (16 )

connection each timestamped
setupTime
0x9F 81
49
OCTET(9)

Issue 1.00 (2008-02-25)
Page 48 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
seizureTime
0x96
OCTET(9)

party side is completed. It
forwarding record.
alertingTime
0x9F 81
4A
OCTET(9)

answerTime
0x97
OCTET(9)

releaseTime
0x98
OCTET(9)

the calling or the called
party releases the traffic
channel.
callDuration
0x99
INTEGER(1..2)

the connection for
holding time of call
attempts.
radioChanRequested
0x9B
ENUMERATED

channel (full-rate or halfrate) requested by the MS.
(1)
radioChanUsed
0x9C
ENUMERATED
(1)

half-rate).
changeOfRadioChan
0xBD
OCTET(14..17)

types of radio traffic
channels each timestamped.
causeForTerm
0x9E
INTEGER(1)

of the connection.
diagnostics
0xBF
1F
INTEGER(4)

the release of the
connection.
callReference
0x9F 20
OCTET(1..8)
A local identifier
MS. It is also used to
identify all partial records
and transactions belonging
to the same connection.
Issue 1.00 (2008-02-25)
Page 49 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
sequenceNumber
0x9F 21
INTEGER(1)

number, only present in
additionalChgInfo
0xBF
22
SEQUENCE(3)

recordExtensions
0xBF
23
SET OF (11*n)
A set of network or
gsm-SCFAddress
0x9F 24
ADRESS(2..9)

applied.
serviceKey
0x9F 25
INTEGER(1..4)

applied.
0x9F 26
OCTET(1..8)
call taking place in
different network nodes.
mSCAddress
0x9F 27
ADRESS(2..9)

0x9F 28
BOOLEAN(1)

record.
defaultCallHandling
0x9F 29
ENUMERATED
Indicates whether a
field shall be present only if
default call handling has
been applied.
(1)
fnur
Issue 1.00 (2008-02-25)
0x9F
2D
ENUMERATED
(1)
The user data rate applied

for the connection in the
fixed network. Shall only
be present for 2G HSCSD
connections and for UMTS
data connections.
Page 50 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
aiurRequested
0x9F
2E
ENUMERATED
The total Air Interface User

Rate Requested by the MS
at call setup. Shall only be
present for non-transparent
HSCSD connections.
(1)
0x9F 31
OCTET(1)
The speech version

supported by the MS with
highest priority indicated
by MS.
speechVersionUsed
0x9F 32
OCTET(1)
The speech version used

for that call.
0x9F 33
INTEGER(1)

points (TDP and EDP)
were encountered. Shall be
applied.
levelOfCAMELService
0x9F 34
BIT STRING(2)

applied.
freeFormatData
0x9F 35
OCTET(1..160)

FCI messages. The data can
be sent either in one FCI
0xBF
36
SEQUENCE OF
A set of CAMEL
these IEs contains
CAMEL is applied.
0x9F 37
BOOLEAN(1)
Issue 1.00 (2008-02-25)
((104..124) * n)
Indicator if free format data

CDR.
Page 51 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
0x9F 38
ENUMERATED
Indicates whether or not a

default call handling for the
dialed service. This field
shall be present only if
been applied. Reserved for
future use.
(1)
gsm-SCFAddress-2
0x9F 39
ADRESS (2..9)

the subscriber for the
service. Reserved for future
use.
serviceKey-2
0x9F
3A
INTEGER (1..4)

to be applied for the second
freeFormatData-2
0x9F
3B
OCTET(1..160)

FCI message(s) for the
dialed service. The data can
be sent either in one FCI
indicator.
0x9F
3C
BOOLEAN (1)

for the second service from
this CDR is to be appended
to free format data in
previous partial CDR. Shall
service. Reserved for future
use.
systemType
0x9F
3D
ENUMERATED

the UTRAN or GERAN
setup.
Issue 1.00 (2008-02-25)
(1)
Page 52 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
rateIndication
0x9F
3E
OCTET(1)

between the MS/UE and
the network, see TS 24.008.
partialRecordType
0x9F 45
ENUMERATED

generation of a partial
record. This field is
mandatory in case of partial
records.
(1)
guaranteedBitrate
0x9F 46
ENUMERATED
(1)
maximumBitrate
0x9F 47
ENUMERATED
(1)
modemType
0x9F 81
0B
ENUMERATED
(1)
The bit-rate the UMTS

bearer service shall
guarantee to the user or
application. This field may
be used to facilitate
admission control based on
available resources, and for
resource allocation within
UMTS. Shall only be
connections.
reservations in the
interface. Its purpose is: 1)
to limit the delivered bitrate to applications or
external networks with
such limitations, 2) to allow
maximum wanted user bitrate to be defined for
applications able to operate
with different rates (e.g.
applications with adapting
codecs). Shall only be
connections.
The type of Modem used. It
forwarding record.
classmark3
0x9F 81
0C
OCTET(2)
The mobile station

classmark 3.
chargedParty
0x9F 81
0D
ENUMERATED

party is charged for the call.
Issue 1.00 (2008-02-25)
(1)
Page 53 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
0x9F 81
0E
ADRESS (2..17)

called party.
chargeAreaCode
0x9F 81
11
OCTET(1..3)

0x9F 81
12
OCTET(1..3)

mscOutgoingCircuit
0x9F 81
26
INTEGER()1..2
The CIC, only present in

case of outgoing bear type
being TDM.
orgRNCorBSCId
0x9F 81
27
OCTET(3)

BSC.
orgMSCId
0x9F 81
28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F 81
2A
OCTET(1)

call. See 29.002.
0x9F 81
2B
OCTET(1)

eaSubscriberInfo
0x9F 81
2E
OCTET(3)

Access. This field is not
available in the forwarding
record.
selectedCIC
0x9F 81
2F
OCTET(3)

Carrier identification. This
field is not available in the
forwarding record.
optimalRoutingFlag
0x9F 81
31
NULL

applied. Reserved for
future use.
optimalRoutingLateForwardFla
g
0x9F 81
32
NULL

late forward. Reserved for
future use.
optimalRoutingEarlyForwardFl
ag
0x9F 81
33
NULL

early forward. Reserved for
future use.
Issue 1.00 (2008-02-25)
Page 54 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
portedflag
0x9F 81
34
ENUMERATED
Indicates whether the user

is ported. Reserved for
future use.
(1)
calledIMSI
0x9F 81
35
TBCD(3..8)
The IMSI of the forwardedto party.
globalAreaID
0x9F 81
3C
OCTET(7)
The GCI of the GSM

WCDMA network.
0xBF
81 3D
SEQUENCE OF
A list of changes in the GCI

/ SAI each time-stamped.
(22 * n)
subscriberCategory
0x9F 81
3E
OCTET(1)
The category of
subscribers.
firstmccmnc
0x9F 81
40
OCTET(3)

initiated.
intermediatemccmnc
0x9F 81
41
OCTET(3)
lastmccmnc
0x9F 81
42
OCTET(3)

handover.
0x9F 81
43
ENUMERATED

CUG call.
(1)
cUGInterlockCode
0x9F 81
44
OCTET(4)
Network code + CUG

interlock
0x9F 81
45
ENUMERATED

group.
(1)
cUGIndex
0x9F 81
46
OCTET(2)

subscribers.
interactionWithIP
0x9F 81
47
NULL (0)

between SSP and IP,
GsmSCF play
start charging.
hotBillingTag
0x9F 81
48
INTEGER(1)

only if the hot charging
function is applied.
Issue 1.00 (2008-02-25)
Page 55 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
voiceIndicator
0x9F 81
4B
ENUMERATED
Indicates that the

released.
0x9F 81
4C
ENUMERATED
0x9F 81
4D
ENUMERATED
(1)

as the intra-office,
incoming, outgoing,
tandem, or unknown.
bCategory
callType
C
C
C
C
(1)
(1)

groupCallType
0x9F 81
50
ENUMERATED(1)
groupCallReference
0x9F 81
51
OCTET(4)

group call.
uus1Type
0x9F 81
52
ENUMERATED(1)
The type of UUS1.
eCategory
0x9F 81
57
INTEGER(1..2)

category.
disconnectparty
0x9F 81
5A
ENUMERATED(1)

call first.
csReference
0x9F 81
5C
OCTET(1..8)

number.
csaReference
0x9F 81
5D
INTEGER (1..4)
The call segment

number.
camelphase
0x9F 81
5E
ENUMERATED(1)
The CAMEL version

number.
networkOperatorId
0x9F 81
5F
OCTET(1)
typeOfSubscribers
0x9F 81
60
ENUMERATED(1)
The type of roaming

subscriber.
audioDataType
0x9F 81
61
ENUMERATED(1)

usertype
0x9F 81
63
ENUMERATED(1)
The user type.
recordNumber
0x9F 81
68
INTEGER

CDR.
partyRelCause
0xBF
81 6C
PartyRelCause

release.
Issue 1.00 (2008-02-25)
Page 56 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
cARP
0x9F 81
76
INTEGER(1)
The CARP value registered

by the subscriber.
redirectingcounter
0x9F 82
11
INTEGER(1)
Times of call forwarding.
2.4 Mobile Terminated Call Attempt

If the generation of these records is enabled, an MTC record shall be created for each
incoming call attempt made for a mobile station. The MTC records shall be produced in the
terminating MSC. Figure 1.4 lists the formats of MTC records.
Figure 1.4 MTC record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
Mobile Terminated.
CallEventRecordType
= 0x01
(1)
servedIMSI
0x81
TBCD(3..8)
The IMSI of the

called party.
servedIMEI
0x82
TBCD(8)
The IMEI of the

called mobile
equipment if
available.
servedMSISDN
0x83
ADRESS(2..9)
The primary
MSISDN of the called
party.
callingNumber
0x84
ADRESS(2..17)
The number of the

calling party if
available.
connectedNumber
0x85
ADRESS(2..17)
Only relevant in case

of call forwarding
where the forwardedto number is
recorded.
recordingEntity
0x86
ADRESS(2..9)
The E.164 number of

the visited MSC
producing the record
(MSC/VLR number:
TON+NPI+MSC
identifier number).
Issue 1.00 (2008-02-25)
Page 57 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
mscIncomingROUTE
0xA7
IA5(1..32)
The MSC route on

which the call is
originated at the
forwarding MSC.
mscOutgoingROUTE
0xA8
IA5(1..32)
The route on which

the call left the MSC,
usually to the BSC or
RNC.
location
0xA9
OCTET(8)
The identity of the

cell or the SAC at the
time of CDR creation.
changeOfLocation
0xAA
SEQUENCE OF
Location Area Code /
Cell Identifier each
time-stamped.
( 23 * n )
basicService
0xAB
OCTET(3)
The bearer or
teleservice employed.
0x8C
ENUMERATED

basic service was
used in transparent or
non-transparent
mode. This parameter
is provided only for
those basic services
which may be
employed in both
transparent and nontransparent modes.
(1)
changeOfService
0xAD
SEQUENCE OF
( (18..27) * n)
supplServicesUsed
0xAE
SEQUENCE OF
(16 * n)
aocParameters
Issue 1.00 (2008-02-25)
0xAF
OCTET(4..28)
A list of changes of
basic service during a
Supplementary
services invoked as a
result of this
connection. This field
shall be present when
one or more
supplementary
services have been
invoked.
The charge advice
parameters sent to the
MS on call setup.
Page 58 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
changeOfAOCParms
0xB0
SEQUENCE OF
The new AOC

parameters sent to the
MS e.g. as a result of
a tariff switchover,
including the time at
which the new set
was applied.
( 43 * n)
msClassmark
0x91
OCTET(2..3)
The mobile station

classmark employed
on call setup.
changeOfClassmark
0xB2
OCTET (16 )
A list of changes to
the classmark during
the connection each
time-stamped
setupTime
0x9F 81 4B
OCTET(9)
The time stamp when

the Setup message or
IAM message is
received from the
calling party side.
seizureTime
0x93
OCTET(9)
The time stamp when

the assignment at the
called party side is
completed.
alertingTime
0x9F 81 4C
OCTET(9)
The time stamp when

the Alerting message
or ACM message is
received from the
called party side.
answerTime
0x94
OCTET(9)
The time stamp when

the call is answered
during a successful
connection.
releaseTime
0x95
OCTET(9)
The time stamp when

either the calling or
the called party
releases the traffic
channel.
callDuration
0x96
INTEGER(1..2)
The chargeable
duration of the
connection for
holding time of call
attempts.
Issue 1.00 (2008-02-25)
Page 59 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
radioChanRequested
0x98
ENUMERATED
The type of radio

traffic channel (fullrate or half-rate)
requested by the MS.
(1)
radioChanUsed
0x99
ENUMERATED
(1)
The type of radio

channel actually used
(full-rate or half-rate).
changeOfRadioChan
0xBA
OCTET (14..17 )
A list of changes to
the types of radio
traffic channels each
time-stamped.
causeForTerm
0x9B
INTEGER(1)
The reason for the

release of the
connection.
diagnostics
0xBC
INTEGER(4)
A more detailed
reason for the release
of the connection.
callReference
0x9D
OCTET(1..8)
A local identifier
distinguishing
between transactions
on the same MS. It is
also used to identify
all partial records and
transactions
belonging to the same
connection.
sequenceNumber
0x9E
INTEGER(1)
The partial record

sequence number,
only present in case
of partial records.
additionalChgInfo
0xBF 1F
SEQUENCE(3)
Charge/no charge
indicator and
additional charging
parameters, when
available.
recordExtensions
0xBF 20
SET OF (11 * n)
A set of network or
extensions to the
record. Reserved for
future use.
0x9F 21
OCTET(1..8)
An identifier to
correlate transactions
on the same call
taking place in
different network
nodes.
Issue 1.00 (2008-02-25)
Page 60 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
mSCAddress
0x9F 22
ADRESS(2..9)
The E.164 number

assigned to the MSC
that generated the
network call
reference.
fnur
0x9F 26
ENUMERATED
The user data rate

applied for the
connection in the
fixed network. Shall
only be present for
2G HSCSD
connections and for
UMTS data
connections.
(1)
aiurRequested
0x9F 27
ENUMERATED
(1)
The total Air Interface

User Rate Requested
by the MS at call
setup. Shall only be
present for nontransparent HSCSD
connections.
0x9F 2A
OCTET(1)
The speech version

supported by the MS
with highest priority
indicated by MS.
speechVersionUsed
0x9F 2B
OCTET(1)
The speech version

used for that call.
gsm-SCFAddress
0x9F 2C
ADRESS(2..9)
The CAMEL server

serving the subscriber.
Shall be present only
if CAMEL is applied.
serviceKey
0x9F 2D
INTEGER(1..4)
The CAMEL service

logic to be applied.
systemType
0x9F 2E
ENUMERATED
This field indicates

the use of GERAN,
UTRAN (or a value
of unknown). This
field is present when
either the UTRAN or
GERAN air-interface
is used on call setup.
(1)
Issue 1.00 (2008-02-25)
Page 61 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
rateIndication
0x9F 2F
OCTET(1)
Present if "rate
adaptation"
parameters for the
basic service were
signaled between the
MS/UE and the
network, see TS
24.008.
partialRecordType
0x9F 36
ENUMERATED
The event that caused

the generation of a
partial record. This
field is mandatory in
case of partial
records.
(1)
guaranteedBitrate
0x9F 37
ENUMERATED
(1)
maximumBitrate
0x9F 38
ENUMERATED
(1)
Issue 1.00 (2008-02-25)
The bit-rate the

UMTS bearer service
shall guarantee to the
user or application.
This field may be
used to facilitate
admission control
based on available
resources, and for
resource allocation
within UMTS. Shall
only be present for
UMTS data
connections.
The maximum bitrate that can be used
to make code
reservations in the
interface. Its purpose
is: 1) to limit the
delivered bit-rate to
applications or
external networks
with such limitations,
2) to allow maximum
wanted user bit-rate to
be defined for
applications able to
operate with different
rates (e.g.
applications with
adapting codecs).
Shall only be present
for UMTS data
connections.
Page 62 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
initialCallAttemptFlag
0x9F 81 09
NULL(0)

call is set up through
the Initial Call
Attempt (ICA)
operation sent by the
SCP.
ussdCallBackFlag
0x9F 81 0A
NULL(0)
Indicates that the call

is set up when a
CAMEL subscriber
roaming outside the
HPLMN uses the
UCB service.
modemType
0x9F 81 0B
ENUMERATED
The type of Modem

used.
(1)
classmark3
0x9F 81 0C
OCTET(2)
The mobile station

classmark 3.
chargedParty
0x9F 81 0D
ENUMERATED

calling party or the
called party is
(1)
0x9F 81 0E
ADRESS(2..17)
The address of
original called party.
chargeAreaCode
0x9F 81 11
OCTET(1..3)
The subscriber logical

area for distance
charge.
0x9F 81 12
OCTET(1..3)
The called party

logical area for
distance charge.
defaultCallHandling
0x9F 81 16
ENUMERATED
Indicates whether a
CAMEL call
encounters default
call handling. This
field shall be present
only if default call
handling has been
applied.
(1)
Issue 1.00 (2008-02-25)
Page 63 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
freeFormatData
0x9F 81 17
OCTET(1..160)
This field contains

data sent by the
gsmSCF in the FCI
messages. The data
can be sent either in
one FCI message or
several FCI messages
with append indicator.
if CAMEL is applied
for the second
service.
0x9F 81 18
BOOLEAN(1)
Indicator if free
format data from this
CDR is to be
appended to free
format data in
previous partial CDR.
0x9F 81 19
INTEGER(1)
Number that counts

how often armed
detection points (TDP
and EDP) were
encountered. Shall be
present only if
CAMEL is applied.
levelOfCAMELService
0x9F 81 1A
BIT STRING(2)

complexity of the
CAMEL feature used.
roamingNumber
0x9F 81 20
ADRESS(2..17)
The Mobile Station

Roaming Number
connection.
mscIncomingCircuit
0x9F 81 26
INTEGER(1..2)
The CIC, only present

in case of incoming
bear type being TDM.
orgRNCorBSCId
0x9F 81 27
OCTET(3)
The SPC of the RNC

or the BSC.
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F 81 2A
OCTET(1)
The EMLPP priority

of the call. See
29.002.
Issue 1.00 (2008-02-25)
Page 64 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
calledDefaultEmlppPriority
0x9F 81 2B
OCTET(1)
The priority of the

EMLPP service
registered by the
calling party. See
29.002.
eaSubscriberInfo
0x9F 81 2E
OCTET(3)
The calling
subscriber's
Access. This field is
not available in the
MTC record.
selectedCIC
0x9F 81 2F
OCTET(3)

Carrier identification.
This field is not
available in the MTC
record.
optimalRoutingFlag
0x9F 81 31
NULL
Shall be present when

the optimal routing
Reserved for future
use.
portedflag
0x9F 81 34
ENUMERATED

user is ported.
Reserved for future
use.
(1)
globalAreaID
0x9F 81 3C
OCTET(7)
The GCI of the GSM

network or the SAI of
the WCDMA
network.
0xBF 81 3D
SEQUENCE
the GCI / SAI each
time-stamped.
OF (22 * n)
subscriberCategory
0x9F 81 3E
OCTET(1)
The category of
subscribers.
firstmccmnc
0x9F 81 40
OCTET(3)
The MCC and MNC

of the network when
the call is initiated.
intermediatemccmnc
0x9F 81 41
OCTET(3)
Reserved for future

use.
lastmccmnc
0x9F 81 42
OCTET(3)
The MCC and MNC

of the network when
the call is served.
Only present after
handover.
Issue 1.00 (2008-02-25)
Page 65 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
0x9F 81 43
ENUMERATED
The access indicator

of the CUG call.
(1)
cUGInterlockCode
0x9F 81 44
OCTET(4)
Network code + CUG

interlock
cUGIncomingAccessUsed
0x9F 81 45
ENUMERATED

calling party and
called party are in the
same CUG group.
(1)
cUGIndex
0x9F 81 46
OCTET(2)

subscribers.
hotBillingTag
0x9F 81 48
INTEGER(1)
Indicates that the

charged party is a
subscriber who
subscribes to the hot
billing service. Shall
be present only if the
hot charging function
is applied.
redirectingnumber
0x9F 81 49
ADRESS(2..17)
The MSISDN of the

forwarding party.
redirectingcounter
0x9F 81 4A
INTEGER(1)
The number of times

of call forwarding.
calledNumber
0x9F 81 4D
ADRESS(2..17)
The address of the

called party e.g. the
number dialed by the
calling party.
voiceIndicator
0x9F 81 4E
ENUMERATED
Indicates that the

announcement is
played for the local
office or other offices
when the call is
released.
(1)
bCategory
0x9F 81 4F
ENUMERATED
(1)
callType
0x9F 81 50
ENUMERATED
(1)

called party is busy or
idle.
Indicates the call
type, such as the
intra-office,
incoming, outgoing,
tandem, or unknown.
groupCallType
0x9F 81 53
ENUMERATED(1
)
The type of a group

call.
groupCallReference
0x9F 81 54
OCTET(4)
The reference number

of a group call.
Issue 1.00 (2008-02-25)
Page 66 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
uus1Type
0x9F 81 55
ENUMERATED(1
)
The type of UUS1.
eCategory
0x9F 81 57
INTEGER(1..2)
The enhanced
subscriber category.
tariffCode
0x9F 81 59
INTEGER(1)
The tariff code.
disconnectparty
0x9F 81 5A
ENUMERATED(1
)
The party who

releases the call first.
csReference
0x9F 81 5C
OCTET(1..8)
The call segment

reference number.
csaReference
0x9F 81 5D
INTEGER (1..4)
The call segment

number.
networkOperatorId
0x9F 81 5F
OCTET(1)
The ID of virtual
operators.
typeOfSubscribers
0x9F 81 60
ENUMERATED(1
)
The type of roaming

subscriber.
audioDataType
0x9F 81 61
ENUMERATED(1
)

data service or speech
service is employed
by a subscriber.
usertype
0x9F 81 63
ENUMERATED(1
)
The user type.
recordNumber
0x9F 81 68
INTEGER
The serial number of

a CDR.
partyRelCause
0xBF 81 6C
PartyRelCause
Indicates the cause of

call release.
translatedNumber
0x9F 81 75
ADRESS (2..17)
The called number

after digit translation
within the MSC (if
applicable).
zoneCode
0x9F 81 70
OCTET (2)
The zone code of a

cell.
cARP
0x9F 81 76
INTEGER(1)
The CARP value

registered by the
subscriber.
2.5 Roaming Call Attempt

If the generation of these records is enabled, a roaming record shall be created for each call
Issue 1.00 (2008-02-25)
Page 67 of 173
CONFIDENTIAL
redirected to a mobile subscriber roaming outside the HPLMN. These roaming records shall
be produced in the GMSC of the roaming subscriber's HPLMN. Figure 1.5 lists the formats of
roaming call attempt records.
Figure 1.5 Roaming record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
Roaming record.
0x02
(1)
servedIMSI
0x81
TBCD(3..8)

(roaming) party.
servedMSISDN
0x82
ADRESS(2..9)
The MSISDN of the called

(roaming) party.
Calling Number
0x83
ADRESS(2..17)

party, if available.
roamingNumber
0x84
ADRESS(2..17)
The Mobile Station

Roaming Number
connection.
recordingEntity
0x85
ADRESS(2..9)

number).
mscIncomingROUTE
0xA6
IA5(1..32)
The incoming GMSC route

on which the call is
originated.
mscOutgoingROUTE
0xA7
IA5(1..32)

left the GMSC.
basicService
0xA8
OCTET(3)

employed.
0x89
ENUMERATE
D
(1)
changeOfService
0xAA
SEQUENCE
OF
( (18..27) * n)
Issue 1.00 (2008-02-25)

service was used in
each time-stamped.
Page 68 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
supplServicesUsed
0xAB
SEQUENCE
OF
more supplementary
services have been invoked.
(16 * n)
seizureTime
0x8C
OCTET(9)
The time of incoming

traffic channel seizure (for
unsuccessful call attempts).
At present, it is not
available.
answerTime
0x8D
OCTET(9)

releaseTime
0x8E
OCTET(9)

channel.
callDuration
0x8F
INTEGER(1..2)

the connection for
successful calls, the holding
time for call attempts.
causeForTerm
0x91
INTEGER(1)

of the connection.
diagnostics
0xB2
INTEGER(4)

the release of the
connection.
callReference
0x93
OCTET(1..8)
A local identifier
sequenceNumber
0x94
INTEGER(1)

recordExtensions
0xB5
SET OF (11 *
n)
A set of network or
0x96
OCTET(1..8)
call taking place in different
network nodes.
Issue 1.00 (2008-02-25)
Page 69 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
mSCAddress
0x97
ADRESS(2..9)

partialRecordType
0x9E
ENUMERATE
D
(1)
additionalChgInfo
chargedParty
0xBF 81
05
0x9F 81
0D
The event (time limit etc.)

that caused the generation
of a partial record. This
field is mandatory in case
of partial records.
SEQUENCE(3)

ENUMERATE
D

calling subscriber or the
called subscriber is charged
for the call.
(1)
0x9F 81
0E
ADRESS(2..17)

called party.
chargeAreaCode
0x9F 81
11
OCTET(1..3)

0x9F 81
12
OCTET(1..3)

mscOutgoingCircuit
0x9F 81
26
INTEGER(1..2)
0x9F 81
27
INTEGER(1..2)
mscIncomingCircuit
This field indicates the CIC,

only present in case of
outgoing bear type being
TDM.
incoming bear type being
TDM.
orgMSCId
0x9F 81
28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F 81
2A
OCTET(1)

call. See 29.002.
eaSubscriberInfo
0x9F 81
2E
OCTET(3)

Access. This field is not
used in ROAM.
selectedCIC
0x9F 81
2F
OCTET(3)

Carrier identification. This
field is not used in ROAM.
Issue 1.00 (2008-02-25)
Page 70 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
optimalRoutingFlag
0x9F 81
31
NULL

applied. Reserved for future
use.
subscriberCategory
0x9F 81
3E
OCTET(1)
The category of
subscribers.
0x9F 81
43
ENUMERATE
D

CUG call.
(1)
cUGInterlockCode
0x9F 81
44
OCTET(4)
Network code + CUG

interlock
hotBillingTag
0x9F 81
48
INTEGER(1)

service. It is available only
when the hot charging
eCategory
0x9F 81
57
INTEGER(1..2)

category.
gsm-SCFAddress
0x9F 81
58
ADRESS(2..9)

applied.
serviceKey
0x9F 81
59
INTEGER(1..4)

applied.
levelOfCAMELService
0x9F 81
5A
BIT STRING(2)

applied.
networkOperatorId
0x9F 81
5F
OCTET (1)
typeOfSubscribers
0x9F 81
60
ENUMERATE
D(1)
The type of roaming

subscriber.
recordNumber
0x9F 81
68
INTEGER

CDR.
partyRelCause
0xBF 81
6C
PartyRelCause

release.
Issue 1.00 (2008-02-25)
Page 71 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
translatedNumber
0x9F 81
75
ADRESS
(2..17)

2.6 Incoming Gateway Call Attempt

If the generation of these records is enabled, an incoming gateway record shall be created for
each incoming call attempt received by a gateway MSC from another network. These records,
produced in the gateway MSC, may be used to settle accounts with other networks. The
generation of gateway records shall not be influenced by the production of MTC records i.e.
even if the GMSC and terminating MSC are co-located a gateway record shall still be
produced. Figure 1.6 lists the formats of incoming gateway call attempt records.
Figure 1.6 Incoming gateway record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
Incoming gateway record.

(1)
callingNumber
0x81
ADRESS(2..17)

party if available at this node.
calledNumber
0x82
ADRESS(2..17)
The address of the called party

as seen by the GMSC. This is
the number employed by the
GMSC for routing.
recordingEntity
0x83
ADRESS(2..9)

number).
mscIncomingROUTE
0xA4
IA5(1..32)
The incoming GMSC route on

which the call is originated.
mscOutgoingROUTE
0xA5
IA5(1..32)

left the GMSC.
setupTime
0x9F 81 49
OCTET(9)

calling party side.
seizureTime
0x86
OCTET(9)

assignment at the called party
side is completed.
Issue 1.00 (2008-02-25)
Page 72 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
alertingTime
0x9F 81
4A
OCTET(9)

called party side.
answerTime
0x87
OCTET(9)

releaseTime
0x88
OCTET(9)

callDuration
0x89
INTEGER(1..2)
The accountable duration

(answer -> release of
incoming trunk) of the
connection if successful.
causeForTerm
0x8B
INTEGER(1)

the connection.
diagnostics
0xAC
INTEGER(4)
A more detailed reason for the

release of the connection.
callReference
0x8D
OCTET(1..8)
A local identifier
partial records and
same connection.
sequenceNumber
0x8E
INTEGER(1)

of partial records.
recordExtensions
0xAF
SET OF (11 * n)
A set of network or
partialRecordType
0x96
ENUMERATED
The event (time limit etc.) that

caused the generation of a
partial record. This field is
records.
(1)
iSDN-BC
Issue 1.00 (2008-02-25)
0x97
OCTET(1..12)
Present if this parameter is

signaled back from the VMSC
to the GMSC in the access
transport parameter of the
Answer message (ANM), see
TS 29.007.
Page 73 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
lLC
0x98
OCTET(1..18)

TS 29.007.
hLC
0x99
OCTET(1..12)

TS 29.007.
basicService
0xBF 81 02
OCTET(3)

employed.
additionalChgInfo
0xBF 81 05
SEQUENCE(3)

chargedParty
0x9F 81
0D
ENUMERATED

(1)
0x9F 81 0E
ADRESS(2..17)

party.
rateIndication
0x9F 81 1F
OCTET(1)

service were signaled between
the MS/UE and the network,
see TS 24.008.
chargeAreaCode
0x9F 81 11
OCTET(1..3)
The subscriber logical area for

distance charge.
roamingNumber
0x9F 81 20
ADRESS(2..17)

this connection.
mscIncomingCircuit
0x9F 81 27
INTEGER(1..2)

TDM.
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F 81
2A
OCTET(1)

call. See 29.002.
eaSubscriberInfo
0x9F 81 2E
OCTET(3)

selectedCIC
0x9F 81 2F
OCTET(3)

identification.
Issue 1.00 (2008-02-25)
Page 74 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
subscriberCategory
0x9F 81 3E
OCTET(1)
0x9F 81 43
ENUMERATED

CUG call.
(1)
cUGInterlockCode
0x9F 81 44
COTET(4)
Network code + CUG

interlock
0x9F 81 45
ENUMERATED

the same CUG group.
(1)
mscIncomingRouteAttribute
0x9F 81 46
ENUMERATED
(1)
mscOutgoingRouteAttribute
0x9F 81 47
ENUMERATED
(1)
The attribute of incoming

routes.
The attribute of outgoing
routes.
0x9F 81 48
OCTET(1..8)
network nodes.
voiceIndicator
0x9F 81 4B
ENUMERATED
Indicates that the

the local office or other offices
when the call is released.
(1)
bCategory
0x9F 81 4C
ENUMERATED
(1)
callType

0x9F 81
4D
ENUMERATED
(1)
Indicates the call type, such as

the intra-office, incoming,
unknown.
disconnectparty
0x9F 81
5A
ENUMERATED
(1)

call first.
networkOperatorId
0x9F 81 5F
OCTET (1)
audioDataType
0x9F 81 61
ENUMERATED
(1)

recordNumber
0x9F 81 68
INTEGER
partyRelCause
0xBF 81
6C
PartyRelCause

release.
servedIMSI
0x9F 81 6F
TBCD(3..8)
The IMSI of the called party.
translatedNumber
0x9F 81 75
ADRESS (2..17)

translation within the MSC (if
applicable).
Issue 1.00 (2008-02-25)
Page 75 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
location
0xBF 81 77
OCTET(8)

location area code.
changeOfLocation
0xBF 81 78
SEQUENCE OF
( 23 * n )

each time-stamped.
firstmccmnc
0x9F 81 79
OCTET(3)

initiated.
lastmccmnc
0x9F 81
7A
OCTET(3)

handover.
redirectingnumber
0x9F 82 10
ADRESS(2..17)
The MSISDN of the

forwarding party.
redirectingcounter
0x9F 82 11
INTEGER(1)
2.7 Outgoing Gateway Call Attempt

If the generation of these records is enabled, an outgoing gateway record shall be created for
each outgoing call attempt from a gateway MSC to another network. These records, produced
in the gateway MSC, may be used to settle accounts with other networks. The generation of
gateway records shall not be influenced by the production of MOC records i.e. even if the
GMSC and originating MSC are co-located a gateway record shall still be produced. Figure
1.7 lists the formats of outgoing gateway call attempt records.
Figure 1.7 Outgoing gateway record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
Outgoing gateway record.

(1)
callingNumber
0x81
ADRESS(2..17
)

party if available at this node.
calledNumber
0x82
ADRESS(2..17
)

party as seen by the GMSC.
This is the number employed
by the GMSC for routing.
Issue 1.00 (2008-02-25)
Page 76 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
recordingEntity
0x83
ADRESS(2..9)

number).
mscIncomingROUTE
0xA4
IA5(1..32)
The incoming GMSC route on

which the call is originated.
mscOutgoingROUTE
0xA5
IA5(1..32)

left the GMSC.
setupTime
0x9F 81 49
OCTET(9)

calling party side.
seizureTime
0x86
OCTET(9)

assignment at the calling party
side is completed.
alertingTime
0x9F 81 4A
OCTET(9)

called party side.
answerTime
0x87
OCTET(9)

releaseTime
0x88
OCTET(9)

callDuration
0x89
INTEGER(1..2
)
The accountable duration

(answer -> release of
incoming trunk) of the
connection if successful.
causeForTerm
0x8B
INTEGER(1)

the connection.
diagnostics
0xAC
INTEGER(4)

callReference
0x8D
OCTET(1..8)
A local identifier
partial records and
same connection.
sequenceNumber
0x8E
INTEGER(1)

of partial records.
Issue 1.00 (2008-02-25)
Page 77 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
recordExtensions
0xAF
SET OF
(11*n )
A set of network or
partialRecordType
0x96
ENUMERATE
D

caused the generation of a
partial record. This field is
records.
(1)
basicService
0xBF 81 02
OCTET(3)

employed.
additionalChgInfo
0xBF 81 05
SEQUENCE(3
)

chargedParty
0x9F 81 0D
ENUMERATE
D
(1)

0x9F 81 0E
ADRESS(2..17
)

party.
chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
rateIndication
0x9F 81 1F
OCTET(1)

service were signaled between
the MS/UE and the network,
see TS 24.008.
roamingNumber
0x9F 81 20
ADRESS(2..17
)

this connection.
mscOutgoingCircuit
0x9F 81 26
INTEGER(1..2
)

TDM.
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F 81 2A
OCTET(1)

call. See 29.002.
eaSubscriberInfo
0x9F 81 2E
OCTET(3)

selectedCIC
0x9F 81 2F
OCTET(3)

identification.
subscriberCategory
0x9F 81 3E
OCTET(1)
Issue 1.00 (2008-02-25)
Page 78 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
0x9F 81 43
ENUMERATE
D

CUG call.
(1)
cUGInterlockCode
0x9F 81 44
OCTET(4)
Network code + CUG

interlock
0x9F 81 45
ENUMERATE
D
(1)

the same CUG group.
ENUMERATE
D

routes.
0x9F 81 46
(1)
0x9F 81 47
ENUMERATE
D

routes.
(1)
0x9F 81 48
OCTET(1..8)
network nodes.
voiceIndicator
0x9F 81 4B
ENUMERATE
D
(1)
Indicates that the

released.
ENUMERATE
D

bCategory
0x9F 81 4C
(1)
callType
0x9F 81 4D
ENUMERATE
D
(1)
Indicates the call type, such as

the intra-office, incoming,
unknown.
disconnectparty
0x9F 81 5A
ENUMERATE
D(1)

call first.
networkOperatorId
0x9F 81 5F
OCTET (1)
audioDataType
0x9F 81 61
ENUMERATE
D(1)

recordNumber
0x9F 81 68
INTEGER
partyRelCause
0xBF 81 6C
PartyRelCause

release.
Issue 1.00 (2008-02-25)
Page 79 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
translatedNumber
0x9F 81 75
ADRESS
(2..17)

translation within the MSC (if
applicable).
location
0xBF 81 77
OCTET(8)

location area code.
changeOfLocation
0xBF 81 78
SEQUENCE
OF ( 23 * n )

each time-stamped.
firstmccmnc
0x9F 81 79
OCTET(3)

initiated.
lastmccmnc
0x9F 81 7A
OCTET(3)

handover.
redirectingnumber
0x9F 82 10
ADRESS(2..17
)
The MSISDN of the

forwarding party.
redirectingcounter
0x9F 82 11
INTEGER(1)
2.8 Transit Call Attempt

If the generation of these records is enabled, a transit record may be generated for each
incoming call attempt received by a Transit MSC i.e. neither originating nor terminating. For
the avoidance of doubt, a transit record shall only be produced if no MOC or MTC record is
produced for this call attempt. The transit records, produced in the TMSC, may be used to
record traffic from particular origins or to particular destinations. Figure 1.8 lists the formats
of transit call attempt records.
Figure 1.8 Transit record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
Transit record.
0x05
(1)
recordingEntity
Issue 1.00 (2008-02-25)
0x81
ADRESS(2..9)

number).
Page 80 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
mscIncomingROUTE
0xA2
IA5(1..32)
The TMSC route on which

the call is originated.
mscOutgoingROUTE
0xA3
IA5(1..32)

left the TMSC.
callingNumber
0x84
ADRESS(2..17
)

party if available at this
node.
calledNumber
0x85
ADRESS(2..17
)

party as seen by the TMSC.
isdnBasicService
0x86
OCTET(1)
The ISDN basic service

employed.
setupTime
0x9F 81
49
OCTET(9)

seizureTime
0x87
OCTET(9)
The time stamp of incoming

trunk seizure for
unsuccessful call attempts.
It is not available at present.
alertingTime
0x9F 81
4A
OCTET(9)

answerTime
0x88
OCTET(9)

releaseTime
0x89
OCTET(9)

channel.
callDuration
0x8A
INTEGER(1..2
)

the connection if successful.
causeForTerm
0x8C
INTEGER(1)

the connection.
diagnostics
0xAD
INTEGER(4)

the release of the
connection.
Issue 1.00 (2008-02-25)
Page 81 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
callReference
0x8E
OCTET(1..8)
A local identifier
sequenceNumber
0x8F
INTEGER(1)

of partial records.
recordExtensions
0xB0
SET OF (11 *
n)
A set of network or
partialRecordType
0x97
ENUMERATE
D

field is mandatory in case of
partial records.
(1)
basicService
0xBF 81
02
OCTET(3)

employed.
additionalChgInfo
0xBF 81
05
SEQUENCE(3)

0x9F 81
0E
ADRESS(2..17
)

called party.
chargeAreaCode
0x9F 81 11
OCTET(1..3)

rateIndication
0x9F 81
1F
OCTET(1)

between the MS/UE and the
network, see TS 24.008.
roamingNumber
0x9F 81
20
ADRESS(2..17
)
The Mobile Station

Roaming Number employed
to route this connection.
mscOutgoingCircuit
0x9F 81
26
INTEGER(1..2
)

TDM.
mscIncomingCircuit
0x9F 81
27
INTEGER(1..2
)

TDM.
Issue 1.00 (2008-02-25)
Page 82 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
orgMSCId
0x9F 81
28
OCTET(3)
The SPC of the MSC.
callEmlppPriority
0x9F 81
2A
OCTET(1)

call. See 29.002.
eaSubscriberInfo
0x9F 81
2E
OCTET(3)

Access.
selectedCIC
0x9F 81
2F
OCTET(3)

identification.
subscriberCategory
0x9F 81
3E
OCTET(1)
0x9F 81
43
ENUMERATE
D

CUG call.
(1)
cUGInterlockCode
0x9F 81
44
OCTET(4)
Network code + CUG

interlock
0x9F 81
45
ENUMERATE
D

group.
(1)
0x9F 81
46
ENUMERATE
D

routes.
(1)
0x9F 81
47
ENUMERATE
D

routes.
(1)
0x9F 81
48
OCTET(1..8)
network nodes.
voiceIndicator
0x9F 81
4B
ENUMERATE
D
(1)
Indicates that the

released.
ENUMERATE
D

bCategory
0x9F 81
4C
(1)
callType
0x9F 81
4D
ENUMERATE
D
(1)
Issue 1.00 (2008-02-25)

as the intra-office,
incoming, outgoing,
tandem, or unknown.
Page 83 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
disconnectparty
0x9F 81
5A
ENUMERATE
D(1)

call first.
networkOperatorId
0x9F 81
5F
OCTET (1)
audioDataType
0x9F 81
61
ENUMERATE
D(1)

recordNumber
0x9F 81
68
INTEGER

CDR.
partyRelCause
0xBF 81
6C
PartyRelCause

release.
translatedNumber
0x9F 81
75
ADRESS
(2..17)

cmnFlag
0x9F 81
7B
ENUMERATE
D(1)
Indicates whether the CMN

call is invoked.
redirectingnumber
0x9F 82
10
ADRESS(2..17
)
The MSISDN of the

forwarding party.
redirectingcounter
0x9F 82 11
INTEGER(1)
2.9 Short Message Service, Mobile Originated

If the generation of these records is enabled, an SMS-MO record shall be produced, within the
originating MSC, for each short message sent by a mobile subscriber. Figure 1.9 lists the
formats of SMS-MO records.
Figure 1.9 SMS-MO record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
SMS-Mobile originated
record.
0x06
(1)
servedIMSI
0x81
TBCD(3..8)
The IMSI of the subscriber

sending the short message.
servedIMEI
0x82
TBCD(8)
The IMEI of the ME

sending the message, if
available.
Issue 1.00 (2008-02-25)
Page 84 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
servedMSISDN
0x83
ADRESS(2..9)
The primary MSISDN of

the subscriber sending the
message.
msClassmark
0x84
OCTET(2..3)
The mobile station

classmark.
serviceCentre
0x85
ADRESS(2..9)
The E.164 address of the

SMS service center.
recordingEntity
0x86
ADRESS(2..9)

number).
location
0xA7
OCTET(8)
The Location Area Code

and Cell Identifier from
which the message is
originated.
messageReference
0x88
OCTET (3..8)
A reference, provided by the

MS uniquely identifying
this message.
originationTime
0x89
OCTET(9)
The time at which the

message was received by
the MSC from the
subscriber.
smsResult
0xAA
INTEGER (4)
The result of the attempted

delivery if unsuccessful.
recordExtensions
0xAB
SET OF (11 *
n)
A set of network or
destinationNumber
0x8C
ADRESS(2..17
)
The destination short

message subscriber number.
cAMELSMSInformation
0xAD
SET (34..58)
A set of CAMEL
these IEs contains
information related to
CAMEL call leg related for
the SMS. Shall be present
only if CAMEL is applied.
systemType
0x8E
ENUMERATE
D

the UTRAN or GERAN airinterface is used on call
setup.
(1)
Issue 1.00 (2008-02-25)
Page 85 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
basicService
0xBF 81
02
OCTET(3)

employed.
additionalChgInfo
0xBF 81
05
SEQUENCE(3)

classmark3
0x9F 81
0C
OCTET(2)
The mobile station

classmark 3.
chargedParty
0x9F 81
0D
ENUMERATE
D

(1)
chargeAreaCode
0x9F 81
11
OCTET(1..3)

orgRNCorBSCId
0x9F 81
27
OCTET(3)

BSC.
orgMSCId
0x9F 81
28
OCTET(3)
The SPC of the MSC.
globalAreaID
0x9F 81
3C
OCTET(7)
The GCI of the GSM

WCDMA network.
subscriberCategory
0x9F 81
3E
OCTET(1)
firstmccmnc
0x9F 81
40
OCTET(3)
Indicates the MCC and

MNC of the network where
the SMS is initiated.
smsUserDataType
0x9F 81
43
OCTET(1)
Indicates the user data type,

such as the normal SM,
picture, or text.
smstext
0x9F 81
44
OCTET(1..160)
Indicates the content of a

short message.
maximumNumberOfSMSInThe
ConcatenatedSMS
0x9F 81
45
INTEGER(1)
Indicates the maximum of

the concatenated short
messages.
concatenatedSMSReferenceNum
ber
0x9F 81
46
INTEGER(1..2
)
Indicates the reference

number of the concatenated
short messages.
sequenceNumberOfTheCurrentS
MS
0x9F 81
47
INTEGER(1)
Indicates the sequence of

the current concatenated
short message, such as 1, 2,
maximum Number Of
SMS In The Concatenated
SMS.
Issue 1.00 (2008-02-25)
Page 86 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
hotBillingTag
0x9F 81
48
INTEGER(1)

callReference
0x9F 81
49
OCTET(1..8)
A local identifier
MS.
tariffCode
0x9F 81
4A
INTEGER(1)
The tariff code.
networkOperatorId
0x9F 81
5F
OCTET (1)
typeOfSubscribers
0x9F 81
60
ENUMERATE
D(1)
The type of roaming

subscriber.
recordNumber
0x9F 81
68
INTEGER

CDR.
zoneCode
0x9F81 70
OCTET (2)
2.10 Short Message Service, Mobile Terminated

If the generation of these records is enabled, an SMS-MT record shall be produced, within the
terminating MSC, for each short message received by a mobile subscriber. Figure 1.10 lists
the formats of SMS-MT records.
Figure 1.10 SMS-MT record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
SMS-Mobile Terminated
record.
0x07
(1)
serviceCentre
0x81
ADRESS(2..9)

SMS service center.
servedIMSI
0x82
TBCD(3..8)
The IMSI of the receiving

party.
servedIMEI
0x83
TBCD(8)
The IMEI of the receiving

servedMSISDN
0x84
ADRESS(2..9)
The MSISDN of the

receiving party.
Issue 1.00 (2008-02-25)
Page 87 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
msClassmark
0x85
OCTET(2..3)
The mobile station

classmark.
recordingEntity
0x86
ADRESS(2..9)

number).
location
0xA7
OCTET(8)
The Location Area Code

and Cell Identifier to which
the message was delivered.
deliveryTime
0x88
OCTET(9)
Delivery time stamp, time

at which message was sent
to the MS by the MSC.
smsResult
0xA9
INTEGER(4)
The result of the attempted

delivery if unsuccessful.
recordExtensions
0xAA
SET OF (11 *
n)
A set of network or
systemType
0x8B
ENUMERATE
D

the UTRAN or GERAN
setup.
(1)
cAMELSMSInformation
0xAC
SET (34..58)
A set of CAMEL
these IEs contains
information related to
CAMEL call leg related for
the SMS.
In CAMEL phase 2 or 3,
SMS MT CSI is not
available in MSC-Server,
so that the
CAMELSMSInformation is
also not available in SMSMT records.
basicService
0xBF 81
02
OCTET(3)

employed.
additionalChgInfo
0xBF 81
05
SEQUENCE(3
)

Issue 1.00 (2008-02-25)
Page 88 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
classmark3
0x9F 81
0C
OCTET(2)
The mobile station

classmark 3.
chargedParty
0x9F 81
0D
ENUMERATE
D

(1)
chargeAreaCode
0x9F 81
11
OCTET(1..3)

'orgRNCorBSCId
0x9F 81
27
OCTET(3)

BSC.
orgMSCId
0x9F 81
28
OCTET(3)
The SPC of the MSC.
globalAreaID
0x9F 81
3C
OCTET(7)
The GCI of the GSM

WCDMA network.
subscriberCategory
0x9F 81
3E
OCTET(1)
The category of
subscribers.
firstmccmnc
0x9F 81
40
OCTET(3)
Indicates the MCC and

MNC of the network where
SMS is terminated.
smsUserDataType
0x9F 81
43
OCTET(1)
Indicates the user data type,

such as the normal SM,
picture, or text.
smstext
0x9F 81
44
OCTET(1..160
)
Indicates the content of a

short message.
maximumNumberOfSMSInTheCo
ncatenatedSMS
0x9F 81
45
INTEGER(1)
Indicates the maximum of

the concatenated short
messages.
concatenatedSMSReferenceNumb
er
0x9F 81
46
INTEGER(1..2
)
Indicates the reference

number of the concatenated
short messages.
sequenceNumberOfTheCurrentS
MS
0x9F 81
47
INTEGER(1)
Indicates the sequence of

the current concatenated
short message, such as 1, 2,
maximum Number Of
SMS In The Concatenated
SMS.
hotBillingTag
0x9F 81
48
INTEGER(1)

Issue 1.00 (2008-02-25)
Page 89 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
origination
0x9F 81
49
ADRESS(2..17
)
The originating short

message subscriber number.
callReference
0x9F 81
4A
OCTET(1..8)
A local identifier
MS.
tariffCode
0x9F 81
4B
INTEGER(1)
The tariff code.
networkOperatorId
0x9F 81
5F
OCTET (1)
typeOfSubscribers
0x9F 81
60
ENUMERATE
D(1)
The type of roaming

subscriber.
recordNumber
0x9F 81
68
INTEGER

CDR.
zoneCode
0x9F 81
70
OCTET (2)
2.11 Mobile Terminated Location Request (MT-LR)

If the generation of these records is enabled, an LCS-MT record shall be produced, within the
visited MSC, for each mobile a terminated location request is performed for. Figure 1.11 lists
the formats of LCS-MT records.
Figure 1.11 LCS-MT record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERAT
ED
LCS-MT record.
(1)
recordingEntity
0x81
ADRESS(2..
9)
The E.164 number of the visited

MSC producing the record
(MSC/VLR number:
TON+NPI+MSC identifier number).
lcsClientType
0x82
ENUMERAT
ED
The type of the LCS client that

invoked the LR.
(1)
lcsClientIdentity
0xA3
SEQUENCE
(13..29)
servedIMSI
Issue 1.00 (2008-02-25)
0x84
TBCD(3..8)
Further identification of the LCS

client.
The IMSI of the subscriber the LR is
invoked for.
Page 90 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
servedMSISDN
0x85
ADRESS(2..
9)
The MSISDN of the subscriber the

LR is invoked for.
locationType
0xA6
SEQUENCE
The type of the location request.
(6..21)
lcsQos
0xA7
SEQUENCE
QoS of the LR, if available.
(11)
lcsPriority
0x88
OCTET(1)
Priority of the LR.
mlc-Number
0x89
ADRESS(2..
9)
The E.164 address of the requesting

GMLC.
eventTimeStamp
0x8A
OCTET(9)
The time at which the LR was

received by the MSC.
measureDuration
0x8B
INTEGER(1..
2)
The duration of preceding the

location request.
notificationToMSUser
0x8C
ENUMERAT
ED
The privacy notification to MS user

that was applicable when the LR was
invoked, with the result of the
notification recorded in the CDR.
(1)
privacyOverride
0x8D
NULL(0)
This parameter indicates whether the

MS privacy was overridden by the
LCS client, if available.
location
0xAE
OCTET(8)
The LAC and CI when the LR is

received.
locationEstimate
0x8F
OCTET(1..20
)
The location estimate for the

subscriber if contained in geographic
position and the LR was successful.
positioningData
0x90
OCTET(1..33
)
The positioning method used or

attempted, if available.
lcsCause
0x91
OCTET(1)
The result of the LR if any failure or

partial success happened as known at
the radio interface.
diagnostics
0xB2
INTEGER(4)
A more detailed information about

the Cause for Termination if any
failure happened.
systemType
0x93
ENUMERAT
ED

GERAN, UTRAN (or a value of
unknown). This field is present when
either the UTRAN or GERAN airinterface is used on call setup.
(1)
recordExtensions
Issue 1.00 (2008-02-25)
0xB4
SET OF (11 *
n)
A set of network or manufacturer

specific extensions to the record.
Page 91 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
causeForTerm
0x95
INTEGER(1)
The reason for the termination of the

location service.
lcsReferenceNumber
0x9F 65
OCTET
STRING
(SIZE (1..8))
servedIMEI
0x9F 66
TBCD(8)
The IMEI of the party who the LR is

executed for if available.
additionalChgInfo
0xBF 81 05
SEQUENCE(
3)
Charge/no charge indicator and

additional charging parameters, when
available.
chargedParty
0x9F 81 0D
ENUMERAT
ED
Indicates whether the calling party or

the called party is charged for the
call.
(1)
chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
orgRNCorBSCId
0x9F 81 27
OCTET(3)
The SPC of the RNC or the BSC.
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
globalAreaID
0x9F 81 3C
OCTET(7)
The GCI of the GSM network or the

SAI of the WCDMA network.
subscriberCategory
0x9F 81 3E
OCTET(1)
firstmccmnc
0x9F 81 40
OCTET(3)
Indicates the MCC and MNC of the

network where LCS is initiated.
hotBillingTag
0x9F 81 48
INTEGER(1)
Indicates that the charged party is a

subscriber who subscribes to the hot
billing service. Shall be present only
applied.
callReference
0x9F 81 49
OCTET(1..8)
A local identifier distinguishing

between transactions on the same
MS.
tariffCode
0x9F 81 59
INTEGER(1)
The tariff code.
networkOperatorId
0x9F 81 5F
OCTET (1)
typeOfSubscribers
0x9F 81 60
ENUMERAT
ED(1)
The type of roaming subscriber.
recordNumber
0x9F 81 68
INTEGER
zoneCode
0x9F 81 70
OCTET (2)
Issue 1.00 (2008-02-25)
Page 92 of 173
CONFIDENTIAL
2.12 Mobile Originated Location Request (MO-LR)

If the generation of these records is enabled, an LCS-MO record shall be produced, within the
visited MSC, for each mobile an originated location request is performed for. Figure 1.12 lists
the formats of LCS-MO records.
Figure 1.12 LCS-MO record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
LCS-MO record.
(1)
recordingEntity
0x81
ADRESS(2..9)

(MSC/VLR number:
number).
lcsClientType
0x82
ENUMERATED

invoked the LR.
(1)
lcsClientIdentity
0xA3
SEQUENCE
(13..29)
Further identification of the

LCS client.
servedIMSI
0x84
TBCD(3..8)
The IMSI of the subscriber the

LR is invoked for.
servedMSISDN
0x85
ADRESS(2..9)
The MSISDN of the subscriber

the LR is invoked for.
molr-Type
0x86
INTEGER(1)
The type of the LR.
lcsQos
0xA7
SEQUENCE(11)
lcsPriority
0x88
OCTET(1)
Priority of the LR.
mlc-Number
0x89
ADRESS(2..9)

involved GMLC, if available.
eventTimeStamp
0x8A
OCTET(9)

measureDuration
0x8B
INTEGER(1..2)

location request.
location
0xAC
SEQUENCE (8)

SAC occupied by the
originating party when the LCS
was applied.
locationEstimate
0x8D
OCTET(1..20)

subscriber if contained in
geographic position and the LR
was successful.
Issue 1.00 (2008-02-25)
Page 93 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
positioningData
0x8E
OCTET(1..33)

lcsCause
0x8F
OCTET(1)
The result of the LR if any

failure or partial success
happened as known at the radio
interface.
diagnostics
0xB0
INTEGER(4)
A more detailed information

about the Cause for Termination
if any failure happened.
systemType
0x91
ENUMERATED

unknown). This field is present
when either the UTRAN or
GERAN air-interface is used on
call setup.
(1)
recordExtensions
0xB2
SET OF (11 * n)
A set of network or
manufacturer specific extensions
to the record. Reserved for
future use.
causeForTerm
0x93
INTEGER(1)
The reason for the termination

of the location service.
lcsReferenceNumber
0x9F 65
OCTET STRING
(SIZE (1..8))
servedIMEI
0x9F 66
TBCD(8)
The IMEI of the party who the

LR is executed for if available.
additionalChgInfo
0xBF 81 05
SEQUENCE(3)

additional charging parameters,
when available.
chargedParty
0x9F 81 0D
ENUMERATED

(1)
chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
orgRNCorBSCId
0x9F 81 27
OCTET(3)

BSC.
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
globalAreaID
0x9F 81 3C
OCTET(7)
The GCI of the GSM network or

the SAI of the WCDMA
network.
subscriberCategory
0x9F 81 3E
OCTET(1)
Issue 1.00 (2008-02-25)
Page 94 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
firstmccmnc
0x9F 81 40
OCTET(3)
Indicates the MCC and MNC of

the network where LCS is
initiated.
hotBillingTag
0x9F 81 48
INTEGER(1)
Indicates that the charged party

is a subscriber who subscribes to
the hot billing service. Shall be
present only if the hot charging
callReference
0x9F 81 49
OCTET(1..8)

between transactions on the
same MS.
tariffCode
0x9F 81 59
INTEGER(1)
The tariff code.
networkOperatorId
0x9F 81 5F
OCTET (1)
typeOfSubscribers
0x9F 81 60
ENUMERATED(
1)
recordNumber
0x9F 81 68
INTEGER
zoneCode
0x9F 81 70
OCTET (2)
2.13 Network Induced Location Request (NI-LR)

If the generation of these records is enabled, an LCS-NI record shall be produced, within the
visited MSC, for each network induced location request performed for a MS e.g. in case of
emergency call. Figure 1.13 lists the formats of LCS-NI records.
Figure 1.13 LCS-NI record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
LCS-NI record.
(1)
recordingEntity
0x81
ADRESS(2..9)

(MSC/VLR number:
number).
lcsClientType
0x82
ENUMERATE
D

invoked the LR.
(1)
lcsClientIdentity
0xA3
SEQUENCE
(13..29)
Issue 1.00 (2008-02-25)
Further identification of the

LCS client.
Page 95 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
servedIMSI
0x84
TBCD(3..8)
The IMSI of the subscriber the

LR is invoked for.
servedMSISDN
0x85
ADRESS(2..9)

the LR is invoked for.
servedIMEI
0x86
TBCD(8)
The IMEI of the subscriber the

LR is invoked for.
emsDigits
0x87
ADRESS(2..9)
The emergency service routing

digits, if emergency call.
emsKey
0x88
ADRESS(2..9)
The emergency service routing

key, if emergency call.
lcsQos
0xA9
SEQUENCE(1
1)
lcsPriority
0x8A
OCTET(1)
Priority of the LR.
mlc-Number
0x8B
ADRESS(2..9)

involved GMLC, if available.
eventTimeStamp
0x8C
OCTET(9)

measureDuration
0x8D
INTEGER(1..2
)

location request.
location
0xAE
OCTET(8)

SAC occupied by the terminated
party when the LCS was
applied.
locationEstimate
0x8F
OCTET(1..20)

subscriber if contained in
geographic position and the LR
was successful.
positioningData
0x90
OCTET(1..33)

lcsCause
0x91
OCTET(1)
The result of the LR if any

failure or partial success
happened as known at the radio
interface.
diagnostics
0xB2
INTEGER(4)
A more detailed information

about the Cause for Termination
if any failure happened.
systemType
0x93
INTEGER(1)

unknown). This field is present
when either the UTRAN or
GERAN air-interface is used on
call setup.
Issue 1.00 (2008-02-25)
Page 96 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
recordExtensions
0xB4
SET OF (11 *
n)
A set of network or
causeForTerm
0x95
INTEGER(1)
The reason for the termination

of the location service.
lcsReferenceNumber
0x9F 65
OCTET
STRING (SIZE
(1..8))
additionalChgInfo
0xBF 81
05
SEQUENCE(3)

when available.
chargedParty
0x9F 81
0D
ENUMERATE
D

(1)
chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
orgRNCorBSCId
0x9F 81 27
OCTET(3)

BSC.
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
globalAreaID
0x9F 81
3C
OCTET(7)
The GCI of the GSM network or

the SAI of the WCDMA
network.
subscriberCategory
0x9F 81
3E
OCTET(1)
firstmccmnc
0x9F 81 40
OCTET(3)
Indicates the MCC and MNC of

the network where LCS is
initiated.
hotBillingTag
0x9F 81 48
INTEGER(1)
Indicates that the charged party

is a subscriber who subscribes
to the hot billing service. Shall
be present only if the hot
charging function is applied.
callReference
0x9F 81 49
OCTET(1..8)

between transactions on the
same MS.
networkOperatorId
0x9F 81
5F
OCTET (1)
typeOfSubscribers
0x9F 81 60
ENUMERATE
D(1)
recordNumber
0x9F 81 68
INTEGER
Issue 1.00 (2008-02-25)
Page 97 of 173
CONFIDENTIAL
2.14 Supplementary Service Actions

A supplementary service record may be produced in the NEF of the appropriate MSC or HLR
for each supplementary service action (activation, deactivation, invocation etc.) performed or
initiated by the subscriber.
There are two fundamental types of SS-actions:
Call related i.e. as a result of a connection e.g. Invocation of CLIP / CLIR / AOC etc.
Non-call related i.e. as a result of Subscriber Controlled Input (SCI) e.g. Registration of
call forwarding.
Each supplementary service action shall be performed on one or more basic service groups. If
the action applies to all teleservices and all bearer services (i.e. to all basic services) then the
basic services field shall be omitted.
SCI actions may be recorded in individual SS-action records. Call related actions may be
recorded in either the appropriate call record (MOC/MTC) or in separate SS-action records.
Additional non-standard supplementary service actions may be made available within some
networks in the form of Unstructured Supplementary Service Data (USSD). These actions
may also be recorded in SS-action records. However, as these actions are non-standard they
may not include an appropriate action type, supplementary service code or basic service code.
Figure 1.14 lists the formats of SS-action records.
Figure 1.14 SS-action record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
Supplementary service action record.

CallEventRecordType = 0x0A
(1)
servedIMSI
0x81
TBCD(3..8)
The IMSI of the MS performing the

action.
servedIMEI
0x82
TBCD(8)
The IMEI of the ME performing the

action.
servedMSISDN
0x83
ADRESS(2..9)
The primary MSISDN of the party

performing the action.
msClassmark
0x84
OCTET(2..3)
The mobile station classmark.
recordingEntity
0x85
ADRESS(2..9)
The E.164 number of the visited MSC

producing the record (MSC/VLR
number: TON+NPI+MSC identifier
number).
location
0xA6
OCTET(8)
The identity of the cell or the SAC,

including the location area code, from
which the request originated.
basicServices
0xA7
OCTET(3)
The basic service group(s) to which

the supplementary service applies.
Issue 1.00 (2008-02-25)
Page 98 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
supplService
0x88
OCTET(1)
The supplementary service or group of

supplementary services for which the
request was made. The field is set to 0
in case of USSD.
ssAction
0x89
ENUMERATE
D
SS actions such as activation,

deactivation, interrogation etc. The
field is set to ussdInvocation (7) in
case of USSD.
(1)
ssActionTime
0x8A
OCTET(9)
The time at which the action was

requested.
ssParameters
0xAB
OCTET
STRING
Service dependent parameters or

unstructured supplementary service
data, if defined for the SS action
recorded in this CDR.
(7..53)
ssActionResult
0xAC
INTEGER(4)
A more detailed reason for the release

of the connection.
callReference
0x8D
OCTET(1..8)

between transactions on the same MS.
recordExtensions
0xAE
SET OF (11 *
n)

systemType
0x8F
ENUMERATE
D

(1)
ussdCodingScheme
0x9F 7E
OCTET(1)
Indicates the USSD coding scheme in

the SS-action record generated for
USSD.
ussdString
0xBF 7F
SEQUENCE
OF
OCTET(1..40)
Indicates the USSD string entered by

subscribers in the SS-action record
generated for USSD.
ussdNotifyCounter
0x9F 81 00
INTEGER(1)
In the case of USSD, indicates the

times of notify procedure.
ussdRequestCounter
0x9F 81 01
INTEGER(1)
In the case of USSD, indicates the

times of request procedure.
additionalChgInfo
0xBF 81
05
SEQUENCE(3)

additional charging parameters, when
available.
classmark3
0x9F 81
0C
OCTET(2)
The mobile station classmark 3.
Issue 1.00 (2008-02-25)
Page 99 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
chargedParty
0x9F 81
0D
ENUMERATE
D
Indicates whether the calling party or

the called party is charged for the call.
(1)
chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
orgRNCorBSCId
0x9F 81 27
OCTET(3)
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
globalAreaID
0x9F 81
3C
OCTET(7)
The GCI of the GSM network or the

SAI of the WCDMA network.
subscriberCategory
0x9F 81
3E
OCTET(1)
firstmccmnc
0x9F 81 40
OCTET(3)
Indicates the MCC and MNC of the

network where SS action is initiated.
hotBillingTag
0x9F 81 48
INTEGER(1)

billing service. Shall be present only if
the hot charging function is applied.
tariffCode
0x9F 81 59
INTEGER(1)
The tariff code.
networkOperatorId
0x9F 81
5F
OCTET (1)
typeOfSubscribers
0x9F 81 60
ENUMERATE
D(1)
recordNumber
0x9F 81 68
INTEGER
zoneCode
0x9F 81 70
OCTET (2)
2.15 HLR Interrogation

If the generation of these records is enabled, an HLR interrogation record shall be created for
each interrogation performed for a mobile subscriber. These records may be produced in
either the HLR itself or the interrogating MSC. Figure 1.15 lists the formats of HLR
interrogation records.
Figure 1.15 HLR interrogation record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATE
D
HLR interrogation record.

CallEventRecordType = 0x0B
(1)
Issue 1.00 (2008-02-25)
Page 100 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
servedIMSI
0x81
TBCD(3..8)
The IMSI of the party being

interrogated, if successful.
servedMSISDN
0x82
ADRESS(2..9)
The MSISDN of the subscriber being

interrogated.
recordingEntity
0x83
ADRESS(2..9)

(MSC/VLR number:
basicService
0xA4
OCTET(3)
The bearer or teleservice employed.

Only for teleservice 21 (SMS-MT).
routingNumber
0xA5
ADRESS(2..17)
Routing number (MSRN, forwarding

no.) provided by the HLR if the
interrogation was successful.
interrogationTime
0x86
OCTET(9)
Time at which the interrogation was

invoked.
numberOfForwarding
0x87
INTEGER(1)
The number of times the call has

been forwarded if provided by ISUP.
interrogationResult
0xA8
INTEGER(4)
recordExtensions
0xA9
SET OF (11 *
n)

chargeAreaCode
0x9F 81
11
OCTET(1..3)

distance charge.
orgMSCId
0x9F 81
28
OCTET(3)
The SPC of the MSC.
callReference
0x9F 81
29
OCTET(1..8)

MS.
eCategory
0x9F 81
57
INTEGER(1..2)
The enhanced subscriber category.
networkOperatorId
0x9F 81
5F
OCTET (1)
recordNumber
0x9F 81
68
INTEGER
2.16 Common Equipment Usage Record

If the generation of these records is enabled, a common equipment usage record shall be
created in the VMSC to record the usage (duration) of common equipment, e.g. conference
Issue 1.00 (2008-02-25)
Page 101 of 173
CONFIDENTIAL
circuits, employed by a mobile subscriber. Figure 1.16 lists the formats of common equipment
usage records.
Figure 1.16 Common equipment usage record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
Common equipment usage record.

CallEventRecordType = 0x0E
(1)
equipmentType
0x81
INTEGER(1)
The type of common equipment e.g.

Conference circuit.
equipmentId
0x82
INTEGER(1)
The local ID of the equipment

employed.
servedIMSI
0x83
TBCD(3..8)
The IMSI of the party responsible

for the seizure of the equipment.
servedIMEI
0x9F 66
TBCD(8)
The IMEI of the calling ME, if

available.
servedMSISDN
0x84
ADRESS(2..9)
The primary MSISDN of the served

party.
recordingEntity
0x85
ADRESS(2..9)

(MSC/VLR number:
basicService
0xA6
OCTET(3)
The bearer or teleservice employed.
changeOfService
0xA7
SEQUENCE OF
A list of changes of basic service

during a connection each timestamped.
( (18..27) * n)
supplServicesUsed
0xA8
SEQUENCE OF
(16 * n)
Supplementary services invoked as a

result of this connection. This field
shall be present when one or more
supplementary services have been
invoked.
seizureTime
0x89
OCTET(9)
The time stamp at which the

equipment was seized.
releaseTime
0x8A
OCTET(9)
The time stamp at which the

equipment was released.
callDuration
0x8B
INTEGER(1..2)
The total duration of the usage of the

equipment.
callReference
0x8C
OCTET(1..8)

MS. It is also used to identify all
partial records and transactions
belonging to the same connection.
Issue 1.00 (2008-02-25)
Page 102 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
sequenceNumber
0x8D
INTEGER(1)
The partial record sequence number,

only present in case of partial
records.
recordExtensions
0xAE
SET OF (11 * n)

systemType
0x8F
ENUMERATED

(1)
rateIndication
0x90
OCTET(1)

parameters for the basic service were
signaled between the MS/UE and the
network, see TS 24.008. Reserved
for future use.
fnur
0x91
ENUMERATED
The user data rate applied for the

connection in the fixed network.
Shall only be present for 2G HSCSD
connections and for UMTS data
connections.
(1)
partialRecordType
0x92
ENUMERATED
(1)

caused the generation of a partial
record. This field is mandatory in
causeForTerm
0x9F 64
INTEGER(1)
The reason for the release of the

connection.
diagnostics
0xBF 65
INTEGER(4)

additionalChgInfo
0xBF 81 05
SEQUENCE(3)

when available.
chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
orgRNCorBSCId
0x9F 81 27
OCTET(3)
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
subscriberCategory
0x9F 81 3E
OCTET(1)
hotBillingTag
0x9F 81 48
INTEGER(1)

billing service. Shall be present only
applied.
Issue 1.00 (2008-02-25)
Page 103 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
networkOperatorId
0x9F 81 5F
OCTET (1)
typeOfSubscribers
0x9F 81 60
ENUMERATED(
1)
recordNumber
0x9F 81 68
INTEGER
2.17 Terminating CAMEL Call Attempt

If the generation of these records is enabled, a terminating CAMEL call attempt record shall
be generated for each call toward a subscriber with a T-CSI or VT-CSI and if the terminating
triggers criteria are met. The record is generated in the GMSC/gsmSSF carrying out the
terminating CAMEL call handling and in the MSC server/gsmSSF carrying out the visited
terminating CAMEL call attempt. Figure 1.17 lists the formats of terminating CAMEL call
attempt records.
Figure 1.17 Terminating CAMEL call attempt record
Field
2G
3G
TAG
TYPE
Description
recordtype
0x80
ENUMERATED
Terminating CAMEL
interrogation record.
0x11
(1)
servedIMSI
0x81
TBCD(3..8)

party.
servedMSISDN
0x82
ADRESS(2..9)
The MSISDN of the called

party.
recordingEntity
0x83
ADRESS(2..9)

number).
interrogationTime
0x84
OCTET(9)
Time at which the

interrogation with HLR was
invoked.
destinationRoutingAddress
0x85
ADRESS(2..17)
The number available for

routing after the CAMEL
server enquiry.
gsm-SCFAddress
0x86
ADRESS(2..9)

applied.
Issue 1.00 (2008-02-25)
Page 104 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
serviceKey
0x87
INTEGER(1..4)

applied.
0x88
OCTET(1..8)
network nodes.
mSCAddress
0x89
ADRESS(2..9)

defaultCallHandling
0x8A
ENUMERATED
Indicates whether a
field shall be present only if
been applied.
(1)
recordExtensions
0xAB
SET OF(11 * n)
A set of network or
calledNumber
0x8C
ADRESS(2..17)

party as received by the
GMSC/gsmSSF.
callingNumber
0x8D
ADRESS(2..17)

mscIncomingROUTE
0xAE
IA5(1..32)
The incoming GMSC route

on which the call is
originated.
mscOutgoingROUTE
0xAF
IA5(1..32)

left the GMSC.
seizureTime
0x90
OCTET(9)
The time of incoming traffic

channel seizure (for
unsuccessful call attempts).
At present, it is not
available.
answerTime
0x91
OCTET(9)

releaseTime
0x92
OCTET(9)

channel.
Issue 1.00 (2008-02-25)
Page 105 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
callDuration
0x93
INTEGER(1..2)

the connection for
successful calls, the holding
time of call attempts.
causeForTerm
0x95
INTEGER(1)

of the connection.
diagnostics
0xB6
INTEGER(4)

the release of the
connection.
callReference
0x97
OCTET(1..8)
A local identifier
sequenceNumber
0x98
INTEGER(1)

0x99
INTEGER(1)

points (TDP and EDP) were
encountered. Shall be
applied.
levelOfCAMELService
0x9A
BIT STRING(2)

applied.
freeFormatData
0x9B
OCTET(1..160)

messages. The data can be
0xBC
SEQUENCE OF
A set of CAMEL
these IEs contains
CAMEL is applied.
((104..124) * n)
Issue 1.00 (2008-02-25)
Page 106 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
0x9D
BOOLEAN(1)

CDR.
mscServerIndication
0x9E
BOOLEAN(1)
Indication if the CAMEL

call handling is active in the
MSC server.
0x9F 1F
ENUMERATED
Indicates whether or not a

default call handling for the
dialed service. This field
shall be present only if
been applied.
(1)
gsm-SCFAddress-2
0x9F 20
ADRESS(2..9)

the subscriber for the
service.
serviceKey-2
0x9F 21
INTEGER(1..4)

to be applied for the second
freeFormatData-2
0x9F 22
OCTET(1..160)

service. The data can be
indicator.
0x9F 23
BOOLEAN(1)

for the second service from
this CDR is to be appended
to free format data in
previous partial CDR. Shall
service.
Issue 1.00 (2008-02-25)
Page 107 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
partialRecordType
0x9F 2A
ENUMERATED

field is mandatory in case of
partial records.
(1)
basicService
0xBF 81 02
OCTET(3)

employed.
additionalChgInfo
0xBF 81 05
SEQUENCE(3)

chargedParty
0x9F 81 0D
ENUMERATED

(1)
0x9F 81 0E
ADRESS(2..17)

called party.
chargeAreaCode
0x9F 81 11
OCTET(1..3)

orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
subscriberCategory
0x9F 81 3E
OCTET(1)
hotBillingTag
0x9F 81 48
INTEGER(1)

0x9F 81 4E
ADRESS (2..17)

announcement in the case of
resource charging.
csReference
0x9F 81 5C
OCTET(1..8)

number.
csaReference
0x9F 81 5D
INTEGER (1..4)
The call segment

number.
camelphase
0x9F 81 5E
ENUMERATED
(1)l
The CAMEL version

number.
networkOperatorId
0x9F 81 5F
OCTET (1)
typeOfSubscribers
0x9F 81 60
ENUMERATED(
1)
The type of roaming

subscriber.
recordNumber
0x9F 81 68
INTEGER

CDR.
Issue 1.00 (2008-02-25)
Page 108 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
partyRelCause
0xBF 81 6C
PartyRelCause

release.
translatedNumber
0x9F 81 75
ADRESS (2..17)

interactionWithIP
0x9F 81 47
NULL (0)

between SSP and IP,
GsmSCF play
start charging.
2.18 IMEI Observation Ticket

An observed IMEI ticket is generated whenever greylisted, blacklisted or non-whitelisted
mobile equipment is detected during an IMEI check. The purpose of the ticket is to link the
mobile equipment under observation with its current user (IMSI). The ticket also includes
information describing when and where the equipment was used to enable the tracking of
such equipment. Finally, if the ticket was triggered by a call attempt, a call reference is
provided in order to locate the corresponding call record. The IMEI tickets are generated by
the NEF of the MSC performing the IMEI check. Figure 1.18 lists the formats of IMEI
tickets.
Figure 1.18 IMEI ticket
Field
2G
3G
TAG
TYPE
Description
servedIMEI
0x80
TBCD(8)
IMEI of the observed mobile

equipment
imeiStatus
0x81
ENUMERATED
The result of the IMEI check e.g.

blacklisted, greylisted, unknown.
(1)
servedIMSI
0x82
TBCD(3..8)
The IMSI of the subscriber currently

using the mobile equipment.
servedMSISDN
0x83
ADRESS(2..9)

currently using the observed mobile
equipment, only available if the event
that triggered the IMEI check was an
MOC, MTC, SMS-MO or SMS-MT.
recordingEntity
0x84
ADRESS(2..9)
The E.164 number of the visited MSC

producing the record (MSC/VLR
number: TON+NPI+MSC identifier
number).
eventTime
0x85
OCTET(9)
The time at which the IMEI check was

performed.
Issue 1.00 (2008-02-25)
Page 109 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
location
0xA6
OCTET(8)
The location area code and cell

identity of the cell from which the
mobile equipment was used.
imeiCheckEvent
0x87
INTEGER(1)
The event that caused IMEI checking

to take place.
callReference
0x88
OCTET(1..8)

between transactions on the same MS.
recordExtensions
0xA9
SET OF (11 * n)

chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
orgMSCId
0x9F 81 28
OCTET(3)
The SPC of the MSC.
networkOperatorId
0x9F 81 5F
OCTET (1)
recordNumber
0x9F 81 68
INTEGER
2.19 Location Update (VLR)

If enabled, a VLR location update record shall be produced in the VLR for each location
registration or location update received by the VLR for a mobile subscriber. Figure 1.19 lists
the formats of Location update (VLR) records.
Figure 1.19 Location update (VLR) record
Field
2G
3G
TAG
TYPE
Description
recordType
0x80
ENUMERATED
(1)
Location update (VLR) record.

CallEventRecordType = 0x0D
servedIMSI
0x81
TBCD(3..8)
The IMSI of the served MS.
servedMSISDN
0x82
ADRESS(2..9)
The primary MSISDN of the party

performing the location update.
recordingEntity
0x83
ADRESS(2..9)

(MSC/VLR number:
number).
oldLocation
0xA4
SEQUENCE (16)
Location area and cell before the

location update.
newLocation
0xA5
SEQUENCE (16)
Location area and cell after the

location update.
Issue 1.00 (2008-02-25)
Page 110 of 173
CONFIDENTIAL
Field
2G
3G
TAG
TYPE
Description
msClassmark
0x86
OCTET(2..3)
The mobile station classmark.
updateTime
0x87
OCTET(9)
Time at which the update was

invoked.
updateResult
0xA8
CHOICE (4)
The result of the location update if

unsuccessful.
recordExtensions
0xA9
SET OF (11 * n)

gsm-SCFAddress
0x8A
ADRESS(2..9)
The CAMEL server serving the

subscriber. Shall be present only if
CAMEL is applied.
serviceKey
0x8B
INTEGER(1..4)
The CAMEL service logic to be

applied. Shall be present only if
CAMEL is applied.
callReference
0x8C
OCTET(1..8)

MS. It is also used to identify all
partial records and transactions
belonging to the same connection.
locationUpdateType
0x8D
ENUMERATED
The type of location update.
(1)
chargeAreaCode
0x9F 81 11
OCTET(1..3)

distance charge.
networkOperatorId
0x9F 81 5F
OCTET(1)
recordNumber
0x9F 81 68
INTEGER
Issue 1.00 (2008-02-25)
Page 111 of 173
Description of Record Fields
The CDR fields are the specific segments in the CDR. Refer to chapter 2"Record Contents."
This section describes the functions of each field in the CDR and the ASN.1 encoding.
3.1 Additional Charging Information

This field is used to identify whether to charge the record and the additional charging
information of the record. This field consists of two parts, a charge indicator and additional
charging parameters.
The charge indicator is derived from the information contained within the ISUP
"backward call indicator" and may be used to store a charge indicator (charge/no charge)
received from another network node.
The additional charging parameters are non-standard and intended to permit the inclusion
of further charging information received from Intelligent Network and/or Value Added
Service nodes.
The ASN.1 encoding of this field is as follows:

ChargeIndicator
::= INTEGER
{
noIndication
(0),
noCharge
(1),
charge
(2)
}
3.2 aiurRequested
This field refers to the total Air Interface User Rate Requested by the MS at call setup. It is
applicable only to non-transparent data services for High Speed Circuit Switched Data
(HSCSD) connections. The ASN.1 encoding of this field is as follows:
AiurRequested
::= ENUMERATED
{
--- See Bearer Capability TS 24.008
-- (note that value "4" is intentionally missing

-- because it is not used in TS 24.008)
-aiur09600BitsPerSecond
aiur14400BitsPerSecond
aiur38400BitsPerSecond1
(1),
(2),
(3),
(5),
(6),
(7),
(8),
(9),
(10),
(11),
(12)
3.3 AoC parameters / change of AoC parameters

This field contains the set of charge advice (AoC) parameters sent to the MS on call set-up. If
further sets of parameters are sent during the call, as a result of a tariff switch-over for
example, then this may be recorded in the Change of AoC Parameter field including the time
at which the change occurred. It should be noted that the Change of AoC Parms. field is
optional and not required if partial records are generated on tariff switch-over. Refer to The
ASN.1 encoding of this field is as follows:
AOCParameters ::= SEQUENCE
{
--- See TS 22.024.
-e1
[1] EParameter OPTIONAL,
e2
e3
e4
e5
e6
e7
[7] EParameter OPTIONAL
}
3.4 audioDataType
This field indicates whether the service used by the user is voice service or data service. The
audioDataType ::= ENUMERATED
{
audio
(0),
fax
(1),
AUDIO_DATA_BUTT (255)
}
3.5 basicService/changeOfService/isdnBasicService
This field contains the code of the basic service employed on call set-up. Any alteration
to the basic service during the connection may be recorded in the change of service field
including the time at which the change took place. Refer to 3GPP TS 29.002 for details.
This field is optional and may be omitted if partial records are created whenever the
basic service is changed.
In the case of the transit record the ISDN basic service employed is generally not
available. However, if the device on which the call originates/terminates is connected via
ISDN digital subscriber signaling then the appropriate ISDN basic service code should
be recorded in the record. One possible example includes the direct connection of an
ISDN PABX to an MSC/VLR.
The ASN.1 encoding of the three fields is as follows:

BasicServiceCode ::= CHOICE
{
bearerService [2] BearerServiceCode,
teleservice [3] TeleserviceCode,
isdnService [4] IsdnServiceCode
}
TeleserviceCode ::= OCTET STRING (SIZE (1))
-- This type is used to represent the code identifying a single
-- teleservice, a group of teleservices, or all teleservices. The
-- services are defined in TS GSM 02.03.
-- The internal structure is defined as follows:
-- bits 87654321: group (bits 8765) and specific service
-- (bits 4321)
------------------------
allTeleservices
(0x00),
allSpeechTransmissionServices (0x10),
telephony
(0x11),
emergencyCalls
(0x12),
allShortMessageServices
shortMessageMT-PP
shortMessageMO-PP
(0x20),
(0x21),
(0x22),
allFacsimileTransmissionServices (0x60),
facsimileGroup3AndAlterSpeech (0x61),
automaticFacsimileGroup3
(0x62),
facsimileGroup4
(0x63),
The following non-hierarchical Compound Teleservice Groups
are defined in TS GSM 02.30:
allDataTeleservices
(0x70),
covers Teleservice Groups 'allFacsimileTransmissionServices'
and 'allShortMessageServices'
allTeleservices-ExeptSMS
(0x80),
covers Teleservice Groups 'allSpeechTransmissionServices' and
'allFacsimileTransmissionServices'
--------------------------
Compound Teleservice Group Codes are only used in call

independent supplementary service operations, i.e. they
are not used in InsertSubscriberData or in
DeleteSubscriberData messages.
allVoiceGroupCallServices (0x90),
voiceGroupCall
(0x91),
voiceBroadcastCall
(0x92),
allPLMN-specificTS
plmn-specificTS-1
plmn-specificTS-2
plmn-specificTS-3
plmn-specificTS-4
plmn-specificTS-5
plmn-specificTS-6
plmn-specificTS-7
plmn-specificTS-8
plmn-specificTS-9
plmn-specificTS-A
plmn-specificTS-B
plmn-specificTS-C
plmn-specificTS-D
plmn-specificTS-E
plmn-specificTS-F
(0xd0),
(0xd1),
(0xd2),
(0xd3),
(0xd4),
(0xd5),
(0xd6),
(0xd7),
(0xd8),
(0xd9),
(0xda),
(0xdb),
(0xdc),
(0xdd),
(0xde),
(0xdf)
BearerServiceCode ::= OCTET STRING (SIZE (1))

-- bearer service, a group of bearer services, or all bearer
-- services. The services are defined in TS 3GPP TS 22.002.
-- The internal structure is defined as follows:
--- plmn-specific bearer services:
-- bits 87654321: defined by the HPLMN operator
-- rest of bearer services:
-- bit 8: 0 (unused)
-- bits 7654321: group (bits 7654), and rate, if applicable
-- (bits 321)
---------------
allBearerServices (0x00),
allDataCDA-Services (0x10),
dataCDA-300bps
(0x11),
dataCDA-1200bps (0x12),
dataCDA-1200-75bps (0x13),
general-dataCDA
(0x17), --not transparency service, such as 3.1k HZ audio
allDataCDS-Services (0x18),
dataCDS-1200bps (0x1a),
dataCDS-2400bps (0x1c),
dataCDS-4800bps (0x1d),
dataCDS-9600bps (0x1e),
-- general-dataCDS
------------------------------------------------------
(0x1f),
-- transparency service, such as 64K UDI H.223 and H.245 VP
allPadAccessCA-Services (0x20),
padAccessCA-300bps
(0x21),
padAccessCA-1200bps
(0x22),
PadAccessCA-1200-75bps (0x23),
padAccessCA-2400bps
(0x24),
padAccessCA-4800bps
(0x25),
padAccessCA-9600bps
(0x26),
general-padAccessCA
(0x27),
allDataPDS-Services
dataPDS-2400bps
dataPDS-4800bps
dataPDS-9600bps
general-dataPDS
(0x28),
(0x2c),
(0x2d),
(0x2e),
(0x2f),
allAlternateSpeech-DataCDA
(0x30),
allAlternateSpeech-DataCDS
(0x38),
allSpeechFollowedByDataCDA
(0x40),
allSpeechFollowedByDataCDS
(0x48),
The following non-hierarchical Compound Bearer Service

Groups are defined in TS GSM 02.30:
allDataCircuitAsynchronous
(0x50),
covers "allDataCDA-Services", "allAlternateSpeech-DataCDA" and
"allSpeechFollowedByDataCDA"
allDataCircuitSynchronous
(0x58),
covers "allDataCDS-Services", "allAlternateSpeech-DataCDS" and
"allSpeechFollowedByDataCDS"
allAsynchronousServices
(0x60),
covers "allDataCDA-Services", "allAlternateSpeech-DataCDA",
"allSpeechFollowedByDataCDA" and "allPadAccessCDA-Services"
allSynchronousServices
(0x68),
covers "allDataCDS-Services", "allAlternateSpeech-DataCDS",
"allSpeechFollowedByDataCDS" and "allDataPDS-Services"
Compound Bearer Service Group Codes are only used in call
independent supplementary service operations, i.e. they
are not used in InsertSubscriberData or in
DeleteSubscriberData messages.
allPLMN-specificBS
plmn-specificBS-1
plmn-specificBS-2
plmn-specificBS-3
plmn-specificBS-4
plmn-specificBS-5
plmn-specificBS-6
plmn-specificBS-7
plmn-specificBS-8
(0xd0),
(0xd1),
(0xd2),
(0xd3),
(0xd4),
(0xd5),
(0xd6),
(0xd7),
(0xd8),
--------
plmn-specificBS-9
plmn-specificBS-A
plmn-specificBS-B
plmn-specificBS-C
plmn-specificBS-D
plmn-specificBS-E
plmn-specificBS-F
(0xd9),
(0xda),
(0xdb),
(0xdc),
(0xdd),
(0xde),
(0xdf)
NOTE:UMTS Bearer servide code:

general-dataCDA (0x17), --not transparency service, such as 3.1k HZ audio
general-dataCDS (0x1f),-- transparency service, such as 64K UDI H.223 and H.245 VP
IsdnServiceCode ::= OCTET STRING (SIZE(1))
--This parameter identifies the ISDN Basic service as defined in ETSI specification ETS 300 196.
-- allServices
'00'h
-- speech
'01'h
-- unrestricteDigtalInfo
'02'h
-- audio3k1HZ
'03'h
-- unrestricteDigtalInfowithtoneandannoucement '04'h
-- telephony3k1HZ
'20'h
-- teletext
'21'h
-- telefaxGroup4Class1
'22'h
-- videotextSyntaxBased
'23'h
-- videotelephony
'24'h
-- telefaxGroup2-3
'25'h
-- telephony7kHZ
'26'h
ChangeOfService
::= SEQUENCE
{
basicService
[0] BasicServiceCode,
transparencyInd
[1] TransparencyInd
OPTIONAL,
changeTime
[2] TimeStamp,
rateIndication
[3] RateIndication
OPTIONAL,
fnur
[4] Fnur OPTIONAL
}
ISDN Basic Service
::= OCTET STRING (SIZE(1))
--This parameter identifies the ISDN Basic service as defined in ETSI specification ETS 300 196.
-- allServices
'00'h
-- speech
'01'h
-- unrestricteDigtalInfo
'02'h
-- audio3k1HZ
'03'h
-- unrestricteDigtalInfowithtoneandannoucement '04'h
-- telephony3k1HZ
'20'h
-- teletext
'21'h
-- telefaxGroup4Class1
'22'h
-- videotextSyntaxBased
'23'h
-- videotelephony
'24'h
-- telefaxGroup2-3
'25'h
-- telephony7kHZ
'26'h
3.6 bCategory
This field indicates the status of the called party. If the call is disconnected due to called party
busy, the value of this field is subscriberBusy. If the call disconnection is not due to called
party busy, the value of this field is subscriberFree. The ASN.1 encoding of this field is as
follows:
BCategory ::= ENUMERATED
{
subscriberFree (0) ,
subscriberBusy (1),
subscriberNoIndication (3)
}
3.7 callDuration
This field contains the relevant call duration in seconds. For complete (answered) calls the
relevant duration is the chargeable duration from answer to release of the traffic channel. For
partial records this is the duration of the individual partial record and not the cumulative
duration of the call. The ASN.1 encoding of this field is as follows:
CallDuration
::= INTEGER
--- The call duration in seconds.
-- For successful calls this is the chargeable duration.
-- For call attempts this is the call holding time.
The format of the time stamp is closely related to call duration. The ASN.1 encoding of the
time stamp is as follows:
TimeStamp
::= OCTET STRING (SIZE(9..10))
--- The contents of this field are a compact form of the UTCTime format
-- containing local time plus an offset to universal time. Binary coded
-- decimal encoding is employed for the digits to reduce the storage and
-- transmission overhead
-- e.g. YYMMDDhhmmssShhmm
-- where
-- YY = Year 00 to 99 BCD encoded
-- MM = Month 01 to 12 BCD encoded
-- DD = Day 01 to 31 BCD encoded
-- hh = hour 00 to 23 BCD encoded
-- mm = minute 00 to 59 BCD encoded
-- ss = second 00 to 59 BCD encoded
-- S = Sign 0 = "+", "-" ASCII encoded
-- hh = hour 00 to 23 BCD encoded
-- mm = minute 00 to 59 BCD encoded
-- DST = 00 to 120
INTEGER encoded (DST is optional)
If CAMEL is invoked for the call and a control relationship is existing, the call might
continue after a RELEASE or a DISCONNECT from the called party side received by the
gsmSSF. The call duration of the incoming leg is stored in the main body of the call record.
For each outgoing leg the call duration is stored in the respective 'CAMELInformation'
module.
An example of how to use the call duration and the timestamps is given in Figure 1.1 and
Figure 1.20. It shows a CAMEL controlled mobile originated follow-on scenario. The
uppermost arrow marks the over all duration of the call that is to be measured and stored in
the main body of the respective MOC record. The duration before t5 (incoming leg) or t4
(outgoing leg) needs not to be stored since the call is answered later on. The call duration in
the first outgoing leg module contains the time interval from t 4 to t6 (period ). The call
duration measurement of the second outleg is started with t9 and ended with t10 (interval ).
The timestamps t1, t2, t3, t7, t8 and t12 mentioned in Figure 1-3 and Table 1-20 are for
completion reasons only.
Figure 1.1 Call duration
inc. leg
outg. leg 1
outg. leg 2
outg. leg 3
t1 t2 t3
t4 t5
t6 t7 t8 t9
t10 t11 t12
t13
time
call duration of incoming leg =

call duration of outgoing leg =
holding time of outgoing leg =
Figure 1.20 Description of the time information

Point in Time
Signaling Message Sent/Received
Duration Logging
Trigger Detection Point Encountered

t1
SETUP; TDP(control)
t2
IAM
t3
ACM
t4
ANSWER
start of call duration (outg.

leg 1)
t5
CONNECT
start of call duration (inc.

leg)
t6
RELEASE; EDP(control)
stop of call duration (outg.

leg 1)
t7
IAM
seizure of outg. leg 2
t8
ACM
t9
ANSWER
start of call duration (outg.

leg 2)
Point in Time
Signaling Message Sent/Received
Duration Logging
Trigger Detection Point Encountered

t10
stop of call duration (outg.

leg 2)
t11
IAM

start of holding time (outg.
leg 3)
t12
ACM
t13
stop of holding time (outg.

leg 3)
3.8 calling Number/called Number / connected

Number/translated Number
In general, a calling Number/called Number / connected Number/translated Number is in the
format of ITU-T E.164, but may also include other numbering plans, for example, X 121.
Each of these fields includes the type of number and number plan as specified in detail in
3GPP TS 24.008.
The calling number is the number received from the network on mobile terminated call
set-up as defined in 3 GPP TS 24.008 [4].
The called number is the number received from the mobile station on mobile originated
call set-up as defined in 3GPP TS 24.008 [4]. In case of CAMEL initiated call forward
(CF), the called (forwarded-to) number is returned by CAMEL.
The translated number is the result of any digit translation performed by the MSC on the
called number received from the mobile station on mobile originated call set-up.
The connected number is the number of the actual party reached as defined in 3GPP TS
24.008. Although this is normally identical to the called number it may differ. This
parameter is not included if identical to the called number.
The following examples are intended to explain the use of these fields:
EXAMPLE 1:Called Number = Connected Number
Normal call from a mobile subscriber to a mobile subscriber or to a PSTN subscriber
EXAMPLE 2: Called Number != Connected Number
In case of routing to a PABX with Automatic Call Distribution or to an ISDN Basic Access
with several devices attached. The connected number is that of the party actually reached.
N.B. The recording of the actual number connected may be limited by the capability of
intermediate signaling connections.
EXAMPLE 3: MTC record for Call Forwarding ("A" -> "B" -> "C")
In case of call forwarding, the connected number recorded in the MTC record of the "B"
subscriber is that of the forwarded-to party or "C" subscriber. The calling party field contains
the number of the "A" subscriber.
EXAMPLE 4: Translated Number

This field is only present if digit translation is applied by the MSC to the called number
received from the mobile station. Examples include abbreviated dialing codes and service
numbers.
For the definitions of the numbers described, refer to the descriptions of the calling number,
called number, and the connected number in the TS 24.008. The descriptions of the number
consist of two parts, with the first part as address information and numbering plan of the
number and the second part as the number information about the TBCD format.
The ASN.1 encoding of the above fields is as follows:
CallingNumber
CalledNumber
TranslatedNumber
ConnectedNumber
::= BCDDirectoryNumber
3.9 callReference
This field uniquely identifies a call or transaction on one side of the interface (i.e. 'A' or 'B'
side) It is also used to identify all partial records and transactions belonging to the same
connection. For example, a unique callReference generated during a call can uniquely identify
the call.
CallReference ::= OCTET STRING (SIZE (1..8)).
3.10 CallType
This field indicates the type of the call. The value of this field can be one of the following:
Unknown
Incoming
Outgoing
Internal
Tandem

CallType ::= ENUMERATED
{
unknown (0),
internal (1),
incoming (2),
outgoing (3),
tandem (4)
}
3.11 cAMELCallLegInformation
This field contains a set of CAMEL information elements (IEs) according to the number of
outgoing CAMEL call legs.

This field consists of CAMEL IEs in the SET structure. A CDR is generated by the Huawei
MSC for the CAMEL LEG Information, and the CDR is then correlated to the corresponding
main CDR by the Huawei iGWB. See CAMEL IEs in the following description and refer to
3GPP 32.250 for details.
CAMELInformation
::= SET
{
cAMELDestinationNumber
[1] CAMELDestinationNumber
OPTIONAL,
connectedNumber
[2] ConnectedNumber
OPTIONAL,
roamingNumber
[3] RoamingNumber
OPTIONAL,
mscOutgoingROUTE
[4] ROUTE
OPTIONAL,
seizureTime
[5] TimeStamp
OPTIONAL,
answerTime
[6] TimeStamp
OPTIONAL,
releaseTime
[7] TimeStamp
OPTIONAL,
callDuration
[8] CallDuration
OPTIONAL,
dataVolume
[9] DataVolume
OPTIONAL,
[10] CAMELInitCFIndicator
OPTIONAL,
causeForTerm
[11] CauseForTerm
OPTIONAL,
cAMELModification
[12] ChangedParameters
OPTIONAL,
freeFormatData
[13] FreeFormatData
OPTIONAL,
diagnostics
[14] Diagnostics
OPTIONAL,
[15] BOOLEAN
OPTIONAL,
freeFormatData-2
[16] FreeFormatData
OPTIONAL,
freeFormatDataAppend-2 [17] BOOLEAN
OPTIONAL,
translatedNumber
[18] TranslatedNumber
OPTIONAL,
additionalChgInfo
[19] AdditionalChgInfo
OPTIONAL,
[20] DefaultCallHandling
OPTIONAL,
gsm-SCFAddress-2
[21] Gsm-SCFAddress
OPTIONAL,
serviceKey-2
[22] ServiceKey
OPTIONAL,
legID
[23] CAMELLegID
OPTIONAL,
partialRecordType
[24] PartialRecordType
OPTIONAL
}
3.12 cAMELDestinationNumber
This field contains Destination/Called Subscriber Number modified by CAMEL service. If
not modified then this field may contain original Destination Number also when CAMEL is
not active. Only the destination delivered by the SCP is valid.
CAMELDestinationNumber ::= DestinationRoutingAddress
DestinationRoutingAddress ::= BCDDirectoryNumber
3.13 cAMELInitCFIndicator
The purpose of this field is to distinguish CAMEL call forwarding service scenarios from
standard GSM call forwarding scenarios. From the Basic Call State Model (BCSM)'s point of
view this field is set to 'CF' whenever the Originating CAMEL Subscription Information
(O_CSI) was applied after terminating CAMEL call processing had been taken place and the
call destination is changed. For the avoidance of doubt: this flag does not depend on other
modified call parameter(s) (e.g.: redirection information, etc.) received in the
CAP_CONNECT message of the Terminating CAMEL Subscription Information (T_CSI)
service.
This flag also indicates that another record might be generated, one containing the charging
information related to the terminating CAMEL service and one containing the charging
information related to the originating CAMEL service.
CAMELInitCFIndicator ::= ENUMERATED
{
noCAMELCallForwarding (0),
cAMELCallForwarding (1)
}
3.14 cAMELSMSInformation
This field contains following CAMEL information for mobile originated and terminated SMS:
Default SMS handling: This field indicates whether or not a CAMEL encounters default
SMS handling. This field shall be present only if default SMS handling has been applied.
Free format data

See Free format data.
Calling Party Number: This field contains Calling Party Number modified by CAMEL
service.
CAMEL modified service centre: This field contains SMS-C address modified by
CAMEL service.
CAMEL Destination Subscriber Number: This field contains short message Destination
Number modified by CAMEL service.
The ASN.1 encoding of cAMELSMSInformation is as follows:

CAMELSMSInformation ::= SET
{
gsm-SCFAddress
[1] Gsm-SCFAddress
OPTIONAL,
serviceKey
[2] ServiceKey
OPTIONAL,
defaultSMSHandling
[3] DefaultSMS-Handling OPTIONAL,
freeFormatData
[4] FreeFormatData
OPTIONAL,
callingPartyNumber
[5] CallingNumber
OPTIONAL,
destinationSubscriberNumber [6] CalledNumber
OPTIONAL,
cAMELSMSCAddress
[7] AddressString
OPTIONAL,
smsReferenceNumber
[8] CallReferenceNumber OPTIONAL
}
3.15 chargeAreaCode
This field indicates the logical charging area code for the calling number. The ASN.1
encoding of this field is as follows:
ChargeAreaCode ::= OCTET STRING(SIZE (1..3))
3.16 calledChargeAreaCode
This field indicates the logical charging area code of the called number. The ASN.1 encoding
of this field is as follows:
ChargeAreaCode ::= OCTET STRING(SIZE (1..3)
3.17 callEmlppPriority/
callerDefaultEmlppPriority/calledEmlppPriority
This field contains the enhanced Multi Level Precedence and Preemption (eMLPP) priority
information of the subscriber. For more details, refer to the 3GPP TS 29.002. The ASN.1
encoding of this field is as follows:
EmlppPriority::= OCTET STRING (SIZE (1))
--priorityLevelA EMLPP-Priority ::= 6
--priorityLevelB EMLPP-Priority ::= 5
--priorityLevel0 EMLPP-Priority ::= 0
3.18 camelphase
This field indicates the CAMEL phase used by a CAMEL call. The ASN.1 encoding of this
field is as follows:
CAMELVPHASE
::= ENUMERATED
{
wininapphase0
(0),
wincamelphase1
(1),
wincamelphase2
(2),
wincamelphase3
(3),
wincamelphase4
(4),
wininapphaseericsson
(8),
wininapphasesiemens
(16),
wininapphasenortel
(24),
wininapphase902
(32),
wininapphasechina
(128),
wininapphasebrazil
(136),
wininapphaserussion
(144),
wininapphaseuk
(152),
wincamelbutt
(255)
}
3.19 cARP
cARP (short for Circuit Assignment Reserve Priority) indicates the CARP value registered by
the subscriber. The ASN.1 encoding of this field is as follows:
CARP
::= INTEGER(0..255)
3.20 Category
This field contains the Category information saved in the MSC/VLR by the HLR through
inserting subscriber data during location updating. The ASN.1 encoding of this field is as
follows:
SubscriberCategory ::= OCTET STRING (SIZE (1))
-- unknownuser = 00,
-- frenchuser = 01,
-- englishuser = 02,
-- germanuser = 03,
-- russianuser = 04,
-- spanishuser = 05,
-- specialuser = 06,
-- reserveuser = 09,
-- commonuser = 0a,
-- superioruser = 0b,
-- datacalluser = 0c,
-- testcalluser = 0d,
-- spareuser = 0e,
-- payphoneuser = 0f,
-- coinuser = 20,
-- isup224
= 0xe0
3.21 chargedParty
This field indicates whether the calling party or the called party is charged or it indicates
whether the call is charged. This field may be modified by the SCP. The ASN.1 encoding of
this field is as follows:
ChargedParty ::= ENUMERATED
{
callingParty
(0),
calledParty
(1)
}
3.22 classmark3
This field contains the radio access capability information about the MS. The ASN.1 encoding
Classmark3 ::= OCTET STRING(SIZE(2))
3.23 concatenatedSMSReferenceNumber
This field indicates that if the length of a short message exceeds the maximum length (140
bytes), the MS splits the short message into several short messages. To correlate these split
segments, the protocol uses the same concatenated SMS reference numbers (CSRNs) to
identify the segments. The sequence number of the current SMS increases by one for each
split segment. The maximum number of SMS in the concatenated SMS indicated the number
of split segments.
Figure 1.1 shows the method of splitting the short message.
Figure 1.1 Method of splitting the short message
Compression Header
HHeannder Header
Compressed Data (CD)
Compression Footer
Segmentation / De-segmentation
TP-UDH
CH
CD
TP-UDH
First segment
CD
TP-UDH
CD
Intermediate segments
CF
Final segment
For example, the subscriber sends two messages in two segments and in four segments
respectively.
Concatenated
SMS
Reference
Number
Maximum
Number Of
SMS In The
Concatenated
SMS
Sequence Number Of The Current SMS
Picture1
Picture2
First
Segment
Second
Segment
Last
Segment
2

ConcatenatedSMSReferenceNumber
::= INTEGER(0..65535)
3.24 csReference
This field indicates that a call segment may contain one or multiple call legs, and the call legs
are controlled by the same SSF. This field identifies the call segment used for communication
by all the participants in a call.
CAMELCSReference
::= OCTET STRING (SIZE (1..8))
3.25 csaReference
This field indicates that a CSA may contain one or multiple call segments, the call legs in
different call segments within the same CSA. This field is used to correlate the CSA flags of
the call segments. The ASN.1 encoding of this field is as follows:

CAMELCSAReference
::= INTEGER (0..4294967295)
3.26 cUGIndex
A value assigned by the network to identify a CUG, the CUG index has significance only
between the subscriber and network.
CUGIndex
::= OCTET STRING(SIZE (2))
3.27 cUGOutgoingAccessIndicator
This field indicates the subscriber with an Outgoing Access. The ASN.1 encoding of this field
is as follows:
CUGOutgoingAccessIndicator ::= ENUMERATED
{
notCUGCall (0),
cUGCall (1)
}
3.28 cUGInterlockCode
This field is used by the network (not by the MS) to identify CUG membership at MOC,
MTC, CFW, and ROAM. The ASN.1 encoding of this field is as follows:
CUG Interlock Code = Network code + CUG interlock
CUGInterlockCode ::= OCTET STRING (SIZE (4))
3.29 cUGOutgoingAccessUsed/ cUGIncomingAccessUsed

This field indicates caller and called whether or not is in the same CUG group.
CUGOutgoingAccessUsed ::= ENUMERATED
{
callInTheSameCUGGroup (0),
callNotInTheSameCUGGroup (1)
}
3.30 causeForTerm
This field contains a generalized reason for the release of the connection including the
following:
Normal release;
CAMEL initiated call release;
Partial record generation;
Partial record call re-establishment;
Unsuccessful call attempt;
Abnormal termination during the stable phase;
Unauthorized network originating a location service request;
Unauthorized client requesting a location service;
Position method failure at a location service execution;
Unknown or unreachable LCS client at a location service request.
A more detailed reason may be found in section 3.35"Diagnostics."

CauseForTerm ::= INTEGER
--- Cause codes from 16 up to 31 are defined in TS 32.015 as 'CauseForRecClosing'
-- (cause for record closing).
-- There is no direct correlation between these two types.
-- LCS related causes belong to the MAP error causes acc. TS 29.002.
-{
normalRelease
(0),
partialRecord
(1),
partialRecordCallReestablishment (2),
unsuccessfulCallAttempt
(3),
stableCallAbnormalTermination (4),
cAMELInitCallRelease
(5),
cAMELCPHCallConfigurationChange (6),
unauthorizedRequestingNetwork (52),
unauthorizedLCSClient
(53),
positionMethodFailure
(54),
unknownOrUnreachableLCSClient (58)
}
3.31 cmnFlag
This field indicates whether the CMN call is invoked.
CmnFlag ::= ENUMERATED
{
notCmnCall (0),
isCmnCall (1)
}
3.32 defaultCallHandling /defaultSMSHandling

This field indicates whether or not a CAMEL encountered default call/SMS handling. This
field shall be present only if default call/SMS handling has been applied. Parameter is defined
in HLR as part of CAMEL subscription information.
DefaultCallHandling ::= ENUMERATED
{
continueCall (0),
releaseCall (1)
}
3.33 destinationNumber
This field contains the destination number in case of SMS MT.
DestinationRoutingAddress
3.34 destinationRoutingAddress
This field contains called party destinationRoutingAddresscalled number modified by
CAMEL flow. The ASN.1 encoding of this field is as follows:
DestinationRoutingAddress
3.35 Diagnostics
This field contains a more detailed technical reason for the release of the connection and may
contain one of the following:
a MAP error from TS 29.002;
a Cause from TS 24.008;
a Cause from TS 29.078;
a Cause from ITU-T Recommendation Q.767;
The diagnostics may also be extended to include manufacturer and network specific
information.
The technical cause value in this field is set as follows, according to the description in the
protocol:
The most significant bit is always set to 1 as an extended bit.
The less significant seven bits are set to the technical cause value defined in the protocol.
For example 24.008 cause
{
unassigned-or-unallocated-number
(0x01),
no-route-to-destination
(0x03),
channel-unacceptable
(0x06),
operator-determined-barring
(0x08),
normal-call-clearing
(0x10),
user-busy
(0x11),
no-user-responding
(0x12),
user-alerting-no-answer
(0x13),
call-rejected
(0x15),
number-changed
(0x16),
pre-emption
(0x19),
non-selected-user-clearing
(0x1a),
destination-out-of-order
(0x1b),
invalid-number-format-incomplete-number (0x1c),
facility-rejected
(0x1d),
response-to-status-enquiry
(0x1e),
normal-unspecified
(0x1f),
no-circuit-channel-available
(0x22),
network-out-of-order
(0x26),
temporary-failure
(0x29),
switching-equipment-congestion
(0x2a),
access-information-discarded
(0x2b),
requested-circuit-channel-not-available (0x2c),
resources-unavailable-unspecified
(0x2f),
quality-of-service-unavailable
(0x31),
requested-facility-not-subscribed
(0x32),
incoming-calls-barred-within-the-cug
(0x37),
bearer-capability-not-authorized
(0x39),
bearer-capability-not-presently-available (0x3a),
service-or-option-not-available-unspecified(0x3f),
bearer-service-not-implemented
(0x41),
acm-equal-to-or-greater-than-acmmax
(0x44),
requested-facility-not-implemented
(0x45),
only-restricted-digital-information-bearer-capability-is-available(0x46),
service-or-option-not-implemented-unspecified (0x4f),
invalid-transaction-identifier-value
(0x51),
user-not-member-of-cug
(0x57),
incompatible-destination
(0x58),
invalid-transit-network-selection
(0x5b),
semantically-incorrect-message
(0x5f),
invalid-mandatory-information
(0x60),
message-type-non-existent-or-not-implemented
(0x61),
message-type-not-compatible-with-protocol-state (0x62),
information-element-non-existent-or-not-implemented (0x63),
conditional-ie-error
(0x64),
message-not-compatible-with-protocol-state
(0x65),
recovery-on-timer-expiry
(0x66),
protocol-error-unspecified
(0x6f),
interworking-unspecified
(0x7f)
}

Diagnostics
{
gsm0408Cause
::= CHOICE
[0] INTEGER,
-- See TS 24.008
gsm0902MapErrorValue
[1] INTEGER,
-- Note: The value to be stored here corresponds to
-- the local values defined in the MAP-Errors and
-- MAP-DialogueInformation modules, for full details
-- see TS 29.002.
ccittQ767Cause
[2] INTEGER,
-- See ITU-T Q.767
networkSpecificCause
[3] ManagementExtension,
-- To be defined by network operator
manufacturerSpecificCause [4] ManagementExtension
-- To be defined by manufacturer
}
3.36 disconnectParty
This field indicates the disconnect party in the CDR. The ASN.1 encoding of this field is as
follows:
Disconnectparty ::= ENUMERATED
{
unknown (0),
callingPartyRelease (1),
calledPartyRelease (2),
networkRelease (3)
}
3.37 eaSubscriberInfo
This field indicates the calling subscribers information of Equal Access. The ASN.1 encoding
EASubscriberInfo ::= OCTET STRING (SIZE (3))
-- The internal structure is defined by the Carrier Identification
-- parameter in ANSI T1.113.3. Carrier codes between "000" and "999"
-- may be encoded as 3 digits using "000" to "999" or as 4 digits
-- using "0000" to "0999". Carrier codes between "1000" and "9999" are
-- encoded using 4 digits.
3.38 eCategory
This field indicates the enhanced subscriber category. The ASN.1 encoding of this field is as
follows:
ECategory
::= INTEGER (0..255)
3.39 emsDigits
This field only applies to location for an emergency services call in North America and gives
the North American Emergency Services Routing Digits as defined in 3PGPP TS 29.002. The
emsDigits
::= ISDN-AddressString,
3.40 emsKey
This field only applies to location for an emergency services call in North America and gives
the North American Emergency Services Routing Key as defined in 3GPP TS 29.002. The
emsKey ::= ISDN-AddressString,
3.41 equipmentId
This field contains a local identifier used to distinguish between equipment of the same
equipment type e.g. the number of the conference circuit employed if more than one is
available. The ASN.1 encoding of this field is as follows:
EquipmentId ::= INTEGER
3.42 equipmentType
This field contains the type of common equipment employed e.g. conference circuit for multiparty service. The ASN.1 encoding of this field is as follows:
EquipmentType
::= INTEGER
{
conferenceBridge (0)
}
3.43 eventTimeStamps
eventTimeStamps contain the event time stamps relevant for various record types. Usually,
these fields can be setupTime, seizureTime, alertingTime, answerTime, releaseTime,
originationTime, deliveryTime, ssActionTime, interrogationTime, and eventTime. These
fields contain the event time stamps relevant to each of the individual record types. The call
records may contain five significant call handling time stamps:
The time at which the setup (or IAM) was received
(Setup time).
The time at which the resource in question was seized (Seizure time).
The time at which the call was alerting (Alerting time).
The time at which the call was answered or at which charging commences (Answer
time).
The time at which the resource was released (Release time).
For both Mobile Originated and Mobile Terminated calls, the Setup time is the time at which
the setup (or IAM) message from calling side is received.
For both Mobile Originated and Mobile Terminated calls, the Seizure time is the time at
which the traffic channel is allocated i.e. the time at which the ASSIGN COMMAND
message is sent to the MS.

For both Mobile Originated and Mobile Terminated calls, the Alerting time is the time at
which the alerting (or ACM) message from called side is received.
For successful calls, the Answer time is mandatory and both the Seizure and Release times are
optional. The call duration recorded is the chargeable duration i.e. the difference between the
Answer and Release time stamps.
For Mobile Originated calls the Answer time is the time at which the CONNECT message is
sent to the calling party. For Mobile Terminated calls the time at which the CONNECT
message is received from the called party. In case of call re-establishment the answer time is
the time at which the new traffic channel is allocated by the MSC i.e. when the ASSIGN
COMMAND is sent to the MS.
The Release time is the time at which the connection is released by either party i.e. a
DISCONNECT or RELEASE is sent by the network or a DISCONNECT is received from the
MS. In the case of a radio link failure, the release time is the time at which the failure was
detected by the MSC.
The event records include the following time stamps:
HLR-int time: The receipt of a MAP_SEND_ROUTING_INFO request by the HLR.
The receipt of a MAP_UPDATE_LOCATION_AREA request by the VLR or the receipt

of a MAP_UPDATE_LOCATION request by the HLR.
SS-Action: The receipt of a supplementary service request by the VLR. e.g.

MAP_REGISTER_SS, MAP_INVOKE_SS
SMS-MO: The receipt of an RP_DATA message from the MS containing an

SMS_SUBMIT PDU.
SMS-MT: The transmission of an RP_DATA message to the MS containing an

SMS_DELIVER PDU.
All time-stamps include a minimum of date, hour, minute and second.

For the ASN.1 encoding of this field, see section 3.6"bCategory."
3.44 firstmccmnc/intermediatemccmnc/lastmccmnc
The MCC and MNC represent country code and mobile network code. For specific MCCs and
MNCs, refer to the 3GPP TS 24.008. For example, the country code of China is 460, and the
MNC of China Mobile is 00.
MCCMNC ::= OCTET STRING(SIZE(3))
-- This type contains the mobile country code (MCC) and the mobile
-- network code (MNC) of a PLMN.
3.45 fnur
This field indicates the user data rate applied for the connection in the fixed network. In
UMTS, it shall be present for all bearer services as specified in TS 22.002. In GSM, this
parameter is part of the HSCSD connection parameters.

Fnur
::= ENUMERATED
{
-fnurNotApplicable
(0),
fnur9600-BitsPerSecond (1),
fnur14400BitsPerSecond (2),
fnur31200BitsPerSecond (11)
}
3.46 freeFormatData
This field contains charging information sent by the gsmSCF in the Furnish Charging
Information (FCI) messages as defined in TS 29.078. The data can be sent either in one FCI
message or several FCI messages with append indicator. This data is transferred transparently
in the CAMEL clauses of the relevant call records. 'Free format data' sent to the legID=1 is
always stored in the top level of the respective record. 'Free format data' sent to the legID >1
is stored in the appropriate CAMEL call leg information field.
If the FCI is received more then once during one continuing incoming/outgoing CAMEL call
leg, the append indicator defines whether the FCI information is appended to previous FCI
and stored in the relevant record or the information of the last FCI received is stored in the
relevant record (the previous FCI information shall be overwritten).
In the event of partial output the currently valid 'Free format data' is stored in the partial
record.
FreeFormatData ::= OCTET STRING (SIZE(1..160))
3.47 freeFormatDataAppend
This field contains an indicator whether free format data is to be appended to free format data
stored in previous partial CDR. This field is needed in CDR post-processing to sort out valid
free format data for that call leg from sequence of partial records. Creation of partial records
is independent on received FCIs and thus valid free format data may be divided to different
partial records.
If field is missing then free format data in this CDR replaces all received free format data in
previous CDRs. Append indicator is not needed in the first partial record. In following partial
records indicator shall get value true if all FCIs received during that partial record have
append indicator. If one or more of the received FCIs for that call leg during the partial record
do not have append indicator then this field shall be missing.

::= BOOLEAN,
3.48 globalAreaID / changeOfglobalAreaID

This field contains the GCGI in the GSM. This field is SAI for the WCDMA system. For
details, refer to the 3GPP TS 24.008.
The ASN.1 encoding of globalAreaID is as follows:
Indicates GCI of GSM or SAI of WCDMA
GAI
::= OCTET STRING(SIZE(7))
--such as 64 F0 00 00 ABCD 1234
The ASN.1 encoding of changeOfglobalAreaID is as follows:

A list of changes in GCI / SAI each time-stamped.
ChangeOfglobalAreaID
::= SEQUENCE
{
location
[0] GAI,
changeTime
[1] TimeStamp
}
3.49 guaranteedBitRate
This field contains the Guaranteed Bit Rate based on the FNUR for transparent and Wanted
AIUR for non-transparent CS data services based on the described mapping in TS 27.001 or
AMR speech. The bit-rate of the UMTS bearer service shall guarantee to the user or
applications refer 3GPP TS 22.002.
GuaranteedBitRate
::= ENUMERATED
{
gBR14400BitsPerSecond (1), -- BS20 non-transparent
gBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
-- BS30 transparent and multimedia
gBR32000BitsPerSecond (3), -- BS30 multimedia
gBR33600BitsPerSecond (4), -- BS30 multimedia
gBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
gBR57600BitsPerSecond (6), -- BS20 non-transparent
gBR64000BitsPerSecond (7), -- BS30 transparent and multimedia
gBR12200BitsPerSecond (106), -- AMR speech

gBR6600BitsPerSecond (118) -- AMR speech
}
3.50 gsm-SCFAddress
This field indicates the CAMEL server that serves the subscriber. Address is defined in HLR
as part of CAMEL subscription information.
Gsm-SCFAddress
::= ISDNAddressString
3.51 groupCallType
This field indicates the type of a group call.
TCallType ::= ENUMERATED
{
NORMAL_CALL_TYPE(0),
VGCS_CALL_TYPE(1),
VBS_CALL_TYPE(2)
}
3.52 groupCallReference
This field is the Reference No. of a group call, it is composed of decimal numerals and is a
number of four bytes in inversed BCD system.
GroupCallReference
3.53 hLC
This field contains the comprehensive contents of the high layer compatibility (hLC). For
details, refer to ITU-T Q.931.
HLC
::= OCTET STRING
3.54 hotbillingTag
This field indicates whether a user is a hotblling subscriber.
HotBillingTag
::= INTEGER
3.55 interrogationResult
This field indicates the result of the interrogation on the routing from the MSC/VLR to the
HLR. For details, refer to 3GPP TS 29.002. This field is provided only when the query fails.
HLRIntResult
::= Diagnostics
3.56 imeiCheckEvent
This field indicates the type of event that causes the IMEI check to take place.
Mobile originating call attempt
Mobile terminating call attempt
Mobile originating SMS
Mobile terminating SMS
Supplementary service actions performed by the subscriber
Location update

IMEICheckEvent
::= INTEGER
{
mobileOriginatedCall (0),
mobileTerminatedCall (1),
smsMobileOriginating (2),
smsMobileTerminating (3),
ssAction
(4),
locationUpdate
(5)
}
3.57 imeiStatus
This field contains the result of the IMEI checking procedure: Greylisted, Blacklisted, Nonwhitelisted.
IMEIStatus
::= ENUMERATED
{
greyListedMobileEquipment (0),
blackListedMobileEquipment (1),
nonWhiteListedMobileEquipment (2)
}
3.58 initialCallAttemptFlag
This field indicates whether a call is originated from the GsmSCF.
initialCallAttemptFlag
::= NULL,
3.59 interactionWithIP
This field indicates whether to play announcement to the subscriber and to start charging in
the case that the SSP interacts with the GsmSCF.
InteractionWithIP
::= NULL
3.60 iSDN-BC
This field contains the comprehensive contents of the bearer capability (BC). For details, refer
to ITU-T Q.931.
ISDN-BC ::= OCTET STRING
3.61 lcsCause
This field provides the reason for an unsuccessful location request. For details, refer to3GPP
TS 49.031.
LCSCause ::= OCTET STRING (SIZE(1))
3.62 lcsClientIdentity
This field contains further information on the LCS Client identity:
Client External ID.
Client Dialed by MS ID.
Client Internal ID.

LCSClientIdentity
::= SEQUENCE
{
lcsClientExternalID
lcsClientDialedByMS
lcsClientInternalID
[0] LCSClientExternalID
[1] AddressString
[2] LCSClientInternalID
OPTIONAL,
OPTIONAL,
OPTIONAL
}
LCSClientExternalID ::= SEQUENCE
{
externalAddress
[0] AddressString
OPTIONAL
-- extensionContainer [1] ExtensionContainer
OPTIONAL
}
LCSClientInternalID ::= ENUMERATED
{
broadcastService
(0),
o-andM-HPLMN
(1),
o-andM-VPLMN
(2),
anonymousLocation
(3),
targetMSsubscribedService (4)
}
3.63 lcsClientType
This field contains the type of the LCS Client as defined in TS 29.002.
LCSClientType ::= ENUMERATED
{
emergencyServices
(0),
valueAddedServices
(1),
plmnOperatorServices
(2),
lawfulInterceptServices (3)
}
3.64 lcsPriority
This field indicates the priority of the location request as defined in TS 49.031.
LCS-Priority ::= OCTET STRING (SIZE (1))
-- 0 = highest priority
-- 1 = normal priority -- all other values treated as 1
3.65 lcsQos
This field indicates the Quality of Service (QoS) for a location request as defined in TS
49.031.
LCSQoSInfo ::= SEQUENCE

{
horizontal-accuracy
verticalCoordinateRequest
vertical-accuracy
responseTime
}
[0]
[1]
[2]
[3]
Horizontal-Accuracy
NULL
Vertical-Accuracy
ResponseTime
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
3.66 levelOfCAMELService
This field briefly describes the complexity of CAMEL invocation.
Basic indicates that CAMEL feature is invoked during the setup phase (e.g. to modify
the destination) of the call only.
Online charging indicates that CAMEL supported AoC parameter were sent to the
mobile station (the Send Charging Information message, SCI, is received from the
gsmSCF).
Call duration supervision is set whenever the call duration supervision is applied in the
gsmSSF of the VPLMN (apply charging message is received from the gsmSCF).

LevelOfCAMELService
::= BIT STRING
{
basic
(0),
callDurationSupervision (1),
onlineCharging
(2),
callPartyHandling
(3)
}
3.67 lLC
This field contains the comprehensive contents of the low layer compatibility (lLC). For
details, refer to ITU-T Q.931.
LLC
::= OCTET STRING
3.68 location / changeOfLocation

This field comprises two parts, the location area code (LAC) and the (CI).
The location field contains a combination of the Location Area Code (LAC) and Cell
Identity (CI) of the cell in which the served party is currently located. Any change of
location may be recorded in the change of location field along with the time at which the
change took place.
The change of location field is optional and it is not required if partial records are
generated when the location changes.
The LAC and CI are both 2 octet quantities coded according to TS 24.008.

LocationAreaAndCell
::= SEQUENCE
{
locationAreaCode [0] LocationAreaCode,
cellIdentifier
[1] CellId
--- For 2G the content of the Cell Identifier is defined by the Cell Id
-- refer TS 24.008 and for 3G by the Service Area Code refer TS 25.413.
-}
LocationAreaCode
CellId ::= OCTET STRING (SIZE(2))

--- Coded according to TS 24.008
--
3.69 locationEstimate
This field indicates an estimate of a geographic location of a target MS according to TS
29.002.
LocationEstimateType ::= ENUMERATED
{
currentLocation
(0),
currentOrLastKnownLocation (1),
initialLocation
(2),
activateDeferredLocation
(3),
cancelDeferredLocation
(4)
}
-- exception handling:
-- a ProvideSubscriberLocation-Arg containing an unrecognized
LocationEstimateType
-- shall be rejected by the receiver with a return error cause of unexpected data
value
3.70 locationType
This field contains the type of the location as defined in TS 29.002.
LocationType ::= SEQUENCE
{
locationEstimateType
[0] LocationEstimateType,
deferredLocationEventType [1] DeferredLocationEventType
}
OPTIONAL
3.71 maximumBitRate
This field contains the Maximum Bit Rate based on the Fixed Network User Rate (FNUR) for
transparent and Wanted Air Interface User Rate (WAIUR) for non-transparent CS data
services based on the described mapping in TS 27.001. Or this field contains the Maximum
Bit Rate of the AMR for voice services. For details, refer to 3GPP TS 27.001.
MaximumBitRate
::= ENUMERATED
{
mBR14400BitsPerSecond (1), -- BS20 non-transparent
mBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
-- BS30 transparent and multimedia
mBR32000BitsPerSecond (3), -- BS30 multimedia
mBR33600BitsPerSecond (4), -- BS30 multimedia
mBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
mBR57600BitsPerSecond (6), -- BS20 non-transparent
mBR64000BitsPerSecond (7), -- BS30 transparent and multimedia
mBR12200BitsPerSecond
(106),
(107),
(108),
(109),
(110),
(111),
(112),
(113),
(114),
(115),
(116),
(117),
(118)
--------------
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
speech
speech
speech
speech
speech
speech
speech
speech
speech
speech
speech
speech
speech
3.72 maximumNumberOfSMSInTheConcatenatedSMS
This field indicates the maximum number of SMS in the concatenated SMS.
MaximumNumberOfSMSInTheConcatenatedSMS
::= INTEGER(0..255)
3.73 MCTType
This field indicates the MCT type of an MOC for which the malicious call trace (MCT)
application is implemented.
MCTType
{
::=
ENUMERATED
MCTI
MCTC
(0),
(1)
3.74 measureDuration
This field contains the duration for the section of the location measurement corresponding to
the location request and the location report messages.
Measure Duration
::= INTEGER
--- The call duration in seconds.
-- For successful calls this is the chargeable duration.
-- For call attempts this is the call holding time.
--
3.75 messageReference
This field contains a unique message reference number allocated by the MS when transmitting
a short message to the service center. This field corresponds to the TP-Message-Reference
element of the SMS_SUBMIT PDU defined in 3GPP TS 23.040.
MessageReference
::= OCTET STRING(size(1))
3.76 mlc-Number
This field quotes an ISDN (E.164) number of a mobile location center (MLC).
mlc-Number ISDN-AddressString
3.77 msClassmark / changeOfClassmark

This field contains the mobile station classmark employed by the served MS on call set-up as
defined in 3GPP TS 24.008 (excerpt from 3GPP TS 24.008 as follows). Any alteration in the
classmark during the connection may be recorded in the change of classmark field and will
include the time at which the change took place.
Classmark
::= OCTET STRING(size(3))
--- See Mobile station classmark 2 or 3 TS 24.008
--
3.78 modemType
This field indicates the type of the modem applied by the terminal from the network when
implementing the data service.
ModemType
::= ENUMERATED
{
none-modem
(0),
modem-v21
(1),
modem-v22
(2),
modem-v22-bis
(3),
modem-v23
(4),
modem-v26-ter
(5),
modem-v32
(6),
modem-undef-interface (7),
modem-autobauding1
(8),
no-other-modem-type
(31),
modem-v34
(33)
}
3.79 molr-Type
This field quotes the type of MO-LR invoked as defined in3GPP TS 24.080.
MOLR-Type
--0
--1
--2
::= INTEGER
locationEstimate
assistanceData
deCipheringKeys
3.80 mSCAddress
This field contains the ITU-T Recommendation E.164 number assigned to the MSC.
MSCAddress
::= AddressString
3.81 mscIncomingCircuit / mscOutgoingCircuit

This field contains the trunk circuit assigned by the MSC to the call.
MSCCIC
::= INTEGER(0..65535)
Circuit Identity Code 1 will be coded as 01 00
3.82 mscIncomingROUTE / mscOutgoingROUTE

This field contains the incoming route and outgoing route described as following:
The incoming route / outgoing route describes the trunk group name or trunk group ID on
which the call comes from / routes to. For mobile originated/terminated calls this will
generally be a BSS trunk or RNS route.
ROUTE
::=
CHOICE
{
rOUTENumber
[0] INTEGER,
rOUTEName
[1] GraphicString
}
3.83 mscIncomingRouteAttribute /
This field indicates the attribute of the incoming/outgoing route.
RouteAttribute
::=
{
cas
(0),
tup
(1),
isup
(2),
pra
(3),
bicc
(4),
sip
(5),
others (255)
}
ENUMERATED
3.84 mscServerIndication
This field indicates whether the VT-CSI is activated in the VMSC, and it also indicates
whether the TCAEML record is generated in the terminating office.
mscServerIndication
::= BOOLEAN,
3.85 networkCallReference
This field is used to correlate call records from the originating MSC (when applicable), the
GMSC, and the terminating MSC. As an optional function, it can also be used to correlate call
records from the gsmSCF.
NetworkCallReference
::= CallReferenceNumber
3.86 networkOperatorId
When the carriers use independent RAN and shared CN, this field is used to indicate the
carrier for which the current record is generated so that the carrier can read the records
correctly from the corresponding channels.
NetworkOperatorId
3.87 notificationToMSUser
This field contains the applicable privacy notification to an MS user when the LR is invoked.
For details, refer to TS 29.002.
NotificationToMSUser ::= ENUMERATED
{
notifyLocationAllowed
(0),
notifyAndVerify-LocationAllowedIfNoResponse (1),
notifyAndVerify-LocationNotAllowedIfNoResponse (2),
locationNotAllowed
(3)
}
3.88 numberOfDPEncountered
This field indicates the number of service triggering points and even detection points detected
during a CAMEL service.
::= INTEGER,
3.89 numberOfForwarding
This field, if provided through the ISUP signaling, contains the number of times a call has
been forwarded prior to the interrogation of the HLR as defined in TS 29.002.
NumberOfForwarding ::= INTEGER (1..5)
3.90 originalCalledNumber
This field indicates the address of original called party in case of call forwarding.
OriginalCalledNumber
3.91 origination
This field contains the originating short message subscriber number.
TimeStamp
3.92 orgMSCId
This field indicates the originating and terminating MSC SPC of an SMS.
MSCId
--National network format , octet order is the same as ISUP signaling
--if spc is coded as 14bit, then OCTET STRING1 will filled with 00,,for example
rnc id = 123 will be coded as 00 01 23
--OCTET STRING1
--OCTET STRING2
--OCTET STRING3
3.93 orgRNCorBSCId
This field contains the originating RNC or BSC SPC.
RNCorBSCId
--octet order is the same as RANAP/BSSAP signaling
--if spc is coded as 14bit, then OCTET STRING1 will filled with 00 ,for example
rnc id = 123 will be coded as 00 01 23
--OCTET STRING1
--OCTET STRING2
--OCTET STRING3
3.94 partialRecordType
This field indicates the type of a partial record.
PartialRecordType
::= ENUMERATED
{
timeLimit
(0),
serviceChange
(1),
locationChange
(2),
classmarkChange
(3),
aocParmChange
(4),
radioChannelChange
(5),
hSCSDParmChange
(6),
changeOfCAMELDestination
(7),
firstHotBill
severalSSOperationBill
iSTalertTimeOut
bearRedirectStart
bearRedirectStop
(20),
(21),
(22),
(23),
(24)
3.95 partyRelCause
Indicates the cause of call release. The field includes two sub-fields: release type and release
cause. When the release type is bssmap or ranap, the call release is caused by the wireless
side.
PartyRelCause ::= SEQUENCE
{
releaseParty [0]
ReleaseParty,
releaseCause [1]
INTEGER
}
ReleaseParty ::= ENUMERATED
{
bssmap
(0),
ranap
(1),
dtap
(2),
isup
(3),
relbutt (255)
}
3.96 portedflag
This field indicates whether the served party uses the number ported service.
PortedFlag
::=
{
numberNotPorted
numberPorted
}
ENUMERATED
(0),
(1)
3.97 positioningData
This field provides the positioning data associated with a location attempt for a target MS
according TS 49.031.
PositioningData
3.98 privacyOverride
This field indicates whether the MS privacy is overridden by the LCS client when the GMLC
and VMSC/SGSN for an MT-LR are in the same country as defined in TS 29.002.
privacyOverride
::=
NULL,
3.99 radioChanRequested/ radioChanUsed /

changeOfRadioChan
This field contains three parts as the radio channel requested, radio channel used and the
change of radio channel.
The radio channel requested field contains the type of channel requested by the user. The
following values are permitted:
Full rate
Half rate
Dual mode half rate preferred
Dual mode full rate preferred

RadioChanRequested
::= ENUMERATED
{
-halfRateChannel
(0),
fullRateChannel
(1),
dualHalfRatePreferred
(2),
dualFullRatePreferred
(3)
The radio channel used field indicates the type of the traffic channel actually employed
for the connection as described in GSM 05.01. The following values are permitted:
Full rate
Half rate

TrafficChannel
::=
ENUMERATED
{
fullRate
(0),
halfRate
(1)
Any change in the type of channel used may be recorded in the change of radio channel
used field along with the time at which the change occurs and the speech version used
after the change of radio channel.

ChangeOfRadioChannel
::= SEQUENCE
{
radioChannel
[0] TrafficChannel,
changeTime
[1] TimeStamp,
speechVersionUsed
[2] SpeechVersionIdentifier
OPTIONAL
3.100 rateIndication
This field indicates the rate adaptation used for the connection. This field is constructed from
the information in the parameters rate adaption and other rate adaption signaled between
the MS/UE and the network. For details, refer to TS 24.008.
The format of this field is a single octet with the following format:
Bits 0-1: the Rate Adaption field as defined in TS 24.008 ;
Bits 2-3: the Other Rate Adaption field as defined in TS 24.008 ;
Bits 4-7: not used.
RateIndication
--0
no rate adaption
--1
V.110, I.460/X.30
--2
ITU-T X.31 flag stuffing
--3
V.120
--7
H.223 & H.245
--11PIAFS
3.101 recordingEntity
This field contains the entity numbers, in ITU-T E.164 format, of the MSC, VLR, and HLR
that generate records. For details, refer to 3GPP TS 23.003.
RecordingEntity
::= AddressString
3.102 recordExtensions
This field enables network operators and/ or manufacturers to add their own extensions to the
standard record definitions. This field contains a set of management extensions defined in
ITU-T X.721.
ManagementExtensions
::= SET OF ManagementExtension
ManagementExtension ::= SEQUENCE

{
identifier
OBJECT IDENTIFIER,
significance
information
[1] BOOLEAN DEFAULT FALSE,

[2] OCTET STRING
3.103 recordNumber
This field is used to record the record numbers of CDRs. The record number is incremented
by 1 after each CDR is generated.
RecordNumber
::=
INTEGER
3.104 recordType
The field indicates the type of the record e.g. mobile originated, mobile terminated, call
forwarding, etc.
CallEventRecordType
{
moCallRecord
mtCallRecord
roamingRecord
incGatewayRecord
outGatewayRecord
transitCallRecord
moSMSRecord
mtSMSRecord
ssActionRecord
hlrIntRecord
commonEquipRecord
moTraceRecord
mtTraceRecord
termCAMELRecord
mtLCSRecord
moLCSRecord
niLCSRecord
forwardCallRecord
}
::= INTEGER
(0),
(1),
(2),
(3),
(4),
(5),
(6),
(7),
(10),
(11),
(14),
(15),
(16),
(17),
(23),
(24),
(25),
(100)
3.105 redirectingnumber
This field contains the number of the forwarding party.
RedirectingNumber
3.106 redirectingcounter
This field indicates the forwarding times.
RedirectingCounter
::= INTEGER
3.107 resourceChargeIPnumber
In the case of interaction between SSP and IP, this field indicates the number of the equipment
that plays the announcement to the subscriber under the control of the GsmSCF.
ResourceCharge IP number
::= AddressString
3.108 Roaming number

This field contains the MS roaming number as defined in 3GPP TS 23.003 and coded
according to 3GPP TS 29.002.
RoamingNumber
::= ISDN-AddressString
3.109 routingNumber
The routing number field of the HLR interrogation record contains either an MS roaming
number or, in case of call forwarding, a forwarded-to number.
RoutingNumber
{
roaming
forwarded
}
::= CHOICE
[1] RoamingNumber,
[2] ForwardToNumber
3.110 sequenceNumber
This field contains a dynamic sequence number employed to link the partial records generated
for a particular connection. The record is generated for the first part of a call, and it begins
with 1.
SequenceNumber
::=
INTEGER
3.111 servedIMEI
This field contains the international mobile equipment identity (IMEI) of the equipment
served. The term served equipment refers to calling MS in the record generated for the calling
party and called MS in the record generated for the called MS. The structure of the IMEI is
defined in 3GPP TS 23.003. Figure 1.1 shows the structure of the IMEI.
Figure 1.1 Structure of the IMEI
8 digits
6 digits
1 digits
TAC
SNR
spare
IMEI 15 digits
The IMEI is composed of the following elements (each element shall consist of decimal digits
only):
Type Allocation Code (TAC): It is a string of six digits used to identify the manufacturer
and type of the terminal.
Facility Allocation Code (FAC): It is used to identify the manufacturing and packing
locations of the terminal.
Serial Number (SNR): It is an individual serial number uniquely identifies the terminal
when the TAC and FAC of the terminal are provided.
Spare digit: This field is permanently set to 0.
The structure of the IMEISV which is the combination of the IMEI and the SVN is shown in
the following figure:
8 digits
6 digits
2 digits
TAC
SNR
SVN
IMEI 16 digits
The difference between the IMEISV and the IMEI is the software version number (SVN)
which indicates the software version information of the currently used terminal. Besides, there
is no spare digit in the IMEISV.
IMEI ::= TBCD-STRING (SIZE (8))
3.112 servedIMSI/calledIMSI
This field contains the international mobile subscriber identity (IMSI) of the served party. The
term "served" party is used to describe the mobile subscriber involved in the transaction
recorded e.g. the calling subscriber in case of an MOC record.
Figure 1.1 shows the structure of the IMSI defined in 3GPP TS 23.003.
Figure 1.1 Structure of the IMSI
Not more than 15
3
2 or 3
MC
MN
MSI
NMS
IMSI
IMSI is composed of three parts:
Mobile Country Code (MCC): The MCC identifies uniquely the country of domicile of
the mobile subscriber;
Mobile Network Code (MNC): The MNC identifies the home PLMN of the mobile
subscriber;
Mobile Subscriber Identification Number (MSIN): It identifies uniquely the mobile

subscriber within a PLMN.

IMSI ::= TBCD-STRING (SIZE (3..8))
-- digits of MCC, MNC, MSIN are concatenated in this order.
3.113 servedMSISDN
This field contains the MS ISDN number (MSISDN) of the served party. The term "served
party" is used to describe the mobile subscriber involved in the transaction recorded, for
example, the called party in an MTC. The structure of the MSISDN is defined in 3GPP
TS 23.003. Figure 1.1 shows the structure of the MSISDN defined in 3GPP TS 23.003.
Figure 1.1 Structure of the MSISDN
CC
NDC
SN
National(significant)
mobile number
Mobile station international
ISDN number
The MSISDN is composed of two parts:
Country Code (CC): It identifies the country in which the MS is registered.
National Destination Code (NDC): It identifies the mobile access number.
Subscriber Number (SN): It identifies the number of the mobile subscriber.

MSISDN
::= ISDN-AddressString
3.114 serviceCentre
This field contains a ITU-T Recommendation E.164 number identifying a particular service
center e.g. short message service centre (see TS 23.040).
serviceCentre
AddressString
3.115 serviceKey
This field identifies the CAMEL service logic applied. Service key is defined in HLR as part
of CAMEL subscription information.
ServiceKey ::= INTEGER (0..2147483647)
3.116 smsResult
This field contains the result of an attempt to deliver a short message. For details, refer to
3GPP TS 29.002.
SMSResult
::= Diagnostics
3.117 speechVersionSupported/speechVersionUsed
The field speechVersionSupported/speechVersionUsed consists two parts as follows. The
speech version supported field contains the speech version supported by the MS with the
highest priority. The speech version used field contains the speech codec version assigned for
that call. The coding is according to 3GPP TS 08.08, and the extension bit 8 is set to 0.
It should be noted that the change of radio channel field is optional and not required if partial
records are generated.
SpeechVersionIdentifier
-- see GSM 08.08
-- 000 0001 GSM speech

full
full
full
half
half
half
rate
rate
rate
rate
rate
rate
version
version
version
version
version
version
1
2
3
1
2
3
used for enhanced full rate

for future use
for future use
for future use
3.118 systemType
This field indicates whether the current air interface used is GERAN or UTRAN (or a value
of unknown).
SystemType ::= ENUMERATED
{
unknown
(0),
iuUTRAN
(1),
gERAN
(2)
3.119 supplServiceUsed/supplService
This field contains the code of the supplementary service on which the action was
performed.For details on the coding of the supplementary service code, refer to TS 29.002.
SS-Code ::= OCTET STRING (SIZE (1))
-- supplementary service, a group of supplementary services, or
-- all supplementary services. The services and abbreviations
-- used are defined in TS 3GPP TS 22.004. The internal structure is
-- defined as follows:
--- bits 87654321: group (bits 8765), and specific service
-- (bits 4321) USSD = ff
------------------------
allSS
(0x00),
reserved for possible future use
all SS
allLineIdentificationSS
all line identification SS
(0x10),
calling-line-identification-presentation
calling line identification presentation
calling-line-identification-restriction
calling line identification restriction
connected-line-identification-presentation
connected line identification presentation
connected-line-identification-restriction
connected line identification restriction
malicious-call-identification
malicious call identification
(0x11),
allNameIdentificationSS
all name identification SS
calling-name-presentation
(0x18),
(0x12),
(0x13),
(0x14),
(0x15),
(0x19),
--------------------------------------------------------
calling name presentation

SS-Codes '00011010'B, to '00011111'B, are reserved for future
NameIdentification Supplementary Service use.
allForwardingSS
(0x20),
all forwarding SS
call-forwarding-unconditional
(0x21),
call forwarding unconditional
call-deflection
(0x24),
call deflection
allCondForwardingSS
(0x28),
all conditional forwarding SS
call-forwarding-on-mobile-subscriber-busy
(0x29),
call forwarding on mobile subscriber busy
call-forwarding-on-no-reply
(0x2a),
call forwarding on no reply
call-forwarding-on-mobile-subscriber-not-reachable (0x2b),
call forwarding on mobile subscriber not reachable
allCallOfferingSS
(0x30),
all call offering SS includes also all forwarding SS
explicit-call-transfer
explicit call transfer
mobile-access-hunting
mobile access hunting
(0x31),
allCallCompletionSS
all Call completion SS
(0x40),
(0x32),
call-waiting
(0x41),
call waiting
call-hold
(0x42),
call hold
completion-of-call-to-busy-subscribers-originating-side
(0x43),
completion of call to busy subscribers, originating side
completion-of-call-to-busy-subscribers-destination-side
(0x44),
completion of call to busy subscribers, destination side
this SS-Code is used only in InsertSubscriberData and DeleteSubscriberData
multicall
multicall
(0x45),
allMultiPartySS
all multiparty SS
(0x50),
multiPTY
multiparty
(0x51),
allCommunityOfInterest-SS
(0x60),
-reserved for possible future use

-all community of interest SS
-- closed-user-group
(0x61),
-closed user group
--- allChargingSS
(0x70),
-all charging SS
-- advice-of-charge-information
(0x71),
-advice of charge information
-- advice-of-charge-charging
(0x72),
-advice of charge charging
--- allAdditionalInfoTransferSS
(0x80),
-all additional information transfer SS
-- uUS1-user-to-user-signalling
(0x81),
-UUS1 user-to-user signalling
(0x82),
(0x83),
--- allBarringSS
(0x90),
-all barring SS
-- barringOfOutgoingCalls
(0x91),
-barring of outgoing calls
-- barring-of-all-outgoing-calls
(0x92),
-barring of all outgoing calls
-- barring-of-outgoing-international-calls
(0x93),
-barring of outgoing international calls
-- boicExHC
(0x94),
-barring of outgoing international calls except those directed
-to the home PLMN
-- barringOfIncomingCalls
(0x99),
-barring of incoming calls
-- barring-of-all-incoming-calls
(0x9a),
-barring of all incoming calls
-- barring-of-incoming-calls-when-roaming-outside-home-PLMN-Country
(0x9b),
-barring of incoming calls when roaming outside home PLMN
-Country
--- allCallPrioritySS
(0xa0),
-all call priority SS
-- enhanced-Multilevel-Precedence-Pre-emption-EMLPP-service
-enhanced Multilevel Precedence Pre-emption 'EMLPP) service
--- allLCSPrivacyException
(0xb0),
-all LCS Privacy Exception Classes
-- universal
(0xb1),
-allow location by any LCS client
-- callrelated
(0xb2),
-allow location by any value added LCS client to which a call
(0xa1),
---------------------------------
is established from the target MS

callunrelated
(0xb3),
allow location by designated external value added LCS clients
plmnoperator
(0xb4),
allow location by designated PLMN operator LCS clients
allMOLR-SS
(0xc0),
all Mobile Originating Location Request Classes
basicSelfLocation
(0xc1),
allow an MS to request its own location
autonomousSelfLocation
(0xc2),
allow an MS to perform self location without interaction
with the PLMN for a predetermined period of time
transferToThirdParty
(0xc3),
allow an MS to request transfer of its location to another LCS client
allPLMN-specificSS
plmn-specificSS-1
plmn-specificSS-2
plmn-specificSS-3
plmn-specificSS-4
plmn-specificSS-5
plmn-specificSS-6
plmn-specificSS-7
plmn-specificSS-8
plmn-specificSS-9
plmn-specificSS-A
plmn-specificSS-B
plmn-specificSS-C
plmn-specificSS-D
plmn-specificSS-E
USSD
(0xf0),
(0xf1),
(0xf2),
(0xf3),
(0xf4),
(0xf5),
(0xf6),
(0xf7),
(0xf8),
(0xf9),
(0xfa),
(0xfb),
(0xfc),
(0xfd),
(0xfe),
(0xff)
3.120 ssAction
This field contains the type of supplementary service action requested by the subscriber or
performed by the network.
SSActionType
::= ENUMERATED
{
registration
(0),
erasure
(1),
activation
(2),
deactivation
(3),
interrogation
(4),
invocation
(5),
passwordRegistration (6),
USSDInvocation
(7)
}
-- USSDInvocation
(7) include USSD phase 1,phase 2
3.121 ssActionResult
This field contains the result of an attempted supplementary service action (refer to 3GPP
TS 29.002). Note that this field is only provided if the SS-action is at least partially
unsuccessful.
SSActionResult
::= Diagnostics
3.122 ssParameters
This field contains the parameters associated with a supplementary service action requested
by the subscriber. For further details of the parameters involved see the GSM 02.8n series of
documents.
In the supplementary service record generated for USSD, the corresponding fields are filled
with the following values:
Supplementary service parameters field: USSD
SSActionType: ussdInvocation(7)
Supplementary service code: 0
Basic service code: not be coded into ASN.1
In the supplementary service record generated for call forwarding, the supplementary service
parameters field is filled with the forwarded-to number.
SSParameters
::= CHOICE
{
forwardedToNumber
[0] ForwardToNumber,
unstructuredData
[1] OCTET STRING
3.123 smstext
This field records the contents of the short message when the SMS uses text format.
SMSTEXT
::= OCTET STRING
3.124 smsUserDataType
This field indicates the information on the subscriber type contained in the short message sent.
SmsUserDataType
::= OCTET STRING (SIZE (1))
--00 concatenated-short-messages-8-bit-reference-number
--01 special-sms-message-indication
--02 reserved
--03 Value not used to avoid misinterpretation as <LF>
--04 characterapplication-port-addressing-scheme-8-bit-address
--05 application-port-addressing-scheme-16-bit-address
--06 smsc-control-parameters
--07 udh-source-indicator
--08 concatenated-short-message-16-bit-reference-number
--09 wireless-control-message-protocol
--0A text-formatting
--0B predefined-sound
--0C user-defined-sound-imelody-max-128-bytes
--0D predefined-animation
--0E large-animation-16-16-times-4-32-4-128-bytes
--0F small-animation-8-8-times-4-8-4-32-bytes
--10 large-picture-32-32-128-bytes
--11 small-picture-16-16-32-bytes
--12 variable-picture
--13 User prompt indicator
--14 Extended Object
--15 Reused Extended Object
--16 Compression Control
--17 Object Distribution Indicator
--18 Standard WVG object
--19 Character Size WVG object
--1A Extended Object Data Request Command
--1B-1F Reserved for future EMS features
--20 RFC 822 E-Mail Header
--21 Hyperlink format element
--22 Reply Address Element
--23 - 6F Reserved for future use
--70 - 7F (U)SIM Toolkit Security Headers
--80 - 9F SME to SME specific use
--A0 - BF Reserved for future use
--C0 - DF SC specific use
--E0 - FE Reserved for future use
--FF normal SMS
3.125 selectedCIC
This field indicates the selected code of carrier identification used in the (North American
equal access) NAEA service.
SelectedCIC ::= OCTET STRING (SIZE (3))
3.126 sequenceNumberOfTheCurrentSMS
This field indicates the sequence number of the current short message in the concatenated
short message. It is numbered from 1.

SequenceNumberOfTheCurrentSMS
::= INTEGER(0..255)
3.127 subscriberCategory
This field indicates the type of subscriber. The subscriber category information is stored in the
MSC/VLR after it is inserted into the subscriber data flow by the HLR during the location
update.
SubscriberCategory ::= OCTET STRING (SIZE (1))
-- unknownuser = 00,
-- frenchuser = 01,
-- englishuser = 02,
-- germanuser = 03,
-- russianuser = 04,
-- spanishuser = 05,
-- specialuser = 06,
-- reserveuser = 09,
-- commonuser = 0a,
-- superioruser = 0b,
-- datacalluser = 0c,
-- testcalluser = 0d,
-- spareuser
= 0e,
-- payphoneuser = 0f,
-- coinuser
= 20,
-- isup224
= 0xe0
3.128 tariffCode
This field indicates the tariff code of the cell.
TariffCode
::= INTEGER (0..255)
3.129 transparencyIndicator
This field indicates whether the basic service is employed in transparent or non-transparent
mode. It should also be noted that this field is only relevant to those services which may be
operated in both transparent and non-transparent modes.
TransparencyInd
{
transparent
nonTransparent
::=
(0),
(1)
ENUMERATED
3.130 typeOfSubscribers
This field indicates the roaming type of subscribers. The value all is not available currently.
TypeOfSubscribers
{
home
visiting
all
}
::= ENUMERATED
(0),
(1),
(2)
-- HPLMN subscribers
-- roaming subscribers
3.131 Usertype
This field indicates the type of the user.
UserType ::= ENUMERATED
{
gsmnormaluser
(0),
gsmprepaiduser
(1),
gsmcameluser
(2),
gsmunknowuser
(31)
}
3.132 ussdCodingScheme
This field indicates the coding scheme of USSD in the case of the USSD service.
UssdCodingScheme
::= OCTET STRING
3.133 ussdString
This field indicates the subscriber input in the case of the USSD service.
UssdString
::= OCTET STRING
3.134 ussdNotifyCounter
This field indicates the times of notify procedure in the case of the USSD service.
UssdNotifyCounter
::=
INTEGER(0..255)
3.135 ussdRequestCounter
This field indicates the times of request procedure in the case of the USSD service.
UssdRequestCounter
::=
INTEGER(0..255)
3.136 ussdCallBackFlag
This field indicates whether a USSD call back is originated by a CAMEL subscriber roaming
aboard.
ussdCallBackFlag
::= NULL,
3.137 uuslType
This field indicates the type of the UUS1 supplementary service.
UUS1Type ::=
ENUMERATED
{
UUS1_IMPLICIT(0),
UUS1_EXPLICIT_REQUIRED(1),
UUS1_EXPLICIT_NOT_REQUIRED(2),
UUS1_SS_UNUSED(3)
3.138 voiceIndicator
This field indicates whether to connect the call or to play an announcement to the subscriber.
It also indicates whether the local office or other offices play the announcement to the
subscriber.
VoiceIndicator ::=
ENUMERATED
{
sendToneByLocalMsc(0) ,
sendToneByOtherMsc(1),
voiceNoIndication (3)
}
3.139 zoneCode
This filed indicates the zone code of a cell.

ZoneCode
ASN.1 Description of the CDR File
The ASN.1 (BER) description of the CDR file describes the encoding of CDRs on the iGWB,
which sends the encoded CDRs to the billing center. For detailed ASN.1 description of the
CDR file, refer to Appendix A CDR Encoding/Decoding Description.ASN.
Examples of CDRs
This chapter describes the ANS.1-encoded CDRs of various services, such as voice calls, CSdomain bearer services, VP calls, SMS, HLR interrogation, USSD, supplementary services,
and emergency calls. This chapter describes only the correlation between different CDRs and
their examples. Detailed CDR examples in the ASN.1 encoding format and the text (after
decoding) format are provided in "ASN.1 CDR example" in Appendix B "CDR Examples".
The suffix of an example of a CDR in the ASN.1 encoding format is dat.
The suffix of an example of a CDR in the decoded text format is txt.
Figure 1.21 The correlation between CDRs and examples

Service
Record Name
ASN.1 BER Code Record
Decoded Record
Voice Call
MOC Record
001-ASN.1_MOC.dat
001-ASN.1_MOC.txt
MTC Record
002-ASN.1_MTC.dat
002-ASN.1_MTC.txt
Vp Call
MOC Record
003-ASN.1_MOC.dat
003-ASN.1_MOC.txt
Other bear
service call
MOC Record
004-ASN.1_MOC.dat
004-ASN.1_MOC.txt
Forwarding
record
Forwarding
record
005-ASN.1_CFW.dat
005-ASN.1_CFW.txt
Emergency
record
Emergency call
record
006-ASN.1_MOC.dat
006-ASN.1_MOC.txt
Middle billing
partial record1
007ASN.1_CallRecord(partial1)_
MOC.dat
007-ASN.1_CallRecord(partial1)_MOC.txt
partial record2
MOC.dat
partial record3
MOC.dat
Service
Record Name
Decoded Record
partial record4
MOC.dat
partial record5
MOC.dat
partial record6
MOC.dat
partial record7
MOC.dat
Sms MOC
record
014-ASN.1_SMS_MOC.dat
014-ASN.1_SMS_MOC.txt
Sms MTC
record
015-ASN.1_SMS_MTC.dat
015-ASN.1_SMS_MTC.txt
Concatenated
Long Sms1
016ASN.1_SMS(partial1)_MOC
.dat
016-ASN.1_SMS(partial1)_MOC.txt
Concatenated
Long Sms2
.dat
Concatenated
Long Sms3
.dat
Concatenated
Long Sms4
.dat
Interrogation
Interrogation
record
020-ASN.1_Query_HLR.dat
020-ASN.1_Query_HLR.txt
USSD
USSD record
021ASN.1_SS_Act(USSD).dat
021-ASN.1_SS_Act(USSD).txt
Supplementary
service
Forward
registration
022ASN.1_SS_Act(Forward).da
t
022-ASN.1_SS_Act(Forward).txt
Handover
Handover MOC
record
023ASN.1_Handover_MOC.dat
023-ASN.1_Handover_MOC.txt
CommonEquip
Record
CommonEquip
Record
024-ASN.1_CommEquip.dat
024-ASN.1_CommEquip.txt
IncGatewayRec
ord
IncGateway
Record
025-ASN.1_GWI.dat
025-ASN.1_GWI.txt
Sms
Concatenated
Long Sms
Service
Record Name
Decoded Record
OutGatewayRe
cord
OutGateway
Record
026-ASN.1_GWO.dat
026-ASN.1_GWO.txt
TransitCallRec
ord
TransitCall
Record
027-ASN.1_Transit.dat
027-ASN.1_Transit.txt
RoamingRecor
d
Roaming
Record
028-ASN.1_Roam.dat
028-ASN.1_Roam.txt
Moc(CAMEL)
Moc(CAMEL)
029ASN.1_MOC(Camel).dat
029-ASN.1_MOC(Camel).txt
Mtc(CAMEL)
Mtc(CAMEL)
030ASN.1_MTC(Camel).dat
030-ASN.1_MTC(Camel).txt
TCAMEL
TCAMEL
031-ASN.1_Tcamel.dat
031-ASN.1_Tcamel.txt
Moc(FCI)
Moc(FCI)
032ASN.1_MOC(withFCI).dat
032-ASN.1_MOC(withFCI).txt
Moc(hotbilling)
Moc(hotbilling)
033-ASN.1_MOC(Hot).dat
033-ASN.1_MOC(Hot).txt
SS_PLMN_SP
ECIFICSS1
record
SS_PLMN_SPE
CIFICSS1
record
034ASN.1_SPECIFICSS1_MO
C.dat
034-ASN.1_SPECIFICSS1_MOC.txt
SS_PLMN_SP
ECIFICSS3
record
SS_PLMN_SPE
CIFICSS3
record
035ASN.1_SPECIFICSS3_MO
C.dat
035-ASN.1_SPECIFICSS3_MOC.txt
MO-LCS
MO-LCS record
036-ASN.1_LR_MOC.dat
036-ASN.1_LR_MOC.txt
MT-LCS
MT-LCS record
037-ASN.1_LR_MTC.dat
037-ASN.1_LR_MTC.txt
NI-LCS
MT-LCS record
038-ASN.1_LR_NI.dat
038-ASN.1_LR_NI.txt
Revision History
Issue
Date
Author
Description
01
200504-10
Guo Jin
Records for the revision from V2.02 to V2.04 were added.
200504-15
Guo Jin/
Zhou
Qiang
02
For details, see V2.02-V2.03: CR 01 and V2.03-V2.04:

CR 01.
The field names in section '1.5 Record contents' were
modified and the fields in section '1.6 Description of
Record Fields ' were arranged according to
alphabetical order.
For details, see V2.04-V2.05: CR 01.
03
200505-05
Guo Jin
The description of the M/C/O field in section 1.5 Record

contents was modified.
04
20058-11
Guo Jin/
Zhou
Qiang
The field eCategory was added.
05
20058-25
Zhou
Qiang
The field resourceChargeIPnumber was added.
06
20065-22
Tan Feng
The following fields were added:

groupCallType
groupCallReference
uus1Type
csReference
csaReference
camel4CDRflag
networkOperatorId
typeOfSubscribers
For details, see section 2.2 V2.07-V2.08: CR 01.
Issue
Date
Author
Description
07
200605-31
Zou
Qiang
The field tariffCode was added.
20066-22
Yu Bin
The field tariffCode was added.
09
20066-20
Zhou
Qiang
The type ofCS reference was changed from INTEGER to

OCTET(1..8).
10
20067-31
Yu Bin
The field audioDataType was added.
11
200608-01
Zhou
Qiang
The type of the camel4CDRflag field was changed from

null to ENUMERATED(1).
12
200608-01
Zhou
Qiang
Section 1.5.19 LocUpdateVLRRecord was added.
13
200608-04
Zhou
Qiang
CallPartyHandling(3) was added to the structure

LevelOfCAMELService.
14
20069-13
Du
Haiwei
The moc/cfw record was changed from CDR

CAMEL4_CDR_flag to camelphase, and disconnectparty
and usertype were added.
08
The type of mscIncomingROUTE and

mscOutgoingROUTE was changed from IA5(1.10) to
IA5(1.32).
The length of mscIncomingROUTE and
mscOutgoingROUTE was changed to 32 bytes.
mtc: Disconnectparty and usertype were added.

gwo/gwi/transit: Disconnectparty was added.
tcamel: Camelphase was added.
15
20069-18
Zhou
Qiang
The fields interactionWithIP and resourceChargeIP were

deleted from numberIncGatewayRecord and
TransitCallRecord.
The fields interactionWithIP and resourceChargeIP were
added to TermCAMELRecord.
16
200610-13
Du
Haiwei
The field interactionWithIP was deleted from the incoming

gateway records and transit records.
17
200612-12
Wang
Fengkui
RecordNumber was added for all the records, and

translatedNumber field was added to MTC, ROAM, GWI,
GWO, and TRANSIT.
18
200601-06
Wang
Fengkui
LAI&CI interface was added (location, changeOfLocation,

firstmccmnc, and lastmccmnc were added) to GWI and
GWO.
19
200701-13
Wang
Fengkui
CMN flag was added to TRANSIT.
20
20072-1
E Xiaofei
The TAG value of disconnectParty and tariffCode was

modified.
Issue
Date
Author
Description
21
20072-2
Du Peng
The field callingChargeAreaCode in the MOC record,

emergency record, forwarding record, MTC record and
roaming record was changed to the field chargeAreaCode.
And the field chargeAreaCode was added to the other
CDRs.
The interface description types of the maximumBitRate
and guaranteedBitRate were added.
The field servedIMSI was added to the GWI CDR.
22
20074-2
Du Peng
Area code was added to MOC, MTC, CFW, SMSMO,

SMSMT, LCS (the LCS launched by the network is
exclusive), and SS_ACT.
23
20074-6
Du Peng
The field cAMELCPHCallConfigurationChange = 0x6

was added to CauseForTerm.
The field interactionWithIP was added to TCAMEL.
24
20077-31
Wang
Xianping
The field MCTType was added to the MOC record.
25
20078-6
Wang
Xianping
The following intelligent fields were added to the ROAM

CDR:
gsm-SCFAddress
serviceKey
levelOfCAMELService
26
20078-16
Du
Haifeng
The CDR examples were added..
27
20078-20
Wang
Fengkui
The CARP field was added to the MOC, CFW and MTC
records.
28
200712-12
Dong
Zhengpin
g
The document structure was re-designed based on the

modification of the billing document.
29
20081-7
Wang
Fengkui
The document was revised based on the modification of

the billing document.
30
20086-17
Wangfen
gkui
1The following fields were added to the TRANSIT

CDR:
redirectingnumberredirectingcounter
2The field partyRelCause was added to the
MOC,CFWMEC,EMC,TRANSIT,GWI,GWO,TCAME
L,ROAM CDR
Issue
Date
Author
Description
31
20086-24
Wangfen
gkui
The following fields were added to the

GWOGWI TRANSIT CDR:
redirectingnumberredirectingcounter
The following fields were added to the CFW CDR:
redirectingcounter
32
200808-06
Lin Hua
Update the TAG VALUE IN CDR
33
20088-25
Lin Hua
ADD roaming-number in transit record
34
20089-12
Lin Hua
ADD The category of subscribers. Field IN

GatewayIncoming redordOutGoingway record transit
record

03-Msoftx3000 v100r006c05 Asn.1 CDR Description

Uploaded by

Document Information

Original Description:

Original Title

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

03-Msoftx3000 v100r006c05 Asn.1 CDR Description

Uploaded by

Copyright:

Available Formats

03-MSOFTX3000 V100R006C05 ASN.

HUAWEI TECHNOLOGIES CO., LTD.

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Huawei Technologies Co., Ltd.

Administration Building, Huawei Technologies Co., Ltd.,

Copyright Huawei Technologies Co., Ltd. 2007. All rights reserved.

Trademarks and Permissions

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

About This Document

Guo Jin, Li Chunlin

Gao Yue, Jia Yongli

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

3 Description of Record Fields......................................................................................................112

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

4 ASN.1 Description of the CDR File...........................................................................................166

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

ASN.1 Encoding Format

1.1 ASN.1 Encoding Format

Identifier octets (also called Tag)

For details, see section 1.2.1"Encoding Rules of Identifier Octets."

For details, see section 1.2.2"Encoding Rules of Length Octets."

For details, see section 1.2.3"Encoding Rules of Contents Octets."

1.2 ASN.1 Encoding Format

1.2.1 Encoding Rules of Identifier Octets

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Application is seldom used, and therefore it is not described here.

Context-Specific is used to define the class types.

Private can be negotiated based on the actual conditions.

The subsequent octets comply with the following rules:

Bits 7-1 of the first subsequent octet cannot be all 0s.

For details, see Figure 1.2.

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

Subsequent octets are encoded as follows:

1.2.2 Encoding Rules of Length Octets

Short Encoding Mode

Bits 7-1 specify the length.

If L is equal to 26H, the length is encoded as 0010,0110.

Long Encoding Mode

Issue 1.00 (2008-02-25)

Huawei Technologies Proprietary

1.2.3 Encoding Rules of Contents Octets

The following describes different data classes:

01H 0000, 0000