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):||18 May 2016|
|PDF File Size:||13.98 Mb|
|ePub File Size:||13.34 Mb|
|Price:||Free* [*Free Regsitration Required]|
This specification, together with the above service specific documents, governs the credit-control message. 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.
However, private services may be deployed that are subject to agreements between providers of the credit-control server and client.
The credit-control server is required to maintain session state for session-based credit- control. Diameter credit- control server. Additionally, application specific state machines can be introduced either later or at a higher abstraction layer.
Information on RFC » RFC Editor
Service Event An event relating to a service provided to the end user. 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. Service-Specific Rating Input and Interoperability The intermediate interrogations may be needed to request new quota while the service is being rendered. This process is accomplished with the one-time event. 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.
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. When real-time credit-control is required, the credit-control client contacts the credit-control server with information about a possible service event.
Service specific authorization and authentication is out of the scope. The identifier is normally a monotonically increasing number, whose start value was randomly generated. NAI realm names are required to be unique, and are piggybacked on the administration of the DNS namespace.
Protocol transparent Diameter relays can exist between the credit- control client and credit-control server. The RFC defines a core state machine for maintaining connections between peers and processing messages. It belongs to the application layer protocols in the internet protocol suite. It is used between the Diameter credit-control client and the credit-control server to request credit authorization for a given service.
This field indicates the version of the Diameter Base Protocol. Prepaid services are now cropping up in many other wireless and wire line based networks. A mechanism has to be provided to allow the user to be informed of the charges to be levied for a requested service. If cleared, the message MUST be locally processed. 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 section needs expansion. The Message Length field indicates the length of the Diameter message in bytes, including the header fields and the padded AVPs. Network access is an example of a service offered in the visited domain where the NAS, through an AAA infrastructure, authenticates and authorizes the user with the user’s home network.
In a multi-service environment, an end user can issue an additional service request e. A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm.
The credit-control process is performed to rff potential charges and to verify whether the end user’s account balance is sufficient to cover the cost of the service being rendered. This page was last edited on 19 Octoberat The Diameter base application needs to be supported by all Diameter implementations.
The End-to-End Identifier is not modified by Diameter agents of diametter kind, and the same value in the corresponding request is used in the answer.
In some cases it might be possible that the service element in the visited domain can offer services to the end user; however, a commercial agreement must exist between the visited domain and the home domain. Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.
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. The string in the NAI that immediately follows the ‘ ‘ character. End to End ID. The specification of another cooperative standardization body e.
Credit-Control Application Related Parameters 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. When combined with the Vendor ID the attribute is uniquely identified. AA request AA request generically refers to a service specific authorization and authentication request.