Searcharxiv⌕ Search
Home/Archive/arXiv

arXiv · 2604.07889

Design and empirical validation of a stock-Android software architecture for Wi-Fi Direct multi-group communication

Kwasi Edward·Wayne Goodridge·Koffka Khan·Amit Ramkissoon
View original source ↗Read source document ↗Export metadata ↓

Abstract

Context: Stock Android exposes Wi-Fi Direct peer-to-peer APIs, but it does not provide application-transparent communication across multiple Wi-Fi Direct groups. For developers working on non-rooted devices, the main obstacle is architectural: interface-specific transport contexts, relay roles, and forwarding state must be coordinated entirely at application level. Objectives: This paper investigates whether multi-group Wi-Fi Direct communication can be realized as a stock-Android software architecture while preserving forwarding-state consistency and remaining compatible with Android 11 devices without rooting or operating-system modification. Methods: We design SWARNET, a layered artifact composed of a Flutter application layer, a Kotlin native networking layer, interface-bound P2P and legacy-Wi-Fi sockets, relay-state management, and subscription-based forwarding tables. We evaluate the implemented artifact on five stock Samsung Galaxy A10s smartphones across four single-group and multi-group scenarios using archived throughput and packet-loss measurements. Results: The artifact remained operational in all four scenarios. Peak receiver throughput observed from the archived curves was approximately 19.7~Mbit/s in 2d1g, 17.9~Mbit/s in 3d1g, 16.1~Mbit/s in 4d2g, and 16.0~Mbit/s in 5d3g. Packet loss increased with forwarding complexity, reaching about 19--20\% only in the highest-load region of the three-group case. Conclusion: The contribution is an implementable software architecture and a feasibility study showing that stock-Android multi-group Wi-Fi Direct communication can be engineered at application level on non-rooted devices. The results support architectural feasibility in a small static testbed; they do not establish broad resilience, scalability, or deployment readiness.

Explore related subjects

cs.NI

Keep this discovery

BibTeXRIS

Kwasi Edward, Wayne Goodridge, Koffka Khan, Amit Ramkissoon. 2026-04-09. Design and empirical validation of a stock-Android software architecture for Wi-Fi Direct multi-group communication. https://arxiv.org/abs/2604.07889

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

arXiv2026

Message-Level Scheduling for RLNC-Coded Multi-Source Traffic

This paper studies weighted decoding-delay minimization for multiple RLNC-coded message streams that compete for finite processing capacity at a destination. Packet arrivals are exogenous, while the scheduler only determines the processing order of packets already available at the destination. A trace-conditioned offline scheduling formulation shows that a batch-release subclass is strongly NP-hard even with a single processing unit. Message-Aware Innovation-Deficit Scheduling (MAIDS) is then developed to prioritize each serviceable message according to its weight and remaining decoding deficit. For a single processing unit, MAIDS is shown to be exactly optimal under nonblocking progressive arrivals with equal weights and under common activation with arbitrary positive weights, while the unrestricted weighted online problem admits no universal deterministic $O(1)$ competitive ratio. Simulation results on streaming and batch benchmarks show that MAIDS consistently reduces weighted decoding delay relative to the tested baselines, remains close to the offline optimum on average, and recovers the predicted exact performance boundaries.

cs.NI↗
arXiv2026

The Towers Were Standing: A Cause Decomposition of Cellular Outages During Hurricane Helene

Hurricane Helene produced the largest absolute cell-site outage in the public FCC record, peaking at 4562 sites. The conventional model is physical: towers destroyed. Helene did destroy over 1700 miles of fibre, but almost none of it was cell sites. We present the first cause-decomposed study of the FCC's Disaster Information Reporting System, reconstructing 80 state-days and 580 county-days from 24 daily filings by two reconciled independent extractions. Damage to cell sites is negligible: 1.1% of attributed cell-site-days across six states, at most 3.8% anywhere. The sites were standing. What took them out divides by terrain: pooled, power dominates at 63.2%, but in mountainous North Carolina severed transport (backhaul) reaches 52.2% against 47.3%, and in Tennessee 69.9%. North Carolina's transport share rises from 7.0% to 85.0% across the event (\r{ho} = 0.92). Seventeen days after landfall, on 15 October, 47 sites lost transport across six contiguous North Carolina counties with no rainfall, no power loss, no damage, and recovery by the next report. Independent active-probe measurement corroborates it: responsive /24s fall 1.02% for twelve hours while Tennessee stays flat. We release the dataset. Backup power is the standard resilience investment; here it addresses the smaller half of the problem.

cs.NI↗
arXiv2026

terms.txt: A Consent and Compensation Protocol for Agentic Web Access

The open web ran on an unwritten bargain: sites admitted crawlers, and search engines sent visitors back. Public measurements show that bargain breaking under AI crawlers and agents. Automated clients now make up most requests, training dominates Cloudflare-classified crawling, and the largest AI platforms fetch thousands of pages for each visitor they return. The web's common control, robots.txt, cannot express identity, purpose, terms, or price, can be circumvented, and newer alternatives are largely proprietary CDN features. We specify terms.txt, a robots.txt-style file for per-path, per-purpose machine-access terms, plus an origin-enforced exchange using Web Bot Auth signatures, signed intent, delegation tokens, HTTP 402 negotiation, and signed receipts. We define what the exchange can enforce, audit, and leave to contract. A dependency-free implementation adds 0.20 to 0.65 ms per request on one vCPU.

cs.NI↗