Integrating Runtime Verification into an
Automated UAS Traffic Management System
Matthew Cauwels, Abigail Hammer, Benjamin Hertz, Phillip H. Jones, Kristin Y. Rozier
This webpage contains supplementary specifications for "Integrating Runtime Verification into an
Automated UAS Traffic Management System" by M. Cauwels, A. Hammer, B. Hertz, P. H. Jones, and K. Y. Rozier
OR_UTM_12
Specification Description
The longitude (Lon) of any UAS's telemetry data will be bounded between LonLB and LonUB.
Signals Required
Lon
Boolean Conversion of Signals to Atomic Inputs
Lon_leq_LonUB = 1;
for(i = 0; i < NumUAS; i++)
{
// if UAS i's Lon is greater than the upper bounded
// and the value is not "nan"
if((Lon[i] > LonUB) && (Lon[i] == Lon[i])
{
Lon_leq_LonUB = 0;
}
}
Lon_geq_LonLB = 1;
for(i = 0; i < NumUAS; i++)
{
// if UAS i's Lon is less than the lower bounded
// and the value is not "nan"
if((Lon[i] < LonLB) && (Lon[i] == Lon[i])
{
Lon_geq_LonLB = 0;
}
}
MLTL Specification
Original: Lon_leq_LonLB ∧ Lon_geq_LonLB
Updated: ☐[0,3] (Lon_leq_LonLB ∧ Lon_geq_LonLB)
Fault Explanation
Any telemetry point should be within the UTM's airspace
Additional Notes