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 10):
An apparatus comprising:\n a) a data store manager running on a computer for receiving performance metric data on a plurality of performance attributes of a plurality of resource types being monitored, and converting each performance metric number to a Unicode text character, and storing said Unicode in a non relational database file system, and for receiving a plurality configuration attributes of said plurality of resource types, and storing said configuration attributes in said non relational database; 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 attribute of said first resource type and a regular expression defining a first filter criteria; receiving a resource addition syntax block and a second resource type which is to be recognized as a related resource type of said first resource type; parsing the search query and finding said first resource type, and making a request for all the data for the first attribute of all instances of the first resource type; creating a thread pool to process each instance of said first resource type; applying the first filter criteria to all said threads, and if said first filter criteria has a number in it, converting that number to Unicode before applying said first filter criteria, and if any thread meets said first filter criteria, determining if there are any subpaths from said first resource type to a related resource type and determining there is not; for all threads which qualify under said first filter criteria, searching during said relevant interval for any second resource type that has been added; and determining if any instance of said first resource type passed said first filter criteria and has an instance said second related resource type added during said relevant interval, and if so, presenting the instance of said first resource type that qualified as output.

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.3462663115506706
- 35 USC 102 Novelty (BERT): 0.5353877835370117
- Combined Prediction Score: 0.3651784587493047
- Mean Citation Score: 385.287312
- Max Citation Score: 396.23264
- Similarity Product: 330.1779171128464

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