Identification cards — Transport layer topologies — Configuration for HCI/HCP interchange

This document specifies the requirements for a protocol derived from HCI/HCP (see ETSI TS 102 622) enabling communication for devices regardless of data link and physical layers. This document covers the following: a) outline of a system comprised of one or more hosts and one controller; b) extension of connection topology between hosts and host controller (i.e. star topology and additional other topologies); c) segregation between existing system using ETSI TS102 613 and new system compliant to this document (this document refers ETSI TS 102 613, but does not change its specification and does not use RFU). For ETSI TS 102 622, data link layer and physical layer like SWP specified in ETSI TS 102 613 is out of the scope. Albeit questioned in this document, the duplication of OSI transport layer by e.g. enforcing encapsulation of HCP into T=1 or the reverse, is out of the scope.

Cartes d'identification — Topologies de la couche transport — Configuration pour les échanges HCI/HCP

General Information

Status
Published
Publication Date
26-May-2021
Current Stage
9060 - Close of review
Start Date
02-Dec-2027
Ref Project

Buy Standard

Technical specification
ISO/IEC TS 22924:2021 - Identification cards -- Transport layer topologies -- Configuration for HCI/HCP interchange
English language
26 pages
sale 15% off
Preview
sale 15% off
Preview
Technical specification
ISO/IEC TS 22924:2021 - Identification cards — Transport layer topologies — Configuration for HCI/HCP interchange Released:5/27/2021
English language
26 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


TECHNICAL ISO/IEC TS
SPECIFICATION 22924
First edition
2021-05
Identification cards — Transport layer
topologies — Configuration for HCI/
HCP interchange
Cartes d'identification — Topologies de la couche transport —
Configuration pour les échanges HCI/HCP
Reference number
©
ISO/IEC 2021
© ISO/IEC 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2021 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms .2
5 Architecture .4
5.1 System architecture view . 4
5.1.1 General. 4
5.1.2 Hosts . 5
5.1.3 Gates . 5
5.1.4 Pipes . 6
5.1.5 Host controller . 7
5.1.6 General aspects on APDU gate . 7
5.2 System architecture with legacy COS . 8
6 Configuration requirements.9
6.1 General . 9
6.2 Logical components of an APDU-enabled host . 9
6.3 Gates registry . 9
6.3.1 General. 9
6.3.2 Administration gate registry .10
6.3.3 Link management gate .11
6.3.4 Identity management gate . .12
6.3.5 Loop back gate .12
6.3.6 APDU gate .13
6.3.7 APDU application gate registry .13
6.4 Example of exchanging APDU via HCI/HCP .13
6.5 APDU transport versus HCP frames .14
6.5.1 General.14
6.5.2 Chaining of T=1 message blocks wrapping HCP packets .15
6.5.3 Handling of error recovery with T=1 features .15
6.6 APDU fragmentation .15
6.7 Supported set of commands and events .15
Annex A (informative) Examples of architecture variants .16
Annex B (informative) Background information .21
Bibliography .26
© ISO/IEC 2021 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives or www .iec .ch/ members
_experts/ refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/ patents) or the IEC
list of patent declarations received (see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/
iso/ foreword .html. In the IEC, see www .iec .ch/ understanding -standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and security devices for personal identification.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html and www .iec .ch/ national
-committees.
iv © ISO/IEC 2021 – All rights reserved

Introduction
This document is laid on the ground of ISO/IEC 7816 (all parts) specifying integrated circuit cards and
the use of such cards for interchange, and on ETSI TS 102 622 defining the HCI core that is an application
independent logical interface.
ETSI TS 102 622 is referenced in this document as a well-known HCI specification, however it should
be noted ETSI TS 102 622 describes another host network with the host controller implemented by
the CLF/NFC controller and with hosts residing on UICCs/SEs all connected to the host controller.
ETSI TS 102 622 allows for other interfaces than SWP for data link layer of HCI, and does not mandate
using the SWP but just describes the condition if the SWP is used.
© ISO/IEC 2021 – All rights reserved v

TECHNICAL SPECIFICATION ISO/IEC TS 22924:2021(E)
Identification cards — Transport layer topologies —
Configuration for HCI/HCP interchange
1 Scope
This document specifies the requirements for a protocol derived from HCI/HCP (see ETSI TS 102 622)
enabling communication for devices regardless of data link and physical layers. This document covers
the following:
a) outline of a system comprised of one or more hosts and one controller;
b) extension of connection topology between hosts and host controller (i.e. star topology and
additional other topologies);
c) segregation between existing system using ETSI TS 102 613 and new system compliant to this
document (this document refers ETSI TS 102 613, but does not change its specification and does not
use RFU).
For ETSI TS 102 622, data link layer and physical layer like SWP specified in ETSI TS 102 613 is out of
the scope.
Albeit questioned in this document, the duplication of OSI transport layer by e.g. enforcing encapsulation
of HCP into T=1 or the reverse, is out of the scope.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 7816-3, Identification cards — Integrated circuit cards — Part 3: Cards with contacts — Electrical
interface and transmission protocols
ISO/IEC 7816-4, Identification cards — Integrated circuit cards — Part 4: Organization, security and
commands for interchange
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
APDU gate
entry point to a service processing command APDU inside a host (3.6) or returning response APDU
3.2
APDU application gate
entry point to a service sending command APDU and retrieving correspondent response APDU
© ISO/IEC 2021 – All rights reserved 1

3.3
gate
entry point to a service that is operated inside a host (3.6)
[SOURCE: ETSI TS 102 622]
3.4
HCI network
star-topology network comprised of a host network (3.8) where hosts (3.6) are interconnected with a
host controller (3.7) through HCI
3.5
HCP stack
layout comprised of a routing layer, a messaging layer and a collection of gates (3.3)
3.6
host
logical entity that operates one or more service(s)
[SOURCE: ETSI TS 102 622]
3.7
host controller
host (3.6) that is also responsible for managing a host network (3.8)
[SOURCE: ETSI TS 102 622]
3.8
host network
network of two or more hosts (3.6)
[SOURCE: ETSI TS 102 622]
3.9
managing host
host (3.6) which is in charge of resolving conflicts and interoperability issues between different
contactless applications provided by different hosts
[SOURCE: ETSI TS 102 622]
3.10
pipe
logical communication channel between two gates (3.3) from different hosts (3.6)
[SOURCE: ETSI TS 102 622]
3.11
terminal host
host (3.6) allocated a static identifier HID '01'
4 Symbols and abbreviated terms
ADM_x arbitrary command for administration gate, see ETSI TS 102 622 clause 6.1, e.g. ADM_CRE-
ATE_PIPE
APDU application pro
...


TECHNICAL ISO/IEC TS
SPECIFICATION 22924
First edition
2021-05
Identification cards — Transport layer
topologies — Configuration for HCI/
HCP interchange
Cartes d'identification — Topologies de la couche transport —
Configuration pour les échanges HCI/HCP
Reference number
©
ISO/IEC 2021
© ISO/IEC 2021
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2021 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms .2
5 Architecture .4
5.1 System architecture view . 4
5.1.1 General. 4
5.1.2 Hosts . 5
5.1.3 Gates . 5
5.1.4 Pipes . 6
5.1.5 Host controller . 7
5.1.6 General aspects on APDU gate . 7
5.2 System architecture with legacy COS . 8
6 Configuration requirements.9
6.1 General . 9
6.2 Logical components of an APDU-enabled host . 9
6.3 Gates registry . 9
6.3.1 General. 9
6.3.2 Administration gate registry .10
6.3.3 Link management gate .11
6.3.4 Identity management gate . .12
6.3.5 Loop back gate .12
6.3.6 APDU gate .13
6.3.7 APDU application gate registry .13
6.4 Example of exchanging APDU via HCI/HCP .13
6.5 APDU transport versus HCP frames .14
6.5.1 General.14
6.5.2 Chaining of T=1 message blocks wrapping HCP packets .15
6.5.3 Handling of error recovery with T=1 features .15
6.6 APDU fragmentation .15
6.7 Supported set of commands and events .15
Annex A (informative) Examples of architecture variants .16
Annex B (informative) Background information .21
Bibliography .26
© ISO/IEC 2021 – All rights reserved iii

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives or www .iec .ch/ members
_experts/ refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/ patents) or the IEC
list of patent declarations received (see patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso .org/
iso/ foreword .html. In the IEC, see www .iec .ch/ understanding -standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and security devices for personal identification.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html and www .iec .ch/ national
-committees.
iv © ISO/IEC 2021 – All rights reserved

Introduction
This document is laid on the ground of ISO/IEC 7816 (all parts) specifying integrated circuit cards and
the use of such cards for interchange, and on ETSI TS 102 622 defining the HCI core that is an application
independent logical interface.
ETSI TS 102 622 is referenced in this document as a well-known HCI specification, however it should
be noted ETSI TS 102 622 describes another host network with the host controller implemented by
the CLF/NFC controller and with hosts residing on UICCs/SEs all connected to the host controller.
ETSI TS 102 622 allows for other interfaces than SWP for data link layer of HCI, and does not mandate
using the SWP but just describes the condition if the SWP is used.
© ISO/IEC 2021 – All rights reserved v

TECHNICAL SPECIFICATION ISO/IEC TS 22924:2021(E)
Identification cards — Transport layer topologies —
Configuration for HCI/HCP interchange
1 Scope
This document specifies the requirements for a protocol derived from HCI/HCP (see ETSI TS 102 622)
enabling communication for devices regardless of data link and physical layers. This document covers
the following:
a) outline of a system comprised of one or more hosts and one controller;
b) extension of connection topology between hosts and host controller (i.e. star topology and
additional other topologies);
c) segregation between existing system using ETSI TS 102 613 and new system compliant to this
document (this document refers ETSI TS 102 613, but does not change its specification and does not
use RFU).
For ETSI TS 102 622, data link layer and physical layer like SWP specified in ETSI TS 102 613 is out of
the scope.
Albeit questioned in this document, the duplication of OSI transport layer by e.g. enforcing encapsulation
of HCP into T=1 or the reverse, is out of the scope.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 7816-3, Identification cards — Integrated circuit cards — Part 3: Cards with contacts — Electrical
interface and transmission protocols
ISO/IEC 7816-4, Identification cards — Integrated circuit cards — Part 4: Organization, security and
commands for interchange
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
3.1
APDU gate
entry point to a service processing command APDU inside a host (3.6) or returning response APDU
3.2
APDU application gate
entry point to a service sending command APDU and retrieving correspondent response APDU
© ISO/IEC 2021 – All rights reserved 1

3.3
gate
entry point to a service that is operated inside a host (3.6)
[SOURCE: ETSI TS 102 622]
3.4
HCI network
star-topology network comprised of a host network (3.8) where hosts (3.6) are interconnected with a
host controller (3.7) through HCI
3.5
HCP stack
layout comprised of a routing layer, a messaging layer and a collection of gates (3.3)
3.6
host
logical entity that operates one or more service(s)
[SOURCE: ETSI TS 102 622]
3.7
host controller
host (3.6) that is also responsible for managing a host network (3.8)
[SOURCE: ETSI TS 102 622]
3.8
host network
network of two or more hosts (3.6)
[SOURCE: ETSI TS 102 622]
3.9
managing host
host (3.6) which is in charge of resolving conflicts and interoperability issues between different
contactless applications provided by different hosts
[SOURCE: ETSI TS 102 622]
3.10
pipe
logical communication channel between two gates (3.3) from different hosts (3.6)
[SOURCE: ETSI TS 102 622]
3.11
terminal host
host (3.6) allocated a static identifier HID '01'
4 Symbols and abbreviated terms
ADM_x arbitrary command for administration gate, see ETSI TS 102 622 clause 6.1, e.g. ADM_CRE-
ATE_PIPE
APDU application pro
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.