Oracle Server E10293-02 ユーザーズマニュアル
3GPP/Rf Diameter Java API
A-8
Oracle Communication and Mobility Server Developer’s Guide
■
SUPERVISION_TIMER_DURATION
■
INTERIM_INTERVAL
■
REALTIME_REQUIRED
The default value of the INTERIM_INTERVAL and REALTIME_REQUIRED options
can be overwritten dynamically by the application for a specific session by using the
setSessionParameter() method.
can be overwritten dynamically by the application for a specific session by using the
setSessionParameter() method.
Rf Application FSM
As presented in the [RFC 3588], different types of accounting records are sent
depending on the actual type of accounted service.
depending on the actual type of accounted service.
If the accounted service is a one-time event, meaning that the start and stop of the
event are simultaneous, then the Accounting-Record-Type AVP must be set to the
value EVENT_RECORD.
event are simultaneous, then the Accounting-Record-Type AVP must be set to the
value EVENT_RECORD.
If the accounted service is of a measurable length, then the AVP must use the values
START_RECORD, STOP_RECORD, and possibly, INTERIM_RECORD.
START_RECORD, STOP_RECORD, and possibly, INTERIM_RECORD.
Here are the two different messages flows which can be handled by the Rf Diameter
application.
application.
One-time event accounting service:
■
Client > ACR (EVENT_RECORD) > Server
■
Client < ACA (EVENT_RECORD) < Server
Measurable length duration accounting service:
■
Client > ACR (START_RECORD) > Server
■
Client < ACA (START_RECORD) < Server
■
Client > ACR (INTERIM_RECORD) > Server
■
Client < ACA (INTERIM_RECORD) < Server
■
Client > ACR (INTERIM_RECORD) > Server
■
Client < ACA (INTERIM_RECORD) < Server
■
Client > ACR (STOP_RECORD) > Server
■
Client < ACA (STOP_RECORD) < Server
ACR(EVENT_RECORD) stands for Accounting-Request message with
Accounting-Record-Type AVP set to EVENT_RECORD and request flag set to true.
Accounting-Record-Type AVP set to EVENT_RECORD and request flag set to true.
ACA(EVENT_RECORD) stands for Accounting-Answer message with
Accounting-Record-Type AVP set to EVENT_RECORD and request flag set to false.
Accounting-Record-Type AVP set to EVENT_RECORD and request flag set to false.
Below are the different types of FSM which can be implemented in Rf application.
Rf Client FSM
This FSM responds to the [RFC 3588] requirements which define the
client side state machine.
A session instantiated by an application implementing this FSM expects to receive an
accounting request message including an Accounting-Record-Type AVP value set to
EVENT_RECORD or START_RECORD as first received message.
accounting request message including an Accounting-Record-Type AVP value set to
EVENT_RECORD or START_RECORD as first received message.
Once an accounting request message with the Accounting-Record-Type AVP value set
to START_RECORD is received, the FSM expects to receive other(s) accounting
request message(s) with the Accounting-Record-Type AVP value set to INTERIM_
to START_RECORD is received, the FSM expects to receive other(s) accounting
request message(s) with the Accounting-Record-Type AVP value set to INTERIM_