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

Author: Kazigar Bradal
Country: Oman
Language: English (Spanish)
Genre: Love
Published (Last): 7 March 2015
Pages: 20
PDF File Size: 3.42 Mb
ePub File Size: 4.66 Mb
ISBN: 456-3-82892-539-6
Downloads: 18503
Price: Free* [*Free Regsitration Required]
Uploader: Malakazahn

Diameter Credit-Control Application

The credit-control application defined in this specification supports two different credit authorization models: The application init parameter ocs. The administrative domain providing services to a user. In order to support real-time credit-control, a new type of server is needed in the AAA infrastructure: When combined diametdr the Vendor ID the attribute is uniquely identified.

The base diameter package, com.

Diameter (protocol)

Thus, the Diameter credit-control client will react faster than would the underlying base protocol. This section needs expansion. Network Working Group H. If S is the total service units within the pool, M1, M2, If credit-control is not required for the subscriber, the home Diameter AAA diameher will respond as usual, with an appropriate AA answer message.

Retrieved 12 October Therefore this specification defines the timer Tx that is used by the credit-control client as defined in section 13 to supervise the communication with the credit-control server. Upon receiving a RAR, the Diameter subsystem invoke the session listener on the applications corresponding RoSession rcf.


RFC – part 1 of 5

Upon expiration of the Validity-Time, the credit-control client MUST generate a credit- control update request and report the used quota to the credit- control server.

Explicitly signaled redirect or restrict instructions always take precedence over configured ones. If the user logs off during an ongoing credit-control session, or if some other reason causes the user to become logged off e. Views Read Edit View history. Example shows an example of how to create and send a CCR. The first, the intermediate, and the final interrogations are executed with credit- control commands defined in this specification.

When the used units are reported to the credit-control server, the credit-control client will not have any units in its possession before new granted units are received from the credit-control server. The credit-control server MUST deduct the used amount from the end user’s account.

This specification, together with the above service specific documents, governs the diametef message. It is also possible to request and allocate quotas on a per service basis. With SCUR, it is also possible to include one or more intermediate interrogations for the CTF in order to report currently-used units, and to dia,eter additional units if required. 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.


For time based services, the quota is continuously consumed at the idameter rate of 60 seconds per minute. The client starts by requesting 10 units from the server.

QoS are common to all the services carried within the access bearer, but the cost ffc the bearer may vary depending on its content. 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 before the consumption of the allotted quota.

If the Diameter credit-control client knows the cost of the service event e. Received answers that do not match a known Hop-by-Hop Identifier are ignored by the Diameter agent. Other IETF standards or standards developed by other standardization bodies may define the most suitable method in their architectures.

Service-Identifiers enable authorization on a per-service based credit as well as itemized reporting of service usage. 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.