Distributed Logical Unit Repository for Database Query Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database integration and consolidation methods are inefficient, costly, and risk data integrity and security, especially in large enterprises with diverse systems and increasing data volumes, due to synchronization issues, legacy system incorporation, and storage and speed problems.

Innovation Solution

The implementation of Distributed Logical Unit Repositories (DLUR) that store and access data by logical units, such as customers or accounts, in a compressed and encrypted format, allowing for rapid query resolution and automatic snapshot updating, with features like parallel processing, encryption, and versioning, enabling efficient data management and retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data is stored in multiple separate databases for different logical units, then data organization follows traditional relational structures, but storage space increases and query speed decreases

Engineering Contradiction:
Improvestorage spaceVSAvoidquery speed
Core Design Contradiction:
Quantity of substanceVSSpeed

Solution Approach 1:

The patent combines multiple database tables and data sources into a single consolidated database structure. All information related to a logical unit (customer, account, etc.) is stored together in one location rather than分散 across multiple databases, reducing storage redundancy and improving query efficiency by eliminating the need to access multiple separate database systems

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments data by logical units (customers, accounts, etc.) rather than by traditional database tables. Each logical unit becomes a self-contained entity in the consolidated database, allowing the system to store only the specific data relevant to each logical unit without unnecessary redundancy from multiple database relationships

Inventive Principle:
Principle #1Segmentation

2Productivity

If data is consolidated into a single database structure, then query speed improves and storage efficiency increases, but system complexity increases

Engineering Contradiction:
Improvequery speedVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent creates a universal consolidated database structure that can handle multiple types of data (customer information, account data, transactions, etc.) in a single system. This multi-functional approach eliminates the need for separate database systems for different data types, simplifying the overall system architecture while maintaining high query performance across diverse data kinds

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

Solution Approach 2:

Instead of organizing data by traditional database tables and relationships, the patent inverts the approach by organizing data by logical units (customers, accounts). This inversion simplifies the data model by making the logical unit the central organizing principle rather than database tables, reducing system complexity while improving query efficiency

Inventive Principle:
Principle #13The other way round (Inversion)

3Adaptability or versatility

If traditional database integration methods are used, then data from diverse systems can be consolidated, but data integrity and security risks increase

Engineering Contradiction:
Improvedata integration capabilityVSAvoiddata integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a consolidated database structure as an intermediary layer between diverse source systems. This intermediary consolidates data from multiple sources into a single trusted repository with unified access controls and security measures, eliminating the need for complex point-to-point integration between systems and reducing security vulnerabilities associated with multiple access paths

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10311022B2CDBMS (cloud database management system) distributed logical unit repository
Publication Date: 2019.06.04 K2VIEW LTD
  • US10311022B2 patent drawing
  • US10311022B2 patent drawing
  • US10311022B2 patent drawing

AI summary

Systems and methods may implement database technology using distributed logical unit repositories (DLURs). DLURs may use a database structure related to a specific logical unit such as a customer, employee, or the like. Information used in DLUR database structures may include data, database structure, functions, and the like that helps form a complete model for a logical unit. In one embodiment, queries to a system concerning entities can be answered immediately by accessing a database using DLURs, which obviates the need to consult a number of databases in parallel and greatly reduces memory and time required to provide the requested information.