Redundancy System Synchronization via Segmented Memory
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing redundancy systems fail to perform synchronization when a failure occurs in an application, leading to incomplete data transfer and potential service interruptions.
Innovation Solution
A redundancy system with a synchronization data memory, management bit map table, and processors for managing flags and synchronization information, allowing for timely data synchronization between active and standby devices, even in the event of application failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a centralized information server is used to manage synchronization data, then data management is simplified, but synchronization cannot be performed if the application fails
Solution Approach 1:
The patent divides the centralized information server architecture into distributed components. Each device maintains its own synchronization data memory and management bit map table, eliminating the single point of failure. The synchronization function is segmented into independent modules that can operate autonomously even if the application fails.
Solution Approach 2:
The patent introduces a management bit map table as an intermediary structure between the application and synchronization data. This bit map table tracks the synchronization status of each segment independently, allowing the system to identify and synchronize only the necessary data portions even when application failures occur.
2Reliability
If all synchronization data is transferred at once, then data consistency is achieved, but synchronization time increases
Solution Approach 1:
The patent divides synchronization data into multiple segments and uses a management bit map table to track each segment's synchronization status. This allows the system to transfer only the segments that have changed or are out of sync, rather than transferring all data, thereby reducing synchronization time while maintaining data consistency.
Solution Approach 2:
The patent implements partial synchronization by using the management bit map table to identify only the necessary segments that require synchronization. This partial action approach transfers only the minimum required data to achieve consistency, reducing unnecessary data transfer time while ensuring data consistency is maintained.
3Reliability
If the system checks for synchronization status frequently, then data consistency is maintained, but system performance decreases
Solution Approach 1:
The patent implements periodic checking of synchronization status using the management bit map table at predetermined intervals rather than continuous monitoring. This periodic action maintains data consistency while minimizing the impact on system performance by checking only when necessary.
Solution Approach 2:
The management bit map table automatically tracks and records the synchronization status of each segment without requiring external intervention. This self-service mechanism allows the system to maintain data consistency information efficiently, reducing the overhead associated with frequent status checks.
Data Source
AI summary
A redundancy system that can perform synchronization even if a failure occurs to an application. According to the redundancy system of the present invention, a synchronization data memory area, a management bit map table having a flag created for each segment of the synchronization data memory area, and a management memory area for storing the starting address of the segment are set in each device. In the service application process, a service is performed using one or more segments, a flag corresponding to the segment is set, and synchronization information is written to the management memory each time the segment is written or overwritten. In the read process, each flag in the management bit map table is checked, and if a flag being set exists, the synchronization data is read from the segment corresponding to the synchronization information stored in the management memory, and the flag is reset.