跳到正文
arXiv cs.AI· Giacomo Paltrinieri (University of Modena,Reggio Emilia), Angelo Ferrando (University of Modena,Reggio Emilia)·· 56 分钟前AI 评分34

ROSMonitoring 扩展:为 ROS 2 Actions 提供运行时监控与强制执行

ROSMonitoring in Action: Runtime Monitoring and Enforcement for ROS 2 Actions

AI 导读

ROSMonitoring 新增对 ROS 2 actions 的运行时监控与强制执行能力,可重建 goal 提交、反馈、结果与取消等 action 级生命周期事件,并通过 goal 标识符关联状态。当通信无法转发时,监控器可执行 goal 拒绝、取消、消息抑制及生成协议合规响应。压力测试显示固定负载下监控开销随重复调用近似线性增长,更大工作负载和更多 client-server 对带来额外开销。

正文 · 原文

View PDF

Abstract:Robotic applications often rely on long-running operations, such as navigation, manipulation, and inspection, which in ROS~2 are commonly implemented as actions. Unlike topics and services, actions involve a structured lifecycle comprising goal submission and acceptance, feedback, status updates, result retrieval, and cancellation. Existing versions of ROSMonitoring support topics and services, but do not reconstruct this lifecycle or expose action-level events to a runtime-verification oracle. In this paper, we extend ROSMonitoring with runtime monitoring and enforcement for ROS~2 actions. Actions are declared directly in the monitoring configuration and automatically instrumented through the underlying ROS~2 communication endpoints. The generated monitor reconstructs action-level events, correlates them through goal identifiers, maintains the state of active goals, and translates violations into protocol-aware enforcement operations. These include goal rejection, cancellation, message suppression, and protocol-compliant responses generated directly by the monitor when the original communication cannot be forwarded. We evaluate the implementation through controlled stress tests that vary the number of action invocations, workload size, and client–server topology. The results show approximately linear growth in monitoring cost with repeated action invocations under a fixed workload, while larger action workloads and a greater number of configured client–server pairs introduce additional overhead. These results characterise the scaling behaviour of the current implementation under the tested sequential workloads while highlighting the main performance limitations of the current synchronous implementation.
Comments: In Proceedings FMAS 2026, arXiv:2611.21375
Subjects: Artificial Intelligence (cs.AI); Logic in Computer Science (cs.LO); Robotics (cs.RO)
Cite as: arXiv:2611.22407 [cs.AI]
  (or arXiv:2611.22407v1 [cs.AI] for this version)
  https://doi.org/10.48550/arXiv.2611.22407

arXiv-issued DOI via DataCite (pending registration)

Journal reference: EPTCS 457, 2026, pp. 136-153
Related DOI: https://doi.org/10.4204/EPTCS.457.10

DOI(s) linking to related resources

Submission history

From: EPTCS [view email] [via EPTCS proxy]
[v1] Tue, 17 Nov 2026 08:46:37 UTC (55 KB)

来源:arXiv cs.AI · arxiv.org