Oracle Server E10293-02 Benutzerhandbuch

3GPP/Ro DIAMETER JAVA API

Oracle Communication and Mobility Server Developer’s Guide

■

DiameterServiceEvent(Object, DiameterSession, int): This event is generated by 
the Diameter implementation when one service is finished. The different reasons 
to trigger an event for the Rf Interface are:

■

TERMINATE_SERVICE: The event is triggered by the stack when service is 
terminated by the stack or by server.

■

GRANT_SERVICE: The event is triggered by the stack when service is granted 
by server.

■

BACKUP_SERVICE: The event is triggered by the stack when Tx2 timer 
expired and backup server needs to be contacted by the application.

■

ERROR_SERVICE: The event is triggered by the stack when a service error is 
detected by the stack.

■

DiameterInvalidMessageReceivedEvent(Object, DiameterSession, Message): This 
event is triggered by the stack when an invalid message has been received. This 
event object contains the invalid received message.

To send an accounting event to the Diameter stack, user has to call the 

accounting application eventRaised(DiameterEvent) method. The only accounting 
event triggered by the Rf application is DiameterBackupEvent(Object, int) 

The different types of event for an DiameterBackupEvent   are:

■

EVT_NOBACKUP_ACCEPTED: The event can be triggered by the application to 
inform the stack that it doesn’t have any backup server address.

■

EVT_BACKUP_SUCCESS: The event can be triggered by the application to inform 
the stack that it received a successful credit control answer from the backup 
server.

■

EVT_BACKUP_FAILED: The event can be triggered by the application to inform 
the stack that it received a failed credit control answer from the backup server.

These events are relevant only when the stack has sent a BackupService event to the 
application.

These options specify the features handled by the accounting Application. This is a list 
of properties (see java.util.properties) which may contain a number of options. An 
option can be specific to an FSM. Here is the list of the Ro application configurable 
options which can be set depending on the implemented FSM:

FSM admits following options setting

■

AUTO_ANSWER

■

AUTO_DELETION

■

SUPERVISION_TIMER_DURATION

■

DELETE_ON_TIMEOUT

■

ENABLE_INVALID_COMMAND

■

ENABLE_SND_MISSING_AVP

FSM admits following options setting

■

AUTO_DELETION

■

DELETE_ON_TIMEOUT