Real Time Correlation of Parallel Charging Events

Abstract

A method is implemented in a network (110) that provides a service to an end user, the network including a first client (115-1), a second client (115-M) and a charging system (130). The method includes the first client (115-1) receiving (900) a service event (120) that is destined for an end user (105) and retrieving (915) a first logical clock value from memory, where the first logical clock value specifies a number of service events received at the second client (115-M). The method further includes the first client (115-1) incrementing (920) a second logical clock value based on receipt of the service event (120) and constructing (920) a first time stamp parameter based on the first logical clock value and the second logical clock value. The method also includes the first client (115-1) sending (925) a charging request to a charging system, where the charging request includes the first time stamp parameter and where the charging request requests credit authorization associated with providing the service event M (120) to the end user (105). The service event may be associated with one of Multimedia messaging service (MMS) data, a Session Initiation Protocol (SIP) signaling message, or a Hypertext Transfer Protocol (HTTP) message received at the first client. In one exemplary embodiment, the first client includes a Gateway General Packet Radio Service (GPRS) Support Node (GGSN) and the second client includes a MultiMedia Messaging Service Center (MMSC). In a second exemplary embodiment, the first client includes a GGSN and the second client comprises a Serving Call Session Control Function (S-CSCF). In a third exemplary embodiment, the first client includes a router and the second client includes a S-CSCF. In a further exemplary embodiment, the first client includes a S-CSCF and the second client includes an Internet Protocol (IP) Multimedia Subsystem Application Server (IMS AS). In another exemplary embodiment, the first client includes a first IMS AS and the second client includes a second IMS AS. In yet another exemplary embodiment, the first client includes a GGSN and the second client includes a Wireless Application Protocol (WAP) portal.

Dependencies are inferred from the claim text.