JCOP41
JCOP41
V2.2.1
JCOP41/72B4 V2.2.1 on Secure Triple Interface PKI Smart
Card Controller
Rev. 1.0 — 16 August 2006 Objective short data sheet
128610
1. General description
JCOP V2.2.1 family based on the SmartMX family which is manufactured in most
advanced CMOS 0.18 µm 5 metal layer technology is positioned to service high volume,
mono- and multi-application markets such as eGovernment e.g. Smart Passport,
banking/finance, mobile communications, public transportation, pay TV, conditional
access, network access and digital rights management.
The JavaCard, GlobalPlatform and ISO industry standards together ensure application
interoperability for card issuers as well as application providers. By adhering not just to the
standards themselves, but also to their spirit as evidenced in numerous heritage
applications, JCOP V2.2.1 ensures largely interoperability with third-party applets as well
as all existing smart card infrastructures. With JCOP V2.2.1 the promise of multi-sourcing
any component in smart card solutions becomes true. Even in existing infrastructures,
JCOP V2.2.1 equipped with proper applications can substitute any existing smart card.
Within its targeted segments, the new JCOP V2.2.1 platform on SmartMX is the most
advanced solution available, combining exceptionally standard interfaces as defined in
JavaCard 2.2.1, GlobalPlatform Card Specification 2.1.1 and the powerful cryptographic
capabilities by using co-processors for public and secret key encryption supporting RSA,
ECC and Triple-DES, within the high security, ultra low power, performance optimized
design concept of Philips Semiconductors’ handshaking technology. The platform
supports Class “C”, “B” and “A” voltage ranges (1.62 - 5.5 V) as required by application
standards such as 3G Mobile Communication (3GPP) and the credit/debit card standard
(EMV).
For further details on general JCOP V2.2.1 platform features refer to Section 2.2
“JCOP V2.2.1 Product Family Features”.
Philips Semiconductors P541x072 V0P
JCOP41/72B4 V2.2.1 on Secure Triple Interface PKI Smart Card
Controller
JCOP V2.2.1 PKI products support additionally RSA, ECC and Korean SEED algorithm. It
includes RSA keys of up to 2432 bit length, the ability to generate all RSA keys on the
card for maximum security, as well as the MD5 and SHA1 hashing methods. For more
information see also Section 5.1.4 “Standard Cryptographic Algorithms”.
This way, standard applications of a particular card issuer can be put into the ROM
thus reducing the EEPROM requirements significantly. For high-volume roll-outs, this can
mean substantial savings. This allows the card issuer to select a JCOP V2.2.1 product
with 10 kB EEPROM in place of a JCOP V2.2.1 product with 72 kB EEPROM that has to
be used without using the JCOP V2.2.1 Custom Mask process.
JCOP V2.2.1 is supporting Custom Mask Process. This unique customization process
has been developed to create transparent blends between any of the JCOP V2.2.1
versions and any set of applets into a so-called custom mask. This way, standard
applications of a particular card issuer can be put into the ROM thus reducing the
EEPROM requirements significantly.
This became possible due to the very low footprint implementation of the JCOP V2.2.1
base system, fitting into 88 kB of ROM; consequently, leaving additionally 70 kB of ROM
space for card issuer applets, i.e. overall 140 kB of applet code and data space on
JCOP41/72 V2.2.1.
Via the pre-personalization of JCOP V2.2.1 the communication protocols as T=0, T=1 or
T=CL, the communication speeds, the UID types (fixed or randomize), the Global Platform
parameter, the Card Manager keys and other parameters can be set.
The device operates either with a single 1.8 V, 3 V or 5 V (voltage classes C, B, A) power
supply at a maximum external clock frequency of 10 MHz supplied by the contact pads
(internally up to 30 MHz) or via the antenna pads (LA/LB) with a power supply generated
from the RF-field emitted by an RF-reader.
1.6 Interfaces
JCOP V2.2.1 uses the contact and the contactless interface. The same level of security,
functionality and flexibility applies for the contact interface as for the contactless interface.
The USB interface uses the ISO contact module and works via a 4-wire connection to any
PC supporting “hot Plug and Play”. The card automatically recognizes an ISO or USB
environment and is able to work with external frequency of up to 6 MHz, in addition to the
internal usable frequencies.
The use of USB interfaces on smart cards is currently in the process of becoming
standardized within ISO/IEC 7816-12.
2. Features
The JCOP V2.2.1 on the P541x072 is an open operating system based on a Secure PKI
Smart Card Controller of the SmartMX platform. Operating both in contact mode
(ISO/IEC 7816) and in contactless mode (ISO/IEC 14443A) the user defines the final
function of the application running on JCOP41 V2.2.1.
3. Applications
4. Ordering information
Philips Semiconductors
Table 1: JCOP41 V2.2.1 Platform Overview
Product Type Java Global VGP Appl. Mifare Interface & Protocols IC Free ROM Free ROM
Card Platform Config Backward EEPROM EEPROM [kB] Data space
ISO/IEC 7 ISO/IEC 1 USB 2.0
1, 2, 3 Compatible [kB] Data space [kB]
816 4443A
VGP 2.0.1’ [kB]
T=0, T=1 T=CL
JCOP41/72B4 V2.2 2.2.1 2.1.1 3 x 4K x x x 72 65 160 70
[1] x = G. For information refer to Data sheet, Section “JCOP V2.2 product naming conventions”
[2] only for RSA and ECC
Rev. 1.0 — 16 August 2006
P541x072 V0P
Controller
6 of 19
Philips Semiconductors P541x072 V0P
JCOP41/72B4 V2.2.1 on Secure Triple Interface PKI Smart Card
Controller
• Ciphers:
– ALG_DES_CBC_NOPAD
– ALG_DES_CBC_ISO9797_M1
– ALG_DES_CBC_ISO9797_M2
– ALG_DES_ECB_NOPAD
– ALG_DES_ECB_ISO9797_M1
– ALG_DES_ECB_ISO9797_M2
– ALG_RSA_NOPAD1
– ALG_RSA_PKCS1
– ALG_AES_BLOCK_128_CBC_NOPAD
– ALG_AES_BLOCK_128_ECB_NOPAD
1. The input data must be the same size as the key length
• Signatures:
– ALG_DES_MAC8_NOPAD
– ALG_DES_MAC8_ISO9797_M1
– ALG_DES_MAC8_ISO9797_M2
– ALG_DES_MAC8_ISO9797_1_M2_ALG3
– ALG_ECDSA_SHA
– ALG_RSA_MD5_PKCS1
– ALG_RSA_SHA_ISO9796
– ALG_RSA_SHA_PKCS1
– ALG_AES_MAC_128_NOPAD
• MessageDigest:
– SHA1 is available on all PKI products of JCOP V2.2.1
– MD5 is available on all PKI products of JCOP V2.2.1
• RandomData:
– ALG_SECURE_RANDOM
– ALG_PSEUDO_RANDOM
• Key Types:
All JCOP V2.2.1 based systems support DES and Triple-DES (with both double and
triple-length keys). AES is supported on JCOP41 V2.2.1. JCOP V2.2.1 PKI products
support RSA and ECC cryptography. The supported key lengths are denoted below:
– LENGTH_DES
– LENGTH_DES3_2KEY
– LENGTH_DES3_3KEY
– LENGTH_AES_128
– LENGTH_AES_192
– LENGTH_AES_256
– LENGTH_RSA_512 up to LENGTH_RSA_24322
– LENGTH_EC_F2M_113 up to 239 (no constant defined in JC 2.2.1 API)
• KeyPairs
On-card key generation (RSA CRT and ECC) available on JCOP V2.2.1 PKI
products:
– ALG_RSA_CRT
– ALG_EC_F2M
• Checksum
– ALG_ISO3309_CRC16
• Signature:
– ALG_DES_MAC8_ISO9797_1_M1_ALG3
5.2 GlobalPlatform
All mandatory features mentioned in Section 5.2.1 are implemented. Optional features are
listed below:
5.2.1 GP Profile
GlobalPlatform permits and requires certain clarifications to the definite operation of an
implementation according to Ref. 2. This section describes the non-obvious profile
adaptations of JCOP V2.2.1.
The card is compliant with the 'GlobalPlatform Card Specification 2.1 & 2.1.1 Compliance
Packages Version 2.0 September 2004', 'Package 0 Core GP functionality', 'Package 24
SCP01 support', 'Package 25 SCP02 support', 'Package 26 SCP02 explicit secure
channel initiation' and 'Package 28 Selection of the Key Version Number in P1 of
INITIALIZE UPDATE' with the following restrictions:
5.3.3 Mifare
JCOP has an implementation of the Mifare API as defined in Ref. 9.
Via JCOP order entry forms (OEF) the options with or without Mifare standard can be
selected.
• In the contact mode if the default clock rate is 3.57 MHz, the following
communication speeds are supported:
– 9600 bit/s [default]
– 19200 bit/s
– 38400 bit/s
– 57600 bit/s
– 115200 bit/s
– 230400 bit/s
• In the contactless mode the following communication speeds according to
ISO/IEC 14443A are supported:
– 106 kbit/s
– 212 kbit/s
– 424 kbit/s
6. Limiting values
Table 3. Limiting values
In accordance with the Absolute Maximum Rating System (IEC 60134). Voltages are referenced to
VSS (ground = 0 V).
Symbol Parameter Conditions Min Max Unit
VDD supply voltage -0.5 +6.0 V
VI input voltage any signal pad -0.5 VDD +0.5 V
II input current pad IO1, IO2 - ± 15.0 mA
IO output current pad IO - ± 15.0 mA
Ilu latch-up current VI < 0 V or VI > VDD - ± 100 mA
Vesd electrostatic discharge pads VDD, VSS, CLK, [1] ± 4.0 kV
voltage RST, IO1, IO2, DP, DM
pads LA, LB [1] ± 2.0 kV
Ptot Total power dissipation [2] - 1 W
Tstg Storage temperature [3]
[1] MIL Standard 883-D method 3015; human body model; C = 100 pF, R = 1.5 kΩ; Tamb = −25 °C to +85 °C.
[2] Depending on appropriate thermal resistance of the package.
[3] Depending on delivery type, refer to Philips Semiconductors General Specification for 8 ” Wafers and to
Philips Semiconductors Contact & Dual Interface Chip Card Module Specification.
7. Abbreviations
Table 4: Abbreviations
Acronym Description
ACM Access Condition Matrix
APDU Application Protocol Data Unit as defined in ISO/IEC 7816
ATR Answer to Reset as defined in ISO/IEC 7816
ATS Answer to Select as defined in ISO/IEC 14443A
CLK External clock signal input contact pad
CPLC Card Production Life Cycle (information): Defined by VISA GlobalPlatform;
among other data, it contains card serial number, release number and date.
Usually used for derivation of card-specific keys
CPU Central Processing Unit
CRC Cyclic redundancy check
DES Data Encryption Standard
Di Baud rate adjustment factor as defined in ISO/IEC 7816-3
EEPROM Electrically Erasable Programmable Read Only Memory
ESD Electrostatic Discharge
FameXE Fast Accelerator for Modular Exponentiation -eXtended
fCLK CLK signal frequency. The timing reference points of a CLK cycle
(period 1/fCLK) are defined at signal level 50% of VDD measured from rising to
rising edge or falling to falling edge.
Fi Clock rate conversion factor as defined in ISO/IEC 7816-3
HW Hardware
ICV Initial Chaining Vector
IDD Supply current into contact pad VDD
IFSC Information Field Size Card as defined in ISO/IEC 7816 (“APDU size”)
IFSD Information Field Size interface Device (= card reader) as defined in
ISO/IEC 7816 (“APDU size”)
II Input current at a signal contact pad
IIH High level input current
IIL Low level input current
IO Input Output
I/O Generic name for all existing I/O contact pads (I/O1, I/O2, ..) and their I/O line
signals
IOH High level output current
IOL Low level output current
i.r.t. In relation to
ISO International Standardization Organization
ISO/IEC 7816 The respective smart card communications standard; second edition, 1997
LSB Least Significant Byte/bit
kB 1024 bytes
KT Transport key / password
Mifarestandard Mifare Standard IC MF1 ICS50 compatible emulation
8. References
Optional section for document references. The bold reference title is optional.
[1] Sun Microsystems: JavaCard 2.2.1 http://java.sun.com/products/javacard
[2] Global Platform Consortium: GlobalPlatform Card Specification 2.1.1
http://www.globalplatform.org/
[3] ISO/IEC 7816 series; Information technology – Identification cards – Integrated
circuit(s) cards with contacts
[4] ISO/IEC 14443A series; Information technology – Identification cards – Contactless
integrated circuit(s) cards – Proximity cards
[5] Philips Semiconductors: Mifare Standard Card IC MF1 IC S50 Functional
Specification
[6] Philips Semiconductors: Mifare Standard 4 kB Card IC MF1 IC S70 Functional
Specification
[7] Java Card Forum: Biometry API specification (BioAPI):
http://www.javacardforum.org/Documents/Biometry/biometry.html
http://www.javacardforum.org/JCFBioAPIV1A.pdf
http://www.javacardforum.org/Documents/Biometry/BCWG_JCBiometricsAPI
_v01_1.pdf Title: Biometric Application Programming Interface (API) for Java Card,
7 August 2002, Version 1.1 Author: NIST/Biometric Consortium: Biometric
Interoperability, Assurance, and Performance Working Group
[8] SEED: http://www.kisa.or.kr/seed/seed_eng.html
[9] Mifare API: JZSystem.html
[10] Anomaly Sheet for JCOP41 V2.2.1 P541x072 (V0P/V0Q) Platform Products,
Doc.No. 1160xx
[11] International Machine Corporation: http://www.zurich.ibm.com/jcop/products/
tools.html
[12] Visa International: Visa GlobalPlatform 2.1.1 Card Implementation
Requirements Version 1.0, June 2005, Errata 2.1
[13] http:// www.semiconductors.philips.com/products/identification/datasheets/
index.html Æ Mifare Æ Chapter Application Notes
9. Revision history
Table 5. Revision history
Document ID Release date Data sheet status Change notice Supersedes
128610 16 August 2006 Objective short data sheet - Revision 1.0
Modifications: • Initial version
[1] Please consult the most recently issued document before initiating or completing a design.
[2] The term ‘short data sheet’ is explained in section “Definitions”.
[3] The product status of device(s) described in this document may have changed since this document was published and may differ in case of multiple devices. The latest product status
information is available on the Internet at URL http://www.semiconductors.philips.com.
Short data sheet — A short data sheet is an extract from a full data sheet Limiting values — Stress above one or more limiting values (as defined in
with the same product type number(s) and title. A short data sheet is intended the Absolute Maximum Ratings System of IEC 60134) may cause permanent
for quick reference only and should not be relied upon to contain detailed and damage to the device. Limiting values are stress ratings only and operation of
full information. For detailed and full information see the relevant full data the device at these or any other conditions above those given in the
sheet, which is available on request via the local Philips Semiconductors Characteristics sections of this document is not implied. Exposure to limiting
sales office. In case of any inconsistency or conflict with the short data sheet, values for extended periods may affect device reliability.
the full data sheet shall prevail. Terms and conditions of sale — Philips Semiconductors products are sold
subject to the general terms and conditions of commercial sale, as published
at http://www.semiconductors.philips.com/profile/terms, including those
10.3 Disclaimers pertaining to warranty, intellectual property rights infringement and limitation
of liability, unless explicitly otherwise agreed to in writing by Philips
General — Information in this document is believed to be accurate and Semiconductors. In case of any inconsistency or conflict between information
reliable. However, Philips Semiconductors does not give any representations in this document and such terms and conditions, the latter will prevail.
or warranties, expressed or implied, as to the accuracy or completeness of
No offer to sell or license — Nothing in this document may be interpreted
such information and shall have no liability for the consequences of use of
or construed as an offer to sell products that is open for acceptance or the
such information.
grant, conveyance or implication of any license under any copyrights, patents
Right to make changes — Philips Semiconductors reserves the right to or other industrial or intellectual property rights.
make changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior 10.4 Trademarks
to the publication hereof.
Notice: All referenced brands, product names, service names and trademarks
Suitability for use — Philips Semiconductors products are not designed,
are the property of their respective owners.
authorized or warranted to be suitable for use in medical, military, aircraft,
space or life support equipment, nor in applications where failure or Mifare — is a trademark of Koninklijke Philips Electronics N.V.
malfunction of a Philips Semiconductors product can reasonably be expected
12. Tables
Table 1: JCOP41 V2.2.1 Platform Overview . . . . . . . . . .6 Table 3. Limiting values . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 2: JCOP41 V2.2.1 Product Commercial Type and Table 4: Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Versions Map . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Table 5. Revision history . . . . . . . . . . . . . . . . . . . . . . . . 15
13. Contents
1 General description . . . . . . . . . . . . . . . . . . . . . . 1 5.5 Supported Communication Speed Parameters 10
1.1 Family description . . . . . . . . . . . . . . . . . . . . . . . 1 5.6 Supported Unique Identifiers (UIDs) . . . . . . . 10
1.2 Cryptographic Functionality . . . . . . . . . . . . . . . 2 6 Limiting values . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3 Custom Mask Process . . . . . . . . . . . . . . . . . . . 2 7 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Low Overall Card Lifecycle costs . . . . . . . . . . . 2
8 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.5 Hardware Features . . . . . . . . . . . . . . . . . . . . . . 3
1.6 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 9 Revision history . . . . . . . . . . . . . . . . . . . . . . . 15
1.6.1 The Contact Interface . . . . . . . . . . . . . . . . . . . 3 10 Legal information . . . . . . . . . . . . . . . . . . . . . . 16
1.6.2 The USB 2.0 (Low Speed) Interface . . . . . . . . . 3 10.1 Data sheet status . . . . . . . . . . . . . . . . . . . . . . 16
1.6.3 The Contactless Interface. . . . . . . . . . . . . . . . . 3 10.2 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.7 Design-in Support. . . . . . . . . . . . . . . . . . . . . . . 4 10.3 Disclaimers. . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.8 JCOP Product Type definition. . . . . . . . . . . . . . 4 10.4 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.8.1 JCOP PKI products (FameXE supported 11 Contact information . . . . . . . . . . . . . . . . . . . . 16
versions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 12 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.8.2 JCOP Security products (DES only versions). . 4
13 Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1 JCOP V2.2.1 Portfolio. . . . . . . . . . . . . . . . . . . . 5
2.2 JCOP V2.2.1 Product Family Features. . . . . . . 5
2.3 JCOP V2.2.1 Product Specific Features on
P541x072 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Application areas . . . . . . . . . . . . . . . . . . . . . . . 5
4 Ordering information . . . . . . . . . . . . . . . . . . . . . 6
5 Supported Additional JCOP V2.2.1 Features . 7
5.1 Java Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.1.1 Garbage Collection . . . . . . . . . . . . . . . . . . . . . . 7
5.1.2 Remote Method Invocation (RMI) . . . . . . . . . . . 7
5.1.3 Supplementary Logical Channel Support . . . . . 7
5.1.4 Standard Cryptographic Algorithms . . . . . . . . . 7
5.1.5 Non-standard Cryptographic Algorithms . . . . . 9
5.2 GlobalPlatform . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2.1 GP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3 Additional Application Programming Interfaces
(APIs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3.1 Biometry Application Programming Interface
(BioAPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3.2 SEED API - Korean Cryptographic Application
Programming Interface . . . . . . . . . . . . . . . . . . . 9
5.3.3 Mifare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.4 Supported Communication Protocols . . . . . . . 10
Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section ‘Legal information’.