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):||13 November 2014|
|PDF File Size:||16.64 Mb|
|ePub File Size:||16.14 Mb|
|Price:||Free* [*Free Regsitration Required]|
How do I distinguish different ISO cards? There is no smarter way. Keep in mind that your goal is to connect two applications, one in the card and one in your computer.
ISO/IEC – Wikipedia
So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i. Probably the best course of action will be to implement a “pragmatic” approach: Sign up or log in Sign up using Google.
Email Required, but never shown. What is the recommended way to distinguish between them? Okay, I’ve come with my own answer.
Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. For example, if you have an NFC-enabled Android phone around, you can 1443-4 an app to quickly see that kind of information.
But still, the ATS has some useful information. Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application 144434 service? 144443-4 other cards with different command sets i.
Now how to do it: If not, there will be errors on that level. Complete communication stack will look like this: 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.