Preferencje help
Widoczny [Schowaj] Abstrakt
Liczba wyników

Znaleziono wyników: 2

Liczba wyników na stronie
first rewind previous Strona / 1 next fast forward last
Wyniki wyszukiwania
help Sortuj według:

help Ogranicz wyniki do:
first rewind previous Strona / 1 next fast forward last
1
Content available remote Sensor Data Protection in Cyber-Physical Systems
EN
Cyber-Physical Systems (CPS) always have a physical part that can interact with sensors and actuators. The data that is read from sensors and the data generated to drive actuators is crucial for the correct operation of this class of devices. The majority of the implementations trust the data being read from sensors and the outputted data to actuators. Real-time validation of the input and output of data for any system is crucial for the safety of its operation. This paper proposes an architecture for handling this issue through smart data guards, which are detached from sensors and controllers and act solely on the data. This mitigates potential issues of malfunctioning sensors and faulty control signals, and intentional sensor and controller attacks. The data guards know the expected data, can detect anomalies and can correct them in real-time. This approach adds more guarantees for fault-tolerant behavior in the presence of attacks and failures.
2
Content available remote Component interface standardization in robotic systems
EN
Components are heavily used in many software systems, including robotic systems. The growth in sophistication and diversity of new capabilities for robotic systems presents new challenges to their architectures. Their complexity is growing exponentially with the advent of AI, smart sensors, and the complex tasks they have to accomplish. Such complexity requires a more flexible approach for creating, using, and interoperability of software components. The issue is exacerbated because robotic systems are becoming increasingly reliant on third-party components for specific functions. In order to achieve this kind of interoperability, including dynamic component replacement, we need a way to standardize their interfaces. A formal approach is desperately needed for specifying what an interface of a robotic software component should contain. This study performs an analysis of the issue and presents a universal and generic approach to standardizing component interfaces for robotic systems. Our approach is inspired and influenced by well-established robotic architectures such as ROS, PX4, and Ardupilot. The study is also applicable to other software systems with similar characteristics to robotic systems. We consider using either JSON or Domain-Specific Languages (DSL) development with tools such as Antlr and automatic code and configuration files generation for frameworks such as ROS and PX4. A case study with ROS2 has been done as a proof of concept for the proposed methodology.
first rewind previous Strona / 1 next fast forward last
JavaScript jest wyłączony w Twojej przeglądarce internetowej. Włącz go, a następnie odśwież stronę, aby móc w pełni z niej korzystać.