Detecting and validating planned event information

• US 10,382,938 B1
• Filed: 01/03/2019
• Issued: 08/13/2019
• Est. Priority Date: 02/09/2018
• Status: Expired due to Fees

• Current Assignee: Banjo, Inc.
• Original Assignee: Banjo, Inc.
• Inventors: Patton, Damien, Newman, Joshua J., Bruckhaus, Tilmann
• Primary Examiner(s): Butt, Walli Z
• Application Number:
  US16/238,782
• Publication Number:
  US 20190253860A1
• Time in Patent Office: 222 Days
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06N 20/00 Machine learning
• CPC Class Codes: G06N 7/01 Probabilistic graphical models, e.g. probabilistic networks
• CPC Class Codes: G06V 10/32 Normalisation of the pattern dimensions
• CPC Class Codes: G06V 20/13 Satellite images
• CPC Class Codes: G06V 20/44 Event detection
• CPC Class Codes: G06V 20/54 of traffic, e.g. cars on the road, trains or boats
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/90 Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]

Abstract

The present invention extends to methods, systems, and computer program products for detecting and validating planned event information. A plurality of normalized signals is accessed. Planned event data across the plurality of normalized signals is checked for inconsistencies. Any inconsistencies are resolved in an automated fashion, for example, through reference to databases containing additional information. A planned event can be detected/validated from concurring and/or resolved planned event data. A validator can refer to an event history database and/or a planning system to validate a possible planned event as an actual planned event.

Claims

1. A method comprising:

ingesting a raw signal including a time stamp, an indication of a signal type, an indication of a signal source, and source data;

applying a transform to re-code the source data and reduce the dimensionality of the raw signal into a Time, Location, Context (TLC) normalized signal including a Time dimension, a Location dimension, and Context dimension;

detecting a possible planned event at a venue based on characteristics of the Time, Location, Context (TLC) normalized signal;

validating the possible planned event as an actual planned event starting at an event start time based on validating data from an event planning system associated with the venue;

forming a polygon listening area around the venue;

initiating signal listening in the listening area at a specified time prior to the event start time;

computing a signal volume of additional ingested signals originating in the listening area and related to the planned event;

validating that the actual planned event is occurring based at least in part on the computed signal volume; and

notifying an entity that the actual planned event is occurring, the entity selected from among a person, a business entity, or a governmental entity.

2. The method of claim 1, wherein applying a transform to re-code the source data and reduce the dimensionality of the raw signal comprises applying a transform to re-code the source data and reduce the dimensionality of the raw signal, the raw signal selected from among:

a social post with geographic content, an image from a traffic camera feed, a 911 call, weather data, IoT device data, satellite data, satellite imagery, a sound clip from a listening device, data from air quality sensors, a sound clip from radio communication, crowd sourced traffic information, or crowd sourced road information.

3. The method of claim 1, further comprising classifying the possible planned event in an event category.

4. The method of claim 1, wherein detecting a possible planned event at a venue comprises deriving the venue through reference to an event history database.

5. The method of claim 4, wherein deriving the venue through reference to an event history database comprises deriving the venue of through reference to a geo cell database.

6. The method of claim 1, wherein detecting a possible planned event based on characteristics of the Time, Location, Context (TLC) normalized signal comprises detecting a possible planned event based on the Context dimension.

14. The method of claim 1, wherein ingesting a raw signal comprises ingesting one of:

a social signal, a web signal, or a streaming signal.

7. A computer system comprising:

a processor;

system memory coupled to the processor and storing instructions configured to cause the processor to;

ingest a raw signal including a time stamp, an indication of a signal type, an indication of a signal source, and source data;

apply a transform to re-code the source data and reduce the dimensionality of the raw signal into a Time, Location, Context (TLC) normalized signal including a Time dimension, a Location dimension, and Context dimension;

detect a possible planned event at a venue based on characteristics of the Time, Location, Context (TLC) normalized signal;

validate the possible planned event as an actual planned event starting at an event start time based on validating data from an event planning system associated with the venue;

form a polygon listening area around the venue;

initiate signal listening in the listening area at a specified time prior to the event start time;

compute a signal volume of additional ingested signals originating in the listening area and related to the planned event;

validate that the actual planned event is occurring based at least in part on the computed signal volume; and

notify an entity that the actual planned event is occurring, the entity selected from among a person, a business entity, or a governmental entity.

8. The computer system of claim 7, further comprising instructions configured to cause the processor to classify the possible planned event in an event category.

9. The computer system of claim 7, wherein instructions configured to cause the processor to detect a possible planned event at a venue comprise instructions configured to cause the processor to derive the venue through reference to an event history database.

15. The computer system of claim 7, wherein instructions configured to cause the processor to ingest a raw signal comprise instructions configured to cause the processor to ingest one of:

a social signal, a web signal, or a streaming signal.

16. The computer system of claim 7, wherein instructions configured to cause the processor to ingest a raw signal comprise instructions configured to cause the processor to extract information from an Internet site.

10. A method comprising:

normalizing a raw signal into a Time, Location, Context (TLC) normalized signal including applying a transform to re-code source data contained in the raw signal and to reduce the dimensionality of the raw signal into a Time dimension, a Location dimension, and Context dimension;

deriving an event context for a possible planned event from characteristics of the Time, Location, Context (TLC) normalized signal and an event history of one or more events previously detected at a venue;

validating the possible planned event as an actual planned event based on the event context, including;

acquiring first planned event data including a first date, a first start time, a first end time, and a first location;

acquiring second planned event data including a second date, a second start time, a second end time, and a second location;

identifying an inconsistency between at least one of;

the first date and the second date, the first start time and the second start time, the first end time and the second end time, or the first location and the second location;

automatically resolving the identified inconsistency into consistent details of the actual planned event, including;

identifying a search term in one of;

the first planned event data or the second planned event data;

referring to a geo cell database to identify a geo cell associated with the search term; and

using other information associated with the geo cell to resolve the inconsistency, including;

querying a venue database with the other information; and

receiving an indication of the venue from the venue database, the venue in a geographic area defined by the geo cell; and

notifying an entity of the actual planned event, the entity selected from among a person, a business entity, or a governmental entity.

11. The method of claim 10, wherein automatically resolving the identified inconsistency into consistent details of a planned event comprises using one or more of:

machine learning, artificial intelligence, or neural networks to resolve the inconsistency into the consistent details.

17. The method of claim 10, wherein normalizing a raw signal into a Time, Location, Context (TLC) normalized signal comprises normalizing one of:

a social signal, a web signal, or a streaming signal into a Time, Location, Context (TLC) normalized signal.

18. The method of claim 10, wherein automatically resolving the identified inconsistency comprises:

determining that the first planned event data is more relevant based on a planning system the first event data was acquired from; and

giving preference to the first planned event data.

12. A computer system comprising:

a processor;

system memory coupled to the processor and storing instructions configured to cause the processor to;

normalize a raw signal into a Time, Location, Context (TLC) normalized signal including applying a transform to re-code source data contained in the raw signal and to reduce the dimensionality of the raw signal into a Time dimension, a Location dimension, and Context dimension;

derive an event context for a possible planned event from characteristics of the Time, Location, Context (TLC) normalized signal and an event history of one or more events previously detected at a venue;

validate the possible planned event as an actual planned event based on the event context, including;

acquire first planned event data including a first date, a first start time, a first end time, and a first location;

acquire second planned event data including a second date, a second start time, a second end time, and a second location;

identify an inconsistency between at least one of;

the first date and the second date, the first start time and the second start time, the first end time and the second end time, or the first location and the second location;

automatically resolve the identified inconsistency into consistent details of the actual planned event, including;

identify a search term in one of;

the first planned event data or the second planned event data;

refer to a geo cell database to identify a geo cell associated with the search term; and

use other information associated with the geo cell to resolve the inconsistency, including;

query a venue database with the other information; and

receive an indication of the venue from the venue database, the venue in a geographic area defined by the geo cell; and

notify an entity of the actual planned event, the entity selected from among a person, a business entity, or a governmental entity.

13. The computer system of claim 12, wherein instructions configured to cause the processor to automatically resolve the identified inconsistency into consistent details of a planned event comprise instructions configured to cause the processor to use one or more of:

machine learning, artificial intelligence, or neural networks to resolve the inconsistency into the consistent details.

19. The computer system of claim 12, wherein instructions configured to cause the processor to normalize a raw signal into a Time, Location, Context (TLC) normalized signal comprise instructions configured to cause the processor to normalize one of:

a social signal, a web signal, or a streaming signal into a Time, Location, Context (TLC) normalized signal.

20. The computer system of claim 12, wherein instructions configured to cause the processor to identify an inconsistency between at least one of:

the first date and the second date, the first start time and the second start time, the first end time and the second end time, or the first location and the second location comprise instructions configured to cause the processor to compare at least one of;

(a) the first date and the second date, (b) the first start time and the second start time, (c) the first end time and the second end time, or (d) the first location and the second location.