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_11
Specification Description
The latitude (Lat) of any UAS's telemetry data will be bounded between LatLB and LatUB.
Signals Required
Lat
Boolean Conversion of Signals to Atomic Inputs
Lat_leq_LatUB = 1;
for(i = 0; i < NumUAS; i++)
{
// if UAS i's Lat is greater than the upper bounded
// and the value is not "nan"
if((Lat[i] > LatUB) && (Lat[i] == Lat[i])
{
Lat_leq_LatUB = 0;
}
}
Lat_geq_LatLB = 1;
for(i = 0; i < NumUAS; i++)
{
// if UAS i's Lat is less than the lower bounded
// and the value is not "nan"
if((Lat[i] < LatLB) && (Lat[i] == Lat[i])
{
Lat_geq_LatLB = 0;
}
}
MLTL Specification
Original: Lat_leq_LatLB ∧ Lat_geq_LatLB
Updated: ☐[0,3] (Lat_leq_LatLB ∧ Lat_geq_LatLB)
Fault Explanation
Any telemetry point should be within the UTM's airspace
Additional Notes