ISO 14443-4 PDF

June 25, 2020 0 By admin

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: Nesho Mikataur
Country: Albania
Language: English (Spanish)
Genre: Business
Published (Last): 1 January 2008
Pages: 16
PDF File Size: 18.59 Mb
ePub File Size: 8.51 Mb
ISBN: 743-9-53798-559-2
Downloads: 11231
Price: Free* [*Free Regsitration Required]
Uploader: Shazuru

By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. There are different smart cards supporting ISO For example, Mifare Plus with its native command set.

Or other cards with different command sets i.

I develop some software for a card reader and I need to identify which commands the card supports for example, iao it supports commands in ISO structure or not. What is the recommended way to distinguish between them? Should I just try some commands from Mifare Plus command set and check if I get correct replies?

Or is there any smarter way to do isso During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. Use SAK only for non cards e.

  GRAHAM ROBB RIMBAUD PDF

ISO/IEC – Wikipedia

ATS is also bad practice as different card vendor can set it differently. Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. Keep in mind that your goal is to connect two applications, one in the card and one in your computer.

On top of it there are implemented interfaces of different cards and if both sides: If not, there will be errors on that level. So you know you will need to use different card driver. 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.

By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy 114443-4 and cookie policyand that your continued use of the website is subject to these policies.

How do Jso distinguish different ISO cards? Alexandr Zarubkin 4 Probably the best course of action will be to implement a “pragmatic” approach: Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service? I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization.

  COMPUTOS Y PRESUPUESTOS CHANDIAS PDF

Okay, I’ve come with my own answer. I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards.

So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i. 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 isoo quickly see that kind of information.

ISO/IEC 14443

Now how to do it: Complete communication stack will look like this: If you have two applications which wants to communicate try one and then try second.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.

Post as a guest Name. Email Required, but never shown. Post Your Answer Discard 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.

Stack Overflow works best with JavaScript enabled.