1 Compliance Statement

Overview

Introduction

This chapter introduces the Diameter Control Driver (DCD) compliance limitations.

DCD Overview

Introduction

The Diameter Charging Driver (DCD) is an interface used by CCS to allow communication of billing requests from an SLC to a billing platform using the DIAMETER protocol. The DIAMETER base protocol is defined by RFC 6733, and extended to include real-time credit-control messages by RFC 4006.

The DCD (and thus this document) only covers the use of CCS as a DIAMETER client. For information about CCS acting as a DIAMETER server, see the Diameter Control Agent (DCA) documentation.

The DCD client runs on the SLC SLEE, taking requests from the billing actions of slee_acs and forwards them to the billing engine. It maintains the connections to the billing engines (or, if configured, DIAMETER proxies).

General restrictions

Specific adherence to the RFCs is described in a later section, but there are some general properties of DIAMETER that are not handled by the DCD.

They are:

  • TLS (RFC 2246) is not supported.
  • Authentication and Authorization messages are not supported
  • Tariff Time Change is not supported
  • Dynamic peer discovery is not performed.
  • Sub-sessions are not supported.