Edge Multicast Trace Translation Across Hybrid MPLS and BGP Networks
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 hybrid environments involving Border Gateway Protocol (BGP) networks, as they fail to account for network heterogeneity, proprietary data protection, and hop-by-hop tracing.
Innovation Solution
The solution involves intercepting multicast trace requests at edge devices to generate new trace requests compatible with the core network format, appending or removing network information as necessary to maintain proprietary security, and translating between different network protocols like BGP and MPLS, using extended standard resource blocks (eSRBs) to gather and summarize network performance data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If existing multicast tracing tools (mtrace, mtrace2) are used in hybrid networks, then the tracing process is simple, but the tracing accuracy and completeness deteriorate due to inability to account for network heterogeneity and proprietary data protection
Solution Approach 1:
The patent introduces an edge device as an intermediary between the multicast tracing client and the core network. This edge device intercepts trace requests, translates them into appropriate formats for different network segments (BGP, MPLS, IP multicast), and manages the collection and summarization of trace data. The intermediary handles the complexity of network heterogeneity and proprietary data protection, allowing accurate tracing without requiring the client to directly manage complex network protocols and security constraints.
2Loss of information
If network information is fully collected for comprehensive tracing, then the tracing completeness improves, but the proprietary data security deteriorates
Solution Approach 1:
The patent applies local quality by allowing different levels of information collection and summarization at different network segments. The edge device can selectively collect detailed trace information from customer networks while summarizing or anonymizing data from the service provider's core network. This enables comprehensive tracing where needed (customer premises) while protecting proprietary data in other areas (service provider infrastructure), creating a differentiated information quality approach.
Solution Approach 2:
The tracing system is segmented into distinct functional components: the tracing client, the edge device, and the core network elements. Each segment handles information collection and processing according to its specific requirements and security constraints. The edge device acts as a boundary that segments the tracing process, allowing detailed local tracing while aggregating and protecting core network information.
3Adaptability or versatility
If translation between different network protocols (BGP, MPLS, IP multicast) is implemented, then the adaptability to hybrid networks improves, but the device complexity increases
Solution Approach 1:
The edge device is designed with multi-functionality to handle multiple network protocols (BGP, MPLS, IP multicast) through a single unified interface. Rather than requiring separate tracing mechanisms for each protocol, the edge device can translate and process trace requests across all these protocols through its multiple network interfaces and protocol handling capabilities, reducing overall system complexity while maintaining broad adaptability.
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