Skip to content
AI News HubLIVE
Original source3 min read

SLED: Sensor SLicing from Edge to Datacenter

Summary

The paper introduces Sensor Slicing (SL), a MAC-level isolation mechanism for individual sensors within a single UE in O-RAN, plus SLED, an end-to-end framework spanning edge, campus, and remote HPC tiers that keeps latency-critical telemetry stable where conventional network slicing fails.

SourcearXiv AIAuthor: Alan Subedi, Avhishek Biswas, Apala Pramanik, Amlan Balabantaray, Mikhail Titov, Santosh Pitla, Ozgur Kilic, Mehmet C. Vuran
SLED: Sensor SLicing from Edge to Datacenter
Report an error

The correction channel is not available yet. You can copy the article reference below for later.

Correction instructions
Read article

[Submitted on 16 Nov 2026]

Title:SLED: Sensor SLicing from Edge to Datacenter

View a PDF of the paper titled SLED: Sensor SLicing from Edge to Datacenter, by Alan Subedi and 7 other authors

View PDF HTML (experimental)

Abstract:Modern sensing systems generate large volumes of heterogeneous data streams from multiple sensor modalities, increasing reliance on datacenters for computation, artificial intelligence/superintelligence (AI/SI) inference, and AI/SI training. Each sensor stream may have different network and compute requirements depending on its type and data volume. However, current wireless systems typically allocate resources at the device level, leading to contention among co-located sensor streams, where bulk data transfers may starve latency-critical telemetry. To this end, this paper introduces Sensor Slicing (SL). SL provides deterministic, medium access control (MAC)-level isolation for individual sensors within a single user equipment (UE) in open radio access networks (O-RAN). Using agentic coding techniques, SL is implemented in two O-RAN-compliant packages, reducing development time by 400 times (2 h 40 min [OCUDU] vs. 6.5 weeks [OAI]), 228-fold fewer human prompts (4 vs. 913), and less than half the tokens (0.64B vs. 1.43B). An associated end-to-end framework, SLED, is implemented to establish per-sensor radio and network isolation across edge, campus, and remote high-performance computing (HPC) tiers. Over-the-air wireless experiments demonstrate that while conventional network slicing causes critical delays to increase more than 2,300-fold under high traffic load, SLED maintains stable latency. Scaling evaluations on the two RAN stacks show that throughput remains within 0.9% and 1.4% of expected allocations even as the number of sensor slices increases. The results demonstrate that SLED preserves latency-critical telemetry while effectively utilizing resources across the sensor-to-HPC pipeline. The SLED software and evaluation datasets are publicly available at this https URL.

Comments: Accepted in IEEE Annual Congress on Artificial Intelligence of Things (IEEE AIoT) 2026. The SLED software and evaluation datasets are publicly available at this https URL

Subjects:

Artificial Intelligence (cs.AI); Computational Engineering, Finance, and Science (cs.CE); Distributed, Parallel, and Cluster Computing (cs.DC); Emerging Technologies (cs.ET); Networking and Internet Architecture (cs.NI)

Cite as: arXiv:2611.21937 [cs.AI]

(or arXiv:2611.21937v1 [cs.AI] for this version)

https://doi.org/10.48550/arXiv.2611.21937

arXiv-issued DOI via DataCite (pending registration)

Submission history

From: Avhishek Biswas [view email] [v1] Mon, 16 Nov 2026 21:51:51 UTC (2,113 KB)

Full-text links:

Access Paper:

View a PDF of the paper titled SLED: Sensor SLicing from Edge to Datacenter, by Alan Subedi and 7 other authors

View PDF

HTML (experimental)

TeX Source

view license

Additional Features

Audio Summary

Current browse context:

cs.AI

new | recent | 2026-11

Change to browse by:

cs cs.CE cs.DC cs.ET cs.NI

References & Citations

SciX

Google Scholar

Semantic Scholar

Loading...

Data provided by:

Bibliographic Tools

Bibliographic and Citation Tools

Bibliographic Explorer Toggle

Bibliographic Explorer (What is the Explorer?)

Connected Papers Toggle

Connected Papers (What is Connected Papers?)

Litmaps Toggle

Litmaps (What is Litmaps?)

scite.ai Toggle

scite Smart Citations (What are Smart Citations?)

Code, Data, Media

Code, Data and Media Associated with this Article

alphaXiv Toggle

alphaXiv (What is alphaXiv?)

Links to Code Toggle

CatalyzeX Code Finder for Papers (What is CatalyzeX?)

DagsHub Toggle

DagsHub (What is DagsHub?)

GotitPub Toggle

Gotit.pub (What is GotitPub?)

Huggingface Toggle

Hugging Face (What is Huggingface?)

ScienceCast Toggle

ScienceCast (What is ScienceCast?)

Demos

Demos

Replicate Toggle

Replicate (What is Replicate?)

Spaces Toggle

Hugging Face Spaces (What is Spaces?)

Spaces Toggle

TXYZ.AI (What is TXYZ.AI?)

Related Papers

Recommenders and Search Tools

Link to Influence Flower

Influence Flower (What are Influence Flowers?)

Core recommender toggle

CORE Recommender (What is CORE?)

Author

Venue

Institution

Topic

About arXivLabs

arXivLabs: experimental projects with community collaborators

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

Which authors of this paper are endorsers? | Disable MathJax (What is MathJax?)

Key points and analysis

Article intelligence

InvestorsAdvanced

Key points

  • SL provides deterministic MAC-level isolation per sensor inside one UE in O-RAN, resolving contention among co-located sensor streams.
  • Agentic coding cut development time roughly 400x (2 h 40 min vs. 6.5 weeks) and human prompts 228x (4 vs. 913).
  • SLED spans edge, campus, and remote HPC; over-the-air tests show conventional slicing inflates critical delays over 2,300x under load while SLED stays stable.
  • Throughput stays within 0.9% and 1.4% of allocations across both RAN stacks as slices scale; software and datasets are public.

Highlights and analysis are generated automatically and may contain errors. Check the original source.