Anycast Control Message Header Rewriting for Routing Accuracy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy control mechanisms and messaging protocols exhibit aberrant behavior in Anycast reliant distributed platforms, leading to incorrect routing of control messages and resulting in packet loss and latency issues due to incorrect identification of the server handling a session.
Innovation Solution
Implementing a control message header rewriting methodology where directors inspect incoming packets to identify control messages originating from intermediary nodes, rewriting the header to ensure correct routing by replacing the source address with the destination address from the offending packet header, allowing the message to reach the correct server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If legacy control mechanisms are used in Anycast reliant platforms, then backward compatibility is maintained, but control messages are incorrectly routed leading to packet loss and latency
Solution Approach 1:
The patent introduces an intermediary mechanism at the PoP level that intercepts and rewrites control messages before they are processed by legacy routing mechanisms. This mediator modifies the control message headers to include correct session identification information, enabling reliable routing without requiring changes to the legacy protocols themselves.
Solution Approach 2:
The invention changes key parameters in the control message headers, specifically adding or modifying session identification fields. By transforming the message parameters to include explicit session context, the system enables accurate routing decisions while maintaining compatibility with the existing legacy protocol structure.
2Speed
If Anycast routing is used to deliver content to closest PoP, then latency is reduced and packet loss decreases, but control messages from intermediary nodes cannot be correctly identified
Solution Approach 1:
The patent segments the control message processing into distinct phases: reception at the PoP, identification of intermediary node messages, extraction of session information, and rewriting of message headers. This segmentation enables clear separation of concerns and systematic handling of control messages.
Solution Approach 2:
The system implements feedback mechanisms where the PoP monitors incoming control messages and actively modifies them based on observed characteristics. The rewritten messages include feedback information about the session context, enabling correct identification and routing of control messages back to the appropriate servers.
Data Source
AI summary
Some embodiments set forth a control message header rewriting methodology. Incoming packets are inspected to identify control messages. Each control message is then inspected to determine whether it originates from a client engaged in a session with a server or from an intermediary node along the path connecting the client and the server. The determination is predicated on a comparison of the addressing provided in the control message header and the addressing provided in the offending packet header, wherein the offending packet is the packet that triggers the intermediary node to issue the control message. If the addressing differs, the header addressing of control message is rewritten using the header addressing of the offending packet. Otherwise, a session table lookup is performed to identify which session the control message is directed to based in part on a hash of the control message header addressing.