Standard Specification for UAS Traffic Management (UTM) UAS Service Supplier (USS) Interoperability

SIGNIFICANCE AND USE
7.1 This specification is intended to be used by USS developers, CAAs, and others to assess USS conformance with this UTM specification.
SCOPE
1.1 This specification is intended to be a global specification providing components that may be used to satisfy requirements expected to be common to many UTM-related regulations. This specification is not intended to comprehensively address all aspects of any particular UTM-related regulation or concept of operations. Similarly, because varying terminology for the same concept is frequently used across different regulations, readers should not expect an exact terminology consistency with any particular UTM-related regulation.  
1.2 This version of the specification is focused on strategic aspects of UAS operations, including strategic conflict detection, aggregate conformance of operations to their operational intents, constraint awareness, and situational awareness in the event of nonconforming or contingent operations. The intention is that this specification will evolve to address increasingly complex strategic aspects of UAS operations and potentially certain tactical aspects of UAS operations.  
1.3 This specification addresses the performance and interoperability requirements, including associated application programming interfaces (APIs), for a set of UTM roles performed by UAS Service Suppliers (USSs) in support of UAS operations.2 Roles are groupings of one or more related UTM services. A competent authority may choose to use the roles defined in this specification in establishing the granularity of authorizations granted to a USS. The roles defined in this specification are:
(1) Strategic Coordination, comprising the Strategic Conflict Detection and Aggregate Operational Intent Conformance Monitoring services;
(2) Conformance Monitoring for Situational Awareness (CMSA);
(3) Constraint Management, comprising the Constraint Management service; and
(4) Constraint Processing, comprising the Constraint Processing service.  
1.4 Section 4, Conceptual Overview, provides a description of each of the services and roles and includes further discussion on their scope.  
1.5 A regulator may choose to require that a USS support a minimum or prescribed set of roles and services and may adopt terminology other than USS for a software system that provides something other than that minimum or prescribed set of roles and services. However, for purposes of this specification, a USS is a system that provides one or more of the UTM services defined in this specification.  
1.6 A USS is not required by this specification to perform all roles or implement all defined services, providing business case flexibility for implementers. A typical USS that supports operators in the planning and execution of UAS operations may implement the Strategic Coordination, Constraint Processing, and CMSA roles. (Note that a USS providing CMSA for a UAS operation is required to also provide Strategic Coordination for the operation.) However, other implementations more limited in scope are possible. For example, a USS may implement only the Constraint Management role and be intended for use only by authorized constraint providers; or, a USS may implement only the Constraint Processing role to provide general airspace awareness to users independent of planning UAS flights. USSs may also provide additional, value-added capabilities and still be compliant with this specification as long as the value-added capabilities do not conflict with the services defined in this specification, and the implementation of services defined in this specification conforms to the applicable requirements.  
1.7 A USS may also support other UTM roles such as Remote ID and airspace access (for example, the FAA’s LAANC), specified in other documents.  
1.8 This specification addresses aspects common to all roles and services, such as Discovery and Synchronization Services (DSS), security, aud...

General Information

Status
Published
Publication Date
30-Nov-2021
Drafting Committee
Current Stage
Ref Project

Buy Standard

Technical specification
ASTM F3548-21 - Standard Specification for UAS Traffic Management (UTM) UAS Service Supplier (USS) Interoperability
English language
49 pages
sale 15% off
Preview
sale 15% off
Preview

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:F3548 −21
Standard Specification for
UAS Traffic Management (UTM) UAS Service Supplier (USS)
1
Interoperability
This standard is issued under the fixed designation F3548; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision.Anumber in parentheses indicates the year of last reapproval.A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1. Scope (3)Constraint Management, comprising the Constraint
Management service; and
1.1 Thisspecificationisintendedtobeaglobalspecification
(4)Constraint Processing, comprising the Constraint Pro-
providingcomponentsthatmaybeusedtosatisfyrequirements
cessing service.
expected to be common to many UTM-related regulations.
This specification is not intended to comprehensively address
1.4 Section 4, Conceptual Overview, provides a description
allaspectsofanyparticularUTM-relatedregulationorconcept
ofeachoftheservicesandrolesandincludesfurtherdiscussion
of operations. Similarly, because varying terminology for the
on their scope.
same concept is frequently used across different regulations,
1.5 Aregulator may choose to require that a USS support a
readers should not expect an exact terminology consistency
minimumorprescribedsetofrolesandservicesandmayadopt
with any particular UTM-related regulation.
terminology other than USS for a software system that pro-
1.2 This version of the specification is focused on strategic
vides something other than that minimum or prescribed set of
aspects of UAS operations, including strategic conflict
roles and services. However, for purposes of this specification,
detection, aggregate conformance of operations to their opera-
a USS is a system that provides one or more of the UTM
tional intents, constraint awareness, and situational awareness
services defined in this specification.
in the event of nonconforming or contingent operations. The
intention is that this specification will evolve to address 1.6 AUSSisnotrequiredbythisspecificationtoperformall
increasingly complex strategic aspects of UAS operations and roles or implement all defined services, providing business
potentially certain tactical aspects of UAS operations. case flexibility for implementers. A typical USS that supports
operators in the planning and execution of UAS operations
1.3 This specification addresses the performance and in-
may implement the Strategic Coordination, Constraint
teroperability requirements, including associated application
Processing, and CMSA roles. (Note that a USS providing
programming interfaces (APIs), for a set of UTM roles
CMSA for a UAS operation is required to also provide
performed by UAS Service Suppliers (USSs) in support of
2
Strategic Coordination for the operation.) However, other
UAS operations. Roles are groupings of one or more related
implementations more limited in scope are possible. For
UTM services. A competent authority may choose to use the
example, a USS may implement only the Constraint Manage-
rolesdefinedinthisspecificationinestablishingthegranularity
mentroleandbeintendedforuseonlybyauthorizedconstraint
of authorizations granted to a USS. The roles defined in this
providers; or, a USS may implement only the Constraint
specification are:
Processing role to provide general airspace awareness to users
(1)Strategic Coordination, comprising the Strategic Con-
independent of planning UAS flights. USSs may also provide
flict Detection andAggregate Operational Intent Conformance
additional, value-added capabilities and still be compliant with
Monitoring services;
thisspecificationaslongasthevalue-addedcapabilitiesdonot
(2)Conformance Monitoring for Situational Awareness
conflict with the services defined in this specification, and the
(CMSA);
implementation of services defined in this specification con-
forms to the applicable requirements.
1
This specification is under the jurisdiction of ASTM Committee F38 on
1.7 A USS may also support other UTM roles such as
UnmannedAircraftSystemsandisthedirectresponsibilityofSubcommitteeF38.02
Remote ID and airspace access (for example, the FAA’s
on Flight Operations.
Current edition approved Dec. 1, 2021. Published March 2022. DOI: 10.1520/
LAANC), specified in other documents.
F3548-21.
2
Many terms describe UTM and UAS Service Suppliers. For example, UTM is
1.8 Thisspecificationaddressesaspectscommontoallroles
referred to as U-Space, and USSs are referred to as U-Space Service Providers
and services, such as Discovery and Synchronization Services
(USSPs) in Europe. In the United Kingdom, UTM Service Providers (UTMSP) is
(DSS), security, auditing, and handling of off-n
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.