The following meanings apply to SHALL, SHALL NOT, MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY in this document (refer to RFC 2119):
- SHALL indicates an absolute requirement, as does MUST.
- SHALL NOT indicates an absolute prohibition, as does MUST NOT.
- SHOULD and SHOULD NOT indicate recommendations.
- MAY indicates an option.
Selected terms used in this document are included in following table.
| Term | Definition |
|---|---|
| Core Management Platform | Part of the Management Platform not covered by this specification. The core management platform is responsible to create the APDU commands that need to be delivered by the Remote Agent |
| RA Endpoint | Base URI used by the Local Agent to makes the Handshake |
| Command | Message sends by the RA during the Remote Management Step |
| Data Format | How data exchanged between Remote Agent and Local Agent are formatted. Defines as a MIME type. |
| Device | User equipment used in conjunction with an eUICC to connect to a mobile network. E.g. a tablet, wearable, smartphone, or handset. |
| Device Application | Any piece of software in the Device. It may be a Device component or an external third-party application. |
| Handshake | Protocol Step during which the Secure Element and the Protocol Binding to be used for the Remote Management Session is selected. |
| Initialization | Protocol Step during which the sessionID is generated and shared |
| Management Platform | A cloud infrastructure able to manage some Secure Element. |
| Management Session | The timing frame during which the management task associated with a sessionID is performed. |
| Message | A dataset of Properties exchanged during a Management Session. |
| Protocol Binding | Rules associated with a Data Format and a Transport protocol to exchange Message |
| Protocol Step | Part of the Management Session. |
| Remote Agent | A Management Platform intermediate between Core Management Platform and the Local Agent. |
| Remote Management Session | A Protocol Step during which the Remote Platform perform the management of a Secure Element. |
| Response | Message that provides a response to a Command Message |
| Rich Execution Environment | As defined by GP TEE |
| SE Access API | API uses on the Local Agent to forward commands to an application in the Secure Element. |
| Secure Element | Physical component attached with the Device manageable according with GP Card specification. |
| sessionId | An identifier shared between the Device Application and the Management Platform and associated with a Management Session |
| Step | See Protocol Step |
| Transport | The transport protocol used between Remote Agent and Local Agent. |
| Trusted Execution Environment | As defined by GP TEE |
| Local Agent | A Device intermediate between Remote Agent and the Secure Element. |