Search arXiv⌕ Search
Home/Archive/arXiv

arXiv · 2610.06123

Identification Codes for Ad Hoc Networks: Use Cases and Challenges

Athin Mohan·Roberto Ferrara·Christian Deppe
View original source ↗Read source document ↗Export metadata ↓

Abstract

In this study, we focus on large-scale ad hoc networks characterized by a high node density. To achieve energy efficiency, the devices must minimize their data transmission, thereby reducing the total number of bits sent and the associated energy consumption. We consider using ID codes for the address field in the MAC layer and reduce the header size. The work explores a range of use cases and challenges that demonstrate the benefits of incorporating these ID codes into packet routing mechanisms for ad hoc networks, thereby providing a foundation for understanding their applicability and the necessary design adaptations.

Explore related subjects

cs.NI

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Athin Mohan, Roberto Ferrara, Christian Deppe. 2026-10-05. Identification Codes for Ad Hoc Networks: Use Cases and Challenges. https://arxiv.org/abs/2610.06123

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

KEEP EXPLORING

Related papers

arXiv2026

From ASIC to Fleet: Lessons from Building and Operating a Hyperscaler NIC

We describe the operational infrastructure built to deploy and operate fbnic, a custom multi-host NIC, across hundreds of thousands of production hosts at Meta. Vendor multi-host NICs, designed by retrofitting single-host architectures, suffered from shared firmware and buffers that created cascading isolation failures over seven years. fbnic eliminates these through physical isolation, but shifting to in-house hardware shifts the entire operational burden to the hyperscaler. We present a hardware-in-the-loop CI pipeline testing firmware, driver, and kernel cross-products; a unified observability pipeline co-locating NIC and switch counters for cross-layer fault attribution; a driver-first architecture with fewer than ten firmware message types; a targeted firmware upgrade orchestrator at sub-sled granularity; and scoped repair automation confining blast radius to individual host slices. Over ten months, fbnic achieved a 12X reduction in unplanned unavailability, 37% lower mean time to repair, and 2.3X fewer hardware swaps compared to vendor NICs on the same platform.

cs.NI↗
arXiv2026

Semantic Split Inference for Remote Modulation Recognition

Remote automatic modulation recognition balances sensing-node complexity, reporting cost and accuracy. To address this trade-off, we propose channel-aware semantic split inference: a sensing node sends a semantic report over a noisy link and the edge server completes recognition. In our model, split depth and report length are independent design variables, with end-to-end training through the channel. We compare the resulting design against basic split placements, which run inference at the edge server or at the sensing node, and against a state-of-the-art collaborative scheme. We assess sensing-node model size, computation, latency and energy against recognition accuracy. We show that intermediate splits give the best accuracy-cost trade-off.

cs.NI↗
arXiv2026

When Weak Reports Matter: Staged Anchored Fusion for Cooperative UAV Sensing

Local multipath rejection can erase evidence needed for cooperative sensing. We propose staged anchored recovery: preserve strong-only confirmations, then query compatible weak reports using unused strong anchors. For any number of sensing nodes, we prove lossless residual screening and derive corroboration and bidirectional cost laws. In 1,024 five-UAV drops, recovery adds 30 matched targets and three false outputs over strict consensus, matching one-pass anchored confirmation's detection counts while reducing weak uploads by 97.4%. Equal-sized cue/report records yield 4.5% less payload than uploading all eligible reports. Independent validation recovers four additional targets with no observed false outputs.

cs.NI↗