Attachment 5 - SBS Essential Services System Specification_FAA-E-3006 Rev. B dated 8-23-2019.pdf

FAA-E-3006, Rev. B/ 8/23/2019 i

REVISION RECORD

Revision

Date Description Approval

Rev.- 5/1/2010 NCP 32248/ATO0E-SBS-1001 NAS CCB

Rev. A 1/7/2015 NCP 35575/JM232-SBS-1005 Surveillance CCB

Rev. B 8/23/2019 NCP 37766/M4200-SBS-1001 Surveillance CCB ii

Table of Contents

1 INTRODUCTION

1.1 BACKGROUND

1.2 PURPOSE

1.3 SCOPE

1.4 SERVICE DESCRIPTION

1.4.1 FUNCTIONAL OVERVIEW

1.4.1.1 Broadcast Services Processing

1.4.1.2 Link Specific Processing

1.4.1.3 Maintenance Processing

1.4.2 EXTERNAL INTERFACES

1.4.2.1 Aircraft/Vehicle

1.4.2.2 Ground-Based Surveillance Systems

1.4.2.3 Meteorological and Aeronautical Information Systems

1.4.2.4 SBS Monitor and Authorized Users

1.4.3 INTER-OPERABILITY BETWEEN ADS-B/ADS-R AND TIS-B/FIS-B SERVICES

1.5 DOCUMENT OVERVIEW

2 APPLICABLE DOCUMENTS

2.1 GENERAL DOCUMENTS

2.1.1 FAA DOCUMENTS

2.1.2 MILITARY DOCUMENTS

2.1.3 NTIA DOCUMENTS

2.1.4 RTCA AND ICAO INDUSTRY STANDARDS

2.1.5 REFERENCE AND GUIDANCE MATERIAL

2.2 MAINTENANCE DOCUMENTS

2.3 INTERFACE DOCUMENTS

2.3.1 INTERFACE REQUIREMENTS DOCUMENTS

2.3.2 FAA INTERFACE CONTROL DOCUMENTS

2.4 DOCUMENTATION SOURCES

2.4.1 FAA DOCUMENTS

2.4.2 MILITARY AND FEDERAL DOCUMENTS

2.4.3 NATIONAL TELECOMMUNICATIONS AND INFORMATION ADMINISTRATION DOCUMENTS

2.4.4 RTCA, INC. DOCUMENTS

2.4.5 ICAO DOCUMENTS

3 REQUIREMENTS

3.1 DEFINITIONS

3.1.1 ACCELERATED FLIGHT

3.1.2 ACCESS CONTROL MECHANISMS

3.1.3 ADS-B MESSAGE

3.1.4 ADS-B REPORT

3.1.5 APPLICATION PROTOCOL DATA UNIT (APDU)

3.1.6 CLIENT

3.1.7 CLUTTER TRACK

3.1.8 COVERAGE VOLUME

iii

3.1.9 DOMAIN

3.1.10 DUAL TRACK

3.1.11 FIS-B SERVICE LATENCY

3.1.12 FIS-B SOURCE DATA APPROVAL

3.1.13 FIS-B MESSAGE

3.1.14 FIS-B SERVICE

3.1.15 PARROT

3.1.16 PRODUCT TRANSMISSION INTERVAL

3.1.17 SBS MONITOR

3.1.18 SENSOR DATA

3.1.19 SERVICE AVAILABILITY

3.1.20 SERVICE DELIVERY POINT

3.1.21 SERVICE STATUS REPORT

3.1.22 SERVICE VOLUME

3.1.23 SPLIT TRACK

3.1.24 SWAP TRACK

3.1.25 STEADY STATE FLIGHT

3.1.26 SURVEILLANCE COVERAGE VOLUME

3.1.27 SHALL

3.1.28 SHOULD

3.1.29 STATE VECTOR

3.1.30 TIME OF APPLICABILITY

3.1.31 TIS-B LATENCY

3.1.32 TIS-B MESSAGE

3.1.33 TIS-B SERVICE

3.1.34 TRANSMISSION DUTY CYCLE

3.1.35 TRANSMISSION RATE

3.1.36 UAT APPLICATION DATA FIELD

3.1.37 UAT INFORMATION FRAME

3.1.38 UAT MESSAGE PAYLOAD

3.1.39 UAT OPTIMUM SAMPLE POINT

3.1.40 UPDATE INTERVAL

3.1.41 UPLINK BROADCAST SERVICE

3.1.42 WILL

3.2 FUNCTIONAL REQUIREMENTS

3.2.1 BROADCAST SERVICES PROCESSING

3.2.1.1 TIS-B Service

3.2.1.1.1 TIS-B Surveillance Processing

3.2.1.1.1.1 Surveillance Sources

3.2.1.1.1.2 Target Tracking

3.2.1.1.1.3 Target Address and Address Qualifier

3.2.1.1.1.4 Target State Vector

3.2.1.1.1.4.1 Horizontal Position

3.2.1.1.1.4.2 Pressure Altitude

3.2.1.1.1.4.3 Horizontal Velocity

3.2.1.1.1.4.4 Vertical Rate

3.2.1.1.1.4.5 Direction – Ground Track

3.2.1.1.1.5 Target Air/Ground State

3.2.1.1.2 TIS-B Target Suppression

3.2.1.1.2.1 TIS-B Suppression for Surface Service Volumes

3.2.1.1.3 TIS-B / ADS-R Service Status

3.2.1.1.4 TIS-B Target Report Generation

3.2.1.1.5 TIS-B Processing Specific to DO-260 and DO-260A Equipped Aircraft

3.2.1.2 FIS-B

iv

3.2.1.2.1 Meteorological and Aeronautical Information Sources

3.2.1.2.2 FIS-B Service Management

3.2.1.2.3 Basic Meteorological Products

3.2.1.2.4 Basic Aeronautical Information Products

3.2.1.2.5 Optional FIS-B Products

3.2.1.2.6 FIS-B Product Characteristics

3.2.1.2.6.1 AIRMET

3.2.1.2.6.2 METAR/SPECI

3.2.1.2.6.3 MRMS NEXRAD Precipitation Reflectivity (CONUS and Regional)

3.2.1.2.6.4 NOTAM-D/FDC (includes Temporary Flight Restrictions [TFRs], TRAs, TMOAs)

3.2.1.2.6.5 PIREP

3.2.1.2.6.6 SIGMET (including Convective SIGMET)

3.2.1.2.6.7 SUA

3.2.1.2.6.8 TAF/AMEND

3.2.1.2.6.9 TIS-B / ADS-R Service Status for the UAT data link

3.2.1.2.6.10 Winds and Temperatures Aloft

3.2.1.2.6.11 Graphical AIRMET (G-AIRMET)

3.2.1.2.6.12 Center Weather Advisories (CWA)

3.2.1.2.6.13 Lightning

3.2.1.2.6.14 Turbulence

3.2.1.2.6.15 Icing, Forecast Potential (FIP)

3.2.1.2.6.16 Cloud Tops

3.2.1.3 FIS-B Product Report Generation

3.2.1.4 Current Report List

3.2.1.5 Truncation of Text Records

3.2.2 LINK SPECIFIC PROCESSING

3.2.2.1 1090ES

3.2.2.1.1 1090ES ADS-B Message Receive

3.2.2.1.2 1090ES TIS-B Message Generation

3.2.2.1.2.1 1090ES TIS-B Message Data

3.2.2.1.2.2 1090ES Address/Parity Generation

3.2.2.1.3 1090ES TIS-B Message Format

3.2.2.1.3.1 1090ES TIS-B Message Types

3.2.2.1.3.2 1090ES TIS-B Message Encoding

3.2.2.1.3.3 1090ES TIS-B Message Payload

3.2.2.1.4 1090ES Media Access

3.2.2.2 UAT

3.2.2.2.1 UAT ADS-B Message Receive

3.2.2.2.2 UAT TIS-B Message Generation

3.2.2.2.3 UAT FIS-B Message Generation

3.2.2.2.3.1 UAT-Specific Header

3.2.2.2.3.2 Application Data

3.2.2.2.4 UAT Media Access

3.2.2.2.4.1 Overview

3.2.2.2.4.2 Relationship of the MSO to the UAT Modulated Data

3.2.2.2.4.3 UAT TIS-B Messages

3.2.2.2.4.4 UAT Ground Uplink Messages (FIS-B)

3.2.2.2.4.4.1 Transmission Time Slots

3.2.2.2.4.4.2 Transmission Time Slot Rotation and “Data Channels”

3.2.2.2.4.4.3 Transmission of UAT Ground Uplink Message

3.2.2.2.5 UAT TIS-B / ADS-R Service Status Message

3.2.2.2.6 Transmit Status Reporting

3.2.2.2.6.1 TIS-B

3.2.2.2.6.2 FIS-B

v

3.2.3 MAINTENANCE PROCESSING

3.2.3.1 Maintenance Data Sets

3.2.3.1.1 Mode Reporting

3.2.3.1.2 Monitored Parameter State Reporting

3.2.3.1.3 Service Volume Message Counts

3.2.3.1.4 ADS-B Test Report

3.2.3.1.4.1 1090ES

3.2.3.1.4.2 UAT

3.2.3.1.5 Processing Requirements for Generating the CAT 033 ADS-B Test Report

3.2.3.1.6 Monitoring ADS-B Test Reports

3.3 PERFORMANCE REQUIREMENTS

3.3.1 GENERAL REQUIREMENTS

3.3.1.1 Expandability

3.3.1.2 System Timing

3.3.1.3 Service Ceiling

3.3.2 TIS-B SERVICE

3.3.2.1 Applications Supported

3.3.2.2 TIS-B Service Management

3.3.2.3 TIS-B Service Volume

3.3.2.4 TIS-B / ADS-R Service Status

3.3.2.5 TIS-B Service Capacity

3.3.2.6 TIS-B Service Latency

3.3.2.7 TIS-B Update Interval

3.3.2.8 TIS-B Information Integrity

3.3.2.9 TIS-B Service Availability

3.3.2.10 Broadcast Services Processing

3.3.2.10.1 TIS-B Track Initiation

3.3.2.10.2 TIS-B Track Accuracy

3.3.2.10.2.1 Horizontal Position

3.3.2.10.2.2 Horizontal Velocity

3.3.2.10.2.3 Heading/Ground Track

3.3.2.10.2.4 Vertical Position

3.3.2.10.2.5 Vertical Velocity

3.3.2.10.3 TIS-B Track Reliability

3.3.2.10.3.1 False Track Rate

3.3.2.10.3.2 Track Continuity Rate

3.3.2.10.3.3 Track Loss Rate

3.3.2.11 Link Specific Processing

3.3.2.11.1 Performance Environment

3.3.2.11.2 Traffic Density and Equipage Scenarios

3.3.2.11.3 ADS-B Update Interval

3.3.2.11.4 TIS-B Update Interval

3.3.2.11.5 TIS-B Extrapolation Accuracy

3.3.2.11.6 1090ES

3.3.2.11.6.1 1090ES Interference Environment

3.3.2.11.6.2 1090ES Transmit Function Characteristics

3.3.2.11.6.3 1090ES Transmit Duty Cycle Limitation

3.3.2.11.6.3.1 SSR Sidelobe Reception

3.3.2.11.6.3.2 SSR Main Beam Reception

3.3.2.11.6.3.3 Multilateration R/T Reception

3.3.2.11.7 UAT

3.3.2.11.7.1 UAT Transmit Function Characteristics

3.3.2.11.7.1.1 UAT Modulation Rate

3.3.2.11.7.1.2 UAT Modulation Distortion

vi

3.3.2.11.7.1.3 UAT Message Transmission Power

3.3.3 FIS-B SERVICE

3.3.3.1 FIS-B Service Capacity

3.3.3.2 FIS-B Service Latency

3.3.3.3 FIS-B Information Integrity

3.3.3.4 FIS-B Service Availability

3.3.3.5 Broadcast Services Processing

3.3.3.5.1 FIS-B Product Processing

3.3.3.6 Link Specific Processing

3.3.3.6.1 UAT

3.4 INTERFACE REQUIREMENTS

3.4.1 REPORTS FROM SURVEILLANCE SYSTEMS

3.4.2 REPORTS FROM MAINTENANCE PROCESSING

3.4.3 REPORTS FROM BROADCAST SERVICE PROCESSING

3.4.4 UAT INFORMATION FRAMES (AVIONICS)

3.4.4.1 UAT Length Field

3.4.4.2 UAT Reserved Field

3.4.4.3 UAT Frame Type Field

3.4.4.4 UAT Frame Data Field

3.4.4.5 FIS Product Encoding (APDUs)

3.4.4.5.1 APDU Header

3.4.4.5.2 UAT FIS-B Basic Products Formats

3.4.4.5.2.1 Textual Products Formats

3.4.4.5.2.2 Graphical Products Formats

3.4.4.5.2.3 Text/Graphical Overlay Formats

3.4.4.6 UAT TIS-B / ADS-R Service Status Message

3.5 SECURITY REQUIREMENTS

3.5.1 GENERAL REQUIREMENTS

4 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

vii

5 GLOSSARY

APPENDIX A TIS-B PERFORMANCE SCENARIOS

A.1 ACCURACY REQUIREMENT VERIFICATION SCENARIOS FOR POSITION, HEADING AND SPEED 95

A.1.1 SCENARIOS FOR POSITION, HEADING, SPEED ACCURACY PERFORMANCE VERIFICATION

A.2 ACCURACY REQUIREMENTS FOR ALTITUDE AND ALTITUDE VELOCITY

A.2.1 SCENARIOS FOR ALTITUDE AND ALTITUDE VELOCITY ACCURACY PERFORMANCE VERIFICATION

A.3 TRACK RELIABILITY

A.3.1 TRACK SWAP REQUIREMENTS

A.4 TRACK LOSS SCENARIO

A.5 REFERENCES FOR THIS APPENDIX

APPENDIX B CURRENT REPORT LIST

B.1 CURRENT REPORT LIST

B.1.1 CRL HEADER AND PAYLOAD ENCODING

B.1.1.1 Product ID

B.1.1.2 TFR

B.1.1.3 Reserved B.1.1.4 LID Flag B.1.1.5 Product range B.1.1.6 Location ID B.1.1.7 Number of CRL Items Listed B.1.1.8 OF Flag B.1.1.9 Reserved Bit B.1.1.10 Report Month or Year B.1.1.11 Text B.1.1.12 Graphic B.1.1.13 Report Number

APPENDIX C TEXT RECORD TRUNCATION

C.1 TRUNCATION OF LONG TEXT RECORDS

C.1.1 BACKGROUND

C.1.2 SOLUTION

C.1.3 ALGORITHM DESCRIPTION OF TRUNCATION

viii

List of Figures

Figure 1-1. Surveillance and Broadcast Services Partitioning Figure 1-2. Broadcast Services Functional Overview Figure 3-1. UAT Frame Figure 3-2. Relationship of “Data Channel Numbers” to Transmission Time Slot Numbers Figure 3-3. Mode S Reply Rate Distributions for Ground Receiver Figure 3-4. ATCRBS Reply Rate Distributions for Ground Receiver Figure 3-5. Mode S Reply Rate Distributions for Airborne Receiver Figure 3-6. ATCRBS Reply Rate Distributions for Airborne Receiver Figure 3-7. 1090ES Duty Cycle Limitations for Transmitters Within RLOS of an SSR Unit –

Sidelobe Reception Figure 3-8. 1090ES Duty Cycle Limitations for Transmitters Within RLOS of an SSR Unit – Main

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

Unit Figure 3-10. UAT Information Frame Figure 3-11. UAT TIS-B / ADS-R Service Status Format Figure A-1. Configuration of Three Long Range Sensors Figure A-2. Configuration of Two Short Range Sensors and One Long Range Sensor Figure A-3. Scenario for Configuration with Two Short Range Sensors and One Long Range Sensor

Figure A-4. Scenario for Configuration with Three Long Range Sensors Figure A-5. Radial and Tangential Flight Paths for Computing Single Sensor Accuracies for the

Short-Range Radar Figure A-6. Radial and Tangential Flight Paths for Computing Single Sensor Accuracies for the

Long Range Radar Figure A-7. Multi-Sensor Scenarios for Computing Turning, Tangential and Linearly Accelerating

Accuracies for the Short-Range Radar Configuration Figure A-8. Multi-Sensor Scenarios for Computing Turning, Tangential, Radial and Linearly

Accelerating Accuracies for the Long-Range Radar Configuration Figure A-9. Radar Locations for Altitude and Altitude Velocity Scenarios Figure A-10. Head-On Approach Scenario Figure A-11. 100 kt Overtake Scenario Figure A-12. 30° Crossing Scenario Figure B-1. Current Report List Frame Figure B-2. Current Report List Encoding ix

List of Tables

Table 3-1: 1090ES TIS-B Message Types Table 3-2. Payload Composition of 1090ES TIS-B Messages Table 3-3. Payload Composition of UAT TIS-B Message Table 3-4. Transmission Time Slot Definition for the UAT Ground Segment Table 3-5. Maintenance Data Sets Table 3-6. Payload Composition of 1090ES ADS-B Test Message Table 3-7. Payload Composition of UAT ADS-B Test Message Table 3-8. Test Message Mapping to CAT 033 ADS-B Report Table 3-9. Requirements for Track Accuracy Table 3-10. Track Swap Requirements Table 3-11. Traffic Density Environments Table 3-12. FIS Product Update and Transmission Intervals Table 3-13. UAT Frame Types Table A-1. Sensor Characteristics for Test Scenarios x

This Page Intentionally Left Blank.

1 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:

1. Automatic Dependent Surveillance-Broadcast (ADS-B),

2. Automatic Dependent Surveillance-Rebroadcast (ADS-R),

3. Traffic Information Service-Broadcast (TIS-B), and

4. 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 designed to the “Critical” level. However, that Service may, at the Government’s option, 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. ADS- B downlink information will be captured as part of providing the TIS-B Service and that information will also be made available to authorized airspace users.

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 Service Status Reports to authorized user systems and the SBS

Monitor, via SDPs. The Critical level Services will provide ADS-B and Critical 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 must comply with FAA Order 1200.22c, 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. Inter-operability between the Services provided in conformance with these two specifications is addressed in §1.4.3. Each Service is described in the following paragraphs.

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.

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 comprehensive air and airport surface picture. The ADS-R Service will eventually be provided at a level sufficient to support specified critical applications.

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 comprehensive air and airport surface picture of traffic in their vicinity. The TIS-B Service will support only essential level applications.

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, NOTAMs, pilot reports (PIREPS), and other similar meteorological and aeronautical information. FIS-B products, from both government and/or 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 using spare bits within the current

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

1.2 Purpose

This document is to be used in the procurement of TIS-B and FIS-B (TIS-B/FIS-B) Services from a commercial service provider per the requirements in this document.

1.3 Scope

This essential services specification details the requirements for TIS-B and FIS-B Services the FAA will acquire under the Surveillance and Broadcast Services Program. The required functionality of the Services as well as the performance that must be provided is included herein. The external interfaces that the Services must provide are also specified.

1.4 Service Description

TIS-B/FIS-B 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 ADS-B/ADS-R Services, the two will be transmitting in the same coverage volume.

Section 1.4.3 discusses the related implications.

1.4.1 Functional Overview

The TIS-B/FIS-B Services will provide the NAS with real-time traffic, meteorological and

NAS status information. The services should also support the overall NAS mission to provide users with a safe and economical mode of operation.

The functional requirements specified herein are grouped by the following three functions:

Broadcast Services Processing

Link Specific Processing

Maintenance Processing

The functional grouping is not meant to imply a system architecture, but is used only to organize requirements and increase the document readability. Any solution which provides equivalent functionality will be considered compliant.

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. Broadcast Services Functional Overview

1.4.1.1 Broadcast Services Processing

Broadcast Services Processing comprises the application data processing necessary to generate TIS-B target data and FIS-B products for broadcast to aircraft/vehicles. Broadcast

Services Processing receives sensor data from ground-base surveillance and ADS-B systems and generates TIS-B target data for transmission as TIS-B Messages by Link- Specific Processing. Additionally, Broadcast Services Processing receives and processes weather and NAS status data from external sources and generates applicable FIS-B products for transmission as FIS-B Messages by Link-Specific Processing.

1.4.1.2 Link Specific Processing

Link-Specific Processing comprises the ground-based transmit and receive functionality.

Link-Specific Processing transmits TIS-B and FIS-B Messages as directed by the Broadcast Services Processing.

Link Specific Processing also receives ADS-B Messages from equipped aircraft/vehicles.

The receive functionality decodes the messages and provides the ADS-B sensor data to the

Broadcast Services Processing for use by the TIS-B Service.

1.4.1.3 Maintenance Processing

Maintenance Processing includes, but is not limited to, providing status on transmit/receive equipment and services to the FAA. The Maintenance Processing also includes the statistics on the quality of the data within the Service Volume.

1.4.2 External Interfaces

The TIS-B/FIS-B Services provides interfaces to the following external systems:

Aircraft and Surface Vehicles (Aircraft/Vehicle), Ground-Based Surveillance Systems, Meteorological and Aeronautical Information Systems, SBS Monitoring System, Authorized Users.

Detailed interface requirements between these systems are contained in Interface

Requirements Documents referenced in §3.4.

1.4.2.1 Aircraft/Vehicle

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 for the Aircraft/Vehicle interface.

The TIS-B Service receives ADS-B Messages on the UAT and 1090ES links from Aircraft and Surface Vehicles to support the tracking of targets and filtering of TIS-B data to be broadcast. The Receive Function 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. 282B260BTo meet specified Service Volume requirements, a network of ground sites (i.e., implementations of the ADS-B Message

Receive Function) may be required to receive and decode the transmitted ADS-B Messages from the ADS-B equipped aircraft/vehicles.

1.4.2.2 Ground-Based Surveillance Systems

Ground based surveillance systems, as referred to in this document, represent FAA and

Department of Defense (DOD) radar systems and FAA multilateration systems. These systems provide sensor data to the TIS-B Service. There are a variety of surveillance systems and their interfaces are equally as varied. The TIS-B Service uses only digital/digitized sensor data from these surveillance systems. The Service Provider may elect to digitize the analog data from surveillance sensors not providing a native digital output. The FAA will establish one or more SDPs to provide the sensor data to the service provider.

1.4.2.3 Meteorological and Aeronautical Information Systems

The raw data used by the FIS-B Service to generate products suitable for aeronautical users is obtained from meteorological and Aeronautical Information Systems (AIS). There are numerous sources of this data within the government and from commercial value-added suppliers that the FIS-B service provider may consider using. Meteorological data includes measured weather and atmospheric conditions. AIS data consists mainly of the status of

National Airspace System (NAS) resources used by aircraft and airport surface vehicles.

Notices to Airmen (NOTAMs) convey a large portion of AIS data, but there are other system status data, such as airport or airspace demand/capacity, that may be useful to aircraft operators.

1.4.2.4 SBS Monitor and Authorized Users

The SBS Monitor and authorized users are external recipients of TIS-B and FIS-B Reports and the Service Status Reports generated by the TIS-B/FIS-B Services. The SBS Monitor supports the FAA’s responsibility to assure the services are provided with the expected quality and availability. Authorized users represent other government or commercial organization that the FAA has designated as necessary recipients of certain data sets.

Additionally, the service provider may elect to provide some of these data sets to other entities, but these arrangements must be first approved by the FAA.

1.4.3 Inter-operability Between ADS-B/ADS-R and TIS-B/FIS-B Services

Any required spectrum coordination across the network of 1090ES and UAT transmitters will be accomplished procedurally through adaptation of the individual transmitters. The requirements necessary to achieve this adaptability are included in this specification.

1.5 Document Overview

The reference documents that are applicable to this specification are in §0. The functional and service performance requirements for the TIS-B/FIS-B Services are in §3. Section 0 contains the quality assurance information. A glossary of acronyms can be found in §5.

Appendix A contains traffic scenarios specifically tailored to the TIS-B track accuracy and reliability performance requirements in §3.3.2.10.

2 APPLICABLE DOCUMENTS

2.1 General 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 take precedence.

2.1.1 FAA Documents

SBS fPR Final Program Requirements for Surveillance and

Broadcast Services, Version 2.1, FAA, August 6, 2007

FAA-E-3011 Automatic Dependent Surveillance-Broadcast (ADS- B) / ADS-B Rebroadcast (ADS-R) Critical Services

Specification, Version 2.8 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.

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)

AC 00-62 U.S. Department of Transportation, Federal Aviation

Administration, Advisory Circular, Internet Communications of Aviation Weather and NOTAMs, November 1, 2002

AC 00-45E U.S. Department of Transportation, Federal Aviation

Administration, Advisory Circular, Aviation Weather Services, December 1, 1999

FAA Order 8100.1 U.S. Department of Transportation, Federal Aviation

Administration, Order, Air Transportation Operations

Inspector’s Handbook, Volume 3.

2.1.2 Military Documents

MIL-STD-810F

Department of Defense Test Method Standard for

Environmental Engineering Considerations and Laboratory Tests, Version F, US DoD, January 1, 2000

2.1.3 NTIA Documents

NTIA Manual Manual of Regulations and Procedures for Federal Radio Frequency Management, May 3003 Edition with

January 2006 Revisions

2.1.4 RTCA and ICAO Industry Standards

DO-181C

Minimum Operational Performance Standards for Air Traffic Control Radar Beacon System/Mode Select

(ATCRBS/Mode S) Airborne Equipment, Revision C, RTCA, Inc.

DO-242A, Change 1

Minimum Aviation System Performance Standards for

Automatic Dependent Surveillance Broadcast (ADS-B), Revision A, RTCA, Inc.

Note: Any reference to RTCA/DO-242A in this specification must be interpreted as including Change 1.

DO-260B

Minimum Operational Performance Standards for 1090

MHz Extended Squitter Automatic Dependent Surveillance-Broadcast (ADS-B) and Traffic

Information Services-Broadcast (TIS-B), Revision B, RTCA, Inc.

260B

DO-267A

Minimum Aviation Systems Performance Standards

(MASPS) for Flight Information Services-Broadcast

(FIS-B) Data Link, RTCA, Inc.

DO-282B

Minimum Operational Performance Standards for

Universal Access Transceiver (UAT), Automatic

Dependent Surveillance-Broadcast (ADS-B), Revision

B, RTCA, Inc.

282B

DO-286A

Minimum Aviation Systems Performance Standards

(MASPS) for Traffic Information Services-Broadcast

(TIS-B), Revision A, RTCA, Inc.

DO-317 Minimum Operational Performance Standards for

Aircraft Surveillance Applications Systems (ASAS), April 14, 2009, RTCA Inc.

DO-358

Minimum Operational Performance Standards for Flight Information Services-Broadcast (FIS-B), RTCA, Inc.

DO-358A DRAFT MOPS for FIS-B Rev A, RTCA, Inc.

ICAO Annex 10 To the Convention on International Civil Aviation

UAT and Mode S Extended Squitter Standards and Recommended Practices (SARPs)

ICAO Annex 3 To the Convention on International Civil Aviation

Meteorological Services

ICAO Annex 15 To the Convention on International Civil Aviation

Aeronautical Information Services

2.1.5 Reference and Guidance Material

Bourgeois, R., F. Castella, “System Integrity and Track Accuracy Methodology for Traffic Information Service – Broadcast (TIS-B),” The Johns Hopkins University Applied Physics Laboratory, 2004.

Chamlou, R., “TIS-B: Calculation of Navigation Accuracy Category for Position and

Velocity Parameters,” The MITRE Corporation, April 2004.

Strain, R., R. Chamlou, J. Giovino, “Operational and Functional Requirements for the Broadcast Services System Implementation,” MP03W0000139R3, The MITRE

Corporation, June 2006.

“Broadcast Services Ground Station Detailed Requirements Specification using the

Universal Access Transceiver (UAT) and the 1090 MHz Extended Squitter (1090ES) ADS-B Data Links, Draft version 2.5,” FAA, 2005.

2.2 Maintenance Documents

FAA Order 6000.15D U.S. Department of Transportation, Federal Aviation Administration, Order, General Maintenance Handbook for NAS Facilities, July 23,2004

FAA Order 1100.157A

U.S. Department of Transportation, Federal Aviation

Administration, Order, National Systems Engineering Divisions Maintenance Program Procedures, Operational Support, June 8, 1995

FAA Order 6032.1B U.S. Department of Transportation, Federal Aviation Administration, Order, NAS Modification Program, September 18, 2002

FAA Order 7210.3T

U.S. Department of Transportation, Federal Aviation

Administration, Order, Facility Operation and Administration, February 19, 2004

2.3 Interface Documents

2.3.1 Interface Requirements Documents

NAS-IR-82320001

Interface Requirements Document – En Route

Communications Gateway (ECG)/Internet Protocol

Local Area Network (IP LAN) User System, February

7, 2003

SUR.ET1.ST05.2000-STD-

07-01

Eurocontrol Standard Document for Surveillance Data

Exchange, Part 7: Category 010, Transmission of

Monosensor Surface Movement Data, April 2005

SUR.ET1.ST05.2000-STD-

08-01

Eurocontrol Standard Document for Surveillance Data Exchange, Part 8: Category 011, Transmission of A-

SMGCS Data, April 2005

NAS-IR-82530001

Surveillance and Broadcast Services (SBS) Service

Delivery Point (SDP) to ATC Automation and Service Monitoring User Subsystems Interface Requirements

Document (IRD) Version 3.3.2 dated December 23, 2010.

2.3.2 FAA Interface Control Documents

NAS-IC-82320001-01

Interface Control Document – En Route

Communications Gateway (ECG)/Internet Protocol (IP)

Local Area Network (LAN) User System, July 30, 2003

ATCBI-6-SE13-002

Air Traffic Control Beacon Interrogator Replacement

(ATCBI-6) Interface Control Document for the NAS

Automation Systems Interface, Issue 3, 19 June 2006.

Note: The ATCBI-6 ICD applies to all en route radar feeds, including Mode S en route, ATCBI-6 (ARSR-1, ARSR-2, ARSR-3, FPS, Beacon Only), and ATCBI-6M (ARSR-4) facilities.

NAS-IC-34032105

Interface Control Document - Airport Surveillance

Radar Model 9 (ASR-9) /Standard Terminal Automation

Replacement System (STARS), 14 June 2001.

A008-001-46 Interface Control Document [ASR-11] – Surveillance

Data Translator (SDT) to ARTS-IIE (modified CD-2)

A008-007 Interface Control Document [ASR-11] – System

Interface Unit (SIU) to ARTS-IIIE with Radar Gateways

NAS-IC-34180001, Rev H Airport Surface Detection Equipment Model – X (ASDE-X) Data Distribution (DD) To End Users ICD, January 11, 2010

NAS-IC-34180001, Rev H

Change Pages

Airport Surface Detection Equipment Model – X (ASDE-X) Data Distribution (DD) To End Users ICD

Change Pages, June 21, 2012

2.4 Documentation Sources

2.4.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.4.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 a.m. to 4:30 p.m. (EST).

2.4.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.4.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 .

2.4.5 ICAO Documents

Copies of documents that are published by the International Civil Aviation Organization (ICAO) may be obtained from the ICAO Document Sales Unit, 999 University Street, Montreal, Quebec, Canada H3C 5H7, or by calling (514) 954-8022, or by sending an email to sales@icao.int , or by visiting the “Publications” link on the ICAO web site at:

http://www.icao.int .

http://www.ntia.doc.gov/ http://www.rtca.org/ mailto:sales@icao.int http://www.icao.int/

3 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 TIS-B/FIS-B

Services.

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

If the FIS-B Service is provided on a link other than UAT, then the Service shall [E3229] meet all requirements with the exception of the UAT link specific requirements.

When a single data link is used in the Service design for the TIS-B Service, the functional, performance, and interface requirements associated with providing the Service on that data link shall [E3230] 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 Accelerated Flight

Accelerated flight as used in this specification means to be changing ground speed, turning, climbing or descending.

3.1.2 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.3 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.4 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 CAT033 Report format detailed in NAS-IR-SBS SDP.

3.1.5 Application Protocol Data Unit (APDU)

The APDU encapsulates FIS-B product data that is data linked from the FIS-B Service to the aircraft. The APDU, as specified in the FIS-B MOPS, RTCA DO-358, represents a standard format for communicating the information necessary for receiving applications to process, store and display FIS-B products.

3.1.6 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.7 Clutter Track

The sensor measurement for a target is far (i.e., >2 NM) from the true target position or the measurement is for non-existent targets. Primary radar is subject to ground reflections, road traffic, speckle or multipath that may cause clutter. Secondary radar is subject to multipath on interrogation/reply pulses resulting in beacon false targets or may cause beacon clutter.

3.1.8 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.9 Domain

For purposes of this specification, there are three service domains: (1) airport surface, (2) terminal airspace, and (3) en route/off-shore airspace.

3.1.10 Dual Track

Each sensor produces one measurement per target, but the tracker produces more than one track for the target. This is indicated by multiple track IDs for the target under consideration.

3.1.11 FIS-B Service Latency

The FIS-B Service latency is measured from the time a product’s source-data is received until the product is ready for transmission to the aircraft/vehicle.

3.1.12 FIS-B Source Data Approval

Approved aviation weather information means that aviation weather information provided by the National Weather Service (NWS), sources approved by the NWS, or those sources authorized for approval by the Administrator in FAA Order 8400.1, “Air Transportation

Operations Inspector’s Handbook,” Volume 3, Chapters 6 and 7.

3.1.13 FIS-B Message

The expression of FIS-B product data in a data link specific format for broadcast. The FIS- B Service will transmit products in the UAT data link Ground Uplink Message format specified in RTCA/DO-282B. The message formats for FIS-B products comply with RTCA DO-358 and specific product definitions and available in this document.

3.1.14 FIS-B Service

The FIS-B service provides NAS users with adequate, accurate, reliable and timely data on weather phenomina occuring in the NAS and non-control aeronautical information regarding the status of NAS systems and resources.

3.1.15 PARROT

A fixed point target that is output from surveillance sensors, such as radar or wide area multilateration, that is used to assess the health of the sensor.

3.1.16 Product Transmission Interval

The amount of time within which a new or updated product transmission must be completed or the rate at which a product is rebroadcast between updates from the source data provider.

3.1.17 SBS Monitor

The SBS Monitor is a system that will monitor the performance of Surveillance and Broadcast Services. To the TIS-B/FIS-B Services, the SBS Monitor will be a Service

Delivery Point.

3.1.18 Sensor Data

Sensor data is a term used in this specification to represent data from radars, multilateration systems and ADS-B systems used by the TIS-B Service to determine a target’s state vector.

Specifically, sensor data may include: radar plots, radar tracks, radar sector synchronization data, radar Real Time Quality Control (RTQC) data, ADS-B Reports, and multilateration plots and tracks. In contrast, sensor data doesn’t include maintenance or status data from these systems.

3.1.19 Service Availability

Service Availability is defined as:

DowntimeUptime

Uptime A

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.

Note: In accordance with the FAA contract (DTFAWA-07-C-00067, Section H.7); the service provider is not liable for outages arising from causes beyond the control and without fault or negligence of the service provider. Examples of such causes include, but are not limited to, (1) acts of God or of the public enemy, (2) acts of the Government (United States or other government entities where ADS-B is located) in either its sovereign or contractual capacity, (3) fires, (4) floods, (5) epidemics, (6) quarantine restrictions, (7) strikes, (8) freight embargos and (9) unusually severe weather and (10) unscheduled, unplanned, or emergency requirements from commercial tower operators to power down transmitters where advance notification is not possible. In each instance the outage must be beyond the control and without fault or negligence of the service provider. Furthermore, in relation to the above availability calculation, the service provider shall not be liable for planned outages for equipment maintenance, equipment upgrades, and software upgrades. However, the service provider is responsible for timely action related to all outages, regardless of cause, and will be liable for extended outages caused by inaction of the service provider.

3.1.20 Service Delivery Point

A Service Delivery Point (SDP) is the physical demarcation point between systems or services where specific information exchange takes place and where responsibility for the information transfers. Interface Requirements Documents and Interface Control Documents are used to specify the expectations and nature of the information exchanges, as well as protocols, formats and other related requirements.

3.1.21 Service Status Report

A periodic report containing equipment and service performance and system status information about the FIS-B/TIS-B Service provided by the Service Provider to the SBS

Monitor. The Service Status Report is provided in the CAT023 format detailed in NAS-

IR-SBS SDP.

3.1.22 Service Volume

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.

3.1.23 Split Track

The sensor produces more than one measurement per target. Primary radar can produce azimuth splits and range splits. Secondary radar can produce mis-columniations or aircraft transponder double-reply.

3.1.24 Swap Track

The identifying attributes for a target are incorrectly reported for that target. In the context of the TIS-B Service, these attributes may include: target address, 4096 identification code or track ID. The sensor may incorrectly report the 4096 identification code or ICAO address due to garble or de-interleaving problem, or the tracker may incorrectly associate attributes from one target to another target.

3.1.25 Steady State Flight

Steady state as it is used in this specification means constant speed, straight and level flight.

3.1.26 Surveillance Coverage Volume

The volume of airspace for which there is coverage from one or more non-ADS-B ground surveillance sensors.

3.1.27 Shall

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

3.1.28 Should

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

3.1.29 State Vector

A State Vector refers to an aircraft/vehicle horizontal and vertical position and horizontal and vertical velocity. When used in reference to the TIS-B Service, a target’s state vector is an estimate of position and velocity resulting from a tracking process.

3.1.30 Time of Applicability

The Time of Applicability for ADS-B, ADS-R and TIS-B reports is the time at which the reported values were valid.

3.1.31 TIS-B Latency

TIS-B latency is the difference between the time of measurement of the source position data and the time of transmission of the TIS-B Message.

3.1.32 TIS-B Message

The expression of TIS-B target information in a data link specific format for broadcast.

The TIS-B Service will use the UAT and 1090ES data link message formats specified in

RTCA/DO-282B and RTCA/DO-260B, respectively.

3.1.33 TIS-B Service

The TIS-B Service provides users equipped with an ADS-B system the ability to receive, process, and display state information on proximate traffic that cannot be adequately obtained air-to-air via ADS-B, but that can be tracked by alternative, ground-based surveillance systems.

3.1.34 Transmission Duty Cycle

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

3.1.35 Transmission Rate

The number of message transmissions per unit of time as measured at the antenna.

3.1.36 UAT Application Data Field

The 424 byte, fixed-length content of an UAT Ground Uplink Message composed of one or more Information Frames. For the purposes of this specification, the Application Data field will consist of FIS-B products and TIS-B / ADS-R Service Status data; however, other uses are possible.

3.1.37 UAT Information Frame

Application Data subframes enabling various data content to be transported within each UAT Ground Uplink Message. For the purposes of this specification, the UAT Information

Frame types include APDUs and TIS-B / ADS-R Service Status; however, other types are possible.

3.1.38 UAT Message Payload

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

3.1.39 UAT Optimum Sample Point

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

3.1.40 Update Interval

The time between the successful reception of reports / messages as measured at the receiving end-system.

3.1.41 Uplink Broadcast Service

Uplink Broadcast Service refers to the entire scope of services defined in this specification.

The terminology is used when not appropriate to use the more specific TIS-B or FIS-B

Service.

3.1.42 Will

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

3.2 Functional Requirements

The TIS-B/FIS-B Services functional requirements are presented in the following sections.

3.2.1 Broadcast Services Processing

The Broadcast Services Processing represents the functionality necessary to transform TIS-

B and FIS-B source data into products transmitted to aircraft/vehicles. This section contains the minimum functionality the services must contain to perform the data transformations.

3.2.1.1 TIS-B Service

TIS-B Service is only provided to aircraft that are clients. The TIS-B service identifies aircraft as clients based on the ADS-B Out and ADS-B In capabilities of an aircraft. The following requirements apply to determining whether an aircraft is set as a client for the provision of this service.

a. The TIS-B Service shall [E5243] identify an aircraft as a client for receiving TIS-B when the aircraft has ADS-B Out equipment that meets a defined performance threshold as follows:

1. Link Version greater than or equal to a configured threshold (defaulted to 1), and

2. NACP greater than or equal to a configured threshold (defaulted to 0), and

3. NIC greater than or equal to a configured threshold (defaulted to 0), and

4. SDA greater than or equal to a configured threshold (defaulted to 0), and

5. SIL greater than or equal to a configured threshold (defaulted to 0), and

6. NACV greater than or equal to a configured threshold (defaulted to 0).

b. The TIS-B Service shall [E5244] only set aircraft with ADS-B Link Version 2 as clients when these aircraft indicate ADS-B In capability on one or more datalinks.

c. The TIS-B service shall [E5245] drop an aircraft from client status if its ADS-B Out data falls below the performance thresholds of requirement 3.2.1.1a for a configured time period (defaulted to 60 seconds).

Other TIS-B Service functional requirements are…