Mobile event notifications for network enabled objects

• US 10,200,486 B2
• Filed: 07/05/2016
• Issued: 02/05/2019
• 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:
  US15/202,397
• Publication Number:
  US 20160316034A1
• Time in Patent Office: 945 Days
• Field of Search: 709220, 709224, 709228
• 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 method for delivering mobile event streams the method comprising:

receiving, by an online system for mobile event streaming, a request from a customer device to create a channel, the channel comprising one or more communications and a data channel between type of Internet of Things (IoT) device and the online system;

identifying one or more IoT devices associated with the received type of IoT device wherein the one or more IoT devices correspond to a defined a segment of a user population;

creating, by the online system, a channel between the one or more IoT devices and the online system;

associating, by the online system, the one or more IoT devices with the created channel;

transmitting by the online system, a notification directly to the segment of the user population associated with the type of IoT device; and

receiving, by the online system, directly from the one or more IoT devices via the created channel, a mobile event notification.

2. The method of claim 1, wherein receiving the request to create a channel further comprises defining at least a Named User, a channelID, a deviceType.

3. The method of claim 1, wherein creating the channel further comprises defining a device type associated with the channel, the device type comprising at least one of a user device and an IoT device.

4. The method of claim 1, wherein transmitting the notification comprises determining a type of interaction associated with the sent notification, the type of interaction including at least one of a group consisting of a visual interaction, a textual interaction, and an audio interaction.

5. The method of claim 1, further comprising filtering the stored message based on a filter parameter, the filter parameter comprising at least one of an identifier and a destination.

6. The method of claim 1, wherein transmitting a notification further comprises:

receiving a request to generate a message;

responsive to the received request, generating a message;

storing the generated message; and

transmitting the generated message to one or more user devices and IoT devices.

7. The method of claim 6, wherein responsive to the received request further comprises generating the message automatically.

8. The method of claim 6, wherein storing the generated message further comprises storing one or more previously generated messages.

9. The method of claim 6, wherein transmitting the generated message further comprises:

maintaining a history of previously transmitted messages; and

scheduling generated messages for transmittal to one or more IoT devices at a later time.

10. The method of claim 6, wherein the generated message further includes instructions to perform an action associated with the IoT device.

11. A system for receiving, processing, and delivering mobile event streams comprising:

a processor configured to; and

receive, by an online system for mobile event streaming, a request from a customer device to create a channel, the channel comprising one or more communication and data channel between an Internet of Things (IoT) device and the online system;

identify one or more IoT devices associated with the received type of IoT device wherein the one or more IoT devices define correspond to a defined a segment of a user population;

create by the online system, a channel between the one or more IoT devices and the;

associate, by the online system, the one or more IoT devices with the created channel;

transmit, by the online system, a notification directly to the segment of the user population associated with the type of IoT device associated with the created channel;

receive, by the online system, directly from the one or more IoT devices via the created channel, a mobile event notification; and

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

12. The system of claim 11, wherein receiving the request to create a channel further comprises defining at least a Named User, a channelID, a deviceType.

13. The system of claim 11, wherein creating the channel further comprises defining a device type associated with the channel, the device type comprising at least one of a user device and an IoT device.

14. The system of claim 11, wherein transmitting the notification comprises determining a type of interaction associated with the sent notification, the type of interaction including at least one of a group consisting of a visual interaction, a textual interaction, and an audio interaction.

15. The system of claim 11, further comprising filtering the stored message based on a filter parameter, the filter parameter comprising at least one of an identifier and a destination.

16. The system of claim 11, wherein transmitting a notification further comprises:

receiving a request to generate a message;

responsive to the received request, generating a message;

storing the generated message; and

transmitting the generated message to one or more user devices and IoT devices.

17. The system of claim 16, wherein responsive to the received request further comprises generating the message automatically.

18. The system of claim 16, wherein storing the generated message further comprises storing one or more previously generated messages.

19. The system of claim 16, wherein transmitting the generated message further comprises:

maintaining a history of previously transmitted messages; and

scheduling generated messages for transmittal to one or more IoT devices at a later time.

20. The system of claim 16, wherein the generated message further includes instructions to perform an action associated with the IoT device.