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):||1 February 2012|
|PDF File Size:||8.47 Mb|
|ePub File Size:||14.84 Mb|
|Price:||Free* [*Free Regsitration Required]|
Use SAK only for non cards e. Keep in mind that your goal is to connect two applications, one in the card and one in your computer. If not, there will be errors on that level.
Email Required, but never shown. Should I just try some commands from Mifare Plus command set and check if I get correct replies?
smartcard – How do I distinguish different ISO cards? – Stack Overflow
Sign up using Facebook. On 1443-4 of it there are implemented interfaces of different cards and if both sides: Complete communication stack will look like this: 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.
Okay, I’ve come with my own answer. ATS is also bad practice as different card vendor can set it differently.
So you know you will need to use different 144443-4 driver. What is the recommended way to distinguish between them?
Alexandr Zarubkin 4 Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service? How do I distinguish different ISO cards?
For example, if you have an NFC-enabled Android phone around, you can install an app to 114443-4 see that kind of information. Now how to do it: But still, the ATS has some useful information.
So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i. There are different smart cards supporting ISO Probably the best course of action will be to implement a “pragmatic” approach: During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. I think that the whole purpose of ISO kso to provide a generic way to exchange information with different cards.
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.
ISO/IEC – Wikipedia
Sign up using Email and Password. Sign up or log in Sign up using Google.