Mobile event notifications for network enabled objects

• US 10,567,536 B2
• Filed: 01/03/2019
• Issued: 02/18/2020
• Est. Priority Date: 02/26/2015
• Status: Active Grant

• Current Assignee: Airship Group, Inc.
• Original Assignee: Urban Airship, Inc.
• Inventors: Herrick, Michael James, Lowry, Adam C., Kolbeck, Cory David Hoffman, McHugh, Michael Shane Robert
• Primary Examiner(s): Dinh, Khanh Q
• Application Number:
  US16/239,173
• Publication Number:
  US 20190158616A1
• Time in Patent Office: 411 Days
• Field of Search: 709220, 709224, 709226, 709228, 709232
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/55 Push-based network services
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

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 system, comprising:

an event source repository configured to store one or more mobile event notifications transmitted from one or more network enabled devices that are associated with a common identifier, wherein a transmission of each mobile event notification is triggered by an event associated with one of the network enabled devices, and each mobile event notification comprises an event descriptor describing one or more attributes of the event;

a plurality of channels associated with one of the network enabled devices, at least two channels configured to communicate information to the one of the network enabled devices through a different communication protocol, communication protocols including at least a push notification protocol and a mail transfer protocol; and

a notification application configured to;

receive a request to send a message to one of the network enabled devices associated with the common identifier;

determine a target type of interaction associated with the message to be sent based on the mobile event notifications associated with the common identifier retrieved from the event source repository;

select one of the plurality of channels based on the target type of interaction, a type of event associated with the message, or a preference associated with the common identifier; and

transmit, using one of the communication protocols, a message through the selected channel to the one of the network enabled devices.

2. The system of claim 1, wherein the network enabled devices comprise a smartphone and an Internet of Things (IoT) device.

3. The system of claim 1, wherein the target type of interaction is one of:

a user clicking the message, a user sharing the message, a user reading the message for more than a duration, and a user replying the message.

4. The system of claim 1, wherein the common identifier identifies a user who is associated with the one or more network enabled devices.

5. The system of claim 1, wherein the notification application is further configured to:

generate, in response to receiving the request, the message based on the request; and

adding information specific to the common identifier to the message.

6. The system of claim 1, wherein the notification application is further configured to:

schedule transmitting the message at a time that is likely to result in the target type of interaction.

7. The system of claim 1, wherein the notification application is further configured to transmit the message through a second selected channel to the one of the network enabled devices.

8. The system of claim 1, wherein a first message associated with a first type of event is transmitted through a first selected channel and a second message associated with a second type of event is transmitted through a second selected channel different from the first selected channel, a selection of channels is determined based on the type of event.

9. The system of claim 1, wherein at least some of the mobile event notifications stored in the event source repository are associated with historical user behaviors, and determining the target type of interaction associated with the message to be sent based on the mobile event notifications retrieved from the event source repository comprising determining the target type of interaction based on the historical user behaviors.

10. The system of claim 1, wherein the common identifier is associated with the preference specified by a user identified by the common identifier, the preference specifying a certain type of messages to be sent from a particular channel associated with a particular communication protocol.

11. A system, comprising:

an event source repository configured to store one or more mobile event notifications transmitted from one or more network enabled devices that are associated with a common identifier, wherein a transmission of each mobile event notification is triggered by an event associated with one of the network enabled devices, and each mobile event notification comprises an event descriptor describing one or more attributes of the event;

a plurality of channels associated with one of the network enabled devices, at least two channels configured to communicate information to the one of the network enabled devices through a different communication protocol, communication protocols including at least a push notification protocol and a mail transfer protocol; and

a notification application configured to;

receive a request to send a message to one of the network enabled devices associated with the common identifier;

determine a target type of interaction associated with the message to be sent based on the mobile event notifications associated with the common identifier retrieved from the event source repository;

select one of the plurality of channels in accordance with a likelihood that the target type of interaction to be occurred based on records of the mobile event notifications retrieved from the event source repository; and

transmit, using one of the communication protocols, a message through the selected channel to the one of the network enabled devices.

12. The system of claim 11, wherein the target type of interaction is one of:

a user clicking the message, a user sharing the message, a user reading the message for more than a duration, and a user replying the message.

13. The system of claim 11, wherein the notification application is further configured to:

generate, in response to receiving the request, the message based on the request; and

adding information specific to the common identifier to the message.

14. The system of claim 11, wherein the notification application is further configured to:

schedule transmitting the message at a time that is likely to result in the target type of interaction.

15. The system of claim 11, wherein the notification application is further configured to transmit the message through a second selected channel to the one of the network enabled devices.

16. A method, comprising:

storing one or more mobile event notifications transmitted from one or more network enabled devices that are associated with a common identifier, wherein a transmission of each mobile event notification is triggered by an event associated with one of the network enabled devices, and each mobile event notification comprises an event descriptor describing one or more attributes of the event;

receiving a request to send a message to one of the network enabled devices associated with the common identifier;

determining a target type of interaction associated with the message to be sent based on the mobile event notifications associated with the common identifier retrieved from the event source repository;

selecting one of a plurality of channels based on the target type of interaction, a type of event associated with the message, or a preference associated with the common identifier, wherein at least two of the channels are configured to communicate information to one of the network enabled devices through a different communication protocol, communication protocols including at least a push notification protocol and a mail transfer protocol; and

transmit, using one of the communication protocols, a message through the selected channel to the one of the network enabled devices.

17. The method of claim 16, further comprising transmitting the message through a second selected channel to the one of the network enabled devices.

18. The method of claim 16, wherein a first message associated with a first type of event is transmitted through a first selected channel and a second message associated with a second type of event is transmitted through a second selected channel different from the first selected channel, a selection of channels is determined based on the type of event.

19. The method of claim 16, wherein at least some of the mobile event notifications stored are associated with historical user behaviors, and determining the target type of interaction associated with the message to be sent based on the mobile event notifications comprising determining the target type of interaction based on the historical user behaviors.

20. The method of claim 16, wherein the common identifier is associated with the preference specified by a user identified by the common identifier, the preference specifying a certain type of messages to be sent from a particular channel associated with a particular communication protocol.