Push notification delivery system

• US 8,554,855 B1
• Filed: 06/14/2011
• Issued: 10/08/2013
• Est. Priority Date: 06/14/2011
• Status: Active Grant

• Current Assignee: Airship Group, Inc.
• Original Assignee: Urban Airship, Inc.
• Inventors: Lowry, Adam C, Onnen, Erik A
• Primary Examiner(s): Patel, Chirag R
• Application Number:
  US13/160,190
• Time in Patent Office: 847 Days
• Field of Search: 709201-207
• US Class Current: 709/206
• CPC Class Codes: H04L 51/02 using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Abstract

An example method for delivery of push notifications includes receiving a push notification including a message and a destination, creating a send token, sending a push notification derived from the received push notification and the send token, and receiving push information concerning a processing of the sent push notification which is identified by the send token. An example system for delivering push notifications includes a server system having a processor, memory, and a network interface, where the memory stores program instructions including code segments for receiving a received push notification via the network interface. In this example, the program instructions further includes code segments for creating a send token, code segments for sending a sent push notification derived from the received push notification and the send token via the network interface, and code segments for receiving received push information concerning a processing of the sent push notification are provided.

Claims

1. A system for delivering push notifications comprising:

a processor configured to;

receive a message and destination information, wherein the destination information is associated with a plurality of destinations to which the message should be sent;

create, for at least some of the destinations, a respective token, wherein the respective token associates a given destination with the message;

store the created tokens;

generate a push notification for a particular destination included in the at least some of the destinations, wherein the push notification is based at least in part on the particular destination and the message;

send to the particular destination, the generated push notification;

receive push information; and

determine, based at least in part on the token created for the particular destination, that the push information is associated with a status of a processing of the sent push notification at a device associated with the particular destination; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system of claim 1 wherein the created tokens comprise identifiers used to distinguish one sent push notification from another sent push notification.

3. The system of claim 1 wherein the processor is further configured to determine, from a set of stored recipients, a subset of recipients to which the message should be sent based at least in part on the destination information.

4. The system of claim 1 wherein the processor is further configured to determine that the message should be sent to all recipients included in a set of stored recipients.

5. The system of claim 1 wherein the processor is further configured to refine a list of the plurality of destinations based at least in part on filter criteria, and wherein push notifications including the received message are sent to each of the destinations included in the refined list.

6. The system of claim 1 wherein sending the generated push notification to the given destination is deferred based at least in part on deferral rules.

7. The system of claim 1 wherein the push notification is generated based at least in part on the token created for the particular destination.

8. The system of claim 1 wherein the processor is further configured to validate the received push information.

9. The system of claim 8 wherein in the event that the received push information is determined to be not valid, the processor is further configured to transmit an error message to the device.

10. The system of claim 1 wherein the processor is further configured to generate statistical information based at least in part on the received push information.

19. The system of claim 10 wherein the statistical information indicates usage patterns associated with an application program associated with the processing of the push notification.

20. The system of claim 10 wherein the statistical information includes a measure of a number of times an application program associated with the processing of the push notification has been opened, initialized, closed, foregrounded, or backgrounded.

11. A method for delivering push notifications comprising:

receiving, via one or more interfaces, a message and destination information, wherein the destination information is associated with a plurality of destinations to which the message should be sent;

creating, for at least some of the destinations, a respective token, wherein the respective token associates a given destination with the message;

storing the created tokens;

generating a push notification for a particular destination included in the at least some of the destinations, wherein the push notification is based at least in part on the particular destination and the message;

sending, to the particular destination, the generated push notification;

receiving push information; and

determining, based at least in part on the token created for the particular destination, that the push information is associated with a status of a processing of the sent push notification at a device associated with the particular destination.

12. The method of claim 11, further comprising determining, from a set of stored recipients, a subset of recipients to which the message should be sent based at least in part on the destination information.

13. The method of claim 11, further comprising determining that the message should be sent to all recipients included in a set of stored recipients.

14. The method of claim 11, further comprising refining a list of the plurality of destinations based at least in part on filter criteria, and wherein push notifications including the received message are sent to each of the destinations included in the refined list.

15. The method of claim 11 wherein the push notification is generated based at least in part on the token created for the particular destination.

16. The method of claim 11, further comprising generating statistical information based at least in part on the received push information.

17. The method of claim 16, wherein the statistical information indicates usage patterns associated with an application program associated with the processing of the push notification.

18. A computer program product embodied in a non-transitory computer readable media comprising:

receiving a message and destination information, wherein the destination information is associated with a plurality of destinations to which the message should be sent;

creating, for at least some of the destinations, a respective token, wherein the respective token associates a given destination with the message;

storing the created tokens;

generating a push notification for a particular destination included in the at least some of the destinations, wherein the push notification is based at least in part on the particular destination and the message;

sending, to the particular destination, the generated push notification;

receiving push information; and

determining, based at least in part on the token created for the particular destination, that the push information is associated with a status of a processing of the sent push notification at a device associated with the particular destination.