Inter-AS Trace Route Message Return Path Determination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Service provider networks face challenges in determining a consistent return path for messages across multiple autonomous systems (ASs), leading to performance issues with messages like ping and trace route due to lack of bidirectional segment identifiers and inconsistent reachability information.
Innovation Solution
Network devices modify messages by adding upstream device identifiers and reachability information, allowing them to determine and convey return paths within and across ASs, enabling efficient routing and reducing resource consumption and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network devices use traditional routing methods without bidirectional segment identifiers, then routing information can be distributed based on standard routing protocols, but return path determination becomes inconsistent across autonomous systems
Solution Approach 1:
The patent segments the routing information by introducing bidirectional segment identifiers that separately identify forward and return paths. Each autonomous system can maintain its own segment identifier space, allowing independent routing decisions while ensuring consistent return path determination across AS boundaries.
Solution Approach 2:
The patent performs preliminary action by embedding reachability information and upstream device identifiers in the forward message before it traverses the network. This pre-populated information enables the return message to be routed correctly without requiring real-time path computation or additional signaling.
2Productivity
If network devices forward messages through multiple autonomous systems without upstream device identifiers, then standard routing protocols can be used, but message routing efficiency decreases due to lack of direct return path information
Solution Approach 1:
The patent performs preliminary action by embedding reachability information and upstream device identifiers in the forward message before it traverses the network. This pre-populated information enables the return message to be routed correctly without requiring real-time path computation or additional signaling.
Solution Approach 2:
The patent implements feedback by using the upstream device identifier and reachability information to dynamically determine the optimal return path. The network device receives feedback about the forward path through these identifiers and uses this information to route the return message efficiently, reducing latency.
3Loss of energy
If network devices do not add reachability information to messages, then message processing is simpler, but resource consumption increases due to inefficient routing decisions
Solution Approach 1:
The patent implements self-service by enabling network devices to autonomously determine reachability and populate return path information without requiring external control or additional signaling protocols. Each device independently assesses reachability and makes routing decisions based on the embedded identifiers, reducing overall system resource consumption.
Solution Approach 2:
The patent performs preliminary action by embedding reachability information and upstream device identifiers in the forward message before it traverses the network. This pre-populated information enables the return message to be routed correctly without requiring real-time path computation or additional signaling.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
A network device may receive a message. The network device may determine that the message includes return information indicating a path to an initial device that generated the message. The network device may modify the message by adding an upstream device identifier, wherein the upstream device identifier identifies a device from which the message is received. The network device may modify the message by adding an indication of whether the initial device is reachable by the network device using a segment identifier. The network device may provide the modified message to a downstream device.