ISO/FDIS 18131

Ships and marine technology — Publish-subscribe architecture on ship-shore data communication — General requirements

This document describes publish-subscribe architecture on ship-shore data communication and is intended for use by stakeholders, such as shipbuilding industry, shipping companies, equipment manufacturers, port and on-shore service providers, to communicate in the publish-subscribe architecture between ship and shore. This document identifies: ― Definition for a role of broker, publisher and subscriber ― Definition for multitenancy-based data management system on cloud environment ― General requirements for a publish-subscribe architecture ― Security requirements for ensuring data confidentiality, integrity and availability ― Configuration for topic naming rule and data structure

Titre manque

General Information

• Status: Not Published
• ICS: 47.020.70 - Navigation and control equipment
• Technical Committee: ISO/TC 8 - Ships and marine technology
• Drafting Committee: ISO/TC 8 - Ships and marine technology
• Current Stage: 5020 - FDIS ballot initiated: 2 months. Proof sent to secretariat
• Start Date: 07-Aug-2025
• Completion Date: 07-Aug-2025

Standards Content (Sample)

FINAL DRAFT
International
Standard
ISO/TC 8/SC 26
Ships and marine technology —
Secretariat: SAC
Publish-subscribe architecture on
Voting begins on:
ship-shore data communication —
2025-08-07
General requirements
Voting terminates on:
2025-10-02
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
FINAL DRAFT
International
Standard
ISO/TC 8/SC 26
Ships and marine technology —
Secretariat: SAC
Publish-subscribe architecture on
Voting begins on:
ship-shore data communication —
General requirements
Voting terminates on:
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO 2025
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland Reference number
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 General requirements for publish-subscribe architecture on ship-shore data
communication . 4
5.1 General .4
5.2 Sequence diagram.5
6 Requirements for security management . 6
6.1 General requirements .6
6.2 Application layer authentication .6
6.3 Authorization for topic permission .8
6.4 Data encryption by transport layer security .8
7 General requirements for message format . 8
7.1 General requirements .8
7.2 Topic name .9
7.2.1 General .9
7.2.2 Topic naming definition .9
7.2.3 Topic name of data type .10
7.3 Data model.14
7.3.1 General .14
7.3.2 Header of data model . 15
7.3.3 Payload of data model . 15
8 Functional requirements for data management.29
8.1 Data backup . 29
8.2 Data recovery . . 29
8.3 Log and event storage management . 29
Annex A (informative) Examples of data taxonomy.30
Bibliography .136

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 8 Ships and marine technology, Subcommittee
SC 26, Smart shipping.
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
Information and Communication Technology (ICT) plays an increasingly important role in assuring effective
and secure data communication in the marine industry. In this context, there is a growing need for an
architecture that not only enables interoperability between applications and systems onboard vessels,
but also supports real-time streaming services within ships. Moreover, data communication between ship
and shore is provided in real time to support decision-making as integrated information by collecting and
analysing data.
In order to expand the usage range between relative entities and to improve the ship's performance, it is
important to standardize the message format transmitted from the ship side server to the shore side server.
Existing International Standards on managing data that are derived from ship or shore have been used in
the industry such as:
— the IEC 61162 series for the digital interfaces of navigational equipment within a ship;
— ISO 19847 for shipboard data servers;
— ISO 19848 for standard data for shipboard machinery and equipment;
— ISO 23807 for asynchronous time-insensitive ship-shore data transmission.
However, it is recommended to establish a message communication system that shall respond flexibly to
the various message formats derived from relevant sectors such as smart shipping, smart ports, smart
logistics, etc. Furthermore, utilizing a communication protocol optimized for satellite communication can be
considered, even in a situation where communication is intermittently disconnected. Furthermore, it should
be highlighted that the data model is designed with scalability to accommodate future expansions related to
eco-friendly technologies and environmental regulations.
This document defines a publish-subscribe architecture to facilitate widespread data utilization. It enables
many-to-many communication by allowing data to be transferred through registered topics. It provides a
dynamic, batch-based messaging structure.
This document provides general requirements for publish-subscribe communication, including security
requirements, topic naming definitions, message format, and functional requirements for data management.

v
FINAL DRAFT International Standard ISO/FDIS 18131:2025(en)
Ships and marine technology — Publish-subscribe
architecture on ship-shore data communication — General
requirements
1 Scope
This document specifies requirements on publish-subscribe architecture on ship-shore data communication.
It is intended for use by system providers and users, including software vendors, platform developers,
fleet managers, application users in the field of the shipbuilding industry, shipping companies, equipment
manufacturers, and port and on-shore service providers, to communicate in the publish-subscribe
architecture between ship and shore.
This document focuses on enabling interoperability of shipboard and shore-based systems for the exchange
of operational data using publish-subscribe methods.
This document describes:
— the role of a broker, publisher and subscriber;
— the multitenancy-based data management system in the cloud environment;
— general requirements for publish-subscribe architecture;
— security requirements for ensuring data confidentiality, integrity and availability;
— the message format for client id and topic name, and data model;
— functional requirements for data management.
2 Normative references
The follow
...

Formatted: Centered
ISO DIS 18131:20242025(en)
Style Definition: Heading 1: Indent: Left: 0 cm, First line:
0 cm, Tab stops: Not at 0.76 cm
ISO TC 8/SC26
Style Definition: Heading 2: Tab stops: Not at 0.63 cm +
0.76 cm
Secretariat: SAC
Style Definition: Heading 3: Tab stops: 1.27 cm, List tab
+ Not at 0.76 cm
Date: 2025-06-1107-23
Style Definition: Heading 4: Tab stops: 1.9 cm, List tab +
Ships and marine technology — Publish-subscribe architecture on ship-shore data Not at 0.76 cm + 1.27 cm
communication — General requirements
Style Definition: Heading 5: Tab stops: 1.9 cm, List tab +
Not at 0.76 cm + 1.27 cm
Style Definition: Heading 6: Tab stops: 2.54 cm, List tab
+ Not at 0.76 cm + 1.27 cm + 1.9 cm
Style Definition: Default Paragraph Font
Style Definition: List Number 1: Tab stops: Not at 0.7 cm
+ 1.4 cm + 2.1 cm + 2.8 cm + 3.5 cm + 4.2 cm + 4.9
cm + 5.6 cm + 6.3 cm + 7 cm
Style Definition: Body Text Indent 2
Style Definition: Body Text Indent 3
Style Definition: a2: Tab stops: 0.63 cm, List tab
Style Definition: a3: Tab stops: 1.27 cm, List tab
Style Definition: a4: Tab stops: 1.9 cm, List tab
Style Definition: a5: Tab stops: 1.9 cm, List tab
Style Definition: a6: Tab stops: 2.54 cm, List tab
Style Definition: ANNEX
Style Definition: zzCopyright
Style Definition: 해시태그1
Style Definition: 멘션1
Style Definition: 스마트 하이퍼링크1
Style Definition: 확인되지 않은 멘션1
Style Definition: AMEND Terms Heading: Tab stops: Not
at 0.76 cm
Style Definition: AMEND Heading 1 Unnumbered: Tab
stops: Not at 0.76 cm
Formatted: English (United States)
Formatted: English (United States)
Formatted: English (United States)
Formatted: Font color: Auto, English (United Kingdom)
Formatted: Font: Bold, Font color: Auto, English (United
Kingdom)
Formatted: Font color: Auto, English (United Kingdom)
Formatted: English (United Kingdom)
Formatted: Centered
ISO/DISFDIS 18131:20242025(en)
Formatted: Indent: Left: 0 cm, Right: 0 cm, Space
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no
Before: 0 pt, No page break before, Adjust space
part of this publication may be reproduced or utilized otherwise in any form or by any means,
between Latin and Asian text, Adjust space between
electronic or mechanical, including photocopying, or posting on the internet or an intranet, without Asian text and numbers
prior written permission. Permission can be requested from either ISO at the address below or
Formatted: Default Paragraph Font
ISO’sISO's member body in the country of the requester.
ISO copyright officeCopyright Office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Formatted: Indent: Left: 0 cm, First line: 0 cm, Right: 0
cm, Adjust space between Latin and Asian text, Adjust
space between Asian text and numbers
Phone: + 41 22 749 01 11
Email: [e-mail]
Email: [e-mail]
Website: www.iso.orgwww.iso.org Formatted: Indent: Left: 0 cm, First line: 0 cm, Right: 0
cm, Adjust space between Latin and Asian text, Adjust
space between Asian text and numbers
Published in Switzerland.
ii
ISO/DISFDIS 18131:20242025(en)
Contents
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Abbreviated terms. 3
5 General Requirements for publish-subscribe architecture on ship-shore data
communication. 4
5.1 A concept of publish-subscribe architecture . 4
5.2 Sequence diagram . 5
6 Requirements for security management . 6
6.1 General requirements . 6
6.2 Application layer authentication . 6
6.3 Authorization for topic permission . 7
6.4 Data encryption by transport layer security . 7
7 General requirements for message format . 7
7.1 General requirements . 7
7.2 Topic name . 8
7.2.1 Topic naming definitions . 8
7.2.2 Topic name of data type . 9
7.3 Data model . 14
7.3.1 Header of data model . 14
7.3.2 Payload of data model . 15
8 Functional requirements for data management . 21
8.1 Data backup . 21
8.2 Data recovery . 21
8.3 Log and event store management . 21
Annex A(informative) Examples of data taxonomy . 22
Bibliography . 206
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms. 3
5 General requirements for publish-subscribe architecture on ship-shore data
communication. 4
5.1 General . 4
Figure 1 — Schematic of ship-shore data communication . 5
5.2 Sequence diagram . 6
iii
ISO/DISFDIS 18131:20242025(en)
Figure 2 — Sequence diagram for data communication flow . 7
6 Requirements for security management . 8
6.1 General requirements . 8
6.2 Application layer authentication . 8
Table 1 — Example of client ID . 8
Figure 3 — Sequence diagram for the authentication process . 10
6.3 Authorization for topic permission . 11
6.4 Data encryption by transport layer security . 11
7 General requirements for message format . 11
7.1 General requirements . 11
Figure 4 — Model of message format. 12
7.2 Topic name . 13
7.2.1 General . 13
7.2.2 Topic naming definition . 13
Table 2 — Example of topic naming definition . 13
7.2.3 Topic name of data type . 14
Table 3 — Topic name of data type . 14
Table 4 — Description of data types . 18
7.3 Data model . 19
7.3.1 General . 19
7.3.2 Header of data model . 19
Table 5 — Description of headers . 19
7.3.3 Payload of data model . 20
Table 6 — Header description for alarm/sensor . 20
Table 7 — Header description for package update request . 21
Table 8 — Header description for package update response . 23
Table 9 — Header description for feedback command request . 24
Table 10 — Header description for feedback command response . 24
Table 11 — Header description for query service (shore to ship) . 25
Table 12 — Header description for query service (ship to shore) . 29
Table 13 — Header description for custom declarations (ship to shore) . 31
8 Functional requirements for data management . 37
8.1 Data backup . 37
8.2 Data recovery . 37
8.3 Log and event storage management . 37
Annex A (informative) Examples of data taxonomy . 38
A.1 Component model . 38
A.2 Model structure . 38
...