SYSTEM AND METHOD FOR MOBILE DEVICE PUSH COMMUNICATIONS

• US 20130047034A1
• Filed: 08/17/2011
• Published: 02/21/2013
• Est. Priority Date: 08/17/2011
• Status: Active Grant

• Current Assignee: Lookout Incorporated
• Original Assignee: Lookout Incorporated
• Inventors: Salomon, Ariel, Mahaffey, Kevin Patrick
• Granted Patent: US 8,788,881 B2
• Time in Patent Office: Days
• US Class Current: 714/18
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/4015 using location information
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/029 Location-based management or tracking services
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

Pushing data to mobile devices can be problematic because mobile platforms may support a number push services, each of which have different cost and reliability characteristics. The problem of being able to push data to multiple different types of mobile devices from a single server is solved by a push service aggregator supporting multiple push services. Upon receiving a push request, one or more push services are selected for pushing data to a client. The selection may be based on a delivery profile included with the push request, information about the client, past performance of the push services, current status of the push services, or combinations of these. The status of the push may be tracked and monitored so as to retry in the case of non-delivery.

Claims

1. A method comprising:

receiving, by a push service aggregator, a push request including both a message to be pushed to a mobile device and a delivery profile;

selecting by the push service aggregator from a plurality of available push services, at least one push service to push the message to the mobile device, the selecting being based on the delivery profile and on information about the mobile device to which the message is to be pushed; and

delivering by the push service aggregator the message to the selected at least one push service for an attempt at pushing the message to the mobile device.

2. The method of claim 1 further comprising:

after the delivering step has been performed, receiving from the selected at least one push service by the push service aggregator an indication that the attempted push failed, the selected at least one push service being then known as a first push service;

in response to the indication that the attempted push by the first push service failed, selecting by the push service aggregator from the plurality of available push services, a second push service, different from the previously selected first push service, to push the message to the mobile device, the selection of the second push service based on the delivery profile and on information about the mobile device to which the message is being pushed; and

delivering by the push service aggregator the message to the selected second push service for an attempted push of the message.

3. The method of claim 1 further comprising:

after the delivering step has been performed, receiving from the selected at least one push service by the push service aggregator an indication that the attempted push failed; and

re-delivering by the push service aggregator the message to the same at least one push service so that the at least one push service can attempt another push of the message to the mobile device.

4. The method of claim 3 wherein the step of re-delivering the message occurs after a specified time period has elapsed, wherein the time period is specified in the delivery profile.

5. The method of claim 1 further comprising:

at the push service aggregator, receiving from the selected at least one push service an indication that the message delivered to the selected at least one push service is pending for an attempted push of the message;

at the push service aggregator, determining that the selected at least one push service is unable to push the message delivered to the selected at least one push service to the mobile device within a specified time period;

at the push service aggregator, selecting from among the plurality of available push services, a second push service, different from the selected at least one push service, to push the message to the mobile device; and

delivering the message to the second push service for an attempted push of the message to the mobile device.

6. The method of claim 5 wherein the step of determining that the selected at least one push service is unable to push the message delivered to the selected at least one push service to the mobile device within the specified time period comprises:

during the specified time period, receiving from the at least one push service an indication that the push attempt of the delivered message failed.

7. The method of claim 5 wherein the step of determining that the at least one push service is unable to push the message to the mobile device within the specified time period comprises:

during the specified time period, failing to receive from the at least one push service an indication that the push attempt of the delivered message failed.

8. The method of claim 1 wherein the delivery profile includes an attribute specifying a maximum cost for pushing the message to the mobile device.

9. The method of claim 1 wherein the delivery profile includes an attribute specifying a priority level of the message.

10. The method of claim 1 wherein the delivery profile includes an attribute specifying a lowest cost push service for use.

11. The method of claim 1 wherein the step of selecting by the push service aggregator further comprises:

selecting the at least one push service also based on a current status of the at least one push service indicating that the at least one push service is operating.

12. The method of claim 1 wherein the step of selecting by the push service aggregator further comprises:

selecting the at least one push service also based on past performance of the at least one push service.

13. The method of claim 1 wherein the information about the mobile device is selected from the group consisting of mobile device telephone number, mobile device operating system, mobile device platform version, mobile device push token, push notification ID, C2DM token and combinations thereof.

14. The method of claim 1 wherein the delivery profile specifies a retry strategy for pushing the message to the mobile device.

15. The method of claim 5 wherein the step of determining that the selected at least one push service is unable to push the message delivered to the selected at least one push service to the mobile device comprises:

failing to receive a successful push notification from the at least one selected push service during a time period.

16. The method of claim 1 wherein the delivery profile is a name of a previously stored delivery profile.

17. A method comprising:

receiving, by a push service aggregator, a push request including a message to be pushed to a mobile device;

analyzing by the push service aggregator past performance data for a plurality of available push services;

selecting by the push service aggregator from among the plurality of available push services, at least one push service to push the message to the mobile device based on the past performance data analysis and on information about the mobile device; and

delivering by the push service aggregator the message to the selected at least one push service for an attempt at pushing the message to the mobile device.

18. The method of claim 17 wherein the past performance data includes an indication of message delivery success rate for each of the plurality of available push services.

19. The method of claim 17 wherein the past performance data includes an indication of message delivery latency for each of the plurality of available push services.

20. The method of claim 17 further comprising:

after the delivering step has been performed, receiving from the selected at least one push service by the push service aggregator an indication that the push failed, the selected at least one push service being then known as a first push service;

in response to the indication that the attempted push by the first push service failed, selecting by the push service aggregator from among the plurality of available push services, a second push service, different from the first push service, to push the message to the mobile device; and

delivering by the push service aggregator the message to the selected second push service for an attempted push of the message to the mobile device.

21. The method of claim 17 further comprising:

after the delivering step has been performed by the push service aggregator, receiving from the at least one push service an indication that the attempted push failed; and

re-delivering by the push service aggregator the message to the same selected at least one push service for the selected at least one push service to attempt another push of the message to the mobile device.

22. The method of claim 17 wherein the information about the mobile device is selected from the group consisting of mobile device telephone number, mobile device operating system, mobile device platform version, mobile device push token, push notification ID, C2DM token and combinations thereof.

23. The method of claim 17 wherein during the receiving step, the push service aggregator also receives a delivery profile for the message to be pushed that specifies a retry strategy for pushing the message to the mobile device.

24. The method of claim 17 further comprising:

determining that the selected at least one push service is unable to push the message delivered to the selected at least one push service to the mobile device by failing to receive a successful push notification from the at least one selected push service during a time period.

25. The method of claim 23 wherein the delivery profile is a name of a previously stored delivery profile.

26. A method comprising:

receiving, by a push service aggregator, a push request including a message to be pushed to a mobile device;

selecting by the push service aggregator from among a plurality of available push services, at least one push service to push the message to the mobile device based on information about the mobile device; and

delivering by the push service aggregator the message to the selected at least one push service for an attempt at pushing the message to the mobile device.

27. The method of claim 26 wherein the information about the mobile device

is selected from the group consisting of mobile device telephone number, mobile device operating system, mobile device platform version, mobile device push token, push notification ID, C2DM token and combinations thereof.

28. The method of claim 26 wherein, during the selecting step, the at least one push service is selected by the push service aggregator based on additional information from a message delivery profile included as part of the push request received by the push service aggregator.

29. The method of claim 26 wherein, during the selecting step, the at least one push service is selected by the push service aggregator based on additional information obtained by the push service aggregator concerning an analysis of past performance data of the selected at least one push service.

30. The method of claim 26 wherein during the receiving step, the push service aggregator also receives a delivery profile for the message to be pushed that specifies a retry strategy for pushing the message to the mobile device.

31. The method of claim 26 further comprising:

determining that the selected at least one push service is unable to push the message delivered to the selected at least one push service to the mobile device by failing to receive a successful push notification from the at least one selected push service during a time period.

32. The method of claim 30 wherein the delivery profile is a name of a previously stored delivery profile.

33. A method comprising:

receiving by a push service a push request from a server, the push request including a message, prioritization criteria and information about a mobile device to receive the message;

in response to the server push request, the push service responding to the server with a unique push identifier for the received push request;

choosing by the push service an initial mechanism for delivery of the message to the mobile device, the push service using the prioritization criteria and information about the mobile device to choose the initial mechanism;

delivering the message to the initial mechanism for an attempt by the initial mechanism at pushing the message to the mobile device;

receiving by the push service a current status indication for the pushing of the delivered message to the mobile device by the initial mechanism;

in response to the receipt by the push service of the current status indication from the initial mechanism, scheduling a job to be performed by the push service at some time in the future to determine the initial mechanism delivery status for the message to be pushed to the mobile device;

if before or during execution of the job by the push service, the push service determines that the initial mechanism has not pushed the message to the mobile device, then choosing by the push service a second mechanism for delivery of the message to the mobile device, the push service using the prioritization criteria and information about the mobile device to choose the second mechanism;

delivering the message to the second mechanism for an attempt by the second mechanism at pushing the message to the mobile device; and

,

in response to the message delivering, receiving by the push service a current status indication for the pushing of the delivered message to the mobile device by the second mechanism.

34. The method of claim 33 wherein the prioritization criteria includes an attribute specifying a maximum cost for pushing the message to the mobile device.

35. The method of claim 33 wherein the prioritization criteria includes an attribute specifying a priority level of the message.

36. The method of claim 33 wherein the prioritization criteria includes an attribute specifying a lowest cost push service for use.

37. The method of claim 33 wherein the step of choosing an initial mechanism by the push service further comprises:

choosing the initial mechanism also based on a current status of the initial mechanism indicating that the initial mechanism is operating.

38. The method of claim 33 wherein the step of choosing an initial mechanism by the push service further comprises:

choosing the initial mechanism also based on past performance of the initial mechanism.

39. The method of claim 33 wherein the information about the mobile device is selected from the group consisting of mobile device telephone number, mobile device operating system, mobile device platform version, mobile device push token, push notification ID, C2DM token and combinations thereof.

40. The method of claim 33 wherein the prioritization criteria specifies a retry strategy for pushing the message to the mobile device.

41. A method comprising:

receiving by a push service a push request from a server, the push request including a message, prioritization criteria and information about a mobile device to receive the message;

in response to the server push request, the push service responding to the server with a unique push identifier for the received push request;

choosing by the push service a plurality of delivery mechanisms for delivery of the message to the mobile device, the push service using the prioritization criteria and information about the mobile device to choose the plurality of delivery mechanisms;

delivering the message to the chosen plurality of delivery mechanisms for attempts by the chosen plurality of delivery mechanisms at pushing the message to the mobile device;

in response to the message delivering, receiving by the push service a current status indication for the pushing of the delivered message to the mobile device by the chosen plurality of delivery mechanisms;

in response to the receipt by the push service of the current status indication from the chosen plurality of delivery mechanisms, scheduling a job to be performed by the push service at some time in the future to determine the chosen plurality of delivery mechanisms delivery status for the message to be pushed to the mobile device; and

,

if before or during execution of the job by the push service, the push service determines that at least one of the chosen plurality of delivery mechanisms has pushed the message to the mobile device, then aborting by the push service of any pushing of the message by the remaining chosen delivery mechanisms.

42. The method of claim 41 wherein the prioritization criteria includes an attribute specifying a maximum cost for pushing the message to the mobile device.

43. The method of claim 41 wherein the prioritization criteria includes an attribute specifying a priority level of the message.

44. The method of claim 41 wherein the prioritization criteria includes an attribute specifying a lowest cost push service for use.

45. The method of claim 41 wherein the step of choosing a plurality of delivery mechanisms by the push service further comprises:

choosing the plurality of delivery mechanisms also based on a current status of the plurality of delivery mechanisms indicating that the delivery mechanism is operating.

46. The method of claim 41 wherein the step of choosing a plurality of delivery mechanisms by the push service further comprises:

choosing the plurality of delivery mechanisms also based on past performance of the delivery mechanism.

47. The method of claim 41 wherein the information about the mobile device is selected from the group consisting of mobile device telephone number, mobile device operating system, mobile device platform version, mobile device push token, push notification ID, C2DM token and combinations thereof.

48. A method comprising:

receiving, by a push service aggregator, a new push request including both a message to be pushed to a mobile device and prioritization criteria;

determining by the push service aggregator whether the new received push request matches any pending push requests having the same requester, the same mobile device and whether the prioritization criteria of the new received push request is met by the prioritization criteria of the pending push request;

selecting by the push service aggregator to combine the new received push request with the matching pending push request; and

delivering by the push service aggregator the message from the new received push request to be combined with the message from the matching pending push request to a delivery mechanism for an attempt at pushing the messages to the mobile device.

49. A method comprising:

receiving from a server by a push service a message send request asking for the message to be delivered to a mobile device;

in response to the received message send request, sending by the push service to the server a response indicating an identifier for the push request;

at the push service, transmitting the message to a delivery mechanism for pushing to the mobile device;

if the delivery mechanism returns status to push service with a failure notification, updating by the push service a message state to failed and at the push service performing an callback to inform the server of the failed message state; and

,

if the delivery mechanism does not respond to the push service with status, then by the push service, polling the delivery mechanism for status, and if there is an update in the message state, the push service performing a callback to inform the server of the updated message state.

50. The method of claim 49 further comprising:

upon connection of the mobile device to the server as a result of delivery of the message, receiving by the push service a callback from the server to confirm delivery of the message.

51. A method comprising:

receiving from a server by a push service a message send request specifying a reliable least-cost delivery profile asking for the message to be delivered to a mobile device that supports a plurality of delivery mechanisms;

in response to the received message send request, sending by the push service to the server a response indicating an identifier for the push request;

at the push service, choosing a first delivery mechanism based upon the message send request reliable least-cost profile for pushing the message to a mobile device;

at the push service, transmitting the message to the chosen first delivery mechanism for pushing the message to the mobile device;

if the chosen first delivery mechanism responds to the push service that the requested message delivery has failed, then at the push service, choosing a second delivery mechanism based upon the message send request reliable least cost delivery profile for delivering the message to the mobile device; and

at the push service, transmitting the message to the chosen second delivery mechanism for pushing the message to the mobile device.

52. The method of claim 51 further comprising:

upon connection of the mobile device to the server as a result of delivery of the message, receiving by the push service a callback from the server to confirm delivery of the message.

53. The method of claim 51 further comprising:

if the chosen first delivery mechanism returns status to push service with a failure notification, updating by the push service a message state to failed and at the push service performing a callback to inform the server of the failed message state.

54. The method of claim 51 further comprising:

if the chosen first delivery mechanism does not respond to the push service with status, then by the push service, polling the chosen first delivery mechanism for status, and if there is an update in the message state, the push service performing a callback to inform the server of the updated message state.