DIAMETER PROTOCOL RFC 4006 PDF
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):||4 December 2012|
|PDF File Size:||5.66 Mb|
|ePub File Size:||4.43 Mb|
|Price:||Free* [*Free Regsitration Required]|
It may also interact with business support systems. The packet consists of a Diameter header and a variable diametet of Attribute-Value Pairs, or AVPs, for encapsulating information relevant to the Diameter message.
These formats are observed in Credit-Control messages. 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 ddiameter.
Abstract 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.
The sender of an Answer message MUST ensure that this field contains the same value that was found in the corresponding request. Diameter Credit-control Client A Diameter credit-control client is an idameter that interacts with a credit-control server.
Service Element A network element that provides a service to the end users. In this case, vendor specific AVPs can be used.
Credit-Control Application Overview The credit authorization diiameter 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. When creating a request, the End-to-End Identifier is set to a locally unique value.
Session based credit-control is described in more detail, with more variations, in section 5. 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.
If cleared, the message MUST be locally processed. The other Diameter applications provide service specific authorization, and they do not provide credit authorization for prepaid users. When combined with the Vendor ID the attribute is uniquely identified. For session based credit-control, both the credit control client and the credit-control server are required to maintain credit-control session state.
The identifier is normally a monotonically increasing number, whose start value was randomly generated. The final interrogation is used to exit the process. A Business Support System is usually deployed; it includes at least the billing functionality.
These agents transparently support the Diameter credit-control application. The Diameter protocol defines a policy protocol used by clients to perform policy, AAA, and resource control. This section needs expansion. Service specific authorization and authentication is out of the scope.
The credit-control process is performed to determine potential charges and to verify whether the end user’s account balance is sufficient to cover the cost of the service being rendered. Messages with this bit set are commonly referred to as error messages. The name is a play on words, derived from the RADIUS protocol, which is the predecessor a diameter is twice the radius.
The administrative domain with which the user maintains an account relationship. AA request AA request generically refers to a service specific authorization and authentication request. After that the transport connection can be disconnected. The combination of the Origin-Host and this field is used to detect duplicates.
RFC – part 1 of 5
Diameter Relay and redirect agents must not reject messages with unrecognized AVPs. This field is used to detect duplicate messages. In some cases it might be protoco, 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.
End to End ID. If set, the message contains a protocol error, and the message will not conform to the ABNF described for this command.
Standards Track Ericsson J-P.
Loughney Nokia August Diameter Fiameter Application Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.
Diameter credit- control server. ;rotocol transparent Diameter relays can exist between the credit- control client and credit-control server. 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 to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.