18.11.2012 Views

Interim Guidance for UAT Avionics Operating with Safe Flight 21 ...

Interim Guidance for UAT Avionics Operating with Safe Flight 21 ...

Interim Guidance for UAT Avionics Operating with Safe Flight 21 ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

8 bytes<br />

<strong>UAT</strong> -Specific Header<br />

I-Frame 1 I-Frame 2 I-Frame 3<br />

Length<br />

9 bits<br />

Res.<br />

3 bits 4 bits<br />

Transmission order<br />

2.2.3.1 <strong>UAT</strong>-Specific Header<br />

Frame Type<br />

432 bytes (message payload)<br />

424 bytes<br />

Application Data<br />

. . .<br />

Frame Data<br />

Length<br />

I-Frame N<br />

Figure 2-1: Decomposition of the Ground Uplink Message Payload<br />

15<br />

fill as needed<br />

The <strong>UAT</strong>-Specific Header is an 8-byte field that contains in<strong>for</strong>mation on the location of<br />

the broadcasting ground station, the time slot used to send the present message, validity<br />

flags <strong>for</strong> position, time, and application data, and other fields as described in Section<br />

2.2.3.2.2 of [<strong>UAT</strong> MOPS].<br />

2.2.3.2 Application Data<br />

The Application Data is a fixed-length field of 424 bytes. The Application Data consists of<br />

In<strong>for</strong>mation Frames, and always consists of an integral number of bytes. Any remaining<br />

unused portion of the field is zero-filled (i.e., all bits set to ZERO).<br />

Note: The Application Data should be discarded if the Application Data Valid field<br />

is set to “0” in the <strong>UAT</strong>-Specific Header, as specified in [<strong>UAT</strong> MOPS].<br />

2.2.3.3 In<strong>for</strong>mation Frames<br />

Each In<strong>for</strong>mation Frame consists of ‘N’ bytes, comprising four fields <strong>for</strong>matted as shown<br />

in Table 2-1.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!