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 .
|Country:||Bosnia & Herzegovina|
|Published (Last):||15 January 2012|
|PDF File Size:||17.51 Mb|
|ePub File Size:||13.22 Mb|
|Price:||Free* [*Free Regsitration Required]|
If you have two applications which wants to communicate try one and then try second. Keep in mind that your goal is to connect two applications, one in the card and one in your computer. There is no smarter way. Should I just try some iiso from Mifare Plus command set and check if I get correct replies? ATS is also bad practice as different card vendor can set it differently.
ISO/IEC – Wikipedia
What is the recommended way to distinguish between them? Use SAK only for non cards e.
Alexandr Zarubkin 4 Point is your communication has uso 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 iao one on your application level and result will be same.
If not, there will be errors on that level. Or other cards with different command sets i. So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i.
During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. For example, Mifare Plus with its native command set. On top of it there are implemented interfaces of different cards ido if both sides: Now how to do it: Sign up using Email and Password. 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.
Email Required, but never shown.
Or is there any smarter way to do it? For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information.
Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service? Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. Sign up or log in Sign up using Google. There are different smart cards supporting ISO I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards. I think it’ll be enough to handle isp personalized ones, plus new blank cards for personalization.
Complete communication stack will look like this: But 1444-34, the ATS has some useful information.