This document has the objective of testing if a profile is correctly interpreted and correctly loaded on an eUICC. It provides a globally standardised means of testing products which implement Version 2.3.1, Version 2.2, Version 2.1 or Version 2.0 of the eUICC Profile Package: Interoperable Format Technical Specification.
The Profile Elements defined in the test specification are provided separately in ASN1 format. It is mandatory to use the ASN1 files for the creation of the DER codes.
The PEDefinitions V2.100_with_unknownTag.asn shall be used when creating the DER code for Test Case 188.8.131.52 (Check unknown tag in Profile Package) at least for the DF-CUSTOM-by-Generic-File-Management-4 profile element.
The Test Applets used in the Profile Packages are provided as an informative attachment of the specification.
This document defines the technical specification of a standard format to be used for the loading and installation of an interoperable Profile Package in any compliant eUICC.
Version 2.3.1 and ASN Module
Version 2.3 and ASN Module
Version 2.2 and ASN Module
Version 2.1 and ASN Module
Version 2 and ASN Module
Version 1.1 and ASN Module
The objective of this document is to guide implementers of versions 2.3 and version 2.3.1 of the eUICC Profile Package Technical Specification in case it is used in an eUICC developed according to version 2.2.1 or earlier of the GSMA Specification SGP.22 (RSP technical specification).
Early Deployment of Version 2.3 for 5G Support
This ecosystem framework document describes the functions and actors involved when loading firmware to a Tamper Resistant Element (TRE).
This document defines the interface between the IDS and the OFL Agent. It complements a GlobalPlatform fast track specification published in 2017 that defines how Tamper Resistant Element (TRE) firmware can be loaded and managed onto various TRE form factors – including SEs such as removable, embedded and integrated SIMs – after a device has been issued.
This document makes it easier for mobile network operators (MNOs), service and solution providers to deploy Mobile Connect services which use an authentication application provisioned on the user’s SIM card.
The Open Mobile API (OMAPI) Specification defines how mobile applications may access different secure elements (SEs), including the UICC and embedded secure elements (eSEs) in a mobile device. Ownership of the OMAPI Specification has been transferred to GlobalPlatform.
Open Mobile API Specification: Second Errata for Version 3.2
Open Mobile API Specification: Errata for Version 3.1
Test Applets for OMAPI Test Specification for Transport API: v2.2 and Errata
Open Mobile API Test Specification for Transport API: Errata for v2.2
Open Mobile API Test Specification for Transport API Version 2.2
Open Mobile API Specification: Errata for Version 3.2
Open Mobile API Specification Version 3.2
Test Applets for OMAPI Test Specification for Transport API v2.0
Open Mobile API Specification Version 3.1
Open Mobile API Test Specification for Transport API Version 2.0
Open Mobile API Specification Version 3.0
Open Mobile API Test Specification for Transport API Version 1.1
Open Mobile API – Test Application
Open Mobile API Test Specification Version 1.0 – Errata Note
Open Mobile API Test Specification for Transport API Version 1.0
Open Mobile API Specification Version 2.05
Open Mobile API Test Specification for Transport API Version 0.9
Open Mobile API Specification Version 2.04
Open Mobile API Specification Version 2.03
Open Mobile API Specification Version 2.02
Open Mobile API Specification – Transport API Test Plan
Open Mobile API Specification – An Introduction
This document defines recommendations for UICC configuration and feature requirements in mobile near field communication (NFC) payments. The aim of this document is to provide guidelines that support service providers, mobile network operators (MNOs), manufacturers and implementers of mobile NFC payment services, by facilitating system integration, simplifying interoperability and reducing market fragmentation.
This document provides interoperability-focused technical considerations, recommendations and specification extracts needed to simplify the development, deployment and support of NFC services across UICC and embedded SE (eSE).
General guidelines intended to ensure that a SIM’s security levels are optimally maintained.
This technical requirements document identifies the integrated UICC features to maximise service
delivery and commercial utilisation of LTE/EPS networks.
This document is a collection of guidelines and recommendations for optimal support of the UICC by device manufacturers designing handsets, tablets, modems and other devices making use of a telecom UICC.
A set of interoperability collaterals containing detailed specifications, standardisation considerations and pragmatic tips to simplify the development, implementation and support of NFC contactless services and applications.
The CAT Loader 2.0 enables network operators and service developers to manage ETSI toolkit applications compliant with the latest release using the high-speed CAT-TP protocol, and allows users to download and install applications on the SIM card, as well as analyse card content and remove applications.
This document specifies the requirements to implement a unified XML schema for SIM cards prototyping and testing. ‘SIMpml’ refers to SIM Profile Mark-Up Language.
This document is a practical guide to interoperability with tips and suggestions to help service developers design applications that will work with any USIM card.