02-A CDR Farmat

HUAWEI iGateway Bill
User Manual Contents
Contents
A CDR Format..............................................................................................................................A-1
A.1 Acronyms and Abbreviations........................................................................................................................A-2
A.2 ASN.1 (Basic Encoding Rules) Description.................................................................................................A-5
A.2.1 General................................................................................................................................................A-5
A.2.2 Coding of ASN.1 Tag..........................................................................................................................A-5
A.2.3 Coding of Length.................................................................................................................................A-6
A.2.4 Coding of Contents..............................................................................................................................A-7
A.2.5 Structure of Call Data Record.............................................................................................................A-7
A.3 Charging Data Record Transfer....................................................................................................................A-8
A.4 Record types.................................................................................................................................................A-8
A.5 Record contents............................................................................................................................................A-9
A.5.1 Mobile Originated Call Attempt..........................................................................................................A-9
A.5.2 Mobile Originated Emergency Call Attempt.....................................................................................A-16
A.5.3 Mobile Originated Call Forwarding Attempt....................................................................................A-19
A.5.4 Mobile Terminated Call Attempt.......................................................................................................A-26
A.5.5 Roaming Call Attempt.......................................................................................................................A-32
A.5.6 Incoming Gateway Call Attempt.......................................................................................................A-35
A.5.7 Outgoing Gateway Call Attempt.......................................................................................................A-38
A.5.8 Transit Call Attempt..........................................................................................................................A-41
A.5.9 Short Message Service, Mobile Originated.......................................................................................A-43
A.5.10 Short Message Service, Mobile Terminated....................................................................................A-46
A.5.11 Mobile Terminated Location Request (MT-LR)..............................................................................A-48
A.5.12 Mobile originaTed Location Request (MO-LR)..............................................................................A-51
A.5.13 Network Induced Location Request (NI-LR)..................................................................................A-54
A.5.14 Supplementary Service Actions.......................................................................................................A-56
A.5.15 HLR Interrogation...........................................................................................................................A-59
A.5.16 Common Equipment Usage Record................................................................................................A-60
A.5.17 Terminating CAMEL Call Attempt.................................................................................................A-62
A.5.18 IMEI Observation Ticket.................................................................................................................A-66
A.6 Description of Record Fields......................................................................................................................A-67
A.6.1 Additional Charging Information......................................................................................................A-68
A.6.2 Aiur Requested..................................................................................................................................A-68
Issue 07 (2007-10-10) Huawei Technologies Proprietary i

Contents User Manual
A.6.3 AoC Parameters/Change of AoC Parameters....................................................................................A-69

A.6.4 Basic Service/Change of Service/ISDN Basic Service.....................................................................A-69
A.6.5 Call Duration.....................................................................................................................................A-75
A.6.6 Call Reference...................................................................................................................................A-77
A.6.7 Calling/Called/Connected/Translated Number..................................................................................A-77
A.6.8 Calling Party Number........................................................................................................................A-79
A.6.9 CAMEL Call Leg Information..........................................................................................................A-79
A.6.10 CAMEL Information.......................................................................................................................A-80
A.6.11 CAMEL Initiated CF Indicator........................................................................................................A-80
A.6.12 CAMEL Modified Service Center...................................................................................................A-81
A.6.13 CAMEL SMS Information..............................................................................................................A-81
A.6.14 Category..........................................................................................................................................A-82
A.6.15 Cause for Termination.....................................................................................................................A-82
A.6.16 Default Call/SMS Handling............................................................................................................A-83
A.6.17 Destination Subscriber Number......................................................................................................A-84
A.6.18 Diagnostics......................................................................................................................................A-84
A.6.19 EMS-Digits......................................................................................................................................A-86
A.6.20 EMS-Key.........................................................................................................................................A-86
A.6.21 Entity Number.................................................................................................................................A-86
A.6.22 Equipment ID..................................................................................................................................A-86
A.6.23 Equipment Type...............................................................................................................................A-86
A.6.24 Event Time Stamps..........................................................................................................................A-87
A.6.25 Fixed Network User Rate................................................................................................................A-88
A.6.26 Free Format Data.............................................................................................................................A-89
A.6.27 Free Format Data Append Indicator................................................................................................A-89
A.6.28 Guaranteed Bit Rate........................................................................................................................A-90
A.6.29 GsmSCF Address............................................................................................................................A-90
A.6.30 Interrogation result..........................................................................................................................A-91
A.6.31 IMEI Check Event...........................................................................................................................A-91
A.6.32 IMEI Status......................................................................................................................................A-91
A.6.33 Incoming/Outgoing Route...............................................................................................................A-92
A.6.34 LCS Cause.......................................................................................................................................A-92
A.6.35 LCS Client Identity..........................................................................................................................A-92
A.6.36 LCS Client Type..............................................................................................................................A-93
A.6.37 LCS Priority....................................................................................................................................A-93
A.6.38 LCS QoS..........................................................................................................................................A-93
A.6.39 Level of CAMEL Service................................................................................................................A-94
A.6.40 Location/Change of Location..........................................................................................................A-94
A.6.41 Location Estimate............................................................................................................................A-95
A.6.42 Location Type..................................................................................................................................A-95
A.6.43 Maximum Bit Rate..........................................................................................................................A-95
A.6.44 MCCMNC.......................................................................................................................................A-96
ii Huawei Technologies Proprietary Issue 07 (2007-10-10)

A.6.45 Measure Duration............................................................................................................................A-96

A.6.46 Message Reference..........................................................................................................................A-97
A.6.47 MLC Number..................................................................................................................................A-97
A.6.48 Mobile Station Classmark/Change of Classmark............................................................................A-97
A.6.49 MOLR Type.....................................................................................................................................A-97
A.6.50 MSC Address...................................................................................................................................A-97
A.6.51 MSC CIC.........................................................................................................................................A-97
A.6.52 Org MSC ID/SPC............................................................................................................................A-98
A.6.53 MSC Server Indication....................................................................................................................A-98
A.6.54 Network Call Reference..................................................................................................................A-98
A.6.55 Notification to MS User..................................................................................................................A-98
A.6.56 Number of DP Encountered............................................................................................................A-99
A.6.57 Number of Forwarding....................................................................................................................A-99
A.6.58 Old/New Location...........................................................................................................................A-99
A.6.59 Partial Record Type.........................................................................................................................A-99
A.6.60 Positioning Data..............................................................................................................................A-99
A.6.61 Privacy Override............................................................................................................................A-100
A.6.62 Radio Channel Requested/Radio Channel Used/Change of Radio Channel.................................A-100
A.6.63 Rate Indication...............................................................................................................................A-100
A.6.64 Record Extensions.........................................................................................................................A-101
A.6.65 Record Type...................................................................................................................................A-101
A.6.66 Recording Entity............................................................................................................................A-102
A.6.67 Org RNC or BSC ID......................................................................................................................A-102
A.6.68 Roaming Number..........................................................................................................................A-102
A.6.69 Routing Number............................................................................................................................A-102
A.6.70 Sequence Number..........................................................................................................................A-102
A.6.71 Served IMEI..................................................................................................................................A-102
A.6.72 Served IMSI..................................................................................................................................A-103
A.6.73 Served MSISDN............................................................................................................................A-104
A.6.74 Service Center Address.................................................................................................................A-105
A.6.75 Service Key...................................................................................................................................A-105
A.6.76 Short Message Service Result.......................................................................................................A-105
A.6.77 Speech Version Supported/Speech Version Used..........................................................................A-105
A.6.78 System Type..................................................................................................................................A-106
A.6.79 Supplementary Service(s)..............................................................................................................A-106
A.6.80 Supplementary Service Action......................................................................................................A-111
A.6.81 Supplementary Service Action Result...........................................................................................A-112
A.6.82 Supplementary Service Parameters...............................................................................................A-112
A.6.83 Transparency Indicator..................................................................................................................A-112
A.6.84 SMS Text.......................................................................................................................................A-112
A.6.85 SMS User Data Type.....................................................................................................................A-112
A.6.86 Concatenated SMS Reference Number.........................................................................................A-114
Issue 07 (2007-10-10) Huawei Technologies Proprietary iii

A.6.87 Maximum Number of SMS in the Concatenated SMS.................................................................A-116

A.6.88 Sequence Number Of the Current SMS........................................................................................A-116
A.6.89 CUG Index.....................................................................................................................................A-116
A.6.90 CUG Outgoing Access Indicator...................................................................................................A-116
A.6.91 CUG Interlock Code......................................................................................................................A-116
A.6.92 CUG Outgoing Access Used/CUG Incoming Access Used..........................................................A-116
A.6.93 Modem Type..................................................................................................................................A-117
A.6.94 Classmark3....................................................................................................................................A-117
A.6.95 Charged Party................................................................................................................................A-117
A.6.96 Original Called Number................................................................................................................A-117
A.6.97 Calling Charge Area Code.............................................................................................................A-118
A.6.98 Called Charge Area Code..............................................................................................................A-118
A.6.99 Call Emlpp Priority........................................................................................................................A-118
A.6.100 Caller/Called Default Emlpp Priority..........................................................................................A-118
A.6.101 Ea Subscriber Info.......................................................................................................................A-119
A.6.102 Selected CIC................................................................................................................................A-119
A.6.103 Ported Flag...................................................................................................................................A-119
A.6.104 Global Area ID.............................................................................................................................A-119
A.6.105 Change Of global Area ID...........................................................................................................A-119
A.6.106 Interaction With IP......................................................................................................................A-120
A.6.107 HLC.............................................................................................................................................A-120
A.6.108 LLC.............................................................................................................................................A-120
A.6.109 ISDN-BC.....................................................................................................................................A-120
A.6.110 USSDCodingScheme...................................................................................................................A-120
A.6.111 USSDString.................................................................................................................................A-120
A.6.112 USSDNotifyCounter....................................................................................................................A-120
A.6.113 USSDRequestCounter.................................................................................................................A-120
A.6.114 Initial Call Attempt Flag..............................................................................................................A-120
A.6.115 USSD Call Back FLAG...............................................................................................................A-121
A.6.116 mscIncomingRouteAttribute.......................................................................................................A-121
A.6.117 mscOutgoingRouteAttribute........................................................................................................A-121
A.6.118 Voice Indicator.............................................................................................................................A-121
A.6.119 Call Type......................................................................................................................................A-122
A.6.120 B_CATEGORY...........................................................................................................................A-122
A.7 Charging Data Record Structure:ASN.1 description................................................................................A-122
A.8 Examples of CDR.....................................................................................................................................A-178
A.8.1 Voice Call........................................................................................................................................A-178
A.8.2 VP Call............................................................................................................................................A-180
A.8.3 Other Bear Service Call...................................................................................................................A-182
A.8.4 Forwarding Record..........................................................................................................................A-184
A.8.5 Emergency Record..........................................................................................................................A-186
A.8.6 Middle Billing.................................................................................................................................A-187
iv Huawei Technologies Proprietary Issue 07 (2007-10-10)

A.8.7 SMS.................................................................................................................................................A-191
A.8.8 Concatenated Long SMS.................................................................................................................A-194
A.8.9 Interrogation....................................................................................................................................A-197
A.8.10 USSD.............................................................................................................................................A-198
A.8.11 Supplementary Service..................................................................................................................A-199
A.8.12 Handover.......................................................................................................................................A-202
A.8.13 CommonEquipRecord...................................................................................................................A-203
A.8.14 IncGatewayRecord........................................................................................................................A-204
A.8.15 OutGatewayRecord.......................................................................................................................A-205
A.8.16 TransitCallRecord..........................................................................................................................A-206
A.8.17 RoamingRecord.............................................................................................................................A-207
A.8.18 Moc(CAMEL)...............................................................................................................................A-209
A.8.19 Mtc(CAMEL)................................................................................................................................A-210
A.8.20 TCAMEL.......................................................................................................................................A-212
A.8.21 Moc(FCI).......................................................................................................................................A-213
A.8.22 Moc(hotbilling).............................................................................................................................A-214
A.8.23 SS_PLMN_SPECIFICSS1 record.................................................................................................A-216
A.8.24 SS_PLMN_SPECIFICSS3 record.................................................................................................A-217
A.8.25 MO-LCS........................................................................................................................................A-218
A.8.26 MT-LCS.........................................................................................................................................A-220
A.8.27 NI-LCS..........................................................................................................................................A-221
Issue 07 (2007-10-10) Huawei Technologies Proprietary v

Figures
Figure A-1 Structure of call data record.............................................................................................................A-8
Figure A-2 Figure 1...........................................................................................................................................A-76
Figure A-3 Figure 2.........................................................................................................................................A-103
Figure A-4 Figure 3.........................................................................................................................................A-103
Figure A-5 Figure 4.........................................................................................................................................A-104
Figure A-6 Figure 5.........................................................................................................................................A-114
Figure A-7 Example--moCallRecord.dat........................................................................................................A-178
Figure A-8 Example--mtCallRecord.dat.........................................................................................................A-179
Figure A-9 Example—moCallRecord(VP).dat...............................................................................................A-181
Figure A-10 Example—moCallRecord(BS).dat.............................................................................................A-183
Figure A-11 Example—forwardCallRecord(cfnry).dat..................................................................................A-184
Figure A-12 Example—moCallRecord(EmergencyCallWithoutSIM).dat.....................................................A-186
Figure A-13 Example—moCallRecord(partial1).dat......................................................................................A-187
Figure A-16 Example—moSMSRecord.dat...................................................................................................A-192
Figure A-17 Example—mtSMSRecord.dat....................................................................................................A-193
Figure A-18 Example1—moSMSRecord(partial1).dat..................................................................................A-194
Figure A-21 Example—hlrRecord.dat............................................................................................................A-197
Figure A-22 Example—ssActionRecord(USSD).dat.....................................................................................A-198
Figure A-23 Example—ssActionRecord(forward registration).dat................................................................A-199
Figure A-24 Example—ssActionRecord(BAOC activation).dat....................................................................A-200
Figure A-25 Example—ssActionRecord(BAOC deactivation).dat................................................................A-201
Figure A-26 Example—moCallRecord(Handover).dat..................................................................................A-202
Issue 07 (2007-10-10) Huawei Technologies Proprietary vii

Figure A-27 Example—commonEquipRecord.dat.........................................................................................A-204
Figure A-28 Example—incGatewayRecord.dat.............................................................................................A-205
Figure A-29 Example—outGatewayRecord.dat.............................................................................................A-206
Figure A-30 Example—transitCallRecord.dat................................................................................................A-207
Figure A-31 Example—roamingRecord.dat...................................................................................................A-208
Figure A-32 Example—moCallRecord(camel).dat........................................................................................A-209
Figure A-33 Example—mtCallRecord(camel).dat.........................................................................................A-210
Figure A-34 Example—termCAMELRecord.dat...........................................................................................A-212
Figure A-35 Example—moc(withFCI).dat.....................................................................................................A-213
Figure A-36 Example—moCallRecord(hot).dat.............................................................................................A-215
Figure A-37 Example—moc(SS_PLMN_SPECIFCSS1).dat.........................................................................A-216
Figure A-38 Example—moc(SS_PLMN_SPECIFCSS3).dat.........................................................................A-217
Figure A-39 Example—lcsMOrecord.dat.......................................................................................................A-219
Figure A-40 Example—lcsMTrecord.dat.......................................................................................................A-220
Figure A-41 Example—lcsNIrecord.dat.........................................................................................................A-221
viii Huawei Technologies Proprietary Issue 07 (2007-10-10)

Tables
Table A-1 MOC record......................................................................................................................................A-10
Table A-2 MOC emergency record...................................................................................................................A-16

Table A-3 MOC, call forwarding record...........................................................................................................A-19
Table A-4 MTC record......................................................................................................................................A-26
Table A-5 Roaming record................................................................................................................................A-32
Table A-6 Incoming gateway record.................................................................................................................A-35
Table A-7 Outgoing gateway record.................................................................................................................A-38
Table A-8 Transit record....................................................................................................................................A-41
Table A-9 SMS-MO record...............................................................................................................................A-44
Table A-10 SMS-MT record.............................................................................................................................A-46
Table A-11 LCS-MT record..............................................................................................................................A-49
Table A-12 LCS-MO record..............................................................................................................................A-51
Table A-13 LCS-NI record................................................................................................................................A-54
Table A-14 SS-action record.............................................................................................................................A-57
Table A-15 HLR interrogation record...............................................................................................................A-59
Table A-16 Common equipment usage record..................................................................................................A-60
Table A-17 Terminating CAMEL record..........................................................................................................A-62
Table A-18 IMEI ticket.....................................................................................................................................A-66
Issue 07 (2007-10-10) Huawei Technologies Proprietary ix

User Manual CDR FormatCDR Format
A CDR Format
About This Chapter
The following table lists the contents of this chapter.
Title Description
A.1 Acronyms and Lists the acronyms and abbreviations related to CDR
Abbreviations format.
A.2 ASN.1 (Basic Encoding Describes the basis encoding rules of the ASN.1 CDR.
Rules) Description
A.3 Charging Data Record Describes how to transfer CDRs from the iGWB to the
Transfer BC.
A.4 Record types Describes the types of call and event records contained in
CDRs.
A.5 Record contents Describes the details of a CDR.
A.6 Description of Record Describes the information on each field in a CDR.
Fields
A.7 Charging Data Record Describes the structure of a ASN.1 CDR.
Structure:ASN.1 description
A.8 Examples of CDR Describes the CDR format with examples.
Issue 07 (2007-10-10) Huawei Technologies Proprietary 1

CDR FormatCDR Format User Manual
A.1 Acronyms and Abbreviations

A
AoC Advice of Charge
B
BCSM Basic Call State Model
BSS Base Station System
C
CAI Charge Advice Information
CAMEL Customised Applications for Mobile network Enhanced Logic
CD Call Divert
CDR Call Detail Record
CUG Closed User Group
D
DP Detection Point
E
ECT Explicit Call Transfer
EDP Event Detection Point
EIR Equipment Identity Register
EMS-Digits North American Emergency Service Routing Digits
EMS-Key North American Emergency Service Routing Key
eMLPP Enhanced Multi-Level Precedence and Pre-emption
ETSI European Telecommunications Standard Institute
F
FCI Furnish Charging Information
FTAM File Transfer Access Management
FTP File Transfer Protocol
2 Huawei Technologies Proprietary Issue 07 (2007-10-10)

G
GMSC Gateway MSC
GERAN GSM/EDGE Radio Access Network
gsmSCF GSM Service Control Function
gsmSSF GSM Service Switching Function
H
HLR Home Location Register
HPLMN Home PLMN
HSCSD High Speed Circuit Switched Data
I
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
ISDN Integrated Services Digital Network
L
LAC Location Area Code
M
MLC Mobile Location Centre
MOC Mobile Originated Call (attempt)
MO-LR Mobile Originated Location Request
MS Mobile Station
MSC Mobile Switching Centre
MSRN Mobile Station Roaming Number
MTC Mobile Terminated Call (attempt)
MT-LR Mobile Terminated Location Request
N
NAR North America Region
NE Network Element
NEF Network Element Function

NM Network Management
NI-LR Network Induced Location Request
O
O_CSI Originating CAMEL Subscription Information
OMC Operations and Maintenance Centre
OS Operations System
P
PLMN Public Land Mobile Network
S
SAC Service Area Code
SCF Service Control Function
SCI Subscriber Controlled Input or Send Charging Information
SMS Short Message Service
SS7 Signalling System No. 7
T
T_CSI Terminating CAMEL Subscription Information
TDP Trigger Detection Point
TMN Telecommunications Management Network
U
USIM User Service Identity Module
USSD Unstructured Supplementary Service Data
UTRAN UMTS Terrestrial Radio Access Network
V
VAS Value Added Service
VLR Visitor Location Register
VMSC Visited MSC
VPLMN Visited PLMN

VT-CSI Visited Terminating CAMEL Subscription Information
Numeric
2G MSC Refer to an MSC Release 98 or prior
3G MSC Refer to an MSC Release 99 or later
A.2 ASN.1 (Basic Encoding Rules) Description

A.2.1 General
ASN.1 is an abbreviation of ‘Abstract Syntax Notation One.
ASN.1 can be regarded as a high-level protocol language and is an internationally accepted
standard for defining application layer protocol syntaxes. It is needed because application
protocols deal with complex data structures.
ASN.1 provides the designer with simple types, for instance, integer, Boolean, and octet string
.With the simple types as building stones the protocol designer can construct more complex
data types. More complex data types can be built from sets or sequences of simpler types, by
uniquely ‘tagging’ particular data structures for easy recognition. For instance, a call data
record can be structured as a set consisting of a number of data fields. Encoding of a data
value consists of 4 components (in correct order):
 Identifier octets
 Length octets
 Contents octets
 End-of-contents octets (for indefinite length encoding)
A.2.2 Coding of ASN.1 Tag

The identifier octets encode the ASN.1 tag of the data value. Two possibilities exist:
Single Octet Encoding for Tag Numbers 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
Use of a Leading Octet for Tag Numbers Bigger Than or Equal to 31

The leading octet is encoded as follows:
8 7 6 5 4 3 2 1
+-------+---+---+---+---+---+---¦
1 ¦ CLASS ¦P/C¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦
+-------------------------------+
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:

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.
Only one subsequent octet is supported (Tag values<128).
A.2.3 Coding of Length

The length octets encode the length of the following content of the data item. Three
possibilities exist in ASN.1: short, long and indefinite. The indefinite variant is not supported
and that’s why not scope of this explanation.
Short Length Encoding for Length from 0 to 127 (Inclusive)

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 Length Encoding for Length > 127

8 7 6 5 4 3 2 1
+---+---------------------------¦
1 ¦ 1 ¦ 0 < n < 127 ¦
+-------------------------------+
+-------------------------------¦
2 ¦ L L L L L L L L ¦
+-------------------------------+
...
+-------------------------------¦
n+1¦ L L L L L L L L ¦
+-------------------------------+
LLLLLLLL represents the length of the content
A.2.4 Coding of Contents

The numbering of bits within one octet and the encoding of a binary value in an octet
structure can be found in the following figure:
8 7 6 5 4 3 2 1
+-------------------------------¦
¦ most significant byte ¦ octet 1
+-------------------------------¦
¦ ¦ octet 2
+-------------------------------¦
. .
. .
+-------------------------------¦
¦ least significant byte ¦ octet n
+-------------------------------+
bit 8 of octet 1 is the most significant bit (msb)

bit 1 of octet n is the least significant bit (lsb)
A.2.5 Structure of Call Data Record

Call Data Record is composed of a header of Call Data Record File and possible Event
Record(s). The header and each record have a tag (ASN.1 TAG) and a length indicator an
overhead. As an example a structure of call data record containing a header and two event
records s is shown in Figure A-1.

Figure 1.1 Structure of call data record
A.3 Charging Data Record Transfer

The charging data records shall be transferred from the MSC-Server to the billing system by
the use of FTAM protocol on ITU-T Recommendation TCP/IP, FTP over TCP/IP. For further
details of the use of FTAM see GSM 12.01, for the use of FTP see RFC 959.
A.4 Record types

The following contents describe the types of each of the call and event records in Huawei
GSM/WCDMA system defined in the present document
 Mobile originated call attempt;
 Mobile originated emergency call attempt;
 Mobile originated, call forwarding attempt;
 Mobile terminated call attempt;

 Roaming call attempt;

 Incoming call attempt in a gateway MSC;
 Outgoing call attempt from a gateway MSC;
 Transit call attempt;
 Supplementary service actions;
 HLR interrogation;
 Short message service (point-to-point), mobile originated;
 Short message service (point-to-point), mobile terminated;
 Mobile terminated location request (MT-LR);
 Mobile originated location request (MO-LR);
 Network induced location request (NI-LR);
 Common equipment usage record;
 Terminating CAMEL call attempt;
 IMEI observation ticket
A.5 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 field has the following meaning:
M This field is mandatory and always present. Any exceptions to this rule are explicitly
described.
C This field is only available under certain conditions. If available the field is present. The
conditions under which the field is available are individually described.
O This field is optional and configurable either via additional TMN management functions
or manufacturer specific means. For the avoidance of doubt, optional does not mean that the
parameter is not supported by the Network Element. Equipment manufacturers shall be
capable of providing all of these fields in order to claim conformance with the present
document.
 2G means 2G-MSC
 3G means 3G-MSC
 n means the element number of sequence or set
A.5.1 Mobile Originated Call Attempt

If the generation of these records is enabled then 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, as listed in Table A-1.

Table 1.1 MOC record

Field 2G 3G TAG TYPE Description
Record M M 0x80 ENUMERAT Mobile originated.

Type 01 00 ED
(1)
Served M M 0x81 TBCD(3..8) IMSI of the calling party.
IMSI
Served C C 0x82 TBCD(8) IMEI of the calling ME, if available.
IMEI
Served M M 0x83 ADRESS(2.. The primary MSISDN of the calling
MSISDN 9) party.
Calling M M 0x84 ADRESS The address of the calling party.
Number (2..17)
Called M M 0x85 ADRESS The address of the called party e.g. the
Number (2..17) number dialled by the calling sub.
Translated O O 0x86 ADRESS The called number after digit
Number (2..17) translation within the MSC (if
applicable)
Connected O O 0x87 ADRESS The number of the connected party if
Number (2..17) different to the Called Number
Roaming O O 0x88 ADRESS The Mobile Station Roaming Number
Number (2..17) employed to route this connection, if
applicable (Roaming Number of B).
Recording M M 0x89 ADRESS The E.164 number of the visited MSC
Entity (2..9) producing the record.
Incoming O O 0xAA IA5(1..10) The MSC route on which the call
ROUTE originated , usually from the BSS
Outgoing O O 0xAB IA5(1..10) The route on which the call left the
ROUTE MSC
Location M M 0xAC OCTET(8) The identity of the cell or the SAC in
which the call originated including the
location area code.
Change of O O 0xAD SEQUENCE A list of changes in Location Area
Location OF ( 23 * n ) Code / Cell Identifier each time-
stamped.
Basic M M 0xAE OCTET(3) Bearer or teleservice employed.
service
Transparenc C C 0x8F ENUMERAT Only provided for those basic services
y Indicator ED which may be employed in both
(1) transparent and non-transparent mode.

Change Of C C 0xB0 SEQUENCE A list of changes of basic service

Service OF ( (18..27) during a connection each time-
* n) stamped.
Supp. C C 0xB1 SEQUENCE Supplementary services invoked as a
Services OF result of this connection.
(16 * n)
AOC O O 0xB2 OCTET(4..2 The charge advice parameters sent to
Parameters 8) the MS on call set-up
Change of O O 0xB3 SEQUENCE New AOC parameters sent to the MS
AOC Para OF ( 43 * n) e.g. as a result of a tariff switch over,
including the time at which the new set
was applied.
MS M M 0x94 OCTET(2..3) The mobile station classmark
Classmark employed on call set-up.
Change of O O 0xB5 OCTET (16 ) A list of changes to the classmark
Classmark during the connection each time-
stamped
Event time M M 0x9F OCTET(9) Setup or IAM timestamp from calling
stamps: O O 81 49 OCTET(9) side
O O 0x96 OCTET(9) Seizure of incoming traffic channel
C C 0x9F OCTET(9) Alerting or ACM timestamp from
81 called side
O O 4A OCTET(9)
Answer (for successful calls)
0x97 Release of traffic channel
0x98
Call M M 0x99 INTEGER(1. The chargeable duration of the
duration .2) connection for successful calls, the
holding time for call attempts.
Radio O - 0x9B ENUMERAT The type of radio traffic channel (full /
Chan. ED half etc.) requested by the MS.
Requested (1)
Radio O - 0x9C ENUMERAT The type of radio channel actually used
Chan. Used ED (full or half rate).
(1)
Change of O - 0xBD OCTET A list of changes each time stamped
Radio (14..17 )
Chan.
Cause for M M 0x9E INTEGER The reason for the release of the
termination (1) connection.
Diagnostics O O 0xBF INTEGER(4) A more detailed reason for the release
1F of the connection.

Call M M 0x9F OCTET(1..8) A local identifier distinguishing

reference 20 between transactions on the same MS
Sequence C C 0x9F INTEGER(1) Partial record sequence number, only
no. 21 present in case of partial records.
Additional O O 0xBF SEQUENCE Charge/no charge indicator and
Chg. Info 22 (3) additional charging parameters
Record O O 0xBF SET OF (11 A set of network/ manufacturer
extensions 23 * n) specific extensions to the record.
gsmSCF C C 0x9F ADRESS(2.. Identifies the CAMEL server serving
address 24 9) the subscriber.
Service key C C 0x9F INTEGER(1. The CAMEL service logic to be
25 .4) applied.
Network C C 0x9F OCTET(1..8) An identifier to correlate transactions
call 26 on the same call taking place in
reference different network nodes shall be
present.
MSC C C 0x9F ADRESS(2.. This field contains the E.164 number
Address 27 9) assigned to the MSC that generated the
network call reference.
CAMEL - - 0x9F BOOLEAN( Indicates that the CAMEL server
initiated CF 28 1) initiated call forwarding in CFW CDR.
indicator
Default call O O 0x9F ENUMERAT Indicates whether or not a CAMEL
handling 29 ED call encountered default call handling.
(1) This field shall be present only if
default call handling has been applied.
Fixed O O 0x9F ENUMERAT Indicates the user data rate applied for
Network 2D ED the connection in the fixed network.
User Rate (1) Shall only be present for 2G HSCSD
connections and for UMTS data
connections.
Air O O 0x9F ENUMERAT The total Air Interface User Rate
Interface 2E ED Requested by the MS at call setup.
User Rate (1) Shall only be present for non-
Requested transparent HSCSD connections.
Speech O - 0x9F OCTET(1) Speech version used for that call
Version 32
Used
Speech O - 0x9F OCTET(1) Speech version supported by the MS
Version 31 with highest priority indicated by MS
Supported

Number of O O 0x9F INTEGER(1) Numbers that counts how often armed

DP 33 detection points (TDP and EDP) were
encountered encountered.
Level of O O 0x9F BIT Indicator for the complexity of the
CAMEL 34 STRING(2) CAMEL feature used.
service
Free format C C 0x9F OCTET(1..1 This field contains data sent by the
Data 35 60) gsmSCF in the FCI messages. The data
can be sent either in one FCI message
or several FCI messages with append
indicator.
CAMEL O O 0xBF SEQUENCE Set of CAMEL information IEs. Each
call leg 36 OF of these IEs contains information
information ((104..124) * related to one outgoing CAMEL call
n) leg.
Free format C C 0x9F BOOLEAN Indicator if free format data from this
data append 37 (1) CDR is to be appended to free format
indicator data in previous partial CDR.
Default call O O 0x9F ENUMERAT Indicates whether or not a CAMEL
handling 2 38 ED call encountered default call handling
(1) for 2nd service such as dialled service.
This field shall be present only if
default call handling has been applied.
GsmSCF C C 0x9F ADRESS Identifies the CAMEL server serving
address 2 39 (2..9) the subscriber for 2nd service such as
dialled service.
Service key C C 0x9F INTEGER The CAMEL service logic to be
2 3A (1..4) applied for 2nd service such as dialled
service.
Free format C C 0x9F OCTET(1..1 This field contains data sent by the
Data 2 3B 60) gsmSCF in the FCI message(s) for 2nd
service such as dialled service. The
data can be sent either in one FCI
message or several FCI messages with
append indicator.
Free format C C 0x9F BOOLEAN Indicator if free format data for 2nd
data append 3C (1) service from this CDR is to be
indicator 2 appended to free format data in
previous partial CDR.
System M M 0x9F ENUMERAT This field indicates the use of GERAN,
Type 3D ED UTRAN (or a value of unknown). This
(1) field is present when either the
UTRAN or GERAN air-interface is
used on call setup.

Rate O O 0x9F OCTET(1) Present if “rate adaption” parameters

Indication 3E for the basic service were signalled
between the MS/UE and the network,
see TS 24.008.
Partial O O 0x9F ENUMERAT Indicates the event (time limit etc.) that
Record 45 ED caused the generation of a partial
Type (1) record.
Guaranteed - O 0x9F ENUMERAT Describes the bit-rate the UMTS

bit rate 46 ED service shall guarantee to the user or
(1) application. Guaranteed Bit Rate may
be used to facilitate admission control
based on available resources, and for
resource allocation within UMTS.
Maximum - O 0x9F ENUMERAT Maximum Bit Rate can be used to
bit rate 47 ED make code reservations in the
(1) 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 bit-rate to
be defined for applications able to
operate with different rates (e.g.
applications with adapting codecs).
Modem O O 0x9F ENUMERAT Indicates the type of Modem used.
Type 81 0B ED
(1)
Classmark3 O O 0x9F OCTET(2) May be present when access in BSC.
81 0C
Charged O O 0x9F ENUMERAT Indicates if the calling subscriber or
Party 81 ED the called subscriber is charged for the
0D (1) call, or if the call is not charged. May
be modified by the SCF.
Original - - 0x9F ADRESS The address of original called party in
Called 81 0E (2..17) CFW CDR.
Number
Calling O O 0x9F OCTET(1..3) Indicates the calling party logical area
Charge 81 11 for distance charge
Area Code
Called O O 0x9F OCTET(1..3) Indicates the called party logical area
Charge 81 12 for distance charge
Area Code
MSC C C 0x9F INTEGER This field indicates the cic, only
Outgoing 81 26 (1..2) present in case of outgoing call and
Circuit TDM bear type.

RNC or M M 0x9F OCTET(3) This field indicates the SPC of RNC or

BSC Id 81 27 BSC.
MSC Id or M M 0x9F OCTET(3) This field indicates the SPC of MSC.
SPC 81 28
Call Emlpp O O 0x9F OCTET(1) Indicates the priority of call. See
Priority 81 24.008
2A
Caller O O 0x9F OCTET(1) Indicates the calling subscriber’s
Default 81 2B priority. See 29.002
Emlpp
Priority
Ea C C 0x9F OCTET(3) Indicates the calling subscriber’s
Subscriber 81 2E information of Equal Access
Info
Selected C C 0x9F OCTET(3) Indicates the selected code of Carrier
CIC 81 2F identification
optimalRou - - 0x9F NULL Reserved for the future
tingFlag 81 31
tingLateFor 81 32
wardFlag
tingEarlyFo 81 33
rwardFlag
Ported flag O O 0x9F ENUMERAT Indicates if called party be ported.
81 34 ED
(1)
Called IMSI C C 0x9F TBCD(3..8) Indicates IMSI of the called party if
81 35 called party be ported.
Global Area O O 0x9F OCTET(7) Indicates CGI of GSM or SAI of
ID 81 3C WCDMA
Change Of O O 0xBF SEQUENCE A list of changes in CGI / SAI each
Global Area 81 OF time-stamped.
ID 3D (22 * n)
Subscriber M M 0x9F OCTET(1) Indicates the category of subscriber.
Category 81 3E
First MCC M M 0x9F OCTET(3) Indicates the MCC and MNC of the
MNC 81 40 network where call is initiated.
Intermediat O O 0x9F OCTET(3) Indicates the MCC and MNC of the
e MCC 81 41 network where call is served only
MNC present after handover.

Last MCC C C 0x9F OCTET(3) Indicates the MCC and MNC of the
MNC 81 42 network where call is served only
present after handover.
CUG O O 0x9F ENUMERAT Indicates the subscriber with a
Outgoing 81 43 ED Outgoing Access.
Access (1)
Indicator
CUG O O 0x9F OCTET(4) Network code + CUG interlock
Interlock 81 44
Code
CUG O O 0x9F ENUMERAT Indicates caller and called whether or
Outgoing 81 45 ED not is in the same CUG group.
Access (1)
Used
CUG Index O O 0x9F OCTET(2) The CUG index has significance only
81 46 between the subscriber and network.
Interaction C C 0x9F NULL (0) In the case of interaction between SSP
With IP 81 47 and IP, GsmSCF play announcement to
SSP and start charging.
Hot billing C C 0x9F INTEGER(1) Indicates the Subscriber is one with
tag 81 48 Hot Billing service.
A.5.2 Mobile Originated Emergency Call Attempt

If the generation of MOC records is enabled then 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, as listed in Table A-2.
Table 1.2 MOC emergency record

Record Type M M 0x80 ENUMERATED Mobile originated.

01 00 (1)
Served IMSI C C 0x81 TBCD(3..8) IMSI of the calling party in case
of an emergency call with a SIM
card.
Served IMEI C C 0x82 TBCD(8) IMEI of the calling mobile
equipment if available.
Served O O 0x83 ADRESS(2..9) The primary MSISDN of the
MSISDN calling party.
Calling M M 0x84 ADRESS (2..17) The address of the calling party.
Number

Called M M 0x85 ADRESS (2..17) The address of the called party

Number e.g. the number dialled by the
calling sub.
Recording M M 0x89 ADRESS(2..9) The E.164 number of the visited
Entity MSC producing the record.
Incoming O O 0xAA IA5(1..10) The MSC route on which the
ROUTE call originated, usually from the
BSS
Outgoing O O 0xAB IA5(1..10) The route on which the call left
ROUTE the MSC
Location M M 0xAC OCTET(8) The identity of the cell or the
SAC in which the call originated
including the location area code.
Change of O O 0xAD SEQUENCE OF A list of changes in Location
Location ( 23 * n ) Area Code / Cell Identifier each
time-stamped.
Basic service M M 0xAE OCTET(3) Teleservice 'emergency call'.
AOC O O 0xB2 OCTET(4..28) The charge advice parameters
Parameters sent to the MS on call set-up
Change of O O 0xB3 SEQUENCE OF New AOC parameters sent to the
AOC Parms ( 43 * n) MS e.g. as a result of a tariff
switch over, including the time
at which the new set was
applied.
MS M M 0x94 OCTET(2..3) The mobile station classmark
Change of O O 0xB5 OCTET (16 ) A list of changes to the
classmark classmark during the connection
each time-stamped
Event time M M 0x9F OCTET(9) Setup or IAM timestamp from
stamps: O O 81 49 OCTET(9) calling side
O O 0x96 OCTET(9) Seizure of incoming traffic
0x9F channel
C C OCTET(9)
814A Alerting or ACM timestamp
O O OCTET(9) from called side
0x97
0x98 Answer (for successful calls)
Release of traffic channel
Call duration M M 0x99 INTEGER(1..2) The chargeable duration of the
connection for successful calls,
the holding time for call
attempts.

Radio Chan. O - 0x9B ENUMERATED The type of radio traffic channel

Requested (1) (full / half etc.) requested by the
MS.
Radio Chan. O - 0x9C ENUMERATED The type of radio channel used
Used (1) (full or half rate).
Change of O - 0xBD OCTET (14..17 ) A list of changes each time

Rad. Chan. stamped
Guaranteed - O 0x9F ENUMERATED Describes the bit-rate the UMTS
bit rate 46 (1) service shall guarantee to the
user or application. Guaranteed
Bit Rate may be used to
facilitate admission control
based on available resources,
and for resource allocation
within UMTS.
Maximum - O 0x9F ENUMERATED Maximum Bit Rate can be used
bit rate 47 (1) to make code 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 bit-rate
to be defined for applications
able to operate with different
rates (e.g. applications with
adapting codecs).
Speech O - 0x9F OCTET(1) Speech version used for that call
Version Used 32
Speech O - 0x9F OCTET(1) Speech version supported by the
Version 31 MS with highest priority
Supported indicated by MS
Cause for M M 0x9E INTEGER(1) The reason for the release of the
termination connection.
Diagnostics O O 0xBF INTEGER(4) A more detailed reason for the
1F release of the connection.
Sequence no. C C 0x9F INTEGER(1) Partial record sequence number,
21 only present in case of partial
records.
reference 20 between transactions on the
same MS
Record O O 0xBF SET OF (11 * n) A set of network/ manufacturer
extensions 23 specific extensions to the record.

System Type M M 0x9F ENUMERATED This field indicates the use of

3D (1) GERAN, UTRAN (or a value of
unknown). This field is present
when either the UTRAN or
GERAN air-interface is used on
call setup.
MSC C C 0x9F INTEGER(1..2) This field indicates the cic, only
Outgoing 81 26 present in case of outgoing call
Circuit and TDM bear type.
RNC or BSC M M 0x9F OCTET(3) This field indicates the SPC of
Id 81 27 RNC or BSC.
MSC Id or M M 0x9F OCTET(3) This field indicates the SPC of
SPC 81 28 MSC.
Subscriber O O 0x9F OCTET(1) Indicates the category of
Category 81 3E subscriber.
First MCC M M 0x9F OCTET(3) Indicates the MCC and MNC of
MNC 81 40 the network where call is
initiated.
Intermediate O O 0x9F OCTET(3) Indicates the MCC and MNC of
MCC MNC 81 41 the network where call is served
only present after handover.
Last MCC C C 0x9F OCTET(3) Indicates the MCC and MNC of
MNC 81 42 the network where call is served,
Partial O O 0x9F ENUMERATED Indicates the event (time limit
Record Type 45 (1) etc.) that caused the generation
of a partial record.
A.5.3 Mobile Originated Call Forwarding Attempt

If the generation of MOC records is enabled then, 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, as listed in Table A-3.
Table 1.3 MOC, call forwarding record
Record Type M M 0x80 ENUMERATED Mobile originated.

01 64 (1)
Served IMSI M M 0x81 TBCD(3..8) IMSI of the calling party.

Served C C 0x82 TBCD(8) IMEI of the calling ME, if

IMEI available.
Served M M 0x83 ADRESS (2..9) The MSISDN of the forwarding
MSISDN party.
Calling M M 0x84 ADRESS (2..17) The address of the calling party.
Number
Called M M 0x85 ADRESS (2..17) The address of the "forwarded-
Number to" party.
Translated O O 0x86 ADRESS (2..17) The called number after digit
Number translation within the MSC (if
applicable)
Connected O O 0x87 ADRESS (2..17) The number of the connected
Number party if different to the Called
Number
Roaming O O 0x88 ADRESS (2..17) The Mobile Station Roaming
Number Number employed to route this
connection, if applicable
(Roaming Number of C).
Recording M M 0x89 ADRESS (2..9) The E.164 number of the
Entity forwarding MSC
Incoming O O 0xAA IA5(1..10) The MSC route on which the
ROUTE call originated at the forwarding
MSC.
Outgoing O O 0xAB IA5(1..10) The route on which the call left
ROUTE the forwarding MSC
Location O O 0xAC OCTET(8) The identity of the cell or the
SAC in which the call
forwarding including the
location area code.(e.g. cfnry)
Change of O O 0xAD SEQUENCE OF A list of changes in Location
time-stamped.
Basic C C 0xAE OCTET(3) Bearer or tele-service employed,
service not always available e.g. in case
of call forwarding unconditional.
Transparenc C C 0x8F ENUMERATED Only provided for those basic
y Indicator (1) services which may be
employed in both transparent
and non-transparent mode.
Change Of O O 0xB0 SEQUENCE OF A list of changes of basic service
Service ( (18..27) * n) during a connection each time-
stamped.

Supp. C C 0xB1 SEQUENCE OF Supplementary services invoked

Services (16 * n) as a result of this connection.
AOC O O 0xB2 OCTET(4..28) The charge advice parameters

AOC Para ( 43 * n) MS e.g. as a result of a tariff
switch over, including the time
applied.
MS O O 0x94 OCTET(2..3) The mobile station classmark
Classmark classmark during the connection
each time-stamped
stamps: OO OO 81 49 OCTET(9) calling side
C C 0x96 OCTET(9) Seizure of incoming traffic
O O 0x9F channel
OCTET(9)
81 4A Alerting or ACM timestamp
0x97 OCTET(9) from called side
0x98 Answer (for successful calls)
Call M M 0x99 INTEGER(1..2) The chargeable duration of the
duration connection for successful calls,
the holding time of call attempts.
Radio Chan. O - 0x9B ENUMERATED The type of radio traffic channel
MS.
Radio Chan. O 0x9C ENUMERATED The type of radio channel
Used (1) actually used (full or half rate).
Change of O 0xBD OCTET(14..17) A list of changes each time

Radio Chan. stamped
Cause for M M 0x9E INTEGER(1) The reason for the release of the
Diagnostics O O 0xBF INTEGER(4) A more detailed reason for the
1F release of the connection.
reference 20 between transactions on the
same MS

Sequence C C 0x9F INTEGER(1) Partial record sequence number,

no. 21 only present in case of partial
records.
Additional O O 0xBF SEQUENCE(3) Charge/no charge indicator and
Chg. Info 22 additional charging parameters
Record O O 0xBF SET OF (11*n) A set of network/ manufacturer
gsmSCF C C 0x9F ADRESS(2..9) Identifies the CAMEL server
address 24 serving the subscriber.
Service key C C 0x9F INTEGER(1..4) The CAMEL service logic to be
25 applied.
Network C C 0x9F OCTET(1..8) An identifier to correlate
call 26 transactions on the same call
reference taking place in different network
nodes shall be present.
MSC C C 0x9F ADRESS(2..9) This field contains the E.164
Address 27 number assigned to the MSC
that generated the network call
reference.
CAMEL C C 0x9F BOOLEAN(1) Indicates that the CAMEL server
initiated CF 28 initiated call forwarding.
indicator
Default call O O 0x9F ENUMERATED Indicates whether or not a
handling 29 (1) CAMEL call encountered
default call handling. This field
shall be present only if default
call handling has been applied.
Fixed O O 0x9F ENUMERATED Indicates the user data rate
Network 2D (1) applied for the connection in the
User Rate fixed network. Shall only be
present for 2G HSCSD
connections.
Air Interface O O 0x9F ENUMERATED The total Air Interface User Rate
User Rate 2E (1) Requested by the MS at call
Requested setup. Shall only be present for
non-transparent HSCSD
connections.
Speech O 0x9F OCTET(1) Speech version used for that call
Version 32
Used
Speech O 0x9F OCTET(1) Speech version supported by the
Version 31 MS with highest priority

Number of O O 0x9F INTEGER(1) Numbers that counts how often

DP 33 armed detection points (TDP and
encountered EDP) were encountered.
Level of O O 0x9F BIT STRING(2) Indicator of the complexity of
CAMEL 34 the CAMEL feature used.
service
Free format C C 0x9F OCTET(1..160) This field contains data sent by
Data 35 the gsmSCF in the FCI
messages. The data can be sent
either in one FCI message or
several FCI messages with
append indicator.
CAMEL call O O 0xBF SEQUENCE OF Set of CAMEL information IEs.
leg 36 ((104..124) * n) Each of these IEs contains
information information related to one
outgoing CAMEL call leg.
Free format C C 0x9F BOOLEAN(1) Indicator if free format data
data append 37 from this CDR is to be appended
indicator to free format data in previous
partial CDR.
System Type C C 0x9F ENUMERATED This field indicates the use of
3D (1) GERAN, UTRAN (or a value of
forwarding call setup.
Rate O O 0x9F OCTET(1) Present if “rate adaption”
Indication 3E parameters for the basic service
were signalled between the
MS/UE and the network, see TS
24.008. May not always be
available in this CDR type.
Bit Rate may be used to
facilitate admission control
based on available resources,
and for resource allocation
within UMTS.


maximum wanted user bit-rate
to be defined for applications
able to operate with different
rates (e.g. applications with
adapting codecs).
Classmark3 O O 0x9F OCTET(2) May be present when access in
81 0C BSC.
Charged O O 0x9F ENUMERATED Indicates if the calling
Party 81 0D (1) subscriber or the called
subscriber is charged for the call,
or if the call is not charged. May
Original C C 0x9F ADRESS (2..17) The address of original called
Called 81 0E party.
Number
Calling O O 0x9F OCTET(1..3) Indicates the forwarding party
Charge Area 81 11 logical area for distance charge
Code
Called O O 0x9F OCTET(1..3) Indicates the called party logical
Charge Area 81 12 area for distance charge
Code
MSC C C 0x9F INTEGER()1..2 This field indicates the cic, only
Outgoing 81 26 present in case of forwarding
Circuit outgoing call and TDM bear
type.
RNC or C C 0x9F OCTET(3) This field indicates the SPC of
BSC Id 81 27 RNC or BSC of forwarding
subscriber.
SPC 81 28 MSC of forwarding call at
conditional forwarding call.
Call Emlpp O O 0x9F OCTET(1) Indicates the priority of
Priority 81 2A forwarding call. See 24.008
Caller O O 0x9F OCTET(1) Indicates the forwarding
Default 81 2B subscriber’s priority. See 29.002
Emlpp
Priority

Ea C C 0x9F OCTET(3) Indicates the forwarding

Subscriber 81 2E subscriber’s information of
Info Equal Access
Selected C C 0x9F OCTET(3) Indicates the selected code of
CIC 81 2F Carrier identification
Ported flag O O 0x9F ENUMERATED Indicates if forwarding party be
81 34 (1) ported.

ID 81 3C WCDMA
Change Of O O 0xBF SEQUENCE OF A list of changes in CGI / SAI
Global Area 81 3D (22 * n) each time-stamped.
ID
Subscriber C C 0x9F OCTET(1) Indicates the category of
Category 81 3E forwarding subscriber.
First MCC C C 0x9F OCTET(3) Indicates the MCC and MNC of
MNC 81 40 the network where forwarding
call is initiated.
MNC 81 42 the network where call is served
CUG O O 0x9F ENUMERATED Indicates the subscriber with a
Outgoing 81 43 (1) Outgoing Access.
Access
Indicator
Interlock 81 44
Code
CUG O O 0x9F ENUMERATED Indicates caller and called
Outgoing 81 45 (1) whether or not is in the same
Access Used CUG group.
CUG Index O O 0x9F OCTET(2) The CUG index has significance
81 46 only between the subscriber and
network.
Hot billing C C 0x9F INTEGER(1) Indicates the Subscriber is one
tag 81 48 with Hot Billing service.

A.5.4 Mobile Terminated Call Attempt

If the generation of these records is enabled, then 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, as listed in Table A-4.
Table 1.4 MTC record

Record Type M M 0x80 ENUMERATED Mobile Terminated.

01 01 (1)
Served IMSI M M 0x81 TBCD(3..8) IMSI of the called party.
Served IMEI C C 0x82 TBCD(8) IMEI of the called ME.
Served O O 0x83 ADRESS(2..9) The MSISDN of the called party.
MSISDN
Calling C C 0x84 ADRESS(2..17) The number of the calling party
Number if available.
Connected O O 0x85 ADRESS(2..17) Only relevant in case of call
Number forwarding where the
"forwarded-to" number is
recorded.
Recording M M 0x86 ADRESS(2..9) The E.164 number of the visited
Entity (terminating) MSC
Incoming O O 0xA7 IA5(1..10) The MSC route on which the call
ROUTE originated.
Outgoing O O 0xA8 IA5(1..10) The route on which the call left
ROUTE the MSC, usually to the BSS
Location C C 0xA9 OCTET(8) The identity of the cell or the
SAC occupied by the called
party when the call was set up
including the location area code.
Change of O O 0xAA SEQUENCE OF A list of changes in Location
time-stamped.
Basic M M 0xAB OCTET(3) Bearer or teleservice employed
Service
Transparenc C C 0x8C ENUMERATED Only provided for those basic
y Indicator (1) services which may be employed
in both transparent and non-
transparent mode.
Change of O O 0x8D SEQUENCE OF A list of changes of basic service
stamped.

Supp. C C 0xAE SEQUENCE OF Supplementary services invoked

Services (16 * n) as a result of this connection.
AOC O O 0xAF OCTET(4..28) The charge advice parameters

AOC Parms. ( 43 * n) MS e.g. as a result of a tariff
switch-over, including the time
applied.
MS M M 0x91 OCTET(2..3) The mobile station class mark
Classmark
Classmark classmark during the connection
each time-stamped
stamps: OO OO 81 4B OCTET(9) calling side
C C 0x93 OCTET(9) Seizure of traffic channel
O O 0x9F OCTET(9) Alerting or ACM timestamp
81 4C from called side
0x94 OCTET(9)
Answer time for successful calls
0x95 Release of traffic channel
Call M M 0x96 INTEGER(1..2) The chargeable duration of the
duration connection if successful, the
holding time of the call if
unsuccessful.
Radio Chan. O 0x98 ENUMERATED The type of radio traffic channel
MS.
Radio Chan. O 0x99 ENUMERATED The type of radio channel used
Used (1) (full or half rate).
Change of O 0xBA OCTET (14..17 ) A list of changes each time

Rad. Chan stamped
Cause for M M 0x9B INTEGER(1) The reason for the release of the
term. call.
Diagnostics O O 0xBC INTEGER(4) A more detailed reason for the
release of the connection.
Call M M 0x9D OCTET(1..8) A local identifier distinguishing
reference between transactions at the same
MS

Sequence C C 0x9E INTEGER(1) Partial record sequence number,

no. only present in case of partial
records.
Chg. Info 1F additional charging parameters
Record O O 0xBF SET OF (11 * n) A set of network/ manufacturer
Network call C C 0x9F OCTET(1..8) An identifier to correlate
reference 21 transactions on the same call
taking place in different network
MSC C C 0x9F ADRESS(2..9) This field contains the E.164
Address 22 number assigned to the MSC
reference.
Fixed O O 0x9F ENUMERATED Indicates the user data rate
Network 26 (1) applied for the connection in the
User Rate fixed network. Shall only be
present for 2G HSCSD
connections.
Air Interface O O 0x9F ENUMERATED The total Air Interface User Rate
User Rate 27 (1) Requested by the MS at call
Requested setup. Shall only be present for
non-transparent HSCSD
connections.
Speech O 0x9F OCTET(1) Speech version supported by the
Version 2A MS with highest priority
Speech O 0x9F OCTET(1) Speech version used for that call
Version 2B
Used
gsmSCF C C 0x9F ADRESS(2..9) Identifies the CAMEL server
address 2C serving the subscriber.
Service key C C 0x9F INTEGER(1..4) The CAMEL service logic to be
2D applied.
System Type C C 0x9F ENUMERATED This field indicates the use of
2E (1) GERAN, UTRAN (or a value of
call setup.

Rate O O 0x9F OCTET(1) Present if “rate adaption”

Indication 2F parameters for the basic service
were signalled between the
MS/UE and the network, see TS
24.008.
Bit Rate may be used to facilitate
admission control based on
available resources, and for
resource allocation within
UMTS.
maximum wanted user bit-rate to
be defined for applications able
to operate with different rates
(e.g. applications with adapting
codecs).
Initial Call O O 0x9F NULL(0) Indicates if a Initial Call Attempt
Attempt 81 09 call from GsmSCF.
Flag
USSD Call O O 0x9F NULL(0) Indicates if a USSD call back
back Flag 81 0A when a CAMEL subscriber
roams aboard.
Modem O O 0x9F ENUMERATED Indicates the type of Modem
Type 81 0B (1) used.
Classmark3 O O 0x9F OCTET(2) This may be present when access

81 0C in BSC.
Charged O O 0x9F ENUMERATED Indicates if the calling subscriber
Party 81 0D (1) or the called subscriber is
charged for the call, or if the call
is not charged. May be modified
by the SCF.
Original O O 0x9F ADRESS(2..17) The address of original called
Called 81 0E party.
Number

Calling O O 0x9F OCTET(1..3) Indicates the calling party logical

Code
Code
handling 81 16 (1) CAMEL call encountered default
call handling. This field shall be
present only if default call
handling has been applied.
Free format C C 0x9F OCTET(1..160) This field contains data sent by
Data 81 17 the gsmSCF in the FCI
message(s). The data can be sent
either in one FCI message or
several FCI messages with
append indicator.
Free format C C 0x9F BOOLEAN(1) Indicator if free format data from
data append 98 this CDR is to be appended to
indicator free format data in previous
partial CDR.
Number of O O 0x9F INTEGER(1) Numbers that counts how often
DP 81 19 armed detection points (TDP and
encountered EDP) were encountered.
Level of O O 0x9F BIT STRING(2) Indicator for the complexity of
CAMEL 81 1A the CAMEL feature used.
service
Roaming C C 0x9F ADRESS(2..17) The Mobile Station Roaming
Number 81 20 Number employed to route this
connection (Served subscriber’s
Roaming Number).
Incoming 81 26 present in case of incoming call
Circuit and TDM bear type.
RNC or M M 0x9F OCTET(3) This field indicates the SPC of
BSC Id 81 27 RNC or BSC.
SPC 81 28 MSC.
Priority 81 2A 24.008
Called O O 0x9F OCTET(1) Indicates the called subscriber’s
Default 81 2B priority. See 29.002
Emlpp
Priority

Ea O O 0x9F OCTET(3) Indicates the calling subscriber’s

Info
Selected O O 0x9F OCTET(3) Indicates the selected code of
optimalRout - - 0x9F NULL Reserved for the future
ingFlag 81 31
Ported flag O O 0x9F ENUMERATED Indicates if called party be
81 34 (1) ported.

ID 81 3C WCDMA
Change Of O O 0xBF SEQUENCE A list of changes in CGI / SAI
Global Area 81 3D OF (22 * n) each time-stamped.
ID
Subscriber M M 0x9F OCTET(1) Indicates the category of
First MCC M M 0x9F OCTET(3) Indicates the MCC and MNC of
MNC 81 40 the network where call is
initiated.
MNC 81 42 the network where call is served
Outgoing 81 43 (1) Incoming Access.
Access
Indicator
Interlock 81 44
Code
CUG O O 0x9F ENUMERATED Indicates caller and called
Incoming 81 45 (1) whether or not is in the same
Access Used CUG group.
CUG Index O O 0x9F OCTET(2) The CUG index has significance
81 46 only between the subscriber and
network.
Hot billing C C 0x9F INTEGER(1) Indicates the Subscriber is one
tag 81 48 with Hot Billing service.

Redirecting C C 0x9F ADRESS(2..17) The MSISDN of the forwarding

Number 81 49 party.
Redirecting O O 0x9F INTEGER(1) Times of call forwarding.
Counter 81 4A
Called party M M 0x9F ADRESS(2..17) The address of the called party
number 81 4D e.g. the number dialled by the
calling sub.
A.5.5 Roaming Call Attempt

If the generation of these records is enabled then, a roaming record shall be created for each
call redirected to a mobile subscriber roaming outside the HPLMN. These roaming records
shall be produced in the GMSC of the roaming subscriber's HPLMN, as listed in Table A-5.
Table 1.5 Roaming record

Record Type M M 0x80 NUMERATED Roaming record.

01 02 (1)
Served IMSI M M 0x81 TBCD(3..8) IMSI of the called (roaming)
party.
Served O O 0x82 ADRESS(2..9) The MSISDN of the called
MSISDN (roaming) party.
Calling C C 0x83 ADRESS(2..17) The address of the calling party,
Number if available.
Roaming M M 0x84 ADRESS(2..17) The Mobile Station Roaming
Number Number employed to route this
connection.
Recording M M 0x85 ADRESS(2..9) The E.164 number of the GMSC
Entity
Incoming O O 0xA6 IA5(1..10) The GMSC route on which the
ROUTE call originated.
Outgoing O O 0xA7 IA5(1..10) The route on which the call left
ROUTE the GMSC
Basic M M 0xA8 OCTET(3) Bearer or teleservice employed.
service

Transparenc C C 0x89 ENUMERATED Indicates whether the basic

y Indicator (1) 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 non-transparent mode.
Change Of O O 0xAA SEQUENCE OF A list of changes of basic service
stamped.
Supplement C C 0xAB SEQUENCE OF Supplementary services invoked
ary Services (16 * n) as a result of this connection.
This field shall be present when
one or more supplementary
services have been invoked.
Event time C C 0x8C OCTET(9) Seizure time: time of incoming
stamps C C 0x8D OCTET(9) traffic channel seizure (This
timestamp is not supported
O O 0x8E OCTET(9) now.)
Answer time: time of answer
(for successful calls)
Release time: time of traffic
channel release
Call M M 0x8F INTEGER(1..2) The chargeable duration of the
duration connection for successful calls,
the holding time of call attempts.
Cause for M M 0x91 INTEGER(1) The reason for the release of the
Diagnostics O O 0xB2 INTEGER(4) A more detailed reason for the
release of the connection.
Call M M 0x93 OCTET(1..8) A local identifier distinguishing
reference between transactions on the
same MS
Sequence C C 0x94 INTEGER(1) Partial record sequence number,
no. only present in case of partial
records.
Record O O 0xB5 SET OF (11 * n) A set of network/ manufacturer
extensions specific extensions to the record,
when available.
Network C C 0x96 OCTET(1..8) An identifier to correlate
call transactions on the same call
reference taking place in different network

MSC C C 0x97 ADRESS(2..9) This field contains the E.164

Address number assigned to the MSC
reference. Shall be present only
if CAMEL is applied.
Partial O O 0x9E ENUMERATED Indicates the event (time limit
Record Type (1) etc.) that caused the generation
Chg. Info 81 05 additional charging parameters
Party 81 0D (1) subscriber or the called
subscriber is charged for the call,
or if the call is not charged. May
Original O O 0x9F ADRESS(2..17) The address of original called
Called 81 0E party.
Number
Calling O O 0x9F OCTET(1..3) Indicates the calling party
Charge Area 81 11 logical area for distance charge
Code
Code
Outgoing 81 26 present in case of outgoing bear
Circuit type being TDM.
Incoming 81 27 present in case of incoming bear
Circuit type being TDM.
SPC 81 28 MSC.
Priority 81 2A 24.008
Ea O O 0x9F OCTET(3) Indicates the calling subscriber’s
Info
Selected O O 0x9F OCTET(3) Indicates the selected code of
optimalRout - - 0x9F NULL Reserved for the future
ingFlag 81 31

Subscriber O O 0x9F OCTET(1) Indicates the category of

Outgoing 81 43 (1) Outgoing Access.
Access
Indicator
Interlock 81 46
Code
Hot billing C C 0x9F INTEGER(1) Indicates the Subscriber with
tag 81 48 Hot Billing service.
A.5.6 Incoming Gateway Call Attempt

If 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, as listed in Table A-6.
Table 1.6 Incoming gateway record

Record Type M M 0x80 01 ENUMERATED Incoming gateway record

03 (1)
Calling M M 0x81 ADRESS(2..17) The number of the calling
Number party if available at this node.
Called M M 0x82 ADRESS(2..17) The address of the called party
Number as seen by the GMSC. This is
the number employed by the
GMSC for routing.
Recording M M 0x83 ADRESS(2..9) The E.164 number of the
Entity GMSC
Incoming M M 0xA4 IA5(1..10) The incoming GMSC route on
ROUTE which the call originated.
Outgoing M M 0xA5 IA5(1..10) The route on which the call
ROUTE left the GMSC.

Event time M M 0x9F 81 OCTET(9) Setup or IAM timestamp from

stamps: OO O 49 OCTET(9) calling side
CO O 0x86 OCTET(9) Seizure of incoming traffic
0x9F 81 channel
CO OCTET(9)
4A 0x87 Alerting or ACM timestamp
OCTET(9) from called side
0x88
Answer (successful calls only)
Release of incoming trunk
Call M M 0x89 INTEGER(1..2) The accountable duration
duration (answer -> release of
incoming trunk) of the
connection if successful.
Cause for M M 0x8B INTEGER(1) The reason for the release of
term. the connection.
Diagnostics O O 0xAC INTEGER(4) A more detailed reason for the
release of the connection
Call M M 0x8D OCTET(1..8) A local identifier
Reference distinguishing between
transactions.
Sequence C C 0x8E INTEGER(1) Partial record sequence
no. number, if applicable.
Record O O 0xAF SET OF (11 * n) A set of network/
extensions manufacturer specific
extensions to the record.
Partial O O 0x96 ENUMERATED Indicates the event (time limit
Record Type (1) etc.) that caused the generation
ISDN O O 0x97 OCTET(1..12) Present if this parameter is
Bearer signalled back from the
Capability VMSC to the GMSC in the
access transport parameter of
the Answer message (ANM),
see TS 29.007
Low Layer O O 0x98 OCTET(1..18) Present if this parameter is
Compatibilit signaled back from the VMSC
y to the GMSC in the access
transport parameter of the
Answer message (ANM), see
TS 29.007

High Layer O O 0x99 OCTET(1..12) Present if this parameter is

Compatibilit signalled back from the
y VMSC to the GMSC in the
access transport parameter of
the Answer message (ANM),
see TS 29.007
Basic O O 0xBF 81 OCTET(3) Bearer or teleservice
Service 02 employed.
Code
Additional O O 0xBF 81 SEQUENCE(3) Charge/no charge indicator
Chg. Info 05 and additional charging
parameters
Party 810D (1) subscriber or the called
subscriber is charged for the
call, or if the call is not
charged. May be modified by
the SCF.
Original O O 0x9F 81 ADRESS(2..17) The address of original called
Called 0E party.
Number
Rate O O 0x9F 81 OCTET(1) Present if “rate adaption”
Indication 1F parameters for the basic
service were signaled between
the MS/UE and the network,
see TS 24.008.
Roaming C C 0x9F 81 ADRESS(2..17) The Mobile Station Roaming
Number 20 Number employed to route
this connection, if applicable.
MSC C C 0x9F 81 INTEGER(1..2) This field indicates the cic,
Incoming 27 only present in case of
Circuit incoming bear type being
TDM.
MSC Id or M M 0x9F 81 OCTET(3) This field indicates the SPC of
SPC 28 MSC.
Call Emlpp O O 0x9F 81 OCTET(1) Indicates the priority of call.
Priority 2A See 24.008
Ea C C 0x9F 81 OCTET(3) Indicates the calling
Subscriber 2E subscriber’s information of
Info Equal Access
Selected C C 0x9F 81 OCTET(3) Indicates the selected code of
CIC 2F Carrier identification

CUG O O 0x9F 81 ENUMERATED Indicates the subscriber with a

Outgoing 43 (1) Outgoing Access.
Access
Indicator
CUG O O 0x9F 81 COTET(4) Network code + CUG
Interlock 44 interlock
Code
CUG O O 0x9F 81 ENUMERATED Indicates caller and called
Incoming 45 (1) whether or not is in the same
Access Used CUG group
mscIncomin O O 0x9F 81 ENUMERATED msc incoming trunk attribute
gRouteAttri 46 (1)
bute
mscOutgoin O O 0x9F 81 ENUMERATED msc Outgoing trunk attribute
gRouteAttri 47 (1)
bute
Network C C 0x9F 81 OCTET(1..8) An identifier to correlate
reference taking place in different
network nodes shall be
present.
A.5.7 Outgoing Gateway Call Attempt

If 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, as listed
in Table A-7.
Table 1.7 Outgoing gateway record

Record Type M M 0x80 01 ENUMERATED Outgoing gateway record

04 (1)
Number party if available at this node.
Called M M 0x82 ADRESS(2..17) The address of the called
Number party as seen by the GMSC.
This is the number employed
by the GMSC for routing.


Entity GMSC
Incoming M M 0xA4 IA5(1..10) The incoming GMSC route
ROUTE on which the call originated.
ROUTE left the GMSC.
Event time M M 0x9F 81 OCTET(9) Setup or IAM timestamp from
stamps: OO O 49 OCTET(9) calling side
CO O 0x86 OCTET(9) Seizure of incoming traffic
0x9F 81 channel
CO OCTET(9)
0x88
Answer (successful calls
only)
Release of incoming trunk
Call M M 0x89 INTEGER(1..2) The accountable duration
duration (answer -> release of
outgoing trunk) of the
connection if successful.
Cause for M M 0x8B INTEGER(1) The reason for the release of
term. the connection.
Diagnostics O O 0xAC INTEGER(4) A more detailed reason for the
release of the connection
transactions.
Sequence C C 0x8E INTEGER(1) Partial record sequence
Record O O 0xAF SET OF (11*n ) A set of network/
Partial O O 0x96 ENUMERATED Indicates the event (time limit
Record Type (1) etc.) that caused the
generation of a partial record.
Code
parameters

Charged O O 0x9F 81 ENUMERATED Indicates if the calling

charged. May be modified by
the SCF.
Original O O 0x9F 81 ADRESS(2..17) The address of original called
Called 0E party.
Number
service were signalled
between the MS/UE and the
network, see TS 24.008.
Roaming C C 0x9F 81 ADRESS(2..17) The Mobile Station Roaming
Number 20 Number employed to route
this connection, if applicable.
Outgoing 26 only present in case of
Circuit outgoing bear type being
TDM.
MSC Id or M M 0x9F 81 OCTET(3) This field indicates the SPC
SPC 28 of MSC.
Info Equal Access
Selected C C 0x9F 81 OCTET(3) Indicates the selected code of
CIC 2F Carrier identification
CUG O O 0x9F 81 ENUMERATED Indicates the subscriber with a
Outgoing 43 (1) Outgoing Access.
Access
Indicator
CUG O O 0x9F 81 OCTET(4) Network code + CUG
Code
Incoming 45 (1) whether or not is in the same
Access Used CUG group
mscIncomin O O 0x9F 81 ENUMERATED msc incoming trunk attribute
gRouteAttri 46 (1)
bute

mscOutgoin O O 0x9F 81 ENUMERATED msc Outgoing trunk attribute

gRouteAttri 47 (1)
bute
present.
A.5.8 Transit Call Attempt

If generation of these records is enabled then 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, as listed in Table A-8.
Table 1.8 Transit record

Record Type M M 0x80 01 ENUMERATED Transit.

05 (1)
Entity transit MSC
Incoming M M 0xA2 IA5(1..10) The TMSC route on which
ROUTE the call originated.
ROUTE left the TMSC.
Number party if available at this
node.
Called M M 0x85 ADRESS(2..17) The address of the called
Number party as seen by the TMSC.
ISDN Basic O O 0x86 OCTET(1) The ISDN basic service
Service employed

Event time MO M 0x9F 81 OCTET(9) Setup or IAM timestamp

stamps: O OO 49 OCTET(9) from calling side
CO CO 0x87 OCTET(9) Seizure of incoming traffic
0x9F 81 channel
OCTET(9)
0x89
Answer (successful calls
only)
Call M M 0x8A INTEGER(1..2) The chargeable duration of
duration the connection if successful.
Cause for M M 0x8C INTEGER(1) The reason for the release
term. of the connection.
Diagnostics O O 0xAD INTEGER(4) A more detailed reason for
the release of the
connection.
Call O O 0x8E OCTET(1..8) A local identifier
transactions.
Sequence C C 0x8F INTEGER(1) Partial record sequence
Record O O 0xB0 SET OF (11 * n) A set of network/
Partial O O 0x97 ENUMERATED Indicates the event (time
Record Type (1) limit etc.) that caused the
generation of a partial
record.
Code
parameters
Original O O 0x9F 81 ADRESS(2..17) The address of original
Called 0E called party.
Number


Incoming 27 only present in case of
Circuit incoming bear type being
TDM.
Outgoing 26 only present in case of
Circuit outgoing bear type being
TDM.
SPC 28 of MSC.
Info Equal Access
Selected C C 0x9F 81 OCTET(3) Indicates the selected code
CIC 2F of Carrier identification
CUG O O 0x9F 81 ENUMERATED Indicates the subscriber
Outgoing 43 (1) with a Outgoing Access.
Access
Indicator
CUG O O 0x9F 81 OCTET(4) Network code + CUG
Code
Incoming 45 (1) whether or not is in the
Access Used same CUG group
mscIncomin O O 0x9F 81 ENUMERATED msc incoming trunk
gRouteAttri 46 (1) attribute
bute
mscOutgoin O O 0x9F 81 ENUMERATED msc Outgoing trunk
gRouteAttri 47 (1) attribute
bute
call 48 transactions on the same
reference call taking place in different
present.
A.5.9 Short Message Service, Mobile Originated

If enabled, an SMS-MO record shall be produced, within the originating MSC, for each short
message sent by a mobile subscriber, as listed in Table A-9.

Table 1.9 SMS-MO record

Record Type M M 0x80 01 ENUMERATED SMS-Mobile originated.

06 (1)
Served IMSI M M 0x81 TBCD(3..8) The IMSI of the subscriber
sending the short message.
Served O O 0x82 TBCD(8) The IMEI of the ME
IMEI sending the message, if
available.
Served M M 0x83 ADRESS(2..9) The primary MSISDN of
MSISDN the subscriber sending the
message.
MS M M 0x84 OCTET(2..3) The mobile station
Classmark classmark.
Service M M 0x85 ADRESS(2..9) The address (E.164) of the
Centre SMS-service centre.
Entity visited MSC
Location O O 0xA7 OCTET(8) The Location Area Code
and Cell Identifier from
which the message
originated.
Message M M 0x88 OCTET (3..8) A reference, provided by
Reference the MS uniquely
identifying this message.
Event Time M M 0x89 OCTET(9) The time at which the
stamp message was received by
the MSC from the
subscriber.
SMS Result C C 0xAA INTEGER (4) The result of the attempted
delivery if unsuccessful.
Record O O 0xAB SET OF (11 * n) A set of network/
Destination M M 0x8C ADRESS(2..17) The destination short
number message subscriber
number.
CAMEL C C 0xAD SET (34..58) Set of CAMEL information
SMS IEs. Each of these IEs
Information contains information
related to CAMEL call leg
related for the SMS.

System Type M M 0x8E ENUMERATED This field indicates the use

(1) 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.
Code
parameters
Classmark3 O O 0x9F 81 OCTET(2) May be present when
0C access in BSC.
subscriber is charged for
the call, or if the call is not
charged. May be modified
by the SCF.
RNC or M M 0x9F 81 OCTET(3) This field indicates the
BSC Id 27 SPC of RNC or BSC.
MSC Id or M M 0x9F 81 OCTET(3) This field indicates the
SPC 28 SPC of MSC.
Global Area O O 0x9F 81 OCTET(7) Indicates CGI of GSM or
ID 3C SAI of WCDMA
Subscriber M M 0x9F 81 OCTET(1) Indicates the category of
Category 3E subscriber.
First MCC M M 0x9F 81 OCTET(3) Indicates the MCC and
MNC 40 MNC of the network where
sms is initiated.
SMS User C C 0x9F 81 OCTET(1) Indicates the user data type
Data Type 43 such as normal SMS,
picture, text.
SMS Text C C 0x9F 81 OCTET(1..160) Indicates the content of
44 subscriber.(Note1)
Maximum C C 0x9F 81 INTEGER(1) Indicates the maximum of
Number Of 45 the concatenated SMS
SMS In The
Concatenate
d SMS

Concatenate C C 0x9F 81 INTEGER(1..2) Indicates the reference

d SMS 46 number of concatenated
Reference SMS
Number
Sequence C C 0x9F 81 INTEGER(1) Indicates the sequence of
Number Of 47 concatenated sms, such as
The Current 1, 2,…maximum Number
SMS Of SMS In The
Concatenated SMS
Hot billing C C 0x9F 81 INTEGER(1) Indicates the Subscriber
tag 48 with Hot Billing service.
Call M M 0x9F 81 OCTET(1..8) A local identifier
reference 49 distinguishing between
transactions on the same
MS
A.5.10 Short Message Service, Mobile Terminated

If enabled, an SMS-MT record shall be produced, within the terminating MSC, for each short
message received by a mobile subscriber, as listed in Table A-10.
Table 1.10 SMS-MT record

Record Type M M 0x80 01 ENUMERATED SMS-Mobile Terminated.

07 (1)
Service M M 0x81 ADRESS(2..9) The E.164 address of the
Centre SMS service centre.
Served IMSI M M 0x82 TBCD(3..8) The IMSI of the receiving
party.
Served O O 0x83 TBCD(8) The IMEI of the receiving
IMEI party, if available.
Served M M 0x84 ADRESS(2..9) The MSISDN of the
MSISDN receiving party.
Entity visited MSC.
Location O O 0xA7 OCTET(8) The Location Area Code
and Cell Identifier to which
the message was delivered.

Event time M M 0x88 OCTET(9) Delivery time stamp, time

stamp at which message was sent
to the MS by the MSC.
SMS Result C C 0xA9 INTEGER(4) The result of the attempted
delivery if unsuccessful.
Record O O 0xAA SET OF (11 * n) A set of network/
System M M 0x8B ENUMERATED This field indicates the use
Type (1) of GERAN, UTRAN (or a
the UTRAN or GERAN
air-interface is used on call
setup.
CAMEL C C 0xAC SET (34..58) Set of CAMEL information
SMS IEs. Each of these IEs
Information contains information
related to CAMEL call leg
related for the SMS.
Code
parameters
Classmark3 O O 0x9F 81 OCTET(2) May be present when
0C access in BSC.
by the SCF.
SPC 28 SPC of MSC.
ID 3C SAI of WCDMA
Subscriber M M 0x9F 81 OCTET(1) Indicates the category of


sms is terminated.
SMS User C C 0x9F 81 OCTET(1) Indicates the user data type
Data Type 43 such as normal SMS,
picture, text.
SMS Text C C 0x9F 81 OCTET(1..160) Indicates the content of
44 subscriber.(Note1)
Maximum C C 0x9F 81 INTEGER(1) Indicates the maximum of
Number Of 45 the concatenated SMS
SMS In The
Concatenate
d SMS
Concatenate C C 0x9F 81 INTEGER(1..2) Indicates the reference
d SMS 46 number of concatenated
Reference SMS
Number
Sequence C C 0x9F 81 INTEGER(1) Indicates the sequence of
Number Of 47 concatenated SMS ,such as
The Current 1, 2,…maximum Number
SMS OfSMS In The
Concatenated SMS
Origination M M 0x9F 81 ADRESS(2..17) The originating short
number 49 message subscriber
number.
MS
This table is for UAE.
A.5.11 Mobile Terminated Location Request (MT-LR)

If enabled, an LCS-MT record shall be produced, within the visited MSC, for each mobile a
terminated location request is performed for, as listed in Table A-11.

Table 1.11 LCS-MT record

Record Type M M 0x80 01 ENUMERATED LCS-MT record.

17 (1)
Entity visited MSC producing the
record.
LCS Client O O 0x82 ENUMERATED The type of the LCS client
Type (1) that invoked the LR.
LCS Client M M 0xA3 SEQUENCE Further identification of the

Identity (13..29) LCS client .

the LR is invoked for.
Served IMEI O O 0x9F 66 TBCD(8) The IMEI of the calling
party the LR is executed
for if available.
MSISDN subscriber the LR is
invoked for.
Location O O 0xA6 SEQUENCE The type of the location
Type (6..21) request.
LCS QoS O O 0xA7 SEQUENCE QoS of the LR, if available.

(11)
LCS Priority C C 0x88 OCTET(1) Priority of the LR, if
available.
MLC M M 0x89 ADRESS(2..9) The E.164 address of the
Number requesting GMLC.
Event Time M M 0x8A OCTET(9) The time at which the LR
Stamp was received by the MSC.
Measure O O 0x8B INTEGER(1..2) The duration of preceding
Duration the location request.
Notification C C 0x8C ENUMERATED The privacy notification to
To MS User (1) MS user that was
applicable when the LR
was invoked, if available.
Privacy C C 0x8D NULL(0) This parameter indicates if
Override MS privacy was overridden
by the LCS client, if
available.

Location M M 0xAE OCTET(8) The identity of the cell or

the SAC occupied by the
terminated party when the
LCS was applied.
Location O O 0x8F OCTET(1..20) The location estimate for
Estimate the subscriber if contained
in geographic position and
the LR was successful.
Positioning C C 0x90 OCTET(1..33) The positioning method
Data used , if available.
LCS Cause O O 0x91 OCTET(1) The result of the LR if any
failure or partial success
happened as known at the
radio interface.
Cause for M M 0x95 INTEGER(1) The reason for the
Termination termination of the location
service.
Diagnostics C C 0xB2 INTEGER(4) A more detailed
information about the
Cause for Termination if
any failure or partial
success happened.
lcs - - 0x9F 65 OCTET STRING Reserved for the future
Reference (SIZE (1..8))
Number
System Type M M 0x93 ENUMERATED This field indicates the use
(1) of GERAN or UTRAN at
the time of the LCS
request. This field is
present when either the
UTRAN or GERAN air-
interface is used on call
setup.
parameters
by the SCF.

RNC or BSC M M 0x9F 81 OCTET(3) This field indicates the

Id 27 SPC of RNC or BSC.
SPC 28 SPC of MSC.
ID 3C SAI of WCDMA
Subscriber C C 0x9F 81 OCTET(1) Indicates the category of
LCS is initiated.
MS
A.5.12 Mobile originaTed Location Request (MO-LR)

If enabled, an LCS-MO record shall be produced, within the visited MSC, for each mobile an
originated location request is performed for, as listed in Table A-12.
Table 1.12 LCS-MO record

Record Type M M 0x80 01 ENUMERATED LCS-MO record.

18 (1)
record.
Type (1) that invoked the LR, if
available.
Identity (13..29) LCS client, if available.

the LR is invoked for.
Served IMEI O O 0x9F 66 TBCD(8) The IMEI of the calling
for if available.


MSISDN subscriber the LR is
invoked for.
MOLR Type O O 0x86 INTEGER(1) The type of the LR.
LCS QoS C C 0xA7 SEQUENCE(11) QoS of the LR, if available.
LCS Priority M M 0x88 OCTET(1) Priority of the LR, if
available.
MLC M M 0x89 ADRESS(2..9) The E.164 address of the
Number involved GMLC, if
available.
Event Time M M 0x8A OCTET(9) The time at which the LR
Measure O O 0x8B INTEGER(1..2) The duration of proceeding
Duration the location request .
Location M M 0x8C OCTET(8) The identity of the cell or
originating party when the
LCS was applied.
Location O O 0xAD OCTET(1..20) The location estimate for
Positioning C C 0x8E OCTET(1..33) The positioning method
Data used, if available.
LCS Cause C C 0x8F OCTET(1) The result of the LR if any
radio interface.
service.
Diagnostics C C 0xB0 INTEGER(4) A more detailed
information about the
Cause for Termination if
any failure or partial
success happened.

System Type M M 0x92 ENUMERATED This field indicates the use

(1) of GERAN or UTRAN at
the time of the LCS
UTRAN or GERAN air-
setup.
Number
parameters
by the SCF.
SPC 28 SPC of MSC.
ID 2C SAI of WCDMA
LCS is initiated.
MS

A.5.13 Network Induced Location Request (NI-LR)

If 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, as listed in
Table A-13.
Table 1.13 LCS-NI record

Record Type M M 0x80 01 ENUMERATED LCS-NI record.

19 (1)
record.
Type (1) that invoked the LR, if
available.
Identity (13..29) LCS client, if available.
Served IMSI M M 0x84 TBCD(3..8) The IMSI of the calling

for if supplied by the UE.
Served M M 0x85 ADRESS(2..9) The MSISDN of the calling
MSISDN party the LR is executed
for if supplied by the UE.
Served IMEI O O 0x86 TBCD(8) The IMEI of the calling
for if available.
EMS-Digits O O 0x87 ADRESS(2..9) The emergency service
routing digits, if emergency
call.
EMS-Key O O 0x88 ADRESS(2..9) The emergency service
routing key, if emergency
call.
LCS QoS O O 0xA9 SEQUENCE(11) QoS of the LR, if available.
LCS Priority C C 0x8A OCTET(1) Priority of the LR, if
available.
MLC M M 0x8B ADRESS(2..9) The E.164 address of the
Number involved GMLC, if
available.
Event Time M M 0x8C OCTET(9) The time at which the LR

Measure O O 0x8D INTEGER(1..2) The duration of proceeding

Duration the location request .
Location M M 0xAE OCTET(8) The identity of the cell or
terminated party when the
LCS was applied.
Location O O 0x8F OCTET(1..20) The location estimate for
Positioning C C 0x90 OCTET(1..33) The positioning method
Data used, if available.
LCS Cause C C 0x91 OCTET(1) The result of the LR if any
radio interface.
service.
Diagnostics C C 0xB2 INTEGER(4) More detailed information
about the Cause for
Termination if any failure
or partial success
happened.
System Type M M 0x93 INTEGER(1) This field indicates the use
of GERAN or UTRAN at
the time of the LCS
UTRAN or GERAN air-
setup.
Number
parameters


by the SCF.
RNC or BSC M M 0x9F 81 OCTET(3) This field indicates the
Id 27 SPC of RNC or BSC.
SPC 28 SPC of MSC.
ID 3C SAI of WCDMA
LCS is initiated.
MS
A.5.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 tele-services 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,
as listed in Table A-14.

Table 1.14 SS-action record

Record M M 0x80 01 ENUMERATED Supplementary service

Type 0A (1) action.
Served M M 0x81 TBCD(3..8) The IMSI of the MS

IMSI performing the action.
Served O O 0x82 TBCD(8) The IMEI of the ME
IMEI performing the action.
Served M M 0x83 ADRESS(2..9) The primary MSISDN of
MSISDN the party performing the
action.
Entity visited MSC / HLR.
Location O O 0xA6 OCTET(8) The identity of the cell or
the SAC, including the
location area code, from
which the request
originated.
Basic C C 0xA7 OCTET(3) The basic service group(s)
Services to which the supplementary
service applies. This field is
not provided if the action
applies to all basic services.
Supplement C C 0x88 OCTET(1) The supplementary service
ary Service or group of supplementary
services for which the
request was made. May not
be available in case of
USSD.
SS Action C C 0x89 ENUMERATED Activation, deactivation,
(1) interrogation etc. May not
be available in case of
USSD.
SS Action M M 0x8A OCTET(9) The time at which the action
time stamp was requested.
SS C C 0xAB OCTET STRING Service dependent
Parameters (7..53) parameters or unstructured
supplementary service data,
if defined for the SS action
recorded in this CDR.

SS Action O O 0xAC INTEGER(4) A more detailed reason for

Result the release of the
connection.
transactions at the same MS.
Record O O 0xAE SET OF (11 * n) A set of network/
extensions to the record,
when available.
System M M 0x8F ENUMERATED This field is present when
Type (1) either the UTRAN or
GERAN air-interface is
used. It is omitted when the
service is provided by a
GSM air interface
USSD O O 0x9F 7E OCTET(1) In the case of USSD,
Coding indicates coding scheme of
Scheme USSD
USSD O O 0xBF 7F OCTET(1..40) In the case of USSD,
String indicates subscriber input
USSD O O 0x9F 81 INTEGER(1) In the case of USSD,
Notify 00 indicates the times of notify
Counter procedure
USSD O O 0x9F 81 INTEGER(1) In the case of USSD,
Request 01 indicates the times of
Counter request procedure
parameters
Classmark3 O O 0x9F 81 OCTET(2) May be present when access
0C in BSC.
by the SCF.
RNC or M M 0x9F 81 OCTET(3) This field indicates the SPC
BSC Id 27 of RNC or BSC.
SPC 28 of MSC.


ID 3C SAI of WCDMA
SS action is initiated.
A.5.15 HLR Interrogation

If enabled, a 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, as listed in Table A-15.
Table 1.15 HLR interrogation record

Record M M 0x80 01 ENUMERATED HLR interrogation.

Type 0B (1)
Served C C 0x81 TBCD(3..8) The IMSI of the party being
IMSI interrogated, if successful
MSISDN subscriber being
interrogated.
Recording M M 0x83 ADRESS(2..9) The E.164 Number of the
Entity HLR / MSC.
Basic O O 0xA4 OCTET(3) Only for teleservice 21
Service (SMS-MT).
Routing C C 0xA5 ADRESS(2..17) Routing number (MSRN,
Number forwarding no.) provided by
the HLR if the interrogation
was successful.
Interrogatio M M 0x86 OCTET(9) Time at which the
n time interrogation was invoked.
stamp
Number of C C 0x87 INTEGER(1) The number of times the
Forwarding call has been forwarded if
provided by ISUP.

interrogatio O O 0x87 INTEGER(4) A more detailed reason for

n Result the release of the
connection.
Record O O 0xA9 SET OF (11 * n) A set of network/
when available.
SPC 28 of MSC.
transactions on the same MS
A.5.16 Common Equipment Usage Record

If enabled, a common equipment usage record shall be created in the VMSC to record the
usage (duration) of common equipment, e.g. conference circuits, employed by a mobile
subscriber, as listed in Table A-16.
Table 1.16 Common equipment usage record

Record M M 0x80 01 ENUMERATED Common equipment usage

Type 0E (1) record.
Equipment M M 0x81 INTEGER(1) e.g. Conference circuit.

type
Equipment C C 0x82 INTEGER(1) The local id. Of the
Id. equipment employed.
Served M M 0x83 TBCD(3..8) The IMSI of the party
IMSI responsible for the seizure
of the equipment..
Served C C 0x9F 66 TBCD(8) IMEI of the calling ME, if
IMEI available.
Served O O 0x84 ADRESS(2..9) The primary MSISDN of
MSISDN the served party..
Entity MSC in which the
equipment is located.
Basic C C 0xA6 OCTET(3) Bearer or teleservice
service employed, if appropriate.

Change Of O O 0xA7 SEQUENCE OF A list of changes of basic

Service ( (18..27) * n) service during a connection
each time-stamped.
Supp. C C 0xA8 SEQUENCE OF Supplementary services
Services (16 * n) invoked in connection with
this equipment.
Event Time M M 0x89 OCTET(9) Seizure time: the time at
Stamp O O 0x8A which the equipment was
seized.
Release time: the time at
which the equipment was
released.
Call M M 0x8B INTEGER(1..2) The total duration of the
Duration usage of the equipment.
Call M M 0x8C OCTET(1..8) A local identifier
transactions.
Sequence C C 0x8D INTEGER(1) Partial record sequence
no. number if applicable.
Record O O 0xAE SET OF (11 * n) A set of network/
when available.
System M M 0x8F ENUMERATED This field indicates the use
Type (1) of GERAN, UTRAN (or a
the UTRAN or GERAN air-
setup.
Rate O O 0x90 OCTET(1) Present if "rate adaption"
Adaptation parameters for the basic
Fixed O O 0x91 ENUMERATED Indicates the user data rate
Network (1) applied for the connection in
User Rate the fixed network. Shall
only be present for 2G
HSCSD connections and for
UMTS data connections.
Partial O O 0x92 ENUMERATED Indicates the event (time
Record (1) limit etc.) that caused the
Type generation of a partial
record.

Cause for M M 0x9F 64 INTEGER(1) The reason for the release of

termination the connection.
Diagnostics O O 0xBF 65 INTEGER(4) A more detailed reason for
the release of the
connection.
parameters
RNC or M M 0x9F 81 OCTET(3) This field indicates the SPC
BSC Id 27 of RNC or BSC.
SPC 28 of MSC.
A.5.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, as listed in Table A-17.
Table 1.17 Terminating CAMEL record

Record M M 0x80 01 ENUMERATED Terminating CAMEL

Type 11 (1) interrogation.
Served M M 0x81 TBCD(3..8) IMSI of the called party

IMSI
Served O O 0x82 ADRESS(2..9) The MSISDN of the called
MSISDN party.
Entity GMSC.
Interrogatio M M 0x84 OCTET(9) Time at which the
n time interrogation was invoked.
stamp

CAMEL M M 0x85 ADRESS(2..17) The number available for

Destination routing after the CAMEL
Number server enquiry.
GsmSCF M M 0x86 ADRESS(2..9) The CAMEL server serving
Address the subscriber.
Service key M M 0x87 INTEGER(1..4) The CAMEL service logic
to be applied.
Network M M 0x88 OCTET(1..8) An identifier to correlate
call transactions on the same call
network nodes.
MSC M M 0x89 ADRESS(2..9) This field contains the
Address E.164 number assigned to
the MSC that generated the
network call reference.
Default call O O 0x8A ENUMERATED Indicates whether or not a
handling (1) CAMEL call encountered
default call handling. This
field shall be present only if
default call handling has
been applied.
Record O O 0xAB SET OF(11 * n) A set of network/
when available.
Called M M 0x8C ADRESS(2..17) The address of the called
Number party as received by the
GMSC/gsmSSF.
Calling C C 0x8D ADRESS(2..17) The address of the calling
Number party, if available.
Incoming O O 0xAE IA5(1..10) The GMSC route on which
ROUTE the call originated. If
available in 3G, this
parameter shall be supplied.
Outgoing O O 0xAF IA5(1..10) The route on which the call
ROUTE left the GMSC. If available
in 3G, this parameter shall
be supplied.

Event time C C 0x90 OCTET(9) Seizure time: time of

stamps: C C 0x91 OCTET(9) incoming traffic channel
seizure (This timestamp is
O O 0x92 OCTET(9) not supported now.)
Answer time: time of
answer (for successful calls)
Release time: time of traffic
channel release
Call M M 0x93 INTEGER(1..2) The chargeable duration of
duration the connection for
successful calls, the holding
time of call attempts.
Cause for M M 0x95 INTEGER(1) The reason for the release of
termination the connection.
Diagnostics O O 0xB6 INTEGER(4) A more detailed reason for
the release of the
connection.
Call M M 0x97 OCTET(1..8) A local identifier
reference distinguishing between
transactions on the same MS
Sequence C C 0x98 INTEGER(1) Partial record sequence
no. number, only present in case
of partial records.
Number of O O 0x99 INTEGER(1) Numbers that counts how
DP often armed detection points
encountered (TDP and EDP) were
encountered.
Level of O O 0x9A BIT STRING(2) Indicator of the complexity
CAMEL of the CAMEL feature used.
service
Free format C C 0x9B OCTET(1..160) This field contains data sent
Data by the gsmSCF in the
Furnish Charging
Information (FCI)
message(s). The data can be
sent either in one FCI
message or several FCI
messages with append
indicator.
CAMEL C C 0xBC SEQUENCE OF Set of CAMEL information
call leg ((104..124) * n) IEs. Each of these Ies
information contains information related
to one outgoing CAMEL
call leg.

Free format C C 0x9D BOOLEAN(1) Indicator if free format data

data append from this CDR is to be
indicator appended to free format data
in previous partial CDR.
MSC server C C 0x9E BOOLEAN(1) Indication if the CAMEL
indication call handling is active in the
MSC server.
handling 2 0x1F (1) CAMEL call encountered
default call handling for 2nd
service such as dialled
service. This field shall be
present only if default call
handling has been applied.
GsmSCF C C 0x9F 20 ADRESS(2..9) Identifies the CAMEL
address 2 server serving the subscriber
for 2nd service such as
dialled service. Shall be
present only if CAMEL is
applied for 2nd service.
Service key C C 0x9F 21 INTEGER(1..4) The CAMEL service logic
2 to be applied for 2nd service
such as dialled service.
Shall be present only if
CAMEL is applied for 2nd
service.
Free format C C 0x9F 22 OCTET(1..160) This field contains data sent
Data 2 by the gsmSCF in the FCI
message(s) for 2nd service
such as dialled service. 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
for 2nd service.
Free format C C 0x9F 23 BOOLEAN(1) Indicator if free format data
data append for 2nd service from this
indicator 2 CDR is to be appended to
free format data in previous
partial CDR. Shall be
present only if CAMEL is
applied for 2nd service.
Partial O O 0x9F 2A ENUMERATED Indicates the event (time
Record (1) limit etc.) that caused the
Type generation of a partial
record.


Code
parameters
by the SCF.
Original O O 0x9F 81 ADRESS(2..17) The address of original
Called 0E called party.
Number
SPC 28 of MSC.
Subscriber O O 0x9F 81 OCTET(1) Indicates the category of
A.5.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, as listed
in Table A-18.
Table 1.18 IMEI ticket

Served M M 0x80 TBCD(8) IMEI of the observed

IMEI mobile equipment
IMEI Status M M 0x81 ENUMERATED The result of the IMEI
(1) check e.g. blacklisted,
greylisted, unknown.

Served M M 0x82 TBCD(3..8) The IMSI of the subscriber

IMSI currently using the mobile
equipment.
Served C C 0x83 ADRESS(2..9) The MSISDN of the
MSISDN subscriber 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
Entity recording MSC.
Event Time M M 0x85 OCTET(9) The time at which the IMEI
Stamp check was performed.
Location M M 0xA6 OCTET(8) The location area code and
cell identity of the cell from
which the mobile equipment
was used.
IMEI Check O O 0x87 INTEGER(1) The event that caused IMEI
Event checking to take place
Call O O 0x88 OCTET(1..8) Only available if the IMEI
Reference check was related to an
MOC or MTC
Record O O 0xA9 SET OF (11 * n) A set of network/
when available.
SPC 28 of MSC.
A.6 Description of Record Fields

This clause contains a brief description of each field of the CDRs described in the previous
clause
A.6.1 Additional Charging Information

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.
ChargeIndicator ::= INTEGER

{
noIndication (0),
noCharge (1),
charge (2)
}
A.6.2 Aiur Requested

The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for
non-transparent HSCSD connections.
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 (1),
aiur38400BitsPerSecond1 (9),
aiur38400BitsPerSecond4 (12)
}

A.6.3 AoC Parameters/Change of AoC Parameters

The AoC parameter 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.
The AoC parameters are defined in TS 22.024 .
AOCParameters ::= SEQUENCE

{
--
-- See TS 22.024.
--
e1 [1] EParameter OPTIONAL,
e7 [7] EParameter OPTIONAL
}
A.6.4 Basic Service/Change of Service/ISDN Basic Service

The basic service 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.
The change of service field is optional and may be omitted if partial records are created
whenever the basic service is changed.
The coding of basic services is defined in detail in TS 29.002.
In the case of the transit record the GSM basic service employed is generally not available.
However, if the device on which the call originates/terminates is connected via ISDN digital
subscriber signalling then the appropriate ISDN basic service code may be recorded in the
record. One possible example includes the direct connection of an ISDN PABX to an
MSC/VLR.
BasicServiceCode ::= CHOICE

{

bearerService [2] BearerServiceCode,

teleservice [3] TeleserviceCode
}
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 (0x20),
-- shortMessageMT-PP (0x21),
-- shortMessageMO-PP (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 (0xd0),
-- plmn-specificTS-1 (0xd1),
-- plmn-specificTS-A (0xda),
-- plmn-specificTS-B (0xdb),
-- plmn-specificTS-C (0xdc),
-- plmn-specificTS-D (0xdd),
-- plmn-specificTS-E (0xde),
-- plmn-specificTS-F (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.


--
-- 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-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-1200-75bps (0x23),

-- general-padAccessCA (0x27),
--
-- allDataPDS-Services (0x28),
-- dataPDS-2400bps (0x2c),
-- dataPDS-4800bps (0x2d),
-- dataPDS-9600bps (0x2e),
-- general-dataPDS (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


--
-- allPLMN-specificBS (0xd0),
-- plmn-specificBS-1 (0xd1),
-- plmn-specificBS-A (0xda),
-- plmn-specificBS-B (0xdb),
-- plmn-specificBS-C (0xdc),
-- plmn-specificBS-D (0xdd),
-- plmn-specificBS-E (0xde),
-- plmn-specificBS-F (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
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
A.6.5 Call Duration

This field contains the relevant call duration in seconds. For incomplete calls (call attempts)
the relevant duration is the call holding time from the seizure to the release of the traffic
channel. For complete (answered) calls this 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.
It should be noted that the time stamps may be expressed in terms of tenths of seconds or even
milliseconds and, as a result, the calculation of the call duration may result in the rounding or
truncation of the measured duration to a whole number of seconds.
TimeStamp ::= OCTET STRING (SIZE(9))
--
-- 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
--
Whether or not rounding or truncation is to be used is considered to be outside the scope of
the present document subject to the following restrictions:

 A call duration of zero seconds shall not be accepted.

 The same method of truncation/rounding shall be applied to both single and partial
records.
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. If a call leg does not reach answer status and attempt charging is enabled a
'CAMELInformation' module containing the holding time is generated.
An example of how to use the call duration and the timestamps is given in figure 1. 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 t4 to t6 (period ). The call duration measurement of the
second outleg is started with t9 and ended with t10 (interval ).
Since the last outgoing leg is not answered, the respective module contains the holding time
starting with t11 and ending with t13 (period ).
(The timestamps t1, t2, t3, t7, t8 and t12 are mentioned for completion reasons only.)
Figure 1.2 Figure 1
inc. leg 

outg. leg 1
outg. leg 2 

outg. leg 3
time
t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13
call duration of incoming leg =

call duration of outgoing leg =
holding time of outgoing leg =
Point in time Signalling message sent/received Duration logging

trigger detection point encountered
t1 SETUP; TDP(control)
t2 IAM seizure of outg. leg 1
t3 ACM
t4 ANSWER start of call duration (outg.
leg 1)
t5 CONNECT start of call duration (inc.
leg)

Point in time Signalling message sent/received Duration logging

trigger detection point encountered
t6 RELEASE; EDP(control) stop of call duration (outg.

leg 1)
t8 ACM
t9 ANSWER start of call duration (outg.
leg 2)
t10 RELEASE; EDP(control) stop of call duration (outg.
leg 2)
start of holding time (outg.
leg 3)
t12 ACM
t13 RELEASE; EDP(control) stop of holding time (outg.
leg 3)
A.6.6 Call Reference

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.
CallReference ::= OCTET STRING (SIZE (1..8)).
A.6.7 Calling/Called/Connected/Translated Number

In general an ITU-T Recomendation E.164 number but may also include other numbering
plans e.g. ITU-T Recommendation X.121. Each of these fields includes the type of number
and number plan as specified in detail in TS 24.008 . Where appropriate, these fields may also
contain the presentation and screening information also specified in TS 24.008 .
The called number is the number received from the mobile station on mobile originated call
set-up as defined in TS 24.008 . Similarly, the calling number is the number received from the
network on mobile terminated call set-up. 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. This
parameter is not included in the CDR if no digit translation has taken place.
The connected number is the number of the actual party reached as defined in 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 signalling 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 dialling codes and service
numbers.
This type contains the binary coded decimal representation of a directory number e.g.
calling/called/connected/translated number. The encoding of the octet string is in accordance
with the elements "Calling party BCD number", "Called party BCD number" and "Connected
number" defined in TS 24.008. This encoding includes type of number(international, national,
subscriber number, or Unknown) and number plan information together with a BCD encoded
digit string. It may also contain both a presentation and screening indicator(octet 3a).For the
avoidance of doubt, this field does not include octets 1 and 2, the element name and length, as
this would be redundant..
-- This type is used to represent a number for addressing

-- purposes. It is composed of
-- a) one octet for nature of address, and numbering plan
-- indicator.
-- b) digits of an address encoded as TBCD-String.
-- a) The first octet includes a one bit extension indicator, a

-- 3 bits nature of address indicator and a 4 bits numbering
-- plan indicator, encoded as follows:
-- bit 8: 1 (no extension)
-- bits 765: nature of address indicator

-- 000 unknown

-- 001 international number

-- 010 national significant number
-- 011 network specific number
-- 100 subscriber number
-- 101 reserved
-- 110 abbreviated number
-- 111 reserved for extension
-- bits 4321: numbering plan indicator

-- 0000 unknown
-- 0001 ISDN/Telephony Numbering Plan (Rec CCITT E.164)
-- 0010 spare
-- 0011 data numbering plan (CCITT Rec X.121)
-- 0100 telex numbering plan (CCITT Rec F.69)
-- 0101 spare
-- 0110 land mobile numbering plan (CCITT Rec E.212)
-- 0111 spare
-- 1000 national numbering plan
-- 1001 private numbering plan
-- all other values are reserved.
-- b) The following octets representing digits of an address

-- encoded as a TBCD-STRING.
A.6.8 Calling Party Number

This field contains Calling Party Number modified by CAMEL service.
See Calling/called/connected/translated number above.
A.6.9 CAMEL Call Leg Information

This field contains a set of CAMEL information IEs according to the number of outgoing
CAMEL call legs.
More detail information see below CAMEL Information

A.6.10 CAMEL Information

This field contains a list of parameters with information related to one CAMEL outgoing call
leg. This parameter list is an Information Element (IE) used in the CAMEL Call Leg
Information field.
As a network option, parameters that are identical to the corresponding values in the top level
structure of the record are not recorded again. That means whenever a value is not mentioned
in this set the value provided in the basic record is valid instead. This might lead to an empty
or even absent structure, if no parameter was modified.
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,
cAMELInitCFIndicator [10] CAMELInitCFIndicator OPTIONAL,
causeForTerm [11] CauseForTerm OPTIONAL,
cAMELModification [12] ChangedParameters OPTIONAL,
freeFormatData [13] FreeFormatData OPTIONAL,
diagnostics [14] Diagnostics OPTIONAL,
freeFormatDataAppend [15] BOOLEAN OPTIONAL,
freeFormatData-2 [16] FreeFormatData OPTIONAL,
freeFormatDataAppend-2 [17] BOOLEAN OPTIONAL
}
A.6.11 CAMEL Initiated CF Indicator

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 changing the call destination. 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)
}
A.6.12 CAMEL Modified Service Center

This field contains SMS-C address modified by CAMEL service. If this field is present the
field Service Centre contain SMS-C address before CAMEL modification.
See Calling/called/connected/translated number
A.6.13 CAMEL SMS Information

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. (NOTE 1 This field is only applicable for originated SMS)
CAMEL Destination Subscriber Number: This field contains short message Destination
Number modified by CAMEL service. (NOTE 2 This field is only applicable for originated
SMS)
SMS Reference Number: This field contains the SMS Reference Number assigned to the
Short Message by the MSC.
CAMELSMSInformation ::= SET
{
gsm-SCFAddress [1] Gsm-SCFAddress OPTIONAL,
serviceKey [2] ServiceKey OPTIONAL,
defaultSMSHandling [3] DefaultSMS-Handling OPTIONAL,
callingPartyNumber [5] CallingNumber OPTIONAL,

destinationSubscriberNumber [6] CalledNumber OPTIONAL,

cAMELSMSCAddress [7] AddressString OPTIONAL,
smsReferenceNumber [8] CallReferenceNumber OPTIONAL
}
A.6.14 Category
Subscriber category will be stored by inserting subscribe data by HLR when 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
A.6.15 Cause for Termination

This field contains a generalised 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;

- unathorized client requesting a location service;

- position method failure at a location service execution;
- unknown or unreachable LCS client at a location service request.
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),
unauthorizedRequestingNetwork (52),
unauthorizedLCSClient (53),
positionMethodFailure (54),
unknownOrUnreachableLCSClient (58)
}
A more detailed reason may be found in the diagnostics field.
A.6.16 Default Call/SMS Handling

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)
}

A.6.17 Destination Subscriber Number

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.
A.6.18 Diagnostics
This field includes 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 ;
- a LCS diagnostics according TS 29.002.
The diagnostics may also be extended to include manufacturer and network specific
information.
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)

A.6.19 EMS-Digits
This parameter only applies to location for an emergency services call in North America and
gives the North American Emergency Services Routing Digits.as defined in TS 29.002.
emsDigits ISDN-AddressString,
A.6.20 EMS-Key
This parameter only applies to location for an emergency services call in North America and
gives the North American Emergency Services Routing Key as defined in TS 29.002.
emsKey ISDN-AddressString,
Service category
Bit 1 Police
Bit 2 Ambulance
Bit 3 Fire Brigade
Bit 4 Marine Guard
Bit 5 Mountain Rescue
A.6.21 Entity Number

This field contains the ITU-T Recommendation E.164 number assigned to the entity (MSC,
VLR, HLR etc.) that produced the record. For further details concerning the structure of MSC
and location register numbers see TS 23.003 .
A.6.22 Equipment ID
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.
EquipmentId ::= INTEGER
A.6.23 Equipment Type

This field contains the type of common equipment employed e.g. conference circuit for multi-
party service.
EquipmentType ::= INTEGER

{
conferenceBridge (0)
}

A.6.24 Event Time Stamps

--
-- where
These fields contain the event time stamps relevant for 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 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. However, if the subscriber has subscribed to the advice of charge charging level
service, then the answer time shall be derived from the time at which the FACILITY message
is received from the MS containing the acknowledgement of receipt of the AOC parameters.
Similarly, if the AOC parameters are changed during the call then the change time recorded
for a subscriber with AOC charging level is the receipt of the FACILITY message from the
MS. For a subscriber with AOC information level the change time recorded is the time at
which the FACILITY is sent to the MS.
Finally, 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.
For unsuccessful call attempts the Setup time is mandatory. The Release time is optional and
the call duration recorded is the call holding time i.e. the difference between the two or is
filled with zero fixed (The filling can be configured by software function parameter).
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.
The event records include the following time stamps:
- HLR-int time: The receipt of a MAP_SEND_ROUTING_INFO 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.
- LCS: The time the LR was processed.
It should be noted that the events listed above are only examples in order to demonstrate the
principles and that the list is by no means exhaustive.
All time-stamps include a minimum of date, hour, minute and second.
A.6.25 Fixed Network User Rate

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)
}
A.6.26 Free Format Data

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))
A.6.27 Free Format Data Append Indicator

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 postprocessing 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.
freeFormatDataAppend BOOLEAN
A.6.28 Guaranteed Bit Rate

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 Guaranteed Bit Rate may be used to facilitate admission control based on
available resources, and for resource allocation within UMTS. The bit-rate of the UMTS
bearer service shall guarantee to the user or applications refer 3GPP TS 22.002 .
Operator may choose any of the possible values less or equal to wanted AIUR (Air Interface
User Rate).
(If WAIUR is less or equal to 14,4 kbit/s then Guaranteed Bit Rate and Maximum Bit Rate
shall be set to 14,4 kbit/s).
GuaranteedBitRate ::= ENUMERATED
{
gBR14400BitsPerSecond (1), -- BS20 non-transparent
gBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
-- BS30 transparent and multimedia
gBR32000BitsPerSecond (3), -- BS30 multimedia
gBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
gBR12200BitsPerSecond (106), -- AMR speech

gBR4750BitsPerSecond (113) -- AMR speech
}
A.6.29 GsmSCF Address

This field identifies the CAMEL server serving the subscriber. Address is defined in HLR as
part of CAMEL subscription information.

See Calling/called/connected/translated number.
A.6.30 Interrogation result

This field contains the result of the HLR interrogation attempt as defined in the MAP
(TS 29.002 ).
NOTE: This field is only provided if the attempted interrogation was unsuccessful.
A.6.31 IMEI Check Event

This field identifies the type of event that caused 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)
}
A.6.32 IMEI Status

This field contains the result of the IMEI checking procedure:
- Greylisted;
- Blacklisted;
- Non-whitelisted.
IMEIStatus ::= ENUMERATED
{
greyListedMobileEquipment (0),
blackListedMobileEquipment (1),
nonWhiteListedMobileEquipment (2)

A.6.33 Incoming/Outgoing Route

The incoming route describes the route on which the call originates as seen from the MSC.
For mobile originated calls this will generally be a BSS trunk or RNS route. Similarly, the
outgoing route describes the route on which the call leaves the MSC.
ROUTE ::= CHOICE

{
rOUTENumber [0] INTEGER,
rOUTEName [1] GraphicString
}
maximum ROUTE name is 10 characters.
A.6.34 LCS Cause

The LCS Cause parameter provides the reason for an unsuccessful location request according
TS 49.031.
LCSCause ::= OCTET STRING (SIZE(1))

--
A.6.35 LCS Client Identity

This field contains further information on the LCS Client identity:
- Client External ID.
- Client Dialled by MS ID.
- Client Internal ID.
LCSClientIdentity ::= SEQUENCE
{
lcsClientExternalID [0] LCSClientExternalID OPTIONAL,
lcsClientDialedByMS [1] AddressString OPTIONAL,
lcsClientInternalID [2] LCSClientInternalID 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)
}
A.6.36 LCS Client Type

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)
}
A.6.37 LCS Priority

This parameter gives 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
A.6.38 LCS QoS

This information element defines the Quality of Service for a location request as defined in
TS 49.031 .
LCSQoSInfo ::= SEQUENCE
{
horizontal-accuracy [0] Horizontal-Accuracy OPTIONAL,
verticalCoordinateRequest [1] NULL OPTIONAL,
vertical-accuracy [2] Vertical-Accuracy OPTIONAL,

responseTime [3] ResponseTime OPTIONAL

}
A.6.39 Level of CAMEL Service

This field describes briefly the complexity of CAMEL invocation.
- 'Basic' means that CAMEL feature is invoked during the setup phase (e.g. to modify the
destination) of the call only.
- 'Online charging' means that CAMEL supported AoC parameter were sent to the mobile
station (the Send Charging Information message, SCI, is received from the gsmSCF).
- The flag '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)
}
A.6.40 Location/Change of Location

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 including the time at which the change took place.
The change of location field is optional and not required if partial records are generated when
the location changes.
The LAC and CI are both 2 octet quantities and 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 ::= OCTET STRING (SIZE(2))
CellId ::= OCTET STRING (SIZE(2))

--
-- Coded according to TS 24.008
--
A.6.41 Location Estimate

The Location Estimate field is providing 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
A.6.42 Location Type

This field contains the type of the location as defined in TS 29.002.
LocationType ::= SEQUENCE
{
locationEstimateType [0] LocationEstimateType,
deferredLocationEventType [1] DeferredLocationEventType OPTIONAL
}
A.6.43 Maximum Bit Rate

This field contains the Maximum Bit Rate based on the FNUR (Fixed Network User Rate) for
transparent and WAIUR( Wanted Air Interface User Rate) for non-transparent CS data
services based on the described mapping in TS 27.001 or AMR speech . The parameter can be
used to make code reservations in the downlink of the radio interface for the UMTS bearer
service (BS20 and BS30) refer TS 22.002. Its purpose is
to limit the delivered bit-rate to applications or external networks with such limitations,

to allow maximum wanted user bit-rate to be defined for applications able to operate with
different rates (e.g. applications with adapting codecs).]
Maximum bit rate is set to the highest value  WAIUR (If WAIUR is less or equal to 14.4
kbit/s then Guaranteed Bit Rate and Maximum Bit Rate shall be set to 14.4 kbit/s)
MaximumBitRate ::= ENUMERATED
{
mBR14400BitsPerSecond (1), -- BS20 non-transparent
mBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
mBR32000BitsPerSecond (3), -- BS30 multimedia
mBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
mBR12200BitsPerSecond (106), -- AMR speech

mBR4750BitsPerSecond (113) -- AMR speech
}
A.6.44 MCCMNC
MCCMNC ::= OCTET STRING(SIZE(3))
-- This type contains the mobile country code (MCC) and the mobile
-- network code (MNC) of a PLMN.
= MCC + MNC, 460 00 will be coded as 64 f0 00
A.6.45 Measure Duration

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.
--
A.6.46 Message Reference

This field contains a unique message reference number allocated by the mobile station when
transmitting a short message to the service centre. This field corresponds to the TP-Message-
Reference element of the SMS_SUBMIT PDU defined in TS 23.040 .
MessageReference ::= OCTET STRING(size(1))
A.6.47 MLC Number

This parameter refers to the ISDN (E.164) number of an MLC.
A.6.48 Mobile Station Classmark/Change of Classmark

This MS classmark field contains the mobile station classmark employed by the served MS on
call set-up as defined in TS 24.008 (see mobile station classmark 2). 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.
It should be noted that the change of classmark field is optional and not required if partial
records are created when the classmark is altered.
Classmark ::= OCTET STRING(size(3))
--
-- See Mobile station classmark 2 or 3 TS 24.008
--
A.6.49 MOLR Type

The MOLR-Type identifier refers to the type of MO-LR that was invoked as defined in TS
24.080.
MOLR-Type ::= INTEGER
A.6.50 MSC Address

This field contains the ITU-T Recommendation E.164 number assigned to the MSC that
produced the record. For further details concerning the structure of MSC numbers see
TS 23.003
See calling number
A.6.51 MSC CIC

MSCCIC ::= INTEGER(0..65535)
Circuit Identity Code 1 will be coded as 01 00

A.6.52 Org MSC ID/SPC

MSCId ::= OCTET STRING(SIZE (3))
--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
A.6.53 MSC Server Indication

This field contains an indicator whether the CAMEL subscription information is active. The
parameter is present for the VT-CSI in the VMSC and not present for the T-CSI in the GMSC.
This indication should be used for differentiation between the validity of the record content
for T-CSI in the GMSC and VT-CSI in the VMSC.
mscServerIndication BOOLEAN,
A.6.54 Network Call Reference

Whenever CAMEL is applied, this field is used for correlation of call records outputted from
the originating MSC (when applicable), the GMSC and the terminating MSC, and a network
optional call record from the gsmSCF.
If CAMEL is'nt applied, this field is used for correlation of call records in one call event in
one MSC.
NetworkCallReference ::= OCTET STRING(SIZE(1..8))
-- See TS 29.002
--
A.6.55 Notification to MS User

This field contains the privacy notification to MS user that was applicable when the LR was
invoked as defined in TS 29.002
NotificationToMSUser ::= ENUMERATED
{
notifyLocationAllowed (0),
notifyAndVerify-LocationAllowedIfNoResponse (1),
notifyAndVerify-LocationNotAllowedIfNoResponse (2),
locationNotAllowed (3)
}

A.6.56 Number of DP Encountered

This field indicates how often CAMEL armed detection points (TDP and EDP) were
encountered and is a measure of signalling between serving network and CAMEL service and
complements 'Level of CAMEL service' field. Detection points from all applied CAMEL
services for a single call leg and processed in the same gsmSSF shall be counted together.
numberOfDPEncountered INTEGER,
A.6.57 Number of Forwarding

This field, if provided via ISUP signalling, contains the number of times a call has been
forwarded prior to the interrogation of the HLR and is defined in TS 29.002 .
NumberOfForwarding ::= INTEGER (1..5)
A.6.58 Old/New Location

These fields contain the location of a mobile subscriber before and after a location update. In
case of VLR location update the location information consists of a VMSC number and
location area code. In case of HLR location update the field contains the VMSC number and
the VLR number.
A.6.59 Partial Record Type

This field indicates the event that caused the generation of a partial record.
PartialRecordType ::= ENUMERATED
{
timeLimit (0),
serviceChange (1),
locationChange (2),
classmarkChange (3),
aocParmChange (4),
radioChannelChange (5),
hSCSDParmChange (6),
changeOfCAMELDestination (7)
}
A.6.60 Positioning Data

This information element is providing positioning data associated with a successful or
unsuccessful location attempt for a target MS according TS 49.031 .
PositioningData ::= OCTET STRING (SIZE(1..33))

A.6.61 Privacy Override

This parameter indicates if 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,
A.6.62 Radio Channel Requested/Radio Channel Used/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 traffic channel actually employed for the
connection i.e. either full rate (Bm) or half rate (Lm) as described in GSM 05.01 . Any change
in the type of channel used may be recorded in the change of radio channel used field
including the time at which the change occurred and the speech version used after the change
of radio channel.
A.6.63 Rate Indication

This parameter specifies the rate adaptation that was used for the connection. The field is
constructed from the information in the parameters "rate adaption" and "other rate adaption"
signalled between the MS/UE and the network, see 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 ::= OCTET STRING(SIZE(1))

--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
--11 PIAFS
A.6.64 Record Extensions

The field enables network operators and/ or manufacturers to add their own extensions to the
standard record definitions.
A.6.65 Record Type

The field identifies the type of the record e.g. mobile originated, mobile terminated etc.
enum recordtype
{
moCallRecord 0,
mtCallRecord 1,
roamingRecord 2,
incGatewayRecord 3,
outGatewayRecord 4,
transitRecord 5,
moSMSRecord 6,
mtSMSRecord 7,
ssActionRecord 10,
hlrIntRecord 11,
commonEquipRecord 14,
recTypeExtensions 15,
termCAMELRecord 16,
mtLCSRecord 17,
moLCSRecord 18,
niLCSRecord 19,
forwardCallRecord 100
}

A.6.66 Recording Entity

This field contains the ITU-T E.164 number assigned to the entity (MSC, VLR, HLR etc.)
that produced the record. For further details concerning the structure of MSC and location
register numbers see TS 23.003 .
A.6.67 Org RNC or BSC ID

RNCorBSCId ::= OCTET STRING(SIZE (3))
--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
A.6.68 Roaming Number

The roaming number field of the MOC record contains the mobile station roaming number as
defined in TS 23.003 and coded according to TS 29.002
A.6.69 Routing Number

The routing number field of the HLR interrogation record contains either a mobile station
roaming number or, in case of call forwarding, a forwarded-to number.
A.6.70 Sequence Number

This field contains a running sequence number employed to link the partial records generated
for a particular connection, begin with 1.
A.6.71 Served IMEI

This fields contains the international mobile equipment identity (IMEI) of the equipment
served. The term "served" equipment is used to describe the ME involved in the transaction
recorded e.g. the called ME in case of an MTC record.
The structure of the IMEI is defined in TS 23.003.
The International Mobile station Equipment Identity (IMEI) is composed as shown in
Figure A-3.

Figure 1.1 Figure 2
8 digits 6 digits 1 digit
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). Its length is 8 digits;
- Serial Number (SNR) is an individual serial number uniquely identifying each equipment
within the TAC. Its length is 6 digits;
- Spare digit: this digit shall be zero, when transmitted by the MS.
The IMEI (14 digits) is complemented by a check digit. The check digit is not part of the
digits transmitted when the IMEI is checked, as described below. The Check Digit is intended
to avoid manual transmission errors, e.g. when customers register stolen MEs at the operator's
customer care desk. The Check Digit is defined according to the Luhn formula, as defined in
annex B.
 The Check Digit is not applied to the Software Version Number.

 The security requirements of the IMEI are defined in 3GPP TS 22.016.
A.6.72 Served IMSI

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.
The structure of the IMSI is defined in TS 23.003.
IMSI is composed as shown in Figure A-4 below.
Figure 1.2 Figure 3
Not more than 15 digits
3 digits 2 or 3
digits
MCC MNC MSIN
NMSI
IMSI

IMSI is composed of three parts:

Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the
country of domicile of the mobile subscriber;
 Mobile Network Code (MNC) consisting of two or three digits for GSM/UMTS
applications. The MNC identifies the home PLMN of the mobile subscriber. The length
of the MNC (two or three digits) depends on the value of the MCC. A mixture of two and
three digit MNC codes within a single MCC area is not recommended and is outside the
scope of this specification.
 Mobile Subscriber Identification Number (MSIN) identifying the mobile subscriber
within a PLMN.
The National Mobile Subscriber Identity (NMSI) consists of the Mobile Network Code and
the Mobile Subscriber Identification Number.
A.6.73 Served MSISDN

This field contains the mobile station ISDN number (MSISDN) of the served party. The term
"served" party is used to describe the mobile subscriber involved in the transaction recorded
e.g. the called subscriber in case of an MTC record. In case of multi-numbering the MSISDN
stored in a MOC record will be the primary MSISDN of the calling party.
The structure of the MSISDN is defined in TS 23.003.
MS international ISDN numbers are allocated from the ITU-T Recommendation E.164
numbering plan; see also ITU-T Recommendation E.213. The structure of the MS
international ISDN number will then be as shown in Figure A-5.
Figure 1.3 Figure 4
CC N D C SN
N a t io n a l ( s ig n if ic a n t)
m o b ile n u m b e r
M o b ile s t a tio n in t e r n a tio n a l
IS D N n u m b e r
The number consists of:

Country Code (CC) of the country in which the MS is registered, followed by:
National (significant) mobile number, which consists of:
National Destination Code (NDC) and Subscriber Number (SN).
For GSM/UMTS applications, a National Destination Code is allocated to each PLMN. In
some countries more than one NDC may be required for each PLMN.
The composition of the MS international ISDN number should be such that it can be used as a
global title address in the Signalling Connection Control Part (SCCP) for routeing messages
to the home location register of the MS. The country code (CC) and the national destination
code (NDC) will provide such routeing information. If further routeing information is
required, it should be contained in the first few digits of the subscriber number (SN).

A sub-address may be appended to an ISDN number for use in call setup and in
supplementary service operations where an ISDN number is required (see ITU-T
Recommendations E.164, clause 11.2 and X.213 annex A). The sub-address is transferred to
the terminal equipment denoted by the ISDN number.
The maximum length of a sub-address is 20 octets, including one octet to identify the coding
scheme for the sub-address (see ITU-T Recommendation X.213, annex A). All coding
schemes described in ITU-T Recommendation X.213, annex A are supported in GSM and
UMTS.
A.6.74 Service Center Address

This field contains a ITU-T Recommendation E.164 number identifying a particular service
centre e.g. short message service centre (see TS 23.040 ).
A.6.75 Service Key

This field identifies the CAMEL service logic applied. Service key is defined in HLR as part
of CAMEL subscription information.
ServiceKey ::= INTEGER (0..2147483647)
A.6.76 Short Message Service Result

This field contains the result of an attempt to deliver a short message either to a service centre
or to a mobile subscriber (see TS 29.002). Note that this field is only provided if the attempted
delivery was unsuccessful.
A.6.77 Speech Version Supported/Speech Version Used

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 GSM 08.08 speech version identifier with the extension bit
8 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 ::= OCTET STRING (SIZE(1))
-- see GSM 08.08
-- 000 0001 GSM speech full rate version 1
-- 001 0001 GSM speech full rate version 2 used for enhanced full rate
-- 010 0001 GSM speech full rate version 3 for future use
-- 000 0101 GSM speech half rate version 1
-- 001 0101 GSM speech half rate version 2 for future use

A.6.78 System Type

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.
SystemType ::= ENUMERATED
{
unknown (0),
iuUTRAN (1),
gERAN (2)
}
A.6.79 Supplementary Service(s)

The supplementary service field in the Supplementary Service record type contains the code
of the supplementary service on which the action was performed.
The supplementary services field in the MOC / MTC records contains the codes of the
supplementary services invoked as a result of, or during, a connection.
The coding of supplementary service is described in detail in 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 (0x10),
-- all line identification SS
--

-- calling-line-identification-presentation (0x11),
-- calling line identification presentation
-- calling-line-identification-restriction (0x12),
-- calling line identification restriction
-- connected-line-identification-presentation (0x13),
-- connected line identification presentation
-- connected-line-identification-restriction (0x14),
--connected line identification restriction
-- malicious-call-identification (0x15),
-- malicious call identification
--
-- allNameIdentificationSS (0x18),
-- all name identification SS
-- calling-name-presentation (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 (0x31),
-- explicit call transfer
-- mobile-access-hunting (0x32),
-- mobile access hunting
--
-- allCallCompletionSS (0x40),
-- all Call completion SS
--
-- 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 (0x45),
-- multicall
--
-- allMultiPartySS (0x50),
-- all multiparty SS
--

-- multiPTY (0x51),
-- multiparty
--
-- allCommunityOfInterest-SS (0x60),
-- 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
--
-- 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 (0xa1),
-- 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
-- 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 (0xf0),
-- plmn-specificSS-1 (0xf1),
-- plmn-specificSS-A (0xfa),
-- plmn-specificSS-B (0xfb),
-- plmn-specificSS-C (0xfc),
-- plmn-specificSS-D (0xfd),
-- plmn-specificSS-E (0xfe),
-- USSD (0xff)
A.6.80 Supplementary Service Action

This field contains the type of supplementary service action requested by the subscriber or
performed by the network. Possible values include:
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
A.6.81 Supplementary Service Action Result

This field contains the result of an attempted supplementary service action (see TS 29.002 ).
Note that this field is only provided if the SS-action was at least partially unsuccessful.
A.6.82 Supplementary Service Parameters

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.
For USSD
an appropriate action type = USSD invoke(vaule = 7),
supplementary service code(vaule = ff) or basic service code(not be coded into ASN.1)
ss parameter is service access code e.g. #111#(ASCII)
for forwarding
ss parameter will be filled with forwarding number.
A.6.83 Transparency Indicator

This field indicates whether the basic service was employed in transparent or non-transparent
mode. It should also be noted that this field is only relevant for those services which may be
operated in both transparent and non-transparent modes.
TransparencyInd ::= ENUMERATED
{
transparent (0),
nonTransparent (1)
}
A.6.84 SMS Text

When sms user contents is text , the field of sms text will be recorded.
SMSTEXT ::= OCTET STRING
A.6.85 SMS User Data Type

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
A.6.86 Concatenated SMS Reference Number

ConcatenatedSMSReferenceNumber ::= INTEGER(0..65535)
This facility allows short messages to be concatenated to form a longer message
In the case of uncompressed 8-bit data, the maximum length of the short message within the
TP-UD field is 134 (140-6) octets.
In the case of uncompressed GSM 7 bit default alphabet data, the maximum length of the
short message within the TP-UD field is 153 (160-7) characters.
In the case of 16 bit uncompressed USC2 data, the maximum length of the short message
within the TP-UD field is 67 ((140-6)/2) characters. A UCS2 character must not be split in the
middle; if the length of the User Data Header is odd, the maximum length of the whole TP-
UD field is 139 octets.
In the case of compressed GSM 7 bit default alphabet data, 8 bit data or UCS2 the maximum
length of the compressed short message within the TP-UD field is 134 (140-6) octets
including the Compression Header and Compression Footer, both or either of which may be
present (see 23.040).
The maximum length of an uncompressed concatenated short message is 39015 (255*153)
default alphabet characters, 34170 (255*134) octets or 17085 (255*67) UCS2 characters.
The maximum length of a compressed concatenated message is 34170 (255*134) octets
including the Compression Header and Compression Footer (see Figure A-6 below).
Figure 1.4 Figure 5
Compression Header Compressed Data (CD) Compression Footer

HHeannder Header
Segmentation / De-segmentation
TP-UDH CH CD TP-UDH CD TP-UDH CD CF
First segment Intermediate segments Final segment
The Information-Element-Data field contains information set by the application in the

SMS-SUBMIT so that the receiving entity is able to re-assemble the short messages in the
correct order. Each concatenated short message contains a reference number which together
with the originating address and Service Centre address allows the receiving entity to
discriminate between concatenated short messages sent from different originating SMEs
and/or SCs. In a network which has multiple SCs, it is possible for different segments of a
concatenated SM to be sent via different SCs and so it is recommended that the SC address
should not be checked by the MS unless the application specifically requires such a check.

The TP elements in the SMS-SUBMIT PDU, apart from TP-MR, TP-SRR, TP-UDL and
TP-UD, should remain unchanged for each SM which forms part of a concatenated SM,
otherwise this may lead to irrational behaviour. TP-MR must be incremented for every
segment of a concatenated message as defined in 23.040. A SC shall handle segments of a
concatenated message like any other short message. The relation between segments of a
concatenated message is made only at the originator, where the message is segmented, and at
the recipient, where the message is reassembled. SMS-COMMANDs identify messages by
TP-MR and therefore apply to only one segment of a concatenated message. It is up to the
originating SME to issue SMS-COMMANDs for all the required segments of a concatenated
message.
The Information-Element-Data octets shall be coded as follows.
Octet 1 Concatenated short message reference number.
This octet shall contain a modulo 256 counter indicating the reference number for a particular
concatenated short message. This reference number shall remain constant for every short
message which makes up a particular concatenated short message.
Octet 2 Maximum number of short messages in the concatenated short message.
This octet shall contain a value in the range 0 to 255 indicating the total number of short
messages within the concatenated short message. The value shall start at 1 and remain
constant for every short message which makes up the concatenated short message. If the value
is zero then the receiving entity shall ignore the whole Information Element.
Octet 3 Sequence number of the current short message.
This octet shall contain a value in the range 0 to 255 indicating the sequence number of a
particular short message within the concatenated short message. The value shall start at 1 and
increment by one for every short message sent within the concatenated short message. If the
value is zero or the value is greater than the value in octet 2 then the receiving entity shall
ignore the whole Information Element.
The IEI and associated IEI length and IEI data shall be present in every segment of the
concatenated SM.
For example , user send message of picture 1 firstly, and then send message of picture 2 .Both
are coded with more than 140 bytes., picture 1 is split into 2 segments, picture 2 is split into 4
segments.
Then Concatenated SMS Reference Number will be coded as x and y in picture 1 and picture
2.
Maximum Number Of SMS In The Concatenated SMS will be coded as 2 and 4 in picture 1
and picture 2
Sequence Number Of The Current SMS will be coded as 1,2 and 1,2,3,4 in picture 1 and
picture 2

Concatenated Maximum Sequence Number Of The Current

SMS Number Of SMS
Reference SMS In The
Number Concatenated First Second … Last
SMS segment Segment segment
Picture1 X(may be 1) 2 1 2
Picture2 Y(may be 1) 4 1 2 3 4
A.6.87 Maximum Number of SMS in the Concatenated SMS

MaximumNumberOfSMSInTheConcatenatedSMS ::= INTEGER(0..255)
See Concatenated SMS Reference Number.
A.6.88 Sequence Number Of the Current SMS

SequenceNumberOfTheCurrentSMS ::= INTEGER(0..255)
Sequence Number Of The Current SMS First segment
A.6.89 CUG Index

A value assigned by the network to identify a CUG, the CUG index has significance only
between the subscriber and network.
A.6.90 CUG Outgoing Access Indicator

Indicates the subscriber with a Outgoing Access.
CUGOutgoingAccessIndicator ::= ENUMERATED
{
notCUGCall (0),
cUGCall (1)
}
A.6.91 CUG Interlock Code

Is used by the network (not by the MS) to identify CUG membership at
MOC,MTC,CFW,ROAM.
CUG Interlock Code = Network code + CUG interlock
CUGInterlockCode ::= OCTET STRING (SIZE (4))
A.6.92 CUG Outgoing Access Used/CUG Incoming Access Used

Indicates caller and called whether or not is in the same CUG group.
CUGOutgoingAccessUsed ::= ENUMERATED

{
callInTheSameCUGGroup (0),
callNotInTheSameCUGGroup (1)
}
A.6.93 Modem Type

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)
}
A.6.94 Classmark3
Classmark3 contains radio capability information about MS.
Classmark3 ::= OCTET STRING(SIZE(2))
A.6.95 Charged Party

Indicates if the calling subscriber or the called subscriber is charged for the call, or if the call
is not charged. May be modified by the SCF.
ChargedParty ::= ENUMERATED
{
callingParty (0),
calledParty (1)
}
A.6.96 Original Called Number

The address of original called party.

OriginalCalledNumber ::= BCDDirectoryNumber
A.6.97 Calling Charge Area Code

Indicates the calling party logical area for distance charge
OCTET STRING(SIZE (1..3))
A.6.98 Called Charge Area Code

Indicates the called party logical area for distance charge
OCTET STRING(SIZE (1..3))
A.6.99 Call Emlpp Priority

SubscriberEmlppPriority::= OCTET STRING (SIZE (1))
--no priority applied 0
--call priority level 4 1
--call priority level B 6
--call priority level A 7
See 24.008
A.6.100 Caller/Called Default Emlpp Priority

EmlppPriority ::= OCTET STRING (SIZE (1))
-- The mapping from the values A,B,0,1,2,3,4 to the integer-value is
-- specified as follows where A is the highest and 4 is the lowest
-- priority level
-- the integer values 7-15 are spare and shall be mapped to value 4
--priorityLevelA EMLPP-Priority ::= 6

--priorityLevelB EMLPP-Priority ::= 5
--priorityLevel0 EMLPP-Priority ::= 0


See 29.002
A.6.101 Ea Subscriber Info

Indicates the calling subscriber’s information of Equal Access
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.
A.6.102 Selected CIC

Indicates the selected code of Carrier identification
SelectedCIC ::= OCTET STRING (SIZE (3))
A.6.103 Ported Flag

Indicates if called party be ported.
PortedFlag ::= ENUMERATED
{
numberNotPorted (0),
numberPorted (1)
}
A.6.104 Global Area ID

Indicates CGI of GSM or SAI of WCDMA
GAI ::= OCTET STRING(SIZE(7))
--such as 64 F0 00 00 ABCD 1234
A.6.105 Change Of global Area ID

A list of changes in CGI / SAI each time-stamped.
ChangeOfglobalAreaID ::= SEQUENCE
{
location [0] GAI,
changeTime [1] TimeStamp
}

A.6.106 Interaction With IP

In the case of interaction between SSP and IP, GsmSCF play announcement to SSP and start
charging.
InteractionWithIP ::= NULL
A.6.107 HLC
This parameter is a 1:1 copy of the contents (i.e. starting with octet 3) of the "high layer
compatibility" parameter of ITU-T Q.931.
HLC ::= OCTET STRING
A.6.108 LLC
This parameter is a 1:1 copy of the contents (i.e. starting with octet 3) of the "low layer
compatibility" parameter of ITU-T Q.931.
LLC ::= OCTET STRING
A.6.109 ISDN-BC
This parameter is a 1:1 copy of the contents (i.e. starting with octet 3) of the "bearer
capability" parameter of ITU-T Q.931.
ISDN-BC ::= OCTET STRING
A.6.110 USSDCodingScheme
In the case of USSD, indicates coding scheme of USSD
A.6.111 USSDString
In the case of USSD, indicates subscriber input
USSDString ::= OCTET STRING
A.6.112 USSDNotifyCounter
In the case of USSD, indicates the times of notify procedure
USSDNotifyCounter ::= INTEGER(0..255)
A.6.113 USSDRequestCounter
In the case of USSD, indicates the times of request procedure
USSDRequestCounter ::= INTEGER(0..255)
A.6.114 Initial Call Attempt Flag

Indicates if a Initial Call Attempt call from GsmSCF.
initialCallAttemptFlag NULL

A.6.115 USSD Call Back FLAG

Indicates if a USSD call back when a CAMEL subscriber roam aboard.
ussdCallBackFlag NULL
A.6.116 mscIncomingRouteAttribute
Indicates the incoming trunk attribute as follows:
RouteAttribute ::= ENUMERATED
{
cas (0),
tup (1),
isup (2),
pra (3),
bicc (4),
sip (5),
others (0xFF)
}
A.6.117 mscOutgoingRouteAttribute
Indicates the incoming trunk attribute as follows:
{
cas (0),
tup (1),
isup (2),
pra (3),
bicc (4),
sip (5),
others (0xFF)
}
A.6.118 Voice Indicator

Indicates the voice indicator attribute as follows:
VoiceIndicator ::= ENUMERATED
{
sendToneByLocalMsc(0) ,

sendToneByOtherMsc(1),
voiceNoIndication (3)
}
A.6.119 Call Type

Indicates the call type as follows:
CallType ::= ENUMERATED
{
unknown (0),
internal (1),
incoming (2),
outgoing (3),
tandem (4)
}
A.6.120 B_CATEGORY
Indicates the called side information as follows:
BCategory ::= ENUMERATED
{
subscriberFree (0) ,
subscriberBusy (1),
subscriberNoIndication (3)
}
A.7 Charging Data Record Structure:ASN.1 description

Huawei MSC use ASN.1 language to describe CDRs. BER (Basic Encoding Rules) is
adopted.
The following is ASN.1 definitions for CDRs (refer to ETSI GSM 12.05, 3GPP R99
TS32.005,R4/R5TS32.205).
[CS_CDR[203].asn]
CS-R99-R4-CHARGING
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
--------------------------------------------------------------------------------

--
-- CALL AND EVENT RECORDS
--
------------------------------------------------------------------------------
--Font: verdana 8
CallEventRecord ::= CHOICE

{
moCallRecord [0] MOCallRecord,
mtCallRecord [1] MTCallRecord,
roamingRecord [2] RoamingRecord,
incGatewayRecord [3] IncGatewayRecord,
outGatewayRecord [4] OutGatewayRecord,
transitRecord [5] TransitCallRecord,
moSMSRecord [6] MOSMSRecord,
mtSMSRecord [7] MTSMSRecord,
ssActionRecord [10] SSActionRecord,
hlrIntRecord [11] HLRIntRecord,
commonEquipRecord [14] CommonEquipRecord,
recTypeExtensions [15] ManagementExtensions,
termCAMELRecord [16] TermCAMELRecord,
mtLCSRecord [17] MTLCSRecord,
moLCSRecord [18] MOLCSRecord,
niLCSRecord [19] NILCSRecord,
forwardCallRecord [100] MOCallRecord
}
MOCallRecord ::= SET

{
recordType [0] CallEventRecordType
OPTIONAL,
servedIMSI [1] IMSI
OPTIONAL,
servedIMEI [2] IMEI
OPTIONAL,
servedMSISDN [3] MSISDN
OPTIONAL,
callingNumber [4] CallingNumber
OPTIONAL,
calledNumber [5] CalledNumber
OPTIONAL,
translatedNumber [6] TranslatedNumber
OPTIONAL,
connectedNumber [7] ConnectedNumber
OPTIONAL,
roamingNumber [8] RoamingNumber
OPTIONAL,
recordingEntity [9] RecordingEntity
OPTIONAL,
mscIncomingROUTE [10] ROUTE
OPTIONAL,
mscOutgoingROUTE [11] ROUTE
OPTIONAL,
location [12] LocationAreaAndCell OPTIONAL,
changeOfLocation [13] SEQUENCE OF LocationChange OPTIONAL,

basicService [14] BasicServiceCode

OPTIONAL,
transparencyIndicator [15] TransparencyInd
OPTIONAL,
changeOfService [16] SEQUENCE OF ChangeOfService
OPTIONAL,
supplServicesUsed [17] SEQUENCE OF SuppServiceUsed
OPTIONAL,
aocParameters [18] AOCParameters
OPTIONAL,
changeOfAOCParms [19] SEQUENCE OF AOCParmChange
OPTIONAL,
msClassmark [20] Classmark
OPTIONAL,
changeOfClassmark [21] ChangeOfClassmark
OPTIONAL,
seizureTime [22] TimeStamp
OPTIONAL,
answerTime [23] TimeStamp
OPTIONAL,
releaseTime [24] TimeStamp
OPTIONAL,
callDuration [25] CallDuration
OPTIONAL,
radioChanRequested [27] RadioChanRequested
OPTIONAL,
radioChanUsed [28] TrafficChannel
OPTIONAL,
changeOfRadioChan [29] ChangeOfRadioChannel
OPTIONAL,
causeForTerm [30] CauseForTerm
OPTIONAL,
diagnostics [31] Diagnostics
OPTIONAL,
callReference [32] CallReference
OPTIONAL,
sequenceNumber [33] SequenceNumber
OPTIONAL,
additionalChgInfo [34] AdditionalChgInfo
OPTIONAL,
recordExtensions [35] ManagementExtensions
OPTIONAL,
gsm-SCFAddress [36] Gsm-SCFAddress
OPTIONAL,
serviceKey [37] ServiceKey
OPTIONAL,
networkCallReference [38] NetworkCallReference
OPTIONAL,
mSCAddress [39] MSCAddress
OPTIONAL,
cAMELInitCFIndicator [40] CAMELInitCFIndicator
OPTIONAL,
defaultCallHandling [41] DefaultCallHandling
OPTIONAL,

fnur [45] Fnur

OPTIONAL,
aiurRequested [46] AiurRequested
OPTIONAL,
speechVersionSupported [49] SpeechVersionIdentifier
OPTIONAL,
speechVersionUsed [50] SpeechVersionIdentifier
OPTIONAL,
numberOfDPEncountered [51] INTEGER
OPTIONAL,
levelOfCAMELService [52] LevelOfCAMELService
OPTIONAL,
freeFormatData [53] FreeFormatData
OPTIONAL,
cAMELCallLegInformation [54] SEQUENCE OF CAMELInformation OPTIONAL,
freeFormatDataAppend [55] BOOLEAN
OPTIONAL,
defaultCallHandling-2 [56] DefaultCallHandling
OPTIONAL,
gsm-SCFAddress-2 [57] Gsm-SCFAddress
OPTIONAL,
serviceKey-2 [58] ServiceKey
OPTIONAL,
freeFormatData-2 [59] FreeFormatData
OPTIONAL,
freeFormatDataAppend-2 [60] BOOLEAN
OPTIONAL,
systemType [61] SystemType
OPTIONAL,
rateIndication [62] RateIndication
OPTIONAL,
partialRecordType [69] PartialRecordType
OPTIONAL,
guaranteedBitRate [70] GuaranteedBitRate
OPTIONAL,
maximumBitRate [71] MaximumBitRate
OPTIONAL,
modemType [139] ModemType
OPTIONAL,
classmark3 [140] Classmark3
OPTIONAL,
chargedParty [141] ChargedParty
OPTIONAL,
originalCalledNumber [142] OriginalCalledNumber
OPTIONAL,
callingChargeAreaCode [145] ChargeAreaCode
OPTIONAL,
calledChargeAreaCode [146] ChargeAreaCode
OPTIONAL,
mscOutgoingCircuit [166] MSCCIC
OPTIONAL,
orgRNCorBSCId [167] RNCorBSCId
OPTIONAL,
orgMSCId [168] MSCId
OPTIONAL,

callEmlppPriority [170] SubscriberEmlppPriority

OPTIONAL,
callerDefaultEmlppPriority 171] SubscriberEmlppPriority OPTIONAL,
eaSubscriberInfo [174] EASubscriberInfo
OPTIONAL,
selectedCIC [175] SelectedCIC
OPTIONAL,
optimalRoutingFlag [177] NULL
OPTIONAL,
optimalRoutingLateForwardFlag [178] NULL
OPTIONAL,
optimalRoutingEarlyForwardFlag [179] NULL
OPTIONAL,
portedflag [180] PortedFlag
OPTIONAL,
calledIMSI [181] IMSI OPTIONAL,
globalAreaID [188] GAI
OPTIONAL,
changeOfglobalAreaID [189] SEQUENCE OF ChangeOfglobalAreaID
OPTIONAL,
subscriberCategory [190] SubscriberCategory
OPTIONAL,
firstmccmnc [192] MCCMNC
OPTIONAL,
intermediatemccmnc [193] MCCMNC
OPTIONAL,
lastmccmnc [194] MCCMNC
OPTIONAL,
cUGOutgoingAccessIndicator [195] CUGOutgoingAccessIndicator OPTIONAL,
cUGInterlockCode [196] CUGInterlockCode
OPTIONAL,
cUGOutgoingAccessUsed [197] CUGOutgoingAccessUsed
OPTIONAL,
cUGIndex [198] CUGIndex
OPTIONAL,
interactionWithIP [199] InteractionWithIP
OPTIONAL,
hotBillingTag [200] HotBillingTag
OPTIONAL,
setupTime [201] TimeStamp
OPTIONAL,
alertingTime [202] TimeStamp
OPTIONAL,
voiceIndicator [203] VoiceIndicator
OPTIONAL,
bCategory [204] BCategory
OPTIONAL,
callType [205] CallType
OPTIONAL
}
--at moc callingNumber is the same as served msisdn except basic msisdn != calling
number such as MSP service
MTCallRecord ::= SET

{
OPTIONAL,
servedIMSI [1] IMSI
OPTIONAL,
servedIMEI [2] IMEI
OPTIONAL,
servedMSISDN [3] CalledNumber
OPTIONAL,
OPTIONAL,
connectedNumber [5] ConnectedNumber
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
location [9] LocationAreaAndCell
OPTIONAL,
changeOfLocation [10] SEQUENCE OF LocationChange
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
aocParameters [15] AOCParameters
OPTIONAL,
changeOfAOCParms [16] SEQUENCE OF AOCParmChange
OPTIONAL,
OPTIONAL,
changeOfClassmark [18] ChangeOfClassmark
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
radioChanRequested [24] RadioChanRequested
OPTIONAL,
radioChanUsed [25] TrafficChannel
OPTIONAL,
changeOfRadioChan [26] ChangeOfRadioChannel
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
fnur [38] Fnur
OPTIONAL,
aiurRequested [39] AiurRequested
OPTIONAL,
speechVersionSupported [42] SpeechVersionIdentifier
OPTIONAL,
speechVersionUsed [43] SpeechVersionIdentifier
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
guaranteedBitRate [55] GuaranteedBitRate
OPTIONAL,
maximumBitRate [56] MaximumBitRate
OPTIONAL,
initialCallAttemptFlag [137] NULL
OPTIONAL,
ussdCallBackFlag [138] NULL
OPTIONAL,
modemType [139] ModemType
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
callingChargeAreaCode [145]ChargeAreaCode
OPTIONAL,
calledChargeAreaCode [146]ChargeAreaCode
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
levelOfCAMELService [154] LevelOfCAMELService
OPTIONAL,
OPTIONAL,
mscIncomingCircuit [166] MSCCIC
OPTIONAL,
OPTIONAL,
OPTIONAL,
callEmlppPriority [170] EmlppPriority
OPTIONAL,
calledDefaultEmlppPriority [171] EmlppPriority
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
portedflag [180] PortedFlag
OPTIONAL,
OPTIONAL,
changeOfglobalAreaID [189] SEQUENCE OF ChangeOfglobalAreaID OPTIONAL,
OPTIONAL,
OPTIONAL,
intermediatemccmnc [193] MCCMNC
OPTIONAL,
lastmccmnc [194] MCCMNC
OPTIONAL,
OPTIONAL,
cUGIncomingAccessUsed [197] CUGIncomingAccessUsed
OPTIONAL,
cUGIndex [198] CUGIndex
OPTIONAL,
OPTIONAL,
redirectingnumber [201] RedirectingNumber
OPTIONAL,
redirectingcounter [202] RedirectingCounter
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
RoamingRecord ::= SET

{
OPTIONAL,
servedIMSI [1] IMSI
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
networkCallReference [22] NetworkCallReference OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
originalCalledNumber [142] OriginalCalledNumber OPTIONAL,
callingChargeAreaCode [145] ChargeAreaCode
OPTIONAL,
calledChargeAreaCode [146] ChargeAreaCode
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
TermCAMELRecord ::= SET

{
recordtype [0] CallEventRecordType
OPTIONAL,
servedIMSI [1] IMSI
OPTIONAL,
OPTIONAL,
OPTIONAL,
interrogationTime [4] TimeStamp
OPTIONAL,
destinationRoutingAddress [5] DestinationRoutingAddress OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
levelOfCAMELService [26] LevelOfCAMELService OPTIONAL,
OPTIONAL,
cAMELCallLegInformation [28] SEQUENCE OF CAMELInformation OPTIONAL,
OPTIONAL,
mscServerIndication [30] BOOLEAN
OPTIONAL,
defaultCallHandling-2 [31] DefaultCallHandling OPTIONAL,
gsm-SCFAddress-2 [32] Gsm-SCFAddress
OPTIONAL,
serviceKey-2 [33] ServiceKey
OPTIONAL,
freeFormatData-2 [34] FreeFormatData
OPTIONAL,
freeFormatDataAppend-2 [35] BOOLEAN
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
IncGatewayRecord ::= SET

{
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
iSDN-BC [23] ISDN-BC
OPTIONAL,
lLC [24] LLC
OPTIONAL,
hLC [25] HLC
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
cUGIncomingAccessUsed [197] CUGIncomingAccessUsed OPTIONAL,
mscIncomingRouteAttribute [198] RouteAttribute OPTIONAL,
mscOutgoingRouteAttribute [199] RouteAttribute OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
OutGatewayRecord ::= SET

{
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
mscIncomingRouteAttribute [198] RouteAttribute
OPTIONAL,
mscOutgoingRouteAttribute [199] RouteAttribute
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL
}
TransitCallRecord ::= SET

{
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
isdnBasicService [6] BasicService
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
callReferen [14] CallReference
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
mscIncomingRouteAttribute [198] RouteAttribute OPTIONAL,
mscOutgoingRouteAttribute [199] RouteAttribute
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
MOSMSRecord ::= SET

{
OPTIONAL,
servedIMSI [1] IMSI
OPTIONAL,
servedIMEI [2] IMEI
OPTIONAL,
OPTIONAL,
OPTIONAL,
serviceCentre [5] AddressString
OPTIONAL,
OPTIONAL,
OPTIONAL,
messageReference [8] MessageReference
OPTIONAL,
originationTime [9] TimeStamp
OPTIONAL,
smsResult [10] SMSResult
OPTIONAL,


OPTIONAL,
destinationNumber [12] SmsTpDestinationNumber
OPTIONAL,
cAMELSMSInformation [13] CAMELSMSInformation
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
smsUserDataType [195] SmsUserDataType
OPTIONAL,
smstext [196] SMSTEXT
OPTIONAL,
maximumNumberOfSMSInTheConcatenatedSMS [197] MaximumNumberOfSMSInTheConcatenatedSMS
OPTIONAL,
concatenatedSMSReferenceNumber [198] ConcatenatedSMSReferenceNumber OPTIONAL,
sequenceNumberOfTheCurrentSMS [199] SequenceNumberOfTheCurrentSMS OPTIONAL,
OPTIONAL,
OPTIONAL
}
MTSMSRecord ::= SET

{
OPTIONAL,
serviceCentre [1] AddressString
OPTIONAL,
servedIMSI [2] IMSI
OPTIONAL,
servedIMEI [3] IMEI
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
deliveryTime [8] TimeStamp
OPTIONAL,
smsResult [9] SMSResult
OPTIONAL,
OPTIONAL,
OPTIONAL,
cAMELSMSInformation [12] CAMELSMSInformation OPTIONAL,
OPTIONAL,
OPTIONAL,
classmark3 [140]Classmark3
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
smsUserDataType [195] SmsUserDataType
OPTIONAL,
smstext [196] SMSTEXT
OPTIONAL,
maximumNumberOfSMSInTheConcatenatedSMS [197] MaximumNumberOfSMSInTheConcatenatedSMS
OPTIONAL,
concatenatedSMSReferenceNumber [198] ConcatenatedSMSReferenceNumber
OPTIONAL,
sequenceNumberOfTheCurrentSMS [199] SequenceNumberOfTheCurrentSMS OPTIONAL,
OPTIONAL,
origination [201] CallingNumber
OPTIONAL,
OPTIONAL
}
HLRIntRecord ::= SET

{
OPTIONAL,
servedIMSI [1] IMSI
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
routingNumber [5] RoutingNumber
OPTIONAL,
interrogationTime [6] TimeStamp
OPTIONAL,
numberOfForwarding [7] NumberOfForwarding
OPTIONAL,
interrogationResult [8] HLRIntResult
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
SSActionRecord ::= SET

{
OPTIONAL,
servedIMSI [1] IMSI
OPTIONAL,
servedIMEI [2] IMEI
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
basicServices [7] BasicServices
OPTIONAL,
supplService [8] SS-Code
OPTIONAL,
ssAction [9] SSActionType
OPTIONAL,
ssActionTime [10] TimeStamp
OPTIONAL,
ssParameters [11] SSParameters
OPTIONAL,
ssActionResult [12] SSActionResult
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
ussdCodingScheme [126] UssdCodingScheme
OPTIONAL,
ussdString [127] SEQUENCE OF UssdString
OPTIONAL,
ussdNotifyCounter [128] UssdNotifyCounter
OPTIONAL,
ussdRequestCounter [129] UssdRequestCounter
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
CommonEquipRecord ::= SET

{
OPTIONAL,
equipmentType [1] EquipmentType
OPTIONAL,
equipmentId [2] EquipmentId
OPTIONAL,
servedIMSI [3] IMSI
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
changeOfService [7] SEQUENCE OF ChangeOfService OPTIONAL,
supplServicesUsed [8] SEQUENCE OF SuppServiceUsed OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
fnur [17] Fnur
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
servedIMEI [102] IMEI
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
------------------------------------------------------------------------------
--
-- OBSERVED IMEI TICKETS
--
------------------------------------------------------------------------------
ObservedIMEITicket ::= SET

{
servedIMEI [0] IMEI,
imeiStatus [1] IMEIStatus,
servedIMSI [2] IMSI,
servedMSISDN [3] MSISDN OPTIONAL,
recordingEntity [4] RecordingEntity,
eventTime [5] TimeStamp,
location [6]
LocationAreaAndCell,
imeiCheckEvent [7] IMEICheckEvent OPTIONAL,
OPTIONAL,
recordExtensions [9] ManagementExtensions OPTIONAL,
OPTIONAL
}

------------------------------------------------------------------------------
--
-- LOCATION SERICE TICKETS
--
------------------------------------------------------------------------------
MTLCSRecord ::= SET

{
OPTIONAL,
OPTIONAL,
lcsClientType [2] LCSClientType
OPTIONAL,
lcsClientIdentity [3] LCSClientIdentity
OPTIONAL,
servedIMSI [4] IMSI
OPTIONAL,
OPTIONAL,
locationType [6] LocationType
OPTIONAL,
lcsQos [7] LCSQoSInfo
OPTIONAL,
lcsPriority [8] LCS-Priority
OPTIONAL,
mlc-Number [9] ISDN-AddressString
OPTIONAL,
ventTimeStamp [10] TimeStamp
OPTIONAL,
measureDuration [11] CallDuration
OPTIONAL,
notificationToMSUser [12] NotificationToMSUser
OPTIONAL,
privacyOverride [13] NULL
OPTIONAL,
OPTIONAL,
locationEstimate [15] Ext-GeographicalInformation
OPTIONAL,
positioningData [16] PositioningData
OPTIONAL,
lcsCause [17] LCSCause
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,

lcsReferenceNumber [101] CallReferenceNumber

OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
MOLCSRecord ::= SET

{
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
servedIMSI [4] IMSI
OPTIONAL,
OPTIONAL,
molr-Type [6] MOLR-Type
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
eventTimeStamp [10] TimeStamp
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,


OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
NILCSRecord ::= SET

{
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
servedIMSI [4] IMSI
OPTIONAL,
OPTIONAL,
servedIMEI [6] IMEI
OPTIONAL,
emsDigits [7] ISDN-AddressString
OPTIONAL,

emsKey [8] ISDN-AddressString

OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
eventTimeStamp [12] TimeStamp
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL
}
------------------------------------------------------------------------------
--
-- FTAM / FTP / TFTP FILE CONTENTS
--

------------------------------------------------------------------------------
CallEventDataFile ::= SEQUENCE

{
headerRecord [0] HeaderRecord,
callEventRecords [1] SEQUENCE OF CallEventRecord,
trailerRecord [2] TrailerRecord,
extensions [3] ManagementExtensions
}
ObservedIMEITicketFile ::= SEQUENCE

{
productionDateTime [0] TimeStamp,
observedIMEITickets [1] SEQUENCE OF ObservedIMEITicket,
noOfRecords [2] INTEGER,
}
HeaderRecord ::= SEQUENCE

{
}
TrailerRecord ::= SEQUENCE

{
firstCallDateTime [2] TimeStamp,
lastCallDateTime [3] TimeStamp,
noOfRecords [4] INTEGER,
}
------------------------------------------------------------------------------
--
-- COMMON DATA TYPES
--
------------------------------------------------------------------------------
AdditionalChgInfo ::= SEQUENCE

{
chargeIndicator [0] ChargeIndicator OPTIONAL,
chargeParameters [1] OCTET STRING OPTIONAL
}
AddressString ::= OCTET STRING (SIZE (1..maxAddressLength))

-- This type is used to represent a number for addressing
-- purposes. It is composed of
-- a) one octet for nature of address, and numbering plan
-- indicator.
-- b) digits of an address encoded as TBCD-String.

-- a) The first octet includes a one bit extension indicator, a

-- 3 bits nature of address indicator and a 4 bits numbering
-- plan indicator, encoded as follows:
-- bit 8: 1 (no extension)
-- bits 765: nature of address indicator

-- 000 unknown
-- 001 international number
-- 010 national significant number
-- 011 network specific number
-- 100 subscriber number
-- 101 reserved
-- 110 abbreviated number
-- bits 4321: numbering plan indicator

-- 0000 unknown
-- 0001 ISDN/Telephony Numbering Plan (Rec CCITT E.164)
-- 0010 spare
-- 0011 data numbering plan (CCITT Rec X.121)
-- 0100 telex numbering plan (CCITT Rec F.69)
-- 0101 spare
-- 0110 land mobile numbering plan (CCITT Rec E.212)
-- 0111 spare
-- 1000 national numbering plan
-- 1001 private numbering plan
-- all other values are reserved.
-- b) The following octets representing digits of an address

-- encoded as a TBCD-STRING.
maxAddressLength INTEGER ::= 20
AiurRequested ::= ENUMERATED

{
--
-- (note that value "4" is intentionally missing
-- because it is not used in TS 24.008)
--
aiur38400BitsPerSecond4 (12)

AOCParameters ::= SEQUENCE

{
--
-- See TS 22.024.
--
e7 [7] EParameter OPTIONAL
}
AOCParmChange ::= SEQUENCE

{
changeTime [0] TimeStamp,
newParameters [1] AOCParameters
}
BasicService ::= 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
BasicServices ::= SET OF BasicServiceCode
BasicServiceCode ::= CHOICE

{
teleservice [3] TeleserviceCode
}
TeleserviceCode ::= OCTET STRING (SIZE (1))

-- teleservice, a group of teleservices, or all teleservices. The
-- services are defined in TS GSM 02.03.

-- bits 87654321: group (bits 8765) and specific service

-- (bits 4321)
-- allTeleservices (0x00),
-- allSpeechTransmissionServices (0x10),
-- telephony (0x11),
-- emergencyCalls (0x12),
--
-- allShortMessageServices (0x20),
-- shortMessageMT-PP (0x21),
-- shortMessageMO-PP (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
--
-- allVoiceGroupCallServices (0x90),
-- voiceGroupCall (0x91),
-- voiceBroadcastCall (0x92),
--
-- allPLMN-specificTS (0xd0),
-- plmn-specificTS-A (0xda),
-- plmn-specificTS-B (0xdb),
-- plmn-specificTS-C (0xdc),
-- plmn-specificTS-D (0xdd),
-- plmn-specificTS-E (0xde),
-- plmn-specificTS-F (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 [3].
--
-- 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-1200-75bps (0x13),
-- general-dataCDA (0x17),
--
-- allDataCDS-Services (0x18),
-- dataCDS-1200bps (0x1a),
-- dataCDS-2400bps (0x1c),
-- dataCDS-4800bps (0x1d),
-- dataCDS-9600bps (0x1e),
-- general-dataCDS (0x1f),
--
-- allPadAccessCA-Services (0x20),
-- padAccessCA-1200-75bps (0x23),
-- general-padAccessCA (0x27),
--
-- allDataPDS-Services (0x28),
-- dataPDS-2400bps (0x2c),
-- dataPDS-4800bps (0x2d),
-- dataPDS-9600bps (0x2e),
-- general-dataPDS (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
--
-- allPLMN-specificBS (0xd0),
-- plmn-specificBS-A (0xda),
-- plmn-specificBS-B (0xdb),
-- plmn-specificBS-C (0xdc),
-- plmn-specificBS-D (0xdd),
-- plmn-specificBS-E (0xde),
-- plmn-specificBS-F (0xdf)
BCDDirectoryNumber ::= OCTET STRING

-- This type contains the binary coded decimal representation of
-- a directory number e.g. calling/called/connected/translated number.
-- The encoding of the octet string is in accordance with the
-- the elements "Calling party BCD number", "Called party BCD number"
-- and "Connected number" defined in TS 24.008.
-- This encoding includes type of number and number plan information
-- together with a BCD encoded digit string.
-- It may also contain both a presentation and screening indicator
-- (octet 3a).
-- For the avoidance of doubt, this field does not include
-- octets 1 and 2, the element name and length, as this would be
-- redundant.
CallDuration ::= INTEGER

--
-- The call duration in seconds.
-- For successful calls this is the chargeable duration.
-- For call attempts this is the call holding time.

--
CallEventRecordType ::= INTEGER

{
moCallRecord (0),
mtCallRecord (1),
roamingRecord (2),
incGatewayRecord (3),
outGatewayRecord (4),
transitCallRecord (5),
moSMSRecord (6),
mtSMSRecord (7),
ssActionRecord (10),
hlrIntRecord (11),
commonEquipRecord (14),
moTraceRecord (15),
mtTraceRecord (16),
termCAMELRecord (17),
mtLCSRecord (23),
moLCSRecord (24),
niLCSRecord (25),
forwardCallRecord (100)
}
CalledNumber ::= BCDDirectoryNumber
CallingNumber ::= BCDDirectoryNumber
CallingPartyCategory ::= Category
CallReference ::= OCTET STRING (SIZE (1..8))
CallReferenceNumber ::= OCTET STRING (SIZE (1..8))
CAMELDestinationNumber ::= DestinationRoutingAddress
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,
OPTIONAL,
dataVolume [9] DataVolume OPTIONAL,
cAMELInitCFIndicator [10] CAMELInitCFIndicator OPTIONAL,
causeForTerm [11] CauseForTerm OPTIONAL,
cAMELModification [12] ChangedParameters OPTIONAL,
OPTIONAL,
freeFormatDataAppend [15] BOOLEAN OPTIONAL,

freeFormatData-2 [16] FreeFormatData OPTIONAL,

freeFormatDataAppend-2 [17] BOOLEAN OPTIONAL
}
CAMELSMSInformation ::= SET

{
gsm-SCFAddress [1] Gsm-SCFAddress OPTIONAL,
OPTIONAL,
defaultSMSHandling [3] DefaultSMS-Handling OPTIONAL,
OPTIONAL,
destinationSubscriberNumber [6] CalledNumber OPTIONAL,
cAMELSMSCAddress [7] AddressString OPTIONAL,
smsReferenceNumber [8] CallReferenceNumber OPTIONAL
}
CAMELInitCFIndicator ::= ENUMERATED

{
noCAMELCallForwarding (0),
cAMELCallForwarding (1)
}
CAMELModificationParameters ::= SET

--
-- The list contains only parameters changed due to CAMEL call
-- handling.
--
{
callingPartyCategory [1] CallingPartyCategory OPTIONAL,
originalCalledPartyNumber [2] OriginalCalledNumber OPTIONAL,
genericNumbers [3] GenericNumbers OPTIONAL,
redirectingPartyNumber [4] RedirectingNumber OPTIONAL,
redirectionCounter [5] NumberOfForwarding OPTIONAL
}
Category ::= OCTET STRING (SIZE(1))

--
-- The internal structure is defined in ITU-T Rec Q.763.
--see subscribe category
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),
unauthorizedRequestingNetwork (52),
unauthorizedLCSClient (53),
positionMethodFailure (54),
unknownOrUnreachableLCSClient (58)
}
CellId ::= OCTET STRING (SIZE(2))

--
-- Coded according to TS 24.008
--
ChangedParameters ::= SET

{
changeFlags [0] ChangeFlags,
changeList [1] CAMELModificationParameters OPTIONAL
}
ChangeFlags ::= BIT STRING

{
callingPartyNumberModified (0),
callingPartyCategoryModified (1),
originalCalledPartyNumberModified (2),
genericNumbersModified (3),
redirectingPartyNumberModified (4),
redirectionCounterModified (5)
}
ChangeOfClassmark ::= SEQUENCE

{
classmark [0] Classmark,
}
ChangeOfRadioChannel ::= SEQUENCE

{
radioChannel [0] TrafficChannel,
speechVersionUsed [2] SpeechVersionIdentifier OPTIONAL
}
ChangeOfService ::= SEQUENCE

{
basicService [0] BasicServiceCode,
transparencyInd [1] TransparencyInd OPTIONAL,
rateIndication [3] RateIndication OPTIONAL,
fnur [4] Fnur OPTIONAL
}
ChannelCoding ::= ENUMERATED

{

tchF4800 (1),
tchF9600 (2),
tchF14400 (3)
}
ChargeIndicator ::= INTEGER

{
noIndication (0),
noCharge (1),
charge (2)
}
Classmark ::= OCTET STRING

--
-- See Mobile station classmark 2 or 3 TS 24.008
--
ConnectedNumber ::= BCDDirectoryNumber
DataVolume ::= INTEGER

--
-- The volume of data transferred in segments of 64 octets.
--
Day ::= INTEGER (1..31)
--DayClass ::= ObjectInstance
--DayClasses ::= SET OF DayClass
--DayDefinition ::= SEQUENCE

--{
-- day [0] DayOfTheWeek,
-- dayClass [1] ObjectInstance
--}
--DayDefinitions ::= SET OF DayDefinition
--DateDefinition ::= SEQUENCE

--{
-- month [0] Month,
-- day [1] Day,
-- dayClass [2] ObjectInstance
--}
--DateDefinitions ::= SET OF DateDefinition
--DayOfTheWeek ::= ENUMERATED

--{
-- allDays (0),
-- sunday (1),
-- monday (2),
-- tuesday (3),
-- wednesday (4),
-- thursday (5),

-- friday (6),
-- saturday (7)
--}
DestinationRoutingAddress ::= BCDDirectoryNumber
DefaultCallHandling ::= ENUMERATED

{
continueCall (0),
releaseCall (1)
}
-- reception of values in range 2-31 shall be treated as "continueCall"
-- reception of values greater than 31 shall be treated as "releaseCall"
DeferredLocationEventType ::= BIT STRING

{
msAvailable (0)
} (SIZE (1..16))
-- exception handling
-- a ProvideSubscriberLocation-Arg containing other values than listed above in
-- DeferredLocationEventType shall be rejected by the receiver with a return
error cause of
-- unexpected data value.
Diagnostics ::= CHOICE

{
gsm0408Cause [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
}
DefaultSMS-Handling ::= ENUMERATED

{
continueTransaction (0) ,
releaseTransaction (1)
}
-- reception of values in range 2-31 shall be treated as "continueTransaction"
-- reception of values greater than 31 shall be treated as "releaseTransaction"
--Destinations ::= SET OF AE-title
EmergencyCallIndEnable ::= BOOLEAN

EmergencyCallIndication ::= SEQUENCE

{
cellId [0] CellId,
callerId [1] IMSIorIMEI
}
EParameter ::= INTEGER (0..1023)

--
-- Coded according to TS 22.024 and TS 24.080
--
EquipmentId ::= INTEGER
Ext-GeographicalInformation ::= OCTET STRING (SIZE (1..maxExt-

GeographicalInformation))
-- Refers to geographical Information defined in 3G TS 23.032.
-- This is composed of 1 or more octets with an internal structure according to
-- 3G TS 23.032
-- Octet 1: Type of shape, only the following shapes in 3G TS 23.032 are
allowed:
-- (a) Ellipsoid point with uncertainty circle
-- (b) Ellipsoid point with uncertainty ellipse
-- (c) Ellipsoid point with altitude and uncertainty ellipsoid
-- (d) Ellipsoid Arc
-- (e) Ellipsoid Point
-- Any other value in octet 1 shall be treated as invalid
-- Octets 2 to 8 for case (a) - Ellipsoid point with uncertainty circle
-- Degrees of Latitude 3 octets
-- Degrees of Longitude 3 octets
-- Uncertainty code 1 octet
-- Octets 2 to 11 for case (b) - Ellipsoid point with uncertainty ellipse:
-- Uncertainty semi-major axis 1 octet
-- Uncertainty semi-minor axis 1 octet
-- Angle of major axis 1 octet
-- confidence 1 octet
-- Octets 2 to 14 for case (c) - Ellipsoid point with altitude and uncertainty
ellipsoid
-- Altitude 2 octets
-- Uncertainty semi-major axis 1 octet
-- Uncertainty semi-minor axis 1 octet
-- Angle of major axis 1 octet
-- Uncertainty altitude 1 octet
-- Octets 2 to 13 for case (d) - Ellipsoid Arc
-- Inner radius 2 octets
-- Uncertainty radius 1 octet
-- Offset angle 1 octet
-- Included angle 1 octet

-- Octets 2 to 7 for case (e) - Ellipsoid Point
--
-- An Ext-GeographicalInformation parameter comprising more than one octet and
-- containing any other shape or an incorrect number of octets or coding
according
-- to 3G TS 23.032 shall be treated as invalid data by a receiver.
--
-- An Ext-GeographicalInformation parameter comprising one octet shall be
discarded
-- by the receiver if an Add-GeographicalInformation parameter is received
-- in the same message.
--
-- An Ext-GeographicalInformation parameter comprising one octet shall be
treated as
-- invalid data by the receiver if an Add-GeographicalInformation parameter is
not
-- received in the same message.
maxExt-GeographicalInformation INTEGER ::= 20

-- the maximum length allows for further shapes in 3G TS 23.032 to be included
in later
-- versions of 3G TS 29.002
EquipmentType ::= INTEGER

{
conferenceBridge (0)
}
FileType ::= INTEGER

{
callRecords (1),
traceRecords (9),
observedIMEITicket (14)
}
Fnur ::= ENUMERATED

{
--
--
fnurNotApplicable (0),
fnur9600-BitsPerSecond (1),

fnur31200BitsPerSecond (11)
}
ForwardToNumber ::= AddressString
FreeFormatData ::= OCTET STRING (SIZE(1..160))

--
-- Free formated data as sent in the FCI message
-- See TS 29.078
--
GenericNumber ::= BCDDirectoryNumber
GenericNumbers ::= SET OF GenericNumber
Gsm-SCFAddress ::= ISDNAddressString

--
-- See TS 29.002
--
HLRIntResult ::= Diagnostics
Horizontal-Accuracy ::= OCTET STRING (SIZE (1))

-- bit 8 = 0
-- bits 7-1 = 7 bit Uncertainty Code defined in 3G TS 23.032. The horizontal
location
-- error should be less than the error indicated by the uncertainty code with
67%
-- confidence.
HotBillingTag ::= INTEGER

{
noHotBilling (0),
hotBilling (1)
}
HSCSDParmsChange ::= SEQUENCE

{
hSCSDChanAllocated [1] NumOfHSCSDChanAllocated,
initiatingParty [2] InitiatingParty
OPTIONAL,
aiurRequested [3] AiurRequested OPTIONAL,
chanCodingUsed [4] ChannelCoding,
hSCSDChanRequested [5] NumOfHSCSDChanRequested OPTIONAL
}
IMEI ::= TBCD-STRING (SIZE (8))

-- Refers to International Mobile Station Equipment Identity
-- and Software Version Number (SVN) defined in TS GSM 03.03.
-- If the SVN is not present the last octet shall contain the
-- digit 0 and a filler.
-- If present the SVN shall be included in the last octet.
IMSI ::= TBCD-STRING (SIZE (3..8))

-- digits of MCC, MNC, MSIN are concatenated in this order.
IMEICheckEvent ::= INTEGER

{
mobileOriginatedCall (0),
mobileTerminatedCall (1),
smsMobileOriginating (2),
smsMobileTerminating (3),
ssAction (4),
locationUpdate (5)
}
IMEIStatus ::= ENUMERATED

{
greyListedMobileEquipment (0),
blackListedMobileEquipment (1),
nonWhiteListedMobileEquipment (2)
}
IMSIorIMEI ::= CHOICE

{
imsi [0] IMSI,
imei [1] IMEI
}
InitiatingParty ::= ENUMERATED

{
network (0),
subscriber (1)
}
ISDN-AddressString ::= AddressString (SIZE (1..maxISDN-AddressLength))

-- This type is used to represent ISDN numbers.
maxISDN-AddressLength INTEGER ::= 9
LCSCause ::= OCTET STRING (SIZE(1))

--
-- See LCS Cause Value, 3GPP TS 49.031
--
LCS-Priority ::= OCTET STRING (SIZE (1))

-- 0 = highest priority
-- 1 = normal priority
-- all other values treated as 1
LCSClientIdentity ::= SEQUENCE

{
lcsClientExternalID [0] LCSClientExternalID OPTIONAL,
lcsClientDialedByMS [1] AddressString OPTIONAL,
lcsClientInternalID [2] LCSClientInternalID 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)
}
-- for a CAMEL phase 3 PLMN operator client, the value
targetMSsubscribedService shall be used
LCSClientType ::= ENUMERATED

{
emergencyServices (0),
valueAddedServices (1),
plmnOperatorServices (2),
lawfulInterceptServices (3)
}
-- unrecognized values may be ignored if the LCS client uses the privacy
override
-- otherwise, an unrecognized value shall be treated as unexpected data by a
receiver
-- a return error shall then be returned if received in a MAP invoke
LCSQoSInfo ::= SEQUENCE

{
horizontal-accuracy [0] Horizontal-Accuracy OPTIONAL,
verticalCoordinateRequest [1] NULL OPTIONAL,
vertical-accuracy [2] Vertical-Accuracy OPTIONAL,
responseTime [3] ResponseTime OPTIONAL
}
LevelOfCAMELService ::= BIT STRING
{
basic (0),
callDurationSupervision (1),
onlineCharging (2)
}
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 ::= OCTET STRING (SIZE(2))

--
-- See TS 24.008
--
LocationChange ::= SEQUENCE

{
location [0] LocationAreaAndCell,
}
Location-info ::= SEQUENCE

{
mscNumber [1] MscNo OPTIONAL,
location-area [2] LocationAreaCode,
cell-identification [3] CellId OPTIONAL
}
LocationType ::= SEQUENCE

{
locationEstimateType [0] LocationEstimateType,
deferredLocationEventType [1] DeferredLocationEventType OPTIONAL
}
LocationEstimateType ::= ENUMERATED

{
currentLocation (0),
currentOrLastKnownLocation (1),
initialLocation (2),
activateDeferredLocation (3),
cancelDeferredLocation (4)
}
-- a ProvideSubscriberLocation-Arg containing an unrecognized
LocationEstimateType
-- shall be rejected by the receiver with a return error cause of unexpected
data value
LocUpdResult ::= Diagnostics
ManagementExtensions ::= SET OF ManagementExtension
ManagementExtension ::= SEQUENCE

{
identifier OBJECT IDENTIFIER,
significance [1] BOOLEAN DEFAULT FALSE,
information [2] OCTET STRING
}
MCCMNC ::= OCTET STRING(SIZE(3))

--
-- This type contains the mobile country code (MCC) and the mobile
-- network code (MNC) of a PLMN.
--

RateIndication ::= OCTET STRING(SIZE(1))
--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
--11 PIAFS
MessageReference ::= OCTET STRING
Month ::= INTEGER (1..12)
MOLR-Type ::= INTEGER
MSCAddress ::= AddressString
MscNo ::= ISDN-AddressString

--
-- See TS 23.003
--
MSISDN ::= ISDN-AddressString

--
-- See TS 23.003
--
MSPowerClasses ::= SET OF RFPowerCapability
NetworkCallReference ::= CallReferenceNumber

-- See TS 29.002
--
NetworkSpecificCode ::= INTEGER

--
-- To be defined by network operator
--
NetworkSpecificServices ::= SET OF NetworkSpecificCode
NotificationToMSUser ::= ENUMERATED

{
notifyLocationAllowed (0),
notifyAndVerify-LocationAllowedIfNoResponse (1),
notifyAndVerify-LocationNotAllowedIfNoResponse (2),
locationNotAllowed (3)
}
-- At reception of any other value than the ones listed the receiver shall
ignore
-- NotificationToMSUser.
NumberOfForwarding ::= INTEGER (1..5)
NumOfHSCSDChanRequested ::= INTEGER
NumOfHSCSDChanAllocated ::= INTEGER

ObservedIMEITicketEnable ::= BOOLEAN
OriginalCalledNumber ::= BCDDirectoryNumber
OriginDestCombinations ::= SET OF OriginDestCombination
OriginDestCombination ::= SEQUENCE

{
origin [0] INTEGER OPTIONAL,
destination [1] INTEGER OPTIONAL
--
-- Note that these values correspond to the contents
-- of the attributes originId and destinationId
-- respectively. At least one of the two must be present.
--
}
PartialRecordTimer ::= INTEGER
PartialRecordType ::= ENUMERATED

{
timeLimit (0),
serviceChange (1),
locationChange (2),
classmarkChange (3),
aocParmChange (4),
radioChannelChange (5),
hSCSDParmChange (6),
changeOfCAMELDestination (7),
firstHotBill (20),
severalSSOperationBill (21)
}
PartialRecordTypes ::= SET OF PartialRecordType
PositioningData ::= OCTET STRING (SIZE(1..33))

--
-- See Positioning Data IE (octet 3..n), 3GPP TS 49.031
--
RadioChannelsRequested ::= SET OF RadioChanRequested
RadioChanRequested ::= ENUMERATED

{
--
--
halfRateChannel (0),
fullRateChannel (1),
dualHalfRatePreferred (2),
dualFullRatePreferred (3)
}
--RecordClassDestination ::= CHOICE

--{
-- osApplication [0] AE-title,
-- fileType [1] FileType
--}
--RecordClassDestinations ::= SET OF RecordClassDestination
RecordingEntity ::= AddressString
RecordingMethod ::= ENUMERATED

{
inCallRecord (0),
inSSRecord (1)
}
RedirectingNumber ::= BCDDirectoryNumber
RedirectingCounter ::= INTEGER
ResponseTime ::= SEQUENCE

{
responseTimeCategory ResponseTimeCategory
}
-- note: an expandable SEQUENCE simplifies later addition of a numeric
response time.
ResponseTimeCategory ::= ENUMERATED

{
lowdelay (0),
delaytolerant (1)
}
-- an unrecognized value shall be treated the same as value 1
(delaytolerant)
RFPowerCapability ::= INTEGER

--
-- This field contains the RF power capability of the Mobile station
-- classmark 1 and 2 of TS 24.008 expressed as an integer.
--
RoamingNumber ::= ISDN-AddressString

--
-- See TS 23.003
--
RoutingNumber ::= CHOICE

{
roaming [1] RoamingNumber,
forwarded [2] ForwardToNumber
}
Service ::= CHOICE

{
teleservice [1] TeleserviceCode,


supplementaryService [3] SS-Code,
networkSpecificService [4] NetworkSpecificCode
}
ServiceDistanceDependencies ::= SET OF ServiceDistanceDependency
ServiceDistanceDependency ::= SEQUENCE

{
aocService [0] INTEGER,
chargingZone [1] INTEGER OPTIONAL
--
-- Note that these values correspond to the contents
-- of the attributes aocServiceId and zoneId
-- respectively.
--
}
ServiceKey ::= INTEGER (0..2147483647)
SimpleIntegerName ::= INTEGER
SimpleStringName ::= GraphicString
SMSResult ::= Diagnostics
SmsTpDestinationNumber ::= OCTET STRING

--
-- This type contains the binary coded decimal representation of
-- the SMS address field the encoding of the octet string is in
-- accordance with the definition of address fields in TS 23.040.
-- This encoding includes type of number and numbering plan indication
-- together with the address value range.
--
SpeechVersionIdentifier ::= OCTET STRING (SIZE(1))

-- see GSM 08.08
-- 000 0001 GSM speech full rate version 1

-- 001 0001 GSM speech full rate version 2 used for enhanced full rate
-- 010 0001 GSM speech full rate version 3 for future use
-- 000 0101 GSM speech half rate version 1
SSActionResult ::= Diagnostics
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
--SS Request = SSActionType
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 [5]. The internal structure is
-- defined as follows:
--
-- bits 87654321: group (bits 8765), and specific service
-- (bits 4321) ussd = ff
-- allSS (0x00),
-- all SS
--
-- allLineIdentificationSS (0x10),
-- all line identification SS
--
--calling-line-identification-presentation (0x11),
-- calling line identification presentation
--calling-line-identification-restriction (0x12),
-- calling line identification restriction
--connected-line-identification-presentation (0x13),
-- connected line identification presentation
--connected-line-identification-restriction (0x14),
-- connected line identification restriction
-- malicious-call-identification (0x15),
-- malicious call identification
--
-- allNameIdentificationSS (0x18),
-- all name identification SS
--calling-name-presentation (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 (0x31),
-- explicit call transfer
-- mobile-access-hunting (0x32),
-- mobile access hunting
--
-- allCallCompletionSS (0x40),
-- all Call completion SS
--
--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 (0x45),
-- multicall
--
-- allMultiPartySS (0x50),
-- all multiparty SS
--
-- multiPTY (0x51),
-- multiparty
--
-- allCommunityOfInterest-SS (0x60),
-- 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
--
-- 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
(0xa1),
-- 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
-- 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 (0xf0),
-- plmn-specificSS-A (0xfa),
-- plmn-specificSS-B (0xfb),
-- plmn-specificSS-C (0xfc),
-- plmn-specificSS-D (0xfd),
-- plmn-specificSS-E (0xfe),
-- ussd (0xff)
SSParameters ::= CHOICE

{
forwardedToNumber [0] ForwardToNumber,
unstructuredData [1] OCTET STRING
}
SupplServices ::= SET OF SS-Code
SuppServiceUsed ::= SEQUENCE

{
ssCode [0] SS-Code OPTIONAL,
ssTime [1] TimeStamp OPTIONAL
}
SwitchoverTime ::= SEQUENCE

{
hour INTEGER (0..23),
minute INTEGER (0..59),
second INTEGER (0..59)
}
SystemType ::= ENUMERATED

-- "unknown" is not to be used in PS domain.
{
unknown (0),
iuUTRAN (1),
gERAN (2)
}
TBCD-STRING ::= OCTET STRING

-- This type (Telephony Binary Coded Decimal String) is used to
-- represent several digits from 0 through 9, *, #, a, b, c, two
-- digits per octet, each digit encoded 0000 to 1001 (0 to 9),

-- 1010 (*), 1011 (#), 1100 (a), 1101 (b) or 1110 (c); 1111 used
-- as filler when there is an odd number of digits.
-- bits 8765 of octet n encoding digit 2n

-- bits 4321 of octet n encoding digit 2(n-1) +1
TariffId ::= INTEGER
TariffPeriod ::= SEQUENCE

{
switchoverTime [0] SwitchoverTime,
tariffId [1] INTEGER
-- Note that the value of tariffId corresponds
-- to the attribute tariffId.
}
TariffPeriods ::= SET OF TariffPeriod
TariffSystemStatus ::= ENUMERATED

{
available (0), -- available for modification
checked (1), -- "frozen" and checked
standby (2), -- "frozen" awaiting activation
active (3) -- "frozen" and active
}

--
-- where
--
TrafficChannel ::= ENUMERATED

{
fullRate (0),
halfRate (1)
}
TranslatedNumber ::= BCDDirectoryNumber
TransparencyInd ::= ENUMERATED

{
transparent (0),
nonTransparent (1)
}
ROUTE ::= cHOICE

{
rOUTENumber [0] INTEGER,
rOUTEName [1] GraphicString
}
--rOUTEName 1 10 octet
TSChangeover ::= SEQUENCE

{
newActiveTS [0] INTEGER,
newStandbyTS [1] INTEGER,
--changeoverTime [2] GeneralizedTime OPTIONAL,
authkey [3] OCTET STRING OPTIONAL,
checksum [4] OCTET STRING OPTIONAL,
versionNumber [5] OCTET STRING OPTIONAL
-- Note that if the changeover time is not
-- specified then the change is immediate.
}
TSCheckError ::= SEQUENCE

{
errorId [0] TSCheckErrorId
--fail [1] ANY DEFINED BY errorId OPTIONAL
}
TSCheckErrorId ::=cHOICE
{
globalForm [0] OBJECT IDENTIFIER,
localForm [1] INTEGER
}
TSCheckResult ::=cHOICE
{
success [0] NULL,
fail [1] SET OF TSCheckError
}
TSCopyTariffSystem ::= SEQUENCE

{
oldTS [0] INTEGER,
newTS [1] INTEGER
}
TSNextChange ::=cHOICE
{
noChangeover [0] NULL,
tsChangeover [1] TSChangeover
}

TypeOfSubscribers ::= ENUMERATED

{
home (0), -- HPLMN subscribers
visiting (1), -- roaming subscribers
all (2)
}
TypeOfTransaction ::= ENUMERATED

{
successful (0),
unsuccessful (1),
all (2)
}
Vertical-Accuracy ::= OCTET STRING (SIZE (1))

-- bit 8 = 0
-- bits 7-1 = 7 bit Vertical Uncertainty Code defined in 3G TS 23.032.
-- The vertical location error should be less than the error indicated
-- by the uncertainty code with 67% confidence.
ISDNAddressString ::= AddressString
EmlppPriority ::= OCTET STRING (SIZE (1))

-- priority level

SubscriberEmlppPriority ::= OCTET STRING (SIZE (1))

-- priority level

CallEmlppPriority ::= OCTET STRING (SIZE (1))

--no priority applied 0


--call priority level B 6
--call priority level A 7
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.
SelectedCIC ::= OCTET STRING (SIZE (3))
PortedFlag ::= ENUMERATED

{
numberNotPorted (0),
numberPorted (1)
}
SubscriberCategory ::= OCTET STRING (SIZE (1))

-- unknownuser = 0x00,
-- frenchuser = 0x01,
-- englishuser = 0x02,
-- germanuser = 0x03,
-- russianuser = 0x04,
-- spanishuser = 0x05,
-- specialuser = 0x06,
-- reserveuser = 0x09,
-- commonuser = 0x0a,
-- superioruser = 0x0b,
-- datacalluser = 0x0c,
-- testcalluser = 0x0d,
-- spareuser = 0x0e,
-- payphoneuser = 0x0f,
-- coinuser = 0x20,
-- isup224 = 0xe0
CUGOutgoingAccessIndicator ::= ENUMERATED

{
notCUGCall (0),
cUGCall (1)
}
CUGInterlockCode ::= OCTET STRING (SIZE (4))
--
CUGOutgoingAccessUsed ::= ENUMERATED

{

}
SMSTEXT ::= OCTET STRING
MSCCIC ::= INTEGER(0..65535)
RNCorBSCId ::= OCTET STRING(SIZE (3))

--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
MSCId ::= OCTET STRING(SIZE (3))

--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
EmergencyCallFlag ::= ENUMERATED

{
notEmergencyCall (0),
emergencyCall (1)
}
CUGIncomingAccessUsed ::= ENUMERATED

{
}
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 (see subclause 3.10)
--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
ConcatenatedSMSReferenceNumber ::= INTEGER(0..65535)
MaximumNumberOfSMSInTheConcatenatedSMS ::= INTEGER(0..255)
SequenceNumberOfTheCurrentSMS ::= INTEGER(0..255)
SequenceNumber ::= INTEGER
--(1... )
--
DisconnectParty ::= ENUMERATED

{
callingPartyRelease (0),
calledPartyRelease (1),
networkRelease (2)
}
ChargedParty ::= ENUMERATED

{
callingParty (0),
calledParty (1)
}
ChargeAreaCode ::= OCTET STRING(SIZE (1..3))
CUGIndex ::= OCTET STRING(SIZE (2))
GuaranteedBitRate ::= ENUMERATED

{
gBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,



gBR4750BitsPerSecond (113) -- AMR speech
}
MaximumBitRate ::= ENUMERATED

{
mBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,

mBR4750BitsPerSecond (113) -- AMR speech
}
HLC ::= OCTET STRING
-- this parameter is a 1:1 copy of the contents (i.e. starting with octet 3) of the
"high layer compatibility" parameter of ITU-T Q.931 [35].
LLC ::= OCTET STRING
"low layer compatibility" parameter of ITU-T Q.931 [35].
"bearer capability" parameter of ITU-T Q.931 [35].
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)
}
UssdCodingScheme ::= OCTET STRING
UssdString ::= OCTET STRING
UssdNotifyCounter ::= INTEGER(0..255)
UssdRequestCounter ::= INTEGER(0..255)

Classmark3 ::= OCTET STRING(SIZE(2))
OptimalRoutingDestAddress ::= BCDDirectoryNumber
GAI ::= OCTET STRING(SIZE(7))

--such as 64 F0 00 00 ABCD 1234
ChangeOfglobalAreaID ::= SEQUENCE

{
location [0] GAI,
}
InteractionWithIP ::= NULL

{
cas (0),
tup (1),
isup (2),
pra (3),
bicc (4),
sip (5),
others (255)
}
VoiceIndicator ::= ENUMERATED

{
sendToneByLocalMsc (0) ,
sendToneByOtherMsc (1),
voiceNoIndication (3)
}
BCategory ::= ENUMERATED

{

subscriberFree (0),
subscriberBusy (1),
subscriberNoIndication (3)
}
CallType ::= ENUMERATED

{
unknown (0),
internal (1),
incoming (2),
outgoing (3),
tandem (4)
}
END
A.8 Examples of CDR

The following present the CDR ans.1 code of voice call,vp call, bear service call , sms,
Interrogation, USSD, Supplementary service, Emergency records and so on.
A.8.1 Voice Call

MOC Record
ASN.1 BER Code (Example--moCallRecord.dat)
Figure 1.1 Example--moCallRecord.dat
Decoding (Example-- moCallRecord.txt)

record no.: 0
recordType: moCallRecord
servedIMSI: 460077690000042

servedIMEI: 350654670244160
servedMSISDN: (91)8613907520027
callingNumber: (A1)13907520027
calledNumber: (81)13907520369
roamingNumber: (A1)13900022063
recordingEntity: (91)8613900022
mscIncomingROUTE: RNC
mscOutgoingROUTE: RNC
location: LAC-2512. CellID-0000
basicService: teleService(11)
msClassmark: 1F034F
answerTime: 040806195446
releaseTime: 040806195456
callDuration: 10
causeForTerm: normalRelease
diagnostics: gsm0408Cause(90)
callReference: 16 00 00 00 01
additionalChgInfo: chargeIndicator-charge
networkcallReference: 5800830800AA
mSCAddress: (91)8613900022
systemType: iuUTRAN
chargedParty: callingParty
orgRNCorBSCId: 00 07
orgMSCId: 08 0A
globalAreaID: 64 F0 23 25 12 00 00
subscriberCategory: Common(A)
firstmccmnc: 64F023
lastmccmnc: 64F023
MTC Record
ASN.1 BER Code (Example--mtCallRecord.dat)

Figure 1.1 Example--mtCallRecord.dat
Decoding (Example--mtCallRecord.txt)
record no.: 0
recordType: mtCallRecord
servedIMSI: 460077690000042
servedIMEI: 350654670244160
servedMSISDN: (91)8613907520027
supplServicesUsed: {ssTime: 040806200130. ssCode: clip(11). }
msClassmark: 1F034F
callDuration: 17
networkcallReference: 5800A40800AA
mSCAddress: (91)8613900022

systemType: iuUTRAN
chargedParty: calledParty
orgMSCId: 08 0A
globalAreaID: 64 F0 23 25 12 00 00
firstmccmnc: 64F023
lastmccmnc: 64F023
A.8.2 VP Call
MOC record
Key field:
Rate Indication: H.223 & H.245
Fixed Network User Rate: such as 64K (optional)
Transparency Indicator: such as transparent (optional)
ASN.1 BER Code (Example—moCallRecord(VP).dat)
Figure 1.2 Example—moCallRecord(VP).dat
Decoding (Example—moCallRecord(VP).txt)
record no.: 0
servedIMSI: 460077552000547
servedIMEI: 352711002055010
servedMSISDN: (91)8613907550547

mscIncomingROUTE: To RNC-9
mscOutgoingROUTE: To RNC-9
basicService: bearerService(1F)
transparencyIndicator: transparent
supplServicesUsed: {ssTime: 040723153416. ssCode: clir(12). }
msClassmark: 1F034F
callDuration: 26
networkcallReference: 00005802B444
mSCAddress: (91)8613900444
fnur: fnur64000BitsPerSecond
systemType: iuUTRAN
rateIndication: H.223 & H.245(7)
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00
firstmccmnc: 64F008
lastmccmnc: 64F008
A.8.3 Other Bear Service Call

MOC record
Basic service: 0x17 or 0x1F in UMTS data service

Other service code in GSM data service

Fixed Network User Rate: such as 64K
Air Interface User Rate Requested: such as 56K
Rate Indication: such as V.110, I.460/X.30
Transparency Indicator: such as non transparent
Modem type: such as modem-autobauding1
Maximum bit rate: such as 64000BitsPerSecond
Guaranteed bit rate: such as 64000BitsPerSecond
ASN.1 BER Code (Example—moCallRecord(BS).dat)
Figure 1.3 Example—moCallRecord(BS).dat
Decoding (Example—moCallRecord(BS).txt)
record no.: 0
servedIMSI: 460077552000547
servedIMEI: 352711002055010
servedMSISDN: (91)8613907550547
mscOutgoingROUTE: To RNC-9

basicService: bearerService(17)
transparencyIndicator: not transparent
supplServicesUsed: {ssTime: 040723153416. ssCode: clir(12). }
msClassmark: 1F034F
callDuration: 26
networkcallReference: 00005802B444
mSCAddress: (91)8613900444
fnur: fnur64000BitsPerSecond
systemType: iuUTRAN
rateIndication: V.110, I.460/X.30(1)
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00
firstmccmnc: 64F008
lastmccmnc: 64F008
A.8.4 Forwarding Record

Forwarding record
ASN.1 BER Code (Example—forwardCallRecord(cfnry).dat)

Figure 1.4 Example—forwardCallRecord(cfnry).dat
Decoding (Example—forwardCallRecord(cfnry).txt)
record no.: 0
recordType: forwardCallRecord
servedIMSI: 460077552000395
servedIMEI: 352711006979220
servedMSISDN: (91)13907520395
callingNumber: (91)13907520395
calledNumber: (A1)13907520369
connectedNumber: (91)7556660066
mscIncomingROUTE: SX_MSRV
supplServicesUsed: {ssTime: 040818102805. ssCode: clip(11). }{ssTime: 040818102805.
ssCode: cfnry(2A). }
msClassmark: 1F0357
callDuration: 16

networkcallReference: 00 00 58 00 82 08
mSCAddress: (91)8613900022
systemType: iuUTRAN
originalCalledNumber: (A1)13907520395
orgMSCId: 08 0A
globalAreaID: 64 60 54 25 12 00 00
firstmccmnc: 646054
lastmccmnc: 646054
A.8.5 Emergency Record

Emergency call MOC record
ASN.1 BER Code (Example—moCallRecord(EmergencyCallWithoutSIM).dat)
Figure 1.5 Example—moCallRecord(EmergencyCallWithoutSIM).dat
Decoding (Example—moCallRecord(EmergencyCallWithoutSIM).txt)
record no.: 0
servedIMEI: 350654670244080
servedMSISDN: (80)350654670244080

translatedNumber: (C1)6660001
mscOutgoingROUTE: toPSTN
msClassmark: 1F034F
callDuration: 17
callReference: 1F 00 00 00 0F
networkcallReference: 00007C018B66
mSCAddress: (91)8613900555
systemType: iuUTRAN
mscOutgoingCircuit: 8
firstmccmnc: 64F072
lastmccmnc: 64F072
A.8.6 Middle Billing

How to Judge Partial Record and Last Record
Partial record :
cause for termination = partial Record / partial Record Call Reestablishment
last record:=
cause for termination != partial Record / partial Record Call Reestablishment
such as normal Release/ unsuccessful Call Attempt…
Partial Record1
ASN.1 BER Code (Example—moCallRecord(partial1).dat)

Figure 1.1 Example—moCallRecord(partial1).dat
Decoding (Example—moCallRecord(partial1).txt)
record no.: 0
servedIMSI: 460077552000548
servedIMEI: 352711000794240
servedMSISDN: (91)8613907550548
mscOutgoingROUTE: NoName
msClassmark: 1F034F
callDuration: 300
causeForTerm: partialRecord
diagnostics: gsm0408Cause(9F)
callReference: 16 00 00 00 0F
sequenceNumber: 1

networkcallReference: 000058084044
mSCAddress: (91)8613900444
systemType: iuUTRAN
partialRecordType: timeLimit
orgMSCId: 44 0B
firstmccmnc: 64F008
lastmccmnc: 64F008
Partial Record2
record no.: 0
servedIMSI: 460077552000548
servedIMEI: 352711000794240
servedMSISDN: (91)8613907550548

msClassmark: 1F034F
callDuration: 300
causeForTerm: partialRecord
diagnostics: gsm0408Cause(9F)
sequenceNumber: 2
mSCAddress: (91)8613900444
systemType: iuUTRAN
partialRecordType: timeLimit
orgMSCId: 44 0B
firstmccmnc: 64F008
lastmccmnc: 64F008
Partial Record3

record no.: 0
servedIMSI: 460077552000548
servedIMEI: 352711000794240
servedMSISDN: (91)8613907550548
msClassmark: 1F034F
callDuration: 285
sequenceNumber: 3

mSCAddress: (91)8613900444
systemType: iuUTRAN
orgMSCId: 44 0B
firstmccmnc: 64F008
lastmccmnc: 64F008
A.8.7 SMS
SMS MOC Record
ASN.1 BER Code (Example—moSMSRecord.dat)
Figure 1.1 Example—moSMSRecord.dat
Decoding (Example—moSMSRecord.txt)
record no.: 0
recordType: moSMSRecord
servedIMSI: 460881104002797
servedIMEI: 350654670244080
servedMSISDN: (91)8613907521002
msClassmark: 4F1880
serviceCentre: (91)8613900007555
messageReference: 60

originationTime: 040723173725
destinationNumber: (81)13907550548
systemType: iuUTRAN
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00
firstmccmnc: 64F008
smsUserDataType: FF
SMS MTC Record

ASN.1 BER Code (Example—mtSMSRecord.dat)
Figure 1.1 Example—mtSMSRecord.dat
Decoding (Example—mtSMSRecord.txt)
record no.: 0
recordType: mtSMSRecord
servedIMSI: 460077552000548
servedIMEI: 352711000794240
servedMSISDN: (91)8613907550548
msClassmark: 4F1880

deliveryTime: 040723173935
systemType: iuUTRAN
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00
firstmccmnc: 64F008
smsUserDataType: FF
origination number: (91)8613907521002
A.8.8 Concatenated Long SMS

SMS MOC record
ASN.1 BER Code
 Example1—moSMSRecord(partial1).dat
Figure 1.2 Example1—moSMSRecord(partial1).dat

Decoding
 Example1—moSMSRecord(partial1).txt
record no.: 0
servedIMSI: 460881104002797
servedIMEI: 350654670244080
servedMSISDN: (91)8613907521002
msClassmark: 4F1880

systemType: iuUTRAN
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00
firstmccmnc: 64F008
smsUserDataType: FF
maximumNumberOfSMSInTheConcatenatedSMS: 3
concatenatedSMSReferenceNumber: 17
sequenceNumberOfTheCurrentSMS: 1
record no.: 0
servedIMSI: 460881104002797
servedIMEI: 350654670244080
servedMSISDN: (91)8613907521002
msClassmark: 4F1880
systemType: iuUTRAN
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00

firstmccmnc: 64F008
smsUserDataType: FF
record no.: 0
servedIMSI: 460881104002797
servedIMEI: 350654670244080
servedMSISDN: (91)8613907521002
msClassmark: 4F1880
systemType: iuUTRAN
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00
firstmccmnc: 64F008
smsUserDataType: FF

A.8.9 Interrogation
ASN.1 BER Code (Example—hlrRecord.dat)
Figure 1.5 Example—hlrRecord.dat
Decoding (Example—hlrRecord.txt)
record no.: 0
recordType: hlrIntRecord
servedIMSI: 460077552000369
servedMSISDN: (91)8613907520369
routingNumber: (91)8613900022020
interrogationTime: 040818101614
orgMSCId: 08 0A
A.8.10 USSD
ASN.1 BER Code (Example—ssActionRecord(USSD).dat)
Figure 1.6 Example—ssActionRecord(USSD).dat
Decoding (Example—ssActionRecord(USSD).txt)
record no.: 0
recordType: ssActionRecord
servedIMSI: 460077552000369

servedIMEI: 350654670244270
servedMSISDN: (91)8613907520369
msClassmark: 4F1880
supplService: allSS(0)
ssAction: USSD INVOCATION(7)
ssActionTime: 040817091859
ssParameters: {unstructuredData-A3 58 2C 36 02 }
callReference: 00 00 59 F3 FC 0A
systemType: iuUTRAN
ussdCodingScheme: 0F
ussdString: { A3 58 2C 36 02}
ussdNotifyCounter: 0
ussdRequestCounter: 1
firstmccmnc: 646054
orgMSCId: 08 0A
globalAreaID: 64 60 54 25 12 00 00
A.8.11 Supplementary Service

Forward Registration
ASN.1 BER Code (Example—ssActionRecord(forward registration).dat)

Figure 1.1 Example—ssActionRecord(forward registration).dat
Decoding (Example—ssActionRecord(forward registration).txt)

record no.: 0
servedIMSI: 460077552000548
servedIMEI: 352711000794240
servedMSISDN: (91)8613907550548
msClassmark: 4F1880
basicServices: {teleService(10)}
supplService: cfb(29)
ssAction: registration(0)
ssParameters: {forwardedToNumber-(91)867556660001}
systemType: iuUTRAN
ussdString: { 91 68 57 65 66 00 10}
firstmccmnc: 64F008
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00

BAOC Activation
ASN.1 BER Code (Example—ssActionRecord(BAOC activation).dat)
Figure 1.1 Example—ssActionRecord(BAOC activation).dat
Decoding (Example—ssActionRecord(BAOC activation).txt)

record no.: 0
servedIMSI: 460077552000548
servedIMEI: 352711000794240
servedMSISDN: (91)8613907550548
msClassmark: 4F1880
supplService: baoc(92)
ssAction: activation(2)
systemType: iuUTRAN
firstmccmnc: 64F008
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00

BAOC Deactivation
ASN.1 BER Code (Example—ssActionRecord(BAOC deactivation).dat)
Figure 1.1 Example—ssActionRecord(BAOC deactivation).dat
Decoding (Example—ssActionRecord(BAOC deactivation).txt)

record no.: 0
servedIMSI: 460077552000548
servedIMEI: 352711000794240
servedMSISDN: (91)8613907550548
msClassmark: 4F1880
supplService: barringOfOutgoingCalls(91)
ssAction: deactivation(3)
systemType: iuUTRAN
firstmccmnc: 64F008
orgMSCId: 44 0B
globalAreaID: 64 F0 08 25 12 00 00

A.8.12 Handover
MOC record
ASN.1 BER Code (Example—moCallRecord(Handover).dat)
Figure 1.1 Example—moCallRecord(Handover).dat
Decoding (Example—moCallRecord(Handover).txt)
record no.: 1
servedIMSI: 460077552000369
servedIMEI: 350654670244270
servedMSISDN: (91)8613907520369
mscOutgoingROUTE: B-SWITCH
changeOfLocation: {changeTime: 040814191301. location: LAC-2513. CellID-FFFF.}
supplServicesUsed: {ssTime: 040814191214. ssCode: hold(42). }{ssTime: 040814191307.
ssCode: hold(42). }
msClassmark: 1F034F

callDuration: 88
mSCAddress: (91)8613900022
systemType: iuUTRAN
orgMSCId: 08 0A
globalAreaID: 64 F0 23 25 12 00 00
changeOfGlobalAreaID: {changeTime: 040814191301. location: 64 F0 23 25 13 FF FF.}
firstmccmnc: 64F023
lastmccmnc: 64F023
A.8.13 CommonEquipRecord
ASN.1 BER Code (Example—commonEquipRecord.dat)
Figure 1.2 Example—commonEquipRecord.dat
Decoding (Example—commonEquipRecord.txt)
record no.: 0
recordType: commonEquipRecord

equipmentType: conferenceBridge
equipmentId: 1F71
servedIMSI: 460077552000369
servedMSISDN: (91)8613907520369
supplServicesUsed: {ssTime: 040817110011. ssCode: multiPTY(51). }
seizureTime: 040817110011
callDuration: 11
callReference: 00 00 7C 0E 23 0A 08 FF
systemType: iuUTRAN
servedIMEI: 350654670244270
orgMSCId: 08 0A
A.8.14 IncGatewayRecord
ASN.1 BER Code (Example—incGatewayRecord.dat)
Figure 1.3 Example—incGatewayRecord.dat
Decoding (Example—incGatewayRecord.txt)
record no.: 0
recordType: incGatewayRecord

mscIncomingROUTE: B-SWITCH
callDuration: 13
callReference: 16 00 00 00 1C
mscIncomingCircuit: 1F
orgMSCId: 08 0A
A.8.15 OutGatewayRecord
ASN.1 BER Code (Example—outGatewayRecord.dat)
Figure 1.4 Example—outGatewayRecord.dat
Decoding (Example—outGatewayRecord.txt)
record no.: 0
recordType: outGatewayRecord
mscOutgoingROUTE: B-SWITCH

callDuration: 9
callReference: 16 00 00 00 1B
orgMSCId: 08 0A
A.8.16 TransitCallRecord
ASN.1 BER Code (Example—transitCallRecord.dat)
Figure 1.5 Example—transitCallRecord.dat
Decoding (Example—transitCallRecord.txt)
record no.: 0
recordType: transitCallRecord
mscIncomingROUTE: New-MSIG1
answerTimestamp: 040807160431
releaseTimestamp: 040807160435
callDuration: 4

mscIncomingCircuit: 12
orgMSCId: 08 0A
A.8.17 RoamingRecord
ASN.1 BER Code (Example—roamingRecord.dat)
Figure 1.6 Example—roamingRecord.dat
Decoding (Example—roamingRecord.txt)
record no.: 0
recordType: roamingRecord
servedIMSI: 460077552000547
servedMSISDN: (91)8613907550547
callDuration: 12

callReference: 16 00 00 00 2E
networkcallReference: 0000580DFF44
mSCAddress: (91)8613900444
A.8.18 Moc(CAMEL)
ASN.1 BER Code (Example—moCallRecord(camel).dat)
Figure 1.7 Example—moCallRecord(camel).dat
Decoding (Example—moCallRecord(camel).txt)
record no.: 0
servedIMSI: 460077552000369
servedIMEI: 350654670244270
servedMSISDN: (91)8613907520369

msClassmark: 1F034F
callDuration: 25
gsm_SCFAddress: (91)8613900128
serviceKey: 3
mSCAddress: (91)8613900022
numberOfDPEncountered: 2
levelOfCAMELService: callDurationSupervision
freeFormatData: 800130
systemType: iuUTRAN
orgMSCId: 08 0A
globalAreaID: 64 60 54 25 12 00 00
firstmccmnc: 646054
lastmccmnc: 646054
A.8.19 Mtc(CAMEL)
ASN.1 BER Code (Example—mtCallRecord(camel).dat)

Figure 1.8 Example—mtCallRecord(camel).dat
Decoding (Example—mtCallRecord(camel).txt)
record no.: 0
recordType: mtCallRecord
servedIMSI: 460077552000369
servedIMEI: 350654670244270
servedMSISDN: (91)8613907520369
msClassmark: 1F034F
callDuration: 50

serviceKey: 3
networkcallReference: 00 00 58 03 DE 08
mSCAddress: (91)8613900022
systemType: iuUTRAN
orgMSCId: 08 0A
globalAreaID: 64 60 54 25 12 00 00
firstmccmnc: 646054
lastmccmnc: 646054
A.8.20 TCAMEL
ASN.1 BER Code (Example—termCAMELRecord.dat)
Figure 1.9 Example—termCAMELRecord.dat
Decoding (Example—termCAMELRecord.txt)
record no.: 0
recordType: termCAMELRecord
servedIMSI: 460077552000369
servedMSISDN: (91)8613907520369
interrogationTime: 040817092812

serviceKey: 3
networkcallReference: 00 00 58 03 BD 08
mSCAddress: (91)8613900022
callDuration: 17
orgMSCId: 08 0A
A.8.21 Moc(FCI)
ASN.1 BER Code (Example—moc(withFCI).dat)

Figure 1.10 Example—moc(withFCI).dat
Decoding (Example—moc(withFCI).txt)
record no.: 0
servedIMSI: 460077552000369
servedIMEI: 350654670244270
servedMSISDN: (91)8613907520369
msClassmark: 1F034F
callDuration: 25

serviceKey: 3
mSCAddress: (91)8613900022
systemType: iuUTRAN
orgMSCId: 08 0A
globalAreaID: 64 60 54 25 12 00 00
firstmccmnc: 646054
lastmccmnc: 646054
A.8.22 Moc(hotbilling)
ASN.1 BER Code (Example—moCallRecord(hot).dat)
Figure 1.11 Example—moCallRecord(hot).dat
Decoding (Example—moCallRecord(hot).txt)
record no.: 0
servedIMSI: 460077552000369
servedIMEI: 350654670244270
servedMSISDN: (91)8613907520369

msClassmark: 1F034F
callDuration: 14
networkcallReference: 00 00 58 00 E4 08
mSCAddress: (91)8613900022
systemType: iuUTRAN
orgMSCId: 08 0A
globalAreaID: 64 60 54 25 12 00 00
firstmccmnc: 646054
lastmccmnc: 646054
hotBillingTag: true
A.8.23 SS_PLMN_SPECIFICSS1 record

ASN.1 BER Code (Example—moc(SS_PLMN_SPECIFCSS1).dat)

Figure 1.12 Example—moc(SS_PLMN_SPECIFCSS1).dat
Decoding (Example—moc(SS_PLMN_SPECIFCSS1).txt)
servedIMSI: 460881104002798
servedIMEI: 350989100621290
servedMSISDN: (91)8613907521001
mscOutgoingROUTE: IsupIO
location: LAC-FFFF. CellID-0000
supplServicesUsed: {ssTime: 040315112525. ssCode: SS_PLMN_SPECIFICSS1(F1). }
msClassmark: 571881
callDuration: 84
callReference: 16 00 00 00 4D
systemType: iuUTRAN
mscOutgoingCircuit: C

orgRNCorBSCId: 00 09 00
orgMSCId: 44 0B 00
subscriberCategory: Superior(B)
firstmccmnc: 24F420
lastmccmnc: 24F420
A.8.24 SS_PLMN_SPECIFICSS3 record

ASN.1 BER Code (Example—moc(SS_PLMN_SPECIFCSS3).dat)
Figure 1.13 Example—moc(SS_PLMN_SPECIFCSS3).dat
Decoding (Example—moc(SS_PLMN_SPECIFCSS3).txt)
servedIMSI: 460881104002798
servedIMEI: 350989100621290
servedMSISDN: (91)8613907521001
mscOutgoingROUTE: IsupIO
location: LAC-FFFF. CellID-0000
supplServicesUsed: {ssTime: 040315112651. ssCode: SS_PLMN_SPECIFICSS3(F3). }
msClassmark: 571881

callDuration: 31
callReference: 16 00 00 00 4D
systemType: iuUTRAN
mscOutgoingCircuit: C
orgRNCorBSCId: 00 09 00
orgMSCId: 44 0B 00
subscriberCategory: Superior(B)
firstmccmnc: 24F420
lastmccmnc: 24F420
A.8.25 MO-LCS
ASN.1 BER Code (Example—lcsMOrecord.dat)
Figure 1.14 Example—lcsMOrecord.dat
Decoding (Example—lcsMOrecord.txt)
record no.: 0
recordType: moLCSRecord
lcsClientType: valueAddedServices
lcsClientIdentity: lcsClientExternalID/externalAddress-(91)861340030800
servedIMSI: 460043004300056
servedMSISDN: (91)8613403000056
molr_Type: locationEstimate(0)
lcsQos: {responseTimeCategory: delaytolerant}

lcsPriority: 1
mlc_Number: (91)8613400308
eventTimeStamp: 040719200559
measureDuration: 2
locationEstimate: 02 00 00 00 00 00 FF 80 00 80
positioningData: 00
systemType: iuUTRAN
firstmccmnc: 64F040
orgMSCId: 01 1E 01
hotBillingTag: true
A.8.26 MT-LCS
ASN.1 BER Code (Example—lcsMTrecord.dat)
Figure 1.15 Example—lcsMTrecord.dat
Decoding (Example—lcsMTrecord.txt)
record no.: 0
recordType: mtLCSRecord
lcsClientType: valueAddedServices
servedIMSI: 460043004300056

servedMSISDN: (91)8613403000056
locationType: locationEstimateType-currentLocation
lcsQos: {horizontal_accuracy: 20} {vertical_accuracy: 30} {verticalCoordinateRequest: 0}
{responseTimeCategory: delaytolerant}
lcsPriority: 1
mlc_Number: (91)8613400308
measureDuration: 3
notificationToMSUser: locationNotAllowed
privacyOverride: 0
positioningData: 00
systemType: iuUTRAN
firstmccmnc: 64F040
orgMSCId: 01 1E 01
hotBillingTag: true
A.8.27 NI-LCS
ASN.1 BER Code (Example—lcsNIrecord.dat)
Figure 1.16 Example—lcsNIrecord.dat
Decoding (Example—lcsNIrecord.txt)

record no.: 0
recordType: niLCSRecord
lcsClientType: emergencyServices
servedIMSI: 460043004300056
servedMSISDN: (91)8613403000056
servedIMEI: 004400003779020
lcsPriority: 1
mlc_Number: (91)8613400308
measureDuration: 2
positioningData: 00
systemType: iuUTRAN
firstmccmnc: 64F040
orgMSCId: 01 1E 01
hotBillingTag: true

02-A CDR Farmat

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

02-A CDR Farmat

Încărcat de

Drepturi de autor:

Formate disponibile

HUAWEI iGateway Bill

User Manual Contents

Issue 07 (2007-10-10) Huawei Technologies Proprietary i

A.6.3 AoC Parameters/Change of AoC Parameters....................................................................................A-69

ii Huawei Technologies Proprietary Issue 07 (2007-10-10)

A.6.45 Measure Duration............................................................................................................................A-96

Issue 07 (2007-10-10) Huawei Technologies Proprietary iii

A.6.87 Maximum Number of SMS in the Concatenated SMS.................................................................A-116

iv Huawei Technologies Proprietary Issue 07 (2007-10-10)

Issue 07 (2007-10-10) Huawei Technologies Proprietary v

Figure A-1 Structure of call data record.............................................................................................................A-8

Figure A-2 Figure 1...........................................................................................................................................A-76

Figure A-3 Figure 2.........................................................................................................................................A-103

Figure A-4 Figure 3.........................................................................................................................................A-103

Figure A-5 Figure 4.........................................................................................................................................A-104

Figure A-6 Figure 5.........................................................................................................................................A-114

Figure A-7 Example--moCallRecord.dat........................................................................................................A-178

Figure A-8 Example--mtCallRecord.dat.........................................................................................................A-179

Figure A-9 Example—moCallRecord(VP).dat...............................................................................................A-181

Figure A-10 Example—moCallRecord(BS).dat.............................................................................................A-183

Figure A-11 Example—forwardCallRecord(cfnry).dat..................................................................................A-184

Figure A-12 Example—moCallRecord(EmergencyCallWithoutSIM).dat.....................................................A-186

Figure A-13 Example—moCallRecord(partial1).dat......................................................................................A-187

Figure A-14 Example—moCallRecord(partial2).dat......................................................................................A-189

Figure A-15 Example—moCallRecord(partial3).dat......................................................................................A-190

Figure A-16 Example—moSMSRecord.dat...................................................................................................A-192

Figure A-17 Example—mtSMSRecord.dat....................................................................................................A-193

Figure A-18 Example1—moSMSRecord(partial1).dat..................................................................................A-194

Figure A-19 Example1—moSMSRecord(partial2).dat..................................................................................A-194

Figure A-20 Example1—moSMSRecord(partial3).dat..................................................................................A-194

Figure A-21 Example—hlrRecord.dat............................................................................................................A-197

Figure A-22 Example—ssActionRecord(USSD).dat.....................................................................................A-198

Figure A-23 Example—ssActionRecord(forward registration).dat................................................................A-199

Figure A-24 Example—ssActionRecord(BAOC activation).dat....................................................................A-200

Figure A-25 Example—ssActionRecord(BAOC deactivation).dat................................................................A-201

Figure A-26 Example—moCallRecord(Handover).dat..................................................................................A-202

Issue 07 (2007-10-10) Huawei Technologies Proprietary vii

Figure A-27 Example—commonEquipRecord.dat.........................................................................................A-204

Figure A-28 Example—incGatewayRecord.dat.............................................................................................A-205

Figure A-29 Example—outGatewayRecord.dat.............................................................................................A-206

Figure A-30 Example—transitCallRecord.dat................................................................................................A-207

Figure A-31 Example—roamingRecord.dat...................................................................................................A-208

Figure A-32 Example—moCallRecord(camel).dat........................................................................................A-209

Figure A-33 Example—mtCallRecord(camel).dat.........................................................................................A-210

Figure A-34 Example—termCAMELRecord.dat...........................................................................................A-212

Figure A-35 Example—moc(withFCI).dat.....................................................................................................A-213

Figure A-36 Example—moCallRecord(hot).dat.............................................................................................A-215

Figure A-37 Example—moc(SS_PLMN_SPECIFCSS1).dat.........................................................................A-216

Figure A-38 Example—moc(SS_PLMN_SPECIFCSS3).dat.........................................................................A-217

Figure A-39 Example—lcsMOrecord.dat.......................................................................................................A-219

Figure A-40 Example—lcsMTrecord.dat.......................................................................................................A-220

Figure A-41 Example—lcsNIrecord.dat.........................................................................................................A-221

viii Huawei Technologies Proprietary Issue 07 (2007-10-10)

Table A-1 MOC record......................................................................................................................................A-10

Table A-2 MOC emergency record...................................................................................................................A-16

Table A-4 MTC record......................................................................................................................................A-26

Table A-5 Roaming record................................................................................................................................A-32

Table A-6 Incoming gateway record.................................................................................................................A-35

Table A-7 Outgoing gateway record.................................................................................................................A-38

Table A-8 Transit record....................................................................................................................................A-41

Table A-9 SMS-MO record...............................................................................................................................A-44

Table A-10 SMS-MT record.............................................................................................................................A-46

Table A-11 LCS-MT record..............................................................................................................................A-49

Table A-12 LCS-MO record..............................................................................................................................A-51