Event based charging in a communications system

• US 7,721,296 B2
• Filed: 06/13/2003
• Issued: 05/18/2010
• Est. Priority Date: 06/13/2003
• Status: Active Grant

• Current Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Inventors: Ricagni, Giuseppe
• Primary Examiner(s): Ho; Andy
• Application Number:
  US10/461,855
• Publication Number:
  US 20040255025A1
• Time in Patent Office: 2,531 Days
• Field of Search: 719/318, 719/313, 705/52
• US Class Current: 719/318
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/06 Recording class or number of calling , i.e. A-party or called party , i.e. B-party
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/7655 shared by technologies
• CPC Class Codes: H04M 15/77 involving multiple accounts per user
• CPC Class Codes: H04M 15/772 per service, e.g. prepay or post-pay
• CPC Class Codes: H04M 15/8207 Time based data metric aspects, e.g. VoIP or circuit switched packet data
• CPC Class Codes: H04M 15/8214 Data or packet based
• CPC Class Codes: H04M 15/8278 Event based
• CPC Class Codes: H04M 15/90 using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
• CPC Class Codes: H04M 2215/016 Billing using Intelligent Networks [IN] or Advanced Intelligent Networks [AIN]
• CPC Class Codes: H04M 2215/202 VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/204 UMTS; GPRS
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/725 Shared by technologies, e.g. one account for different access technologies
• CPC Class Codes: H04M 2215/7254 Multiple accounts per user
• CPC Class Codes: H04M 2215/7263 per service, e.g. prepay and post-pay
• CPC Class Codes: H04M 2215/7813 : Time based data, e.g. VoIP or circuit switched packet data
• CPC Class Codes: H04M 2215/782 : Data or packet based
• CPC Class Codes: H04M 2215/788 : Event based

Abstract

A communications system in which event based charging is implemented and in which service flows between end user equipments and application servers are filtered for charging purposes by a traffic plane function (TPF). The TPF identifies a service flow between an end user equipment and an application server and implements event based charging by sending a message to an Event Owner for the service flow requesting notification of Events associated with the service flow. The Event Owner sends a message containing an Event Result to the TPF when an Event associated with the service flow occurs and the TPF correlates the Event Result with the service flow. This correlation may include the matching of the Event Result to the service flow which the TPF then notifies to a billing control function so that the billing control function can bill the end user appropriately based on the Events. This correlation may also include the matching of the Event Result to a data download detected by the TPF on the service flow so that the system operator can confirm that the service flows filtered by the TPF match the Events notified to the TPF by the Event Owner.

Claims

1. A communications system comprising a network subsystem, wherein the communications system is configured to implement event based charging, and the communications system is to filter service flows between end user equipments and application servers for charging purposes, wherein the network subsystem is configured to:

identify an instance of service flow between an end user equipment and a particular application server,

send a first message containing information identifying a set of events to report, and

receive a second message containing an event result responsive to occurrence of an event of the particular application server that is one of the set of events and that is associated with the instance of service flow, which event result is correlated with the instance of service flow, the event result containing information about occurrence of the event.

2. A communications system according to claim 1 wherein the network subsystem comprises at least a traffic plane function (TPF) to perform the identifying, the sending, and the receiving, and wherein the TPF is configured to correlate the event result with the instance of service flow.

3. A communications system according to claim 2, further comprising a billing system, wherein the TPF is configured to provide notification of the event result and the instance of service flow to a billing system and the billing system is configured to implement at least one of debiting, crediting and discounting to the user of the end user equipment based on the event result.

4. A communications system according to claim 1 wherein to identify the instance of the service flow the network subsystem matches characteristics of the service flow to triggering criteria and applies associated triggering actions to the service flow.

5. A communications system according to claim 1 wherein to identify the instance of the service flow the network subsystem is configured to match characteristics of the service flow to triggering criteria and to apply associated triggering actions to the service flow, including at least one of the following:

instructions on how to filter a service flow matched to the triggering criteria;

instructions on how to identify the instance of service flow among those matched to the triggering criteria;

instructions on how to dynamically filter the instance of service flow;

identification of an event owner for the service flow that matched the triggering criteria;

indication of whether a time stamp should be recorded;

identification of a set of events to be reported by the event owner;

maximum number of events to be reported for the instance of service flow; and

maximum number of events allowed for the instance of service flow.

6. A communications system according to claim 1 in which the network subsystem is configured to allocate a unique identifier to the instance of service flow, and the communications system additionally includes a billing system configured to cooperate with the network subsystem to implement at least one of pre-paid and post-paid billing in which the billing system correlates the event result with the instance of service flow by using the unique identifier.

7. A communications system according to claim 1 additionally including a billing system, wherein the billing system, in response to the occurrence of the event, is configured to retrospectively amend charges incurred for the instance of service flow before that event occurred.

8. A communications system according to claim 1 wherein the network subsystem is configured to correlate the event result with the instance of service flow by matching the event result to the instance of service flow and notifying a billing system of the match.

9. A communications system according to claim 1 wherein the event result is correlated with the instance of service flow by matching the event result to an event detected by the network subsystem on the instance of service flow.

10. A communications system according to claim 1 wherein the occurred event is one of the following:

a purchase of goods or services from the particular application server;

a download of data from the particular application server;

access to a specific page on the particular application server;

access to a particular videoclip streaming service on the particular application server;

completion of a videoclip streaming from the particular application server;

or

a predetermined situation of usage of an application on the particular application server.

11. The communications system of claim 10, wherein the predetermined situation of usage of the application in the particular application server comprises an end user reaching a given score in a gaming application.

12. A communications system according to claim 1 wherein the network subsystem includes a gateway GPRS support node (GGSN).

13. The communications system of claim 1, wherein the network subsystem is to further send a request to a network entity to request notification of information associated with the instance of service flow, the information to enable billing for the instance of service flow.

14. A communications system according to claim 13 wherein the network entity is a server operated by an operator of the application server.

15. A communications system according to claim 13 wherein the network subsystem is configured to allocate a unique identifier to the instance of service flow and to include the unique identifier in the request to the network entity.

16. A communications system according to claim 15 wherein the network entity includes the identifier with the event result in the message received by the network subsystem.

17. A communications system according to claim 13 wherein the network subsystem is configured to include at least one of the following in the request to the network entity:

a unique identifier allocated for the instance of service flow;

a set of flow characteristics for end user and session identification;

a timestamp;

a maximum number of events to be reported;

a maximum number of events allowed for the instance of service flow; and

an address of a device to which event results are to be sent.

18. A communications system according to claim 13 additionally including a billing system, wherein the network subsystem is configured to allocate a unique identifier to the instance of service flow and to notify the unique identifier to the network entity, wherein the unique identifier is included by the network entity in the event result and the second message is sent to the billing system, and the network subsystem is configured to send results of filtering of the instance of service flow to the billing system identifying the instance of service flow by the unique identifier, and wherein the billing system is configured to correlate the filtering results and the event result based on the unique identifier.

19. A network subsystem for implementing event based charging in a communications system by filtering service flows between end user equipments and application servers, the network subsystem having a computer-readable storage medium encoded with software that when executed cause the network subsystem to:

identify an instance of service flow between an end user equipment and a particular application server;

send a first message containing information identifying a set of events to report, and

receive a second message responsive to occurrence of an event that is one of the set of events at the particular application server for the instance of service flow, the second message containing an event result that is correlated with the instance of service flow, and the event result containing information about occurrence of the event.

20. A network subsystem according to claim 19 wherein the first message is to be sent to an event owner for the instance of service flow and further requests information associated with the instance of service flow to enable billing for the instance of service flow.

21. A network subsystem according to claim 20 which includes at least one of the following in the first message to the event owner:

a unique identifier allocated by the network subsystem for the instance of service flow;

a set of flow characteristics for end user and session identification;

a timestamp, as recorded by the network subsystem;

a maximum number of events to be reported;

a maximum number of events allowed for the instance of service flow; and

an address of a device to which the event owner should send event reports, if different from the network subsystem.

22. A network subsystem according to claim 20 which is configured to allocate a unique identifier to the instance of service flow and to include the identifier in the first message to the event owner.

23. A network subsystem according to claim 19 wherein to identify the instance of the service flow the network subsystem is configured to match characteristics of the service flow to triggering criteria and to apply associated triggering actions to the service flow.

24. A network subsystem according to claim 19 wherein to identify the instance of the service flow the network subsystem is configured to match characteristics of the service flow to triggering criteria and to apply associated triggering actions to the service flow, including at least one of the following:

instructions on how to filter the service flow matched to the triggering criteria;

instructions on how to identify the instance of service flow among those matched to the triggering criteria;

instructions on how to dynamically filter the instance of service flow;

identification of an event owner for the service flow that matched the triggering criteria;

identification of a set of service flow characteristics to be sent to the event owner for end user and session identification;

indication of whether a time stamp should be recorded;

identification of a set of events to be reported by the event owner;

maximum number of events to be reported for the instance of service flow; and

maximum number of events allowed for the instance of service flow.

25. A network subsystem according to claim 19, wherein the software when executed causes the network subsystem to correlate the event result with the instance of service flow by matching the event result to the instance of service flow and notifying a billing system of the match.

26. A network subsystem according to claim 19, wherein the software when executed causes the network subsystem to correlate the event result with the instance of service flow by matching the event result to an event detected by the network subsystem on the instance of service flow.

27. A network subsystem according to claim 19 which includes a gateway GPRS support node.

28. The network subsystem of claim 19, wherein the network subsystem comprises at least one traffic plane function.

29. A computer server associated with an event owner of an application server for which event based charging is implemented for service flows between end user equipments and the application server by a network subsystem filtering the service flows for charging purposes, wherein the computer server associated with the event owner is configured to:

receive a first message from the network subsystem requesting notification of a set of events associated with an instance of service flow, and

in response to occurrence of an event that is one of the set of events at the application server, send a message to the network subsystem containing an event result containing information about the occurrence of the event.

30. A computer server associated with the event owner according to claim 29 wherein the occurred event is one of the following:

a purchase of goods or services from the application server;

a download of data from the application server;

access to a specific page on the application server;

access to a particular videoclip streaming service on the application server;

completion of a videoclip streaming from the application server;

or

a predetermined situation of usage of an application on the application server.

31. A computer server associated with the event owner according to claim 29 wherein the first message received from the network subsystem further contains at least one of the following:

a unique identifier of the instance of service flow allocated by the network subsystem;

a set of flow characteristics for end user and session identification;

a timestamp, as recorded by the network subsystem;

a maximum number of events to be reported;

a maximum number of events allowed for the instance of service flow; and

an address of the device to which the event owner should send event results.

32. A method of event based charging in a communications system wherein service flows between end user equipments and application servers are filtered for charging purposes, the method comprising:

a network subsystem identifying an instance of service flow between an end user equipment and a particular application server;

the network subsystem sending a first message containing information identifying a set of events to report;

the network subsystem receiving a second message containing an event result responsive to occurrence of an event of the particular application server that is one of the set of events and that is associated with the instance of service flow, wherein the event result contains information regarding occurrence of the event.

33. A method according to claim 32 wherein the network subsystem identifying the instance of the service flow includes the network subsystem matching characteristics of the service flow to triggering criteria and applying associated triggering actions to the service flow.

34. A method according to claim 32 wherein the network subsystem identifying the instance of service flow includes the network subsystem matching characteristics of the service flow to triggering criteria and applying the associated triggering actions to the service flow, including at least one of the following:

instructions on how to filter the service flow matched to the triggering criteria;

instructions on how to identify the instance of service flow among those matched to the triggering criteria;

instructions on how to dynamically filter the instance of service flow.

35. A method according to claim 32 wherein an event owner performs generating the event result which contains information enabling an operator of the communications system to confirm by filtering of the instance of service flow that the event has taken place.

36. A method according to claim 32, further comprising the network subsystem correlating the event result with the instance of service flow by matching the event result to the instance of service flow and notifying a billing system of the match.

37. A method according to claim 32, further comprising correlating the event result with the instance of service flow by matching the event result to an event detected by the network subsystem on the instance of service flow.

38. A method according to claim 32 wherein the occurred event is one of the following:

a purchase of goods or services from the particular application server;

a download of data from the particular application server;

access to a specific page on the particular application server;

access to a particular videoclip streaming service on the particular application server;

completion of a videoclip streaming from the particular application server;

or

a predetermined situation of usage of an application on the particular application server.

39. The method of claim 32, further comprising:

the network subsystem sending a request to a network entity to request notification of information associated with the instance of service flow.