Mobile event notifications

• US 10,554,762 B2
• Filed: 08/31/2018
• Issued: 02/04/2020
• Est. Priority Date: 02/26/2015
• Status: Active Grant

• Current Assignee: Airship Group, Inc.
• Original Assignee: Urban Airship, Inc.
• Inventors: Lowry, Adam C., Kolbeck, Cory David Hoffman, Herrick, Michael James
• Primary Examiner(s): Dinh, Khanh Q
• Application Number:
  US16/119,916
• Publication Number:
  US 20180375943A1
• Time in Patent Office: 522 Days
• Field of Search: 709203, 709205, 709220, 709228, 709225, 715753
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Disclosed is a mobile event streaming system that receives customer application lifecycle and user events including a message, event source and a destination then processes data for consumption by one or more customers, generating a secure data stream and sending the processed data over the generated data stream. An example system for receiving, processing, and delivering customer application lifecycle and user engagement data includes a server system having at least one processor, memory and a network interface where the memory stores program instructions for receiving, storing, processing and transmitting messages via the network interface. The mobile event streaming system may be a distributed content delivery service wherein the content delivered via the service is processed. Processing the data comprises the addition of metadata, one or more identifiers such as user, and event identifiers including predictions of future user engagement to enable real-time data consumption by customers.

Claims

1. A method for delivering mobile event notification data, the method comprising:

receiving, by a computing server, a plurality of mobile event notifications from a plurality of event source devices, a particular mobile event notification generated in response to an action associated with one of the plurality of event source devices, the particular mobile event notification comprising a (i) an event descriptor describing the action, (ii) a particular destination address associated with a message publisher, and (iii) a tag trigger that is associated with an automated message set by the message publisher;

filtering, by the computing server, the plurality of mobile event notifications including the particular mobile event notification based on one or more criteria specified by the message publisher and based on destination addresses included in the plurality of mobile event notifications, filtered mobile event notifications including the particular mobile event notification generated in response to the action;

generating, by the computing server, a plurality of data objects that comprise filtered information of events transmitted from the plurality of event source devices extracted from the filtered mobile event notifications;

transmitting, by the computing server and based on the tag trigger remained in the filtered information, the automated message set by the message publisher to the one of the event source devices; and

transmitting, by the computing server, the plurality of data objects comprising filtered information of the events to a data store, the data store accessible by message publisher.

2. The method of claim 1, further comprising:

decorating the filtered plurality of mobile event notifications with one or more metadata tags.

3. The method of claim 2, wherein the generated plurality of data objects further comprise the metadata tags.

4. The method of claim 1, wherein the action associated with the particular mobile event notification is an action performed by a user when using a mobile application.

5. The method of claim 1, wherein the action associated with the particular mobile event notification is associated with an application lifecycle event.

6. The method of claim 1, wherein the action associated with the particular mobile event notification is associated with a user engagement event.

7. The method of claim 1, wherein the data objects are in a pre-defined data format.

8. The method of claim 7, wherein the pre-defined data format is a format that allows a plurality of key-value pairs.

9. The method of claim 7, wherein the pre-defined data format is JSON.

10. The method of claim 1, wherein the event descriptor describing at least one of an app lifecycle event, a user engagement event, a behavior event, or a user location event, and the event descriptor including a timestamp.

11. A mobile event streaming system, comprising:

a processor;

a memory configured to store instructions, the instructions, when executed by the processor, cause the processor to;

receive, by a computing server, a plurality of mobile event notifications from a plurality of event source devices, a particular mobile event notification generated in response to an action associated with one of the plurality of event source devices, the particular mobile event notification comprising (i) an event descriptor describing the action, (ii) a particular destination address associated with a message publisher, and (iii) a tag trigger that is associated with an automated message set by the message publisher;

filter, by the computing server, the plurality of mobile event notifications including the particular mobile event notification based on one or more criteria specified by the message publisher and based on destination addresses included in the plurality of mobile event notifications, filtered mobile event notifications including the particular mobile event notification generated in response to the action;

generate, by the computing server, a plurality of data objects that comprise filtered information of events transmitted from the plurality of event source devices extracted from the filtered mobile event notifications;

transmit, by the computing server and based on the tag trigger remained in the filtered information, the automated message set by the message publisher to the one of the event source devices; and

transmit, by the computing server, the plurality of data objects comprising filtered information of the events to a data store, the data store accessible by message publisher.

12. The mobile event streaming system of claim 11, wherein the instructions further cause the processor to:

decorate the filtered plurality of mobile event notifications with one or more metadata tags.

13. The mobile event streaming system of claim 12, wherein the generated plurality of data objects further comprise the metadata tags.

14. The mobile event streaming system of claim 11, wherein the action associated with the particular mobile event notification is an action performed by a user when using a mobile application.

15. The mobile event streaming system of claim 11, wherein the action associated with the particular mobile event notification is associated with an application lifecycle event.

16. The mobile event streaming system of claim 11, wherein the action associated with the particular mobile event notification is associated with a user engagement event.

17. The mobile event streaming system of claim 11, wherein the data objects are in a pre-defined data format.

18. The mobile event streaming system of claim 17, wherein the pre-defined data format is a format that allows a plurality of key-value pairs.

19. The mobile event streaming system of claim 17, wherein the pre-defined data format is JSON.

20. The mobile event streaming system of claim 11, wherein the event descriptor describing at least one of a app lifecycle event, an user engagement event, a behavior event, or a user location event, and the event descriptor including a timestamp.