Segmented Database Architecture for Real-Time Transaction Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems combine real-time data values and configuration data values in a single record structure, leading to unnecessary integrity updates and mixed performance criteria, where critical and non-critical operations are treated equally, and versioning is required outside the real-time database.

Innovation Solution

A database architecture is segmented into separate real-time and configuration segments, with each segment storing distinct types of data, allowing for independent handling and ensuring transactional integrity by using a high-performance database to manage locks and provide a unified view to applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If real-time data values and configuration data values are stored in a single record structure, then data access is simplified, but unnecessary integrity updates occur and performance criteria are mixed

Engineering Contradiction:
Improvedata access simplicityVSAvoidupdate efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent divides the previously unified record structure into two separate segments: a real-time data segment and a configuration data segment. This segmentation allows independent handling of each data type, enabling version comparison for configuration updates without forcing updates on real-time data, thereby eliminating unnecessary integrity updates while maintaining simplified access through unified management.

Inventive Principle:
Principle #1Segmentation

2Reliability

If versioning is implemented outside the real-time database, then configuration data integrity can be maintained, but system complexity increases

Engineering Contradiction:
Improveconfiguration data integrityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the versioning functionality directly into the real-time database system by implementing it within the configuration data segment. This integration allows the database to natively handle version comparison and integrity control for configuration data, eliminating the need for external versioning mechanisms while maintaining data integrity and reducing system complexity.

Inventive Principle:
Principle #5Merging (Combining)

3Ease of operation

If critical and non-critical operations are treated equally, then operational simplicity is maintained, but performance optimization is lost

Engineering Contradiction:
Improveoperational simplicityVSAvoidoperation performance
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent applies different quality attributes to different data segments: the real-time data segment is optimized for high-speed access and updates with minimal locking, while the configuration data segment implements version control and integrity checks. This local differentiation allows critical real-time operations to maintain high performance while non-critical configuration operations undergo thorough validation, optimizing overall system performance without sacrificing operational simplicity.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3792781B1Transactional integrity in a segmented database architecture
Publication Date: 2026.04.08 AVEVA SOFTWARE LLC
  • EP3792781B1 patent drawingFigure 1
  • EP3792781B1 patent drawingFigure 2
  • EP3792781B1 patent drawingFigure 3

AI summary

This disclosre provides separate real-time and configuration segments in a database. The real-time segment provides real-time data values to a real-time application and the configuration segment provides configuration data values to the real-time application. Utilizing two or more configuration segments enables changes to configuration data values without impacting real-time applications.