Patent No. US11379416 (titled "Systems And Methods For Common Data Ingestion") was filed by Jpmorgan Chase Bank Na on Mar 15, 2017.
’416 is related to the field of data processing, specifically addressing the challenge of efficiently ingesting data from diverse sources into a unified system. Organizations grapple with the complexity and cost of handling data that arrives in various formats and structures. The patent aims to streamline this process, reducing both monetary expenses and the man-hours required for data integration.
The underlying idea behind ’416 is to create a standardized data ingestion pipeline that automates the process of receiving, transforming, and storing data. This involves registering projects and their associated data, then using file-watcher threads to monitor a common drop zone for incoming data files matching predefined patterns. Upon detection, a data processing job is triggered, which includes classifying personal information, establishing security policies, and routing the data to appropriate data zones within a data reservoir.
The claims of ’416 focus on a method implemented in an information processing apparatus for common data ingestion. This involves registering a project with multiple data files, each having a specific characteristic and adhering to a predefined naming pattern. The claims also cover registering multiple data zones within a data reservoir, each zone associated with a different data characteristic like format, retention, and compression. The method includes receiving data files into a common drop zone, using file-watcher threads to monitor for predefined patterns , triggering a data processing job based on pattern matching, classifying personal information, establishing security policies, routing data to appropriate zones, and exporting the processed data to a target.
In practice, the system establishes a data reservoir logically partitioned into zones like archive, conformed, and semantic data zones. The archive zone stores raw data, the conformed zone stores reformatted data in a common format, and the semantic zone stores business-friendly data. The file watcher threads monitor the common drop zone, and upon detecting a file matching a registered project's pattern, a data ingestion service is triggered. This service then performs tasks like renaming the file with a timestamp to prevent collisions, classifying personal information, and routing the data to the appropriate data zone based on its characteristics.
The differentiation from prior approaches lies in the automated and standardized nature of the data ingestion process. Instead of manually handling each data source and format, the system uses a registration process and file-watcher threads to automatically trigger data processing jobs. The inclusion of personal information classification and security policy enforcement within the ingestion pipeline also enhances data governance and compliance. This self-service onboarding procedure allows data providers and consumers to easily integrate their data into the system, reducing the need for manual intervention and improving overall efficiency.
In the mid-2010s when ’416 was filed, data ingestion systems were typically implemented using a combination of file systems, databases, and ETL (Extract, Transform, Load) processes. At a time when systems commonly relied on batch processing rather than real-time streaming for many data ingestion tasks, hardware or software constraints made efficient and scalable data ingestion pipelines non-trivial. It was also a time when security and compliance requirements were becoming increasingly important, making it necessary to incorporate security policies and personal information classification into data ingestion workflows.
The examiner approved the application because the prior art of record, including Neiman, Herrnstadt, Lietz, and Earhart, did not explicitly teach "a plurality of project data files, each project data file having a source file name that adheres to a predefined pattern; instantiating a plurality of file-watcher threads at a data ingestion service of the processing apparatus, wherein each of the file-watcher threads is configured to monitor for a corresponding pattern, monitoring, by one file watcher thread of the plurality of file-watcher threads, for incoming data from the common drop zone that is associated with the predefined pattern; determining, by the one file-watcher thread of the plurality of file watcher threads, that the project data files are associated with the predefined pattern".
This patent includes 13 claims, with claim 1 being independent. Independent claim 1 is directed to a method for common data ingestion. The dependent claims elaborate on and add detail to the method described in the independent claim, further defining aspects such as project registration, data zones, routing processes, and system resource requirements.
Definitions of key terms used in the patent claims.
US Latest litigation cases involving this patent.

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.
Date
Description
Get instant alerts for new documents