Asterix Spec v2.0
Asterix Spec v2.0
Enclosure 1
EUROCONTROL Specification
for
Surveillance Data Exchange -
Part 1
All Purpose Structured
EUROCONTROL Surveillance
Information Exchange
(ASTERIX)
DOCUMENT CHARACTERISTICS
TITLE
EUROCONTROL Specification for Surveillance Data Exchange
- Part 1 All Purpose Structured EUROCONTROL Surveillance
Information Exchange (ASTERIX)
Publications Reference: SPEC-
ISBN Number:
Document Identifier Edition Number: 2.00
EUROCONTROL-SPEC- Edition Date: April 2012
Abstract
This document presents the general structure of the ASTERIX format.
Keywords
Data Exchange Messages SAC SIC
Data Category Data Field Data Block Data Item
ASTERIX UAP
DOCUMENT APPROVAL
The following table identifies all management authorities who have successively approved the
present issue of this document.
ASTERIX
Manager D. Doukas
SES Unit
Manager P. Green
DSS
Director L. Tytgat
Working August 1998 Suppress RFS, units, add migration policy and
Draft compound data item structure.
Ed 1.1
Draft October Where applicable the term Radar replaced by ALL
Ed 1.2 Surveillance
1998
Introduction amended (1)
X.121 reference suppressed. (2)
Documents referenced in paragraph 2.2 updated
(2.2)
Definitions, acronyms and abbreviations updated.(3)
Characteristics of the data suppressed.(4)
Data item symbolic reference changed.(4)
UAP unique per Category as a rule.(4)
Source Identification must be present in every
record.(4)
Explicit Length data fields suppressed.(4)
Conventions updated to be more general.(5)
Annex A redesigned and changed to informative. (A)
Annex B replaced by list of SACs affected to USA,
Canada & Mexico. (B)
Annex C suppressed. (C)
Draft January 1.1 reworded ALL
Ed 1.21 1999 Explicit Length data fields re-introduced. (4)
Reserved Expansion field added. (4)
Migration Policy reworded. (7)
Draft March 1999 Editorial corrections ALL
Ed 1.22
Proposed September Editorial corrections ALL
Ed 1.24 1999
Proposed November SAC added for UK and for Ukraine 6.4
Ed 1.26 2000 Annex A updated
A
Working November Editorial correction 4.1.1.5
Draft 2001 List of SAC removed
Ed 1.27 6.4.1
Annex A updated A
Annex B removed B
Working December Editorial corrections
Draft 2001 Annex A removed
Ed 1.28 A
Publications
EUROCONTROL Headquarters
96 Rue de la Fusée
B-1130 BRUSSELS
CONTENTS
DOCUMENT CHARACTERISTICS…………………..………..…………………………………...ii
DOCUMENT APPROVAL……………………………..………..…………………………………..iii
DOCUMENT CHANGE RECORD…………………...………..……………………………………iv
CONTENTS ………………………………………….………..……………………………………..vi
LIST OF FIGURES…………………………………..………..…………………………………....viii
LIST OF TABLES…………………………………..………..………………………………………ix
EXECUTIVE SUMMARY …………………………………...……………………………………….x
1. INTRODUCTION................................................................................................ 1
1.1 General..................................................................................................................... 1
1.2 Scope ....................................................................................................................... 2
2. REFERENCES................................................................................................... 3
5. CONVENTIONS ............................................................................................... 18
5.1 Bit Numbering ....................................................................................................... 18
5.2 Binary Values ........................................................................................................ 18
5.3 Time Management................................................................................................. 18
LIST OF FIGURES
Figure 1 - Organisation of the Data ................................................................................................7
Figure 2 - Data Block Structure ....................................................................................................10
Figure 3 - Standard Data Fields Types (except compound) ......................................................12
Figure 4 - Compound Data Field Type .........................................................................................13
Figure 5 - Field Sequencing Organisation...................................................................................16
Figure 6 - Overall Record Structure .............................................................................................17
LIST OF TABLES
Table 1 - Compliance matrix .........................................................................................................25
Table 2 - ASTERIX Categories managed by RDE-TF ..................................................................27
Table 3 - ASTERIX Categories coordinated with RDE-TF ..........................................................28
EXECUTIVE SUMMARY
This EUROCONTROL specification describes the basic rules and procedures to be applied when
implementing the ASTERIX data format for the transmission of surveillance related information.
It provides information on the way ASTERIX data is organised, defines the structure of ASTERIX
messages and specifies the format conventions to be respected when composing ASTERIX
records.
Finally the ASTERIX addressing scheme is defined as well as the procedure to be followed in the
evolution of ASTERIX Category definitions.
This EUROCONTROL specification is the successor of the EUROCONTROL Standard
SUR.ET1.ST05.2000-STD-01-01.
1. INTRODUCTION
1.1 General
This EUROCONTROL Specification describes the message structure, known
by the acronym ASTERIX, originally standing for “All Purpose STructured
EUROCONTROL Radar Information Exchange”, devised by the Study Group
on the exchange of surveillance related data between processors of ATC
systems. This group was a subgroup of the former Radar Systems Specialist
Panel (RSSP), whose responsibilities have been taken over by the
Surveillance Team (SURT) as from April 1994. ASTERIX was approved by the
former RSSP at their 15th Meeting held on 1/4 July 1986. The ASTERIX
Specification is now under the responsibility of the Surveillance Data
Exchange Task Force (RDE-TF), a working arrangement under the
EUROCONTROL CNS-Team. The expansion of the application domains of
ASTERIX beyond radar led to a modification of the significance of the
acronym ASTERIX, now standing for “All Purpose STructured
EUROCONTROL SuRveillance Information Exchange”.
1.2 Scope
1.2.1 ASTERIX is an application/presentation protocol responsible for data definition
and data assembly developed to support the transmission and exchange of
surveillance related data.
Its purpose is to allow a meaningful transfer of information between two
application entities using a mutually agreed representation of the data to be
exchanged.
1.2.2 The ASTERIX Specification (consisting of this Part 1 as well as the category
definitions) refers to the Presentation and Application layers (layers six and
seven) as defined by the Open Systems Interconnection (OSI) Reference
Model (International Standards Organization (ISO) Standard 7498) [Ref. 1].
1.2.3 The definition of the lower telecommunication support layers (layers one to
five) is out of the scope of the ASTERIX Specification. Transmission of
ASTERIX coded surveillance information can make use of any available
communication medium, for instance a packet switched Wide Area Network
(WAN) as well as a Local Area Network (LAN).
1.2.4 The lower telecommunication protocol levels will be agreed between the
partners of the data exchange.
1.2.5 The ASTERIX Specification, as a Presentation protocol, defines the structure
of the data to be exchanged over the communication medium, from the
encoding of every bit of information up to the organisation of the data within a
block of data.
1.2.6 Considering that there is information common to all systems (for instance
position, Mode-A Code and Mode-C Code information), ASTERIX specifies
minimum requirements at the Application level, so as to ease data exchanges
between heterogeneous applications. The communication between two
different systems (even located in different countries) is thus made possible,
based on a core of commonly used surveillance related data, transferred in
the same way by the ASTERIX Presentation layer.
1.2.7 In order to achieve the intended level of interoperability the implementation of
the individual ASTERIX categories shall be performed exactly like specified in
the latest editions of the respective definitions as published on the
EUROCONTROL ASTERIX website (www.eurocontrol.int/asterix). In cases
where the exchange of specific information between two users is required,
exclusively the Special Purpose Field (see 4.2.5 below) shall be used.
1.2.8 This edition of Part 1 does not apply to Categories 001, 002 and 008. The
implementation of these categories shall follow the rules as described in the
corresponding definitions.
2. REFERENCES
1. ISO/IEC 7498-1: 1994 [ITU-Rec.X.200 (19940]
Information Processing Systems - OSI Reference Model - The Basic
Model
2. Commission Regulation (EC) No 1207/2011 of 22/11/2011 laying down
requirements for the Performance and Interoperability of Surveillance for
the Single European Sky
3.1 Definitions
For the purposes of this EUROCONTROL Specification, the following
definitions shall apply:
3.1.1 Catalogue of List of all the possible Data Items of each Data Category
describing the Data Items by their reference, structure, size
Data Items:
and units (where applicable).
3.1.5 Data Item: The smallest unit of information in each Data Category.
3.1.7 User The mechanism for assigning Data Items to Data Fields,
and containing all necessary information which needs to be
Application
standardised for the successful encoding and decoding of
Profile:
the messages.
SURVEILLANCE RELATED
DATA
...
DATA ITEM (x + 1) x
...
Primary Subfield
Octet No.1
8 7 6 5 4 3 2 1
Data Subfield No 1
.
.
.
.
.
Data Subfield No 7
Octet No.1
8 7 6 5 4 3 2 1
Item of Information 7
bit 1 bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 bit 8 bit 9 bit 10 bit 11 bit 12 bit 13 bit 14 bit 15 bit 16
Released Issue
FSPEC
RECORD
Surveillance Information Exchange (ASTERIX)
Edition : 2.00
EUROCONTROL Specification for Surveillance Data Exchange - Part 1 All Purpose Structured EUROCONTROL
Surveillance Information Exchange (ASTERIX)
5. CONVENTIONS
5.1 Bit Numbering
5.1.1 All bit positions within a one octet field shall be numbered right to left from one
to eight.
5.1.2 For an n-octet field:
the octets shall be numbered left to right from one to n;
the bit positions shall be numbered right to left from one to n x 8.
5.1.3 With an FSPEC field the following exceptions for bit positions shall apply:
in a one-octet FSPEC the bits will be numbered left to right from one to
eight;
in a p-octet FSPEC the bits will be numbered left to right from one to
px8.
5.1.4 Data shall be presented to the application at the receiving end in the same
order as generated at the transmitting end.
6.1 General
In order to avoid ambiguity, every system shall have a unique identification in
an area where ASTERIX is used for the exchange of data.
6.2 Syntax
The ASTERIX System Identifier format shall be composed of two subfields as
illustrated below:
SAC SIC
6.3 Formats
6.3.1 System Area Code (SAC)
6.3.1.1 The SAC field shall consist of an eight-bit number assigned to a geographical
area or a country.
6.3.1.3 The SAC field format shall be as illustrated below:
b b b b b b b b
b b b b b b b b
7.2 Description
7.2.1 Application Domain
7.2.1.1 The ASTERIX format can be used to convey various information related to
surveillance. An application domain is a particular application of ASTERIX,
such as the transmission of mono-surveillance target reports or the
transmission of mono-surveillance service messages.
7.2.1.2 The ASTERIX migration policy allows the definition of 32 application domains
that shall be identified by an initial Category number between 0 and 31. Each
application domain shall be described in one and only one part of the
ASTERIX Specification.
7.2.3 Modifications
7.2.3.1 Modifications, which would result in non-interoperable implementations, shall
be withheld and collected during a five to ten years period for implementation
in the next version, which then re-uses the eldest Category number from the
cyclic pool.
7.2.3.2 Recommendation Minor modifications, not leading to interoperability
problems, should be implemented at intermediate points in time (in the last
version, thus not creating a new version).
NOTE - The Reserved Expansion field feature provides an escape
mechanism to introduce modifications at an early stage, before
proceeding to a new version.
A.1 General
Commission Regulation (EC) No 1207/2011 of 22/11/2011 lays down
requirements for the performance and interoperability of surveillance for the
Single European Sky.
ASTERIX as data format for the exchange of surveillance related data is fully
consistent with the relevant requirements of the Regulation therefore it may be
used by the stakeholders in the implementation of these requirements. In
order to facilitate the implementation as well as the demonstration of
compliance, Annex A.2 provides the traceability between the relevant
regulatory requirements and content of the ASTERIX Specification.
To be considered compliant with the interoperability requirements of the
regulation the basic principles as laid down in Part 1 of ASTERIX have to be
respected and the ASTERIX categories have to be implemented as described
in the respective definitions.
To be compliant with the interoperability requirements of the regulation it is
assumed that the appropriate surveillance infrastructure has been
implemented.
A. 2 Compliance Matrix
Commission Regulation
ASTERIX Requirements
No 1207/2011
Regulatory Requirements
Category Application
Category Application
3
128 C I Messages
150 Flight Data Messages
151 Association Messages
152 Time Stamp Messages
240 Radar Video Transmission
247 Version Number Exchange
251 Supplemental Data (Birdtam)
252 Session and Service Control Messages
253 Remote Station Monitoring and Control Information