Flow tagging for service policy implementation

• US 10,326,675 B2
• Filed: 05/03/2017
• Issued: 06/18/2019
• Est. Priority Date: 01/28/2009
• Status: Active Grant

• Current Assignee: Headwater Research LLC (Greg Raleigh)
• Original Assignee: Headwater Research LLC (Greg Raleigh)
• Inventors: Raleigh, Gregory G., Green, Jeffrey, Lavine, James, Nguyen, Vien-Phuong
• Primary Examiner(s): Rudy, Andrew Joseph
• Application Number:
  US15/586,118
• Publication Number:
  US 20170366433A1
• Time in Patent Office: 776 Days
• Field of Search: 370252-254, 4554141, 4554142, 4554321, 4554561, 709203, 709217-224
• CPC Class Codes: H04L 12/1485 Tariff-related aspects
• 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/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/5019 Ensuring fulfilment of SLA
• CPC Class Codes: H04L 41/5029 Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
• CPC Class Codes: H04L 43/062 related to network traffic
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 43/0888 Throughput
• CPC Class Codes: H04L 47/19 at layers above the network layer network arrangements for networked applications for scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04L 47/806 Broadcast or multicast traffic
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04L 65/75 Media network packet handling
• CPC Class Codes: H04L 65/752 adapting media to network capabilities
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]

Abstract

A flow tagging technique includes tagging a data flow at a plurality of points in the data flow. For example, the data flow can be tagged at a socket and at a proxy manager API. By tagging the data flow at multiple points, it becomes possible to map network service usage activities to the appropriate initiating applications.

Claims

1. A method of operating a wireless end-user device, the method comprising:

providing Internet data connectivity via a wireless network;

providing an Application Programming Interface (API), callable by each of a plurality of device applications, the API accepting a network resource identifier for a media object;

configuring the API to, in response to a call by any particular one of the plurality of device applications, the call identifying a particular network resource identifier, invoke a software service, the software service

managing one or more data transfer connections to retrieve data via the wireless network for a particular media object associated with the particular network resource identifier,

receiving user interface control inputs to allow a user to control playback of the particular media object from the data, and

playing the particular media object via a user interface, responsive to the user interface control inputs;

classifying the one or more data transfer connections as associated with the particular one of the device applications calling the API; and

,

responsive to the classifying, attributing wireless network data transfer usage amounts for the one or more data transfer connections to the particular one of the device applications; and

tracking aggregate wireless network data transfer usage amounts for each of the plurality of device applications, such that upon attributing wireless network data transfer usage amounts for the one or more data transfer connections to the particular one of the device applications, an aggregate wireless network data transfer usage amount for the particular one of the device applications is updated to include the wireless data transfer usage amounts for the one or more data transfer connections.

2. The method of claim 1, further comprising enforcing an application-specific usage control, associated with the particular one of the plurality of device applications, on the one or more data transfer connections, based on classifying the one or more data transfer connections as associated with the particular one of the device applications.

3. The method of claim 1, wherein classifying the one or more data transfer connections as associated with the particular one of the device applications calling the API comprises identifying at least one of an application name, an application identifier, or a process identifier for the particular one of the device applications.

4. The method of claim 3, wherein the particular network resource identifier identifies a source of the data to be transferred, a proxy to the source of the data to be transferred, or the media object to be transferred.

5. The method of claim 4, wherein attributing wireless network data transfer usage amounts comprises storing an entry comprising the at least one of the application name, the application identifier, or the process identifier, the stored entry further comprising information about the particular network resource identifier.

6. The method of claim 5, wherein the classifying is performed by the software service.

7. The method of claim 6, wherein the software service is one of a plurality of different media service software services invokable by the API, the method further comprising the API selecting the software service based on a media type of the media object.

8. The method of claim 4, wherein the particular network resource identifier comprises one or more of an Internet Protocol address, a Uniform Resource Locator, a remote file name/address, a stream name, and an object name.

9. The method of claim 4, wherein managing one or more data transfer connections to retrieve data via the wireless network for a particular media object associated with the network resource identifier comprises interfacing with a device networking stack to map the network resource identifier to the one or more data transfer connections, the one or more data transfer connections communicated through the device networking stack.

10. The method of claim 9, wherein managing one or more data transfer connections to retrieve data via the wireless network for a particular media object associated with the network resource identifier further comprises managing, for the one or more data transfer connections, a resulting flow of data between a network accessible through the wireless network and the network stack.

11. The method of claim 10, wherein classifying the one or more data transfer connections as associated with the particular one of the device applications calling the API further comprises monitoring and recording network data flow identifiers for the one or more data transfer connections.

12. The method of claim 11, wherein the network data flow identifiers comprise at least one of a data flow tag, an Internet Protocol address, a Transmission Control Protocol identifier, an application layer identifier, and a socket tuple.

13. The method of claim 1, wherein the API comprises a first API, the method further comprising, for at least a first one of the plurality of device applications, providing a second API that allows the first one of the plurality of device applications to launch a data transfer request and manage network data transfers for the data transfer request through a network stack on the wireless end-user device, independent of the first API.

14. The method of claim 1, wherein receiving user interface control inputs to allow a user to control playback of the particular media object from the data comprises:

returning to the particular one of the plurality of device applications, as a result of the API call, a media object handle descriptor; and

accepting, from the particular one of the plurality of device applications, commands associated with the media object handle descriptor, as the user interface control inputs.

15. The method of claim 1, further comprising:

storing the tracked aggregate wireless network data transfer usage amounts in a local database, the stored data transfer usage amounts classified by device application; and

retrieving from the local database and displaying the stored data transfer usage amounts, classified by application, to a user via the user interface.