|
The implemented sending and receiving protocol is specified by two action/state diagrams. When viewing the diagrams it shall be noted that:
 The diagrams are similar to UML state diagrams
 All states are named after the activity they carry out.
 All state changes are the result of either "receiving a telecommand" or "an action carried out in the state".
The protocol implemented for the receiving sub-service is depicted below.
When a service data unit is uplinked to an application process/service using the large data transfer service, the service automatically receives and stores the service data unit part telecommands. When all parts have been received the service data unit is assembled, transformed in a telecommand packet, and delivered to the destination service.
Transferring the first part of a service data unit
Uplink the first service data unit part telecommand packet.
Transferring an intermediate part of a service data unit
Uplink an intermediate service data unit part telecommand packet.
Transferring the last part of a service data unit
Uplink the last service data unit part telecommand packet.
Re-transferring a part of a service data unit
Uplink a repeated service data unit part telecommand packet.
Transfer abort initiated by the sending end
The ground system initiates abort of the current service data unit downlink.
Acknowledging the successful reception up to a part (all parts)
The large data transfer service acknowledges the successful reception of all service data unit parts, specifying the sequence number of the last part, to the ground system.
Notifying which parts have not been properly received
The large data transfer service notifies the ground system which service data unit parts have not been properly received, requesting re-uplink of said parts.
Transfer abort initiated by the receiving end
The large data transfer service requests abort of the current service data unit uplink.
|