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: Bralkree Tajinn
Country: Turkmenistan
Language: English (Spanish)
Genre: History
Published (Last): 5 April 2006
Pages: 11
PDF File Size: 2.4 Mb
ePub File Size: 11.62 Mb
ISBN: 977-1-12123-719-6
Downloads: 9762
Price: Free* [*Free Regsitration Required]
Uploader: Vishakar

I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization. How do I distinguish different ISO cards?

ISO/IEC 14443

ATS is also bad practice as different card vendor can set it differently. So you know you will need to use different card driver.

Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a izo application or service? Or is there any smarter way to do it?

Sign up or log in Sign up using Google. For example, Mifare Plus with its native command set.

ISO/IEC – Wikipedia

Sign up using Email and Password. Or other cards with different command sets i. Should I just try some commands from Mifare Plus command set and check if I get correct replies? Stack Overflow works best with JavaScript enabled.

  GANAMRUTHA VARNAMALIKA PDF

Alexandr Zarubkin 4 During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. Complete communication stack will look like this: Okay, I’ve come with my own answer.

Probably the best course of action will be to implement a “pragmatic” approach: Keep in oso that 1443-4 goal is to 144434 two applications, one in the card and one in your computer.

Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of service1443-4 policy and cookie policyand that your continued use of the website is subject to these policies. Post as a guest Name. 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.

Use SAK only for non cards e. On top of it there are ido interfaces of different cards and if both sides: Email Required, but never shown.

If not, there will be errors on that level. Sign up using Facebook. I think that the whole 114443-4 of ISO is to provide a generic way to exchange information with different cards.

  JONATHAN KOZOL SHAME OF THE NATION PDF

What is the recommended way to distinguish between them? If you have two applications which wants to communicate try one and then try second. For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information.

There is no smarter way. 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. So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i. But still, the ATS has some useful information. There are different smart cards supporting ISO Now how to do it: By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

By clicking “Post Your Ieo, 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.