ISO/IEC (E). PDF disclaimer. This PDF file may contain embedded typefaces. In accordance with Adobe’s licensing policy, this file. Reference number. ISO/IEC (E). Fourth edition. Permission can be requested from either ISO at the address below or ISO’s. During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. For example, the SAK byte will inform the .
|Published (Last):||3 October 2013|
|PDF File Size:||14.17 Mb|
|ePub File Size:||2.18 Mb|
|Price:||Free* [*Free Regsitration Required]|
smartcard – How do I distinguish different ISO cards? – Stack Overflow
Should I just try some commands from Mifare Plus command set and check if I get correct replies?
During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service? Sign up using Email and Password. Okay, I’ve come with my own answer. For example, Mifare Plus with its native command set.
ATS is also bad practice as different card vendor can set it differently. What is the recommended way to distinguish between them?
Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. Sign up or log in Sign up using Google. I develop some software for a card reader and I need to identify which commands the card supports for example, if it supports commands in ISO structure or not. On top of it there are implemented interfaces of different cards and if both sides: If you have two applications which wants to communicate try one and then try second.
Keep in mind that your goal is to connect two applications, one in the card and one in your computer. Point is your communication has to succed on all levels so don’t worry to try to communicate with card by not compatible protocol – if you by some miracle will not get error on CardProtocol level you will definitely get one on your application level and result will be same.
There is no smarter way. But still, the ATS has some useful information. For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information.
If not, there will be errors on that level.
Or other cards with different command sets isso. Complete communication stack will look like this: I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization. So you know you will need to use different card driver.
I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards.