B4.3.4.9 ZXWN CDR Asn.1 Format For Cs (v5.4.0)

ZTE CDR ASN.
1 Format for
ZXWN CS
ZTE CDR ASN.1 Format for ZXWN CS V5.2.0
ZTE CDR Format for ZXWN CS V5.4.0
About the Document

Old New
Date Content Remarks
Version Version
V3.0.0 11/09/2002 Created
Add “HotBillingTag” to MOC,

V3.0.0 V3.0.1 01/04/2005 MTC, MCF, MOE,SMS-MO,
SMS-MT CDRs
1. Modify error tag values

2. Change the length of
“TrunkGroup” from 2 bytes to 4
bytes
3. Add “pbrt”,”carp”,”CUGIndex”,
4. ”CUGOutcomingAccessUsed”
5. and “CUGOutcomingAccessInd”
to MOC and MCF
6. Add “pbrt” to Gate_in,Gate_out
and Transit CDRs
7. Add “carp” to MOE CDR
V3.0.1 V3.0.2 30/06/2005
8. Add “pbrt”,”carp”,”CUGIndex”,
9. ”CUGIncomingAccessUsed”
10. and “CUGIncomingAccessInd”
to MTC CDR
11. Modity the tag value to
HLR,MOE and MCF
12. to 11,12 and 13.Modify
recordtype value of hlr,moe and
mcf to 11,12 and 13
13. Add “redirectiongNumber” to
MTC CDR
Add “hotBillingTag2” to
MOC,MTC,MCF,MO,ROAM,
V3.0.2 V3.1.0 25/08/2005
SMS,LCSMO,LSCMT and LCSNI
for India Spice.
V3.1.0 V3.1.1 30/12/2005 Add definition of McdType
Modify the value of
V3.1.1 V3.1.2 12/09/2006
“RateIndication”
ZTE Confidential Proprietary I

Change the title of chapter 2 and

3.Change the number of chapter
V3.1.2 V3.1.3 25/10/2006
3.Delete “General” part and other
miscellaneous modifies.
1. Add VIG 、 USSD 、 MGCF
record
V3.1.3 V4.0.0 02/11/2006
2. Add hotbillingTag2 to SS, CEU,
TCI, HLR record
Change the document
template.Add the mapping
information of field name and
V4.0.0 V5.0.0 07/12/2006
ASN.1 name.Delete GMLC
records, which are dealed by
service product.
ZTE Confidential Proprietary II

1. Modify the tag value of

teleService and bearerService in
BasicServiceCode
2. Modify “Forward record type” to
“Forward type”.Modify the
description of it.
3. Add dDCFlag to
MOC/MTC/GATE/TRANSIT
record
4. Add
bSCIdentification/calledLocation
/
callingPartyRoamingInd/service
Category/TransactionIdentificatio
n/incomingCic/outgoingCic/msc
SPC/incomingTKGPName/outgo
ingTKGPName to MOC record
5. Add bSCIdentification/
6. TransactionIdentification/incomi
ngCic/OutgoingCic/mscSPC/inco
mingTKGPName/outgoingTKGP
Name to MOE record
7. Add bSCIdentification/
8. CalledLocation/callingPartyRoa
mingInd/serviceCategory/incomi
ngCic/outgoingCic/mscSPC/inco
mingTKGPName/outgoingTKGP
Name to MCF record
9. Add
terminatingRecordType/original
CalledNumber/callingLocation/b
SCIdentification/calledPartyRoa
V5.0.0 V5.1.0 11/05/2007 mingInd/serviceCategory/transac
tionIdentification/incomingCic/o
utgoingCic/mscSPC/incomingTK
GPName/outgoingTKGPName to
MTC record
10. Add
redirectNumber/bSCIdentificatio
n/serviceCategory/incomingCic/o
utgoingCic/mscSPC/incomingTK
GPName/outgoingTKGPName to
ROAM record
11. Add transactionIdentification to
SS record
12. Add
gatewayRecordType/roamingNu
mber/redirectNumber/incomingC
ic/outgoingCic/mscSPC/incomin
gTKGPName/outgoingTKGPNa
me /forwardCallIndicator to
GATE/TRANSIT record
13. Add
transactionIdentification/mscSPC
to SMSMO/SMSMT record
14. Add incomingCic/outgoingCic
/mscSPC
/incomingTKGPName
/outgoingTKGPName to
ZTE Confidential Proprietary III

1. Add
PartialRecordType,ServiceChang
eInitiator,ReasonForServiceChan
ge,TypeOfServiceChange to
MOC,MTC,MCF,GATEIN,GAT
EOUT record
2. Modify description of
cUGOutgoingAccessUsed and
cUGOutgoingAccessInd for
V5.1.0 V5.2.0 11/8/2007 MTC record
3. Modify tag value of
lcsClientExternalID for LCS
record
4. Add mscspc14 and mscspc24 to
SS record
5. Add “isdnBasicService” to
IncGatewayRecord and
OutGatewayRecord
1. Add SmsRefrenceNumber filed

to cAMELSMSInformation.
2. Add cAMELSMSInformation to
MTSMSRecord.
3. Modify the description of CUG
Category field of Mobile
Originated Call,Mobile
Terminated Call,Roaming
Call,Mobile Originated
CallForwarding Call
4. Modify callingPartyRoamingInd
and calledPartyRoamingInd to
BOOLEAN
5. Modify mscSPC14 to SPC14,
mscSPC24 to SPC24
6. Modify the tag of userType to 1
7. Modify the asn.1 description of
Cic to CICCode
V5.2.0 V5.3.0 06/02/2008 8. Modify recordExtensions to
ManagementExtensions,
causeForRecordClosing to
CauseForTerm of MGCFRecord
9. Modify the
LocationAreaAndCell’s sub-filed
rncID to OPTIONAL
10. Modify the asn.1 description of
CallEventRecordType,
sigMTPStatisticRecord to 41,
sigSCCPStatisticRecord to 42
11. Add local free special service to
service category.
12. Add falseAnswerCharge to
causeForTerm.
13. Modify the definition of spc14
and spc24
14. Modify the definition of
CICCode
ZTE Confidential Proprietary IV

1. Add transRoamingNumber to
ROAMRecord
2. Add packing of 7-bit characters
for MSISDN and
V5.3.0 V5.4.0 06/11/2008 originationNumber/destinationN
umber of SMS, Modify the tag
value definition of
positioningData and MOLR-
Type for LCS, Modify the ASN.1
description of BSCIdentification
10
Copyright © 2005 ZTE Corporation Shenzhen P. R. China
ZTE CONFIDENTIAL: This document contains proprietary information of ZTE Corporation and
is not to be disclosed or used except in accordance with applicable
agreements.
Due to update and improvement of ZTE products and technologies,

information of the document is subjected to change without notice.
ZTE Confidential Proprietary V

Table of Contents
1 GENERAL INFORMATION..................................................................................................................1
1.1 Abbreviation.......................................................................................................................................1
5 1.2 Structure of the CDR File...................................................................................................................2
1.2.1 Field...........................................................................................................................................2
1.2.2 Charging Data Record...............................................................................................................2
1.2.3 Block...........................................................................................................................................2
1.2.4 CDR File....................................................................................................................................2
10 1.3 CDR Encoding....................................................................................................................................2
1.3.1 ASN.1 (Basic Encoding Rules) description................................................................................2
1.3.2 Encoding of the Tag....................................................................................................................3
1.3.3 Encoding of the length...............................................................................................................4
1.3.4 Encoding of the content..............................................................................................................4
15 1.3.5 ASN.1 BER Encoding of Integers...............................................................................................5
1.3.6 Structure Diagrams of Charging Data Record..........................................................................5
2 DESCRIPTION OF CDRS......................................................................................................................6
2.1 Record Types......................................................................................................................................6
2.1.1 Mobile Originated Call..............................................................................................................6
20 2.1.2 Mobile Terminated Call............................................................................................................11
2.1.3 Roaming Call...........................................................................................................................15
2.1.4 Gateway Record.......................................................................................................................17
2.1.5 TRANSIT..................................................................................................................................20
2.1.6 SMS-MO...................................................................................................................................21
25 2.1.7 SMS-MT....................................................................................................................................22
2.1.8 SMS-MO-IW/GMSC.................................................................................................................23
2.1.9 SMS-MT-GW/GMSC................................................................................................................24
2.1.10 Supplementary Service Call.....................................................................................................24
2.1.11 Mobile Originated Emergency Call.........................................................................................25
30 2.1.12 Mobile Originated Call Forwarding........................................................................................27
2.1.13 Common Equipment Usage Call..............................................................................................30
2.1.14 Terminating CAMEL Interrogation Call..................................................................................31
2.1.15 HLR Interrogation....................................................................................................................33
2.1.16 Mobile Terminated Location Request (MT-LR)........................................................................33
35 2.1.17 Mobile Originated Location Request (MO-LR).......................................................................34
2.1.18 Network Induced Location Request (NI-LR)............................................................................35
2.1.19 USSD Operation Record..........................................................................................................36
2.1.20 VIG Record...............................................................................................................................37
2.1.21 MGCF......................................................................................................................................38
40 2.1.22 MTP3 Signnaling Record.........................................................................................................40
2.1.23 SCCP Signnaling Record.........................................................................................................41
2.2 Description of Fields........................................................................................................................42
2.2.1 Additional Charging Information.............................................................................................42
2.2.2 Amount Of Global Translated Messages..................................................................................42
45 2.2.3 Amount Of Messages................................................................................................................42
2.2.4 Amount Of Octets.....................................................................................................................42
2.2.5 AoC Parameters / Change of AoC Parameters........................................................................42
2.2.6 Basic Service/Change of Service/ISDN Basic Service.............................................................42
2.2.7 Bearer Service(MGCF)............................................................................................................43
50 2.2.8 Bill Type....................................................................................................................................43
2.2.9 BSC Identification....................................................................................................................43
2.2.10 Call Duration...........................................................................................................................43
2.2.11 Call Reference..........................................................................................................................44
ZTE Confidential Proprietary VI

2.2.12 Called Party Address(MGCF)..................................................................................................44

2.2.13 Calling Party Address(MGCF)................................................................................................45
2.2.14 Calling/Called Location...........................................................................................................45
2.2.15 Calling/Called Party Roaming Indicator.................................................................................45
5 2.2.16 Calling/Called/Connected/Translated Number........................................................................45
2.2.17 Calling Party Number..............................................................................................................46
2.2.18 CAMEL Call Leg Information..................................................................................................46
2.2.19 CAMEL Information.................................................................................................................46
2.2.20 CAMEL Initiated CF Indicator................................................................................................46
10 2.2.21 CAMEL Modified Service Centre.............................................................................................47
2.2.22 CAMEL SMS Information........................................................................................................47
2.2.23 Cause for Termination..............................................................................................................47
2.2.24 Channel Coding Accepted/Channel Coding Used...................................................................48
2.2.25 Charged Neighbor SPC............................................................................................................48
15 2.2.26 CS Allocation/Retention Priority (CARP)................................................................................48
2.2.27 CUG Category.........................................................................................................................48
2.2.28 CUG InterLockCode................................................................................................................48
2.2.29 CUG Index...............................................................................................................................48
2.2.30 CUG Incoming Access Indicator..............................................................................................49
20 2.2.31 CUG Incoming Access Used....................................................................................................49
2.2.32 CUG Outgoing Access Used....................................................................................................49
2.2.33 CUG Outgoing Access Indicator..............................................................................................49
2.2.34 Data Rate.................................................................................................................................49
2.2.35 Data Volume.............................................................................................................................49
25 2.2.36 DDCFlag..................................................................................................................................49
2.2.37 Default Call/SMS Handling.....................................................................................................49
2.2.38 Destination Number.................................................................................................................50
2.2.39 Diagnostics...............................................................................................................................50
2.2.40 Dialed Number.........................................................................................................................50
30 2.2.41 DPC..........................................................................................................................................50
2.2.42 EMLP Priority Level................................................................................................................50
2.2.43 EMLP Request Priority Level..................................................................................................50
2.2.44 EMS-Digits...............................................................................................................................51
2.2.45 EMS-Key..................................................................................................................................51
35 2.2.46 Equipment ID...........................................................................................................................51
2.2.47 Equipment Type........................................................................................................................51
2.2.48 Error Code...............................................................................................................................51
2.2.49 Event Time Stamps...................................................................................................................51
2.2.50 Exchange Identity.....................................................................................................................52
40 2.2.51 Fixed Network User Rate.........................................................................................................52
2.2.52 Free Format Data....................................................................................................................52
2.2.53 Forward Call Indicator............................................................................................................53
2.2.54 Forward Type...........................................................................................................................53
2.2.55 Forwarded Sub. Number..........................................................................................................53
45 2.2.56 Free Format Data Append Indicator.......................................................................................53
2.2.57 Gateway Record Type...............................................................................................................54
2.2.58 GGSN Address(MGCF)............................................................................................................54
2.2.59 GPRS Charging ID(MGCF).....................................................................................................54
2.2.60 GsmSCF Address......................................................................................................................54
50 2.2.61 Guaranteed Bit Rate.................................................................................................................54
2.2.62 Hot Billing Tag.........................................................................................................................54
2.2.63 Hot Billing Tag 2......................................................................................................................55
2.2.64 HSCSD Parameters/Change of HSCSD Parameters...............................................................55
2.2.65 IMS Charging Identifier(MGCF).............................................................................................55
55 2.2.66 Incoming/Outgoing Cic............................................................................................................56
2.2.67 Incoming/Outgoing TKGP.......................................................................................................56
2.2.68 Incoming/Outgoing TKGP Name.............................................................................................56
2.2.69 Incomplete CDR Indication(MGCF)........................................................................................56
2.2.70 Inter Operator Identifiers.........................................................................................................56
60 2.2.71 Interrogation Result.................................................................................................................56
ZTE Confidential Proprietary VII

2.2.72 Is CAMEL Call.........................................................................................................................57

2.2.73 Is CUG Used............................................................................................................................57
2.2.74 Is MultiMedia Call...................................................................................................................57
2.2.75 Is HSCSD Used........................................................................................................................57
5 2.2.76 Last Long Part Indicator..........................................................................................................57
2.2.77 LCS Cause................................................................................................................................57
2.2.78 LCS Client Identity...................................................................................................................57
2.2.79 LCS Client Type........................................................................................................................58
2.2.80 LCS Priority.............................................................................................................................58
10 2.2.81 LCS QoS...................................................................................................................................58
2.2.82 Level of CAMEL Service..........................................................................................................58
2.2.83 List of Message Bodies(MGCF)...............................................................................................58
2.2.84 Location/Change of Location...................................................................................................59
2.2.85 Location Estimate.....................................................................................................................59
15 2.2.86 Location Type...........................................................................................................................59
2.2.87 Maximum Bit Rate....................................................................................................................59
2.2.88 Measure Duration....................................................................................................................59
2.2.89 Media Initiator Flag(MGCF)...................................................................................................59
2.2.90 Message Reference...................................................................................................................60
20 2.2.91 MLC Number............................................................................................................................60
2.2.92 Mobile station Classmark/Change of Classmark.....................................................................60
2.2.93 MOLR Type..............................................................................................................................60
2.2.94 MSC Address............................................................................................................................60
2.2.95 Msc SPC14...............................................................................................................................60
25 2.2.96 Msc SPC24...............................................................................................................................60
2.2.97 MSC Server Indication.............................................................................................................61
2.2.98 Network Call Reference............................................................................................................61
2.2.99 Node Address(MGCF)..............................................................................................................61
2.2.100 No Reply CondTime..............................................................................................................61
30 2.2.101 Notification to MS user........................................................................................................61
2.2.102 Number of DP Encountered.................................................................................................61
2.2.103 Number of Forwarding.........................................................................................................61
2.2.104 Old/New Location................................................................................................................62
2.2.105 OPC......................................................................................................................................62
35 2.2.106 Originator(MGCF)............................................................................................................62
2.2.107 Original Called Number......................................................................................................62
2.2.108 Origination Number.............................................................................................................62
2.2.109 Partial Record Type..............................................................................................................62
2.2.110 Personal Back Ring Tone Indicator (PBRT)........................................................................62
40 2.2.111 Positioning Data..................................................................................................................62
2.2.112 Privacy Override..................................................................................................................63
2.2.113 Radio Channel Requested/Radio Channel Used/Change of Radio Channel/Speech Version
Supported/Speech Version Used...............................................................................................................63
2.2.114 Rate Indication.....................................................................................................................63
45 2.2.115 Reason for Service Change..................................................................................................63
2.2.116 Record Closure Time............................................................................................................64
2.2.117 Record Extensions................................................................................................................64
2.2.118 Record Opening Time...........................................................................................................64
2.2.119 Record Sequence Number....................................................................................................64
50 2.2.120 Record Type..........................................................................................................................64
2.2.121 Recording Entity...................................................................................................................64
2.2.122 Redirect Number..................................................................................................................65
2.2.123 Redirecting Number.............................................................................................................65
2.2.124 Retransmission.....................................................................................................................65
55 2.2.125 Roaming Number.................................................................................................................65
2.2.126 Role of Node(MGCF)...........................................................................................................65
2.2.127 Routing Number...................................................................................................................65
2.2.128 SDP Media Components(MGCF)........................................................................................65
2.2.129 SDP Media Description(MGCF).........................................................................................66
60 2.2.130 SDP Media Name(MGCF)...................................................................................................66
ZTE Confidential Proprietary VIII

2.2.131 SDP Session Description(MGCF)........................................................................................66

2.2.132 Sequence Number.................................................................................................................67
2.2.133 Served IMEI.........................................................................................................................67
2.2.134 Served IMSI..........................................................................................................................67
5 2.2.135 Served MSISDN....................................................................................................................67
2.2.136 Service Category..................................................................................................................67
2.2.137 Service Centre Address.........................................................................................................67
2.2.138 Service Change Initiator......................................................................................................68
2.2.139 Service Delivery End Time Stamp(MGCF)..........................................................................68
10 2.2.140 Service Delivery Start Time Stamp(MGCF).........................................................................68
2.2.141 Service Identifier..................................................................................................................68
2.2.142 Service Key...........................................................................................................................68
2.2.143 Service Reason Return Code(MGCF)..................................................................................68
2.2.144 Service Request Timestamp(MGCF)....................................................................................69
15 2.2.145 Session ID(MGCF)...............................................................................................................69
2.2.146 Short Message Service Result..............................................................................................69
2.2.147 SIP Method(MGCF).............................................................................................................69
2.2.148 SIP Request Timestamp(MGCF)..........................................................................................69
2.2.149 SIP Response Timestamp(MGCF)........................................................................................69
20 2.2.150 SPC.......................................................................................................................................69
2.2.151 Speech Version Supported/Speech Version Used.................................................................70
2.2.152 System Type..........................................................................................................................70
2.2.153 SSN.......................................................................................................................................70
2.2.154 Subscriber Category.............................................................................................................70
25 2.2.155 Supplementary Service(s).....................................................................................................70
2.2.156 Supplementary Service Action..............................................................................................70
2.2.157 Supplementary Service Action Result...................................................................................71
2.2.158 Supplementary Service Parameters.....................................................................................71
2.2.159 Terminating Record Type......................................................................................................71
30 2.2.160 Transaction Identification....................................................................................................71
2.2.161 Transparency Indicator........................................................................................................71
2.2.162 Trunk Group ID Incoming/Outgoing(MGCF)......................................................................71
2.2.163 Type of service change.........................................................................................................71
2.2.164 Unstructured SS Data...........................................................................................................72
35 2.2.165 USSD interaction count........................................................................................................72
2.2.166 Ussd data coding scheme.....................................................................................................72
2.2.167 USSD operation code...........................................................................................................72
2.2.168 USSD Service Code..............................................................................................................72
2.2.169 VIG Call Type.......................................................................................................................72
403 ASN.1 DEFINITIONS FOR CDRS......................................................................................................72
3.1 CDR Structure..................................................................................................................................72
3.1.1 CallEventRecord......................................................................................................................72
3.1.2 MOCallRecord.........................................................................................................................73
3.1.3 MTCallRecord..........................................................................................................................75
45 3.1.4 ROAMRecord...........................................................................................................................76
3.1.5 IncGatewayRecord...................................................................................................................77
3.1.6 OutGatewayRecord..................................................................................................................77
3.1.7 TransitRecord...........................................................................................................................78
3.1.8 MOSMSRecord.........................................................................................................................79
50 3.1.9 MTSMSRecord.........................................................................................................................79
3.1.10 MOSMSIWRecord....................................................................................................................80
3.1.11 MTSMSGWRecord...................................................................................................................80
3.1.12 SSActionRecord........................................................................................................................80
3.1.13 MOECallRecord.......................................................................................................................81
55 3.1.14 MCFCallRecord.......................................................................................................................81
3.1.15 CommonEquipRecord..............................................................................................................83
3.1.16 TermCAMELIntRecord.............................................................................................................83
3.1.17 HLRIntRecord..........................................................................................................................84
3.1.18 MTLCSRecord..........................................................................................................................84
ZTE Confidential Proprietary IX

3.1.19 MOLCSRecord.........................................................................................................................85
3.1.20 NILCSRecord...........................................................................................................................85
3.1.21 USSDRecord.............................................................................................................................86
3.1.22 VIGRecord................................................................................................................................86
5 3.1.23 MGCFRecord...........................................................................................................................86
3.1.24 SigMTPStatisticRecord............................................................................................................87
3.1.25 SigSCCPStatisticRecord...........................................................................................................87
3.2 CDR Fields Structure........................................................................................................................88
3.2.1 ACRInterimLost(MGCF)..........................................................................................................88
10 3.2.2 AdditionalChgInfo....................................................................................................................88
3.2.3 AddressString...........................................................................................................................88
3.2.4 AiurRequested..........................................................................................................................89
3.2.5 AOCParameters.......................................................................................................................89
3.2.6 AOCParmChange....................................................................................................................89
15 3.2.7 BasicServiceCode.....................................................................................................................89
3.2.8 BasicServices............................................................................................................................89
3.2.9 BearerServiceCode...................................................................................................................90
3.2.10 BCDDirectoryNumber.............................................................................................................91
3.2.11 BillOrValidateFlag...................................................................................................................92
20 3.2.12 BSCIdentification.....................................................................................................................92
3.2.13 CallDuration............................................................................................................................92
3.2.14 CalledNumber..........................................................................................................................92
3.2.15 CalledPartyNumber.................................................................................................................92
3.2.16 CallEventRecordType...............................................................................................................93
25 3.2.17 CallingNum..............................................................................................................................93
3.2.18 CallingNumber.........................................................................................................................93
3.2.19 CallingPartyCategory..............................................................................................................93
3.2.20 CallReference...........................................................................................................................93
3.2.21 CAMELDestinationNumber.....................................................................................................93
30 3.2.22 CAMELInformation..................................................................................................................93
3.2.23 CAMELInitCFIndicator...........................................................................................................94
3.2.24 CAMELModificationParameters.............................................................................................94
3.2.25 CAMELSMSInformation..........................................................................................................94
3.2.26 Carp..........................................................................................................................................94
35 3.2.27 Category...................................................................................................................................94
3.2.28 CauseForTerm..........................................................................................................................95
3.2.29 ChangedParameters.................................................................................................................96
3.2.30 ChangeFlags............................................................................................................................96
3.2.31 ChangeOfClassmark................................................................................................................96
40 3.2.32 ChangeOfRadioChannel..........................................................................................................96
3.2.33 ChangeOfService......................................................................................................................96
3.2.34 ChannelCoding........................................................................................................................96
3.2.35 ChargeIndicator.......................................................................................................................97
3.2.36 ChargedParty...........................................................................................................................97
45 3.2.37 CICCode...................................................................................................................................97
3.2.38 Classmark.................................................................................................................................97
3.2.39 ConnectedNumber....................................................................................................................97
3.2.40 CUGCategory..........................................................................................................................97
3.2.41 CUGIndex................................................................................................................................97
50 3.2.42 CUGInterLockCode.................................................................................................................98
3.2.43 DataRate..................................................................................................................................98
3.2.44 DataVolume..............................................................................................................................98
3.2.45 DefaultCallHandling................................................................................................................98
3.2.46 DefaultSMS-Handling..............................................................................................................98
55 3.2.47 DeferredLocationEventType.....................................................................................................98
3.2.48 DestinationRoutingAddress......................................................................................................98
3.2.49 Diagnostics...............................................................................................................................98
3.2.50 EMLPPriorityLevel................................................................................................................108
3.2.51 EMLPRequestPriorityLevel...................................................................................................108
60 3.2.52 Eparameter.............................................................................................................................108
ZTE Confidential Proprietary X

3.2.53 EquipmentId...........................................................................................................................108
3.2.54 EquipmentType.......................................................................................................................108
3.2.55 Ext-GeographicalInformation................................................................................................108
3.2.56 Fnur........................................................................................................................................108
5 3.2.57 ForwardCallIndicator............................................................................................................108
3.2.58 ForwardedSubNumber...........................................................................................................109
3.2.59 ForwardToNumber.................................................................................................................109
3.2.60 FreeFormatData....................................................................................................................109
3.2.61 GatewayRecordType...............................................................................................................109
10 3.2.62 GenericNumber......................................................................................................................109
3.2.63 GenericNumbers....................................................................................................................109
3.2.64 Gsm-SCFAddress....................................................................................................................109
3.2.65 GuaranteedBitRate.................................................................................................................109
3.2.66 HLRIntResult..........................................................................................................................109
15 3.2.67 HotBillingTag.........................................................................................................................109
3.2.68 HotBillingTag2.......................................................................................................................110
3.2.69 HSCSDParmsChange.............................................................................................................110
3.2.70 IMEI........................................................................................................................................110
3.2.71 IMS-Charging-Identifier(MGCF)...........................................................................................110
20 3.2.72 IMSI........................................................................................................................................110
3.2.73 Incomplete-CDR-Indication(MGCF).....................................................................................110
3.2.74 InitiatingParty........................................................................................................................110
3.2.75 InterOperatorIdentiferlist(MGCF).........................................................................................110
3.2.76 InterOperatorIdentifiers.........................................................................................................111
25 3.2.77 InvolvedParty(MGCF)...........................................................................................................111
3.2.78 IPAddress................................................................................................................................111
3.2.79 IPBinaryAddress.....................................................................................................................111
3.2.80 IPTextRepresentedAddress.....................................................................................................111
3.2.81 ISDN-AddressString...............................................................................................................111
30 3.2.82 ISDN-SubaddressString..........................................................................................................111
3.2.83 LCSCause...............................................................................................................................112
3.2.84 LCSClientExternalID.............................................................................................................112
3.2.85 LCSClientInternalID..............................................................................................................112
3.2.86 LCSClientIdentity...................................................................................................................113
35 3.2.87 LCSClientType........................................................................................................................113
3.2.88 LCS-Priority...........................................................................................................................113
3.2.89 LCSQoSInfo............................................................................................................................113
3.2.90 LevelOfCAMELService...........................................................................................................114
3.2.91 LocationAreaAndCell.............................................................................................................114
40 3.2.92 LocationAreaCode..................................................................................................................114
3.2.93 LocationChange.....................................................................................................................114
3.2.94 LocationEstimateType............................................................................................................114
3.2.95 LocationType..........................................................................................................................115
3.2.96 LongPartSeqNumber..............................................................................................................115
45 3.2.97 ManagementExtensions..........................................................................................................115
3.2.98 MaximumBitRate....................................................................................................................115
3.2.99 McfType..................................................................................................................................115
3.2.100 Media-Components-List(MGCF).......................................................................................115
3.2.101 MessageBody(MGCF)........................................................................................................115
50 3.2.102 MessageReference..............................................................................................................116
3.2.103 MOLR-Type........................................................................................................................116
3.2.104 MSCAddress.......................................................................................................................116
3.2.105 MSISDN..............................................................................................................................116
3.2.106 MTPServiceIdentifier.........................................................................................................116
55 3.2.107 NetworkCallReference........................................................................................................116
3.2.108 NodeAddress(MGCF).........................................................................................................116
3.2.109 NoReplyCondTime..............................................................................................................116
3.2.110 NotificationToMSUser........................................................................................................117
3.2.111 NumberOfDPEncountered..................................................................................................117
60 3.2.112 NumberOfForwarding........................................................................................................117
ZTE Confidential Proprietary XI

3.2.113 NumOfHSCSDChanAllocated............................................................................................117
3.2.114 NumOfHSCSDChanRequested...........................................................................................117
3.2.115 OriginalCalledNumber.......................................................................................................117
3.2.116 PartialRecordType..............................................................................................................117
5 3.2.117 Pbrt.....................................................................................................................................117
3.2.118 PlmnId................................................................................................................................117
3.2.119 PositioningData..................................................................................................................117
3.2.120 RadioChanRequested.........................................................................................................118
3.2.121 RateIndication....................................................................................................................118
10 3.2.122 RecordingEntity..................................................................................................................118
3.2.123 ReasonForServiceChange..................................................................................................119
3.2.124 RecordSeqNumber..............................................................................................................119
3.2.125 RedirectingNumber.............................................................................................................119
3.2.126 RncID..................................................................................................................................119
15 3.2.127 RoamingNumber.................................................................................................................119
3.2.128 Role-of-Node(MGCF).........................................................................................................119
3.2.129 RoutingNumber...................................................................................................................119
3.2.130 SDP-Media-Component(MGCF).......................................................................................119
3.2.131 SDP-Media-Description(MGCF).......................................................................................120
20 3.2.132 ServiceCategory.................................................................................................................120
3.2.133 ServiceID............................................................................................................................120
3.2.134 ServiceKey..........................................................................................................................120
3.2.135 Session-Id(MGCF).............................................................................................................121
3.2.136 Sip-Method(MGCF)...........................................................................................................121
25 3.2.137 SMSResult..........................................................................................................................121
3.2.138 SPC14.................................................................................................................................121
3.2.139 SPC24.................................................................................................................................121
3.2.140 SPCCode............................................................................................................................121
3.2.141 SpeechVersionIdentifier......................................................................................................121
30 3.2.142 SSActionResult...................................................................................................................122
3.2.143 SSActionType......................................................................................................................122
3.2.144 SS-Code..............................................................................................................................122
3.2.145 SSNCode.............................................................................................................................123
3.2.146 SSParameters.....................................................................................................................124
35 3.2.147 SubscriberCategory............................................................................................................124
3.2.148 SuppServiceUsed................................................................................................................124
3.2.149 SystemType.........................................................................................................................124
3.2.150 TBCD-STRING...................................................................................................................124
3.2.151 TeleserviceCode.................................................................................................................124
40 3.2.152 TerminatingRecordType......................................................................................................125
3.2.153 TimeStaTimeStamp.............................................................................................................125
3.2.154 TKGPName........................................................................................................................126
3.2.155 TrafficChannel....................................................................................................................126
3.2.156 TranslatedNumber..............................................................................................................126
45 3.2.157 TransmissionMedium(MGCF)...........................................................................................126
3.2.158 TransparencyInd.................................................................................................................126
3.2.159 TrunkGroup........................................................................................................................126
3.2.160 TrunkGroupID(MGCF)......................................................................................................127
3.2.161 TypeOfServiceChange........................................................................................................127
50 3.2.162 USSDDataCodingSchema..................................................................................................127
3.2.163 USSDOperationCode.........................................................................................................129
3.2.164 USSDServiceCode..............................................................................................................129
3.2.165 VIGCallType.......................................................................................................................129
3.3 TAG Value Definition.....................................................................................................................129
55 3.3.1 CallEventRecord....................................................................................................................129
3.3.2 MOCallRecord.......................................................................................................................130
3.3.3 MTCallRecord........................................................................................................................134
3.3.4 ROAMRecord.........................................................................................................................137
3.3.5 IncGatewayRecord.................................................................................................................138
60 3.3.6 OutGatewayRecord................................................................................................................139
ZTE Confidential Proprietary XII

3.3.7 TransitRecord.........................................................................................................................140
3.3.8 MOSMSRecord.......................................................................................................................140
3.3.9 MTSMSRecord.......................................................................................................................141
3.3.10 MOSMSIWRecord..................................................................................................................142
5 3.3.11 MTSMSGWRecord.................................................................................................................142
3.3.12 SSActionRecord......................................................................................................................142
3.3.13 MOECallRecord.....................................................................................................................143
3.3.14 MCFCallRecord.....................................................................................................................145
3.3.15 CommonEquipRecord............................................................................................................147
10 3.3.16 TermCAMELIntRecord...........................................................................................................147
3.3.17 HLRIntRecord........................................................................................................................149
3.3.18 LCSMTRecord........................................................................................................................149
3.3.19 LCSMORecord.......................................................................................................................150
3.3.20 LCSNIRecord.........................................................................................................................151
15 3.3.21 USSDRecord...........................................................................................................................151
3.3.22 VIGRecord..............................................................................................................................152
3.3.23 MGCFRecord.........................................................................................................................152
3.3.24 SigMTPStatisticRecord..........................................................................................................154
3.3.25 sigSCCPStatisticRecord.........................................................................................................154
204 ANNEX..................................................................................................................................................154
4.1 Packing of 7-bit characters.............................................................................................................154
4.2 Description of Version Number......................................................................................................155
ZTE Confidential Proprietary XIII

Figures and Tables

Figures
Figure 1 Structure Diagrams of Block....................................................2
Figure 2 Structure Diagrams of CDR File..............................................2
5 Figure 3 Structure Diagrams of Charging Data Record..........................5
Figure 4 Definition of version number................................................156
Tables
Table 1 MOC Record............................................................................6
10 Table 2 MTC Record...........................................................................11
Table 3 Roaming record......................................................................15
Table 4 Incoming Gateway Record.....................................................17
Table 5 Outgoing Gateway Record.....................................................19
Table 6 Transit Record........................................................................20
15 Table 7 SMSMO Record....................................................................21
Table 8 SMSMT Record....................................................................22
Table 9 SMSMO Interworking Record..............................................23
Table 10 SMSMT Gateway Record.....................................................24
Table 11 SSAction Record...................................................................24
20 Table 12 MOC Emergency Record.......................................................25
Table 13 Mobile Originated Call Forwarding Record...........................27
Table 14 Common Equipment Usage Record.......................................30
Table 15 Terminating CAMEL Record.................................................31
Table 16 HLR Interrogation Record......................................................33
25 Table 17 LCSMT record......................................................................33
Table 18 LCSMO record......................................................................34
Table 19 LCSNI record........................................................................35
Table 20 USSD record..........................................................................36
Table 21 VIG record.............................................................................37
30 Table 22 MGCF record.........................................................................38
Table 23 MTP3 Signnaling Record.......................................................40
Table 24 SCCP Signnaling Record.......................................................41
Table 25 CallEventRecord Tag Values...............................................129
Table 26 MOCallRecord Tag Values..................................................130
35 Table 27 MTCallRecord Tag Values...................................................134
Table 28 ROAMRecord Tag Values...................................................137
ZTE Confidential Proprietary XIV

Table 29 IncGatewayRecord Tag Values............................................138
Table 30 OutGatewayRecord Tag Values...........................................139
Table 31 TransitRecord Tag Values....................................................140
Table 32 MOSMSRecord Tag Values.................................................140
5 Table 33 MTSMSRecord Tag Values.................................................141
Table 34 MOSMSIWRecord Tag Values............................................142
Table 35 MTSMSGWRecord Tag Values...........................................142
Table 36 SSActionRecord Tag Values................................................142
Table 37 MOECallRecord Tag Values................................................143
10 Table 38 MCFCallRecord Tag Values................................................145
Table 39 CommonEquipRecord Tag Values.......................................147
Table 40 TermCAMELIntRecord Tag Values.....................................147
Table 41 HLRIntRecord Tag Values...................................................149
Table 42 LCSMTRecord Tag Values..................................................149
15 Table 43 LCSMORecord Tag Values..................................................150
Table 44 LCSNIRecord Tag Values....................................................151
Table 45 USSDRecord Tag Values.....................................................151
Table 46 VIGRecord Tag Values........................................................152
Table 47 MGCFRecord Tag Values....................................................152
20 Table 48 SigMTPStatisticRecord Tag Valies......................................154
Table 49 sigSCCPStatisticRecord Tag Values....................................154
ZTE Confidential Proprietary XV

1 GENERAL INFORMATION
1.1 Abbreviation
Abb. Full Name
AoC Advice of Charge
Customised Applications for Mobile network Enhanced
CAMEL
Logic
DP Detection Point
GMSC Gateway MSC
gsmSCF GSM Service Control Function
gsmSSF GSM Service Switching Function
HLR Home Location Register
HPLMN Home PLMN
HSCSD High Speed Circuit Switched Data
IMEI International Mobile Equipment Identity
IMS IP Multimedia Subsystem
IMSI International Mobile Subscriber Identity
ISDN Integrated Services Digital Network
MGCF Media Gateway Control Function
MOC Mobile Originated Call (attempt)
MS Mobile Station
MSC Mobile Services Switching Centre
MSRN Mobile Station Roaming Number
MTC Mobile Terminated Call (attempt)
O-CSI Originating CAMEL Subscription Information
OMC Operations and Maintenance Centre
PLMN Public Land Mobile Network
SAC Service Area Code
SIP Session Initiation Protocol
SMS Short Message Service
T-CSI Terminating CAMEL Subscription Information
TDP Trigger Detection Point
USSD Unstructured Supplementary Service Data
VIG Video Internet GateWay
VLR Visitor Location Register
VMSC Visited MSC
VPLMN Visited PLMN
ZTE Confidential Proprietary Page 1 of 173

1.2 Structure of the CDR File

1.2.1 Field
Basic data unit, which is the basic element forming the ticket record. Each field has
its own tag and length (Len). The field can be divided into fixed length field and
5 non-fixed length field.
1.2.2 Charging Data Record

Record the billing information related to a chargeable event.
Each CDR contains multiple fields. Each CDR length can not exceed max.2048
bytes.
101.2.3 Block
The block contains one or more (n) CDRs with variable lengths (L). The block has a
fixed size (2048 bytes). It is filled with CDRs until there is no more room to add the
next record. The rest of the fixed size block will then be filled with fillers(H’FF).
15 Figure 1 Structure Diagrams of Block
1.2.4 CDR File

The CDR file consists of one or multiple “Blocks”. MSC Server will generate a
CDR file at the specified time or the specified length according to the system
20 configuration.
Figure 2 Structure Diagrams of CDR File
1.3 CDR Encoding

251.3.1 ASN.1 (Basic Encoding Rules) description
The CDRs generated at MSC Server is specified using the Abstract Syntax Notation
One (ASN.1). ASN.1 is a language that defines the way data is sent across dissimilar
communication systems. ASN.1 ensures that the data received is the same as the
data transmitted by providing a common syntax for specifying application layer
30 protocols. ASN.1 is an ISO/ITU-T standard based on the OSI model and is defined

in “ASN.1 encoding rules: Specification of Basic Notation, ITU-T Recommendation

X.680”.
The MSC Server uses ASN.1 Basic Encoding Rules (BER) to encode the CDRs.
BER is a set of standard rules, defined in “ASN.1 encoding rules: Specification of
5 Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished
Encoding Rules (DER) ITU-T Recommendation X.690”, for encoding data types
specified in ASN.1. A field containing a value of a certain data type is encoded into
the following parts:
1. Identifier: identifies the data type and consists of an ASN.1 tag and data
10 structure information
2. Length: the length of the content part in number of octets
3. Contents: the value encoded according to data type specific rules
The ASN.1 tags assigned to CDR fields are specified in chapter 3.3.
1.3.2 Encoding of the Tag

15 The identifier octets encode the ASN.1 tag of the data value. Two possibilities exist:
1. single octet encoding for tag numbers from 0 to 30 (inclusive)
 Bits 8-7  Class identifier

 0 0 Universal
 0 1 Application
 1 0 Context-specific
 1 1 Private
 Bit 6  0 Primitive
 1 Constructed
 Bit 5-1  binary integer with bit 5 as msb
2. Use of a leading octet for tag numbers bigger than or equal to 31

The leading octet is encoded as follows:
20
 Bits 8-7  Class identifier as for single octet id
 Bit 6  0 Primitive
 1 Constructed
 Bit 5-1  all bits set to 1
Subsequent octets are encoded as:
 Bits 8  set to 1 in all non-last subsequent octets

 Bit 7-1  Bits 7-1 of all subsequent octets encoded as

a binary integer equal to the tag number
with bit 7 of the first subsequent octet as
most significant bit.
1.3.3 Encoding of the 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
used in this CDR format.
5 1. short length encoding for length from 0 to 127 (inclusive)
LLLLLLL represents the length of the content

2. long length encoding for length > 127
10 LLLLLLLL represents the length of the content
1.3.4 Encoding of the content

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:
15 bit 8 of octet 1 is the most significant bit (msb), bit 1 of octet n is the least
significant bit (lsb)
1.3.5 ASN.1 BER Encoding of Integers

ASN.1 defines the integer type as a simple type with distinguished values, which are
20 the positive and negative numbers, including zero. The content part for a field of
type integer is BER encoded in one or more octets. The content octets contain the
two’s complement binary number equal to the integer value, and consisting of bits 8

to 1 of the first octet, followed by bit 8 to 1 of each octet in turn up to and including
the last content octet. The two’s complement form implies that the most significant
bit of the content octets indicates the sign of the value (0 for positive numbers and 1
for negative numbers). This means that the highest positive number a sequence of X
5 octets can represent is: 2(8X-1)-1.
Example-1:
The highest positive number represented by four octets (32 bits) is: 2 31-1.
Example-2:
To represent the highest value for a 32 bits positive integer (2 32-1), five
10 content octets are needed
1.3.6 Structure Diagrams of Charging Data Record
Figure 3 Structure Diagrams of Charging Data Record
15
20

2 DESCRIPTION OF CDRS
2.1 Record Types
Field category definition:
M:Mandatory field. All the fields marked with “M” must be present in CDRs.
5 C:This field shall be present in CDRs only when the specified conditions are
satisfied. These conditions are specified as part of the field definition.
OM:This field must be included in CDRs if operators require that it is present in
CDRs. In other words, the specified O M field, as a mandatory parameter, shall be
present.
10 OC:This field must be included in CDRs if operators require that it is present in
CDRs in the case that the specified conditions are satisfied. In other words, a field
configured to QC must be present when conditions are satisfied.
2.1.1 Mobile Originated Call

A mobile originated call (MOC) record the charging information of a caller (mobile
15 subscriber) during a call, and the information serves as the original voucher of
charging submitted by the MSC to the billing center for the caller.
Table 1 MOC Record
Field Category Description
Record Type M Mobile originated record
Served IMSI M IMSI of the calling party
Served IMEI C IMEI of the calling ME , if available.
Served MSISDN OM The primary MSISDN of the calling party
The address of the called party i.e. the number
Called Number OM
dialled by the calling
The called number after digit translation within
Translated Number OC
the MSC (if applicable)
The number of the connected party if different to
Connected Number OC
the Called Number
The Mobile Station Roaming Number employed
Roaming Number OC
to route this connection, if applicable.
The E.164 number of the visited MSC producing
Recording Entity M
the record.
The MSC trunk group on which the call originated
Incoming TKGP OC , usually from the BSS. If available in 3G, this
parameter shall be supplied.
The trunk group on which the call left the MSC. If
Outgoing TKGP OC
available in 3G, this parameter shall be supplied.
The identity of the cell or the SAC at the time of
Location M
CDR creation, including the location area code.
A list of changes in Location Area Code / Service
Change of Location OC
Area Code / Cell Id. Each time-stamped.
Basic service M Bearer or teleservice employed.
C Indicates whether the basic service was used in
transparent or non-transparent mode. This
Transparency
parameter is provided only for those basic services
Indicator
which may be employed in both transparent and
non-transparent mode.


OC A list of changes of basic service during a
Change of Service
connection each time-stamped.
C Supplementary services invoked as a result of this
connection. This field shall be present when one
Supp. Services
or more supplementary services have been
invoked.
OC The charge advice parameters sent to the MS on
AOC Parameters call set-up. This field shall be supplied only when
AoC parameters have been sent.
OC New AOC parameters sent to the MS e.g. as a
result of a tariff switch over, including the time at
Change of AOC
which the new set was applied. This field shall be
Parameters
supplied only when AoC parameters have been
sent.
M The mobile station classmark employed on call
MS Classmark
set-up.
OC A list of changes to the classmark during the
Change of Classmark
connection each time-stamped
C Seizure time: time of incoming traffic channel
C seizure (for unsuccessful call attempts)
Event time stamps:
C Answer: time of answer (for successful calls)
Release time: time of traffic channel release
M The chargeable duration of the connection for
Call duration
successful calls, the holding time for call attempts.
OC The number of data segments transmitted if
Data volume
available at the MSC
Radio Chan. OC The type of radio traffic channel (full / half etc.)
Requested requested by the MS.
OC The type of radio channel actually used (full or
Radio Chan. Used
half rate).
Change of Rad. Chan. OC A list of changes each time stamped
Cause for termination M The reason for the release of the connection.
OM A more detailed reason for the release of the
Diagnostics
connection.
M A local identifier distinguishing between
Call reference
transactions on the same MS
Partial record sequence number, only present in
Sequence no. C
case of partial records.
Last Long Part Ind. C Identification of last CDR
Charge/no charge indicator and additional
Additional Chg. Info OC
charging parameters, when available.
A set of network / manufacturer specific
Record extensions OC
extensions to the record, when available.
The field indicates that the CAMEL service is
Is CAMEL Call OM
applied in the call.
Identifies the CAMEL server serving the
gsmSCF address C subscriber. Shall be present only if CAMEL is
applied.
The CAMEL service logic to be applied. Shall be
Service key C
present only if CAMEL is applied.
An identifier to correlate transactions on the same
Network Call
C call taking place in different network nodes, shall
Reference
be present if CAMEL is applied.


This field contains the E.164 number assigned to
the MSC that generated the network call
MSC Address C
reference. Shall be present only if CAMEL is
applied.
Indicates whether or not a CAMEL call
encountered default call handling. This field shall
Default call handling OC
be present only if default call handling has been
applied.
The field indicates that the HSCSD service is
Is HSCSD Used OM
applied in the call.
The maximum number of HSCSD channels
Number of HSCSD
OC requested as received from the MS at call set-up.
Channels Requested
Shall only be present for HSCSD connections.
The number of HSCSD channels allocated to the
Number of HSCSD
OC MS at call set-up. Shall only be present for
Channels Allocated
HSCSD connections.
A list of network or user initiated changes of
number of HSCSD channels during a connection
Change of HSCSD each time-stamped. Shall only be present in case
OC
Parameters of an HSCSD call, if the basic HSCSD parameters
are modified due the user or network initiated
modification procedure.
Indicates the user data rate applied for the
Fixed Network User connection in the fixed network. Shall only be
OC
Rate present for 2G HSCSD connections and for
UMTS data connections.
The total Air Interface User Rate Requested by the
Air Interface User
OC MS at call set-up. Shall only be present for non-
Rate Requested
transparent HSCSD connections.
A list of the traffic channels codings accepted by
Channel Coding
OC the MS. Shall only be present for HSCSD
Accepted
connections.
The traffic channels codings negotiated between
Channel Coding Used OC the MS and the network at call set-up. Shall only
be present for HSCSD connections.
Speech Version Speech version supported by the MS with highest
OC
Supported priority indicated by MS
Speech Version Used OC Speech version used for that call
Number that counts how often armed detection
Number of DP
OC points (TDP and EDP) were encountered. Shall be
encountered
present only if CAMEL is applied.
Indicator for the complexity of the CAMEL
Level of CAMEL
OC feature used. Shall be present only if CAMEL is
service
applied.
This field contains data sent by the gsmSCF in the
Furnish Charging Information (FCI) message(s).
Free format Data C 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.
Set of CAMEL information IEs. Each of these IEs
CAMEL call leg contains information related to one outgoing
C
information CAMEL call leg. Shall be present only if CAMEL
is applied.
Indicator if free format data from this CDR is to
Free format data
C be appended to free format data in previous partial
append indicator
CDR. Shall be present only if CAMEL is applied.


Indicates whether or not a CAMEL call
Default call handling encountered default call handling for 2nd service
OC
2 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.
GsmSCF address 2 C
Shall be present only if CAMEL is applied for 2nd
service.
The CAMEL service logic to be applied for 2nd
Service key 2 C 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
Free format Data 2 C
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
Free format data this CDR is to be appended to free format data in
C
append indicator 2 previous partial CDR. Shall be present only if
CAMEL is applied for 2nd service.
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 set-up. For an open CDR in a 2G
System Type M NE (responsible for the CDR), the field is not
present (even if the call is handed off to a 3G air
interface). For a CDR in a 3G NE (responsible for
the CDR), the value unknown shall be used after
handover.
Exchange Identity OM Identity of the MSC that generates original bills.
Number dialed by subscribers. It is used in
Dialled Number C
originating calls only.
Subscriber property registered by mobile
Subscriber Category C
subscribers in the HLR
Record Sequence Record sequence number. It is the unique ID of a
M
Number CDR.
The level of priority actually used by subscribers
EMLP Priority Level C
when invoking the eMLPP service.
EMLP Request The priority level of subscription when
C
Priority Level subscribers invoke the eMLPP service.
Hot billing tag C Hot billing tag defined by operators
The field indicates that the CUG service is applied
Is CUG Used OM
in the call.
CUG Category C Reserved for extention
Inter-lock code of CUG, used to identify different
CUG InterLockCode C
CUGs in the same network
Data Rate C Rate of the data service
This field indicates that the call is a CS
Is MultiMedia Call OM multimedia call in the case of multimedia service
based on data bearer in the CS
This indication is present when the “rate match”
Rate Indication OC of basic services between the MS or user
equipment and the network is informed.


Bit rate guaranteed by the UMTS carrier service
for users or applications. It is based on available
resources. It can make admission easy to control
Guaranteed bit rate Oc
and fit for resource allocation in the UMTS. This
parameter is present in the UMTS data
connections only.
The maximum bit rate can be used to establish
coding restrictions in the down lines of the
wireless interface. It is used to restrict the bit rate
from transmission to applications or external
Maximum bit rate Oc
network and to define the maximum user bit rate
for the applications that can use different bit rates
for transmission. This parameter is present for the
UMTS data connections only.
Personal back ring Indicate whether the personal back ring tone
OC
tone indicator (PBRT) service is applied in the call.
CS
CS allocation/retention priority (CARP) of
Allocation/Retention OC
visiting international roaming subscribers
Priority
CUG Index C CUG index for the subscriber
CUG Outgoing
C CUG outgoing access is used.
Access Used
This parameter indicates that the calling
CUG Outgoing
C subscriber has made a CUG call with outgoing
Access Indicator
access.
Hot billing tag 2 defined by operators. The pre-
Hot Billing Tag2 C paid service and post-paid service subscribers are
distinguished.
DDCFlag OC Direct Collect Call Flag defined by operators.
BSC Identification OC This field indicates the BSC spc code where the
served subscriber is located when the call is
started.This field is provided only when 2G radio
access technology is used.
Called Location OC This field indicates the location of the called
subscriber when the call is started
Calling Party OC This field is the roaming indicator of the calling
Roaming Indicator party.It is provided only when the calling
subscriber is roaming
Service Category OC This field indicates the service category of the
call.
Transaction OC This field is provided when the user has more than
Identification one ongoing calls at the same time.It is used to
identify different ongoing calls.
Msc SPC14 OC This field is the spc14 code of the serving MSC
Incoming Cic OC This field indicates the cic value of the incoming
trunk.
Outgoing Cic OC This field indicates the cic value of the outgoing
trunk.
Incoming TKGP OC This field indicates the incoming trunk group
Name name.
Outgoing TKGP OC This field indicates the outgoing trunk group
Name name.
Partial Record Type OC Indicates the event (time limit etc.) that caused the
generation of a partial record.Provided if
SCUDIF service is used.


Service change OC Indicates the service change initiator. Provided if
initiator SCUDIF service is used
Reason for service OC Indicates the type of service change and fallback.
change Provided if SCUDIF service is used
Type of service OC Indicates the type of service change. Provided if
change SCUDIF service is used
2.1.2 Mobile Terminated Call

A mobile terminated call (MTC) record the charging information of the called party
(mobile subscriber) during a call, and the information serves as the original voucher
of charging submitted by the MSC to the billing center for the called party.
5 Table 2 MTC Record


Record Type M Mobile Terminated.
Served IMSI M IMSI of the called party.
Served IMEI C IMEI of the called ME, if available.
Served MSISDN OM The MSISDN of the called party.
Calling Number C The number of the calling party if available.
Recording Entity M The E.164 number of the visited (terminating) MSC
Incoming TKGP OM The MSC trunk group on which the call originated.
The trunk group on which the call left the MSC,
Outgoing TKGP OC usually to the BSS. If available in 3G, this parameter
shall be supplied.
The identity of the cell or the SAC occupied by the
Location C called party when the call was set up, including the
location area code.
A list of changes in Location Area Code / Service Area
Code / Cell Id. Each time-stamped.
Basic Service M Bearer or teleservice employed
Indicates whether the basic service was used in
transparent or non-transparent mode. This
Transparency Indicator C 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
Change of Service OC
each time-stamped.
Supplementary services invoked as a result of this
Supplementary services C connection. This field shall be present when one or
more supplementary services have been invoked.
The charge advice parameters sent to the MS on call
AOC Parameters OC set-up. This field shall be supplied only when AoC
parameters have been sent.
New AOC parameters sent to the MS e.g. as a result of
Change of AOC a tariff switch-over, including the time at which the
OC
Parameters new set was applied. This field shall be supplied only
when AoC parameters have been sent.
MS Classmark M The mobile station class mark.
A list of changes to the classmark during the
Change of Classmark OC
connection each time-stamped
Seizure time: time of traffic channel seizure for
C
unsuccessful call attempts
Event time stamps: C
Answer time: time of answer for successful calls
C
The chargeable duration of the connection if
Call duration M
successful, the holding time of the call if unsuccessful.
The number of data segments transmitted, if available
Data volume OC
at the MSC
The type of radio traffic channel (full / half etc.)
Radio Chan. Requested OC
requested by the MS.
Radio Chan. Used OC The type of radio channel used (full or half rate).
Change of Rad. Chan OC A list of changes each time stamped
Cause for termination M The reason for the release of the call.
A more detailed reason for the release of the
Diagnostics OM
connection.
A local identifier distinguishing between transactions
Call reference M
at the same MS
Partial record sequence number, only present in case
Sequence no. C
of partial records.
Charge/no charge indicator and additional charging
Additional Chg. Info OC
parameters, when available.
A set of network/ manufacturer specific extensions to
the record, when available.
An identifier to correlate transactions on the same call
Network Call Reference C taking place in different network nodes, shall be
present if CAMEL is applied.


The field indicates that the CAMEL service is applied
Is CAMEL Call OM
in the call.
This field contains the E.164 number assigned to the
MSC Address C MSC that generated the network call reference. Shall
The maximum number of HSCSD channels requested
Number of HSCSD
OC as received from the MS at call set-up. Shall only be
Channels Requested
present for HSCSD connections.
The number of HSCSD channels allocated to the MS
Number of HSCSD
OC at call set-up. Shall only be present for HSCSD
Channels Allocated
connections.
A list of network or user initiated changes of number
of HSCSD channels during a connection each time-
Change of HSCSD
OC stamped. Shall only be present in case of an HSCSD
Parameters
call, if the basic HSCSD parameters are modified due
the user or network initiated modification procedure.
Indicates the user data rate applied for the connection
Fixed Network User Rate C 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
Air Interface User Rate
C at call set-up. Shall only be present for non-transparent
Requested
HSCSD connections.
A list of the traffic channels codings accepted by the
Channel Coding Accepted C
MS. Shall only be present for HSCSD connections.
The traffic channels codings negotiated between the
Channel Coding Used C MS and the network at call set-up. Shall only be
present for HSCSD connections.
Speech version supported by the MS with highest
Speech Version Supported OC
priority indicated by MS
Speech Version Used OC Speech version used for the call
Identification address of the CAMEL server used by
subscribers. This parameter is present in the called
GsmSCF address C
CDR of the called GMSC only when the CAMEL
service is applied.
CAMEL service logic to be applied. This parameter is
Service Key C
present only when the CAMEL service is applied.
Indicate whether the default call handling is applied
Default Call handling C for a CAMEL call. This field is present only when the
default call handling is applied.
This parameter contains data of FCI messages sent by
the SCF. The data can be sent in an FCI message or
multiple FCI messages and indicated by corresponding
Free format Data C
suffix. This parameter is present in the called CDR
only when the CAMEL service is applied and the SCP
sends FCI messages.
Free format data append Free format data of a CDR. It is appended to the free
C
indicator format data of the previous partial output CDR.
Indicate that a call happens in the 3G-UMTS or GSM
System Type M
system.
Mobile redirect number, usually the call forwarding
Redirect Number C
number C
Subscriber attribute registered by mobile
subscribers in the HLR
M
Number CDR.
Number of the connected party (number C) if it is
Connected Number OC
different from the called number.
The field indicates that the CUG service is applied in
Is CUG Used OM
the call.


CUG InterLockCode C
This field indicates that the call is a CS multimedia
Is MultiMedia Call OM call in the case of multimedia service based on data
bearer in the CS.
This indication is present when the “rate match” of
Rate Adaptation OC basic services between the MS or user equipment and
the network is informed.
Bit rate guaranteed by the UMTS carrier service for
users or applications It is based on available resources.
Guaranteed bit rate Oc It can make admission easy to control and fit for
resource allocation in the UMTS. This parameter is
present in the UMTS data connections only.
The maximum bit rate can be used to establish coding
restrictions in the down lines of the wireless interface.
It is used to restrict the bit rate for transmission to
Maximum bit rate Oc applications or external networks and to define the
maximum user bit rate for the applications that can use
different bit rates for transmission. This parameter is
present for the UMTS data connection only.
Personal back ring tone Indicate whether the PBRT service is applied in the
OM
indicator call.
CS Allocation/Retention CS allocation/retention priority (CARP) of visiting
OC
Priority international roaming subscribers
CUG Incoming Access
C CUG incoming access is used.
Used
CUG Incoming Access This parameter indicates that the calling subscriber has
C
Indicator made a CUG call with outgoing access.
Mobile redirect number, usually number B before
Redirecting Number C
forwarding
Hot billing tag 2 defined by operators. The pre-paid
Hot Billing Tag 2 C service and post-paid service subscribers are
distinguished.
Terminating Record OC This field indicates the type of the terminating
Type record.
Original Called Number OC The original called number.It is the B number in
the terminating record of C
started. This field is provided only when 2G radio
Calling Location OC This field indicates the location of the calling
Called Party OC This field is the roaming indicator of the called
Roaming Indicator party.It is provided only when the called
call.
trunk.


trunk.
Name name.
Name name.
2.1.3 Roaming Call

A roaming (Inter-PLMN) record is generated by the routing GMSC of HPLMN
when the called subscriber is roaming outside the PLMN. It is used to record the
5 location information of the roaming called subscriber.
If it is configured to output intra-PLMN roaming record, a roaming (Intra-PLMN)
record is generated in the routing GMSC when the called subscriber is roaming
inside the PLMN. It is used to record the location information of the roaming called
subscriber.
10 Table 3 Roaming record


Record Type M Roaming record.
Served IMSI M IMSI of the called (roaming) party.
Served MSISDN OM The MSISDN of the called (roaming) party.
Calling Number C The address of the calling party, if available.
The Mobile Station Roaming Number employed to
Roaming Number M
route this connection.
Recording Entity M The E.164 number of the GMSC
Incoming TKGP OM The GMSC trunk group on which the call originated.
Outgoing TKGP OM The trunk group on which the call left the GMSC
Basic service M Bearer or teleservice employed.
Indicates whether the basic service was used in
transparent or non-transparent mode. This parameter is
Transparency Indicator C 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
Change Of Service OC
each time-stamped.
Supplementary services invoked as a result of this
Supplementary Services OC connection. This field shall be present when one or
more supplementary services have been invoked.
Seizure time: time of incoming traffic channel seizure
C
(for unsuccessful call attempts)
Event time stamps C
Answer time: time of answer (for successful calls)
OM
The chargeable duration of the connection for
Call duration M
successful calls, the holding time of call attempts.
The number of data segments transmitted if available
Data volume C
at the GMSC
Diagnostics OM
connection.
A local identifier distinguishing between transactions
Call reference M
on the same MS
Partial record sequence number, only present in case
Sequence no. C
of partial records.
A set of network/ manufacturer specific
extensions to the record, when available
Is CAMEL Call OM
in the CDR.
An identifier to correlate transactions on the same call
Network Call Reference C taking place in different network nodes, shall be
present if CAMEL is applied.
This field contains the E.164 number assigned to the
MSC Address C MSC that generated the network call reference. Shall
M
Number CDR.
Is CUG Used OM
the call.
CUG InterLockCode C
bearer in the CS
distinguished.
Redirect Number OC The redirect number of the call.


call.
trunk.
trunk.
Name name.
Name name.
Trans Roaming Oc This field indicates the changed Mobile Station
Number Roaming Number
2.1.4 Gateway Record

A gateway record charging information related to the trunk. It is used to settle
accounts with other networks. According to the direction of a call, the gateway CDR
5 falls into incoming gateway CDR and outgoing gateway CDR.
The generation of gateway CDRs can be configured through the configuration
management system of the switch.
Table 4 Incoming Gateway Record


Record Type M Incoming gateway record
The number of the calling party if available at this
Calling Number C
node.
The address of the called party as seen by the GMSC.
Called Number M This is the number employed by the GMSC for
routing.
The incoming GMSC trunk group on which the call
Incoming TKGP M
originated.
The trunk group on which the call left the GMSC. If
Outgoing TKGP OC
available in 3G, this parameter shall be supplied.
M Seizure time: time of incoming trunk seizure
Event time stamps C Answer time: time of answer (successful calls only)
OM Release time: time of incoming trunk release
The accountable duration (answer -> release of
incoming trunk) of the connection if successful, the
Call duration M
call holding time of the incoming trunk for call
attempts.
Data Volume C If applicable and known at the GMSC
Diagnostics OM
connection.
Call Reference M A local identifier distinguishing between transactions.
Sequence no. C Partial record sequence number, if applicable.
Additional Chg. Info OC Charge/No charge and additional charge indicator
M
Number CDR.
OC
indicator call.
Gateway Record Type OC This field indicates the type of the trunk.
e.g.gateway,trunk
Roaming Number OC This field is the roaming number of the called
subscriber
Redirect Number OC The redirect number of the call
trunk.
trunk.
Incoming TKGP Name OC This field indicates the incoming trunk group
name.
Outgoing TKGP Name OC This field indicates the outgoing trunk group
name.
Forward Call Indicator OC This field is only provided in the incoming
gateway record,it is used to identify the type of
the originating party of the call. e.g. international
or national


ISDN Basic Service OM The ISDN basic service employed
Table 5 Outgoing Gateway Record

Record Type M Outgoing gateway record
Calling Number C
node.
The address of the called party as seen by the GMSC.
Called Number M This is the number employed by the GMSC for
routing.
The incoming GMSC trunk group on which the call
Incoming TKGP OC originated. If available in 3G, this parameter shall be
supplied.
Outgoing TKGP M The trunk group on which the call left the GMSC.
M Seizure time: time of outgoing trunk seizure
Event time
C Answer time: time of answer (successful calls only)
stamps:
OM Release time: time of outgoing trunk release
The accountable duration (answer -> release of
outgoing trunk) of the connection if successful, the
Call duration M
call holding time of the outgoing trunk for call
attempts.
Data Volume C If applicable and known at the GMSC
Cause for The reason for the release of the connection.
M
termination
Diagnostics OM
connection.
Last Long Part
C Identification of last CDR
Ind.
A set of network/ manufacturer specific extensions to
the record, when available
Additional Chg.
OC Charge/No charge and additional charge indicator
Info
M
Number CDR.
Personal back ring Indicate whether the PBRT service is applied in the
OM
tone indicator call.


Gateway Record OC This field indicates the type of the trunk.
Type e.g.gateway,trunk
subscriber
trunk.
trunk.
Incoming TKGP OC This field indicates the incoming trunk group name.
Name
Outgoing TKGP OC This field indicates the outgoing trunk group name.
Name
generation of a partial record.Provided if SCUDIF
service is used.
Type of service OC Indicates the type of service change and fallback.
2.1.5 TRANSIT
A transit record is generated when the MSC serves as the TMSC. That is, the MSC
is not an MSC that a calling party visits or an MSC that a terminating party visits. It
5 implements the function of call connection. In this case, the MSC generates the
transit bill. The transit CDR cannot be generated at the same time when the trunk
CDR is generated. The transit CDR or trunk CDR can be generated through setting
of configuration management system.
Table 6 Transit Record


Record Type M Transit
Calling Number C
node.
Called Number M The address of the called party as seen by the TMSC.
Recording Entity M The E.164 number of the transit MSC
Incoming TKGP OM The TMSC trunk group on which the call originated.
Outgoing TKGP OM The trunk group on which the call left the TMSC.
Seizure time: time of incoming trunk seizure for
C
unsuccessful call attempts
Answer time: time of answer (successful calls only)
OM
The chargeable duration of the connection if
Call duration M
successful, the call holding time for call attempts.
Data Volume OC If applicable and known at the transit MSC
Diagnostics OM
connection.
M
Number CDR.
OC
indicator call.
subscriber
trunk.
trunk.
Incoming TKGP Name OC This field indicates the incoming trunk group
name.
Outgoing TKGP Name OC This field indicates the outgoing trunk group
name.
2.1.6 SMS-MO
An SMS-MO record is generated by the VMSC for each short message sent by a
mobile subscriber.
5 Table 7 SMS-MO Record


Record Type M SMS-Mobile originated
Served IMSI M IMSI of the subscriber sending the short message
Served IMEI OC IMEI of the subscriber sending the short message
Primary MSISDN of the subscriber sending the short
Served MSISDN OM
message
MS Classmark M Mobile station classmark
Address of the short message service center (E.164
Service Centre Address M
number)
E.164 number of the visited MSC (serial number of
Recording Entity M
MSC/VLR: TON + NPI + MSC ID)
Location area code (LAC) and service area code
Location OM (SAC) or cell ID (CID) from which the message is
sent
A reference, provided by the MS uniquely identifying
Message Reference OM
this message
Time stamp when the MSC receives the short message
Event Time stamp M
from a subscriber
Result of the attempted delivery if the delivery is
SMS Result C
unsuccessful.
A series of CDR extension information defined by the
network or manufacturer
Destination number dialed by the MS sending the
Destination number OM
message
A series of CAMEL information IEs. Each of these
CAMEL SMS
C contains information related to CAMEL call leg of the
Information
short message.
System Type M
system.
M
Number CDR.
distinguished.
2.1.7 SMS-MT
An SMS-MT record is generated by the VMSC for each short message received by a
mobile subscriber.
5 Table 8 SMS-MT Record

Category Description
Field
Record Type M SMS-Mobile terminated
number)
Served IMSI M IMSI of the subscriber receiving the short message
Served IMEI OC IMEI of the subscriber receiving the short message
Primary MSISDN of the subscriber receiving the short
Served MSISDN OM
message
MS Classmark C Mobile station classmark
E.164 number of the visited MSC (serial number of
Recording Entity M
Location OM (SAC) or cell ID (CID) to which the message is
delivered.
Time stamp when the MSC sends a short message to
Event Time stamp M
the subscriber
SMS Result C
unsuccessful.
System Type M
system.
M
Number CDR.
Origination number OC Number of the subscriber sending this short message
distinguished.
A series of CAMEL information IEs. Each of these
CAMEL SMS
C contains information related to CAMEL call leg of the
Information
short message.
2.1.8 SMS-MO-IW/GMSC
An SMS-MO interworking record is generated by the interworking MSC for each
short message sent by a mobile subscriber. It is used to settle accounts between the
5 PLMNs and short message service center (SMSC).
Table 9 SMS-MO Interworking Record


Record Type M SMS-MO interworking record
number)
Served IMSI M IMSI of the subscriber sending the short message
Served MSISDN M MSISDN of the subscriber sending the short message
Recording Entity M E.164 number of the MSC
Time stamp when the interworking MSC receives the
Event Time stamp M
short message
SMS Result C
unsuccessful.
System Type M
system.
Record Sequence
M Record sequence number. It is the unique ID of a CDR.
Number
2.1.9 SMS-MT-GW/GMSC
An SMS-MT gateway record is generated by the GMSC for each short message sent
to a mobile subscriber. It is used to settle accounts between the PLMN and SMSC.
5 Table 10 SMS-MT Gateway Record
Record Type M SMS-MT interworking record
number)
Served IMSI M IMSI of the subscriber receiving the short message
Served MSISDN OM MSISDN of the subscriber receiving the short message
Recording Entity M E.164 number of the MSC
Time stamp when the GMSC receives the short
Event Time stamp M
message
SMS Result C
unsuccessful.
System Type M
system.
M
Number CDR.
2.1.10 Supplementary Service Call

An SS-Action record is generated by the VMSC if a supplementary service is
invoked for a mobile subscriber.
10 Table 11 SS-Action Record


Record Type M Supplementary service action
Served IMSI M IMSI of the MS performing the action
Served IMEI OC IMEI of the MS performing the action
Served MSISDN OM Primary MSISDN of the party performing the action
MS Classmark M Mobile station classmark
E.164 serial number of the MSC/VLR that generates
Recording Entity M the CDR (serial number of MSC/HLR: TON + NPI +
MSC ID)
LAC and SAC or CID of the called subscriber when
Location OM
the call is established.
Basic service types related to supplementary services.
Basic Services C This field is not provided if the action is applicable to
all basic services.
Supplementary service or group to which
Supplementary Service C supplementary services apply. This parameter is
unavailable in the case of USSD.
Supplementary service actions such as activation,
SS Action C deactivation, interrogation etc. It is unavailable in the
case of USSD.
SS Action time stamp M Time at which the action is requested
SS Parameters C Parameters and data related to supplementary services
SS Action Result C Result of the requested transaction if unsuccessful
Unique identifier of a call or conversation for a party
Call Reference M (A or B) in a call. It is also used to identify some
output CDRs that belong to the same connection.
System Type M
system.
M
Number CDR.
Forwarded Sub. Number C Forwarded sub-number
Time for no response before forwarding when a
No Reply CondTime C
mobile subscriber requests the forwarding service.
Hot Billing Tag2 C service and post-paid service subscribers are
distinguished.
2.1.11 Mobile Originated Emergency Call

A mobile originated emergency call (MOE) record is a type of record defined by
ZTE. It is generated when a mobile subscriber dials the emergency special service
5 number “112”.
Note: The CDR generated when an MS dials the number “119” or “110” is a
common CDR instead of an MOE CDR.
Table 12 MOC Emergency Record
Record Type M Emergent call record
IMSI of the calling party in the case of an emergency
Served IMSI C
call with a SIM card.
Served IMEI C IMEI of the calling ME
Primary MSISDN of the calling party in the case of an
Served MSISDN OC
emergency call with a SIM card.


Called number after digit translation within the MSC
(if applicable)
E.164 serial number of the MSC that generates an
Recording Entity M emergency call CDR (serial number of MSC/VLR:
TON + NPI + MSC ID)
Incoming trunk group through which the call is
Incoming TKGP OC originated in the MSC, usually trunk between the MSC
and the BSS.
Outgoing trunk group through which a call is released
Outgoing TKGP OC
at the originating MSC.
Location M (SAC) or cell ID (CID) of a subscriber when the
subscriber originates a call.
A list of changed in LAC. Each change in time-
stamped.
Indicate the teleservice “emergency call” is applied in
Basic service M
this call.
AOC Parameters OC AOC parameters sent to the MS during setup of a call.
New AOC parameters sent to the MS (for example,
Change of AOC
OC when the charge rate is changed), including the time
Parameters
when the new parameters are used.
MS Classmark M Mobile station classmark employed on call setup
A list of changes to the classmark during the
Change of classmark OC
connection. Each change is time-stamped.
Channel seizure time: time seized by channels during
calls
C
Answer time: time of answer for the called party in a
successfully connected call
OM
Release time: time of traffic channel released by the
calling or called party
Call duration M Call duration for charging
Radio channel type requested by MS (full rate/half
Radio Chan. Requested C
rate)
Radio channel type actually used by MS (full rate/half
Radio Chan. Used C
rate)
A list of changes of radio traffic channel in a
Change of Rad. Chan. C
Cause for termination M Cause for release of the connection
Diagnostics OM Detailed reason for release of the connection
Sequence No. of part of output CDRs. This parameter
Sequence no. C
is present only when some CDRs are output.
Call reference M (A or B) in a call. It is also used to identify some
System Type M
system.
Subscriber attribute registered by mobile subscribers
in the HLR
Destination number of the called party (often dialed by
Called Number OC
the calling party)
M
Number CDR.
Mobile station routing number employed to route this
Roaming Number OC
connection
The level of priority used by subscribers when
EMLP Priority Level C
invoking the eMLPP service
EMLP Request Priority The priority level of subscription when subscribers
C
Level invoke the eMLPP service.


OM
distinguished.
trunk.
trunk.
Name name.
Name name.
2.1.12 Mobile Originated Call Forwarding
A mobile originated call forwarding call (MCF) record is a type of record defined by
ZTE. It is generated for subscriber B at the MSC when subscriber A originates a call
to subscriber B and the call is forwarded to subscriber C.
5 Table 13 Mobile Originated Call Forwarding Record
Record Type M Mobile originated forwarding record
Type of forwarding, i.e forward on busy,forward on
Forward Type M
unconditional.
Served IMSI M IMSI of the subscriber originating call forwarding
Served IMEI OM IMEI of the forwarding ME
MSISDN of the subscriber originating call forwarding
Served MSISDN OM
(original called number)
Calling Number OM Address of the calling party
Called Number M Address of the forwarded-to party
Called number after digit translation within the MSC
(if applicable)
The number of the connected party if it is different
Connected Number OC from the original called number dialed by the calling
party.
Mobile station roaming number employed to route this
Roaming Number OC
connection (dynamic roaming number of subscriber C)
E.164 serial number of the MSC that generates the
Recording Entity M CDR for the calling party (serial number of
Incoming TKGP OM
originated at the forwarding MSC
Outgoing TKGP OM
at the forwarding MSC.
Bearer or teleservice employed. This parameter may
Basic service C not be available, for example, in the case of call
forwarding unconditional (CFU).


This parameter is present only when a teleservice is
Transparency Indicator C used in the transparent mode and non-transparent
mode.
A list of changes of basic service during a call
Supplementary service invoked as a result of this
Supplementary Services C
connection.
calls
C
OM
Data volume sent through the MSC when the data
Data volume C service borne by the circuit switched (CS) domain is
applied.
Sequence no. C
Is CAMEL Call OM
in the CDR.
Identification address of the CAMEL server used by
gsmSCF address C subscribers. This parameter is present only when the
CAMEL service is used by subscribers.
CAMEL service logic to be applied. This parameter is
Service key C
NCR used to correlate CDRs generated by network
Network Call Reference C elements to which a call passes when the CAMEL
service is applied.
E.164 code of the MSC in which the NCR is
MSC Address C generated. This parameter is present only when the
CAMEL service is applied.
Indicate that the CAMEL server initiates the call
CAMEL initiated CF
C forwarding. This parameter is present only when the
indicator
CAMEL service is applied.
Indicate whether the default call handling is used in a
Default call handling OC CAMEL call when the default call handling of
CAMEL is available.
Number of DP
OC Number of detection points (DP) encountered
encountered
CAMEL service level to be applied. This parameter is
Level of CAMEL service OC
Free format Data C
suffix. This parameter is present only when the
CAMEL service is applied and the SCP sends FCI
messages.
A series of CAMEL information IEs. Each IE contains
CAMEL call leg corresponding CAMEL call leg information. This
C
information parameter is present only when the CAMEL service is
applied.
C


This parameter indicates whether a call invokes the
default call handling of the second type of CAMEL
Default call handling 2 OC
service if the second type of CAMEL service is
available, for example, the dialed service.
This parameter indicates that a call invokes the SCF
address of the second type of CAMEL service if the
GsmSCF address 2 C
second type of CAMEL service is applied, for
example, the dialed service.
This parameter indicates the second service logic
Service key 2 C invoked by a call if the second type of CAMEL service
is available, for example, the dialed service.
the SCF for the second type of CAMEL service when
the second type of CAMEL service is applied, for
example, the dialed service. The data can be sent in an
FCI message or multiple FCI messages and indicated
by corresponding suffix.
This parameter indicates that the free format data in
Free format data append the CDR is appended to the previous partial output
C
indicator 2 CDR when the second type of CAMEL service is
applied, for example, the dialed service.
Subscriber attribute registered by mobile subscribers
in the HLR
System Type C
system.
M
Number CDR.
Number Of Forwarding C Number of times when a call is forwarded.
Is CUG Used OM
the call.
CUG InterLockCode C
bearer in the CS.
Rate Indication OC basic services between the MS or user equipment and
Rate at which the data generated for the HSCSD traffic
Fixed Network User Rate OC
is transmitted through the interface of PSTN/ISDN
OC
indicator call.
OC
CUG Outgoing Access
C CUG outgoing access is used.
Used
CUG Outgoing Access This parameter indicates that the calling subscriber has
C
Indicator made a CUG call with outgoing access.
distinguished.
Called Location OC This field indicates the location of the called


Calling Party OC This field indicates the roaming indicator of the
Roaming Indicator calling party.It is provided only when the calling
call.
trunk.
trunk.
Name name.
Name name.
2.1.13 Common Equipment Usage Call

A common equipment usage (CEU) record is generated to record the use of
conference circuits and conference connection duration when the multi-party service
5 is applied in a call.
Table 14 Common Equipment Usage Record
Record Type M Common equipment usage record
Type of common equipment, for example, conference
Equipment type M
circuit
Equipment Id. C Local ID of the equipment employed
Served IMSI M IMSI of the party that seizes the equipment
Served MSISDN OM Primary MSISDN of the served party
E.164 number of the MSC in which the equipment is
Recording Entity M
located
Basic service C Bearer services or telecom services employed
A list of changes of basic service during a call
Supplementary service invoked as a result of this
Supp. Services C
connection.
M Seizure time: start time when the equipment is used
Event time stamps:
OM Release time: time when the equipment is released
Call Duration M Total duration of usage of the equipment
Call Reference M (A or B) in a call. It is also used to identify some
Sequence no. C



M
Number CDR.
System Type M
system.
Rate Indication OC basic services between the MS or user equipment and
Rate at which the data generated for the HSCSD traffic
Fixed Network User Rate OC
is transmitted through the interface of PSTN/ISDN
distinguished.
2.1.14 Terminating CAMEL Interrogation Call

A terminating CAMEL interrogation (TCI) record is generated at the GMSC to
record the position information of the terminating subscriber.
5 Table 15 Terminating CAMEL Record
Record Type M Terminating CAMEL interrogation
Served IMSI M IMSI of the called party
Served MSISDN OM MSISDN of the called party
Recording Entity M E.164 number of the GMSC
Interrogation time stamp M Time when the interrogation is invoked.
CAMEL Destination Routing number after interrogation by the CAMEL
M
Number server
GsmSCF Address M Address of the CAMEL server serving subscribers
Service key M CAMEL service logic to be applied
An identifier used to correlate transactions on the same
Network Call Reference M
call taking place in different network nodes
E.164 number assigned to the MSC that generates the
MSC Address M
NCR.
Indicate whether the default call handling is used in a
Default call handling OC CAMEL call when the default call handling of
CAMEL is available.
Address of the called party received by the
Called Number M
GMSC/gsmSSF
Calling Number C Address of the calling party, if available
Incoming TKGP OC
originated at the forwarding MSC
Outgoing TKGP OC
at the forwarding MSC.
calls
C
OM
Data volume sent through the MSC when the data
Data volume OC service borne by the circuit switched (CS) domain is
applied.


Sequence no. C
Number of DP
OC Number of detection points (DP) encountered
encountered
Level of CAMEL service OC Level of CAMEL service applied
Free format Data C
suffix. This parameter is present only when the
CAMEL service is applied and the SCP sends FCI
messages.
A series of CAMEL information IEs. Each IE contains
CAMEL call leg corresponding CAMEL call leg information. This
C
information parameter is present only when the CAMEL service is
applied.
C
M
Number CDR.
This parameter indicates whether a call invokes the
default call handling of the second type of CAMEL
Default call handling 2 OC
service if the second type of CAMEL service is
available, for example, the dialed service.
This parameter indicates that a call invokes the SCF
address of the second type of CAMEL service if the
GsmSCF address 2 C
second type of CAMEL service is applied, for
example, the dialed service.
This parameter indicates the second service logic
Service key 2 C invoked by a call if the second type of CAMEL service
is available, for example, the dialed service.
the SCF for the second type of CAMEL service when
the second type of CAMEL service is applied, for
example, the dialed service. The data can be sent in an
FCI message or multiple FCI messages and indicated
by corresponding suffix.
This parameter indicates that the free format data in
Free format data append the CDR is appended to the previous partial output
C
indicator 2 CDR when the second type of CAMEL service is
applied, for example, the dialed service.
Indicate whether the CAMEL call handling is active in
MSC server indication C
the MSC server
distinguished.
trunk.
trunk.
Name name.
Name name.

2.1.15 HLR Interrogation

An HLR interrogation record is generated when the MSC interrogates mobile
subscriber information from the HLR.
Table 16 HLR Interrogation Record
Record Type M HLR interrogation record
Served IMSI C IMSI of the party being interrogated
Served MSISDN M MSISDN of the subscriber being interrogated
E.164 number of the GMSC (serial number of GMSC:
Recording Entity M
TON + NPI + MSC ID)
Basic Service OC Only for teleservice 21 (SMS-MT)
Routing number (MSRN or forwarding number)
Routing Number C
provided by the HLR for connection
Interrogation time stamp M Time when the interrogation is invoked.
Number of times when the call is forwarded through
Number of Forwarding C
the ISUP.
Interrogation Result C Result of the interrogation request if unsuccessful.
M
Number CDR.
distinguished.
5
2.1.16 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.
Table 17 LCS-MT record
Record Type M LCS-MT record.
Recording Entity M The E.164 number of the visited MSC producing
the record.
LCS Client Type M The type of the LCS client that invoked the LR.
LCS Client Identity M Further identification of the LCS client .
Served IMSI M The IMSI of the subscriber the LR is invoked for.
Served MSISDN OM The MSISDN of the subscriber the LR is invoked
for.
Location Type M The type of the location request.
LCS QoS C QoS of the LR, if available.
LCS Priority C Priority of the LR, if available.
MLC Number M The E.164 address of the requesting GMLC.
Event Time Stamp M The time at which the LR was received by the
MSC.
MeasureDuration OM The duration of proceeding the location request .
Notification To MS C The privacy notification to MS user that was
User applicable when the LR was invoked, if available.
Privacy Override C This parameter indicates if MS privacy was
overridden by the LCS client, if available.
Location OM The LAC and CI when the LR is received.


Location Estimate OC The location estimate for the subscriber if
contained in geographic position and the LR was
successful.
Positioning Data C The positioning method used or attempted, if
available.
LCS Cause OC The result of the LR if any failure or partial
success happened as known at the radio interface.
Detailed cause for failure or partial success of the
Diagnostics C
location service
System type applied for the location service,
System Type M
GERAN of the EDGE or UTRAN of WCDMA
A series of CDR extension information defined by
the network or manufacturer
M
Number CDR.
Cause for
M Cause for termination of the location service
Termination
Hot Billing Tag 2 C paid service and post-paid service subscribers are
distinguished.
2.1.17 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.
5 Table 18 LCS-MO record
Field Attr. Description
Record Type M LCS-MO record.
the record.
LCS Client Type C The type of the LCS client that invoked the LR, if
available.
LCS Client Identity C Further identification of the LCS client, if
available.
Served IMSI M The IMSI of the subscriber the LR is invoked for.
Served MSISDN OM The MSISDN of the subscriber the LR is invoked
for.
MOLR Type M The type of the LR.
LCS Priority OC Priority of the LR, if available.
MLC Number C The E.164 address of the involved GMLC, if
available.
MSC.
successful.

Field Attr. Description

available.
LCS Cause C The result of the LR if any failure or partial
success happened as known at the radio interface.
Diagnostics C
location service
System type applied for the location service,
System Type M
GERAN of the EDGE or UTRAN of WCDMA
A series of CDR extension information defined by
the network or manufacturer
M
Number CDR.
Indicate the calling party in the call is a hot billing
Hot billing tag C
subscriber.
Cause for
M Cause for termination of the location service
Termination
Hot Billing Tag 2 C paid service and post-paid service subscribers are
distinguished.
2.1.18 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.
5 Table 19 LCS-NI record
Record Type M LCS-NI record.
the record.
LCS Client Type C The type of the LCS client that invoked the LR, if
available.
LCS Client Identity C Further identification of the LCS client, if
available.
Served IMSI C The IMSI of the calling party the LR is executed
for if supplied by the UE.
Served MSISDN C The MSISDN of the calling party the LR is
executed for if supplied by the UE.
Served IMEI C The IMEI of the calling party the LR is executed
for if available.
EMS-Digits OC The emergency service routing digits, if
emergency call.
EMS-Key OC The emergency service routing key, if emergency
call.
LCS Priority C Priority of the LR, if available.
MLC Number C The E.164 address of the involved GMLC, if
available.
MSC.


successful.
available.
LCS Cause C The result of the LR if any failure or partial
success happened as known at the radio
interface.
Diagnostics C
location service
System type applied for the location service, GERAN
System Type M
of the EDGE or UTRAN of WCDMA
M
Number CDR.
Indicate the calling party in the call is a hot billing
Hot billing tag C
subscriber.
Cause for Termination M Cause for termination of the location service
distinguished.
2.1.19 USSD Operation Record

A record is generated by VMSC when the mobile or network originated a USSD
operation request.The record is used to record the original information of the
5 operation.
Table 20 USSD record


Record Type M USSD record
Served IMSI M IMSI of the served subscriber
Served IMEI C IMEI of the served ME , if available.
Served MSISDN M The primary MSISDN of the served party
MS Classmark M The mobile station classmark employed.
the record
Event time stamps: C Start time: start time of USSD request
C Answer:end time of USSD operation
Location M The identity of the cell or the SAC at the time of
CDR creation, including the location area code.
Call reference M A local identifier distinguishing between
USSD interaction count OM USSD interaction count
Unstructured SS Data M Unstructured SS Data
USSD operation code M USSD operation code
USSD data coding OM USSD data coding scheme
scheme
USSD Service Code M Service Code
Error code Oc Result of the attempted operation if the operation
is unsuccessful.
System Type M 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 set-up. For an open CDR in a 2G
NE (responsible for the CDR), the field is not
present (even if the call is handed off to a 3G air
interface). For a CDR in a 3G NE (responsible for
the CDR), the value unknown shall be used after
handover.
Hot Billing Tag 2 C Hot billing tag 2 defined by operators. The pre-
paid service and post-paid service subscribers
are distinguished.
Exchange Identity OM Identity of the VMSC that generates original bills.
Record Sequence M Record sequence number. It is the unique ID of a
Number CDR.
2.1.20 VIG Record

A record is generated by the VIG when a mobile terminal(e.g 3G-343M) is
interconnected with the video terminal of other network.The record is used to record
5 the charging information of vedio telephone service.
Table 21 VIG record


Record Type M Indicate the type of record is VIG
Calling Number C The number of the calling party if available.
Called Number C The number of the called party.Only provided
when the called party is a mobile subscriber
VIG Call Type M The direction of the call (i.e incoming,outgoing)
Event time stamps: C Start time:the start time of the call
C End time:the end time of the call
Call duration M The duration of the call
Cause for termination M The reason for the release of the call.
Diagnostics OC A more detailed reason for the release of the
connection.
Sequence no. C Partial record sequence number, only present in case
of partial records.
Call reference M A local identifier distinguishing between
Call Data Rate M The Data Rate of the call which is represented by
kbps
Exchange Identity OM Identity of the VMSC that generates original bills.
Number CDR.
2.1.21 MGCF
MGCF is the media gateway control function between CS domain and IMS
subsystem.A record is generatedat MGCF when a session is established between the
5 CS subscriber and an IMS subscriber.
Table 22 MGCF record


Record Type M Identifies the type of record. The parameter is
derived from the Node functionality parameter.
Retransmission OC This parameter, when present, indicates that
information from retransmitted Charging Data
Requests has been used in this CDR
SIP Method OC Specifies the SIP-method for which the CDR is
generated. Only available in session unrelated
cases.
Role of Node OM This field indicates the role of the MGCF.
Node Address OM This item holds the address of the node providing
the information for the CDR. This may either be
the IP address or the FQDN of the IMS node
generating the accounting data.
Session ID OM The Session identification. For a SIP session the
Session-ID contains the SIP Call ID as defined in
the Session Initiation Protocol RFC 3261 [404].
Calling Party Address OM The address (Public User ID) of the party
requesting a service or initiating a session. This
field holds either the SIP URL (according to IETF
RFC 3261 [404]) or the TEL URL (according to
RFC 2806 [403]) of the calling party.
Called Party Address OM In the context of an end-to-end SIP transaction
this field holds the address of the party (Public
User ID) to whom the SIP transaction is posted.
Service Request Time OM This field contains the time stamp which indicates
Stamp the time at which the service was requested. This
parameter corresponds to SIP Request
Timestamp. Present with Charging Data Request
[Start] and Charging Data Request [Event].
Service Delivery Start OM This field holds the time stamp reflecting either:
Time Stamp successful session set-up, a delivery unrelated
service, an unsuccessful session set-up and an
unsuccessful session unrelated request. This
parameter corresponds to SIP Response
Timestamp. Present with Charging Data Request
[Start] and Charging Data Request [Event].
Service Delivery End OC This field records the time at which the service
Time Stamp delivery was terminated. It is Present only in SIP
session related case. This parameter
corresponds to SIP Request Timestamp. Present
with Charging Data Request [Stop].
Record Opening Time OC A time stamp reflecting the time the CDF opened
this record. Present only in SIP session related
case.
Record Closure Time OM A Time stamp reflecting the time the CDF closed
the record.
Inter Operator OC Holds the identification of the home network
Identifiers (originating and terminating) if exchanged via SIP
signalling, as recorded in the P-Charging-Vector
header.
Originating IOI OC This parameter corresponds to Orig-IOI header of
the P-Charging-Vector defined in TS 24.229
[204].
Terminating OC This parameter corresponds to Term-IOI header
IOI of the P-Charging-Vector defined in TS 24.229
[204].
Local Record OM This field includes a unique record number
Sequence Number created by this node. The number is allocated
sequentially for each partial CDR (or whole CDR)
including all CDR types. The number is unique
within the CDF.
Record Sequence OC This field contains a running sequence number
Number employed to link the partial records generated by
the CDF for a particular session.


Cause For Record OM This field contains a reason for the close of the
Closing CDR.
Incomplete CDR OC This field provides additional diagnostics when
Indication the CDF detects missing Charging Data
Requests.
IMS Charging Identifier OM This parameter holds the IMS charging identifier
(ICID) as generated by the IMS node for the SIP
session.
SDP Session OC Holds the Session portion of the SDP data
Description exchanged between the User Agents if available
in the SIP transaction.
List of SDP Media OC This is a grouped field comprising several sub-
Components fields associated with one media component. It
may occur several times in one CDR. The field is
present only in a SIP session related case.
SIP Request OM This parameter contains the time of the SIP
Timestamp Request (usually a (Re)Invite). This parameter
corresponds to SIP Request Timestamp in
Charging Data Request [Interim].
SIP Response OM This parameter contains the time of the response
Timestamp to the SIP Request (usually a 200 OK). This
parameter corresponds to SIP Response
Timestamp in Charging Data Request [Interim].
SDP Media OM This is a grouped field comprising several sub-
Components fields associated with one media component.
Since several media components may exist for a
session in parallel these sub-fields may occur
several times.
SDP OM This field holds the name of the media as
Media Name available in the SDP data. This parameter
corresponds to SDP-Media-Name.
SDP OM This field holds the attributes of the media as
Media Description available in the SDP data.
OM This parameter holds the GPRS charging ID
GPRS (GCID) which is generated by the GGSN for a
Charging ID GPRS PDP context.
OC This field indicates if the called party has
Media Initiator requested the session modification and it is
Flag present only if the initiator was the called party.
GGSN Address OC This parameter holds the control plane IP
address of the GGSN that handles one or more
media component(s) of a IMS session.
Service Reason Return OM This parameter provides the returned SIP status
Code code for the service request for the successful
and failure case,
Trunk Group ID OM Contains the outgoing trunk group ID for an
Incoming/Outgoing outgoing session/call or the incoming trunk group
ID for an incoming session/call.
Bearer Service OM Holds the used bearer service for the PSTN leg.
Record Extensions OC A set of operator/manufacturer specific
extensions to the record, conditioned upon
existence of an extension.
2.1.22 MTP3 Signnaling Record

A MTP3 signnaling record is used to collect the usage of MTP3 signnaling in
MSCServer and MGW. If it is configured to output MTP3 billing and billing
5 validate record, the record is output periodically. The period can be configured by
man-machine interface.
Table 23 MTP3 Signnaling Record

Record Type M Identifies the type of record.

Number CDR.
Bill Type M The type of the record. The value of the field can
be charging or charging validate.
Service Identifier M The service identifier of MTP3 message
SPC M The SPC code of the MSCServer or MGW that
generate the record.
OPC M The SPC code of the MTP3 message originating
node.
DPC M The SPC code of MTP3 message destination node
Charged Neighbor M The SPC code of the charged neighbor
SPC
Amount Of Messages M The amount of messages from the opc to dpc
during the statistic period.
Amount Of Octets M The amount of octets from the opc to dpc during
the statistic period
Record Opening M The opening time of the record
Time
Record Closing Time M The closing time of the record
Physical Location M The field is used to identify the MP that generate
the record
2.1.23 SCCP Signnaling Record

A SCCP signnaling record is used to collect the usage of SCCP signnaling in
MSCServer and MGW. If it is configured to output SCCP billing and billing validate
5 record, the record is output periodically. The period can be configured by man-
machine interface.
Table 24 SCCP Signnaling Record

Record Type M Identifies the type of record.
Number CDR.
Bill Type M The type of the record. The value of the field can
be charging or charging validate.
SPC M The SPC code of the MSCServer or MGW that
generate the record.
OPC M The SPC code of the SCCP message originating
node.
DPC M The SPC code of SCCP message destination node
SSN M The SSN of the SCCP signnaling
Amount Of Global M The amount of SCCP messages that have been GT
Translated Messages translated by the node
Record Opening M The opening time of the record
Time
Record Closing Time M The closing time of the record
Physical Location M The field is used to identify the MP that generate
the record

2.2 Description of Fields

2.2.1 Additional Charging Information
The field is correspond to the ASN.1 field “additionalChgInfo”.
5 This field consists of two parts, a charge indicator and other charging parameters.
The charge indicator is derived from the information contained in the ISUP
“backward call indicator” and may be used to store a charge indicator (charge/no
charge) received from another network node. Other parameters are non-standard and
intended to permit inclusion of further charging information received from the
10 Intelligent Network and/or value added service nodes.
2.2.2 Amount Of Global Translated Messages

This field is correspond to the ASN.1 field “amountOfGTMessages”.
This field contains the amount of global translated SCCP signaling messages in
15 current node.
2.2.3 Amount Of Messages

This field is correspond to the ASN.1 field “amountOfMessage”.
This field contains the amount of MTP3 signnaling messages transferred from the
20 originating node to the destination node by current node.
2.2.4 Amount Of Octets

This field is correspond to the ASN.1 field “amountOfOctets”.
This field contains the octets of MTP3 signnaling messages transferred from the
25 originationg node to the destination node by current node.
2.2.5 AoC Parameters / Change of AoC Parameters

The field is correspond to the ASN.1 field “aocParameters/changeOfAOCParms”.
The AoC parameter field contains a set of charge of advice (AoC) parameters sent to
30 an MS on call setup. If more sets of parameters are sent during a call, for example as
a result of change in charge rate, this may be recorded in the Change of AoC
Parameter field including the time at which the change occurs.
Note that the Change of AoC Parameters field is optional and is not required if
partial records are generated for change of the charge rate. AoC parameters are
35 defined in 3GPP TS 22.024.
2.2.6 Basic Service/Change of Service/ISDN Basic Service

The field is correspond to the ASN.1 field “basicService/changeOfService/
isdnBasicService”.

The basic service field contains the code of basic service employed on call setup.
Any change for the basic service during a connection shall be recorded in the change
of service field, including the time at which the change takes place.
The change of service field is optional and may be omitted if partial records are
5 generated when the basic service is changed.
The coding of basic services are defined in detail in 3GPP TS 29.002.
The basic service employed is generally not recorded in the transit CDR. However,
if the device at which a call is originated or terminated through ISDN signaling
messages, the corresponding ISDN basic service code shall be recorded in the CDR.
10 One possible example is the direct connection of an ISDN PABX to the MSC/VLR
2.2.7 Bearer Service(MGCF)

The field is correspond to the ASN.1 field “bearerService” in MGCF record.
Holds the used bearer service for the PSTN leg.
152.2.8 Bill Type

The field is correspond to the ASN.1 field “billType”.
This field is used to identify the record is for billing or billing validate.
2.2.9 BSC Identification

20 The field is correspond to the ASN.1 field “bSCIdentification”
This field indicates the BSC spc code where the served subscriber is located when
the call is started.This field is provided only when 2G radio access technology is
used.
252.2.10 Call Duration

The field is correspond to the ASN.1 field “callDuration”.
This field contains relevant call duration in seconds. For complete (answered) calls,
it is the chargeable duration from when the calls are answered to when the channel is
30 released. For some records, it is the duration of the CDRs of the parts instead of the
cumulative duration of the call.
Note 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
rounding or truncation of the measured duration to an integer of seconds.
35 Whether the rounding or truncation is to be used for the MSC is beyond the scope of
this document. However, the following principles shall be complied with:
1) The CDR whose call duration is 0 second shall not be generated.
2) The same method of truncation or rounding shall be applied to both single
and partial records.
40 If CAMEL is invoked for the call and a control relationship is existing, the call may
continue after the gsmSSF receives a RELEASE or a DISCONNECT from the
called party. The call duration of the incoming leg is stored in the major CDR, and
the duration of outgoing leg is stored in the corresponding CAMEL information
module.

The figure below gives an example on how to use call duration and time stamp. It
shows how an MS controlled by the CAMEL originates an intelligent service.
The uppermost arrow  marks the overall duration of the call that is to be measured
and stored in the main body of the corresponding MOC record. The duration before
5 t5 (incoming leg) or t4 (outgoing leg) needs not to be stored because the call is
answered later. The call duration in the first outgoing leg module contains the time
interval from t4 to t6 (period). The call duration measurement for the second
outgoing leg starts with t9 and end at t10 (interval).
(The timestamps t1, t2, t3, t7, t8 and t12 are mentioned for the sake of completion
10 only.) )

inc. leg

outg. leg 1
outg. leg 2 

outg. leg 3
time
t1 t2 t3 t4 t5 t6 t7 t8 t9 t10 t11 t12 t13
call duration of incoming leg =

call duration of outgoing leg =
holding time of outgoing leg =
Signaling Message Sent/Received

Time Point Recording Duration
Trigger Detection Point Encountered
t1 SETUP; TDP(control)
t2 IAM seizure of outg. leg 1
t3 ACM
t4 ANSWER start of call duration (outg. leg 1)
t5 CONNECT start of call duration (inc. leg)
t6 RELEASE; EDP(control) stop of call duration (outg. leg 1)
t7 IAM seizure of outg. leg 2
t8 ACM
t9 ANSWER start of call duration (outg. leg 2)
t10 RELEASE; EDP(control) stop of call duration (outg. leg 2)
seizure of outg. leg 3
t11 IAM
start of holding time (outg. leg 3)
t12 ACM
t13 RELEASE; EDP(control) stop of holding time (outg. leg 3)
2.2.11 Call Reference

15 The field is correspond to the ASN.1 field “callReference”.
This field is derived from transactions defined in 3GPP TS24.008 and uniquely
identifies a call or transaction at one side of the call (party A or party B). It is also
used to identify some output CDRs that belong to the same connection.
20 To make it clear, the global call reference is not provided in the GSM system. The
call reference field cannot be used to combine MOC and MTC records for end-to-
end connections.
2.2.12 Called Party Address(MGCF)

The field is correspond to the ASN.1 field “called-Party-Address”.
25

In the context of an end-to-end SIP transaction this field holds the address of the
party (Public User ID) to whom the SIP transaction is posted.
For a subscription/registration procedure this field holds the party to be
registered/subscribed.
5 This field contains either a SIP URL (according to IETF RFC3261 or a TEL URL
(according to RFC2806).
2.2.13 Calling Party Address(MGCF)

The field is correspond to the ASN.1 field “calling-Party-Address”.
10 The address (Public User ID) of the party requesting a service or initiating a session.
This field holds either the SIP URL (according to IETF RFC 3261) or the TEL URL
(according to RFC 2806) of the calling party. The address is obtained from the P-
Asserted-Identity header.
2.2.14 Calling/Called Location

15 The field is correspond to the ASN.1 field “callingLocation/calledLocation”
This field indicates the location of the calling/called subscriber when the call is
started.
2.2.15 Calling/Called Party Roaming Indicator

20 The field is correspond to the ASN.1 field
“callingPartyRoamingInd/calledPartyRoamingInd”
This field indicates the roaming number of the calling/called party.The field is
provided if the calling/called subscriber is roaming when the call is started.
252.2.16 Calling/Called/Connected/Translated Number

The field is correspond to the ASN.1 field
“callingNumber/calledNumber/connectedNumber/translatedNumber”.
In general, the number is an ITU-T E.164 number. However, other number plans
30 such as X.121 can also be included. Each of these fields contains number type and
number plans defined in 3GPP TS24.008 in detail. Where appropriate, these fields
may also contain the display and screening information defined in 3GPP TS24.008.
Called numbers are the ones received from MSs on mobile originated call setup as
defined in 3GPP TS24.008. Similarly, calling numbers are the ones received from
35 the network on mobile terminated call setup. In case of CAMEL initiated call
forwarding (CF), the called (forwarded-to) number is returned by CAMEL.
Translated numbers are the ones received from MSs and then converted by the MSC
server.
Connected numbers are the ones of the connected party as defined in 3GPP
40 TS24.008. It may be the same as or different from the called number. The following
examples describe the use of these fields.
Example 1: A called number is the connected number.
Normal calls from a mobile subscriber to a mobile or PSTN subscriber.
Example 2: A called number is not the connected number.

In the case of routing to the PABX with the automatic call distribution function or to
an ISDN basic access with multiple devices, the connected number is the one in the
number group of the party finally connected.
Example 3: Numbers in the MTC record generated for subscriber B when subscriber
5 A calls subscriber B and the call is forwarded to subscriber C.
In the case of call forwarding, the connected number in the MTC record for
subscriber B is the number of subscriber C and the calling number is the number of
subscriber A.
Example 4: Translated number
10 Called number received from an MS and converted based on digit translation by
the MSC server.
2.2.17 Calling Party Number

The field is correspond to the ASN.1 field “originalCalledPartyNumber ” in
CAMELModificationParameters.
15
This field contains called numbers modified by the CAMEL service.
2.2.18 CAMEL Call Leg Information

The field is correspond to the ASN.1 field “cAMELCallLegInformation”.
20 This field contains a group of CAMEL information elements (IEs) based on the
number of outgoing CAMEL call legs.
2.2.19 CAMEL Information

The field is correspond to the ASN.1 field “CAMELInformation”.
25 This field contains a list of parameters related to one CAMEL outgoing call leg.
As a network option, parameters that are identical to the corresponding values in the
high-level structure of records are not recorded again. That means if this group of
parameters does not contain a value, the value provided in the basic record is valid.
This may lead to an empty or even absent structure, if no parameters are modified.
302.2.20 CAMEL Initiated CF Indicator

The field is correspond to the ASN.1 field “cAMELInitCFIndicator”.
The purpose of this field is to distinguish CAMEL call forwarding from the standard
GSM call forwarding.
35 From the view of basic call state model (BCSM), this field is set to “CF” as long as
the originating CAMEL subscription information (O_CSI) is applied after the
destination is changed for the terminating CAMEL call processing. To make it clear,
this indicator does not depend on the call parameters (that is, redirection
information) received in the CAP_CONNECT message of other terminating
40 CAMEL subscription information (T_CSI) service. This indicator also indicates that
another record may be generated. The record contains the charging information
related to the terminating CAMEL service and the charging information related to
the originating CAMEL service.

2.2.21 CAMEL Modified Service Centre

The field is correspond to the ASN.1 field “cAMELSMSCAddress”.
This field contains SMS-SC address modified by CAMEL service. If this field is
5 present, the Service Centre field contains the SMS-SC address before being
modified by the CAMEL service.
2.2.22 CAMEL SMS Information

The field is correspond to the ASN.1 field “CAMELSMSInformation”.
10 This field contains the following CAMEL information for mobile originated SMS.
 Default SMS handling
This field indicates whether the CAMELserivice encounters the default SMS handling.
The field is present only when the default SMS handling is applied.
 Free format data
15  Calling party number
This field contains calling numbers modified by the CAMEL service.
 CAMEL modified service center
This field contains the SMS-C address modified by the CAMEL service.
 Destination subscriber number
20 This field contains SMS destination numbers modified by the CAMEL service.
 Destination SmsRefrenceNumber
This field contains SMS call reference number.
2.2.23 Cause for Termination

The field is correspond to the ASN.1 field “CauseForTern”.
25
This field contains possible causes for common release, including:
 Normal release
 CAMEL initiated call release
 Partial record generation
30  Partial record upon call re-establishment
 Unsuccessful call attempt
 Abnormal release in the normal stage
 Location service request originated by unauthorized network
 Location service request originated by unauthorized client
35  Location method failure upon execution of location service
 Unknown or unreachable LCS client upon location service request
 False answer charge.
More detailed causes can be found in the diagnostics field .

2.2.24 Channel Coding Accepted/Channel Coding Used

“chanCodingsAcceptable/chanCodingUsed”.
5 This field contains a list of traffic channel coding for HSCSD connections accepted
or negotiated by the MS. It is present in the CDRs of HSCSD connections only.
2.2.25 Charged Neighbor SPC

This field is conrrespond to the ASN.1 field “chargedNeighbor”.
10 This field contains the charged neighbor SPC code.
2.2.26 CS Allocation/Retention Priority (CARP)

The field is correspond to the ASN.1 field “carp”.
CS allocation/retention priority (CARP) of visiting international roaming

15 subscribers.
Allocation/Retention Priority is a parameter in the UMTS QoS parameters. It
specifies important parameters for the mapping between non-UMTS QoS
parameters and UMTS QoS parameters. This field is present in the CDRs for
international roaming subscribers.
202.2.27 CUG Category

The field is correspond to the ASN.1 field “cUGCategory”.
This field is reserved for extention.
2.2.28 CUG InterLockCode

25 The field is correspond to the ASN.1 field “cUGInterLockCode”.
This field is used to identify different CUGs in the same network.

In MOC CDRs, the CUG interlock code indicates that the subscriber has made a
CUG call.
30 In MTC CDRs, the CUG interlock code indicates that the subscriber receives a CUG
call from a subscriber of another CUG.
In call forwarding CDRs, the CUG interlock code indicates that the subscriber has
forwarded a CUG call.
In roaming call forwarding CDRs, the CUG interlock code indicates that the calling
35 subscriber has made a CUG call.
2.2.29 CUG Index

The field is correspond to the ASN.1 field “cUGIndex”.
This field contains the codes of user groups. It is significant between subscribers and
40 network only.

2.2.30 CUG Incoming Access Indicator

The field is correspond to the ASN.1 field “cUGIncomingAccessInd”.
This field indicates the group access capability of users.
52.2.31 CUG Incoming Access Used

The field is correspond to the ASN.1 field “cUGIncomingAccessUsed”.
This parameter indicates the subscriber has subscribed to CUG supplementary

service and received a call from external CUGs.
102.2.32 CUG Outgoing Access Used

The field is correspond to the ASN.1 field “cUGOutgoingAccessUsed”.
This parameter indicates that the subscriber has subscribed to the CUG
supplementary service and made a non-CUG call or CUG call.
152.2.33 CUG Outgoing Access Indicator

The field is correspond to the ASN.1 field “cUGOutgoingAccessIn”.
This parameter indicates the CUG outgoing access capability.
2.2.34 Data Rate

20 The field is correspond to the ASN.1 field “dataRate”.
This field indicates the rate of the data service.

In non-transparent services, the wanted air-interface user rate (WAIUR) of the BC is
used.
25 In transparent services, the fixed network user rate (FNUR) is used.
2.2.35 Data Volume

The field is correspond to the ASN.1 field “dataVolume”.
This field contains the number of 64-byte segments transmitted during the use of
30 data services.
2.2.36 DDCFlag
The field is correspond to the ASN.1 field “dDCFlag”
This field indicates that the Direct Collect Call service is used.
352.2.37 Default Call/SMS Handling

“defaultCallHandling/defaultSMSHandling”.

This field indicates whether the CAMEL default call handling is available. This field
is present only when default call handling is applied. This parameter is defined in the
HLR as part of CAMEL subscription information.
2.2.38 Destination Number

5 The field is correspond to the ASN.1 field “destinationNumber”.
This field contains the destination number to which short messages are sent.
2.2.39 Diagnostics
The field is correspond to the ASN.1 field “diagnostics”.
10
This field contains a more detailed technical reason for release of a connection, and
the reason may be one of the following:
 A MAP error from 3GPPTS29.002
 A cause from 3GPPTS24.008
15  A cause from 3GPPTS29.078
 A cause from ISUP Q.767
The diagnostics information can also contain the specific information of
manufacturer and network.
2.2.40 Dialed Number

20 The field is correspond to the ASN.1 field “dialledNumber”.
Number dialed by subscribers. It is used in originating calls only.
2.2.41 DPC
The field is correspond to the ASN.1 field “dPC”.
25
This field contains the SPC code of the destination node that will be billed or
validated.
2.2.42 EMLP Priority Level

The field is correspond to the ASN.1 field “eMLPPriorityLevel”.
30
This field indicates the actually used priority level when the eMLPP service is
invoked.
2.2.43 EMLP Request Priority Level

The field is correspond to the ASN.1 field “eMLPRequestPriorityLevel”.
35
This field indicates the subscription priority level when the eMLPP service is
invoked.

2.2.44 EMS-Digits
The field is correspond to the ASN.1 field “emsDigits”.
This parameter is applicable to the emergency service in North America and gives
5 routing numbers defined in TS 29.002.
2.2.45 EMS-Key
The field is correspond to the ASN.1 field “emsKey”.
This parameter is applicable to the emergency service in North America and gives
10 the routing key defined in TS 29.002.
2.2.46 Equipment ID
The field is correspond to the ASN.1 field “equipmentId”.
This field contains a local ID used to distinguish equipment of the same type, for
15 example, the number of the conference circuit employed if multiple conference
circuits are available.
2.2.47 Equipment Type

The field is correspond to the ASN.1 field “equipmentType”.
20 This field contains the type of common equipment employed, for example,
conference circuit for the multi-party service.
2.2.48 Error Code

The field is correspond to the ASN.1 field “errorCode”.
25 This field contains the reason for unsuccessful USSD operation.
2.2.49 Event Time Stamps

The field is correspond to the ASN.1 field “seizureTime/ answerTime/
releaseTime/originationTime/deliveryTime/eventTime/ ssActionTime”.
30 These fields contain possible time stamps in a CDR.

In a CDR, there are two important call processing time stamps:
 Time when a call is answered or the charging starts (answer time)
 Time at which a call is released (release time)
For mobile originated calls, the answer time is the time when the CONNECT
35 message is sent to the calling party. For mobile terminated calls, the answer time
refers to the time when the CONNECT message is received from the called party.
However, if the subscriber has subscribed to the AoC service, the answer time is
derived from the time at which the FACILITY message containing AoC parameters
is received from the MS. If the AoC parameters are changed during a call, the time
40 stamp for change of AoC charging level records the time when the MS received the
FACILITY message. For a subscriber with AOC information level, the recorded

change time is the time at which the FACILITY message is sent to the MS. In case
of call re-establishment, the answer time is the time at which a new traffic channel is
allocated by the MSC, that is, when the ASSIGN COMMAND is sent to the MS.
The Release time is the time at which a connection is released by either one party,
5 that is, a DISCONNECT or RELEASE message is sent by the network or a
DISCONNECT message is received from the MS. In the case of link failure, the
release time is the time at which the MSC detects the failure.
For successful calls, the answer time is mandatory, and the release time is optional.
The recorded call duration is the chargeable duration, that is, the difference between
10 the answer stamp and release time stamp.
The event records include the following time stamps:
 HLR-int time: receipt of a MAP_SEND_ROUTING_INFO request
from the HLR
 Loc.Upd. time: receipt of a MAP_UPDATE_LOCATION_AREA
15 request from the HLR or a MAP_UPDATE_LOCATION request
from the HLR
 SS-Action: receipt of a supplementary service request from the VLR,
for example, MAP_REGISTER_SS, MAP_INVOKE_SS
 SMS-MO: receipt of an RP_DATA message from the MS containing
20 an SMS_SUBMIT data unit
 SMS-MT: an RP_DATA message containing the SMS_DELIVER
data unit sent to the MS
Note that the events listed above are used to demonstrate the principles only.
A time stamp shall contain date, hour, minute, and second at least.
252.2.50 Exchange Identity

The field is correspond to the ASN.1 field “exchangeIdentity”.
Identity of the MSC that generates original bills.
2.2.51 Fixed Network User Rate

30 The field is correspond to the ASN.1 field “fnur”.
This field indicates the user data rate applied for the connection in the fixed
network. In the UMTS, it is provided for all bearer services as specified in TS
22.002. In the GSM system, this parameter is part of the HSCSD connection
35 parameters.
2.2.52 Free Format Data

The field is correspond to the ASN.1 field “freeFormatData/freeFormatData-2”.
This field contains charging information sent by the gsmSCF in an FCI message as
40 defined in 3GPP TS 29.078. The data can be transmitted in one FCI message or
several FCI messages containing the append indicator. The free format data is
transmitted transparently to the charge CDRs and recorded. In the first call leg, the

data is recorded in the major CDRs. In other legs, the data is recorded in
corresponding sub-CDR.
If the FCI is received more than once during an ongoing incoming/outgoing
CAMEL call leg, the append indicator defines whether the FCI information is
5 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 case of partial output, the currently valid “free format data” is stored in the
partial record.
102.2.53 Forward Call Indicator

The field is correspond to the ASN.1 field “forwardCallIndicator”
This field is only provided in the incoming gateway record,it is used to identify the
type of the originating party of the call. e.g. international or national
152.2.54 Forward Type

The field is correspond to the ASN.1 field “mcfType”.
This field records the type of forwarding, e.g forward on busy, forward on
unconditional.
20
Note: Forward type 254 is used to identify the call back leg triggered by the overlay
method. It is configurable whether to generate the call back forwarding CDR. The
value 254 is only used in France OMT project.
2.2.55 Forwarded Sub. Number

25 The field is correspond to the ASN.1 field “forwardedSubNumber”.
This field indicates the forwarded sub-address. It is used with the forwarded-to
number.
A sub-address is used to identify subscriber terminals connected through the ISDN
30 network interface. A sub-address is transmitted transparently in the network, and it is
checked and verified through user terminals.
2.2.56 Free Format Data Append Indicator

The field is correspond to the ASN.1 field “freeFormatDataAppend/
freeFormatDataAppend-2”.
35
This field indicates whether free format data is to be appended to the free format
data stored in the previous partial CDR. This field is used to sort out valid free
format data from CDRs during CDR post-processing. Partial records are
independent of received FCIs. Thus, valid free format data may be divided into
40 different partial records.
If field does not exist, the free format data in a CDR will overwrite all the free
format data received in the previous CDRs. The append indicator is not required in
the first CDR. In the following partial CDR indicators, a real value shall be assigned
to the partial CDR that receives an append indicator with the FCI during output of

the CDR. If one or more FCIs without append indicator are received from a call leg
during output of the CDR, this field does not exist.
2.2.57 Gateway Record Type

The field is correspond to the ASN.1 field “gatewayRecordType”
5
This field indicates the type of the trunk. e.g.gateway,trunk
2.2.58 GGSN Address(MGCF)

The field is correspond to the ASN.1 field “gGSNaddress”.
10 This parameter holds the control plane IP address of the GGSN that handles one or
more media component(s) of a IMS session. If GPRS is used to access the IMS, the
GGSN address is used together with the GPRS charging ID as the access part of the
charging correlation vector. The charging correlation vector is comprised of an
access part and an IMS part, which is the IMS Charging Identifier. For further
15 information regarding the composition of the charging correlation vector refer to the
appropriate clause in TS 32.200 [2].
2.2.59 GPRS Charging ID(MGCF)

The field is correspond to the ASN.1 field “gPRS-Charging-Id”.
20 This parameter holds the GPRS charging ID (GCID) which is generated by the
GGSN for a GPRS PDP context. There is a 1:1 relationship between the GCID and
the PDP context. If GPRS is used to access the IMS, the GCID is used together with
the GGSN address as the access part of the charging correlation vector that is
comprised of an access part and an IMS part, which is the IMS Charging Identifier.
25 For further information regarding the composition of the charging correlation vector
refer to the appropriate clause in TS 32.200 [2].
2.2.60 GsmSCF Address

The field is correspond to the ASN.1 field “gsmSCFAddress/ gsmSCFAddress_2”.
30 This field indicates the address of CAMEL service controller serving subscribers.
The address is defined in the HLR as a part of CAMEL subscriber information.
2.2.61 Guaranteed Bit Rate

The field is correspond to the ASN.1 field “guaranteedBitRate”.
35 This field contains the guaranteed bit rate of transparent CS data services described
in TS 27.001 and the requested AIUR from non-transparent CS data services. The
guaranteed bit rate can be used in the UMTS to help control the rate and allocate
resources based on available resources. Referring to TS 22.002, UMTS bearer
services provide the guaranteed bit rate for subscribers or applications.
40 Operators can choose to provide a value that is smaller than or equal to the WAIUR.
Note if the WAIUR is smaller than or equal to 14.4 kbit/s, the guaranteed bit rate and
the maximum bit rate shall be set to 14.4 kbit/s.

2.2.62 Hot Billing Tag

The field is correspond to the ASN.1 field “hotBillingTag”.
This field indicates the hot billing tag defined by operators. The value “1” indicates
5 the hot billing service, and the value “0” indicates non-hot billing service.
2.2.63 Hot Billing Tag 2

The field is correspond to the ASN.1 field “hotBillingTag2”.
This filed indicates hot billing tag 2 defined by operators. It distinguishes the pre-
10 paid service and post-paid service subscribers. The value “1” indicates pre-paid
subscribers, and the value “0” indicates post-paid subscribers.
2.2.64 HSCSD Parameters/Change of HSCSD Parameters

The field is correspond to the ASN.1 field “ hSCSDChanRequested/
hSCSDChanAllocated/ changeOfHSCSDParms/ fnur/ aiurRequested/
15 chanCodingsAcceptable/ chanCodingUsed”.
The basic HSCSD parameters are negotiated between the MS and the network
during call setup. The parameters consist of the following:
 Fixed network user rate (FNUR) (optional)
20  Total AIUR requested by the MS (for non-transparent HSCSD
connections only)
 Channel No. list accepted by MS
 Maximum number of voice channels accepted by MS (indicated in
the channels requested field)
25  Channel No. and number of voice channels actually used for a call
In case that the network or a subscriber initiates the update procedure during a call,
the requested AIUR, the applied channel No. and the number of voice channels
requested or applied shall be recorded in the Change of HSCSD Parameters field
together with the time when the change takes place and the entity requested to be
30 changed.
It should be noted that the Change of HSCSD Parameters field is optional and not
required if partial records are generated when a change of HSCSD parameters takes
place.
2.2.65 IMS Charging Identifier(MGCF)

35 The field is correspond to the ASN.1 field “iMS-Charging-Identifier”.
This parameter holds the IMS charging identifier (ICID) as generated by the IMS
node for the SIP session. The value of the ICID parameter is identical with the 'icid-
value' parameter defined in[xx]. The 'icid-value' is a mandatory part of the P-
40 Charging-Vector and coded as a text-based UTF-8 charset (as are all SIP messages).
For further information regarding the composition and usage of the P-Charging-
Vector refer to TS 32.200 [2], TS 24.229 [79] and[xx].
The ICID value is globally unique across all 3GPP IMS networks for a time period
of at least one month, implying that neither the node that generated this ICID nor

any other IMS node reuse this value before the uniqueness period expires. The one
month minimum uniqueness period counts from the time of release of the ICID, i.e.
the ICID value no longer being used. This can be achieved by using node specific
information, e.g. high-granularity time information and/or topology/location
5 information. The exact method how to achieve the uniqueness requirement is an
implementation issue.
An ICID is generated by the P-CSCF during the initial IMS registration procedure for
a Private User ID. This ICID is valid for all Public User IDs registered for that
Private User ID until the user (Private User ID) is deregistered. All subsequent SIP
10 session unrelated methods (e.g., REGISTER, NOTIFY, MESSAGE etc.) must use
this ICID value regardless of whether the same Public User ID is used or not.
At each SIP session establishment a new, session specific ICID is generated at the
first IMS network element that processes the session-initiating SIP INVITE
message. This ICID is then used in all subsequent SIP messages for that session
15 (e.g., 200 OK, (re-)INVITE, BYE etc.) until the session is terminated.
2.2.66 Incoming/Outgoing Cic

The field is correspond to the ASN.1 field “incomingCic/outgoingCic”
20 This field indicates the cic value of the incoming/outgoing trunk.
2.2.67 Incoming/Outgoing TKGP

“mscIncomingTKGP/mscOutgoingTKGP”.
25 An incoming trunk group indicates the trunks through which calls are originated at
the MSC. It is a BSS trunk for mobile originated calls. Similarly, the outgoing trunk
group indicates trunks used for outgoing calls.
2.2.68 Incoming/Outgoing TKGP Name

30 “incomingTKGPName/outgoingTKGPName”
This field indicates the incoming/outgoing trunk group name.
2.2.69 Incomplete CDR Indication(MGCF)

The field is correspond to the ASN.1 field “incomplete-CDR-Indication”.
35
This field provides additional diagnostics when the CCF detects missing ACRs.
2.2.70 Inter Operator Identifiers

The field is correspond to the ASN.1 field “interOperatorIdentifiers”.
40 Holds a list of the Called party address(es), if the address(es) are determined by an
AS (SIP URL, E.164…)

2.2.71 Interrogation Result

The field is correspond to the ASN.1 field “interrogationResult”.
This field contains the result of the HLR interrogation attempt defined in the MAP
5 (TS 29.002).
Note: This field is present only when the attempted interrogation fails.
2.2.72 Is CAMEL Call

The field is correspond to the ASN.1 field “isCAMELCall”.
10 The field indicates that the CAMEL service is applied in the call.
2.2.73 Is CUG Used

The field is correspond to the ASN.1 field “isCUGUsed”.
The field indicates that the CUG service is applied in the call.
152.2.74 Is MultiMedia Call

The field is correspond to the ASN.1 field “isMultiMediaCall”.
This field indicates that the call is a CS multimedia call in the case of multimedia
service based on data bearer in the CS
202.2.75 Is HSCSD Used

The field is correspond to the ASN.1 field “isHSCSDUsed”.
The field indicates that the HSCSD service is applied in the call.
2.2.76 Last Long Part Indicator

25 The field is correspond to the ASN.1 field “lastLongPartInd”.
It indicates that the CDR is the last part CDR.
2.2.77 LCS Cause

The field is correspond to the ASN.1 field “lcsCause”.
30
This parameter provides causes for an unsuccessful location request based on TS
49.031.
2.2.78 LCS Client Identity

The field is correspond to the ASN.1 field “lcsClientIdentity”.
35
This field contains further information of LCS Client identity:
 Client external ID

 Client ID dialed by MS
 Client internal ID
2.2.79 LCS Client Type

The field is correspond to the ASN.1 field “lcsClientType”.
5
This field contains the type of the LCS Client defined in TS 29.002.
2.2.80 LCS Priority

The field is correspond to the ASN.1 field “lcsPriority”.
10 This field gives the priority of location requests defined in TS 49.031.
2.2.81 LCS QoS

The field is correspond to the ASN.1 field “lcsQos”.
This field gives the QoS of location requests defined in TS 49.031.
152.2.82 Level of CAMEL Service

The field is correspond to the ASN.1 field “levelOfCAMELService”.
This field briefly describes the complexity of CAMEL invocation.

 “Basic” indicates that CAMEL function is invoked during call setup
20 only, for example, change of destination.
 “Online charging” indicates that CAMEL supported AoC parameter
are sent to the MS (the Send Charging Information message is
received from the gsmSCF).
The “call duration management” flag is set if the call duration management is
25 applied in the gsmSSF of the VPLMN (when the application charging message is
received from the gsmSCF).
2.2.83 List of Message Bodies(MGCF)

The field is correspond to the ASN.1 field “list-Of-Message-Bodies”.
30 This grouped field comprising several sub-fields describing the data that may be
conveyed end-to-end in the body of a SIP message. Since several message bodies
may be exchanged via SIP-signalling, this grouped field may occur several times.
The List of Message Bodies contains the following elements:
 Content Type;
35  Content Disposition;
 Content Length;
 Originator.

They are described in the appropriate subclause. Message bodies with the "Content-
Type" field set to application/sdp and the "Content-Disposition" field set to session
are not included in the "Message Bodies" field.
2.2.84 Location/Change of Location

5 The field is correspond to the ASN.1 field “location/changeOfLocation”.
The location field contains the combination of the LAC and CI of the location in
which the served party is currently located. Any change of location shall be recorded
in the change of location field, including the time at which the change takes place.
10 The change of location field is optional, and it is not required if partial records are
generated when the location changes.
The LAC and CI are 2-byte numbers and coded according to 3GPP TS24.008.
2.2.85 Location Estimate

The field is correspond to the ASN.1 field “locationEstimate”.
15
The Location Estimate field provides estimate for the geographic location of a target
MS according to TS29.002.
2.2.86 Location Type

The field is correspond to the ASN.1 field “lcsClientType”.
20
This field contains the types of location defined in TS 29.002.
2.2.87 Maximum Bit Rate

The field is correspond to the ASN.1 field “maximumBitRate”.
25 This field contains the maximum bit rate based on the FNUR in transparent data
services and WAIUR in non-transparent data services based on the description in
3GPPTS27.001. This parameter can be used to reserve codes on the downlink
interface of UMTS bearer services (BS20 and BS30). Refer to 3GPP TS22.002. It
has the following functions:
30 1) Restrict the bit rate provided for applications or external networks
according to the value of this parameter.
2) Allow applications (for example, applications with adaptive codec)
working at different rates to provide different maximum wanted user bit
rates.
35 The value of maximum bit rate is smaller than or equal to the WAIUR (if the
WAIUR is less or equal to 14.4 kbit/s, the guaranteed bit rate and maximum bit rate
shall be set to 14.4 kbit/s).
2.2.88 Measure Duration

The field is correspond to the ASN.1 field “measureDuration”.
40
This field contains the location measurement duration of the response to location
requests and the location report messages.

2.2.89 Media Initiator Flag(MGCF)

The field is correspond to the ASN.1 field “mediaInitiatorFlag”.
This field indicates if the called party has requested the session modification and it is
5 present only if the initiator was the called party.
2.2.90 Message Reference

The field is correspond to the ASN.1 field “messageReference”.
This field contains a unique message reference number allocated by the MS when
10 sending a short message to the SMSC. This field corresponds to the TP-Message-
Reference element of the SMS_SUBMIT PDU defined in 3GPP TS 23.040.
2.2.91 MLC Number

The field is correspond to the ASN.1 field “mlc-Number”.
15 This parameter indicates the ISDN (E.164) number of an MLC.
2.2.92 Mobile station Classmark/Change of Classmark

The field is correspond to the ASN.1 field “msClassmark/changeOfClassmark”.
This field contains the mobile station classmark employed by the served MS on call
20 setup as defined in 3GPP TS24.008. Any change in the classmark during connection
shall be recorded together with the time when the change takes place in the change
of classmark field.
The change of classmark field is optional and is not required if partial records are
generated when the classmark is changed.
252.2.93 MOLR Type

The field is correspond to the ASN.1 field “molr-Type”.
The field uses the type of invoked mobile originated location requests defined in TS
24.080.
302.2.94 MSC Address

The field is correspond to the ASN.1 field “mSCAddress”.
This field contains the ITU-T E.164 number assigned to the MSC that generate
records. For details concerning numbers of the MSC, see TS23.003.
352.2.95 Msc SPC14

The field is correspond to the ASN.1 field “mscSPC14”.
This field is the spc14 code of the serving MSC
2.2.96 Msc SPC24

The field is correspond to the ASN.1 field “mscSPC24”.

This field is the spc24 code of the serving MSC
2.2.97 MSC Server Indication

The field is correspond to the ASN.1 field “mscServerIndication”.
5
This field contains an indicator whether the CAMEL subscriber 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 can be used to check whether CDRs in T-CSI of
the GMSC and VT-CSI of the VMSC are correct.
102.2.98 Network Call Reference

The field is correspond to the ASN.1 field “networkCallReference”.
This field is used to correlate the call records generated on the originating MSC (if
applicable), GMSC, and terminating MSC, and network optional call records on the
15 gsmSCF if the CAMEL service is applied.
2.2.99 Node Address(MGCF)

The field is correspond to the ASN.1 field “nodeAddress”.
This item holds the address of the node providing the information for the CDR. This
20 may either be the IP address or the FQDN of the IMS node generating the
accounting data. This parameter corresponds to the Origin-Host AVP.
2.2.100 No Reply CondTime

The field is correspond to the ASN.1 field “noReplyCondTime”.
25 When a mobile subscriber requests for the forwarding service, the field indicates the
time for call forwarding no reply. The value of this parameter is in the range of 0 to
30s.
2.2.101 Notification to MS user

The field is correspond to the ASN.1 field “notificationToMSUser”.
30
This field contains the private notification to mobile subscribers when a location
request is originated, as defined in TS 29.002.
2.2.102 Number of DP Encountered

The field is correspond to the ASN.1 field “numberOfDPEncountered”.
35
This field records service triggering points and event detection points detected in the
CAMEL service.
2.2.103 Number of Forwarding

The field is correspond to the ASN.1 field “numberOfForwarding”.
40

This field contains the number of forwarding times of a call before HLR
interrogation if ISUP signaling message can be provided, as defined in 3GPP
TS29.002.
2.2.104 Old/New Location

5 The field is correspond to the ASN.1 field “location/changeOfLocation”.
These fields contain the locations of a mobile subscriber before and after a location
update. In the case of VLR location update, the location information consists of a
VMSC number and a location area code. In the case of HLR location update, the
10 fields contain the VMSC number and VLR number.
2.2.105 OPC
The field is correspond to the ASN.1 field “oPC”.
This field contains the SPC code of the originating node that will be billed or
15 validated.
2.2.106 Originator(MGCF)
The field is correspond to the ASN.1 field “Originator”.
This sub-field of the "List of Message Bodies" indicates the originating party of the
20 message body.
2.2.107 Original Called Number

The field is correspond to the ASN.1 field “originalCalledNumber”
The original called number.It is the B number in the terminating record of C
252.2.108 Origination Number

The field is correspond to the ASN.1 field “originationNumber”.
This field records the number of the party sending short messages.
2.2.109 Partial Record Type

30 The field is correspond to the ASN.1 field “partialRecordType”.
This field indicates the event that caused the generation of a partial record.
2.2.110 Personal Back Ring Tone Indicator (PBRT)

The field is correspond to the ASN.1 field “pbrt”.
35
This field indicates whether the personal back ring tone service is applied in the call.
2.2.111 Positioning Data

The field is correspond to the ASN.1 field “positioningData”.

This information unit is used to provide positioning data associated with successful
or unsuccessful positioning attempts for a target MS according to TS 49.031.
2.2.112 Privacy Override

5 The field is correspond to the ASN.1 field “privacyOverride”.
This parameter indicates whether the MS privacy is overridden by the LCS client
when the GMLC and VMSC/SGSN for an mobile terminated request are in the same
country, as defined in TS 29.002.
102.2.113 Radio Channel Requested/Radio Channel Used/Change of Radio

Channel/Speech Version Supported/Speech Version Used
“radioChanRequested/radioChanUsed/changeOfRadioChan/speechVersionSupporte
d/ speechVersionUsed”.
15
The radio channel requested field contains the types of channel requested by
subscribers. It can be set to one of the following values:
 Full rate
 Half rate
20  Dual-mode half rate preferred
 Dual-mode full rate preferred
The radio channel used field indicates the types of traffic channel actually used for
connections, that is, the full rate (Bm) or half rate (Lm) as described in GSM 05.01.
Any change in the type of channel used shall be recorded in the change of radio
25 channel used field, including the time when the change happens and the speech
version used after the change of radio channel.
The speech version supported field contains the speech version supported by the MS
with the highest priority. The speech version used field contains the version of the
30 speech code allocated for a call. The code is based on the speech version indicator in
GSM08.08 and the eighth extension location is 0.
Note that the change of radio channel field is optional and is not required when
some records are generated.
2.2.114 Rate Indication

35 The field is correspond to the ASN.1 field “rateIndication”.
This parameter gives the rate adaptation used in connections. The field is
constructed based on the signaling parameters "rate adaptation" and "other rate
adaptation" between the MS/UE and the network. See TS 24.008.
40 The format of this field is a byte in the following formats:
 Bits 0-1: the rate adaptation field, as defined in TS 24.008
 Bits 2-3: the other rate adaptation field, as defined in TS 24.008
 Bits 4-7: not used

2.2.115 Reason for Service Change

The field is correspond to the ASN.1 field “reasonForServiceChange”.
This field contains the type of service change requested by the subscriber or
5 performed by the network. Possible values include:
- subscriber initiated;
- network initated;
- call setup fallback;
- call setup change order.
102.2.116 Record Closure Time

The field is correspond to the ASN.1 field “recordClosureTime”.
A Time stamp reflecting the time the MGCF closed the record.
2.2.117 Record Extensions

15 The field is correspond to the ASN.1 field “recordExtensions”.
This field allows network operators or suppliers to add their extension flags to
standards CDRs. This field contains a set of management extensions defined in ITU-
T X.721.
202.2.118 Record Opening Time

The field is correspond to the ASN.1 field “recordOpeningTime”.
A time stamp reflecting the time the MGCF opened this record. Present only in SIP
session related case
252.2.119 Record Sequence Number

The field is correspond to the ASN.1 field “recordSequenceNumber”.
The field contains one consecutive positive integer, serving as the unique ID of each
CDR.
302.2.120 Record Type

The field is correspond to the ASN.1 field “recordType”.
The field indicates the type of CDR, for example, mobile originated CDR, mobile
terminated CDR and forwarding CDR.
352.2.121 Recording Entity

The field is correspond to the ASN.1 field “recordingEntity”.

This field contains the ITU-T E.164 number assigned to the recording entity such as
MSC, VLR and HLR that generate records. For details concerning the MSC and
location registration numbers, see 3GPP TS23.003.
2.2.122 Redirect Number

5 The field is correspond to the ASN.1 field “redirectNumber”.
The field contains the mobile subscriber redirect numbers defined in 3GPP
TS23.003 and coded according to 3GPP TS29.002.
2.2.123 Redirecting Number

10 The field is correspond to the ASN.1 field “redirectingNumber”.
This field indicates the number of subscriber B upon call forwarding. This parameter
is present in call forwarding only.
2.2.124 Retransmission
15 The field is correspond to the ASN.1 field “retransmission”.
This parameter, when present, indicates that information from retransmitted

Charging Data Requests has been used in this CDR.
2.2.125 Roaming Number

20 The field is correspond to the ASN.1 field “roamingNumber”.
The roaming numbers in MOC CDRs contain mobile roaming numbers defined in
3GPP TS23.003 and coded according to 3GPP TS29.002.
2.2.126 Role of Node(MGCF)

25 The field is correspond to the ASN.1 field “role-of-Node”.
This fields indicates the role of the AS/CSCF. As specified in TS 23.218 [80] the
role can be:
 originating (CSCF serving the calling subscriber or AS initiated
30 session);
 terminating (CSCF serving the called subscriber or AS terminated
session);
 proxy (only applicable for an AS, when a request is proxied);
 B2BUA (only applicable for an AS, when the AS performs third party
35 control/acts in B2BUA mode.
2.2.127 Routing Number

The field is correspond to the ASN.1 field “routingNumber”.

The routing number field in HLR interrogation records contains a mobile station
roaming number or a forwarded-to number in the case of call forwarding.
2.2.128 SDP Media Components(MGCF)

The field is correspond to the ASN.1 field “sDP-Media-Components”.
5
This is a grouped field comprising several sub-fields associated with one media
component. Since several media components may exist for a session in parallel
these sub-fields may occur several times (as much times as media are involved in the
session). The sub-fields are present if medium (media) is (are) available in the SDP
10 data which is provided in the ACR received from the IMS node.
The SDP media component contains the following elements:
 SDP media name;
 SDP media description;
 GPRS Charging ID;
15 These field elements are described in the appropriate subclause.
2.2.129 SDP Media Description(MGCF)

The field is correspond to the ASN.1 field “SDP-Media-Description”.
This field holds the attributes of the media as available in the SDP data tagged with
20 "i=", "c=","b=","k=", "a=". Only the attribute lines relevant for charging are
recorded. To be recorded "SDP lines" shall be recorded in separate "SDP Media
Description" fields, thus multiple occurrence of this field is possible. Always
complete "SDP lines" are recorded per field.
This field corresponds to the SDP-Media-Description AVP as defined in Table 5.8.
25 Example: "c=IN IP4 134.134.157.81"
For further information on SDP please refer to IETF draft 'SDP.Session Description
Protocol'[xx].
Note: session unrelated procedures typically do not contain SDP data.
2.2.130 SDP Media Name(MGCF)

30 The field is correspond to the ASN.1 field “sDP-Media-Name”.
This field holds the name of the media as available in the SDP data tagged with
"m=". Always the complete "SDP line" is recorded.
This field corresponds to the SDP-Media-Name AVP as defined in Table 5.8.
35 Example: "m=video 51372 RTP/AVP 31"
For further information on SDP please refer to IETF draft 'SDP: Session Description
Protocol'[xx].
2.2.131 SDP Session Description(MGCF)

The field is correspond to the ASN.1 field “sDP-Session-Description”.
40
Holds the Session portion of the SDP data exchanged between the User Agents if
available in the SIP transaction.

This field holds the attributes of the media as available in the session related part of
the SDP data tagged with "c=" and "a=" (multiple occurrence possible). Only
attribute lines relevant for charging are recorded.
The content of this field corresponds to the SDP-Session-Description AVP of the
5 ACR message.
Note: session unrelated procedures typically do not contain SDP data.
2.2.132 Sequence Number

The field is correspond to the ASN.1 field “sequenceNumber”.
10 This field contains a dynamic sequence number used to connect the partial records
generated for a specified call. For the first partial record of the call, the sequence
number is 1.
2.2.133 Served IMEI

The field is correspond to the ASN.1 field “servedIMEI”.
15
This field contains the IMEI of the served user. The user refers to the record mobile
equipment related to calls, for example, called mobile equipment in MTC records.
The structure of the IMEI is defined in 3GPP TS2 3.003.
2.2.134 Served IMSI

20 The field is correspond to the ASN.1 field “servedIMSI”.
This field contains the IMSI of the served party. The served party refers to a
recorded mobile subscriber related to calls, for example, the called subscriber in
MTC records.
25 The structure of the IMSI is defined in 3GPP TS23.003.
2.2.135 Served MSISDN

The field is correspond to the ASN.1 field “servedMSISDN”.
This field contains the MSISDN of the server party. The served party refers to a
30 recorded mobile subscriber related to calls, for example, the called subscriber in
MTC records. In the case of multi-numbering, for example, one card with two
numbers, the MSISDN stored in an MOC record is the primary MSISDN of the
calling party.
The structure of the MSISDN is defined in 3GPP TS23.003.
352.2.136 Service Category

The field is correspond to the ASN.1 field “serviceCategory”
This field indicates the service category of the call.
2.2.137 Service Centre Address

40 The field is correspond to the ASN.1 field “serviceCentre”.

This field contains the service centre identified through an ITU-T E.164 number, for
example, short message service centre. See 3GPP TS23.040.
2.2.138 Service Change Initiator

The field is correspond to the ASN.1 field “serviceChangeInitiator”.
5
This field indicates that the owner of this CDR is the initiator of the service change.
2.2.139 Service Delivery End Time Stamp(MGCF)

The field is correspond to the ASN.1 field “serviceDeliveryEndTimeStamp”.
10 This field records the time at which the service delivery was terminated. It is Present
only in SIP session related case.
The content of this field corresponds to the SIP-Request-Timestamp AVP of a
received ACR[Stop] message indicating a session termination.
2.2.140 Service Delivery Start Time Stamp(MGCF)

15 The field is correspond to the ASN.1 field “serviceDeliveryStartTimeStamp”.
This field holds the time stamp reflecting either:

 a successful session set-up: this field holds the start time of a service
delivery (session related service)
20  a delivery of a session unrelated service: the service delivery time
stamp
 an unsuccessful session set-up and an unsuccessful session unrelated
request: this field holds the time the network entity forwards the
unsuccessful indication (SIP "RESPONSE" with error codes 3xx,
25 4xx, 5xx) towards the requesting User direction.
The content of this field corresponds to the SIP-Response-Timestamp AVP as
defined in Table 5.8.
For partial CDRs this field remains unchanged.
2.2.141 Service Identifier

30 The field is conrrespond to the ASN.1 field “serviceIdentifier”
The field contains the SI of the MTP3 signnaling messages.
2.2.142 Service Key

The field is correspond to the ASN.1 field “serviceKey”.
35
This field determines the applied CAMEL service. The service key is defined in the
HLR as a part of CAMEL subscription information.
2.2.143 Service Reason Return Code(MGCF)

The field is correspond to the ASN.1 field “serviceReasonReturnCode”.

Provides the returned cause code for the service request (both successful and
failure). This parameter corresponds to the Cause-Code AVP.
2.2.144 Service Request Timestamp(MGCF)

5 The field is correspond to the ASN.1 field “serviceRequestTimeStamp”.
This field contains the time stamp which indicates the time at which the service was
requested ("SIP request" message) and is present for session related and session
unrelated procedures. The content of this item is derived from the SIP-Request-
10 Timestamp AVP as defined in Table 5.8. If the SIP-Request-Timestamp AVP is not
supplied by the network entity this field is not present.
For partial CDRs this field remains unchanged.
This field is present for unsuccessful service requests if the ACR message includes
the SIP-Request-Timestamp AVP.
152.2.145 Session ID(MGCF)

The field is correspond to the ASN.1 field “session-Id”.
The Session identification. For a SIP session the Session-ID contains the SIP Call ID
as defined in the Session Initiation Protocol RFC[xx].
202.2.146 Short Message Service Result

The field is correspond to the ASN.1 field “smsResult”.
This field contains the result of an attempt to deliver a short message to a service
centre or a mobile subscriber (see TS 29.002).
25 Note: This field is not provided when the attempted delivery is unsuccessful.
2.2.147 SIP Method(MGCF)

The field is correspond to the ASN.1 field “sIP-Method”.
Specifies the SIP-method for which the CDR is generated. Only available in session
30 unrelated cases.
2.2.148 SIP Request Timestamp(MGCF)

The field is correspond to the ASN.1 field “sIP-Request-Timestamp”.
This parameter contains the time of the SIP Request (usually a (Re)Invite).
352.2.149 SIP Response Timestamp(MGCF)

The field is correspond to the ASN.1 field “sIP-Response-Timestamp”.
This parameter contains the time of the response to the SIP Request (usually a 200
OK).

2.2.150 SPC
The field is correspond to the ASN.1 field “sPC”
This field contains the SPC code of the STP node that generated the record.
52.2.151 Speech Version Supported/Speech Version Used

“speechVersionSupported/speechVersionUsed”.
The speech version supported field contains the speech version of the highest
10 priority supported by the MS. The speech version used field contains the version of
the speech code allocated for a call. The code is the speech version indicator in GSM
08.08 with the extension bit (eighth bit) set to “0”.
Note that the change of radio channel field is optional and not required if partial
records are generated.
152.2.152 System Type

The field is correspond to the ASN.1 field “systemType”.
Indicate that a call happens in the 3G-UMTS or GSM system.
2.2.153 SSN
20 The field is correspond to the ASN.1 field “sSN”.
This field contains the SSN of the SCCP messages
2.2.154 Subscriber Category

The field is correspond to the ASN.1 field “subscriberCategory”.
25
Subscriber category, also called subscriber identification, indicates properties of
mobile subscribes registered in the HLR. See ITU-T Q763 and NO.7 ISUP.
2.2.155 Supplementary Service(s)

The field is correspond to the ASN.1 field “supplService/supplServicesUsed”.
30
The supplementary service field in supplementary service records contains the codes
of supplementary services.
The supplementary services field in the MOC or MTC records contains the codes of
supplementary services invoked as a result of call connections.
35 The codes of supplementary services are described in 3GPP TS29.002 in detail.
2.2.156 Supplementary Service Action

The field is correspond to the ASN.1 field “ssAction”.
This field contains supplementary service actions requested by subscribers or

40 performed by the network. The value of this field can be following:

 Registration
 Erasure
 Activation
 Deactivation
5  Query
 Invocation
For more details, see 3GPP TS 22.004.
2.2.157 Supplementary Service Action Result

The field is correspond to the ASN.1 field “ssActionResult”.
10
This field contains the result of an attempted supplementary service action (see TS
29.002). Note that this field is present only when part of a supplementary service
action fails.
2.2.158 Supplementary Service Parameters

15 The field is correspond to the ASN.1 field “ssParameters”.
This field contains parameters related to a requested supplementary service action.

For more details of the related parameters, see GSM 02.8X series of documents.
2.2.159 Terminating Record Type

20 The field is correspond to the ASN.1 field “terminatingRecordType”
This field indicates the type of the terminating record.
2.2.160 Transaction Identification

The field is correspond to the ASN.1 field “transactionIdentification”
25
This field is provided when the user has more than one ongoing calls at the same
time.It is used to identify different ongoing calls.
2.2.161 Transparency Indicator

The field is correspond to the ASN.1 field “transparencyIndicator”.
30
This field indicates basic services are applied in the transparent mode or non-
transparent mode. Note that this field is only related to the services that can operate
in both the transparent mode and non-transparent mode.
2.2.162 Trunk Group ID Incoming/Outgoing(MGCF)

35 The field is correspond to the ASN.1 field
“mscIncomingTKGP/mscOutgoingTKGP”.
Contains the outgoing trunk group ID for an outgoing session/call or the incoming
trunk group ID for an incoming session/call.

2.2.163 Type of service change

The field is correspond to the ASN.1 field “typeOfServiceChange”
Indicates the type of service change. Provided if SCUDIF service is used. Possible
5 values include
- to speech
- to multimedia
2.2.164 Unstructured SS Data

The field is correspond to the ASN.1 field “uSSDUnstructuredData”.
10
The SS Data exchanged between the mobile and network.
2.2.165 USSD interaction count

The field is correspond to the ASN.1 field “uSSDInteractionCount”.
15 The USSD interaction count.
2.2.166 Ussd data coding scheme

The field is correspond to the ASN.1 field “uSSDDateCodingSchema”.
The coding scheme of USSD data.
202.2.167 USSD operation code

The field is correspond to the ASN.1 field “uSSDOpreationCode”.
The operation code of USSD.
2.2.168 USSD Service Code

25 The field is correspond to the ASN.1 field “uSSDServiceCode”.
The service code of USSD operation.
2.2.169 VIG Call Type

The field is correspond to the ASN.1 field “vigCallType”.
30
The direction of a call, which is defined as “incoming” or “outgoing”.

3 ASN.1 DEFINITIONS FOR CDRS

3.1 CDR Structure
3.1.1 CallEventRecord
CallEventRecord ::= CHOICE
5 {
moCallRecord [0] MOCallRecord OPTIONAL,
mtCallRecord [1] MTCallRecord OPTIONAL,
roamRecord [2] ROAMRecord OPTIONAL,
incGatewayRecord [3] IncGatewayRecord OPTIONAL,
10 outGatewayRecord [4] OutGatewayRecord OPTIONAL,
transitRecord [5] TransitRecord OPTIONAL,
moSMSRecord [6] MOSMSRecord OPTIONAL,
mtSMSRecord [7] MTSMSRecord OPTIONAL,
moSMSIWRecord [8] MOSMSIWRecord OPTIONAL,
15 mtSMSGWRecord [9] MTSMSGWRecord OPTIONAL,
ssActionRecord [10] SSActionRecord OPTIONAL,
hlrIntRecord [11] HLRIntRecord OPTIONAL,
moeCallRecord [12] MOECallRecord OPTIONAL,
mcfCallRecord [13] MCFCallRecord OPTIONAL,
20 commonEquipRecord [14] CommonEquipRecord OPTIONAL,
termCAMELIntRecord [16] TermCAMELIntRecord OPTIONAL,
mtLCSRecord [17] MTLCSRecord OPTIONAL,
moLCSRecord [18] MOLCSRecord OPTIONAL,
niLCSRecord [19] NILCSRecord OPTIONAL,
25
mGCFRecord [67] MGCFRecord OPTIONAL,
sigMTPStatisticRecord [100] SigMTPStatisticRecord OPTIONAL,
sigSCCPStatisticRecord [101] SigSCCPStatisticRecord OPTIONAL,
uSSDRecord [102] USSDRecord OPTIONAL,
30 vIGRecord [103] VIGRecord OPTIONAL,
}
3.1.2 MOCallRecord
MOCallRecord ::= SET
{
35 recordType [0] CallEventRecordType,
servedIMSI [1] IMSI ,
servedIMEI [2] IMEI OPTIONAL,
servedMSISDN [3] MSISDN,
calledNumber [4] CalledNumber OPTIONAL,
40 translatedNumber [5] TranslatedNumber OPTIONAL,
connectedNumber [6] ConnectedNumber OPTIONAL,
roamingNumber [7] RoamingNumber OPTIONAL,
recordingEntity [8] RecordingEntity,
mscIncomingTKGP [9] TrunkGroup OPTIONAL,
45 mscOutgoingTKGP [10] TrunkGroup OPTIONAL,
location [11] LocationAreaAndCell ,
changeOfLocation [12] SEQUENCE OF LocationChange OPTIONAL,
basicService [13] BasicServiceCode ,
transparencyIndicator [14] TransparencyInd OPTIONAL,
50 changeOfService [15] SEQUENCE OF ChangeOfService OPTIONAL,
supplServicesUsed [16] SEQUENCE OF SuppServiceUsed OPTIONAL,
aocParameters [17] AOCParameters OPTIONAL,
changeOfAOCParms [18] SEQUENCE OF AOCParmChange OPTIONAL,
msClassmark [19] Classmark,
55 changeOfClassmark [20] ChangeOfClassmark OPTIONAL,
seizureTime [21] TimeStamp OPTIONAL,
answerTime [22] TimeStamp OPTIONAL,
releaseTime [23] TimeStamp OPTIONAL,

callDuration [24] CallDuration,

dataVolume [25] DataVolume OPTIONAL,
radioChanRequested [26] RadioChanRequested OPTIONAL,
radioChanUsed [27] TrafficChannel OPTIONAL,
5 changeOfRadioChan [28] ChangeOfRadioChannel OPTIONAL,
causeForTerm [29] CauseForTerm,
diagnostics [30] Diagnostics OPTIONAL,
callReference [31] CallReference,
sequenceNumber [32] LongPartSeqNumber OPTIONAL,
10 lastLongPartInd [33] NULL OPTIONAL,
additionalChgInfo [34] AdditionalChgInfo OPTIONAL,
recordExtensions [35] ManagementExtensions OPTIONAL,
isCAMELCall [36] NULL OPTIONAL,
gsm-SCFAddress [37] Gsm-SCFAddress OPTIONAL,
15 serviceKey [38] ServiceKey OPTIONAL,
networkCallReference [39] NetworkCallReference OPTIONAL,
mSCAddress [40] MSCAddress OPTIONAL,
defaultCallHandling [41] DefaultCallHandling OPTIONAL,
isHSCSDUsed [42] NULL OPTIONAL,
20 hSCSDChanRequested [43] NumOfHSCSDChanRequested OPTIONAL,
hSCSDChanAllocated [44] NumOfHSCSDChanAllocated OPTIONAL,
changeOfHSCSDParms [45] SEQUENCE OF HSCSDParmsChange OPTIONAL,
fnur [46] Fnur OPTIONAL,
aiurRequested [47] AiurRequested OPTIONAL,
25 chanCodingsAcceptable [48] SEQUENCE OF ChannelCoding OPTIONAL,
chanCodingUsed [49] ChannelCoding OPTIONAL,
speechVersionSupported [50] SpeechVersionIdentifier OPTIONAL,
speechVersionUsed [51] SpeechVersionIdentifier OPTIONAL,
numberOfDPEncountered [52] NumberOfDPEncountered OPTIONAL,
30 levelOfCAMELService [53] LevelOfCAMELService OPTIONAL,
freeFormatData [54] FreeFormatData OPTIONAL,
cAMELCallLegInformation [55] SEQUENCE OF CAMELInformation OPTIONAL,
freeFormatDataAppend [56] BOOLEAN OPTIONAL,
defaultCallHandling_2 [57] DefaultCallHandling OPTIONAL,
35 gsm-SCFAddress_2 [58] Gsm-SCFAddress OPTIONAL,
serviceKey_2 [59] ServiceKey OPTIONAL,
freeFormatData_2 [60] FreeFormatData OPTIONAL,
freeFormatDataAppend_2 [61] BOOLEAN OPTIONAL,
systemType [62] SystemType OPTIONAL,
40 exchangeIdentity [63] IA5STRING OPTIONAL,
dialledNumber [64] BCDDirectoryNumber OPTIONAL,
subscriberCategory [65] SubscriberCategory OPTIONAL,
recordSequenceNumber [66] RecordSeqNumber OPTIONAL,
eMLPPriorityLevel [67] EMLPPriorityLevel OPTIONAL,
45 eMLPRequestPriorityLevel [68] EMLPRequestPriorityLevel OPTIONAL,
hotBillingTag [69] HotBillingTag OPTIONAL,
isCUGUsed [70] NULL OPTIONAL,
cUGCategory [71] CUGCategory OPTIONAL,
cUGInterLockCode [72] CUGInterLockCode OPTIONAL,
50 dataRate [73] DataRate OPTIONAL,
isMultiMediaCall [74] NULL OPTIONAL,
rateIndication [75]RateIndication OPTIONAL,
guaranteedBitRate [76] GuaranteedBitRate OPTIONAL,
maximumBitRate [77] MaximumBitRate OPTIONAL,
55 pbrt [78] Pbrt OPTIONAL,
carp [79] Carp OPTIONAL,
cUGIndex [80] CUGIndex OPTIONAL,
cUGOutgoingAccessUsed [81] NULL OPTIONAL,
cUGOutgoingAccessInd [82] NULL OPTIONAL,
60 hotBillingTag2 [83] HotBillingTag2 OPTIONAL,
dDCFlag [88] BOOLEAN OPTIONAL,
bSCIdentification [89] BSCIdentification OPTIONAL,
calledLocation [90] LocationAreaAndCell OPTIONAL,
callingPartyRoamingInd [91] BOOLEAN OPTIONAL,
65 serviceCategory [92] ServiceCategory OPTIONAL,
transactionIdentification [93] INTEGER OPTIONAL,
incomingCic [94] CICCode OPTIONAL,

outgoingCic [95] CICCode OPTIONAL,

mscSPC14 [96] SPC14 OPTIONAL,
incomingTKGPName [98] TKGPName OPTIONAL,
5 outgoingTKGPName [99] TKGPName OPTIONAL,
partialRecordType [100] PartialRecordType OPTIONAL,
serviceChangeInitiator [101] INTEGER OPTIONAL,
reasonForServiceChange [102] ReasonForServiceChange OPTIONAL,
typeOfServiceChange [103] TypeOfServiceChange OPTIONAL
10 }
3.1.3 MTCallRecord
MTCallRecord ::= SET
{
recordType [0] CallEventRecordType,
15 servedIMSI [1] IMSI ,
servedMSISDN [3] CalledNumber OPTIONAL,
callingNumber [4] CallingNumber OPTIONAL,
20 mscIncomingTKGP [6] TrunkGroup OPTIONAL,
mscOutgoingTKGP [7] TrunkGroup OPTIONAL,
location [8] LocationAreaAndCell OPTIONAL,
changeOfLocation [9] SEQUENCE OF LocationChange
OPTIONAL,
25 basicService [10] BasicServiceCode ,
changeOfService [12] SEQUENCE OF ChangeOfService OPTIONAL,
30 changeOfAOCParms [15] SEQUENCE OF AOCParmChange OPTIONAL,
msClassmark [16] Classmark OPTIONAL,
changeOfClassmark [17] ChangeOfClassmark OPTIONAL,
35 releaseTime [20] TimeStamp OPTIONAL,
40 changeOfRadioChan [25] ChangeOfRadioChannel OPTIONAL,
50 mSCAddress [35] MSCAddress OPTIONAL,
isHSCSDUsed [36] NULL OPTIONAL,
hSCSDChanRequested [37] NumOfHSCSDChanRequested OPTIONAL,
hSCSDChanAllocated [38] NumOfHSCSDChanAllocated OPTIONAL,
changeOfHSCSDParms [39] SEQUENCE OF HSCSDParmsChange OPTIONAL,
55 fnur [40] Fnur OPTIONAL,
chanCodingsAcceptable [42] SEQUENCE OF ChannelCoding OPTIONAL,
chanCodingUsed [43] ChannelCoding OPTIONAL,
speechVersionSupported [44] SpeechVersionIdentifier OPTIONAL,
60 speechVersionUsed [45] SpeechVersionIdentifier OPTIONAL,
gsm-SCFAddress [46] Gsm-SCFAddress OPTIONAL
serviceKey [47] ServiceKey OPTIONAL,


exchangeIdentity [52] IA5STRING OPTIONAL,
5 redirectNumber [53] BCDDirectoryNumber OPTIONAL,
connectedNumber [56] BCDDirectoryNumber OPTIONAL,
10 isCUGUsed [58] NULL OPTIONAL,
dataRate [61] DataRate OPTIONAL,
15 rateIndication [63]RateIndication OPTIONAL
guaranteedBitRate [64] GuaranteedBitRate OPTIONAL,
maximumBitRate [65] MaximumBitRate OPTIONAL,
pbrt [66] Pbrt OPTIONAL,
20 cUGIndex [68] CUGIndex OPTIONAL,
cUGIncomingAccessUsed [69] NULL OPTIONAL,
cUGIncomingAccessInd [70] NULL OPTIONAL,
redirectingNumber [71] BCDDirectoryNumber OPTIONAL,
hotBillingTag2 [72] HotBillingTag2 OPTIONAL,
25 dDCFlag [77] BOOLEAN OPTIONAL,
terminatingRecordType [78] TerminatingRecordType OPTIONA,
originalCalledNumber [79] AddressString OPTIONAL,
callingLocation [80] LocationAreaAndCell OPTIONAL,
30 calledPartyRoamingInd [82] BOOLEAN OPTIONAL,
serviceCategory [83] ServiceCategory OPTIONAL,
35 mscSPC14 [87] SPC14 OPTIONAL,
outgoingTKGPName [90] TKGPName OPTIONAL,
40 serviceChangeInitiator [92] INTEGER OPTIONAL,
}
3.1.4 ROAMRecord
45 ROAMRecord ::= SET
{
servedIMSI [1] IMSI,
servedMSISDN [2] MSISDN OPTIONAL,
50 callingNumber [3] CallingNumber OPTIONAL,
55 basicService [8] BasicServiceCode,
60 answerTime [13] TimeStamp OPTIONAL,


10 exchangeIdentity [26] IA5STRING OPTIONAL,
redirectNumber [34] BCDDirectoryNumber OPTIONAL,
25 incomingTKGPName [41] TKGPName OPTIONAL,
transRoamingNumber [43] ISDN-AddressString OPTIONAL
}
3.1.5 IncGatewayRecord
30 IncGatewayRecord ::= SET
{
calledNumber [2] CalledNumber,
35 recordingEntity [3] RecordingEntity,
45 callReference [13] CallReference,
lastLongPartInd [15] NULL OPTIONAL,
50 additionalChgInfo [18] AdditionalChgInfo OPTIONAL,
gatewayRecordType [26] GatewayRecordType OPTIONAL,
55 roamingNumber [27] BCDDirectoryNumber OPTIONAL,
forwardCallIndicator [35] ForwardCallIndicator OPTIONAL,


5 isdnBasicService [40] BasicServiceCode OPTIONAL,
}
3.1.6 OutGatewayRecord
OutGatewayRecord ::= SET
{
15 mscOutgoingTKGP [5] TrunkGroup OPTIONAL,
20 dataVolume [10] DataVolume OPTIONAL,
gatewayRecordType [26] GatewayRecordType OPTIONAL,
roamingNumber [27] BCDDirectoryNumber OPTIONAL,
35 incomingCic [29] CICCode OPTIONAL,
40 outgoingTKGPName [34] TKGPName OPTIONAL,
45 isdnBasicService [40] BasicServiceCode OPTIONAL,
}
3.1.7 TransitRecord
TransitRecord ::= SET
{
isdnBasicService [3] BasicServiceCode OPTIONAL,
60 callDuration [10] CallDuration,


roamingNumber [27] BCDDirectoryNumber OPTIONAL,
15 outgoingCic [30] CICCode OPTIONAL,
20 }
3.1.8 MOSMSRecord
MOSMSRecord ::= SET
{
25 servedIMSI [1] IMSI,
servedIMEI [2] IMEI OPTIONAL
serviceCentre [5] AddressString,
messageReference [8] MessageReference OPTIONAL,
originationTime [9] TimeStamp,
smsResult [10] SMSResult OPTIONAL,
35 recordExtensions [11] ManagementExtensions OPTIONAL,
destinationNumber [12] CalledNumber OPTIONAL,
cAMELSMSInformation [13] CAMELSMSInformation OPTIONAL,
40 recordSequenceNumber [16] RecordSeqNumber OPTIONAL,
}
3.1.9 MTSMSRecord
MTSMSRecord ::= SET
{
55 msClassmark [5] Classmark,
deliveryTime [8] TimeStamp,


originationNumber [14] BCDDirectoryNumber,
5 hotBillingTag [15] HotBillingTag OPTIONAL,
10 cAMELSMSInformation [20] CAMELSMSInformation OPTIONAL,
}
3.1.10 MOSMSIWRecord
MOSMSIWRecord ::= SET
{
20 eventTime [5] TimeStamp,
25 recordSequenceNumber [10] RecordSeqNumber OPTIONAL
}
3.1.11 MTSMSGWRecord
MTSMSGWRecord ::= SET
{
35 eventTime [5] TimeStamp,
40 recordSequenceNumber [10] RecordSeqNumber OPTIONAL
}
3.1.12 SSActionRecord
SSActionRecord ::= SET
{
basicService [7] BasicServices OPTIONAL,
supplService [8] SS-Code OPTIONAL,
ssAction [9] SSActionType OPTIONAL,
55 ssActionTime [10] TimeStamp,
ssParameters [11] SSParameters OPTIONAL,
ssActionResult [12] SSActionResult OPTIONAL,


forwardedSubNumber [18] ForwardedSubNumber OPTIONAL,
noReplyCondTime [19] NoReplyCondTime OPTIONAL,
}
3.1.13 MOECallRecord
MOECallRecord ::= SET
15 {
servedIMSI [1] IMSI OPTIONAL,
20 translatedNumber [4] BCDDirectoryNumber OPTIONAL,
25 changeOfLocation [9] SEQUENCE OF LocationChange
OPTIONAL,
basicService [10] BasicServiceCode OPTIONAL,
changeOfAOCParms [12] SEQUENCE OF AOCParmChange OPTIONAL
30 msClassmark [13] Classmark OPTIONAL,
changeOfClassmark [14] ChangeOfClassmark OPTIONAL,
changeOfRadioChan [21] ChangeOfRadioChannel OPTIONAL,
40 diagnostics [23] Diagnostics OPTIONAL,
45 systemType [28] SystemType OPTIONAL,
calledNumber [31] CalledNumber OPTIONAL,
50 roamingNumber [33] MSISDN OPTIONAL,
eMLPPriorityLevel [34] EMLPPriorityLevel OPTIONAL,
eMLPRequestPriorityLevel [35]EMLPRequestPriorityLevel OPTIONAL,
hotBillingTag [36]HotBillingTag OPTIONAL,

3.1.14 MCFCallRecord
MCFCallRecord ::= SET
{
mcfType [1] McfType,
servedIMEI [3] IMEI ,
10 callingNumber [5] BCDDirectoryNumber OPTIONAL,
calledNumber [6] BCDDirectoryNumber OPTIONAL,
translatedNumber [7] BCDDirectoryNumber OPTIONAL,
connectedNumber [8] BCDDirectoryNumber OPTIONAL,
roamingNumber [9] ISDN-AddressString OPTIONAL,
20 changeOfService [15] SEQUENCE OF ChangeOfService OPTIONAL,
35 gsm-SCFAddress [30] Gsm-SCFAddress OPTIONAL,
cAMELInitCFIndicator [34] CAMELInitCFIndicator OPTIONAL,
40 defaultCallHandling [35] DefaultCallHandling OPTIONAL,
levelOfCAMELService [37] LevelOfCAMELService OPTIONAL,
cAMELCallLegInformation [39] SEQUENCE OF CAMELInformation OPTIONAL,
45 freeFormatDataAppend [40] BOOLEAN OPTIONAL,
defaultCallHandling_2 [41] DefaultCallHandling OPTIONAL,
gsm-SCFAddress_2 [42] Gsm-SCFAddress OPTIONAL,
serviceKey_2 [43] ServiceKey OPTIONAL,
50 freeFormatDataAppend_2 [45] BOOLEAN OPTIONAL,
55 numberOfForwarding [50] NumberOfForwarding OPTIONAL,
rateIndication [57]RateIndication OPTIONAL,
fnur [58] Fnur OPTIONAL,


cUGIndex [61] CUGIndex OPTIONAL,
cUGOutgoingAccessUsed [62] NULL OPTIONAL,
5 cUGOutgoingAccessInd [63] NULL OPTIONAL,
calledLocation [66] LocationAreaAndCell OPTIONAL,
callingPartyRoamingInd [67] BOOLEAN OPTIONAL,
20 typeOfServiceChange [78] TypeOfServiceChange OPTIONAL
}
3.1.15 CommonEquipRecord
CommonEquipRecord ::= SET
{
equipmentType [1] EquipmentType,
equipmentId [2] EquipmentId OPTIONAL,
systemType [18]SystemType,
rateIndication [19] RateIndication OPTIONAL,
45 fnur [20] Fnur OPTIONAL,
hotBillingTag2 [21] HotBillingTag2 OPTIONAL
}
3.1.16 TermCAMELIntRecord
TermCAMELIntRecord ::= SET
50 {
55 interrogationTime [4] TimeStamp,
destinationRoutingAddress [5] DestinationRoutingAddress,
gsm-SCFAddress [6] Gsm-SCFAddress,
serviceKey [7] ServiceKey,
60 mSCAddress [9] MSCAddress OPTIONAL,


15 sequenceNumber [24] LongPartSeqNumber OPTIONAL,
levelOfCAMELService [27] LevelOfCAMELService OPTIONAL,
20 cAMELCallLegInformation [29] SEQUENCE OF CAMELInformation OPTIONAL,
mscServerIndication [33] BOOLEAN OPTIONAL,
25 gsm-SCFAddress-2 [34] Gsm-SCFAddress OPTIONAL,
serviceKey-2 [35] ServiceKey OPTIONAL,
defaultCallHandling-2 [36] DefaultCallHandling OPTIONAL,
freeFormatData-2 [37] FreeFormatData OPTIONAL,
freeFormatDataAppend-2 [38] BOOLEAN OPTIONAL,
MscSPC14 [46] SPC14 OPTIONAL,
MscSPC24 [47] SPC24 OPTIONAL,
outgoingTKGPName [49] TKGPName OPTIONAL
}
3.1.17 HLRIntRecord
HLRIntRecord ::= SET
40 {
45 basicService [4] BasicServiceCode OPTIONAL,
routingNumber [5] RoutingNumber,
interrogationTime [6] TimeStamp,
numberOfForwarding [7] NumberOfForwarding OPTIONAL,
interrogationResult [8] HLRIntResult OPTIONAL,
}
553.1.18 MTLCSRecord
MTLCSRecord::= SET
{

lcsClientType [2] LCSClientType,

lcsClientIdentity [3] LCSClientIdentity,
5 locationType [6] LocationType,
lcsQos [7] LCSQoSInfo OPTIONAL,
lcsPriority [8] LCS-Priority OPTIONAL,
mlc-Number [9] ISDN-AddressString,
eventTimeStamp [10] TimeStamp,
10 measureDuration [11] CallDuration OPTIONAL,
notificationToMSUser [12] NotificationToMSUser OPTIONAL,
privacyOverride [13] NULL OPTIONAL,
locationEstimate [15] Ext-GeographicalInformation OPTIONAL,
15 positioningData [16] PositioningData OPTIONAL,
lcsCause [17] LCSCause OPTIONAL,
causeForTerm [23] CauseForTerm OPTIONAL,
additionalChgInfo [24] AdditionalChgInfo,
25 }
3.1.19 MOLCSRecord
MOLCSRecord ::= SET
{
lcsClientType [2] LCSClientType OPTIONAL,
lcsClientIdentity [3] LCSClientIdentity OPTIONAL,
35 molr-Type [6] MOLR-Type,
mlc-Number [9] ISDN-AddressString OPTIONAL,
eventTimeStamp [10] TimeStamp,
40 measureDuration [11] CallDuration OPTIONAL,
positioningData [14] PositioningData OPTIONAL,
lcsCause [15] LCSCause OPTIONAL,
45 diagnostics [16] Diagnostics OPTIONAL,
50 causeForTerm [21] CauseForTerm OPTIONAL,
}
3.1.20 NILCSRecord
55 NILCSRecord::= SET
{
lcsClientType [2] LCSClientType OPTIONAL,

lcsClientIdentity [3] LCSClientIdentity OPTIONAL,

5 emsDigits [7] ISDN-AddressString OPTIONAL,
emsKey [8] ISDN-AddressString OPTIONAL,
mlc-Number [11] ISDN-AddressString OPTIONAL,
10 eventTimeStamp [12] TimeStamp,
measureDuration [13] CallDuration OPTIONAL,
positioningData [16] PositioningData OPTIONAL,
15 lcsCause [17] LCSCause OPTIONAL,
}
253.1.21 USSDRecord
USSDRecord ::= SET
{
30 servedIMEI [2] IMEI OPTIONAL,
startTime [6] TimeStamp OPTIONAL,
35 endTime [7] TimeStamp OPTIONAL,
location [8] LocationAreaAndCell ,
uSSDInteractionCount [10] INTEGER OPTIONAL,
uSSDUnstructuredData [11] OCTET STRING(SIZE(0..185)),
40 uSSDOpreationCode [12] USSDOperationCode OPTIONAL,
uSSDDataCodingSchema [13] USSDDataCodingSchema OPTIONAL,
uSSDServiceCode [14] USSDServiceCode OPTIONAL,
errorCode [15] Diagnostics OPTIONAL,
}
503.1.22 VIGRecord
VIGRecord ::= SET
{
callingNumber [1] CallingNumber,
55 calledNumber [2] CalledNumber ,
vigCallType [3] VIGCallType,
startTime [4] TimeStamp OPTIONAL,
endTime [5] TimeStamp OPTIONAL,


callDataRate [12] INTEGER,
}
103.1.23 MGCFRecord
MGCFRecord ::= SET
{
retransmission [1] NULL OPTIONAL,
15 sIP-Method [2] SIP-Method OPTIONAL,
role-of-Node [3] Role-of-Node OPTIONAL,
nodeAddress [4] NodeAddress OPTIONAL,
session-Id [5] Session-Id OPTIONAL,
calling-Party-Address [6] InvolvedParty OPTIONAL,
20 called-Party-Address [7] InvolvedParty OPTIONAL,
privateUserID [8] GraphicString OPTIONAL,
serviceRequestTimeStamp [9] TimeStamp OPTIONAL,
serviceDeliveryStartTimeStamp [10] TimeStamp OPTIONAL,
serviceDeliveryEndTimeStamp [11] TimeStamp OPTIONAL,
25 recordOpeningTime [12] TimeStamp OPTIONAL,
recordClosureTime [13] TimeStamp OPTIONAL,
interOperatorIdentifiers [14] InterOperatorIdentifierlist OPTIONAL,
localRecordSequenceNumber [15] LocalSequenceNumber OPTIONAL,
recordSequenceNumber [16] INTEGER OPTIONAL,
30 causeForRecordClosing [17] CauseForTerm OPTIONAL,
incomplete-CDR-Indication [18] Incomplete-CDR-Indication OPTIONAL
iMS-Charging-Identifier [19] IMS-Charging-Identifier OPTIONAL,
list-Of-SDP-Media-Components [21] SEQUENCE OF Media-Components-List
OPTIONAL,
35 gGSNaddress [22] NodeAddress OPTIONAL,
serviceReasonReturnCode [23] UTF8String OPTIONAL,
list-Of-Message-Bodies [24] SEQUENCE OF MessageBody OPTIONAL,
trunkGroupID [80] TrunkGroupID OPTIONAL,
40 bearerService [81] TransmissionMedium OPTIONAL,
}
3.1.24 SigMTPStatisticRecord
SigMTPStatisticRecord::= SET
{
billType [2] BillOrValidateFlag OPTIONAL,
serviceIdentifier [3] MTPServiceIdentifier OPTIONAL,
sPC [4] SPCCode OPTIONAL,
50 oPC [5] SPCCode OPTIONAL,
dPC [6] SPCCode OPTIONAL,
chargedNeighbor [7] SPCCode OPTIONAL,
amountOfMessage [8] INTEGER OPTIONAL,
amountOfOctets [9] INTEGER OPTIONAL,
55 recordOpeningTime [10] TimeStamp OPTIONAL,
recordClosingTime [11] TimeStamp OPTIONAL,
physicalLocation [12] INTEGER OPTIONAL,
}

3.1.25 SigSCCPStatisticRecord
SigSCCPStatisticRecord::= SET
{
billType [2] BillOrValidateFlag OPTIONAL,
sPC [3] SPCCode OPTIONAL,
oPC [4] SPCCode OPTIONAL,
dPC [5] SPCCode OPTIONAL,
10 sSN [6] SSNCode OPTIONAL,
amountOfGTMessages [7] INTEGER OPTIONAL,
recordOpeningTime [8] TimeStamp OPTIONAL,
recordClosingTime [9] TimeStamp OPTIONAL,
physicalLocation [10] INTEGER OPTIONAL,
15 }
3.2 CDR Fields Structure

3.2.1 ACRInterimLost(MGCF)
ACRInterimLost ::= ENUMERATED
20 {
no (0),
yes (1),
unknown (2)
}
253.2.2 AdditionalChgInfo
AdditionalChgInfo ::= SEQUENCE
{
chargeIndicator [0] ChargeIndicator OPTIONAL,
chargedParty [1] ChargedParty OPTIONAL
30 }
3.2.3 AddressString
AddressString ::= OCTET STRING (SIZE (1..maxAddressLength))
maxAddressLength INTEGER ::= 20
8 7 6 5 4 3 2 1
Octet 1 1 Nature Of Address Numbering plan
ext Indicator
Octet 2 Number digit 2 Number digit 1
Octet 4
..
..
Nature of address indicator:
Bits
7 6 5
0 0 0 unknown
0 0 1 international number
0 1 0 national significant number
0 1 1 network specific number

1 0 0 subscriber number
1 0 1 reserved
1 1 0 abbreviated number
1 1 1 reserved for extension
The MSISDN TON of SMS may be 5, the number digit will be packed by 7-bit
characters. See 4.1 for packing of 7-bit characters
Numbering plan indicator
Bits
4 3 2 1
0 0 0 0 Unknown
0 0 0 1 ISDN/telephony numbering plan (Rec. E.164)
0 0 1 0 Spare
0 0 1 1 data numbering plan (Recommendation X.121)
0 1 0 0 telex numbering plan (Recommendation F.69)
0 1 0 1 Spare
0 1 1 0 land mobile numbering plan (CCITT Rec E.212)
0 1 1 1 Spare
1 0 0 0 national numbering plan
1 1 1 1 reserved for extension
3.2.4 AiurRequested
5 AiurRequested ::= ENUMERATED
{
aiur09600BitsPerSecond (1),
10 aiur28800BitsPerSecond (5),
aiur38400BitsPerSecond1 (9),
15 aiur38400BitsPerSecond2 (10),
aiur38400BitsPerSecond3 (11),
aiur38400BitsPerSecond4 (12)
}
3.2.5 AOCParameters
20 AOCParameters::= SEQUENCE
{
e1 [1] EParameter OPTIONAL,
e2 [2] Eparameter OPTIONAL,
25 e4 [4] Eparameter OPTIONAL,
e7 [7] Eparameter OPTIONAL
}
303.2.6 AOCParmChange
AOCParmChange ::= SEQUENCE
{
changeTime [0] TimeStamp,
newParameters [1] AOCParameters
35 }

3.2.7 BasicServiceCode
BasicServiceCode ::= CHOICE
{
bearerService [3] BearerServiceCode,
5 teleservice [2] TeleserviceCode
}
3.2.8 BasicServices
BasicServices ::= SET OF BasicServiceCode
3.2.9 BearerServiceCode
10 BearerServiceCode ::= OCTET STRING (SIZE (1))
Value
Meaning
Binary Hexadecimal
‘00000000’B 0 All Bearer Services
‘00010000’B 10 AllData CDA(Circuit Data Asychronous)-Services
‘00010001’B 11 Data CDA-300bps
‘00010010’B 12 Data CDA-1200bps
‘00010011’B 13 Data CDA-1200-75bps
‘00010100’B 14 Data CDA-2400bps
‘00010101’B 15 Data CDA-4800bps
‘00010110’B 16 Data CDA-9600bps
‘00010111’B 17 general-data CDA
‘00011000’B 18 All Data CDS(Circuit Data Synchronous) –Services
‘00011010’B 1A Data CDS-1200bps
‘00011100’B 1C Data CDS-2400bps
‘00011101’B 1D Data CDS-4800bps
‘00011110’B 1E Data CDS-9600bps
‘00011111’B 1F general-data CDS
‘00100000’B 20 All Pad(Packed Assembly/Disassambly) Services
‘00100001’B 21 Pad AccessCA-300bps
‘00100011’B 23 Pad AccessCA-1200-75bps
‘00100111’B 27 general-pad AccessCA
‘00101000’B 28 All DataPDS-Services
‘00101100’B 2C Data PDS-2400bps
‘00101101’B 2D Data PDS-4800bps
‘00101110’B 2E Data PDS-9600bps
‘00101111’B 2F general-data PDS
‘00110000’B 30 All Alternate Speech-Data CDA
‘00111000’B 38 All Alternate Speech-Data CDS
‘01000000’B 40 All Speech Followed By Data CDA
‘01001000’B 48 All peech Followed By Data CDS
‘01010000’B 50 All Data Circuit Asynchronous
‘01100000’B 60 All Asynchronous Services
‘01011000’B 58 All Data Circuit Synchronous

‘01101000’B 68 All SynchronousServices

‘11010000’B D0 All PLMN-specificBS
‘11010001’B D1 plmn-specific BS-1
‘11011000’B D8 plmn-specificBS-8
‘11011001’B D9 plmn-specificBS-9
‘11011010’B DA plmn-specificBS-A
‘11011011’B DB plmn-specificBS-B
‘11011100’B DC plmn-specificBS-C
‘11011101’B DD plmn-specificBS-D
‘11011110’B DE plmn-specificBS-E
‘11011111’B DF plmn-specificBS-F
3.2.10 BCDDirectoryNumber
BCDDirectoryNumber ::= OCTET STRING(SIZE(1..14))
8 7 6 5 4 3 2 1
Octet 1 0/1 type of number Numbering plan
ext identification
Octet 2 1 Present 0 0 0 Screening
Ext Indicator Spare Indicator
Octet 5
..
..
Type Of Number:
Bits
7 6 5
0 0 0 unknown
0 0 1 international number
0 1 0 national number
0 1 1 network specific number
1 0 0 dedicated access, short code
1 0 1 reserved
1 1 0 reserved
1 1 1 reserved for extension
The destinationNumber/ originationNumber TON of SMS may be 5, the number
5 digit will be packed by 7-bit characters. See 4.1 for packing of 7-bit characters
Numbering plan identification:
Bits
4 3 2 1
0 0 0 0 Unknown
0 0 0 1 ISDN/telephony numbering plan (Rec. E.164/E.163)
0 0 1 1 data numbering plan (Recommendation X.121)
0 1 0 0 telex numbering plan (Recommendation F.69)
1 0 0 1 private numbering plan
1 0 1 1 reserved for CTS (see GSM 04.56)
1 1 1 1 reserved for extension

Number digits :
Bits Number digit value
4 3 2 1 or
8 7 6 5
0 0 0 0 0
0 0 0 1 1
0 0 1 0 2
0 0 1 1 3
0 1 0 0 4
0 1 0 1 5
0 1 1 0 6
0 1 1 1 7
1 0 0 0 8
1 0 0 1 9
1 0 1 0 *
1 0 1 1 #
1 1 0 0 a
1 1 0 1 b
1 1 1 0 c
1 1 1 1 used as an endmark in the case of an odd
number of number digits
Presentation indicator：
Bits
7 6
0 0 Presentation allowed
0 1 Presentation restricted
1 0 Number not available due to interworking
1 1 Reserved
If Octet 2 is omitted, the value “00 – Presentation allowed” is assumed
Screening indicator：
Bits
2 1
0 0 User-provided, not screened
0 1 User-provided, verified and passed
1 0 User-provided, verified and failed
1 1 Network provided
5 If octet 2 is omitted the value “00 – User provided, not screened” is assumed.
3.2.11 BillOrValidateFlag
BillOrValidateFlag ::= ENUMERATED
{
billRecord (1),
10 validateRecord (2)
}
3.2.12 BSCIdentification
BSCIdentification::= OCTET STRING (SIZE(2))
bit 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
spare main sub spc
octet 1 octet 2
15 The octet 1 appears first in the coding stream,followed by octet 2. For example,if the
spc14 is “7.4.5” , spccode=5, subspccode=4, maincode=7. the codeing stream is
0x38 0x25

3.2.13 CallDuration
CallDuration ::= INTEGER
3.2.14 CalledNumber
CalledNumber ::= BCDDirectoryNumber
53.2.15 CalledPartyNumber
CalledPartyNumber ::= BCDDirectoryNumber
3.2.16 CallEventRecordType
CallEventReocrdType ::= INTEGER
{
10 moCallRecord (0),
mtCallRecord (1),
roamingRecord (2),
incGatewayRecord (3),
outGatewayRecord (4),
15 transitCallRecord (5),
moSMSRecord (6),
mtSMSRecord (7),
moSMSIWRecord (8),
mtSMSGWRecord (9),
20 ssActionRecord (10),
hlrIntRecord (11),
moeCallRecord (12),
mcfCallRecord (13),
commonEquipRecord (14),
25 termCAMELIntRecord (17),
mtLCSRecord (23),
moLCSRecord (24),
niLCSRecord (25),
sigMTPStatisticRecord (41),
30 sigSCCPStatisticRecord (42),
uSSDRecord (43),
vIGRecord (44),
mGCFRecord (67),
}
353.2.17 CallingNum
CallingNum ::= ISDN-AddressString
3.2.18 CallingNumber
CallingNumber ::= BCDDirectoryNumber
3.2.19 CallingPartyCategory
40 CallingPartyCategory::= Category
3.2.20 CallReference
CallReference ::= OCTET STRING(SIZE(1..4))
8 7 6 5 4 3 2 1
Octet 1 (MSB) SeqNo
Octet 2 SeqNo Continue
Octet 3 SeqNo Continue

Octet 4 SeqNo Continue (LSB)
3.2.21 CAMELDestinationNumber
CAMELDestinationNumber ::= DestinationRoutingAddress
3.2.22 CAMELInformation
CAMELInformation ::= SET
5 {
cAMELDestinationNumber [1] CAMELDestinationNumber OPTIONAL,
connectedNumber [2] ConnectedNumber OPTIONAL,
10 seizureTime [5] TimeStamp OPTIONAL,
callDuration [8] CallDuration OPTIONAL,
15 cAMELInitCFIndicator [10] CAMELInitCFIndicator OPTIONAL,
cAMELModification [12] ChangedParameters OPTIONAL,
20 freeFormatDataAppend [15] BOOLEAN OPTIONAL,
freeFormatDataAppend_2 [17] BOOLEAN OPTIONAL
}
3.2.23 CAMELInitCFIndicator
25 CAMELInitCFIndicator ::= ENUMERATED
{
noCAMELCallForwarding (0),
cAMELCallForwarding (1)
}
303.2.24 CAMELModificationParameters
CAMELModificationParameters::= SET
{
callingPartyNumber [0] CallingNumber OPTIONAL,
callingPartyCategory [1] CallingPartyCategory OPTIONAL,
35 originalCalledPartyNumber [2] OriginalCalledNumber OPTIONAL,
genericNumbers [3] GenericNumbers OPTINAL,
redirectingPartyNumber [4] RedirectingNumber OPTIONAL,
redirectionCounter [5] NumberOfForwarding OPTIONAL
}
403.2.25 CAMELSMSInformation
CAMELSMSInformation::= SET
{
gsm-SCFAddress [1] Gsm-SCFAddress OPTIONAL,
45 defaultSMSHandling [3] DefaultSMS-Handling OPTIONAL,
callingPartyNumber [5] CallingNumber OPTIONAL,
destinationSubscriberNumber [6] CalledNumber OPTIONAL,

cAMELSMSCAddress [7] AddressString OPTIONAL

smsRefrenceNumber [8] INTEGER OPTIONAL
}
3.2.26 Carp
5 Carp::=INTEGER
3.2.27 Category
Category ::= OCTET STRING (SIZE(1))
From ITU-T Q.763E:
8 7 6 5 4 3 2 1
Octet 1 Calling party’s category
10
Value Meaning
Binary Decimal
00000000 0 Unknown
00000001 1 Operator, French
00000010 2 Operator, English
00000011 3 Operator, German
00000100 4 Operator, Russian
00000101 5 Operator, Spanish
00000110 6 Language adopted by both parties through
negotiation, Chinese
negotiation
negotiation, Japanese
00001001 9 National operator
00001010 10 Common calling subscriber
00001011 11 Preferred calling subscriber
00001100 12 Data service call
00001101 13 Test call
00001110 14 Idle
00001111 15 Payphone
00010000 16 Idle
to
11011111
11110000 240 Common calling subscriber, free
11110001 241 Common calling subscriber, pay in regular
period
11110010 242 Common calling subscriber, list of subscribers,
instant
11110011 243 Common calling subscriber, printer, instant
11110100 244 Preferred calling subscriber, free
11110101 245 Preferred calling subscriber, pay in regular
period
11111111 Idle
3.2.28 CauseForTerm
CauseForTern ::= ENUMERATED
{
15 normalRelease (0),
partialRecord (1),
partialRecordCallReestablishment (2),
unsuccessfulCallAttempt (3),

stableCallAbnormalTermination (4),
cAMELInitCallRelease (5),
volumeLimit (16),
timeLimit (17),
5 sGSNChange (18),
maxChangeCond (19),
managementIntervention (20)
unauthorizedRequestingNetwork (52),
unauthorizedLCSClient (53),
10 positionMethodFailure (54),
unknownOrUnreachableLCSClient (58),
cAMELPlayTone (101),
falseAnswerCharge (103)
}
153.2.29 ChangedParameters
ChangedParameters ::= SET
{
changeFlags [0] ChangeFlags,
changeList [1] CAMELModificationParameters OPTIONAL
20 }
3.2.30 ChangeFlags
ChangeFlags ::= BIT STRING
{
callingPartyNumberModified (0),
25 callingPartyCategoryModified (1),
originalCalledPartyNumberModified (2),
genericNumbersModified (3),
redirectingPartyNumberModified (4),
redirectionCounterModified (5)
30 }
3.2.31 ChangeOfClassmark
ChangeOfClassmark ::= SEQUENCE
{
classmark [0] Classmark,
35 changeTime [1] TimeStamp
}
3.2.32 ChangeOfRadioChannel
ChangeOfRadioChannel ::= SEQUENCE
{
40 radioChannel [0] TrafficChannel,
speechVersionUsed [2] SpeechVersionIdentifier OPTIONAL
}
3.2.33 ChangeOfService
45 ChangeOfService ::= SEQUENCE
{
basicService [0] BasicServiceCode,
transparencyInd [1] TransparencyInd OPTIONAL,

changeTime [2] TimeStamp

}
3.2.34 ChannelCoding
ChannelCoding ::= ENUMERATED
5 {
tchF4800 (1),
tchF9600 (2),
tchF14400 (3)
}
103.2.35 ChargeIndicator
ChargeIndicator ::= INTEGER
{
noCharge (0),
Charge (1)
15 }
3.2.36 ChargedParty
ChargedParty ::= ENUMERATED
{
CallingAsChargedParty (0),
20 CalledAsChargedParty (1),
NoCharging (2),
AnotherNumAsChargedParty (3)
}
3.2.37 CICCode
25 CICCode ::= SEQUENCE
{
pcmUnit [0] INTEGER,
channel [1] INTEGER
}
303.2.38 Classmark
Classmark ::= OCTET STRING(SIZE(1..3))
8 7 6 5 4 3 2 1
Octet 1 0 Revision ES A5/1 RF power
spare level IND capability
Octet 2 0 PS SS Screen. SM VBS VGC FC
spare capa. Indicator capabi. S
Octet 3 CM3 0 LCSVA UCS SoLSA CMS A5/3 A5/2

spare CAP 2 P
3.2.39 ConnectedNumber
ConnectedNumber::= BCDDirectoryNumber

3.2.40 CUGCategory
CUGCategory ::= SEQUENCE
{
callType [0] INTEGER,
5 userType [1] INTEGER
}
3.2.41 CUGIndex
CUGIndex::= INTEGER
3.2.42 CUGInterLockCode
10 CUGInterLockCode ::= OCTET STRING(SIZE(1..4))
3.2.43 DataRate
DataRate ::= INTEGER
3.2.44 DataVolume
DataVolume ::= INTEGER
153.2.45 DefaultCallHandling
DefaultCallHandling ::= ENUMERATED
{
continueCall (0),
releaseCall (1)
20 }
3.2.46 DefaultSMS-Handling
DefaultSMS-Handling ::= ENUMERATED
{
continueTransaction (0) ,
25 releaseTransaction (1)
}
3.2.47 DeferredLocationEventType
DeferredLocationEventType ::= BIT STRING
{
30 msAvailable (0)
} (SIZE (1..16))
3.2.48 DestinationRoutingAddress
DestinationRoutingAddress ::= CalledPartyNumber
3.2.49 Diagnostics
35 Diagnostics ::= CHOICE
{
gsm0408Cause [0] INTEGER,
-- See TS 24.008

gsm0902MapErrorValue [1] INTEGER,

-- Note: The value to be stored here corresponds to
-- the local values defined in the MAP-Errors and
-- MAP-DialogueInformation modules, for full details
5 -- see TS 29.002.
ccittQ767Cause [2] INTEGER,
-- See ITU-T Q.767
networkSpecificCause [3] ManagementExtensions,
-- To be defined by network operator
10 manufacturerSpecificCause [4] ManagementExtensions
SS- To be defined by manufacturer
}
networkSpecificCause value：
Scope(Hex) Dec Hex Description
The “TUP” diagnostic results
are as follows
Call succeeded
07D0 + 01f0 Caller hooks on first during a
2496 09C0
call.
+ 01f1 Calleed hooks on first during
2497 09C1
a call.
+ 01f2 Forced releasing at the caller
2498 09C2
side during communication.
+ 01f3 Forced releasing at the called
2499 09C3
side during communication.
+ 01f4 CCL is received, but the line is
disconnected due to the
2500 09C4
followed office with old
specifications.
+ 01f5 The circuit is blocked during
2501 09C5
communication.
Forward error
07D0 + 0100 2256 08D0 Conducting examination error
+ 0101 Forward circuit recovery is recived
2257 08D1 when reciving number.
+ 0102 Forward circuit group recovery is
2258 08D2 recived when reciving number.
+ 0103 Forward hardware group blockage
2259 08D3 is recived when reciving number.
2260 08D4 when ringing.
2261 08D5 recived when ringing.
2262 08D6 is recived when ringing.
2263 08D7 during a call.
2264 08D8 recived during a call.
2265 08D9 is recived during a call.
+ 010a Forward circuit recovery is recived
2266 08DA during pause.
+ 010b Forward circuit group recovery is
2267 08DB recived during pause.
+ 010c Forward hardware group blockage
2268 08DC is recived during pause.
Forward release
07D0 + 0110 Forward release is received when
2272 08E0
reciving number
+ 0111 Forward release is received when
2273 08E1
ringing

Backward failed
07D0 + 00f0 2240 08C0 Circuit blocked
+ 00f1 2241 08C1 Switching equipment congestion
+ 00f2 2242 08C2 Circuit group congestion
+ 00f3 2243 08C3 Domestic network congestion
+ 00f4 2244 08C4 Incomplete address
+ 00f5 2245 08C5 Call fault
+ 00f6 2246 08C6 Unknown busy
+ 00f7 2247 08C7 Unallocated number
+ 00f8 2248 08C8 Line fault
+ 00f9 2249 08C9 Sending dedicated signal tone
+ 00fa 2250 08CA Access prohibited
+ 00fb 2251 08CB Digital channel unavailable
+ 00fd 2253 08CD Local call busy
+ 00fe 2254 08CE Toll busy
+ 00ff Backward transmitted conduction
2255 08CF fault
+ 0001 2001 07D1 Unallocated No.
+ 0002 No route to assigned transfer
2002 07D2
network.
+ 0003 2003 07D3 No route to destination
+ 0004 2004 07D4 Sending dedicated information tone
+ 0005 2005 07D5 Misdialing toll number header
+ 0008 2008 07D8 Preoccupied
+ 0009 Preoccupied—circuit is reserved for
2009 07D9
reuse.
+ 0011 2017 07E1 Uer on busy
+ 0012 2018 07E2 User not responding
+ 0013 2019 07E3 No reply from user
+ 0014 2020 07E4 Absent user
+ 0015 2021 07E5 Call rejected
+ 0016 2022 07E6 Number changed
+ 001b 2027 07EB Unreachable destination
+ 001c 2028 07EC Invalid number format
+ 001d 2029 07ED Performance rejected
+ 001f 2031 07EF Normal – unspecified
+ 0022 2034 07F2 No circuit/ valid channel
+ 0026 2038 07F6 Abnormal network operation
+ 0029 2041 07F9 Temporary fault
+ 002a 2042 07FA Switching equipment congestion
+ 002b 2043 07FB Access information discarded
+ 002c 2044 07FC Unavailable circuit/channel
+ 002e 2046 07FE Priority call congestion
+ 002f 2047 07FF Unavailable resource—unspecified
+ 0057 2087 0827 Called is not member of CUG
+ 0058 2088 0828 Destination incompatible
+ 005a 2090 082A Inexistent CUG
+ 005b 2091 082B Invalid transit network
+ 005f 2095 082F Invalid information, unspecified
+ 007f 2127 084F Interworking-unspecified
+ 0080 Backward circuit maintenance
2128 0850
congestion is received when dialing.
+ 0081 Backward circuit recovery
2129 0851
+ 0082 Backward circuit group recovery
2130 0852
+ 0083 Backward hardware group recovery
2131 0853
+ 0084 Backward circuit recovery is
2132 0854
received when ringing.
+ 0085 Backward circuit group recovery is
2133 0855
received when ringing.
2134 0856
is received when ringing.

+ 0087 Backward circuit recovery is

2135 0857
received during a call.
+ 0088 Backward circuit group recovery is
2136 0858
received during a call.
2137 0859
is received during a call.
+ 008a Backward circuit recovery is
2138 085A
received during pause.
+ 008b Backward circuit group recovery is
2139 085B
received during pause.
+ 008c Backward hardware group recovery
2140 085C
is received during pause.
Local resource Insufficient or
fault
07D0 + 0150 2336 0920 Outgoing trunk unavailable
+ 0151 2337 0921 Digital trunk unavailable
+ 0152 2338 0922 Re-routing error
+ 0153 2339 0923 Buffer area overflow
+ 0154 2340 0924 No timer
+ 0155 2341 0925 No check tone time slot
+ 0156 2342 0926 Busy communication
+ 0157 2343 0927 Communication terminated
+ 0158 2344 0928 No Snet time slot
+ 0159 2345 0929 No Tnet time slot
+ 015a 2346 092A Callee blocked
+ 015b 2347 092B Release TN_Bridge abnormal
+ 015c 2348 092C Conduction examination error
+ 0090 2144 0860 Outgoing trunk unavailable
+ 0091 2145 0861 Digital trunk unavailable
+ 0092 2146 0862 Re-routing error
+ 0093 2147 0863 Buffer area overflow
+ 0094 2148 0864 No timer
+ 0095 2149 0865 No check tone time slot
+ 0096 2150 0866 Busy communication
+ 0097 2151 0867 Communication terminated
+ 0098 2152 0868 No Snet time slot
+ 0099 2153 0869 No Tnet time slot
+ 009a 2154 086A Callee blocked
+ 009b 2155 086B Release TN_Bridge abnormal
+ 00a0 2160 0870 Local circuit recovery during a call.
+ 00a1 Local circuit group recovery during
2161 0871
a call.
+ 00a2 Local hardware group blocked
2162 0872
during a call.
+ 00a3 2163 0873 Local circuit recovery during pause.
+ 00a4 Local circuit group recovery during
2164 0874 pause.
+ 00a5 Local hardware group blocked
2165 0875 during pause.
+ 00a6 2166 0876 Forced release during a call
+ 00a7 2167 0877 Forced release during pause
Requested service unavailable
07D0 + 0032 2050 0802 Reuested facility not precoocupied
+ 0035 2053 0805 Outgoing call barred in CUG
+ 0037 2055 0807 Incoming call barred in CUG
+ 0039 2057 0809 Bearer capability unauthorized
+ 003a 2058 080A Bearer capability unavailable
+ 003e Specified access information not
2062 080E coordinate with subscriber category
+ 003f Service /option unavailable,
2063 080F unspecified
Locally generated
+ 00b0 2176 0880 Requested facility not preoccupying
+ 00b1 2177 0881 Outgoing call barred in CUG

+ 00b2 2178 0882 Incoming call barred in CUG

+ 00b3 2179 0883 Bearer capability unauthorized
+ 00b4 2180 0884 Bearer capability unavailable
+ 00b5 Specified access information not
2181 0885 coordinate with subscriber category
+ 00b6 Service /option unavailable,
2182 0886 unspecified
Requested service not implemented
07D0 + 0041 2065 0811 Bearer capability not implemented
+ 0045 Requested facility not
2069 0815
implemented
+ 0046 Only restricted digital
2070 0816 information bearing
capability available
+ 004f Service /option unavailable,
2079 081F
unspecified
Locally generated
+ 00c0 2192 0890 Bearer capability not implemented
+ 00c1 Requested facility not
2193 0891
implemented
+ 00c2 Only restricted digital
2194 0892 information bearing
+ 00c3 Service /option unavailable,
2195 0893 unspecified
Protocol error and time expiry of
timer
07D0 + 0160 Time expiry in waiting for
2352 0930 COT/CCF signal
+ 0161 Time expiry in waiting for ‘address
2353 0931 completely received’ signal
+ 0162 Time expiry in waiting for
2354 0932 backwark check monotone
+ 0163 2355 0933 Time expiry in digit interval
+ 0164 2356 0934 Incomplete address
+ 0165 2357 0935 Equal SP code
+ 0166 Receiving abnormal message during
2358 0936
call connection
+ 0167 Abnormal interoffice release
2359 0937
signaling
+ 0168 Abnormal interoffice GSM/GRQ
2360 0938
signaling
+ 0061 Message type not existent or not
2097 0831
implemented
+ 0063 Parameter not existent or not
2099 0833
implemented
+ 0066 2102 0836 Timer recovery finally
+ 0067 Parameter not existent or not
2103 0837 implemented- transit
+ 006d Receiving abnormal message during
2109 083D call connection
+ 006e Message with unidentified
2110 083E parameter- discarded
+ 006f 2111 083F Protocol error, unspecified
Local call connection error
07D0 + 0170 2368 0940 Vacant callee number
+ 0172 2370 0942 Forced call clearing
+ 0173 2371 0943 Forced call clearing during dialing
+ 0174 2372 0944 Forced call clearing during ringing
+ 0175 Circuit blocked by maintenance
2373 0945 when dialing
+ 0176 Circuit blocked by circuit when
2374 0946 dialing
+ 0177 Circuit blocked by hardware when
2375 0947 dialing

+ 0178 2376 0948 Transit No. abnormal

+ 0179 Access information not coordinate
2377 0949 with subscriber ©
+ 017a 2378 094A Callee local call busy
+ 017b 2379 094B Callee toll busy
+ 017c 2380 094C SeizingBlockedTrunk
+ 00d0 2208 08A0 Vacant callee number
+ 00d1 2209 08A1 Call transfer exceeding limits
+ 00d2 2210 08A2 Call repeating time exceeding limits
+ 00d4 2212 08A4 Forced call clearing when dialing
+ 00d5 2213 08A5 Forced call clearing when ringing
+ 00d6 Local circuit maintenance blocked
2214 08A6 when dialling
+ 00d7 Local circuit hardware blocked
2215 08A7 when dialling
+ 00d8 2216 08A8 Local circuit recovery when dialing
+ 00d9 Local circuit group recovery when
2217 08A9
dialling
+ 00da Local circuit hardware blocked
2218 08AA
when ringing
+ 00db 2219 08AB Local circuit recovery when ringing
+ 00dc Local circuit group recovery when
2220 08AC ringing
+ 00dd 2221 08AD Transit number abnormal
+ 00de Access information not coordinate
2222 08AE
with subscriber category
+ 00df 2223 08AF Callee on busy
+ 00e0 2224 08B0 Local data error
+ 00e1 2225 08B1 Subscriber not responding
+ 00e2 2226 08B2 No reply from subscriber
+ 00e3 2227 08B3 Subscriber absense
+ 00e4 2228 08B4 Call rejected
+ 00e5 2229 08B5 Destination unreachable
+ 00e6 2230 08B6 Invalid number format
+ 00e7 2231 08B7 Performance rejected
+ 00e8 2232 08B8 Caller information unavailable
+ 00e9 2233 08B9 No.7 SP congestion
+ 00ea 2234 08BA Switch overload
8000 + 0110 Normal call clearing invoked by the

33040 8110 other MS side
+ 0190 Normal call clearing invoked by
33168 8190 TUP, ISUP or CAS user
+ 011c 33052 811C LAI index error
+ 021c 33308 821C Vacant called number
+ 031c 33564 831C Subscriber line No. error
+ 041c 33820 841C Called number too short
+ 0116 33046 8116 Number changed
8000 + 011f 33055 811F Timer expiry on out-call process

+ 021f Timer expiry on waiting
33311 821F CONNECT_ACK from MS
+ 031f RELEASE_CMP received from MS
33567 831F on OP waiting COMPLETE-CALL
33823 841F on OP waiting ASSIGNMENT-CNF
34079 851F on OP waiting TP’s response
34335 861F on OP waiting ALERTING
34591 871F on OP waiting CONNECT
34847 881F on TP waiting OP’s SETUP


35103 891F
on TP waiting ASSIGNMENT-CNF
+ 0a1f RELEASE_CMP received from MS
35359 8A1F
on TP waiting ALERTING
+ 0b1f RELEASE_CMP received from MS
35615 8B1F
on TP waiting MS’s CONNECT
+ 0c1f RELEASE_CMP received from MS
35871 8C1F
on talking status
+ 0d1f RELEASE_CMP received from MS
36127 8D1F
on waiting MS’s RELEASE
8000 + 0103 No route to destination (Timer

33027 8103 expiry on waiting ROUTING-ACK)
+ 0203 No route to destination (Timer
33283 8203 expiry on querying TP’s module)
8000 + 0112 33042 8112 Timer expiry on in_call process

+ 0212 Timer expiry on waiting
33298 8212 ALERTING
+ 0312 Timer expiry on waiting MS’s
33554 8312 CALL-CONFIRM
+ 011b Destination system disorder (Timer

33051 811B
expiry on waiting TP’ response)
8000 + 0113 Ringing without 104ontrans from

33043 8113 user (Timer expiry on OP waiting
TP’s CONNECT)
+ 0213 Ringing without 104ontrans from
33299 8213 user (Timer expiry on TP waiting
MS’s CONNECT)
8000 + 0129 33065 8129 Parameter error on DN analysis

+ 0229 Timer expiry on OP waiting TP’s
33321 8229 SETUP
+ 0329 Timer expiry on TP waiting OP’s
33577 8329 INFO-ACK
+ 0429 33833 8429 TLN (Time-slot error)
+ 0529 Temporary overtime in handover
34089 8529
process
8000 + 0126 33062 8126 DAS non-existent

+ 0226 33318 8226 Fail on re-occuping trunk circuit
+ 0326 33574 8326 Fail on re-occuping time-slot
+ 0122 33058 8122 Terrestrial circuit unavailable
8000 + 012a Switching equipment congestion

33066 812ª (Time-slot busy)
+ 022a Switching equipment congestion
33322 822A (Timer expiry on waiting BRIDEG)
33578 832A (Bridge unavailable)
33834 842A (SLN unavailable)
8000 + 012f Resource unavailable (Timer expiry

33071 812F
on waiting ASSIGNMENT-CNF)
+ 022f Resource unavailable (Timer expiry
33327 822F on waiting MM connection
established)
+ 032f Resource unavailable (DTMF
33583 832F unavailable)
+ 042f Resource unavailable (SCCP
33839 842F disconnected)

+ 052f Resource unavailable (BSC circuit

34095 852F
reseted)
+ 082f Resource unavailable (clear request
34863 882F
from BSC)
+ 00ac (opposite end release) Circuit/path
32940 80AC
unavailable
+ 00ae (opposite end release) Priority call
32942 80AE
blocked)
+ 00af (opposite end release) (Priority call
32943 80AF
blocked)
8000 + 00b2 (opposite end release) Facility not

32946 80B2 registered)
+ 00b5 (opposite end release) Outgoing
32949 80B5 prohibited within CUG)
+ 00b7 (opposite end release) Incoming
32951 80B7 prohibited within CUG)
+ 00b9 (opposite end release) Bearer
32953 80B9 capability unauthorized
+ 00ba (opposite end release) Bearer
32954 80BA capability unavailable
+ 00be (opposite end release) Access
32958 80BE information not coordinate with
subscriber category
+ 00bf (opposite end release) Service or
32959 80BF
option unavailable, unspecified
8000 + 00c1 (opposite end release) Bearer

32961 80C1 capability not implemented
+ 00c5 (opposite end release) Facility not
32965 80C5 implemented
+ 00c6 (opposite end release) Only
32966 80C6 restricted digital information bearer
+ 00cf (opposite end release) Service or
32975 80CF option not implemented,
unspecified
8000 + 00d7 (opposite end release) Callee not

32983 80D7
member of CUG
+ 00d8 (opposite end release) Destination
32984 80D8
incompatible
+ 00da (opposite end release) CUG non-
32986 80DA
existent
+ 00db (opposite end release) Invalid transit
32987 80DB
network
+ 00df (opposite end release) Invalid
32991 80DF
message
8000 + 00e1 (opposite end release) Message type

32993 80E1 not exist or unimplemented
+ 00e3 (opposite end release) Parameter
32995 80E3 discarded
+ 00e6 (opposite end release) Recovery
32998 80E6 from timer expiry
+ 00e7 (opposite end release) Parameter
32999 80E7 discarded—Passed
+ 00ee (opposite end release) Parameter
33006 80EE unrecognized—Discarded
+ 00ef (opposite end release) Protocol
33007 80EF misunderstanding, unspecified
+ 00ff (opposite end release) Interworking
33023 80FF problem)
+ 0210 33296 8210 Normal call release (MS hooking on

while alerting)
+ 013f Service unavailable
33087 813F (CLIRInvocation error)
8000 + 0e1f (GMSC) Unknown service type

36383 8E1F
(Unknown svCAT)
+ 0f1f (GMSC) Original MsIsdn Number
36639 8F1F
Error
+ 101f 36895 901F (GMSC) MSRN number error
+ 111f 37151 911F (GMSC) Routing Information Error
37407 921F
on TP waiting MS’s call confirm
+ 131f 37663 931F Timer expiry in handover process
+ 0115 Call barred (originating call:

33045 8115 outgoing call barred; terminating
call: incoming call barred)
+ 0222 33314 8222 Radio channel congested
+ 062f No available resource (Release
34351 862F
DTMF resource error)
+ 072f No available resource (Assignment
34607 872F
fail)
+ 173a Bearing capability unavailable
38714 973A
(Only speech service provided now)
8000 + 0145 Requested facility not implemented

33093 8145 (Timer expiry while waiting for
AOCC ACK message)
+ 0245 Requested performance not
33349 8245 implemented (Fail on acquiring
AOC information)
+ 0345 Requested performance not
33605 8345 implemented (AOCC ACK message
error)
8000 + 043f Service unavailable (Invalid CW

33855 843F service)
+ 053f 34111 853F Service unavailable (Forword fail)
+ 053f 34111 853F Service unavailable (Forword fail)
+ 063f Service unavailable (Err forword
34367 863F times)
+ 073f Service unavailable (CF bill table
34623 873F overflow)
+ 083f Service unavailable (Handover
34879 883F unsupported)
+ 093f Service unavailable (InterHO table
35135 893F overflow)
+ 051c 34076 851C Invalid CI

+ 061c 34332 861C Invalid handover number
ccittQ767Cause value:
Value(Dec) Description
Normal Class
1 Unassigned/unallocated number
3 No route to destination
4 Send special information tone)
6 Channel unacceptable
8 Operator determined barring
16 Normal call clearing
17 User busy
18 No user responding
19 User alerting, no answer
21 Call rejected
22 Number changed

26 Non-selected user clearing<--not supported

27 Destination out of order
28 Invalid number format or incomplete number
29 Facility rejected
30 Response to STATUS ENQUIRY
31 Normal,unspecified
Resource unavailable class
34 No circuit/channel available
38 Network out of order
41 Temporary failure
42 Switching equipment congestion
43 (Access © discarded
44 Requested circuit/channel not available
47 Resource unavailable,unspecified
Service or option not available class
49 Quaity of service unavailable
50 Requested facility not subscribed
55 Incoming calls barred within the CUG
57 Bearer capability not authorized
58 Bearer capability not presenty available
63 Service or option not available,unspecified
Service or option not implemented class
65 Bearer service not implemented
68 ACM equal to or greater than ACMmax
69 Requested facility not implemented
70 Only restricted digital information bearer capability
is available
71 Service or option not implemented,unspecified
Invalid message class
81 Invalid transaction identifier value
87 called user not member of CUG
88 Incompatible destination
91 Invalid transit network selection
95 Semantically incorrect message
protocol error class
96 Invalid mandatory information(3GPP)
97 Invalid 107ontransp information,Message type
nonexistent or not implemented
98 Message type non-existent or not implemented,Parameter
not existent or not implemented discarded
99 Message type not compatible with 107ontrans state
100 Information element no-existent or not
implemented;3GPP：conditional IE error
101 Condiional IE error
102 Message not compatible with protocol state,Recovery on
timer expiry
103 Recovery on timer expiry,Parameter nonexistent or not
implemented passed on
111 Protocol error,unspecified
interworking class
127 Interworking,unspecified
3.2.50 EMLPPriorityLevel
EMLPPriorityLevel ::= INTEGER
3.2.51 EMLPRequestPriorityLevel
5 EMLPRequestPriorityLevel ::= INTEGER
3.2.52 Eparameter
Eparameter::= INTEGER (0..1023)

3.2.53 EquipmentId
EquipmentId ::= INTEGER
3.2.54 EquipmentType
EquipmentType::= INTEGER
5 {
conferenceBridge (0)
}
3.2.55 Ext-GeographicalInformation
Ext-GeographicalInformation ::=
10 OCTET STRING (SIZE (1..maxExt-GeographicalInformation))
maxExt-GeographicalInformation INTEGER ::= 20
3.2.56 Fnur
Fnur ::= ENUMERATED
{
15 Fnur9600-BitsPerSecond (1),
Fnur14400BitsPerSecond (2),
20 Fnur48000BitsPerSecond (6),
Fnur64000BitsPerSecond (8)
}
3.2.57 ForwardCallIndicator
25 ForwardCallIndicator ::= ENUMERATED
{
nationalIncoming (0),
internationalIncoming (1),
unknown (255)
30 }
3.2.58 ForwardedSubNumber
ForwardedSubNumber::= AddressString
3.2.59 ForwardToNumber
ForwardToNumber ::= AddressString
353.2.60 FreeFormatData
FreeFormatData ::= OCTET STRING (SIZE(1..160))
3.2.61 GatewayRecordType
GatewayRecordType ::= ENUMERATED
{
40 gatewayRecord (0),

trunkRecord (1)
}
3.2.62 GenericNumber
GenericNumber ::= BCDDirectoryNumber
53.2.63 GenericNumbers
GenericNumbers ::= SET OF GenericNumber
3.2.64 Gsm-SCFAddress
Gsm-SCFAddress ::= ISDNAddressString
3.2.65 GuaranteedBitRate
10 GuaranteedBitRate ::= ENUMERATED
{
gBR14400BitsPerSecond (1), -- BS20 non-transparent
gBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent
TT- BS30 transparent and multimedia
15 gBR32000BitsPerSecond (3), -- BS30 multimedia
gBR33600BitsPerSecond (4), -- BS30 multimedia
gBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
gBR57600BitsPerSecond (6), -- BS20 non-transparent
gBR64000BitsPerSecond (7) -- BS30 transparent and multimedia
20 }
3.2.66 HLRIntResult
HLRIntResult ::= Diagnostics
3.2.67 HotBillingTag
HotBillingTag::= INTEGER
25 {
noHotBilling (0),
HotBilling (1)
}
3.2.68 HotBillingTag2
30 HotBillingTag2::= INTEGER
{
postPayed (0),
prePaied (1)
}
353.2.69 HSCSDParmsChange
HSCSDParmsChange ::= SEQUENCE
{
hSCSDChanAllocated [1] NumOfHSCSDChanAllocated,
40 initiatingParty [2] InitiatingParty OPTIONAL,
chanCodingUsed [4] ChannelCoding,
hSCSDChanRequested [5] NumOfHSCSDChanRequested OPTIONAL

3.2.70 IMEI
IMEI ::= TBCD-STRING (SIZE (8))
3.2.71 IMS-Charging-Identifier(MGCF)
5 IMS-Charging-Identifier ::= OCTET STRING
3.2.72 IMSI
IMSI ::= TBCD-STRING (SIZE (3..8))
3.2.73 Incomplete-CDR-Indication(MGCF)
Incomplete-CDR-Indication ::= SET
10 {
aCRStartLost [0] BOOLEAN,
aCRInterimLost [1] ACRInterimLost,
aCRStopLost [2] BOOLEAN
}
153.2.74 InitiatingParty
InitiatingParty::= ENUMERATED
{
network (0),
subscriber (1)
20 }
3.2.75 InterOperatorIdentiferlist(MGCF)
InterOperatorIdentifierlist ::= SEQUENCE OF InterOperatorIdentifiers
3.2.76 InterOperatorIdentifiers
InterOperatorIdentifiers ::= SEQUENCE
25 {
originatingIOI [0] GraphicString OPTIONAL,
terminatingIOI [1] GraphicString OPTIONAL
}
3.2.77 InvolvedParty(MGCF)
30 InvolvedParty ::= CHOICE
{
sIP-URI [0] GraphicString,
tEL-URI [1] GraphicString
}
353.2.78 IPAddress
IPAddress ::= CHOICE
{
iPBinaryAddress IPBinaryAddress,
iPTextRepresentedAddress IPTextRepresentedAddress

3.2.79 IPBinaryAddress
IPBinaryAddress ::= CHOICE
{
5 iPBinV4Address [0] OCTET STRING (SIZE(4)),
iPBinV6Address [1] OCTET STRING (SIZE(16))
}
3.2.80 IPTextRepresentedAddress
IPTextRepresentedAddress ::= CHOICE
10 {
iPTextV4Address [2] IA5String (SIZE(7..15)),
iPTextV6Address [3] IA5String (SIZE(15..45))
}
3.2.81 ISDN-AddressString
15 ISDN-AddressString ::= AddressString (SIZE (1..maxISDN-AddressLength))
maxISDN-AddressLength INTEGER ::= 9
3.2.82 ISDN-SubaddressString
ISDN-SubaddressString ::= OCTET STRING (SIZE (1..maxISDN-
SubaddressLength))
20 maxISDN-SubaddressLength INTEGER ::= 21
8 7 6 5 4 3 2 1
Octet 1 1 type of subaddress O/ 0 0 0
ext E Un Used
Octet 4
..
..
type of subaddress:
Bits
7 6 5
0 0 0 NSAP (X.213/ISO 8348 AD2)
0 1 0 User Specified
odd/even indicator：
Bits
4
0 even number of address signals
1 odd number of address signals
3.2.83 LCSCause
LCSCause ::= OCTET STRING (SIZE(1))

LCS Cause value (octet 3)

Bits
87654321
0 0 0 0 0 0 0 0 Unspecified
0 0 0 0 0 0 0 1 System Failure
0 0 0 0 0 0 1 0 Protocol Error
0 0 0 0 0 0 1 1 Data missing in position request
0 0 0 0 0 1 0 0 Unexpected data value in position request
0 0 0 0 0 1 0 1 Position method failure
0 0 0 0 0 1 1 0 Target MS Unreachable
0 0 0 0 0 1 1 1 Location request aborted
0 0 0 0 1 0 0 0 Facility not supported
0 0 0 0 1 0 0 1 Inter-BSC Handover Ongoing
0 0 0 0 1 0 1 0 Intra-BSC Handover Complete
0 0 0 0 1 0 1 1 Congestion
00001100
to unspecified in this version of the protocol
11111111
3.2.84 LCSClientExternalID
LCSClientExternalID ::= SEQUENCE
{
externalAddress [0] AddressString OPTIONAL
5 }
3.2.85 LCSClientInternalID
LCSClientInternalID ::= ENUMERATED
{
broadcastService (0),
10 o-andM-HPLMN (1),
o-andM-VPLMN (2),
anonymousLocation (3),
targetMSsubscribedService (4)
...
15 }
3.2.86 LCSClientIdentity
LCSClientIdentity::= SEQUENCE
{
lcsClientExternalID [0] LCSClientExternalID OPTIONAL,
20 lcsClientDialedByMS [1] AddressString OPTIONAL,
lcsClientInternalID [2] LCSClientInternalID OPTIONAL
}
3.2.87 LCSClientType
LCSClientType ::= ENUMERATED
25 {
emergencyServices (0),
valueAddedServices (1),
plmnOperatorServices (2),
lawfulInterceptServices (3)
30 ...
}

3.2.88 LCS-Priority
LCS-Priority ::= OCTET STRING (SIZE (1))
-- 0 = highest priority
-- 1 = normal priority
5 -- all other values treated as 1
3.2.89 LCSQoSInfo
LCSQoSInfo::= OCTET STRING (SIZE(4))
8 7 6 5 4 3 2 1
Octet 1 Spare VERT
Octet 2 HA Horizontal Accuracy
Octet 3 VA Vertical Accuracy
Octet 4 RT Spare
Octet 1
VERT = vertical coordinate indicator
10 0 : vertical coordinate not requested
1 : vertical coordinate is requested
Octet 2
bit 8 HA = horizontal accuracy indicator
0 : Horizontal Accuracy is not specified
15 1 : Horizontal Accuracy is specified
bits 7-1 Horizontal Accuracy :
spare (set all zeroes) if HA=0
set to 7 bit uncertainty code in 3GPP TS 23.032 if HA=1
Octet 3 – applicable only if VERT = 1
20 bit 8 VA = vertical accuracy indicator
0 : Vertical Accuracy is not specified
1 : Vertical Accuracy is specified
bits 7-1 Vertical Accuracy :
spare (set all zeroes) if VA=0
25 set to 7 bit uncertainty altitude code in 3GPP TS 23.032 if VA=1
Octet 4
bits 8-7 RT = response time category
00 : Response Time is not specified
01 : Low Delay
30 10 : Delay Tolerant
11 : reserved
bits 6-1 spare
3.2.90 LevelOfCAMELService
LevelOfCAMELService::= BIT STRING
35 {
basic (0),
callDurationSupervision (1),
onlineCharging (2)
}
403.2.91 LocationAreaAndCell
LocationAreaAndCell ::= SEQUENCE
{
locationArea [0] LocationAreaCode,
rncID [1] RncId OPTIONAL
45 }

3.2.92 LocationAreaCode
LocationAreaCode ::= OCTET STRING (SIZE(9))
8 7 6 5 4 3 2 1
Octet 1 MCC digit 2 MCC digit 1
Octet 2 MNC digit 3 MCC digit 3
Octet 3 MNC digit 2 MNC digit 1
Octet 4 (MSB) LAC
Octet 5 LAC Continue (LSB)
Octet 6 (MSB) CI
Octet 7 CI Continue (LSB)
Octet 8 (MSB) SAC
Octet 9 SAC Continue (LSB)
3.2.93 LocationChange
LocationChange ::= SEQUENCE
5 {
location [0] LocationAreaAndCell,
changeTime [1] TimeStamp
}
3.2.94 LocationEstimateType
10 LocationEstimateType ::= ENUMERATED
{
currentLocation (0),
currentOrLastKnownLocation (1),
initialLocation (2),
15 ...,
activateDeferredLocation (3),
cancelDeferredLocation (4)
}
3.2.95 LocationType
20 LocationType ::= SEQUENCE
{
locationEstimateType [0] LocationEstimateType,
deferredLocationEventType [1] DeferredLocationEventType OPTIONAL
}
253.2.96 LongPartSeqNumber
LongPartSeqNumber ::= INTEGER
3.2.97 ManagementExtensions
ManagementExtensions ::=INTEGER
3.2.98 MaximumBitRate
30 MaximumBitRate ::= ENUMERATED
{
mBR14400BitsPerSecond (1), -- BS20 non-transparent
mBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,

UU- BS30 transparent and multimedia

mBR32000BitsPerSecond (3), -- BS30 multimedia
mBR33600BitsPerSecond (4), -- BS30 multimedia
mBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
5 mBR57600BitsPerSecond (6), -- BS20 non-transparent
mBR64000BitsPerSecond (7) -- BS30 transparent and multimedia
}
3.2.99 McfType
McfType ::= ENUMERATED
10 {
unconditional (0),
busy (1),
notReply (2),
notReachable (3),
15
115ontrans (254)
}
3.2.100 Media-Components-List(MGCF)
Media-Components-List ::= SEQUENCE
20 {
sIP-Request-Timestamp [0] TimeStamp OPTIONAL,
sIP-Response-Timestamp [1] TimeStamp OPTIONAL,
sDP-Media-Components [2] SEQUENCE OF SDP-Media-Component OPTIONAL,
mediaInitiatorFlag [3] NULL OPTIONAL,
25 sDP-Session-Description [4] SEQUENCE OF GraphicSTRING OPTIONAL
}
3.2.101 MessageBody(MGCF)
MessageBody ::= SEQUENCE
{
30 Content-Type [0] GraphicString OPTIONAL,
Content-Disposition [1] GraphicString OPTIONAL,
Content-Length [2] INTEGER OPTIONAL,
Originator [3] InvolvedParty OPTIONAL
}
353.2.102 MessageReference
MessageReference::= OCTET STRING(SIZE(1..10))
3.2.103 MOLR-Type
MOLR-Type::= ENUMERATED
{
40 locationEstimate (0),
assistanceData (1),
deCipheringKeys (2)
}
3.2.104 MSCAddress
45 MSCAddress::= AddressString

3.2.105 MSISDN
MSISDN::= ISDN-AddressString
3.2.106 MTPServiceIdentifier
MTPServiceIdentifier::= ENUMERATED
5 {
managementMessage (1),
maintenanceAndTestMessage (2),
sccpMessage (3),
tupMessage (4),
10 isupMessage (5),
DataUserPartCallAndCircuitRelatedMessages) (6),
DataUserPartFacilityRegistrationAndCancellationMessages) (7),
RANAP (8),
BSSAP (9),
15 ALCAP (12),
BICC (13),
H248 (14)
}
3.2.107 NetworkCallReference
20 NetworkCallReference::= OCTET STRING (SIZE (1..8))
3.2.108 NodeAddress(MGCF)
NodeAddress ::= CHOICE
{
iPAddress [0] IPAddress,
25 domainName [1] GraphicString
}
3.2.109 NoReplyCondTime
NoReplyCondTime::=INTEGER
3.2.110 NotificationToMSUser
30 NotificationToMSUser ::= ENUMERATED
{
notifyLocationAllowed (0),
notifyAndVerify-LocationAllowedIfNoResponse (1),
notifyAndVerify-LocationNotAllowedIfNoResponse (2),
35 ...,
locationNotAllowed (3)
}
3.2.111 NumberOfDPEncountered
NumberOfDPEncountered ::= INTEGER
403.2.112 NumberOfForwarding
NumberOfForwarding::= INTEGER (1..5)
3.2.113 NumOfHSCSDChanAllocated
NumOfHSCSDChanAllocated ::= INTEGER

3.2.114 NumOfHSCSDChanRequested
NumOfHSCSDChanRequested::= INTEGER
3.2.115 OriginalCalledNumber
OriginalCalledNumber ::= BCDDirectoryNumber
53.2.116 PartialRecordType
PartialRecordType::= ENUMERATED
{
serviceChange (1)
}
103.2.117 Pbrt
Pbrt::=INTEGER
Value
Description
Binary Decimal
‘000 0000’B 0 Service of “Coloring Ring Back
Tone “ is not applied in this call
‘000 0001’B 1 Service of “Coloring Ring Back
Tone “ is applied in this call
3.2.118 PlmnId
PlmnId:= OCTET STRING (SIZE(3))
153.2.119 PositioningData
PositioningData::= OCTET STRING (SIZE(1..33))
--
-- See Positioning Data IE (octet 3..n), 3GPP TS 49.031
--
Octet 1 spare Positioning Data Discriminator
Octets 2-2+m Positioning Method 1
Octets ..-2+nm Positioning Method n

20 The positioning data discrminator (bits 4-1 of octet 1) defines the type of data
provided for each positioning method:
VV- indicate usage of each positioning method that was attempted either successfully or unsuccessfully
all other values are reserved
Coding of the postioning method octets for positioning data discrminator = 0:
Octet x positioning method usage
25 Coding of positioning method (bits 8-4):
00000 Timing Advance
00001 Reserved ( Note)
00010 Reserved ( Note)
00011 Mobile Assisted E-OTD
30 00100 Mobile Based E-OTD
00101 Mobile Assisted GPS
00110 Mobile Based GPS
00111 Conventional GPS
01000
35 to reserved for GSM
01111

10000
to reserved for network specific positioning methods
11111
Coding of usage (bits 3-1)
5 000 Attempted unsuccessfully due to failure or interruption
001 Attempted successfully: results not used to generate location
010 Attempted successfully: results used to verify but not generate location
011 Attempted successfully: results used to generate location
100 Attempted successfully: case where MS supports multiple mobile based positioning methods
10 and the actual method or methods used by the MS cannot be determined
NOTE: These values of the codepoints shall not be used as they were used in an
earlier version of the protocol.
3.2.120 RadioChanRequested
RadioChanRequested ::= ENUMERATED
15 {
halfRateChannel (0),
fullRateChannel (1),
dualHalfRatePreferred (2),
dualFullRatePreferred (3)
20 }
3.2.121 RateIndication
RateIndication::= OCTET STRING(SIZE(1))
--0x01=V.110-I.460/X.30RateAdaptation
--0x02=ITU-T-X.31FlagStuffing
25 --0x03=V.120
--0x07=H.223&H.245
--0x0B=PIAFS
--0x0F=Not Used
3.2.122 RecordingEntity
30 RecordingEntity::= AddressString
3.2.123 ReasonForServiceChange
ReasonForServiceChange::= ENUMERATED
{
msubInitiate (0),
35 mscInitiated (1),
callSetupFallBack (2),
callSetupChangeOrder (3)
}
3.2.124 RecordSeqNumber
40 RecordSeqNumber ::= INTEGER
3.2.125 RedirectingNumber
RedirectingNumber ::= BCDDirectoryNumber
3.2.126 RncID
RncId::= SEQUENCE
45 {

plmnId [0] PlmnId,

rncId [1] INTEGER (0..4095)
}
3.2.127 RoamingNumber
5 RoamingNumber ::= ISDN-AddressString
3.2.128 Role-of-Node(MGCF)
Role-of-Node ::= ENUMERATED
{
originating 0),
10 terminating (1),
proxy (2),
b2bua (3)
}
3.2.129 RoutingNumber
15 RoutingNumner ::= CHOICE
{
roaming [1] RoamingNumber,
forwarded [2] ForwardToNumber
}
203.2.130 SDP-Media-Component(MGCF)
SDP-Media-Component ::= SEQUENCE
{
sDP-Media-Name [0] GraphicString OPTIONAL,
sDP-Media-Descriptions [1] SDP-Media-Description OPTIONAL,
25 gPRS-Charging-Id [2] INTEGER OPTIONAL,
authorized-QoS [3] GraphicString OPTIONAL
}
3.2.131 SDP-Media-Description(MGCF)
SDP-Media-Description ::= SEQUENCE OF GraphicString OPTIONAL,
303.2.132 ServiceCategory
ServiceCategory ::= OCTET STRING (SIZE(1))
Values (decimal) Meanings
0 Vacant No.
1 Local network LE/ Ordinary service
2 Local network outgoing/local call service
3 Local network outgoing/rural call (network call) service
4 Domestic toll (intra-area) manual service
5 Domestic toll (intra-area) automatic service
6 Domestic toll (inter-area) manual service
7 Domestic toll (inter-area) automatic service
8 International toll manual service
9 International toll automatic service
10 LE-charging special service
11 Mobile emergent special service

12 Outgoing-charging special service

13 Outgoing free special service
14 Supplementary service
15 CENTREX LE call
16 CENTREX outgoing call
32 MSC ordinary service
33 MSC local service
34 MSC local outgoing service
36 MSC domestic toll call
38 OVERLAY prefix incoming service
39 OVERLAY call service
40 MSC internatjional toll call
41 IP phone service
42 SSP vouching quest service
43 Non-SSP vouching quest service
53 Local free special service
3.2.133 ServiceID
ServiceID ::= INTEGER
3.2.134 ServiceKey
5 ServiceKey ::= OCTET STRING((SIZE1..4))
8 7 6 5 4 3 2 1
Octet 1 (MSB)
Octet 2
Octet 3
Octet 4 (LSB)
3.2.135 Session-Id(MGCF)
Session-Id ::= GraphicString
Note: example for SIP Call-ID: f81d4fae-7dec-11d0-a765-
10 00a0c91e6bf6@foo.bar.com
3.2.136 Sip-Method(MGCF)
Sip-Method ::= GraphicString
3.2.137 SMSResult
SMSResult ::= Diagnostics
153.2.138 SPC14
Spc14 ::= OCTET STRING (SIZE(2))
Spc14 ::= OCTET STRING (SIZE(2))
bit 8 7 6 5 4 3 2 1 8 7 6 5 4 3 2 1
spare main sub spc
octet 2 octet 1

The octet 1 appears first in the coding stream,followed by octet 2. For example,if the
spc14 is “7.4.5” , the codeing stream is 0x25 0x38
3.2.139 SPC24
5 Spc24 ::= OCTET STRING (SIZE(3))
8 7 6 5 4 3 2 1
main octet1
sub octet2
spc octet3
3.2.140 SPCCode
SPCCode ::= CHOICE
{
10 SPCCode14 [0] OCTET STRING(SIZE(3)) OPTIONAL,
SPCCode24 [1]OCTET STRING(SIZE(3) OPTIONAL
}
3.2.141 SpeechVersionIdentifier
SpeechVersionIdentifier::= OCTET STRING (SIZE(1))
15
Value
Meaning
Binary Decimal
‘000 0001’B 1 GSM speech full rate version 1
GSM speech full rate version 2 used for
‘001 0001’B 17
enhanced full rate
‘010 0001’B 33 GSM speech full rate version 3 for future use
‘000 0101’B 5 GSM speech half rate version 1
‘001 0101’B 21 GSM speech half rate version 2 for future use
‘010 0101’B 37 GSM speech half rate version 3 for future use
3.2.142 SSActionResult
SSActionResult ::= Diagnostics
3.2.143 SSActionType
SSActionType::= ENUMERATED
20 {
registration (0),
erasure (1),
activation (2),
deactivation (3),
25 interrogation (4),
invocation (5),
passwordRegistration (6)
}
3.2.144 SS-Code
30 SS-Code ::= OCTET STRING (SIZE (1))

Value
Meaning
Binary Hexdecimal
all line identification SS
‘00010001’B 11 calling line identification presentation
‘00010010’B 12 calling line identification restriction
‘00010011’B 13 connected line identification presentation
‘00010100’B 14 connected line identification restriction
‘00010101’B 15 malicious call identification
‘00011000’B 18 all name identification SS
‘00011001’B 19 calling name presentation
all forwarding SS
‘00100001’B 21 call forwarding unconditional
‘00101000’B 28 all conditional forwarding SS
‘00101001’B 29 call forwarding on mobile subscriber busy
‘00101010’B 2A call forwarding on no reply
‘00101011’B 2B call forwarding on mobile subscriber not reachable
‘00100100’B 2C call deflection
all call offering SS includes also all forwarding SS
‘00110001’B 31 explicit call transfer
‘00110010’B 32 mobile access hunting
all Call completion SS
‘01000001’B 41 call waiting
‘01000010’B 42 call hold
‘01000011’B 43 completion of call to busy subscribers, originating side
‘01000100’B 44 completion of call to busy subscribers, destination side
‘01000101’B 45 multicall
all multiparty SS
‘01010001’B 51 multiparty
all community of interest SS
‘01100001’B 61 closed user group
all charging SS
‘01110001’B 71 advice of charge information
‘01110010’B 72 advice of charge charging
all additional information transfer SS
‘10000001’B 81 UUS1 user-to-user signalling
all barring SS
‘10010001’B 91 barring of outgoing calls
‘10010010’B 92 barring of all outgoing calls
‘10010011’B 93 barring of outgoing international calls
‘10010100’B 94 barring of outgoing international calls except those
directed to the home PLMN
‘10011001’B 99 barring of incoming calls
‘10011010’B 9A barring of all incoming calls
‘10011011’B 9B barring of incoming calls when roaming outside home
PLMN Country
all call priority SS
‘10100001’B A1 enhanced Multilevel Precedence Pre-emption (EMLPP)
service
all LCS Privacy Exception Classes

‘10110001’B B1 allow location by any LCS client

‘10110010’B B2 allow location by any value added LCS client to which a
call is established from the target MS
‘10110011’B B3 allow location by designated external value added LCS
clients
‘10110100’B B4 allow location by designated PLMN operator LCS clients
all Mobile Originating Location Request Classes
‘11000001’B C1 allow an MS to request its own location
‘11000010’B C2 allow an MS to perform self location without interaction
with the PLMN for a predetermined period of time
‘11000011’B C3 allow an MS to request transfer of its location to another
LCS client
3.2.145 SSNCode
SSNCode ::= ENUMERATED
{
SCCPManagement (1),
5 ISDNUserPart (3),
OMAP (4),
MAP (5),
HLRMAP (6),
VLRMAP (7),
10 MSCMAP (8),
EIRMAP (9),
AUC (10),
INAP (12),
RANAP (142),
15 RNSAP (143),
GMLCMAP (145),
CAP (146),
GsmSCFMAP (147),
SIWFMAP (148),
20 SGSNMAP (149),
GGSNMAP (150),
BSCBSSAP-LE (250),
MSCBSSAP-LE (251),
SMLCBSSAP-LE (252),
25 BSSO&M-A-Interface (253),
BSSAP-A-Interface (254),
SCTCAP (238),
IPTCAP (237),
}
303.2.146 SSParameters
SSParameters::= CHOICE
{
forwardedToNumber [0] ForwardToNumber,
unstructuredData [1] OCTET STRING
35 }
3.2.147 SubscriberCategory
SubscriberCategory ::= Category
3.2.148 SuppServiceUsed
SuppServiceUsed::= SEQUENCE
40 {

ssCode [0] SS-Code,

ssAction [1] SSActionType,
ssTime [2] TimeStamp OPTIONAL
}
53.2.149 SystemType
SystemType ::= ENUMERATED
{
unknown (0),
iuUTRAN (1)
10 gERAN (2)
}
3.2.150 TBCD-STRING
TBCD-STRING ::= OCTET STRING
-- This type (Telephony Binary Coded Decimal String) is used to
15 -- 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.
20 -- bits 8765 of octet n encoding digit 2n

-- bits 4321 of octet n encoding digit 2(n-1) +1
3.2.151 TeleserviceCode
TeleserviceCode ::= OCTET STRING (SIZE (1))
Value
Meaning
Binary Hexdecimal
‘00000000’B 00 All Teleservices
‘00010000’B 10 All Speech Transmission Services
‘00010001’B 11 telephony
‘00010010’B 12 emergencyCalls
‘00100000’B 20 All Short Message Services
‘00100001’B 21 Short Message MT-PP
‘00100010’B 22 Short Message MO-PP
‘01100000’B 60 All Facsimile Transmission Services
‘01100001’B 61 Facsimile Group3 And Alter Speech
‘01100010’B 62 Automatic Facsimile Group 3
‘01100011’B 63 Facsimile Group4
‘01110000’B 70 All DataTeleservices
‘10000000’B 80 All Teleservices-ExeptSMS
‘10010000’B 90 All oice Group Call Services
‘10010001’B 91 Voice Group Call
‘10010010’B 92 Voice Broadcast Call
‘11010000’B D0 All PLMN-specificTS
‘11010001’B D1 plmn-specific TS-1


‘11011010’B DA plmn-specific TS-A
‘11011011’B DB plmn-specific TS-B
‘11011100’B DC plmn-specific TS-C
‘11011101’B DD plmn-specific TS-D
‘11011110’B DE plmn-specific TS-E
‘11011111’B DF plmn-specific TS-F
3.2.152 TerminatingRecordType
TerminatingRecordType ::= ENUMERATED
{
ordinaryTerminating (0),
5 forwardOnUnconditionalTerminating (1),
forwardOnBusyTerminating (2),
forwardOnNotReplyTerminating (3),
forwardOnMsNotReachableTerminating (4),
}
103.2.153 TimeStaTimeStamp
TimeStamp ::= OCTET STRING (SIZE(9))
8 7 6 5 4 3 2 1
Octet 1 YY
Octet 2 MM
Octet 3 DD
Octet 4 hh
Octet 5 mm
Octet 6 ss
Octet 7 S
Octet 8 hh
Octet 9 mm
Local time of UTC compression format
--YY = Year 00 to 99 BCD encoded
--MM = Month 01 to 12 BCD encoded
15 --DD = Day 01 to 31 BCD encoded
-- hh = hour 00 to 23 BCD encoded
-- mm = minute 00 to 59 BCD encoded
-- ss = second 00 to 59 BCD encoded
-- S = Sign 0 = “+”, “-“ ASCII encoded
20 -- hh = hour 00 to 23 BCD encoded
-- mm = minute 00 to 59 BCD encoded
3.2.154 TKGPName
TKGPName ::= IA5String (SIZE(1..32))
3.2.155 TrafficChannel
25 TrafficChannel::= ENUMERATED
{

fullRate (0),
halfRate (1)
}
3.2.156 TranslatedNumber
5 TranslatedNumber::= BCDDirectoryNumber
3.2.157 TransmissionMedium(MGCF)
TransmissionMedium ::= SEQUENCE
{
-- Transmission Medium Required, refer to ITU-T Q.763:
10 tMR[0] OCTET STRING (SIZE (1)) OPTIONAL,
WW- Transmission Medium USED, refer to ITU-T Q.763:
tMU[1] OCTET STRING (SIZE (1)) OPTIONAL
}
3.2.158 TransparencyInd
15 TransparencyInd::= ENUMERATED
{
transparent (0),
126ontransparent (1)
}
203.2.159 TrunkGroup
TrunkGroup ::= OCTET STRING(SIZE(4))
8 7 6 5 4 3 2 1
Octet 1 (MSB) Mudule (LSB)
Octet 2 (MSB) Mudule (LSB)
Octet 3 (MSB) Group (LSB)
Octet 4 (MSB) Group (LSB)
3.2.160 TrunkGroupID(MGCF)
TrunkGroupID ::= CHOICE
{
25 incoming [0] GraphicString,
outgoing [1] GraphicString
}
3.2.161 TypeOfServiceChange
TypeOfServiceChange::=ENUMERATED
30 {
changeToSpeech (0),
changeToMultimedia (1)
}
3.2.162 USSDDataCodingSchema
35 USSDDataCodingSchema ::= OCTET STRING(SIZE(1))

Coding Group
Bits Use of bits 3..0
7..4
0000 Language using the GSM 7 bit default alphabet
Bits 3..0 indicate the language:

0000 German
0001 English
0010 Italian
0011 French
0100 Spanish
0101 Dutch
0110 Swedish
0111 Danish
1000 Portuguese
1001 Finnish
1010 Norwegian
1011 Greek
1100 Turkish
1101 Hungarian
1110 Polish
1111 Language unspecified
0001 0000 GSM 7 bit default alphabet; message preceded by language
indication.
The first 3 characters of the message are a two-character

representation of the language encoded according to ISO 639 [12], followed
by a CR character. The CR character is then followed by 90 characters of
text.
XX- UCS2; message preceded by language indication
The message starts with a two GSM 7-bit default alphabet

character representation of the language encoded according to ISO 639 [12].
This is padded to the octet boundary with two bits set to 0 and then
followed by 40 characters of UCS2-encoded message.
An MS not supporting UCS2 coding will present the two character
language identifier followed by improperly interpreted user data.
0010..1111 Reserved
0010.. 0000 Czech
0001 Hebrew
0010 Arabic
0011 Russian
0100 Icelandic
0101..1111 Reserved for other languages using the GSM 7 bit default
alphabet, with unspecified handling at the MS
0011 0000..1111 Reserved for other languages using the GSM 7 bit default
alphabet, with unspecified handling at the MS
01xx General Data Coding indication
Bits 5..0 indicate the following:
Bit 5, if set to 0, indicates the text is uncompressed

Bit 5, if set to 1, indicates the text is compressed using the compression
algorithm defined in 3GPP TS 23.042 [13]
Bit 4, if set to 0, indicates that bits 1 to 0 are reserved and have no message

Coding Group
Bits Use of bits 3..0
7..4
class meaning
Bit 4, if set to 1, indicates that bits 1 to 0 have a message class meaning:
Bit 1 Bit 0 Message Class:

0 0 Class 0
0 1 Class 1 Default meaning: ME-
specific.
1 0 Class 2 (U)SIM specific
message.
1 1 Class 3 Default meaning: TE-
specific (see 3GPP TS 27.005 [8])
Bits 3 and 2 indicate the character set being used, as follows:

Bit 3 Bit 2 Character set:
0 0 GSM 7 bit default alphabet
0 1 8 bit data
1 0 UCS2 (16 bit) [10]
1 1 Reserved
1000 Reserved coding groups
1001 Message with User Data Header (UDH) structure:

0 0 Class 0
0 1 Class 1 Default meaning: ME-
specific.
1 0 Class 2 (U)SIM specific
message.
1 1 Class 3 Default meaning: TE-
specific (see 3GPP TS 27.005 [8])
Bits 3 and 2 indicate the alphabet being used, as follows:

Bit 3 Bit 2 Alphabet:
0 0 GSM 7 bit default alphabet
0 1 8 bit data
1 0 USC2 (16 bit) [10]
1 1 Reserved
1010..1101 Reserved coding groups
1110 Defined by the WAP Forum [15]
1111 Data coding / message handling
Bit 3 is reserved, set to 0.
Bit 2 Message coding:

0 GSM 7 bit default alphabet
1 8 bit data

0 0 No message class.
0 1 Class 1 user defined.
1 0 Class 2 user defined.
1 1 Class 3
default meaning: TE specific
(see 3GPP TS 27.005 [8])
3.2.163 USSDOperationCode
USSDOperationCode ::= ENUMERATED

{
processUnstructuredSS-Data (19),
processUnstructuredSS-Request (59),
unstructuredSS-Request (60),
5 unstructuredSS-Notify (61)
}
3.2.164 USSDServiceCode
USSDServiceCode ::= INTEGER
3.2.165 VIGCallType
10 VIGCallType ::= ENUMERATED
{
incoming (0),
outgoing (1)
}
153.3 TAG Value Definition

3.3.1 CallEventRecord
Table 25 CallEventRecord Tag Values
Tag Value Description
H’ A0 MOCallRecord
H’A1 MTCallRecord
H’A2 ROAMRecord
H’A3 IncGatewayRecord
H’A4 OutGatewayRecord
H’A5 TransitRecord
H’A6 MOSMSRecord
H’A7 MTSMSRecord
H’A8 MOSMSIWRecord
H’A9 MTSMSGWRecord
H’AA SSActionRecord
H’AB HLRIntRecord
H’AC MOECallRecord
H’AD MCFCallRecord
H’AE CommonEquipRecord
H’B0 TermCAMELIntRecord
H’B1 MTLCSRecord
H’B2 MOLCSRecord
H’B3 NILCSRecord
H’BF43 MGCFRecord
H’BF64 sigMTPStatisticRecord
H’BF65 sigSCCPStatisticRecord
H’BF66 USSDRecord
H’BF67 VIGRecord
3.3.2 MOCallRecord
Table 26 MOCallRecord Tag Values

TAG Value Description

H’80 recordType
H’81 servedIMSI
H’82 servedIMEI
H’83 servedMSISDN
H’84 calledNumber
H’85 translatedNumber
H’86 connectedNumber
H’87 roamingNumber
H’88 recordingEntity
H’89 mscIncomingTKGP
H’8A mscOutgoingTKGP
H’AB location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’AC changeOfLocation
H’30 SEQUENCE OF
H’A0 locationAreaAndCell
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’81 changeTime
H’AD basicService
H’83 bearerService
H’82 teleService
H’8E transparencyIndicator
H’AF changeOfService
H’30 SEQUENCE OF
H’A0 basicService
H’82 teleService
H’81 transparencyIndicator
H’82 changeTime
H’B0 supplServicesUsed
H’30 SEQUENCE OF
H’80 SS-Code
H’81 SSActionType
H’82 ssTime
H’B1 aocParameters
H’81 e1
H’82 e2
H’83 e3
H’84 e4
H’85 e5
H’86 e6
H’87 e7
H’B2 changeOfAOCParms
H’30 SEQUENCE OF
H’80 changeTime
H’A1 newParameters
H’81 e1
H’82 e2
H’83 e3
H’84 e4
H’85 e5
H’86 e6
H’87 e7
H’93 msClassmark

H’B4 changeOfClassmark
H’30 SEQUENCE OF
H’80 classmark
H’81 changeTime
H’95 seizureTime
H’96 answerTime
H’97 releaseTime
H’98 callDuration
H’99 dataVolume
H’9A radioChanRequested
H’9B radioChanUsed
H’BC changeOfRadioChan
H’80 radioChannel
H’81 changeTime
H’82 speechVersionUsed
H’9D causeForTerm
H’BE diagnostics
H’80 gsm0408Cause
H’81 gsm0902MapErrorValue
H’82 ccittQ767Cause
H’83 networkSpecificCause
H’84 manufacturerSpecificCause
H’9F1F callReference
H’9F20 sequenceNumber
H’9F21 lastLongPartInd
H’BF22 additionalChgInfo
H’80 chargeIndicator
H’81 chargedParty
H’9F23 recordExtensions
H’9F24 isCAMELCall
H’9F25 Gsm-SCFAddress
H’9F26 serviceKey
H’9F27 networkCallReference
H’9F28 mSCAddress
H’9F29 defaultCallHandling
H’9F2A isHSCSDUsed
H’9F2B hSCSDChanRequested
H’9F2C hSCSDChanAllocated
H’BF2D changeOfHSCSDParms
H’30 SEQUENCE OF
H’80 changeTime
H’81 hSCSDChanAllocated
H’82 initiatingParty
H’83 aiurRequested
H’84 chanCodingUsed
H’85 hSCSDChanRequested
H’9F2E fnur
H’9F2F aiurRequested
H’BF30 chanCodingsAcceptable
H’0A Enumerated
H’9F31 chanCodingUsed
H’9F32 speechVersionSupported
H’9F33 speechVersionUsed
H’9F34 numberOfDPEncountered
H’9F35 levelOfCAMELService

H’9F36 freeFormatData
H’BF37 cAMELCallLegInformation
H’30 SEQUENCE OF
H’81 cAMELDestinationNumber
H’84 mscOutgoingTKGP
H’85 seizureTime
H’86 answerTime
H’87 releaseTime
H’88 callDuration
H’89 dataVolume
H’8A cAMELInitCFIndicator
H’8B causeForTerm
H’AC cAMELModification
H’80 changeFlags
H’A1 changeList
H’80 callingPartyNumber
H’81 callingPartyCategory
H’82 origCalledPartyNumber
H’83 genericNumbers
H’84 redirectingPartyNumber
H’85 redirectionCounter
H’8D freeFormatData
H’AE diagnostics
H’80 gsm0408Cause
H’8F freeFormatDataAppend
H’90 freeFormatData_2
H’91 freeFormatDataAppend_2
H’9F38 freeFormatDataAppend
H’9F39 defaultCallHandling_2
H’9F3A gsmSCFAddress_2
H’9F3B serviceKey_2
H’9F3C freeFormatData_2
H’9F3D freeFormatDataAppend_2
H’9F3E systemType
H’9F3F exchangeIdentity
H’9F40 dialledNumber
H’9F41 subscriberCategory
H’9F42 recordSequenceNumber
H’9F43 eMLPPriorityLevel
H’9F44 eMLPRequestPriorityLevel
H’9F45 hotBillingTag
H’9F46 isCUGUsed
H’BF47 cUGCategory
H80 callType
H81 userType
H’9F48 cUGInterLockCode
H’9F49 dataRate
H’9F4A isMultiMediaCall
H’9F4B rateIndication
H’9F4C guaranteedBitRate
H’9F4D maximumBitRate
H’9F4E Pbrt

H’9F4F Carp
H’9F50 cUGIndex
H’9F51 cUGOutgoingAccessUsed
H’9F52 cUGOutgoingAccessInd
H’9F53 hotBillingTag2
H’9F58 dDCFlag
H’9F59 BSCIdentification
H’BF5A calledLocation
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’9F5B callingPartyRoamingInd
H’9F5C serviceCategory
H’9F5D transactionIdentification
H’9F5E incomingCic
H’9F5F outgoingCic
H’9F60 mscSPC14
H’9F61 mscSPC24
H’9F62 incomingTKGPName
H’9F63 outgoingTKGPName
H’9F64 partialRecordType
H’9F65 serviceChangeInitiator
H’9F66 reasonForServiceChange
H’9F67 typeOfServiceChange
3.3.3 MTCallRecord
Table 27 MTCallRecord Tag Values
H’80 RecordType
H’81 ServedIMSI
H’82 ServedIMEI
H’83 ServedMSISDN
H’84 CallingNumber
H’85 RecordingEntity
H’A8 location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’A9 changeOfLocation
H’30 SEQUENCE OF
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’81 changeTime
H’AA basicService
H’82 teleService
H’8B transparencyIndicator
H’AC changeOfService
H’30 SEQUENCE OF
H’A0 basicService
H’82 teleService
H’82 changeTime

H’AD supplServicesUsed
H’30 SEQUENCE OF
H’80 SS-Code
H’81 SSActionType
H’82 SsTime
H’AE AocParameters
H’81 e1
H’82 e2
H’83 e3
H’84 e4
H’85 e5
H’86 e6
H’87 e7
H’AF changeOfAOCParms
H’30 SEQUENCE OF
H’80 changeTime
H’81 e1
H’82 e2
H’83 e3
H’84 e4
H’85 e5
H’86 e6
H’87 e7
H’90 msClassmark
H’B1 changeOfClassmark
H’30 SEQUENCE OF
H’80 classmark
H’81 changeTime
H’92 seizureTime
H’93 answerTime
H’94 releaseTime
H’95 callDuration
H’96 dataVolume
H’97 radioChanRequested
H’98 radioChanUsed
H’B9 changeOfRadioChan
H’80 radioChannel
H’81 changeTime
H’9A causeForTerm
H’BB diagnostics
H’80 gsm0408Cause
H’9C callReference
H’9D sequenceNumber
H’9E lastLongPartInd
H’BF1F additionalChgInfo
H’81 chargedParty
H’9F20 recordExtensions
H’9F21 isCAMELCall
H’9F23 mSCAddress
H’9F24 isHSCSDUsed
H’9F25 hSCSDChanRequested
H’9F26 hSCSDChanAllocated

H’BF27 changeOfHSCSDParms
H’30 SEQUENCE OF
H’80 changeTime
H’81 hSCSDChanAllocated
H’82 initiatingParty
H’83 aiurRequested
H’84 chanCodingUsed
H’85 hSCSDChanRequested
H’9F28 Fnur
H’9F29 aiurRequested
H’BF2A chanCodingsAcceptable
H’0A Enumerated
H’9F2B chanCodingUsed
H’9F2C speechVersionSupported
H’9F2D speechVersionUsed
H’9F2E Gsm-SCFAddress
H’9F2F serviceKey
H’9F33 systemType
H’9F34 exchangeIdentity
H’9F35 redirectNumber
H’9F36 subscriberCategory
H’9F38 connectedNumber
H’9F3A isCUGUsed
H’BF3B cUGCategory
H80 callType
H81 userType
H’9F3C cUGInterLockCode
H’9F3D dataRate
H’9F3E isMultiMediaCall
H’9F3F rateIndication
H’9F40 guaranteedBitRate
H’9F41 maximumBitRate
H’9F42 pbrt
H’9F43 carp
H’9F44 cUGIndex
H’9F45 cUGIncomingAccessUsed
H’9F46 cUGIncomingAccessInd
H’9F47 redirectingNumber
H’9F4D dDCFlag
H’9F4E terminatingRecordType
H’9F4F originalCalledNumber
H’BF50 callingLocation
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’9F51 bSCIdentification
H’9F52 calledPartyRoamingInd
H’9F53 serviceCategory
H’9F54 transactionIdentification

H’9F55 incomingCic
H’9F56 outgoingCic
H’9F57 mscSPC14
H’9F58 mscSPC24
H’9F5A outgoingTKGPName
H’9F5B partialRecordType
H’9F5C serviceChangeInitiator
H’9F5D reasonForServiceChange
H’9F5E typeOfServiceChange
3.3.4 ROAMRecord
Table 28 ROAMRecord Tag Values
H’80 recordType
H’81 servedIMSI
H’82 servedMSISDN
H’83 callingNumber
H’A8 basicService
H’82 teleService
H’AA changeOfService
H’30 SEQUENCE OF
H’A0 basicService
H’82 teleService
H’82 changeTime
H’AB supplServicesUsed
H’30 SEQUENCE OF
H’80 SS-Code
H’81 SSActionType
H’82 ssTime
H’8C seizureTime
H’8D answerTime
H’8E releaseTime
H’8F callDuration
H’90 dataVolume
H’91 causeForTerm
H’B2 diagnostics
H’80 gsm0408Cause
H’93 callReference
H’94 sequenceNumber
H’95 lastLongPartInd
H’96 recordExtensions
H’97 isCAMELCall
H’98 networkCallReference
H’99 mSCAddress
H’9A exchangeIdentity
H’9B recordSequenceNumber
H’9C isCUGUsed

H’BD cUGCategory
H80 callType
H81 userType
H’9E cUGInterLockCode
H’9F1F dataRate
H’9F20 isMultiMediaCall
H’9F22 redirectNumber
H’9F27 mscSPC14
H’9F28 mscSPC24
H’9F2B transRoamingNumber
3.3.5 IncGatewayRecord
Table 29 IncGatewayRecord Tag Values
H’80 recordType
H’82 calledNumber
H’86 seizureTime
H’87 answerTime
H’88 releaseTime
H’89 callDuration
H’8A dataVolume
H’8B causeForTerm
H’AC diagnostics
H’80 gsm0408Cause
H’8D callReference
H’8E sequenceNumber
H’8F lastLongPartInd
H’91 exchangeIdentity
H’B2 additionalChgInfo
H’81 chargedParty
H’93 recordSequenceNumber
H’94 pbrt
H’99 dDCFlag
H’9A gatewayRecordType
H’9B roamingNumber
H’9C redirectNumber
H’9D incomingCic
H’9E outgoingCic
H’9F1F mscSPC14
H’9F20 mscSPC24

H’9F23 forwardCallIndicator
H’BF28 isdnBasicService
H’82 teleService
3.3.6 OutGatewayRecord
Table 30 OutGatewayRecord Tag Values
H’80 recordType
H’82 calledNumber
H’86 seizureTime
H’87 answerTime
H’88 releaseTime
H’89 callDuration
H’8A dataVolume
H’8B causeForTerm
H’AC diagnostics
H’80 gsm0408Cause
H’8E sequenceNumber
H’8F lastLongPartInd
H’81 chargedParty
H’94 pbrt
H’99 dDCFlag
H’9A gatewayRecordType
H’9D incomingCic
H’9E outgoingCic
H’9F1F mscSPC14
H’9F20 mscSPC24
H’BF28 isdnBasicService
H’82 teleService

3.3.7 TransitRecord
Table 31 TransitRecord Tag Values
H’80 recordType
H’82 calledNumber
H’A3 isdnBasicService
H’82 teleService
H’87 seizureTime
H’88 answerTime
H’89 releaseTime
H’8A callDuration
H’8B dataVolume
H’8C causeForTerm
H’AD diagnostics
H’80 gsm0408Cause
H’8E callReference
H’8F sequenceNumber
H’81 chargedParty
H’95 pbrt
H’9A dDCFlag
H’9D incomingCic
H’9E outgoingCic
H’9F1F mscSPC14
H’9F20 mscSPC24
3.3.8 MOSMSRecord
Table 32 MOSMSRecord Tag Values
H’80 recordType
H’81 servedIMSI
H’82 servedIMEI
H’83 servedMSISDN
H’84 msClassmark
H’85 serviceCentre
H’A7 location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’88 messageReference

H’89 originationTime
H’AA smsResult
H’80 gsm0408Cause
H’8B recordExtensions
H’8C destinationNumber
H’AD cAMELSMSInformation
H’81 sCFAddress
H’82 serviceKey
H’83 defaultSMSHandling
H’84 freeFormatData
H’85 cAMELCallingPartyNumber
H’86 cAMELDestSubscriberNumber
H’87 cAMELSMSCAddress
H’88 smsRefrenceNumber
H’8E systemType
H’8F exchangeIdentity
H’91 hotBillingTag
H’92 hotBillingTag2
H’93 transactionIdentification
H’94 mscSPC14
H’95 mscSPC24
3.3.9 MTSMSRecord
Table 33 MTSMSRecord Tag Values
H’80 recordType
H’82 servedIMSI
H’83 servedIMEI
H’84 servedMSISDN
H’85 msClassmark
H’A7 location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’88 deliveryTime
H’A9 smsResult
H’80 gsm0408Cause
H’8A recordExtensions
H’8B systemType
H’8C exchangeIdentity
H’8D recordSequenceNumber
H’8E originationNumber
H’8F hotBillingTag
H’92 mscSPC14
H’93 mscSPC24

H’B4 cAMELSMSInformation
H’81 sCFAddress
H’82 serviceKey
H’83 defaultSMSHandling
H’84 freeFormatData
H’85 cAMELCallingPartyNumber
H’86 cAMELDestSubscriberNumber
H’87 cAMELSMSCAddress
H’88 smsRefrenceNumber
3.3.10 MOSMSIWRecord
Table 34 MOSMSIWRecord Tag Values
H’80 recordType
H’82 servedIMSI
H’83 servedMSISDN
H’85 eventTime
H’A6 smsResult
H’80 gsm0408Cause
H’89 systemType
H’8A recordSequenceNumber
3.3.11 MTSMSGWRecord
Table 35 MTSMSGWRecord Tag Values
H’80 recordType
H’82 servedIMSI
H’83 servedMSISDN
H’85 eventTime
H’A6 smsResult
H’80 gsm0408Cause
H’89 systemType
H’8A recordSequenceNumber
53.3.12 SSActionRecord
Table 36 SSActionRecord Tag Values
H’80 recordType
H’81 servedIMSI
H’82 servedIMEI
H’83 servedMSISDN
H’84 msClassmark

H’A6 location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’A7 basicService
H’31 SET OF
H’82 teleService
H’88 supplService
H’89 ssAction
H’8A ssActionTime
H’AB ssParameters
H’80 forwardedToNumber
H’81 unstructuredData
H’AC ssActionResult
H’80 gsm0408Cause
H’8E recordExtensions
H’8F systemType
H’92 forwardedSubNumber
H’93 noReplyCondTime
H’96 mscSPC14
H’97 mscSPC24
3.3.13 MOECallRecord
Table 37 MOECallRecord Tag Values
H’80 recordType
H’81 servedIMSI
H’82 servedIMEI
H’83 servedMSISDN
H’A8 location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’A9 changeOfLocation
H’30 SEQUENCE OF
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’81 changeTime
H’AA basicService
H’82 teleService
H’AB aocParameters
H’81 e1
H’82 e2

H’83 e3
H’84 e4
H’85 e5
H’86 e6
H’87 e7
H’AC changeOfAOCParms
H’30 SEQUENCE OF
H’80 changeTime
H’81 e1
H’82 e2
H’83 e3
H’84 e4
H’85 e5
H’86 e6
H’87 e7
H’8D msClassmark
H’AE changeOfClassmark
H’30 SEQUENCE OF
H’80 classmark
H’81 changeTime
H’8F seizureTime
H’90 answerTime
H’91 releaseTime
H’92 callDuration
H’93 radioChanRequested
H’94 radioChanUsed
H’B5 changeOfRadioChan
H’80 radioChannel
H’81 changeTime
H’96 causeForTerm
H’B7 diagnostics
H’80 gsm0408Cause
H’9A callReference
H’9C systemType
H’9D exchangeIdentity
H’9E subscriberCategory
H’9F1F calledNumber
H’9F21 roamingNumber
H’9F22 eMLPPriorityLevel
H’9F23 eMLPRequestPriorityLevel
H’9F25 carp
H’9F28 transactionIdentification
H’9F2A outgoingCic
H’9F2B mscSPC14
H’9F2C mscSPC24
H’9F2D incomingTKGPName
H’9F2E outgoingTKGPName

3.3.14 MCFCallRecord
Table 38 MCFCallRecord Tag Values
H’80 recordType
H’81 mcfType
H’82 servedIMSI
H’83 servedIMEI
H’84 servedMSISDN
H’86 calledNumber
H’8A recordingEntity
H’8B mscIncomingTKGP
H’8C mscOutgoingTKGP
H’AD basicService
H’82 teleService
H’8E transparencyIndicator
H’AF changeOfService
H’30 SEQUENCE OF
H’A0 basicService
H’82 teleService
H’82 changeTime
H’B0 supplServicesUsed
H’30 SEQUENCE OF
H’80 SS-Code
H’81 SSActionType
H’82 ssTime
H’91 seizureTime
H’92 answerTime
H’93 releaseTime
H’94 callDuration
H’95 causeForTerm
H’B6 diagnostics
H’80 gsm0408Cause
H’97 dataVolume
H’9A callReference
H’BB additionalChgInfo
H’81 chargedParty
H’9C recordExtensions
H’9D isCAMELCall
H’9E gsm-SCFAddress
H’9F1F serviceKey
H’9F21 mSCAddress
H’9F22 cAMELInitCFIndicator
H’9F24 numberOfDPEncountered
H’9F25 levelOfCAMELService
H’BF27 cAMELCallLegInformation

H’30 SEQUENCE OF
H’85 seizureTime
H’86 answerTime
H’87 releaseTime
H’88 callDuration
H’89 dataVolume
H’8B causeForTerm
H’80 changeFlags
H’A1 changeList
H’AE diagnostics
H’80 gsm0408Cause
H’9F29 defaultCallHandling_2
H’9F2A gsm-SCFAddress_2
H’9F2B serviceKey_2
H’9F2C freeFormatData_2
H’9F2D freeFormatDataAppend_2
H’9F2E subscriberCategory
H’9F2F systemType
H’9F30 exchangeIdentity
H’9F32 numberOfForwarding
H’9F34 isCUGUsed
H’BF35 cUGCategory
H80 callType
H81 userType
H’9F36 cUGInterLockCode
H’9F37 dataRate
H’9F38 isMultiMediaCall
H’9F39 rateIndication
H’9F3A fnur
H’9F3B pbrt
H’9F3C carp
H’9F3D cUGIndex
H’9F3E cUGOutgoingAccessUsed
H’9F3F cUGOutgoingAccessInd
H’BF42 calledLocation
H’80 locationArea
H’A1 rncID
H’80 plmnID

H’81 rncID
H’9F43 callingPartyRoamingInd
H’9F47 mscSPC14
H’9F48 mscSPC24
H’9F4B partialRecordType
H’9F4C serviceChangeInitiator
H’9F4D reasonForServiceChange
H’9F4E typeOfServiceChange
3.3.15 CommonEquipRecord
Table 39 CommonEquipRecord Tag Values
H’80 recordType
H’81 equipmentType
H’82 equipmentId
H’83 servedIMSI
H’84 servedMSISDN
H’A6 basicService
H’82 teleService
H’A7 changeOfService
H’30 SEQUENCE OF
H’A0 basicService
H’82 teleService
H’82 changeTime
H’A8 supplServicesUsed
H’30 SEQUENCE OF
H’80 SS-Code
H’81 SSActionType
H’82 ssTime
H’89 seizureTime
H’8A releaseTime
H’8B callDuration
H’8C callReference
H’8D sequenceNumber
H’8E lastLongPartInd
H’8F recordExtensions
H’92 systemType
H’93 rateIndication
H’94 fnur
3.3.16 TermCAMELIntRecord
Table 40 TermCAMELIntRecord Tag Values
H’80 recordType
H’81 servedIMSI
H’82 servedMSISDN

H’84 interrogationTime
H’85 destinationRoutingAddress
H’86 gsm-SCFAddress
H’87 serviceKey
H’88 networkCallReference
H’89 mSCAddress
H’8A defaultCallHandling
H’8C calledNumber
H’8D callingNumber
H’8E mscIncomingTKGP
H’8F mscOutgoingTKGP
H’90 seizureTime
H’91 answerTime
H’92 releaseTime
H’93 callDuration
H’94 dataVolume
H’95 causeForTerm
H’B6 diagnostics
H’80 gsm0408Cause
H’9A numberOfDPEncountered
H’9B levelOfCAMELService
H’9C freeFormatData
H’BD cAMELCallLegInformation
H’30 SEQUENCE OF
H’85 seizureTime
H’86 answerTime
H’87 releaseTime
H’88 callDuration
H’89 dataVolume
H’8B causeForTerm
H’80 changeFlags
H’A1 changeList
H’AE diagnostics
H’80 gsm0408Cause
H’9E freeFormatDataAppend
H’9F1F exchangeIdentity

H’9F21 mscServerIndication
H’9F22 gsm-SCFAddress-2
H’9F23 serviceKey-2
H’9F24 defaultCallHandling-2
H’9F25 freeFormatData-2
H’9F26 freeFormatDataAppend-2
H’9F2B hotBillingTag2
H’9F2C incomingCic
H’9F2D outgoingCic
H’9F2E mscSPC14
H’9F2F mscSPC24
3.3.17 HLRIntRecord
Table 41 HLRIntRecord Tag Values
H’80 recordType
H’81 servedIMSI
H’82 servedMSISDN
H’A4 basicService
H’82 teleService
H’A5 routingNumber
H’81 roaming
H’82 Forwarded
H’86 interrogationTime
H’87 numberOfForwarding
H’A8 interrogationResult
H’80 gsm0408Cause
H’8A exchangeIdentity
H’8B recordSequenceNumber
H’8C hotBillingTag2
3.3.18 LCSMTRecord
Table 42 LCSMTRecord Tag Values
H’80 recordType
H’82 lcsClientType
H’A3 lcsClientIdentity
H’A0 lcsClientExternalID
H’80 externalAddress
H’81 lcsClientDialedByMS
H’82 lcsClientInternalID
H’84 servedIMSI
H’85 servedMSISDN
H’A6 locationType
H’80 locationEstimateType
H’81 deferredLocationEventType
H’87 lcsQos
H’88 lcsPriority
H’89 mlc-Number
H’8A eventTimeStamp

H’8B measureDuration
H’8C notificationToMSUser
H’8D privacyOverride
H’AE location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’8F locationEstimate
H’90 positioningData
H’91 lcsCause
H’B2 diagnostics
H’80 gsm0408Cause
H’93 systemType
H’97 causeForTerm
3.3.19 LCSMORecord
Table 43 LCSMORecord Tag Values
H’80 recordType
H’84 servedIMSI
H’85 servedMSISDN
H’86 molr-Type
H’87 lcsQos
H’88 lcsPriority
H’89 mlc-Number
H’8A eventTimeStamp
H’8B measureDuration
H’AC location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’8D locationEstimate
H’8E positioningData
H’8F lcsCause
H’B0 diagnostics
H’80 gsm0408Cause
H’91 systemType

H’95 causeForTerm
3.3.20 LCSNIRecord
Table 44 LCSNIRecord Tag Values
H’80 recordType
H’84 servedIMSI
H’85 servedMSISDN
H’86 servedIMEI
H’87 emsDigits
H’88 emsKey
H’89 lcsQos
H’8A lcsPriority
H’8B mlc-Number
H’8C eventTimeStamp
H’8D measureDuration
H’AE location
H’80 locationArea
H’A1 rncID
H’80 plmnID
H’81 rncID
H’8F locationEstimate
H’90 positioningData
H’91 lcsCause
H’B2 diagnostics
H’80 gsm0408Cause
H’93 systemType
H’97 causeForTerm
3.3.21 USSDRecord
Table 45 USSDRecord Tag Values
H’80 RecordType
H’81 ServedIMSI
H’82 ServedIMEI
H’83 ServedMSISDN
H’84 MsClassmark
H’86 StartTime
H’87 EndTime
H’A8 location
H’80 locationArea

H’A1 rncID
H’80 plmnID
H’81 rncID
H’89 CallReference
H’8A uSSDInteractionCount
H’8B uSSDUnstructuredData
H’8C uSSDOpreationCode
H’8D uSSDDataCodingSchema
H’8E uSSDServiceCode
H’AF errorCode
H’80 gsm0408Cause
H’90 systemType
3.3.22 VIGRecord
Table 46 VIGRecord Tag Values
H’80 RecordType
H’82 calledNumber
H’83 vigCallType
H’84 startTime
H’85 endTime
H’86 callDuration
H’87 causeForTerm
H’A8 diagnostics
H’80 gsm0408Cause
H’8A sequenceNumber
H’8B lastLongPartInd
H’8C callDataRate
H’8D exchangeIdentity
H’8E recordSequenceNumber
3.3.23 MGCFRecord
Table 47 MGCFRecord Tag Values
H’80 RecordType
H’81 Retransmission
H’82 sIP-Method
H’83 role-of-Node
H’A4 nodeAddress
H’A0 iPAddress
H’80 iPBinV4Address
H’82 iPTextV4Address
H’82 domainName
H’85 session-Id

H’A6 calling-Party-Address
H’80 sIP-URI
H’81 tEL-URI
H’A7 called-Party-Address
H’80 sIP-URI
H’81 tEL-URI
H’88 privateUserID
H’89 serviceRequestTimeStamp
H’8A serviceDeliveryStartTimeStamp
H’8B serviceDeliveryEndTimeStamp
H’8C recordOpeningTime
H’8D recordClosureTime
H’AE interOperatorIdentifiers
H’30 SEQUENCE OF
H’80 originatingIOI
H’81 terminatingIOI
H’8F localRecordSequenceNumber
H’91 causeForRecordClosing
H’B2 incomplete-CDR-Indication
H’80 aCRStartLost
H’81 aCRInterimLost
H’82 aCRStopLost
H’93 iMS-Charging-Identifier
H’B4 list-Of-SDP-Media-Components
H’30 SEQUENCE OF
H’80 sIP-Request-Timestamp
H’81 sIP-Response-Timestamp
H’A2 sDP-Media-Components
H’30 SEQUENCE OF
H’80 sDP-Media-Name
H’A1 sDP-Media-Descriptions
H’30 SEQUENCE OF
H’81 SDP-Media-Description
H’82 gPRS-Charging-Id
H’83 authorized-QoS
H’83 mediaInitiatorFlag
H’A4 sDP-Session-Description
H’30 SEQUENCE OF
H’81 GraphicString
H’B5 gGSNaddress
H’A0 iPAddress
H’82 domainName
H’96 serviceReasonReturnCode
H’B7 list-Of-Message-Bodies
H’30 SEQUENCE OF
H’80 Content-Type
H’81 Content-Disposition
H’82 Content-Length
H’A3 Originator
H’80 sIP-URI
H’81 tEL-URI
H’BF50 trunkGroupID
H’80 incoming
H’81 Outgoing
H’BF82 bearerService
H’80 tMR
H’81 tMU

3.3.24 SigMTPStatisticRecord
Table 48 SigMTPStatisticRecord Tag Valies
H’80 recordType
H’82 billType
H’83 serviceIdentifier
H’A4 sPC
H’80 sPC14
H’81 sPC24
H’A5 oPC
H’80 sPC14
H’81 sPC24
H’A6 dPC
H’80 sPC14
H’81 sPC24
H’A7 chargedNeighbor
H’80 sPC14
H’81 sPC24
H’88 amountOfMessage
H’89 amountOfOctets
H’8A recordOpeningTime
H’8B recordClosingTime
H’8C physicalLocation
3.3.25 sigSCCPStatisticRecord
Table 49 sigSCCPStatisticRecord Tag Values
H’80 recordType
H’82 billType
H’A3 sPC
H’80 sPC14
H’81 sPC24
H’A4 oPC
H’80 sPC14
H’81 sPC24
H’A5 dPC
H’80 sPC14
H’81 sPC24
H’86 sSN
H’87 amountOfGTMessages
H’88 recordOpeningTime
H’89 recordClosingTime
H’8A physicalLocation
5
4 ANNEX
4.1 Packing of 7-bit characters
If a character number  is noted in the following way:
b7 b6 b5 b4 b3 b2 b1
10 a b c d e f g

The packing of the 7-bitscharacters in octets is done by completing the octets with
zeros on the left.
For examples, packing: 
one character in one octet:
5 bits number:
7 6 5 4 3 2 1 0
0 1a 1b 1c 1d 1e 1f 1g
two characters in two octets:
bits number:
10 7 6 5 4 3 2 1 0
2g 1a 1b 1c 1d 1e 1f 1g
0 0 2a 2b 2c 2d 2e 2f
three characters in three octets:
bits number:
15 7 6 5 4 3 2 1 0
2g 1a 1b 1c 1d 1e 1f 1g
3f 3g 2a 2b 2c 2d 2e 2f
0 0 0 3a 3b 3c 3d 3e
20
seven characters in seven octets:
bits number:
7 6 5 4 3 2 1 0
2g 1a 1b 1c 1d 1e 1f 1g
25 3f 3g 2a 2b 2c 2d 2e 2f
4e 4f 4g 3a 3b 3c 3d 3e
5d 5e 5f 5g 4a 4b 4c 4d
6c 6d 6e 6f 6g 5a 5b 5c
7b 7c 7d 7e 7f 7g 6a 6b
30 0 0 0 0 0 0 0 7a
eight characters in seven octets:
bits number:
7 6 5 4 3 2 1 0
2g 1a 1b 1c 1d 1e 1f 1g
35 3f 3g 2a 2b 2c 2d 2e 2f
4e 4f 4g 3a 3b 3c 3d 3e
5d 5e 5f 5g 4a 4b 4c 4d
6c 6d 6e 6f 6g 5a 5b 5c
7b 7c 7d 7e 7f 7g 6a 6b
40 8a 8b 8c 8d 8e 8f 8g 7a
The bit number zero is always transmitted first.

Therefore, in 140 octets, it is possible to pack (140x8)/7=160 characters.
4.2 Description of Version Number

45 The version number of current document is composed of three parts separated by
“.”(e.g V4.5.0) as defined below:

Vxx.xx.xx The third digit is incremented when editorial

changes have been incorporated in the
document.When the digit is changed,the
billing system need not upgrade it’s
software.
The second digit is incremented when adding
new fields to the current CDRs or when the
definition of certain field changed.When the digit
is changed,the billing system should upgrade
it’s software.
The first digit is incremented when new CDR
types have been added to current document.
When the digit is changed,the billing system may
upgrade it’s software if it needs the added CDR
type.
Figure 4 Definition of version number

B4.3.4.9 ZXWN CDR Asn.1 Format For Cs (v5.4.0)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

B4.3.4.9 ZXWN CDR Asn.1 Format For Cs (v5.4.0)

Încărcat de

Drepturi de autor:

Formate disponibile

ZTE CDR ASN.

ZTE CDR Format for ZXWN CS V5.4.0

About the Document

Add “HotBillingTag” to MOC,

1. Modify error tag values

ZTE Confidential Proprietary I

Change the title of chapter 2 and

ZTE Confidential Proprietary II

1. Modify the tag value of

ZTE Confidential Proprietary III

1. Add SmsRefrenceNumber filed

ZTE Confidential Proprietary IV

Copyright © 2005 ZTE Corporation Shenzhen P. R. China

Due to update and improvement of ZTE products and technologies,

ZTE Confidential Proprietary V

ZTE Confidential Proprietary VI

2.2.12 Called Party Address(MGCF)..................................................................................................44

ZTE Confidential Proprietary VII

2.2.72 Is CAMEL Call.........................................................................................................................57

ZTE Confidential Proprietary VIII

2.2.131 SDP Session Description(MGCF)........................................................................................66

ZTE Confidential Proprietary IX

ZTE Confidential Proprietary X

ZTE Confidential Proprietary XI

ZTE Confidential Proprietary XII

ZTE Confidential Proprietary XIII

Figures and Tables

ZTE Confidential Proprietary XIV

ZTE Confidential Proprietary XV

ZTE Confidential Proprietary Page 1 of 173

1.2 Structure of the CDR File

1.2.2 Charging Data Record

15 Figure 1 Structure Diagrams of Block

1.2.4 CDR File

Figure 2 Structure Diagrams of CDR File

1.3 CDR Encoding

ZTE Confidential Proprietary Page 2 of 173

in “ASN.1 encoding rules: Specification of Basic Notation, ITU-T Recommendation

1.3.2 Encoding of the Tag

 Bits 8-7  Class identifier

2. Use of a leading octet for tag numbers bigger than or equal to 31

Subsequent octets are encoded as:

 Bits 8  set to 1 in all non-last subsequent octets

ZTE Confidential Proprietary Page 3 of 173

 Bit 7-1  Bits 7-1 of all subsequent octets encoded as

1.3.3 Encoding of the length

LLLLLLL represents the length of the content

10 LLLLLLLL represents the length of the content

1.3.4 Encoding of the content

1.3.5 ASN.1 BER Encoding of Integers

ZTE Confidential Proprietary Page 4 of 173

1.3.6 Structure Diagrams of Charging Data Record

Figure 3 Structure Diagrams of Charging Data Record

ZTE Confidential Proprietary Page 5 of 173

2.1.1 Mobile Originated Call

ZTE Confidential Proprietary Page 6 of 173

Field Category Description

ZTE Confidential Proprietary Page 7 of 173

Field Category Description

ZTE Confidential Proprietary Page 8 of 173

Field Category Description

ZTE Confidential Proprietary Page 9 of 173

Field Category Description