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.
|Published (Last):||21 March 2008|
|PDF File Size:||19.44 Mb|
|ePub File Size:||4.25 Mb|
|Price:||Free* [*Free Regsitration Required]|
Event-based charging is typically used when units are not continuously consumed, e. If cleared, the message MUST be locally processed. In the latter case, the interface between the Service Element and the Diameter credit- control client is outside the scope of this specification.
Diameter Credit-Control Application
Service specific authorization and authentication is out of the scope. Hakala Request for Comments: The credit- control protocol is the Diameter base protocol with the Diameter credit-control application. Service-Specific Rating Input and Interoperability The Diameter rfd server is the entity responsible for credit authorization for prepaid subscribers. The client is allowed to request units before the previous grant is completely used, in order to avoid suspending the subscriber session while talking to the server.
Rating Rrfc act of determining the cost of the service event.
When an account is exhausted diametre expired, the user must be denied the ability to compile additional chargeable events. Pages using RFC magic links.
Diameter Credit-Control Application Protocol
The RFC defines a core state machine for maintaining connections between peers and processing messages. This page was last edited on 19 Octoberat For price inquiries the client ask the server what the price for a unit is, and the server responds with the price.
Transaction state implies that upon forwarding a request, its Hop-by-Hop Identifier is saved; the field is replaced with a locally unique identifier, which is restored to its original value when the corresponding answer is received. Adding a new optional AVP does not require diameetr new application.
It is reasonable to expect that a service level agreement will exist between providers of the credit-control client and the credit-control server covering the charging, services offered, roaming agreements, agreed rating input i. Rtc 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.
It monitors the usage of the granted quota according to instructions returned by credit-control server. These agents transparently support the Diameter credit-control application.
A Command Code is used to determine the action that is to be taken for a particular message. This is left to the service context that has to be specified separately, as is some of the semantics. The real configuration can combine them into a single host.
Credit-Control Application State Machine The other Diameter applications provide service specific authorization, and they do not provide credit authorization for prepaid users. From Wikipedia, the free encyclopedia. It is used between the credit-control server and the Diameter credit-control client to acknowledge a Credit- Control-Request command. As ofthe only value supported is 1. Application-ID is used to identify for which Diameter application the message is applicable.
Therefore, it is assumed that a Diameter credit-control server 406 provide service only for Diameter credit-control clients that have agreed beforehand as to the content of credit-control messages. 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.
The credit-control server and AAA server in this architecture model are logical entities. In case of redirecting agents, the Hop-by-Hop Identifier is maintained in the diametet as the Diameter agent responds with an answer message.