Citation Document Update Synchronization via Relationship Diagrams

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In databases where documents are stored by citing each other, there is a risk of ignoring synchronous updates or modifications of associated documents during the updating process, leading to inconsistencies in document update content.

Innovation Solution

An updating method for citation documents that involves acquiring a document relationship diagram from the database, extracting associated document identifications based on the document modification instruction, and pushing the modification content to the corresponding associated documents, ensuring synchronous updates across citation relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If documents are stored by citing each other to save storage space, then storage efficiency is improved, but document update consistency deteriorates due to complex citation relationships causing missed synchronous updates

Engineering Contradiction:
Improvestorage spaceVSAvoiddocument update consistency
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The system performs preliminary actions by acquiring the document relationship diagram before processing updates, identifying all associated documents in advance through graph traversal, and preparing the update propagation plan beforehand. This ensures that when an update occurs, all affected documents are already known and can be updated consistently without missing any citations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by pushing document modification content back to associated documents through the extraction and propagation mechanism. When a document is updated, the system traces citation relationships bidirectionally, identifies all affected documents, and ensures they receive the modification content, creating a feedback loop that maintains consistency across the citation network.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If complex citation relationships are implemented in the database, then document interconnectivity is improved, but update synchronization deteriorates due to difficulty in tracking all associated documents

Engineering Contradiction:
Improvedocument interconnectivityVSAvoidupdate tracking complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system introduces a graph database as an intermediary structure to manage citation relationships. The graph database with nodes and edges provides a natural fit for representing documents and their citation connections, making it easier to traverse and track relationships compared to traditional relational databases. This intermediary structure simplifies the complexity of tracking associations while maintaining high interconnectivity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the update process into distinct phases: acquiring the relationship diagram, extracting associated document identifications through graph traversal, and pushing modifications to specific associated documents. This segmentation breaks down the complex task of maintaining citation consistency into manageable steps, reducing the overall complexity of update tracking.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12287834B2Citation document updates based on associated document modification
Publication Date: 2025.04.29 DOUYIN VISION CO LTD
  • US12287834B2 patent drawing
  • US12287834B2 patent drawing
  • US12287834B2 patent drawing

AI summary

An updating method of a citation document, an apparatus, an electronic device and a storage medium. The method includes: acquiring a document relationship diagram of a database; acquiring a document modification instruction, where the document modification instruction includes a document identification and a document modification content; extracting an associated document identification from the document relationship diagram according to the document identification; pushing the document modification content to an associated document corresponding to the associated document identification.