Distributed History Relay Units for Equipment Data Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing information processing systems for equipment management face challenges in efficiently managing and relaying large quantities of history data, particularly in preventing duplicate data collection and handling failures, which leads to increased processing loads and network communication burdens.

Innovation Solution

The system employs a network architecture with first, second, and third equipment items interconnected via a network, utilizing history storage blocks, response blocks, and lists to manage and relay history data efficiently, ensuring consistent data collection and relay even in failure scenarios, by using history relay units to store and transmit data with sequence numbers and IDs for accurate data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If centralized history management is implemented where all equipment histories are transmitted to center equipment, then data consistency is improved, but processing load and network communication burden increase significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidprocessing load
Core Design Contradiction:
Stability of the object's compositionVSPower

Solution Approach 1:

The patent divides the centralized history management system into distributed history relay units, each responsible for specific equipment items. Instead of one center equipment handling all histories, multiple relay units segment the processing load while maintaining data consistency through coordinated updates across the network.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to the system architecture, with history relay units at the intermediate level between equipment and center equipment. This adds a spatial dimension to data management, allowing local processing at relay units while maintaining centralized coordination, thus reducing the burden on center equipment.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If all equipment histories are transmitted to center equipment for disaster recovery, then data reliability is improved, but network communication burden and processing load increase

Engineering Contradiction:
Improvedata reliabilityVSAvoidnetwork communication volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts the history relay function from the center equipment and places it at distributed relay units close to the equipment. This extraction allows history data to be maintained locally at relay units, reducing the need to transmit all history data across the network while ensuring reliability through local storage and selective synchronization.

Inventive Principle:
Principle #2Taking out (Extraction)

3Loss of time

If continuous updates of flagged contents are performed, then data freshness is improved, but processing load increases

Engineering Contradiction:
Improvedata freshnessVSAvoidprocessing load
Core Design Contradiction:
Loss of timeVSPower

Solution Approach 1:

The patent implements periodic history collection at history relay units, where equipment histories are gathered at scheduled intervals rather than continuously. This periodic action maintains data freshness by regularly updating history information while reducing processing load compared to continuous real-time collection.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS9262453B2Information processing system and processing method for use therewith
Publication Date: 2016.02.16 HITACHI LTD
  • US9262453B2 patent drawing
  • US9262453B2 patent drawing
  • US9262453B2 patent drawing

AI summary

Information processing system including pluralities of first and second equipment items, and a third equipment item. Each first equipment item stores history data and returns a first response block about controls and changes in status of each first equipment item, responsive to a data request from the second equipment items. Each second equipment item stores the history data returned responsive to the data request; a second response block returns history data stored in the second history storage block responsive to a request from the third equipment item; first and second lists store first information identifying latest history data returned from the first equipment items regarding each first equipment item, and second information identifies history data last returned to the third equipment item regarding each first equipment item. Third equipment item's third history storage block stores history data returned responsive to the data request made to the second equipment items.