pith. sign in

arxiv: 2607.01304 · v1 · pith:RY34AWSTnew · submitted 2026-07-01 · 💻 cs.RO · cs.DC· cs.NI

The Three Dimensions of ROS 2 Middleware

Pith reviewed 2026-07-03 20:31 UTC · model grok-4.3

classification 💻 cs.RO cs.DCcs.NI
keywords ROS 2middlewareDDSZenohwireless roboticsdistributed systemsspatial abstractiontemporal predictability
0
0 comments X

The pith

ROS 2 middleware exhibits structural trade-offs among spatial abstraction, temporal predictability, and state continuity that become visible under constrained wireless conditions.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper surveys ROS 2 middleware implementations such as DDS and Zenoh and organizes their behavior through three dimensions required by distributed robotic systems. Space refers to abstraction from physical topology that supports modular deployment. Time refers to predictability needed for control loops. State refers to continuity of context despite changing node participation. The survey shows that these dimensions interact such that spatial abstraction can hide network variability and degrade timing, while state preservation mechanisms add overhead that interferes with time-critical exchanges. The resulting framework maps existing work onto these trade-offs and identifies gaps in current analysis methods.

Core claim

The central claim is that the architectural limits of ROS 2 middleware are captured by three structural dimensions—Space as abstraction enabling modular deployment from physical topology, Time as temporal predictability for control loops, and State as contextual continuity despite intermittent connectivity—and that under constrained wireless conditions spatial abstraction obscures variability thereby weakening temporal guarantees while state mechanisms introduce computational and network overhead that competes with time-critical communication.

What carries the argument

The three structural dimensions of Space, Time, and State that the paper states are required by distributed robotic systems and that organize the analysis of middleware discovery, data exchange, and state management mechanisms.

If this is right

  • Spatial abstraction from physical topology can weaken temporal guarantees by obscuring network variability.
  • Mechanisms preserving state continuity introduce overhead that competes with time-critical communication.
  • Trade-offs among the three dimensions characterize the practical limits of current middleware implementations.
  • A principled research roadmap follows for architectures that better balance the dimensions.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • The framework could be used to evaluate middleware choices for specific robot tasks by quantifying the cost of each dimension.
  • Similar dimensions might apply to other distributed real-time systems outside robotics.
  • Explicit metrics for each dimension would allow direct comparison of future middleware designs.

Load-bearing premise

That the three dimensions of Space, Time, and State are sufficient and structurally complete to capture the architectural limits and trade-offs of ROS 2 middleware.

What would settle it

An implementation of ROS 2 middleware that maintains both temporal guarantees and state continuity in constrained wireless settings while preserving the benefits of spatial abstraction would falsify the claimed trade-offs.

Figures

Figures reproduced from arXiv: 2607.01304 by Angelo Corsaro, Kyung-Joon Park, Sanghoon Lee, Taehun Kim.

Figure 1
Figure 1. Figure 1: Structural abstraction of the ROS 2 communication architecture. For DDS, TCP/IP and SHM (marked with *) are vendor-specific extensions. [PITH_FULL_IMAGE:figures/full_fig_p004_1.png] view at source ↗
Figure 2
Figure 2. Figure 2: ROS 2 Middleware Operational Dynamics. IV. THREE DIMENSIONS OF ROBOT MIDDLEWARE This section formalizes the three structural dimensions essential to distributed robotic systems: Space, Time, and State. These dimensions are not design choices unique to a particular middleware; they are universal structural requirements imposed by the nature of distributed robotic systems. ROS 2 middleware must provide (i) l… view at source ↗
Figure 3
Figure 3. Figure 3: Structural Trade-off Cycle of ROS 2 Middleware [PITH_FULL_IMAGE:figures/full_fig_p020_3.png] view at source ↗
read the original abstract

ROS 2 (Robot Operating System 2) has emerged as the de facto standard for modern robot software development, with middleware implementations such as the Data Distribution Service (DDS) and Zenoh forming the core infrastructure for distributed robotic communication. Despite their architectural flexibility, these middleware systems exhibit structural limitations, particularly under dynamic and resource-constrained wireless environments. This paper presents a systematic survey of ROS 2 middleware and introduces a conceptual framework to examine its architectural limits through three structural dimensions required by distributed robotic systems, namely Space, Time, and State. We first provide a structured analysis of middleware architecture and operational dynamics, including discovery, data exchange, and state management mechanisms. Building on this foundation, we formalize Time as temporal predictability for control loops, Space as spatial abstraction from physical topology to enable modular deployment, and State as contextual continuity despite dynamic node participation and intermittent connectivity. Through a comprehensive review of existing implementations and prior studies, we organize middleware research according to the structural trade-offs that arise among these dimensions. Under constrained wireless conditions, spatial abstraction can obscure network variability and weaken temporal guarantees, while mechanisms that preserve state continuity introduce computational and network overhead that competes with time-critical communication. These interactions reveal structural trade-offs that characterize the practical limits of contemporary robot middleware. By synthesizing architectural patterns and identifying gaps in current modeling and analysis approaches, this survey outlines a principled research roadmap for robust and scalable robotic middleware architectures.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

1 major / 0 minor

Summary. The paper surveys ROS 2 middleware (DDS, Zenoh) and introduces a conceptual three-dimensional framework (Space, Time, State) to organize architectural limits and trade-offs in distributed robotic systems. It reviews discovery, data exchange, and state management; formalizes the dimensions descriptively; identifies interactions such as spatial abstraction weakening temporal guarantees under wireless constraints; and outlines a research roadmap based on gaps in modeling.

Significance. If the framework is demonstrated to be complete and the trade-offs are shown to be exhaustive, the survey could provide a useful organizing lens for middleware research and highlight priorities for robust wireless robotic systems. The work synthesizes prior studies and identifies modeling gaps, which is a standard contribution for a survey, though its value depends on adoption rather than new empirical or formal results.

major comments (1)
  1. [Abstract] Abstract: the claim that Space, Time, and State are 'the three structural dimensions required by distributed robotic systems' is asserted without derivation from first principles of distributed systems, enumeration of candidate alternatives (e.g., security, energy, fault tolerance), or demonstration that every identified limitation maps into these three without remainder. This assertion is load-bearing because the entire organization of middleware research and the analysis of trade-offs (including the strongest claim on spatial abstraction and state continuity) rests on the framework's claimed structural completeness.

Simulated Author's Rebuttal

1 responses · 0 unresolved

We thank the referee for the thoughtful and detailed review. The feedback highlights an important point about the justification of our proposed framework. We address the major comment below and outline planned revisions.

read point-by-point responses
  1. Referee: [Abstract] Abstract: the claim that Space, Time, and State are 'the three structural dimensions required by distributed robotic systems' is asserted without derivation from first principles of distributed systems, enumeration of candidate alternatives (e.g., security, energy, fault tolerance), or demonstration that every identified limitation maps into these three without remainder. This assertion is load-bearing because the entire organization of middleware research and the analysis of trade-offs (including the strongest claim on spatial abstraction and state continuity) rests on the framework's claimed structural completeness.

    Authors: We agree that the abstract's phrasing asserts the framework's status without sufficient supporting discussion. The three dimensions were selected because they directly correspond to the core structural challenges observed in ROS 2 middleware for robotics: physical node distribution and topology (Space), timing predictability for control loops (Time), and continuity of contextual information under churn and intermittency (State). These arise from the requirements of distributed robotic applications rather than a formal derivation from general distributed-systems theory. We did not enumerate alternatives such as security or energy because the survey focuses on communication-layer structural limits and trade-offs; those aspects are largely orthogonal and handled at other layers. We also do not claim that every conceivable limitation maps exhaustively into the three dimensions. To address the concern, we will revise the abstract to describe Space, Time, and State as 'key structural dimensions' rather than 'the three structural dimensions required,' and we will add a short subsection in the introduction that (a) motivates the choice from the surveyed middleware behaviors, (b) briefly notes candidate alternatives, and (c) clarifies that the framework is a descriptive organizing lens rather than a proven complete taxonomy. This change preserves the paper's organization while removing the unsupported claim of structural completeness. revision: partial

Circularity Check

0 steps flagged

No circularity detected; framework is an asserted organizing lens with no derivation chain or reduction to inputs

full rationale

The paper is a survey that introduces Space, Time, and State as 'the three structural dimensions required by distributed robotic systems' to organize middleware analysis and trade-offs. No equations, predictions, fitted parameters, or first-principles derivations are present. The dimensions are presented as the basis for the review rather than derived from or reduced to any prior inputs, self-citations, or fitted data within the paper. No self-definitional loops, fitted-input predictions, or load-bearing self-citation chains exist. The central claim organizes existing literature without claiming to derive the dimensions from first principles in a way that collapses back to the inputs by construction. This matches the default expectation of no significant circularity for a conceptual survey framework.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 1 invented entities

This is a survey paper that introduces a conceptual framework rather than a quantitative model; no fitted parameters, mathematical axioms, or new physical entities are introduced.

axioms (1)
  • domain assumption Space, Time, and State constitute the three structural dimensions required by distributed robotic systems.
    Stated directly in the abstract as the basis for the framework.
invented entities (1)
  • Three-dimensional framework (Space, Time, State) no independent evidence
    purpose: To examine architectural limits and trade-offs in ROS 2 middleware
    New conceptual tool introduced by the paper; no independent evidence provided.

pith-pipeline@v0.9.1-grok · 5790 in / 1227 out tokens · 26180 ms · 2026-07-03T20:31:01.112048+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

234 extracted references · 234 canonical work pages · 4 internal anchors

  1. [1]

    ROS metrics,

    Open Robotics, “ROS metrics,” [Online]. Available: http://metrics.ros. org/, 2026

  2. [2]

    2025 ROS metrics report,

    K. Scott and T. Foote, “2025 ROS metrics report,” Open Source Robotics Foundation (OSRF), Tech. Rep., 2025. [Online]. Available: https://discourse.openrobotics.org/t/2025-ros-metrics-report/52575

  3. [3]

    Distributed robotic systems in the edge-cloud continuum with ROS 2: A review on novel architectures and technology readiness,

    J. Zhang, F. Keramat, X. Yu, D. M. Hernández, J. P. Queralta, and T. Westerlund, “Distributed robotic systems in the edge-cloud continuum with ROS 2: A review on novel architectures and technology readiness,” inProc. 2022 Seventh Int. Conf. on Fog and Mobile Edge Computing (FMEC). IEEE, 2022, pp. 1–8

  4. [4]

    IoRT ROS 2 applications: Evaluating Zenoh and VPN for robotic networking in the edge-cloud continuum,

    L. Fu, G. Kapoor, L. Militano, G. T. Carughi, and T. M. Bohnert, “IoRT ROS 2 applications: Evaluating Zenoh and VPN for robotic networking in the edge-cloud continuum,” inProc. 2025 IEEE Symp. on Computers and Communications (ISCC). IEEE, 2025, pp. 1–6

  5. [5]

    Multi-robot systems and cooperative object transport: Communications, platforms, and challenges,

    X. An, C. Wu, Y . Lin, M. Lin, T. Yoshinaga, and Y . Ji, “Multi-robot systems and cooperative object transport: Communications, platforms, and challenges,”IEEE Open J. of the Computer Society, vol. 4, pp. 23–36, 2023

  6. [6]

    Robot Operating System 2: Design, architecture, and uses in the wild,

    S. Macenski, T. Foote, B. Gerkey, C. Lalancette, and W. Woodall, “Robot Operating System 2: Design, architecture, and uses in the wild,” Science Robotics, vol. 7, no. 66, p. eabm6074, 2022

  7. [7]

    A DDS-based middleware for quality-of-service and high-performance networked robotics,

    J. M. Cruz, A. Romero-Garcés, J. P. B. Rubio, R. M. Robles, and A. B. Rubio, “A DDS-based middleware for quality-of-service and high-performance networked robotics,”Concurrency and Computation: Practice and Experience, vol. 24, no. 16, pp. 1940–1952, 2012

  8. [8]

    Integrating Data Distribution Service (DDS) in smart traffic systems: A comprehensive review,

    B. Al-Madani, S. Hasan, A. Abualhassan, and F. Aliyu, “Integrating Data Distribution Service (DDS) in smart traffic systems: A comprehensive review,”Computer, vol. 58, no. 2, pp. 25–34, 2025

  9. [9]

    A novel testbed for evaluating ROS 2 robot swarm wireless communica- tions,

    J.-B. Castillo-Sánchez, E. González-Parada, and J.-M. Cano-García, “A novel testbed for evaluating ROS 2 robot swarm wireless communica- tions,” inProc. 2024 IEEE 22nd Mediterranean Electrotechnical Conf. (MELECON). IEEE, 2024, pp. 68–73

  10. [10]

    A scalable multi-robot framework for decentralized and asynchronous perception-action- communication loops,

    S. Agarwal, A. Ribeiro, and V . Kumar, “A scalable multi-robot framework for decentralized and asynchronous perception-action- communication loops,”arXiv preprint arXiv:2309.10164, 2025

  11. [11]

    Design of a multimodal control system based on ROS 2: A hierarchical architecture for real-time human-robot collaboration,

    S. Kong, H. Zhang, C. Ye, Y . Xu, and A. Li, “Design of a multimodal control system based on ROS 2: A hierarchical architecture for real-time human-robot collaboration,” inProc. 2025 7th Int. Conf. on Data-driven Optimization of Complex Systems (DOCS). IEEE, 2025, pp. 441–446

  12. [12]

    Edge robotics: Are we ready? an experimental evaluation of current vision and future directions,

    M. Groshev, G. Baldoni, L. Cominardi, A. De La Oliva, and R. Gazda, “Edge robotics: Are we ready? an experimental evaluation of current vision and future directions,”Digital Communications and Networks, vol. 9, no. 1, pp. 166–174, 2023

  13. [13]

    ROS 2 in a nutshell: A survey,

    A. Al-Batati, A. Koubaa, K. Gabr, M. Abdelkader, and H. Aloquaily, “ROS 2 in a nutshell: A survey,”ACM Computing Surveys, 2025

  14. [14]

    Communi- cation isolation for multi-robot systems using ROS 2,

    L. Naury, A. Gouguet, G. Lozenguez, and L. Fabresse, “Communi- cation isolation for multi-robot systems using ROS 2,” inProc. 40th ACM/SIGAPP Symp. on Applied Computing, 2025, pp. 850–858

  15. [15]

    Overview and performance analysis of robotic software framework Flexbot,

    L. Hietasalo, “Overview and performance analysis of robotic software framework Flexbot,” Master’s thesis, Tampere University, 2024

  16. [16]

    Response-time analysis of ROS 2 processing chains under reservation-based scheduling,

    D. Casini, T. Blaß, I. Lütkebohle, and B. Brandenburg, “Response-time analysis of ROS 2 processing chains under reservation-based scheduling,” inProc. 31st Euromicro Conf. on Real-Time Systems. Schloss Dagstuhl, 2019, pp. 1–23

  17. [17]

    End-to-end timing analysis and optimization of multi- executor ROS 2 systems,

    H. Teper, T. Betz, M. Günzel, D. Ebner, G. V on Der Brüggen, J. Betz, and J.-J. Chen, “End-to-end timing analysis and optimization of multi- executor ROS 2 systems,” inProc. 2024 IEEE 30th Real-Time and Embedded Technology and Applications Symp. (RTAS). IEEE, 2024, pp. 212–224

  18. [18]

    Real-time performance analysis of processing systems on ROS 2 executors,

    Y . Tang, N. Guan, X. Jiang, X. Luo, and W. Yi, “Real-time performance analysis of processing systems on ROS 2 executors,” inProc. 2023 IEEE 29th Real-Time and Embedded Technology and Applications Symp. (RTAS). IEEE, 2023, pp. 80–92

  19. [19]

    Response time analysis and priority assignment of processing chains on ROS 2 executors,

    Y . Tang, Z. Feng, N. Guan, X. Jiang, M. Lv, Q. Deng, and W. Yi, “Response time analysis and priority assignment of processing chains on ROS 2 executors,” inProc. 2020 IEEE Real-Time Systems Symp. (RTSS). IEEE, 2020, pp. 231–243

  20. [20]

    Dynamic priority scheduling for periodic systems using ROS 2,

    L. Dust and S. Mubeen, “Dynamic priority scheduling for periodic systems using ROS 2,” inProc. Int. Conf. on Engineering of Computer- Based Systems. Springer, 2023, pp. 239–243

  21. [21]

    RTeX: An efficient and timing-predictable multithreaded executor for ROS 2,

    S. Liu, X. Jiang, N. Guan, Z. Wang, M. Yu, and W. Yi, “RTeX: An efficient and timing-predictable multithreaded executor for ROS 2,” IEEE Trans. on Computer-Aided Design of Integrated Circuits and Systems, vol. 43, no. 9, pp. 2578–2591, 2024

  22. [22]

    The rclc executor: Domain- specific deterministic scheduling mechanisms for ROS applications on microcontrollers: Work-in-progress,

    J. Staschulat, I. Lütkebohle, and R. Lange, “The rclc executor: Domain- specific deterministic scheduling mechanisms for ROS applications on microcontrollers: Work-in-progress,” inProc. 2020 Int. Conf. on Embedded Software (EMSOFT). IEEE, 2020, pp. 18–19

  23. [23]

    Exploring real-time executor on ROS 2,

    Y . Yang and T. Azumi, “Exploring real-time executor on ROS 2,” in Proc. 2020 IEEE Int. Conf. on Embedded Software and Systems (ICESS). IEEE, 2020, pp. 1–8

  24. [24]

    PAAM: A framework for coordinated and priority-driven accelerator management in ROS 2,

    D. Enright, Y . Xiang, H. Choi, and H. Kim, “PAAM: A framework for coordinated and priority-driven accelerator management in ROS 2,” inProc. 2024 IEEE 30th Real-Time and Embedded Technology and Applications Symp. (RTAS). IEEE, 2024

  25. [25]

    PiCAS: New design of priority-driven chain-aware scheduling for ROS 2,

    H. Choi, Y . Xiang, and H. Kim, “PiCAS: New design of priority-driven chain-aware scheduling for ROS 2,” inProc. 2021 IEEE 27th Real-Time and Embedded Technology and Applications Symp. (RTAS). IEEE, 2021, pp. 251–263

  26. [26]

    3DS: An efficient DPDK-based Data Distribution Service for distributed real-time applications,

    T. Xu, X. Chen, C. Wu, J. Wang, R. Zheng, D. Liu, Y . Tan, A. Ren, and J. Li, “3DS: An efficient DPDK-based Data Distribution Service for distributed real-time applications,” inProc. 2022 IEEE 24th Int. Conf. on High Performance Computing & Communications (HPCC/DSS/SmartCity/DependSys). IEEE, 2022, pp. 1283–1290

  27. [27]

    Automatic latency management for ROS 2: Benefits, challenges, and open problems,

    T. Blass, A. Hamann, R. Lange, D. Ziegenbein, and B. B. Brandenburg, “Automatic latency management for ROS 2: Benefits, challenges, and open problems,” inProc. 2021 IEEE 27th Real-Time and Embedded Technology and Applications Symp. (RTAS). IEEE, 2021, pp. 264–277

  28. [28]

    A novel open and efficient robot development framework based on Data Distribution Service orchestration for agile manufacturing,

    L. Qi, X. Zhang, H. Tan, H. Chen, and Y . Wang, “A novel open and efficient robot development framework based on Data Distribution Service orchestration for agile manufacturing,”Robotics and Computer- Integrated Manufacturing, vol. 96, p. 103067, 2025

  29. [29]

    Facilitating distributed data-flow programming with Eclipse Zenoh: The ERDOS 27 case,

    G. Baldoni, J. Loudet, L. Cominardi, A. Corsaro, and Y . He, “Facilitating distributed data-flow programming with Eclipse Zenoh: The ERDOS 27 case,” inProc. 1st Workshop on Serverless Mobile Networking for 6G Communications, 2021, pp. 13–18

  30. [30]

    Harness Engineering for Physical AI: Robot Middleware Is the Harness Layer

    S. Lee, J. Chae, and K.-J. Park, “Harness engineering for Phys- ical AI: Robot middleware is the harness layer,”arXiv preprint arXiv:2606.09416, 2026

  31. [31]

    Autoware_Perf: A tracing and performance analysis framework for ROS 2 applications,

    Z. Li, A. Hasegawa, and T. Azumi, “Autoware_Perf: A tracing and performance analysis framework for ROS 2 applications,”J. of Systems Architecture, vol. 123, p. 102341, 2022

  32. [32]

    Robot Operating System 2 (ROS 2)-based frameworks for increasing robot autonomy: A survey,

    A. Bonci, F. Gaudeni, M. C. Giannini, and S. Longhi, “Robot Operating System 2 (ROS 2)-based frameworks for increasing robot autonomy: A survey,”Applied Sciences, vol. 13, no. 23, p. 12796, 2023

  33. [33]

    Internal ROS 2 interfaces,

    Open Robotics, “Internal ROS 2 interfaces,” [Online]. Available: https://docs.ros.org/en/kilted/Concepts/Advanced/ About-Internal-Interfaces.html, accessed: Mar. 28, 2026

  34. [34]

    Different ROS 2 middleware vendors,

    ——, “Different ROS 2 middleware vendors,” [Online]. Available: https://docs.ros.org/en/kilted/Concepts/Intermediate/ About-Different-Middleware-Vendors.html, accessed: Mar. 28, 2026

  35. [35]

    ROS 2 middleware implementations,

    ——, “ROS 2 middleware implementations,” [Online]. Available: https://docs.ros.org/en/kilted/Concepts/Advanced/ About-Middleware-Implementations.html, accessed: Mar. 28, 2026

  36. [36]

    Changes between ROS 1 and ROS 2,

    ——, “Changes between ROS 1 and ROS 2,” [Online]. Available: https://design.ros2.org/articles/changes.html, accessed: Mar. 28, 2026

  37. [37]

    Creating an RMW implementation,

    ——, “Creating an RMW implementation,” [Online]. Available: https://docs.ros.org/en/kilted/Tutorials/Advanced/ Creating-An-RMW-Implementation.html, accessed: Mar. 28, 2026

  38. [38]

    Executors,

    ——, “Executors,” [Online]. Available: https://docs.ros.org/en/kilted/ Concepts/Intermediate/About-Executors.html, accessed: Mar. 28, 2026

  39. [39]

    Middleware: A model for distributed system services,

    P. A. Bernstein, “Middleware: A model for distributed system services,” Communications of the ACM, vol. 39, no. 2, pp. 86–98, 1996

  40. [40]

    Software engineering and middleware: A roadmap,

    W. Emmerich, “Software engineering and middleware: A roadmap,” in Proc. Conf. on the Future of Software Engineering, 2000, pp. 117–129

  41. [41]

    ROS 2 Kilted Kaiju released,

    Open Robotics, “ROS 2 Kilted Kaiju released,” [Online]. Available: https://www.openrobotics.org/blog/2025/5/23/ ros-2-kilted-kaiju-released, accessed: Mar. 28, 2026

  42. [42]

    OMG Data Distribution Service: Architectural overview,

    G. Pardo-Castellote, “OMG Data Distribution Service: Architectural overview,” inProc. 23rd Int. Conf. on Distributed Computing Systems Workshops. IEEE, 2003, pp. 200–206

  43. [43]

    What is Zenoh?

    ZettaScale Technology, “What is Zenoh?” [Online]. Available: https: //zenoh.io/docs/overview/what-is-zenoh/, accessed: Mar. 28, 2026

  44. [44]

    ROS 2 alternative middleware report,

    Open Robotics, “ROS 2 alternative middleware report,” Open Robotics, Tech. Rep., Sep. 2023, accessed: 2026-03-11. [Online]. Available: https://discourse.ros.org/t/ros-2-alternative-middleware-report/33771

  45. [45]

    Zenoh: Unifying communication, storage and computation from the cloud to the microcontroller,

    A. Corsaro, L. Cominardi, O. Hecart, G. Baldoni, J. E. P. Avital, J. Loudet, C. Guimares, M. Ilyin, and D. Bannov, “Zenoh: Unifying communication, storage and computation from the cloud to the microcontroller,” inProc. 2023 26th Euromicro Conf. on Digital System Design (DSD). IEEE, 2023, pp. 422–428

  46. [46]

    Zenoh abstractions,

    ZettaScale Technology, “Zenoh abstractions,” [Online]. Available: https: //zenoh.io/docs/manual/abstractions/, accessed: Mar. 28, 2026

  47. [47]

    rmw_zenoh,

    Open Robotics, “rmw_zenoh,” [Online]. Available: https://github.com/ ros2/rmw_zenoh/tree/kilted, gitHub repository, Accessed: Mar. 28, 2026

  48. [48]

    Shared-memory-based lock-free queues: The key to fast and robust communication on safety-critical edge devices,

    M. Pöhnl, C. Eltzschig, and T. Blass, “Shared-memory-based lock-free queues: The key to fast and robust communication on safety-critical edge devices,” inProc. Cyber-Physical Systems and Internet of Things Week 2023, 2023, pp. 179–184

  49. [49]

    Overview analysis of Micro-ROS system as an embedded solution for microcontrollers in automatics and robotics applications,

    B. Stadnik and A. Wymysłowski, “Overview analysis of Micro-ROS system as an embedded solution for microcontrollers in automatics and robotics applications,”Przegl ˛ ad Elektrotechniczny, vol. 100, 2024

  50. [50]

    Syntactic interop- erability in real-time systems, ROS 2, and adaptive AUTOSAR using Data Distribution Services: An approach,

    N. Parmar, V . Ranga, and B. Simhachalam Naidu, “Syntactic interop- erability in real-time systems, ROS 2, and adaptive AUTOSAR using Data Distribution Services: An approach,” inInventive Communication and Computational Technologies: Proc. ICICCT 2019. Springer, 2020, pp. 257–274

  51. [51]

    A survey of real-time support, analysis, and advancements in ROS 2,

    D. Casini, J.-J. Chen, J. Li, F. Reghenzani, and H. Teper, “A survey of real-time support, analysis, and advancements in ROS 2,”Leibniz Trans. on Embedded Systems (LITES), vol. 11, no. 1, pp. 1:1–1:37, 2026

  52. [52]

    Scheduling performance evaluation framework for ROS 2 applications,

    B. Peng, A. Hasegawa, and T. Azumi, “Scheduling performance evaluation framework for ROS 2 applications,” inProc. 2022 IEEE 24th Int. Conf. on High Performance Computing & Communications (HPCC/DSS/SmartCity/DependSys). IEEE, 2022, pp. 2031–2038

  53. [53]

    Performance evaluation of a ROS 2 based automated driving system,

    J. Kouril, B. Schäufele, I. Radusch, and B. Schnor, “Performance evaluation of a ROS 2 based automated driving system,” inProc. 10th Int. Conf. on Vehicle Technology and Intelligent Transport Systems (VEHITS). SciTePress, 2024, pp. 52–63

  54. [54]

    Topics vs services vs actions,

    Open Robotics, “Topics vs services vs actions,” [Online]. Available: https://docs.ros.org/en/kilted/How-To-Guides/Topics-Services-Actions. html, accessed: Mar. 28, 2026

  55. [55]

    Understanding topics,

    ——, “Understanding topics,” [Online]. Available: https://docs.ros.org/ en/kilted/Tutorials/Beginner-CLI-Tools/Understanding-ROS2-Topics/ Understanding-ROS2-Topics.html, accessed: Mar. 28, 2026

  56. [56]

    Understanding services,

    ——, “Understanding services,” [Online]. Available: https://docs.ros.org/en/kilted/Tutorials/Beginner-CLI-Tools/ Understanding-ROS2-Services/Understanding-ROS2-Services.html, accessed: Mar. 28, 2026

  57. [57]

    Understanding actions,

    ——, “Understanding actions,” [Online]. Available: https://docs.ros.org/en/kilted/Tutorials/Beginner-CLI-Tools/ Understanding-ROS2-Actions/Understanding-ROS2-Actions.html, accessed: Mar. 28, 2026

  58. [58]

    Interfaces,

    ——, “Interfaces,” [Online]. Available: https://docs.ros.org/en/kilted/ Concepts/Basic/About-Interfaces.html, accessed: Mar. 28, 2026

  59. [59]

    Data Distribution Services performance evaluation framework,

    K. Krinkin, A. Filatov, A. Filatov, O. Kurishev, and A. Lyanguzov, “Data Distribution Services performance evaluation framework,” inProc. 2018 22nd Conf. of Open Innovations Association (FRUCT). IEEE, 2018, pp. 94–100

  60. [60]

    Enhancing communication security in ROS 2,

    F. J. Blanco Romero, “Enhancing communication security in ROS 2,” Master’s thesis, Universidad Miguel Hernández de Elche, 2024

  61. [61]

    Message passing optimization in Robot Operating System,

    Z. Jiang, Y . Gong, J. Zhai, Y .-P. Wang, W. Liu, H. Wu, and J. Jin, “Message passing optimization in Robot Operating System,”Int. J. of Parallel Programming, vol. 48, no. 1, pp. 119–136, 2020

  62. [62]

    ROS 2 discovery server — Fast DDS documentation,

    eProsima, “ROS 2 discovery server — Fast DDS documentation,” [Online]. Available: https://fast-dds.docs.eprosima.com/en/latest/fastdds/ ros2/discovery_server/ros2_discovery_server.html, 2024, accessed: 2026- 04-03

  63. [63]

    RTI routing service — RTI Connext DDS Professional 7.3.0 documentation,

    Real-Time Innovations (RTI), “RTI routing service — RTI Connext DDS Professional 7.3.0 documentation,” [Online]. Available: https://community.rti.com/static/documentation/connext-dds/7.3.0/ doc/manuals/connext_dds_professional/services/routing_service/index. html, 2024, accessed: 2026-04-03

  64. [64]

    Node discovery scheme of DDS for combat management system,

    H. A. Putra and D.-S. Kim, “Node discovery scheme of DDS for combat management system,”Computer Standards & Interfaces, vol. 37, pp. 20–28, 2015

  65. [65]

    2022, OMG Document Number: formal/2022-04-01

    Object Management Group,The real-time publish-subscribe protocol DDS interoperability wire protocol (DDSI-RTPS) specification, version 2.5, Object Management Group, Apr. 2022, OMG Document Number: formal/2022-04-01. [Online]. Available: https://www.omg.org/spec/ DDSI-RTPS/2.5

  66. [66]

    A security analysis of the Data Distribution Service (DDS) protocol,

    F. Maggi, R. V osseler, M. Cheng, P. Kuo, C. Toyama, T. Yen, and E. B. V . Vilches, “A security analysis of the Data Distribution Service (DDS) protocol,”Trend Micro Research, pp. 15–20, 2022

  67. [67]

    Efficient support for deep sleeping modes in embedded systems: The case of Zenoh-pico,

    A. Zanni, “Efficient support for deep sleeping modes in embedded systems: The case of Zenoh-pico,” Master’s thesis, University of Bologna, 2024

  68. [68]

    Autonomous navigation for quadruped robots: Development and optimization on the Unitree Go1 platform,

    G. Caruso, “Autonomous navigation for quadruped robots: Development and optimization on the Unitree Go1 platform,” Ph.D. dissertation, Politecnico di Torino, 2024

  69. [69]

    Attacking OMG Data Distribution Service (DDS) based real-time mission critical distributed systems,

    M. J. Michaud, T. Dean, and S. P. Leblanc, “Attacking OMG Data Distribution Service (DDS) based real-time mission critical distributed systems,” inProc. 2018 13th Int. Conf. on Malicious and Unwanted Software (MALWARE). IEEE, 2018, pp. 68–77

  70. [70]

    On the performance of Zenoh in industrial IoT scenarios,

    M. Baron, L. Diez, M. Zverev, J. R. Juarez, and R. Agüero, “On the performance of Zenoh in industrial IoT scenarios,”Ad Hoc Networks, vol. 170, p. 103784, 2025

  71. [71]

    On the schedulability of a data-centric real-time distribution middleware,

    H. P. Tijero and J. J. Gutiérrez, “On the schedulability of a data-centric real-time distribution middleware,”Computer Standards & Interfaces, vol. 34, no. 1, pp. 203–211, 2012

  72. [72]

    Hardware acceleration of Data Distribution Service (DDS) for automotive communication and computing,

    C. Scordino, A. G. Mariño, and F. Fons, “Hardware acceleration of Data Distribution Service (DDS) for automotive communication and computing,”IEEE Access, vol. 10, pp. 109 626–109 651, 2022

  73. [73]

    A performance study on the throughput and latency of Zenoh, MQTT, Kafka, and DDS,

    W.-Y . Liang, Y . Yuan, and H.-J. Lin, “A performance study on the throughput and latency of Zenoh, MQTT, Kafka, and DDS,”arXiv preprint arXiv:2303.09419, 2023

  74. [74]

    Zenoh: A next-generation protocol for IoT and edge computing,

    F. Desbiens, “Zenoh: A next-generation protocol for IoT and edge computing,” Presentation at Open Source Summit + Embedded Linux Conf. (OSS + ELC) 2021, Eclipse Foundation, Sep. 2021

  75. [75]

    Supporting end-to-end quality of service properties in OMG Data Distribution Service publish/subscribe middleware over wide area networks,

    A. Hakiri, P. Berthou, A. Gokhale, D. C. Schmidt, and T. Gayraud, “Supporting end-to-end quality of service properties in OMG Data Distribution Service publish/subscribe middleware over wide area networks,”J. of Systems and Software, vol. 86, no. 10, pp. 2574–2593, 2013. 28

  76. [76]

    A. Corsaro. (2021, Jun.) Zenoh reliability: How it works? [Online]. Available: https://zenoh.io/blog/2021-06-14-zenoh-reliability/. ZettaS- cale Technology

  77. [77]

    (2023, Jun.) Zenoh for ROS 2: Char- mander and beyond

    ZettaScale Technology. (2023, Jun.) Zenoh for ROS 2: Char- mander and beyond. [Online]. Available: https://zenoh.io/blog/ 2023-06-05-charmander2/

  78. [78]

    (2024) Module zenoh::liveliness — Rust documentation

    ——. (2024) Module zenoh::liveliness — Rust documentation. [On- line]. Available: https://docs.rs/zenoh/latest/zenoh/liveliness/index.html. Official Rust API Reference

  79. [79]

    Performance study of the Robot Operating System 2 with QoS and cyber security settings,

    J. Fernandez, B. Allen, P. Thulasiraman, and B. Bingham, “Performance study of the Robot Operating System 2 with QoS and cyber security settings,” inProc. 2020 IEEE Int. Systems Conf. (SysCon). IEEE, 2020, pp. 1–6

  80. [80]

    Information distribution in multi-robot systems: Utility-based evaluation model,

    M. Barci ´s, A. Barci ´s, and H. Hellwagner, “Information distribution in multi-robot systems: Utility-based evaluation model,”Sensors, vol. 20, no. 3, p. 710, 2020

Showing first 80 references.