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 .
| Author: | Vom Jumi |
| Country: | Germany |
| Language: | English (Spanish) |
| Genre: | Finance |
| Published (Last): | 22 June 2005 |
| Pages: | 234 |
| PDF File Size: | 8.38 Mb |
| ePub File Size: | 2.16 Mb |
| ISBN: | 436-3-89977-398-6 |
| Downloads: | 26756 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Grokora |
Stack Overflow works best with JavaScript enabled. So you know you will need to use io card driver. So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i.
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? Email Required, but never shown. How do I distinguish different ISO cards?
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?
By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. Keep in mind that your goal is to connect two applications, one in the card and one in your computer. Okay, I’ve come with my own answer. There are different smart cards supporting ISO Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model.
During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. Sign up using Facebook.
ISO/IEC 14443
Sign up or log in Sign up using Google. For example, Mifare Plus with its native command set.
Point is your communication has to succed on 1444-34 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 14443-44 will be same. Sign up using Email and Password. I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization. Or other cards with different command sets i.
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.
ISO/IEC – Wikipedia
Post as a 1444-4 Name. Probably the best course of action will be to implement a “pragmatic” approach: Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies. By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.
There is no smarter way. But still, the ATS has some useful information.
On top of it there are implemented interfaces uso different cards and if both sides: Or is there any smarter way to do it? Complete communication stack will look like this: Use SAK only for non cards e. Now how to do it: Will your reader 14443-4 have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service? Alexandr Zarubkin 4 For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information.