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):||20 June 2004|
|PDF File Size:||11.40 Mb|
|ePub File Size:||17.2 Mb|
|Price:||Free* [*Free Regsitration Required]|
Should I just try some commands from Mifare Plus command set and check if I get correct replies? If not, there will be errors on that level.
ATS is also bad practice as different card vendor can set it differently. What is the recommended way to distinguish between them?
Sign up or log in Sign up using Google. There are different smart cards supporting ISO Probably the best course of action will be to implement a “pragmatic” approach: I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards.
Email Required, but never shown. Okay, I’ve come with my own answer.
144434 do I distinguish different ISO cards? During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i. Use SAK only for non cards e. I develop some software for a card reader and I 144434 to identify which commands the card supports for example, if it supports commands in ISO structure or not.
ISO/IEC – Wikipedia
Or other cards with different command sets i. Post as a guest Name. For example, Mifare Plus with its native command set. So you know you will need to use different card driver. Now how to do it: Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model.
smartcard – How do I distinguish different ISO cards? – Stack Overflow
I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization. Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service?
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.
On top of it there are implemented interfaces of different cards and if both sides: 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.
Alexandr Zarubkin 4 Sign up using Facebook.