Network Tunnel Header Embedding Tenant Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current traffic engineering techniques, such as MPLS, do not readily support encapsulating tenant identifiers, requiring additional policies and multiple encapsulations for overlay and underlay networks, which complicates data message flow management in multi-tenant environments.
Innovation Solution
A method that embeds a specific path for a tenant's data message flow through network tunnel headers, placing the outer tunnel header outside layers 2-4 headers, and uses this path information to direct the flow, selecting paths based on classification operations and contextual attributes, and includes tenant identifiers to specify associated tenants.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MPLS techniques are used for traffic engineering, then path descriptive information can be added between layers 2 and 3 headers, but tenant identifiers cannot be encapsulated and multiple encapsulations are required for overlay and underlay
Solution Approach 1:
The patent combines path descriptive information and tenant identifiers into a single tunnel header structure. Instead of using separate MPLS labels for path identification and separate encapsulations for tenant identification, the invention merges these functions into one unified Geneve tunnel header that carries both the path identifier and tenant identifier fields simultaneously, eliminating the need for multiple encapsulations.
Solution Approach 2:
The tunnel header is designed as a universal structure that performs multiple functions: it provides path identification for traffic engineering, encapsulates tenant identifiers for multi-tenant environment support, and enables single-encapsulation forwarding. This multi-functional header replaces the need for separate MPLS label stacking and multiple encapsulation layers.
2Adaptability or versatility
If multiple encapsulations are used for overlay and underlay, then tenant identification is possible, but data message flow management becomes complicated
Solution Approach 1:
The patent extracts the tenant identification function from the complex multi-layer encapsulation structure and places it directly into the tunnel header. By taking out the tenant identifier field and positioning it at the appropriate layer in the single-encapsulation structure, the invention simplifies flow management while maintaining tenant identification capabilities.
Solution Approach 2:
Instead of adding multiple encapsulation layers to achieve tenant identification (which complicates flow management), the invention inverts the approach by implementing tenant identification within a single encapsulation layer. This reverses the traditional overlay-underlay model by integrating both path and tenant information at the same encapsulation level.
3Productivity
If path information is embedded in tunnel headers, then efficient routing is achieved, but additional header processing is required
Solution Approach 1:
The patent performs preliminary classification and path selection operations at the ingress node before encapsulation. By pre-determining the path based on classification operations and embedding the complete path identifier in the tunnel header, the invention enables efficient traffic-engineered routing while minimizing in-transit header processing, as intermediate nodes only need to forward based on the pre-computed path identifier.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
Traffic engineering refers to a process by which a network administrative program defines specific paths through the network for a series of data message flows. The approaches used to date include MPLS (multiprotocol label switching) techniques that add path descriptive information between layers 2 and 3 headers. Because of this location of the path description, MPLS is commonly referred to as a layer 2.5 protocol. The MPLS techniques, and other previous traffic engineering techniques, however do not readily support encapsulating tenant identifiers. Tying these prior solutions to a tenant will require other policies and multiple encapsulations for the overlay and underlay.