ANNEX I CU.K.Requirements for construction, testing, installation, and inspection
Appendix 2
TACHOGRAPH CARDS SPECIFICATION U.K.
4.TACHOGRAPH CARDS STRUCTUREU.K.
4.3. Workshop card applications U.K.
4.3.1 Workshop card application generation 1 U.K.
TCS_156After its personalisation, the workshop card application generation 1 shall have the following permanent file structure and file access rules:U.K.
The following abbreviations for the security conditions are used in this table:
SC2
ALW OR SM-MAC-G1 OR SM-MAC-G2
SC3
SM-MAC-G1 OR SM-MAC-G2
[SC4
For the READ BINARY command with even INS byte:
(SM-C-MAC-G1 AND SM-R-ENC-MAC-G1) OR
(SM-C-MAC-G2 AND SM-R-ENC-MAC-G2)
For the READ BINARY command with odd INS byte (if supported): NEV]
TCS_157All EF structures shall be transparent.U.K.
TCS_158The workshop card application generation 1 shall have the following data structure:U.K.
TCS_159The following values, used to provide sizes in the table above, are the minimum and maximum record number values the workshop card data structure must use for a generation 1 application:U.K.
4.3.2 Workshop card application generation 2 U.K.
TCS_160After its personalisation, the workshop card application generation 2 shall have the following permanent file structure and file access rules.U.K.
Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.U.K.
The following abbreviations for the security conditions are used in this table:
SC5
For the Read Binary command with even INS byte: SM-C-MAC-G2 AND SM-R-ENC-MAC-G2
For the Read Binary command with odd INS byte (if supported): NEV
TCS_161All EFs structures shall be transparent.U.K.
TCS_162The workshop card application generation 2 shall have the following data structure:U.K.
TCS_163The following values, used to provide sizes in the table above, are the minimum and maximum record number values the workshop card data structure must use for a generation 2 application:U.K.