IP Library Granted Patent US 10,049,378
Granted Patent B1
US 10,049,378 · App. 15/161,154 · Granted Aug 14, 2018

Push reporting

Inventors: Gary Todd Johnson (Portland, OR); Erik A. Onnen (Portland, OR); Dave K. Revell (Portland, OR); Jeffrey A. Towle (Portland, OR); Nathan A. Putnam (Lake Oswego, OR)
Assignee: Urban Airship, Inc.
G06Q30/0242G06Q30/0267G06Q30/0276H04L67/26H04W88/02
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,049,378
App. No.
15/161,154
Granted
Aug 14, 2018
Kind
B1
Abstract

Push reporting is disclosed. A first payload comprising feature reporting information and meta information is received from a first device at a first time. A second payload comprising feature reporting information and meta information is received from a second device at a second time. At respective third and fourth times, respective third and fourth payloads are received from the first and second devices, respectively. The third and fourth payloads include additional feature reporting information and meta information. The processing of the information received from the first and second devices is coordinated. A request for information is received. Metrics are provided as output. The metrics are based at least in part on the processing of the information received from the first and second devices.

Claims (65)

1. A system, comprising:

an interface configured to:

receive, from a device, information associated with push notifications delivered to the device;

a processing engine configured to:

coordinate processing of at least a portion of the information received from the device, and

determine a location of interest for a user associated with the device; and

a reporting engine configured to:

receive a request for information indicating influence of the delivered push notifications; and

responsive to the request for information, provide metrics as output, wherein the metrics indicate influence of the delivered push notifications and include measures of user responses to received instances of the push notifications on the device, the metrics based at least in part on the processing of the information received from the device.

2. The system of claim 1 , wherein the processing engine is further configured to extract features from the received information.

3. The system of claim 2 , wherein the processing engine is further configured to increment counters associated with the extracted features.

4. The system of claim 1 , wherein the processing engine is further configured to construct user timelines.

5. A method, comprising:

receiving, from a device, information associated with push notifications delivered to the device;

coordinating processing of at least a portion of the information received from the device;

determining a location of interest for a user associated with the device;

receiving a request for information indicating influence of the delivered push notifications; and

responsive to the request for information, providing metrics as output, wherein the metrics indicate influence of the delivered push notifications and include measures of user responses to received instances of the push notifications on the device, the metrics based at least in part on the processing of the information received from the device.

6. The method of claim 5 , further comprising extracting features from the received information.

7. The method of claim 6 , further comprising incrementing counters associated with the extracted features.

8. The method of claim 5 , further comprising constructing user timelines.

9. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions that when executed by processor causes the processor to:

receive from a device, information associated with push notifications delivered to the device;

coordinate processing of at least a portion of the information received from the device;

determine a location of interest for a user associated with the device;

receive a request for information indicating influence of the delivered push notifications; and

provide for output metrics in response to the request for information, the metrics indicative of influence of the delivered push notifications and inclusive of measures of user responses to received instances of the push notifications on the device, the metrics based at least in part on the processing of the information received from the device.

10. The non-transitory computer readable storage medium of claim 9 , further comprising extracting features from the received information.

11. The non-transitory computer readable storage medium of claim 10 , further comprising incrementing counters associated with the extracted features.

12. The non-transitory computer readable storage medium of claim 9 , further comprising constructing user timelines.

13. A system comprising:

a processor; and

a memory comprising stored instructions, the instruction when executed causes the processor to:

receive, from a device, information associated with push notifications delivered to the device;

coordinate, processing of at least a portion of the information received from the device;

determine a location of interest for a user associated with the device;

receive, a request for information indicating influence of the delivered push notifications; and

provide for output metrics in response to the request for information, the metrics indicative of influence of the delivered push notifications and inclusive of measures of user responses to received instances of the push notifications on the device, the metrics based at least in part on the processing of the information received from the device.

14. The system of claim 13 , wherein the memory further comprises stored instructions that when executed cause the processor to extract features from the received information.

15. The system of claim 14 , wherein the memory further comprises stored instructions that when executed cause the processor to increment counters associated with the extracted features.

16. The system of claim 13 , wherein the memory further comprises stored instructions that when executed cause the processor to construct user timelines.

17. A system, comprising:

an interface configured to:

receive, from a device, information associated with push notifications delivered to the device;

a processing engine configured to:

coordinate processing of at least a portion of the information received from the device,

extract features from the received information, and

increment counters associated with the extracted features; and

a reporting engine configured to:

receive a request for information indicating influence of the delivered push notifications; and

responsive to the request for information, provide metrics as output, wherein the metrics indicate influence of the delivered push notifications and include measures of user responses to received instances of the push notifications on the device, the metrics based at least in part on the processing of the information received from the device.

18. The system of claim 17 , wherein the processing engine is further configured to determine a location of interest for a user associated with the device.

19. The system of claim 17 , wherein the processing engine is further configured to construct user timelines.

20. A system, comprising:

an interface configured to:

receive, from a device, information associated with push notifications delivered to the device;

a processing engine configured to:

coordinate processing of at least a portion of the information received from the device, and

construct user timelines; and

a reporting engine configured to:

receive a request for information indicating influence of the delivered push notifications; and

provide, responsive to the request for information, metrics as output, the metrics indicative of influence of the delivered push notifications and include measures of user responses to received instances of the push notifications on the device, the metrics based at least in part on the processing of the information received from the device.

21. The system of claim 20 , wherein the processing engine is further configured to extract features from the received information.

22. The system of claim 21 , wherein the processing engine is further configured to increment counters associated with the extracted features.

23. The system of claim 20 , wherein the processing engine is further configured to determine a location of interest for a user associated with the device.

Assignments (9)
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: SILVER LAKE WATERMAN FUND, L.P.
To: URBAN AIRSHIP, INC.; TELLO, INC.
Reel/Frame 052300/0284 →
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2020
From: SILICON VALLEY BANK
To: URBAN AIRSHIP, INC.
Reel/Frame 052300/0425 →
SECURITY INTEREST Recorded Jun 28, 2019
From: URBAN AIRSHIP, INC.
To: SILICON VALLEY BANK
Reel/Frame 049627/0826 →
SECOND SUPPLEMENT TO INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 29, 2018
From: URBAN AIRSHIP, INC.; TELLO, INC.
To: SILVER LAKE WATERMAN FUND, L.P., AS AGENT
Reel/Frame 047347/0278 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2016
From: JOHNSON, GARY TODD; ONNEN, ERIK A.; REVELL, DAVE K.; TOWLE, JEFFREY A.; PUTNAM, NATHAN A.
To: URBAN AIRSHIP, INC.
Reel/Frame 038709/0097 →
Continuity (2)
Continuation 13763541 · Feb 8, 2013
Provisional Application 61598290 · Feb 13, 2012