TCP Session Mobility in Service Mesh Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service meshes face performance issues due to unnecessary throughput and latency overhead caused by 'hairpinning' network traffic when a node determines it no longer needs to handle the traffic, leading to end-to-end congestion and resource utilization inefficiencies.
Innovation Solution
Implementing TCP session mobility logic in service mesh nodes to transfer state information of existing TCP sessions to downstream nodes, allowing the establishment of new TCP sessions and terminating the original sessions, thereby bypassing nodes that no longer require the traffic, using techniques like Segment Routing and Network Address Translation to ensure seamless traffic rerouting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a service mesh node continues to handle network traffic through a pre-existing TCP session after it no longer needs to, then service integrity is maintained, but unnecessary throughput overhead and latency occur causing end-to-end congestion
Solution Approach 1:
The patent implements dynamic TCP session mobility where the TCP session endpoint can be moved from one service mesh node to another based on real-time routing decisions. This allows the system to adapt to changing traffic patterns and service requirements, enabling nodes to exit sessions when no longer needed and transfer ownership to appropriate downstream nodes, thereby eliminating unnecessary throughput overhead and latency
Solution Approach 2:
The patent extracts the TCP session state information from the original node and transfers it to a downstream node using protocols like Segment Routing and Network Address Translation. This separation allows the original node to exit the session completely, removing it from the traffic path and eliminating the hairpinning effect that causes congestion and latency
2Adaptability or versatility
If network traffic is hairpinned through nodes that no longer need to handle it, then service mesh routing flexibility is maintained, but resource utilization efficiency deteriorates
Solution Approach 1:
The system dynamically determines when a node should exit a TCP session based on L7 information and routing decisions. This dynamic session management allows the service mesh to maintain routing flexibility for necessary traffic while efficiently removing unnecessary nodes from the path, optimizing resource utilization by preventing wasted processing and memory resources on exited sessions
Solution Approach 2:
The patent enables downstream nodes to autonomously establish new TCP sessions with upstream network elements by receiving session state information from upstream nodes. This self-service mechanism allows nodes to independently manage their own session ownership without requiring continuous involvement from upstream nodes, thereby improving resource efficiency while maintaining routing adaptability
Data Source
AI summary
A first node in a service mesh is configured to perform one or more services on network traffic obtained from an upstream network element via a pre-existing Transmission Control Protocol (TCP) session and provide the network traffic obtained from the upstream network element via the pre-existing TCP session to a downstream network element. The first node determines that the first node should no longer obtain the network traffic from the upstream network element via the pre-existing TCP session. In response, the first node provides state information for the pre-existing TCP session to the downstream network element. The downstream network element is configured to establish a new TCP session having the state information for the pre-existing TCP session with the upstream network element and to obtain further network traffic from the upstream network element via the new TCP session. The first node terminates the pre-existing TCP session.