Virtual Appliance Chaining for Packet Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In conventional virtual appliance deployment schemes, packet latency builds up due to multiple packet exchanges and separate resource management is required for each virtual appliance, leading to increased resource needs and compatibility issues in heterogeneous environments.
Innovation Solution
A system that interconnects multiple virtual appliances, providing a rules module to determine whether to execute software services within each appliance or pass data packets to the next appliance, allowing for efficient packet handling and resource sharing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple virtual appliances are deployed to provide multiple software services, then service functionality is improved, but packet latency increases due to multiple packet exchanges
Solution Approach 1:
The system segments virtual appliances into a chained architecture where each appliance handles specific services. The packet routing mechanism segments the packet flow, allowing packets to be directed to only those appliances that need to process them, rather than requiring sequential exchanges with all appliances. This segmentation reduces unnecessary packet exchanges and latency.
Solution Approach 2:
The patent introduces a packet routing mechanism as an intermediary that sits between the virtual machine and the chained virtual appliances. This intermediary intelligently directs packets to the appropriate appliance in the chain based on service requirements, eliminating the need for multiple back-and-forth packet exchanges and reducing overall latency.
2Reliability
If separate resource management is implemented for each virtual appliance, then service independence is improved, but resource usage increases
Solution Approach 1:
The patent merges resource management at the virtual machine level while maintaining service independence through the chained appliance architecture. Resources such as log files, configuration files, and infrastructure libraries are shared across the virtual machine host, eliminating redundant resource consumption. Each virtual appliance maintains its service logic independence while sharing underlying system resources.
Solution Approach 2:
The virtual machine host provides universal resource management that serves all chained virtual appliances. A single set of infrastructure resources (filesystem, libraries, OS abstraction calls) serves multiple appliances simultaneously, making the resource management system multi-functional and reducing overall resource consumption while maintaining service independence.
3Adaptability or versatility
If heterogeneous virtual appliances are deployed to provide diverse services, then service diversity is improved, but compatibility issues arise
Solution Approach 1:
The patent implements a homogeneous execution environment at the virtual machine level where all chained virtual appliances run within the same virtualized context. This homogeneous environment provides consistent OS abstraction calls, unified filesystem access, and standardized infrastructure libraries, ensuring compatibility across heterogeneous appliances while allowing service diversity.
4Ease of operation
If multiple packet exchanges are used to manage service context, then service control is improved, but packet processing time increases
Solution Approach 1:
The system performs preliminary actions by pre-configuring the chained virtual appliance architecture and establishing routing rules before packet arrival. The packet routing mechanism is pre-programmed with knowledge of which appliances handle which services, allowing for direct packet routing without requiring multiple exploratory packet exchanges to determine the appropriate service handler.
Data Source
AI summary
Management of virtual resources may be provided by interconnecting a plurality of virtual appliances with common executable software services. A data packet may be sent through multiple virtual appliances invoking services within each if rules stored within respective virtual appliances correspond to a request for service in the data packet. The data packet may be passed through multiple virtual appliances prior to being returned to a hypervisor.