1. The shore based AIS Service as an e-navigation service
Focus on the shore-based AIS service as a means for dataflow between shipboard and shore-based applications.
Does not focus on AIS dataflow between shipboard applications
Also considers interaction between the shore-based AIS service and other shore-based services
Principle engineer Tom Braute Norwegian Coastal Administration
NNF E-navigation Conference – Oslo, October 16th – 17th 2007
NNF E-navigation Conference Oslo, October 16th – 17th 2007

2. The Norwegian Coastal Administration AIS service
Layered structure:
AIS Service Management
Logical Shore Station
Physical Shore Station
36 AIS Physical
Shore Stations
Layered structure of the shore-based AIS service
Functional interface to shore-based applications is defined as a set of external Basic AIS Services (service in stead of device oriented)
External Basic AIS Services
NNF E-navigation Conference Oslo, October 16th – 17th 2007

3. External Basic AIS Services - examples
Receive data from AIS mobile stations
Transmit safety related messages
Transmit DGNSS corrections
Transmit binary messages
Transmit synthetic/virtual AtoN data
Transmit assignment command
Shows examples of external basic AIS services provided by an shore-based AIS service
NNF E-navigation Conference Oslo, October 16th – 17th 2007

4. Use of received AIS data
Examples
AISOnline (WEB presentation tool)
VTS; in combination with other shore-based ENAV services
Radar
VHF
LRIT...
Received AIS data is used in a number of various shore-based applications
Figure shows example of use of received AIS data to produce and present a traffic image on the WEB based tool AISOnline.
Use received AIS data from AIS services provided by several administrations
VTS services depend on the use of received AIS data in combination with other shore-based ENAV services as radar, VHF communication, LRIT, etc
NNF E-navigation Conference Oslo, October 16th – 17th 2007

5. Use of AIS Binary Messages (MET/HYD data application)
Figure show example of display of MET/HYD data transmitted by use of AIS binary message
Example is based on transmissions from a buoy, but the same application could be offered from a shore-based AIS service
Other applications (IMO S/N Circ. 236)
Dangerous cargo indication
Fairway closed
Tidal window
Ext. ship static and voyage related data
No of persons onboard
Pseudo AIS target
NNF E-navigation Conference Oslo, October 16th – 17th 2007

6. Use of DGNSS Corrections
AIS
GNSS
DGNSS corrections
Base Station
Shore-base AIS service can be used to distribute DGNSS corrections to shipboard systems and applications.
Typically the shore based AIS service will receive DGNSS data from a DGNSS service, which is part of the ENAV service bundle.
Onboard Equipment
VESSEL
DGNSS Service
Shore based AIS Service
LAND
NNF E-navigation Conference Oslo, October 16th – 17th 2007

7. NNF E-navigation Conference Oslo, October 16th – 17th 2007
Virtual AtoN
NB! Demonstration only. IEC standard for presentation of navigation information (IEC 62288) requires AIS AtoNs to be displayed by a diamond symbol.
Example:
Need to mark temporary danger
Possible solution: Virtual special mark
Shore-base AIS service can be used to transmit virtual and/or synthetic AtoN data
Virtual = data from a non-existing AtoN
Synthetic = data for an existing AtoN, not transmitted from the AtoN itself
Typically the shore based AIS service will receive AtoN data from an AtoN service, which is part of the ENAV service bundle.
As an example, virtual AtoN can be used to mark a temporary danger
Note: symbol used for displaying virtual AtoN is not according to current IEC standard for presentation of navigation information – used here for demonstration only
NNF E-navigation Conference Oslo, October 16th – 17th 2007

8. Concept of ENAV service
Point of view
from shore applications
Applica-tion 1
Applica-tion 2
Applica-tion 3
Applica-tion 4
Data Trans-fer
Net-work
Link
eNAV-
service
Shore based AIS
Service
AIS VDL
Application-to- application virtual connection (peer-to-peer)
Concept of ENAV service as seen from shore
The ENAV services provide shore-based interfaces to the physical links
The ENAV services ashore interface to an data transfer network, which distributes the data to applications
Key element in ENAV concept: thinking in terms of data flow between applications
ENAV concept can be modelled as a number of virtual connections between shipboard and shorebased applications
The shore based AIS Service is a prominent example for a shore-based ENAV Service – the AIS VDL is a bi-directional physical ENAV link
Other physical ENAV links:
VHF voice/data communication channels
MF data transmissions (DGNSS)
Radar
AtoN
Encapsulation of complexity for shore applications
NNF E-navigation Conference Oslo, October 16th – 17th 2007

9. ENAV System Architecture
Interfacing ENAV system to physical links
Add value to raw data
MMI to primary users (single service)
Shore based AIS Service
Functional interface = External Basic AIS Services
Structural overview representation of the common mode shore-based ENAV system architecture
Based on work done so far within the IALA ENAV Committee TWG
ENAV services are the main building blocks – encapsulating all primary functionality
Figure gives some blocks of ENAV services
Interfacing ENAV system to physical links
Add value to raw data
MMI to primary users (single service)
Data exchange shore-to-shore
AIS Service is example of shore based ENAV service within the block of “Data Collection and Data Transfer services”
AIS Service will be requested by other ENAV services within the system (client-server relationship)
Functional interface to shore-based applications are the external Basic AIS Services as discussed earlier
Data exchange shore-to-shore
NNF E-navigation Conference Oslo, October 16th – 17th 2007

10. Definition of e-navigation (IMO WG on ENAV)
“E-Navigation is the harmonized collection, integration, exchange, presentation and analysis of maritime information onboard and ashore by electronic means to enhance berth to berth navigation and related services, for safety and security at sea and protection of the marine environment.”
IMO Working Group on e-navigation approved this definition at NAV 53. Based on proposal made by IALA.
As seen from the previous ENAV System Architecture, the shore based AIS service will provide ENAV services both within collection and exchange of maritime information
NNF E-navigation Conference Oslo, October 16th – 17th 2007

11. Limitations of AIS as an ENAV service
Limited link capabilities
Safety issues
Limited shipborne equipment capabilities
Display of virtual/syntetic AtoNs
Display of binary application data
Use of DGNSS corrections
Use of shore-based AIS service gives great opportunities, but must bear in mind that the service also has its limitations
The link capabilities have limitations (addressed later)
There are safety issues (addressed later)
Also, shipborne applications has limited capabilities
Displaying virtual/synthetic AtoNs
Display of data provided by binary applications
Use of DGNSS corrections
Limitations of the shipborne applications will hopefully be dealt with within the scope of e-navigation
NNF E-navigation Conference Oslo, October 16th – 17th 2007

12. NNF E-navigation Conference Oslo, October 16th – 17th 2007
AIS link capabilities
Integrity?
Authenticity?
Confidentiality?
Authenticity
Confidentiality
Integrity
Traffic data
Aids to Navigation
Maritime Safety Info
Met/Hyd/Oce service
Ship Reporting
...
Shore
e-Nav
System
Ship
e-Nav
System
Capabilities of link between shorebased and shipborn ENAV systems can be described in form of integrity, authenticity, confidentiality, transparency, availability, etc.
The AIS link has its limitations, specially with regard to integrity, authenticity and confidentiality
Integrity of AIS link
Un-authorized control of AIS data link parameters is possible
Authenticity of AIS data link
Limited restrictions on access to the AIS data link
Lack of mechanisms for authentication of senders- or receivers of information
Confidentiality
Limited mechanisms for data encryption
Everyone can listen in to the data traffic
Availability
Transparency
AIS LINK
NNF E-navigation Conference Oslo, October 16th – 17th 2007

13. Safety issues !! Main function of AIS is anti-collision !!
AIS Services requires capacity on the VDL
Management of the VDL capacity is needed to protect the main functions of AIS
Should not forget that the main function for AIS is anti-collision.
Provision of applications by a shore-based AIS service will require capacity on the VHF Data Link
International management of the VDL capacity is needed to protect the main functions of AIS
Could be done by IALA and IMO
NNF E-navigation Conference Oslo, October 16th – 17th 2007

14. NNF E-navigation Conference Oslo, October 16th – 17th 2007
Questions?
NNF E-navigation Conference Oslo, October 16th – 17th 2007