Ingangsdatum: 15-12-2006
2.2.2 - LRIT Ship Position Reports (Messages 1, 2 and 3)
2.2.2.1 Table 2 outlines the parameters associated with the positional data messages (ship position reports).
2.2.2.2 The parameters added by the LRIT shipborne equipment include the latitude, longitude, Time Stamp when the position was generated, and the shipborne equipment identifier.
2.2.2.3 The parameter "ASP ID#" table 2 provides the unique LRIT component ID of the ASP that has received the LRIT positional data.
2.2.2.4 The "Message type" parameter in table 2 indicates the type of message of the associated LRIT message. The LRIT components such as the LRIT Data Centres can use this parameter to distinguish between the various LRIT messages listed in table 1.
2.2.2.5 The "Message ID#" parameter in table 2 is a unique identification number that LRIT components can use to identify individual messages within the LRIT network. The Message ID# is generated by using a concatenation of the following parameters: message type, IMO #, ASP ID# and Time Stamp. All these parameters are necessary in order to generate a unique ID number.
2.2.2.6 The "Reference ID#" parameter in table 2 will either be a message ID of an associated request message or a 0 value. The 0 value is populated if the message is not the result of a request message whereas a valid "Message ID" value indicates that a request message has initiated the LRIT positional data report.
2.2.2.7 The "IMO#" and "MMSI#" parameters in table 2 are the IMO ship identification number and Maritime Mobile Service Identity (MMSI) number of the ship being tracked respectively.
2.2.2.8 The "Time Stamp 2" and "Time Stamp 3" parameters in table 2 represent the date and time associated with when the ASP received and transmitted the positional data message.
2.2.2.9 The "Other" parameter is reserved for future parameters.
2.2.2.10 The parameter "DC ID#" in table 2 provides the unique LRIT component ID of the Data Centre receiving the LRIT positional data.
2.2.2.11 The "Time Stamp 4" and "Time Stamp 5" parameters in table 2 represent the date and time associated with when the Data Centre received and transmitted the positional data message.
2.2.2.12 The "Response type" parameter in table 2 provides information on why the designated LRIT Data User (Requestor) is receiving the LRIT positional data. The LRIT Data User will be entitled to receive the LRIT positional data report based upon functioning as: a flag State; a port State; a coastal State; or a SAR service.
2.2.2.13 The "LRIT Data User (Requestor)" parameter in table 2 represents the LRIT Data User that is originating the request message.
2.2.2.14 The "Ship Name" parameter in table 2 represents the ship name.
2.2.2.15 The "LRIT Data User (Provider)" parameter in table 2 is a unique identification number associated with the Contracting Government to which the ship is registered. This parameter is used to identify the destination of the request message. The International LRIT Data Exchange will look at this parameter during processing of the request message and use it to correctly route the message to the appropriate Data Centre(s).
2.2.2.16 If responding to a SAR request, the response type would be SAR; if responding to a port request, the response type would be Port; if responding to a coastal request, the response type would be Coastal; if responding to a flag request, the response type would be Flag.
Table 2 - LRIT positional data (position report) messages
Parameter
Added By | Parameter | Values | Description | LRIT
Segments |
LRIT
Shipborne
equipment | Latitude | Lat | Latitude position of the ship. | A, B, C, D |
| Longitude | Long | Longitude position of the ship. | A, B, C, D |
| Time Stamp 1 | Time1 | Date and time when position was taken. | A, B, C, D |
| Shipborne equipment identifier | Equip# | Unique LRIT shipborne equipment (terminal) number used for communication. | A, B, C, D |
LRIT ASP | ASP ID# | ASP# | LRIT ASP unique identification number.
All Data Centres must ensure that all of their ASPs have a unique number. | B, C, D |
| Message type | 1, 2, 3 | Message identification number:
1 - Periodic Report
2 - Polled Report
3 - SAR Report | B, C, D |
| Message ID# | Unique
number | Unique message number generated by using:
Message type, IMO ship identification number of ship being tracked, ASP ID# and Time Stamp 2. | B, C, D |
| Reference ID# | Unique
number | The message ID of the associated request message. It is only valid for a response to a request message (a 0 value indicates the message is not a result of a request message). | B, C, D |
| IMO# | IMO# | IMO ship identification number of the ship being tracked. | B, C, D |
| MMSI# | MMSI# | Maritime Mobile Service Identity number of the ship being tracked. | B, C, D |
| Time Stamp 2 | Time2 | Date and time ASP receives message. | B, C, D |
| Time Stamp 3 | Time3 | Date and time ASP transmits message. | B, C, D |
| Other | Other | Reserved field that may include price or billing specific information. | B, C, D, E |
LRIT Data
Centre | DC ID# | DC# | LRIT Data Centre unique identification number. | D, C |
| Time Stamp 4 | Time4 | Date and time when the Data Centre receives message from ASP. | D, C |
| Time Stamp 5 | Time5 | Date and time when the Data Centre transmits a message to a LRIT Data User. | D, C |
| Response type | Coastal Flag Port SAR | One of these four values is added by the Data Centre when the message is transmitted. | D, C |
LRIT Data User
(Requestor) | UserID# | Unique identification number identifying Requesting LRIT Data User. Every participating LRIT Data User has a unique number.
For a coastal State the request is part of the Standing Order in the Data Distribution Plan. | B, C, D |
| Ship Name | Name | Name of ship associated with position report. | D, C |
LRIT Data User
(Provider) | UserID# | Unique identification number identifying Contracting Government to which the ship is registered. | B, C, D |