IALA endorsed the Maritime Connectivity Platform (MCP) test instance
An important part of IALA’s work is focused on digital solutions within their domain, which is stated in R1019, ‘The provision of maritime services in the context of e-navigation in the domain of IALA’. One phrase of this recommendation states that IALA members should;
Ensure worldwide harmonization and interoperability by taking into account international standards and guidance for platforms for providing users with interoperable service discovery, identity authentication and messaging services.
The MCP is a decentralised realisation of this element of the recommendation, which provides exactly these features.
The MCP supports multiple digitalisation efforts, not least the development of SECOM‑based Technical Services, which require the authentication and service discoverability capabilities.
Status on IALA Technical Service Specifications and related information is available here:
https://www.iala.int/technical/technical-services/
The IALA endorsed MCP test instance is offered not only for IALA members, but also for any other relevant maritime stakeholders. The MCP test instance comprises:
- Maritime Identity Registry (MIR): Compliant with IALA G1183 Provision of MCP identities
- Maritime Service Registry (MSR): IALA guideline in preparation
- Maritime Messaging Service (MMS): Compliant with RTCM standard 13900.0
The MMS comprises two MMS router nodes with attached edge routers, and these are located in Sweden and Korea.
A management portal for MIR and MSR is available here:
https://management.maritimeconnectivity.net
New organisations and users can request access through this portal.
MMS endpoints (Programming API’s, not for user login):
- Korea Edge Router: wss://kr-edgerouter.dmc.international:8888
- Sweden Edge Router: wss://eu-edgerouter.dmc.international:8888
- Korea Router: wss://kr-router.dmc.international:8080
- Sweden Router: wss://eu-router.dmc.international:8080
The reference implementation should be maintained as long as it supports member needs in developing and testing digital maritime services. IALA may withdraw its endorsement at any time if the service is no longer required or if alternative providers emerge.
The IALA MCP test instance is operated by MCP Consortium members, KRISO and GLA Research & Development Directorate (GRAD).
More information on the MCP consortium can be found here: www.maritimeconnectivity.net
It is important to stress that the test instance obviously must not be used for any operational purposes. No guarantee or liability of this free service is given, not by IALA and not by KRISO or GRAD either.
——————————————————————————————————————-
Frequently Asked Questions (FAQ)
What is the MCP, and why is it important?
IALA, as a global organisation, has a specific purpose to foster safe, economic and efficient movement of vessels through the improvement and harmonisation of Aids to Navigation (AtoN) worldwide. This is achieved to a large extent through the IALA committee work, which has a consultative, recommendatory and technical nature. Especially in the area of e-Navigation, as this is defined by the IMO (MSC85/26, Annexes 20 & 21), IALA has been extremely active with multiple innovative proposals. Work produced by IALA includes the evolution of VHF communications (e.g. VDES), the definition of relevant IHO product specifications (e.g. S‑201, S‑211, S‑212) and the development of a comprehensive framework for the specification of the future maritime services (e.g. IALA G‑1128).
The evolution of the e-Navigation concept and the production of the S-100 product specifications were initially slower than originally envisaged. In the last few years, however, it has been picking up pace. The first operational S-101 ENC data are expected to be available as early as 2025, while IALA members have already begun to demonstrate interoperability of their maritime service using S-100 (e.g. DTEC3 and ARM19 plenary meeting presentations). A crucial technology in this global innovation effort has been the new IEC standard for secure communications in the maritime domain, called SECOM. This defines a generic set of interfaces (APIs) and enables two key operations:
- Discovery of available maritime services by interested clients
- End-to-end security of bi-directional communication
SECOM is primarily focus for delivering data to the ECDIS, but its generic payload-agnostic nature makes it suitable for almost all maritime communications, i.e. internet web-portals, inter-authority data exchange etc. SECOM, however, is just a standard. To actually realise the envisaged solution, an implementation platform that supports SECOM is required.
The Maritime Connectivity Platform (MCP) is currently the only available option for this implementation. In addition, it also augments the communication capabilities of SECOM through publish-subscribe messaging. The MCP is an open‑source project, governed by the MCP Consortium (MCC), a group of non-profit organisations. IALA members have expressed considerable interest in this technology, especially due to its decentralised nature, with IALA guidelines already being published to standardize its operation (e.g. G-1183).
Why should IALA provide an MCP reference implementation?
Several IALA members, as well as affiliated organisations, have been making use of the MCP technology in preparation for the provision of their new digital services. A number of test service instances are already available and can support multiple S-100 data products, including Route‑Exchange, VTS, Navigational Warning and AtoN information. The purpose of this global effort, for the benefit of all mariners, is to:
- Evaluate the validity and clarity of the standards
- Ensure interoperability
- Encourage innovation
None of that would be possible without the provision of at least an MCP reference, allowing maritime authorities to exchange information, easily and securely.
During the 2nd Joint IALA/IHO Workshop on S-100/S-200 Development and Portrayal, held in Annapolis, USA, in September 2024, however, it became apparent that several private organisations active in the maritime domain have a number of misconceptions about the true purpose and nature of the MCP. The platform is viewed as a proprietary and expensive solution, closed to organisations outside the MCC. Obviously, none of these statements is true.
The IALA members who currently develop and benefit from the operational capabilities of the MCP are concerned that a significant technological advantage might be lost due to anachronistic misconceptions and limited promotional experience. As such, the support of IALA as an experienced and globally well-respected organisation could be a game‑changer. By supporting the current reference implementation and promoting it as the official reference implementation of the MCP, IALA has the ability to reassure equipment manufacturers and maritime industry community as a whole; this is not a profit-focused endeavour, but a valuable open technology with a huge public-service value, just as in the case of AIS, VDES, Maritime Resource Names (MRN) etc.
After all, it is well‑established after decades of IALA experience that only through the combined efforts between the maritime industry and the relevant authorities can we have a lasting impact on the big issues. Technology and innovation are a crucial tool, through which IALA can support its founding purpose. The provision of a reference implementation of the MCP is a clear step towards achieving that goal.
What does IALA need to do?
Two reference implementations of the MCP are currently active. The first one is funded by the Korea Research Institute of Ships and Ocean Engineering (KRISO) and maintained by the MCC. The second one is funded and maintained by the GLA Research and Development Directorate (GRAD). IALA is requested to take the appropriate actions to recognise the aforementioned instances and promote them as “IALA MCP Reference Implementations” for testing and developing purposes. These actions could be:
- A decision from the IALA Council to allow the use of the term “IALA MCP Reference Implementations” for the aforementioned instances.
- A link to the current MCP instances’ online locations through the IALA website.
The offered MCP instances can remain under the current funding operational regime, resulting in no additional costs or workload to IALA. Should IALA decide in the future to host and operate its own separate instance, or decide that there are no more benefits in providing an official reference implementation, these recognitions may be withdrawn.
By doing so, IALA will demonstrate that it recognises the need for the provision of more resources to support the standardisation, development and testing of the future maritime services. Alternatively, a party interested in developing or testing a product through the MCP will have to liaise with either a specific national authority (e.g. GLA), the less well‑known MCP Consortium for access to their instance, or set up their own, which can be a relatively complicated and costly process.
Who will be responsible for the maintenance of the MCP Reference Implementation?
The organisations currently operating the active MCP instances will continue to be responsible for any maintenance activity required. Software development will continue as it is today, through the work of the MCC members and the whole MCP open‑source community.
It has to be noted that the reference implementations are not intended for production use, and no assurances are offered in terms of reliability/availability. They can, however, be used, until the IALA requirements change, free of charge with a simple registration. IALA is also welcome to operate the registration process if deemed necessary.
As already stated, the current operating organisations are offering their already reserved resources to IALA, in order to encourage research, innovation and further development. and allow other IALA members and maritime organisations to evaluate whether the MCP is a technology that can benefit them.
How long will an MCP Reference Implementation be required?
The proposal for the provision of an “IALA MCP Reference Implementation” is based on the suggestion of the 2nd Joint IALA/IHO Workshop on S-100/S-200 Development and Portrayal, held in Annapolis, USA, in September 2024. The workshop identified the need to support the maritime community towards the realisation of the new generation of maritime services. This whole endeavour is currently at a critical point, where research and innovation need to balance against the gradual launch of maritime services. Therefore, the minimisation of any technological barriers is of great value to IALA members and the whole maritime community.
As long as there is a need to support state authorities, equipment manufacturers, and shipping operators with the capability to evaluate and test their services, IALA may continue to offer an “IALA MCP Reference Implementation”. Of course, if other providers decide to fill in that gap, then IALA may decide to cease this provision, without any claims from the MCC or the MCP instance operators.