Oracle Server E10293-02 ユーザーズマニュアル
3GPP/Rf Diameter Java API
Oracle Diameter Java APIs
A-5
3GPP/Rf Diameter Java API
This section defines a Java API for the 3GPP [TS 32.299] Rf Interface over the Diameter
protocol ([TS 32.225], [TS 32.200] and [TS 32.240] in order to specify).
protocol ([TS 32.225], [TS 32.200] and [TS 32.240] in order to specify).
3GPP/Rf Diameter Java Interface
This section describes the Java interface.
Rf Provider
The DiameterRfProvider interface represents a Rf Diameter Application as defined in
3GPP Interfaces. An instance of a class implementing this interface can be obtained by
calling the DiameterStack.createDiameterRfProvider(Properties, refFSM). The different
values of refFSM are:
3GPP Interfaces. An instance of a class implementing this interface can be obtained by
calling the DiameterStack.createDiameterRfProvider(Properties, refFSM). The different
values of refFSM are:
■
RFC_SRV_LESS for Rfc 3588 stateless server state machine
■
RFC_SRV_FULL for Rfc 3588 stateful server state machine
■
RFC_CL for Rfc 3588 client state machine
The Properties parameter specifies the features that will be handled by this Rf
provider. This is a list of properties which may contain a number of options. See
section [3.2.6] for know more about Rf Application options.
provider. This is a list of properties which may contain a number of options. See
section [3.2.6] for know more about Rf Application options.
Rf Listener
The DiameterRfListener interface processes accounting messages that are received by
the DiameterRfProviderImpl class implementing the DiameterRfProvider interface. A
DiameterRfListener instance is registered to a provider by the following method
DiameterRfProvider. setDiameterRfListener ().
the DiameterRfProviderImpl class implementing the DiameterRfProvider interface. A
DiameterRfListener instance is registered to a provider by the following method
DiameterRfProvider. setDiameterRfListener ().
This interface provides two principles methods: accountingRequestReceived() and
accountingAnswerReceived(). The first one must be implemented and called when the
option AUTO_ANSWER is set to false. In this case, the server must be able to create an
accounting answer corresponding to the received accounting request. The second one
processes the received accounting answer.
accountingAnswerReceived(). The first one must be implemented and called when the
option AUTO_ANSWER is set to false. In this case, the server must be able to create an
accounting answer corresponding to the received accounting request. The second one
processes the received accounting answer.
Rf Message Factory
The DiameterRfMessageFactory interface provides factory methods that enable an
application to create Diameter Rf messages as defined in 3GPP:
createAccountingRequest() and createAccountingAnswer(). An instance of a class
implementing this interface can be obtained by calling the
DiameterStack.getRfDiameterMessageFactory() method.
application to create Diameter Rf messages as defined in 3GPP:
createAccountingRequest() and createAccountingAnswer(). An instance of a class
implementing this interface can be obtained by calling the
DiameterStack.getRfDiameterMessageFactory() method.
Messages created by this factory are as following:
■
Accounting-Request (ACR)--The first following method creates a basic ACR (with
only mandatory AVPs) and the second one creates a more sophisticated ACR with
the most used AVPs as defined in 3GPP:
only mandatory AVPs) and the second one creates a more sophisticated ACR with
the most used AVPs as defined in 3GPP:
■
DiameterMessage
createAccountingRequest (String Destination-Realm,
int Accounting-Record-Type,
int Accounting-Record-Number)
■
DiameterMessage
createAccountingRequest(String Destination-Realm,
int Accounting-Record-Type,