The Charging Software Development Kit (SDK) makes it easy for operators and developers to develop applications and serv­ices with charging capabilities. This SDK provides ’know how’ about imple­mentation of applications that use charging and about how charging will be implemented towards the charging system via the Diameter interface.

The Charging SDK includes the Diameter Credit Control (DCC), for example, Multiple Service and Multiple Unit Environments, where the DCC Charging SDK will allow additional service request during an ongoing service (such as PTT session) towards the same account. This can be achieved by either individual or independent Credit Control Request (CCRs) for each service or by one CCR with individual Multiple Service Credit Control (MSCC) for each service.

The APIs in Charging SDK 2.0 provide full support for the SCAPv2 Service Context on the Diameter Credit Control Application.

The Charging SDK provides a model on how to implement an application with charging capabilities. By using this model, developers are less likely to make errors and mistakes.

Charging SDK 2.0 is directly connected to Ericsson Charging System 4 and onwards. A test client is included in Charging SDK 2.0.


Differences between Charging SDK 2.0 and 1.0
Charging SDK 2.0 is an entirely new product. It supports the RFC 3588 version of the Diameter base protocol, whereas Charging SDK 1.0 supports the draft 8 version.

Charging SDK 2.0 is functionally backward compatible towards Charging SDK 1.0, that is, the same operations in SDK 1.0, such as Credit Control Session, Direct Debit and Refund (Credit), are also supported in SDK 2.0. It is not possible to deploy Charging SDK 2.0 in a solution using Charging SDK 1.0. If this is needed, parts of the software using the Charging SDK need to be rewritten.