Xwapseries.lat - Vaishnavy And Sharun Raj P15 H...

| Concept | Description | Relevance to XWapseries.Lat | |---------|-------------|-----------------------------| | Latency‑Aware Protocol (XWap‑Lat) | A thin adaptation layer placed between the transport (QUIC/TCP) and the application. It tags each packet with a deadline and a priority based on the predicted latency. | Enables the scheduler to drop, reorder, or compress low‑priority frames before the deadline expires. | | ARMAX Prediction Engine | Utilises recent RTT measurements, RSSI, AP load, and device CPU usage to forecast latency 10–30 ms ahead. | Drives the deadline assignment in XWap‑Lat. | | Edge‑Compute Offloading | Dynamically decides whether a compute‑intensive task (e.g., video transcoding) should run on‑device, on the edge, or in the cloud, based on current latency budget. | Guarantees that offloaded tasks complete before the next frame deadline. | | Adaptive Redundancy (AR) | Sends a duplicate of the most critical packets only when the confidence in latency prediction drops below a threshold. | Improves reliability without a permanent bandwidth overhead. | | Energy‑Aware Scheduling | Uses CPU frequency scaling and radio power state transitions coordinated with the latency model to minimise energy draw. | Achieves the observed ~30 % power saving. |

XWapseries.Lat seeks to pre‑empt latency degradation by: XWapseries.Lat - Vaishnavy And Sharun Raj P15 H...

| Approach | Latency (95 pct) | Energy Impact | Remarks | |----------|------------------|---------------|---------| | Standard QUIC | 82 ms | 0 % | Baseline | | BBR Congestion Control | 71 ms | –2 % | Improves throughput but not latency predictability. | | MPTCP with Scheduler | 64 ms | –5 % | Reduces loss but adds complexity. | | XWapseries.Lat (P15 H) | 38 ms | –30 % | First work to combine predictive scheduling with edge‑offload and adaptive redundancy. | | Concept | Description | Relevance to XWapseries