Trunk Endpoint Tag Translation for E-Tree Service Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions struggle to properly forward Ethernet frames across multiple network domains while maintaining the E-Tree service rules, as they fail to differentiate between root and leaf frames at network-to-network interfaces, leading to improper forwarding and potential leaf-to-leaf communications.
Innovation Solution
Implementing a system with trunk end points that perform tag translation for root and leaf tags across domains, ensuring that frames are correctly identified and forwarded according to E-Tree service rules, and using different VLAN tags to distinguish between root and leaf frames, thereby preventing leaf-to-leaf communications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing forwarding solutions are used across multiple network domains, then frame forwarding simplicity is maintained, but E-Tree service rules compliance deteriorates due to inability to differentiate root and leaf frames
Solution Approach 1:
The patent introduces trunk end points as intermediary devices at network-to-network interfaces that perform tag translation between different VLAN tag formats (IEEE 802.1Q and Provider Bridge). These intermediaries enable proper E-Tree service rules compliance by translating tags to differentiate root and leaf frames across domain boundaries, without requiring complex changes throughout the entire network.
Solution Approach 2:
The patent changes the VLAN tag parameters at network boundaries by translating between different tag formats and formats. This parameter transformation allows frames to maintain their root or leaf identification across domain boundaries while adapting to different network domain requirements, ensuring E-Tree service rules compliance without uniform complexity throughout the network.
2Adaptability or versatility
If uniform VLAN tagging is used across all network domains, then implementation simplicity is improved, but adaptability to different network domain standards deteriorates
Solution Approach 1:
The patent applies parameter changes by translating VLAN tags between different formats (IEEE 802.1Q and Provider Bridge) at network boundaries. This allows each network domain to maintain its native tagging standard while ensuring interoperability across domains through the translation mechanism at interface points.
Solution Approach 2:
The patent segments the network into multiple domains with independent tagging standards, with tag translation occurring only at the boundary interfaces. This segmentation allows each domain to operate with its own simplified uniform tagging while achieving overall network adaptability through the modular translation approach at boundaries.
3Reliability
If tag translation is implemented at all network interfaces, then E-Tree service compliance is improved, but processing overhead increases
Solution Approach 1:
The patent places tag translation functionality specifically at trunk end points (intermediary devices) at network-to-network interfaces rather than at every network interface. This targeted placement ensures E-Tree service compliance only where domain boundaries require translation, minimizing unnecessary processing overhead at interfaces that don't require translation.
Data Source
AI summary
A network apparatus comprising a trunk end point associated with an Ethernet-tree (E-Tree) service in a network domain and configured to forward a frame that comprises a tag according to the tag in the frame, wherein the tag in the frame is a root tag that indicates a root source of the frame or a leaf tag that indicates a leaf source of the frame, and wherein the trunk end point is coupled to a second end point associated with the E-tree service outside the network domain.