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.
|Published (Last):||18 June 2018|
|PDF File Size:||6.4 Mb|
|ePub File Size:||11.97 Mb|
|Price:||Free* [*Free Regsitration Required]|
The End-to-End Identifier is an unsigned bit integer field in network byte order that is used to detect duplicate messages along with the combination of the Origin-Host AVP. Retransmissions by other entities do not need to be tracked. The final interrogation is used to exit the process.
Information on RFC » RFC Editor
Credit-control is a process of checking whether credit is available, credit-reservation, deduction of credit from the protocil user account when service is completed and refunding of reserved credit that is not used. In the first diamefer, 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.
Protocol transparent Diameter relays can exist between the credit- control client and credit-control server. Hop by Hop ID. A process through which two Diameter nodes establish end-to-end security. The credit-control server is required to maintain session state for session-based credit- control. However, prltocol real-time credit-control, these authorization and accounting models are not sufficient.
Diameter is used for many different interfaces defined by the 3GPP standards, with each interface typically defining new commands and attributes. Protoocol the latter case, the interface between the Service Element and the Diameter credit- control client is outside the scope of this diametet. Interrogation The Diameter credit-control client uses interrogation to initiate a session based credit-control process.
Total size of the AVP header and data in bytes. If an AVP with the ” M ” bit set is received by a Diameter client, server, proxy, or translation agent and either the AVP or its value is unrecognized, the message must be rejected. 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.
Messages with the “E” bit set are commonly referred to as error messages.
The Message Length field indicates the length of the Diameter message in bytes, including the header fields and the padded AVPs. Service A type of task performed by a service element for an end user. Also, Diameter Redirect agents that refer credit-control clients to credit-control servers and allow them to communicate directly can exist.
During the credit-control process, it is used to report the used quota and request a new one. Typical credit-control architecture There can be multiple credit-control servers in the system for redundancy and load balancing. Senders of request messages MUST insert a unique identifier on each message. The name is a play on words, derived from the RADIUS protocol, which is the predecessor a diameter is twice the radius.
Upon receipt of a successful credit authorization answer, the credit-control client allows service delivery to the end user.
The administrative domain providing services to a user. In addition, there are services such as gaming and advertising that may credit as well as debit a user account.
It belongs to the application layer protocols in the internet protocol suite. Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.
If Diameter credit-control proxies exist between the credit-control client and the credit-control server, they MUST advertise the Diameter credit-control application support. The Command Codes are as follows: It may also interact with business support systems. When an rcc is exhausted or expired, diametef user must be denied the ability to compile additional chargeable events.
In some cases it might be possible that the service element in ptotocol visited domain can offer diamfter to the end user; however, a commercial agreement must exist between the visited domain and the home domain. Consequently, this needs to be considered when credit resources are granted to the services. If set, the message is a request. When combined with the Vendor ID the attribute is uniquely identified.
The intermediate interrogations may be needed to request new quota while the service is being rendered. 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.
From Wikipedia, the free encyclopedia. Table of Contents 1. Used to identify to which application the message is applicable for.
Note that credit resources may not imply actual monetary credit; credit resources may be granted to the credit control client in the form of units e. The general principles for sending rating parameters are as follows: 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 diaketer answer.