System and method for generating a report to a network operator by distributing aggregation of data

• US 10,098,036 B2
• Filed: 11/18/2014
• Issued: 10/09/2018
• Est. Priority Date: 12/14/2011
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Backholm, Ari, Bott, Ross, Luna, Michael
• Primary Examiner(s): SERRAO, RANODHI N
• Application Number:
  US14/546,053
• Publication Number:
  US 20150074270A1
• Time in Patent Office: 1,421 Days
• CPC Class Codes: H04L 41/0823 characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for optimising operational conditions of wireless networks H04W24/02
• CPC Class Codes: H04L 41/083 for increasing network speed
• CPC Class Codes: H04L 43/062 related to network traffic
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 28/06 Optimizing the usage of the radio link, e.g. header compression, information sizing , discarding information system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365
• CPC Class Codes: H04W 52/0258 controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A method and system are for generating a report for delivery to or access or query by a network operator by determining, by a server-side proxy, optimization efficiency for traffic in a wireless network, tracking, by the server-side proxy, user-related information in the wireless network, generating, based on at least one of the optimization efficiency and the user-related information, a report for delivery to or access by an operator of the wireless network, the report including an alert of viral take-up of a new application, and performing, by the server-side proxy, traffic optimization functions alleviating traffic in the wireless network.

Claims

1. A method comprising:

capturing, on a mobile device, metadata related to activities on the mobile device, wherein the metadata indicates a type of activities of an application on the mobile device;

storing, on a local cache of the mobile device, the captured metadata;

intercepting, at the mobile device subsequently to storing the captured metadata, a data request initiated on the mobile device by the application;

transferring, by the mobile device, the stored captured metadata and the data request to a remote entity, wherein the captured metadata includes request timing history;

intercepting, at the mobile device, additional data requests initiated on the mobile device by the application or other applications;

satisfying at least some of the additional data requests using content stored on the local cache; and

capturing data requests on the mobile device, and delaying transfer of the data requests.

2. The method of claim 1, wherein the metadata is used to generate rules for satisfying requests of applications on the mobile device.

3. The method of claim 1, wherein the metadata is associated with an application profile.

4. The method of claim 1, wherein the metadata is related to application request or response characteristics.

5. The method of claim 4, wherein the request or response characteristics includes timing patterns, timing repeatability, and content repeatability.

6. The method of claim 1, wherein the request timing history includes for each of a plurality of data requests received at the mobile device, at least one of request time, request start time, request end time.

7. The method of claim 1, wherein traffic from the mobile device is optimized based on the metadata.

8. The method of claim 1, further including generating a report based on the captured metadata.

9. The method of claim 8, wherein the report is further generated based on statistics from the group of user statistics, data statistics, signaling statistics, application statistics, and device statistics.

10. The method of claim 8, wherein the report is further generated based on applications executing on the mobile device, type of mobile device, bearer type, host, operation, and protocols.

11. The method of claim 8, wherein the report is based on a transaction-by-transaction level.

12. The method of claim 8, wherein the report is based on aggregated transactions.

13. The method of claim 1, wherein the captured metadata includes application usage history.

14. A mobile device comprising:

a memory;

a radio; and

a processor configured to;

capture metadata related to activities on the mobile device, wherein the metadata indicates a type of activities of an application on the mobile device;

store, in the memory, the captured metadata;

intercept a data request initiated on the mobile device by the application;

transfer the captured metadata and the received data request to a remote entity, wherein the captured metadata includes request timing history;

intercept, at the mobile device, additional data requests initiated on the mobile device by the application or other applications; and

satisfy at least some of the additional data requests using content stored on the local cache, wherein the processor is further configured to capture data requests on the mobile device, and delay transfer of the data requests.

15. The mobile device of claim 14, wherein the metadata is used to generate rules for satisfying requests of applications on the mobile device.

16. The mobile device of claim 14, wherein the metadata is associated with an application profile.

17. The mobile device of claim 14, wherein the metadata is related to application request or response characteristics.

18. The mobile device of claim 14, wherein the request timing history includes for each of a plurality of data requests received at the mobile device, at least one of request time, request start time, request end time.

19. The mobile device of claim 14, wherein the captured metadata includes application usage history.

20. A method comprising:

capturing metadata related to activities on the mobile device, wherein the metadata indicates a type of activities of an application on the mobile device;

storing, on a local cache of the mobile device, the captured metadata;

intercepting, at the mobile device subsequently to storing the captured metadata, a data request initiated on the mobile device by the application; and

transferring, by the mobile device, the stored captured metadata and the data request to a remote entity, wherein the captured metadata includes request timing history;

intercepting, at the mobile device, additional data requests initiated on the mobile device by the application or other applications; and

satisfying at least some of the additional data requests using content stored on the local cache, wherein traffic from the mobile device is optimized based on the metadata.

21. The method of claim 20, wherein the captured metadata includes application usage history.

22. A method comprising:

capturing, on a mobile device, metadata related to activities on the mobile device, wherein the metadata indicates a type of activities of an application on the mobile device;

storing, on a local cache of the mobile device, the captured metadata;

intercepting, at the mobile device subsequently to storing the captured metadata, a data request initiated on the mobile device by the application;

transferring, by the mobile device, the stored captured metadata and the data request to a remote entity, wherein the captured metadata includes request timing history;

intercepting, at the mobile device, additional data requests initiated on the mobile device by the application or other applications;

satisfying at least some of the additional data requests using content stored on the local cache; and

generating a report based on the captured metadata.

23. The method of claim 22, wherein the captured metadata includes application usage history.