Anycast Edge Server Response Packet Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional direct server return (DSR) methods in network communications prevent intermediate devices from performing OSI Layer 7 filtering and additional security features on response traffic, as response packets are not routed back through the same intermediate device as request packets, limiting security and content inspection capabilities.
Innovation Solution
Incorporating edge servers with shared anycast IP addresses that modify request packets with identifying information, allowing response packets to be routed back through the edge server network, where they can be inspected and secured before being sent to the client, using techniques like IPv4 source-routing or IPv6 flow-labels, and encapsulation methods like GRE to redirect packets to the edge server network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If direct server return is used to send response packets directly to requesting devices, then network traffic efficiency is improved, but security and content inspection capabilities are worsened because response packets bypass intermediate devices
Solution Approach 1:
The patent introduces an intermediary mechanism (anycast routing with embedded edge server identifiers) that allows response packets to be redirected through edge servers without breaking the direct server return model. The edge server identifier embedded in the response packet acts as a mediator that enables security inspection while maintaining efficient routing.
2Speed
If response packets are routed directly to client devices, then response time is reduced, but the ability to perform OSI Layer 7 filtering and security features is lost
Solution Approach 1:
The patent applies preliminary action by embedding the edge server identifier in the request packet before it reaches the origin server. This pre-prepared identifier enables the origin server to route the response through the correct edge server for security inspection, ensuring that filtering capabilities are available when needed without adding delay to the response path.
3Reliability
If edge servers use shared anycast IP addresses, then load distribution and redundancy are improved, but packet routing complexity increases due to the need for identifying information
Solution Approach 1:
The patent applies local quality by embedding specific identifying information (edge server identifiers) within the packet headers at local edge servers. This allows each edge server to be uniquely identified despite sharing the same anycast IP address, enabling precise routing decisions without requiring complex global routing changes.
Data Source
AI summary
A first edge server of multiple edge servers of a distributed edge computing network receives a request from a client device regarding a resource hosted at an origin server according to an anycast implementation. The first edge server modifies the request to include identifying information for the first edge server prior to sending the request to the origin server. The origin server responds with a response packet that includes the identifying information of the first edge server. Instead of routing the response packet to the client device directly, one of the multiple edge servers receives the response packet due to the edge servers each having the same anycast address. If the edge server that receives the response packet is not the first edge server, that edge server transmits the response packet to the first edge server, who processes the response packet and transmits the response packet to the client device.