QoS Behavior Encapsulation in Tunnel Endpoints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network devices face complexity in maintaining Quality of Service (QoS) behavior across tunnel endpoints, as they often require re-deriving QoS policies at destination networks, which can lead to inconsistent service quality and increased operational complexity.
Innovation Solution
The solution involves encapsulating QoS behavior within a tagging packet frame and an outer tunnel transport header by the source tunnel endpoint, allowing the same QoS behavior to be applied across intermediate networks without re-derivation at the destination endpoint, using protocols like VXLAN or GRE over L3 networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network devices re-derive QoS policies at destination networks, then QoS behavior can be adapted to local policies, but operational complexity increases and service consistency deteriorates
Solution Approach 1:
The source tunnel endpoint performs preliminary action by deriving and encapsulating the QoS behavior before the packet traverses the tunnel. This advance preparation eliminates the need for destination endpoints to re-derive QoS policies, reducing operational complexity while maintaining policy adaptability through the encapsulated behavior information
Solution Approach 2:
The source tunnel endpoint creates a copy of the derived QoS behavior and encapsulates it within the packet metadata. This copied behavior information is then transported to the destination endpoint, allowing it to apply the same QoS behavior without re-deriving it from local policies, thus reducing complexity while maintaining adaptability
2Adaptability or versatility
If QoS behavior is re-derived at destination endpoints, then local customer policies can be applied, but service consistency across tunnel endpoints deteriorates
Solution Approach 1:
The source tunnel endpoint creates a copy of the derived QoS behavior and encapsulates it within the packet metadata. This copied behavior information is then transported to the destination endpoint, allowing it to apply the same QoS behavior without re-deriving it from local policies, thus reducing complexity while maintaining adaptability
Solution Approach 2:
The QoS behavior derivation and application process is segmented into distinct phases: derivation at the source endpoint, encapsulation in metadata, transport through the tunnel, and application at the destination endpoint. This segmentation allows each endpoint to perform its specific function while maintaining overall service consistency through the encapsulated behavior information
3Stability of the object's composition
If QoS behavior is encapsulated in tagging packet frames, then service consistency improves, but device complexity increases
Solution Approach 1:
The encapsulation mechanism uses universal tagging packet frames (such as IEEE 802.1Q tags) that can carry QoS behavior information across different tunnel protocols and network infrastructures. This universal approach maintains service consistency while avoiding protocol-specific complexity, as the same encapsulation method works across VXLAN, GRE, MPLS, and other tunneling protocols
Solution Approach 2:
The tagging packet frame acts as an intermediary carrier that transports QoS behavior information from the source endpoint through the tunnel to the destination endpoint. This intermediary structure simplifies the encapsulation process by providing a standardized container that naturally integrates with existing network infrastructures, reducing the complexity of implementing service consistency
Data Source
AI summary
In general, techniques are described for provisioning Quality of Service (QoS) behavior on tunnel endpoints. For example, a network device operating as a source tunnel endpoint, e.g., a provider edge (PE) device, may encapsulate a QoS behavior that was derived by the PE device upon receiving the packet from a source network (e.g., a customer or tenant network) and send the encapsulated packet through the tunnel across one or more intermediate networks (such as data center networks) to the destination tunnel endpoint such that the destination tunnel endpoint may apply the same QoS behavior derived by the source tunnel endpoint when injecting the original packet into a destination network (e.g., a second network of the customer or tenant) without having to re-derive the QoS behavior from customer/tenant QoS policies for the destination network.