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):||18 October 2013|
|PDF File Size:||3.69 Mb|
|ePub File Size:||16.42 Mb|
|Price:||Free* [*Free Regsitration Required]|
Sign up using Facebook. Email Required, but never shown. Alexandr Zarubkin 4 If not, there will be errors on that level. Use SAK only for non cards e.
smartcard – How do I distinguish different ISO cards? – Stack Overflow
How do I distinguish different ISO cards? If you have two applications which wants to communicate try one and then try second. 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. Sign up using Email and Password.
For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information.
There is no smarter way. Probably the best course of action will be to implement a “pragmatic” approach: Now how to do it: Or is there any smarter way to do it? Should I just try some commands from Mifare Plus command set and check if I get correct replies? On top of it there are implemented interfaces of different cards and if both sides: I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards. Keep in mind that your goal is to connect two applications, one in the card and one in your computer.
Sign up or log in Sign up using Google. Post as a guest Name.
What is the recommended way to distinguish between them? Only way how to think about card and don’t 144434- crazy is imagine it like it is full communication stack see OSI model. Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service?
During the connection protocol some parameters are exchanged that you can isoo to determine the card’s capabilities.
ATS is also bad practice as different card vendor can set it differently. There are different smart cards supporting ISO Ios other cards with different command sets i.
So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i.
But still, the ATS has some useful information.