AI Lifecycle-Aware Feasibility Framework for Split-RIC Orchestration in NTN O-RAN

Daniele Tarchi
3/24/2026
cs.NIcs.AI

No confident code implementation found for this paper. 3 possible matches can be shown below.

Abstract

Integrating Artificial Intelligence (AI) into Non-Terrestrial Networks (NTN) is constrained by the joint limits of satellite SWaP and feeder-link capacity, which directly impact O-RAN closed-loop control and model lifecycle management. This paper studies the feasibility of distributing the O-RAN control hierarchy across Ground, LEO, and GEO segments through a Split-RIC architecture. We compare three deployment scenarios: (i) ground-centric control with telemetry streaming, (ii) ground--LEO Split-RIC with on-board inference and store-and-forward learning, and (iii) GEO--LEO multi-layer control enabled by inter-satellite links. For each scenario, we derive closed-form expressions for lifecycle energy and lifecycle latency that account for training-data transfer, model dissemination, and near-real-time inference. Numerical sensitivity analysis over feeder-link conditions, model complexity, and orbital intermittency yields operator-relevant feasibility regions that delineate when on-board inference and non-terrestrial learning loops are physically preferable to terrestrial offloading.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. 3 weaker matches are hidden by default — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{tarchi2026lifecycleaware,
  title  = {AI Lifecycle-Aware Feasibility Framework for Split-RIC Orchestration in NTN O-RAN},
  author = {Daniele Tarchi},
  year   = {2026},
  eprint = {2603.23252},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2603.23252v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2603.23252.svg)](https://codeofpaper.com/paper/2603.23252)

Discussion