JavaCard OS

Hello, I have a new question about T0 ATR. When I send chained blocks, a mismake happened. The commands are:
OUT 63 00 00 00 00 00 69 00 00 00
IN 81 00 00 00 00 00 69 01 00 00
OUT 62 00 00 00 00 00 6a 00 00 00
IN 80 13 00 00 00 00 6a 00 00 00 3b 9c 95 80 1f 03 90 67 46 4a 01 01 38 06 00 00 00 00 50
OUT 61 05 00 00 00 00 6b 00 00 00 95 00 00 0a 00
IN 82 07 00 00 00 00 6b 00 00 00 95 00 00 0a 00
OUT 6f 05 00 00 00 00 6c 00 00 01 00 a4 04 00 00
IN 80 16 00 00 00 00 6c 00 00 01 00 00 a5 50 73 4a 06 07 2a 86 48 86 fc 6b 01 60 0c 06 0a 2a 86 48
OUT 6f 05 00 00 00 00 6d 00 10 00 00 00 00 00 00
IN 80 16 00 00 00 00 6d 00 00 03 00 00 00 00 00 86 fc 6b 02 02 01 01 63 09 06 07 2a 86 48 86 fc 6b
OUT 63 00 00 00 00 00 6e 00 00 00
IN 81 00 00 00 00 00 6e 01 00 00
The 8st byte is 0x10, that's means this abData field of the out block should be empty. Where the 5 bytes '00' are come form? And how to process them?

The response command to '61' was wrong. When I corrected this error, this phenomenon did not recur.

There are two variables： IFSC and maxCCIDmessageLength in In CCID class descripter. Which factor plays a decisive role in determining the length of CCID subcontracting?

The IFSC is dedicated to T=1. For APDU level, maxCCIDMessageLenth decided fsc length. In fact，we can send any length by only need to take care of this length smaller than maxCCIDmessageLength.

For APDU level, do we need achieve T0 envelope commands ?

yes， T0 evelope command is packaged by application Layer on PC.The tool does not determine if the device is an APDU level. If I want extend APDU, I should implement envelope command.

There is a new way to implement T0 extend APDU. Applet can send T0 envelope command by ThrowIt function. In this way, whether the card support T0 or not, applet can simulate T0 extend APDU.