ZTE Online Charging Interface

Specification (Diameter)

Prepared by:
ZTESoft Technology Co., LTD, P.R
China

(Document Version: V1.0)

 ZTE Online Charging Interface-Diameter v1.0_Kenya

Document History

Doc. No. Ver. no. Editor revision Date Modification

1 v0.1 Frank 10 Jan 2009

© 2003－2007 ZTEsoft
This document contains proprietary and confidential information of ZTEsoft and shall not be reproduced or
transferred to other documents, disclosed to others, or used for any purpose other than that for which it is furnished,
without the prior written consent of ZTEsoft. It shall be returned to the respective ZTEsoft companies upon
request.
The trademark and service marks of ZSmart, including the ZSmart mark and logo, are the exclusive property of
ZTEsfot, and may not be used without permission. All other marks mentioned in this material are the property of
their respective owners.

Document Information
Software Version: 7.0
Publication Date: December 2007
Catalog Number:

Page 2 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

Content

1 Foreword................................................................................................................................................5

2 Scope .....................................................................................................................................................5

3 Architecture Considerations................................................................................................................6

3.1 High level architecture .............................................................................................................6

3.1.1 Charging related transfer requirements..................................................................... 7

4 Charging Applications Requirements ................................................................................................9

4.1 Online Charging scenarios......................................................................................................9

4.1.1 Basic principles .............................................................................................................9

4.1.2 Charging Scenarios....................................................................................................10

5 ZTE Online Charging Interface Definition .......................................................................................29

5.1 Message formats for ZTE Online Charging ........................................................................29

5.1.1 Summary of Online Charging Message Formats...................................................29

5.1.2 Credit-Control-Request Message.............................................................................30

5.1.3 Credit-Control-Answer Message ..............................................................................41

5.1.4 Capabilities-Exchange-Request Message ..............................................................47

5.1.5 Capabilities-Exchange-Answer Message ...............................................................47

5.1.6 Device-Watchdog-Request Message .............................................................................48

5.1.7 Device-Watchdog-Answer Message........................................................................48

5.1.8 Disconnect-Peer-Request Message ........................................................................49

5.1.9 Disconnect-Peer-Answer Message..........................................................................49

6 AVP Definition ......................................................................................................................................50

6.1 Session-Id..................................................................................................................................50

6.2 Origin-Host................................................................................................................................50

6.3 Origin-Realm.............................................................................................................................51

6.4 Destination-Host........................................................................................................................51

6.5 Destination-Realm.....................................................................................................................51

6.6 Auth-Application-Id ..................................................................................................................52

Page 3 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

6.7 Service-Context-Id ....................................................................................................................52

6.8 CCR-Type..................................................................................................................................53

6.9 CCR-Request-Number ..............................................................................................................54

6.10 Event-Timestamp ......................................................................................................................55

6.11 Subscription-Id ..........................................................................................................................55

6.12 Subscription-Id-Type.................................................................................................................55

6.13 Subscription-Id-Data .................................................................................................................56

6.14 Call-Type...................................................................................................................................56

6.15 Requested-Action ......................................................................................................................57

6.16 Service-Identifier.......................................................................................................................58

6.17 OA-Subscription-Id...................................................................................................................58

6.18 DA-Subscription-Id...................................................................................................................59

6.19 SMSC-Address..........................................................................................................................60

6.20 SM-Id ........................................................................................................................................60

6.21 SM-Length ................................................................................................................................61

6.22 Result-Notification-Type...........................................................................................................61

7 Definitions, Symbols and Abbreviations..........................................................................................62

7.1 Definitions ................................................................................................................................62

7.2 Symbols ...................................................................................................................................62

7.3 Abbreviations...........................................................................................................................62

8 References ..........................................................................................................................................64

Page 4 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

1 Foreword
This Technical Specification has been produced by ZTE (ZTESoft System Department).It

is divided into six parts, first section describe the scope of document, in second section we

discussed ZTE OCS Architecture Consideration, third section describes ZTE OCS charging

application requirements. In fourth section we discussed detail regarding ZTE Online charging

interfaces. Fifth section contains Abbreviation, Symbols and definitions used in this document.

Finally we have given the details about references documents.

2 Scope
The present document is part of a series of documents that specify charging functionality

and charging management in GSM/UMTS networks.

This document contains the most familiar scenarios of Online Charging and the definition of

Online Charging interface. Also we have discussed the detail OCS Architecture and it is

charging related transfer requirements.

Page 5 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

3 Architecture Considerations
3.1 High level architecture
The Rf and Ro are reference points from the Charging Trigger Function (CTF) to the

Charging Data Function (CDF) and the Online Charging Function (OCF) respectively, and are

intended for the transport of charging events. Rf is used for offline charging whereas Ro is

used for online charging. The following figures show the position of the Rf and Ro reference

points within the overall ZTE online and offline charging architecture.

3GPP network

CN
Domain
Rf
C C C
Service Rf Ga Bx
T G Billing
nodes D
Domain
F
F F
Sub-
system Rf

CTF: Charging Trigger Function

CDF: Charging Data Function

CGF: Charging Gateway Function

BD: Billing Domain. This may also be a billing mediation device / post-processing system.

Figure 3.1.1: Logical ubiquitous offline charging architecture

Page 6 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

3GPP network

CN
Domain
Ro
C O
Ga C Bo
Service Ro
T G Billing
nodes C
Domain
F
F F
Sub-
system Ro

CTF: Charging Trigger Function

OCF: Online Charging Function

CGF: Charging Gateway Function

BD: Billing Domain. This may also be a billing mediation device / post-processing system.

Figure 3.1.2: Logical ubiquitous online charging architecture

Different mappings of the ubiquitous offline charging functions, CTF, CDF and CGF, onto

physical implementations are possible. Further details of the configuration refer to 3GPP TS

32.240 [1]. Details of the implementation options per domain / subsystem / service are

specified in the respective middle tier TS.

3.1.1 Charging related transfer requirements

Each CTF would have CDF and OCF address list to which it can send its charging events

and/or charging requests. The list will be organized in address priority order. If the primary

charging function is not available (e.g., out of service) then the CTF shall send the charging

information to the secondary charging function.

Within the scope of this release, each network element that generates charging

information will send the information only to the charging entities of the same PLMN, and not

to charging entities in other PLMNs.

Page 7 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

Each CDF in the PLMN may know of other CDFs' network addresses (e.g., for

redundancy reasons, to be able to recommend another CDF address with the Redirection

Request message). This is achieved by OAM&P configuration facilities that will enable each

CDF to have a configurable list of peer CDF addresses.

Page 8 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

4 Charging Applications Requirements

4.1 Online Charging scenarios
Online charging for both events and sessions between CTF and the OCF is performed

using the Ro reference point. The Ro reference point supports integrity protection and

authentication for the case that the CTF is outside the operator domain.

4.1.1 Basic principles

There are two sub-functions for online charging that affect online charging principles and

require a more detailed description: rating and unit determination. Both rating and unit

determination can be implemented centralized, i.e. on the OCF, or decentralized, that is, on

the CTF.

Unit determination refers to the calculation of the number of non-monetary units (service

units, data volume, time and events) that shall be assigned prior to starting service delivery.

 With Centralized Unit Determination, the OCF determines the number of

non-monetary units that a certain service user can consume based on a service

identifier received from the CTF.

 With the Decentralized Unit Determination approach, the CTF determines itself

how many units are required to start service delivery, and requests these units

from the OCF.

After checking the service user's account balance, the OCF returns the number of granted

units to the CTF. The CTF is then responsible for the supervision of service delivery.

Particularly, the CTF shall limit service delivery to the corresponding number of granted units.

Rating refers to the calculation of a price out of the non-monetary units calculated by the unit

determination function.

 With the Centralized Rating approach, the CTF and the OCF exchange

information about non-monetary units. The OCF translates these units into

monetary units.

 With the Decentralized Rating approach, the corresponding rating control is

performed within the CTF. Consequently, CTF and OCF exchange information

Page 9 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

about monetary units.

Three cases for online charging can be distinguished:

1. Immediate event charging (IEC)

2. Event charging with unit reservation (ECUR)

3. Session charging with unit reservation (SCUR)

4.1.2 Charging Scenarios

In order to perform event charging via Ro, the scenarios between the involved entities UE-A,

OCF and CTF need to be defined. The charging flows shown in this sub clause include

scenarios with immediate event charging and event charging with reservation. In particular,

the following cases are shown:

1 Immediate Event Charging

a) Decentralized Unit Determination and Centralized Rating

b) Centralized Unit Determination and Centralized Rating

c) Decentralized Unit Determination and Decentralized Rating

2 Event charging with Reservation

a) Decentralized Unit Determination and Centralized Rating

b) Centralized Unit Determination and Centralized Rating

c) Decentralized Unit Determination and Decentralized Rating

3 Session charging with Reservation

a) Decentralized Unit Determination and Centralized Rating

b) Centralized Unit Determination and Centralized Rating

c) Decentralized Unit Determination and Decentralized Rating

Page 10 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

4.1.2.1 Immediate Event Charging

4.1.2.1.1 Decentralized Unit Determination and Centralized Rating

In the following scenario, CTF asks the OCF to assign a defined number of units.
UE-A OCF CTF

1. Request for resource usage

Credit Unit
Control 2. Units
Determination

3. Debit Units Request (Non-monetary Units)

4. Rating
Control

5. Account
Control
6. Debit Units Response (Non-monetary Units)

7. Content/Service Delivery

8. Credit Unit Control (cont.)

10. Session released

Figure 4.1.2.1.1: ZTE OCS Immediate Event Charging with Centralized Rating and

Decentralized Unit Determination

1. Request for Resource Usage: UE-A requests the desired resource from the network

element.

2. Units Determination: depending on the requested service the CTF determines the

number of units accordingly.

3. Debit Units Request: the CTF requests the OCF to assign the defined number of units.

4. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units that represents the price for the number of units determined in item 2.

Page 11 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5. Account Control: Provided that the user's credit balance is sufficient, the OCF triggers the

deduction of the calculated amount from the subscriber's account.

6. Debit Units Response: The OCF informs the CTF of the number of granted units.

7. Content/Service Delivery: The CTF delivers the content/service at once, in fractions or in

individually chargeable items, corresponding to the number of granted units.

8. Credit Unit Control (cont.): This function block is optional and a replication of items 2 to 6.

9. Content/Service Delivery (cont.): The continuation of content delivery occurs in

correspondence with the occurrence of item 8.

10. Session released: Session is released.

Page 12 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

4.1.2.1.2 Centralized Unit Determination and Centralized Rating

In the following scenario, CTF asks the OCF to assign units based on the service identifier

specified by the CTF.

UE-A OCF CTF

1. Request for resource usage

Credit Service
Control 2. Debit Units Request (Service Key)

3. Units
Determination

4. Rating
Control

5. Account
Control
6. Debit Units Response (Non-monetary Units)

7. Content/Service Delivery

8. Credit Service Control (cont.)

9. Content/Service Delivery (cont.)

10. Session released

Figure 4.1.2.1.2: ZTE OCS Immediate Event Charging with Centralized Rating and

Centralized Unit Determination

1. Request for resource usage: The UE-A requests the desired resource or content from the

network element.

2. Debit Units Request: Depending on the service requested by the UE-A, the CTF selects the

service identifier and forwards the Debit Units Request to the OCF.

3. Units Determination: The OCF determines the number of non-monetary units needed for

the content/service delivery, based on the received service key.

4. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

Page 13 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

units that represent the price for the number of units determined in item 3.

5. Account Control: Provided that the user's credit balance is sufficient, the OCF triggers the

deduction of the calculated amount from the subscriber's account.

6. Debit Units Response: The OCF informs the CTF of the number of granted units. This

includes the case where the number of units granted indicates the permission to render the

service that was identified by the received service key.

7. Content/Service Delivery: The CTF delivers the content/service at once, in fractions or in

individually chargeable items, corresponding to the number of granted units.

8. Credit Service Control (cont.): This function block is optional and a replication of items 2to6.

9. Content/Service Delivery (cont.): The continuation of content delivery occurs in

correspondence with the occurrence of item 8.

10. Session released: The session is released.

4.1.2.1.3 Decentralized Unit Determination and Decentralized Rating

In the following scenario, the CTF asks the OCF to assure the deduction of an amount of the

specified number of monetary units from the subscriber's account.

Page 14 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

UE-A OCF CTF

1. Request for resource usage

Credit Amount
Control 2. Units
Determination

3. Rating
Control
4. Debit Units Request(Monetary Units)

5. Account
Control
6. Debit Units Response(Monetary Units)

7. Content/Service Delivery

8. Credit Amount Control (cont.)

9. Content/Service Delivery (cont.)

10. Session released

Figure 4.1.2.1.3: ZTE OCS Immediate Event Charging with Decentralized Rating and

Decentralized Unit Determination

1. Request for resource usage: The UE-A requests the desired content from the network

element.

2. Units Determination: Depending on the service requested by the UE-A, the CTF

determines the number of units accordingly.

3. Rating Control: The CTF calculates the number of monetary units that represent the price

for the number of units determined in item 2.

4. Debit Units Request: The CTF requests the OCF to assure the deduction of an amount

corresponding to the calculated number of monetary units from the subscriber's account.

5. Account Control: Provided that the user's credit balance is sufficient, the OCF triggers the

deduction of the calculated amount from the subscriber's account.

6. Debit Units Response: The OCF indicates to the CTF the number of deducted monetary

Page 15 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

units.

7. Content/Service Delivery: The CTF delivers the content/service at once, in fractions or in

individually chargeable items, corresponding to the number of units as specified in items 2

and 3.

8. Credit Amount Control (cont.): This function block is optional and a replication of items 2

to 6.

9. Content/Service Delivery (cont.): The continuation of content delivery occurs in

correspondence with the occurrence of item 8.

10. Session released: The session is released.

4.1.2.1.4 Further Options

In addition to the flows that are specified in the previous sub clauses, the Debit Unit operation

may alternatively be carried out concurrently with service delivery, or after completion of

service delivery.

4.1.2.2 Event charging with Reservation

4.1.2.2.1 Decentralized Unit Determination and Centralized Rating

In the following scenario, the CTF requests the reservation of units prior to service delivery. An

account debit operation is carried out following the conclusion of service delivery.

Page 16 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

UE-A OCF CTF

1. Request for resource usage

2. Units
Determination

3. Reserve Units Request (Non-monetary Units)

4. Rating
Control

5. Account
Control

6.Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Reserved Units
Supervision

9. Content/Service Delivery

10. Debit Units Request (Non-monetary Units)

11. Rating
Control

12. Account
Control

13. Debit Units Response (Non-monetary Units)

14. Session released

Figure 4.1.2.2.1: ZTE OCS Event Charging with Reservation / Decentralized Unit

Determination and Centralized Rating

1. Request for resource usage: The UE-A requests the desired content/service from the NE.

2. Units Determination: Depending on the requested service the CTF determines the

number of units accordingly.

3. Reserve Units Request: The CTF requests the OCF to reserve the number of units

determined in item 2.

4. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units that represents the price for the number of units determined in item 2.

Page 17 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5. Account Control: The OCF checks whether the user's account balance is sufficient for the

requested reservation.

6. Reservation Control: If the user's account balance is sufficient then the corresponding

reservation is made.

7. Reserve Units Response: The OCF informs the CTF of the reserved number of units.

Items 3 to 7 may be repeated several times.

8. Reserved Units Supervision: Simultaneously with the service delivery, the CTF monitors

the consumption of the reserved units.

9. Content/Service Delivery: The CTF delivers the content/service at once, in fractions or in

individually chargeable items, corresponding to the reserved number of units.

10. Debit Units Request: The CTF requests the OCF to assure the deduction of an amount

corresponding to the consumed number of units from the subscriber's account. In the case

that no further units are required for this service, an appropriate indication triggering the

release of the remaining reservation is given.

11. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units to deduct from the subscriber's account.

12. Account Control: The OCF triggers the deduction of the calculated amount from the

subscriber's account.

13. Debit Units Response: The OCF informs the CTF of the actually deducted units. Items 10

to 13 may be repeated several times.

14. Session Release: The session is released.

4.1.2.2.2 Centralized Unit Determination and Centralized Rating

In the following scenario, the CTF requests the OCF to reserve units based on the service

identifier specified by the CTF. An account debit operation is carried out following the

conclusion of service delivery.

Page 18 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

UEa OCF CTF

1. Request for resource usage

2. Reserve Units Request (Service Key)

3. Units
Determination

4. Rating Control

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Granted Units
Supervision

9. Content/Service Delivery

10. Debit Units Request (Non-monetary Units)

11. Rating
Control

12. Account
Control
13. Debit Units Response (Non-monetary Units)

14. Session released

Figure 4.1.2.2.2: ZTE OCS Event Charging with Reservation / Centralized Unit

Determination and Centralized Rating

1. Request for resource usage: The UE-A requests the desired content from the CTF.

2. Reserve Units Request: Depending on the service requested by the UE-A, the CTF

selects the service identifier and forwards the Reserve Units Request to the OCF.

3. Units Determination: The OCF determines the number of non-monetary units needed for

the content/service delivery, based on the received service key.

4. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units that represent the price for the number of units determined in item 3.

5. Account Control: The OCF checks whether the user's account balance is sufficient for the
Page 19 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

requested reservation.

6. Reservation Control: If the user's account balance is sufficient, then the corresponding

reservation is made.

7. Reserve Units Response: The OCF informs the CTF of the reserved number of units.

This includes the case where the number of units reserved indicates the permission to render

the service that was identified by the received service key. Items 2 to 7 may be repeated

several times.

8. Granted Units Supervision: Simultaneously with the service delivery, the CTF monitors

the consumption of the reserved units.

9. Content/Service Delivery: The CTF delivers the content/service at once, in fractions or in

individually chargeable items, corresponding to the reserved number of units.

10. Debit Units Request: The CTF provides according to previous Reserve Units Response

either the request to deduct of an amount corresponding to the consumed number of units

from the subscriber's account, or solely the indication of whether the service was successfully

delivered or not. In the case that no further units are required for this service, an appropriate

indication triggering the release of the remaining reservation is given.

11. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units to deduct from the subscriber's account.

12. Account Control: The OCF triggers the deduction of the calculated amount from the

subscriber's account.

13. Debit Units Response: The OCF informs the CTF of the actually deducted units. Items 10

to 13 may be repeated several times.

14. Session Released: The session is released.

4.1.2.2.3 Decentralized Unit Determination and Decentralized Rating

In the following scenario, the CTF request the OCF to assure the reservation of an amount of

the specified number of monetary units from the subscriber's account. An account debit

operation that triggers the deduction the amount from the subscriber's account is carried out

following the conclusion of service delivery.

Page 20 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

UEa OCF CTF

1. Request for resource usage

2. Units
Determination

3. Rating Control

4. Reserve Units Request (Monetary Units)

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Monetary Units)

8. Budget
Control

9. Content/Service Delivery

10. Debit Units Request (Monetary Units)

11. Account
Control

12. Debit Units Response (Monetary Units)

13. Session released

Figure 4.1.2.2.3: ZTE OCS Event Charging with Reservation / Centralized Unit

Determination and Centralized Rating

1. Request for resource usage: The UE-A requests the desired content from the CTF.

2. Units Determination: Depending on the service requested by the UE-A, the CTF

determines the number of units accordingly.

3. Rating Control: The CTF calculates the number of monetary units that represent the price

for the number of units determined in item 2.

4. Reserve Units Request: The CTF requests the OCF to assure the reservation of an

amount corresponding to the calculated number of monetary units from the subscriber's

account.

5. Account Control: The OCF checks whether the user's account balance is sufficient for the

requested reservation.

Page 21 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

6. Reservation Control: If the user's credit balance is sufficient, then the corresponding

reservation is made.

7. Reserve Units Response: The OCF informs the CTF of the reserved number of monetary

units. Items 4 to 7 may be repeated several times.

8. Budget Control: Simultaneously with the service delivery, the CTF monitors the

consumption of the granted amount.

9. Content/Service Delivery: The CTF delivers the content/service at once, in fractions or in

individually chargeable items, corresponding to the number of units.

10. Debit Units Request: The CTF requests the OCF to assure the deduction of an amount

corresponding to the consumed number of monetary units from the subscriber's account.

11. Account Control: The OCF triggers the deduction of the consumed amount from the

subscriber's account.

12. Debit Units Response: OCF indicates to the CTF the number of deducted monetary units.

Items 10 to 12 may be repeated several times.

13. Session Released: Session is released.

4.1.2.3 Session charging with Reservation

4.1.2.3.1 Decentralized Unit Determination and Centralized Rating

In the following scenario, the CTF requests the reservation of units prior to session

supervision. An account debit operation is carried out following the conclusion of session

termination.

Page 22 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

UE-A OCF CTF

1. Request for resource usage

2. Units
Determination

3. Reserve Units Request (Non-monetary Units)

4. Rating
Control

5. Account
Control

6.Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Reserved Units
Supervision

9. Session ongoing

10. Session released

11. Debit Units Request (Non-monetary Units)

12. Rating
Control

13. Account
Control
14. Debit Units Response (Non-monetary Units)

Figure 4.1.2.3.1: ZTE OCS Session Charging with Reservation / Decentralized Unit

Determination and Centralized Rating

1. Request for resource usage: The UE-A requests session establishment from the CTF.

2. Units Determination: Depending on the requested type of the session the CTF

determines the number of units accordingly.

3. Reserve Units Request: CTF requests the OCF to reserve the number of units

determined in item 2

4. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units that represents the price for the number of units determined in item 2.

Page 23 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5. Account Control: OCF checks whether the user's account balance is sufficient for the

requested reservation.

6. Reservation Control: If the user's account balance is sufficient then the corresponding

reservation is made.

7. Reserve Units Response: OCF informs the CTF of the reserved number of units.

8. Reserved Units Supervision: Simultaneously with the ongoing session, the CTF monitors

the consumption of the reserved units.

9. Session ongoing: CTF maintains the session. One or more debit and reserve operations

may be performed when the session is ongoing.

10. Session Release: Session is released

11. Debit Units Request: CTF requests the OCF to assure the deduction of an amount

corresponding to the consumed number of units from the subscriber's account.

12. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units to deduct from the subscriber's account.

13. Account Control: The OCF triggers the deduction of the calculated amount from the

subscriber's account.

14. Debit Units Response: The OCF informs the CTF of the actually deducted units.

4.1.2.3.2 Centralized Unit Determination and Centralized Rating

In the following scenario, the CTF requests the OCF to reserve units based on the session

identifiers specified by the CTF. An account debit operation is carried out following the

conclusion of session.

Page 24 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

UEa OCF CTF

1. Request for resource usage

2. Reserve Units Request (Service Key)

3. Units
Determination

4. Rating Control

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Granted Units
Supervision

9. Session ongoing

10. Session released

11. Debit Units Request (Non-monetary Units)

12. Rating
Control

13. Account
Control

14. Debit Units Response (Non-monetary Units)

Figure 4.1.2.3.2: ZTE OCS Session Charging with Reservation / Centralized Unit

Determination and Centralized Rating

1. Request for resource usage: The UE-A requests the session establishment from the CTF.

2. Reserve Units Request: Depending on the requested type of the session by the UE-A, the

CTF selects the service identifier and forwards the Reserve Units Request to the OCF.

3. Units Determination: OCF determines the number of non-monetary units needed for the

content/service delivery, based on the received service key.

4. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units that represent the price for the number of units determined in item 3.
Page 25 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5. Account Control: OCF checks whether the user's account balance is sufficient for the

requested reservation.

6. Reservation Control: If the user's account balance is sufficient, then the corresponding

reservation is made.

7. Reserve Units Response: OCF informs the CTF of the reserved number of units. This

includes the case where the number of units reserved indicates the permission to render the

service that was identified by the received service key.

8. Granted Units Supervision: Simultaneously with the ongoing session, the CTF monitors

the consumption of the reserved units.

9. Session ongoing: CTF maintains the session. One or more debit and reserve operations

may be performed when the session is ongoing.

10. Session Released: Session is released.

11. Debit Units Request: CTF requests the OCF to assure the deduction of an amount

corresponding to the consumed number of units from the subscriber's account

12. Rating Control: Assisted by the rating entity the OCF calculates the number of monetary

units to deduct from the subscriber's account.

13. Account Control: OCF triggers the deduction of the calculated amount from the

subscriber's account.

14. Debit Units Response: OCF informs the CTF of the actually deducted units.

4.1.2.3.3 Decentralized Unit Determination and Decentralized Rating

In the following scenario, the CTF request the OCF to assure the reservation of an amount of

the specified number of monetary units from the subscriber's account. An account debit

operation that triggers the deduction the amount from the subscriber's account is carried out

following the conclusion of session establishment.

Page 26 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

UEa OCF CTF

1. Request for resource usage

2. Units
Determination

3. Rating Control

4. Reserve Units Request (Monetary Units)

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Monetary Units)

8. Budget
Control

9. Session ongoing

10. Session released

11. Debit Units Request (Monetary Units)

12. Account
Control
13. Debit Units Response (Monetary Units)

Figure 4.2.2.3.3: ZTE OCS Session Charging with Reservation / Decentralized Unit

Determination and Decentralized Rating

1. Request for resource usage: The UE-A requests the session establishment from the CTF.

2. Units Determination: Depending on the requested type of the session by the UE-A, the

CTF determines the number of units accordingly.

3. Rating Control: The CTF calculates the number of monetary units that represent the price

for the number of units determined in item 2.

4. Reserve Units Request: The CTF requests the OCF to assure the reservation of an

amount corresponding to the calculated number of monetary units from the subscriber's

account.

5. Account Control: The OCF checks whether the user's account balance is sufficient for the

requested reservation.

Page 27 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

6. Reservation Control: If the user's credit balance is sufficient, then the corresponding

reservation is made.

7. Reserve Units Response: The OCF informs the CTF of the reserved number of monetary

units.

8. Budget Control: Simultaneously with the ongoing session, the CTF monitors the

consumption of the granted amount.

9. Session ongoing: The CTF maintains the session. One or more debit and reserve

operations may be performed when the session is ongoing.

10. Session Released: The session is released.

11. Debit Units Request: The CTF requests the OCF to assure the deduction of an amount

corresponding to the consumed number of monetary units from the subscriber's account.

12. Account Control: The OCF triggers the deduction of the consumed amount from the

subscriber's account.

13. Debit Units Response: The OCF indicates to the CTF the number of deducted monetary

units.

Page 28 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5 ZTE Online Charging Interface Definition

5.1 Message formats for ZTE Online Charging
5.1.1 Summary of Online Charging Message Formats

5.1.1.1 General

The corresponding Diameter credit control application messages for the Debit / Reserve Unit

Request operation is Credit-Control-Request (CCR) and for the Debit / Reserve Unit

Response operation is Credit-Control-Answer (CCA) as specified in IETF RFC 4006 [402].

The Diameter Credit-Control Application (DCCA) specifies an approach based on a

series of "interrogations":

 Initial interrogation.

 Zero, one or more interim interrogations.

 Final interrogation.

In addition to a series of interrogations, also a one time event (interrogation) can be used e.g.

in the case when service execution is always successful.

All of these interrogations use Credit-Control-Request and Credit-Control-Answer messages.

The Credit-Control-Request for the "interim interrogation" and "final interrogation" reports the

actual number of "units" that were used, from what was previously reserved. This determines

the actual amount debited from the subscriber's account.

Command-Name Source Destination Abbreviation
Credit-Control-Request CTF OCS CCR
Credit-Control-Answer OCS CTF CCA
Capabilities-Exchange-Request CTF OCS CER
Capabilities Exchange Answer OCS CTF CEA
Device-Watchdog-Request CTF/OCS OCS/CTF DWR
Device-Watchdog-Answer OCS/CTF CTF/OCS DWA
Disconnect-Peer-Request OCS/CTF CTF/OCS DPR
Disconnect-Peer-Anwser CTF/OCS OCS/CTF DPA

Table 5.1.1.1: Online Charging Messages Reference Table

CER/CEA and DWR/DWA are mandatory Diameter capabilities for capabilities exchange and

transport failure detection.

Page 29 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5.1.1.2 Structure for the Credit Control Message Formats

The following is the basic structure shared by all online charging messages. This is based

directly on the format of the messages defined in IETF RFC 4006 [402].

The following symbols are used in the message format definitions:

 <AVP> indicates a mandatory AVP with a fixed position in the message.

 {AVP} indicates a mandatory AVP in the message.

 [AVP] indicates an optional AVP in the message.

 *AVP indicates that multiple occurrences of an AVP are possible.

5.1.2 Credit-Control-Request Message

The CCR messages, indicated by the Command-Code field set to 272 is sent by the CTF

to the OCF in order to request credits for the request bearer / subsystem /service.

<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}

{CC-Request-Number}

[Destination-Host]

[User-Name]

[Origin-State-Id]

[Event-Timestamp]

*[Subscription-Id]

[Termination-Cause]

*[Route-Record]

[Service-Identifier]

[Requested-Action]
Page 30 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[Requested-Service-Unit]

*[Used-Service-Unit]

[Multiple-Services-Indicator]

*[Multiple-Services-Credit-Control]

[CC-Correlation-Id]

[User-Equipment-Info]

*[Proxy-Info]

[Service-Information]

[AoC-Information]

Table 5.1.2 illustrates the basic structure of a ZTE Diameter Credit Control Credit-Control-Request

message as used for Online Charging.

Table 5.1.2: ZTE Credit-Control-Request Message Content

AVP Name AVP Code VendorID Data Type Category

<Session-Id> 263 -- UTF8String M

{Origin-Host} 264 -- Diameter Identity M

{Origin-Realm} 296 -- Diameter Identity M

{Destination-Realm} 283 -- Diameter Identity M

{Auth-Application-Id} 258 -- Unsigned32 M

{Service-Context-Id} 461 -- UTF8String M

{CC-Request-Type} 416 -- Enumerated M

{CC-Request-Number} 415 -- Unsigned32 M

[Destination-Host] 293 -- Diameter Identity Oc

[User-Name] 1 -- UTF8String OC

[Origin-State-Id] 278 -- Unsigned32 OC

[Event-Timestamp] 55 -- Time OC

*[Subscription-Id] 443 -- Grouped OC

{Subscription-Id-Type} 450 -- Enumerated OC

{Subscription-Id-Data} 444 -- UTF8String OC

Page 31 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[Release-Cause] 20315 -- Enumerated OC

[Termination-Cause] 295 -- Enumerated OC

*[Route-Record] 282 -- Diameter Identity OC

[Service-Identifier] 439 -- Unsigned32 OC

[Requested-Action] 436 -- Enumerated OC

[Requested-Service-Unit] 437 -- Grouped OC

[CC-Time] 420 -- Unsigned32 OC

[CC-Money] 413 -- Grouped OC

{Unit-Value} 445 -- Grouped OC

{Value-Digits} 447 -- Integer64 OC

[Exponent] 429 -- Integer32 OC

[Currency-Code] 425 -- Unsigned32 OC

[CC-Total-Octets] 421 -- Unsigned64 OC

[CC-Input-Octets] 412 -- Unsigned64 OC

[CC-Output-Octets] 414 -- Unsigned64 OC

[CC-Service-Specific-Units] 417 -- Unsigned64 OC

*[Used-Service-Unit] 446 -- Grouped OC

[Reporting-Reason] 872 10415 Enumerated OC

[Tariff-Change-Usage] 452 -- Enumerated OC

[CC-Time] 420 -- Unsigned32 OC

[CC-Money] 413 -- Grouped OC

{Unit-Value} 445 -- Grouped OC

{Value-Digits} 447 -- Integer64 OC

[Exponent] 429 -- Integer32 OC

[Currency-Code] 425 -- Unsigned32 OC

[CC-Total-Octets] 421 -- Unsigned64 OC

[CC-Input-Octets] 412 -- Unsigned64 OC

[CC-Output-Octets] 414 -- Unsigned64 OC

Page 32 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[CC-Service-Specific-Units] 417 -- Unsigned64 OC

[Multiple-Services-Indicator] 455 -- Enumerated OC

*[Multiple-Services-Credit-Control] 456 -- Grouped OC

[Reporting-Reason] 872 10415 Enumerated OC

*[ Trigger-Type] 870 10415 Enumerated OC

[Service-Identifier] 439 -- Unsigned32 OC

[Requested-Service-Unit] 437 -- Grouped OC

[CC-Time] 420 -- Unsigned32 OC

[CC-Money] 413 -- Grouped OC

{Unit-Value} 445 -- Grouped OC

447 -- Integer64 OC

{Value-Digits}

[Exponent] 429 -- Integer32 OC

[Currency-Code] 425 -- Unsigned32 OC

[CC-Total-Octets] 421 -- Unsigned64 OC

[CC-Input-Octets] 412 -- Unsigned64 OC

[CC-Output-Octets] 414 -- Unsigned64 OC

[CC-Service-Specific-Units] 417 -- Unsigned64 OC

446 -- Grouped OC
*[Used-Service-Unit]

[ Reporting-Reason ] 872 -- Enumerated OC

[Tariff-Change-Usage] 452 -- Enumerated OC

[CC-Time] 420 -- Unsigned32 OC

[CC-Money] 413 -- Grouped OC

{Unit-Value} 445 -- Grouped OC

447 -- Integer64 OC

{Value-Digits}

[Exponent] 429 -- Integer32 OC

[Currency-Code] 425 -- Unsigned32 OC

Page 33 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[CC-Total-Octets] 421 -- Unsigned64 OC

[CC-Input-Octets] 412 -- Unsigned64 OC

[CC-Output-Octets] 414 -- Unsigned64 OC

[CC-Service-Specific-Units] 417 -- Unsigned64 OC

[Rating-Group] 432 -- Unsigned32 OC

[CC-Correlation-Id] 411 -- Octet String OC

[User-Equipment-Info] 458 -- Grouped OC

{User-Equipment-Info-Type} 459 -- Enumerated OM

{User-Equipment-Info-Value} 460 -- Octet String OM

*[Proxy-Info] 284 -- Grouped OC

{Proxy-Host} 280 -- Diameter Identity OM

{Proxy-State} 33 -- Octet String OM

{Service-Information} 873 10415 Grouped OM

[PS-Information] 874 10415 Grouped OC

[IN-Information] 20300 81000 Grouped OC

[P2PSMS-Information] 20400 81000 Grouped OC

[ISMP-Information] 20500 81000 Grouped OC

[DSL-Information] 20600 81000 Grouped OC

[PSTN-Event-Information] 20700 81000 Grouped OC

[Recharge-information] 20800 81000 Grouped OC

[QueryBalance-Information] 20900 81000 Grouped OC

[POC-Information] 879 10415 Grouped OC

[IM-Information] 22200 81000 Grouped OC

[Broadband -Information] 30300 81000 Grouped OC

[IMS-Information] 876 10415 Grouped OC

[AoC-Information] 20329 81000 Grouped OC

[AoC-Confirmation] 20340 81000 Enumerated OC

Page 34 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5.1.2.1 Package Switched (PS)-Information Definition

AVP Name AVP Vendor Data Type Category
Code ID
[3GPP-Charging-Id] 2 10415 UTF8String OC

[3GPP-PDP-Type] 3 10415 Enumerated OC

[PDP-Address] 1227 10415 Address OC

[3GPP-GPRS-Negotiated-QoS-Profile] 5 10415 UTF8String OC

[SGSN-Address] 1228 10415 Address OC

[GGSN-Address] 847 10415 Address OC

[CG-Address] 846 10415 Address OC

[3GPP-IMSI-MCC-MNC] 8 10415 UTF8String OC

[3GPP-GGSN- MCC-MNC] 9 10415 UTF8String OC

[3GPP-NSAPI] 10 10415 UTF8String OC

[Called-Station-Id] 30 10415 UTF8String OC

[3GPP-Session-Stop-Indicator] 11 10415 Unsigned32 OC

[3GPP-Selection-Mode] 12 10415 UTF8String OC

[3GPP-Charging-Characteristics] 13 10415 Unsigned32 OC

[3GPP-SGSN-MCC-MNC] 18 10415 UTF8String OC

[3GPP-MS-TimeZone] 23 10415 UTF8String OC

[3GPP-CAMEL-Charging-Info] 24 10415 UTF8String OC

[Charging-Rule-Based-Name] 1004 10415 UTF8String OC

[3GPP-User-Location-Info] 22 10415 UTF8String OC

[3GPP-RAT-Type] 21 10415 UTF8String OC

5.1.2.2 P2PSMS-Information Definition

AVP Name AVP VendorID Data Type Category
Code
{OA-Subscription-Id} 20511 81000 Grouped OM

{Subscription-Id-Type} 450 -- Enumerated OM

{Subscription-Id-Data} 444 -- UTF8String OM

{DA-Subscription-Id} 20512 81000 Grouped OM

{Subscription-Id-Type} 450 -- Enumerated OM

{Subscription-Id-Data} 444 -- UTF8String OM

{SMSC-Address} 20401 81000 UTF8String OM

Page 35 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya
{SM-Id} 20402 81000 UTF8String OC

[SM-Length] 20403 81000 Unsigned32 OC

Calling_Vlr_Number 20302 81000 UTF8String OC

Called_Vlr_Number 20305 81000 UTF8String OC

5.1.2.3 IN-Information Definition

AVP Name AVP VendorID Data Type Category
Code
[Calling-Party-Number] 20336 81000 UTF8String OC

[Called-Party-Number] 20337 81000 UTF8String OC

[Service-Key] 20338 81000 Unsigned32 OC

[Calling-Partys-Category] 20301 81000 Unsigned32 OC

[Calling-Vlr-Number] 20302 81000 UTF8String OC

[Calling-CellID-Or-SAI] 20303 81000 UTF8String OC

[Calling-LAI] 20304 81000 UTF8String OC

[Called-Vlr-Number] 20305 81000 UTF8String OC

[Called-CellID-Or-SAI] 20306 81000 UTF8String OC

[Called-LAI] 20307 81000 UTF8String OC

[Called-IMEI] 20308 81000 UTF8String OC

[Calling-IMEI] 20309 81000 UTF8String OC

[Oiginal-Called-Party-Id] 20310 81000 UTF8String OC

[High-Layer-Compatibility] 20311 81000 UTF8String OC

[Additional-Calling-Party-Number] 20312 81000 UTF8String OC

[Bearer-Capability] 20313 81000 OctetString OC

[Bearer-Capability2] 20314 81000 OctetString OC

[EventType-BCSM] 20315 81000 Unsigned32 OC

[Redirecting-Party-Id] 20316 81000 UTF8String OC

[Redirection-Information] 20317 81000 OctetString OC

[IMSI] 20201 81000 UTF8String OC

[Tele-Service-Code] 20319 81000 OctetString OC

[Bearer-Service-Code] 20320 81000 OctetString OC

[Call-Reference-Number] 20321 81000 OctetString OC

[MSC-Address] 20322 81000 UTF8String OC

[GMSC-Address] 20323 81000 UTF8String OC

[Time-Zone] 20324 81000 Unsigned32 OC

[IN-Service-Indicator] 20325 81000 Unsigned32 OC

[Ms-Classmark2] 20326 81000 OctectString OC

[Tele-Service-Code2] 20327 81000 OctectString OC

[Bearer-Service-Code2] 20328 81000 OctectString OC

Page 36 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5.1.2.4 SP/CP-Information Definition

AVP Name AVP VendorID Data Type Category
Code
[Message-Id] 20501 81000 OctectString OC

[Charge-Party-Type] 20502 81000 Enumerated OC

[OA-Subscription-Id] 20511 81000 Grouped OC

450 -- Enumerated OC
{Subscription-Id-Type}

444 -- UTF8String OC
{Subscription-Id-Data}

[DA-Subscription-Id] 20512 81000 Grouped OC

450 -- Enumerated OC
{Subscription-Id-Type}

444 -- UTF8String OC
{Subscription-Id-Data}

[Third-Party-Subscription-Id] 20503 81000 Grouped OC

450 -- Enumerated OC
{Subscription-Id-Type}

444 -- UTF8String OC
{Subscription-Id-Data}

[SP-Id] 20504 81000 OctectString OC

[Sevice-Enabler-Type] 20505 81000 Enumerated OC

[ChargingType] 20515 81000 Unsigned32 OC

[Product-Id] 20506 81000 OctectString OC

[Product-Offer-ID] 20513 81000 OctectString OC

[Service-Type] 20507 81000 Enumerated OC

[Content-Id] 20508 81000 OctectString OC

[Media-Type] 20509 81000 OctectString OC

[Client-IP] 20510 81000 IPAddress OC

Act_Billing_Cycle_Id 38012 3902 Unsigned64 OC

Ring_Id 38013 3902 Unsigned64 OC

Page 37 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5.1.2.5 IMS-Information Definition

AVP Name AVP Code VendorID Data Type Category
Event Type 823 10415 Grouped OC

Node Functionality 862 10415 Enumerated M

Role of Node 829 10415 Enumerated OM

User Session ID 830 10415 UTF8String OM

Calling Party Address 831 10415 UTF8String OM

Called Party Address 832 10415 UTF8String OM

Page 38 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

Alternate Charged Party Address 1080 10415 UTF8String OC

Requested Party Address 1251 10415 UTF8String OC

Called Asserted Identity 1250 10415 UTF8String OC

Associated URI 856 10415 UTF8String OC

Time Stamps 833 10415 Grouped OM

Application Server Information 850 10415 Grouped OC

Inter Operator Identifier 838 10415 Grouped OC

IMS Charging Identifier 841 10415 UTF8String OM

Page 39 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya
Early Media Description 1272 10415 grouped OC

SDP Session Description 842 10415 UTF8String OC

SDP Media Component 843 10415 Grouped OC

Served Party IP Address 848 10415 Address OC

Server Capabilities 603 10415 OC

Trunk Group ID 851 10415 Grouped OC

Bearer Service 854 OctetString OC

Service Id 855 10415 UTF8String OC

Service Specific Info 1249 10415 Grouped OC

Page 40 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya
Message Bodies 889 10415 Grouped OC

Access Network Information 1263 10415 OctetString OC

Cause Code 861 10415 Integer32 OC

5.1.3 Credit-Control-Answer Message

The Credit-Control-Answer (CCA) messages, indicated by the Command-Code field set

to 272 is sent by the OCF to the CTF in order to reply to the CCR.

The CCA message format is defined according to IETF RFC 4006 [402] as follows:

<Credit-Control-Answer> ::= < Diameter Header: 272, PXY >

<Session-Id>

{Result-Code}

{Origin-Host}

{Origin-Realm}

{Auth-Application-Id}

{CC-Request-Type}

{CC-Request-Number}

[CC-Session-Failover]

[Origin-State-Id]

[Service-Identifier]

[Granted-Service-Unit]

Page 41 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[Cost-Information]

[Final-Unit-Indication]

[Credit-Control-Failure-Handling]

*[Trigger-Type]

[Direct-Debiting-Failure-Handling]

*[Proxy-Info]

*[Multiple-Services-Credit-Control]

*[Route-Record]

*[Failed-AVP]

[AoC-Information]

Table 5.1.3 illustrates the basic structure of a ZTE Diameter Credit-Control

Credit-Control-Answer message as used for online charging. This message is always used by

the OCF as specified below, independent of the receiving CTF and the CCR record type that

is being replied to.

Table 5.1.3: ZTE Credit-Control-Answer Message Content

AVP Name AVP VendorID Data Type Category
Code
<Session-Id> 263 -- UTF8String M

{Result-Code} 268 -- Unsigned32 M

{Origin-Host} 264 -- DiameterIdentity M

{Origin-Realm} 296 -- DiameterIdentity M

{Auth-Application-Id} 258 -- Unsigned32 M

{CC-Request-Type} 416 -- Enumerated M

{CC-Request-Number} 415 -- Unsigned32 M

[ CC-Session-Failover ] 418 -- Enumerated OC

[ Origin-State-Id ] 278 -- Unsigned32 OC

[Service-Identifier] 439 -- Unsigned32 OC

[ Granted-Service-Unit ] 431 -- Grouped OC

[Tariff-Time-Change] 451 -- Time OC

[CC-Time] 420 -- Unsigned32 OC

[CC-Money] 413 -- Grouped OC

{Unit-Value} 445 -- Grouped OC

{Value-Digits} 447 -- Integer64 OC

[Exponent] 429 -- Integer32 OC

Page 42 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[Currency-Code] 425 -- Unsigned32 OC

[CC-Total-Octets] 421 -- Unsigned64 OC

[CC-Input-Octets] 412 -- Unsigned64 OC

[CC-Output-Octets] 414 -- Unsigned64 OC

[CC-Service-Specific-Units] 417 -- Unsigned64 OC

[Time-Quota-Threshold ] 868 10415 Unsigned64 OC

[Volume-Quota-Threshold ] 869 10415 Unsigned64 OC

[Cost-Information] 423 -- Grouped OC

{Unit-Value} 445 -- Grouped OC

{Value-Digits} 447 -- Integer64 OC

[Exponent] 429 -- Integer32 OC

{Currency-Code} 425 -- Unsigned32 OC

[Cost-Unit] 424 -- UTF8String OC

[Final-Unit-Indication] 430 -- Grouped OC

{Final-Unit-Action} 449 -- Enumerated OC

*[Restriction-Filter-Rule] 438 -- IPFilterRule OC

*[Filter-Id] 11 -- OctectString OC

[Redirect-Server] 434 -- Grouped OC

{Redirect-Address-Type} 433 -- Emumerated OC

{Redirect-Server-Address} 435 -- UTF8String OC

[Credit-Control-Failure-Handling] 427 -- Enumerated OC

*[Trigger-Type] 870 10415 Enumerated OC

[Direct-Debiting-Failure-Handling] 428 -- Enumerated OC

*[Multiple-Services-Credit-Control] 456 -- Grouped OC

[Quota-Holding-Time] 871 10415 Unsigned32 OC

[Service-Identifier] 439 -- Unsigned32 OC

[Granted-Service-Unit] 431 -- Grouped OC

[Tariff-Time-Change] 451 -- Time OC

[CC-Time] 420 -- Unsigned32 OC

[CC-Total-Octets] 421 -- Unsigned64 OC

[CC-Input-Octets] 412 -- Unsigned64 OC

[CC-Output-Octets] 414 -- Unsigned64 OC

[CC-Service-Specific-Units] 417 -- Unsigned64 OC

[ Time-Quota-Threshold ] 868 10415 Unsigned64 OC

[ Volume-Quota-Threshold ] 869 10415 Unsigned64 OC

[ Quota-Consumption-Time ] 881 10415 Unsigned32 OC

[Rating-Group] 432 -- Unsigned32 OC

[Validity-Time] 448 -- Unsigned32 OC

[Result-Code] 268 -- Unsigned32 OC

[Final-Unit-Indication] 430 -- Grouped OC

{Final-Unit-Action} 449 -- Enumerated OC

Page 43 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

438 -- IPFilterRule OC
*[Restriction-Filter-Rule]

*[Filter-Id] 11 -- OctectString OC

[Redirect-Server] 434 -- Grouped OC

433 -- Emumerated OC
{Redirect-Address-Type}

435 -- UTF8String OC
{Redirect-Server-Address}

*[Route-Record] 282 -- DiameterIdentity OC

*[Proxy-Info] 284 -- Grouped OC

{Proxy-Host} 280 -- DiameterIdentity OM

{Proxy-State} 33 -- OctetString OM

*[Failed-AVP] 279 -- Grouped OC

[AoC-Information] 20329 81000 Grouped OC

[AoC-Balance] 20330 81000 Unsigned32 OC

[AoC-Language-ID] 20331 81000 Enumerated OC

*[AoC-Tariff] 20332 81000 Grouped OC

[AoC-Start-Time] 20333 81000 Unsigned32 OC

[AoC-Unit] 20334 81000 Unsigned32 OC

{AoC-Price} 20335 81000 Unsigned32 OC

*[Account-Information] 20356 81000 Grouped OC

[AccountId] 20357 81000 OctetString OC

[Account-Type] 20372 81000 Unsigned32 OC

[Balance_Source] 38003 3902 Unsigned32 OC

[PreBalance-CC-Money] 38002 3902 Grouped OC

{Unit-Value} 445 Grouped OC

{Value-Digits} 447 Integer64 OC

[Exponent] 429 Integer32 OC

[Currency-Code] 425 Unsigned32 OC

[CC-Money] 413 -- Grouped OC

{Unit-Value} 445 -- Grouped OC

{Value-Digits} 447 -- Integer64 OC

[Exponent] 429 -- Integer32 OC

[Currency-Code] 425 -- Unsigned32 OC

[AccountDate] 20359 81000 Time OC

[Prefered-Language] 30096 3902 Enumerated OC

Notification-Information 30090 3902 Grouped M

Page 44 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

{Notification-Type} 30091 3902 Enumerated M

[Balance-Limit] 30092 3902 Unsigned32 OC

[Monthly-Limit] 30093 3902 Unsigned32 OC

[Daily-Limit] 30094 3902 Unsigned32 OC

[Active-stop ] 30095 3902 OctetString OC

{call-Type} 30100 3902 Enumerated M

[anncode] 30102 3902 Enumerated OC

[free-time] 30103 3902 Enumerated OC

[Redirection-NO] 30104 3902 UTF8String OC

[IP-Prefix] 30105 3902 UTF8String OC

[IsCalledRoaming] 30106 3902 Enumerated OC

[Expired-Period-Notification] 30107 3902 Enumerated OC

[Last_Recharge_Amount] 30114 3902 Integer64 OC

Page 45 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[Brand-Type] 30108 3902 Enumerated M

VPN-Call-Type 30109 3902 Enumerated OC

VPN-calling-short-number 30110 3902 UTF8String OC

VPN-calling-show-mode 30111 3902 Enumerated OC

VPN-notification 30112 3902 Enumerated OC

Called-Party-Number 20337 81000 UTF8String OC

Password 30097 3902 UTF8String OC

Customer-Type 30098 3902 Enumerated OC

Prod_State 38001 3902 Enumerated OC

Home_Zone_Flag 30113 3902 Enumerated OC

Basic_Acct_Eff_Time 501 3902 Time OC

Basic_Acct_Exp_Time 502 3902 Time OC

Subs_Acct_Type 503 3902 Enumerated OC

Call_Out_Pwd 504 3902 UTF8String OC

Black_List_Level 505 3902 Enumerated OC

Block_Days 506 3902 Integer64 OC

Management_Pwd 507 3902 UTF8String OC

OPG-Information 38005 3902 Grouped OC

[Client_ID] 38006 3902 UTF8String OM

[TRAN_ID] 38007 3902 UTF8String OM

[TRAN_CODE] 38008 3902 UTF8String OC

Page 46 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[MSISDN] 38010 3902 UTF8String OC

[Message_ID] 38011 3902 UTF8String OC

Reserve-Information 38014 3902 Grouped OC

[Reserve1] 38015 3902 UTF8String OC

[Reserve2] 38016 3902 UTF8String OC

[Reserve3] 38017 3902 UTF8String OC

[Reserve4] 38018 3902 UTF8String OC

[Reserve5] 38019 3902 UTF8String OC

Internal-Return-Code 38020 3902 Unsigned32 OC

SCE_CLASS 38021 3902 Enumerated OC

5.1.4 Capabilities-Exchange-Request Message

<CER> ::= < Diameter Header: 257, REQ >

{ Origin-Host }

{ Origin-Realm }

1* { Host-IP-Address }

{ Vendor-Id }

{ Product-Name }

[ Origin-State-Id ]

* [ Supported-Vendor-Id ]

* [ Auth-Application-Id ]

* [ Inband-Security-Id ]

* [ Acct-Application-Id ]

* [ Vendor-Specific-Application-Id ]

[ Firmware-Revision ]

* [ AVP ]

5.1.5 Capabilities-Exchange-Answer Message

<CEA> ::= < Diameter Header: 257 >

{ Result-Code }

Page 47 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

{ Origin-Host }

{ Origin-Realm }

1* { Host-IP-Address }

{ Vendor-Id }

{ Product-Name }

[ Origin-State-Id ]

[ Error-Message ]

* [ Failed-AVP ]

* [ Supported-Vendor-Id ]

* [ Auth-Application-Id ]

* [ Inband-Security-Id ]

* [ Acct-Application-Id ]

* [ Vendor-Specific-Application-Id ]

[ Firmware-Revision ]

* [ AVP ]

5.1.6 Device-Watchdog-Request Message

<DWR> ::= < Diameter Header: 280, REQ >

{ Origin-Host }

{ Origin-Realm }

[ Origin-State-Id ]

5.1.7 Device-Watchdog-Answer Message

<DWA> ::= < Diameter Header: 280 >

{ Result-Code }

{ Origin-Host }

{ Origin-Realm }

[ Error-Message ]

* [ Failed-AVP ]

[ Original-State-Id ]

Page 48 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

5.1.8 Disconnect-Peer-Request Message

<DPR> ::= < Diameter Header: 282, REQ >

{ Origin-Host }

{ Origin-Realm }

{ Disconnect-Cause }

5.1.9 Disconnect-Peer-Answer Message

<DPA> ::= < Diameter Header: 282 >

{ Result-Code }

{ Origin-Host }

{ Origin-Realm }

[ Error-Message ]

* [ Failed-AVP ]

Page 49 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

6 AVP Definition
6.1 Session-Id
AVP Name Session-Id

AVP Code 263

AVP Type UTF8String

Quoted From

Directions: Session ID. It is the only identifier of a DCC session process.

The syntax is as follows:

<DiameterIdentity>;<high 32 bits>;<low 32 bits>[;<optional value>]

<DiameterIdentity> : the same with Origin-Host;

<high 32 bits>: the current time of the system, which is in accordance with the data format

defined in TIME;

<low 32 bits>: increase circularly. Its initial value is 0 and it is set to 0 when the system

restarts;

<Optional value>: reserved.

All the aforementioned fields are separated by the character ";".

For example:
SMSC001.TKL.com;8876583210;588

6.2 Origin-Host
AVP Name Origin-Host

AVP Code 264

Page 50 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

AVP Type Diameter Identity

Quoted From
Directions: the service ID of the launcher. It is distributed by the entire network in a unified
way and the uniqueness of different Diameter peers must be guaranteed.

For example: SMSC001.TKL.com

6.3 Origin-Realm
AVP Name Origin-Realm

AVP Code 296

AVP Type Diameter Identity

Quoted From 【2】6.4

Directions: the origin realm of the launcher service.

For example: TKL.com

6.4 Destination-Host
AVP Name Destination-Host

AVP Code 293

AVP Type Diameter Identity

Quoted From 【2】6.5

Directions: the service ID of the destination. It is distributed by the entire network in a
unified way and the uniqueness of different Diameter peers must be guaranteed.

It must be carried in a message that initiated by the agent; it can be carried in the request
message; and it can not be carried in a reply message.

For example: ocs001.chinatelecom.com

6.5 Destination-Realm
AVP Name Destination-Realm

Page 51 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

AVP Code 283

AVP Type Diameter Identity

Quoted From 【2】6.6

Directions: the origin realm of the destination service. This attribute can not appear in a
reply message.

For example: chinatelecom.com

6.6 Auth-Application-Id
AVP Name Auth-Application-Id

AVP Code 258

AVP Type Unsigned32

Quoted From 【2】6.8

Directions: the unique identifier for re-authentication and re-authorization.
Diameter Common Messages 0
NASREQ 1 [NASREQ]
Mobile-IP 2 [DIAMMIP]
Diameter Base Accounting 3
Relay 0xffffffff
DCCA 4

6.7 Service-Context-Id
AVP Name Service-Context-Id

AVP Code 461

AVP Type UTF8String

Quoted From 【1】8.42

Page 52 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

Directions: the unique identifier of a DCC service.

The format is:
"service-context" "@" "domain"
The definition of service-context is: ”version””[X]””.””[Y]””.””[Z]”
[X] is the version number of the protocol composed of integers. Its initial
value is 1;
[Y] is the service type composed of characters.
Its value can be: in/ismp/ccg/ p2psms/wlan/DSL, etc.
[Z] is the terminal type composed of characters. If [Z] does not exist, the
default terminal type is gsm.
Its value can be: pstn/ phs/ gsm/cdma, etc.
The value of the domain: TKL.com
For example:

version3.P2PSMS.gsm@TKL.com

6.8 CCR-Type
AVP Name CC-Request-Type

AVP Code 416

AVP Type Enumerated

Quoted From 【1】8.3

Directions: the reason for sending a CCR message. It is a enumeration type and must be

shown in a CCR message

The following parameters are defined in the CC-Request AVP:

INITIAL_REQUEST 1

The initial credit-control request. It is used to initiate a credit control session, which

involves the corresponding credit control information.

UPDATE_REQUEST 2

The -credit-control-update request. It involves the credit control information of the

established credit control session. The credit-control request can be used to initiate a

re-authorization.

Page 53 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

TERMINATION_REQUEST 3

The termination request. It can be used to terminate a session.

EVENT_REQUEST 4

EVENT_REQUEST can be used when there is no need for the DDC server to maintain

the session state, which involves all of the information of the corresponding service.

And it is the unique request of this service. When CC-Request-Type in the CCR request

message is set to EVENT_REQUEST, Requested-Action must be involved in the CCR

message.

The deduction request in the TKL short message center is an event deduction request, 4

should be filled in.

6.9 CCR-Request-Number
AVP Name CC-Request-Number

AVP Code 415

AVP Type Unsigned32

Quoted From

Directions: the identifier of different requests in one session. Because of the global

uniqueness of the Session-Id, different requests and replies can be matched through the

Session-Id and the CC-Request-Number.

In every INITIAL_REQUESTand EVENT_REQUEST, CC-Request-Number, the first

UPDATE REQUEST and the second UPDATE REQUEST can be set to 0,1 and 2,

respectively. And all the rest can be set in the same way until the

TERMINATION_REQUEST is sent.

Page 54 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

6.10 Event-Timestamp
AVP Name Event-Timestamp

AVP Code 55

AVP Type Time

Quoted From
Directions: timestamp; It is counted by seconds from 1900 00:00 UTC January the first.

6.11 Subscription-Id
AVP Name Subscription-ID

AVP Code 443

AVP Type Grouped

Quoted From

Directions: it is used to identify the information of the terminal user in the service

subscription side.

Subscription-ID is an AVP group. The concrete ABNF syntax is as follows:

*Subscription-Id ::= < AVP Header: 443 >

{ Subscription-Id-Type }

{ Subscription-Id-Data }

Diameter Proxy or Agent should route according to this field.

If more than one Subscription-Id exists, the first Subscription-Id is prevailing.

6.12 Subscription-Id-Type
AVP Name Subscription-Id-Type

AVP Code 450

AVP Type Enumerated

Quoted From

Directions: it is used to determine the terminal identifier type of the subscriber

Page 55 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

Define the following parameters:

END_USER_E164 0

The format of the terminal identifier is the international E.164 format defined in

accordance with the ITU-T E.164 number plan.

END_USER_IMSI 1

The format of the terminal identifier is the international IMSI format defined in

accordance with the ITU-T E.212 number plan.

END_USER_SIP_URI 2

The terminal identifier is a SIP URI.

END_USER_NAI 3

The terminal identifier is a network access identifier.

END_USER_PRIVATE 4

The terminal identifier is the private identifier of a DCC server.

For the SMSC of TKL, the END_USER_E164 should be used to send the subscriber

MSISDN.

6.13 Subscription-Id-Data
AVP Name Subscription-Id-Data

AVP Code 444

AVP Type UTF8String

Quoted From 【1】8.48

Directions: the terminal user ID

6.14 Call-Type
AVP Name Call-Type

AVP Code 38022

Page 56 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

AVP Type Enumerated

Quoted From

Directions: 1-MO

2-MT

6.15 Requested-Action
AVP Name Requested-Action

AVP Code 436

AVP Type Enumerated

Quoted From

Directions: if the value of CC-Request-Type in the CCR command is set to

EVENT_REQUEST, the Requested_Action AVP involves the requested actions.

The following parameters are defined in the Requested-Action AVP:

DIRECT_DEBITING 0

Direct deduction. It represents that the corresponding amount of the user’

s account is

deducted according to the information in the Requested-Service-Unit AVP. The amount to

be deducted is involved In the Granted-Service-Unit AVP of CCA.

Additional charging information can be involved in the corresponding AVP of the

service.

REFUND_ACCOUNT 1

Refund. It represents that the corresponding amount of the user’

s account is refunded

according to the information in the Requested-Service-Unit AVP. The amount to be

refunded is involved in the Granted-Server-Unit AVP of CCA.

Additional charging information can be involved in the corresponding AVP of the

service.

CHECK_BALANCE 2

Balance check. The request that this command initiates is to check the balance. In this

Page 57 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

situation, only the balance of the user’

s account is checked, but the account credit is not

reserved. The result of the balance check is returned through the Balance-Result AVP in

the CCA command.

PRICE_ENQUIRY 3

Price enquiry. The request that this command initiates is to query the price. In this

situation, the balance of the user’

s account is not checked and the account credit is not

reserved, too. Only the requested service price is returned through the Cost-Information in

the CCA.

For the TKL, if it is successful, the DIRECT_DEBITING should be filled in; if it is failing,

the REFUND_ACCOUNT should be filled in when returning the result notification.

6.16 Service-Identifier
AVP Name Service-Identifier

AVP Code 439

AVP Type Unsigned32

Quoted From Serve ID

Directions: service ID, which determines a service uniquely along with the

Service-Context-Id.

For the TKL projects, it is reserved temporarily. The sub –service in the P2PSMS can be

discriminated by this attribute.

6.17 OA-Subscription-Id
AVP Name OA-Subscription-Id

AVP Code 20511

AVPType Grouped

Page 58 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

Quoted From

Directions: it is used to identify the information of terminal user in the initiative side

OA-Subscription-Id is an AVP group. The concrete ABNF syntax is as follows:

OA-Subscription-Id ::= < AVP Header: 20511>

{ Subscription-Id-Type }

{ Subscription-Id-Data }

Domestic fixed-line, PHS: district number＋phone number;

Domestic mobile phone: 86＋phone number;

International number: country code＋phone number；

The special numbers can transform directly.

For example: fixed-line, PHS: 01058751234; mobile phone: 8613912345678; international

number: 0085212345678

6.18 DA-Subscription-Id
AVP Name DA-Subscription-Id

AVP Code 20512

AVP Type Grouped

Quoted From

Directions: it is used to identify the information of the terminal user in the destination

side.

DA-Subscription-Id is an AVP group. The concrete ABNF syntax is as follows:

DA-Subscription-Id ::= < AVP Header: 20512>

{ Subscription-Id-Type }

Page 59 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

{ Subscription-Id-Data }

Domestic fixed-line, PHS: district number＋phone number;

Domestic mobile phone: 86＋phone number;

International number: country code＋phone number；

The special numbers can transform directly.

For example: fixed-line, PHS: 01058751234; mobile phone: 8613912345678; international

number: 0085212345678

6.19 SMSC-Address
AVP Name SMSC-Address

AVP Code 20401

AVP Type UTF8String

Quoted From
Directions: the address of the short message center

6.20 SM-Id
AVP Name SM-Id

AVP Code 20402

AVP Type UTF8String

Quoted From
Directions: the short message identifier. It is used to relate the deduction request of the
IEC and the refund request of the Result Notification Request.

Page 60 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

6.21 SM-Length
AVP Name SM-Length

AVP Code 20403

AVP Type Unsigned32

Quoted From
Directions: the short message length

6.22 Result-Notification-Type
AVP Name Result-Notification-Type

AVP Code 38023

AVP Type Enumerated

Quoted From
Directions:

0x00 – the billing notification will be sent whether the short message is sent successfully
or not.

0x01 – the billing notification will be sent only when the short message is not sent
successfully.

0x02 –the billing notification will be sent only when the short message is sent successfully.

0x03 –he billing notification will not be sent whether the short message is sent
successfully or not.

Page 61 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

7 Definitions, Symbols and Abbreviations

7.1 Definitions
For the purposes of the present document, the following terms and definitions apply:

Offline Charging: charging mechanism where charging information does not affect, in

real-time, the service rendered

Online Charging: charging mechanism where charging information can affect, in real-time, the

service rendered and therefore a direct interaction of the charging mechanism with

session/service control is required

7.2 Symbols
For the purposes of the present document, the following symbols apply:

Rf Offline Charging Reference Point between a 3G network element and the CDF.

Ro Online Charging Reference Point between a 3G network element and the OCS.

7.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:

ACA ACcounting Answer

ACR ACcounting Request

AS Application Server

ASA Abort Session Answer

ASR Abort Session Request

AVP Attribute Value Pair

CCA Credit Control Answer

CCR Credit Control Request

CDF Charging Data Function

CDR Charging Data Record

CI Cost-Information

DBPA Diameter Base Protocol Accounting

Page 62 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

DPA Disconnect Peer Answer

DPR Disconnect Peer Request

ECUR Event Charging with Unit Reservation

FUI Final-Unit-Indication

GSU Granted-Service-Unit

IEC Immediate Event Charging

IMS IP Multimedia Subsystem

MSCC Multiple Services Credit Control

OCS Online Charging System

OAM&P Operation, Administration, Maintenance and Provisioning

Page 63 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

8 References
[001] 3GPP TS 32.240: "Telecommunication management; Charging management;

Charging Architecture and Principles".

[002] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"

[003] 3GPP TS 23.207: "End to end quality of service concept and architecture".

[004] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".

[005] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage

3."

[006] 3GPP TS 29.207: "Policy control over Go interface".

[007] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; Protocol

Details".

[008] 3GPP TS 29.230: "3GPP specific codes and identifiers".

[009] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN)

supporting packet based services and Packet Data Networks (PDN)".

[010] 3GPP TS 23.140: " Multimedia Messaging Service (MMS); Functional description;

Stage 2".

[011] OMA "Multimedia Messaging Service; Encapsulation Protocol".

[012] OMNA WSP Content Type Codes database.

http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.htm

[013] OMA-CP-POC: "OMA PoC Control Plane"

[014] 3GPP 29.234: "3GPP system to Wireless Local Area Network (WLAN) interworking;

Stage 3".

[015] 3GPP TS 29.140: "MM10 interface based on Diameter protocol; Stage 3".

[016] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point; Stage 3".

[017] 3GPP TS 29.212: "Policy and Charging Control over Gx reference point".

[018] 3GPP TS 23.040: "Technical realization of Short Message Service (SMS)".

[019] IETF RFC 3588: "Diameter Base Protocol".

[020] IETF RFC 4006: "Diameter Credit Control Application"

Page 64 of 65
 ZTE Online Charging Interface-Diameter v1.0_Kenya

[021] IETF Draft, "Carrying Location Objects in RADIUS", draft-ietf-geopriv-radius-lo-04.txt,

work in progress

[022] IETF RFC 3455 , "Private Extensions to the Session Initiation Protocol (SIP) for the

3rd Generation Partnership Projects (3GPP)".

[023] IETF RFC 3261: "SIP: Session Initiation Protocol".

[024] IETF Internet-Draft, "SDP: Session Description

Protocol".http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-new-24.txt

[025] IETF RFC 4005: "Diameter Network Access Server Application".

[026] IETF RFC 3264: An Offer/Answer Model with the Session Description Protocol

(SDP).

[027] 3GPP TS 32.299: The use of the Attribute Value Pairs (AVPs) that are defined in the

ZTE Online Charging Interface- Diameter document. Detailed specification of these AVPs can

be found from Diameter charging Application document

Page 65 of 65