Identification card systems - European Citizen Card - Part 5: General Introduction

The European Citizen Card (ECC) standard addresses the difficulties presented to citizens when attempting to access various public services using a smart card as an access token. The scope of the ECC standard covers
card capabilities and structures specified under the following headings:
- Specific definition of minimum features (for example, card surface print structure).
- Definition of optional features that may be required to provide the desired electronic services.
- Specification of discovery mechanisms to allow supported and in-use card capabilities and features to be identified.
- Besides covering the hardware and software of the card, the ECC standard also addresses interfaces to readers and servers through middleware components. This simple concept can enable ECC cards to adopt a widely different set of personas, even though a common application may be housed on cards used in different environments and in different ways. Generically, we can consider ECC cards as being classed as one of the following groups, even though the same application may be loaded (alongside others) in each environment. These groupings are:
- eID Verification token;
- Inter-European Union travel document;
- Provider of logical access to e-Government or local administration services or to private sector services by housing personal credentials. In order to support the above, it is noted that there will be certain minimum requirements upon any card conforming to the ECC, specifically, the European Citizen Card will be at a minimum a smart card with Identification, Authentication and electronic Signature (IAS) service capabilities. The ECC may act as a bridge between different application requirements of an integrated circuit card and in so doing act to reduce the number of different European specifications and standards required. The ECC will be issued under the responsibility of a European National Public Administration in order to provide a token supporting one of the above usage groupings by housing one or more relevant applications. In addition, there is nothing to stop the ECC being used to support private applications and environments which would therefore allow the ECC to be used in a shared public-private application scenario. It is apparent that the ECC is intended to offer the card issuer/ service provider with a great deal of flexibility in the services that the ECC provides, the authentication mechanisms supported and the local national specific public policy with an special concern to protect the citizen privacy according to the applicable European legislation.

Identifikationskartensysteme - Europäische Bürgerkarte - Teil 5: Allgemeine Einführung (ECC-5)

Systèmes de cartes d'identification - Carte Européene du Citoyen - Partie 5 : Introduction générale (ECC-5)

Sistemi z identifikacijskimi karticami - Kartica evropskih državljanov - 5. del: Splošna predstavitev

Standard za kartico evropskih državljanov (ECC) obravnava težave, ki jih imajo državljani pri poskusu dostopa do različnih javnih storitev z uporabo pametne kartice kot žetona za dostop. Na področje uporabe standarda za kartico evropskih državljanov spadajo
zmogljivosti in strukture kartic, opredeljene pod naslednjimi naslovi:
– Posebna opredelitev minimalnih funkcij (na primer struktura tiska na površini kartice).
– Opredelitev dodatnih funkcij, ki so morda zahtevane za zagotavljanje želenih elektronskih storitev.
– Specifikacija mehanizmov odkrivanja, da se omogoči opredelitev podprtih zmogljivosti in funkcij kartice med uporabo.
– Standard za kartico evropskih državljanov poleg strojne opreme in programske opreme kartice obravnava tudi vmesnike za bralce in strežnike prek komponent vmesne programske opreme. Ta preprosti koncept lahko karticam evropskih državljanov omogoči sprejetje drugačnega sklopa oseb, čeprav je lahko na karticah skupna aplikacija, ki se uporablja v različnih okoljih in na različne načine. Na splošno lahko kartice evropskih državljanov obravnavamo kot razvrščene v eno od naslednjih skupin, čeprav je mogoče enako aplikacijo (poleg drugih) naložiti v vsakem okolju. Te skupine so:
– žeton za preverjanje eID;
– dokument za potovanje znotraj Evropske unije;
– ponudnik logičnega dostopa do e-vladnih ali lokalnih upravnih storitev ali do storitev zasebnega sektorja z vsebovanjem osebnih poverilnic. Za podporo navedenega morajo vse kartice v skladu s kartico evropskih državljanov izpolnjevati določene minimalne zahteve, tj. kartica evropskih državljanov mora biti najmanj pametna kartica, ki lahko zagotavlja storitve identifikacije, preverjanja pristnosti in elektronskega podpisa (IAS). Kartica evropskih državljanov lahko povezuje različne zahteve glede aplikacij kartice z integriranim vezjem, pri čemer znižuje število različnih zahtevanih evropskih specifikacij in standardov. Kartica evropskih državljanov se izda na odgovornost evropske nacionalne javne uprave, da bi se zagotovil žeton, ki podpira eno od zgoraj navedenih skupin uporabe, tako da je na njej ena ali več ustreznih aplikacij. Poleg tega nič ne preprečuje uporabe kartice evropskih državljanov za podporo zasebnih aplikacij in okolij, kar bi omogočilo uporabo kartice v scenariju deljene javno-zasebne aplikacije. Očitno je, da je kartica evropskih državljanov oblikovana tako, da izdajatelju kartice/ponudniku storitev omogoča veliko mero prilagodljivosti v zvezi s storitvami, ki jih kartica omogoča, podprtimi mehanizmi za preverjanje pristnosti in lokalno nacionalno posebno javno politiko s posebnim namenom zaščite zasebnosti državljanov v skladu z veljavno evropsko zakonodajo.

General Information

Status
Published
Publication Date
13-May-2013
Technical Committee
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
06-May-2013
Due Date
11-Jul-2013
Completion Date
14-May-2013

Buy Standard

Technical specification
TS CEN/TS 15480-5:2013
English language
20 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 15480-5:2013
01-junij-2013
Sistemi z identifikacijskimi karticami - Kartica evropskih državljanov - 5. del:
Splošna predstavitev
Identification card systems - European Citizen Card - Part 5: General Introduction
Identifikationskartensysteme - Europäische Bürgerkarte - Teil 5: Allgemeine Einführung
(ECC-5)
Systèmes de cartes d'identification - Carte Européene du Citoyen - Partie 5 : Introduction
générale (ECC-5)
Ta slovenski standard je istoveten z: CEN/TS 15480-5:2013
ICS:
35.240.15 Identifikacijske kartice in Identification cards and
sorodne naprave related devices
SIST-TS CEN/TS 15480-5:2013 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TS CEN/TS 15480-5:2013

---------------------- Page: 2 ----------------------

SIST-TS CEN/TS 15480-5:2013


TECHNICAL SPECIFICATION
CEN/TS 15480-5

SPÉCIFICATION TECHNIQUE

TECHNISCHE SPEZIFIKATION
April 2013
ICS 35.240.15
English Version
Identification card systems - European Citizen Card - Part 5:
General Introduction
Systèmes de cartes d'identification - Carte Européene du Identifikationskartensysteme - Europäische Bürgerkarte -
Citoyen - Partie 5 : Introduction générale (ECC-5) Teil 5: Allgemeine Einführung (ECC-5)
This Technical Specification (CEN/TS) was approved by CEN on 12 February 2013 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their
comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available
promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in parallel to the CEN/TS)
until the final decision about the possible conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United
Kingdom.





EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2013 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 15480-5:2013: E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
Contents Page
Foreword .3
Introduction .4
1 Scope .5
1.1 Scope of CEN/TS 15480-5:2013 .5
1.2 Scope of the ECC standard .5
2 Normative references .5
3 Terms and definitions .6
4 Symbols and abbreviations .6
5 Construction of the ECC standard .7
6 Clarification of key concepts used in the ECC standard .7
6.1 Interoperability .7
6.2 Privacy .8
6.3 ECC Profiles .8
6.3.1 General .8
6.3.2 Types of profiles defined in the ECC standard .9
6.3.3 Relationship between ECC Profiles . 10
6.3.4 Example of the usage of an ECC Card Profile . 10
6.3.5 Example of the usage of an ECC Application Discovery Profile . 11
6.3.6 Example of usage of an ECC User Accessibility Profile . 11
7 Requirements and options . 11
8 Part 1: Physical, electrical and transport protocol characteristics . 13
8.1 General . 13
8.2 Compliance with public administration requirements and citizen expectations . 14
8.3 Identifying an ECC holder . 14
9 Part 2: Logical data structures and card services . 14
10 Part 3: European Citizen Card Interoperability using an application interface . 15
10.1 General . 15
10.2 Tools for smartcard suppliers . 15
10.3 Tools for integrators . 16
10.4 Compatibility with other standards. 17
11 Part 4: Recommendations for European Citizen Card issuance, operation and use . 17
Annex A (informative) Relationship between ECC standard parts and ISO standards . 19
A.1 Mapping of ECC to ISO standards . 19
Bibliography . 20

2

---------------------- Page: 4 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
Foreword
This document (CEN/TS 15480-5:2013) has been prepared by Technical Committee CEN/TC 224 “Personal
identification, electronic signature and cards and their related systems and operations”, the secretariat of
which is held by AFNOR.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the following
countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus,
Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany,
Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.

3

---------------------- Page: 5 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
Introduction
Within the European Union there will be many integrated circuit cards issued by public bodies and
administrations, each of which can house a variety of applications in different combinations. The cardholder
can hold several multi-application public service cards and is concerned that:
 He or she knows or can find out which applications are on a card;
 Applications on a card may be read and dealt with by appropriate terminals;
 Security is appropriate for the application being used, while also being fit-for-purpose in protecting the
user's data on the card and ensuring privacy to the level required.
Different cards will have different capabilities. This presents application providers and scheme operators with
a number of challenges:
 Does the card have the specific minimum level of functionality, capability and security features necessary
to house the application to be loaded onto the card?
 Are there other applications on this card that would preclude this application being loaded (including for
example, surface printing requirements)?
 What are the features and functions of the card (that are being used) that the terminal will have to
support?
This Technical Specification provides mechanisms to resolve the above issues together with a formalised
approach that will allow different applications and services to co-exist and interoperate in a single card
environment.
This Technical Specification also recognises that there will be legacy systems in evidence as and when the
ECC card is being introduced. It provides a mechanism (described in CEN/TS 15480-3) by which legacy
systems can operate in an ECC environment until cards may be replaced by European Citizen Cards in
batches as the opportunity arises.

4

---------------------- Page: 6 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
1 Scope
1.1 Scope of CEN/TS 15480-5:2013
The scope of this Technical Specification is to provide a general description of the standard together with an
introduction to each part of the ECC standard.
Informative Annex A maps the relationship between the various parts of the ECC standard and other ISO/IEC
standards relating to the card platform.
1.2 Scope of the ECC standard
The European Citizen Card (ECC) standard addresses the difficulties presented to citizens when attempting to
access various public services using a smart card as an access token. The scope of the ECC standard covers
card capabilities and structures specified under the following headings:
 Specific definition of minimum features (for example, card surface print structure).
 Definition of optional features that may be required to provide the desired electronic services.
 Specification of discovery mechanisms to allow supported and in-use card capabilities and features to be
identified.
 Besides covering the hardware and software of the card, the ECC standard also addresses interfaces to
readers and servers through middleware components.
This simple concept can enable ECC cards to adopt a widely different set of personas, even though a
common application may be housed on cards used in different environments and in different ways.
Generically, we can consider ECC cards as being classed as one of the following groups, even though the
same application may be loaded (alongside others) in each environment. These groupings are:
 eID Verification token;
 Inter-European Union travel document;
 Provider of logical access to e-Government or local administration services or to private sector services
by housing personal credentials.
In order to support the above, it is noted that there will be certain minimum requirements upon any card
conforming to the ECC, specifically, the European Citizen Card will be at a minimum a smart card with
Identification, Authentication and electronic Signature (IAS) service capabilities. The ECC may act as a bridge
between different application requirements of an integrated circuit card and in so doing act to reduce the
number of different European specifications and standards required.
The ECC will be issued under the responsibility of a European National Public Administration in order to
provide a token supporting one of the above usage groupings by housing one or more relevant applications. In
addition, there is nothing to stop the ECC being used to support private applications and environments which
would therefore allow the ECC to be used in a shared public-private application scenario.
It is apparent that the ECC is intended to offer the card issuer/ service provider with a great deal of flexibility in
the services that the ECC provides, the authentication mechanisms supported and the local national specific
public policy with an special concern to protect the citizen privacy according to the applicable European
legislation.
2 Normative references
Not applicable.
5

---------------------- Page: 7 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
ECC Application Profile
set of ECC mandatory and optional features which is referred to by a unique registered identifier. An
Application Profile implements an interoperable ECC service
3.2
ECC Card Profile
profile made up of one or more ECC Application Profiles with their associated electrical interfaces and
possibly one or more ECC User Accessibility Profiles. In addition an ECC Card Profile may also include an
ECC Durability Profile. An ECC Card Profile is referred to by a unique registered identifier
3.3
ECC Conditional Feature
feature required by an ECC Application Profile
3.4
ECC Durability Profile
profile associated with an ECC, which provides information that relates to the card durability performance
3.5
ECC Layout Profile
optional profile which indicates card body requirements
3.6
ECC Mandatory Feature
card software feature required to claim compliance with the ECC standard
3.7
ECC Optional Feature
card software feature not required to claim compliance with an ECC
3.8
ECC User Accessibility Profile
set of card optional features not identified in any ECC Application Profile supported by the card and which
may improve the accessibility to services and/or the usability of the ECC. An ECC User Accessibility Profile is
referred to by a unique registered identifier
3.9
ECC Discovery Profile
set of features supported by the card-applications and personalised in different formats depending on card
issuer’s choice. Once read by the terminal, this profile uncovers card-application services with their related
data references and the security rules applying to it. This profile allows ECC fitting in an ISO/IEC 24727
framework
4 Symbols and abbreviations
EF Elementary File
EF.DIR Elementary File Directory
ELC Elliptic Curve cryptography
6

---------------------- Page: 8 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
5 Construction of the ECC standard
The ECC standard is specified in five parts as follows:
1) Part 1: Specifies the physical characteristics and construction of the card including:
a) card body;
b) electrical interfaces;
c) data transport protocols;
d) authentication elements visible at the card surface;
e) the specification of an ECC Layout Profile and an ECC Durability Profile;
2) Part 2: Specifies the logical characteristics and security features at the card/system Interface.
These include:
a) the specification of supported services;
b) the specification of supported data structures as well as the access to them;
c) the definition of the command set;
d) the specification of ECC Application Profiles;
3) Part 3: Covers the achievement of interoperability using an application interface. In particular, this
part covers how interoperability can be achieved:
a) to fit in a framework designed based on ISO/IEC 24727;
b) to provide a means for legacy card support within the ECC framework;
c) the specification of ECC Application Discovery Profile;
4) Part 4: Looks at operational and policy issues:
a) recommends card issuance and operational procedures including citizen registration;
b) makes recommendations for citizen contact and interaction (for example, accessibility, usability,
privacy and health and safety issues);
c) specifies a number of ECC Card Profiles and ECC User Accessibility Profiles;
5) Part 5: This introductory and overview document.
Parts 1 to 4 of the ECC standard are explained in more detail in Clauses 8 to 11.
6 Clarification of key concepts used in the ECC standard
6.1 Interoperability
This standard is about interoperability in access to services. However, interoperability is a wide ranging
concept and its use within this standard requires further qualification.
7

---------------------- Page: 9 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
Interoperability in this context is about integrated circuit cards issued in one environment being able to be
used in another, where environments may specify different controlling public administrations, different
application environments and different card issuers. This does not, however, imply that all cards are the same,
all applications are the same, all terminals are the same and all security controls are the same. Rather, this
standard defines an open framework for interoperability:
 at the highest level interoperability will be defined by agreements between different service providers
within the same or different public administrations;
 at the lowest level the card must be physically readable in the terminal implying compatibility with
ISO/IEC 7816-1, 2, and 3 for contact interface cards or ISO/IEC 14443-1,2 and 3 for contactless interface
cards;
 this standard defines the minimum requirements of card level service support required of the ECC.
Optional additional support may be required for access to certain services. Only those cards supporting
the additional requirements will be able to access those services;
 terminals must support the environment in which they exist. However, by design and service operator
agreement, that does not mean that all services can be accessed by all terminals. ISO/IEC 24727 may
apply to the terminals and surrounding environment (servers), in which case Part 3 of this standard
defines the additional interoperability requirements which may or may not be available in the card.
It will be seen that full any-to-any interoperability is not intended or provided for. However, this standard
provides a basis for interoperability within a multiplicity of environments in which different cards with different
capabilities will operate, issued by different issuers, representing different public administrations and
accessing different services each with its own access requirements. Depending upon the circumstances
applying, for example commonality of basic card support, this standard offers a way of migrating to the ECC
environment, gradually, one legacy system at a time, while continuing to interoperate.
6.2 Privacy
Privacy principles for card issuance and operation as well as privacy features for ECC along with
recommendations and legislation guidance can be found in CEN/TS 15480-4:2012 respectively in 5.1 and
Clause 6. References to EU legal acts can be found in CEN/TS 15480-4:2012, Annex C. Privacy-compliant
implementation examples are provided in CEN/TS 15480-2:2012 as reference to authentication protocols (see
6.4.4.3 for Device authentication with privacy protection, or 7.8 for Restricted Identification, or 7.10 for modular
Enhanced Role Authentication) or as Application Profiles (see E.4 for Profile 3 "eID Application", or E.6 for
Profile 5 "eServices Application with Trusted Third Party").
6.3 ECC Profiles
6.3.1 General
The ECC as defined in this standard specifies a minimum set of requirements plus a set of options that may
be used in different circumstances as required. ECC Profiles are optional and if used, an example of the set of
minimum requirements plus optional facilities that are most likely (or may be mandated) to be used in different
usage scenarios. If different card issuers meet the requirement set down in a specific profile,, then
interoperability will be guaranteed. One example could be a profile for an ECC to act as a European Travel
Document.
Open profiles will be registered and given unique numbers as part of this standard which may be discovered
by the card terminal in which the ECC is placed. This enables the terminal quickly to determine whether this
ECC supports the service being accessed or provided at this terminal. Private, proprietary profiles may also
be defined, however, interoperability will only be guaranteed among terminals recognising and supporting
these profiles.
8

---------------------- Page: 10 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
Any national body member of CEN/TC 224 may submit an ECC Profile to CEN/TC 224/WG 15 acting as the
Registration Authority for integration in the standard. An ECC may also be issued supporting one or more
Proprietary ECC Profiles which shall not be allocated or reuse any registered ECC Profile identifier.
It is perfectly possible for a card to support multiple profiles indicating its multi-application capability where
different applications require different profiles each indicating the card support required. It is noted that the
actual card services required by different profiles on a card may overlap or even be the same.
6.3.2 Types of profiles defined in the ECC standard
The basic interoperability profile is the ECC Application Profile. If present, it specifies those mandatory and
optional features of the ECC required to implement an interoperable ECC service. There may be more than
one ECC Application Profile, indicating perhaps overlapping features, each profile indicating the requirements
of a different ECC service. ECC Application Profiles may be created, managed and maintained during the life
of the ECC. Correspondingly, other ECC Profiles discussed below may also be managed during the life of the
ECC.
In addition to ECC Application Profiles linking feature requirements to services, one or more ECC User
Accessibility Profiles may be present where the ECC User Accessibility Profile indicates card features not
specifically listed in any ECC Application Profile and therefore not essential for interoperable ECC service
delivery but which may improve the accessibility to services and/or the usability of the ECC.
An ECC Card Profile may or may not be present but if present offers a convenient way to identify and access
other Profiles on the card. It is made up of one or more ECC Application Profiles with their associated
electrical interfaces and possibly one or more ECC User Accessibility Profiles. In addition, it may also contain
an ECC Durability Profile which contains information relating to the card’s durability performance determined
according to ISO/IEC 24789 methodology.
An ECC Layout Profile may also be present and indicates the card body features.
Taken together, the use of ECC Profiles will:
 simplify the identification of availability versus requirements of interoperability services;
 cover the whole range of use cases for the ECC;
 provide a sufficient level of flexibility for the card specification;
 enhance the ability of the user to access services according to its personal preferences;
 guarantee the in-field capability and reliability of the card.
The advantages brought about by the specification of these ECC Profiles are clear, however, the specification
of profiles is purely optional. In order for a card to comply with the ECC standard the only condition is the
implementation of the mandatory requirements of ECC-1 and -2.
Table 1 details in which part of the ECC standard each profile is described:
9

---------------------- Page: 11 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
Table 1 — Location of ECC Profile Description
Application User
Part of the ECC Durability Layout Application Card
Discovery Accessibility
Standard Profile Profile Profile Profile
Profile Profile
ECC-5 Purpose, Definition and Rules for Profile Usage
ECC-1 X X
ECC-2  X
ECC-3  X
ECC-4   X X
6.3.3 Relationship between ECC Profiles
The relationships between ECC Profiles discussed above are illustrated in Figure 1:

Figure 1 — ECC Profiles relationships
6.3.4 Example of the usage of an ECC Card Profile
The ECC issuer may use the same Card Profile with different card-applications. The Card Profile unique
identifier informs the terminal about the type of card platform and so allows the terminal to recognise which
Application Profile(s) can be present on such a card and through this matching, the terminal can initialise the
appropriate set of functions to handle a transaction with this card.
10

---------------------- Page: 12 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
6.3.5 Example of the usage of an ECC Application Discovery Profile
Specifying a Application Discovery Profile is relevant whenever the issuer wants to have all or part of the card-
applications acting in an ISO/IEC 24727-framework as set down in ECC Part 3.
For example, consider the use of a Card Profile which includes two Application Profiles referring respectively
to two card-applications. The issuer may select one or both of the two card-applications to run within
an ISO/IEC 24727-framework. In addition, the issuer may opt for only part of a selected card-application’s
features to be exposed to the discovery mechanism. In order to achieve this, the issuer will take the steps as
listed below and detailed in part 3 of the ECC standard:
 selection of a method for card discovery;
 implementation of the selected method to publish the registry allowing card discovery;
 since the terminal identifies the ISO/IEC 24727 enabled card application linkages may now be made to
that application in one of a variety of methods as described in part 3 of the ECC standard.
Once the measures above are completed, the card can be considered as fitting in with ISO/IEC 24727
middleware.
6.3.6 Example of usage of an ECC User Accessibility Profile
User Accessibility Profiles are needed to determine the set of features and data structures that are to be
supported by a card to meet ISO/IEC 12905 [4] requirements for user accessibility. They are assigned
OBJECT IDENTIFIERs (OID) for the purpose of their discovery by the terminal as described in ECC Part 4,
The terminal may look up the OID values in different ways: either from a normalised information file or from
within a dedicated application when present on-card, in both cases, the Profile is said Global to the card. In
case the Profile is recoverable from within an application other than the dedicated one, it is said specific to this
application.
7 Requirements and options
This standard specifies an ECC that meets the following requirements:
 identification and authentication of the holder by electronic means using reference data stored in the card
and also by visual inspection or an appropriate device;
 mutual authentication where required between the card and the terminal communicating with the card;
 secure transmission of data using contact and/or contactless interfaces;
 confidential exchange of data if required;
 electronic signature generation and verification;
 access control mechanisms to stored data;
 the surface of the card shall allow customisation by public administrations to suit their own requirements;
 surface and print security techniques shall be in evidence (or example, holograms and photographs);
 cards shall be resistant to physical attack;
 cards shall provide the capability to support interoperability with other key standards as well as co-exist in
environments supporting certain legacy applications;
11

---------------------- Page: 13 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
 cards shall be capable of fitting in with the procedures and policies of the public administrations making
use of the ECC;
and optionally:
 multi-application capability;
 post-issuance loading and deleting of applications on the card;
 controlled updating of electronically stored data.
12

---------------------- Page: 14 ----------------------

SIST-TS CEN/TS 15480-5:2013
CEN/TS 15480-5:2013 (E)
8 Part 1: Physical, electrical and transport protocol characteristics
8.1 General
Part 1 of the ECC standard defines the characteristics of a public service card which may b
...

Questions, Comments and Discussion

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