Adaptive ambient services

• US 8,527,630 B2
• Filed: 08/23/2012
• Issued: 09/03/2013
• Est. Priority Date: 01/28/2009
• Status: Active Grant

• Current Assignee: Headwater Research LLC (Greg Raleigh)
• Original Assignee: Headwater Partners I LLC (Greg Raleigh)
• Inventors: Rightmyer, Rob, Kudelin, Vladislav, Raleigh, Gregory G
• Primary Examiner(s): RUDY, ANDREW J
• Application Number:
  US13/593,164
• Publication Number:
  US 20120317284A1
• Time in Patent Office: 376 Days
• Field of Search: 455/414.1, 455/414.4, 455/403, 455405-409, 455/456.3, 455/557, 709/203, 709/217, 709/223, 709/224, 370/465, 370/466, 370/485
• US Class Current: 709/224
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 50/10 Services
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5045 Making service definitions prior to deployment
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 47/803 Application aware
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring
• CPC Class Codes: H04W 48/14 : using user query or user detection
• CPC Class Codes: H04W 72/29 : between an access point and the access point controlling device
• CPC Class Codes: H04W 72/53 : based on regulatory allocation policies
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/24 : Transfer of terminal data
• CPC Class Codes: H04W 80/04 : Network layer protocols, e.g. mobile IP [Internet Protocol]

Abstract

A method comprising inspecting a traffic flow associated with a device; identifying a requested access within the traffic flow; determining, based on one or more rules, whether the requested access is within a profile associated with a first service available to the device over a wireless network, the profile identifying a network destination, an application on the device, or a content type, a first usage associated with the service being accounted for separately from a second usage associated with a second service available to the device; and if the requested access is within the profile, creating or modifying a record for assisting in accounting for a measure of the first usage to a sponsor entity responsible for at least subsidizing at least a portion of the first usage, wherein determining whether the requested access is within the profile comprises determining whether the requested access is associated with the service.

Claims

1. A method comprising:

inspecting a traffic flow associated with an end-user device;

identifying a requested access within the traffic flow;

determining, based on a set of one or more access rules, whether the requested access is within a service profile associated with a first service available to the end-user device over a wireless network, the service profile identifying a particular network destination, a particular application on the end-user device, a particular content type, or a combination of these, a first service usage associated with the first service being accounted for separately from a second service usage associated with at least one other service available to the end-user device over the wireless network; and

if the requested access is within the service profile, creating or modifying a record, the record for assisting in accounting for at least a portion of a measure of the first service usage to a sponsor entity responsible for paying for or subsidizing at least a portion of the first service usage, the sponsor entity being an entity other than a user or subscriber associated with the end-user device,

wherein determining, based on the set of one or more access rules, whether the requested access is within the service profile comprises determining whether the requested access is associated with the first service.

2. The method of claim 1, further comprising:

applying one or more control rules to the requested access.

3. The method of claim 2, wherein the one or more control rules are configured to modify a transmission speed or limit a total amount of data transmitted.

4. The method of claim 2, wherein the one or more control rules are configured to provide a differentiated bandwidth or a differentiated data transfer limit to the requested access based on whether the requested access is a particular activity.

5. The method of claim 2, wherein the one or more control rules are based on a period of time, a network address, a service type, a content type, an application type, a quality-of-service (QoS) class, a time of day, a network busy state, a transmission speed, a bandwidth, a data usage, a rate of service usage, a policy limit, a number of transactions, or a user activity.

6. The method of claim 1, wherein determining whether the requested access is associated with the first service comprises determining whether the requested access is within a particular traffic flow, the particular traffic flow being associated with the first service.

7. The method of claim 1, wherein determining whether the requested access is associated with the first service comprises identifying a referred uniform resource locator (URL), a hyperlink reference (HREF), or a hypertext markup language (HTML) tag based on the requested access.

8. The method of claim 1, wherein determining whether the requested access is associated with the first service comprises performing a reverse lookup based on the requested access.

9. The method of claim 1, wherein determining whether the requested access is associated with the first service comprises monitoring:

a total traffic, the particular application on the end-user device, a source, the particular network destination, a network socket, a time of day, a service profile categorization, a web browsing traffic pattern, a content download pattern, or a combination of these.

10. The method of claim 1, wherein determining whether the requested access is associated with the first service comprises determining whether the requested access is associated with an in-progress Internet protocol (IP) session or socket that is associated with the first service.

11. The method of claim 1, wherein the service profile identifies the particular application on the end-user device, and wherein determining whether the requested access is associated with the first service comprises determining whether the requested access is associated with the particular application on the end-user device.

12. The method of claim 1, wherein the service profile identifies the particular network destination, and wherein determining whether the requested access is associated with the first service comprises determining whether the requested access is associated with a referral from the particular network destination.

13. The method of claim 1, wherein determining whether the requested access is associated with the first service comprises determining whether the requested access is associated with a traffic usage pattern.

14. The method of claim 1, further comprising receiving side information from the end-user device, and wherein determining whether the requested access is associated with the first service comprises examining the side information.

15. The method of claim 14, wherein the side information comprises embedded information or information identifying a link or tunnel associated with the first service.

16. The method of claim 1, further comprising obtaining a header or field included in the traffic flow.

17. The method of claim 14, wherein the side information is received from the end-user device over a control channel or a secure network connection.

18. The method of claim 1, wherein the record is a record, and further comprising:

if the requested access is not within the service profile, creating or modifying a second record.

19. The method of claim 18, wherein the second record is configured to account for at least a portion of traffic that is not associated with the first service.

20. The method of claim 18, further comprising performing a pro-rata allocation, based on information in the second record, to a plurality of entities, each of the plurality of entities responsible for paying for or subsidizing at least a portion of an end-user device service usage.

21. The method of claim 18, wherein the sponsor entity is a first sponsor entity, and wherein the second record assists in providing an accounting, to the user or subscriber or to a second sponsor entity, of at least a portion of a measure of the second service usage.

22. The method of claim 18, wherein the second record is configured to account for traffic that is likely to be associated with an ambient service, a user-paid service, or network overhead.

23. The method of claim 18, wherein the second record is configured to account for traffic that is not identified as being associated with an allowed service.

24. The method of claim 19, further comprising:

monitoring an amount of traffic accounted for in the second record; and

when the amount of traffic accounted for in the second record exceeds a limit, modifying one or more rules that allow, restrict, or control traffic accounted for in the second record.

25. The method of claim 19, further comprising:

monitoring a growth of traffic accounted for in the second record; and

when the growth of traffic accounted for in the second record exceeds a limit, modifying one or more rules that allow, restrict, or control traffic accounted for in the second record.

26. The method of claim 24, wherein the amount of traffic is measured as an amount of service usage charges.

27. The method of claim 25, wherein the rate of growth of traffic is measured as a rate of service usage.

28. The method of claim 1, wherein the side information comprises information about the first service usage, information about the record, information about the measure of the first service usage, or a combination of these.

29. The method of claim 1, wherein at least a portion of the method is performed by a network element communicatively coupled to the end-user device over the wireless network.

30. The method of claim 1, wherein at least a portion of the method is performed by the end-user device.