0% found this document useful (0 votes)

480 views

ATS9900 Ro Interface Specifications

Uploaded by

aranibarm

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

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

480 views

ATS9900 Ro Interface Specifications

Uploaded by

aranibarm

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

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 69

ATS9900

V100R005C02
Ro Interface Specifications

Issue

Date 2012-11-30

PUBLIC

HUAWEI TECHNOLOGIES CO., LTD.

Copyright @ Huawei Technologies Co., Ltd. 2011. 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 the 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: [email protected]

Issue (2012-11-30) Huawei Proprietary and Confidential i

About This Document

Author
Prepared by Qin Kaiyong Date 2009-4-7

Reviewed by Date
Approved by Date

Authorized by Date

Change History
Date Revision CR ID Section Change Description Author
Version / Number
Defect
ID
2009-4-7 1.00 First draft Qin Kaiyong
(ID:56306)
2009-09-18 1.10 Added new AVPs, removed some AVPs Wei Yinghua
that the ATS does not use, and modified the (00111487)
description of some AVPs.

Issue (2012-11-30) Huawei Proprietary and Confidential ii

2010-7-2 1.11 A new AVP [VPN-Call-property] was Sun Ming

added. (00151555)
2010-8-28 1.12 Add new AVPs: Song Yuan
Private-Network-Indication, Group-ID, (00129716)
Subgroup-ID,
Private-Number,PBX-Address
2010-10-18 1.13 Correction of Diversion-Reason Chen Wukun
(00108076)
2010-11-2 1.14 Add new AVPS: Qin Shuang
Service-Identity-List_CTEL (00048083)

2011-2-26 1.15 refresh data for IMS 8.2 Wei Yinghua

(00111487)
2011-5-10 1.16 Remove Origin-State-Id AVP Wei Yinghua
(00111487)
2011-8-31 1.17 Add AVP [Currency-Code] to Liu Yan
AVP [Aoc-Information] (42144)
2012-11-5 1.18 Add new AVPs: Liu Shenglin
Call-Property, Called-Asserted-Identity, (00131882)
Number-Portability-Routing-Information,
Ringing-Duration, Abnormal-Finish-Info,
Abnormal-Finish-Reason,
Abnormal-Finish-Warning,
Carrier-Select-Routing-Information

2013-7-8 1.19 Add new AVP: Huangkai

Session-Priority (48270)

Issue (2012-11-30) Huawei Proprietary and Confidential iii

Contents

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

1 Standard Reference Files ............................................................................................................. 1
2 Definitions Symbols and Acronyms ......................................................................................... 2
2.1 Definitions ........................................................................................................................................................ 2
2.2 Symbols and Acronyms .................................................................................................................................... 3

3 Protocol Architecture .................................................................................................................... 5

3.1 Protocol Format ................................................................................................................................................ 5
3.1.1 Message Head Format ............................................................................................................................. 5
3.1.2 Message List ........................................................................................................................................... 7
3.1.3 AVP Head Format ................................................................................................................................... 7
3.1.4 AVP Data Formats ................................................................................................................................... 8

4 Interface Description .................................................................................................................. 11

4.1 ATS+OCS Charging Framework .................................................................................................................... 11
4.2 Entity Functions ............................................................................................................................................. 11
4.3 Interworking Requirements ............................................................................................................................ 12

5 Interface Definition .................................................................................................................... 13

5.1 Message Definition ........................................................................................................................................ 13
5.2 Credit-Control-Request (CCR)....................................................................................................................... 13
5.3 Credit-Control-Answer (CCA) ....................................................................................................................... 16
5.3.2 Re-Auth-Request (RAR) ....................................................................................................................... 18
5.3.3 Re-Auth-Answer (RAA) ....................................................................................................................... 19
5.3.4 Abort-Session-Request (ASR) .............................................................................................................. 19
5.3.5 Abort-Session-Answer (ASA) ............................................................................................................... 19
5.4 AVP Definition ............................................................................................................................................... 20
5.4.1 Access-Network-Information ................................................................................................................ 20
5.4.2 Accumulated-Cost ................................................................................................................................. 20
5.4.3 Aoc-Confirmation ................................................................................................................................. 21
5.4.4 Aoc-Cost-Information ........................................................................................................................... 21
5.4.5 Aoc-Information .................................................................................................................................... 22
5.4.6 Aoc-Price .............................................................................................................................................. 22
5.4.7 Aoc-Start-Time ...................................................................................................................................... 22

Issue (2012-11-30) Huawei Proprietary and Confidential iv

5.4.8 Aoc-Tariff .............................................................................................................................................. 23

5.4.9 Aoc-Tariff-Information ......................................................................................................................... 23
5.4.10 Aoc-Unit .............................................................................................................................................. 24
5.4.11 Auth-Application-Id ............................................................................................................................ 24
5.4.12 Called-Party-Address .......................................................................................................................... 25
5.4.13 Calling-Party-Address ......................................................................................................................... 26
5.4.14 CC-Request-Number ........................................................................................................................... 26
5.4.15 CC-Request-Type ................................................................................................................................ 27
5.4.16 CC-Time.............................................................................................................................................. 27
5.4.17 CC-Total-Octets .................................................................................................................................. 28
5.4.18 Content-Disposition ............................................................................................................................ 28
5.4.19 Content-Length ................................................................................................................................... 28
5.4.20 Content-Type....................................................................................................................................... 29
5.4.21 Cost-Information ................................................................................................................................. 29
5.4.22 Cost-Value ........................................................................................................................................... 30
5.4.23 Currency-Code .................................................................................................................................... 30
5.4.24 Destination-Host ................................................................................................................................. 30
5.4.25 Destination-Realm .............................................................................................................................. 31
5.4.26 Dialed-Party-Address .......................................................................................................................... 32
5.4.27 Diversion-Count .................................................................................................................................. 32
5.4.28 Diversion-Reason ................................................................................................................................ 33
5.4.29 Event-Timestamp ................................................................................................................................ 34
5.4.30 Exponent ............................................................................................................................................. 34
5.4.31 Event-Type .......................................................................................................................................... 34
5.4.32 Final-Unit-Action ................................................................................................................................ 35
5.4.33 Final-Unit-Indication .......................................................................................................................... 35
5.4.34 Granted-Service-Unit .......................................................................................................................... 36
5.4.35 Group-ID ............................................................................................................................................. 36
5.4.36 Message-Body..................................................................................................................................... 37
5.4.37 Multiple-Services-Credit-Control ....................................................................................................... 37
5.4.38 Multiple-Services-Indicator ................................................................................................................ 38
5.4.39 Node-Functionality ............................................................................................................................. 38
5.4.40 Origin-Host ......................................................................................................................................... 39
5.4.41 Origin-Realm ...................................................................................................................................... 40
5.4.42 PBX-Address ...................................................................................................................................... 40
5.4.43 Private-Network-Indication ................................................................................................................ 40
5.4.44 Private-Number ................................................................................................................................... 40
5.4.45 Rating-Element ................................................................................................................................... 41
5.4.46 Re-Auth-Request-Type ....................................................................................................................... 41
5.4.47 Requested-Party-Address .................................................................................................................... 42
5.4.48 Requested-Service-Unit ...................................................................................................................... 42
5.4.49 Reporting-Reason ............................................................................................................................... 43

Issue (2012-11-30) Huawei Proprietary and Confidential v

5.4.50 Result-Code......................................................................................................................................... 43
5.4.51 Role-of-Node ...................................................................................................................................... 44
5.4.52 Scale-Factor ........................................................................................................................................ 44
5.4.53 Service-Context-Id .............................................................................................................................. 45
5.4.54 Session-Id ............................................................................................................................................ 45
5.4.55 Service-Identifier ................................................................................................................................ 46
5.4.56 Service-Identity-List_CTEL ............................................................................................................... 46
5.4.57 Service-Information ............................................................................................................................ 46
5.4.58 SDP-Media-component ....................................................................................................................... 47
5.4.59 SDP-Session-Description .................................................................................................................... 47
5.4.60 SIP-Method ......................................................................................................................................... 47
5.4.61 SIP-Request-Timestamp ..................................................................................................................... 48
5.4.62 SIP-Response-Timestamp ................................................................................................................... 48
5.4.63 SDP-Media-Identifier.......................................................................................................................... 49
5.4.64 Subgroup-ID ....................................................................................................................................... 49
5.4.65 Subscription-ID ................................................................................................................................... 50
5.4.66 Subscription-Id-Type .......................................................................................................................... 50
5.4.67 Subscription-Id-Data ........................................................................................................................... 51
5.4.68 Termination-Cause .............................................................................................................................. 51
5.4.69 Time-Stamps ....................................................................................................................................... 52
5.4.70 Unit-Value ........................................................................................................................................... 52
5.4.71 Unit-Threshold .................................................................................................................................... 52
5.4.72 Used-Service-Unit ............................................................................................................................... 53
5.4.73 User-Session-Id ................................................................................................................................... 53
5.4.74 Value-Digits ........................................................................................................................................ 54
5.4.75 VPN-Call-property .............................................................................................................................. 54
5.4.76 Call-Property ....................................................................................................................................... 54
5.4.77 Called-Asserted-Identity ..................................................................................................................... 55
5.4.78 Number-Portability-Routing-Information ........................................................................................... 55
5.4.79 Ringing-Duration ................................................................................................................................ 56
5.4.80 Abnormal-Finish-Info ......................................................................................................................... 56
5.4.81 Abnormal-Finish-Warning .................................................................................................................. 56
5.4.82 Abnormal-Finish-Reason .................................................................................................................... 56
5.4.83 Carrier-Select-Routing-Information .................................................................................................... 57
5.4.84 Session-Priority ................................................................................................................................... 57
5.5 Work Flow ...................................................................................................................................................... 58
5.5.1 Online Charging Flow for the ATS + OCS Solution ............................................................................. 58
5.5.2 Configuring Data for Interworking Between the ATS and an External OCS ........................................ 59

A Result-Code Definition............................................................................................................. 60

Issue (2012-11-30) Huawei Proprietary and Confidential vi

1 Standard Reference Files

The clauses in the following files become the clauses of this specification through reference.
All the sequent modification sheets (excluding the corrigenda) of the referenced files marked
with date are not fit for this specification. However, the parties that reach an agreement
according to this specification are recommended to study whether the latest versions of these
files can be used. The latest versions for all the referenced files without date are fit for this
specification.
[1] IETF RFC 3588: "Diameter Base Protocol"
[2] IETF RFC 4006: "Diameter Credit-Control Application"
[3] 3GPP TS 32.299 V8.3.0: "Telecommunication management; Charging management;
Diameter charging application"
[4] 3GPP TS 32.251 V8.2.0: "Telecommunication management; Charging management;
Packet Switched (PS) domain charging"
[5] 3GPP TS 32.296 V8.3.0: "Charging management; Online Charging System (OCS)
Applications and interfaces"
[6] 3GPP TS 32.815 V6.1.0: "Charging management; Online Charging System (OCS)
architecture study"

Issue (2012-11-30) Huawei Proprietary and Confidential 1

2 Definitions Symbols and Acronyms

2.1 Definitions
AAA
Authentication, Authorization and Accounting.

Accounting
The act of collecting information on resource usage for the purpose of capacity planning,
auditing, billing or cost allocation.

Accounting Record
An accounting record represents a summary of the resource consumption of a user over the
entire session. Accounting servers creating the accounting record by processing interim
accounting events or accounting events from several devices serving the same user.

Authentication
The act of verifying the identity of an entity (subject).

Authorization
The act of determining whether a requesting entity (subject) will be allowed access to a
resource (object).

AVP
The Diameter protocol consists of a header followed by one or more Attribute-Value-Pairs
(AVPs). An AVP includes a header and is used to encapsulate protocol-specific data (for
example, routing information) as well as authentication, authorization or accounting
information.

Diameter Agent
A Diameter Agent is a Diameter node that provides either relay, proxy, redirect or translation
services.

Issue (2012-11-30) Huawei Proprietary and Confidential 2

Diameter Client
A Diameter Client is a device at the edge of the network that performs access control. An
example of a Diameter client is a Network Access Server (NAS) or a Foreign Agent (FA).

Diameter Node
A Diameter node is a host process that implements the Diameter protocol, and acts either as a
Client, Agent or Server.

Diameter Peer
A Diameter Peer is a Diameter Node to which a given Diameter Node has a direct transport
connection.

Diameter Server
A Diameter Server is one that handles authentication, authorization and accounting requests
for a particular realm. By its very nature, a Diameter Server must support Diameter
applications in addition to the base protocol.

Network Access Identifier

The Network Access Identifier, or NAI [NAI], is used in the Diameter protocol to extract a
user's identity and realm. The identity is used to identify the user during authentication or
authorization, while the realm is used for message routing purposes.

Realm
The string in the NAI that immediately follows the '@' character. NAI realm names are
required to be unique, and are piggybacked on the administration of the DNS name space.
Diameter uses the realm, also loosely referred to as domain, to determine whether messages
can be satisfied locally, or whether they must be routed or redirected. In RADIUS, realm
names are not necessarily piggybacked on the DNS name space but may be independent of it.

Session State
A stateful agent is one that maintains session state information, by keeping track of all
authorized active sessions. Each authorized session is bound to a particular service, and its
state is considered active either until it is notified otherwise, or by expiration.

Transport Connection
A transport connection is a TCP or SCTP connection existing directly between two Diameter
peers, otherwise known as a Peer-to-Peer Connection.

2.2 Symbols and Acronyms

Acronym Full Name
AAA Authentication, Authorization and Accounting

Issue (2012-11-30) Huawei Proprietary and Confidential 3

ABNF Augmented BNF for Syntax Specifications

AVP Attribute Value Pairs
RADIUS Remote Authentication Dial-In User Service
SCTP Stream Control Transmission Protocol
TCP Transmission Control Protocol
IP Internet Protocol
TLS Transport Layer Security
IMPU IP Multimedia Public Identity

Issue (2012-11-30) Huawei Proprietary and Confidential 4

3 Protocol Architecture

This chapter describes the protocol architecture of the DCCA.

3.1 Protocol Format

3.1.1 Message Head Format
The message architecture of the Diameter protocol is shown in the following figure. These
segments are sent in the order of network byte.

Figure 3-1 Message head format

0 1 2 3
01234567890123456789012345678901
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| command flags | Command-Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Application-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Hop-by-Hop Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| End-to-End Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVPs ...
+-+-+-+-+-+-+-+-+-+-+-+-+-

Issue (2012-11-30) Huawei Proprietary and Confidential 5

Version: This field must be set to 1 to indicate Diameter Version 1.

Message Length: The Message Length field is three octets and indicates the length of the
Diameter message including the header fields.
Command flags: The Command Flags field is eight bits. The following bits are assigned:
01234567
+-+-+-+-+-+-+-+-+
|R P E T r r r r|
+-+-+-+-+-+-+-+-+
− R(equest): If set, the message is a request. If cleared, the message is an answer.
− P(roxiable): If set, the message may be deputized, relayed or redirected. If cleared,
the message must be locally processed.
− E(rror): If set, the message contains a protocol error, and the message will not
conform to the ABNF described for this command. Messages with the 'E' bit set are
commonly referred to as error messages. This bit must not be set in request messages.
− T(Potentially re-transmitted message):This flag is set after a link failover procedure,
to aid the removal of duplicate requests. It is set when resending requests not yet
acknowledged, as an indication of a possible duplicate due to a link failure. This bit
must be cleared when sending a request for the first time, otherwise the sender must
set this flag. Diameter agents only need to be concerned about the number of requests
they send based on a single received request; retransmissions by other entities do not
need to be tracked. Diameter agents that receive a request with the T flag set, must
keep the T flag set in the forwarded request. This flag must not be set if an error
answer message (for example, a protocol error) has been received for the earlier
message. It can be set only in cases where no answer has been received from the
server for a request and the request is sent again. This flag must not be set in answer
messages.
− r(eserved): These flag bits are reserved for future use, and must be set to zero, and
ignored by the receiver.
Command-Code: The Command-Code field is three octets, and is used in order to
communicate the command associated with the message.
Application-ID: Application-ID is four octets and is used to identify to which application
the message is applicable for. The application can be an authentication application, an
accounting application or a vendor-specific application.
The Application-ID in the header must be the same as what is contained in any relevant
AVPs contained in the message.
Hop-by-Hop Identifier: The Hop-by-Hop Identifier is an unsigned 32-bit integer field (in
network byte order) and aids in matching requests and replies. The sender must ensure
that the Hop-by-Hop identifier in a request is unique on a given connection at any given
time, and may attempt to ensure that the number is unique across reboots. The sender of
an Answer message must ensure that the Hop-by-Hop Identifier field contains the same
value that is found in the corresponding request. The Hop-by-Hop identifier is normally
a monotonically increasing number, whose start value is randomly generated. An answer
message that is received with an unknown Hop-by-Hop Identifier must be discarded.
End-to-End Identifier: The End-to-End Identifier is an unsigned 32-bit integer field (in
network byte order) and is used to detect duplicate messages. Upon reboot
implementations may set the high order 12 bits to contain the low order 12 bits of current
time, and the low order 20 bits to a random value. Senders of request messages must
insert a unique identifier on each message. The identifier must remain locally unique for
a period of at least 4 minutes, even across reboots. The originator of an Answer message
must ensure that the End-to-End Identifier field contains the same value that is found in

Issue (2012-11-30) Huawei Proprietary and Confidential 6

the corresponding request. The End-to-End Identifier must not be modified by Diameter
agents of any kind. The combination of the Origin-Host and this field is used to detect
duplicates. Duplicate requests cause the same answer to be transmitted, and must not
affect any state that is set when the original request is processed. Duplicate answer
messages that are to be locally consumed are silently discarded.
AVPs: AVPs are a method of encapsulating information relevant to the Diameter
message.

3.1.2 Message List

Command Name Acronym Command Code

Credit-Control-Request CCR 272

Credit-Control-Answer CCA 272
Re-Auth-Request RAR 258
Re-Auth-Answer RAA 258
Abort-Session-Request ASR 274
Abort-Session-Answer ASA 274

3.1.3 AVP Head Format

The segments in the AVP are sent in the order of network byte. The AVP head format is shown
in the following figure.

Figure 3-2 AVP head format

0 1 2 3
01234567890123456789012345678901
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AVP Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V M P r r r r r| AVP Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor-ID (opt) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data ...
+-+-+-+-+-+-+-+-+

AVP Code
The AVP Code, combined with the Vendor-ID field, identifies the attribute uniquely. AVP
numbers 1 to 255 are reserved for backward compatibility with RADIUS, without setting

Issue (2012-11-30) Huawei Proprietary and Confidential 7

the Vendor-ID field. AVP numbers 256 and above are used for Diameter, which are
allocated by IANA.
AVP Flags
The AVP Flags field informs the receiver how each attribute must be handled. The 'r'
(reserved) bits are unused and must be set to 0. Note that subsequent Diameter
applications may define additional bits within the AVP header, and an unrecognized bit is
considered an error. The 'P' bit indicates the need for encryption for end-to-end security.
The 'M' Bit, known as the Mandatory bit, indicates whether support of the AVP is
required. If an AVP with the 'M' bit set is received by a Diameter client, server, proxy, or
translation agent and either the AVP or its value is unrecognized, the message must be
rejected. Diameter Relay and redirect agents must not reject messages with unrecognized
AVPs.
AVPs with the 'M' bit cleared are informational only and a receiver that receives a
message with such an AVP that is not supported, or whose value is not supported, may
simply ignore the AVP.
The 'V' bit, known as the Vendor-Specific bit, indicates whether the optional Vendor-ID
field is present in the AVP header. When set the AVP Code belongs to the specific vendor
code address space.
Unless otherwise noted, AVPs will have the following default AVP
Flags field settings:
The 'M' bit must be set. The 'V' bit must not be set.
AVP Length
The AVP Length field is three octets, and indicates the number of octets in this AVP
including the AVP Code, AVP Length, AVP Flags, Vendor-ID field (if present) and the
AVP data. If a message is received with an invalid attribute length, the message is
rejected.

3.1.4 AVP Data Formats

The Data field is zero or more octets and contains information specific to Attribute. The
format and length of the Data field is determined by the AVP Code and AVP Length fields.
The format of the Data field must be one of the following base data types.
OctetString
The data contains arbitrary data of variable length. Unless otherwise noted, the AVP
Length field must be set to at least 8 (12 if the 'V' bit is enabled). AVP Values of this type
that are not a multiple of four-octets in length is followed by the necessary padding so
that the next AVP (if any) will start on a 32-bit boundary.
Integer32
32 bit signed value, in network byte order. The AVP Length field must be set to 12 (16 if
the 'V' bit is enabled).
Integer64
64 bit signed value, in network byte order. The AVP Length field must be set to 16 (20 if
the 'V' bit is enabled).
Unsigned32
32 bit unsigned value, in network byte order. The AVP Length field must be set to 12 (16
if the 'V' bit is enabled).
Unsigned64

Issue (2012-11-30) Huawei Proprietary and Confidential 8

64 bit unsigned value, in network byte order. The AVP Length field must be set to 16 (20
if the 'V' bit is enabled).
Float32
This represents floating point values of single precision as described by IEEE 754-1985.
The 32-bit value is transmitted in network byte order. The AVP Length field must be set
to 12 (16 if the 'V' bit is enabled).
Float64
This represents floating point values of double precision as described by IEEE 754-1985.
The 64-bit value is transmitted in network byte order. The AVP Length field must be set
to 16 (20 if the 'V' bit is enabled).
Grouped
The Data field is specified as a sequence of AVPs. Each of these AVPs follows - in the
order in which they are specified - including their headers and padding. The AVP Length
field is set to 8 (12 if the 'V' bit is enabled) plus the total length of all included AVPs,
including their headers and padding. In this way, the AVP length field of an AVP of the
Grouped type is always a multiple of 4.
Address
The Address format is derived from the OctetString AVP Base Format. It is a
discriminated union, representing, for example a 32-bit (IPv4) [IPV4] or 128-bit (IPv6)
[IPV6] address, most significant octet first. The first two octets of the Address AVP
represent the AddressType, which contains an Address Family defined in
[IANAADFAM]. The AddressType is used to discriminate the content and format of the
remaining octets.
Time
The Time format is derived from the OctetString AVP Base Format. The string must
contain four octets, in the same format as the first four bytes are in the NTP timestamp
format. The NTP Timestamp format is defined in chapter 3 of [SNTP]. This represents
the number of seconds since 0h on 1 January 1900 with respect to the Coordinated
Universal Time (UTC). On 6h 28m 16s UTC, 7 February 2036 the time value will
overflow. SNTP [SNTP] describes a procedure to extend the time to 2104. This
procedure must be supported by all DIAMETER nodes.
UTF8String
The UTF8String format is derived from the OctetString AVP Base Format. This is a
human readable string represented using the ISO/IEC IS 10646-1 character set, encoded
as an OctetString using the UTF-8 [UFT8] transformation format described in RFC
2279.
Diameter Identity
The Diameter Identity format is derived from the OctetString AVP Base Format.
Diameter Identity = FQDN
Diameter Identity value is used to uniquely identify a Diameter node for purposes of
duplicate connection and routing loop detection.
The contents of the string must be the FQDN of the Diameter node. If multiple Diameter
nodes run on the same host, each Diameter node must be assigned a unique Diameter
Identity. If a Diameter node can be identified by several FQDNs, a single FQDN is
picked at startup, and used as the only Diameter Identity for that node, whatever the
connection it is sent on.
Enumerated

Issue (2012-11-30) Huawei Proprietary and Confidential 9

Enumerated is derived from the Integer32 AVP Base Format. The definition contains a
list of valid values and their interpretation and is described in the Diameter application
introducing the AVP.

Issue (2012-11-30) Huawei Proprietary and Confidential 10

4 Interface Description

4.1 ATS+OCS Charging Framework

Figure 4-1 shows the ATS+OCS charging framework.

Figure 4-1 ATS+OCS charging framework

4.2 Entity Functions

Ro Interface
The Ro interface is a credit-control interface complying with the Diameter protocol.

Issue (2012-11-30) Huawei Proprietary and Confidential 11

ATS
The Advanced Telephony Server (ATS) complies with the Diameter protocol and implements
the authentication, authorization, and accounting (AAA) functions in the IMS.

OCS
The Online Charge System (OCS) implements the credit control, account management,
accounting management, and real-time service authorization functions.

4.3 Interworking Requirements

The interworking requirements are as follows:
The Diameter for Ro interface is based on the TCP or SCTP protocol, and the TCP is
preferred. The transmission protocol must be set the same as that configured on the OCS.
If the SCTP is used on both the ATS and the OCS, the SCTP checksum algorithm type
must be set to the same value on both the ATS and the OCS.
The ATS serves as a client or server in the transport layer. If it serves as a client, the OCS
serves as a server.
In IMS V200R008C00, the ATS interconnects with multiple OCS devices at the same
time, and sends online charging messages to the OCS devices (the IP addresses can be
obtained from INVITE/SIP messages sent from the CSCF according to the user profile).
The OCS supports multiple Diameter links to one ATS for reliability, and these Diameter
links work in round-robin mode, session-based mode, or stand-by mode. The
round-robin mode is preferred.
The OCS supports the session-based online charging in Session Charging with Unit
Reservation (SCUR) mode.
The ATS reserves resources for a minimum of 60 seconds.
The OCS meets the performance requirements of the Ro interface according to the traffic
model.
To reduce the size of the CCR message, some AVPs are not carried in latter CCR[update]
and CCR[term] messages because the AVP values are not changed. The OCS obtains the
AVP values from the earlier CCR messages (even from the CCR[initial] messages) to
create a CDR.
Based on new service requirements, new AVPs can be added in later versions. In this
case, the OCS device must ignore these new unknown AVPs or deal with these AVPs, but
not release sessions.
In the IMS, a subscriber has multiple public identities (IMPU), such as a SIP URI and a
TEL URI. The OCS associates the SIP URI with the TEL URI of the subscriber.

In IMS V200R008C00, the ATS supports only the sessions based on online charging for basic calls,
calling line identity presentation/restriction, and call forwarding services.

For certain third-party call control (3PCC) services, in which a call is initiated by the ATS, the
ATS cannot obtain the OCS IP address configured in the user profile carried in SIP messages.
In this case, the ATS sends an online charging message to another OCS based on the local
configuration in the ATS. The OCS forwards the online charging message to the OCS
specified in the user profile.

Issue (2012-11-30) Huawei Proprietary and Confidential 12

5 Interface Definition

5.1 Message Definition

The meanings of signs in this chapter are as follows:
<>: It is mandatory and at the beginning of a message
{}: It is mandatory
[]: It is optional
*[]: The option can be repeated
The meanings of marks in this chapter are as follows:
M: Mandatory
C: Optional
OM: Mandatory option defined by the operator
OC: Optional option defined by the operator

5.2 Credit-Control-Request (CCR)

The Credit-Control-Request (CCR) message is indicated by the command-code field being set
to 272 and the 'R' bit being set in the Command Flags field. It is used between the Diameter
credit-control client and the credit-control server to request credit authorization for a given
service.

Message Format
<Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY >
<Session-Id>
{Origin-Host}
{Origin-Realm}
{Destination-Realm}
{Auth-Application-Id}
{Service-Context-Id}
{CC-Request-Type}

Issue (2012-11-30) Huawei Proprietary and Confidential 13

{CC-Request-Number}
[Destination-Host]
[Event-Timestamp]
[Subscription-Id]
[Service-Identifier ]
[Multiple-Services-Indicator]
[Multiple-Services-Credit Control]
[Service-Information]
[Aoc-Information]
[Termination-Cause]
[Dialed-Party-Address]
Table 5-1 describes the Credit-Control-Request AVP.

Table 5-1 Credit-Control-Request AVP

AVP Name Vendor ID AVP Code Data Format Option

<Session-Id> 0 263 UTF8String M
{Origin-Host} 0 264 DiameterIdentity M
{Origin-Realm} 0 296 DiameterIdentity M
{Destination-Realm} 0 283 DiameterIdentity M
{Auth-Application-Id} 0 258 Unsigned32 M
{Service-Context-Id} 0 461 UTF8String M
{CC-Request-Type} 0 416 Enumerated M
{CC-Request-Number} 0 415 Unsigned32 M
[Destination-Host] 0 293 DiameterIdentity Oc
[Event-Timestamp] 0 55 Time OC
[Subscription-Id] 0 443 Grouped OC
{Subscription-Id-Type} 0 450 Enumerated OC
{Subscription-Id-Data} 0 444 UTF8String OC
[Multiple-Services-Indicator] 0 455 Enumerated OC
[Multiple-Services-Credit Control] 0 456 Grouped OC
[Requested-Service-Unit] 0 437 Grouped OC
[CC-Time] 0 420 Unsigned32 Om
[Used-Service-Unit] 0 446 Grouped OC

Issue (2012-11-30) Huawei Proprietary and Confidential 14

AVP Name Vendor ID AVP Code Data Format Option

[CC-Time] 0 420 Unsigned32 Om
[Reporting-Reason] 10415 872 Enumerated OC
[Service-Information] 10415 873 Grouped OC
[IMS-Information] 10415 876 Grouped OC
[Aoc-Information] 2011 903 Grouped Oc
[Aoc-Confirmation] 2011 904 Enumerated Oc
[Termination-Cause] 0 295 Enumerated Oc
[Dialed-Party-Address] 2011 806 UTF8String Oc

Table 5-2 describes the IMS-Information AVP.

Table 5-2 IMS-Information AVP

AVP Name Vendor AVP Data Format Option

ID Code

[Event-Type] 10415 823 Grouped OC

[SIP-Method] 10415 824 UTF8String OC
[Message-Body ] 10415 889 Grouped OC
[Content-Type] 10415 826 UTF8String OC
[Content-Length] 10415 827 UTF8String OC
[Content-Disposition] 10415 828 UTF8String OC
[Role-of-Node] 10415 829 Enumerated OC
[User-Session-Id] 10415 830 UTF8String OC
[Calling-Party-Address] 10415 831 UTF8String OC
[Called-Party-Address] 10415 832 UTF8String OC
[Time-stamps] 10415 833 Grouped OC
[SIP-Request-Timestamp] 10415 834 UTF8String OC
[SIP-Response-Timestamp] 10415 835 UTF8String OC
[Inter-Operator-Identifier] 10415 838 Grouped OC
[Originating-IOI] 10415 839 UTF8String OC
[Terminating-IOI] 10415 840 UTF8String OC
[IMS-Charging-Identifier] 10415 841 UTF8String OC
*[SDP-Session-Description] 10415 842 UTF8String OC

Issue (2012-11-30) Huawei Proprietary and Confidential 15

AVP Name Vendor AVP Data Format Option

ID Code

*[SDP-Media-component] 10415 843 Grouped OC

[SDP-Media-Name] 10415 844 UTF8String OC
*[SDP-Media-Description] 10415 845 UTF8String OC
[Cause-Code] 10415 861 Enumerated OC
{Node-Functionality} 10415 862 Enumerated OC
[SDP-Media-Identifier] 2011 20820 Enumerated OC
[Diversion-Reason] 2011 20821 Enumerated OC
[Diversion-Count] 2011 20822 Unsigned32 OC
[Requested-Party-Address] 10415 1251 UTF8String OC
[Access-Network-Information] 10415 1263 UTF8String OC
[VPN-Call-property] 2011 922 Enumerated Oc
[Private-Network-Indication] 2011 923 Unsigned32 Oc
[Group-ID] 2011 924 Unsigned32 Oc
[Subgroup-ID] 2011 925 Unsigned32 Oc
[Private-Number] 2011 926 UTF8String Oc
[PBX-Address] 2011 1467 UTF8String Oc
[Service-Identity-List_CTEL] 81000 2202 Unsigned32 Oc
[ Session-Priority ] 10415 650 Unsigned32 Oc

5.3 Credit-Control-Answer (CCA)

The Credit-Control-Answer (CCA) message is indicated by the command-code field being set
to 272 and the 'R' bit being cleared in the Command Flags field. It is used between the
credit-control server and the Diameter credit-control client to acknowledge a
Credit-Control-Request command.

Message Format
<Credit-Control-Answer> ::= < Diameter Header: 272, PXY >
<Session-Id>
{Result-Code}
{Origin-Host}
{Origin-Realm}

Issue (2012-11-30) Huawei Proprietary and Confidential 16

{Auth-Application-Id}
{CC-Request-Type}
{CC-Request-Number}
*[Multiple-Services-Credit-Control]
[Aoc-Tariff]
[Aoc-Cost-Information]
[AoC-Information]
[Cost-Information]
Table 5-3 describes the Credit-Control-Answer AVP.

Table 5-3 Credit-Control-Answer AVP

AVP Name Vendor Id AVP Code Data Format Option

<Session-Id> 0 263 UTF8String M
{Result-Code} 0 268 Unsigned32 M
{Origin-Host} 0 264 DiameterIdentity M
{Origin-Realm} 0 296 DiameterIdentity M
{Auth-Application-Id} 0 258 Unsigned32 M
{CC-Request-Type} 0 416 Enumerated M
{CC-Request-Number} 0 415 Unsigned32 M
[Multiple-Services-Credit-Control] 0 456 Grouped OC
[Granted-Service-Unit] 0 431 Grouped OC
[CC-Time] 0 420 Unsigned32 OC
[Final-Unit-Indication] 0 430 Grouped OC
{Final-Unit-Action} 0 449 Enumerated OC
[Redirect-Server] 0 434 Grouped OC
{Redirect-Address-Type} 0 433 Enumerated OC
{Redirect-Server-Address} 0 435 UTF8String OC
[Aoc-Tariff] 2011 913 Grouped Oc
[Currency-Code] 0 425 Unsigned32 Oc
[Scale-Factor] 2011 914 Grouped Oc
[Value-Digits] 0 447 Integer64 Oc
[Exponent] 0 429 Integer32 Oc
*[ Rating-Element] 2011 915 Grouped Oc

Issue (2012-11-30) Huawei Proprietary and Confidential 17

AVP Name Vendor Id AVP Code Data Format Option

[Unit-Value] 0 445 grouped Oc
[Value-Digits] 0 447 Integer64 Oc
[Exponent] 0 429 Integer32 Oc
[Cost-Value] 2011 917 grouped Oc
[Value-Digits] 0 447 Integer64 Oc
[Exponent] 0 429 Integer32 Oc
[Unit-Threshold] 2011 918 Unsigned32 Oc
[Aoc-Cost-Information] 2011 919 Grouped Oc
[Accumulated-Cost] 2011 920 grouped Oc
[Value-Digits] 0 447 Integer64 Oc
[Exponent] 0 429 Integer32 Oc
[Currency-Code] 0 425 Unsigned32 Oc
[Aoc-Information] 2011 903 Grouped Oc
*[ Aoc-Tariff-Information] 2011 907 Grouped Oc
[Aoc-Start-Time] 2011 908 Unsigned32 Oc
[Aoc-Unit] 2011 909 Unsigned32 Oc
{Aoc-Price} 2011 910 Unsigned32 Oc
[Cost-Information] 0 423 Grouped Oc
{Unit-Value} 0 445 Grouped Oc
{Value-Digits} 0 447 Integer64 Oc
[Exponent ] 0 429 Integer32 Oc
{Currency-Code} 0 425 Unsigned32 Oc
[Cost-Unit] 0 424 UTF8String Oc

5.3.2 Re-Auth-Request (RAR)

The Re-Auth-Request (RAR) message, indicated by the Command-Code set to 258 and the
message flags' 'R' bit set, may be sent by any server to the access device that is providing
session services, to request that the user be re-authenticated or re-authorized.

Message Format
<RAR> ::= < Diameter Header: 258, REQ, PXY >
< Session-Id >
{ Origin-Host }

Issue (2012-11-30) Huawei Proprietary and Confidential 18

{ Origin-Realm }
{ Destination-Realm }
{ Destination-Host }
{ Auth-Application-Id }
{ Re-Auth-Request-Type }

5.3.3 Re-Auth-Answer (RAA)

The Re-Auth-Answer (RAA) message, indicated by the Command-Code set to 258 and the
message flags' 'R' bit cleared, is sent in response to the RAR. The Result-Code AVP must be
present, indicating the disposition of the request.
A successful RAA message must be followed by an application-specific authentication or
authorization message.

Message Format
<RAA> ::= < Diameter Header: 258, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Application-Id }
[ Destination-Host ]

5.3.4 Abort-Session-Request (ASR)

The Abort-Session-Request (ASR) message, indicated by the Command-Code set to 274 and
the message flags' 'R' bit set, may be sent by any server to the access device that is providing
session services, to request that the session identified by the Session-Id be stopped.

Message Format
<ASR> ::= < Diameter Header: 274, REQ, PXY >
< Session-Id >
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
[ Destination-Host ]
{ Auth-Application-Id }

5.3.5 Abort-Session-Answer (ASA)

The Abort-Session-Answer (ASA) message, indicated by the Command-Code set to 274 and
the message flags' 'R' bit cleared, is sent in response to the ASR. The Result-Code AVP must
be present, indicating the disposition of the request.
If the session identified by Session-Id in the ASR is successfully terminated,
Result-Code is set to DIAMETER_SUCCESS.
If the session is not currently active, Result-Code is set to
DIAMETER_UNKNOWN_SESSION_ID.
If the access device does not stop the session for any other reason, Result-Code is set to
DIAMETER_UNABLE_TO_COMPLY.

Issue (2012-11-30) Huawei Proprietary and Confidential 19

Message Format
<ASA> ::= < Diameter Header: 274, PXY >
< Session-Id >
{ Result-Code }
{ Origin-Host }
{ Origin-Realm }
{ Destination-Realm }
{ Auth-Application-Id }
[ Destination-Host ]

5.4 AVP Definition

5.4.1 Access-Network-Information
AVP Name Access-Network-Information

AVP Code 1263

Vendor ID 10415

AVP Type UTF8String

This AVP corresponds to the P-Access-Network-Info header field.

This AVP in an MO CCR is set to the value of the P-Access-Network-Info header field contained in the
SIP message originated by a calling party, and this AVP in an MT CCR is set to the value of the
P-Access-Network-Info header field contained in the SIP message originated by a called party.
This AVP is first set to the value of the P-Access-Network-Info header field contained in an INVITE
request. If the INVITE request does not contain the P-Access-Network-Info header field, this AVP is set
to the value of the P-Access-Network-Info header field contained in a REGISTER request.）
More details of the Access-Network-Information AVP are defined in 3GPP TS 32.299 V8.3.0.

5.4.2 Accumulated-Cost
AVP Name Accumulated-Cost

AVP Code 920

Vendor ID 2011

AVP Type Grouped

This AVP specifies the amount charged since the beginning of the session. The ABNF syntax is as
follows:
Accumulated-Cost ::= < AVP Header: 920 >
{Value-Digits}
{Exponent}

Issue (2012-11-30) Huawei Proprietary and Confidential 20

5.4.3 Aoc-Confirmation
AVP Name Aoc-Confirmation

AVP Code 904

Vendor ID 2011

AVP Type Enumerated

This AVP is a sub-AVP of Aoc-Information (AVP code 903).

Values:
1: SUPPORTED
This AVP is applicable only to the AOC service in the first CCR, when the ATS supports the charging
AVP defined by Huawei.

5.4.4 Aoc-Cost-Information
AVP Name Aoc-Cost-Information

AVP Code 919

Vendor ID 2011

AVP Type Grouped

This AVP specifies the information about the AOC service. This AVP is applicable only to the AOC
service in CCA messages. The ABNF syntax is as follows:
Aoc-Cost-Information ::= < AVP Header: 919 >
{Accumulated-Cost}
[Incremental-Cost]
[Currency-Code]

Issue (2012-11-30) Huawei Proprietary and Confidential 21

5.4.5 Aoc-Information
AVP Name Aoc-Information

AVP Code 903

Vendor ID 2011

AVP Type Grouped

This AVP specifies the information about the AOC service. This AVP is applicable only to the AOC
service in the CCA message. The ABNF syntax is as follows:
Aoc-Information ::= < AVP Header: 903 >
[Currency-Code]
*{Aoc-Tariff-Information}

5.4.6 Aoc-Price
AVP Name Aoc-Price

AVP Code 910

Vendor ID 2011

AVP Type Unsigned32

This AVP specifies the unit price.

5.4.7 Aoc-Start-Time
AVP Name Aoc-Start-Time

AVP Code 908

Vendor ID 2011

AVP Type Integer32

This AVP specifies the start time of a tariff, in units of seconds and starting from 0. To improve the user
experience, the peer device can convert the Aoc-Start-Time value that is a multiple of 60 to a value
expressed in minutes. For example, at the first minute, the Aoc-Start-Time is 0 seconds. At the fourth
minute, the Aoc-Start-Time is set to 180 seconds. If this AVP is contained, the tariff starts from the first
minute.

Issue (2012-11-30) Huawei Proprietary and Confidential 22

5.4.8 Aoc-Tariff
AVP Name Aoc-Tariff

AVP Code 913

Vendor ID 2011

AVP Type Grouped

This AVP contains the following sub-AVP information related to the AOC service in a CCA message.
The ABNF syntax is as follows:
Aoc-Tariff ::= < AVP Header: 913 >
[Currency-Code]
{Scale-Factor}
*{Rating-Element}

5.4.9 Aoc-Tariff-Information
AVP Name Aoc-Tariff-Information

AVP Code 907

Vendor ID 2011

AVP Type Grouped

This AVP specifies the tariff information about the AOC service. This AVP must be contained in every
initial CCA message and updated CCA message. The ABNF syntax is as follows:
Aoc-Tariff-Information ::= < AVP Header: 907 >
{Aoc-Start-Time}
[Aoc-Unit]
{Aoc-Price}

Issue (2012-11-30) Huawei Proprietary and Confidential 23

5.4.10 Aoc-Unit
AVP Name Aoc-Unit

AVP Code 909

Vendor ID 2011

AVP Type Integer32

This AVP specifies the time unit of a tariff, in units of seconds. If this AVP is not contained, the AOC
unit is considered to be 60 seconds.

5.4.11 Auth-Application-Id
AVP Name Auth-Application-Id

AVP Code 258

Vendor ID 0

AVP Type Unsigned32

This AVP must contain the value of 4 as defined in RFC 4006 [402] according to TS 29.230 [206].

Issue (2012-11-30) Huawei Proprietary and Confidential 24

5.4.12 Called-Party-Address
AVP Name Called-Party-Address

AVP Code 832

Vendor ID 10415

AVP Type UTF8String

This AVP indicates the called number that can be a SIP URI or a TEL URI. It is contained in the
Request-URI field.
1. If the called number is a TEL URI, the ATS9900 normalizes this number.
This AVP in the originating CCR is set based on the value of the Bill unification type parameter
defined by running ADD CNACLD:
(1) If Bill unification type is set to UNIFORM_WITHNO_SEP, the called number is
normalized to a global number prefixed with the plus sign (+), for example, +867552842001
(2) If Bill unification type is set to UNIFORM_WITH_SEP: the called number is normalized
to a global number with the plus sign (+) and minus sign (-), for example, tel:+86-755-2842001
(3) If Bill unification type is set to UNIFORM_WITH_IDD: the called number is normalized
to an international number with the international toll call prefix, for example, 00867552842001
(4) If Bill unification type is set to UNIFORM_WITHNO_IDD: the called number is
normalized to an international number without the international toll call prefix, for example,
867552842001
(5) If Bill unification type is set to NO_UNITFORM: The ATS9900 does not normalize the
called number.
This AVP in a terminating CCR is set to a global number with a plus sign (+).
If the called number is a TEL URI containing “user=phone”, for example,
sip:[email protected];user=phone, the ATS9900 does not normalize this number.
2. If the called number is a SIP URI, the ATS9900 does not normalize this number.
The TEL URI can be in two formats, for example:
tel:+8675528420001 or tel:28420001
sip:[email protected];user=phone
The SIP URI is as follows:
sip:[email protected]

Issue (2012-11-30) Huawei Proprietary and Confidential 25

5.4.13 Calling-Party-Address
AVP Name Calling-Party-Address

AVP Code 831

Vendor ID 10415

AVP Type UTF8String

This AVP indicates the calling number. It corresponds to the PAI header field contained in an INVITE
request. If the P-Asserted-Identity header field is not contained in an INVITE request, this AVP
corresponds to the From header field. The value can be a SIP URI or a TEL URI. This AVP appears one
time when the P-Asserted-Identity header contains both a SIP URI and a TEL URI.
If the value is a TEL URI, it can be a global number with the plus sign.
The TEL URI can be in two formats, for example:
tel:+8675528420001
sip:[email protected];user=phone
The SIP URI is as follows:
sip:[email protected]

5.4.14 CC-Request-Number
AVP Name CC-Request-Number

AVP Code 415

Vendor ID 0

AVP Type Unsigned32

This AVP identifies a request within a session. As Session-Id AVPs are globally unique, the combination
of Session-Id and CC-Request-Number AVPs is also globally unique and can be used in matching
credit-control messages with confirmations.
Set the value to 0 for a credit-control request of the INITIAL_REQUEST type and set the value to 1
for the first UPDATE_REQUEST, to 2 for the second, and so on until the value for
TERMINATION_REQUEST is one more than that of the last UPDATE_REQUEST.

Issue (2012-11-30) Huawei Proprietary and Confidential 26

5.4.15 CC-Request-Type
AVP Name CC-Request-Type

AVP Code 416

Vendor ID 0

AVP Type Enumerated

This AVP specifies the reason for sending the CCR message, and is contained in the CCR message.
The following values are defined in the CC-Request AVP:
INITIAL_REQUEST 1
An Initial request is used to initiate a credit-control session, and contains credit control information
that is relevant to the initiation.
UPDATE_REQUEST 2
An Update request contains credit control information for an existing credit-control session. Update
credit-control requests are sent when a credit-control re-authorization is needed at the expiry of the
allocated quota or validity time.
TERMINATION_REQUEST 3
A Termination request is sent to terminate a credit-control session and contains credit-control
information relevant to the existing session.

5.4.16 CC-Time
AVP Name CC-Time

AVP Code 420

Vendor ID 0

AVP Type Unsigned32

This AVP defines the requested, allocated, or used time in units of seconds.

Issue (2012-11-30) Huawei Proprietary and Confidential 27

5.4.17 CC-Total-Octets
AVP Name CC-Total-Octets

AVP Code 421

Vendor ID 0

AVP Type Unsigned64

This AVP specifies the total requested, allocated, or used bytes. This value is not related to the direction
(sending or receiving).

5.4.18 Content-Disposition
AVP Name Content-Disposition

AVP Code 828

Vendor ID 10415

AVP Type UTF8String

This AVP indicates how the message-body or a message-body part (for example, session, render) is to be
interpreted, as described in RFC 3261 [405].

5.4.19 Content-Length
AVP Name Content-Length

AVP Code 827

Vendor ID 10415

AVP Type UTF8String

This AVP specifies the size of the message-body, as described in RFC 3261 [405].

Issue (2012-11-30) Huawei Proprietary and Confidential 28

5.4.20 Content-Type
AVP Name Content-Type

AVP Code 826

Vendor ID 10415

AVP Type UTF8String

This AVP specifies the media type (for example, application/sdp, text/html) of the message-body, as
described in RFC 3261 [405].

5.4.21 Cost-Information
AVP Name Cost-Information

AVP Code 423

Vendor ID 0

AVP Type Grouped

This AVP specifies the cost information about a service. In the initial CCA message, this field is set to 0.
In the update and termination CCA messages, this field is set to the actual value.
The ABNF syntax is as follows:
Cost-Information ::= < AVP Header: 423 >
{Unit-Value}
{Currency-Code}
[Cost-Unit]

Issue (2012-11-30) Huawei Proprietary and Confidential 29

5.4.22 Cost-Value
AVP Name Cost-Value

AVP Code 917

Vendor ID 2011

AVP Type Grouped

This AVP specifies the associated cost (in currency code) to be charged per unit-value. The ABNF
syntax is as follows:
Cost-Value ::= < AVP Header: 917 >
{Value-Digits}
{Exponent]}

5.4.23 Currency-Code
AVP Name Currency-Code

AVP Code 425

Vendor ID 0

AVP Type Unsigned32

This AVP specifies the currency type. It is a sub-AVP of Aoc-Tariff.

5.4.24 Destination-Host
AVP Name Destination-Host

AVP Code 293

Vendor ID 0

AVP Type Diameter Identity

This AVP specifies the ID of the device receiving the message. The global network allocates it in
centralized mode. Diameter peers must be unique.
It is contained in the request message but cannot be contained in the response message.
Example: ocs001.huawei.com.

Issue (2012-11-30) Huawei Proprietary and Confidential 30

5.4.25 Destination-Realm
AVP Name Destination-Realm

AVP Code 283

Vendor ID 0

AVP Type Diameter Identity

This AVP specifies the home field of the device receiving the message. This attribute cannot be
contained in the response message.
Example: huawei.com.

Issue (2012-11-30) Huawei Proprietary and Confidential 31

5.4.26 Dialed-Party-Address
AVP Name Dialed-Party-Address

AVP Code 806

Vendor ID 2011

AVP Type UTF8String

It is a AVP defined by Huawei Technologies Co., Ltd. This field indicates the dialed number in
original CCR. The value can be a SIP URI or a TEL URI. This AVP is set to the value of the
Request-URI header field. The ATS sends the number that are not normalized.
The TEL URI can be in two formats, for example:
tel:+8675528420001 or tel:28420001
sip:[email protected];user=phone
The SIP URI is as follows:
sip:[email protected]

5.4.27 Diversion-Count
AVP Name Diversion-Count

AVP Code 20822

Vendor ID 2011

AVP Type Unsigned32

This field contains the forwarding count. It is used for call forwarding service. The field is valued as the
sum of diversion count in History-Info header of INVITE message and calling forward times triggered
in the local ATS.
For example, when A calls B, the call is forwarded to C, and then to D.
ATS-A: ACR(A->B) null
ATS-B: ACR(A-C) 0
ATS-B: ACR(B->C) 1
ATS-C: ACR(A-C) 1
ATS-C: ACR(C-D) 2

Issue (2012-11-30) Huawei Proprietary and Confidential 32

5.4.28 Diversion-Reason
AVP Name Diversion-Reason

AVP Code 20821

Vendor ID 2011

AVP Type Enumerated

This field contains the forwarding reason. It is used for call forwarding service. It can be one of the
following:
0: RFR_UNKNOWN
1: CALL_CFU
2: CALL_CFB
3: CALL_CFNR
4: CALL_CFNL
5: CALL_DEFLECTION_ALERTING_RESPONSE
6: CALL_DEFLECTION_IMMEDIATE_RESPONSE
7: CALL_CFNRC
8: CALL_CFU_TO_MAILBOX
9: CALL_CFB_TO_MAILBOX
10: CFNR_TO_MAILBOX
11: CFNL_TO_MAILBOX
12: CFNRC_TO_MAILBOX
13: CALL_CFTB
14: CALL_DND_TO_MAILBOX
15: CALL_CW_CFNR
16: CALL_CFS
17:CALL_DND_TO_MAILBOX
18:CALL_CW_CFNR
19:CALL_CFS
20:CALL_ACR_TO_MAILBOX
255: RFR_BUTT
The ATS sends an ACR for each call forwarding operation. This field indicates only the current
forwarding reason.

Issue (2012-11-30) Huawei Proprietary and Confidential 33

5.4.29 Event-Timestamp
AVP Name Event-Timestamp

AVP Code 55

Vendor ID 0

AVP Type Time

This AVP specifies the time stamp, indicating the number of seconds from January 1, 1900 00:00 UTC
to the sending time of the AVP.

5.4.30 Exponent
AVP Name Exponent

AVP Code 429

Vendor ID 0

AVP Type Integer32

This AVP specifies the exponent part of a float value.

5.4.31 Event-Type
AVP Name Event-Type

AVP Code 823

Vendor ID 10415

AVP Type Grouped

This AVP contains information about the type of chargeable telecommunication service for which the
credit-control request message(s) is generated. The ABNF syntax is as follows:
<Event-Type>:: = <AVP Header: 823 >
[ SIP-Method ]

Issue (2012-11-30) Huawei Proprietary and Confidential 34

5.4.32 Final-Unit-Action
AVP Name Final-Unit-Action

AVP Code 449

Vendor ID 0

AVP Type Enumerated

This AVP indicates the action when the user account balance is insufficient to pay for the service charge.
Final-Unit-Action defines the following values:
TERMINATE 0
DCC client must end the service session. This is the default processing when the DCC user terminal
receives a Final-Unit-Action that is not supported.

5.4.33 Final-Unit-Indication
AVP Name Final-Unit-Indication

AVP Code 430

Vendor ID 0

AVP Type Grouped

This AVP indicates in the CCA message the number of the final units included in Granted-Service-Unit.
When these units are used up, the DCC client performs the actions designated in Final-Unit-Action.
If multiple service types are received in CCA, the service unit type that is first used up causes the DCC
client to perform the designated actions.
Final-Unit-Action defines the action performed by the service processing node when the user account
balance is insufficient to pay for the service charge. If Final-Unit-Indication exists, Final-Unit-Action
must also exist.
If Final-Unit-Action is set to TERMINATE, other AVPs in the Final-Unit-Indication AVP group must
not be contained. The ATS supports TERMINATE only.
The ABNF syntax is as follows:
Final-Unit-Indication ::= < AVP Header: 430 >
{ Final-Unit-Action }
[ Redirect-Server ]

Issue (2012-11-30) Huawei Proprietary and Confidential 35

5.4.34 Granted-Service-Unit
AVP Name Granted-Service-Unit

AVP Code 431

Vendor ID 0

AVP Type Grouped

This AVP includes the number of the units that allow the DCC client to provide services to terminal
users. When these units are used up, the DDC client must apply for new quota from the DCC server or
stop providing services to the terminal users. The DCC client does not need to distinguish all unit types.
In the CCA message when the client receives a unit type that cannot be distinguished or supported, the
CCA is regarded as error, and the DCC client must abort the session by sending a CCR message in
which the Termination-Cause is DIAMETER_BAD_ANSWER.
The ABNF syntax is as follows:
Granted-Service-Unit ::= < AVP Header: 431 >
[ CC-Time ]
[ CC-Total-Octets ]

5.4.35 Group-ID
AVP Name Group-ID

AVP Code 924

Vendor ID 2011

AVP Type Unsigned32

It is an AVP defined by Huawei Technologies Co., Ltd. It is an optional AVP, which indicates the
Centrex group number of a Centrex subscriber.

Issue (2012-11-30) Huawei Proprietary and Confidential 36

5.4.36 Message-Body
AVP Name Message-Body

AVP Code 889

Vendor ID 10415

AVP Type Grouped

This AVP specifies information about the message bodies including user-to-user data.
The ABNF syntax is as follows:
<Message-Body>::= < AVP Header: 889 >
[ Content-Type ]
[ Content-Length ]
[ Content-Disposition ]

5.4.37 Multiple-Services-Credit-Control
AVP Name Multiple-Services-Credit-Control

AVP Code 456

Vendor ID 0

AVP Type Grouped

This AVP is related to independent multiple-service credit control. Each instance contains one or more
services.
The details are defined in IETF RFC 4006. The Service-Identifier AVP is not a sub-AVP of the
Multiple-Services-Credit-Control AVP in the current ATS version.

Issue (2012-11-30) Huawei Proprietary and Confidential 37

5.4.38 Multiple-Services-Indicator
AVP Name Multiple-Services-Indicator

AVP Code 455

Vendor ID 0

AVP Type Enumerated

This AVP indicates whether the DCC client can deal with multiple services independently in a session or
sub-session. If this AVP is not specified, the DCC client does not support multiple services.
If the DCC server does not support independent multiple-service credit control, then this AVP is
regarded as invalid.
For the same session, the client only needs to use this AVP in the first query.
The following values are defined in the Multiple-Services-Indicator AVP:
MULTIPLE_SERVICES_NOT_SUPPORTED 0
The client does not support independent multiple-service credit control in a session or sub-session.
MULTIPLE_SERVICES_SUPPORTED 1
The client supports independent multiple-service credit control in a session or sub-session.

5.4.39 Node-Functionality
AVP Name Node-Functionality

AVP Code 862

Vendor ID 10415

AVP Type Enumerated

This AVP includes the functionality identifier of the node.

The functionality identifier can be one of the following:
S-CSCF: 0
P-CSCF: 1
I-CSCF: 2
MRFC: 3
MGCF: 4
BGCF: 5
AS: 6
IBCF: 7
Only the value 6 is used by the ATS.

Issue (2012-11-30) Huawei Proprietary and Confidential 38

5.4.40 Origin-Host
AVP Name Origin-Host

AVP Code 264

Vendor ID 0

AVP Type Diameter Identity

This AVP specifies the ID of the device sending the message. The global network allocates it in
centralized mode. Diameter peers must be unique.
Example: SCP001.huawei.com.

Issue (2012-11-30) Huawei Proprietary and Confidential 39

5.4.41 Origin-Realm
AVP Name Origin-Realm

AVP Code 296

Vendor ID 0

AVP Type Diameter Identity

This AVP specifies the home field of the device sending the message.
Example: huawei.com.

5.4.42 PBX-Address
AVP Name PBX-Address

AVP Code 1467

Vendor ID 2011

AVP Type UFT8String

It is an AVP defined by Huawei Technologies Co., Ltd.

This AVP indicates 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.

5.4.43 Private-Network-Indication
AVP Name Private-Network-Indication

AVP Code 923

Vendor ID 2011

AVP Type Unsigned32

It is an AVP defined by Huawei Technologies Co., Ltd.

This AVP indicates 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 CXSBR command.
This field contains the call indication:
0- CENTREX Call
1- PERSON Call

5.4.44 Private-Number
AVP Name Private-Number

Issue (2012-11-30) Huawei Proprietary and Confidential 40

AVP Code 926

Vendor ID 2011

AVP Type UFT8String

It is an AVP defined by Huawei Technologies Co., Ltd. It is an optional AVP, which indicates the user's
short number.
Examples:
tel:71001
tel: 60171001

5.4.45 Rating-Element
AVP Name Rating-Element

AVP Code 915

Vendor ID 2011

AVP Type Grouped

This AVP specifies the rate information and contains the following sub-AVPs:
{Unit-Value}
{Cost-Value}
{Unit-Threshold}
The ABNF syntax is as follows:
Rating-Element ::= < AVP Header: 915 >
{Unit-Value}
{Cost-Value}
{Unit-Threshold}

5.4.46 Re-Auth-Request-Type
AVP Name Re-Auth-Request-Type

AVP Code 285

Vendor ID 0

AVP Type Enumerated

This AVP is included in application-specific answer to inform the client of the expected action upon
expiration of the Authorization-Lifetime. The details are defined in IETF RFC 3588.

Issue (2012-11-30) Huawei Proprietary and Confidential 41

5.4.47 Requested-Party-Address
AVP Name Requested-Party-Address

AVP Code 1251

Vendor ID 10415

AVP Type UTF8String

This AVP contains the address (SIP URI or TEL URI) of the party (Public User ID or Public Service ID) to whom the
SIP transaction is originally posted.
The Requested-Party-Address AVP contains the SIP URI or TEL URI contained in the Request-URI of the incoming
request. This field is present only when it is different from the Called Party Address parameter.
The TEL URI can be in two formats, for example:
tel:+8675528420001 or tel:28420001
sip:[email protected];user=phone
The SIP URI is as follows:
sip:[email protected]

5.4.48 Requested-Service-Unit
AVP Name Requested-Service-Unit

AVP Code 437

Vendor ID 0

AVP Type Grouped

This AVP specifies the requested service unit or total amount.

Requested-Service-Unit must be contained in the first or middle CCR request. If the DCC client (for
example: test that the terminal user terminates the service) does not contain Requested-Service-Unit in
the request, then the DCC server deducts the used amount from the user's account. In addition, a new
quota cannot be returned in the response.
The specific ABNF grammars are as follows:
Requested-Service-Unit ::= < AVP Header: 437 >
[ CC-Time ]

Issue (2012-11-30) Huawei Proprietary and Confidential 42

5.4.49 Reporting-Reason
AVP Name Reporting-Reason

AVP Code 872

Vendor ID 10415

AVP Type Enumerated

This AVP specifies the reason for sending the message. More details of this AVP are defined in 3GPP TS
32.299 V8.3.0.

5.4.50 Result-Code
AVP Name Result-Code

AVP Code 268

Vendor ID 0

AVP Type Unsigned32

This AVP shows whether a specific request is executed successfully or an error occurs. All Diameter
replies defined in the IETF application include Result-Code.
The Result-Code data includes a 32-bit address space managed by INAN to show an error. The error
code types provided by the Diameter are as follows and the error types are distinguished by the
thousands digit:
- 1xxx (Information)
- 2xxx (Succeded)
- 3xxx (Protocol error)
- 4xxx (Temporary failure)
- 5xxx (Permanent failure)
For the value definition of this field, see Appendix A "Result-Code Definition."

Issue (2012-11-30) Huawei Proprietary and Confidential 43

5.4.51 Role-of-Node
AVP Name Role-of-Node

AVP Code 829

Vendor ID 10415

AVP Type Enumerated

This AVP specifies the role of the ATS. The identifier can be one of the following:
ORIGINATING_ROLE: 0
The AS is applying an originating role, serving the calling subscriber.
TERMINATING_ROLE: 1
The AS is applying a terminating role, serving the called subscriber.
PROXY ROLE: 2
The AS is applying a proxy role.
B2BUA_ROLE 3
The AS is applying a B2BUA role.

5.4.52 Scale-Factor
AVP Name Scale-Factor

AVP Code 914

Vendor ID 2011

AVP Type Grouped

This AVP specifies the scaling factor on the whole calculation. It is a sub-AVP of Aoc-Tariff. The ABNF
syntax is as follows:
Scale-Factor ::= < AVP Header: 914 >
{Value-Digits}
{Exponent}
[Rating-Element]

Issue (2012-11-30) Huawei Proprietary and Confidential 44

5.4.53 Service-Context-Id
AVP Name Service-Context-Id

AVP Code 461

Vendor ID 0

AVP Type UTF8String

More details of the Service-Context-Id AVP are defined in 3GPP TS 32.299 V8.3.0 7.17.

5.4.54 Session-Id
AVP Name Session-Id

AVP Code 263

Vendor ID 0

AVP Type UTF8String

This AVP uniquely identifies a DCC session process.

The syntax is as follows:
<Diameter Identity>;<high 32 bits>;<low 32 bits>[;<optional value>]
<Diameter Identity>: The same as Origin-Host.
<high 32 bits>: System current time.
<low 32 bits>: Circularly increasing. The initial value is 0. When the system restarts, it is set to 0.
<optional value>: Reserved.
The preceding fields are separated with ";".
Example: SCP001.huawei.com;1876543210;523.

Issue (2012-11-30) Huawei Proprietary and Confidential 45

5.4.55 Service-Identifier
AVP Name Service-Identifier

AVP Code 439

Vendor ID 0

AVP Type Unsigned32

This AVP indicates the ID of the service.

Values:

Service identifer.TXT

5.4.56 Service-Identity-List_CTEL
AVP Name Service-Identity-List_CTEL

AVP Code 2202

Vendor ID 81000

AVP Type Unsigned32

This AVP indicates the supplement services or centrex services used.

It is available only when the supplement service or centrex service is triggered.The enum value
reference specifications of china telecom.

5.4.57 Service-Information
AVP Name Service-Information

AVP Code 873

Vendor ID 10415

AVP Type Grouped

This AVP is of service information group. Defining this AVP is to allow the client to deliver specific
additional service information.
The ABNF syntax is as follows:
Service-Information :: = < AVP Header: 873>
[ IMS-Information ]

Issue (2012-11-30) Huawei Proprietary and Confidential 46

5.4.58 SDP-Media-component
AVP Name SDP-Media-component

AVP Code 843

Vendor ID 10415

AVP Type Grouped

This AVP contains information about media used for an IMS session.
The ABNF syntax is as follows:
<SDP-Media-Component>:: = <AVP Header: 843 >
[ SDP-Media-Name ]
* [ SDP-Media-Description ]

5.4.59 SDP-Session-Description
AVP Name SDP-Session-Description

AVP Code 842

Vendor ID 10415

AVP Type UTF8String

This AVP specifies the content of attribute-line (i=, c=, b=, k=, or a=) related to a session, as described
in RFC 4566 [406].

5.4.60 SIP-Method
AVP Name SIP-Method

AVP Code 824

Vendor ID 10415

AVP Type UTF8String

This AVP specifies the name of the SIP Method (INVITE, or UPDATE) causing a credit-control request
to be sent to the OCF.

Issue (2012-11-30) Huawei Proprietary and Confidential 47

5.4.61 SIP-Request-Timestamp
AVP Name SIP-Request-Timestamp

AVP Code 834

Vendor ID 10415

AVP Type UTF8String

This AVP specifies the time in UTC format of the SIP request (for example, Invite, Update), indicating
the number of seconds from January 1, 1900 00:00 UTC to the sending time of the AVP.
Example: 3504394089.420

5.4.62 SIP-Response-Timestamp
AVP Name SIP-Response-Timestamp

AVP Code 835

Vendor ID 10415

AVP Type UTF8String

This AVP specifies the time in UTC format of the response to the SIP request (for example, 200 OK),
indicating the number of seconds from January 1, 1900 00:00 UTC to the sending time of the AVP.
Example: 3504394089.420

Issue (2012-11-30) Huawei Proprietary and Confidential 48

5.4.63 SDP-Media-Identifier
AVP Name SDP-Media-Identifier

AVP Code 20820

Vendor ID 2011

AVP Type Enumerated

This AVP indicates the type of SDP in CCR. It is applicable when the SDP-Session-Description AVP is
carried in CCR.
Values:
0: VoiceCall
The received SDP is voice media.
1: VideoCall
The received SDP is video media.
2: Fax
The received SDP is Fax.
3: CSD
4: PABX

5.4.64 Subgroup-ID
AVP Name Subgroup-ID

AVP Code 925

Vendor ID 2011

AVP Type Unsigned32

It is an AVP defined by Huawei Technologies Co., Ltd. It is an optional AVP, which indicates the user's
subgroup ID.

Issue (2012-11-30) Huawei Proprietary and Confidential 49

5.4.65 Subscription-ID
AVP Name Subscription-ID

AVP Code 443

Vendor ID 0

AVP Type Grouped

This AVP identifies the terminal user information.

Subscription-ID is an AVP group. The specific ABNF syntax is as follows:
Subscription-Id ::= < AVP Header: 443 >
{ Subscription-Id-Type }
{ Subscription-Id-Data }
The Subscription-ID AVP contains information which identifies the subscriber. The value can be a SIP
URI or a TEL URI.

5.4.66 Subscription-Id-Type
AVP Name Subscription-Id-Type

AVP Code 450

Vendor ID 0

AVP Type Enumerated

This AVP identifies the terminal ID type of this user. The detailed description is defined in IETF RFC
4006.
It is used inside the Subscription-Id AVP, and it indicates which kind of subscriber information is
contained in this Subscription-Id AVP.
The following values are currently defined for the Subscription-Id-Type AVP:
0: END_USER_E164
1: END_USER_IMSI
2: END_USER_SIP_URI
3: END_USER_NAI
4: END_USER_PRIVATE

Issue (2012-11-30) Huawei Proprietary and Confidential 50

5.4.67 Subscription-Id-Data
AVP Name Subscription-Id-Data

AVP Code 444

Vendor ID 0

AVP Type UTF8String

This field contains the user data content, for example, the MSISDN. The details are defined in IETF
RFC 4006.
If the value is TEL URI, it can be a global number with the plus sign.
The TEL URI can be in two formats, for example:
+8675528420001
[email protected];user=phone
The SIP URI is as follows:
[email protected]

5.4.68 Termination-Cause
AVP Name Termination-Cause

AVP Code 295

Vendor ID 0

AVP Type Enumerated

More details of the Termination-Cause AVP are defined in RFC 3588.

Issue (2012-11-30) Huawei Proprietary and Confidential 51

5.4.69 Time-Stamps
AVP Name Time-Stamps

AVP Code 833

Vendor ID 10415

AVP Type Grouped

This AVP specifies the time of the initial SIP request and the time of the response to the initial SIP
request.
The ABNF syntax is as follows:
<Time-Stamps>:: = < AVP Header: 833 >
[ SIP-Request-Timestamp ]
[ SIP-Response-Timestamp ]

5.4.70 Unit-Value
AVP Name Unit-Value

AVP Code 445

Vendor ID 0

AVP Type Grouped

This AVP specifies the number of consumed units that incur the charge. The ABNF syntax is as follows:
Unit-Value ::= < AVP Header: 445 >
{Value-Digits}
{Exponent}

5.4.71 Unit-Threshold
AVP Name Unit-Threshold

AVP Code 918

Vendor ID 2011

AVP Type Integer32

This AVP specifies the upper limit for consumed units where the rate is still valid.

Issue (2012-11-30) Huawei Proprietary and Confidential 52

5.4.72 Used-Service-Unit
AVP Name Used-Service-Unit

AVP Code 446

Vendor ID 0

AVP Type Grouped

This AVP specifies the number of total used units tested after the service is activated (if middle charging
time is adopted, then the number is counted from the end of the last test).
The ABNF syntax is as follows:
Used-Service-Unit ::= < AVP Header: 446>
[ CC-Time ]

5.4.73 User-Session-Id
AVP Name User-Session-Id

AVP Code 829

Vendor ID 10415

AVP Type UTF8String

This AVP holds the session identifier. For a SIP session, the User-Session-ID contains the SIP Call ID,
as defined in RFC 3261 [405].

Issue (2012-11-30) Huawei Proprietary and Confidential 53

5.4.74 Value-Digits
AVP Name Value-Digits

AVP Code 447

Vendor ID 0

AVP Type Integer64

This AVP specifies the integer part of a floating value.

5.4.75 VPN-Call-property
AVP Name VPN-Call-property

AVP Code 922

Vendor ID 2011

AVP Type Enumerated

It is an AVP defined by Huawei Technologies Co., Ltd. It indicates whether the call is an in-group call.

Values:

0: onnet (in-group)

1: offnet (out-group)

2: virtual onnet (WAC group)

3: forced onnet (in-group calls made by dialing the long number)

4: emergency offnet (emergency out-group calls)

5.4.76 Call-Property
AVP Name Call-Property

AVP Code 912

Vendor ID 2011

AVP Type Enumerated

Issue (2012-11-30) Huawei Proprietary and Confidential 54

It is an AVP defined by Huawei Technologies Co., Ltd. It indicates the call attribute.

This AVP in originating CCRs is set to the actual call attribute such as Local-Call and
International-Toll-Call.

This AVP in terminating CCRs is set based on the Called-Party-Address and Calling-Party-Address in
CDRs. For example, if the country codes of both the Calling-Party-Address and Called-Party-Address are
the same, but the national area codes are different, the AVP is set to National-toll (4).

Values:

0:Unknown-Call(Unknown call type)

1:Intra-Office-Call(Intra-office call)
2:Local-Call(Local call)
3:Local-Toll-Call(Local toll call or the number with different charges is dialed in the same area)
4:National-Toll-Call(National toll call)
5:International-Toll-Call(International toll call)
6:Intra-Local-Toll-Call(Intra-office local toll call)
7:Intra-National-Toll-Call(Intra-office national toll call)
8:Intra-Inter-Toll-Call(Intra-office international toll call)

5.4.77 Called-Asserted-Identity
AVP Name Called-Asserted-Identity

AVP Code 1250

Vendor ID 10415

AVP Type UTF8String

This AVP indicates the SIP URI or TEL URI of the final called party. It is contained only in originating
CCRs and is set to the called number in the P-Asserted-Identity header field of 18x or 200 responses
returned by the final called party.
The TEL URI can be in two formats, for example:
tel:+8675528420001
sip:[email protected];user=phone
The SIP URI is as follows:
sip:[email protected]

5.4.78 Number-Portability-Routing-Information
AVP Name Number-Portability-Routing-Information

AVP Code 2024

Vendor ID 10415

AVP Type UTF8String

Issue (2012-11-30) Huawei Proprietary and Confidential 55

It is an AVP defined by Huawei Technologies Co., This AVP contains the information about the new
number in the Number Portability service registered by the subscriber. The information is obtained from
the rn parameter in the Request-URI or P-Charging-Vector header field (the Request-URI header field is
preferable) of a SIP message.

5.4.79 Ringing-Duration
AVP Name Ringing-Duration

AVP Code 807

Vendor ID 2011

AVP Type Integer32

It is an AVP defined by Huawei Technologies Co., This AVP indicates the ringing duration, that is, the
interval between the 18x message and the 200 response to the INVITE message when the call is
connected.

5.4.80 Abnormal-Finish-Info
AVP Name Abnormal-Finish-Info

AVP Code 810

Vendor ID 2011

AVP Type Grouped

It is an AVP defined by Huawei Technologies Co., This AVP is of type Grouped and consists of
Abnormal-Finish-Warning and Abnormal-Finish-Reason.

5.4.81 Abnormal-Finish-Warning
AVP Name Abnormal-Finish-Warning

AVP Code 811

Vendor ID 2011

AVP Type UTF8String

It is an AVP defined by Huawei Technologies Co., This AVP indicates the session failure information
contained in the Warning header field of SIP messages. It is contained only in CCR(Terminate).

5.4.82 Abnormal-Finish-Reason
AVP Name Abnormal-Finish-Reason

AVP Code 812

Issue (2012-11-30) Huawei Proprietary and Confidential 56

Vendor ID 2011

AVP Type UTF8String

It is an AVP defined by Huawei Technologies Co., This AVP indicates the session failure information
contained in the Reason header field of SIP messages. It is contained only in CCR(Terminate).

5.4.83 Carrier-Select-Routing-Information
AVP Name Carrier-Select-Routing-Information

AVP Code 2023

Vendor ID 10415

AVP Type UTF8String

This AVP indicates the carrier selection code.

CCRs contain this AVP only when subscribers of the MO side use the Carrier Selection on Call by Call
(CBC) or Carrier Pre-Selection (CPS) service and the initial INVITE message received from the MT
side carries the CIC parameter.

5.4.84 Session-Priority
AVP Name Session-Priority

AVP Code 650

Vendor ID 10415

AVP Type Unsigned32

The Session-Priority AVP indicates to the HSS the session's priority. The following values are defined:
PRIORITY-0 (0)
PRIORITY-1 (1)
PRIORITY-2 (2)
PRIORITY-3 (3)
PRIORITY-4 (4)
PRIORITY-0 is the highest priority.

Issue (2012-11-30) Huawei Proprietary and Confidential 57

5.5 Work Flow

5.5.1 Online Charging Flow for the ATS + OCS Solution

Corresponding to the same S-CSCF of MO or MT

S-CSCF ATS OCS S-CSCF

INVITE

D1:CCR(initial)
D2:CCA(initial)
INVITE
180
180
200 OK

D3:CCR(update)
D4:CCA(update)
200 OK
ACK
ACK

Caller and callee in conversation

D5:CCR(update)
D6:CCA(update)

BYE

D7:CCR(termination)
BYE
D8:CCA(termination)

200 OK
200 OK

The online-charging flow for the ATS + OCS solution is as follows:

D1: After the ATS receives the INVITE message, the ATS requests the authorization for
the subscriber session using the CCR (initial) message.
D2: The OCS calculates the traffic usage according to the subscriber’s balance and rate
policy that the subscriber has ordered, and then delivers the traffic usage to the ATS
through the CCA (initial).
D3: After the ATS receives the 200 response for the INVITE message, the ATS requests
the quota for the subscriber through the CCR (update) message.
D4: The OCS returns the CCA (update) message to the ATS with the GSU.

Issue (2012-11-30) Huawei Proprietary and Confidential 58

D5: After the GSU expires, the ATS requests the quota for the subscriber through the
CCR (update) message with the USU.
D6: The OCS returns the CCA (update) message to the ATS with the GSU.
D7: After receiving the BYE message, the ATS requests the termination of the SIP
session using the CCR (termination) message with the USU.
D8: The OCS returns the CCA (termination) message to the ATS.

5.5.2 Configuring Data for Interworking Between the ATS

and an External OCS
Task Description
Configure two links for interworking between the ATS and an external OCS. Use the IP
interworking mode and the direct connection mode.

Scripts
MOD ATS: ATSID=0, AOCTYPE=Extern_ocs;
//Add the OCS device data.
ADD DMDEV: ATSID=0, DEVID=2, DEVTP=OCS, DN="OCS-main",
HN="ocs-0.home1.com", RN="home1.com", SVCID="0";
//Add the OCS link set data.
ADD DMLKS: DEVID=2, LKSID=0, LKSN="OCSmain-lks";
//Add the OCS link data.
ADD DMLNK: DEVID=2, LKSID=0, LNKID=1, LNKN="TO_OCS1", MID=501,
IPTP=IPV4, ADDRID1=0, LPORT=6300, PIP41="200.1.1.34";
ADD DMLNK: DEVID=2, LKSID=0, LNKID=2, LNKN="TO_OCS2", MID=502,
IPTP=IPV4, ADDRID1=0, LPORT=6302, PIP41="200.1.1.34";
ADD DMLNK: DEVID=2, LKSID=0, LNKID=3, LNKN="TO_OCS3", MID=503,
IPTP=IPV4, ADDRID1=0, LPORT=6301, PIP41="200.1.1.34";
ADD DMLNK: DEVID=2, LKSID=0, LNKID=4, LNKN="TO_OCS4", MID=504,
IPTP=IPV4, ADDRID1=0, LPORT=6303, PIP41="200.1.1.34";

Issue (2012-11-30) Huawei Proprietary and Confidential 59

A Result-Code Definition

Result-Code Result-Code Name Description

1001 DIAMETER_MULTI_ This informational error is returned by a Diameter server to
ROUND_AUTH inform the access device that the authentication mechanism
being used requires multiple round trips, and a subsequent
request needs to be issued for access to be granted.
2001 DIAMETER_SUCCES The request is successfully completed.
S
2002 DIAMETER_LIMITED When returned, the request is successfully completed, but
_SUCCESS additional processing is required by the application to provide
service to the user.
3001 DIAMETER_COMMA The request contains a Command-Code that the receiver does
ND_UNSUPPORTED not recognize or support. This must be used when a Diameter
node receives an experimental command that it does not
understand.
3002 DIAMETER_UNABLE This error is given when Diameter cannot deliver the message to
_TO_DELIVER the destination, either because no host within the realm
supporting the required application is available to process the
request, or because Destination-Host AVP is given without the
associated Destination-Realm AVP.
3003 DIAMETER_REALM_ The intended realm of the request is not recognized.
NOT_SERVED
3004 DIAMETER_TOO_BU When returned, a Diameter node attempts to send the message to
SY an alternate peer. This error must only be used when a specific
server is requested, and it cannot provide the requested service.
3005 DIAMETER_LOOP_D An agent detected a loop while trying to get the message to the
ETECTED intended recipient. The message may be sent to an alternate peer,
if one is available, but the peer reporting the error has identified
a configuration problem.
3006 DIAMETER_REDIRE A redirect agent has determined that the request cannot be
CT_INDICATION satisfied locally and the initiator of the request sends the request
directly to the server, whose contact information has been added
to the response. When set, the Redirect-Host AVP must be
present.
3007 DIAMETER_APPLIC A request is sent for an application that is not supported.
ATION_UNSUPPORT
ED

Issue (2012-11-30) Huawei Proprietary and Confidential 60

Result-Code Result-Code Name Description

3008 DIAMETER_INVALI A request is received whose bits in the Diameter header were
D_HDR_BITS either set to an invalid combination, or to a value that is
inconsistent with the command code definition.
3009 DIAMETER_INVALI A request is received that included an AVP whose flag bits are
D_AVP_BITS set to an unrecognized value, or that is inconsistent with the
AVP definition.
3010 DIAMETER_UNKNO A Capabilities-Exchange-Request (CER) is received from an
WN_PEER unknown peer.
4001 DIAMETER_AUTHEN The authentication process for the user failed, most likely due to
TICATION_REJECTE an invalid password used by the user. Further attempts must be
D tried only after prompting the user for a new password.
4002 DIAMETER_OUT_OF A Diameter node receives the accounting request but is unable to
_SPACE commit it to stable storage due to a temporary lack of space.
4003 ELECTION_LOST The peer has determined that it has lost the election process and
has therefore disconnected the transport connection.
5001 DIAMETER_AVP_UN The peer receives a message that contained an AVP that is not
SUPPORTED recognized or supported and is marked with the mandatory bit. A
Diameter message with this error must contain one or more
Failed-AVP AVP containing the AVPs that caused the failure.
5002 DIAMETER_UNKNO The request contains an unknown Session-Id.
WN_SESSION_ID
5003 DIAMETER_AUTHO A request is received for which the user cannot be authorized.
RIZATION_REJECTE This error may occur if the service requested is not permitted to
D the user.
5004 DIAMETER_INVALI The request contains an AVP with an invalid value in its data
D_AVP_VALUE portion. A Diameter message indicating this error must include
the offending AVPs within a Failed-AVP AVP.
5005 DIAMETER_MISSING The request does not contain an AVP that is required by the
_AVP Command Code definition. If this value is sent in the
Result-Code AVP, a Failed-AVP AVP is included in the
message. The Failed-AVP AVP must contain an example of the
missing AVP complete with the Vendor-ID if applicable. The
value field of the missing AVP is of the minimum length and
contains zeros.
5006 DIAMETER_RESOUR A request is received that cannot be authorized because the user
CES_EXCEEDED has already expended allowed resources. An example of this
error condition is a user that is restricted to one dial-up PPP port,
attempts to establish a second PPP connection.
5007 DIAMETER_CONTRA The home Diameter server has detected AVPs in the request that
DICTING_AVPS contradicted each other, and provides services to the user. One
or more Failed-AVP AVPs must be present, containing the
AVPs that contradicted each other.

Issue (2012-11-30) Huawei Proprietary and Confidential 61

Result-Code Result-Code Name Description

5008 DIAMETER_AVP_NO A message is received with an AVP that must not be present.
T_ALLOWED The Failed-AVP AVP must be included and contain a copy of
the offending AVP.
5009 DIAMETER_AVP_OC A message is received that included an AVP that appeared more
CURS_TOO_MANY_ often than permitted in the message definition. The Failed-AVP
TIMES AVP must be included and contain a copy of the first instance of
the offending AVP that exceeded the maximum number of
occurrences.
5010 DIAMETER_NO_CO This error is returned when a CER message is received, and
MMON_APPLICATIO there are no common applications supported between the peers.
N
5011 DIAMETER_UNSUPP This error is returned when a request is received, whose version
ORTED_VERSION number is unsupported.
5012 DIAMETER_UNABLE This error is returned when a request is rejected for unspecified
_TO_COMPLY reasons.
5013 DIAMETER_INVALI This error is returned when an unrecognized bit in the Diameter
D_BIT_IN_HEADER header is set to 1.
5014 DIAMETER_INVALI The request contains an AVP with an invalid length. A Diameter
D_AVP_LENGTH message indicating this error must include the offending AVPs
within a Failed-AVP AVP.
5015 DIAMETER_INVALI This error is returned when a request is received with an invalid
D_MESSAGE_LENGT message length.
H
5016 DIAMETER_INVALI The request contains an AVP with which is not allowed to have
D_AVP_BIT_COMBO the given value in the AVP Flags field. A Diameter message
indicating this error must include the offending AVPs within a
Failed-AVP AVP.
5017 DIAMETER_NO_CO This error is returned when a CER message is received, and
MMON_SECURITY there are no common security mechanisms supported between
the peers. A Capabilities-Exchange-Answer (CEA) must be
returned with the Result-Code AVP set to
DIAMETER_NO_COMMON_SECURITY.

Issue (2012-11-30) Huawei Proprietary and Confidential 62

Technical White Paper For Huawei SPS Signaling Accounting
No ratings yet
Technical White Paper For Huawei SPS Signaling Accounting
31 pages
HUAWEI SIG9800 V300R001C00 Configuration Guide 01 PDF
No ratings yet
HUAWEI SIG9800 V300R001C00 Configuration Guide 01 PDF
1,010 pages
(Basic Training) ATS9900 Product Introduction ISSUE5.00
50% (2)
(Basic Training) ATS9900 Product Introduction ISSUE5.00
52 pages
LTE QCI Mapping
No ratings yet
LTE QCI Mapping
32 pages
CloudSE2980 V500R021C10 Product Overview - Huawei Enterprise
100% (1)
CloudSE2980 V500R021C10 Product Overview - Huawei Enterprise
76 pages
OCS DCC Description
100% (2)
OCS DCC Description
39 pages
HUAWEI CG9812 V300R001 Product Description
0% (2)
HUAWEI CG9812 V300R001 Product Description
26 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
Martis Networks Elements
100% (1)
Martis Networks Elements
14 pages
GSM R Hlr9820
No ratings yet
GSM R Hlr9820
0 pages
CG9812 V500R006C10 Feature Description
No ratings yet
CG9812 V500R006C10 Feature Description
79 pages
CGP V200R002C10 MML Command Hidden Parameters
No ratings yet
CGP V200R002C10 MML Command Hidden Parameters
26 pages
Huawei VTR PCRF Function Requirement Specification 20120118
No ratings yet
Huawei VTR PCRF Function Requirement Specification 20120118
51 pages
Guide To Application For BSC6900 License-20110531-A-V4.1
No ratings yet
Guide To Application For BSC6900 License-20110531-A-V4.1
64 pages
CS Fallback (ERAN3.0 06)
No ratings yet
CS Fallback (ERAN3.0 06)
130 pages
BTS3900 V100R008C00SPC220 (ENodeB) Performance Counter Reference
No ratings yet
BTS3900 V100R008C00SPC220 (ENodeB) Performance Counter Reference
2,162 pages
PCRF Information: UPCC Service Analysis
No ratings yet
PCRF Information: UPCC Service Analysis
7 pages
BSC6900 GSM Commissioning Guide (V900R011C00 - 01)
No ratings yet
BSC6900 GSM Commissioning Guide (V900R011C00 - 01)
70 pages
HUAWEI CBS Performance Metrics Reference - (R002C02LLA302 - 01, Laos-ETL) PDF
No ratings yet
HUAWEI CBS Performance Metrics Reference - (R002C02LLA302 - 01, Laos-ETL) PDF
155 pages
HLR9820 System Overview
No ratings yet
HLR9820 System Overview
29 pages
HUAWEI UGW9811 Unified Gateway V900R010C00 Feature Description (Basic Feature)
No ratings yet
HUAWEI UGW9811 Unified Gateway V900R010C00 Feature Description (Basic Feature)
351 pages
Number Analysis
No ratings yet
Number Analysis
11 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
Asterisk Sip Session Timers
No ratings yet
Asterisk Sip Session Timers
15 pages
ATS9900 V500R021C10SPC100 Product Description - Huawei Enterprise
0% (1)
ATS9900 V500R021C10SPC100 Product Description - Huawei Enterprise
78 pages
MSOFTX3000 Product Training Practice Exercise Guide
No ratings yet
MSOFTX3000 Product Training Practice Exercise Guide
70 pages
RAN17.1 Reconfiguration Guide For BSC6900 (03) (PDF) - en
No ratings yet
RAN17.1 Reconfiguration Guide For BSC6900 (03) (PDF) - en
382 pages
Imaster Nce v100r019c10spc200 Tl1 Nbi User Guide 01
No ratings yet
Imaster Nce v100r019c10spc200 Tl1 Nbi User Guide 01
5,203 pages
2015CustomerTrainingCatalog CourseDescriptions (CN USC)
No ratings yet
2015CustomerTrainingCatalog CourseDescriptions (CN USC)
56 pages
HLR9820 Maintenance Manual-Emergency Maintenance
No ratings yet
HLR9820 Maintenance Manual-Emergency Maintenance
99 pages
4 G
No ratings yet
4 G
189 pages
CS10.0 Introduction To MSOFTX3000 V200R010C00
No ratings yet
CS10.0 Introduction To MSOFTX3000 V200R010C00
28 pages
CSSR Analysis
No ratings yet
CSSR Analysis
14 pages
GBSS15.0 Optional Feature Description
No ratings yet
GBSS15.0 Optional Feature Description
394 pages
HSS9860 V9R8C00 Data Configuration and O&M (LTE) - 20121015-B-V1.0
No ratings yet
HSS9860 V9R8C00 Data Configuration and O&M (LTE) - 20121015-B-V1.0
49 pages
0aa000008 Ss7 Protocol Issue2.0
No ratings yet
0aa000008 Ss7 Protocol Issue2.0
49 pages
Call Reestablishment (RAN18.1 01)
No ratings yet
Call Reestablishment (RAN18.1 01)
412 pages
Huawei - Configuring Signaling Transport Data
No ratings yet
Huawei - Configuring Signaling Transport Data
100 pages
IGWB
No ratings yet
IGWB
8 pages
Base Station OMCH Self-Recovery (SRAN10.1 - 02)
No ratings yet
Base Station OMCH Self-Recovery (SRAN10.1 - 02)
30 pages
RAN Network Optimization Parameter Reference (RAN5.1)
No ratings yet
RAN Network Optimization Parameter Reference (RAN5.1)
248 pages
U2000 ATAE Cluster System Administrator Guide (SUSE) (V200R016C10 - 05) PDF
No ratings yet
U2000 ATAE Cluster System Administrator Guide (SUSE) (V200R016C10 - 05) PDF
761 pages
¡ IMS 8.2¡¿SPG2800 Version Differences (Between R3C02 and R3C01)
No ratings yet
¡ IMS 8.2¡¿SPG2800 Version Differences (Between R3C02 and R3C01)
23 pages
Bsc6910 Umts LMT User Guide (v100r015c00 - 09) (PDF) - en
100% (1)
Bsc6910 Umts LMT User Guide (v100r015c00 - 09) (PDF) - en
342 pages
Huawei LTE CS Fallback Feature
No ratings yet
Huawei LTE CS Fallback Feature
99 pages
RAN17 1 Troubleshooting Guide 01 PDF en
No ratings yet
RAN17 1 Troubleshooting Guide 01 PDF en
249 pages
Quick Guide To DC-HSDPA
No ratings yet
Quick Guide To DC-HSDPA
5 pages
Huawei LTE KPI Ref
No ratings yet
Huawei LTE KPI Ref
50 pages
Alarm Description: HUAWEI SE2900 Session Border Controller
No ratings yet
Alarm Description: HUAWEI SE2900 Session Border Controller
32 pages
LTE PP Slides
67% (3)
LTE PP Slides
13 pages
Oeb9fa331 Usn9810 v900r015c10 (Mme SGSN) Basic Service Configuration Issue1.00
No ratings yet
Oeb9fa331 Usn9810 v900r015c10 (Mme SGSN) Basic Service Configuration Issue1.00
153 pages
Huawei BSS KPI Reference
No ratings yet
Huawei BSS KPI Reference
68 pages
Handover Algorithm and Parameters
No ratings yet
Handover Algorithm and Parameters
59 pages
Diameter Protocol A Complete Guide
From Everand
Diameter Protocol A Complete Guide
Gerardus Blokdyk
No ratings yet
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
IP Multimedia Subsystem IMS A Complete Guide
From Everand
IP Multimedia Subsystem IMS A Complete Guide
Gerardus Blokdyk
No ratings yet
ATS9900 V100R006C00 Feature List FT
No ratings yet
ATS9900 V100R006C00 Feature List FT
14 pages
ATM Transport (RAN15.0 01)
No ratings yet
ATM Transport (RAN15.0 01)
103 pages
Huawei 8950 Datasheet
No ratings yet
Huawei 8950 Datasheet
4 pages
Huawei Video Phone 8950 Datasheet
No ratings yet
Huawei Video Phone 8950 Datasheet
4 pages
ATM Transport (RAN15.0 03)
No ratings yet
ATM Transport (RAN15.0 03)
180 pages
ATM Transport (RAN19.1 01)
No ratings yet
ATM Transport (RAN19.1 01)
180 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
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
MRP6600 V100R005C01 Feature Description
No ratings yet
MRP6600 V100R005C01 Feature Description
206 pages
SPS V300R007C10 Part III Appendix
No ratings yet
SPS V300R007C10 Part III Appendix
7 pages
SPS V300R007C10 Part II Operation Guide (Special)
No ratings yet
SPS V300R007C10 Part II Operation Guide (Special)
63 pages
01-14 Sip
100% (1)
01-14 Sip
20 pages
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
sd2 l7 Capture
No ratings yet
sd2 l7 Capture
67 pages
Cylinder Cutout
No ratings yet
Cylinder Cutout
3 pages
External NCR Monitoring
No ratings yet
External NCR Monitoring
7 pages
Shivam Real
No ratings yet
Shivam Real
2 pages
NCTB 2010 Class V English For Today
100% (1)
NCTB 2010 Class V English For Today
147 pages
Lista de Precios Farmacos 27-04-2022
No ratings yet
Lista de Precios Farmacos 27-04-2022
5 pages
Philips M-Power Style Hedquarter
No ratings yet
Philips M-Power Style Hedquarter
44 pages
Instructions For UG 1 & 5 Semester Examination 2023 December
No ratings yet
Instructions For UG 1 & 5 Semester Examination 2023 December
2 pages
Immediate download Instrumentation, Measurement and Analysis 4th Edition Chaudhary Nakra ebooks 2024
100% (1)
Immediate download Instrumentation, Measurement and Analysis 4th Edition Chaudhary Nakra ebooks 2024
55 pages
Configuring and Implementing Automatic External
No ratings yet
Configuring and Implementing Automatic External
9 pages
Soliciting Letter To Auditor
No ratings yet
Soliciting Letter To Auditor
1 page
Krull - LVL 2
No ratings yet
Krull - LVL 2
5 pages
EY Business Case
No ratings yet
EY Business Case
6 pages
Atg Worksheet Thisthatthesethose
No ratings yet
Atg Worksheet Thisthatthesethose
2 pages
A Semi-Detailed Lesson Plan in Mathematics Grade 10
No ratings yet
A Semi-Detailed Lesson Plan in Mathematics Grade 10
3 pages
BC Ministry of Energy, Mines and Low Carbon Innovation Service Plan
No ratings yet
BC Ministry of Energy, Mines and Low Carbon Innovation Service Plan
14 pages
View / Download Account Statement: Savings Account No.: 16751140002568, MEMNAGAR
100% (1)
View / Download Account Statement: Savings Account No.: 16751140002568, MEMNAGAR
2 pages
1LE1002 1BB23 4AA4 Z H22 Datasheet en
No ratings yet
1LE1002 1BB23 4AA4 Z H22 Datasheet en
2 pages
5c8eb52f2e 53eb9b926d
No ratings yet
5c8eb52f2e 53eb9b926d
61 pages
Lgs Summative 1.1
No ratings yet
Lgs Summative 1.1
4 pages
TR Hairdressing NC III
No ratings yet
TR Hairdressing NC III
85 pages
Vostro-A860 Service Manual En-Us
No ratings yet
Vostro-A860 Service Manual En-Us
36 pages
How To Prepare Ir Samples
No ratings yet
How To Prepare Ir Samples
3 pages
Climate of The Philippines
100% (1)
Climate of The Philippines
8 pages
Monzo Bank Statement 2022 03 01-2022 03 08 1311
No ratings yet
Monzo Bank Statement 2022 03 01-2022 03 08 1311
5 pages
Key Selection Criteria
No ratings yet
Key Selection Criteria
5 pages
Password Recovery Procedure For The Cisco 1700 and 1800 Series Routers - Cis
No ratings yet
Password Recovery Procedure For The Cisco 1700 and 1800 Series Routers - Cis
7 pages
Biobase Proforma Invoice For YSI Pharmaceuticals 20240508
No ratings yet
Biobase Proforma Invoice For YSI Pharmaceuticals 20240508
1 page
Chapter 2 - Ricardian Model
No ratings yet
Chapter 2 - Ricardian Model
9 pages