This document and the corresponding sample code is intended to enable performance evaluation with respect to execution speed and certain implementation characteristics. It may be used during product development itself or for final product evaluation by card issuers or application providers. The purpose of the benchmark test is to provide indications for the execution speed of individual functionality as well as overall measures of the implementation characteristics (e.g. buffers size) and execution speed in general. A benchmark setup consists of two components:

On-card functionality to exercise methods and functionality under test. This is implemented as several JavaCard applets.

Off-card driving mechanisms with timing measurements and evaluation algorithms.

A Table of Contents for this document is available to view here.

This document provides implementation guidelines for mapping a card implementation based on the Card Specification v2.1.1 to a GlobalPlatform card compliant to v2.2. The guidelines define card configurations (i.e. subsets of Card Specification features) and describe implementations based on Java Card specifications.

A Table of Contents for this document is available to view here.

The components of this Test Plan, developed in partnership with Calton Hill, include:

• GPD/STIP v2.3 Test Plan - A document which provides the basis for building suites of test software that prove GlobalPlatform compliance.

A table of contents for this document is available to view here.

This is an implementation guide for deploying GlobalPlatform Card Specification v2.2 within the mobile services sector and managing the secure delivery over-the-air of new services. It outlines the behavior of each and every actor involved in a UICC implementation, how they should be represented, and a summary of their role / responsibilities in a variety of business models.

A Table of Contents for this document is available to view here.

This is a bundle of both UICC Configuration and GlobalPlatform Card v2.1.1 to v2.2 Mapping Guidelines of Existing 2.1.1 Implementations.