IP Library Granted Patent US 8,244,822
Granted Patent B1
US 8,244,822 · App. 13/326,269 · Granted Aug 14, 2012

Push notification delivery system

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,244,822
App. No.
13/326,269
Granted
Aug 14, 2012
Kind
B1
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 (41)

1. A method for delivery of push notifications comprising:

receiving, via an interface, a message and destination information representing a plurality of destinations to which the message should be sent;

creating, for each destination, a respective token associating the destination and the message;

storing each of the created tokens;

generating, for a given destination in the plurality of destinations, a push notification based at least in part on the given destination and the received message;

sending the generated push notification to the given destination;

receiving push information and determining, using a microprocessor, that the push information is associated with a status of a processing of the push notification at a device associated with the given destination, wherein the determination is based at least in part on the token created for the given destination; and

storing the received push information.

2. The method of claim 1 , 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.

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

4. The method of claim 3 , 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.

5. The method of claim 1 , wherein the push notification is generated based at least in part on the token created for the given destination.

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

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

8. A system for delivering push notifications comprising:

a processor configured to:

receive a message and destination information representing a plurality of destinations to which the message should be sent;

create, for each destination, a respective token associating the destination and the message;

store each of the created tokens;

generate, for a given destination in the plurality of destinations, a push notification based at least in part on the given destination and the received message;

send the generated push notification to the given destination; and

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

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

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

10. The system of claim 8 , 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.

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

12. The system of claim 11 , 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.

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

14. The system of claim 8 , wherein the push notification is generated based at least in part on the token created for the given destination.

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

16. The system of claim 15 , 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.

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

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

19. The system of claim 17 , 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.

20. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a message and destination information representing a plurality of destinations to which the message should be sent;

creating, for each destination, a respective token associating the destination and the message;

storing each of the created tokens;

generating, for a given destination in the plurality of destinations, a push notification based at least in part on the given destination and the received message;

sending the generated push notification to the given destination; and

receiving push information and determining that the push information is associated with a status of a processing of the push notification at a device associated with the given destination, wherein the determination is based at least in part on the token created for the given destination.

Assignments (12)
SECURITY INTEREST Recorded Jul 1, 2024
From: AIRSHIP GROUP, INC.; APPTIMIZE, LLC
To: RUNWAY GROWTH FINANCE CORP.
Reel/Frame 068099/0779 →
RELEASE OF SECURITY INTEREST Recorded Jun 28, 2024
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: AIRSHIP GROUP, INC.; APPTIMIZE, LLC
Reel/Frame 067965/0545 →
CHANGE OF NAME Recorded Jan 21, 2021
From: URBAN AIRSHIP, INC.
To: AIRSHIP GROUP, INC.
Reel/Frame 055059/0223 →
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2020
From: SILVER LAKE WATERMAN FUND, L.P.
To: URBAN AIRSHIP, INC.; TELLO, INC.
Reel/Frame 052300/0284 →
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2020
From: SILICON VALLEY BANK
To: URBAN AIRSHIP, INC.
Reel/Frame 052300/0425 →
SECURITY INTEREST Recorded Apr 2, 2020
From: URBAN AIRSHIP, INC.; APPTIMIZE, LLC
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 052308/0550 →
SECURITY INTEREST Recorded May 30, 2017
From: URBAN AIRSHIP, INC.; TELLO, INC.
To: SILVER LAKE WATERMAN FUND, L.P., AS AGENT
Reel/Frame 042532/0575 →
RELEASE OF SECURITY INTEREST Recorded Apr 6, 2017
From: ORIX GROWTH CAPITAL, LLC (F/K/A ORIX VENTURES, LLC)
To: URBAN AIRSHIP, INC.; TELLO, INC.
Reel/Frame 041890/0286 →
SECURITY INTEREST Recorded Sep 25, 2015
From: URBAN AIRSHIP, INC.; TELLO, INC.
To: ORIX VENTURES, LLC
Reel/Frame 036654/0332 →
SECURITY INTEREST Recorded Jun 30, 2015
From: URBAN AIRSHIP, INC.
To: SILICON VALLEY BANK
Reel/Frame 035959/0313 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 20, 2012
From: LOWRY, ADAM C.; ONNEN, ERIK A.
To: URBAN AIRSHIP, INC.
Reel/Frame 027571/0592 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2012
From: LOWRY, ADAM C.; ONNEN, ERIK A.
To: URBAN AIRSHIP, INC.
Reel/Frame 027556/0109 →