Hybrid Network Traffic Mirroring via ERSPAN-GRE Encapsulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In hybrid network environments, particularly those managed by different cloud providers, existing technologies struggle to forward mirrored traffic between networks due to incompatible communication protocols and restrictions, hindering data analysis and load balancing across these networks.
Innovation Solution
A controller is employed to manage network communication between different networks, translating and encapsulating mirrored traffic using standardized formats like ERSPAN within GRE, enabling seamless forwarding across networks with different protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If native traffic mirroring service is used in one cloud-provider network, then traffic mirroring can be achieved within that network, but the mirrored traffic cannot be forwarded to another service in another cloud-provider network due to protocol incompatibility
Solution Approach 1:
The patent introduces a standardized encapsulation format (ERSPAN within GRE) as an intermediary that translates proprietary traffic mirroring protocols from different cloud providers into a universal format. This mediator layer enables mirrored traffic from one cloud network to be forwarded to services in another cloud network without direct protocol compatibility, resolving the cross-network compatibility issue while maintaining reliable traffic mirroring functionality.
Solution Approach 2:
The patent transforms the traffic mirroring data by changing its protocol parameters through encapsulation. By wrapping the original mirrored traffic in standardized protocol headers (ERSPAN and GRE), the data format parameters are modified to be compatible with different cloud network protocols, enabling universal forwarding across heterogeneous networks while preserving the original mirroring functionality.
2Productivity
If proprietary communication protocols are used by different cloud providers, then each provider can optimize their network performance, but services from different providers cannot communicate with each other
Solution Approach 1:
The standardized encapsulation protocol acts as a mediator between proprietary cloud provider protocols. Each cloud provider can continue using their optimized proprietary protocols internally, while the encapsulation layer translates their mirrored traffic into a universal format that other providers can understand, enabling inter-provider communication without sacrificing internal network performance optimizations.
Solution Approach 2:
The patent creates a universal protocol wrapper (ERSPAN within GRE) that can carry mirrored traffic from any cloud provider regardless of their proprietary protocols. This universal format performs multiple functions: it preserves the original traffic characteristics, adds necessary routing information, and enables compatibility across different provider networks, thus achieving multi-functionality in a single solution.
3Productivity
If traffic mirroring is implemented across hybrid network environments, then data analysis and load balancing can be improved, but protocol incompatibility and forwarding restrictions prevent effective implementation
Solution Approach 1:
The patent simplifies the complexity of cross-protocol traffic mirroring by systematically changing protocol parameters through a standardized two-layer encapsulation approach. Instead of implementing complex custom translation logic for each provider pair, the solution applies a consistent parameter transformation (original protocol → ERSPAN → GRE) that reduces implementation complexity while enabling data analysis and load balancing across hybrid networks.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
This disclosure describes various methods, systems, and devices related to mirrored traffic forwarding in a hybrid network. An example method includes receiving, from a source forwarder in a source network, a mirrored data packet. A session of the mirrored data packet may be identified based on a header of the mirrored data packet. A destination forwarder in a destination network may be identified based on the session. The destination network may be different than the source network. The mirrored data packet may be forwarded to the destination forwarder.