Control Node List Updates for Nth-Order Data Transmission

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In nth-order data transmission systems, each node struggles to correctly grasp the data distribution source and destination, leading to inefficient data routing and incomplete cancellation of data transmission, as existing systems lack mechanisms for updating distribution lists across multiple nodes.

Innovation Solution

A control system with nodes that maintain and update distribution source and destination lists through update requests and responses, ensuring each node accurately tracks data flow and cancels transmissions appropriately by propagating update and cancellation requests across the network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each node independently manages data transmission in nth-order transmission systems, then data can be distributed across multiple nodes, but nodes cannot correctly grasp distribution sources and destinations leading to incomplete transmission cancellation

Engineering Contradiction:

Improveaccuracy of distribution source and destination identificationVSAvoidcomplexity of distribution list management mechanism

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system pre-establishes distribution source lists and distribution destination lists in each node before data transmission occurs. These lists are maintained and updated through update requests and responses, allowing nodes to proactively know their roles in the transmission chain rather than discovering them during transmission or cancellation operations.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where nodes send update requests to adjacent nodes and receive update completion responses. This feedback loop ensures that when a node's distribution list changes, the information is propagated to relevant nodes, which then update their own lists and propagate further, maintaining consistency across the entire transmission chain.

Inventive Principle:

Principle #23Feedback

2Productivity

If the most upstream node exchanges data with all other nodes one by one, then data can be distributed to all nodes, but the load is concentrated on the upstream node reducing efficiency

Engineering Contradiction:

Improvedata distribution efficiencyVSAvoidcomputational load on upstream node

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The data transmission task is segmented and distributed across multiple nodes in the chain. Each node independently manages its own distribution source list and destination list, and independently propagates update requests to its adjacent nodes. This segmentation eliminates the bottleneck at the upstream node, as each node only needs to communicate with its immediate neighbors rather than all other nodes.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system merges the functions of distribution list management and data transmission routing into a unified mechanism. The distribution source lists and destination lists serve dual purposes: they track the transmission chain for reliability purposes and simultaneously guide efficient data routing, eliminating the need for separate management systems.

Inventive Principle:

Principle #5Merging (Combining)

3Reliability

If nodes propagate update requests to all adjacent nodes, then distribution lists can be updated across the network, but the update process becomes complex and time-consuming

Engineering Contradiction:

Improveconsistency of distribution lists across nodesVSAvoidtime for update propagation

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

Nodes maintain their distribution source lists and destination lists in advance, so when an update is needed, the information is already structured and ready for propagation. This preliminary organization of data reduces the processing time required during actual update operations compared to systems that must discover and construct transmission paths in real-time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Instead of requiring every node to update its lists in response to every change in the network, the system uses partial updates propagated only to affected adjacent nodes. A node updates its lists and propagates update requests only to nodes that are actually part of its transmission chain, rather than broadcasting to all nodes in the network, reducing unnecessary update operations.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS20240111262A1Control system, control device, control method, and computer-readable recording medium storing control program

Publication Date: 2024.04.04 FUJITSU LTD

AI summary

A system including control devices configured to perform nth-order transmission, each control device including: a storage device storing, in relation to the control devices, a source list being a list of the control devices to be passed through from a most upstream control device to the control device and a destination list being a list of the control devices to be passed through from the control device to a most downstream control device; and a processor performing processing including: when an update request including a first source list of a first control device is received, updating the source list using the update request, generating a new update request using the updated source list, and transmitting the new update request to a second control device; and when a completion response including a second destination list of the second control device is received, updating the destination list using the completion response.