Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob

CIPURSE™ file structure

CIPURSE™ file structure

First comment on blog 250 sign-ins 25 likes received

One fine morning as I was scanning my ID card at the entrance of my office, I wondered how data is structured in the ID card. I then explored to find some information about this and came across the file structure that can be used to implement an application on a card. In this blog we will understand how a CIPURSE™ application can be implemented.

In the previous blog, we discussed about the CIPURSE™ open standards and Infineon’s offerings for CIPURSE™ compliant products. We now know what features are provided by these products, let us understand how an application of access management can be implemented. The basic idea of this use case is that the reader reads some data from the card and then either grants or rejects access to a building or a room. Any of the L, S and T profile compliant products can be used for this application.

Let us consider a scenario, where a user wants to use smart card to access building 'A'. This scenario can be implemented as follows:

  1. Create a CIPURSE™ application for access management.
  2. Under this application file, create a binary file to store user data such as name, number etc. and create a linear record file to store user specific identification data such as ID number, validity, access permissions etc.
  3. Once the card is issued with this information, the user can use it to scan at the entrance of the building.
  4. If the access permission to enter building ‘A’ is defined in the application’s files, the door is opened and the user can enter the building, else the user cannot enter the building. 

Now, let us consider a scenario where the user wants to use the same card for access management and micro-payment at a store. In this case, S and T profile compliant products can be used as they support multi-application use cases. This scenario can be implemented as follows:

  1. Create two CIPURSE™ applications, one corresponding to access management and another corresponding to micro-payment. 
  2. The access management application can be same as discussed above.
  3. Under the micro-payment CIPURSE™ application, create a binary file to store user data, a value-record file to store the purse value, and a cyclic record file to store the latest transaction history. 
  4. With these applications, when the card is used at the entrance of a building, the access management application is selected based on the application ID. The user can enter the building if the right access permissions are present in the application’s files, else the user cannot enter the building.
  5. If the user uses this card at the store, then the micro-payment application is selected based on the application ID. The value-record file is updated based on the transaction amount and the cyclic record file is updated to include the latest transaction details.

Figure 1 shows the CIPURSE™ application file structure for this scenario.



Figure 1. File structure for multi-application use case

This is how a single or multiple CIPURSE™ applications can be implemented on a CIPURSE™ compliant card. For more information on this, refer the following link.