Specifying the Session Expiration Sending Asynchronous Events

11-8 Oracle WebLogic Server SIP Container Developer’s Guide Using the Diameter Ro Interface API for Online Charging 12-1 12 Using the Diameter Ro Interface API for Online Charging The following chapter describes how to use the Diameter Ro interface API, based on the WebLogic Server Diameter protocol implementation, in your own applications, and contains the following sections: ■ Section 12.1, Overview of Ro Interface Support ■ Section 12.2, Understanding Credit Authorization Models ■ Section 12.3, Configuring the Ro Application ■ Section 12.4, Overview of the Online Charging API ■ Section 12.5, Accessing the Ro Application ■ Section 12.6, Implementing Session-Based Charging ■ Section 12.7, Sending Credit-Control-Request Messages ■ Section 12.8, Handling Failures

12.1 Overview of Ro Interface Support

Online charging, also known as credit-based charging, is used to charge prepaid services. A typical example of a prepaid service is a calling card purchased for voice or video. The Ro protocol allows a Charging Trigger Function CTF to issue charging events to an Online Charging Function OCF. The charging events can be immediate, event-based, or session-based. WebLogic Server provides a Diameter Online Charging Application that deployed applications can use to generate charging events based on the Ro protocol. This enables deployed applications to act as CTF to a configured OCF. The Diameter Online Charging Application uses the base Diameter protocol that underpins both the Rf and Sh applications. The Diameter Online Charging Application is based on IETF RFC 4006: Diameter Credit Control Application http:www.ietf.orgrfcrfc4006.txt . However, the application supports only a subset of the RFC 4006 required for compliance with 3GPP TS 32.299: Telecommunication management; Charging management; Diameter charging applications http:www.3gpp.orgftpSpecshtml-info32299.htm . Specifically, the WebLogic Server Diameter Online Charging Application provides no direct support for service-specific Attribute-Value Pairs AVPs, but the API that is provided is flexible enough to allow applications to include custom service-specific AVPs in any credit control request.