Client-based context-based billing for wireless networks

• US 20060141984A1
• Filed: 12/29/2004
• Published: 06/29/2006
• Est. Priority Date: 12/29/2004
• Status: Active Grant

• Current Assignee: United States Cellular Corporation (Telephone & Data Systems, Inc.)
• Original Assignee: United States Cellular Corporation (Telephone & Data Systems, Inc.)
• Inventors: Saxena, Narothum, Irizarry, Michael, Taglienti, Claudio
• Granted Patent: US 7,620,383 B2
• Time in Patent Office: Days
• US Class Current: 455/406
• 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/06 Recording class or number of calling , i.e. A-party or called party , i.e. B-party
• CPC Class Codes: H04M 15/30 the meter or calculation of charges not being controlled from an exchange
• CPC Class Codes: H04M 15/31 Distributed metering or calculation of charges
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/62 based on trigger specification
• CPC Class Codes: H04M 15/82 Criteria or parameters used for performing billing operations
• 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/8221 Message based
• CPC Class Codes: H04M 15/8278 Event based
• CPC Class Codes: H04M 2215/0164 Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/2013 Fixed data network, e.g. PDN, ATM, B-ISDN
• CPC Class Codes: H04M 2215/2026 Wireless network, e.g. GSM, PCS, TACS
• CPC Class Codes: H04M 2215/2033 WLAN
• CPC Class Codes: H04M 2215/206 CDMA, i.e. Code Division Multiple Access
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/78 Metric aspects
• 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/7826 : Message based
• CPC Class Codes: H04M 2215/788 : Event based
• CPC Class Codes: H04M 2215/96 : Distributed calculation of charges, e.g. in different nodes like for mobiles between HLR and VLR, or between the terminal and the billing function
• CPC Class Codes: H04W 4/24 : Accounting or billing

Abstract

The invention increases billing options for a wireless service provider by allowing the provider to make billing decisions based upon what a client or mobile station application does both on and off the network. This type of billing, based on context, generates a billing record of events whether or not a particular client accesses the wireless network or not. The invention also provides transmission quality data allowing the wireless network provider to improve user experience in a wireless network. The invention captures the context, including content, quantity, and/or quality of data processed by a mobile station using a client-based application rather than a network-based application. The client-based application causes the mobile station to transmit a billing record corresponding to the captured context to a user monitoring server. The user monitoring server processes the billing record for determining billing and for generating engineering reports.

Claims

1. A method for generating context-based billing information for a mobile station, the method comprising:

receiving, from an application running on the mobile station, an event trigger;

determining if the event trigger corresponds to a billable event;

generating a billing record based upon the event trigger when it is determined the event trigger corresponds to a billable event, the billing record further including a static subscriber identifier; and

transmitting the billing record from the mobile station to a user monitoring server.

2. A method in accordance with claim 1, further comprising:

determining whether the billing record should be transmitted immediately,

wherein generating the billing record includes accumulating data based upon one or more billable events into a single billing record when it is determined that the billing record should not be transmitted immediately.

3. A method in accordance with claim 1, further comprising:

capturing a content of a data stream transmitted from or received by the mobile station;

determining a type of content of the data stream;

determining if the type of content corresponds to a billable event,

wherein generating the billing record includes adding type data to the billing record when it is determined that the type of content corresponds to a billable event.

4. A method in accordance with claim 1, wherein a billable event is selected from the group consisting of transmitting voice data, receiving voice data, receiving data from the Internet, receiving data from a wireless service provider, initiation of a call, termination of a call, initiation of an application that does not access a wireless network, termination of an application that does not access a wireless network, and a change in level of an application that does not access a wireless network.

5. A method in accordance with claim 1, wherein generating the billing record includes adding a time at which a billable event occurred to the billing record.

6. A method in accordance with claim 1, further comprising:

calculating billing information based upon the billing record; and

displaying, on the mobile station, the billing information.

7. A method in accordance with claim 1, further comprising:

detecting transmission quality of a data stream transmitted from or received by the mobile station,

wherein generating the billing record includes adding the detected transmission quality of the data stream to the billing record.

8. A method in accordance with claim 7, wherein the transmission quality of the data stream is one or more metrics selected from the group consisting of transmission latency, transmission jitter, and transmission errors.

9. A method in accordance with claim 7, further comprising:

determining if the detected transmission quality exceeds a subscriber standard; and

determining if a billing event corresponds to the detected transmission quality,

wherein generating the billing record includes deleting a portion of a billing record corresponding to a billing event when it is determined the detected transmission quality does not exceed the subscriber standard for the billing event.

10. A method in accordance with claim 7, further comprising:

detecting a location of the mobile station,

wherein generating the billing record includes adding the detected location of the mobile station to the billing record.

11. A method for generating a context-based bill for a mobile station subscriber, the method comprising:

receiving, from a billing client running on a mobile station, a billing record, the billing record based upon a billable event, the billing record including a static subscriber identifier;

accumulating one or more billing records for a billing period;

determining if the billing period has elapsed; and

generating, for the mobile station subscriber corresponding to the static subscriber identifier, the context-based bill based upon the accumulated one or more billing records when it is determined that the billing period has elapsed.

12. A method in accordance with claim 11, further comprising:

receiving, from an authorization server, data corresponding to a quantity of data transmitted and received by the mobile station;

comparing the data received from the authorization server with a portion of the billing record corresponding to a quantity of data transmitted and received by the mobile station; and

determining the billing client has been compromised when the data received from the authorization server does not correspond to the portion of the billing record corresponding to a quantity of data transmitted and received by the mobile station.

13. A method in accordance with claim 11, further comprising:

determining a time at which a billable event occurred from the billing record;

wherein generating the context-based bill includes billing the billable event at a first rate when the billable event is determined to have occurred during a first time period and billing the billable event at a second rate when the billable event is determine to have occurred during a second time period, the second time period different from the first time period.

14. A method in accordance with claim 11, further comprising:

determining if a billing record includes detected transmission quality; and

generating a network engineering report when it is determined that the billing record includes detected transmission quality.

15. A method in accordance with claim 14, wherein the detected transmission quality is one or more metrics selected from the group consisting of transmission latency, transmission jitter, and transmission errors.

16. A method in accordance with claim 14, further comprising:

determining if the detected transmission quality exceeds a subscriber standard;

determining if a billing event corresponds to the detected transmission quality,

wherein generating the context-based bill includes deleting a portion of a context-based bill corresponding to a billing event when it is determined the detected transmission quality does not exceed the subscriber standard for the billing event.

17. A method in accordance with claim 14, further comprising:

determining if a billing record includes a location of the mobile station,

wherein generating the network engineering report includes adding the location of the mobile station to the network engineering report.

18. A mobile station for generating context-based billing information, the mobile station comprising:

a transmitter for transmitting a billing record;

a memory for storing computer executable code; and

a processor for processing the computer executable code stored in the memory, the computer executable code including;

computer executable code for receiving, from an application running on the mobile station, an event trigger;

computer executable code for determining if the event trigger corresponds to a billable event;

computer executable code for generating the billing record based upon the event trigger when it is determined the event trigger corresponds to a billable event;

computer executable code for adding to the billing record a static subscriber identifier; and

computer executable code for causing the transmitter to transmit the billing record from the mobile station to a user monitoring server.

19. A mobile station in accordance with claim 18, wherein the computer executable code further includes:

computer executable code for determining whether the billing record should be transmitted immediately,

wherein the computer executable code for generating the billing record includes computer executable code for accumulating data based upon one or more billable events into a single billing record when it is determined that the billing record should not be transmitted immediately.

20. A mobile station in accordance with claim 18, wherein the computer executable code further includes:

computer executable code for capturing a content of a data stream transmitted from or received by the mobile station;

computer executable code for determining a type of content of the data stream;

computer executable code for determining if the type of content corresponds to a billable event,

wherein the computer executable code for generating the billing record includes computer executable code for adding type data to the billing record when it is determined that the type of content corresponds to a billable event.

21. A mobile station in accordance with claim 18, wherein a billable event is selected from the group consisting of transmitting voice data, receiving voice data, receiving data from the Internet, receiving data from a wireless service provider, initiation of a call, termination of a call, initiation of an application that does not access a wireless network, termination of an application that does not access a wireless network, and a change in level of an application that does not access a wireless network.

22. A mobile station in accordance with claim 18, wherein the computer executable code for generating the billing record includes computer executable code for adding a time at which a billable event occurred to the billing record.

23. A mobile station in accordance with claim 18, wherein the computer executable code further includes:

computer executable code for calculating billing information based upon the billing record; and

computer executable code for displaying, on the mobile station, the billing information.

24. A mobile station in accordance with claim 18, wherein the computer executable code further includes:

computer executable code for detecting transmission quality of a data stream transmitted from or received by the mobile station,

wherein the computer executable code for generating the billing record includes computer executable code for adding the detected transmission quality of the data stream to the billing record.

25. A mobile station in accordance with claim 24, wherein the transmission quality of the data stream is one or more metrics selected from the group consisting of transmission latency, transmission jitter, and transmission errors.

26. A mobile station in accordance with claim 24, wherein the computer executable code further includes:

computer executable code for determining if the detected transmission quality exceeds a subscriber standard; and

computer executable code for determining if a billing event corresponds to the detected transmission quality,

wherein the computer executable code for generating the billing record includes computer executable code for deleting a portion of a billing record corresponding to a billing event when it is determined the detected transmission quality does not exceed the subscriber standard for the billing event.

27. A mobile station in accordance with claim 24, further comprising:

location detecting apparatus for detecting a location of the mobile station;

wherein the computer executable code further include;

computer executable code for receiving, from the location detecting apparatus, the detected location of the mobile station, and

wherein the computer executable code for generating the billing record includes computer executable code for adding the detected location of the mobile station to the billing record.

28. A user monitoring server for generating a context-based bill for a mobile station subscriber, the user monitoring server comprising:

a receiver for receiving a billing record;

a memory for storing computer executable code; and

a processor for processing the computer executable code stored in the memory, the computer executable code including;

computer executable code for receiving, from the receiver, a billing record from a billing client running on a mobile station, the billing record based upon a billable event, the billing record including a static subscriber identifier;

computer executable code for accumulating one or more billing records for a billing period;

computer executable code for determining if the billing period has elapsed; and

computer executable code for generating, for the mobile station subscriber corresponding to the static subscriber identifier, the context-based bill based upon the accumulated one or more billing records when it is determined that the billing period has elapsed.

29. A user monitoring server in accordance with claim 28, wherein the computer executable code further includes:

computer executable code for receiving, from the receiver, data from an authorization server, the data corresponding to a quantity of data transmitted and received by the mobile station;

computer executable code for comparing the data from the authorization server with a portion of the billing record corresponding to a quantity of data transmitted and received by the mobile station; and

computer executable code for determining the billing client has been compromised when the data received from the authorization server does not correspond to the portion of the billing record corresponding to a quantity of data transmitted and received by the mobile station.

30. A user monitoring server in accordance with claim 28, wherein the computer executable code further includes:

computer executable code for determining a time at which a billable event occurred from the billing record;

wherein the computer executable code for generating the context-based bill includes computer executable code for billing the billable event at a first rate when the billable event is determined to have occurred during a first time period and computer executable code for billing the billable event at a second rate when the billable event is determine to have occurred during a second time period, the second time period different from the first time period.

31. A user monitoring server in accordance with claim 28, wherein the computer executable code further includes:

computer executable code for determining if a billing record includes detected transmission quality; and

computer executable code for generating a network engineering report when it is determined that the billing record includes detected transmission quality.

32. A user monitoring server in accordance with claim 31, wherein the detected transmission quality is one or more metrics selected from the group consisting of transmission latency, transmission jitter, and transmission errors.

33. A user monitoring server in accordance with claim 31, wherein the computer executable code further includes:

computer executable code for determining if the detected transmission quality exceeds a subscriber standard;

computer executable code for determining if a billing event corresponds to the detected transmission quality,

wherein the computer executable code for generating the context-based bill includes computer executable code for deleting a portion of a context-based bill corresponding to a billing event when it is determined the detected transmission quality does not exceed the subscriber standard for the billing event.

34. A user monitoring server in accordance with claim 31, wherein the computer executable code further includes:

computer executable code for determining if a billing record includes a location of the mobile station,

wherein the computer executable code for generating the network engineering report includes computer executable code for adding the location of the mobile station to the network engineering report.