Thank you for your answer.
I found that :
Contactless cards do NOT provide a real ATR. Instead, a pseudo-ATR generated by the PC/SC driver that connect your smartcard reader to applications is return (the value which I get when use reader to read the card), for example:
The pseudo-ATR (not generated or "returned" by the card) is used to pass (otherwise inaccesible) information about the contactless protocol to the application layer. As Android does not use PC/SC for access to smartcards through NFC there is also no ATR involved here.
But I still have questions:
1. If contactless cards dose not return ATR and pseudo-ATR is used to pass information about contactless protocol then what information I can get?
2. As I read in ISO 7816, if cards support extended length it should be store in ATR, but if in case contactless card ATR is not not real or returned by card then how can i get such kind of information.
I also read about definitions of ATS (answer-to-select) for type A (which comes close to an ATR as in that it also contains historical bytes) and an answer-to-ATTRIB for type B.
But I still do not have clear understanding about these definitions.
Could you give some documents that specify these matters!
Thank you very much for your support.