ASTM F3411-22a
(Specification)Standard Specification for Remote ID and Tracking
Standard Specification for Remote ID and Tracking
SCOPE
1.1 This specification covers the performance requirements for remote identification (Remote ID) of unmanned aircraft systems (UAS). Remote ID allows governmental and civil identification of UAS for safety, security, and compliance purposes. The objective is to increase UAS remote pilot accountability by removing anonymity while preserving operational privacy for remote pilots, businesses, and their customers. Remote ID is an enabler of enhanced operations such as beyond visual line of sight (BVLOS) operations as well as operations over people.
1.2 This specification defines message formats, transmission methods, and minimum performance standards for two forms of Remote ID: broadcast and network. Broadcast Remote ID is based on the transmission of radio signals directly from a UAS to receivers in the UAS’s vicinity. Network Remote ID is based on communication by means of the internet from a network Remote ID service provider (Net-RID SP) that interfaces directly or indirectly with the UAS, or with other sources in the case of intent-based network participants.
1.3 This specification addresses the communications and test requirements of broadcast or network Remote ID, or both, in UAS and Net-RID SP systems.
1.4 Applicability:
1.4.1 This specification is applicable to UAS that operate at very low level (VLL) airspace over diverse environments including but not limited to rural, urban, networked, network degraded, and network denied environments, regardless of airspace class.
1.4.2 This specification neither purports to address UAS operating with approval to use ADS-B or secondary surveillance radar transponders, nor does it purport to solve ID needs of UAS for all operations.
1.4.3 In particular, this specification does not purport to address identification needs for UAS that are not participating in Remote ID or operators that purposefully circumvent Remote ID.
1.5 The values stated in SI units are to be regarded as standard. The values given in parentheses after SI units are provided for information only and are not considered standard.
1.5.1 Units of measurement included in this specification:
m
meters
deg, °
degrees of latitude and longitude, compass direction
s
seconds
Hz
Hertz (frequency)
dBm
decibel-milliwatts (radio frequency power)
ppm
parts per million (radio frequency variation)
μs
microseconds
ms
milliseconds
1.6 Table of Contents:
Title
Section
Scope
1
Referenced Documents
2
Terminology
3
Remote ID and Network Interoperability Conceptual Overview
4
Performance Requirements
5
TEST METHODS
Scope
6
Significance and Use
7
Hazards
8
Test Units
9
Procedure
10
Precision and Bias
11
Product Marking
12
Packaging and Package Marking
13
Keywords
14
ANNEX A1—Broadcast Authentication Verifier Service
Annex A1
ANNEX A2—Network Remote ID Interoperability Requirements, APIs, and Testing
Annex A2
ANNEX A3—Tables of Values
Annex A3
ANNEX A4—USS-DSS and USS-USS OpenAPI YAML Description
Annex A4
ANNEX A5—Number Registrar Management Policy
Annex A5
APPENDIX X1—Performance Characteristics
Appendix X1
APPENDIX X2—List of Subcommittee Participants and Contributors
Appendix X2
APPENDIX X3—Background Information
Appendix X3
1.7 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use. Some specific hazards statements are given in Section 8 on Hazards.
1.8 This international standard was developed in accordance with internationally recognized principles on standardization established in the D...
General Information
Relations
Standards Content (Sample)
This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the
Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
Designation:F3411 −22a
Standard Specification for
Remote ID and Tracking
This standard is issued under the fixed designation F3411; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
NOTE—Subsection 5.4.3 and Table A3.3 were corrected, with other editorial changes made throughout, and the yeardate changed on
June 17, 2022.
1. Scope lance radar transponders, nor does it purport to solve ID needs
of UAS for all operations.
1.1 This specification covers the performance requirements
1.4.3 In particular, this specification does not purport to
for remote identification (Remote ID) of unmanned aircraft
address identification needs for UAS that are not participating
systems (UAS). Remote ID allows governmental and civil
in Remote ID or operators that purposefully circumvent
identification of UAS for safety, security, and compliance
Remote ID.
purposes. The objective is to increase UAS remote pilot
accountabilitybyremovinganonymitywhilepreservingopera- 1.5 The values stated in SI units are to be regarded as
tional privacy for remote pilots, businesses, and their custom- standard. The values given in parentheses after SI units are
ers. Remote ID is an enabler of enhanced operations such as provided for information only and are not considered standard.
beyond visual line of sight (BVLOS) operations as well as 1.5.1 Units of measurement included in this specification:
operations over people.
m meters
deg, ° degrees of latitude and longitude, compass direction
1.2 This specification defines message formats, transmis-
s seconds
sion methods, and minimum performance standards for two Hz Hertz (frequency)
dBm decibel-milliwatts (radio frequency power)
forms of Remote ID: broadcast and network. Broadcast Re-
ppm parts per million (radio frequency variation)
mote ID is based on the transmission of radio signals directly
µs microseconds
from a UAS to receivers in the UAS’s vicinity. Network
ms milliseconds
RemoteIDisbasedoncommunicationbymeansoftheinternet
1.6 Table of Contents:
from a network Remote ID service provider (Net-RID SP) that
Title Section
interfaces directly or indirectly with the UAS, or with other
Scope 1
Referenced Documents 2
sources in the case of intent-based network participants.
Terminology 3
1.3 This specification addresses the communications and
Remote ID and Network Interoperability Conceptual Overview 4
Performance Requirements 5
test requirements of broadcast or network Remote ID, or both,
TEST METHODS
in UAS and Net-RID SP systems.
Scope 6
Significance and Use 7
1.4 Applicability:
Hazards 8
1.4.1 This specification is applicable to UAS that operate at
Test Units 9
Procedure 10
very low level (VLL) airspace over diverse environments
Precision and Bias 11
including but not limited to rural, urban, networked, network
Product Marking 12
degraded, and network denied environments, regardless of
Packaging and Package Marking 13
Keywords 14
airspace class.
ANNEX A1—Broadcast Authentication Verifier Service Annex A1
1.4.2 This specification neither purports to address UAS
ANNEX A2—Network Remote ID Interoperability Requirements, Annex A2
operating with approval to use ADS-B or secondary surveil-
APIs, and Testing
ANNEX A3—Tables of Values Annex A3
ANNEX A4—USS-DSS and USS-USS OpenAPI YAML Annex A4
Description
This specification is under the jurisdiction of ASTM Committee F38 on
ANNEX A5—Number Registrar Management Policy Annex A5
UnmannedAircraftSystemsandisthedirectresponsibilityofSubcommitteeF38.02
APPENDIX X1—Performance Characteristics Appendix X1
on Flight Operations.
APPENDIX X2—List of Subcommittee Participants and Appendix X2
Current edition approved June 17, 2022. Published July 2022. Originally
Contributors
approved in 2019. Last previous edition approved in 2022 as F3411–22. DOI:
APPENDIX X3—Background Information Appendix X3
10.1520/F3411-22A.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
F3411−22a
1.7 This standard does not purport to address all of the WGS-84 World Geodetic System — 1984
safety concerns, if any, associated with its use. It is the
3. Terminology
responsibility of the user of this standard to establish appro-
priate safety, health, and environmental practices and deter- 3.1 This standard uses terminology contained within F3341,
mine the applicability of regulatory limitations prior to UAS Terminology Standard, and F3060,Aircraft Terminology
use. SomespecifichazardsstatementsaregiveninSection8on Standard.These terms are not duplicated within this document.
Hazards.
3.2 Unique and Common Terminology—Terminology used
1.8 This international standard was developed in accor-
in multiple standards is defined in F3341 and F3060. Termi-
dance with internationally recognized principles on standard-
nology that is unique to this specification is defined in 3.3.
ization established in the Decision on Principles for the
3.3 Definitions of Terms Specific to This Standard:
Development of International Standards, Guides and Recom-
3.3.1 authentication, n—the process or action of verifying
mendations issued by the World Trade Organization Technical
that the source of a Remote ID message is the originator of the
Barriers to Trade (TBT) Committee.
message.
3.3.2 broadcast, v—to transmit data to no specific destina-
2. Referenced Documents
tion or recipient; data can be received by anyone within
2.1 ASTM Standards:
broadcast range.
F3060 Terminology for Aircraft
3.3.3 broadcast UAS, n—a UAS that is equipped for and is
F3341 Terminology for Unmanned Aircraft Systems
actively broadcasting Remote ID data during an operation;
2.2 Other Standards:
being a broadcast UAS is not mutually exclusive with being a
ANSI/CTA-2063-A Small Unmanned Aerial Systems Serial
networked UAS.
Numbers
4,5 6
3.3.4 discovery, n—the process of determining the set of
Bluetooth Core Specification 5.0
USSs with which data exchange is required for some UTM
IEEE 802.11 Standard for Information technology--
function; discovery is accomplished by means of the discovery
Telecommunications and information exchange between
and synchronization service (DSS).
systems - Local and metropolitan area networks--Specific
3.3.5 DSS entity, n—a generic concept that refers to infor-
requirements - Part 11: Wireless LAN Medium
mation that can be discovered using the discovery and syn-
Access Control (MAC) and Physical Layer (PHY)
7,5
chronization service (DSS).
Specifications
3.3.5.1 Discussion—Entities are characterized by a 4-D
IEEE 1609.2 IEEE Standard for Wireless Access in Vehicu-
volumeofairspace(thatis,avolumedefinedin x, y, zplustime
lar Environments--Security Services for Applications and
limits). For Remote ID, the entity type is referred to as an
Management Messages
identification service area. Operations and constraints are
IETF RFC3339 Date andTime on the Internet:Timestamps
examples of other types of entities that are the subject of other
IETF RFC4122 A Universally Unique IDentifier (UUID)
UTM standards.
URN Namespace
IETF RFC8126 Guidelines for Writing an IANA Consider-
3.3.6 DSS pool, n—a synchronized set of DSS instances
ations Section in RFCs
where operations may be performed on any instance with the
11,5
Neighbor Awareness Networking Specification
same result, and information may be queried from any instance
FAAUTM ConOps v1.0 UnmannedAircraft System (UAS)
with the same result. A DSS region will often have a produc-
Traffic Management (UTM) Concept of Operations
tion DSS pool along with one or more test or staging DSS
pools.
3.3.7 DSS region, n—the geographic area supported by a
For referenced ASTM standards, visit the ASTM website, www.astm.org, or DSS pool.
contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM
3.3.8 dynamic data, n—data that changes over the duration
Standards volume information, refer to the standard’s Document Summary page on
the ASTM website. of the flight; for example, longitude and latitude.
Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St.,
3.3.9 Ground Control Station (GCS), n—the part of a UAS
4th Floor, New York, NY 10036, http://www.ansi.org.
thatremotelycontrolstheUA.Itmayormaynothavearemote
Used throughout the specification, Bluetooth is a registered trademark of
Bluetooth SIG, Inc., 5209 Lake Washington Blvd. NE, Suite 350, Kirkland, WA
pilot directly manipulating the controls.
98033.
5 3.3.10 identify—the result of the process to establish the
Other names and brands may be claimed as the property of others.
Available from https://www.bluetooth.com/specifications/archived- identity of a specific UAS that is traceable to the owner and
%20specifications/.
remote pilot.
Available from Institute of Electrical and Electronics Engineers, Inc. (IEEE),
3.3.11 intent-based network participant, n—a UAS for
445 Hoes Ln., Piscataway, NJ 08854-4141, https://standards.ieee.org/standard/802
_11-2016.html.
which the operator has reported an intended area (a volume of
Available from IETF Tools, https://tools.ietf.org/html/rfc3339.
Available from IETF Tools, https://tools.ietf.org/html/rfc4122.
Available from https://datatracker.ietf.org/doc/html/rfc8126. Available from International CivilAviation Organization (ICAO), 999 Robert-
Available from Wi-Fi Alliance, 10900-B Stonelake Boulevard, Suite 126, Bourassa Boulevard, Montréal, Quebec, Canada H3C 5H7, https://www.icao.int/
Austin, TX 78759, https://www.wi-fi.org/discover-wi-fi/wi-fi-aware. safety/pbn/Documentation/EUROCONTROL/
Available from https://utm.arc.nasa.gov/docs/2018-UTM-ConOps-v1.0.pdf. Eurocontrol%20WGS%2084%20Implementation%20Manual.pdf.
F3411−22a
airspace) and time for an operation through a Net-RID service compliance (for example, threshold values, test methods,
provider; such information is then reported through the net- oversight, and references to other standards). “Should” state-
work Remote ID infrastructure. Intent-based Remote ID par- ments also represent parameters that could be used in safety
ticipationisanoptionfornon-equippedUASorUASoperating evaluations, and could lead to development of future require-
in environments that preclude broadcast or network participa- ments. “May” statements are provided to clarify acceptability
tion. of a specific item or practice, and offer options for satisfying
requirements.
3.3.12 network Remote ID (Net-RID) service provider, n—a
logical entity denoting a UTM system or comparable UAS 3.3.22 static data, n—datathatremainsthesameordoesnot
flight management system that participates in network Remote change often over the duration of a flight (for example, Unique
ID and provides data for and about UAS it manages. ID); this is in contrast to dynamic data that may change more
frequently (such as longitude and latitude).
3.3.13 network Remote ID (Net-RID) display provider, n—a
logical entity that aggregates network Remote ID data from 3.3.23 UAS operation plan, n—a UAS operation plan is
potentially multiple Net-RID service providers and provides developed prior to the operation and should indicate the
the data to a display application (that is, an app or website); in
volume of airspace within which the operation is expected to
practice, it is expected that many USSs may be both Net-RID occur,thetimesandlocationsofthekeyeventsassociatedwith
display providers and Net-RID service providers, but stand-
the operation, including launch, recovery, and any other
alone Net-RID display providers are possible. information deemed important (for example, segmentation of
the operation trajectory by time).
3.3.14 network publishing, v—the act of transmitting data to
UTM ConOps v1.0
aninternetserviceorfederationofservices;clients,whetherair
traffic control (ATC), public safety officials, or possibly the
3.3.24 UAS registration ID, n—an identification number or
general public can access the data to obtain ID and tracking combination of letters and numbers assigned by a CAA or
information for UAS for which such data has been published.
authorized representative to a UAS; this is sometimes referred
to as a registration number (which may or may not contain
3.3.15 networked UAS, n—a UAS that during operations is
letters).
in electronic communication with a Net-RID service provider
(for example, by means of internet Wi-Fi, cellular, or 3.3.25 UAS service supplier (USS), n—USSs provide UTM
satellite, or other communications medium such as short burst
services to support the UAS community, to connect operators
data satellite communications). and other entities to enable information flow across the USS
network, and to promote shared situational awareness among
3.3.16 non-equipped UAS, n—in the context of Remote ID,
UTM participants. UTM ConOps v1.0
a UAS that is neither a networked nor broadcast UAS (for
example, a radio controlled model aircraft) and cannot directly
3.3.26 unique ID, n—a data element that can be traced to a
report its location or identity.
unique UAS and its operator.
3.3.17 operator, n—theindividualororganizationwhouses,
3.4 Acronyms and Abbreviations:
causes to use, or authorizes to use an aircraft for the purpose of
3.4.1 AES, n—advanced encryption standard
air navigation, including the piloting of an aircraft, with or
3.4.2 AGL, adj—above ground level
without the right of legal control (as owner, lessee, or
3.4.3 API, n—application programming interface
otherwise). F3060
3.4.4 ARC, n—aviation rulemaking committee
3.3.18 operator location, n—the geographic location of the
remote pilot in command of a UAS. 3.4.5 BVLOS, adj—beyond visual line of sight
3.3.19 position extrapolation, n—a capability of a Net-RID
3.4.6 C2, n—command and control
service provider to predict the location of a UAS based on a
3.4.7 CAA, n—Civil Aviation Authority
modeled 4-D trajectory derived from an intended UAS opera-
3.4.8 CONUS, n—contiguous United States
tion plan.
3.4.9 DAR, n—DSS airspace representation
3.3.20 registration, n—the process by which an owner/
3.4.10 DSS, n—discovery and synchronization service
operator (including contact information and other PII) and
aircraft (for example, make, model) are associated with an
3.4.11 EIRP, n—effective isotropic radiated power
assigned, unique identifier.
3.4.12 EMI, n—electromagnetic interference
3.3.21 shall, must versus should versus may—use of the
3.4.13 FAA, n—Federal Aviation Administratio
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.