Bridge Identifier Routing for Scalable Network Frames
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current computer networking technologies, such as IEEE 802.1Q and TRILL, face limitations due to the 4096 VLAN identifier constraint, leading to scaling issues and inefficiencies in provider bridge networks, particularly when serving large virtual networks and requiring MAC-in-MAC encapsulation support which is not available in typical rack-mounted bridges.
Innovation Solution
The solution involves routing frames using bridge identifiers, allowing existing rack-mounted bridges to function as edge bridges in networks that require MAC-in-MAC encapsulation, such as TRILL or SPB networks, without the need for hardware support, by utilizing software updates and customized headers to include ingress and egress bridge identifiers within the frames.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MAC-in-MAC encapsulation is used to overcome VLAN identifier limitation, then network scalability is improved, but device complexity increases due to specialized hardware requirements
Solution Approach 1:
The patent replaces the mechanical hardware-based MAC-in-MAC encapsulation with a software-based bridge identifier insertion mechanism. Instead of requiring specialized hardware to perform MAC-in-MAC encapsulation, the invention uses software to insert bridge identifiers directly into frame headers, achieving the same scalability benefit without the hardware complexity
Solution Approach 2:
The patent introduces bridge identifiers as an intermediary element between the VLAN identifier limitation and the need for network scalability. Rather than directly implementing MAC-in-MAC encapsulation which requires complex hardware, the bridge identifier acts as a mediator that enables scalable networking through software processing
2Ease of manufacture
If existing rack-mounted bridges are used without hardware support for MAC-in-MAC, then device cost is reduced, but functionality is limited
Solution Approach 1:
The patent changes the operational parameters of existing bridges by introducing software-based bridge identifier insertion. Instead of requiring hardware changes to enable MAC-in-MAC functionality, the invention modifies the software processing parameters to insert bridge identifiers, allowing existing bridges to function in advanced networking scenarios
Solution Approach 2:
The patent makes existing rack-mounted bridges universal by enabling them to perform bridge identifier insertion through software updates. This allows the same hardware to serve both traditional VLAN networking and advanced networking protocols like TRILL and SPB, achieving multi-functionality without hardware changes
3Productivity
If bridge identifiers are inserted into frames, then routing efficiency is improved, but frame processing complexity increases
Solution Approach 1:
The patent applies preliminary action by inserting bridge identifiers at the ingress bridge before frames enter the core network. This upfront insertion eliminates the need for complex real-time processing at each hop, as core bridges can simply read the pre-inserted bridge identifiers for efficient routing decisions
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods, apparatus, and products for routing frames in a network using bridge identifiers, wherein the network includes a plurality of bridge nodes. At least one of the bridge nodes operates as an ingress bridge node through which frames are received into the network. At least one of the bridge nodes operates as an egress bridge node through which frames are transmitted out of the network. One of the bridge nodes receives, from the ingress bridge node, a frame for transmission to a destination node. The destination node connects to the network through the egress bridge node. The frame includes an ingress bridge identifier and an egress bridge identifier. The bridge that received the frame then routes the frame to the egress bridge node through which the destination node connects to the network in dependence upon the ingress bridge identifier and the egress bridge identifier included in the frame.