Oracle Server E10293-02 Benutzerhandbuch
3GPP/Ro DIAMETER JAVA API
A-10
Oracle Communication and Mobility Server Developer’s Guide
Ro Listener
The DiameterRoListener interface processes accounting messages that are received by
the DiameterRoProviderImpl class implementing the DiameterRoProvider interface. A
DiameterRoListener instance is registered to a provider by the following method
DiameterRoProvider. setDiameterRoListener ().
the DiameterRoProviderImpl class implementing the DiameterRoProvider interface. A
DiameterRoListener instance is registered to a provider by the following method
DiameterRoProvider. setDiameterRoListener ().
This interface provides four principles methods: creditControlRequestReceived(),
creditControlAnswerReceived(), reAuthRequestReceived() and
reAuthAnswerReceived().The first and third 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 and last methods process the received accounting answers.
creditControlAnswerReceived(), reAuthRequestReceived() and
reAuthAnswerReceived().The first and third 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 and last methods process the received accounting answers.
Ro Message Factory
The DiameterRoMessageFactory interface provides factory methods that enable an
application to create Diameter Ro messages as defined in 3GPP:
createCreditControlRequest(), createCreditConrolAnswer(), createReAuthRequest()
and createReAuthAnswer(). An instance of a class implementing this interface can be
obtained by calling the DiameterStack.getRoDiameterMessageFactory() method.
application to create Diameter Ro messages as defined in 3GPP:
createCreditControlRequest(), createCreditConrolAnswer(), createReAuthRequest()
and createReAuthAnswer(). An instance of a class implementing this interface can be
obtained by calling the DiameterStack.getRoDiameterMessageFactory() method.
Messages created by this factory are:
■
Credit-Control-Request (CCR)
These methods create a basic CCR (with only mandatory AVPs). The first one
creates the CCR without the Requested-Action AVP (mandatory only in event
sessions). In the others, the method’s name specifies the Requested-Action value:
creates the CCR without the Requested-Action AVP (mandatory only in event
sessions). In the others, the method’s name specifies the Requested-Action value:
■
DiameterMessage
createCreditControlRequest (String destinationRealm,
int authApplicationId,
StringserviceContextId,
String CCRequestType
int CCRequestNumber)
■
DiameterMessage
createCreditControlRequestDirectDebiting(String destinationRealm,
int authApplicationId,
String serviceContextId,
int CCRequestNumber)
■
DiameterMessage
createCreditControlRequestRefundAccount(String destinationRealm,
int authApplicationId,
String serviceContextId,
int CCRequestNumber)
■
DiameterMessage
createCreditControlRequestCheckBalance(String destinationRealm,
int authApplicationId,
String serviceContextId,
int CCRequestNumber)
■
DiameterMessage
createCreditControlRequestPriceEnquiry(String destinationRealm,
int authApplicationId,
String serviceContextId,
int CCRequestNumber)