Category-Based DBMS Interface for Dynamic Data Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional DBMS infrastructure faces challenges in predicting and accommodating new data types and processing requirements, leading to complex and time-consuming data integration, often requiring redundant storage and manual cleansing, which is error-prone and inflexible.
Innovation Solution
An interface application that dynamically assigns categories to data records and executable program routines, allowing for flexible modification of data processing and output at runtime, eliminating the need for mass alterations of existing data records and enabling efficient integration of new data types without altering the internal data structure or source code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If new data types are integrated into existing DBMS data models, then data compatibility and processing capability are improved, but system complexity and time consumption increase significantly
Solution Approach 1:
The patent introduces an intermediary layer between the DBMS and data records that handles type conversion and mapping. This intermediary translates new data types into existing data model structures without requiring modifications to the core DBMS or existing data records, thereby integrating new data types while maintaining system simplicity.
Solution Approach 2:
The patent segments the data integration process into distinct components: data acquisition, type identification, mapping rule application, and data transformation. This segmentation allows new data types to be integrated through modular processing steps rather than requiring comprehensive restructuring of the entire data model.
2Adaptability or versatility
If data records are altered to accommodate new data types, then data model compatibility is improved, but processing time and computational resources increase
Solution Approach 1:
The patent establishes mapping rules and conversion logic in advance, before new data needs to be integrated. These pre-configured rules enable automatic type conversion when new data arrives, eliminating the need for time-consuming manual data cleansing and integration processes.
Solution Approach 2:
The system performs automatic type matching and conversion without requiring manual intervention. The DBMS infrastructure autonomously identifies new data types, retrieves appropriate mapping rules, and transforms data records, thereby reducing the time loss associated with manual data integration.
3Reliability
If redundant storage is used to maintain data synchronization across different DBMS, then data availability is improved, but storage consumption and hardware requirements increase
Solution Approach 1:
The patent creates a universal data interface layer that can handle multiple data types and formats through a single standardized structure. This universal interface eliminates the need for redundant storage of the same data in multiple different DBMS instances, as the same data can be accessed and processed through the unified interface regardless of its original format.
4Manufacturing precision
If manual data cleansing is performed to integrate new data types, then data quality is improved, but labor intensity and error probability increase
Solution Approach 1:
The patent implements automated validation and error checking mechanisms that provide feedback during the data integration process. The system validates new data against mapping rules, identifies conversion issues, and corrects errors automatically, thereby maintaining high data integration accuracy without requiring manual cleansing operations.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
The invention relates to a method for operating a DBMS infrastructure (102). The method is implemented by an interface application (104, {301, 303}) operatively coupled to the DBMS infrastructure. The method comprises: -storing (202) a plurality of categories (108-116) in the DBMS infrastructure; -storing (204) assignments (130) of one or more of the categories to one or more executable program routines (132-140) in the DBMS infrastructure; -storing (206) data records (120-128, 514, 516, 518) in the DBMS (102) such that each of the data records is assigned to none, one or multiple ones of the plurality of categories, whereby at least some of the database records are assigned to multiple categories; -providing (208) an interface (144) enabling an entity (308, 303) to dynamically modify the stored assignments; -in response to receiving a data request, retrieve matching data records and their respectively assigned categories; -processing (212) the retrieved data records with the executable program routines stored in association with the zero, one or multiple categories associated to each of the retrieved data records; and -outputting (214, 600, 700) a result (602, 702, 704) of the processing.