Diameter is an authentication, authorization, and accounting protocol for computer networks. The Diameter base protocol is defined by RFC ( Obsoletes: RFC ) and CCR, , Diameter Credit-Control Application – RFC Diameter Credit-Control Application, is a networking protocol for Diameter application used to implement real-time credit-control for a variety of end user services. It is an IETF standard defined in RFC RFC (part 1 of 5): Diameter Credit-Control Application. Network Working Group H. Hakala Request for Comments: L. Mattila Category: Standards.

Author: Yozuru Nalabar
Country: Angola
Language: English (Spanish)
Genre: Education
Published (Last): 5 May 2008
Pages: 426
PDF File Size: 19.51 Mb
ePub File Size: 11.53 Mb
ISBN: 419-4-47456-458-3
Downloads: 97151
Price: Free* [*Free Regsitration Required]
Uploader: Samuzilkree

RFC – Diameter Credit-Control Application

Service-Specific Rating Input and Interoperability The Diameter credit-control application defines the framework for credit-control; it provides generic credit-control mechanisms supporting multiple service applications. The credit-control process is performed to determine potential charges and to verify whether the end user’s account balance is sufficient to cover the cost of the service being rendered.

Service specific authorization and authentication is out of the scope. Introduction This document specifies a Diameter application that can be used to implement real-time credit-control for a variety of end user services such as network access, Session Initiation Protocol SIP services, messaging services, and download services.

Session based credit-control A credit-control process that makes use of several interrogations: A session-based credit control process uses several interrogations which may include first, intermediate and last interrogation. When an account is exhausted or expired, the user must be denied the ability to compile additional chargeable events.

When real-time credit-control is required, the credit-control client contacts the credit-control server with information about a possible service event. Diameter is an authentication, authorization, and accounting protocol for computer networks.

In addition, diaketer is necessary to check that the end user’s account provides coverage for the requested service prior to initiation of that service. The RFC defines an authorization and an accounting state machine. Credit-Control Application Related Parameters In a multi-service environment, an end user can issue an additional service dfc e.


To ensure that the end user’s account is not debited or credited multiple times for the same service event, only one place in the credit-control system should perform duplicate detection. In this example the client sends the request when 7 units of the 10 previously granted rf have been used; and ask for 10 more units, which the server grants.

In case of redirecting agents, the Hop-by-Hop Identifier is maintained in the header as the Diameter agent responds with an answer message. The Command Codes are as follows: It is used between the Diameter credit-control client and the credit-control server to request credit authorization for a given service. Note that credit resources may not imply actual monetary credit; credit resources may be granted to the credit control client in the form of units e. During interrogation money is reserved from the user account.

In the latter case, the interface between the Service Element and the Diameter credit- control client diametet outside the scope of this specification.

The credit-control application also supports operations such as service price enquiry, user’s balance check, and refund of credit on the user’s account.

Diameter Credit-Control Applicationis a networking protocol for Diameter application diamefer to implement real-time credit-control for a variety of end user services. Retrieved 12 October The ” R ” Request bit — If set, the message is a request.

By using this site, you agree to the Terms of Use and Privacy Policy. Distribution of this memo is unlimited. When set the AVP Code belongs to the specific vendor code address space. Diameter credit- control server. The credit-control server deducts the used amount from the end user’s account; it may perform rating and make a new credit reservation if the service delivery is continuing.

The prepaid model has been shown to be ciameter successful, for instance, in GSM networks, where network operators offering prepaid services have experienced a substantial growth of their customer base and revenues. Diameter Applications can extend the base protocol by adding new commands, attributes, or both.


Upon receipt of a successful credit authorization answer, the credit-control client allows service delivery to the end user. The Diameter protocol requires that relaying and proxying agents maintain transaction state, which is used for failover purposes. AA request AA request generically refers to a service specific authorization and authentication request.

Credit-Control Application State Machine The Service Element may include the Diameter credit-control client, or another entity e. A flexible credit-control application specific failure handling is defined in which the home service provider can model the credit- control client behavior according to its own credit risk management policy. Retrieved from ” https: From Wikipedia, the free encyclopedia.

Diameter (protocol)

During the credit-control process, it is used to report the used quota and request a new one. Typical credit-control architecture There can be multiple credit-control servers in the system for redundancy and load balancing. The server grants units and charges the user.

Rating The act of determining the cost of the service event. Diameter Credit-control Server A Diameter credit-control server acts as a prepaid server, performing real-time rating and credit-control. If cleared, the message is an answer. When creating a request, the End-to-End Identifier is set to a locally unique value.

The RFC defines a core state machine for maintaining connections between peers and processing messages. The specific service or rating group the request relates to is uniquely identified by the combination of Service-Context-Id and Service-Identifier or Rating-Group.