PATENT CLAIM ANALYSIS

Application Number: 15974522
Application Type: Utility
Filing Date: 2018-05
Publication Date: 2019-05
Patent Classification: ["709", "224000"]

Abstract:
A system to collect and store in a special data structure arranged for rapid searching massive amounts of data. Performance metric data is one example. The performance metric data is recorded in time-series measurements, converted into unicode, and arranged into a special data structure having one directory for every day which stores all the metric data collected that day. The performance metric data is collected by one or more probes running on machines about which data is being collected. The performance metric data is compressed prior to transmission to a server over any data path. The data structure at the server where analysis is done has a subdirectory for every resource type. Each subdirectory contains text files of performance metric data values measured for attributes in a group of attributes to which said text file is dedicated. Each attribute has its own section and the performance metric data values are recorded in time series as unicode hex numbers as a comma delimited list. Analysis of the performance metric data is done using regular expressions. For speed, cache memory is used. Performance metric data outside the start time and end time named by the user on a query screen is eliminated before the regular expression is applied.

Claim (Index 16):
An apparatus for searching large amounts of performance metric data using regular expressions, comprising:\n a) a data store manager running on a computer for receiving performance metric numbers collected in strings from a plurality of performance attributes of a plurality of resource types, converting each string of performance metric numbers to a string of Unicode text characters and storing each Unicode string in a flat file of a non relational database file system, and receives a plurality of configuration data from a plurality of configuration attributes of a plurality of resource types and stores in a separate place in said NRDB, and wherein said data store manager receives a plurality of event data from a plurality of resources types and stores in said NRDB; b) a query request processor and a NRDB access manager running on a computer for performing the following steps: receiving a start and stop time request and syntax blocks defining a first resource type, a first configuration attribute and a first regular expression defining a first filter criteria on said first configuration attribute, a syntax block defining an event filter, a syntax block defining a first performance attribute of said first resource type and a second regular expression defining a second filter criteria on said first performance attribute, and a syntax block defining an addition to said first resource type and a syntax block defining a second resource type to be added; parsing the search query and making a request for the all specified first configuration attribute and all the first performance attribute data of the first resource type; making a thread pool with one thread to process every instance of said first resource type; applying said first filter criterion to every thread for a first resource type, and determining which, if any, of said threads qualify with configuration data that matches said first filter criteria, then applying said event filter to the threads that qualified said first filter criteria and determining which, if any, thread qualified said event filter, and then applying said second filter criteria to the performance metric data of the threads which qualify said configuration filter and said event filter, and if said second filter criterion involves any numbers, converting said numbers to Unicode before applying said second filter criterion; if any thread has its performance attribute data meet said second filter criterion, determining if there is a subpath to a subresource; if no subpath, searching each thread which qualified for addition of a second resource type; proceeding to output said all said first resource types whose data passed all filter criteria along with the data which qualified.

Metadata:
- Claim Count in Document: 14.0
- Percentile: 93.0
- Lexical Diversity: 1.98198
- Patent Class: 709.0
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: False
- Related Applications: ['15376629', '15829697', '15425094', '14806550', '13200995']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.3470650143036941
- 35 USC 102 Novelty (BERT): 0.5343489532385165
- Combined Prediction Score: 0.3657934081971763
- Mean Citation Score: 385.287312
- Max Citation Score: 396.23264
- Similarity Product: 308.2864695926285

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

Dataset: test