ISO 23629-5:2023
(Main)UAS traffic management (UTM) - Part 5: UTM functional structure
UAS traffic management (UTM) - Part 5: UTM functional structure
This document is dedicated to establishing a common understanding of UTM core functions and functional structure. It provides a detailed description of the UTM system layer given in the UTM Framework. This document excludes: - role-sharing among entities constituting UTM, which is left to implementations; - technical methodology of communication or data transaction among core functions; - business model of players engaging in a function of UTM.
Gestion du trafic des aéronefs sans pilote (UTM) — Partie 5: Structure fonctionnelle de l'UTM
General Information
- Status
- Published
- Publication Date
- 25-Apr-2023
- Technical Committee
- ISO/TC 20/SC 16 - Unmanned aircraft systems
- Drafting Committee
- ISO/TC 20/SC 16/WG 4 - UAS Traffic Management
- Current Stage
- 6060 - International Standard published
- Start Date
- 26-Apr-2023
- Due Date
- 05-Feb-2023
- Completion Date
- 26-Apr-2023
Overview
ISO 23629-5:2023 defines a common UTM functional structure for Unmanned Aircraft System (UAS) Traffic Management (UTM). It provides a detailed description of the UTM system layer in the UTM Framework, establishing shared terminology and core UTM functions to support safe, harmonized UAS operations. The document purposely excludes role-sharing among entities, technical communication methods between functions, and commercial/business models.
Key topics and requirements
- Classification of UTM functionalities - The standard groups UTM capabilities into core functional categories that underpin safe, scalable UTM systems.
- Core UTM functions (high-level descriptions):
- Registration function - Official recordkeeping for remote pilots, UAs, and operators (qualification, aircraft type, serial numbers, ownership, authorization).
- Flight information management - Exchange of aeronautical information, traffic information and interfaces with Air Traffic Services (ATS) to deconflict manned and unmanned flights.
- Operation plan management - Planning and dynamic management of operation plans (routes, departure/arrival times, and plan changes during flight).
- Position data management - Collection, management and sharing of UA position and status to monitor compliance with plans and generate advisories/alerts.
- Reporting function - Collection and sharing of incident/accident reports for analysis and operational improvement.
- Supplemental data supply - Provision of supporting data such as meteorological and geospatial information.
- Functional structure and interactions - Guidance on relationships between functions to support system design, evaluation and verification.
- Implementation guidance - Recommendations for using the functional structure for procurement, system design, testing and conformance assessment.
- Scope limitations - Excludes detailed communication protocols and business models; refers implementers to ISO 23629-12 for UTM service provider requirements.
Practical applications and users
ISO 23629-5 is intended for:
- UTM service providers designing functional architecture and ensuring compliance with service-level requirements.
- National authorities and regulators harmonizing UTM capabilities and defining geozones, routes and authorization mechanisms.
- UAS operators and manufacturers aligning registration, position-reporting and operation-planning capabilities with a common functional baseline.
- Systems integrators, procurement agencies and testers using the functional structure as a reference for procurement criteria, evaluation, testing and verification.
- Standards bodies and policy makers comparing UTM frameworks and fostering international interoperability.
Related standards
- ISO 23629-12 - Requirements for UTM service providers (referenced for communication services and provider requirements).
- ISO 21384-4 - UAS vocabulary (terms and definitions referenced by ISO 23629-5).
- ISO 23629 series - Other parts of the UTM suite providing complementary guidance.
Keywords: ISO 23629-5:2023, UAS traffic management, UTM functional structure, UTM functions, registration function, flight information management, position data management, operation plan management.
Frequently Asked Questions
ISO 23629-5:2023 is a standard published by the International Organization for Standardization (ISO). Its full title is "UAS traffic management (UTM) - Part 5: UTM functional structure". This standard covers: This document is dedicated to establishing a common understanding of UTM core functions and functional structure. It provides a detailed description of the UTM system layer given in the UTM Framework. This document excludes: - role-sharing among entities constituting UTM, which is left to implementations; - technical methodology of communication or data transaction among core functions; - business model of players engaging in a function of UTM.
This document is dedicated to establishing a common understanding of UTM core functions and functional structure. It provides a detailed description of the UTM system layer given in the UTM Framework. This document excludes: - role-sharing among entities constituting UTM, which is left to implementations; - technical methodology of communication or data transaction among core functions; - business model of players engaging in a function of UTM.
ISO 23629-5:2023 is classified under the following ICS (International Classification for Standards) categories: 49.020 - Aircraft and space vehicles in general. The ICS classification helps identify the subject area and facilitates finding related standards.
You can purchase ISO 23629-5:2023 directly from iTeh Standards. The document is available in PDF format and is delivered instantly after payment. Add the standard to your cart and complete the secure checkout process. iTeh Standards is an authorized distributor of ISO standards.
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 23629-5
First edition
2023-04
UAS traffic management (UTM) —
Part 5:
UTM functional structure
Gestion du trafic des aéronefs sans pilote (UTM) —
Partie 5: Structure fonctionnelle de l'UTM
Reference number
© ISO 2023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
3.1 UTM constituent related terms . 1
3.2 UA operation related terms . 2
4 General recommendations .2
5 Classification of UTM functionalities .3
5.1 Functional categories . 3
5.2 UTM functions . 4
5.2.1 General . 4
5.2.2 Registration function . 4
5.2.3 Flight information management function . 4
5.2.4 Operation plan management function . 5
5.2.5 Position data management function . 6
5.2.6 Reporting function . 6
5.2.7 Supplemental data supply function . 6
6 UTM functional structure . 7
6.1 Functional structure and configuration . 7
6.2 Relationships and interactions among UTM functions . 8
Annex A (informative) Design models comparison of UTM frameworks and approach to
determining UTM functions .10
Bibliography .14
iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use
of (a) patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed
patent rights in respect thereof. As of the date of publication of this document, ISO had not received
notice of (a) patent(s) which may be required to implement this document. However, implementers are
cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents. ISO shall not be held responsible for identifying any or all
such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 20, Aircraft and space vehicles,
Subcommittee SC 16, Unmanned aircraft systems.
A list of all parts in the ISO 23629 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
Introduction
The market expects rapid growth of civil unmanned aircraft system (UAS) operations in the near future.
To manage growing operations, several states are making an effort to develop UAS traffic management
(UTM). However, this can cause a lack of harmonization among countries and affect safety, security, the
environment, system reliability and economic efficiency.
Some organizations have already created models and references of UTM functional structure, for
example, existing documents and ongoing discussion in other organizations such as ASTM to create the
UTM functional structure. These models are recognised to share a lot of common aspects.
To avoid discordance, the creation of a generic UTM functional structure as a basis of further
developments is needed. The reference functional structure can serve as a mechanism to evaluate and
compare different UTM systems and can foster adoption of better technologies and solutions.
The UTM structure and core functions are to be harmonized with the following perspectives:
— creating terms and definitions related to core functions of UTM referencing existing international
standards;
— listing existing documents and ongoing discussion related to UTM functional structure;
— creating a common UTM structure;
— checking contradiction and inconsistency between terms and definition and UTM structure.
v
INTERNATIONAL STANDARD ISO 23629-5:2023(E)
UAS traffic management (UTM) —
Part 5:
UTM functional structure
1 Scope
This document is dedicated to establishing a common understanding of UTM core functions and
functional structure. It provides a detailed description of the UTM system layer given in the UTM
Framework.
This document excludes:
— role-sharing among entities constituting UTM, which is left to implementations;
— technical methodology of communication or data transaction among core functions;
— business model of players engaging in a function of UTM.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 21384-4, Unmanned aircraft systems — Part 4: Vocabulary
ISO 23629-12, UAS traffic management (UTM) — Part 12: Requirements for UTM service providers
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 21384-4, ISO 23629-12 and
the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1 UTM constituent related terms
3.1.1
UTM function
function which constitutes UTM and contributes to safe UA operation
3.1.2
UTM functional structure
UTM structure in functional perspective which consists of mutual complementary and interacting UTM
functions (3.1.1)
3.1.3
registration
making an official record of UA, remote pilot and UA operator by relevant authorities or delegated
entities
3.1.4
UA operation
activity of UA organized to execute a particular mission
3.1.5
flight plan
specified information provided to ATS units, relative to an intended flight or portion of a flight of a
manned aircraft
3.1.6
operation plan
specified information provided to UTM service providers, relative to an intended flight or portion of a
flight of a UA
3.1.7
supplemental data
reference information to conduct safe UA operation (3.1.4) such as geospatial information, meteorological
information and so on
3.2 UA operation related terms
3.2.1
UTM route
reserved airspace where UA with a proper capability and performance are permitted to fly within
3.2.2
UAS geographical zone
volume of airspace defined by the competent authority in which UAS operations are prohibited,
restricted to specific conditions (UA type, specific equipment, effective period, etc.) or authorization by
a geozone manager on a regulatory perspective is required
4 General recommendations
Whilst UTM services are relevant for UTM actors, it is significant to get into the UTM system layer
and to clarify its components for further installation efforts of UTM systems, including evaluation and
verification. This document gives definitions of UTM functions indispensable from the view point of
safety in a manner to enable localization of UTM systems as well. Functions that are not unique to UTM
(for example, communication and database) are not described.
Clause 5 and 6 describe the detailed recommendations.
In Clause 5, classification of UTM functionalities are identified from the perspective of ensuring safety
and to fulfil service layer requirements. Related service providers should comply with requirements
in ISO 23629-12. The high-level functionalities common to UTM systems retain flexibility in designing
system architecture and implementation in accordance with local needs.
In Clause 6, interactions between the UTM functional elements and the UTM functional structure are
provided.
Implementation of UTM systems should consider to include, but not limited to, the UTM functions
described in Clause 5 and to implement the functional structure described in Clause 6 in the following
situations:
— Global efforts to develop UTM systems should use the functional structure for reference purposes,
to resolve certain requirements into their own UTM architectural designs, and to conduct tests and
verifications.
— UTM procurement agencies should use the functional structure as a reference, for procurement
criteria and UTM technology evaluation.
— Possible evaluation/verification frameworks of UTM and any organization willing to evaluate UTM
should use the functional structure for reference purposes, to design conformance criteria for
requirements and compliance to regulations.
5 Classification of UTM functionalities
5.1 Functional categories
UTM functions are identified by reference to available UTM frameworks (see Annex A). UTM is
composed of functional categories as follows:
a) Registration function
To ensure operation of UA with legal authority, the registration function provides a mechanism to
register and share the official record of UA, operator and remote pilot with authorised UTM actors,
including law enforcement agencies. Registration is one of the UTM services which a state authority
may provide directly or which could be delegated to a service provider.
b) Flight information management function
To ensure the safe operation of manned aircraft and UA in the same airspace, flight information
management function exchange information such as flight information, traffic information and
aeronautical information with traffic management system for manned aircraft.
c) Operation plan management function
Operation plan management function supports to set route of flight, departure and arrival times, etc. so
that operations can be carried out safely and efficiently at the planning stage in advance.
The function also supports necessary plan changes when conditions such as weather conditions change
during operation.
d) Position data management function
To support safe operation, the position management function manages the position and status
information provided by the UA, and shares it among UTM actors. In addition, the function confirms
that the operation is being executed correctly as planned, and issues an advisory and alert to UTM
users when a danger such as an accident is foreseen.
e) Reporting function
For analysis when an incident or accident occurs and operational improvement to prevent recurrence of
the accident, the reporting function collects and share the incident or accident report on UA operation
from operators or third parties.
f) Supplemental data supply function
Supplemental data supply function provides UTM actors with supplemental data, such as weather
information and 3D map information to conduct safe and efficient operation.
For all involved exchanges of digital data by utilizing the functions above, a UTM communication
service, identified in ISO 23629-12 is in addition necessary.
5.2 UTM functions
5.2.1 General
For each functional category, UTM functions are identified in the following subclauses.
5.2.2 Registration function
Table 1 shows the detailed description of the registration functions.
Table 1 — Registration functions
Function Description
1-1 Remote pilot registra- Register and manage information about qualification and competency of
tion remote pilot. The information managed by this function could be provided to
appropriate UTM users, such as national authority and police. The information
to be registered and managed, and the provision destination are regulated in
each country according to the specifications of various international standards
and based on laws and regulations.
1-2 UA registration Register and manage information about UA such as manufacturer, type of
aircraft, performance, specifications, aircraft unique serial number, owner,
on-board equipment, etc. The information managed by this function could be
provided to appropriate UTM users, such as national authority and police. The
information to be registered and managed, and the provision destination are
regulated in each country according to the specifications of various interna-
tional standards and based on laws and regulations.
1-3 Operator registration Register and manage information about operator who fly or intend to fly UA.
Such as name of operator, authorization information, etc. The information
managed by this function could be provided to appropriate UTM users, such as
national authority and police. The information to be registered and managed,
and the provision destination are regulated in each country according to the
specifications of various international standards and based on laws and regu-
lations.
5.2.3 Flight information management function
Table 2 shows the detailed description of the flight information management functions.
Table 2 — Flight information management functions
Function Description
2-1 Aeronautical information man- Exchanges information which is necessary for safe UA operation
agement for UA such as vertiport, UTM route, airspace and operational restriction
among UTM/ATM.
2-2 Collaborative interface with ATC Provides UA operators and remote crew member with communica-
tion means to contact ATS services when they intend to fly or enter
into controlled airspaces.
2-3 Airspace organization and man- Design the structure of airspace and manage the usage of airspace to
agement achieve safe and efficient UA operation.
2-3-1 Airspace organization Define the geographical zones where UA activity should be prohib-
ited or restricted. It also designs and establishes the geographical
zones and UTM routes where UA can fly safely. The horizontal and
vertical dimensions of the section of the UTM route and airspace
depend on the navigation performance of the UA in terms of total
system error.
TTaabblle 2 e 2 ((ccoonnttiinnueuedd))
Function Description
2-3-2 Geo-awareness Publish airspace definition information defined by airspace organ
...
기사 제목: ISO 23629-5:2023 - UAS 교통 관리 (UTM) - 파트 5: UTM 기능적 구조 기사 내용: 이 문서는 UTM 핵심 기능과 기능적 구조에 대한 공통된 이해를 확립하는 데 전념하고 있습니다. 이 문서는 UTM 프레임 워크에서 제공하는 UTM 시스템 레이어에 대한 상세한 설명을 제공합니다. 이 문서는 다음 사항을 제외합니다: - UTM을 구성하는 엔티티 간의 역할 분담(구현에 맡김) - 핵심 기능 간의 통신이나 데이터 거래의 기술적 방법론 - UTM 기능을 수행하는 플레이어의 비즈니스 모델
記事のタイトル:ISO 23629-5:2023 - UASトラフィックマネジメント(UTM)- 第5部:UTMの機能構造 記事の内容:この文書は、UTMのコア機能と機能構造についての共通の理解を確立することに捧げられています。 UTMフレームワークで定義されたUTMシステムレイヤーの詳細な説明を提供しています。 この文書は、次の点を除外しています: - UTMを構成するエンティティ間の役割共有(実装に委ねられる)- コア機能間の通信やデータトランザクションの技術的方法論 - UTMの機能を果たすプレイヤーのビジネスモデル
ISO 23629-5:2023 is a document that aims to establish a shared understanding of the core functions and structure of UAS Traffic Management (UTM). It provides a detailed description of the UTM system layer as defined in the UTM Framework. The document does not cover the role-sharing between UTM entities, the technical methodology of communication or data transaction among core functions, or the business model of UTM players. These aspects are left to individual implementations.










Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...