Addressed binary message

Printer-friendly versionPDF version
msg_ID: 
6
Extended description: 
Binary data for addressed communication
Priority: 
4
Access scheme: 
RATDMA
ITDMA
FATDMA
Communication state: 
N/A
Transmitted by: 
Mobile station
Base station

The addressed binary message should be variable in length, based on the amount of binary data. The length should vary between 1 and 5 slots. See application identifiers in § 2.1, Annex 5.

TABLE 54

ParameterNumber of bitsDescription
Message ID6Identifier for Message 6; always 6
Repeat indicator2Used by the repeater to indicate how many times a message has been repeated. Refer to § 4.6.1, Annex 2; 0-3; default = 0; 3 = do not repeat any more
Source ID30MMSI number of source station
Sequence number20-3; refer to § 5.3.1, Annex 2
Destination ID30MMSI number of destination station
Retransmit flag1Retransmit flag should be set upon retransmission: 0 = no retransmission = default; 1 = retransmitted
Spare1Not used. Should be zero. Reserved for future use
Binary dataMaximum 936Application identifier16 bitsShould be as described in § 2.1, Annex 5
Application dataMaximum 920 bitsApplication specific data
Maximum number of bitsMaximum 1 008Occupies up to 3 slots, or up to 5 slots when able to use FATDMA reservations. For Class B “SO” mobile AIS stations the length of the message should not exceed 3 slots For Class B “CS” mobile AIS stations should not transmit;
[size= 13.008px]Additional bit stuffing will be required for these message types. For details refer to transport layer, § 5.2.1, Annex 2.[/size]

Table 55 gives the number of binary data bytes (including application ID and application data), so that the whole message fits into a given number of slots. It is recommended that any application minimizes the use of slots by limiting the number of binary data bytes to the numbers given, if possible:

TABLE 55
Number of slotsMaximum binary data bytes
18
236
364
492
5117
These numbers also take bit stuffing into account.

Addressed messages should have a destination user ID. The source station should anticipate an acknowledgement message (Message 7 or Message 13). If an acknowledgement is not received the station excluding Class B “SO” should retry the transmission. The station should wait 4 s before attempting retries. When a transmission is retried, the retransmit flag should be set to retransmitted. The number of retries should be 3, but it could be configurable between 0 and 3 retries by an external application via the presentation interface. When set to a different value by an external application, the number of retries should default to 3 retries after 8 min. The overall result of the data transfer should be forwarded to above layers. The acknowledgement should be between transport layers in two stations.

Each data transfer packet on the presentation interface should have a unique packet identifier consisting of the message type (binary or safety related messages), the source-ID, the destination-ID, and a sequence number.

The sequence number should be assigned in the appropriate presentation interface message which is input to the station.

The destination station should return the same sequence number in its acknowledgement message on the presentation interface.

The source station should not reuse a sequence number until it has been acknowledged or time-out has occurred.

The acknowledgement should be put first in the data transfer queue both on the presentation interface and on the VDL.

These acknowledgements are applicable only to the VDL. Other means must be employed for acknowledging applications.

1371-5 figure 23 annex 6