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:
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:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.