Edge Bridge MAC Frame Transfer for Backbone Network Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current customer MAC frame forwarding techniques in Ethernet communication face issues such as increased processing time and cost due to bulky forwarding tables, limited Service VLAN ID range, cumbersome address management, and the inability to identify terminals with the same destination MAC address across different VLANs within a VPN, as well as complexities in connecting stacked VLAN networks to backbone networks and detecting loops in the backbone network.
Innovation Solution
The proposed method involves an edge Bridge that selectively forwards customer MAC frames based on predetermined Service VLAN IDs, reduces the number of MAC addresses processed in the backbone network, and enables hierarchical management of Service VLANs, allowing for efficient frame switching between specific Service VLANs in the backbone network and Provider VLANs in the stacked VLAN network, while detecting loops and specifying their position.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the backbone network manages all customer network addresses using the same address system, then address management is simplified, but the forwarding table becomes bulky and processing time increases
Solution Approach 1:
The patent segments the address management system into two parts: the backbone network manages only backbone MAC addresses, while customer networks manage their own customer MAC addresses. This segmentation prevents the forwarding table from becoming bulky by excluding customer network addresses from backbone network management, thereby reducing processing time while maintaining simplified address management at each level.
Solution Approach 2:
The patent extracts customer network address management from the backbone network's address management system. By taking out customer MAC addresses from the backbone forwarding table and managing them separately in customer networks, the forwarding table size is reduced, which decreases processing time while keeping the backbone address management simple.
2Ease of operation
If the Service VLAN ID is implemented by 12 bits, then VLAN identification is straightforward, but the possible range is limited to 4,096
Solution Approach 1:
The patent introduces a new dimension to VLAN identification by adding a 4-bit VPN ID field to the existing 12-bit Service VLAN ID structure. This dimensional expansion allows the system to identify up to 4,096 Service VLANs within each of 16 VPNs, providing a total capacity of 65,536 VLANs while maintaining straightforward 12-bit Service VLAN identification within each VPN context.
3Measurement precision
If the Bridge in the backbone network searches for all addresses on the customer network, then complete address resolution is achieved, but processing complexity and cost increase
Solution Approach 1:
The patent segments the address resolution function between backbone Bridges and customer network Bridges. Backbone Bridges only resolve backbone MAC addresses, while customer network Bridges resolve customer MAC addresses. This segmentation maintains complete address resolution accuracy at each level while reducing forwarding processing complexity and cost by eliminating the need for backbone Bridges to search customer network addresses.
Solution Approach 2:
The patent extracts customer MAC address resolution from the backbone Bridge's function. By taking out the resolution of customer MAC addresses from backbone Bridges and assigning it to customer network Bridges, the patent maintains accurate address resolution while significantly reducing the complexity and cost of backbone network processing.
4Reliability
If multiple customer-facing ports are provided for each Service VLAN, then VPN connectivity is ensured, but the number of ports and cables increases
Solution Approach 1:
The patent makes the customer-facing port universal by allowing a single port to handle multiple Service VLANs through the concept of Service VLAN groups. Instead of requiring dedicated ports for each Service VLAN, a single customer-facing port can be configured to access multiple Service VLANs within the same VPN, thereby ensuring VPN connectivity while reducing the number of ports and cables needed.
Data Source
AI summary
An edge Bridge (2A) executes Ethernet encapsulation. Even when redundant MAC addresses are used in the network of a customer, the MAC address of the customer is not referred to in a backbone network (1). Since forwarding is done on the basis of a MAC address added by the edge Bridge (2A), correct forwarding is possible. Additionally, in the edge Bridge (2A), a Service VLAN ID based on the customer-facing port which has received a customer MAC frame and the VLAN ID in the customer MAC frame is added to the customer MAC frame, thereby building a completely closed network for each customer. The customer can belong to a plurality of Service VLANs through a single customer-facing port and select, by a VLAN ID, a Service VLAN to which he/she should belong.