Virtual Proxy VPN Switching for Simpler VNF Ethernet Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for connecting virtual Ethernet interfaces of VNFs on IP/MPLS VPNs in data centers are complex, costly, and limit the ability to combine solutions from different service providers, affecting transfer throughput and fault-free operation.
Innovation Solution
Implementing a labeled multiprotocol virtual switching proxy that replaces PE router functions, allowing virtual Ethernet interfaces to be connected through a tunnel identifier associated with a private network, enabling simpler and less expensive communication methods.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If PE routers are used in data center servers to connect virtual Ethernet interfaces of VNFs on IP/MPLS VPNs, then virtual network connectivity is achieved, but implementation complexity increases and transfer throughput performance cannot be guaranteed
Solution Approach 1:
The patent replaces complex PE router implementations with a simplified proxy architecture that copies only the essential VPN tunneling functionality. The proxy implements a lightweight version of VPN tunnel establishment and management, avoiding the full complexity of router implementations while maintaining the core connectivity function.
Solution Approach 2:
The patent extracts the essential VPN tunneling function from the complex PE router system and isolates it into a dedicated proxy component. This separation allows the proxy to handle only VPN-related operations without the overhead of full router functionality, reducing implementation complexity while maintaining reliability.
2Adaptability or versatility
If PE routers with switching tables are deployed to enable VPN tunnel traffic insertion, then virtual Ethernet interfaces can be connected across VPNs, but implementation cost increases significantly
Solution Approach 1:
The proxy is designed with universal functionality that can work with multiple VPN solutions and service providers. It implements a standardized interface for VPN tunnel management that is compatible with different IP/MPLS VPN implementations, allowing operators to combine solutions from different providers without requiring provider-specific complex router configurations.
Solution Approach 2:
The patent replaces expensive, complex PE router infrastructure with simpler, more cost-effective proxy implementations. The proxy uses lightweight data structures and simplified tunnel management mechanisms that reduce hardware and software costs while maintaining the ability to connect virtual Ethernet interfaces across multiple VPNs.
3Productivity
If switching tables are updated each time a remote host is identified to enable VPN traffic routing, then correct traffic delivery is achieved, but transfer throughput performance deteriorates
Solution Approach 1:
The proxy performs preliminary tunnel establishment and routing configuration before actual data traffic flows. Virtual tunnel interfaces are pre-configured with routing information, allowing traffic to be forwarded through established tunnels without requiring real-time switching table updates during data transmission, thus maintaining both correctness and throughput.
Solution Approach 2:
The patent implements nested tunnel interfaces where virtual tunnels are created within the proxy structure. These nested interfaces encapsulate the routing logic, allowing traffic to be directed through pre-established tunnel paths without requiring external switching table modifications, ensuring both accurate delivery and high throughput.
Data Source
Figure 1~3
Figure 4
Figure 5
AI summary
The invention relates, in particular, to a communication method implemented by a virtual proxy, called "source proxy" (PR-S), belonging to a computer system (SI) comprising a virtualisation management system (SGV), a server, in which the source proxy and a host, called "source host" (CE-S), are connected, another server, in which a virtual proxy, called "destination proxy" (PR-D1), and a host, called "destination host" (CE-D1), are connected. Said method comprises the following steps: - executing (E40) a request to configure, on a private network of the source host, a virtual interface, said request comprising a demand to associate a hardware address (CE-S MAC@) of the source host with an identifier associated with an identifier (VPN-ID) of the private network; - sending (E80) the destination proxy an address resolution request transmitted by the source host; - sending (E120) the source host a response to said resolution request, the response comprising a hardware address (CE-D1 MAC@) of the destination host.