Master-Slave Adapter Hardware Synchronization for Reliable Message Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing message passing systems face challenges in efficiently transferring messages across switched networks, including packet loss, sequencing issues, and unreliable paths, particularly when handling multiple tasks and large numbers of channels, which can lead to performance bottlenecks and errors.
Innovation Solution
The introduction of a specialized hardware register, channel state register (CH_STATE), and communication adapters with processing engines that enable direct memory-to-memory data transfer, time of day synchronization, and error handling mechanisms, allowing for efficient and reliable message packet transfer across networks while managing backup and master/slave relationships among adapters.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If semaphores are used to coordinate tasks for every channel action, then task synchronization is achieved, but system overhead and processing speed deteriorate
Solution Approach 1:
The patent extracts the synchronization mechanism from general-purpose semaphores and implements it directly in hardware within the communication adapter. The channel status register and task synchronization logic are built into the adapter's hardware architecture, allowing tasks to be synchronized without software semaphore overhead, thus resolving the contradiction between reliable synchronization and processing speed.
Solution Approach 2:
The patent replaces the software-based semaphore mechanism with hardware-based synchronization logic embedded in the communication adapter. This substitution eliminates the software overhead and coordination delays associated with semaphores, achieving both reliable task synchronization and high processing speed through direct hardware control.
2Adaptability or versatility
If multiple message packets are transmitted through a switched network, then communication coverage is improved, but packet loss and sequencing errors increase
Solution Approach 1:
The patent implements preliminary actions by establishing backup communication paths and pre-configuring routing information before failures occur. The system maintains multiple active paths and pre-computes alternative routes, allowing it to quickly switch to backup paths when packet loss or sequencing errors occur, thus maintaining reliable delivery across extended communication coverage.
Solution Approach 2:
The patent implements feedback mechanisms through acknowledgment packets and path quality monitoring. When packets are transmitted through multiple paths, the system receives feedback about packet delivery status and path conditions, allowing it to dynamically adjust routing decisions and retransmit lost packets, thereby maintaining reliability despite expanded communication coverage.
3Reliability
If backup adapter units are designated for failover, then system availability is improved, but device complexity increases
Solution Approach 1:
The patent merges the backup adapter functionality with the primary adapter by implementing hot-standby capabilities within the same hardware unit. The adapter can operate in primary or backup mode without requiring separate physical devices, reducing overall system complexity while maintaining high availability through seamless failover capabilities.
Solution Approach 2:
The patent implements self-service failover mechanisms where the adapter automatically detects failures and transitions between primary and backup roles without manual intervention. The system monitors its own health status and autonomously manages failover, reducing the operational complexity associated with manual backup configuration and management.
Data Source
AI summary
A system and method are provided in which communication adapters, which are used for the transfer of message packets from and amongst a plurality of data processing nodes, are provided with internal storage which is used to indicate the status of a particular adapter as a master, as a slave or as a backup up adapter. This information provides the adapters with the ability to be called into service to take over the operations of another adapter in the event of node or adapter failure.