HTTP Trace Location Headers for Cross-Layer Network Parsing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing distributed tracing systems struggle to trace across network layers beyond the application layer due to network switches' inability to parse variable-length HTTP headers, limiting the evaluation of delays in transport and network layers.
Innovation Solution
The method involves adding fixed-length location information (custom headers) in predetermined positions within packets to guide network switches in accessing trace information, allowing tracing across multiple network layers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If distributed tracing is implemented using HTTP headers in microservices architecture, then application layer tracing is achieved, but network switches cannot parse variable-length HTTP headers to trace across transport and network layers
Solution Approach 1:
The patent segments the tracing information into two parts: location information (fixed-length) placed in the packet header, and actual trace information (variable-length) placed in the HTTP header. Network switches only need to parse the fixed-length location information, while application layer components handle the full trace information. This segmentation resolves the contradiction by enabling network layer tracing without requiring switches to parse variable-length HTTP headers.
Solution Approach 2:
The patent introduces location information as an intermediary element that bridges the network layer and application layer. This fixed-length marker acts as a mediator that network switches can easily parse to identify the position of trace information in HTTP headers, without requiring switches to understand or parse the variable-length HTTP header structure itself.
2Measurement precision
If network switches parse variable-length HTTP headers to access trace information, then comprehensive tracing across all network layers is achieved, but processing complexity and time increase
Solution Approach 1:
By segmenting the tracing system into location information (for network layer) and trace information (for application layer), the patent enables network switches to quickly locate trace data without parsing the entire variable-length HTTP header. This significantly reduces packet processing time while maintaining comprehensive tracing coverage across all network layers.
Solution Approach 2:
The patent performs preliminary action by placing fixed-length location information in the packet header before the variable-length HTTP header. This allows network switches to quickly access the position of trace information without having to parse through the entire HTTP header, thereby reducing processing time while maintaining complete tracing capability.
3Loss of information
If fixed-length location information is added to packets to enable network switch parsing, then tracing across network layers is enabled, but packet size increases
Solution Approach 1:
The patent changes the parameter of location information from variable-length (if embedded in HTTP headers) to fixed-length (placed in packet headers). This parameter change enables network switches to efficiently parse and access trace information without the complexity of variable-length parsing, while the fixed-length format minimizes the increase in packet size compared to embedding full trace information in the packet.
Data Source
AI summary
A first communication node includes, in a first message generated by a first application addressed to a second communication node, a first communication node for tracking said first message among a plurality of communication nodes, and adding location information indicating the location of the first trace information to a predetermined position before the first message in the first packet containing the first message, transmit the first packet to which the first trace information and the location information have been added.