CDR Format PDF

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
Contents
HUAWEI iGateway Bill 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
Issue 07 (2007-10-10)
Contents
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)
iii
Contents
HUAWEI iGateway Bill User Manual 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
Issue 07 (2007-10-10)
Contents
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)
Figures
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 ExamplemoCallRecord(VP).dat..............................................................................................A-181 Figure A-10 ExamplemoCallRecord(BS).dat............................................................................................A-183 Figure A-11 ExampleforwardCallRecord(cfnry).dat .................................................................................A-184 Figure A-12 ExamplemoCallRecord(EmergencyCallWithoutSIM).dat ....................................................A-186 Figure A-13 ExamplemoCallRecord(partial1).dat.....................................................................................A-187 Figure A-14 ExamplemoCallRecord(partial2).dat.....................................................................................A-189 Figure A-15 ExamplemoCallRecord(partial3).dat.....................................................................................A-190 Figure A-16 ExamplemoSMSRecord.dat ..................................................................................................A-192 Figure A-17 ExamplemtSMSRecord.dat...................................................................................................A-193 Figure A-18 Example1moSMSRecord(partial1).dat .................................................................................A-194 Figure A-19 Example1moSMSRecord(partial2).dat .................................................................................A-194 Figure A-20 Example1moSMSRecord(partial3).dat .................................................................................A-194 Figure A-21 ExamplehlrRecord.dat...........................................................................................................A-197 Figure A-22 ExamplessActionRecord(USSD).dat ....................................................................................A-198 Figure A-23 ExamplessActionRecord(forward registration).dat...............................................................A-199 Figure A-24 ExamplessActionRecord(BAOC activation).dat...................................................................A-200 Figure A-25 ExamplessActionRecord(BAOC deactivation).dat ...............................................................A-201 Figure A-26 ExamplemoCallRecord(Handover).dat .................................................................................A-202
vi
Issue 07 (2007-10-10)
Figures
Figure A-27 ExamplecommonEquipRecord.dat........................................................................................A-204 Figure A-28 ExampleincGatewayRecord.dat ............................................................................................A-205 Figure A-29 ExampleoutGatewayRecord.dat............................................................................................A-206 Figure A-30 ExampletransitCallRecord.dat...............................................................................................A-207 Figure A-31 ExampleroamingRecord.dat..................................................................................................A-208 Figure A-32 ExamplemoCallRecord(camel).dat .......................................................................................A-209 Figure A-33 ExamplemtCallRecord(camel).dat ........................................................................................A-210 Figure A-34 ExampletermCAMELRecord.dat..........................................................................................A-212 Figure A-35 Examplemoc(withFCI).dat....................................................................................................A-213 Figure A-36 ExamplemoCallRecord(hot).dat............................................................................................A-215 Figure A-37 Examplemoc(SS_PLMN_SPECIFCSS1).dat........................................................................A-216 Figure A-38 Examplemoc(SS_PLMN_SPECIFCSS3).dat........................................................................A-217 Figure A-39 ExamplelcsMOrecord.dat......................................................................................................A-219 Figure A-40 ExamplelcsMTrecord.dat ......................................................................................................A-220 Figure A-41 ExamplelcsNIrecord.dat........................................................................................................A-221
Issue 07 (2007-10-10)
vii
Tables
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
viii
Issue 07 (2007-10-10)
A CDR Format
A
About This Chapter
The following table lists the contents of this chapter. Title A.1 Acronyms and Abbreviations A.2 ASN.1 (Basic Encoding Rules) Description A.3 Charging Data Record Transfer A.4 Record types A.5 Record contents A.6 Description of Record Fields A.7 Charging Data Record Structure:ASN.1 description A.8 Examples of CDR Description
CDR Format
Lists the acronyms and abbreviations related to CDR format. Describes the basis encoding rules of the ASN.1 CDR. Describes how to transfer CDRs from the iGWB to the BC. Describes the types of call and event records contained in CDRs. Describes the details of a CDR. Describes the information on each field in a CDR. Describes the structure of a ASN.1 CDR. Describes the CDR format with examples.
Issue 07 (2007-10-10)
A-1
A CDR Format
A.1 Acronyms and Abbreviations

A AoC Advice of Charge
B BCSM BSS Basic Call State Model Base Station System
C CAI CAMEL CD CDR CUG Charge Advice Information Customised Applications for Mobile network Enhanced Logic Call Divert Call Detail Record Closed User Group
D DP Detection Point
E ECT EDP EIR EMS-Digits EMS-Key eMLPP ETSI Explicit Call Transfer
Event Detection Point Equipment Identity Register North American Emergency Service Routing Digits North American Emergency Service Routing Key Enhanced Multi-Level Precedence and Pre-emption European Telecommunications Standard Institute
F FCI FTAM FTP Furnish Charging Information File Transfer Access Management File Transfer Protocol
A-2
Issue 07 (2007-10-10)
A CDR Format
G GMSC GERAN gsmSCF gsmSSF Gateway MSC GSM/EDGE Radio Access Network GSM Service Control Function GSM Service Switching Function
H HLR HPLMN HSCSD Home Location Register Home PLMN High Speed Circuit Switched Data
I IMEI IMSI ISDN International Mobile Equipment Identity International Mobile Subscriber Identity Integrated Services Digital Network
L LAC Location Area Code
M MLC MOC MO-LR MS MSC MSRN MTC MT-LR Mobile Location Centre Mobile Originated Call (attempt) Mobile Originated Location Request Mobile Station Mobile Switching Centre Mobile Station Roaming Number Mobile Terminated Call (attempt) Mobile Terminated Location Request
N NAR NE NEF North America Region Network Element Network Element Function
Issue 07 (2007-10-10)
A-3
A CDR Format
NM NI-LR
Network Management Network Induced Location Request
O O_CSI OMC OS Originating CAMEL Subscription Information Operations and Maintenance Centre Operations System
P PLMN Public Land Mobile Network
S SAC SCF SCI SMS SS7 Service Area Code Service Control Function Subscriber Controlled Input or Send Charging Information Short Message Service Signalling System No. 7
T T_CSI TDP TMN Terminating CAMEL Subscription Information Trigger Detection Point Telecommunications Management Network
U USIM USSD UTRAN User Service Identity Module Unstructured Supplementary Service Data UMTS Terrestrial Radio Access Network
V VAS VLR VMSC VPLMN Value Added Service Visitor Location Register Visited MSC Visited PLMN
A-4
Issue 07 (2007-10-10)
A CDR Format
VT-CSI
Visited Terminating CAMEL Subscription Information
Numeric 2G 3G MSC MSC Refer to an MSC Release 98 or prior 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: +----------------------------+ Universal Application Context-specific Private 1 Bit: 8 0 0 1 7 0 1 0 1 +----------------------------
+----------------------------+
Issue 07 (2007-10-10)
A-5
A CDR Format
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 subsequent . . subsequent +---+--------------------------- first 2 1 NUMBER of TAG (msb) . . 0 NUMBER of TAG (lsb) +-------------------------------
+------------------------------- last +-------------------------------+ 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 thats why not scope of this explanation.
Short Length Encoding for Length from 0 to 127 (Inclusive)

8 1 0 7 L 6 L 5 L 4 L 3 L 2 L 1 L +------------------------------- +-------------------------------+ LLLLLLL represents the length of the content
A-6
Issue 07 (2007-10-10)
A CDR Format
Long Length Encoding for Length > 127

8 7 6 5 4 3 2 1 +---+--------------------------- 1 1 0 < n < 127 +-------------------------------+ +------------------------------- 2 L L L L ... +------------------------------- n+1 L L L L L L L L +-------------------------------+ LLLLLLLL represents the length of the content L L L L +-------------------------------+
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 octet 1 octet 2 . . octet n +------------------------------- most significant byte . . least significant byte +------------------------------- +-------------------------------
+------------------------------- +-------------------------------+ 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.
Issue 07 (2007-10-10)
A-7
A CDR Format
Figure A-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;
A-8
Issue 07 (2007-10-10)

A CDR Format
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.
Issue 07 (2007-10-10)
A-9
A CDR Format
Table A-1 MOC record Field Record Type 2G M 3G M TAG 0x80 01 00 TYPE ENUMERA TED (1) Served IMSI Served IMEI Served MSISDN Calling Number Called Number Translated Number Connected Number Roaming Number Recording Entity Incoming ROUTE Outgoing ROUTE Location M C M M M O M C M M M O 0x81 0x82 0x83 0x84 0x85 0x86 TBCD(3..8) TBCD(8) ADRESS(2.. 9) ADRESS (2..17) ADRESS (2..17) ADRESS (2..17) ADRESS (2..17) ADRESS (2..17) ADRESS (2..9) IA5(1..10) IA5(1..10) OCTET(8) IMSI of the calling party. IMEI of the calling ME, if available. The primary MSISDN of the calling party. The address of the calling party. The address of the called party e.g. the number dialled by the calling sub. The called number after digit translation within the MSC (if applicable) The number of the connected party if different to the Called Number The Mobile Station Roaming Number employed to route this connection, if applicable (Roaming Number of B). The E.164 number of the visited MSC producing the record. The MSC route on which the call originated , usually from the BSS The route on which the call left the MSC The identity of the cell or the SAC in which the call originated including the location area code. A list of changes in Location Area Code / Cell Identifier each time-stamped. Bearer or teleservice employed. Only provided for those basic services which may be employed in both transparent and non-transparent mode. Description Mobile originated.
O O
O O
0x87 0x88
M O O M
M O O M
0x89 0xAA 0xAB 0xAC
Change of Location Basic service Transparenc y Indicator
0xAD
SEQUENCE OF ( 23 * n ) OCTET(3) ENUMERA TED (1)
M C
M C
0xAE 0x8F
A-10
Issue 07 (2007-10-10)
A CDR Format
Field Change Of Service Supp. Services
2G C
3G C
TAG 0xB0
TYPE SEQUENCE OF ( (18..27) * n) SEQUENCE OF (16 * n)
Description A list of changes of basic service during a connection each time-stamped. Supplementary services invoked as a result of this connection.
0xB1
AOC Parameters Change of AOC Para
O O
O O
0xB2 0xB3
OCTET(4..2 8) SEQUENCE OF ( 43 * n)
The charge advice parameters sent to the MS on call set-up New AOC parameters sent to the MS e.g. as a result of a tariff switch over, including the time at which the new set was applied. The mobile station classmark employed on call set-up. A list of changes to the classmark during the connection each time-stamped Setup or IAM timestamp from calling side Seizure of incoming traffic channel Alerting or ACM timestamp from called side Answer (for successful calls) Release of traffic channel
MS Classmark Change of Classmark Event time stamps:
M O
M O
0x94 0xB5
OCTET(2..3) OCTET (16 )
M O O C O
M O O C O
0x9F 81 49 0x96 0x9F 81 4A 0x97 0x98
OCTET(9) OCTET(9) OCTET(9) OCTET(9) OCTET(9)
Call duration Radio Chan. Requested Radio Chan. Used
0x99
INTEGER(1. .2) ENUMERA TED (1)
The chargeable duration of the connection for successful calls, the holding time for call attempts. The type of radio traffic channel (full / half etc.) requested by the MS.
0x9B
0x9C
ENUMERA TED (1)
The type of radio channel actually used (full or half rate).
Change of Radio Chan. Cause for termination Diagnostics
0xBD
OCTET (14..17 ) INTEGER (1) INTEGER(4)
A list of changes each time stamped
M O
M O
0x9E 0xBF 1F
The reason for the release of the connection. A more detailed reason for the release of the connection.
Issue 07 (2007-10-10)
A-11
A CDR Format
Field Call reference Sequence no. Additional Chg. Info Record extensions gsmSCF address Service key Network call reference MSC Address CAMEL initiated CF indicator Default call handling
2G M C O O C C C
3G M C O O C C C
TAG 0x9F 20 0x9F 21 0xBF 22 0xBF 23 0x9F 24 0x9F 25 0x9F 26
TYPE OCTET(1..8) INTEGER(1) SEQUENCE (3) SET OF (11 * n) ADRESS(2.. 9) INTEGER(1. .4) OCTET(1..8)
Description A local identifier distinguishing between transactions on the same MS Partial record sequence number, only present in case of partial records. Charge/no charge indicator and additional charging parameters A set of network/ manufacturer specific extensions to the record. Identifies the CAMEL server serving the subscriber. The CAMEL service logic to be applied. An identifier to correlate transactions on the same call taking place in different network nodes shall be present. This field contains the E.164 number assigned to the MSC that generated the network call reference. Indicates that the CAMEL server initiated call forwarding in CFW CDR. Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for non-transparent HSCSD connections. Speech version used for that call
0x9F 27 0x9F 28 0x9F 29
ADRESS(2.. 9) BOOLEAN( 1) ENUMERA TED (1)
Fixed Network User Rate
0x9F 2D
ENUMERA TED (1)
Air Interface User Rate Requested Speech Version Used Speech Version Supported
0x9F 2E
ENUMERA TED (1)
0x9F 32 0x9F 31
OCTET(1)
OCTET(1)
Speech version supported by the MS with highest priority indicated by MS
A-12
Issue 07 (2007-10-10)
A CDR Format
Field Number of DP encountered Level of CAMEL service Free format Data
2G O
3G O
TAG 0x9F 33 0x9F 34 0x9F 35
TYPE INTEGER(1)
Description Numbers that counts how often armed detection points (TDP and EDP) were encountered. Indicator for the complexity of the CAMEL feature used. This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Indicates whether or not a 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. Identifies the CAMEL server serving the subscriber for 2nd service such as dialled service. The CAMEL service logic to be applied for 2nd service such as dialled service. This field contains data sent 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. Indicator if free format data for 2nd service from this CDR is to be appended to free format data in previous partial CDR. 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.
BIT STRING(2) OCTET(1..1 60)
CAMEL call leg information
0xBF 36
SEQUENCE OF ((104..124) * n)
Free format data append indicator Default call handling 2
0x9F 37 0x9F 38
BOOLEAN (1) ENUMERA TED (1)
GsmSCF address 2 Service key 2 Free format Data 2
0x9F 39 0x9F 3A 0x9F 3B
ADRESS (2..9) INTEGER (1..4) OCTET(1..1 60)
Free format data append indicator 2 System Type
0x9F 3C
BOOLEAN (1)
0x9F 3D
ENUMERA TED (1)
Issue 07 (2007-10-10)
A-13
A CDR Format
Field Rate Indication
2G O
3G O
TAG 0x9F 3E
TYPE OCTET(1)
Description Present if rate adaption parameters for the basic service were signalled between the MS/UE and the network, see TS 24.008. Indicates the event (time limit etc.) that caused the generation of a partial record. Describes the bit-rate the UMTS 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 Bit Rate can be used 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). Indicates the type of Modem used.
Partial Record Type Guaranteed bit rate
0x9F 45
ENUMERA TED (1)
0x9F 46
ENUMERA TED (1)
Maximum bit rate
0x9F 47
ENUMERA TED (1)
Modem Type
0x9F 81 0B
ENUMERA TED (1)
Classmark3 Charged Party
O O
O O
0x9F 81 0C 0x9F 81 0D 0x9F 81 0E 0x9F 81 11 0x9F 81 12 0x9F 81 26
OCTET(2) ENUMERA TED (1) ADRESS (2..17) OCTET(1..3)
May be present when access in BSC. 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. The address of original called party in CFW CDR. Indicates the calling party logical area for distance charge Indicates the called party logical area for distance charge This field indicates the cic, only present in case of outgoing call and TDM bear type.
Original Called Number Calling Charge Area Code Called Charge Area Code MSC Outgoing Circuit
OCTET(1..3)
INTEGER (1..2)
A-14
Issue 07 (2007-10-10)
A CDR Format
Field RNC or BSC Id MSC Id or SPC Call Emlpp Priority Caller Default Emlpp Priority Ea Subscriber Info Selected CIC optimalRou tingFlag optimalRou tingLateFor wardFlag optimalRou tingEarlyFo rwardFlag Ported flag
2G M M O
3G M M O
TAG 0x9F 81 27 0x9F 81 28 0x9F 81 2A 0x9F 81 2B
TYPE OCTET(3) OCTET(3) OCTET(1)
Description This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates the priority of call. See 24.008 Indicates the calling subscribers priority. See 29.002
OCTET(1)
0x9F 81 2E 0x9F 81 2F 0x9F 81 31 0x9F 81 32 0x9F 81 33 0x9F 81 34
OCTET(3)
Indicates the calling subscribers information of Equal Access Indicates the selected code of Carrier identification Reserved for the future Reserved for the future
C -
C -
OCTET(3) NULL NULL
NULL
Reserved for the future
ENUMERA TED (1)
Indicates if called party be ported.
Called IMSI Global Area ID Change Of Global Area ID Subscriber Category First MCC MNC Intermediat e MCC MNC
C O O
C O O
0x9F 81 35 0x9F 81 3C 0xBF 81 3D 0x9F 81 3E 0x9F 81 40 0x9F 81 41
TBCD(3..8) OCTET(7) SEQUENCE OF (22 * n) OCTET(1) OCTET(3) OCTET(3)
Indicates IMSI of the called party if called party be ported. Indicates CGI of GSM or SAI of WCDMA A list of changes in CGI / SAI each time-stamped.
M M O
M M O
Indicates the category of subscriber. Indicates the MCC and MNC of the network where call is initiated. Indicates the MCC and MNC of the network where call is served only present after handover.
Issue 07 (2007-10-10)
A-15
A CDR Format
Field Last MCC MNC CUG Outgoing Access Indicator CUG Interlock Code CUG Outgoing Access Used CUG Index Interaction With IP Hot billing tag
2G C
3G C
TAG 0x9F 81 42 0x9F 81 43
TYPE OCTET(3)
Description Indicates the MCC and MNC of the network where call is served only present after handover. Indicates the subscriber with a Outgoing Access.
ENUMERA TED (1)
0x9F 81 44 0x9F 81 45
OCTET(4)
Network code + CUG interlock
ENUMERA TED (1)
Indicates caller and called whether or not is in the same CUG group.
O C
O C
0x9F 81 46 0x9F 81 47 0x9F 81 48
OCTET(2) NULL (0)
The CUG index has significance only between the subscriber and network. In the case of interaction between SSP and IP, GsmSCF play announcement to SSP and start charging. Indicates the Subscriber is one with Hot Billing service.
INTEGER(1)
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 A-2 MOC emergency record Field Record Type 2G M 3G M TAG 0x80 01 00 0x81 TYPE ENUMERATED (1) TBCD(3..8) IMSI of the calling party in case of an emergency call with a SIM card. IMEI of the calling mobile equipment if available. The primary MSISDN of the calling party. The address of the calling party. Description Mobile originated.
Served IMSI
Served IMEI Served MSISDN Calling Number
C O M
C O M
0x82 0x83 0x84
TBCD(8) ADRESS(2..9) ADRESS (2..17)
A-16
Issue 07 (2007-10-10)
A CDR Format
Field Called Number Recording Entity Incoming ROUTE Outgoing ROUTE Location
2G M
3G M
TAG 0x85
TYPE ADRESS (2..17)
Description The address of the called party e.g. the number dialled by the calling sub. The E.164 number of the visited MSC producing the record. The MSC route on which the call originated, usually from the BSS The route on which the call left the MSC The identity of the cell or the SAC in which the call originated including the location area code. A list of changes in Location Area Code / Cell Identifier each time-stamped. Teleservice 'emergency call'. The charge advice parameters sent to the MS on call set-up New AOC parameters sent to the MS e.g. as a result of a tariff switch over, including the time at which the new set was applied. The mobile station classmark employed on call set-up. A list of changes to the classmark during the connection each time-stamped Setup or IAM timestamp from calling side Seizure of incoming traffic channel Alerting or ACM timestamp from called side Answer (for successful calls) Release of traffic channel
M O
M O
0x89 0xAA
ADRESS(2..9) IA5(1..10)
O M
O M
0xAB 0xAC
IA5(1..10) OCTET(8)
Change of Location Basic service AOC Parameters Change of AOC Parms
0xAD
SEQUENCE OF ( 23 * n )
M O O
M O O
0xAE 0xB2 0xB3
OCTET(3) OCTET(4..28) SEQUENCE OF ( 43 * n)
MS Classmark Change of classmark Event time stamps:
M O
M O
0x94 0xB5
M O O C O
M O O C O
0x9F 81 49 0x96 0x9F 814A 0x97 0x98
Call duration
0x99
INTEGER(1..2)
The chargeable duration of the connection for successful calls, the holding time for call attempts.
Issue 07 (2007-10-10)
A-17
A CDR Format
Field Radio Chan. Requested Radio Chan. Used Change of Rad. Chan. Guaranteed bit rate
2G O
3G -
TAG 0x9B
TYPE ENUMERATED (1)
Description The type of radio traffic channel (full / half etc.) requested by the MS. The type of radio channel used (full or half rate). A list of changes each time stamped Describes the bit-rate the UMTS 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 Bit Rate can be used 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 version used for that call
0x9C
ENUMERATED (1)
O -
0xBD 0x9F 46
OCTET (14..17 ) ENUMERATED (1)
Maximum bit rate
0x9F 47
ENUMERATED (1)
Speech Version Used Speech Version Supported Cause for termination Diagnostics Sequence no.
0x9F 32 0x9F 31 0x9E 0xBF 1F 0x9F 21 0x9F 20
OCTET(1)
OCTET(1)
Speech version supported by the MS with highest priority indicated by MS The reason for the release of the connection. A more detailed reason for the release of the connection. Partial record sequence number, only present in case of partial records. A local identifier distinguishing between transactions on the same MS
M O C
M O C
INTEGER(1) INTEGER(4) INTEGER(1)
Call reference
OCTET(1..8)
A-18
Issue 07 (2007-10-10)
A CDR Format
Field Record extensions System Type
2G O M
3G O M
TAG 0xBF 23 0x9F 3D
TYPE SET OF n) (11 *
Description A set of network/ manufacturer specific extensions to the record. 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. This field indicates the cic, only present in case of outgoing call and TDM bear type. This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates the category of subscriber. Indicates the MCC and MNC of the network where call is initiated. Indicates the MCC and MNC of the network where call is served only present after handover. Indicates the MCC and MNC of the network where call is served, only present after handover. Indicates the event (time limit etc.) that caused the generation of a partial record.
ENUMERATED (1)
MSC Outgoing Circuit RNC or BSC Id MSC Id or SPC Subscriber Category First MCC MNC Intermediate MCC MNC Last MCC MNC Partial Record Type
0x9F 81 26 0x9F 81 27 0x9F 81 28 0x9F 81 3E 0x9F 81 40 0x9F 81 41 0x9F 81 42 0x9F 45
INTEGER(1..2)
M M O M
M M O M
OCTET(3) OCTET(3) OCTET(1) OCTET(3)
OCTET(3)
OCTET(3)
ENUMERATED (1)
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 A-3 MOC, call forwarding record Field Record Type 2G M 3G M TAG 0x80 01 64 TYPE ENUMERATED (1) Description Mobile originated.
Issue 07 (2007-10-10)
A-19
A CDR Format
Field Served IMSI Served IMEI Served MSISDN Calling Number Called Number Translated Number Connected Number Roaming Number
2G M C M M M O
3G M C M M M O
TAG 0x81 0x82 0x83 0x84 0x85 0x86
TYPE TBCD(3..8) TBCD(8) ADRESS (2..9) ADRESS (2..17) ADRESS (2..17) ADRESS (2..17)
Description IMSI of the calling party. IMEI of the calling ME, if available. The MSISDN of the forwarding party. The address of the calling party. The address of the "forwarded-to" party. The called number after digit translation within the MSC (if applicable) The number of the connected party if different to the Called Number The Mobile Station Roaming Number employed to route this connection, if applicable (Roaming Number of C). The E.164 number of the forwarding MSC The MSC route on which the call originated at the forwarding MSC. The route on which the call left the forwarding MSC The identity of the cell or the SAC in which the call forwarding including the location area code.(e.g. cfnry) A list of changes in Location Area Code / Cell Identifier each time-stamped. Bearer or tele-service employed, not always available e.g. in case of call forwarding unconditional. Only provided for those basic services which may be employed in both transparent and non-transparent mode.
0x87
ADRESS (2..17)
0x88
ADRESS (2..17)
Recording Entity Incoming ROUTE Outgoing ROUTE Location
M O
M O
0x89 0xAA
ADRESS (2..9) IA5(1..10)
O O
O O
0xAB 0xAC
IA5(1..10) OCTET(8)
Change of Location Basic service
0xAD
0xAE
OCTET(3)
Transparenc y Indicator
0x8F
ENUMERATED (1)
A-20
Issue 07 (2007-10-10)
A CDR Format
Field Change Of Service Supp. Services AOC Parameters Change of AOC Para
2G O
3G O
TAG 0xB0
TYPE SEQUENCE OF ( (18..27) * n)
Description A list of changes of basic service during a connection each time-stamped. Supplementary services invoked as a result of this connection. The charge advice parameters sent to the MS on call set-up New AOC parameters sent to the MS e.g. as a result of a tariff switch over, including the time at which the new set was applied. The mobile station classmark employed on call set-up. A list of changes to the classmark during the connection each time-stamped Setup or IAM timestamp from calling side Seizure of incoming traffic channel Alerting or ACM timestamp from called side Answer (for successful calls) Release of traffic channel
0xB1
SEQUENCE OF (16 * n)
O O
O O
0xB2 0xB3
OCTET(4..28) SEQUENCE OF ( 43 * n)
O O
O O
0x94 0xB5
M OO C O
M OO C O
0x9F 81 49 0x96 0x9F 81 4A 0x97 0x98
Call duration
0x99
INTEGER(1..2)
The chargeable duration of the connection for successful calls, the holding time of call attempts. The type of radio traffic channel (full / half etc.) requested by the MS. The type of radio channel actually used (full or half rate). A list of changes each time stamped The reason for the release of the connection. A more detailed reason for the release of the connection.
Radio Chan. Requested Radio Chan. Used Change of Radio Chan. Cause for termination Diagnostics
0x9B
ENUMERATED (1)
0x9C
ENUMERATED (1)
O M O M O
0xBD 0x9E 0xBF 1F
OCTET(14..17) INTEGER(1) INTEGER(4)
Issue 07 (2007-10-10)
A-21
A CDR Format
Field Call reference Sequence no. Additional Chg. Info Record extensions gsmSCF address Service key Network call reference MSC Address
2G M
3G M
TAG 0x9F 20 0x9F 21 0xBF 22 0xBF 23 0x9F 24 0x9F 25 0x9F 26
TYPE OCTET(1..8)
Description A local identifier distinguishing between transactions on the same MS Partial record sequence number, only present in case of partial records. Charge/no charge indicator and additional charging parameters A set of network/ manufacturer specific extensions to the record. Identifies the CAMEL server serving the subscriber. The CAMEL service logic to be applied. An identifier to correlate transactions on the same call taking place in different network nodes shall be present. This field contains the E.164 number assigned to the MSC that generated the network call reference. Indicates that the CAMEL server initiated call forwarding. Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for non-transparent HSCSD connections. Speech version used for that call
INTEGER(1)
O O C C C
O O C C C
SEQUENCE(3) SET OF (11*n)
ADRESS(2..9) INTEGER(1..4) OCTET(1..8)
0x9F 27
ADRESS(2..9)
CAMEL initiated CF indicator Default call handling
0x9F 28 0x9F 29
BOOLEAN(1)
ENUMERATED (1)
0x9F 2D
ENUMERATED (1)
Air Interface User Rate Requested
0x9F 2E
ENUMERATED (1)
Speech Version Used
0x9F 32
OCTET(1)
A-22
Issue 07 (2007-10-10)
A CDR Format
Field Speech Version Supported Number of DP encountered Level of CAMEL service Free format Data
2G O
3G
TAG 0x9F 31
TYPE OCTET(1)
Description Speech version supported by the MS with highest priority indicated by MS Numbers that counts how often armed detection points (TDP and EDP) were encountered. Indicator of the complexity of the CAMEL feature used. This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. 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 forwarding call setup. Present if rate adaption 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. Indicates the event (time limit etc.) that caused the generation of a partial record. Describes the bit-rate the UMTS 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.
0x9F 33 0x9F 34 0x9F 35
INTEGER(1)
BIT STRING(2)
OCTET(1..160)
CAMEL call leg information Free format data append indicator System Type
0xBF 36
SEQUENCE OF ((104..124) * n)
0x9F 37
BOOLEAN(1)
0x9F 3D
ENUMERATED (1)
Rate Indication
0x9F 3E
OCTET(1)
0x9F 45 0x9F 46
ENUMERATED (1) ENUMERATED (1)
Issue 07 (2007-10-10)
A-23
A CDR Format
Field Maximum bit rate
2G -
3G O
TAG 0x9F 47
TYPE ENUMERATED (1)
Description Maximum Bit Rate can be used 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). May be present when access in BSC. 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. The address of original called party. Indicates the forwarding party logical area for distance charge Indicates the called party logical area for distance charge This field indicates the cic, only present in case of forwarding outgoing call and TDM bear type. This field indicates the SPC of RNC or BSC of forwarding subscriber. This field indicates the SPC of MSC of forwarding call at conditional forwarding call. Indicates the priority of forwarding call. See 24.008 Indicates the forwarding subscribers priority. See 29.002
Classmark3 Charged Party
O O
O O
0x9F 81 0C 0x9F 81 0D
OCTET(2) ENUMERATED (1)
Original Called Number Calling Charge Area Code Called Charge Area Code MSC Outgoing Circuit RNC or BSC Id MSC Id or SPC Call Emlpp Priority Caller Default Emlpp Priority
0x9F 81 0E 0x9F 81 11 0x9F 81 12 0x9F 81 26
ADRESS (2..17)
OCTET(1..3)
OCTET(1..3)
INTEGER()1..2
0x9F 81 27 0x9F 81 28 0x9F 81 2A 0x9F 81 2B
OCTET(3)
OCTET(3)
O O
O O
OCTET(1) OCTET(1)
A-24
Issue 07 (2007-10-10)
A CDR Format
Field Ea Subscriber Info Selected CIC Ported flag
2G C
3G C
TAG 0x9F 81 2E 0x9F 81 2F 0x9F 81 34 0x9F 81 3C 0xBF 81 3D 0x9F 81 3E 0x9F 81 40 0x9F 81 41 0x9F 81 42
TYPE OCTET(3)
Description Indicates the forwarding subscribers information of Equal Access Indicates the selected code of Carrier identification Indicates if forwarding party be ported. Indicates CGI of GSM or SAI of WCDMA A list of changes in CGI / SAI each time-stamped. Indicates the category of forwarding subscriber. Indicates the MCC and MNC of the network where forwarding call is initiated. Indicates the MCC and MNC of the network where call is served only present after handover. Indicates the MCC and MNC of the network where call is served only present after handover. Indicates the subscriber with a Outgoing Access.
C O
C O
OCTET(3) ENUMERATED (1) OCTET(7) SEQUENCE OF (22 * n) OCTET(1) OCTET(3)
Global Area ID Change Of Global Area ID Subscriber Category First MCC MNC Intermediate MCC MNC Last MCC MNC
O O
O O
C C
C C
OCTET(3)
OCTET(3)
CUG Outgoing Access Indicator CUG Interlock Code CUG Outgoing Access Used CUG Index
0x9F 81 43
ENUMERATED (1)
0x9F 81 44 0x9F 81 45 0x9F 81 46 0x9F 81 48
OCTET(4)
ENUMERATED (1) OCTET(2)
Indicates caller and called whether or not is in the same CUG group. The CUG index has significance only between the subscriber and network. Indicates the Subscriber is one with Hot Billing service.
Hot billing tag
INTEGER(1)
Issue 07 (2007-10-10)
A-25
A CDR Format
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 A-4 MTC record Field Record Type 2G M 3G M TAG 0x80 01 01 0x81 0x82 0x83 0x84 0x85 TYPE ENUMERATED (1) TBCD(3..8) TBCD(8) ADRESS(2..9) ADRESS(2..17) ADRESS(2..17) IMSI of the called party. IMEI of the called ME. The MSISDN of the called party. The number of the calling party if available. Only relevant in case of call forwarding where the "forwarded-to" number is recorded. The E.164 number of the visited (terminating) MSC The MSC route on which the call originated. The route on which the call left the MSC, usually to the BSS The identity of the cell or the SAC occupied by the called party when the call was set up including the location area code. A list of changes in Location Area Code / Cell Identifier each time-stamped. Bearer or teleservice employed Only provided for those basic services which may be employed in both transparent and non-transparent mode. A list of changes of basic service during a connection each time-stamped. Description Mobile Terminated.
Served IMSI Served IMEI Served MSISDN Calling Number Connected Number
M C O C O
M C O C O
Recording Entity Incoming ROUTE Outgoing ROUTE Location
M O O C
M O O C
0x86 0xA7 0xA8 0xA9
ADRESS(2..9) IA5(1..10) IA5(1..10) OCTET(8)
Change of Location Basic Service Transparenc y Indicator
0xAA
M C
M C
0xAB 0x8C
Change of Service
0x8D
SEQUENCE OF ( (18..27) * n)
A-26
Issue 07 (2007-10-10)
A CDR Format
Field Supp. Services AOC Parameters Change of AOC Parms.
2G C
3G C
TAG 0xAE
TYPE SEQUENCE OF (16 * n)
Description Supplementary services invoked as a result of this connection. The charge advice parameters sent to the MS on call set-up New AOC parameters sent to the MS e.g. as a result of a tariff switch-over, including the time at which the new set was applied. The mobile station class mark A list of changes to the classmark during the connection each time-stamped Setup or IAM timestamp from calling side Seizure of traffic channel Alerting or ACM timestamp from called side Answer time for successful calls Release of traffic channel
O O
O O
0xAF 0xB0
OCTET(4..28) SEQUENCE OF ( 43 * n)
M O
M O
0x91 0xB2
M OO C O
M OO C O
0x9F 81 4B 0x93 0x9F 81 4C 0x94 0x95
Call duration
0x96
INTEGER(1..2)
The chargeable duration of the connection if successful, the holding time of the call if unsuccessful. The type of radio traffic channel (full / half etc.) requested by the MS. The type of radio channel used (full or half rate). A list of changes each time stamped The reason for the release of the call. A more detailed reason for the release of the connection. A local identifier distinguishing between transactions at the same MS
Radio Chan. Requested Radio Chan. Used Change of Rad. Chan Cause for term. Diagnostics Call reference
0x98
ENUMERATED (1)
0x99
ENUMERATED (1)
O M O M M O M
0xBA 0x9B 0xBC 0x9D
OCTET (14..17 ) INTEGER(1) INTEGER(4) OCTET(1..8)
Issue 07 (2007-10-10)
A-27
A CDR Format
Field Sequence no. Additional Chg. Info Record extensions Network call reference
2G C
3G C
TAG 0x9E
TYPE INTEGER(1)
Description Partial record sequence number, only present in case of partial records. Charge/no charge indicator and additional charging parameters A set of network/ manufacturer specific extensions to the record. An identifier to correlate transactions on the same call taking place in different network nodes shall be present. This field contains the E.164 number assigned to the MSC that generated the network call reference. Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for non-transparent HSCSD connections. Speech version supported by the MS with highest priority indicated by MS Speech version used for that call
O O C
O O C
0xBF 1F 0xBF 20 0x9F 21
SEQUENCE(3) SET OF (11 * n) OCTET(1..8)
MSC Address
0x9F 22
ADRESS(2..9)
0x9F 26
ENUMERATED (1)
Air Interface User Rate Requested
0x9F 27
ENUMERATED (1)
Speech Version Supported Speech Version Used gsmSCF address Service key System Type
0x9F 2A 0x9F 2B C C C 0x9F 2C 0x9F 2D 0x9F 2E
OCTET(1)
OCTET(1)
C C C
ADRESS(2..9) INTEGER(1..4) ENUMERATED (1)
Identifies the CAMEL server serving the subscriber. The CAMEL service logic to be applied. 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.
A-28
Issue 07 (2007-10-10)
A CDR Format
Field Rate Indication
2G O
3G O
TAG 0x9F 2F
TYPE OCTET(1)
Description Present if rate adaption parameters for the basic service were signalled between the MS/UE and the network, see TS 24.008. Indicates the event (time limit etc.) that caused the generation of a partial record. Describes the bit-rate the UMTS 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 Bit Rate can be used 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). Indicates if a Initial Call Attempt call from GsmSCF. Indicates if a USSD call back when a CAMEL subscriber roams aboard. Indicates the type of Modem used. This may be present when access in BSC. 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. The address of original called party.
0x9F 36 0x9F 37
Maximum bit rate
0x9F 38
ENUMERATED (1)
Initial Call Attempt Flag USSD Call back Flag Modem Type Classmark3 Charged Party
0x9F 81 09 0x9F 81 0A 0x9F 81 0B 0x9F 81 0C 0x9F 81 0D
NULL(0)
NULL(0)
ENUMERATED (1) OCTET(2) ENUMERATED (1)
O O
O O
Original Called Number
0x9F 81 0E
ADRESS(2..17)
Issue 07 (2007-10-10)
A-29
A CDR Format
Field Calling Charge Area Code Called Charge Area Code Default call handling
2G O
3G O
TAG 0x9F 81 11 0x9F 81 12 0x9F 81 16
TYPE OCTET(1..3)
Description Indicates the calling party logical area for distance charge Indicates the called party logical area for distance charge Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. This field contains data sent by the gsmSCF in the FCI message(s). The data can be sent either in one FCI message or several FCI messages with append indicator. Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Numbers that counts how often armed detection points (TDP and EDP) were encountered. Indicator for the complexity of the CAMEL feature used. The Mobile Station Roaming Number employed to route this connection (Served subscribers Roaming Number). This field indicates the cic, only present in case of incoming call and TDM bear type. This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates the priority of call. See 24.008 Indicates the called subscribers priority. See 29.002
OCTET(1..3)
ENUMERATED (1)
Free format Data
0x9F 81 17
OCTET(1..160)
Free format data append indicator Number of DP encountered Level of CAMEL service Roaming Number
0x9F 98
BOOLEAN(1)
0x9F 81 19 0x9F 81 1A 0x9F 81 20
INTEGER(1)
BIT STRING(2)
ADRESS(2..17)
MSC Incoming Circuit RNC or BSC Id MSC Id or SPC Call Emlpp Priority Called Default Emlpp Priority
0x9F 81 26 0x9F 81 27 0x9F 81 28 0x9F 81 2A 0x9F 81 2B
INTEGER(1..2)
M M O O
M M O O
A-30
Issue 07 (2007-10-10)
A CDR Format
Field Ea Subscriber Info Selected CIC optimalRout ingFlag Ported flag
2G O
3G O
TAG 0x9F 81 2E 0x9F 81 2F 0x9F 81 31 0x9F 81 34 0x9F 81 3C 0xBF 81 3D 0x9F 81 3E 0x9F 81 40 0x9F 81 41 0x9F 81 42 0x9F 81 43
TYPE OCTET(3)
Description Indicates the calling subscribers information of Equal Access Indicates the selected code of Carrier identification Reserved for the future Indicates if called party be ported. Indicates CGI of GSM or SAI of WCDMA A list of changes in CGI / SAI each time-stamped. Indicates the category of subscriber. Indicates the MCC and MNC of the network where call is initiated. Indicates the MCC and MNC of the network where call is served only present after handover. Indicates the MCC and MNC of the network where call is served only present after handover. Indicates the subscriber with a Incoming Access.
O O
O O
OCTET(3) NULL ENUMERATED (1) OCTET(7) SEQUENCE OF (22 * n) OCTET(1) OCTET(3)
Global Area ID Change Of Global Area ID Subscriber Category First MCC MNC Intermediate MCC MNC Last MCC MNC CUG Outgoing Access Indicator CUG Interlock Code CUG Incoming Access Used CUG Index
O O
O O
M M
M M
OCTET(3)
OCTET(3)
ENUMERATED (1)
0x9F 81 44 0x9F 81 45 0x9F 81 46 0x9F 81 48
OCTET(4)
ENUMERATED (1) OCTET(2)
Indicates caller and called whether or not is in the same CUG group. The CUG index has significance only between the subscriber and network. Indicates the Subscriber is one with Hot Billing service.
Hot billing tag
INTEGER(1)
Issue 07 (2007-10-10)
A-31
A CDR Format
Field Redirecting Number Redirecting Counter Called party number
2G C O M
3G C O M
TAG 0x9F 81 49 0x9F 81 4A 0x9F 81 4D
TYPE ADRESS(2..17) INTEGER(1) ADRESS(2..17)
Description The MSISDN of the forwarding party. Times of call forwarding. The address of the called party 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 A-5 Roaming record Field Record Type Served IMSI Served MSISDN Calling Number Roaming Number Recording Entity Incoming ROUTE Outgoing ROUTE Basic service 2G M 3G M TAG 0x80 01 02 0x81 0x82 0x83 0x84 TYPE NUMERATED (1) TBCD(3..8) ADRESS(2..9) ADRESS(2..17) ADRESS(2..17) IMSI of the called (roaming) party. The MSISDN of the called (roaming) party. The address of the calling party, if available. The Mobile Station Roaming Number employed to route this connection. The E.164 number of the GMSC The GMSC route on which the call originated. The route on which the call left the GMSC Bearer or teleservice employed. Description Roaming record.
M O C M
M O C M
M O O M
M O O M
0x85 0xA6 0xA7 0xA8
ADRESS(2..9) IA5(1..10) IA5(1..10) OCTET(3)
A-32
Issue 07 (2007-10-10)
A CDR Format
Field Transparenc y Indicator
2G C
3G C
TAG 0x89
TYPE ENUMERATED (1)
Description Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent mode. A list of changes of basic service during a connection each time-stamped. Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked. Seizure time: time of incoming traffic channel seizure (This timestamp is not supported now.) Answer time: time of answer (for successful calls) Release time: time of traffic channel release
Change Of Service Supplement ary Services
0xAA
SEQUENCE OF ( (18..27) * n)
0xAB
Event time stamps
C C O
C C O
0x8C 0x8D 0x8E
OCTET(9) OCTET(9) OCTET(9)
Call duration
0x8F
INTEGER(1..2)
The chargeable duration of the connection for successful calls, the holding time of call attempts. The reason for the release of the connection. A more detailed reason for the release of the connection. A local identifier distinguishing between transactions on the same MS Partial record sequence number, only present in case of partial records. A set of network/ manufacturer specific extensions to the record, when available. An identifier to correlate transactions on the same call taking place in different network nodes shall be present.
Cause for termination Diagnostics Call reference Sequence no. Record extensions Network call reference
M O M
M O M
0x91 0xB2 0x93
INTEGER(1) INTEGER(4) OCTET(1..8)
0x94
INTEGER(1)
0xB5
SET OF (11 * n)
0x96
OCTET(1..8)
Issue 07 (2007-10-10)
A-33
A CDR Format
Field MSC Address
2G C
3G C
TAG 0x97
TYPE ADRESS(2..9)
Description This field contains the E.164 number assigned to the MSC that generated the network call reference. Shall be present only if CAMEL is applied. Indicates the event (time limit etc.) that caused the generation of a partial record. Charge/no charge indicator and additional charging parameters 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. The address of original called party. Indicates the calling party logical area for distance charge Indicates the called party logical area for distance charge This field indicates the cic, only present in case of outgoing bear type being TDM. This field indicates the cic, only present in case of incoming bear type being TDM. This field indicates the SPC of MSC. Indicates the priority of call. See 24.008 Indicates the calling subscribers information of Equal Access Indicates the selected code of Carrier identification Reserved for the future
Partial Record Type Additional Chg. Info Charged Party
0x9E
ENUMERATED (1)
O O
O O
0xBF 81 05 0x9F 81 0D
SEQUENCE(3) ENUMERATED (1)
Original Called Number Calling Charge Area Code Called Charge Area Code MSC Outgoing Circuit MSC Incoming Circuit MSC Id or SPC Call Emlpp Priority Ea Subscriber Info Selected CIC optimalRout ingFlag
0x9F 81 0E 0x9F 81 11 0x9F 81 12 0x9F 81 26 0x9F 81 27 0x9F 81 28 0x9F 81 2A 0x9F 81 2E 0x9F 81 2F 0x9F 81 31
ADRESS(2..17)
OCTET(1..3)
OCTET(1..3)
INTEGER(1..2)
INTEGER(1..2)
M O O
M O O
O -
O -
OCTET(3) NULL
A-34
Issue 07 (2007-10-10)
A CDR Format
Field Subscriber Category CUG Outgoing Access Indicator CUG Interlock Code Hot billing tag
2G O O
3G O O
TAG 0x9F 81 3E 0x9F 81 43
TYPE OCTET(1) ENUMERATED (1)
Description Indicates the category of subscriber. Indicates the subscriber with a Outgoing Access.
0x9F 81 46 0x9F 81 48
OCTET(4)
INTEGER(1)
Indicates the Subscriber with 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 A-6 Incoming gateway record Field Record Type Calling Number Called Number 2G M 3G M TAG 0x80 01 03 0x81 0x82 TYPE ENUMERATED (1) ADRESS(2..17) ADRESS(2..17) The number of the calling party if available at this node. The address of the called party as seen by the GMSC. This is the number employed by the GMSC for routing. The E.164 number of the GMSC The incoming GMSC route on which the call originated. The route on which the call left the GMSC. Description Incoming gateway record
M M
M M
Recording Entity Incoming ROUTE Outgoing ROUTE
M M M
M M M
0x83 0xA4 0xA5
ADRESS(2..9) IA5(1..10) IA5(1..10)
Issue 07 (2007-10-10)
A-35
A CDR Format
Field Event time stamps:
2G M OO CO
3G M O O CO
TAG 0x9F 81 49 0x86 0x9F 81 4A 0x87 0x88
TYPE OCTET(9) OCTET(9) OCTET(9) OCTET(9) OCTET(9)
Description Setup or IAM timestamp from calling side Seizure of incoming traffic channel Alerting or ACM timestamp from called side Answer (successful calls only) Release of incoming trunk
Call duration
0x89
INTEGER(1..2)
The accountable duration (answer -> release of incoming trunk) of the connection if successful. The reason for the release of the connection. A more detailed reason for the release of the connection A local identifier distinguishing between transactions. Partial record sequence number, if applicable. A set of network/ manufacturer specific extensions to the record. Indicates the event (time limit etc.) that caused the generation of a partial record. Present if this parameter is signalled back from the VMSC to the GMSC in the access transport parameter of the Answer message (ANM), see TS 29.007 Present if this parameter is signaled back from the VMSC to the GMSC in the access transport parameter of the Answer message (ANM), see TS 29.007
Cause for term. Diagnostics Call Reference Sequence no. Record extensions Partial Record Type ISDN Bearer Capability
M O M
M O M
0x8B 0xAC 0x8D
C O
C O
0x8E 0xAF
INTEGER(1) SET OF n) (11 *
0x96
ENUMERATED (1)
0x97
OCTET(1..12)
Low Layer Compatibilit y
0x98
OCTET(1..18)
A-36
Issue 07 (2007-10-10)
A CDR Format
Field High Layer Compatibilit y
2G O
3G O
TAG 0x99
TYPE OCTET(1..12)
Description Present if this parameter is signalled back from the VMSC to the GMSC in the access transport parameter of the Answer message (ANM), see TS 29.007 Bearer or teleservice employed. Charge/no charge indicator and additional charging parameters 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. The address of original called party. Present if rate adaption parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008. The Mobile Station Roaming Number employed to route this connection, if applicable. This field indicates the cic, only present in case of incoming bear type being TDM. This field indicates the SPC of MSC. Indicates the priority of call. See 24.008 Indicates the calling subscribers information of Equal Access Indicates the selected code of Carrier identification
Basic Service Code Additional Chg. Info Charged Party
0xBF 81 02 0xBF 81 05 0x9F 810D
OCTET(3)
SEQUENCE(3)
ENUMERATED (1)
Original Called Number Rate Indication
0x9F 81 0E 0x9F 81 1F
ADRESS(2..17)
OCTET(1)
Roaming Number MSC Incoming Circuit MSC Id or SPC Call Emlpp Priority Ea Subscriber Info Selected CIC
0x9F 81 20 0x9F 81 27
ADRESS(2..17)
INTEGER(1..2)
M O C
M O C
0x9F 81 28 0x9F 81 2A 0x9F 81 2E 0x9F 81 2F
OCTET(3)
Issue 07 (2007-10-10)
A-37
A CDR Format
Field CUG Outgoing Access Indicator CUG Interlock Code CUG Incoming Access Used mscIncomin gRouteAttri bute mscOutgoin gRouteAttri bute Network call reference
2G O
3G O
TAG 0x9F 81 43
TYPE ENUMERATED (1)
Description Indicates the subscriber with a Outgoing Access.
0x9F 81 44 0x9F 81 45 0x9F 81 46 0x9F 81 47 0x9F 81 48
COTET(4)
Network code + CUG interlock Indicates caller and called whether or not is in the same CUG group msc incoming trunk attribute
ENUMERATED (1) ENUMERATED (1) ENUMERATED (1) OCTET(1..8)
msc Outgoing trunk attribute
An identifier to correlate transactions on the same call 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 A-7 Outgoing gateway record Field Record Type Calling Number Called Number 2G M 3G M TAG 0x80 01 04 0x81 0x82 TYPE ENUMERATED (1) ADRESS(2..17) ADRESS(2..17) The number of the calling party if available at this node. The address of the called party as seen by the GMSC. This is the number employed by the GMSC for routing. Description Outgoing gateway record
M M
M M
A-38
Issue 07 (2007-10-10)
A CDR Format
Field Recording Entity Incoming ROUTE Outgoing ROUTE Event time stamps:
2G M M M M OO CO
3G M M M M O O CO
TAG 0x83 0xA4 0xA5 0x9F 81 49 0x86 0x9F 81 4A 0x87 0x88
TYPE ADRESS(2..9) IA5(1..10) IA5(1..10) OCTET(9) OCTET(9) OCTET(9) OCTET(9) OCTET(9)
Description The E.164 number of the GMSC The incoming GMSC route on which the call originated. The route on which the call left the GMSC. Setup or IAM timestamp from calling side Seizure of incoming traffic channel Alerting or ACM timestamp from called side Answer (successful calls only) Release of incoming trunk
Call duration
0x89
INTEGER(1..2)
The accountable duration (answer -> release of outgoing trunk) of the connection if successful. The reason for the release of the connection. A more detailed reason for the release of the connection A local identifier distinguishing between transactions. Partial record sequence number, if applicable. A set of network/ manufacturer specific extensions to the record. Indicates the event (time limit etc.) that caused the generation of a partial record. Bearer or teleservice employed. Charge/no charge indicator and additional charging parameters
Cause for term. Diagnostics Call Reference Sequence no. Record extensions Partial Record Type Basic Service Code Additional Chg. Info
M O M
M O M
0x8B 0xAC 0x8D
C O
C O
0x8E 0xAF
INTEGER(1) SET OF (11*n )
0x96
ENUMERATED (1)
0xBF 81 02 0xBF 81 05
OCTET(3)
SEQUENCE(3)
Issue 07 (2007-10-10)
A-39
A CDR Format
Field Charged Party
2G O
3G O
TAG 0x9F 81 0D
TYPE ENUMERATED (1)
Description 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. The address of original called party. Present if rate adaption parameters for the basic service were signalled between the MS/UE and the network, see TS 24.008. The Mobile Station Roaming Number employed to route this connection, if applicable. This field indicates the cic, only present in case of outgoing bear type being TDM. This field indicates the SPC of MSC. Indicates the calling subscribers information of Equal Access Indicates the selected code of Carrier identification Indicates the priority of call. See 24.008 Indicates the subscriber with a Outgoing Access.
Original Called Number Rate Indication
0x9F 81 0E 0x9F 81 1F
ADRESS(2..17)
OCTET(1)
Roaming Number MSC Outgoing Circuit MSC Id or SPC Ea Subscriber Info Selected CIC Call Emlpp Priority CUG Outgoing Access Indicator CUG Interlock Code CUG Incoming Access Used mscIncomin gRouteAttri bute
0x9F 81 20 0x9F 81 26
ADRESS(2..17)
INTEGER(1..2)
M C
M C
0x9F 81 28 0x9F 81 2E 0x9F 81 2F 0x9F 81 2A 0x9F 81 43
OCTET(3) OCTET(3)
C O O
C O O
OCTET(3) OCTET(1) ENUMERATED (1)
0x9F 81 44 0x9F 81 45 0x9F 81 46
OCTET(4)
Network code + CUG interlock Indicates caller and called whether or not is in the same CUG group msc incoming trunk attribute
A-40
Issue 07 (2007-10-10)
A CDR Format
Field mscOutgoin gRouteAttri bute Network call reference
2G O
3G O
TAG 0x9F 81 47 0x9F 81 48
TYPE ENUMERATED (1) OCTET(1..8)
Description msc Outgoing trunk attribute
An identifier to correlate transactions on the same call taking place in different network nodes shall be 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 A-8 Transit record Field Record Type Recording Entity Incoming ROUTE Outgoing ROUTE Calling Number Called Number ISDN Basic Service 2G M 3G M TAG 0x80 01 05 0x81 0xA2 0xA3 0x84 TYPE ENUMERATED (1) ADRESS(2..9) IA5(1..10) IA5(1..10) ADRESS(2..17) The E.164 number of the transit MSC The TMSC route on which the call originated. The route on which the call left the TMSC. The number of the calling party if available at this node. The address of the called party as seen by the TMSC. The ISDN basic service employed Description Transit.
M M M M
M M M M
M O
M O
0x85 0x86
ADRESS(2..17) OCTET(1)
Issue 07 (2007-10-10)
A-41
A CDR Format
2G M O O CO
3G M OO CO
TAG 0x9F 81 49 0x87 0x9F 81 4A 0x88 0x89
Description Setup or IAM timestamp from calling side Seizure of incoming traffic channel Alerting or ACM timestamp from called side Answer (successful calls only) Release of traffic channel
Call duration Cause for term. Diagnostics
M M O
M M O
0x8A 0x8C 0xAD
INTEGER(1..2) INTEGER(1) INTEGER(4)
The chargeable duration of the connection if successful. The reason for the release of the connection. A more detailed reason for the release of the connection. A local identifier distinguishing between transactions. Partial record sequence number, if applicable. A set of network/ manufacturer specific extensions to the record. Indicates the event (time limit etc.) that caused the generation of a partial record. Bearer or teleservice employed. Charge/no charge indicator and additional charging parameters The address of original called party. Present if rate adaption parameters for the basic service were signalled between the MS/UE and the network, see TS 24.008.
Call Reference Sequence no. Record extensions Partial Record Type Basic Service Code Additional Chg. Info Original Called Number Rate Indication
0x8E
OCTET(1..8)
C O
C O
0x8F 0xB0
INTEGER(1) SET OF (11 * n)
0x97
ENUMERATED (1)
0xBF 81 02 0xBF 81 05 0x9F 81 0E 0x9F 81 1F
OCTET(3)
SEQUENCE(3)
ADRESS(2..17)
OCTET(1)
A-42
Issue 07 (2007-10-10)
A CDR Format
Field MSC Incoming Circuit MSC Outgoing Circuit MSC Id or SPC Call Emlpp Priority Ea Subscriber Info Selected CIC CUG Outgoing Access Indicator CUG Interlock Code CUG Incoming Access Used mscIncomin gRouteAttri bute mscOutgoin gRouteAttri bute Network call reference
2G C
3G C
TAG 0x9F 81 27
TYPE INTEGER(1..2)
Description This field indicates the cic, only present in case of incoming bear type being TDM. This field indicates the cic, only present in case of outgoing bear type being TDM. This field indicates the SPC of MSC. Indicates the priority of call. See 24.008 Indicates the calling subscribers information of Equal Access Indicates the selected code of Carrier identification Indicates the subscriber with a Outgoing Access.
0x9F 81 26
INTEGER(1..2)
M O C
M O C
0x9F 81 28 0x9F 81 2A 0x9F 81 2E 0x9F 81 2F 0x9F 81 43
C O
C O
0x9F 81 44 0x9F 81 45 0x9F 81 46 0x9F 81 47 0x9F 81 48
OCTET(4)
Network code + CUG interlock Indicates caller and called whether or not is in the same CUG group msc incoming trunk attribute msc Outgoing trunk attribute An identifier to correlate transactions on the same call taking place in different network nodes shall be present.
ENUMERATED (1) ENUMERATED (1) ENUMERATED (1) OCTET(1..8)
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.
Issue 07 (2007-10-10)
A-43
A CDR Format
Table A-9 SMS-MO record Field Record Type Served IMSI Served IMEI Served MSISDN MS Classmark Service Centre Recording Entity Location 2G M 3G M TAG 0x80 01 06 0x81 0x82 TYPE ENUMERATED (1) TBCD(3..8) TBCD(8) The IMSI of the subscriber sending the short message. The IMEI of the ME sending the message, if available. The primary MSISDN of the subscriber sending the message. The mobile station classmark. The address (E.164) of the SMS-service centre. The E.164 number of the visited MSC The Location Area Code and Cell Identifier from which the message originated. A reference, provided by the MS uniquely identifying this message. The time at which the message was received by the MSC from the subscriber. The result of the attempted delivery if unsuccessful. A set of network/ manufacturer specific extensions to the record. The destination short message subscriber number. Set of CAMEL information IEs. Each of these IEs contains information related to CAMEL call leg related for the SMS. Description SMS-Mobile originated.
M O
M O
0x83
ADRESS(2..9)
M M M O
M M M O
0x84 0x85 0x86 0xA7
OCTET(2..3) ADRESS(2..9) ADRESS(2..9) OCTET(8)
Message Reference Event Time stamp
0x88
OCTET (3..8)
0x89
OCTET(9)
SMS Result Record extensions Destination number CAMEL SMS Information
C O
C O
0xAA 0xAB
INTEGER (4) SET OF (11 * n)
0x8C
ADRESS(2..17)
0xAD
SET (34..58)
A-44
Issue 07 (2007-10-10)
A CDR Format
Field System Type
2G M
3G M
TAG 0x8E
TYPE ENUMERATED (1)
Description 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. Bearer or teleservice employed. Charge/no charge indicator and additional charging parameters May be present when access in BSC. 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. This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates CGI of GSM or SAI of WCDMA Indicates the category of subscriber. Indicates the MCC and MNC of the network where sms is initiated. Indicates the user data type such as normal SMS, picture, text. Indicates the content of subscriber.(Note1) Indicates the maximum of the concatenated SMS
Basic Service Code Additional Chg. Info Classmark3 Charged Party
0xBF 81 02 0xBF 81 05 0x9F 81 0C 0x9F 81 0D
OCTET(3)
SEQUENCE(3)
O O
O O
RNC or BSC Id MSC Id or SPC Global Area ID Subscriber Category First MCC MNC SMS User Data Type SMS Text Maximum Number Of SMS In The Concatenate d SMS
M M O M M
M M O M M
0x9F 81 27 0x9F 81 28 0x9F 81 3C 0x9F 81 3E 0x9F 81 40 0x9F 81 43 0x9F 81 44 0x9F 81 45
OCTET(1)
C C
C C
OCTET(1..160) INTEGER(1)
Issue 07 (2007-10-10)
A-45
A CDR Format
Field Concatenate d SMS Reference Number Sequence Number Of The Current SMS Hot billing tag Call reference
2G C
3G C
TAG 0x9F 81 46
TYPE INTEGER(1..2)
Description Indicates the reference number of concatenated SMS Indicates the sequence of concatenated sms, such as 1, 2,maximum Number Of SMS In The Concatenated SMS Indicates the Subscriber with Hot Billing service. A local identifier distinguishing between transactions on the same MS
0x9F 81 47
INTEGER(1)
C M
C M
0x9F 81 48 0x9F 81 49
INTEGER(1) OCTET(1..8)
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 A-10 SMS-MT record Field Record Type Service Centre Served IMSI Served IMEI Served MSISDN MS Classmark Recording Entity Location 2G M 3G M TAG 0x80 01 07 0x81 0x82 0x83 0x84 0x85 0x86 0xA7 TYPE ENUMERATED (1) ADRESS(2..9) TBCD(3..8) TBCD(8) ADRESS(2..9) OCTET(2..3) ADRESS(2..9) OCTET(8) The E.164 address of the SMS service centre. The IMSI of the receiving party. The IMEI of the receiving party, if available. The MSISDN of the receiving party. The mobile station classmark. The E.164 number of the visited MSC. The Location Area Code and Cell Identifier to which the message was delivered. Description SMS-Mobile Terminated.
M M O M M M O
M M O M M M O
A-46
Issue 07 (2007-10-10)
A CDR Format
Field Event time stamp SMS Result Record extensions System Type
2G M
3G M
TAG 0x88
TYPE OCTET(9)
Description Delivery time stamp, time at which message was sent to the MS by the MSC. The result of the attempted delivery if unsuccessful. A set of network/ manufacturer specific extensions to the record. 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. Set of CAMEL information IEs. Each of these IEs contains information related to CAMEL call leg related for the SMS. Bearer or teleservice employed. Charge/no charge indicator and additional charging parameters May be present when access in BSC. 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. This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates CGI of GSM or SAI of WCDMA Indicates the category of subscriber.
C O
C O
0xA9 0xAA
0x8B
ENUMERATED (1)
CAMEL SMS Information
0xAC
SET (34..58)
Basic Service Code Additional Chg. Info Classmark3 Charged Party
0xBF 81 02 0xBF 81 05 0x9F 81 0C 0x9F 81 0D
OCTET(3)
SEQUENCE(3)
O O
O O
RNC or BSC Id MSC Id or SPC Global Area ID Subscriber Category
M M O M
M M O M
0x9F 81 27 0x9F 81 28 0x9F 81 3C 0x9F 81 3E
Issue 07 (2007-10-10)
A-47
A CDR Format
Field First MCC MNC SMS User Data Type SMS Text Maximum Number Of SMS In The Concatenate d SMS Concatenate d SMS Reference Number Sequence Number Of The Current SMS Hot billing tag Origination number Call reference
2G M
3G M
TAG 0x9F 81 40 0x9F 81 43 0x9F 81 44 0x9F 81 45
TYPE OCTET(3)
Description Indicates the MCC and MNC of the network where sms is terminated. Indicates the user data type such as normal SMS, picture, text. Indicates the content of subscriber.(Note1) Indicates the maximum of the concatenated SMS
OCTET(1)
C C
C C
0x9F 81 46
INTEGER(1..2)
Indicates the reference number of concatenated SMS Indicates the sequence of concatenated SMS ,such as 1, 2,maximum Number OfSMS In The Concatenated SMS Indicates the Subscriber with Hot Billing service. The originating short message subscriber number. A local identifier distinguishing between transactions on the same MS
0x9F 81 47
INTEGER(1)
C M
C M
0x9F 81 48 0x9F 81 49 0x9F 81 50
INTEGER(1) ADRESS(2..17)
OCTET(1..8)
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.
A-48
Issue 07 (2007-10-10)
A CDR Format
Table A-11 LCS-MT record Field Record Type 2G M 3G M TAG 0x80 01 17 0x81 TYPE ENUMERATED (1) ADRESS(2..9) The E.164 number of the visited MSC producing the record. The type of the LCS client that invoked the LR. Further identification of the LCS client . The IMSI of the subscriber the LR is invoked for. The IMEI of the calling party the LR is executed for if available. The MSISDN of the subscriber the LR is invoked for. The type of the location request. QoS of the LR, if available. Description LCS-MT record.
Recording Entity LCS Client Type LCS Client Identity Served IMSI Served IMEI
0x82
ENUMERATED (1)
0xA3
SEQUENCE (13..29)
M O
M O
0x84 0x9F 66
TBCD(3..8) TBCD(8)
Served MSISDN Location Type LCS QoS
0x85
ADRESS(2..9)
0xA6
SEQUENCE (6..21)
0xA7
SEQUENCE (11)
LCS Priority MLC Number Event Time Stamp Measure Duration Notification To MS User
C M M O C
C M M O C
0x88 0x89 0x8A 0x8B 0x8C
OCTET(1) ADRESS(2..9) OCTET(9) INTEGER(1..2) ENUMERATED (1)
Priority of the LR, if available. The E.164 address of the requesting GMLC. The time at which the LR was received by the MSC. The duration of preceding the location request. The privacy notification to MS user that was applicable when the LR was invoked, if available. This parameter indicates if MS privacy was overridden by the LCS client, if available.
Privacy Override
0x8D
NULL(0)
Issue 07 (2007-10-10)
A-49
A CDR Format
Field Location
2G M
3G M
TAG 0xAE
TYPE OCTET(8)
Description The identity of the cell or the SAC occupied by the terminated party when the LCS was applied. The location estimate for the subscriber if contained in geographic position and the LR was successful. The positioning method used , if available. The result of the LR if any failure or partial success happened as known at the radio interface. The reason for the termination of the location service. A more detailed information about the Cause for Termination if any failure or partial success happened. Reserved for the future
Location Estimate
0x8F
OCTET(1..20)
Positioning Data LCS Cause
C O
C O
0x90 0x91
OCTET(1..33) OCTET(1)
Cause for Termination Diagnostics
0x95
INTEGER(1)
0xB2
INTEGER(4)
lcs Reference Number System Type
0x9F 65
OCTET STRING (SIZE (1..8)) ENUMERATED (1)
0x93
This field indicates the use 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. A set of network/ manufacturer specific extensions to the record. Charge/no charge indicator and additional charging parameters 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.
Record extensions Additional Chg. Info Charged Party
0xB4
SET OF (11 * n)
0xBF 81 05 0x9F 81 0D
SEQUENCE(3)
ENUMERATED (1)
A-50
Issue 07 (2007-10-10)
A CDR Format
Field RNC or BSC Id MSC Id or SPC Global Area ID Subscriber Category First MCC MNC Hot billing tag Call reference
2G M M O C M
3G M M O C M
TAG 0x9F 81 27 0x9F 81 28 0x9F 81 3C 0x9F 81 3E 0x9F 81 40 0x9F 81 48 0x9F 81 49
Description This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates CGI of GSM or SAI of WCDMA Indicates the category of subscriber. Indicates the MCC and MNC of the network where LCS is initiated. Indicates the Subscriber with Hot Billing service. A local identifier distinguishing between transactions on the same MS
C M
C M
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 A-12 LCS-MO record Field Record Type 2G M 3G M TAG 0x80 01 18 0x81 TYPE ENUMERATED (1) ADRESS(2..9) The E.164 number of the visited MSC producing the record. The type of the LCS client that invoked the LR, if available. Further identification of the LCS client, if available. The IMSI of the subscriber the LR is invoked for. The IMEI of the calling party the LR is executed for if available. Description LCS-MO record.
Recording Entity LCS Client Type LCS Client Identity Served IMSI Served IMEI
0x82
ENUMERATED (1)
0xA3
SEQUENCE (13..29)
M O
M O
0x84 0x9F 66
TBCD(3..8) TBCD(8)
Issue 07 (2007-10-10)
A-51
A CDR Format
Field Served MSISDN MOLR Type LCS QoS LCS Priority MLC Number Event Time Stamp Measure Duration Location
2G M
3G M
TAG 0x85
TYPE ADRESS(2..9)
Description The MSISDN of the subscriber the LR is invoked for. The type of the LR. QoS of the LR, if available. Priority of the LR, if available. The E.164 address of the involved GMLC, if available. The time at which the LR was received by the MSC. The duration of proceeding the location request . The identity of the cell or the SAC occupied by the originating party when the LCS was applied. The location estimate for the subscriber if contained in geographic position and the LR was successful. The positioning method used, if available. The result of the LR if any failure or partial success happened as known at the radio interface. The reason for the termination of the location service. A more detailed information about the Cause for Termination if any failure or partial success happened.
O C M M
O C M M
0x86 0xA7 0x88 0x89
INTEGER(1) SEQUENCE(11) OCTET(1) ADRESS(2..9)
M O M
M O M
0x8A 0x8B 0x8C
OCTET(9) INTEGER(1..2) OCTET(8)
Location Estimate
0xAD
OCTET(1..20)
C C
C C
0x8E 0x8F
0x93
INTEGER(1)
0xB0
INTEGER(4)
A-52
Issue 07 (2007-10-10)
A CDR Format
Field System Type
2G M
3G M
TAG 0x92
TYPE ENUMERATED (1)
Description This field indicates the use 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. A set of network/ manufacturer specific extensions to the record. Reserved for the future
Record extensions lcs Reference Number Additional Chg. Info Charged Party
0xB2
SET OF (11 * n)
0x9F 65
OCTET STRING (SIZE (1..8)) SEQUENCE(3)
0xBF 81 05 0x9F 81 0D
Charge/no charge indicator and additional charging parameters 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. This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates CGI of GSM or SAI of WCDMA Indicates the category of subscriber. Indicates the MCC and MNC of the network where LCS is initiated. Indicates the Subscriber with Hot Billing service. A local identifier distinguishing between transactions on the same MS
ENUMERATED (1)
RNC or BSC Id MSC Id or SPC Global Area ID Subscriber Category First MCC MNC Hot billing tag Call reference
M M O C M
M M O C M
0x9F 81 27 0x9F 81 28 0x9F 81 2C 0x9F 81 3E 0x9F 81 40 0x9F 81 48 0x9F 81 49
C M
C M
Issue 07 (2007-10-10)
A-53
A CDR Format
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 A-13 LCS-NI record Field Record Type 2G M 3G M TAG 0x80 01 19 0x81 TYPE ENUMERATED (1) ADRESS(2..9) The E.164 number of the visited MSC producing the record. The type of the LCS client that invoked the LR, if available. Further identification of the LCS client, if available. The IMSI of the calling party the LR is executed for if supplied by the UE. The MSISDN of the calling party the LR is executed for if supplied by the UE. The IMEI of the calling party the LR is executed for if available. The emergency service routing digits, if emergency call. The emergency service routing key, if emergency call. QoS of the LR, if available. Priority of the LR, if available. The E.164 address of the involved GMLC, if available. The time at which the LR was received by the MSC. Description LCS-NI record.
Recording Entity LCS Client Type LCS Client Identity Served IMSI
0x82
ENUMERATED (1)
0xA3
SEQUENCE (13..29)
0x84
TBCD(3..8)
Served MSISDN
0x85
ADRESS(2..9)
Served IMEI
0x86
TBCD(8)
EMS-Digits
0x87
ADRESS(2..9)
EMS-Key
0x88
ADRESS(2..9)
LCS QoS LCS Priority MLC Number Event Time Stamp
O C M
O C M
0xA9 0x8A 0x8B
SEQUENCE(11) OCTET(1) ADRESS(2..9)
0x8C
OCTET(9)
A-54
Issue 07 (2007-10-10)
A CDR Format
Field Measure Duration Location
2G O M
3G O M
TAG 0x8D 0xAE
TYPE INTEGER(1..2) OCTET(8)
Description The duration of proceeding the location request . The identity of the cell or the SAC occupied by the terminated party when the LCS was applied. The location estimate for the subscriber if contained in geographic position and the LR was successful. The positioning method used, if available. The result of the LR if any failure or partial success happened as known at the radio interface. The reason for the termination of the location service. More detailed information about the Cause for Termination if any failure or partial success happened. This field indicates the use 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. A set of network/ manufacturer specific extensions to the record. Reserved for the future
Location Estimate
0x8F
OCTET(1..20)
C C
C C
0x90 0x91
0x95
INTEGER(1)
0xB2
INTEGER(4)
System Type
0x93
INTEGER(1)
Record extensions lcs Reference Number Additional Chg. Info
0xB2
SET OF (11 * n)
0x9F 65
OCTET STRING (SIZE (1..8)) SEQUENCE(3)
0xBF 81 05
Charge/no charge indicator and additional charging parameters
Issue 07 (2007-10-10)
A-55
A CDR Format
Field Charged Party
2G O
3G O
TAG 0x9F 81 0D
TYPE ENUMERATED (1)
Description 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. This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates CGI of GSM or SAI of WCDMA Indicates the category of subscriber. Indicates the MCC and MNC of the network where LCS is initiated. Indicates the Subscriber with Hot Billing service. A local identifier distinguishing between transactions on the same MS
RNC or BSC Id MSC Id or SPC Global Area ID Subscriber Category First MCC MNC Hot billing tag Call reference
M M O C M
M M O C M
0x9F 81 27 0x9F 81 28 0x9F 81 3C 0x9F 81 3E 0x9F 81 40 0x9F 81 48 0x9F 81 49
C M
C M
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.
A-56
Issue 07 (2007-10-10)
A CDR Format
Table A-14 SS-action record Field Record Type Served IMSI Served IMEI Served MSISDN MS Classmark Recording Entity Location 2G M 3G M TAG 0x80 01 0A 0x81 0x82 0x83 TYPE ENUMERATED (1) TBCD(3..8) TBCD(8) ADRESS(2..9) Description Supplementary service action. The IMSI of the MS performing the action. The IMEI of the ME performing the action. The primary MSISDN of the party performing the action. The mobile station classmark. The E.164 number of the visited MSC / HLR. The identity of the cell or the SAC, including the location area code, from which the request originated. The basic service group(s) to which the supplementary service applies. This field is not provided if the action applies to all basic services. The supplementary service or group of supplementary services for which the request was made. May not be available in case of USSD. Activation, deactivation, interrogation etc. May not be available in case of USSD. The time at which the action was requested. Service dependent parameters or unstructured supplementary service data, if defined for the SS action recorded in this CDR.
M O M
M O M
M M O
M M O
0x84 0x85 0xA6
OCTET(2..3) ADRESS(2..9) OCTET(8)
Basic Services
0xA7
OCTET(3)
Supplement ary Service
0x88
OCTET(1)
SS Action
0x89
ENUMERATED (1)
SS Action time stamp SS Parameters
M C
M C
0x8A 0xAB
OCTET(9) OCTET STRING (7..53)
Issue 07 (2007-10-10)
A-57
A CDR Format
Field SS Action Result Call Reference
2G O
3G O
TAG 0xAC
TYPE INTEGER(4)
Description A more detailed reason for the release of the connection. A local identifier distinguishing between transactions at the same MS. A set of network/ manufacturer specific extensions to the record, when available. This field is present when either the UTRAN or GERAN air-interface is used. It is omitted when the service is provided by a GSM air interface In the case of USSD, indicates coding scheme of USSD In the case of USSD, indicates subscriber input In the case of USSD, indicates the times of notify procedure In the case of USSD, indicates the times of request procedure Charge/no charge indicator and additional charging parameters May be present when access in BSC. 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. This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC.
0x8D
OCTET(1..8)
Record extensions
0xAE
SET OF (11 * n)
System Type
0x8F
ENUMERATED (1)
USSD Coding Scheme USSD String USSD Notify Counter USSD Request Counter Additional Chg. Info Classmark3 Charged Party
0x9F 7E
OCTET(1)
O O
O O
0xBF 7F 0x9F 81 00 0x9F 81 01 0xBF 81 05 0x9F 81 0C 0x9F 81 0D
INTEGER(1)
SEQUENCE(3)
O O
O O
RNC or BSC Id MSC Id or SPC
M M
M M
0x9F 81 27 0x9F 81 28
OCTET(3) OCTET(3)
A-58
Issue 07 (2007-10-10)
A CDR Format
Field Global Area ID Subscriber Category First MCC MNC Hot billing tag
2G O C M
3G O C M
TAG 0x9F 81 3C 0x9F 81 3E 0x9F 81 40 0x9F 81 48
Description Indicates CGI of GSM or SAI of WCDMA Indicates the category of subscriber. Indicates the MCC and MNC of the network where SS action is initiated. Indicates the Subscriber with Hot Billing service.
INTEGER(1)
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 A-15 HLR interrogation record Field Record Type Served IMSI Served MSISDN Recording Entity Basic Service Routing Number 2G M 3G M TAG 0x80 01 0B 0x81 0x82 TYPE ENUMERATED (1) TBCD(3..8) ADRESS(2..9) The IMSI of the party being interrogated, if successful The MSISDN of the subscriber being interrogated. The E.164 Number of the HLR / MSC. Only for teleservice 21 (SMS-MT). Routing number (MSRN, forwarding no.) provided by the HLR if the interrogation was successful. Time at which the interrogation was invoked. The number of times the call has been forwarded if provided by ISUP. Description HLR interrogation.
C M
C M
M O C
M O C
0x83 0xA4 0xA5
ADRESS(2..9) OCTET(3) ADRESS(2..17)
Interrogatio n time stamp Number of Forwarding
0x86
OCTET(9)
0x87
INTEGER(1)
Issue 07 (2007-10-10)
A-59
A CDR Format
Field interrogatio n Result Record extensions
2G O
3G O
TAG 0x87
TYPE INTEGER(4)
Description A more detailed reason for the release of the connection. A set of network/ manufacturer specific extensions to the record, when available. This field indicates the SPC of MSC. A local identifier distinguishing between transactions on the same MS
0xA9
SET OF (11 * n)
MSC Id or SPC Call reference
M M
M M
0x9F 81 28 0x9F 81 29
OCTET(3) OCTET(1..8)
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 A-16 Common equipment usage record Field Record Type Equipment type Equipment Id. Served IMSI Served IMEI Served MSISDN Recording Entity Basic service 2G M 3G M TAG 0x80 01 0E 0x81 0x82 0x83 TYPE ENUMERATED (1) INTEGER(1) INTEGER(1) TBCD(3..8) Description Common equipment usage record. e.g. Conference circuit. The local id. Of the equipment employed. The IMSI of the party responsible for the seizure of the equipment.. IMEI of the calling ME, if available. The primary MSISDN of the served party.. The E.164 number of the MSC in which the equipment is located. Bearer or teleservice employed, if appropriate.
M C M
M C M
C O M
C O M
0x9F 66 0x84 0x85
TBCD(8) ADRESS(2..9) ADRESS(2..9)
0xA6
OCTET(3)
A-60
Issue 07 (2007-10-10)
A CDR Format
Field Change Of Service Supp. Services Event Time Stamp
2G O
3G O
TAG 0xA7
TYPE SEQUENCE OF ( (18..27) * n)
Description A list of changes of basic service during a connection each time-stamped. Supplementary services invoked in connection with this equipment. Seizure time: the time at which the equipment was seized. Release time: the time at which the equipment was released.
0xA8
M O
M O
0x89 0x8A
OCTET(9)
Call Duration Call Reference Sequence no. Record extensions
M M
M M
0x8B 0x8C
INTEGER(1..2) OCTET(1..8)
The total duration of the usage of the equipment. A local identifier distinguishing between transactions. Partial record sequence number if applicable. A set of network/ manufacturer specific extensions to the record, when available. 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. Present if "rate adaption" parameters for the basic service were signalled between the MS/UE and the network, see TS 24.008. Indicates the user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections. Indicates the event (time limit etc.) that caused the generation of a partial record.
C O
C O
0x8D 0xAE
System Type
0x8F
ENUMERATED (1)
Rate Adaptation
0x90
OCTET(1)
0x91
ENUMERATED (1)
Partial Record Type
0x92
ENUMERATED (1)
Issue 07 (2007-10-10)
A-61
A CDR Format
Field Cause for termination Diagnostics
2G M O
3G M O
TAG 0x9F 64 0xBF 65
TYPE INTEGER(1) INTEGER(4)
Description The reason for the release of the connection. A more detailed reason for the release of the connection. Charge/no charge indicator and additional charging parameters This field indicates the SPC of RNC or BSC. This field indicates the SPC of MSC. Indicates the category of subscriber. Indicates the Subscriber with Hot Billing service.
Additional Chg. Info RNC or BSC Id MSC Id or SPC Subscriber Category Hot billing tag
0xBF 81 05 0x9F 81 27 0x9F 81 28 0x9F 81 3E 0x9F 81 48
SEQUENCE(3)
M M C C
M M C C
OCTET(3) OCTET(3) OCTET(1) INTEGER(1)
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 A-17 Terminating CAMEL record Field Record Type Served IMSI Served MSISDN Recording Entity Interrogatio n time stamp 2G M 3G M TAG 0x80 01 11 0x81 0x82 0x83 0x84 TYPE ENUMERATED (1) TBCD(3..8) ADRESS(2..9) ADRESS(2..9) OCTET(9) Description Terminating CAMEL interrogation. IMSI of the called party The MSISDN of the called party. The E.164 number of the GMSC. Time at which the interrogation was invoked.
M O M M
M O M M
A-62
Issue 07 (2007-10-10)
A CDR Format
Field CAMEL Destination Number GsmSCF Address Service key Network call reference MSC Address
2G M
3G M
TAG 0x85
TYPE ADRESS(2..17)
Description The number available for routing after the CAMEL server enquiry. The CAMEL server serving the subscriber. The CAMEL service logic to be applied. An identifier to correlate transactions on the same call taking place in different network nodes. This field contains the E.164 number assigned to the MSC that generated the network call reference. Indicates whether or not a CAMEL call encountered default call handling. This field shall be present only if default call handling has been applied. A set of network/ manufacturer specific extensions to the record, when available. The address of the called party as received by the GMSC/gsmSSF. The address of the calling party, if available. The GMSC route on which the call originated. If available in 3G, this parameter shall be supplied. The route on which the call left the GMSC. If available in 3G, this parameter shall be supplied.
M M M
M M M
0x86 0x87 0x88
ADRESS(2..9) INTEGER(1..4) OCTET(1..8)
0x89
ADRESS(2..9)
Default call handling
0x8A
ENUMERATED (1)
Record extensions
0xAB
SET OF(11 * n)
Called Number Calling Number Incoming ROUTE
0x8C
ADRESS(2..17)
C O
C O
0x8D 0xAE
ADRESS(2..17) IA5(1..10)
Outgoing ROUTE
0xAF
IA5(1..10)
Issue 07 (2007-10-10)
A-63
A CDR Format
2G C C O
3G C C O
TAG 0x90 0x91 0x92
Description Seizure time: time of incoming traffic channel seizure (This timestamp is not supported now.) Answer time: time of answer (for successful calls) Release time: time of traffic channel release
Call duration
0x93
INTEGER(1..2)
The chargeable duration of the connection for successful calls, the holding time of call attempts. The reason for the release of the connection. A more detailed reason for the release of the connection. A local identifier distinguishing between transactions on the same MS Partial record sequence number, only present in case of partial records. Numbers that counts how often armed detection points (TDP and EDP) were encountered. Indicator of the complexity of the CAMEL feature used. This field contains data sent 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. Set of CAMEL information IEs. Each of these Ies contains information related to one outgoing CAMEL call leg.
Cause for termination Diagnostics
M O
M O
0x95 0xB6
INTEGER(1) INTEGER(4)
Call reference
0x97
OCTET(1..8)
Sequence no. Number of DP encountered Level of CAMEL service Free format Data
0x98
INTEGER(1)
0x99
INTEGER(1)
0x9A
BIT STRING(2)
0x9B
OCTET(1..160)
CAMEL call leg information
0xBC
SEQUENCE OF ((104..124) * n)
A-64
Issue 07 (2007-10-10)
A CDR Format
Field Free format data append indicator
2G C
3G C
TAG 0x9D
TYPE BOOLEAN(1)
Description Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR. Indication if the CAMEL call handling is active in the MSC server. Indicates whether or not a 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. Identifies the CAMEL server serving the subscriber for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. The CAMEL service logic to be applied for 2nd service such as dialled service. Shall be present only if CAMEL is applied for 2nd service. This field contains data sent 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. Indicator if free format data for 2nd service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for 2nd service.
MSC server indication Default call handling 2
0x9E
BOOLEAN(1)
0x9F 0x1F
ENUMERATED (1)
GsmSCF address 2
0x9F 20
ADRESS(2..9)
Service key 2
0x9F 21
INTEGER(1..4)
Free format Data 2
0x9F 22
OCTET(1..160)
Free format data append indicator 2
0x9F 23
BOOLEAN(1)
Issue 07 (2007-10-10)
A-65
A CDR Format
Field Partial Record Type Basic Service Code Additional Chg. Info Charged Party
2G O
3G O
TAG 0x9F 2A
TYPE ENUMERATED (1)
Description Indicates the event (time limit etc.) that caused the generation of a partial record. Bearer or teleservice employed. Charge/no charge indicator and additional charging parameters 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. The address of original called party. This field indicates the SPC of MSC. Indicates the category of subscriber. Indicates the Subscriber with Hot Billing service.
0xBF 81 02 0xBF 81 05 0x9F 81 0D
OCTET(3)
SEQUENCE(3)
ENUMERATED (1)
Original Called Number MSC Id or SPC Subscriber Category Hot billing tag
0x9F 81 0E 0x9F 81 28 0x9F 81 3E 0x9F 81 48
ADRESS(2..17)
M O C
M O C
OCTET(3) OCTET(1) INTEGER(1)
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 A-18 IMEI ticket Field Served IMEI 2G M 3G M TAG 0x80 TYPE TBCD(8) Description IMEI of the observed mobile equipment
A-66
Issue 07 (2007-10-10)
A CDR Format
Field IMEI Status
2G M
3G M
TAG 0x81
TYPE ENUMERATED (1)
Description The result of the IMEI check e.g. blacklisted, greylisted, unknown. The IMSI of the subscriber currently using the mobile equipment. The MSISDN of the 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 The E.164 number of the recording MSC. The time at which the IMEI check was performed. The location area code and cell identity of the cell from which the mobile equipment was used. The event that caused IMEI checking to take place Only available if the IMEI check was related to an MOC or MTC A set of network/ manufacturer specific extensions to the record, when available. This field indicates the SPC of MSC.
Served IMSI Served MSISDN
0x82
TBCD(3..8)
0x83
ADRESS(2..9)
Recording Entity Event Time Stamp Location
M M M
M M M
0x84 0x85 0xA6
ADRESS(2..9) OCTET(9) OCTET(8)
IMEI Check Event Call Reference Record extensions
O O
O O
0x87 0x88
0xA9
SET OF (11 * n)
MSC Id or SPC
0x9F 81 28
OCTET(3)
A.6 Description of Record Fields

This clause contains a brief description of each field of the CDRs described in the previous clause
Issue 07 (2007-10-10)
A-67
A CDR Format
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 { noIndication noCharge charge } (2) (0),
::= INTEGER
(1),
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 { --- See Bearer Capability TS 24.008 -- (note that value "4" is intentionally missing -- because it is not used in TS 24.008) -::= ENUMERATED
aiur09600BitsPerSecond aiur14400BitsPerSecond aiur19200BitsPerSecond aiur28800BitsPerSecond aiur38400BitsPerSecond aiur43200BitsPerSecond aiur57600BitsPerSecond aiur38400BitsPerSecond1 aiur38400BitsPerSecond2 aiur38400BitsPerSecond3
(1), (2), (3), (5), (6), (7), (8), (9), (10), (11),
A-68
Issue 07 (2007-10-10)
A CDR Format
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 { --- See TS 22.024. -e1 e2 e3 e4 e5 e6 e7 }
::= SEQUENCE
[1] EParameter [2] EParameter [3] EParameter [4] EParameter [5] EParameter [6] EParameter [7] EParameter
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, 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.
Issue 07 (2007-10-10)
A-69
A CDR Format
BasicServiceCode ::= CHOICE { bearerService teleservice } [2] BearerServiceCode,
[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 emergencyCalls (0x11), (0x12),
allShortMessageServices shortMessageMT-PP shortMessageMO-PP
(0x20), (0x21), (0x22),
allFacsimileTransmissionServices (0x60), facsimileGroup3AndAlterSpeech automaticFacsimileGroup3 facsimileGroup4 (0x61), (0x62), (0x63),
The following non-hierarchical Compound Teleservice Groups are defined in TS GSM 02.30: allDataTeleservices (0x70),
-- covers Teleservice Groups 'allFacsimileTransmissionServices'
A-70
Issue 07 (2007-10-10)
A CDR Format
---
and 'allShortMessageServices' allTeleservices-ExeptSMS (0x80),
--covers Teleservice Groups 'allSpeechTransmissionServices' and ---------------------------allPLMN-specificTS plmn-specificTS-1 plmn-specificTS-2 plmn-specificTS-3 plmn-specificTS-4 plmn-specificTS-5 plmn-specificTS-6 plmn-specificTS-7 plmn-specificTS-8 plmn-specificTS-9 plmn-specificTS-A plmn-specificTS-B plmn-specificTS-C plmn-specificTS-D plmn-specificTS-E plmn-specificTS-F (0xd0), (0xd1), (0xd2), (0xd3), (0xd4), (0xd5), (0xd6), (0xd7), (0xd8), (0xd9), (0xda), (0xdb), (0xdc), (0xdd), (0xde), (0xdf) allVoiceGroupCallServices (0x90), voiceGroupCall voiceBroadcastCall (0x91), (0x92), 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. 'allFacsimileTransmissionServices'
BearerServiceCode ::= OCTET STRING (SIZE (1)) -- This type is used to represent the code identifying a single
Issue 07 (2007-10-10)
A-71
A CDR Format
-- bearer service, a group of bearer services, or all bearer -- services. The services are defined in TS 3GPP TS 22.002. -- The internal structure is defined as follows: --- plmn-specific bearer services: -- bits 87654321: defined by the HPLMN operator
-- rest of bearer services: -- bit 8: 0 (unused) -- bits 7654321: group (bits 7654), and rate, if applicable -- (bits 321)
---------------
allBearerServices allDataCDA-Services dataCDA-300bps dataCDA-1200bps dataCDA-1200-75bps dataCDA-2400bps dataCDA-4800bps dataCDA-9600bps general-dataCDA allDataCDS-Services dataCDS-1200bps dataCDS-2400bps dataCDS-4800bps dataCDS-9600bps
(0x00), (0x10), (0x11), (0x12), (0x13), (0x14), (0x15), (0x16), (0x17), (0x18), (0x1a), (0x1c), (0x1d), (0x1e), (0x1f), -- transparency service, such as 64K UDI H.223 and --not transparency service, such as 3.1k HZ audio
-- general-dataCDS H.245 VP
-----allPadAccessCA-Services padAccessCA-300bps padAccessCA-1200bps PadAccessCA-1200-75bps (0x20), (0x21), (0x22), (0x23),
A-72
Issue 07 (2007-10-10)
A CDR Format
-----------------------
padAccessCA-2400bps padAccessCA-4800bps padAccessCA-9600bps general-padAccessCA
(0x24), (0x25), (0x26), (0x27),
allDataPDS-Services dataPDS-2400bps dataPDS-4800bps dataPDS-9600bps general-dataPDS
(0x28), (0x2c), (0x2d), (0x2e), (0x2f),
allAlternateSpeech-DataCDA
(0x30),
allAlternateSpeech-DataCDS
(0x38),
allSpeechFollowedByDataCDA
(0x40),
allSpeechFollowedByDataCDS
(0x48),
The following non-hierarchical Compound Bearer Service Groups are defined in TS GSM 02.30: allDataCircuitAsynchronous (0x50),
-- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA" and --"allSpeechFollowedByDataCDA" allDataCircuitSynchronous (0x58),
-- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS" and --"allSpeechFollowedByDataCDS" allAsynchronousServices (0x60),
-- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA", --"allSpeechFollowedByDataCDA" and "allPadAccessCDA-Services" allSynchronousServices (0x68),
--covers "allDataCDS-Services", "allAlternateSpeech-DataCDS", -"allSpeechFollowedByDataCDS" and "allDataPDS-Services"
Issue 07 (2007-10-10)
A-73
A CDR Format
----------------------allPLMN-specificBS plmn-specificBS-1 plmn-specificBS-2 plmn-specificBS-3 plmn-specificBS-4 plmn-specificBS-5 plmn-specificBS-6 plmn-specificBS-7 plmn-specificBS-8 plmn-specificBS-9 plmn-specificBS-A plmn-specificBS-B plmn-specificBS-C plmn-specificBS-D plmn-specificBS-E plmn-specificBS-F (0xd0), (0xd1), (0xd2), (0xd3), (0xd4), (0xd5), (0xd6), (0xd7), (0xd8), (0xd9), (0xda), (0xdb), (0xdc), (0xdd), (0xde), (0xdf) Compound Bearer Service Group Codes are only used in call independent supplementary service operations, i.e. they are not used in InsertSubscriberData or in DeleteSubscriberData messages.
NOTE:UMTS Bearer servide code: general-dataCDA general-dataCDS (0x17), --not transparency service, such as 3.1k HZ audio (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 speech unrestricteDigtalInfo '00'h '01'h '02'h
A-74
Issue 07 (2007-10-10)
A CDR Format
----------
audio3k1HZ
'03'h '04'h '20'h '21'h '22'h '23'h '24'h '25'h '26'h
unrestricteDigtalInfowithtoneandannoucement telephony3k1HZ teletext telefaxGroup4Class1 videotextSyntaxBased videotelephony telefaxGroup2-3 telephony7kHZ
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 --- 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 -- MM -- DD -- hh = = Year 00 to 99 Month 01 to 12 BCD encoded BCD encoded ::= OCTET STRING (SIZE(9))
= Day 01 to 31 = hour 00 to 23 minute 00 to 59 second 00 to 59
BCD encoded BCD encoded BCD encoded BCD encoded
-- mm = -- ss -- S -- hh = =
Sign 0 = "+", "-" ASCII encoded BCD encoded BCD encoded
= hour 00 to 23 minute 00 to 59
-- mm =
Issue 07 (2007-10-10)
A-75
A CDR Format
-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 A-2 Figure 1
inc. leg outg. leg 1 outg. leg 2 outg. leg 3 t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 time t13 call duration of incoming leg = call duration of outgoing leg = holding time of outgoing leg =
Point in time
Signalling message sent/received trigger detection point encountered
Duration logging
t1 t2 t3 t4
SETUP; TDP(control) IAM ACM ANSWER start of call duration (outg. leg 1) seizure of outg. leg 1
A-76
Issue 07 (2007-10-10)
A CDR Format
Point in time
Signalling message sent/received trigger detection point encountered
Duration logging
t5 t6 t7 t8 t9 t10 t11
CONNECT RELEASE; EDP(control) IAM ACM ANSWER RELEASE; EDP(control) IAM
start of call duration (inc. leg) stop of call duration (outg. leg 1) seizure of outg. leg 2
start of call duration (outg. leg 2) stop of call duration (outg. leg 2) seizure of outg. leg 3 start of holding time (outg. leg 3)
t12 t13
ACM 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.
Issue 07 (2007-10-10)
A-77
A CDR Format
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 ---b) a) one octet for nature of address, and numbering plan indicator. 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
A-78
Issue 07 (2007-10-10)
A CDR Format
-------
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
-- 1111 reserved for extension -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
Issue 07 (2007-10-10)
A-79
A CDR Format
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 connectedNumber roamingNumber mscOutgoingROUTE seizureTime answerTime releaseTime callDuration dataVolume cAMELInitCFIndicator causeForTerm cAMELModification freeFormatData diagnostics freeFormatDataAppend freeFormatData-2 freeFormatDataAppend-2 }
[1] CAMELDestinationNumber
OPTIONAL,
[2] ConnectedNumber [3] RoamingNumber [4] ROUTE [5] TimeStamp [6] TimeStamp [7] TimeStamp [8] CallDuration [9] DataVolume [10] CAMELInitCFIndicator [11] CauseForTerm [12] ChangedParameters [13] FreeFormatData [14] Diagnostics [15] BOOLEAN [16] FreeFormatData [17] BOOLEAN
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, 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
A-80
Issue 07 (2007-10-10)
A CDR Format
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 cAMELCallForwarding } (0), (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 { gsm-SCFAddress serviceKey defaultSMSHandling freeFormatData callingPartyNumber [1] Gsm-SCFAddress [2] ServiceKey OPTIONAL, OPTIONAL, OPTIONAL, ::= SET
[3] DefaultSMS-Handling [4] FreeFormatData [5] CallingNumber
OPTIONAL, OPTIONAL,
Issue 07 (2007-10-10)
A-81
A CDR Format
destinationSubscriberNumber cAMELSMSCAddress smsReferenceNumber }
[6] CalledNumber [7] AddressString
OPTIONAL, OPTIONAL,
[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 -- englishuser -- germanuser = 01, = 02, = 03,
-- russianuser = 04, -- spanishuser = 05, -- specialuser = 06,
-- reserveuser = 09, -- commonuser = 0a, -- superioruser = 0b, -- datacalluser = 0c, -- testcalluser = 0d, -- spareuser = 0e,
-- payphoneuser = 0f, -- coinuser -- isup224 = 20, = 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;
A-82
Issue 07 (2007-10-10)
A CDR Format
unathorized client requesting a location service; position method failure at a location service execution; unknown or unreachable LCS client at a location service request. ::= INTEGER
CauseForTerm --
-- 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 partialRecord partialRecordCallReestablishment unsuccessfulCallAttempt stableCallAbnormalTermination cAMELInitCallRelease unauthorizedRequestingNetwork unauthorizedLCSClient positionMethodFailure unknownOrUnreachableLCSClient } A more detailed reason may be found in the diagnostics field. (0), (1), (2), (3), (4), (5), (52), (53), (54), (58)
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 releaseCall } (1) (0),
Issue 07 (2007-10-10)
A-83
A CDR Format
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. See Calling/called/connected/translated number
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 no-route-to-destination channel-unacceptable operator-determined-barring normal-call-clearing user-busy no-user-responding user-alerting-no-answer call-rejected number-changed pre-emption non-selected-user-clearing destination-out-of-order (0x01), (0x03), (0x06), (0x08), (0x10), (0x11), (0x12), (0x13), (0x15), (0x16), (0x19), (0x1a), (0x1b), (0x1c),
invalid-number-format-incomplete-number facility-rejected response-to-status-enquiry (0x1d), (0x1e),
A-84
Issue 07 (2007-10-10)
A CDR Format
normal-unspecified no-circuit-channel-available network-out-of-order temporary-failure switching-equipment-congestion access-information-discarded requested-circuit-channel-not-available resources-unavailable-unspecified quality-of-service-unavailable requested-facility-not-subscribed incoming-calls-barred-within-the-cug bearer-capability-not-authorized bearer-capability-not-presently-available
(0x1f), (0x22), (0x26), (0x29), (0x2a), (0x2b), (0x2c), (0x2f), (0x31), (0x32), (0x37), (0x39), (0x3a), (0x3f), (0x41), (0x44), (0x45),
service-or-option-not-available-unspecified bearer-service-not-implemented acm-equal-to-or-greater-than-acmmax requested-facility-not-implemented
only-restricted-digital-information-bearer-capability-is-available(0x46), service-or-option-not-implemented-unspecified invalid-transaction-identifier-value user-not-member-of-cug incompatible-destination invalid-transit-network-selection semantically-incorrect-message invalid-mandatory-information (0x4f),
(0x51), (0x57), (0x58), (0x5b), (0x5f), (0x60), (0x61), (0x62),
message-type-non-existent-or-not-implemented message-type-not-compatible-with-protocol-state
information-element-non-existent-or-not-implemented (0x63), conditional-ie-error (0x64), (0x65),
message-not-compatible-with-protocol-state recovery-on-timer-expiry protocol-error-unspecified interworking-unspecified (0x66), (0x6f), (0x7f)
Issue 07 (2007-10-10)
A-85
A CDR Format
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,
See Calling/called/connected/translated number
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 Service category Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Police Ambulance Fire Brigade Marine Guard Mountain Rescue ISDN-AddressString,
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 . See Calling/called/connected/translated number
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 { conferenceBridge }
::= INTEGER
(0)
A-86
Issue 07 (2007-10-10)
A CDR Format
A.6.24 Event Time Stamps

TimeStamp --- 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 -- MM -- DD -- hh = = Year 00 to 99 Month 01 to 12 BCD encoded BCD encoded ::= OCTET STRING (SIZE(9))
= Day 01 to 31 = hour 00 to 23 minute 00 to 59 second 00 to 59
BCD encoded BCD encoded BCD encoded BCD encoded
-- mm = -- ss -- S -- hh = =
Sign 0 = "+", "-" ASCII encoded BCD encoded BCD encoded
= hour 00 to 23 minute 00 to 59
-- mm =
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.
Issue 07 (2007-10-10)
A-87
A CDR Format
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: SMS_SUBMIT PDU. SMS-MT: SMS_DELIVER LCS: The receipt of an RP_DATA message from the MS containing an
The transmission of an RP_DATA message to the MS containing an PDU.
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
A-88
Issue 07 (2007-10-10)
A CDR Format
-- See Bearer Capability TS 24.008 -fnurNotApplicable fnur9600-BitsPerSecond fnur14400BitsPerSecond fnur19200BitsPerSecond fnur28800BitsPerSecond fnur38400BitsPerSecond fnur48000BitsPerSecond fnur56000BitsPerSecond fnur64000BitsPerSecond fnur33600BitsPerSecond fnur32000BitsPerSecond fnur31200BitsPerSecond } (0), (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (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
Issue 07 (2007-10-10)
A-89
A CDR Format
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 { gBR14400BitsPerSecond (1), gBR28800BitsPerSecond (2), -- BS20 non-transparent -- BS20 non-transparent and transparent, ::= ENUMERATED
-- BS30 transparent and multimedia gBR32000BitsPerSecond (3), gBR33600BitsPerSecond (4), gBR56000BitsPerSecond (5), gBR57600BitsPerSecond (6), gBR64000BitsPerSecond (7), -- BS30 multimedia -- BS30 multimedia -- BS30 transparent and multimedia -- BS20 non-transparent -- BS30 transparent and multimedia
gBR12200BitsPerSecond (106), gBR10200BitsPerSecond (107), gBR7950BitsPerSecond (108), gBR7400BitsPerSecond (109), gBR6700BitsPerSecond (110), gBR5900BitsPerSecond (111), gBR5150BitsPerSecond (112), gBR4750BitsPerSecond (113) }
-- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- 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.
A-90
Issue 07 (2007-10-10)
A CDR Format
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. ::= INTEGER
IMEICheckEvent { mobileOriginatedCall mobileTerminatedCall
(0), (1),
smsMobileOriginating (2), smsMobileTerminating (3), ssAction locationUpdate } (4), (5)
A.6.32 IMEI Status

This field contains the result of the IMEI checking procedure: Greylisted; Blacklisted; Non-whitelisted. ::= ENUMERATED
IMEIStatus {
greyListedMobileEquipment blackListedMobileEquipment
(0), (1), (2)
nonWhiteListedMobileEquipment
Issue 07 (2007-10-10)
A-91
A CDR Format
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 { rOUTENumber rOUTEName }
::=
CHOICE
[0] INTEGER, [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. ::= SEQUENCE
LCSClientIdentity {
lcsClientExternalID [0] LCSClientExternalID lcsClientDialedByMS [1] AddressString lcsClientInternalID } [2] LCSClientInternalID
OPTIONAL, OPTIONAL, OPTIONAL
LCSClientExternalID ::= SEQUENCE { externalAddress [0] AddressString OPTIONAL
A-92
Issue 07 (2007-10-10)
A CDR Format
-}
extensionContainer [1] ExtensionContainer OPTIONAL
LCSClientInternalID ::= ENUMERATED { broadcastService o-andM-HPLMN o-andM-VPLMN anonymousLocation (0), (1), (2), (3), (4)
targetMSsubscribedService }
A.6.36 LCS Client Type

This field contains the type of the LCS Client as defined in TS 29.002 . LCSClientType ::= ENUMERATED { emergencyServices valueAddedServices plmnOperatorServices lawfulInterceptServices } (0), (1), (2), (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 verticalCoordinateRequest vertical-accuracy [0] Horizontal-Accuracy [1] NULL [2] Vertical-Accuracy OPTIONAL, OPTIONAL, OPTIONAL,
Issue 07 (2007-10-10)
A-93
A CDR Format
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 { basic callDurationSupervision onlineCharging } (0), (1), (2) ::= BIT STRING
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 --- 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. -} [1] CellId
A-94
Issue 07 (2007-10-10)
A CDR Format
LocationAreaCode
CellId --
-- 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 currentOrLastKnownLocation initialLocation activateDeferredLocation cancelDeferredLocation } ---exception handling: a ProvideSubscriberLocation-Arg containing an unrecognized LocationEstimateType shall be rejected by the receiver with a return error cause of unexpected data value (0), (1), (2), (3), (4)
A.6.42 Location Type

This field contains the type of the location as defined in TS 29.002. LocationType ::= SEQUENCE { locationEstimateType [0] LocationEstimateType, [1] DeferredLocationEventType OPTIONAL
deferredLocationEventType }
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,
Issue 07 (2007-10-10)
A-95
A CDR Format
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 { mBR14400BitsPerSecond (1), mBR28800BitsPerSecond (2), -- BS20 non-transparent -- BS20 non-transparent and transparent, ::= ENUMERATED
-- BS30 transparent and multimedia mBR32000BitsPerSecond (3), mBR33600BitsPerSecond (4), mBR56000BitsPerSecond (5), mBR57600BitsPerSecond (6), mBR64000BitsPerSecond (7), -- BS30 multimedia -- BS30 multimedia -- BS30 transparent and multimedia -- BS20 non-transparent -- BS30 transparent and multimedia
mBR12200BitsPerSecond (106), mBR10200BitsPerSecond (107), mBR7950BitsPerSecond (108), mBR7400BitsPerSecond (109), mBR6700BitsPerSecond (110), mBR5900BitsPerSecond (111), mBR5150BitsPerSecond (112), mBR4750BitsPerSecond (113) }
-- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- 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
A-96
Issue 07 (2007-10-10)
A CDR Format
-- 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 --- See Mobile station classmark 2 or 3 TS 24.008 -::= OCTET STRING(size(3))
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
Issue 07 (2007-10-10)
A-97
A CDR Format
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 -- See TS 29.002 -::= OCTET STRING(SIZE(1..8))
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), (1),
notifyAndVerify-LocationAllowedIfNoResponse
notifyAndVerify-LocationNotAllowedIfNoResponse (2), locationNotAllowed } (3)
A-98
Issue 07 (2007-10-10)
A CDR Format
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 { timeLimit serviceChange locationChange classmarkChange aocParmChange radioChannelChange hSCSDParmChange changeOfCAMELDestination } (0), (1), (2), (3), (4), (5), (6), (7) ::= ENUMERATED
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))
Issue 07 (2007-10-10)
A-99
A CDR Format
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. ::= ENUMERATED
RadioChanRequested { --
-- See Bearer Capability TS 24.008 -halfRateChannel fullRateChannel dualHalfRatePreferred dualFullRatePreferred } 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. (0), (1), (2), (3)
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.
A-100
Issue 07 (2007-10-10)
A CDR Format
RateIndication --0 no rate adaption --1 V.110, I.460/X.30
::= OCTET STRING(SIZE(1))
--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 mtCallRecord roamingRecord incGatewayRecord outGatewayRecord transitRecord moSMSRecord mtSMSRecord ssActionRecord hlrIntRecord 0, 1, 2, 3, 4, 5, 6, 7, 10, 11,
commonEquipRecord 14, recTypeExtensions termCAMELRecord mtLCSRecord moLCSRecord niLCSRecord forwardCallRecord } 15, 16, 17, 18, 19, 100
Issue 07 (2007-10-10)
A-101
A CDR Format
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 . See Calling/called/connected/translated number.
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 See Calling/called/connected/translated number.
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. See Calling/called/connected/translated 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.
A-102
Issue 07 (2007-10-10)
A CDR Format
Figure A-3 Figure 2

8 digits 6 digits 1 digit
TAC
SNR IMEI 15 digits
spare
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 A-4 Figure 3
Not more than 15 digits 3 digits MCC 2 or 3 MNC NMSI IMSI MSIN
Issue 07 (2007-10-10)
A-103
A CDR Format
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 A-5 Figure 4
CC NDC SN
National (significant) mobile number Mobile station international ISDN number
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-104
Issue 07 (2007-10-10)
A CDR Format
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 ). See Calling/called/connected/translated number.
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 -------see GSM 08.08 000 0001 001 0001 010 0001 000 0101 001 0101 010 0101 GSM speech full rate version 1 GSM speech full rate version 2 GSM speech full rate version 3 GSM speech half rate version 1 GSM speech half rate version 2 GSM speech half rate version 3 for future use for future use used for enhanced full rate for future use ::= OCTET STRING (SIZE(1))
Issue 07 (2007-10-10)
A-105
A CDR Format
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 iuUTRAN gERAN } (0), (1), (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)) -- This type is used to represent the code identifying a single -- 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), reserved for possible future use all line identification SS
A-106
Issue 07 (2007-10-10)
A CDR Format
--
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 -------allNameIdentificationSS (0x18), all name identification SS calling-name-presentation (0x19), malicious-call-identification reserved for possible future use malicious call identification (0x15),
-- calling name presentation -------allForwardingSS all forwarding SS call-forwarding-unconditional (0x21), (0x20), SS-Codes '00011010'B, to '00011111'B, are reserved for future NameIdentification Supplementary Service use.
--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),
Issue 07 (2007-10-10)
A-107
A CDR Format
--call forwarding on mobile subscriber not reachable ----------------call-waiting (0x41), allCallCompletionSS (0x40), explicit-call-transfer explicit call transfer mobile-access-hunting reserved for possible future use mobile access hunting (0x32), (0x31), allCallOfferingSS (0x30),
reserved for possible future use all call offering SS includes also all forwarding SS
reserved for possible future use all Call completion SS
-- 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 ---------allMultiPartySS (0x50), multicall multicall (0x45), this SS-Code is used only in InsertSubscriberData and DeleteSubscriberData
reserved for possible future use all multiparty SS
A-108
Issue 07 (2007-10-10)
A CDR Format
--------
multiPTY multiparty
(0x51),
allCommunityOfInterest-SS
(0x60),
reserved for possible future use all community of interest SS closed-user-group (0x61),
--closed user group -------------------------allBarringSS all barring SS barringOfOutgoingCalls (0x91), barring of outgoing calls barring-of-all-outgoing-calls barring of all outgoing calls (0x92), (0x90), allAdditionalInfoTransferSS (0x80), allChargingSS (0x70),
reserved for possible future use all charging SS advice-of-charge-information advice of charge information advice-of-charge-charging advice of charge charging (0x72), (0x71),
reserved for possible future use all additional information transfer SS uUS1-user-to-user-signalling UUS1 user-to-user signalling uUS2-user-to-user-signalling UUS2 user-to-user signalling uUS3-user-to-user-signalling UUS3 user-to-user signalling (0x83), (0x82), (0x81),
Issue 07 (2007-10-10)
A-109
A CDR Format
------------
barring-of-outgoing-international-calls barring of outgoing international calls boicExHC (0x94),
(0x93),
barring of outgoing international calls except those directed to the home PLMN barringOfIncomingCalls (0x99), barring of incoming calls barring-of-all-incoming-calls barring of all incoming calls barring-of-incoming-calls-when-roaming-outside-home-PLMN-Country barring of incoming calls when roaming outside home PLMN (0x9b), (0x9a),
-- country ---------------------allMOLR-SS (0xc0), allLCSPrivacyException (0xb0), all LCS Privacy Exception Classes universal (0xb1), allCallPrioritySS (0xa0),
reserved for possible future use all call priority SS enhanced-Multilevel-Precedence-Pre-emption-EMLPP-service enhanced Multilevel Precedence Pre-emption 'EMLPP) service (0xa1),
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
all Mobile Originating Location Request Classes
A-110
Issue 07 (2007-10-10)
A CDR Format
-------------------------
basicSelfLocation
(0xc1),
allow an MS to request its own location autonomousSelfLocation (0xc2),
allow an MS to perform self location without interaction with the PLMN for a predetermined period of time transferToThirdParty (0xc3),
allow an MS to request transfer of its location to another LCS client
allPLMN-specificSS plmn-specificSS-1 plmn-specificSS-2 plmn-specificSS-3 plmn-specificSS-4 plmn-specificSS-5 plmn-specificSS-6 plmn-specificSS-7 plmn-specificSS-8 plmn-specificSS-9 plmn-specificSS-A plmn-specificSS-B plmn-specificSS-C plmn-specificSS-D plmn-specificSS-E USSD
(0xf0), (0xf1), (0xf2), (0xf3), (0xf4), (0xf5), (0xf6), (0xf7), (0xf8), (0xf9), (0xfa), (0xfb), (0xfc), (0xfd), (0xfe), (0xff)
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 { registration erasure activation deactivation (0), (1), (2), (3), ::= ENUMERATED
Issue 07 (2007-10-10)
A-111
A CDR Format
interrogation invocation
(4), (5),
passwordRegistration (6), USSDInvocation } -- USSDInvocation (7) include USSD phase 1,phase 2 (7)
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 { transparent nonTransparent } (0), (1) ::= ENUMERATED
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))
A-112
Issue 07 (2007-10-10)
A CDR Format
--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 --20 --21 --22 Reserved for future EMS features
RFC 822 E-Mail Header Hyperlink format element Reply Address Element Reserved for future use
--23 - 6F
--70 - 7F (U)SIM Toolkit Security Headers
Issue 07 (2007-10-10)
A-113
A CDR Format
--80 - 9F --A0 - BF --C0 - DF --E0 - FE --FF
SME to SME specific use Reserved for future use SC specific use Reserved for future use 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 A-6 Figure 5
Compression Header Compressed Data (CD) Compression Footer
Segmentation / De-segmentation TP-UDH CH First segment CD TP-UDH CD TP-UDH CD Final segment CF
Intermediate segments
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.
A-114
Issue 07 (2007-10-10)
A CDR Format
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
Issue 07 (2007-10-10)
A-115
A CDR Format
Concatenated SMS Reference Number Picture1 Picture2 X(may be 1) Y(may be 1)
Maximum Number Of SMS In The Concatenated SMS 2 4
Sequence Number Of The Current SMS First segment 1 1 2 3 Second Segment Last segment 2 4
A.6.87 Maximum Number of SMS in the Concatenated SMS

MaximumNumberOfSMSInTheConcatenatedSMS See Concatenated SMS Reference Number. ::= INTEGER(0..255)
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 ::= { notCUGCall (0), cUGCall } (1) ENUMERATED
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
A-116
Issue 07 (2007-10-10)
A CDR Format
{ callInTheSameCUGGroup callNotInTheSameCUGGroup } (0), (1)
A.6.93 Modem Type

ModemType { none-modem modem-v21 modem-v22 modem-v22-bis modem-v23 modem-v26-ter modem-v32 modem-undef-interface modem-autobauding1 no-other-modem-type (31), modem-v34 } (33) (0), (1), (2), (3), (4), (5), (6), (7), (8), ::= ENUMERATED
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 { callingParty calledParty } (0), (1) ::= ENUMERATED
A.6.96 Original Called Number

The address of original called party.
Issue 07 (2007-10-10)
A-117
A CDR Format
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 --call priority level 4 --call priority level 3 --call priority level 2 --call priority level 1 --call priority level 0 --call priority level B --call priority level A See 24.008 0 1 2 3 4 5 6 7
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 --priorityLevelB --priorityLevel0 --priorityLevel1 --priorityLevel2 --priorityLevel3 --priorityLevel4
EMLPP-Priority ::= 6 EMLPP-Priority ::= 5 EMLPP-Priority ::= 0 EMLPP-Priority ::= 1 EMLPP-Priority ::= 2 EMLPP-Priority ::= 3 EMLPP-Priority ::= 4
A-118
Issue 07 (2007-10-10)
A CDR Format
See 29.002
A.6.101 Ea Subscriber Info

Indicates the calling subscribers 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 { numberNotPorted numberPorted } (0), (1) ::= ENUMERATED
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 { location changeTime } [0] GAI, [1] TimeStamp ::= SEQUENCE
Issue 07 (2007-10-10)
A-119
A CDR Format
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 ISDN-BC ::= OCTET STRING
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-120
Issue 07 (2007-10-10)
A CDR Format
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 { cas (0), tup (1), isup (2), pra (3), bicc (4), sip (5), others (0xFF) } ::= ENUMERATED
A.6.117 mscOutgoingRouteAttribute
Indicates the incoming trunk attribute as follows: RouteAttribute { cas (0), tup (1), isup (2), pra (3), bicc (4), sip (5), others (0xFF) } ::= ENUMERATED
A.6.118 Voice Indicator

Indicates the voice indicator attribute as follows: VoiceIndicator { sendToneByLocalMsc(0) , ::= ENUMERATED
Issue 07 (2007-10-10)
A-121
A CDR Format
sendToneByOtherMsc(1), voiceNoIndication (3) }
A.6.119 Call Type

Indicates the call type as follows: CallType { unknown (0), internal incoming outgoing tandem } (1), (2), (3), (4) ::= ENUMERATED
A.6.120 B_CATEGORY
Indicates the called side information as follows: BCategory { subscriberFree (0) , subscriberBusy (1), subscriberNoIndication (3) } ::= ENUMERATED
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 -------------------------------------------------------------------------------::=
A-122
Issue 07 (2007-10-10)

--- CALL AND EVENT RECORDS --
A CDR Format
-------------------------------------------------------------------------------Font: verdana 8 CallEventRecord { moCallRecord mtCallRecord roamingRecord incGatewayRecord outGatewayRecord transitRecord moSMSRecord mtSMSRecord ssActionRecord hlrIntRecord commonEquipRecord recTypeExtensions termCAMELRecord mtLCSRecord moLCSRecord niLCSRecord forwardCallRecord } MOCallRecord { recordType OPTIONAL, servedIMSI OPTIONAL, servedIMEI OPTIONAL, servedMSISDN OPTIONAL, callingNumber OPTIONAL, calledNumber OPTIONAL, translatedNumber OPTIONAL, connectedNumber OPTIONAL, roamingNumber OPTIONAL, recordingEntity OPTIONAL, mscIncomingROUTE OPTIONAL, mscOutgoingROUTE OPTIONAL, location changeOfLocation [12] LocationAreaAndCell OPTIONAL, OPTIONAL, [13] SEQUENCE OF LocationChange [11] ROUTE [10] ROUTE [9] RecordingEntity [8] RoamingNumber [7] ConnectedNumber [6] TranslatedNumber [5] CalledNumber [4] CallingNumber [3] MSISDN [2] IMEI [1] IMSI [0] CallEventRecordType ::= SET [0] MOCallRecord, [1] MTCallRecord, [2] RoamingRecord, [3] IncGatewayRecord, [4] OutGatewayRecord, [5] TransitCallRecord, [6] MOSMSRecord, [7] MTSMSRecord, [10] SSActionRecord, [11] HLRIntRecord, [14] CommonEquipRecord, [15] ManagementExtensions, [16] TermCAMELRecord, [17] MTLCSRecord, [18] MOLCSRecord, [19] NILCSRecord, [100] MOCallRecord ::= CHOICE
Issue 07 (2007-10-10)
A-123
A CDR Format
basicService OPTIONAL, transparencyIndicator OPTIONAL, changeOfService supplServicesUsed aocParameters OPTIONAL, changeOfAOCParms msClassmark OPTIONAL, changeOfClassmark OPTIONAL, seizureTime OPTIONAL, answerTime OPTIONAL, releaseTime OPTIONAL, callDuration radioChanRequested OPTIONAL, radioChanUsed OPTIONAL, changeOfRadioChan OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, callReference OPTIONAL, sequenceNumber OPTIONAL, additionalChgInfo recordExtensions gsm-SCFAddress OPTIONAL, serviceKey OPTIONAL, networkCallReference mSCAddress OPTIONAL, cAMELInitCFIndicator defaultCallHandling fnur OPTIONAL, aiurRequested OPTIONAL, speechVersionSupported speechVersionUsed numberOfDPEncountered OPTIONAL, levelOfCAMELService [52] LevelOfCAMELService [49] SpeechVersionIdentifier [46] AiurRequested [40] CAMELInitCFIndicator [41] DefaultCallHandling [45] Fnur [38] NetworkCallReference [39] MSCAddress [37] ServiceKey [34] AdditionalChgInfo [33] SequenceNumber [32] CallReference [31] Diagnostics [30] CauseForTerm [29] ChangeOfRadioChannel [28] TrafficChannel [25] CallDuration [27] RadioChanRequested [24] TimeStamp [23] TimeStamp [22] TimeStamp [21] ChangeOfClassmark [15] TransparencyInd [14] BasicServiceCode
[16] SEQUENCE OF ChangeOfService [17] SEQUENCE OF SuppServiceUsed [18] AOCParameters [19] SEQUENCE OF AOCParmChange [20] Classmark
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL, OPTIONAL,
[35] ManagementExtensions [36] Gsm-SCFAddress
OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
[50] SpeechVersionIdentifier [51] INTEGER
OPTIONAL,
A-124
Issue 07 (2007-10-10)

freeFormatData OPTIONAL, cAMELCallLegInformation freeFormatDataAppend OPTIONAL, defaultCallHandling-2 gsm-SCFAddress-2 OPTIONAL, serviceKey-2 OPTIONAL, freeFormatData-2 OPTIONAL, freeFormatDataAppend-2 OPTIONAL, systemType OPTIONAL, rateIndication OPTIONAL, partialRecordType OPTIONAL, guaranteedBitRate OPTIONAL, maximumBitRate OPTIONAL, modemType OPTIONAL, classmark3 OPTIONAL, chargedParty OPTIONAL, originalCalledNumber OPTIONAL, callingChargeAreaCode OPTIONAL, calledChargeAreaCode OPTIONAL, mscOutgoingCircuit OPTIONAL, orgRNCorBSCId OPTIONAL, orgMSCId OPTIONAL, callEmlppPriority OPTIONAL, callerDefaultEmlppPriority eaSubscriberInfo OPTIONAL, selectedCIC OPTIONAL, optimalRoutingFlag OPTIONAL, optimalRoutingLateForwardFlag OPTIONAL, optimalRoutingEarlyForwardFlag OPTIONAL, [179] NULL [178] NULL [177] NULL [175] SelectedCIC 171] SubscriberEmlppPriority [174] EASubscriberInfo [170] SubscriberEmlppPriority [168] MSCId [167] RNCorBSCId [166] MSCCIC [146] ChargeAreaCode [145] ChargeAreaCode [142] OriginalCalledNumber [141] ChargedParty [140] Classmark3 [139] ModemType [71] MaximumBitRate [70] GuaranteedBitRate [69] PartialRecordType [62] RateIndication [61] SystemType [60] BOOLEAN [59] FreeFormatData [58] ServiceKey [56] DefaultCallHandling [57] Gsm-SCFAddress [54] SEQUENCE OF CAMELInformation [55] BOOLEAN [53] FreeFormatData
A CDR Format
OPTIONAL,
OPTIONAL,
OPTIONAL,
Issue 07 (2007-10-10)
A-125
A CDR Format
portedflag OPTIONAL, calledIMSI globalAreaID OPTIONAL, changeOfglobalAreaID subscriberCategory OPTIONAL, firstmccmnc OPTIONAL, intermediatemccmnc OPTIONAL, lastmccmnc OPTIONAL, cUGOutgoingAccessIndicator cUGInterlockCode OPTIONAL, cUGOutgoingAccessUsed cUGIndex OPTIONAL, interactionWithIP OPTIONAL, hotBillingTag OPTIONAL, setupTime OPTIONAL, alertingTime OPTIONAL, voiceIndicator OPTIONAL, bCategory OPTIONAL, callType OPTIONAL } [205] CallType [204] BCategory [203] VoiceIndicator [202] TimeStamp [201] TimeStamp [200] HotBillingTag [199] InteractionWithIP [197] CUGOutgoingAccessUsed [198] CUGIndex [195] CUGOutgoingAccessIndicator [196] CUGInterlockCode [194] MCCMNC [193] MCCMNC [192] MCCMNC [181] IMSI [188] GAI [180] PortedFlag
OPTIONAL,
[189] SEQUENCE OF ChangeOfglobalAreaID OPTIONAL, [190] SubscriberCategory
OPTIONAL,
OPTIONAL,
--at moc callingNumber is the same as served msisdn except basic msisdn != calling number such as MSP service MTCallRecord { recordType OPTIONAL, servedIMSI OPTIONAL, servedIMEI OPTIONAL, servedMSISDN OPTIONAL, callingNumber OPTIONAL, connectedNumber OPTIONAL, recordingEntity OPTIONAL, [6] RecordingEntity [5] ConnectedNumber [4] CallingNumber [3] CalledNumber [2] IMEI [1] IMSI [0] CallEventRecordType ::= SET
A-126
Issue 07 (2007-10-10)

mscIncomingROUTE OPTIONAL, mscOutgoingROUTE OPTIONAL, location OPTIONAL, changeOfLocation OPTIONAL, basicService OPTIONAL, transparencyIndicator OPTIONAL, changeOfService supplServicesUsed aocParameters OPTIONAL, changeOfAOCParms msClassmark OPTIONAL, changeOfClassmark OPTIONAL, seizureTime OPTIONAL, answerTime OPTIONAL, releaseTime OPTIONAL, callDuration OPTIONAL, radioChanRequested OPTIONAL, radioChanUsed OPTIONAL, changeOfRadioChan OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, callReference OPTIONAL, sequenceNumber OPTIONAL, additionalChgInfo OPTIONAL, recordExtensions OPTIONAL, networkCallReference OPTIONAL, mSCAddress OPTIONAL, fnur OPTIONAL, aiurRequested OPTIONAL, [39] AiurRequested [38] Fnur [34] MSCAddress [33] NetworkCallReference [32] ManagementExtensions [31] AdditionalChgInfo [30] SequenceNumber [29] CallReference [28] Diagnostics [27] CauseForTerm [26] ChangeOfRadioChannel [25] TrafficChannel [24] RadioChanRequested [22] CallDuration [21] TimeStamp [20] TimeStamp [19] TimeStamp [18] ChangeOfClassmark [16] SEQUENCE OF AOCParmChange [17] Classmark [13] SEQUENCE OF ChangeOfService [14] SEQUENCE OF SuppServiceUsed [15] AOCParameters [12] TransparencyInd [11] BasicServiceCode [10] SEQUENCE OF LocationChange [9] LocationAreaAndCell [8] ROUTE [7] ROUTE
A CDR Format
OPTIONAL, OPTIONAL,
OPTIONAL,
Issue 07 (2007-10-10)
A-127
A CDR Format
speechVersionSupported speechVersionUsed OPTIONAL, gsm-SCFAddress OPTIONAL, serviceKey OPTIONAL, systemType OPTIONAL, rateIndication OPTIONAL, partialRecordType OPTIONAL, guaranteedBitRate OPTIONAL, maximumBitRate OPTIONAL, initialCallAttemptFlag OPTIONAL, ussdCallBackFlag OPTIONAL, modemType OPTIONAL, classmark3 OPTIONAL, chargedParty OPTIONAL, originalCalledNumber callingChargeAreaCode OPTIONAL, calledChargeAreaCode OPTIONAL, defaultCallHandling OPTIONAL, freeFormatData OPTIONAL, freeFormatDataAppend OPTIONAL, numberOfDPEncountered OPTIONAL, levelOfCAMELService OPTIONAL, roamingNumber OPTIONAL, mscIncomingCircuit OPTIONAL, orgRNCorBSCId OPTIONAL, orgMSCId OPTIONAL, callEmlppPriority OPTIONAL, calledDefaultEmlppPriority OPTIONAL, [171] EmlppPriority [170] EmlppPriority [168] MSCId [167] RNCorBSCId [166] MSCCIC [160] RoamingNumber [154] LevelOfCAMELService [153] INTEGER [152] BOOLEAN [151] FreeFormatData [150] DefaultCallHandling [146]ChargeAreaCode [142] OriginalCalledNumber [145]ChargeAreaCode [141] ChargedParty [140] Classmark3 [139] ModemType [138] NULL [137] NULL [56] MaximumBitRate [55] GuaranteedBitRate [54] PartialRecordType [47] RateIndication [46] SystemType [45] ServiceKey [44] Gsm-SCFAddress [42] SpeechVersionIdentifier [43] SpeechVersionIdentifier

OPTIONAL,
OPTIONAL,
A-128
Issue 07 (2007-10-10)

eaSubscriberInfo OPTIONAL, selectedCIC OPTIONAL, optimalRoutingFlag OPTIONAL, portedflag OPTIONAL, globalAreaID OPTIONAL, changeOfglobalAreaID subscriberCategory OPTIONAL, firstmccmnc OPTIONAL, intermediatemccmnc OPTIONAL, lastmccmnc OPTIONAL, cUGOutgoingAccessIndicator cUGInterlockCode OPTIONAL, cUGIncomingAccessUsed cUGIndex OPTIONAL, hotBillingTag OPTIONAL, redirectingnumber redirectingcounter setupTime OPTIONAL, alertingTime OPTIONAL, calledNumber OPTIONAL, voiceIndicator OPTIONAL, bCategory OPTIONAL, callType OPTIONAL } RoamingRecord { recordType OPTIONAL, servedIMSI OPTIONAL, servedMSISDN OPTIONAL, callingNumber OPTIONAL, roamingNumber OPTIONAL, [4] RoamingNumber [3] CallingNumber [2] MSISDN [1] IMSI [0] CallEventRecordType ::= SET [208] CallType [207] BCategory [206] VoiceIndicator [205] CalledNumber [204] TimeStamp [201] RedirectingNumber [202] RedirectingCounter [203] TimeStamp [200] HotBillingTag [197] CUGIncomingAccessUsed [198] CUGIndex [195] CUGOutgoingAccessIndicator [196] CUGInterlockCode [194] MCCMNC [193] MCCMNC [192] MCCMNC [188] GAI [180] PortedFlag [177] NULL [175] SelectedCIC [174] EASubscriberInfo
A CDR Format
[189] SEQUENCE OF ChangeOfglobalAreaID OPTIONAL, [190] SubscriberCategory
OPTIONAL,
OPTIONAL,
OPTIONAL, OPTIONAL,
Issue 07 (2007-10-10)
A-129
A CDR Format
recordingEntity OPTIONAL, mscIncomingROUTE OPTIONAL, mscOutgoingROUTE OPTIONAL, basicService OPTIONAL, transparencyIndicator changeOfService supplServicesUsed seizureTime OPTIONAL, answerTime OPTIONAL, releaseTime OPTIONAL, callDuration OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, callReference OPTIONAL, sequenceNumber OPTIONAL, recordExtensions networkCallReference mSCAddress OPTIONAL, partialRecordType additionalChgInfo chargedParty OPTIONAL, originalCalledNumber callingChargeAreaCode OPTIONAL, calledChargeAreaCode mscOutgoingCircuit OPTIONAL, mscIncomingCircuit OPTIONAL, orgMSCId OPTIONAL, callEmlppPriority eaSubscriberInfo selectedCIC OPTIONAL, optimalRoutingFlag OPTIONAL, subscriberCategory cUGInterlockCode OPTIONAL, [190] SubscriberCategory [196] CUGInterlockCode [177] NULL [170] EmlppPriority [174] EASubscriberInfo [175] SelectedCIC [168] MSCId [167] MSCCIC [146] ChargeAreaCode [166] MSCCIC [142] OriginalCalledNumber [145] ChargeAreaCode [30] PartialRecordType [133] AdditionalChgInfo [141] ChargedParty [20] SequenceNumber [19] CallReference [18] Diagnostics [17] CauseForTerm [15] CallDuration [14] TimeStamp [13] TimeStamp [9] TransparencyInd [8] BasicServiceCode [7] ROUTE [6] ROUTE [5] RecordingEntity
OPTIONAL, OPTIONAL, OPTIONAL,
[10] SEQUENCE OF ChangeOfService [11] SEQUENCE OF SuppServiceUsed [12] TimeStamp
[21] ManagementExtensions [22] NetworkCallReference [23] MSCAddress
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL,
cUGOutgoingAccessIndicator [195] CUGOutgoingAccessIndicator OPTIONAL,
A-130
Issue 07 (2007-10-10)

hotBillingTag OPTIONAL } TermCAMELRecord { recordtype servedIMSI OPTIONAL, servedMSISDN OPTIONAL, recordingEntity interrogationTime OPTIONAL, destinationRoutingAddress gsm-SCFAddress OPTIONAL, serviceKey OPTIONAL, networkCallReference mSCAddress OPTIONAL, defaultCallHandling recordExtensions calledNumber OPTIONAL, callingNumber OPTIONAL, mscIncomingROUTE OPTIONAL, mscOutgoingROUTE OPTIONAL, seizureTime OPTIONAL, answerTime OPTIONAL, releaseTime OPTIONAL, callDuration OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, callReference OPTIONAL, sequenceNumber OPTIONAL, numberOfDPEncountered OPTIONAL, levelOfCAMELService freeFormatData OPTIONAL, cAMELCallLegInformation [26] LevelOfCAMELService [27] FreeFormatData [25] INTEGER [24] SequenceNumber [23] CallReference [22] Diagnostics [21] CauseForTerm [19] CallDuration [18] TimeStamp [17] TimeStamp [16] TimeStamp [15] ROUTE [14] ROUTE [13] CallingNumber [10] DefaultCallHandling [11] ManagementExtensions [12] CalledNumber [8] NetworkCallReference [9] MSCAddress [7] ServiceKey [5] DestinationRoutingAddress [6] Gsm-SCFAddress [3] RecordingEntity [4] TimeStamp [2] MSISDN [0] CallEventRecordType [1] IMSI ::= SET [200] HotBillingTag
A CDR Format
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL,
[28] SEQUENCE OF CAMELInformation OPTIONAL,
Issue 07 (2007-10-10)
A-131
A CDR Format
freeFormatDataAppend OPTIONAL, mscServerIndication OPTIONAL, defaultCallHandling-2 gsm-SCFAddress-2 OPTIONAL, serviceKey-2 OPTIONAL, freeFormatData-2 OPTIONAL, freeFormatDataAppend-2 OPTIONAL, partialRecordType basicService additionalChgInfo chargedParty OPTIONAL, originalCalledNumber orgMSCId OPTIONAL, subscriberCategory hotBillingTag OPTIONAL } IncGatewayRecord { recordType OPTIONAL, callingNumber OPTIONAL, calledNumber OPTIONAL, recordingEntity mscIncomingROUTE OPTIONAL, mscOutgoingROUTE OPTIONAL, seizureTime OPTIONAL, answerTime OPTIONAL, releaseTime OPTIONAL, callDuration OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, callReference OPTIONAL, sequenceNumber recordExtensions [14] SequenceNumber [15] ManagementExtensions [13] CallReference [12] Diagnostics [11] CauseForTerm [9] CallDuration [8] TimeStamp [7] TimeStamp [6] TimeStamp [5] ROUTE [3] RecordingEntity [4] ROUTE [2] CalledNumber [1] CallingNumber [0] CallEventRecordType ::= SET [190] SubscriberCategory [200] HotBillingTag [142] OriginalCalledNumber [168] MSCId [42] PartialRecordType [130] BasicServiceCode [133] AdditionalChgInfo [141] ChargedParty [35] BOOLEAN [34] FreeFormatData [33] ServiceKey [31] DefaultCallHandling [32] Gsm-SCFAddress [30] BOOLEAN [29] BOOLEAN
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL, OPTIONAL,
A-132
Issue 07 (2007-10-10)

partialRecordType iSDN-BC OPTIONAL, lLC OPTIONAL, hLC OPTIONAL, basicService additionalChgInfo chargedParty OPTIONAL, originalCalledNumber rateIndication roamingNumber OPTIONAL, mscIncomingCircuit OPTIONAL, orgMSCId OPTIONAL, callEmlppPriority eaSubscriberInfo selectedCIC OPTIONAL, cUGOutgoingAccessIndicator [195] CUGOutgoingAccessIndicator OPTIONAL, cUGInterlockCode cUGIncomingAccessUsed [196] CUGInterlockCode [197] CUGIncomingAccessUsed [170] EmlppPriority [174] EASubscriberInfo [175] SelectedCIC [168] MSCId [167] MSCCIC [142] OriginalCalledNumber [159] RateIndication [160] RoamingNumber [130] BasicServiceCode [133] AdditionalChgInfo [141] ChargedParty [25] HLC [24] LLC [22] PartialRecordType [23] ISDN-BC
A CDR Format
OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
mscIncomingRouteAttribute [198] RouteAttribute mscOutgoingRouteAttribute [199] RouteAttribute networkCallReference setupTime OPTIONAL, alertingTime OPTIONAL, voiceIndicator bCategory OPTIONAL, callType OPTIONAL } OutGatewayRecord { recordType OPTIONAL, callingNumber OPTIONAL, calledNumber OPTIONAL, recordingEntity mscIncomingROUTE OPTIONAL, mscOutgoingROUTE OPTIONAL, seizureTime OPTIONAL, [6] TimeStamp [5] ROUTE [3] RecordingEntity [4] ROUTE [2] CalledNumber [1] CallingNumber [0] CallEventRecordType ::= SET [205] CallType [203] VoiceIndicator [204] BCategory [202] TimeStamp [200] NetworkCallReference [201] TimeStamp
OPTIONAL,
OPTIONAL,
Issue 07 (2007-10-10)
A-133
A CDR Format
answerTime OPTIONAL, releaseTime OPTIONAL, callDuration OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, callReference OPTIONAL, sequenceNumber recordExtensions partialRecordType basicService additionalChgInfo chargedParty OPTIONAL, originalCalledNumber rateIndication OPTIONAL, roamingNumber OPTIONAL, mscOutgoingCircuit OPTIONAL, orgMSCId OPTIONAL, eaSubscriberInfo selectedCIC OPTIONAL, callEmlppPriority cUGInterlockCode OPTIONAL, cUGIncomingAccessUsed mscIncomingRouteAttribute mscOutgoingRouteAttribute networkCallReference setupTime OPTIONAL, alertingTime OPTIONAL, voiceIndicator OPTIONAL, bCategory OPTIONAL, callType OPTIONAL } TransitCallRecord { recordType OPTIONAL, [0] CallEventRecordType ::= SET [205] CallType [204] BCategory [203] VoiceIndicator [202] TimeStamp [197] CUGIncomingAccessUsed [198] RouteAttribute [199] RouteAttribute [200] NetworkCallReference [201] TimeStamp [170] EmlppPriority [196] CUGInterlockCode [174] EASubscriberInfo [175] SelectedCIC [168] MSCId [166] MSCCIC [160] RoamingNumber [142] OriginalCalledNumber [159] RateIndication [14] SequenceNumber [15] ManagementExtensions [22] PartialRecordType [130] BasicServiceCode [133] AdditionalChgInfo [141] ChargedParty [13] CallReference [12] Diagnostics [11] CauseForTerm [9] CallDuration [8] TimeStamp [7] TimeStamp
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
cUGOutgoingAccessIndicator [195] CUGOutgoingAccessIndicator OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
A-134
Issue 07 (2007-10-10)

recordingEntity OPTIONAL, mscIncomingROUTE OPTIONAL, mscOutgoingROUTE OPTIONAL, callingNumber OPTIONAL, calledNumber OPTIONAL, isdnBasicService OPTIONAL, seizureTime OPTIONAL, answerTime OPTIONAL, releaseTime OPTIONAL, callDuration OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, callReferen OPTIONAL, sequenceNumber OPTIONAL, recordExtensions OPTIONAL, partialRecordType OPTIONAL, basicService OPTIONAL, additionalChgInfo OPTIONAL, originalCalledNumber OPTIONAL, rateIndication OPTIONAL, mscOutgoingCircuit OPTIONAL, mscIncomingCircuit OPTIONAL, orgMSCId OPTIONAL, callEmlppPriority eaSubscriberInfo selectedCIC OPTIONAL, cUGOutgoingAccessIndicator [195] CUGOutgoingAccessIndicator OPTIONAL, cUGInterlockCode OPTIONAL, cUGIncomingAccessUsed [197] CUGIncomingAccessUsed [196] CUGInterlockCode [170] EmlppPriority [174] EASubscriberInfo [175] SelectedCIC [168] MSCId [167] MSCCIC [166] MSCCIC [159] RateIndication [142] OriginalCalledNumber [133] AdditionalChgInfo [130] BasicServiceCode [23] PartialRecordType [16] ManagementExtensions [15] SequenceNumber [14] CallReference [13] Diagnostics [12] CauseForTerm [10] CallDuration [9] TimeStamp [8] TimeStamp [7] TimeStamp [6] BasicService [5] CalledNumber [4] CallingNumber [3] ROUTE [2] ROUTE [1] RecordingEntity
A CDR Format
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
mscIncomingRouteAttribute [198] RouteAttribute
Issue 07 (2007-10-10)
A-135
A CDR Format
mscOutgoingRouteAttribute [199] RouteAttribute OPTIONAL, networkCallReference setupTime OPTIONAL, alertingTime OPTIONAL, voiceIndicator OPTIONAL, bCategory OPTIONAL, callType OPTIONAL } MOSMSRecord { recordType OPTIONAL, servedIMSI OPTIONAL, servedIMEI OPTIONAL, servedMSISDN OPTIONAL, msClassmark OPTIONAL, serviceCentre OPTIONAL, recordingEntity location OPTIONAL, messageReference OPTIONAL, originationTime OPTIONAL, smsResult OPTIONAL, recordExtensions destinationNumber cAMELSMSInformation systemType OPTIONAL, basicService OPTIONAL, additionalChgInfo classmark3 OPTIONAL, chargedParty OPTIONAL, orgRNCorBSCId OPTIONAL, orgMSCId OPTIONAL, [168] MSCId [167] RNCorBSCId [141] ChargedParty [133] AdditionalChgInfo [140] Classmark3 [130] BasicServiceCode [11] ManagementExtensions [12] SmsTpDestinationNumber [13] CAMELSMSInformation [14] SystemType [10] SMSResult [9] TimeStamp [8] MessageReference [6] RecordingEntity [5] AddressString [4] Classmark [3] MSISDN [2] IMEI [1] IMSI [0] CallEventRecordType ::= SET [205] CallType [204] BCategory [203] VoiceIndicator [202] TimeStamp [200] NetworkCallReference [201] TimeStamp
OPTIONAL,
OPTIONAL,
[7] LocationAreaAndCell
OPTIONAL,
A-136
Issue 07 (2007-10-10)

globalAreaID OPTIONAL, subscriberCategory firstmccmnc OPTIONAL, smsUserDataType smstext OPTIONAL, [195] SmsUserDataType [196] SMSTEXT [190] SubscriberCategory [192] MCCMNC [188] GAI
A CDR Format
OPTIONAL,
OPTIONAL,
maximumNumberOfSMSInTheConcatenatedSMS [197] MaximumNumberOfSMSInTheConcatenatedSMS OPTIONAL, concatenatedSMSReferenceNumber [198] ConcatenatedSMSReferenceNumber OPTIONAL, sequenceNumberOfTheCurrentSMS [199] SequenceNumberOfTheCurrentSMS OPTIONAL, hotBillingTag callReference OPTIONAL } MTSMSRecord { recordType OPTIONAL, serviceCentre OPTIONAL, servedIMSI OPTIONAL, servedIMEI OPTIONAL, servedMSISDN OPTIONAL, msClassmark OPTIONAL, recordingEntity OPTIONAL, location OPTIONAL, deliveryTime OPTIONAL, smsResult OPTIONAL, recordExtensions OPTIONAL, systemType OPTIONAL, cAMELSMSInformation basicService OPTIONAL, additionalChgInfo classmark3 chargedParty OPTIONAL, orgRNCorBSCId OPTIONAL, orgMSCId OPTIONAL, [168] MSCId [167] RNCorBSCId [133] AdditionalChgInfo [140]Classmark3 [141] ChargedParty OPTIONAL, OPTIONAL, [12] CAMELSMSInformation [130] BasicServiceCode OPTIONAL, [11] SystemType [10] ManagementExtensions [9] SMSResult [8] TimeStamp [7] LocationAreaAndCell [6] RecordingEntity [5] Classmark [4] MSISDN [3] IMEI [2] IMSI [1] AddressString [0] CallEventRecordType ::= SET [200] HotBillingTag [201] CallReference OPTIONAL,
Issue 07 (2007-10-10)
A-137
A CDR Format
globalAreaID OPTIONAL, subscriberCategory firstmccmnc OPTIONAL, smsUserDataType OPTIONAL, smstext OPTIONAL, [196] SMSTEXT [195] SmsUserDataType [190] SubscriberCategory [192] MCCMNC [188] GAI
OPTIONAL,
maximumNumberOfSMSInTheConcatenatedSMS [197] MaximumNumberOfSMSInTheConcatenatedSMS OPTIONAL, concatenatedSMSReferenceNumber hotBillingTag origination callReference OPTIONAL } HLRIntRecord { recordType servedIMSI OPTIONAL, servedMSISDN recordingEntity OPTIONAL, basicService OPTIONAL, routingNumber interrogationTime OPTIONAL, numberOfForwarding interrogationResult OPTIONAL, recordExtensions orgMSCId OPTIONAL, callReference OPTIONAL } SSActionRecord { recordType OPTIONAL, servedIMSI OPTIONAL, servedIMEI OPTIONAL, servedMSISDN OPTIONAL, msClassmark OPTIONAL, [4] Classmark [3] MSISDN [2] IMEI [1] IMSI [0] CallEventRecordType ::= SET [169] CallReference [9] ManagementExtensions [168] MSCId OPTIONAL, [7] NumberOfForwarding [8] HLRIntResult OPTIONAL, [5] RoutingNumber [6] TimeStamp OPTIONAL, [4] BasicServiceCode [2] MSISDN [3] RecordingEntity OPTIONAL, [0] CallEventRecordType [1] IMSI OPTIONAL, ::= SET [198] ConcatenatedSMSReferenceNumber OPTIONAL, sequenceNumberOfTheCurrentSMS [199] SequenceNumberOfTheCurrentSMS [200] HotBillingTag [201] CallingNumber [202] CallReference OPTIONAL, OPTIONAL, OPTIONAL,
A-138
Issue 07 (2007-10-10)

recordingEntity OPTIONAL, location OPTIONAL, basicServices OPTIONAL, supplService OPTIONAL, ssAction OPTIONAL, ssActionTime OPTIONAL, ssParameters OPTIONAL, ssActionResult OPTIONAL, callReference OPTIONAL, recordExtensions systemType OPTIONAL, ussdCodingScheme ussdString ussdNotifyCounter OPTIONAL, ussdRequestCounter additionalChgInfo OPTIONAL, classmark3 OPTIONAL, chargedParty OPTIONAL, orgRNCorBSCId orgMSCId OPTIONAL, globalAreaID OPTIONAL, subscriberCategory firstmccmnc OPTIONAL, hotBillingTag OPTIONAL } CommonEquipRecord { recordType OPTIONAL, equipmentType OPTIONAL, equipmentId OPTIONAL, servedIMSI OPTIONAL, [3] IMSI [2] EquipmentId [1] EquipmentType [0] CallEventRecordType ::= SET [200] HotBillingTag [190] SubscriberCategory [192] MCCMNC [188] GAI [167] RNCorBSCId [168] MSCId [141] ChargedParty [140] Classmark3 [129] UssdRequestCounter [133] AdditionalChgInfo [126] UssdCodingScheme [127] SEQUENCE OF UssdString [128] UssdNotifyCounter [14] ManagementExtensions [15] SystemType [13] CallReference [12] SSActionResult [11] SSParameters [10] TimeStamp [9] SSActionType [8] SS-Code [7] BasicServices [6] LocationAreaAndCell [5] RecordingEntity
A CDR Format
OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
Issue 07 (2007-10-10)
A-139
A CDR Format
servedMSISDN OPTIONAL, recordingEntity OPTIONAL, basicService OPTIONAL, changeOfService supplServicesUsed seizureTime OPTIONAL, releaseTime OPTIONAL, callDuration OPTIONAL, callReference OPTIONAL, sequenceNumber recordExtensions systemType OPTIONAL, rateIndication OPTIONAL, fnur OPTIONAL, partialRecordType OPTIONAL, causeForTerm OPTIONAL, diagnostics OPTIONAL, servedIMEI OPTIONAL, additionalChgInfo OPTIONAL, orgRNCorBSCId orgMSCId OPTIONAL, subscriberCategory hotBillingTag OPTIONAL } [190] SubscriberCategory [200] HotBillingTag [167] RNCorBSCId [168] MSCId [133] AdditionalChgInfo [102] IMEI [101] Diagnostics [100] CauseForTerm [18] PartialRecordType [17] Fnur [16] RateIndication [13] SequenceNumber [14] ManagementExtensions [15] SystemType [12] CallReference [11] CallDuration [10] TimeStamp [7] SEQUENCE OF ChangeOfService [8] SEQUENCE OF SuppServiceUsed [9] TimeStamp [6] BasicServiceCode [5] RecordingEntity [4] MSISDN
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
-------------------------------------------------------------------------------- OBSERVED IMEI TICKETS ------------------------------------------------------------------------------ObservedIMEITicket { servedIMEI imeiStatus servedIMSI servedMSISDN recordingEntity [0] IMEI, [1] IMEIStatus, [2] IMSI, [3] MSISDN OPTIONAL, [4] RecordingEntity, ::= SET
A-140
Issue 07 (2007-10-10)

eventTime location imeiCheckEvent callReference recordExtensions orgMSCId OPTIONAL } [5] TimeStamp,
A CDR Format
[6] LocationAreaAndCell, [7] IMEICheckEvent OPTIONAL, [8] CallReference OPTIONAL, [9] ManagementExtensions OPTIONAL, [168] MSCId
-------------------------------------------------------------------------------- LOCATION SERICE TICKETS ------------------------------------------------------------------------------MTLCSRecord { recordType OPTIONAL, recordingEntity OPTIONAL, lcsClientType OPTIONAL, lcsClientIdentity OPTIONAL, servedIMSI OPTIONAL, servedMSISDN OPTIONAL, locationType OPTIONAL, lcsQos OPTIONAL, lcsPriority OPTIONAL, mlc-Number OPTIONAL, ventTimeStamp OPTIONAL, measureDuration OPTIONAL, notificationToMSUser OPTIONAL, privacyOverride location OPTIONAL, locationEstimate positioningData OPTIONAL, lcsCause OPTIONAL, diagnostics OPTIONAL, [18] Diagnostics [17] LCSCause [15] Ext-GeographicalInformation [16] PositioningData OPTIONAL, [13] NULL [14] LocationAreaAndCell OPTIONAL, [12] NotificationToMSUser [11] CallDuration [10] TimeStamp [9] ISDN-AddressString [8] LCS-Priority [7] LCSQoSInfo [6] LocationType [5] MSISDN [4] IMSI [3] LCSClientIdentity [2] LCSClientType [1] RecordingEntity [0] CallEventRecordType ::= SET
Issue 07 (2007-10-10)
A-141
A CDR Format
systemType OPTIONAL, recordExtensions OPTIONAL, causeForTerm OPTIONAL, lcsReferenceNumber OPTIONAL, servedIMEI OPTIONAL, additionalChgInfo OPTIONAL, chargedParty OPTIONAL, orgRNCorBSCId OPTIONAL, orgMSCId OPTIONAL, globalAreaID OPTIONAL, subscriberCategory OPTIONAL, firstmccmnc OPTIONAL, hotBillingTag OPTIONAL, callReference OPTIONAL } MOLCSRecord { recordType OPTIONAL, recordingEntity OPTIONAL, lcsClientType OPTIONAL, lcsClientIdentity OPTIONAL, servedIMSI OPTIONAL, servedMSISDN OPTIONAL, molr-Type OPTIONAL, lcsQos OPTIONAL, lcsPriority OPTIONAL, mlc-Number OPTIONAL, eventTimeStamp OPTIONAL, [10] TimeStamp [9] ISDN-AddressString [8] LCS-Priority [7] LCSQoSInfo [6] MOLR-Type [5] MSISDN [4] IMSI [3] LCSClientIdentity [2] LCSClientType [1] RecordingEntity [0] CallEventRecordType ::= SET [201] CallReference [200] HotBillingTag [192] MCCMNC [190] SubscriberCategory [188] GAI [168] MSCId [167] RNCorBSCId [141] ChargedParty [133] AdditionalChgInfo [102] IMEI [101] CallReferenceNumber [21] CauseForTerm [20] ManagementExtensions [19] SystemType
A-142
Issue 07 (2007-10-10)

measureDuration OPTIONAL, location OPTIONAL, locationEstimate positioningData OPTIONAL, lcsCause OPTIONAL, diagnostics OPTIONAL, systemType OPTIONAL, recordExtensions causeForTerm OPTIONAL, lcsReferenceNumber servedIMEI OPTIONAL, additionalChgInfo OPTIONAL, chargedParty OPTIONAL, orgRNCorBSCId orgMSCId OPTIONAL, globalAreaID OPTIONAL, subscriberCategory firstmccmnc OPTIONAL, hotBillingTag OPTIONAL, callReference OPTIONAL } NILCSRecord { recordType OPTIONAL, recordingEntity OPTIONAL, lcsClientType OPTIONAL, lcsClientIdentity OPTIONAL, servedIMSI OPTIONAL, servedMSISDN OPTIONAL, servedIMEI OPTIONAL, emsDigits OPTIONAL, [7] ISDN-AddressString [6] IMEI [5] MSISDN [4] IMSI [3] LCSClientIdentity [2] LCSClientType [1] RecordingEntity [0] CallEventRecordType ::= SET [201] CallReference [200] HotBillingTag [190] SubscriberCategory [192] MCCMNC [188] GAI [167] RNCorBSCId [168] MSCId [141] ChargedParty [133] AdditionalChgInfo [101] CallReferenceNumber [102] IMEI [18] ManagementExtensions [19] CauseForTerm [17] SystemType [16] Diagnostics [15] LCSCause [13] Ext-GeographicalInformation [14] PositioningData [12] LocationAreaAndCell [11] CallDuration
A CDR Format
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
Issue 07 (2007-10-10)
A-143
A CDR Format
emsKey OPTIONAL, lcsQos OPTIONAL, lcsPriority OPTIONAL, mlc-Number OPTIONAL, eventTimeStamp OPTIONAL, measureDuration OPTIONAL, location OPTIONAL, locationEstimate positioningData OPTIONAL, lcsCause OPTIONAL, diagnostics OPTIONAL, systemType OPTIONAL, recordExtensions OPTIONAL, causeForTerm OPTIONAL, lcsReferenceNumber OPTIONAL, additionalChgInfo OPTIONAL, chargedParty OPTIONAL, orgRNCorBSCId OPTIONAL, orgMSCId OPTIONAL, globalAreaID OPTIONAL, subscriberCategory OPTIONAL, firstmccmnc OPTIONAL, hotBillingTag OPTIONAL, callReference OPTIONAL } [201] CallReference [200] HotBillingTag [192] MCCMNC [190] SubscriberCategory [188] GAI [168] MSCId [167] RNCorBSCId [141] ChargedParty [133] AdditionalChgInfo [101] CallReferenceNumber [21] CauseForTerm [19] SystemType [18] Diagnostics [17] LCSCause [13] CallDuration [12] TimeStamp [11] ISDN-AddressString [10] LCS-Priority [9] LCSQoSInfo [8] ISDN-AddressString
[14] LocationAreaAndCell [15] Ext-GeographicalInformation [16] PositioningData OPTIONAL,
[20] ManagementExtensions
-------------------------------------------------------------------------------- FTAM / FTP / TFTP FILE CONTENTS -------------------------------------------------------------------------------
A-144
Issue 07 (2007-10-10)
A CDR Format
CallEventDataFile { headerRecord callEventRecords trailerRecord extensions } ObservedIMEITicketFile { productionDateTime observedIMEITickets noOfRecords extensions } HeaderRecord { productionDateTime recordingEntity extensions } TrailerRecord { productionDateTime recordingEntity firstCallDateTime lastCallDateTime noOfRecords extensions }
::= SEQUENCE [0] HeaderRecord, [1] SEQUENCE OF CallEventRecord, [2] TrailerRecord, [3] ManagementExtensions
::= SEQUENCE
[0] TimeStamp, [1] SEQUENCE OF ObservedIMEITicket, [2] INTEGER, [3] ManagementExtensions
::= SEQUENCE [0] TimeStamp, [1] RecordingEntity, [2] ManagementExtensions
::= SEQUENCE [0] TimeStamp, [1] RecordingEntity, [2] TimeStamp, [3] TimeStamp, [4] INTEGER, [5] ManagementExtensions
-------------------------------------------------------------------------------- COMMON DATA TYPES ------------------------------------------------------------------------------AdditionalChgInfo { chargeIndicator chargeParameters } AddressString ::= OCTET STRING (SIZE (1..maxAddressLength)) -- This type is used to represent a number for addressing -- purposes. It is composed of ----- a) b) a) one octet for nature of address, and numbering plan indicator. digits of an address encoded as TBCD-String. The first octet includes a one bit extension indicator, a [0] ChargeIndicator [1] OCTET STRING OPTIONAL, OPTIONAL ::= SEQUENCE
Issue 07 (2007-10-10)
A-145
A CDR Format
---

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 -------------- b) -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 1111 reserved for extension all other values are reserved. The following octets representing digits of an address encoded as a TBCD-STRING.
maxAddressLength INTEGER ::= 20 AiurRequested { --- See Bearer Capability TS 24.008 -- (note that value "4" is intentionally missing -- because it is not used in TS 24.008) -aiur09600BitsPerSecond aiur14400BitsPerSecond aiur19200BitsPerSecond aiur28800BitsPerSecond aiur38400BitsPerSecond aiur43200BitsPerSecond aiur57600BitsPerSecond aiur38400BitsPerSecond1 aiur38400BitsPerSecond2 aiur38400BitsPerSecond3 aiur38400BitsPerSecond4 } (1), (2), (3), (5), (6), (7), (8), (9), (10), (11), (12) ::= ENUMERATED
A-146
Issue 07 (2007-10-10)
A CDR Format
AOCParameters { --- See TS 22.024. -e1 e2 e3 e4 e5 e6 e7 } AOCParmChange { changeTime newParameters } BasicService
::= SEQUENCE
[1] EParameter [2] EParameter [3] EParameter [4] EParameter [5] EParameter [6] EParameter [7] EParameter
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
::= SEQUENCE [0] TimeStamp, [1] AOCParameters
--This parameter identifies the ISDN Basic service as defined in ETSI specification ETS 300 196. ------------allServices speech unrestricteDigtalInfo audio3k1HZ unrestricteDigtalInfowithtoneandannoucement telephony3k1HZ teletext telefaxGroup4Class1 videotextSyntaxBased videotelephony telefaxGroup2-3 telephony7kHZ '23'h '24'h '25'h '26'h '04'h '20'h '21'h '22'h '00'h '01'h '02'h '03'h
BasicServices
::= SET OF BasicServiceCode
BasicServiceCode ::= CHOICE { bearerService teleservice } [2] BearerServiceCode, [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:
Issue 07 (2007-10-10)
A-147
A CDR Format
-- bits 87654321: group (bits 8765) and specific service -- (bits 4321) -------------------------compound Teleservice Group Codes are only used in call ------------------------allPLMN-specificTS plmn-specificTS-1 plmn-specificTS-2 plmn-specificTS-3 plmn-specificTS-4 plmn-specificTS-5 plmn-specificTS-6 plmn-specificTS-7 plmn-specificTS-8 plmn-specificTS-9 plmn-specificTS-A plmn-specificTS-B plmn-specificTS-C plmn-specificTS-D plmn-specificTS-E plmn-specificTS-F (0xd0), (0xd1), (0xd2), (0xd3), (0xd4), (0xd5), (0xd6), (0xd7), (0xd8), (0xd9), (0xda), (0xdb), (0xdc), (0xdd), (0xde), (0xdf) allVoiceGroupCallServices (0x90), voiceGroupCall voiceBroadcastCall (0x91), (0x92), independent supplementary service operations, i.e. they are not used in InsertSubscriberData or in DeleteSubscriberData messages. allFacsimileTransmissionServices (0x60), facsimileGroup3AndAlterSpeech automaticFacsimileGroup3 facsimileGroup4 (0x61), (0x62), (0x63), allShortMessageServices shortMessageMT-PP shortMessageMO-PP (0x20), (0x21), (0x22), allTeleservices telephony emergencyCalls (0x00), (0x10), (0x11), (0x12),
allSpeechTransmissionServices
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'
BearerServiceCode ::= OCTET STRING (SIZE (1)) -- This type is used to represent the code identifying a single
A-148
Issue 07 (2007-10-10)

-- bearer service, a group of bearer services, or all bearer -- services. The services are defined in TS 3GPP TS 22.002 [3]. -- The internal structure is defined as follows: --- plmn-specific bearer services: -- bits 87654321: defined by the HPLMN operator -- rest of bearer services: -- bit 8: 0 (unused) -- bits 7654321: group (bits 7654), and rate, if applicable -- (bits 321) -------------------------------------------The following non-hierarchical Compound Bearer Service Groups are defined in TS GSM 02.30: allDataCircuitAsynchronous (0x50), allSpeechFollowedByDataCDS (0x48), allSpeechFollowedByDataCDA (0x40), allAlternateSpeech-DataCDS (0x38), allAlternateSpeech-DataCDA (0x30), allDataPDS-Services dataPDS-2400bps dataPDS-4800bps dataPDS-9600bps general-dataPDS (0x28), (0x2c), (0x2d), (0x2e), (0x2f), allPadAccessCA-Services padAccessCA-300bps padAccessCA-1200bps padAccessCA-1200-75bps padAccessCA-2400bps padAccessCA-4800bps padAccessCA-9600bps general-padAccessCA (0x20), (0x21), (0x22), (0x23), (0x24), (0x25), (0x26), (0x27), allDataCDS-Services dataCDS-1200bps dataCDS-2400bps dataCDS-4800bps dataCDS-9600bps general-dataCDS (0x18), (0x1a), (0x1c), (0x1d), (0x1e), (0x1f), allBearerServices allDataCDA-Services dataCDA-300bps dataCDA-1200bps dataCDA-1200-75bps dataCDA-2400bps dataCDA-4800bps dataCDA-9600bps general-dataCDA (0x00), (0x10), (0x11), (0x12), (0x13), (0x14), (0x15), (0x16), (0x17),
A CDR Format
Issue 07 (2007-10-10)
A-149
A CDR Format
-------------- compound Bearer Service Group Codes are only used in call --------------------allPLMN-specificBS plmn-specificBS-1 plmn-specificBS-2 plmn-specificBS-3 plmn-specificBS-4 plmn-specificBS-5 plmn-specificBS-6 plmn-specificBS-7 plmn-specificBS-8 plmn-specificBS-9 plmn-specificBS-A plmn-specificBS-B plmn-specificBS-C plmn-specificBS-D plmn-specificBS-E plmn-specificBS-F (0xd0), (0xd1), (0xd2), (0xd3), (0xd4), (0xd5), (0xd6), (0xd7), (0xd8), (0xd9), (0xda), (0xdb), (0xdc), (0xdd), (0xde), (0xdf) independent supplementary service operations, i.e. they are not used in InsertSubscriberData or in DeleteSubscriberData messages.

covers "allDataCDA-Services", "allAlternateSpeech-DataCDA" and "allSpeechFollowedByDataCDA" allDataCircuitSynchronous "allSpeechFollowedByDataCDS" allAsynchronousServices (0x60), covers "allDataCDA-Services", "allAlternateSpeech-DataCDA", "allSpeechFollowedByDataCDA" and "allPadAccessCDA-Services" allSynchronousServices (0x68), covers "allDataCDS-Services", "allAlternateSpeech-DataCDS", "allSpeechFollowedByDataCDS" and "allDataPDS-Services" (0x58), covers "allDataCDS-Services", "allAlternateSpeech-DataCDS" and
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 --- The call duration in seconds. -- For successful calls this is the chargeable duration. -- For call attempts this is the call holding time. -::= INTEGER
A-150
Issue 07 (2007-10-10)
A CDR Format
CallEventRecordType { moCallRecord mtCallRecord roamingRecord incGatewayRecord outGatewayRecord transitCallRecord moSMSRecord mtSMSRecord ssActionRecord hlrIntRecord commonEquipRecord moTraceRecord mtTraceRecord termCAMELRecord mtLCSRecord moLCSRecord niLCSRecord forwardCallRecord } CalledNumber CallingNumber CallingPartyCategory CallReference
::= INTEGER (0), (1), (2), (3), (4), (5), (6), (7), (10), (11), (14), (15), (16), (17), (23), (24), (25), (100)
::= BCDDirectoryNumber ::= BCDDirectoryNumber ::= Category ::= OCTET STRING (SIZE (1..8))
CallReferenceNumber ::= OCTET STRING (SIZE (1..8)) CAMELDestinationNumber CAMELInformation { cAMELDestinationNumber connectedNumber roamingNumber mscOutgoingROUTE seizureTime answerTime releaseTime callDuration dataVolume cAMELInitCFIndicator causeForTerm cAMELModification freeFormatData diagnostics freeFormatDataAppend freeFormatData-2 freeFormatDataAppend-2 } [1] CAMELDestinationNumber [2] ConnectedNumber [3] RoamingNumber [4] ROUTE [5] TimeStamp [6] TimeStamp [7] TimeStamp [8] CallDuration [9] DataVolume [10] CAMELInitCFIndicator [11] CauseForTerm [12] ChangedParameters [13] FreeFormatData [14] Diagnostics [15] BOOLEAN [16] FreeFormatData [17] BOOLEAN OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL ::= DestinationRoutingAddress ::= SET
Issue 07 (2007-10-10)
A-151
A CDR Format
CAMELSMSInformation { gsm-SCFAddress serviceKey defaultSMSHandling freeFormatData callingPartyNumber
::= SET [1] Gsm-SCFAddress [2] ServiceKey [3] DefaultSMS-Handling [4] FreeFormatData [5] CallingNumber [6] CalledNumber [7] AddressString [8] CallReferenceNumber OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL OPTIONAL, OPTIONAL,
destinationSubscriberNumber cAMELSMSCAddress smsReferenceNumber } CAMELInitCFIndicator { noCAMELCallForwarding cAMELCallForwarding } CAMELModificationParameters -(0), (1)
::= ENUMERATED
::= SET
-- The list contains only parameters changed due to CAMEL call -- handling. -{ callingPartyNumber callingPartyCategory originalCalledPartyNumber genericNumbers redirectingPartyNumber redirectionCounter } [0] CallingNumber [1] CallingPartyCategory [2] OriginalCalledNumber [3] GenericNumbers [4] RedirectingNumber [5] NumberOfForwarding OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
Category --
-- The internal structure is defined in ITU-T Rec Q.763. --see subscribe category CauseForTerm --- 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 partialRecord partialRecordCallReestablishment unsuccessfulCallAttempt stableCallAbnormalTermination cAMELInitCallRelease unauthorizedRequestingNetwork unauthorizedLCSClient (5), (52), (53), (0), (1), (2), (3), (4), ::= INTEGER
A-152
Issue 07 (2007-10-10)

positionMethodFailure unknownOrUnreachableLCSClient } CellId --- Coded according to TS 24.008 -ChangedParameters { changeFlags changeList } ChangeFlags { callingPartyNumberModified callingPartyCategoryModified originalCalledPartyNumberModified genericNumbersModified redirectingPartyNumberModified redirectionCounterModified } ChangeOfClassmark { classmark changeTime } ChangeOfRadioChannel { radioChannel changeTime speechVersionUsed } ChangeOfService { basicService transparencyInd changeTime rateIndication fnur } ChannelCoding { tchF4800 tchF9600 tchF14400 } ChargeIndicator ::= INTEGER (1), (2), (3) ::= ENUMERATED [0] BasicServiceCode, [1] TransparencyInd [2] TimeStamp, [3] RateIndication [4] Fnur OPTIONAL OPTIONAL, OPTIONAL, ::= SEQUENCE [0] TrafficChannel, [1] TimeStamp, [2] SpeechVersionIdentifier OPTIONAL ::= SEQUENCE [0] Classmark, [1] TimeStamp ::= SEQUENCE (0), (1), (2), (3), (4), (5) ::= BIT STRING [0] ChangeFlags, [1] CAMELModificationParameters OPTIONAL ::= SET ::= OCTET STRING (SIZE(2)) (54), (58)
A CDR Format
Issue 07 (2007-10-10)
A-153
A CDR Format
{ noIndication noCharge charge } Classmark --- See Mobile station classmark 2 or 3 TS 24.008 -ConnectedNumber DataVolume -::= BCDDirectoryNumber ::= INTEGER ::= OCTET STRING (2) (0), (1),
-- The volume of data transferred in segments of 64 octets. -Day --DayClass --DayClasses --DayDefinition --{ ----} --DayDefinitions --DateDefinition --{ -----} --DateDefinitions --DayOfTheWeek --{ ----------} DestinationRoutingAddress ::= BCDDirectoryNumber allDays sunday monday tuesday wednesday thursday friday saturday (0), (1), (2), (3), (4), (5), (6), (7) ::= SET OF DateDefinition ::= ENUMERATED month day dayClass [0] Month, [1] Day, [2] ObjectInstance ::= SET OF DayDefinition ::= SEQUENCE day dayClass [0] DayOfTheWeek, [1] ObjectInstance ::= INTEGER (1..31) ::= ObjectInstance ::= SET OF DayClass ::= SEQUENCE
A-154
Issue 07 (2007-10-10)

DefaultCallHandling ::= ENUMERATED { continueCall releaseCall } -- exception handling: (0), (1)
A CDR Format
-- 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 } (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 { gsm0408Cause -- 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 -- See ITU-T Q.767 networkSpecificCause manufacturerSpecificCause } DefaultSMS-Handling ::= ENUMERATED { continueTransaction releaseTransaction } ---exception handling: reception of values in range 2-31 shall be treated as "continueTransaction" reception of values greater than 31 shall be treated as "releaseTransaction" ::= SET OF AE-title ::= BOOLEAN ::= SEQUENCE (0) , (1) [3] ManagementExtension, [4] ManagementExtension -- To be defined by network operator -- To be defined by manufacturer [2] INTEGER, [0] INTEGER, ::= CHOICE (0)
--Destinations EmergencyCallIndEnable EmergencyCallIndication { cellId callerId }
[0] CellId, [1] IMSIorIMEI
Issue 07 (2007-10-10)
A-155
A CDR Format
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 ----------------------------- An Ext-GeographicalInformation parameter comprising more than one octet and -- containing any other shape or an incorrect number of octets or coding according Degrees of Latitude Degrees of Longitude Uncertainty code Degrees of Latitude Degrees of Longitude Uncertainty semi-major axis Uncertainty semi-minor axis Angle of major axis confidence Degrees of Latitude Degrees of Longitude Altitude 2 octets 1 octet 1 octet 1 octet 1 octet 1 octet 3 octets 3 octets 2 octets 1 octet 1 octet 1 octet 1 octet 3 octets 3 octets Uncertainty semi-major axis Uncertainty semi-minor axis Angle of major axis Uncertainty altitude confidence Degrees of Latitude Degrees of Longitude Inner radius Uncertainty radius Offset angle Included angle confidence Degrees of Latitude Degrees of Longitude 1 octet 3 octets 3 octets 3 octets 3 octets 1 octet 3 octets 3 octets 1 octet 1 octet 1 octet
-- Octets 2 to 11 for case (b) - Ellipsoid point with uncertainty ellipse:
-- Octets 2 to 14 for case (c) - Ellipsoid point with altitude and uncertainty ellipsoid
-- Octets 2 to 13 for case (d) - Ellipsoid Arc
-- Octets 2 to 7 for case (e) - Ellipsoid Point
A-156
Issue 07 (2007-10-10)

-- to 3G TS 23.032 shall be treated as invalid data by a receiver. --
A CDR Format
-- 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 { conferenceBridge } FileType { callRecords traceRecords observedIMEITicket } Fnur { --- See Bearer Capability TS 24.008 -fnurNotApplicable fnur9600-BitsPerSecond fnur14400BitsPerSecond fnur19200BitsPerSecond fnur28800BitsPerSecond fnur38400BitsPerSecond fnur48000BitsPerSecond fnur56000BitsPerSecond fnur64000BitsPerSecond fnur33600BitsPerSecond fnur32000BitsPerSecond fnur31200BitsPerSecond } ForwardToNumber FreeFormatData --- Free formated data as sent in the FCI message -- See TS 29.078 -::= AddressString ::= OCTET STRING (SIZE(1..160)) (1), (2), (3), (4), (5), (6), (7), (8), (9), (10), (11) (0), ::= ENUMERATED (1), (9), (14) ::= INTEGER (0) ::= INTEGER
Issue 07 (2007-10-10)
A-157
A CDR Format
GenericNumber GenericNumbers Gsm-SCFAddress --- See TS 29.002 -HLRIntResult ::= Diagnostics ::= BCDDirectoryNumber ::= SET OF GenericNumber ::= ISDNAddressString
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 { noHotBilling hotBilling } HSCSDParmsChange { changeTime hSCSDChanAllocated initiatingParty aiurRequested chanCodingUsed hSCSDChanRequested } [0] TimeStamp, [1] NumOfHSCSDChanAllocated, [2] InitiatingParty [3] AiurRequested [4] ChannelCoding, [5] NumOfHSCSDChanRequested OPTIONAL OPTIONAL, OPTIONAL, ::= SEQUENCE (0), (1) ::= INTEGER
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 { mobileOriginatedCall mobileTerminatedCall smsMobileOriginating smsMobileTerminating ssAction locationUpdate } IMEIStatus { ::= ENUMERATED (0), (1), (2), (3), (4), (5) ::= INTEGER
A-158
Issue 07 (2007-10-10)

greyListedMobileEquipment blackListedMobileEquipment } IMSIorIMEI { imsi imei } InitiatingParty { network subscriber } ISDN-AddressString ::= (0), (1) ::= ENUMERATED [0] IMSI, [1] IMEI ::= CHOICE (0), (1),
A CDR Format
nonWhiteListedMobileEquipment (2)
AddressString (SIZE (1..maxISDN-AddressLength))
-- This type is used to represent ISDN numbers. maxISDN-AddressLength INTEGER ::= 9 LCSCause --- 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 { lcsClientExternalID lcsClientDialedByMS lcsClientInternalID } LCSClientExternalID ::= SEQUENCE { externalAddress -} LCSClientInternalID ::= ENUMERATED { broadcastService o-andM-HPLMN o-andM-VPLMN anonymousLocation } -- for a CAMEL phase 3 PLMN operator client, the value targetMSsubscribedService shall be used (0), (1), (2), (3), (4) extensionContainer [0] AddressString OPTIONAL [1] ExtensionContainer OPTIONAL [0] LCSClientExternalID [1] AddressString [2] LCSClientInternalID OPTIONAL, OPTIONAL, OPTIONAL ::= SEQUENCE ::= OCTET STRING (SIZE(1))
targetMSsubscribedService
Issue 07 (2007-10-10)
A-159
A CDR Format
LCSClientType ::= ENUMERATED { emergencyServices valueAddedServices plmnOperatorServices lawfulInterceptServices } ---receiver -a return error shall then be returned if received in a MAP invoke exception handling: 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 (0), (1), (2), (3)
LCSQoSInfo ::= SEQUENCE { horizontal-accuracy verticalCoordinateRequest vertical-accuracy responseTime } LevelOfCAMELService { basic callDurationSupervision onlineCharging } LocationAreaAndCell { locationAreaCode cellIdentifier --- 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 --- See TS 24.008 -LocationChange { location changeTime } Location-info { mscNumber location-area cell-identification [1] MscNo [2] LocationAreaCode, [3] CellId OPTIONAL OPTIONAL, ::= SEQUENCE [0] LocationAreaAndCell, [1] TimeStamp ::= SEQUENCE ::= OCTET STRING (SIZE(2)) [0] LocationAreaCode, [1] CellId ::= SEQUENCE (0), (1), (2) ::= BIT STRING [0] Horizontal-Accuracy [1] NULL [2] Vertical-Accuracy [3] ResponseTime OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
A-160
Issue 07 (2007-10-10)

} LocationType ::= SEQUENCE { locationEstimateType deferredLocationEventType } LocationEstimateType ::= ENUMERATED { currentLocation currentOrLastKnownLocation initialLocation activateDeferredLocation cancelDeferredLocation } ---value LocUpdResult ManagementExtensions ::= Diagnostics ::= SET OF ManagementExtension exception handling: a ProvideSubscriberLocation-Arg containing an unrecognized (0), (1), (2), (3), (4) [0] LocationEstimateType, [1] DeferredLocationEventType
A CDR Format
OPTIONAL
LocationEstimateType shall be rejected by the receiver with a return error cause of unexpected data
ManagementExtension ::= SEQUENCE { identifier significance information } OBJECT IDENTIFIER, [1] BOOLEAN DEFAULT FALSE, [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 --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 Month MOLR-Type MSCAddress ::= OCTET STRING ::= INTEGER (1..12) ::= INTEGER ::= AddressString ::= OCTET STRING(SIZE(1))
Issue 07 (2007-10-10)
A-161
A CDR Format
MscNo --- See TS 23.003 -MSISDN --- See TS 23.003 -MSPowerClasses NetworkCallReference -- See TS 29.002 -NetworkSpecificCode --
::= ISDN-AddressString
::= ISDN-AddressString
::= SET OF RFPowerCapability ::= CallReferenceNumber
::= INTEGER
-- To be defined by network operator -NetworkSpecificServices ::= SET OF NetworkSpecificCode
NotificationToMSUser ::= ENUMERATED { notifyLocationAllowed (0), (1), (2), notifyAndVerify-LocationAllowedIfNoResponse notifyAndVerify-LocationNotAllowedIfNoResponse locationNotAllowed } -- exception handling: -- At reception of any other value than the ones listed the receiver shall ignore -- NotificationToMSUser. NumberOfForwarding ::= INTEGER (1..5) NumOfHSCSDChanRequested NumOfHSCSDChanAllocated ObservedIMEITicketEnable OriginalCalledNumber OriginDestCombinations OriginDestCombination { origin destination --- Note that these values correspond to the contents -- of the attributes originId and destinationId -- respectively. At least one of the two must be present. -[0] INTEGER [1] INTEGER OPTIONAL, OPTIONAL ::= INTEGER ::= INTEGER ::= BOOLEAN ::= BCDDirectoryNumber ::= SET OF OriginDestCombination ::= SEQUENCE (3)
A-162
Issue 07 (2007-10-10)

} PartialRecordTimer PartialRecordType { timeLimit serviceChange locationChange classmarkChange aocParmChange radioChannelChange hSCSDParmChange changeOfCAMELDestination firstHotBill severalSSOperationBill } PartialRecordTypes PositioningData --- See Positioning Data IE (octet 3..n), 3GPP TS 49.031 -RadioChannelsRequested RadioChanRequested { --- See Bearer Capability TS 24.008 -halfRateChannel fullRateChannel dualHalfRatePreferred dualFullRatePreferred } --RecordClassDestination --{ ----} --RecordClassDestinations RecordingEntity RecordingMethod { inCallRecord inSSRecord } RedirectingNumber ::= BCDDirectoryNumber (0), (1) ::= SET OF RecordClassDestination osApplication fileType [0] AE-title, [1] FileType ::= CHOICE (0), (1), (2), (3) ::= SET OF RadioChanRequested ::= ENUMERATED ::= SET OF PartialRecordType ::= OCTET STRING (SIZE(1..33)) (3), (4), (5), (6), (7), (20), (21) (0), (1), (2), ::= INTEGER ::= ENUMERATED
A CDR Format
::= AddressString ::= ENUMERATED
Issue 07 (2007-10-10)
A-163
A CDR Format
RedirectingCounter
::= INTEGER
ResponseTime ::= SEQUENCE { responseTimeCategory } -time. ResponseTimeCategory ::= ENUMERATED { lowdelay delaytolerant } --exception handling: an unrecognized value shall be treated the same as value 1 (delaytolerant) ::= INTEGER (0), (1) note: an expandable SEQUENCE simplifies later addition of a numeric response ResponseTimeCategory
RFPowerCapability --
-- This field contains the RF power capability of the Mobile station -- classmark 1 and 2 of TS 24.008 expressed as an integer. -RoamingNumber --- See TS 23.003 -RoutingNumber { roaming forwarded } Service { teleservice bearerService supplementaryService networkSpecificService } ServiceDistanceDependencies ServiceDistanceDependency { aocService chargingZone --- Note that these values correspond to the contents -- of the attributes aocServiceId and zoneId -- respectively. -} [0] INTEGER, [1] INTEGER OPTIONAL ::= SET OF ServiceDistanceDependency ::= SEQUENCE [1] TeleserviceCode, [2] BearerServiceCode, [3] SS-Code, [4] NetworkSpecificCode ::= CHOICE [1] RoamingNumber, [2] ForwardToNumber ::= CHOICE ::= ISDN-AddressString
A-164
Issue 07 (2007-10-10)
A CDR Format
ServiceKey ::= INTEGER (0..2147483647) SimpleIntegerName SimpleStringName SMSResult ::= INTEGER ::= GraphicString ::= 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 -------see GSM 08.08 000 0001 001 0001 010 0001 000 0101 001 0101 010 0101 GSM speech full rate version 1 GSM speech full rate version 2 GSM speech full rate version 3 GSM speech half rate version 1 GSM speech half rate version 2 GSM speech half rate version 3 ::= Diagnostics ::= ENUMERATED (0), (1), (2), (3), (4), (5), (6), (7) for future use for future use used for enhanced full rate for future use ::= OCTET STRING (SIZE(1))
SSActionResult SSActionType { registration erasure activation deactivation interrogation invocation passwordRegistration ussdInvocation } -- ussdInvocation
(7) include ussd phase 1,phase 2
--SS Request = SSActionType SS-Code ::= OCTET STRING (SIZE (1)) -- This type is used to represent the code identifying a single -- 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
Issue 07 (2007-10-10)
A-165
A CDR Format
---------
allSS all SS
(0x00),
reserved for possible future use
allLineIdentificationSS (0x10), reserved for possible future use all line identification SS (0x11), (0x12), (0x13), (0x14), (0x15),
--calling-line-identification-presentation ------------------------------------allCallCompletionSS (0x40), explicit-call-transfer explicit call transfer mobile-access-hunting reserved for possible future use mobile access hunting (0x32), (0x31), allCallOfferingSS (0x30), reserved for possible future use allForwardingSS (0x20), (0x21), (0x24), (0x28), all forwarding SS call forwarding unconditional call deflection allCondForwardingSS all conditional forwarding SS allNameIdentificationSS (0x18), all name identification SS (0x19), calling name presentation calling line identification presentation calling line identification restriction connected line identification presentation connected line identification restriction malicious-call-identification reserved for possible future use malicious call identification --calling-line-identification-restriction --connected-line-identification-presentation --connected-line-identification-restriction
--calling-name-presentation
SS-Codes '00011010'B, to '00011111'B, are reserved for future NameIdentification Supplementary Service use.
--call-forwarding-unconditional --call-deflection
--call-forwarding-on-mobile-subscriber-busy call forwarding on mobile subscriber busy (0x2a), call forwarding on no reply --call-forwarding-on-no-reply
(0x29),
--call-forwarding-on-mobile-subscriber-not-reachable call forwarding on mobile subscriber not reachable
(0x2b),
all call offering SS includes also all forwarding SS
A-166
Issue 07 (2007-10-10)

-----call-waiting -----------------------------------------------allBarringSS all barring SS barringOfOutgoingCalls (0x91), barring of outgoing calls barring-of-all-outgoing-calls barring of all outgoing calls barring-of-outgoing-international-calls barring of outgoing international calls (0x93), (0x92), (0x90), allAdditionalInfoTransferSS (0x80), reserved for possible future use all additional information transfer SS uUS1-user-to-user-signalling UUS1 user-to-user signalling uUS2-user-to-user-signalling UUS2 user-to-user signalling uUS3-user-to-user-signalling UUS3 user-to-user signalling (0x83), (0x82), (0x81), allChargingSS all charging SS advice-of-charge-information advice of charge information advice-of-charge-charging advice of charge charging (0x72), (0x71), (0x70), reserved for possible future use allCommunityOfInterest-SS (0x60), reserved for possible future use all community of interest SS (0x61), closed user group multiPTY multiparty (0x51), allMultiPartySS all multiparty SS (0x50), reserved for possible future use multicall multicall (0x45), call waiting (0x42), call hold --call-hold (0x41), reserved for possible future use all Call completion SS
A CDR Format
--completion-of-call-to-busy-subscribers-originating-side completion of call to busy subscribers, originating side --completion-of-call-to-busy-subscribers-destination-side completion of call to busy subscribers, destination side
(0x43), (0x44),
this SS-Code is used only in InsertSubscriberData and DeleteSubscriberData
--closed-user-group
Issue 07 (2007-10-10)
A-167
A CDR Format
---------------------------------------------------allPLMN-specificSS plmn-specificSS-1 plmn-specificSS-2 plmn-specificSS-3 plmn-specificSS-4 plmn-specificSS-5 plmn-specificSS-6 plmn-specificSS-7 plmn-specificSS-8 plmn-specificSS-9 plmn-specificSS-A plmn-specificSS-B plmn-specificSS-C plmn-specificSS-D (0xf0), (0xf1), (0xf2), (0xf3), (0xf4), (0xf5), (0xf6), (0xf7), (0xf8), (0xf9), (0xfa), (0xfb), (0xfc), (0xfd), allMOLR-SS basicSelfLocation autonomousSelfLocation (0xc0), (0xc1), (0xc2), all Mobile Originating Location Request Classes allow an MS to request its own location allLCSPrivacyException (0xb0), all LCS Privacy Exception Classes universal (0xb1), (0xb2), allow location by any LCS client (0xa1), allCallPrioritySS (0xa0), reserved for possible future use all call priority SS enhanced-Multilevel-Precedence-Pre-emption-EMLPP-service (0x9b), boicExHC to the home PLMN barringOfIncomingCalls (0x99), barring of incoming calls barring-of-all-incoming-calls barring of all incoming calls (0x9a), (0x94),
barring of outgoing international calls except those directed
barring-of-incoming-calls-when-roaming-outside-home-PLMN-Country barring of incoming calls when roaming outside home PLMN country
enhanced Multilevel Precedence Pre-emption 'EMLPP) service
--callrelated
allow location by any value added LCS client to which a call is established from the target MS (0xb3), (0xb4), allow location by designated external value added LCS clients plmnoperator allow location by designated PLMN operator LCS clients
--callunrelated
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
A-168
Issue 07 (2007-10-10)

--plmn-specificSS-E ussd (0xfe), (0xff)
A CDR Format
SSParameters { forwardedToNumber unstructuredData } SupplServices SuppServiceUsed { ssCode ssTime } SwitchoverTime { hour minute second }
::= CHOICE [0] ForwardToNumber, [1] OCTET STRING
::= SET OF SS-Code ::= SEQUENCE [0] SS-Code [1] TimeStamp OPTIONAL, OPTIONAL
::= SEQUENCE INTEGER (0..23), INTEGER (0..59), INTEGER (0..59)
SystemType ::= ENUMERATED -- "unknown" is not to be used in PS domain. { unknown iuUTRAN gERAN } 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 TariffPeriod { switchoverTime tariffId [0] SwitchoverTime, [1] INTEGER ::= INTEGER ::= SEQUENCE (0), (1), (2)
-- Note that the value of tariffId corresponds -- to the attribute tariffId. } TariffPeriods ::= SET OF TariffPeriod
Issue 07 (2007-10-10)
A-169
A CDR Format
TariffSystemStatus { available checked standby active } (0), (1), (3) (2), -- available for modification -- "frozen" and checked ::= ENUMERATED
-- "frozen" awaiting activation -- "frozen" and active
TimeStamp --
-- 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 -- MM -- DD -- hh -- mm -- ss -- S -- hh -- mm -TrafficChannel { fullRate halfRate } TranslatedNumber TransparencyInd { transparent nonTransparent } ROUTE { rOUTENumber rOUTEName } --rOUTEName 1 10 octet TSChangeover { newActiveTS newStandbyTS --changeoverTime [0] INTEGER, [1] INTEGER, [2] GeneralizedTime OPTIONAL, ::= SEQUENCE [0] INTEGER, [1] GraphicString ::= cHOICE (0), (1) ::= ::= BCDDirectoryNumber ENUMERATED (0), (1) ::= ENUMERATED = = = = = = = = = Year 00 to 99 Month 01 to 12 Day 01 to 31 hour 00 to 23 minute 00 to 59 second 00 to 59 Sign 0 = "+", "-" hour 00 to 23 minute 00 to 59 BCD encoded BCD encoded BCD encoded BCD encoded BCD encoded BCD encoded ASCII encoded BCD encoded BCD encoded
A-170
Issue 07 (2007-10-10)

authkey checksum versionNumber [3] OCTET STRING [4] OCTET STRING [5] OCTET STRING OPTIONAL, OPTIONAL, OPTIONAL
A CDR Format
-- Note that if the changeover time is not -- specified then the change is immediate. } TSCheckError { errorId --fail } TSCheckErrorId { globalForm localForm } TSCheckResult { success fail } TSCopyTariffSystem { oldTS newTS } TSNextChange { noChangeover tsChangeover } TypeOfSubscribers { home visiting all } TypeOfTransaction { successful unsuccessful all } 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 (0), (1), (2) ::= ENUMERATED (0), (1), (2) -- HPLMN subscribers -- roaming subscribers ::= ENUMERATED [0] NULL, [1] TSChangeover ::=cHOICE [0] INTEGER, [1] INTEGER ::= SEQUENCE [0] NULL, [1] SET OF TSCheckError ::=cHOICE [0] OBJECT IDENTIFIER, [1] INTEGER ::=cHOICE [0] TSCheckErrorId [1] ANY DEFINED BY errorId OPTIONAL ::= SEQUENCE
Issue 07 (2007-10-10)
A-171
A CDR Format
-- by the uncertainty code with 67% confidence. ISDNAddressString ::= AddressString 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 --priorityLevelB --priorityLevel0 --priorityLevel1 --priorityLevel2 --priorityLevel3 --priorityLevel4 EMLPP-Priority ::= 6 EMLPP-Priority ::= 5 EMLPP-Priority ::= 0 EMLPP-Priority ::= 1 EMLPP-Priority ::= 2 EMLPP-Priority ::= 3 EMLPP-Priority ::= 4
SubscriberEmlppPriority ::= 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 --priorityLevelB --priorityLevel0 --priorityLevel1 --priorityLevel2 --priorityLevel3 --priorityLevel4 EMLPP-Priority ::= 6 EMLPP-Priority ::= 5 EMLPP-Priority ::= 0 EMLPP-Priority ::= 1 EMLPP-Priority ::= 2 EMLPP-Priority ::= 3 EMLPP-Priority ::= 4
CallEmlppPriority ::= OCTET STRING (SIZE (1)) --no priority applied --call priority level 4 --call priority level 3 --call priority level 2 --call priority level 1 --call priority level 0 --call priority level B --call priority level A 0 1 2 3 4 5 6 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
A-172
Issue 07 (2007-10-10)

{ numberNotPorted numberPorted } SubscriberCategory -- frenchuser -- englishuser -- germanuser ::= OCTET STRING (SIZE (1)) (0), (1)
A CDR Format
-- unknownuser = 0x00, = 0x01, = 0x02, = 0x03,
-- russianuser = 0x04, -- spanishuser = 0x05, -- specialuser = 0x06, -- reserveuser = 0x09, -- commonuser = 0x0a, -- superioruser = 0x0b, -- datacalluser = 0x0c, -- testcalluser = 0x0d, -- spareuser -- coinuser -- isup224 = 0x0e, = 0x20, = 0xe0 -- payphoneuser = 0x0f,
CUGOutgoingAccessIndicator ::= { notCUGCall (0), cUGCall } (1)
ENUMERATED
CUGInterlockCode ::= OCTET STRING (SIZE (4)) -CUGOutgoingAccessUsed ::= ENUMERATED { callInTheSameCUGGroup callNotInTheSameCUGGroup } SMSTEXT MSCCIC RNCorBSCId ::= OCTET STRING ::= INTEGER(0..65535) ::= OCTET STRING(SIZE (3)) (0), (1)
--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
Issue 07 (2007-10-10)
A-173
A CDR Format

--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 } CUGIncomingAccessUsed ::= ENUMERATED { callInTheSameCUGGroup callNotInTheSameCUGGroup } SmsUserDataType ---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 --20 --21 --22 Reserved for future EMS features (see subclause 3.10) RFC 822 E-Mail Header Hyperlink format element Reply Address Element Reserved for future use (U)SIM Toolkit Security Headers SME to SME specific use Reserved for future use ::= OCTET STRING (SIZE (1)) (0), (1) (1)
--23 - 6F --70 - 7F --80 - 9F --A0 - BF
A-174
Issue 07 (2007-10-10)

--C0 - DF --E0 - FE --FF SC specific use Reserved for future use normal SMS
A CDR Format
ConcatenatedSMSReferenceNumber MaximumNumberOfSMSInTheConcatenatedSMS SequenceNumberOfTheCurrentSMS SequenceNumber --(1... -DisconnectParty { callingPartyRelease calledPartyRelease networkRelease } ChargedParty { callingParty calledParty } ChargeAreaCode CUGIndex GuaranteedBitRate { gBR14400BitsPerSecond (1), gBR28800BitsPerSecond (2), gBR32000BitsPerSecond (3), gBR33600BitsPerSecond (4), gBR56000BitsPerSecond (5), gBR57600BitsPerSecond (6), gBR64000BitsPerSecond (7), gBR12200BitsPerSecond (106), gBR10200BitsPerSecond (107), gBR7950BitsPerSecond (108), gBR7400BitsPerSecond (109), gBR6700BitsPerSecond (110), gBR5900BitsPerSecond (111), gBR5150BitsPerSecond (112), gBR4750BitsPerSecond (113) } MaximumBitRate { ::= ENUMERATED (0), (1) ::= ENUMERATED (2) (0), (1), ::= ENUMERATED ) ::= INTEGER
::= INTEGER(0..65535) ::= INTEGER(0..255) ::= INTEGER(0..255)
::= OCTET STRING(SIZE (1..3)) ::= OCTET STRING(SIZE (2)) ::= ENUMERATED -- BS20 non-transparent -- BS20 non-transparent and transparent, -- BS30 multimedia -- BS30 multimedia -- BS30 transparent and multimedia -- BS20 non-transparent -- BS30 transparent and multimedia -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech
-- BS30 transparent and multimedia
Issue 07 (2007-10-10)
A-175
A CDR Format
mBR14400BitsPerSecond (1), mBR28800BitsPerSecond (2), mBR32000BitsPerSecond (3), mBR33600BitsPerSecond (4), mBR56000BitsPerSecond (5), mBR57600BitsPerSecond (6), mBR64000BitsPerSecond (7), mBR12200BitsPerSecond (106), mBR10200BitsPerSecond (107), mBR7950BitsPerSecond (108), mBR7400BitsPerSecond (109), mBR6700BitsPerSecond (110), mBR5900BitsPerSecond (111), mBR5150BitsPerSecond (112), mBR4750BitsPerSecond (113) } -- BS20 non-transparent
-- BS20 non-transparent and transparent, -- BS30 multimedia -- BS30 multimedia -- BS30 transparent and multimedia -- BS20 non-transparent -- BS30 transparent and multimedia -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech -- AMR speech
-- BS30 transparent and multimedia
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
-- 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 [35].
ISDN-BC
::= OCTET STRING
-- 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 [35]. ModemType { none-modem modem-v21 modem-v22 modem-v22-bis modem-v23 modem-v26-ter modem-v32 modem-undef-interface modem-autobauding1 no-other-modem-type modem-v34 } UssdCodingScheme UssdString ::= OCTET STRING ::= OCTET STRING (0), (1), (2), (3), (4), (5), (6), (7), (8), (31), (33) ::= ENUMERATED
A-176
Issue 07 (2007-10-10)

UssdNotifyCounter UssdRequestCounter Classmark3 ::= INTEGER(0..255) ::= INTEGER(0..255) ::= OCTET STRING(SIZE(2))
A CDR Format
OptimalRoutingDestAddress ::= BCDDirectoryNumber GAI --such as 64 F0 00 00 ABCD 1234 ChangeOfglobalAreaID { location changeTime } InteractionWithIP RouteAttribute { cas (0), tup isup pra bicc sip } VoiceIndicator ::= { sendToneByLocalMsc (0) , sendToneByOtherMsc (1), voiceNoIndication (3) } BCategory ::= { subscriberFree subscriberBusy } CallType { unknown internal incoming outgoing tandem } (0), (1), (2), (3), (4) ::= ENUMERATED (0), (1), ENUMERATED ENUMERATED (1), (2), (3), (4), (5), ::= ENUMERATED ::= NULL [0] GAI, [1] TimeStamp ::= SEQUENCE ::= OCTET STRING(SIZE(7))
others (255)
subscriberNoIndication (3)
END
Issue 07 (2007-10-10)
A-177
A CDR Format
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 A-7 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
A-178
Issue 07 (2007-10-10)
A CDR Format
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: orgMSCId: 08 0A globalAreaID: 64 F0 23 25 12 00 00 00 07
subscriberCategory: Common(A) firstmccmnc: 64F023 lastmccmnc: 64F023
MTC Record
ASN.1 BER Code (Example--mtCallRecord.dat) Figure A-8 Example--mtCallRecord.dat
Decoding (Example--mtCallRecord.txt) record no.: 0 recordType: mtCallRecord servedIMSI: 460077690000042
Issue 07 (2007-10-10)
A-179
A CDR Format
servedIMEI: 350654670244160 servedMSISDN: (91)8613907520027 callingNumber: (A1)13907520369 recordingEntity: (91)8613900022 mscIncomingROUTE: RNC mscOutgoingROUTE: RNC location: LAC-2512. CellID-0000 basicService: teleService(11) supplServicesUsed: {ssTime: 040806200130. ssCode: clip(11). } msClassmark: 1F034F answerTime: 040806200130 releaseTime: 040806200147 callDuration: 17 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 02 additionalChgInfo: chargeIndicator-charge networkcallReference: 5800A40800AA mSCAddress: (91)8613900022 systemType: iuUTRAN chargedParty: calledParty roamingNumber: (A1)13900022064 orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 F0 23 25 12 00 00 00 07
A.8.2 VP Call
MOC record Key field: Rate Indication: Fixed Network User Rate: H.223 & H.245 such as 64K (optional)
A-180
Issue 07 (2007-10-10)
A CDR Format
Transparency Indicator:
such as transparent (optional)
ASN.1 BER Code (ExamplemoCallRecord(VP).dat) Figure A-9 ExamplemoCallRecord(VP).dat
Decoding (ExamplemoCallRecord(VP).txt) record no.: 0 recordType: moCallRecord servedIMSI: 460077552000547 servedIMEI: 352711002055010 servedMSISDN: (91)8613907550547 callingNumber: (A1)13907550547 calledNumber: (81)13907550548 roamingNumber: (A1)13900444028 recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: To RNC-9 location: LAC-2512. CellID-0000 basicService: bearerService(1F) transparencyIndicator: transparent supplServicesUsed: {ssTime: 040723153416. ssCode: clir(12). } msClassmark: 1F034F answerTime: 040723153416 releaseTime: 040723153442 callDuration: 26 causeForTerm: normalRelease
Issue 07 (2007-10-10)
A-181
A CDR Format
diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 06 additionalChgInfo: chargeIndicator-charge networkcallReference: 00005802B444 mSCAddress: (91)8613900444 fnur: fnur64000BitsPerSecond systemType: iuUTRAN rateIndication: H.223 & H.245(7) chargedParty: callingParty orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
A.8.3 Other Bear Service Call

MOC record Basic service: service in GSM data service Fixed Network User Rate: Air Interface User Rate Requested: Rate Indication: Transparency Indicator: Modem type: Maximum bit rate: Guaranteed bit rate: such as 64K such as 56K such as V.110, I.460/X.30 such as non transparent such as modem-autobauding1 such as 64000BitsPerSecond such as 64000BitsPerSecond 0x17 or 0x1F in UMTS data Other service code
ASN.1 BER Code (ExamplemoCallRecord(BS).dat)
A-182
Issue 07 (2007-10-10)
A CDR Format
Figure A-10 ExamplemoCallRecord(BS).dat
Decoding (ExamplemoCallRecord(BS).txt) record no.: 0 recordType: moCallRecord servedIMSI: 460077552000547 servedIMEI: 352711002055010 servedMSISDN: (91)8613907550547 callingNumber: (A1)13907550547 calledNumber: (81)13907550548 roamingNumber: (A1)13900444028 recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: To RNC-9 location: LAC-2512. CellID-0000 basicService: bearerService(17) transparencyIndicator: not transparent supplServicesUsed: {ssTime: 040723153416. ssCode: clir(12). } msClassmark: 1F034F answerTime: 040723153416 releaseTime: 040723153442 callDuration: 26 causeForTerm: normalRelease diagnostics: gsm0408Cause(90)
Issue 07 (2007-10-10)
A-183
A CDR Format
callReference: 16 00 00 00 06 additionalChgInfo: chargeIndicator-charge networkcallReference: 00005802B444 mSCAddress: (91)8613900444 fnur: fnur64000BitsPerSecond systemType: iuUTRAN rateIndication: V.110, I.460/X.30(1) chargedParty: callingParty orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
A.8.4 Forwarding Record

Forwarding record ASN.1 BER Code (ExampleforwardCallRecord(cfnry).dat) Figure A-11 ExampleforwardCallRecord(cfnry).dat
Decoding (ExampleforwardCallRecord(cfnry).txt) record no.: 0 recordType: forwardCallRecord servedIMSI: 460077552000395
A-184
Issue 07 (2007-10-10)
A CDR Format
servedIMEI: 352711006979220 servedMSISDN: (91)13907520395 callingNumber: (91)13907520395 calledNumber: (A1)13907520369 connectedNumber: (91)7556660066 roamingNumber: (A1)13900022024 recordingEntity: (91)8613900022 mscIncomingROUTE: SX_MSRV mscOutgoingROUTE: RNC location: LAC-2512. CellID-0000 basicService: teleService(11) supplServicesUsed: {ssTime: 040818102805. ssCode: clip(11). }{ssTime: 040818102805. ssCode: cfnry(2A). } msClassmark: 1F0357 answerTime: 040818102805 releaseTime: 040818102821 callDuration: 16 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 04 additionalChgInfo: chargeIndicator-charge networkcallReference: 00 00 58 00 82 08 mSCAddress: (91)8613900022 systemType: iuUTRAN chargedParty: callingParty originalCalledNumber: (A1)13907520395 orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 60 54 25 12 00 00 00 07
subscriberCategory: Common(A) firstmccmnc: 646054 lastmccmnc: 646054
Issue 07 (2007-10-10)
A-185
A CDR Format
A.8.5 Emergency Record

Emergency call MOC record ASN.1 BER Code (ExamplemoCallRecord(EmergencyCallWithoutSIM).dat) Figure A-12 ExamplemoCallRecord(EmergencyCallWithoutSIM).dat
Decoding (ExamplemoCallRecord(EmergencyCallWithoutSIM).txt) record no.: 0 recordType: moCallRecord servedIMEI: 350654670244080 servedMSISDN: (80)350654670244080 calledNumber: (81)112 translatedNumber: (C1)6660001 recordingEntity: (91)8613900555 mscIncomingROUTE: RNC mscOutgoingROUTE: toPSTN location: LAC-2513. CellID-0001 basicService: teleService(12) msClassmark: 1F034F answerTime: 040724104735 releaseTime: 040724104752 callDuration: 17 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 1F 00 00 00 0F additionalChgInfo: chargeIndicator-charge
A-186
Issue 07 (2007-10-10)
A CDR Format
networkcallReference: 00007C018B66 mSCAddress: (91)8613900555 systemType: iuUTRAN chargedParty: callingParty mscOutgoingCircuit: 8 orgRNCorBSCId: 00 06
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 (ExamplemoCallRecord(partial1).dat) Figure A-13 ExamplemoCallRecord(partial1).dat
Decoding (ExamplemoCallRecord(partial1).txt) record no.: 0 recordType: moCallRecord
Issue 07 (2007-10-10)
A-187
A CDR Format
servedIMSI: 460077552000548 servedIMEI: 352711000794240 servedMSISDN: (91)8613907550548 callingNumber: (A1)13907550548 calledNumber: (81)13907550547 roamingNumber: (A1)13900333019 recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: NoName location: LAC-2512. CellID-0000 basicService: teleService(11) msClassmark: 1F034F answerTime: 040723170545 releaseTime: 040723171045 callDuration: 300 causeForTerm: partialRecord diagnostics: gsm0408Cause(9F) callReference: 16 00 00 00 0F sequenceNumber: 1 additionalChgInfo: chargeIndicator-charge networkcallReference: 000058084044 mSCAddress: (91)8613900444 systemType: iuUTRAN partialRecordType: timeLimit chargedParty: callingParty mscOutgoingCircuit: 0 orgRNCorBSCId: orgMSCId: 44 0B subscriberCategory: Common(A) firstmccmnc: 64F008 lastmccmnc: 64F008 00 09
Partial Record2
ASN.1 BER Code (ExamplemoCallRecord(partial2).dat)
A-188
Issue 07 (2007-10-10)
A CDR Format
Figure A-14 ExamplemoCallRecord(partial2).dat
Decoding (ExamplemoCallRecord(partial2).txt) record no.: 0 recordType: moCallRecord servedIMSI: 460077552000548 servedIMEI: 352711000794240 servedMSISDN: (91)8613907550548 callingNumber: (A1)13907550548 calledNumber: (81)13907550547 roamingNumber: (A1)13900333019 recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: NoName location: LAC-2512. CellID-0000 basicService: teleService(11) msClassmark: 1F034F answerTime: 040723171045 releaseTime: 040723171545 callDuration: 300 causeForTerm: partialRecord diagnostics: gsm0408Cause(9F) callReference: 16 00 00 00 0F sequenceNumber: 2 additionalChgInfo: chargeIndicator-charge
Issue 07 (2007-10-10)
A-189
A CDR Format
networkcallReference: 000058084044 mSCAddress: (91)8613900444 systemType: iuUTRAN partialRecordType: timeLimit chargedParty: callingParty mscOutgoingCircuit: 0 orgRNCorBSCId: orgMSCId: 44 0B subscriberCategory: Common(A) firstmccmnc: 64F008 lastmccmnc: 64F008 00 09
Partial Record3
ASN.1 BER Code (ExamplemoCallRecord(partial3).dat) Figure A-15 ExamplemoCallRecord(partial3).dat
Decoding (ExamplemoCallRecord(partial3).txt) record no.: 0 recordType: moCallRecord servedIMSI: 460077552000548 servedIMEI: 352711000794240 servedMSISDN: (91)8613907550548 callingNumber: (A1)13907550548 calledNumber: (81)13907550547 roamingNumber: (A1)13900333019
A-190
Issue 07 (2007-10-10)
A CDR Format
recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: NoName location: LAC-2512. CellID-0000 basicService: teleService(11) msClassmark: 1F034F answerTime: 040723171545 releaseTime: 040723172030 callDuration: 285 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 0F sequenceNumber: 3 additionalChgInfo: chargeIndicator-charge networkcallReference: 000058084044 mSCAddress: (91)8613900444 systemType: iuUTRAN chargedParty: callingParty mscOutgoingCircuit: 0 orgRNCorBSCId: orgMSCId: 44 0B subscriberCategory: Common(A) firstmccmnc: 64F008 lastmccmnc: 64F008 00 09
A.8.7 SMS
SMS MOC Record
ASN.1 BER Code (ExamplemoSMSRecord.dat)
Issue 07 (2007-10-10)
A-191
A CDR Format
Figure A-16 ExamplemoSMSRecord.dat
Decoding (ExamplemoSMSRecord.txt) record no.: 0 recordType: moSMSRecord servedIMSI: 460881104002797 servedIMEI: 350654670244080 servedMSISDN: (91)8613907521002 msClassmark: 4F1880 serviceCentre: (91)8613900007555 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 messageReference: 60 originationTime: 040723173725 destinationNumber: (81)13907550548 systemType: iuUTRAN basicService: teleService(22) additionalChgInfo: chargeIndicator-charge chargedParty: callingParty orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
subscriberCategory: Common(A) firstmccmnc: 64F008 smsUserDataType: FF
A-192
Issue 07 (2007-10-10)
A CDR Format
SMS MTC Record

ASN.1 BER Code (ExamplemtSMSRecord.dat) Figure A-17 ExamplemtSMSRecord.dat
Decoding (ExamplemtSMSRecord.txt) record no.: 0 recordType: mtSMSRecord serviceCentre: (91)8613900007555 servedIMSI: 460077552000548 servedIMEI: 352711000794240 servedMSISDN: (91)8613907550548 msClassmark: 4F1880 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 deliveryTime: 040723173935 systemType: iuUTRAN basicService: teleService(21) additionalChgInfo: chargeIndicator-charge chargedParty: calledParty orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
subscriberCategory: Common(A) firstmccmnc: 64F008 smsUserDataType: FF origination number: (91)8613907521002
Issue 07 (2007-10-10)
A-193
A CDR Format
A.8.8 Concatenated Long SMS

SMS MOC record ASN.1 BER Code

Example1moSMSRecord(partial1).dat Example1moSMSRecord(partial2).dat Example1moSMSRecord(partial3).dat
Figure A-18 Example1moSMSRecord(partial1).dat
A-194
Issue 07 (2007-10-10)
A CDR Format
Decoding

Example1moSMSRecord(partial1).txt Example1moSMSRecord(partial2).txt Example1moSMSRecord(partial3).txt
record no.: 0 recordType: moSMSRecord servedIMSI: 460881104002797 servedIMEI: 350654670244080 servedMSISDN: (91)8613907521002 msClassmark: 4F1880 serviceCentre: (91)8613900007555 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 messageReference: 62 originationTime: 040723174602 destinationNumber: (81)13907550548 systemType: iuUTRAN basicService: teleService(22) additionalChgInfo: chargeIndicator-charge chargedParty: callingParty orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
subscriberCategory: Common(A) firstmccmnc: 64F008 smsUserDataType: FF maximumNumberOfSMSInTheConcatenatedSMS: 3 concatenatedSMSReferenceNumber: 17 sequenceNumberOfTheCurrentSMS: 1
record no.: 0 recordType: moSMSRecord servedIMSI: 460881104002797 servedIMEI: 350654670244080
Issue 07 (2007-10-10)
A-195
A CDR Format
servedMSISDN: (91)8613907521002 msClassmark: 4F1880 serviceCentre: (91)8613900007555 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 messageReference: 63 originationTime: 040723174611 destinationNumber: (81)13907550548 systemType: iuUTRAN basicService: teleService(22) additionalChgInfo: chargeIndicator-charge chargedParty: callingParty orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
record no.: 0 recordType: moSMSRecord servedIMSI: 460881104002797 servedIMEI: 350654670244080 servedMSISDN: (91)8613907521002 msClassmark: 4F1880 serviceCentre: (91)8613900007555 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 messageReference: 64 originationTime: 040723174618
A-196
Issue 07 (2007-10-10)
A CDR Format
destinationNumber: (81)13907550548 systemType: iuUTRAN basicService: teleService(22) additionalChgInfo: chargeIndicator-charge chargedParty: callingParty orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
A.8.9 Interrogation
ASN.1 BER Code (ExamplehlrRecord.dat) Figure A-21 ExamplehlrRecord.dat
Decoding (ExamplehlrRecord.txt) record no.: 0 recordType: hlrIntRecord servedIMSI: 460077552000369 servedMSISDN: (91)8613907520369 recordingEntity: (91)8613900022 routingNumber: (91)8613900022020 interrogationTime: 040818101614 orgMSCId: 08 0A
Issue 07 (2007-10-10)
A-197
A CDR Format
A.8.10 USSD
ASN.1 BER Code (ExamplessActionRecord(USSD).dat) Figure A-22 ExamplessActionRecord(USSD).dat
Decoding (ExamplessActionRecord(USSD).txt) record no.: 0 recordType: ssActionRecord servedIMSI: 460077552000369 servedIMEI: 350654670244270 servedMSISDN: (91)8613907520369 msClassmark: 4F1880 recordingEntity: (91)8613900022 location: LAC-2512. CellID-0000 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 additionalChgInfo: chargeIndicator-charge chargedParty: callingParty subscriberCategory: Common(A)
A-198
Issue 07 (2007-10-10)
A CDR Format
firstmccmnc: 646054 orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 60 54 25 12 00 00 00 07
A.8.11 Supplementary Service

Forward Registration
ASN.1 BER Code (ExamplessActionRecord(forward registration).dat) Figure A-23 ExamplessActionRecord(forward registration).dat
Decoding (ExamplessActionRecord(forward registration).txt) record no.: 0 recordType: ssActionRecord servedIMSI: 460077552000548 servedIMEI: 352711000794240 servedMSISDN: (91)8613907550548 msClassmark: 4F1880 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 basicServices: {teleService(10)} supplService: cfb(29) ssAction: registration(0) ssActionTime: 040723180429 ssParameters: {forwardedToNumber-(91)867556660001} callReference: 16 00 00 00 21 systemType: iuUTRAN
Issue 07 (2007-10-10)
A-199
A CDR Format
ussdString: { 91 68 57 65 66 00 10} additionalChgInfo: chargeIndicator-charge chargedParty: callingParty subscriberCategory: Common(A) firstmccmnc: 64F008 orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
BAOC Activation
ASN.1 BER Code (ExamplessActionRecord(BAOC activation).dat) Figure A-24 ExamplessActionRecord(BAOC activation).dat
Decoding (ExamplessActionRecord(BAOC activation).txt) record no.: 0 recordType: ssActionRecord servedIMSI: 460077552000548 servedIMEI: 352711000794240 servedMSISDN: (91)8613907550548 msClassmark: 4F1880 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 supplService: baoc(92) ssAction: activation(2) ssActionTime: 040723180748 callReference: 16 00 00 00 25 systemType: iuUTRAN
A-200
Issue 07 (2007-10-10)
A CDR Format
additionalChgInfo: chargeIndicator-charge chargedParty: callingParty subscriberCategory: Common(A) firstmccmnc: 64F008 orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
BAOC Deactivation
ASN.1 BER Code (ExamplessActionRecord(BAOC deactivation).dat) Figure A-25 ExamplessActionRecord(BAOC deactivation).dat
Decoding (ExamplessActionRecord(BAOC deactivation).txt) record no.: 0 recordType: ssActionRecord servedIMSI: 460077552000548 servedIMEI: 352711000794240 servedMSISDN: (91)8613907550548 msClassmark: 4F1880 recordingEntity: (91)8613900444 location: LAC-2512. CellID-0000 supplService: barringOfOutgoingCalls(91) ssAction: deactivation(3) ssActionTime: 040723181157 callReference: 16 00 00 00 29 systemType: iuUTRAN additionalChgInfo: chargeIndicator-charge
Issue 07 (2007-10-10)
A-201
A CDR Format
chargedParty: callingParty subscriberCategory: Common(A) firstmccmnc: 64F008 orgRNCorBSCId: orgMSCId: 44 0B globalAreaID: 64 F0 08 25 12 00 00 00 09
A.8.12 Handover
MOC record
ASN.1 BER Code (ExamplemoCallRecord(Handover).dat) Figure A-26 ExamplemoCallRecord(Handover).dat
Decoding (ExamplemoCallRecord(Handover).txt) record no.: 1 recordType: moCallRecord servedIMSI: 460077552000369 servedIMEI: 350654670244270 servedMSISDN: (91)8613907520369 callingNumber: (91)8613907520369 calledNumber: (81)6660066 recordingEntity: (91)8613900022 mscIncomingROUTE: RNC mscOutgoingROUTE: B-SWITCH
A-202
Issue 07 (2007-10-10)
A CDR Format
location: LAC-2512. CellID-0000 changeOfLocation: {changeTime: 040814191301. location: LAC-2513. CellID-FFFF.} basicService: teleService(11) supplServicesUsed: {ssTime: 040814191214. ssCode: hold(42). }{ssTime: 040814191307. ssCode: hold(42). } msClassmark: 1F034F answerTime: 040814191147 releaseTime: 040814191315 callDuration: 88 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 05 additionalChgInfo: chargeIndicator-charge networkcallReference: 00 00 58 02 93 08 mSCAddress: (91)8613900022 systemType: iuUTRAN chargedParty: callingParty mscOutgoingCircuit: 2 orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 F0 23 25 12 00 00 64 F0 23 25 13 FF FF.} 00 07
changeOfGlobalAreaID: {changeTime: 040814191301. location: subscriberCategory: Common(A) firstmccmnc: 64F023 lastmccmnc: 64F023
A.8.13 CommonEquipRecord
ASN.1 BER Code (ExamplecommonEquipRecord.dat)
Issue 07 (2007-10-10)
A-203
A CDR Format
Figure A-27 ExamplecommonEquipRecord.dat
Decoding (ExamplecommonEquipRecord.txt) record no.: 0 recordType: commonEquipRecord equipmentType: conferenceBridge equipmentId: 1F71 servedIMSI: 460077552000369 servedMSISDN: (91)8613907520369 recordingEntity: (91)8613900022 basicService: teleService(11) supplServicesUsed: {ssTime: 040817110011. ssCode: multiPTY(51). } seizureTime: 040817110011 releaseTime: 040817110022 callDuration: 11 callReference: 00 00 7C 0E 23 0A 08 FF systemType: iuUTRAN causeForTerm: normalRelease diagnostics: gsm0408Cause(90) servedIMEI: 350654670244270 orgRNCorBSCId: orgMSCId: 08 0A subscriberCategory: Common(A) 00 07
A.8.14 IncGatewayRecord
ASN.1 BER Code (ExampleincGatewayRecord.dat)
A-204
Issue 07 (2007-10-10)
A CDR Format
Figure A-28 ExampleincGatewayRecord.dat
Decoding
(ExampleincGatewayRecord.txt)
record no.: 0 recordType: incGatewayRecord callingNumber: (A1)07556660066 calledNumber: (A1)13907520369 recordingEntity: (91)8613900022 mscIncomingROUTE: B-SWITCH mscOutgoingROUTE: RNC answerTime: 040817104736 releaseTime: 040817104749 callDuration: 13 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 1C basicService: teleService(11) additionalChgInfo: chargeIndicator-charge roamingNumber: (A1)13900022078 mscIncomingCircuit: 1F orgMSCId: 08 0A
A.8.15 OutGatewayRecord
ASN.1 BER Code (ExampleoutGatewayRecord.dat)
Issue 07 (2007-10-10)
A-205
A CDR Format
Figure A-29 ExampleoutGatewayRecord.dat
Decoding (ExampleoutGatewayRecord.txt) record no.: 0 recordType: outGatewayRecord callingNumber: (91)8613907520369 calledNumber: (81)6660066 recordingEntity: (91)8613900022 mscIncomingROUTE: RNC mscOutgoingROUTE: B-SWITCH answerTime: 040817104456 releaseTime: 040817104505 callDuration: 9 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 1B basicService: teleService(11) additionalChgInfo: chargeIndicator-charge mscOutgoingCircuit: 6 orgMSCId: 08 0A
A.8.16 TransitCallRecord
ASN.1 BER Code (ExampletransitCallRecord.dat)
A-206
Issue 07 (2007-10-10)
A CDR Format
Figure A-30 ExampletransitCallRecord.dat
Decoding (ExampletransitCallRecord.txt) record no.: 0 recordType: transitCallRecord recordingEntity: (91)8613900168 mscIncomingROUTE: New-MSIG1 mscOutgoingROUTE: NoName callingNumber: (A1)13907520018 calledNumber: (81)6660000 answerTimestamp: 040807160431 releaseTimestamp: 040807160435 callDuration: 4 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 58 additionalChgInfo: chargeIndicator-charge mscOutgoingCircuit: 4 mscIncomingCircuit: 12 orgMSCId: 08 0A
A.8.17 RoamingRecord
ASN.1 BER Code (ExampleroamingRecord.dat)
Issue 07 (2007-10-10)
A-207
A CDR Format
Figure A-31 ExampleroamingRecord.dat
Decoding (ExampleroamingRecord.txt) record no.: 0 recordType: roamingRecord servedIMSI: 460077552000547 servedMSISDN: (91)8613907550547 callingNumber: (A1)13907521002 roamingNumber: (A1)13900333040 recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: NoName basicService: teleService(11) supplServicesUsed: {ssTime: 040724113312. ssCode: clip(11). } answerTime: 040724113312 releaseTime: 040724113324 callDuration: 12 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 2E networkcallReference: 0000580DFF44 mSCAddress: (91)8613900444 additionalChgInfo: chargeIndicator-charge chargedParty: calledParty mscOutgoingCircuit: 0
A-208
Issue 07 (2007-10-10)
A CDR Format
A.8.18 Moc(CAMEL)
ASN.1 BER Code (ExamplemoCallRecord(camel).dat) Figure A-32 ExamplemoCallRecord(camel).dat
Decoding (ExamplemoCallRecord(camel).txt) record no.: 0 recordType: moCallRecord servedIMSI: 460077552000369 servedIMEI: 350654670244270 servedMSISDN: (91)8613907520369 callingNumber: (91)8613907520369 calledNumber: (81)13907520394 roamingNumber: (A1)13900022077 recordingEntity: (91)8613900022 mscIncomingROUTE: RNC mscOutgoingROUTE: RNC location: LAC-2512. CellID-0000 basicService: teleService(11) msClassmark: 1F034F answerTime: 040817101048 releaseTime: 040817101113 callDuration: 25 causeForTerm: normalRelease diagnostics: gsm0408Cause(90)
Issue 07 (2007-10-10)
A-209
A CDR Format
callReference: 16 00 00 00 19 additionalChgInfo: chargeIndicator-charge gsm_SCFAddress: (91)8613900128 serviceKey: 3 networkcallReference: 00 00 58 04 21 08 mSCAddress: (91)8613900022 numberOfDPEncountered: 2 levelOfCAMELService: callDurationSupervision freeFormatData: 800130 systemType: iuUTRAN chargedParty: callingParty orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 60 54 25 12 00 00 00 07
A.8.19 Mtc(CAMEL)
ASN.1 BER Code (ExamplemtCallRecord(camel).dat) Figure A-33 ExamplemtCallRecord(camel).dat
Decoding (ExamplemtCallRecord(camel).txt) record no.: 0
A-210
Issue 07 (2007-10-10)
A CDR Format
recordType: mtCallRecord servedIMSI: 460077552000369 servedIMEI: 350654670244270 servedMSISDN: (91)8613907520369 callingNumber: (91)8613907520395 recordingEntity: (91)8613900022 mscIncomingROUTE: RNC mscOutgoingROUTE: RNC location: LAC-2512. CellID-0000 basicService: teleService(11) supplServicesUsed: {ssTime: 040817093835. ssCode: clip(11). } msClassmark: 1F034F answerTime: 040817093835 releaseTime: 040817093925 callDuration: 50 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 16 additionalChgInfo: chargeIndicator-charge gsm_SCFAddress: (91)8613900128 serviceKey: 3 networkcallReference: 00 00 58 03 DE 08 mSCAddress: (91)8613900022 systemType: iuUTRAN chargedParty: calledParty freeFormatData: 800130 numberOfDPEncountered: 2 roamingNumber: (A1)13900022072 orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 60 54 25 12 00 00 00 07
subscriberCategory: Common(A) firstmccmnc: 646054
Issue 07 (2007-10-10)
A-211
A CDR Format
lastmccmnc: 646054
A.8.20 TCAMEL
ASN.1 BER Code (ExampletermCAMELRecord.dat) Figure A-34 ExampletermCAMELRecord.dat
Decoding (ExampletermCAMELRecord.txt) record no.: 0 recordType: termCAMELRecord servedIMSI: 460077552000369 servedMSISDN: (91)8613907520369 recordingEntity: (91)8613900022 interrogationTime: 040817092812 gsm_SCFAddress: (91)8613900128 serviceKey: 3 networkcallReference: 00 00 58 03 BD 08 mSCAddress: (91)8613900022 calledNumber: (A1)13907520369 callingNumber: (91)8613907520395 mscIncomingROUTE: RNC mscOutgoingROUTE: RNC answerTime: 040817092826 releaseTime: 040817092843 callDuration: 17 causeForTerm: normalRelease diagnostics: gsm0408Cause(90)
A-212
Issue 07 (2007-10-10)
A CDR Format
callReference: 16 00 00 00 14 levelOfCAMELService: callDurationSupervision basicService: teleService(11) additionalChgInfo: chargeIndicator-charge orgMSCId: 08 0A subscriberCategory: Common(A) chargedParty: calledParty
A.8.21 Moc(FCI)
ASN.1 BER Code (Examplemoc(withFCI).dat) Figure A-35 Examplemoc(withFCI).dat
Decoding (Examplemoc(withFCI).txt) record no.: 0 recordType: moCallRecord servedIMSI: 460077552000369 servedIMEI: 350654670244270 servedMSISDN: (91)8613907520369 callingNumber: (91)8613907520369 calledNumber: (81)13907520394 roamingNumber: (A1)13900022077 recordingEntity: (91)8613900022 mscIncomingROUTE: RNC mscOutgoingROUTE: RNC location: LAC-2512. CellID-0000
Issue 07 (2007-10-10)
A-213
A CDR Format
basicService: teleService(11) msClassmark: 1F034F answerTime: 040817101048 releaseTime: 040817101113 callDuration: 25 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 19 additionalChgInfo: chargeIndicator-charge gsm_SCFAddress: (91)8613900128 serviceKey: 3 networkcallReference: 00 00 58 04 21 08 mSCAddress: (91)8613900022 numberOfDPEncountered: 2 levelOfCAMELService: callDurationSupervision freeFormatData: 800130 systemType: iuUTRAN chargedParty: callingParty orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 60 54 25 12 00 00 00 07
A.8.22 Moc(hotbilling)
ASN.1 BER Code (ExamplemoCallRecord(hot).dat)
A-214
Issue 07 (2007-10-10)
A CDR Format
Figure A-36 ExamplemoCallRecord(hot).dat
Decoding (ExamplemoCallRecord(hot).txt) record no.: 0 recordType: moCallRecord servedIMSI: 460077552000369 servedIMEI: 350654670244270 servedMSISDN: (91)8613907520369 callingNumber: (91)8613907520369 calledNumber: (81)13907520395 roamingNumber: (A1)13900022026 recordingEntity: (91)8613900022 mscIncomingROUTE: RNC mscOutgoingROUTE: RNC location: LAC-2512. CellID-0000 basicService: teleService(11) msClassmark: 1F034F answerTime: 040818105543 releaseTime: 040818105557 callDuration: 14 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 05 additionalChgInfo: chargeIndicator-charge networkcallReference: 00 00 58 00 E4 08
Issue 07 (2007-10-10)
A-215
A CDR Format
mSCAddress: (91)8613900022 systemType: iuUTRAN chargedParty: callingParty orgRNCorBSCId: orgMSCId: 08 0A globalAreaID: 64 60 54 25 12 00 00 00 07
subscriberCategory: Common(A) firstmccmnc: 646054 lastmccmnc: 646054 hotBillingTag: true
A.8.23 SS_PLMN_SPECIFICSS1 record

ASN.1 BER Code (Examplemoc(SS_PLMN_SPECIFCSS1).dat) Figure A-37 Examplemoc(SS_PLMN_SPECIFCSS1).dat
Decoding (Examplemoc(SS_PLMN_SPECIFCSS1).txt) recordType: moCallRecord servedIMSI: 460881104002798 servedIMEI: 350989100621290 servedMSISDN: (91)8613907521001 callingNumber: (91)8613907521001 calledNumber: (81)6660032 recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: IsupIO location: LAC-FFFF. CellID-0000
A-216
Issue 07 (2007-10-10)
A CDR Format
basicService: teleService(11) supplServicesUsed: {ssTime: 040315112525. ssCode: SS_PLMN_SPECIFICSS1(F1). } msClassmark: 571881 answerTime: 040315112506 releaseTime: 040315112630 callDuration: 84 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 4D additionalChgInfo: chargeIndicator-charge 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 (Examplemoc(SS_PLMN_SPECIFCSS3).dat) Figure A-38 Examplemoc(SS_PLMN_SPECIFCSS3).dat
Decoding (Examplemoc(SS_PLMN_SPECIFCSS3).txt) recordType: moCallRecord servedIMSI: 460881104002798 servedIMEI: 350989100621290
Issue 07 (2007-10-10)
A-217
A CDR Format
servedMSISDN: (91)8613907521001 callingNumber: (91)8613907521001 calledNumber: (81)6660032 recordingEntity: (91)8613900444 mscIncomingROUTE: To RNC-9 mscOutgoingROUTE: IsupIO location: LAC-FFFF. CellID-0000 basicService: teleService(11) supplServicesUsed: {ssTime: 040315112651. ssCode: SS_PLMN_SPECIFICSS3(F3). } msClassmark: 571881 answerTime: 040315112646 releaseTime: 040315112677 callDuration: 31 causeForTerm: normalRelease diagnostics: gsm0408Cause(90) callReference: 16 00 00 00 4D additionalChgInfo: chargeIndicator-charge 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 (ExamplelcsMOrecord.dat)
A-218
Issue 07 (2007-10-10)
A CDR Format
Figure A-39 ExamplelcsMOrecord.dat
Decoding (ExamplelcsMOrecord.txt) record no.: 0 recordType: moLCSRecord recordingEntity: (91)8613400300 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 location: LAC-0280. CellID-0000 locationEstimate: 02 00 00 00 00 00 FF 80 00 80 positioningData: 00 systemType: iuUTRAN causeForTerm: normalRelease additionalChgInfo: chargeIndicator-charge subscriberCategory: Common(A) firstmccmnc: 64F040 orgRNCorBSCId: 08 09
orgMSCId: 01 1E 01 hotBillingTag: true
Issue 07 (2007-10-10)
A-219
A CDR Format
A.8.26 MT-LCS
ASN.1 BER Code (ExamplelcsMTrecord.dat) Figure A-40 ExamplelcsMTrecord.dat
Decoding (ExamplelcsMTrecord.txt) record no.: 0 recordType: mtLCSRecord recordingEntity: (91)8613400300 lcsClientType: valueAddedServices lcsClientIdentity: lcsClientExternalID/externalAddress-(91)861340030800 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 eventTimeStamp: 040719201158 measureDuration: 3 notificationToMSUser: locationNotAllowed privacyOverride: 0 location: LAC-0280. CellID-0000 locationEstimate: 02 00 00 00 00 00 FF 80 00 80 positioningData: 00 systemType: iuUTRAN causeForTerm: normalRelease
A-220
Issue 07 (2007-10-10)
A CDR Format
additionalChgInfo: chargeIndicator-charge subscriberCategory: Common(A) firstmccmnc: 64F040 orgRNCorBSCId: 08 09
A.8.27 NI-LCS
ASN.1 BER Code (ExamplelcsNIrecord.dat) Figure A-41 ExamplelcsNIrecord.dat
Decoding (ExamplelcsNIrecord.txt) record no.: 0 recordType: niLCSRecord recordingEntity: (91)8613400300 lcsClientType: emergencyServices lcsClientIdentity: lcsClientExternalID/externalAddress-(91)861340030800 servedIMSI: 460043004300056 servedMSISDN: (91)8613403000056 servedIMEI: 004400003779020 lcsPriority: 1 mlc_Number: (91)8613400308 eventTimeStamp: 040719201344 measureDuration: 2 location: LAC-0280. CellID-0000 locationEstimate: 02 00 00 00 00 00 FF 80 00 80 positioningData: 00
Issue 07 (2007-10-10)
A-221
A CDR Format
systemType: iuUTRAN causeForTerm: normalRelease additionalChgInfo: chargeIndicator-charge subscriberCategory: Common(A) firstmccmnc: 64F040 orgRNCorBSCId: 00 00
A-222
Issue 07 (2007-10-10)

CDR Format PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CDR Format PDF

Transféré par

Droits d'auteur :

Formats disponibles

HUAWEI iGateway Bill User Manual

Huawei Technologies Proprietary

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Huawei Technologies Proprietary

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

A.1 Acronyms and Abbreviations

B BCSM BSS Basic Call State Model Base Station System

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

L LAC Location Area Code

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Network Management Network Induced Location Request

P PLMN Public Land Mobile Network

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Visited Terminating CAMEL Subscription Information

A.2 ASN.1 (Basic Encoding Rules) Description

A.2.2 Coding of ASN.1 Tag

Single Octet Encoding for Tag Numbers from 0 to 30 (Inclusive).

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Use of a Leading Octet for Tag Numbers Bigger Than or Equal to 31

Subsequent octets are encoded as:

Only one subsequent octet is supported (Tag values<128).

A.2.3 Coding of Length

Short Length Encoding for Length from 0 to 127 (Inclusive)

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Long Length Encoding for Length > 127

A.2.4 Coding of Contents

A.2.5 Structure of Call Data Record

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Figure A-1 Structure of call data record

A.3 Charging Data Record Transfer

A.4 Record types

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

A.5 Record contents

A.5.1 Mobile Originated Call Attempt

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

0x89 0xAA 0xAB 0xAC

Change of Location Basic service Transparenc y Indicator

SEQUENCE OF ( 23 * n ) OCTET(3) ENUMERA TED (1)

Huawei Technologies Proprietary

HUAWEI iGateway Bill User Manual

Field Change Of Service Supp. Services

TYPE SEQUENCE OF ( (18..27) * n) SEQUENCE OF (16 * n)

AOC Parameters Change of AOC Para