Detecting and validating planned event information

• US 10,575,162 B1
• Filed: 06/27/2019
• Issued: 02/25/2020
• 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/455,010
• Publication Number:
  US 20200077247A1
• Time in Patent Office: 243 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 that includes a time, a signal type, a signal source, and source data;

reducing the dimensionality of the raw signal into a normalized signal that includes a Time dimension, a Location dimension, and a Context dimension, wherein the context dimension includes a probability value at least approximating a probability that the normalized signal indicates that a real-world event of a specified event type is occurring;

based on the normalized signal, including the at least approximated probability, detecting that the real-world event of the specified event type is a possible planned event occurring at a venue;

validating the possible planned event as an actual planned event based on validating data of the possible planned event with data from an event planning system associated with the venue; and

notifying an entity that the actual planned event is occurring.

2. The method of claim 1, wherein reducing 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, wherein validating the possible planned event as an actual planned event comprises validating the possible event as an actual planned event of the specified event type.

4. The method of claim 1, wherein detecting the 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 the possible planned event based on characteristics of the normalized signal comprises detecting a possible planned event based on the Context dimension.

7. The method of claim 1, wherein ingesting the raw signal comprises ingesting one of:

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

8. 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 of the raw signal into a normalized signal including a Time dimension, a Location dimension, and a Context dimension, wherein the context dimension includes a probability value at least approximating a probability that a real-world event of a specified event type is occurring;

based on characteristics of the normalized signal, including the at least approximated probability, detect that the real-world event of the specified event type is a possible planned event occurring at a venue;

validate the possible planned event as an actual planned event based on validating data of the possible planned event with data from an event planning system associated with the venue; and

notify an entity that the actual planned event is occurring.

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

10. The computer system of claim 8, 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.

11. The computer system of claim 8, 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.

12. The computer system of claim 8, 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.

13. 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 that includes a time, a signal type, a signal source, and source data;

reducing the dimensionality of the raw signal into a Time, Location, Context (TLC) normalized signal, wherein a context dimension within the TLC signal includes a probability value at least approximating a probability that the normalized signal indicates that a real-world event of a specified event type is occurring;

derive an event context for a possible planned event from characteristics of the 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;

identifying an inconsistency between a first start time and a second start time associated with the actual planned event; and

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

notify an entity of the actual planned event.

14. The computer system of claim 13, wherein the instructions configured to cause the processor to automatically resolve the identified inconsistency into consistent details of a planned event further 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.

15. The computer system of claim 13, wherein the instructions configured to cause the processor to normalize a raw signal into a TLC normalized signal further comprise instructions configured to cause the processor to normalize one of:

a social signal, a web signal, or a streaming signal into a TLC normalized signal.

16. The computer system of claim 13, wherein the instructions configured to cause the processor to identify an inconsistency between the first start time and the second start time comprises further instructions configured to cause the processor to compare at least one of:

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

17. The method of claim 13, wherein normalizing the raw signal into a TLC normalized signal comprises normalizing one of:

a social signal, a web signal, or a streaming signal into the TLC normalized signal.

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

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

giving preference to the first planned event data.