Oracle Server E10293-02 Benutzerhandbuch

3GPP/Ro DIAMETER JAVA API

Oracle Diameter Java APIs

■

Credit-Control-Answer (CCA)

The first following method creates a basic CCA (with only mandatory AVPs) and 
the second one creates an CCA from an CCR:

■

DiameterMessage

createCreditControlAnswer(String resultCode,

   int authApplicationId,

   String CCRequestType,

   int CCRequestNumber)

■

Diameter Message

createCreditControlAnswer(String resultCode,

   DiameterMessage messageCCR)

■

Re-Auth-Request (RAR)

This method creates a basic RAR (with only mandatory AVPs)

■

Diameter Message

createReAuthRequest(String destinationRealm,

   String destinationHost,

   int authApplicationId,

   String reAuthRequestType)

■

Re-Auth-Answer (RAA)

This method creates a RAA, specifying only the Result-Code AVP.

■

Diameter Message

createReAuthAnswer(String resultCode)

The 3GPP Ro Interface dictionary is returned by getRoDictionary() and must be 
extended by the Diameter stack.

Like any Diameter application, an Ro application can receive/send events from/to the 
Diameter stack.

To receive an accounting event from the Diameter stack, user has to 

implement the processEvent(DiameterEvent) callback in the DiameterRoListener 
implementation.

The list of the possible received accounting events are the following ones:

■

DiameterTimeoutEvent(Object, DiameterSession, int): This event is generated by 
the Diameter implementation when one of the session timers elapses. The different 
reasons to trigger an event for the Ro Interface are:

■

SESSION_TIMEOUT_EXPIRED: The event is triggered by the stack on session 
supervision timer expiration

■

TX_TIMEOUT_EXPIRED: The event is triggered by the stack on session 
supervision timer expiration.

■

TRA_TIMEOUT_EXPIRED: The event is triggered by the stack when the RAA 
is not sent on time by the application.