Oracle Server E10293-02 User Manual
Diameter Application Example
A-18
Oracle Communication and Mobility Server Developer’s Guide
The network element (acting as client) sends an Accounting-Request (ACR) with
Accounting-Record-Type AVP set to EVENT_RECORD to indicate service specific
information to the CDF (acting as server).
Accounting-Record-Type AVP set to EVENT_RECORD to indicate service specific
information to the CDF (acting as server).
The server processes the received Accounting-Request and returns an
Accounting-Answer (ACA) message with Accounting-Record-Type AVP set to
EVENT_RECORD to the client.
Accounting-Answer (ACA) message with Accounting-Record-Type AVP set to
EVENT_RECORD to the client.
The following section describes all the steps that must be performed to create a Rf
client/server Diameter Application. The steps where the side (client or server) is not
specified are common to both sides.
client/server Diameter Application. The steps where the side (client or server) is not
specified are common to both sides.
Several steps are required to initialize the Diameter stack before messages can be
exchanged. These steps are the following ones:
exchanged. These steps are the following ones:
■
Create a DiameterStack instance
■
Register the Rf Diameter application to the created Diameter stack
■
Create listening points to bind to local transport addresses (optional / server side)
■
Configure routes and connect to Diameter peers (optional / client side)
Application initialization
An instance of the Diameter stack can be created as follows:
Figure A–4
Oracle Diameter Stack Creation
1.
Get an instance of the DiameterFactory class myFactory using the following
method: DiameterFactory.getInstance().
method: DiameterFactory.getInstance().
2.
Create myStack, an instance of the DiameterStack class, using the following
method: myFactory.createDiameterStack().
method: myFactory.createDiameterStack().
Rf Diameter Application
Once the Diameter stack is defined, the current accounting
application objects may be instantiated. An Accounting Diameter application is
represented by instances of the two following interfaces: DiameterRfProvider and
DiameterRfListener. The former represents the Accounting Diameter application for
use by the higher-level user code; the latter represents the Accounting Diameter
application for use by the Diameter stack. The DiameterRfProvider interface is used by
the higher-level user code to send accounting messages (Accounting Request(ACR)
and accounting Answer(ACA)) and control the application behavior. All the call back
methods defined in the DiameterRfListener interface are used by the Diameter stack to
deliver these accounting messages and some events to the user code.
represented by instances of the two following interfaces: DiameterRfProvider and
DiameterRfListener. The former represents the Accounting Diameter application for
use by the higher-level user code; the latter represents the Accounting Diameter
application for use by the Diameter stack. The DiameterRfProvider interface is used by
the higher-level user code to send accounting messages (Accounting Request(ACR)
and accounting Answer(ACA)) and control the application behavior. All the call back
methods defined in the DiameterRfListener interface are used by the Diameter stack to
deliver these accounting messages and some events to the user code.
The Rf provider is created as follows: