PduApi implements the PDU_IOCTL_SUSPEND_TX_QUEUE and PDU_IOCTL_RESUME_TX_QUEUE in PDUIoctl.

That makes it possible to flash a remote ECU transaction save against mobile connection break.
This doesn't protect from internal VCI-ECU communication problems.

If connection breaks between PDU_IOCTL_SUSPEND_TX_QUEUE and PDU_IOCTL_RESUME_TX_QUEUE, ECU stays alive and the ComPrimitives are lost.

If connection breaks after PDU_IOCTL_RESUME_TX_QUEUE ECU might be flashed without any problem.
Only the PDU_RESULT_DATA - Events are lost and no result is received.

This fearure is important, because some flashing processes are sometimes separated in multiple UDS commands (0x3d-WriteMemoryByAddress) because of the iHEX and SRec fileformat.

This D-PDU API - feature avoids the implementation of a fallback image for each ECU.