Method and system for conserving network resources when sending information to mobile devices

• US 8,943,204 B2
• Filed: 01/23/2012
• Issued: 01/27/2015
• Est. Priority Date: 01/23/2012
• Status: Active Grant

• Current Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Original Assignee: Cellco Partnership, Inc. (Verizon Communications Inc.)
• Inventors: Caldeira de Andrada, Mauricio Pati, Ren, Xin, Dennis, Anthony
• Primary Examiner(s): Gee, Jason K.
• Assistant Examiner(s): Tsang, Henry
• Application Number:
  US13/356,434
• Publication Number:
  US 20130191544A1
• Time in Patent Office: 1,100 Days
• Field of Search: None
• US Class Current: 709/226
• 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/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 76/15 Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/38 triggered by timers

Abstract

Information is provided to a mobile device while reducing the number of traffic channels established over a predetermined time period. A pull client on a mobile device receives requests for information from applications on the mobile device. The pull client creates a timing list which includes the timing requirements for each application. Applications that have overlapping timing requirements are grouped together into the same timing group. Once the time for creating a traffic channel for one of the groups arrives, a traffic channel is created between the mobile device and a carrier gateway. Information for each respective application within the same timing group is obtained through the network using the same traffic channel. When the requested information is provided to all applications within the same timing group, the traffic channel is released after a predetermined time. The method is repeated for a next timing group entry.

Claims

1. A method of providing information to a mobile device, comprising steps of:

receiving a request for information, from each of a number of applications on the mobile device, by a pull client on the mobile device;

determining a timing requirement for each application;

creating a timing list, wherein the timing list includes the timing requirements for each application;

grouping applications that have overlapping timing requirements within a timing group;

for each timing group, randomizing a trigger time for each target application scheduled to be updated within a scheduled traffic channel session based on a trigger time of a previous application having a randomized trigger time in the respective timing group, wherein a random sequence of the target applications in the respective timing group is generated;

for each timing group, setting a time to create a traffic channel for the respective timing group based on the randomized trigger times within boundaries of the overlapping timing requirements of the applications grouped within the respective timing group; and

when the time for creating the traffic channel for the respective timing group has arrived;

sending a request to a mobile communication network to establish a traffic channel through the mobile communication network for a session between the mobile device and a carrier gateway;

requesting and receiving information for the applications of the respective timing group from at least one application server during the same established traffic channel session through the mobile communication network;

identifying target applications of the respective timing group;

forwarding information received during the same established traffic channel session through the network, to the target applications; and

releasing the traffic channel after a predetermined time after the forwarding of received information to every target application for the respective timing group has been completed.

2. The method of claim 1, wherein determining the timing requirement for each application comprises obtaining a delay and time tolerance for the information request from each application.

3. The method of claim 2, wherein:

determining the timing requirement for each application further comprises obtaining a period of an information request from at least one of the applications.

4. The method of claim 3, further comprises:

based on the obtained period, adjusting a timer after completion of a last corresponding timer for the information request from the at least one application by determining;

a minimum trigger time is the time when the last corresponding timer expired plus the obtained period, wherein the minimum trigger time represents the earliest time when the request to establish the traffic channel for the at least one application is to be sent to the mobile communication network; and

a maximum trigger time is the time when the last corresponding timer expired, plus the period, and plus the respective time tolerance, wherein the maximum trigger time represents the latest time when the request to establish the traffic channel for the at least one application is to be sent to the mobile communication network.

5. The method of claim 1, wherein the timing list is sorted in an ascending time order from an earliest maximum trigger time to a latest maximum trigger time relative to each of the applications included in the timing list.

6. The method of claim 5, wherein:

a minimum trigger time of each respective application is equivalent to a delay plus a current time for the information request for the respective application, and is an earliest time the request to establish the traffic channel is to be sent to the mobile communication network; and

a maximum trigger time of each application in the respective timing group is equivalent to the delay plus a respective tolerance plus the current time for the information request for the respective application, and is a latest time the request to establish the traffic channel is to be sent to the mobile communication network.

7. The method of claim 1, wherein the grouping of applications comprises:

determining, for each application from which an information request was received, a minimum trigger time and a maximum trigger time requirement for the application, wherein the minimum trigger time is an earliest time the request to establish the traffic channel is to be sent for the application and the maximum trigger time is a latest time the request to establish the traffic channel is to be sent for the application;

determining which applications have an overlap in timing between the minimum trigger time and the maximum trigger time; and

scheduling requesting information from at least one application server during a same traffic channel session for all applications in the respective timing group.

8. The method of claim 7, wherein an earliest possible trigger time in a timing group falls after a latest minimum trigger time of each application in the timing group.

9. The method of claim 1, further comprising:

updating the created timing list every time either a traffic session completes or there is a request for information from at least one of the target applications.

10. The method of claim 1, further comprising for each timing group:

once the respective timing group from the timing list expires, removing the respective timing group from the timing group list; and

replacing the respective timing group with a next timing group.

11. The method of claim 1, wherein randomizing the trigger time further comprises:

having a trigger time of

12. A mobile device comprising:

a user interface;

a storage device for content and holding applications;

a communication interface configured to enable communications via a mobile communication network;

a processor coupled to the user interface and communication interface and having access to the storage device for execution of the applications to enable the mobile device to obtain content related to the applications from application servers via the mobile communication network; and

a pull client, wherein execution of the pull client by the processor configures the mobile device to;

receive a request for information from each of a number of applications on the mobile device;

determine a timing requirement for each application;

create a timing list, wherein the timing list includes the timing requirement for each application and is maintained by the pull client;

group applications that have overlapping timing requirements within one of a plurality of timing groups;

for each timing group, randomize a trigger time for each application in the timing group scheduled to be updated within a scheduled traffic channel session based on a trigger time of a previous application having a randomized trigger time in the respective timing group, wherein a random sequence of the target applications in the respective timing group is generated;

for a first timing group of the plurality of timing groups scheduled to be updated within a scheduled traffic channel session, setting a time to create a traffic channel for the first timing group based on the randomized trigger times within boundaries of the overlapping timing requirements of the applications grouped within the first timing group; and

in response to the arrival of the time for creating a traffic channel;

send a request to the mobile communication network to establish a traffic channel through the mobile communication network for a session between the mobile device and the at least one carrier gateway;

provide authentication information to the carrier gateway;

request and receive information for the respective applications of the first timing group from at least one application server during the same established traffic channel session through the mobile communication network;

identify target applications of the first timing group;

forward information received during the same established traffic channel session through the mobile communication network, to the target applications; and

in response to a determination that the forwarding of received information to every target application of the first timing group is completed, release the traffic channel after a predetermined time.

13. The device of claim 12, wherein execution of the pull client by the processor configures the mobile device to determine the timing requirement for each application configures the mobile device to obtain a delay and a time tolerance for an information request from the application.

14. The device of claim 13, wherein:

execution of the pull client by the processor configures the mobile device to determine the timing requirement for each application further configures the mobile device to obtain a period of an information request for at least one of the applications.

15. The device of claim 14, wherein execution of the pull client by the processor configures the mobile device to determine the timing requirement for each respective application further configures the mobile device to:

based on the obtained period, adjust a timer after completion of a last corresponding time for the information request from the at least one application by determining;

a minimum trigger time is the time when the last corresponding timer expired plus a respective period, and is the earliest time when the request to establish the traffic channel for the at least one application is to be sent by the pull client to the mobile communication network; and

a maximum trigger time is the time when the last corresponding timer expired, plus the period, and plus the respective tolerance, and is the latest time when the request to establish the traffic channel for the at least one application is to be sent by the pull client to the mobile communication network.

16. The device of claim 15, wherein the timing list maintained by the pull client is sorted in an ascending time order from an earliest maximum trigger time to a latest maximum trigger time relative to each of the applications included in the timing list.

17. The device of claim 16, wherein:

a minimum trigger time of each application is equivalent to a delay plus a current time for the information request for the application, and is an earliest time the request to establish the traffic channel is to be sent by the pull client to the mobile communication network for the application; and

a maximum trigger time of each application is equivalent to the delay plus a respective tolerance plus a current time for the information request for the respective application, and is a latest time the request to establish the traffic channel is to be sent by the pull client to the mobile communication network for the application.

18. The device of claim 12, wherein execution of the pull client by the processor configures the mobile device to group applications, the mobile device is further configured to:

determining, for each application from which an information request was received, a minimum trigger time and a maximum trigger time requirement for the application, wherein the minimum trigger time is an earliest time the request to establish the traffic channel is to be sent for the application and the maximum trigger time is a latest time the request to establish the traffic channel is to be sent for the application;

determining which applications have an overlap in timing between the minimum trigger time and the maximum trigger time; and

scheduling requesting information from at least one application server during a same traffic channel session for all applications in the respective timing group.

19. The device of claim 18, wherein an earliest possible trigger time in a timing group falls after a latest minimum trigger time of each application in the timing group.

20. The device of claim 12, wherein execution of the pull client by the processor configures the mobile device to:

update the created timing list every time either a traffic session completes or there is a request for information from at least one of the applications.

21. The device of claim 12, wherein the mobile device is further configured to:

once the first timing group from the timing list expires, remove the first timing group from the timing group list; and

replace the first timing group with a second timing group.

22. The device of claim 12, wherein randomizing the trigger time further comprises:

having a trigger time of