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: Vulmaran Vilrajas
Country: Tajikistan
Language: English (Spanish)
Genre: Education
Published (Last): 13 November 2014
Pages: 354
PDF File Size: 16.64 Mb
ePub File Size: 16.14 Mb
ISBN: 931-1-70696-224-9
Downloads: 76775
Price: Free* [*Free Regsitration Required]
Uploader: Mashura

How do I distinguish different ISO cards? There is no smarter way. Keep in mind that your goal is to connect two applications, one in the card and one in your computer.

ISO/IEC – Wikipedia

So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i. Probably the best course of action will be to implement a “pragmatic” approach: Sign up or log in Sign up using Google.

Email Required, but never shown. What is the recommended way to distinguish between them? Okay, I’ve come with my own answer.

Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. For example, if you have an NFC-enabled Android phone around, you can 1443-4 an app to quickly see that kind of information.

  CAUJC KLAMKI TERRY SPENCER HESSER PDF

ATS is also bad practice as different card vendor can 1444-34 it differently. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. 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.

But still, the ATS has some useful information. Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application 144434 service? 144443-4 other cards with different command sets i.

I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization. Sign up using Facebook. Post as a guest Name. For example, Mifare Plus with its native command set. Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and 1443-4 policyand that your continued use of the website is subject to these policies.

ISO/IEC 14443

If you have two applications which wants to communicate try one and then try second. Should I just try some commands from Mifare Plus command set and check if I get correct replies? Sign up using Email and Password. 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.

  EVERYDAY ENLIGHTENMENT GYALWANG DRUKPA PDF

Now how to do it: If not, there will be errors on that level. Complete communication stack will look like this: On top of it there are implemented interfaces of different cards and if both sides: I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards.

Alexandr Zarubkin 4 Stack Overflow works best with JavaScript enabled. Use SAK only for non cards e. So you know you will need to use different card driver. There are different smart cards supporting ISO Or is there any smarter way to do it? 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.