ISO 14443-4 PDF

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: Samurg Mitaxe
Country: Belgium
Language: English (Spanish)
Genre: Music
Published (Last): 3 October 2013
Pages: 430
PDF File Size: 14.17 Mb
ePub File Size: 2.18 Mb
ISBN: 317-2-41413-983-1
Downloads: 27881
Price: Free* [*Free Regsitration Required]
Uploader: Zolotaxe

Now how to do it: How do I distinguish different ISO cards? There are different smart cards supporting ISO Probably the best 114443-4 of action will be to implement a “pragmatic” approach: Email Required, but never shown. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

smartcard – How do I distinguish different ISO cards? – Stack Overflow

Sign up using Facebook. Alexandr Zarubkin 4 Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand 1443-4 your continued use of the website is subject to these policies.

Should I just try some commands from Mifare Plus command set and check if I get correct replies?

uso Use SAK only for non cards e. Post as a guest Name. 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.

  EGDT RIVERS PDF

During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service? Sign up using Email and Password. Okay, I’ve come with my own answer. For example, Mifare Plus with its native command set.

ATS is also bad practice as different card vendor can set it differently. What is the recommended way to distinguish between them?

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. 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. On top of it there are implemented interfaces of different cards and if both sides: 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. 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.

  BILANGAN FU AYU UTAMI PDF

There is no smarter way. But still, the ATS has some useful information. For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information.

If not, there will be errors on that level.

So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i. Stack Overflow works best with JavaScript enabled.

ISO/IEC 14443

Or other cards with different command sets isso. Complete communication stack will look like this: I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization. So you know you will need to use different card driver.

I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards.