Ships and marine technology — General requirements for the asynchronous time-insensitive ship-shore data transmission

This document describes the requirements involved in ship to shore data communication between the shipboard data servers and the on-shore data servers. It provides information on: — asynchronous communication; — a method to measure end-to-end communication quality; — transport integrity; — transport security (e.g. encryption, authentication and authorization); — management of data transmission (e.g. prioritization, logging, carrier awareness/management); — communication optimization (e.g. deduplication, compression, resume, multiplexing); — compliance with the data communication protocols, including but not limited to ISO 19847. This document does not cover: — the security of the data producer/consumer (e.g. identity management); — communication equipment requirements; — carrier performance requirements (e.g. bandwidth and latency).

Titre manque

General Information

Status
Published
Publication Date
05-Mar-2023
Current Stage
6060 - International Standard published
Start Date
06-Mar-2023
Due Date
24-Mar-2023
Completion Date
06-Mar-2023
Ref Project

Buy Standard

Standard
ISO 23807:2023 - Ships and marine technology — General requirements for the asynchronous time-insensitive ship-shore data transmission Released:3/6/2023
English language
15 pages
sale 15% off
Preview
sale 15% off
Preview
Draft
REDLINE ISO 23807 - Ships and marine technology — General requirements for the asynchronous time-insensitive ship-shore data transmission Released:1/11/2023
English language
15 pages
sale 15% off
Preview
sale 15% off
Preview
Draft
ISO 23807 - Ships and marine technology — General requirements for the asynchronous time-insensitive ship-shore data transmission Released:1/11/2023
English language
15 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 23807
First edition
2023-03
Ships and marine technology —
General requirements for the
asynchronous time-insensitive ship-
shore data transmission
Reference number
ISO 23807:2023(E)
© ISO 2023
---------------------- Page: 1 ----------------------
ISO 23807:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© 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
© ISO 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 23807:2023(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction .................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ..................................................................................................................................................................................... 1

3 Terms and definitions .................................................................................................................................................................................... 1

4 Abbreviated terms ............................................................................................................................................................................................. 2

5 General requirements .................................................................................................................................................................................... 3

5.1 General ........................................................................................................................................................................................................... 3

5.2 Encryption .................................................................................................................................................................................................. 4

5.3 Compression ............................................................................................................................................................................................. 4

5.4 Deduplication ........................................................................................................................................................................................... 4

5.5 Distribution ............................................................................................................................................................................................... 5

5.6 Recovery ....................................................................................................................................................................................................... 5

6 Data transport agent — vessel side interface ....................................................................................................................... 5

6.1 General ......................................................................................................................................................................................................... 5

6.2 Transportation folders .................................................................................................................................................................... 5

6.3 File move and sync .............................................................................................................................................................................. 5

6.3.1 Moving files ............................................................................................................................................................................. 5

6.3.2 Synchronizing folders .................................................................................................................................................... 5

6.4 Server message block ....................................................................................................................................................................... 5

6.5 Asynchronous message service .............................................................................................................................................. 6

6.6 API ........................................................................................................................................... ........................................................................... 6

7 Data transport agent — shore side interface ........................................................................................................................ 6

8 Requirements for asynchronous data management agent ..................................................................................... 6

8.1 General ......................................................................................................................................................................................................... 6

8.2 Size restrictions ..................................................................................................................................................................................... 6

8.3 Prioritization of data ......................................................................................................................................................................... 7

8.4 Carrier status ........................................................................................................................................................................................... 7

8.5 On-demand data request ............................................................................................................................................................... 7

8.6 Delayed transmission ....................................................................................................................................................................... 7

8.7 Resume on interrupt ......................................................................................................................................................................... 7

8.8 Monitoring .................................................................................................................................................................................................. 7

9 Requirements for security of data transmission .............................................................................................................. 8

9.1 General ......................................................................................................................................................................................................... 8

9.2 Transport security .............................................................................................................................................................................. 8

9.3 Data security ............................................................................................................................................................................................ 8

Annex A (informative) Correlation chart .....................................................................................................................................................10

Annex B (informative) Functions of asynchronous data management agent .......................................................11

Annex C (informative) HTTP file input and output protocol used on the data transport agent .......13

Bibliography .............................................................................................................................................................................................................................15

iii
© ISO 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO 23807:2023(E)
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 documents 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).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www.iso.org/patents).

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.

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.
© ISO 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 23807:2023(E)
Introduction

Sharing data between ships and the shore to ensure the safe and efficient operation of ships is becoming

increasingly common.

Progress has been made in establishing data sharing between ships and the shore, related to ports,

cargo and shipping routes. This includes the development of and discussions around standards related

to Maritime Single Window and e-Navigation, which help to share some stylized data safely and in a

timely manner between ships and shore.

On the other hand, the ship-shore communication environment is still narrower than those on land,

and its connection is unstable. Therefore, a method for stably and efficiently sharing files of any format

with a relatively large file size, such as various data and image files used in ship operation business

applications, between ships and shore has not yet been standardized.

For example, in ship operations, onboard and on-shore application users determine the timing of data

transmission and reception in relation to the connection status and communication quality of ship-

shore communication each time, and perform data retransmission processing independently for each

application.

In order to further promote the safe and efficient operation of ships, it is increasingly important to be

able to send and receive files between ships and shore in a stable and efficient manner asynchronously

without being affected by the ship-shore communication status.

In this document, asynchronous communication means the communication and/or application

processing perspective, such as time-insensitive data transmission for non-real-time applications

where the timing of the data generating and consuming can be different.

Although ISO 19847 and ISO 19848 provide standardized processes for efficient collection and

storage of data for ship equipment systems, the method of asynchronously transmitting and receiving

a large amount of ship equipment data accumulated on board between ships and shore has not been

standardized yet. In order to promote shore support for ship operation and maintenance of onboard

equipment systems, there is a need for a stable and efficient method for transmitting and receiving

such onboard field data asynchronously between ships and shore.

This document specifies the functional requirements but does not intend to specify technical protocols.

See Annex A for more information on the correlation between the different relevant standards.

© ISO 2023 – All rights reserved
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 23807:2023(E)
Ships and marine technology — General requirements
for the asynchronous time-insensitive ship-shore data
transmission
1 Scope

This document describes the requirements involved in ship to shore data communication between the

shipboard data servers and the on-shore data servers. It provides information on:

— asynchronous communication;
— a method to measure end-to-end communication quality;
— transport integrity;
— transport security (e.g. encryption, authentication and authorization);

— management of data transmission (e.g. prioritization, logging, carrier awareness/management);

— communication optimization (e.g. deduplication, compression, resume, multiplexing);

— compliance with the data communication protocols, including but not limited to ISO 19847.

This document does not cover:
— the security of the data producer/consumer (e.g. identity management);
— communication equipment requirements;
— carrier performance requirements (e.g. bandwidth and latency).
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/IEC 20922, Information technology — Message Queuing Telemetry Transport (MQTT) v3.1.1

3 Terms and definitions
For the purposes of this document, the following terms and definitions 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
asynchronous communication

time-insensitive data transmission for onboard applications that transmit ship data and/or non-real-

time applications where the timing of the data generating and consuming can be different

Note 1 to entry: This definition is not from the data protocol perspective.
© ISO 2023 – All rights reserved
---------------------- Page: 6 ----------------------
ISO 23807:2023(E)
Note 2 to entry: ISO 19847 is an example of an onboard application.

Note 3 to entry: The scope of the definition of asynchronous communication in this document covers messaging

services such as message queueing telemetry transport and similar protocols but not streaming using datagram

protocol.

Note 4 to entry: Table 1 compares the definition of synchronous and asynchronous communication.

Table 1 — Intentions regarding synchronous/asynchronous in this document
Communication/application perspective
Synchronous The receiver sends a response, and the sender waits for the re-
sponse before sending the next data.
Asynchronous The receiver sends a response, and the sender sends the next data
without waiting for the response.
3.2
data transport agent

software installed on a ship or shore that interfaces with peripheral devices and systems

Note 1 to entry: The data transport agent collects and sends data to the asynchronous data management agent

(3.3), or receives data from the asynchronous data management.
3.3
asynchronous data management agent

software used for the control and transport of data between ship and shore data transport agent (3.2)

4 Abbreviated terms
AES advanced encryption standard
AES-CCM AES-counter with cipher block chaining-message authentication code
AES-GCM AES-galois/counter mode
API application programming interface
BIZ-LAN business local area network
ChaCha20 a stream cipher specified in RFC 8439
ChaCha20-Poly1305 a cryptographic algorithm that combines ChaCha20 and Poly1305
DH Diffie-Hellman key exchange algorithm
DHE Diffie-Hellman Ephemeral key exchange algorithm
DMZ DeMilitarized Zone
ECDH elliptic curve Diffie–Hellman key exchange algorithm
ECDHE elliptic curve Diffie–Hellman ephemeral key exchange algorithm
ECDSA elliptic curve digital signature algorithm
F/W firewall
GraphQL query language and runtime designed for APIs
HTTP hypertext transfer protocol
© ISO 2023 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 23807:2023(E)
IoT Internet of things
LAN local area network
MQTT message queueing telemetry transport
OT operational technology
Poly1305 a cryptographic message authentication mode specified in RFC 8439

PSEC-KEM provably secure elliptic curve encryption with key encapsulation mechanisms

REST REpresentational state transfer
RSASSA-PKCS1-v1_5 a digital signature algorithm specified in RFC 8017
RSASSA-PSS a digital signature algorithm specified in RFC 8017
SHA-256 secure hash algorithm-256
SHA-384 secure hash algorithm-384
SHA-512 secure hash algorithm-512
TCP transmission control protocol
TLS1.3 transport layer security version 1.3
UDP user datagram protocol

UR E22 International Association of Classification Societies (IACS) Unified Requirement

Electrical and Electronic Installations 22
UTM unified threat management
VSAT very small aperture terminal
5 General requirements
5.1 General

Communication between shore and ship are usually initiated from the vessel side. The vessel in most

cases has a random IP address and it is difficult to change the firewall rules to allow traffic from shore

sites. It is both easier and safer to initiate the communication link from behind the firewall, meaning

that the vessel shall initiate the contact with shore. The same is true for shore sites, such as ship

managers office locations. These locations should be considered a client side location, and should be

responsible for initiating the communication link to a common centre resource such as the cloud server

or the on-premises.
Figure 1 shows the overall picture of this document.
© ISO 2023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO 23807:2023(E)
Figure 1 — Image of asynchronous transmission

Asynchronous communication is used on all communication where data can be transmitted

intermittently.

It shall be applied to narrow-band and unstable ship-shore communication to exchange various types

of data such as documents, media files, sensor data and machine-to-machine communication, and shall

be applied to transferring the onboard server data. Best effort, variable bit rate and communication at

regular intervals utilize spare capacity on an available carrier. Such communication shall comply with

the requirements in 5.2, 5.3, 5.4, 5.5 and 5.6.

A single agent, or multiple agents, can be used to service multiple data formats.

5.2 Encryption

All traffic shall use appropriate encryption as dictated by the sensitivity of the data.

5.3 Compression

The content shall be compressed whenever the compressed size is significantly smaller than the

raw data. The compression algorithm used shall be optimal for the intended use of the data, and not

necessarily what provides the highest compression.
5.4 Deduplication

Transferring a large amount of data can have significant bandwidth savings by using proper

deduplication. The deduplication protocol divides sending data into chunks and tracks their progress.

The chunk size used in deduplication is not a fixed size and can be from 2K to 32K in size. For small data

transfers, the overhead for the control traffic for deduplication can be bigger than the data itself. In

such cases, deduplication should be avoided and any file below 2KB in size shall not be split into parts.

Files larger than 2KB can be split into parts for deduplication, depending on the structure of the file.

The deduplication protocol recognizes data blocks already available on the destination client, and only

sends blocks not already on the client. This is true even for binary encoded data whenever the content

can be shared among other communication data. For example, binary docker images greatly benefit

from deduplication due to the layers inherent in such an image. These layers are shared between

multiple docker images.
© ISO 20
...

INTERNATIONAL STANDARD
Style Definition: Normal

ISO/DIS 23807:2023(E) Style Definition: Heading 1: Indent: Left: 0 pt, First line:

0 pt, Tab stops: Not at 21.6 pt
2022-08-15
Style Definition: Base_Heading
Date: 2023-01-11
Style Definition: List Number 1: Tab stops: Not at 19.85
ISO TC 8
pt + 39.7 pt + 59.55 pt + 79.4 pt + 99.25 pt + 119.05
pt + 138.9 pt + 158.75 pt + 178.6 pt + 198.45 pt
Secretariat: SAC
Style Definition: Base_Text

Ships and marine technology — General requirements for the asynchronous time-insensitive

Style Definition: List Number: Tab stops: Not at 18 pt
ship-shore data transmission
Style Definition: Block Text
Style Definition: TOC 3: Font: Bold
Style Definition: TOC 2
Style Definition: Footer
Style Definition: Header
Style Definition: Subtitle
Style Definition: Normal (Web)
Style Definition: a2: Tab stops: 18 pt, List tab
Style Definition: a3: Tab stops: 36 pt, List tab
Style Definition: a4: Tab stops: 54 pt, List tab
Style Definition: a5: Tab stops: 54 pt, List tab
Style Definition: a6: Tab stops: 72 pt, List tab
Style Definition: ANNEX
Style Definition: zzCopyright
Style Definition: Revision1
Style Definition: AMEND Terms Heading: Font: Bold,
Pattern: 15%
Style Definition: AMEND Heading 1 Unnumbered: Font:
Bold, Pattern: 15%
Style Definition: Hashtag1
Style Definition: Intense Quote
Style Definition: Mention1
Style Definition: No Spacing
Style Definition: Quote
Style Definition: Smart Hyperlink1
Style Definition: Subtle Emphasis1
Style Definition: Subtle Reference1
Style Definition: Unresolved Mention1
Formatted: Different first page header
Formatted: Don't adjust space between Latin and Asian
text, Don't adjust space between Asian text and numbers
---------------------- Page: 1 ----------------------
ISO/DIS 23807:20222023(E)
© ISO 202#, Published in Switzerland2023
Formatted: No page break before
Formatted: Default Paragraph Font

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’sISO's member body in the country of the requester.
ISO copyright officeCopyright Office
Ch. de Blandonnet 8 • CP 401
• CH-1214 Vernier, Geneva, Switzerland
Tel.Phone: + 41 22 749 01 11
Fax + 41 22 749 09 47
copyright@iso.org
www.iso.org
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland.
Formatted: Font: 11 pt
Formatted: Line spacing: single
2 © ISO 2022 – All rights reserved
ii © ISO 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/DIS 23807:20222023(E)
Formatted: Tab stops: 451.7 pt, Left
Contents

Foreword .......................................................................................................................................................................... v

Introduction.................................................................................................................................................................... vi

1 Scope .................................................................................................................................................................... 1

2 Normative references .................................................................................................................................... 1

3 Terms and definitions .................................................................................................................................... 1

4 Abbreviations and Symbols ......................................................................................................................... 2

5 General Requirements for Asynchronous time-insensitive ship-shore data

transmission ..................................................................................................................................................... 3

5.1 General requirements ................................................................................................................................... 3

5.2 Encryption .......................................................................................................................................................... 4

5.3 Compression ...................................................................................................................................................... 4

5.4 Deduplication ................................................................................................................................................... 4

5.5 Distribution ....................................................................................................................................................... 5

5.6 Recovery ............................................................................................................................................................. 5

6 Data transport agent - Vessel side interface .......................................................................................... 5

6.1 General requirements ................................................................................................................................... 5

6.2 Transportation Folders ................................................................................................................................. 5

6.3 File move and sync .......................................................................................................................................... 5

6.3.1 Moving files ........................................................................................................................................................ 5

6.3.2 Synchronizing folders .................................................................................................................................... 5

6.4 SMB ....................................................................................................................................................................... 5

6.5 Asynchronous message service .................................................................................................................. 6

6.6 API ......................................................................................................................................................................... 6

7 Data transport agent - Shore side interface ........................................................................................... 6

8 Requirements for Asynchronous data management agent .............................................................. 6

8.1 General requirements ................................................................................................................................... 6

8.2 Size restrictions ............................................................................................................................................... 7

8.3 Prioritization of data ...................................................................................................................................... 7

8.4 Carrier status .................................................................................................................................................... 7

8.5 On-demand Data Request ............................................................................................................................. 7

8.6 Delayed transmission .................................................................................................................................... 7

8.7 Resume on interrupt ...................................................................................................................................... 7

8.8 Monitoring ......................................................................................................................................................... 7

Formatted: Font: 11 pt

9 Requirements for security of data transmission ................................................................................. 8

Formatted: Line spacing: single
© ISO 2022 – All rights reserved 3
© ISO 2023 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/DIS 23807:20222023(E)

9.1 General requirements ................................................................................................................................... 8

9.2 Transport security .......................................................................................................................................... 8

9.3 Data security ..................................................................................................................................................... 9

Annex A (informative) Correlation Chart .......................................................................................................... 10

A.1 General ............................................................................................................................................................. 10

Annex B (informative) Functions of Asynchronous data management agent ...................................... 11

B.1 General ............................................................................................................................................................. 11

B.2 Expressions ..................................................................................................................................................... 11

B.3 Clients registration ...................................................................................................................................... 11

B.4 Task configuration ....................................................................................................................................... 11

B.4.1 Create task ...................................................................................................................................................... 11

B.4.2 Modify task ..................................................................................................................................................... 12

B.4.3 Activate/Deactiovate task ......................................................................................................................... 12

B.4.4 Remove task ................................................................................................................................................... 12

Annex C (Informative) HTTP File input and output protocol to be used on the data transport

agent .................................................................................................................................................................. 13

C.1 General ............................................................................................................................................................. 13

C.2 Access control ................................................................................................................................................ 13

C.3 Protocol specification ................................................................................................................................. 13

C.4 Encryption ....................................................................................................................................................... 14

Bibliography ................................................................................................................................................................. 16

Foreword ......................................................................................................................................................................... iv

Introduction..................................................................................................................................................................... v

1 Scope .................................................................................................................................................................... 1

2 Normative references .................................................................................................................................... 1

3 Terms and definitions .................................................................................................................................... 1

4 Abbreviated terms .......................................................................................................................................... 2

5 General requirements ................................................................................................................................... 3

5.1 General ................................................................................................................................................................ 3

5.2 Encryption .......................................................................................................................................................... 5

5.3 Compression ...................................................................................................................................................... 5

5.4 Deduplication ................................................................................................................................................... 5

5.5 Distribution ....................................................................................................................................................... 5

5.6 Recovery ............................................................................................................................................................. 5

6 Data transport agent — vessel side interface ....................................................................................... 5

6.1 General ................................................................................................................................................................ 5

6.2 Transportation folders .................................................................................................................................. 6

6.3 File move and sync .......................................................................................................................................... 6

6.3.1 Moving files ........................................................................................................................................................ 6

Formatted: Font: 11 pt

6.3.2 Synchronizing folders .................................................................................................................................... 6

6.4 Server message block ..................................................................................................................................... 6 Formatted: Line spacing: single

4 © ISO 2022 – All rights reserved
iv © ISO 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/DIS 23807:20222023(E)

6.5 Asynchronous message service .................................................................................................................. 6

6.6 API ......................................................................................................................................................................... 6

7 Data transport agent — shore side interface ........................................................................................ 7

8 Requirements for asynchronous data management agent .............................................................. 7

8.1 General ................................................................................................................................................................ 7

8.2 Size restrictions ............................................................................................................................................... 7

8.3 Prioritization of data ...................................................................................................................................... 7

8.4 Carrier status .................................................................................................................................................... 7

8.5 On-demand data request .............................................................................................................................. 8

8.6 Delayed transmission .................................................................................................................................... 8

8.7 Resume on interrupt ...................................................................................................................................... 8

8.8 Monitoring ......................................................................................................................................................... 8

9 Requirements for security of data transmission ................................................................................. 8

9.1 General ................................................................................................................................................................ 8

9.2 Transport security .......................................................................................................................................... 9

9.3 Data security ..................................................................................................................................................... 9

Annex A (informative) Correlation chart .......................................................................................................... 11

Annex B (informative) Functions of asynchronous data management agent ..................................... 13

Annex C (informative) HTTP file input and output protocol used on the data transport

agent .................................................................................................................................................................. 15

Bibliography ................................................................................................................................................................. 18

Formatted: Font: 11 pt
Formatted: Line spacing: single
© ISO 2022 – All rights reserved 5
© ISO 2023 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/DIS 23807:20222023(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards Formatted: English (United Kingdom)

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

Formatted: Don't adjust space between Latin and Asian

through ISO technical committees. Each member body interested in a subject for which a technical

text, Don't adjust space between Asian text and numbers

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 documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directiveswww.iso.org/directives). Formatted: English (United Kingdom)

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any

patent rights identified during the development of the document will be in the Introduction and/or on

the ISO list of patent declarations received (see www.iso.org/patentswww.iso.org/patents).

Formatted: English (United Kingdom)

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.htmlwww.iso.org/iso/foreword.html.
Formatted: English (United Kingdom)

This document was prepared by Technical Committee ISO/TC 8, Ships and marine technology.

Any feedback or questions on this document should be directed to the user’s national standards body. A Formatted: English (United Kingdom)

complete listing of these bodies can be found at
www.iso.org/members.html.www.iso.org/members.html.
Formatted: English (United Kingdom)
Formatted: Don't adjust space between Latin and Asian
text, Don't adjust space between Asian text and numbers
Formatted: Font: 11 pt
Formatted: Line spacing: single
6 © ISO 2022 – All rights reserved
vi © ISO 2023 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/DIS 23807:20222023(E)
Introduction

Sharing data between ships and the shore to ensure the safe and efficient operation of ships is becoming

increasingly common.

Progress has been made in establishing data sharing between ships and the shore, related to ports, cargo

and shipping routes. This includes the development of and discussions around standards such asrelated

to Maritime Single Window and e-Navigation, which help to share some stylized data safely and in a

timely manner between ships and shore.

On the other hand, the ship-shore communication environment is still narrower than those on land, and

its connection is unstable. Therefore, a method for stably and efficiently sharing files of any format with

a relatively large file size, such as various data and image files used in ship operation business

applications, between ships and shore has not yet been standardized.

For example, in ship operations, onboard and on-shore application users determine the timing of data

transmission and reception in relation to the connection status and communication quality of ship-shore

communication each time, and perform data retransmission processing independently for each

application.

In order to further promote the safe and efficient operation of ships, it is increasingly important to be

able to send and receive files between ships and shore in a stable and efficient manner asynchronously

without being affected by the ship-shore communication status.

In this document, asynchronous communication means the communication and/or application

processing perspective, such as time-insensitive data transmission for non-real-time applications where

the timing of the data generating and consuming can be different.

Although ISO 19847 and ISO 19848 provide standardized processes for efficient collection and storage

of data for ship equipment systems, the method of asynchronously transmitting and receiving a large

amount of ship equipment data accumulated on board between ships and shore has not been

standardized yet. In order to promote shore support for ship operation and maintenance of onboard

equipment systems, there is a need for a stable and efficient method for transmitting and receiving such

onboard field data asynchronously between ships and shore.

This document specifies the functional requirements but does not intend to specify technical protocols. Formatted: Default Paragraph Font

Please seeSee Annex A for more information on the correlation ofbetween the different relevant Formatted: cite_app

standards.
Formatted: cite_app
Formatted: Font: 11 pt
Formatted: Line spacing: single
© ISO 2022 – All rights reserved 7
© ISO 2023 – All rights reserved vii
---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO 23807:2023(E)
Formatted: Different first page header
Ships and marine technology — General requirements for the
Asynchronousasynchronous time-insensitive ship-shore data
transmission
1 Scope

This document describes the requirements involved in ship to shore data communication between the

shipboard data servers and the on-shore data servers. It provides information on:

— asynchronous communication;
— a method to measure end-to-end communication quality;
— transport integrity;
— transport security (ege.g. encryption, authentication and authorization);

— management of data transmission (e.g. prioritization, logging, carrier awareness/management);

Formatted: Default Paragraph Font

— communication optimization (e.g. deduplication, compression, resume, multiplexing);

Formatted: Don't adjust space between Latin and Asian
text, Don't adjust space between Asian text and numbers

— compliance with the data communication protocols, including but not limited to ISO 19847.

Formatted: RefNorm, Tab stops: 19.85 pt, Left + 39.7
pt, Left + 59.55 pt, Left + 79.4 pt, Left + 99.25 pt, Left
This document does not cover:
+ 119.05 pt, Left + 138.9 pt, Left + 158.75 pt, Left +

— the security of the data producer/consumer (e.g. identity management); 178.6 pt, Left + 198.45 pt, Left

Formatted: std_publisher
— communication equipment requirements;
Formatted: std_docNumber
— carrier performance requirements (e.g. bandwidth and latency).
Formatted: std_docTitle, Font: Not Italic
Formatted: Don't adjust space between Latin and Asian
text, Don't adjust space between Asian text and numbers
2 Normative references
Formatted: English (United Kingdom)

The following documents are referred to in the text in such a way that some or all of their content

Formatted: Font: Cambria, 11 pt, English (United

constitutes requirements of this document. For dated references, only the edition cited applies. For

Kingdom)

undated references, the latest edition of the referenced document (including any amendments) applies.

Formatted: No underline, Font color: Auto, English

ISO/IEC 20922, Information technology — Message Queuing Telemetry Transport (MQTT) v3.1.1 (United Kingdom)

Formatted: Don't adjust space between Latin and Asian
text, Don't adjust space between Asian text and numbers,
3 Terms and definitions
Tab stops: 19.85 pt, Left + 39.7 pt, Left + 59.55 pt, Left
+ 79.4 pt, Left + 99.25 pt, Left + 119.05 pt, Left +

For the purposes of this document, the following terms and definitions apply. 138.9 pt, Left + 158.75 pt, Left + 178.6 pt, Left +

198.45 pt, Left

ISO and IEC maintain terminology databases for use in standardization at the following addresses: Formatted: English (United Kingdom)

Formatted: Default Paragraph Font, English (United

— ISO Online browsing platform: available at https://www.iso.org/obphttps://www.iso.org/obp

Kingdom)
© ISO 2022 – All rights reserved 1
---------------------- Page: 8 ----------------------
ISO 23807:2022(E)
Formatted: Line spacing: Exactly 12 pt

— IEC Electropedia: available at https://www.electropedia.org/https://www.electropedia.org/

Formatted: No underline, Font color: Auto, English
(United Kingdom)
3.1
Formatted: English (United Kingdom)
asynchronous communication
Formatted: Default Paragraph Font, English (United

Timetime-insensitive data transmission for onboard applications that transmit ship data and/or non-

Kingdom)

real-time applications where the timing of the data generating and consuming can be different.

Note 1 to entry: This definiton is not from the data protocol perspective.
Formatted: Don't adjust space between Latin and Asian
text, Don't adjust space between Asian text and numbers,
Note 2 to entry: ISO 19847 is an example of an onboard application.
Tab stops: 19.85 pt, Left + 39.7 pt, Left + 59.55 pt, Left
+ 79.4 pt, Left + 99.25 pt, Left + 119.05 pt, Left +

Note 3 to entry: The scope of the definition of asynchronous communication in this standard coverdocument covers 138.9 pt, Left + 158.75 pt, Left + 178.6 pt, Left +

messaging services such as message queueing telemetry transport and similar protocols but not streaming using 198.45 pt, Left

Formatted: Default Paragraph Font
datagram protocol.
Formatted: Default Paragraph Font

Note 4 to entry: Table 1 compares the definition of synchronous and asynchronous communication.

Formatted: Default Paragraph Font
Formatted: Default Paragraph Font
Table 1 — Intentions regarding synchronous/asynchronous in this document
Formatted: Default Paragraph Font
Communication/application perspective
Formatted: Default Paragraph Font
Synchronous The receiver sends a response, and the sender waits for the
Formatted: cite_tbl
response before sending the next data.
Formatted: cite_tbl
Asynchronous The receiver sends a response, and the sender sends the next
data without waiting for the response.
3.2
data transport agent

software installed on a ship or shore that interfaces with peripheral devices and systems

Note 1 to entry: The data transport agent collects and sends data to the asynchronous data management agent (3.3)

Formatted: Don't adjust space between Latin and Asian
,), or receives data from the asynchronous data management.
text, Don't adjust space between Asian text and numb
...

INTERNATIONAL ISO
STANDARD 23807
First edition
Ships and marine technology —
General requirements for the
asynchronous time-insensitive ship-
shore data transmission
PROOF/ÉPREUVE
Reference number
ISO 23807:2023(E)
© ISO 2023
---------------------- Page: 1 ----------------------
ISO 23807:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© 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
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 23807:2023(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction .................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ..................................................................................................................................................................................... 1

3 Terms and definitions .................................................................................................................................................................................... 1

4 Abbreviated terms ............................................................................................................................................................................................. 2

5 General requirements .................................................................................................................................................................................... 3

5.1 General ........................................................................................................................................................................................................... 3

5.2 Encryption .................................................................................................................................................................................................. 4

5.3 Compression ............................................................................................................................................................................................. 4

5.4 Deduplication ........................................................................................................................................................................................... 4

5.5 Distribution ............................................................................................................................................................................................... 5

5.6 Recovery ....................................................................................................................................................................................................... 5

6 Data transport agent — vessel side interface ....................................................................................................................... 5

6.1 General ......................................................................................................................................................................................................... 5

6.2 Transportation folders .................................................................................................................................................................... 5

6.3 File move and sync .............................................................................................................................................................................. 5

6.3.1 Moving files ............................................................................................................................................................................. 5

6.3.2 Synchronizing folders .................................................................................................................................................... 5

6.4 Server message block ....................................................................................................................................................................... 5

6.5 Asynchronous message service .............................................................................................................................................. 6

6.6 API ........................................................................................................................................... ........................................................................... 6

7 Data transport agent — shore side interface ........................................................................................................................ 6

8 Requirements for asynchronous data management agent ..................................................................................... 6

8.1 General ......................................................................................................................................................................................................... 6

8.2 Size restrictions ..................................................................................................................................................................................... 6

8.3 Prioritization of data ......................................................................................................................................................................... 7

8.4 Carrier status ........................................................................................................................................................................................... 7

8.5 On-demand data request ............................................................................................................................................................... 7

8.6 Delayed transmission ....................................................................................................................................................................... 7

8.7 Resume on interrupt ......................................................................................................................................................................... 7

8.8 Monitoring .................................................................................................................................................................................................. 7

9 Requirements for security of data transmission .............................................................................................................. 8

9.1 General ......................................................................................................................................................................................................... 8

9.2 Transport security .............................................................................................................................................................................. 8

9.3 Data security ............................................................................................................................................................................................ 8

Annex A (informative) Correlation chart .....................................................................................................................................................10

Annex B (informative) Functions of asynchronous data management agent .......................................................11

Annex C (informative) HTTP file input and output protocol used on the data transport agent .......13

Bibliography .............................................................................................................................................................................................................................15

iii
© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 3 ----------------------
ISO 23807:2023(E)
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 documents 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).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www.iso.org/patents).

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.

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.
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 23807:2023(E)
Introduction

Sharing data between ships and the shore to ensure the safe and efficient operation of ships is becoming

increasingly common.

Progress has been made in establishing data sharing between ships and the shore, related to ports,

cargo and shipping routes. This includes the development of and discussions around standards related

to Maritime Single Window and e-Navigation, which help to share some stylized data safely and in a

timely manner between ships and shore.

On the other hand, the ship-shore communication environment is still narrower than those on land,

and its connection is unstable. Therefore, a method for stably and efficiently sharing files of any format

with a relatively large file size, such as various data and image files used in ship operation business

applications, between ships and shore has not yet been standardized.

For example, in ship operations, onboard and on-shore application users determine the timing of data

transmission and reception in relation to the connection status and communication quality of ship-

shore communication each time, and perform data retransmission processing independently for each

application.

In order to further promote the safe and efficient operation of ships, it is increasingly important to be

able to send and receive files between ships and shore in a stable and efficient manner asynchronously

without being affected by the ship-shore communication status.

In this document, asynchronous communication means the communication and/or application

processing perspective, such as time-insensitive data transmission for non-real-time applications

where the timing of the data generating and consuming can be different.

Although ISO 19847 and ISO 19848 provide standardized processes for efficient collection and

storage of data for ship equipment systems, the method of asynchronously transmitting and receiving

a large amount of ship equipment data accumulated on board between ships and shore has not been

standardized yet. In order to promote shore support for ship operation and maintenance of onboard

equipment systems, there is a need for a stable and efficient method for transmitting and receiving

such onboard field data asynchronously between ships and shore.

This document specifies the functional requirements but does not intend to specify technical protocols.

See Annex A for more information on the correlation between the different relevant standards.

© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 23807:2023(E)
Ships and marine technology — General requirements
for the asynchronous time-insensitive ship-shore data
transmission
1 Scope

This document describes the requirements involved in ship to shore data communication between the

shipboard data servers and the on-shore data servers. It provides information on:

— asynchronous communication;
— a method to measure end-to-end communication quality;
— transport integrity;
— transport security (e.g. encryption, authentication and authorization);

— management of data transmission (e.g. prioritization, logging, carrier awareness/management);

— communication optimization (e.g. deduplication, compression, resume, multiplexing);

— compliance with the data communication protocols, including but not limited to ISO 19847.

This document does not cover:
— the security of the data producer/consumer (e.g. identity management);
— communication equipment requirements;
— carrier performance requirements (e.g. bandwidth and latency).
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/IEC 20922, Information technology — Message Queuing Telemetry Transport (MQTT) v3.1.1

3 Terms and definitions
For the purposes of this document, the following terms and definitions 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
asynchronous communication

time-insensitive data transmission for onboard applications that transmit ship data and/or non-real-

time applications where the timing of the data generating and consuming can be different

Note 1 to entry: This definiton is not from the data protocol perspective.
© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 6 ----------------------
ISO 23807:2023(E)
Note 2 to entry: ISO 19847 is an example of an onboard application.

Note 3 to entry: The scope of the definition of asynchronous communication in this document covers messaging

services such as message queueing telemetry transport and similar protocols but not streaming using datagram

protocol.

Note 4 to entry: Table 1 compares the definition of synchronous and asynchronous communication.

Table 1 — Intentions regarding synchronous/asynchronous in this document
Communication/application perspective
Synchronous The receiver sends a response, and the sender waits for the re-
sponse before sending the next data.
Asynchronous The receiver sends a response, and the sender sends the next data
without waiting for the response.
3.2
data transport agent

software installed on a ship or shore that interfaces with peripheral devices and systems

Note 1 to entry: The data transport agent collects and sends data to the asynchronous data management agent

(3.3), or receives data from the asynchronous data management.
3.3
asynchronous data management agent

software used for the control and transport of data between ship and shore data transport agent (3.2)

4 Abbreviated terms
AES advanced encryption standard
AES-CCM AES-counter with cipher block chaining-message authentication code
AES-GCM AES-galois/counter mode
API application programming interface
BIZ-LAN business local area network
ChaCha20 a stream cipher specified in RFC 8439
ChaCha20-Poly1305 a cryptographic algorithm that combines ChaCha20 and Poly1305
DH Diffie-Hellman key exchange algorithm
DHE Diffie-Hellman Ephemeral key exchange algorithm
DMZ DeMilitarized Zone
ECDH elliptic curve Diffie–Hellman key exchange algorithm
ECDHE elliptic curve Diffie–Hellman ephemeral key exchange algorithm
ECDSA elliptic curve digital signature algorithm
F/W firewall
GraphQL query language and runtime designed for APIs
HTTP hypertext transfer protocol
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 23807:2023(E)
IoT Internet of things
LAN local area network
MQTT message queueing telemetry transport
OT operational technology
Poly1305 a cryptographic message authentication mode specified in RFC 8439

PSEC-KEM provably secure elliptic curve encryption with key encapsulation mechanisms

REST REpresentational state transfer
RSASSA-PKCS1-v1_5 a digital signature algorithm specified in RFC 8017
RSASSA-PSS a digital signature algorithm specified in RFC 8017
SHA-256 secure hash algorithm-256
SHA-384 secure hash algorithm-384
SHA-512 secure hash algorithm-512
TCP transmission control protocol
TLS1.3 transport layer security version 1.3
UDP user datagram protocol

UR E22 International Association of Classification Societies (IACS) Unified Requirement

Electrical and Electronic Installations 22
UTM unified threat management
VSAT very small aperture terminal
5 General requirements
5.1 General

Communication between shore and ship are usually initiated from the vessel side. The vessel in most

cases has a random IP address and it is difficult to change the firewall rules to allow traffic from shore

sites. It is both easier and safer to initiate the communication link from behind the firewall, meaning

that the vessel shall initiate the contact with shore. The same is true for shore sites, such as ship

managers office locations. These locations should be considered a client side location, and should be

responsible for initiating the communication link to a common centre resource such as the cloud server

or the ompremises.
Figure 1 shows the overall picture of this document.
© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 8 ----------------------
ISO 23807:2023(E)
Figure 1 — Image of asynchronous transmission

Asynchronous communication is used on all communication where data can be transmitted

intermittently.

It shall be applied to narrow-band and unstable ship-shore communication to exchange various types

of data such as documents, media files, sensor data and machine-to-machine communication, and shall

be applied to transferring the onboard server data. Best effort, variable bit rate and communication at

regular intervals utilize spare capacity on an available carrier. Such communication shall comply with

the requirements in 5.2, 5.3, 5.4, 5.5 and 5.6.

A single agent, or multiple agents, can be used to service multiple data formats.

5.2 Encryption

All traffic shall use appropriate encryption as dictated by the sensitivity of the data.

5.3 Compression

The content shall be compressed whenever the compressed size is significantly smaller than the

raw data. The compression algorithm used shall be optimal for the intended use of the data, and not

necessarily what provides the highest compression.
5.4 Deduplication

Transferring a large amount of data can have significant bandwidth savings by using proper

deduplication. The deduplication protocol divides sending data into chunks and tracks their progress.

The chunk size used in deduplication is not a fixed size and can be from 2K to 32K in size. For small data

transfers, the overhead for the control traffic for deduplication can be bigger than the data itself. In

such cases, deduplication should be avoided and any file below 2KB in size shall not be split into parts.

Files larger than 2KB can be split into parts for deduplication, depending on the structure of the file.

The deduplication protocol recognizes data blocks already available on the destination client, and only

sends blocks not already on the client. This is true even for binary encoded data whenever the content

can be shared among other communication data. For example, binary docker images greatly benefit

from deduplication due to the layers inherent in such an image. These layers are shared between

multiple docker images.
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
...

Questions, Comments and Discussion

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