PATENT CLAIM ANALYSIS

Application Number: 16238782
Application Type: Utility
Filing Date: 2019-01
Publication Date: 2019-08
Patent Classification: ["370", "338000"]

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.

Claim (Index 17):
A computer system comprising:\n 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:\n acquire first planned event data including a first date, a first start time, a first end time, and a first location; \n acquire second planned event data including a second date, a second start time, a second end time, and a second location; \n 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; \n automatically resolve the identified inconsistency into consistent details of the actual planned event, including:\n identify a search term in one of: the first planned event data or the second planned event data; \n refer to a geo cell database to identify a geo cell associated with the search term; and \n use other information associated with the geo cell to resolve the inconsistency, including:\n query a venue database with the other information; and \n receive an indication of the venue from the venue database, the venue in a geographic area defined by the geo cell; and \n \n \n notify an entity of the actual planned event, the entity selected from among a person, a business entity, or a governmental entity.

Metadata:
- Claim Count in Document: 13.0
- Percentile: 99.0
- Lexical Diversity: 1.64516
- Patent Class: 370.0
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: False
- Related Applications: ['16121917', '16131637', '16203792', '16170325', '16038537']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.5612183451082752
- 35 USC 102 Novelty (BERT): 0.5760225652570009
- Combined Prediction Score: 0.5626987671231477
- Mean Citation Score: 302.864008
- Max Citation Score: 487.15308
- Similarity Product: 420.9121480015468

Labels:
- Claim Label 101: 1
- Claim Label 102: 1
- Claim Label 103: 1
- Claim Label 112: 1
- Combined Label: 1
- Label 101 Adjusted: 1

Dataset: test