PATENT CLAIM ANALYSIS

Application Number: 16109106
Application Type: Utility
Filing Date: 2018-08
Publication Date: 2020-02
Patent Classification: ["null", "null"]

Abstract:
Described is a system (and method) that provides a framework for performing data transformations, which may be part of an Extract, Transform, and Load (ETL) process. The system may perform a data transformation by creating a pipeline that executes a set of independent software components (or component, plugins, add-ons, etc.). The components may be executed as individual services (e.g., microservices) that may be provided within containers to allow the components to be deployed as self-contained units on various types of host systems including cloud-based infrastructures. In addition, to provide further flexibility for the framework, the components may be implemented using preexisting software libraries.

Claim (Index 1):
A method for transforming data from a source data store for loading onto a target data store, the method comprising:\n obtaining a transformation graph of a set of components, each component executable as an independent service and performing a predefined operation, the transformation graph representing one or more sequences of operations to transform data from one or more source data stores to a format for updating the target data store, wherein the data from the one or more source data stores corresponds to one or more accounts during a current day and a previous day; initiating an execution of the set of components based on the transformation graph, each component executing as a separate process, wherein the execution of the set of components includes executing:\n a first source component that performs operations including:\n reading the data associated with the current day from a first of the one or more source data stores; and \n converting the data associated with the current day to a first table data structure; \n \n a second source component that performs operations including:\n reading data from a second of the one or more source data stores; and \n converting the data to a second table data structure; and \n \n a third source component that performs operations including:\n reading the data associated with the previous day from a third of the one or more source data stores; and \n converting the data associated with the previous day to a third table data structure; \n \n one or more transformation components that perform operations including:\n transforming the data of the first table data structure as part of a first sequence of transformation operations; \n transforming the data of the second table data structure as part of a second sequence of transformation operations; and \n transforming the data of the third data table structure as part of a third sequence of transformation operations, wherein the third sequence of transformation operations comprises:\n identifying updated data based upon a comparison of the data associated with the current day and the data associated with the previous day; \n combining the updated data with data corresponding to one or more new accounts to produce combined data; and \n joining the combined data with a copy of the data of the third table data structure to produce joined data; and \n \n \n one or more target components that perform operations including:\n writing one or more output files for updating the target data store, wherein the one or more output files comprise: \n a first output file, based at least partially upon the updated data, that includes an updated list of the one or more accounts that is synchronized with changes to the one or more accounts within or between the previous day and the current day; and \n a second output file, based at least partially upon the joined data, that includes the changes that occur within or between the previous day and the current day to the one or more accounts; and \n \n initiating a loading of the one or more output files to the target data store.

Metadata:
- Claim Count in Document: 41.0
- Percentile: 96.0
- Lexical Diversity: 1.63158
- Patent Class: nan
- Transitional Phrase Type: open
- Component Type: 1
- Foreign Priority: False
- Related Applications: ['10465222', '15614608', '10118667', '14846919', '14051390']

Analysis Scores:
- 35 USC 101 Eligibility (BERT): 0.4730145109689674
- 35 USC 102 Novelty (BERT): 0.4572731070237561
- Combined Prediction Score: 0.4714403705744463
- Mean Citation Score: 100.9875342
- Max Citation Score: 103.695656
- Similarity Product: 74.44412900032806

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

Dataset: test