Change-Detection Halt Records for Accurate Database Transactions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in managing data processing activities efficiently outside normal hours due to constraints imposed by data changes, such as corporate actions or instrument changes, which limit all-day trading capabilities.

Innovation Solution

A system is developed to create halt records for database items undergoing changes, preventing data processing during specified periods, and allowing processing only when changes are complete, using multiple data sources to ensure accuracy and resolve conflicts, ensuring high availability and service levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data processing activities are constrained to specific times or conditions to ensure data accuracy, then data reliability is improved, but productivity deteriorates due to limited processing windows

Engineering Contradiction:
Improvedata accuracyVSAvoidprocessing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by evaluating data change conditions outside of processing sessions and updating data before processing sessions begin. This allows the system to prepare data in advance during off-hours, ensuring data accuracy during processing while enabling extended processing windows without compromising reliability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If instrument changes are evaluated during after-market hours to maintain data accuracy, then data reliability is improved, but loss of time increases due to limited evaluation windows

Engineering Contradiction:
Improveinstrument data accuracyVSAvoidevaluation delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables continuous evaluation of instrument changes by operating outside traditional market hours. Data change evaluation and instrument updates can occur continuously during extended hours, eliminating the constraint of limited after-market evaluation windows while maintaining data accuracy through proper timing controls.

Inventive Principle:
Principle #20Continuity of useful action

3Productivity

If all-day instrument trading is enabled without change detection, then productivity is improved, but reliability deteriorates due to potential data errors

Engineering Contradiction:
Improvetrading availabilityVSAvoiddata accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback mechanisms by continuously monitoring for data change conditions even during extended processing sessions. When instrument changes are detected, the system can respond by updating instruments or adjusting processing parameters, ensuring data accuracy is maintained throughout all-day trading operations.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20250348382A1Managing data availability based on change detection
Publication Date: 2025.11.13 ROBINHOOD MARKETS INC
  • US20250348382A1 patent drawing
  • US20250348382A1 patent drawing
  • US20250348382A1 patent drawing

AI summary

A system for managing data availability for database transactions is disclosed. The system is programmed to receive source data and extract a plurality of events from the source data. The system is programmed to create a halt record corresponding to each event of the plurality of events. The system is programmed to resolve conflicts among one or more halt records. The system is programmed to receive a request for a specific database transaction related to a specific database item from a client device. The system is programmed to determine whether any halt record is in effect for the specific database item. The system is programmed to perform the specific database transaction in response to determining no halt record is in effect. The system is programmed to transmit a result of the specific database transaction in response to the request to the client device.