Hierarchical Network Management via Provider Backbone Bridges
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network architectures, particularly in provider backbone bridges, face limitations in scalability and management due to rigid VLAN restrictions and the need for global validity of service tags, which restricts network flexibility and increases complexity.
Innovation Solution
A hierarchical network system is established using Provider Backbone Bridges, where each layer is partitioned into domains, allowing local management of service tags and MAC addresses, enabling independent allocation and mapping of tags between layers, thereby simplifying network management and enhancing scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If global validity of service tags is enforced in provider backbone bridges, then network reliability is improved, but device complexity and scalability are worsened
Solution Approach 1:
The patent divides the network into hierarchical layers (access layer, aggregation layer, backbone layer) with independent domain management. Each layer maintains its own service tag namespace, allowing local independence while ensuring reliability through hierarchical coordination. This segmentation eliminates the need for global service tag validity enforcement across the entire network.
Solution Approach 2:
The patent introduces a hierarchical dimension to network management, transitioning from flat global management to multi-level domain management. Service tags are managed independently at each hierarchical level, with mapping relationships established between layers. This dimensional change allows each domain to operate autonomously while maintaining overall network reliability through structured interaction between layers.
2Reliability
If rigid VLAN restrictions are applied in provider backbone bridges, then network security is improved, but adaptability and scalability are worsened
Solution Approach 1:
The patent implements dynamic service tag allocation and mapping at each hierarchical level. Service tags are no longer rigidly restricted but can be dynamically assigned and mapped according to local domain requirements. This dynamic mechanism maintains security through controlled access at each layer while enabling adaptability through flexible tag management across the hierarchical network.
Solution Approach 2:
The patent changes the parameter of service tag management from static/global to dynamic/local. Each domain can independently allocate and manage service tags according to its specific needs, while the hierarchical structure ensures security through controlled parameter changes at each level. This parameter transformation enables both security and adaptability simultaneously.
3Reliability
If extensive MAC address learning is required across the network, then network reliability is improved, but loss of time and productivity are worsened
Solution Approach 1:
The patent segments MAC address learning into local domain scope rather than requiring network-wide learning. Each hierarchical domain maintains its own MAC address table, learning only addresses within its domain. This segmentation dramatically reduces the time and resources required for MAC address learning while maintaining reliability through localized forwarding decisions.
Solution Approach 2:
The patent introduces hierarchical mapping relationships as intermediaries between layers. Instead of requiring extensive MAC address learning across the entire network, the system uses mapping tables at each layer to translate between local and remote addresses. This intermediary mechanism maintains reliability through proper address translation while significantly reducing the time and complexity of MAC address learning.
Data Source
AI summary
A method for establishing a hierarchical network with Backbone Provider Bridges includes: dividing the network into a plurality of layers, and partitioning each layer into at least one domain; each domain assigning a service tag for itself; a local domain sending a mapping request including a user type ID to a further domain in the same layer; the further domain in the same layer returning a service tag corresponding to the user type ID to the local domain; the local domain establishing and saving a mapping relationship; and edge devices of each domain learning MAC addresses. Further, a system and device having the same are also provided in the disclosure.