ANNEX I CRequirements for construction, testing, installation, and inspection
TACHOGRAPH CARDS SPECIFICATION
3.HARDWARE AND COMMUNICATION
3.5.Command descriptions
3.5.2READ BINARY
3.5.2.3Command with odd instruction byte
3.5.2.3.1Command with secure messaging (example)
TCS_55Response message if the command is successful
Byte | Length | Value | Description |
---|---|---|---|
#1 | 1 | ‘B3h’ | Plain Data encoded in BER-TLV |
#2 | L | ‘NNh’ or ‘81 NNh’ | LPV: length of returned data (=original Le). L is 2 bytes if LPV>127 bytes. |
#(2+L)-#(1+L+NN) | NN | ‘XX..XXh’ | Plain Data value encoded in BER-TLV, i.e. data read encapsulated in a discretionary data object with tag ‘53h’. |
#(2+L+NN) | 1 | ‘99h’ | Processing Status of the unprotected response APDU |
#(3+L+NN) | 1 | ‘02h’ | Length of Processing Status |
#(4+L+NN) — #(5+L+NN) | 2 | ‘XX XXh’ | Processing Status of the unprotected response APDU |
#(6+L+NN) | 1 | ‘8Eh’ | TCC: Tag for cryptographic checksum |
#(7+L+NN) | 1 | ‘XXh’ | LCC: Length of following cryptographic checksum ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B) |
#(8+L+NN)-#(7+M+L+NN) | M | ‘XX..XXh’ | Cryptographic checksum |
SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |