Adaptive Traffic Management in Cellular Wireless Networks

• US 20130263167A1
• Filed: 03/30/2012
• Published: 10/03/2013
• Est. Priority Date: 03/30/2012
• Status: Abandoned Application

• Current Assignee: OptiMorphix, Inc.
• Original Assignee: Bytemobile Inc. (Cloud Software Group)
• Inventors: Parthasarathy, Kannan, Stavrakos, Nicholas James
• Application Number:
  US13/436,658
• Publication Number:
  US 20130263167A1
• Time in Patent Office: Days
• US Class Current: 725/14
• CPC Class Codes: H04L 41/5067 Customer-centric QoS measurements
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04M 15/66 Policy and charging system
• CPC Class Codes: H04N 21/6131 involving transmission via a mobile phone network wireless downlink channel access H04W74/006
• CPC Class Codes: H04N 21/64322 IP
• CPC Class Codes: H04N 21/64707 for transferring content from a first network to a second network, e.g. between IP and wireless
• CPC Class Codes: H04N 21/64738 Monitoring network characteristics, e.g. bandwidth, congestion level data switched network analysis H04L41/14; monitoring functioning in data switched networks H04L43/0817; flow control in packet networks H04L47/10
• CPC Class Codes: H04N 21/64792 Controlling the complexity of the content stream, e.g. by dropping packets intermediate media network packet handling H04L65/765; proxy provisioning conversion or adaptation for reducing the amount or size of exchanged application data H04L67/5651; negotiation of resources in wireless networks H04W28/16
• CPC Class Codes: H04W 16/18 Network planning tools

Abstract

A method including determining whether historical content data is available for a time period; acquiring historical content data associated with a web content source if the historical content data is available; determining one or more user experience metrics for a specific terminal based on the acquired historical content data; and acquiring an expected quality of experience score based at least in part on the determined one or more user experience metrics, wherein the expected quality of experience score can be used for providing one or more traffic management optimization rules for current content data to the specific terminal.

Claims

1. A method comprising:

determining whether historical content data is available for a time period;

acquiring historical content data associated with a web content source if the historical content data is available;

determining one or more user experience metrics for a specific terminal based on the acquired historical content data; and

acquiring an expected quality of experience score based at least in part on the determined one or more user experience metrics, wherein the expected quality of experience score can be used for providing one or more traffic management optimization rules for current content data to the specific terminal.

2. The method of claim 1, wherein the determining whether historical content data is available for a time period comprises:

determining whether the historical content data is available for a first time period; and

if the historical content data is not available for the first time period, determining whether the historical content data is available for a second time period, wherein the second time period is greater than the first time period.

3. The method of claim 2, wherein the determining one or more user experience metrics comprises:

acquiring one or more cell level user experience metrics for at least one past time period, if the historical content data is not available for the second time period.

4. The method of claim 1, wherein the historical content data is historical video data.

5. The method of claim 4, wherein the determining one or more user experience metrics comprises:

measuring a play time of the acquired video data;

measuring a stalling time of the acquired video data; and

computing a video playback smoothness index of the acquired video data based on the measured play time and the measured stalling time.

6. The method of claim 4, wherein the determining one or more user experience metrics further comprises:

measuring a play time of the acquired video data;

measuring a delay time of the acquired video data; and

computing a video client network delay index of the acquired video data based on the measured delay time and the measured play time.

7. The method of claim 1, wherein the historical content data is historical web data.

8. The method of claim 7, wherein the determining one or more user experience metrics comprises:

determining a normalized page unit time according to one or more measurement corresponding to time for rendering a pre-defined number of objects based on acquired historical web data.

9. The method of claim 1, wherein the acquiring the expected quality of experience score comprises:

quantizing the one or more user experience metrics; and

determining the expected quality of experience score of the acquired historical content data based on an established lookup table, wherein the established lookup table includes a pre-determined quality of experience score corresponding to the quantized one or more user experience metrics for at least one time period.

10. The method of claim 1, wherein the providing one or more traffic management optimization rules for current content data to the specific terminal is further according to network probes, remote authentication dial-in user service, policy charging and rules function, subscriber profile repository, application types, and network performance metrics including packet round trip time, packet retransmission rate, and bandwidth.

11. A non-transitory computer readable storage medium storing instruction that, when executed by a computer, cause the computer to perform a method for processing historical content data, the method comprising:

determining whether historical content data is available for a time period;

acquiring historical content data associated with a web content source if the historical content data is available;

determining one or more user experience metrics for a specific terminal based on the acquired historical content data; and

acquiring an expected quality of experience score based at least in part on the determined one or more user experience metrics, wherein the expected quality of experience score can be used for providing one or more traffic management optimization rules for current content data to the specific terminal.

12. The computer readable storage medium of claim 11, wherein the determining whether historical content data is available for a time period comprises:

determining whether the historical content data is available for a first time period; and

if the historical content data is not available for the first time period, determining whether the historical content data is available for a second time period, wherein the second time period is greater than the first time period.

13. The computer readable storage medium of claim 12, wherein the determining one or more user experience metrics comprises:

acquiring one or more cell level user experience metrics for at least one past time period, if the historical content data is not available for the second time period.

14. The computer readable storage medium of claim 11, wherein the historical content data is historical video data.

15. The computer readable storage medium of claim 14, wherein the determining one or more user experience metrics comprises:

measuring a play time of the acquired video data;

measuring a stalling time of the acquired video data; and

computing a video playback smoothness index of the acquired video data based on the measured play time and the measured stalling time.

16. The computer readable storage medium of claim 14, wherein the determining one or more user experience metrics further comprises:

measuring a play time of the acquired video data;

measuring a delay time of the acquired video data; and

computing a video client network delay index of the acquired video data based on the measured delay time and the measured play time.

17. The computer readable storage medium of claim 11, wherein the historical content data is historical web data.

18. The computer readable storage medium of claim 17, wherein the determining one or more user experience metrics comprises:

determining a normalized page unit time according to one or more measurement corresponding to time for rendering a pre-defined number of objects based on acquired historical web data.

19. The computer readable storage medium of claim 11, wherein the acquiring the expected quality of experience score comprises:

quantizing the one or more user experience metrics; and

determining the expected quality of experience score of the acquired historical content data based on an established lookup table, wherein the established lookup table includes a pre-determined quality of experience score corresponding to the quantized one or more user experience metrics for at least one time period.

20. The computer readable storage medium of claim 11, wherein the providing one or more traffic management optimization rules for current content data to the specific terminal is further according to network performance metrics, network probes, remote authentication dial-in user service, policy charging and rules function, subscriber profile repository, and application types, and network performance metrics including packet round trip time, packet retransmission rate, and bandwidth.

21. An apparatus for adaptive traffic management, comprising:

a traffic processor configured to determine whether historical content data is available for a time period and to acquire historical content data associated with a web content source if the historical content data is available;

a user experience monitor configured to determine one or more user experience metrics for a specific terminal based on the acquired historical content data; and

a predictor configured to acquire an expected quality of experience score based at least in part on the determined one or more user experience metrics, wherein the expected quality of experience score can be used for providing one or more traffic management optimization rules for current content data to the specific terminal.

22. The apparatus of claim 21, wherein the traffic processor is configured to determine whether historical content data is available by determining whether the historical content data is available for a first time period, and if the historical content data is not available for the first time period, determining whether the historical content data is available for a second time period, wherein the second time period is greater than the first time period.

23. The apparatus of claim 22, wherein the user experience monitor is configured to determine one or more user experience metrics after acquiring one or more cell level user experience metrics for at least one past time period, if the historical content data is not available for the second time period.

24. The apparatus of claim 21, wherein the historical content data is historical video data.

25. The apparatus of claim 24, wherein the traffic monitor is configured to determine one or more user experience metrics by measuring a play time of the acquired video data, measuring a stalling time of the acquired video data, and computing a video playback smoothness index of the acquired video data based on the measured play time and the measured stalling time.

26. The apparatus of claim 24, wherein the traffic monitor is configured to determine one or more user experience metrics further by measuring a play time of the acquired video data, measuring a delay time of the acquired video data, and computing a video client network delay index of the acquired video data based on the measured delay time and the measured play time.

27. The apparatus of claim 21, wherein the historical content data is historical web data.

28. The apparatus of claim 27, wherein the traffic monitor is configured to determine one or more user experience metrics by determining a normalized page unit time according to one or more measurements corresponding to time for rendering a pre-defined number of objects based on acquired historical web data.

29. The apparatus of claim 21, wherein the predictor is configured to acquire the expected quality of experience score by quantizing the one or more user experience metrics, and determining the expected quality of experience score of the acquired historical content data based on an established lookup table, wherein the established lookup table includes a predetermined quality of experience score corresponding to the quantized one or more user experience metrics for at least one time period.

30. The apparatus of claim 21, wherein the provided one or more traffic management optimization rules for current content data to the specific terminal is based at least in part on network probes, remote authentication dial-in user service, policy charging and rules function, subscriber profile repository, application types, and network performance metrics including packet round trip time, packet retransmission rate, and bandwidth.