17949131. ON-DEVICE LATENCY DETECTION simplified abstract (T-Mobile USA, Inc.)
Contents
- 1 ON-DEVICE LATENCY DETECTION
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 ON-DEVICE LATENCY DETECTION - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 How does this technology impact cybersecurity measures in client-server communications?
- 1.11 What are the scalability limitations of this technology in large-scale network environments?
- 1.12 Original Abstract Submitted
ON-DEVICE LATENCY DETECTION
Organization Name
Inventor(s)
Do Kyu Lee of Mercer Island WA (US)
Tyler Gothmann of Renton WA (US)
Ryan Christopher Lindstrom of Olathe KS (US)
ON-DEVICE LATENCY DETECTION - A simplified explanation of the abstract
This abstract first appeared for US patent application 17949131 titled 'ON-DEVICE LATENCY DETECTION
Simplified Explanation
The present disclosure involves implementing on-device latency detection into the operating system functionality of a client device in client-server and/or network communications. This includes extracting packet headers from data-connection packets transmitted between a local application client and a remote application server, storing data records with packet headers and timestamps, identifying related data-connection packets, comparing timestamps to determine latency measurements, distributing measurements to relevant application clients, presenting measurements in a dashboard display, and using them for server-side dynamic load balancing.
- Extracting packet headers from data-connection packets
- Storing data records with packet headers and timestamps
- Identifying related data-connection packets
- Comparing timestamps to determine latency measurements
- Distributing measurements to relevant application clients
- Presenting measurements in a dashboard display
- Using measurements for server-side dynamic load balancing
Potential Applications
The technology can be applied in various industries such as telecommunications, cloud computing, online gaming, and financial services to monitor and optimize network performance.
Problems Solved
This technology addresses the challenge of detecting and managing latency issues in client-server and network communications, leading to improved user experience and efficient resource allocation.
Benefits
The benefits of this technology include enhanced network performance, real-time latency monitoring, proactive troubleshooting, and optimized server load distribution.
Potential Commercial Applications
The technology can be commercially applied in network monitoring tools, cloud service providers, online gaming platforms, financial trading systems, and any application requiring real-time data transmission with low latency.
Possible Prior Art
One possible prior art could be the use of network monitoring tools that track latency but may not integrate with the operating system level of client devices for real-time detection and load balancing.
Unanswered Questions
How does this technology impact cybersecurity measures in client-server communications?
This article does not delve into the cybersecurity implications of implementing on-device latency detection. It would be interesting to explore how this technology affects the security of data transmissions and potential vulnerabilities it may introduce.
What are the scalability limitations of this technology in large-scale network environments?
The article does not address the scalability challenges that may arise when deploying this technology in extensive network infrastructures. Understanding the limitations and potential solutions for scalability issues would be crucial for widespread adoption.
Original Abstract Submitted
Aspects of the present disclosure relate to implementing on-device latency detection into operating system (OS)-level functionality of a client device in client-server and/or network communications. An example method includes extracting packet headers from data-connection packets transmitted between a local application client and a remote application server. Data records including packet headers and timestamps are stored. Data records for related data-connection packets (e.g., queries and responses, handshakes) are identified via the packet headers, and timestamps of the identified data records are compared to determine latency measurements. Latency measurements are then distributed to relevant application clients locally residing on an upper layer. The latency measurements are presented in dashboard display to an end user and used for server-side dynamic load balancing.
