Traffic Replication Node for Load-Balanced Packet Mirroring

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current traffic mirroring technologies deploy the traffic mirroring process on the same node as the load balancer or cloud service application, leading to resource occupation and low efficiency in traffic replication.

Innovation Solution

Introduce a traffic replication node that receives traffic replication rules and generates new service packets based on these rules, replicating traffic without occupying resources on the load balancer or computing nodes, thus providing a dedicated computing resource for efficient traffic replication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the traffic mirroring process is deployed on the same node as the load balancer or cloud service application, then the traffic replication function can be implemented, but it occupies resources of the load balancer or cloud service application and causes low efficiency of traffic replication

Engineering Contradiction:
Improvetraffic replication efficiencyVSAvoidresource occupation
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the traffic mirroring function from the load balancer and cloud service applications by deploying it on a dedicated traffic replication node. This separation allows the traffic replication process to operate independently without consuming resources of the original systems, thereby improving traffic replication efficiency while reducing resource occupation on critical infrastructure components.

Inventive Principle:
Principle #1Segmentation

2Productivity

If the traffic mirroring process is deployed on the same node as the load balancer or cloud service application, then the traffic replication function can be implemented, but it causes low efficiency of traffic replication

Engineering Contradiction:
Improvetraffic replication efficiencyVSAvoidtraffic replication time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

By segmenting the traffic mirroring process onto a dedicated node, the system eliminates resource contention and processing delays that occur when multiple functions share the same infrastructure. This dedicated deployment reduces traffic replication time and improves overall productivity of the replication operation.

Inventive Principle:
Principle #1Segmentation

3Productivity

If the traffic mirroring process occupies resources on the load balancer or cloud service application, then the traffic replication can be performed, but service stability is compromised

Engineering Contradiction:
Improvetraffic replication capabilityVSAvoidservice stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent extracts the traffic mirroring process from the load balancer and cloud service application infrastructure, moving it to a dedicated traffic replication node. This extraction eliminates the harmful effect of resource occupation on service stability while preserving the traffic replication capability, thereby improving system reliability without sacrificing productivity.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20260052104A1Load balancing-based traffic replication method and apparatus, and traffic replication node
Publication Date: 2026.02.19 HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
  • US20260052104A1 patent drawing
  • US20260052104A1 patent drawing
  • US20260052104A1 patent drawing

AI summary

This application discloses a load balancing-based traffic replication method and apparatus, and a traffic replication node, and relates to the field of cloud computing technologies. In this application, a traffic replication node is disposed in an infrastructure. The traffic replication node receives a traffic replication rule configured by a user, where the traffic replication rule includes an IP address of a first computing node and an IP address of a second computing node. The traffic replication node receives a first service packet sent by a load balancer node, sends the first service packet to the first computing node based on a destination IP address of the first service packet, generates a second service packet based on the first service packet and the traffic replication rule, and sends the second service packet to the second computing node based on a destination IP address of the second service packet.