Accelerated Emulation Backend Software Update Context Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Updating or replacing emulation device backend software in cloud computing environments often requires significant downtime due to the need to stop and restart software processes, leading to increased lag and application downtime.
Innovation Solution
The solution involves transferring the context of the running software to the updated software and rebuilding the context map, allowing the new software to take over while the original software is still running, thereby reducing downtime by enabling the new software only after the context map is rebuilt.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional software update process is used, then software can be updated, but significant downtime is required
Solution Approach 1:
The patent applies preliminary action by preparing the updated backend software and transferring its context map while the original software is still running. The context map transfer includes copying data structures, variable states, and execution contexts from the running software to the updated software in advance, so that when the switch occurs, the updated software can immediately resume execution with minimal interruption.
Solution Approach 2:
The patent uses the context map as an intermediary mechanism to enable seamless software updates. The context map serves as a mediator that carries essential runtime information between the original and updated software versions, allowing the system to transition from one version to another without losing critical execution state, thereby minimizing downtime.
2Ease of manufacture
If software is stopped for update, then update can be performed, but application downtime increases
Solution Approach 1:
The patent implements continuity of useful action by maintaining software execution throughout the update process. The original backend software continues to run and handle requests while the updated software is being prepared and its context map is being transferred. This allows the system to perform updates without interrupting the useful action of processing network packets and I/O operations.
Solution Approach 2:
The context map transfer and preparation of updated software occurs in advance while the original software is still operational. This preliminary preparation ensures that when the switch to updated software occurs, it can immediately take over without requiring the application to shut down, thus maintaining continuous service availability.
3Loss of time
If context map transfer is performed while software is running, then downtime is reduced, but system complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the software update process into distinct manageable components: the original backend software, the updated backend software, and the context map structure. This segmentation allows each component to be independently managed and transferred, making the complex update process more controllable and less error-prone despite the increased overall system complexity.
Solution Approach 2:
The context map serves as an intermediary data structure that simplifies the transfer process between software versions. By using this standardized intermediate representation to carry execution context, variable states, and data structures, the patent manages the complexity of live updates through a well-defined mediation layer rather than direct complex interactions between old and new software.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems and methods are presented that reduce the downtime of communication when updating backend software of an accelerated emulation system. In at least one embodiment, by first transferring the context of the running software to the updated software and rebuilding the context map for the communication and programming the context in the accelerated emulated device, downtime can be reduced by only enabling the new software and disabling the original software after the context map has been rebuilt as the last stage of execution.