IP Library Granted Patent US 11,711,442
Granted Patent B2
US 11,711,442 · App. 17/582,953 · Granted Jul 25, 2023

Push notification delivery system

Inventors: Adam C. Lowry (Portland, OR); Erik A. Onnen (Portland, OR)
Assignee: Airship Group, Inc.
H04L67/55H04L51/02H04L51/04H04L51/18H04L51/224H04L67/10H04L67/104H04L67/564H04L67/568H04W4/14
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 11,711,442
App. No.
17/582,953
Granted
Jul 25, 2023
Kind
B2
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 (55)

1. A method comprising:

receiving, from an originator, a message content, recipient information, and one or more target application life cycle events targeted by the originator, the recipient information identifying one or more lists of message recipients;

identifying a plurality of devices that are associated with the message recipients in the one or more lists;

receiving, from one of the plurality of devices that are associated with the message recipients, information associated with an application installed at the one of the plurality of devices, the information comprising data of one of more occurred application life cycle events associated with the application occurred at the device; and

determining whether at least one of the occurred application life cycle events matches at least one of the one or more target application life cycle events; and

transmitting, responsive to at least one of the occurred application life cycle events matching at least one of the one or more target application life cycle events, a message comprising the message content to the one of the plurality of devices.

2. The method of claim 1 , wherein the message content includes a message payload.

3. The method of claim 1 , wherein the message is a push notification, and wherein the method further comprises:

receiving, after transmitting the push notification, push information associated with the push notification.

4. The method of claim 1 , further comprising:

developing statistics from the message and additional messages after the additional messages are transmitted to the plurality of devices; and

presenting the statistics to the originator.

5. The method of claim 4 , wherein the statistics comprises a number of times a specific application life cycle event is performed on an application program associated with the message, the specific application life cycle event is one of: opening the application program, initializing the application program, closing the application program, foregrounding the application program, or backgrounding the application program.

6. The method of claim 1 , wherein the occurred application life cycle events is associated with an application program that is published by the originator.

7. The method of claim 1 , wherein the message is generated by steps comprising:

creating, for each message recipient, a respective token associating the message recipient, the respective token comprising an identifier used to distinguish the message to be transmitted to the message recipient from another message to be transmitted to another message recipient;

creating the message based on the message content; and

associating the message with the respective token.

8. The method of claim 1 , wherein transmitting the message to the one of the plurality of devices is based on one or more deferral rules.

9. A system comprising:

one or more processors; and

memory configured to store computer code comprising instructions, the instructions, when executed by the one or more processors, cause the one or more processors to:

receive, from an originator, a message content, recipient information, and one or more target application life cycle events targeted by the originator, the recipient information comprising one or more lists of message recipients;

identify a plurality of devices that are associated with the message recipients in the one or more lists;

receive, from one of the plurality of devices that are associated with the message recipients, information associated with an application installed at the one of the plurality of devices, the information comprising data of one of more occurred application life cycle events associated with the application occurred at the device; and

determine whether at least one of the occurred application life cycle events matches at least one of the one or more target application life cycle events; and

transmit, responsive to at least one of the occurred application life cycle events matching at least one of the one or more target application life cycle events, a message comprising the message content to the one of the plurality of devices.

10. The system of claim 9 , wherein the message content includes a message payload.

11. The system of claim 9 , wherein the message is a push notification, and wherein the instructions, when executed, further cause the one or more processors to:

receive, after transmitting the push notification, push information associated with the push notification.

12. The system of claim 9 , wherein the instructions, when executed, further cause the one or more processors to:

develop statistics from the message and additional messages after the additional messages are transmitted to the plurality of devices; and

present the statistics to the originator.

13. The system of claim 12 , wherein the statistics comprises a number of times a specific application life cycle event is performed on an application program associated with the message, the specific application life cycle event is one of: opening the application program, initializing the application program, closing the application program, foregrounding the application program, or backgrounding the application program.

14. The system of claim 9 , wherein the occurred application life cycle events is associated with an application program that is published by the originator.

15. The system of claim 9 , wherein the message is generated by steps comprising:

creating, for each message recipient, a respective token associating the message recipient, the respective token comprising an identifier used to distinguish the message to be transmitted to the message recipient from another message to be transmitted to another message recipient;

creating the message based on the message content; and

associating the message with the respective token.

16. The system of claim 9 , wherein transmitting the message to the one of the plurality of devices is based on one or more deferral rules.

17. A non-transitory computer readable medium for storing computer code comprising

instructions, the instructions, when executed by one or more processors, cause the one or more processors to:

receive, from an originator, a message content, recipient information, and one or more target application life cycle events targeted by the originator, the recipient information comprising one or more lists of message recipients;

identify a plurality of devices that are associated with the message recipients in the one or more lists;

receive, from one of the plurality of devices that are associated with the message recipients, information associated with an application installed at the one of the plurality of devices, the information comprising data of one of more occurred application life cycle events associated with the application occurred at the device; and

determine whether at least one of the occurred application life cycle events matches at least one of the one or more target application life cycle events; and

transmit, responsive to at least one of the occurred application life cycle events matching at least one of the one or more target application life cycle events, a message comprising the message content to the one of the plurality of devices.

18. The non-transitory computer readable medium of claim 17 , wherein the instructions, when executed, further cause the one or more processors to:

develop statistics from the message and additional messages after the additional messages are transmitted to the plurality of devices; and

present the statistics to the originator.

19. The non-transitory computer readable medium of claim 17 , wherein the occurred application life cycle events is associated with an application program that is published by the originator.

20. The non-transitory computer readable medium of claim 17 , wherein the message is generated by steps comprising:

creating, for each message recipient, a respective token associating the message recipient, the respective token comprising an identifier used to distinguish the message to be transmitted to the message recipient from another message to be transmitted to another message recipient;

creating the message based on the message content; and

associating the message with the respective token.

Assignments (3)
SECURITY INTEREST Recorded Jul 1, 2024
From: AIRSHIP GROUP, INC.; APPTIMIZE, LLC
To: RUNWAY GROWTH FINANCE CORP.
Reel/Frame 068099/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 1, 2022
From: LOWRY, ADAM C.; ONNEN, ERIK A.
To: URBAN AIRSHIP, INC.
Reel/Frame 059132/0729 →
CHANGE OF NAME Recorded Mar 1, 2022
From: URBAN AIRSHIP, INC.
To: AIRSHIP GROUP, INC.
Reel/Frame 059132/0736 →