Attachment 4 - SBS ADS-B and ADS-R Critical Services Spec_FAA-E-3011_Rev. A.pdf

FAA-E-3011, Rev. A/ January 7, 2015

REVISION RECORD

Revision Date Description Approval

Rev.- 6/17/2010 NCP 32528/ATO0E-SBS-1013 NAS CCB Rev. A 1/7/2015 NCP 35587/JM232-SBS-1006 Surveillance

CCB

Table of Contents

1.0 INTRODUCTION

1.1 Background

1.1.1 Automatic Dependent Surveillance-Broadcast (ADS-B)

1.1.2 Automatic Dependent Surveillance-Rebroadcast (ADS-R)

1.1.3 Traffic Information Service-Broadcast (TIS-B)

1.1.4 Flight Information Service-Broadcast (FIS-B)

1.2 Purpose

1.3 Scope

1.4 Service Description

1.4.1 Functional Overview

1.4.1.1 ADS-B Message Receive and Decode Function

1.4.1.2 Processing and Report Distribution Function

1.4.1.3 ADS-R Message Generation and Scheduling Function

1.4.1.4 ADS-R Message Transmission Function

1.4.1.5 Maintenance Function

1.4.2 External Interfaces

1.4.2.1 External Interface to Aircraft and Surface Vehicles

1.4.2.1.1 Inputs to the ADS-B/ADS-R Services from Aircraft/Vehicles

1.4.2.1.2 Outputs of the ADS-R Service to Aircraft/Vehicles

1.4.2.2 External Interface to SDPs

1.5 Document Overview

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents

2.1.1 Orders

2.1.2 Standards

2.1.3 Other Government Documents

2.2 Non-Government Documents

2.3 Documentation Sources

2.3.1 FAA Documents

2.3.2 Military and Federal Documents

2.3.3 National Telecommunications and Information Administration Documents

2.3.4 RTCA, Inc. Documents

3.0 REQUIREMENTS

3.1 Definitions

3.1.1 Access Control Mechanisms

3.1.2 ADS-B Message

3.1.3 ADS-B Report

3.1.4 ADS-B Service

3.1.5 ADS-B Service Volume

3.1.6 ADS-B/ADS-R Service

3.1.7 ADS-R Message

3.1.8 ADS-R Service

3.1.9 ADS-R Service Volume

3.1.10 Aircraft Surveillance Applications (ASA)

3.1.11 Client

3.1.12 Coverage Volume

3.1.13 Compact Position Reporting (CPR)

3.1.14 Service Status Report

3.1.15 Data Source Validation

3.1.16 Duty Cycle

3.1.17 Least Significant Bit (LSB or Lsb)

3.1.18 ME Field

3.1.19 Most Significant Bit (MSB or Msb)

3.1.20 Receiver

3.1.21 SBS Monitor

3.1.22 Service Availability

3.1.23 Service Delivery Point

3.1.24 Service Domain

3.1.25 Service Enhancement

3.1.26 Service Volume

3.1.27 Shall

3.1.28 Should

3.1.29 State Vector

3.1.30 Transmitter

3.1.31 Update Interval

3.1.32 UAT Message Payload

3.1.33 UAT Optimum Sample Point

3.1.34 Validation

3.1.35 Victim

3.1.36 Will

3.1.37 Type 1 Duplicate

3.1.38 Type 2 Duplicate

3.1.39 Composite Traffic Volume

3.2 Functional Requirements

3.2.1 ADS-B Message Receive and Decode

3.2.1.1 1090ES

3.2.1.2 UAT

3.2.2 Processing and Report Distribution

3.2.2.1 Message to Report Conversion

3.2.2.1.1 1090ES Squitter Processing

3.2.2.1.1.1 Input Message Reception and Processing

3.2.2.1.1.1.1 Message Format Version Determination

3.2.2.1.1.1.2 CPR Decode

3.2.2.1.1.1.3 Message Information Storage

3.2.2.1.1.1.4 Duplicate 24 Bit Addresses and Position Outliers: Same Radio Station Receiver

3.2.2.1.1.1.5 Duplicate 24 Bit Addresses: Different Radio Station Receivers

3.2.2.1.1.2 ADS-B Report Generation

3.2.2.1.2 UAT Processing

3.2.2.1.2.1 Message Information Storage

3.2.2.1.2.2 ADS-B Report Generation

3.2.2.1.3 Service Volume Identifier and Data Source Qualifier

3.2.2.1.4 Special Report Processing Requirements Common to Both Links

3.2.2.1.5 Special UAT Report Processing to Support Dual Link Test Aircraft

3.2.2.2 Independent Validation

3.2.2.3 Report Configuration and Filtering

3.2.2.3.1 Certified Aircraft List for Link Version 1 Targets

3.2.2.4 Report Formatting and Output

3.2.3 ADS-R Message Generation and Scheduling

3.2.3.1 1090ES Specific

3.2.3.1.1 ADS-R Message Encoding

3.2.3.1.1.1 Message Types

3.2.3.1.1.2 Extrapolation

3.2.3.1.1.3 CPR Encoding

3.2.3.1.2 ADS-R Message Payload

3.2.3.2 UAT Specific

3.2.4 ADS-R Message Transmission

3.2.4.1 1090ES Specific

3.2.4.1.1 1090ES Transmitter Characteristics

3.2.4.1.2 Media Access

3.2.4.1.3 Duty Cycle Limitations

3.2.4.1.3.1 Secondary Surveillance Radar (SSR) Sidelobes

3.2.4.1.3.2 SSR Main Beam

3.2.4.1.3.3 Multilateration R/T

3.2.4.2 UAT Specific

3.2.4.2.1 UAT Transmitter Characteristics

3.2.4.2.1.1 Modulation Rate

3.2.4.2.1.2 Modulation Distortion

3.2.4.2.1.3 Message Maximum Power

3.2.4.2.2 UAT Media Access

3.2.5 Maintenance Processing

3.2.5.1 SBS Monitor Maintenance Data Sets

3.2.5.1.1 Mode Reporting

3.2.5.1.2 Monitored Parameters State Reporting

3.2.5.1.3 Service Volume Message Counts

3.2.5.2 ADS-B Test Report

3.2.5.2.1 UAT

3.2.5.2.2 1090ES

3.2.5.2.3 Processing Requirements for Generating the Cat 33 ADS-B Test Report

3.2.5.2.4 Monitoring ADS-B Test Reports

3.3 Performance Requirements

3.3.1 Performance Environment

3.3.1.1 Type of Service Volume

3.3.1.2 Service Volume Dimensions

3.3.1.3 Service Domain

3.3.1.4 Operating Environment

3.3.1.4.1 Interference Environment

3.3.1.4.2 Capacity

3.3.1.4.3 Scalability

3.3.1.5 Independent Validation Required

3.3.1.6 ADS-B Service Delivery Points

3.3.1.7 Data Links

3.3.1.8 List of 1090 “Victim” Receivers in the Service Volume

3.3.1.9 Composite Traffic Volume

3.3.2 Performance Requirements

3.3.2.1 Operating Environment

3.3.2.2 ADS-B Service

3.3.2.2.1 ADS-B Report Integrity

3.3.2.2.2 Position Update Interval

3.3.2.2.2.1 Surface Update Requirements

3.3.2.2.2.2 Terminal Airspace Update Intervals

3.3.2.2.2.3 En Route Airspace Update Intervals

3.3.2.2.2.4 Update Interval for Other Information

3.3.2.2.2.5 Enhancements

3.3.2.2.3 Latency

3.3.2.2.4 Independent Validation Performance

3.3.2.2.5 Enhanced Validation

3.3.2.2.6 ADS-B Service Availability

3.3.2.3 ADS-R Service

3.3.2.3.1 ADS-R Extrapolation Accuracy

3.3.2.3.2 Latency

3.3.2.3.3 Information Integrity

3.3.2.3.4 ADS-R Update Interval

3.3.2.3.5 ADS-R Service Availability

3.3.2.3.6 Service Enhancements

3.3.2.3.7 TIS-B / ADS-R Service Status

3.3.3 Maintenance Processing

3.4 Interfaces

3.5 Security

4.0 QUALITY ASSURANCE

4.1 Test Program

4.1.1 General

4.1.2 Phases of Test

4.1.2.1 First Article

4.1.2.1.1 Service Provider Qualification Tests

4.1.2.1.1.1 Factory Acceptance Test (FAT)

4.1.2.1.1.2 Service Integration Test (SIT)

4.1.2.1.1.3 Service Acceptance Test (SAT)

4.1.2.1.2 Government Qualification Tests

4.1.2.1.2.1 End-to-End System Test (EEST)

4.1.2.1.2.2 Operational Test and Evaluation (OT&E)

4.1.2.1.2.3 Independent Operational Test and Evaluation (IOT&E)

4.1.2.2 Implementation

4.1.2.2.1 Implementation Service Acceptance Test (ISAT)

4.1.2.2.2 Implementation System Test (IST)

4.1.2.3 Life Cycle

4.1.2.3.1 Service Re-Qualification Test (SRQT)

4.1.2.3.2 Service Performance Monitoring (SPM)

4.1.2.3.3 Government Performance Monitoring (GPM)

4.1.3 Verification Requirements Traceability Matrix (VRTM)

4.1.4 Verification Methods

List of Tables

Table 3-1: ADS-B Message Parameter Validity Time Table 3-2: 1090ES ADS-B Message (Version 1 and Version 2) to ADS-B Report Mapping Table 3-3: 1090ES ADS-B Message (Version 0) to ADS-B Report Mapping Table 3-4: ADS-B Message Parameter Validity Time (UAT) Table 3-5: UAT ADS-B Message to ADS-B Report Mapping Table 3-5a: Test Aircraft - Special UAT Report Processing Table 3-6: ADS-R Uplink Response based on Client Rx Equipage Table 3-7: 1090ES ADS-R Message Types to Encode Upon Receipt of UAT Message Types Table 3-8: Payload Composition of 1090ES ADS-R Messages Table 3-9: Payload Composition of UAT ADS-R Messages Table 3-10: Maintenance Data Sets Table 3-11: Fault Reports Table 3-12: Payload Composition of UAT Test Message Table 3-13: Payload Composition of 1090ES Critical Services Test Message Table 3-14: Generating the ADS-B Test Report Table 3-15: Traffic Density Environments Table A-1: NACp Coding Values Table A-2: NACp Coding Values Table B-3: Format of Individual ADS-R Customer Address

List of Figures

Figure 1-1: Surveillance and Broadcast Services Partitioning Figure 1-2: ADS-B/ADS-R Services Functions Figure 3-1: 1090ES Duty Cycle Limitations for Transmitters Within RLOS of an SSR Unit –

Sidelobe Reception Figure 3-2: 1090ES Duty Cycle Limitations for Transmitters Within RLOS of an SSR Unit –

Main Beam Reception Figure 3-3: 1090ES Duty Cycle Limitations for Transmitters Within RLOS of a Multilateration

R/T Figure 3-4: UAT Frame Figure 3-5: Service Volumes (SV) Figure 3-6: Mode S Reply Rate Distributions for Ground Receiver Figure 3-7: ATCRBS Reply Rate Distributions for Ground Receiver Figure 3-8: Mode S Reply Rate Distributions for Airborne Receiver Figure 3-9: ATCRBS Reply Rate Distributions for Airborne Receiver

1.0 INTRODUCTION

1.1 Background

The Federal Aviation Administration (FAA)’s Surveillance and Broadcast Services Program plans to introduce Automatic Dependent Surveillance–Broadcast (ADS-B) technology based Services into the NAS. Four distinct Services are to be provided:

Automatic Dependent Surveillance-Broadcast (ADS-B).

Automatic Dependent Surveillance-Rebroadcast (ADS-R).

Traffic Information Service-Broadcast (TIS-B).

Flight Information Service-Broadcast (FIS-B).

The Service requirements are documented in two separate specifications: (1) ADS- B/ADS-R Services and (2) TIS-B/FIS-B Services.

The ADS-B Service will support critical Air Traffic Control (ATC) Surveillance applications in the NAS. The ADS-R Service will support specified air-to-air applications involving aircraft which are equipped with different ADS-B links. The ADS-R Service will be deployed at an “Essential” level until such time as the ADS-R Service is required to provide a critical level of functionality.

The TIS-B/FIS-B Services will provide traffic, weather, and NAS Status information to equipped aircraft/vehicles, supporting airborne applications at the “Essential” level.

Surveillance data, including that from radar systems and ADS-B receptions, will be output as part of providing the TIS-B Service

The Essential and Critical level Services will provide data to FAA defined Service Delivery Points (SDP). The SDPs are the demarcation point between the Services and the systems which ultimately use the data on the ground. The Essential level Services will provide TIS-B, FIS-B, ADS-B, and Services Status Reports to authorized user systems and the SBS Monitor system, via SDPs. The Critical level Services will provide ADS-B and Service Status Reports to ATC Automation, other authorized user systems, and the SBS Monitor system, via SDPs.

The Service Provider may provide data to user systems in addition to those specified by the FAA, but has to comply with FAA Order 1200.22 (current version), Data and Interface Equipment Used by Outside Interests, and have FAA approval.

Figure 1-1 provides an overview of the partitioning of these Services between the two specifications. Each Service is described in the following paragraphs.

1.1.1 Automatic Dependent Surveillance-Broadcast (ADS-B)

ADS-B equipped aircraft and vehicles broadcast their state vector (horizontal and vertical position, horizontal and vertical velocity) and other information over one of the link technologies approved for use in the NAS, Universal Access Transceiver (UAT) or 1090 MHz Extended Squitter (1090ES). These ADS-B Message broadcasts are intercepted by other aircraft in the vicinity and by the ADS-B ground infrastructure.

Aircraft equipped with the proper equipment receive the ADS-B Messages and process and display the information for use in air-to-air applications. The ADS-B ground infrastructure processes ADS-B Messages that are transmitted by aircraft/vehicles on each data link and formats them into a common ADS-B Report format. These ADS-B Reports are delivered to ATC for use in separation assurance and other services.

1.1.2 Automatic Dependent Surveillance-Rebroadcast (ADS-R)

The FAA’s 2002 ADS-B Link Decision approved two data link technologies, UAT and 1090ES, for use in the NAS. As aircraft operating in the NAS or a vehicle operating in the movement area of an airport may equip with either UAT or 1090ES, the ground infrastructure will provide a Service to rebroadcast ADS-B data, which is received via one data link, on the other data link in some areas. This and the TIS-B Service will provide aircraft equipped with either UAT or 1090ES data link technologies a more complete air and airport surface picture. The ADS-R Service will eventually be provided at a level sufficient to support specified critical applications.

The ADS-R Service is to be provided when two data links are implemented for the ADS- B Service. If a single data link is used, the ADS-R Service is not necessary provided all aircraft are equipped with the same link technology.

1.1.3 Traffic Information Service-Broadcast (TIS-B)

During NAS-wide deployment of ADS-B, aircraft will begin equipping with ADS-B avionics. Equipped aircraft will receive broadcast ADS-B Messages directly from other aircraft equipped with the same data link technology. Thus an aircraft equipped with a particular data link will have, in the absence of ground infrastructure, surveillance information only on like-equipped aircraft. The aircraft will lack surveillance information on other aircraft in the vicinity that are not ADS-B equipped and those that are equipped with the other data link technology. The Surveillance and Broadcast Services ground infrastructure will support air-to-air applications by broadcasting TIS-B Messages for targets detected and reported by radar, or other non-ADS-B surveillance systems, on both the UAT and 1090ES data links for reception by equipped aircraft.

This, in conjunction with the ADS-R Service, will provide equipped aircraft the information needed for a more complete air and airport surface picture of traffic in their vicinity. The TIS-B Service will support only essential level applications.

1.1.4 Flight Information Service-Broadcast (FIS-B)

FIS-B provides the broadcast of weather and non-control, advisory information providing users valuable, near real-time aeronautical information, supporting safe and efficient operations. Broadcast of FIS is limited to the UAT link. FIS-B products include, but are not limited to: Graphical and textual weather reports and forecasts, Special Use Airspace (SUA) information, Notice to Airmen (NOTAMS), electronic pilot reports (E-PIREPS), and other similar meteorological and aeronautical information. FIS-B products, from both Government and commercial sources, will be broadcast to aircraft from the ground.

In the future, aircraft equipped with the UAT data link may also broadcast FIS-B products within ADS-B Messages.

1090ES TX UAT TX1090ES RX UAT RX

FIS-B

Processing

TIS-B

Processing

UAT TX

Ground Interface Function

1090ES TX

TIS-B Data Sources

FIS-B Data Sources

ADS-B Critical Service + ADS-R Service*

TIS-B & FIS-B

Essential Service

Uplink Air InterfaceDownlink Air Interface Uplink Air Interface

ADS-B

Downlink ADS-R Broadcast

TIS-B

Broadcast

FIS-B

Broadcast

Boundary of Performance Specifications #1 & #2

Contractor Monitoring and Control

Ground Interface & ADS-R Processing Function

Operational & other Data

FAA

Monitoring

Other Data Users

(e.g. Airlines)

ATC

Automation & Display

ADS-B Equipped Aircraft & Vehicles

ADS-B Equipped Aircraft & Vehicles

Contractor Monitoring and Control

FAA

Monitoring

Other Data Users

(e.g. Airlines)

ADS-B

Downlink

Downlink Air Interface

UAT RX 1090ES RX

SDP SDP SDP

SDP SDP

*Design = Critical, Initial Implementation = Essential

Figure 1-1: Surveillance and Broadcast Services Partitioning

FAA-E-3011, Rev. A/Date

1.2 Purpose

This document is to be used in the procurement of Service Provider provided ADS-B and ADS-R Services per the requirements in this document.

1.3 Scope

This document details the requirements for ADS-B and ADS-R Services that the Federal Aviation Administration (FAA) will acquire under the Surveillance and Broadcast Services Program. The required functionality of the Services as well as the performance that is required is included herein. The interfaces that the Services are to provide are also specified.

1.4 Service Description

ADS-B/ADS-R Services will be deployed NAS-wide on the airport surface and in terminal and en route airspace. As these Services will operate, in many cases, in the same airspace as TIS-B/FIS-B Services, the two will be transmitting in the same coverage.

1.4.1 Functional Overview

The ADS-B Service receives ADS-B Messages transmitted on either the UAT or 1090ES data links, generates ADS-B Reports based on these messages, and distributes the ADS- B Reports to SDPs. The SDPs may be ATC Automation systems, authorized user systems, or systems that further distribute data to end user systems. The ADS-B Rebroadcast (ADS-R) Service transmits an ADS-B Message on a given ADS-B data link based upon a reception of an ADS-B Message over the other data link. ADS-R makes it possible for aircraft using one link to make use of information being transmitted by aircraft using the other link.

ADS-B/ADS-R Services can logically be broken into five major functions. This division of functionality is not meant to imply any particular architecture. The functions are offered only as a convenient means of describing and organizing the requirements for the Services. Figure 1-2 summarizes the ADS-B/ADS-R Services functions, inside the shaded box, and the external interfaces, outside of the box. The TIS-B and FIS-B Service functions are shown to fully represent the functionality of the Surveillance and Broadcast Services, but are not addressed in this specification.

Aircraft / Vehicle Service Delivery Point

TIS-B

Surveillance Processing

ADS-B Message Receive &

Decode Function

FIS-B

Processing

ADS-B

Messages

TIS-B / FIS-B

Message

Transmission Function

TIS-B & FIS-B

Messages

Surv.

Sources (Radar, Multi-lat) FIS-B Data

Sources

Maintenance Function

Processing and Report Distribution Functions

ADS-B

Message

Receive & Decode

Functions

Maintenance Function

ADS-B

Messages

ADS-R

Message

Generation and

Scheduling Function

ADS-R

Message Transmit Function

ADS-B / ADS-R

Service Status

ADS-R

Messages

Validation Information

ADS-B

Reports

Service Delivery Points (FAA Monitoring, ATC, or Authorized Users)

ADS-B & ADS-R

Service

TIS-B & FIS-B

Service

TIS-B

Reports*

* - TIS-B Reports include information from multiple surveillance sources, including ADS-B (see §3.2.1.1.4 & §3.4.3 in Essential TIS-B/FIS-B Services Specification)

FIS-B

Reports

TIS-B / FIS-B Service, & Surv. Status Reports

Figure 1-2: ADS-B/ADS-R Services Functions

1.4.1.1 ADS-B Message Receive and Decode Function

The ADS-B Message Receive and Decode Function receives the Radio Frequency (RF) ADS-B Messages, on both UAT and 1090ES data links, and recovers the Message payloads. This function may be resident at one or more ground locations as required to provide the specified ADS-B Service Volume. The ADS-B Message Receive and Decode Function box in Figure 1-2 is meant to represent all ground locations that are required per the Service Provider’s design to cover the ADS-B Service Volume required by the FAA. The ADS-B Message Receive and Decode Function sends the decoded ADS-B Messages to the Processing and Report Distribution Function.

1.4.1.2 Processing and Report Distribution Function

The Processing and Report Distribution Function takes the decoded ADS-B Message information and formats it into ADS-B Reports. The function addresses the circumstance of multiple targets broadcasting the same target address (described in detail in Section §3.2.2.1.1.4) on the 1090ES link.

Specifically, the Processing and Report Distribution Function:

• Performs validation processing using independent measurements (if required in the Service Volume),

• Generates ADS-B Reports from received ADS-B Messages,

• Provides for configuration of certain parameters

• Filters Reports based on specified criteria, and

• Distributes ADS-B Reports in FAA CAT033 format to SDPs.

1.4.1.3 ADS-R Message Generation and Scheduling Function

The ADS-R Message Generation and Scheduling Function considers ADS-B Messages received over one data link for rebroadcast on the other link. The Function:

• Suppresses the rebroadcast of Messages when validation is not successful and also when aircraft are broadcasting on both ADS-B data links,

• Extrapolates the received position data within a processed ADS-R Report to the Time of Applicability appropriate for the data link on which the ADS-R Message(s) are to be broadcast,

• Constructs and schedules the ADS-R Message(s) that is (are) to be broadcast on the other ADS-B data link, including repeating Messages, if appropriate, in order to ensure adequate reception probability within the Service Volume,

• Outputs the scheduled ADS-R Messages to the ADS-R Message Transmission Function.

1.4.1.4 ADS-R Message Transmission Function

The ADS-R Message Transmission Function broadcasts the ADS-R Messages it receives from the ADS-R Message Generation and Scheduling Function on the indicated link.

This function will be resident at one or more ground locations as required to support the specified ADS-R Service Volume. The ADS-R Message Transmission Function box in Figure 1-2 is meant to represent all ground locations that are required to support the Service Volume. The ADS-R Message Transmission Function applies rate limiting to the transmission of ADS-R Messages according to the spectrum license limitations of each ADS-B data link.

1.4.1.5 Maintenance Function

Maintenance function includes, but is not limited to, providing status on transmit/receive equipment and service to the FAA. The Maintenance function also includes the statistics on the quality of the data within the service volume.

1.4.2 External Interfaces

ADS-B/ADS-R Services interface to the following external systems:

• Aircraft and Surface Vehicles equipped with UAT and 1090ES ADS-B avionics

• SDPs (ATC Automation Systems, SBS Monitor Systems, and other authorized external users)

Note: The ADS-R Service provides only inputs to the Service Status Reports.

Detailed interface requirements between these systems are contained in Interface Requirements Documents referenced in sections §2 and §3.

The Service Provider may provide data to user systems in addition to those specified by the FAA, but has to comply with FAA Order 1200.22 (current version), Data and Interface Equipment Used by Outside Interests, and have FAA approval.

1.4.2.1 External Interface to Aircraft and Surface Vehicles

The interfaces to Aircraft/Vehicles are largely defined by the UAT and 1090ES data link MOPS. Any additional requirements for these interfaces are specified herein, thus Interface Requirements Documents (IRDs) are not needed.

1.4.2.1.1 Inputs to the ADS-B/ADS-R Services from Aircraft/Vehicles

The ADS-B Service receives ADS-B Messages on the UAT and 1090ES links from Aircraft and Surface Vehicles to support ATC surveillance applications and the ADS-R Service. The ADS-B Message Receive and Decode Function of the ADS-B/ADS-R Services System accepts and processes the incoming ADS-B Messages such as the aircraft’s position, velocity, identification, and accuracy/integrity measures of position/velocity. ADS-B Messages are decoded based upon the MOPS Version number contained in the transmitted ADS-B Messages received from equipped aircraft or surface vehicles. UAT equipment complies with either RTCA DO-282A, MOPS Version number 1, or RTCA DO-282B, MOPS Version number 2. 1090ES equipment comply with either RTCA DO-260, MOPS Version number 0, RTCA DO-260A, MOPS Version number 1 or RTCA DO-260B, MOPS Version number 2. To meet specified Service Volume requirements, a network of ground sites (i.e., implementations of the ADS-B Message Receive and Decode Function) may be required to receive and decode the transmitted ADS-B Messages from the ADS-B equipped aircraft/vehicles.

1.4.2.1.2 Outputs of the ADS-R Service to Aircraft/Vehicles

The ADS-R Service transmits ADS-R Messages on the UAT and 1090ES links through the ADS-R Message Transmission Function. This Function broadcasts on one data link ADS-B Messages that are received on the other data link. The ADS-R Service uplinks ADS-R Messages in accordance with the received MOPS Version number of the transmitting aircraft/vehicle.

1.4.2.2 External Interface to SDPs

The ADS-B Service sends ADS-B Reports to SDPs, supporting ATC Automation Systems, SBS Monitor Systems, and other authorized external users including Airlines Operations Centers. The ADS-B Reports contain principally surveillance related data on aircraft within the Service Volume. The ADS-B/ADS-R Services additionally send Service Status Reports containing monitored information, such as alerts and alarms to SDPs. The minimum set of monitored parameters are described in Section §3.2.5 of this document.

1.5 Document Overview

Section §2 lists reference documents that are applicable to this specification. Section §3 includes definitions and requirements for the ADS-B/ADS-R Services. Section §4 contains the ADS-B/ADS-R quality assurance information.

Appendix A provides details for calculating the NIC and NACp values for the ADS-B test Report.

Appendix C provides Aircraft/Vehicle antenna information.

2.0 APPLICABLE DOCUMENTS

2.1 Government Documents

The following documents form a part of this specification and are applicable to the extent specified here. In a case of conflict between the documents referenced here and the contents of this specification, the contents of this specification shall [0000] take precedence.

2.1.1 Orders

Orders: Title:

FAA Order 1200.22 (current version)

Data and Interface Equipment Used by Outside Interests

2.1.2 Standards

FAA Documents: Title:

SBS fPR Final Program Requirements for Surveillance and Broadcast Services, Version 2.1, FAA, August 6, 2007

FAA-E-3006

Traffic Information Service – Broadcast (TIS-B) / Flight Information Service – Broadcast (FIS-B) Essential Services Specification, Version 2.4 dated April 20, 2011

FAA TSO C154C

Universal Access Transceiver (UAT) Automatic Dependent Surveillance - Broadcast (ADS-B) Equipment Operating on the Frequency of 978 MHz, December 2, 2009

FAA TSO C166B

Extended Squitter Automatic Dependent Surveillance - Broadcast (ADS-B) and Traffic Information Service - Broadcast (TIS-B) Equipment Operating on the Radio Frequency of 1090 Megahertz (MHz), December 2, NAS-IR-82530001 (NAS-

IR-SBS SDP)

Surveillance and Broadcast Services (SBS) Service Delivery Point (SDP) to ATC Automation and Service Monitoring User Subsystems Interface Requirements Document (IRD), Current Version

FAA Documents: Title:

NAS-IR-82530002

Surveillance and Broadcast Services (SBS) Service Delivery Point (SDP) Common Digitizer-2 (CD-2) / En Route Communications Gateway (ECG) Interface Requirements Document (IRD), Version 3.2 dated December 3, 2010

NAS-RD-2012 NAS

System Requirements Specification, 4 December 2012

Military Documents: Title:

MIL-STD-810F Environmental Test Methods and Engineering Guidelines, January 1, 2000

2.1.3 Other Government Documents

NTIA Documents: Title:

Manual of Regulations and Procedures for Federal

Radio Frequency Management, May 2003 Edition with January 2006 Revisions

2.2 Non-Government Documents

RTCA Documents: Title:

DO-260B

Minimum Operational Performance Standards for 1090 MHz Extended Squitter Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic Information Services – Broadcast (TIS-B), December

DO-282B

Minimum Operational Performance Standards for Universal Access Transceiver (UAT) Automatic Dependent Surveillance – Broadcast (ADS-B)

DO-289

Minimum Aviation Systems Performance Standards (MASPS) for Aircraft Surveillance Applications, December 9, 2003 Note: Any reference to RTCA/DO-282A in this specification is to be interpreted as including Change 1.

DO-289, Change 1

Minimum Aviation System Performance Standards (MASPS) for Aircraft Surveillance Applications (ASA), December 13, 2006 Note: Any reference to RTCA/DO-282A in this specification is to be interpreted as including Change 1.

RTCA Documents: Title:

RTCA Free Flight Select Committee, Safe Flight 21 Steering Committee, and Eurocontrol ADS-B Programme ADS-B Technical Link Assessment Team, “Technical Link Assessment Report”, March 2001, is also available at http://adsb.tc.faa.gov/WG6_Meetings/Meeting4.htm

2.3 Documentation Sources

2.3.1 FAA Documents

Copies of FAA specifications, standards, and publications may be obtained from the FAA Contracting Officer. Requests should clearly identify the desired material by number and state the intended use of the material.

2.3.2 Military and Federal Documents

Single copies of unclassified military and federal specifications, standards, and publications may be obtained by writing the Naval Publications and Forms Center, 5801 Tabor Avenue, Philadelphia, PA 19120 or by calling (215) 697 3321 Monday through Friday, 8:00 am to 4:30 pm (EST).

2.3.3 National Telecommunications and Information Administration Documents

Copies of National Telecommunications and Information Administration (NTIA) materials may be obtained from NTIA, Department of Commerce, 14th Street and Constitution Avenue NW, Washington, DC 20230, by calling (202) 377-1832, or through the web site http://www.ntia.doc.gov.

2.3.4 RTCA, Inc. Documents

Copies of RTCA, Inc. documents may be obtained from RTCA, Incorporated, 1828 L Street NW, Suite 805, Washington, DC 20036, by calling (202) 833-9339, or through the web site http://www.rtca.org.

http://www.ntia.doc.gov/ http://www.rtca.org/

3.0 REQUIREMENTS

Two data links have been approved for use in the NAS. The requirements in this document support the use of one or both of those data links. If both data links are utilized in the Service design, then all requirements within this document apply to the ADS-B/ADS-R Services. If a single data link is used in the ADS-B Service, then the ADS-R requirements and all requirements associated with the unused data link do not apply.

If the Service Provider chooses to use a data link not described in this document to support ADS-B/ADS-R Services, all functional, performance, interface, and security requirements in Sections §3.2, §3.3, §3.4, and §3.5 shall [4127] be met for these Services with the exception of those functional requirements that are not applicable due to the characteristics of the selected link.

The ADS-B/ADS-R Service shall [4128] meet all requirements in Section §3.2, §3.3, §3.4, and §3.5 when the 1090ES and UAT data links are used in the Service design.

When a single data link is used in the Service design, the functional, performance, interface, and security requirements associated with providing the ADS-B Service on that data link shall [4129] be met.

3.1 Definitions

The definitions in this Section are for informational purposes. Should any of these terms need to become a part of the Contract between the Service Provider and the Government, they will be specifically incorporated in the Contract.

3.1.1 Access Control Mechanisms

Protection of system resources against unauthorized access; a process by which use of system resources is regulated according to a security policy and is permitted by only authorized entities according to that policy.

3.1.2 ADS-B Message

An ADS-B Message is an expression of the ADS-B target information in a data link specific format broadcast from aircraft/vehicles. ADS-B Messages are transmitted and received on either the UAT or 1090ES data links, per the formats defined in the Minimum Operational Performance Standards (MOPS) documents, RTCA/DO-282B and RTCA/DO-260B, respectively.

3.1.3 ADS-B Report

ADS-B information concerning a single target expressed in a data link independent format and exchanged between non-RF systems. An ADS-B Report is derived from one or more ADS-B Messages received on either the UAT or 1090ES data link. The ADS-B Report is provided in the FAA CAT033 Report format detailed in NAS-IR-SBS SDP.

3.1.4 ADS-B Service

The ADS-B Service as used in this document applies to the component of the Surveillance and Broadcast Services ground infrastructure that receives ADS-B Messages, processes them, and distributes them in the form of ADS-B Reports to the SDPs and the ADS-R Service.

3.1.5 ADS-B Service Volume

For purposes of this specification, the ADS-B Service Volume is the volume in which the performance of the ADS-B Service satisfies the ADS-B Service requirements in this document.

3.1.6 ADS-B/ADS-R Service

ADS-B/ADS-R Service refers to the entire scope of Services defined in this specification. The terminology is used when not appropriate to use the more specific ADS-B or ADS-R Service.

3.1.7 ADS-R Message

An ADS-R Message is broadcast, by the ADS-B Rebroadcast Service, on either the UAT or 1090ES data link, per the TIS-B Message format in RTCA/DO-282B and the ADS-B Rebroadcast Message formats defined in §2.2.18 of RTCA/DO-260B. An ADS-R Message is the retransmission of ADS-B data that was received on one data link on the other data link.

3.1.8 ADS-R Service

The ADS-B Rebroadcast (ADS-R) Service rebroadcasts ADS-B Messages received over one ADS-B data link on the other ADS-B data link.

3.1.9 ADS-R Service Volume

The ADS-R Service Volume is the volume in which the performance of the ADS-R Service satisfies the requirements of specific air-to-air applications. In some cases, the ADS-R Service volume may be smaller than the corresponding ADS-B Service Volume.

3.1.10 Aircraft Surveillance Applications (ASA)

The Aircraft Surveillance Applications (ASA) system comprises a number of flight-deck based aircraft surveillance and separation assurance applications that may directly provide flight crews with surveillance information as well as surveillance-based guidance and alerts. Surveillance information consists of position and other state data about other aircraft, and also, when on or near the airport surface, position and other state data about appropriately equipped surface vehicles or obstacles. The situational awareness and separation assurance capabilities of ASA are provided by applications.

Numerous applications have been proposed, and it is expected that additional applications will be developed and standardized in future versions of the ASA MASPS (RTCA/DO-289). The ASA MASPS specifies detailed requirements for an initial set of applications. The following five applications are specified in detail: (1) Enhanced Visual Acquisition, (2) Conflict Detection, (3) Airport Surface Situational Awareness,

(4) Final Approach and Runway Occupancy Awareness, and (5) Enhanced Visual Approach.

3.1.11 Client

Aircraft that are identified as being eligible to receive ADS-R and TIS-B services based on their ADS-B Out/In equipage and ADS-B reporting performance level.

3.1.12 Coverage Volume

A Coverage Volume is an airspace volume within which Broadcast Services are provided. Service is ordered on a Coverage Volume basis. A Coverage Volume contains one or more Service Volumes.

3.1.13 Compact Position Reporting (CPR)

The Mode-S 1090 MHz ADS-B Extended Squitters use Compact Position Reporting (CPR) to encode latitude and longitude efficiently into fewer bits of the 1090ES Message than would otherwise be required to specify the position of the aircraft. The resulting 1090ES Messages are compact in the sense that several higher-order bits, which are normally constant for long periods of time, are not transmitted in every message. For example, in a direct binary representation of latitude, one bit would designate whether the aircraft is in the northern or southern hemisphere. This bit would remain constant for a long time, possibly the entire life of the aircraft. To repeatedly transmit this bit in every position message would be inefficient. Because the higher-order bits are not transmitted, it follows that multiple locations on the earth will produce the same encoded position. If only a single 1090ES Position Message were received, the decoding would involve ambiguity as to which of the multiple solutions is the correct location of the aircraft. The CPR technique includes a provision to enable a receiving system to unambiguously determine the location of the aircraft. This is done by encoding in two ways that differ slightly. The two formats, called even-format and odd-format, are each transmitted 50 per cent of the time. Upon reception of both types within a short period (approximately 10 seconds), the receiving system can unambiguously determine the location of the aircraft. Once this process has been carried out, the higher-order bits are known at the receiving station, so subsequent single message receptions serve to unambiguously indicate the location of the aircraft as it moves.

3.1.14 Service Status Report

A Service Status Report contains Service status information and is generated periodically by the ADS-B/ADS-R Service. The Service Status Report is provided in the FAA CAT023 Report format detailed in NAS-IR-SBS SDP.

3.1.15 Data Source Validation

The process of proving the identity of the data source.

3.1.16 Duty Cycle

The percentage of time the transmit function is keyed in proportion to total service time.

3.1.17 Least Significant Bit (LSB or Lsb)

The least significant bit of data.

3.1.18 ME Field

The ME Field is the 56 bits that define the Mode-S 1090 MHz Extended Squitter (1090ES) Message.

3.1.19 Most Significant Bit (MSB or Msb)

The most significant bit of data.

3.1.20 Receiver

The term “receiver” as used in this document refers to the receiver sub-function of the ADS- B Message Receive and Decode Function.

3.1.21 SBS Monitor

The SBS Monitor is a Government system that will independently monitor the performance of Surveillance and Broadcast Services. To the ADS-B/ADS-R Services, the SBS Monitor will be a Service Delivery Point.

3.1.22 Service Availability

Service Availability (A0) is defined as:

( )DowntimeUptime UptimeAo +

Uptime is defined as the element of time during which the service provider’s system is performing its required service functions. Downtime is the element of time during which the service provider’s system is not performing its required service functions. The sum of Uptime and Downtime is the total time the service is planned to be provided by the Service Provider. It excludes time for testing and integration prior to the service being made available for operational use.

3.1.23 Service Delivery Point

The Service Delivery Point is the physical demarcation point for the ADS-B Service.

ADS-B Reports and Service Status Reports are delivered by the ADS-B/ADS-R Services to the Service Delivery Point. The specific Service Delivery Points for each Service Volume will be defined in the Contract Schedule. Each ADS-B Service Volume will have one or more SDPs. The interface between the ADS-B Service and the SDP is defined in NAS-IR-SBS SDP.

3.1.24 Service Domain

For purposes of this specification, there are three Service domains: (1) Surface, (2) Terminal, and (3) En Route/Off-Shore. Each Service Volume specified by the FAA will have a single domain identified.

3.1.25 Service Enhancement

Capabilities identified as desirable for the ADS-B Service to meet a future need but are not within the “core” capabilities for the ADS-B, ADS-R, TIS-B, and FIS-B services.

The Service would need to provide these enhanced capabilities in the future, if and when they are ordered. Included in this specification are the currently identified Service Enhancement (SE) requirements. Service Enhancement requirements are noted with an “SE” marking following the requirement number for each sentence containing the requirements for these future capabilities.

3.1.26 Service Volume

A Service Volume is an airspace volume within which a specific Broadcast Services application is supported and the associated performance requirements are achieved. A Service Volume lies within a Coverage Volume (see Figure 3-5).

3.1.27 Shall

When used in this specification, the word “shall” refers to an explicit requirement of a service function or the entire service.

3.1.28 Should

When used in this specification, the word “should” refers to a desired characteristic of a service function or the entire service.

3.1.29 State Vector

A State Vector includes horizontal and vertical position and horizontal and vertical velocity.

3.1.30 Transmitter

The term “transmitter” as used in this document refers to the ADS-R Message Transmission Function.

3.1.31 Update Interval

Update interval refers to the time between two successive ADS-B Reports for a particular aircraft that are based on the reception of ADS-B Messages containing position information.

3.1.32 UAT Message Payload

UAT Message Payload is that portion of the UAT Message that carries data (user information) that will be consumed by application systems outside the UAT system.

3.1.33 UAT Optimum Sample Point

The point during the bit period at which the opening of the eye diagram (i.e., minimum separation between positive and negative frequency offsets at very high signal-to-noise ratios) is maximized.

3.1.34 Validation

Validation is the process of performing a check on whether or not the position information reported in an ADS-B Message from a particular aircraft/vehicle could reasonably have been transmitted from the reported location. Validation processing is an option in the ADS-B Service Volumes. When the option is exercised, the ADS-B Service will perform validation processing.

3.1.35 Victim

In this document, the term “victim” is used to refer to existing receivers/antennas on the 1090 MHz frequency belonging to other systems, including SSR, TCAS, PRM and Multilateration systems. The requirements in §3.2.4.1.3 are to be met for each “Victim” within a Service Volume.

3.1.36 Will

When used in this specification, the word “will” provides information for a characteristic of a service function or of the entire service.

3.1.37 Type 1 Duplicate

A Type 1 Duplicate occurs when 2 distinct tracks are detected via 1090ES with the same 24-bit address from the same radio channel receiver.

3.1.38 Type 2 Duplicate

A Type 2 Duplicate occurs when 2 distinct tracks are detected via 1090ES with the same 24-bit address from different radio channel receivers

3.1.39 Composite Traffic Volume

A Composite Traffic Volume is the aggregation of reports from multiple Service Volumes with reports additionally filtered spatially according to a specified polygon and filtered to eliminate radio station duplicates.

3.2 Functional Requirements

The ADS-B/ADS-R Service functional requirements are presented in the following sections. The requirements are organized by function as shown in Figure 1-2.

3.2.1 ADS-B Message Receive and Decode

The ADS-B Message Receive and Decode Function receives ADS-B Messages, in the form of RF signals transmitted by UAT and 1090ES equipped Aircraft/Vehicles, and decodes the information contained in the signals to recover the ADS-B Message information.

3.2.1.1 1090ES

The ADS-B Message Receive and Decode Function will receive and decode V0, V1, and V2 1090ES ADS-B Messages per RTCA/DO-260B. 1090ES equipped aircraft/vehicles in conformance with RTCA DO-260B are required to broadcast MOPS Version TWO ADS-B Messages. Version ZERO and Version ONE ADS-B Message formats are contained in RTCA DO-260B Appendix N. The function is also required to send reports to the SBS Monitor for of aircraft equipped with MOPS Versions ZERO or ONE that are present in the NAS.

a. Reserved

Note: Above requirement deleted (reference FAA contracts letter ADS-B 0007dated November 5 2007)

b. The ADS-B Service shall [3533] process only ADS-B Messages received on the 1090ES link that have DF=17, DF=18 with CF Field EQUAL to 0 or 1 and DF=19 with AF=0.

Notes:

1. ADS-B reports are to be generated based only on reception of ADS-B Messages, as opposed to reception of TIS-B or ADS-R transmissions from a ground station.

2. The Downlink Format (DF), the "CF", and "AF" Fields are defined in DO-260B.

c. The ADS-B Service shall [1158] receive and decode the following 1090ES ADS-B Messages.

1. Version 1 (ONE) and Version 2 (TWO) Messages as defined in DO-260B:

• Airborne Position Messages,

• Airborne Velocity Messages (Subtypes 1 and 2),

• Aircraft Identification and Category Messages,

• Surface Position Messages,

• Operational Status Messages,

• Extended Squitter Aircraft Status Messages (Emergency/Priority) (Type=28, Subtype=1)

• Target State & Status Messages, and

• Test Messages (Type=23, Subtype=7)

Note: Test Messages do not apply to 1090 ES V2

2. Version 0 (ZERO) Messages as defined in DO-260B Appendix N

• Airborne Position Messages,

• Airborne Velocity Messages (Subtypes 1 and 2),

• Aircraft Identification and Category Messages,

• Surface Position Messages

• Operational Status Messages,

• Extended Squitter Aircraft Status Messages (Emergency/Priority), and

• Test Messages (Type=23, Subtype=7)

d. The ADS-B Service shall [4122 ] receive and decode the following 1090ES ADS-B Messages.

• Extended Squitter Aircraft Status Messages (TCAS/ACAS RA) (Type=28, Subtype=2)

Note: For guidance relating to the requirement to receive and decode the Aircraft Status Messages for Type=28 and Subtype 2, see SDP IRD.

e. The ADS-B Service shall [3040] declare a Time of Message Receipt (TOMR) and Time of Applicability (TOA) for each ADS-B Message received that could result in the generation of an ADS-B Report.

f. TOMR of a 1090ES ADS-B Message shall [3629] be measured relative to the arrival of the leading edge of the first preamble pulse of the amplitude modulated Mode S waveform conveying the 1090ES ADS-B Message.

g. Time measurement shall [3630] have a resolution of 100 nanoseconds or less, and an absolute accuracy relative to UTC of ±500 nanoseconds or less.

Note: Independent Validation processing (see §3.2.2.2 and §3.3.2.2.4) may lead to the need for a more accurate time measurement.

h. For the uncoupled case (T-bit=0), the TOA for each received 1090ES ADS-B Message shall [3631] be determined by rounding the TOMR off to the nearest 1/128th second UTC value.

i. For the coupled case (T-bit=1), the TOA for each received 1090ES ADS-B Message shall [3632] be the nearest applicable even or odd 200 ms UTC epoch determined by the F-bit.

Note: See Section2.2.8.1.4.2.2 of RTCA DO-260B for definition of the T-bit and F-bit and for definition of the even and odd 200 ms epoch

3.2.1.2 UAT

a. The ADS-B Service shall [211] receive and decode ADS-B Messages received over the UAT link per the Message formats described in Section §2.2.3.1 of RTCA DO- 282B.

b. The ADS-B Service shall [1159] receive and decode each of the ADS-B Message Payload Types identified in DO-282B.

Note: This includes Message Payloads from both Version 1 and Version 2 systems.

Appendix R of DO-282B indicates the changes in the message payload relative to that of Version 1. Most of the changes are new bit fields that were formerly “reserved”. One exception is the change in interpretation of the “SIL” field as indicated in the appendix.

c. The ADS-B Service shall [3672] process only ADS-B Messages received on the UAT link with ADDRESS QUALIFIER field NOT EQUAL to 2 or 3.

Notes:

1. ADS-B reports are to be generated based only on reception of ADS-B Messages, as opposed to reception of TIS-B or ADS-R transmissions from a ground station.

2. The ADDRESS QUALIFIER field is defined in DO-282B. Values of 2 and 3 indicate TIS-B targets.

d. TOMR of a UAT ADS-B Message shall [2759] be measured relative to the arrival of the optimum sample point of the first bit of the UAT synchronization sequence.

Notes:

1. See Sections §2.2.2.3 and §2.2.6.2.2 of RTCA/DO-282B.

2. The optimum sample point is the nominal center of the bit period.

e. Time measurement shall [2762] have a resolution of 100 nanoseconds or less, and an absolute accuracy relative to UTC of ±500 nanoseconds or less.

Note: Independent Validation processing (see §3.2.2.2 and §3.3.2.2.4) may lead to the need for a more accurate time measurement.

f. The ADS-B Service shall [213] determine the TOA for each ADS-B Message received on the UAT link based on the Time of Message Receipt (TOMR) as follows:

1. If the ADS-B Message payload indicates “UTC Coupled” and the Non-Precision Condition, the TOA is the start of the 1-second UTC epoch containing the

TOMR.

2. If the ADS-B Message payload indicates “UTC Coupled” and the Precision Condition, the TOA is the start of the 0.2-second UTC epoch containing the

TOMR.

1. The precision condition is in effect when: 1) the NACP value is 10 or 11; or

2) the NIC value is 9, 10, or 11. Otherwise the non-precision condition is in effect.

2. The receiver function can assign a TOA that can be 200 ms too late when a very late MSO in the 200 ms epoch is selected and there is 40 NM or more propagation delay

3. If the ADS-B Message payload indicates “Non-UTC Coupled,” the TOA is the TOMR minus 1 second.

Note: This condition is a degraded mode for UAT avionics. When an aircraft is in the non-UTC coupled condition, the receiving system cannot accurately recreate the transmitter’s TOA for its reported position. The TOA assumed here is an average of possible TOA values, in which data can be as old as 2 seconds from the TOMR. It is not expected that critical applications will use this data in this case.

3.2.2 Processing and Report Distribution

3.2.2.1 Message to Report Conversion

The information conveyed in ADS-B Messages on the UAT and 1090ES links is comparable and is used to populate ADS-B Reports that indicate the link over which the information was received, but otherwise contain very similar information. However, there are substantial differences in the characteristics of the two links, including the message rates and the content of the individual ADS-B Messages that are used in constructing the ADS-B Reports. The conversion of ADS-B Messages to ADS-B Reports on the 1090ES and UAT links is discussed in §3.2.2.1.1 and §3.2.2.1.2, respectively.

3.2.2.1.1 1090ES Squitter Processing

1090ES equipped aircraft/vehicles convey information in multiple types of ADS-B Messages. The information received in some Messages is to be stored for inclusion in future ADS-B Reports. ADS-B Reports are triggered by the reception of an ADS-B Message containing Position information or indication of an emergency condition.

3.2.2.1.1.1 Input Message Reception and Processing

3.2.2.1.1.1.1 Message Format Version Determination

1090ES ADS-B Messages comply with 1090ES Message Formats, Version Number ZERO (0) Version Number ONE (1) or Version Number TWO (2).. The ADS-B Service has to be able to identify the Version Number associated with the transmitting equipment to properly decode the ADS-B Messages.

a. The ADS-B Service shall [3058] consider the Version Number associated with a particular aircraft/vehicle to be Version Number ZERO (0) until an Operational Status Message is received.

b. The ADS-B Service shall [3648] identify ADS-B Messages received from a particular aircraft/vehicle with the Version Number contained in the Operational Status…