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):||13 January 2017|
|PDF File Size:||14.40 Mb|
|ePub File Size:||14.27 Mb|
|Price:||Free* [*Free Regsitration Required]|
Intermediate Interrogation When all the granted service units for one unit type are spent by the end user or the Diameter rfc 4006 is diameter rfc 4006, the Diameter credit-control client MUST send a new Credit-Control-Request to the credit-control server. The services can be grouped into rating groups in order to achieve even further aggregation of credit allocation.
Developing Diameter Applications
Session based credit-control is described in more detail, with more variations, in section 5. The failure handling for credit-control sessions is defined in section 5. Unit determination refers to calculating the number of non-monetary units service units, time, events that can be assigned prior to delivering services. The type of the Granted-Service-Unit AVP diameter rfc 4006 be time, volume, service diameter rfc 4006, or money, depending on the type of diameteer event.
The credit-control process is performed to determine potential charges and to verify whether the diameter rfc 4006 user’s account balance is sufficient dfc cover the cost of the service being rendered. The recommended default initial value for Tw Twinit is 30 seconds. Diameter credit- control server.
Timer Tx has a default value of 10 seconds, but can be overridden using the tx. Similarly, the server can determine the units consumed at the before rate and the units consumed at the rate afterward in the event that the end-user closes the session diaketer the consumption of the allotted diameted. 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.
Certain applications require multiple credit-control sub-sessions. If service specific re-authorization is diameter rfc 4006 i. Upon receiving a successful authorization answer message with the Granted-Service-Unit AVP sthe credit-control client will grant the service to the end user and will generate an intermediate credit-control request, as required by using diameter rfc 4006 commands. The home Diameter AAA server diameter rfc 4006 make use of this credit-control message flow to deduce that the user’s activity is ongoing; therefore, it is recommended to set the authorization-lifetime to a reasonably high value diameter rfc 4006 credit-control diameter rfc 4006 used for the subscriber.
Figure 1 illustrates the typical credit-control architecture, which consists of a Service Element with an embedded Diameter credit- control client, a Diameter credit-control server, and an AAA server. The charging events can be immediate, event-based, or session-based. The server processes the received requests and returns an appropriate answer to both requests. Oracle Communications Converged Application Server provides a Diameter Online Charging Application that deployed applications can use to generate charging events based diaketer the Ro protocol.
RFC – part 1 of 5
If another entity working in conjunction with the Diameter credit- control application already provisions the access device with all the required filter rules for the end user, diameter rfc 4006 credit-control server presumably need not send diameter rfc 4006 additional filter.
In some service environments e. Credit-Control for Multiple Services within a sub- Session When multiple services are used within the same user session and each service or group of services is subject to different cost, it is necessary to perform credit-control for each service independently.
Use dmy dates from December Articles to be expanded from June All articles to be expanded Articles using small message boxes Articles to be expanded from December All articles with dead external links Articles with dead external links from July Wikipedia articles with GND identifiers Pages using RFC magic links.
The application init parameter ocs. It is diameter rfc 4006 to extend. This result code at command level implies that the credit-control session is to be terminated. Event Charging with Unit Reservation.
The corresponding realm definition must also exist in the global Diameter configuration. When the new granted units are received, these units apply from the point where the measurement of the reported used units stopped.
The Used-Service-Unit AVP contains the amount of used service units measured from the point when the service became diameter rfc 4006 or, if interim interrogations are used during the session, from the point when the previous measurement ended. The RFC defines an authorization and an accounting state machine. However, diameter rfc 4006 the user’s 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.
The credit-control server SHOULD rate the diameter rfc 4006 event and make a siameter from the end user’s account that covers the cost of the service event. The Twinit default value is 3 times more than the Tx recommended value. The credit-control server will reserve money from the user’s diameter rfc 4006, will rate the request and will send a Credit-Control-Answer message to the home Diameter AAA server.