IP Library Granted Patent US 10,200,486
Granted Patent B2
US 10,200,486 · App. 15/202,397 · Granted Feb 5, 2019

Mobile event notifications for network enabled objects

Inventors: Michael James Herrick (Portland, OR); Adam C. Lowry (Portland, OR); Cory David Hoffman Kolbeck (Portland, OR); Michael Shane Robert McHugh (Portland, OR)
Assignee: Urban Airship, Inc.
H04L67/26H04L63/10H04L65/1069H04L67/02H04L67/146H04L67/32H04L67/327
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 10,200,486
App. No.
15/202,397
Granted
Feb 5, 2019
Kind
B2
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 (46)

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.

Assignments (7)
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 →
SECURITY INTEREST Recorded Apr 2, 2020
From: URBAN AIRSHIP, INC.; APPTIMIZE, LLC
To: WELLS FARGO BANK, NATIONAL ASSOCIATION
Reel/Frame 052308/0550 →
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2020
From: SILICON VALLEY BANK
To: URBAN AIRSHIP, INC.
Reel/Frame 052300/0425 →
SECURITY INTEREST Recorded Jul 7, 2017
From: URBAN AIRSHIP, INC.
To: SILICON VALLEY BANK
Reel/Frame 042932/0593 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 27, 2016
From: HERRICK, MICHAEL JAMES; LOWRY, ADAM C.; KOLBECK, CORY DAVID HOFFMAN; MCHUGH, MICHAEL SHANE ROBERT
To: URBAN AIRSHIP, INC.
Reel/Frame 039869/0663 →
Continuity (6)
Continuation In Part 15055474 · Feb 26, 2016
Provisional Application 62188432 · Jul 2, 2015
Provisional Application 62138904 · Mar 26, 2015
Provisional Application 62121228 · Feb 26, 2015
Provisional Application 62121280 · Feb 26, 2015
Related Publication 20160316034A1 · Oct 27, 2016
Cited By (6)
US 12,255,860 US 12,335,205 US 12,335,216 US 12,379,903 US 12,425,474 US 12,639,049