Packet-Aware Fault Tolerance for Virtual Machines

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional fault-tolerance methods for virtual machines in cloud services, such as Kemari, often disrupt the primary virtual machine's execution due to continuous checkpointing triggered by external events, leading to inefficiencies in resource usage and performance.

Innovation Solution

A packet-aware fault-tolerance method and system that employs a novel synchronization mechanism by comparing packet checksums between primary and backup virtual machines, optimizing resource consumption and enhancing efficiency by minimizing unnecessary synchronization operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous checkpointing is used for fault tolerance synchronization, then reliability is improved, but productivity deteriorates due to frequent execution stops

Engineering Contradiction:
Improvefault toleranceVSAvoidexecution efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements periodic checkpointing instead of continuous checkpointing, where synchronization occurs at predetermined intervals or triggers rather than after every external event. This reduces the frequency of execution stops while maintaining fault tolerance capabilities, directly resolving the contradiction between reliability and productivity.

Inventive Principle:
Principle #19Periodic action

2Reliability

If state synchronization is performed after every external event, then reliability is improved, but loss of time increases due to frequent interruptions

Engineering Contradiction:
Improvesynchronization accuracyVSAvoidexecution downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs synchronization periodically based on predetermined triggers or time intervals rather than after every external event. This reduces the number of interruptions and time losses while maintaining sufficient synchronization accuracy for fault tolerance.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent changes the synchronization trigger parameters from event-driven to time-driven or threshold-driven, adjusting the frequency and timing of synchronization operations to balance reliability requirements with time efficiency.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If resource-intensive synchronization methods are used, then reliability is improved, but use of energy increases

Engineering Contradiction:
Improvefault tolerance capabilityVSAvoidcomputing resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

By implementing periodic synchronization instead of continuous synchronization, the system reduces the total computing operations required over time, thereby lowering energy consumption while maintaining fault tolerance reliability through regular state updates.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10402264B2Packet-aware fault-tolerance method and system of virtual machines applied to cloud service, computer readable record medium and computer program product
Publication Date: 2019.09.03 NAT CENT UNIV
  • US10402264B2 patent drawing
  • US10402264B2 patent drawing
  • US10402264B2 patent drawing

AI summary

The present disclosure relates to packet-aware fault tolerance methods of virtual machines applied to cloud services. One such method includes using a primary input processing unit to receive an uploaded packet and replicating the uploaded packet to a backup input processing unit. The method can further include utilizing a primary execution unit to operate the uploaded packet to generate an output packet, which is then transmitted to a processing unit. A backup execution unit can be used to operate the uploaded packet to generate a backup output packet. The backup output packet can be transmitted to a backup processing unit. A fault-tolerance control component can receive the primary output packet from the primary output processing unit. The primary fault-tolerance control component can be used to compare a primary packet checksum of the primary output packet is consistent with a backup packet checksum.