METHOD, SYSTEM AND APPARATUS FOR MANAGING PUSH DATA TRANSFERS

• US 20110217953A1
• Filed: 06/21/2010
• Published: 09/08/2011
• Est. Priority Date: 03/03/2010
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Chalk Media Service Corp (Blackberry Limited)
• Inventors: O'REILLY, Jacob Samuel
• Granted Patent: US 9,178,949 B2
• Time in Patent Office: Days
• US Class Current: 455/412.1
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols

Abstract

A method, system, and apparatus for managing push data transfers is provided whereby in one implementation at least one push data server is situated on a network between a plurality of content servers and a plurality of computing devices. The push data server is configured to only perform a maximum number of concurrent data transfers of content between the content servers and the plurality of computing devices. The push data server is configured to deem that a particular push data transfer has been completed even if no express acknowledgment of such completion is ever received at the push data server, thereby reducing the likelihood of failure of push data transfers due to a misperception that the maximum number of concurrent data transfers being obtained.

Claims

1. A method for managing push data transfers comprising:

receiving content at a push data server from a content server for push delivery to a computing device;

beginning a push data transfer of the content to the computing device from the push data server;

incrementing a counter for use in determining a maximum number of concurrent push data transfers that can be effected from the push data server; and

decrementing the counter after the push data transfer is determined to be actually completed or deemed to be completed.

2. The method of claim 1, comprising deeming the push data transfer to be completed after a predefined time limit has been reached.

3. The method of claim 2, comprising:

receiving, at the push data server, transfer parameters, the transfer parameters include data representing parameters of a historic successfully completed push data transfer; and

determining the predefined time limit by comparing the transfer parameters.

4. The method of claim 3, wherein the transfer parameters further include at least one of a beginning time and ending time, a transfer duration, a content size, server specifications, and link specifications.

5. The method of claim 4, wherein the push data transfer is determined to be actually completed when an acknowledgement is received, by the push data server, confirming completion of the push data transfer.

6. The method of claim 5, wherein the comparing includes applying a probability model such that the push data server can infer with a high degree of confidence that the push data transfer is actually completed.

7. The method of claim 6, wherein the applying a probability model includes:

compiling a table of values of the transfer parameters; and

determining a mean and standard deviation for the transfer parameters that best match an expected duration of time to be used as the predefined time limit.

8. The method of claim 6, wherein the applying a probability model includes employing a cumulative distribution function to determine a minimum time duration to be used as the predefined time limit.

9. The method of claim 8, comprising:

receiving, at the push data server, a push data transfer request;

determining a capacity;

comparing the capacity to the counter; and

when the capacity equals the counter, queuing the push data transfer request.

10. The method of claim 9, wherein the beginning the push data transfer starts when the capacity is greater than the counter.

11. The method of claim 10, wherein the queuing the push data transfer request includes maintaining, at the push data server, a record of push data transfer requests.

12. The method of claim 10, wherein the queuing the push data transfer request includes rejecting the push data request.

13. The method of claim 12, wherein the rejecting the push data transfer request includes sending an error message to the content server.

14. The method of claim 13, comprising tracking of successful push data transfers where acknowledgements of completions are received at the push data server.

15. A push data server comprising a processor configured to:

receive content, from a content server, for push delivery to a computing device;

begin a push data transfer of the content to the computing device;

increment a counter for use in determining a maximum number of concurrent push data transfers that can be effected from the push data server; and

decrement the counter after the push data transfer is determined to be actually completed or deemed to be completed.

16. The push data server of claim 15, wherein the processor is further configured to deem the push data transfer to be completed after a predefined time limit has been reached.

17. The push data server of claim 16, wherein the processor is further configured to:

receive transfer parameters, the transfer parameters include data representing parameters of a historic successfully completed push data transfer; and

determine the predefined time limit by comparing the transfer parameters.

18. The push data server of claim 17, wherein the transfer parameters further include at least one of a beginning time and ending time, a transfer duration, a content size, server specifications, and link specifications.

19. The push data server of claim 18, wherein the processor is further configured to determine that the push data transfer is actually completed when the processor receives an acknowledgement confirming completion of the push data transfer.

20. A computer program product, for a push data server, comprising a computer readable storage medium having a computer-readable program code adapted to be executable on the push data server to implement a method for managing push data transfers, the method comprising:

receiving content at a push data server from a content server for push delivery to a computing device;

beginning a push data transfer of the content to the computing device from the push data server;

incrementing a counter for use in determining a maximum number of concurrent push data transfers that can be effected from the push data server; and

decrementing the counter after the push data transfer is determined to be actually completed or deemed to be completed.