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):||27 April 2018|
|PDF File Size:||10.33 Mb|
|ePub File Size:||8.27 Mb|
|Price:||Free* [*Free Regsitration Required]|
Consequently, this needs to be dimaeter when credit resources are granted to the services. This method can be used to avoid unnecessary conversions from an existing data format to an AVP format.
When set the AVP Code belongs to the specific vendor code address space. It is used between the Diameter credit-control client and the credit-control server to request credit authorization for a given service. The general principles for sending rating parameters protocoll as follows: The combination of the Origin-Host and this field is used to detect duplicates.
The credit-control application defined in this specification supports two different credit authorization models: The specification of another cooperative standardization body e.
In addition, there are services such as gaming and advertising that may credit as well as debit a user account. In next generation wireless networks, additional functionality is required beyond that specified in the Diameter base protocol.
The administrative domain providing services to a user. The Diameter protocol defines a policy protocol used by clients to pdotocol policy, AAA, and resource control. Session based credit-control is described in more detail, with more variations, in section 5. The dlameter in the NAI that immediately follows the ‘ ‘ character. This process is accomplished with session based credit-control that includes the first interrogation, possible intermediate interrogations, and the final interrogation.
This flag is set after a link failover procedure, to aid the removal of duplicate requests. Credit-control is a process of checking whether credit is available, credit-reservation, deduction of credit from the end user account when service is completed and refunding of reserved credit that is not used.
Diameter (protocol) – Wikipedia
However, private services may be deployed that are subject to agreements between providers of the credit-control server and client. The Diameter protocol was initially developed by Pat R. This field diameer in matching requests and replies. 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.
However, for real-time credit-control, these authorization and accounting models are not sufficient. To ensure that the end user’s account is not debited or credited multiple times for the same service event, only one place in the credit-control system should perform duplicate detection.
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. Diameter Relay and redirect agents diameteg not reject messages with unrecognized AVPs. The credit-control server is required to maintain session state for session-based credit- control.
This specification, together with the above service specific documents, governs the credit-control message. It belongs to the application layer protocols in the internet protocol suite. Retrieved 30 April Obsolete RFCs are indicated with strikethrough text. These formats are observed in Credit-Control messages. In contrast, credit authorization with direct debiting is a single transaction process wherein the credit-control server directly deducts a suitable amount of money from the user’s account as soon as the credit authorization request is received.
A flexible credit-control application specific diametfr handling is defined in which the home service provider can model the credit- control client behavior according to its own credit risk management policy. 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.
Diameter agents only need to be concerned about the number of requests they send based on a single received request. Credit-Control Application Related Parameters Listing the possible services that could use this Diameter application is out of scope pfotocol this generic mechanism.
Service 406 authorization and authentication is out of the scope. Typical credit-control architecture There can be multiple credit-control servers in the system for redundancy and load balancing.
Diameter makes use 400 the realm, also loosely referred to as domain, to determine whether messages can be satisfied locally, or whether they must be routed or redirected. The application can be an authentication application, an accounting application, or a vendor-specific application.
An answer message that is received with an unknown identifier MUST be discarded.
Rating The act of determining the cost of the service event. These operations are accomplished with the one- time event. The administrative domain with which the user maintains an account relationship. In order to support real-time credit-control, a new type of server is needed in the AAA infrastructure: In the first model, 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.
Additionally, application specific state machines can be introduced either later or at a higher abstraction layer.