Distributed Database Segregation for Avionics Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Avionics systems face challenges in meeting disparate data requirements for security, integrity, and latency due to the inflexibility of fixed database architectures, which can be cost-prohibitive and fail to accommodate varying client application needs effectively.

Innovation Solution

A system and method that instantiates multiple databases with different performance attributes, allowing it to determine and meet specific data access requirements by routing requests to the appropriate databases, potentially submitting requests to two or more databases for increased integrity and comparing results for robust checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a fixed database architecture is used, then system simplicity is maintained, but flexibility to meet disparate data requirements deteriorates

Engineering Contradiction:
Improveflexibility to meet data requirementsVSAvoiddatabase architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the database architecture into multiple independent database instances, each optimized for specific performance attributes (security, integrity, latency). This allows the system to meet disparate data requirements by routing queries to appropriate segmented databases rather than using a monolithic fixed architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a universal database access layer that handles multiple types of data access requests (security-critical, integrity-critical, latency-critical) through a single interface. This multi-functional access layer routes requests to different database instances based on requirements, providing flexibility without increasing client-side complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple databases with different performance attributes are instantiated, then ability to meet disparate requirements improves, but system complexity increases

Engineering Contradiction:
Improveability to meet security, integrity, and latency requirementsVSAvoidnumber of databases
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a database access layer as an intermediary between client applications and multiple database instances. This mediator handles the complexity of routing requests to appropriate databases based on performance requirements, shielding clients from the underlying database infrastructure complexity while enabling flexible requirement fulfillment.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If strict requirements in one metric are accommodated, then data security or integrity is improved, but cost becomes prohibitive

Engineering Contradiction:
Improvedata security or integrityVSAvoidstorage cost
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent applies local quality by instantiating multiple databases with different performance attributes and routing queries to appropriate databases based on specific requirements. This allows the system to allocate resources efficiently - using high-cost databases only when strict security or integrity requirements are needed, rather than uniformly applying high-cost infrastructure across all data access operations.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12153599B2Distributed database for segregation of concerns
Publication Date: 2024.11.26 ROCKWELL COLLINS INC
  • US12153599B2 patent drawing
  • US12153599B2 patent drawing
  • US12153599B2 patent drawing

AI summary

A system and method for accessing data to meet disparate security, integrity, and latency requirements includes multiple databases instantiated in the system with different performance attributes. The system receives a data access request from a client application. The system determines one or more data access requirements associated with the data access request and identify a database or set of databases that conform to those requirements. The system then submits the data access request to the identified databases and returns the result to the client application. The system may determine a data integrity threshold for the data access request, and submit the data access request to two or more databases simultaneously.