COMP4DRONES - User contributions [en]

WP5-08

2022-11-25T16:22:21Z

Rotechnology: /* General Description */

=Lightweigth Cryptography=
{|class="wikitable"
| ID|| WP5-08
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Communication service
|-
| Provide || Communication security and intrusion detection.
|-
| Input || A plain text to encrypt or a cyper text to decrypt.
|-
| Output || An encrypted message (cyper text) or a decrypted message (plain text).
|-
| C4D building block || The component is transversal with respect to the application fields. In the context of C4D, it has been adopted in the UC5 - Demo 1.
|-
| TRL || 6
|}

==General Description==
The Lightweigth Cryptography is supposed to be used by other components which need to encrypt data in order to send it outside the system. The other components have to call the LC component encryption or decryption function according to which operation needs to be carried out.
In addition to the encryption/decryption functionalities, an authentication mechanism is carried out during the decryption function to recognize if the encrypted data has been sent by a trusted node.
The component is based on TAKS2 scheme, a network topology-based scheme which provides passive security at link layer along a topology-based authentication with minimal performance overhead.

==Specification and contribution==
In the C4D project, it has been exploited in the UC5 - Demo 1, namely '''Precision Agricolture''', used to secure the communication between drone and rover towards the infrastructure.
It has been integrated through components that provide an integrated methodology to implement ready-to-use accelerators from an FPGA-based companion computer that can be used both in the drone and the rover.

==Design and Implementation==
The scheme works in two different phases: encryption and decryption, the second of which implicitly also carries out Intrusion Detection functionality through the authentication operation.
The component is provided as a software library developed in C++ and is architecturally composed by three different modules:
* LCM: takes care of the configuration of the nodes and provides encryption and decryption functionalities;
* TAKS: this module performs the TAKS scheme, executing the message encryption, decryption and authentication functions;
* AES: this library contains the AES-128 standard primitives.

==Reference==
[1] Pugliese, M, Santucci, F. Pair-wise network topology authenticated hybrid cryptographic keys for Wireless Sensor Networks using vector algebra. In: 5th IEEE international workshop on wireless sensor networks security (WSNS2008), Atlanta, GA, 29 September–2 October 2008. New York: IEEE

[2] Tiberti W, Caruso F, Pomante L, Pugliese M, Santic M, Santucci F. Development of an extended topology-based lightweight cryptographic scheme for IEEE 802.15.4 wireless sensor networks. International Journal of Distributed Sensor Networks. October 2020.

[3] L. Pomante, M. Pugliese, L. Bozzi, W. Tiberti, D. Grimani and F. Santucci, "SEAMLESS Project: Development of a Performing Secure Platform for IEEE 802.15.4 WSN Applications," 2020 23rd Euromicro Conference on Digital System Design (DSD), 2020, pp. 588-595, doi: 10.1109/DSD51259.2020.00097.

[4] https://github.com/RoTechnology/Lightweight-Cryptography

WP5-08

2022-11-25T16:19:15Z

Rotechnology: /* Design and Implementation */

=Lightweigth Cryptography=
{|class="wikitable"
| ID|| WP5-08
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Communication service
|-
| Provide || Communication security and intrusion detection.
|-
| Input || A plain text to encrypt or a cyper text to decrypt.
|-
| Output || An encrypted message (cyper text) or a decrypted message (plain text).
|-
| C4D building block || The component is transversal with respect to the application fields. In the context of C4D, it has been adopted in the UC5 - Demo 1.
|-
| TRL || 6
|}

==General Description==
The Lightweigth Cryprography is supposed to be used by other components which need to encrypt data in order to send it outside the system. The other components have to call the LC component encryption or decryption function according to which operation needs to be carried out.
In addition to the encryption/decryption functionalities, an authentication mechanism is carried out during the decryption function to recognize if the encrypted data has been sent by a trusted node.
The component is based on TAKS2 scheme, a network topology-based scheme which provides passive security at link layer along a topology-based authentication with minimal performance overhead.

==Specification and contribution==
In the C4D project, it has been exploited in the UC5 - Demo 1, namely '''Precision Agricolture''', used to secure the communication between drone and rover towards the infrastructure.
It has been integrated through components that provide an integrated methodology to implement ready-to-use accelerators from an FPGA-based companion computer that can be used both in the drone and the rover.

==Design and Implementation==
The scheme works in two different phases: encryption and decryption, the second of which implicitly also carries out Intrusion Detection functionality through the authentication operation.
The component is provided as a software library developed in C++ and is architecturally composed by three different modules:
* LCM: takes care of the configuration of the nodes and provides encryption and decryption functionalities;
* TAKS: this module performs the TAKS scheme, executing the message encryption, decryption and authentication functions;
* AES: this library contains the AES-128 standard primitives.

==Reference==
[1] Pugliese, M, Santucci, F. Pair-wise network topology authenticated hybrid cryptographic keys for Wireless Sensor Networks using vector algebra. In: 5th IEEE international workshop on wireless sensor networks security (WSNS2008), Atlanta, GA, 29 September–2 October 2008. New York: IEEE

[2] Tiberti W, Caruso F, Pomante L, Pugliese M, Santic M, Santucci F. Development of an extended topology-based lightweight cryptographic scheme for IEEE 802.15.4 wireless sensor networks. International Journal of Distributed Sensor Networks. October 2020.

[3] L. Pomante, M. Pugliese, L. Bozzi, W. Tiberti, D. Grimani and F. Santucci, "SEAMLESS Project: Development of a Performing Secure Platform for IEEE 802.15.4 WSN Applications," 2020 23rd Euromicro Conference on Digital System Design (DSD), 2020, pp. 588-595, doi: 10.1109/DSD51259.2020.00097.

[4] https://github.com/RoTechnology/Lightweight-Cryptography

WP5-08

2022-11-25T16:16:33Z

Rotechnology: /* Specification and contribution */

=Lightweigth Cryptography=
{|class="wikitable"
| ID|| WP5-08
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Communication service
|-
| Provide || Communication security and intrusion detection.
|-
| Input || A plain text to encrypt or a cyper text to decrypt.
|-
| Output || An encrypted message (cyper text) or a decrypted message (plain text).
|-
| C4D building block || The component is transversal with respect to the application fields. In the context of C4D, it has been adopted in the UC5 - Demo 1.
|-
| TRL || 6
|}

==General Description==
The Lightweigth Cryprography is supposed to be used by other components which need to encrypt data in order to send it outside the system. The other components have to call the LC component encryption or decryption function according to which operation needs to be carried out.
In addition to the encryption/decryption functionalities, an authentication mechanism is carried out during the decryption function to recognize if the encrypted data has been sent by a trusted node.
The component is based on TAKS2 scheme, a network topology-based scheme which provides passive security at link layer along a topology-based authentication with minimal performance overhead.

==Specification and contribution==
In the C4D project, it has been exploited in the UC5 - Demo 1, namely '''Precision Agricolture''', used to secure the communication between drone and rover towards the infrastructure.
It has been integrated through components that provide an integrated methodology to implement ready-to-use accelerators from an FPGA-based companion computer that can be used both in the drone and the rover.

==Design and Implementation==
The scheme works in two different phases: encryption and decryption, the second of which implicitly carries out also Intrusion Detection functionality through the authentication operation.
The component is provided as a software library developed in C++ and is architecturally composed by three different modules:
* LCM: it takes care of the configuration of the nodes and provides encryption and decryption functionalities;
* TAKS: this module performs the TAKS scheme, executing the message encryption, decryption and authentication functions;
* AES: this library contains the AES-128 standard primitives.

==Reference==
[1] Pugliese, M, Santucci, F. Pair-wise network topology authenticated hybrid cryptographic keys for Wireless Sensor Networks using vector algebra. In: 5th IEEE international workshop on wireless sensor networks security (WSNS2008), Atlanta, GA, 29 September–2 October 2008. New York: IEEE

[2] Tiberti W, Caruso F, Pomante L, Pugliese M, Santic M, Santucci F. Development of an extended topology-based lightweight cryptographic scheme for IEEE 802.15.4 wireless sensor networks. International Journal of Distributed Sensor Networks. October 2020.

[3] L. Pomante, M. Pugliese, L. Bozzi, W. Tiberti, D. Grimani and F. Santucci, "SEAMLESS Project: Development of a Performing Secure Platform for IEEE 802.15.4 WSN Applications," 2020 23rd Euromicro Conference on Digital System Design (DSD), 2020, pp. 588-595, doi: 10.1109/DSD51259.2020.00097.

[4] https://github.com/RoTechnology/Lightweight-Cryptography

WP5-08

2022-11-25T16:14:18Z

Rotechnology: /* General Description */

=Lightweigth Cryptography=
{|class="wikitable"
| ID|| WP5-08
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Communication service
|-
| Provide || Communication security and intrusion detection.
|-
| Input || A plain text to encrypt or a cyper text to decrypt.
|-
| Output || An encrypted message (cyper text) or a decrypted message (plain text).
|-
| C4D building block || The component is transversal with respect to the application fields. In the context of C4D, it has been adopted in the UC5 - Demo 1.
|-
| TRL || 6
|}

==General Description==
The Lightweigth Cryprography is supposed to be used by other components which need to encrypt data in order to send it outside the system. The other components have to call the LC component encryption or decryption function according to which operation needs to be carried out.
In addition to the encryption/decryption functionalities, an authentication mechanism is carried out during the decryption function to recognize if the encrypted data has been sent by a trusted node.
The component is based on TAKS2 scheme, a network topology-based scheme which provides passive security at link layer along a topology-based authentication with minimal performance overhead.

==Specification and contribution==
In the C4D project, it has been exploited in the UC5 - Demo 1, namely '''Precision Agricolture''', used to secures the communication between drone and rover communication towards the infrastructure.
It has been integrated through components that provide an integrated methodology to implement ready-to-use accelerators from an FPGA-based companion computer, that can be used both in the drone and the rover.

==Design and Implementation==
The scheme works in two different phases: encryption and decryption, the second of which implicitly carries out also Intrusion Detection functionality through the authentication operation.
The component is provided as a software library developed in C++ and is architecturally composed by three different modules:
* LCM: it takes care of the configuration of the nodes and provides encryption and decryption functionalities;
* TAKS: this module performs the TAKS scheme, executing the message encryption, decryption and authentication functions;
* AES: this library contains the AES-128 standard primitives.

==Reference==
[1] Pugliese, M, Santucci, F. Pair-wise network topology authenticated hybrid cryptographic keys for Wireless Sensor Networks using vector algebra. In: 5th IEEE international workshop on wireless sensor networks security (WSNS2008), Atlanta, GA, 29 September–2 October 2008. New York: IEEE

[2] Tiberti W, Caruso F, Pomante L, Pugliese M, Santic M, Santucci F. Development of an extended topology-based lightweight cryptographic scheme for IEEE 802.15.4 wireless sensor networks. International Journal of Distributed Sensor Networks. October 2020.

[3] L. Pomante, M. Pugliese, L. Bozzi, W. Tiberti, D. Grimani and F. Santucci, "SEAMLESS Project: Development of a Performing Secure Platform for IEEE 802.15.4 WSN Applications," 2020 23rd Euromicro Conference on Digital System Design (DSD), 2020, pp. 588-595, doi: 10.1109/DSD51259.2020.00097.

[4] https://github.com/RoTechnology/Lightweight-Cryptography

WP5-08

2022-11-25T16:08:33Z

Rotechnology: /* Lightweigth Cryprography */

=Lightweigth Cryptography=
{|class="wikitable"
| ID|| WP5-08
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Communication service
|-
| Provide || Communication security and intrusion detection.
|-
| Input || A plain text to encrypt or a cyper text to decrypt.
|-
| Output || An encrypted message (cyper text) or a decrypted message (plain text).
|-
| C4D building block || The component is transversal with respect to the application fields. In the context of C4D, it has been adopted in the UC5 - Demo 1.
|-
| TRL || 6
|}

==General Description==
The Lightweigth Cryprography is supposed to be used by other components which need to encrypt data in order to send it outside the system. The other components have to call the LC component encryption or decryption function based on which operation need to be carried out.
In addition to the encryption/decryption functionalities, an authentication mechanism is carried out during the decryption function to recognize if the encrypted data has been sent by a trusted node .
The component is based on TAKS2 scheme, a network topology-based scheme which provides passive security at link layer along a topology-based authentication with minimal performance overhead.

==Specification and contribution==
In the C4D project, it has been exploited in the UC5 - Demo 1, namely '''Precision Agricolture''', used to secures the communication between drone and rover communication towards the infrastructure.
It has been integrated through components that provide an integrated methodology to implement ready-to-use accelerators from an FPGA-based companion computer, that can be used both in the drone and the rover.

==Design and Implementation==
The scheme works in two different phases: encryption and decryption, the second of which implicitly carries out also Intrusion Detection functionality through the authentication operation.
The component is provided as a software library developed in C++ and is architecturally composed by three different modules:
* LCM: it takes care of the configuration of the nodes and provides encryption and decryption functionalities;
* TAKS: this module performs the TAKS scheme, executing the message encryption, decryption and authentication functions;
* AES: this library contains the AES-128 standard primitives.

==Reference==
[1] Pugliese, M, Santucci, F. Pair-wise network topology authenticated hybrid cryptographic keys for Wireless Sensor Networks using vector algebra. In: 5th IEEE international workshop on wireless sensor networks security (WSNS2008), Atlanta, GA, 29 September–2 October 2008. New York: IEEE

[2] Tiberti W, Caruso F, Pomante L, Pugliese M, Santic M, Santucci F. Development of an extended topology-based lightweight cryptographic scheme for IEEE 802.15.4 wireless sensor networks. International Journal of Distributed Sensor Networks. October 2020.

[3] L. Pomante, M. Pugliese, L. Bozzi, W. Tiberti, D. Grimani and F. Santucci, "SEAMLESS Project: Development of a Performing Secure Platform for IEEE 802.15.4 WSN Applications," 2020 23rd Euromicro Conference on Digital System Design (DSD), 2020, pp. 588-595, doi: 10.1109/DSD51259.2020.00097.

[4] https://github.com/RoTechnology/Lightweight-Cryptography

WP4-07

2022-11-25T16:06:55Z

Rotechnology: /* General Description */

=Run-Time Safety Checker=
{|class="wikitable"
| ID|| WP4-07
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Safety rules based on risk assessment
|-
| Provide || Increasing flight control to prevent harm to drones, objects or people.
|-
| Input || Sensor parameters
|-
| Output || Operational status
|-
| TRL || 3
|}

==General Description==
The RSC (Run-Time Safety Checker) is a software module proposed to be used for control and management of the parameters that could be critical for the flight of the drone.
The implementation is based on the predefined Safety Rules, which define the functioning of the component. The RSC will be activated whenever one of the safety rules fails and it will implement a resolution procedure. The module requires the management of several parameters and their combination, as the conditions that may occur are various.

==Specification and contribution==
In the C4D project it was considered a scenario regarding bad atmospheric conditions. Specific temperature and humidity values can affect the navigation of the drone to the point of compromising the mission, so these parameters must be constantly monitored and kept under control.
Two different risky situations have been considered:
* A critical battery temperature value, overcoming battery’s safe thresholds, can lead to an early battery discharge or compromise its operability;
* A combination of low temperature and high humidity could cause the icing phenomenon on the drone’s control surfaces, compromising the flight attitude or, in the worst case, stalling it.

The module monitors, at runtime, the parameter values acquired by the on-board sensors. Sensor parameter values are the input of the Runtime Monitoring, which controls the range in which these values are.
The ranges define three different states: safe, warning and critical, covering cases ranging from safe conditions for a normal flight, to the necessity for the drone to abort its mission and land immediately, since conditions for a safe flight are no longer guaranteed.
The module activates a safety procedure whenever one or more thresholds are exceeded, in other words, every time a safety rule is broken. When this occurs, the module changes its state to Warning or Critical state, depending on the values of the parameters.
When the measured values identify a Warning or Critical state, the RSC activates a risky situation implementing the operations defined for that specific status.

==Design and Implementation==
The component is delivered as a software library developed in C++.
Its entry point is the RuntimeMonitor which takes as input a vector of float values containing the battery temperature, the external temperature and the humidity, as registered by the sensors. These are, subsequently, fed to the AssessmentManager which takes care of sorting calls to the RSCController and the DecisionHandler.
Making use of the methods provided by the SafetyChecker, the RSCController evaluates the situation according to the values it received as input; afterwards, the DecisionHandler takes as input the output of the RSCController and sends out the situation assessment.

[[File: WP4-07_Information Flow.png|thumb|upright 2|center|WP4-07-ROT Runtime Safety Checker information flow]]

==Reference==

[1] Ranquist E., Steiner M., Argrow B., Exploring the range of weather impacts on UAS operations. 18th Conference on Aviation, Range and Aerospace Meteorology, Seattle, WA, 2017

[2] Apparatus for controlling safety of drone, Cho Sung-sik, Hoonmo Kim, 2016

[3] https://github.com/RoTechnology/Run-time-Safety-Checker

WP4-07

2022-11-25T16:05:55Z

Rotechnology: /* Run-Time Safety Checker */

=Run-Time Safety Checker=
{|class="wikitable"
| ID|| WP4-07
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Safety rules based on risk assessment
|-
| Provide || Increasing flight control to prevent harm to drones, objects or people.
|-
| Input || Sensor parameters
|-
| Output || Operational status
|-
| TRL || 3
|}

==General Description==
The RSC (Run-Time Safety Checker) is a software module proposed to be used for control and management of the parameters that could be critical for the flight of the drone.
The implementation is based on the predefined Safety Rules, which define the functioning of the component. The RSC will be activated whenever one of the safety rules fails and it will implement a resolution procedure. The module requires the management of several parameters and their combination as the conditions that may occur are various.

==Specification and contribution==
In the C4D project it was considered a scenario regarding bad atmospheric conditions. Specific temperature and humidity values can affect the navigation of the drone to the point of compromising the mission, so these parameters must be constantly monitored and kept under control.
Two different risky situations have been considered:
* A critical battery temperature value, overcoming battery’s safe thresholds, can lead to an early battery discharge or compromise its operability;
* A combination of low temperature and high humidity could cause the icing phenomenon on the drone’s control surfaces, compromising the flight attitude or, in the worst case, stalling it.

The module monitors, at runtime, the parameter values acquired by the on-board sensors. Sensor parameter values are the input of the Runtime Monitoring, which controls the range in which these values are.
The ranges define three different states: safe, warning and critical, covering cases ranging from safe conditions for a normal flight, to the necessity for the drone to abort its mission and land immediately, since conditions for a safe flight are no longer guaranteed.
The module activates a safety procedure whenever one or more thresholds are exceeded, in other words, every time a safety rule is broken. When this occurs, the module changes its state to Warning or Critical state, depending on the values of the parameters.
When the measured values identify a Warning or Critical state, the RSC activates a risky situation implementing the operations defined for that specific status.

==Design and Implementation==
The component is delivered as a software library developed in C++.
Its entry point is the RuntimeMonitor which takes as input a vector of float values containing the battery temperature, the external temperature and the humidity, as registered by the sensors. These are, subsequently, fed to the AssessmentManager which takes care of sorting calls to the RSCController and the DecisionHandler.
Making use of the methods provided by the SafetyChecker, the RSCController evaluates the situation according to the values it received as input; afterwards, the DecisionHandler takes as input the output of the RSCController and sends out the situation assessment.

[[File: WP4-07_Information Flow.png|thumb|upright 2|center|WP4-07-ROT Runtime Safety Checker information flow]]

==Reference==

[1] Ranquist E., Steiner M., Argrow B., Exploring the range of weather impacts on UAS operations. 18th Conference on Aviation, Range and Aerospace Meteorology, Seattle, WA, 2017

[2] Apparatus for controlling safety of drone, Cho Sung-sik, Hoonmo Kim, 2016

[3] https://github.com/RoTechnology/Run-time-Safety-Checker

WP5-08

2022-10-17T08:40:51Z

Rotechnology: Created page with "=Lightweigth Cryprography= {|class="wikitable" | ID|| WP5-08 |- | Contributor || ROT |- | Levels || Functional |- | Require || Communication service |- | Provide || Communication security and intrusion detection. |- | Input || A plain text to encrypt or a cyper text to decrypt. |- | Output || An encrypted message (cyper text) or a decrypted message (plain text). |- | C4D building block || The component is transversal with respect to the application fi..."

=Lightweigth Cryprography=
{|class="wikitable"
| ID|| WP5-08
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Communication service
|-
| Provide || Communication security and intrusion detection.
|-
| Input || A plain text to encrypt or a cyper text to decrypt.
|-
| Output || An encrypted message (cyper text) or a decrypted message (plain text).
|-
| C4D building block || The component is transversal with respect to the application fields. In the context of C4D, it has been adopted in the UC5 - Demo 1.
|-
| TRL || 6
|}

==General Description==
The Lightweigth Cryprography is supposed to be used by other components which need to encrypt data in order to send it outside the system. The other components have to call the LC component encryption or decryption function based on which operation need to be carried out.
In addition to the encryption/decryption functionalities, an authentication mechanism is carried out during the decryption function to recognize if the encrypted data has been sent by a trusted node .
The component is based on TAKS2 scheme, a network topology-based scheme which provides passive security at link layer along a topology-based authentication with minimal performance overhead.

==Specification and contribution==
In the C4D project, it has been exploited in the UC5 - Demo 1, namely '''Precision Agricolture''', used to secures the communication between drone and rover communication towards the infrastructure.
It has been integrated through components that provide an integrated methodology to implement ready-to-use accelerators from an FPGA-based companion computer, that can be used both in the drone and the rover.

==Design and Implementation==
The scheme works in two different phases: encryption and decryption, the second of which implicitly carries out also Intrusion Detection functionality through the authentication operation.
The component is provided as a software library developed in C++ and is architecturally composed by three different modules:
* LCM: it takes care of the configuration of the nodes and provides encryption and decryption functionalities;
* TAKS: this module performs the TAKS scheme, executing the message encryption, decryption and authentication functions;
* AES: this library contains the AES-128 standard primitives.

==Reference==
[1] Pugliese, M, Santucci, F. Pair-wise network topology authenticated hybrid cryptographic keys for Wireless Sensor Networks using vector algebra. In: 5th IEEE international workshop on wireless sensor networks security (WSNS2008), Atlanta, GA, 29 September–2 October 2008. New York: IEEE

[2] Tiberti W, Caruso F, Pomante L, Pugliese M, Santic M, Santucci F. Development of an extended topology-based lightweight cryptographic scheme for IEEE 802.15.4 wireless sensor networks. International Journal of Distributed Sensor Networks. October 2020.

[3] L. Pomante, M. Pugliese, L. Bozzi, W. Tiberti, D. Grimani and F. Santucci, "SEAMLESS Project: Development of a Performing Secure Platform for IEEE 802.15.4 WSN Applications," 2020 23rd Euromicro Conference on Digital System Design (DSD), 2020, pp. 588-595, doi: 10.1109/DSD51259.2020.00097.

[4] https://github.com/RoTechnology/Lightweight-Cryptography

Component repository

2022-10-17T08:33:00Z

Rotechnology: /* Components list */

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication establishment
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing
|-
|[[WP3-20]]
|MODIS
|Multi-sensor positioning
|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing
|-
|[[WP4-5]]
|SCALIAN
|AI detection for clearance
|-
|[[WP4-07]]
|ROT
|Run-Time Safety Checker
|-
|[[WP4-10]]
|ALM
|Cooperative Planner
|-
|[[WP4-14]]
|ALM
|Map Enhancement Service
|-
|[[WP4-15]]
|ALM
|Visual Analytics
|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18_A]]
|TEKNE
|Drone-Rover Transponder
|-
|[[WP4-20]]
|ALM
|Attractor-based Navigation
|-
|[[WP4-22]]
|ALM
|Shared Reference Frame
|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components
|-
|[[WP4-42]]
|SCALIAN
|AI Stabilization
|-
|[[WP5-02]]
|IKERLAN
|Security Management Toolchain
|-
|[[WP5-03]]
|SCALIAN
|EZ_Com Safe fleet communication
|-
|[[WP5-08]]
|ROT
|Lightweight Cryptography
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05_A]]
|TEKNE
|LP-WAN for UAV identification and monitoring
|-

|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP6-P4R]]
|CEA
|Model driven engineering
|-
|[[WP6-20]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-21]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated SYstems (HEPSYCODE)
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

Component repository

2022-10-17T08:32:03Z

Rotechnology: /* Components list */

This repository aims at providing common components usable in different application domains, in particular those covered by project use-cases.

The requirements for using a components will be listed, as well as a documentation on how to use it. The component itself will be hosted by the partner who provides it.

==Components list==

{| class="wikitable"
|ID
|Contributor
|Title
|-
|[[WP3-01]]
|IKERLAN
|Safety function - Pre-Certified SOM
|-
|[[WP3-02]]
|EDI
|Modular SoC-based embedded reference architecture
|-
|[[WP3-03]]
|BUT
|Sensor information algorithms
|-
|[[WP3-04]]
|HIB
|Computer Vision Components for drones
|-
|[[WP3-10]]
|IFAT
|Component for trusted communication establishment
|-
|[[WP3-13]]
|ENAC
|Paparazzi UAV
|-
|[[WP3-14_1]]
|ENSMA
|Collision avoidance and geo-fencing
|-
|[[WP3-14_2]]
|ENSMA
|Distributed control of multi-drone system
|-
|[[WP3-15_1]]
|ACORDE
|UWB based indoor positioning
|-
|[[WP3-15_2]]
|ACORDE
|Multi-antenna GNSS/INS based navigation
|-
|[[WP3-16]]
|SCALIAN
|EZ_Chains Fleet Architecture
|-
|[[WP3-19_1]]
|IMEC
|Hyperspectral payload
|-
|[[WP3-19_2]]
|IMEC
|Hyperspectral image processing
|-
|[[WP3-20]]
|MODIS
|Multi-sensor positioning
|-
|[[WP3-22]]
|UNIMORE
|Onboard Compute Platform Desing Methodology
|-
|[[WP3-24]]
|UNIVAQ
|Efficient digital implementation of controllers
|-
|[[WP3-26]]
|UWB
|Droneport: an autonomous drone battery management system
|-
|[[WP3-28]]
|UNISS
|Accelerator Design Methodology for OOCP
|-
|[[WP3-36_1]]
|UDANET
|Smart and predictive energy management system
|-
|[[WP3-36_2]]
|UDANET
|AI drone system modules
|-
|[[WP3-37]]
|Aitek
|Video and data analytics
|-
|[[WP4-2]]
|SCALIAN
|EZ_Land Precision landing
|-
|[[WP4-5]]
|SCALIAN
|AI detection for clearance
|-
|[[WP4-07]]
|ROT
|Run-Time Safety Checker
|-
|[[WP4-10]]
|ALM
|Cooperative Planner
|-
|[[WP4-14]]
|ALM
|Map Enhancement Service
|-
|[[WP4-15]]
|ALM
|Visual Analytics
|-
|[[WP4-16]]
|ACORDE
|Enhanced Navigation Software
|-
|[[WP4-17]]
|ACORDE
|Anchor&Tag firmware of the Indoor Positioning System
|-
|[[WP4-18_A]]
|TEKNE
|Drone-Rover Transponder
|-
|[[WP4-20]]
|ALM
|Attractor-based Navigation
|-
|[[WP4-22]]
|ALM
|Shared Reference Frame
|-
|[[WP4-32]]
|SHERPA
|Dynamic control development for navigation and precision landing
|-
|[[WP4-33]]
|UNIVAQ
|Autonomy, cooperation, and awareness
|-
|[[WP4-36]]
|IMCS
|Autonomous Decision Making in Critical Situations
|-
|[[WP4-37]]
|IMCS
|Algorithms for Runtime Safety Monitoring
|-
|[[WP4-39]]
|HIB
|Simulated data aggregator supporting intelligent decision in computer vision components
|-
|[[WP4-42]]
|SCALIAN
|AI Stabilization
|-
|[[WP5-02]]
|IKERLAN
|Security Management Toolchain
|-
|[[WP5-03]]
|SCALIAN
|EZ_Com Safe fleet communication
|-
|[[WP5-09]]
|ABI
|Communication scheme for unified system management
|-
|[[WP5-05_A]]
|TEKNE
|LP-WAN for UAV identification and monitoring
|-
|[[WP5-08]]
|ROT
|Lightweight Cryptography
|-
|[[WP5-11_ACO]]
|ACORDE
|Navigation system with anti-jamming and anti-spoofing features
|-
|[[WP5-16-AIT]]
|AIT
|Cryptographic algorithms adapted for drones
|-
|[[WP5-19_ACO]]
|ACORDE
|Robust communication for an improved Indoor Positioning System
|-
|[[WP6-P4R]]
|CEA
|Model driven engineering
|-
|[[WP6-20]]
|ACORDE
|ESL embedded SW Design Environment (ESDE)
|-
|[[WP6-21]]
|ACORDE
|Indoor Positioning System Modelling&Analysis Framework (IPS-MAF)
|-
|[[WP6-17]]
|UNIVAQ
|HW/SW CO-DEsign of HEterogeneous Parallel dedicated SYstems (HEPSYCODE)
|-
|[[WP6-34]]
|UNIVAQ
|HEPSYCODE SystemC SIMulator Version 2.0 (HEPSIM2)
|}

WP4-07

2022-10-17T08:29:10Z

Rotechnology: Created page with "=Run-Time Safety Checker= {|class="wikitable" | ID|| WP4-07 |- | Contributor || ROT |- | Levels || Functional |- | Require || Set of safety rules based on risk assessment |- | Provide || Increasing flight control thus preventing harm to drones, object or people. |- | Input || Sensor parameters |- | Output || Operational status |- | TRL || 3 |} ==General Description== The RSC (Run-Time Safety Checker) is a software module proposed to be used for control..."

=Run-Time Safety Checker=
{|class="wikitable"
| ID|| WP4-07
|-
| Contributor || ROT
|-
| Levels || Functional
|-
| Require || Set of safety rules based on risk assessment
|-
| Provide || Increasing flight control thus preventing harm to drones, object or people.
|-
| Input || Sensor parameters
|-
| Output || Operational status
|-
| TRL || 3
|}

==General Description==
The RSC (Run-Time Safety Checker) is a software module proposed to be used for control and management of the parameters that could be critical for the flight of the drone.
The implementation is based on the predefined Safety Rules, which define the functioning of the component, and it will be activated whenever one of the safety rules fails and thus it will implement a resolution procedure. The module requires the management of several parameters and their combination as the conditions that may occur are various.

==Specification and contribution==
In the C4D project it was considered a scenario regarding bad atmospheric conditions. Particular temperature and humidity values can affect the navigation of the drone to the point of compromising the mission, so these parameters must be constantly monitored and kept under control.
Two different risky situations have been considered:
* A critical battery temperature value, overcoming battery’s safe thresholds, can lead to an early battery discharge or compromise its operativity;
* A combination of low temperature and high humidity could cause the icing phenomenon on drone’s control surfaces, compromising the flight attitude or, in the worst case, stalling it.

The module monitors, at runtime, the parameters value acquired by the on-board sensors. Sensor parameter values are the input of the Runtime Monitoring, which controls the range at which these values belong to.
The ranges define three different state: safe, warning and critical, where in the first one drone flight normally and in the last one drone should abort its mission and land immediately since there are no longer safety conditions to fly.
The module activates a safety procedure whenever one or more thresholds are exceeded, in other words, every time a safety rule is broken. When this occurs, the module changes its state to Warning or Critical state, depending on the values of the parameters.
When the measured values identify a Warning or Critical state, the RSC activates a risky situation implementing the operations defined for specific status.

==Design and Implementation==
The component is delivered as a software library developed in C++.
Its entry point is the RuntimeMonitor which takes as input a vector of float values containing the battery temperature, the external temperature and the humidity, as registered by the sensors. These are, subsequently, fed to the AssessmentManager which takes care of sorting calls to the RSCController and the DecisionHandler.
Making use of the methods provided by the SafetyChecker, the RSCController evaluates the situation according to the values it received as input; afterwards, the DecisionHandler takes as input the output of the RSCController and sends out the situation assessment.

[[File: WP4-07_Information Flow.png|thumb|upright 2|center|WP4-07-ROT Runtime Safety Checker information flow]]

==Reference==

[1] Ranquist E., Steiner M., Argrow B., Exploring the range of weather impacts on UAS operations. 18th Conference on Aviation, Range and Aerospace Meteorology, Seattle, WA, 2017

[2] Apparatus for controlling safety of drone, Cho Sung-sik, Hoonmo Kim, 2016

[3] https://github.com/RoTechnology/Run-time-Safety-Checker

File:WP4-07 Information Flow.png

2022-10-17T07:55:23Z

Rotechnology: