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

SB_UTM_4

Specification Description

The longitude (Lon) of any UAS's telemetry data will be bounded between MaxLonLB and MinLonUB.

Signals Required

Lon

Boolean Conversion of Signals to Atomic Inputs

Lon_leq_MaxLonUB = 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] > MaxLonUB) && (Lon[i] == Lon[i])
    { 
        Lon_leq_MaxLonUB = 0;
    }
} 
Lon_geq_MinLonLB = 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] < MinLonLB) && (Lon[i] == Lon[i])
    { 
        Lon_geq_MinLonLB = 0;
    }
}

MLTL Specification

Original: (Lon_leq_MaxLonUB ∧ Lon_geq_MinLonLB)

Updated: ☐[0,3] (Lon_leq_MaxLonUB ∧ Lon_geq_MinLonLB)

Fault Explanation

A UAS's longitude is not physically possible.

Additional Notes

Longitude can only ever by between -180 and 180 degrees. Anything outside these bounds is nonsensical and indicates a fault within the system.

Figures

FFigure 1: All of the longitude (Lon) inputs from each GCS the UTM reads from the telemetry datatable.
Figure 2: The output of R2U2's monitoring of specification SB_UTM_4, confirming that no UAS exceeds its waypoint longitude sensor bounds.
Figure 3: Since Fig. 1 had no Lon inputs that exceeded MaxLonUB or MinLonLB, we manually injected a fault into a single UAS (purple).
Figure 4: The output of R2U2's monitoring of specification SB_UTM_4, showing that R2U2 catches when the injected fault occurs. However, notice that there is bouncing in the initial Boolean specificaiton, which can lead to undesireable false-positive alerts.
Figure 5: The output of R2U2's monitoring of the updated specification SB_UTM_4, showing that R2U2 catches when the injected fault occurs and the "☐[0,3]" temporal operator acts as a sliding filter, debouncing R2U2's output.