ETSI TS 102 127-2018 Smart Cards Transport protocol for CAT applications Stage 2 (V14 0 0 Release 14).pdf

1、 ETSI TS 102 127 V15.0.0 (2018-07) Smart Cards; Transport protocol for CAT applications; Stage 2 (Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 102 127 V15.0.0 (2018-07)2Release 15Reference RTS/SCP-T0015rcvf00 Keywords protocol, smart card, transport ETSI 650 Route des Lucioles F-06921 Sophia Ant

2、ipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present

3、document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions

4、and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the curren

5、t status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part

6、 may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoi

7、ng restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organiza

8、tional Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 102 127 V15.0.0 (2018-07)3Release 15Contents Intellectual Property Rights 8g3Foreword . 8g3Modal verbs terminology 8g31 Scope 9g32 Re

9、ferences 9g32.1 Normative references . 9g32.2 Informative references 10g33 Definitions, symbols, abbreviations and coding conventions 10g33.1 Definitions 10g33.2 Symbols 11g33.3 Abbreviations . 11g33.4 Coding conventions 11g34 Description . 11g35 CAT_TP layer 12g35.0 Layers presentation. 12g35.1 Dat

10、a communication. 13g35.2 Segmentation management . 13g35.2.1 Segmentation and re-assembly . 13g35.2.1.0 Segmentation behaviour 13g35.2.1.1 N-SDU and N-PDU when segmentation is needed . 14g35.2.1.2 N-SDU and N-PDU when no segmentation 14g35.2.2 Limitations 14g35.2.3 CAT_TP segmentation management 14g

11、35.3 Transport management . 15g35.3.1 CAT_TP connection management 15g35.3.1.0 Connection description 15g35.3.1.1 Opening a connection 16g35.3.1.2 Ports 16g35.3.1.3 Connection states 16g35.3.1.3.0 Connection states presentation 16g35.3.1.3.1 CLOSED state . 16g35.3.1.3.2 LISTEN state. 17g35.3.1.3.3 S

12、YN-SENT state . 17g35.3.1.3.4 SYN-RCVD state 17g35.3.1.3.5 OPEN state 17g35.3.1.3.6 CLOSE-WAIT state 17g35.3.1.4 Connection record . 17g35.3.1.4.0 Overview . 17g35.3.1.4.1 STATE. 17g35.3.1.4.2 Variables for CAT_TP sending activity 17g35.3.1.4.3 Variables for CAT_TP receiving activity 18g35.3.1.4.4 V

13、ariables from current PDU 18g35.3.1.4.5 Variables from SYN PDU . 18g35.3.1.5 Closing a connection . 18g35.3.1.6 Detecting a Half-Open and/or inactive connection . 19g35.3.1.7 Version Number Management 19g35.3.2 Reliable Communication 19g35.3.2.0 Reliability mechanisms . 19g35.3.2.1 Sequence number 1

14、9g35.3.2.2 Checksum 19g35.3.2.3 Positive acknowledgement of PDUs . 20g35.3.2.4 Retransmission timeout . 20g35.3.3 Flow control and window management 20g35.4 Events processing . 21g3ETSI ETSI TS 102 127 V15.0.0 (2018-07)4Release 155.4.0 Overview 21g35.4.1 Upper layer events 23g35.4.1.0 Introduction .

15、 23g35.4.1.1 Open request . 23g35.4.1.2 Close request . 26g35.4.1.3 Receive request . 29g35.4.1.4 Send request 31g35.4.2 PDU arrival events 35g35.4.2.0 PDU pre-treatment 35g35.4.2.1 Initial state: CLOSE 35g35.4.2.2 Initial state: OPEN 36g35.4.2.3 Initial state: LISTEN . 40g35.4.2.4 Initial state: SY

16、N-SENT . 41g35.4.2.5 Initial state: SYN-RCVD 42g35.4.2.6 Initial state: CLOSE-WAIT 45g35.4.3 Timeout events 45g35.4.3.0 Timeout description 45g35.4.3.1 Retransmission timeout . 46g35.4.3.2 Close-wait timeout 47g35.5 Identification 47g35.6 CAT_TP header format 48g35.6.0 CAT_TP header description . 48

17、g35.6.1 First octet 49g35.6.2 Header length 49g35.6.3 Source and destination ports . 49g35.6.4 Data length 50g35.6.5 Sequence number 50g35.6.6 Acknowledgement number . 50g35.6.7 Window size . 50g35.6.8 Checksum . 50g35.6.9 Variable header area . 50g35.6.10 RFU field 50g35.7 SYN PDU . 51g35.7.0 SYN P

18、DU description . 51g35.7.1 SYN PDU fields . 51g35.7.1.1 Data length 51g35.7.1.2 Sequence number 51g35.7.1.3 Acknowledgment number . 51g35.7.1.4 Maximum PDU size 52g35.7.1.5 Maximum SDU size 52g35.7.1.6 Identification . 52g35.8 ACK PDU 52g35.8.0 ACK PDU description 52g35.8.1 ACK PDU field . 53g35.8.1

19、.1 Data length 53g35.8.1.2 Sequence number 53g35.8.1.3 Acknowledgment number . 53g35.9 EACK PDU 54g35.9.0 EACK PDU description 54g35.9.1 EACK PDU Field . 55g35.9.1.1 Data length 55g35.9.1.2 Sequence number 55g35.9.1.3 Acknowledgment number . 55g35.9.1.4 Variable header area 55g35.10 RST PDU 55g35.10

20、.0 RST PDU description . 55g35.10.1 RST PDU fields 56g35.10.1.1 Data length 56g35.10.1.2 Sequence number 56g35.10.1.3 Acknowledgment number . 56g35.10.1.4 Reason code 56g35.11 NUL PDU . 57g3ETSI ETSI TS 102 127 V15.0.0 (2018-07)5Release 155.11.0 NUL PDU description 57g35.11.1 NUL PDU fields . 57g35.

21、11.1.1 Data length 57g35.11.1.2 Sequence number 57g35.11.1.3 Acknowledgment number . 57g35.11.1.4 Variable header area 58g35.12 Header flags combinations . 59g36 Implementation on BIP 60g36.1 Sending and receiving data . 60g36.2 Timers 60g3Annex A (informative): Scenarios examples 61g3A.1 Connection

22、 establishment. 61g3A.2 Lost PDUs 61g3A.3 PDUs received out of order 62g3A.4 Communication over long delay path. 62g3A.5 Communication over long delay path with lost PDUs . 63g3A.6 Detecting a half open connection on crash recovery 63g3A.7 Detecting a half open connection from the active side . 64g3

23、A.8 Dynamic window management 64g3Annex B (informative): CAT_TP-Upper layer interface definition . 66g3B.0 Introduction 66g3B.1 OPEN . 66g3B.2 Send 67g3B.3 Receive . 67g3B.4 CLOSE . 67g3B.5 Status 68g3Annex C (informative): Change history . 69g3History 70g3ETSI ETSI TS 102 127 V15.0.0 (2018-07)6Rele

24、ase 15List of figures Figure 1: Environment description 12g3Figure 2: CAT_TP layer position 12g3Figure 3: CAT_TP layer description .13g3Figure 4: PDUs exchange between two Layers N .13g3Figure 5: N-SDU and N-PDU with segmentation .14g3Figure 6: N-SDU and N-PDU with no segmentation 14g3Figure 7: Segm

25、entation description .15g3Figure 8: CAT_TP functional state machine .16g3Figure 9: Open Request in OPEN, LISTEN, SYN-SENT, SYN-RCVD state 23g3Figure 10: Open request in CLOSE-WAIT state .24g3Figure 11: Open request in CLOSED state .25g3Figure 12: Close request in Open state 26g3Figure 13: Close requ

26、est in CLOSE state 26g3Figure 14: Close request in CLOSE-WAIT state 27g3Figure 15: Close request in SYN-SENT or SYN-RCVD state 27g3Figure 16: Close request in LISTEN state .28g3Figure 17: Receive request in OPEN state 29g3Figure 18: Receive request in CLOSE state 30g3Figure 19: Receive request in CL

27、OSE-WAIT state 30g3Figure 20: Receive request in LISTEN, SYN-SENT or SYN-RCVD state 31g3Figure 21: Send data request in OPEN state .32g3Figure 21a: Send NUL request in OPEN state 33g3Figure 22: Send request in CLOSE, LISTEN, SYN-SENT or SYN-RCVD state.34g3Figure 23: Send request in CLOSE-WAIT state

28、.34g3Figure 24: CLOSE state PDU arrival event processing.35g3Figure 25: OPEN state PDU arrival event processing 1/4 .36g3Figure 26: OPEN state PDU arrival event processing 2/4 .37g3Figure 27: OPEN state PDU arrival event processing 3/4 .38g3Figure 28: OPEN state PDU arrival event processing 4/4 .39g

29、3Figure 29: LISTEN state PDU arrival event processing .40g3Figure 31: SYN-RCVD state PDU arrival event processing 1/4 .42g3Figure 32: SYN-RCVD state PDU arrival event processing 2/4 .43g3Figure 33: SYN-RCVD state PDU arrival event processing 3/4 .43g3ETSI ETSI TS 102 127 V15.0.0 (2018-07)7Release 15

30、Figure 34: SYN-RCVD state PDU arrival event processing 4/4 .44g3Figure 35: CLOSE-WAIT state PDU arrival event processing .45g3Figure 36: PDU retransmission timeout 46g3Figure 37: CLOSE-WAIT timeout 47g3Figure 38: CAT_TP header format .48g3Figure 39: First octet bits description 49g3Figure 40: SYN PD

31、U structure .51g3Figure 41: ACK PDU structure .52g3Figure 42: EACK PDU structure .54g3Figure 43: RST PDU structure 55g3Figure 44: NUL PDU structure .57g3Figure 45: PDU Flags possible combinations .59g3ETSI ETSI TS 102 127 V15.0.0 (2018-07)8Release 15Intellectual Property Rights Essential patents IPR

32、s essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or

33、potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETS

34、I. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted

35、 and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by E

36、TSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Smart Card Platform (SCP). The contents of the present document are subject to continuing work within TC SCP and may change following

37、formal TC SCP approval. If TC SCP modifies the contents of the present document, it will then be republished by ETSI with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x: the first digit: 0 early working draft; 1 presented to TC SCP for info

38、rmation; 2 presented to TC SCP for approval; 3 or greater indicates TC SCP approved document under change control. y: the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z: the third digit is incremented when editorial only changes ha

39、ve been incorporated in the document. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression o

40、f provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 102 127 V15.0.0 (2018-07)9Release 151 Scope The present document defines the stage two description of the Card Application Toolkit Transport Protocol (CAT_TP), for CAT applicat

41、ions based on ETSI TS 102 223 2. The present document contains the core functionalities for the CAT_TP between two CAT_TP entities hosting for instance on a UICC and on a remote entity. The CAT_TP described in the present document is based on RDP version 2 as specified in IETF RFC 908 4 and IETF RFC

42、 1151 5. The present document describes, according requirements defined in ETSI TS 102 124 1: The core functionalities of CAT_TP (data structures, state diagrams, protocol procedures, etc.). Usage of CAT_TP on top of the Bearer Independent Protocol (BIP). The following items are out of the scope of

43、the present document: The specific implementation of an API. Anything dealing with the security above CAT_TP. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, onl

44、y the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference/. In the case of a

45、 reference to a TC SCP document, a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. Th

46、e following referenced documents are necessary for the application of the present document. 1 ETSI TS 102 124: “Smart Cards; Transport Protocol for UICC based Applications; Stage 1 (Release 6)“. 2 ETSI TS 102 223: “Smart Cards; Card Application Toolkit (CAT) (Release 7)“. 3 IETF RFC 793 (1981): “Tra

47、nsmission Control Protocol“. 4 IETF RFC 908 (1984): “Reliable Data Protocol“. 5 IETF RFC 1151 (1990): “Version 2 of the Reliable Data Protocol (RDP)“. ETSI ETSI TS 102 127 V15.0.0 (2018-07)10Release 152.2 Informative references References are either specific (identified by date of publication and/or

48、 edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. In the case of a reference to a TC SCP document, a non-specific reference implic

49、itly refers to the latest version of that document in the same Release as the present document. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TR 102 216: “Smart cards; Vocabulary for Smart Card Platform specifications“. i.2 ETSI TS 102 221: “Smart Cards; UICC-Terminal interface; Phys