5.1 Application Services Provider(s) (ASPs) providing
services to:
-
.1 a National LRIT Data Centre, should be recognized
by the Contracting Government establishing the centre;
-
.2 a Regional or a Cooperative LRIT Data Centre,
should be recognized by the Contracting Governments establishing the
centre. In such a case, the arrangements for recognizing the ASPs
should be agreed amongst the Contracting Governments establishing
the centre; and
-
.3 an International LRIT Data Centre, should be
recognized by the Committee.
5.2 Contracting Governments should provide to
the Organization a list with the names and contact details of the
ASPs they recognize together with any associated conditions of recognition
and thereafter should, without undue delay, update the Organization
as changes occur.
5.2.1 The Organization should communicate information
it receives pursuant to the provisions of paragraph 5.2 and information
in relation to the ASP(s) recognized by the Committee for providing
services to the International LRIT Data Centre and any changes thereto
to all Contracting Governments, all LRIT Data Centres, the International
LRIT Data Exchange and the LRIT Coordinator.
5.3 An ASP function should:
-
.1 provide a communication protocol interface
between the Communication Service Providers and the LRIT Data Centre
to enable the following minimum functionality:
-
.1 remote integration of the shipborne equipment
into an LRIT Data Centre;
-
.2 automatic configuration of transmission of
LRIT information;
-
.3 automatic modification of the interval of transmission
of LRIT information;
-
.4 automatic suspension of transmission of LRIT
information;
-
.5 on demand transmission of LRIT information;
and
-
.6 automatic recovery and management of transmission
of LRIT information;
-
.2 provide an integrated transaction management
system for the monitoring of LRIT information throughput and routeing;
and
-
.3 ensure that LRIT information is collected,
stored and routed in a reliable and secure manner.
5.4 The ASP where used should add the data identified
in table 2 to each transmission of LRIT information:
Table 2 - Data to be added by an
Application Service Provider and at the LRIT Data Centre
| Parameters
|
Comments
|
| Ship
Identity(1)
|
The IMO
ship identification number(1) and MMSI for the ship.
|
| Name of
ship
|
Name of
the ship which has transmitted the LRIT information in the English language
using latin-1 alphabet and UTF-8 encoding.
|
| Type of
ship(2)
|
Type of
the ship which has transmitted the LRIT information using a pre-defined
code.
|
| Time
Stamp 2
|
The date
and time(3) the transmission of LRIT information is received by
the ASP (if used).
|
| Time
Stamp 3
|
The date
and time(3) the received LRIT information is forwarded from the
ASP (if used) to the appropriate LRIT Data Centre.
|
LRIT Data
Centre
Identifier
|
The
identity of the LRIT Data Centre to be clearly indicated by a Unique
Identifier.
|
| Time
Stamp 4
|
The date
and time(3) the LRIT information is received by the LRIT Data
Centre.
|
| Time
Stamp 5
|
The date
and time(3) the transmission of LRIT information is forwarded
from the LRIT Data Centre to an LRIT Data User.
|
| Notes:
(1) See
regulation XI-1/3 and resolution A. 6001078(1528) on IMO ship
identification number scheme.
(2)
Types of ships to be used in LRIT messages are outlined in LRIT Technical
documentation, part I (MSC.1/Circ.1259, as revised).
(3) All times should be indicated as Universal Coordinated
Time (UTC).
|
5.5 In addition to the provisions of paragraph
5.3, Administrations, Contracting Governments and the Committee may
establish, in relation to the ASPs seeking their recognition, specific
requirements as a condition of recognizing a particular ASP.