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):||15 January 2018|
|PDF File Size:||15.17 Mb|
|ePub File Size:||1.38 Mb|
|Price:||Free* [*Free Regsitration Required]|
ISO/IEC – Wikipedia
Sign up or log in Sign up using Google. For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information. How do I distinguish different ISO cards? Or is there any smarter way to do it?
Probably the best course of action will be to implement a “pragmatic” approach: But still, the ATS has some useful information.
Should I just try some commands from Mifare Plus command set and check if I get correct replies? So you know you will need to use different card driver. Email Required, but never shown. Keep in mind that your goal is to connect two applications, one in the card and one in your computer. Sign up using Facebook. Complete communication stack will look like this: There is no smarter way. Sign up using Email and Password.
If not, there will isl errors on that level.
On top of it there are implemented interfaces of different cards and if both sides: What is the recommended way to ieo between them? 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.
I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards.
Or other cards with different command sets i. Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. Alexandr Zarubkin 4 Isk are different smart cards supporting ISO For example, Mifare Plus with its native command set. Now how to do it: Okay, I’ve come with my own answer. Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service?