Service Instance Mapping for Cloud Network Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current L2 network technologies, such as TRILL and SPB, are inadequate in supporting a large number of service instances in public cloud environments, particularly in fat tree network architectures, leading to limitations in traffic load balance and network expansion.
Innovation Solution
A service instance mapping method that correlates a layer-2 service instance with a service access port and maps the service instance identifier to a service label, enabling extended service label capabilities through formats like 802.1q and QinQ encapsulation, thereby supporting more service instances and enhancing traffic load balance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If TRILL protocol with 12-bit VLAN ID is used for service instance identification, then the protocol structure is simple and control plane calculation is reduced, but the number of supported service instances is limited to 4094
Solution Approach 1:
The patent transitions from a 12-bit VLAN ID (single dimension) to a 24-bit service instance identifier (extended dimension), exponentially increasing the number of supported service instances from 4094 to 16 million while maintaining the TRILL protocol framework
Solution Approach 2:
The patent changes the identifier parameter from 12-bit VLAN ID to 24-bit service instance identifier, and modifies the encapsulation format to accommodate the extended identifier length, thereby resolving the limitation on the number of service instances
2Quantity of substance
If SPB protocol with 24-bit ISID is used for service instance identification, then the number of supported service instances increases to 16M, but the control plane involves more calculation
Solution Approach 1:
The patent makes the TRILL protocol multi-functional by enabling it to support both traditional 12-bit VLAN IDs and extended 24-bit service instance identifiers, allowing it to achieve SPB-level service instance capacity while maintaining TRILL's simpler control plane characteristics
3Extent of automation
If fixed routing at ingress is used in SPB protocol, then service traffic can be planned globally, but traffic load balance is not optimized and network bandwidth utilization decreases
Solution Approach 1:
The patent introduces dynamic service instance mapping that can adapt traffic distribution based on network conditions, moving from static fixed routing to a more flexible approach that maintains global planning capabilities while optimizing load balance and bandwidth utilization
Data Source
AI summary
Embodiments provide a service instance mapping method, apparatus and system. The service instance mapping method includes: correlating a layer-2 service instance with a service access port of the service instance, and determining correspondence between the service access port and a service instance identifier. The method also includes mapping the service instance identifier to a service label of a packet.