Tomcat
Professional
- Messages
- 2,689
- Reaction score
- 963
- Points
- 113
Consider now the structure of the FCI Template data object for the DDF file shown in Fig. 3.6.
As you can see from the figure, the FCI Template object for the DDF file consists of the same two required data objects DF Name (Tag '84') and the FCI Proprietary Template (Tag'A5 ') as in the case of the FCI Template for the ADF file.
The DF Name Data Object (Tag '84') is required and its data field is encoded in a binary string of 5 to 16 bytes.
Consider now the FCI Proprietary Template object. Its structure is different from that of the FCI Proprietary Template for the ADF file. It consists of only two objects presented in table. 3.8. An exception is the PSE file (see below), which contains additional optional data items.
Tag 6F - FCI Template (М)
The SFI of Directory Elementary file (Tag '88') data object is required because it defines a link (short name) to a Directory Elementary File that reflects the structure of the DDF file (more on this below).
The FCI Issuer Discretionary Data object (Tag 'BFOC') is optional and contains information specific to the issuer of card applications grouped in a DDF file.
An important attribute of any DDF file is an EF file called a Directory Elementary File (DEF) file. The DEF file is a required file in the DDF directory. It defines the structure of the DDF file. Each DEF record generally contains several Application Template Data Objects (Tag '61'). The Application Template object stores the details of a single ADF or DDF file for which the DDF file we are considering is the parent. However, the content of the Application Template data object is different for ADF and DDF files.
In the case of an ADF file, the Application Template object stores two required data objects: ADF Name (Tag '4F') and Application Label (Tag '50'). Optionally, the Application Template can also contain Application Preferred Name, Issuer Code Table Index, and Application Priority Indicator data objects.
Recall that the data field of the ADF Name object is either equal to the AID of the application whose data is stored in the ADF file, or starts with the AID.
In the case of a DDF file, the Application Template contains a single DDF Name data object (Tag '9D') and does not contain any optional data objects.
Rice. 3.7 demonstrates what has been said above regarding the structure of the Application Template and the AEF Data Template DEF file.
Note that Application Template objects for an ADF or DDF file may contain Directory Discretionary Template objects (Tag '73') that define data useful from the point of view of the issuer of applications located in the appropriate IPC directories.
Rice. 3.7. DEF file record structure
As you can see from the figure, the FCI Template object for the DDF file consists of the same two required data objects DF Name (Tag '84') and the FCI Proprietary Template (Tag'A5 ') as in the case of the FCI Template for the ADF file.
The DF Name Data Object (Tag '84') is required and its data field is encoded in a binary string of 5 to 16 bytes.
Consider now the FCI Proprietary Template object. Its structure is different from that of the FCI Proprietary Template for the ADF file. It consists of only two objects presented in table. 3.8. An exception is the PSE file (see below), which contains additional optional data items.
Tag 6F - FCI Template (М)
- ----? Tad 84 - DF Name (M)
- -----? Tad A5 - FCI Proprietary Template (М)
- -----? Thad 88 - SFI of the directory (elementary) file (M)
- -----? Tag BFOC - FCI Issuer Discretionary Data (0)
| Tag | Data object content | Obligation of data object |
| '88'h | SFI of Directory Elementary File (short name of directory file name) | Mandatory |
| 'BFOC'h | FCI Issuer Discretionary Data | Optional |
The SFI of Directory Elementary file (Tag '88') data object is required because it defines a link (short name) to a Directory Elementary File that reflects the structure of the DDF file (more on this below).
The FCI Issuer Discretionary Data object (Tag 'BFOC') is optional and contains information specific to the issuer of card applications grouped in a DDF file.
An important attribute of any DDF file is an EF file called a Directory Elementary File (DEF) file. The DEF file is a required file in the DDF directory. It defines the structure of the DDF file. Each DEF record generally contains several Application Template Data Objects (Tag '61'). The Application Template object stores the details of a single ADF or DDF file for which the DDF file we are considering is the parent. However, the content of the Application Template data object is different for ADF and DDF files.
In the case of an ADF file, the Application Template object stores two required data objects: ADF Name (Tag '4F') and Application Label (Tag '50'). Optionally, the Application Template can also contain Application Preferred Name, Issuer Code Table Index, and Application Priority Indicator data objects.
Recall that the data field of the ADF Name object is either equal to the AID of the application whose data is stored in the ADF file, or starts with the AID.
In the case of a DDF file, the Application Template contains a single DDF Name data object (Tag '9D') and does not contain any optional data objects.
Rice. 3.7 demonstrates what has been said above regarding the structure of the Application Template and the AEF Data Template DEF file.
Note that Application Template objects for an ADF or DDF file may contain Directory Discretionary Template objects (Tag '73') that define data useful from the point of view of the issuer of applications located in the appropriate IPC directories.
Rice. 3.7. DEF file record structure
