Understanding Mode S Technology
Understanding Mode S Technology
Stemming from several mid-air collisions in the mid-1980s, mode S has been an integral part of airborne transportation today. Although air traffic is the safest mode of transportation, more in-flight information is needed due to the increase in traffic. Enhanced surveillance and ADS-B address this need.
What is mode S? How does it work and why is it needed? What was wrong with the old mode A and C? What is Flight ID, UF and DF, squitter and elementary surveillance? This article will touch on many aspects of mode S technologies of today and tomorrow. The article will also discuss flight ID, elementary surveillance and UF and DF; explain the details of basic mode S surveillance, how it works and discuss the best practices to verify and test an installation. This discussion will also introduce the new enhanced surveillance, DF17 extended squitter and ADS-B; explain the difference between each of these new technologies and what is needed to verify and test installations.
What is mode S?
Mode S or mode select, is a new way to interrogate an airframe by using a distinct address, such as an aircraft address, that only a particular airframe will respond. Many years ago, mode A and C were developed for airframe identification and altitude reporting. This was and still is an important component of air traffic control and air space management. As more and more airframes were available to the private and commercial flying community, this basic form of surveillance was overwhelming the capacity of the air traffic control radar beacon system (ATCRBS). Given the technology behind the mode A and C interrogation and reply, there were also problems with false reply uncorrelated in time (FRUIT), seeing replies from another interrogation, and garbling one reply interfering with another. The problem is analogous to attempting to listen to several conversations at the same time. As such, the capacity of the ATCRBS was being taxed to its limit. ATCRBS also uses the sliding window technique to determine the azimuth position of the aircraft. This requires many interrogations and replies, which reduce the target-handling capacity of the ATC secondary surveillance radar (SSR). The mode S system uses a monopulse SSR, which has an electrically narrowed beamwidth, typically 2.5 . Apart from better azimuth accuracy the monopulse technique reduces the number of interrogations required to track a target, as it theoretically requires only one reply to obtain the azimuth and range of the airframe.
1. ATCRBS all call: This interrogation consists of P1, P3 and a 0.8 s P4 pulse. P2 SLS is transmitted as 2. 3.
normal. All ATCRBS transponders reply with the 4096 identification code for mode A interrogations and altitude data for mode C. Mode S transponders do not reply on this interrogation. ATCRBS/mode S all call: This interrogation is identical to the former except P4 is 1.6 s long. ATCRBS transponders reply with the 4096 code or altitude data as per the ATCRBS all call. Mode S transponders reply with a special code, which contains the identity and the aircraft's discrete address. Mode S discrete interrogation: This interrogation is directed at a specific mode S transponder-equipped aircraft. The interrogation consists of P1, P2 and P6. P2 is transmitted via the directional antenna and hence is the same amplitude as P1 and P3. This effectively suppresses ATCRBS transponders from replying. P6 is actually a DPSK data block that contains either a 56-bit or 112-bit message. The DPSK modulation produces a spread-spectrum signal, which has immunity to interference.
When the transponder receives a valid mode S discrete interrogation, it will return a reply 128 s after reception. The reply is transmitted on 1090 MHz and uses a 56-bit or 112-bit PPM transmission. Each mode S interrogation will have a 24-bit address unique to the aircraft as well as a 24-bit parity check for validation. In basic mode S surveillance, the information is limited to altitude reporting (DF0), aircraft identification (DF4) and basic airframe information (DF11). The SSR is the main component of the interrogation and reply. The interrogation happens about 50 Hz PRF. The reply will happen at the same PRF. Once the SSR has received the reply it will decode the mode (A, C or S) and demodulate the information within each mode.
What is squitter?
A definition of squitter is a reply format transmission without being interrogated. These unsolicited replies or squitters are used to provide TCAS 2-equipped airframes with the discrete address of the squittering airframe, to enable the TCAS 2 system to acquire and track the airframe using mode S formats UF/DF0 and UF/DF16. Squitter has its origins in distance-measuring equipment (DME) transmissions. The DME ground station would broadcast unsolicited replies or squitters. When the airborne DME interrogator was in range, the squitter would be seen and the DME interrogator would then transmit a range interrogation and receive range replies from the DME ground station. This served to limit unnecessary transmissions over the air and optimized DME ground stationhandling capability. TCAS 2 systems use mode S squitters in a similar fashion; the TCAS just listens for the DF11 squitters, which contain the sending aircraft's discrete address, thereby reducing the need to interrogate over the air. The discrete address, once obtained, is placed on the TCAS 2 processor's roll call of addresses for ongoing tracking. Mode S technology has two types of squitter, a short (56 bit) DF11 acquisition squitter and the extended (112 bit) DF17 squitter.
UF and DF
The functional components of mode S are uplink format (UF) and downlink format (DF). UF is a specific interrogation originating from SSR or another airframe asking specific, addressable information about that airframe. DF is the reply from the airframe in regard to the UF interrogation. UF 0, 4, 5, 11 and 16 make up basic surveillance. Basic surveillance messages are comprised of the airframe address, parity bits and a 56-bit data word known as short interrogations and replies. UF0 is a short air-to-air surveillance for TCAS/ACAS (Figure 1). The DF0 reply will include the mode C altitude as well as the mode S address. To test DF0, its altitude reply is compared to the mode C altitude and the mode S address for verification. Also encoded in the DF0 reply is the vertical status (VS) bit, the reply information (RI) field. The VS bit will indicate a 1 if the airframe is on the ground and a 0 if it is on the air. The RI field is a four-bit word containing the airframe's true speed capability and type of reply to the interrogating airframes.
UF4 is a short, ground station request for altitude similar to the UF0 request, but initialized by the ground station (Figure 2). Testing the DF4 reply is verified against the mode C altitude and the mode S address for validity. Also encoded in the DF4 reply is the flight status (FS) field, downlink request (DR) field, utility message (UM) and the altitude code (AC) field. The FS field is a three-bit word reflecting eight different conditions of airborne, alert and special position indicator (SPI) status of the airframe. The DR field is a five-bit word that will contain the request to downlink certain airframe information. The UM field is a six-bit word that contains transponder communication status information. The AC field is a 13-bit word that contains the altitude of the airframe with special encoding for feet or metric units and if the altitude resolution is 25 feet or 100 feet.
UF5 is a short, ground station request for the airframe identity. The DF5 reply is the airframe's identification and is compared to the mode A 4096 code for validity. Also encoded in the DF5 reply is the flight status (FS) field, downlink request (DR) field, utility message (UM) and the identification (ID) field. The FS field is a three-bit word reflecting eight different conditions of airborne, alert and special position indicator (SPI) status of the airframe. The DR field is a fivebit word that will contain the request to downlink certain airframe information. The UM field is a six-bit word that contains transponder communication status information. The ID field is a 24-bit word that contains the mode A identification of the airframe. UF11 will request the airframe's mode S address. The DF11, or all-call reply, will reply with the airframe address (squitter address) as well as the capability (CA) field, parity/interrogator identifier (PI) field, the interrogator identifier (II) and surveillance identifier (SI). The CA field is a three-bit word that contains the communication capabilities of the transponder. The PI field is a 24-bit word that will report the interrogator identification code with a parity overlay. The II field is a four-bit word, from 0 to 15, containing the identification code of the interrogator. The SI field is a six-bit word, from 0 to 63, used to identify the types of surveillance. UF16 is a long, air-to-air surveillance for ACAS and is the long form of a UF0. Where the DF0 is 56 bits long, the DF16 is 112 bits long. The DF16 reply will have in it the mode C altitude, as well as the mode S address. Testing DF0, the altitude reply is compared to the mode C altitude and the mode S address for verification. Also encoded in the DF16 reply is the vertical status (VS) bit, the reply information (RI) field and the altitude code (AC) field. The VS bit will indicate a 1 if the airframe is on the ground and a 0 if it is in the air. The RI field is a four-bit word containing the airframe's true speed capability and type of reply to the interrogating airframes. The AC field is the mode S altitude that is compared to the mode C reply for validity. Also in the DF16 is the message comm V (MV) field. This field contains information used in air-to-air exchanges (coordination reply message). UF20 is the long form of a UF4. Where the DF4 is 56 bits long, the DF20 is 112 bits long. The DF20 reply is also known as comm A altitude request. The DF20 reply also contains a 56-bit message field for transferring downlinked aircraft parameters (DAPS). To properly test the DF20 reply, the UF20 must contain a reply request (RR) of 17, a designator identifier (DI) of 7 and a reply request subfield (RRS) of 0. The working component of the DF20 reply is the comm B message field (MB). Contained in the MB field is aircraft address (AA), downlink request (DR), flight status (FS) and altitude code (AC). These parameters are compared to the DF11 reply for validity. A transponder that does not have an active subsystem that will accept comm A data will not reply to a UF20 interrogation. UF21 is the long from of a UF5. Where the DF5 is 56 bits long, the DF21 is 112 bits long. The DF21 reply is also known as comm A identity request. The DF21 reply also contains a 56-bit message field for transferring downlinked aircraft parameters (DAPS). To properly test the DF21 reply, the UF21 must contain a reply request (RR) of 17, a designator identifier (DI) of 7 and a reply request subfield (RRS) of 0. The working component of the DF21 reply is the comm B message field or MB. Contained in the MB field is aircraft address (AA), downlink request (DR), flight status (FS) and identification code (ID). These parameters are compared to the DF11 reply for validity. A transponder that does not have an active subsystem that will accept comm A data will not reply to a UF21 interrogation.
message segments for this extended message. The working component of DELM is the comm D message (MD) field. This MD field works in conjunction with the number of D (ND) segments to allow for the extended message.
What is ADS-B?
As previously discussed, DF17 is the integral and working portion of automatic dependent surveillance broadcast (ADS-B) (Figure 3). Breaking down the meaning of the terms: automatic there is no interrogation needed to start the data or squitter coming from the transponder; dependent as it relies on onboard navigation and broadcast equipment to provide information to other ADS-B users; and surveillance it is a means of automatic surveillance and traffic coordination. Some of the benefits of ADS-B technology are better use of airspace, improved aircraft-onground surveillance and better safety for traffic avoidance and conflict management.
Conclusion
Will the air transport industry of tomorrow truly be a free flight community, without the need for ATC or ground surveillance? This is another discussion entirely. However, mode S will continue to evolve to meet the needs of an ever-expanding airborne community. The notion of small private aircraft and large air transports sharing the same airspace without the ever-watchful eye of ATC may be a far-fetched idea for the near term, but may become a reality in the future. Only 50 or 60 years ago, pilots coined the original phrase of IFR or I Follow Road for guidance and surveillance. All the while the pilots are relying on radio contact and visual acquisition for collision avoidance. Today, we rely upon high-tech electronics to autonomously navigate our airspace. What will the next 50 years reveal? For now, an understanding of the mode S of today and the new technologies of tomorrow is needed to provide for a safe flying environment.