Papers › A Just-In-Time Networking Framework for Minimizing Request-Response Latency of...

A Just-In-Time Networking Framework for Minimizing Request-Response Latency of Wireless Time-Sensitive Applications

7 Sep 2021arXiv:2109.03032links table onlyarchive 2025-07-28

Lihao Zhang, Soung Chang Liew, He Chen

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

This paper puts forth a networking paradigm, referred to as just-in-time (JIT) communication, to support client-server applications with stringent request-response latency requirement. Of interest is not just the round-trip delay of the network, but the actual request-response latency experienced by the application. The JIT framework contains two salient features. At the client side, the communication layer will 'pull' a request from the client just when there is an upcoming transmission opportunity from the network. This ensures that the request contains information that is as fresh as possible (e.g., a sensor reading obtained just before the transmission opportunity). At the server side, the network ascertains that the server, after receiving and processing the request to generate a response (e.g., a control command to be sent to the client), will have a transmission opportunity at just this time. We realize the JIT system, including the protocol stack, over a Time-Division-Multiple-Access (TDMA) network implemented on a System-on-Chip (SoC) platform. We prove that a TDMA network with a power-of-2 time slots per superframe is optimal for realizing the server-side JIT function. Our experimental results validate that JIT networks can yield significantly lower request-response latency than networks without JIT support can.

PaperPDFCode

Code

leo-cheung-cuhk/openwifi-jit officialmentioned in papermentioned on GitHub report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections