Hybrid Multicast Path Tracing With Edge Protocol Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multicast tracing tools, such as mtrace and mtrace2, are inadequate for tracing multicast paths in hybrid networks, particularly in multiprotocol label switching (MPLS) networks and border gateway protocol (BGP) networks, as they do not account for hop-by-hop tracing, proprietary data collection, and network configuration differences.
Innovation Solution
The solution involves intercepting multicast trace requests at edge devices, generating new trace requests compatible with the core network's format, and appending or removing network information to maintain proprietary security, using extended standard resource blocks (eSRBs) to trace paths across heterogeneous networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing multicast tracing tools (mtrace, mtrace2) are used in hybrid networks, then tracing can be performed in simple IP multicast networks, but tracing fails or provides incomplete information in MPLS and BGP networks due to protocol incompatibility and lack of hop-by-hop tracing capability
Solution Approach 1:
The patent introduces an intermediary translation mechanism at network edges that converts standard multicast trace requests into MPLS-specific trace requests and vice versa. This intermediary layer enables compatibility between different network protocols without requiring changes to the core tracing tools, allowing accurate tracing across hybrid networks while maintaining protocol-specific optimizations.
Solution Approach 2:
The tracing system is segmented into multiple components: edge devices that handle protocol translation, core network elements that perform hop-by-hop tracing, and centralized collection points that aggregate trace information. This segmentation allows each component to be optimized for its specific function while working together to provide comprehensive tracing across heterogeneous networks.
2Loss of information
If detailed network information is collected during tracing, then comprehensive path analysis is achieved, but proprietary data security is compromised
Solution Approach 1:
The patent applies local quality by allowing different levels of information collection at different network locations. Core network elements collect detailed local trace information for accurate path analysis, while edge devices and external observers receive aggregated or anonymized data that preserves security. This selective information disclosure maintains both tracing effectiveness and proprietary data protection.
Solution Approach 2:
The system dynamically changes information parameters based on security requirements and tracing needs. Trace data is transformed through various parameter changes including aggregation, anonymization, and selective filtering, allowing comprehensive analysis capabilities while controlling the exposure of sensitive proprietary information through configurable data transformation.
3Measurement precision
If protocol-specific trace requests are generated for core networks, then accurate tracing in MPLS networks is achieved, but device complexity increases due to protocol translation requirements
Solution Approach 1:
The patent implements universality by designing edge devices with multi-functional capabilities that handle multiple protocol types (IP multicast, MPLS, BGP) through a unified translation framework. This universal approach allows single devices to perform protocol translation for different network types without requiring separate specialized systems, reducing overall complexity while maintaining precise tracing accuracy for each protocol.
Data Source
AI summary
Disclosed are systems, apparatuses, methods, and computer-readable media for tracing multicast paths in hybrid networks. A method for tracing multicast paths in hybrid networks includes intercepting, by an edge device, a first multicast trace request transmitted by a first network device that a source device is connected to for tracing a route between the source device to a receiver device, wherein the first network device receives a message from a multicast tracing client to trace a multicast path from the receiver device to the source device; generating a second multicast trace request based on the format for the core network using information from the first multicast trace request; and transmitting the second multicast trace request from an edge network device to the receiver device using the core network, the second multicast trace request including network information related to network performance between the first network device and the edge network device.