Hardware Trapping for Link-Local Multicast Flood Suppression
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Networking protocols like mDNS and DHCP generate large amounts of link-local multicast or broadcast traffic, leading to degraded network performance and reduced reliability, particularly in wireless networks.
Innovation Solution
Implementing a network device with a data plane that drops multicast and broadcast messages in hardware while copying them to the CPU for software processing, using TCAM entries to trap and proxy messages, thereby reducing the need for local flooding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If link-local multicast and broadcast transmissions are used for protocols like mDNS and DHCP, then service discovery and dynamic IP assignment functions are enabled, but network performance degrades and overhead increases due to large amounts of traffic flooding
Solution Approach 1:
The patent extracts the flooding function from the data plane to the control plane. The data plane drops link-local multicast and broadcast messages instead of flooding them, while the control plane selectively forwards only necessary messages. This separation removes the harmful flooding effect while preserving the essential service discovery and IP assignment functions.
Solution Approach 2:
The control plane acts as an intermediary between the data plane and the network segments. It receives dropped messages from the data plane, processes them selectively, and forwards only necessary messages to appropriate network segments. This intermediary function reduces unnecessary traffic flooding while maintaining protocol functionality.
2Reliability
If link-local multicast and broadcast messages are flooded throughout local network segments, then protocol messages are delivered to all nodes, but network overhead increases and reliability decreases
Solution Approach 1:
The patent applies different handling rules to different types of messages in the control plane. Instead of uniformly flooding all link-local multicast and broadcast messages, the control plane analyzes each message type (mDNS, DHCP, etc.) and forwards only those that are necessary for specific network segments. This selective forwarding reduces network overhead while maintaining reliable delivery where needed.
3Adaptability or versatility
If all link-local multicast and broadcast messages are processed by software, then message handling is flexible, but processing overhead increases significantly
Solution Approach 1:
The patent segments the message processing function into two parts: the data plane handles the bulk of message dropping in hardware for efficiency, while the control plane handles selective forwarding for flexibility. This segmentation allows the system to maintain adaptability through control plane processing while reducing overall processing overhead through data plane hardware filtering.
Solution Approach 2:
The patent replaces pure software processing with a hybrid hardware-software system. The data plane uses hardware-based filtering and dropping mechanisms to handle the majority of messages, substituting software processing with faster hardware operations for the common case, while retaining control plane software for complex decision-making.
Data Source
AI summary
Techniques for suppressing the flooding of link-local multicast and broadcast traffic are provided. In certain embodiments, these techniques include receiving, by a network device, a link-local multicast or broadcast message from an endpoint, where the message pertains to a networking protocol that uses link-local multicast and/or broadcast transmissions; dropping, by a data plane of the network device, the message in hardware, such that the message is not flooded on the local network segment of the endpoint; copying, by the data plane, the message to the device's central processing unit (CPU); and processing, by software running on the CPU, the message in accordance with the message's networking protocol (and in a manner that eliminates the need to flood the message).


