Java Card OpenPlatform
| Developer | IBM, > 2007 NXP |
|---|---|
| OS family | Embedded operating systems |
| Working state | Current |
| Latest release | JCOP 3.1 |
| Marketing target | Smart cards, Secure Elements, USB security tokens, Telematics |
| Platforms | Java Card |
| Official website | [1] |
Java Card OpenPlatform (JCOP) is a smart card operating system for the Java Card platform developed by IBM Zürich Research Laboratory. On 31 January 2006 the development and support responsibilities transferred to the IBM Smart Card Technology team in Böblingen, Germany. Since July 2007 support and development activities for the JCOP operating system on NXP / Philips silicon are serviced by NXP Semiconductors.
The title is originated from standards it comply with:
A Java Card JCOP has a Java Card Virtual Machine (JCVM) which allows it to run applications written in Java programming language.
Mask 0 : 1998 (spring)
Mask 1 : 1998
Mask 2 and 3 : 1999
Mask 4 : 1999
Mask 5 : 2000
Visa breakthrough program
JCOP v2
JCOP v2.2
JCOP v2.2.1 – JCOP v2.3.1
JCOP v2.3.2
JCOP v2.4
JCOP v2.4.1
JCOP v2.4.2
Smartcard controller SmartMX2, P61, flash based persistent memory
JCOP 3.0
JCOP 3.1
SMX2, P60, EEPROM based persistent memory
JCOP 3.x (not released as of Dec 26, 2014)
JCOP is an operating system for a security sensitive embedded system environment, smartcard or secure element controllers in particular. The functional architecture can be partitioned into three parts:
NXP offers also MIFARE emulations for Classic and DESFIRE on the same chip as additional (native) operating systems. While JCOP is based on open standards, MIFARE technology is NXP specific. Java Card applets running in JCOP can then be used to manage the MIFARE memory through Java Card API. MIFARE Plus and MIFARE Ultralight are not (yet) supported.
GP is a high-level standard with many options. As of JCOP 3, support for GP 2.2.1 was added, in particular to support mobile use cases JCOP 3 is fully Secure Element configuration compliant.
GP 2.2.1 card specification, core
Amendment A - Confidential Card Content Management (C3M)
Amendment C - Contactless Services
Amendment D - Secure Channel Protocol 03 (AES)
Amendment E - Security Upgrade
UICC configuration
Secure Element configuration
From the optional packages JCOP 3 does not support the javacardx.famework. From the crypto and signature classes, some algorithms are not supported, i.e. MD5 and EC F2M. The key lengths (amongst others) supported are AES-128, DES, 2DES3, 3DES3, EC up to 521 bit, RSA up to 2048 bit.
...
Wikipedia