Timestamp Signature Embedding in Protocol Frames
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for inserting timestamp information into packets, especially at higher protocol layers like Layer 7, introduce indeterminate latency due to processing times and interrupts, leading to inaccurate network latency measurements in real-time network traffic environments.
Innovation Solution
A method that embeds a timestamp signature with initialized data in a frame during processing at an upper protocol layer, allowing modification of this data subsequent to error detection code computation at a lower protocol layer, ensuring the error detection code remains valid and minimizing inherent latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If timestamp information is inserted into a packet at an upper protocol layer (e.g., Layer 7) before transmission, then the timestamp can be placed early in the processing pipeline, but the indeterminate processing time and interrupts at multiple protocol layers introduce latency measurement errors
Solution Approach 1:
The patent applies preliminary action by embedding a timestamp signature with initialized data into the packet at the upper protocol layer (Layer 7) during initial processing. This timestamp signature is prepared in advance with placeholder data that will be replaced later with the actual transmission timestamp, allowing the packet to be processed through the protocol stack without waiting for the final timestamp to be available.
Solution Approach 2:
The patent uses an intermediary approach by introducing a timestamp signature structure that acts as a placeholder or mediator between the upper layer processing and the lower layer error detection code computation. This timestamp signature includes both a timestamp field and a corrector field, where the corrector field serves as an intermediary element that can be adjusted to maintain error detection code validity while the timestamp field is updated with actual timing information.
2Measurement precision
If timestamp information is modified after error detection code computation at a lower protocol layer, then accurate latency measurement is achieved, but the error detection code becomes invalid and must be recalculated
Solution Approach 1:
The patent applies parameter changes by modifying the timestamp signature structure to include a corrector field that can be adjusted when the timestamp field is updated. When the timestamp information is changed after error detection code computation, only the corrector field parameter needs to be modified to maintain the validity of the error detection code, rather than recalculating the entire code.
Solution Approach 2:
The patent segments the timestamp signature into two distinct fields: a timestamp field for storing the actual timing information and a corrector field for maintaining error detection code validity. This segmentation allows independent modification of each field - the timestamp can be updated for accurate latency measurement while the corrector field is adjusted separately to preserve the integrity of the error detection mechanism.
3Productivity
If a timestamp signature with corrector field is used to maintain error detection code validity, then packet processing efficiency is improved, but the device complexity increases
Solution Approach 1:
The patent applies universality by designing the timestamp signature structure to serve multiple functions simultaneously: it acts as both a timing marker for latency measurement and as part of the error detection mechanism. The corrector field in the timestamp signature enables the structure to maintain error detection code validity while allowing timestamp updates, eliminating the need for separate error detection recalculation logic.
Data Source
AI summary
Timestamp information can be placed in a frame that includes a first portion processable at a selected layer of a protocol stack and a second portion processable at a lower protocol layer of the protocol stack subsequently to the processing of the first portion, wherein the first portion is contained within the second portion and wherein a numerically computed error detection code for the second portion is computed during processing of the second portion. A timestamp signature having a timestamp subfield of initialized data and a corrector subfield of initialized data is embedded in the first portion during processing thereof at the selected protocol layer. A numerical constant functionally equivalent to the numerically computed error detection code is determinable from the initialized data in the timestamp subfield and the corrector subfield. The data in said timestamp subfield is modified with timestamp information subsequently to processing of the second portion at the lower protocol layer. The data in the corrector subfield is then modified such that the numerical constant as determinable from the modified data in the timestamp subfield and the corrector subfield remains unchanged, whereby the numerically computed error detection code computed at the lower protocol layer remains valid.