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 March 2014|
|PDF File Size:||1.74 Mb|
|ePub File Size:||9.61 Mb|
|Price:||Free* [*Free Regsitration Required]|
RFC – part 1 of 5
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.
This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications.
The diametfr process is performed to determine potential charges and to verify whether the end user’s account balance is protocool to cover the cost of the service being rendered. It is set when resending requests not yet acknowledged, as an indication of a possible duplicate due to a link failure.
During the credit-control process, it is used to report the used quota and request a new one. If set, the message contains a protocol error, and the message will not conform to the ABNF described for this command.
Diameter Credit-Control Application Protocol
Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol. Rfx is set when resending requests not yet acknowledged as an indication of a possible duplicate due to a link failure. However, the detailed architecture of the credit-control system and its interfaces are implementation specific and are out of diametsr of this specification.
If cleared, the message MUST be locally processed. Upon receipt of a successful credit authorization prltocol with a certain amount of credit resources, the credit-control client allows service delivery to the end user and starts monitoring the usage of the granted doameter. A Diameter Node to which a given Diameter Node has a direct transport connection.
Loughney Nokia August Diameter Credit-Control Application Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.
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. 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 Command Codes are as follows: The system can also contain separate rating server sand accounts can be located in a centralized database. Protocol transparent Diameter relays can exist between the credit- control client and credit-control server. Otherwise the message MUST be locally processed. The identifier is normally a monotonically increasing number, whose start value was randomly generated. Messages with protocl “E” bit set are commonly referred to as error messages.
In a multi-service environment, an end user can issue an additional service request e. Used to extract the identity and realm of a user.
A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm. These operations are accomplished with the one- time event.
The credit-control application, therefore, does not define AVPs that could be used as input in the rating process. In rc latter case, the interface between the Service Element and the Diameter credit- control client is outside the scope of this specification. Rating The act of determining the cost of the service event.
The credit authorization shall be generic and applicable to all the service environments required to support prepaid services. The values are for permanent, standard commands allocated by IANA. The administrative domain with which the user maintains an account relationship. 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.
This field indicates the version of the Diameter Base Protocol. However, private services may be deployed that are subject to agreements between providers of the credit-control server and client.
When set the AVP Code belongs to the specific vendor code address space. 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.
When combined with the Vendor ID the attribute is uniquely identified.
Direct Connection with Redirects Used to identify proyocol which application the message is applicable for. The RFC defines a core state machine for maintaining connections between peers and processing messages. This section needs expansion. Obsolete RFCs are indicated with strikethrough text.
Introduction This document specifies a Diameter application that can be used to implement real-time credit-control for a variety of end user services such as network access, Session Initiation Protocol SIP services, messaging services, and download services.
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. Adding a new optional AVP does not require a new application.
Service A diametfr of task performed by a service element for an end user. The Diameter protocol requires that relaying and proxying agents maintain transaction state, which is used for failover purposes. This method can be used to avoid unnecessary conversions from an existing data format to an AVP format. 406 answer commands are defined in service specific authorization applications, e. Credit-control Credit-control is a mechanism that directly interacts in real-time with an account and controls or monitors the charges related to the service usage.
If set, the message MAY be proxied, relayed or redirected. The credit-control application defined in this specification supports two different credit authorization models: It can be set only in cases where no answer has been received from the server for a request and the request is sent again.
Prepaid services are now cropping up in many other wireless and wire line based networks. NAI realm names are required to be unique, and are piggybacked on the administration of the DNS namespace. This is part of the basic protocol functionality and all stacks should support it and as such abstract from the connectivity related operations.