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):||16 June 2008|
|PDF File Size:||5.53 Mb|
|ePub File Size:||8.8 Mb|
|Price:||Free* [*Free Regsitration Required]|
This specification, together with the above service specific documents, governs the credit-control message. The real configuration can combine orotocol into a single host. As ofthe only value supported is 1. A host process that implements the Diameter protocol, and acts either as a Client, Agent or Server.
Diameter Credit-Control Application Protocol
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 rfcc applications.
Retrieved from ” https: AA request commands are defined in service specific authorization applications e. 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. A process through which two Diameter nodes establish end-to-end security. The first interrogation is used to reserve money from the user’s account and to initiate the process.
This process is accomplished with the one-time event. These agents transparently support the Diameter credit-control application. It is used between the Diameter credit-control client and the credit-control server to request credit authorization for a given service.
If an AVP with the prorocol 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. A structure used to encapsulate protocol specific data as well as authentication, authorization and accounting information. In next generation wireless networks, additional functionality is required beyond that specified in the Diameter base protocol. For session based credit-control, both the credit control client and the credit-control server are required to maintain credit-control session state.
When creating a request, the End-to-End Identifier is set to a locally unique value. An answer message that is received with an unknown identifier MUST be discarded. The credit-control application, therefore, does not define AVPs that could be used as input in the rating process.
Accounting protocols such as RADIUS accounting and the Diameter base accounting diametdr can be used to provide accounting data to the accounting server after service is initiated, and to provide possible interim reports until service completion. Additionally, application specific state machines can be introduced either later or at a higher abstraction layer. Network Working Group H. Standards Track Ericsson J-P.
In this case, vendor specific AVPs can be used. The Diameter base application needs to be supported by all Diameter implementations. The credit-control application also supports operations such as service price enquiry, user’s balance check, and refund of credit on the user’s account.
This section needs expansion. Service-Specific Rating Input and Interoperability AA request AA request generically refers to a service specific authorization and authentication request.
A Command Code is used to determine the action that is to be taken for a particular message. The credit-control server is required to maintain session state for session-based credit- control. In addition, it is necessary to check that the end user’s account provides coverage for the requested service prior to initiation of that service. Messages with the “E” bit set are commonly rff to as error messages.
Diameter makes use of the realm, also loosely referred to as domain, to determine whether messages can be satisfied locally, or fiameter they must be routed or redirected.
In the first model, the credit-control server rates the request, reserves a suitable amount of money from the user’s account, and pdotocol the corresponding amount of credit resources.
Adding a new optional AVP does not require a new application.
This field is used to detect duplicate messages. The credit-control server and AAA server in this architecture model are logical entities.
The ” E ” Error bit — If set, the message contains a protocol error, and the message will not conform to the CCF described for this command. The name is a play on words, derived from the RADIUS protocol, which is the predecessor a diameter is twice the radius.
It monitors the usage of the granted quota according to instructions returned by credit-control server. Retransmissions by other entities do not need to be tracked. During the credit-control process, it is used to report the used quota and request a new one. Typical credit-control protcol There can be multiple credit-control servers in the system for redundancy protockl load balancing. The specific service or rating group the request relates to is uniquely identified by the combination of Service-Context-Id and Service-Identifier or Rating-Group.
A Diameter Node to which a given Diameter Node has a direct transport connection.