Gateway Server Network Latency Measurement via DNS and TLS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile Network Operators (MNOs) lack a completely internal method to measure network latency of their wireless carrier networks, relying on third-party services with proprietary algorithms, making it difficult to verify measurement accuracy.
Innovation Solution
Implementing a latency measurement application on a gateway server that uses Domain Name System (DNS) and Transport Layer Security (TLS) handshake events to calculate network latency, allowing MNOs to independently assess their network latency by tracking timestamps of DNS and TLS messages within their internal network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If MNOs use third-party network performance assessment service providers to measure network latency, then network latency measurement capability is provided, but measurement accuracy cannot be verified due to proprietary algorithms
Solution Approach 1:
The patent introduces an intermediary mechanism by having the gateway server capture and record timestamps of DNS response messages and TLS handshake messages. These timestamps serve as verifiable intermediaries that allow the MNO to independently calculate network latency without relying on third-party proprietary algorithms, thus resolving the contradiction between obtaining measurement capability and verifying accuracy.
2Reliability
If MNOs implement internal network latency measurement using DNS and TLS events, then measurement verification capability is improved, but device complexity increases due to gateway server requirements
Solution Approach 1:
The gateway server is designed to perform multiple functions: it serves as a standard network gateway for routing traffic while simultaneously functioning as a measurement instrument by capturing DNS and TLS timestamps. This multi-functionality reduces the need for separate dedicated measurement devices, thereby mitigating the increase in device complexity while improving measurement verification capability.
3Device complexity
If conventional TCP signaling methods are used to measure network latency, then measurement methodology is simple, but visibility to wireless carrier network events is lost
Solution Approach 1:
The patent extracts the measurement function from the complex TCP signaling process by using DNS response messages and TLS handshake messages as separate, identifiable events. These extracted events provide clear visibility points within the wireless carrier network where timestamps can be captured, maintaining measurement simplicity while improving visibility to network events.
Data Source
AI summary
A first time that a Domain Name System (DNS) response message is sent by the gateway server of a network to a user device may be determined, the DNS response message being generated by a Local DNS server of the network in response to a DNS request message from the user device for routing via the gateway server to the user device. A second time that a client handshake message for an external server identified by a network address in the DNS response is received at the gateway server may be determined, in which the client handshake message is sent by the user device. A roundtrip time for the network that is a time difference between the first time and the second time is calculated. The roundtrip trip time is then halved to obtain a network latency time measurement for the network.