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):||19 March 2007|
|PDF File Size:||9.13 Mb|
|ePub File Size:||17.4 Mb|
|Price:||Free* [*Free Regsitration Required]|
Additional service event information to be rated. After that the transport connection can be disconnected. If another diameter rfc 4006 working in conjunction with the Diameter credit- control application already provisions the access device with all the required filter rules for the end user, the credit-control server presumably need not rfd any additional filter.
Retrieved 12 October Credit-Control Application State Machine 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 diameter rfc 4006 should perform duplicate ffc.
RFC – part 1 of 5
If cleared, the 40006 is an answer. When session based credit-control is used for diameter rfc 4006 subscriber, a constant credit-control message stream flows through diameter rfc 4006 home Diameter AAA server. If credit-control is required the credit-control server needs to be contacted prior to initiating service delivery to the end user. Rating The act of determining the cost of the service event.
Information on RFC » RFC Editor
Consequently, this needs to be considered when credit resources are granted to the services. A flexible credit-control application specific failure diameter rfc 4006 is defined in which the home service diameter rfc 4006 can model the credit- control client behavior according to 40006 own credit risk management policy.
User disconnected due to exhausted account 5. Some common Diameter commands defined in the protocol base and applications are:.
If diameter rfc 4006 re-authorization is ongoing at the time when the RAR message is received diameetr. It is always up to the Diameter credit-control client to send a new request well in advance of the expiration of the previous request in order to avoid interruption in the service element.
Protocol example with use of the authorization messages for the first interrogation 5.
Session based credit-control A credit-control process that makes use of several interrogations: These actions may be communicated explicitly from the server to the client or may be configured per-service at the client.
In the first model, the credit-control server rates the request, reserves a suitable amount of money from the user’s account, and returns the corresponding amount of credit resources. Even if the granted service units reserved by the credit- control server have not been spent upon expiration diameteer the Validity- Time, the Diameter credit-control client MUST send a new Diameter rfc 4006 Control-Request to the credit-control server.
ECUR begins with an interrogation to reserve units before delivering services, followed by an additional interrogation to report the actual used units diameter rfc 4006 the OCF upon service termination. The first approach uses credit-control messages diametdr the user’s authorization and authentication takes place. For instance, during one network access session the end user may use several http-services subject diameter rfc 4006 different access cost.
Telecommunication management; Charging management; Diameter charging applications.
Diameter Credit-Control Application
In this case, the graceful termination process installs a set of packet filters to restrict the user’s.
This is illustrated in Figures 2 and 3. Diameter rfc 4006 the Diameter credit-control client knows the cost of the service event e.
In addition, it is necessary to check that the end user’s account provides coverage for the requested service prior to initiation of that service. It MAY rate the new request and make a new credit- reservation from the end user’s account that covers the cost of the requested service event. Credit authorization with direct debiting uses immediate charging events. Online charging, also known as credit-based charging, is used to charge prepaid services.
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. Where independent credit-control of multiple services diameter rfc 4006 supported, this process may be executed for one diameter rfc 4006 more services, a single rating-group, or a pool within the sub session. Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.
If S is the total service units within the diameter rfc 4006, M1, M2, This field indicates the version of the Diameter Base Protocol. However, the user’s account might be empty when this first interrogation is performed. Figure 1 illustrates the typical credit-control architecture, which consists of a Service Element with an embedded Diameter credit- diameter rfc 4006 client, a Diameter credit-control server, and an AAA server.
If the credit-control client receives a successful answer from the backup diameter rfc 4006, it continues the credit-control session with such a server.
This allows a single server to handle policies for many services. Typical credit-control architecture There can be multiple credit-control servers in the system for redundancy and load balancing.
However, when the diameter rfc 4006 account cannot cover the cost of the requested service, the action taken is the responsibility of the credit-control server that controls the prepaid subscriber. However, private services may be deployed that are subject to agreements between providers of the credit-control server and client.
It is up to the credit-control server whether to authorize credit for one or more services or for the whole rating-group. 44006 Connection diameter rfc 4006 Redirects In this case, vendor specific AVPs can be used.
The Frc diameter rfc 4006 packaged as a Diameter application similar to the Sh application used for managing profile data.
It is assumed that the service element is provided with Rating-Groups, Ffc, and their associated parameters that define what has to be metered by means outside the scope of this specification.