CCN Programmer's Guide - DAAC/SCAPv2

Version 1.0
CCN 5

CUSTOMER PRODUCT INFORMATION

1/1553-FAY 302 099/1 Uen B

Copyright

© Ericsson AB 2012. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Contents

Contents

1 Introduction 1
1.1 Service Definition / Purpose 1
1.2 Notation 1

2 Service Contract 3
2.1 Overview 3
2.2 Supported Service Operations 6

3 Service and Protocol Usage 7

3.1 Application Specific Parameters 7
3.2 Service-Parameter-Info AVP 10
3.3 Credit Control Session, Initial 11
3.4 Credit Control Session, Update 16
3.5 Credit Control Session, Terminate 21
3.6 Direct Debit 24
3.7 Refund 27

4 Backward Compatibility Notice 31

4.1 Dedicated Accounts 31
4.2 Result Codes 31
4.3 Service-Parameter-Info 31

5 Limitations 33
5.1 Range Limitations 33

6 Apendix A – Parameter Configurations 35

6.1 Definitions 35
6.2 DAAC/SCAPv2 AVP Configurations 36

7 Appendix B – AVP Flag Rules 41

Glossary 45

Reference List 47

1/1553-FAY 302 099/1 Uen B | 2012-06-28

CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Introduction

1 Introduction

1.1 Service Definition / Purpose

Diameter Credit Control (DCC) is an external protocol that is used by the
DAAC/SCAPv2 Service.

The DAAC Service specifies a framework to be used when defining a charging

interface for an application. This charging interface is in DCC called a service
context.

The service context defines how the DAAC Service is used for a specific
application, including exact usage of interface parameters, charging models
and configuration of the DAAC Service.

The SCAP service context provides online charging support based on Diameter
Credit Control. The service context is used for real-time cost and credit control
of content and service charging between the Charging System and application
servers.

1.2 Notation
Table 1 Notation
Icon Description
Operation() Message Operation
{Parameter} Mandatory parameter
[Parameter] Optional parameter
<Parameter> Mandatory fixed parameter (defines the fixed
position of a parameter in a message)
*Parameter Multiple instances of the parameter is possible
{[Parameter]} Optional parameter on the protocol but mandatory
for the specific scenario
= ‘data’ Data for a parameter, for example constants used
to distinguish different processing requested using
the same message

1/1553-FAY 302 099/1 Uen B | 2012-06-28 1

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

2 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service Contract

2 Service Contract

2.1 Overview

2.1.1 Service Context Identification

The SCAP service context is identified by the serving element setting the value
[email protected] in the Service-Context-Id AVP.

2.1.2 Service Identification

The Service can be used to charge for several services where each
unique service is identified by the serving element setting a value in the
Service-Identifier AVP.

The actual value used to identify a charged service has to be configured both in
the serving element and the Service.

The Service-Identifier is only limited in range by the constraints of the defined

AVP, that is, Unsigned32.

The Diameter Credit Control specification, Reference [3], allows a DCC client
to omit the Service-Identifier AVP for a service context with only one defined
service. This is not allowed for the SCAP service context – even if only one
service is to be charged for. That is, the Service-Identifier is mandatory in the
SCAP service context.

2.1.3 Over Usage

The serving element should not report more used units than have been granted
in order to not risk that there is not enough credit on the account. If this
occurs, the Service will deduct the account with the cost of the reported usage,
including the over usage.

2.1.4 Final Unit Indication

Final-Unit-Indication will be set to TERMINATE in case the Service has judged
that no more units will be granted in the next request, for a service. The only
allowed interrogation type after this is a service termination, that is, omitting the
RSU in the next request, even if the provided Validity-Time expires before the
credits are used up or if external rating parameters have changed.

1/1553-FAY 302 099/1 Uen B | 2012-06-28 3

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

2.1.5 Multi Unit Support

The Service can request, report and be granted the following unit types:

• CC-Time

• CC-Money

• CC-Service-Specific-Units

• CC-Total-Octets

• CC-Uplink-Octets

• CC-Downlink-Octets

It is not allowed to request, report and get multiple unit types for a service in
a request. Only the unit type that has been granted is allowed to be reported
as used.

2.1.6 Tariff Change

The SCAP service context will use a tariff-change mechanism and the serving
element must be prepared to handle distributed tariff handling. The serving
element must support reception of the Tariff-Time-Change AVP and when this
AVP has been received, it must report usage before and after the defined time.
If the serving element cannot determine if the consumption of credits was done
before or after the tariff switch, it is allowed to report the usage as indeterminate.

The SCAP service context will not make use of Continuous Time tariff
handling. That is, the serving element must always be prepared to handle
the Tariff-Time-Change AVP.

2.1.7 Toll-free
It is possible to configure the Service so that a particular service is defined to
be toll-free. A toll-free service is also Out-of-credit-control, meaning that when
credits for the service are sought, the response from the Service will be 4011 -
DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE.

When the Service has responded with 4011 it necessarily does not mean that
the rendered service will be toll-free. The serving element is still expected to
produce CDR’s in order to be able to perform off-line charging.

The exact behavior of the serving element and how to handle toll-free and
off-line charging is out-of-scope of this service contract.

4 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service Contract

2.1.8 Free-of-charge
It is possible to configure the Service so that a particular service is
free-of-charge. A free-of-charge service is no different than any other service,
from the serving element point of view, except that Cost-Information indicates
no cost. The units sought will be granted and the client is expected to report
usage as normal.

2.1.9 Request Number

The value of the request number in EVENT and INITIAL requests must
be zero. The value of the request number in UPDATE and FINAL
requests must be received consecutively. The result code 5004 -
DIAMETER_INVALID_AVP_VALUE will be returned to the serving element if
an incorrect value of the request number is received.

This response will be accompanied by a Result-Code-Extension AVP.

2.1.10 Multiple Services

The service supports Multiple Service Credit Control, MSCC and it is thus
possible to charge for multiple parallel services in a charging session. Each
service must be identified with a unique value set to the Service-Identifier AVP.

The serving element is not allowed to use asynchronous signaling towards the
service, even when using MSCC. That is, the serving element must wait for and
answer to a CCR before issuing a new.

2.1.11 Active Services

It is not allowed to have an active charging session without any active
services. The effect of this rule is that the serving element must issue a CCR
(FINAL_INTERROGATION) when reporting usage, without requesting for more
units for the last service.

If the service detects a violation to this rule, the result code 5012 -
DIAMETER_UNABLE_TO_COMPLY is returned to the serving element.

This response will be accompanied by a Result-Code-Extension AVP.

If the service has decided that the serving element has reached the allowed
credit limit for the last service, the service will send Result-Code 4012
(DIAMETER_CREDIT_LIMIT_REACHED) on the command line to the serving
element and will not expect a CCR (FINAL_INTERROGATION) from the
serving element.

This response will be accompanied by a Result-Code-Extension AVP.

1/1553-FAY 302 099/1 Uen B | 2012-06-28 5

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

2.2 Supported Service Operations

• Credit Control Session

• Direct Debit

• Refund

Note: Service Operations Balance Check and Price Enquiry are not
supported by this service context. The result code 5003 -
DIAMETER_AUTHORIZATION_REJECTED will be returned to the
serving element if a not supported operation is received.

The Service Operation Refund is only possible with the unit type is CC-Money.
The result code 5012 - DIAMETER_UNABLE_TO_COMPLY will be returned to
the serving element if any other unit type is used for Refund.

This response will be accompanied by a Result-Code-Extension AVP.

6 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

3 Service and Protocol Usage

3.1 Application Specific Parameters

The SCAP service context defines a number of service context specific
parameters.

3.1.1 Account-Location AVP

The Account-Location AVP (AVP code 1073) is of type Unsigned32 and holds
the logical identity of the account location. If the location is not known to the
serving element the AVP must be excluded from the request.

The AVP is in this service context defined as ‘static’ and ‘cached’.

3.1.2 Subscription-Id-Location AVP

The Subscription-Id-Location AVP (AVP Code 1074), of type UTF8String, is
used to define the location of a user, identified by the Subscription-Id AVP. The
format of the UTF8String is in international E.164 format according to the ITU-T
E.164 numbering plan defined in Reference [4].

The Subscription-Id-Location AVP in DAAC/SCAPv2 is an optional parameter,

but must be provided when MNP functions of the Service are to be used for
terminating traffic cases.

When sending the Location data it is mandatory to provide the CC and

recommended to send NDC. LSP is considered optional.

The AVP is in this service context defined as ‘static’ and ‘cached’.

3.1.3 Other-Party-Id AVP

The Other-Party-Id AVP (AVP code 1075) holds an identifier of the other party
involved in a session in addition to the Subscription-Id. The other party is
related to the session but not charged for the session. The other party could
be for example a calling party, a called party, a redirecting party, a sender or a
receiver; depending on service. The Other-Party-Id AVP is a grouped AVP as
specified below.
Other-Party-Id ::= < AVP Header: 1075, Vendor Id: 193 >
{ Other-Party-Id-Type }
{ Other-Party-Id-Data }
[ Other-Party-Id-Nature ]
*[ AVP ]

1/1553-FAY 302 099/1 Uen B | 2012-06-28 7

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

The Other-Party-Id AVP is in this service context defined as ‘static’ and ‘cached’.

The serving element is not allowed to use the *[AVP] part of the Other-Party-Id
since it’s reserved for internal use within the Service.

3.1.4 Other-Party-Id-Nature AVP

The Other-Party-Id-Nature AVP (AVP code 1076) is of type Enumerated

and holds the nature of address indicator for the number carried by the
Other-Party-Id-Data AVP.

This specification defines the following nature of address indicators.

• UNKNOWN 0

• INTERNATIONAL 1 (default)

• NATIONAL (SIGNIFICANT) 2

As the Other-Party-Id-Nature address is an optional AVP, the default value

used by the SCAPv2 service context shall be 1 (INTERNATIONAL) when the
AVP is omitted and the Other-Party-Id-Type AVP is 0 (END_USER_E164).

3.1.5 Other-Party-Id-Data AVP

The Other-Party-Id-Data AVP (AVP code 1077) is of type UTF8String and holds
the E.164 number of the other party involved in a session. Other-Party-Id-Type
AVP and Other-Party-Id-Nature AVP define the type and nature of address
that is used.

The following characters can be used for E.164 number: 0123456789*#ABCD

Eabcde

3.1.6 Other-Party-Id-Type AVP

The Other-Party-Id-Type AVP (AVP code 1078) is of type Enumerated and it is
used to determine which type of identifier is carried by the Other-Party-Id AVP.

END_USER_E164 0

The identifier is in E.164 format. Other-Party-Id-Nature

AVP defines the nature of address that is used.

END_USER_IMSI 1

The identifier is in international IMSI format.

8 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

END_USER_SIP_URI
2

The identifier is in the form of a SIP URI.

END_USER_NAI 3

The identifier is in the form of a Network Access

Identifier.

The only supported value is END_USER_E164 in the SCAPv2 service context.

3.1.7 Service-Provider-Id AVP

The Service-Provider-Id AVP (AVP code 1081) is of type UTF8String and
holds an identifier of the service provider. The use of the service provider is
operator specific.

The AVP is in this service context defined as ‘static’ and ‘cached’.

3.1.8 3GPP-MS-TimeZone AVP

The 3GPP-MS-TimeZone AVP (AVP code 23) is of type OctetString and holds
the time zone for the time reported in the Event-Time AVP. It is only applicable
together with an Event-Timestamp in the same request.

The definition of 3GPP-MS-TimeZone can be found in Reference [2].

3.1.9 Traffic-Case AVP

The Traffic-Case AVP (AVP code 1082) is of type Unsigned32 and holds the
traffic case for the charged event.

Table 2 Traffic-Case AVP

Traffic Case ACP
Value Traffic Case
0–19 Reserved for future use.
20 Originating Service Charging
21 Terminating Service Charging
22 – MAXRANGE Reserved for future use. MAXRANGE
is defined as the maximum range of
the unit type.

The AVP is in this service context defined as ‘static’ and ‘cached’.

1/1553-FAY 302 099/1 Uen B | 2012-06-28 9

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

3.1.10 Time-Quota-Threshold AVP

The Time-Quota-Threshold AVP is specified in Reference [2]. If received, the

serving element seeks re-authorization from the server for the quota when the
quota contents fall below the supplied threshold. The serving element allows
service to continue while the re-authorization is in progress, until the time at
which the original quota would have been consumed.

The use of the AVP is operator specific, and configured in the Service. The
Service will not relate the value of the AVP to the time given in Validity-Time
or vice versa.

If the Service has been incorrectly configured, there is a risk that the serving
element receives a value in the AVP larger than provided Validity-Time.

3.1.11 Volume-Quota-Threshold AVP

The Volume-Quota-Threshold AVP is specified in Reference [2]. If received, the
serving element seeks re-authorization from the server for the quota when the
quota contents fall below the supplied threshold. The serving element allows
service to continue while the re-authorization is in progress, until the time at
which the original quota would have been consumed.

The use of the AVP is operator specific, and configured in the Service.

3.1.12 Unit-Quota-Threshold AVP

The Unit -Quota-Threshold AVP is specified in Reference [2]. If received, the
serving element seeks re-authorization from the server for the quota when the
quota contents fall below the supplied threshold. The serving element allows
service to continue while the re-authorization is inprogress, until the time at
which the original quota would have been consumed.

The use of the AVP is operator specific, and configured in the Service.

3.2 Service-Parameter-Info AVP

Three types of service parameters are included in the Service-Parameter-Info
AVP. The use of the different types in rating is operator specific.

Table 3 Service-Parameter-Info AVP

Service-Parameter-Info AVP
Service-Parameter-Type Parameter Type
0–199 Integer32
200–399 UTF8String

10 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

400–599 OctetString
600–MAXRANGE Reserved for future use. MAXRANGE
is defined as the maximum range of
the unit type.

The AVP is in this service context defined as ‘non-static’ and ‘cached’.

3.3 Credit Control Session, Initial

3.3.1 Description
The serving element contacts the Service in order to verify that the requested
service/services are allowed. The possible results of the session establishment
are:

• Allowed, the session will continue (for multiple services, at least one service
is allowed).

• Not allowed, the session will be rejected.

The Service reports the result of the establishment request back to the serving
element.

3.3.2 Protocol Binding

Table 4 Protocol Bindings for Credit Control Session, Initial Request
Credit Control Session, Initial Request
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Origin-Host} DAAC-Client-Host
{Origin-Realm} DAAC-Client-Realm
{Destination-Realm}
{Auth-Application-Id} DAAC-Application-Id
{Service-Context-Id} Service-Context-Id Value is ‘SCAP_V.2.0
@ericsson.com’
{CC-Request-Type} DAAC-Request-Type Value is INITIAL_REQ
UEST
{CC-Request-Number} DAAC-Request-Number Value is 0
[Origin-State-Id]
{[Event-Timestamp]} DAAC-Event-Timestamp

1/1553-FAY 302 099/1 Uen B | 2012-06-28 11

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

{[Subscription-Id]} Subscription-Id
[Service-Identifier] Service-Identifier Mandatory when
MSCC is not used.
[Requested-Service-Unit] Requested-Service-Unit Mandatory when
MSCC is not used.
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
[Multiple-Services-Indicator] Multiple-Services-Indicator
*[Multiple-Services-Credit-C Multiple-Services-Credit-C See Table 5.
ontrol] ontrol
*[Service-Parameter-Info] Service-Parameter-Info Cached parameters
A value of the Servic
e-Parameter-Type is
only allowed once in a
request per service.
[Proxy-Info]
[Route-Record]
[Account-Location] Application-Specific-Inform The value of the
ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.
[Subscription-Id-Location] Application-Specific-Inform The value of the
ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.
[Other-Party-Id] Application-Specific-Inform The value of the
ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.

12 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

[Service-Provider-Id] Application-Specific-Inform The value of the

ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.
{[3GPP-MS-TimeZone]} Application-Specific-Inform The value of the
ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.
[Traffic-Case] Application-Specific-Inform The value of the
ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.

Table 5 Protocol Bindings for Credit Control Session, Initial Request, MSCC
Credit Control Session, Initial Request, MSCC Group Parameter
DCC AVP Semantic Parameter Service Operation
Specific Handling
{[Requested-Service-Unit]}
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
{[Service-Identifier]} Service-Identifier
[Other-Party-Id] Application-Specific-Inform The value of the
ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.
[Service-Provider-Id] Application-Specific-Inform The value of the
ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.

1/1553-FAY 302 099/1 Uen B | 2012-06-28 13

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

[Traffic-Case] Application-Specific-Inform The value of the

ation parameter will be used
in the authorization and
accounting analysis in
this and all following
requests in the session.
*[Service-Parameter-Info] Application-Specific-Inform Cached parameters
ation
A value of the Servic
e-Parameter-Type is
only allowed once in a
request per service.

Table 6 Protocol Bindings for Credit Control Session, Initial Answer

Credit Control Session, Initial Answer
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Result-Code} Result-Code
{Origin-Host}
{Origin-Realm}
{Auth-Application-Id} DAAC-Application-Id Value is INITIAL_REQ
UEST
{CC-Request-Number} DAAC-Request-Number
[Origin-State-Id]
[Granted-Service-Unit] Granted-Service-Unit
[Tariff-Time-Change ]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
*[Multiple-Services-Credit-C Multiple-Services-Credit-C See Table 7
ontrol] ontrol
[Final-Unit-Indication] Final-Unit-Indication
[Credit-Control-Failure-Hand DAAC-Session-Failure-Ha
ling] ndling
[Validity-Time] Validity-Time
[Proxy-Info]
[Route-Record]

14 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

*[Failed-AVP] Failed-AVP
[Result-Code-Extension] Application-Specific-Inform
ation
[Time-Quota-Threshold] Application-Specific-Inform
ation
[Volume-Quota-Threshold] Application-Specific-Inform
ation
[Unit-Quota-Threshold] Application-Specific-Inform
ation

Table 7 Protocol Bindings for Credit Control Session, Initial Answer, MSCC
Credit Control Session, Initial Answer, MSCC Group Parameter
DCC AVP Semantic Parameter Service Operation
Specific Handling
[Granted-Service-Unit] Granted-Service-Unit
[Tariff-Time-Change ]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
{[Service-Identifier]} Service-Identifier
[Validity-Time] Validity-Time
{[Result-Code]} Result-Code
[Final-Unit-Indication] Final-Unit-Indication
[Result-Code-Extension] Application-Specific-Inform
ation
*[Failed-AVP] Application-Specific-Inform
ation
[Time-Quota-Threshold] Application-Specific-Inform
ation
[Volume-Quota-Threshold] Application-Specific-Inform
ation
[Unit-Quota-Threshold] Application-Specific-Inform
ation

1/1553-FAY 302 099/1 Uen B | 2012-06-28 15

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

3.4 Credit Control Session, Update

3.4.1 Description
An Update will prolong an ongoing charging session in-between the serving
element and the Service. The serving element contacts the Service, in order to
verify that the requested Service Operation is allowed.

3.4.2 Protocol Binding

Table 8 Protocol Bindings for Credit Control Session, Update Request

Credit Control Session, Update Request
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Origin-Host } DAAC-Client-Host
{Origin-Realm} DAAC-Client-Realm
{Destination-Realm}
{Auth-Application-Id} DAAC-Application-Id
{Service-Context-Id} Service-Context-Id Value is ‘SCAP_V.2.0
@ericsson.com’
{CC-Request-Type} DAAC-Request-Type Value is UPDATE_RE
QUEST
{CC-Request-Number} DAAC-Request-Number The value will
be incremented
sequentially
[Destination-Host] Value as received
in previous CCA,
Origin-Host
[Origin-State-Id]
{[Event-Timestamp]} DAAC-Event-Timestamp
[Subscription-Id] Subscription-Id Parameter defined as
‘static’ and ‘cached’
and may be omitted
by the client, must not
change.
[Service-Identifier] Service-Identifier Mandatory when
MSCC is not used.

16 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

[Requested-Service-Unit] Requested-Service-Unit Mandatory when

MSCC is not used.
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
*[Used-Service-Unit] Used-Service-Unit Mandatory when
MSCC is not used.
[Tariff-Change-Usage]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
*[Service-Parameter-Info] Service-Parameter-Info Cached parameters
A value of the Servic
e-Parameter-Type is
only allowed once in a
request per service.
*[Multiple-Services-Credit-C Multiple-Services-Credit-C See Table 9.
ontrol] ontrol
[Proxy-Info]
[Route-Record]
[Account-Location] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Subscription-Id-Location] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Other-Party-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Service-Provider-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.

1/1553-FAY 302 099/1 Uen B | 2012-06-28 17

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

{[3GPP-MS-TimeZone]} Application-Specific-Inform The parameter must,

ation if sent, have the same
value as in the initial
request.
[Traffic-Case] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.

Table 9 Protocol Bindings for Credit Control Session, Update Request, MSCC
Credit Control Session, Update Request, MSCC Group Parameter
DCC AVP Semantic Parameter Service Operation
Specific Handling
[Requested-Service-Unit] Requested-Service-Unit
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
*[Used-Service-Unit] Used-Service-Unit
[Tariff-Change-Usage]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
{[Service-Identifier]} Service-Identifier
[Other-Party-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Service-Provider-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.

18 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

[Traffic-Case] Application-Specific-Inform The parameter must,

ation if sent, have the same
value as in the initial
request.
*[Service-Parameter-Info] Application-Specific-Inform Cached parameters
ation
A value of the Servic
e-Parameter-Type is
only allowed once in a
request per service.

Table 10 Protocol Bindings for Credit Control Session, Update Answer

Credit Control Session, Update Answer
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Result-Code} Result-Code
{Origin-Host}
{Origin-Realm}
{Auth-Application-Id} DAAC-Application-Id
{CC-Request-Type} DAAC-Request-Type Value is UPDATE_RE
QUEST
{CC-Request-Number} DAAC-Request-Number
[Origin-State-Id]
[Granted-Service-Unit] Granted-Service-Unit
[Tariff-Time-Change ]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
*[Multiple-Services-Credit-C Multiple-Services-Credit-C See Table 11.
ontrol] ontrol
[Cost-Information] Cost-Information
[Final-Unit-Indication] Final-Unit-Indication
[Credit-Control-Failure-Hand DAAC-Session-Failure-Ha
ling] ndling
[Validity-Time] Validity-Time
[Proxy-Info]

1/1553-FAY 302 099/1 Uen B | 2012-06-28 19

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

[Route-Record]
*[Failed-AVP] Failed-AVP
[Result-Code-Extension] Application-Specific-Inform
ation
[Time-Quota-Threshold] Application-Specific-Inform
ation
[Volume-Quota-Threshold] Application-Specific-Inform
ation
[Unit-Quota-Threshold] Application-Specific-Inform
ation

Table 11 Protocol Bindings for Credit Control Session, Update Answer,

MSCC
Credit Control Session, Update Answer, MSCC Group Parameter
DCC AVP Semantic Parameter Service Operation
Specific Handling
[Granted-Service-Unit] Granted-Service-Unit
[Tariff-Time-Change ]
[CC-Time] [CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
{[Service-Identifier]} Service-Identifier
[Validity-Time] Validity-Time
{Result-Code} Result-Code
[Final-Unit-Indication] Final-Unit-Indication
[Cost-Information] Application-Specific-Inform
ation
[Result-Code-Extension] Application-Specific-Inform
ation
*[Failed-AVP] Application-Specific-Inform
ation
[Time-Quota-Threshold] Application-Specific-Inform
ation
[Volume-Quota-Threshold] Application-Specific-Inform
ation
[Unit-Quota-Threshold] Application-Specific-Inform
ation

20 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

3.5 Credit Control Session, Terminate

3.5.1 Description
A Terminate related to a charging session will end the session. The serving
element contacts the Service in order to adjust the account’s balance with the
used value.

3.5.2 Protocol Binding

Table 12 Protocol Bindings for Credit Control Session, Terminate Request

Credit Control Session, Terminate Request
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Origin-Host } DAAC-Client-Host
{Origin-Realm} DAAC-Client-Realm
{Destination-Realm}
{Auth-Application-Id} DAAC-Application-Id
{Service-Context-Id} Service-Context-Id Value is ‘SCAP_V.2.0
@ericsson.com’
{CC-Request-Type} DAAC-Request-Type Value is TERMINATE_
REQUEST
{CC-Request-Number} DAAC-Request-Number The value will
be incremented
sequentially
[Destination-Host] Value as received
in previous CCA,
Origin-Host
[Origin-State-Id]
{[Event-Timestamp]} DAAC-Event-Timestamp
[Subscription-Id] Subscription-Id Parameter defined as
‘static’ and ‘cached’
and may be omitted by
the client.
[Service-Identifier] Service-Identifier Mandatory when
MSCC is not used.
[Termination-Cause] Termination-Cause

1/1553-FAY 302 099/1 Uen B | 2012-06-28 21

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

*[Used-Service-Unit] Used-Service-Unit Mandatory when

MSCC is not used.
[Tariff-Change-Usage]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
*[Multiple-Services-Credit-C Multiple-Services-Credit-C See Table 13.
ontrol] ontrol
*[Service-Parameter-Info] Service-Parameter-Info A value of the Servic
e-Parameter-Type is
only allowed once in a
request per service.
[Proxy-Info]
[Route-Record]
[Account-Location] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Subscription-Id-Location] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Other-Party-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Service-Provider-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
{[3GPP-MS-TimeZone]} Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Traffic-Case] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.

22 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

Table 13 Protocol Bindings for Credit Control Session, Terminate Request,

MSCC
Credit Control Session, Terminate Request, MSCC Group Parameter
DCC AVP Semantic Parameter Service Operation
Specific Handling
*[Used-Service-Unit] Used-Service-Unit
[Tariff-Change-Usage]
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
{[Service-Identifier]} Service-Identifier
[Other-Party-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Service-Provider-Id] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
[Traffic-Case] Application-Specific-Inform The parameter must,
ation if sent, have the same
value as in the initial
request.
*[Service-Parameter-Info] Application-Specific-Inform A value of the Servic
ation e-Parameter-Type is
only allowed once in a
request per service.

Table 14 Protocol Bindings for Credit Control Session, Terminate Answer

Credit Control Session, Terminate Answer
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Result-Code} Result-Code
{Origin-Host}
{Origin-Realm}
{Auth-Application-Id} DAAC-Application-Id

1/1553-FAY 302 099/1 Uen B | 2012-06-28 23

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

{CC-Request-Type} DAAC-Request-Type Value is UPDATE_RE

QUEST
{CC-Request-Number} DAAC-Request-Number
[Origin-State-Id]
*[Multiple-Services-Credit-C Multiple-Services-Credit-C See Table 15.
ontrol] ontrol
[Credit-Control-Failure-Hand DAAC-Session-Failure-Ha
ling] ndling
[Cost-Information] Cost-Information
[Proxy-Info]
[Route-Record]
*[Failed-AVP] Failed-AVP
[Result-Code-Extension] Application-Specific-Inform
ation

Table 15 Protocol Bindings for Credit Control Session, Terminate Answer,

MSCC
Credit Control Session, Terminate Answer, MSCC Group Parameter
DCC AVP Semantic Parameter Service Operation
Specific Handling
{[Service-Identifier]} Service-Identifier
{Result-Code} Result-Code
[Cost-Information] Application-Specific-Inform
ation
[Result-Code-Extension] Application-Specific-Inform
ation
*[Failed-AVP] Application-Specific-Inform
ation

3.6 Direct Debit

3.6.1 Description
A Direct Debit request for a service will be initiated. The Service will calculate
the cost based on the received charging input and adjust the account. The

24 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

response will include the granted units and as an option cost information, that
is, the total cost for the service.

3.6.2 Protocol Binding

Table 16 Protocol Bindings for Charging Event, Direct Debit Request

Charging Event, Direct Debit, Request
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Origin-Host} DAAC-Client-Host
{Origin-Realm} DAAC-Client-Realm
{Destination-Realm}
{Auth-Application-Id} DAAC-Application-Id
{Service-Context-Id} Service-Context-Id Value is ‘SCAP_V.2.0
@ericsson.com’
{CC-Request-Type} DAAC-Request-Type Value is ‘EVENT_REQ
UEST’
{CC-Request-Number} DAAC-Request-Number Value is 0
[Origin-State-Id]
{[Event-Timestamp]} DAAC-Event-Timestamp
{[Subscription-Id]} Subscription-Id
{[Service-Identifier]} Service-Identifier
{[Requested-Service-Unit]} Requested-Service-Unit
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
{[Requested-Action]} DAAC-Requested-Action Value is ‘DIRECT_DE
BITING’
*[Service-Parameter-Info] Service-Parameter-Info A value of the Servic
e-Parameter-Type is
only allowed once in a
request per service.
[Proxy-Info]
[Route-Record]

1/1553-FAY 302 099/1 Uen B | 2012-06-28 25

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

[Account-Location] Application-Specific-Inform
ation
[Subscription-Id-Location] Application-Specific-Inform
ation
[Other-Party-Id] Application-Specific-Inform
ation
[Service-Provider-Id] Application-Specific-Inform
ation
{[3GPP-MS-TimeZone]} Application-Specific-Inform
ation
[Traffic-Case] Application-Specific-Inform
ation

Table 17 Protocol Bindings for Charging Event, Direct Debit Answer

Charging Event, Direct Debit, Answer
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Result-Code} Result-Code
{Origin-Host}
{Origin-Realm}
{Auth-Application-Id} DAAC-Application-Id
{CC-Request-Type} DAAC-Request-Type Value is ‘EVENT_REQ
UEST’
{CC-Request-Number} DAAC-Request-Number
[Origin-State-Id]
[Granted-Service-Units] Granted-Service-Units
[CC-Time]
[CC-Money]
[CC-Total-Octets]
[CC-Input- Octets]
[CC-Output- Octets]
[CC-Service-Specific-Units]
[Cost-Information] Cost-Information
[Proxy-Info]
[Route-Record]

26 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

*[Failed-AVP] Failed-AVP
[Result-Code-Extension] Application-Specific-Inform
ation

3.7 Refund

3.7.1 Description
A Refund request related to a service with unit type set to money will be
initiated. The Service executes a cost calculation based on the received
charging input for the service and makes a Refund to the account.

3.7.2 Protocol Binding

Table 18 Protocol Bindings for Charging Event, Refund Request

Charging Event, Refund, Request
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Origin-Host} DAAC-Client-Host
{Origin-Realm} DAAC-Client-Realm
{Destination-Realm}
{Auth-Application-Id} DAAC-Application-Id
{Service-Context-Id} Service-Context-Id Value is ‘SCAP_V.2.0
@ericsson.com’
{CC-Request-Type} DAAC-Request-Type Value is ‘EVENT_REQ
UEST’
{CC-Request-Number} DAAC-Request-Number Value is 0
[Origin-State-Id]
{[Event-Timestamp]} DAAC-Event-Timestamp
{[Subscription-Id]} Subscription-Id
{[Service-Identifier]} Service-Identifier
{Requested-Service-Unit} Requested-Service-Unit Only money is
supported for Refund
[CC-Money]

1/1553-FAY 302 099/1 Uen B | 2012-06-28 27

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

{Requested-Action} DAAC-Requested-Action Value is ‘REFUND’

*[Service-Parameter-Info] Service-Parameter-Info A value of the Servic
e-Parameter-Type is
only allowed once in a
request per service.
[Proxy-Info]
[Route-Record]
[Account-Location] Application-Specific-Inform
ation
[Subscription-Id-Location] Application-Specific-Inform
ation
[Other-Party-Id] Application-Specific-Inform
ation
[Service-Provider-Id] Application-Specific-Inform
ation
{[3GPP-MS-TimeZone]} Application-Specific-Inform
ation
[Traffic-Case] Application-Specific-Inform
ation

Table 19 Protocol Bindings for Charging Event, Refund Answer

Charging Event, Refund, Answer
DCC AVP Semantic Parameter Service Operation
Specific Handling
<Session-Id> Session-Id
{Result-Code} Result-Code
{Origin-Host}
{Origin-Realm}
{Auth-Application-Id} DAAC-Application-Id
{CC-Request-Type} DAAC-Request-Type Value is ‘EVENT_REQ
UEST’
{CC-Request-Number} DAAC-Request-Number
[Origin-State-Id]
[Cost-Information] Cost-Information
[Proxy-Info]
[Route-Record]

28 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Service and Protocol Usage

*[Failed-AVP] Failed-AVP
[Result-Code-Extension] Application-Specific-Inform
ation

1/1553-FAY 302 099/1 Uen B | 2012-06-28 29

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

30 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Backward Compatibility Notice

4 Backward Compatibility Notice

The SCAP service context is functionally backward compatible with the Service
Charging Application Protocol as described in Programmer's Guide - Service
Charging Based on Diameter, Reference [1].

This means that the charging functionality that was possible to build using
Reference [1] shall also be possible with this service context.

Some limitations/changes have been notices and are explained in the following
sub-chapters.

4.1 Dedicated Accounts

It is not possible to explicitly identify a dedicated account from the serving
element as it was possible in Reference [1]. It is however possible to
implicitly identify a dedicated account using request parameters together with
configuration in the Service.

4.2 Result Codes

Some result codes used in the Draft-8 version of SCAP, Reference
[1], have changed. The result code 4241 is replaced by 4010 -
DIAMETER_END_USER_SERVICE_DENIED and result code 5241 is replaced
by 5030 - DIAMETER_USER_UNKNOWN.

4.3 Service-Parameter-Info
The use of the Service-Parameter-Info has changed a lot between SCAP
and the SCAPv2 service context. Table 20 defines the differences between
the two protocols.

Table 20 Service-Parameter-Info mapping between SCAP and

DAAC/SCAPv2
Service- SCAP Semantics DAAC/SCAPv2 Parameter
Parameter-
Type
0 ServiceProviderID Service-Provider-Id AVP
*1–4 ExtensionNumber1–4 Service-Parameter-Info AVP
(0..199)
*5 ExtensionText Service-Parameter-Info AVP
(200..399)

1/1553-FAY 302 099/1 Uen B | 2012-06-28 31

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

*6 GPRSQualityOf-Service Service-Parameter-Info AVP

(0..199)
*7 RedirectingParty-Number Other-Party-Id AVP or
Service-Parameter-Info AVP
*8 OriginatingLocation-Informat Subscription-Id-Location AVP
ion or Service-Parameter-Info
AVP
*9 TerminatingLocationInformat Subscription-Id-Location AVP
ion or Service-Parameter-Info
AVP
*10 Network Id Service-Parameter-Info AVP
(0..199)
*11 SubscriptionType Service-Parameter-Info AVP
(0..199)
*12 SmsDeliveryStatus Service-Parameter-Info AVP
(0..199)
*13 Trigger-Time Service-Parameter-Info AVP
(200..399)
14 Traffic Case Traffic-Case AVP
*15 Dedicated account ID N/A
*16 NumberList/CallingPartyNum Service-Parameter-Info AVP
ber (200..399)
*17 NumberList/CalledPartyNum Service-Parameter-Info AVP
ber (200..399)
*18 Tele-service Code N/A
*19 Service Key Account-Location AVP

32 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Limitations

5 Limitations

5.1 Range Limitations

Some of the AVPs used to signal units between the serving element and the
Service are in DCC,Reference [3], defined to be of type unsigned 64 bit, that is,
Unsigned64 (0 – 264-1).

The serving element cannot handle the full range of this parameter and will treat
these parameters as signed 64 bit instead, that is, Integer64 (-263 – 263-1).

The affected parameters are listed in Table 21.

Table 21 Unit parameters limited in range

AVP Code AVP Name Allowed Range
417 CC-Service-Specific-Un 0–263-1
its
412 CC-Input-Octets
414 CC-Output-Octets
421 CC-Total-Octets

1/1553-FAY 302 099/1 Uen B | 2012-06-28 33

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

34 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Apendix A – Parameter Configurations

6 Apendix A – Parameter Configurations

This appendix is created to show, for a Credit Control Session, parameter

configuration of SCAPv2 service context.

6.1 Definitions

6.1.1 Static [AVP]

The value of the parameter may not change during the session. If omitted in
first interrogation, providing it in upcoming interrogations are considered to
be violations to the static rule.

A static parameter is always cached.

6.1.2 Cached [AVP]

If the parameter has been submitted in an interrogation, the value is cached in
the case it is omitted in upcoming interrogations.

6.1.3 Static/Cached *[AVP], Single AVP, Multiple Occurrences

A single AVP, that is, non-grouped, of multiple occurrences cannot be static or
cached.

6.1.4 Static Grouped [AVP]

A Grouped [AVP] that is defined to be static must provide the same information
in all upcoming request, but the order of the included parameters may change.

6.1.5 Cached Grouped [AVP]

See Section 6.1.2 on page 35

6.1.6 Static or Cached Grouped *[AVP], Multiple Occurances

An unordered grouped [AVP] with multiple occurances cannot be defined either
as static or non-static, see A.1.3.

1/1553-FAY 302 099/1 Uen B | 2012-06-28 35

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

However, by defining one of the AVP’s in a grouped AVP to be the key, an

ordered grouped AVP is defined.

The Service-Parameter-Info AVP can be used as en example on how to create

an ordered grouped AVP where the Service-Parameter-Info-Type defines the
order in the list. This AVP shall be treated as a key to the list-order in a more
general approach.

Service-Parameter-Info ::= < AVP Header: 440 >

{ Service-Parameter-Type } // KEY
{ Service-Parameter-Value }

Example 1 Service-Parameter-Info AVP

Another example is the Subcription-Id AVP where the key to the data is
Subcription-Id-Data AVP.

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

{ Subscription-Id-Type }
{ Subscription-Id-Data } // KEY

Example 2 Subscription-Id AVP

6.2 DAAC/SCAPv2 AVP Configurations

6.2.1 Credit-Control Request Configuration

Table 22 Credit-Control Request Configuration

Credit-Control Request Configuration
AVP Name Groupe Key Stati Cache Note
d c d
<Session-Id> No N/A Yes N/A
{Origin-Host} No N/A Yes N/A
{Origin-Realm} No N/A Yes N/A
{Destination-Realm} No N/A Yes N/A
{Auth-Application-Id} No N/A Yes N/A
{Service-Context-Id} No N/A Yes N/A
{CC-Request-Type} No N/A No No
{CC-Request-Numbe No N/A No No
r}

36 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Apendix A – Parameter Configurations

[Destination-Host] No N/A No No
[User-Name] No N/A Yes N/A
[Acct-Multi-Session- No N/A Yes N/A
Id]
[Origin-State-Id] No N/A No No
[Event-Timestamp] No N/A No No
*[Subscription-Id] Yes Subscription Yes N/A Static group
-Id-Data ed *AVP; All
‘sub-AVP’ are
static.
[Service-Identifier] No N/A No N/A
[Termination-Cause] No N/A No N/A
[Requested-Service- Yes Table 24 N/A N/A
Unit]
[Requested-Action] No N/A No No
*[Used-Service-Unit] Yes Table 25 No No
[Multiple-Services-In No N/A Yes N/A
dicator]
[Multiple-Services-In No N/A Yes N/A
dicator]
*[Multiple-Services-C Yes Table 23 N/A N/A
redit-Control]
*[Service-Parameter- Yes Service-Para No Yes Cached
Info] meter-Info-T grouped
ype *AVP; Each
instance,
identified
by Key,
is cached
individually
[CC-Correlation-Id] No N/A No No Not used
in SCAPv2
service
context
[User-Equipment-Inf Yes N/A Yes N/A Static group
o] ed AVP; All
‘sub-AVP’ are
static
*[Proxy-Info] Yes Proxy-Host No No Grouped
*AVP
*[Route-Record] Yes None No No *AVP

1/1553-FAY 302 099/1 Uen B | 2012-06-28 37

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

[Account-Location] No N/A Yes N/A Only used by

CCN
[Subscription-Id-Loc No N/A Yes N/A
ation]
[Other-Party-Id] Yes N/A Yes N/A Static group
ed AVP; All
‘sub-AVP’ are
static.
[Service-Provider-Id] No N/A Yes N/A
{[3GPP-MS-TimeZon No N/A Yes N/A
e]}
[Traffic-Case] No N/A Yes N/A

6.2.2 Multiple-Services Credit-Control Configuration

Table 23 Multiple-Services Credit-Control Configuration

Multiple-Services Credit-Control Configuration
AVP Name Groupe Key Stati Cache Note
d c d
[Requested-Service- Yes Table 24 N/A N/A
Unit]
[Used-Service-Unit] Yes Table 25 N/A N/A
[Tariff-Change-Usag No N/A No No
e]
[Service-Identifier] No N/A No N/A
[Other-Party-Id] Yes N/A Yes N/A Static group
ed AVP; All
‘sub-AVP’ are
static.
[Service-Provider-Id No N/A Yes N/A
[Traffic-Case] No N/A Yes N/A
*[Service-Parameter- Yes Service-Para No Yes Cached
Info] meter-Info-T grouped
ype *AVP; Each
instance,
identified
by Key,
is cached
individually

38 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Apendix A – Parameter Configurations

6.2.3 Requested-Service-Unit Configuration

Table 24 Requested-Service-Unit Configuration

Requested-Service-Unit Configuration
AVP Name Groupe Key Stati Cache Note
d c d
[CC-Time] No N/A No No
[CC-Money] Yes Table 26 No No
[CC-Total-Octets] No N/A No No
[CC-Input-Octets] No N/A No No
[CC-Output-Octets] No N/A No No
[CC-Service-Specific No N/A No No
-Units]

6.2.4 Used-Service-Unit Configuration

Table 25 Used-Service-Unit Configuration

Used-Service-Unit Configuration
AVP Name Groupe Key Stati Cache Note
d c d
[Tariff-Change-Usag No N/A No No
e]
[CC-Time] No N/A No No
[CC-Money] Yes Table 26 No No
[CC-Total-Octets] No N/A No No
[CC-Input-Octets] No N/A No No
[CC-Output-Octets] No N/A No No
[CC-Service-Specific No N/A No No
-Units]

6.2.5 CC-Money Configuration

1/1553-FAY 302 099/1 Uen B | 2012-06-28 39

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

Table 26 CC-Money Configuration

CC-Money Configuration
AVP Name Groupe Key Stati Cache Note
d c d
{Unit-Value} No N/A No No
{[Currency-Code]} No N/A No No Static and
cached
between RSU
and USU*

40 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Appendix B – AVP Flag Rules

7 Appendix B – AVP Flag Rules

Table 27 defines the AVP Flag Rules for the SCAPv2 service context as well
as the Vendor-Id used for Vendor Specific AVPs. Vendor Specific AVPs from
Ericsson (193) and 3GPP (10415) are used.

Table 27 AVP Flag Rules

Attribute AVP Data Type Vendo AVP Flag Rules May
Name Code r Id Encr
Shoul Must
Must May
d Not Not
Account-Locat 1073 Unsigned32 193 V,M P N
ion
CC-Correlation 411 OctetString N/A P,M V N
-Id
CC-Input-Octe 412 Unsigned64 N/A M P V N
ts
CC-Money 413 Grouped N/A M P V N
CC-Output-Oct 414 Unsigned64 N/A M P V N
ets
CC-Request-N 415 Unsigned32 N/A M P V N
umber
CC-Request-T 416 Enumerate N/A M P V N
ype d
CC-Service-Sp 417 Unsigned64 N/A M P V N
ecific-Units
CC-Session-F 418 Enumerate N/A M P V N
ailover d
CC-Sub-Sessi 419 Unsigned64 N/A M P V N
on-Id
CC-Time 420 Unsigned32 N/A M P V N
CC-Total-Octe 421 Unsigned64 N/A M P V N
ts
CC-Unit-Type 454 Enumerate N/A M P V N
d
Check-Balanc 422 Enumerate N/A M P V N
e-Result d
Cost-Informati 423 Grouped N/A M P V N
on

1/1553-FAY 302 099/1 Uen B | 2012-06-28 41

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

Cost-Unit 424 UTF8String N/A M P V N

Credit-Control 426 Enumerate N/A M P V N
d
Credit-Control 427 Enumerate N/A M P V N
-Failure-Handl d
ing
Currency-Cod 425 Unsigned32 N/A M P V N
e
Direct-Debiting 428 Enumerate N/A M P V N
-Failure-Handl d
ing
Exponent 429 Integer32 N/A M P V N
Final-Unit-Acti 449 Enumerate N/A M P V N
on d
Final-Unit-Indic 430 Grouped N/A M P V N
ation
Granted-Servic 431 Grouped N/A M P V N
e-Unit
G-S-U-Pool-Id 453 Unsigned32 N/A M P V N
entifier
G-S-U-Pool-R 457 Grouped N/A M P V N
eference
Multiple-Servic 456 Grouped N/A M P V N
es-Credit-Cont
rol
Multiple-Servic 455 Enumerate N/A M P V N
es-Indicator d
Rating-Group 432 Unsigned32 N/A M P V N
Other-Party-Id 1075 Grouped 193 V,M P N
Other-Party-Id- 1076 Enumerate 193 V,M P N
Nature d
Other-Party-Id 1077 UTF8String 193 V,M P N
-Data
Other-Party-Id 1078 Enumerate 193 V,M P N
-Type d
Redirect-Addre 433 Enumerate N/A M P V N
ss-Type d
Redirect-Serve 434 Grouped N/A M P V N
r

42 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Appendix B – AVP Flag Rules

Redirect-Serve 435 UTF8String N/A M P V N

r-Address
Requested-Act 436 Enumerate N/A M P V N
ion d
Requested-Ser 437 Grouped N/A M P V N
vice-Unit
Restriction-Filt 438 IPFiltrRule N/A M P V N
er-Rule
Service-Conte 461 UTF8String N/A M P V N
xt-Id
Service-Identif 439 Unsigned32 N/A M P V N
er
Service-Param 440 Grouped N/A M, V N
eter-Info P
Service-Param 441 Unsigned32 N/A M, V N
eter-Type P
Service-Param 442 OctetString N/A M, V N
eter-Value P
Service-Provid 1081 UTF8String 193 V,M P N
er-Id
Subscription-Id 443 Grouped N/A M P V N
Subscription-Id 444 UTF8String N/A M P V N
-Data
Subscription-Id 450 Enumerate N/A M P V N
-Type d
Subscription-Id 1074 UTF8String 193 V,M P N
-Location
Tariff-Change- 452 Enumerate N/A M P V N
Usage d
Tariff-Time-Ch 451 Time N/A M P V N
ange
3GPP-MS-Tim 23 OctetString N/A V,M P N
eZone
Time-Quota-T 868 Unsigned32 10415 V,M P N
hreshold
Traffic-Case 1082 UTF8String 193 V,M P N
Unit-Value 445 Grouped N/A M P V N
Unit-Quota-Th 1226 Unsigned32 10415 V,M P N
reshold

1/1553-FAY 302 099/1 Uen B | 2012-06-28 43

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

Used-Service- 446 Grouped N/A M P V N

Unit
User-Equipme 458 Grouped N/A P,M V N
nt-Info
User-Equipme 459 Enumerate N/A P,M V N
nt-Type d
User-Equipme 460 OctetString N/A P,M V N
nt-Value
Value-Digits 447 Integer64 N/A M P V N
Validity-Time 448 Unsigned32 N/A M P V N
Volume-Quota 869 Unsigned32 10415 V,M P N
-Threshold

44 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Glossary

Glossary

AVP
Attribute Value Pair

CC
Country Code

CCN
Charging Control Node

CDR
Charging Data Record

DAAC
Diameter Accounting and Authorization
Control

DCC
Diameter Credit Control

LSP
Locally Significant Part

MNP
Mobile Number Portability

NDC
National Destination Code

RSU
Requested Service Unit

SCAP
Service Charging Application Protocol

1/1553-FAY 302 099/1 Uen B | 2012-06-28 45

 CCN Programmer's Guide - DAAC/SCAPv2 Version 1.0

46 1/1553-FAY 302 099/1 Uen B | 2012-06-28

 Reference List

Reference List

[1] Programmer's Guide - Service Charging Based on Diameter, 7/1553-FAM

901 098/5 Uen

[2] 3GPP TS 32.299 V.6.a.0, Diameter Charging Applications

[3] Diameter Credit Control, RFC 4006

[4] Recommendation E.164/I.331 (05/97), The International Public

Telecommunication Numbering Plan

1/1553-FAY 302 099/1 Uen B | 2012-06-28 47