Multicast Flow Context Registration for Network Traffic Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network filtering solutions face difficulties in managing and classifying multicast network traffic, as response communications from multiple receiving nodes often replace key attributes, causing them to be placed in different flows, which complicates the association and processing of inbound and outbound traffic.

Innovation Solution

A computing node registers a context for a multicast communication flow, including IP addresses and ports, and modifies the multicast IP address to a local IP address for responses, allowing outbound communications to be associated with the correct flow and processed according to policy rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network filtering solutions use standard addressing attributes to group communications, then unicast communications can be effectively correlated to a single packet flow, but multicast response communications cannot be properly associated with the original flow because receiving nodes replace key attributes

Engineering Contradiction:
Improveflow association accuracyVSAvoidmulticast traffic handling
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the flow association mechanism into two distinct parts: (1) a segment for handling unicast communications using standard addressing attributes, and (2) a segment for handling multicast communications using modified attributes including multicast group ID and context identifiers. This segmentation allows each segment to be optimized for its specific traffic type without interfering with the other.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary flow context structure that acts as a mediator between the incoming multicast communication and the outgoing response communication. This flow context stores the original addressing attributes and creates a mapping relationship, allowing response packets to be correctly associated with their parent flow even when attributes are modified.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If receiving nodes replace addressing attributes in response communications, then nodes can identify themselves in responses, but the responses are placed in different flows making association difficult

Engineering Contradiction:
Improvenode identification in responsesVSAvoidflow management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by creating and storing the flow context before the response communication is generated. The flow context captures the original addressing attributes and establishes the flow association in advance, so when the response communication is later created with modified attributes, the association can be quickly resolved by referencing the pre-stored context rather than performing complex analysis at response time.

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If standard flow association methods are used for multicast traffic, then simple unicast filtering rules apply, but multicast traffic requires special handling to maintain flow context across multiple nodes

Engineering Contradiction:
Improvefiltering rule simplicityVSAvoidflow context information
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The patent creates a universal flow association mechanism that can handle both unicast and multicast traffic through a single standardized interface. The flow context structure is designed to be multi-functional, accommodating both standard unicast addressing attributes and multicast-specific attributes, allowing the same flow management infrastructure to serve multiple traffic types without requiring separate specialized systems.

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

Data Source

PatentUS12068967B2Filtering and classifying multicast network traffic
Publication Date: 2024.08.20 VMWARE INC
  • US12068967B2 patent drawing
  • US12068967B2 patent drawing
  • US12068967B2 patent drawing

AI summary

Described herein are systems and methods to filter and classify multicast network traffic. In one example, a first computing node may receive a multicast communication from a second computing node and register a for a flow associated with the multicast communication, wherein the context includes at least the multicast port associated with the multicast communication. The first computing node further identifies an outbound communication destined for the second computing node and determines that addressing attributes in the outbound communication match the context for the flow. Once it is determined that the attributes match the context for the flow, the first computing node associates the outbound communication with the flow.