In relation to Java Card or EMV credit card, the Card Production Life Cycle (CPLC) are data element that contain information about the production process of the card such as the operating system or the ICC manufacturer. The Card issuer BIN data contains usually the serial number of the card. The Open Platform specification proposes only that the CPLC data should be retrievable.
The Card Production Life Cycle may be used by an off-card entity to track the life of the card and also to determine the versions and features of each Java Card. The CPLC data typically contains the whom, when and what identification for the following:
- The integrated circuit (IC) fabrication;
- The Operating System;
- The integrated circuit card (ICC) manufacturer.;
- Module fabrication;
- Pre-personalization; and;
Each new secure element that is issued by the SAP Mobile Platform operator can be identified by a unique ID, and requires a specific keyset. The secure element unique ID is stored in a structure called CPLC data, which uniquely identifies each secure element and is stored into each secure element prior to configuration.
known to each other: card management and all commercial issues are contractually regulated well in advance. The stored applications and the Service Providers involved are usually static, and will not change during the card’s life cycle. Technically the cards do allow content download after issuance, but this is rarely done.
APDU command ‘9F7F’ (CPLC / Card Production Life Cycle Data): Defined in “Visa Integrated Circuit Card / Card Specification“. The Open Platform 2.0.1 (predecessor of GlobalPlatform) defines that CPLC should be retrievable with the GET DATA command — but it does not tell the particular tag.
The product life cycle is the course of the life of a product from when the product is in development to after it has been removed from the market.
Example of CPLC data from an NXP JCOP 3 using the “9F7F” APDU command with GlobalPlatformPro:
Utilities used to read CPLC data: