![](https://csdnimg.cn/release/download_crawler_static/11670228/bg10.jpg)
GSM Association Non-confidential
Official Document SGP.25 - Embedded UICC for Consumer Devices Protection Profile
V1.0 Page 16 of 153
1.2.1.1 Application Layer
The goal of the Application layer is to implement the eUICC functionalities described in [23]
and [24], which rely on the notion of a Profile. A Profile is the combination of a file structure,
data and applications to be provisioned onto, or present on, an eUICC. Each Profile, combined
with the functionality of the eUICC, behaves basically as a SIM card. An eUICC may contain
more than one Profile, but one and only one is activated at a time. Each Profile is controlled
by a unique ISD-P; consequently, there is one and only one enabled ISD-P at a time on the
eUICC.
A Profile can have several forms:
A Provisioning Profile: A Profile that allows connectivity to a mobile network solely to
provide the provisioning of Profiles;
An Operational Profile: A Profile that allows connectivity to a mobile network;
A Test Profile: A Profile that can only be used in Device Test Mode and cannot be used
to connect to any MNO. The support of this kind of profile is not mandatory for an
eUICC implementation.
This document will use the term “Profile” to describe either Provisioning Profiles, Operational
Profiles, or Test Profiles.
All Profiles include Network Access Applications and associated Parameters, but these
applications rely on the algorithms stored in the platform layer of the eUICC.
In the same manner, the Profile includes policy rules (PPR), but relies on the Platform Layer
to have them enforced on the eUICC. The Profile structure, composed of a set of Profile
Components, is specified by, and under the full control of, the MNO. The full Profile structure
shall be contained in a unique ISD-P. The Profile structure shall contain a Profile Component,
called MNO-SD, which performs an identical Role as the ISD for a UICC. The Profile structure
shall include:
The MNO-SD;
Supplementary Security Domains (SSD) and a CASD;
Applets;
Applications, e.g. NFC applications;
NAAs;
Other elements of the File System;
Profile metadata, including Profile Policy Rules (PPR).
More details on the Profile can be found in [23] and [24].
In addition to Profile data, the eUICC itself has a Rules Authorisation Table (RAT) that is used
by the Profile Policy Enabler (PPE) and the Local Profile Assistant (non-TOE element LPAd) to
determine whether or not a Profile containing PPRs is authorised and can be installed on the
eUICC.
The RAT is initialised at eUICC manufacturing time, or during the initial Device setup provided
that there is no installed Operational Profile. In particular, it cannot be affected by the Memory
Reset function.
ISD-P
The ISD-P is a secure container (Security Domain) for the hosting of a Profile. The ISD-P is
also used for updating the Profile Metadata on behalf of the MNO.
As defined in [24], the ISD-P shall ensure that: