DATA BUNDLING AND FAST DORMANCY BASED UPON INTELLIGENT APPLICATION LEARNING

• US 20120124196A1
• Filed: 11/16/2010
• Published: 05/17/2012
• Est. Priority Date: 11/16/2010
• Status: Active Grant

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Brisebois, Arthur Richard, Tong, Yonghui
• Granted Patent: US 9,167,618 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• 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: H04W 52/0264 by selectively disabling software applications
• CPC Class Codes: H04W 76/25 Maintenance of established connections
• CPC Class Codes: H04W 76/27 Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 76/38 triggered by timers
• CPC Class Codes: H04W 88/12 Access point controller devices
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A system and methodology that performs data bundling and controls fast dormancy based on application monitoring and classification is provided. Moreover, the system provides a balance between saving battery power of a user equipment (UE) and reducing signaling and processing load in a radio resource controller (RRC). Specifically, the system observes data flow related behavior of applications on the UE. On receiving a first data flow request, an arrival time of a next data flow request is predicted based on an analysis of the behavior, and the system determines whether the two data flows can be bundled together and transmitted over a single connection. Additionally, on completion of the first data flow, the arrival time of the next data flow request is predicted based on the analysis, and the system determines whether a fast dormancy timer can be disabled to transmit the next data flow over the current connection.

Claims

1. A system, comprising:

an application profiler (AP) component that determines characteristics of one or more applications on a user equipment (UE) in a wireless communication network; and

an AP engine that identifies an arrival time of a next data flow request associated with the one or more applications based on an analysis of the characteristics,

wherein at least one of data bundling is performed or a fast dormancy timer is disabled based in part on the arrival time.

2. The system of claim 1, further comprising, a monitoring component that tracks data flows associated with the one or more applications.

3. The system of claim 2, further comprising, a profile creation component that generates at least one profile for the one or more applications based on at least one of a disparate analysis of the tracked data flows or data received from the one or more applications, wherein the at least one profile includes one or more profile keys relating to the one or more applications.

4. The system of claim 3, wherein the one or more profile keys include at least one of inter-arrival time, frequency of use, packet size, session duration, delay tolerance, application interactivity time, service provider preference, user preference, application developer preference, or UE manufacturer preference, and

wherein the analysis includes at least one of historical data analysis or statistical analysis that employs the one or more profile keys.

5. The system of claim 3, further comprising, an application profile database that stores the at least one profile.

6. The system of claim 1, wherein the AP engine determines that a current data flow request is to be bundled with the next data flow request, based on at least one of the arrival time of the next data flow request or a delay tolerance of an application associated with the current data flow request.

7. The system of claim 6, further comprising, a bundle cache that stores the current data flow request until at least one of a bundling timer expires or the next data flow request is received.

8. The system of claim 7, further comprising, a data bundling component that bundles the current data flow request and the next data flow request and delivers a current data flow together with a next data flow over a single connection established between the UE and a radio resource controller (RRC)

9. The system of claim 1, wherein the AP engine detects whether the arrival time is between expiration of the fast dormancy timer and expiration of at least one network timer that transitions the UE to an IDLE state.

10. The system of claim 9, further comprising, a fast dormancy component that disables the fast dormancy timer based on the detection.

11. The system of claim 1, further comprising a user interactivity component that monitors user input to identify at least one of time correlations or gaps associated with data flows, which are employed by the AP engine to determine the arrival time.

12. A method, comprising:

monitoring data flow behavior of an application on a user equipment (UE) to identify one or more data flow characteristics of the application;

predicting an arrival time of a next data flow associated with the application based on an analysis of the one or more data flow characteristics; and

at least one of performing data bundling of the next data flow with a current data flow, or disabling a fast dormancy timer on completion of the current data flow, based in part on the arrival time.

13. The method of claim 12, further comprising creating a profile for the application that includes data relating to at least one of inter-arrival time, frequency of use, packet size, session duration, delay tolerance, application interactivity time, service provider preference, user preference, application developer preference, or UE manufacturer preference.

14. The method of claim 12, further comprising classifying the application based on its delay tolerance.

15. The method of claim 12, wherein the predicting includes analyzing the one or more data flow characteristics to forecast when a request for the next data flow will be initiated.

16. The method of claim 12, wherein the performing includes:

identifying, on receiving a request for the current data flow, a delay tolerance of a current application associated with the current data flow;

holding the current data flow in a cache, if the current application is delay tolerant; and

transmitting the current data flow and the next data flow over a single connection, on arrival of a next request for the next data flow.

17. The method of claim 12, wherein the disabling includes:

detecting, on completion of the current data flow, whether the arrival time of the next data flow is between expiration of the fast dormancy timer and expiration of at least one network timer that transitions the UE to an IDLE state; and

at least one of disabling or delaying the fast dormancy timer if detected that the arrival time of the next data flow is between expiration of the fast dormancy timer and expiration of the at least one network timer.

18. A system, comprising:

means for forecasting an arrival time of a next data flow associated with one or more applications in a user equipment (UE), based on an analysis of data flow related activity of the one or more applications; and

means for controlling at least one of data bundling or a fast dormancy mechanism in a wireless communication network, based in part on the arrival time.

19. The system of claim 18, wherein the means for controlling includes:

means for identifying, on receiving a request for a current data flow, a delay tolerance of a current application associated with the current data flow;

means for storing the current data flow, if the current application is delay tolerant; and

means for transmitting the current data flow and the next data flow over a common connection, on arrival of a next request for the next data flow.

20. The system of claim 18, wherein the means for controlling includes means for at least one of disabling or delaying a fast dormancy timer, if detected that the arrival time of the next data flow is between expiration of the fast dormancy timer and expiration of at least one network timer that transitions the UE to an IDLE state.