Concurrent Hierarchical Data Structures Consistency

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data management systems struggle to efficiently handle the same set of data records organized in multiple hierarchical structures, where changes in one hierarchy may not be consistently propagated or approved across concurrent hierarchies, leading to potential inconsistencies and management challenges.

Innovation Solution

A method and system for maintaining multiple hierarchies of data records, where changes in one hierarchy can be propagated, approved, or denied based on operational rules, with notifications and permissions ensuring consistency across concurrent hierarchies, allowing for real-time interactions and management of overlapping records.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple hierarchical data structures are maintained concurrently with the same set of records, then the system's adaptability and versatility are improved, but the complexity of managing data consistency across hierarchies increases

Engineering Contradiction:

Improveability to organize data in multiple hierarchical structuresVSAvoidcomplexity of managing changes across concurrent hierarchies

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the management of changes by introducing distinct change request objects for each hierarchy. When a record needs to be modified, separate change requests are created for each hierarchical structure containing that record, allowing independent tracking and approval processes for each hierarchy without interfering with others.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary components including change request objects, approval mechanisms, and notification systems that mediate between different hierarchical structures. These intermediaries coordinate changes across hierarchies, ensuring that modifications in one hierarchy are properly communicated and approved by relevant authorities in other hierarchies before implementation.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If change propagation is enforced across all concurrent hierarchies, then data consistency is improved, but the time required to process and approve changes increases

Engineering Contradiction:

Improvedata consistency across hierarchiesVSAvoidtime for change approval and propagation

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by creating change request objects that capture the intended modification before actual implementation. These change requests are prepared in advance with all necessary information about the proposed change, allowing for efficient review and approval processes without delaying the actual data modification once approved.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where notifications are automatically sent to relevant parents and authorities when changes are proposed or approved in any hierarchy. This feedback loop ensures that all stakeholders are promptly informed of status changes, enabling parallel processing of approvals rather than sequential waiting, thus reducing overall processing time while maintaining consistency.

Inventive Principle:

Principle #23Feedback

3Reliability

If notifications are sent to all parents in concurrent hierarchies before allowing changes, then data consistency is improved, but the operational complexity and processing overhead increase

Engineering Contradiction:

Improveconsistency of data across hierarchical structuresVSAvoidease of making changes to records

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent merges the notification and approval processes into a unified change request workflow. Instead of separate notification steps to each parent followed by separate approval steps, the system combines these into an integrated process where notifications are automatically routed to appropriate authorities and their approvals are tracked within the same change request object, simplifying the user experience while ensuring all necessary consents are obtained.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11650973B2Concurrent multiple hierarchical data structures with consistent data

Publication Date: 2023.05.16 ORACLE INT CORP

AI summary

A method may include maintaining first data structure with records organized in a first hierarchy, and maintaining a second data structure with records organized in a second hierarchy. The method may additionally include receiving a change request for the value stored in the first record. The change request may be received from a parent in the second data structure of the first record. The method may further include sending a notification to the parent in the first data structure that the parent in the second data structure is attempting to change the first record.