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 April 2017|
|PDF File Size:||7.37 Mb|
|ePub File Size:||11.78 Mb|
|Price:||Free* [*Free Regsitration Required]|
Diameter Credit-control Client A Diameter credit-control client is an entity that interacts with a credit-control server.
This field aids in matching requests and replies. The prepaid model has been shown to be very successful, for instance, in GSM gfc, where network operators offering prepaid services have experienced a substantial growth diametr their customer base and revenues. The combination of the Origin-Host and this field is used to detect duplicates. Diameter Relay and redirect agents must not reject messages with unrecognized AVPs. 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.
In addition, there are services such as gaming and advertising that may credit as well as debit a user account. The administrative domain providing services to a user. The Diameter base application needs to be supported by all Diameter implementations.
The system can also contain separate rating server sand accounts can be located in a centralized database. However, private services may be deployed that are subject to agreements between providers of the diamefer server and client.
System internal interfaces can exist to relay messages between servers and an account manager. These operations are accomplished with the one- time event. These formats are observed in Credit-Control messages. Service Event An event relating to a service provided to the end user. A structure rdc to encapsulate protocol specific data as well as authentication, authorization and accounting information. Credit-Control Application State Machine When the credit resources granted to the user have been consumed or the service has been successfully delivered or terminated, the credit-control client reports back to the server the used amount.
Retransmissions by other entities do not need to be tracked. The first interrogation is used to reserve money from the user’s account and to initiate the process. In both models, the credit- control client requests credit authorization from the credit-control server prior to allowing any service to be delivered to the end user. The originator of an Answer message MUST ensure that the field contains the same value that was found in the corresponding request.
However, for real-time credit-control, these authorization and accounting models diamdter not sufficient. These agents transparently support the Diameter credit-control application.
The Hop-by-Hop Identifier is an unsigned bit integer field in network byte order that is used to match the requests with their djameter as the same value in the request is used in the response. The string in the NAI that immediately follows the ‘ ‘ character. Size of the Diameter message including the header fields.
The ” R ” Request bit — If set, the message is a request. 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.
Service-Specific Rating Input and Interoperability The Proocol credit-control application defines the framework for credit-control; it provides generic credit-control mechanisms supporting multiple service applications.
Network Working Group H. Diameter Applications can extend the base protocol by adding new commands, attributes, or both. It is used between the credit-control server and the Diameter credit-control client to rgc a Credit- Control-Request command.
Listing the possible services that could use this Diameter application is out of scope for this generic mechanism.
RFC – part 1 of 5
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. This process is accomplished with the one-time event. This page was last edited on 19 Octoberat Archived from the original on 4 July The sender MUST ensure that the identifier in a request is unique on a given connection at any given time, and MAY attempt to ensure that the number is unique across reboots.