View
780
Download
131
Category
Tags:
Preview:
Citation preview
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1CDR Description
HUAWEI TECHNOLOGIES CO., LTD.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page ii of 176
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, 518129, People’s Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2007. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 3 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
About This Document
Author
Prepared by Guo Jin, Li Chunlin Date 2004-8-9
Reviewed by
Gao Yue, Jia Yongli Date 2005-3-14
Approved by
Yang Jun Date 2005-3-14
SummaryThis document introduces HUAWEI CDR structure.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 5 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1CDR Description
History
Issue
Details Date Author Approved by
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 6 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Contents
1 ASN.1 Encoding Format................................................................161.1 ASN.1 Encoding Format..................................................................................................................................16
1.2 ASN.1 Encoding Format..................................................................................................................................16
1.2.1 Encoding Rules of Identifier Octets.......................................................................................................17
1.2.2 Encoding Rules of Length Octets...........................................................................................................18
1.2.3 Encoding Rules of Contents Octets........................................................................................................19
1.2.4 Encoding Rules of End-of-Contents Octets............................................................................................21
1.2.5 Structure of CDR Files...........................................................................................................................21
2 Record Contents..........................................................................252.1 Mobile Originated Call Attempt......................................................................................................................25
2.2 Mobile Originated Emergency Call Attempt...................................................................................................36
2.3 Mobile Originated Call Forwarding Attempt...................................................................................................47
2.4 Mobile Terminated Call Attempt.....................................................................................................................58
2.5 Roaming Call Attempt.....................................................................................................................................68
2.6 Incoming Gateway Call Attempt.....................................................................................................................73
2.7 Outgoing Gateway Call Attempt......................................................................................................................77
2.8 Transit Call Attempt.........................................................................................................................................81
2.9 Short Message Service, Mobile Originated.....................................................................................................85
2.10 Short Message Service, Mobile Terminated..................................................................................................88
2.11 Mobile Terminated Location Request (MT-LR)............................................................................................91
2.12 Mobile Originated Location Request (MO-LR)............................................................................................93
2.13 Network Induced Location Request (NI-LR)................................................................................................96
2.14 Supplementary Service Actions.....................................................................................................................98
2.15 HLR Interrogation........................................................................................................................................101
2.16 Common Equipment Usage Record............................................................................................................102
2.17 Terminating CAMEL Call Attempt..............................................................................................................105
2.18 IMEI Observation Ticket.............................................................................................................................110
2.19 Location Update (VLR)...............................................................................................................................111
3 Description of Record Fields.......................................................1133.1 Additional Charging Information...................................................................................................................113
3.2 aiurRequested.................................................................................................................................................113
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 7 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1CDR Description
3.3 AoC parameters / change of AoC parameters................................................................................................114
3.4 audioDataType...............................................................................................................................................114
3.5 basicService/changeOfService/isdnBasicService..........................................................................................115
3.6 bCategory.......................................................................................................................................................119
3.7 callDuration....................................................................................................................................................119
3.8 calling Number/called Number / connected Number/translated Number......................................................121
3.9 callReference.................................................................................................................................................122
3.10 CallType.......................................................................................................................................................122
3.11 cAMELCallLegInformation.........................................................................................................................122
3.12 cAMELDestinationNumber.........................................................................................................................123
3.13 cAMELInitCFIndicator...............................................................................................................................123
3.14 cAMELSMSInformation.............................................................................................................................124
3.15 chargeAreaCode...........................................................................................................................................124
3.16 calledChargeAreaCode................................................................................................................................125
3.17 callEmlppPriority/ callerDefaultEmlppPriority/calledEmlppPriority.........................................................125
3.18 camelphase...................................................................................................................................................125
3.19 cARP............................................................................................................................................................125
3.20 Category.......................................................................................................................................................126
3.21 chargedParty................................................................................................................................................126
3.22 classmark3...................................................................................................................................................126
3.23 concatenatedSMSReferenceNumber...........................................................................................................126
3.24 csReference..................................................................................................................................................127
3.25 csaReference................................................................................................................................................128
3.26 cUGIndex.....................................................................................................................................................128
3.27 cUGOutgoingAccessIndicator.....................................................................................................................128
3.28 cUGInterlockCode.......................................................................................................................................128
3.29 cUGOutgoingAccessUsed/ cUGIncomingAccessUsed...............................................................................128
3.30 causeForTerm...............................................................................................................................................129
3.31 cmnFlag.......................................................................................................................................................129
3.32 defaultCallHandling /defaultSMSHandling.................................................................................................130
3.33 destinationNumber.......................................................................................................................................130
3.34 destinationRoutingAddress..........................................................................................................................130
3.35 Diagnostics...................................................................................................................................................130
3.36 disconnectParty............................................................................................................................................132
3.37 eaSubscriberInfo..........................................................................................................................................132
3.38 eCategory.....................................................................................................................................................132
3.39 emsDigits.....................................................................................................................................................133
3.40 emsKey........................................................................................................................................................133
3.41 equipmentId.................................................................................................................................................133
3.42 equipmentType.............................................................................................................................................133
3.43 eventTimeStamps.........................................................................................................................................133
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 8 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
3.44 firstmccmnc/intermediatemccmnc/lastmccmnc...........................................................................................134
3.45 fnur...............................................................................................................................................................135
3.46 freeFormatData............................................................................................................................................135
3.47 freeFormatDataAppend...............................................................................................................................135
3.48 globalAreaID / changeOfglobalAreaID.......................................................................................................136
3.49 guaranteedBitRate........................................................................................................................................136
3.50 gsm-SCFAddress..........................................................................................................................................137
3.51 groupCallType..............................................................................................................................................137
3.52 groupCallReference.....................................................................................................................................137
3.53 hLC..............................................................................................................................................................137
3.54 hotbillingTag................................................................................................................................................138
3.55 interrogationResult.......................................................................................................................................138
3.56 imeiCheckEvent...........................................................................................................................................138
3.57 imeiStatus.....................................................................................................................................................138
3.58 initialCallAttemptFlag.................................................................................................................................139
3.59 interactionWithIP.........................................................................................................................................139
3.60 iSDN-BC......................................................................................................................................................139
3.61 lcsCause.......................................................................................................................................................139
3.62 lcsClientIdentity...........................................................................................................................................139
3.63 lcsClientType...............................................................................................................................................140
3.64 lcsPriority.....................................................................................................................................................140
3.65 lcsQos...........................................................................................................................................................141
3.66 levelOfCAMELService...............................................................................................................................141
3.67 lLC...............................................................................................................................................................141
3.68 location / changeOfLocation........................................................................................................................141
3.69 locationEstimate...........................................................................................................................................142
3.70 locationType.................................................................................................................................................142
3.71 maximumBitRate.........................................................................................................................................143
3.72 maximumNumberOfSMSInTheConcatenatedSMS.....................................................................................143
3.73 MCTType.....................................................................................................................................................144
3.74 measureDuration..........................................................................................................................................144
3.75 messageReference........................................................................................................................................144
3.76 mlc-Number.................................................................................................................................................144
3.77 msClassmark / changeOfClassmark............................................................................................................144
3.78 modemType..................................................................................................................................................145
3.79 molr-Type.....................................................................................................................................................145
3.80 mSCAddress................................................................................................................................................145
3.81 mscIncomingCircuit / mscOutgoingCircuit................................................................................................146
3.82 mscIncomingROUTE / mscOutgoingROUTE............................................................................................146
3.83 mscIncomingRouteAttribute / mscOutgoingRouteAttribute.......................................................................146
3.84 mscServerIndication....................................................................................................................................146
3.85 networkCallReference.................................................................................................................................147
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 9 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1CDR Description
3.86 networkOperatorId.......................................................................................................................................147
3.87 notificationToMSUser..................................................................................................................................147
3.88 numberOfDPEncountered............................................................................................................................147
3.89 numberOfForwarding..................................................................................................................................147
3.90 originalCalledNumber.................................................................................................................................148
3.91 origination....................................................................................................................................................148
3.92 orgMSCId....................................................................................................................................................148
3.93 orgRNCorBSCId..........................................................................................................................................148
3.94 partialRecordType........................................................................................................................................149
3.95 portedflag.....................................................................................................................................................149
3.96 positioningData............................................................................................................................................150
3.97 privacyOverride...........................................................................................................................................150
3.98 radioChanRequested/ radioChanUsed / changeOfRadioChan.....................................................................150
3.99 rateIndication...............................................................................................................................................151
3.100 recordingEntity..........................................................................................................................................151
3.101 recordExtensions........................................................................................................................................152
3.102 recordNumber............................................................................................................................................152
3.103 recordType.................................................................................................................................................152
3.104 redirectingnumber......................................................................................................................................153
3.105 redirectingcounter......................................................................................................................................153
3.106 resourceChargeIPnumber...........................................................................................................................153
3.107 Roaming number........................................................................................................................................153
3.108 routingNumber...........................................................................................................................................153
3.109 sequenceNumber........................................................................................................................................154
3.110 servedIMEI.................................................................................................................................................154
3.111 servedIMSI/calledIMSI..............................................................................................................................155
3.112 servedMSISDN..........................................................................................................................................156
3.113 serviceCentre..............................................................................................................................................156
3.114 serviceKey..................................................................................................................................................156
3.115 smsResult...................................................................................................................................................156
3.116 speechVersionSupported/speechVersionUsed............................................................................................157
3.117 systemType.................................................................................................................................................157
3.118 supplServiceUsed/supplService.................................................................................................................157
3.119 ssAction......................................................................................................................................................161
3.120 ssActionResult...........................................................................................................................................161
3.121 ssParameters...............................................................................................................................................161
3.122 smstext.......................................................................................................................................................162
3.123 smsUserDataType......................................................................................................................................162
3.124 selectedCIC................................................................................................................................................163
3.125 sequenceNumberOfTheCurrentSMS.........................................................................................................163
3.126 subscriberCategory....................................................................................................................................163
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 10 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
3.127 tariffCode...................................................................................................................................................164
3.128 transparencyIndicator.................................................................................................................................164
3.129 typeOfSubscribers......................................................................................................................................164
3.130 Usertype.....................................................................................................................................................164
3.131 ussdCodingScheme....................................................................................................................................165
3.132 ussdString...................................................................................................................................................165
3.133 ussdNotifyCounter.....................................................................................................................................165
3.134 ussdRequestCounter...................................................................................................................................165
3.135 ussdCallBackFlag......................................................................................................................................165
3.136 uuslType.....................................................................................................................................................165
3.137 voiceIndicator............................................................................................................................................166
3.138 zoneCode...................................................................................................................................................166
4 ASN.1 Description of the CDR File...............................................167
5 Examples of CDRs......................................................................168
6 Revision History............................................................................................171
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 11 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Figures
Figure 1-1 Encoding diagram when the value of tag ranges from 0 to 30 (inclusive)..........................................17
Figure 1-2 Encoding diagram when the value of tag is equal to or more than 31................................................18
Figure 1-3 Structure of a CDR file........................................................................................................................22
Figure 1-4 Binary code stream of the ASN.1 CDR file........................................................................................23
Figure 3-1 Call duration......................................................................................................................................120
Figure 3-2 Method of splitting the short message...............................................................................................127
Figure 3-3 Structure of the IMEI........................................................................................................................154
Figure 3-4 Structure of the IMSI.........................................................................................................................155
Figure 3-5 Structure of the MSISDN..................................................................................................................156
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 13 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Tables
Table 2-1 MOC record..........................................................................................................................................25
Table 2-2 MOC emergency record........................................................................................................................36
Table 2-3 MOC, call forwarding record................................................................................................................47
Table 2-4 MTC record...........................................................................................................................................58
Table 2-5 Roaming record.....................................................................................................................................68
Table 2-6 Incoming gateway record......................................................................................................................73
Table 2-7 Outgoing gateway record......................................................................................................................77
Table 2-8 Transit record........................................................................................................................................81
Table 2-9 SMS-MO record....................................................................................................................................85
Table 2-10 SMS-MT record..................................................................................................................................88
Table 2-11 LCS-MT record...................................................................................................................................91
Table 2-12 LCS-MO record..............................................................................................................................9493
Table 2-13 LCS-NI record.....................................................................................................................................96
Table 2-14 SS-action record..................................................................................................................................99
Table 2-15 HLR interrogation record..................................................................................................................101
Table 2-16 Common equipment usage record.....................................................................................................103
Table 2-17 Terminating CAMEL call attempt record.........................................................................................105
Table 2-18 IMEI ticket........................................................................................................................................110
Table 2-19 Location update (VLR) record..........................................................................................................111
Table 3-1 Description of the time information....................................................................................................120
Table 5-1 The correlation between CDRs and examples....................................................................................168
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 15 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
1 ASN.1 Encoding Format
1.1 ASN.1 Encoding FormatASN.1 is short for Abstract Syntax Notation One.
ASN.1 is regarded as a high-level protocol language. It can be used to clearly describe the complex data structures, and it is widely accepted as the syntax standard for the application layer protocols.
ASN.1 provides protocol designers with simple types, for instance, integer, Boolean, and octet string. Based on these simple types, the protocol designer can construct more complex data types.
More complex data types can be built from a set of simple types by using the unique Tags.
For example, a CDR can be structured with a serial of combinations of data fields. Each data field can be an encoding unit or a combination of several encoding units.
An encoding unit consists of 4 components at most:
Identifier octets (also called Tag)
For details, see section 1.2.1 "Encoding Rules of Identifier Octets."
Length octets
For details, see section 1.2.2 "Encoding Rules of Length Octets."
Contents octets
For details, see section 1.2.3 "Encoding Rules of Contents Octets."
End-of-contents octets
They are used only in indefinite length encoding mode. For details, see section 1.2.4 "Encoding Rules of End-of-Contents Octets."
1.2 ASN.1 Encoding FormatThis section describes the encoding rules of each ASN.1 unit and the CDR file structure.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 16 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
1.2.1 Encoding Rules of Identifier OctetsThe identifier octet identifies the protocol data type corresponding to this encoding unit. The encoding is classified into the following cases:
Case 1
A single octet is used when the value of tag ranges from 0 to 30 (inclusive). The meaning of each bit is as follows:
Bits 8 and 7 specify the class identifiers of the data. The values are Universal-00, Application-01, Context-Specific-10, and Private-11.
Bit 6 specifies whether the data unit is primitive or constructed. The values are Primitive-0 and Construct-1.
Bits 5-1 specify the class numbers, that is, number of tag.
Universal is a basic class defined in the ASN.1 specifications. It is used to allocate tags for the basic class. For example, Boolean is used when the value of Tag is 1.
Application is seldom used, and therefore it is not described here.
Context-Specific is used to define the class types.
Private can be negotiated based on the actual conditions.
Primitive indicates that the minimum ASN encoding unit is applied for the field.
Construct indicates that the field is composed of multiple ASN encoding units.
Figure 1-1 Encoding diagram when the value of tag ranges from 0 to 30 (inclusive)
8 7 6 5 4 3 2 1
+-------+---+------------------+
1 ¦ CLASS ¦P/C¦ TAG NUMBER ¦
+------------------------------+
Bits 8-7: Class identifier:
+----------------------------+
¦ Bit: 8 7 ¦
+----------------------------¦
¦ Universal 0 0 ¦
¦ Application 0 1 ¦
¦ Context-specific 1 0 ¦
¦ Private 1 1 ¦
+----------------------------+
Bit 6 : Primitive (0) or
Constructed (1)
Bits 5-1: binary integer with bit 5 as msb
Case 2
A leading octet together with several subsequent octets is used when the value of the tag is equal to or more than 31.
Bits 8, 7, and 6 of the leading octet are the same as those of the single octet; bits 5-1 of the leading octet are 11111.
The subsequent octets comply with the following rules:
− Bit 8 of all the subsequent octets, except for the last one, is 1.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 17 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
− The value of bits 7-1 from the first subsequent octet to the last subsequent octet is equal to the tag number.
− Bits 7-1 of the first subsequent octet cannot be all 0s.
For details, see Figure 1-1.
Figure 1-1 Encoding diagram when the value of tag is equal to or more than 31
8 7 6 5 4 3 2 1
+-------+---+---+---+---+---+---¦
1 ¦ CLASS ¦P/C¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦
+-------------------------------+
Bits 8-7: Class identifier as for single octet id
Bit 6 : Primitive (0) or
Constructed (1)
Bits 5-1: all bits set to 1
Subsequent octets are encoded as follows:
8 7 6 5 4 3 2 1
+---+---------------------------¦ first
2 ¦ 1 ¦ NUMBER of TAG (msb) ¦ subsequent
+-------------------------------¦
. .
. .
+-------------------------------¦ last
¦ 0 ¦ NUMBER of TAG (lsb) ¦ subsequent
+-------------------------------+
Bits 8 : set to 1 in all non-last subsequent
octets
Bits 7-1: Bits 7-1 of all subsequent octets
encoded as a binary integer equal to
the tag number with bit 7 of the first
subsequent octet as most significant
bit.
1.2.2 Encoding Rules of Length OctetsThe length octets identify the length of the content fields, without the length of other fields.
There are three modes for encoding length octets: short, long, and indefinite. The indefinite encoding mode is not applied in ASN.1 CDRs; therefore, it is not described in the subsequent sections.
Short Encoding Mode
A single octet is used when the value of the length octets is equal to or less than 127.
Bit 8 is 0.
Bits 7-1 specify the length.
If L is equal to 26H, the length is encoded as 0010,0110.
8 7 6 5 4 3 2 1
+----------------------------¦
1 ¦ 0 L L L L L L L ¦
+----------------------------+
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 18 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
LLLLLLL represents the length of the content
Long Encoding Mode
More octets are used when the value of the length octets is more than 127.
8 7 6 5 4 3 2 1
+---+-------------------------¦
1 ¦ 1 ¦ 0 < n < 127 ¦
+-----------------------------+
+-----------------------------¦
2 ¦ L L L L L L L L ¦
+-----------------------------+
...
+-----------------------------¦
n+1¦ L L L L L L L L ¦
+-----------------------------+
LLLLLLL represents the length of the content
Bit 8 of the first octet is 1 fixedly and bits 1-7 specify the number of octets occupied by the length.
The second octet to the n+1 octet specify the value of the length.
1.2.3 Encoding Rules of Contents OctetsThe content octets can be null, or a single octet, or more octets. The value of the content octets depends on the data class it stands for.
The content octets are encoded as follows:
8 7 6 5 4 3 2 1
+------------------------------¦
¦ most significant byte ¦ octet 1
+------------------------------¦
¦ ¦ octet 2
+------------------------------¦
. .
. .
+------------------------------¦
¦ least significant byte ¦ octet n
+------------------------------+
The following describes different data classes:
BOOLEAN
This class can be encoded only in primitive mode.
The false encoding is as follows:
Tag Length Value
+------------------------------¦
¦ 01H ¦ 01H ¦ 0000, 0000 ¦
+------------------------------¦
The true encoding is as follows (with any of bits is not 0):
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 19 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Tag Length Value
+------------------------------¦
¦ 01H ¦ 01H ¦ 1111, 1011 ¦
+------------------------------¦
NULL
This class can be encoded only in primitive mode and has only one value. Therefore, if you do not fill the value, it does not consume the space.
Tag Length Value
+------------------------------¦
¦ 05H ¦ 00H ¦
+------------------------------¦
INTEGER
This class can be encoded only in primitive mode. It is classified into the positive and the negative. The negative number is not applied in the ASN.1 CDRs; therefore, it is not described in the subsequent sections.
For the positive number, if the highest bit is 0, this class is encoded directly; if the highest bit is 1, an octet with all 0s is added before the highest bit, that is, the code-filling mode is adopted. For example, 250 is encoded as follows:
Tag Length Value
+-------------------------------------¦
¦ 02H ¦ 02H ¦ 0000,0000 1111,1010¦
+-------------------------------------¦
ENUMERATED
The encoding mode of this class is the same as that of the INTEGER class.
BIT STRING
This class can be encoded in primitive mode or in structured mode. The following takes the bit string 1011011101011'B as an example to describe the two modes for encoding.
Primitive
Tag Length Value
+------------------------------------------¦
¦ 03H ¦ 03H ¦ 03H 10110111 01011xxx¦
+------------------------------------------¦
Note: An octet is added before the bit string '1011011101011'B and its value ranges from 0 to 7. This octet indicates the number of bits filled after the bit string and is mainly applied when the bit string is not the multiple of number 8.
Constructed
The constructed mode is used when certain encodings are still unsure. The bit string '1011011101011'B is encoded as follows:
Tag Length Value
+----------------------------------------------¦
¦ 03H ¦ 80H ¦ T L V
¦ ¦ 03H ¦ 02H ¦ 00H 10110111¦
¦ ¦ 03H ¦ 02H ¦ 03H 01011xxx¦
00H 00H
+-----------------------------------------------¦
Note: In this case, the length of the whole bit string uses the indefinite encoding mode
OCTET STRING
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 20 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
The encoding rule of this class is the same as that of the BIT STRING class. This class takes an octet as a unit; therefore, you need not fill any bit any more.
SET
This class can be encoded only in constructed mode. Each member is encoded in the TLV format.
The following takes MOC {recordType ENUMERATED, callDuration INTEGER }:={ recordType 0,callDuration 11} as an example:
Tag Length Value
+--------------------------------------------¦
¦ 16H ¦ 80H ¦ T L V
¦ ¦ 02H ¦ 01H ¦ 0000 0000¦
¦ ¦ 02H ¦ 01H ¦ 0000 1011¦
+--------------------------------------------¦
SEQUENCE
The encoding mode of this class is the same as that of the SET class. The sequence of members of this class must be consistent with the defined sequence, but this requirement does not apply to the SET class.
SET OF
The encoding mode of this class is the same as that of the SET class.
SEQUENCE OF
The encoding mode of this class is the same as that of the SEQUENCE class.
Other types are not common; therefore, they are not described in the subsequent sections.
1.2.4 Encoding Rules of End-of-Contents OctetsThe end-of-contents octets exist only in the indefinite mode; therefore, they are not described in the subsequent sections.
1.2.5 Structure of CDR FilesIf a CDR file is of the SEQUENCE type and uses the TLV format, its value is composed of following parts:
Header: It is the header of the CDR file and the TAG value is A0.
Event Record: It is the content of the CDR file. SEQUENCE OF indicates that the event record can be composed of many CDRs and the TAG value of the callEventRecords is A1.
Trailer: It is the trailer of the CDR file and the TAG value is A2.
Extensions: The TAG value is A3, without contents. The length is 0.
For details, see Figure 1-1.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 21 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Figure 1-1 Structure of a CDR file
Figure 1-2 takes the ASN.1 CDR file as an example to show its binary code stream.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 22 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Figure 1-2 Binary code stream of the ASN.1 CDR file
The following shows the ASN.1 files corresponding to the figure above:
ASN.1 BER
Decoded files
record no.: 0
recordType: moCallRecord
servedIMSI: 460007001002000
servedMSISDN: (91)8613720012000
callingNumber: (91)8613720012000
calledNumber: (A1)13720012010
roamingNumber: (A1)136755002201
recordingEntity: (91)86136755002
mscIncomingROUTE: TO_BSC1
mscOutgoingROUTE: TO_BSC2
location: LAC-3001. CellID-0001
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 23 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
basicService: teleService(11)
msClassmark: 021C00
answerTime: 070809141502
releaseTime: 070809141513
callDuration: 11
radioChanRequested: fullRateChannel
radioChanUsed: halfRate
causeForTerm: normalRelease
diagnostics: gsm0408Cause(90)
callReference: 16 00 00 00 ED
additionalChgInfo: chargeIndicator-charge
networkcallReference: 16 05 A2 30 1B
mSCAddress: (91)86136755002
speechVersionSupported: 1
speechVersionUsed: 1
systemType: gERAN
chargedParty: callingParty
mscOutgoingCircuit: 1
orgRNCorBSCId: 01 0B
orgMSCId: 00 0B
callerDefaultEmlppPriority: EMLPP_CallPriorityLevel4(1)
globalAreaID: 64 F0 00 30 01 00 01
subscriberCategory: Common(A)
firstmccmnc: 64F000
lastmccmnc: 64F000
calledIMSI: 460007001002010
typeOfSubscribers:visiting
audioDataType:audio
disconnectparty:unknown
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 24 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
2 Record Contents
The following tables describe the contents of each of the call and event records defined in the present document. Each table contains the name of the field, a key indicating whether or not the field is mandatory, and a description of the contents.
The key fields have the following meanings:
M: This field is mandatory and always present in this CDR.
O: This field is optional in this CDR.
C: This field is only available under certain conditions. This field is present if it is available.
-: This field need not be encoded in this CDR.
2G: The MSOFTX3000functions as an MSC in a 2G network.
3G: The MSOFTX3000 functions as an MSC in a 3G network.
n: It specifies the number of "sequence" or "set".
The numbers in the brackets after field types specify the value range of this field length.
2.1 Mobile Originated Call AttemptIf the generation of these records is enabled, an MOC record shall be created for each outgoing call attempt made by a mobile station. These MOC records shall be produced in the originating MSC. Table 2-1 lists the formats of MOC records.
Table 2-1 MOC record
Field 2G
3G
TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Mobile originated. CallEventRecordType = 0x00
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the calling party.
servedIMEI O O 0x82 TBCD(8) The IMEI of the calling ME, if available.
servedMSISDN M M 0x83 ADRESS(2..9) The primary MSISDN of the calling party.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 25 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
callingNumber M M 0x84 ADRESS (2..17) The address of the calling party.
calledNumber M M 0x85 ADRESS (2..17) The address of the called party, for example, the number dialed by the calling subscriber.
translatedNumber O O 0x86 ADRESS (2..17) The called number after digit translation within the MSC (if applicable).
connectedNumber O O 0x87 ADRESS (2..17) The number of the connected party if it is different from the Called Number.
roamingNumber O O 0x88 ADRESS (2..17) The Mobile Station Roaming Number employed to route this connection, if applicable.
recordingEntity M M 0x89 ADRESS (2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xAA IA5(1..32) The MSC route on which the call is originated, usually from the BSC or RNC.
mscOutgoingROUTE M M 0xAB IA5(1..32) The route on which the call left the MSC.
location M M 0xAC OCTET(8) The identity of the cell or the SAC at the time of CDR creation, including the location area code.
changeOfLocation O O 0xAD SEQUENCE OF ( 23 * n )
A list of changes in Location Area Code / Cell Identifier each time-stamped.
basicService M M 0xAE OCTET(3) The bearer or teleservice employed.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 26 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
transparencyIndicator O O 0x8F ENUMERATED
(1)
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent mode.
changeOfService - - 0xB0 SEQUENCE OF ( (18..27) * n)
A list of changes of basic service during a connection each time-stamped.
supplServicesUsed O O 0xB1 SEQUENCE OF
(16 * n)
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked.
aocParameters O O 0xB2 OCTET(4..28) The charge advice parameters sent to the MS on call setup.
changeOfAOCParms O O 0xB3 SEQUENCE OF ( 43 * n)
The new AOC parameters sent to the MS, for example, as a result of a tariff switchover, including the time at which the new set was applied.
msClassmark M M 0x94 OCTET(2..3) The mobile station classmark employed on call setup.
changeOfClassmark O O 0xB5 OCTET (16 ) A list of changes to the classmark during the connection each time-stamped.
setupTime C C 0x9F 81 49
OCTET(9) The time stamp when the Setup message or IAM message is received from the calling party side.
seizureTime C C 0x96 OCTET(9) The time stamp when the assignment at the calling party side is completed.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 27 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
alertingTime C C 0x9F 81 4A
OCTET(9) The time stamp when the Alerting message or ACM message is received from the called party side.
answerTime M M 0x97 OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x98 OCTET(9) The time stamp when either of the calling or called party releases the traffic channel.
callDuration M M 0x99 INTEGER(1..2) The chargeable duration of the connection for successful calls, the holding time for call attempts.
radioChanRequested M - 0x9B ENUMERATED
(1)
The type of radio traffic channel (full-rate or half-rate) requested by the MS.
radioChanUsed M - 0x9C ENUMERATED
(1)
The type of radio channel actually used (full-rate or half-rate).
changeOfRadioChan O - 0xBD OCTET (14..17 ) A list of changes to the types of radio traffic channels each time-stamped.
causeForTerm M M 0x9E INTEGER (1) The reason for the release of the connection.
diagnostics M M 0xBF 1F INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x9F 20 OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
sequenceNumber O O 0x9F 21 INTEGER(1) The partial record sequence number, only present in case of partial records.
additionalChgInfo M M 0xBF 22 SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 28 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
recordExtensions - - 0xBF 23 SET OF (11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
gsm-SCFAddress O O 0x9F 24 ADRESS(2..9) The CAMEL server serving the subscriber. Shall be present only if CAMEL is applied.
serviceKey O O 0x9F 25 INTEGER(1..4) The CAMEL service logic to be applied. Shall be present only if CAMEL is applied.
networkCallReference M M 0x9F 26 OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes. Shall be present only if CAMEL is applied.
mSCAddress M M 0x9F 27 ADRESS(2..9) The E.164 number assigned to the MSC that generated the network call reference.
cAMELInitCFIndicator - - 0x9F 28 BOOLEAN(1) Indicates that the CAMEL server initiates call forwarding in the CFW record.
defaultCallHandling O O 0x9F 29 ENUMERATED
(1)
Indicates whether a CAMEL call encounters default call handling. This field shall be present only if default call handling has been applied.
fnur O O 0x9F 2D ENUMERATED
(1)
The user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 29 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
aiurRequested O O 0x9F 2E ENUMERATED
(1)
The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for non-transparent HSCSD connections.
speechVersionSupported M - 0x9F 31 OCTET(1) The speech version supported by the MS with highest priority indicated by MS.
speechVersionUsed M - 0x9F 32 OCTET(1) The speech version used for that call.
numberOfDPEncountered O O 0x9F 33 INTEGER(1) Number that counts how often armed detection points (TDP and EDP) were encountered. Shall be present only if CAMEL is applied.
levelOfCAMELService O O 0x9F 34 BIT STRING(2) The indicator for the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied.
freeFormatData O O 0x9F 35 OCTET(1..160) This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied.
cAMELCallLegInformation O O 0xBF 36 SEQUENCE OF
((104..124) * n)
A set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Shall be present only if CAMEL is applied.
freeFormatDataAppend O O 0x9F 37 BOOLEAN (1) Indicates that free format data from this CDR is to be appended to free format data in previous partial CDR.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 30 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
defaultCallHandling-2 O O 0x9F 38 ENUMERATED
(1)
Indicates whether a CAMEL call encountered default call handling for the second service such as the dialed service. This field shall be present only if default call handling has been applied.
gsm-SCFAddress-2 O O 0x9F 39 ADRESS (2..9) Indicates the CAMEL server serving the subscriber for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service.
serviceKey-2 O O 0x9F 3A INTEGER (1..4) Indicates the CAMEL service logic to be applied for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service.
freeFormatData-2 O O 0x9F 3B OCTET(1..160) Indicates the data sent by the gsmSCF in the FCI message(s) for the second service such as the dialed service. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for the second service. Shall be present only if CAMEL is applied for the second service.
freeFormatDataAppend-2 O O 0x9F 3C BOOLEAN (1) Indicates that free format data for the second service such as the dialed service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for the second service.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 31 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
systemType M M 0x9F 3D ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
rateIndication O O 0x9F 3E OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008.
partialRecordType O O 0x9F 45 ENUMERATED
(1)
The event that caused the generation of a partial record. This field is mandatory in case of partial records.
guaranteedBitrate - M 0x9F 46 ENUMERATED
(1)
The bit-rate the UMTS bearer service shall guarantee to the user or application. This field may be used to facilitate admission control based on available resources, and for resource allocation within UMTS.
maximumBitrate - M 0x9F 47 ENUMERATED
(1)
The maximum bit-rate that can be used to make code reservations in the downlink of the radio interface. Its purpose is: 1) to limit the delivered bit-rate to applications or external networks with such limitations, 2) to allow maximum wanted user bit-rate to be defined for applications able to operate with different rates (e.g. applications with adapting codecs). Shall only be present for UMTS data connections.
modemType O O 0x9F 81 0B
ENUMERATED
(1)
The type of Modem used.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 32 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
classmark3 O O 0x9F 81 0C
OCTET(2) The mobile station classmark 3.
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
originalCalledNumber - - 0x9F 81 0E
ADRESS (2..17) The address of original called party in CFW record. It is invalid in the MOC record.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
calledChargeAreaCode - - 0x9F 81 12
OCTET(1..3) The called party logical area for distance charge.
mscOutgoingCircuit O O 0x9F 81 26
INTEGER (1..2) The CIC, only present in case of outgoing bear type being TDM.
orgRNCorBSCId M M 0x9F 81 27
OCTET(3) The SPC of f the RNC or the BSC.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A
OCTET(1) The EMLPP priority of the call. See 29.002.
callerDefaultEmlppPriority O O 0x9F 81 2B
OCTET(1) The priority of the EMLPP service registered by the calling party. See 29.002.
eaSubscriberInfo O O 0x9F 81 2E
OCTET(3) The calling subscriber's information of Equal Access.
selectedCIC O O 0x9F 81 2F
OCTET(3) The selected code of Carrier identification.
optimalRoutingFlag - - 0x9F 81 31
NULL Shall be present when the optimal routing function is applied. Reserved for future use.
optimalRoutingLateForwardFlag - - 0x9F 81 32
NULL Shall be present when the optimal routing function is applied in the case of the late forward. Reserved for future use.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 33 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
optimalRoutingEarlyForwardFlag - - 0x9F 81 33
NULL Shall be present when the optimal routing function is applied in the case of the early forward. Reserved for future use.
portedflag O O 0x9F 81 34
ENUMERATED
(1)
Indicates whether the user is ported. Reserved for future use.
calledIMSI O O 0x9F 81 35
TBCD(3..8) The IMSI of the called party.
globalAreaID M M 0x9F 81 3C
OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
changeOfglobalAreaID O O 0xBF 81 3D
SEQUENCE OF
(22 * n)
A list of changes in the GCI / SAI each time-stamped.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40
OCTET(3) The MCC and MNC of the network when the call is initiated.
intermediatemccmnc - - 0x9F 81 41
OCTET(3) Reserved for future use.
lastmccmnc O O 0x9F 81 42
OCTET(3) The MCC and MNC of the network when the call is served. Only present after handover.
cUGOutgoingAccessIndicator O O 0x9F 81 43
ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44
OCTET(4) Network code + CUG interlock
cUGOutgoingAccessUsed O O 0x9F 81 45
ENUMERATED
(1)
Indicates whether the calling party and called party are in the same CUG group.
cUGIndex O O 0x9F 81 46
OCTET(2) The index of the CUG subscribers.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 34 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
interactionWithIP O O 0x9F 81 47
NULL (0) In the case of interaction between SSP and IP, GsmSCF play announcement to SSP and start charging.
hotBillingTag O O 0x9F 81 48
INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
voiceIndicator O O 0x9F 81 4B
ENUMERATED
(1)
Indicates that the announcement is played for the local office or other offices when the call is released.
bCategory C C 0x9F 81 4C
ENUMERATED
(1)
Indicates whether the called party is busy or idle.
callType C C 0x9F 81 4D
ENUMERATED
(1)
Indicates the call type, such as the intra-office, incoming, outgoing, tandem, or unknown.
resourceChargeIPnumber O O 0x9F 81 4E
ADRESS (2..17) The address of the IP equipment that plays the announcement in the case of resource charging.
groupCallType O O 0x9F 81 50
ENUMERATED(1) The type of a group call.
groupCallReference O O 0x9F 81 51
OCTET(4) The reference number of a group call.
uus1Type O O 0x9F 81 52
ENUMERATED(1) The type of UUS1.
eCategory O O 0x9F 81 57
INTEGER(1..2) The enhanced subscriber category.
tariffCode O O 0x9F 81 59
INTEGER(1) The tariff code.
disconnectparty O O 0x9F 81 5A
ENUMERATED(1) The party who releases the call first.
csReference O O 0x9F 81 5C
OCTET(1..8) The call segment reference number.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 35 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
csaReference O O 0x9F 81 5D
INTEGER (1..4) The call segment association reference number.
camelphase O O 0x9F 81 5E
ENUMERATED(1) The CAMEL version number.
networkOperatorId O O 0x9F 81 5F
OCTET(1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60
ENUMERATED(1) The type of roaming subscriber.
audioDataType O O 0x9F 81 61
ENUMERATED(1) Indicates whether the data service or speech service is employed by a subscriber.
usertype O O 0x9F 81 63
ENUMERATED(1) Indicates the user type.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C
PartyRelCause Indicates the cause of call release.
zoneCode O O 0x9F 81 70
OCTET (2) The zone code of a cell.
MCTType O O 0x9F 81 75
ENUMERATED(1) The MCT record type.
cARP O O 0x9F 81 76
INTEGER(1) The CARP value registered by the subscriber.
2.2 Mobile Originated Emergency Call AttemptIf the generation of MOC records is enabled, an MOC emergency record shall be created for each outgoing emergency call attempt made by a mobile station. These records shall be produced in the originating MSC. Table 2-1 lists the formats of MOC emergency records.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 36 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Table 2-1 MOC emergency record
Field 2G
3G
TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Mobile originated. CallEventRecordType = 0x00
servedIMSI O O 0x81 TBCD(3..8) The IMSI of the calling party in case of an emergency call with a SIM card.
servedIMEI O O 0x82 TBCD(8) The IMEI of the calling mobile equipment if available.
servedMSISDN O O 0x83 ADRESS(2..9) The primary MSISDN of the calling party.
callingNumber M M 0x84 ADRESS (2..17) The address of the calling party.
calledNumber M M 0x85 ADRESS (2..17) The address of the called party e.g. the number dialed by the calling subscriber.
translatedNumber O O 0x86 ADRESS (2..17) The called number after digit translation within the MSC (if applicable).
connectedNumber O O 0x87 ADRESS (2..17) The number of the connected party if it is different from the Called Number.
roamingNumber O O 0x88 ADRESS (2..17) The Mobile Station Roaming Number employed to route this connection.
recordingEntity M M 0x89 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xAA IA5(1..32) The MSC route on which the call is originated, usually from the BSC or RNC.
mscOutgoingROUTE M M 0xAB IA5(1..32) The route on which the call left the MSC.
location M M 0xAC OCTET(8) The identity of the cell or the SAC at the time of CDR creation, including the location area code.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 37 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
changeOfLocation O O 0xAD SEQUENCE OF
( 23 * n )
A list of changes in Location Area Code / Cell Identifier each time-stamped.
basicService M M 0xAE OCTET(3) The bearer or teleservice employed. Teleservice 'emergency call' in the case of the MOC emergency record.
transparencyIndicator O O 0x8F ENUMERATED
(1)
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent modes.
changeOfService - - 0xB0 SEQUENCE OF ( (18..27) * n)
A list of changes of basic service during a connection each time-stamped.
supplServicesUsed O O 0xB1 SEQUENCE OF
(16 * n)
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked.
aocParameters O O 0xB2 OCTET(4..28) The charge advice parameters sent to the MS on call setup.
changeOfAOCParms O O 0xB3 SEQUENCE OF
( 43 * n)
The new AOC parameters sent to the MS e.g. as a result of a tariff switchover, including the time at which the new set was applied.
msClassmark M M 0x94 OCTET(2..3) The mobile station classmark employed on call setup.
changeOfClassmark O O 0xB5 OCTET (16 ) A list of changes to the classmark during the connection each time-stamped
setupTime C C 0x9F 81 49
OCTET(9) The time stamp when the Setup message or IAM message is received from the calling party side.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 38 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
seizureTime C C 0x96 OCTET(9) The time stamp when the assignment at the calling party side is completed.
alertingTime C C 0x9F 81 4A
OCTET(9) The time stamp when the Alerting message or ACM message is received from the called party side.
answerTime M M 0x97 OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x98 OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x99 INTEGER(1..2) The chargeable duration of the connection for successful calls, the holding time for call attempts.
radioChanRequested M - 0x9B ENUMERATED
(1)
The type of radio traffic channel (full-rate or half-rate) requested by the MS.
radioChanUsed M - 0x9C ENUMERATED
(1)
The type of radio channel actually used (full-rate or half-rate).
changeOfRadioChan O - 0xBD OCTET (14..17 ) A list of changes to the types of radio traffic channels each time-stamped.
causeForTerm M M 0x9E INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xBF 1F
INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x9F 20
OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
sequenceNumber O O 0x9F 21
INTEGER(1) The partial record sequence number, only present in case of partial records.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 39 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
additionalChgInfo M M 0xBF 22
SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
recordExtensions - - 0xBF 23
SET OF (11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
gsm-SCFAddress - - 0x9F 24
ADRESS(2..9) The CAMEL server serving the subscriber. Shall be present only if CAMEL is applied.
serviceKey O O 0x9F 25
INTEGER(1..4) The CAMEL service logic to be applied. Shall be present only if CAMEL is applied. It is not available in the emergency call.
networkCallReference M M 0x9F 26
OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
mSCAddress M M 0x9F 27
ADRESS(2..9) The E.164 number assigned to the MSC that generated the network call reference.
cAMELInitCFIndicator - - 0x9F 28
BOOLEAN(1) Indicates that the CAMEL server initiates call forwarding in the CFW record.
defaultCallHandling - - 0x9F 29
ENUMERATED
(1)
Indicates whether a CAMEL call encounters default call handling. This field shall be present only if default call handling has been applied. It is not available in the emergency call.
fnur O O 0x9F 2D
ENUMERATED
(1)
The user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections.
aiurRequested O O 0x9F 2E
ENUMERATED
(1)
The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for non-transparent HSCSD connections.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 40 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
speechVersionSupported M - 0x9F 31
OCTET(1) The speech version supported by the MS with highest priority indicated by MS.
speechVersionUsed M - 0x9F 32
OCTET(1) The speech version used for that call.
numberOfDPEncountered - - 0x9F 33
INTEGER(1) Number that counts how often armed detection points (TDP and EDP) were encountered. Shall be present only if CAMEL is applied. It is not available in the emergency call.
levelOfCAMELService - - 0x9F 34
BIT STRING(2) The indicator for the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied. It is not available in the emergency call.
freeFormatData - - 0x9F 35
OCTET(1..160) This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for the second service. Shall be present only if CAMEL is applied. It is not available in the emergency call.
cAMELCallLegInformation - - 0xBF 36
SEQUENCE OF
((104..124) * n)
A set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Shall be present only if CAMEL is applied. It is not available in the emergency call.
freeFormatDataAppend - - 0x9F 37
BOOLEAN (1) Indicates that free format data from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied. It is not available in the emergency call.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 41 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
defaultCallHandling-2 - - 0x9F 38
ENUMERATED
(1)
Indicates whether a CAMEL call encountered default call handling for the second service such as the dialed service. This field shall be present only if default call handling has been applied. It is not available in the emergency call.
gsm-SCFAddress-2 - - 0x9F 39
ADRESS (2..9) Indicates the CAMEL server serving the subscriber for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service. It is not available in the emergency call.
serviceKey-2 - - 0x9F 3A
INTEGER (1..4) Indicates the CAMEL service logic to be applied for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service. It is not available in the emergency call.
freeFormatData-2 - - 0x9F 3B
OCTET(1..160) Indicates the data sent by the gsmSCF in the FCI message(s) for the second service such as the dialed service. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for the second service. Shall be present only if CAMEL is applied for the second service. It is not available in the emergency call.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 42 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
freeFormatDataAppend-2 - - 0x9F 3C
BOOLEAN (1) Indicates that free format data for the second service such as the dialed service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for the second service. It is not available in the emergency call.
systemType M M 0x9F 3D
ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
rateIndication O O 0x9F 3E
OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008.
partialRecordType O O 0x9F 45
ENUMERATED
(1)
The event that caused the generation of a partial record. This field is mandatory in case of partial records.
guaranteedBitrate - M 0x9F 46
ENUMERATED
(1)
The bit-rate the UMTS bearer service shall guarantee to the user or application. This field may be used to facilitate admission control based on available resources, and for resource allocation within UMTS. Shall only be present for UMTS data connections.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 43 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
maximumBitrate - M 0x9F 47
ENUMERATED
(1)
The maximum bit-rate that can be used to make code reservations in the downlink of the radio interface. Its purpose is: 1) to limit the delivered bit-rate to applications or external networks with such limitations, 2) to allow maximum wanted user bit-rate to be defined for applications able to operate with different rates (e.g. applications with adapting codecs). Shall only be present for UMTS data connections.
modemType - - 0x9F 81 0B
ENUMERATED
(1)
The type of Modem used.
classmark3 O O 0x9F 81 0C
OCTET(2) The mobile station classmark 3.
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
originalCalledNumber - - 0x9F 81 0E
ADRESS (2..17) The address of original called party in CFW record. It is not available in the emergency call.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
calledChargeAreaCode - - 0x9F 81 12
OCTET(1..3) The called party logical area for distance charge.
mscOutgoingCircuit O O 0x9F 81 26
INTEGER (1..2) The CIC, only present in case of outgoing bear type being TDM.
orgRNCorBSCId M M 0x9F 81 27
OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A
OCTET(1) The EMLPP priority of the call. See 29.002.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 44 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
callerDefaultEmlppPriority O O 0x9F 81 2B
OCTET(1) The priority of the EMLPP service registered by the calling party. See 29.002.
eaSubscriberInfo O O 0x9F 81 2E
OCTET(3) The calling subscriber's information of Equal Access.
selectedCIC O O 0x9F 81 2F
OCTET(3) The selected code of Carrier identification.
optimalRoutingFlag - - 0x9F 81 31
NULL Shall be present when the optimal routing function is applied. Reserved for future use.
optimalRoutingLateForwardFlag - - 0x9F 81 32
NULL Shall be present when the optimal routing function is applied in the case of the late forward. Reserved for future use.
optimalRoutingEarlyForwardFlag
- - 0x9F 81 33
NULL Shall be present when the optimal routing function is applied in the case of the early forward. Reserved for future use.
portedflag - - 0x9F 81 34
ENUMERATED
(1)
Indicates whether the user is ported. Reserved for future use.
calledIMSI O O 0x9F 81 35
TBCD(3..8) The IMSI of the called party.
globalAreaID M M 0x9F 81 3C
OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
changeOfglobalAreaID O O 0xBF 81 3D
SEQUENCE OF
(22 * n)
A list of changes in the GCI / SAI each time-stamped.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40
OCTET(3) The MCC and MNC of the network when the call is initiated.
intermediatemccmnc - - 0x9F 81 41
OCTET(3) Reserved for future use.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 45 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
lastmccmnc O O 0x9F 81 42
OCTET(3) The MCC and MNC of the network when the call is served. Only present after handover.
cUGOutgoingAccessIndicator O O 0x9F 81 43
ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44
OCTET(4) Network code + CUG interlock
cUGOutgoingAccessUsed O O 0x9F 81 45
ENUMERATED
(1)
Indicates whether the calling party and called party are in the same CUG group.
cUGIndex O O 0x9F 81 46
OCTET(2) The index of the CUG subscribers.
interactionWithIP - - 0x9F 81 47
NULL (0) In the case of interaction between SSP and IP, GsmSCF play announcement to SSP and start charging.
hotBillingTag O O 0x9F 81 48
INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
voiceIndicator O O 0x9F 81 4B
ENUMERATED
(1)
Indicates that the announcement is played for the local office or other offices when the call is released.
bCategory C C 0x9F 81 4C
ENUMERATED
(1)
Indicates whether the called party is busy or idle.
callType C C 0x9F 81 4D
ENUMERATED
(1)
Indicates the call type, such as the intra-office, incoming, outgoing, tandem, or unknown.
resourceChargeIPnumber O O 0x9F 81 4E
ADRESS (2..17) The address of the IP equipment that plays the announcement in the case of resource charging.
groupCallType O O 0x9F 81 50
ENUMERATED(1) The type of a group call.
groupCallReference O O 0x9F 81 51
OCTET(4) The reference number of a group call.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 46 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
uus1Type O O 0x9F 81 52
ENUMERATED(1) The type of UUS1.
eCategory O O 0x9F 81 57
INTEGER(1..2) The enhanced subscriber category.
disconnectparty O O 0x9F 81 5A
ENUMERATED(1) The party who releases the call first.
csReference O O 0x9F 81 5C
OCTET(1..8) The call segment reference number.
csaReference O O 0x9F 81 5D
INTEGER (1..4) The call segment association reference number.
camelphase O O 0x9F 81 5E
ENUMERATED(1) The CAMEL version number.
networkOperatorId O O 0x9F 81 5F
OCTET(1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60
ENUMERATED(1) The type of roaming subscriber.
usertype O O 0x9F 81 63
ENUMERATED(1) The user type.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C
PartyRelCause Indicates the cause of call release.
2.3 Mobile Originated Call Forwarding AttemptIf the generation of MOC records is enabled in case of call forwarding, the forwarded-leg of the call shall also result in the production of an MOC record in the MSC that forwards the call. Table 2-1 lists the formats of MOC call forwarding records.
Table 2-1 MOC, call forwarding record
Field 2G
3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Call forwarding. CallEventRecordType = 0x64
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the forwarding party.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 47 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
servedIMEI O O 0x82 TBCD(8) The IMEI of the forwarding mobile equipment if available.
servedMSISDN M M 0x83 ADRESS (2..9) The MSISDN of the forwarding party.
callingNumber M M 0x84 ADRESS (2..17) The number of the calling party if available at this node.
calledNumber M M 0x85 ADRESS (2..17) The address of the "forwarded-to" party.
translatedNumber O O 0x86 ADRESS (2..17) The called number after digit translation within the MSC (if applicable).
connectedNumber O O 0x87 ADRESS (2..17) The number of the connected party if it is different from the Called Number.
roamingNumber O O 0x88 ADRESS (2..17) The Mobile Station Roaming Number employed to route this connection, if applicable.
recordingEntity M M 0x89 ADRESS (2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xAA IA5(1..32) The MSC route on which the call is originated at the forwarding MSC.
mscOutgoingROUTE M M 0xAB IA5(1..32) The route on which the call left the forwarding MSC.
location O O 0xAC OCTET(8) The identity of the cell or the SAC in which the call is forwarded including the location area code.
changeOfLocation O O 0xAD SEQUENCE OF
( 23 * n )
A list of changes in Location Area Code / Cell Identifier each time-stamped.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 48 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
basicService M M 0xAE OCTET(3) The bearer or teleservice employed. It is not available in the forwarding record.
transparencyIndicator O O 0x8F ENUMERATED
(1)
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent modes.
changeOfService O O 0xB0 SEQUENCE OF
( (18..27) * n)
A list of changes of basic service during a connection each time-stamped.
supplServicesUsed O O 0xB1 SEQUENCE OF
(16 * n)
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked.
aocParameters O O 0xB2 OCTET(4..28) The charge advice parameters sent to the MS on call setup.
changeOfAOCParms O O 0xB3 SEQUENCE OF
( 43 * n)
The new AOC parameters sent to the MS e.g. as a result of a tariff switchover, including the time at which the new set was applied.
msClassmark O O 0x94 OCTET(2..3) The mobile station classmark employed on call setup.
changeOfClassmark O O 0xB5 OCTET (16 ) A list of changes to the classmark during the connection each time-stamped
setupTime C C 0x9F 81 49
OCTET(9) The time stamp when the Setup message or IAM message is received from the calling party side.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 49 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
seizureTime C C 0x96 OCTET(9) The time stamp when the assignment at the calling party side is completed. It is not available in the forwarding record.
alertingTime C C 0x9F 81 4A
OCTET(9) The time stamp when the Alerting message or ACM message is received from the called party side.
answerTime M M 0x97 OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x98 OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x99 INTEGER(1..2) The chargeable duration of the connection for successful calls, the holding time of call attempts.
radioChanRequested M - 0x9B ENUMERATED
(1)
The type of radio traffic channel (full-rate or half-rate) requested by the MS.
radioChanUsed M - 0x9C ENUMERATED
(1)
The type of radio channel actually used (full-rate or half-rate).
changeOfRadioChan O - 0xBD OCTET(14..17) A list of changes to the types of radio traffic channels each time-stamped.
causeForTerm M M 0x9E INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xBF 1F
INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x9F 20 OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 50 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
sequenceNumber O O 0x9F 21 INTEGER(1) The partial record sequence number, only present in case of partial records.
additionalChgInfo M M 0xBF 22
SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
recordExtensions - - 0xBF 23
SET OF (11*n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
gsm-SCFAddress O O 0x9F 24 ADRESS(2..9) The CAMEL server serving the subscriber. Shall be present only if CAMEL is applied.
serviceKey O O 0x9F 25 INTEGER(1..4) The CAMEL service logic to be applied. Shall be present only if CAMEL is applied.
networkCallReference M M 0x9F 26 OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
mSCAddress M M 0x9F 27 ADRESS(2..9) The E.164 number assigned to the MSC that generated the network call reference.
cAMELInitCFIndicator O O 0x9F 28 BOOLEAN(1) Indicates that the CAMEL server initiates call forwarding in the CFW record.
defaultCallHandling O O 0x9F 29 ENUMERATED
(1)
Indicates whether a CAMEL call encounters default call handling. This field shall be present only if default call handling has been applied.
fnur O O 0x9F 2D
ENUMERATED
(1)
The user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 51 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
aiurRequested O O 0x9F 2E
ENUMERATED
(1)
The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for non-transparent HSCSD connections.
speechVersionSupported M - 0x9F 31 OCTET(1) The speech version supported by the MS with highest priority indicated by MS.
speechVersionUsed M - 0x9F 32 OCTET(1) The speech version used for that call.
numberOfDPEncountered O O 0x9F 33 INTEGER(1) Number that counts how often armed detection points (TDP and EDP) were encountered. Shall be present only if CAMEL is applied.
levelOfCAMELService O O 0x9F 34 BIT STRING(2) The indicator for the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied.
freeFormatData O O 0x9F 35 OCTET(1..160) This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for the second service.
cAMELCallLegInformation O O 0xBF 36
SEQUENCE OF
((104..124) * n)
A set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Shall be present only if CAMEL is applied.
freeFormatDataAppend O O 0x9F 37 BOOLEAN(1) Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 52 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
defaultCallHandling-2 - - 0x9F 38 ENUMERATED
(1)
Indicates whether or not a CAMEL call encountered default call handling for the second service such as the dialed service. This field shall be present only if default call handling has been applied. Reserved for future use.
gsm-SCFAddress-2 - - 0x9F 39 ADRESS (2..9) The CAMEL server serving the subscriber for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service. Reserved for future use.
serviceKey-2 - - 0x9F 3A
INTEGER (1..4) The CAMEL service logic to be applied for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service. Reserved for future use.
freeFormatData-2 - - 0x9F 3B
OCTET(1..160) This field contains data sent by the gsmSCF in the FCI message(s) for the second service such as the dialed service. The data can be sent either in one FCI message or several FCI messages with append indicator.
freeFormatDataAppend-2 - - 0x9F 3C
BOOLEAN (1) Indicator if free format data for the second service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for the second service. Reserved for future use.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 53 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
systemType O O 0x9F 3D
ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
rateIndication O O 0x9F 3E
OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008.
partialRecordType O O 0x9F 45 ENUMERATED
(1)
The event that caused the generation of a partial record. This field is mandatory in case of partial records.
guaranteedBitrate - M 0x9F 46 ENUMERATED
(1)
The bit-rate the UMTS bearer service shall guarantee to the user or application. This field may be used to facilitate admission control based on available resources, and for resource allocation within UMTS. Shall only be present for UMTS data connections.
maximumBitrate - M 0x9F 47 ENUMERATED
(1)
The maximum bit-rate that can be used to make code reservations in the downlink of the radio interface. Its purpose is: 1) to limit the delivered bit-rate to applications or external networks with such limitations, 2) to allow maximum wanted user bit-rate to be defined for applications able to operate with different rates (e.g. applications with adapting codecs). Shall only be present for UMTS data connections.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 54 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
modemType - - 0x9F 81 0B
ENUMERATED
(1)
The type of Modem used. It is not available in the forwarding record.
classmark3 O O 0x9F 81 0C
OCTET(2) The mobile station classmark 3.
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
originalCalledNumber M M 0x9F 81 0E
ADRESS (2..17) The address of original called party.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
calledChargeAreaCode - - 0x9F 81 12
OCTET(1..3) The called party logical area for distance charge.
mscOutgoingCircuit O O 0x9F 81 26
INTEGER()1..2 The CIC, only present in case of outgoing bear type being TDM.
orgRNCorBSCId O O 0x9F 81 27
OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A
OCTET(1) The EMLPP priority of the call. See 29.002.
callerDefaultEmlppPriority O O 0x9F 81 2B
OCTET(1) The priority of the EMLPP service registered by the calling party. See 29.002.
eaSubscriberInfo - - 0x9F 81 2E
OCTET(3) The calling subscriber's information of Equal Access. This field is not available in the forwarding record.
selectedCIC - - 0x9F 81 2F
OCTET(3) The selected code of Carrier identification. This field is not available in the forwarding record.
optimalRoutingFlag - - 0x9F 81 31
NULL Shall be present when the optimal routing function is applied. Reserved for future use.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 55 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
optimalRoutingLateForwardFlag
- - 0x9F 81 32
NULL Shall be present when the optimal routing function is applied in the case of the late forward. Reserved for future use.
optimalRoutingEarlyForwardFlag
- - 0x9F 81 33
NULL Shall be present when the optimal routing function is applied in the case of the early forward. Reserved for future use.
portedflag - - 0x9F 81 34
ENUMERATED
(1)
Indicates whether the user is ported. Reserved for future use.
calledIMSI O O 0x9F 81 35
TBCD(3..8) The IMSI of the forwarded-to party.
globalAreaID O O 0x9F 81 3C
OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
changeOfglobalAreaID O O 0xBF 81 3D
SEQUENCE OF
(22 * n)
A list of changes in the GCI / SAI each time-stamped.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
firstmccmnc O O 0x9F 81 40
OCTET(3) The MCC and MNC of the network when the call is initiated.
intermediatemccmnc - - 0x9F 81 41
OCTET(3) Reserved for future use.
lastmccmnc O O 0x9F 81 42
OCTET(3) The MCC and MNC of the network when the call is served. Only present after handover.
cUGOutgoingAccessIndicator O O 0x9F 81 43
ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44
OCTET(4) Network code + CUG interlock
cUGOutgoingAccessUsed O O 0x9F 81 45
ENUMERATED
(1)
Indicates whether the calling party and called party are in the same CUG group.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 56 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
cUGIndex O O 0x9F 81 46
OCTET(2) The index of the CUG subscribers.
interactionWithIP O O 0x9F 81 47
NULL (0) In the case of interaction between SSP and IP, GsmSCF play announcement to SSP and start charging.
hotBillingTag O O 0x9F 81 48
INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
voiceIndicator O O 0x9F 81 4B
ENUMERATED
(1)
Indicates that the announcement is played for the local office or other offices when the call is released.
bCategory C C 0x9F 81 4C
ENUMERATED
(1)
Indicates whether the called party is busy or idle.
callType C C 0x9F 81 4D
ENUMERATED
(1)
Indicates the call type, such as the intra-office, incoming, outgoing, tandem, or unknown.
groupCallType O O 0x9F 81 50
ENUMERATED(1) The type of a group call.
groupCallReference O O 0x9F 81 51
OCTET(4) The reference number of a group call.
uus1Type O O 0x9F 81 52
ENUMERATED(1) The type of UUS1.
eCategory O O 0x9F 81 57
INTEGER(1..2) The enhanced subscriber category.
disconnectparty O O 0x9F 81 5A
ENUMERATED(1) The party who releases the call first.
csReference O O 0x9F 81 5C
OCTET(1..8) The call segment reference number.
csaReference O O 0x9F 81 5D
INTEGER (1..4) The call segment association reference number.
camelphase O O 0x9F 81 5E
ENUMERATED(1) The CAMEL version number.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 57 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G TAG TYPE Description
networkOperatorId O O 0x9F 81 5F
OCTET(1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60
ENUMERATED(1) The type of roaming subscriber.
audioDataType O O 0x9F 81 61
ENUMERATED(1) Indicates whether the data service or speech service is employed by a subscriber.
usertype O O 0x9F 81 63
ENUMERATED(1) The user type.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C
PartyRelCause Indicates the cause of call release.
cARP O O 0x9F 81 76
INTEGER(1) The CARP value registered by the subscriber.
redirectingcounter O O 0x9F 82 11
INTEGER(1) Times of call forwarding.
2.4 Mobile Terminated Call AttemptIf the generation of these records is enabled, an MTC record shall be created for each incoming call attempt made for a mobile station. The MTC records shall be produced in the terminating MSC. Table 2-1 lists the formats of MTC records.
Table 2-1 MTC record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Mobile Terminated. CallEventRecordType = 0x01
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the called party.
servedIMEI O O 0x82 TBCD(8) The IMEI of the called mobile equipment if available.
servedMSISDN M M 0x83 ADRESS(2..9) The primary MSISDN of the called party.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 58 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
callingNumber O O 0x84 ADRESS(2..17) The number of the calling party if available.
connectedNumber O O 0x85 ADRESS(2..17) Only relevant in case of call forwarding where the forwarded-to number is recorded.
recordingEntity M M 0x86 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xA7 IA5(1..32) The MSC route on which the call is originated at the forwarding MSC.
mscOutgoingROUTE M M 0xA8 IA5(1..32) The route on which the call left the MSC, usually to the BSC or RNC.
location M M 0xA9 OCTET(8) The identity of the cell or the SAC at the time of CDR creation.
changeOfLocation O O 0xAA SEQUENCE OF
( 23 * n )
A list of changes in Location Area Code / Cell Identifier each time-stamped.
basicService M M 0xAB OCTET(3) The bearer or teleservice employed.
transparencyIndicator O O 0x8C ENUMERATED
(1)
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent modes.
changeOfService - - 0xAD SEQUENCE OF
( (18..27) * n)
A list of changes of basic service during a connection each time-stamped.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 59 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
supplServicesUsed O O 0xAE SEQUENCE OF
(16 * n)
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked.
aocParameters O O 0xAF OCTET(4..28) The charge advice parameters sent to the MS on call setup.
changeOfAOCParms O O 0xB0 SEQUENCE OF
( 43 * n)
The new AOC parameters sent to the MS e.g. as a result of a tariff switchover, including the time at which the new set was applied.
msClassmark M M 0x91 OCTET(2..3) The mobile station classmark employed on call setup.
changeOfClassmark O O 0xB2 OCTET (16 ) A list of changes to the classmark during the connection each time-stamped
setupTime C C 0x9F 81 4B OCTET(9) The time stamp when the Setup message or IAM message is received from the calling party side.
seizureTime C C 0x93 OCTET(9) The time stamp when the assignment at the called party side is completed.
alertingTime C C 0x9F 81 4C OCTET(9) The time stamp when the Alerting message or ACM message is received from the called party side.
answerTime M M 0x94 OCTET(9) The time stamp when the call is answered during a successful connection.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 60 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
releaseTime M M 0x95 OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x96 INTEGER(1..2) The chargeable duration of the connection for successful calls, the holding time of call attempts.
radioChanRequested M - 0x98 ENUMERATED
(1)
The type of radio traffic channel (full-rate or half-rate) requested by the MS.
radioChanUsed M - 0x99 ENUMERATED
(1)
The type of radio channel actually used (full-rate or half-rate).
changeOfRadioChan O - 0xBA OCTET (14..17 ) A list of changes to the types of radio traffic channels each time-stamped.
causeForTerm M M 0x9B INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xBC INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x9D OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
sequenceNumber O O 0x9E INTEGER(1) The partial record sequence number, only present in case of partial records.
additionalChgInfo M M 0xBF 1F SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 61 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
recordExtensions - - 0xBF 20 SET OF (11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
networkCallReference M M 0x9F 21 OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
mSCAddress M M 0x9F 22 ADRESS(2..9) The E.164 number assigned to the MSC that generated the network call reference.
fnur O O 0x9F 26 ENUMERATED
(1)
The user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections.
aiurRequested O O 0x9F 27 ENUMERATED
(1)
The total Air Interface User Rate Requested by the MS at call setup. Shall only be present for non-transparent HSCSD connections.
speechVersionSupported M - 0x9F 2A OCTET(1) The speech version supported by the MS with highest priority indicated by MS.
speechVersionUsed M - 0x9F 2B OCTET(1) The speech version used for that call.
gsm-SCFAddress O O 0x9F 2C ADRESS(2..9) The CAMEL server serving the subscriber. Shall be present only if CAMEL is applied.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 62 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
serviceKey O O 0x9F 2D INTEGER(1..4) The CAMEL service logic to be applied. Shall be present only if CAMEL is applied.
systemType M M 0x9F 2E ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
rateIndication O O 0x9F 2F OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008.
partialRecordType O O 0x9F 36 ENUMERATED
(1)
The event that caused the generation of a partial record. This field is mandatory in case of partial records.
guaranteedBitrate - M 0x9F 37 ENUMERATED
(1)
The bit-rate the UMTS bearer service shall guarantee to the user or application. This field may be used to facilitate admission control based on available resources, and for resource allocation within UMTS. Shall only be present for UMTS data connections.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 63 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
maximumBitrate - M 0x9F 38 ENUMERATED
(1)
The maximum bit-rate that can be used to make code reservations in the downlink of the radio interface. Its purpose is: 1) to limit the delivered bit-rate to applications or external networks with such limitations, 2) to allow maximum wanted user bit-rate to be defined for applications able to operate with different rates (e.g. applications with adapting codecs). Shall only be present for UMTS data connections.
initialCallAttemptFlag O O 0x9F 81 09 NULL(0) Indicates whether the call is set up through the Initial Call Attempt (ICA) operation sent by the SCP.
ussdCallBackFlag O O 0x9F 81 0A NULL(0) Indicates that the call is set up when a CAMEL subscriber roaming outside the HPLMN uses the UCB service.
modemType O O 0x9F 81 0B ENUMERATED
(1)
The type of Modem used.
classmark3 O O 0x9F 81 0C OCTET(2) The mobile station classmark 3.
chargedParty M M 0x9F 81 0D ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
originalCalledNumber O O 0x9F 81 0E ADRESS(2..17) The address of original called party.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 64 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
calledChargeAreaCode - - 0x9F 81 12 OCTET(1..3) The called party logical area for distance charge.
defaultCallHandling O O 0x9F 81 16 ENUMERATED
(1)
Indicates whether a CAMEL call encounters default call handling. This field shall be present only if default call handling has been applied.
freeFormatData O O 0x9F 81 17 OCTET(1..160) This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for the second service.
freeFormatDataAppend O O 0x9F 81 18 BOOLEAN(1) Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR.
numberOfDPEncountered O O 0x9F 81 19 INTEGER(1) Number that counts how often armed detection points (TDP and EDP) were encountered. Shall be present only if CAMEL is applied.
levelOfCAMELService O O 0x9F 81 1A BIT STRING(2) The indicator for the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied.
roamingNumber M M 0x9F 81 20 ADRESS(2..17) The Mobile Station Roaming Number employed to route this connection.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 65 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
mscIncomingCircuit O O 0x9F 81 26 INTEGER(1..2) The CIC, only present in case of incoming bear type being TDM.
orgRNCorBSCId M M 0x9F 81 27 OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A OCTET(1) The EMLPP priority of the call. See 29.002.
calledDefaultEmlppPriority O O 0x9F 81 2B OCTET(1) The priority of the EMLPP service registered by the calling party. See 29.002.
eaSubscriberInfo - - 0x9F 81 2E OCTET(3) The calling subscriber's information of Equal Access. This field is not available in the MTC record.
selectedCIC - - 0x9F 81 2F OCTET(3) The selected code of Carrier identification. This field is not available in the MTC record.
optimalRoutingFlag - - 0x9F 81 31 NULL Shall be present when the optimal routing function is applied. Reserved for future use.
portedflag - - 0x9F 81 34 ENUMERATED
(1)
Indicates whether the user is ported. Reserved for future use.
globalAreaID M M 0x9F 81 3C OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
changeOfglobalAreaID O O 0xBF 81 3D SEQUENCE
OF (22 * n)
A list of changes in the GCI / SAI each time-stamped.
subscriberCategory M M 0x9F 81 3E OCTET(1) The category of subscribers.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 66 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
firstmccmnc M M 0x9F 81 40 OCTET(3) The MCC and MNC of the network when the call is initiated.
intermediatemccmnc - - 0x9F 81 41 OCTET(3) Reserved for future use.
lastmccmnc O O 0x9F 81 42 OCTET(3) The MCC and MNC of the network when the call is served. Only present after handover.
cUGOutgoingAccessIndicator O O 0x9F 81 43 ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44 OCTET(4) Network code + CUG interlock
cUGIncomingAccessUsed O O 0x9F 81 45 ENUMERATED
(1)
Indicates whether the calling party and called party are in the same CUG group.
cUGIndex O O 0x9F 81 46 OCTET(2) The index of the CUG subscribers.
hotBillingTag O O 0x9F 81 48 INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
redirectingnumber O O 0x9F 81 49 ADRESS(2..17) The MSISDN of the forwarding party.
redirectingcounter O O 0x9F 81 4A INTEGER(1) The number of times of call forwarding.
calledNumber C C 0x9F 81 4D ADRESS(2..17) The address of the called party e.g. the number dialed by the calling party.
voiceIndicator O O 0x9F 81 4E ENUMERATED
(1)
Indicates that the announcement is played for the local office or other offices when the call is released.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 67 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
bCategory M M 0x9F 81 4F ENUMERATED
(1)
Indicates whether the called party is busy or idle.
callType M M 0x9F 81 50 ENUMERATED
(1)
Indicates the call type, such as the intra-office, incoming, outgoing, tandem, or unknown.
groupCallType O O 0x9F 81 53 ENUMERATED(1)
The type of a group call.
groupCallReference O O 0x9F 81 54 OCTET(4) The reference number of a group call.
uus1Type O O 0x9F 81 55 ENUMERATED(1)
The type of UUS1.
eCategory O O 0x9F 81 57 INTEGER(1..2) The enhanced subscriber category.
tariffCode O O 0x9F 81 59 INTEGER(1) The tariff code.
disconnectparty O O 0x9F 81 5A ENUMERATED(1)
The party who releases the call first.
csReference O O 0x9F 81 5C OCTET(1..8) The call segment reference number.
csaReference O O 0x9F 81 5D INTEGER (1..4) The call segment association reference number.
networkOperatorId O O 0x9F 81 5F OCTET(1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60 ENUMERATED(1)
The type of roaming subscriber.
audioDataType O O 0x9F 81 61 ENUMERATED(1)
Indicates whether the data service or speech service is employed by a subscriber.
usertype O O 0x9F 81 63 ENUMERATED(1)
The user type.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C PartyRelCause Indicates the cause of call release.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 68 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
translatedNumber O O 0x9F 81 75 ADRESS (2..17) The called number after digit translation within the MSC (if applicable).
zoneCode O O 0x9F 81 70 OCTET (2) The zone code of a cell.
cARP O O 0x9F 81 76 INTEGER(1) The CARP value registered by the subscriber.
2.5 Roaming Call AttemptIf the generation of these records is enabled, a roaming record shall be created for each call redirected to a mobile subscriber roaming outside the HPLMN. These roaming records shall be produced in the GMSC of the roaming subscriber's HPLMN. Table 2-1 lists the formats of roaming call attempt records.
Table 2-1 Roaming record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Roaming record. CallEventRecordType = 0x02
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the called (roaming) party.
servedMSISDN M M 0x82 ADRESS(2..9) The MSISDN of the called (roaming) party.
Calling Number O O 0x83 ADRESS(2..17) The address of the calling party, if available.
roamingNumber M M 0x84 ADRESS(2..17)
The Mobile Station Roaming Number employed to route this connection.
recordingEntity M M 0x85 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xA6 IA5(1..32) The incoming GMSC route on which the call is originated.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 69 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
mscOutgoingROUTE M M 0xA7 IA5(1..32) The route on which the call left the GMSC.
basicService M M 0xA8 OCTET(3) The bearer or teleservice employed.
transparencyIndicator O O 0x89 ENUMERATED
(1)
Indicates whether the basic service was used in transparent or non-transparent mode. This parameter is provided only for those basic services which may be employed in both transparent and non-transparent modes.
changeOfService O O 0xAA SEQUENCE OF
( (18..27) * n)
A list of changes of basic service during a connection each time-stamped.
supplServicesUsed O O 0xAB SEQUENCE OF
(16 * n)
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked.
seizureTime - - 0x8C OCTET(9) The time of incoming traffic channel seizure (for unsuccessful call attempts). At present, it is not available.
answerTime M M 0x8D OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x8E OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x8F INTEGER(1..2)
The chargeable duration of the connection for successful calls, the holding time for call attempts.
causeForTerm M M 0x91 INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xB2 INTEGER(4) A more detailed reason for the release of the connection.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 70 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
callReference M M 0x93 OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
sequenceNumber O O 0x94 INTEGER(1) The partial record sequence number, only present in case of partial records.
recordExtensions - - 0xB5 SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
networkCallReference M M 0x96 OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
mSCAddress M M 0x97 ADRESS(2..9) The E.164 number assigned to the MSC that generated the network call reference.
partialRecordType O O 0x9E ENUMERATED
(1)
The event (time limit etc.) that caused the generation of a partial record. This field is mandatory in case of partial records.
additionalChgInfo M M 0xBF 81 05
SEQUENCE(3)
Charge/no charge indicator and additional charging parameters, when available.
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling subscriber or the called subscriber is charged for the call.
originalCalledNumber O O 0x9F 81 0E
ADRESS(2..17) The address of original called party.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
calledChargeAreaCode - - 0x9F 81 12
OCTET(1..3) The called party logical area for distance charge. Reserved for future use.
mscOutgoingCircuit O O 0x9F 81 26
INTEGER(1..2)
This field indicates the CIC, only present in case of outgoing bear type being TDM.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 71 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
mscIncomingCircuit O O 0x9F 81 27
INTEGER(1..2)
This field indicates the CIC, only present in case of incoming bear type being TDM.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A
OCTET(1) The EMLPP priority of the call. See 29.002.
eaSubscriberInfo - - 0x9F 81 2E
OCTET(3) The calling subscriber's information of Equal Access. This field is not used in ROAM.
selectedCIC - - 0x9F 81 2F
OCTET(3) The selected code of Carrier identification. This field is not used in ROAM.
optimalRoutingFlag - - 0x9F 81 31
NULL Shall be present when the optimal routing function is applied. Reserved for future use.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
cUGOutgoingAccessIndicator O O 0x9F 81 43
ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44
OCTET(4) Network code + CUG interlock
hotBillingTag O O 0x9F 81 48
INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. It is available only when the hot charging function is applied.
eCategory O O 0x9F 81 57
INTEGER(1..2) The enhanced subscriber category.
gsm-SCFAddress O O 0x9F 81 58
ADRESS(2..9) The CAMEL server serving the subscriber. Shall be present only if CAMEL is applied.
serviceKey O O 0x9F 81 59
INTEGER(1..4) The CAMEL service logic to be applied. Shall be present only if CAMEL is applied.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 72 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
levelOfCAMELService O O 0x9F 81 5A
BIT STRING(2)
The indicator for the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied.
networkOperatorId O O 0x9F 81 5F
OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60
ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C
PartyRelCause Indicates the cause of call release.
translatedNumber O O 0x9F 81 75
ADRESS (2..17)
The called number after digit translation within the MSC (if applicable).
2.6 Incoming Gateway Call AttemptIf the generation of these records is enabled, an incoming gateway record shall be created for each incoming call attempt received by a gateway MSC from another network. These records, produced in the gateway MSC, may be used to settle accounts with other networks. The generation of gateway records shall not be influenced by the production of MTC records i.e. even if the GMSC and terminating MSC are co-located a gateway record shall still be produced. Table 2-1 lists the formats of incoming gateway call attempt records.
Table 2-1 Incoming gateway record
Field 2G
3G
TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Incoming gateway record. CallEventRecordType = 0x03
callingNumber O O 0x81 ADRESS(2..17) The number of the calling party if available at this node.
calledNumber M M 0x82 ADRESS(2..17) The address of the called party as seen by the GMSC. This is the number employed by the GMSC for routing.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 73 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
recordingEntity M M 0x83 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xA4 IA5(1..32) The incoming GMSC route on which the call is originated.
mscOutgoingROUTE M M 0xA5 IA5(1..32) The route on which the call left the GMSC.
setupTime C C 0x9F 81 49 OCTET(9) The time stamp when the Setup message or IAM message is received from the calling party side.
seizureTime O O 0x86 OCTET(9) The time stamp when the assignment at the called party side is completed.
alertingTime C C 0x9F 81 4A
OCTET(9) The time stamp when the Alerting message or ACM message is received from the called party side.
answerTime M M 0x87 OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x88 OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x89 INTEGER(1..2) The accountable duration (answer -> release of incoming trunk) of the connection if successful.
causeForTerm M M 0x8B INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xAC INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x8D OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 74 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
sequenceNumber O O 0x8E INTEGER(1) The partial record sequence number, only present in case of partial records.
recordExtensions - - 0xAF SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
partialRecordType O O 0x96 ENUMERATED
(1)
The event (time limit etc.) that caused the generation of a partial record. This field is mandatory in case of partial records.
iSDN-BC O O 0x97 OCTET(1..12) Present if this parameter is signaled back from the VMSC to the GMSC in the access transport parameter of the Answer message (ANM), see TS 29.007.
lLC O O 0x98 OCTET(1..18) Present if this parameter is signaled back from the VMSC to the GMSC in the access transport parameter of the Answer message (ANM), see TS 29.007.
hLC O O 0x99 OCTET(1..12) Present if this parameter is signaled back from the VMSC to the GMSC in the access transport parameter of the Answer message (ANM), see TS 29.007.
basicService M M 0xBF 81 02 OCTET(3) The bearer or teleservice employed.
additionalChgInfo M M 0xBF 81 05 SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
chargedParty - - 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
originalCalledNumber O O 0x9F 81 0E ADRESS(2..17) The address of original called party.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 75 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
rateIndication O O 0x9F 81 1F OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
roamingNumber O O 0x9F 81 20 ADRESS(2..17) The Mobile Station Roaming Number employed to route this connection.
mscIncomingCircuit M O 0x9F 81 27 INTEGER(1..2) This field indicates the CIC, only present in case of incoming bear type being TDM.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A
OCTET(1) The EMLPP priority of the call. See 29.002.
eaSubscriberInfo O O 0x9F 81 2E OCTET(3) The calling subscriber's information of Equal Access.
selectedCIC O O 0x9F 81 2F OCTET(3) The selected code of Carrier identification.
subscriberCategory M M 0x9F 81 3E OCTET(1) The category of subscribers.
cUGOutgoingAccessIndicator O O 0x9F 81 43 ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44 COTET(4) Network code + CUG interlock
cUGIncomingAccessUsed O O 0x9F 81 45 ENUMERATED
(1)
Indicates whether the calling party and called party are in the same CUG group.
mscIncomingRouteAttribute O O 0x9F 81 46 ENUMERATED
(1)
The attribute of incoming routes.
mscOutgoingRouteAttribute O O 0x9F 81 47 ENUMERATED
(1)
The attribute of outgoing routes.
networkCallReference M M 0x9F 81 48 OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 76 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
voiceIndicator O O 0x9F 81 4B ENUMERATED
(1)
Indicates that the announcement is played for the local office or other offices when the call is released.
bCategory C C 0x9F 81 4C ENUMERATED
(1)
Indicates whether the called party is busy or idle.
callType C C 0x9F 81 4D
ENUMERATED
(1)
Indicates the call type, such as the intra-office, incoming, outgoing, tandem, or unknown.
disconnectparty O O 0x9F 81 5A
ENUMERATED(1)
The party who releases the call first.
networkOperatorId O O 0x9F 81 5F OCTET (1) The ID of virtual operators.
audioDataType O O 0x9F 81 61 ENUMERATED(1)
Indicates whether the data service or speech service is employed by a subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C
PartyRelCause Indicates the cause of call release.
servedIMSI O O 0x9F 81 6F TBCD(3..8) The IMSI of the called party.
translatedNumber O O 0x9F 81 75 ADRESS (2..17) The called number after digit translation within the MSC (if applicable).
location O O 0xBF 81 77 OCTET(8) The identity of the cell or the SAC at the time of CDR creation, including the location area code.
changeOfLocation O O 0xBF 81 78 SEQUENCE OF ( 23 * n )
A list of changes in Location Area Code / Cell Identifier each time-stamped.
firstmccmnc O O 0x9F 81 79 OCTET(3) The MCC and MNC of the network when the call is initiated.
lastmccmnc O O 0x9F 81 7A
OCTET(3) The MCC and MNC of the network when the call is served. Only present after handover.
redirectingnumber O O 0x9F 82 10 ADRESS(2..17) The MSISDN of the forwarding party.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 77 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
redirectingcounter O O 0x9F 82 11 INTEGER(1) Times of call forwarding.
2.7 Outgoing Gateway Call AttemptIf the generation of these records is enabled, an outgoing gateway record shall be created for each outgoing call attempt from a gateway MSC to another network. These records, produced in the gateway MSC, may be used to settle accounts with other networks. The generation of gateway records shall not be influenced by the production of MOC records i.e. even if the GMSC and originating MSC are co-located a gateway record shall still be produced. Table 2-1 lists the formats of outgoing gateway call attempt records.
Table 2-1 Outgoing gateway record
Field 2G
3G
TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Outgoing gateway record. CallEventRecordType = 0x04
callingNumber O O 0x81 ADRESS(2..17)
The number of the calling party if available at this node.
calledNumber M M 0x82 ADRESS(2..17)
The address of the called party as seen by the GMSC. This is the number employed by the GMSC for routing.
recordingEntity M M 0x83 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xA4 IA5(1..32) The incoming GMSC route on which the call is originated.
mscOutgoingROUTE M M 0xA5 IA5(1..32) The route on which the call left the GMSC.
setupTime C C 0x9F 81 49 OCTET(9) The time stamp when the Setup message or IAM message is received from the calling party side.
seizureTime O O 0x86 OCTET(9) The time stamp when the assignment at the calling party side is completed.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 78 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
alertingTime C C 0x9F 81 4A OCTET(9) The time stamp when the Alerting message or ACM message is received from the called party side.
answerTime M M 0x87 OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x88 OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x89 INTEGER(1..2)
The accountable duration (answer -> release of incoming trunk) of the connection if successful.
causeForTerm M M 0x8B INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xAC INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x8D OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
sequenceNumber O O 0x8E INTEGER(1) The partial record sequence number, only present in case of partial records.
recordExtensions - - 0xAF SET OF (11*n )
A set of network or manufacturer specific extensions to the record. Reserved for future use.
partialRecordType O O 0x96 ENUMERATED
(1)
The event (time limit etc.) that caused the generation of a partial record. This field is mandatory in case of partial records.
basicService M M 0xBF 81 02 OCTET(3) The bearer or teleservice employed.
additionalChgInfo M M 0xBF 81 05 SEQUENCE(3)
Charge/no charge indicator and additional charging parameters, when available.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 79 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
chargedParty - - 0x9F 81 0D ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
originalCalledNumber O O 0x9F 81 0E ADRESS(2..17)
The address of original called party.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
rateIndication O O 0x9F 81 1F OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008.
roamingNumber O O 0x9F 81 20 ADRESS(2..17)
The Mobile Station Roaming Number employed to route this connection.
mscOutgoingCircuit M O 0x9F 81 26 INTEGER(1..2)
This field indicates the CIC, only present in case of outgoing bear type being TDM.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A OCTET(1) The EMLPP priority of the call. See 29.002.
eaSubscriberInfo O O 0x9F 81 2E OCTET(3) The calling subscriber's information of Equal Access.
selectedCIC O O 0x9F 81 2F OCTET(3) The selected code of Carrier identification.
subscriberCategory M M 0x9F 81 3E OCTET(1) The category of subscribers.
cUGOutgoingAccessIndicator O O 0x9F 81 43 ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44 OCTET(4) Network code + CUG interlock
cUGIncomingAccessUsed O O 0x9F 81 45 ENUMERATED
(1)
Indicates whether the calling party and called party are in the same CUG group.
mscIncomingRouteAttribute O O 0x9F 81 46 ENUMERATED
(1)
The attribute of incoming routes.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 80 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
mscOutgoingRouteAttribute O O 0x9F 81 47 ENUMERATED
(1)
The attribute of outgoing routes.
networkCallReference M M 0x9F 81 48 OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
voiceIndicator O O 0x9F 81 4B ENUMERATED
(1)
Indicates that the announcement is played for the local office or other offices when the call is released.
bCategory C C 0x9F 81 4C ENUMERATED
(1)
Indicates whether the called party is busy or idle.
callType C C 0x9F 81 4D ENUMERATED
(1)
Indicates the call type, such as the intra-office, incoming, outgoing, tandem, or unknown.
disconnectparty O O 0x9F 81 5A ENUMERATED(1)
The party who releases the call first.
networkOperatorId O O 0x9F 81 5F OCTET (1) The ID of virtual operators.
audioDataType O O 0x9F 81 61 ENUMERATED(1)
Indicates whether the data service or speech service is employed by a subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C PartyRelCause Indicates the cause of call release.
translatedNumber O O 0x9F 81 75 ADRESS (2..17)
The called number after digit translation within the MSC (if applicable).
location O O 0xBF 81 77 OCTET(8) The identity of the cell or the SAC at the time of CDR creation, including the location area code.
changeOfLocation O O 0xBF 81 78 SEQUENCE OF ( 23 * n )
A list of changes in Location Area Code / Cell Identifier each time-stamped.
firstmccmnc O O 0x9F 81 79 OCTET(3) The MCC and MNC of the network when the call is initiated.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 81 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G
3G
TAG TYPE Description
lastmccmnc O O 0x9F 81 7A OCTET(3) The MCC and MNC of the network when the call is served. Only present after handover.
redirectingnumber O O 0x9F 82 10 ADRESS(2..17)
The MSISDN of the forwarding party.
redirectingcounter O O 0x9F 82 11 INTEGER(1) Times of call forwarding.
2.8 Transit Call AttemptIf the generation of these records is enabled, a transit record may be generated for each incoming call attempt received by a Transit MSC i.e. neither originating nor terminating. For the avoidance of doubt, a transit record shall only be produced if no MOC or MTC record is produced for this call attempt. The transit records, produced in the TMSC, may be used to record traffic from particular origins or to particular destinations. Table 2-1 lists the formats of transit call attempt records.
Table 2-1 Transit record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Transit record. CallEventRecordType = 0x05
recordingEntity M M 0x81 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
mscIncomingROUTE M M 0xA2 IA5(1..32) The TMSC route on which the call is originated.
mscOutgoingROUTE M M 0xA3 IA5(1..32) The route on which the call left the TMSC.
callingNumber O O 0x84 ADRESS(2..17)
The number of the calling party if available at this node.
calledNumber M M 0x85 ADRESS(2..17)
The address of the called party as seen by the TMSC.
isdnBasicService O O 0x86 OCTET(1) The ISDN basic service employed.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 82 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
setupTime C C 0x9F 81 49
OCTET(9) The time stamp when the Setup message or IAM message is received from the calling party side.
seizureTime - - 0x87 OCTET(9) The time stamp of incoming trunk seizure for unsuccessful call attempts. It is not available at present.
alertingTime C C 0x9F 81 4A
OCTET(9) The time stamp when the Alerting message or ACM message is received from the called party side.
answerTime M M 0x88 OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x89 OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x8A INTEGER(1..2)
The chargeable duration of the connection if successful.
causeForTerm M M 0x8C INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xAD INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x8E OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
sequenceNumber O O 0x8F INTEGER(1) The partial record sequence number, only present in case of partial records.
recordExtensions - - 0xB0 SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 83 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
partialRecordType O O 0x97 ENUMERATED
(1)
The event (time limit etc.) that caused the generation of a partial record. This field is mandatory in case of partial records.
basicService M M 0xBF 81 02
OCTET(3) The bearer or teleservice employed.
additionalChgInfo M M 0xBF 81 05
SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
originalCalledNumber O O 0x9F 81 0E
ADRESS(2..17)
The address of original called party.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
rateIndication O O 0x9F 81 1F
OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008.
roamingNumber O O 0x9F 81 20
ADRESS(2..17)
The Mobile Station Roaming Number employed to route this connection.
mscOutgoingCircuit M O 0x9F 81 26
INTEGER(1..2)
This field indicates the CIC, only present in case of outgoing bear type being TDM.
mscIncomingCircuit M O 0x9F 81 27
INTEGER(1..2)
This field indicates the CIC, only present in case of incoming bear type being TDM.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
callEmlppPriority O O 0x9F 81 2A
OCTET(1) The EMLPP priority of the call. See 29.002.
eaSubscriberInfo O O 0x9F 81 2E
OCTET(3) The calling subscriber's information of Equal Access.
selectedCIC O O 0x9F 81 2F
OCTET(3) The selected code of Carrier identification.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 84 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
cUGOutgoingAccessIndicator O O 0x9F 81 43
ENUMERATED
(1)
The access indicator of the CUG call.
cUGInterlockCode O O 0x9F 81 44
OCTET(4) Network code + CUG interlock
cUGIncomingAccessUsed O O 0x9F 81 45
ENUMERATED
(1)
Indicates whether the calling party and called party are in the same CUG group.
mscIncomingRouteAttribute O O 0x9F 81 46
ENUMERATED
(1)
The attribute of incoming routes.
mscOutgoingRouteAttribute O O 0x9F 81 47
ENUMERATED
(1)
The attribute of outgoing routes.
networkCallReference M M 0x9F 81 48
OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
voiceIndicator O O 0x9F 81 4B
ENUMERATED
(1)
Indicates that the announcement is played for the local office or other offices when the call is released.
bCategory C C 0x9F 81 4C
ENUMERATED
(1)
Indicates whether the called party is busy or idle.
callType C C 0x9F 81 4D
ENUMERATED
(1)
Indicates the call type, such as the intra-office, incoming, outgoing, tandem, or unknown.
disconnectparty O O 0x9F 81 5A
ENUMERATED(1)
The party who releases the call first.
networkOperatorId O O 0x9F 81 5F
OCTET (1) The ID of virtual operators.
audioDataType O O 0x9F 81 61
ENUMERATED(1)
Indicates whether the data service or speech service is employed by a subscriber.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 85 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
partyRelCause O O 0xBF 81 6C
PartyRelCause Indicates the cause of call release.
translatedNumber O O 0x9F 81 75
ADRESS (2..17)
The called number after digit translation within the MSC (if applicable).
cmnFlag O O 0x9F 81 7B
ENUMERATED(1)
Indicates whether the CMN call is invoked.
redirectingnumber O O 0x9F 82 10
ADRESS(2..17)
The MSISDN of the forwarding party.
redirectingcounter O O 0x9F 82 11
INTEGER(1) Times of call forwarding.
2.9 Short Message Service, Mobile OriginatedIf the generation of these records is enabled, an SMS-MO record shall be produced, within the originating MSC, for each short message sent by a mobile subscriber. Table 2-1 lists the formats of SMS-MO records.
Table 2-1 SMS-MO record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
SMS-Mobile originated record. CallEventRecordType = 0x06
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the subscriber sending the short message.
servedIMEI O O 0x82 TBCD(8) The IMEI of the ME sending the message, if available.
servedMSISDN M M 0x83 ADRESS(2..9) The primary MSISDN of the subscriber sending the message.
msClassmark M M 0x84 OCTET(2..3) The mobile station classmark.
serviceCentre M M 0x85 ADRESS(2..9) The E.164 address of the SMS service center.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 86 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
recordingEntity M M 0x86 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
location M M 0xA7 OCTET(8) The Location Area Code and Cell Identifier from which the message is originated.
messageReference M M 0x88 OCTET (3..8) A reference, provided by the MS uniquely identifying this message.
originationTime M M 0x89 OCTET(9) The time at which the message was received by the MSC from the subscriber.
smsResult O O 0xAA INTEGER (4) The result of the attempted delivery if unsuccessful.
recordExtensions - - 0xAB SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
destinationNumber M M 0x8C ADRESS(2..17)
The destination short message subscriber number.
cAMELSMSInformation O O 0xAD SET (34..58) A set of CAMEL information IEs. Each of these IEs contains information related to CAMEL call leg related for the SMS. Shall be present only if CAMEL is applied.
systemType M M 0x8E ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
basicService M M 0xBF 81 02
OCTET(3) The bearer or teleservice employed.
additionalChgInfo M M 0xBF 81 05
SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 87 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
classmark3 O O 0x9F 81 0C
OCTET(2) The mobile station classmark 3.
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
orgRNCorBSCId M M 0x9F 81 27
OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
globalAreaID M M 0x9F 81 3C
OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40
OCTET(3) Indicates the MCC and MNC of the network where the SMS is initiated.
smsUserDataType M M 0x9F 81 43
OCTET(1) Indicates the user data type, such as the normal SM, picture, or text.
smstext O O 0x9F 81 44
OCTET(1..160) Indicates the content of a short message.
maximumNumberOfSMSInTheConcatenatedSMS
O O 0x9F 81 45
INTEGER(1) Indicates the maximum of the concatenated short messages.
concatenatedSMSReferenceNumber
O O 0x9F 81 46
INTEGER(1..2)
Indicates the reference number of the concatenated short messages.
sequenceNumberOfTheCurrentSMS
O O 0x9F 81 47
INTEGER(1) Indicates the sequence of the current concatenated short message, such as 1, 2, … maximum Number Of SMS In The Concatenated SMS.
hotBillingTag O O 0x9F 81 48
INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 88 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
callReference M M 0x9F 81 49
OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
tariffCode O O 0x9F 81 4A
INTEGER(1) The tariff code.
networkOperatorId O O 0x9F 81 5F
OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60
ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
zoneCode O O 0x9F81 70 OCTET (2) The zone code of a cell.
2.10 Short Message Service, Mobile Terminated
If the generation of these records is enabled, an SMS-MT record shall be produced, within the terminating MSC, for each short message received by a mobile subscriber. Table 2-1 lists the formats of SMS-MT records.
Table 2-1 SMS-MT record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
SMS-Mobile Terminated record. CallEventRecordType = 0x07
serviceCentre M M 0x81 ADRESS(2..9) The E.164 address of the SMS service center.
servedIMSI M M 0x82 TBCD(3..8) The IMSI of the receiving party.
servedIMEI O O 0x83 TBCD(8) The IMEI of the receiving party, if available.
servedMSISDN M M 0x84 ADRESS(2..9) The MSISDN of the receiving party.
msClassmark M M 0x85 OCTET(2..3) The mobile station classmark.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 89 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
recordingEntity M M 0x86 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
location M M 0xA7 OCTET(8) The Location Area Code and Cell Identifier to which the message was delivered.
deliveryTime M M 0x88 OCTET(9) Delivery time stamp, time at which message was sent to the MS by the MSC.
smsResult O O 0xA9 INTEGER(4) The result of the attempted delivery if unsuccessful.
recordExtensions - - 0xAA SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
systemType M M 0x8B ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
cAMELSMSInformation O O 0xAC SET (34..58) A set of CAMEL information IEs. Each of these IEs contains information related to CAMEL call leg related for the SMS.
In CAMEL phase 2 or 3, SMS MT CSI is not available in MSC-Server, so that the CAMELSMSInformation is also not available in SMS-MT records.
basicService M M 0xBF 81 02
OCTET(3) The bearer or teleservice employed.
additionalChgInfo M M 0xBF 81 05
SEQUENCE(3)
Charge/no charge indicator and additional charging parameters, when available.
classmark3 O O 0x9F 81 0C
OCTET(2) The mobile station classmark 3.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 90 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
'orgRNCorBSCId M M 0x9F 81 27
OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
globalAreaID M M 0x9F 81 3C
OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40
OCTET(3) Indicates the MCC and MNC of the network where SMS is terminated.
smsUserDataType M M 0x9F 81 43
OCTET(1) Indicates the user data type, such as the normal SM, picture, or text.
smstext O O 0x9F 81 44
OCTET(1..160)
Indicates the content of a short message.
maximumNumberOfSMSInTheConcatenatedSMS
O O 0x9F 81 45
INTEGER(1) Indicates the maximum of the concatenated short messages.
concatenatedSMSReferenceNumber
O O 0x9F 81 46
INTEGER(1..2)
Indicates the reference number of the concatenated short messages.
sequenceNumberOfTheCurrentSMS
O O 0x9F 81 47
INTEGER(1) Indicates the sequence of the current concatenated short message, such as 1, 2, … maximum Number Of SMS In The Concatenated SMS.
hotBillingTag O O 0x9F 81 48
INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 91 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
origination M M 0x9F 81 49
ADRESS(2..17)
The originating short message subscriber number.
callReference M M 0x9F 81 4A
OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
tariffCode O O 0x9F 81 4B
INTEGER(1) The tariff code.
networkOperatorId O O 0x9F 81 5F
OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60
ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
zoneCode O O 0x9F 81 70
OCTET (2) The zone code of a cell.
2.11 Mobile Terminated Location Request (MT-LR)
If the generation of these records is enabled, an LCS-MT record shall be produced, within the visited MSC, for each mobile a terminated location request is performed for. Table 2-1 lists the formats of LCS-MT records.
Table 2-1 LCS-MT record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
LCS-MT record. CallEventRecordType = 0x17
recordingEntity M M 0x81 ADRESS(2..9)
The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
lcsClientType M M 0x82 ENUMERATED
(1)
The type of the LCS client that invoked the LR.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 92 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
lcsClientIdentity M M 0xA3 SEQUENCE
(13..29)
Further identification of the LCS client.
servedIMSI M M 0x84 TBCD(3..8) The IMSI of the subscriber the LR is invoked for.
servedMSISDN M M 0x85 ADRESS(2..9)
The MSISDN of the subscriber the LR is invoked for.
locationType M M 0xA6 SEQUENCE
(6..21)
The type of the location request.
lcsQos O O 0xA7 SEQUENCE
(11)
QoS of the LR, if available.
lcsPriority M M 0x88 OCTET(1) Priority of the LR.
mlc-Number M M 0x89 ADRESS(2..9)
The E.164 address of the requesting GMLC.
eventTimeStamp M M 0x8A OCTET(9) The time at which the LR was received by the MSC.
measureDuration M M 0x8B INTEGER(1..2)
The duration of preceding the location request.
notificationToMSUser M M 0x8C ENUMERATED
(1)
The privacy notification to MS user that was applicable when the LR was invoked, with the result of the notification recorded in the CDR.
privacyOverride O O 0x8D NULL(0) This parameter indicates whether the MS privacy was overridden by the LCS client, if available.
location M M 0xAE OCTET(8) The LAC and CI when the LR is received.
locationEstimate M M 0x8F OCTET(1..20)
The location estimate for the subscriber if contained in geographic position and the LR was successful.
positioningData M M 0x90 OCTET(1..33)
The positioning method used or attempted, if available.
lcsCause O O 0x91 OCTET(1) The result of the LR if any failure or partial success happened as known at the radio interface.
diagnostics O O 0xB2 INTEGER(4) A more detailed information about the Cause for Termination if any failure happened.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 93 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
systemType M M 0x93 ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
recordExtensions - - 0xB4 SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
causeForTerm M M 0x95 INTEGER(1) The reason for the termination of the location service.
lcsReferenceNumber - - 0x9F 65 OCTET STRING (SIZE (1..8))
Reserved for future use.
servedIMEI O O 0x9F 66 TBCD(8) The IMEI of the party who the LR is executed for if available.
additionalChgInfo M M 0xBF 81 05 SEQUENCE(3)
Charge/no charge indicator and additional charging parameters, when available.
chargedParty M M 0x9F 81 0D ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
orgRNCorBSCId M M 0x9F 81 27 OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
globalAreaID M M 0x9F 81 3C OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
subscriberCategory M M 0x9F 81 3E OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40 OCTET(3) Indicates the MCC and MNC of the network where LCS is initiated.
hotBillingTag O O 0x9F 81 48 INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
callReference M M 0x9F 81 49 OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
tariffCode O O 0x9F 81 59 INTEGER(1) The tariff code.
networkOperatorId O O 0x9F 81 5F OCTET (1) The ID of virtual operators.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 94 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
typeOfSubscribers O O 0x9F 81 60 ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
zoneCode O O 0x9F 81 70 OCTET (2) The zone code of a cell.
2.12 Mobile Originated Location Request (MO-LR)
If the generation of these records is enabled, an LCS-MO record shall be produced, within the visited MSC, for each mobile an originated location request is performed for. Table 2-1 lists the formats of LCS-MO records.
Table 2-1 LCS-MO record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
LCS-MO record. CallEventRecordType = 0x18
recordingEntity M M 0x81 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
lcsClientType O O 0x82 ENUMERATED
(1)
The type of the LCS client that invoked the LR.
lcsClientIdentity O O 0xA3 SEQUENCE
(13..29)
Further identification of the LCS client.
servedIMSI M M 0x84 TBCD(3..8) The IMSI of the subscriber the LR is invoked for.
servedMSISDN M M 0x85 ADRESS(2..9) The MSISDN of the subscriber the LR is invoked for.
molr-Type M M 0x86 INTEGER(1) The type of the LR.
lcsQos O O 0xA7 SEQUENCE(11) QoS of the LR, if available.
lcsPriority M M 0x88 OCTET(1) Priority of the LR.
mlc-Number O O 0x89 ADRESS(2..9) The E.164 address of the involved GMLC, if available.
eventTimeStamp M M 0x8A OCTET(9) The time at which the LR was received by the MSC.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 95 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
measureDuration M M 0x8B INTEGER(1..2) The duration of preceding the location request.
location M M 0xAC SEQUENCE (8) The identity of the cell or the SAC occupied by the originating party when the LCS was applied.
locationEstimate M M 0x8D OCTET(1..20) The location estimate for the subscriber if contained in geographic position and the LR was successful.
positioningData M M 0x8E OCTET(1..33) The positioning method used or attempted, if available.
lcsCause O O 0x8F OCTET(1) The result of the LR if any failure or partial success happened as known at the radio interface.
diagnostics O O 0xB0 INTEGER(4) A more detailed information about the Cause for Termination if any failure happened.
systemType M M 0x91 ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
recordExtensions - - 0xB2 SET OF (11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
causeForTerm M M 0x93 INTEGER(1) The reason for the termination of the location service.
lcsReferenceNumber - - 0x9F 65 OCTET STRING (SIZE (1..8))
Reserved for future use.
servedIMEI O O 0x9F 66 TBCD(8) The IMEI of the party who the LR is executed for if available.
additionalChgInfo M M 0xBF 81 05 SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
chargedParty M M 0x9F 81 0D ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 96 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
orgRNCorBSCId M M 0x9F 81 27 OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
globalAreaID M M 0x9F 81 3C OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
subscriberCategory M M 0x9F 81 3E OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40 OCTET(3) Indicates the MCC and MNC of the network where LCS is initiated.
hotBillingTag O O 0x9F 81 48 INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
callReference M M 0x9F 81 49 OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
tariffCode O O 0x9F 81 59 INTEGER(1) The tariff code.
networkOperatorId O O 0x9F 81 5F OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60 ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
zoneCode O O 0x9F 81 70 OCTET (2) The zone code of a cell.
2.13 Network Induced Location Request (NI-LR)
If the generation of these records is enabled, an LCS-NI record shall be produced, within the visited MSC, for each network induced location request performed for a MS e.g. in case of emergency call. Table 2-1 lists the formats of LCS-NI records.
Table 2-1 LCS-NI record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
LCS-NI record. CallEventRecordType = 0x19
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 97 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
recordingEntity M M 0x81 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
lcsClientType O O 0x82 ENUMERATED
(1)
The type of the LCS client that invoked the LR.
lcsClientIdentity O O 0xA3 SEQUENCE
(13..29)
Further identification of the LCS client.
servedIMSI M M 0x84 TBCD(3..8) The IMSI of the subscriber the LR is invoked for.
servedMSISDN M M 0x85 ADRESS(2..9) The MSISDN of the subscriber the LR is invoked for.
servedIMEI O O 0x86 TBCD(8) The IMEI of the subscriber the LR is invoked for.
emsDigits O O 0x87 ADRESS(2..9) The emergency service routing digits, if emergency call.
emsKey O O 0x88 ADRESS(2..9) The emergency service routing key, if emergency call.
lcsQos O O 0xA9 SEQUENCE(11)
QoS of the LR, if available.
lcsPriority M M 0x8A OCTET(1) Priority of the LR.
mlc-Number M M 0x8B ADRESS(2..9) The E.164 address of the involved GMLC, if available.
eventTimeStamp M M 0x8C OCTET(9) The time at which the LR was received by the MSC.
measureDuration M M 0x8D INTEGER(1..2)
The duration of preceding the location request.
location M M 0xAE OCTET(8) The identity of the cell or the SAC occupied by the terminated party when the LCS was applied.
locationEstimate O O 0x8F OCTET(1..20) The location estimate for the subscriber if contained in geographic position and the LR was successful.
positioningData M M 0x90 OCTET(1..33) The positioning method used or attempted, if available.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 98 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
lcsCause O O 0x91 OCTET(1) The result of the LR if any failure or partial success happened as known at the radio interface.
diagnostics O O 0xB2 INTEGER(4) A more detailed information about the Cause for Termination if any failure happened.
systemType M M 0x93 INTEGER(1) This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
recordExtensions - - 0xB4 SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
causeForTerm M M 0x95 INTEGER(1) The reason for the termination of the location service.
lcsReferenceNumber - - 0x9F 65 OCTET STRING (SIZE (1..8))
Reserved for future use.
additionalChgInfo M M 0xBF 81 05
SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
orgRNCorBSCId M M 0x9F 81 27 OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
globalAreaID M M 0x9F 81 3C
OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40 OCTET(3) Indicates the MCC and MNC of the network where LCS is initiated.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 99 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
hotBillingTag O O 0x9F 81 48 INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
callReference M M 0x9F 81 49 OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
networkOperatorId O O 0x9F 81 5F
OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60 ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
2.14 Supplementary Service ActionsA supplementary service record may be produced in the NEF of the appropriate MSC or HLR for each supplementary service action (activation, deactivation, invocation etc.) performed or initiated by the subscriber.
There are two fundamental types of SS-actions:
Call related i.e. as a result of a connection e.g. Invocation of CLIP / CLIR / AOC etc.
Non-call related i.e. as a result of Subscriber Controlled Input (SCI) e.g. Registration of call forwarding.
Each supplementary service action shall be performed on one or more basic service groups. If the action applies to all teleservices and all bearer services (i.e. to all basic services) then the basic services field shall be omitted.
SCI actions may be recorded in individual SS-action records. Call related actions may be recorded in either the appropriate call record (MOC/MTC) or in separate SS-action records.
Additional non-standard supplementary service actions may be made available within some networks in the form of Unstructured Supplementary Service Data (USSD). These actions may also be recorded in SS-action records. However, as these actions are non-standard they may not include an appropriate action type, supplementary service code or basic service code. Table 2-1 lists the formats of SS-action records.
Table 2-1 SS-action record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Supplementary service action record. CallEventRecordType = 0x0A
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the MS performing the action.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 100 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
servedIMEI O O 0x82 TBCD(8) The IMEI of the ME performing the action.
servedMSISDN M M 0x83 ADRESS(2..9) The primary MSISDN of the party performing the action.
msClassmark M M 0x84 OCTET(2..3) The mobile station classmark.
recordingEntity M M 0x85 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
location M M 0xA6 OCTET(8) The identity of the cell or the SAC, including the location area code, from which the request originated.
basicServices O O 0xA7 OCTET(3) The basic service group(s) to which the supplementary service applies.
supplService M M 0x88 OCTET(1) The supplementary service or group of supplementary services for which the request was made. The field is set to 0 in case of USSD.
ssAction M M 0x89 ENUMERATED
(1)
SS actions such as activation, deactivation, interrogation etc. The field is set to ussdInvocation (7) in case of USSD.
ssActionTime M M 0x8A OCTET(9) The time at which the action was requested.
ssParameters O O 0xAB OCTET STRING
(7..53)
Service dependent parameters or unstructured supplementary service data, if defined for the SS action recorded in this CDR.
ssActionResult O O 0xAC INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x8D OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
recordExtensions - - 0xAE SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
systemType M M 0x8F ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 101 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
ussdCodingScheme O O 0x9F 7E OCTET(1) Indicates the USSD coding scheme in the SS-action record generated for USSD.
ussdString O O 0xBF 7F SEQUENCE OF OCTET(1..40)
Indicates the USSD string entered by subscribers in the SS-action record generated for USSD.
ussdNotifyCounter O O 0x9F 81 00 INTEGER(1) In the case of USSD, indicates the times of notify procedure.
ussdRequestCounter O O 0x9F 81 01 INTEGER(1) In the case of USSD, indicates the times of request procedure.
additionalChgInfo M M 0xBF 81 05
SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
classmark3 O O 0x9F 81 0C
OCTET(2) The mobile station classmark 3.
chargedParty M M 0x9F 81 0D
ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
orgRNCorBSCId M M 0x9F 81 27 OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
globalAreaID M M 0x9F 81 3C
OCTET(7) The GCI of the GSM network or the SAI of the WCDMA network.
subscriberCategory M M 0x9F 81 3E
OCTET(1) The category of subscribers.
firstmccmnc M M 0x9F 81 40 OCTET(3) Indicates the MCC and MNC of the network where SS action is initiated.
hotBillingTag O O 0x9F 81 48 INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
tariffCode O O 0x9F 81 59 INTEGER(1) The tariff code.
networkOperatorId O O 0x9F 81 5F
OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60 ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
zoneCode O O 0x9F 81 70 OCTET (2) The zone code of a cell.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 102 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
2.15 HLR InterrogationIf the generation of these records is enabled, an HLR interrogation record shall be created for each interrogation performed for a mobile subscriber. These records may be produced in either the HLR itself or the interrogating MSC. Table 2-1 lists the formats of HLR interrogation records.
Table 2-1 HLR interrogation record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
HLR interrogation record. CallEventRecordType = 0x0B
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the party being interrogated, if successful.
servedMSISDN M M 0x82 ADRESS(2..9) The MSISDN of the subscriber being interrogated.
recordingEntity M M 0x83 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
basicService O O 0xA4 OCTET(3) The bearer or teleservice employed. Only for teleservice 21 (SMS-MT).
routingNumber O O 0xA5 ADRESS(2..17) Routing number (MSRN, forwarding no.) provided by the HLR if the interrogation was successful.
interrogationTime M M 0x86 OCTET(9) Time at which the interrogation was invoked.
numberOfForwarding O O 0x87 INTEGER(1) The number of times the call has been forwarded if provided by ISUP.
interrogationResult O O 0xA8 INTEGER(4) Reserved for future use.
recordExtensions - - 0xA9 SET OF (11 * n)
A set of network or manufacturer specific extensions to the record. Reserved for future use.
chargeAreaCode O O 0x9F 81 11
OCTET(1..3) The subscriber logical area for distance charge.
orgMSCId M M 0x9F 81 28
OCTET(3) The SPC of the MSC.
callReference M M 0x9F 81 29
OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 103 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
eCategory O O 0x9F 81 57
INTEGER(1..2) The enhanced subscriber category.
networkOperatorId O O 0x9F 81 5F
OCTET (1) The ID of virtual operators.
recordNumber O O 0x9F 81 68
INTEGER The serial number of a CDR.
2.16 Common Equipment Usage RecordIf the generation of these records is enabled, a common equipment usage record shall be created in the VMSC to record the usage (duration) of common equipment, e.g. conference circuits, employed by a mobile subscriber. Table 2-1 lists the formats of common equipment usage records.
Table 2-1 Common equipment usage record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Common equipment usage record. CallEventRecordType = 0x0E
equipmentType M M 0x81 INTEGER(1) The type of common equipment e.g. Conference circuit.
equipmentId M M 0x82 INTEGER(1) The local ID of the equipment employed.
servedIMSI M M 0x83 TBCD(3..8) The IMSI of the party responsible for the seizure of the equipment.
servedIMEI O O 0x9F 66 TBCD(8) The IMEI of the calling ME, if available.
servedMSISDN M M 0x84 ADRESS(2..9) The primary MSISDN of the served party.
recordingEntity M M 0x85 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
basicService M M 0xA6 OCTET(3) The bearer or teleservice employed.
changeOfService - - 0xA7 SEQUENCE OF
( (18..27) * n)
A list of changes of basic service during a connection each time-stamped.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 104 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
supplServicesUsed M M 0xA8 SEQUENCE OF
(16 * n)
Supplementary services invoked as a result of this connection. This field shall be present when one or more supplementary services have been invoked.
seizureTime M M 0x89 OCTET(9) The time stamp at which the equipment was seized.
releaseTime M M 0x8A OCTET(9) The time stamp at which the equipment was released.
callDuration M M 0x8B INTEGER(1..2) The total duration of the usage of the equipment.
callReference M M 0x8C OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
sequenceNumber - - 0x8D INTEGER(1) The partial record sequence number, only present in case of partial records.
recordExtensions - - 0xAE SET OF (11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
systemType M M 0x8F ENUMERATED
(1)
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either the UTRAN or GERAN air-interface is used on call setup.
rateIndication - - 0x90 OCTET(1) Present if "rate adaptation" parameters for the basic service were signaled between the MS/UE and the network, see TS 24.008. Reserved for future use.
fnur - - 0x91 ENUMERATED
(1)
The user data rate applied for the connection in the fixed network. Shall only be present for 2G HSCSD connections and for UMTS data connections.
partialRecordType - - 0x92 ENUMERATED
(1)
The event (time limit etc.) that caused the generation of a partial record. This field is mandatory in case of partial records.
causeForTerm M M 0x9F 64 INTEGER(1) The reason for the release of the connection.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 105 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
diagnostics M M 0xBF 65 INTEGER(4) A more detailed reason for the release of the connection.
additionalChgInfo M M 0xBF 81 05 SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
orgRNCorBSCId M M 0x9F 81 27 OCTET(3) The SPC of the RNC or the BSC.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
subscriberCategory M M 0x9F 81 3E OCTET(1) The category of subscribers.
hotBillingTag O O 0x9F 81 48 INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
networkOperatorId O O 0x9F 81 5F OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60 ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
2.17 Terminating CAMEL Call AttemptIf the generation of these records is enabled, a terminating CAMEL call attempt record shall be generated for each call toward a subscriber with a T-CSI or VT-CSI and if the terminating triggers criteria are met. The record is generated in the GMSC/gsmSSF carrying out the terminating CAMEL call handling and in the MSC server/gsmSSF carrying out the visited terminating CAMEL call attempt. Table 2-1 lists the formats of terminating CAMEL call attempt records.
Table 2-1 Terminating CAMEL call attempt record
Field 2G 3G TAG TYPE Description
recordtype M M 0x80 ENUMERATED
(1)
Terminating CAMEL interrogation record. CallEventRecordType = 0x11
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the called party.
servedMSISDN M M 0x82 ADRESS(2..9) The MSISDN of the called party.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 106 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
recordingEntity M M 0x83 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
interrogationTime M M 0x84 OCTET(9) Time at which the interrogation with HLR was invoked.
destinationRoutingAddress O O 0x85 ADRESS(2..17) The number available for routing after the CAMEL server enquiry.
gsm-SCFAddress M M 0x86 ADRESS(2..9) The CAMEL server serving the subscriber. Shall be present only if CAMEL is applied.
serviceKey M M 0x87 INTEGER(1..4) The CAMEL service logic to be applied. Shall be present only if CAMEL is applied.
networkCallReference M M 0x88 OCTET(1..8) An identifier to correlate transactions on the same call taking place in different network nodes.
mSCAddress M M 0x89 ADRESS(2..9) The E.164 number assigned to the MSC that generated the network call reference.
defaultCallHandling O O 0x8A ENUMERATED
(1)
Indicates whether a CAMEL call encounters default call handling. This field shall be present only if default call handling has been applied.
recordExtensions - - 0xAB SET OF(11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
calledNumber M M 0x8C ADRESS(2..17) The address of the called party as received by the GMSC/gsmSSF.
callingNumber O O 0x8D ADRESS(2..17) The address of the calling party, if available.
mscIncomingROUTE M M 0xAE IA5(1..32) The incoming GMSC route on which the call is originated.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 107 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
mscOutgoingROUTE M M 0xAF IA5(1..32) The route on which the call left the GMSC.
seizureTime - - 0x90 OCTET(9) The time of incoming traffic channel seizure (for unsuccessful call attempts). At present, it is not available.
answerTime M M 0x91 OCTET(9) The time stamp when the call is answered during a successful connection.
releaseTime M M 0x92 OCTET(9) The time stamp when either the calling or the called party releases the traffic channel.
callDuration M M 0x93 INTEGER(1..2) The chargeable duration of the connection for successful calls, the holding time of call attempts.
causeForTerm M M 0x95 INTEGER(1) The reason for the release of the connection.
diagnostics M M 0xB6 INTEGER(4) A more detailed reason for the release of the connection.
callReference M M 0x97 OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
sequenceNumber O O 0x98 INTEGER(1) The partial record sequence number, only present in case of partial records.
numberOfDPEncountered O O 0x99 INTEGER(1) Number that counts how often armed detection points (TDP and EDP) were encountered. Shall be present only if CAMEL is applied.
levelOfCAMELService M M 0x9A BIT STRING(2) The indicator for the complexity of the CAMEL feature used. Shall be present only if CAMEL is applied.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 108 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
freeFormatData O O 0x9B OCTET(1..160) This field contains data sent by the gsmSCF in the FCI messages. The data can be sent either in one FCI message or several FCI messages with append indicator. Shall be present only if CAMEL is applied for the second service.
cAMELCallLegInformation O O 0xBC SEQUENCE OF
((104..124) * n)
A set of CAMEL information IEs. Each of these IEs contains information related to one outgoing CAMEL call leg. Shall be present only if CAMEL is applied.
freeFormatDataAppend O O 0x9D BOOLEAN(1) Indicator if free format data from this CDR is to be appended to free format data in previous partial CDR.
mscServerIndication O O 0x9E BOOLEAN(1) Indication if the CAMEL call handling is active in the MSC server.
defaultCallHandling-2 - - 0x9F 1F ENUMERATED
(1)
Indicates whether or not a CAMEL call encountered default call handling for the second service such as the dialed service. This field shall be present only if default call handling has been applied.
gsm-SCFAddress-2 - - 0x9F 20 ADRESS(2..9) The CAMEL server serving the subscriber for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service.
serviceKey-2 - - 0x9F 21 INTEGER(1..4) The CAMEL service logic to be applied for the second service such as the dialed service. Shall be present only if CAMEL is applied for the second service.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 109 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
freeFormatData-2 - - 0x9F 22 OCTET(1..160) This field contains data sent by the gsmSCF in the FCI message(s) for the second service such as the dialed service. The data can be sent either in one FCI message or several FCI messages with append indicator.
freeFormatDataAppend-2 - - 0x9F 23 BOOLEAN(1) Indicator if free format data for the second service from this CDR is to be appended to free format data in previous partial CDR. Shall be present only if CAMEL is applied for the second service.
partialRecordType O O 0x9F 2A ENUMERATED
(1)
The event (time limit etc.) that caused the generation of a partial record. This field is mandatory in case of partial records.
basicService M M 0xBF 81 02 OCTET(3) The bearer or teleservice employed.
additionalChgInfo M M 0xBF 81 05 SEQUENCE(3) Charge/no charge indicator and additional charging parameters, when available.
chargedParty M M 0x9F 81 0D ENUMERATED
(1)
Indicates whether the calling party or the called party is charged for the call.
originalCalledNumber O O 0x9F 81 0E ADRESS(2..17) The address of original called party.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
subscriberCategory M M 0x9F 81 3E OCTET(1) The category of subscribers.
hotBillingTag O O 0x9F 81 48 INTEGER(1) Indicates that the charged party is a subscriber who subscribes to the hot billing service. Shall be present only if the hot charging function is applied.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 110 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
resourceChargeIPnumber O O 0x9F 81 4E ADRESS (2..17) The address of the IP equipment that plays the announcement in the case of resource charging.
csReference O O 0x9F 81 5C OCTET(1..8) The call segment reference number.
csaReference O O 0x9F 81 5D INTEGER (1..4) The call segment association reference number.
camelphase O O 0x9F 81 5E ENUMERATED
(1)l
The CAMEL version number.
networkOperatorId O O 0x9F 81 5F OCTET (1) The ID of virtual operators.
typeOfSubscribers O O 0x9F 81 60 ENUMERATED(1)
The type of roaming subscriber.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
partyRelCause O O 0xBF 81 6C PartyRelCause Indicates the cause of call release.
translatedNumber O O 0x9F 81 75 ADRESS (2..17) The called number after digit translation within the MSC (if applicable).
interactionWithIP O O 0x9F 81 47 NULL (0) In the case of interaction between SSP and IP, GsmSCF play announcement to SSP and start charging.
2.18 IMEI Observation TicketAn observed IMEI ticket is generated whenever greylisted, blacklisted or non-whitelisted mobile equipment is detected during an IMEI check. The purpose of the ticket is to link the mobile equipment under observation with its current user (IMSI). The ticket also includes information describing when and where the equipment was used to enable the tracking of such equipment. Finally, if the ticket was triggered by a call attempt, a call reference is provided in order to locate the corresponding call record. The IMEI tickets are generated by the NEF of the MSC performing the IMEI check. Table 2-1 lists the formats of IMEI tickets.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 111 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Table 2-1 IMEI ticket
Field 2G 3G TAG TYPE Description
servedIMEI M M 0x80 TBCD(8) IMEI of the observed mobile equipment
imeiStatus M M 0x81 ENUMERATED
(1)
The result of the IMEI check e.g. blacklisted, greylisted, unknown.
servedIMSI M M 0x82 TBCD(3..8) The IMSI of the subscriber currently using the mobile equipment.
servedMSISDN O O 0x83 ADRESS(2..9) The MSISDN of the subscriber currently using the observed mobile equipment, only available if the event that triggered the IMEI check was an MOC, MTC, SMS-MO or SMS-MT.
recordingEntity M M 0x84 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
eventTime M M 0x85 OCTET(9) The time at which the IMEI check was performed.
location M M 0xA6 OCTET(8) The location area code and cell identity of the cell from which the mobile equipment was used.
imeiCheckEvent M M 0x87 INTEGER(1) The event that caused IMEI checking to take place.
callReference M M 0x88 OCTET(1..8) A local identifier distinguishing between transactions on the same MS.
recordExtensions - - 0xA9 SET OF (11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
orgMSCId M M 0x9F 81 28 OCTET(3) The SPC of the MSC.
networkOperatorId O O 0x9F 81 5F OCTET (1) The ID of virtual operators.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 112 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
2.19 Location Update (VLR)If enabled, a VLR location update record shall be produced in the VLR for each location registration or location update received by the VLR for a mobile subscriber. Table 2-1 lists the formats of Location update (VLR) records.
Table 2-1 Location update (VLR) record
Field 2G 3G TAG TYPE Description
recordType M M 0x80 ENUMERATED
(1)
Location update (VLR) record. CallEventRecordType = 0x0D
servedIMSI M M 0x81 TBCD(3..8) The IMSI of the served MS.
servedMSISDN M M 0x82 ADRESS(2..9) The primary MSISDN of the party performing the location update.
recordingEntity M M 0x83 ADRESS(2..9) The E.164 number of the visited MSC producing the record (MSC/VLR number: TON+NPI+MSC identifier number).
oldLocation O O 0xA4 SEQUENCE (16) Location area and cell before the location update.
newLocation M M 0xA5 SEQUENCE (16) Location area and cell after the location update.
msClassmark M M 0x86 OCTET(2..3) The mobile station classmark.
updateTime M M 0x87 OCTET(9) Time at which the update was invoked.
updateResult O O 0xA8 CHOICE (4) The result of the location update if unsuccessful.
recordExtensions O O 0xA9 SET OF (11 * n) A set of network or manufacturer specific extensions to the record. Reserved for future use.
gsm-SCFAddress O O 0x8A ADRESS(2..9) The CAMEL server serving the subscriber. Shall be present only if CAMEL is applied.
serviceKey O O 0x8B INTEGER(1..4) The CAMEL service logic to be applied. Shall be present only if CAMEL is applied.
callReference O O 0x8C OCTET(1..8) A local identifier distinguishing between transactions on the same MS. It is also used to identify all partial records and transactions belonging to the same connection.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 113 of 176
CONFIDENTIALMSOFTX3000 V100R006C05
03-MSOFTX3000 V100R006C05 ASN.1 CDR Description
Field 2G 3G TAG TYPE Description
locationUpdateType M M 0x8D ENUMERATED
(1)
The type of location update.
chargeAreaCode O O 0x9F 81 11 OCTET(1..3) The subscriber logical area for distance charge.
networkOperatorId O O 0x9F 81 5F OCTET(1) The ID of virtual operators.
recordNumber O O 0x9F 81 68 INTEGER The serial number of a CDR.
Issue 1.00 (2008-02-25)
Huawei TechnologiesProprietaryHuawei TechnologiesProprietaryHuawei Technologies
Proprietary
Page 114 of 176
3 Description of Record Fields
The CDR fields are the specific segments in the CDR. Refer to chapter 2 "Record Contents." This section describes the functions of each field in the CDR and the ASN.1 encoding.
3.1 Additional Charging InformationThis field is used to identify whether to charge the record and the additional charging information of the record. This field consists of two parts, a charge indicator and additional charging parameters.
The charge indicator is derived from the information contained within the ISUP "backward call indicator" and may be used to store a charge indicator (charge/no charge) received from another network node.
The additional charging parameters are non-standard and intended to permit the inclusion of further charging information received from Intelligent Network and/or Value Added Service nodes.
The ASN.1 encoding of this field is as follows:
ChargeIndicator ::= INTEGER
{
noIndication (0),
noCharge (1),
charge (2)
}
3.2 aiurRequestedThis field refers to the total Air Interface User Rate Requested by the MS at call setup. It is applicable only to non-transparent data services for High Speed Circuit Switched Data (HSCSD) connections. The ASN.1 encoding of this field is as follows:
AiurRequested ::= ENUMERATED
{
--
-- See Bearer Capability TS 24.008
-- (note that value "4" is intentionally missing
-- because it is not used in TS 24.008)
--
aiur09600BitsPerSecond (1),
aiur14400BitsPerSecond (2),
aiur19200BitsPerSecond (3),
aiur28800BitsPerSecond (5),
aiur38400BitsPerSecond (6),
aiur43200BitsPerSecond (7),
aiur57600BitsPerSecond (8),
aiur38400BitsPerSecond1 (9),
aiur38400BitsPerSecond2 (10),
aiur38400BitsPerSecond3 (11),
aiur38400BitsPerSecond4 (12)
}
3.3 AoC parameters / change of AoC parametersThis field contains the set of charge advice (AoC) parameters sent to the MS on call set-up. If further sets of parameters are sent during the call, as a result of a tariff switch-over for example, then this may be recorded in the Change of AoC Parameter field including the time at which the change occurred. It should be noted that the Change of AoC Parms. field is optional and not required if partial records are generated on tariff switch-over. Refer to The ASN.1 encoding of this field is as follows:
AOCParameters ::= SEQUENCE
{
--
-- See TS 22.024.
--
e1 [1] EParameter OPTIONAL,
e2 [2] EParameter OPTIONAL,
e3 [3] EParameter OPTIONAL,
e4 [4] EParameter OPTIONAL,
e5 [5] EParameter OPTIONAL,
e6 [6] EParameter OPTIONAL,
e7 [7] EParameter OPTIONAL
}
3.4 audioDataTypeThis field indicates whether the service used by the user is voice service or data service. The ASN.1 encoding of this field is as follows:
audioDataType ::= ENUMERATED
{
audio (0),
fax (1),
AUDIO_DATA_BUTT (255)
}
3.5 basicService/changeOfService/isdnBasicService This field contains the code of the basic service employed on call set-up. Any alteration
to the basic service during the connection may be recorded in the change of service field including the time at which the change took place. Refer to 3GPP TS 29.002 for details.
This field is optional and may be omitted if partial records are created whenever the basic service is changed.
In the case of the transit record the ISDN basic service employed is generally not available. However, if the device on which the call originates/terminates is connected via ISDN digital subscriber signaling then the appropriate ISDN basic service code should be recorded in the record. One possible example includes the direct connection of an ISDN PABX to an MSC/VLR.
The ASN.1 encoding of the three fields is as follows:
BasicServiceCode ::= CHOICE
{
bearerService [2] BearerServiceCode,
teleservice [3] TeleserviceCode,
isdnService [4] IsdnServiceCode
}
TeleserviceCode ::= OCTET STRING (SIZE (1))
-- This type is used to represent the code identifying a single
-- teleservice, a group of teleservices, or all teleservices. The
-- services are defined in TS GSM 02.03.
-- The internal structure is defined as follows:
-- bits 87654321: group (bits 8765) and specific service
-- (bits 4321)
-- allTeleservices (0x00),
-- allSpeechTransmissionServices (0x10),
-- telephony (0x11),
-- emergencyCalls (0x12),
--
-- allShortMessageServices (0x20),
-- shortMessageMT-PP (0x21),
-- shortMessageMO-PP (0x22),
--
-- allFacsimileTransmissionServices (0x60),
-- facsimileGroup3AndAlterSpeech (0x61),
-- automaticFacsimileGroup3 (0x62),
-- facsimileGroup4 (0x63),
--
-- The following non-hierarchical Compound Teleservice Groups
-- are defined in TS GSM 02.30:
-- allDataTeleservices (0x70),
-- covers Teleservice Groups 'allFacsimileTransmissionServices'
-- and 'allShortMessageServices'
-- allTeleservices-ExeptSMS (0x80),
-- covers Teleservice Groups 'allSpeechTransmissionServices' and
-- 'allFacsimileTransmissionServices'
--
-- Compound Teleservice Group Codes are only used in call
-- independent supplementary service operations, i.e. they
-- are not used in InsertSubscriberData or in
-- DeleteSubscriberData messages.
--
-- allVoiceGroupCallServices (0x90),
-- voiceGroupCall (0x91),
-- voiceBroadcastCall (0x92),
--
-- allPLMN-specificTS (0xd0),
-- plmn-specificTS-1 (0xd1),
-- plmn-specificTS-2 (0xd2),
-- plmn-specificTS-3 (0xd3),
-- plmn-specificTS-4 (0xd4),
-- plmn-specificTS-5 (0xd5),
-- plmn-specificTS-6 (0xd6),
-- plmn-specificTS-7 (0xd7),
-- plmn-specificTS-8 (0xd8),
-- plmn-specificTS-9 (0xd9),
-- plmn-specificTS-A (0xda),
-- plmn-specificTS-B (0xdb),
-- plmn-specificTS-C (0xdc),
-- plmn-specificTS-D (0xdd),
-- plmn-specificTS-E (0xde),
-- plmn-specificTS-F (0xdf)
BearerServiceCode ::= OCTET STRING (SIZE (1))
-- This type is used to represent the code identifying a single
-- bearer service, a group of bearer services, or all bearer
-- services. The services are defined in TS 3GPP TS 22.002.
-- The internal structure is defined as follows:
--
-- plmn-specific bearer services:
-- bits 87654321: defined by the HPLMN operator
-- rest of bearer services:
-- bit 8: 0 (unused)
-- bits 7654321: group (bits 7654), and rate, if applicable
-- (bits 321)
-- allBearerServices (0x00),
-- allDataCDA-Services (0x10),
-- dataCDA-300bps (0x11),
-- dataCDA-1200bps (0x12),
-- dataCDA-1200-75bps (0x13),
-- dataCDA-2400bps (0x14),
-- dataCDA-4800bps (0x15),
-- dataCDA-9600bps (0x16),
-- general-dataCDA (0x17), --not transparency service, such as 3.1k HZ audio
-- allDataCDS-Services (0x18),
-- dataCDS-1200bps (0x1a),
-- dataCDS-2400bps (0x1c),
-- dataCDS-4800bps (0x1d),
-- dataCDS-9600bps (0x1e),
-- general-dataCDS (0x1f), -- transparency service, such as 64K UDI H.223 and H.245 VP
--
-- allPadAccessCA-Services (0x20),
-- padAccessCA-300bps (0x21),
-- padAccessCA-1200bps (0x22),
-- PadAccessCA-1200-75bps (0x23),
-- padAccessCA-2400bps (0x24),
-- padAccessCA-4800bps (0x25),
-- padAccessCA-9600bps (0x26),
-- general-padAccessCA (0x27),
--
-- allDataPDS-Services (0x28),
-- dataPDS-2400bps (0x2c),
-- dataPDS-4800bps (0x2d),
-- dataPDS-9600bps (0x2e),
-- general-dataPDS (0x2f),
--
-- allAlternateSpeech-DataCDA (0x30),
--
-- allAlternateSpeech-DataCDS (0x38),
--
-- allSpeechFollowedByDataCDA (0x40),
--
-- allSpeechFollowedByDataCDS (0x48),
--
-- The following non-hierarchical Compound Bearer Service
-- Groups are defined in TS GSM 02.30:
-- allDataCircuitAsynchronous (0x50),
-- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA" and
-- "allSpeechFollowedByDataCDA"
-- allDataCircuitSynchronous (0x58),
-- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS" and
-- "allSpeechFollowedByDataCDS"
-- allAsynchronousServices (0x60),
-- covers "allDataCDA-Services", "allAlternateSpeech-DataCDA",
-- "allSpeechFollowedByDataCDA" and "allPadAccessCDA-Services"
-- allSynchronousServices (0x68),
-- covers "allDataCDS-Services", "allAlternateSpeech-DataCDS",
-- "allSpeechFollowedByDataCDS" and "allDataPDS-Services"
--
-- Compound Bearer Service Group Codes are only used in call
-- independent supplementary service operations, i.e. they
-- are not used in InsertSubscriberData or in
-- DeleteSubscriberData messages.
--
-- allPLMN-specificBS (0xd0),
-- plmn-specificBS-1 (0xd1),
-- plmn-specificBS-2 (0xd2),
-- plmn-specificBS-3 (0xd3),
-- plmn-specificBS-4 (0xd4),
-- plmn-specificBS-5 (0xd5),
-- plmn-specificBS-6 (0xd6),
-- plmn-specificBS-7 (0xd7),
-- plmn-specificBS-8 (0xd8),
-- plmn-specificBS-9 (0xd9),
-- plmn-specificBS-A (0xda),
-- plmn-specificBS-B (0xdb),
-- plmn-specificBS-C (0xdc),
-- plmn-specificBS-D (0xdd),
-- plmn-specificBS-E (0xde),
-- plmn-specificBS-F (0xdf)
NOTE:UMTS Bearer servide code:
general-dataCDA (0x17), --not transparency service, such as 3.1k HZ audio
general-dataCDS (0x1f),-- transparency service, such as 64K UDI H.223 and H.245 VP
IsdnServiceCode ::= OCTET STRING (SIZE(1)) --This parameter identifies the ISDN Basic service as defined in ETSI specification ETS 300 196.
-- allServices '00'h
-- speech '01'h
-- unrestricteDigtalInfo '02'h
-- audio3k1HZ '03'h
-- unrestricteDigtalInfowithtoneandannoucement '04'h
-- telephony3k1HZ '20'h
-- teletext '21'h
-- telefaxGroup4Class1 '22'h
-- videotextSyntaxBased '23'h
-- videotelephony '24'h
-- telefaxGroup2-3 '25'h
-- telephony7kHZ '26'h
ChangeOfService ::= SEQUENCE
{
basicService [0] BasicServiceCode,
transparencyInd [1] TransparencyInd OPTIONAL,
changeTime [2] TimeStamp,
rateIndication [3] RateIndication OPTIONAL,
fnur [4] Fnur OPTIONAL
}
ISDN Basic Service ::= OCTET STRING (SIZE(1))
--This parameter identifies the ISDN Basic service as defined in ETSI specification ETS 300 196.
-- allServices '00'h
-- speech '01'h
-- unrestricteDigtalInfo '02'h
-- audio3k1HZ '03'h
-- unrestricteDigtalInfowithtoneandannoucement '04'h
-- telephony3k1HZ '20'h
-- teletext '21'h
-- telefaxGroup4Class1 '22'h
-- videotextSyntaxBased '23'h
-- videotelephony '24'h
-- telefaxGroup2-3 '25'h
-- telephony7kHZ '26'h
3.6 bCategoryThis field indicates the status of the called party. If the call is disconnected due to called party busy, the value of this field is subscriberBusy. If the call disconnection is not due to called party busy, the value of this field is subscriberFree. The ASN.1 encoding of this field is as follows:
BCategory ::= ENUMERATED
{
subscriberFree (0) ,
subscriberBusy (1),
subscriberNoIndication (3)
}
3.7 callDurationThis field contains the relevant call duration in seconds. For complete (answered) calls the relevant duration is the chargeable duration from answer to release of the traffic channel. For partial records this is the duration of the individual partial record and not the cumulative duration of the call. The ASN.1 encoding of this field is as follows:
CallDuration ::= INTEGER
--
-- The call duration in seconds.
-- For successful calls this is the chargeable duration.
-- For call attempts this is the call holding time.
The format of the time stamp is closely related to call duration. The ASN.1 encoding of the time stamp is as follows:
TimeStamp ::= OCTET STRING (SIZE(9..10))
--
-- The contents of this field are a compact form of the UTCTime format
-- containing local time plus an offset to universal time. Binary coded
-- decimal encoding is employed for the digits to reduce the storage and
-- transmission overhead
-- e.g. YYMMDDhhmmssShhmm
-- where
-- YY = Year 00 to 99 BCD encoded
-- MM = Month 01 to 12 BCD encoded
-- DD = Day 01 to 31 BCD encoded
-- hh = hour 00 to 23 BCD encoded
-- mm = minute 00 to 59 BCD encoded
-- ss = second 00 to 59 BCD encoded
-- S = Sign 0 = "+", "-" ASCII encoded
-- hh = hour 00 to 23 BCD encoded
-- mm = minute 00 to 59 BCD encoded
-- DST = 00 to 120 INTEGER encoded (DST is optional)
If CAMEL is invoked for the call and a control relationship is existing, the call might continue after a RELEASE or a DISCONNECT from the called party side received by the gsmSSF. The call duration of the incoming leg is stored in the main body of the call record. For each outgoing leg the call duration is stored in the respective 'CAMELInformation' module.
An example of how to use the call duration and the timestamps is given in Figure 3-1 and Table 3-1. It shows a CAMEL controlled mobile originated follow-on scenario. The uppermost arrow marks the over all duration of the call that is to be measured and stored in the main body of the respective MOC record. The duration before t5 (incoming leg) or t4 (outgoing leg) needs not to be stored since the call is answered later on. The call duration in the first outgoing leg module contains the time interval from t4 to t6 (period ). The call duration measurement of the second outleg is started with t9 and ended with t10 (interval ).
The timestamps t1, t2, t3, t7, t8 and t12 mentioned in Figure 1-3 and Table 1-20 are for completion reasons only.
Figure 3-1 Call duration
time
outg. leg 1
outg. leg 2
outg. leg 3
inc. leg
t2 t3 t5 t6t1 t7 t8 t9 t10 t11 t12 t13
call duration of incoming leg =
call duration of outgoing leg =
holding time of outgoing leg =
t4
Table 3-1 Description of the time information
Point in Time Signaling Message Sent/Received
Trigger Detection Point Encountered
Duration Logging
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)
Point in Time Signaling Message Sent/Received
Trigger Detection Point Encountered
Duration Logging
t11 IAM seizure of outg. leg 3
start of holding time (outg. leg 3)
t12 ACM
t13 RELEASE; EDP(control) stop of holding time (outg. leg 3)
3.8 calling Number/called Number / connected Number/translated Number
In general, a calling Number/called Number / connected Number/translated Number is in the format of ITU-T E.164, but may also include other numbering plans, for example, X 121. Each of these fields includes the type of number and number plan as specified in detail in 3GPP TS 24.008.
The calling number is the number received from the network on mobile terminated call set-up as defined in 3 GPP TS 24.008 [4].
The called number is the number received from the mobile station on mobile originated call set-up as defined in 3GPP TS 24.008 [4]. In case of CAMEL initiated call forward (CF), the called (forwarded-to) number is returned by CAMEL.
The translated number is the result of any digit translation performed by the MSC on the called number received from the mobile station on mobile originated call set-up.
The connected number is the number of the actual party reached as defined in 3GPP TS 24.008. Although this is normally identical to the called number it may differ. This parameter is not included if identical to the called number.
The following examples are intended to explain the use of these fields:
EXAMPLE 1:Called Number = Connected Number
Normal call from a mobile subscriber to a mobile subscriber or to a PSTN subscriber
EXAMPLE 2: Called Number != Connected Number
In case of routing to a PABX with Automatic Call Distribution or to an ISDN Basic Access with several devices attached. The connected number is that of the party actually reached. N.B. The recording of the actual number connected may be limited by the capability of intermediate signaling connections.
EXAMPLE 3: MTC record for Call Forwarding ("A" -> "B" -> "C")
In case of call forwarding, the connected number recorded in the MTC record of the "B" subscriber is that of the forwarded-to party or "C" subscriber. The calling party field contains the number of the "A" subscriber.
EXAMPLE 4: Translated Number
This field is only present if digit translation is applied by the MSC to the called number received from the mobile station. Examples include abbreviated dialing codes and service numbers.
For the definitions of the numbers described, refer to the descriptions of the calling number, called number, and the connected number in the TS 24.008. The descriptions of the number consist of two parts, with the first part as address information and numbering plan of the number and the second part as the number information about the TBCD format.
The ASN.1 encoding of the above fields is as follows:
CallingNumber ::= BCDDirectoryNumber
CalledNumber ::= BCDDirectoryNumber
TranslatedNumber ::= BCDDirectoryNumber
ConnectedNumber ::= BCDDirectoryNumber
3.9 callReferenceThis field uniquely identifies a call or transaction on one side of the interface (i.e. 'A' or 'B' side) It is also used to identify all partial records and transactions belonging to the same connection. For example, a unique callReference generated during a call can uniquely identify the call.
CallReference ::= OCTET STRING (SIZE (1..8)).
3.10 CallTypeThis field indicates the type of the call. The value of this field can be one of the following:
Unknown
Incoming
Outgoing
Internal
Tandem
The ASN.1 encoding of this field is as follows:
CallType ::= ENUMERATED
{
unknown (0),
internal (1),
incoming (2),
outgoing (3),
tandem (4)
}
3.11 cAMELCallLegInformationThis field contains a set of CAMEL information elements (IEs) according to the number of outgoing CAMEL call legs.
This field consists of CAMEL IEs in the SET structure. A CDR is generated by the Huawei MSC for the CAMEL LEG Information, and the CDR is then correlated to the corresponding main CDR by the Huawei iGWB. See CAMEL IEs in the following description and refer to 3GPP 32.250 for details.
The ASN.1 encoding of this field is as follows:
CAMELInformation ::= SET
{
cAMELDestinationNumber [1] CAMELDestinationNumber OPTIONAL,
connectedNumber [2] ConnectedNumber OPTIONAL,
roamingNumber [3] RoamingNumber OPTIONAL,
mscOutgoingROUTE [4] ROUTE OPTIONAL,
seizureTime [5] TimeStamp OPTIONAL,
answerTime [6] TimeStamp OPTIONAL,
releaseTime [7] TimeStamp OPTIONAL,
callDuration [8] CallDuration OPTIONAL,
dataVolume [9] DataVolume OPTIONAL,
cAMELInitCFIndicator [10] CAMELInitCFIndicator OPTIONAL,
causeForTerm [11] CauseForTerm OPTIONAL,
cAMELModification [12] ChangedParameters OPTIONAL,
freeFormatData [13] FreeFormatData OPTIONAL,
diagnostics [14] Diagnostics OPTIONAL,
freeFormatDataAppend [15] BOOLEAN OPTIONAL,
freeFormatData-2 [16] FreeFormatData OPTIONAL,
freeFormatDataAppend-2 [17] BOOLEAN OPTIONAL,
translatedNumber [18] TranslatedNumber OPTIONAL,
additionalChgInfo [19] AdditionalChgInfo OPTIONAL,
defaultCallHandling-2 [20] DefaultCallHandling OPTIONAL,
gsm-SCFAddress-2 [21] Gsm-SCFAddress OPTIONAL,
serviceKey-2 [22] ServiceKey OPTIONAL,
legID [23] CAMELLegID OPTIONAL,
partialRecordType [24] PartialRecordType OPTIONAL
}
3.12 cAMELDestinationNumberThis field contains Destination/Called Subscriber Number modified by CAMEL service. If not modified then this field may contain original Destination Number also when CAMEL is not active. Only the destination delivered by the SCP is valid.
The ASN.1 encoding of this field is as follows:
CAMELDestinationNumber ::= DestinationRoutingAddress
DestinationRoutingAddress ::= BCDDirectoryNumber
3.13 cAMELInitCFIndicatorThe purpose of this field is to distinguish CAMEL call forwarding service scenarios from standard GSM call forwarding scenarios. From the Basic Call State Model (BCSM)'s point of view this field is set to 'CF' whenever the Originating CAMEL Subscription Information (O_CSI) was applied after terminating CAMEL call processing had been taken place and the call destination is changed. For the avoidance of doubt: this flag does not depend on other
modified call parameter(s) (e.g.: redirection information, etc.) received in the CAP_CONNECT message of the Terminating CAMEL Subscription Information (T_CSI) service.
This flag also indicates that another record might be generated, one containing the charging information related to the terminating CAMEL service and one containing the charging information related to the originating CAMEL service.
The ASN.1 encoding of this field is as follows:
CAMELInitCFIndicator ::= ENUMERATED
{
noCAMELCallForwarding (0),
cAMELCallForwarding (1)
}
3.14 cAMELSMSInformationThis field contains following CAMEL information for mobile originated and terminated SMS:
Default SMS handling: This field indicates whether or not a CAMEL encounters default SMS handling. This field shall be present only if default SMS handling has been applied.
Free format data See Free format data.
Calling Party Number: This field contains Calling Party Number modified by CAMEL service.
CAMEL modified service centre: This field contains SMS-C address modified by CAMEL service.
CAMEL Destination Subscriber Number: This field contains short message Destination Number modified by CAMEL service.
The ASN.1 encoding of cAMELSMSInformation is as follows:
CAMELSMSInformation ::= SET
{
gsm-SCFAddress [1] Gsm-SCFAddress OPTIONAL,
serviceKey [2] ServiceKey OPTIONAL,
defaultSMSHandling [3] DefaultSMS-Handling OPTIONAL,
freeFormatData [4] FreeFormatData OPTIONAL,
callingPartyNumber [5] CallingNumber OPTIONAL,
destinationSubscriberNumber [6] CalledNumber OPTIONAL,
cAMELSMSCAddress [7] AddressString OPTIONAL,
smsReferenceNumber [8] CallReferenceNumber OPTIONAL
}
3.15 chargeAreaCodeThis field indicates the logical charging area code for the calling number. The ASN.1 encoding of this field is as follows:
ChargeAreaCode ::= OCTET STRING(SIZE (1..3))
3.16 calledChargeAreaCodeThis field indicates the logical charging area code of the called number. The ASN.1 encoding of this field is as follows:
ChargeAreaCode ::= OCTET STRING(SIZE (1..3)
3.17 callEmlppPriority/ callerDefaultEmlppPriority/calledEmlppPriority
This field contains the enhanced Multi Level Precedence and Preemption (eMLPP) priority information of the subscriber. For more details, refer to the 3GPP TS 29.002. The ASN.1 encoding of this field is as follows:
EmlppPriority::= OCTET STRING (SIZE (1))
--priorityLevelA EMLPP-Priority ::= 6
--priorityLevelB EMLPP-Priority ::= 5
--priorityLevel0 EMLPP-Priority ::= 0
--priorityLevel1 EMLPP-Priority ::= 1
--priorityLevel2 EMLPP-Priority ::= 2
--priorityLevel3 EMLPP-Priority ::= 3
--priorityLevel4 EMLPP-Priority ::= 4
3.18 camelphaseThis field indicates the CAMEL phase used by a CAMEL call. The ASN.1 encoding of this field is as follows:
CAMELVPHASE ::= ENUMERATED
{
wininapphase0 (0),
wincamelphase1 (1),
wincamelphase2 (2),
wincamelphase3 (3),
wincamelphase4 (4),
wininapphaseericsson (8),
wininapphasesiemens (16),
wininapphasenortel (24),
wininapphase902 (32),
wininapphasechina (128),
wininapphasebrazil (136),
wininapphaserussion (144),
wininapphaseuk (152),
wincamelbutt (255)
}
3.19 cARPcARP (short for Circuit Assignment Reserve Priority) indicates the CARP value registered by the subscriber. The ASN.1 encoding of this field is as follows:
CARP ::= INTEGER(0..255)
3.20 CategoryThis field contains the Category information saved in the MSC/VLR by the HLR through inserting subscriber data during location updating. The ASN.1 encoding of this field is as follows:
SubscriberCategory ::= OCTET STRING (SIZE (1))
-- unknownuser = 00,
-- frenchuser = 01,
-- englishuser = 02,
-- germanuser = 03,
-- russianuser = 04,
-- spanishuser = 05,
-- specialuser = 06,
-- reserveuser = 09,
-- commonuser = 0a,
-- superioruser = 0b,
-- datacalluser = 0c,
-- testcalluser = 0d,
-- spareuser = 0e,
-- payphoneuser = 0f,
-- coinuser = 20,
-- isup224 = 0xe0
3.21 chargedPartyThis field indicates whether the calling party or the called party is charged or it indicates whether the call is charged. This field may be modified by the SCP. The ASN.1 encoding of this field is as follows:
ChargedParty ::= ENUMERATED
{
callingParty (0),
calledParty (1)
}
3.22 classmark3This field contains the radio access capability information about the MS. The ASN.1 encoding of this field is as follows:
Classmark3 ::= OCTET STRING(SIZE(2))
3.23 concatenatedSMSReferenceNumberThis field indicates that if the length of a short message exceeds the maximum length (140 bytes), the MS splits the short message into several short messages. To correlate these split
segments, the protocol uses the same concatenated SMS reference numbers (CSRNs) to identify the segments. The sequence number of the current SMS increases by one for each split segment. The maximum number of SMS in the concatenated SMS indicated the number of split segments.
Figure 3-1 shows the method of splitting the short message.
Figure 3-1 Method of splitting the short message
For example, the subscriber sends two messages in two segments and in four segments respectively.
Concatenated SMS Reference Number
Maximum Number Of SMS In The Concatenated SMS
Sequence Number Of The Current SMS
First Segment
Second Segment
… Last Segment
Picture1 X 2 1 2
Picture2 Y 4 1 2 3 4
The ASN.1 encoding of this field is as follows:
ConcatenatedSMSReferenceNumber ::= INTEGER(0..65535)
3.24 csReferenceThis field indicates that a call segment may contain one or multiple call legs, and the call legs are controlled by the same SSF. This field identifies the call segment used for communication by all the participants in a call.
The ASN.1 encoding of this field is as follows:
CAMELCSReference ::= OCTET STRING (SIZE (1..8))
3.25 csaReferenceThis field indicates that a CSA may contain one or multiple call segments, the call legs in different call segments within the same CSA. This field is used to correlate the CSA flags of the call segments. The ASN.1 encoding of this field is as follows:
CAMELCSAReference ::= INTEGER (0..4294967295)
3.26 cUGIndexA value assigned by the network to identify a CUG, the CUG index has significance only between the subscriber and network.
The ASN.1 encoding of this field is as follows:
CUGIndex ::= OCTET STRING(SIZE (2))
3.27 cUGOutgoingAccessIndicatorThis field indicates the subscriber with an Outgoing Access. The ASN.1 encoding of this field is as follows:
CUGOutgoingAccessIndicator ::= ENUMERATED
{
notCUGCall (0),
cUGCall (1)
}
3.28 cUGInterlockCodeThis field is used by the network (not by the MS) to identify CUG membership at MOC, MTC, CFW, and ROAM. The ASN.1 encoding of this field is as follows:
CUG Interlock Code = Network code + CUG interlock
CUGInterlockCode ::= OCTET STRING (SIZE (4))
3.29 cUGOutgoingAccessUsed/ cUGIncomingAccessUsedThis field indicates caller and called whether or not is in the same CUG group.
The ASN.1 encoding of this field is as follows:
CUGOutgoingAccessUsed ::= ENUMERATED
{
callInTheSameCUGGroup (0),
callNotInTheSameCUGGroup (1)
}
3.30 causeForTermThis field contains a generalized reason for the release of the connection including the following:
Normal release;
CAMEL initiated call release;
Partial record generation;
Partial record call re-establishment;
Unsuccessful call attempt;
Abnormal termination during the stable phase;
Unauthorized network originating a location service request;
Unauthorized client requesting a location service;
Position method failure at a location service execution;
Unknown or unreachable LCS client at a location service request.
A more detailed reason may be found in section 3.35 "Diagnostics."
The ASN.1 encoding of this field is as follows:
CauseForTerm ::= INTEGER
--
-- Cause codes from 16 up to 31 are defined in TS 32.015 as 'CauseForRecClosing'
-- (cause for record closing).
-- There is no direct correlation between these two types.
-- LCS related causes belong to the MAP error causes acc. TS 29.002.
--
{
normalRelease (0),
partialRecord (1),
partialRecordCallReestablishment (2),
unsuccessfulCallAttempt (3),
stableCallAbnormalTermination (4),
cAMELInitCallRelease (5),
cAMELCPHCallConfigurationChange (6),
unauthorizedRequestingNetwork (52),
unauthorizedLCSClient (53),
positionMethodFailure (54),
unknownOrUnreachableLCSClient (58)
}
3.31 cmnFlagThis field indicates whether the CMN call is invoked.
The ASN.1 encoding of this field is as follows:
CmnFlag ::= ENUMERATED
{
notCmnCall (0),
isCmnCall (1)
}
3.32 defaultCallHandling /defaultSMSHandlingThis field indicates whether or not a CAMEL encountered default call/SMS handling. This field shall be present only if default call/SMS handling has been applied. Parameter is defined in HLR as part of CAMEL subscription information.
The ASN.1 encoding of this field is as follows:
DefaultCallHandling ::= ENUMERATED
{
continueCall (0),
releaseCall (1)
}
3.33 destinationNumberThis field contains the destination number in case of SMS MT.
The ASN.1 encoding of this field is as follows:
DestinationRoutingAddress ::= BCDDirectoryNumber
3.34 destinationRoutingAddressThis field contains called party destinationRoutingAddresscalled number modified by CAMEL flow. The ASN.1 encoding of this field is as follows:
DestinationRoutingAddress ::= BCDDirectoryNumber
3.35 DiagnosticsThis field contains a more detailed technical reason for the release of the connection and may contain one of the following:
a MAP error from TS 29.002;
a Cause from TS 24.008;
a Cause from TS 29.078;
a Cause from ITU-T Recommendation Q.767;
The diagnostics may also be extended to include manufacturer and network specific information.
The technical cause value in this field is set as follows, according to the description in the protocol:
The most significant bit is always set to 1 as an extended bit.
The less significant seven bits are set to the technical cause value defined in the protocol.
For example 24.008 cause
{
unassigned-or-unallocated-number (0x01),
no-route-to-destination (0x03),
channel-unacceptable (0x06),
operator-determined-barring (0x08),
normal-call-clearing (0x10),
user-busy (0x11),
no-user-responding (0x12),
user-alerting-no-answer (0x13),
call-rejected (0x15),
number-changed (0x16),
pre-emption (0x19),
non-selected-user-clearing (0x1a),
destination-out-of-order (0x1b),
invalid-number-format-incomplete-number (0x1c),
facility-rejected (0x1d),
response-to-status-enquiry (0x1e),
normal-unspecified (0x1f),
no-circuit-channel-available (0x22),
network-out-of-order (0x26),
temporary-failure (0x29),
switching-equipment-congestion (0x2a),
access-information-discarded (0x2b),
requested-circuit-channel-not-available (0x2c),
resources-unavailable-unspecified (0x2f),
quality-of-service-unavailable (0x31),
requested-facility-not-subscribed (0x32),
incoming-calls-barred-within-the-cug (0x37),
bearer-capability-not-authorized (0x39),
bearer-capability-not-presently-available (0x3a),
service-or-option-not-available-unspecified(0x3f),
bearer-service-not-implemented (0x41),
acm-equal-to-or-greater-than-acmmax (0x44),
requested-facility-not-implemented (0x45),
only-restricted-digital-information-bearer-capability-is-available(0x46),
service-or-option-not-implemented-unspecified (0x4f),
invalid-transaction-identifier-value (0x51),
user-not-member-of-cug (0x57),
incompatible-destination (0x58),
invalid-transit-network-selection (0x5b),
semantically-incorrect-message (0x5f),
invalid-mandatory-information (0x60),
message-type-non-existent-or-not-implemented (0x61),
message-type-not-compatible-with-protocol-state (0x62),
information-element-non-existent-or-not-implemented (0x63),
conditional-ie-error (0x64),
message-not-compatible-with-protocol-state (0x65),
recovery-on-timer-expiry (0x66),
protocol-error-unspecified (0x6f),
interworking-unspecified (0x7f)
}
The ASN.1 encoding of this field is as follows:
Diagnostics ::= CHOICE
{
gsm0408Cause [0] INTEGER,
-- See TS 24.008
gsm0902MapErrorValue [1] INTEGER,
-- Note: The value to be stored here corresponds to
-- the local values defined in the MAP-Errors and
-- MAP-DialogueInformation modules, for full details
-- see TS 29.002.
ccittQ767Cause [2] INTEGER,
-- See ITU-T Q.767
networkSpecificCause [3] ManagementExtension,
-- To be defined by network operator
manufacturerSpecificCause [4] ManagementExtension
-- To be defined by manufacturer
}
3.36 disconnectPartyThis field indicates the disconnect party in the CDR. The ASN.1 encoding of this field is as follows:
Disconnectparty ::= ENUMERATED
{
unknown (0),
callingPartyRelease (1),
calledPartyRelease (2),
networkRelease (3)
}
3.37 eaSubscriberInfoThis field indicates the calling subscriber’s information of Equal Access. The ASN.1 encoding of this field is as follows:
EASubscriberInfo ::= OCTET STRING (SIZE (3))
-- The internal structure is defined by the Carrier Identification
-- parameter in ANSI T1.113.3. Carrier codes between "000" and "999"
-- may be encoded as 3 digits using "000" to "999" or as 4 digits
-- using "0000" to "0999". Carrier codes between "1000" and "9999" are
-- encoded using 4 digits.
3.38 eCategoryThis field indicates the enhanced subscriber category. The ASN.1 encoding of this field is as follows:
ECategory ::= INTEGER (0..255)
3.39 emsDigitsThis field only applies to location for an emergency services call in North America and gives the North American Emergency Services Routing Digits as defined in 3PGPP TS 29.002. The ASN.1 encoding of this field is as follows:
emsDigits ::= ISDN-AddressString,
3.40 emsKeyThis field only applies to location for an emergency services call in North America and gives the North American Emergency Services Routing Key as defined in 3GPP TS 29.002. The ASN.1 encoding of this field is as follows:
emsKey ::= ISDN-AddressString,
3.41 equipmentIdThis field contains a local identifier used to distinguish between equipment of the same equipment type e.g. the number of the conference circuit employed if more than one is available. The ASN.1 encoding of this field is as follows:
EquipmentId ::= INTEGER
3.42 equipmentTypeThis field contains the type of common equipment employed e.g. conference circuit for multi-party service. The ASN.1 encoding of this field is as follows:
EquipmentType ::= INTEGER
{
conferenceBridge (0)
}
3.43 eventTimeStampseventTimeStamps contain the event time stamps relevant for various record types. Usually, these fields can be setupTime, seizureTime, alertingTime, answerTime, releaseTime, originationTime, deliveryTime, ssActionTime, interrogationTime, and eventTime. These fields contain the event time stamps relevant to each of the individual record types. The call records may contain five significant call handling time stamps:
The time at which the setup (or IAM) was received (Setup time).
The time at which the resource in question was seized (Seizure time).
The time at which the call was alerting (Alerting time).
The time at which the call was answered or at which charging commences (Answer time).
The time at which the resource was released (Release time).
For both Mobile Originated and Mobile Terminated calls, the Setup time is the time at which the setup (or IAM) message from calling side is received.
For both Mobile Originated and Mobile Terminated calls, the Seizure time is the time at which the traffic channel is allocated i.e. the time at which the ASSIGN COMMAND message is sent to the MS.
For both Mobile Originated and Mobile Terminated calls, the Alerting time is the time at which the alerting (or ACM) message from called side is received.
For successful calls, the Answer time is mandatory and both the Seizure and Release times are optional. The call duration recorded is the chargeable duration i.e. the difference between the Answer and Release time stamps.
For Mobile Originated calls the Answer time is the time at which the CONNECT message is sent to the calling party. For Mobile Terminated calls the time at which the CONNECT message is received from the called party. In case of call re-establishment the answer time is the time at which the new traffic channel is allocated by the MSC i.e. when the ASSIGN COMMAND is sent to the MS.
The Release time is the time at which the connection is released by either party i.e. a DISCONNECT or RELEASE is sent by the network or a DISCONNECT is received from the MS. In the case of a radio link failure, the release time is the time at which the failure was detected by the MSC.
The event records include the following time stamps:
HLR-int time: The receipt of a MAP_SEND_ROUTING_INFO request by the HLR.
The receipt of a MAP_UPDATE_LOCATION_AREA request by the VLR or the receipt of a MAP_UPDATE_LOCATION request by the HLR.
SS-Action: The receipt of a supplementary service request by the VLR. e.g. MAP_REGISTER_SS, MAP_INVOKE_SS
SMS-MO: The receipt of an RP_DATA message from the MS containing an SMS_SUBMIT PDU.
SMS-MT: The transmission of an RP_DATA message to the MS containing an SMS_DELIVER PDU.
All time-stamps include a minimum of date, hour, minute and second.
For the ASN.1 encoding of this field, see section 3.6 "bCategory."
3.44 firstmccmnc/intermediatemccmnc/lastmccmncThe MCC and MNC represent country code and mobile network code. For specific MCCs and MNCs, refer to the 3GPP TS 24.008. For example, the country code of China is 460, and the MNC of China Mobile is 00.
The ASN.1 encoding of this field is as follows:
MCCMNC ::= OCTET STRING(SIZE(3))
-- This type contains the mobile country code (MCC) and the mobile
-- network code (MNC) of a PLMN.
3.45 fnurThis field indicates the user data rate applied for the connection in the fixed network. In UMTS, it shall be present for all bearer services as specified in TS 22.002. In GSM, this parameter is part of the HSCSD connection parameters.
The ASN.1 encoding of this field is as follows:
Fnur ::= ENUMERATED
{
--
-- See Bearer Capability TS 24.008
--
fnurNotApplicable (0),
fnur9600-BitsPerSecond (1),
fnur14400BitsPerSecond (2),
fnur19200BitsPerSecond (3),
fnur28800BitsPerSecond (4),
fnur38400BitsPerSecond (5),
fnur48000BitsPerSecond (6),
fnur56000BitsPerSecond (7),
fnur64000BitsPerSecond (8),
fnur33600BitsPerSecond (9),
fnur32000BitsPerSecond (10),
fnur31200BitsPerSecond (11)
}
3.46 freeFormatDataThis field contains charging information sent by the gsmSCF in the Furnish Charging Information (FCI) messages as defined in TS 29.078. The data can be sent either in one FCI message or several FCI messages with append indicator. This data is transferred transparently in the CAMEL clauses of the relevant call records. 'Free format data' sent to the legID=1 is always stored in the top level of the respective record. 'Free format data' sent to the legID >1 is stored in the appropriate CAMEL call leg information field.
If the FCI is received more then once during one continuing incoming/outgoing CAMEL call leg, the append indicator defines whether the FCI information is appended to previous FCI and stored in the relevant record or the information of the last FCI received is stored in the relevant record (the previous FCI information shall be overwritten).
In the event of partial output the currently valid 'Free format data' is stored in the partial record.
The ASN.1 encoding of this field is as follows:
FreeFormatData ::= OCTET STRING (SIZE(1..160))
3.47 freeFormatDataAppendThis field contains an indicator whether free format data is to be appended to free format data stored in previous partial CDR. This field is needed in CDR post-processing to sort out valid free format data for that call leg from sequence of partial records. Creation of partial records
is independent on received FCIs and thus valid free format data may be divided to different partial records.
If field is missing then free format data in this CDR replaces all received free format data in previous CDRs. Append indicator is not needed in the first partial record. In following partial records indicator shall get value true if all FCIs received during that partial record have append indicator. If one or more of the received FCIs for that call leg during the partial record do not have append indicator then this field shall be missing.
The ASN.1 encoding of this field is as follows:
freeFormatDataAppend ::= BOOLEAN,
3.48 globalAreaID / changeOfglobalAreaIDThis field contains the GCGI in the GSM. This field is SAI for the WCDMA system. For details, refer to the 3GPP TS 24.008.
The ASN.1 encoding of globalAreaID is as follows:
Indicates GCI of GSM or SAI of WCDMA
GAI ::= OCTET STRING(SIZE(7))
--such as 64 F0 00 00 ABCD 1234
The ASN.1 encoding of changeOfglobalAreaID is as follows:
A list of changes in GCI / SAI each time-stamped.
ChangeOfglobalAreaID ::= SEQUENCE
{
location [0] GAI,
changeTime [1] TimeStamp
}
3.49 guaranteedBitRateThis field contains the Guaranteed Bit Rate based on the FNUR for transparent and Wanted AIUR for non-transparent CS data services based on the described mapping in TS 27.001 or AMR speech. The bit-rate of the UMTS bearer service shall guarantee to the user or applications refer 3GPP TS 22.002.
The ASN.1 encoding of this field is as follows:
GuaranteedBitRate ::= ENUMERATED
{
gBR14400BitsPerSecond (1), -- BS20 non-transparent
gBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
-- BS30 transparent and multimedia
gBR32000BitsPerSecond (3), -- BS30 multimedia
gBR33600BitsPerSecond (4), -- BS30 multimedia
gBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
gBR57600BitsPerSecond (6), -- BS20 non-transparent
gBR64000BitsPerSecond (7), -- BS30 transparent and multimedia
gBR12200BitsPerSecond (106), -- AMR speech
gBR10200BitsPerSecond (107), -- AMR speech
gBR7950BitsPerSecond (108), -- AMR speech
gBR7400BitsPerSecond (109), -- AMR speech
gBR6700BitsPerSecond (110), -- AMR speech
gBR5900BitsPerSecond (111), -- AMR speech
gBR5150BitsPerSecond (112), -- AMR speech
gBR4750BitsPerSecond (113), -- AMR speech
gBR23850BitsPerSecond (114), -- AMR speech
gBR15850BitsPerSecond (115), -- AMR speech
gBR12650BitsPerSecond (116), -- AMR speech
gBR8850BitsPerSecond (117), -- AMR speech
gBR6600BitsPerSecond (118) -- AMR speech
}
3.50 gsm-SCFAddressThis field indicates the CAMEL server that serves the subscriber. Address is defined in HLR as part of CAMEL subscription information.
The ASN.1 encoding of this field is as follows:
Gsm-SCFAddress ::= ISDNAddressString
3.51 groupCallTypeThis field indicates the type of a group call.
The ASN.1 encoding of this field is as follows:
TCallType ::= ENUMERATED
{
NORMAL_CALL_TYPE(0),
VGCS_CALL_TYPE(1),
VBS_CALL_TYPE(2)
}
3.52 groupCallReferenceThis field is the Reference No. of a group call, it is composed of decimal numerals and is a number of four bytes in inversed BCD system.
The ASN.1 encoding of this field is as follows:
GroupCallReference ::= OCTET STRING(SIZE(4))
3.53 hLCThis field contains the comprehensive contents of the high layer compatibility (hLC). For details, refer to ITU-T Q.931.
The ASN.1 encoding of this field is as follows:
HLC ::= OCTET STRING
3.54 hotbillingTagThis field indicates whether a user is a hotblling subscriber.
The ASN.1 encoding of this field is as follows:
HotBillingTag ::= INTEGER
3.55 interrogationResultThis field indicates the result of the interrogation on the routing from the MSC/VLR to the HLR. For details, refer to 3GPP TS 29.002. This field is provided only when the query fails.
The ASN.1 encoding of this field is as follows:
HLRIntResult ::= Diagnostics
3.56 imeiCheckEventThis field indicates the type of event that causes the IMEI check to take place.
Mobile originating call attempt
Mobile terminating call attempt
Mobile originating SMS
Mobile terminating SMS
Supplementary service actions performed by the subscriber
Location update
The ASN.1 encoding of this field is as follows:
IMEICheckEvent ::= INTEGER
{
mobileOriginatedCall (0),
mobileTerminatedCall (1),
smsMobileOriginating (2),
smsMobileTerminating (3),
ssAction (4),
locationUpdate (5)
}
3.57 imeiStatusThis field contains the result of the IMEI checking procedure: Greylisted, Blacklisted, Non-whitelisted.
The ASN.1 encoding of this field is as follows:
IMEIStatus ::= ENUMERATED
{
greyListedMobileEquipment (0),
blackListedMobileEquipment (1),
nonWhiteListedMobileEquipment (2)
}
3.58 initialCallAttemptFlagThis field indicates whether a call is originated from the GsmSCF.
The ASN.1 encoding of this field is as follows:
initialCallAttemptFlag ::= NULL,
3.59 interactionWithIPThis field indicates whether to play announcement to the subscriber and to start charging in the case that the SSP interacts with the GsmSCF.
The ASN.1 encoding of this field is as follows:
InteractionWithIP ::= NULL
3.60 iSDN-BCThis field contains the comprehensive contents of the bearer capability (BC). For details, refer to ITU-T Q.931.
The ASN.1 encoding of this field is as follows:
ISDN-BC ::= OCTET STRING
3.61 lcsCauseThis field provides the reason for an unsuccessful location request. For details, refer to3GPP TS 49.031.
The ASN.1 encoding of this field is as follows:
LCSCause ::= OCTET STRING (SIZE(1))
3.62 lcsClientIdentityThis field contains further information on the LCS Client identity:
Client External ID.
Client Dialed by MS ID.
Client Internal ID.
The ASN.1 encoding of this field is as follows:
LCSClientIdentity ::= SEQUENCE
{
lcsClientExternalID [0] LCSClientExternalID OPTIONAL,
lcsClientDialedByMS [1] AddressString OPTIONAL,
lcsClientInternalID [2] LCSClientInternalID OPTIONAL
}
LCSClientExternalID ::= SEQUENCE
{
externalAddress [0] AddressString OPTIONAL
-- extensionContainer [1] ExtensionContainer OPTIONAL
}
LCSClientInternalID ::= ENUMERATED
{
broadcastService (0),
o-andM-HPLMN (1),
o-andM-VPLMN (2),
anonymousLocation (3),
targetMSsubscribedService (4)
}
3.63 lcsClientTypeThis field contains the type of the LCS Client as defined in TS 29.002.
The ASN.1 encoding of this field is as follows:
LCSClientType ::= ENUMERATED
{
emergencyServices (0),
valueAddedServices (1),
plmnOperatorServices (2),
lawfulInterceptServices (3)
}
3.64 lcsPriorityThis field indicates the priority of the location request as defined in TS 49.031.
The ASN.1 encoding of this field is as follows:
LCS-Priority ::= OCTET STRING (SIZE (1))
-- 0 = highest priority
-- 1 = normal priority -- all other values treated as 1
3.65 lcsQosThis field indicates the Quality of Service (QoS) for a location request as defined in TS 49.031.
The ASN.1 encoding of this field is as follows:
LCSQoSInfo ::= SEQUENCE
{
horizontal-accuracy [0] Horizontal-Accuracy OPTIONAL,
verticalCoordinateRequest [1] NULL OPTIONAL,
vertical-accuracy [2] Vertical-Accuracy OPTIONAL,
responseTime [3] ResponseTime OPTIONAL
}
3.66 levelOfCAMELServiceThis field briefly describes the complexity of CAMEL invocation.
Basic indicates that CAMEL feature is invoked during the setup phase (e.g. to modify the destination) of the call only.
Online charging indicates that CAMEL supported AoC parameter were sent to the mobile station (the Send Charging Information message, SCI, is received from the gsmSCF).
Call duration supervision is set whenever the call duration supervision is applied in the gsmSSF of the VPLMN (apply charging message is received from the gsmSCF).
The ASN.1 encoding of this field is as follows:
LevelOfCAMELService ::= BIT STRING
{
basic (0),
callDurationSupervision (1),
onlineCharging (2),
callPartyHandling (3)
}
3.67 lLCThis field contains the comprehensive contents of the low layer compatibility (lLC). For details, refer to ITU-T Q.931.
The ASN.1 encoding of this field is as follows:
LLC ::= OCTET STRING
3.68 location / changeOfLocationThis field comprises two parts, the location area code (LAC) and the (CI).
The location field contains a combination of the Location Area Code (LAC) and Cell Identity (CI) of the cell in which the served party is currently located. Any change of location may be recorded in the change of location field along with the time at which the change took place.
The change of location field is optional and it is not required if partial records are generated when the location changes.
The LAC and CI are both 2 octet quantities coded according to TS 24.008.
The ASN.1 encoding of this field is as follows:
LocationAreaAndCell ::= SEQUENCE
{
locationAreaCode [0] LocationAreaCode,
cellIdentifier [1] CellId
--
-- For 2G the content of the Cell Identifier is defined by the Cell Id
-- refer TS 24.008 and for 3G by the Service Area Code refer TS 25.413.
--
}
LocationAreaCode ::= OCTET STRING (SIZE(2))
CellId ::= OCTET STRING (SIZE(2))
--
-- Coded according to TS 24.008
--
3.69 locationEstimateThis field indicates an estimate of a geographic location of a target MS according to TS 29.002.
The ASN.1 encoding of this field is as follows:
LocationEstimateType ::= ENUMERATED
{
currentLocation (0),
currentOrLastKnownLocation (1),
initialLocation (2),
activateDeferredLocation (3),
cancelDeferredLocation (4)
}
-- exception handling:
-- a ProvideSubscriberLocation-Arg containing an unrecognized
LocationEstimateType
-- shall be rejected by the receiver with a return error cause of unexpected data
value
3.70 locationTypeThis field contains the type of the location as defined in TS 29.002.
The ASN.1 encoding of this field is as follows:
LocationType ::= SEQUENCE
{
locationEstimateType [0] LocationEstimateType,
deferredLocationEventType [1] DeferredLocationEventType OPTIONAL
}
3.71 maximumBitRateThis field contains the Maximum Bit Rate based on the Fixed Network User Rate (FNUR) for transparent and Wanted Air Interface User Rate (WAIUR) for non-transparent CS data services based on the described mapping in TS 27.001. Or this field contains the Maximum Bit Rate of the AMR for voice services. For details, refer to 3GPP TS 27.001.
The ASN.1 encoding of this field is as follows:
MaximumBitRate ::= ENUMERATED
{
mBR14400BitsPerSecond (1), -- BS20 non-transparent
mBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
-- BS30 transparent and multimedia
mBR32000BitsPerSecond (3), -- BS30 multimedia
mBR33600BitsPerSecond (4), -- BS30 multimedia
mBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
mBR57600BitsPerSecond (6), -- BS20 non-transparent
mBR64000BitsPerSecond (7), -- BS30 transparent and multimedia
mBR12200BitsPerSecond (106), -- AMR speech
mBR10200BitsPerSecond (107), -- AMR speech
mBR7950BitsPerSecond (108), -- AMR speech
mBR7400BitsPerSecond (109), -- AMR speech
mBR6700BitsPerSecond (110), -- AMR speech
mBR5900BitsPerSecond (111), -- AMR speech
mBR5150BitsPerSecond (112), -- AMR speech
mBR4750BitsPerSecond (113), -- AMR speech
mBR23850BitsPerSecond (114), -- AMR speech
mBR15850BitsPerSecond (115), -- AMR speech
mBR12650BitsPerSecond (116), -- AMR speech
mBR8850BitsPerSecond (117), -- AMR speech
mBR6600BitsPerSecond (118) -- AMR speech
}
3.72 maximumNumberOfSMSInTheConcatenatedSMS
This field indicates the maximum number of SMS in the concatenated SMS.
The ASN.1 encoding of this field is as follows:
MaximumNumberOfSMSInTheConcatenatedSMS ::= INTEGER(0..255)
3.73 MCTTypeThis field indicates the MCT type of an MOC for which the malicious call trace (MCT) application is implemented.
The ASN.1 encoding of this field is as follows:
MCTType ::= ENUMERATED
{
MCTI (0),
MCTC (1)
}
3.74 measureDurationThis field contains the duration for the section of the location measurement corresponding to the location request and the location report messages.
The ASN.1 encoding of this field is as follows:
Measure Duration ::= INTEGER
--
-- The call duration in seconds.
-- For successful calls this is the chargeable duration.
-- For call attempts this is the call holding time.
--
3.75 messageReferenceThis field contains a unique message reference number allocated by the MS when transmitting a short message to the service center. This field corresponds to the TP-Message-Reference element of the SMS_SUBMIT PDU defined in 3GPP TS 23.040.
The ASN.1 encoding of this field is as follows:
MessageReference ::= OCTET STRING(size(1))
3.76 mlc-NumberThis field quotes an ISDN (E.164) number of a mobile location center (MLC).
The ASN.1 encoding of this field is as follows:
mlc-Number ISDN-AddressString
3.77 msClassmark / changeOfClassmarkThis field contains the mobile station classmark employed by the served MS on call set-up as defined in 3GPP TS 24.008 (excerpt from 3GPP TS 24.008 as follows). Any alteration in the
classmark during the connection may be recorded in the change of classmark field and will include the time at which the change took place.
The ASN.1 encoding of this field is as follows:
Classmark ::= OCTET STRING(size(3))
--
-- See Mobile station classmark 2 or 3 TS 24.008
--
3.78 modemTypeThis field indicates the type of the modem applied by the terminal from the network when implementing the data service.
The ASN.1 encoding of this field is as follows:
ModemType ::= ENUMERATED
{
none-modem (0),
modem-v21 (1),
modem-v22 (2),
modem-v22-bis (3),
modem-v23 (4),
modem-v26-ter (5),
modem-v32 (6),
modem-undef-interface (7),
modem-autobauding1 (8),
no-other-modem-type (31),
modem-v34 (33)
}
3.79 molr-TypeThis field quotes the type of MO-LR invoked as defined in3GPP TS 24.080.
The ASN.1 encoding of this field is as follows:
MOLR-Type ::= INTEGER
--0 locationEstimate
--1 assistanceData
--2 deCipheringKeys
3.80 mSCAddressThis field contains the ITU-T Recommendation E.164 number assigned to the MSC.
The ASN.1 encoding of this field is as follows:
MSCAddress ::= AddressString
3.81 mscIncomingCircuit / mscOutgoingCircuitThis field contains the trunk circuit assigned by the MSC to the call.
The ASN.1 encoding of this field is as follows:
MSCCIC ::= INTEGER(0..65535)
Circuit Identity Code 1 will be coded as 01 00
3.82 mscIncomingROUTE / mscOutgoingROUTEThis field contains the incoming route and outgoing route described as following:
The incoming route / outgoing route describes the trunk group name or trunk group ID on which the call comes from / routes to. For mobile originated/terminated calls this will generally be a BSS trunk or RNS route.
The ASN.1 encoding of this field is as follows:
ROUTE ::= CHOICE
{
rOUTENumber [0] INTEGER,
rOUTEName [1] GraphicString
}
3.83 mscIncomingRouteAttribute / mscOutgoingRouteAttribute
This field indicates the attribute of the incoming/outgoing route.
The ASN.1 encoding of this field is as follows:
RouteAttribute ::= ENUMERATED
{
cas (0),
tup (1),
isup (2),
pra (3),
bicc (4),
sip (5),
others (255)
}
3.84 mscServerIndicationThis field indicates whether the VT-CSI is activated in the VMSC, and it also indicates whether the TCAEML record is generated in the terminating office.
The ASN.1 encoding of this field is as follows:
mscServerIndication ::= BOOLEAN,
3.85 networkCallReferenceThis field is used to correlate call records from the originating MSC (when applicable), the GMSC, and the terminating MSC. As an optional function, it can also be used to correlate call records from the gsmSCF.
The ASN.1 encoding of this field is as follows:
NetworkCallReference ::= CallReferenceNumber
3.86 networkOperatorIdWhen the carriers use independent RAN and shared CN, this field is used to indicate the carrier for which the current record is generated so that the carrier can read the records correctly from the corresponding channels.
The ASN.1 encoding of this field is as follows:
NetworkOperatorId ::= OCTET STRING(SIZE(1))
3.87 notificationToMSUserThis field contains the applicable privacy notification to an MS user when the LR is invoked. For details, refer to TS 29.002.
The ASN.1 encoding of this field is as follows:
NotificationToMSUser ::= ENUMERATED
{
notifyLocationAllowed (0),
notifyAndVerify-LocationAllowedIfNoResponse (1),
notifyAndVerify-LocationNotAllowedIfNoResponse (2),
locationNotAllowed (3)
}
3.88 numberOfDPEncounteredThis field indicates the number of service triggering points and even detection points detected during a CAMEL service.
The ASN.1 encoding of this field is as follows:
numberOfDPEncountered ::= INTEGER,
3.89 numberOfForwardingThis field, if provided through the ISUP signaling, contains the number of times a call has been forwarded prior to the interrogation of the HLR as defined in TS 29.002.
The ASN.1 encoding of this field is as follows:
NumberOfForwarding ::= INTEGER (1..5)
3.90 originalCalledNumberThis field indicates the address of original called party in case of call forwarding.
The ASN.1 encoding of this field is as follows:
OriginalCalledNumber ::= BCDDirectoryNumber
3.91 originationThis field contains the originating short message subscriber number.
The ASN.1 encoding of this field is as follows:
TimeStamp ::= OCTET STRING (SIZE(9..10))
3.92 orgMSCIdThis field indicates the originating and terminating MSC SPC of an SMS.
The ASN.1 encoding of this field is as follows:
MSCId ::= OCTET STRING(SIZE (3))
--National network format , octet order is the same as ISUP signaling
--if spc is coded as 14bit, then OCTET STRING1 will filled with 00,,for example
rnc id = 123 will be coded as 00 01 23
--OCTET STRING1
--OCTET STRING2
--OCTET STRING3
3.93 orgRNCorBSCIdThis field contains the originating RNC or BSC SPC.
The ASN.1 encoding of this field is as follows:
RNCorBSCId ::= OCTET STRING(SIZE (3))
--octet order is the same as RANAP/BSSAP signaling
--if spc is coded as 14bit, then OCTET STRING1 will filled with 00 ,for example
rnc id = 123 will be coded as 00 01 23
--OCTET STRING1
--OCTET STRING2
--OCTET STRING3
3.94 partialRecordTypeThis field indicates the type of a partial record.
The ASN.1 encoding of this field is as follows:
PartialRecordType ::= ENUMERATED
{
timeLimit (0),
serviceChange (1),
locationChange (2),
classmarkChange (3),
aocParmChange (4),
radioChannelChange (5),
hSCSDParmChange (6),
changeOfCAMELDestination (7),
firstHotBill (20),
severalSSOperationBill (21),
iSTalertTimeOut (22),
bearRedirectStart (23),
bearRedirectStop (24)
}
3.95 partyRelCauseIndicates the cause of call release. The field includes two sub-fields: release type and release cause. When the release type is bssmap or ranap, the call release is caused by the wireless side.
PartyRelCause ::= SEQUENCE
{
releaseParty [0] ReleaseParty,
releaseCause [1] INTEGER
}
ReleaseParty ::= ENUMERATED
{
bssmap (0),
ranap (1),
dtap (2),
isup (3),
relbutt (255)
}
3.96 portedflagThis field indicates whether the served party uses the number ported service.
The ASN.1 encoding of this field is as follows:
PortedFlag ::= ENUMERATED
{
numberNotPorted (0),
numberPorted (1)
}
3.97 positioningDataThis field provides the positioning data associated with a location attempt for a target MS according TS 49.031.
The ASN.1 encoding of this field is as follows:
PositioningData ::= OCTET STRING (SIZE(1..33))
3.98 privacyOverrideThis field indicates whether the MS privacy is overridden by the LCS client when the GMLC and VMSC/SGSN for an MT-LR are in the same country as defined in TS 29.002.
The ASN.1 encoding of this field is as follows:
privacyOverride ::= NULL,
3.99 radioChanRequested/ radioChanUsed / changeOfRadioChan
This field contains three parts as the radio channel requested, radio channel used and the change of radio channel.
The radio channel requested field contains the type of channel requested by the user. The following values are permitted:
− Full rate
− Half rate
− Dual mode half rate preferred
− Dual mode full rate preferred
The ASN.1 encoding of this field is as follows:
RadioChanRequested ::= ENUMERATED
{
--
-- See Bearer Capability TS 24.008
--
halfRateChannel (0),
fullRateChannel (1),
dualHalfRatePreferred (2),
dualFullRatePreferred (3)
}
The radio channel used field indicates the type of the traffic channel actually employed for the connection as described in GSM 05.01. The following values are permitted:
− Full rate
− Half rate
The ASN.1 encoding of this field is as follows:
TrafficChannel ::= ENUMERATED
{
fullRate (0),
halfRate (1)
}
Any change in the type of channel used may be recorded in the change of radio channel used field along with the time at which the change occurs and the speech version used after the change of radio channel.
The ASN.1 encoding of this field is as follows:
ChangeOfRadioChannel ::= SEQUENCE
{
radioChannel [0] TrafficChannel,
changeTime [1] TimeStamp,
speechVersionUsed [2] SpeechVersionIdentifier OPTIONAL
}
3.100 rateIndicationThis field indicates the rate adaptation used for the connection. This field is constructed from the information in the parameters rate adaption and other rate adaption signaled between the MS/UE and the network. For details, refer to TS 24.008.
The ASN.1 encoding of this field is as follows:
The format of this field is a single octet with the following format:
Bits 0-1: the Rate Adaption field as defined in TS 24.008 ;
Bits 2-3: the Other Rate Adaption field as defined in TS 24.008 ;
Bits 4-7: not used.
RateIndication ::= OCTET STRING(SIZE(1))
--0 no rate adaption
--1 V.110, I.460/X.30
--2 ITU-T X.31 flag stuffing
--3 V.120
--7 H.223 & H.245
--11PIAFS
3.101 recordingEntityThis field contains the entity numbers, in ITU-T E.164 format, of the MSC, VLR, and HLR that generate records. For details, refer to 3GPP TS 23.003.
The ASN.1 encoding of this field is as follows:
RecordingEntity ::= AddressString
3.102 recordExtensionsThis field enables network operators and/ or manufacturers to add their own extensions to the standard record definitions. This field contains a set of management extensions defined in ITU-T X.721.
The ASN.1 encoding of this field is as follows:
ManagementExtensions ::= SET OF ManagementExtension
ManagementExtension ::= SEQUENCE
{
identifier OBJECT IDENTIFIER,
significance [1] BOOLEAN DEFAULT FALSE,
information [2] OCTET STRING
}
3.103 recordNumberThis field is used to record the record numbers of CDRs. The record number is incremented by 1 after each CDR is generated.
The ASN.1 encoding of this field is as follows:
RecordNumber ::= INTEGER
3.104 recordTypeThe field indicates the type of the record e.g. mobile originated, mobile terminated, call forwarding, etc.
The ASN.1 encoding of this field is as follows:
CallEventRecordType ::= INTEGER
{
moCallRecord (0),
mtCallRecord (1),
roamingRecord (2),
incGatewayRecord (3),
outGatewayRecord (4),
transitCallRecord (5),
moSMSRecord (6),
mtSMSRecord (7),
ssActionRecord (10),
hlrIntRecord (11),
commonEquipRecord (14),
moTraceRecord (15),
mtTraceRecord (16),
termCAMELRecord (17),
mtLCSRecord (23),
moLCSRecord (24),
niLCSRecord (25),
forwardCallRecord (100)
}
3.105 redirectingnumberThis field contains the number of the forwarding party.
The ASN.1 encoding of this field is as follows:
RedirectingNumber ::= BCDDirectoryNumber
3.106 redirectingcounterThis field indicates the forwarding times.
The ASN.1 encoding of this field is as follows:
RedirectingCounter ::= INTEGER
3.107 resourceChargeIPnumberIn the case of interaction between SSP and IP, this field indicates the number of the equipment that plays the announcement to the subscriber under the control of the GsmSCF.
The ASN.1 encoding of this field is as follows:
ResourceCharge IP number ::= AddressString
3.108 Roaming numberThis field contains the MS roaming number as defined in 3GPP TS 23.003 and coded according to 3GPP TS 29.002.
The ASN.1 encoding of this field is as follows:
RoamingNumber ::= ISDN-AddressString
3.109 routingNumberThe routing number field of the HLR interrogation record contains either an MS roaming number or, in case of call forwarding, a forwarded-to number.
The ASN.1 encoding of this field is as follows:
RoutingNumber ::= CHOICE
{
roaming [1] RoamingNumber,
forwarded [2] ForwardToNumber
}
3.110 sequenceNumberThis field contains a dynamic sequence number employed to link the partial records generated for a particular connection. The record is generated for the first part of a call, and it begins with 1.
The ASN.1 encoding of this field is as follows:
SequenceNumber ::= INTEGER
3.111 servedIMEIThis field contains the international mobile equipment identity (IMEI) of the equipment served. The term served equipment refers to calling MS in the record generated for the calling party and called MS in the record generated for the called MS. The structure of the IMEI is defined in 3GPP TS 23.003. Figure 3-1 shows the structure of the IMEI.
Figure 3-1 Structure of the IMEI
The IMEI is composed of the following elements (each element shall consist of decimal digits only):
Type Allocation Code (TAC): It is a string of six digits used to identify the manufacturer and type of the terminal.
Facility Allocation Code (FAC): It is used to identify the manufacturing and packing locations of the terminal.
Serial Number (SNR): It is an individual serial number uniquely identifies the terminal when the TAC and FAC of the terminal are provided.
Spare digit: This field is permanently set to 0.
The structure of the IMEISV which is the combination of the IMEI and the SVN is shown in the following figure:
The difference between the IMEISV and the IMEI is the software version number (SVN) which indicates the software version information of the currently used terminal. Besides, there is no spare digit in the IMEISV.
The ASN.1 encoding of this field is as follows:
IMEI ::= TBCD-STRING (SIZE (8))
3.112 servedIMSI/calledIMSIThis field contains the international mobile subscriber identity (IMSI) of the served party. The term "served" party is used to describe the mobile subscriber involved in the transaction recorded e.g. the calling subscriber in case of an MOC record.
Figure 3-1 shows the structure of the IMSI defined in 3GPP TS 23.003.
Figure 3-1 Structure of the IMSI
IMSI is composed of three parts:
Mobile Country Code (MCC): The MCC identifies uniquely the country of domicile of the mobile subscriber;
Mobile Network Code (MNC): The MNC identifies the home PLMN of the mobile subscriber;
Mobile Subscriber Identification Number (MSIN): It identifies uniquely the mobile subscriber within a PLMN.
The ASN.1 encoding of this field is as follows:
IMSI ::= TBCD-STRING (SIZE (3..8))
-- digits of MCC, MNC, MSIN are concatenated in this order.
3.113 servedMSISDNThis field contains the MS ISDN number (MSISDN) of the served party. The term "served party" is used to describe the mobile subscriber involved in the transaction recorded, for example, the called party in an MTC. The structure of the MSISDN is defined in 3GPP TS 23.003. Figure 3-1 shows the structure of the MSISDN defined in 3GPP TS 23.003.
Figure 3-1 Structure of the MSISDN
The MSISDN is composed of two parts:
Country Code (CC): It identifies the country in which the MS is registered.
National Destination Code (NDC): It identifies the mobile access number.
Subscriber Number (SN): It identifies the number of the mobile subscriber.
The ASN.1 encoding of this field is as follows:
MSISDN ::= ISDN-AddressString
3.114 serviceCentreThis field contains a ITU-T Recommendation E.164 number identifying a particular service center e.g. short message service centre (see TS 23.040).
The ASN.1 encoding of this field is as follows:
serviceCentre AddressString
3.115 serviceKeyThis field identifies the CAMEL service logic applied. Service key is defined in HLR as part of CAMEL subscription information.
The ASN.1 encoding of this field is as follows:
ServiceKey ::= INTEGER (0..2147483647)
3.116 smsResultThis field contains the result of an attempt to deliver a short message. For details, refer to 3GPP TS 29.002.
The ASN.1 encoding of this field is as follows:
SMSResult ::= Diagnostics
3.117 speechVersionSupported/speechVersionUsed
The field speechVersionSupported/speechVersionUsed consists two parts as follows. The speech version supported field contains the speech version supported by the MS with the highest priority. The speech version used field contains the speech codec version assigned for that call. The coding is according to 3GPP TS 08.08, and the extension bit 8 is set to 0.
It should be noted that the change of radio channel field is optional and not required if partial records are generated.
The ASN.1 encoding of this field is as follows:
SpeechVersionIdentifier ::= OCTET STRING (SIZE(1))
-- see GSM 08.08
-- 000 0001 GSM speech full rate version 1
-- 001 0001 GSM speech full rate version 2 used for enhanced full rate
-- 010 0001 GSM speech full rate version 3 for future use
-- 000 0101 GSM speech half rate version 1
-- 001 0101 GSM speech half rate version 2 for future use
-- 010 0101 GSM speech half rate version 3 for future use
3.118 systemTypeThis field indicates whether the current air interface used is GERAN or UTRAN (or a value of unknown).
The ASN.1 encoding of this field is as follows:
SystemType ::= ENUMERATED
{
unknown (0),
iuUTRAN (1),
gERAN (2)
}
3.119 supplServiceUsed/supplServiceThis field contains the code of the supplementary service on which the action was performed.For details on the coding of the supplementary service code, refer to TS 29.002.
The ASN.1 encoding of this field is as follows:
SS-Code ::= OCTET STRING (SIZE (1))
-- This type is used to represent the code identifying a single
-- supplementary service, a group of supplementary services, or
-- all supplementary services. The services and abbreviations
-- used are defined in TS 3GPP TS 22.004. The internal structure is
-- defined as follows:
--
-- bits 87654321: group (bits 8765), and specific service
-- (bits 4321) USSD = ff
-- allSS (0x00),
-- reserved for possible future use
-- all SS
--
-- allLineIdentificationSS (0x10),
-- reserved for possible future use
-- all line identification SS
--
-- calling-line-identification-presentation (0x11),
-- calling line identification presentation
-- calling-line-identification-restriction (0x12),
-- calling line identification restriction
-- connected-line-identification-presentation (0x13),
-- connected line identification presentation
-- connected-line-identification-restriction (0x14),
-- connected line identification restriction
-- malicious-call-identification (0x15),
-- reserved for possible future use
-- malicious call identification
--
-- allNameIdentificationSS (0x18),
-- all name identification SS
-- calling-name-presentation (0x19),
-- calling name presentation
--
-- SS-Codes '00011010'B, to '00011111'B, are reserved for future
-- NameIdentification Supplementary Service use.
--
-- allForwardingSS (0x20),
-- all forwarding SS
-- call-forwarding-unconditional (0x21),
-- call forwarding unconditional
-- call-deflection (0x24),
-- call deflection
-- allCondForwardingSS (0x28),
-- all conditional forwarding SS
-- call-forwarding-on-mobile-subscriber-busy (0x29),
-- call forwarding on mobile subscriber busy
-- call-forwarding-on-no-reply (0x2a),
-- call forwarding on no reply
-- call-forwarding-on-mobile-subscriber-not-reachable (0x2b),
-- call forwarding on mobile subscriber not reachable
--
-- allCallOfferingSS (0x30),
-- reserved for possible future use
-- all call offering SS includes also all forwarding SS
--
-- explicit-call-transfer (0x31),
-- explicit call transfer
-- mobile-access-hunting (0x32),
-- reserved for possible future use
-- mobile access hunting
--
-- allCallCompletionSS (0x40),
-- reserved for possible future use
-- all Call completion SS
--
-- call-waiting (0x41),
-- call waiting
-- call-hold (0x42),
-- call hold
-- completion-of-call-to-busy-subscribers-originating-side (0x43),
-- completion of call to busy subscribers, originating side
-- completion-of-call-to-busy-subscribers-destination-side (0x44),
-- completion of call to busy subscribers, destination side
-- this SS-Code is used only in InsertSubscriberData and DeleteSubscriberData
--
-- multicall (0x45),
-- multicall
--
-- allMultiPartySS (0x50),
-- reserved for possible future use
-- all multiparty SS
--
-- multiPTY (0x51),
-- multiparty
--
-- allCommunityOfInterest-SS (0x60),
-- reserved for possible future use
-- all community of interest SS
-- closed-user-group (0x61),
-- closed user group
--
-- allChargingSS (0x70),
-- reserved for possible future use
-- all charging SS
-- advice-of-charge-information (0x71),
-- advice of charge information
-- advice-of-charge-charging (0x72),
-- advice of charge charging
--
-- allAdditionalInfoTransferSS (0x80),
-- reserved for possible future use
-- all additional information transfer SS
-- uUS1-user-to-user-signalling (0x81),
-- UUS1 user-to-user signalling
-- uUS2-user-to-user-signalling (0x82),
-- UUS2 user-to-user signalling
-- uUS3-user-to-user-signalling (0x83),
-- UUS3 user-to-user signalling
--
-- allBarringSS (0x90),
-- all barring SS
-- barringOfOutgoingCalls (0x91),
-- barring of outgoing calls
-- barring-of-all-outgoing-calls (0x92),
-- barring of all outgoing calls
-- barring-of-outgoing-international-calls (0x93),
-- barring of outgoing international calls
-- boicExHC (0x94),
-- barring of outgoing international calls except those directed
-- to the home PLMN
-- barringOfIncomingCalls (0x99),
-- barring of incoming calls
-- barring-of-all-incoming-calls (0x9a),
-- barring of all incoming calls
-- barring-of-incoming-calls-when-roaming-outside-home-PLMN-Country
(0x9b),
-- barring of incoming calls when roaming outside home PLMN
-- Country
--
-- allCallPrioritySS (0xa0),
-- reserved for possible future use
-- all call priority SS
-- enhanced-Multilevel-Precedence-Pre-emption-EMLPP-service (0xa1),
-- enhanced Multilevel Precedence Pre-emption 'EMLPP) service
--
-- allLCSPrivacyException (0xb0),
-- all LCS Privacy Exception Classes
-- universal (0xb1),
-- allow location by any LCS client
-- callrelated (0xb2),
-- allow location by any value added LCS client to which a call
-- is established from the target MS
-- callunrelated (0xb3),
-- allow location by designated external value added LCS clients
-- plmnoperator (0xb4),
-- allow location by designated PLMN operator LCS clients
--
-- allMOLR-SS (0xc0),
-- all Mobile Originating Location Request Classes
-- basicSelfLocation (0xc1),
-- allow an MS to request its own location
-- autonomousSelfLocation (0xc2),
-- allow an MS to perform self location without interaction
-- with the PLMN for a predetermined period of time
-- transferToThirdParty (0xc3),
-- allow an MS to request transfer of its location to another LCS client
--
-- allPLMN-specificSS (0xf0),
-- plmn-specificSS-1 (0xf1),
-- plmn-specificSS-2 (0xf2),
-- plmn-specificSS-3 (0xf3),
-- plmn-specificSS-4 (0xf4),
-- plmn-specificSS-5 (0xf5),
-- plmn-specificSS-6 (0xf6),
-- plmn-specificSS-7 (0xf7),
-- plmn-specificSS-8 (0xf8),
-- plmn-specificSS-9 (0xf9),
-- plmn-specificSS-A (0xfa),
-- plmn-specificSS-B (0xfb),
-- plmn-specificSS-C (0xfc),
-- plmn-specificSS-D (0xfd),
-- plmn-specificSS-E (0xfe),
-- USSD (0xff)
3.120 ssActionThis field contains the type of supplementary service action requested by the subscriber or performed by the network.
The ASN.1 encoding of this field is as follows:
SSActionType ::= ENUMERATED
{
registration (0),
erasure (1),
activation (2),
deactivation (3),
interrogation (4),
invocation (5),
passwordRegistration (6),
USSDInvocation (7)
}
-- USSDInvocation (7) include USSD phase 1,phase 2
3.121 ssActionResultThis field contains the result of an attempted supplementary service action (refer to 3GPP TS 29.002). Note that this field is only provided if the SS-action is at least partially unsuccessful.
The ASN.1 encoding of this field is as follows:
SSActionResult ::= Diagnostics
3.122 ssParametersThis field contains the parameters associated with a supplementary service action requested by the subscriber. For further details of the parameters involved see the GSM 02.8n series of documents.
In the supplementary service record generated for USSD, the corresponding fields are filled with the following values:
Supplementary service parameters field: USSD
SSActionType: ussdInvocation(7)
Supplementary service code: 0
Basic service code: not be coded into ASN.1
In the supplementary service record generated for call forwarding, the supplementary service parameters field is filled with the forwarded-to number.
The ASN.1 encoding of this field is as follows:
SSParameters ::= CHOICE
{
forwardedToNumber [0] ForwardToNumber,
unstructuredData [1] OCTET STRING
}
3.123 smstextThis field records the contents of the short message when the SMS uses text format.
The ASN.1 encoding of this field is as follows:
SMSTEXT ::= OCTET STRING
3.124 smsUserDataTypeThis field indicates the information on the subscriber type contained in the short message sent.
The ASN.1 encoding of this field is as follows:
SmsUserDataType ::= OCTET STRING (SIZE (1))
--00 concatenated-short-messages-8-bit-reference-number
--01 special-sms-message-indication
--02 reserved
--03 Value not used to avoid misinterpretation as <LF>
--04 characterapplication-port-addressing-scheme-8-bit-address
--05 application-port-addressing-scheme-16-bit-address
--06 smsc-control-parameters
--07 udh-source-indicator
--08 concatenated-short-message-16-bit-reference-number
--09 wireless-control-message-protocol
--0A text-formatting
--0B predefined-sound
--0C user-defined-sound-imelody-max-128-bytes
--0D predefined-animation
--0E large-animation-16-16-times-4-32-4-128-bytes
--0F small-animation-8-8-times-4-8-4-32-bytes
--10 large-picture-32-32-128-bytes
--11 small-picture-16-16-32-bytes
--12 variable-picture
--13 User prompt indicator
--14 Extended Object
--15 Reused Extended Object
--16 Compression Control
--17 Object Distribution Indicator
--18 Standard WVG object
--19 Character Size WVG object
--1A Extended Object Data Request Command
--1B-1F Reserved for future EMS features
--20 RFC 822 E-Mail Header
--21 Hyperlink format element
--22 Reply Address Element
--23 - 6F Reserved for future use
--70 - 7F (U)SIM Toolkit Security Headers
--80 - 9F SME to SME specific use
--A0 - BF Reserved for future use
--C0 - DF SC specific use
--E0 - FE Reserved for future use
--FF normal SMS
3.125 selectedCICThis field indicates the selected code of carrier identification used in the (North American equal access) NAEA service.
The ASN.1 encoding of this field is as follows:
SelectedCIC ::= OCTET STRING (SIZE (3))
3.126 sequenceNumberOfTheCurrentSMSThis field indicates the sequence number of the current short message in the concatenated short message. It is numbered from 1.
The ASN.1 encoding of this field is as follows:
SequenceNumberOfTheCurrentSMS ::= INTEGER(0..255)
3.127 subscriberCategoryThis field indicates the type of subscriber. The subscriber category information is stored in the MSC/VLR after it is inserted into the subscriber data flow by the HLR during the location update.
The ASN.1 encoding of this field is as follows:
SubscriberCategory ::= OCTET STRING (SIZE (1))
-- unknownuser = 00,
-- frenchuser = 01,
-- englishuser = 02,
-- germanuser = 03,
-- russianuser = 04,
-- spanishuser = 05,
-- specialuser = 06,
-- reserveuser = 09,
-- commonuser = 0a,
-- superioruser = 0b,
-- datacalluser = 0c,
-- testcalluser = 0d,
-- spareuser = 0e,
-- payphoneuser = 0f,
-- coinuser = 20,
-- isup224 = 0xe0
3.128 tariffCodeThis field indicates the tariff code of the cell.
The ASN.1 encoding of this field is as follows:
TariffCode ::= INTEGER (0..255)
3.129 transparencyIndicatorThis field indicates whether the basic service is employed in transparent or non-transparent mode. It should also be noted that this field is only relevant to those services which may be operated in both transparent and non-transparent modes.
The ASN.1 encoding of this field is as follows:
TransparencyInd ::= ENUMERATED
{
transparent (0),
nonTransparent (1)
}
3.130 typeOfSubscribersThis field indicates the roaming type of subscribers. The value all is not available currently.
The ASN.1 encoding of this field is as follows:
TypeOfSubscribers ::= ENUMERATED
{
home (0), -- HPLMN subscribers
visiting (1), -- roaming subscribers
all (2)
}
3.131 UsertypeThis field indicates the type of the user.
The ASN.1 encoding of this field is as follows:
UserType ::= ENUMERATED
{
gsmnormaluser (0),
gsmprepaiduser (1),
gsmcameluser (2),
gsmunknowuser (31)
}
3.132 ussdCodingSchemeThis field indicates the coding scheme of USSD in the case of the USSD service.
The ASN.1 encoding of this field is as follows:
UssdCodingScheme ::= OCTET STRING
3.133 ussdStringThis field indicates the subscriber input in the case of the USSD service.
The ASN.1 encoding of this field is as follows:
UssdString ::= OCTET STRING
3.134 ussdNotifyCounterThis field indicates the times of notify procedure in the case of the USSD service.
The ASN.1 encoding of this field is as follows:
UssdNotifyCounter ::= INTEGER(0..255)
3.135 ussdRequestCounterThis field indicates the times of request procedure in the case of the USSD service.
The ASN.1 encoding of this field is as follows:
UssdRequestCounter ::= INTEGER(0..255)
3.136 ussdCallBackFlagThis field indicates whether a USSD call back is originated by a CAMEL subscriber roaming aboard.
The ASN.1 encoding of this field is as follows:
ussdCallBackFlag ::= NULL,
3.137 uuslTypeThis field indicates the type of the UUS1 supplementary service.
The ASN.1 encoding of this field is as follows:
UUS1Type ::= ENUMERATED
{
UUS1_IMPLICIT(0),
UUS1_EXPLICIT_REQUIRED(1),
UUS1_EXPLICIT_NOT_REQUIRED(2),
UUS1_SS_UNUSED(3)
}
3.138 voiceIndicatorThis field indicates whether to connect the call or to play an announcement to the subscriber. It also indicates whether the local office or other offices play the announcement to the subscriber.
The ASN.1 encoding of this field is as follows:
VoiceIndicator ::= ENUMERATED
{
sendToneByLocalMsc(0) ,
sendToneByOtherMsc(1),
voiceNoIndication (3)
}
3.139 zoneCodeThis filed indicates the zone code of a cell.
The ASN.1 encoding of this field is as follows:
ZoneCode ::= OCTET STRING (SIZE(2))
4 ASN.1 Description of the CDR
File
The ASN.1 (BER) description of the CDR file describes the encoding of CDRs on the iGWB, which sends the encoded CDRs to the billing center. For detailed ASN.1 description of the CDR file, refer to Appendix A “CDR Encoding/Decoding Description.ASN”.
5 Examples of CDRs
This chapter describes the ANS.1-encoded CDRs of various services, such as voice calls, CS-domain bearer services, VP calls, SMS, HLR interrogation, USSD, supplementary services, and emergency calls. This chapter describes only the correlation between different CDRs and their examples. Detailed CDR examples in the ASN.1 encoding format and the text (after decoding) format are provided in "ASN.1 CDR example" in Appendix B "CDR Examples".
The suffix of an example of a CDR in the ASN.1 encoding format is dat.
The suffix of an example of a CDR in the decoded text format is txt.
Table 5-1 The correlation between CDRs and examples
Service Record Name
ASN.1 BER Code Record
Decoded Record
Voice Call MOC Record 001-ASN.1_MOC.dat 001-ASN.1_MOC.txt
MTC Record 002-ASN.1_MTC.dat 002-ASN.1_MTC.txt
Vp Call MOC Record 003-ASN.1_MOC.dat 003-ASN.1_MOC.txt
Other bear service call
MOC Record 004-ASN.1_MOC.dat 004-ASN.1_MOC.txt
Forwarding record
Forwarding record
005-ASN.1_CFW.dat 005-ASN.1_CFW.txt
Emergency record
Emergency call record
006-ASN.1_MOC.dat 006-ASN.1_MOC.txt
Middle billing partial record1 007-ASN.1_CallRecord(partial1)_MOC.dat
007-ASN.1_CallRecord(partial1)_MOC.txt
partial record2 008-ASN.1_CallRecord(partial2)_MOC.dat
008-ASN.1_CallRecord(partial2)_MOC.txt
Service Record Name
ASN.1 BER Code Record
Decoded Record
partial record3 009-ASN.1_CallRecord(partial3)_MOC.dat
009-ASN.1_CallRecord(partial3)_MOC.txt
partial record4 010-ASN.1_CallRecord(partial4)_MOC.dat
010-ASN.1_CallRecord(partial4)_MOC.txt
partial record5 011-ASN.1_CallRecord(partial5)_MOC.dat
011-ASN.1_CallRecord(partial5)_MOC.txt
partial record6 012-ASN.1_CallRecord(partial6)_MOC.dat
012-ASN.1_CallRecord(partial6)_MOC.txt
partial record7 013-ASN.1_CallRecord(partial7)_MOC.dat
013-ASN.1_CallRecord(partial7)_MOC.txt
Sms Sms MOC record
014-ASN.1_SMS_MOC.dat 014-ASN.1_SMS_MOC.txt
Sms MTC record
015-ASN.1_SMS_MTC.dat 015-ASN.1_SMS_MTC.txt
Concatenated Long Sms
Concatenated Long Sms1
016-ASN.1_SMS(partial1)_MOC.dat
016-ASN.1_SMS(partial1)_MOC.txt
Concatenated Long Sms2
017-ASN.1_SMS(partial2)_MOC.dat
017-ASN.1_SMS(partial2)_MOC.txt
Concatenated Long Sms3
018-ASN.1_SMS(partial3)_MOC.dat
018-ASN.1_SMS(partial3)_MOC.txt
Concatenated Long Sms4
019-ASN.1_SMS(partial4)_MOC.dat
019-ASN.1_SMS(partial4)_MOC.txt
Interrogation Interrogation record
020-ASN.1_Query_HLR.dat 020-ASN.1_Query_HLR.txt
USSD USSD record 021-ASN.1_SS_Act(USSD).dat
021-ASN.1_SS_Act(USSD).txt
Supplementary service
Forward registration
022-ASN.1_SS_Act(Forward).dat
022-ASN.1_SS_Act(Forward).txt
Handover Handover MOC record
023-ASN.1_Handover_MOC.dat
023-ASN.1_Handover_MOC.txt
Service Record Name
ASN.1 BER Code Record
Decoded Record
CommonEquipRecord
CommonEquipRecord
024-ASN.1_CommEquip.dat 024-ASN.1_CommEquip.txt
IncGatewayRecord
IncGateway Record
025-ASN.1_GWI.dat 025-ASN.1_GWI.txt
OutGatewayRecord
OutGateway Record
026-ASN.1_GWO.dat 026-ASN.1_GWO.txt
TransitCallRecord
TransitCall Record
027-ASN.1_Transit.dat 027-ASN.1_Transit.txt
RoamingRecord
Roaming Record
028-ASN.1_Roam.dat 028-ASN.1_Roam.txt
Moc(CAMEL) Moc(CAMEL) 029-ASN.1_MOC(Camel).dat
029-ASN.1_MOC(Camel).txt
Mtc(CAMEL) Mtc(CAMEL) 030-ASN.1_MTC(Camel).dat
030-ASN.1_MTC(Camel).txt
TCAMEL TCAMEL 031-ASN.1_Tcamel.dat 031-ASN.1_Tcamel.txt
Moc(FCI) Moc(FCI) 032-ASN.1_MOC(withFCI).dat
032-ASN.1_MOC(withFCI).txt
Moc(hotbilling) Moc(hotbilling) 033-ASN.1_MOC(Hot).dat 033-ASN.1_MOC(Hot).txt
SS_PLMN_SPECIFICSS1 record
SS_PLMN_SPECIFICSS1 record
034-ASN.1_SPECIFICSS1_MOC.dat
034-ASN.1_SPECIFICSS1_MOC.txt
SS_PLMN_SPECIFICSS3 record
SS_PLMN_SPECIFICSS3 record
035-ASN.1_SPECIFICSS3_MOC.dat
035-ASN.1_SPECIFICSS3_MOC.txt
MO-LCS MO-LCS record 036-ASN.1_LR_MOC.dat 036-ASN.1_LR_MOC.txt
MT-LCS MT-LCS record 037-ASN.1_LR_MTC.dat 037-ASN.1_LR_MTC.txt
NI-LCS MT-LCS record 038-ASN.1_LR_NI.dat 038-ASN.1_LR_NI.txt
6 Revision History
Issue
Date Author Description
01 2005-04-10
Guo Jin Records for the revision from V2.02 to V2.04 were added.
For details, see V2.02-V2.03: CR 01 and V2.03-V2.04: CR 01.
02 2005-04-15
Guo Jin/ Zhou Qiang
The field names in section '1.5 Record contents' were modified and the fields in section '1.6 Description of Record Fields ' were arranged according to alphabetical order.
For details, see V2.04-V2.05: CR 01.
03 2005-05-05
Guo Jin The description of the M/C/O field in section 1.5 Record contents was modified.
04 2005-8-11
Guo Jin/ Zhou Qiang
The field eCategory was added.
05 2005-8-25
Zhou Qiang
The field resourceChargeIPnumber was added.
06 2006-5-22
Tan Feng The following fields were added:
groupCallType groupCallReference uus1Type csReference csaReference camel4CDRflag networkOperatorId typeOfSubscribers
For details, see section 2.2 “V2.07-V2.08: CR 01.”
Issue
Date Author Description
07 2006-05-31
Zou Qiang
The field tariffCode was added.
The type of mscIncomingROUTE and mscOutgoingROUTE was changed from IA5(1.10) to IA5(1.32).
08 2006-6-22
Yu Bin The field tariffCode was added.
The length of mscIncomingROUTE and mscOutgoingROUTE was changed to 32 bytes.
09 2006-6-20
Zhou Qiang
The type ofCS reference was changed from INTEGER to OCTET(1..8).
10 2006-7-31
Yu Bin The field audioDataType was added.
11 2006-08-01
Zhou Qiang
The type of the camel4CDRflag field was changed from null to ENUMERATED(1).
12 2006-08-01
Zhou Qiang
Section 1.5.19 “LocUpdateVLRRecord” was added.
13 2006-08-04
Zhou Qiang
CallPartyHandling(3) was added to the structure LevelOfCAMELService.
14 2006-9-13
Du Haiwei
The moc/cfw record was changed from CDR CAMEL4_CDR_flag to camelphase, and disconnectparty and usertype were added.
mtc: Disconnectparty and usertype were added.
gwo/gwi/transit: Disconnectparty was added.
tcamel: Camelphase was added.
15 2006-9-18
Zhou Qiang
The fields interactionWithIP and resourceChargeIP were deleted from numberIncGatewayRecord and TransitCallRecord.
The fields interactionWithIP and resourceChargeIP were added to TermCAMELRecord.
16 2006-10-13
Du Haiwei
The field interactionWithIP was deleted from the incoming gateway records and transit records.
17 2006-12-12
Wang Fengkui
RecordNumber was added for all the records, and translatedNumber field was added to MTC, ROAM, GWI, GWO, and TRANSIT.
18 2006-01-06
Wang Fengkui
LAI&CI interface was added (location, changeOfLocation, firstmccmnc, and lastmccmnc were added) to GWI and GWO.
19 2007-01-13
Wang Fengkui
CMN flag was added to TRANSIT.
20 2007-2-1
E Xiaofei The TAG value of disconnectParty and tariffCode was modified.
Issue
Date Author Description
21 2007-2-2
Du Peng The field callingChargeAreaCode in the MOC record, emergency record, forwarding record, MTC record and roaming record was changed to the field chargeAreaCode. And the field chargeAreaCode was added to the other CDRs.
The interface description types of the maximumBitRate and guaranteedBitRate were added.
The field servedIMSI was added to the GWI CDR.
22 2007-4-2
Du Peng Area code was added to MOC, MTC, CFW, SMSMO, SMSMT, LCS (the LCS launched by the network is exclusive), and SS_ACT.
23 2007-4-6
Du Peng The field cAMELCPHCallConfigurationChange = 0x6 was added to CauseForTerm.
The field interactionWithIP was added to TCAMEL.
24 2007-7-31
Wang Xianping
The field MCTType was added to the MOC record.
25 2007-8-6
Wang Xianping
The following intelligent fields were added to the ROAM CDR:
gsm-SCFAddress
serviceKey
levelOfCAMELService
26 2007-8-16
Du Haifeng
The CDR examples were added..
27 2007-8-20
Wang Fengkui
The CARP field was added to the MOC, CFW and MTC records.
28 2007-12-12
Dong Zhengping
The document structure was re-designed based on the modification of the billing document.
29 2008-1-7
Wang Fengkui
The document was revised based on the modification of the billing document.
30 2008-6-17
Wangfengkui
1)The following fields were added to the TRANSIT CDR:
redirectingnumber,redirectingcounter;
2)The field partyRelCause was added to the
MOC,CFW,MEC,EMC,TRANSIT,GWI,GWO,TCAMEL,ROAM CDR
Issue
Date Author Description
31 2008-6-24
Wangfengkui
The following fields were added to the GWO、GWI、TRANSIT CDR::
redirectingnumber,redirectingcounter;
The following fields were added to the CFW CDR::redirectingcounter
32 2008-08-06
Lin Hua Update the TAG VALUE IN CDR
33 2008-8-25
Lin Hua ADD roaming-number in transit record
34 2008-9-12
Lin Hua ADD The category of subscribers. Field IN GatewayIncoming redord、OutGoingway record 、transit record
Recommended