On-Demand Multicast Hello Message Transmission
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large multicast deployments, the scalability of Protocol Independent Multicast (PIM) is compromised due to the high frequency of periodic 'Hello' messages sent by each device to announce itself as multicast capable, leading to increased network load and potential inefficiencies.
Innovation Solution
Implementing an on-demand transmission of 'Hello' messages within a local area network (LAN) where multicast-enabled devices only send 'Hello' messages in response to a 'Join' message with a 'Hello Request' indication, thereby minimizing unnecessary neighbor adjacencies and reducing network load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If periodic PIM Hello messages are transmitted by each device to announce multicast capability, then device visibility and neighbor discovery are improved, but network load and message frequency increase significantly
Solution Approach 1:
The patent changes the periodic transmission of Hello messages to event-triggered transmission. Instead of sending Hello messages at fixed intervals (every 30 seconds), devices now send Hello messages only when specific events occur, such as when a device joins the network or when a neighbor relationship needs to be established. This transforms the periodic action into an on-demand action, significantly reducing the quantity of Hello messages in large multicast deployments.
Solution Approach 2:
The patent implements a mechanism where devices autonomously determine when to send Hello messages based on their own state and received messages. When a device receives a Join message or needs to establish a neighbor relationship, it automatically triggers a Hello message transmission without requiring external scheduling or periodic reminders. This self-service approach allows the system to optimize message transmission based on actual network conditions.
2Loss of information
If each device sends Hello messages periodically to all potential neighbors, then complete neighbor lists are maintained, but network traffic and processing overhead increase
Solution Approach 1:
The patent extracts the essential function of Hello messages (neighbor discovery and capability announcement) from the periodic transmission cycle and implements it only when necessary. Instead of maintaining complete neighbor lists through continuous periodic messaging, the system extracts and performs neighbor discovery only when a device needs to join or when a neighbor relationship is being established, thereby reducing network traffic while maintaining the essential information.
Solution Approach 2:
The patent applies partial action by sending Hello messages only to the extent necessary for maintaining functional neighbor relationships. Rather than sending Hello messages to all potential neighbors periodically, the system sends Hello messages only when a device joins or when a neighbor relationship needs reinforcement, performing exactly the amount of action needed without excess.
3Reliability
If PIM Hello messages are transmitted frequently to refresh neighbor lists, then neighbor relationships are maintained, but scalability is compromised in large deployments
Solution Approach 1:
The patent introduces dynamics into the Hello message transmission by making it adaptive rather than static. The transmission frequency and triggering are dynamic, responding to network events such as device joins, leaves, or state changes. This dynamic approach allows the system to maintain neighbor relationships reliably while adapting to the actual needs of the network, thereby improving scalability in large deployments.
Solution Approach 2:
The patent changes the parameter of Hello message transmission from fixed periodic intervals to event-driven timing. By changing this parameter, the system transforms the transmission behavior from a rigid schedule to a flexible, condition-based approach, enabling the system to maintain neighbor relationships while significantly reducing the overall message count and improving scalability.
Data Source
AI summary
In one embodiment, a particular multicast-enabled device on a LAN may determine that it is to send a Join message to an upstream multicast-enabled device that is configured to source multicast data into the LAN. As such, the particular device may transmit a Join message to the upstream device, where the Join message may have a Hello Request indication when there are no downstream multicast neighbors for the upstream device in the LAN, or may not have the Hello Request indication if there is at least one downstream multicast neighbor for the upstream device. Specifically, the Hello Request requests that the upstream device transmit Hello messages onto the LAN. Multicast-enabled devices in the LAN may thus transmit Hello messages in response to receiving a Join message having a Hello Request directed to that particular device, that is, transmitting the Hello messages so long as there is interest in receiving them.