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 August 2014|
|PDF File Size:||7.5 Mb|
|ePub File Size:||15.71 Mb|
|Price:||Free* [*Free Regsitration Required]|
For AVPs of type Enumerated, the service may require a new value to be defined. AA answer commands are defined in service specific authorization applications, e. Network Working Group H.
The scope of this specification is the credit authorization. For session based credit-control, both the credit control client and the credit-control server are required to maintain credit-control session state. AA request commands are defined in service specific authorization applications e.
Service-Specific Rating Input and Interoperability The ” T ” Potentially re-transmitted message bit — This flag is set after a link failover procedure, to aid the removal of duplicate requests. A flexible credit-control application specific failure handling is defined in which the home service provider can model the credit- control client behavior according to prltocol own credit risk management policy.
The Diameter protocol defines a policy protocol used by clients to perform policy, AAA, and resource control. 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.
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.
Consequently, this needs to be considered when credit resources are granted to the services. 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.
Please refer protocoll the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol. The Diameter protocol was initially developed by Pat R.
The other Diameter applications provide service specific authorization, and they do not provide credit authorization for prepaid users.
This eiameter part of the basic protocol functionality and all stacks should support it and as such abstract from the connectivity related operations.
Upon receipt of a successful credit authorization answer with a certain amount of credit resources, the credit-control client allows service delivery to dlameter end user and starts monitoring the usage of the granted resources. Upon reboot implementations MAY set the high order 12 bits to contain the low order 12 bits of current time, and the low order 20 bits to a random value.
The application can be an authentication application, an accounting application or a vendor specific application. Obsolete RFCs are indicated with strikethrough text. The Diameter credit-control server is the entity responsible for credit authorization for prepaid subscribers.
When creating a request, the End-to-End Identifier is set to a locally unique value. The End-to-End Identifier is not modified by Diameter agents of any kind, and the same value in the corresponding request is used in the answer.
This field aids in matching requests and replies. Session state is not maintained.
RFC – Diameter Credit-Control Application
A Diameter Node to which a given Diameter Node has a direct transport connection. Credit-Control Application Overview The credit authorization process takes place before and during service delivery to the end user and generally requires the user’s authentication and authorization before any request is sent to the credit-control server.
Interrogation The Diameter credit-control client uses interrogation to initiate a session based credit-control process. 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. 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.
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. Views Read Edit View history. However, private services may be deployed that are subject to agreements between providers of the credit-control server and client.
If cleared, the message MUST be locally processed. The identifier MUST remain locally unique for a period of at least 4 minutes, even across reboots. Protocol transparent Diameter relays can exist between the credit- control client and credit-control rrc. A Business Support System is usually deployed; it includes at least dimeter billing functionality.