Virtual Network Device for Cloud VM Scalability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Standard network devices in cloud computing environments struggle to manage communications between a large number of virtual machines (VMs), despite supporting thousands of VLANs and MAC addresses, limiting scalability.

Innovation Solution

Implementing virtual network devices that utilize a Layer 2 protocol to transfer data between computing resources, storing local and remote VLAN addresses in a data structure to enable efficient packet routing and scaling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard network devices are used to manage communications between VMs, then basic network functionality is maintained, but the system cannot scale to handle large numbers of VMs

Engineering Contradiction:
ImprovescalabilityVSAvoidnetwork device complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a virtual network device as an intermediary component between VMs and physical network infrastructure. This virtual device manages Layer 2 communications by maintaining address mappings and routing decisions, offloading the complexity from standard physical network devices and enabling scalable VM communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional physical network device mechanisms with a software-based virtual network device that uses data structures (address mappings, routing tables) to manage communications. This substitution allows the system to scale beyond the hardware limitations of standard network devices.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Quantity of substance

If standard network devices support thousands of VLANs and MAC addresses, then basic network capacity is achieved, but they still cannot manage communications between large numbers of VMs

Engineering Contradiction:
Improvenumber of VMsVSAvoidcommunication management reliability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent segments the network communication management function into a dedicated virtual network device that handles Layer 2 operations separately from VM creation. This segmentation allows the virtual device to maintain reliable communication management regardless of the total number of VMs, as it centrally coordinates address mappings and routing decisions.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If virtual network devices are implemented to enable unlimited VM creation, then scalability is achieved, but new components and protocols are required

Engineering Contradiction:
Improveunlimited VM creationVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The virtual network device is designed as a universal component that handles multiple functions: maintaining address mappings, making routing decisions, managing VLAN communications, and supporting both local and remote network segments. This multi-functionality consolidates complexity into a single scalable component rather than requiring separate systems for each function.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9559865B2Virtual network device in a cloud computing environment
Publication Date: 2017.01.31 ATLASSIAN US INC
  • US9559865B2 patent drawing
  • US9559865B2 patent drawing
  • US9559865B2 patent drawing

AI summary

A device, of a cloud computing environment, includes a virtual network device that receives a packet with an address, and determines whether the packet is a broadcast packet or a unicast packet. The virtual network device processes the packet based on whether the packet is a broadcast packet or a unicast packet. The packet is transmitted to local address(es) or remote address(es) when the packet is a broadcast packet. The local address(es) is associated with at least one hardware component of the device, and the remote address(es) is associated with at least one other device, of the cloud computing environment, that is separate from the device. The packet is transmitted based on whether the address, of the packet, matches the local address(es) or the remote address(es) when the packet is a unicast packet.