oSIST prEN IEC 63281-5-1:2026

• Status: Not Published
• Public Enquiry End Date: 19-Nov-2026
• ICS: 43.120 - Electric road vehicles
• Technical Committee: I11 - Imaginarni 11
• Current Stage: 4020 - Public enquire (PE) (Adopted Project)
• Start Date: 01-Sep-2026
• Due Date: 19-Jan-2027
• Ref Project: prEN IEC 63281-5-1:2026 - Interface requirements of autonomous cargo e-Transporters and cloud platform scheduling system

Overview

oSIST prEN IEC 63281-5-1:2026 sets out the interface requirements for seamless communication between autonomous cargo e-Transporters (ACeTs) and a cloud platform scheduling system. Driven by rapid advancements in electric road vehicles and the increasing adoption of autonomous technologies, this standard provides a unified communication framework to ensure compatibility, interoperability, and operational efficiency. By addressing the technical needs of both hardware manufacturers and software developers, this document promotes safe, standardized and scalable deployment of autonomous cargo transport systems.

Key Topics

• Communication Protocols:
  Specifies that message transmission between ACeTs and the cloud platform should use standardized application-layer protocols, namely MQTT 3.1.1 (ISO/IEC 20922:2016) or HTTP/1.1 (IETF RFC 9112). Messages must be encoded in JSON format (ISO/IEC 21778:2017) for maximum compatibility and efficiency.

• Message Architecture:
  Outlines a robust messaging system that includes structured headers and multiple objects (route, action, state, verification, etc.), each serving distinct functions:

  • Message headers track sender, receiver, version, timestamp, manufacturer, model, and device ID.
  • Dedicated communication objects for key functions including transmission of route instructions, execution feedback, action commands (e.g., fault reset or pause), and status updates.

• Route Management:
  Defines the creation, update, and cancellation mechanisms for transport routes. Route objects describe paths via a series of nodes, each with attributes such as coordinates, direction, speed, and allowable deviation-essential for accurate path planning and execution.

• Autonomous e-Transporter States:
  Provides a clear definition of state reporting, including position, speed, energy level, charging status, control mode, and any faults detected. This supports real-time monitoring and enhances operational safety.

• Granularity and Adaptability:
  Ensures the interface supports varying levels of transporter autonomy by allowing scalable node definition along transport routes.

Applications

oSIST prEN IEC 63281-5-1:2026 is crucial for stakeholders in the autonomous freight and logistics industry looking to:

• Develop Connected Autonomous Vehicles:
  Enables manufacturers to implement cloud-compatible ACeTs that can safely and effectively interact with scheduling systems using globally recognized data formats and protocols.

• Optimize Logistics and Fleet Operations:
  Assists logistics providers in managing and routing autonomous fleets efficiently, ensuring timely delivery, higher resource utilization, and reduced operational risks.

• Integrate Heterogeneous Systems:
  Offers a uniform interface to connect ACeTs from different manufacturers to a centralized scheduling cloud, facilitating interoperability and simplified deployment for public roads, industrial parks, warehouses, and urban delivery networks.

• Enhance Safety and Compliance:
  By defining standardized feedback and exception handling messages, the standard supports continuous compliance with evolving safety and operational regulations.

Related Standards

Organizations and professionals using this standard should also consult these related documents:

• IEC 63281-1:2023: E-Transporters - Terminology and classification
• IEC 63281-2-2: Safety requirements and test methods for autonomous cargo e-Transporters
• ISO/IEC 20922:2016: Message Queuing Telemetry Transport (MQTT) v3.1.1
• ISO/IEC 21778:2017: The JSON data interchange syntax
• IETF RFC 9112: HTTP/1.1
• Additional references and examples are included within the standard to facilitate implementation.

By adhering to oSIST prEN IEC 63281-5-1:2026, stakeholders can ensure interoperability, reliability, and future-readiness of their autonomous cargo transport solutions. This contributes to safer, smarter, and more efficient electric road vehicle ecosystems driven by international best practices.

SLOVENSKI STANDARD
01-november-2026
Zahteve za vmesnike avtonomnih tovornih e-prevoznikov in oblačnega sistema za
razporejanje prometa
Interface requirements of autonomous cargo e-Transporters and cloud platform
scheduling system
Ta slovenski standard je istoveten z: prEN IEC 63281-5-1:2026
ICS:
43.120 Električna cestna vozila Electric road vehicles
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

125/134/CDV
COMMITTEE DRAFT FOR VOTE (CDV)
PROJECT NUMBER:
IEC 63281-5-1 ED1
DATE OF CIRCULATION: CLOSING DATE FOR VOTING:
2026-08-28 2026-11-20
SUPERSEDES DOCUMENTS:
125/129/CD, 125/132/CC
IEC TC 125 : E-TRANSPORTERS
SECRETARIAT: SECRETARY:
Belgium Mr Bram Rotthier
OF INTEREST TO THE FOLLOWING COMMITTEES: HORIZONTAL FUNCTION(S):

ASPECTS CONCERNED:
SUBMITTED FOR CENELEC PARALLEL VOTING NOT SUBMITTED FOR CENELEC PARALLEL VOTING
Attention IEC-CENELEC parallel voting
The attention of IEC National Committees, members of
CENELEC, is drawn to the fact that this Committee Draft for
Vote (CDV) is submitted for parallel voting.
The CENELEC members are invited to vote through the
CENELEC online voting system.
This document is still under study and subject to change. It should not be used for reference purposes.
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which
they are aware and to provide supporting documentation.
Recipients of this document are invited to submit, with their comments, notification of any relevant “In Some Countries”
clauses to be included should this proposal proceed. Recipients are reminded that the CDV stage is the final stage for
submitting ISC clauses. (SEE AC/22/2007 OR NEW GUIDANCE DOC).

TITLE:
Interface requirements of autonomous cargo e-Transporters and cloud platform scheduling system

PROPOSED STABILITY DATE: 2030
NOTE FROM TC/SC OFFICERS:
electronic file, to make a copy and to print out the content for the sole purpose of preparing National Committee positions.
You may not copy or "mirror" the file or printed version of the document, or any part of it, for any other purpose without
permission in writing from IEC.

Link to Committee Draft for Vote (CDV) online document:
Click here
How to access
This link leads you to the Online Standards Development (OSD) platform for National Mirror Committee’s
(NMC) comments. The project draft may be found further down this document.

Resource materials
We recommend NCs to review the available materials to better understand the member commenting on the
OSD platform. This includes the:
• OSD NC roles overview
• How to add and submit comments to the IEC

Contact
Should you require any assistance, please contact the IEC IT Helpdesk.

IEC CDV 63281-5-1 © IEC 2026
CONTENTS
Contact . 2
CONTENTS . 1
FOREWORD . 3
INTRODUCTION . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 6
4 Basic specifications . 8
4.1 Overall Architecture . 8
4.1.1 General . 8
4.1.2 Information Flow . 8
5 Message format . 9
5.1 Message Header . 9
5.2 Communication Object . 9
5.3 Route Object . 10
5.3.1 Explanation of Route Mechanism . 10
5.3.2 Format of Route Object . 11
5.4 Action Object . 12
5.4.1 Description . 12
5.4.2 Format of Action Object . 13
5.5 RouteState Object . 13
5.5.1 Description . 13
5.5.2 Format of RouteState Object . 13
5.6 RouteVerificationState Object . 14
5.6.1 Description . 14
5.6.2 Format of RouteVerificationState Object . 14
5.7 State Object . 14
5.7.1 Description . 14
5.7.2 Format of State Object. 14
Annex A (normative) Message example . 16
A.1 Example of new Route . 16
A.2 Example of updating Route . 16
A.3 Example of State . 17
A.4 Example of RouteState . 18
A.5 Example of Action PauseRoute . 18
Bibliography . 19

Figure 1 – Information Flow . 9
Figure 2 – Nodes in a route . 10
Figure 3 – Route update diagram . 11

Table 1 – Message head . 9
Table 2 – Communication Object . 9
Table 3 – Structure of Route . 11
Table 4 – Structure of node . 12
IEC CDV 63281-5-1 © IEC 2026
Table 5 – Structure of Action Object . 13
Table 6 – Optional values of actionType . 13
Table 7 – Structure of nodeSequenceId . 13
Table 8 – Structure of RouteState Object . 13
Table 9 – Structure of RouteCheckState Object . 14
Table 10 – Structure of State Object . 14
Table 11 – Structure of fault. 15

IEC CDV 63281-5-1 © IEC 2026
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
Interface requirements of autonomous cargo e-Transporters and cloud
platform scheduling system
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for
standardization comprising all national electrotechnical committees (IEC National Committees).
The object of IEC is to promote international co-operation on all questions concerning
standardization in the electrical and electronic fields. To this end and in addition to other
activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as "IEC
Publication(s)"). Their preparation is entrusted to technical committees; any IEC National
Committee interested in the subject dealt with may participate in this preparatory work.
International, governmental and non-governmental organizations liaising with the IEC also
participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two
organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as
possible, an international consensus of opinion on the relevant subjects since each technical
committee has representation from all interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted
by IEC National Committees in that sense. While all reasonable efforts are made to ensure that
the technical content of IEC Publications is accurate, IEC cannot be held responsible for the
way in which they are used or for any misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC
Publications transparently to the maximum extent possible in their national and regional
publications. Any divergence between any IEC Publication and the corres ponding national or
regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies
provide conformity assessment services and, in some areas, access to IEC marks of conformity.
IEC is not responsible for any services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including
individual experts and members of its technical committees and IEC National Committees for
any personal injury, property damage or other damage of any nature whatsoever, whether direct
or indirect, or for costs (including legal fees) and expenses arising out of the publication, use
of, or reliance upon, this IEC Publication or any other IEC Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced
publications is indispensable for the correct application of this publication.
9) IEC draws attention to the possibility that the implementation of this document may involve
the use of (a) patent(s). IEC 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,
IEC had 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
IEC CDV 63281-5-1 © IEC 2026
may be obtained from the patent database available at https://patents.iec.ch or 9) IEC draws
attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). IEC 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, IEC had 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 https://patents.iec.ch or www.iso.org/patents.
IEC shall not be held responsible for identifying any or all such patent rights. . IEC shall not be
held responsible for identifying any or all such patent rights.
IEC 6XXXX has been prepared by IEC technical committee 125: e-Transporters. It is an
International Standard.
The text of this International Standard is based on the following documents:
Draft Report on voting
XX/XX/FDIS XX/XX/RVD
Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this International Standard is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1 and ISO/IEC Directives, IEC Supplement, available
at www.iec.ch/members_experts/refdocs. The main document types developed by IEC are
described in greater detail at www.iec.ch/publications.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under webstore.iec.ch in the data related to the
specific document. At this date, the document will be
– reconfirmed,
– withdrawn, or
– revised.
IEC CDV 63281-5-1 © IEC 2026
INTRODUCTION
Standardization of "autonomous cargo e-Transporters": autonomous cargo electrically powered
transport devices for use on public roads or in public spaces. These e-Transporters provide
solutions for transporting goods.
These devices should be autonomous.
This document has been developed in response to an increased demand throughout the world
for Autonomous Cargo e-Transporters. The world market sizes and applications are expected
to grow significantly. To date, autonomous cargo e-Transporters have not had a complete and
unified standard of interface with cloud platform scheduling system. This has created
challenges for engineers, producers, operators, and other actors in the field of autonomous
cargo e-Transporters. The development of an interface standard applicable to autonomous
cargo e-Transporters, will promote the standardization of autonomous cargo e-Transporters,
aid the progress of technology, improve product quality, and increase safety.
IEC CDV 63281-5-1 © IEC 2026
1 Scope
This document specifies the communication protocol for the interface between autonomous
cargo e-Transporters as defined by IEC 63281-2-2 and cloud platform scheduling system,
including technical requirements such as message format, message transmission met hod.
This document mainly describes the communication protocol of the autonomous cargo e -
Transporters in terms of driving, including the creation, update, and cancellation of path
instructions issued by the cloud platform scheduling system, as well as the statu s feedback of
the autonomous cargo e-Transporters when executing path instructions and basic exception
handling messages.
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.
IEC 63281-1:2023, E-Transporters - Part 1: Terminology and classification
ISO/IEC 20922:2016, Information technology — Message Queuing Telemetry Transport
(MQTT) v3.1.1
ISO/IEC 21778:2017, Information technology — The JSON data interchange syntax
IEC 63281-2-2: E-Transporters – Part 2-2: Safety requirements and test methods for
autonomous cargo e-Transporters
IETF RFC 9112, HTTP/1.1
3 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 63281-1:2023 and
the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
– IEC Electropedia: available at https://www.electropedia.org/
– ISO Online browsing platform: available at https://www.iso.org/obp
3.1
e-Transporter
electrically powered transport device for use on public roads or in public spaces which provides
solutions for transporting either passengers or goods, or both
[SOURCE: SOURCE: IEC 63281-1:2023, 3.2]
3.2
autonomous e-Transporter
e-Transporter that can operate in autonomous driving mode or semi-autonomous driving mode,
and it drives within defined operational preconditions such as ODDa (IEC 63281-2-2, 3.6)

[SOURCE: SOURCE: IEC 63281-2-2 , 3.2]
IEC CDV 63281-5-1 © IEC 2026
3.3
cargo e-Transporter (CeT)
e-Transporter that is primarily designed for transporting cargo or goods, or both
[SOURCE: IEC 63281-1:2023, 3.4]
3.4
autonomous cargo e-Transporter(ACeT)
autonomous e-transporters traveling without human intervention in carrying loads of parcels
and goods to designated locations including public road environments and public spaces (e.g.,
walkway, pedestrian road, big building's corridors) coexisting with unspecified humans with a
maximum speed not exceeding specified limit

Note 1 to entry: Even if in case of over the operational preconditions, an authorized users can operate remotely for
the ACeTs manually via an external systems or supplementary telecommunication control devices.
[SOURCE: IEC 63281-2-2, 3.4]
3.5
cloud platform scheduling system
cloud platform
Cloud
software system deployed in public/private networks, providing full-lifecycle management and
scheduling for ACeT—including real-time operating status monitoring, intelligent task
assignment, and overall transportation efficiency optimization
3.6
instruction
data collection for communication between ACeTs and cloud platform scheduling system, used
to guide and regulate the operation of ACeTs
3.7
route
instruction to move the ACeT along the path, consisting of a series of nodes forming a straight
line or curve, describing complete information from the starting point to the endpoint
3.8
HTTP/1.1
HyperText Transfer Protocol version 1.1
Note 1 to entry: HTTP/1.1 is a stateless application-level request/response protocol for distributed, collaborative
hypermedia information systems.
Note 2 to entry: In this document, “HTTP” means HTTP/1.1 unless otherwise specified.
[SOURCE: IETF RFC 9112]
3.9
MQTT v3.1.1
Message Queuing Telemetry Transport version 3.1.1
Note 1 to entry: MQTT v3.1.1 is a lightweight client-server publish/subscribe messaging transport protocol for
machine-to-machine (M2M) and Internet of Things (IoT) applications.
[SOURCE: ISO/IEC 20922:2016]
3.10
JSON
JavaScript Object Notation
IEC CDV 63281-5-1 © IEC 2026
Note 1 to entry: JSON is a lightweight, text-based, language-independent data interchange syntax.
Note 2 to entry: This syntax is consistent with IETF RFC 8259
...