RFC (part 1 of 5): Diameter Credit-Control Application. Network Working Group H. Hakala Request for Comments: L. Mattila Category: Standards. RFC (part 2 of 5): Diameter Credit-Control Application. 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
|Published (Last):||1 March 2017|
|PDF File Size:||6.39 Mb|
|ePub File Size:||7.30 Mb|
|Price:||Free* [*Free Regsitration Required]|
Credit-control Credit-control is a mechanism that directly interacts in real-time with an account and controls or monitors the charges related to the service usage.
Whether the credit-control message diameter rfc 4006 is moved to diameter rfc 4006 backup credit-control server during an ongoing credit-control session depends on the value of the CC-Session-Failover AVP.
For instance, if an implementation of the credit-control client can determine primary credit-control server unavailability, it can establish the new credit-control sessions with a possibly available secondary credit- control server. Retrieved 12 October Online charging, also known as credit-based charging, is used to charge prepaid dia,eter.
It will then forward the packet to the diameter rfc 4006 client. Interrogation The Diameter credit-control client uses interrogation to initiate a session based credit-control process. Alternatively, during an active multimedia session, an additional media type is added to the session, causing a new simultaneous request toward same account.
RFC – Diameter Credit-Control Application
This is typically the diameter rfc 4006 when a tariff time change is expected and the credit-control server wants to make a distinction between the granted quota before and after tariff change. Note that the RoSession class automatically handles creating session IDs; the application is not required to set the session ID. There is no need diameter rfc 4006 additional traffic between client and server in the case of tariff time changes for continuous time based service.
In a multi-service environment, an end user can issue an additional service request e. An example of this diameter rfc 4006 given in Appendix A Figure A.
Locally-generated errors, such as an unavailable peer or invalid route specification, cause the request send method to throw an IOException to with a detailed message indicating the nature of the failure.
For prepaid services, however, the diameter rfc 4006 user expects an answer from the network in a reasonable time. If several unit types are sent in the Answer message, the credit- control client MUST handle each unit type separately.
One of the granted units is allocated to be used before the potential tariff change, while the second granted units are for use after a tariff change. Diameter rfc 4006 answers to all pending messages are diameterr, the state machine moves to OPEN state, and Tx is stopped.
However, failover may occur at any point in the diameter rfc 4006 between the credit- control client and the credit-control server if a transport failure is detected with a peer, as described in [ DIAMBASE ].
The first approach uses credit-control messages after the user’s authorization and diameter rfc 4006 takes place. The OCF host must also be configured in the peer table as part of the global Diameter configuration. The Diameter protocol defines a policy protocol used by clients to perform policy, AAA, and resource control.
RFC – part 1 of 5
Diqmeter order to support failover between credit-control servers, information transfer about the credit-control session and account diameter rfc 4006 SHOULD take place between the primary and diameter rfc 4006 secondary credit-control server.
Table of Contents 1. When the final granted units have been consumed, the credit-control client MUST perform an intermediate interrogation. The sections that follow describe each model in more detail. Service A type of task performed by a service element for an end user.
The CCR is then sent to initiate credit re-authorization. This section defines the optional graceful service termination feature that MAY be supported by the diameter rfc 4006 server.