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.
|Country:||Turks & Caicos Islands|
|Published (Last):||16 May 2012|
|PDF File Size:||15.39 Mb|
|ePub File Size:||16.67 Mb|
|Price:||Free* [*Free Regsitration Required]|
The values are for permanent, standard commands allocated by IANA.
An answer message that is received with an unknown identifier MUST be protocoll. The originator of an Answer message MUST ensure that the field contains the same value that was found in the corresponding request. Session state is not maintained. Additionally, application specific state machines can be introduced either later or at 400 higher abstraction layer.
The Command Codes are as follows: When combined with the Vendor ID the attribute is uniquely identified.
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.
The first interrogation is used to reserve money from the user’s account and to initiate the idameter.
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. Prepaid services are now cropping up in many other wireless and wire line based networks. These agents transparently support the Diameter credit-control application.
In a multi-service environment, an end user can issue an additional service request e. A host process that implements the Diameter protocol, and acts either as a Client, Agent or Server.
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.
Credit-control Credit-control is a mechanism that directly interacts in real-time with an account and controls rrfc monitors the charges gfc to the service usage. This allows a single server to handle policies for many services. Diameter is used for many different interfaces defined prottocol the 3GPP standards, with each interface typically defining new commands and attributes. Diameter Applications can extend the base protocol by adding new commands, attributes, or both.
RFC – Diameter Credit-Control Application
A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm. It belongs to the application layer protocols in the internet protocol suite. In order to support real-time credit-control, a new type of server is needed in the AAA infrastructure: If set, the message is a request.
System internal interfaces can exist to relay messages between servers and an account manager. The credit-control server deducts the used amount from the end user’s account; it may perform rating and make a new credit reservation if the service delivery is continuing.
In addition, there are services such as gaming and advertising that may credit as well as debit a user account. Network Working Group H. The Hop-by-Hop Identifier is an unsigned bit integer field in network byte order that is used to match the requests with their answers as the same value in the request is used in the response.
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. 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.
This field indicates the version of the Diameter Base Protocol. Service Element A network element that provides a service to the diamter users.
The scope of this specification is the credit authorization. The specification of another cooperative standardization body e. TPotentially retransmitted message. The Diameter base application needs to be supported by all Diameter implementations.
The credit-control application, therefore, does not define AVPs that could be used as input in the rating process. The other Diameter applications provide service specific authorization, and they do not provide credit authorization for prepaid users. The Diameter protocol requires that relaying and proxying agents maintain transaction state, which is used for failover purposes. Listing the possible services that could use this Diameter application is out of scope for this generic mechanism.
The credit-control application defined in this specification supports two different credit authorization models: This field aids in matching requests and replies. Service Event An event relating dimaeter a service provided to the end user. A mechanism has to be provided to allow the user to be informed of the charges to be levied for a requested service.