Database System for Dynamic Model Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database systems struggle to efficiently integrate and process large, disparate data sets from various sources while maintaining accuracy and efficiency, especially when dealing with constantly updating data and geographical variations.

Innovation Solution

A database system that merges data from discrete sources, generates customized models dynamically, and applies filters to segregate records based on specific criteria, using a hardware processor to execute instructions and update records in real-time.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If data from multiple discrete sources is integrated and processed, then the completeness and accuracy of the data model is improved, but the processing power and memory usage increase significantly

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing power
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The system segments the database into multiple discrete data sources (user database, event database, transaction database) that can be independently processed and integrated. This allows selective processing of only relevant data portions rather than loading entire datasets into memory, reducing processing power requirements while maintaining data accuracy.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary data integration and model generation in the background before user requests. Pre-generated models are stored and can be quickly retrieved and updated rather than generated on-demand, significantly reducing real-time processing power consumption while maintaining high data accuracy.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If customized models are dynamically generated based on user requirements, then the adaptability to user needs is improved, but the time required for model generation increases

Engineering Contradiction:
Improvecustomization capabilityVSAvoidmodel generation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system pre-generates customized models based on anticipated user requirements and stores them in the database. When users access the system, pre-generated models are immediately available for viewing and customization, eliminating the time-consuming model generation process and enabling rapid adaptation to user needs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system allows users to dynamically customize pre-generated models by selecting different parameters, filters, and criteria. The model structure is flexible and can be adjusted in real-time without regenerating the entire model from scratch, maintaining high adaptability while minimizing generation time.

Inventive Principle:
Principle #15Dynamics

3Measurement precision

If geographical filters are applied to segregate records, then the relevance of retrieved data is improved, but the complexity of the query processing increases

Engineering Contradiction:
Improvedata relevanceVSAvoidquery processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system pre-segments data by geographical regions and stores location information in discrete fields within the database structure. Geographical filters can be applied by simply querying pre-segmented regional data rather than filtering entire datasets, reducing query processing complexity while maintaining high data relevance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses lightweight, disposable filter objects that are created temporarily for each query execution and automatically discarded after use. These simple filter structures enable complex geographical segmentation queries without requiring permanent storage of complex query logic, reducing overall system complexity.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

4Reliability

If event data is continuously integrated into user records, then the up-to-date nature of the data is improved, but the frequency of database updates and processing overhead increase

Engineering Contradiction:
Improvedata currencyVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system implements periodic batch processing of event data integration rather than continuous real-time updates. Events are accumulated in buffers and integrated into user records at scheduled intervals, reducing the frequency of database write operations and processing overhead while maintaining sufficiently current data for most applications.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system uses incremental update strategies where only changed data portions are processed and integrated, rather than reprocessing entire datasets. Changed event data is identified, processed, and merged with existing records, discarding redundant processing while maintaining data currency and improving processing efficiency.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS12265578B1Database system for dynamically generating customized models
Publication Date: 2025.04.01 EXPERIAN INFORMATION SOLUTIONS INC
  • US12265578B1 patent drawing
  • US12265578B1 patent drawing
  • US12265578B1 patent drawing

AI summary

Embodiments of a system may comprise databases and a processor that receives a first filter item and a database filter item, generates a first database based on the first filter item, integrate data from the first database into the user database to create an updated plurality of user records, generate a second database based on a selected set of records, in the updated plurality of user records, corresponding to the database filter item, determine metrics that correspond to the second database, generate a model to segregate the second database using the metrics, receive criteria, compare the segregated second database with the criteria to remove records that do not meet the criteria, cause a subsequent update to the updated second database to integrate data from the event database to create an updated diminished second database, and generate a notification including information included in the updated diminished second database.