IP Library Granted Patent US 10,701,183
Granted Patent B2
US 10,701,183 · App. 16/195,612 · Granted Jun 30, 2020

Configuring a computing device to automatically obtain data in response to a predetermined event

Inventors: David Richardson (San Francisco, CA); Kevin Patrick Mahaffey (San Francisco, CA); Jonathan Grubb (Los Angeles, CA)
Assignee: Lookout, Inc.
H04L67/34G06F8/61H04L43/10H04L67/16H04L67/18H04W4/029H04W4/60H04W8/18H04W12/0023H04W12/0802H04W12/12H04W4/80
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,701,183
App. No.
16/195,612
Granted
Jun 30, 2020
Kind
B2
Abstract

An operating system of a computing device is configured to monitor for occurrence of an event. In response to determining that the event has occurred, data associated with the event is obtained from the computing device. An address associated with an account of the computing device is determined, and the data associated with the event is sent to the address.

Claims (44)

1. A method, comprising:

configuring an operating system of a first computing device to monitor for occurrence of at least one of a plurality of predetermined events, wherein each of the predetermined events is registered by an application of the first computing device;

determining that a first event of the predetermined events has occurred, the first event including a network connectivity change;

in response to determining that the first event has occurred, obtaining first data associated with the network connectivity change from the first computing device;

providing the obtained first data to the application;

determining, by the application, an address associated with a first account of the first computing device; and

sending the first data to the address.

2. The method of claim 1 , wherein the first data includes data regarding a location of the first computing device.

3. The method of claim 1 , wherein the first computing device is associated with a user, and the address corresponds to a second computing device of the user.

4. The method of claim 1 , wherein the first event further includes receiving a message.

5. The method of claim 1 , further comprising starting the application in response to occurrence of the first event.

6. The method of claim 5 , wherein the application, after starting, locates a position of the first computing device, and wherein sending the first data comprises sending a message to a second computing device, the message including the position.

7. The method of claim 1 , wherein the first event further includes at least one of an installation referrer callback, receiving a message, a timer event, or activation of an input device by a user.

8. The method of claim 1 , wherein sending the first data comprises sending a message including the first data, and wherein the message further includes a link.

9. The method of claim 8 , wherein the message is sent to a second computing device, and the link is configured to connect the second computing device to a third computing device.

10. The method of claim 1 , wherein the first account is associated with a user, the method further comprising using the address to create a second account associated with the user.

11. The method of claim 10 , further comprising, in response to creating the second account, sending authentication credentials for the second account to a computing device associated with the user.

12. The method of claim 1 , further comprising, in response to determining that the first event has occurred, locking user access to the first computing device other than by use of authorized user credentials.

13. A system, comprising:

at least one processor; and

memory storing instructions configured to instruct the at least one processor to:

configure a first computing device to monitor for at least one of a plurality of predetermined events;

determine that a first event of the predetermined events has occurred, the first event including a network connectivity change;

in response to determining that the first event has occurred, obtain data from the first computing device;

determine, by an application, an address associated with a first account of the first computing device; and

send the obtained data to the address.

14. The system of claim 13 , wherein each of the predetermined events is registered by the application, and wherein the obtained data is provided to the application.

15. The system of claim 13 , wherein the obtained data is sent to a second computing device, wherein the instructions are further configured to instruct the at least one processor to send a link to the second computing device, and wherein the link is configured to connect the second computing device to a third computing device.

16. The system of claim 13 , wherein the first event further includes receipt of a message sent by an authorized user of the first computing device.

17. The system of claim 13 , wherein the first account is associated with a user, and the instructions are further configured to instruct the at least one processor to:

use the address to create a second account associated with the user; and

in response to creating the second account, send authentication credentials for the second account to a second computing device associated with the user.

18. A non-transitory storage medium storing computer-readable instructions, which when executed, cause a computing device to:

configure the computing device to monitor for occurrence of at least one of a plurality of predetermined events, wherein each of the predetermined events is registered by an application of the computing device;

determine that a first event of the predetermined events has occurred, the first event including a network connectivity change;

in response to determining that the first event has occurred, obtain data from the computing device;

determine an address associated with a first account of the computing device; and

send the obtained data to the address.

19. The non-transitory storage medium of claim 18 , wherein:

sending the obtained data comprises sending a position of the computing device; and

the first event further includes activation of an input device by a user.

20. The non-transitory storage medium of claim 18 , wherein the computing device is a first computing device, the first account is associated with a user, the obtained data is sent to a second computing device, and the second computing device is configured to create, using the address, a second account associated with the user.

21. The non-transitory storage medium of claim 18 , wherein the first event further includes receiving a message.

22. The non-transitory storage medium of claim 18 , wherein sending the obtained data comprises sending a message including the obtained data and a link.

Assignments (8)
SECURITY INTEREST Recorded Oct 7, 2025
From: LOOKOUT, INC.
To: MIDCAP FINANCIAL TRUST
Reel/Frame 073028/0189 →
SECURITY INTEREST Recorded Oct 2, 2025
From: LOOKOUT, INC.
To: CRESCENT COVE OPPORTUNITY LENDING, LLC, AS AGENT
Reel/Frame 072989/0675 →
SECURITY INTEREST Recorded Aug 10, 2024
From: LOOKOUT, INC.
To: MIDCAP FINANCIAL TRUST
Reel/Frame 068538/0177 →
RELEASE OF PATENT SECURITY INTEREST AT REEL 59909 AND FRAME 0764 Recorded Jun 2, 2023
From: ALTER DOMUS (US) LLC, AS ADMINISTRATIVE AGENT
To: LOOKOUT, INC.
Reel/Frame 063844/0638 →
RELEASE OF SECURITY INTEREST Recorded May 9, 2022
From: SILICON VALLEY BANK (THE "BANK")
To: LOOKOUT, INC.
Reel/Frame 059909/0668 →
SECURITY INTEREST Recorded May 9, 2022
From: LOOKOUT, INC.
To: ALTER DOMUS (US) LLC
Reel/Frame 059909/0764 →
SECURITY INTEREST Recorded Feb 18, 2020
From: LOOKOUT, INC.
To: SILICON VALLEY BANK
Reel/Frame 051966/0282 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 6, 2019
From: RICHARDSON, DAVID; MAHAFFEY, KEVIN; GRUBB, JONATHAN
To: LOOKOUT, INC.
Reel/Frame 050298/0814 →
Continuity (5)
Continuation 15049620 · Feb 22, 2016
Continuation 14553832 · Nov 25, 2014
Continuation 13403927 · Feb 23, 2012
Provisional Application 61445957 · Feb 23, 2011
Related Publication 20190089815A1 · Mar 21, 2019