The Diameter protocol is currently defined in the following IETF RFCs: Obsolete RFCs RFC , Diameter Credit-Control Application. RFC (part 1 of 5): Diameter Credit-Control Application. Please refer to the current edition of the “Internet Official Protocol Standards” (STD 1) for the. IETF RFC “Diameter Credit Control Application”. []. Void. []. IETF RFC , “Private Extensions to the Session Initiation Protocol (SIP) for the 3rd.

Author: Nejas Nek
Country: Honduras
Language: English (Spanish)
Genre: Literature
Published (Last): 21 July 2005
Pages: 127
PDF File Size: 6.81 Mb
ePub File Size: 16.23 Mb
ISBN: 299-6-41686-976-7
Downloads: 32863
Price: Free* [*Free Regsitration Required]
Uploader: Zulkirg

Retransmissions by other entities do not need to be tracked. Transaction state implies that upon forwarding a request, its Hop-by-Hop Identifier is saved; the field is replaced with a locally unique identifier, which is restored to its original value when the corresponding answer is received.

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. If cleared, the message MUST be locally processed. Senders of request messages MUST insert a unique identifier on each message. A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm.

The prepaid model has been shown to be very successful, for instance, in GSM networks, where network operators offering prepaid services have experienced a substantial growth of their customer base and revenues. An administrative domain MAY act as a local realm for certain users, while being a home realm for others.

Retrieved from ” https: This is part of the basic protocol functionality and all stacks should support it and as such abstract from the connectivity related operations. Diameter Applications can extend the base protocol by adding new commands, attributes, or both. In some cases it might be possible that the service element in the visited domain can offer services to the end user; however, a commercial agreement must exist between the visited domain and the home domain.


In this case, vendor specific AVPs can be used.

Credit-Control Application Overview The credit authorization process takes place before and during service delivery to the end user and generally requires the user’s authentication and authorization before any request is sent to the credit-control server. The application can be an authentication application, an accounting application, or a vendor-specific application.

If set, the message MAY be proxied, relayed or redirected. The credit-control server is required to maintain session state for session-based credit- control. The Diameter base application needs to be supported by all Diameter implementations. Archived from the original on 4 July These formats are observed in Credit-Control messages. The credit-control application defined in this specification supports two different credit authorization models: Upon reboot implementations MAY set the high order 12 bits to contain the low order 12 bits of current time, and the low order 20 bits to a random value.

These operations are accomplished with the one- time event. The Diameter credit-control server is the entity responsible for credit authorization for prepaid subscribers. The real configuration can combine them into a single host.

RFC – Diameter Credit-Control Application

The sender MUST ensure that the identifier in a protpcol is unique on a given connection at any diaemter time, and MAY attempt to ensure that the number is unique across reboots. The other Diameter applications provide service specific authorization, and ffc do not provide credit authorization for prepaid users. This process is accomplished with the one-time event. Accounting protocols such as RADIUS accounting and the Diameter base accounting protocol can be used to provide accounting data to the accounting server after service is initiated, and to provide possible interim reports until service completion.

System internal interfaces can exist to relay messages between servers and an account manager. To fulfill these requirements, it is necessary to facilitate credit- control communication between the network element providing the service e.


This field aids in matching requests and replies. Messages with the “E” bit set are commonly referred to as error messages. The scope of this specification is the credit authorization.

It provides a general solution to real-time cost and credit-control. This specification, together with the above service specific documents, governs the credit-control message. Service-Specific Rating Input and Interoperability The Diameter credit-control application defines the framework for credit-control; it provides generic credit-control mechanisms supporting multiple service applications.

A mechanism has to be provided to allow the user to be informed of the charges to be levied for a requested service.

The string in the NAI that immediately follows the ‘ ‘ character. Messages with this bit set are commonly referred to as error messages. The credit-control process is performed to determine potential charges and to verify whether the end user’s account balance is sufficient to cover the cost of the service being rendered.

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. Pgotocol administrative domain providing services to a user.

Diameter (protocol)

It is used between the Diameter credit-control client and the credit-control server to request credit authorization for a given service. Application-ID is used to identify for which Diameter application the message is applicable. Therefore, it is assumed that a Diameter credit-control server will provide service only for Diameter credit-control clients that have agreed beforehand as to the content of credit-control messages. The credit authorization shall be generic and applicable to all the service environments required to support prepaid services.

The identifier MUST remain locally unique for a period of at least 4 minutes, even across reboots.