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):||5 November 2012|
|PDF File Size:||3.29 Mb|
|ePub File Size:||1.89 Mb|
|Price:||Free* [*Free Regsitration Required]|
The credit-control application also supports operations diameter rfc 4006 as service price enquiry, user’s balance check, and refund of credit on the user’s account. The dfc server is required to maintain session state for session-based credit- control. When the new granted units are received, these units diameter rfc 4006 from the point where the measurement of the reported used units stopped. This is part of the basic protocol functionality and all stacks should support it and as such abstract from the connectivity related operations.
Whether the credit-control message stream is moved to a backup credit-control server during an ongoing credit-control session depends on the value of the CC-Session-Failover AVP.
If service specific re-authorization fails, the user will be disconnected, and the credit-control client MUST send a final interrogation to the credit-control diameter rfc 4006.
Diameter Credit-control Rdc Diameter rfc 4006 Diameter credit-control client is an entity that interacts with a credit-control server.
Diameter Credit-Control Application
Credit-control Credit-control rrfc a mechanism that directly interacts diameter rfc 4006 real-time with an account and controls or monitors the charges related to the service usage. The End-to-End Identifier is not modified by Diameter agents of any kind, and the same value in the corresponding request is used in the answer. Adding a new optional AVP does not require a new application. If the user logs off during an ongoing credit-control session, or if some other reason causes the user to become logged off e.
With IEC, a single transaction is created where the OCF deducts a specific amount from the user’s account immediately after completing the credit authorization. Views Read Edit View history.
Diameter Applications can extend the base protocol by adding new commands, attributes, or both. When an diiameter user requests services such as SIP or messaging, the request is typically forwarded rfd a service element e.
Also, Diameter Redirect agents diameter rfc 4006 refer credit-control clients to credit-control servers and allow them to communicate directly can exist. Oracle Communications Converged Application Server provides a Diameter Diameter rfc 4006 Charging Application that deployed applications can use to generate charging events based on the Ro protocol. How the credit-control server uses this information is outside the scope of diameter rfc 4006 document. The OCF host must also be configured in the peer table as part of the global Diameter configuration.
Distribution of this memo is unlimited. To support these scenarios optimally, the credit-control application enables independent credit-control of multiple services in a single credit-control sub- session.
If efc communication failure occurs during the graceful service termination procedure, the service element SHOULD diameter rfc 4006 terminate the ongoing service session. Note that the RoSession class automatically handles creating session IDs; the application is not diameter rfc 4006 to set the session ID.
Service specific authorization and authentication is out of the scope. This specification, together with the above service specific documents, governs the credit-control message.
RFC – part 1 of 5
diameter rfc 4006 After final interrogation, the credit-control server MUST refund the reserved credit amount not used to the end user’s account and deduct the used monetary amount from the end user’s account. The ” R ” Request bit — Diameher set, the message is a request. After that the transport connection can be disconnected. System internal interfaces can exist to relay messages between servers and an account manager. In both models, the credit- control client requests credit authorization from the credit-control server prior to allowing diameter rfc 4006 service to be delivered to the end user.
Diameter Credit Control Application. The server will return the appropriate Result-Code see section 9.
Explicitly signaled redirect or restrict instructions always take precedence over configured ones. Therefore, tuning the timer Twinit to a lower value in order to satisfy the requirements of real-time applications, such diameterr the Diameter credit-control application, diameter rfc 4006 certainly cause the above mentioned problems.
More credit-control sequence examples are given in Annex A.