0% found this document useful (0 votes)

621 views227 pages

Huawei IMS CDR Formats

Uploaded by

aranibarm

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

621 views227 pages

Huawei IMS CDR Formats

Uploaded by

aranibarm

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOC, PDF, TXT or read online on Scribd

You are on page 1/ 227

HUAWEI iCG9815 IMS Charging Gateway

V300R003C00
CCF CDR Formats

Issue 01

Date 2013-11-25

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
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 a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com

Email: support@huawei.com

Issue 01 (2013-11-25) Huawei Proprietary and Confidential i

About This Document

Purpose
This document describes the ASN.1-based CDR format that is supported by the CCF in IMS
offline charging. It can be used in the communication with customers and the development of
customized CDRs.
This document applies to billing interfaces of the IMS10.0 for CCF CDRs.

Intended Audience
This document is intended for:
 Technical support engineers
 Maintenance engineers

Document
[1] 3GPP TS 32.260 V6.8.0
[2] IETF RFC 3588 (2003): “diameter base protocol".
[3] ITU X.680 - X.683 (ASN.1

Change History
Issue Revising Date Revised By Description

01 2013-11-25 Xiaojun Liu Initial release.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential ii

Contents

About This Document....................................................................................................................ii

1 IMS Offline Charging..................................................................................................................1
1.1 Functional Entities.............................................................................................................................................1
1.2 Architecture of IMS Offline Charging Network................................................................................................2
1.3 Offline Charging Process...................................................................................................................................3
1.3.1 Overview..................................................................................................................................................3
1.3.2 Charging Process of Offline Events.........................................................................................................4
1.3.3 Charging Process of Establishing MO in Sessions...................................................................................5
1.3.4 Charging Process of Establishing MT in Sessions...................................................................................7

2 ASN.1 Encoding.............................................................................................................................9
2.1 Structure of CDR File........................................................................................................................................9
2.2 ASN.1...............................................................................................................................................................10
2.2.1 ASN.1 Encoding Format.........................................................................................................................11
2.2.2 Coding of ASN.1 Tag..............................................................................................................................11
2.2.3 Coding of Length....................................................................................................................................12
2.2.4 Coding of Contents.................................................................................................................................12
2.2.5 Coding of End-Of-Contents Octets........................................................................................................14

3 Description of CDR Formats.....................................................................................................15

3.1 S-CSCF CDR...................................................................................................................................................16
3.2 P-CSCF CDR...................................................................................................................................................26
3.3 I-CSCF CDR....................................................................................................................................................35
3.4 ATS9900 CDR.................................................................................................................................................40
3.5 MediaX3600 CDR...........................................................................................................................................88
3.6 MGCF CDR...................................................................................................................................................101
3.7 IBCF CDR......................................................................................................................................................110
3.8 ALUCTS CDR...............................................................................................................................................119
3.9 Centrex-AS CDR...........................................................................................................................................129
3.10 SBC CDR.....................................................................................................................................................140
3.11 AGCF CDR..................................................................................................................................................145
3.12 RCS CDR.....................................................................................................................................................151

4 Description of CDR Fields......................................................................................................160

Issue 01 (2013-11-25) Huawei Proprietary and Confidential iii

4.1 abnormal-Finish-Info.....................................................................................................................................160
4.2 abnormalFinishReason...................................................................................................................................160
4.3 abnormalFinishWarning.................................................................................................................................160
4.4 accessNetworkChargingIdentifier..................................................................................................................160
4.5 accessNetworkInformation............................................................................................................................161
4.6 access-phone..................................................................................................................................................161
4.7 accounting-record-type..................................................................................................................................161
4.8 aCName.........................................................................................................................................................161
4.9 aCRInterimLost.............................................................................................................................................161
4.10 aCRStartLost................................................................................................................................................162
4.11 aCRStopLost................................................................................................................................................162
4.12 adapter-Resource..........................................................................................................................................162
4.13 additional-Called-Party-Address.................................................................................................................162
4.14 additional-Calling-Party-Address................................................................................................................162
4.15 alternateChargedPartyAddress.....................................................................................................................162
4.16 applicationProvidedCalledParties................................................................................................................162
4.17 applicationServersInformation.....................................................................................................................162
4.18 applicationServersInvolved.........................................................................................................................163
4.19 application-Servers-State.............................................................................................................................163
4.20 associated-Party-Address.............................................................................................................................163
4.21 audioPort-Resource......................................................................................................................................163
4.22 authorized-QoS............................................................................................................................................163
4.23 bandwidth-Resource....................................................................................................................................163
4.24 bearerService...............................................................................................................................................163
4.25 bill-type........................................................................................................................................................164
4.26 call-description.............................................................................................................................................164
4.27 call-id...........................................................................................................................................................164
4.28 call-property.................................................................................................................................................165
4.29 call-Watch-Flag............................................................................................................................................165
4.30 called-local-dn-set........................................................................................................................................166
4.31 called-Party-Address....................................................................................................................................166
4.32 called-party-number-type.............................................................................................................................167
4.33 called-party-subgroup-number.....................................................................................................................168
4.34 caller-Service-Identifier...............................................................................................................................168
4.35 carrierSelectRouting....................................................................................................................................168
4.36 carrier-Identification-Code..........................................................................................................................168
4.37 calling-local-dn-set......................................................................................................................................169
4.38 calling-party-category..................................................................................................................................169
4.39 calling-party-number-type...........................................................................................................................170
4.40 calling-party-subgroup-number...................................................................................................................170
4.41 calling-User-Type.........................................................................................................................................170
4.42 causeForRecordClosing...............................................................................................................................171

Issue 01 (2013-11-25) Huawei Proprietary and Confidential iv

4.43 changeTime..................................................................................................................................................171
4.44 change-category...........................................................................................................................................171
4.45 charging-Complaint.....................................................................................................................................171
4.46 chargingCategory.........................................................................................................................................172
4.47 charged-party...............................................................................................................................................172
4.48 closed-code..................................................................................................................................................172
4.49 closed-time...................................................................................................................................................172
4.50 closed-User-Group-ID.................................................................................................................................173
4.51 content-Disposition......................................................................................................................................173
4.52 content-Length.............................................................................................................................................173
4.53 content-Type................................................................................................................................................173
4.54 created-time.................................................................................................................................................173
4.55 current-data-party.........................................................................................................................................173
4.56 current-party.................................................................................................................................................173
4.57 current-telepresence-party............................................................................................................................173
4.58 dialled-Party-Address..................................................................................................................................174
4.59 diversioncount..............................................................................................................................................174
4.60 diversionreason............................................................................................................................................174
4.61 down-CascadePorts......................................................................................................................................174
4.62 duration........................................................................................................................................................175
4.63 end-code.......................................................................................................................................................175
4.64 event.............................................................................................................................................................175
4.65 expiresInformation.......................................................................................................................................175
4.66 fci-Free-Format-Data-Manne.......................................................................................................................175
4.67 default-Call-Handling..................................................................................................................................176
4.68 first-level-bill-group.....................................................................................................................................176
4.69 gGSNaddress...............................................................................................................................................176
4.70 gPRS-Charging-Id........................................................................................................................................176
4.71 groupID........................................................................................................................................................176
4.72 group-id........................................................................................................................................................177
4.73 group-number...............................................................................................................................................177
4.74 iMS-Charging-Identifier..............................................................................................................................177
4.75 iMSCommunicationServiceIdentifier..........................................................................................................177
4.76 incomplete-CDR-Indication.........................................................................................................................177
4.77 initialIMS-Charging-Identifier.....................................................................................................................178
4.78 inner-error....................................................................................................................................................178
4.79 interOperatorIdentifiers...............................................................................................................................178
4.80 list-of-application-Servers-Abnormal..........................................................................................................178
4.81 list-Of-Associated-URI................................................................................................................................178
4.82 list-Of-Calling-Party-Address......................................................................................................................179
4.83 list-Of-Called-Asserted-Identity..................................................................................................................180
4.84 list-Of-Early-sDP-Media-Components........................................................................................................180

Issue 01 (2013-11-25) Huawei Proprietary and Confidential v

4.85 list-Of-Message-Bodies...............................................................................................................................180
4.86 list-Of-sDP-Media-Components..................................................................................................................180
4.87 list-of-subscription-ID.................................................................................................................................181
4.88 locationInformation.....................................................................................................................................181
4.89 localRecordSequenceNumber......................................................................................................................181
4.90 location-routing-number..............................................................................................................................181
4.91 lrn-query-status............................................................................................................................................181
4.92 lrn-source-indicator......................................................................................................................................181
4.93 main-screen..................................................................................................................................................182
4.94 main-screen-entrance-type...........................................................................................................................182
4.95 mediaInitiatorFlag........................................................................................................................................182
4.96 mediaInitiatorParty......................................................................................................................................182
4.97 media-type...................................................................................................................................................182
4.98 mediax-conference-information...................................................................................................................182
4.99 mediax-terminal-information.......................................................................................................................183
4.100 mediax-user-information............................................................................................................................183
4.101 meeting-frequency.....................................................................................................................................184
4.102 meeting-id..................................................................................................................................................184
4.103 meeting-mode............................................................................................................................................184
4.104 mMTelInformation.....................................................................................................................................184
4.105 modified-Adapter-Resource.......................................................................................................................184
4.106 modified-AudioPort-Resource...................................................................................................................184
4.107 modified-Bandwidth-Resource..................................................................................................................184
4.108 multiPic-Resource......................................................................................................................................185
4.109 modified-MultiPic-Resource.....................................................................................................................185
4.110 modified-start-time.....................................................................................................................................185
4.111 modified-end-time......................................................................................................................................185
4.112 modified-party............................................................................................................................................185
4.113 modified-telepresence-party.......................................................................................................................185
4.114 modified-Up-CascadePorts........................................................................................................................185
4.115 modified-Down-CascadePorts...................................................................................................................185
4.116 modified-VideoPort-Resource...................................................................................................................185
4.117 msc-number................................................................................................................................................186
4.118 nP-Data.......................................................................................................................................................186
4.119 nP-Query....................................................................................................................................................186
4.120 np-Route-Number......................................................................................................................................186
4.121 nodeAddress...............................................................................................................................................186
4.122 numberOfDiversions..................................................................................................................................186
4.123 numberOfParticipants................................................................................................................................187
4.124 numberPortabilityRouting.........................................................................................................................187
4.125 onlineChargingFlag....................................................................................................................................187
4.126 onlineChargingType...................................................................................................................................187

Issue 01 (2013-11-25) Huawei Proprietary and Confidential vi

4.127 operation-time............................................................................................................................................187
4.128 order-end-time............................................................................................................................................187
4.129 order-party..................................................................................................................................................187
4.130 order-start-time..........................................................................................................................................188
4.131 origin-Callee-Party-Address......................................................................................................................188
4.132 originatingIOI............................................................................................................................................188
4.133 organization-id...........................................................................................................................................188
4.134 originator....................................................................................................................................................188
4.135 originator-sccp-address..............................................................................................................................188
4.136 osg-bill-indication......................................................................................................................................189
4.137 participantActionType................................................................................................................................189
4.138 pay-account................................................................................................................................................189
4.139 pbxaddress.................................................................................................................................................189
4.140 pBX-Pilot-Number.....................................................................................................................................189
4.141 port-type.....................................................................................................................................................190
4.142 privateNetworkIndication..........................................................................................................................190
4.143 privateNumber...........................................................................................................................................190
4.144 privateUserID.............................................................................................................................................190
4.145 pstn-cdr-info...............................................................................................................................................190
4.146 private-MediaPartialRecordNumber..........................................................................................................191
4.147 private-User-Equipment-Info.....................................................................................................................191
4.148 private-User-Equipment-Info-Type...........................................................................................................191
4.149 private-User-Equipment-Info-Value..........................................................................................................192
4.150 recordClosureTime.....................................................................................................................................192
4.151 recordExtensions........................................................................................................................................192
4.152 recordExtensions-1....................................................................................................................................192
4.153 recordExtensions-2....................................................................................................................................192
4.154 recordOpeningTime...................................................................................................................................192
4.155 recordSequenceNumber.............................................................................................................................192
4.156 recordType.................................................................................................................................................192
4.157 refer-To.......................................................................................................................................................193
4.158 related-call-reference.................................................................................................................................193
4.159 requested-Party-Address............................................................................................................................193
4.160 retransmission............................................................................................................................................193
4.161 restriction-Group-ID..................................................................................................................................194
4.162 ringing-Duration........................................................................................................................................194
4.163 role-of-Node...............................................................................................................................................194
4.164 rst-information...........................................................................................................................................194
4.165 rST-Subscriber-ID......................................................................................................................................195
4.166 s-CSCF-Information..................................................................................................................................195
4.167 screen-number............................................................................................................................................195
4.168 sDP-Media-Components............................................................................................................................195

Issue 01 (2013-11-25) Huawei Proprietary and Confidential vii

4.169 sDP-Media-Descriptions............................................................................................................................195
4.170 sDP-Media-Identifier.................................................................................................................................195
4.171 sDP-Media-Name......................................................................................................................................196
4.172 sDP-Session-Description...........................................................................................................................196
4.173 sDP-Type....................................................................................................................................................196
4.174 second-level-bill-group..............................................................................................................................196
4.175 servedPartyIPAddress................................................................................................................................196
4.176 server-Role.................................................................................................................................................196
4.177 serverUserType..........................................................................................................................................197
4.178 serviceContextID.......................................................................................................................................197
4.179 serviceDeliveryEndTimeStamp.................................................................................................................197
4.180 serviceDeliveryStartTimeStamp................................................................................................................197
4.181 serviceId.....................................................................................................................................................198
4.182 serviceIdentifier.........................................................................................................................................198
4.183 service-indetity-list....................................................................................................................................198
4.184 service-mode..............................................................................................................................................199
4.185 serviceMode...............................................................................................................................................199
4.186 serviceRequestTimeStamp.........................................................................................................................200
4.187 serviceReasonReturnCode.........................................................................................................................200
4.188 serviceSpecificData...................................................................................................................................200
4.189 serviceSpecificInfo....................................................................................................................................201
4.190 serviceSpecificType...................................................................................................................................201
4.191 service-type................................................................................................................................................201
4.192 session-Id...................................................................................................................................................201
4.193 session-Priority..........................................................................................................................................202
4.194 session-Type...............................................................................................................................................202
4.195 short-number..............................................................................................................................................203
4.196 sIP-Method.................................................................................................................................................203
4.197 sIP-Request-Timestamp.............................................................................................................................203
4.198 sIP-Request-Timestamp-Fraction..............................................................................................................203
4.199 sIP-Response-Timestamp...........................................................................................................................203
4.200 sIP-Response-Timestamp-Fraction............................................................................................................204
4.201 sms-information.........................................................................................................................................204
4.202 sms- node...................................................................................................................................................204
4.203 SMS-Notify-Type......................................................................................................................................204
4.204 smsc-address..............................................................................................................................................205
4.205 subscriber-Identity.....................................................................................................................................205
4.206 subgroup-id................................................................................................................................................205
4.207 sub-meetingID...........................................................................................................................................205
4.208 subscriberRole...........................................................................................................................................205
4.209 subscriptionIDData....................................................................................................................................206
4.210 subscriptionIDType....................................................................................................................................206

Issue 01 (2013-11-25) Huawei Proprietary and Confidential viii

4.211 supplementary-Service-Info.......................................................................................................................206
4.212 Segment-Id.................................................................................................................................................207
4.213 target..........................................................................................................................................................207
4.214 tariffPulses.................................................................................................................................................207
4.215 telepresence-party......................................................................................................................................207
4.216 terminatingIOI...........................................................................................................................................207
4.217 terminal-type..............................................................................................................................................207
4.218 tADS-Indication.........................................................................................................................................208
4.219 trunkGroupID(Incoming/Outgoing)..........................................................................................................208
4.220 up-CascadePorts.........................................................................................................................................208
4.221 user-id........................................................................................................................................................208
4.222 user-sip-uri.................................................................................................................................................208
4.223 user-Agent-Value.......................................................................................................................................208
4.224 videoPort-Resource....................................................................................................................................208
4.225 visited-network-id......................................................................................................................................209
4.226 vlr-number..................................................................................................................................................209
4.227 vmsc-id.......................................................................................................................................................209
4.228 vPNCallProperty........................................................................................................................................209
4.229 user-Category.............................................................................................................................................210
4.230 list-Of-Logic-Resource..............................................................................................................................210
4.231 port-Media-Type........................................................................................................................................210
4.232 port-Count..................................................................................................................................................210

5 Cases.............................................................................................................................................211
5.1 How the Mediation Merges the CCF Partial CDRs.......................................................................................211

6 ASN.1-Based CDR Description Files.....................................................................................213

7 CDR Samples.............................................................................................................................214
8 Abbreviation................................................................................................................................215

Issue 01 (2013-11-25) Huawei Proprietary and Confidential ix

1 IMS Offline Charging

1.1 Functional Entities

Figure 1-1 Architecture of IMS offline charging

CTF is an entity in the IMS domain. It collects chargeable events and sends them to the CCF
through the Rf interface.
The charging data function (CDF) and the charging gateway function (CGF) are called the
charging collection function (CCF).
The CCF collects charging information from the IMS entities (such as the P-CSCF, I-CSCF,
S-CSCF, AS, and MGCF) through the Rf interface, pre-processes the information, and sends it
to the billing domain as required by a network operator. The CCF performs the following
functions:

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 1

 Collecting charging information from IMS entities

 Associating, consolidating and filtering out unnecessary fields, and adding carrier-
specific information to the received charging information
 Pre-processing charging information and generating CDRs
 Providing the CDRs to the billing domain
 Caching CDRs when the billing domain is busy
In networking, a network element (NE) can connect to multiple CCFs, one of which serves as
the primary CCF others serve as secondary ones. When the connection between the NE and
the primary CCF is interrupted, or when the primary CCF fails to receive ACRs sent by the
NE due to exceptions, the NE can send ACRs to the secondary CCFs instead. When the
primary CCF is restored to normal, the NE switches back to the primary CCF and sends
ACRs to it.
The billing domain provides such functions as rating and charging correlation. It is part of the
operation and maintenance system of a carrier. The CCF/CGF sends CDRs to the billing
domain. The billing domain associates the charging information according to the charging
identifiers, and generates bills for subscribers.
The interface Bx between CCF and billing center is used to transfer the CDR files to billing
center from CCF which supports FTP protocol. CCF push the CDR files to billing center
through FTP protocol or the billing center get the CDR files from CCF by FTP PULL method.

1.2 Architecture of IMS Offline Charging Network

Figure 1-1 Architecture of IMS offline charging network

The CDF/CCF collects charging information from the nodes, such as the MRFC, S-CSCF,
MGCF, I-CSCF, BGCF, P-CSCF, and AS, through the Rf interface.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 2

These nodes (the MRFC, S-CSCF, MGCF, I-CSCF, BGCF, P-CSCF, and AS) support the
generation of interim CDRs in an IMS session and the transmission of interim CDR
information in ACR[Interim] messages. Interim CDRs can be based on call duration or
transmitted bytes in messages.
When collecting and sending charging messages, these nodes (the MRFC, S-CSCF, MGCF, I-
CSCF, BGCF, P-CSCF, and AS) will add the value of the call-id header field to the Diameter
charging messages such as ACR[Start], ACR[Interim], ACR[Stop], and ACR[event]. They
will also add the value of the Tag parameter of the From header and To header fields in
corresponding SIP messages to such ACR charging messages.
In processing these Diameter charging messages (such as ACR[Start], ACR[Interim],
ACR[Stop], and ACR[event]), the CDF/CCF will differentiate and associate ACRs according
to not only the call-ids but also the Tag values contained in the From header and To header
fields. Those ACRs that have the same call-id, the same Tag value in the From header field,
and the same Tag value in the To header field are regarded as ACRs that are generated in the
same Dialog. The CDF/CCF organizes the charging messages accordingly, generates CDRs,
and provides them to the billing center. The CDF/CCF will also add the Tag values of the
From header field and the To header field to the CDRs that are provided to the billing center.
Where an IMS session is initiated by an end user, the first node of the SIP signaling route in
the IMS network (for example, the P-CSCF in the visited network or home network)
generates ICIDs. The ICIDs are transmitted through SIP signaling between the visited
network and the home network within the IMS network.
Where a session is initiated by an AS, the AS generates ICIDs.
Upon the completion of exchange between GCID and ICID, the P-CSCF transmits the GCID
and GGSN address information to such nodes as the S-CSCF and As through SIP signaling.
Then, the S-CSCF transmits the GCID and GGSN address information to the CCF in the
generated CDRs. GCID and GGSN address information cannot be transmitted between IMS
networks.
If an IMS session involves two IMS networks and two different carriers, the CCF must be
able to identify the two networks through IOI information exchanging. When an SIP request
message is sent by an IMS network, the identifier of this originating IMS network must be
contained in the IOI. Likewise, when an SIP response message is sent by the peer IMS
network, its identifier must be contained in the IOI of the SIP response message. The IOI of
an IMS network must be unique.
The IOI information must be contained in CDRs and used in IMS session based charging
across different IMS carriers.

1.3 Offline Charging Process

1.3.1 Overview
This section specifies the roles and functions of relevant IMS network elements in offline
charging by describing three typical offline charging scenarios.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 3

1.3.2 Charging Process of Offline Events

Figure 1-1 Charging process of offline events (referring to 3GPP 32.260 R6)

The process is described as follows:

1. The IMS user initiates a non-session request (such as a SIP SUBSCRIBE request) in the
visited network. The P-CSCF in the visited network receives the request message, generates
an ICID, adds the ICID to the P-Charging-Vector message header, and forwards this request
message to the home network. The S-CSCF in the home network receives the request
message, and saves the ICID contained in the P-Charging-Vector passage header. The
SUBSCRIBE request message forwarded by the P-CSCF contains the following information.
SUBSCRIBE sip:user1@home1.net SIP/2.0
P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

2. Response to the SUBSCRIBE request is obtained. The P-CSCF in the visited network
deletes the P-Charging-Vector message header before it forwards the response message to the
UE.
3. The S-CSCF in the home network sends an ACR[event] message to the CDF in the same
network. The accounting-record-type of the message is EVENT_RECORD, which indicates
that the message is an event-based charging message.
4. The CDF in the home network receives and saves the ACR[event] message, generates an S-
CSCF CDR, and sends an ACA to the S-CSCF.
5. After forwarding the response message to the UE, the P-CSCF in the visited network sends
an ACR[event] message to the CDF in the same network. The accounting-record-type of the
message is EVENT_RECORD, which indicates that the message is an event-based charging
message.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 4

6. The CDF in the visited network receives and saves the ACR[event] message, generates a P-
CSCF CDR, and sends an ACA to the P-CSCF.

1.3.3 Charging Process of Establishing MO in Sessions

Figure 1-1 Charging process of establishing MO in sessions

The process is described as follows:

1. The IMS registered user initiates an initial INVITE request in the visited network. The P-
CSCF in the visited network receives the initial INVITE request, generates an ICID, adds the
ICID to the P-Charging-Vector message header, and sends the request to the S-CSCF in the
home network. The S-CSCF in the home network receives the INIVITE request, saves the
ICID, and adds to the P-Charging-Vector message header the orig-ioi, that is, the IOI of the
home network of the calling party. The initial INVITE request is forwarded to other IMS
entities by the S-CSCF in the home network. The INVITE request message forwarded by the
P-CSCF in the visited network contains the following information.
INVITE sip:user2@home2.net SIP/2.0
P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

The INVITE request message forwarded by the S-CSCF in the home network contains the
following information.
INVITE sip:user2@home2.net SIP/2.0

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 5

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"; orig-

ioi=home1.net

2. The calling party receives a 183 response. The S-CSCF in the home network saves and
deletes the term-ioi, that is, the IOI of the home network of the called party. The P-CSCF in
the visited network deletes the P-Charging-Vector message header before it forwards the 183
response to the UE. The 183 response forwarded by the S-CSCF in the home network
contains the following information.
SIP/2.0 183 Session Progress
P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

3. The calling party receives a 200 OK response. The P-CSCF in the visited network deletes
the P-Charging-Vector message header before it forwards the 200 OK response to the UE.
4. The S-CSCF in the home network receives the 200 OK response, and sends an ACR[Start]
message to the CDF in the same network. The accounting-record-type of the message is
START_RECORD, which indicates the start of session-based charging.
5. The CDF in the home network receives and saves the ACR[Start] message, generates an S-
CSCF CDR, and sends an ACA to the S-CSCF.
6. The P-CSCF in the visited network receives the 200 OK response, and sends an ACR[Start]
message to the CDF in the same network. The accounting-record-type of the message is
START_RECORD, which indicates the start of session-based charging.
7. The CDF in the visited network receives and saves the ACR[Start] message, generates a P-
CSCF CDR, and sends an ACA to the P-CSCF.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 6

1.3.4 Charging Process of Establishing MT in Sessions

Figure 1-1 Charging process of establish MT in sessions (referring to 3GPP 32 260 R6)

The process is described as follows:

1. The called party receives a session establishment request. The S-CSCF in the home
network saves and deletes the orig-ioi, that is, the IOI of the home network of the calling
party. The P-CSCF in the visited network deletes the P-Charging-Vector message header
before it forwards the request message to the UE. The INVITE request message forwarded by
the I-CSCF in the home network contains the following information.
INVITE sip:user2@home2.net SIP/2.0
P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"; orig-
ioi=home1.net

The INVITE request message forwarded by the S-CSCF in the home network is as follows:
INVITE sip:[5555::eee:fff:aaa:bbb]:8805;comp=sigcomp SIP/2.0

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 7

P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

2. After querying information in the HSS successfully, the I-CSCF in the visited network
sends an ACR[event] message to the CDF in the home network.
3. The CDF in the home network receives and saves the ACR[event] message, generates an I-
CSCF CDR, and sends an ACA to the I-CSCF.
4. The called party sends a 183 message to the calling party. The P-CSCF in the visited
network adds the saved ICID to the P-Charging-Vector message header. The S-CSCF in the
home network adds the IOI of the home network of the called party to the P-Charging-Vector
message header, and the address of the charging entity to the P-Charging-Function-Addresses
message header. The last entity in the called party should delete the P-Charging-Function-
Addresses header of the 183 message.
The 183 message forwarded by the P-CSCF in the visited network contains the following
information.
SIP/2.0 183 Session Progress
P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"

The 183 message forwarded by the S-CSCF in the home network contains the following
information.
SIP/2.0 183 Session Progress
P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"; orig-
ioi=home1.net; term-ioi=home2.net
P-Charging-Function-Addresses: ccf=[5555::b99:c88:d77:e66];
ccf=[5555::a55:b44:c33:d22]; ecf=[5555::1ff:2ee:3dd:4cc];
ecf=[5555::6aa:7bb:8cc:9dd]

The 183 message forwarded by the I-CSCF in the home network contains the following
information.
SIP/2.0 183 Session Progress
P-Charging-Vector: icid-value="AyretyU0dm+6O2IrT5tAFrbHLso=023551024"; orig-
ioi=home1.net; term-ioi=home2.net

5. The called party sends a 200 OK response to the calling party.

6. The P-CSCF in the visited network receives the 200 OK response, and sends an ACR[Start]
message to the CDF in the same network. The accounting-record-type of the message is
START_RECORD, which indicates the start of session-based charging.
7. The CDF in the visited network receives and saves the ACR[Start] message, generates a P-
CSCF CDR, and sends an ACA to the P-CSCF.
8. The S-CSCF in the home network receives the 200 OK response, and sends an ACR[Start]
message to the CDF in the same network. The accounting-record-type of the message is
START_RECORD, which indicates the start of session-based charging.
9. The CDF in the home network receives and saves the ACR[Start] message, generates an S-
CSCF CDR, and sends an ACA to the S-CSCF.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 8

2 ASN.1 Encoding

2.1 Structure of CDR File

A CDR file begins with a 3GPP header, which is structured as follows:

Bits

Octets 8 7 6 5 4 3 2 1
1-4 File length
5-8 Header length
9 High Release Identifier High Version Identifier
10 Low Release Identifier Low Version Identifier
11-14 File opening timestamp
15-18 Timestamp when last CDR was appended to file
19-22 Number of CDRs in file

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 9

23-26 File sequence number

27 File Closure Trigger Reason
28-47 IP Address of Node that generated file
48 Lost CDR indicator
49-50 Length of CDR routing filter

Each CDR is an ASN.1-based coding structure that consists of the following parts:

CDR Header

Record Data

And a CDR header is structured as follows:

Bits

Octets 8 7 6 5 4 3 2 1
1-2 CDR length
3 Release Identifier Version Identifier
4 Data Record Format TS number

2.2 ASN.1
ASN.1 is an abbreviation of '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 therefore it is widely accepted as the syntax standard for the
application layer protocols.
ASN.1 provides the designer with simple types, for instance, integer, Boolean, and octet
string. With the simple types as building stones the protocol designer can construct more
complex data types. More complex data types can be built from sets or sequences of simpler
types, by uniquely 'tagging' particular data structures for easy recognition. For instance, a call
data record can be structured as a set consisting of a number of data fields. Encoding of a data
value consists of 4 components (in correct order):
 Identifier octets
 Length octets
 Contents octets
 End-of-contents octets (for indefinite length encoding)

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 10

2.2.1 ASN.1 Encoding Format

The CCF provides CDRs that are structured according to ASN.1 to the billing center. This
chapter describes the encoding rules for each ASN.1 components and the CDR structure.

2.2.2 Coding of ASN.1 Tag

The identifier octets encode the ASN.1 tag of the data value. Two possibilities exist:
 Single octet encoding for tag numbers from 0 to 30 (inclusive).
8 7 6 5 4 3 2 1
+-------+---+------------------+
1 ¦ CLASS ¦P/C¦ TAG NUMBER ¦
+------------------------------+

Bits 8-7: Class identifier:

+----------------------------+
¦ Bit: 8 7 ¦
+----------------------------¦
¦ Universal 0 0 ¦
¦ Application 0 1 ¦
¦ Context-specific 1 0 ¦
¦ Private 1 1 ¦
+----------------------------+
Bit 6 : Primitive (0) or
Constructed (1)
Bits 5-1: binary integer with bit 5 as msb

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

The leading octet is encoded as follows:
8 7 6 5 4 3 2 1
+-------+---+---+---+---+---+---¦
1 ¦ CLASS ¦P/C¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦
+-------------------------------+

Bits 8-7: Class identifier as for single octet id

Bit 6 : Primitive (0) or
Constructed (1)
Bits 5-1: all bits set to 1

Subsequent octets are encoded as:

8 7 6 5 4 3 2 1
+---+---------------------------¦ first
2 ¦ 1 ¦ NUMBER of TAG (msb) ¦ subsequent
+-------------------------------¦
. .
. .
+-------------------------------¦ last
¦ 0 ¦ NUMBER of TAG (lsb) ¦ subsequent
+-------------------------------+

Bits 8 : set to 1 in all non-last subsequent

octets
Bits 7-1: Bits 7-1 of all subsequent octets
encoded as a binary integer equal to

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 11

the tag number with bit 7 of the first

subsequent octet as most significant
bit.

2.2.3 Coding of Length

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

Short length encoding for length from 0 to 127 (inclusive)

8 7 6 5 4 3 2 1
+-------------------------------¦
1 ¦ 0 L L L L L L L ¦
+-------------------------------+
LLLLLLL represents the length of the content.

Long length encoding for length greater 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 ¦
+-------------------------------+
LLLLLLLL represents the length of the content

2.2.4 Coding of Contents

The contents octets may contain no, one or multiple bytes. Their values depend on the
presented data types.
Contents 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
+------------------------------+

Here is a description of the encoding of different data types.

 BOOLEAN

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 12

This data type can only be encoded in the primitive format.

The value FALSE is encoded as:
Tag Length Value
+------------------------------¦
¦ 01H ¦ 01H ¦ 0000, 0000 ¦
+------------------------------¦

The value TRUE (indicating any octets except the all "0"s octet) is encoded as:
Tag Length Value
+------------------------------¦
¦ 01H ¦ 01H ¦ 1111, 1011 ¦
+------------------------------¦

 NULL
This data type can only be encoded in the primitive format and has only one value. The
Value of this data type is left blank, that is, the Value will not take up any space.
Tag Length Value
+------------------------------¦
¦ 05H ¦ 00H ¦
+------------------------------¦

 INTEGER
This data type can only be encoded in the primitive format. Integers are of two types:
positive integers and negative integers. Negative integers are not present in ASN.1-based
CDR files, and therefore are not discussed in this document.
If the highest bit of a positive integer is 0, encode the integer directly. If the highest bit is
1, add an all "0"s octet before the highest bit and save it as complement. The following is
the encoding of the positive integer 250:
Tag Length Value
+-------------------------------------¦
¦ 02H ¦ 02H ¦ 0000,0000 1111,1010¦
+-------------------------------------¦

 ENUMERATED
This data type is encoded in the same way as the INTEGER data type.
 BIT STRING
This data type can be encoded in the primitive format or the constructed format. The
following examples demonstrate the encoding of the bit string '1011011101011'B in
these two formats respectively.
Primitive
Tag Length Value
+------------------------------------------¦
¦ 03H ¦ 03H ¦ 03H 10110111 01011xxx¦
+------------------------------------------¦

An octet is added before the bit string '1011011101011'B. The value of the added octet
ranges from 0 to 7 and indicates the number of complementary bits to the bit string. An
octet is added where the bit string is not a multiple of 8.
Constructed
The constructed format is applied where some codes cannot be ascertained. The bit string
'1011011101011'B is encoded in the constructed format as follows:
Tag Length Value
+----------------------------------------------¦

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 13

¦ 03H ¦ 80H ¦ T L V
¦ ¦
03H ¦ 02H ¦ 00H 10110111¦
¦ ¦
03H ¦ 02H ¦ 03H 01011xxx¦
00H 00H
+-----------------------------------------------¦

Note: The Length of the bit string is indefinite here.

 OCTET STRING
This data type is encoded in the same ways as the BIT STRING data type. Because this
type of data is measured in octets, there is no need to add complementary bits to it when
encoding the data.
 SET
This data type is encoded in the constructed format. Each component is encoded in the
TLV format.
The following is the encoding of MOC {recordType ENUMERATED, callDuration
INTEGER }:={ recordType 0,callDuration 11}:
Tag Length Value
+--------------------------------------------¦
¦ 16H ¦ 80H ¦ T L V
¦ ¦ 02H ¦ 01H ¦ 0000 0000¦
¦ ¦ 02H ¦ 01H ¦ 0000 1011¦
+--------------------------------------------¦

 SEQUENCE
This data type is encoded in the same way as the SET data type. The difference is that
the sequence of the members of this data item in the encoding must be the same as that in
the definition, while the sequence is not required in the encoding of the SET data.
 SET OF
This data type is encoded in the same way as the SET data type.
 SEQUENCE OF
This data type is encoded in the same way as the SEQUENCE data type.

Other classes are not common; therefore, they are not described in the subsequent sections.

2.2.5 Coding of End-Of-Contents Octets

End-of-contents octets are present only in indefinite length encoding and therefore are not
discussed here.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 14

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

3 Description of CDR Formats

At the time, the iCG9815 (IMS Charging Gateway) provides the following types of charging
data records (CDRs) to the billing system (BS):
 The iCG9815 generates S-CSCF-CDRs based on the accounting requests (ACRs) sent by
the CSC3300 that functions as the serving-call session control function (S-CSCF).
 The iCG9815 generates P-CSCF-CDRs based on the ACRs sent by the CSC3300 that
functions as the proxy-call session control function (P-CSCF).
 The iCG9815 generates I-CSCF-CDRs based on the ACRs sent by the CSC3300 that
functions as the interrogating-call session control function (I-CSCF).
 The iCG9815 generates ATS-CDRs based on the ACRs sent by the ATS9900 that
functions as the advanced telephony server (ATS).
 The iCG9815 generates MediaX-CDRs based on the ACRs sent by the MediaX3600.
 The iCG9815 generates MGCF-CDRs based on the ACRs sent by the UGC3200.
 The iCG9815 generates IBCF-CDRs based on the ACRs sent by the CSC3200.
 The iCG9815 generates ALUCTS-CDRs based on the ACRs sent by the ALUCTS.
 The iCG9815 generates Centrex-AS-CDRs based on the ACRs sent by the Centrex AS.
 The iCG9815 generates SBC-CDRs based on the ACRs sent by the SE2600.
 The iCG9815 generates AGCF-CDRs based on the ACRs sent by the UAC3000.
 The iCG9815 generates RCS-CDRs based on the ACRs sent by the RCS9880.
The content of each CDR type is defined in the following sections. For each CDR type the
field definition includes the field name, category, source, and field description.
A field category can have one of two primary values:
 M
It indicates a mandatory field that is always present in CDRs.
 C
It indicates a field that is present in CDRs only when certain conditions are met. These
conditions are specified as part of the field definition.
Operators can include or exclude certain fields from CDRs through the Operation and
Maintenance Center (OMC) management function or specific tools provided. Once excluded,
these fields are not present in CDRs. All these fields are available in the IMS NE, and their
present in CDRs is determined by the configuration of operators.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 15

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Configure a mandatory or optional field as follows:

 OM
If this field is set to be present by an operator, it is always included in CDRs. In other
words, the OM parameter that is set to be present is a mandatory parameter.
 OC
If this field is set to be present by an operator, it is included in CDRs only when the
required conditions are met. In other words, the OC parameter that is set to be present is
an optional parameter.
Some fields consist of hierarchical sub-fields. This chapter clarifies the hierarchical
relationship by using the superscript "[NUM]". "NUM" shows the level.
[1]
 indicates that a field includes sub-fields and shows the fist level.
[2]
 indicates a sub-flied of the first level. It also shows the second level.
[3]
 indicates a sub-flied of the second level. It also shows the third level.
[4]
 indicates a sub-flied of the third level. It also shows the fourth level.

3.1 S-CSCF CDR

The tag value in the S-CSCF CDR is 0xBF 3F.

Table 3-1 Format of S-CSCF CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

CDR, indicating which NE
generated the CDR.
retransmission OC 0x81 NULL This field specifies whether the
ACRs from the S-CSCF are sent
repeatedly.
sIP-Method OC 0x82 GraphicString This field specifies the reason why
ACRs are generated. This field is
only available in unrelated sessions.
role-of-Node OM 0x83 INTEGER This field specifies the role of the S-
CSCF in the current session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ME that
provides the charging messages. It
can be an IP address or a valid
domain name of the ME providing
charging data. This field is derived
from the Origin-Host field in the S-
CSCF CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 16

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

session-Id OM 0x85 GraphicString This field specifies the session ID.

For a SIP session, the session ID
contains the SIP call ID as defined
in the SIP RFC3261 [404].
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field specifies the number
Address [1] information about the calling party.
It can be in tel URI format or SIP
URI format. This field contains
multiple values in a CDR. This field
is derived from the Calling-Party-
Address field in the S-CSCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
called-Party-Address OM 0xA7 CHOICE This field specifies the number
[1]
information about the called party. It
can be in SIP URI format or tel URI
format. This field is derived from
the Called-Party-Address field in
the S-CSCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
privateUserID OM 0x88 GraphicString This field specifies the used network
access ID of the served party
according to the RFC2486 [405].
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
serviceDeliveryStartTi OM 0x8A OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE receives a response after the
peer NE initiates a session request.
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE initiates a request to end a
session.
recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation starts. This
field shows the time when the CCF
receives the first ACR in a session.
At present, it is present only in the
cases related to SIP sessions.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 17

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordClosureTime OM 0x8D OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation ends. This
field shows the time when the CCF
receives the last ACR in a session.
interOperatorIdentifier OC 0xAE SEQUENCE OF This field specifies the identities of
s[1] the pair of an originating network
and a terminating network in SIP
signaling transmission.
This field contains the following
sub-fields:
 originatingIOI
 terminatingIOI
originatingIOI [2] OC 0x80 GraphicString This field identifies the network that
serves the calling party.
terminatingIOI [2] OC 0x81 GraphicString This field identifies the network that
serves the called party.
localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN
Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.
recordSequenceNumb OC 0x90 INTEGER This field is filled only when
er incomplete CDRs are to be
generated.
In the case of timeout or other cases,
the CCF may generate multiple
partial CDRs for the same charging
session. In that case, the CCF
allocates a record SN (starting with
1) to each partial CDR.
It helps the BS check whether a
CDR is complete.
causeForRecordClosin OC 0x91 ENUMERATED This field specifies the reason why a
g session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 18

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

incomplete-CDR- OC 0xB2 SET This field provides additional

Indication [1] diagnostics when the CCF finds that
charging data is missing. This field
shows whether the CDR content is
complete. If the CDR misses a
partial ACR, the CCF fills in the
following fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
iMS-Charging- OM 0x93 OCTET STRING This field is assigned by the first
Identifier accessed ME in the IMS domain and
sent to all MEs in the IMS domain.
It is unique in an end-to-end session.
This field is also called ICID for
short.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 19

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-sDP-Media- OC 0xB5 SEQUENCE OF A field of the group type.

Components [1] It contains several sub-fields
associated with one media
component. This field is present in
only one SIP session and may
appear several times in one CDR
because one CDR may contain
multiple sessions.
It describes the details about media
changes in an E2E session. For
example, calling party A starts voice
communications with called party B
at 9:00 am. Then, A and B change
the communication way into video
at 9:30 a.m. The initiator of the
video communications can be A or
B.
This field is essential to the CCF and
the BS.
This field contains the following
sub-fields:
 sDP-Session-Description
 SIP-Request-Timestamp
 SIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
sIP-Request- OM 0x80 OCTET STRING This field specifies the SIP Request
Timestamp [2] (SIZE(9)) time.
sIP-Response- OM 0x81 OCTET STRING This field specifies the SIP
Timestamp [2] (SIZE(9)) Response time.
sDP-Media- OM 0xA2 SEQUENCE OF A field of the group type.
Components [2] It contains several sub-fields
associated with one media
component. Because several media
components may exist for a session
in parallel, these sub-fields may
appear several times.
This field contains the following
sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 20

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sDP-Media-Name [3] OM 0x80 GraphicString This field specifies the media name.
It contains the information indicated
by the line m= in the SDP
information.
sDP-Media- OM 0xA1 SEQUENCE OF This field specifies the session
Descriptions [3] description, including the IP address
that provides media support.
gPRS-Charging-Id [3] OM 0x82 INTEGER This field specifies the ID of the
GGSN that provides bearer at the
bearer layer (PS domain), namely,
GCID. It is implemented by
converting the numeric string into
integers. If the PS domain bearer
changes, the IMS domain is notified
of the field. The BS then uses the
ICID and GCID to associate with
CDRs.
accessNetworkChargi OM 0x84 GraphicString This field specifies the access
ngIdentifier [3] network charging ID.
authorized-QoS [3] OC 0x83 GraphicString This field authorizes the QoS for
end-to-end services.
mediaInitiatorFlag [2] OC 0x83 NULL This field specifies whether the
media initiated by the called party
changes.
sDP-Session- OC 0xA4 SEQUENCE OF This field specifies the session
Description [2] portion of the SDP data exchanged
between user agents in the SIP
transaction.
This field is the attribute line (i=, c=,
b=, k=, a=, ...) in an SDP message
and used to describe a session.
mediaInitiatorParty [2] OC 0xA5 CHOICE It is reserved for future expansion
and is not in use at present.
sIP-Request- OC 0x86 Unsigned32 This field specifies the SIP request
Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the field SIP-
Request-Timestamp.
sIP-Response- OC 0x87 Unsigned32 This field specifies the SIP response
Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the field SIP-
Response-Timestamp.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 21

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

gGSNaddress [1] OC 0xB6 CHOICE This field specifies the IP address of

the GGSN that provides media
bearer support.
This field is derived from GGSN-
Address in the S-CSCF CDRs.
iPAddress [2] OC 0xA0 CHOICE This field specifies the type of IP
address.
serviceReasonReturn OC 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails.
It is displayed as
serviceDeliveryFailureReason in
the R5 version and
serviceReasonReturnCode in the
R6 version.
list-Of-Message- OC 0xB8 SEQUENCE OF A field of the group type.
Bodies [1] It contains several sub-fields
describing the SIP messages
transmitted between the IMS NEs.
Because SIP signaling may be
exchanged among several messages,
the field may appear several times.
This field contains the following
sub-fields:
 content-Type
 content-Disposition
 content-Length
 originator
content-Type [2] OC 0x80 GraphicString This field specifies the media type of
a SIP message, such as
application/zip, image/gif, or
audio/mpeg.
content-Disposition [2] OC 0x81 GraphicString This field specifies the way in which
a SIP message is deployed.
content-Length [2] OC 0x82 INTEGER This field specifies the length of a
SIP message.
originator [2] OC 0xA3 CHOICE A sub-field of list-Of-Message-
Bodies. This field specifies the ID of
the originating party of the message
body. This field is derived from
originator in the S-CSCF CDRs.
sIP-URI [3] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 22

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordExtensions OC 0xB9 SET OF It is reserved for future expansion

and is not in use at present.
expiresInformation OC 0x9A INTEGER "Expires" from SIP Message.
list-Of-Associated- OC 0xBB SEQUENCE OF It is reserved for future expansion
URI and is not in use at present.
event OC 0x9C UTF8String This field specifies the content of the
event header.
accessNetworkInform OC 0x9D OCTET STRING This field specifies the details about
ation special access technologies.
serviceContextID OC 0x9E UTF8String This field specifies the specific
services in a session.
list-of-subscription-ID OC 0xBF 1F SEQUENCE OF This field records the IDs of the
[1]
subscriptions of the services.
subscriptionIDType [2] OC 0x80 ENUMERATED This field specifies the type of the
subscription ID.
The types are represented as
follows:
 eND-USER-E164 (0)
 eND-USER-IMSI (1)
 eND-USER-SIPURI (2)
 eND-USER-NAI (3)
 eND-USER-PRIVATE (4)
subscriptionIDData [2] OC 0x81 UTF8String This field specifies the ID of the
subscription of a specific service.
The value is the URI of the calling
party, called party, or connection
party.
list-Of-Early-sDP- OC 0xBF 20 SEQUENCE OF This field specifies the multimedia
Media-Components information (such as ring back tone)
before session establishment.
iMSCommunicationS OC 0xBF 21 OCTET STRING It is reserved for future expansion
erviceIdentifier and is not in use at present.
numberPortabilityRou OC 0x9F 22 GraphicString It is reserved for future expansion
ting and is not in use at present.
carrierSelectRouting OC 0x9F 23 GraphicString It is reserved for future expansion
and is not in use at present.
ims-3gpp-Session- OC 0x9F 24 INTEGER The field contains the priority of the
Priority session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 23

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

applicationServersInfo OC 0xBF 28 SEQUENCE OF A field of the group type. It contains

rmation [1] two sub-fields:
 applicationServersInvolved
 applicationProvidedCalledParties
applicationServersInv OC 0xA0 CHOICE This field specifies the AS ID
olved [2] identified by a SIP URI.
domainName [3] OC 0x81 GraphicString This field specifies the type of the
domain name.
applicationProvidedC OC 0xA1 SEQUENCE OF This field specifies the SN of the
alledParties [2] service triggered by the AS NE.
Because there may be multiple
services, this item is a list.
sIP-URI [3] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field is in tel URI format.
requested-Party- OC 0xBF 29 CHOICE This field specifies the address of
Address [1] the original called party in a SIP
transaction. The value is in SIP URI
or tel URI format. This field is used
when the address of the original
called party is inconsistent with the
value of Called Party Address.
This field is derived from
Requested-Party-Address in the S-
CSCF CDRs.
sIP-URI [2] OC 0x80 GraphicString This field specifies a SIP URI
address of the called party.
tEL-URI [2] OC 0x81 GraphicString This field specifies a tel URI address
of the called party.
list-Of-Called- OC 0xBF 2A SEQUENCE OF It is reserved for future expansion
Asserted-Identity and is not in use at present.
duration OC 0x9F 81 48 INTEGER This field specifies the call duration
in a SIP session.
onlineChargingType OC 0x9F 81 49 ENUMERATED This field specifies the type of
online charging.
origin-Callee-Party- OC 0xBF 81 4A CHOICE In the forwarding service, the field
Address [1] saves the forwarding called number.
The value can be in SIP URI or tel
URI format. This field is derived
from Origin-Callee-Party-Address
in the S-CSCF CDRs.
sIP-URI [2] OC 0x80 GraphicString This field specifies that the called
number is in SIP URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 24

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

tEL-URI [2] OC 0x81 GraphicString This field specifies that the called
number is in tel URI format.
dialled-Party-Address OC 0xBF 81 4B CHOICE This field identifies the address of
[1]
the original called party. It is
contained only in MOC CDRs. If
subscribers use the number change
service active, the dialed number
refers to the number before the
conversion. This field is derived
from Dialled-Party-Address in the
S-CSCF CDRs.
sIP-URI [2] OC 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OC 0x81 GraphicString This field specifies that the called
number is in tel URI format.
ringing-Duration OC 0x9F 81 4C INTEGER This field specifies the ringing
duration (between 180 and 200).
session-Priority OC 0x9F 81 4D INTEGER This field specifies the ID of an
urgent call.
carrier-Identification- OC 0x9F 81 4E GraphicString This field specifies the code of
Code carriers to be selected.
abnormal-Finish-Info OC 0xBF 81 4F SEQUENCE This field contains the reason why a
[1]
session or an event is ended
abnormally. The reason is carried in
a BYE message or other SIP
messages.
abnormalFinishWarni OC 0x80 GraphicString This field contains the warning code
ng [2] and text in the Warning header field
of a SIP message (a character string
contains two parts).
abnormalFinishReaso OC 0x81 GraphicString This field contains the cause and text
n [2] in the Reason header field of a SIP
message (a character string contains
two parts).
nP-Data [1] OC 0xBF 81 50 SET This field contains data information.
location-routing-numb OC 0x80 UTF8String This field contains the routing
er [2] number of the called party.
lrn-source-indicator [2] OC 0x81 INTEGER This field contains the source of the
LRN.
lrn-query-status [2] OC 0x82 INTEGER This field contains the query status
of the LRN.
refer-To OC 0x9F 81 51 UTF8String This field contains the refer-To
header field in a SIP session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 25

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

target OC 0x9F 81 52 UTF8String This field contains the target header

field in a SIP session.
inner-error OC 0x9F 82 09 INTEGER This field contains the information
about an inner faulty operation.
application-Servers- OC 0x9F 82 0A INTEGER This field specifies whether any
State unavailable AS exists.
list-of-application- OC 0xBF 82 0B UTF8String This field specifies the status of the
Servers-Abnormal unavailable AS subscribed by a
subscriber.
The SIP URL of the host name of
the unavailable AS in the SIP
session must be filled in this field.
serviceRequestTimeSt OC 0x9F 25 INTEGER This field set to the value (in
ampFraction (0..999) millisecond) of the field
serviceRequestTimeStamp.
serviceDeliveryStartTi OC 0x9F 26 INTEGER This field set to the value (in
meStampFraction (0..999) millisecond) of the field
serviceDeliveryStartTimeStamp.
serviceDeliveryEndTi OC 0x9F 27 INTEGER This field set to the value (in
meStampFraction (0..999) millisecond) of the field
serviceDeliveryEndTimeStamp.
Segment-Id OC 0x9F 82 2C Unsigned32 This AVP contains the identification
of the subscriber's segment
(e.g. prepaid or postpaid)

3.2 P-CSCF CDR

The tag value in the P-CSCF CDR is 0xBF 40.

Table 3-1 Format of P-CSCF CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

CDR, indicating which NE generated
the CDR.
retransmission OC 0x81 NULL This field specifies whether the
ACRs from the P-CSCF are sent
repeatedly.
sIP-Method OC 0x82 GraphicString This field specifies the reason why
ACRs are generated. This field is
only available in unrelated sessions.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 26

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

role-of-Node OM 0x83 INTEGER This field specifies the role of the P-

CSCF in the current session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ME that
provides the charging messages. It
can be an IP address or a valid
domain name of the ME providing
charging data. This field is derived
from Origin-Host in the P-CSCF
CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the session ID.
For a SIP session, the session ID
contains the SIP call ID as defined in
the SIP RFC3261 [404].
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field contains the number
Address [1] information about the calling party.
It can be in SIP URI format or tel
URI format. This field contains
multiple values in a CDR. This field
is derived from the Calling-Party-
Address AVP in the P-CSCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
called-Party-Address OM 0xA7 CHOICE This field specifies the number
[1]
information about the called party. It
can be in SIP URI format or tel URI
format. This field is derived from
Called-Party-Address in the P-
CSCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when a
imeStamp (SIZE(9)) peer NE receives a response after the
peer NE initiates a session request.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 27

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE initiates a request to end a
session.
recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation starts. This
field shows the time when the CCF
receives the first ACR in a session.
At present, it is present only in the
cases related to SIP sessions.
recordClosureTime OM 0x8D OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation ends. This
field shows the time when the CCF
receives the last ACR in a session.
interOperatorIdentifie OC 0xAE SEQUENCE OF This field specifies the identities of
rs [1] the pair of an originating network
and a terminating network in SIP
signaling transmission.
This field contains the following
sub-fields:
 originatingIOI
 terminatingIOI
originatingIOI [2] OC 0x80 GraphicString This field identifies the network that
serves the calling party.
terminatingIOI [2] OC 0x81 GraphicString This field identifies the network that
serves the called party.
localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN
Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.
recordSequenceNumb OC 0x90 INTEGER This field is filled only when
er incomplete CDRs are to be
generated.
In the case of timeout or other cases,
the CCF may generate multiple
partial CDRs for the same charging
session. In that case, the CCF
allocates a record SN (starting with
1) to each partial CDR.
It helps the BS check whether a CDR
is complete.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 28

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

causeForRecordClosi OM 0x91 ENUMERATED This field specifies the reason why a

ng session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field provides additional
Indication [1] diagnostics when the CCF finds that
charging data is missing.
It contains the following three sub-
fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
This field shows whether the CDR
content is complete. If the CDR
misses a partial ACR, the CCF fills
in the following fields:
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
iMS-Charging- OM 0x93 OCTET STRING This field is assigned by the first
Identifier accessed ME in the IMS domain and
sent to all MEs in the IMS domain. It
is unique in an end-to-end session.
This field is also called ICID for
short.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 29

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-sDP-Media- OC 0xB5 SEQUENCE OF A field of the group type.

Components [1] It contains several sub-fields
associated with one media
component. This field is present in
only one SIP session and may appear
several times in one CDR because
one CDR may contain multiple
sessions.
It describes the details about media
changes in an E2E session. For
example, calling party A starts voice
communications with called party B
at 9:00 am. Then, A and B change
the communication way into video at
9:30 a.m. The initiator of the video
communications can be A or B.
This field is essential to the CCF and
the BS.
This field contains the following
sub-fields:
 sDP-Session-Description
 SIP-Request-Timestamp
 SIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
sIP-Request- OM 0x80 OCTET STRING This field specifies when the SIP
Timestamp [2] (SIZE(9)) Request is initiated.
sIP-Response- OM 0x81 OCTET STRING Time when the response to the SIP
Timestamp [2] (SIZE(9)) request is sent.
sDP-Media- OM 0xA2 SEQUENCE OF A field of the group type.
Components [2] It contains several sub-fields
associated with one media
component. Because several media
components may exist for a session
in parallel, these sub-fields may
appear several times.
This field contains the following
sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id
sDP-Media-Name [3] OM 0x80 GraphicString This field specifies the media name.
It contains the information indicated
by the line m= in the SDP
information.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 30

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sDP-Media- OM 0xA1 SEQUENCE OF The session description, including

Descriptions [3] the IP address that provides media
support.
gPRS-Charging-Id [3] OM 0x82 INTEGER This field specifies the ID of the
GGSN that provides bearer at the
bearer layer (PS domain), namely,
GCID. It is implemented by
converting the numeric string into
integers. If the PS domain bearer
changes, the IMS domain is notified
of the field. The BS then uses the
ICID and GCID to associate with
CDRs.
accessNetworkChargi OM 0x84 GraphicString This field specifies the access
ngIdentifier [3] network charging ID.
authorized-QoS [3] OC 0x83 GraphicString This field authorizes the QoS for
end-to-end services.
mediaInitiatorFlag [2] OC 0x83 NULL This field specifies whether the
media initiated by the called party
changes.
sDP-Session- OC 0xA4 SEQUENCE OF This field specifies the session
Description [2] portion of the SDP data exchanged
between user agents in the SIP
transaction.
This field is the attribute line (i=, c=,
b=, k=, a=, ...) in an SDP message
and used to describe a session.
mediaInitiatorParty [2] OC 0xA5 CHOICE This field is reserved for future
expansion and is not in use at
present.
sIP-Request- OC 0x86 Unsigned32 This field specifies the SIP request
Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the field SIP-
Request-Timestamp.
sIP-Response- OC 0x87 Unsigned32 This field specifies the SIP response
Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the field SIP-
Response-
Timestamp.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 31

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

gGSNaddress OC 0xB6 CHOICE This field specifies the IP address of

the GGSN that provides media
bearer support.
The value of the first two bytes of
the ID address can be one of the
following:
 1: IPv4 IP address.
 2: IPv6 IP address.
serviceReasonReturn OM 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails.
It is displayed as
serviceDeliveryFailureReason in
the R5 version and
serviceReasonReturnCode in the
R6 version.
list-Of-Message- OC 0xB8 SEQUENCE OF A field of the group type.
Bodies [1] It contains several sub-fields
describing the SIP messages
transmitted between the IMS NEs.
Because SIP signaling may be
exchanged among several messages,
the field may appear several times.
This field contains the following
sub-fields:
 content-Type
 content-Disposition
 content-Length
 originator
content-Type [2] OC 0x80 GraphicString This field specifies the media type of
a SIP message, such as
application/zip, image/gif, or
audio/mpeg.
content-Disposition [2] OC 0x81 GraphicString This field specifies the way in which
a SIP message is deployed.
content-Length [2] OC 0x82 INTEGER This field specifies the length of a
SIP message.
originator [2] OC 0xA3 CHOICE A sub-field of list-Of-Message-
Bodies. This field specifies the ID of
the originating party of the message
body. This field is derived from
originator in the P-CSCF CDRs.
sIP-URI [3] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 32

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordExtensions OC 0xB9 SET OF This field is reserved for future

expansion and is not in use at
present.
expiresInformation OC 0x9A INTEGER "Expires" from SIP Message.
list-Of-Associated- OC 0xBB SEQUENCE OF It is reserved for future expansion
URI and is not in use at present.
event OC 0x9C UTF8String This field specifies the content of the
event header.
accessNetworkInform OC 0x9D OCTET STRING This field specifies the details about
ation special access technologies.
serviceContextID OC 0x9E UTF8String This field specifies the specific
services in a session.
list-of-subscription-ID OC 0xBF 1F SEQUENCE OF This field records the IDs of the
[1]
subscriptions of the services.
subscriptionIDType [2] OC 0x80 ENUMERATED This field specifies the type of the
subscription ID.
The types are represented as follows:
 eND-USER-E164 (0)
 eND-USER-IMSI (1)
 eND-USER-SIPURI (2)
 eND-USER-NAI (3)
 eND-USER-PRIVATE (4)
subscriptionIDData [2] OC 0x81 UTF8String This field specifies the ID of the
subscription of a specific service.
The value is the URI of the calling
party, called party, or connection
party.
list-Of-Early-sDP- OC 0xBF 20 SEQUENCE OF This field specifies the multimedia
Media-Components information (such as ring back tone)
before session establishment.
numberPortabilityRou OC 0x9F 22 GraphicString This field is reserved for future
ting expansion and is not in use at
present.
carrierSelectRouting OC 0x9F 23 GraphicString This field is reserved for future
expansion and is not in use at
present.
ims-3gpp-Session- OC 0x9F 24 INTEGER The field contains the priority of the
Priority session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 33

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

servedPartyIPAddress OC 0xBF 32 IPAddress This field specifies the IP address of

the called party or the calling party.
The P-CSCF uses it to keep in touch
with the called party or calling party.
duration OC 0x9F 81 48 NTEGER This field specifies the call duration
in a SIP session.
privateUserID OM 0x88 GraphicString This field specifies the used network
access ID of the served party
according to the RFC2486 [405].
ringing-Duration OC 0x9F 81 4C INTEGER This field specifies the ringing
duration (between 180 and 200).
session-Priority OC 0x9F 81 4D INTEGER This field is the ID of an urgent call.
abnormal-Finish-Info OC 0xBF 81 4F SEQUENCE This field contains the reason why a
[1]
session or an event is ended
abnormally. The reason is carried in
a BYE message or other SIP
messages.
abnormalFinishWarni OC 0x80 GraphicString This field contains the warning code
ng [2] and text in the Warning header field
of a SIP message (a character string
contains two parts).
abnormalFinishReaso OC 0x81 GraphicString This field contains the cause and text
n [2] in the Reason header field of a SIP
message (a character string contains
two parts).
refer-To OC 0x9F 81 51 UTF8String This field contains the refer-To
header field in a SIP session.
target OC 0x9F 81 52 UTF8String This field contains the target header
field in a SIP session.
locationInformation OC 0x9F 81 70 GraphicString This field specifies the location of
the exchange providing services.
This field is defined by Huawei.
inner-error OC 0x9F 82 09 INTEGER This field contains the information
about an inner faulty operation.
charge-Category OC 0x9F 82 0C ENUMERATED This field is reserved.
serviceRequestTimeSt OC 0x9F 25 INTEGER This field set to the value (in
ampFraction (0..999) millisecond) of the field
serviceRequestTimeStamp.
serviceDeliveryStartT OC 0x9F 26 INTEGER This field set to the value (in
imeStampFraction (0..999) millisecond) of the field
serviceDeliveryStartTimeStamp.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 34

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceDeliveryEndTi OC 0x9F 27 INTEGER This field set to the value (in

meStampFraction (0..999) millisecond) of the field
serviceDeliveryEndTimeStamp.

3.3 I-CSCF CDR

The tag value in the I-CSCF CDR is 0xBF 41.

Table 3-1 Format of I-CSCF CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

CDR, indicating which NE
generated the CDR.
retransmission OC 0x81 NULL This field specifies whether the
ACRs from the I-CSCF are sent
repeatedly.
sIP-Method OC 0x82 GraphicString This field specifies the reason why
ACRs are generated. This field is
only available in unrelated sessions.
role-of-Node OM 0x83 INTEGER This field specifies the role of the I-
CSCF in the current session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ME that
provides the charging messages. It
can be an IP address or a valid
domain name of the ME providing
charging data. This field is derived
from Origin-Host in the I-CSCF
CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the session ID.
For a SIP session, the session ID
contains the SIP call ID as defined in
the SIP RFC3261 [404].

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 35

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field specifies the number

Address [1] information about the calling party.
It can be in SIP URI format or tel
URI format. This field contains
multiple values in a CDR. This field
is derived from Calling-Party-
Address in the I-CSCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
called-Party-Address OM 0xA7 CHOICE This field specifies the number
[1]
information about the called party. It
can be in SIP URI format or tel URI
format. This field is derived from
Called-Party-Address in the I-
CSCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
interOperatorIdentifie OC 0xAE SEQUENCE OF This field specifies the identities of
rs [1] the pair of an originating network
and a terminating network in SIP
signaling transmission.
This field contains the following
sub-fields:
 originatingIOI
 terminatingIOI
originatingIOI [2] OC 0x80 GraphicString This field identifies the network that
serves the called party.
terminatingIOI [2] OC 0x81 GraphicString This field specifies the ID of a
terminating network.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 36

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN

Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.
causeForRecordClosi OM 0x91 ENUMERATED This field specifies the reason why a
ng session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field provides additional
Indication [1] diagnostics when the CCF finds that
charging data is missing.
It contains the following three sub-
fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
This field shows whether the CDR
content is complete. If the CDR
misses a partial ACR, the CCF fills
in the following fields:
 aCRStartLost: If the charging
information on the Start type is
missing, the value is TRUE.
Otherwise, the value is FALSE.
 aCRInterimLost: If there is
charging information on the
Interim type, the value of this
field is NO. Otherwise, the value
is YES. If it is uncertain whether
the charging information is
missing, the value is
UNKNOWN.
 aCRStopLost: If the charging
information on the Stop type is
missing, the value is TRUE.
Otherwise, the value is FALSE.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 37

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the

Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
iMS-Charging- OM 0x93 OCTET STRING This field is assigned by the first
Identifier accessed ME in the IMS domain and
sent to all MEs in the IMS domain.
It is unique in an end-to-end session.
This field is also called ICID for
short.
serviceReasonReturn OM 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails.
It is displayed as
serviceDeliveryFailureReason in
the R5 version and
serviceReasonReturnCode in the
R6 version.
recordExtensions OC 0xB9 SET OF This field is reserved for future
expansion and is not in use at
present.
expiresInformation OC 0x9A INTEGER "Expires" from SIP Message.
list-Of-Associated- OC 0xBB SEQUENCE OF It is reserved for future expansion
URI and is not in use at present.
event OC 0x9C UTF8String This field specifies the content of the
event header.
accessNetworkInform OC 0x9D OCTET STRING This field specifies the details about
ation special access technologies.
serviceContextID OC 0x9E UTF8String This field specifies the specific
services in a session.
numberPortabilityRou OC 0x9F 22 GraphicString This field is reserved for future
ting expansion and is not in use at
present.
carrierSelectRouting OC 0x9F 23 GraphicString This field is reserved for future
expansion and is not in use at
present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 38

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

ims-3gpp-Session- OC 0x9F 24 INTEGER The field contains the priority of the

Priority session.
s-CSCF-Information OC 0xBF 3D SEQUENCE This field is reserved for future
expansion and is not in use at
present.
list-Of-Message- OC 0xB8 SEQUENCE OF A field of the group type.
Bodies [1] It contains several sub-fields
describing the SIP messages
transmitted between the IMS NEs.
Because SIP signaling may be
exchanged among several messages,
the field may appear several times.
This field contains the following
sub-fields:
 content-Type
 content-Disposition
 content-Length
 originator
content-Type [2] OC 0x80 GraphicString This field specifies the media type of
a SIP message, such as
application/zip, image/gif, or
audio/mpeg.
content-Disposition [2] OC 0x81 GraphicString This field specifies the way in which
a SIP message is deployed.
content-Length [2] OC 0x82 INTEGER This field specifies the length of a
SIP message.
originator [2] OC 0xA3 CHOICE A sub-field of list-Of-Message-
Bodies. This field specifies the ID of
the originating party of the message
body. This field is derived from
originator in the I-CSCF CDRs.
sIP-URI [3] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field is in tel URI format.
list-of-subscription-ID OC 0xBF 1F SEQUENCE OF This field records the IDs of the
[1]
subscriptions of the services.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 39

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

subscriptionIDType [2] OC 0x80 ENUMERATED This field specifies the type of the
subscription ID.
The types are represented as follows:
 eND-USER-E164 (0)
 eND-USER-IMSI (1)
 eND-USER-SIPURI (2)
 eND-USER-NAI (3)
 eND-USER-PRIVATE (4)
subscriptionIDData [2] OC 0x81 UTF8String This field specifies the ID of the
subscription of a specific service.
The value is the URI of the calling
party, called party, or connection
party.
abnormal-Finish-Info OC 0xBF 81 4F SEQUENCE This field contains the reason why a
[1]
session or an event is ended
abnormally. The reason is carried in
a BYE message or other SIP
messages.
abnormalFinishWarni OC 0x80 GraphicString This field contains the warning code
ng [2] and text in the Warning header field
of a SIP message (a character string
contains two parts).
abnormalFinishReaso OC 0x81 GraphicString This field contains the cause and text
n [2] in the Reason header field of a SIP
message (a character string contains
two parts).

3.4 ATS9900 CDR

The tag value in the ATS9900 CDR is 0xBF 45.
Fields marked with ● indicate that the Vobb(Fixed Only) Vobb(FMC) or Volte service is
supported. Fields marked with ○ indicate that the Vobb(Fixed Only) Vobb(FMC) or Volte
service is not supported.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 40

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Table 3-1 Format of ATS9900 CDR

Field Cate TAG Field Vob Vob Volt Description
gory Type b(Fi b(F e
xed MC)
Only
)
recordType M 0x80 INTEGER ● ● ● This field identifies the type of
the final CDR generated for a
session, indicating the NE that
generates the CDR.
For details, see section 4.156
"recordType."
retransmission OC 0x81 NULL ● ● ● This field specifies whether the
CDR contains ACRs
retransmitted by NE. This field
is mandatory when there is a
retransmitted ACR. If this field
is displayed in the CDR, ACRs
retransmitted by NE are
contained in this CDR. If this
field is not displayed in the
CDR, ACRs retransmitted by
NE are not contained.
The value of this field is derived
from the Retransmission field in
the Diameter message header.
For details, see section 4.160
"retransmission."
sIP-Method OC 0x82 GraphicSt ● ● ● This field specifies the type of
ring the SIP message for charging,
for example, INVITE,
UPDATE, BYE, and CANCEL.
If the session ends properly, the
value of this field is BYE or
CANCEL.
The value of this field is derived
from the SIP-Method field in
Event-Type in the last ATS9900
ACR received by the CCF.
For details, see section 4.196
"sIP-Method."
role-of-Node OM 0x83 INTEGER ● ● ● This field specifies the role of
the NE in a session. The value
of this field is derived from the
Role-Of-Node field in the
ATS9900 CDR.
For details, see section 4.163
"role-of-Node."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 41

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

domainName [2] OM 0x81 GraphicSt ● ● ● This field specifies the host

ring name of the ME that generates
the current charging message.
session-Id OM 0x85 GraphicSt ● ● ● This field specifies the ID of a
ring SIP session, that is, Call-ID in a
SIP message.
The value of this field is derived
from the User-Session-Id field
in an ATS9900 ACR.
For details, see section 4.192
"session-Id."
list-Of-Calling- OM 0xA6 SEQUEN ● ● ● This field specifies the number
Party-Address [1] CE OF information about the calling
party. The value of this field is
derived from the Calling-Party-
Address field in an ATS9900
ACR.
For details, see section 4.82
"list-Of-Calling-Party-Address."
sIP-URI [2] OM 0x80 GraphicSt ● ● ● This field specifies that the
ring calling number is in SIP URI
format.
tEL-URI [2] OM 0x81 GraphicSt ● ● ● This field specifies that the
ring calling number is in tel URI
format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 42

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 43

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 44

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 45

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 46

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 47

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 48

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 49

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 50

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)
sIP-Request- OC 0x86 Unsigned3 ● ● ● This field specifies the SIP
Timestamp- 2 request fraction time. It is set to
Fraction [2] the value (in millisecond) of the
SIP-Request-Timestamp field.
The value of this field is derived
from the SIP-Request-
Timestamp-Fraction field in an
ATS9900 ACR.
For details, see section 4.198
"sIP-Request-Timestamp-
Fraction."
sIP-Response- OC 0x87 Unsigned3 ● ● ● This field specifies the SIP
Timestamp- 2 response fraction time. It is set
Fraction [2] to the value (in millisecond) of
the field SIP-Response-
Timestamp.
The value of this field is derived
from the SIP-Response-
Timestamp-Fraction field in an
ATS9900 ACR.
For details, see section 4.200
"sIP-Response-Timestamp-
Fraction."
gGSNaddress [1] OC 0xB6 CHOICE ● ● ● This field carries the IP address
of the Gateway GPRS Support
Node (GGSN) that generates the
GPRS charging number. The
value of this field is derived
from the GGSN-Address field in
an ATS9900 ACR.
For details, see section 4.69
"gGSNaddress."
iPAddress [2] OC 0xA0 CHOICE ● ● ● This field specifies the IP
address.
serviceReasonRe OM 0x97 UTF8Strin ● ● ● This field specifies the reason
turnCode g why a service request succeeds
or fails.
For details, see section 4.187
"serviceReasonReturnCode."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 51

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 52

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 53

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 54

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)
subscriptionIDT OC 0x80 ENUMER ● ● ● This field specifies the type of
ype [2] ATED the subscription ID.
The value of this field is derived
from the Subscription-Id-Type
field in an ATS9900 ACR.
For details, see section 4.210
"subscriptionIDType."
subscriptionIDD OC 0x81 UTF8Strin ● ● ● This field specifies the ID of the
ata [2] g subscription of a specific
service. The value is the URI of
the calling party, called party, or
connection party.
If the ATS9900 is on the
originating side, the field
records the URI of the calling
party.
If the ATS9900 is on the
terminating side, the field
records the URI of the called
party.
The value of this field is derived
from the Subscription-Id-Data
field in an ATS9900 ACR.
For details, see section 4.209
"subscriptionIDData."
list-Of-Early- OC 0xBF 20 SEQUEN ○ ○ ○ This field is reserved for future
sDP-Media- CE OF expansion and is not in use at
Components present.
iMSCommunicat OC 0xBF 21 OCTET ○ ○ ○ This field is reserved for future
ionServiceIdentif STRING expansion and is not in use at
ier present.
numberPortabilit OC 0x9F 22 GraphicSt ○ ○ ○ This field is reserved for future
yRouting ring expansion and is not in use at
present.
carrierSelectRout OC 0x9F 23 GraphicSt ○ ○ ○ This field is reserved for future
ing ring expansion and is not in use at
present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 55

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 56

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)
requested-Party- OC 0xBF 65 CHOICE ● ● ● This field specifies the address
Address [1] of the original called party in a
SIP transaction. The value is in
SIP URI or tel URI format.
The value of this field is derived
from the Requested-Party-
Address field in an ATS9900
ACR.
For details, see section 4.159
"requested-Party-Address."
sIP-URI [2] OC 0x80 GraphicSt ● ● ● This field specifies that the
ring called address is in SIP URI
format.
tEL-URI [2] OC 0x81 GraphicSt ● ● ● This field specifies that the
ring called address is in tel URI
format.
list-Of-Called- OC 0xBF 66 SEQUEN ● ● ● This field identifies the address
Asserted-Identity CE OF of the final called party. It is
[1]
contained only in MOC CDRs.
It records the number of the
number who answered a basic
call. In event CDRs, this field is
set to Empty.
The value of this field is derived
from the Called-Asserted-
Identity field in an ATS9900
ACR.
For details, see section 4.83
"list-Of-Called-Asserted-
Identity."
sIP-URI [2] OC 0x80 GraphicSt ● ● ● This field specifies that the
ring called address is in SIP URI
format.
tEL-URI [2] OC 0x81 GraphicSt ● ● ● This field specifies that the
ring called address is in tel URI
format.
alternateCharged OC 0x9F 67 UTF8Strin ○ ○ ○ This field is reserved for future
PartyAddress g expansion and is not in use at
present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 57

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)

initialIMS- OC 0x9F69 OCTET ● ○ ● This field is used to associate

Charging-Identifier STRING CDRs generated for a VoLTE
session in which a
SRVCC/eSRVCC handover
occurs. During a
SRVCC/eSRVCC handover, a
CDR containing this field is
generated. This field contains
the ICID of CDRs generated
before the handover.
For details, see section 4.77
"initialIMS-Charging-
Identifier."
duration OC 0x9F 81 INTEGER ● ● ● This field specifies the duration
48 of a SIP session.
For details, see section 4.62
"duration."
serviceIdentifier OC 0xBF 81 SEQUEN ● ○ ○ This field contains the
55 CE OF information about the services
that the subscriber uses. In event
CDRs, this field is set to the
actual service identifier. In basic
call CDRs, this field is set to
BASICCALL.
The value of this field is derived
from the Service-Identifier field
in an ATS9900 ACR.
For details, see section 4.182
"serviceIdentifier."
np-Route-Numbe OC 0x9F 81 OCTET ● ○ ○ This field contains the
r 53 STRING information about the new
number in NP service. The
value of this field is derived
from the NP-Route-Number
field in an ATS9900 ACR.
For details, see section 4.120
"np-Route-Number."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 58

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 59

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 60

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 61

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 62

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 63

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 64

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 65

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 66

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 67

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 68

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

second-level- Oc 0x9F 81 INTEGER ● ○ ○ This field specifies the number

bill-group 7B of the second-level bill group to
which the subscriber belongs.
The value of this field is derived
from the Second-Level-Bill-
Group field in an ATS9900
ACR.
For details, see section 4.174
"second-level-bill-group."
onlineChargingF Oc 0x9F 81 ENUMER ● ● ● Field for China Mobile.
lag 16 ATED It is the online charging flag and
mandatory when both the online
charging and offline charging
are deployed. If the online
charging has performed for a
service, the CDR does not
contain the offline charging.
Enumerative value:
 0: The current subscriber is an
offline charging subscriber.
 1: The current subscriber is an
online charging subscriber.
 2: Online charging is
abnormal.
The value of this field is derived
from the Online-Charging-Flag
field in an ATS9900 ACR.
For details, see section 4.125
"onlineChargingFlag."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 69

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 70

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 71

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 72

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 73

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 74

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 75

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 76

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 77

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 78

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 79

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 80

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)
pBX-Pilot- Oc 0x9F 82 UTF8Strin ● ○ ○ This field specifies the PBX
Number 03 g pilot number of the business
trunk to which the subscribers
belong. This field is available
only for calls made by business
trunking subscribers and
supplyment services.
This field is derived from PBX-
Pilot-Number in the ATS9900
CDRs.
For details, see section 4.140
"pBX-Pilot-Number."
Valueadded- Oc 0xBF 82 SEQUEN ● ○ ○ This field, which is originated
Service-Identity- 04 CE OF from the Valueadded-Service-
List Identity AVP of the ATS9900
CDR, identifies the type of
value-added service that the
calling party has subscribed to.
Its value ranges from 1 to 32.
virtual-Caller- Oc 0xBF 82 CHOICE ● ○ ○ This field contains the virtual
Number 0E caller number generated by
Emulational Local Call service.
This field is derived from
virtual-Caller-Number in the
ATS9900 CDRs.
sIP-URI [2] OM 0x80 GraphicSt ● ○ ○ Number is SIP URI format.
ring
tEL-URI [2] OM 0x81 GraphicSt ● ○ ○ Number is SIP URI format.
ring
charging-Label Oc 0X9F 82 UTF8Strin ● ○ ○ This AVP contains the charging
0F g label generated by Emulational
Local Call service.This field is
derived from charging-Label in
the ATS9900 CDRs.
emulational- Oc 0x9F 83 UTF8Strin ● ○ ○ This AVP contains ATS’s
Service-Type 14 g domain name generated by
Emulational Local Call
service.This field is derived
from emulational-Service-Type
in the ATS9900 CDRs.
serviceRequestTi Oc 0x9F 25 INTEGER ● ○ ○ This field set to the value (in
meStampFractio (0..999) millisecond) of the field
n serviceRequestTimeStamp.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 81

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)
serviceDeliveryS Oc 0x9F 26 INTEGER ● ○ ○ This field set to the value (in
tartTimeStampFr (0..999) millisecond) of the field
action serviceDeliveryStartTimeStamp.
serviceDeliveryE Oc 0x9F 27 INTEGER ● ○ ○ This field set to the value (in
ndTimeStampFra (0..999) millisecond) of the field
ction serviceDeliveryEndTimeStamp.
calling-User- Oc 0x9F 81 INTEGER ● ○ ○ This field indicates the type of
Type 6F the calling user. This field is
derived from Calling-User-Type
AVP in the ATS9900 ACRs.
For details, see section 4.41
"calling-User-Type"
user-Charging- Oc 0x9F 83 INTEGER ● ○ ○ This field indicates the charging
Category 75 type of subscribers and it is set
to the charging type of the
subscriber obtained from the
user profile of the subscriber.
This field is derived from User-
Charging-Category AVP in the
ATS9900 ACRs.
0: CHARGE-NORMAL
1: CHARGE-FREE
2: CHARGE-PREPAID
charging- Oc 0x9F831 ENUMER ● ○ ○ This field is used to determine
Complaint 2 ATED whether the ATS9900
additionally generates a
complaint CDR for outgoing
calls of a subscriber.
This field is derived from
Charging-Complaint AVP in the
ATS9900 ACRs.
For details, see section 4.45
"charging-Complaint".

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 82

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 83

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 84

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)
call-Reference- Oc 0x81 UTF8Strin ○ ○ ● This field carries the IN service
Number[2] g call reference number. This field
is derived from Call-Reference-
Number AVP in the ATS9900
ACRs.
fci-Free-Format- Oc 0x82 OCTET ○ ○ ● This field is used to carry data
Data[2] STRING contained in one or multiple FCI
messages and is identified by
corresponding filling manners.
This field is derived from Fci-
Free-Format-Data AVP in the
ATS9900 ACRs.
fci-Free-Format- Oc 0x83 ENUMER ○ ○ ● This field is used to identify the
Data-Manne[2] ATED filling mode of the Fci-Free-
Format-Data and is contained in
the FCI messages of the IN
services.
This field is derived from Fci-
Free-Format-Data-Manne AVP
in the ATS9900 ACRs.
For details, see section 4.66
"fci-Free-Format-Data-Manne".
default-Call- Oc 0x84 ENUMER ○ ○ ● This field is used to identify the
Handling[2] ATED default call process type of IN
service. if no default call
process occurred, this field
doesn't appear.
process type:
0：CONTINUE
1：RELEASE
Scf-Address[2] Oc 0x85 OCTET ○ ○ ● This field specifies the SCP
STRING Address to current Intelligent
Service.This field is derived
from Scf-Address AVP in the
ATS9900 ACRs.
0xF is an invalid value and the
BC filters out it during CDR
parsing.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 85

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 86

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Cate TAG Field Vob Vob Volt Description

gory Type b(Fi b(F e
xed MC)
Only
)
location-Info[2] OC 0x80 UTF8Strin ○ ● ○ This field is used to carry cell
g information change during calls
in call CDRs generated for the
DHZ service.
This field is derived from
Location-Info AVP in the
ATS9900 ACRs.
private-User- Oc 0xBF83 SEQUEN ○ ○ ● This field is of type Grouped
Equipment- 22 CE and carries the identity and
Info[1] capability of the terminal.
This field contains the following
sub- fields:
{ User-Equipment-Info-Type }
{ User-Equipment-Info-Value }
private-User- Om 0x80 ENUMER ○ ○ ● This field carries the
Equipment-Info- ATED information type of the User-
Type[2] Equipment-Info-Value.
For details, see section4.148
private-User-Equipment-Info-
Type.
private-User- Om 0x81 OCTET ○ ○ ● This field carries terminal
Equipment-Info- STRING information. Current, it carries
Value[2] only the IMEI.
private- Oc 0x9F832 INTEGER ● ● ● This field is used to identify the
MediaPartialRec 3 (0..429496 consecutive partial CDRs
ordNumber 7295) generated for the same media
type within a session when
media switching occurs in the
session.
For details, see section 4.146
"private-
MediaPartialRecordNumber"
user-Agent- Oc 0x9F832 UTF8Strin ○ ○ ● This field is used to carry the
Value 4 g User-Agent header field value
of the INVITE message
received from the originating
side.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 87

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

3.5 MediaX3600 CDR

The tag value in the MediaX3600 CDR is 0xBF 81 4C.

Table 3-1 Format of MedaiX3600 CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the CDR type. In

detail, it specifies the ME that
generates the CDR.
retransmission OC 0x81 NULL This field specifies whether to
retransmit ACR messages from
trunks.
sIP-Method OC 0x82 GraphicString This field does not exist at present. No
intervention is required.
role-of-Node OM 0x83 INTEGER This field specifies the role of the
MediaX3600 in the current session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ME that
provides the charging messages. It can
be an IP address or a valid domain
name of the ME providing charging
data. This field is derived from
Origin-Host in the MediaX CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the session ID. For
a SIP session, it specifies the ID of the
SIP session in IETF RFC 3261 [404].
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field specifies the address of the
Address [1] party that requests or initiates the SIP
transaction. This field can include the
SIP URI or tel URI of the calling
party.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 88

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

called-Party-Address OM 0xA7 CHOICE This field specifies the actual address

[1]
of the called party of the SIP
transaction. For example, in the
subscription or registration
transaction, the called-Party-Address
field is identified as the actual address
of the party that completes the
subscription or registration. This field
can include the SIP URI or tel URI.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time requested
amp (SIZE(9)) by the SIP.
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when the
imeStamp (SIZE(9)) NE receives the response after the NE
initiates a session request.
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when the
meStamp (SIZE(9)) NE requests to end the session.
recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when the
(SIZE(9)) CCF receives the first ACR. At
present, this field exists only in the
session.
recordClosureTime OM 0x8D OCTET STRING This field specifies the time when the
(SIZE(9)) CCF receives the last ACR.
interOperatorIdentifie OC 0xAE SEQUENCE OF This field does not exist at present. No
rs [1] intervention is required.
originatingIOI [2] OC 0x80 GraphicString This field does not exist at present. No
intervention is required.
terminatingIOI [2] OC 0x81 GraphicString This field does not exist at present. No
intervention is required.
localRecordSequence OM 0x8F INTEGER (0- The CCF assigns a unique and
Number 4294967295) consecutive number for each CDR
related to the MediaX3600. The
number begins with 1. That is, the
localRecordSequenceNumber
assigned for each CDR by the same
CCF is unique.
This field is used to determine
whether a CDR is lost. The value of
this field is unique in the entire
charging data.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 89

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordSequenceNumb OC 0x90 INTEGER Only when partial CDR is generated,

er the CCF needs to fill this field. If the
CCF generates several partial CDRs
for one charging session because of
timeout or else, the CCF assigns
recordSequenceNumber for each
partial CDR. The number begins with
1 and increases by 1 consecutively.
This field is used to determine
whether the partial CDR of a session
is lost.
causeForRecordClosi OC 0x91 ENUMERATED This field identifies the cause for
ng ending a session. Only event and stop
ACRs can fill this field. That is, only
in event and stop ACRs, the value of
this field exists.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field is used to request an
Indication [1] additional lost function record when
the charging data function is lack of
charging data.
This field includes three sub-fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
This field specifies whether the
content of the CDR is complete. If the
CDR is lack of the partial ACR, this
field is set as follows:
 aCRStartLost: If the charging
message of the Start type is lost,
the value of this field is set to
True; otherwise, it is set to False.
 aCRInterimLost: If the charging
message of the interim type exists,
the value of this field is set to No;
otherwise, it is set to Yes. If it is
unknown whether the charging
message of the interim type is lost,
the value of this field is set to
Unknown.
 aCRStopLost: If the charging
message of the Stop type is lost,
the value of this field is set to
True; otherwise, it is set to False.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 90

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

aCRStartLost [2] OC 0x80 BOOLEAN If the charging message of the Start

type is lost, the value of this field is
set to True; otherwise, it is set to
False.
aCRInterimLost [2] OC 0x81 ENUMERATED If the charging message of the interim
type exists, the value of this field is
No; otherwise, it is Yes. If whether the
charging message of the interim type
is lost is unknown, the value of this
field is Unknown.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging message of the Stop
type is lost, the value of this field is
True; otherwise, it is False.
iMS-Charging- OM 0x93 OCTET STRING The first ME of the IMS assigns the
Identifier charging identifier for each ME in the
IMS domain. The value is unique in
an end-to-end session. This field is
also called ICID for short.
list-Of-sDP-Media- OC 0xB5 SEQUENCE OF This field is of the group type. It
Components [1] consists of several associated sub-
fields in the media information. This
field exists only in one session. One
CDR may include several sessions, so
it may contain more than one list-Of-
sDP-Media-Components.
This field describes details of media
changes in an end-to-end session. For
example, if calling party A initiates a
voice call to called party B at 09:00,
and then A or B initiates a video call
to the peer party at 9:30, the
communication media change is
recorded by this field.
This field is important for the CCF. It
is the key charging field of the
charging center.
This field contains the following
contents:
 sDP-Session-Description
 sIP-Request-Timestamp
 sIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
sIP-Request- OC 0x80 OCTET STRING This field specifies the time when a
Timestamp [2] (SIZE(9)) SIP request (the initiator).

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 91

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sIP-Response- OC 0x81 OCTET STRING This field specifies the time when a
Timestamp [2] (SIZE(9)) SIP request is responded.
sDP-Media- OC 0xA2 SEQUENCE OF This field is a group type field. It
Components [2] consists of several sub fields that
associate with certain media
information. These fields may exist in
CDRs of multiple time spans in a
session. Therefore, multiple media
components may exist.
The structure of this field is as
follows:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id
 accessNetworkChargingIdentifier
 authorized-QoS
sDP-Media-Name [3] OC 0x80 GraphicString This field specifies the name of a
session and the relevant protocol.
sDP-Media- OC 0xA1 SEQUENCE OF This field specifies the description of
Descriptions [3] a session. It provides the IP address of
a media supporting service.
gPRS-Charging-Id [3] OC 0x82 INTEGER This field is also called GCID for
short. In application, the numeric
strings are converted to integers. This
field identifies the GGSN that
provides the bearer capability on the
bearer layer (PS domain). If the bearer
in the PS domain changes, this field
will be sent to the IMS domain. The
charging center associates CDRs
using the ICID and the GCID. No
intervention is required at present.
authorized-QoS [3] OC 0x83 GraphicString This field authorizes the QoS for end-
to-end services.
sDP-Session- OC 0xA4 SEQUENCE OF This field specifies partial SDP
Description [2] (Session Description Protocol)
messages transmitted between proxies
in SIP message procedures. This field
is the attribute-line (i=, c=, b=, k=, a=,
...) part of the SDP messages and is
used to describe a session.
mediaInitiatorParty [2] OC 0xA5 CHOICE This field is reserved for future
expansion and is not in use at present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 92

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

gGSNaddress OC 0xB6 CHOICE This field specifies the IP address of

the GGSN that provides media bearer
support.
The value of the first two bytes of the
ID address can be one of the
following:
 1: IPv4 IP address.
 2: IPv6 IP address.
This field is reserved for future
expansion and is not in use at present.
serviceReasonReturn OM 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails. It is
displayed as
serviceDeliveryFailureReason in the
R5 version and
serviceReasonReturnCode in the R6
version.
list-Of-Message- OC 0xB8 SEQUENCE OF This field is of the group type. It
Bodies [1] describes the SIP messages between
IMS Esther. SIP signaling is
exchanged among several messages.
Therefore, this field may exist in
several time spans.
The structure of this field is as
follows:
 content-Type
 content-Disposition
 content-Length
 originator
content-Type [2] OC 0x80 GraphicString This field specifies the media type of a
SIP message, such as application/zip,
image/gif, or audio/mpeg.
content-Disposition [2] OC 0x81 GraphicString This field specifies the way in which a
SIP message is deployed.
content-Length [2] OC 0x82 INTEGER This field specifies the length of a SIP
message.
originator [2] OC 0xA3 CHOICE This field is a sub-field of list-Of-
Message-Bodies. It carries the ID of
the originating party of the SIP
message. This field is derived from
originator in the MediaX CDRs.
sIP-URI [3] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 93

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordExtensions OC 0xB9 SET OF This field is reserved for future

expansion and is unavailable now.
expiresInformation OC 0x9A INTEGER This field is reserved for future
expansion and is not in use at present.
event OC 0x9C UTF8String This field specifies the content of the
event header.
accessNetworkInform OC 0x9D OCTET STRING This field contains detailed access
ation technologies, such as protocols in use
and versions. For example: 3GPP-
UTRAN-TDD; utran-cell-id-
3gpp=234151D0FCE11.
Information in this field is sent to CCF
through accessNetworkInformation
FIELD of an MediaX3600ACR.
serviceContextID OC 0x9E UTF8String This field describes the ID of the party
who provides the service in the
session. The value of this field is
carried to CCF through
serviceContextID field by the
MediaX3600.
list-of-subscription-ID OC 0xBF 1F SEQUENCE OF This field is used to record the ID of
[1]
the user who subscribes a service. The
value is the URI of the calling party,
called party, or connection party.
subscriptionIDType [2] OC 0x80 ENUMERATED This field specifies the type of the
subscription ID.
The types are described as follows:
 eND-USER-E164 (0)
 eND-USER-IMSI (1)
 eND-USER-SIPURI (2)
 eND-USER-NAI (3)
 eND-USER-PRIVATE (4)
subscriptionIDData [2] OC 0x81 UTF8String This field specifies the ID of the
subscription of a specific service. The
value is the URI of the calling party,
called party, or connection party.
If the MediaX3600is on the
originating side, this field records the
URI of the calling party; if the
MediaX3600is on the terminating
side, this field records the URI of the
called party.
list-Of-Early-sDP- OC 0xBF 20 SEQUENCE OF This field is reserved for future
Media-Components expansion and is not in use at present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 94

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

iMSCommunicationS OC 0xBF 21 OCTET STRING This field is reserved for future

erviceIdentifier expansion and is not in use at present.
numberPortabilityRou OC 0x9F 22 GraphicString This field is reserved for future
ting expansion and is not in use at present.
carrierSelectRouting OC 0x9F 23 GraphicString This field is reserved for future
expansion and is not in use at present.
serviceSpecificInfo [1] OC 0xBF 64 SEQUENCE OF This field contains the data and type
of a special service. This field is set to
Empty for basic calls.
This field contains the following sub-
fields:
 serviceSpecificData
 serviceSpecificType
serviceSpecificData [2] OC 0x80 GraphicString This field specifies the special data
related to the service. It is a service-
specific field. It records the service
details used by a subscriber in a call. It
applies to the AS. The information
contained in this field is the original
calling party for the moment. Usually,
this field is set to Empty in basic
CDRs.
serviceSpecificType [2] OC 0x81 INTEGER This field contains the type of the
serviceSpecificData.
requested-Party- OC 0xBF 65 CHOICE This field specifies the number of a
Address [1] service subscriber. It is only valid
when the number of the called party
changes. It is in SIP URI or tel URI
format. Usually, this field is set to
Empty for basic calls. This field is
derived from Requested-Party-
Address in the MediaX CDRs.
sIP-URI [2] OC 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OC 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
list-Of-Called- OC 0xBF 66 SEQUENCE OF This field specifies the address of the
Asserted-Identity [1] final called party. In basic calls, this
field records the number of the
subscriber that answers the call. The
recorded number is carried to CCF
through the Called-Asserted-Identity
FIELD by the MediaX3600in ACRs.
sIP-URI [2] OC 0x80 GraphicString This field is in SIP URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 95

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

tEL-URI [2] OC 0x81 GraphicString This field is in tel URI format.

alternateChargedParty OC 0x9F 67 UTF8String This field is reserved for future
Address expansion and is not in use at present.
privateUserID OM 0x88 GraphicString This field specifies the used network
access ID of the served party
according to the RFC2486 [405].
duration OC 0x9F 81 48 INTEGER This field specifies the call duration in
a SIP session.
bill-type OC 0x9F 82 22 ENUMERATED This field specifies the service type.
For details, see section 4.25 "bill-
type"
mediax-conference- OC 0xBF 82 23 SET This field specifies the conference
information [1] information.
meeting-id [2] OC 0x80 UTF8String This field specifies the conference ID.
access-phone [2] OC 0x81 UTF8String This field specifies the access code.
meeting-frequency [2] OC 0x82 ENUMERATED This field specifies the type of the
conference frequency.
meeting-mode [2] OC 0x83 ENUMERATED This field specifies the conference
mode.
Service-Mode [2] OC 0x84 ENUMERATED This field specifies the service mode.
For details, see section 4.184 "service-
mode."
order-start-time [2] OC 0x85 OCTET STRING This field specifies the start time of a
(SIZE(9)) scheduled conference.
order-end-time [2] OC 0x86 OCTET STRING This field specifies the end time of a
(SIZE(9)) scheduled conference.
order-party [2] OC 0x87 INTEGER This field specifies the number of
parties in a scheduled conference.
media-type [2] OC 0x88 INTEGER This field specifies the media type.
modified-start-time [2] OC 0x89 OCTET STRING This field specifies the start time of a
(SIZE(9)) modified conference.
modified-end-time [2] OC 0x8A OCTET STRING This field specifies the end time of a
(SIZE(9)) modified conference.
modified-party [2] OC 0x8B INTEGER This field specifies the number of
parties in a modified conference.
operation-time [2] OC 0x8C OCTET STRING This field specifies the operation
(SIZE(9)) duration.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 96

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

multiPic-Resource [2] OC 0x8D INTEGER This field specifies the resources used
by a multi-picture conference. If the
conference is not a multi-picture one,
the value of this field is 0.
adapter-Resource [2] OC 0x8E INTEGER This field specifies the adapter
resource occupied by a conference. It
is used only when the scheduled
conference needs to be adapted.
bandwidth-Resource OC 0x8F INTEGER This field specifies the bandwidth
[2]
resource occupied by a video
conference. You need this field when
scheduling a video conference.
videoPort-Resource [2] OC 0x90 INTEGER This field specifies the video port used
by a conference.
audioPort-Resource [2] OC 0x91 INTEGER This field specifies the audio port used
by a conference.
modified-MultiPic- OC 0x92 INTEGER This field specifies the resource
Resource [2] occupied by a modified multi-picture
conference.
modified-Adapter- OC 0x93 INTEGER This field specifies the adapter
Resource [2] resource occupied by a modified
conference.
modified-Bandwidth- OC 0x94 INTEGER This field specifies the bandwidth
Resource [2] resource occupied by a modified
conference.
modified-VideoPort- OC 0x95 INTEGER This field specifies the video port used
Resource [2] by a modified conference.
modified-AudioPort- OC 0x96 INTEGER This field specifies the audio port used
Resource [2] by a modified conference.
telepresence-party [2] OC 0x97 INTEGER This field specifies the number of the
Telepresence conference sites in a
conference.
modified- OC 0x98 INTEGER This field specifies the number of
telepresence-party [2] parties in a modified telepresence
conference.
created-time [2] OC 0x99 OCTET STRING This field specifies the time when a
(SIZE(9)) conference is created.
closed-time [2] OC 0x9A OCTET STRING This field specifies the time when a
(SIZE(9)) conference is ended.
closed-code [2] OC 0x9B ENUMERATED This field specifies the cause of
ending a conference.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 97

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

current-party [2] OC 0x9C INTEGER This field specifies the number of

participants in the current voice or
video conference, excluding the
participants in the telepresence
conference and data conference.
current-data-party [2] OC 0x9D INTEGER This field specifies the number of
participants in the current data
conference.
current-telepresence- OC 0x9E INTEGER This field specifies the number of
party [2] participants in the current telepresence
conference.
sub-meetingID [2] OC 0x9F 1F UTF8String This field specifies the ID of a sub-
conference. The original conference
ID attribute specifies the ID of the
main conference in cascaded
conferences.
up-CascadePorts [2] OC 0x9F 20 INTEGER This field specifies the number of up-
cascade ports in a cascaded-
conference CDR.
modified-Up- OC 0x9F 21 INTEGER This field specifies the number of
CascadePorts [2] modified up-cascade ports.
down-CascadePorts [2] OC 0x9F 22 INTEGER This field specifies the number of
down-cascade ports in a cascaded-
conference CDR.
modified-Down- OC 0x9F 23 INTEGER This field specifies the number of
CascadePorts [2] modified down-cascade ports.
OC 0x9F 24 INTEGER This field specifies the conference
control mode.
sMS-Notify-Type[2]
For details, see section 4.203 SMS-
Notify-Type.
OC 0x9F 25 INTEGER This field specifies how many short
[2] messages a long message is divided
sMS-Notify-Amount
into so that the mobile network can
send these short messages.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 98

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

OC 0x9F 26 INTEGER This field specifies the number of

recording resource channels required
when a conference is scheduled. This
field is independently of the media
type. To record a voice or SD video
conference, one voice recording
resource channel is required; to record
recording-Resource[2]
a unidirectional HD video or
telepresence video conference, one
HD recording resource channel is
requird; to record a bidirectional HD
video or telepresence video
conference, two HD recording
resource channels are required.
OC 0x9F 27 INTEGER This field specifies the number of
recording resource channels required
modified-Recording-
when a conference is modified. This
Resource[2]
field is independently of the media
type.
OC 0x9F 28 INTEGER This field indicates the media
encyption mode in a conference.
mediaEncrypt-Mode[2] AUTO_ENCRYPT 0
MUST_ENCRYPT 1
NO_ENCRYPT 2
OC 0x9F 29 INTEGER This field indicates the media
encyption mode in a modified
conference.
modified-
MediaEncrypt-Mode[2] AUTO_ENCRYPT 0
MUST_ENCRYPT 1
NO_ENCRYPT 2
OC 0x9F2A UTF8String This field specifies the ID of a main-
main-Meeting-ID [2]
conference.
modified-Media- Oc 0x9F 2B INTEGER This field specifies the modified
Type[2] media type.
mediax-user- OC 0xBF 82 24 SET This field carries the user information
information [1] in media interaction.
pay-account [2] OC 0x80 UTF8String This field specifies the payment
account.
organization-id [2] OC 0x81 UTF8String This field specifies the ID of an
organization (the unique ID of an
enterprise or a department).
user-id [2] OC 0x82 UTF8String This field specifies the user ID.
call-id [2] OC 0x83 UTF8String This field specifies the conference ID.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 99

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

port-type [2] OC 0x84 ENUMERATED This field specifies the port type.
end-code [2] OC 0x85 ENUMERATED This field specifies the end code.
group-id [2] OC 0x86 UTF8String This field specifies the group ID. It is
used in the Group call service.
user-Category [2] OC 0x92 ENUMERATED This field specifies the user category.
USER-UC 1 //UC user
USER-M-MEETING 2 //M-
meeting user
USER-ROOM 3 //room user
USER-UNDEFINED 256
//undefined user

list-Of-Logic- OC 0xB3 SEQUENCE OF This group field consists of the

Resource[2] following fields:
port-Media-Type
port-Count
port-Media-Type[3] OC 0x94 ENUMERATED This field specifies the port media
type.
PORT-AUDIO 1 //audio port
PORT-SD-VIDEO 2 //SD video
port
PORT-HD-VIDEO-2M 3 //HD
video port 2Mbps(720p)
PORT-HD-VIDEO-4M 4 // HD
video port 4Mbps(1080p)
port-Count [3] OC 0x95 INTEGER This field specifies the port count.
Qos-Statistics [2] OC 0x87 UTF8String This field is optional. It specifies the
media plane statistical information in
a BYE or 200 (to BYE) message.
mediax-terminal- OC 0xBF 83 11 SET This field specifies the information of
information [1] relevant access terminal in the
charging data.
terminal-type [2] OC 0x80 ENUMERATED This field specifies the terminal type.
screen-number [2] OC 0x81 INTEGER This field specifies the number of
screens. It includes single screen,
three screens and so on.
main-screen [2] OC 0x82 UTF8String This field specifies the number of the
main screen.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 100

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

main-screen- OC 0x83 INTEGER This field specifies the mode by which

Entrance-Type [2] the main screen joins a conference. It
includes dialing a specific number,
being invited and others.
mediaX-Online- OC 0x9F8312 ENUMERATED This field specifies whether online
Charging-Flag charging is performed. When the
subscriber is an offline subscriber, the
system sets this parameter to 0. When
the subscriber is an online subscriber,
the system sets this parameter to 1. If
an error occurs during online
charging, the system sets this
parameter to 2.
Offline_Charging 0
Online_Charging 1
Abnormal_Online_Service 2
mediaX-Online- OC 0x9F8313 INTEGER This field specifies the duration for
Charging-Duration which online charging lasts. The
system sets this field only when the
charging object is a prepaid
subscriber.
mediaX-OCS-Failed- OC 0x9F8314 OCTET STRING This field specifies the time when an
TimeStamp (SIZE(9)) error occurs during online charging.

This field carries the appliation

applicationId OC 0x9F8315 UTF8String identifier assigned by the application
developer.
ringing-Duration OC 0x9F 81 4C INTEGER This field specifies the ringing
duration.

3.6 MGCF CDR

The tag value in the MGCF CDR is 0xBF 43.

Table 3-1 Format of MGCF CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

CDR, indicating which NE
generated the CDR.
retransmission OC 0x81 NULL This field specifies whether the
ACRs from the MGCF are sent
repeatedly.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 101

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sIP-Method OC 0x82 GraphicString This field specifies the reason why

the MGCF generates charging
CDRs. The value of this field is from
the value of the sub field sIP-Method
in event-Type AV. It is used to
record the reason why a CDR is
generated, that is, the CDR type
generated by the MGCF. Normally,
the value is a start CDR (INVITE),
end CDR (BYE), and so on. The
value in a CDR is the last MGCF
CDR value received if a session ends
properly, the value of this field is
BYE.
role-of-Node OM 0x83 INTEGER This field specifies a session. It can
be Call ID carried in a SIP message.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ME that
provides the charging messages. It
can be an IP address or a valid
domain name of the ME providing
charging data. This field is derived
from Origin-Host in the MGCF
CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the session ID.
For a SIP session, the session ID
contains the SIP call ID as defined in
the SIP RFC3261 [404].
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field contains the number
Address [1] information about the calling party.
It can be in SIP URI format or tel
URI format. This field contains
multiple values in a CDR. This field
is derived from Calling-Party-
Address in the MGCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 102

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

called-Party-Address OM 0xA7 CHOICE This field specifies the number

[1]
information about the called party. It
can be in SIP URI format or tel URI
format. This field is derived from
Called-Party-Address in the
MGCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when a
imeStamp (SIZE(9)) peer NE receives a response after the
peer NE initiates a session request.
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE initiates a request to end a
session.
recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation starts. This
field shows the time when the CCF
receives the first ACR in a session.
At present, it is present only in the
cases related to SIP sessions.
recordClosureTime OM 0x8D OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation ends. This
field shows the time when the CCF
receives the last ACR in a session.
interOperatorIdentifie OC 0xAE SEQUENCE OF This field specifies the identities of
rs [1] the pair of an originating network
and a terminating network in SIP
signaling transmission.
This field contains the following
sub-fields:
 originatingIOI
 terminatingIOI
originatingIOI [2] OC 0x80 GraphicString This field identifies the network that
serves the calling party.
terminatingIOI [2] OC 0x81 GraphicString This field identifies the network that
serves the called party.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 103

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN

Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.
recordSequenceNumb OC 0x90 INTEGER This field is filled only when
er incomplete CDRs are to be
generated.
In the case of timeout or other cases,
the CCF may generate multiple
partial CDRs for the same charging
session. In that case, the CCF
allocates a record SN (starting with
1) to each partial CDR.
It helps the BS check whether a
CDR is complete.
causeForRecordClosi OC 0x91 ENUMERATED This field specifies the reason why a
ng session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field provides additional
Indication [1] diagnostics when the CCF finds that
charging data is missing.
It contains the following three sub-
fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
This field shows whether the CDR
content is complete. If the CDR
misses a partial ACR, the CCF fills
in the following fields:
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 104

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on

the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
iMS-Charging- OM 0x93 OCTET STRING This field is assigned by the
Identifier accessed first ME in the IMS domain
and sent to all MEs in the IMS
domain. It is unique in an end-to-end
session. This field is also called
ICID for short. If the first ME does
not generate an ICID, the MGCF
generates an ICID. The value of this
field is sent to the CCF by the
MGCF through the iMS-Charging-
Identifier field.
list-Of-sDP-Media- OC 0xB5 SEQUENCE OF A field of the group type.
Components [1] It contains several sub-fields
associated with one media
component. This field is present in
only one SIP session and may appear
several times in one CDR because
one CDR may contain multiple
sessions.
It describes the details about media
changes in an E2E session. For
example, calling party A starts voice
communications with called party B
at 9:00 am. Then, A and B change
the communication way into video at
9:30 a.m. The initiator of the video
communications can be A or B.
This field is essential to the CCF and
the BS.
This field contains the following
sub-fields:
 sDP-Session-Description
 SIP-Request-Timestamp
 SIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
sIP-Request- OM 0x80 OCTET STRING This field specifies the time when a
Timestamp [2] (SIZE(9)) SIP request is initiated.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 105

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sIP-Response- OM 0x81 OCTET STRING This field specifies the time when
Timestamp [2] (SIZE(9)) the response to the SIP request is
sent.
sDP-Media- OM 0xA2 SEQUENCE OF A field of the group type.
Components [2] It contains several sub-fields
associated with one media
component. Because several media
components may exist for a session
in parallel, these sub-fields may
appear several times.
This field contains the following
sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id
sDP-Media-Name [3] OM 0x80 GraphicString This field specifies the media name.
It contains the information indicated
by the line m= in the SDP
information.
sDP-Media- OM 0xA1 SEQUENCE OF This field specifies the session
Descriptions [3] description, including the IP address
that provides media support.
gPRS-Charging-Id [3] OM 0x82 INTEGER This field specifies the ID of the
GGSN that provides bearer at the
bearer layer (PS domain), namely,
GCID. It is implemented by
converting the numeric string into
integers. If the PS domain bearer
changes, the IMS domain is notified
of the field. The BS then uses the
ICID and GCID to associate with
CDRs.
accessNetworkChargi OM 0x84 GraphicString This field specifies the access
ngIdentifier [3] network charging ID.
authorized-QoS [3] OC 0x83 GraphicString This field authorizes the QoS for
end-to-end services.
mediaInitiatorFlag [2] OC 0x83 NULL This field specifies whether the
media initiated by the called party
changes.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 106

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sDP-Session- OC 0xA4 SEQUENCE OF This field specifies the session

Description [2] portion of the SDP data exchanged
between user agents in the SIP
transaction.
This field is the attribute line (i=, c=,
b=, k=, a=, ...) in an SDP message
and used to describe a session.
mediaInitiatorParty [2] OC 0xA5 CHOICE It is reserved for future expansion
and is not in use at present.
sIP-Request- OC 0x86 Unsigned32 This field specifies the SIP request
Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the SIP-Request-
Timestamp field.
sIP-Response- OC 0x87 Unsigned32 This field specifies the SIP response
Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the SIP-Response-
Timestamp field.
serviceReasonReturn OC 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails.
It is displayed as
serviceDeliveryFailureReason in
the R5 version and
serviceReasonReturnCode in the
R6 version.
recordExtensions OC 0xB9 SET OF This field is reserved for future
expansion and is not in use at
present.
expiresInformation OC 0x9A INTEGER This field is reserved for future
expansion and is not in use at
present.
event OC 0x9C UTF8String This field is reserved for future
expansion and is not in use at
present.
accessNetworkInform OC 0x9D OCTET STRING This field contains detailed access
ation technologies, such as protocols in
use and versions. For example:
3GPP-UTRAN-TDD; utran-cell-id-
3gpp=234151D0FCE11. This field
is in the P-
accessNetworkInformation header
field of a SIP message. Information
in this field is sent to CCF through
accessNetworkInformation field of
MGCF ACR.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 107

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceContextID OC 0x9E UTF8String This field is reserved for future

expansion and is not in use at
present.
list-Of-Early-sDP- OC 0xBF 20 SEQUENCE OF This field is reserved for future
Media-Components expansion and is not in use at
present.
numberPortabilityRou OC 0x9F 22 GraphicString This field is reserved for future
ting expansion and is not in use at
present.
carrierSelectRouting OC 0x9F 23 GraphicString This field is reserved for future
expansion and is not in use at
present.
trunkGroupID(Incomi OC 0xBF 50 CHOICE This field specifies the outgoing
ng/Outgoing) trunk or incoming trunk obtained
from the ACR. For an originating-
party CDR, if the outgoing trunk of
its corresponding ACR is available,
the value of this field is the outgoing
trunk; otherwise, the value is the
incoming trunk. For a terminating-
party CDR, if the incoming trunk of
its corresponding ACR is available,
the value of this field is the
incoming trunk; otherwise, the value
is the outgoing trunk.
bearerService OC 0xBF 51 SEQUENCE Bearer-Service is a sub-field of the
IMS-Information field and is used to
describe the bearer services used by
the PSTN to communicate with the
IMS network.
privateUserID OM 0x88 GraphicString This field is reserved for future
expansion and is not in use at
present.
gGSNaddress OC 0xB6 CHOICE This field is reserved for future
expansion and is not in use at
present.
list-Of-Message- OC 0xB8 SEQUENCE OF This field is reserved for future
Bodies [1] expansion and is not in use at
present.
duration OC 0x9F 81 48 INTEGER This field specifies the call duration
in a SIP session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 108

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

nP-Query Oc 0xBF 86 21 Enumerated The field has the following means:

 When the value of the field is 0, it
specifies the user calls other user
with not NP query.
 When the value of the field is 1, it
specifies the user calls other user
with NP query.
additional-Calling- Oc 0x9F 81 7C UTF8String This field holds information about
Party-Address the additional calling number (tel
URI). In Number-Portability feature,
the field holds the calling subscriber
physical number. It is obtained from
the P-Additional-Calling-Party
header of INVITE message.
abnormal-Finish-Info OC 0xBF 81 4F SEQUENCE This field contains the reason why a
[1]
session or an event is ended
abnormally.
The reason is carried in a BYE
message or other SIP messages.
It used only in Number-Portability
feature when MGCF received a 410
message.
This field contains the following
sub-fields:
 AbnormalFinishWarning
 abnormalFinishReason
abnormalFinishWarni OC 0x80 GraphicString This field is reserved for future
ng [2] expansion and is not in use at
present.
abnormalFinishReaso OC 0x81 GraphicString This field specifies the content of
n [2] Abnormal Finish Reason contains
cause. The cause value is contained
in the Reason header field of the SIP
message. A character string should
contain cause.
In Number-Portability feature when
MGCF received 410 message, the
value is "Q.850; cause=14".
session-Priority OC 0x9F 81 4D INTEGER This field is the ID of an urgent call.
nP-Data [1] OC 0xBF 81 50 SET This field contains data information.
location-routing- OC 0x80 UTF8String This field contains the called route
number [2] number.
lrn-source-indicator [2] OC 0x81 INTEGER This field contains the LRN src flag.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 109

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

lrn-query-status [2] OC 0x82 INTEGER This field contains the LRN query
state.
chargingCategory OC 0x9F 81 58 ENUMERATED This field contains the following
user charging type:
 0: CHARGE-NORMAL
 1: CHARGE-FREE
 2: CHARGE-PREPAID
 3: CHARGE-CALLED
call-property OC 0x9F 81 5E INTEGER This field specifies whether this call
is a local call, national toll call, or
international toll call.
charged-party [1] Oc 0xBF 81 1C CHOICE Field for China Mobile.
This field specifies a charged party.
This value is the IMPU of the
current charged party. It can be in
SIP URI or tel URI format. This
field is derived from Charged-Party
in the IBCF CDRs.
sIP-URI [2] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [2] OC 0x81 GraphicString This field is in tel URI format.
serviceRequestTimeSt Oc 0x9F 25 INTEGER This field set to the value (in
ampFraction (0..999) millisecond) of the field
serviceRequestTimeStamp.
serviceDeliveryStartT Oc 0x9F 26 INTEGER This field set to the value (in
imeStampFraction (0..999) millisecond) of the field
serviceDeliveryStartTimeStamp.
serviceDeliveryEndTi Oc 0x9F 27 INTEGER This field set to the value (in
meStampFraction (0..999) millisecond) of the field
serviceDeliveryEndTimeStamp.
ims-3gpp-Session- OC 0x9F 24 INTEGER The field contains the priority of the
Priority session.
ringing-Duration OC 0x9F 81 4C INTEGER This field specifies the ringing
duration.

3.7 IBCF CDR

The tag value in the IBCF CDR is 0xBF 52.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 110

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Table 3-1 Format of IBCF CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

CDR, indicating which NE
generated the CDR.
retransmission OC 0x81 NULL This field specifies whether the
ACRs from the IBCF are sent
repeatedly.
sIP-Method OC 0x82 GraphicString This field specifies the reason why
ACRs are generated. This field is
only available in unrelated sessions.
role-of-Node OM 0x83 INTEGER This field specifies the role of the
IBCF NE in a session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ME that
provides the charging messages. It
can be an IP address or a valid
domain name of the ME providing
charging data. This field is derived
from Origin-Host in the IBCF
CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies a session. It can
be Call ID carried in a SIP message.
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field specifies the number
Address [1] information about the calling party.
It can be in SIP URI format or tel
URI format. This field contains
multiple values in a CDR. This field
is derived from Calling-Party-
Address in the IBCF CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
called-Party-Address OM 0xA7 CHOICE This field specifies the number
[1]
information about the called party. It
can be in SIP URI format or tel URI
format. This field is derived from
Called-Party-Address in the IBCF
CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 111

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when a
imeStamp (SIZE(9)) peer NE receives a response after the
peer NE initiates a session request.
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE initiates a request to end a
session.
recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation starts. This
field shows the time when the CCF
receives the first ACR in a session.
At present, it is present only in the
cases related to SIP sessions.
recordClosureTime OM 0x8D OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation ends. This
field shows the time when the CCF
receives the last ACR in a session.
interOperatorIdentifie OC 0xAE SEQUENCE OF This field specifies the identities of
rs [1] the pair of an originating network
and a terminating network in SIP
signaling transmission.
This field contains the following
sub-fields:
 originatingIOI
 terminatingIOI
originatingIOI [2] OC 0x80 GraphicString This field identifies the network that
serves the calling party.
terminatingIOI [2] OC 0x81 GraphicString This field identifies the network that
serves the called party.
localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN
Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 112

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordSequenceNumb OC 0x90 INTEGER This field is filled only when

er incomplete CDRs are to be
generated.
In the case of timeout or other cases,
the CCF may generate multiple
partial CDRs for the same charging
session. In that case, the CCF
allocates a record SN (starting with
1) to each partial CDR.
It helps the BS check whether a
CDR is complete.
causeForRecordClosi OC 0x91 ENUMERATED This field specifies the reason why a
ng session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field provides additional
Indication [1] diagnostics when the CCF finds that
charging data is missing.
It contains the following three sub-
fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
This field shows whether the CDR
content is complete. If the CDR
misses a partial ACR, the CCF fills
in the following fields:
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 113

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

iMS-Charging- OM 0x93 OCTET STRING This field is assigned by the first

Identifier accessed ME in the IMS domain and
sent to all MEs in the IMS domain.
It is unique in an end-to-end session.
This field is also called ICID for
short.
list-Of-sDP-Media- OC 0xB5 SEQUENCE OF A field of the group type.
Components [1] It contains several sub-fields
associated with one media
component. This field is present in
only one SIP session and may appear
several times in one CDR because
one CDR may contain multiple
sessions.
It describes the details about media
changes in an E2E session. For
example, calling party A starts voice
communications with called party B
at 9:00 am. Then, A and B change
the communication way into video at
9:30 a.m. The initiator of the video
communications can be A or B.
This field is essential to the CCF and
the BS.
This field contains the following
sub-fields:
 sDP-Session-Description
 sIP-Request-Timestamp
 sIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
sIP-Request- OC 0x80 OCTET STRING This field specifies when the SIP
Timestamp [2] (SIZE(9)) Request is initiated.
sIP-Response- OC 0x81 OCTET STRING This field specifies the time when
Timestamp [2] (SIZE(9)) the response to the SIP request is
sent.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 114

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sDP-Media- OC 0xA2 SEQUENCE OF A field of the group type.

Components [2] It contains several sub-fields
associated with one media
component. Because several media
components may exist for a session
in parallel, these sub-fields may
appear several times.
This field contains the following
sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id
sDP-Media-Name [3] OC 0x80 GraphicString This field specifies the name of a
session and the relevant protocol.
sDP-Media- OC 0xA1 SEQUENCE OF This field specifies the session
Descriptions [3] description, including the IP address
that provides media support.
gPRS-Charging-Id [3] OC 0x82 INTEGER This field is reserved for future
expansion and is not in use at
present.
accessNetworkChargi OC 0x84 GraphicString This field is reserved for future
ngIdentifier [3] expansion and is not in use at
present.
authorized-QoS [3] OC 0x83 GraphicString This field is reserved for future
expansion and is not in use at
present.
mediaInitiatorFlag [2] OC 0x83 NULL This field specifies whether the
media initiated by the called party
changes.
sDP-Session- OC 0xA4 SEQUENCE OF This field specifies the session
Description [2] portion of the SDP data exchanged
between user agents in the SIP
transaction.
This field is the attribute line (i=, c=,
b=, k=, a=, ...) in an SDP message
and used to describe a session.
mediaInitiatorParty [2] OC 0xA5 CHOICE This field is reserved for future
expansion and is not in use at
present.
sIP-Request- OC 0x86 Unsigned32 This field specifies the SIP request
Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the field SIP-
Request-Timestamp.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 115

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sIP-Response- OC 0x87 Unsigned32 This field specifies the SIP response

Timestamp-Fraction [2] fraction time. It is set to the value (in
millisecond) of the SIP-Response-
Timestamp field.
serviceReasonReturn OC 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails.
It is displayed as
serviceDeliveryFailureReason in
the R5 version and
serviceReasonReturnCode in the
R6 version.
recordExtensions OC 0xB9 SET OF This field is reserved for future
expansion and is not in use at
present.
expiresInformation OC 0x9A INTEGER "Expires" from SIP Message.
event OC 0x9C UTF8String This field specifies the content of the
event header.
serviceContextID OC 0x9E UTF8String This field specifies the specific
services in a session.
list-Of-Early-sDP- OC 0xBF 20 SEQUENCE OF This field is reserved for future
Media-Components expansion and is not in use at
present.
iMSCommunicationS OC 0x9F 21 OCTET STRING This field is reserved for future
erviceIdentifier expansion and is not in use at
present.
numberPortabilityRou OC 0x9F 22 GraphicString This field is reserved for future
ting expansion and is not in use at
present.
carrierSelectRouting OC 0x9F 23 GraphicString This field is reserved for future
expansion and is not in use at
present.
ims-3gpp-Session- OC 0x9F 24 INTEGER The field contains the priority of the
Priority session.
privateUserID OM 0x88 GraphicString This field specifies the used network
access ID of the served party
according to the RFC2486 [405].

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 116

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-Message- OC 0xB8 SEQUENCE OF A field of the group type.

Bodies [1] It contains several sub-fields
describing the SIP messages
transmitted between the IMS NEs.
Because SIP signaling may be
exchanged among several messages,
the field may appear several times.
This field contains the following
sub-fields:
 content-Type
 content-Disposition
 content-Length
 originator
content-Type [2] OC 0x80 GraphicString This field specifies the media type of
a SIP message, such as
application/zip, image/gif, or
audio/mpeg.
content-Disposition [2] OC 0x81 GraphicString This field specifies the way in which
a SIP message is deployed.
content-Length [2] OC 0x82 INTEGER This field specifies the length of a
SIP message.
originator [2] OC 0xA3 CHOICE A sub-field of list-Of-Message-
Bodies. This field specifies the ID of
the originating party of the message
body. This field is derived from
originator in the IBCF CDRs.
sIP-URI [3] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field is in tel URI format.
accessNetworkInform OC 0x9D OCTET STRING This field specifies the details about
ation special access technologies.
list-of-subscription-ID OC 0xBF 1F SEQUENCE OF This field records the IDs of the
[1]
subscriptions of the services.
subscriptionIDType [2] OC 0x80 ENUMERATED This field specifies the type of the
subscription ID.
The types are represented as follows:
 eND-USER-E164 (0)
 eND-USER-IMSI (1)
 eND-USER-SIPURI (2)
 eND-USER-NAI (3)
 eND-USER-PRIVATE (4)

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 117

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

subscriptionIDData [2] OC 0x81 UTF8String This field specifies the ID of the

subscription of a specific service.
The value is the URI of the calling
party, called party, or connection
party.
servedPartyIPAddress OC 0xBF 32 IPAddress This field specifies the IP address of
the called party or the calling party.
The IBCF uses it to keep in touch
with the called party or calling party.
duration OC 0x9F 81 48 INTEGER This field specifies the call duration
in a SIP session.
ringing-Duration OC 0x9F 81 4C INTEGER This field specifies the ringing
duration (between 180 and 200).
session-Priority OC 0x9F 81 4D INTEGER This field is the ID of an urgent call.
carrier-Identification- OC 0x9F 81 4E UTF8String This field specifies the code of
Code carriers to be selected.
abnormal-Finish- OC 0xBF 81 4F SEQUENCE This field contains the reason why a
Info[1] session or an event is ended
abnormally. The reason is carried in
a BYE message or other SIP
messages.
abnormalFinishWarni OC 0x80 GraphicString This field contains the warning code
ng [2] and text in the Warning header field
of a SIP message (a character string
contains two parts).
abnormalFinishReaso OC 0x81 GraphicString This field contains the cause and text
n [2] in the Reason header field of a SIP
message (a character string contains
two parts).
nP-Data [1] OC 0xBF 81 50 SET This field contains data information.
location-routing-numb OC 0x80 UTF8String This field contains the routing
er [2] number of the called party.
lrn-source-indicator [2] OC 0x81 INTEGER This field contains the source of the
LRN.
lrn-query-status [2] OC 0x82 INTEGER This field contains the query status
of the LRN.
refer-To OC 0x9F 81 51 UTF8String This field contains the refer-To
header field in a SIP session.
target OC 0x9F 81 52 UTF8String This field contains the target header
field in a SIP session.
np-Route-Number OC 0x9F 81 53 OCTET STRING This field specifies the number of a
router.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 118

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordExtensions-1 OC 0xBF 81 71 SET OF This field is reserved for future

expansion and is not in use at
present.
recordExtensions-2 OC 0xBF 81 72 SET OF This field is reserved for future
expansion and is not in use at
present.
BCF- Trunk-Group- OC 0xBF 81 73 SEQUENCE This field is a group field containing
ID [1] two sub-fields: Incoming-Trunk-
Group-ID and Outgoing-Trunk-
Group-ID.
BCF-Incoming- OC 0x80 GraphicString This field specifies the incoming
Trunk-Group-ID [2] trunk group ID or name.
BCF-Outgoing- OC 0x81 GraphicString This field specifies the incoming
Trunk-Group-ID [2] trunk group ID or name.
serviceRequestTimeSt Oc 0x9F 25 INTEGER This field set to the value (in
ampFraction (0..999) millisecond) of the field
serviceRequestTimeStamp.
serviceDeliveryStartT Oc 0x9F 26 INTEGER This field set to the value (in
imeStampFraction (0..999) millisecond) of the field
serviceDeliveryStartTimeStamp.
serviceDeliveryEndTi Oc 0x9F 27 INTEGER This field set to the value (in
meStampFraction (0..999) millisecond) of the field
serviceDeliveryEndTimeStamp.

3.8 ALUCTS CDR

The tag value in the ALUCTS CDR is 0xBF 81 4B.

Table 3-1 Format of ALUCTS CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 119

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

role-of-Node OM 0x83 INTEGER This field specifies the role of the

ALUCTS in a session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ID of the NE
that provides CDRs. The value may
be either the IP address or the FQDN
of the NE that generates charging
information. This field is derived
from Origin-Host in the ALUCTS
CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the session ID.
For a SIP session, the session ID
contains the SIP call ID as defined in
the SIP RFC3261 [404].
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field specifies the number
Address [1] information about the calling party.
It can be in SIP URI format or tel
URI format. This field contains
multiple values in a CDR. This field
is derived from Calling-Party-
Address in the ALUCTS CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
called-Party-Address OM 0xA7 CHOICE This field specifies the address of
[1]
the receiver in an E2E SIP event.
For example, in the subscription or
registration procedure, called-Party-
Address is defined as the address of
the party who carries out the
subscription or registration. This
field contains the SIP URI or tel
URI. This field is derived from
Called-Party-Address in the
ALUCTS CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 120

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when a
imeStamp (SIZE(9)) peer NE receives a response after the
peer NE initiates a session request.
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE initiates a request to end a
session.
recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation starts. This
field shows the time when the CCF
receives the first ACR in a session.
At present, it is present only in the
cases related to SIP sessions.
recordClosureTime OM 0x8D OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation ends. This
field shows the time when the CCF
receives the last ACR in a session.
interOperatorIdentifie OC 0xAE SEQUENCE OF This field specifies the identities of
rs [1] the pair of an originating network
and a terminating network in SIP
signaling transmission.
This field contains the following
sub-fields:
 originatingIOI
 terminatingIOI
originatingIOI [2] OC 0x80 GraphicString This field specifies the ID of an
originating network.
terminatingIOI [2] OC 0x81 GraphicString This field specifies the ID of a
terminating network.
localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN
Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 121

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordSequenceNumb OC 0x90 INTEGER This field is filled only when

er incomplete CDRs are to be
generated.
In the case of timeout or other cases,
the CCF may generate multiple
partial CDRs for the same charging
session. In that case, the CCF
allocates a record SN (starting with
1) to each partial CDR.
It helps the BS check whether a
CDR is complete.
causeForRecordClosi OM 0x91 ENUMERATED This field specifies the reason why a
ng session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field provides additional
Indication [1] diagnostics when the CCF finds that
charging data is missing. This field
shows whether the CDR content is
complete. If the CDR misses a
partial ACR, the CCF fills in the
following fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
iMS-Charging- OM 0x93 OCTET STRING This field specifies the ICID.
Identifier The P-CSCF allocates the ICID and
notifies each NE in the IMS. The
ICID is unique in an E2E session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 122

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-sDP-Media- OC 0xB5 SEQUENCE OF A field of the group type.

Components [1] It contains several sub-fields
associated with one media
component. This field is present in
only one SIP session and may
appear several times in one CDR
because one CDR may contain
multiple sessions.
It describes the details about media
changes in an E2E session. For
example, calling party A starts voice
communications with called party B
at 9:00 am. Then, A and B change
the communication way into video at
9:30 a.m. The initiator of the video
communications can be A or B.
This field is essential to the CCF and
the BS.
This field contains the following
sub-fields:
 sDP-Session-Description
 SIP-Request-Timestamp
 SIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
sIP-Request- OM 0x80 OCTET STRING This field specifies when the SIP
Timestamp [2] (SIZE(9)) Request is initiated.
sIP-Response- OM 0x81 OCTET STRING This field specifies the time when
Timestamp [2] (SIZE(9)) the response to the SIP request is
sent.
sDP-Media- OM 0xA2 SEQUENCE OF A field of the group type.
Components [2] It contains several sub-fields
associated with one media
component. Because several media
components may exist for a session
in parallel, these sub-fields may
appear several times.
This field contains the following
sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id
sDP-Media-Name [3] OM 0x80 GraphicString This field specifies the name of a
session and the relevant protocol.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 123

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sDP-Media- OM 0xA1 SEQUENCE OF This field specifies the session

Descriptions [3] description, including the IP address
that provides media support.
gPRS-Charging-Id [3] OM 0x82 INTEGER This field specifies the ID of the
GGSN that provides bearer at the
bearer layer (PS domain), namely,
GCID. It is implemented by
converting the numeric string into
integers. If the PS domain bearer
changes, the IMS domain is notified
of the field. The BS then uses the
ICID and GCID to associate with
CDRs.
This field is reserved for future
expansion and is not in use at
present.
accessNetworkChargi OM 0x84 GraphicString This field is reserved for future
ngIdentifier [3] expansion and is not in use at
present.
authorized-QoS [3] OC 0x83 GraphicString This field is reserved for future
expansion and is not in use at
present.
mediaInitiatorFlag [2] OC 0x83 NULL This field specifies whether the
media initiated by the called party
changes.
sDP-Session- OC 0xA4 SEQUENCE OF This field specifies the session
Description [2] portion of the SDP data exchanged
between user agents in the SIP
transaction.
This field is the attribute line (i=, c=,
b=, k=, a=, ...) in an SDP message
and used to describe a session.
mediaInitiatorParty [2] OC 0xA5 CHOICE This field is reserved for future
expansion and is not in use at
present.
gGSNaddress OC 0xB6 CHOICE This field is reserved for future
expansion and is not in use at
present.
serviceReasonReturn OC 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails.
It is displayed as
serviceDeliveryFailureReason in
the R5 version and
serviceReasonReturnCode in the
R6 version.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 124

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-Message- OC 0xB8 SEQUENCE OF A field of the group type.

Bodies [1] It contains several sub-fields
describing the SIP messages
transmitted between the IMS NEs.
Because SIP signaling may be
exchanged among several messages,
the field may appear several times.
This field contains the following
sub-fields:
 content-Type
 content-Disposition
 content-Length
 originator
content-Type [2] OC 0x80 GraphicString This field specifies the media type of
a SIP message, such as
application/zip, image/gif, or
audio/mpeg.
content-Disposition [2] OC 0x81 GraphicString This field specifies the way in which
a SIP message is deployed.
content-Length [2] OC 0x82 INTEGER This field specifies the length of a
SIP message.
originator [2] OC 0xA3 CHOICE A sub-field of list-Of-Message-
Bodies. This field specifies the ID of
the originating party of the message
body. This field is derived from
originator in the ALUCTS CDRs.
sIP-URI [3] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field is in tel URI format.
recordExtensions OC 0xB9 SET OF This field is reserved for future
expansion and is not in use at
present.
expiresInformation OC 0x9A INTEGER This field is reserved for future
expansion and is not in use at
present.
event OC 0x9C UTF8String This field specifies the content of the
event header.
accessNetworkInform OC 0x9D OCTET STRING This field specifies the details about
ation special access technologies.
serviceContextID OC 0x9E UTF8String This field specifies the specific
services in a session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 125

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-of-subscription-ID OC 0xBF 1F SEQUENCE OF This field records the IDs of the

[1]
subscriptions of the services.
This field is reserved for future
expansion and is not in use at
present.
subscriptionIDType [2] OC 0x80 ENUMERATED This field specifies the type of the
subscription ID.
The types are represented as follows:
 eND-USER-E164 (0)
 eND-USER-IMSI (1)
 eND-USER-SIPURI (2)
 eND-USER-NAI (3)
 eND-USER-PRIVATE (4)
subscriptionIDData [2] OC 0x81 UTF8String This field specifies the ID of the
subscription of a specific service.
The value is the URL of the calling
party, called party, or connection
party.
This field is reserved for future
expansion and is not in use at
present.
list-Of-Early-sDP- OC 0xBF 20 SEQUENCE OF This field is reserved for future
Media-Components expansion and is not in use at
present.
iMSCommunicationS OC 0xBF 21 OCTET STRING This field is reserved for future
erviceIdentifier expansion and is not in use at
present.
numberPortabilityRou OC 0x9F 22 GraphicString This field is reserved for future
ting expansion and is not in use at
present.
carrierSelectRouting OC 0x9F 23 GraphicString This field is reserved for future
expansion and is not in use at
present.
Service-Specific- OC 0xBF 64 SEQUENCE OF This field contains the data and type
Information [1] of a special service.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 126

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceSpecificData [2] OC 0x80 GraphicString This field specifies the special data
related to the service.
It is a service-specific field.
Poc-Information, Message-
Information, and Confrence-
Information of the Service and
Software Sector of Huawei can be
considered as such a field.
It records the service details used by
a subscriber in a call.
It applies to the AS.
serviceSpecificType [2] OC 0x81 INTEGER This field is reserved for future
expansion and is not in use at
present.
requested-Party- OC 0xBF 65 CHOICE This field specifies the address of
Address the original called party in a SIP
transaction. The value is in SIP URI
or tel URI format. This field is used
when the address of the original
called party is inconsistent with the
value of Called Party Address.
list-Of-Called- OC 0xBF 66 SEQUENCE OF This field specifies the address of
Asserted-Identity the final called party.
alternateChargedParty OC 0x9F 67 UTF8String This field is reserved for future
Address expansion and is not in use at
present.
duration OC 0x9F 81 48 INTEGER This field specifies the call duration
in a SIP session.
supplementary- OC 0xBF 82 18 SEQUENCE OF This field is a group field. It records
Service-Info[1] the information about each session
of the ALU supplementary service.
service-type [2] OC 0x80 ENUMERATED This field specifies the service-type
type.
When the value of service type
ranges from 1 to 20, the encoding is
performed.
action [2] OC 0x81 ENUMERATED The values are as follows:
 1: activation
 2: deactivation
 3: interrogation
 4: cancellation

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 127

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

service-Mode [2] OC 0x82 ENUMERATED This field describes the CFU type of
the supplementary service.
When the value of service type
ranges from 1 to 24, the encoding is
performed.
serviceId [2] OC 0x83 UTF8String This field specifies the service ID.
associated-Number [2] OC 0x84 UTF8String This field specifies the associated
number in the service.
start-Time [2] OC 0x85 UTF8String This field specifies the session start
time.
stop-Time [2] OC 0x86 UTF8String This field specifies the session end
time.
name-Space [2] OC 0x87 UTF8String This field specifies the MLPP name
space.
precedence-Level [2] OC 0x88 ENUMERATED This field describes the MLPP
priority. The values are as follows:
 0: none
 1: routine
 2: priority
 3: immediate
 4: flash
 5: flash-override
 6: flash-override-or
call-Direction OC 0x9F 82 19 ENUMERATED This field specifies the receiver
address of the call.
The values are as follows:
 0: origination
 1: termination
call-type OC 0x9F 82 1A ENUMERATED This field specifies the ALU-call-
type type. It specifies the type of the
call in each session.
When the value of service type
ranges from 1 to 29, the encoding is
performed.
mobile-id [1] OC 0xBF 82 1B SET This field specifies the mobile ID in
the supplementary service.
calling-IMSI [2] OC 0x80 UTF8String This field specifies the IMSI
information of the calling party.
calling-MIN [2] OC 0x81 UTF8String This field specifies the MIN
information of the calling party.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 128

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

called-IMSI [2] OC 0x82 UTF8String This field specifies the IMSI

information of the called party.
called-MIN [2] OC 0x83 UTF8String This field specifies the MIN
information of the called party.
ue-local-timezone- OC 0x9F 82 1C UTF8String This field specifies the time offset
offset information.
mAC-ID OC 0x9F 82 1D UTF8String This field specifies the ID of the
MAC address.
ain-information [1] OC 0xBF 82 1E SET This field specifies the AIN service
information in the ALU
supplementary service.
amaslpid [2] OC 0x80 UTF8String This field specifies the AIN service
information ID.

3.9 Centrex-AS CDR

The tag value in the Centrex-AS CDR is 0xBF 81 7E.

Table 3-1 Format of Centrex-AS CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

CDR, indicating which NE
generated the CDR.
retransmission OC 0x81 NULL This field specifies whether the
ACRs sent from the relay station
need to be retransmitted.
sIP-Method OC 0x82 GraphicString This field specifies the reason why
ACRs are generated. This field is
only available in unrelated sessions.
role-of-Node OM 0x83 INTEGER This field specifies the role of the
Centrex-AS in a session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ID of the NE
that provides CDRs. The value may
be either the IP address or the FQDN
of the NE that generates charging
information. This field is derived
from Origin-Host in the Centrex-AS
CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 129

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the session ID.
For a SIP session, the session ID
contains the SIP call ID as defined in
the SIP RFC3261 [404].
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field specifies the number
Address [1] information about the calling party.
It can be in SIP URI format or tel
URI format. This field contains
multiple values in a CDR. This field
is derived from Calling-Party-
Address in the Centrex-AS CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
called-Party-Address OM 0xA7 CHOICE This field specifies the address of the
[1]
receiver in an E2E SIP event.
For example, in the subscription or
registration procedure, called-Party-
Address is defined as the address of
the party who carries out the
subscription or registration. This
field contains the SIP URI or tel
URI. This field is derived from
Called-Party-Address in the
Centrex-AS CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when a
imeStamp (SIZE(9)) peer NE receives a response after the
peer NE initiates a session request.
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE initiates a request to end a
session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 130

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation starts. This
field shows the time when the CCF
receives the first ACR in a session.
At present, it is present only in the
cases related to SIP sessions.
recordClosureTime OM 0x8D OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation ends. This
field shows the time when the CCF
receives the last ACR in a session.
interOperatorIdentifie OC 0xAE SEQUENCE OF This field specifies the identities of
rs [1] the pair of an originating network
and a terminating network in SIP
signaling transmission.
This field contains the following
sub-fields:
 originatingIOI
 terminatingIOI
originatingIOI [2] OC 0x80 GraphicString This field specifies the ID of an
originating network.
terminatingIOI [2] OC 0x81 GraphicString This field specifies the ID of a
terminating network.
localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN
Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.
recordSequenceNumb OC 0x90 INTEGER This field is filled only when
er incomplete CDRs are to be
generated.
In the case of timeout or other cases,
the CCF may generate multiple
partial CDRs for the same charging
session. In that case, the CCF
allocates a record SN (starting with
1) to each partial CDR.
It helps the BS check whether a
CDR is complete.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 131

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

causeForRecordClosi OC 0x91 ENUMERATED This field specifies the reason why a

ng session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field provides additional
Indication [1] diagnostics when the CCF finds that
charging data is missing. This field
shows whether the CDR content is
complete. If the CDR misses a
partial ACR, the CCF fills in the
following fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
iMS-Charging- OM 0x93 OCTET STRING This field specifies the ICID.
Identifier The P-CSCF allocates the ICID and
notifies each NE in the IMS. The
ICID is unique in an E2E session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 132

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-sDP-Media- OC 0xB5 SEQUENCE OF A field of the group type.

Components [1] It contains several sub-fields
associated with one media
component. This field is present in
only one SIP session and may appear
several times in one CDR because
one CDR may contain multiple
sessions.
It describes the details about media
changes in an E2E session. For
example, calling party A starts voice
communications with called party B
at 9:00 am. Then, A and B change
the communication way into video at
9:30 a.m. The initiator of the video
communications can be A or B.
This field is essential to the CCF and
the BS.
This field contains the following
sub-fields:
 sDP-Session-Description
 SIP-Request-Timestamp
 SIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
sIP-Request- OC 0x80 OCTET STRING This field specifies when the SIP
Timestamp [2] (SIZE(9)) Request is initiated.
sIP-Response- OC 0x81 OCTET STRING This field specifies the time when
Timestamp [2] (SIZE(9)) the response to the SIP request is
sent.
sDP-Media- OC 0xA2 SEQUENCE OF A field of the group type.
Components [2] It contains several sub-fields
associated with one media
component. Because several media
components may exist for a session
in parallel, these sub-fields may
appear several times.
This field contains the following
sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id
sDP-Media-Name [3] OC 0x80 GraphicString This field specifies the name of a
session and the relevant protocol.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 133

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sDP-Media- OC 0xA1 SEQUENCE OF This field specifies the session

Descriptions [3] description, including the IP address
that provides media support.
gPRS-Charging-Id [3] OC 0x82 INTEGER This field specifies the ID of the
GGSN that provides bearer at the
bearer layer (PS domain), namely,
GCID. It is implemented by
converting the numeric string into
integers. If the PS domain bearer
changes, the IMS domain is notified
of the field. The BS then uses the
ICID and GCID to associate with
CDRs.
accessNetworkChargi OC 0x84 GraphicString This field is reserved for future
ngIdentifier [3] expansion and is not in use at
present.
authorized-QoS [3] OC 0x83 GraphicString This field is reserved for future
expansion and is not in use at
present.
mediaInitiatorFlag [2] OC 0x83 NULL This field specifies whether the
media initiated by the called party
changes.
sDP-Session- OC 0xA4 SEQUENCE OF This field specifies the session
Description [2] portion of the SDP data exchanged
between user agents in the SIP
transaction.
This field is the attribute line (i=, c=,
b=, k=, a=, ...) in an SDP message
and used to describe a session.
sDP-Type [2] OC 0x85 ENUMERATED Specifies whether the SDP data in a
session is an SDP request or answer.
The enumerated values are as
follows:
sDP-offer (0)
sDP-answer (1)
mediaInitiatorParty [2] OC 0xA5 CHOICE This field is reserved for future
expansion and is not in use at
present.
gGSNaddress OC 0xB6 CHOICE This field is reserved for future
expansion and is not in use at
present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 134

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceReasonReturn OC 0x97 UTF8String This field specifies the reason why a

Code service request succeeds or fails.
It is displayed as
serviceDeliveryFailureReason in
the R5 version and
serviceReasonReturnCode in the
R6 version.
list-Of-Message- OC 0xB8 SEQUENCE OF A field of the group type.
Bodies [1] It contains several sub-fields
describing the SIP messages
transmitted between the IMS NEs.
Because SIP signaling may be
exchanged among several messages,
the field may appear several times.
This field contains the following
sub-fields:
 content-Type
 content-Disposition
 content-Length
 originator
content-Type [2] OC 0x80 GraphicString This field specifies the media type of
a SIP message, such as
application/zip, image/gif, or
audio/mpeg.
content-Disposition [2] OC 0x81 GraphicString This field specifies the way in which
a SIP message is deployed.
content-Length [2] OC 0x82 INTEGER This field specifies the length of a
SIP message.
originator [2] OC 0xA3 CHOICE This field specifies the party that
provides the Answer during
mediation negotiation. The value can
be Calling Party or Called Party.
This field is derived from originator
in the Centrex-AS CDRs.
sIP-URI [3] OC 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [3] OC 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
recordExtensions OC 0xB9 SET OF This field is reserved for future
expansion and is not in use at
present.
expiresInformation OC 0x9A INTEGER This field is reserved for future
expansion and is not in use at
present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 135

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

event OC 0x9C UTF8String This field specifies the content of the

event header.
accessNetworkInform OC 0x9D OCTET STRING This field specifies the details about
ation special access technologies.
serviceContextID OC 0x9E UTF8String This field specifies the specific
services in a session.
list-of-subscription-ID OC 0xBF 1F SEQUENCE OF This field records the IDs of the
[1]
subscriptions of the services.
subscriptionIDType [2] OC 0x80 ENUMERATED This field specifies the type of the
subscription ID.
The types are represented as follows:
 eND-USER-E164 (0)
 eND-USER-IMSI (1)
 eND-USER-SIPURI (2)
 eND-USER-NAI (3)
 eND-USER-PRIVATE (4)
subscriptionIDData [2] OC 0x81 UTF8String This field specifies the ID of the
subscription of a specific service.
The value is the URI of the calling
party, called party, or connection
party.
list-Of-Early-sDP- OC 0xBF 20 SEQUENCE OF This field is reserved for future
Media-Components expansion and is not in use at
present.
iMSCommunicationS OC 0xBF 21 OCTET STRING This field is reserved for future
erviceIdentifier expansion and is not in use at
present.
numberPortabilityRou OC 0x9F 22 GraphicString This field is reserved for future
ting expansion and is not in use at
present.
carrierSelectRouting OC 0x9F 23 GraphicString This field is reserved for future
expansion and is not in use at
present.
serviceSpecificInfo [1] OC 0xBF 64 SEQUENCE OF This field contains the data and type
of a special service.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 136

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceSpecificData [2] OC 0x80 GraphicString This field specifies the special data
related to the service.
It is a service-specific field.
Poc-Information, Message-
Information, and Confrence-
Information of the Service and
Software Sector of Huawei can be
considered as such a field.
It records the service details used by
a subscriber in a call.
It applies to the AS.
serviceSpecificType [2] OC 0x81 INTEGER This field holds the type of the
serviceSpecificData.
requested-Party- OC 0xBF 65 CHOICE This field specifies the address of the
Address [1] original called party in a SIP
transaction. The value is in SIP URI
or tel URI format. This field is used
when the address of the original
called party is inconsistent with the
value of Called Party Address.
This field is derived from
Requested-Party-Address in the
Centrex-AS CDRs.
sIP-URI [2] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [2] OC 0x81 GraphicString This field is in tel URI format.
list-Of-Called- OC 0xBF 66 SEQUENCE OF This field specifies the address of the
Asserted-Identity [1] final called party.
sIP-URI [2] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [2] OC 0x81 GraphicString This field is in tel URI format.
alternateChargedParty OC 0x9F 67 UTF8String This field is reserved for future
Address expansion and is not in use at
present.
duration OC 0x9F 81 48 INTEGER This field specifies the call duration
in a SIP session.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 137

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

onlineChargingFlag Oc 0x9F 81 16 ENUMERATED This field for China Mobile.

It is the online charging flag and
mandatory when both the online
charging and offline charging are
deployed. If the online charging has
performed for a service, the CDR
does not contain the offline
charging.
 NOT_ONLINE_SERVICE: 0
 ONLINE_SERVICE: 1
 ABNORMAL_ONLINE_SERVIC
E(Online charge exception.): 2
service-indetity-list Oc 0xBF 81 1B SEQUENCE OF Field for China Mobile.
service-indetity- It is the supplementary service flag
list and mandatory when the user
subscribes a supplementary service.
This field specifies the
supplementary service that is used in
this session. If multiple
supplementary services are to be
triggered in a session, multiple
service-indetity-list fields must be
provided.
charged-party [1] Oc 0xBF 81 1C CHOICE Field for China Mobile.
It specifies the charged party. The
user fills the IMPU (tel URI or SIP
URI) of the current charged party in
this field. This field is derived from
Charged-Party in the Centrex-AS
CDRs.
sIP-URI [2] OM 0x80 GraphicString This field is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field is in tel URI format.
call-description Oc 0x9F 81 18 ENUMERATED Field for China Mobile.
It is the session attribute description
and mandatory for the Centrex
service to describe the attribute of
the current call. Value: 1 to 20
This field is user-defined.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 138

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

group-number Oc 0x9F 81 19 UTF8String Field for China Mobile.

This field contains the group number
and is mandatory for the Centrex
service. It specifies the group
numbers that the calling party of the
Centrex user provides for the CCF
calling party and the called party
provides for the CCF called party.
short-number Oc 0x9F 81 1A UTF8String This field specifies the short number
of the Centrex subscriber.
This field in an MOC CDR is set to
the short number of the calling party,
and this field in an MTC CDR is set
to the short number of the called
party.
subscriber-Identity [1] Oc 0xBF 81 49 CHOICE This field specifies the subscriber.
For CRD service, this field is the
user identifier of subscriber A who
initiates a CTD call. This field can
be a SIP URL or a tel URL. For SIP
MESSAGE, the value is set to P-
Asserted-Identify header in the
message; for WEB SERVICE, the
value is set to uc number on the
dialCall interface.
sIP-URI [2] OC 0x80 GraphicString This field is in SIP URI format.
tEL-URI [2] OC 0x81 GraphicString This field is in tel URI format.
calling-party- Oc 0x9F 81 4A UTF8String This field is used to describe the
subgroup-number CUG number of the VTN network
on the originating side. If the calling
party has not subscribed to the CUG
service, this field is set to 0.
called-party-subgrou Oc 0x9F 81 4B UTF8String This field is used to describe the
p-number CUG number of the VTN network
on the terminating side. If the called
party has not subscribed to the CUG
service, this field is set to 0.
calling-party[1] Oc 0xBF814C CHOICE This field is used to describe the
IMPU of the calling party. If P-
Asserted-Identify contains only one
SIP URL, the system sets this field to
the SIP URL. If P-Asserted-Identify
contains more than one SIP URL, the
system sets this field to the TEL URL.

sIP-URI [2] OC 0x80 GraphicString This field is in SIP URI format.

tEL-URI [2] OC 0x81 GraphicString This field is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 139

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

3.10 SBC CDR

The tag value in the SBC CDR is 0xBF 81 7D.

Table 3-1 Format of SBC CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field specifies the type of a

CDR, indicating which NE
generated the CDR.
retransmission OC 0x81 NULL This field specifies whether the
ACRs from the SBC are sent
repeatedly.
sIP-Method OC 0x82 GraphicString This field specifies the reason why
ACRs are generated. This field is
only available in unrelated sessions.
role-of-Node OM 0x83 INTEGER This field specifies the role of the
SBC in the current session.
nodeAddress [1] OM 0xA4 CHOICE This field specifies the ME that
provides the charging messages. It
can be an IP address or a valid
domain name of the ME providing
charging data. This field is derived
from Origin-Host in the SBC
CDRs.
iPAddress [2] OM 0xA0 CHOICE This field is reserved.
domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the session ID.
For a SIP session, the session ID
contains the SIP call ID as defined in
the SIP RFC3261 [404].
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field contains the number
Address [1] information about the calling party.
It can be in SIP URI format or tel
URI format. This field contains
multiple values in a CDR. This field
is derived from the Calling-Party-
Address field in the SBC CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 140

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.
called-Party-Address OM 0xA7 CHOICE This field specifies the number
[1]
information about the called party. It
can be in SIP URI format or tel URI
format. This field is derived from
Called-Party-Address in the SBC
CDRs.
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time when a
amp (SIZE(9)) SIP request is initiated.
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when a
imeStamp (SIZE(9)) peer NE receives a response after the
peer NE initiates a session request.
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when a
meStamp (SIZE(9)) peer NE initiates a request to end a
session.
recordOpeningTime OC 0x8C OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation starts. This
field shows the time when the CCF
receives the first ACR in a session.
At present, it is present only in the
cases related to SIP sessions.
recordClosureTime OM 0x8D OCTET STRING This field specifies the time when
(SIZE(9)) the CDR consolidation ends. This
field shows the time when the CCF
receives the last ACR in a session.
localRecordSequence OM 0x8F INTEGER (0- The CCF allocates a unique SN
Number 4294967295) (these SNs are consecutive and start
with 1) to each CDR. This ensures
that each CDR is unique in the same
CCF. In other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 141

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordSequenceNumb OC 0x90 INTEGER This field is filled only when

er incomplete CDRs are to be
generated.
In the case of timeout or other cases,
the CCF may generate multiple
partial CDRs for the same charging
session. In that case, the CCF
allocates a record SN (starting with
1) to each partial CDR.
It helps the BS check whether a
CDR is complete.
causeForRecordClosi OM 0x91 ENUMERATED This field specifies the reason why a
ng session is ended. It is valid only in
the event and Stop ACR fields.
It is of the enumeration type.
For details, see section 4.42
"causeForRecordClosing."
incomplete-CDR- OC 0xB2 SET This field provides additional
Indication [1] diagnostics when the CCF finds that
charging data is missing. This field
shows whether the CDR content is
complete. If the CDR misses a
partial ACR, the CCF fills in the
following fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value is NO.
Otherwise, the value is YES. If the
charging information is unknown
yet, the value is UNKOWN.
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
iMS-Charging- OM 0x93 OCTET STRING This field is assigned by the first
Identifier accessed ME in the IMS domain and
sent to all MEs in the IMS domain.
It is unique in an end-to-end session.
This field is also called ICID for
short.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 142

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

list-Of-sDP-Media- OC 0xB5 SEQUENCE OF A field of the group type.

Components [1] It contains several sub-fields
associated with one media
component. This field is present in
only one SIP session and may appear
several times in one CDR because
one CDR may contain multiple
sessions.
It describes the details about media
changes in an E2E session. For
example, calling party A starts voice
communications with called party B
at 9:00 am. Then, A and B change
the communication way into video at
9:30 a.m. The initiator of the video
communications can be A or B.
This field is essential to the CCF and
the BS.
This field contains the following
sub-fields:
 SIP-Request-Timestamp
 SIP-Response-Timestamp
 sDP-Media-Components
sIP-Request- OM 0x80 OCTET STRING This field specifies when the SIP
Timestamp [2] (SIZE(9)) Request is initiated.
sIP-Response- OM 0x81 OCTET STRING This field specifies the time when
Timestamp [2] (SIZE(9)) the response to the SIP request is
sent.
sDP-Media- OM 0xA2 SEQUENCE OF A field of the group type.
Components [2] It contains several sub-fields
associated with one media
component. Because several media
components may exist for a session
in parallel, these sub-fields may
appear several times.
This field contains the following
sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
sDP-Media-Name [3] OM 0x80 GraphicString This field specifies the media name.
It contains the information indicated
by the line m= in the SDP
information.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 143

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

sDP-Media- OM 0xA1 SEQUENCE OF This field specifies the media

Descriptions [3] description. It contains the
information indicated by the line a=
in the SDP information.
sIP-Request- OC 0x86 Unsigned32 The field contains the time
Timestamp-Fraction [2] (milliseconds) corresponding to SIP-
Request-Timestamp.
sIP-Response- OC 0x87 Unsigned32 The field contains the time
Timestamp-Fraction [2] (milliseconds) corresponding to SIP-
Response-Timestamp.
serviceReasonReturn OM 0x97 UTF8String This field specifies the reason why a
Code service request succeeds or fails.
accessNetworkInform OC 0x9D OCTET STRING This field specifies the details about
ation special access technologies.
servedPartyIPAddress OC 0xBF 32 IPAddress This field specifies the IP address of
the called party or the calling party.
The SBC uses it to keep in touch
with the called party or calling party.
duration OC 0x9F 81 48 INTEGER This field specifies the call duration
in a SIP session.
Origin- Realm OC 0x9F 82 0A OCTET STRING This field specifies the Rf interface
SBC configuration local-realmname.
Destination- Realm OC 0x9F 82 0B OCTET STRING This field specifies the Rf interface
SBC configuration peer-realmname.
serviceRequestTimeSt Oc 0x9F 25 INTEGER This field set to the value (in
ampFraction (0..999) millisecond) of the field
serviceRequestTimeStamp.
serviceDeliveryStartT Oc 0x9F 26 INTEGER This field set to the value (in
imeStampFraction (0..999) millisecond) of the field
serviceDeliveryStartTimeStamp.
serviceDeliveryEndTi Oc 0x9F 27 INTEGER This field set to the value (in
meStampFraction (0..999) millisecond) of the field
serviceDeliveryEndTimeStamp.
ringing-Duration OC 0x9F 81 4C INTEGER This field specifies the ringing
duration.

3.11 AGCF CDR

The tag value in the AGCF CDR is 0xBF 81 4D.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 144

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Table 3-1 Format of AGCF CDR

Field Category TAG Field Type Description

recordType M 0x80 INTEGER This field identifies the type of the

final CDR generated for a session,
indicating the NE that generates the
CDR.
For details, see section 4.156
"recordType."
retransmission OC 0x81 NULL This field specifies whether the CDR
contains ACRs retransmitted by NE.
This field is mandatory when there is
a retransmitted ACR. If this field is
displayed in the CDR, ACRs
retransmitted by NE are contained in
this CDR. If this field is not
displayed in the CDR , ACRs
retransmitted by NE are not
contained.
The value of this field is derived
from the Retransmission field in the
Diameter message header.
For details, see section 4.160
"retransmission."
sIP-Method OC 0x82 GraphicString This field specifies the type of the
SIP message for charging, for
example, INVITE, UPDATE, BYE,
and CANCEL. If the session ends
properly, the value of this field is
BYE or CANCEL.
The value of this field is derived
from the SIP-Method field in Event-
Type in the last AGCF ACR
received by the CCF.
For details, see section 4.196 "sIP-
Method."
role-of-Node OM 0x83 INTEGER This field specifies the role of the
NE in a session. The value of this
field is derived from the Role-Of-
Node field in the AGCF CDR.
For details, see section 4.163 "role-
of-Node."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 145

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

nodeAddress [1] OM 0xA4 CHOICE This field specifies the ID of the NE

that provides the charging
information. The value may be either
the IP address or the host name of
the NE that generates charging
information. The CCF assigns a
unique ID for each NE in the IMS
domain.
The value of this field is derived
from the Origin-Host field in an
AGCF ACR.
For details, see section 4.121
"nodeAddress."
iPAddress [2] OM 0xA0 CHOICE This field is reserved.

domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the ID of a SIP
session, that is, Call-ID in a SIP
message.
The value of this field is derived
from the User-Session-Id field in an
AGCF ACR.
For details, see section 4.192
"session-Id."
list-Of-Calling-Party- OM 0xA6 SEQUENCE OF This field specifies the number
Address [1] information about the calling party.
The value of this field is derived
from the Calling-Party-Address
field in an AGCF ACR.
For details, see section 4.82 "list-Of-
Calling-Party-Address."
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 146

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

called-Party-Address OM 0xA7 CHOICE This field specifies the number of

[1]
the called party in SIP URI or tel
URI format.
 If the number is in the tel URI
format, the AGCF normalizes the
number.
 If the number is in the SIP URI
format, the AGCF does not
normalize the number.
The value of this field is derived
from the Called-Party-Address field
in an AGCF ACR.
For details, see section 4.31 "called-
Party-Address."
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
serviceRequestTimeSt OM 0x89 OCTET STRING This field specifies the time of the
amp (SIZE(9)) SIP request, that is, the time when
the NEs receive the INVITE
message.
For details, see section 4.186
"serviceRequestTimeStamp."
serviceDeliveryStartT OM 0x8A OCTET STRING This field specifies the time when
imeStamp (SIZE(9)) the NE receives the response after
initiating a session start request, that
is, the time when the NE sends the
start ACR. The NE sends the start
ACR after receiving a 200 OK
message.
For details, see section 4.180
"serviceDeliveryStartTimeStamp."
serviceDeliveryEndTi OC 0x8B OCTET STRING This field specifies the time when an
meStamp (SIZE(9)) NE initiates the request to end the
session.
For details, see section 4.179
"serviceDeliveryEndTimeStamp."
recordOpeningTime OC 0x8C OCTET STRING This field specifies the CDR opening
(SIZE(9)) time, that is, the time when the CCF
receives the first ACR in a session.
At present, it is present only in a
session.
For details, see section 4.154
"recordOpeningTime."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 147

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 148

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

incomplete-CDR- OC 0xB2 SET This field provides additional

Indication [1] diagnostics when the CCF finds that
charging data is missing.
It contains the following three sub-
fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
This field shows whether the CDR
content is complete.
For details, see section 4.76
"incomplete-CDR-Indication."
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
For details, see section 4.10
"aCRStartLost."
aCRInterimLost [2] OC 0x81 ENUMERATED If there is charging information on
the Interim type, the value of this
field is NO. Otherwise, the value is
YES. If it is uncertain whether the
charging information is missing, the
value is UNKNOWN.
For details, see section 4.9
"aCRInterimLost."
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
For details, see section 4.11
"aCRStopLost."
iMS-Charging- OM 0x93 OCTET STRING This field contains the IMS charging
Identifier identifier (ICID) of a SIP session
generated by IMS NEs. Generally,
the charging identifier is generated
by the P-CSCF and assigned to IMS
NEs. It is unique in an end-to-end
(E2E) session and used to associate
CDRs of different NEs in the same
call.
The value of this field is derived
from the IMS-Charging-Identifier
field in an AGCF ACR.
For details, see section 4.74 "iMS-
Charging-Identifier."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 149

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceReasonReturn OM 0x97 UTF8String This field specifies the reason why a

Code service request succeeds or fails.
For details, see section 4.187
"serviceReasonReturnCode."
duration OC 0x9F 81 48 INTEGER This field specifies the duration of a
SIP session.
For details, see section 4.62
"duration."
accounting-record- OC 0x9F 81 63 INTEGER This field specifies the type of the
type offline charging message, including
event CDRs and session CDRs.
 Event CDRs (EVENT_RECORD):
EVENT_RECORD (event CDRs)
 Session CDRs (SIS_RECORD):
START_RECORD (start ACRs)
INTERIM_RECORD (Interim
ACRs)
STOP_RECORD (stop ACRs)
For details, see section 4.7
"accounting-record-type."
charge-category OC 0x9F 81 64 INTEGER This field specifies the type of CDRs
that are generated by the AGCF
during selfswitch, which involves
the following two values:
 0: Normal CDRs
 1: Selfswitch CDRs
This field is from the Charge-
Category AVP of the AGCF.
For details, see section 4.44
"change-category. "
sCSCF-Bypass-State OC 0x9F 81 4C INTEGER This field specifies the type of CDRs
that are generated by the AGCF
during selfswitch, which involves
the following two values:
0 - Normal CDRs
1 - Bypass CDRs
This field is from the sCSCF-
Bypass-State AVP of the AGCF.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 150

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

3.12 RCS CDR

The tag value in the AGCF CDR is 0x BF817C.

Table 3-1 Format of RCS CDR

Field Category TAG Field Type Description

recordType OM 0x80 INTEGER This field identifies the type of the

final CDR generated for a session,
indicating the NE that generates the
CDR.
For details, see section 4.156
"recordType."
retransmission OC 0x81 NULL This field specifies whether the
CDR contains ACRs retransmitted
by NE. This field is mandatory
when there is a retransmitted ACR.
If this field is displayed in the CDR,
ACRs retransmitted by NE are
contained in this CDR. If this field
is not displayed in the CDR , ACRs
retransmitted by NE are not
contained.
The value of this field is derived
from the Retransmission field in the
Diameter message header.
For details, see section 4.160
"retransmission."
sIP-Method OC 0x82 GraphicString This field specifies the type of the
SIP message for charging, for
example, INVITE, UPDATE, BYE,
and CANCEL. If the session ends
properly, the value of this field is
BYE or CANCEL.
The value of this field is derived
from the SIP-Method field in
Event-Type in the last RCS ACR
received by the CCF.
For details, see section 4.196 "sIP-
Method."
role-of-Node OM 0x83 INTEGER This field specifies the role of the
NE in a session. The value of this
field is derived from the Role-Of-
Node field in the RCS CDR.
For details, see section 4.163 "role-
of-Node."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 151

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

nodeAddress [1] OM 0xA4 CHOICE This field specifies the ID of the

NE that provides the charging
information. The value may be
either the IP address or the host
name of the NE that generates
charging information. The CCF
assigns a unique ID for each NE in
the IMS domain.
The value of this field is derived
from the Origin-Host field in an
RCS ACR.
For details, see section 4.121
"nodeAddress."
iPAddress [2] OM 0xA0 CHOICE This field is reserved.

domainName [2] OM 0x81 GraphicString This field specifies the host name of
the ME that generates the current
charging message.
session-Id OM 0x85 GraphicString This field specifies the ID of a SIP
session, that is, Call-ID in a SIP
message.
The value of this field is derived
from the User-Session-Id field in an
RCS ACR.
For details, see section 4.192
"session-Id."
list-Of-Calling-Party- OM 0xA6 SEQUENCE This field specifies the number
Address [1] OF information about the calling party.
The value of this field is derived
from the Calling-Party-Address
field in an RCS ACR.
For details, see section 4.82 "list-
Of-Calling-Party-Address."
sIP-URI [2] OM 0x80 GraphicString This field specifies that the calling
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the calling
number is in tel URI format.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 152

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

called-Party-Address OM 0xA7 CHOICE This field specifies the number of

[1]
the called party in SIP URI or tel
URI format.
 If the number is in the tel URI
format, the RCS normalizes the
number.
 If the number is in the SIP URI
format, the RCS does not
normalize the number.
The value of this field is derived
from the Called-Party-Address field
in an RCS ACR.
For details, see section 4.31 "called-
Party-Address."
sIP-URI [2] OM 0x80 GraphicString This field specifies that the called
number is in SIP URI format.
tEL-URI [2] OM 0x81 GraphicString This field specifies that the called
number is in tel URI format.
privateUserID OM 0x88 GraphicString This field specifies the used
network access ID of the served
party according to the RFC2486
[405].
serviceRequestTimeSt OM 0x89 OCTET This field specifies the time of the
amp STRING SIP request, that is, the time when
(SIZE(9)) the NEs receive the INVITE
message.
For details, see section 4.186
"serviceRequestTimeStamp."
serviceDeliveryStartT OM 0x8A OCTET This field specifies the time when
imeStamp STRING the NE receives the response after
(SIZE(9)) initiating a session start request,
that is, the time when the NE sends
the start ACR. The NE sends the
start ACR after receiving a 200 OK
message.
For details, see section 4.180
"serviceDeliveryStartTimeStamp."
serviceDeliveryEndTi OC 0x8B OCTET This field specifies the time when
meStamp STRING an NE initiates the request to end
(SIZE(9)) the session.
For details, see section 4.179
"serviceDeliveryEndTimeStamp."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 153

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

recordOpeningTime OC 0x8C OCTET This field specifies the CDR

STRING opening time, that is, the time when
(SIZE(9)) the CCF receives the first ACR in a
session. At present, it is present
only in a session.
For details, see section 4.154
"recordOpeningTime."
recordClosureTime OM 0x8D OCTET This field specifies the CDR
STRING closure time. This field shows the
(SIZE(9)) time when the CCF receives the last
ACR in a session.
For details, see section 4.150
"recordClosureTime."
localRecordSequence OM 0x8F INTEGER The CCF allocates a unique SN
Number (0..4294967295 (these SNs are consecutive and start
) with 1) to each CDR. This ensures
that each CDR is unique in the
same Coffin other words, the CCF
allocates a unique Local Record
Sequence Number for each CDR.
This field is unique in the entire
charging process and helps the BS
check whether a CDR is complete.
For details, see section 4.89
"localRecordSequenceNumber."
recordSequenceNumb OC 0x90 INTEGER This field is filled only when
er incomplete CDRs are to be
generated. In the case of timeout or
other cases, the CCF may generate
multiple partial CDRs for the same
charging session. In that case, the
CCF allocates a record SN (starting
with 1) to each partial CDR.
It helps the BS check whether a
CDR is complete.
For details, see section 4.155
"recordSequenceNumber."
causeForRecordClosi OM 0x91 ENUMERATE This field identifies the cause for
ng D ending a session. The value of this
field is derived from the Cause-
Code field in an RCS ACR.
For details, see section 4.42
"causeForRecordClosing."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 154

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

incomplete-CDR- OC 0xB2 SET This field provides additional

Indication diagnostics when the CCF finds
that charging data is missing.
It contains the following three sub-
fields:
 aCRStartLost
 aCRInterimLost
 aCRStopLost
This field shows whether the CDR
content is complete.
For details, see section 4.76
"incomplete-CDR-Indication."
aCRStartLost [2] OC 0x80 BOOLEAN If the charging information on the
Start type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
For details, see section 4.10
"aCRStartLost."
aCRInterimLost [2] OC 0x81 ENUMERATE If there is charging information on
D the Interim type, the value of this
field is NO. Otherwise, the value is
YES. If it is uncertain whether the
charging information is missing, the
value is UNKNOWN.
For details, see section 4.9
"aCRInterimLost."
aCRStopLost [2] OC 0x82 BOOLEAN If the charging information on the
Stop type is missing, the value is
TRUE. Otherwise, the value is
FALSE.
For details, see section 4.11
"aCRStopLost."
iMS-Charging- OM 0x93 OCTET This field contains the IMS
Identifier STRING charging identifier (ICID) of a SIP
session generated by IMS NEs.
Generally, the charging identifier is
generated by the P-CSCF and
assigned to IMS NEs. It is unique in
an end-to-end (E2E) session and
used to associate CDRs of different
NEs in the same call.
The value of this field is derived
from the IMS-Charging-Identifier
field in an RCS ACR.
For details, see section 4.74 "iMS-
Charging-Identifier."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 155

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

serviceReasonReturn OM 0x97 UTF8String This field specifies the reason why

Code a service request succeeds or fails.
For details, see section 4.187
"serviceReasonReturnCode."
serviceContextID OC 0x9D UTF8String This field specifies the specific
services in a session.
duration OC 0x9F 81 48 INTEGER This field specifies the duration of a
SIP session.
For details, see section 4.62
"duration."
serviceRequestTimeSt OC 0x9F 25 INTEGER This field set to the value (in
ampFraction (0..999) millisecond) of the field
serviceRequestTimeStamp.
serviceDeliveryStartT OC 0x9F 26 INTEGER This field set to the value (in
imeStampFraction (0..999) millisecond) of the field
serviceDeliveryStartTimeStamp.
serviceDeliveryEndTi OC 0x9F 27 INTEGER This field set to the value (in
meStampFraction (0..999) millisecond) of the field
serviceDeliveryEndTimeStamp.
serviceIdentifier M 0x BF8155 SEQUENCE This field specifies what types of
OF services are used by a subscriber.
The value of the field is an
enumerated value. It is defined as
follows:
1 PAGER MODE
2 LAGER MODE
3 SM
4 1-1 CHAT
5 1-N CHAT
6 FT
7 IS
8 VS
related-call-reference OC 0x9F815C UTF8String This field is used to associate
session CDRs with event CDRs for
a session.
rcs-Message-Id OM 0x9F8218 UTF8String This field is a message ID used
inside the RCS to associate
charging CDRs with RCS CDRs.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 156

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

message-Source OM 0x9F8219 INTEGER This field specifies the message

source. The values are as follows:
0: SOURCE_IMS_SIP
1: SOURCE_SMSC
2: SOURCE_MSRP
called-Sum OC 0x9F821A INTEGER This field specifies the number of
called parties.
list-Of-Called-User OC 0xBF821B SEQUENCE This field specifies the called
OF number.
message-Length OM 0x9F821C INTEGER This field specifies the length of the
message. When the message is used
to send files, this field indicates the
size of the file. If the message is not
used to send files, this field
indicates the length of the message.
file-Name OC 0x9F821D UTF8String This field specifies the name of the
transferred file.
accessNetworkInform OC 0x9D OCTET This field contains detailed
ation STRING information about the access
network of the subscriber, such as
the protocol and version. You can
determine whether a subscriber is
roaming.
For details, see section 4.5
"accessNetworkInformation."
interOperatorIdentifie OC 0xAE SEQUENCE This field specifies the network
rs [1] OF where a call is initiated and the
network where a call destined for.
During SIP signaling transmission,
this field is recorded in the header
of the P-Charging-Vector.
This group field consists of the
following fields:
 originatingIOI
 terminatingIOI
For details, see section 4.79
"interOperatorIdentifiers."
originatingIOI [2] OC 0x80 GraphicString This field identifiers the network of
the calling party.
For details, see section 4.132
"originatingIOI."

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 157

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

terminatingIOI [2] OC 0x81 GraphicString This field identifiers the network of

the called party.
For details, see section 4.216
"terminatingIOI."
User-Agent-Value OC 0x9F8222 UTF8String This field is used to carry the User-
Agent header field value of the
INVITE message received from the
originating side.
onlineChargingFlag Oc 0x9F8116 ENUMERATE It is the online charging flag and
D mandatory when both the online
charging and offline charging are
deployed. If the online charging has
performed for a service, the CDR
does not contain the offline
charging.
Enumerative value:
 0: The current subscriber is an
offline charging subscriber.
 1: The current subscriber is an
online charging subscriber.
 2: Online charging is abnormal.
For details, see section 4.125
"onlineChargingFlag."
accountingInputOctets Oc 0x9F821E Unsigned64 This field specifies the number of
octets (resp packets) ,transmitted
during the data container recording
interval, reflecting the volume
counts for uplink traffic for a data
flow.
accountingOutputOcte Oc 0x9F821F Unsigned64 This field specifies the number of
ts octets (resp packets) ,transmitted
during the data container recording
interval, reflecting the volume
counts for downlink traffic for a
data flow.
accountingInputPacke Oc 0x9F8220 Unsigned64 This field specifies the number of
ts packets (resp octets) ,transmitted
during the data container recording
interval, reflecting the volume
counts for uplink traffic for a data
flow.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 158

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Formats

Field Category TAG Field Type Description

accountingOutputPac Oc 0x9F8221 Unsigned64 This field specifies the number of

kets packets (resp octets) ,transmitted
during the data container recording
interval, reflecting the volume
counts for downlink traffic for a
data flow.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 159

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4 Description of CDR Fields

CDR fields refer to the specific fields that are present in CDRs. For more information on the
fields that are present in different CDRs, see chapter 3 "Description of CDR Formats." This
chapter describes the functions and ASN.1 codes of some of these CDR fields.

4.1 abnormal-Finish-Info
This field contains the reason why a session or an event is ended abnormally. The reason is
carried in a BYE message or other SIP messages. This field contains the following sub-fields:
 abnormalFinishReason
 abnormalFinishWarning

4.2 abnormalFinishReason
This field contains session failure information in the Reason header field of a SIP message.
The session failure information is carried in an ACR[Stop] message or the event ACR in a
4XX, 5XX, or 6XX message.

4.3 abnormalFinishWarning
This field contains session failure information in the Warning header field of a SIP message.
The session failure information is carried in an ACR[Stop] message or the event ACR in a
4XX, 5XX, or 6XX message.

4.4 accessNetworkChargingIdentifier
This field specifies the access network charging ID. It can be appeared only when the type of
access NEs is not a standard type defined in 3GPP specifications.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 160

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.5 accessNetworkInformation
This field contains detailed access technologies, such as protocols in use and versions. For
example: 3GPP-UTRAN-TDD; utran-cell-id-3gpp=234151D0FCE11. 3GPP-UTRAN-TDD;
utran-cell-id-3gpp=234151D0FCE11. You can determine whether a subscriber is roaming. If
the home network is different from the access network, the subscriber is roaming.
This field is displayed only when the access network element (NE) is not in a standard type
defined in 3GPP.
In an MOC CDR, this field is set to the access network information about the calling party. In
an MTC CDR, this field is set to the access network information about the called party.

4.6 access-phone
This field specifies the access code of the conference. It is related to a specified conference
service. For example, the user can participate in an HD video conference by dialing the access
code for the HD video conference service.

4.7 accounting-record-type
This field specifies the service type. It is used to identify whether the CDRs are event CDRs
or session CDRs.
 1: EVENT_RECORD (EVENT_RECORD);
 2: START_RECORD (SIS_RECORD);
 3: INTERIM_RECORD (SIS_RECORD);
 4: STOP_RECORD (SIS_RECORD)

4.8 aCName
This field contains the service name of the ATS9900. This service name is configured in
Application Server of the iFC. The ATS9900 obtains the value of the ACName field from the
Route header field of a SIP message. If the Route header field does not carry the service name
of the ATS9900, the aCName field is set to the value of the ATS9900 instance name.

4.9 aCRInterimLost
If there is charging information on the Interim type, the value of this field is NO. Otherwise,
the value is YES. If it is uncertain whether the charging information is missing, the value is
UNKNOWN.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 161

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.10 aCRStartLost
If the charging information on the Start type is missing, the value is TRUE. Otherwise, the
value is FALSE.

4.11 aCRStopLost
If the charging information on the Stop type is missing, the value if this field is TRUE.
Otherwise, the value is FALSE.

4.12 adapter-Resource
Adapter resource occupied by a conference: This resource is required only when a scheduled
conference needs to be adapted.

4.13 additional-Called-Party-Address
This field holds information about the additional called party number. In Number-Portability
feature, the field holds the called subscriber physical number.

4.14 additional-Calling-Party-Address
This field holds information about the additional calling number. In Number-Portability
feature, the field holds the calling subscriber physical number.

4.15 alternateChargedPartyAddress
This field is reserved for future expansion and is not in use at present.

4.16 applicationProvidedCalledParties
This field specifies the SN of the service triggered by the AS NE. Because there may be
multiple services, this item is a list.

4.17 applicationServersInformation
This field specifies the group type. It contains two sub-fields: applicationServersInvolved and
applicationProvidedCalledParties.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 162

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.18 applicationServersInvolved
This field specifies the AS ID identified by a SIP URI.

4.19 application-Servers-State
This field specifies whether any unavailable AS exists. This field can be set to the following
values:
 0: No unavailable AS exists.
 1: An unavailable AS exists.

4.20 associated-Party-Address
 In forwarding service, this field contains the number of the forwarding service party.
 In ECT service, this field contains the number of the party that presses the hookflash.
 If the calling party presses the hookflash, this field can be set to a tel URI or a SIP URI
in preference.
Typical scenarios for the ATS9900 are as follows:
 For a call forwarding service, this field is set to the forwarded-to number.
 For a hookflash service, this field is set to the switched-to number of the explicit call
transfer (ECT) service.

4.21 audioPort-Resource
This field specifies the audio port used by a conference.

4.22 authorized-QoS
This field is reserved for future expansion and is not in use at present.

4.23 bandwidth-Resource
This field specifies the bandwidth resource occupied by a conference. This resource is
required only for scheduled a video conference.

4.24 bearerService
Bearer-Service is a sub-field of the IMS-Information field and is used to describe the bearer
services used by the PSTN to communicate with the IMS network. The UGC3200 puts two
character strings in the Bearer-Service field. These two character strings are both hexadecimal

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 163

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

strings consisting of two bytes. The CCU assigns one character string to the tMU and the
other to the tMR.

4.25 bill-type
MediaX3600 offline charging CDR modes:
 ACCESS_CDR 1 //Access CDR
 CONFERENCE_CDR 2 //Conference CDR
 RECORDING_LISTEN_CDR 3 //Record listening CDR
 SCHEDULING_CDR 5 //Conference scheduling CDR
 CANCLING_CDR 6 //Cancellation CDR
 MODIFICATION_CDR 7 //Modification CDR
 CALL_SET_CDR 8 //Call set CDR
 EXTENSION_CDR 9 //Prolong CDR
 DATA_CONFERNCE_CDR 10 //Data conference CDR
 RECORDING_CDR 11 //Recording CDR
 MEETING_CDR 12 //Meeting CDR
 SMS_CDR 13 //SMS CDR
 ORDER_CDR 15 // ORDER CDR
 QOS_CDR 16 // QOS CDR

4.26 call-description
Field for China Mobile.
It is the session attribute description and mandatory for the Centrex service to describe the
attribute of the current call. The values range from 1 to 20. This field is configurable.
This field is set to the value of the VPN-Call-Property field on the ATS9900 when the
following conditions are met:
 The software parameter Release of the Format Engine Package is set to CTEL.
 The Rf interface version parameter is set to Version R7 in the AP object.
 The Dynamic link library for merging CDRs parameter is set to IMS_R8 in the
PROCESSOR object.

4.27 call-id
This field specifies the ID of a specific conference:
The ID is expressed as a running count + @ + the host IP (for example: 200@10.78.216.200).

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 164

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.28 call-property
This field specifies the call property type. This field specifies whether this call is a local call,
national toll call, or international toll call.
In basic calls, this field is usually filled with local call, national toll call or other call
properties. For services that need to dial a prefix, this field is filled with new service call in
event CDRs. This field is empty for call forwarding/restriction services.
This field describes call property types. It is defined as follows:
 Unknown-Call (0), //Undefined call property type which may appear in CDR for the
terminating side for forwarding services.
 Intra-Office-Call (1), //The current call is an intra-office call.
 Local-Call (2), //The current call is a local call.
 Local-Toll-Call (3), //The current call is a local toll call. This call type applies to
regional calls to certain numbers which charge higher/lower than normal.
 National-Toll-Call (4), //The current call is a national toll call.
 International-Toll-Call (5), //The current call is an international toll call.
 Intra-Local-Toll-Call (6),
 Intra-National-Toll-Call (7),
 Intra-Inter-Toll-Call (8),
 PQRN-Call (9),
 PQRNNTP-Call (10),
 PQRNNTPP-Call (11),
 PQRPN-Call (12),
 PQRI-Call (13),
 PQRIITP -Call (14),
 PQRIITPP-Call (15),
 PQRPI-Call (16),
 New-Service-Call (17), //This value only appears in event CDRs.

4.29 call-Watch-Flag
This field is used to determine whether the ATS9900 checks all calls made by a subscriber. If
this field is contained, the ATS9900 adds a call-watch-flag to CRDs, such as session CDRs,
event CDRs, and failure CDRs, when the subscriber makes either an ingoing or outgoing call.
This field is defined as follows:
Call-Watch-Flag ::= ENUMERATED
{
nO (0),
yES (1)
}

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 165

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.30 called-local-dn-set
This field contains the local DN set of the called user.
In an ACR sent by the originating ATS9900, the corresponding field is set to the local DN set
of the calling party.
In an ACR sent by the terminating ATS9900, the corresponding field is set to the local DN set
of the called party.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is carried in the session ACR and event ACR.
 In a Centrex basic call, this field is carried in the session ACR and event ACR.
 In a basic call of a North America subscriber, this field is carried in the session ACR and
event ACR.
 In an ICS basic call, this field is carried in the session ACR and event ACR.
 In other services, this field is carried in the session ACR, but not in the event ACR.

4.31 called-Party-Address
The field corresponding to this field contains the called number, which may be a SIP UIR or a
tel URI. The value is obtained from the Request-URI header field of a SIP message.
If the called number is a tel URI, the ATS9900 normalizes the number.
The originating ATS9900 specifies this field based on the value of Bill unification type
configured by running ADD CNACLD. The number may be in the following format:
 A global number with a preceding plus sign (+), for example, +867552842001
 A global number with a preceding plus sign (+) and hyphens, for example, tel:+86-755-
2842001
 An international number with the international toll prefix, for example, 00867552842001
 An international number without the international toll prefix, for example,
867552842001
 Source number format (the ATS9900 does not normalize the number)
The terminating ATS9900 sets this field to a global number with a preceding plus sign (+).
If the called number is a SIP URI, the ATS9900 does not normalize the number.
The value of this field depends on the service type. The relationship between the field value
and the service type is as follows:
 Centrex basic call service
− If the Adapt NGN CDR parameter is not configured in the RFPARAM object, the
value of the called-Party-Address field in a Centrex basic call is the same as that of
the called-Party-Address field in a basic call.
− If the Adapt NGN CDR parameter has been configured in the RFPARAM object, a
terminating ATS9900 sets the called-Party-Address field in a Centrex basic call to the
subscriber number. An originating ATS9900 specifies the same field based on the call
type. For a local call, the field is set to the subscriber number. For a national toll call,
the field is set to the national number with the national toll prefix. For an

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 166

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

international toll call, the field is set to the international number with the international
toll prefix.
 CF service
− A call from A to B is forwarded to C. The call is successfully connected. If the
Number fill mode in bill parameter is set to A-C and B-C bill in the CFXCFG
object, ATS9900 B generates two CDRs, an MTC CDR and an MOC CDR. In both
CDRs, the called-Party-Address field is set to the number of C.
− If the Number fill mode in bill parameter is set to A-B and B-C bill in the CFXCFG
object, ATS9900 B generates two CDRs, an MTC CDR and an MOC CDR. In the
MTC CDR, the called-Party-Address field is set to the number of B. In the MOC
CDR, the same field is set to the number of C.
− If the Number fill mode in bill parameter is set to A-C bill in the CFXCFG object,
ATS9900 B generates a CDR, in which the called-Party-Address field is set to the
number of C.
 Number normalization
− The green call service is triggered in a call from A to B, and the call is forwarded to
C. The call is successfully connected. ATS9900 B generates two CDRs, an MTC
CDR and an MOC CDR. In the MTC CDR, the called-Party-Address field is set to
the normalized number of B. In the MOC CDR, the same field is set to the
normalized number of C.
− A call from A to B is forwarded to C. The call is successfully connected. ATS9900 B
generates two CDRs, an A-C CDR and an A-B CDR. In the A-C CDR, the called-
Party-Address field is set to the normalized number of C. In the A-B CDR, the same
field is set to the normalized number of B.
 In a hookflash service, the setting of the called-Party-Address field is similar to that in
the green call service.
 In a multi-ring service, A initiates a call to B. The UEs of B and C ring at the same time.
C answers the call. ATS9900 B generates two CDRs, an MTC CDR and an MOC CDR.
In the MTC CDR, the called-Party-Address field is set to the number of B. In the MOC
CDR, the same field is set to the number of C.
 In an inbound service, when a subscriber is the calling party, the setting of the called-
Party-Address field is similar to that in the basic call service; when a subscriber receives
a call by the vice number, the called-Party-Address field is set to the major number of the
subscriber.
 In an outbound service, when a subscriber is the calling party, the setting of the called-
Party-Address field is similar to that in the basic call service. When a subscriber receives
a call by the vice number, the setting of the called-Party-Address field depends on the
setting of software parameter P1131. If P1131 is set to 1, the field is set to the major
number of the subscriber; otherwise, the setting of the called-Party-Address field is
similar to that in the basic call service.

4.32 called-party-number-type
This field specifies the number type of the called party.
An originating ATS9900 sets the corresponding field to the subscriber number.
A terminating ATS9900 sets the corresponding field to the subscriber number for a SIP URI.
For a tel URI, the terminating ATS9900 specifies the field depending on the call type, a local
call, a national toll call, or an international toll call.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 167

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

This field is defined as follows:

 0: Subscriber number; called number = local number.
 1: Reserved.
 2: National number; called number = area code + local number.
 3: International number; called number = country code + area code + local number.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is carried in the session ACR and event ACR.
 In a Centrex basic call, this field is carried in the session ACR and event ACR.
 In a basic call of a North America subscriber, this field is carried in the session ACR and
event ACR.
 In an ICS basic call, this field is carried in the session ACR and event ACR.
 In other services, this field is carried in the session ACR, but not in the event ACR.

4.33 called-party-subgroup-number
This field describes the CUG number of the VTN network on the terminating side. If the
called party has not subscribed to the CUG service, this field is set to 0.

4.34 caller-Service-Identifier
The field corresponding to this field carries the service ID used by the calling party. This
service ID is displayed only in the MTC CDR.
This field is included in an MTC CDR only if the terminating ATS9900 receives an INVITE
message that carries the id parameter in the Privacy header field.
The value of this parameter can be 1 (CLIR).

4.35 carrierSelectRouting
This field is reserved for future expansion and is not in use at present.

4.36 carrier-Identification-Code
This field specifies the code of carriers to be selected.
The field corresponding to this field is included only if the value of the call-property field is
PQRN, PQRNNTP, PQRNNTPP, PQRPN, PQRI, PQRIITP, PQRIITPP, PQRPI, or CBCP.
In a CDR for a common call, this field is set to Empty.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 168

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.37 calling-local-dn-set
This field specifies the local DN set of the calling number.
On the originating ATS9900, the value of the corresponding field is the local DN set of the
calling number.
On the terminating ATS9900, the value of the corresponding field is the local DN set of the
calling number received from the network. If the ATS9900 fails to obtain the local DN set of
the calling number from the P-Asserted-Service-Info header field, the calling-local-dn-set
field is set to the local DN set of the called party.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is carried in the session ACR and event ACR.
 In a Centrex basic call, this field is carried in the session ACR and event ACR.
 In a basic call of a North America subscriber, this field is carried in the session ACR and
event ACR.
 In an ICS basic call, this field is carried in the session ACR and event ACR.
 In other services, this field is carried in the session ACR, but not in the event ACR.

4.38 calling-party-category
This field contains the category of the calling party.
An originating ATS9900 queries the subscriber data to obtain the subscriber type and sets this
field to the queried subscriber type.
A terminating ATS9900 obtains the value in the P-Asserted-Service-Info header field received
from the network.
This field is defined as follows:
 00: unknown
 01: operator - French
 02: operator - English
 03: operator - German
 04: operator - Russian
 05: operator - Spanish
 06: operator - language by mutual agreement (Chinese)
 07: operator - language by mutual agreement
 08: operator - language by mutual agreement (Japanese)
 09: domestic operator
 0A: common subscriber (used for national toll call - national toll call and national toll
call - local call)
 0B: prioritized subscriber (used for national toll call - national toll call, national toll call -
local call and local call - local call)
 0C: data call (voice band data)
 0D: test call
 0E: reserved

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 169

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

 0F: payphone
 10: Prison
 224: Local Brazil
 226: Customized operator 226
 232: Customized IN platform 232
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is carried in the session ACR and event ACR.
 In a Centrex basic call, this field is carried in the session ACR and event ACR.
 In a basic call of a North America subscriber, this field is carried in the session ACR and
event ACR.
 In an ICS basic call, this field is carried in the session ACR and event ACR.
 In other services, this field is carried in the session ACR, but not in the event ACR.

4.39 calling-party-number-type
This field specifies the address type of the calling party's number.
This field is defined as follows:
 0: subscriber number; calling party's number = local number.
 1: reserved.
 2: valid domestic number; calling party's number = area code + local number.
 3: international number; calling party's number = country code + area code + local
number.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is carried in the session ACR and event ACR.
 In a Centrex basic call, this field is carried in the session ACR and event ACR.
 In a basic call of a North America subscriber, this field is carried in the session ACR and
event ACR.
 In an ICS basic call, this field is carried in the session ACR and event ACR.
 In other services, this field is carried in the session ACR, but not in the event ACR.

4.40 calling-party-subgroup-number
This field describes the CUG number of the VTN network on the originating side. If the
calling party has not subscribed to the CUG service, this field is set to 0.

4.41 calling-User-Type
This field specifies the type of the calling user.
This field is defined as follows:

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 170

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

0 ORDINARY // ordinary subscriber

1 TEST // test subscriber
2 OPERATOR // operator
3 PAYPHONE // prepaid subscriber
5 PRIORITY // priority subscriber
6 DATA // data subscriber

4.42 causeForRecordClosing
This field specifies why a session is ended and is only filled in event and Stop ACRs. It is
defined as follows:
CauseForRecordClosing ::= ENUMERATED
{
0, "SERVICE_DELIVERY_END_SUCCESSFULLY",//The session ends properly.
1, "UNSUCCESSFUL_SERVICE_DELIVERY",//The session fails or an exception
response is received.
3, "TIME_LIMIT",//CDR consolidation times out.
4, "SERVICE_CHANGE",//change in media due to Re-Invite.
5, "MANAGEMENT_INTERVENTION",//partial record generation reasons to be added.
6, "MAX_CHANGE_COND", //Number in List of Message Bodies exceeded.
-- Additional codes are for further study
}

4.43 changeTime
This field carries the UTC time when a subscriber creates, joins or quits a conference. This
field is used in three-party conference calls and conference charging.

4.44 change-category
This field is used to specify the type of CDRs that are generated by the AGCF during
selfswitch, which involves the following two values:
 0: Normal CDRs
 1: Selfswitch CDRs

4.45 charging-Complaint
This field is used to determine whether the ATS9900 additionally generates a complaint CDR
for outgoing calls of a subscriber.
This field is defined as follows:

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 171

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

Charging-Complaint ::= ENUMERATED

{
nO (0),
yES (1)
}

4.46 chargingCategory
This field specifies a charging type. It is available only for prepaid and free subscribers.
 0: CHARGE-NORMAL(Common subscriber)
 1: CHARGE-FREE(Free subscriber)
 2: CHARGE-PREPAID(Prepayment subscriber)
 3: CHARGE-CALLED

4.47 charged-party
This field is only for China Mobile.
This field specifies the charged party and is filled in with the IMPU (tel URI or SIP URI) of
the current charged party.
An MOC field carries the normalized calling number. This field is set to the value of the PSU
header field, if available. An MTC field carries the normalized called number. This field is set
to the service party number, which is carried in the Request-URI header field, if a
supplementary service is triggered.

4.48 closed-code
This field specifies the cause of ending a conference. This field is defined as follows:
 0: CLOSED_CODE_ TERMINAL //The end time is reached,
and the conference is closed normally.
 1: CLOSED _CODE_FORCED_TERMINAL //The conference is forcibly
closed.
 2: CLOSED _CODE_ABORT //The conference is
abnormally closed.

4.49 closed-time
This field specifies the time when a conference is ended.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 172

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.50 closed-User-Group-ID
This field specifies a CUG group number. It is available only for the CUG service. This AVP
value is generated by the combination of networkIndicator and cugInterlockBinaryCode.
This field must be a hexadecimal number, with the fixed length of two bytes. For example, if
networkIndicator is 512, and cugInterlockBinaryCode is 3EF, the Closed-User-Group-ID
is 051203EF.

4.51 content-Disposition
This field indicates the description of media. It is contained in the Content-Disposition header
field of SIP messages.

4.52 content-Length
This field specifies the length of a SIP message.

4.53 content-Type
This field indicates the media type. It is contained in the Content-Type header field of SIP
messages.

4.54 created-time
This field specifies the time when a conference is created.

4.55 current-data-party
This field specifies the number of participants in the current data conference.

4.56 current-party
This field specifies the number of participants in the current voice or video conference,
excluding the participants in the telepresence conference and data conference.

4.57 current-telepresence-party
This field specifies the number of participants in the current telepresence conference.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 173

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.58 dialled-Party-Address
This field specifies the called number. If the subscriber has subscribed to number changing
services, the number displayed by this field is the original number.
The field corresponding to this field is obtained from the Request-URI header field carried in
a Request message that the ATS9900 receives. The ATS9900 normalizes the format of only
international numbers.

4.59 diversioncount
This field specifies the count of diversion. This field is carried only in a CDR for a service
that call forwarding occurs, for example, a CF CDR, a secretary CDR, and a commercial
trunk CDR.
This field is empty in basic calls, common CDRs and forwarded terminating side CDRs.
This field is only filled with a value for forwarded originating side CDRs. For the same call,
this field is increased by 1 each time the call is forwarded. For example, a call can be
forwarded in this order: A  B  C  D  E.
 ATS-A: ACR(A->B) null
 ATS-B: ACR(A-C) null
 ATS-B: ACR(B->C) 1
 ATS-C: ACR(A-C) null
 ATS-C: ACR(C-D) 2
 ATS-D: ACR(A-D) null
 ATS-D: ACR(D-E) 3
 ATS-E: ACR(A-E) null

4.60 diversionreason
This field specifies the reasons for diversion.
This field describes the reason for ATS9900 diversion. Each reason corresponds to a diversion
service. It is defined as follows:

4.61 down-CascadePorts
This field specifies the number of down-cascade ports in a cascaded-conference CDR

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 174

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.62 duration
This field specifies the call duration in a SIP session.

4.63 end-code
This field specifies the end code.
 END_CODE_NORMAL 0 //The user quits the call normally.
 END_CODE_NO _PORT 1 //No port is configured.
 END_CODE_TERMINAL 2 //The end time is reached.
 END_CODE_FORCED_TERMINAL 3 //The conference is forcibly closed.
 END_CODE_BUSY 4 //The called number set is busy.
 END_CODE_NOT_FOUND 5 //The called number set does not exist.
 END_CODE_INVITE_FAILED 6 //The call set fails.
 END_CODE_REFUSED 7 //The call is rejected.
 END_CODE_LOCKED 8 //The conference is locked.
 END_CODE_ABORT 9 //The system is abnormal.

4.64 event
This field corresponds to the event header field in a SUBSCRIBE or NOTIFY message. The
field corresponding to this field is carried only in the event ACR of a SUBSCRIBE message.

4.65 expiresInformation
This field is reserved for future expansion and is not in use at present.

4.66 fci-Free-Format-Data-Manne
This field is used to identify the filling mode of the Fci-Free-Format-Data and is contained in
the FCI messages of the IN services.
This field is defined as follows:
Fci-Free-Format-Data-Manner ::= ENUMERATED
{
oVERWRITE (0), // Fci-Free-Format-Data is filled in overwriting manner
aPPEND (1) // Fci-Free-Format-Data is filled in appending manner
}

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 175

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.67 default-Call-Handling
This field is used to identify the default call process type of IN service. if no default call
process occurred, this field doesn't appear.
process type：
0：CONTINUE
1：RELEASE

4.68 first-level-bill-group
This field specifies the first level distinctive charging group number of the subscriber.
The field corresponding to this field is determined by the First level bill group parameter
configured by running ADD SBR. The field does not carry the PBX index, which does not
carry subscriber data.

4.69 gGSNaddress
This field specifies the IP address of the GGSN that generates a GPRS charging number. The
field corresponding to this field is carried only if the P_Charging_Vector header field of a SIP
message carries the IP address of the corresponding GGSN.
The first two bytes of this field specify the address type.
 If the first two bytes are 01, the IP address is an IPv4 address.
 If the first two bytes are 10, the IP address is an IPv6 address.

4.70 gPRS-Charging-Id
This field specifies the ID of the GGSN that provides bearer at the bearer layer (PS domain),
namely, GCID. It is implemented by converting the numeric string into integers. If the PS
domain bearer changes, the IMS domain is notified of the field. The BS then uses the ICID
and GCID to associate with CDRs. This field is reserved for future expansion and is not in use
at present. It can be appeared only when the type of access NEs is a standard type defined in
3GPP specifications. This field is carried in the P-Charging-Vector header field. Otherwise,
this field is carried in the Access-Network-Charging-Identifier-Value header field.

4.71 groupID
The field contains the group ID of a group subscriber. An originating ATS9900 sends the
group ID of the calling party to the CCF. A terminating ATS9900 sends the group ID of the
called party to the CCF.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is not available.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 176

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

 In a Centrex basic call, this field carries the group ID of a group subscriber.
 In a basic call of a North America subscriber, this field is not available.
 In an ICS basic call, this field is not available.
 In other services, this field carries the group ID of a group subscriber.

4.72 group-id
This field specifies the group ID. It is used in the Group call service.

4.73 group-number
Field for China Mobile.
This field contains the group number and is mandatory for the Centrex service. It specifies the
group numbers that the calling party of the Centrex user provides for the CCF calling party
and the called party provides for the CCF called party.
This field is set to the value of the Group-ID field on the ATS9900 when the following
conditions are met:
 The software parameter Release of the Format Engine Package is set to CTEL.
 The Rf interface version parameter is set to Version R7 in the AP object.
 The Dynamic link library for merging CDRs parameter is set to IMS_R8 in the
PROCESSOR object.

4.74 iMS-Charging-Identifier
This field contains the IMS charging identifier (ICID) for a SIP session. Generally, the ICID is
generated by the P-CSCF and sent to the NEs in the IMS. The ICID is unique in an E2E
session and is used to associate CDRs on different NEs.
The field corresponding to this field is carried in the P-Charging-Vector header field. If an NE
receives a SIP message that does not carry the P-Charging-Vector header field, the NE
generates an ICID.

4.75 iMSCommunicationServiceIdentifier
This field is reserved for future expansion and is not in use at present.

4.76 incomplete-CDR-Indication
This field provides additional diagnostics when the CCF finds that charging data is missing,
as defined below:
incomplete-CDR-Indication ::= SET
{

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 177

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

aCRStartLost [0] BOOLEAN, -- TRUE if ACR[Start] was lost, FALSE otherwise

aCRInterimLost [1] ACRInterimLost,
aCRStopLost [2] BOOLEAN -- TRUE if ACR[Stop] was lost, FALSE otherwise
}

 aCRStartLost: If the charging information on the Start type is missing, the value is
TRUE. Otherwise, the value is FALSE.
 aCRInterimLost: If there is charging information on the Interim type, the value of this
field is NO. Otherwise, the value is YES. If it is uncertain whether the charging
information is missing, the value is UNKNOWN.
 aCRStopLost: If the charging information on the Stop type is missing, the value is
TRUE. Otherwise, the value is FALSE.

4.77 initialIMS-Charging-Identifier
This field is used to associate CDRs generated for a VoLTE session in which a
SRVCC/eSRVCC handover occurs. During a SRVCC/eSRVCC handover, a CDR containing
this field is generated. This field contains the ICID of CDRs generated before the handover.

4.78 inner-error
This field contains the information about an inner faulty operation.

4.79 interOperatorIdentifiers
This field specifies the network where a call is initiated and the network where a call destined
for. During SIP signaling transmission, this field is recorded in the header of the P-Charging-
Vector.
This field is of the group type, containing the following sub-fields:
 originatingIOI
 terminatingIOI

4.80 list-of-application-Servers-Abnormal
This field specifies the list of ASs which failed to be triggered during a call.

4.81 list-Of-Associated-URI
This field is reserved for future expansion and is not in use at present.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 178

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.82 list-Of-Calling-Party-Address
This field specifies the information about calling number. This field can contain the SIP URI
or tel URI of the calling party. It corresponds to the PAI header field contained in an INVITE
request. If the PAI header field is not contained in an INVITE request, this field corresponds
to the From header field. This field contains multiple values in a CDR.
The format of the value of this field depends on the value of software parameter P1054:
 If software parameter P1054 is set to 0, the value of this field is a tel URI.
 If software parameter P1054 is set to 1, the value of this field is a SIP URI.
 If software parameter P1054 is set to 2, the value of this field is in the format of tel URI
+ SIP URI.
 If software parameter P1054 is set to 3, the value of this field is in the format of SIP URI
+ tel URI.
If software parameter P1054 is set to 0, this field is set to a global number (tel URI) with
the plus sign (+).
The values of this field in CDRs generated for different services are described as
follows:
 Centrex basic calls
If the Adapt NGN CDR parameter is not set by running the MOD RFPARAM
command, the value of this field is the same as that of an original basic call.
If the Adapt NGN CDR parameter is set, this field in an MOC CDR is set to a
subscriber number. This field in an MTC CDR is set based on the call attribute. For a
local call, this field in an MTC CDR is set to the subscriber number. For a national toll
call, this field in an MTC CDR is set to the calling number in the format of area code +
local number. For an international toll call, this field in an MTC CDR is set to the calling
number in the format of country code + area code + local number.
 CF service:
Subscriber A calls subscriber B, and the call is successfully forwarded to subscriber C. If
the Number fill mode in bill parameter is set to A-C and B-C bill, an MOC CDR and
an MTC CDR are generated for subscriber B, and this field in the MTC CDR is set to the
number of subscriber A and this field in the MOC CDR is set to the number of subscriber
B.
If the Number fill mode in bill parameter is set to A-B and B-C bill, an MOC CDR and
an MTC CDR are generated for subscriber B, and this field in the MTC CDR is set to the
number of subscriber A and this field in the MOC CDR is set to the number of subscriber
B.
If the Number fill mode in bill parameter is set to A-C bill, only one CDR is generated
for subscriber B, and this field in the CDR is set to the number of subscriber A.
 Hook Switch services:
Subscriber A calls subscriber B. B presses the hookflash and forwards the call to
subscriber C. Two ACRs are generated for B. One is a terminating ACR in which this
field is set to A's number and one is an originating ACR in which this field is set to B's
number.
If A calls B and transfers the call to C, two ACRs are generated for A. In both the two
ACRs, this field is set to A's number.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 179

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.83 list-Of-Called-Asserted-Identity
This field specifies the address of the final called party (SIP number or tel number). It can be
contained only in the MOC CDRs. The number contained in the P-Asserted-Identity header
field in 18X or 200 response message of the final connected party is filled in this field.
This field records the number of the subscriber that answers the call in basic calls. The value
of this field is set to Empty in the event CDRs. For example, if the subscriber is registered by
dialing the service access number or uses the call forwarding or call barring service, the value
of the event CDR which is triggered by this registration or subscription set to Empty.

4.84 list-Of-Early-sDP-Media-Components
This field is reserved for future expansion and is not in use at present.

4.85 list-Of-Message-Bodies
This field is a group type field. It describes the SIP messages transmitted between the IMS
NEs. Because SIP signaling may be exchanged among several messages, the field may appear
several times.
This field contains the following sub-fields:
 content-Type
 content-Disposition
 content-Length
 originator

4.86 list-Of-sDP-Media-Components
This field describes the details about media change in an end-to-end session. It is of the group
type. It contains several sub-fields associated with one media component. This field is present
in only one SIP session and may appear several times in one CDR because one CDR may
contain multiple sessions.
It provides details about media changes in an E2E session. For example, calling party A starts
voice talk with called party B at 9:00 am. Then, A and B change the communication way into
video at 9:30 a.m. The initiator of the video communications can be A or B.
This field is essential to the CCF and the BS. Nevertheless, it can be empty in event CDRs.
This field is complex and contains the following sub-fields:
 sDP-Session-Description
 sIP-Request-Timestamp
 sIP-Response-Timestamp
 sDP-Media-Components
 mediaInitiatorFlag
 mediaInitiatorParty

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 180

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.87 list-of-subscription-ID
This field records the IDs of the subscriptions of the services. The value is the URI of the
calling party, called party, or connection party.
This field is of the group type, containing the following sub-fields:
 subscriptionIDType
 subscriptionIDData
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is not available.
 In a Centrex basic call, this field is not available.
 In a basic call of a North America subscriber, this field is not contained.
 In an ICS basic call, this field is set to the subscriber identifier.
 In other services, this field is set to the subscriber identifier.

4.88 locationInformation
This field specifies the location of the exchange providing services. This field is defined by
Huawei.

4.89 localRecordSequenceNumber
The CCF allocates a unique SN (these SNs are consecutive and start with 1) to each CDR.
This ensures that each CDR is unique in the same CCF. In other words, the CCF allocates a
unique Local Record Sequence Number for each CDR.
This field is unique in the entire charging process and helps the BS check whether a CDR is
complete.

4.90 location-routing-number
This field contains the routing number of the called party.

4.91 lrn-query-status
This field contains the query status of the LRN.

4.92 lrn-source-indicator
This field contains the source of the LRN.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 181

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.93 main-screen
This field specifies the number of the main screen.

4.94 main-screen-entrance-type
This field specifies the mode by which the main screen joins a conference. It includes dialing
a specific number, being invited and others.

4.95 mediaInitiatorFlag
This field specifies whether the called party redirects the media. When the value in the Media-
Initiator-Flag field sent by the host is called-Party, this field encodes. Otherwise, this field
does not encode.

4.96 mediaInitiatorParty
This field is reserved for future expansion and is not in use at present.

4.97 media-type
Media type of the conference:
 ONLY_AUDIO 1 //Voice
 AUDIO_AND_DATA 2 //Voice and data
 AUDIO_AND_VIDEO 3 //Voice and SD video
 AUDIO_DATA_VIDEO 4 //Voice, SD video, and data
 AUDIO_AND_HDVIDEO 5 //Voice and HD video
 AUDIO_DATA_HDVIDEO 6 //Voice, HD video, and data
 AUDIO_AND_telEPRESENCE 7 //Voice and telepresence (new)
 AUDIO_DATA_telEPRESENCE 8 //Voice, telepresence, and data (new)
 AUDIO_AND_720P 10 // Voice and 720P HD video
 AUDIO_DATA_720P 11 // Voice and data and 720P HD video
 AUDIO_AND_1080P 12 // Voice and 1080P HD video
 AUDIO_DATA_1080P 13 // Voice and data and 1080P HD video

4.98 mediax-conference-information
This field is defined as below:
mediax-conference-information ::= SET
{

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 182

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

meeting-id [0] UTF8String OPTIONAL, //ID of a meeting

access-phone [1] UTF8String OPTIONAL, //An access phone number
meeting-frequency [2] meeting-frequency OPTIONAL, //Type of a meeting frequency
meeting-mode [3] meeting-mode OPTIONAL, //Mode of a meeting
Service-Mode [4] Service-Mode OPTIONAL, //Mode of a service
order-start-time [5] TimeStamp OPTIONAL, //Scheduled starting time
order-end-time [6] TimeStamp OPTIONAL, //Scheduled ending time
Order-party [7] INTEGER OPTIONAL, //Scheduled party number
media-type [8] MediaX-Type OPTIONAL,//Media type
modified-start-time [9] TimeStamp OPTIONAL, //Modified starting time of a meeting
modified-end-time [10] TimeStamp OPTIONAL,//Modified ending time of a meeting
modified-party [11] INTEGER OPTIONAL, //Modified party number
operation-time [12] TimeStamp OPTIONAL //Operation time
multiPic-Resource [13] INTEGER OPTIONAL //
adapter-Resource [14] INTEGER OPTIONAL //
bandwidth-Resource [15] INTEGER OPTIONAL //
videoPort-Resource [16] INTEGER OPTIONAL //
audioPort-Resource [17] INTEGER OPTIONAL //
modified-MultiPic-Resource [18] INTEGER OPTIONAL //
modified-Adapter-Resource [19] INTEGER OPTIONAL //
modified-Bandwidth-Resource[20] INTEGER OPTIONAL //
modified-VideoPort-Resource [21] INTEGER OPTIONAL //
modified-AudioPort-Resource[22] INTEGER OPTIONAL //
telepresence-party [23] INTEGER OPTIONAL //
modified-telepresence-party [24] INTEGER OPTIONAL //
created-time [25] TimeStamp OPTIONAL,//
closed-time [26] TimeStamp OPTIONAL,//
closed-code [27] Enumerated OPTIONAL //
current-party [28] INTEGER OPTIONAL //
current-data-party [29] INTEGER OPTIONAL //
current-data-party [30] INTEGER OPTIONAL //
}

4.99 mediax-terminal-information
mediax-terminal-information::= SET
{
terminal-type [0] terminal-type OPTIONAL //
screen-number [1] INTEGER OPTIONAL //
main-screen [2] UTF8String OPTIONAL//
main-screen-Entrance-Type [3] main-screen-Entrance-Type OPTIONAL //
}

4.100 mediax-user-information
This field specifies the user information in user-media interaction. It is defined as follows:
mediax-user-information ::= SET
{
pay-account [0] UTF8String OPTIONAL, //Account that pays
organization-id [1] UTF8String OPTIONAL, //ID of an organization (the unique ID of an
enterprise or a department)

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 183

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

user-id [2] UTF8String OPTIONAL,//ID of a user

call-id [3] UTF8String OPTIONAL,//ID of a meeting
port-type [4] port-type OPTIONAL, //Type of a port
end-code [5] end-code OPTIONAL //Ending code
group-id [6] UTF8String OPTIONAL//
}

4.101 meeting-frequency
This field specifies the type of the conference frequency.

4.102 meeting-id
This field specifies the conference ID.

4.103 meeting-mode
This field specifies the conference mode.

4.104 mMTelInformation
This field contains the specific fields in the MMTel related services.
This field is of type Group, containing the following sub-fields:
 subscriberRole
 listOfSupplService

4.105 modified-Adapter-Resource
This field specifies the adapter resource occupied by a modified conference.

4.106 modified-AudioPort-Resource
This field specifies the audio port used by a modified conference.

4.107 modified-Bandwidth-Resource
This field specifies the bandwidth resource occupied by a modified conference.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 184

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.108 multiPic-Resource
This field specifies the resources used by a multi-picture conference. If the conference is not a
multi-picture one, the value of this field is 0.

4.109 modified-MultiPic-Resource
This field specifies the resource occupied by a modified multi-picture conference.

4.110 modified-start-time
This field specifies the start time of a modified conference.

4.111 modified-end-time
This field specifies the end time of a modified conference.

4.112 modified-party
This field specifies the number of parties in a modified conference.

4.113 modified-telepresence-party
This field specifies the number of parties in a modified telepresence conference.

4.114 modified-Up-CascadePorts
This field specifies the number of modified up-cascade ports

4.115 modified-Down-CascadePorts
This field specifies the number of modified down-cascade ports.

4.116 modified-VideoPort-Resource
This field specifies the video port used by a modified conference.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 185

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.117 msc-number
This field specifies the MSC number of a subscriber. It is available only for mobile and ICS
subscribers. The field value depends on the roaming information of the subscriber obtained
from the HSS.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is set to the MSC number of a subscriber is contained.
 In a Centrex basic call, this field is not available.
 In a basic call of a North America subscriber, this field is not available.
 In an ICS basic call, the MSC number of a subscriber is contained in this field.
 In other services, this field is set to the MSC number of a subscriber.

4.118 nP-Data
This field holds the data information.

4.119 nP-Query
The field has the following means:
 When the value of the field is 0, it specifies the user calls other user with not NP query.
 When the value of the field is 1, it specifies the user calls other user with NP query.

4.120 np-Route-Number
This field contains the information about a subscriber's new number in the NP service. The
ATS9900 obtains the new number from the rn parameter contained in the Request-URI or P-
Charging-Vector header field in the SIP message. The new number is obtained from Request-
URI in preference.
The field is contained only in R6 and R7 versions. The NP rout information in R8 version is
contained in Number-Portability-Routing-Information.

4.121 nodeAddress
This field specifies the ID of the NE that provides CDRs. The value may be either the IP
address or the FQDN of the NE that generates charging information. The CCF assigns a
unique ID for each NE in the IMS domain.

4.122 numberOfDiversions
This field specifies the number of diversions related to a CDIV service. When the number of
diversions is counted, all types of diversion are included.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 186

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.123 numberOfParticipants
This field contains the number of current subscribers in a conference.

4.124 numberPortabilityRouting
This field is reserved for future expansion and is not in use at present.

4.125 onlineChargingFlag
It is the online charging flag and mandatory when both the online charging and offline
charging are deployed. If the online charging has performed for a service, the CDR does not
contain the offline charging.
This field is defined as follows:
 0: Offline_Charging
 1: Online_Charging
 2: ABNORMAL_ONLINE_SERVICE

4.126 onlineChargingType
This field specifies the type of online charging.

4.127 operation-time
This field specifies the duration of the operation by a conference administrator: It is recorded
in seconds starting from 1900 00:00 UTC.
It specifies the duration of scheduling a conference, modifying the scheduled conference, or
canceling the scheduled conference.

4.128 order-end-time
This field specifies the scheduled ending time.

4.129 order-party
This field specifies the scheduled party number.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 187

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.130 order-start-time
This field specifies the scheduled starting time.

4.131 origin-Callee-Party-Address
This field specifies the address of the original called party which forwards a call in the first
place. If the changed number has a higher priority, the address is the changed number.
The value of the field is empty for basic calls.
CDRs for the originating side for call forwarding services usually carry the number of the
party which forwards a call in the first place. If the changed number has a higher priority, the
address is the changed number. That is, when B forwards a call from A to C, the field shall be
filled with the number of B.
Typical scenarios for the ATS9900 are as follows:
 For a basic call, service party CDRs do not carry the number of the original called party.
 For a call forwarding service, service party CDRs carry the number of the original called
party.
 For a multi-ringing service, service party CDRs carry the number of the original called
party.
 For other services, service party CDRs do not carry the number of the original called
party.

4.132 originatingIOI
This field identifies the network that serves the calling party. It is recorded in Orig-IOI header
of the P-Charging-Vector header field in the SIP signaling transmission.

4.133 organization-id
This field specifies the ID of an organization (the unique ID of an enterprise or a department).

4.134 originator
This field specifies the party that provides the Answer during mediation negotiation.
If the calling party provides the Answer, the field is set to Calling Party. If the calling party
does not provide the Answer, the field is set to Called Party.

4.135 originator-sccp-address
This field specifies the GT code of the IP-SM-GW.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 188

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

Typical scenarios are as follows:

 For SMS service, this field is carried in an ACR [Event].
 For other services, this field is not carried.

4.136 osg-bill-indication
This field specifies whether the OSG downloads user CDRs from the CCF.
The value of this field can be obtained by querying the OSG download bill from ccf
parameter in the CXSUBGRP configuration based on the group number and sub-group
number of the subscriber.
This field is defined as follows:
 0: The OSG does not download CDRs.
 1: The OSG downloads CDRs.

4.137 participantActionType
This field specifies the participant’s action type during the conference for Billing Domain’s
information.
This field is defined as follows:
 0: CREATE_CONF
 1: JOIN_CONF
 2: INVITE_INTO_CONF
 3: QUIT_CONF

4.138 pay-account
This field specifies the payment account.

4.139 pbxaddress
This field specifies the PBX pilot number in SIP URI or tel URI format.
It is available only when the PBX service is triggered and the Send pilot number mode
parameter is set to SDPL by running the ADD PBX command.

4.140 pBX-Pilot-Number
This field specifies the PBX pilot number of the business trunk to which the subscribers
belong. This field is available only for calls made by business trunk subscribers and other
supplementary services.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 189

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.141 port-type
This field specifies the type of the port that a user uses:
 ACCESS_PORT 1 Access port
 CONFERENCE_PORT 2 Conference port
 FLEXIBLE_PORT 3 Flexible port
 COMMON_PORT 4 Common port
NOTE
When a conference is scheduled, the telepresence terminal is specified and the resource is measured.
Therefore, the telepresence terminal occupies no flexible resource.

4.142 privateNetworkIndication
This field specifies whether the subscriber is a Centrex subscriber or an individual subscriber.
It is set to the value of the Centrex User parameter defined by running the ADD SBR
command.

4.143 privateNumber
This field specifies the short number of the Centrex subscriber.
This field in an MOC CDR is set to the short number of the calling party, and this field in an
MTC CDR is set to the short number of the called party.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is not available.
 In a Centrex basic call, the field is set to the short number of the Centrex subscriber.
 In a basic call of a North America subscriber, this field is not available.
 In an ICS basic call, this field is not available.
 In other services, the field is set to the short number of the Centrex subscriber.

4.144 privateUserID
This field specifies the used network access ID of the served party according to the RFC2486
[405].

4.145 pstn-cdr-info
This field records the PSTN CDR information.
This field is specified only when Adapt NGN CDR in the RFPARAM command is set to
YES.
This group field consists of the following fields:

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 190

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

 calling-Local-DN-Set
 calling-Party-Number-Type
 called-Local-DN-Set
 called-Party-Number-Type
 calling-Party-Category
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is carried in the session ACR and event ACR.
 In a Centrex basic call, this field is carried in the session ACR and event ACR.
 In a basic call of a North America subscriber, this field is carried in the session ACR and
event ACR.
 In an ICS basic call, this field is carried in the session ACR and event ACR.
 In other services, this field is carried in the session ACR, but not in the event ACR.

4.146 private-MediaPartialRecordNumber
This field is used to identify the consecutive partial CDRs generated for the same media type
within a session when media switching occurs in the session.
For example, after media switching occurs in a session, the CCF generates partial CDRs for
the session as follows:
 Generating two partial CDRs for the first call (common audio).
 Generating two partial CDRs for the second call (video).
 Generating two partial CDRs for the third call (common audio).
 Generating a partial CDR for the last call (video).
Then the values of the private-MediaPartialRecordNumber field recorded in these partial
CDRs are 1, 1, 2, 2, 3, 3, and 4 (in sequence). The Mediation consolidates the partial CDRs
with the same values of the private-MediaPartialRecordNumber field into a final CDR and
thereby generates four final CDRs.
This field takes effect only when Interim CDR on media renegotiation in ADD CDRPROC
has been set to YES in the MML Command - CCF window of the OMU client.

4.147 private-User-Equipment-Info
This field is of type Grouped and carries the identity and capability of the terminal.
This field contains the following sub- fields:
{ User-Equipment-Info-Type }
{ User-Equipment-Info-Value }

4.148 private-User-Equipment-Info-Type
This field carries the information type of the User-Equipment-Info-Value.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 191

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.149 private-User-Equipment-Info-Value
This field carries terminal information. Current, it carries only the IMEI.

4.150 recordClosureTime
This field contains the time when the CDR consolidation ends. This field shows the time
when the CCF receives the last ACR in a session.

4.151 recordExtensions
This field is reserved for future expansion and is unavailable now.

4.152 recordExtensions-1
This field is reserved for future expansion and is not in use at present.

4.153 recordExtensions-2
This field is reserved for future expansion and is not in use at present.

4.154 recordOpeningTime
This field contains the time when the CDR consolidation starts. This field shows the time
when the CCF receives the first ACR in a session. At present, it is present only in a session.

4.155 recordSequenceNumber
This field is filled only when incomplete CDRs are to be generated. In the case of timeout or
other cases, the CCF may generate multiple partial CDRs for the same charging session. In
that case, the CCF allocates a record SN (starting with 1) to each partial CDR.
It helps the BS check whether a CDR is complete.

4.156 recordType
This field specifies the category of a CDR. A CDR is classified into a category based on
which NE generated the CDR. It is defined as follows:
recordType ::= INTEGER
{
sCSCFRecord (63), //S-CSCF CDR

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 192

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

pCSCFRecord (64), //P-CSCF CDR

iCSCFRecord (65), //I-CSCF CDR
mRFCRecord (66), //MRFC CDR
mGCFRecord (67), //MGCF CDR
bGCFRecord (68), //BGCF CDR
aTSRecord (69), //ATS9900 CDR
iBCFRecord (82), //IBCF CDR
vCCASRecord (201), //VCCAS CDR
vIDEOASRecord (202), //VIDEOAS CDR
aLUCTSRecord (203), //ALUCT CDR
mEDIAXRecord (204), //MediaX3600 CDR
aGCFRecord (205), //AGCF CDR
cONFERENCEASRecord (206) //CONFERENCEAS CDR
rCSRecord (252), //RCS NE CDR
sBCRecord (253) //SBC NE CDR
cENTREXASRecord (254) //CENTREX NE CDR
}

CDRs generated by the ATS9900 only use the value aTSRecord.

4.157 refer-To
This field contains the refer-To header field in a SIP session.

4.158 related-call-reference
This field associates CDRs of all sessions related to a specific service in three-party session,
conference, and ECT service. The value is the same in CDRs of all related calls. The value is
generated by the ATS9900 in the same manner as the ICID.

4.159 requested-Party-Address
This field indicates the original called number. It is contained in the Request-URI field of
requests received by the ATS9900.
If the called party has subscribed to the User Number Change service, this field is set to the
called number before change.

4.160 retransmission
This field specifies whether ACRs retransmitted by NEs are contained. This field is
mandatory when there is a retransmitted ACR. When the CDRs contain the retransmission
ACR, the field is mandatory. If this field is displayed in the CDR, ACRs retransmitted by NEs
are contained in this CDR. If this field is not displayed in the CDR, no ACRs retransmitted by
NEs is contained.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 193

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.161 restriction-Group-ID
This field contains the calling barring group number. The value of this field is the calling
barring group number in the user data.

4.162 ringing-Duration
This field specifies the ringing duration. It can be classified into two conditions:
 This field specifies the ring duration between the time when the ATS9900 receives a
ringing message (180 Ring) and the time when it receives a response message (200 OK).
 This field specifies the ring duration between the time when the ATS9900 receives a
ringing message (180 Ring) and the time when it receives an error message (0xx or
Cancel).

4.163 role-of-Node
This field specifies the role of the ATS9900. It is defined as follows:
 ORIGINATING_ROLE (0), //NE is on the originating side in this call
 TERMINATING_ROLE (1), //NE is on the terminating side in this call
 PROXY ROLE (2), //NE acts as an agent in this call
 B2BUA_ROLE (3), //NE is used for ordinary transparent
transmission in this call
 CALLFORWARD_ROLE (4), //NE trigger call forwarding service.
 ROAMING_ROLE (16) //NE provides roaming CDR when roaming
happens.
Typical scenarios for the ATS9900 are as follows:
 For a basic call, this field in MOC CDRs is set to ORIGINATING_ROLE and the field
in MTC CDRs is set to TERMINATING_ROLE.
 For a call forwarding service, if the CFXCFG object configuration sends the forwarding
identifier, the field in the service party CDRs is set to CALLFORWARD_ROLE.
 For other services, this field in MOC CDRs is set to ORIGINATING_ROLE and the
field in MTC CDRs is set to TERMINATING_ROLE.

4.164 rst-information
This field contains special information on additional RST services.
It is only contained in event CDRs of basic calls (including supplementary service and OXX
charging) in North America.
It contains the following sub-fields:
 server-Role
 session-Type

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 194

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

 rST-Subscriber-ID

4.165 rST-Subscriber-ID
This field specifies the number normalized by the service party.
It is only contained in event CDRs of basic calls (including supplementary service and OXX
charging) in North America.

4.166 s-CSCF-Information
This field is reserved for future expansion and is not in use at present.

4.167 screen-number
This field specifies the number of the screen. It includes single screen, three screens and so
on.

4.168 sDP-Media-Components
This field is of the group type and contains several sub-fields associated with one media
component. Because several media components may exist for a session in parallel, these sub-
fields may appear several times.
This field contains the following sub-fields:
 sDP-Media-Name
 sDP-Media-Descriptions
 gPRS-Charging-Id
 accessNetworkChargingIdentifier
 authorized-QoS

4.169 sDP-Media-Descriptions
This field indicates the contents of the attribute line (the a line) in the SDP.
Generally, This field is contained in the SDP carried in the Answer of a finished media
negotiation.

4.170 sDP-Media-Identifier
This field specifies the multimedia service ID.
 0: VoiceCall //Common voice calls.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 195

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

 1: VideoCall //Video calls.

 2: Fax //Fax.
 3: CDD //Data service.
 4: PABX //This field is reserved for future expansion and is not in use at present.
 5: Text

4.171 sDP-Media-Name
This field indicates the contents of the media line (the m line) in the SDP of a finished media
negotiation.

4.172 sDP-Session-Description
This field indicates all the contents before the attribute line (the m line) in the SDP (the SDP
of the calling party is contained in the originating ACR, and the SDP of the called party is
contained in the terminating ACR)..

4.173 sDP-Type
This field describes the SDP data in a session is the SDP Request or the SDP Answer.
It is defined as follows:
 0: sDP-offer
 1: sDP-answer

4.174 second-level-bill-group
This field specifies the second-level bill group number of the subscriber.
It is set to the value of the Second level bill group parameter defined by running the ADD
SBR command.

4.175 servedPartyIPAddress
This field specifies the IP address of the called party or the calling party. This field in an MOC
CDR is set to the IP address of the calling party, and this field in an MTC CDR is set to the IP
address of the called party.

4.176 server-Role
This field describes the services used by subscribers.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 196

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

It is only contained in event CDRs of basic calls (including supplementary service and OXX
charging) in North America.
It is defined as follows:

4.177 serverUserType
This field specifies the access type configured by the current service user.
The corresponding field value comes from the data when the subscriber is defined of a
subscriber, which is the Type and VCC Flag parameter in the ADD SBR command. In the
originating CDRs, the field is set to calling user type. In the MTC CDRs, the field is set to
called user type.
This field contains the following user types:
 0: IMS Subscriber
 1: PSTN Subscriber
 2: VCC Subscriber
 3: MOBILE Subscriber
 4: BRA Subscriber
 5: PRA Subscriber

4.178 serviceContextID
This field describes the ID of the party who provides the service in the session.

4.179 serviceDeliveryEndTimeStamp
This field specifies the time when an NE initiates the request to end the session, or when NE
sends stop CDRs. This field is usually filled with a time. Nevertheless, in event CDRs, the
value is set to Empty.

4.180 serviceDeliveryStartTimeStamp
This field specifies the time when an NE receives the answer after initiating the request to
start a session, or when NE sends start CDRs. NE usually sends start CDRs on receiving 200
OK.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 197

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.181 serviceId
This field is used to carry the conference address (Conference Focus URI) for conference
charging.

4.182 serviceIdentifier
This field specifies what types of services are used by a subscriber.
This field in an event CDR is set to the actual service identifier, filled with related events. For
example, if a subscriber cancels the CFU service by dialing the service access code, the field
is filled with CFU_CANCEL.
In CDRs for basic calls, this field in a session CDR is set in accordance with the value of
software parameter P1023. If the value of software parameter P1023 is 1, this field is set to
BASICCALL; otherwise, this field is set to the actual service identifier.
This field is available only in R6 and R7.
If the Rf interface is R8 version, the service usage information is contained in Supplementary-
Service.
The value of the field is an enumerated value. It is defined as follows:

4.183 service-indetity-list
This field is the supplementary service flag and mandatory when the user subscribes to a
supplementary service. This field specifies the supplementary service that is used in this
session. If multiple supplementary services are to be triggered in a session, multiple service-
indetity-list fields must be provided.
This field is empty for CDRs of basic calls.
This field is set to the value of the Service-Identity-List (field dedicated for China Mobile)
and Service-Identity-List-Ctel (field dedicated for China Telecom) field on the ATS9900. This
field is set to the value of the Service-Identifier when the following conditions are met:
 The software parameter Release of the Format Engine Package is set to CTEL.
 The Rf interface version parameter is set to Version R7 in the AP object.
 The Dynamic link library for merging CDRs parameter is set to IMS_R8 in the
PROCESSOR object.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is not available.
 In a Centrex basic call, this field is not available.
 In a basic call of a North America subscriber, this field is not available.
 In an ICS basic call, this field is not available.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 198

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

 For a call forwarding service, this field is set to the forwarding service ID.
 For a multi-ringing service, the field is set to the multi-ringing service ID.
 For a hookflash service, this field is set to the hookflash service ID.
 For a PBX service, this field is set to the PBX service ID.
 For a callback service, this field is set to the callback service ID.

4.184 service-mode
This field specifies the conference service modes as follows:
 CONFERENCE_SCHEDULE 2 //Scheduling conference mode
 SELF_MEETING 3 //Self conference mode
 GROUP_CALL 4 //Group conference mode
 FIXED_CALL 5 //Fixed conference mode
 CONFERENCE_INDIVIDUAL 6 //Public conference mode
 ALERT_CALL 7 //alert conference mode
 BROADCAST_CALL 8 // broadcast conference mode
 RECEPTION_CALL 9 // reception conference mode
 SUBCONFERENCE 10 // sub conference mode

4.185 serviceMode
This field indicates the service used by the subscriber. At present, it is available only for the
call forwarding, call barring, and hookflash services.
The ATS9900 supports the following services:
0-Communication Forwarding Unconditional (CFU)
1-Communication Forwarding Busy (CFB)
2-Communication Forwarding No Reply (CFNR)
3-Communication Forwarding Offline (CFNL)
4-Communication Deflection (CD)
5-Communication Forwarding on User Not Reachable (CFNRC)
6-Incoming Call Barring (ICB)
7-Outgoing Call Barring (OCB)
8-Anonymous Communication Rejection (ACR)
9-Blind Transfer
10-Consultative Transfer
11- Three-Party (3PTY)
12- Advice of Charge -S (AoC-S)

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 199

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

13- Advice of Charge -D (AoC-D)

14- Advice of Charge -E (AoC-E)

4.186 serviceRequestTimeStamp
This field specifies the time of SIP requests, namely, the time when the NE receives the
INVITE message.

4.187 serviceReasonReturnCode
This field specifies the reason why a service request succeeds or fails.
This field is defined as follows:
 Redirection -399~-300
 Final Response -299~-200
 End of REGISTER dialog -3
 End of SUBSCRIBE dialog -2
 Successful transaction -1
 Normal end of session 0
 Unspecified error 1
 Unsuccessful session setup 2
 Internal error 3
 Session timer timeout 4
 Request failure 400-499
 Server failure 500-599
 Global failure 600-699

4.188 serviceSpecificData
This field contains service-specific data if and as provided by an Application Server.
It is a service-related field. It records the specific data that users have in a session and is
provided by the ATS9900. This field identifies the original calling party. Only when the user
subscribes the call forwarding service, this field can be contained in the service party MOC
CDRs. The value of this field can be obtained from the PAI header field. The value of this
field is set to Empty in the CDRs of a basic call.
Typical scenario for the ATS9900 is as follows:
For a forwarded call, this field is set to the tel URI of the original calling party. For example,
if subscriber A calls subscriber B and the call is forwarded to subscriber C, then this field is
set to the tel URI of subscriber A. If subscriber A does not register a tel URI, then this field is
set to the SIP URI of the subscriber.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 200

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.189 serviceSpecificInfo
This field contains the data and type of the specific service that a subscriber uses in a session.
The value of this field is set to Empty in the CDRs of a basic call.
This field is of the group type, containing the following sub-fields:
 serviceSpecificData
 serviceSpecificType
When the Rf interface is of R6 version, the CDRs have a single field Service-Specific-Data
instead of this group field.

4.190 serviceSpecificType
This field contains the data and type of the specific service that a subscriber uses in a session.
The value of this field is set to Empty in the CDRs of a basic call.

4.191 service-type
This field contains the service identifier used by subscriber. Other services are indicated by
the value of the corresponding Service-Identifier field plus 5000, except for the basic call
service and the following values:
 0: "Originating Identification Presentation (OIP)",
 1: "Originating Identification Restriction (OIR)",
 2: "Terminating Identification Presentation (TIP)",
 3: "Terminating Identification Restriction (TIR)",
 4: "Communication HOLD (HOLD)",
 5: "Communications Barring (CB)",
 6: "Communication Diversion (CDIV)",
 7: "Communication Diversion Notification (CDIVN)",
 8: "Communication Waiting (CW)",
 9: "Message Waiting Indication (MWI)",
 10: "Conference (CONF)",
 11: "Flexible Alerting (FA)",
 12: "Completion of Communication to Busy Subscriber (CCBS)",
 13: "Completion of Communications on No Reply (CCNR)",
 14: "Malicious Communication Identification (MCID)",
 15: "Customized Alerting Tone (CAT)"
 19: "Advice of Charge (AoC) "

4.192 session-Id
This field specifies the SIP session ID, that is, the SIP CALL ID.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 201

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

Example: e105bd97bdeec079c65d458243f3f87e.

4.193 session-Priority
This field is the ID of an urgent call.

4.194 session-Type
This field identifies the session type. It is only contained in event CDRs of basic calls
(including supplementary service and OXX charging) in North America. It is defined as
follows:
 Activation 1, //CFX service activation or successful registration, or subscribers
use RID and NRID services
 De-activation 2, //Cancel CFX service, dial-back (CR)/redial (RD), or cancel the
subscription charge of the CCBS
 Session establishment 3, //Successfully use CFX service or disable call forwarding
 Subscribe 4, //Successful subscription
 Notify 5, //Reception of peer free notification or NOTIFY ACK timeout after
subscription of CCBS service
 Call Block 6, //The user triggers call restriction services and is restricted from
calling.
 Call Block Override 7,//Not in use for the moment
 Call Block Disabled 8, //Not in use for the moment
 Reference 9, //MCID service is used.
 Success 10, //Successful dial-back of CRRD service.
 Delay_Success 11, //Successful subscription of CRRD service
 Failure_Timeout 12, //The calling party is unavailable before timeout of the
subscription of CCBS service; timeout of the calling party's call attempts.
 Failure_SUBS_Limit 13, //Reception of unsuccessful response 480 for subscription
 Failure_Dialog 14, //Reception of error response 489 for subscription
 Failure_Identity 15, //Subscription failed
 CALL_VM_REDIRECTION 101, //Call forwarding to voice mailbox before temporary
suspension
 CARE_REDIRECTION 102, //OWN service is used.
 CALL_NOANSWER 103, //No answer from the subscriber
 CALL_BUSY 104, //The called party is busy.
 CALL_UNREACHABLE 105, //The called party cannot be reached.
 CALL_OFFLINE 106, //The called party has not registered.
 CALL_CANCEL 107, //The calling party hangs up before the called party answers
the call.
 INTERNAL_ERROR 199

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 202

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.195 short-number
This field specifies the short number of the Centrex subscriber.
This field in an MOC CDR is set to the short number of the calling party, and this field in an
MTC CDR is set to the short number of the called party.
This field is set to the value of the VPN-Call-Property field on the ATS9900 when the
following conditions are met:
 The software parameter Release of the Format Engine Package is set to CTEL.
 The Rf interface version parameter is set to Version R7 in the AP object.
 The Dynamic link library for merging CDRs parameter is set to IMS_R8 in the
PROCESSOR object.

4.196 sIP-Method
This field describes the cause of CDRs. It is set to BYE or CANCEL for normal CDRs. If
other values are presented, the CDR may be incomplete. Nevertheless, in event CDRs, this
field may be empty or INVITE.
This field is defined as follows:
 "INVITE" //This value is filled in start CDRs.
 "REINVITE" //This value occurs in the CDR sent during media renegotiation.
 "UPDATE" //This value occurs in the CDR sent during media update.
 "BYE" //This value occurs in stop CDR and is the normal value for common CDRs.
 "CANCEL" //This value only occurs in event CDRs.

4.197 sIP-Request-Timestamp
This field specifies when the SIP Request is initiated.

4.198 sIP-Request-Timestamp-Fraction
The field contains the time (milliseconds) corresponding to SIP-Request-Timestamp.

4.199 sIP-Response-Timestamp
This field specifies the time when the response to the SIP request is sent.

4.200 sIP-Response-Timestamp-Fraction
This field specifies the field that contains the time (milliseconds) corresponding to SIP-
Response-Timestamp.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 203

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.201 sms-information
This field carries the information about the SMS service. This group field consists of the
following fields:
 sms-node
 smsc-address
 originator-sccp-address
Typical scenarios are as follows:
 For SMS service, this field is carried in an ACR [Event].
 For other services, this field is not carried.

4.202 sms- node

This field carries the role of a SMS node. It contains the following values:
SMS Router, 0 //SMS Router
IP-SM-GW, 1 //IP-Short Message-Gateway
SMS Router and IP-SM-GW, 2 //SMS Router and IP-Short Message-Gateway
SMS-SC 3 //SMS-SC
Typical scenarios are as follows:
 For SMS service, this field is carried in an ACR [Event].
 For other services, this field is not carried.

4.203 SMS-Notify-Type
The conference control modes are as follows:
 NOT_SPECIFY 0 //Non-specified.
 SCHEDULE_CONF 1 //Schedule a conference.
 REMIND_CONF 2 //Conference reminder.
 CANCLE_CONF 3 //Cancel a conference.
 MODIFY_CONF 4 //Modify a conference.
 INVITE_FAIL 5 //Fail to invite a user to a conference.
 LEAVE_CONF 6 //Leave a conference.
 CREATE_USER 7 //Short message notification during creation of a user.
 INITIAL_PW 8 //Short message notification during initialization of the user
password.
 SEND_PW 9 //Send a password by short messages.
 GROUP_SMS 10 //Mass sending of short messages.
 CONF_RECORD 11 //

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 204

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.204 smsc-address
This field specifies the SMSC address.
Typical scenarios are as follows:
 For SMS service, this field is carried in an ACR [Event].
 For other services, this field is not carried.

4.205 subscriber-Identity
This field specifies the subscriber. This field is the identifier for user A who initiates a Click to
Dial (CTD) service either in SIP URL and tel URL mode. For the SIP MESSAGE mode, this
field is set to P-Asserted-Identify header in the message. For the WEB SERVICE, this field is
set to the uc number of the dialCall interface.

4.206 subgroup-id
This field specifies the subgroup ID to which the Centrex subscriber belongs.

4.207 sub-meetingID
This field specifies the ID of a sub-conference. The original conference ID attribute specifies
the ID of the main conference in cascaded conferences.

4.208 subscriberRole
This field specifies the role of the subscriber (originating party or terminating party) in
MMTel supplementary services.
It is defined as follows:
 0: ORIGINATING
 1: TERMINATING

4.209 subscriptionIDData
This field specifies the ID of the subscription of a specific service. The value is the URI of the
calling party, called party, or connection party.
If the NE is on the originating side, the field records the URI of the calling party.
If the NE is on the terminating side, the field records the URI of the called party.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 205

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.210 subscriptionIDType
This field describes the format of the ID carried by Subscription-Id. It is defined as follows:
 END_USER_E164 (0), //The ID uses E.164 format and meets the ITU-T E.164 ID
planning standard. For example, MSISDN number.
 END_USER_IMSI (1), //The ID uses IMSI format and meets the ITU-T E.212 ID
planning standard.
 END_USER_SIP_URI (2), //The ID uses SIP format defined by RFC 3261 of SIP
protocol.
 END_USER_NAI (3), //The ID uses NAI format defined by RFC 2486.
 END_USER_PRIVATE (4), //Private ID of the subscriber.
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is not available.
 In a Centrex basic call, this field is not available.
 In a basic call of a North America subscriber, this field is not available.
 In an ICS basic call, the field is set to END_USER_IMSI.
 In other basic calls, the field is set to END_USER_IMSI.

4.211 supplementary-Service-Info
This field specifies the information about the MMTel supplementary service.
This field is of the group type, containing the following sub-fields:
 serviceType
 serviceMode
 numberOfDiversions
 associated-Party-Address
 serviceID
 changeTime
 numberOfParticipants
 participantActionType

4.212 Segment-Id
This AVP contains the identification of the subscriber's segment (e.g. prepaid or postpaid).
The following values are defined:
0 ：prepaid
1 ：postpaid
3 ：pre active
9 ：online postpaid

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 206

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.213 target
This field contains the target header field in a SIP session.

4.214 tariffPulses
This field specifies the number of the charging pulses to be sent in a call with pulse-based
charging service. It is used only in pulse-based charging, PAYPHONE, and AOC services.
In CDRs of pulse-based charging service for the called party, this field is always set to 0.
If the subscriber does not use the pulse-based charging, PAYPHOHE, or AOC service, this
field is always set to 0.

4.215 telepresence-party
This field specifies the number of participants in the current telepresence conference.

4.216 terminatingIOI
This field specifies the ID of a terminating network.
In the SIP signaling, the field is recorded in the Term-IOI header of the P-Charging-Vector
header field.

4.217 terminal-type
This field specifies the terminal type.

4.218 tADS-Indication
This field indicates that a VoLTE call is routed to the CS domain after the Terminating Access
Domain Selection (T-ADS) is performed. In such a call, both the terminating ATS9900 and
the vMSC on the CS domain generate CDRs. This AVP is added to the CDRs generated by the
terminating ATS9900 to prevent repeated charging.
It is defined as follows:
TADS-Indication ::= ENUMERATED
{
cS (0)
}

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 207

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.219 trunkGroupID(Incoming/Outgoing)
This field specifies the outgoing trunk or incoming trunk obtained from the ACR. For an
originating-party CDR, if the outgoing trunk of its corresponding ACR is available, the value
of this field is the outgoing trunk; otherwise, the value is the incoming trunk. For a
terminating-party CDR, if the incoming trunk of its corresponding ACR is available, the value
of this field is the incoming trunk; otherwise, the value is the outgoing trunk.

4.220 up-CascadePorts
This field specifies the number of up-cascade ports in a cascaded-conference CDR.

4.221 user-id
This field specifies the access network ID of the service section in IETF RFC 2486 [405].

4.222 user-sip-uri
This field identifies the user SIP URI.

4.223 user-Agent-Value
This field is used to carry the User-Agent header field value of the INVITE message received
from the originating side.

4.224 videoPort-Resource
This field specifies the video port used by a conference.

4.225 visited-network-id
This field specifies the ID of a network visited by subscribers.

4.226 vlr-number
This field specifies the VLR number of the subscriber. It is available only for mobile.
The field value is derived from the roaming information about the subscriber obtained from
the HSS.
Typical scenarios for the ATS9900 are as follows:

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 208

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

 In a basic call, it is available only for mobile and this field is set to the MSC number of a
subscriber.
 In a Centrex basic call, this field is not available.
 In a basic call of a North America subscriber, this field is not available.
 In an ICS basic call, this field is not available.
 In other calls, it is available only for mobile and this field is set to the MSC number of a
subscriber.

4.227 vmsc-id
This field is reserved for future expansion and is not in use at present.

4.228 vPNCallProperty
This field specifies whether this call is an inter-group call. The options are as follows:
 0: ONNET (intra-group). A subscriber dials the number of other subscriber in the same
group.
 1: OFFNET (inter-group). A subscriber calls another one outside the group.
 2: VIRTUAL-ONNET (WAN group). The call initiated by subscribers contains an access
code of the WAC group.
 3: FORCED-ONNET (subscriber numbers dialed within the group)
 4: EMERGENCY-OFFNET (emergency inter-group calls).
Typical scenarios for the ATS9900 are as follows:
 In a basic call, this field is not available.
 In a Centrex basic call, the field is set to inter-group call types of the Centrex subscriber.
 In a basic call of a North America subscriber, this field is not available.
 In an ICS basic call, this field is not available.
 In other services, the field is set to inter-group call types of the Centrex subscriber.

4.229 user-Category
This field specifies the user category.
USER-UC 1 //UC user
USER-M-MEETING 2 //M-meeting user
USER-ROOM 3 //room user
USER-UNDEFINED 256 //undefined user

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 209

Copyright © Huawei Technologies Co.,
Ltd.
HUAWEI iCG9815 IMS Charging Gateway
CCF CDR Formats 5 Description of CDR Fields

4.230 list-Of-Logic-Resource
This group field consists of the following fields:
[Port-Media-Type]
[Port-Count]

4.231 port-Media-Type
This field specifies the port media type.
PORT-AUDIO 1 //audio port
PORT-SD-VIDEO 2 //SD video port
PORT-HD-VIDEO-2M 3 //HD video port 2Mbps(720p)
PORT-HD-VIDEO-4M 4 // HD video port 4Mbps(1080p)

4.232 port-Count
This field specifies the port count.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 210

5 Cases

How the Mediation Merges the CCF Partial CDRs

If the call duration is longer than the timeout duration set by the BC, the CCF merges all
received ACRs and generates one partial CDR. Consequently, several partial CDRs are
generated in one conversation for charging by the Mediation. The Mediation merges partial
CDRs generated by the CCF based on the following methods:
Step 1 The Mediation checks whether the recordSequenceNumber field is encoded. If not, this CDR
is a complete CDR and Mediation does not need to merge it any more.

NOTE
Most CDRs are complete.

If yes, this CDR is a partial CDR. For details about the recordSequenceNumber field, see
section 4.155 recordSequenceNumber.

NOTE
If RSNIncreaseType in the format engine package is set to 1, the RSN of the partial CDR that contains
Stop ACR is 0. In this case, this method is not applicable.

Step 2 For the partial CDR, the Mediation obtains the value of the iMS-Charging-Identifier field to
determine the conversation the partial CDR belongs to. Then the Mediation obtains all CDRs
that belong to this conversation. For details about the iMS-Charging-Identifier field, see
section 4.74 iMS-Charging-Identifier.
Step 3 Sort the CDRs according to the value of the recordSequenceNumber field. For example, the
CDR with the recordSequenceNumber field set to 1 is the first CDR. If the value is 2, the
CDR is the second CDR, and so on.
Step 4 Check the value of the incomplete-CDR-Indication field in the last partial CDRs which is
confirmed in last step to determine whether these patial CDRs can be merged to one complete
conversation. If the aCRStopLost sub-field of the incomplete-CDR-Indication field his set to
FALSE, this CDR is the last CDR in this conversation. Merge all partial CDRs into one
complete CDR. For details about the incomplete-CDR-Indication field, see section 4.76
incomplete-CDR-Indication.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 211

Figure 5-1 Partial CDR merge flowchart

----End

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 212

6 ASN.1-Based CDR Description Files

The CDR description files are based on ASN.1 (Basic Encoding Rules) and used by IMS
products, particularly by the CCF in encoding. The CCF will provide the encoded CDRs to
the billing center. For more information about ASN.1-based CDR description files, see the
IMS_R8.asn file in the same folder of this document.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 213

7 CDR Samples

Obtain CDR samples from the attachments.

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 214

8 Abbreviation

3GPP The 3rd Generation Partnership Project

A
ABNF Augmented Backus-Naur Form
ACA Accounting Answer
ACR Accounting Request
AS Application Server
ATS Advance Telephony Server
ASN.1 Abstract Syntax Notation One
B
BER Base Encode Rule
BS Billing System
C
CCF Charging Collection Function
CDF Charging Data Function
CDR Charging Data Record
Centrex-AS Centrex Application Server
CGF Charging Gateway Function
CSCF Call Session Control Function
CTF Charging Trigger Function
D
DOPRA Distributed Object-oriented Programmable Realtime Architecture
F
FTP File Transfer Protocol

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 215

G
GCID GPRS Charging Identifier
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service System
H
HSS Home Subscriber Server
I
iCG IMS Charging Gateway
ICID IMS Charging Identifier
I-CSCF Interrogating-CSCF
ID IDentification/IDentity
IMPU IP Multimedia Public Identity
IMS IP Multimedia Subsystem
IMSI International Mobile Station Identification Code
IOI Interoperator Identifier
IP Internet Protocol
L
LRN Location Routing Number
M
MGCF Media Gateway Control Function
MLPP Multi Level Precedence and Preemption
MO Mobile Origination
MRFC Multimedia Resource Function Controller
MSC Mobile Switching Center
MT Mobile Termination
N
NE Network Element
O
OS Operational System
P
P-CSCF Proxy-CSCF
R
RFC Request For Comments

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 216

S
SDP Session Description Protocol
S-CSCF Serving CSCF
SIP Session Initiation Protocol
U
URI Uniform Resource Identification
URL Uniform Resource Location
V
VCC Virtual Channel Connection

Issue 01 (2013-11-25) Huawei Proprietary and Confidential 217

RCEM 2.2 Ag Latest PDF
No ratings yet
RCEM 2.2 Ag Latest PDF
222 pages
Technical White Paper For Huawei SPS Signaling Accounting
No ratings yet
Technical White Paper For Huawei SPS Signaling Accounting
31 pages
Alaris Sms Platform 3.5.25
No ratings yet
Alaris Sms Platform 3.5.25
708 pages
Docmine: Spare Parts Catalog
No ratings yet
Docmine: Spare Parts Catalog
83 pages
ZXUN USPP Theoretical Basic-Interface Protocol-Interfaces and Services
No ratings yet
ZXUN USPP Theoretical Basic-Interface Protocol-Interfaces and Services
61 pages
SMSC Competitive Overview 08
100% (1)
SMSC Competitive Overview 08
31 pages
ATS9900 Ro Interface Specifications
No ratings yet
ATS9900 Ro Interface Specifications
69 pages
Internal Structure of A Leaf
50% (2)
Internal Structure of A Leaf
25 pages
Huawei SPS Convergent Solution For IPSTP and DA v1.0
No ratings yet
Huawei SPS Convergent Solution For IPSTP and DA v1.0
53 pages
SMSC SMPP Server-Client
No ratings yet
SMSC SMPP Server-Client
8 pages
Presentation of 3GPP Charging Management-Sep 2004
No ratings yet
Presentation of 3GPP Charging Management-Sep 2004
46 pages
Online Charging Description Document (FMC) : HUAWEI ATS9900 Advanced Telephony Server V100R006C10SPC200
100% (1)
Online Charging Description Document (FMC) : HUAWEI ATS9900 Advanced Telephony Server V100R006C10SPC200
94 pages
Handbook of Chemical Engineering Calculations, Third Edition. Nicholas P. Chopey
No ratings yet
Handbook of Chemical Engineering Calculations, Third Edition. Nicholas P. Chopey
3 pages
Huawei VTR PCRF Function Requirement Specification 20120118
No ratings yet
Huawei VTR PCRF Function Requirement Specification 20120118
51 pages
910-6854-001 Rev B PDF
No ratings yet
910-6854-001 Rev B PDF
22 pages
Prepared By: Rady Abdelwahed
67% (3)
Prepared By: Rady Abdelwahed
168 pages
Cellusys Portfolio
No ratings yet
Cellusys Portfolio
8 pages
1 - Cloud Computing Basics
No ratings yet
1 - Cloud Computing Basics
63 pages
PRS Product Description
No ratings yet
PRS Product Description
36 pages
Cisco NX-OS Software Architecture
100% (1)
Cisco NX-OS Software Architecture
69 pages
Topeng Mediation Product DescriptionV2
No ratings yet
Topeng Mediation Product DescriptionV2
22 pages
Charging System (CS) 16 System Administration: Exercises
No ratings yet
Charging System (CS) 16 System Administration: Exercises
54 pages
Gsma PRD FF.09
No ratings yet
Gsma PRD FF.09
35 pages
GGSN CDR Filed Description
No ratings yet
GGSN CDR Filed Description
20 pages
Cisco Asr 9000 Diameter Support in BNG
No ratings yet
Cisco Asr 9000 Diameter Support in BNG
26 pages
2015CustomerTrainingCatalog CourseDescriptions (CN USC)
No ratings yet
2015CustomerTrainingCatalog CourseDescriptions (CN USC)
56 pages
Lecture4 v3
No ratings yet
Lecture4 v3
49 pages
R360-Installation Guide PDF
No ratings yet
R360-Installation Guide PDF
172 pages
Advoss Aaa Product Datasheet
No ratings yet
Advoss Aaa Product Datasheet
26 pages
SMSC
No ratings yet
SMSC
12 pages
En NEON-dX DataFoundationGuide V6.1.5
No ratings yet
En NEON-dX DataFoundationGuide V6.1.5
96 pages
OAX000200 SoftX3000 Data Configuration For h.323 Sip Terminal ISSUE2.0-20041018-A
No ratings yet
OAX000200 SoftX3000 Data Configuration For h.323 Sip Terminal ISSUE2.0-20041018-A
21 pages
SMSGW & SMSC PDF
100% (1)
SMSGW & SMSC PDF
24 pages
ICC2008 LBSfor Mobilessimplified R2
No ratings yet
ICC2008 LBSfor Mobilessimplified R2
123 pages
3g Umts Terminating Callssssss
No ratings yet
3g Umts Terminating Callssssss
27 pages
Traffic Analysis of A Short Message Service Network: January 2010
No ratings yet
Traffic Analysis of A Short Message Service Network: January 2010
5 pages
SIP IMS Specifications For Dummies v7.4
100% (1)
SIP IMS Specifications For Dummies v7.4
71 pages
SMS Firewall
No ratings yet
SMS Firewall
5 pages
Huawei Csoftx3000
100% (1)
Huawei Csoftx3000
44 pages
ER00743-V-1900-CE-PDF Mobile Gateway Product Overview
No ratings yet
ER00743-V-1900-CE-PDF Mobile Gateway Product Overview
69 pages
Valid 8 SIP Conformance Solution PDF
No ratings yet
Valid 8 SIP Conformance Solution PDF
9 pages
InfoX SMS V300R002 System Description
100% (2)
InfoX SMS V300R002 System Description
102 pages
Moog Valves DIVelectricalInterfaces Manual
No ratings yet
Moog Valves DIVelectricalInterfaces Manual
108 pages
ZXIN10 SACP IMP Platform Installation Guide
No ratings yet
ZXIN10 SACP IMP Platform Installation Guide
55 pages
SMS Firewall PDF
No ratings yet
SMS Firewall PDF
5 pages
Ranap Release Cause
0% (1)
Ranap Release Cause
397 pages
Enterprise Deployment Guide IOS
No ratings yet
Enterprise Deployment Guide IOS
90 pages
TACACS Advantages
No ratings yet
TACACS Advantages
6 pages
BT Cloud Voice Customer Firewall and Lan Guide
No ratings yet
BT Cloud Voice Customer Firewall and Lan Guide
3 pages
CS SIP Trunk T Mobile Czech v40815
No ratings yet
CS SIP Trunk T Mobile Czech v40815
1 page
GSM Inter MSC Handover Subscriber MSC Interactions
No ratings yet
GSM Inter MSC Handover Subscriber MSC Interactions
1 page
SIP, NAT, and Firewalls: Master's Thesis by Fredrik Thernelius
No ratings yet
SIP, NAT, and Firewalls: Master's Thesis by Fredrik Thernelius
69 pages
Specification: Short Message Service Centre External Machine Interface
No ratings yet
Specification: Short Message Service Centre External Machine Interface
68 pages
A2PSMSC 21270.v.2.0 Web
No ratings yet
A2PSMSC 21270.v.2.0 Web
4 pages
Monetizing Mobile Data:: Top 10 Pricing and Charging Innovations
No ratings yet
Monetizing Mobile Data:: Top 10 Pricing and Charging Innovations
9 pages
MOP - GGSN Huawei Configure QCI-DSCP Mapping v3
No ratings yet
MOP - GGSN Huawei Configure QCI-DSCP Mapping v3
6 pages
Asn.1 CDR - Formats
No ratings yet
Asn.1 CDR - Formats
477 pages
MSOFTX3000 V200R010C20 ASN.1 CDR Description
No ratings yet
MSOFTX3000 V200R010C20 ASN.1 CDR Description
259 pages
Deep and Surface Learning PDF
No ratings yet
Deep and Surface Learning PDF
1 page
UMTS CS Protocols and Signaling Analysis
100% (1)
UMTS CS Protocols and Signaling Analysis
446 pages
01-Chapter 1 H.248
67% (3)
01-Chapter 1 H.248
22 pages
SCP Service Control Point 032010 en
No ratings yet
SCP Service Control Point 032010 en
4 pages
SPS V300R007C10 Part II Operation Guide (Special)
No ratings yet
SPS V300R007C10 Part II Operation Guide (Special)
63 pages
Alternative Routes To Monoethylene Glycol (MEG) : Section
No ratings yet
Alternative Routes To Monoethylene Glycol (MEG) : Section
11 pages
AC2 Engineering Utilities 2 Syllabus
No ratings yet
AC2 Engineering Utilities 2 Syllabus
16 pages
19 20 Solution Kernel SIM OTA
No ratings yet
19 20 Solution Kernel SIM OTA
2 pages
Jurnal Manajemen Strategi Agribisnis Jessica Halaman 74 - 87
No ratings yet
Jurnal Manajemen Strategi Agribisnis Jessica Halaman 74 - 87
46 pages
Location Update GSM
No ratings yet
Location Update GSM
120 pages
Plucker and Callahan 2014
No ratings yet
Plucker and Callahan 2014
17 pages
Analog Electronic Circuits Lab Manual
No ratings yet
Analog Electronic Circuits Lab Manual
99 pages
01-14 Sip
100% (1)
01-14 Sip
20 pages
SPS V300R007C10 Part III Appendix
No ratings yet
SPS V300R007C10 Part III Appendix
7 pages
Affected Models: Date: November, 2006 No. 2006-06 (W) MODELS: 2007 Evinrude SUBJECT: Engine Software Update
No ratings yet
Affected Models: Date: November, 2006 No. 2006-06 (W) MODELS: 2007 Evinrude SUBJECT: Engine Software Update
2 pages
Unit 2 Principles of Assessm Ent in Instructional Decision
No ratings yet
Unit 2 Principles of Assessm Ent in Instructional Decision
11 pages
2 5348041922055258424
No ratings yet
2 5348041922055258424
26 pages
Creativity Is Always A Social Process
No ratings yet
Creativity Is Always A Social Process
17 pages
ATS9900 V100R006C00 Feature List FT
No ratings yet
ATS9900 V100R006C00 Feature List FT
14 pages
Project Management: - Dr. Gyanesh Kumar Sinha Associate Professor - Operations and Analytics
No ratings yet
Project Management: - Dr. Gyanesh Kumar Sinha Associate Professor - Operations and Analytics
10 pages
Mil H 6875H
No ratings yet
Mil H 6875H
29 pages
HUAWEI UGW9811 Unified Gateway V900R010C00 Feature Description (EPSN Optional Feature)
No ratings yet
HUAWEI UGW9811 Unified Gateway V900R010C00 Feature Description (EPSN Optional Feature)
21 pages
Understanding Color and Color Schemes
No ratings yet
Understanding Color and Color Schemes
20 pages
HUAWEI UGW9811 Unified Gateway V900R010C00 Feature Description (GUL Optional Feature)
No ratings yet
HUAWEI UGW9811 Unified Gateway V900R010C00 Feature Description (GUL Optional Feature)
190 pages
Forward and Inverse Modeling of Gravity Data
No ratings yet
Forward and Inverse Modeling of Gravity Data
14 pages
Sheets, Preset Names and Formatting Descriptions For Different Elements (Such As "Chapter Title" or
No ratings yet
Sheets, Preset Names and Formatting Descriptions For Different Elements (Such As "Chapter Title" or
2 pages
A Simple Proof of Bernoulli's Inequality: Sanjeev Saxena
No ratings yet
A Simple Proof of Bernoulli's Inequality: Sanjeev Saxena
2 pages
MRP6600 V100R005C01 Feature Description
No ratings yet
MRP6600 V100R005C01 Feature Description
206 pages
School Students' Physical Activity Physical Activity and Its Contributing Factors in
No ratings yet
School Students' Physical Activity Physical Activity and Its Contributing Factors in
8 pages
Kihlstrom GeneralPsych Sum12 Syllabus
No ratings yet
Kihlstrom GeneralPsych Sum12 Syllabus
12 pages
Ed Ruscha's One Way Street
No ratings yet
Ed Ruscha's One Way Street
16 pages
Foot-Surface-Structure Analysis Using A Smartphone-Based 3D Foot Scanner
No ratings yet
Foot-Surface-Structure Analysis Using A Smartphone-Based 3D Foot Scanner
7 pages
ADP-233600-019 R1 MS of Air Curtain (A)
No ratings yet
ADP-233600-019 R1 MS of Air Curtain (A)
24 pages
Mains Voltage Compensation
No ratings yet
Mains Voltage Compensation
6 pages
Planning Engineer
No ratings yet
Planning Engineer
2 pages
BQ1031 Exercises
No ratings yet
BQ1031 Exercises
90 pages
MAQ TNC AC Test
No ratings yet
MAQ TNC AC Test
1 page
Physics Grade 9 Worksheet I Second Sem
No ratings yet
Physics Grade 9 Worksheet I Second Sem
11 pages
Blockchain Technology for Paperless Trade Facilitation in Maldives
From Everand
Blockchain Technology for Paperless Trade Facilitation in Maldives
Asian Development Bank
No ratings yet
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)
IP Multimedia Subsystem IMS A Complete Guide
From Everand
IP Multimedia Subsystem IMS A Complete Guide
Gerardus Blokdyk
No ratings yet
Online charging system Second Edition
From Everand
Online charging system Second Edition
Gerardus Blokdyk
No ratings yet
Network performance Third Edition
From Everand
Network performance Third Edition
Gerardus Blokdyk
No ratings yet
Revenue Assurance Complete Self-Assessment Guide
From Everand
Revenue Assurance Complete Self-Assessment Guide
Gerardus Blokdyk
No ratings yet

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.