Cookies
We need your consent to use the individual data so that you can see information about your interests, among other things. Click "OK" to give your consent.
IEC 63173-2-ed.1.0
Maritime navigation and radiocommunication equipment and systems - Data interfaces - Part 2: Secure communication between ship and shore (SECOM)
Translate name
STANDARD published on 30.5.2022
The information about the standard:
Designation standards: IEC 63173-2-ed.1.0
Publication date standards: 30.5.2022
SKU: NS-1064307
The number of pages: 402
Approximate weight : 1237 g (2.73 lbs)
Country: International technical standard
Category: Technical standards IEC
The category - similar standards:
Annotation of standard text IEC 63173-2-ed.1.0 :
IEC 63173-2:2022 the scope of secure communication between ship and shore (SECOM) includes interfaces (APIs) for data exchange (information services), information security measures to enable secure communication and interfaces for service discoverability. SECOM provides technical interoperability, where the same service interface is used for exchanging the information regardless of its operational use, up to the level of exchanging information securely online. Although designed for IHO S-100 based products, SECOM is technically payload agnostic and applicable also for other types of data. Communication between SECOM information services for data exchange relies on IP based web services. The "last mile" links between a SECOM information service and the end-user application is not defined in this document, thus the communication technology between the vendor API and a ship/shore system can be non-IP based as well as IP based. The informative Annex D describes one such implementation of this. This allows different solutions between the service and shore/ship’s system/applications. SECOM does not define physical layer or link layer for transport of data between SECOM information services, but requires that the transport supports IP communication. SECOM is applicable for both public (governmental) and private (business) services. SECOM is applicable for ship-shore and shore-ship communication, and can be used for ship-ship communication. IEC 63173-2:2022 Le domaine d’application du SECOM comprend des interfaces (API) pour l’echange de donnees (services d’information), des mesures de securite de l’information pour permettre des communications securisees et des interfaces pour la decouvrabilite des services. Le SECOM assure l’interoperabilite technique, ou la meme interface de service est utilisee pour l’echange d’informations independamment de son utilisation operationnelle, jusqu’au niveau de l’echange d’informations en ligne securise. Bien que concu pour les produits bases sur la S-100 de l’OHI, le SECOM ne depend pas techniquement des donnees utiles et est egalement applicable a d’autres types de donnees. Les communications entre services d’information SECOM pour l’echange de donnees sont basees sur des services web sur IP. Les liens du "dernier kilometre" entre un service d’information SECOM et l’application d’utilisateur ne sont pas definis dans le present document et, par consequent, la technologie de communication entre l’API du fournisseur et un systeme navire/terre peut etre aussi bien basee sur IP que non basee sur IP. L’Annexe D informative decrit une mise en ouvre de celles-ci. Elle permet differentes solutions entre le service et les systemes/applications a terre/du navire. Le SECOM ne definit pas la couche physique ou la couche de liaison pour le transport des donnees entre services d’information SECOM, mais exige que le transport prenne en charge la communication IP. Le SECOM est applicable aux services publics (gouvernementaux) et prives (entreprises). Le SECOM est applicable aux communications navire-terre et terre-navire, et peut etre utilise pour les communications navire-navire.
We recommend:
Updating of laws
Do you want to be sure about the validity of used regulations?
We offer you a solution so that you could use valid and updated legislative regulations.
Would you like to get more information? Look at this page.
