Network Path Trace API for Cloud Routing Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for tracing and diagnosing data traffic in network service clouds face limitations, including failure to identify all routing nodes, especially in complex networks like VPC peering connections, and require multiple logins and authentication, leading to security concerns and high resource consumption.

Innovation Solution

An API-based approach that transmits API call requests to identify data routing nodes and generates transmission path objects by retrieving data routing table objects, determining node types and identifiers, and iteratively building the transmission path without the need for agents or extensive authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional traceroute or mtr commands are used for network traffic tracing, then basic routing path information can be obtained, but routing nodes in complex networks (e.g., VPC peering connections) cannot be fully identified and multiple logins/authentication are required

Engineering Contradiction:
Improverouting path identification accuracyVSAvoidauthentication complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces a path trace API as an intermediary between the tracing system and the network routing infrastructure. This API mediator handles authentication and communication with routing nodes, eliminating the need for multiple manual logins while enabling complete identification of routing nodes including those in complex VPC peering connections. The API serves as a centralized interface that simplifies the tracing process while maintaining access to detailed routing information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If traditional tracing methods are used, then some routing information can be obtained, but resource consumption is high and response latency is increased

Engineering Contradiction:
Improverouting path information completenessVSAvoidresponse latency
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by establishing the path trace API connection and retrieving routing table objects before actual traffic tracing is needed. Routing path information is pre-computed and cached, so when tracing is required, the system can quickly retrieve and compare pre-stored routing information with current traffic patterns, significantly reducing response latency while maintaining complete information accuracy.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If multiple logins and authentication are required for tracing, then security can be maintained, but resource consumption increases and operation becomes cumbersome

Engineering Contradiction:
ImprovesecurityVSAvoidtracing operation simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The path trace API serves multiple functions: it handles authentication, retrieves routing table objects, traces traffic paths, and provides diagnostic information all through a single unified interface. This multi-functional API eliminates the need for separate authentication steps and multiple logins, making the tracing operation simple while maintaining security through the API's built-in authentication mechanisms.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11394637B1Methods, apparatuses and computer program products for generating transmission path objects based on data object transmissions in a network service cloud
Publication Date: 2022.07.19 ATLASSIAN US INC
  • US11394637B1 patent drawing
  • US11394637B1 patent drawing
  • US11394637B1 patent drawing

AI summary

Various examples herein described are directed to methods, apparatuses and computer program products configured for tracking, tracing, and/or diagnosing data object transmissions in a network service cloud. In some embodiments, a path finder server entity may transmit one or more Application Programming Interface (API) calls to one or more APIs associated with the network service cloud to obtain one or more data routing table objects, and may determine transmission paths of data objects based at least in part on the data routing table objects.