Oracle Server E10293-02 ユーザーズマニュアル

3GPP/Ro DIAMETER JAVA API

Oracle Diameter Java APIs

■

TX_TIMER_DURATION

■

TRA_TIMER_DURATION

■

CCFH

■

ENABLE_INVALID_COMMAND

■

ENABLE_SND_MISSING_AVP

FSM admits following options setting

■

AUTO_DELETION

■

DDFH

■

TX1_TIMER_DURATION

■

TX2_TIMER_DURATION

■

BACKUP_TIMER_DURATION

■

RETRANSMISSION_INTERVAL

■

RETRANSMISSION_ATTEMPS

■

ENABLE_INVALID_COMMAND

■

ENABLE_SND_MISSING_AVP

As presented in the [RFC 4006], different types of credit control requests are sent 
depending on the actual type of credit control service. If the credit control service is a 
one-time event, meaning that the start and stop of the event are simultaneous, then the 
CC-Request-Type AVP must be set to the value EVENT_REQUEST.

If the credit control service is of a measurable length, then the AVP must use the 
values INITIAL_REQUEST, TERMINATION_REQUEST, and possibly, UPDATE_
REQUEST.

Here are the two different messages flows which can be handled by the Ro Diameter 
application.

One-time event credit control service:

■

Client  > CCR (EVENT_REQUEST) > Server

■

Client < CCA (EVENT_REQUEST) < Server

Measurable length duration accounting service:

■

Client > CCR (INITIAL_REQUEST) > Server

■

Client < CCA (INITIAL_REQUEST) < Server

■

Client > CCR (UPDATE_REQUEST) > Server

■

Client < CCA (UPDATE_REQUEST) < Server

■

Client > CCR (UPDATE_REQUEST) > Server

■

Client < CCA (UPDATE_REQUEST) < Server

■

Client > CCR (TERMINATION_REQUEST) > Server

■

Client < CCA (TERMINATION_REQUEST) < Server

CCR(EVENT_REQUEST) stands for Credit-Control-Request message with 
CC-Request-Type AVP set to EVENT_REQUEST.