Hierarchical Document Grouping for Parallel Update Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face difficulties in ensuring consistency between documents when they are modified in parallel, as exemplified by the system described in Japanese Unexamined Patent Application Publication No. 2002-351727 (JP 2002-351727 A), which does not address this issue.

Innovation Solution

An information processing system that groups hierarchical documents and concurrently confirms their states after updates, using a processing unit to manage references and locks to ensure consistency across documents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If documents are modified in parallel to improve productivity, then the update speed increases, but consistency between referenced documents cannot be ensured

Engineering Contradiction:
Improveparallel update capabilityVSAvoiddocument consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system segments documents into hierarchical structures with clear reference relationships, grouping parent documents and referenced child documents together. This segmentation allows the system to manage consistency at the group level while enabling parallel updates of independent groups, thus maintaining reliability while improving productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary consistency management mechanism that tracks reference relationships between documents. This intermediary layer coordinates updates across parallel operations by monitoring which documents reference which others, ensuring consistency is maintained even when multiple documents are updated simultaneously.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If consistency verification is performed to ensure document reliability, then data accuracy improves, but the complexity of the system increases

Engineering Contradiction:
Improvedata accuracyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by pre-establishing reference relationship maps between documents before updates occur. This preliminary structuring of document relationships allows consistency verification to be performed efficiently during parallel updates without adding significant complexity, as the reference framework is already in place.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If all document states are concurrently confirmed to maintain consistency, then data integrity is improved, but the time required for updates increases

Engineering Contradiction:
Improvedata integrityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system segments the concurrency confirmation process by grouping documents based on their reference relationships. Only documents within the same reference group need to be concurrently confirmed, rather than all documents in the system. This segmentation reduces the time required while maintaining data integrity for affected documents.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements self-service mechanisms where each document group manages its own consistency verification independently. This allows multiple document groups to undergo concurrency confirmation simultaneously without interfering with each other, reducing overall update time while maintaining integrity within each group.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20260064779A1Information processing system
Publication Date: 2026.03.05 TOYOTA JIDOSHA KK
  • US20260064779A1 patent drawing
  • US20260064779A1 patent drawing
  • US20260064779A1 patent drawing

AI summary

An information processing system includes a processing unit for grouping a first hierarchical document and a second hierarchical document referred to by at least one document included in the first hierarchical document to generate a document group, and concurrently confirming states of all the hierarchical documents after at least one of the hierarchical documents included in the document group is updated.