Expand description
§CFDP Destination Entity Module
The DestinationHandler is the primary component of this module which converts the PDUs sent from a remote source entity back to a file. A file copy operation on the receiver side is started with the reception of a Metadata PDU, for example one generated by the spacepackets::cfdp::pdu::metadata::MetadataPduCreator. After that, file packet PDUs, for example generated with the spacepackets::cfdp::pdu::file_data module, can be inserted into the destination handler and will be assembled into a file.
A destination entity might still generate packets which need to be sent back to the source entity of the file transfer. However, this handler allows freedom of communication like the source entity by using a user-provided PduSender instance to send all generated PDUs.
The transaction will be finished when following conditions are met:
- A valid EOF PDU, for example one generated by the spacepackets::cfdp::pdu::eof::EofPdu helper, has been inserted into the class.
- The file checksum verification has been successful. If this is not the case for the unacknowledged mode, the handler will re-attempt the checksum calculation up to a certain threshold called the check limit. If the threshold is reached, the transaction will finish with a failure.
§Unacknowledged mode with closure
- Finished PDU has been sent back to the remote side.
§Acknowledged mode
- An EOF ACK PDU has been sent back to the remote side.
- A Finished PDU has been sent back to the remote side.
- A Finished PDU ACK was received.
Structs§
- Acknowledged
Mode Params - Anomaly
Tracker - Destination
Handler - This is the primary CFDP destination handler. It models the CFDP destination entity, which is primarily responsible for receiving files sent from another CFDP entity. It performs the reception side of File Copy Operations.
Enums§
- Dest
Error - Transaction
Step - This enumeration models the different transaction steps of the destination entity handler.