AI-RAN 的实时去中心化应用：内联物理层与时隙级控制的实测接口需求
Real-Time dApps for AI-RAN: Measured Interface Requirements for Inline PHY and Slot-Level Control
- DeepSig Inc.（深信号公司）
机构由 AI 辅助整理，请以论文原文为准。
AI总结：
本文通过实测39个AI-RAN用例和多种接口机制，证明多数用例需进程内接口以满足实时性，并据此发布了ABI及四种dApps验证方案。
AI中文摘要：
去中心化应用（dApps）将人工智能引入到5G分布式单元（DU）旁边的微秒到毫秒频段，但每个公开的dApp框架都以相同方式实现它们：一个接收指示并返回控制消息的外部进程。该边界适用于感知和咨询类工作负载。它无法表达必须在时隙内完成的神经接收机，也无法承载MAC正在等待的调度决策。本文探讨了dApp接口在延迟和带宽方面必须提供什么，才能使目前以该名称归档的AI-RAN用例真正作为dApps实现。它将dApp与DU之间的耦合视为一个设计轴，具有两个合法端点：DU进程内的C ABI和通过SCTP的协议标准E3AP关联，并将三个OCUDU dApp类别置于其上。一个经过审计的39个运行时AI-RAN用例语料库（按5G NR时序衡量）显示，超过一半的用例无法跨越观察者边界：内联物理层工作因为指示无法返回到同一时隙，而有界控制则因为负载下的尾部延迟。在安静主机和空中实时小区上测量每个框架实际使用的机制表明，每个载波在空闲主机上都能满足100微秒的控制截止时间，而只有进程内路径在DU运行后仍能满足。异步用例在每个位置仍然可行，因此协议标准端保持为一等选项；进程内放置为它们带来的额外价值是可问责的陈旧性和无消息的观察-决策路径。这些测量得出了已发布的ABI、用于内联工作的流、经过验证的有界控制调用，以及用于观察的租约、受监督环或便携式E3客户端的选择，并且所有三个类别的四个dApps在一个空中小区上共同验证。
英文摘要：
Distributed applications (dApps) bring AI to the microsecond-to-millisecond band beside the 5G distributed unit (DU), but every public dApp framework realizes them the same way: an external process that receives an indication and returns a control message. That boundary is right for sensing and advisory workloads. It cannot express a neural receiver that must finish inside a slot, and it cannot hold a scheduling decision the MAC is waiting on. This paper asks what a dApp interface must deliver, in latency and bandwidth, for the AI-RAN use cases now filed under that name to be realized as dApps at all. It treats the coupling between a dApp and the DU as a design axis with two legitimate ends, a C ABI inside the DU process and a protocol-standard E3AP association over SCTP, and places the three OCUDU dApp classes on it. An audited corpus of 39 runtime AI-RAN use cases, sized by 5G NR timing, shows that more than half cannot cross the observer boundary: inline PHY work because an indication has no return path into the same slot, and bounded control because of the tail under load. Measuring the mechanisms each framework actually uses, on a quiet host and with a live cell on the air, shows that every carrier meets a 100 us control deadline on an idle host and that only the in-process paths still do once the DU is running. The asynchronous use cases remain feasible at every position, so the protocol-standard end is kept as a first-class option; what in-process placement adds for them is accountable staleness and an observation-to-decision path with no message on it. These measurements derive the released ABI, a stream for inline work, a validated call for bounded control, and a choice of lease, supervised ring, or portable E3 client for observation, and four dApps of all three classes are validated together on one over-the-air cell.
