Rf accounting Web service call
flows describe how the application transmits and receives accounting packets
and interacts with the application server, the Diameter Enabler base,
and the CCF.
Diameter Enabler base supports
multiple realms. The internal routing table controls which realm a packet
is sent to.
The Rf accounting Web service routing
table is independent from each of the other services (Sh and Ro). Although
all of the Web services use the Diameter Enabler base,
the configuration and usage of the routing table remains independent.
Rf accounting Web service uses
a consistent flow for all Accounting messages:
- An IMS™ Application Server invokes
one of the Rf accounting Web service requests,
such as startRfAccounting.
- The Rf accounting Web service application
validates the parameters received from the Web service interface
and then builds an Rf Accounting Request (ACR) message using those parameters. Diameter Enabler base
then sends the Accounting Request message to the CCF.
- The CCF receives the Accounting Request message, updates the
Charging Data Record, and returns the result to the Diameter Enabler base
in an Accounting Answer (ACA) message.
- The Rf accounting Web service application
receives the Accounting Answer message from the Diameter Enabler base
that contains the result of the Accounting operation. Then the Rf accounting Web service application returns the result to the application that invoked
the Web service request.