PIM Null Register Optimization for Multicast Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Protocol Independent Multicast (PIM) protocols face performance issues due to the high number of register messages and states maintained by first hop routers (FHR) and rendezvous points (RP), which can lead to network bottlenecks and reduced scalability, especially in scenarios with a large number of multicast streams.
Innovation Solution
The method involves sending null register messages from the FHR to the RP to request the suppression of register-stop messages and to send multicast stream data in a non-encapsulated format, reducing the number of register states and messages exchanged, and eliminating the need for data register packets and timers, thereby optimizing the register state machine and improving network scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional PIM register messages are used to maintain multicast stream states, then routing accuracy and reliability are improved, but network congestion and processing overhead increase due to the high number of register messages and states
Solution Approach 1:
The patent extracts and eliminates unnecessary register-stop messages and data register packets from the traditional PIM register message exchange process. By removing these redundant message types, the system maintains essential routing reliability while significantly reducing network congestion and processing overhead caused by excessive register messages.
Solution Approach 2:
The patent discards the traditional register-stop message mechanism and recovers routing control through a simplified null register message approach. This allows the system to maintain multicast stream state information without the overhead of continuous register-stop message exchanges, thereby improving network throughput while preserving routing reliability.
2Manufacturing precision
If multiple register states are maintained by FHR and RP to manage multicast streams, then routing precision and control are improved, but device complexity increases due to the number of states and messages exchanged
Solution Approach 1:
The patent extracts only the essential state information needed for multicast routing from the traditional complex register state machine. By removing unnecessary state transitions and message types (register-stop, data register packets), the system maintains routing precision while significantly reducing the complexity of register state management at FHR and RP devices.
Solution Approach 2:
The patent creates a universal null register message format that serves multiple functions: maintaining stream state, requesting suppression of register-stop messages, and enabling non-encapsulated data transmission. This multi-functional approach reduces the number of different message types and states needed, thereby reducing device complexity while preserving routing precision.
3Reliability
If data is sent in encapsulated format through register messages, then protocol compatibility and reliability are improved, but processing overhead and network congestion increase
Solution Approach 1:
The patent performs preliminary action by sending a null register message before transmitting data in non-encapsulated format. This preliminary message establishes protocol compatibility and notifies the receiver of the upcoming non-encapsulated data transmission, ensuring reliable reception while avoiding the overhead of continuous encapsulation and decapsulation operations.
Solution Approach 2:
The patent changes the data transmission parameter from encapsulated to non-encapsulated format after establishing protocol compatibility through the null register message. This parameter change reduces processing overhead and network congestion while maintaining protocol compatibility through the initial null register message exchange.
Data Source
AI summary
An example method includes receiving, by a first hop router (FHR) and from a source device, multicast stream data associated with a multicast stream, sending, from the FHR and to a rendezvous point (RP) using a Protocol Independent Multicast (PIM) protocol, one or more null register messages that are each associated with the multicast stream. Each of the one or more null register messages includes a source address and a group address that are collectively associated with the multicast stream, and each of the one or more null register messages further includes an indication to request that the RP refrain from sending any register-stop messages associated with the multicast stream to the FHR. The example method further includes, after sending the one or more null register messages that are each associated with the multicast stream, sending, to the RP, the multicast stream data in a non-encapsulated format.