TERMA
TERMA
TERMA
Class: ICD
Doc. no: 794948-DI
Rev: G CAGE code: R0567
Prepared by: CHR
Approved by: CGL
© Terma, Denmark, 2018. Proprietary and intellectual rights of Terma A/S and/or its subsidiaries are involved in the subject-matter of this material and all manu-
facturing, reproduction, use, disclosure, and sales rights pertaining to such subject-matter are expressly reserved. This material is submitted for a specific pur-
pose as agreed in writing, and the recipient by accepting this material agrees that this material will not be used, copied, or reproduced in whole or in part nor its
contents (or any part thereof) revealed in any manner or to any third party, except own staff, to meet the purpose for which it was submitted and subject to the
terms of the written agreement.
Record of Changes
ECR/ECO Description Rev Date
Released. A 2012-08-31
Corrected I048 data-item numbers for FRN6 and FRN22+. A1 2013-08-05
45210/65526 Added sector support for CAT 034 and multicast. B 2014-10-21
46848/66927 Added FRN 6/7/8 to CAT 034. C 2015-06-18
“Always” -> “Defaults to”.
Minor textual changes.
Added note that output of coasting and termination mes-
sages in CAT 048 can be disabled.
Added section “Unimplemented Fields in ASTERIX mes-
sages”.
47781/67933 Added CAT 240 video messages. D 2015-12-03
Minor textual touch-ups.
Added bandwidth usage.
50111/70143 Added CAT 010 Track and status messages. E 2016-11-24
RAB bit is set to 1 for permanent echoes in CAT 048
Target Report Descriptor.
Clarified data transmitted in CAT 240.
Updated examples in CAT 240 to show that only instru-
mented video is sent.
50285/70566 Field CBS corrected to GBS in CAT 010. E1 2017-02-21
Field RAP corrected to RAB in CAT 010.
Field TFF corrected to TTF in CAT 010.
FRN 40, Measured Position in Polar Co-ordinates in CAT
010 is not affected by the TCC bit.
53166/72766 Added FRN 25 (I010/210) to CAT 010. F 2018-02-14
In the CAT 010 field FRN 3 Target Report Descriptor
(I010/020), the CHN and RAB fields are supported.
Made CAT 010 Periodic Status Message transmission
interval configurable.
Added clarification of the CAT034 CH-A/B field in FRN 4
(I034/050) and active/passive multicast port options for
dual transceiver configurations.
54043/73786 FRN 9 Calculated Track Velocity in Cartesian Coordinates G See front
(I010/202) supported in CAT 010. page
FRN 22 Standard Deviation of Position (I010/500) sup-
ported in CAT010.
Made publication of optional fields configurable in CAT
010, 034, 048 and 240. Recommended UAPs added.
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 3 of 22
Contents
1 Introduction ...................................................................................................... 4
1.1 Purpose ............................................................................................................. 4
1.2 Scope ................................................................................................................ 4
2 References ....................................................................................................... 4
3 Definitions ........................................................................................................ 4
4 Supported ASTERIX categories ...................................................................... 4
4.1 Unimplemented Fields in ASTERIX messages .................................................. 5
4.2 Connection ........................................................................................................ 5
4.3 Category 010 – Monosensor Surface Movement Data ....................................... 6
4.4 Category 034 – Monoradar Service Messages ................................................ 10
4.5 Category 048 – Monoradar Target Reports...................................................... 13
4.6 Category 240 – Radar Video Transmission...................................................... 16
5 Network Bandwidth Usage ............................................................................ 20
5.1 Category 010 ................................................................................................... 20
5.2 Category 034 ................................................................................................... 20
5.3 Category 048 ................................................................................................... 21
5.4 Category 240 ................................................................................................... 21
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 4 of 22
1 Introduction
1.1 Purpose
The purpose of this document is to specify the ASTERIX data categories and data fields
supported in the implementation of the SCANTER ASTERIX data.
1.2 Scope
The scope of this document is to describe the implemented parts of the supported ASTERIX
categories. For details on the protocol implementation, see documents [1] [2] [3] [4].
2 References
Ref. Doc. No. Title
[1] SUR.ET1.ST05.2000-STD-01-01 Surveillance Data Exchange – part 1 (ASTERIX) v1.26
[2] SUR.ET1.ST05.2000-STD-02b-01 Surveillance Data Exchange – part 2b (ASTERIX) v1.27
[3] SUR.ET1.ST05.2000-STD-04-01 Surveillance Data Exchange – part 4 (ASTERIX) v1.21
[4] EUROCONTROL-SPEC-0149-240 Surveillance Data Exchange – ASTERIX Category 240 v1.3
[5] RFC 1950 ZLIB Compressed Data Format Specification version 3.3 - 1996
[6] SUR.ET1.ST05.2000-STD-07-01 Transmission of Monosensor Surface Movement Data v1.1
3 Definitions
Term Definition
ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange
ET2 Embedded Tracker 2
SAC System Area Code
SIC System Identification Code
TCP Transmission Control Protocol
UAP User Application Profile
UDP User Datagram Protocol
Permanent Echo A target that the radar always has to detect to verify that the radar is functional
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 5 of 22
Publication of each data category can be disabled/enabled at run time by adjusting equiva-
lent parameters. It is furthermore possible to configure publication of optional fields within
each data category and message type according to the standard UAP. Each implemented
optional data item can be suppressed using configurable parameters at the service level.
In the ASTERIX protocol a sensor is identified using an area code (SAC, an octet) and a sys-
tem identifier (SIC, an octet) which is unique within the SAC. The SIC and SAC codes are
configurable parameters at the service level under the Track Publisher parameter category.
Each transmitted ASTERIX Data Block contains the SAC/SIC code pair in a Data Source
Identifier Data Field.
Note that all time stamps in ASTERIX are time-of-day time stamps. Thus, date information is
assumed to be known from elsewhere. Thus a date log need to be maintained elsewhere if
unambiguous date and time information for logged ASTERIX data is to be reestablished in
later offline analysis.
4.2 Connection
ASTERIX data is obtained by connecting to TCP to port 19000 or a configurable multicast
address. For dual systems, it is possible to configure different multicast ports for the publica-
tion of ASTERIX data depending on whether the individual transceiver is actively transmitting
or in a passive standby role.
ASTERIX Category 240 is sent on a separate configurable “multicast address” / ”UDP port”
and is also available on TCP port 1400 for Surface video and 1401 for Air/OSD video.
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 6 of 22
23 I010/280 Presence - - - -
26 Spare - - - -
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 7 of 22
Track cancellation message is when TRE = 1 in FRN11 I010/170 Track Status. Note, it is
possible to disable output of coasting or termination messages if needed.
Four types of category 010 is transmitted:
T1 = Target Report Message
T2 = Start Of Update Cycle Message
T3 = Periodic Status Message
T4 = Event-Triggered Status Message
The “Target Report Message” is sent each time a track is updated.
The “Start Of Update Cycle Message” is sent every time the azimuth passes north.
The “Periodic Status Message” is sent with a configurable interval between 100-10000ms.
The “Event-Triggered Status Message” is sent each time the system status updates to a new
state.
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 8 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 9 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 10 of 22
3 I034/030 Time-of-Day M M
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 11 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 12 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 13 of 22
2 I048/140 Time-of-Day M
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 14 of 22
Track cancellation message is when TRE = 1 in FRN14 I048/170 Track Status. Note, it is
possible to disable output of coasting or termination messages if needed.
FRN1 I048/010, Data Source Identifier
SAC/SIC are configurable parameters of the radar system.
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 15 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 16 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 17 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 18 of 22
Example: Compression used on an 8-bit 6000 cells radial (sweep) that ends up having the
compressed size of 1502 bytes:
NB_VB = 1502
NB_CELLS = 6000
Example: Compression used on an 8-bit 6000 cells radial (sweep) that ends up having the
compressed size of 1502 bytes:
REP = ⌈1502/64⌉ = 24
VIDEO_BLOCK = 24 * 64 bytes blocks
Last block has the last 34 bytes zero padded (24*64-1502).
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 19 of 22
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 20 of 22
Example: The tracker publishes 1000 concurrent tracks per rotation, and is set up in a 20
RPM profile. The average required data bandwidth is then:
ADBW = (0.0043 × 1000 × 20) kbit/s = 86 kbit/s
NOTE: The calculated bandwidth is an average value. If the tracks are concentrated in cer-
tain directions, extra bandwidth is needed to avoid additional transmission latency. For in-
stance, if the radar system is setup with a 180º transmission sector and the tracks can be as-
sumed to uniformly distributed in azimuth in that sector, the actual required bandwidth will be
twice the ADWB in order to avoid additional transmission latency.
Example: The radar is set up in a 20 RPM profile. The required data bandwidth is then:
DBW = (0.0491 × 20) kbit/s = ~1 kbit/s
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 21 of 22
Example: The tracker publishes 1000 concurrent tracks per rotation, and is set up in a 20
RPM profile. The average required data bandwidth is then:
ADBW = (0.0033 × 1000 × 20) kbit/s = 67 kbit/s
NOTE: The calculated bandwidth is an average value. If the tracks are concentrated in cer-
tain directions, extra bandwidth is needed to avoid additional transmission latency. For in-
stance, if the radar system is setup with a 180º transmission sector and the tracks can be as-
sumed to uniformly distributed in azimuth in that sector, the actual required bandwidth will be
twice the ADWB in order to avoid additional transmission latency.
Typically configured system configurations results in azimuth and range resolutions of 4092 ×
4096 or 4096 × 8192. Antenna RPM is from 2 – 60 RPM and video type can be both com-
pressed and uncompressed.
Type Estimated Compression Ratio
Uncompressed (100:100) 1
5.4.1 Uncompressed
The bandwidth usage for the uncompressed is constant, i.e. the compression ratio does not
change depending on the amount of information in the radar image.
So for a 4096 × 4096 azimuth and range resolution, instrumented range set to cover full 4096
range and an antenna RPM of 30 the bandwidth usage will be:
0.0001333 × 4096 × (4096 + 33) × 30 × 1 = 67633 kbit/s = 68Mbit/s.
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED
COMPANY UNCLASSIFIED
SCANTER ASTERIX Protocol
Doc. no: 794948-DI, Rev: G Page 22 of 22
5.4.2 Compressed
The bandwidth usage for compressed video depends on the amount of information in the ra-
dar image and is very site specific. Over land with almost no processing enabled the com-
pression ratio will typically be 10:3 (30%) whereas a scenario with aggressive processing
over land and sea, the compression ratio will be less than 100:2 (2%) of the original size.
So for a 4096 × 4096 azimuth and range resolution, instrumented range set to cover full 4096
cell range, an antenna RPM of 30 and a 10:3 (30%) compression ratio, the bandwidth usage
will be:
0.0001333 × 4096 × (4096 + 33) × 30 × 0.3 = 27290 kbit/s = 27Mbit/s.
The use and/or disclosure, etc. of the contents of this document (or any part thereof) is subject to the restrictions referenced on the front page.
COMPANY UNCLASSIFIED