# US 2019/0317972 A1 · Notifying entities of relevant events

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0317972 A1
- Document ID: US20190317972A1
- Status: Published application
- Kind: A1
- Application number: 16/353,212
- Filed: 2019-03-14
- Published: 2019-10-17
- Earliest claimed: 2018-04-13
- Assignees: Banjo, Inc.
- Applicants: Banjo, Inc.
- Inventors: Damien Patton; KW Justin Leung; Rish Mehta; Corey Hart
- Web page: https://patentgrep.com/patent/US20190317972A1

## CPC

- G06F 16/9535: Search customisation based on user profiles and personalisation
- G06F 16/9537: Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present invention extends to methods, systems, and computer program products for notifying entities of relevant events. An event feed containing a plurality of events is received. Each event includes an event location, an event category, an event an event truthfulness, an event severity, and an event time. Entity notification preferences defining events relevant to an entity are accessed. Location and distance preferences collectively define an interest in events within a specified distance of one or more locations. The time preferences define that event notification occur at least within a specified time period of event detection. For an event in the event feed, characteristics of the event are compared to the entity notification preferences. It is determined that the event satisfies the entity notification preferences based on the comparisons. The entity (or another entity) is notified of the event in compliance with the time preferences.

## Claims

### Claim 1

A method comprising:
receiving an event feed containing a plurality of events, each event detected from one or more Time, Location, Context (TLC) normalized signals derived from one or more raw signals, each event including (1) an event location, (2) an event category, (3) an event truthfulness, (4) an event severity, and (5) an event time, the event truthfulness comprising an indication of how likely the event is a valid event;
accessing entity notification preferences defining events relevant to an entity;
identifying from within the entity notification preferences: category preferences, location preferences, time preferences, and truth preferences, wherein the time preferences define that the entity desires to be notified of events with respective event times indicating that the event occurred within a defined time period;
for an event in the event feed, comparing characteristics of the event to the entity event preferences, including:
comparing the event time to the time preferences;
comparing the event location to the location preferences;
comparing the event category to the category preferences; and
comparing the event truthfulness to the truth preferences;
determining that the event satisfies each of the entity event preferences based on the comparisons; and
based on determining that the event satisfies each of the entity event preferences, notifying an electronic device of the event.

### Claim 2 (depends on 1)

The method of claim 1, wherein the time preferences further define the entity's desire to be notified of events detected in live time.

### Claim 3 (depends on 1)

The method of claim 1, wherein the time preferences define the entity's desire to be notified of events that occurred within a specific amount of time prior to a present time.

### Claim 4 (depends on 3)

The method of claim 3, wherein the specified time period is between 1 minute and 60 minutes since a present time.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
accessing location data corresponding to the entity;
determining a current location of the entity from the location data; and
wherein comparing the event location to the location preferences comprises comparing the event location to the current location of the entity.

### Claim 6 (depends on 5)

The method of claim 5, wherein notifying the electronic device comprises notifying another entity.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
accessing location data corresponding to the entity;
determining a probable future location of the entity from the location data; and
wherein comparing the event location to the location preferences comprises comparing the event location to the probable future location of the entity.

### Claim 8 (depends on 7)

The method of claim 7, wherein notifying the electronic device comprises notifying another entity.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
comparing characteristics of the event to characteristics of a plurality prior events;
identifying sufficient similarity between the event and one or more prior events from the plurality of prior events;
predicting an impact of the event based on impacts associated with the one or more prior events;
creating a second notification indicative of the predicted impacts; and
sending the second notification to the electronic device.

### Claim 10

A computer system comprising:
a processor;
system memory coupled to the processor and storing instructions configured to cause the processor to:
receive an event feed containing a plurality of events, each event detected from one or more Time, Location, Context (TLC) normalized signals derived from one or more raw signals, each event including an event location, an event category, an event truthfulness, an event severity, and an event time;
access entity notification preferences defining events relevant to an entity;
determining from the entity notification preferences a category preference, a location preference, a truthfulness preference, a severity preference, and a time preference, the time preference defining that the entity desires to be notified of events with respective event times indicating that the event occurred within a defined time period;
for an event in the event feed, compare characteristics of the event to the entity event preferences, including:
compare the event location to the location preferences in view of the distance preferences;
compare the event category to the category preferences;
compare the event truthfulness to the truth preferences; and
compare the event severity to the severity preferences;
determine that the event satisfies each of the entity event preferences based on the comparisons; and
based on determining that the event satisfies each of the entity event preferences, notify an electronic device of the event in compliance with the time preferences.

### Claim 11 (depends on 10)

The computer system of claim 10, wherein the time preferences define notifying the entity in live time; and
wherein instructions configured to cause the processor to notify an electronic device comprise instructions configured to cause the processor to notify the electronic device in live time.

### Claim 12 (depends on 10)

The computer system of claim 10, further comprising instructions configured to cause the processor to, prior to notifying the electronic device, wait for a time delay defined in the time preferences.

### Claim 13 (depends on 12)

The computer system of claim 12, wherein the time delay is between 1 minute and 60 minutes.

### Claim 14 (depends on 10)

The computer system of claim 10, further comprising instructions configured to cause the processor to:
access location data corresponding to the entity; and
determine a current location of the entity from the location data; and
wherein instructions configured to cause the processor to compare the event location to the location preferences in view of the distance preferences comprises instructions configured to cause the processor to compare the event location to the current location of the entity.

### Claim 15 (depends on 14)

The computer system of claim 14, wherein instructions configured to cause the processor to notify an electronic device comprises instructions configured to cause the processor to notify another entity.

### Claim 16 (depends on 10)

The computer system of claim 10, further comprising instructions configured to cause the processor to:
access location data corresponding to the entity; and
determine a probable future location of the entity from the location data; and
wherein instructions configured to cause the processor to compare the event location to the location preferences in view of the distance preferences comprise instructions configured to cause the processor to compare the event location to the probable future location of the entity.

### Claim 17 (depends on 16)

The computer system of claim 16, wherein instructions configured to cause the processor to notify an electronic device comprise instructions configured to cause the processor to notify another entity.

### Claim 18 (depends on 10)

The computer system of claim 10, further comprising instructions configured to cause the processor to:
compare characteristics of the event to characteristics of a plurality prior events;
identify sufficient similarity between the event and one or more prior events from the plurality of prior events;
predict an impact of the event based on impacts associated with the one or more prior events; and
create a second notification indicative of the predicted impacts; and
send the second notification to the electronic device.
