Menu

GSMA · Specification

SGP.32v1.1

eSIM IoT Technical Specification

Specifies the technical solution for remotely provisioning and managing eUICCs in IoT devices, supporting interoperability across deployment scenarios.

Version
v1.1
  1. v1.32026-05-22
  2. v1.22024-06-27
  3. v1.12024-04-26
  4. v1.0.12023-07-04
  5. v1.02023-05-26
Issued
2024-04-26
Source
Original PDF

A formatted version of this document is not available yet; the text below is extracted clause by clause, so tables and figures may be incomplete.

Overview

This specification describes remote provisioning and management of eUICCs in IoT devices with network-constrained and/or user-interface-constrained operation. It defines the IoT eUICC architecture, roles, interfaces, security functions, profile handling, and procedures for provisioning, configuration, state management, and notifications. It also specifies interface bindings over HTTP and CoAP, with ASN.1 and JSON function bindings, and includes mappings for LwM2M and MQTT. The solution is intended to provide a basis for global interoperability across supported deployment scenarios.

  • eUICC
  • HTTP
  • CoAP
  • ASN.1
  • JSON
  • LwM2M

Overview generated automatically from the document's scope and outline. The document text is authoritative.

Changes since v1.0.1

125 clauses modified, 28 clauses added, 5 clauses removed

Compared automatically clause by clause from the extracted text of both versions; differences only in layout, spacing or table cells are ignored. The documents are authoritative.

1.2 Scopemodified

This specification provides a technical description of: - The remote provisioning and management of the eUICC in IoT Network Constrained and/or User Interface Constrained Devices. - The eUICC architecture for IoT Devices. - The interfaces used within the eSIM IoT architecture; and - The security functions used within the eSIM IoT architecture.

1.5 Definition of Termsmodified

Term Description Activation Code As defined in SGP.22 [4]. Activation Code Token As defined in SGP.22 [4]. Associated eIM As defined in SGP.31 [1]. Bound Profile Package As defined in SGP.31 [1]. Certificate Public key certificate. Certification Authority An authority which issues public key certificates. CoAPA Constrainedset Applicationof Protocol.data (e.g. APN, login, password, …) required by the IPA Connectivity Parameters to open a communication channel (e.g. HTTPS, CoAP) on a dedicated network. Device Baseband A device component that manages the cellular radio functions. DTLS Datagram Transport Layer Security. eIM Configuration Data As defined in SGP.31 [1]. eIM Configuration Operation As defined in SGP.31 [1]. eIM Package Contains an eUICC Package, a request for IPA and/or eUICC data, a Profile download trigger (e.g., containing an Activation eIM Package Code) or acknowledgements of eUICC Package Results and Notifications. eIM Package Result Execution result of an eIM Package. eUICCEmergency Mechanism As defined in SGP.22SGP.31 [4].[1]. Emergency Profile As defined in SGP.31 [1]. eUICC PackageAs defined in SGP.22 [4]. A cryptographically signed package prepared by the eIM that eUICC Package contains either PSMO(s) or eCO(s). The package is verified and executed by the eUICC. eUICC Package Result A cryptographically signed package prepared by the eUICC that eUICC Package Result contains the execution result of the eUICC Package. Event As defined in SGP.22 [4]. EventID As defined in SGP.22 [4]. Event Deletion A process of deleting an Event from an SM-DS by the SM-DP+. Event Record As defined in SGP.22 [4]. Event Registration As defined in SGP.22 [4]. A process of retrieving from the SM-DS any available Event Retrieval information for a specific eUICC registered by a specific SM- DP+ or a specific SM-DS. This is an attribute of a Profile which, when set, identifies the Fallback Attribute Profile to be enabled by the Fallback Mechanism. eUICC-based mechanism which enables and disables the Fallback Mechanism Profile with Fallback Attribute set. Fallback Profile An Operational Profile having the Fallback Attribute set. Field-Test eUICC As defined in SGP.22 [4] IoT As defined in SGP.31 [1]. IoT Device As defined in SGP.31 [1]. IPA Capabilities Indicates to the eIM what the IPA is capable of related to the functional split of Profile download between the eIM and the IPA IPA Capabilities and the use of compact data object structures in ESipa functions. MatchingId As defined in SGP.22 [4]. Mobile Service Provider As defined in SGP.31 [1]. Network Constrained Device As defined in SGP.31 [1]. Notification As defined in SGP.22 [4]. Notification Recei … [4]. Operator As defined in SGP.22 [4]. Profile As defined in SGP.22 [4]. Profile Metadata As defined in SGP.22 [4]. Profile Package As defined in SGP.31 [1]. … Profile Package Interpreter An eUICC Operating System service that translates the Profile Profile Package Interpreter Package data into an installed Profile using the specific internal format of the target eUICC. Profile State Management Operation (PSMO) As defined in SGP.31 [1]. Operation Provisioning Profile As defined in SGP.22 [4]. Registered PLMN As defined in 3GPP TS 23.122 [19]. Rollback Mechanism As defined in SGP.31 [1]. Root SM-DS As defined in SGP.22 [4]. RSP Server As defined in SGP.22 [4]. Rules Authorisation Table As defined in SGP.22 [4]. Signed eCO eIM Configuration Operation performed by an Associated eIM Signed eCO using cryptographically signed eIM Configuration Operation that contains the eIM Configuration Data. Subscription Manager Data Preparation (SM-DP+) As defined in SGP.22 [4]. Preparation Subscription Manager Discovery Server (SM-DS) As defined in SGP.22 [4]. TelecomDiscovery FrameworkServer An eUICC Operating System service that provides standardised network authentication algorithms to the network authentication Telecom Framework applications hosted in the ISD-Ps. Furthermore, it provides capabilities to configure the algorithm with necessary parameters in the Enabled Profile. Test Profile As defined in SGP.22 [4]. TLSNon-cryptographically Transportsigned Layer Security. Unsigned eCO Non-signed eIM Configuration Operation of the Unsigned eCO initial eIM. User Interface Constrained Device As defined in SGP.31 [1]. Device

1.6 Abbreviationsmodified

Abbreviation Description CA Certification Authority CoAP Constrained Application Protocol. CRL Certificate Revocation List DTLS Datagram Transport Layer Security. ECASD eUICC Controlling Authority Security Domain eCO eIM Configuration Operation EID eUICC-IDeUICC-IDentifier as defined in SGP.22 [4] eIM eSIM IoT Remote Manager eIMID eIM Identifier EUM eUICC Manufacturer IoT Internet of Things IPA IoT Profile Assistant IPAd IoT Profile Assistant in the IoT Device IPAe IoT Profile Assistant in the eUICC ISD … Rules Authorisation Table RPLMN Registered Public Land Mobile Network SM-DP+ Subscription Manager Data Preparation + SM-DS Subscription Manager Discovery Server … TLS Transport Layer Security. UICD User Interface Constrained Device

1.7 Referencesmodified

|Document Ref | Document | Title | Number | [1] | SGP.31 | eSIM IoT Architecture and Requirements, version 1.11.2 | [2] | RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels, S. Bradner[2] |RFC [3]2119 |Bradner [3] RFC 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words | [4] | SGP.22 | RSP Technical Specification, version 2.5 | [5] | ETSI TS 102 223 | Smart Cards; Card Application Toolkit (CAT) | [6] | SGP.02 | GSMA Remote Provisioning of Embedded UICC Technical specification version 4.24.3 | [7] | RFC 7252 | The Constrained Application Protocol (CoAP) | [8] | RFC 5246 | The Transport Layer Security (TLS) Protocol Version 1.2 | [9] | RFC 8446 | The Transport Layer Security (TLS) Protocol Version 1.3 | [10] | RFC 6347 | Datagram Transport Layer Security Version 1.2 | [11] | RFC 9147 | The Datagram Transport Layer Security (DTLS) Protocol Version 1.3 | [12] | RFC 7959 | Block-Wise Transfers in the Constrained Application Protocol (CoAP) | [13] | RFC 9175 | Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token Processing | [14] | RFC 9146 | Connection Identifier for DTLS 1.2 | [15] | RFC 8422 | Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS) Versions 1.2 and earlier | [16] | RFC 7027 | Elliptic Curve Cryptography (ECC) Brainpool Curves for Transport Layer Security (TLS) | [17] | RFC 5289 | TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM) | [18] | RFC 8410 | Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key Infrastructure | [19] | 3GPP TS 23.122 | 3rd Generation Partnership Project; | Technical Specification Group Core Network and Terminals; |[19] 3GPP TS 23.122 Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | [20] | RFC 5077 | Transport Layer Security (TLS) Session Resumption without Server-Side State | [21] | RFC 6960 | X.509 Internet Public Key Infrastructure Online Certificate Status Protocol – OCSP | [22] | 3GPP TS 24.008 | 3rd Generation Partnership Project; | Technical Specification Group Core Network and Terminals; |[22] 3GPP TS 24.008 Mobile radio interface Layer 3 specification; | Core network protocols; | Stage 3 | [23] | MQTTs | MQTTs version 5.0 based on TLS | [24] | RFC 5639 | Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation | [25] | RFC 5280 | Internet X.509 Public Key Infrastructure Certificate and Certificate RFC 5280 Revocation List (CRL) Profile | [26] | ANSSI ECC | Avis relatif aux paramètres de courbes elliptiques définis par l'Etat ANSSI ECC français. JORF n°0241 du 16 octobre 2011 page 17533. texte n° 30. 2011 | [27] | RFC 5480 | Elliptic Curve Cryptography Subject Public Key Information | [28] | ISO 14888-3 | IT Security techniques — Digital signatures with appendix — Part ISO 14888-3 3: Discrete logarithm-based mechanisms | [29] | TCA eUICC Profile PackagePackage: |Interoperable Format Technical eUICC Profile Package:Specification InteroperablePackage Format[30] TechnicalOMA LwM2M OMA LwM2M Object and Resource Registry : Object and Resource https://technical.openmobilealliance.org/OMNA/LwM2M/Lw Registry M2MRegistry.html [31] RFC 2818 HTTP Over TLS. [32] GPC_SPE_034 GlobalPlatform Technology Card Specification |v2.3.1 [33] GPD_SPE_075 GlobalPlatform Technology Open Mobile API Specification v3.3 [34] Smart Cards; UICC-Terminal interface; Physical and logical ETSI 102 221 characteristics [35] RFC 6066 Transport Layer Security (TLS) Extensions: Extension Definitions [36] RFC 7159 The JavaScript Object Notation (JSON) Data Interchange Format

1.9 References to SGP.22modified

The present document contains several references to SGP.22 [4]. The following list maps the terms used by SGP.22 [4] to the terms used in the present document: - LPA (Local Profile Assistant) refers to IPA.

2.1.1 Architecture Diagram with IPA in the IoT Devicemodified

This section further specifies the roles and interfaces associated with the Remote SIM Provisioning and Management with the IPA in the IoT Device (Figure 1). []ES12 1.SM-DP+ :ES2+ Operator ES9+’ ES9 SM-DS ES8+ + ES8+ ES11’ eSIM IoT remote Manager ESipa ES6 ES8+ ES8 ES11 + ESep IPAd ES10a ES10b ISD-R ISD-P eUICC MNO-SD IoT Device Figure 1 eSIM IoT Functional Architecture (IPA in the IoT Device)

2.1.2 Architecture Diagram with IPA in the eUICCmodified

This section further specifies the roles and interfaces associated with the Remote SIM Provisioning and Management with the IPA in the eUICC (Figure 2).[]2). 2.ES12 :SM-DP SM-DP+ ES2+ Operator ES9+’ SM-DS ES8+ ES9+ ES11’ ES8+ eSIM IoT remote Manager ESipa ESep ES6 ES8+ ES8+ ES8+ IPAe ES11 ES8+ ISD-R ISD-P MNO-SD eUICC IoT Device Figure 2 eSIM IoT Functional Architecture (IPA in the eUICC)

2.1.3 ASN.1modified

The description of some data objects in this specification is based on ASN.1 specified in ITU‑TITU-T X.680 [49] and encoded in TLV structures using DER (Distinguished Encoding Rule) encoding as specified in ITU-T X.690 [50]. This provides a flexible descriptio … ) asn1modules(1) sgp32v1(31)} DEFINITIONS AUTOMATIC TAGS EXTENSIBILITY IMPLIED ::= BEGIN IMPORTS Certificate, SubjectPublicKeyInfo FROM PKIX1Explicit88 {iso(1) … identified-organization(3)identified- organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-pkix1-explicit(18)}id- pkix1-explicit(18)} SubjectKeyIdentifier FROM PKIX1Implicit88 {iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-pkix1-implicit(19)} ProfileInfo, EuiccSigned1, CancelSessionReason, RetrieveNotificationsListResponse, ServerSigned1, RspCapability, Iccid, TransactionId, ProfileInfoListRequest, ProfileInfoListResponse, RulesAuthorisationTable, EUICCInfo1, DeviceInfo, VersionType, UICCCapability, SubjectKeyIndentifier, PprIds, CertificationDataObject, Octet1, Octet16, Octet32, PrepareDownloadResponse, PrepareDownloadResponseOk, PrepareDownloadResponseError, AuthenticateServerResponse, AuthenticateResponseOk, AuthenticateResponseError, CtxParams1, ProfileInstallationResult, ProfileInstallationResultData, OtherSignedNotification, EuiccSignPIR, ErrorResult, NotificationMetadata, CancelSessionResponse, CancelSessionResponseOk, CancelSessionResponseError,SmdpSigned2, StoreMetadataRequest,BoundProfilePackage, SmdpSigned2,NotificationEvent, BoundProfilePackageVendorSpecificExtension, DpProprietaryData, OperatorId, NotificationConfigurationInformation, ProfileClass, IconType, ProfileState, OctetTo16 FROM RSPDefinitions {joint-iso-itu-t(2) international-organizations(23) gsma(146) rsp(1) asn1modules(1) sgp22v2(2)}; -- ASN1STOP Two encoding/decoding attributes are defined: - AUTOMATIC TAGS means that the tags are defined automatically using the encoding rules unless a tag notation is present in a data object format definition. - EXTENSIBILITY IMPLIED means that types MAY have elements that are not defined in this specification. This means that decoders SHALL be able to handle values wi… …

2.3 Interfacesmodified

… Profile download at the IPA and to provide a secure transport for the delivery of eUICC Packages, unless the underlying transport provides necessary security. … 1.Table :1 Interfaces NOTE: Support of the ES10c interface as defined in SGP.22 [4] is out of scope of this specification.

2.4.1.1 eUICC Architecture Diagram (IPA in the IoT Device)modified

The following diagram represents the eUICC architecture when the IPA is located in the IoT Device. []the 3.IoT :Device To Operator To SM-DP+ To IPA in To eIM ES6 ES8+ ESep ES10a,b eUICC Operating System Profile ISD-P ISD-P Policy IPA Enabler MNO-SD MNO-SD Services ISD-R Profile File System Package File System Applets CASD Applets NAAs CASD SSD Interpreter NAAs SSD ECASD Telecom Framework Operator Disabled Profile Operator Enabled Profile Figure 3 Schematic Representation of the eUICC (IPA in the Device)

2.4.1.2 eUICC Architecture Diagram (IPA in the eUICC)modified

The following diagram represents the eUICC architecture when the IPA is located in the eUICC. []To 4.SM-DP+ :To Operator To SM-DP+ To SM-DS To eIM To eIM ES9+ ESipa ES11 ESep ES6 ES8+ eUICC Operating System ISD-P IPA in the Profile Policy ISD-P eUICC Enabler MNO-SD MNO-SD IPA Profile Services File System Package File System Applets CASD Applets Interpreter NAAs CASD NAAs SSD SSD ISD-R Telecom ECASD Framework Operator Disabled Profile Operator Enabled Profile Figure 4 Schematic Representation of the eUICC (IPA in the eUICC)

2.4.4 ISD-Pmodified

The ISD-P entity as defined in SGP.22 [4]. In addition to the current ISD-P as defined in SGP.22, the Connectivity Parameters MAY be included as per Table 93 from SGP.02 [6], with the exception of parameters related to SMS, and Table 95 from SGP.02 [6].

2.4.9 IPA Servicesmodified

This role provides the necessary access to the services and data required by functions of the IPA. These services include: - Provide the address of the Root SM-DS and (if configured) the default SM-DP+ - Transfer Bound Profile Package from the IPAd to the ISD-P - Provide list of installed Profiles and their Profile Metadata - Retrieve EID - Provide Profile State Management Operations - Provide eUICC execution results and Notifications.

2.6.3.1 TLS Requirements for communication to the RSP Serversmodified

… section 2.6.6 and 6.1 (and its subsections) of SGP.22 [4] SHALL apply, where the IPA plays the role of the LPA. In addition, the following requirements apply: … - TLS with server authentication SHALL be used over ES9+’ (eIM with SM-DP+), and ES11’ (eIM with SM-DS). NOTE: Here the eIM is playing the role of the LPA. - TLS with mutual authentication MAY be used over ES2+. If TLS with mutual authentication is not used over ES2+, ES2+ SHALL be protected with level of security equivalent to TLS.

2.6.3.2 TLS/DTLS Requirements for communication to the eIMmodified

…, or trusts the CA to which the server Certificate chains back or trusts an intermediate CA along the path. The following elliptic curve(s) SHALL be supported: … - NIST P-256 with the namedCurve secp256r1 (23) as defined in RFC 8422 [15] The following elliptic curves MAY be supported: - brainpoolP256r1(26) as defined in RFC 7027 [16], - NIST P-384 with the namedCurve secp384r1 (24) as defined in RFC 8422 [15], - Ed25519 as defined in RFC 8410 [18], and x25519 with the namedCurve x25519 (29) as defined in RFC 8422 [15] The following cipher suites SHALL be supported: - For (D)TLS 1.2 -o TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC 5289 [17] -o TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 [17] - For (D)TLS 1.3 -o TLS_AES_128_GCM_SHA256 as defined in TLS 1.3 (RFC 8446 [9]) -o TLS_AES_256_GCM_SHA384 as defined in TLS 1.3 (RFC 8446 [9]) The following cipher suites MAY be supported: - For (D)TLS 1.2 -o TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289 [17] - For (D)TLS 1.3 -o TLS_CHACHA20_POLY1305_SHA256 as defined in TLS 1.3 (RFC 8446 [9])

2.6.4.1 eIM Keys and eIM Certificates Naming Conventionsmodified

The eIM keys and eIM Certificates used in this specification are named according to the conventions described in this section. The general name structure is: <XX>. <YY>. <ZZ> Where: - <XX> designates the nature of the element, the following values are defined: -o PK: the public key of an asymmetric key pair -o SK: the private key of an asymmetric key pair -o CERT: a Certificate containing a public key - <YY> designates the owner of the element, the following values are defined: -o EIM: an eIM - <ZZ> designates the usage of the element, the following values are defined: -o ECDSA: for a digital signature -o TLS: for TLS connection establishment -o DTLS: for DTLS connection establishment Examples: - PK.EIM.ECDSA: Public key of an eIM, used to verify an eIM signature. - CERT.EIM.TLS: Certificate of the eIM, used to establish TLS connection.

2.6.4.2 Algorithms and Parameters for eIM Signing Keymodified

…For section 'subjectPublicKeyInfo' the following settings SHALL apply: 'AlgorithmIdentifier.algorithm' field SHALL be set to: "iso (1) member-body (2) us (840) … ansi-X9-62(10045)ansi- X9-62(10045) keyType (2) ecPublicKey (1)" as defined in RFC 5480 [27], or 'AlgorithmIdentifier.parameters' field SHALL be set to: - for BrainpoolP256r1: "iso (1) identified-organization (3) teletrust (36) algorithm (3) signatureAlgorithm (3) ecSign (2) ecStdCurvesAndGeneration (8) ellipticCurve (1) versionOne (1) brainpoolP256r1 (7)" as defined in RFC 5639 [24] - for NIST P-256: "iso (1) member-body (2) us (840) ansi-X9-62 (10045) curves (3) prime (1) prime256v1(7)" as defined in RFC 5480 [27]

2.6.4.3 eIM Signing Certificate (CERT.EIM.ECDSA)modified

This specification supports X.509 certificate format as defined in RFC 5280 [25]. The table below describes the common fields that a CERT.EIM.ECDSA SHALL contain. | Certificate common fields | Field | Value Description | tbsCertificate | Data to be signed | Field | Value Description | version | Version SHALL be 3. | serialNumber | Certificate serial number. | signature | Contains the algorithm identifier used to compute the value of the field 'signatureValue'. | NOTE: The algorithm identifier value SHALL be the same as the one of the field 'signatureAlgorithm'. | issuer | Distinguished Name of the entity that has signed the certificate. | validity | Validity period of the eIM Certificate. | subject | Distinguished Name of the entity owning the certificate. The following DN components SHALL be used: | CN=<eIMiD> -- mandatory | C=<country code> -- mandatory | O=<company> -- optional | OU=<organizational unit> -- optional | L=<locality> -- optional | subjectPublicKeyInfo | Contains the algorithm identifier, parameters, and public key value. | Algorithm identifier and parameters SHALL be set according to section 2.6.4.2 | subjectPublicKeyInfo.subjectPublicKey contains the public key value and SHALL be coded as defined in RFC 5480 [27]. | Extension for Authority Key Identifier (RFC 5280 [17] section 4.2.1.1) | extnID = id-ce-authorityKeyIdentifier |Authority Key critical = false |Identifier (RFC 5280 extnValue = <Identifier of the public key to verify this certificate>[25] |section 4.2.1.1) certificate> To identify the CA public key that has to be used to verify this certificate. | Extensions for Key Usage (RFC 5280 [17] section 4.2.1.3) | Extension for Key usage (RFC 5280 [25] section Usage (RFC 5280 4.2.1.3): |[25] section 4.2.1.3) extnID = id-ce-keyUsage | critical = true | extnValue = digitalSignature (0) | Other extensions | CRL and OCSP SHOULD NOT be defined, since the eUICC will have no means to access those. | Policies SHOULD NOT be defined since they will increase the certificate size. | Subject Alternative Names SHOULD NOT be specified. | signatureAlgorithm | Section 2.6.4.2 | signatureValue | Signature computed accordingly to one of the possible algorithms listed in section 2.6.4.2 |Table 2. :2 eIM Certificate fields

2.6.4.4 eIM TLS/DTLS Certificate (CERT.EIM.TLS)added

This specification supports X.509 certificate format as defined in RFC 5280 [25]. The table below describes the common fields that a CERT.EIM.TLS or CERT.EIM.DTLS SHALL contain. NOTE: If the eIM supports both TLS and DTLS, it may use the same certificate. Certificate common fields Field Value Description tbsCertificate Data to be signed Field Value Description version Version SHALL be 3. serialNumber Certificate serial number. signature Contains the algorithm identifier used to compute the value of the field 'signatureValue'. NOTE: The algorithm identifier value SHALL be the same as the one of the field 'signatureAlgorithm'. issuer Distinguished Name of the entity that has signed the certificate. validity Validity period of the eIM TLS/DTLS Certificate. subject Distinguished Name of the entity owning the certificate. The following DN components SHALL be used: CN=<eIMiD> -- mandatory C=<country code> -- mandatory O=<company> -- optional OU=<organizational unit> -- optional L=<locality> -- optional subjectPublicKeyInfo Contains the algorithm identifier, parameters, and public key value. Algorithm identifier and parameters SHALL be set according to section 2.6.4.2 subjectPublicKeyInfo.subjectPublicKey contains the public key value and SHALL be coded as defined in RFC 5480 [27]. Extension for extnID = id-ce-authorityKeyIdentifier Authority Key critical = false Identifier (RFC 5280 extnValue = <Identifier of the public key to verify this [25] section 4.2.1.1) certificate> To identify the CA public key that has to be used to verify this certificate. Extensions for Key Extension for Key usage (RFC 5280 [25] section Usage (RFC 5280 4.2.1.3): [25] section 4.2.1.3) extnID = id-ce-keyUsage critical = true extnValue = digitalSignature (0) Extensions for extnID = id-ce-subjectAltName subjectAltName critical = false (RFC 5280 [25] section 4.2.1.6): extnValue = GeneralNames ::= { { dNSName '<eIM hostname (FQDN) value>' }, { registeredID '<eIM OID value>' } } This extension SHALL contain at least one dNSName entry, and only one registeredID entry. A dNSName entry MAY contain the wildcard character * as allowed by RFC 2818 [31]. Extension for Extension for Extended Key usage (RFC 5280 [25] extendedKeyUsage section 4.2.1.12): (RFC 5280 [25] extnID = id-ce-extKeyUsage section 4.2.1.12) critical = true extnValue = ExtKeyUsageSyntax ::{ { id-kp-serverAuth }, { id-kp-clientAuth } } Certificate SHALL not contain any other extended key usage. Other extensions Extension for CRL Distribution Points (RFC 5280 [25] section 4.2.1.13). Policies SHOULD NOT be defined since they will increase the certificate size. signatureAlgorithm Section 2.6.4.2 signatureValue Signature computed accordingly to one of the possible algorithms listed in section 2.6.4.2 Table 3 eIM TLS/DTLS Certificate fields

2.6.5 Use of Server Name indication extension (SNI) for ESipa.added

Server Name Indication, often abbreviated SNI, is an extension for TLS protocol. This extension allows multiple hostnames and consequently multiple TLS certificates to be served over HTTPS from the same IP address. This capacity could be useful for the eIM server to select the right TLS certificate chain that IPA is able to verify. This section provides to the IPA and the eIM Server a mechanism to guide the eIM Server selection of an appropriate TLS certificate chain. The eIM Server and the IPA SHOULD support this mechanism. An eIM Server and an IPA that support this mechanism SHALL comply with this section. IPA/Device side: An IPA SHALL perform a DNS resolution using the eIM FQDN registered during the eIM association, then IPA SHALL proceed with the TLS handshake including the "server_name" extension defined in RFC 6066 [35] in the ClientHello containing the eIM FQDN. If the eIM Server replies with a fatal-level alert different from unrecognized_name(112), the IPA SHALL retry the TLS handshake without sending the Server Name indication extension. NOTE: This section is also applicable to the IPAe. eIM Server side: The eIM Server SHALL take care that its domain names in their final encoding do not violate the length limits of domain names. The eIM Server SHALL support the "server_name" extension to determine the TLS certificate to use. • If the received ClientHello message contains the "server_name" extension with an unrecognized FQDN, the eIM Server SHALL abort the handshake by sending a fatal- level unrecognized_name(112) alert. • If the received ClientHello message doesn't contain the "server_name" extension, the eIM Server SHOULD use a TLS certificate associated with a default domain.

2.7.2 eUICC/EUM Certificatesmodified

…r eIM SHALL NOT pass any revocation information (CRL, OCSP) to the eUICC. The eUICC Certificates (i.e., CERT.EUICC.ECDSA) according to SGP.22 [4] SHALL be used. … A Field-Test eUICC MAY contain certificates that chain up to the GSMA CI for the purpose of integration and/or end-to-end testing, as defined in SGP.22 [4].

2.7.3 eIM Certificatesmodified

The following Certificates MAY be supported, and MAY be revoked at any time: - eIM Certificate for signing eUICC Packages (if any) - eIM DTLS/TLS Certificate (if any) The issuance, verification and revocation of eIM Certificates for signing eUICC Packages are implementation specific and out … …

2.9.2 Immediate Profile enabling of an IPA initiated Profile download from default SM-DP+modified was Automatic Profile enabling of an IPA initiated Profile download from Default SM-DP+

…to successful download and installation, the IPA MAY also request the eUICC to enable this newly downloaded Profile. The eUICC MAY be configured to support the … automaticimmediate enablingenabling: by:by - EUMs during eUICC manufacturing, -or Anby an Associated eIM via PSMO, or -by the IPA via ES10b only if there is no Associated eIM. If automaticimmediate enabling is not configured within the eUICC, the request for automaticimmediate Profile enabling SHALL be rejected. An eUICC configured to support the automaticimmediate enabling and requested by IPA to automaticallyimmediately enable a particular Profile, SHALL verify that the OID and FQDN of the SM-DP+ from where the Profile is downloaded match to the default SM-DP+ data (OID and FQDN) stored in the eUICC (see section 3.2.3.1). The storage of the default SM-DP+ data MAY be performed according to the following options: -by EUMs during eUICC manufacturing, -or by an Associated eIM,eIM via PSMO, or -by the IPA via ES10b only if there is no Associated eIM. NOTE: SM-DS triggered Profile download and automaticimmediate enabling without signed PSMO from any potentially Associated eIM is not specified in this version of the specification.

2.10 eIM Configurationmodified

In order to perform Profile State Management Operation on a given eUICC, an eIM SHALL be associated with this eUICC. For every Associated eIM the eUICC stores the eIM Configuration Data (see section 2.11.2.1.1)2.11.1.1.1) that is used by the eUICC for verification of signed PSMOs and Signed eIM Configuration Operations as part of eUICC Package(s). eIM Configuration Operations MA… …

2.10.1 eIM Configuration by eIMmodified

… contains one or more eIM Configuration Operations. The following eIM Configuration Operations MAY be supported by the eIM and SHALL be supported by the eUICC: … - addEim: Adds an Associated eIM to the eUICC by providing its eIM Configuration Data including the eimID to the eUICC. - deleteEim: Deletes an Associated eIM identified by its eimID from the eUICC. If the successfully deleted Associated eIM was the last available Associated eIM, the eUICC SHALL allow ES10b.AddInitialEim again. - updateEim: Updates eIM Configuration Data, i.e., the public key or Certificate and the related anti-replay counter value of an Associated eIM with a given eimID within the eUICC while keeping the same eimID. - listEim: Requests the eUICC to provide a list of all currently configured Associated eIMs to the eIM. NOTE:NOTE1: Replacing an existing Associated eIM with a new Associated eIM could be realized by first adding a new Associated eIM and then deleting the existing Associated eIM. NOTE:NOTE2: How the eIM triggers the IPA is out of scope of this specification.

2.10.2 eIM configuration by IPAmodified

If an eUICC does not have an Associated eIM, the eUICC SHALL accept Unsigned eCO. To enable Unsigned eCO, the IPAd MAY and the eUICC SHALL support the following function: - ES10b.AddInitialEim: Adds eIM Configuration Data of a particular eIM with a given eimID to an eUICC that does not yet contain any Associated eIM. NOTE: Mechanis… …

2.11 eIM Package Structuresmodified

This section describes the structure of eIM Package requests and responses that comprise: - Signed eUICC Package and its execution result. - IPA and/or eUICC data - Profile Download trigger - List of Notifications - Acknowledgements of eUICC Package Results and Notifications

2.11.1 eIM Package Requestmodified

The eIM Package request contains either: - an EuiccPackageRequest, - an IpaEuiccDataRequest, - a ProfileDownloadTrigger,ProfileDownloadTriggerRequest, or - an EimAcknowledgements data object.

2.11.1.1 EuiccPackageRequestmodified

…tedForPsmoV1.0.0# euiccPackageSigned EuiccPackageSigned, eimSignature [APPLICATION 55] OCTET STRING -- Tag '5F37' } EuiccPackageSigned ::= SEQUENCE { eimId [0] … UTF8String,UTF8String (SIZE(1..128)), eidValue [APPLICATION 26] Octet16, -- Tag '5A' counterValue [1] INTEGER, transactionIdeimTransactionId [2] TransactionId OPTIONAL, euiccPackage EuiccPackage } EuiccPackage ::= CHOICE { psmoList SEQUENCE OF Psmo, -- #SupportedForPsmoV1.0.0# ecoList SEQUENCE OF Eco -- #SupportedForEcoV1.0.0# } -- ASN1STOP The euiccPackageSigned includes: - eIM identifier (eimId) : identifier of the eIM that issues the eUICC Package. See section 4.3. - EID (eidValue) of the targeted eUICC. - Counter value (counterValue) used by the eIM for replay protection. Each eIM manages its own counter. The eIM increments its counterValue by 1 for each eUICC Package being sent to the target eUICC. The eUICC implementation SHALL be able to handle counter values at least up to value of 8388607 (0x7FFFFF), included. - Optional Transaction ID (transactionId,(eimTransactionId, see [4]). - eUICC Package (euiccPackage) consisting of either PSMOs or eCOs. The eIM SHALL sign the euiccPackageSigned data object concatenated with the associationToken da … ata, the associationToken data object SHALL be used with the value set to zero (i.e., '84 01 00') for creating the signature. The eUICC returns the same eimId, … transactionIdeimTransactionId and counterValue in the eUICC Package Result, which allows the eIM to link a received eUICC Package Result to a sent eUICC Package.

2.11.1.1.1 eIM Configuration Dataremoved

The eIM Configuration Data stored by the eUICC for each Associated eIM consists of: - eimId: uniquely identifies the Associated eIM within the eUICC. See section 4.3. - eimFqdn: Identifier of the eIM that issues the eUICC Package encoded as a FQDN. - eimIdType: For more information regarding eIM identifier types (EimIdType) see section 4.3. - counterValue: used to protect against replay of eUICC Packages sent by the eIM. The highest received counterValue per Associated eIM is stored within the eUICC. The eUICC implementation SHALL be able to handle counter values at least up to value of 8388607 (0x7FFFFF), included. The eUICC SHALL return the error code counterValueOutOfRange in case the counterValue exceeds the maximum value supported by the eUICC. - associationToken: optional, for replay protection. The association token is the value of one global counter on each eUICC, which SHALL start at zero and SHALL be incremented to generate the next association token each time an association token is requested (i.e., the first association token will be 1). It SHALL NOT be possible to reset the counter by any mechanism (e.g., eUICC Memory Reset). NOTE: The association token can protect against an attack scenario where a whole sequence of operations beginning with AddInitialEim is replayed after a reset of the eIM Configuration Data. It is optional to configure this mechanism for an eIM. - eimPublicKeyData: eIM public key data either as a raw public key (eimPublicKey) or as a Certificate (eimCertificate) , used for eUICC Package verification. - trustedPublicKeyDataTls: either eIM public key (trustedEimPkTls) or a Certificate (trustedCertificateTls) used for TLS/DTLS. The trustedCertificateTls is a certificate that is trusted in the chain of certificates ending with the eIM certificate (leaf certificate). This certificate MAY be the certificate of the eIM itself, or the certificate of the root CA or the certificate of a trusted intermediate CA. This certificate SHALL contain the SubjectKeyIdentifier extension. A root CA or intermediate CA certificate SHALL include the BasicConstraints extension with the value of “cA” set to TRUE[25]. The IPAd MAY ignore this field. - eimSupportedProtocol: For more information regarding eIM protocol support (EimSupportedProtocol) see section 4.2. - euiccCiPKId: CI Public Key Identier allowing to select the eUICC Certificate for signing eUICC Package Results returned to this eIM. If not provided, the first entry of euiccCiPKIdListForSigning in eUICCInfo2 SHALL be used as euiccCiPKId.. NOTE: trustedCertificateTls data object is needed if the IoT Device uses the IPAe and the eIM Package transfer use eimRetrieveHttps or eimRetrieveCoaps. This will allow to avoid any potential failure of the TLS/DTLS session. When adding, updating, or retrieving eIM Configuration Data for a particular eIM from the eUICC the following ASN.1 data object is used, where the optionality of certain fields is described below: -- ASN1START EimConfigurationData ::= SEQUENCE { eimId [0] UTF8String, -- eimId of eIM eimFqdn [1] UTF8String OPTIONAL, -- FQDN of eIM eimIdType [2] EimIdType OPTIONAL, counterValue [3] INTEGER OPTIONAL, -- initial counterValue for the eIM associationToken [4] INTEGER OPTIONAL, eimPublicKeyData [5] CHOICE { eimPublicKey SubjectPublicKeyInfo, -- public key of eIM, used for eUICC Package signature verification, where the encoding follows X.509 standard eimCertificate Certificate -- certificate of eIM, used for eUICC Package signature verification, where the encoding follows X.509 standard } OPTIONAL, trustedPublicKeyDataTls [6] CHOICE { trustedEimPkTls SubjectPublicKeyInfo, -- public key of eIM, used for TLS or DTLS, where the encoding follows X.509 standard trustedCertificateTls Certificate -- either the certificate of eIM, used for (D)TLS, or the certificate of the CA, where the encoding follows X.509 standard } OPTIONAL, eimSupportedProtocol [7] EimSupportedProtocol OPTIONAL, euiccCiPKId [8] SubjectKeyIdentifier OPTIONAL -- CI Public Key Identifier supported on the eUICC for signature creation } EimIdType ::= INTEGER { eimIdTypeOid(1), eimIdTypeFqdn(2), eimIdTypeProprietary(3) } EimSupportedProtocol ::= BIT STRING { eimRetrieveHttps(0), eimRetrieveCoaps(1), eimInjectHttps(2), eimInjectCoaps(3), eimProprietary(4) } -- ASN1STOP

2.11.1.1.2 eUICC Package Request Containing eCOsremoved

The eCOs within the eUICC Package request SHALL be encoded in the ASN.1 data object as shown below. -- ASN1START Eco ::= CHOICE { addEim [8] EimConfigurationData, -- for eIM configuration data see 2.11.1 deleteEim [9] SEQUENCE {eimId [0] UTF8String}, updateEim [10] EimConfigurationData, listEim [11] SEQUENCE {} } -- ASN1STOP If the eCO is the addition of an Associated eIM (addEim), then eimId, counterValue and eimPublicKeyData SHALL be provided as part of the EimConfigurationData data object. The trustedPublicKeyDataTls is optional in EimConfigurationData data object. It SHOULD be provided in addEim if the IpaMode in eUICCInfo2 is ipae, and if the eimSupportedProtocol contains eimRetrieveHttps or eimRetrieveCoaps. The eimFqdn is optional for the eIM to provide in EimConfigurationData data object. It SHALL NOT be provided if eimIdTypeFqdn is present in that EimConfigurationData data object, to avoid redundancy with eimId. The eimIdType is optional for the eIM to provide in EimConfigurationData data object. If not provided, the eUICC SHALL assign the value eimIdTypeProprietary before storing the eIM Configuration Data.If the eUICC is requested to calculate an association token for the new Associated eIM, the associationToken data object SHALL be provided with the value set to -1. Otherwise, the data object SHALL NOT be provided. The eimSupportedProtocol is optional for the eIM to provide in EimConfigurationData data object. If not provided, the eUICC SHALL assign the value where only the eimProprietary bit is set before storing the eIM Configuration Data. The euiccCiPKId is optional for the eIM to provide in EimConfigurationData. If not provided, the eUICC SHALL assign the value of first entry of euiccCiPKIdListForSigning in eUICCInfo2 before storing the eIM Configuration Data. If the eCO is the update of the configuration of an Associated eIM (updateEim), then eimId of the target Associated eIM and at least one of either counterValue, eimPublicKeyData, eimIdType, eimFqdn, eimSupportedProtocol or euiccCiPKId SHALL be provided as part of the EimConfigurationData data object. The associationToken data object SHALL NOT be provided. NOTE: It is not possible to update eimId. Updating counterValue to a lower value without also updating eimPublicKeyData SHALL NOT be permitted. If the eCO is the deletion of an Associated eIM (deleteEim), then only the eimId of the target Associated eIM SHALL be provided.

2.11.1.1.3 eUICC Package Request Containing PSMOsremoved

The PSMOs within the eUICC Package request SHALL be encoded in the ASN.1 data object as shown below. -- ASN1START Psmo ::= CHOICE { enable [3] SEQUENCE { iccid [APPLICATION 26] Iccid, rollbackFlag NULL OPTIONAL }, disable [4] SEQUENCE {iccid [APPLICATION 26] Iccid}, delete [5] SEQUENCE {iccid [APPLICATION 26] Iccid}, listProfileInfo [45] ProfileInfoListRequest, -- Tag 'BF2D' getRAT [6] SEQUENCE {}, configureAutoEnable [7] SEQUENCE { autoEnableFlag [0] NULL OPTIONAL, smdpOid [1] OBJECT IDENTIFIER OPTIONAL, smdpAddress [2] UTF8String OPTIONAL } } -- ASN1STOP The iccid indicates the Target Profile at the eUICC as defined in SGP.22 [4]. The rollbackFlag is presented by the eIM within the enable PSMO. The IPA MAY trigger the Rollback Mechanism using the ES10b.ProfileRollback function if the newly enabled Profile fails to provide connectivity. The listProfileInfo SHALL be coded and processed as defined in SGP.22 [4] section 5.7.15. Automatic Profile enabling is activated when autoEnableFlag is present in the configureAutoEnable command and deactivated when autoEnableFlag is not present. The configuration of automatic enabling data (smdpOid and smdpAddress for default SM-DP+) for use in the automatic Profile enabling is possible independently of the whether autoEnableFlag is present or not. At most one enable command SHALL occur in an eUICC Package. At most one disable command SHALL occur in an eUICC Package. A listProfileInfo command SHALL NOT occur after an enable, disable or delete command in an eUICC Package. If this situation occurs the response SHALL indicate the error profileChangeOngoing.

2.11.1.2 IpaEuiccDataRequestmodified

…and/or IPA. It SHALL be encoded as follows: -- ASN1START IpaEuiccDataRequest ::= [82] SEQUENCE { -- Tag BF52 tagList [APPLICATION 28] OCTET STRING, -- Tag '5C' … euiccCiPKIdeuiccCiPKIdentifierToBeUsed SubjectKeyIdentifierOCTET STRING OPTIONAL, -- CI Public Key Identifier (possibly truncated) supported on the eUICC for signature creation searchCriteriasearchCriteriaNotification [1] CHOICE { seqNumber [0] INTEGER, profileManagementOperation [1] NotificationEvent,NotificationEvent euiccPackageResults} OPTIONAL, searchCriteriaEuiccPackageResult [2] NULLCHOICE { seqNumber [0] INTEGER } OPTIONAL, eimTransactionId [3] TransactionId OPTIONAL -- Tag '82' } -- ASN1STOP The eIM MAY request one or more IPA and eUICC data items by listing each tag of a requested item in the tagList of IpaEuiccDataRequest. The following IPA and eUICC data and tags are defined: -List of Notifications tag 'A0'. Default SM-DP+ address (see SGP.22 [4]), tag '80’.'81’. -eUICC Package Results, tag 'A2'. eUICCInfo1 (see section 5.9.2 of this specification), tag 'BF20'. - eUICCInfo2 (see section 5.9.2 of this specification), tag 'BF22'. - Root SM-DS address (see SGP.22 [4]), tag '83'. - Association token (see sections 2.11.1 and 5.9.18 of this specification), tag '84'. - EUM certificate (see SGP.22 [4]), tag 'A5'. - eUICC certificate (see SGP.22 [4]), tag 'A6'. - IPA Capabilities (see section 4.1), tag '88'.'A8'. - Device Information (see SGP.22 [4] section 4.2), tag 'A9'. -Any Listtag ofthat Notificationsis and/orpresent eUICCin Packagethe ResultstagList (seeof sectionIpaEuiccDataRequest, 5.9.11but is not in the list of thistags specification),above, tagis 'BF2B’.ignored without error. In order to select between multiple of EUM certificates and eUICC certificates within the eUICC the eIM MAY provide the CI Public Key Identifier (euiccCiPKId).(euiccCiPKIdentifierToBeUsed). If euiccCiPKIdpresent, the full CI Public Key Identifier (20 bytes) SHALL be sent to an IPA without IPA Capability minimizeEsipaBytes and the CI Public Key Identifier in truncated form SHALL be sent to an IPA with IPA Capability minimizeEsipaBytes (to minimize the number of transmitted bytes). Truncated form means only enough leading bytes of the CI Public Key Identifier are provided for IPA to be able to uniquely locate and extract the chosen CI Public Key Identifier from the euiccCiPKIdListForSigning of eUICCInfo1 / eUICCInfo2. If euiccCiPKIdentifierToBeUsed is not provided, the first entry of euiccCiPKIdListForSigning in eUICCInfo1 / eUICCInfo2 SHALL be used as euiccCiPKIdeuiccCiPKIdentifierToBeUsed when selecting the EUM certificate and/or eUICC certificate to return. The searchCriteriasearchCriteriaNotification and searchCriteriaEuiccPackageResult data object can be used to filter the list of Notifications and/oror eUICC Package Results that SHALL be returned by the IPA according to the following: If tag ‘A0’ is present in the tagList, then o if there is no searchCriteriaNotification the IPA SHALL return the notificationsList as part of the IpaEuiccDataResponse containing all Notifications stored in the eUICC. o if the searchCriteriaNotification is present and specifies seqNumber, and there is a Notification with the given sequence number stored in the eUICC, then the IPA SHALL return the notificationsList as part of the IpaEuiccDataResponse containing the Notification. o if the searchCriteriaNotification is present and specifies profileManagementOperation the IPA SHALL return the notificationsList as part of the IpaEuiccDataResponse containing all the Notifications of the types specified by profileManagementOperation (a bit set to 1 in the profileManagementOperation indicates that the eUICC SHALL return all the Notifications corresponding to this type). If tag ‘A2’ is present in the tagList, then o if there is no searchCriteriaEuiccPackageResult the IPA SHALL return the euiccPackageResults as definedpart of the IpaEuiccDataResponse containing all eUICC Package Results stored in sectionthe 5.9.11.eUICC. o if the searchCriteriaEuiccPackageResult is present and specifies seqNumber, and there is an eUICC Package Result with the given sequence number stored in the eUICC, then the IPA SHALL return the euiccPackageResults as part of the IpaEuiccDataResponse containing the eUICC Package Result. If tag ‘A0’ or tag ‘A2’ are not present, the IPA SHALL ignore searchCriteriaNotification and searchCriteriaEuiccPackageResult respectively. Optionally, eIM MAY provide eIM transaction identifier (eimTransactionId) in order to correlate IpaEuiccDataRequest and IpaEuiccDataResponse. IPA uses the following functions to obtain eUICC data: ES10b.GetEUICCInfo (see section 5.9.2), ES10b.GetCerts (see section 5.9.10), ES10b.GetEID (see section 5.9.19 … mply ignored by IPA when building the IpaEuiccDataResponse structure (see section 2.11.2.2). Depending on IPA Capabilities the IPA SHALL support the following: … - An IPA having IPA Capability eimCtxParams1Generation SHALL support providing deviceInfo to the eIM. - An IPA having IPA Capability minimizeEsipaBytes SHALL support providing euiccInfo1, euiccInfo2, eumCertificate, and euiccCertificate to the eIM.

2.11.1.3 ProfileDownloadTriggerRequestmodified

…1] NULL, contactSmds [2] SEQUENCE { smdsAddress UTF8String OPTIONAL } } -- ASN1STOP The eIM SHALL provide ProfileDownloadTriggerRequest data object as follows. … - If and only if the IPA indicates eimDownloadDataHandling in IPA Capabilities and the eIM requests the IPA to call ESipa.InitiateAuthentication function, an empty data object is provided (i.e., without profileDownloadData). The IPA continues with the indirect Profile download or Event Retrieval procedure. - Otherwise profileDownloadData is provided, containing one of the following: -o activationCode, if the eIM provides an Activation Code. -o contactDefaultSmdp, if the eIM requests the IPA to contact the default SM‑DP+SM-DP+ address that is available in the IoT Device. -o contactSmds, if the eIM requests the IPA to contact the SM‑DSSM-DS address that is available in the IoT Device (smdsAddress is absent) or specified by the eIM (smdsAddress is present). This triggers the retrieval of the SM-DP+ … NAL for the eIM to include in the ProfileDownloadTriggerRequest. It MAY be used for linking a ProfileDownloadTriggerRequest to a ProfileInstallationResult in a … directDirect Profile downloadDownload scenario.procedure, or determine the IoT Device in Indirect Profile Download procedure.

2.11.2 eIM Package Resultmodified

The eIM Package Result contains either: - an EuiccPackageResult, - an EuiccPackageResult concatenated with a RetrieveNotificationsListResponsePendingNotificationList (see SGP.22section [4])2.11.2.2), orIpaEuiccDataResponse, -ProfileDownloadTriggerResult IpaEuiccDataResponseEimPackageResultErrorCode or EimPackageResultResponseError data object.

2.11.2.1 EuiccPackageResultmodified

…ith PSMO or eCO processing result(s) and if there is not enough space, the eUICC SHALL delete one or more of the previously stored signed eUICC Package Results … and Pending Notifications in order of their sequence number, beginning with the lowest. If deleting all signed eUICC Package Results and Pending Notifications is still not enough to store a new signed eUICC Package Result, the eUICC SHALL return the signed eUICC Package Result to the IPA without storing it. The eUICC Package Result SHALL be encoded in the ASN.1 data object as shown below. -- ASN1START EuiccPackageResult ::= [81] CHOICE { -- Tag 'BF51' #SupportedFor … eResultDataSigned, euiccSignEPR [APPLICATION 55] OCTET STRING -- Tag '5F37' } EuiccPackageResultDataSigned ::= SEQUENCE { -- #SupportedForPsmoV1.0.0# eimId [0] … UTF8String,UTF8String (SIZE(1..128)), counterValue [1] INTEGER, transactionId[2]eimTransactionId[2] TransactionId OPTIONAL, seqNumber [3] INTEGER, euiccResult SEQUENCE OF EuiccResultData } EuiccResultData ::= CHOICE { enableResult [3] EnableProfileResult, disableResult [4] DisableProfileResult, deleteResult [5] DeleteProfileResult, listProfileInfoResult [45] ProfileInfoListResponse, getRATResult [6] RulesAuthorisationTable, -- see SGP.22 configureAutoEnableResultconfigureImmediateEnableResult [7] ConfigureAutoEnableResult,ConfigureImmediateEnableResult, addEimResult [8] AddEimResult, deleteEimResult [9] DeleteEimResult, updateEimResult [10] UpdateEimResult, listEimResult [11] ListEimResult, rollbackResult [12] RollbackProfileResult, setFallbackAttributeResult [13] SetFallbackAttributeResult, unsetFallbackAttributeResult [14] UnsetFallbackAttributeResult, processingTerminated INTEGER { resultSizeOverflow(1), unknownOrDamagedCommand(2), interruption(3), undefinedError(127) }}, setDefaultDpAddressResult [101] SetDefaultDpAddressResponse } EuiccPackageErrorSigned ::= SEQUENCE { euiccPackageErrorDataSigned EuiccPackageErrorDataSigned, euiccSignEPE [APPLICATION 55] OCTET STRING -- Tag '5F37' } EuiccPackageErrorDataSigned ::= SEQUENCE { eimId [0] UTF8String,UTF8String (SIZE(1..128)), counterValue [1] INTEGER, transactionIdeimTransactionId [2] TransactionId OPTIONAL, euiccPackageErrorCode EuiccPackageErrorCode } EuiccPackageErrorCode ::= INTEGER { invalidEid(3), replayError(4), counterValueOutOfRange(6), sizeOverflow(15), ecallActive(104), undefinedError(127)} EuiccPackageErrorUnsigned ::= SEQUENCE { eimId [0] UTF8String,UTF8String (SIZE(1..128)), eimTransactionId [2] TransactionId OPTIONAL, associationToken [4] INTEGER OPTIONAL } ConfigureAutoEnableResultConfigureImmediateEnableResult ::= INTEGER { ok(0), insufficientMemory(1), commandError(7), undefinedError(127) } EnableProfileResult ::= INTEGER { ok(0), iccidOrAidNotFound(1), profileNotInDisabledState(2), disallowedByPolicy(3), catBusy(5), rollbackNotAvailable(20), undefinedError(127) } DisableProfileResult ::= INTEGER { ok(0), iccidOrAidNotFound(1), profileNotInEnabledState(2), disallowedByPolicy(3), catBusy(5), undefinedError(127) } DeleteProfileResult ::= INTEGER { ok(0), iccidOrAidNotFound(1), profileNotInDisabledState(2), disallowedByPolicy(3), rollbackNotAvailable(20), returnFallbackProfile(21), undefinedError(127) } ProfileInfoListResponse ::= [45] CHOICE { profileInfoListOk SEQUENCE OF ProfileInfo, -- see SGP.22 profileInfoListError ProfileInfoListError } ProfileInfoListError ::= INTEGER { incorrectInputValues(1), profileChangeOngoing (11), undefinedError(127) } RollbackProfileResult ::= INTEGER { ok(0), undefinedError(127) } SetFallbackAttributeResult ::= INTEGER { ok(0), iccidOrAidNotFound (1), fallbackNotAllowed (2), fallbackProfileEnabled (3), undefinedError (127) } UnsetFallbackAttributeResult ::= INTEGER { ok(0), noFallbackAttribute(2), fallbackProfileEnabled (3), commandError(7), undefinedError (127) } AddEimResult ::= CHOICE { associationToken [4] INTEGER, addEimResultCode INTEGER { ok(0), insufficientMemory(1), associatedEimAlreadyExists(2), ciPKUnknown(3), invalidAssociationToken(5), counterValueOutOfRange(6), commandError(7), undefinedError(127) } } DeleteEimResult ::= INTEGER { ok(0), eimNotFound … nknown(3), counterValueOutOfRange(6), commandError(7), undefinedError(127) } ListEimResult ::= CHOICE { eimIdList SEQUENCE OF EimIdInfo, listEimError INTEGER { … commandError(7), undefinedError(127) } } EimIdInfo ::= SEQUENCE { eimId [0] UTF8String,UTF8String (SIZE(1..128)), eimIdType [4][2] EimIdType OPTIONAL -- present in case of eimIdTypeOid and eimIdTypeFqdn } -- ASN1STOP The eIM transaction identifier (transactionId)(eimTransactionId) is OPTIONAL to use by the eIM in the signed eUICC Package. If it was included in the signed eUICC Package, the eUICC SHALL include the same transactionIdeimTransactionId in the signed eUICC Package Result.Result and also euiccPackageErrorUnsigned and euiccPackageErrorSigned in case of errors. euiccSignEPR and euiccSignEPE SHALL be created using the SK.EUICC.ECDSA and verified using the related PK.EUICC.ECDSA. In case there are more than one SK.EUICC. … d eIM for which the eUICC Package Result is intended) SHALL be used. euiccSignEPR SHALL apply on the concatenated data objects euiccPackageResultDataSigned and … eimSignature.associationToken. euiccSignEPE SHALL apply on the concatenated data objects euiccPackageErrorDataSigned and eimSignature.associationToken. If no associationToken is configured for the eIM, the associationToken data object SHALL be used with the value set to zero for creating the signature. The eIM SHALL use the PK.EUICC.ECDSA from CERT.EUICC.ECDSA to verify the signature euiccSignEPR and euiccSignEPE. The eIM SHALL verify CERT.EUICC.ECDSA. When the Emergency Profile is enabled, the eUICC SHALL reject any EuiccPackageRequest, EuiccMemoryResetRequest, or ExecuteFallbackMechanism with the error codes ecallActive.

2.11.2.2 IpaEuiccDataResponsemodified

The IpaEuiccDataResponse SHALL be encoded as follows: -- ASN1START IpaEuiccDataErrorCode ::= INTEGER { incorrectTagList (1), euiccCiPKIdNotFound(5), ecallActive(104), undefinedError(127) } IpaEuiccDataResponseError ::= SEQUENCE { eimTransactionId [0] TransactionId OPTIONAL, ipaEuiccDataErrorCode IpaEuiccDataErrorCode } IpaEuiccDataResponse ::= [82] CHOICE { -- Tag 'BF52' ipaEuiccData IpaEuiccData, ipaEuiccDataErroripaEuiccDataResponseError INTEGERIpaEuiccDataResponseError {} incorrectTagListPendingNotificationList (1),::= euiccCiPKIdNotFound(5),SEQUENCE undefinedError(127)OF }PendingNotification }EuiccPackageResultList ::= SEQUENCE OF EuiccPackageResult IpaEuiccData ::= SEQUENCE { defaultSmdpAddressnotificationsList [0] PendingNotificationList OPTIONAL, -- Tag 'A0' defaultSmdpAddress [1] UTF8String OPTIONAL, -- Tag '80''81' euiccPackageResultList [2] EuiccPackageResultList OPTIONAL, -- Tag 'A2' euiccInfo1 [32] EUICCInfo1 OPTIONAL, -- Tag 'BF20' euiccInfo2 [34] EUICCInfo2 OPTIONAL, -- Tag 'BF22' rootSmdsAddress [3] UTF8String OPTIONAL, -- Tag '83' associationToken [4] INTEGER OPTIONAL, -- Tag '84' eumCertificate [5] Certificate OPTIONAL, -- Tag 'A5' euiccCertificate [6] Certificate OPTIONAL, -- Tag 'A6' ipaCapabilitieseimTransactionId [8][7] IpaCapabilitiesTransactionId OPTIONAL, -- Tag '88''87' deviceInfoipaCapabilities [9][8] DeviceInfoIpaCapabilities OPTIONAL, -- Tag 'A9''A8' notificationsListdeviceInfo [43][9] RetrieveNotificationsListResponseDeviceInfo OPTIONAL -- Tag 'BF2B'.'A9' } -- ASN1STOP If the associationToken is requested, but no association token is configured for the eIM, the associationToken data object SHALL be absent in the response. An IPA with IPA Capability minimizeEsipaBytes SHOULD include each pending Notification in notificationsList in compact format as described in section 5.14.7. If eimTransactionId was present in the IpaEuiccDataRequest, the IPA SHALL return the same eimTransactionId in the IpaEuiccData or IpaEuiccDataResponseError. If the Emergency Profile is enabled, then the IPA SHALL stop the procedure and return an IpaEuiccDataResponseError containing ipaEuiccDataErrorCode set to ecallActive.

2.11.2.3 ProfileDownloadTriggerResultmodified

…OPTIONAL, profileDownloadTriggerResultData CHOICE { profileInstallationResult [55] ProfileInstallationResult, -- see SGP.22 [4] profileDownloadError SEQUENCE { … profileDownloadErrorReason [0] INTEGER { ecallActive (104), undefinedError(127) }, errorResponse OCTET STRING OPTIONAL } } } -- ASN1STOP The IPA SHALL send ProfileDownloadTriggerResult to inform the eIM about the result of a direct Profile download that was requested by the eIM. - If the eIM provided a transaction identifier (eimTransactionId) in ProfileDownloadTriggerRequest, the IPA SHALL return the same transaction identifier in ProfileDownloadTriggerResult. Otherwise, eimTransactionId SHALL NOT be present. -If the Emergency Profile is enabled, then the IPA SHALL stop the procedure and return an profileDownloadError containing profileDownloadErrorReason set to ecallActive. If the IPA successfully downloaded a Profile and obtained a Profile Installation Result as a response of ES10b.LoadBoundProfilePackage function calls, the IPA SHALL return the Profile Installation Result in profileInstallationResult. Otherwise, the IPA SHALL return a profileDownloadError that MAY include an errorResponse.. -o The errorResponse, if present, SHALL include the error response of an ES10b function or an ES9+ function with ASN.1 binding that the IPA encountered during the… …

3 Proceduresmodified

…ate the case where the IPA is in the Device (IPAd). Such call flows with an IPAe would be identical except that all ES10 calls become internal to the eUICC and … are out of scope of this specification.

3.1.1.1 eIM Package Retrievalmodified

…ation(s)]) EIM -> EIM : [7] Manage eIM Package queue EIM -> IPA : [8] ESipa.ProvideEimPackageResult response (sequence numbers) else Otherwise IPA -> EIM : [9] … ESipa.HandleNotificationsESipa.HandleNotification (eIM Package Result) EIM -> EIM : [10] Manage eIM Package queue EIM -> IPA : [11] OK end end@endumlend [Application@enduml DescriptionFigure automatically5 generated with medium confidence] 5. : eIM Package Retrieval Start Conditions: The IoT Device can trigger the IPA through an internal event (e.g., a timer expiration) without any knowledge about pend … Notification mechanism is out of scope of this document. The IPA has the address (configured or retrieved using GetEimConfigurationData) of the Associated eIM. … The IPA MAY have retrieved from the eUICC the Connectivity Parameters of the currently enabled Profile. The IPAd MAY use ES10b.GetConnectivityParameters. How the IPAe retrieves Connectivity Parameters is implementation specific. Procedure: 1. The eIM and IPA establish a secure connection as defined in section 3.1.2. 2. The IPA calls ESipa.GetEimPackage function including EID. 3. The eI… …

3.1.1.2 eIM Package Injectionmodified

…a.TransferEimPackage (eIM Package) rnote over IPA : [3] [Process the eIM Package] IPA -> EIM : [4] ESipa.TransferEimPackage response (Execution result) @enduml … [C:\Users\gtrujillo\Desktop\eSIMFigure Group\eSIMWG7\eSIMWG7#56\MicrosoftTeams-image.png]6 6. : eIM Package Injection Start Conditions: The eIM and the IPA could be part of a whole system responsible of maintaining the communication between the eIM and the … secure connection as defined in section 3.1.2. NOTE: the hosting system (e.g.: device management system) allows the eIM to retrieve the EID of the IoT Device. … 1.2. The eIM calls ESipa.TransferEimPackage function to the IPA comprising the eIM Package. NOTE: It is implementation specific how this commandpackage is transferred from the eIM to the IPA using the underlying transport protocol. See examples in Annex B. 2.3. The IPA processes the eIM Package. 3.4. The IPA returns the eIM Package Result to the eIM.

3.1.2 Secure Connection Establishmentmodified

… the delivery of Bound Profile Packages. If ESipa is providing the protocol to transport ESipa messages as shown in Figure 7, the following ones are suggested: … - HTTP over TCP with TLS security. NOTE: This could be used by a UICD which is not an NCD. - CoAP over UDP with DTLS security. NOTE: This mode could be used by an NCD. [GraphicalFigure user7 interface Description automatically generated with medium confidence] 7. : ESipa (eIM -- IPA) If the IoT Device has already implemented an interface and protocol with an external entity (e.g., a server) that is used for other functions of the IoT Device as shown in Figure 8, this underlying interface and its protocol can be used to transport ESipa messages. [GraphicalFigure user interface, application Description automatically generated] 8.8 ESipa (eIM -- IPA), using underlying protocol to transport ESipa messages

3.1.2.2 Secure Connection over CoAPmodified

…ation for better reliability. If DTLS 1.2 is used, IPA SHOULD implement both and eIM SHOULD implement at least one of the following session resumption methods: … - The Session Identifiers as defined in RFC 5246 [8], or - The Session Tickets as defined in RFC 5077 [20].

3.2.3.1 Direct Profile Downloadmodified

…ote over IPA : [3] IPA parses the eIM Package and obtains profile \ndownload trigger that contain AC, or SM-DP+ Address and EventID \nor instruction to use the … Defaultdefault SM-DP+ Address end group If option (a) and AC is available to IPA rnote over IPA : [4] IPA parses AC to retrieve SM-DP+ Address, Activation Code Token, [SM-DP+ OID] end rnote over DP, E #FFFFFF [5] - Execution of common mutual authentication procedure as defined in section 3.1.2 of SGP.22 [4]. - If automaticimmediate Profile enabling is activated, the eUICC SHALL verify that the download is coming from the default SM-DP+ configured in the eUICC. If the verification is successful the eUICC SHALL grant automaticimmediate enabling for this Profile. endrnote rnote over DP #FFFFFF [6] - Look for Profile download pending order - Eligibility Check using Device Info, euiccInfo2 endrn … note over DP SM-DP+ SHALL continue the procedure as defined in section 3.1.3.3 of SGP.22 [4] step 8 to 10 endrnote end group opt rnote over IPA #FFFFFF [15] If … optiondefault (c)SM-DP+was was used, the IPA MAY request automaticimmediate Profile enabling (ES10b.EnableUsingDD).(ES10b.ImmediateEnable). - In this case, execute steps (15)(16) and (16).(17). - Otherwise the procedure SHALL stop. endrnote end group opt rnote over E #FFFFFF [16] If automaticimmediate Profile enabling was granted in step (5), the eUICC SHALL enable the Profile and generate enable Notifications as configured. endrnote end rnote over IPA #FFFFFF [17] IPA SHALL retrieve and send any new Notifications generated due to the Profile enabling to Notification Receivers according to section 3.5 of SGP.22 [4]. Endrnote @enduml [DiagramFigure Description9 automatically generated] 9. : Direct Profile Download Start Conditions: In addition to the start conditions required by the Common Mutual Authentication procedure defined in section 3.1.2 of … n Activation Code: The eIM or IPA has an Activation Code that is coded as defined in section 4.1 of SGP.22 [4]. Option (b) use of SM-DS: The eIM or the IPA has … retrievedpreviously been triggered to perform Event Retrieval and has the SM-DP+ Address and EventID from an SM-DS, as an outcome of the procedure defined in sectionsections 3.6.23.9.2.1 ofor SGP.223.9.2.2. [4]. Option (c) use of default SM-DP+: The eIM or the IPA has been triggered to perform the Profile download from the default SM-DP+. The triggered entity (IPA/eIM) knows the default SM-DP+ Address (e.g.:(e.g. by callingIPA having called the function ES10a.GetEuiccConfiguredAddresses).ES10a.GetEuiccConfiguredAddresses or by eIM having sent an eIM Package containing an IpaEuiccDataRequest). NOTE: How the eIM is triggered is out of scope of this version of the specification. How the IPA is triggered could be through received ProfileDownloadTriggerRequest containing contactDefaultSmdp or by IoT Device specific means. The Emergency Profile is not enabled. Procedure: 1. If option (a) is used and the Activation Code is available to the eIM, the eIM parses the Activation Code and finds the SM-DP+ address, Activation Code Token, and optional SM-DP+ OID. If the format of the Activation Code is invalid, the procedure SHALL stop. 2. In case of a Profile download trigger from an eIM Package: a secure connection is established between the IPA and the eIM for the IPA to obtain the eIM Package. How this is triggered is out of scope of this specification. There are two options for the delivery of the eIM Package to the IPA: - The eIM Package Retrieval Procedure defined in section 3.1.1.1 is executed between the IPA and the eIM, or - The eIM Package Injection Procedure defined in section 3.1.1.2 is executed between the IPA and the eIM. 3. The IPA parses the eIM Package received in step 2. The IPA identifies if the eIM Package contains a ProfileDownloadTriggerRequest. If option (a) is used this trigger SHALL contain the Activation Code. If option (b) is used this trigger contains the SM-DP+ Address and EventID.EventID (formatted as an Activation Code). If option (c) is used this trigger contains instruction to use the default SM-DP+ Address. If the format of the trigger profile download eIM Package is invalid, or data needed by IPA to perform the profile download is missing,missing the IPA SHALL return invalidPackageFormat error and the procedure SHALL stop. 4. If option (a) is used, the IPA parses the Activation Code and finds the SM-DP+ Address, Activation Code Token, and optional SM-DP+ OID. If the format of the Activation Code is invalid,invalid the IPA SHALL return invalidPackageFormat error and the procedure SHALL stop. 5. The common mutual authentication procedure defined in section 3.1.2 of SGP.22 [4] SHALL be executed. When this procedure is used for Profile download and instal … SHALL build the ctxParams1 data object to provide the MatchingID, Device Info to the eUICC for signature. The value of the MatchingID SHALL be set as follows: … - If an Activation Code is used (option (a)), the MatchingID value SHALL be set to Activation Code Token. - If an SM-DS is used (option (b)), the MatchingID value SHALL be set to EventID. - If a default SM-DP+ is used (option (c)), the MatchingID SHALL be missing. If automaticimmediate Profile enabling is activated, the eUICC SHALL verify that the download is coming from the default SM-DP+ configured in the eUICC. If the verification is successful, the eUICC SHALL grant automaticimmediate enabling for this Profile. 6. After having successfully authenticated the eUICC at the end of the step (5) above, the SM-DP+ SHALL: - Verify that there is a related pending Profile download order for the provided MatchingID. - If this Profile download order is already linked to an EID, verify that it matches the EID of the authenticated eUICC. - Verify that the Profile corresponding to the pending Profile download order is in 'Released' state, or, in case of a retry due to a previous installation failur … ICCInfo2. These checks SHALL include the check if the eUICC can install one more Profile. See Annex F of SGP.22 [4] for more information on Eligibility checks. … 7. (Optional step) Depending on the agreed behaviour with the Operator (out of scope of this specification), the SM-DP+ SHALL notify the Operator with the outcome … Eligibility check’), the timestamp when this point was reached, and the execution result of this step. NOTE: This notification step MAY be done asynchronously. … 8. If the eligibility check fails, the SM-DP+ SHALL: - set the Profile corresponding with the pending Profile download order in ‘Error’ state (section 3.1.6 of SGP.22 [4]). - return an error status to the IPA and the procedure SHALL stop. Otherwise, the SM-DP+ SHALL: - Determine whether the Profile is already bound to the EID from a previous unsuccessful download attempt. If so, the SM-DP+ MAY include the otPK.Euicc.ECKA obtained in the previous session in the smdpSigned2 data structure. - Determine if a Confirmation Code is required for this pending order. NOTE: How the Confirmation Code is sent to the IoT Device is out of the scope of this specification. - Generate a smdpSigned2 data structure containing the TransactionID and the Confirmation Code Required Flag. - Compute the smdpSignature2 over smdpSigned2 and euiccSignature1 using the SK.DPpb.ECDSA. 9. The SM-DP+ returns the TransactionID, ProfileMetadata, smdpSigned2, smdpSignature2 and CERT.DPpb.ECDSA to the IPA. 10. On reception of the SM-DP+ response, the IPA that SHALL verify the Profile Metadata according to steps 7a, b, c and 8 of section 3.23.1.3 (Profile Download and Installation) of SGP.22 [4]. For thisthese verification,verifications, the IPA MAY use previously fetched Rules Authorisation Table and/or list of installed Profiles. If the IPA has not already fetched the required information, the IPA SHALL request those from the eUICC by calling the ES10b.GetRAT and/or ES10b.GetProfilesInfo functions. If one of the verification fails, the IPA SHALL trigger the cancellation of the on-going RSP session and terminate the procedure. 11. The IPA and eUICC process ES10b.PrepareDownload function call as defined in section 5.7.5 of SGP.22 [4] and the ongoing RSP session SHALL continue with the sub-procedure Profile Download and Installation – Download Confirmation as defined in section 3.1.3.2 of SGP.22 [4].[4] with the following changes: Upon any error returned in the verifications of ES10b.PrepareDownload, the eUICC SHALL terminate the RSP Session. 12. The IPA installs the Profile to the eUICC as defined in section 3.1.3.3 (Sub-procedure Profile Installation) of SGP.22 [4]. If the Profile to be downloaded is an Emergency Profile, i.e. contains the ecallIndication data element set to TRUE within its Profile Metadata, the eUICC SHALL stop the procedure and return incorrectInputValues if either the eUICC does not support the Emergency Mechanism, or the eUICC supports the Emergency Mechanism and already contains an Emergency Profile with ecallIndication set to TRUE. The IPA SHALL then perform the Sub-procedure “Profile Download and installation – Download rejection” as defined in SGP.22[4] with reason code “metadataMismatch”. 13. In case of a Profile download trigger from an eIM Package: the IPA SHALL send the ProfileDownloadTriggerResult to the eIM as defined in section 2.11.2.3 by using the function "ESipa.HandleNotification". NOTE: This step is executed whenever an error is reported between steps 5 and 12. 14. On reception of the "ES9+.HandleNotification" function, the SM-DP+ SHALL proceed as defined in section 3.1.3.3 of SGP.22 [4] step 8 to 10. 15. If optiondefault (c)SM-DP+ was used, the IPA MAY request automaticimmediate Profile enabling by calling ES10b.EnableUsingDD.ES10b.ImmediateEnable. In this case steps (15)(16) and (16)(17) SHALL be executed. Otherwise, the procedure SHALL stop. 16. If automaticimmediate Profile enabling was granted in step (5), the eUICC SHALL enable the Profile and generate enable Notifications as configured. 17. The IPA SHALL retrieve and send any new Notifications generated due to the Profile enabling to Notification Receivers according to section 3.5 of SGP.22 [4].

3.2.3.2 Indirect Profile Downloadmodified

… else eIM-initiated rnote over EIM, IPA : [2b] eIM Package Injection Procedure including secure connection establishment (section 3.1.1.2) end rnote over IPA : … [][3] IPA parses the eIM Package andthat obtainscontains Profile\n \ndownloadProfileDownloadTriggerRequest trigger including e.g. an AC end group If option (a) and AC is available to IPA rnote over IPA : [4] IPA parses AC to retrieve SM-DP+ Address, Activation Code Token, [SM-DP+ OID] end opt Ge … pa.GetBoundProfilePackage request rnote over EIM, DP : [18] ES9+'.GetBoundProfilePackage function EIM -> IPA : [19] ESipa.GetBoundProfilePackage response group … [20] Profile Installation Procedure rnote over IPA, E : [20] Profile Installation group opt rnote over IPA #FFFFFF [21] If default SM-DP+ used, the IPA MAY request immediate Profile enabling (ES10b.ImmediateEnable). Otherwise, continue in step (23). endrnote end group opt rnote over E #FFFFFF [22] If immediate Profile enabling was granted in step (12), the eUICC SHALL enable the Profile and generate enable Notifications as configured. endrnote end rnote over DP, E : [23] Notification Handling IPA -> EIM : [a] ESipa.HandleNotification EIM -> IPA : [b] ACK IPA -> E : [c] ES10b.RemoveNotificationFromList EIM -> DP : [d] ES9+'.HandleNotification end rnote over DP : [21][24] Step 8-10 section 3.1.3.3 of SGP.22 @enduml [PlantUMLFigure diagram]10 10. : Indirect Profile Download and Installation Start Conditions: In addition to the start conditions required by the Common Mutual Authentication procedure defined … trieved the SM-DP+ Address and EventID from the SM-DS, as defined in section 3.9.2.2 of this document. Option (c) use of default SM-DP+: The eIM or the IPA has … has been triggered to perform the Profile download from the default SM-DP+. The triggered entity (IPA/eIM) knows the default SM-DP+ Address.Address (e.g.: by IPA having called the function ES10a.GetEuiccConfiguredAddresses or by eIM having sent an eIM Package containing an IpaEuiccDataRequest). The Emergency Profile is not enabled. IPA indicated in IPA Capability the support of indirectRspServerCommunication. The eIM indicated the support of indirectProfileDownload. Procedure: 1. If option (a) is used and the Activation Code is available to the eIM, the eIM parses the Activation Code and finds the SM-DP+ address, Activation Code Token, and optional SM-DP+ OID. If the format of the Activation Code is invalid, the procedure SHALL stop. 2. In case a Profile download trigger from an eIM Package: a secure connection is established between the IPA and the eIM for IPA to obtain the eIM Package. How this is triggered is out of scope of this specification. There are two options for the delivery of the eIM Package to the IPA: a) The eIM Package Retrieval Procedure steps 1 to 4 as defined in section 3.1.1.1 isare executed between the IPA and the eIM. b) The eIM Package Injection Procedure steps 1 and 2 as defined in section 3.1.1.2 isare executed between the IPA and the eIM. 3. The IPA parses the eIM Package received in step 2. The IPA identifies that the eIM Package contains a ProfileDownloadTriggerRequest. If ProfileDownloadTriggerRequest data object is empty (i.e., without profileDownloadData), then the Procedure continues in step 5. If option (a) is used this trigger MAY contain the Activation Code. Alternatively, the eIM handles the AC (see IPA Capability eimDownloadDataHandling). If option ( … use the default SM-DP+ Address. If the format of the trigger profile download eIM Package is invalid, or data needed by IPA to perform the profile download is … missing,missing the IPA SHALL return invalidPackageFormat error and the procedure SHALL stop. 4. If the IPA retrieved an Activation Code in step 3, or if IPA retrieved an Activation Code by some other means outside of this specification before the start of this procedure, the IPA parses the Activation Code and finds the SM-DP+ address, Activation Code Token, and optional SM-DP+ OID. If the format of the Activation Code is invalid,invalid the IPA SHALL return invalidPackageFormat error and the procedure SHALL stop. 5. If euiccInfo1 is not yet retrieved by the eIM or IPA, the IPA MAY request euiccInfo1 from the eUICC by calling ES10b.GetEuiccInfo (see section 5.9.2). 6. The IPA requests an eUICC Challenge from the eUICC by calling the ES10.GetEUICCChallenge function (see section 5.9.3). 7. A secure connection is established between the IPA and the eIM if it is not yet established. 8. The IPA calls ESipa.InitiateAuthentication function comprising eUICC Challenge, optionally SM-DP+ FQDN, and optionally euiccInfo1(see IPA Capability minimizeEsipaBytes).minimizeEsipaBytes) and eimTransactionId (if included by eIM in ProfileDownloadTriggerRequest). If the IPA does not provide SM-DP+ FQDN or euiccInfo1, the eIM SHALL identify the relevant information. 9. The eIM establishes an HTTPS connection with the SM-DP+ in server authentication mode according to SGP.22 [4]. 10. The eIM and the SM-DP+ process ES9+'.InitiateAuthentication function comprising eUICC Challenge, SM-DP+ FQDN, and euiccInfo1 as defined in section 5.6.1 of SGP. … e eIM SHALL check that the SM-DP+ OID from the AC matches the SM-DP+ OID of the SM-DP+ Certificate (serverCertificate). If not, the procedure SHALL be stopped. … 11. The eIM sends the ESipa.InitiateAuthentication response to the IPA, based on the ES9+'.InitiateAuthentication response from the SM-DP+. The eIM SHALL additionally provide ctxParams1 as defined in SGP.22 [4] if the IPA does not generate it (see IPA capability eimCtxParams1Generation). 12. The IPA and eUICC process ES10b.AuthenticateServer function call as defined in section 5.7.13 of SGP.22 [4]. If immediate Profile enabling is activated, the eUICC SHALL verify that the download is coming from the default SM-DP+ configured in the eUICC. If the verification is successful, the eUICC SHALL grant immediate enabling for this Profile. 13. The IPA calls ESipa.AuthenticateClient function comprising euiccSigned1 or compactEuiccSigned1, euiccSignature1, optionally CERT.EUM.ECDSA, and optionally CERT. … he compactEuiccSigned1 instead of euiccSigned1 (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify the relevant information and build euiccSigned1. … 14. The eIM and SM-DP+ process the ES9+'.AuthenticateClient function as defined in 5.6.3 of SGP.22 [4]. 15. The eIM sends the ESipa.AuthenticateClient response to the IPA, based on the ES9+'.AuthenticateClient response from the SM-DP+. If the response returns an error, IPA SHALL trigger the cancellation of the on-going RSP session (see section 3.2.3.3) with reason sessionAbortedundefinedReason and the procedure SHALL stop. - If the IPA is capable of verifying the Profile Metadata, the eIM SHALL provide the Profile Metadata to IPA that SHALL verify the Profile Metadata according to section 3.1.33.2.3.1 (Profile(Direct DownloadProfile andDownload) Installation)step of10. SGP.22 [4]. For this verification, the IPA MAY use previously fetched Rules Authorisation Table and/or list of installed Profiles. If the IPA has not already fetched the re … ose from the eUICC by calling the ES10b.GetRAT and/or ES10b.GetProfilesInfo functions. If the verification fails, the IPA SHALL trigger the cancellation of the … on-goingon- going RSP session (see section 3.2.3.3) and terminate the procedure.procedure -SHALL stop. If the IPA is not capable of verifying the Profile Metadata (see IPA Capability eimProfileMetadataVerification) according to section 3.1.33.1..3 (Profile Download and Installation) of SGP.22 [4], the eIM SHALL verify the Profile Metadata according to steps 7a, b, c and 8 of section 3.1.3 (Profile Download and Installation) of SGP.22 [4] and SHALL NOT provide the Profile Metadata to IPA. For this verification, the eIM SHALL use Rules Authorisation Table and information on installed Profiles available to the eIM, e.g., obtained prior to the start of this procedure using the PSMOs getRAT and listProfileInfo. If the verification fails, the eIM SHALL return an error code to IPA and terminate the procedure.procedure SHALL stop. The error code triggers IPA to cancel the on-going RSP session with SM-DP+ according to section 3.2.3.3. The cancel session reason (pprNotAllowed) to be used by IPA when calling the ESipa.CancelSession is given by the error code. 16. The IPA and eUICC process ES10b.PrepareDownload function call as defined in section 5.7.5 of SGP.22 [4].[4] with the following change: Upon any error returned in the verifications of ES10b.PrepareDownload, the procedure SHALL stop and the eUICC SHALL terminate the RSP Session 17. The IPA calls ESipa.GetBoundProfilePackage function comprising euiccSignature2 and either euiccSigned2 or compactEuiccSigned2. If compactEuiccSigned2 is provided (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify the relevant information and build euiccSigned2. 18. The eIM and SM-DP+ process ES9+'.GetBoundProfilePackage function as defined in section 5.6.2 of SGP.22 [4]. NOTE: In the ES9+'.GetBoundProfilePackage function request, the eIM forwards the ESipa.GetBoundProfilePackage function request. 19. The eIM sends the ESipa.GetBoundProfilePackage response to the IPA, based on the ES9+'.GetBoundProfilePackage response from the SM-DP+. If the eIM or IPA previo … cation), the eIM SHALL return an error code that triggers IPA to cancel the session and also indicates the cancel session reason (metadataMismatch) to be used. … 20. The IPA installs the Profile to the eUICC as defined in section 3.1.3.3 (Sub-procedure Profile Installation) of SGP.22 [4]. In case of errors during the installation of the Profile the cancel session procedure in section 3.2.3.3 is triggered with cancel session reason loadBppExecutionError and the procedure SHALL stop. If the Profile to be downloaded is an Emergency Profile, i.e. contains the ecallIndication data element set to TRUE within its Profile Metadata, the eUICC SHALL stop the procedure and return incorrectInputValues if either the eUICC does not support the Emergency Mechanism, or the eUICC supports the Emergency Mechanism and already contains an Emergency Profile with ecallIndication set to TRUE. The IPA SHALL then perform the Sub-procedure “Profile Download and installation – Download rejection” as defined in SGP.22[4] with reason code “metadataMismatch”. 21. If default SM-DP+ was used, the IPA MAY request immediate Profile enabling by calling ES10b.ImmediateEnable and the procedure SHALL continue with step (22). Otherwise, the procedure SHALL continue in step (23). 22. If immediate Profile enabling was granted in step (12), the eUICC SHALL enable the Profile and generate enable Notifications as configured. 23. The following changes are made to the Notification procedure compared to section 3.1.3.3 of SGP.22 [4]: a) The IPA calls ESipa.HandleNotification function comprising ProfileInstallationResult.PendingNotification data object that contains ProfileInstallationResult that contains the TransactionID generated by the SM-DP+. If a compact version of the ProfileInstallationResult is provided (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify the relevant information and b … tes the ProfileInstallationResult from its memory. d) The eIM and SM-DP+ process ES9+’.HandleNotification function as defined in section 5.7.4 of this document. … 24. On reception of the ES9+’.HandleNotification function, the SM-DP+ SHALL proceed as defined in section 3.1.3.3 of SGP.22 [4] step 8 to 10.

3.2.3.3 Cancel Session Procedure for Indirect Profile Downloadmodified

This section describes the cancel session call flow used to cancel an indirect Profile download session. This procedure can occur due to an error at the following steps of the protocol: - after the response to "ESipa.AuthenticateClient" - after the response to "ESipa.GetBoundProfilePackage" @startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam s … pute euiccCancelSessionSignature over euiccCancelSessionSigned endrnote E --> IPA : [3] cancelSessionResponseOk rnote over IPA [Stop procedure if the reason is … sessionAborted]undefinedReason] endrnote IPA -> eIM : [4] ESipa.CancelSession(TransactionID, cancelSessionResponseOk) eIM -> DP : [4] ES9+’.CancelSession(TransactionID, cancelSessionResponseO … -> eIM : [ERROR] eIM --> IPA : [ERROR] rnote over DP [6] Process the reason according to SGP.22 [4] endrnote DP --> eIM : [10] OK eIM --> IPA : [10] OK @enduml … [DiagramFigure Description11 automatically generated] 11. Cancel Session Procedure Start Conditions: This procedure can be used in the following cases. Reasons in the response to "ESipa.AuthenticateClient": - The IPAd receives “pprNotAllowed” error in the response to "ESipa.AuthenticateClient" due to that eIM, when verifying the Profile Metadata, discovered that the … present in the Profile Metadata and an Operational Profile is already installed on the eUICC. In this case the reason code for step (1) SHALL be pprNotAllowed. … - The IPAd receives any other error in the response to "ESipa.AuthenticateClient". In this case the reason for step (1) SHALL be sessionAborted.undefinedReason. Cancel reasons after "ESipa.AuthenticateClient" related to Profile download: - The IPAd verifies Profile Metadata and discovers that the PPR(s) in the Profile Metadata are not allowed according to the Rules Authorisation Table, or PPR1 is … already installed on the eUICC. In these cases, the reason code for step (1) SHALL be pprNotAllowed. Reasons in the response to "ESipa.GetBoundProfilePackage": … - The IPAd receives “profileMetadataMismatch”metadataMismatch error in the response to "ESipa.GetBoundProfilePackage" due to that eIM discovered that the Profile Metadata in the Bound Profile Package does not match the Pr … sponse to "ES9+’.AuthenticateClient". In this case the reason code for step (1) SHALL be metadataMismatch. Cancel reasons after "ESipa.GetBoundProfilePackage": … - The IPAd discovers that the Profile Metadata in the Bound Profile Package does not match the Profile Metadata received previously in the response to "ESipa.AuthenticateClient". In this case the reason for step (1) SHALL be metadataMismatch. - The IPAd has encountered an error while installing a Bound Profile Package. In this case the reason for step (1) SHALL be loadBppExecutionError. Procedure: 1. The IPAd SHALL call the "ES10b.CancelSession" function with input data comprising the TransactionID and the reason. 2. The eUICC SHALL: - Generate the euiccCancelSessionSigned data object containing the TransactionID and the reason provided by the IPAd. - Compute the euiccCancelSessionSignature over euiccCancelSessionSigned using the SK.EUICC.ECDSA corresponding to the euiccCiPKIdToBeUsedeuiccCiPKIdentifierToBeUsed as received during the common mutual authentication procedure. 3. The eUICC SHALL return the euiccCancelSessionSigned and euiccCancelSessionSignature. If the reason is sessionAborted,undefinedReason, the IPAd SHALL ignore the response from the eUICC and stop the procedure. 4. The IPAd SHALL call the "ESipa.CancelSession" function with input data comprising … all the "ES9+’.CancelSession" function with the input data from "ESipa.CancelSession". 5. On reception of the "ES9+’.CancelSession" function, the SM-DP+ SHALL: … - Retrieve the on-going RSP session identified by the TransactionID. If the TransactionID is unknown, the SM-DP+ SHALL return a function execution status 'Failed' with relevant status code and the procedure SHALL stop. - Verify the euiccCancelSessionSignature performed over euiccCancelSessionSigned using the PK.EUICC.ECDSA associated with the ongoing RSP session. If the signature is invalid, the SM-DP+ SHALL return a function execution status 'Failed' with relevant status code and the procedure SHALL stop. - Verify that the received OID is the same value as the one contained in the CERT.DPauth.ECDSA used during the common mutual authentication procedure. If the val… …

3.3.1 Generic eUICC Package Download and Executionmodified

…d" as IPA participant "<b>eUICC" as E participant "<b>Device Baseband" as DevBB rnote left IPA [1] - Build euiccPackageSigned = {eimId, eidValue, counterValue, … [transactionId],[eimTransactionId], euiccPackage} and compute eimSignature over euiccPackageSigned - Build eIMPackage endrnote rnote over eIM, IPA: [2] Transfer eIM Package containing signed \n e … ackage rnote over E [5] Execute PSMO/eCO endrnote end rnote over E: [6] Generate and sign the result of the eUICC Package \nincluding eUICC sequence number end … E -> IPA : [7] Signed eUICC Package Result opt IfAny enablemarked Profile opt "to be disabled", "to be disabled and deleted", or disable"to PSMObe enabled" E -> DevBB: [7a][8a] REFRESH DevBB -> E: Terminal Response or RESET End opt rnote over E [7b][8b] The marked Profile(s) are enabledenabled, disabled and/or disableddeleted endrnote rnote over DevBB [Network attach procedure with the newly enabled Profile] end rnote end opt E -> IPA : [8] Signed eUICC Package Result group If the IPAd sends eUICC Package Result and Notifications to the eIM in a single eIM Package Result IPA -> E : [9] ES10b.RetrieveNotificationsList E -> IPA … ES9+.HandleNotification or ESipa.HandleNotification rnote over DP, E #FFFFFF : [Refer to procedure Notification Delivery to Notification Receivers] end @enduml … [PlantUMLFigure diagram]12 12. : Generic eUICC Package Download and Execution Start Condition: This procedure requires the following start conditions: - The eUICC is associated with the eIM and has the eIM public key and eIM ID. - The eIM has received a request to perform a PSMO/eCO for the particular eUICC and has the EID of the eUICC in its storage along with the current value of the counter for replay protection as well as the relevant information of the target Profile in the eUICC. - A Secure Connection between the eIM and the IPA is established. Procedure: 1. The eIM SHALL prepare the eUICC Package structure including signing the eUICC Pack … rent value of the counter for replay protection in eIM storage is updated accordingly. The eIM then builds the eIM Package containing the signed eUICC Package. … TransactionId,eimTransactionId, if included, MAY be used for linking an eUICC Package with an eUICC Package Result. 2. The eIM SHALL transfer the eIM Package (containing the signed eUICC Pack … l the end is reached or an error is encountered for a PSMO/eCO. If an interruption (e.g. power loss) occurs during the processing of the ES10b.LoadEuiccPackage … command,function, the eUICC SHALL restore its original state prior to execution, see details in section 5.9.1. 6. The eUICC SHALL generate the result of the eUICC Package execut … r is incremented by 1 within the eUICC. The eUICC SHALL update the stored counter value to the counter value of the signed eUICC Package received in step 4. 7. … IfThe IPAd obtains the signed eUICC Package containedResult anfrom enablethe and/oreUICC. disable8. PSMOs:any Profile is marked as "to be disabled", "to be disabled and deleted", "to be enabled", or "to be deleted" a. If any Profile is marked as "to be disabled", "to be disabled and deleted", or "to be enabled", the eUICC SHALL send the REFRESH command in "eUICC Profile State Change" mode (if supported by the Device) or "UICC Reset" mode to the Device, according to ETSI TS 102 223 [5], to prepare the IoT Device for a change in Profile state. NOTE: Enabling or disabling via PSMO always uses REFRESH. b. Upon reception of the Terminal Response or after the RESET, or in case the ISD-RREFRESH SHALL:command i.is Disablenot sent, the profileISD-R (ifSHALL: any)If a Profile is marked "to be disabled"disabled": ordisable the marked Profile. If a Profile is marked "to be disabled and deleted".deleted": ii.disable Enable the profilemarked (ifProfile any)and then delete it. If a Profile is marked "to be enabled".enabled": Ifenable the eUICCmarked PackageProfile. containedIf onea orProfile severalis deletemarked PSMO,"to be deleted": delete the ISD-Rmarked SHALLProfile. deleteIf any marked Profile markedis "tosuccessfully beenabled, deleted"disabled, (oror "todeleted bein disabledthe andprevious deleted").steps, 8.generate Theas IPAdmany obtainsNotifications as configured in each Profile Metadata (notificationConfigurationInfo) in the signedformat eUICCof PackageOtherSignedNotification. ResultUnmark fromall marked Profiles. If a Profile is now in Enabled state, the eUICC.IoT Device baseband executes the network attach procedure. 9. If the IPAd sends eUICC Package Result and Notifications to the eIM in a single eIM Package Result and if the eUICC Package contains PSMO(s), the IPAd SHALL … e Result (using ESipa.ProvideEimPackageResult), the IPAd SHALL, in case of a non-empty list of pending Notifications, include the list of pending Notifications … (RetrieveNotificationsListResponse(PendingNotificationList as defined in SGP.22section [4])2.11.2.2) together with the signed eUICC Package Result in the eIM Package Result. In case of an IPAd with IPA Capability minimizeEsipaBytes, the IPAd SHOULD include each pending Notification in the list in compact format as described in section 5.14.7. If the IPAd does not send Notifications together with the eUICC Package Result, the IPAd MAY use ESipa.HandleNotificationsESipa.HandleNotification instead to send the eUICC Package Result to the eIM. If the IPAd fails sending the eIM Package Result to the eIM due to a lack of connectivity, it SHOULD apply the Profile Rollback procedure described below. 1.11. The eIM SHALL extract the eUICC Package Result and verify the eUICC signature of the signed eUICC Package Result using the public key PK.EUICC.ECDSA of the eUI … p 13 to acknowledge the received Notifications (but not the eUICC Package Result) and sends the received Notifications to Notification Receivers (see step 14). … 2.12. The eIM SHALL process the result of the eUICC Package execution. 3.13. If the eIM Package Result was transmitted using the ESipa.ProvideEimPackageResult function (resp. the response to ESipa.TransferEimPackage), then the eIM SHALL … re successfully processed by sending their sequence numbers in the response to ESipa.ProvideEimPackageResult (resp. the next call to ESipa.TransferEimPackage). … 11.14. If the If the eIM Package Result was transmitted using ESipa.HandleNotifications,ESipa.HandleNotification, then the eIM does not acknowledge the signed eUICC Package Result and received Notifications (if any). In case the eIM received pending Notifications in step 1 … ytes), the eIM SHALL identify the relevant information and build the full pending Notification before forwarding the Notification to the Notification Receiver. … 12.15. IPAd SHALL call ES10b.RemoveNotificationFromList (see SGP.22 [4]) one or more times to delete the eUICC Package Result and pending Notifications for which acknowledgement has been received. The eUICC Package Result and each pending Notification to be deleted are identified by the sequence number(s) received in step 13. 13.16. The eUICC SHALL delete the eUICC Package Result or pending Notification from its memory. 14.17. If IPAd sends Notifications using ES9+.HandleNotification or ESipa.HandleNotification, the IPAd SHALL continue execution according to procedure “Notification Delivery to Notification Receivers.” ProfileNOTE: RollbackNotifications Procedure:(if Ifany) theneeds IPAd fails sending the eIM Package Result to thebe eIM due to a lack of connectivity, it SHOULD call the ES10b.ProfileRollback function (see section 5.9.16) to request the eUICC to roll back to the previously Enabled Profile (if any). If the result of ES10b.ProfileRollback indicates successful processing (the eUICC returns 'ok'), then a new eUICC Package Result is available, and the IPAd SHALL: - Discard the previous eIM Package Result, i.e., the IPAd SHALL NOT send during this eIMprocedure Package Result to the eIM and SHALL call ES10b.RemoveNotificationFromList (see SGP.22 [4]) to delete the related eUICC Package Result. - The IPAd SHALL build a new eIM Package Result including the new eUICC Package Result returned by theone ES10b.ProfileRollback command and try to send this new eIM Package Result to the eIM. NOTE: As Profiles have returned to their states prior to the processing of thedescribed eUICCmeans Package(either Request,together aswith an optimization, the IPA may inquire which Notifications (if any) were generated by the processing of the eUICC Package RequestResults andin ES10b.ProfileRollbackstep command10, andor decideusing toES9+.HandleNotification discardor suchESipa.HandleNotification Notificationsin withoutstep sending them to the eIM.17).

3.3.2 Profile Rollback Procedureadded

If the IPAd fails sending the eIM Package Result to the eIM due to a lack of connectivity, it SHOULD call the ES10b.ProfileRollback function (see section 5.9.16) to request the eUICC to roll back to the previously Enabled Profile (if any). If the result of ES10b.ProfileRollback indicates successful processing (the eUICC returns 'ok'), then a new eUICC Package Result is available, and: • The IPAd SHALL discard the previous eIM Package Result, i.e., the IPAd SHALL NOT send the previous eIM Package Result to the eIM. • The IPAd SHALL build a new eIM Package Result including the new eUICC Package Result returned by the ES10b.ProfileRollback function and try to send this new eIM Package Result to the eIM. NOTE1: When the ES10b.ProfileRollback is successful, the eUICC automatically discards the previous eUICC Package Result (see section 5.9.16) and there is no need for the IPAd to remove it from the eUICC. In particular, the ES10b.RemoveNotificationFromList function would return nothingToDelete(1) if the IPAd tried to do so. NOTE2: As Profiles have returned to their states prior to the processing of the eUICC Package Request, as an optimization, the eUICC may discard Notifications (if any) generated by the processing of the eUICC Package Request and ES10b.ProfileRollback.

3.4.1 Enable Profilemodified

…C\n<b>IPA Services (ISD-R)" as IPAServices rnote over IPAServices [1] Profile identification [2] Verify Profile state End rnote rnote over IPAServices [3] Mark … Targettarget Profile "to be enabled" and, if granted, record "usage of Rollback Mechanism is allowed" endrnote rnote over IPAServices [4] Generate Enable PSMO execution result data structure (enableResult) and continue as described in 3.3.1 endrnote @enduml [GraphicalFigure user13 interface, application, table Description automatically generated] 13. : Enable Profile Start Conditions: A Profile is already downloaded and installed in the eUICC. A eUICC Package containing an 'Enable Profile' is received within a … d in 3.3.1 Generic eUICC Package Download and Execution. Procedure: If an Enable command has already been processed in this eUICC Package, then the ISD-R SHALL … stopindicate thea procedurefailure within athe PSMO execution result indicatingand aprocedure failure.SHALL continue in step 4. 1. The ISD-R SHALL find the Targettarget Profile with the ICCID. If the Targettarget Profile is not found, the ISD-R SHALL stopindicate a failure in the PSMO execution result with iccidOrAidNotFound(1) error code and procedure SHALL continue in step 4. If the target Profile is the Emergency Profile with ecallIndication set to TRUE, the ISD-R SHALL indicate a failure in the PSMO execution result indicatingwith aundefinedError failure.(127) error code and procedure SHALL continue in step 4. 2. The ISD-R SHALL verify the state of the Targettarget Profile and, if usage of the Rollback Mechanism is granted, whether a Profile is currently enabled (or marked as "to be disabled"). If the Targettarget Profile is not in Disabled state, or if usage of the Rollback Mechanism is granted and there is no currently Enabled Profile (or no Profile marked as "to be disabled"), then the ISD-R SHALL stopindicate a failure in the procedurePSMO execution result respectively with aprofileNotInDisabledState(2) resultor indicatingrollbackNotAvailable(20) aerror failure.codes and procedure SHALL continue in step 4. 3. The eUICCISD-R SHALL mark the target Profile “to be enabled” and the currently Enabled Profile (if any) "to be disabled” and SHALL record whether usage of the Rollback Mechanism is granted (together with a reference to the Profile (if any) which is to be disabled). If the target Profile is a Fallback Profile, the ISD-R SHALL record information on the currently Enabled Profile. NOTE1: This recorded information is used when ES10b.ReturnFromFallback is executed. NOTE2: If the currently enabled Profile is a Fallback Profile it is also marked as “to be disabled”. 4. The eUICC SHALL generate the PSMO execution result data structure indicating the result of the PSMO 'Enable Profile’, and the procedure continues as described in section 3.3.1. End Conditions: The Targettarget Profile is marked “to be enabled” and the currently Enabled Profile (if any) is marked "to be disabled". If granted, the authorisation to use the Rollback Mech… …

3.4.2 Disable Profilemodified

…tbox participant "<b>eUICC\n<b>IPA Services (ISD-R)" as IPAServices rnote over IPAServices [1] Profile identification [2] Verify Profile state [3] Mark profile … Targettarget profileProfile as ‘to be disabled’ End rnote rnote over IPAServices [4] Generate Disable PSMO execution result data structure (disableResult) endrnote @enduml [PlantUMLFigure diagram]14 14. : Disable Profile Start Conditions: A Profile is already downloaded and installed in the eUICC. A eUICC Package containing a 'Disable Profile' is received within … neric eUICC Package Download and Execution. Procedure: If a Disable or an Enable command has already been processed in this eUICC Package, then the ISD-R SHALL … stopindicate thea procedurefailure within athe PSMO execution result indicatingand aprocedure failure.SHALL continue in step 4. 1. The ISD-R SHALL find the Targettarget Profile with the ICCID. If the Targettarget Profile is not found, the ISD-R SHALL stopindicate thea procedurefailure within athe PSMO execution result indicatingand aprocedure failure.SHALL continue in step 4. 2. The ISD-R SHALL verify the state of the Targettarget Profile. If the Targettarget Profile is not in Enabled state, the ISD-R SHALL stopindicate thea procedurefailure within athe PSMO execution result indicatingand aprocedure failure.SHALL continue in step 4. 3. The eUICC SHALL mark the Targettarget Profile “to be disabled”. 4. The eUICC SHALL generate the PSMO execution result data structure indicating the result of the PSMO 'Disable Profile’, and the procedure continues as described in section 3.3.1. End Conditions: The Targettarget Profile is marked “to be disabled”. The signed eUICC Package execution result data structure containing the result of disabled Profile is stored in the eUICC. … …

3.4.3 Delete Profilemodified

…within a eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution, used to delete a Profile already downloaded and installed on an eUICC. … The conditions under which a Provisioning Profile could be deleted are implementation- dependent and out of the scope of this specification. The eUICC implementation MAY not support deletion of a Provisioning Profile or a preloaded Test Profile. An eUICC Package SHALL NOT include an Enable command with granted usage of the Rollback Mechanism and a Delete command, where the Delete command would try to de … x participant "<b>eUICC\n<b>IPA Services (ISD-R)" as IPAServices rnote over IPAServices [1] Profile identification [2] Verify the profile state of the targeted … profileProfile endrnote alt If the Targettarget Profile is in Disabled state\n and is not marked “to be enabled” rnote over IPAServices [2.a] eUICC shall deletemark "to be deleted" the Targettarget Profile endrnote else If the Targettarget Profile is in Enabled state and marked “to be disabled”: rnote over IPAServices [2.b] eUICC shall re-mark the Targettarget Profile “to be disabled and deleted”. endrnote else If the Targettarget Profile is in Enabled state and is not marked “to be disabled”disabled”\n or the target Profile is in Disabled state and is marked "to be enabled" rnote over IPAServices [2.c] the ISD-R SHALL indicate a failure in the PSMO execution result.result with 'profileNotInDisabledState' code. endrnote else If the target Profile is in Disabled state (or marked "to be disabled") but is currently referenced by the Rollback Mechanism rnote over IPAServices [2.d] the ISD-R SHALL indicate a failure in the PSMO execution result with 'rollbackNotAvailable' code. Endrnote else If the target Profile is Disabled (or marked "to be disabled") but is currently referenced by the Fallback Mechanism rnote over IPAServices [2.e] the ISD-R SHALL indicate a failure in the PSMO execution result with 'returnFallbackProfile' code. endrnote end rnote over IPAServices [3] The eUICC SHALL generate the PSMO execution result data structure state result of the PSMO 'Delete Profile' as described in section 3.3.1 endrnote @enduml [GeneratedFigure by15 PlantUML] 15. : Delete Profile Start Conditions: A Profile is already downloaded and installed in the eUICC. An eUICC Package containing a 'Delete‘Delete Profile'Profile’ is received within an "ES10b.LoadEuiccPackage" by the eUICC as described in 3.3.1 Generic eUICC Package Download and Execution. The eIM signature the EID, and replay counter are verified as defined in 3.3.1 Generic eUICC Package Download and Execution. Procedure: 1. The ISD-R SHALL find the Targettarget Profile with the ICCID. If the Targettarget Profile is not found, then the ISD-R SHALL stop the procedure with a result indicating a failure.failure with error code: iccidOrAidNotFound(1). 2. The ISD-R SHALL verify the state of the Targettarget Profile. a. If the Targettarget Profile is either in Disabled state and is not marked “to be enabled”, or, then the eUICC SHALL mark the target Profile “to be deleted”. b. If the target Profile is in Enabled state and marked "to be disabled" and is not currently referenced by the Rollback Mechanism (see Enable command), then the eUICC SHALL deletemark the Targettarget Profile.Profile b.“to be disabled and deleted”. c. If the Targettarget Profile is in Enabled state and is not marked “to be disabled”disabled”, thenor the eUICCtarget SHALLProfile re-markis thein TargetDisabled Profilestate “toand beis disabledmarked and"to deleted”.be c.enabled", Ifthen the TargetISD-R ProfileSHALL isindicate a failure in Enabledthe statePSMO andexecution isresult notwith markedprofileNotInDisabledState(2) “toerror becode. disabled”d. orIf the target Profile is in Disabled state (or marked "to be disabled") but is currently referenced by the Rollback Mechanism (see Enable command), then the ISD-R SHALL indicate a failure in the PSMO execution result.result with rollbackNotAvailable(20) error code. NOTE: The ISD-R does not check if the target Profile is a Fallback Profile, i.e. it is allowed to delete a Fallback Profile. e. If the Fallback Profile is enabled and if the target Profile is the Profile that was disabled using the ES10b.ExecuteFallbackMechanism function (i.e. is currently referenced by the Fallback Mechanism), the ISD-R SHALL indicate a failure in the PSMO execution result with returnFallbackProfile (21) error code. 3. The eUICC SHALL generate the PSMO execution result data structure indicating the result of the PSMO 'Delete Profile' as described in section 3.3.1. End Conditions: The Targettarget Profile is either deleted,marked as “to be deleted”, marked “to be disabled and deleted” or remains in “enabled” state and a failure is indicated in the signed eUICC Package execution result. NOTE: If the Targettarget Profile is deleted, all the associated data of this Profile is deleted. The signed eUICC Package execution result data structure containing the result of Delete Profile is stored in the eUICC.

3.4.4 Configure by eIM of Immediate Profile Enablingmodified was Configure Automatic Profile Enabling by eIM

This procedure defines the execution of a configureAutoEnableconfigureImmediateEnable command contained within an eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution, used to activate or deactivate automaticimmediate Profile enabling in the eUICC and to add or update automaticdefault enablingSM-DP+ data used in the automaticimmediate Profile enablingenabling. using default SM-DP+. @startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox participant "<b>eUICC\n<b>IPA Services (ISD-R)" as IPAServices rnote over IPAServices [1] Activate/deactivate automaticimmediate Profile enabling endrnote rnote over IPAServices [2] Store automaticdefault enablingSM-DP+ data (defaultSmdpOid and defaultSmdpAddress) if present in the command endrnote rnote over IPAServices [3] Generate configureAutoEnableconfigureImmediateEnable PSMO execution result data structure (configureAutoEnableResult)(configureImmediateEnableResult) endrnote @enduml [TableFigure Description16 automaticallyConfiguration generated]by 16.eIM :of ConfigureImmediate Automatic Profile Enabling by eIM Start Conditions: An eUICC Package containing a 'configureAutoEnable''configureImmediateEnable' command was received within an "ES10b.LoadEuiccPackage" by the eUICC. The eIM signature, the EID, and replay counter has been verified (see 3.3.1 Generic eUICC Package Download and Execution). Procedure: 1. If autoEnableFlagimmediateEnableFlag is present and automaticimmediate Profile enabling is not activated, the ISD-R SHALL activate automaticimmediate Profile enabling. If autoEnableFlagimmediateEnableFlag is not present and automaticimmediate Profile enabling is activated, the ISD-R SHALL deactivate automaticimmediate Profile enabling. In all other cases, the automaticimmediate Profile enabling state is left unchanged. 2. If present, the ISD-R SHALL store automaticdefault enablingSM-DP+ data (smdpOid(defaultSmdpOid andand/or smdpAddressdefaultSmdpAddress) for default SM-DP+) for use in the automaticimmediate Profile enabling. NOTE: if defaultSmdpAddress is stored here, then it is also used as the default SM-DP+ address in the response that is provided by the GetEuiccConfiguredAddresses function (described in 5.8.1 of this specification). 3. The eUICC SHALL generate the PSMO execution result data structure indicating the result of the PSMO 'Configure‘Configure AutomaticImmediate Profile Enabling'Enabling’ and the procedure continues as described in section 3.3.1.

3.4.5 Configure by IPA of Immediate Profile Enablingmodified was Configure Automatic Profile Enabling by IPA

This procedure describes thehow procedure to configure automaticimmediate Profile enabling usingwhen default SM-DP+ requested by IPA. @startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox participant "<b>IPA"“<b>IPA” as IPA participant "<b>eUICC“<b>eUICC (ISD-R)"(ISD-R)” as eUICC IPA -> eUICC : [1] ES10b.ConfigureAutomaticProfileEnabling([autoEnableFlag],[smdpOid],[smdpAddress])ES10b.ConfigureImmediateProfileEnabling ([immediateEnableFlag],[smdpOid],[smdpAddress]) alt If any eIM Configuration Data is already present in the eUICC eUICC -->→ IPA : [2] error else Otherwise rnote over eUICC [3] Activate/deactivate automaticimmediate Profile enabling [4] Store the automaticdefault enablingSM-DP+ data (smdpOid(defaultSmdpOid and smdpAddress),defaultSmdpAddress), if present in the command end rnote eUICC -->→ IPA : [5] OK end @enduml [TableFigure Description17 automaticallyConfigure generated]by 17.IPA :of ConfigureImmediate Automatic Profile Enabling by IPA Start Conditions: The eUICC does not contain any eIM Configuration Data. Procedure: 1. The IPA calls "ES10b.ConfigureAutomaticProfileEnabling"“ES10b. ConfigureImmediateProfileEnabling” function optionally comprising autoEnableFlag,immediateEnableFlag, smdpOid,defaultSmdpOid, and smdpAddress.defaultSmdpAddress. 2. If any eIM Configuration Data is already present in the eUICC, the eUICC SHALL return an error and the procedure SHALL stop. Otherwise, the procedure continues in step (3). 3. If autoEnableFlagimmediateEnableFlag is present and automaticimmediate Profile enabling is not activated, the eUICC SHALL activate automaticimmediate Profile enabling. If autoEnableFlagimmediateEnableFlag is not present and automaticimmediate Profile enabling is activated, the eUICC SHALL deactivate automaticimmediate Profile enabling. In all other cases, the automaticimmediate Profile enabling state is left unchanged. 4. If present,provided by IPA in step 1, the eUICC SHALL storestoredefault automaticSM-DP+ enabling data (smdpOid(defaultSmdpOid andand/or smdpAddressdefaultSmdpAddress) for default SM-DP+) for use in the automaticimmediate Profile enabling. NOTE: if defaultSmdpAddress is stored here, then it is also used as the default SM-DP+ address in the response that is provided by the GetEuiccConfiguredAddresses function (described in 5.8.1 of this specification). 5. The eUICC returns ok to the IPA. NOTE: How the configuration data (immediateEnableFlag, defaultSmdpOid, and defaultSmdpAddress) is sent to the IPAe is implementation specific.

3.4.6 Setting the Fallback Attribute for the target Profileadded

This procedure defines the execution of a setFallbackAttribute command contained within an eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution. The command is used to set the Fallback Attribute for the target Profile. @startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox participant “<b>IPA” as IPA participant “<b>eUICC\n<b>IPA Services (ISD-R)” as E rnote right IPA [1] Check if Fallback Mechanism is supported by eUICC End rnote E --> IPA: error rnote over E [2] Find target Profile End rnote E --> IPA: error rnote right IPA [3] check if current Fallback Profile is target Profile end rnote E --> IPA: ok rnote right IPA [4] Verify that FallbackAllowed is TRUE End rnote E --> IPA: error alt [5a] If Fallback Profile is enabled E --> IPA: error else [5b] If Fallback Profile is disabled rnote right IPA Remove Fallback Attribute from Fallback Profile end rnote rnote right IPA Set Fallback Attribute for target Profile end rnote E -> IPA: ok end rnote right IPA [6] Set Fallback Attribute for target Profile end rnote E -> IPA: ok @enduml Figure 18 Set Fallback Attribute Start Conditions: An eUICC Package containing a ‘setFallbackAttribute’ command was received within an “ES10b.LoadEuiccPackage” by the eUICC. The eIM signature and replay counter have successfully been verified (see 3.3.1 Generic eUICC Package Download and Execution). Procedure: 1. If the eUICC does not support the Fallback Mechanism the procedure SHALL stop and the result of this command SHALL indicate error (‘processingTerminated’ with ‘unknownOrDamagedCommand). 2. The ISD-R SHALL find the target Profile with the given ICCID. If the target Profile is not available, the ISD-R SHALL stop the procedure with a result indicating a failure (‘iccidOrAidNotFound‘). 3. The ISD-R SHALL check if the target Profile already has the Fallback Attribute set, if yes, the procedure SHALL stop and the result of this command SHALL indicate success (‘ok’). 4. The ISD-R SHALL check if Fallback is allowed for the target Profile by verifying that the fallbackAllowed flag is set to TRUE. If the flag is absent or set to FALSE, the procedure SHALL stop and the result of this command SHALL indicate error (‘fallbackNotAllowed (2)’). The ISD-R SHALL check if the target Profile is the Emergency Profile with ecallIndication set to TRUE. If yes, the procedure SHALL stop and the result of this command SHALL indicate error (‘undefinedError(127)’). 5. The ISD-R SHALL check if there is a Profile that already has the Fallback Attribute set (i.e., a Fallback Profile is present). If so, the ISD-R SHALL check the state of this Fallback Profile: a. if this Fallback Profile is enabled, the procedure SHALL stop and the result of this command SHALL indicate error (‘fallbackProfileEnabled (3)’). b. if this Fallback Profile is disabled, the ISD-R SHALL unset the Fallback Attribute from this Profile, and set the Fallback Attribute of the target Profile. After that the procedure SHALL stop and the result of this command SHALL indicate success (‘ok’).

3.4.7 Unsetting the Fallback Attribute for the target Profileadded

This procedure defines the execution of a unsetFallbackAttribute command contained within an eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution. The command is used to unset the Fallback Attribute of the current Fallback Profile. @startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox participant “<b>IPA ” as IPA participant “<b>eUICC\n<b>IPA Services (ISD-R)” as E alt If Fallback Profile does not exist E -> IPA: [1a] error else If Fallback Profile exists and is disabled rnote right IPA [1bi] remove Fallback Attribute from current Fallback Profile end rnote E -> IPA: [1bi] OK else If Fallback Profile exists and is enabled E-> IPA: [1bii] error end @enduml Figure 19 Unset Fallback Attribute Start Conditions: An eUICC Package containing a ‘unsetFallbackAttribute’ command was received within an “ES10b.LoadEuiccPackage” by the eUICC. The eIM signature and replay counter have successfully been verified (see 3.3.1 Generic eUICC Package Download and Execution). The Fallback Mechanism is supported by the eUICC. Procedure: 1. The ISD-R SHALL check if the Fallback Attribute is set for any Profile on the eUICC and a. if not, the procedure SHALL stop, and the result of this command SHALL indicate an error (‘noFallbackAttribute’) b. if yes, and i. if the Fallback Profile is disabled, unset the Fallback Attribute of that Profile. After that, the procedure is completed, and the result of this command SHALL indicate success (‘ok’). ii. if the Fallback Profile is enabled, the procedure SHALL stop and the result of this command SHALL indicate error (‘fallbackProfileEnabled (3)’). NOTE: Upon successful completion of this command, no Fallback Profile exists on the eUICC.

3.5.1 eIM Configuration Data managed by eIMmodified

…equested by the eIM. All the initiated requests by the eIM SHALL be signed by an Associated eIM and verified by the eUICC. The eIM initiated procedures are to: … - Add a new eIM Configuration Data. - Delete an existing eIM Configuration Data. - Update an existing eIM Configuration Data.

3.5.1.1 Addition of eIM Configuration Datamodified

… Add eIM Configuration Data to eUICC storage end rnote rnote over eUICC [2] Generate addEIM eCO execution result data structure (addEimResult) endrnote @enduml … [PlantUMLFigure diagram]20 18. Addition of eIM Configuration Data Start Conditions: - A eUICC Package containing an 'addEim' was received within an "ES10b.LoadEuiccPackage" by the eUICC. - The eUICC contains eIM Configuration Data of at least one Associated eIM and the eUICC Package was verified as defined in section 3.3.1. Procedure: 1. Upon succ … M to its list of Associated eIMs. The eUICC SHALL stop the procedure indicating a failure if: a. the eUICC does not have sufficient memory to store the new eIM … (“eimInsufficientMemory”)(“insufficientMemory”) b. no eimId is provided in the eUICC Package or eimId exceeds its maximum length (“commandError”) c. the provided eimId belongs to an eIM already associated with the eUICC (“commandError”)(“associatedEimAlreadyExists”) d. the counterValue exceeds the maximum value supported by the eUICC (“counterValueOutOfRange”) e. the eUICC is requested to generate an associationToken but the value provided is not set to -1 (“invalidAssociationToken”) f. the provided euiccCiPKId is not an entry within euiccCiPKIdListForSigning in eUICCInfo2 (“ciPKUnknown”) e.g. any other error during command execution occurs (“undefinedError”). 2. The procedure continues as defined in section 3.3.1. End Conditions: eIM Configuration D… …

3.5.1.2 Deletion of eIM Configuration Datamodified

…emove eIM Configuration Data from eUICC endrnote rnote over eUICC [3] Generate deleteEim eCO execution result data structure (deleteEimResult) endrnote @enduml … [PlantUMLFigure diagram]21 19. Deletion of eIM Configuration Data Start Conditions: - A eUICC Package containing a 'deleteEim' was received within an "ES10b.LoadEuiccPackage" by the eUICC. - The eUICC contains eIM Configuration Data of at least one Associated eIM and the verifications as defined in section 3.3.1 were performed. Procedure: 1. Upon s… …

3.5.1.3 Update of eIM Configuration Datamodified

…IM Configuration Data in eUICC storage end rnote rnote over eUICC [2] Generate updateEim eCO execution result data structure (updateEimResult) endrnote @enduml … [GraphicalFigure user22 interface, application, table Description automatically generated] 20. Update of eIM Configuration Data Start Conditions: - A eUICC Package containing an 'updateEim' was received within an "ES10b.LoadEuiccPackage" by the eUICC. - The eUICC contains eIM Configuration Data of at least one Associated eIM and the eUICC Package was verified as defined in section 3.3.1. Procedure: 1. Upon successful verifications of the eUICC Package (see section 3.3.1), the ISD-R SHALL update the eIM Configuration Data of the eIM addressed by the provided “eimID”.“eimId”. The eUICC SHALL stop the procedure indicating a failure if: a. the eIM cannot be found in the list of Associated eIMs or no “eimID”“eimId” is provided in the eUICC Package (“eimNotFound”) b. neitherthe ”associationToken” is included in the EimConfigurationData data object (“commandError”) c. none of “counterValue” nor, theeimPublicKeyData, “eimPublicKeyData”eimIdType, areeimFqdn, eimSupportedProtocol, trustedPublicKeyDataTls or euiccCiPKId is included in the eUICCEimConfigurationData Packagedata object (“commandError”) c.d. the “counterValue” is updated to a value lower than the currently stored value while the “eimPublicKeyData” are not updated (“commandError”). d.e. the provided euiccCiPKId is not an entry within euiccCiPKIdListForSigning in eUICCInfo2 (“ciPKUnknown”) e.f. any other error during command execution occurs (“undefinedError”) 2. The procedure continues as defined in section 3.3.1. End Conditions: The eIM Configuratio… …

3.5.1.4 Request for a list of Associated eIMsmodified

…r eUICC [1] List associated eIMs (listEim) end rnote rnote over eUICC [2] Generate listEim eCO execution result data structure (listEimResult) endrnote @enduml … [GraphicalFigure user23 interface, text, application, table Description automatically generated] 21. Request for a list of Associated eIMs Start Conditions: - A eUICC Package containing a 'listEim' was received within an "ES10b.LoadEuiccPackage" by the eUICC. - The eUICC contains eIM Configuration Data of at least one Associated eIM and the eUICC Package was verified as defined in section 3.3.1. Procedure: 1. Upon suc… …

3.5.2 eIM Configuration Data managed by IPAmodified

…onfiguration Data requested by the IPA. All the initiated requests by the IPA SHALL be protected as per the ES10 security. The IPA initiated procedures are to: … - Add of an initial eIM Configuration Data. - Complete removal of eIM Configuration Data. NOTE: The protection of IPA initiated request is implementation specific under the responsibility of IoT Device manufacturer.

3.5.2.1 Addition of initial eIM Configuration Datamodified

… eUICC IPA -> eUICC : [1] ES10b.AddInitialEim(EimConfigurationData) alt If any eIM Configuration Data is already present in the eUICC eUICC --> IPA : [2] error … (associatedEimAlreadyExist) else Otherwise continue processing the command alt Any of the subsequent checks fails eUICC --> IPA : [3] error (one of: insufficientMemory, invalidAssociationToken, counterValueOutOfRange, commandError, ciPKUnknown, undefinedError) else Otherwise rnote over eUICC [3][4] Store the eIM Configuration Data end rnote eUICC --> IPA : [4][5] AddInitialEimResponse end @enduml [TableFigure Description24 automatically generated] 22. Addition of initial eIM Configuration Data Start Conditions: - The eUICC does not contain any eIM Configuration Data. Procedure: 1. The IPA calls "ES10b.AddInitialEim" function comprising eIM Configuration Data (EimConfigurationData). 2. If any eIM Configuration Data is already present in the eUICC, the eUICC SHALL return an error and(“associatedEimAlreadyExists”) the and the procedure SHALL stop. Otherwise,3. The eUICC SHALL stop the procedure continuesindicating a failure if: a. the counterValue exceeds the maximum value supported by the eUICC (“counterValueOutOfRange”). b. the eUICC is requested to generate an associationToken but the value provided is not set to -1 (“invalidAssociationToken”) c. the eUICC does not have sufficient memory to store the initial eIM (“insufficientMemory”) d. no eimId is provided or eimId exceeds its maximum length (“commandError”) e. the provided euiccCiPKId is not an entry within euiccCiPKIdListForSigning in stepeUICCInfo2 (3).(“ciPKUnknown”) 3.f. any other error during command execution occurs (“undefinedError”). 4. If requested, the eUICC SHALL calculate the association token and store it together with the eIM Configuration Data. 4.5. The eUICC returns the AddInitialEimResponse to the IPA. End Conditions: - The eUICC is associated with the eIM as per the eIM Configuration Data. NOTE: In case IPAe is used, the addition of initial eIM Configuration Data uses the Eim… …

3.5.2.2 Deletion of all eIM Configuration Datamodified

… ES10b.EuiccMemoryReset(resetEimConfigData) rnote over eUICC [2] Removes all eIM Configuration Data end rnote eUICC --> IPA : [3] ok or nothingToDelete @enduml … [GraphicalFigure user25 interface,Deletion text, application Description automatically generated] 23. :Deletion of all eIM Configuration Data Start Conditions: - None Procedure: 1. The IPA calls "ES10b.EuiccMemoryReset" function with resetEimConfigData bit set to one. 2. The eUICC removes all eIM Configuration Data. 3. The eUICC returns ok or nothingToDelete. End Conditions: - The eUICC does not contain any eIM Configuration Data.

3.5.2.3 Reading eIM Configuration Datamodified

…b>IPA" as IPA participant "<b>eUICC (ISD-R)" as eUICC IPA -> eUICC : [1] ES10b.GetEimConfigurationData eUICC --> IPA : [2] List of EimConfigurationData @enduml … [GraphicalFigure user26 interface, text, application, email Description automatically generated] 24. : Reading eIM Configuration Data by IPA Start Conditions: - None Procedure: 1. The IPA calls "ES10b.GetEimConfigurationData" function. 2. The eUICC returns the list of eIM Configuration Data stored in the eUICC to the IPA. End Conditions: - None

3.6 Error handling within an RSP sessionmodified

… Session could fail while the IPA is invoking an ES10 function for reasons other than an error status reported by the eUICC. Examples of such failures include: … - In the case of a removable eUICC card, the card is unexpectedly removed. - The IoT Device is powered off, e.g., by running out of the battery or by the user. - A software fault could cause a crash of the IPA, host IoT Device, and/or baseband processor. When possible (e.g., when power is restored), the IPA SHOULD provi… …

3.7 Notification Delivery to Notification Receiversmodified

… eIM -> DP : ES9+’.HandleNotification DP -> eIM : ACK end IPA -> E : [3] ES10b.RemoveNotificationFromList rnote over E: [4] Delete Notification end end @enduml … [DiagramFigure Description27 automatically generated] 25. : Notification Delivery to Notification Receivers Start Condition: This procedure requires the following start conditions: - A Secure Connection between the eIM and the IPAd is established. - Either a profile installation or a PSMO has been executed such that one or more Notifications MAY have been generated by the eUICC. - IPAd is configured to send Notifications using ES9+.HandleNotification or ESipa.HandleNotification. Procedure: 1. The IPAd SHALL retrieve pending Notifications… …

3.8 IoT Device and eUICC Initialisationmodified

The IoT Device and eUICC SHALL be initialised according to SGP.22 [4] sections 3.4.1,3.8.1, 3.4.2,3.8.2, 3.4.33.8.3 and 5.7.1.3.8.4 of this specification.

3.8.1 eUICC Initialisationadded

The eUICC SHALL be initialised according to sections 3.4.1 of SGP.22 [4].

3.8.2 IoT Device Capabilitiesadded

The eUICC SHALL request the IoT Device to send the Terminal Capability command by setting the related bit in the file control parameters of the MF. The IoT Device SHALL report its support of IPA functions using the Terminal Capability command data defined in ETSI TS 102 221 [34]. This command SHALL be sent before the SELECT ISD-R command defined in section 3.8.4 of this specification. Within the Terminal Capability template (tag ‘A9’), the tag ‘84’ is used for indicating the IoT Device’s support for eUICC related functions. . The IPAd support is indicated in the first byte within the TLV object under tag '84': b8 b7 b6 b5 b4 b3 b2 b1 Meaning - - - - - - - 1 IPAd supported - - - - - - - 0 IPAd not supported x x x x x x x - Not applicable Table 4 eUICC-related IoT Device Capabilities If an IoT Device supports IPAd, b1 SHALL be set to 1. Otherwise, b1 SHALL be set to 0. The eUICC SHALL only enable the ES10 functions if the IoT Device indicates support for IPAd. The conditions for activating the IPAe are defined in section 3.8.4.

3.8.3 eUICC File Structureadded

The eUICC File structure SHALL be initialised according to sections 3.4.3 of SGP.22 [4].

3.8.4 ISD-R Selection and IPAe Activationadded

Before sending any command to the eUICC, the IPAd SHALL establish a logical channel and select the ISD-R. The opening of the logical channel and the selection of the ISD-R SHALL be done explicitly using, respectively, the MANAGE CHANNEL command and the SELECT command defined in GlobalPlatform Card Specification [32]. This MANAGE CHANNEL and SELECT commands can be intrinsically used via a dedicated IoT Device Operating System API (e.g., OMAPI defined by GlobalPlatform[33] if provided). The IoT Device SHALL ensure that only the IPAd, but no other application on the IoT Device, is permitted to select the ISD-R, except that the ISD-R MAY also be selected during eUICC initialisation as defined in section 3.8.1. In order to provide information about the capabilities supported by the eUICC at an early point in time, additional information is provided by the ISD-R. On the reception of the SELECT ISD-R Command, the following data SHALL be returned within the FCI template after the objects defined in GlobalPlatform Card Specification [32]: -- ASN1START ISDRProprietaryApplicationTemplateIoT ::= [PRIVATE 1] SEQUENCE { -- Tag 'E1' euiccConfiguration BIT STRING { ipaeSupported(0), -- IPA in the eUICC (IPAe) supported enabledProfile(1) -- eUICC contains an Enabled Profile } } -- ASN1STOP The eUICC SHALL indicate its support for IPAe by setting the ipaeSupported bit in the euiccConfiguration field. If the IoT Device supports the requirements on IPAe as defined in Annex A.2 and if the eUICC indicated support for IPAe in the ISDRProprietaryApplicationTemplateIoT, the IoT Device MAY activate the IPAe by sending an IpaeActivationRequest to the ISD-R. The IpaeActivationRequest SHALL be sent to the ISD-R using the transport mechanism defined in section 5.7.2 of SGP.22 [4]. The command data SHALL be coded as follows: -- ASN1START IpaeActivationRequest ::= [66] SEQUENCE { -- Tag 'BF42' ipaeOption BIT STRING { activateIpae(0) -- IPAe activation } } -- ASN1STOP The response data SHALL be coded as follows: -- ASN1START IpaeActivationResponse ::= [66] SEQUENCE { -- Tag 'BF42' ipaeActivationResult INTEGER {ok(0), notSupported(1)} } -- ASN1STOP If the IoT Device indicates in the Terminal Capability command the support for IPAd (see section 3.8.2) and the IPAd does not send an IpaeActivationRequest, the eUICC SHALL NOT activate the IPAe. If the IoT Device indicates that IPAd is not supported, the eUICC SHALL activate the IPAe, if supported by the eUICC. NOTE: For IoT Devices and eUICC that support both IPAe and IPAd, the IoT Device can reset the eUICC and send new Terminal Capability indicating that IPAd is supported to activate the IPAd in case the IPAe is activated.

3.9.2.2 Event Retrieval by the eIMmodified

This section describes the indirect Event retrievalRetrieval from SM-DS to eIM. @startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochro … '.AuthenticateClient function rnote over EIM : [13] Parse Event entry/ies \nobtained from the SM-DS EIM -> IPA : [14] ESipa.AuthenticateClient response @enduml … [DiagramFigure Description28 automatically generated] 26. : Event Retrieval by the eIM Start Conditions: In addition to the start conditions required by the Common Mutual Authentication procedure defined in section 3.1.2 … and the eIM. 2. The IPA parses the eIM Package received in step 1. The IPA identifies that the eIM Package contains a ProfileDownloadTriggerRequest. To trigger … eventEvent retrievalRetrieval from the SM-DS, the ProfileDownloadTriggerRequest is either an empty data object (i.e., without profileDownloadData) or contains a profileDownloadData with con … the latter case the IPA is expected to provide SM-DS FQDN in step (6). If the format of ProfileDownloadTriggerRequest is invalid, or data needed by IPA for the … eventEvent retrievalRetrieval is missing, the procedure SHALL stop. 3. If euiccInfo1 is not yet retrieved by the eIM or IPA, the IPA MAY request euiccInfo1 from the eUICC by calling ES10b.G … SGP.22 [4]. 8. The eIM and the SM-DS process ES11'.InitiateAuthentication function comprising eUICC Challenge, SM-DS FQDN, and euiccInfo1 as defined in section … 5.6.15.11.1. of SGP.22 [4]. If the SM-DS FQDN provided in ES11'.InitiateAuthentication did not come from IPA (was not obtained from IPA in step 6 e.g., due to IPA has capability eimDownloa … tes), the eIM SHALL identify the relevant information and build euiccSigned1. 12. The eIM and SM-DS process the ES11'.AuthenticateClient function as defined in … 5.6.35.11.2. of SGP.22 [4]. 13. The eIM parses the Event entry/ies obtained from the ES11'.AuthenticateClient from the SM-DS. 14. The eIM sends the ESipa.AuthenticateClient response to the … e IPA to start downloading a new Profile. In case of an error, IPA SHALL trigger the cancellation of the on-going RSP session (see section 3.2.3.3) with reason … sessionAbortedundefinedReason and the procedure SHALL stop.

4.1 IPA Capabilitiesmodified

…ns. In addition, IPA Capabilities MAY indicate the support of eIM Package transfer including the type of connection over ESipa. IPA Capabilities SHALL include: … - Support for direct profile download - Support for indirect profile download -o Support for eIM handled download data (e.g. Activation Code) during indirect profile download. -o Support for eIM generated ctxParams1 during indirect profile download. -o Support for eIM performed Profile Metadata verification during indirect profile download. -o Use of compact data objects to minimize number of transferred ESipa bytes during indirect profile download. IPA Capabilities MAY include support for eIM Package transfer over ESipa: - eIM Package retrieval using HTTPs over TCP (see section 3.1.2.1) - eIM Package retrieval using CoAP/DTLS over UDP (see section 3.1.2.2) - eIM Package injection using HTTPs over TCP (see section 3.1.2.1) - eIM Package injection using CoAP/DTLS over UDP (see section 3.1.2.2) - proprietary IPA Capabilities data object structure is defined as follows: -- ASN1START IpaCapabilities ::= SEQUENCE { ipaFeatures [0] BIT STRING { directRspServ … ipaRetrieveCoaps(1), ipaInjectHttps(2), ipaInjectCoaps(3), ipaProprietary(4) } OPTIONAL } -- ASN1STOP ipaFeatures indicates the features supported by the IPA: … - The directRspServerCommunication set to 1 indicates that IPA supports direct Profile download according to Section 3.2.3.1. This includes direct delivery of Notifications to the SM-DP+. - The indirectRspServerCommunication set to 1 indicates that IPA supports indirect Profile download according to Section 3.2.3.2. This includes delivery of Notifications via the eIM to SM-DP+. - An IPA supporting indirect profile download MAY further have the following capabilities: -o The eimDownloadDataHandling set to 1 indicates that IPA does not handle download data such as Activation Codes, SM-DP+ data retrieved from SM-DS, and default S … main at the eIM where the eIM parses and extracts the relevant data such as SM-DP+ address, matchingId, and SM-DP+ OID for use in ESipa.InitiateAuthentication. … -o The eimCtxParams1Generation set to 1 indicates that IPA does not support generation of CtxParams1 and expects the eIM to generate and provide CtxParams1 to IPA as part of ESipa.InitiateAuthentication. -o The eimProfileMetadataVerification set to 1 indicates that IPA does not support verification of Profile Metadata and expects the eIM to verify Profile Metadata … that eIM checks as part of ESipa.GetBoundProfilePackage that the Profile Metadata provided in the BPP matches the Profile Metadata in ESipa.AuthenticateClient. … -o The minimizeEsipaBytes set to 1 indicates that IPA uses compact data objects and avoids sending data over ESipa that the other party already knows in order to minimize the number of transmitted bytes between IPA and eIM. It is expected that the eIM is able to identify missing parts (bytes) and re-buildre- build full data object structures. The eIM MAY leverage pre-configured static eUICC data, eUICC data obtained from another IoT Device within the same batch for which … e download related ESipa function descriptions in Section 5.14. ipaSupportedProtocols indicates which eIM Package transfer (see 3.1.1) is supported by the IPA: … - ipaRetrieveHttps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using HTTPs over TCP as described in section 3.1.2.1 - ipaRetrieveCoaps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using CoAP/DTLS over UDP as described in section 3.1.2.2 - ipaInjectHttps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using HTTPs over TCP as described in section 3.1.2.1 - ipaInjectCoaps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using CoAP/DTLS over UDP as described in section 3.1.2.2 ipaProprieta… …

4.2 eIM Supported Protocolmodified

…IM over ESipa. eimRetrieveHttps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using HTTPs over TCP as described in section 3.1.2.1 … - eimRetrieveCoaps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using CoAP/DTLS over UDP as described in section 3.1.2.2 - eimInjectHttps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using HTTPs over TCP as described in section 3.1.2.1 - eimInjectCoaps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using CoAP/DTLS over UDP as described in section 3.1.2.2 - eimProprietary set to 1 indicates support of a transport protocol not described in section 3.1.2.

4.3 eIM Identifiermodified

…signment, an eIM OID SHOULD be allocated to the eIM and used to encode the eimId. An eimId of type eimIdTypeOid SHALL be encoded using the OID, as allocated by … https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers,https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers. withNOTE1: theIt following child nodes: - eim (999): indicates that this is anup eIM.to - eimOwner (x): identifies the eIM owner, where “x” is freely chosen by the eimOwner. NOTE: If the eIM owner is identical to thedefine enterprisechild indicatednodes inand thevalues OIDaccordingly. prefix, the same value can be used. - eimInstance (y): identifies an eIM instance, where “y” is freely chosen by the eimOwner. NOTE: Prefix is iso.org.dod.internet.private.enterprise (1.3.6.1.4.1). NOTE:NOTE2: An example OID “iso.org.dod.internet.private.company.eim.eimowner.124” is encoded as follows: “1.3.6.1.4.12345.999.10.124”. An eimId of type eimIdTypeFqdn SHAL… …

4.4 Profile MetaDataadded

The profile Metadata as defined in SGP.22 [4] SHALL be replaced as follows: -- ASN1START -- Definition of ProfileInfo ProfileInfo ::= [PRIVATE 3] SEQUENCE { -- Tag 'E3' iccid Iccid OPTIONAL, isdpAid [APPLICATION 15] OctetTo16 OPTIONAL, -- AID of the ISD-P containing the Profile, tag '4F' profileState [112] ProfileState OPTIONAL, -- Tag '9F70' profileNickname [16] UTF8String (SIZE(0..64)) OPTIONAL, -- Tag '90' serviceProviderName [17] UTF8String (SIZE(0..32)) OPTIONAL, -- Tag '91' profileName [18] UTF8String (SIZE(0..64)) OPTIONAL, -- Tag '92' iconType [19] IconType OPTIONAL, -- Tag '93' icon [20] OCTET STRING (SIZE(0..1024)) OPTIONAL, -- Tag '94', see condition in ES10b:GetProfilesInfo profileClass [21] ProfileClass OPTIONAL, -- Tag '95' notificationConfigurationInfo [22] SEQUENCE OF NotificationConfigurationInformation OPTIONAL, -- Tag 'B6' profileOwner [23] OperatorId OPTIONAL, -- Tag 'B7' dpProprietaryData [24] DpProprietaryData OPTIONAL, -- Tag 'B8' profilePolicyRules [25] PprIds OPTIONAL, -- Tag '99' serviceSpecificDataStoredInEuicc [34] VendorSpecificExtension OPTIONAL, -- Tag 'BF22' ecallIndication [123] BOOLEAN OPTIONAL, -- Tag '9F7B' fallbackAttribute [38] BOOLEAN DEFAULT FALSE, -- Tag '9F26', indicates a Fallback Profile if set to TRUE fallbackAllowed [103] BOOLEAN OPTIONAL -- Tag '9F67', indicates if Fallback is authorized by the Profile Owner } -- ASN1STOP The data item ecallIndication MAY be present. If absent it SHALL be treated as if it was set to FALSE. An ecallIndication data item set to TRUE indicates, that the enabling or disabling of an Emergency Profile MAY be triggered using the ES10b.EnableEmergencyProfile and ES10b.DisableEmergencyProfile functions. It SHALL NOT be possible to have multiple Profiles on an eUICC with the ecallIndication data item set to TRUE. The data item fallbackAttribute MAY be present. If set to TRUE, the Profile can be enabled using the ES10b.ExecuteFallbackMechanism function. If the fallbackAttribute data item is absent or set to FALSE the Profile can not be enabled using the ES10b.ExecuteFallbackMechanism function. It SHALL NOT be possible to have multiple Profiles on an eUICC with the fallbackAttribute set to TRUE. The data item fallbackAllowed MAY be present. Only if set to TRUE, it SHALL be possible to set the fallbackAttribute. NOTE: The Profile Owner decides upon Profile generation to include or not the fallbackAllowed flag into the Profile.

5.1 Overview of Functions per Interfacemodified

This section provides the description of the interfaces and functions within the Remote SIM Provisioning and Management system involving the eUICC, including the following: eUICC Interfaces - ES6: The interface used by the Operator to manage the content of their Profile. - ES8+: Provides a secure end-to-end channel between the SM-DP+ and the eUICC for the administration of the ISD-P and the associated Profile during download and installation. - ES9+: Used to provide a secure transport between the SM-DP+ and the IPAe for the delivery of the Profile Package. - ES10a: Used by the IPAd to get the configured addresses from the eUICC for Root SM-DS, and optionally for the default SM-DP+. - ES10b: Used by the IPAd to transfer a Profile Package to the eUICC. - ES11: Interface between the IPAe and an SM-DS (Alternative SM-DS or Root SM-DS)SM- DS) for the Event retrieval.Retrieval. - ESipa: Interface between an eIM and an IPA used to trigger a Profile download at the IPA and to provide a secure transport for the delivery of eUICC Packages unless the underlying transport provides necessary security. - ESep: Logical end-to-end interface between the eIM and the eUICC used to transfer eUICC Packages for Profile State Management and eIM configuration by eIM. Server to Server Interfaces - ES2+: Interface between the Operator and the SM-DP+ used by the Operator to order Profile Package preparation. - ES12: Interface between the SM-DP+ and an SM-DS (Alternative SM-DS or Root SM-DS) for the Event management. Device to RSP Server Interfaces - ES9+: Used to provide a secure transport between the SM-DP+ and the IPAd for the delivery of the Profile Package. - ES11: Interface between the IPAd and an SM-DS (Alternative SM-DS or Root SM-DS)SM- DS) for the Event retrieval.Retrieval. eIM interfaces - ES9+’: Used to provide a secure transport between the SM-DP+ and the eIM for the delivery of the Bound Profile Package. - ESipa: Interface between an eIM and an IPA used to trigger a Profile download at the IPA and to provide a secure transport for the delivery of eUICC Packages unless the underlying transport provides necessary security. - ESep: Logical end-to-end interface between the eIM and the eUICC used to transfer eUICC Packages for Profile State Management and eIM configuration by eIM. - ES11’: Interface between the eIM and the SM-DS (Alternative SM-DS or Root SM-DS)SM- DS) for the Event retrieval.Retrieval. The following table presents the normative list of all the functions that are defined in this section. Request-Response Functions: |Function Interface | Functions | Function | provider Role | ES2+ | As defined in section 5.3 of SGP.22 [4]. | SM-DP+ | ES6 | As defined in section 5.2 of SGP.22 [4]. | ISD-P | ES8+ | As defined in section 5.5 of SGP.22 [4]. | eUICC | ES9+ | As defined in section 5.6 of SGP.22 [4]. |ES9+ SM-DP+AuthenticateClient | ES9+’ | InitiateAuthentication | GetBoundProfilePackage |SM-DP+ ES9+’ AuthenticateClient | HandleNotification | CancelSession | ES10a | As defined in section 5.7 of SGP.22 [4]. | ISD-R ES10a (IPA Services) | GetEuiccConfiguredAddresses |Services) ES10b | LoadEuiccPackage | ISD-R (IPA Services) | GetEUICCInfo | GetEUICCChallenge | AddInitialEim | eUICCMemoryReset | AuthenticateServer | PrepareDownload | LoadBoundProfilePackage | CancelSession | GetCerts | GetEID | RetrieveNotificationsList |ISD-R ES10b RemoveNotificationFromList |(IPA GetRAT |Services) GetProfilesInfo |ImmediateEnable EnableUsingDDProfileRollback |ConfigureImmediateProfileEnabling ProfileRollbackGetEimConfigurationData |ExecuteFallbackMechanism ConfigureAutomaticProfileEnablingReturnFromFallback |EnableEmergencyProfile GetEimConfigurationDataDisableEmergencyProfile |GetConnectivityParameters SetDefaultDpAddress ES11 | As defined in section 5.8 of SGP.22 [4]. | SM-DS |InitiateAuthentication ES11’ | As defined in section 5.8 of SGP.22 [4]. | SM-DS |AuthenticateClient ES12 | As defined in section 5.9 of SGP.22 [4]. | SM-DS | ESipa | TransferEimPackage | IPA | InitiateAuthentication | eIM | GetBoundProfilePackage |ESipa AuthenticateClient |eIM GetEimPackage | ProvideEimPackageResult | HandleNotification | CancelSession | ESep | Enable | eUICC | Disable | Delete | ListProfileInfo | GetRAT |ESep ConfigureAutoEnableConfigureImmediateEnable |eUICC AddEim | UpdateEim | DeleteEim | ListEim |SetDefaultDpAddress 3.Table :5 Request-Response Functions Notification Handler Functions: |Function Interface | Notification handler functions | Function | handler/recipient | ES2+ | As defined in section 5.3 of SGP.22 [4]. | Operator | ES9+ | HandleNotification | SM-DP+ | ES9+’ | HandleNotification | SM-DP+ | ESipa | HandleNotification | eIM |Table 4. :6 Notification Handler Functions

5.2.1 Common Data Typesmodified

The functions provided in this section deal with management of the eUICC and Profile, so that the common data defined in this section needs to be used in most of the functions. Type name Description Type definition 5.As :defined in table 21 of section 5.2.1 of SGP.22 [4] Table 7 Common data types

5.3 ES2+ (Operator -- SM-DP+)modified

ES2+ is the interface between: - The Operator. - SM-DP+ This interface is used by the Operator to order the Profile Package preparation for specific eUICC(s) and the delivery of the Profile Package from the S… …

5.4 ES6 (Operator -- eUICC)modified

ES6 is the interface between: - The Operator. - eUICC (Enabled Profile) This interface is used by the Operator to make modifications on their Profile in the eUICC using legacy OTA mechanisms. This interface … …

5.5 ES8+ (SM-DP+ -- eUICC)modified

The ES8+ is the interface between: - The SM-DP+ (Profile Package Binding function). - The eUICC. This interface is intended to be tunnelled either over: - the ES9+ and ES10b interfaces for direct profile download (i.e., the IPA directly communicates with the SM-DP+) as shown in Figure 1929 or - ES9+', ESipa, and ES10b for indirect profile download (i.e., the IPA communicates with the SM-DP+ via the eIM) as shown in Figure 20.30. []SM-DP+ 27.IoT :Device Profile Profile IPA Package Package Binding delivery eUICC ES8+ functions ES8+ ES8+ ES8+ ES9+ ES10b Figure 29 ES8+ interface through ES9+ and ES10b []SM-DP+ 28.eIM :IoT Device Profile Profile IPA Package Package Binding delivery eUICC ES8+ functions ES8+ ES8+ ES8+ ES8+ ES8+ ES9+’ ESipa ES10b Figure 30 ES8+ through ES9+’ ESipa, and ES10b The ES8+ functions are addressed to the eUICC through a secure channel established between the Profile Package Binding function of the SM-DP+ and the eUICC. The ES8+ functions are called by the SM-DP+ and executed by the eUICC. All the functions related to ES8+ SHALL be processed as defined in section 5.5 of SGP.22 [4].[4] Theywith arethe calledfollowing modifications to the command data structure of the ES8+.StoreMetadata function. Command data The command data for this function is identified by the SM-DP+data structure defined hereunder. -- ASN1START StoreMetadataRequest ::= [37] SEQUENCE { -- Tag 'BF25' iccid Iccid, serviceProviderName [17] UTF8String (SIZE(0..32)), -- Tag '91' profileName [18] UTF8String (SIZE(0..64)), -- Tag '92' (corresponds to 'Short Description' defined in SGP.21 [2]) iconType [19] IconType OPTIONAL, -- Tag '93' (JPG or PNG) icon [20] OCTET STRING (SIZE(0..1024)) OPTIONAL, -- Tag '94' (Data of the icon. Size 64 x 64 pixel. This field SHALL only be present if iconType is present) profileClass [21] ProfileClass DEFAULT operational, -- Tag '95' notificationConfigurationInfo [22] SEQUENCE OF NotificationConfigurationInformation OPTIONAL, profileOwner [23] OperatorId OPTIONAL, -- Tag 'B7' profilePolicyRules [25] PprIds OPTIONAL, -- Tag '99' serviceSpecificDataStoredInEuicc [34] VendorSpecificExtension OPTIONAL, -- Tag 'BF22' serviceSpecificDataNotStoredInEuicc [35] VendorSpecificExtension OPTIONAL, -- Tag ‘BF23’ ecallIndication [123] BOOLEAN OPTIONAL, -- Tag '9F7B' fallbackAllowed [103] BOOLEAN OPTIONAL -- Tag '9F67' } -- ASN1STOP Upon reception of a StoreMetadataRequest containing ecallIndication the following steps are performed in addition to the procedure defined in SGP.22[4] section 5.5.3: Start Conditions: The target Profile SHALL NOT have the fallbackAllowed set Procedure: The eUICC SHALL: 1. Verify that the target Profile has the fallbackAllowed not set. If it is set, the eUICC SHALL stop the procedure and executedreturn byerror with reason incorrectInputValues. 2. Set the eUICC.Emergency Profile Attribute for the target Profile. 3. Generate as many Notifications as configured in the metadata. 4. Return ok.

5.6 ES9+ (IPA -- SM-DP+)modified

… described in SGP.22 [4] section 2.6.6. This interface is identical to the ES9+ interface defined in section 5.6 of SGP.22 [4], where the IPA plays the role of … LPA.LPA, except Function (ES9+): AuthenticateClient which is defined bellow.

5.6.1 Function (ES9+): AuthenticateClientadded

Related Procedures: Profile Download and Installation Function Provider Entity: SM-DP+ Description: This function SHALL be called by the IPA to request the authentication of the eUICC by the SM-DP+. This function is identical to the ES9+.AuthenticateClient function defined in section 5.6.3 of SGP.22 [4], where the IPA plays the role of LPA and the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification. -- ASN1START AuthenticateClientRequest ::= [59] SEQUENCE { -- Tag 'BF3B' transactionId [0] TransactionId, authenticateServerResponse [56] AuthenticateServerResponse -- This is the response from ES10b.AuthenticateServer } -- ASN1STOP

5.7 ES9+’ (eIM -- SM-DP+)modified

ES9+’ is the interface between: - The eIM entity. - The SM-DP+. The eIM SHALL communicate with the SM-DP+ secured by HTTPS in server authentication mode as described in SGP.22 [4] section 5.6 using the TLS requirements in SGP.22 [4] section 2.6.6.

5.7.2 Function (ES9+’): GetBoundProfilePackagemodified

Related Procedures: Profile Download and Installation Function Provider Entity: SM-DP+ Function Caller Entity: eIM Description: This function SHALL be called by the eIM to request the delivery and the binding of a Profile Package for the eUICC. This function is identical to … …

5.7.3 Function (ES9+’): AuthenticateClientmodified

Related Procedures: Profile Download and Installation Function Provider Entity: SM-DP+ Function Caller Entity: eIM Description: This function SHALL be called by the eIM to request the authentication of the eUICC by the SM-DP+. This function is identical to the ES9+.AuthenticateClient function defined in section 5.6.3 of SGP.22 [4], where the eIM plays the role of LPA.LPA and the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification.

5.7.4 Function (ES9+’): HandleNotificationmodified

Related Procedures: Profile Download and Installation Function Provider Entity: SM-DP+ Function Caller Entity: eIM Description: This function SHALL be called by the eIM to notify the SM-DP+ that a Profile Management Operation has successfully been performed on the eUICC. This function is called by the eIM upon the receipt by the eIM of either an ESipa.HandleNotification function call or an ESipa.ProvideEimPackageResult function call sent by the IPA containing a PendingNotification. When the received PendingNotification contains a ProfileInstallation result that is part of an ongoing Indirect Profile Download session, the eIM SHALL send the ES9+’.HandleNotification call to the SM-DP+ that is participating in that Indirect Profile Download session. When the PendingNotification contains an OtherSignedNotification, the eIM SHALL send the ES9+’.HandleNotification to the NotificationAddress contained in the NotificationMetadata of the OtherSignedNotification. This function is identical to the ES9+.HandleNotification function defined in section 5.6.4 of SGP.22 [4], where the eIM plays the role of LPA. In addition, in… …

5.8.1 Function (ES10a): GetEuiccConfiguredAddressesmodified

…ption: This function is identical to the ES10a.GetEuiccConfiguredAddresses function defined in section 5.7.3 of SGP.22 [4], where the IPA plays the role of LPA. … NOTE : the default SM-DP+ address that is stored in the eUICC can be updated through the functions ConfigureImmediateProfileEnabling (described in 5.9.17 of this specification) and ConfigureImmediateEnable (described in 5.13.6 of this specification) as well as functions ES10b.SetDefaultDpAddress as described in 5.9.25 of this specification and ESep.SetDefaultDpAddress as described in 5.13.11 of this specification.

5.9.1 Function (ES10b): LoadEuiccPackagemodified

Related Procedures: Generic eUICC Package Download and Execution Function Provider Entity: ISD-R (IPA Services) Description: This function executes a eUICC Package. On reception of this command,package, the eUICC SHALL: Retrieve the public key of the Associated eIM using the eimId in euiccPackageSigned. If the eimId is unknown, the eUICC SHALL return an unsigned eUICC Package error result (euiccPackageErrorUnsigned) containing the eimId received in the euiccPackageSigned. - Verify the eimSignature created upon euiccPackageSigned concatenated with associationToken using the retrieved eIM public key. If no association token is config … ived in the euiccPackageSigned. If and only if an association token is configured for the eIM, the eUICC SHALL return the associationToken in the error result. … - Verify that the eidValue in euiccPackageSigned matches its own EID. If the EID verification fails, the eUICC SHALL return a signed eUICC error result (euiccPackageErrorSigned) containing the invalidEid error code. - Verify that the counterValue in euiccPackageSigned is greater than the counter value stored in the eUICC for the Associated eIM. If the counter value verification fails, the eUICC SHALL return a signed eUICC Package error result (euiccPackageErrorSigned) containing the replayError error code. - Reset any authorisation previously granted to use the Profile Rollback Mechanism (and any related data). - Execute PSMO(s) or eCO(s) contained in the eUICC Package and generate the corresponding PSMO or eCO result(s) (euiccResultData) sequentially. If the eUICC encou … eUICC SHALL terminate processing of the remaining command sequence and generate euiccResultData containing processingTerminated with the following error codes: … -o For a PSMO 'List Profile Info' request, if the eUICC cannot generate the euiccResultData due to the size limit of the response data, the error code SHALL be resultSizeOverflow. NOTE: this could happen, e.g., when retrieving Profile Metadata of multiple Profiles containing large icons. -o If a PSMO or an eCO in the eUICC Package is unknown or unsupported, or the command data cannot be interpreted, the error code SHALL be unknownOrDamagedCommand. - Generate a signed eUICC Package Result (euiccPackageResultSigned) with the execution results of the PSMOs/eCOs (euiccResultData). The eUICC Package Result SHALL … esult is intended) SHALL be used. The signed data includes the next (not used) value of the sequence number (defined in SGP.22 [4] for use with Notifications). … - Increment the sequence number in eUICC storage by 1. - Update the counter value stored in the eUICC for the Associated eIM to the counterValue received in the euiccPackageSigned. - Return the signed eUICC Package Result (euiccPackageResultSigned). The ES10b.LoadEuiccPackage function SHALL be processed in an atomic way, meaning that in case … discarded. NOTE: In case of non-resumable interruption the ISD-R withdraws the previously received eUICC Package. The IPAd MAY call the ES10b.LoadEuiccPackage … commandfunction again, including the same eUICC Package, if it detects that the previous processing was interrupted. NOTE: How the IPA detects the interruption and how an IPA … …

5.9.2 Function (ES10b): GetEUICCInfomodified

…ication [57] additionalEuiccProfilePackageVersions [15] SEQUENCE OF VersionType OPTIONAL, ipaMode [16] IpaMode OPTIONAL, -- active IPA, mandatory within SGP.32 … rfu2euiccCiPKIdListForSigningV3 [17] SEQUENCE OF SubjectKeyIdentifier OPTIONAL, -- not used by this version of SGP.32. rfu3additionalEuiccInfo [18] OCTET STRING (SIZE(0..32)) OPTIONAL, -- not used by this version of SGP.32 rfu4highestSvn [19] VersionType OPTIONAL, -- not used by this version of SGP.32 iotSpecificInfo [20] IoTSpecificInfo OPTIONAL -- mandatory within SGP.32 } -- Definition of IoTSpecificInfo IoTSpecificInfo ::= SEQUENCE { iotVersion [0] SEQUENCE OF VersionTypeVersionType, -- SGP.32 version(s) supported by the eUICC, at least one must be present ecallSupported [1] NULL OPTIONAL, -- if present, eUICC supports the Emergency Mechanism fallbackSupported [2] NULL OPTIONAL -- if present, eUICC supports the Fallback Mechanism } -- Definition of IpaMode IpaMode ::= INTEGER { ipad (0), -- IPAd is active ipae (1) -- IPAe is active } -- ASN1STOP The procedures related to the eUICC Profil … rofile type called “IoT Minimal Profile” has been introduced with the intention to be useful for the provisioning of eUICCs in Network Constrained Devices. The … rfu2,euiccCiPKIdListForSigningV3, rfu3,additionalEuiccInfo, and rfu4highestSvn fields are reservednot forused futurein use.this version of the specification. The eUICC SHALL NOT include these fields in euiccInfo2. The SM-DP+ SHOULD ignore these fields if received with iotSpecificInfo being present. The ioTSpecificInfo data object SHALL be present. If the eUICC supports the Fallback Mechanism, the fallbackSupported flag SHALL be present within IoTSpecificInfo. The ecallSupported data object SHALL be present within IoTSpecificInfo. If the flag is set, the eUICC SHALL support the Emergency Mechanism.

5.9.4 Function (ES10b): AddInitialEimmodified

…store eIM Configuration Data to the eUICC in case the eUICC does not contain any eIM Configuration Data. Upon reception of this function call, the eUICC SHALL: … - Check if any eIM Configuration Data is already present in the eUICC. If so, the eUICC SHALL return an error code unsignedEimConfigDisallowed.associatedEimAlreadyExists. -Check if counterValue exceeds the maximum value supported by the eUICC. If so, the eUICC SHALL return the error code counterValueOutOfRange. Check if the eUICC has enough memory to store the list of provided eIM Configuration Data. If not, the eUICC SHALL return an error code insufficientMemory. -Check that the sub-field eimId of EimConfigurationData in each entry of the eimConfigurationDataList is present and that its length does not exceed the allowed maximum value. Otherwise, the eUICC SHALL return an error code commandError. Check that the sub-field euiccCiPKId of EimConfigurationData in each entry of the eimConfigurationDataList, if present, is a valid entry within euiccCiPKIdListForSigning in eUICCInfo2. If not, the eUICC SHALL return an error code ciPKUnknown. - If requested for an Associated eIM, calculate an associationToken. -If associationToken is not set to -1 the eUICC SHALL return an error code invalidAssociationToken. Store the provided list of eIM Configuration Data, including the associationToken (if requested). - Return the associationToken for each Associated eIM where it is requested. NOTE: Any further addition of eIM Configuration Data can be performed by an Associated eIM using signed eUICC Packages containing eCO(s) as defined in section 3.5.1.1. The function SHALL be performed in an atomic way, meaning that in case of any error during the commandfunction execution, the command SHALL stop and SHALL leave the eIM Configuration Data in their original state prior to commandfunction execution. Command Data The command data SHALL be coded as follows: -- ASN1START AddInitialEimRequest ::= [87] SEQUENCE { -- Tag 'BF57' eimConfigurationDataList [0] SEQUENCE OF EimConfigurationData } -- ASN1STOP The following sub-fields of EimConfigurationData SHALL be present in each entry of the eimConfigurationDataList: - eimId; - counterValue; and - either eimPublicKey or eimCertificate. The eimIdType, , the associationToken (with the value set to -1 to request the calculation of an association token for the new Associated eIM) and eimFqdn are optional for the I … 87] CHOICE { -- Tag 'BF57' addInitialEimOk SEQUENCE OF CHOICE { associationToken [4] INTEGER, addOk NULL }, addInitialEimError INTEGER { insufficientMemory(1), … unsignedEimConfigDisallowed(2),associatedEimAlreadyExists (2), ciPKUnknown(3), invalidAssociationToken(5), counterValueOutOfRange(6), commandError(7), undefinedError(127) } } -- ASN1STOP

5.9.5 Function (ES10b): eUICCMemoryResetmodified

Related Procedures: eUICC Memory Reset Function Provider Entity: ISD-R (IPA Services) Description: NOTE: ES10c.eUICCMemoryReset function defined in SGP.22 [4] has a tag number 'BF34'. This function deletes selected subsets of the Profiles stored on an eUICC regardless of their enabled status or any Profile Policy Rules. The following subsets are defined: - Operational Profiles - Test Profiles that were not pre-installed (i.e., Test Profiles that were "field loaded") Test Profiles that were pre-installed (i.e., Test Profiles that were loaded in the factory) Provisioning Profiles NOTE: The identification of pre-installed Test Profiles is out of the scope of this specification. The eUICC returns a status in resetResult indicating whether any Profiles were deleted. - The eUICC returns ok if at least one Profile is deleted. - The eUICC returns nothingToDelete if no Profile is deleted. This function can also be used to: - Reset the default SM-DP+ address to its initial value. In this context both ok and nothingToDelete response in resetResult indicates a successful execution of resetting the default SM-DP+ address. - Remove all eIM Configuration Data. The execution result of this operation is returned in resetEimResult as described below. - Reset the configuration of the automaticimmediate Profile enabling. The execution result of this operation is returned in resetAutoEnableConfigResultresetImmediateEnableConfigResult as described below. Any combination MAY be specified in the request. If the eUICC does not support Test Profiles, then a request to delete them is ignored. The … l interruptions (e.g., power loss): the eUICC SHALL continue the processing of that command upon the next eUICC power on. In case of any other error during the … commandfunction execution, the command SHALL stop and SHALL leave the eUICC and the involved Profiles in their original states prior to commandfunction execution. NOTE: How this commandfunction is protected from misuse is implementation specific. Upon reception of this function call, the eUICCMemoryReseteUICC functionSHALL: andIf dependentthe onEmergency Profile is enabled, terminate the parameterscommand set,and return error code ecallActive. If the eUICCeUICCMemoryReset SHALLfunction call indicates at least one of deleteOperationalProfiles, deleteFieldLoadedTestProfiles, deletePreLoadedTestProfiles or deleteProvisioningProfiles, perform the following: -o If there is an Enabled Profile with a proactive session ongoing, the eUICC SHALL perform one of the following: - terminate the command and return error code catBusy. - internally terminate the proactive session and prepare to send the REFRESH proactive command as the next proactive command. If a TERMINAL RESPONSE is still outstanding, the REFRESH proactive command SHALL only be sent after reception of the TERMINAL RESPONSE. NOTE: In case of the catBusy error, the Device MAY take implementation-dependent action to terminate the proactive command session, and MAY send the eUICC Memory Reset command again without any further End User interaction. -o Delete all the selected ISD-Ps with their Profiles regardless of their enabled status or Profile Policy Rules and all related Profiles Metadata stored in the ISD-R and prepare resetResult. -o For each deleted Profile, the eUICC SHALL generate as many Notifications as configured in its Profile Metadata (notificationConfigurationInfo) in the format of OtherSignedNotification. -If Resetthe eUICCMemoryReset function call indicates resetDefaultSmdpAddress: reset the default SM-DP+ address to its default value. -If Removethe eUICCMemoryReset function call indicates resetEimConfigData: remove all eIM Configuration Data of all Associated eIMs and prepare resetEimResult. -o If there is no eIM Configuration Data to be removed, the eUICC SHALL return error code nothingToDelete. -o If the command is not supported by the eUICC, the eUICC SHALL return error code eimResetNotSupported. -If Resetthe eUICCMemoryReset function call indicates resetImmediateEnableConfig: reset the configuration of the automaticimmediate Profile enabling by deactivating automaticimmediate Profile enabling and removing any automaticimmediate enabling data for use with automaticimmediate Profile enabling. The eUICC SHALL also prepare resetAutoEnableConfigResult.resetImmediateEnableConfigResult. -o If the command is not supported by the eUICC, the eUICC SHALL return error code resetAECNotSupported.resetIECNotSupported. - Return EuiccMemoryResetResponse including resetResult,resetResult. andIn addition, if resetEimConfigDataresetResult and/orindicates resetAutoEnableConfigeither bitsok wereor nothingToDelete: o If resetEimConfigData bit was set in the command data, return EuiccMemoryResetResponse additionally including resetEimResultresetEimResult. and/oro resetAutoEnableConfig,If respectively.resetImmediateEnableConfig -bit Ifwas thereset wasin the command data, return EuiccMemoryResetResponse additionally including resetImmediateEnableConfig. If an Enabled Profile,Profile was deleted, the ISD-R SHALL send a REFRESH proactive command to the Device with mode "UICC Reset". Command Data The command data SHALL be coded as follows: -- ASN1START EuiccMemoryResetRequest ::= [52][100] SEQUENCE { -- Tag 'BF34''BF64' resetOptions [2] BIT STRING { deleteOperationalProfiles(0), deleteFieldLoadedTestProfiles(1), resetDefaultSmdpAddress(2), resetEimConfigData(3),deletePreLoadedTestProfiles(3), resetAutoEnableConfig(4)deleteProvisioningProfiles(4), resetEimConfigData(5), resetImmediateEnableConfig (6) } } -- ASN1STOP Response Data The response data SHALL be coded as follows: -- ASN1START EuiccMemoryResetResponse ::= [52][100] SEQUENCE { -- Tag 'BF34''BF64' resetResult INTEGER {ok(0), nothingToDelete(1), catBusy(5), ecallActive(104), undefinedError(127)}, resetEimResult [1] INTEGER {ok(0), nothingToDelete(1), eimResetNotSupported(2), undefinedError(127)} OPTIONAL, resetAutoEnableConfigResultresetImmediateEnableConfigResult [2] INTEGER {ok(0), resetAECNotSupported(1),resetIECNotSupported (1), undefinedError(127)} OPTIONAL } -- ASN1STOP

5.9.6 Function (ES10b): AuthenticateServermodified

…ices) Description: This function is identical to the ES10b.AuthenticateServer function defined in section 5.7.13 of SGP.22 [4], where the IPA plays the role of … LPA,LPA withand the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification. The following additional eUICC behaviour applies after attaching the received RSP Server Certificate in the RSP session context: - If automaticimmediate Profile enabling is activated, the eUICC SHALLSHALL, in case the MatchingID is missing in CtxParams1, verify that the OID in the RSP Server Certificate and FQDN in serverSigned1 match to the Defaultdefault SM-DP+ data (OID and FQDN) stored in the eUICC. If the verification is successful, the eUICC SHALL grant automaticimmediate enabling of the Profile. Regardless of the verification result, the eUICC continues the processing of this function by generating euiccSigned1.

5.9.9 Function (ES10b): CancelSessionmodified

…o the ES10b.CancelSession function defined in section 5.7.14 of SGP.22 [4], where the IPA plays the role of LPA, with the following additional eUICC behaviour: … - The eUICC SHALL revoke any grant to automaticallyimmediately enable a Profile. NOTE: The following values of CancelSessionReason are not used inthis specification: endUserRejection(0), postponed(1), timeout(2).

5.9.11 Function (ES10b): RetrieveNotificationsListmodified

…ction retrieves the list of pending Notifications for installed Profiles and/or eUICC Package Results. Command Data The command data SHALL be coded as follows: … -- ASN1START RetrieveNotificationsListRequest ::= [43] SEQUENCE { -- Tag 'BF2B' searchCriteria CHOICE { seqNumber [0] INTEGER, profileManagementOperation [1] NotificationEvent, euiccPackageResults [2] NULL } OPTIONAL } -- ASN1STOP The searchCriteria data object can be used to filter the list of Notifications and/oror eUICC Package Results that the eUICC SHALL return. - seqNumber indicates that the eUICC SHALL return either a Notification or an eUICC Package Result that has the sequncesequence number. - A bit set to 1 in the profileManagementOperation indicates that the eUICC SHALL return all the Notifications corresponding to this type. The type notificationInstall SHALL include ProfileInstallationResult. - euiccPackageResults indicates that the eUICC SHALL return all the eUICC Package Results. If searchCriteria data object is omitted, the eUICC SHALL return all stored Notifications andthat eUICCare Packagein Resultsthe informat notificationAndEprList.of PendingNotificationList.. Response Data The response data SHALL contain the list of PendingNotification data objects and/oror EuiccPackageResult data objects. The list SHALL be filtered according to the command data. The eUICC MAY provide the Notifications and/or eUICC Package Results … definition of the RetrieveNotificationsListResponse data object -- ASN1START RetrieveNotificationsListResponse ::= [43] CHOICE { -- Tag 'BF2B' notificationList … SEQUENCEPendingNotificationList, OF-- PendingNotification,Tag 'A0' notificationsListResultError INTEGER { undefinedError(127)}, euiccPackageResultList-- SEQUENCETag OF'81' EuiccPackageResult, notificationAndEprList SEQUENCE { notificationList SEQUENCE OF PendingNotification, euiccPackageResultList SEQUENCEEuiccPackageResultList OF-- EuiccPackageResultTag }'A2' } -- ASN1STOP The PendingNotification is either a ProfileInstallationResult or an OtherSignedNotification according to definition in section 5.7.10 of SGP.22 [4].

5.9.14 Function (ES10b): GetProfilesInfomodified

Related Procedures: Profile Download and Installation Function Provider Entity: ISD-R (IPA Services) Description: This function is identicalbased toon the ES10c.GetProfilesInfo function defined in section 5.7.15 of SGP.22 [4], where the IPA plays the role of LPA. The ProfileInfo data object as defined in SGP.22[4] SHALL be replaced by the definition of the section 4.4 of this document. The section 4.4 describes the additional tags.

5.9.15 Function (ES10b): ImmediateEnablemodified was Function (ES10b): EnableUsingDD

Related Procedures: Profile Download and Installation Function Provider Entity: ISD-R (IPA Services) Description: This function is used by the IPA to request automaticimmediate Profile enabling without eIM involvement. The eUICC MAY be configured to support the automaticimmediate enabling. On reception of this function call, the eUICC SHALL: - Verify that, except for Notification retrieval commands, the previous ES10 commandfunction was an ES10b.LoadBoundProfilePackage. If not, the eUICC SHALL return an error code noSessionContext. - Verify that automaticimmediate enabling was granted for the newly installed Profile. If not, the eUICC SHALL return an error code autoEnableNotAvailable.immediateEnableNotAvailable. -Verify that the target Profile is not an Emergency Profile. If it is an Emergency Profile with ecallIndication set to TRUE, the eUICC SHALL return an error code immediateEnableNotAvailable. If the refreshFlag is not set, the eUICC SHALL then: Check whether there is a proactive session ongoing (which the Device did not terminate). If so: o the eUICC MAY terminate the ImmediateEnable command with error 'catBusy'. o If the eUICC does not terminate the ImmediateEnable command with error 'catBusy', the eUICC SHALL internally terminate the proactive session and ignore any incoming TERMINAL RESPONSE from that proactive session. Close all logical channels which still have an application of the currently Enabled Profile selected (which the IoT Device did not close), without generating an error. Reset the PIN status. Disable the currently Enabled Profile (if any). Enable the newlydownloaded installedProfile. Reset any authorisation previously granted to use the Profile Rollback Mechanism (and any related data). Implicitly select the MF on the basic logical channel. Return 'ok' to the IPA. If the refreshFlag is set: If there is a proactive session ongoing; o The eUICC MAY terminate the ImmediateEnable command with error 'catBusy'. o If the eUICC does not terminate the ImmediateEnable command with error 'catBusy', the eUICC SHALL internally terminate the proactive session and generatesend enablethe NotificationsREFRESH command as configured.the next proactive command. If a TERMINAL RESPONSE is still outstanding, the REFRESH command SHALL only be sent after reception of the TERMINAL RESPONSE. Otherwise, the eUICC SHALL: o Mark the currently Enabled Profile as "to be disabled" (if any). o Mark the target Profile as "to be enabled". o Return 'ok' to the IPA. o Send the REFRESH command in "eUICC Profile State Change" mode (if supported by the IoT Device) or "UICC Reset" mode to the IoT Device according to ETSI TS 102 223 [5]. o Upon reception of the Terminal Response with result "command performed successfully" or upon reset of the eUICC, disable the currently Enabled Profile (if any) and enable the downloaded Profile. o Upon reception of the Terminal Response with result "temporary problem with executing command" or "permanent problem with executing command", the eUICC SHALL NOT disable the currently Enabled Profile (if any) nor enable the downloaded Profile. Subsequent actions are implementation specific. Command Data The command data SHALL be encoded as follows: -- ASN1START EnableUsingDDRequestImmediateEnableRequest ::= [90] SEQUENCE { -- Tag 'BF5A' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP Response Data The response data SHALL be encoded as follows: -- ASN1START EnableUsingDDResponseImmediateEnableResponse ::= [90] SEQUENCE { -- Tag 'BF5A' enableUsingDDResultimmediateEnableResult [0] INTEGER { ok(0), autoEnableNotAvailable(1),immediateEnableNotAvailable (1), noSessionContext(4), catBusy(5), undefinedError(127) } } -- ASN1STOP

5.9.16 Function (ES10b): ProfileRollbackmodified

…f any, that was enabled before the processing of the last eUICC Package. This SHALL be performed in an atomic way, meaning that in case of any error during the … commandfunction execution, the command SHALL stop and SHALL leave the involved Profiles in their original states (prior to commandfunction execution). NOTE: Before calling the ProfileRollback function with the refreshFlag not being set, the IoT Device has the responsibility to ensure that the relevant conditions for use are met, as indicated for the ES10c.EnableProfile function in section 3.2.1 of SGP.22 [4]. In the following procedure, the Targettarget Profile designates the Profile (if any) that was enabled before the processing of the last eUICC Package, and which is to be re-enabled. Upon reception of the ProfileRollback command, the eUICC SHALL: - Check whether the usage of the Rollback Mechanism had been previously granted by the eIM. If not, the procedure SHALL stop, and the result of this commandfunction SHALL indicate an error ('rollbackNotAllowed'). - Check whether a Profile is currently enabled. If not, the procedure SHALL stop, and the result of this commandfunction shall indicate an error ('commandError'). If the refreshFlag is not set, the eUICC SHALL: - Check whether there is a proactive session ongoing (which the Device did not terminate). If so: -o the eUICC MAY terminate the ProfileRollback“ES10b.ProfileRollback” commandfunction with error 'catBusy'. -o If the eUICC does not terminate the ProfileRollback“ES10b.ProfileRollback” commandfunction with error 'catBusy', the eUICC SHALL internally terminate the proactive session and ignore any incoming TERMINAL RESPONSE from that proactive session. - Close all logical channels which still have an application of the currently Enabled Profile selected (which the Device did not close), without generating an error. - Reset the PIN status. - Disable the currently Enabled Profile. - Enable the Targettarget Profile (if any). - Implicitly select the MF on the basic logical channel. - Generate a new eUICC Package Result including an additional ProfileRollbackResult (see Response Data below).below) -and remove the previous eUICC Package Result (which is now obsolete). Return 'ok' and the newly generated eUICC Package Result to the IPA. NOTE: For subsequent actions by the Device following the enablement of the Targettarget Profile, see ES10c.EnableProfile function in section 3.2.1 of SGP.22 [4]. If the refreshFlag is set: - If there is a proactive session ongoing; -o The eUICC MAY terminate the ProfileRollback“ES10b.ProfileRollback” commandfunction with error 'catBusy'. -o If the eUICC does not terminate the ProfileRollback“ES10b.ProfileRollback” commandfunction with error 'catBusy', the eUICC SHALL internally terminate the proactive session and send the REFRESH command as the next proactive command. If a TERMINAL RESPONSE is still outstanding, the REFRESH command SHALL only be sent after reception of the TERMINAL RESPONSE. - Otherwise, the eUICC SHALL: -o Mark the currently Enabled Profile as "to be disabled". -o Mark the Targettarget Profile (if any) as "to be enabled". -o Generate a new eUICC Package Result including an additional ProfileRollbackResult (see Response Data below) -and remove the previous eUICC Package Result (which is now obsolete). o Return 'ok' and the newly generated eUICC Package Result to the IPA. -o Send the REFRESH command in "eUICC Profile State Change" mode (if supported by the Device) or "UICC Reset" mode to the Device according to ETSI TS 102 223 [5]. -o Upon reception of the Terminal Response with result "command performed successfully" or upon reset of the eUICC, disable the currently Enabled Profile and enable the Targettarget Profile (if any). -o Upon reception of the Terminal Response with result "temporary problem with executing command" or "permanent problem with executing command", the eUICC SHALL NOT disable the currently Enabled Profile nor Enable the Targettarget Profile (if any). Subsequent actions are implementation specific. The eUICC MAY start a new proactive UICC session only after a new TERMINAL PROFILE command is executed. - If the currently Enabled Profile was successfully disabled, the eUICC SHALL generate as many Notifications as configured in its metadata (notificationConfigurationInfo) in the format of OtherSignedNotification. - If the Targettarget Profile is successfully enabled, the eUICC SHALL generate as many Notifications as configured in its metadata (notificationConfigurationInfo) in the format of … cmdResult is 'ok' (i.e., a Rollback Mechanism has been executed by the eUICC). In this case, the eUICCPackageResult SHALL include the same eimId, counterValue, … transactionIdeimTransactionId as the result generated for the previous eUICC Package, its seqNumber SHALL be incremented, and its eUICCResultData SHALL include the same PSMO results followe… …

5.9.17 Function (ES10b): ConfigureImmediateProfileEnablingmodified was Function (ES10b): ConfigureAutomaticProfileEnabling

Related Procedures: Configure automaticby ProfileIPA enablingof byImmediate IPA.Profile Enabling. Function Provider Entity: eUICC (ISD-R) Description: This function is used by the IPA to activate or deactivate automaticimmediate Profile enabling in the eUICC and to add or update automaticimmediate enabling data used in the automaticimmediate Profile enabling. Upon reception of this function call, the eUICC SHALL: - Check if any eIM Configuration Data is already present in the eUICC. If so, the eUICC SHALL return an error code unsignedAutoEnableConfigDisallowed.associatedEimAlreadyExists. - Check if autoEnableFlagimmediateEnableFlag is present in the command data. If autoEnableFlagimmediateEnableFlag is present and automaticimmediate Profile enabling is not activated, the eUICC SHALL activate automaticimmediate Profile enabling. If autoEnableFlagimmediateEnableFlag is not present and automaticimmediate Profile enabling is activated, the eUICC SHALL deactivate automaticimmediate Profile enabling. In all other cases, the automaticimmediate Profile enabling state is left unchanged. - Check if automaticdefault enablingSM-DP+ data (smdpOid(defaultSmdpOid andand/or smdpAddressdefaultSmdpAddress) for default SM-DP+) is present in the command data. If so, and if the eUICC has enough memory to store theit, automatic enabling data, the eUICC SHALL store theit automatic enabling data for use in the automaticimmediate Profile enabling. If there is not enough memory, the eUICC SHALL return an error code insufficientMemory. The function SHALL be performed in an atomic way, meaning that in case of any error during the commandfunction execution, the command SHALL stop and SHALL leave the automaticimmediate Profile enabling configuration in its original state prior to commandfunction execution. Command Data The command data SHALL be coded as follows: -- ASN1START ConfigureAutoProfileEnablingRequestConfigureImmediateProfileEnablingRequest ::= [89] SEQUENCE { -- Tag 'BF59' autoEnableFlagimmediateEnableFlag [0] NULL OPTIONAL, smdpOiddefaultSmdpOid [1] OBJECT IDENTIFIER OPTIONAL, smdpAddressdefaultSmdpAddress [2] UTF8String OPTIONAL } -- ASN1STOP Response Data The response data SHALL be coded as follows: -- ASN1START ConfigureAutoProfileEnablingResponseConfigureImmediateProfileEnablingResponse ::= [89] SEQUENCE { -- Tag 'BF59' configAutoEnableResultconfigImmediateEnableResult [0] INTEGER { ok(0), insufficientMemory(1), unsignedAutoEnableConfigDisallowed(2),associatedEimAlreadyExists(2), undefinedError(127) } } -- ASN1STOP

5.9.18 Function (ES10b): GetEimConfigurationDatamodified

…ata stored in the eUICC. Command Data The command data SHALL be coded as follows: -- ASN1START GetEimConfigurationDataRequest ::= [85] SEQUENCE { -- Tag 'BF55' … searchCriteria CHOICE { eimId [0] UTF8String (SIZE(1..128)) } OPTIONAL } -- ASN1STOP The searchCriteria data object can be used to filter the list of eIM Configuration Data that the eUICC SHALL return. eimId is the eIM identifier defined in the section 4.3 of this document. It indicates that the eUICC SHALL return the eIM Configuration Data having the specified eimId. If searchCriteria data object is omitted, the eUICC SHALL return all stored eIM Configuration Data. Response Data The response data SHALL be coded as follows: -- ASN1START GetEimConfigurationDataResponse ::= [85] SEQUENCE { -- Tag 'BF55' eimConfigurationDataList [0] SEQUENCE OF EimConfigurationData } -- ASN1STOP In each EimConfigurationData entry of the eimConfigurationDataList, the eUICC SHALL provide eimId, eimFqdn (if present), eimIdType, trustedPublicKeyDataTls (if present), eimSupportedProtocol, euiccCiPKId (if present) and, if configured, associationToken, and MAY additionally provide either eimPublicKey or eimCertificate. The eUICC SHALL NOT provide counterValue. If there is no eIM Configuration Data stored in the eUICC, or if there is no eIM Configuration Data matching to the searchCriteria (if received), the eUICC SHALL return an empty list in the eimConfigurationDataList.

5.9.20 Function (ES10b): ExecuteFallbackMechanismadded

Function Provider: ISD-R (IPA Services) Function Caller: IPA Description: This function is OPTIONAL for the eUICC and MAY be used by the IPA to instruct the eUICC to enable the Fallback Profile and to disable the currently Enabled Profile. This function SHALL be performed in an atomic way, meaning that in case of any error during the function execution, the command SHALL stop and SHALL leave the involved Profiles in their original states (prior to function execution). Upon reception of this function, the ISD-R SHALL: • verify that there is an enabled Profile. If no, the procedure SHALL stop and the result of this command SHALL indicate error ('commandError(7)'). • verify that the fallbackAttribute is set for a Profile on the eUICC. If not, the procedure SHALL stop, and the result of this command SHALL indicate an error ('fallbackNotAvailable(6)'). • verify that the Emergency Profile is disabled. If it is enabled, the procedure SHALL stop and the result of this command SHALL indicate error ('ecallActive(104)'). • verify that the Fallback Profile is disabled. If not, the procedure SHALL stop, and the result of this command SHALL indicate an error ('profileNotInDisabledState'). If the refreshFlag is not set, the eUICC SHALL: • Check whether there is a proactive session ongoing (which the Device did not terminate). If so: o the eUICC MAY terminate the “ES10b.ExecuteFallbackMechanism” function with error 'catBusy'. o If the eUICC does not terminate the “ES10b.ExecuteFallbackMechanism” function with error 'catBusy', the eUICC SHALL internally terminate the proactive session and ignore any incoming TERMINAL RESPONSE from that proactive session. • Close all logical channels which still have an application of the currently Enabled Profile selected (which the Device did not close), without generating an error. • Reset the PIN status. • Disable the currently Enabled Profile. • Enable the Fallback Profile. • Reset any authorisation previously granted to use the Profile Rollback Mechanism (and any related data). • Implicitly select the MF on the basic logical channel. • Return 'ok' to the IPA. If the refreshFlag is set: • If there is a proactive session ongoing; o The eUICC MAY terminate the “ES10b.ExecuteFallbackMechanism” function with error 'catBusy'. o If the eUICC does not terminate the “ES10b.ExecuteFallbackMechanism” function with error 'catBusy', the eUICC SHALL internally terminate the proactive session and send the REFRESH command as the next proactive command. If a TERMINAL RESPONSE is still outstanding, the REFRESH command SHALL only be sent after reception of the TERMINAL RESPONSE. • Otherwise, the eUICC SHALL: o Mark the currently Enabled Profile as "to be disabled". o Mark the target Fallback Profile as "to be enabled". o Reset any authorisation previously granted to use the Profile Rollback Mechanism (and any related data). o Return 'ok' to the IPA. o Send the REFRESH command in "eUICC Profile State Change" mode (if supported by the IoT Device) or "UICC Reset" mode to the IoT Device according to ETSI TS 102 223 [5]. o Upon reception of the Terminal Response with result "command performed successfully" or upon reset of the eUICC, disable the currently Enabled Profile and enable the target Fallback Profile. o Upon reception of the Terminal Response with result "temporary problem with executing command" or "permanent problem with executing command", the eUICC SHALL NOT disable the currently Enabled Profile nor Enable the targeted Fallback Profile. Subsequent actions are implementation specific. The eUICC MAY start a new proactive UICC session only after a new TERMINAL PROFILE command is executed. • If the currently Enabled Profile was successfully disabled, the eUICC SHALL generate as many Notifications as configured in its metadata (notificationConfigurationInfo) in the format of OtherSignedNotification. • If the Fallback Profile is successfully enabled, the eUICC SHALL generate as many Notifications as configured in its metadata (notificationConfigurationInfo) in the format of OtherSignedNotification. Command Data The command data SHALL be coded as follows: -- ASN1START ExecuteFallbackMechanismRequest ::= [93] SEQUENCE { -- Tag ' BF5D' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP Response Data The response data SHALL be coded as follows: -- ASN1START ExecuteFallbackMechanismResponse ::= [93] SEQUENCE { -- Tag ' BF5D' executeFallbackMechanismResult [0] INTEGER { ok(0), profileNotInDisabledState(2), catBusy(5), fallbackNotAvailable(6), -- Fallback Attribute not set commandError(7), ecallActive(104), undefinedError(127) } } -- ASN1STOP NOTE: It’s IoT Device implementation specific to decide when the IPA calls the ReturnFromFallback function.

The list is shortened; compare the original documents for the remaining changes.

Contents
  1. 1 Introduction
  2. 1.1 Overview
  3. 1.2 Scope
  4. 1.3 Document Purpose
  5. 1.4 Intended Audience
  6. 1.5 Definition of Terms
  7. 1.6 Abbreviations
  8. 1.7 References
  9. 1.8 Conventions
  10. 1.9 References to SGP.22
  11. 2 General Architecture
  12. 2.1 General Architecture
  13. 2.1.1 Architecture Diagram with IPA in the IoT Device
  14. 2.1.2 Architecture Diagram with IPA in the eUICC
  15. 2.1.3 ASN.1
  16. 2.2 Roles
  17. 2.3 Interfaces
  18. 2.4 eUICC Architecture
  19. 2.4.1 eUICC Architecture Diagram
  20. 2.4.2 ECASD
  21. 2.4.3 ISD-R
  22. 2.4.4 ISD-P
  23. 2.4.5 Profile
  24. 2.4.6 Telecom Framework
  25. 2.4.7 Profile Package Interpreter
  26. 2.4.8 IPA in the eUICC
  27. 2.4.9 IPA Services
  28. 2.5 Profile Protection and Delivery
  29. 2.6 Security Overview
  30. 2.6.1 Relation to SGP.22
  31. 2.6.2 IoT Device Security
  32. 2.6.3 TLS Requirements
  33. 2.6.4 eIM Keys and eIM Certificates
  34. 2.6.5 Use of Server Name indication extension (SNI) for ESipa.
  35. 2.7 Certificate Management
  36. 2.7.1 RSP Server Certificates
  37. 2.7.2 eUICC/EUM Certificates
  38. 2.7.3 eIM Certificates
  39. 2.8 Profile Policy Management
  40. 2.9 Profile State Management
  41. 2.9.1 Profile State Management by the eIM
  42. 2.9.2 Immediate Profile enabling of an IPA initiated Profile download from default SM-DP+
  43. 2.10 eIM Configuration
  44. 2.10.1 eIM Configuration by eIM
  45. 2.10.2 eIM configuration by IPA
  46. 2.11 eIM Package Structures
  47. 2.11.1 eIM Package Request
  48. 2.11.2 eIM Package Result
  49. 3 Procedures
  50. 3.1 eIM and IPA Communication
  51. 3.1.1 Transferring eIM Package
  52. 3.1.2 Secure Connection Establishment
  53. 3.2 Profile Download and Installation
  54. 3.2.1 Profile Download Initiation
  55. 3.2.2 Common Mutual Authentication
  56. 3.2.3 Profile Download
  57. 3.3 eUICC Package Handling
  58. 3.3.1 Generic eUICC Package Download and Execution
  59. 3.3.2 Profile Rollback Procedure
  60. 3.4 Profile State Management
  61. 3.4.1 Enable Profile
  62. 3.4.2 Disable Profile
  63. 3.4.3 Delete Profile
  64. 3.4.4 Configure by eIM of Immediate Profile Enabling
  65. 3.4.5 Configure by IPA of Immediate Profile Enabling
  66. 3.4.6 Setting the Fallback Attribute for the target Profile
  67. 3.4.7 Unsetting the Fallback Attribute for the target Profile
  68. 3.5 eIM Configuration at eUICC
  69. 3.5.1 eIM Configuration Data managed by eIM
  70. 3.5.2 eIM Configuration Data managed by IPA
  71. 3.6 Error handling within an RSP session
  72. 3.7 Notification Delivery to Notification Receivers
  73. 3.8 IoT Device and eUICC Initialisation
  74. 3.8.1 eUICC Initialisation
  75. 3.8.2 IoT Device Capabilities
  76. 3.8.3 eUICC File Structure
  77. 3.8.4 ISD-R Selection and IPAe Activation
  78. 3.9 SM-DS Use
  79. 3.9.1 Event Registration
  80. 3.9.2 Event Retrieval
  81. 3.9.3 Event Deletion
  82. 4 Data Elements
  83. 4.1 IPA Capabilities
  84. 4.2 eIM Supported Protocol
  85. 4.3 eIM Identifier
  86. 4.4 Profile MetaData
  87. 5 Functions
  88. 5.1 Overview of Functions per Interface
  89. 5.2 Server to Server Function Commonalities
  90. 5.2.1 Common Data Types
  91. 5.2.2 Request-Response Function
  92. 5.2.3 Notification Handler Function
  93. 5.2.4 Functions Input Header
  94. 5.2.5 Functions Output Header
  95. 5.2.6 Status Code
  96. 5.3 ES2+ (Operator -- SM-DP+)
  97. 5.4 ES6 (Operator -- eUICC)
  98. 5.5 ES8+ (SM-DP+ -- eUICC)
  99. 5.6 ES9+ (IPA -- SM-DP+)
  100. 5.6.1 Function (ES9+): AuthenticateClient
  101. 5.7 ES9+’ (eIM -- SM-DP+)
  102. 5.7.1 Function (ES9+’): InitiateAuthentication
  103. 5.7.2 Function (ES9+’): GetBoundProfilePackage
  104. 5.7.3 Function (ES9+’): AuthenticateClient
  105. 5.7.4 Function (ES9+’): HandleNotification
  106. 5.7.5 Function (ES9+’): CancelSession
  107. 5.8 ES10a (IPA -- eUICC)
  108. 5.8.1 Function (ES10a): GetEuiccConfiguredAddresses
  109. 5.9 ES10b (IPA -- eUICC)
  110. 5.9.1 Function (ES10b): LoadEuiccPackage
  111. 5.9.2 Function (ES10b): GetEUICCInfo
  112. 5.9.3 Function (ES10b): GetEUICCChallenge
  113. 5.9.4 Function (ES10b): AddInitialEim
  114. 5.9.5 Function (ES10b): eUICCMemoryReset
  115. 5.9.6 Function (ES10b): AuthenticateServer
  116. 5.9.7 Function (ES10b): PrepareDownload
  117. 5.9.8 Function (ES10b): LoadBoundProfilePackage
  118. 5.9.9 Function (ES10b): CancelSession
  119. 5.9.10 Function (ES10b): GetCerts
  120. 5.9.11 Function (ES10b): RetrieveNotificationsList
  121. 5.9.12 Function (ES10b): RemoveNotificationFromList
  122. 5.9.13 Function (ES10b): GetRAT
  123. 5.9.14 Function (ES10b): GetProfilesInfo
  124. 5.9.15 Function (ES10b): ImmediateEnable
  125. 5.9.16 Function (ES10b): ProfileRollback
  126. 5.9.17 Function (ES10b): ConfigureImmediateProfileEnabling
  127. 5.9.18 Function (ES10b): GetEimConfigurationData
  128. 5.9.19 Function (ES10b): GetEID
  129. 5.9.20 Function (ES10b): ExecuteFallbackMechanism
  130. 5.9.21 Function (ES10b): ReturnFromFallback
  131. 5.9.22 Function (ES10b): EnableEmergencyProfile
  132. 5.9.23 Function (ES10b): DisableEmergencyProfile
  133. 5.9.24 Function (ES10b): GetConnectivityParameters
  134. 5.9.25 Function (ES10b): SetDefaultDpAddress
  135. 5.10 ES11 (IPA -- SM-DS)
  136. 5.11 ES11’ (eIM -- SM-DS)
  137. 5.11.1 Function (ES11’): InitiateAuthentication
  138. 5.11.2 Function (ES11’): AuthenticateClient
  139. 5.12 ES12 (SM-DS -- SM-DP+)
  140. 5.13 ESep (eIM -- eUICC)
  141. 5.13.1 Function (ESep): Enable
  142. 5.13.2 Function (ESep): Disable
  143. 5.13.3 Function (ESep): Delete
  144. 5.13.4 Function (ESep): ListProfileInfo
  145. 5.13.5 Function (ESep): GetRAT
  146. 5.13.6 Function (ESep): ConfigureImmediateEnable
  147. 5.13.7 Function (ESep): AddEim
  148. 5.13.8 Function (ESep): UpdateEim
  149. 5.13.9 Function (ESep): DeleteEim
  150. 5.13.10 Function (ESep): ListEim
  151. 5.13.11 Function (ESep): SetDefaultDpAddress
  152. 5.14 ESipa (eIM -- IPA)
  153. 5.14.1 Function (ESipa): InitiateAuthentication
  154. 5.14.2 Function: (ESipa) GetBoundProfilePackage
  155. 5.14.3 Function: (ESipa) AuthenticateClient
  156. 5.14.4 Function (ESipa): TransferEimPackage
  157. 5.14.5 Function (ESipa): GetEimPackage
  158. 5.14.6 Function (ESipa): ProvideEimPackageResult
  159. 5.14.7 Function (ESipa): HandleNotification
  160. 5.14.8 Function (ESipa): CancelSession
  161. 6 Interface Binding
  162. 6.1 ESipa interface binding over HTTP
  163. 6.1.1 ASN.1 message definition
  164. 6.1.2 JSON message definition
  165. 6.2 ESipa interface binding over CoAP
  166. 6.3 ESipa function binding in ASN.1
  167. 6.3.1 ASN.1 structures for ESipa messages between IPA and eIM
  168. 6.3.2 ESipa functions provided by eIM
  169. 6.3.3 ESipa functions provided by IPA
  170. 6.4 ESipa function binding in JSON
  171. 6.4.1 List of functions
  172. A IoT Device Requirements (Normative)
  173. A.1 Functional IoT Device Requirements
  174. A.2 Support for CAT Mechanisms
  175. B Mapping of procedures to IoT protocols (Informative)
  176. B.1 LwM2M
  177. B.1.1 Secure connection
  178. B.1.2 LwM2M object
  179. B.1.3 Procedures
  180. B.2 MQTT
  181. B.2.1 Mapping of MQTT Roles
  182. B.2.2 Secure connection
  183. B.2.3 Description
  184. B.2.4 Procedures
  185. C ASN.1 Definitions (Normative)
  186. D Tag allocation (Normative)
  187. E Document Management (Informative)
  188. E.1 Document History

SGP.32 – eSIM IoT Technical Specification

eSIM IoT Technical Specification
                                                     Version 1.1
                                                 26 April 2024

Security Classification: Non-Confidential Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted under the security classification without the prior written approval of the Association.

Copyright Notice Copyright © 2024 GSM Association

Disclaimer The GSMA makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice.

Compliance Notice The information contain herein is in full compliance with the GSMA Antitrust Compliance Policy.

This Permanent Reference Document is classified by GSMA as an Industry Specification, as such it has been developed and is maintained by GSMA in accordance with the provisions set out GSMA AA.35 - Procedures for Industry Specifications.

1 Introduction

1.1 Overview

This document provides a technical description of the GSMA’s eSIM IoT Architecture and Requirements SGP.31 [1] specification.

1.2 Scope

This specification provides a technical description of:

•   The remote provisioning and management of the eUICC in IoT Network Constrained
    and/or User Interface Constrained Devices.
•   The eUICC architecture for IoT Devices.
•   The interfaces used within the eSIM IoT architecture; and
•   The security functions used within the eSIM IoT architecture.

1.3 Document Purpose

This document defines a technical solution for the remote provisioning and management of the eUICC in IoT Devices as defined in eSIM IoT Architecture and Requirements SGP.31 [1]. The adoption of this technical solution will provide the basis for global interoperability between different deployment scenarios supported by the eSIM IoT Architecture and Requirements SGP.31 [1].

1.4 Intended Audience

Technical experts working for Operators, eUICC solution providers, IoT Device vendors, standards organisations, network infrastructure vendors, Mobile Service Providers and IoT service providers and other impacted industry bodies.

1.5 Definition of Terms

Term                          Description
Activation Code               As defined in SGP.22 [4].
Activation Code Token         As defined in SGP.22 [4].
Associated eIM                As defined in SGP.31 [1].
Bound Profile Package         As defined in SGP.31 [1].
Certificate                   Public key certificate.
Certification Authority       An authority which issues public key certificates.
                              A set of data (e.g. APN, login, password, …) required by the IPA
Connectivity Parameters       to open a communication channel (e.g. HTTPS, CoAP) on a
                              dedicated network.
Device Baseband               A device component that manages the cellular radio functions.
eIM Configuration Data        As defined in SGP.31 [1].
eIM Configuration Operation   As defined in SGP.31 [1].
                               Contains an eUICC Package, a request for IPA and/or eUICC
                               data, a Profile download trigger (e.g., containing an Activation
eIM Package
                               Code) or acknowledgements of eUICC Package Results and
                               Notifications.
eIM Package Result             Execution result of an eIM Package.
Emergency Mechanism            As defined in SGP.31 [1].
Emergency Profile              As defined in SGP.31 [1].
eUICC                          As defined in SGP.22 [4].
                               A cryptographically signed package prepared by the eIM that
eUICC Package                  contains either PSMO(s) or eCO(s). The package is verified and
                               executed by the eUICC.
                               A cryptographically signed package prepared by the eUICC that
eUICC Package Result
                               contains the execution result of the eUICC Package.
Event                          As defined in SGP.22 [4].
EventID                        As defined in SGP.22 [4].
Event Deletion                 A process of deleting an Event from an SM-DS by the SM-DP+.
Event Record                   As defined in SGP.22 [4].
Event Registration             As defined in SGP.22 [4].
                               A process of retrieving from the SM-DS any available
Event Retrieval                information for a specific eUICC registered by a specific SM-
                               DP+ or a specific SM-DS.
                               This is an attribute of a Profile which, when set, identifies the
Fallback Attribute
                               Profile to be enabled by the Fallback Mechanism.
                               eUICC-based mechanism which enables and disables the
Fallback Mechanism
                               Profile with Fallback Attribute set.
Fallback Profile               An Operational Profile having the Fallback Attribute set.
Field-Test eUICC               As defined in SGP.22 [4]
IoT                            As defined in SGP.31 [1].
IoT Device                     As defined in SGP.31 [1].
                               Indicates to the eIM what the IPA is capable of related to the
                               functional split of Profile download between the eIM and the IPA
IPA Capabilities
                               and the use of compact data object structures in ESipa
                               functions.
MatchingId                     As defined in SGP.22 [4].
Mobile Service Provider        As defined in SGP.31 [1].
Network Constrained Device     As defined in SGP.31 [1].
Notification                   As defined in SGP.22 [4].
Notification Receivers         As defined in SGP.31 [1].
Operational Profile            As defined in SGP.22 [4].
Operator                       As defined in SGP.22 [4].
Profile                        As defined in SGP.22 [4].
Profile Metadata               As defined in SGP.22 [4].
Profile Package               As defined in SGP.31 [1].
                              An eUICC Operating System service that translates the Profile
Profile Package Interpreter   Package data into an installed Profile using the specific internal
                              format of the target eUICC.
Profile State Management      As defined in SGP.31 [1].
Operation
Provisioning Profile          As defined in SGP.22 [4].
Registered PLMN               As defined in 3GPP TS 23.122 [19].
Rollback Mechanism            As defined in SGP.31 [1].
Root SM-DS                    As defined in SGP.22 [4].
RSP Server                    As defined in SGP.22 [4].
Rules Authorisation Table     As defined in SGP.22 [4].
                              eIM Configuration Operation performed by an Associated eIM
Signed eCO                    using cryptographically signed eIM Configuration Operation that
                              contains the eIM Configuration Data.
Subscription Manager Data
                              As defined in SGP.22 [4].
Preparation
Subscription Manager          As defined in SGP.22 [4].
Discovery Server
                              An eUICC Operating System service that provides standardised
                              network authentication algorithms to the network authentication
Telecom Framework             applications hosted in the ISD-Ps. Furthermore, it provides
                              capabilities to configure the algorithm with necessary
                              parameters in the Enabled Profile.
Test Profile                  As defined in SGP.22 [4].
                              Non-cryptographically signed eIM Configuration Operation of the
Unsigned eCO
                              initial eIM.
User Interface Constrained    As defined in SGP.31 [1].
Device

1.6 Abbreviations

Abbreviation                  Description
CA                            Certification Authority
CoAP                          Constrained Application Protocol.
CRL                           Certificate Revocation List
DTLS                          Datagram Transport Layer Security.
ECASD                         eUICC Controlling Authority Security Domain
eCO                           eIM Configuration Operation
EID                           eUICC-IDentifier as defined in SGP.22 [4]
eIM                           eSIM IoT Remote Manager
eIMID                         eIM Identifier
EUM                           eUICC Manufacturer
IoT                          Internet of Things
IPA                          IoT Profile Assistant
IPAd                         IoT Profile Assistant in the IoT Device
IPAe                         IoT Profile Assistant in the eUICC
ISD-P                        Issuer Security Domain – Profile
ISD-R                        Issuer Security Domain – Root
NCD                          Network Constrained Device
OCSP                         Online Certificate Status Protocol
OTA                          Over The Air
PSMO                         Profile State Management Operation
RAT                          Rules Authorisation Table
RPLMN                        Registered Public Land Mobile Network
SM-DP+                       Subscription Manager Data Preparation +
SM-DS                        Subscription Manager Discovery Server
TLS                          Transport Layer Security.
UICD                         User Interface Constrained Device

1.7 References

          Document
Ref                         Title
          Number
[1]       SGP.31            eSIM IoT Architecture and Requirements, version 1.2
                            Key words for use in RFCs to Indicate Requirement Levels, S.
[2]       RFC 2119
                            Bradner
[3]       RFC 8174          Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
[4]       SGP.22            RSP Technical Specification, version 2.5
[5]       ETSI TS 102 223   Smart Cards; Card Application Toolkit (CAT)
[6]       SGP.02            GSMA Remote Provisioning of Embedded UICC Technical
                            specification version 4.3
[7]       RFC 7252          The Constrained Application Protocol (CoAP)
[8]       RFC 5246          The Transport Layer Security (TLS) Protocol Version 1.2
[9]       RFC 8446          The Transport Layer Security (TLS) Protocol Version 1.3
[10]      RFC 6347          Datagram Transport Layer Security Version 1.2
[11]      RFC 9147          The Datagram Transport Layer Security (DTLS) Protocol Version
                            1.3
[12]      RFC 7959          Block-Wise Transfers in the Constrained Application Protocol
                            (CoAP)
[13]      RFC 9175          Constrained Application Protocol (CoAP): Echo, Request-Tag,
                            and Token Processing
[14]      RFC 9146          Connection Identifier for DTLS 1.2
[15]      RFC 8422            Elliptic Curve Cryptography (ECC) Cipher Suites for Transport
                              Layer Security (TLS) Versions 1.2 and earlier
[16]      RFC 7027            Elliptic Curve Cryptography (ECC) Brainpool Curves for Transport
                              Layer Security (TLS)
[17]      RFC 5289            TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES
                              Galois Counter Mode (GCM)
[18]      RFC 8410            Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for
                              Use in the Internet X.509 Public Key Infrastructure
                              3rd Generation Partnership Project;
                              Technical Specification Group Core Network and Terminals;
[19]      3GPP TS 23.122
                              Non-Access-Stratum (NAS) functions related to Mobile
                              Station (MS) in idle mode
[20]      RFC 5077            Transport Layer Security (TLS) Session Resumption without
                              Server-Side State
[21]      RFC 6960            X.509 Internet Public Key Infrastructure Online Certificate Status
                              Protocol – OCSP
                              3rd Generation Partnership Project;
                              Technical Specification Group Core Network and Terminals;
[22]      3GPP TS 24.008      Mobile radio interface Layer 3 specification;
                              Core network protocols;
                              Stage 3
[23]      MQTTs               MQTTs version 5.0 based on TLS
[24]      RFC 5639            Elliptic Curve Cryptography (ECC) Brainpool Standard Curves
                              and Curve Generation
[25]                          Internet X.509 Public Key Infrastructure Certificate and Certificate
          RFC 5280
                              Revocation List (CRL) Profile
[26]                          Avis relatif aux paramètres de courbes elliptiques définis par l'Etat
          ANSSI ECC           français. JORF n°0241 du 16 octobre 2011 page 17533. texte n°
                              30. 2011
[27]      RFC 5480            Elliptic Curve Cryptography Subject Public Key Information
[28]                          IT Security techniques — Digital signatures with appendix — Part
          ISO 14888-3
                              3: Discrete logarithm-based mechanisms
[29]      TCA                 eUICC Profile Package: Interoperable Format Technical
          eUICC Profile       Specification
          Package
[30]      OMA LwM2M           OMA LwM2M Object and Resource Registry :
          Object and
          Resource            https://technical.openmobilealliance.org/OMNA/LwM2M/Lw
          Registry            M2MRegistry.html
[31]      RFC 2818            HTTP Over TLS.
[32]      GPC_SPE_034         GlobalPlatform Technology Card Specification v2.3.1
[33]      GPD_SPE_075         GlobalPlatform Technology Open Mobile API Specification v3.3
[34]                          Smart Cards; UICC-Terminal interface; Physical and logical
          ETSI 102 221
                              characteristics
[35]      RFC 6066            Transport Layer Security (TLS) Extensions: Extension Definitions
[36]      RFC 7159         The JavaScript Object Notation (JSON) Data Interchange Format

1.8 Conventions

“The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 [2] and clarified by RFC 8174 [3], when, and only when, they appear in all capitals, as shown here.”

1.9 References to SGP.22

The present document contains several references to SGP.22 [4]. The following list maps the terms used by SGP.22 [4] to the terms used in the present document: • LPA (Local Profile Assistant) refers to IPA.

2 General Architecture

This section contains a technical description and architecture of the eSIM IoT system for IoT Devices. The statements in this section define the basic characteristics that need to be taken into account when reviewing this specification.

2.1 General Architecture

This section further specifies the roles and interfaces associated with the Remote SIM Provisioning and Management of the eUICC for IoT Devices.

2.1.1 Architecture Diagram with IPA in the IoT Device

This section further specifies the roles and interfaces associated with the Remote SIM Provisioning and Management with the IPA in the IoT Device (Figure 1).

ES12                             SM-DP+                                ES2+           Operator
                                                   ES9+’
                                                                      ES9
SM-DS                                           ES8+                  +
                                                                    ES8+
              ES11’
                         eSIM IoT remote Manager

ESipa

ES6

                                       ES8+           ES8
ES11                                                  +
                                    ESep                    IPAd
ES10a                    ES10b

ISD-R

ISD-P

eUICC                      MNO-SD
 IoT
Device
Figure 1        eSIM IoT Functional Architecture (IPA in the IoT Device)

2.1.2 Architecture Diagram with IPA in the eUICC

This section further specifies the roles and interfaces associated with the Remote SIM
Provisioning and Management with the IPA in the eUICC (Figure 2).
                                    ES12
                                                                       SM-DP
                                                                    SM-DP+                                    ES2+          Operator
                                                 ES9+’
SM-DS                                      ES8+                      ES9+
ES11’                                                   ES8+
                    eSIM IoT remote Manager

ESipa

ESep                                                             ES6
ES8+                  ES8+
                                                         ES8+ IPAe
ES11                                      ES8+

ISD-R

                           ISD-P
                         MNO-SD
eUICC

IoT Device

Figure 2     eSIM IoT Functional Architecture (IPA in the eUICC)

2.1.3 ASN.1

The description of some data objects in this specification is based on ASN.1 specified in ITU-T X.680 [49] and encoded in TLV structures using DER (Distinguished Encoding Rule) encoding as specified in ITU-T X.690 [50]. This provides a flexible description of those data objects.

Data structures in these specifications are defined in a single, self-contained, ASN.1 definition module called SGP32Definitions, with an ISO Object Identifier in the GSMA namespace. A number of definitions are imported from the RSPDefinitions module defined in SGP.22 [4]. -- ASN1START SGP32Definitions {joint-iso-itu-t(2) international-organizations(23) gsma(146) rsp(1) asn1modules(1) sgp32v1(31)} DEFINITIONS AUTOMATIC TAGS EXTENSIBILITY IMPLIED ::= BEGIN

IMPORTS Certificate, SubjectPublicKeyInfo FROM PKIX1Explicit88 {iso(1) identified- organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id- pkix1-explicit(18)} SubjectKeyIdentifier FROM PKIX1Implicit88 {iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-pkix1-implicit(19)} CancelSessionReason, ServerSigned1, RspCapability, Iccid, TransactionId, ProfileInfoListRequest, RulesAuthorisationTable, EUICCInfo1, DeviceInfo, VersionType, UICCCapability, PprIds, CertificationDataObject, Octet1, Octet16, Octet32, PrepareDownloadResponseOk, PrepareDownloadResponseError, AuthenticateResponseError, CtxParams1, ProfileInstallationResultData, OtherSignedNotification, EuiccSignPIR, ErrorResult, NotificationMetadata, CancelSessionResponseOk, SmdpSigned2, BoundProfilePackage, NotificationEvent, VendorSpecificExtension, DpProprietaryData, OperatorId, NotificationConfigurationInformation, ProfileClass, IconType, ProfileState, OctetTo16 FROM RSPDefinitions {joint-iso-itu-t(2) international-organizations(23) gsma(146) rsp(1) asn1modules(1) sgp22v2(2)}; -- ASN1STOP Two encoding/decoding attributes are defined:

•   AUTOMATIC TAGS means that the tags are defined automatically using the
    encoding rules unless a tag notation is present in a data object format definition.
•   EXTENSIBILITY IMPLIED means that types MAY have elements that are not defined
    in this specification. This means that decoders SHALL be able to handle values with
    unspecified tags, either by processing them if they know their value content or
    ignoring them silently (without reporting an error) if they do not know them. This is
    useful when processing data definitions from a newer specification and to handle
    proprietary tag values.

As the eUICC cannot implement an off-the-shelf standard decoder, the requirement on extensibility SHALL NOT apply to the eUICC.

2.2 Roles

Roles are defined within SGP.31 [1] section 3.

2.3 Interfaces

The following table provides information about the interfaces within the architecture.

Interface Between                      Description
ES2+         Operator   SM-DP+         Used by the Operator to order Profiles for specific eUICCs
                                       as well as other administrative functions as defined in
                                       SGP.31 [1].
ES6          Operator   eUICC          Used by the Operator for the management of Operator
                                       services via OTA services as defined in SGP.31 [1].
ES8+         SM-DP+     eUICC          Provides a secure end-to-end channel between the SM-DP+
                                       and the eUICC for the administration of the ISD-P and the
                                       associated Profile during download and installation. It
                                       provides Perfect Forward Secrecy as defined in SGP.31 [1].
ES9+         SM-DP+     IPA            Used to provide a secure transport between the SM-DP+
                                       and the IPA for the delivery of the Bound Profile Package as
                                       defined in SGP.31 [1].
ES9+’        SM-DP+     eIM            Used to provide a secure transport between the SM-DP+
                                       and the eIM for the delivery of the Bound Profile Package as
                                       defined in SGP.31 [1].
ES10a        IPA        eUICC          Used between the IPA (in the IoT Device) and the eUICC to
                                       handle a Profile discovery as defined in SGP.31 [1].
ES10b        IPA        eUICC          Used between the IPA (in the IoT Device) and the IPA
                                       Services to transfer a Bound Profile Package to the eUICC
                                       as defined in SGP.31 [1]. This interface plays no role in the
                                       decryption of Profile Packages.
ES11         IPA        SM-DS          Used by the IPA to retrieve Event Records for the respective
                                       eUICC as defined in SGP.31 [1].
ES11’        eIM        SM-DS          Used by the eIM to retrieve Event Records for the respective
                                       eUICC as defined in SGP.31 [1].
ES12         SM-DP+     SM-DS          Used by the SM-DP+ to issue or remove Event Registrations
                                       on the SM-DS as defined in SGP.31 [1].
ESep         eIM        eUICC          Logical end-to-end interface between the eIM and the
                                       eUICC used to transfer eUICC Packages for Profile State
                                       management and eIM configuration by eIM, as defined in
                                       SGP.31 [1].
ESipa        eIM        IPA            Logical interface between an eIM and an IPA, as defined in
                                       SGP.31 [1], used to trigger a Profile download at the IPA
                                       and to provide a secure transport for the delivery of eUICC
                                       Packages, unless the underlying transport provides
                                       necessary security.

Table 1 Interfaces

NOTE:Support of the ES10c interface as defined in SGP.22 [4] is out of scope of this specification.

2.4 eUICC Architecture

This section describes the internal high-level architecture of the eUICC.

NOTE:The eUICC architecture is very similar to that used in SGP.22 [4].

2.4.1 eUICC Architecture Diagram

The IPA SHALL be located either in the IoT Device (IPAd) or in the eUICC (IPAe).

2.4.1.1 eUICC Architecture Diagram (IPA in the IoT Device)

The following diagram represents the eUICC architecture when the IPA is located in the IoT Device.

                                                                    the IoT Device
To Operator

To SM-DP+

                                                                         To IPA in
                                                             To eIM
ES6                     ES8+                          ESep            ES10a,b
eUICC
Operating
System
                                                                                                                                                    Profile
                        ISD-P                                                ISD-P                                                                   Policy
                                                                                                                      IPA                           Enabler
                  MNO-SD                                           MNO-SD                                           Services
                                                                                                            ISD-R                                 Profile
   File System
                                                                                                                        Package
                        File System
Applets

CASD

                                                              Applets
NAAs
                                                                  CASD
SSD
                                                                              Interpreter
NAAs

SSD

ECASD

                                                                                                                                              Telecom
                                                                                                                                             Framework
Operator Disabled Profile                      Operator Enabled Profile
Figure 3                     Schematic Representation of the eUICC (IPA in the Device)

2.4.1.2 eUICC Architecture Diagram (IPA in the eUICC)

The following diagram represents the eUICC architecture when the IPA is located in the eUICC.

                                                                                         To SM-DP+
To Operator

To SM-DP+

                            To SM-DS
To eIM

To eIM

                              ES9+
ESipa
                                                                        ES11
                                                ESep
ES6                           ES8+
eUICC
Operating
System
                      ISD-P                                                                                                   IPA in the                                     Profile Policy
                                                                        ISD-P                                                  eUICC                                           Enabler
                     MNO-SD                                          MNO-SD
                                                                                                                          IPA                                                   Profile
                                                                                                                        Services
File System
                                                                                                                                                        Package
                         File System
Applets

CASD

                                                                     Applets                                                                                    Interpreter
NAAs
                                                                        CASD
                            NAAs
SSD
SSD
                    ISD-R
                                                                                  Telecom
                     ECASD                                                       Framework
Operator Disabled Profile                        Operator Enabled Profile
Figure 4                          Schematic Representation of the eUICC (IPA in the eUICC)

2.4.2 ECASD

The eUICC Controlling Authority Security Domain (ECASD) as defined in SGP.22 [4].

2.4.3 ISD-R

The ISD-R as defined in SGP.22 [4].

2.4.4 ISD-P

The ISD-P entity as defined in SGP.22 [4].

In addition to the current ISD-P as defined in SGP.22, the Connectivity Parameters MAY be included as per Table 93 from SGP.02 [6], with the exception of parameters related to SMS, and Table 95 from SGP.02 [6].

2.4.5 Profile

The Profile as defined in SGP.22 [4].

2.4.5.1 Operational Profile

The Operational Profile as defined in SGP.22 [4].

2.4.5.2 Provisioning Profile

The Provisioning Profile as defined in SGP.22 [4].

2.4.5.3 Test Profile

The Test Profile as defined in SGP.22 [4].

2.4.6 Telecom Framework

The Telecom Framework as defined in SGP.22 [4].

2.4.7 Profile Package Interpreter

The Profile Package Interpreter as defined in SGP.22 [4].

2.4.8 IPA in the eUICC

The IPAe is a functional element which provides similar features as those provided by the IPA in the IoT Device. The implementation of IPAe is OPTIONAL.

The technical implementation of the IPAe is EUM-specific.

2.4.9 IPA Services

This role provides the necessary access to the services and data required by functions of the IPA. These services include:

•   Provide the address of the Root SM-DS and (if configured) the default SM-DP+
•   Transfer Bound Profile Package from the IPAd to the ISD-P
•   Provide list of installed Profiles and their Profile Metadata
•   Retrieve EID
•   Provide Profile State Management Operations
•   Provide eUICC execution results and Notifications.

2.5 Profile Protection and Delivery

An Operator’s Profile is protected within a Profile Package prior to being downloaded to the eUICC as defined in section 2.5 of SGP.22 [4].

2.6 Security Overview

2.6.1 Relation to SGP.22

This specification SHALL re-use the overall security features specified in SGP.22 [4] section 2.6, unless otherwise specified.

2.6.2 IoT Device Security

IoT Devices will be located in a wide variety of environments. It is a basic assumption that in addition to the measures described in this specification, these IoT Devices will have adequate security measures applied in order to provide whatever protection is required to satisfy the security policy for the use-case. Descriptions of these additional measures are out of scope of this specification.

2.6.3 TLS Requirements

TLS v1.2 as defined in RFC 5246 [8] SHALL be the minimal version for any TLS connection in this specification. DTLS v1.2 as defined in RFC 6347 [10] SHALL be the minimal version for any DTLS connection in this specification.

2.6.3.1 TLS Requirements for communication to the RSP Servers

For communication with SM-DP+ and SM-DS, all the TLS requirements defined in section 2.6.6 and 6.1 (and its subsections) of SGP.22 [4] SHALL apply, where the IPA plays the role of the LPA. In addition, the following requirements apply:

•TLS with server authentication SHALL be used over ES9+’ (eIM with SM-DP+), and ES11’ (eIM with SM-DS).

NOTE:Here the eIM is playing the role of the LPA.

•TLS with mutual authentication MAY be used over ES2+. If TLS with mutual authentication is not used over ES2+, ES2+ SHALL be protected with level of security equivalent to TLS.

2.6.3.2 TLS/DTLS Requirements for communication to the eIM

NOTE:The following TLS/DTLS requirements for communication with the eIM applies to section 3.1.2.1 and 3.1.2.2.

TLS v1.3 as defined in RFC8446 [9] and DTLS v1.3 as defined in RFC 9147 [11] MAY be supported for the communication over ESipa (IPA with eIM).

TLS with server authentication SHALL be used. The client (e.g., IPA) either directly trusts the server (i.e., eIM) Certificate or public key, or trusts the CA to which the server Certificate chains back or trusts an intermediate CA along the path.

The following elliptic curve(s) SHALL be supported: • NIST P-256 with the namedCurve secp256r1 (23) as defined in RFC 8422 [15]

The following elliptic curves MAY be supported:
   • brainpoolP256r1(26) as defined in RFC 7027 [16],
   • NIST P-384 with the namedCurve secp384r1 (24) as defined in RFC 8422 [15],
   • Ed25519 as defined in RFC 8410 [18], and x25519 with the namedCurve x25519
        (29) as defined in RFC 8422 [15]
The following cipher suites SHALL be supported:
   • For (D)TLS 1.2
           o TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as defined in RFC
               5289 [17]
           o TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 as defined in RFC
               5289 [17]
   • For (D)TLS 1.3
           o TLS_AES_128_GCM_SHA256 as defined in TLS 1.3 (RFC 8446 [9])
           o TLS_AES_256_GCM_SHA384 as defined in TLS 1.3 (RFC 8446 [9])
The following cipher suites MAY be supported:
   • For (D)TLS 1.2
        o  TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 as defined in RFC 5289
           [17]
•   For (D)TLS 1.3
o   TLS_CHACHA20_POLY1305_SHA256 as defined in TLS 1.3 (RFC 8446 [9])

2.6.4 eIM Keys and eIM Certificates

2.6.4.1 eIM Keys and eIM Certificates Naming Conventions

The eIM keys and eIM Certificates used in this specification are named according to the
conventions described in this section.
The general name structure is: <XX>. <YY>. <ZZ>
Where:
   •     <XX> designates the nature of the element, the following values are defined:
            o   PK: the public key of an asymmetric key pair
            o   SK: the private key of an asymmetric key pair
            o   CERT: a Certificate containing a public key
   •     <YY> designates the owner of the element, the following values are defined:
            o   EIM: an eIM
   •     <ZZ> designates the usage of the element, the following values are defined:
            o   ECDSA: for a digital signature
            o   TLS: for TLS connection establishment
            o   DTLS: for DTLS connection establishment
Examples:
   -     PK.EIM.ECDSA: Public key of an eIM, used to verify an eIM signature.
   -     CERT.EIM.TLS: Certificate of the eIM, used to establish TLS connection.

2.6.4.2 Algorithms and Parameters for eIM Signing Key

This section provides the values to be set in 'AlgorithmIdentifier.algorithm' and 'AlgorithmIdentifier.parameters' fields of the eIM signing key for each of the algorithms used in this specification.

For section 'subjectPublicKeyInfo' the following settings SHALL apply:

'AlgorithmIdentifier.algorithm' field SHALL be set to: "iso (1) member-body (2) us (840) ansi- X9-62(10045) keyType (2) ecPublicKey (1)" as defined in RFC 5480 [27], or

'AlgorithmIdentifier.parameters' field SHALL be set to:

•for BrainpoolP256r1: "iso (1) identified-organization (3) teletrust (36) algorithm (3) signatureAlgorithm (3) ecSign (2) ecStdCurvesAndGeneration (8) ellipticCurve (1) versionOne (1) brainpoolP256r1 (7)" as defined in RFC 5639 [24]

•for NIST P-256: "iso (1) member-body (2) us (840) ansi-X9-62 (10045) curves (3) prime (1) prime256v1(7)" as defined in RFC 5480 [27]

2.6.4.3 eIM Signing Certificate (CERT.EIM.ECDSA)

This specification supports X.509 certificate format as defined in RFC 5280 [25].

The table below describes the common fields that a CERT.EIM.ECDSA SHALL contain.

Certificate common fields
Field                Value Description
tbsCertificate       Data to be signed
                     Field                   Value Description
                     version                 Version SHALL be 3.
                     serialNumber            Certificate serial number.
                     signature               Contains the algorithm identifier used to compute the
                                             value of the field 'signatureValue'.
                                             NOTE: The algorithm identifier value SHALL be the
                                             same as the one of the field 'signatureAlgorithm'.
                     issuer                  Distinguished Name of the entity that has signed the
                                             certificate.
                     validity                Validity period of the eIM Certificate.
                     subject                 Distinguished Name of the entity owning the
                                             certificate. The following DN components SHALL be
                                             used:
                                             CN=<eIMiD> -- mandatory
                                             C=<country code> -- mandatory
                                             O=<company> -- optional
                                             OU=<organizational unit> -- optional
                                             L=<locality> -- optional
                     subjectPublicKeyInfo    Contains the algorithm identifier, parameters, and
                                             public key value.
                                             Algorithm identifier and parameters SHALL be set
                                             according to section 2.6.4.2
                                             subjectPublicKeyInfo.subjectPublicKey contains the
                                             public key value and SHALL be coded as defined in
                                             RFC 5480 [27].
                     Extension for           extnID = id-ce-authorityKeyIdentifier
                     Authority Key           critical = false
                     Identifier (RFC 5280    extnValue = <Identifier of the public key to verify this
                     [25] section 4.2.1.1)   certificate>
                                             To identify the CA public key that has to be used to
                                             verify this certificate.
                     Extensions for Key      Extension for Key usage (RFC 5280 [25] section
                     Usage (RFC 5280         4.2.1.3):
                     [25] section 4.2.1.3)   extnID = id-ce-keyUsage
                                             critical = true
                                             extnValue = digitalSignature (0)
                     Other extensions       CRL and OCSP SHOULD NOT be defined, since the
                                            eUICC will have no means to access those.
                                            Policies SHOULD NOT be defined since they will
                                            increase the certificate size.
                                            Subject Alternative Names SHOULD NOT be
                                            specified.
signatureAlgorithm   Section 2.6.4.2
signatureValue       Signature computed accordingly to one of the possible algorithms listed in
                     section 2.6.4.2

Table 2 eIM Certificate fields

2.6.4.4 eIM TLS/DTLS Certificate (CERT.EIM.TLS)

This specification supports X.509 certificate format as defined in RFC 5280 [25].

The table below describes the common fields that a CERT.EIM.TLS or CERT.EIM.DTLS SHALL contain.

NOTE:If the eIM supports both TLS and DTLS, it may use the same certificate.

Certificate common fields
Field                Value Description
tbsCertificate       Data to be signed
                     Field                  Value Description
                     version                Version SHALL be 3.
                     serialNumber           Certificate serial number.
                     signature              Contains the algorithm identifier used to compute the
                                            value of the field 'signatureValue'.
                                            NOTE: The algorithm identifier value SHALL be the
                                            same as the one of the field 'signatureAlgorithm'.
                     issuer                 Distinguished Name of the entity that has signed the
                                            certificate.
                     validity               Validity period of the eIM TLS/DTLS Certificate.
                     subject                Distinguished Name of the entity owning the
                                            certificate. The following DN components SHALL be
                                            used:
                                            CN=<eIMiD> -- mandatory
                                            C=<country code> -- mandatory
                                            O=<company> -- optional
                                            OU=<organizational unit> -- optional
                                            L=<locality> -- optional
subjectPublicKeyInfo    Contains the algorithm identifier, parameters, and
                        public key value.
                        Algorithm identifier and parameters SHALL be set
                        according to section 2.6.4.2
                        subjectPublicKeyInfo.subjectPublicKey contains the
                        public key value and SHALL be coded as defined in
                        RFC 5480 [27].
Extension for           extnID = id-ce-authorityKeyIdentifier
Authority Key           critical = false
Identifier (RFC 5280    extnValue = <Identifier of the public key to verify this
[25] section 4.2.1.1)   certificate>
                        To identify the CA public key that has to be used to
                        verify this certificate.
Extensions for Key      Extension for Key usage (RFC 5280 [25] section
Usage (RFC 5280         4.2.1.3):
[25] section 4.2.1.3)   extnID = id-ce-keyUsage
                        critical = true
                        extnValue = digitalSignature (0)
Extensions for          extnID = id-ce-subjectAltName
subjectAltName
                        critical = false
(RFC 5280 [25]
section 4.2.1.6):       extnValue = GeneralNames ::= {
                        {
                        dNSName '<eIM hostname (FQDN) value>'
                        },
                        {
                        registeredID '<eIM OID value>'
                        }
                        }
                        This extension SHALL contain at least one dNSName
                        entry, and only one registeredID entry.
                        A dNSName entry MAY contain the wildcard
                        character * as allowed by RFC 2818 [31].
                      Extension for          Extension for Extended Key usage (RFC 5280 [25]
                      extendedKeyUsage       section 4.2.1.12):
                      (RFC 5280 [25]         extnID = id-ce-extKeyUsage
                      section 4.2.1.12)      critical = true
                                             extnValue = ExtKeyUsageSyntax ::{
                                                 {
                                                 id-kp-serverAuth
                                                 },
                                                 {
                                                 id-kp-clientAuth
                                                 }
                                             }
                                             Certificate SHALL not contain any other extended
                                             key usage.
                      Other extensions       Extension for CRL Distribution Points (RFC 5280 [25]
                                             section 4.2.1.13).
                                             Policies SHOULD NOT be defined since they will
                                             increase the certificate size.
signatureAlgorithm    Section 2.6.4.2
signatureValue        Signature computed accordingly to one of the possible algorithms listed in
                      section 2.6.4.2

Table 3 eIM TLS/DTLS Certificate fields

2.6.5 Use of Server Name indication extension (SNI) for ESipa.

Server Name Indication, often abbreviated SNI, is an extension for TLS protocol. This extension allows multiple hostnames and consequently multiple TLS certificates to be served over HTTPS from the same IP address.

This capacity could be useful for the eIM server to select the right TLS certificate chain that IPA is able to verify.

This section provides to the IPA and the eIM Server a mechanism to guide the eIM Server selection of an appropriate TLS certificate chain.

The eIM Server and the IPA SHOULD support this mechanism. An eIM Server and an IPA that support this mechanism SHALL comply with this section.

IPA/Device side:

An IPA SHALL perform a DNS resolution using the eIM FQDN registered during the eIM association, then IPA SHALL proceed with the TLS handshake including the "server_name" extension defined in RFC 6066 [35] in the ClientHello containing the eIM FQDN. If the eIM Server replies with a fatal-level alert different from unrecognized_name(112), the IPA SHALL retry the TLS handshake without sending the Server Name indication extension.

NOTE:This section is also applicable to the IPAe.

eIM Server side:

The eIM Server SHALL take care that its domain names in their final encoding do not violate the length limits of domain names.

The eIM Server SHALL support the "server_name" extension to determine the TLS certificate to use.

•If the received ClientHello message contains the "server_name" extension with an unrecognized FQDN, the eIM Server SHALL abort the handshake by sending a fatal- level unrecognized_name(112) alert.

•If the received ClientHello message doesn't contain the "server_name" extension, the eIM Server SHOULD use a TLS certificate associated with a default domain.

2.7 Certificate Management

2.7.1 RSP Server Certificates

The RSP Server Certificate management and verification SHALL follow what is specified in SGP.22 [4].

2.7.2 eUICC/EUM Certificates

The RSP Certificate revocation management as defined in SGP.22 [4] does not apply to the eUICC. Therefore, the revocation management is not supported by the eUICC and the IPA or eIM SHALL NOT pass any revocation information (CRL, OCSP) to the eUICC.

The eUICC Certificates (i.e., CERT.EUICC.ECDSA) according to SGP.22 [4] SHALL be used. A Field-Test eUICC MAY contain certificates that chain up to the GSMA CI for the purpose of integration and/or end-to-end testing, as defined in SGP.22 [4].

2.7.3 eIM Certificates

The following Certificates MAY be supported, and MAY be revoked at any time:

•   eIM Certificate for signing eUICC Packages (if any)
•   eIM DTLS/TLS Certificate (if any)

The issuance, verification and revocation of eIM Certificates for signing eUICC Packages are implementation specific and out of scope of this specification.

If an eIM utilizes DTLS/TLS for ESipa protection, the eIM SHALL use a Certificate or Public Key. The eIM DTLS/TLS Certificate (if any) or the CA that issues the eIM DTLS/TLS Certificate SHALL be trusted by the IPA. This CA MAY be public or private. In case of TLS, there SHALL be means for the IPAd to check the revocation status of this Certificate either through CRL or OCSP [21] made available by the issuing CA. The eIM MAY provide OCSP stapling. In case of DTLS, revocation status SHALL NOT be checked.

NOTE:For constrained IoT Devices, a private CA allows for flexibility in configuring how many sub CA layers are utilized or in defining the CA lifecycle.

A Certificate listed in a CRL SHALL be considered as definitively revoked (i.e., the 'Hold' state is not considered).

2.8 Profile Policy Management

Profile Policy Management provides mechanisms by which Profile Owners can enforce the conditions of use under which services are provided. Please refer to section 2.9 of SGP.22 [4] for details on this.

2.9 Profile State Management

Profile State Management Operation is related to the state update of a Profile in a dedicated ISD-P on the eUICC (e.g.: enable Profile, disable Profile, delete Profile, list Profile information).

2.9.1 Profile State Management by the eIM

Profile State Management is performed by an eIM. For this purpose, the eIM SHALL prepare a signed eUICC Package. For Profile State Management, an eUICC Package contains one or more PSMOs.

The eUICC Package is provided from the eIM to the IPA via ESipa. IPA transfers the eUICC Package to the eUICC via ES10b. The eUICC verifies the signature of the eUICC Package and, upon successful verification, executes the eUICC Package and generates a signed eUICC Package Result. The eUICC Package Result is provided to the IPA that provides it to the eIM. The eIM verifies the signature of the eUICC Package Result before processing the execution result of the eUICC Package.

All the procedure of Profile State Management by the eIM are described in section 3.4.

2.9.2 Immediate Profile enabling of an IPA initiated Profile download from default SM-DP+

The IPA MAY initiate a Profile download request towards the eUICC by instructing the use of the default SM-DP+. Subsequent to successful download and installation, the IPA MAY also request the eUICC to enable this newly downloaded Profile. The eUICC MAY be configured to support the immediate enabling:

•   by EUMs during eUICC manufacturing, or
•   by an Associated eIM via PSMO, or
•   by the IPA via ES10b only if there is no Associated eIM.

If immediate enabling is not configured within the eUICC, the request for immediate Profile enabling SHALL be rejected.

An eUICC configured to support the immediate enabling and requested by IPA to immediately enable a particular Profile, SHALL verify that the OID and FQDN of the SM-DP+ from where the Profile is downloaded match to the default SM-DP+ data (OID and FQDN) stored in the eUICC (see section 3.2.3.1). The storage of the default SM-DP+ data MAY be performed according to the following options:

•   by EUMs during eUICC manufacturing, or
•   by an Associated eIM via PSMO, or

•by the IPA via ES10b only if there is no Associated eIM.

NOTE:SM-DS triggered Profile download and immediate enabling without signed PSMO from any potentially Associated eIM is not specified in this version of the specification.

2.10 eIM Configuration

In order to perform Profile State Management Operation on a given eUICC, an eIM SHALL be associated with this eUICC. For every Associated eIM the eUICC stores the eIM Configuration Data (see section 2.11.1.1.1) that is used by the eUICC for verification of signed PSMOs and Signed eIM Configuration Operations as part of eUICC Package(s).

eIM Configuration Operations MAY be performed at different stages within the eUICC or IoT Device life cycle as described in SGP.31 [1].

NOTE:Annex B of SGP.31 [1] describes the different eIM Configuration scenarios.

2.10.1 eIM Configuration by eIM

If an eUICC has an Associated eIM, only Signed eIM Configuration SHALL be accepted by the eUICC after successful verification of the signature of the Associated eIM. Any Unsigned eCO SHALL be rejected by the eUICC.

When an eUICC has one or more Associated eIMs, a signed eUICC Package SHALL be prepared by one of the Associated eIM to make changes to the eIM Configuration Data of the eUICC. The signed eUICC Package SHALL be transferred from the eIM to the IPAd via ESipa (see also Annex B.5 of SGP.31 [1]) and further to the eUICC where it will be processed. The details are described in section 3.5.1.

The signed eUICC Package contains one or more eIM Configuration Operations. The following eIM Configuration Operations MAY be supported by the eIM and SHALL be supported by the eUICC:

•addEim: Adds an Associated eIM to the eUICC by providing its eIM Configuration Data including the eimID to the eUICC.

•deleteEim: Deletes an Associated eIM identified by its eimID from the eUICC. If the successfully deleted Associated eIM was the last available Associated eIM, the eUICC SHALL allow ES10b.AddInitialEim again.

•updateEim: Updates eIM Configuration Data, i.e., the public key or Certificate and the related anti-replay counter value of an Associated eIM with a given eimID within the eUICC while keeping the same eimID.

•listEim: Requests the eUICC to provide a list of all currently configured Associated eIMs to the eIM.

NOTE1:Replacing an existing Associated eIM with a new Associated eIM could be realized by first adding a new Associated eIM and then deleting the existing Associated eIM.

NOTE2:How the eIM triggers the IPA is out of scope of this specification.

2.10.2 eIM configuration by IPA

If an eUICC does not have an Associated eIM, the eUICC SHALL accept Unsigned eCO.

To enable Unsigned eCO, the IPAd MAY and the eUICC SHALL support the following function:

•ES10b.AddInitialEim: Adds eIM Configuration Data of a particular eIM with a given eimID to an eUICC that does not yet contain any Associated eIM.

NOTE:Mechanisms and functions used for Unsigned eCO at eUICC production (see Annex B.1 of SGP.31 [1]) are out of scope of this specification.

In addition, the eUICC and the IPAd MAY support ES10b.eUICCMemoryReset to completely remove all eIM Configuration Data of all Associated eIMs from the eUICC.

NOTE:The security of this mechanism is left to the implementation as described in SGP.31 [1].

2.11 eIM Package Structures

This section describes the structure of eIM Package requests and responses that comprise:
    • Signed eUICC Package and its execution result.
    • IPA and/or eUICC data
    • Profile Download trigger
    • List of Notifications
    • Acknowledgements of eUICC Package Results and Notifications

2.11.1 eIM Package Request

The eIM Package request contains either:

•an EuiccPackageRequest,

•an IpaEuiccDataRequest,

•a ProfileDownloadTriggerRequest, or

•an EimAcknowledgements

data object.

2.11.1.1 EuiccPackageRequest

The signed eUICC Package structure SHALL be encoded in the ASN.1 data object as shown below. -- ASN1START EuiccPackageRequest ::= [81] SEQUENCE { -- Tag ' BF51', #SupportedForPsmoV1.0.0# euiccPackageSigned EuiccPackageSigned, eimSignature [APPLICATION 55] OCTET STRING -- Tag '5F37' }

EuiccPackageSigned ::= SEQUENCE { eimId [0] UTF8String (SIZE(1..128)), eidValue [APPLICATION 26] Octet16, -- Tag '5A' counterValue [1] INTEGER,

    eimTransactionId [2] TransactionId OPTIONAL,
    euiccPackage EuiccPackage
}

EuiccPackage ::= CHOICE { psmoList SEQUENCE OF Psmo, -- #SupportedForPsmoV1.0.0# ecoList SEQUENCE OF Eco -- #SupportedForEcoV1.0.0# } -- ASN1STOP The euiccPackageSigned includes:

•eIM identifier (eimId) : identifier of the eIM that issues the eUICC Package. See section 4.3. • EID (eidValue) of the targeted eUICC. • Counter value (counterValue) used by the eIM for replay protection. Each eIM manages its own counter. The eIM increments its counterValue by 1 for each eUICC Package being sent to the target eUICC. The eUICC implementation SHALL be able to handle counter values at least up to value of 8388607 (0x7FFFFF), included. • Optional Transaction ID (eimTransactionId, see [4]). • eUICC Package (euiccPackage) consisting of either PSMOs or eCOs. The eIM SHALL sign the euiccPackageSigned data object concatenated with the associationToken data object (retrieved from the eIM Configuration Data) to create the eimSignature. If no association token is configured in the eIM Configuration Data, the associationToken data object SHALL be used with the value set to zero (i.e., '84 01 00') for creating the signature. The eUICC returns the same eimId, eimTransactionId and counterValue in the eUICC Package Result, which allows the eIM to link a received eUICC Package Result to a sent eUICC Package.

              eIM Configuration Data
The eIM Configuration Data stored by the eUICC for each Associated eIM consists of:
•   eimId: uniquely identifies the Associated eIM within the eUICC. See section 4.3.
•   eimFqdn: Identifier of the eIM that issues the eUICC Package encoded as a FQDN.

NOTE:In case an intermediate server, e.g. MQTT Broker, is used for the communication between the eIM and the IoT Device, the identifier of that intermediate server is provided in eimFqdn.

•   eimIdType: For more information regarding eIM identifier types (EimIdType) see
    section 4.3.
•   counterValue: used to protect against replay of eUICC Packages sent by the eIM.
    The highest received counterValue per Associated eIM is stored within the eUICC.
    The eUICC implementation SHALL be able to handle counter values at least up to
    value of 8388607 (0x7FFFFF), included. The eUICC SHALL return the error code
    counterValueOutOfRange in case the counterValue exceeds the maximum
    value supported by the eUICC.
•   associationToken: optional, for replay protection. The association token is the
    value of one global counter on each eUICC, which SHALL start at zero and SHALL be
incremented to generate the next association token each time an association token is
requested (i.e., the first association token will be 1). It SHALL NOT be possible to reset
the counter by any mechanism (e.g., eUICC Memory Reset).

NOTE:The association token can protect against an attack scenario where a whole sequence of operations beginning with AddInitialEim is replayed after a reset of the eIM Configuration Data. It is optional to configure this mechanism for an eIM.

•   eimPublicKeyData: eIM public key data either as a raw public key (eimPublicKey)
    or as a Certificate (eimCertificate) , used for eUICC Package verification.
•   trustedPublicKeyDataTls: either eIM public key (trustedEimPkTls) or a
    Certificate        (trustedCertificateTls)                   used        for        TLS/DTLS.
    The trustedCertificateTls is a certificate that is trusted in the chain of
    certificates ending with the eIM certificate (leaf certificate). This certificate MAY be the
    certificate of the eIM itself, or the certificate of the root CA or the certificate of a trusted
    intermediate CA. This certificate SHALL contain the SubjectKeyIdentifier extension. A
    root CA or intermediate CA certificate SHALL include the BasicConstraints extension
    with the value of “cA” set to TRUE[25]. The IPAd MAY ignore this field.
•   eimSupportedProtocol: For more information regarding eIM protocol support
    (EimSupportedProtocol) see section 4.2.
•   euiccCiPKId: CI Public Key Identifier allowing to select the eUICC Certificate for
    signing eUICC Package Results returned to this eIM. If not provided, the first entry
    of euiccCiPKIdListForSigning in eUICCInfo2 SHALL be used as euiccCiPKId.
•   indirectProfileDownload: if present it indicates the eIM support of Indirect
    Profile download with indicated EimSupportedProtocol.

NOTE:trustedCertificateTls data object is needed if the IoT Device uses the IPAe and the eIM Package transfer use eimRetrieveHttps or eimRetrieveCoaps. This will allow to avoid any potential failure of the TLS/DTLS session.

When adding, updating, or retrieving eIM Configuration Data for a particular eIM from the
eUICC the following ASN.1 data object is used, where the optionality of certain fields is
described below:
-- ASN1START
EimConfigurationData ::= SEQUENCE {
   eimId [0] UTF8String (SIZE(1..128)), -- eimId of eIM
   eimFqdn [1] UTF8String OPTIONAL, -- FQDN of eIM or intermediate server, if used
   eimIdType [2] EimIdType OPTIONAL,
   counterValue [3] INTEGER OPTIONAL, -- initial counterValue for the eIM
   associationToken [4] INTEGER OPTIONAL,
   eimPublicKeyData [5] CHOICE {
      eimPublicKey SubjectPublicKeyInfo, -- public key of eIM, used for eUICC
Package signature verification, where the encoding follows X.509 standard
      eimCertificate Certificate -- certificate of eIM, used for eUICC Package
signature verification, where the encoding follows X.509 standard
   } OPTIONAL,
   trustedPublicKeyDataTls [6] CHOICE {
     trustedEimPkTls SubjectPublicKeyInfo, -- public key of eIM, used for TLS or DTLS,
where the encoding follows X.509 standard
     trustedCertificateTls Certificate -- either the certificate of eIM, used for
(D)TLS, or the certificate of the CA, where the encoding follows X.509 standard
   } OPTIONAL,
   eimSupportedProtocol [7] EimSupportedProtocol OPTIONAL,
   euiccCiPKId [8] SubjectKeyIdentifier OPTIONAL, -- CI Public Key Identifier
supported on the eUICC for signature creation
   indirectProfileDownload[9] NULL OPTIONAL -- support of Indirect Profile download
with indicated EimSupportedProtocol
}
EimIdType ::= INTEGER {
   eimIdTypeOid(1),
   eimIdTypeFqdn(2),
   eimIdTypeProprietary(3)
}
EimSupportedProtocol ::= BIT STRING {
   eimRetrieveHttps(0),
   eimRetrieveCoaps(1),
   eimInjectHttps(2),
   eimInjectCoaps(3),
   eimProprietary(4)
}
-- ASN1STOP
              eUICC Package Request Containing eCOs
The eCOs within the eUICC Package request SHALL be encoded in the ASN.1 data object as
shown below.
-- ASN1START
Eco ::= CHOICE {
   addEim [8] EimConfigurationData, -- for eIM configuration data see 2.11.1
   deleteEim [9] SEQUENCE {eimId [0] UTF8String},
   updateEim [10] EimConfigurationData,
   listEim [11] SEQUENCE {}
}
-- ASN1STOP

If the eCO is the addition of an Associated eIM (addEim), then eimId, counterValue and eimPublicKeyData SHALL be provided as part of the EimConfigurationData data object.

The trustedPublicKeyDataTls is optional in EimConfigurationData data object. It SHOULD be provided in addEim if the IpaMode in eUICCInfo2 is ipae, and if the eimSupportedProtocol contains eimRetrieveHttps or eimRetrieveCoaps.

NOTE :       IPAd of some IoT Devices may need to retrieve
             trustedPublicKeyDataTls from the eUICC by calling
             GetEimConfigurationData. In this case, trustedPublicKeyDataTls
             needs to be included in EimConfigurationData data of addEim.
The eimFqdn is optional for the eIM to provide in EimConfigurationData data object.
It   SHALL   be     provided      if  eimIdType       is  not  eimIdTypeFqdn     in
the EimConfigurationData data object. It SHALL NOT be provided if eimIdType is
eimIdTypeFqdn in that EimConfigurationData data object, to avoid redundancy with
eimId.

The eimIdType is optional for the eIM to provide in EimConfigurationData data object. If not provided, the eUICC SHALL assign the value eimIdTypeProprietary before storing

the eIM Configuration Data.If the eUICC is requested to calculate an association token for the new Associated eIM, the associationToken data object SHALL be provided with the value set to -1. Otherwise, the data object SHALL NOT be provided.

The   eimSupportedProtocol       is    optional    for    the   eIM    to    provide in
EimConfigurationData data object. If not provided, the eUICC SHALL assign the value
where only the eimProprietary bit is set before storing the eIM Configuration Data.
The euiccCiPKId is optional for the eIM to provide in EimConfigurationData. If not
provided, the  eUICC      SHALL       assign    the    value of   first entry    of
euiccCiPKIdListForSigning in eUICCInfo2 before storing the eIM Configuration Data.

If the eCO is the update of the configuration of an Associated eIM (updateEim), then eimId of the target Associated eIM and at least one of either counterValue, eimPublicKeyData, eimIdType, eimFqdn, eimSupportedProtocol, trustedPublicKeyDataTls, euiccCiPKId or indirectProfileDownload SHALL be provided as part of the EimConfigurationData data object. The associationToken data object SHALL NOT be provided.

eimId is used to retrieve the associated configuration. Updating eimId SHALL NOT be permitted. Updating counterValue to a lower value without also updating eimPublicKeyData SHALL NOT be permitted.

If the eCO is the deletion of an Associated eIM (deleteEim), then only the eimId of the
target Associated eIM SHALL be provided.
              eUICC Package Request Containing PSMOs
The PSMOs within the eUICC Package request SHALL be encoded in the ASN.1 data object
as shown below.
-- ASN1START
Psmo ::= CHOICE {
   enable [3] SEQUENCE {
      iccid [APPLICATION 26] Iccid,
      rollbackFlag NULL OPTIONAL
   },
   disable [4] SEQUENCE {iccid [APPLICATION 26] Iccid},
   delete [5] SEQUENCE {iccid [APPLICATION 26] Iccid},
   listProfileInfo [45] ProfileInfoListRequest, -- Tag 'BF2D'
   getRAT [6] SEQUENCE {},
   configureImmediateEnable [7] SEQUENCE {
      immediateEnableFlag [0] NULL OPTIONAL,
      defaultSmdpOid [1] OBJECT IDENTIFIER OPTIONAL,
      defaultSmdpAddress [2] UTF8String OPTIONAL
   },
   setFallbackAttribute [8] SEQUENCE {iccid [APPLICATION 26] Iccid},
   unsetFallbackAttribute [9] SEQUENCE {},
   setDefaultDpAddress [101] SetDefaultDpAddressRequest -- Tag 'BF65'
}
-- ASN1STOP
The iccid indicates the target Profile at the eUICC as defined in SGP.22 [4].

The rollbackFlag is presented by the eIM within the enable PSMO. The IPA MAY trigger the Rollback Mechanism using the ES10b.ProfileRollback function if the newly enabled Profile fails to provide connectivity.

The listProfileInfo SHALL be coded and processed as defined in section 5.9.14.

If no tag list is present for listProfileInfo, the eUICC SHALL return by default the following list:

•   ICCID, tag '5A'
•   ISD-P AID, tag '4F'
•   Profile state, tag '9F70'
•   Service provider name, tag '91'
•   Profile name, tag '92'
•   Profile Class, tag '95'
•   ecallIndication, tag '9F7B'
•   fallbackAttribute, tag '9F26'
•   fallbackAllowed, tag '9F67'

Immediate Profile enabling is activated when immediateEnableFlag is present in the configureImmediateEnable command and deactivated when immediateEnableFlag is not present. The configuration of default SM-DP+ data (defaultSmdpOid and defaultSmdpAddress) for use in the immediate Profile enabling is possible independently of whether the immediateEnableFlag is present or not.

The setDefaultDpAddress SHALL be coded and processed as defined in section 5.9.25.

At most one enable command SHALL occur in an eUICC Package.

At most one disable command SHALL occur in an eUICC Package.

A listProfileInfo command SHALL NOT occur after an enable, disable or delete command in an eUICC Package. If this situation occurs the response SHALL indicate the error profileChangeOngoing.

The setFallbackAttribute command is used to set the Fallback Attribute for the target Profile. The IPA MAY trigger the Fallback Mechanism using the ES10b. ExecuteFallbackMechanism function (see section 5.9.20) if the IoT Device detects a permanent loss of connectivity using the currently enabled Profile. The IPA MAY afterwards disable the Fallback Profile using the ES10b.ReturnFromFallback function (see section 5.9.21).

NOTE:How the IoT Device detects a permanent loss of connectivity is implementation specific. How and upon which events the IPA is instructed by the IoT Device to execute an enable or disable of the Fallback Profile is IoT Device implementation specific.

The unsetFallbackAttribute command is used to unset the Fallback Attribute for the target Profile.

2.11.1.2 IpaEuiccDataRequest

The IpaEuiccDataRequest is used by the eIM to retrieve data from eUICC and/or IPA. It
SHALL be encoded as follows:
-- ASN1START
IpaEuiccDataRequest ::= [82] SEQUENCE { -- Tag BF52
   tagList [APPLICATION 28] OCTET STRING, -- Tag '5C'
   euiccCiPKIdentifierToBeUsed OCTET STRING OPTIONAL, -- CI Public Key Identifier
(possibly truncated) supported on the eUICC for signature creation
   searchCriteriaNotification [1] CHOICE {
      seqNumber [0] INTEGER,
      profileManagementOperation [1] NotificationEvent
   } OPTIONAL,
   searchCriteriaEuiccPackageResult [2] CHOICE {
      seqNumber [0] INTEGER
   } OPTIONAL,
   eimTransactionId [3] TransactionId OPTIONAL -- Tag '82'
}
-- ASN1STOP

The eIM MAY request one or more IPA and eUICC data items by listing each tag of a requested item in the tagList of IpaEuiccDataRequest. The following IPA and eUICC data and tags are defined:

•   List of Notifications tag 'A0'.
•   Default SM-DP+ address (see SGP.22 [4]), tag '81’.
•   eUICC Package Results, tag 'A2'.
•   eUICCInfo1 (see section 5.9.2 of this specification), tag 'BF20'.
•   eUICCInfo2 (see section 5.9.2 of this specification), tag 'BF22'.
•   Root SM-DS address (see SGP.22 [4]), tag '83'.
•   Association token (see sections 2.11.1 and 5.9.18 of this specification), tag '84'.
•   EUM certificate (see SGP.22 [4]), tag 'A5'.
•   eUICC certificate (see SGP.22 [4]), tag 'A6'.
•   IPA Capabilities (see section 4.1), tag 'A8'.
•   Device Information (see SGP.22 [4] section 4.2), tag 'A9'.

Any tag that is present in the tagList of IpaEuiccDataRequest, but is not in the list of tags above, is ignored without error.

In order to select between multiple of EUM certificates and eUICC certificates within the eUICC
the eIM MAY provide the CI Public Key Identifier (euiccCiPKIdentifierToBeUsed). If
present, the full CI Public Key Identifier (20 bytes) SHALL be sent to an IPA without IPA
Capability minimizeEsipaBytes and the CI Public Key Identifier in truncated form SHALL
be sent to an IPA with IPA Capability minimizeEsipaBytes (to minimize the number of
transmitted bytes). Truncated form means only enough leading bytes of the CI Public Key
Identifier are provided for IPA to be able to uniquely locate and extract the chosen CI Public
Key Identifier from the euiccCiPKIdListForSigning of eUICCInfo1 / eUICCInfo2. If
euiccCiPKIdentifierToBeUsed               is    not     provided,   the      first   entry    of
euiccCiPKIdListForSigning in eUICCInfo1 / eUICCInfo2 SHALL be used as
euiccCiPKIdentifierToBeUsed when selecting the EUM certificate and/or eUICC
certificate to return.

The searchCriteriaNotification and searchCriteriaEuiccPackageResult data object can be used to filter the list of Notifications or eUICC Package Results that SHALL be returned by the IPA according to the following:

•   If tag ‘A0’ is present in the tagList, then
         o if there is no searchCriteriaNotification the IPA SHALL return the
             notificationsList as part of the IpaEuiccDataResponse containing all
             Notifications stored in the eUICC.
         o if the searchCriteriaNotification is present and specifies seqNumber,
             and there is a Notification with the given sequence number stored in the eUICC,
             then the IPA SHALL return the notificationsList as part of the
             IpaEuiccDataResponse containing the Notification.
         o if the searchCriteriaNotification is present and specifies
             profileManagementOperation                 the   IPA   SHALL       return   the
             notificationsList as part of the IpaEuiccDataResponse containing all
             the Notifications of the types specified by profileManagementOperation
             (a bit set to 1 in the profileManagementOperation indicates that the
             eUICC SHALL return all the Notifications corresponding to this type).
•   If tag ‘A2’ is present in the tagList, then
         o if there is no searchCriteriaEuiccPackageResult the IPA SHALL return
             the euiccPackageResults as part of the IpaEuiccDataResponse
             containing all eUICC Package Results stored in the eUICC.
         o if the searchCriteriaEuiccPackageResult is present and specifies
             seqNumber, and there is an eUICC Package Result with the given sequence
             number stored in the eUICC, then the IPA SHALL return the
             euiccPackageResults as part of the IpaEuiccDataResponse containing
             the eUICC Package Result.

•If tag ‘A0’ or tag ‘A2’ are not present, the IPA SHALL ignore searchCriteriaNotification and searchCriteriaEuiccPackageResult respectively.

Optionally, eIM MAY provide eIM transaction identifier (eimTransactionId) in order to correlate IpaEuiccDataRequest and IpaEuiccDataResponse.

IPA uses the following functions to obtain eUICC data: ES10b.GetEUICCInfo (see section 5.9.2), ES10b.GetCerts (see section 5.9.10), ES10b.GetEID (see section 5.9.19), ES10b. RetrieveNotificationsList (see section 5.9.11), ES10a.GetEuiccConfiguredAddresses (see section 5.8.1) and ES10b.GetEimConfigurationData (see section 5.9.18). IPA SHALL support providing at least the association token and the IPA Capabilities to the eIM. The rest of the IPA and eUICC data are not mandatory to support by IPA but depends on the IPA Capabilities. If a particular IPA or eUICC data is not supported by IPA it is simply ignored by IPA when building the IpaEuiccDataResponse structure (see section 2.11.2.2). Depending on IPA Capabilities the IPA SHALL support the following:

•   An IPA having IPA Capability eimCtxParams1Generation SHALL support
    providing deviceInfo to the eIM.
•   An IPA having IPA Capability minimizeEsipaBytes SHALL support providing
    euiccInfo1, euiccInfo2, eumCertificate, and euiccCertificate to the
    eIM.

2.11.1.3 ProfileDownloadTriggerRequest

The ProfileDownloadTriggerRequest SHALL be encoded as follows:

-- ASN1START
ProfileDownloadTriggerRequest ::= [84] SEQUENCE { -- Tag 'BF54'
   profileDownloadData [0] ProfileDownloadData OPTIONAL,
   eimTransactionId [2] TransactionId OPTIONAL
}
ProfileDownloadData ::= CHOICE {
   activationCode [0] UTF8String (SIZE(0..255)),
   contactDefaultSmdp [1] NULL,
   contactSmds [2] SEQUENCE {
      smdsAddress UTF8String OPTIONAL
   }
}
-- ASN1STOP

The eIM SHALL provide ProfileDownloadTriggerRequest data object as follows.

•   If and only if the IPA indicates eimDownloadDataHandling in IPA Capabilities and
    the eIM requests the IPA to call ESipa.InitiateAuthentication function, an empty data
    object is provided (i.e., without profileDownloadData). The IPA continues with the
    indirect Profile download or Event Retrieval procedure.
•   Otherwise profileDownloadData is provided, containing one of the following:
        o activationCode, if the eIM provides an Activation Code.
        o contactDefaultSmdp, if the eIM requests the IPA to contact the default
            SM-DP+ address that is available in the IoT Device.
        o contactSmds, if the eIM requests the IPA to contact the SM-DS address that
            is available in the IoT Device (smdsAddress is absent) or specified by the eIM
            (smdsAddress is present). This triggers the retrieval of the SM-DP+ Address
            and EventID from the SM-DS, either over ES11 as defined in section 3.6.2 of
            SGP.22 [4] or over ESipa and ES11’ as defined in section 3.9.2.2 of this
            document.
    For each use case the IPA continues with the corresponding direct/indirect Profile
    download or Event Retrieval procedure depending on its capability.
The eIM transaction identifier (eimTransactionId) is OPTIONAL for the eIM to
include in the ProfileDownloadTriggerRequest. It MAY be used for linking a
ProfileDownloadTriggerRequest to a ProfileInstallationResult in a
Direct Profile Download procedure, or determine the IoT Device in Indirect Profile
Download procedure.

2.11.1.4 EimAcknowledgements

The EimAcknowledgements structure is sent from the eIM to the IPA to inform the IPA that the eIM successfully received Notifications and/or eUICC Package Results sent from the IPA

to the eIM. The structure contains the sequence number(s) of received Notifications and/or eUICC Package Results and is defined as follows: -- ASN1START EimAcknowledgements ::= [83] SEQUENCE OF SequenceNumber -- Tag BF53 SequenceNumber ::= [0] INTEGER -- ASN1STOP

2.11.2 eIM Package Result

The eIM Package Result contains either:

•an EuiccPackageResult,

•an EuiccPackageResult concatenated with a PendingNotificationList (see section 2.11.2.2),

•IpaEuiccDataResponse,

•ProfileDownloadTriggerResult

•EimPackageResultErrorCode or EimPackageResultResponseError

data object.

2.11.2.1 EuiccPackageResult

Before processing the PSMOs or the eCOs in the eUICC Package, the eUICC verifies the
signed eUICC Package as defined in sections 3.3 and 5.9.1.
Upon successful verification of the signed eUICC Package, the PSMOs or eCOs in the eUICC
Package are executed sequentially by the eUICC until the end is reached or an error is
encountered for a PSMO or an eCO. Upon finishing the execution of the signed eUICC
Package,    the      eUICC        produces    a    signed    eUICC    Package      Result
(euiccPackageResultSigned) containing the PSMO or eCO execution result(s).
A signed eUICC Package Result with PSMO or eCO processing result(s)
(euiccPackageResultSigned) SHALL be kept by the eUICC (which can hold one or
several such signed eUICC Package Result) until explicitly deleted by the IPA, after successful
delivery to the eIM. Before being deleted, the signed eUICC Package Result(s) MAY be
retrieved at any time by the IPA. The unsigned and signed eUICC Package error results
generated from eUICC Package verification errors (euiccPackageErrorUnsigned and
euiccPackageErrorSigned) are not kept by the eUICC.
When the eUICC needs to store a new signed eUICC Package Result with PSMO or eCO
processing result(s) and if there is not enough space, the eUICC SHALL delete one or more
of the previously stored signed eUICC Package Results and Pending Notifications in order of
their sequence number, beginning with the lowest. If deleting all signed eUICC Package
Results and Pending Notifications is still not enough to store a new signed eUICC Package
Result, the eUICC SHALL return the signed eUICC Package Result to the IPA without storing
it.

The eUICC Package Result SHALL be encoded in the ASN.1 data object as shown below. -- ASN1START EuiccPackageResult ::= [81] CHOICE { -- Tag 'BF51' #SupportedForPsmoV1.0.0# euiccPackageResultSigned EuiccPackageResultSigned, euiccPackageErrorSigned EuiccPackageErrorSigned,

   euiccPackageErrorUnsigned EuiccPackageErrorUnsigned
}
EuiccPackageResultSigned ::= SEQUENCE {
   euiccPackageResultDataSigned EuiccPackageResultDataSigned,
   euiccSignEPR [APPLICATION 55] OCTET STRING -- Tag '5F37'
}
EuiccPackageResultDataSigned ::= SEQUENCE { -- #SupportedForPsmoV1.0.0#
   eimId [0] UTF8String (SIZE(1..128)),
   counterValue [1] INTEGER,
   eimTransactionId[2] TransactionId OPTIONAL,
   seqNumber [3] INTEGER,
   euiccResult SEQUENCE OF EuiccResultData
}
EuiccResultData ::= CHOICE {
   enableResult [3] EnableProfileResult,
   disableResult [4] DisableProfileResult,
   deleteResult [5] DeleteProfileResult,
   listProfileInfoResult [45] ProfileInfoListResponse,
   getRATResult [6] RulesAuthorisationTable, -- see SGP.22
   configureImmediateEnableResult [7] ConfigureImmediateEnableResult,
   addEimResult [8] AddEimResult,
   deleteEimResult [9] DeleteEimResult,
   updateEimResult [10] UpdateEimResult,
   listEimResult [11] ListEimResult,
   rollbackResult [12] RollbackProfileResult,
   setFallbackAttributeResult [13] SetFallbackAttributeResult,
   unsetFallbackAttributeResult [14] UnsetFallbackAttributeResult,
   processingTerminated INTEGER {
      resultSizeOverflow(1),
      unknownOrDamagedCommand(2),
      interruption(3),
      undefinedError(127)
   },
   setDefaultDpAddressResult [101] SetDefaultDpAddressResponse
}
EuiccPackageErrorSigned ::= SEQUENCE {
   euiccPackageErrorDataSigned EuiccPackageErrorDataSigned,
   euiccSignEPE [APPLICATION 55] OCTET STRING -- Tag '5F37'
}
EuiccPackageErrorDataSigned ::= SEQUENCE {
   eimId [0] UTF8String (SIZE(1..128)),
   counterValue [1] INTEGER,
   eimTransactionId [2] TransactionId OPTIONAL,
   euiccPackageErrorCode EuiccPackageErrorCode
}
EuiccPackageErrorCode ::= INTEGER {
   invalidEid(3),
   replayError(4),
   counterValueOutOfRange(6),
   sizeOverflow(15),
   ecallActive(104),
   undefinedError(127)}

EuiccPackageErrorUnsigned ::= SEQUENCE { eimId [0] UTF8String (SIZE(1..128)), eimTransactionId [2] TransactionId OPTIONAL, associationToken [4] INTEGER OPTIONAL } ConfigureImmediateEnableResult ::= INTEGER { ok(0), insufficientMemory(1), commandError(7), undefinedError(127) } EnableProfileResult ::= INTEGER { ok(0), iccidOrAidNotFound(1), profileNotInDisabledState(2),

   disallowedByPolicy(3),
   catBusy(5),
   rollbackNotAvailable(20),
   undefinedError(127)
}
DisableProfileResult ::= INTEGER {
   ok(0),
   iccidOrAidNotFound(1),
   profileNotInEnabledState(2),
   disallowedByPolicy(3),
   catBusy(5),
   undefinedError(127)
}
DeleteProfileResult ::= INTEGER {
   ok(0),
   iccidOrAidNotFound(1),
   profileNotInDisabledState(2),
   disallowedByPolicy(3),
   rollbackNotAvailable(20),
   returnFallbackProfile(21),
   undefinedError(127)
}
ProfileInfoListResponse ::= [45] CHOICE {
   profileInfoListOk SEQUENCE OF ProfileInfo, -- see SGP.22
   profileInfoListError ProfileInfoListError
}
ProfileInfoListError ::= INTEGER {
   incorrectInputValues(1),
   profileChangeOngoing (11),
   undefinedError(127)
}
RollbackProfileResult ::= INTEGER {
   ok(0),
   undefinedError(127)
}
SetFallbackAttributeResult ::= INTEGER {
   ok(0),
   iccidOrAidNotFound (1),
   fallbackNotAllowed (2),
   fallbackProfileEnabled (3),
   undefinedError (127)
}
UnsetFallbackAttributeResult ::= INTEGER {
   ok(0),
   noFallbackAttribute(2),
   fallbackProfileEnabled (3),
   commandError(7),
   undefinedError (127)
}
AddEimResult ::= CHOICE {
   associationToken [4] INTEGER,
   addEimResultCode INTEGER {
      ok(0),
      insufficientMemory(1),
      associatedEimAlreadyExists(2),
      ciPKUnknown(3),
      invalidAssociationToken(5),
      counterValueOutOfRange(6),
      commandError(7),
      undefinedError(127)
   }
}
DeleteEimResult ::= INTEGER {
   ok(0),
   eimNotFound(1),
   lastEimDeleted(2), -- no eIM Configuration Data available in eUICC,
   commandError(7),
   undefinedError(127)
}
UpdateEimResult ::= INTEGER {
   ok(0),
   eimNotFound (1),
   ciPKUnknown(3),
   counterValueOutOfRange(6),
   commandError(7),
   undefinedError(127)
}
ListEimResult ::= CHOICE {
   eimIdList SEQUENCE OF EimIdInfo,
   listEimError INTEGER {
      undefinedError(127)
   }
}
EimIdInfo ::= SEQUENCE {
   eimId [0] UTF8String (SIZE(1..128)),
   eimIdType [2]     EimIdType    OPTIONAL   --   present   in   case   of   eimIdTypeOid   and
eimIdTypeFqdn
}
-- ASN1STOP
The eIM transaction identifier (eimTransactionId) is OPTIONAL to use by the eIM in the
signed eUICC Package. If it was included in the signed eUICC Package, the eUICC SHALL
include the same eimTransactionId in the signed eUICC Package Result and also
euiccPackageErrorUnsigned and euiccPackageErrorSigned in case of
errors.

euiccSignEPR and euiccSignEPE SHALL be created using the SK.EUICC.ECDSA and verified using the related PK.EUICC.ECDSA. In case there are more than one SK.EUICC.ECDSA available for signing, the SK.EUICC.ECDSA chaining back to the CI public key identified by the euiccCiPKId of the eIM Configuration Data (of the Associated eIM for which the eUICC Package Result is intended) SHALL be used. euiccSignEPR SHALL apply on the concatenated data objects euiccPackageResultDataSigned and associationToken. euiccSignEPE SHALL apply on the concatenated data objects euiccPackageErrorDataSigned and associationToken.

If no associationToken is configured for the eIM, the associationToken data object SHALL be used with the value set to zero for creating the signature.

The eIM SHALL use the PK.EUICC.ECDSA from CERT.EUICC.ECDSA to verify the signature euiccSignEPR and euiccSignEPE. The eIM SHALL verify CERT.EUICC.ECDSA.

When the Emergency Profile is enabled, the eUICC SHALL reject any EuiccPackageRequest, EuiccMemoryResetRequest, or ExecuteFallbackMechanism with the error codes ecallActive.

2.11.2.2 IpaEuiccDataResponse

The IpaEuiccDataResponse SHALL be encoded as follows:

-- ASN1START

IpaEuiccDataErrorCode ::= INTEGER {

    incorrectTagList (1),
    euiccCiPKIdNotFound(5),
    ecallActive(104),
    undefinedError(127)
}

IpaEuiccDataResponseError ::= SEQUENCE { eimTransactionId [0] TransactionId OPTIONAL, ipaEuiccDataErrorCode IpaEuiccDataErrorCode }

IpaEuiccDataResponse ::= [82] CHOICE { -- Tag 'BF52' ipaEuiccData IpaEuiccData, ipaEuiccDataResponseError IpaEuiccDataResponseError }

PendingNotificationList ::= SEQUENCE OF PendingNotification EuiccPackageResultList ::= SEQUENCE OF EuiccPackageResult

IpaEuiccData ::= SEQUENCE { notificationsList [0] PendingNotificationList OPTIONAL, -- Tag 'A0' defaultSmdpAddress [1] UTF8String OPTIONAL, -- Tag '81' euiccPackageResultList [2] EuiccPackageResultList OPTIONAL, -- Tag 'A2' euiccInfo1 [32] EUICCInfo1 OPTIONAL, -- Tag 'BF20' euiccInfo2 [34] EUICCInfo2 OPTIONAL, -- Tag 'BF22' rootSmdsAddress [3] UTF8String OPTIONAL, -- Tag '83' associationToken [4] INTEGER OPTIONAL, -- Tag '84' eumCertificate [5] Certificate OPTIONAL, -- Tag 'A5' euiccCertificate [6] Certificate OPTIONAL, -- Tag 'A6' eimTransactionId [7] TransactionId OPTIONAL, -- Tag '87' ipaCapabilities [8] IpaCapabilities OPTIONAL, -- Tag 'A8' deviceInfo [9] DeviceInfo OPTIONAL -- Tag 'A9' } -- ASN1STOP If the associationToken is requested, but no association token is configured for the eIM, the associationToken data object SHALL be absent in the response.

An IPA with IPA Capability minimizeEsipaBytes SHOULD include each pending Notification in notificationsList in compact format as described in section 5.14.7.

If eimTransactionId was present in the IpaEuiccDataRequest, the IPA SHALL return the same eimTransactionId in the IpaEuiccData or IpaEuiccDataResponseError.

If the Emergency Profile is enabled, then the IPA SHALL stop the procedure and return an IpaEuiccDataResponseError containing ipaEuiccDataErrorCode set to ecallActive.

2.11.2.3 ProfileDownloadTriggerResult

The ProfileDownloadTriggerResult SHALL be encoded as follows:

-- ASN1START
ProfileDownloadTriggerResult ::= [84] SEQUENCE { -- tag 'BF54'
   eimTransactionId [2] TransactionId OPTIONAL,
   profileDownloadTriggerResultData CHOICE {
      profileInstallationResult [55] ProfileInstallationResult, -- see SGP.22 [4]
      profileDownloadError SEQUENCE {
         profileDownloadErrorReason [0] INTEGER {
            ecallActive (104),
            undefinedError(127)
         },
         errorResponse OCTET STRING OPTIONAL
      }

} } -- ASN1STOP

The IPA SHALL send ProfileDownloadTriggerResult to inform the eIM about the result of a direct Profile download that was requested by the eIM.

•   If the eIM provided a transaction identifier (eimTransactionId) in
    ProfileDownloadTriggerRequest, the IPA SHALL return the same transaction
    identifier in ProfileDownloadTriggerResult. Otherwise, eimTransactionId
    SHALL NOT be present.
•   If the Emergency Profile is enabled, then the IPA SHALL stop the procedure and
    return an profileDownloadError containing profileDownloadErrorReason set to
    ecallActive.

•If the IPA successfully downloaded a Profile and obtained a Profile Installation Result as a response of ES10b.LoadBoundProfilePackage function calls, the IPA SHALL return the Profile Installation Result in profileInstallationResult. Otherwise, the IPA SHALL return a profileDownloadError that MAY include an errorResponse..

o   The errorResponse, if present, SHALL include the error response of an
    ES10b function or an ES9+ function with ASN.1 binding that the IPA
    encountered during the Profile download procedure.

NOTE:the errorResponse for an error response of an ES9+ function with JSON binding is FFS.

3 Procedures

This section specifies the procedures associated with eUICC for IoT Devices.

Some call flows illustrate the case where the IPA is in the Device (IPAd). Such call flows with an IPAe would be identical except that all ES10 calls become internal to the eUICC and are out of scope of this specification.

3.1 eIM and IPA Communication

This section defines the procedures between the eIM and the IPA.

3.1.1 Transferring eIM Package

These procedures are used to transfer an eIM Package from the eIM to the IPA. It could be the IPA which retrieves any pending command from the eIM (section 3.1.1.1 eIM Package Retrieval), or the eIM which directly sends the command to the IPA (section 3.1.1.2 eIM Package Injection). The eIM SHALL support at least, one of these procedures. The IPA implementing ESipa SHALL support, at least, one of these procedures.

If ESipa is established between the eIM and the IPA, the eIM and IPA SHALL support the same mode (“eIM Package retrieval” or “eIM Package injection”) and use the same secure connection method (see section 3.1.2).

NOTE:An eIM intended to serve many different types of IoT Devices is recommended to support both procedures (“eIM Package Retrieval” and “eIM Package Injection”).

3.1.1.1 eIM Package Retrieval

This procedure is used by the IPA to retrieve any pending eIM Package from the eIM.

@startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid

participant "<b>eIM" as EIM participant "<b>IPA" as IPA

rnote over EIM, IPA : [1] [Secure connection establishment]

loop until ESipa.GetEimPackage response is noEimPackageAvailable IPA -> EIM : [2] ESipa.GetEimPackage request (EID) EIM -> EIM : [3] Fetch pending eIM Package(s) for the EID EIM -> IPA : [4] ESipa.GetEimPackage response (eIM Package) rnote over IPA : [5] [Process the eIM Package] alt If the IPA needs acknowledgement of sending eIM Package Result IPA -> EIM : [6] ESipa. ProvideEimPackageResult request (eIM Package Result, [Notification(s)]) EIM -> EIM : [7] Manage eIM Package queue EIM -> IPA : [8] ESipa.ProvideEimPackageResult response (sequence numbers) else Otherwise IPA -> EIM : [9] ESipa.HandleNotification (eIM Package Result) EIM -> EIM : [10] Manage eIM Package queue EIM -> IPA : [11] OK end end @enduml

Figure 5   eIM Package Retrieval

Start Conditions:

The IoT Device can trigger the IPA through an internal event (e.g., a timer expiration) without any knowledge about pending eIM Package. The IPA could also be informed, via a push Notification, about pending eIM Package in the eIM. For instance, the eIM or a backend system of the IoT Device maker can notify the IPA via out-of-band channel about pending eIM Package. The push Notification mechanism is out of scope of this document.

The IPA has the address (configured or retrieved using GetEimConfigurationData) of the Associated eIM. The IPA MAY have retrieved from the eUICC the Connectivity Parameters of the currently enabled Profile. The IPAd MAY use ES10b.GetConnectivityParameters. How the IPAe retrieves Connectivity Parameters is implementation specific.

Procedure:

1. The eIM and IPA establish a secure connection as defined in section 3.1.2.
2. The IPA calls ESipa.GetEimPackage function including EID.
3. The eIM fetches pending eIM Package(s) for the EID.
4. The eIM returns the eIM Package to the IPA.

5. The IPA processes the eIM Package.

If the IPA sends eIM Package Result together with Notifications, or if the IPA needs acknowledgements of sending eIM Package Result and optionally Notifications, the procedure continues in step (6). Otherwise, the procedure continues in step (9).

6. The IPA calls ESipa.ProvideEimPackageResult function including the eIM
Package Result and optionally one or more Notifications.
7. The eIM processes the eIM Package Result and manages the eIM Packages
pending in the queue for the eUICC.
8. The eIM acknowledges the reception of the eIM Package Result and optionally
Notifications by returning the corresponding sequence numbers.
9. The IPA calls ESipa.HandleNotification function comprising either the eIM
Package Result or a Notification.
10. The eIM processes the eIM Package Result and manages the eIM Packages
pending in the queue for the eUICC.
11. The eIM returns OK.

The IPA MAY repeat the above procedure until the eIM response is noEimPackageAvailable.

3.1.1.2 eIM Package Injection

This procedure is used by the eIM to inject eIM Package to the IPA.

@startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid

participant "<b>eIM" as EIM participant "<b>IPA" as IPA

rnote over EIM, IPA : [1] [Secure connection establishment] EIM -> IPA : [2] ESipa.TransferEimPackage (eIM Package) rnote over IPA : [3] [Process the eIM Package] IPA -> EIM : [4] ESipa.TransferEimPackage response (Execution result) @enduml

Figure 6   eIM Package Injection

Start Conditions:

The eIM and the IPA could be part of a whole system responsible of maintaining the communication between the eIM and the IPA.

Procedure:

1. The eIM and IPA establish a secure connection as defined in section 3.1.2.

NOTE:the hosting system (e.g.: device management system) allows the eIM to retrieve the EID of the IoT Device.

2. The eIM calls ESipa.TransferEimPackage function to the IPA comprising the eIM Package.

NOTE:It is implementation specific how this package is transferred from the eIM to the IPA using the underlying transport protocol. See examples in Annex B.

3. The IPA processes the eIM Package. 4. The IPA returns the eIM Package Result to the eIM.

3.1.2 Secure Connection Establishment

The present document does not mandate any protocol between the eIM and the IPA for
conveying an eIM Package. However, the protocol SHALL provide at least the integrity and
the confidentiality of messages.
This permits IoT Device deployments using any suitable protocol for the exchange of eIM
Packages and the delivery of Bound Profile Packages.
If ESipa is providing the protocol to transport ESipa messages as shown in Figure 7, the
following ones are suggested:
     • HTTP over TCP with TLS security.

NOTE:This could be used by a UICD which is not an NCD.

•CoAP over UDP with DTLS security.

NOTE:This mode could be used by an NCD.

Figure 7   ESipa (eIM -- IPA)

If the IoT Device has already implemented an interface and protocol with an external entity (e.g., a server) that is used for other functions of the IoT Device as shown in Figure 8, this underlying interface and its protocol can be used to transport ESipa messages.

Figure 8    ESipa (eIM -- IPA), using underlying protocol to transport ESipa
                                    messages

3.1.2.1 Secure Connection using HTTP over TCP

If HTTP/TLS (HTTPS) is used between the IPA and the eIM, the specification details in this section SHALL apply.

The HTTP/TLS (HTTPS) secure connection mode is used with server authentication. This means that only the eIM is authenticated by the IPA. If HTTPS is used, the TLS requirements defined in section 2.6.3.2 SHALL apply to the TLS session between IPA and eIM.

The ESipa functions requests and functions responses are sent over HTTPS. The interface binding over HTTP SHALL follow section 6.

NOTE:It is RECOMMENDED to use HTTP/TLS wherever TCP is available and working.

3.1.2.2 Secure Connection over CoAP

If CoAP with DTLS security is used between the IPA and the eIM, the specification details in this section SHALL apply.

The DTLS secure connection mode is used with server authentication. This means that only the eIM is authenticated by the IPA.

If CoAP is used, the DTLS requirements defined in section 2.6.3.2 SHALL apply to the DTLS session between IPA and eIM.

The ESipa functions requests and functions responses SHALL be sent over CoAP. The interface binding over CoAP SHALL follow section 6.

If DTLS 1.2 is used, IPA and eIM SHOULD use Connection ID (CID) as per RFC 9146 [14] to maintain the current DTLS association for better reliability.

If DTLS 1.2 is used, IPA SHOULD implement both and eIM SHOULD implement at least one of the following session resumption methods:

•The Session Identifiers as defined in RFC 5246 [8], or

•The Session Tickets as defined in RFC 5077 [20].

3.1.2.3 Secure Connection by underlying transport layer

This mode is used when the underlying transport layer supported by the IoT Device can transport ESipa messages.

ESipa messages SHALL be protected in terms of confidentiality, integrity, and authenticity.

This mode is not specified by this document. It’s out of scope how the ESipa messages are conveyed. Hence, the compatibility of the exchanges between the IPA and eIM is ultimately the responsibility of the integrator.

Annex B gives some deployments scenario using the underlying transport layer.

3.2 Profile Download and Installation

3.2.1 Profile Download Initiation

This procedure is identical to the Profile Download Initiation Procedure defined in section 3.1.1 of SGP.22 [4].

3.2.2 Common Mutual Authentication

This procedure is identical to Common Mutual Authentication Procedure defined in section 3.1.2 of SGP.22 [4]. It defines the mutual authentication procedure between the eUICC and the RSP Server.

3.2.3 Profile Download

3.2.3.1 Direct Profile Download

This section describes the Profile download and installation procedure where the IoT Device directly connects to the SM-DP+.

@startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid participant "<b>Operator" as OP participant "<b>SM-DP+" as DP participant "<b>eIM" as EIM participant "<b>IPA" as IPA participant "<b>eUICC" as E

group If option (a) and AC is available to eIM rnote over EIM : [1] eIM parses the AC to retrieve SM-DP+ Address, Activation Code Token, [SM-DP+ OID] end

group If IPA obtains a profile download trigger from eIM Package alt IPA-initiated rnote over EIM, IPA : [2a] eIM Package Retrieval Procedure including secure connection establishment (section 3.1.1.1) else eIM-initiated rnote over EIM, IPA : [2b] eIM Package Injection Procedure including secure connection establishment (section 3.1.1.2) end

rnote over IPA : [3] IPA parses the eIM Package and obtains profile \ndownload trigger that contain AC, or SM-DP+ Address and EventID \nor instruction to use the default SM-DP+ Address end

group If option (a) and AC is available to IPA rnote over IPA : [4] IPA parses AC to retrieve SM-DP+ Address, Activation Code Token, [SM-DP+ OID] end

rnote over DP, E #FFFFFF [5] - Execution of common mutual authentication procedure as defined in section 3.1.2 of SGP.22 [4]. - If immediate Profile enabling is activated, the eUICC SHALL verify that the download is coming from the default SM-DP+ configured in the eUICC. If the verification is successful the eUICC SHALL grant immediate enabling for this Profile. endrnote

rnote over DP #FFFFFF [6] - Look for Profile download pending order - Eligibility Check using Device Info, euiccInfo2 endrnote

Group Opt. DP -> OP : [7] ES2+.HandleDownloadProgressInfo(...) OP --> DP : OK end DP --> IPA : [error]

rnote over DP #FFFFFF [8] - Build Profile Metadata - Check if download retry - Build smdpSigned2 = {TransactionID, Confirmation Code Required Flag, [bppEuiccOtpk]} - Compute smdpSignature2 over smdpSigned2 and euiccSignature1 endrnote

DP -> IPA : [9] TransactionID, Profile Metadata, smdpSigned2, smdpSignature2, CERT.DPpb.ECDSA

group [10] Check if ProfileMetadata \ncontains PPR(s) rnote over IPA #FFFFFF endrnote IPA -> E : [ES10b.GetRAT] E --> IPA : [RAT] IPA -> E : [ES10b.GetProfilesInfo] E --> IPA : [ProfileInfoListOk] end

rnote over DP, E #FFFFFF [11] sub-procedure Profile Download and Installation – Download Confirmation as defined in section 3.1.3.2 of SGP.22 [4] endrnote

rnote over IPA, E #FFFFFF [12] IPA installs the Profile to the eUICC as defined in sub-procedure Profile Installation in section 3.1.3.3 of SGP.22 [4] endrnote

IPA -> EIM : [13] ["ESipa.HandleNotification" function]

group [14].

IPA -> DP : "ES9+.HandleNotification" function

rnote over DP
SM-DP+ SHALL continue the procedure as defined
         in section 3.1.3.3 of SGP.22 [4] step 8 to 10
endrnote
end

group opt rnote over IPA #FFFFFF [15]

If default SM-DP+was used, the IPA MAY request immediate Profile enabling (ES10b.ImmediateEnable). - In this case, execute steps (16) and (17). - Otherwise the procedure SHALL stop. endrnote end

group opt rnote over E #FFFFFF [16]

If immediate Profile enabling was granted in step (5), the eUICC SHALL enable the Profile and generate enable Notifications as configured. endrnote end

rnote over IPA #FFFFFF [17]

IPA SHALL retrieve and send any new Notifications generated due to the Profile enabling to Notification Receivers according to section 3.5 of SGP.22 [4]. Endrnote @enduml

Figure 9    Direct Profile Download

Start Conditions:

In addition to the start conditions required by the Common Mutual Authentication procedure defined in section 3.1.2 of SGP.22 [4], this procedure requires the following start conditions depending on the following exclusive options in step 1:

Option (a) use of an Activation Code: The eIM or IPA has an Activation Code that is coded as defined in section 4.1 of SGP.22 [4].

Option (b) use of SM-DS: The eIM or the IPA has previously been triggered to perform Event Retrieval and has the SM-DP+ Address and EventID from an SM-DS, as an outcome of the procedure defined in sections 3.9.2.1 or 3.9.2.2.

Option (c) use of default SM-DP+: The eIM or the IPA has been triggered to perform the Profile download from the default SM-DP+. The triggered entity (IPA/eIM) knows the default SM-DP+ Address (e.g. by IPA having called the function ES10a.GetEuiccConfiguredAddresses or by eIM having sent an eIM Package containing an IpaEuiccDataRequest).

NOTE:How the eIM is triggered is out of scope of this version of the specification. How the IPA is triggered could be through received ProfileDownloadTriggerRequest containing contactDefaultSmdp or by IoT Device specific means.

The Emergency Profile is not enabled.

Procedure:

1. If option (a) is used and the Activation Code is available to the eIM, the eIM parses the
   Activation Code and finds the SM-DP+ address, Activation Code Token, and optional
   SM-DP+ OID. If the format of the Activation Code is invalid, the procedure SHALL stop.
2. In case of a Profile download trigger from an eIM Package: a secure connection is
   established between the IPA and the eIM for the IPA to obtain the eIM Package. How
   this is triggered is out of scope of this specification. There are two options for the
   delivery of the eIM Package to the IPA:

•The eIM Package Retrieval Procedure defined in section 3.1.1.1 is executed between the IPA and the eIM, or

•The eIM Package Injection Procedure defined in section 3.1.1.2 is executed between the IPA and the eIM.

3. The IPA parses the eIM Package received in step 2. The IPA identifies if the eIM
   Package contains a ProfileDownloadTriggerRequest. If option (a) is used this
   trigger SHALL contain the Activation Code. If option (b) is used this trigger contains the
   SM-DP+ Address and EventID (formatted as an Activation Code). If option (c) is used
   this trigger contains instruction to use the default SM-DP+ Address. If the format of the
   trigger profile download eIM Package is invalid, or data needed by IPA to perform the
   profile download is missing the IPA SHALL return invalidPackageFormat error and
   the procedure SHALL stop.
4. If option (a) is used, the IPA parses the Activation Code and finds the SM-DP+ Address,
   Activation Code Token, and optional SM-DP+ OID. If the format of the Activation Code
   is invalid the IPA SHALL return invalidPackageFormat error and the procedure
   SHALL stop.
5. The common mutual authentication procedure defined in section 3.1.2 of SGP.22 [4]
   SHALL be executed. When this procedure is used for Profile download and installation,
   SM-XX         is     SM-DP+.        CERT.XXauth.ECDSA,         PK.XXauth.ECDSA           and
   SK.XXauth.ECDSA            are      CERT.DPauth.ECDSA,         PK.DPauth.ECDSA           and
   SK.DPauth.ECDSA respectively. ESXX is ES9+.
   During the common mutual authentication procedure at step (10) in section 3.1.2 of
   SGP.22 [4], the IPA SHALL verify that the SM-DP+ OID contained in the
   CERT.DPauth.ECDSA returned by the SM-DP+ is identical to the SM-DP+ OID if the
   IPA has acquired it from the Activation Code at step (1). If the comparison fails, the
   procedure SHALL stop.
   During the common mutual authentication procedure at step (10) in section 3.1.2 of
   SGP.22 [4], the IPA SHALL build the ctxParams1 data object to provide the MatchingID,
   Device Info to the eUICC for signature. The value of the MatchingID SHALL be set as
   follows:
        • If an Activation Code is used (option (a)), the MatchingID value SHALL be set
             to Activation Code Token.
        • If an SM-DS is used (option (b)), the MatchingID value SHALL be set to EventID.
        • If a default SM-DP+ is used (option (c)), the MatchingID SHALL be missing.
   If immediate Profile enabling is activated, the eUICC SHALL verify that the download
   is coming from the default SM-DP+ configured in the eUICC. If the verification is
   successful, the eUICC SHALL grant immediate enabling for this Profile.
6. After having successfully authenticated the eUICC at the end of the step (5) above, the
   SM-DP+ SHALL:
        • Verify that there is a related pending Profile download order for the provided
             MatchingID.
        • If this Profile download order is already linked to an EID, verify that it matches
             the EID of the authenticated eUICC.
        • Verify that the Profile corresponding to the pending Profile download order is in
             'Released' state, or, in case of a retry due to a previous installation failure, in
             'Downloaded' state (section 3.1.6 of SGP.22 [4]).
   If any of these verifications fail, the SM-DP+ SHALL return the relevant error status and
   the procedure SHALL stop.
   The SM-DP+ SHALL increment the count of download attempts for the identified Profile.
   If the maximum number of attempts has been exceeded, the SM-DP+ SHALL terminate
   the corresponding Profile download order and notify the Operator by calling the
   "ES2+.HandleDownloadProgressInfo" function with an operation status indicating
   'Failed' with the relevant error status, and the procedure SHALL be stopped. Otherwise,
   the SM-DP+ SHALL perform appropriate eligibility checks, based on the Device Info
   and/or eUICCInfo2. These checks SHALL include the check if the eUICC can install
   one more Profile. See Annex F of SGP.22 [4] for more information on Eligibility checks.
7. (Optional step) Depending on the agreed behaviour with the Operator (out of scope of
   this specification), the SM-DP+ SHALL notify the Operator with the outcome of the
   eligibility check using the function “ES2+.HandleDownloadProgressInfo”. The SM-DP+
   SHALL provide the EID, the ICCID, the identification of the point reached (in that case
   it SHALL be ‘Eligibility check’), the timestamp when this point was reached, and the
   execution result of this step.

NOTE:This notification step MAY be done asynchronously.

8. If the eligibility check fails, the SM-DP+ SHALL:
            • set the Profile corresponding with the pending Profile download order in
                 ‘Error’ state (section 3.1.6 of SGP.22 [4]).
            • return an error status to the IPA and the procedure SHALL stop.
    Otherwise, the SM-DP+ SHALL:
            • Determine whether the Profile is already bound to the EID from a previous
                 unsuccessful download attempt. If so, the SM-DP+ MAY include the
                 otPK.Euicc.ECKA obtained in the previous session in the smdpSigned2
                 data structure.
            • Determine if a Confirmation Code is required for this pending order.

NOTE:How the Confirmation Code is sent to the IoT Device is out of the scope of this specification.

•Generate a smdpSigned2 data structure containing the TransactionID and the Confirmation Code Required Flag. • Compute the smdpSignature2 over smdpSigned2 and euiccSignature1 using the SK.DPpb.ECDSA. 9. The SM-DP+ returns the TransactionID, ProfileMetadata, smdpSigned2, smdpSignature2 and CERT.DPpb.ECDSA to the IPA. 10. On reception of the SM-DP+ response, the IPA that SHALL verify the Profile Metadata according to steps 7a, b, c and 8 of section 3.1.3 (Profile Download and Installation) of SGP.22 [4]. For these verifications, the IPA MAY use previously fetched Rules Authorisation Table and/or list of installed Profiles. If the IPA has not already fetched the required information, the IPA SHALL request those from the eUICC by calling the ES10b.GetRAT and/or ES10b.GetProfilesInfo functions. If one of the verification fails, the IPA SHALL trigger the cancellation of the on-going RSP session and terminate the procedure. 11. The IPA and eUICC process ES10b.PrepareDownload function call as defined in section 5.7.5 of SGP.22 [4] and the ongoing RSP session SHALL continue with the sub-procedure Profile Download and Installation – Download Confirmation as defined in section 3.1.3.2 of SGP.22 [4] with the following changes: • Upon any error returned in the verifications of ES10b.PrepareDownload, the eUICC SHALL terminate the RSP Session.

12. The IPA installs the Profile to the eUICC as defined in section 3.1.3.3 (Sub-procedure
    Profile Installation) of SGP.22 [4]. If the Profile to be downloaded is an Emergency
    Profile, i.e. contains the ecallIndication data element set to TRUE within its
    Profile Metadata, the eUICC SHALL stop the procedure and return
    incorrectInputValues if either the eUICC does not support the Emergency
    Mechanism, or the eUICC supports the Emergency Mechanism and already contains
    an Emergency Profile with ecallIndication set to TRUE. The IPA SHALL then
    perform the Sub-procedure “Profile Download and installation – Download rejection”
    as defined in SGP.22[4] with reason code “metadataMismatch”.
13. In case of a Profile download trigger from an eIM Package: the IPA SHALL send the
    ProfileDownloadTriggerResult to the eIM as defined in section 2.11.2.3 by
    using the function "ESipa.HandleNotification".

NOTE:This step is executed whenever an error is reported between steps 5 and 12.

14. On reception of the "ES9+.HandleNotification" function, the SM-DP+ SHALL proceed
    as defined in section 3.1.3.3 of SGP.22 [4] step 8 to 10.
15. If default SM-DP+ was used, the IPA MAY request immediate Profile enabling by
    calling ES10b.ImmediateEnable. In this case steps (16) and (17) SHALL be executed.
    Otherwise, the procedure SHALL stop.
16. If immediate Profile enabling was granted in step (5), the eUICC SHALL enable the
    Profile and generate enable Notifications as configured.
17. The IPA SHALL retrieve and send any new Notifications generated due to the Profile
    enabling to Notification Receivers according to section 3.5 of SGP.22 [4].

3.2.3.2 Indirect Profile Download

This section describes the indirect Profile download and installation procedure where the eIM is used as a proxy between the IoT Device and the SM-DP+.

@startuml

hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid

participant "<b>SM-DP+" as DP participant "<b>eIM" as EIM participant "<b>IPA" as IPA participant "<b>eUICC" as E

group If option (a) and AC is available to eIM rnote over EIM : [1] eIM parses the AC to retrieve SM-DP+ Address, Activation Code Token, [SM-DP+ OID] end

group If IPA obtains a Profile download trigger from eIM Package alt IPA-initiated rnote over EIM, IPA : [2a] eIM Package Retrieval Procedure including secure connection establishment (section 3.1.1.1) else eIM-initiated rnote over EIM, IPA : [2b] eIM Package Injection Procedure including secure connection establishment (section 3.1.1.2) end

rnote over IPA : [3] IPA parses the eIM Package that contains \n ProfileDownloadTriggerRequest end

group If option (a) and AC is available to IPA rnote over IPA : [4] IPA parses AC to retrieve SM-DP+ Address, Activation Code Token, [SM-DP+ OID] end

opt Get euiccInfo1 if not yet retrieved by IPA or eIM IPA -> E : [5] ES10b.GetEuiccInfo E --> IPA : euiccInfo1 end IPA -> E : [6] ES10b.GetEuiccChallenge

E -> IPA : euiccChallenge

group If a secure connection is not yet established rnote over EIM, IPA : [7] Establish secure connection end IPA -> EIM : [8] ESipa.InitiateAuthentication request rnote over EIM, DP : [9] Establish HTTPS connection rnote over EIM, DP : [10] ES9+'.InitiateAuthentication function EIM -> IPA : [11] ESipa.InitiateAuthentication response rnote over IPA, E: [12] ES10b.AuthenticateServer function IPA -> EIM : [13] ESipa.AuthenticateClient request rnote over EIM, DP : [14] ES9+'.AuthenticateClient function EIM -> IPA : [15] ESipa.AuthenticateClient response rnote over IPA, E: [16] ES10b.PrepareDownload function IPA -> EIM : [17] ESipa.GetBoundProfilePackage request rnote over EIM, DP : [18] ES9+'.GetBoundProfilePackage function EIM -> IPA : [19] ESipa.GetBoundProfilePackage response group Profile Installation Procedure rnote over IPA, E : [20] Profile Installation group opt rnote over IPA #FFFFFF [21]

If default SM-DP+ used, the IPA MAY request immediate Profile enabling (ES10b.ImmediateEnable). Otherwise, continue in step (23). endrnote end

group opt rnote over E #FFFFFF [22]

If immediate Profile enabling was granted in step (12), the eUICC SHALL enable the Profile and generate enable Notifications as configured. endrnote end

rnote over DP, E : [23] Notification Handling

IPA -> EIM : [a] ESipa.HandleNotification EIM -> IPA : [b] ACK IPA -> E : [c] ES10b.RemoveNotificationFromList EIM -> DP : [d] ES9+'.HandleNotification end rnote over DP : [24] Step 8-10 section 3.1.3.3 of SGP.22 @enduml

Figure 10 Indirect Profile Download and Installation

Start Conditions:

In addition to the start conditions required by the Common Mutual Authentication procedure defined in section 3.1.2 of SGP.22 [4], this procedure requires the following start conditions depending on the following exclusive options in step 1:

Option (a) use of an Activation Code: The eIM or IPA has an Activation Code that is coded as defined in section 4.1 of SGP.22 [4].

Option (b) use of SM-DS: The eIM has retrieved the SM-DP+ Address and EventID from the SM-DS, as defined in section 3.9.2.2 of this document.

Option (c) use of default SM-DP+: The eIM or the IPA has has been triggered to perform the Profile download from the default SM-DP+. The triggered entity (IPA/eIM) knows the default SM-DP+ Address (e.g.: by IPA having called the function ES10a.GetEuiccConfiguredAddresses or by eIM having sent an eIM Package containing an IpaEuiccDataRequest).

The Emergency Profile is not enabled.

IPA indicated in IPA Capability the support of indirectRspServerCommunication.

The eIM indicated the support of indirectProfileDownload.

Procedure:

1. If option (a) is used and the Activation Code is available to the eIM, the eIM parses the
   Activation Code and finds the SM-DP+ address, Activation Code Token, and optional
   SM-DP+ OID. If the format of the Activation Code is invalid, the procedure SHALL stop.
2. In case a Profile download trigger from an eIM Package: a secure connection is
   established between the IPA and the eIM for IPA to obtain the eIM Package. How this
   is triggered is out of scope of this specification. There are two options for the delivery
   of the eIM Package to the IPA:

a)The eIM Package Retrieval Procedure steps 1 to 4 as defined in section 3.1.1.1 are executed between the IPA and the eIM.

b)The eIM Package Injection Procedure steps 1 and 2 as defined in section 3.1.1.2 are executed between the IPA and the eIM.

3. The IPA parses the eIM Package received in step 2. The IPA identifies that the eIM
   Package          contains       a      ProfileDownloadTriggerRequest.                   If
   ProfileDownloadTriggerRequest data object is empty (i.e., without
   profileDownloadData), then the Procedure continues in step 5. If option (a) is used
   this trigger MAY contain the Activation Code. Alternatively, the eIM handles the AC
   (see IPA Capability eimDownloadDataHandling). If option (b) is used this trigger
   MAY contain the SM-DP+ Address and EventID (formatted as an Activation Code), if
   handled by IPA. If option (c) is used this trigger MAY contain information to use the
   default SM-DP+ Address. If the format of the trigger profile download eIM Package is
   invalid, or data needed by IPA to perform the profile download is missing the IPA
   SHALL return invalidPackageFormat error and the procedure SHALL stop.
4. If the IPA retrieved an Activation Code in step 3, or if IPA retrieved an Activation Code
   by some other means outside of this specification before the start of this procedure,
    the IPA parses the Activation Code and finds the SM-DP+ address, Activation Code
    Token, and optional SM-DP+ OID. If the format of the Activation Code is invalid the IPA
    SHALL return invalidPackageFormat error and the procedure SHALL stop.
5. If euiccInfo1 is not yet retrieved by the eIM or IPA, the IPA MAY request euiccInfo1
    from the eUICC by calling ES10b.GetEuiccInfo (see section 5.9.2).
6. The IPA requests an eUICC Challenge from the eUICC by calling the
    ES10.GetEUICCChallenge function (see section 5.9.3).
7. A secure connection is established between the IPA and the eIM if it is not yet
    established.
8. The IPA calls ESipa.InitiateAuthentication function comprising eUICC Challenge,
    optionally SM-DP+ FQDN, and optionally euiccInfo1(see IPA Capability
    minimizeEsipaBytes) and eimTransactionId (if included by eIM in
    ProfileDownloadTriggerRequest). If the IPA does not provide SM-DP+ FQDN
    or euiccInfo1, the eIM SHALL identify the relevant information.
9. The eIM establishes an HTTPS connection with the SM-DP+ in server authentication
    mode according to SGP.22 [4].
10. The eIM and the SM-DP+ process ES9+'.InitiateAuthentication function comprising
    eUICC Challenge, SM-DP+ FQDN, and euiccInfo1 as defined in section 5.6.1 of
    SGP.22 [4]. If the SM-DP+ FQDN provided in ES9+'.InitiateAuthentication in step 9 did
    not come from IPA (was not obtained from IPA in step 7 e.g., due to IPA has capability
    eimDownloadDataHandling), the eIM SHALL verify that this SM-DP+ FQDN
    matches the SM-DP+ FQDN returned by the SM-DP+ (in serverSigned1). If not, the
    procedure SHALL be stopped. If the Activation Code contains the SM-DP+ OID and is
    available to the eIM, the eIM SHALL check that the SM-DP+ OID from the AC matches
    the SM-DP+ OID of the SM-DP+ Certificate (serverCertificate). If not, the procedure
    SHALL be stopped.
11. The eIM sends the ESipa.InitiateAuthentication response to the IPA, based on the
    ES9+'.InitiateAuthentication response from the SM-DP+. The eIM SHALL additionally
    provide ctxParams1 as defined in SGP.22 [4] if the IPA does not generate it (see IPA
    capability eimCtxParams1Generation).
12. The IPA and eUICC process ES10b.AuthenticateServer function call as defined in
    section 5.7.13 of SGP.22 [4]. If immediate Profile enabling is activated, the eUICC
    SHALL verify that the download is coming from the default SM-DP+ configured in the
    eUICC. If the verification is successful, the eUICC SHALL grant immediate enabling for
    this Profile.
13. The IPA calls ESipa.AuthenticateClient function comprising euiccSigned1 or
    compactEuiccSigned1, euiccSignature1, optionally CERT.EUM.ECDSA, and
    optionally CERT.EUICC.ECDSA. If the IPA does not provide CERT.EUM.ECDSA and
    CERT.EUICC.ECDSA and/or provide the compactEuiccSigned1 instead of
    euiccSigned1 (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify
    the relevant information and build euiccSigned1.
14. The eIM and SM-DP+ process the ES9+'.AuthenticateClient function as defined in
    5.6.3 of SGP.22 [4].
15. The eIM sends the ESipa.AuthenticateClient response to the IPA, based on the
    ES9+'.AuthenticateClient response from the SM-DP+. If the response returns an error,
    IPA SHALL trigger the cancellation of the on-going RSP session (see section 3.2.3.3)
    with reason undefinedReason and the procedure SHALL stop.

•If the IPA is capable of verifying the Profile Metadata, the eIM SHALL provide the Profile Metadata to IPA that SHALL verify the Profile Metadata according to section 3.2.3.1 (Direct Profile Download) step 10. For this verification, the IPA MAY use previously fetched Rules Authorisation Table and/or list of installed Profiles. If the IPA has not already fetched the required information, the IPA SHALL request those from the eUICC by calling the ES10b.GetRAT and/or ES10b.GetProfilesInfo functions. If the verification fails, the IPA SHALL trigger the cancellation of the on- going RSP session (see section 3.2.3.3) and the procedure SHALL stop. • If the IPA is not capable of verifying the Profile Metadata (see IPA Capability eimProfileMetadataVerification) according to section 3.1..3 (Profile Download and Installation) of SGP.22 [4], the eIM SHALL verify the Profile Metadata according to steps 7a, b, c and 8 of section 3.1.3 (Profile Download and Installation) of SGP.22 [4] and SHALL NOT provide the Profile Metadata to IPA. For this verification, the eIM SHALL use Rules Authorisation Table and information on installed Profiles available to the eIM, e.g., obtained prior to the start of this procedure using the PSMOs getRAT and listProfileInfo. If the verification fails, the eIM SHALL return an error code to IPA and the procedure SHALL stop. The error code triggers IPA to cancel the on-going RSP session with SM-DP+ according to section 3.2.3.3. The cancel session reason (pprNotAllowed) to be used by IPA when calling the ESipa.CancelSession is given by the error code. 16. The IPA and eUICC process ES10b.PrepareDownload function call as defined in section 5.7.5 of SGP.22 [4] with the following change: • Upon any error returned in the verifications of ES10b.PrepareDownload, the procedure SHALL stop and the eUICC SHALL terminate the RSP Session

17. The IPA calls ESipa.GetBoundProfilePackage function comprising euiccSignature2
    and either euiccSigned2 or compactEuiccSigned2. If compactEuiccSigned2 is provided
    (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify the relevant
    information and build euiccSigned2.
18. The eIM and SM-DP+ process ES9+'.GetBoundProfilePackage function as defined in
    section 5.6.2 of SGP.22 [4].

NOTE:In the ES9+'.GetBoundProfilePackage function request, the eIM forwards the ESipa.GetBoundProfilePackage function request.

19. The eIM sends the ESipa.GetBoundProfilePackage response to the IPA, based on the
    ES9+'.GetBoundProfilePackage response from the SM-DP+. If the eIM or IPA
    previously verified the Profile Metadata in step (14), the eIM or IPA SHOULD check if
    the Profile Metadata has been changed. If so, IPA SHALL be triggered to cancel the
    on-going RSP session with the SM-DP+ (see section 3.2.3.3) with cancel session
    reason metadataMismatch and the procedure SHALL be terminated. In case of eIM
    performing the check (see IPA Capability eimProfileMetadataVerification),
    the eIM SHALL return an error code that triggers IPA to cancel the session and also
    indicates the cancel session reason (metadataMismatch) to be used.
20. The IPA installs the Profile to the eUICC as defined in section 3.1.3.3 (Sub-procedure
    Profile Installation) of SGP.22 [4]. In case of errors during the installation of the Profile
    the cancel session procedure in section 3.2.3.3 is triggered with cancel session reason
    loadBppExecutionError and the procedure SHALL stop. If the Profile to be downloaded
is an Emergency Profile, i.e. contains the ecallIndication data element set to
TRUE within its Profile Metadata, the eUICC SHALL stop the procedure and return
incorrectInputValues if either the eUICC does not support the Emergency
Mechanism, or the eUICC supports the Emergency Mechanism and already contains
an Emergency Profile with ecallIndication set to TRUE. The IPA SHALL then
perform the Sub-procedure “Profile Download and installation – Download rejection” as
defined in SGP.22[4] with reason code “metadataMismatch”.
21. If default SM-DP+ was used, the IPA MAY request immediate Profile enabling by
    calling ES10b.ImmediateEnable and the procedure SHALL continue with step (22).
    Otherwise, the procedure SHALL continue in step (23).
22. If immediate Profile enabling was granted in step (12), the eUICC SHALL enable the
    Profile and generate enable Notifications as configured.
23. The following changes are made to the Notification procedure compared to section
    3.1.3.3 of SGP.22 [4]:

a)The IPA calls ESipa.HandleNotification function comprising PendingNotification data object that contains ProfileInstallationResult that contains the TransactionID generated by the SM-DP+. If a compact version of the ProfileInstallationResult is provided (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify the relevant information and build the full ProfileInstallationResult. b) The eIM acknowledges the reception of the ProfileInstallationResult. c) Upon acknowledgement of successful reception of the ProfileInstallationResult, IPA calls the ES10b.RemoveNotificationFromList function with corresponding seqNumber as input parameter and the eUICC deletes the ProfileInstallationResult from its memory. d) The eIM and SM-DP+ process ES9+’.HandleNotification function as defined in section 5.7.4 of this document.

24. On reception of the ES9+’.HandleNotification function, the SM-DP+ SHALL proceed as
    defined in section 3.1.3.3 of SGP.22 [4] step 8 to 10.

3.2.3.3 Cancel Session Procedure for Indirect Profile Download

This section describes the cancel session call flow used to cancel an indirect Profile download session. This procedure can occur due to an error at the following steps of the protocol:

•      after the response to "ESipa.AuthenticateClient"
•      after the response to "ESipa.GetBoundProfilePackage"

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>SM-DP+" as DP participant "<b>eIM" as eIM

participant "<b>IPAd" as IPA participant "<b>eUICC" as E

IPA -> E : [1] ES10b.CancelSession(TransactionID, reason)
rnote over E
[2]
- Generate euiccCancelSessionSigned = {
     TransactionID, reason}
- Compute euiccCancelSessionSignature
     over euiccCancelSessionSigned
endrnote

E --> IPA : [3] cancelSessionResponseOk

rnote over IPA [Stop procedure if the reason is undefinedReason] endrnote

IPA -> eIM : [4] ESipa.CancelSession(TransactionID, cancelSessionResponseOk) eIM -> DP : [4] ES9+’.CancelSession(TransactionID, cancelSessionResponseOk)

rnote over DP [5] - Retrieve the on-going RSP session - Verify euiccCancelSessionSignature - Verify the SM-DP+ OID endrnote DP --> eIM : [ERROR] eIM --> IPA : [ERROR]

rnote over DP [6] Process the reason according to SGP.22 [4] endrnote

DP --> eIM : [10] OK eIM --> IPA : [10] OK @enduml

Figure 11 Cancel Session Procedure

Start Conditions:

This procedure can be used in the following cases.

Reasons in the response to "ESipa.AuthenticateClient":

•   The IPAd receives “pprNotAllowed” error in the response to "ESipa.AuthenticateClient"
    due to that eIM, when verifying the Profile Metadata, discovered that the PPR(s) in the
    Profile Metadata are not allowed according to the Rules Authorisation Table, or PPR1
    is present in the Profile Metadata and an Operational Profile is already installed on the
    eUICC. In this case the reason code for step (1) SHALL be pprNotAllowed.
•   The IPAd receives any other error in the response to "ESipa.AuthenticateClient". In
    this case the reason for step (1) SHALL be undefinedReason.

Cancel reasons after "ESipa.AuthenticateClient" related to Profile download:

•The IPAd verifies Profile Metadata and discovers that the PPR(s) in the Profile Metadata are not allowed according to the Rules Authorisation Table, or PPR1 is present in the Profile Metadata and an Operational Profile is already installed on the eUICC. In these cases, the reason code for step (1) SHALL be pprNotAllowed.

Reasons in the response to "ESipa.GetBoundProfilePackage":
   • The IPAd receives             metadataMismatch error in the response to
      "ESipa.GetBoundProfilePackage" due to that eIM discovered that the Profile Metadata
      in the Bound Profile Package does not match the Profile Metadata received previously
      in the response to "ES9+’.AuthenticateClient". In this case the reason code for step (1)
      SHALL be metadataMismatch.

Cancel reasons after "ESipa.GetBoundProfilePackage":

•   The IPAd discovers that the Profile Metadata in the Bound Profile Package does not
    match the Profile Metadata received previously in the response to
    "ESipa.AuthenticateClient". In this case the reason for step (1) SHALL be
    metadataMismatch.
•   The IPAd has encountered an error while installing a Bound Profile Package. In this
    case the reason for step (1) SHALL be loadBppExecutionError.

Procedure:

1. The IPAd SHALL call the "ES10b.CancelSession" function with input data comprising
   the TransactionID and the reason.
2. The eUICC SHALL:
       • Generate the euiccCancelSessionSigned data object containing the
           TransactionID and the reason provided by the IPAd.
       • Compute the euiccCancelSessionSignature over euiccCancelSessionSigned
           using       the     SK.EUICC.ECDSA           corresponding     to     the
           euiccCiPKIdentifierToBeUsed as received during the common mutual
           authentication procedure.
3. The      eUICC       SHALL     return    the    euiccCancelSessionSigned     and
   euiccCancelSessionSignature. If the reason is undefinedReason, the IPAd SHALL
   ignore the response from the eUICC and stop the procedure.
4. The IPAd SHALL call the "ESipa.CancelSession" function with input data comprising
   TransactionID, euiccCancelSessionSigned and euiccCancelSessionSignature. Upon
   receiving the "ESipa.CancelSession" function call, the eIM SHALL call the
   "ES9+’.CancelSession" function with the input data from "ESipa.CancelSession".
5. On reception of the "ES9+’.CancelSession" function, the SM-DP+ SHALL:
       • Retrieve the on-going RSP session identified by the TransactionID. If the
           TransactionID is unknown, the SM-DP+ SHALL return a function execution
           status 'Failed' with relevant status code and the procedure SHALL stop.
       • Verify         the       euiccCancelSessionSignature         performed      over
           euiccCancelSessionSigned using the PK.EUICC.ECDSA associated with the
           ongoing RSP session. If the signature is invalid, the SM-DP+ SHALL return a
           function execution status 'Failed' with relevant status code and the procedure
           SHALL stop.
       • Verify that the received OID is the same value as the one contained in the
           CERT.DPauth.ECDSA used during the common mutual authentication
           procedure. If the value does not match, the SM-DP+ SHALL return a function
           execution status 'Failed' with relevant status code and the procedure SHALL
           stop.
6. The SM-DP+ SHALL process the error reason according to steps 5 to 7 in Section
   3.1.3.1 of SGP.22 [4].
7. The SM-DP+ SHALL return a function execution status 'Executed-Success' and the
   procedure SHALL stop. The eIM returns the function execution status from
   "ES9+’.CancelSession" function as the function execution status of
   "ESipa.CancelSession".

3.3 eUICC Package Handling

3.3.1 Generic eUICC Package Download and Execution

This procedure describes the download of an eUICC Package contained within an eIM
Package. It also describes how to process the eUICC Package and how to return a signed
result of the eUICC Package execution to the eIM.
      NOTE:       The Sub-procedures for Profile State Management, described in section 3.4,
                  and eIM Configuration, as described in section 3.5.1, are executed in step 5
                  of the procedure described in this section.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF skinparam ParticipantPadding 70 hide footbox

participant "<b>SM-DP+" as DP participant "<b>eIM" as eIM participant "<b>IPAd" as IPA participant "<b>eUICC" as E participant "<b>Device Baseband" as DevBB

rnote left IPA [1] - Build euiccPackageSigned = {eimId, eidValue, counterValue, [eimTransactionId], euiccPackage}

and compute eimSignature over euiccPackageSigned - Build eIMPackage endrnote

rnote over eIM, IPA: [2] Transfer eIM Package containing signed \n eUICC Package from eIM to IPAd (see section 3.1.1)

group Process the eIM Package IPA -> E : [3] ES10b.LoadEuiccPackage (eUICC Package)

rnote over E: [4] Verify the eIM signature \nand check EID and replay counter

E --> IPA : [ERROR]

loop Up to the number of\n PSMOs/eCOs in the eUICC Package rnote over E [5] Execute PSMO/eCO endrnote end

rnote over E: [6] Generate and sign the result of the eUICC Package \nincluding eUICC sequence number

end E -> IPA : [7] Signed eUICC Package Result opt Any marked Profile opt "to be disabled", "to be disabled and deleted", or "to be enabled" E -> DevBB: [8a] REFRESH DevBB -> E: Terminal Response or RESET End opt rnote over E [8b] The marked Profile(s) are enabled, disabled and/or deleted endrnote

rnote over DevBB [Network attach procedure with the newly enabled Profile] end rnote end opt

group If the IPAd sends eUICC Package Result and Notifications to the eIM in a single eIM Package Result IPA -> E : [9] ES10b.RetrieveNotificationsList E -> IPA : List of pending Notifications end

rnote over eIM, IPA: [10] Transfer eIM Package Result containing signed eUICC Package Result \nand optionally Notifications list from IPAd to eIM (see section 3.1.1)

rnote over eIM: [11] Extract eUICC Package Result, \nverify the eUICC signature and check \nsequence number to prevent replay

rnote over eIM: [12] Process the result of the eUICC Package

rnote over eIM, IPA: [13] Acknowledge successfully received signed eUICC Package Result\n and Notifications if any. group [14] For each pending Notification obtained by the eIM in step 10 eIM -> DP : ES9+’.HandleNotification DP -> eIM : ACK end

group Delete eUICC Package Result and Notifications

loop IPA -> E : [15] ES10b.RemoveNotificationFromList

rnote over E: [16] Delete eUICC Package Result / Notification end end

group [17] If IPAd sends Notifications using ES9+.HandleNotification or ESipa.HandleNotification rnote over DP, E #FFFFFF : [Refer to procedure Notification Delivery to Notification Receivers] end

@enduml

Figure 12 Generic eUICC Package Download and Execution

Start Condition:
This procedure requires the following start conditions:
      •   The eUICC is associated with the eIM and has the eIM public key and eIM ID.
•   The eIM has received a request to perform a PSMO/eCO for the particular eUICC
    and has the EID of the eUICC in its storage along with the current value of the
    counter for replay protection as well as the relevant information of the target Profile in
    the eUICC.
•   A Secure Connection between the eIM and the IPA is established.
Procedure:
   1. The eIM SHALL prepare the eUICC Package structure including signing the eUICC
      Package using the eIM private key. The signed data includes, for the particular eUICC,
      the eIMID, the EID and the current value incremented by 1 of the counters for replay
      protection of eUICC Packages obtained from eIM storage. The current value of the
      counter for replay protection in eIM storage is updated accordingly. The eIM then builds
      the eIM Package containing the signed eUICC Package. eimTransactionId, if
      included, MAY be used for linking an eUICC Package with an eUICC Package Result.
   2. The eIM SHALL transfer the eIM Package (containing the signed eUICC Package) to
      the IPAd as described in section 3.1.1.
   3. IPAd then processes the eIM Package. The IPAd SHALL call
      ES10b.LoadEuiccPackage to provide the signed eUICC Package to the eUICC.
   4. The eUICC SHALL verify the eIM signature and check the EID and replay counter. See
      details in section 5.9.1. In case of error, the eUICC SHALL return an error message
      and the procedure SHALL stop.
   5. If all verifications are successful, the eUICC SHALL process the eUICC Package. The
      PSMOs or eCOs in the eUICC Package SHALL be executed sequentially by the eUICC
      until the end is reached or an error is encountered for a PSMO/eCO. If an interruption
      (e.g. power loss) occurs during the processing of the ES10b.LoadEuiccPackage
      function, the eUICC SHALL restore its original state prior to execution, see details in
      section 5.9.1.
   6. The eUICC SHALL generate the result of the eUICC Package execution and sign it
      using the eUICC private key SK.EUICC.ECDSA. The signed data includes the next
      (not used) value of the eUICC sequence number (defined in SGP.22 [4] for use with
      Notifications) and the eUICC sequence number is incremented by 1 within the eUICC.
      The eUICC SHALL update the stored counter value to the counter value of the signed
      eUICC Package received in step 4.
   7. The IPAd obtains the signed eUICC Package Result from the eUICC.
   8. any Profile is marked as "to be disabled", "to be disabled and deleted", "to be enabled",
      or "to be deleted"
          a. If any Profile is marked as "to be disabled", "to be disabled and deleted", or "to
               be enabled", the eUICC SHALL send the REFRESH command in "eUICC
               Profile State Change" mode (if supported by the Device) or "UICC Reset" mode
               to the Device, according to ETSI TS 102 223 [5], to prepare the IoT Device for
               a change in Profile state.

NOTE:Enabling or disabling via PSMO always uses REFRESH.

b. Upon reception of the Terminal Response or after the RESET, or in case the
   REFRESH command is not sent, the ISD-R SHALL:
   • If a Profile is marked "to be disabled": disable the marked Profile.
            •   If a Profile is marked "to be disabled and deleted": disable the marked
                Profile and then delete it.
            •   If a Profile is marked "to be enabled": enable the marked Profile.
            •   If a Profile is marked "to be deleted": delete the marked Profile.
            •   If any marked Profile is successfully enabled, disabled, or deleted in the
                previous steps, generate as many Notifications as configured in each
                Profile Metadata (notificationConfigurationInfo) in the format of
                OtherSignedNotification.
            •   Unmark all marked Profiles.
    •
    If a Profile is now in Enabled state, the IoT Device baseband executes the network
    attach procedure.
9. If the IPAd sends eUICC Package Result and Notifications to the eIM in a single eIM
    Package Result and if the eUICC Package contains PSMO(s), the IPAd SHALL
    retrieve pending Notifications by calling ES10b.RetrieveNotificationsList function.
10. The IPAd SHALL transfer the eIM Package Result containing the signed eUICC
    Package Result to the eIM. The details on the transfer of the eIM Package Result
    depends on the underlying ESipa transport and is further described in section 3.1.1. If
    the IPAd sends eUICC Package Result and Notifications to the eIM in a single eIM
    Package Result (using ESipa.ProvideEimPackageResult), the IPAd SHALL, in case of
    a non-empty list of pending Notifications, include the list of pending Notifications
    (PendingNotificationList as defined in section 2.11.2.2) together with the
    signed eUICC Package Result in the eIM Package Result. In case of an IPAd with IPA
    Capability minimizeEsipaBytes, the IPAd SHOULD include each pending
    Notification in the list in compact format as described in section 5.14.7.
    If the IPAd does not send Notifications together with the eUICC Package Result, the
    IPAd MAY use ESipa.HandleNotification instead to send the eUICC Package Result
    to the eIM.
    If the IPAd fails sending the eIM Package Result to the eIM due to a lack of connectivity,
    it SHOULD apply the Profile Rollback procedure described below.
11. The eIM SHALL extract the eUICC Package Result and verify the eUICC signature of
    the signed eUICC Package Result using the public key PK.EUICC.ECDSA of the
    eUICC obtained from the eUICC Certificate in the eIM storage. Upon successful
    verification, the eIM SHALL retrieve the counter value included in the eUICC Package
    Result and map it to the related eUICC Package. It SHALL then check that the
    sequence number contained in the eUICC Package Result is greater than the value of
    the sequence number currently stored in the eIM for the particular eUICC. If all checks
    are successful, the eIM SHALL update the stored value of the sequence number for
    the particular eUICC to the value of the signed eUICC Package Result. If any of the
    checks fail, the eIM SHALL stop the processing of the eUICC Package Result. In case
    the eIM received pending Notifications in step 10, the eIM continues the execution in
    step 13 to acknowledge the received Notifications (but not the eUICC Package Result)
    and sends the received Notifications to Notification Receivers (see step 14).
12. The eIM SHALL process the result of the eUICC Package execution.
13. If the eIM Package Result was transmitted using the ESipa.ProvideEimPackageResult
    function (resp. the response to ESipa.TransferEimPackage), then the eIM SHALL
    acknowledge the signed eUICC Package Result and Notifications (if any) that were
    successfully processed by sending their sequence numbers in the response to
    ESipa.ProvideEimPackageResult (resp. the next call to ESipa.TransferEimPackage).
14. If the If the eIM Package Result was transmitted using ESipa.HandleNotification, then
    the eIM does not acknowledge the signed eUICC Package Result and received
    Notifications (if any). In case the eIM received pending Notifications in step 10, the eIM
    SHALL forward them to the Notification Receivers. If a pending Notification is in
    compact format (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify
    the relevant information and build the full pending Notification before forwarding the
    Notification to the Notification Receiver.
15. IPAd SHALL call ES10b.RemoveNotificationFromList (see SGP.22 [4]) one or more
    times to delete the eUICC Package Result and pending Notifications for which
    acknowledgement has been received. The eUICC Package Result and each pending
    Notification to be deleted are identified by the sequence number(s) received in step 13.
16. The eUICC SHALL delete the eUICC Package Result or pending Notification from its
    memory.
17. If IPAd sends Notifications using ES9+.HandleNotification or ESipa.HandleNotification,
    the IPAd SHALL continue execution according to procedure “Notification Delivery to
    Notification Receivers.”

NOTE:Notifications (if any) needs to be send during this procedure by one of described means (either together with eUICC Package Results in step 10, or using ES9+.HandleNotification or ESipa.HandleNotification in step 17).

3.3.2 Profile Rollback Procedure

If the IPAd fails sending the eIM Package Result to the eIM due to a lack of connectivity, it SHOULD call the ES10b.ProfileRollback function (see section 5.9.16) to request the eUICC to roll back to the previously Enabled Profile (if any).

If the result of ES10b.ProfileRollback indicates successful processing (the eUICC returns 'ok'), then a new eUICC Package Result is available, and:

•    The IPAd SHALL discard the previous eIM Package Result, i.e., the IPAd SHALL
     NOT send the previous eIM Package Result to the eIM.
•    The IPAd SHALL build a new eIM Package Result including the new eUICC Package
     Result returned by the ES10b.ProfileRollback function and try to send this new eIM
     Package Result to the eIM.

NOTE1:When the ES10b.ProfileRollback is successful, the eUICC automatically discards the previous eUICC Package Result (see section 5.9.16) and there is no need for the IPAd to remove it from the eUICC. In particular, the ES10b.RemoveNotificationFromList function would return nothingToDelete(1) if the IPAd tried to do so.

NOTE2:As Profiles have returned to their states prior to the processing of the eUICC Package Request, as an optimization, the eUICC may discard Notifications (if any) generated by the processing of the eUICC Package Request and ES10b.ProfileRollback.

3.4 Profile State Management

3.4.1 Enable Profile

This procedure defines the execution of an Enable command contained within a eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution, used to enable a Profile already downloaded and installed on an eUICC.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC\n<b>IPA Services (ISD-R)" as IPAServices

rnote over IPAServices [1] Profile identification [2] Verify Profile state End rnote

rnote over IPAServices [3] Mark target Profile "to be enabled" and, if granted, record "usage of Rollback Mechanism is allowed"

endrnote

rnote over IPAServices
[4] Generate Enable PSMO execution result
     data structure (enableResult)
and continue as described in 3.3.1
endrnote
@enduml

Figure 13 Enable Profile

Start Conditions:

A Profile is already downloaded and installed in the eUICC. A eUICC Package containing an 'Enable Profile' is received within an "ES10b.LoadEuiccPackage" by the eUICC as described in 3.3.1 Generic eUICC Package Download and Execution.

The eIM signature the EID, and replay counter are verified as defined in 3.3.1 Generic eUICC Package Download and Execution.

Procedure:

If an Enable command has already been processed in this eUICC Package, then the ISD-R SHALL indicate a failure in the PSMO execution result and procedure SHALL continue in step 4.

1. The ISD-R SHALL find the target Profile with the ICCID. If the target Profile is not found,
   the ISD-R SHALL indicate a failure in the PSMO execution result with
   iccidOrAidNotFound(1) error code and procedure SHALL continue in step 4. If
   the target Profile is the Emergency Profile with ecallIndication set to TRUE, the
   ISD-R SHALL indicate a failure in the PSMO execution result with undefinedError
   (127) error code and procedure SHALL continue in step 4.
2. The ISD-R SHALL verify the state of the target Profile and, if usage of the Rollback
   Mechanism is granted, whether a Profile is currently enabled (or marked as "to be
   disabled"). If the target Profile is not in Disabled state, or if usage of the Rollback
   Mechanism is granted and there is no currently Enabled Profile (or no Profile marked
   as "to be disabled"), then the ISD-R SHALL indicate a failure in the PSMO execution
   result       respectively         with      profileNotInDisabledState(2)                 or
   rollbackNotAvailable(20) error codes and procedure SHALL continue in step
   4.
3. The ISD-R SHALL mark the target Profile “to be enabled” and the currently Enabled
   Profile (if any) "to be disabled” and SHALL record whether usage of the Rollback
   Mechanism is granted (together with a reference to the Profile (if any) which is to be
   disabled). If the target Profile is a Fallback Profile, the ISD-R SHALL record information
   on the currently Enabled Profile.

NOTE1:This recorded information is used when ES10b.ReturnFromFallback is executed.

NOTE2:If the currently enabled Profile is a Fallback Profile it is also marked as “to be disabled”.

4. The eUICC SHALL generate the PSMO execution result data structure indicating the
   result of the PSMO 'Enable Profile’, and the procedure continues as described in
   section 3.3.1.

End Conditions:

The target Profile is marked “to be enabled” and the currently Enabled Profile (if any) is marked "to be disabled". If granted, the authorisation to use the Rollback Mechanism has been recorded (together with a reference to the Profile (if any) which is to be disabled).

The signed eUICC Package execution result data structure containing the result of Enable command is stored in the eUICC.

3.4.2 Disable Profile

This procedure defines the execution of an Disable command contained within a eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution, used to disable a Profile already downloaded and installed on an eUICC.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC\n<b>IPA Services (ISD-R)" as IPAServices

rnote over IPAServices [1] Profile identification [2] Verify Profile state [3] Mark profile target Profile as ‘to be disabled’ End rnote

rnote over IPAServices [4] Generate Disable PSMO execution result data structure (disableResult) endrnote

@enduml

Figure 14 Disable Profile

Start Conditions: A Profile is already downloaded and installed in the eUICC.

A eUICC Package containing a 'Disable Profile' is received within an "ES10b.LoadEuiccPackage" by the eUICC as described in 3.3.1 Generic eUICC Package Download and Execution.

The eIM signature, the EID, and replay counter are verified as defined in 3.3.1 Generic eUICC Package Download and Execution.

Procedure:

If a Disable or an Enable command has already been processed in this eUICC Package, then the ISD-R SHALL indicate a failure in the PSMO execution result and procedure SHALL continue in step 4.

1. The ISD-R SHALL find the target Profile with the ICCID. If the target Profile is not found,
   the ISD-R SHALL indicate a failure in the PSMO execution result and procedure
   SHALL continue in step 4.
2. The ISD-R SHALL verify the state of the target Profile. If the target Profile is not in
   Enabled state, the ISD-R SHALL indicate a failure in the PSMO execution result and
   procedure SHALL continue in step 4.
3. The eUICC SHALL mark the target Profile “to be disabled”.
4. The eUICC SHALL generate the PSMO execution result data structure indicating the
   result of the PSMO 'Disable Profile’, and the procedure continues as described in
   section 3.3.1.

End Conditions:

The target Profile is marked “to be disabled”.

The signed eUICC Package execution result data structure containing the result of disabled Profile is stored in the eUICC.

NOTE:To maintain connectivity, a Disable command needs to be followed by an Enable command in the same eUICC Package.

3.4.3 Delete Profile

This procedure defines the execution of a Delete command contained within a eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution, used to delete a Profile already downloaded and installed on an eUICC.

The conditions under which a Provisioning Profile could be deleted are implementation- dependent and out of the scope of this specification. The eUICC implementation MAY not support deletion of a Provisioning Profile or a preloaded Test Profile.

An eUICC Package SHALL NOT include an Enable command with granted usage of the Rollback Mechanism and a Delete command, where the Delete command would try to delete the Profile to which the IPA might want to roll back.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC\n<b>IPA Services (ISD-R)" as IPAServices
rnote over IPAServices
[1] Profile identification
[2] Verify the profile state of the targeted Profile
endrnote
  alt If the target Profile is in Disabled state\n and is not marked “to be
enabled”
    rnote over IPAServices
      [2.a] eUICC shall mark "to be deleted" the target Profile
    endrnote
  else If the target Profile is in Enabled state and marked “to be disabled”:
    rnote over IPAServices
      [2.b] eUICC shall re-mark the target Profile “to be disabled and deleted”.
    endrnote
  else If the target Profile is in Enabled state and is not marked “to be
disabled”\n or the target Profile is in Disabled state and is marked "to be
enabled"
    rnote over IPAServices
     [2.c] the ISD-R SHALL indicate a failure in the PSMO execution result with
'profileNotInDisabledState' code.
    endrnote
  else If the target Profile is in Disabled state (or marked "to be disabled") but
is currently referenced by the Rollback Mechanism
    rnote over IPAServices
      [2.d] the ISD-R SHALL indicate a failure in the PSMO execution result with
'rollbackNotAvailable' code.
    Endrnote
  else If the target Profile is Disabled (or marked "to be disabled") but is
currently referenced by the Fallback Mechanism
    rnote over IPAServices
      [2.e] the ISD-R SHALL indicate a failure in the PSMO execution result with
'returnFallbackProfile' code.
    endrnote
end
rnote over IPAServices
[3] The eUICC SHALL generate the PSMO execution result data structure state
      result of the PSMO 'Delete Profile' as described in section 3.3.1
endrnote

@enduml

Figure 15 Delete Profile

Start Conditions:

A Profile is already downloaded and installed in the eUICC. An eUICC Package containing a ‘Delete Profile’ is received within an "ES10b.LoadEuiccPackage" by the eUICC as described in 3.3.1 Generic eUICC Package Download and Execution.

The eIM signature the EID, and replay counter are verified as defined in 3.3.1 Generic eUICC Package Download and Execution.

Procedure:

1. The ISD-R SHALL find the target Profile with the ICCID. If the target Profile is not found,
   then the ISD-R SHALL stop the procedure with a result indicating a failure with error
   code: iccidOrAidNotFound(1).
2. The ISD-R SHALL verify the state of the target Profile.
      a. If the target Profile is in Disabled state and is not marked “to be enabled”, ,
           then the eUICC SHALL mark the target Profile “to be deleted”.
      b. If the target Profile is in Enabled state and marked "to be disabled" and is not
           currently referenced by the Rollback Mechanism (see Enable command), then
           the eUICC SHALL mark the target Profile “to be disabled and deleted”.
      c. If the target Profile is in Enabled state and is not marked “to be disabled”, or
           the target Profile is in Disabled state and is marked "to be enabled", then the
           ISD-R SHALL indicate a failure in the PSMO execution result with
           profileNotInDisabledState(2) error code.
      d. If the target Profile is in Disabled state (or marked "to be disabled") but is
           currently referenced by the Rollback Mechanism (see Enable command), then
           the ISD-R SHALL indicate a failure in the PSMO execution result with
           rollbackNotAvailable(20) error code.

NOTE:The ISD-R does not check if the target Profile is a Fallback Profile, i.e. it is allowed to delete a Fallback Profile.

      e. If the Fallback Profile is enabled and if the target Profile is the Profile that was
           disabled using the ES10b.ExecuteFallbackMechanism function (i.e. is
           currently referenced by the Fallback Mechanism), the ISD-R SHALL indicate a
           failure in the PSMO execution result with returnFallbackProfile (21) error
           code.
3. The eUICC SHALL generate the PSMO execution result data structure indicating the
   result of the PSMO 'Delete Profile' as described in section 3.3.1.

End Conditions:

The target Profile is either marked as “to be deleted”, marked “to be disabled and deleted” or remains in “enabled” state and a failure is indicated in the signed eUICC Package execution result.

NOTE:If the target Profile is deleted, all the associated data of this Profile is deleted.

The signed eUICC Package execution result data structure containing the result of Delete Profile is stored in the eUICC.

3.4.4 Configure by eIM of Immediate Profile Enabling

This procedure defines the execution of a configureImmediateEnable command contained within an eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution, used to activate or deactivate immediate Profile enabling in the eUICC and to add or update default SM-DP+ data used in the immediate Profile enabling.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC\n<b>IPA Services (ISD-R)" as IPAServices

rnote over IPAServices [1] Activate/deactivate immediate Profile enabling endrnote rnote over IPAServices [2] Store default SM-DP+ data (defaultSmdpOid and defaultSmdpAddress) if present in the command endrnote rnote over IPAServices [3] Generate configureImmediateEnable PSMO execution result data structure (configureImmediateEnableResult) endrnote

@enduml

Figure 16 Configuration by eIM of Immediate Profile Enabling

Start Conditions:

An eUICC Package containing a 'configureImmediateEnable' command was received within an "ES10b.LoadEuiccPackage" by the eUICC.

The eIM signature, the EID, and replay counter has been verified (see 3.3.1 Generic eUICC Package Download and Execution).

Procedure:

1. If immediateEnableFlag is present and immediate Profile enabling is not activated,
   the ISD-R SHALL activate immediate Profile enabling. If immediateEnableFlag is
   not present and immediate Profile enabling is activated, the ISD-R SHALL deactivate
   immediate Profile enabling. In all other cases, the immediate Profile enabling state is
   left unchanged.
2. If present, the ISD-R SHALL store default SM-DP+ data (defaultSmdpOid and/or
   defaultSmdpAddress) for use in the immediate Profile enabling.

NOTE:if defaultSmdpAddress is stored here, then it is also used as the default SM-DP+ address in the response that is provided by the GetEuiccConfiguredAddresses function (described in 5.8.1 of this specification).

3. The eUICC SHALL generate the PSMO execution result data structure indicating the
   result of the PSMO ‘Configure Immediate Profile Enabling’ and the procedure
   continues as described in section 3.3.1.

3.4.5 Configure by IPA of Immediate Profile Enabling

This procedure describes how to configure immediate Profile enabling when requested by IPA.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant “<b>IPA” as IPA participant “<b>eUICC (ISD-R)” as eUICC

IPA -> eUICC : [1] ES10b.ConfigureImmediateProfileEnabling ([immediateEnableFlag],[smdpOid],[smdpAddress]) alt If any eIM Configuration Data is already present in the eUICC eUICC → IPA : [2] error else Otherwise rnote over eUICC [3] Activate/deactivate immediate Profile enabling [4] Store the default SM-DP+ data (defaultSmdpOid and defaultSmdpAddress), if present in the command end rnote eUICC → IPA : [5] OK end

@enduml

Figure 17 Configure by IPA of Immediate Profile Enabling

Start Conditions:

The eUICC does not contain any eIM Configuration Data.

Procedure:

1. The IPA calls “ES10b. ConfigureImmediateProfileEnabling” function optionally
   comprising         immediateEnableFlag,                  defaultSmdpOid,           and
   defaultSmdpAddress.
2. If any eIM Configuration Data is already present in the eUICC, the eUICC SHALL return
   an error and the procedure SHALL stop. Otherwise, the procedure continues in step
   (3).
3. If immediateEnableFlag is present and immediate Profile enabling is not activated,
   the eUICC SHALL activate immediate Profile enabling. If immediateEnableFlag is
   not present and immediate Profile enabling is activated, the eUICC SHALL deactivate
   immediate Profile enabling. In all other cases, the immediate Profile enabling state is
   left unchanged.
4. If provided by IPA in step 1, the eUICC SHALL storedefault SM-DP+ data
   (defaultSmdpOid and/or defaultSmdpAddress) for use in the immediate Profile
   enabling.

NOTE:if defaultSmdpAddress is stored here, then it is also used as the default SM-DP+ address in the response that is provided by the GetEuiccConfiguredAddresses function (described in 5.8.1 of this specification).

5. The eUICC returns ok to the IPA.

NOTE:How the configuration data (immediateEnableFlag, defaultSmdpOid, and defaultSmdpAddress) is sent to the IPAe is implementation specific.

3.4.6 Setting the Fallback Attribute for the target Profile

This procedure defines the execution of a setFallbackAttribute command contained within an eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution. The command is used to set the Fallback Attribute for the target Profile.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant “<b>IPA” as IPA participant “<b>eUICC\n<b>IPA Services (ISD-R)” as E

rnote right IPA [1] Check if Fallback Mechanism is supported by eUICC End rnote E --> IPA: error rnote over E [2] Find target Profile End rnote E --> IPA: error rnote right IPA [3] check if current Fallback Profile is target Profile

end rnote
E --> IPA: ok
rnote right IPA
 [4] Verify that FallbackAllowed is TRUE
End rnote
E --> IPA: error
alt [5a] If Fallback Profile is enabled
    E --> IPA: error
 else [5b] If Fallback Profile is disabled
   rnote right IPA
     Remove Fallback Attribute from Fallback Profile
   end rnote
   rnote right IPA
     Set Fallback Attribute for target Profile
   end rnote
   E -> IPA: ok
end

rnote right IPA [6] Set Fallback Attribute for target Profile end rnote E -> IPA: ok @enduml

Figure 18 Set Fallback Attribute

Start Conditions:

An eUICC Package containing a ‘setFallbackAttribute’ command was received within an “ES10b.LoadEuiccPackage” by the eUICC.

The eIM signature and replay counter have successfully been verified (see 3.3.1 Generic eUICC Package Download and Execution).

Procedure:

1. If the eUICC does not support the Fallback Mechanism the procedure SHALL stop and
   the result of this command SHALL indicate error (‘processingTerminated’ with
   ‘unknownOrDamagedCommand).
2. The ISD-R SHALL find the target Profile with the given ICCID. If the target Profile is
   not available, the ISD-R SHALL stop the procedure with a result indicating a failure
   (‘iccidOrAidNotFound‘).
3. The ISD-R SHALL check if the target Profile already has the Fallback Attribute set, if
   yes, the procedure SHALL stop and the result of this command SHALL indicate
   success (‘ok’).
4. The ISD-R SHALL check if Fallback is allowed for the target Profile by verifying that
   the fallbackAllowed flag is set to TRUE. If the flag is absent or set to FALSE, the
   procedure SHALL stop and the result of this command SHALL indicate error
   (‘fallbackNotAllowed (2)’).
The ISD-R SHALL check if the target Profile is the Emergency Profile with
ecallIndication set to TRUE. If yes, the procedure SHALL stop and the result of
this command SHALL indicate error (‘undefinedError(127)’).
5. The ISD-R SHALL check if there is a Profile that already has the Fallback Attribute set
   (i.e., a Fallback Profile is present). If so, the ISD-R SHALL check the state of this
   Fallback Profile:
        a. if this Fallback Profile is enabled, the procedure SHALL stop and the result of
            this command SHALL indicate error (‘fallbackProfileEnabled (3)’).
        b. if this Fallback Profile is disabled, the ISD-R SHALL unset the Fallback Attribute
            from this Profile, and set the Fallback Attribute of the target Profile. After that
            the procedure SHALL stop and the result of this command SHALL indicate
            success (‘ok’).

3.4.7 Unsetting the Fallback Attribute for the target Profile

This procedure defines the execution of a unsetFallbackAttribute command contained within an eUICC Package as defined in 3.3.1 Generic eUICC Package Download and Execution. The command is used to unset the Fallback Attribute of the current Fallback Profile.

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid

skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant “<b>IPA ” as IPA participant “<b>eUICC\n<b>IPA Services (ISD-R)” as E

alt If Fallback Profile does not exist
  E -> IPA: [1a] error
else If Fallback Profile exists and is disabled
  rnote right IPA
    [1bi] remove Fallback Attribute from current Fallback Profile
  end rnote
  E -> IPA: [1bi] OK
else If Fallback Profile exists and is enabled
  E-> IPA: [1bii] error
end
@enduml

Figure 19 Unset Fallback Attribute

Start Conditions:

An eUICC Package containing a ‘unsetFallbackAttribute’ command was received within an “ES10b.LoadEuiccPackage” by the eUICC.

The eIM signature and replay counter have successfully been verified (see 3.3.1 Generic eUICC Package Download and Execution).

The Fallback Mechanism is supported by the eUICC.

Procedure:

1. The ISD-R SHALL check if the Fallback Attribute is set for any Profile on the eUICC
   and
      a. if not, the procedure SHALL stop, and the result of this command SHALL
         indicate an error (‘noFallbackAttribute’)
      b. if yes, and
              i. if the Fallback Profile is disabled, unset the Fallback Attribute of that
                  Profile. After that, the procedure is completed, and the result of this
                  command SHALL indicate success (‘ok’).
ii. if the Fallback Profile is enabled, the procedure SHALL stop and the
    result      of    this      command       SHALL     indicate   error
    (‘fallbackProfileEnabled (3)’).

NOTE:Upon successful completion of this command, no Fallback Profile exists on the eUICC.

3.5 eIM Configuration at eUICC

3.5.1 eIM Configuration Data managed by eIM

This section describes the procedures related to managing eIM Configuration Data requested
by the eIM. All the initiated requests by the eIM SHALL be signed by an Associated eIM and
verified by the eUICC.
The eIM initiated procedures are to:
      •   Add a new eIM Configuration Data.
      •   Delete an existing eIM Configuration Data.
      •   Update an existing eIM Configuration Data.

3.5.1.1 Addition of eIM Configuration Data

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC (ISD-R)" as eUICC

rnote over eUICC [1] Add eIM Configuration Data to eUICC storage end rnote

rnote over eUICC [2] Generate addEIM eCO execution result data structure (addEimResult) endrnote

@enduml

Figure 20 Addition of eIM Configuration Data

Start Conditions:

•   A eUICC Package containing an 'addEim' was received within an
    "ES10b.LoadEuiccPackage" by the eUICC.
•   The eUICC contains eIM Configuration Data of at least one Associated eIM and the
    eUICC Package was verified as defined in section 3.3.1.

Procedure:

1. Upon successful verifications of the eUICC Package (see section 3.3.1), the ISD-R
   SHALL add the eIM Configuration Data of the new eIM to its list of Associated eIMs.
   The eUICC SHALL stop the procedure indicating a failure if:
      a. the eUICC does not have sufficient memory to store the new eIM
         (“insufficientMemory”)
      b. no eimId is provided in the eUICC Package or eimId exceeds its maximum
         length (“commandError”)
      c. the provided eimId belongs to an eIM already associated with the eUICC
         (“associatedEimAlreadyExists”)
      d. the counterValue exceeds the maximum value supported by the eUICC
          (“counterValueOutOfRange”)
      e. the eUICC is requested to generate an associationToken but the value
          provided is not set to -1 (“invalidAssociationToken”)
      f. the     provided        euiccCiPKId      is    not  an     entry    within
          euiccCiPKIdListForSigning in eUICCInfo2 (“ciPKUnknown”)
      g. any other error during command execution occurs (“undefinedError”).
2. The procedure continues as defined in section 3.3.1.

End Conditions:

eIM Configuration Data of the new eIM is added to the list of Associated eIMs within
the eUICC.
The new eUICC is added to the list of eUICCs within the eIM.

3.5.1.2 Deletion of eIM Configuration Data

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC (ISD-R)" as eUICC

rnote over eUICC [1] Find target eIM end rnote

rnote over eUICC [2] Remove eIM Configuration Data from eUICC endrnote

rnote over eUICC [3] Generate deleteEim eCO execution result data structure (deleteEimResult)

endrnote

@enduml

Figure 21 Deletion of eIM Configuration Data

Start Conditions:

•   A eUICC Package containing a 'deleteEim' was received within an
    "ES10b.LoadEuiccPackage" by the eUICC.
•   The eUICC contains eIM Configuration Data of at least one Associated eIM and the
    verifications as defined in section 3.3.1 were performed.

Procedure:

1. Upon successful verifications of the eUICC Package (see section 3.3.1), the ISD-R
   SHALL find the eIM Configuration Data of the target eIM in its list of Associated eIMs.
   The eUICC SHALL stop the procedure indicating a failure if:
        a. the eUICC does not find the eimId within its list of Associated eIMs
            (“eimNotFound”)
        b. in case no eimId is provided in the eUICC Package (“commandError”)
        c. any other error during command execution occurs (“undefinedError”).
2. The eUICC SHALL remove the eIM Configuration Data from its list of Associated eIMs.
   If the target Associated eIM to be deleted is the requesting eIM, the eUICC SHALL
   include the relevant information into the eCO execution result and SHALL only delete
   the eIM Configuration Data after the eCO execution result was generated and signed.
   If the target Associated eIM to be deleted is the last available Associated eIM within
   the eUICC, the eUICC SHALL set its state such, that it allows for addition of eIM
   Configuration Data using Unsigned eCO and SHALL return “lastEimDeleted” within its
   eCO execution result.
3. The procedure continues as defined in section 3.3.1.

End Conditions:

eIM Configuration Data of the target eIM is deleted from the list of Associated eIMs within the eUICC.

3.5.1.3 Update of eIM Configuration Data

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center

skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC (ISD-R)" as eUICC

rnote over eUICC [1] Update eIM Configuration Data in eUICC storage end rnote

rnote over eUICC [2] Generate updateEim eCO execution result data structure (updateEimResult) endrnote

@enduml

Figure 22 Update of eIM Configuration Data

Start Conditions:

•   A eUICC Package containing an 'updateEim' was received within an
    "ES10b.LoadEuiccPackage" by the eUICC.
•   The eUICC contains eIM Configuration Data of at least one Associated eIM and the
    eUICC Package was verified as defined in section 3.3.1.

Procedure:

1. Upon successful verifications of the eUICC Package (see section 3.3.1), the ISD-R
   SHALL update the eIM Configuration Data of the eIM addressed by the provided
   “eimId”. The eUICC SHALL stop the procedure indicating a failure if:
      a. the eIM cannot be found in the list of Associated eIMs or no “eimId” is provided
          in the eUICC Package (“eimNotFound”)
      b. the ”associationToken” is included in the EimConfigurationData data
          object (“commandError”)
      c. none of “counterValue” , eimPublicKeyData, eimIdType, eimFqdn,
          eimSupportedProtocol,                  trustedPublicKeyDataTls                or
          euiccCiPKId is included in the EimConfigurationData data object
          (“commandError”)
      d. the “counterValue” is updated to a value lower than the currently stored
          value while the “eimPublicKeyData” are not updated (“commandError”).
      e. the      provided     euiccCiPKId          is     not     an    entry      within
          euiccCiPKIdListForSigning in eUICCInfo2 (“ciPKUnknown”)
      f. any other error during command execution occurs (“undefinedError”)
2. The procedure continues as defined in section 3.3.1.

End Conditions:

The eIM Configuration Data of the targeted eIM is updated within the list of Associated eIMs within the eUICC.

3.5.1.4 Request for a list of Associated eIMs

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>eUICC (ISD-R)" as eUICC

rnote over eUICC [1] List associated eIMs (listEim) end rnote

rnote over eUICC [2] Generate listEim eCO execution result data structure (listEimResult) endrnote

@enduml

Figure 23 Request for a list of Associated eIMs

Start Conditions:

•   A eUICC Package containing a 'listEim' was received within an
    "ES10b.LoadEuiccPackage" by the eUICC.
•   The eUICC contains eIM Configuration Data of at least one Associated eIM and the
    eUICC Package was verified as defined in section 3.3.1.

Procedure:

1. Upon successful verifications of the eUICC Package (see section 3.3.1), the ISD-R
   SHALL provide as a result the eIM identifier(s) of Associated eIM(s).
2. The procedure continues as defined in section 3.3.1.

End Conditions:

The eIM identifier of Associated eIM(s) can be provided through the signed eUICC Package Result to the IPA and via eIM Package Result to the eIM.

3.5.2 eIM Configuration Data managed by IPA

This section describes the procedures related to managing eIM Configuration Data requested
by the IPA. All the initiated requests by the IPA SHALL be protected as per the ES10 security.
The IPA initiated procedures are to:
   •    Add of an initial eIM Configuration Data.
   •    Complete removal of eIM Configuration Data.
   NOTE:        The protection of IPA initiated request is implementation specific under the
                responsibility of IoT Device manufacturer.

3.5.2.1 Addition of initial eIM Configuration Data

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>IPA" as IPA participant "<b>eUICC (ISD-R)" as eUICC

IPA -> eUICC : [1] ES10b.AddInitialEim(EimConfigurationData) alt If any eIM Configuration Data is already present in the eUICC eUICC --> IPA : [2] error (associatedEimAlreadyExist) else Otherwise continue processing the command alt Any of the subsequent checks fails eUICC --> IPA : [3] error (one of: insufficientMemory, invalidAssociationToken, counterValueOutOfRange, commandError, ciPKUnknown, undefinedError) else Otherwise rnote over eUICC [4] Store eIM Configuration Data end rnote eUICC --> IPA : [5] AddInitialEimResponse end

@enduml

Figure 24 Addition of initial eIM Configuration Data

Start Conditions:

•The eUICC does not contain any eIM Configuration Data.

Procedure:

1. The IPA calls "ES10b.AddInitialEim" function comprising eIM Configuration Data
   (EimConfigurationData).
2. If any eIM Configuration Data is already present in the eUICC, the eUICC SHALL return
   an error (“associatedEimAlreadyExists”) and the procedure SHALL stop.
3. The eUICC SHALL stop the procedure indicating a failure if:
        a. the counterValue exceeds the maximum value supported by the eUICC
           (“counterValueOutOfRange”).
        b. the eUICC is requested to generate an associationToken but the value
           provided is not set to -1 (“invalidAssociationToken”)
        c. the eUICC does not have sufficient memory to store the initial eIM
           (“insufficientMemory”)
        d. no eimId is provided or eimId exceeds its maximum length (“commandError”)
        e. the      provided      euiccCiPKId     is    not    an      entry     within
           euiccCiPKIdListForSigning in eUICCInfo2 (“ciPKUnknown”)
        f. any other error during command execution occurs (“undefinedError”).
4. If requested, the eUICC SHALL calculate the association token and store it together
   with the eIM Configuration Data.
5. The eUICC returns the AddInitialEimResponse to the IPA.

End Conditions:

•The eUICC is associated with the eIM as per the eIM Configuration Data.

NOTE:In case IPAe is used, the addition of initial eIM Configuration Data uses the EimConfigurationData structure. How the eIM Configuration Data is sent to the eUICC is implementation specific.

3.5.2.2 Deletion of all eIM Configuration Data

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>IPA" as IPA participant "<b>eUICC (ISD-R)" as eUICC

IPA -> eUICC : [1] ES10b.EuiccMemoryReset(resetEimConfigData) rnote over eUICC [2] Removes all eIM Configuration Data end rnote eUICC --> IPA : [3] ok or nothingToDelete

@enduml

Figure 25 Deletion of all eIM Configuration Data

Start Conditions:

•None

Procedure:

1. The IPA calls "ES10b.EuiccMemoryReset" function with resetEimConfigData bit
   set to one.
2. The eUICC removes all eIM Configuration Data.
3. The eUICC returns ok or nothingToDelete.

End Conditions:

•The eUICC does not contain any eIM Configuration Data.

3.5.2.3 Reading eIM Configuration Data

@startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF hide footbox

participant "<b>IPA" as IPA participant "<b>eUICC (ISD-R)" as eUICC

IPA -> eUICC : [1] ES10b.GetEimConfigurationData eUICC --> IPA : [2] List of EimConfigurationData @enduml

Figure 26 Reading eIM Configuration Data by IPA

Start Conditions:

•None

Procedure:

1. The IPA calls "ES10b.GetEimConfigurationData" function.
2. The eUICC returns the list of eIM Configuration Data stored in the eUICC to the IPA.

End Conditions:

•None

3.6 Error handling within an RSP session

The RSP sessions comprise a sequence of operations between the SM-DP+, the IPA, the eUICC, and/or the eIM over a period of time. In addition to errors reported by ES9+, ES9+', ES10 and/or ESipa functions, other conditions MAY impact the successful execution of this procedure. The IPA SHOULD indicate such failures to external entities, e.g., a device management platform; however, the specific presentation of these errors is out of the scope of this document.

The IPA SHOULD NOT initiate a new RSP session while there is an active RSP session. However, in the event that this does occur, the eUICC SHALL discard its session state with the possible exception that unused one-time keys MAY be stored for future retries, when a new RSP session is started with "ES10b.GetEUICCChallenge".

If an eUICC Memory Reset or eUICC Test Memory Reset is successfully processed during an RSP session, the eUICC SHALL discard its session state.

An RSP Session MAY fail because of a communications failure between the IPA and the RSP Server, or the IPA and the eIM. The IPA MAY retry the failed RSP session for a period of time. The IPA SHALL reset its own session state when all retry attempts have failed.

An RSP Session could fail while the IPA is invoking an ES10 function for reasons other than
an error status reported by the eUICC. Examples of such failures include:
    • In the case of a removable eUICC card, the card is unexpectedly removed.
    • The IoT Device is powered off, e.g., by running out of the battery or by the user.
    • A software fault could cause a crash of the IPA, host IoT Device, and/or baseband
        processor.
When possible (e.g., when power is restored), the IPA SHOULD provide an appropriate error
indication to external entities, e.g., the device management platform, and MAY restart the
relevant procedure. The specific presentation of such an error Notification is out of scope of
this document.

3.7 Notification Delivery to Notification Receivers

This procedure describes the delivery of Notifications to Notification Receivers. Notifications MAY also be delivered together with an eUICC Package Result as described in Section 3.3.1. @startuml skinparam monochrome true skinparam ArrowColor Black skinparam lifelinestrategy solid skinparam sequenceMessageAlign center

skinparam noteBackgroundColor #FFFFFF skinparam participantBackgroundColor #FFFFFF skinparam ParticipantPadding 70 hide footbox

participant "<b>SM-DP+" as DP participant "<b>eIM" as eIM participant "<b>IPAd" as IPA participant "<b>eUICC" as E

IPA -> E : [1] ES10b.RetrieveNotificationsList E -> IPA : List of pending Notifications

group If pending Notifictions to be delivered group For each pending Notification alt [2a] Direct ES9+ interface to SM-DP+ IPA -> DP : ES9+.HandleNotification DP -> IPA : ACK else [2b] No direct ES9+ interface to SM-DP+ IPA -> eIM : ESipa.HandleNotification eIM -> IPA : ACK eIM -> DP : ES9+’.HandleNotification DP -> eIM : ACK end IPA -> E : [3] ES10b.RemoveNotificationFromList rnote over E: [4] Delete Notification end end

@enduml

Figure 27 Notification Delivery to Notification Receivers

Start Condition:
This procedure requires the following start conditions:
      •   A Secure Connection between the eIM and the IPAd is established.
      •   Either a profile installation or a PSMO has been executed such that one or more
          Notifications MAY have been generated by the eUICC.
      •   IPAd is configured to send Notifications using ES9+.HandleNotification or
          ESipa.HandleNotification.
Procedure:
   1. The     IPAd      SHALL      retrieve   pending    Notifications by    calling    the
      ES10b.RetrieveNotificationsList function.
   2. In case of a non-empty list of pending Notifications, IPAd SHALL deliver the pending
      Notifications to the Notification Receivers:
          a. If a direct ES9+ interface to the SM-DP+ is used to deliver Notifications, the
              IPAd SHALL send the Notifications by using the ES9+.HandleNotification
              function as described in section 5.6.4 of SGP.22 [4].
              b. If Notifications are delivered via the eIM to the SM-DP+, the IPAd SHALL send
                 the Notifications to the eIM by using the ESipa.HandleNotification function as
                 described in section 5.14.7 of this document and the eIM SHALL forward them
                 to the Notification Receivers by using the ES9+’.HandleNotification function as
                 described in section 5.7.4 of this document. In case of an IPAd with IPA
                 Capability minimizeEsipaBytes the IPAd SHOULD send Notifications in
                 compact format as described in Section 5.14.7. An eIM receiving a pending
                 Notification in compact format SHALL identify the relevant information and build
                 the full pending Notification before forwarding the Notification to the Notification
                 Receiver.
3. IPAd SHALL call ES10b.RemoveNotificationFromList (see SGP.22 [4]) to delete the
   pending Notification for which acknowledgement has been received.
4. The eUICC SHALL delete the pending Notification.

3.8 IoT Device and eUICC Initialisation

The IoT Device and eUICC SHALL be initialised according to sections 3.8.1, 3.8.2, 3.8.3 and 3.8.4 of this specification.

3.8.1 eUICC Initialisation

The eUICC SHALL be initialised according to sections 3.4.1 of SGP.22 [4].

3.8.2 IoT Device Capabilities

The eUICC SHALL request the IoT Device to send the Terminal Capability command by setting the related bit in the file control parameters of the MF.

The IoT Device SHALL report its support of IPA functions using the Terminal Capability command data defined in ETSI TS 102 221 [34]. This command SHALL be sent before the SELECT ISD-R command defined in section 3.8.4 of this specification.

Within the Terminal Capability template (tag ‘A9’), the tag ‘84’ is used for indicating the IoT Device’s support for eUICC related functions.

.

The IPAd support is indicated in the first byte within the TLV object under tag '84':

b8 b7 b6 b5 b4 b3 b2 b1 Meaning
-   -    -   -   -    -    -   1    IPAd supported
-   -    -   -   -    -    -   0    IPAd not supported
x   x    x   x   x    x    x   -    Not applicable

Table 4 eUICC-related IoT Device Capabilities

If an IoT Device supports IPAd, b1 SHALL be set to 1. Otherwise, b1 SHALL be set to 0.

The eUICC SHALL only enable the ES10 functions if the IoT Device indicates support for IPAd.

The conditions for activating the IPAe are defined in section 3.8.4.

3.8.3 eUICC File Structure

The eUICC File structure SHALL be initialised according to sections 3.4.3 of SGP.22 [4].

3.8.4 ISD-R Selection and IPAe Activation

Before sending any command to the eUICC, the IPAd SHALL establish a logical channel and select the ISD-R.

The opening of the logical channel and the selection of the ISD-R SHALL be done explicitly using, respectively, the MANAGE CHANNEL command and the SELECT command defined in GlobalPlatform Card Specification [32]. This MANAGE CHANNEL and SELECT commands can be intrinsically used via a dedicated IoT Device Operating System API (e.g., OMAPI defined by GlobalPlatform[33] if provided).

The IoT Device SHALL ensure that only the IPAd, but no other application on the IoT Device, is permitted to select the ISD-R, except that the ISD-R MAY also be selected during eUICC initialisation as defined in section 3.8.1.

In order to provide information about the capabilities supported by the eUICC at an early point in time, additional information is provided by the ISD-R.

On the reception of the SELECT ISD-R Command, the following data SHALL be returned within the FCI template after the objects defined in GlobalPlatform Card Specification [32]:

-- ASN1START
ISDRProprietaryApplicationTemplateIoT ::= [PRIVATE 1] SEQUENCE { -- Tag 'E1'
   euiccConfiguration BIT STRING {
      ipaeSupported(0), -- IPA in the eUICC (IPAe) supported
      enabledProfile(1) -- eUICC contains an Enabled Profile

} } -- ASN1STOP

The eUICC SHALL indicate its support for IPAe by setting the ipaeSupported bit in the euiccConfiguration field.

If the IoT Device supports the requirements on IPAe as defined in Annex A.2 and if the eUICC indicated support for IPAe in the ISDRProprietaryApplicationTemplateIoT, the IoT Device MAY activate the IPAe by sending an IpaeActivationRequest to the ISD-R. The IpaeActivationRequest SHALL be sent to the ISD-R using the transport mechanism defined in section 5.7.2 of SGP.22 [4].

The command data SHALL be coded as follows:

-- ASN1START
IpaeActivationRequest ::= [66] SEQUENCE { -- Tag 'BF42'
   ipaeOption BIT STRING {
      activateIpae(0) -- IPAe activation
   }
}
-- ASN1STOP

The response data SHALL be coded as follows:

-- ASN1START IpaeActivationResponse ::= [66] SEQUENCE { -- Tag 'BF42' ipaeActivationResult INTEGER {ok(0), notSupported(1)} } -- ASN1STOP

If the IoT Device indicates in the Terminal Capability command the support for IPAd (see section 3.8.2) and the IPAd does not send an IpaeActivationRequest, the eUICC SHALL NOT activate the IPAe. If the IoT Device indicates that IPAd is not supported, the eUICC SHALL activate the IPAe, if supported by the eUICC.

NOTE:For IoT Devices and eUICC that support both IPAe and IPAd, the IoT Device can reset the eUICC and send new Terminal Capability indicating that IPAd is supported to activate the IPAd in case the IPAe is activated.

3.9 SM-DS Use

3.9.1 Event Registration

Event Registration SHALL follow the procedure defined in section 3.6.1 of SGP.22 [4].

3.9.2 Event Retrieval

3.9.2.1 Event Retrieval by the IPA

The Event Retrieval by the IPA SHALL follow the procedure defined in section 3.6.2 of SGP.22 [4]. The IPA plays the role of the LPA.

3.9.2.2 Event Retrieval by the eIM

This section describes the indirect Event Retrieval from SM-DS to eIM.

@startuml

hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid

participant "<b>SM-DS" as DS participant "<b>eIM" as EIM participant "<b>IPA" as IPA participant "<b>eUICC" as E

group If IPA obtains a profile download trigger from eIM Package alt IPA-initiated rnote over EIM, IPA : [1a] eIM Package Retrieval Procedure including secure connection establishment (section 3.1.1.1) else eIM-initiated rnote over EIM, IPA : [1b] eIM Package Injection Procedure including secure connection establishment (section 3.1.1.2) end

rnote over IPA : [2] IPA parses the eIM Package and obtains profile \ndownload trigger end

opt Get euiccInfo1 if not yet retrieved by IPA or eIM IPA -> E : [3] ES10b.GetEuiccInfo E --> IPA : euiccInfo1 end IPA -> E : [4] ES10b.GetEuiccChallenge E -> IPA : euiccChallenge

group If a secure connection is not yet established rnote over EIM, IPA : [5] Establish secure connection end IPA -> EIM : [6] ESipa.InitiateAuthentication request rnote over EIM, DS : [7] Establish HTTPS connection rnote over EIM, DS : [8] ES11'.InitiateAuthentication function EIM -> IPA : [9] ESipa.InitiateAuthentication response rnote over IPA, E: [10] ES10b.AuthenticateServer function IPA -> EIM : [11] ESipa.AuthenticateClient request rnote over EIM, DS : [12] ES11'.AuthenticateClient function rnote over EIM : [13] Parse Event entry/ies \nobtained from the SM-DS EIM -> IPA : [14] ESipa.AuthenticateClient response

@enduml

Figure 28 Event Retrieval by the eIM

Start Conditions:

In addition to the start conditions required by the Common Mutual Authentication procedure defined in section 3.1.2 of SGP.22 [4], this procedure requires the following start condition:

The eIM and/or the IPA has the SM-DS Address.

Procedure:

1. In case a Profile download trigger from an eIM Package: a secure connection is
   established between the IPA and the eIM for IPA to obtain the eIM Package. How this
   is triggered is out of scope of this specification. There are two options for the delivery
   of the eIM Package to the IPA:
        a) The eIM Package Retrieval Procedure defined in section 3.1.1.1 is executed
            between the IPA and the eIM.

b)The eIM Package Injection Procedure defined in section 3.1.1.2 is executed between the IPA and the eIM.

2. The IPA parses the eIM Package received in step 1. The IPA identifies that the eIM
    Package contains a ProfileDownloadTriggerRequest. To trigger Event Retrieval
    from the SM-DS, the ProfileDownloadTriggerRequest is either an empty data
    object (i.e., without profileDownloadData) or contains a profileDownloadData
    with contactSmds. In the first case the IPA is not expected to provide SM-DS FQDN
    in step (6) whereas in the latter case the IPA is expected to provide SM-DS FQDN in
    step (6). If the format of ProfileDownloadTriggerRequest is invalid, or data
    needed by IPA for the Event Retrieval is missing, the procedure SHALL stop.
3. If euiccInfo1 is not yet retrieved by the eIM or IPA, the IPA MAY request euiccInfo1
    from the eUICC by calling ES10b.GetEuiccInfo (see section 5.9.2).
4. The IPA requests an eUICC Challenge from the eUICC by calling the
    ES10b.GetEUICCChallenge function (see section 5.9.3).
5. A secure connection is established between the IPA and the eIM if it is not yet
    established.
6. The IPA calls ESipa.InitiateAuthentication function comprising eUICC Challenge,
    optionally SM-DS FQDN, and optionally euiccInfo1 (see IPA Capability
    minimizeEsipaBytes). If the IPA does not provide SM-DS FQDN or euiccInfo1, the
    eIM SHALL identify the relevant information.
7. The eIM establishes an HTTPS connection with the SM-DS in server authentication
    mode according to SGP.22 [4].
8. The eIM and the SM-DS process ES11'.InitiateAuthentication function comprising
    eUICC Challenge, SM-DS FQDN, and euiccInfo1 as defined in section 5.11.1. If the
    SM-DS FQDN provided in ES11'.InitiateAuthentication did not come from IPA (was not
    obtained from IPA in step 6 e.g., due to IPA has capability
    eimDownloadDataHandling), the eIM SHALL verify that this SM-DS FQDN
    matches the SM-DS FQDN returned by the SM-DS (in serverSigned1). If not, the
    procedure SHALL stop.
9. The eIM sends the ESipa.InitiateAuthentication response to the IPA, based on the
    ES11'.InitiateAuthentication response from the SM-DS. The eIM SHALL additionally
    provide ctxParams1 as defined in SGP.22 [4] if the IPA does not generate it. (see IPA
    capability eimCtxParams1Generation).
10. The IPA and eUICC process ES10b.AuthenticateServer function call as defined in
    section 5.7.13 of SGP.22 [4].
11. The IPA calls ESipa.AuthenticateClient function comprising euiccSigned1 or
    compactEuiccSigned1, euiccSignature1, optionally CERT.EUM.ECDSA, and
    optionally CERT.EUICC.ECDSA. If the IPA does not provide CERT.EUM.ECDSA and
    CERT.EUICC.ECDSA and/or provide the compactEuiccSigned1 instead of
    euiccSigned1 (see IPA Capability minimizeEsipaBytes), the eIM SHALL identify
    the relevant information and build euiccSigned1.
12. The eIM and SM-DS process the ES11'.AuthenticateClient function as defined in 5.11.2.
13. The eIM parses the Event entry/ies obtained from the ES11'.AuthenticateClient from
    the SM-DS.
14. The eIM sends the ESipa.AuthenticateClient response to the IPA, based on the
    ES11'.AuthenticateClient response from the SM-DS. In case of a successful
ES11'.AuthenticateClient response the eIM sends only the transactionId (without
including      eventEntries).       The         eIM      MAY         include        a
ProfileDownloadTriggerRequest data object in order to trigger the IPA to start
downloading a new Profile. In case of an error, IPA SHALL trigger the cancellation of
the on-going RSP session (see section 3.2.3.3) with reason undefinedReason and the
procedure SHALL stop.

3.9.3 Event Deletion

Event Deletion SHALL follow the procedure defined in section 3.6.3 of SGP.22 [4].

4 Data Elements

4.1 IPA Capabilities

The IPA Capabilities are intended for the eIM for the functional split related to profile download between the eIM and the IPA and the use of compact data object structures in ESipa functions. In addition, IPA Capabilities MAY indicate the support of eIM Package transfer including the type of connection over ESipa.

IPA Capabilities SHALL include:

•Support for direct profile download

•Support for indirect profile download

o   Support for eIM handled download data (e.g. Activation Code) during indirect
    profile download.
o   Support for eIM generated ctxParams1 during indirect profile download.
o   Support for eIM performed Profile Metadata verification during indirect profile
    download.
o   Use of compact data objects to minimize number of transferred ESipa bytes
    during indirect profile download.

IPA Capabilities MAY include support for eIM Package transfer over ESipa:

•eIM Package retrieval using HTTPs over TCP (see section 3.1.2.1)

•eIM Package retrieval using CoAP/DTLS over UDP (see section 3.1.2.2)

•eIM Package injection using HTTPs over TCP (see section 3.1.2.1)

•eIM Package injection using CoAP/DTLS over UDP (see section 3.1.2.2)

•proprietary

IPA Capabilities data object structure is defined as follows: -- ASN1START IpaCapabilities ::= SEQUENCE {

   ipaFeatures [0] BIT STRING {
   directRspServerCommunication (0),
   indirectRspServerCommunication (1),
   eimDownloadDataHandling (2),
   eimCtxParams1Generation (3),
   eimProfileMetadataVerification (4),
   minimizeEsipaBytes (5)
   },
   ipaSupportedProtocols [1] BIT STRING {
      ipaRetrieveHttps(0),
      ipaRetrieveCoaps(1),
      ipaInjectHttps(2),
      ipaInjectCoaps(3),
      ipaProprietary(4)
   } OPTIONAL
}
-- ASN1STOP
ipaFeatures indicates the features supported by the IPA:

•The directRspServerCommunication set to 1 indicates that IPA supports direct Profile download according to Section 3.2.3.1. This includes direct delivery of Notifications to the SM-DP+.

•The indirectRspServerCommunication set to 1 indicates that IPA supports indirect Profile download according to Section 3.2.3.2. This includes delivery of Notifications via the eIM to SM-DP+.

•An IPA supporting indirect profile download MAY further have the following capabilities:

o   The eimDownloadDataHandling set to 1 indicates that IPA does not
    handle download data such as Activation Codes, SM-DP+ data retrieved from
    SM-DS, and default SM-DP+ address during indirect Profile download and
    expects Activation Codes and Event Records to remain at the eIM where the
    eIM parses and extracts the relevant data such as SM-DP+ address,
    matchingId, and SM-DP+ OID for use in ESipa.InitiateAuthentication.
o   The eimCtxParams1Generation set to 1 indicates that IPA does not
    support generation of CtxParams1 and expects the eIM to generate and
    provide CtxParams1 to IPA as part of ESipa.InitiateAuthentication.
o   The eimProfileMetadataVerification set to 1 indicates that IPA does
    not support verification of Profile Metadata and expects the eIM to verify
    Profile Metadata as part of ESipa.AuthenticateClient. It is also expected that
    eIM checks as part of ESipa.GetBoundProfilePackage that the Profile
    Metadata provided in the BPP matches the Profile Metadata in
    ESipa.AuthenticateClient.
o   The minimizeEsipaBytes set to 1 indicates that IPA uses compact data
    objects and avoids sending data over ESipa that the other party already
    knows in order to minimize the number of transmitted bytes between IPA and
    eIM. It is expected that the eIM is able to identify missing parts (bytes) and re-
    build full data object structures. The eIM MAY leverage pre-configured static
    eUICC data, eUICC data obtained from another IoT Device within the same
batch for which the data is common, eUICC data read from the IoT Device,
and session data obtained from the SM-DP+. For more information refer to
the profile download related ESipa function descriptions in Section 5.14.

ipaSupportedProtocols indicates which eIM Package transfer (see 3.1.1) is supported by the IPA:

•ipaRetrieveHttps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using HTTPs over TCP as described in section 3.1.2.1

•ipaRetrieveCoaps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using CoAP/DTLS over UDP as described in section 3.1.2.2

•ipaInjectHttps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using HTTPs over TCP as described in section 3.1.2.1

•ipaInjectCoaps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using CoAP/DTLS over UDP as described in section 3.1.2.2

•ipaProprietary set to 1 indicates support of a transport protocol not described in section 3.1.2.

The eIM SHALL obtain IPA Capabilities to determine whether it is able to support profile download and profile management for the particular IoT Device/IPA. IPA Capabilities MAY be obtained out-of-band from the IoT Device owner/user, or it MAY be requested from IPA in an eIM Package.

4.2 eIM Supported Protocol

EimSupportedProtocol indicates which transport protocol, and eIM Package transfer method is supported by the eIM over ESipa. eimRetrieveHttps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using HTTPs over TCP as described in section 3.1.2.1

•eimRetrieveCoaps set to 1 indicates support for eIM Package retrieval (see section 3.1.1.1) using CoAP/DTLS over UDP as described in section 3.1.2.2

•eimInjectHttps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using HTTPs over TCP as described in section 3.1.2.1

•eimInjectCoaps set to 1 indicates support for eIM Package injection (see section 3.1.1.2) using CoAP/DTLS over UDP as described in section 3.1.2.2

•eimProprietary set to 1 indicates support of a transport protocol not described in section 3.1.2.

4.3 eIM Identifier

The eimId is an eIM identifier that SHALL exist uniquely within the eUICC’s list of Associated eIMs. The eimId is a text string (ASN.1 type UTF8String) as shown in section

2.11.1.1.1 and section 2.11.1.1.2. The total length of the eimId SHALL not exceed 128 Bytes.

The eimId text string MAY be of the following types as defined by EimIdType in section 2.11.1.1.1: OID, FQDN, and Proprietary.

Where an eIM operator holds or can request an OID assignment, an eIM OID SHOULD be allocated to the eIM and used to encode the eimId.

An eimId of type eimIdTypeOid SHALL be encoded using the OID, as allocated by https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers.

NOTE1:It is up to the eIM owner to define child nodes and values accordingly.

NOTE2:An example OID “iso.org.dod.internet.private.company.eim.eimowner.124” is encoded as follows: “1.3.6.1.4.12345.999.10.124”.

An eimId of type eimIdTypeFqdn SHALL be encoded as a FQDN.

NOTE:An example could be: “eim.enterprise.com”.

For an eimId of type eimIdTypeProprietary the eimId value can be freely chosen, following the requirements set out in this section.

4.4 Profile MetaData

The profile Metadata as defined in SGP.22 [4] SHALL be replaced as follows: -- ASN1START -- Definition of ProfileInfo ProfileInfo ::= [PRIVATE 3] SEQUENCE { -- Tag 'E3' iccid Iccid OPTIONAL, isdpAid [APPLICATION 15] OctetTo16 OPTIONAL, -- AID of the ISD-P containing the Profile, tag '4F' profileState [112] ProfileState OPTIONAL, -- Tag '9F70' profileNickname [16] UTF8String (SIZE(0..64)) OPTIONAL, -- Tag '90' serviceProviderName [17] UTF8String (SIZE(0..32)) OPTIONAL, -- Tag '91' profileName [18] UTF8String (SIZE(0..64)) OPTIONAL, -- Tag '92' iconType [19] IconType OPTIONAL, -- Tag '93' icon [20] OCTET STRING (SIZE(0..1024)) OPTIONAL, -- Tag '94', see condition in ES10b:GetProfilesInfo profileClass [21] ProfileClass OPTIONAL, -- Tag '95' notificationConfigurationInfo [22] SEQUENCE OF NotificationConfigurationInformation OPTIONAL, -- Tag 'B6' profileOwner [23] OperatorId OPTIONAL, -- Tag 'B7' dpProprietaryData [24] DpProprietaryData OPTIONAL, -- Tag 'B8' profilePolicyRules [25] PprIds OPTIONAL, -- Tag '99' serviceSpecificDataStoredInEuicc [34] VendorSpecificExtension OPTIONAL, -- Tag 'BF22' ecallIndication [123] BOOLEAN OPTIONAL, -- Tag '9F7B' fallbackAttribute [38] BOOLEAN DEFAULT FALSE, -- Tag '9F26', indicates a Fallback Profile if set to TRUE fallbackAllowed [103] BOOLEAN OPTIONAL -- Tag '9F67', indicates if Fallback is authorized by the Profile Owner } -- ASN1STOP

The data item ecallIndication MAY be present. If absent it SHALL be treated as if it was set to FALSE. An ecallIndication data item set to TRUE indicates, that the enabling or disabling of an Emergency Profile MAY be triggered using the ES10b.EnableEmergencyProfile and ES10b.DisableEmergencyProfile functions.

It SHALL NOT be possible to have multiple Profiles on an eUICC with the ecallIndication data item set to TRUE.

The data item fallbackAttribute MAY be present. If set to TRUE, the Profile can be enabled using the ES10b.ExecuteFallbackMechanism function. If the fallbackAttribute data item is absent or set to FALSE the Profile can not be enabled using the ES10b.ExecuteFallbackMechanism function.

It SHALL NOT be possible to have multiple Profiles on an eUICC with the fallbackAttribute set to TRUE.

The data item fallbackAllowed MAY be present. Only if set to TRUE, it SHALL be possible to set the fallbackAttribute.

NOTE:The Profile Owner decides upon Profile generation to include or not the fallbackAllowed flag into the Profile.

5 Functions

5.1 Overview of Functions per Interface

This section provides the description of the interfaces and functions within the Remote SIM Provisioning and Management system involving the eUICC, including the following:

eUICC Interfaces
   • ES6: The interface used by the Operator to manage the content of their Profile.
   • ES8+: Provides a secure end-to-end channel between the SM-DP+ and the eUICC
     for the administration of the ISD-P and the associated Profile during download and
     installation.
   • ES9+: Used to provide a secure transport between the SM-DP+ and the IPAe for the
     delivery of the Profile Package.
   • ES10a: Used by the IPAd to get the configured addresses from the eUICC for Root
     SM-DS, and optionally for the default SM-DP+.
   • ES10b: Used by the IPAd to transfer a Profile Package to the eUICC.
   • ES11: Interface between the IPAe and an SM-DS (Alternative SM-DS or Root SM-
     DS) for the Event Retrieval.
   • ESipa: Interface between an eIM and an IPA used to trigger a Profile download at the
     IPA and to provide a secure transport for the delivery of eUICC Packages unless the
     underlying transport provides necessary security.
   • ESep: Logical end-to-end interface between the eIM and the eUICC used to transfer
     eUICC Packages for Profile State Management and eIM configuration by eIM.

Server to Server Interfaces

•    ES2+: Interface between the Operator and the SM-DP+ used by the Operator to
     order Profile Package preparation.
•    ES12: Interface between the SM-DP+ and an SM-DS (Alternative SM-DS or Root
     SM-DS) for the Event management.
Device to RSP Server Interfaces
  • ES9+: Used to provide a secure transport between the SM-DP+ and the IPAd for the
      delivery of the Profile Package.
  • ES11: Interface between the IPAd and an SM-DS (Alternative SM-DS or Root SM-
      DS) for the Event Retrieval.
eIM interfaces
   • ES9+’: Used to provide a secure transport between the SM-DP+ and the eIM for the
       delivery of the Bound Profile Package.
•    ESipa: Interface between an eIM and an IPA used to trigger a Profile download at the
     IPA and to provide a secure transport for the delivery of eUICC Packages unless the
     underlying transport provides necessary security.
•    ESep: Logical end-to-end interface between the eIM and the eUICC used to transfer
     eUICC Packages for Profile State Management and eIM configuration by eIM.
•    ES11’: Interface between the eIM and the SM-DS (Alternative SM-DS or Root SM-
     DS) for the Event Retrieval.

The following table presents the normative list of all the functions that are defined in this section.

Request-Response Functions:

                                                                                 Function
Interface Functions                                                              provider
                                                                                 Role
ES2+       As defined in section 5.3 of SGP.22 [4].                              SM-DP+
ES6        As defined in section 5.2 of SGP.22 [4].                               ISD-P
ES8+       As defined in section 5.5 of SGP.22 [4].                               eUICC
           As defined in section 5.6 of SGP.22 [4].
ES9+
           AuthenticateClient
           InitiateAuthentication
           GetBoundProfilePackage                                                SM-DP+
ES9+’      AuthenticateClient
           HandleNotification
           CancelSession
           As defined in section 5.7 of SGP.22 [4].    ISD-R
ES10a                                                   (IPA
           GetEuiccConfiguredAddresses                Services)
           LoadEuiccPackage
           GetEUICCInfo
           GetEUICCChallenge
           AddInitialEim
           eUICCMemoryReset
           AuthenticateServer
           PrepareDownload
           LoadBoundProfilePackage
           CancelSession
           GetCerts
           GetEID
           RetrieveNotificationsList                   ISD-R
ES10b      RemoveNotificationFromList                   (IPA
           GetRAT                                     Services)
           GetProfilesInfo
           ImmediateEnable
           ProfileRollback
           ConfigureImmediateProfileEnabling
           GetEimConfigurationData
           ExecuteFallbackMechanism
           ReturnFromFallback
           EnableEmergencyProfile
           DisableEmergencyProfile
           GetConnectivityParameters
           SetDefaultDpAddress
ES11       As defined in section 5.8 of SGP.22 [4].    SM-DS
           InitiateAuthentication
ES11’                                                  SM-DS
           AuthenticateClient
ES12       As defined in section 5.9 of SGP.22 [4].    SM-DS
           TransferEimPackage                           IPA
           InitiateAuthentication
           GetBoundProfilePackage
ESipa      AuthenticateClient
                                                        eIM
           GetEimPackage
           ProvideEimPackageResult
           HandleNotification
            CancelSession
            Enable
            Disable
            Delete
            ListProfileInfo
            GetRAT
ESep        ConfigureImmediateEnable                                            eUICC
            AddEim
            UpdateEim
            DeleteEim
            ListEim
            SetDefaultDpAddress

Table 5 Request-Response Functions

Notification Handler Functions:

                                                                 Function
Interface    Notification handler functions
                                                                 handler/recipient
ES2+         As defined in section 5.3 of SGP.22 [4].            Operator
ES9+         HandleNotification                                  SM-DP+
ES9+’        HandleNotification                                  SM-DP+
ESipa        HandleNotification                                  eIM

Table 6 Notification Handler Functions

5.2 Server to Server Function Commonalities

Each function represents an entry point that is provided by a Role (function provider), and that can be called by other Roles (function requester).

5.2.1 Common Data Types

The functions provided in this section deal with management of the eUICC and Profile, so that the common data defined in this section needs to be used in most of the functions.

Type name              Description                                    Type definition
As defined in table 21 of section 5.2.1 of SGP.22 [4]

Table 7 Common data types

5.2.2 Request-Response Function

As defined in section 5.2.2 of SGP.22 [4].

5.2.3 Notification Handler Function

As defined in section 5.2.3 of SGP.22 [4].

5.2.4 Functions Input Header

As defined in section 5.2.4 of SGP.22 [4].

5.2.5 Functions Output Header

As defined in section 5.2.5 of SGP.22 [4].

5.2.6 Status Code

This specification relies on subject codes and reason codes as defined in section 5.2.6 of SGP.22 [4]. In addition, this specification defines additional codes.

5.2.6.1 Subject Code

Hereunder are listed the subject codes used in this specification:

1. Generic (as defined in SGP.02 [6])

1.1. Function Requester (as defined in SGP.02 [6])

1.2. Function Provider (as defined in SGP.02 [6])

1.3. Protocol (as defined in SGP.02 [6])

1.3.1. Protocol Format (as defined in SGP.02 [6])

1.3.2. Protocol Version (as defined in SGP.02 [6])

1.6. Function (as defined in SGP.02 [6])

8. eUICC Remote Provisioning (as defined in SGP.02 [6])

8.1. eUICC (as defined in SGP.02 [6])

8.1.1. EID (as defined in SGP.02 [6])

8.1.2. EUM Certificate (as defined in SGP.22 [4])

8.1.3. eUICC Certificate (as defined in SGP.22 [4])

8.2. Profile (as defined in SGP.02 [6])

8.2.1. Profile ICCID (as defined in SGP.02 [6])

8.2.5. Profile Type (as defined in SGP.02 [6])

8.2.6. Matching ID (as defined in SGP.22 [4])

8.2.7. Confirmation Code (as defined in SGP.22 [4])

8.2.8. PPR (as defined in SGP.22 [4])

8.2.9. Profile Metadata (as defined in SGP.22 [4])

8.2.10. Bound Profile Package (as defined in SGP.22 [4])

8.8. SM-DP+ (as defined in SGP.22 [4])

8.8.1. SM-DP+ Address (as defined in SGP.22 [4])

8.8.2. Security configuration (as defined in SGP.22 [4])

8.8.3. Specification Version Number (SVN) (as defined in SGP.22 [4])

8.8.4. SM-DP+ Certificate (as defined in SGP.22 [4])

8.8.5 Download order (as defined in SGP.22 [4])

8.9. SM-DS (as defined in SGP.22 [4])

8.9.1. SM-DS Address (as defined in SGP.22 [4])

8.9.2. Security configuration (as defined in SGP.22 [4])

8.9.3. Specification Version Number (SVN) (as defined in SGP.22 [4])

8.9.4 SM-DS Certificate (as defined in SGP.22 [4])

8.9.5. Event Record (as defined in SGP.22 [4])

8.10. RSP Operation (as defined in SGP.22 [4])

8.10.1. TransactionId (as defined in SGP.22 [4])

8.11. GSMA CI (as defined in SGP.22 [4])

8.11.1. Public Key (PK) (as defined in SGP.22 [4])

5.2.6.2 Reason Code

Hereunder are listed the reason codes used in this specification:

1. Access Error (as defined in SGP.02 [6])

1.1. Unknown (Identification or Authentication) (as defined in SGP.02 [6])

1.2. Not Allowed (Authorisation) (as defined in SGP.02 [6])

2. Format Error (as defined in SGP.02 [6])

2.1. Invalid (as defined in SGP.02 [6])

2.2. Mandatory Element Missing (as defined in SGP.02 [6])

2.3. Conditional Element Missing (as defined in SGP.02 [6])

3. Conditions of Use Not Satisfied (as defined in SGP.02 [6])

3.1. Unsupported (as defined in SGP.02 [6])

3.3. Already in Use (Uniqueness) (as defined in SGP.02 [6])

3.7. Unavailable (as defined in SGP.02 [6])

3.8. Refused (as defined in SGP.02 [6])

3.9. Unknown (as defined in SGP.02 [6])

3.10. Invalid Association (as defined in SGP.22 [6])

3.11. Value has Changed (as defined in SGP.22 [6])

4. Processing Error (as defined in SGP.02 [6)

4.2. Execution Error (as defined in SGP.02 [6)

4.3. Stopped on Warning (as defined in SGP.02 [6])

4.8. Insufficient Memory (as defined in SGP.02 [6])

4.10 Time to Live Expired (as defined in SGP.22 [4])

5. Transport Error (as defined in SGP.02 [6])

5.1. Inaccessible (as defined in SGP.02 [6])

6. Security Error (as defined in SGP.02 [6])

6.1. Verification Failed (as defined in SGP.02 [26)

6.3. Expired (as defined in SGP.22 [4])

6.4. Maximum number of retries exceeded (as defined in SGP.22 [4])

5.2.6.3 Common Function Status Code

As defined in SGP.02 [6].

5.3 ES2+ (Operator -- SM-DP+)

ES2+ is the interface between:

•The Operator.

•SM-DP+

This interface is used by the Operator to order the Profile Package preparation for specific eUICC(s) and the delivery of the Profile Package from the SM-DP+. This interface is identical to the one defined in section 5.3 of SGP.22 [4].

5.4 ES6 (Operator -- eUICC)

ES6 is the interface between:

•The Operator.

•eUICC (Enabled Profile)

This interface is used by the Operator to make modifications on their Profile in the eUICC using legacy OTA mechanisms. This interface is identical to the one defined in section 5.4 of SGP.22 [4].

NOTE :                 SCP80 over SMS might not be supported in ES6 in case of NCD.

5.5 ES8+ (SM-DP+ -- eUICC)

The ES8+ is the interface between:
      •      The SM-DP+ (Profile Package Binding function).
      •      The eUICC.
This interface is intended to be tunnelled either over:
   • the ES9+ and ES10b interfaces for direct profile download (i.e., the IPA directly
        communicates with the SM-DP+) as shown in Figure 29 or
   • ES9+', ESipa, and ES10b for indirect profile download (i.e., the IPA communicates
        with the SM-DP+ via the eIM) as shown in Figure 30.
SM-DP+                                                 IoT Device
 Profile                   Profile                                IPA
Package                   Package
Binding                   delivery

eUICC

ES8+ functions     ES8+                       ES8+                         ES8+
ES9+                         ES10b

Figure 29 ES8+ interface through ES9+ and ES10b

SM-DP+                                 eIM                          IoT Device
 Profile                    Profile                                          IPA
Package                    Package
Binding                    delivery

eUICC

ES8+ functions   ES8+                ES8+         ES8+             ES8+            ES8+
                                    ES9+’                       ESipa             ES10b

Figure 30 ES8+ through ES9+’ ESipa, and ES10b

The ES8+ functions are addressed to the eUICC through a secure channel established between the Profile Package Binding function of the SM-DP+ and the eUICC.

The ES8+ functions are called by the SM-DP+ and executed by the eUICC.

All the functions related to ES8+ SHALL be processed as defined in section 5.5 of SGP.22 [4] with the following modifications to the command data structure of the ES8+.StoreMetadata function.

Command data

The command data for this function is identified by the data structure defined hereunder. -- ASN1START StoreMetadataRequest ::= [37] SEQUENCE { -- Tag 'BF25' iccid Iccid, serviceProviderName [17] UTF8String (SIZE(0..32)), -- Tag '91' profileName [18] UTF8String (SIZE(0..64)), -- Tag '92' (corresponds to 'Short Description' defined in SGP.21 [2]) iconType [19] IconType OPTIONAL, -- Tag '93' (JPG or PNG) icon [20] OCTET STRING (SIZE(0..1024)) OPTIONAL, -- Tag '94' (Data of the icon. Size 64 x 64 pixel. This field SHALL only be present if iconType is present) profileClass [21] ProfileClass DEFAULT operational, -- Tag '95' notificationConfigurationInfo [22] SEQUENCE OF NotificationConfigurationInformation OPTIONAL, profileOwner [23] OperatorId OPTIONAL, -- Tag 'B7' profilePolicyRules [25] PprIds OPTIONAL, -- Tag '99' serviceSpecificDataStoredInEuicc [34] VendorSpecificExtension OPTIONAL, -- Tag 'BF22' serviceSpecificDataNotStoredInEuicc [35] VendorSpecificExtension OPTIONAL, -- Tag ‘BF23’ ecallIndication [123] BOOLEAN OPTIONAL, -- Tag '9F7B' fallbackAllowed [103] BOOLEAN OPTIONAL -- Tag '9F67' } -- ASN1STOP

Upon reception of a StoreMetadataRequest containing ecallIndication the following steps are performed in addition to the procedure defined in SGP.22[4] section 5.5.3:

Start Conditions:

•The target Profile SHALL NOT have the fallbackAllowed set Procedure:

The eUICC SHALL:

1. Verify that the target Profile has the fallbackAllowed not set. If it is set, the
   eUICC SHALL stop the procedure and return error with reason
   incorrectInputValues.
2. Set the Emergency Profile Attribute for the target Profile.
3. Generate as many Notifications as configured in the metadata.
4. Return ok.

5.6 ES9+ (IPA -- SM-DP+)

ES9+ is the interface between:

•The IPA entity.

•The SM-DP+

The IPA SHALL communicate with the SM-DP+ secured by HTTPS in server authentication mode as described in SGP.22 [4] section 2.6.6.

This interface is identical to the ES9+ interface defined in section 5.6 of SGP.22 [4], where the IPA plays the role of LPA, except Function (ES9+): AuthenticateClient which is defined bellow.

5.6.1 Function (ES9+): AuthenticateClient

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DP+

Description:

This function SHALL be called by the IPA to request the authentication of the eUICC by the SM-DP+.

This function is identical to the ES9+.AuthenticateClient function defined in section 5.6.3 of SGP.22 [4], where the IPA plays the role of LPA and the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification. -- ASN1START AuthenticateClientRequest ::= [59] SEQUENCE { -- Tag 'BF3B' transactionId [0] TransactionId, authenticateServerResponse [56] AuthenticateServerResponse -- This is the response from ES10b.AuthenticateServer } -- ASN1STOP

5.7 ES9+’ (eIM -- SM-DP+)

ES9+’ is the interface between:

•The eIM entity.

•The SM-DP+.

The eIM SHALL communicate with the SM-DP+ secured by HTTPS in server authentication mode as described in SGP.22 [4] section 5.6 using the TLS requirements in SGP.22 [4] section 2.6.6.

5.7.1 Function (ES9+’): InitiateAuthentication

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DP+

Description:

This function SHALL be called by the eIM to authenticate the SM-DP+.

This function is identical to the ES9+.InitiateAuthentication function defined in section 5.6.1 of SGP.22 [4], where the eIM plays the role of LPA. In addition, in case the IPA has sent all the necessary input data in ESipa.InitiateAuthentication request, the eIM SHALL forward it as ES9+'.InitiateAuthentication request. Otherwise, the eIM SHALL complete the missing input data as described in ES9+.InitiateAuthentication function.

5.7.2 Function (ES9+’): GetBoundProfilePackage

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DP+

Function Caller Entity: eIM

Description:

This function SHALL be called by the eIM to request the delivery and the binding of a Profile Package for the eUICC.

This function is identical to the ES9+.GetBoundProfilePackage function defined in section 5.6.2 of SGP.22 [4], where the eIM plays the role of LPA.

5.7.3 Function (ES9+’): AuthenticateClient

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DP+

Function Caller Entity: eIM

Description:

This function SHALL be called by the eIM to request the authentication of the eUICC by the SM-DP+.

This function is identical to the ES9+.AuthenticateClient function defined in section 5.6.3 of SGP.22 [4], where the eIM plays the role of LPA and the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification.

5.7.4 Function (ES9+’): HandleNotification

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DP+

Function Caller Entity: eIM

Description:

This function SHALL be called by the eIM to notify the SM-DP+ that a Profile Management Operation has successfully been performed on the eUICC. This function is called by the eIM upon the receipt by the eIM of either an ESipa.HandleNotification function call or an ESipa.ProvideEimPackageResult function call sent by the IPA containing a PendingNotification. When the received PendingNotification contains a ProfileInstallation result that is part of an ongoing Indirect Profile Download session, the eIM SHALL send the ES9+’.HandleNotification call to the SM-DP+ that is participating in that Indirect Profile Download session. When the PendingNotification contains an OtherSignedNotification, the eIM SHALL send the ES9+’.HandleNotification to the NotificationAddress contained in the NotificationMetadata of the OtherSignedNotification.

This function is identical to the ES9+.HandleNotification function defined in section 5.6.4 of SGP.22 [4], where the eIM plays the role of LPA. In addition, in case the IPA has sent all the necessary input data in ESipa.HandleNotification request, the eIM SHALL forward it as ES9+'.HandleNotification request. Otherwise, the eIM SHALL complete the missing input data as described in ES9+.HandleNotification function.

5.7.5 Function (ES9+’): CancelSession

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DP+

Description:

This function SHALL be called by the eIM to request the cancellation of an on-going RSP session.

This function is identical to the ES9+.CancelSession function defined in section 5.6.5 of SGP.22 [4], where the eIM plays the role of LPA. In addition, in case the IPA has sent all the necessary input data in ESipa.CancelSession request, the eIM SHALL forward it as ES9+'.CancelSession request. Otherwise, the eIM SHALL complete the missing input data as described in ES9+.CancelSession function.

5.8 ES10a (IPA -- eUICC)

5.8.1 Function (ES10a): GetEuiccConfiguredAddresses

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10a.GetEuiccConfiguredAddresses function defined in section 5.7.3 of SGP.22 [4], where the IPA plays the role of LPA.

NOTE :      the default SM-DP+ address that is stored in the eUICC can be updated
            through the functions ConfigureImmediateProfileEnabling (described in
            5.9.17 of this specification) and ConfigureImmediateEnable (described in
            5.13.6 of this specification) as well as functions
            ES10b.SetDefaultDpAddress as described in 5.9.25 of this specification and
            ESep.SetDefaultDpAddress as described in 5.13.11 of this specification.

5.9 ES10b (IPA -- eUICC)

5.9.1 Function (ES10b): LoadEuiccPackage

Related Procedures: Generic eUICC Package Download and Execution

Function Provider Entity: ISD-R (IPA Services)

Description:

This function executes a eUICC Package.

On reception of this package, the eUICC SHALL:

•   Retrieve the public key of the Associated eIM using the eimId in
    euiccPackageSigned. If the eimId is unknown, the eUICC SHALL return an
    unsigned eUICC Package error result (euiccPackageErrorUnsigned) containing
    the eimId received in the euiccPackageSigned.
•   Verify the eimSignature created upon euiccPackageSigned concatenated with
    associationToken using the retrieved eIM public key. If no association token is
    configured for the eIM, the associationToken data object SHALL be used with the
    value set to zero for verifying the signature. If the signature is invalid, the eUICC
    SHALL return an unsigned eUICC Package error result
    (euiccPackageErrorUnsigned) containing the eimId received in the
    euiccPackageSigned. If and only if an association token is configured for the eIM,
    the eUICC SHALL return the associationToken in the error result.
•   Verify that the eidValue in euiccPackageSigned matches its own EID. If the EID
    verification fails, the eUICC SHALL return a signed eUICC error result
    (euiccPackageErrorSigned) containing the invalidEid error code.
•   Verify that the counterValue in euiccPackageSigned is greater than the counter
    value stored in the eUICC for the Associated eIM. If the counter value verification
    fails, the eUICC SHALL return a signed eUICC Package error result
    (euiccPackageErrorSigned) containing the replayError error code.
•   Reset any authorisation previously granted to use the Profile Rollback Mechanism
    (and any related data).
•   Execute PSMO(s) or eCO(s) contained in the eUICC Package and generate the
    corresponding PSMO or eCO result(s) (euiccResultData) sequentially.
If the eUICC encounters an error for a PSMO or an eCO, the eUICC SHALL
terminate processing of the remaining command sequence and generate
euiccResultData containing processingTerminated with the following error
codes:
o For a PSMO 'List Profile Info' request, if the eUICC cannot generate the
  euiccResultData due to the size limit of the response data, the error code
  SHALL be resultSizeOverflow.

NOTE:this could happen, e.g., when retrieving Profile Metadata of multiple Profiles containing large icons.

o If a PSMO or an eCO in the eUICC Package is unknown or unsupported, or the
  command data cannot be interpreted, the error code SHALL be
  unknownOrDamagedCommand.
•   Generate a signed eUICC Package Result (euiccPackageResultSigned) with the
    execution results of the PSMOs/eCOs (euiccResultData). The eUICC Package
    Result SHALL be signed using SK.EUICC.ECDSA. In case there are more than one
    SK.EUICC.ECDSA available for signing, the SK.EUICC.ECDSA chaining back to the
    CI public key identified by the euiccCiPKId of the eIM Configuration Data (of the
    Associated eIM for which the eUICC Package Result is intended) SHALL be used.
    The signed data includes the next (not used) value of the sequence number (defined
    in SGP.22 [4] for use with Notifications).
•   Increment the sequence number in eUICC storage by 1.
•   Update the counter value stored in the eUICC for the Associated eIM to the
    counterValue received in the euiccPackageSigned.
•   Return the signed eUICC Package Result (euiccPackageResultSigned).

The ES10b.LoadEuiccPackage function SHALL be processed in an atomic way, meaning that in case of non-resumable interruption (e.g., power loss), the eUICC SHALL revert all performed changes related to PSMOs or eCOs within that eUICC Package. The eUICC SHALL restore its original state prior to execution of the ES10b.LoadEuiccPackage, including the counterValue. Any intermediate result generated for the eUICC Package SHALL be discarded.

NOTE:In case of non-resumable interruption the ISD-R withdraws the previously received eUICC Package.

The IPAd MAY call the ES10b.LoadEuiccPackage function again, including the same eUICC Package, if it detects that the previous processing was interrupted.

NOTE:How the IPA detects the interruption and how an IPA resubmits the eUICC Package is out of scope.

Command Data

The EuiccPackageRequest as defined in section 2.11.1.1.

Response Data

The EuiccPackageResult as defined in section 2.11.2.1.

5.9.2 Function (ES10b): GetEUICCInfo

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.GetEUICCInfo function defined in section 5.7.8 of SGP.22 [4], where the IPA plays the role of LPA.

The response data for EUICCInfo2 SHALL follow the ASN.1 message definition below replacing the EUICCInfo2 described in section 5.7.8 and Annex H of SGP.22 [4].

NOTE:EUICCInfo2 in this specification is based on EUICCInfo2 as defined in SGP.22 [4] but has been extended for IoT purposes. -- ASN1START EUICCInfo2 ::= [34] SEQUENCE { -- Tag 'BF22' profileVersion [1] VersionType, -- Base eUICC Profile package version supported svn [2] VersionType, -- GSMA SGP.22 version supported (SVN)referenced by SGP.32 euiccFirmwareVer [3] VersionType, -- eUICC Firmware version extCardResource [4] OCTET STRING, -- Extended Card Resource Information according to ETSI TS 102 226 uiccCapability [5] UICCCapability, ts102241Version [6] VersionType OPTIONAL, globalplatformVersion [7] VersionType OPTIONAL, rspCapability [8] RspCapability, euiccCiPKIdListForVerification [9] SEQUENCE OF SubjectKeyIdentifier, -- List of CI Public Key Identifiers supported on the eUICC for signature verification euiccCiPKIdListForSigning [10] SEQUENCE OF SubjectKeyIdentifier, -- List of CI Public Key Identifier supported on the eUICC for signature creation euiccCategory [11] INTEGER { other(0), basicEuicc(1), mediumEuicc(2), contactlessEuicc(3) } OPTIONAL, forbiddenProfilePolicyRules [25] PprIds OPTIONAL, -- Tag '99' ppVersion VersionType, -- Protection Profile version sasAcreditationNumber UTF8String (SIZE(0..64)), certificationDataObject [12] CertificationDataObject OPTIONAL, treProperties [13] BIT STRING { isDiscrete(0), isIntegrated(1), usesRemoteMemory(2) -- refers to the usage of remote memory protected by the Remote Memory Protection Function described in SGP.21 [4] } OPTIONAL,

   treProductReference [14] UTF8String OPTIONAL, -- Platform_Label as defined in
GlobalPlatform DLOA specification [57]
   additionalEuiccProfilePackageVersions [15] SEQUENCE OF VersionType OPTIONAL,
   ipaMode [16] IpaMode OPTIONAL, -- active IPA, mandatory within SGP.32
   euiccCiPKIdListForSigningV3 [17] SEQUENCE OF SubjectKeyIdentifier OPTIONAL, --
not used by this version of SGP.32.
   additionalEuiccInfo [18] OCTET STRING (SIZE(0..32)) OPTIONAL,   -- not used by
this version of SGP.32
   highestSvn [19] VersionType OPTIONAL, -- not used by this version of SGP.32
   iotSpecificInfo [20] IoTSpecificInfo OPTIONAL -- mandatory within SGP.32
}

-- Definition of IoTSpecificInfo IoTSpecificInfo ::= SEQUENCE { iotVersion [0] SEQUENCE OF VersionType, -- SGP.32 version(s) supported by the eUICC, at least one must be present ecallSupported [1] NULL OPTIONAL, -- if present, eUICC supports the Emergency Mechanism fallbackSupported [2] NULL OPTIONAL -- if present, eUICC supports the Fallback Mechanism }

-- Definition of IpaMode IpaMode ::= INTEGER { ipad (0), -- IPAd is active ipae (1) -- IPAe is active } -- ASN1STOP The procedures related to the eUICC Profile Package versioning and associated to profileVersion, additionalEuiccProfilePackageVersions and uiccCapability are described in section 5.7.8 of SGP.22 [4].

NOTE :       as part of the TCA eUICC Profile Package specification [29], in version v3.3
             a new Profile type called “IoT Minimal Profile” has been introduced with the
             intention to be useful for the provisioning of eUICCs in Network Constrained
             Devices.

The euiccCiPKIdListForSigningV3, additionalEuiccInfo, and highestSvn fields are not used in this version of the specification. The eUICC SHALL NOT include these fields in euiccInfo2. The SM-DP+ SHOULD ignore these fields if received with iotSpecificInfo being present.

The ioTSpecificInfo data object SHALL be present.

If the eUICC supports the Fallback Mechanism, the fallbackSupported flag SHALL be present within IoTSpecificInfo.

The ecallSupported data object SHALL be present within IoTSpecificInfo. If the flag is set, the eUICC SHALL support the Emergency Mechanism.

5.9.3 Function (ES10b): GetEUICCChallenge

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.GetEUICCChallenge function defined in section 5.7.7 of SGP.22 [4], where the IPA plays the role of LPA.

5.9.4 Function (ES10b): AddInitialEim

Related Procedures: Addition of initial eIM by IPAd

Function Provider Entity: eUICC (ISD-R)

Description:

This function is used by the IPAd to store eIM Configuration Data to the eUICC in case the eUICC does not contain any eIM Configuration Data.

Upon reception of this function call, the eUICC SHALL:

•    Check if any eIM Configuration Data is already present in the eUICC. If so, the
     eUICC SHALL return an error code associatedEimAlreadyExists.
•    Check if counterValue exceeds the maximum value supported by the eUICC. If so,
     the eUICC SHALL return the error code counterValueOutOfRange.
•    Check if the eUICC has enough memory to store the list of provided eIM
     Configuration Data. If not, the eUICC SHALL return an error code
     insufficientMemory.
•    Check that the sub-field eimId of EimConfigurationData in each entry of the
     eimConfigurationDataList is present and that its length does not exceed the allowed
     maximum value. Otherwise, the eUICC SHALL return an error code commandError.

•Check that the sub-field euiccCiPKId of EimConfigurationData in each entry of the eimConfigurationDataList, if present, is a valid entry within euiccCiPKIdListForSigning in eUICCInfo2. If not, the eUICC SHALL return an error code ciPKUnknown.

•If requested for an Associated eIM, calculate an associationToken. If associationToken is not set to -1 the eUICC SHALL return an error code invalidAssociationToken.

•Store the provided list of eIM Configuration Data, including the associationToken (if requested).

•Return the associationToken for each Associated eIM where it is requested.

NOTE:Any further addition of eIM Configuration Data can be performed by an Associated eIM using signed eUICC Packages containing eCO(s) as defined in section 3.5.1.1.

The function SHALL be performed in an atomic way, meaning that in case of any error during the function execution, the command SHALL stop and SHALL leave the eIM Configuration Data in their original state prior to function execution.

Command Data

The command data SHALL be coded as follows:

-- ASN1START AddInitialEimRequest ::= [87] SEQUENCE { -- Tag 'BF57' eimConfigurationDataList [0] SEQUENCE OF EimConfigurationData } -- ASN1STOP

The following sub-fields of EimConfigurationData SHALL be present in each entry of the eimConfigurationDataList:

•eimId;

•counterValue; and

•either eimPublicKey or eimCertificate.

The eimIdType, the associationToken (with the value set to -1 to request the calculation of an association token for the new Associated eIM) and eimFqdn are optional for the IPA to provide in each EimConfigurationData. If not provided, the eUICC SHALL assign the value eimIdTypeProprietary before storing the eIM Configuration Data. The eimSupportedProtocol is optional for the IPA to provide in EimConfigurationData. If not provided, the eUICC SHALL assign the value where only the eimProprietary bit is set before storing the eIM Configuration Data. The euiccCiPKId is optional for the IPA to provide in EimConfigurationData. If not provided, the eUICC SHALL assign the value of first entry of euiccCiPKIdListForSigning in eUICCInfo2 before storing the eIM Configuration Data. The trustedPublicKeyDataTls is optional for the IPAd to provide in each EimConfigurationData data object.

NOTE:It is IPA's responsibility to correctly formulate each entry, including the uniqueness of eimId, and the eUICC is not mandated to check the validity.

Response Data

The response data SHALL be coded as follows:
-- ASN1START
AddInitialEimResponse ::= [87] CHOICE { -- Tag 'BF57'
   addInitialEimOk SEQUENCE OF CHOICE {
      associationToken [4] INTEGER,
      addOk NULL
   },
   addInitialEimError INTEGER {
         insufficientMemory(1),
      associatedEimAlreadyExists (2),
      ciPKUnknown(3),
      invalidAssociationToken(5),
      counterValueOutOfRange(6),
      commandError(7),
      undefinedError(127)
   }
}
-- ASN1STOP

5.9.5 Function (ES10b): eUICCMemoryReset

Related Procedures: eUICC Memory Reset

Function Provider Entity: ISD-R (IPA Services)

Description:

NOTE:ES10c.eUICCMemoryReset function defined in SGP.22 [4] has a tag number 'BF34'.

This function deletes selected subsets of the Profiles stored on an eUICC regardless of their enabled status or any Profile Policy Rules. The following subsets are defined:

•    Operational Profiles
•    Test Profiles that were not pre-installed (i.e., Test Profiles that were "field loaded")
•    Test Profiles that were pre-installed (i.e., Test Profiles that were loaded in the factory)
•    Provisioning Profiles

NOTE:The identification of pre-installed Test Profiles is out of the scope of this specification.

The eUICC returns a status in resetResult indicating whether any Profiles were deleted.

•    The eUICC returns ok if at least one Profile is deleted.
•    The eUICC returns nothingToDelete if no Profile is deleted.

This function can also be used to:

•    Reset the default SM-DP+ address to its initial value. In this context both ok and
     nothingToDelete response in resetResult indicates a successful execution of
     resetting the default SM-DP+ address.
•    Remove all eIM Configuration Data. The execution result of this operation is returned
     in resetEimResult as described below.
•    Reset the configuration of the immediate Profile enabling. The execution result of this
     operation is returned in resetImmediateEnableConfigResult as described
     below.

Any combination MAY be specified in the request.

If the eUICC does not support Test Profiles, then a request to delete them is ignored.

The eUICC Memory Reset SHALL be performed in an atomic and non-reversible way in case of external interruptions (e.g., power loss): the eUICC SHALL continue the processing of that command upon the next eUICC power on. In case of any other error during the function execution, the command SHALL stop and SHALL leave the eUICC and the involved Profiles in their original states prior to function execution.

NOTE:How this function is protected from misuse is implementation specific.

Upon reception of this function call, the eUICC SHALL:

•If the Emergency Profile is enabled, terminate the command and return error code ecallActive.

•If the eUICCMemoryReset function call indicates at least one of deleteOperationalProfiles, deleteFieldLoadedTestProfiles, deletePreLoadedTestProfiles or deleteProvisioningProfiles, perform the following:

o If there is an Enabled Profile with a proactive session ongoing, the eUICC SHALL
  perform one of the following:
▪   terminate the command and return error code catBusy.
▪   internally terminate the proactive session and prepare to send the
    REFRESH proactive command as the next proactive command. If a
    TERMINAL RESPONSE is still outstanding, the REFRESH proactive
    command SHALL only be sent after reception of the TERMINAL
    RESPONSE.

NOTE:In case of the catBusy error, the Device MAY take implementation-dependent action to terminate the proactive command session, and MAY send the eUICC Memory Reset command again without any further End User interaction.

o Delete all the selected ISD-Ps with their Profiles regardless of their enabled status
  or Profile Policy Rules and all related Profiles Metadata stored in the ISD-R and
  prepare resetResult.
o For each deleted Profile, the eUICC SHALL generate as many Notifications as
  configured in its Profile Metadata (notificationConfigurationInfo) in the
  format of OtherSignedNotification.
•   If the eUICCMemoryReset function call indicates resetDefaultSmdpAddress:
    reset the default SM-DP+ address to its default value.
•   If the eUICCMemoryReset function call indicates resetEimConfigData: remove all
    eIM Configuration Data of all Associated eIMs and prepare resetEimResult.
         o If there is no eIM Configuration Data to be removed, the eUICC SHALL return
             error code nothingToDelete.
         o If the command is not supported by the eUICC, the eUICC SHALL return
             error code eimResetNotSupported.

•If the eUICCMemoryReset function call indicates resetImmediateEnableConfig: reset the configuration of the immediate Profile enabling by deactivating immediate Profile enabling and removing any immediate enabling data for use with immediate Profile enabling. The eUICC SHALL also prepare resetImmediateEnableConfigResult.

o If the command is not supported by the eUICC, the eUICC SHALL return error
  code resetIECNotSupported.

•Return EuiccMemoryResetResponse including resetResult. In addition, if resetResult indicates either ok or nothingToDelete:

o   If resetEimConfigData bit was set in the command data, return
    EuiccMemoryResetResponse additionally including resetEimResult.
o   If resetImmediateEnableConfig bit was set in the command data, return
    EuiccMemoryResetResponse additionally including
    resetImmediateEnableConfig.

•If an Enabled Profile was deleted, the ISD-R SHALL send a REFRESH proactive command to the Device with mode "UICC Reset".

Command Data

The command data SHALL be coded as follows:
-- ASN1START
EuiccMemoryResetRequest ::= [100] SEQUENCE { -- Tag 'BF64'
   resetOptions [2] BIT STRING {
      deleteOperationalProfiles(0),
      deleteFieldLoadedTestProfiles(1),
      resetDefaultSmdpAddress(2),
      deletePreLoadedTestProfiles(3),
      deleteProvisioningProfiles(4),
      resetEimConfigData(5),
      resetImmediateEnableConfig (6)
   }
}
-- ASN1STOP
Response Data

The response data SHALL be coded as follows: -- ASN1START EuiccMemoryResetResponse ::= [100] SEQUENCE { -- Tag 'BF64' resetResult INTEGER {ok(0), nothingToDelete(1), catBusy(5), ecallActive(104), undefinedError(127)}, resetEimResult INTEGER {ok(0), nothingToDelete(1), eimResetNotSupported(2), undefinedError(127)} OPTIONAL, resetImmediateEnableConfigResult INTEGER {ok(0), resetIECNotSupported (1), undefinedError(127)} OPTIONAL } -- ASN1STOP

5.9.6 Function (ES10b): AuthenticateServer

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.AuthenticateServer function defined in section 5.7.13 of SGP.22 [4], where the IPA plays the role of LPA and the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification. The following additional eUICC behaviour applies after attaching the received RSP Server Certificate in the RSP session context:

•If immediate Profile enabling is activated, the eUICC SHALL, in case the MatchingID is missing in CtxParams1, verify that the OID in the RSP Server Certificate and

FQDN in serverSigned1 match to the default SM-DP+ data (OID and FQDN)
stored in the eUICC. If the verification is successful, the eUICC SHALL grant
immediate enabling of the Profile. Regardless of the verification result, the eUICC
continues the processing of this function by generating euiccSigned1.

5.9.7 Function (ES10b): PrepareDownload

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.PrepareDownload function defined in section 5.7.5 of SGP.22 [4], where the IPA plays the role of LPA.

5.9.8 Function (ES10b): LoadBoundProfilePackage

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.LoadBoundProfilePackage function defined in section 5.7.6 of SGP.22 [4], where the IPA plays the role of LPA.

5.9.9 Function (ES10b): CancelSession

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.CancelSession function defined in section 5.7.14 of SGP.22 [4], where the IPA plays the role of LPA, with the following additional eUICC behaviour:

•The eUICC SHALL revoke any grant to immediately enable a Profile.

NOTE:The following values of CancelSessionReason are not used inthis specification: endUserRejection(0), postponed(1), timeout(2).

5.9.10 Function (ES10b): GetCerts

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is used by the IPA to retrieve the eUICC Certificate and the EUM Certificate from the eUICC. This function can be used at any time by the IPA.

In order to select between multiple of EUM certificates and eUICC certificates within the eUICC the IPA MAY provide the CI Public Key Identifier (euiccCiPKId). If euiccCiPKId is not provided, the first entry of euiccCiPKIdListForSigning in eUICCInfo1 / eUICCInfo2 is used as euiccCiPKId when selecting the EUM certificate and/or eUICC certificate to return.

Command Data The command data SHALL be coded as follows: -- ASN1START GetCertsRequest ::= [86] SEQUENCE { -- Tag 'BF56' euiccCiPKId SubjectKeyIdentifier OPTIONAL -- CI Public Key Identifier supported on the eUICC for signature creation } -- ASN1STOP

Response Data
The response data SHALL be coded as follows:
-- ASN1START
GetCertsResponse ::= [86] CHOICE { -- Tag 'BF56'
   certs SEQUENCE {
      eumCertificate [5] Certificate, -- Tag 'A5'
      euiccCertificate [6] Certificate -- Tag 'A6'
   },
   getCertsError INTEGER {invalidCiPKId(1), undfinedError(127)}
}
-- ASN1STOP

5.9.11 Function (ES10b): RetrieveNotificationsList

Related Procedures: Generic eUICC Package Download and Execution

Function Provider Entity: ISD-R (IPA Services)

Description:

This function retrieves the list of pending Notifications for installed Profiles and/or eUICC Package Results.

Command Data

The command data SHALL be coded as follows:
-- ASN1START
RetrieveNotificationsListRequest ::= [43] SEQUENCE { -- Tag 'BF2B'
   searchCriteria CHOICE {
      seqNumber [0] INTEGER,
      profileManagementOperation [1] NotificationEvent,
      euiccPackageResults [2] NULL
   } OPTIONAL
}
-- ASN1STOP
The searchCriteria data object can be used to filter the list of Notifications or eUICC
Package Results that the eUICC SHALL return.

•seqNumber indicates that the eUICC SHALL return either a Notification or an eUICC Package Result that has the sequence number.

•A bit set to 1 in the profileManagementOperation indicates that the eUICC SHALL return all the Notifications corresponding to this type. The type notificationInstall SHALL include ProfileInstallationResult.

•euiccPackageResults indicates that the eUICC SHALL return all the eUICC Package Results.

If searchCriteria data object is omitted, the eUICC SHALL return all stored Notifications that are in the format of PendingNotificationList..

Response Data

The response data SHALL contain the list of PendingNotification data objects or EuiccPackageResult data objects. The list SHALL be filtered according to the command data. The eUICC MAY provide the Notifications and/or eUICC Package Results in any order within each list. The list SHALL be empty if there are no pending Notifications or eUICC Package Results matching the filtering criteria.

The following is the definition of the RetrieveNotificationsListResponse data object -- ASN1START RetrieveNotificationsListResponse ::= [43] CHOICE { -- Tag 'BF2B' notificationList PendingNotificationList, -- Tag 'A0' notificationsListResultError INTEGER { undefinedError(127)}, -- Tag '81' euiccPackageResultList EuiccPackageResultList -- Tag 'A2' } -- ASN1STOP The PendingNotification is either a ProfileInstallationResult or an OtherSignedNotification according to definition in section 5.7.10 of SGP.22 [4].

5.9.12 Function (ES10b): RemoveNotificationFromList

Related Procedures: Profile Download and Installation, Generic eUICC Package Download and Execution

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.RemoveNotificationFromList function defined in section 5.7.11 of SGP.22 [4], where the IPA plays the role of LPA, with the addition that besides Notifications the function is also used to delete eUICC Package Results. Hence, the provided seqNumber in NotificationSentRequest provided by IPA is either a seqNumber of a Notification or a seqNumber of an eUICC Package Result.

5.9.13 Function (ES10b): GetRAT

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10b.GetRAT function defined in section 5.7.22 of SGP.22 [4], where the IPA plays the role of LPA.

5.9.14 Function (ES10b): GetProfilesInfo

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is based on the ES10c.GetProfilesInfo function defined in section 5.7.15 of SGP.22 [4], where the IPA plays the role of LPA.

The ProfileInfo data object as defined in SGP.22[4] SHALL be replaced by the definition of the section 4.4 of this document. The section 4.4 describes the additional tags.

5.9.15 Function (ES10b): ImmediateEnable

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is used by the IPA to request immediate Profile enabling without eIM involvement. The eUICC MAY be configured to support the immediate enabling.

On reception of this function call, the eUICC SHALL:

•     Verify that, except for Notification retrieval commands, the previous ES10 function
      was an ES10b.LoadBoundProfilePackage. If not, the eUICC SHALL return an error
      code noSessionContext.
•     Verify that immediate enabling was granted for the newly installed Profile. If not, the
      eUICC SHALL return an error code immediateEnableNotAvailable.
•     Verify that the target Profile is not an Emergency Profile. If it is an Emergency Profile
      with ecallIndication set to TRUE, the eUICC SHALL return an error code
      immediateEnableNotAvailable.

If the refreshFlag is not set, the eUICC SHALL then:

•     Check whether there is a proactive session ongoing (which the Device did not
      terminate). If so:
      o the eUICC MAY terminate the ImmediateEnable command with error 'catBusy'.
      o If the eUICC does not terminate the ImmediateEnable command with error
         'catBusy', the eUICC SHALL internally terminate the proactive session and
         ignore any incoming TERMINAL RESPONSE from that proactive session.
•     Close all logical channels which still have an application of the currently Enabled
      Profile selected (which the IoT Device did not close), without generating an error.
•     Reset the PIN status.
   •    Disable the currently Enabled Profile (if any).
   •    Enable the downloaded Profile.
   •    Reset any authorisation previously granted to use the Profile Rollback Mechanism
        (and any related data).
     • Implicitly select the MF on the basic logical channel.
     • Return 'ok' to the IPA.
If the refreshFlag is set:
•   If there is a proactive session ongoing;
    o The eUICC MAY terminate the ImmediateEnable command with error 'catBusy'.
    o If the eUICC does not terminate the ImmediateEnable command with error
         'catBusy', the eUICC SHALL internally terminate the proactive session and send
         the REFRESH command as the next proactive command. If a TERMINAL
         RESPONSE is still outstanding, the REFRESH command SHALL only be sent
         after reception of the TERMINAL RESPONSE.
•   Otherwise, the eUICC SHALL:
    o Mark the currently Enabled Profile as "to be disabled" (if any).
    o Mark the target Profile as "to be enabled".
    o Return 'ok' to the IPA.
    o Send the REFRESH command in "eUICC Profile State Change" mode (if
         supported by the IoT Device) or "UICC Reset" mode to the IoT Device according
         to ETSI TS 102 223 [5].
    o Upon reception of the Terminal Response with result "command performed
         successfully" or upon reset of the eUICC, disable the currently Enabled Profile (if
         any) and enable the downloaded Profile.
    o Upon reception of the Terminal Response with result "temporary problem with
         executing command" or "permanent problem with executing command", the
         eUICC SHALL NOT disable the currently Enabled Profile (if any) nor enable the
         downloaded Profile. Subsequent actions are implementation specific.

Command Data

The command data SHALL be encoded as follows: -- ASN1START ImmediateEnableRequest ::= [90] SEQUENCE { -- Tag 'BF5A' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP Response Data

The response data SHALL be encoded as follows:
-- ASN1START
ImmediateEnableResponse ::= [90] SEQUENCE { -- Tag 'BF5A'
   immediateEnableResult [0] INTEGER {
      ok(0),
      immediateEnableNotAvailable (1),
      noSessionContext(4),
      catBusy(5),
      undefinedError(127)

} } -- ASN1STOP

5.9.16 Function (ES10b): ProfileRollback

Related Procedures: Generic eUICC Package Download and Execution, Profile State Management.

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is used by the IPA to request to roll back to the previously Enabled Profile, if any. If the usage of the Rollback Mechanism had been previously granted by the eIM (i.e., in the last enable PSMO), this function disables the currently Enabled Profile and enables the Profile, if any, that was enabled before the processing of the last eUICC Package. This SHALL be performed in an atomic way, meaning that in case of any error during the function execution, the command SHALL stop and SHALL leave the involved Profiles in their original states (prior to function execution).

NOTE:Before calling the ProfileRollback function with the refreshFlag not being set, the IoT Device has the responsibility to ensure that the relevant conditions for use are met, as indicated for the ES10c.EnableProfile function in section 3.2.1 of SGP.22 [4].

In the following procedure, the target Profile designates the Profile (if any) that was enabled before the processing of the last eUICC Package, and which is to be re-enabled.

Upon reception of the ProfileRollback command, the eUICC SHALL:

•     Check whether the usage of the Rollback Mechanism had been previously granted by
      the eIM. If not, the procedure SHALL stop, and the result of this function SHALL
      indicate an error ('rollbackNotAllowed').
•     Check whether a Profile is currently enabled. If not, the procedure SHALL stop, and
      the result of this function shall indicate an error ('commandError').

If the refreshFlag is not set, the eUICC SHALL:

•Check whether there is a proactive session ongoing (which the Device did not terminate). If so:

o the eUICC MAY terminate the “ES10b.ProfileRollback” function with error
  'catBusy'.
o If the eUICC does not terminate the “ES10b.ProfileRollback” function with
  error 'catBusy', the eUICC SHALL internally terminate the proactive session
  and ignore any incoming TERMINAL RESPONSE from that proactive session.
•     Close all logical channels which still have an application of the currently Enabled
      Profile selected (which the Device did not close), without generating an error.
•     Reset the PIN status.
•   Disable the currently Enabled Profile.
•   Enable the target Profile (if any).
•   Implicitly select the MF on the basic logical channel.
•   Generate a new eUICC Package Result including an additional ProfileRollbackResult
    (see Response Data below) and remove the previous eUICC Package Result (which
    is now obsolete).
•   Return 'ok' and the newly generated eUICC Package Result to the IPA.

NOTE:For subsequent actions by the Device following the enablement of the target Profile, see ES10c.EnableProfile function in section 3.2.1 of SGP.22 [4].

If the refreshFlag is set:

•If there is a proactive session ongoing;

o The eUICC MAY terminate the “ES10b.ProfileRollback” function with error
  'catBusy'.
o If the eUICC does not terminate the “ES10b.ProfileRollback” function with error
  'catBusy', the eUICC SHALL internally terminate the proactive session and send
  the REFRESH command as the next proactive command. If a TERMINAL
  RESPONSE is still outstanding, the REFRESH command SHALL only be sent
  after reception of the TERMINAL RESPONSE.

•Otherwise, the eUICC SHALL:

o Mark the currently Enabled Profile as "to be disabled".
o Mark the target Profile (if any) as "to be enabled".
o Generate a new eUICC Package Result including an additional
  ProfileRollbackResult (see Response Data below) and remove the previous
  eUICC Package Result (which is now obsolete).
o Return 'ok' and the newly generated eUICC Package Result to the IPA.
o Send the REFRESH command in "eUICC Profile State Change" mode (if
  supported by the Device) or "UICC Reset" mode to the Device according to ETSI
  TS 102 223 [5].
o Upon reception of the Terminal Response with result "command performed
  successfully" or upon reset of the eUICC, disable the currently Enabled Profile
  and enable the target Profile (if any).
o Upon reception of the Terminal Response with result "temporary problem with
  executing command" or "permanent problem with executing command", the
  eUICC SHALL NOT disable the currently Enabled Profile nor Enable the target
  Profile (if any). Subsequent actions are implementation specific.

The eUICC MAY start a new proactive UICC session only after a new TERMINAL PROFILE command is executed.

•If the currently Enabled Profile was successfully disabled, the eUICC SHALL generate as many Notifications as configured in its metadata

      (notificationConfigurationInfo) in the format of
      OtherSignedNotification.
•     If the target Profile is successfully enabled, the eUICC SHALL generate as many
      Notifications as configured in its metadata (notificationConfigurationInfo) in
      the format of OtherSignedNotification.

Command Data

The command data SHALL be coded as follows: -- ASN1START ProfileRollbackRequest ::= [88] SEQUENCE { -- Tag 'BF58' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP Response Data

The response data SHALL be coded as follows:
-- ASN1START
ProfileRollbackResponse ::= [88] SEQUENCE { -- Tag 'BF58'
   cmdResult INTEGER {
      ok(0),
      rollbackNotAllowed(1), -- Usage of rollback was not granted by the eIM
      catBusy(5),
      commandError(7),
      undefinedError(127)
   },
   eUICCPackageResult [81] EuiccPackageResult OPTIONAL
}
-- ASN1STOP
The eUICCPackageResult SHALL be present if the cmdResult is 'ok' (i.e., a Rollback
Mechanism has been executed by the eUICC). In this case, the eUICCPackageResult
SHALL include the same eimId, counterValue, eimTransactionId as the result
generated for the previous eUICC Package, its seqNumber SHALL be incremented, and its
eUICCResultData SHALL include the same PSMO results followed by an additional
RollbackProfileResult (see section 2.11.2.1).

5.9.17 Function (ES10b): ConfigureImmediateProfileEnabling

Related Procedures: Configure by IPA of Immediate Profile Enabling.

Function Provider Entity: eUICC (ISD-R)

Description:

This function is used by the IPA to activate or deactivate immediate Profile enabling in the eUICC and to add or update immediate enabling data used in the immediate Profile enabling.

Upon reception of this function call, the eUICC SHALL:

•     Check if any eIM Configuration Data is already present in the eUICC. If so, the
      eUICC SHALL return an error code associatedEimAlreadyExists.
•     Check if immediateEnableFlag is present in the command data. If
      immediateEnableFlag is present and immediate Profile enabling is not activated,
      the eUICC SHALL activate immediate Profile enabling. If immediateEnableFlag is
       not present and immediate Profile enabling is activated, the eUICC SHALL
       deactivate immediate Profile enabling. In all other cases, the immediate Profile
       enabling state is left unchanged.
    • Check if default SM-DP+ data (defaultSmdpOid and/or defaultSmdpAddress) is
       present in the command data. If so, and if the eUICC has enough memory to store it,
       the eUICC SHALL store it for use in the immediate Profile enabling. If there is not
       enough memory, the eUICC SHALL return an error code insufficientMemory.
The function SHALL be performed in an atomic way, meaning that in case of any error during
the function execution, the command SHALL stop and SHALL leave the immediate Profile
enabling configuration in its original state prior to function execution.

Command Data

The command data SHALL be coded as follows: -- ASN1START ConfigureImmediateProfileEnablingRequest ::= [89] SEQUENCE { -- Tag 'BF59' immediateEnableFlag [0] NULL OPTIONAL, defaultSmdpOid [1] OBJECT IDENTIFIER OPTIONAL, defaultSmdpAddress [2] UTF8String OPTIONAL } -- ASN1STOP

Response Data

The response data SHALL be coded as follows:
-- ASN1START
ConfigureImmediateProfileEnablingResponse ::= [89] SEQUENCE { -- Tag 'BF59'
   configImmediateEnableResult [0] INTEGER {
      ok(0),
      insufficientMemory(1),
      associatedEimAlreadyExists(2),
      undefinedError(127)
   }
}
-- ASN1STOP

5.9.18 Function (ES10b): GetEimConfigurationData

Related Procedures: Reading eIM Configuration Data by IPA

Function Provider Entity: eUICC (ISD-R)

Description:

This function is used by the IPA to read eIM Configuration Data stored in the eUICC.

Command Data

The command data SHALL be coded as follows:
-- ASN1START
GetEimConfigurationDataRequest ::= [85] SEQUENCE { -- Tag 'BF55'
   searchCriteria CHOICE {
      eimId [0] UTF8String (SIZE(1..128))
   } OPTIONAL
}
-- ASN1STOP

The searchCriteria data object can be used to filter the list of eIM Configuration Data that the eUICC SHALL return.

•eimId is the eIM identifier defined in the section 4.3 of this document. It indicates that the eUICC SHALL return the eIM Configuration Data having the specified eimId.

If searchCriteria data object is omitted, the eUICC SHALL return all stored eIM Configuration Data.

Response Data

The response data SHALL be coded as follows: -- ASN1START GetEimConfigurationDataResponse ::= [85] SEQUENCE { -- Tag 'BF55' eimConfigurationDataList [0] SEQUENCE OF EimConfigurationData } -- ASN1STOP

In each EimConfigurationData entry of the eimConfigurationDataList, the eUICC SHALL provide eimId, eimFqdn (if present), eimIdType, trustedPublicKeyDataTls (if present), eimSupportedProtocol, euiccCiPKId (if present) and, if configured, associationToken, and MAY additionally provide either eimPublicKey or eimCertificate. The eUICC SHALL NOT provide counterValue.

If there is no eIM Configuration Data stored in the eUICC, or if there is no eIM Configuration Data matching to the searchCriteria (if received), the eUICC SHALL return an empty list in the eimConfigurationDataList.

5.9.19 Function (ES10b): GetEID

Related Procedures: Profile Download and Installation

Function Provider Entity: ISD-R (IPA Services)

Description:

This function is identical to the ES10c.GetEID function defined in section 5.7.20 of SGP.22 [4], where the IPA plays the role of LPA.

5.9.20 Function (ES10b): ExecuteFallbackMechanism

Function Provider: ISD-R (IPA Services)

Function Caller: IPA

Description:

This function is OPTIONAL for the eUICC and MAY be used by the IPA to instruct the eUICC to enable the Fallback Profile and to disable the currently Enabled Profile.

This function SHALL be performed in an atomic way, meaning that in case of any error during the function execution, the command SHALL stop and SHALL leave the involved Profiles in their original states (prior to function execution).

Upon reception of this function, the ISD-R SHALL:

•verify that there is an enabled Profile. If no, the procedure SHALL stop and the result of this command SHALL indicate error ('commandError(7)'). • verify that the fallbackAttribute is set for a Profile on the eUICC. If not, the procedure SHALL stop, and the result of this command SHALL indicate an error ('fallbackNotAvailable(6)'). • verify that the Emergency Profile is disabled. If it is enabled, the procedure SHALL stop and the result of this command SHALL indicate error ('ecallActive(104)'). • verify that the Fallback Profile is disabled. If not, the procedure SHALL stop, and the result of this command SHALL indicate an error ('profileNotInDisabledState'). If the refreshFlag is not set, the eUICC SHALL:

•Check whether there is a proactive session ongoing (which the Device did not terminate). If so:

o the eUICC MAY terminate the “ES10b.ExecuteFallbackMechanism” function with
  error 'catBusy'.
o If the eUICC does not terminate the “ES10b.ExecuteFallbackMechanism”
  function with error 'catBusy', the eUICC SHALL internally terminate the
  proactive session and ignore any incoming TERMINAL RESPONSE from that
  proactive session.
•   Close all logical channels which still have an application of the currently Enabled
    Profile selected (which the Device did not close), without generating an error.
•   Reset the PIN status.
•   Disable the currently Enabled Profile.
•   Enable the Fallback Profile.
•   Reset any authorisation previously granted to use the Profile Rollback Mechanism
    (and any related data).
•   Implicitly select the MF on the basic logical channel.
•   Return 'ok' to the IPA.

If the refreshFlag is set:

•If there is a proactive session ongoing;

o The eUICC MAY terminate the “ES10b.ExecuteFallbackMechanism” function with
  error 'catBusy'.
o If the eUICC does not terminate the “ES10b.ExecuteFallbackMechanism” function
  with error 'catBusy', the eUICC SHALL internally terminate the proactive session
  and send the REFRESH command as the next proactive command. If a
TERMINAL RESPONSE is still outstanding, the REFRESH command SHALL only
be sent after reception of the TERMINAL RESPONSE.

•Otherwise, the eUICC SHALL:

o Mark the currently Enabled Profile as "to be disabled".
o Mark the target Fallback Profile as "to be enabled".
o Reset any authorisation previously granted to use the Profile Rollback Mechanism
  (and any related data).
o Return 'ok' to the IPA.
o Send the REFRESH command in "eUICC Profile State Change" mode (if
  supported by the IoT Device) or "UICC Reset" mode to the IoT Device according
  to ETSI TS 102 223 [5].
o Upon reception of the Terminal Response with result "command performed
  successfully" or upon reset of the eUICC, disable the currently Enabled Profile
  and enable the target Fallback Profile.
o Upon reception of the Terminal Response with result "temporary problem with
  executing command" or "permanent problem with executing command", the
  eUICC SHALL NOT disable the currently Enabled Profile nor Enable the targeted
  Fallback Profile. Subsequent actions are implementation specific.

The eUICC MAY start a new proactive UICC session only after a new TERMINAL PROFILE command is executed.

•   If the currently Enabled Profile was successfully disabled, the eUICC SHALL
    generate as many Notifications as configured in its metadata
    (notificationConfigurationInfo) in the format of
    OtherSignedNotification.
•   If the Fallback Profile is successfully enabled, the eUICC SHALL generate as many
    Notifications as configured in its metadata (notificationConfigurationInfo) in
    the format of OtherSignedNotification.

Command Data

The command data SHALL be coded as follows: -- ASN1START ExecuteFallbackMechanismRequest ::= [93] SEQUENCE { -- Tag ' BF5D' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP

Response Data

The response data SHALL be coded as follows: -- ASN1START ExecuteFallbackMechanismResponse ::= [93] SEQUENCE { -- Tag ' BF5D' executeFallbackMechanismResult [0] INTEGER {

       ok(0),
       profileNotInDisabledState(2),
       catBusy(5),
       fallbackNotAvailable(6), -- Fallback Attribute not set
       commandError(7),
       ecallActive(104),
       undefinedError(127)
   }
}
-- ASN1STOP

NOTE:It’s IoT Device implementation specific to decide when the IPA calls the ReturnFromFallback function.

5.9.21 Function (ES10b): ReturnFromFallback

Function Provider: ISD-R (IPA Services)

Function Caller: IPA

Description:

This function is OPTIONAL for the eUICC and MAY be used by the IPA to instruct the eUICC to return from the Fallback Profile. It disables the currently enabled Fallback Profile and enables the Profile that was previously enabled prior to enabling the Fallback Profile. If “ES10b.ExecuteFallbackMechanism” function is supported, this function SHALL also be supported.

This function SHALL be performed in an atomic way, meaning that in case of any error during the function execution, the command SHALL stop and SHALL leave the involved Profiles in their original states (prior to function execution).

Upon reception of this function, the ISD-R SHALL:

•check if the currently enabled Profile is the Fallback Profile. If not, the procedure SHALL stop, and the result of this command SHALL indicate an error ('fallbackNotAvailable (6)').

If the refreshFlag is not set, the eUICC SHALL:

•Check whether there is a proactive session ongoing (which the Device did not terminate). If so:

o the eUICC MAY terminate the “ES10b.ReturnFromFallback” function with error
  'catBusy'.
o If the eUICC does not terminate the “ES10b.ReturnFromFallback” function with
  error 'catBusy', the eUICC SHALL internally terminate the proactive session and
  ignore any incoming TERMINAL RESPONSE from that proactive session.
•     Close all logical channels which still have an application of the currently Enabled
      Fallback Profile selected (which the Device did not close), without generating an
      error.
•     Reset the PIN status.
•   Disable the currently enabled Fallback Profile.
•   Enable the Profile that was previously enabled (prior to enabling the Fallback Profile).
•   Implicitly select the MF on the basic logical channel.
•   Return 'ok' to the IPA.

If the refreshFlag is set:

•If there is a proactive session ongoing;

o The eUICC MAY terminate the “ES10b.ReturnFromFallback” function with error
  'catBusy'.
o If the eUICC does not terminate the “ES10b.ReturnFromFallback” function with
  error 'catBusy', the eUICC SHALL internally terminate the proactive session and
  send the REFRESH command as the next proactive command. If a TERMINAL
  RESPONSE is still outstanding, the REFRESH command SHALL only be sent
  after reception of the TERMINAL RESPONSE.

•Otherwise, the eUICC SHALL:

o Mark the currently enabled Fallback Profile as "to be disabled".
o Mark the previously enabled Profile as "to be enabled".
o Return 'ok' to the IPA.
o Send the REFRESH command in "eUICC Profile State Change" mode (if
  supported by the IoT Device) or "UICC Reset" mode to the IoT Device according
  to ETSI TS 102 223 [5].
o Upon reception of the Terminal Response with result "command performed
  successfully" or upon reset of the eUICC, disable the currently enabled Fallback
  Profile and enable the previously enabled Profile.
o Upon reception of the Terminal Response with result "temporary problem with
  executing command" or "permanent problem with executing command", the
  eUICC SHALL NOT disable the currently enabled Fallback Profile nor enable the
  previously enabled Profile. Subsequent actions are implementation specific.

The eUICC MAY start a new proactive UICC session only after a new TERMINAL PROFILE command is executed.

•   If the currently enabled Fallback Profile was successfully disabled, the eUICC SHALL
    generate as many Notifications as configured in its metadata
    (notificationConfigurationInfo) in the format of
    OtherSignedNotification.
•   If the previously enabled Profile is successfully enabled, the eUICC SHALL generate
    as many Notifications as configured in its metadata
    (notificationConfigurationInfo) in the format of
    OtherSignedNotification.

Command Data

The command data SHALL be coded as follows: -- ASN1START ReturnFromFallbackRequest ::= [94] SEQUENCE { -- Tag 'BF5E' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP

Response Data

The response data SHALL be coded as follows:
-- ASN1START
ReturnFromFallbackResponse ::= [94] SEQUENCE { -- Tag 'BF5E'
   returnFromFallbackResult [0] INTEGER {
      ok(0),
      catBusy(5),
      fallbackNotAvailable(6), -- Fallback Attribute not set
      commandError(7),
      undefinedError(127)
   }
}
-- ASN1STOP

5.9.22 Function (ES10b): EnableEmergencyProfile

Function Provider: eUICC

Description:

This function is OPTIONAL for eUICC and IPA, and MAY be used by the IPA to instruct the eUICC to enable the Emergency Profile with ecallIndication set to TRUE.

This function disables the currently Enabled Profile and enables the Emergency Profile. This function SHALL be performed in an atomic way, meaning that in case of any error during the function execution, the command SHALL stop and SHALL leave the involved Profiles in their original states (prior to function execution).

Upon enabling the Emergency Profile, the eUICC SHALL NOT generate any Notifications.

The Emergency Profile SHALL remain enabled until the IoT Device disables it again using the ES10b.DisableEmergencyProfile function, i.e. it remains enabled even after restart of the IoT Device.

Upon reception of this function, the eUICC SHALL:

•     check if the Emergency feature is supported. If not, the procedure SHALL stop, and
      the result of this command SHALL indicate an error ('ecallNotAvailable').
•     verify that the Emergency Profile (Profile with the ecallIndication set to TRUE)
      is available. If not, the procedure SHALL stop, and the result of this command SHALL
      indicate an error ('ecallNotAvailable').

•verify that the selected Emergency Profile is disabled. If not, the procedure SHALL stop, and the result of this command SHALL indicate an error ('profileNotInDisabledState').

If the refreshFlag is not set, the eUICC SHALL:

•Check whether there is a proactive session ongoing (which the Device did not terminate). If so:

o the eUICC MAY terminate the “ES10b.EnableEmergencyProfile” function with
  error 'catBusy'.
o If the eUICC does not terminate the “ES10b.EnableEmergencyProfile” function
  with error 'catBusy', the eUICC SHALL internally terminate the proactive session
  and ignore any incoming TERMINAL RESPONSE from that proactive session.
•   Close all logical channels which still have an application of the currently Enabled
    Profile selected (which the IoT Device did not close), without generating an error.
•   Reset the PIN status.
•   Disable the currently Enabled Profile.
•   Enable the Emergency Profile.
•   Reset any authorisation previously granted to use the Profile Rollback Mechanism
    (and any related data).
•   Implicitly select the MF on the basic logical channel.
•   Return 'ok' to the IPA.

If the refreshFlag is set:

•   If there is a proactive session ongoing;
    o The eUICC MAY terminate the “ES10b.EnableEmergencyProfile” function with
         error 'catBusy'.
    o If the eUICC does not terminate the “ES10b.EnableEmergencyProfile” function
         with error 'catBusy', the eUICC SHALL internally terminate the proactive session
         and send the REFRESH command as the next proactive command. If a
         TERMINAL RESPONSE is still outstanding, the REFRESH command SHALL only
         be sent after reception of the TERMINAL RESPONSE.
•   Otherwise, the eUICC SHALL:
    o Mark the currently Enabled Profile as "to be disabled".
    o Mark the target Emergency Profile as "to be enabled".
    o Return 'ok' to the IPA.
    o Send the REFRESH command in "eUICC Profile State Change" mode (if
         supported by the IoT Device) or "UICC Reset" mode to the IoT Device according
         to ETSI TS 102 223 [5].
    o Upon reception of the Terminal Response with result "command performed
         successfully" or upon reset of the eUICC, disable the currently Enabled Profile
         and enable the Emergency Profile.
    o Upon reception of the Terminal Response with result "temporary problem with
         executing command" or "permanent problem with executing command", the
eUICC SHALL NOT disable the currently Enabled Profile nor enable the
Emergency Profile. Subsequent actions are implementation specific.

The eUICC MAY start a new proactive UICC session only after a new TERMINAL PROFILE command is executed.

When the Emergency Profile is enabled, the eUICC SHALL reject an incoming EuiccPackageRequest with the appropriate error code as defined in section 2.11.2.1.

Command Data

The command data SHALL be coded as follows: -- ASN1START EnableEmergencyProfileRequest ::= [91] SEQUENCE { -- Tag 'BF5B' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP Response Data

The response data SHALL be coded as follows:
-- ASN1START
EnableEmergencyProfileResponse ::= [91] SEQUENCE { -- Tag 'BF5B'
   enableEmergencyProfileResult [0] INTEGER {
      ok(0),
      profileNotInDisabledState(2),
      catBusy(5),
      ecallNotAvailable(8), -- Emergency Profile does not exist
      undefinedError(127)
   }
}
-- ASN1STOP

5.9.23 Function (ES10b): DisableEmergencyProfile

Function Provider: eUICC

Description:

This function is OPTIONAL for eUICC and IPA, and MAY be used by the IPA to instruct the eUICC to disable the Emergency Profile. If “ES10b.EnableEmergencyProfile” function is supported, this function SHALL also be supported.

This function disables the currently enabled Emergency Profile and enables the Profile that was previously enabled prior to enabling the Emergency Profile. This function SHALL be performed in an atomic way, meaning that in case of any error during the function execution, the command SHALL stop and SHALL leave the involved Profiles in their original states (prior to function execution).

Upon reception of this function, the eUICC SHALL:

•   check if the Emergency feature is supported. If not, the procedure SHALL stop, and
    the result of this command SHALL indicate an error ('ecallNotAvailable').
•   verify that the Emergency Profile (Profile with the ecallIndication set to TRUE)
    is available. If not, the procedure SHALL stop, and the result of this command SHALL
    indicate an error ('ecallNotAvailable').
•   verify that the selected Emergency Profile is enabled. If not, the procedure SHALL
    stop, and the result of this command SHALL indicate an error
    ('profileNotInEnabledState').

If the refreshFlag is not set, the eUICC SHALL:

•Check whether there is a proactive session ongoing (which the IoT Device did not terminate). If so: o the eUICC MAY terminate the “ES10b.DisableEmergencyProfile” function with error 'catBusy'. o If the eUICC does not terminate the “ES10b.DisableEmergencyProfile” function with error 'catBusy', the eUICC SHALL internally terminate the proactive session and ignore any incoming TERMINAL RESPONSE from that proactive session. • Close all logical channels which still have an application of the currently Enabled Profile selected (which the IoT Device did not close), without generating an error. • Reset the PIN status. • Disable the Emergency Profile. • Enable the previously Enabled Profile. • Reset any authorisation previously granted to use the Profile Rollback Mechanism (and any related data). • Implicitly select the MF on the basic logical channel. • Return 'ok' to the IPA. If the refreshFlag is set:

•   If there is a proactive session ongoing;
    o The eUICC MAY terminate the “ES10b.EnableEmergencyProfile” function with
         error 'catBusy'.
    o If the eUICC does not terminate the “ES10b.EnableEmergencyProfile” function
         with error 'catBusy', the eUICC SHALL internally terminate the proactive session
         and send the REFRESH command as the next proactive command. If a
         TERMINAL RESPONSE is still outstanding, the REFRESH command SHALL only
         be sent after reception of the TERMINAL RESPONSE.
•   Otherwise, the eUICC SHALL:
    o Mark the Emergency Profile as "to be disabled".
    o Mark the previously Enabled Profile as "to be enabled".
    o Return 'ok' to the IPA.
    o Send the REFRESH command in "eUICC Profile State Change" mode (if
         supported by the IoT Device) or "UICC Reset" mode to the IoT Device according
         to ETSI TS 102 223 [5].
    o Upon reception of the Terminal Response with result "command performed
         successfully" or upon reset of the eUICC, disable the Emergency Profile and
         enable the previously Enabled Profile.
      o Upon reception of the Terminal Response with result "temporary problem with
         executing command" or "permanent problem with executing command", the
         eUICC SHALL NOT disable the Emergency Profile nor enable the previous
         Enabled Profile. Subsequent actions are implementation specific.
The eUICC MAY start a new proactive UICC session only after a new TERMINAL PROFILE
command is executed.
•     If the Emergency Profile is successfully disabled, the eUICC MAY generate as many
      Notifications as configured in its Profile Metadata
      (notificationConfigurationInfo) in the format of
      OtherSignedNotification.
•     If the previously enabled Profile is successfully enabled, the eUICC MAY generate as
      many Notifications as configured in its Profile Metadata
      (notificationConfigurationInfo) in the format of
      OtherSignedNotification.

Command Data -- ASN1START DisableEmergencyProfileRequest ::= [92] SEQUENCE { -- Tag 'BF5C' refreshFlag BOOLEAN -- indicating whether REFRESH is required } -- ASN1STOP

Response Data
-- ASN1START
DisableEmergencyProfileResponse ::= [92] SEQUENCE { -- Tag 'BF5C'
   disableEmergencyProfileResult [0] INTEGER {
      ok(0),
      profileNotInEnabledState(2),
      catBusy(5),
      undefinedError(127)
   }
}
-- ASN1STOP

5.9.24 Function (ES10b): GetConnectivityParameters

Related Procedures: eIM Package Retrieval, Indirect Profile Download

Function Provider Entity: eUICC (ISD-R)

Function Caller Entity: IPA

Description:

This function is used by the IPA to read the HTTP/CoAP Connectivity Parameters of the currently enabled Profile, if available. The Connectivity Parameters for HTTP protocol SHOULD be provided as part of an Profile Package as described in the TCA Profile Interoperability Technical Specification [29]. They can be updated by the operator using ES6 as described in section 3.13 (Connectivity Parameters Update by Operator) of SGP.02 [6].

If available, the Connectivity Parameters for HTTP protocol SHALL be returned in the httpParams field described below. The format of this field is identical to that described in Table 95 of SGP.02 [6].

If not available, the parametersNotAvailable error SHALL be returned.

Command Data

The command data SHALL be coded as follows: -- ASN1START GetConnectivityParametersRequest ::= [95] SEQUENCE { -- Tag 'BF5F' } -- ASN1STOP

Response Data

The response data object SHALL be coded as follows: -- ASN1START GetConnectivityParametersResponse ::= [95] CHOICE { -- Tag 'BF5F' connectivityParameters ConnectivityParameters, connectivityParametersError ConnectivityParametersError }

ConnectivityParameters ::= SEQUENCE { httpParams [1] OCTET STRING OPTIONAL -- Also used for CoAP }

ConnectivityParametersError ::= INTEGER { parametersNotAvailable(1), undefinedError(127) } -- ASN1STOP

5.9.25 Function (ES10b): SetDefaultDpAddress

Function Provider Entity: ISD-R (IPA Services)

Description:

NOTE:ES10a.SetDefaultDpAddress function defined in SGP.22 [4] has a tag number 'BF3F'.

This function is used to update the default SM-DP+ address.

ES10b.SetDefaulDpAddress SHALL only be used if immediate enable is not configured. In case it is configured and the eUICC receives an ES10b.SetDefaultDpAddress, the eUICC SHALL reject the command with error code “undefinedError”.

If the provided UTF8 string is not empty, it SHALL constitute the new default SM-DP+ address.

If the provided UTF8 string is empty, an existing default SM-DP+ address SHALL be removed.

Command Data

The command data SHALL be coded as follows: -- ASN1START SetDefaultDpAddressRequest ::= [101] SEQUENCE { -- Tag 'BF65' defaultDpAddress UTF8String -- Default SM-DP+ address as an FQDN } -- ASN1STOP

Response Data

The response data SHALL be coded as follows: -- ASN1START SetDefaultDpAddressResponse ::= [101] SEQUENCE { -- Tag 'BF65' setDefaultDpAddressResult INTEGER { ok (0), undefinedError (127)} } -- ASN1STOP

5.10 ES11 (IPA -- SM-DS)

ES11 is the interface to retrieve Event Records (see section 3.9.2.1) between:

•The IPA entity.

•The SM-DS.

The IPA SHALL communicate with the SM-DS secured by TLS in server authentication mode as described in section 2.6.4 of this document.

This interface is identical to the ES11 interface defined in section 5.8 of SGP.22 [4], where the IPA plays the role of LPA, except Function (ES11): AuthenticateClient where the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification.

5.11 ES11’ (eIM -- SM-DS)

ES11’ is the interface to retrieve Event Records (see section 3.9.2.2) between:

•The eIM entity.

•The SM-DS.

The eIM SHALL communicate with the SM-DS secured by TLS in server authentication mode as described in section 2.6.4 of this document.

5.11.1 Function (ES11’): InitiateAuthentication

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DS

Function Caller Entity: eIM

Description:

This function SHALL be called by the eIM to authenticate the SM-DS.

This function is identical to the “ES11.InitiateAuthentication” function defined in section 5.8.1 of SGP.22 [4], where the eIM plays the role of LPA. In addition, in case the IPA has sent all the necessary input data in the “ESipa.InitiateAuthentication” function request, the eIM SHALL forward it as an “ES11'.InitiateAuthentication” function request. Otherwise, the eIM SHALL complete the missing input data as described in “ES11.InitiateAuthentication” function as defined in section 5.8.1 of SGP.22 [4].

5.11.2 Function (ES11’): AuthenticateClient

Related Procedures: Profile Download and Installation

Function Provider Entity: SM-DS

Function Caller Entity: eIM

Description:

This function SHALL be called by the eIM to request the authentication of the eUICC by the SM-DS.

This function is identical to the “ES11.AuthenticateClient” function defined in section 5.8.2 of SGP.22 [4], where the eIM plays the role of LPA and the EUICCInfo2 in AuthenticateResponseOk is according to Section 5.9.2 of this specification.

5.12 ES12 (SM-DS -- SM-DP+)

The ES12 is used by the SM-DP+ to manage Event Registration (see section 3.9.1) and Event Deletion (see section 3.9.3). This interface is identical to the one defined in section 5.9 of SGP.22 [4].

5.13 ESep (eIM -- eUICC)

ESep is the interface between:

•The eIM entity.

•The eUICC.

The ESep interface is based on the eIM sending a signed EuiccPackageRequest to the eUICC containing PSMO(s) or eCO(s) and receiving a signed EuiccPackageResult in return from the eUICC containing the execution results. The ESep functions are the PSMOs and eCOs in the eUICC Package.

5.13.1 Function (ESep): Enable

Related Procedures: Profile State Management

Function Provider Entity: eUICC

Description:

This function enables an installed Profile in the eUICC. The input data is the enable structure defined in section 2.11.1.1.3 and the output is the enableResult structure defined in section 2.11.2.1. The function is further described in the Enable Profile procedure defined in section 3.4.1. In addition, the eUICC behaviour with refreshFlag set as defined in SGP.22 [4] section 5.7.16 applies.

5.13.2 Function (ESep): Disable

Related Procedures: Profile State Management

Function Provider Entity: eUICC

Description:

This function disables an enabled Profile in the eUICC. The input data is the disable structure defined in section 2.11.1.1.3 and the output is the disableResult structure defined in section 2.11.2.1. The function is further described in the Disable Profile procedure defined in section 3.4.2. In addition, the eUICC behaviour with refreshFlag set as defined in SGP.22 [4] section 5.7.17 applies.

5.13.3 Function (ESep): Delete

Related Procedures: Profile State Management

Function Provider Entity: eUICC

Description:

This function deletes an installed Profile in the eUICC. The input data is the delete structure defined in section 2.11.1.1.3 and the output is the deleteResult structure defined in section 2.11.2.1. The function is further described in the Delete Profile procedure defined in section 3.4.3. In addition, the eUICC behaviour as defined in SGP.22 [4] section 5.7.18 applies.

5.13.4 Function (ESep): ListProfileInfo

Related Procedures: Indirect Profile Download

Function Provider Entity: eUICC

Description:

This function allows the eIM to retrieve the list of Profile information for installed Profiles including their current state (Enabled/Disabled) and their associated Profile Metadata. The input data is the listProfileInfo structure defined in section 2.11.1.1.3 and the output is the listProfileInfoResult structure defined in section 2.11.2.1.

5.13.5 Function (ESep): GetRAT

Related Procedures: Indirect Profile Download

Function Provider Entity: eUICC

Description:

This function allows the eIM to retrieve the Rules Authorisation Table (RAT) from the eUICC. The input data is the getRAT structure defined in section 2.11.1.1.3 and the output is the getRATResult structure defined in section 2.11.2.1.

5.13.6 Function (ESep): ConfigureImmediateEnable

Related Procedures: Configure by eIM of Immediate Profile Enabling

Function Provider Entity: eUICC

Description:

This function configures the immediate enabling of a Profile in the eUICC. The input data is the configureImmediateEnable structure defined in section 2.11.1.1.3 and the output is the configureImmediateEnableResult structure defined in section 2.11.2.1. The function is further described in the Configuration by eIM of Immediate Profile Enabling procedure defined in section 3.4.4.

5.13.7 Function (ESep): AddEim

Related Procedures: Addition of eIM Configuration Data

Function Provider Entity: eUICC

Description:

This function adds an Associated eIM to the eUICC by providing its eIM Configuration Data including the eimID to the eUICC. The input data is the addEim structure defined in section 2.11.1.1.2 and the output is the addEimResult structure defined in section 2.11.2.1. The function is further described in the Addition of eIM Configuration Data procedure defined in section 3.5.1.1.

5.13.8 Function (ESep): UpdateEim

Related Procedures: Update of eIM Configuration Data

Function Provider Entity: eUICC

Description:

This function updates eIM Configuration Data, i.e., the public key or Certificate and the related anti-replay counter value of an Associated eIM with a given eimID within the eUICC while keeping the same eimID. The input data is the updateEim structure defined in section 2.11.1.1.2 and the output is the updateEimResult structure defined in section 2.11.2.1. The

function is further described in the Update of eIM Configuration Data procedure defined in section 3.5.1.3.

5.13.9 Function (ESep): DeleteEim

Related Procedures: Deletion of eIM Configuration Data

Function Provider Entity: eUICC

Description:

This function deletes an Associated eIM identified by its eimID from the eUICC. If the successfully deleted Associated eIM was the last available Associated eIM, the eUICC SHALL allow ES10b.AddInitialEim again. The input data is the deleteEim structure defined in section 2.11.1.1.2 and the output is the deleteEimResult structure defined in section 2.11.2.1. The function is further described in the Deletion of eIM Configuration Data procedure defined in section 3.5.1.2.

5.13.10 Function (ESep): ListEim

Related Procedures: Request for a list of Associated eIMs

Function Provider Entity: eUICC

Description:

This function requests the eUICC to provide a list of all currently configured Associated eIMs to the eIM. The input data is the listEim structure defined in section 2.11.1.1.2 and the output is the listEimResult structure defined in section 2.11.2.1. The function is further described in the Request for a list of Associated eIMs procedure defined in section 3.5.1.4.

5.13.11 Function (ESep): SetDefaultDpAddress

Function Provider Entity: eUICC

Description:

This function allows the eIM to update the Default SM-DP+ address configured within the eUICC. The input data is the setDefaultDpAddress structure defined in section 2.11.1.1.3 and the output is the setDefaultDpAddressResult structure defined in section 2.11.2.1.

5.14 ESipa (eIM -- IPA)

This ESipa interface is used between:

•The IPA entity

•The eIM entity.

This section defines the different functions used through the ESipa interface.

5.14.1 Function (ESipa): InitiateAuthentication

Related Procedures: Profile Download and Installation

Function Provider Entity: eIM

Function Caller Entity: IPA

Description:

This function requests the SM-DP+/SM-DS authentication via the eIM. This follows the ES10b.GetEUICCChallenge by the IPA, where the IPA retrieves the relevant information from the eUICC and provides it to the eIM. The eIM SHALL send this information to the SM- DP+/SM-DS to initiate mutual authentication between the eUICC and the SM-DP+/SM-DS.

On reception of this function call, the eIM SHALL call the ES9+'.InitiateAuthentication function
/ ES11’.InitiateAuthentication based on the received input data. The eIM SHALL identify any
missing input data before calling               the ES9+’.InitiateAuthentication       function/
ES11’.InitiateAuthentication.

The input parameters of this function are identical to those of the “ES9+.InitiateAuthentication” / “ES11.InitiateAuthentication” defined in section 5.6.1/5.8.1 of SGP.22 [4], except the following change in MOC column of the input data table where the euiccInfo1 and smdpAddress are OPTIONAL. An IPA with IPA Capability minimizeEsipaBytes SHOULD NOT send euiccInfo1 and smdpAddress in order to reduce the number of transmitted bytes. In case an Activation Code is used, an IPA with IPA Capability eimDownloadDataHandling SHALL not send smdpAddress. The IPA SHALL include the same eimTransactionId in case it has been sent by the eIM using ProfileDownloadTriggerRequest.

Additional Input Data:

Input data name           Description                                    Type         No.   MOC
                          euiccChallenge generated by the eUICC. IPA
                          can retrieve the euiccChallenge from the eUICC
euiccChallenge                                                           Binary[16]    1    M
                          by calling "ES10b.GetEUICCChallenge" (section
                          5.9.3).
                          euiccInfo1 of the eUICC. IPA can retrieve the
euiccInfo1                euiccInfo1 by calling "ES10b.GetEUICCInfo" Binary(1)         1    O
                          (section 5.9.2).
smdpAddress               The SM-DP+/SM-DS Address as known and                             O
                                                                FQDN                   1
                          provided by the IPA.
eimTransactionId          The transaction ID received from the eIM in Binary[1-             C
                                                                                       1
                          ProfileDownloadTriggerRequest               16]
       NOTE1: euiccInfo1 SHALL be provided as an encoded EuiccInfo1 data object.

Table 8 InitiateAuthentication Additional Input Data

Upon receiving the ES9+’.InitiateAuthentication / ES11’.InitiateAuthentication response, the eIM SHALL perform the following:

•If the smdpAddress provided as input to ES9+’.InitiateAuthentication / ES11’.InitiateAuthentication did not come from IPA (not present in ESipa.InitiateAuthentication e.g., due to IPA has capability

eimDownloadDataHandling), the eIM SHALL verify that the serverAddress in
serverSigned1 returned by the SM-DP+/SM-DS matches the smdpAddress that the
eIM provided as input in ES9+'.InitiateAuthentication. If not, the procedure SHALL
stop and return an error.

•If the Activation Code contains the SM-DP+ OID and is available to the eIM (e.g., due to IPA has capability eimDownloadDataHandling), the eIM SHALL check that the SM-DP+ OID from the Activation Code matches the SM-DP+ OID of the SM-DP+ Certificate (serverCertificate). If not, the procedure SHALL stop and return an error.

•If IPA does not generate ctxParams1 (see IPA capability eimCtxParams1Generation), the eIM SHALL generate ctxParams1 based on matchingId DeviceInfo. DeviceInfo MAY be common for several IoT Devices and MAY have been retrieved from one IoT Device and re-used for other IoT Devices.

The eIM SHALL prepare the ESipa.InitiateAuthentication response. The output parameters of this function are identical to those of ES9+.InitiateAuthentication / ES11’.InitiateAuthentication defined in section 5.6.1/5.8.1 of SGP.22 [4] with the following modifications:

•transactionId is conditional since it is also part of serverSigned1 and SHALL NOT be sent by the eIM to an IPA with IPA Capability minimizeEsipaBytes (i.e., IPA is capable of extracting transactionId from serverSigned1),

•euiccCiPKIdentifierToBeUsed SHALL be sent in truncated form (instead of the full CI Public Key Identifier) to an IPA with IPA Capability minimizeEsipaBytes to minimize the number of transmitted bytes.

•ctxParams1 SHALL be provided to IPA if IPA is not capable of generating it (IPA capability eimCtxParams1Generation),

•matchingId SHALL be provided to the IPA if IPA generates ctxParams1 and the matchingId is available to the eIM but not available to the IPA.

Additional Output Data:
Output data name               Description                               Type           No.   MOC
                               Transaction ID as generated by the
transactionId                  SM-DP+/SM-DS (section 3.1.1.4 of          Binary[1-16]     1   C
                               SGP.22 [4]).
serverSigned1                  The data object signed by the SM-DP+. Binary(1)            1   M
serverSignature1               SM-DP+/SM-DS signature                    Binary(1)        1   M
euiccCiPKIdentifierToBeUsed CI Public Key Identifier to be used by                            M
                                                                   Binary(1,2)            1
                            the eUICC for signature.
serverCertificate              SM-DP+/SM-DS                Certificate                        M
                               (CERT.DPauth.ECDSA/                       Binary(1)        1
                               CERT.DSauth.ECDSA)
matchingId                     MatchingID/ EventID as defined in         UTF8String       1   C(3)
                               SGP.22 [4] identifying a specific
management order at the SM-
DP+/SM-DS.
ctxParams1                      Data structure used in Common Mutual Binary(1)              1    C(3)
                                Authentication.
NOTE 1: serverSigned1, serverSignature1, euiccCiPKIdentifierToBeUsed, serverCertificate, and
ctxParams1 are data objects defined in section 5.7.13 (function "ES10b.AuthenticateServer") of
SGP.22 [4]. They SHALL be returned as encoded data objects including the tags defined for them in
the AuthenticateServerRequest data object.
NOTE 2: euiccCiPKIdentifierToBeUsed contains either the full CI Public Key Identifier or a truncated
version of the CI Public Key Identifier where only enough leading bytes of the CI Public Key Identifier
are provided for IPA to be able to uniquely locate and extract the chosen CI Public Key Identifier from
the euiccCiPKIdListForSigning of eUICCInfo1. If the euiccCiPKIdListForSigning only contains one CI
Public Key Identifier, the euiccCiPKIdentifierToBeUsed encoded data object in truncated form
indicates a zero length CI Public Key Identifier. The euiccCiPKIdentifierToBeUsed SHALL be sent
in truncated form to an IPA with IPA Capability minimizeEsipaBytes. Otherwise, the full CI Public Key
Identifier SHALL be used.
NOTE 3: matchingId and ctxParams1 are conditional since either the IPA or the eIM generates the
ctxParams1. If the IPA generates ctxParams1 and the matchingId is available to the eIM but not
available to the IPA (i.e. IPA sets in IpaCapabilities the value of eimDownloadDataHandling to 1 and
the value of eimCtxParams1Generation to 0), the eIM SHALL provide the Matching ID to IPA.

Table 9 InitiateAuthentication Additional Output Data

The error codes returned by ESipa.InitiateAuthentication SHALL be the same as those of ES9+’.InitiateAuthentication / ES11’.InitiateAuthentication with the following additions:

•smdpAddressMismatch – indicates an error when matching SM-DP+/SM-DS Address sent in ES9+’.InitiateAuthentication with / ES11’.InitiateAuthentication SM- DP+/SM-DS Address received from the SM-DP+/SM-DS,

•smdpOidMismatch – indicates an error when matching SM-DP+ OID from AC with SM-DP+ OID from SM-DP+ Certificate.

•invalidEimTransactionId – indicates that the eimTransactionID included in the Esipa.InitiateAuthentication is invalid (e.g. absent or related to another transaction).

5.14.2 Function: (ESipa) GetBoundProfilePackage

Related Procedures: Profile Download and Installation

Function Provider Entity: eIM

Description:

This function requests the delivery and the binding of a Profile Package for the eUICC.

This function is correlated to a previous normal execution of an Esipa.AuthenticateClient function through a TransactionID delivered by the SM-DP+.

On reception of this function call, the eIM SHALL call the ES9+’.GetBoundProfilePackage function based on the received input data. The input parameters of this function are identical

to the those of ES9+.GetBoundProfilePackage defined in section 5.6.2 of SGP.22 [4]. However, the prepareDownloadResponse is extended according to the below ASN.1 structure where a compactDownloadResponseOk is added. An IPA with IPA Capability minimizeEsipaBytes SHOULD re-encode a prepareDownloadResponse with downloadResponseOk received from eUICC into a prepareDownloadResponse with compactDownloadResponseOk in order to reduce the number of bytes to transmit to the eIM. Before calling the ES9+’.GetBoundProfilePackage function, an eIM that receives a prepareDownloadResponse from an IPA with IPA Capability minimizeEsipaBytes SHALL restore the prepareDownloadResponse prepared by the eUICC based on the received prepareDownloadResponse and data already available to the eIM (smdpSigned2 and hashCc).

Additional Input Data:
Input data name                Description                            Type             No. MOC
                               Transaction ID as generated by the
transactionId                  SM-DP+ (section 3.1.1.4 of SGP.22      Binary[1-16]     1     M
                               [4]).
                               PrepareDownloadResponse data object
                               defined in section 5.7.5 of SGP.22
                               extended                          with
                               compactDownloadResponseOk        (see
prepareDownloadResponse        structure  below).   IPA    retrieves Binary(1)         1     M
                               prepareDownloadResponse from the
                               eUICC            by            calling
                               “ES10b.PrepareDownload”      (section
                               5.9.7).
NOTE    1:    prepareDownloadResponse         SHALL      be    provided   as      an       encoded
PrepareDownloadResponse data object.
                 Table 10 GetBoundProfilePackage Additional Input Data
-- ASN1START
PrepareDownloadResponse ::= [33] CHOICE { -- Tag 'BF21'
   downloadResponseOk PrepareDownloadResponseOk,
   downloadResponseError PrepareDownloadResponseError,
   compactDownloadResponseOk CompactPrepareDownloadResponseOk
}
CompactPrepareDownloadResponseOk ::= SEQUENCE {
   compactEuiccSigned2 CompactEuiccSigned2, -- Compact version of EuiccSigned2
   euiccSignature2 [APPLICATION 55] OCTET STRING -- tag '5F37' signature on
EuiccSigned2
}
CompactEuiccSigned2 ::= SEQUENCE {
   euiccOtpk [APPLICATION 73] OCTET STRING OPTIONAL, -- otPK.EUICC.ECKA, tag '5F49'
euiccOtpk is always present except if bppEuiccOtpk was chosen by the eUICC
   hashCc Octet32 OPTIONAL -- Hash of confirmation code, if not received from eIM
}
-- ASN1STOP
Upon receiving the ES9+’.GetBoundProfilePackage response, the eIM SHALL perform the
following:

•If the eIM verified the Profile Metadata in Esipa.AuthenticateClient (due to IPA Capability eimProfileMetadataVerification), the eIM SHOULD parse the boundProfilePackage received from SM-DP+, extract the Profile Metadata (encoded

in the StoreMetadataRequest field), and check that the Profile Metadata has not
changed. If it has changed, the eIM SHALL return an error code to IPA indicating
Metadata mismatch and terminate the procedure. The error code SHALL trigger the
IPA to cancel the on-going RSP session with SM-DP+ using Esipa.CancelSession.
The cancel session reason code to be used by IPA when calling the
Esipa.CancelSession SHALL be given by the error code, i.e., Metadata mismatch.

The eIM SHALL prepare the Esipa.GetBoundProfilePackage response. The output parameters of this function are identical to the those of ES9+.GetBoundProfilePackage defined in section 5.6.2 of SGP.22 [4] except for that transactionId is conditional. The transactionId is also part of boundProfilePackage. An eIM SHALL NOT send the transactionId to an IPA with IPA Capability minimizeEsipaBytes (i.e., IPA is capable of extracting transactionId from boundProfilePackage). Otherwise, the eIM SHALL send the transactionId.

Additional Output Data:
Output data name      Description                                  Type           No.   MOC
transactionId            Transaction ID as generated by the SM-DP+ Binary[1-16]    1    C
                         (section 3.1.1.4 of SGP.22 [4]).
                         Bound Profile Package data object to be
                         transferred   to  the   eUICC      using
boundProfilePackage                                               Binary(1)        1    M
                         "ES10b.LoadBoundProfilePackage" (section
                         5.9.8).
NOTE 1: boundProfilePackage SHALL be provided as an encoded BoundProfilePackage data object.

Table 11 GetBoundProfilePackage Additional Output Data

The error codes returned by ESipa.GetBoundProfilePackage SHALL be the same as those of ES9+’.GetBoundProfilePackage with the following additions:

•metadataMismatch – indicates an error when matching Profile Metadata received in the ES9+’.AuthenticateClient and Profile Metadata in the BPP.

5.14.3 Function: (ESipa) AuthenticateClient

Related Procedures: Profile Download and Installation

Function Provider Entity: eIM

Function Caller Entity : IPA

Description:

This function SHALL be called by the IPA to request the authentication of the eUICC by the SM-DP+/SM-DS.

This function is correlated to a previous normal execution of an ESipa.InitiateAuthentication through a TransactionID delivered by the SM-DP+/SM-DS.

On reception of this function call, the eIM SHALL call the “ES9+’.AuthenticateClient” / ”ES11’.AuthenticateClient” function based on the received input data. The input parameters

of this function are identical to the those of the “ES9+.AuthenticateClient” / “ES11.AuthenticateClient” defined in section 5.6.3/5.8.2 of SGP.22 [4], with the following exceptions:

•   authenticateServerResponse is extended according to the below ASN.1
    structure where a compactAuthenticateResponseOk is added.
      o An IPA with IPA Capability minimizeEsipaBytes SHOULD re-encode an
          authenticateResponseOk contained in authenticateServerResponse
          from eUICC into compactAuthenticateResponseOk.
      o An eIM that receives an compactAuthenticateResponseOk in
          authenticateServerResponse          SHALL         restore          the
          authenticateResponseOk by using the data already available to the eIM
          (serverSigned1, eUICCInfo2, ctxParams1, euiccCertificate, and
          eumCertificate) before calling the      ES9+'.AuthenticateClient or
          ES11'.AuthenticateClient function.

NOTE:the use of this compactAuthenticateResponseOk reduces the number of transmitted bytes over ESipa by omitting eUICC Certificate and/or EUM Certificate, and sending only non-static parts of euiccInfo2.

Additional Input Data:
Input data name                Description                            Type            No. MOC
                               Transaction ID as generated by the
transactionId                  SM-DP+/SM-DS (section 3.1.1.4 of       Binary[1-16]    1     M
                               SGP.22 [4]).
                               AuthenticateServerResponse          data
                               object defined in section 5.7.13 of
                               SGP.22 with EUICCInfo2 according to
                               Section 5.9.2 of this specification and
                               extended                             with
authenticateServerResponse     compactAuthenticateResponseOk (see Binary(1)           1     M
                               structure   below).    IPA     retrieves
                               authenticateServerResponse from the
                               eUICC             by              calling
                               "ES10b.AuthenticateServer"      (section
                               5.9.6).
NOTE      1:   authenticateServerResponse      SHALL     be     provided   as    an       encoded
AuthenticateServerResponse data object.
                    Table 12 AuthenticateClient Additional Input Data
-- ASN1START
EuiccSigned1 ::= SEQUENCE {
   transactionId [0] TransactionId,
   serverAddress [3] UTF8String,
   serverChallenge [4] Octet16,   -- The RSP Server Challenge
   euiccInfo2 [34] EUICCInfo2,
   ctxParams1 CtxParams1
}
AuthenticateResponseOk ::= SEQUENCE {
   euiccSigned1 EuiccSigned1,            -- Signed information
   euiccSignature1 [APPLICATION 55] OCTET STRING,     --EUICC_Sign1, tag 5F37
   euiccCertificate Certificate, -- eUICC Certificate (CERT.EUICC.ECDSA) signed by
the EUM
   eumCertificate Certificate     -- EUM Certificate (CERT.EUM.ECDSA) signed by the
requested CI
}
AuthenticateServerResponse ::= [56] CHOICE { -- Tag 'BF38'
   authenticateResponseOk AuthenticateResponseOk,
   authenticateResponseError AuthenticateResponseError,
   compactAuthenticateResponseOk CompactAuthenticateResponseOk
}
CompactAuthenticateResponseOk ::= SEQUENCE {
   signedData CHOICE {
      euiccSigned1 EuiccSigned1,
      compactEuiccSigned1 [0] CompactEuiccSigned1 -- Compact version of EuiccSigned1
   },
   euiccSignature1 [APPLICATION 55] OCTET STRING, -- tag 5F37 signature on
EuiccSigned1
   euiccCertificate [1] Certificate OPTIONAL, -- eUICC Certificate (CERT.EUICC.ECDSA)
   eumCertificate [2] Certificate OPTIONAL -- EUM Certificate (CERT.EUM.ECDSA)
}
CompactEuiccSigned1 ::= SEQUENCE {
   extCardResource [4] OCTET STRING, -- Extended Card Resource Information according
to ETSI TS 102 226 extracted from euiccInfo2,
   ctxParams1 [2] CtxParams1 OPTIONAL -- ctxParams1 may be left out by IPA if eIM
ctxParams1 was received from the eIM
}
-- ASN1STOP
Upon receiving the ES9+’.AuthenticateClient response, the eIM SHALL perform the
following:

•If the IPA is not capable of verifying the Profile Metadata (see IPA Capability eimProfileMetadataVerification), the eIM SHALL verify the Profile Metadata according to steps 7a, b, c and 8 of section 3.1.3 (Profile Download and Installation) of SGP.22 [4]. For this verification, the eIM SHALL use Rules Authorisation Table and information on installed Profiles available to the eIM, e.g., obtained prior to the start of this procedure using the PSMOs getRAT and listProfileInfo. If the verification fails, the eIM SHALL return an error code to IPA and terminate the procedure. The error code SHALL trigger IPA to cancel the on-going RSP session with SM-DP+ using ESipa.CancelSession. The cancel session reason (e.g., PPR not allowed) to be used by IPA when calling the ESipa.CancelSession is given by the error code.

Upon receiving the ES11’.AuthenticateClient response, the eIM SHALL perform the
following:
     • Extract Event entries from the ES11’.AuthenticateClient response. Optionally,
        prepare and provide a ProfileDownloadTriggerRequest as part of
        ESipa.AuthenticateClient response to trigger the IPA to initiate download of a new
        Profile where information obtained from the Event entries are leveraged.

The eIM SHALL prepare the ESipa.AuthenticateClient response. The output parameters of this function are identical to the those of ES9+.AuthenticateClient / ES11.AuthenticateClient defined in section 5.6.3 / 5.8.2 of SGP.22 [4] , with the following exceptions:

•If smdpSign2 is provided, transactionId is optional. The eIM SHALL NOT send the transactionId to an IPA with IPA capability minimizeEsipaBytes,

•The eIM SHALL NOT send profileMetadata (from ES9+’.AuthenticateClient) to an IPA that does not indicate IPA Capability eimProfileMetadataVerification,

•hashCc (Hash of the Confirmation Code) from ES9+’.AuthenticateClient MAY be provided if a confirmation code is requested by the SM-DP+ and the confirmation code is available to the eIM,

•eventEntries from ES11’.AuthenticateClient are not forwarded to the IPA,

•a ProfileDownloadTriggerRequest data object MAY be provided in case the ESipa.AuthenticateClient originates from ES11’.AuthenticateClient.

Additional Output Data:
Output data name      Description                                         Type              No.   MOC
transactionId            Transaction ID as generated by the SM-DP+ Binary[1-16]               1   C
                         (section 3.1.1.4 of SGP.22 [4]).
                         Profile Metadata to check against eUICC
profileMetadata                                                  Binary(1)                    1   C
                         settings.
smdpSigned2              The data to be signed by the SM-DP+.             Binary(1)           1   C
                                                                                   (1)
smdpSignature2           SM-DP+ signature                                 Binary              1   C
smdpCertificate          SM-DP+ Certificate (CERT.DPpb.ECDSA)             Binary(1)           1   C
hashCc                   Hash of the confirmation code if confirmation                            O
                                                                       Binary(1)              1
                         code is requested and available to eIM
profileDownloadTrigger   Profile download trigger (see section 2.11.2.3                           O
                                                                          Binary              1
                         ProfileDownloadTriggerRequest)
NOTE 1: profileMetadata is the data object StoreMetadataRequest defined in section 5.5.3 (function
"ES8+.StoreMetadata"); smdpSigned2, smdpSignature2 and smdpCertificate are data objects
defined in section 5.7.5 (function "ES10b.PrepareDownload") of SGP.22 [4]. They SHALL be returned
as    encoded       data    objects    including  the   tags    defined     for  them    in    the
StoreMetadataRequest/PrepareDownloadRequest data object.

Table 13 AuthenticateClient Additional Output Data

The error codes returned by ESipa.AuthenticateClient SHALL be the same as those of ES9+’.AuthenticateClient with the following additions:

•pprNotAllowed – indicates PPRs in Profile Metadata are not allowed by the Rules Authorisation Table.

5.14.4 Function (ESipa): TransferEimPackage

Related Procedures: eIM Package injection

Function Provider Entity: IPA

Description:

This function is used by the eIM to transfer single eIM Package to the IPA.

On reception of the function call:

•In case the eIM Package contains an eUICC Package (EuiccPackageRequest), the IPA SHALL: o Call the "ES10b.LoadEuiccPackage" function of the ISD-R with its relevant input data,

o   collect the eUICC Package execution result from the eUICC to notify the eIM
    about the result of the operation,
o   and in case the IPA detects that the eIM cannot be notified about the result of
    the eIM Package execution then the IPA SHOULD call the
    "ES10b.ProfileRollback" function (see section 5.9.16) of the ISD-R as defined
    in section 3.3.1. The response to the eIM Package execution SHALL be then
    collected again after the Rollback operation.

NOTE:In case the IPA detects that the eIM cannot be notified about the result, the IPA can retry notifying the eIM at a later stage prior to calling the function “ES10b.ProfileRollback”.

o   If the IPA sends Notifications together with the eUICC Package Result in the
    eIM Package Result and if the eUICC Package contains PSMO(s): retrieve
    pending Notifications by calling ES10b.RetrieveNotificationsList and, if a non-
    empty list of pending Notifications, include the list of pending Notifications
    (PendingNotificationList as defined in section 2.11.2.2) after the
    signed eUICC Package Result in the eIM Package. In case of an IPA with IPA
    Capability minimizeEsipaBytes, the IPA SHOULD include each
    Notification in the list in compact format as described in section 5.14.7.

•In case the eIM Package contains a request for IPA and/or eUICC data (IpaEuiccDataRequest) the IPA SHALL collect the requested data and return the IpaEuiccDataResponse structure.

•   In case the eIM Package contains a Profile download                      trigger   request
    (ProfileDownloadTriggerRequest), the IPA SHALL:
o   Parse ProfileDownloadTriggerRequest to obtain any necessary data
    needed for the Profile download (e.g., an Activation Code).

▪If the ProfileDownloadTriggerRequest indicates direct Profile download, the IPA SHALL return the eimPackageReceived structure.

▪If the ProfileDownloadTriggerRequest indicates indirect Profile download, the IPA MAY return the eimPackageReceived structure.

NOTE:After sending ProfileDownloadTriggerRequest indicating indirect Profile download to the IPA, the eIM expects either eimPackageReceived structure followed by the ESipa.InitiateAuthentication function call or directly the ESipa.InitiateAuthentication function call. In the latter case successful reception of the ProfileDownloadTriggerRequest is implicit.

o   Proceed with the suitable Profile download and installation procedure as
    described in section 3.2.
•   In case the eIM Package contains the EimAcknowledgements structure with
    one or more sequence numbers of Notifications and/or eUICC Package
    Results, the IPA SHALL:
        o   Return the eimPackageReceived structure.
           o   For each sequence number, call the
               ES10b.RemoveNotificationFromList function where the eUICC deletes
               the Notification/eUICC Package Result identified by SequenceNumber
               from its memory.
   This function SHALL return one of the following:
          o A 'Function execution status' with 'Executed-Success' indicating that the eIM
               Package has been successfully executed and an eIM Package Result is
               generated.
          o A 'Function execution status' indicating 'Failed' with a status code as defined
               in section 5.2.6 or a specific status code as defined in the following table.
Additional input data:
Input data name                     Description                Type       No.         MOC
EuiccPackageRequest                 The eUICC Package          Binary     1           C(1)
                                    Request
IpaEuiccDataRequest                 The request for IPA        Binary     1           C(1)
                                    and/or eUICC data
ProfileDownloadTriggerRequest       The request for IPA to     Binary     1           C(1)
                                    trigger profile download
EimAcknowledgements                 Sequence number(s)         Binary     1           C(1)
                                    of Notifications and/or
                                    eUICC Package
                                    Results to be
                                    acknowledged

NOTE 1:The eIM Package SHALL either contain an EuiccPackageRequest data object, an IpaEuiccDataRequest data object, ProfileDownloadTriggerRequest data object, or an EimAcknowledgements data object.

Table 14: TransferEimPackage Additional Input Data

Additional Output data:

Output data name                      Description              Type       No.         MOC
EuiccPackageResult                    The result of eUICC      Binary     1           C(1)
                                      Package processing
IpaEuiccDataResponse                  The response              Binary        1           C(1)
                                      containing requested
                                      IPA and/or eUICC
                                      data
PendingNotificationList               List of pending           Binary        1           C(1,2)
                                      Notifications

NOTE 1:The eIM Package Result MAY contain either an EuiccPackageResult data object, an EuiccPackageResult data object concatenated with a PendingNotificationList data object, or an IpaEuiccDataResponse data object, or a simple acknowledgement that the eIM Package was successfully received (eimPackageReceived). NOTE 2: The PendingNotificationList data object, if included, SHALL be sent together with an EuiccPackageResult in the same eIM Package Result.

Table 15 TransferEimPackage Additional Output Data

5.14.5 Function (ESipa): GetEimPackage

Related Procedures: eIM Package retrieval

Function Provider Entity: eIM

Description:

This function is used by the IPA to retrieve an eIM Package.

The IPA provides the EID as an input to the function call.

The IPA MAY notify the eIM that one or several changes occurred in the eUICC (e.g. list of Profiles, Profiles states, …). In that case, the eIM SHOULD update its information about the eUICC.

The IPA MAY include the identity of the last PLMN the IoT Device registered to, in order for the eIM to detect a roaming situation.

On reception of the function call the eIM SHALL:

•Check if there is any eIM Package available for the eUICC identified by the EID. o If so, the eIM SHALL return a single eIM Package. If multiple eIM Packages are pending for the eUICC, it is eIM implementation-specific to select one of the pending eIM Packages. o Otherwise, the eIM SHALL return a status code "EID – Unavailable".

NOTE:In case the IPA detects that the eIM cannot be notified about the result, the IPA can retry notifying the eIM at a later stage prior to calling the function “ES10b.ProfileRollback”.

The eIM MAY perform additional operations, which are out of scope of this specification.

This function SHALL return one of the following:

•     A 'Function execution status' with 'Executed-Success' indicating that an eIM Package
      has been successfully identified.
•     A 'Function execution status' indicating 'Failed' with a status code as defined in section
      5.2.6 or a specific status code as defined in the following table.
Additional input data:
Input data name       Description                       Type              No.              MOC
Eid                   The EID of the eUICC for          EID               1                M
                      which the eIM Package
                      SHALL be retrieved
NotifyStateChange     Notification to the eIM that it   (empty)           1                O
                      SHOULD update its
                      information about the eUICC
                      (e.g. list of Profiles, Profile
                      states...)
stateChangeCause      Provide the cause of the          Integer           1                C(1)
                      notified state change(s)
RPLMN                 Identifier of the last            Binary            1                O
                      Registered PLMN (RPLMN),
                      as defined in 3GPP TS
                      23.122 [19] and coded as
                      defined in 3GPP TS 24.008
                      [22]

NOTE 1:mandatory if NotifyStateChange is present.

Table 16 GetEimPackage Additional Input Data

Additional output data:

Output data name                    Description                  Type           No.         MOC
EuiccPackageRequest                 The eUICC Package            Binary         1           C(1)
                                    Request
IpaEuiccDataRequest                 The request for IPA          Binary         1           C(1)
                                    and/or eUICC data
ProfileDownloadTriggerRequest       The request for IPA to       Binary         1           C(1)
                                    trigger profile download

NOTE 1:Either one and only one of EuiccPackageRequest, IpaEuiccDataRequest or ProfileDownloadTriggerRequest can be present.

Table 17 GetEimPackage Additional Output Data

Specific Status Codes

Subject                 Reason
           Subject                Reason            Description
Code                    code
8.1.1      EID          3.7       Unavailable       No pending eIM Package for the EID.
                                                    EID parameter is invalid.
8.1.1      EID          2.1       Invalid
                                                    See EID format defined in [6] section 2.2.2
                                  Mandatory
8.1.1      EID          2.2                         Mandatory EID parameter is missing.
                                  Element Missing
8.1.1      EID          3.9       Unknown           No eUICC found with specified EID.

Table 18 GetEimPackage Specific Status Codes

5.14.6 Function (ESipa): ProvideEimPackageResult

Related Procedures: eIM Package Retrieval

Function Provider Entity: eIM

Description:

This function is used by the IPA to deliver an eIM Package Result optionally including one or more Notifications to the eIM in the same function call.

On reception of the function call the eIM SHALL:

•Process the eIM Package Result. For that, the eIM SHALL: o If the eIM Package Result contains EuiccPackageResult (possibly within ePRAndNotifications data object): ▪ Verify the eUICC signature using PK.EUICC.ECDSA of the eUICC. If the signature is invalid, the eIM SHALL discard the input. ▪ Check if the sequence number of the EuiccPackageResult is greater than the expected sequence number of the eUICC. If not, the eIM SHALL discard the input. ▪ Manage the eIM Packages pending for the eUICC. ▪ Update the expected sequence number of the eUICC to the received sequence number. o If the eIM Package Result contains IpaEuiccDataResponse: ▪ Store the received IPA and/or eUICC information for future use. o If the eIM Package Result contains a notificationList data object within ePRAndNotifications: ▪ If the notificationList contains compact format of Notification(s), restore the Notification(s) in notificationList by using the data already available to the eIM. ▪ Forward the (restored) Notifications to the corresponding Notification Receiver(s). o If the eIM Package Result contains profileDownloadTriggerResult or eimPackageError: ▪ Manage the eIM Packages pending for the eUICC.

•Return the sequence numbers of the eUICC Package Result and optionally Notifications that were processed (including discarded results) and/or forwarded above.

The eIM MAY perform additional operations, which are out of scope of this specification.

This function SHALL return one of the following:
   •   A 'Function execution status' with 'Executed-Success' indicating that the eIM
       Package Result has been successfully delivered.
   •   A 'Function execution status' indicating 'Failed' with a status code as defined in
       section 5.2.6 or a specific status code as defined in the following table.
Additional input data:
Input data name                                          Description Type         No. MOC
Eid                                                      The EID of      EID      1        O
                                                         the involved
                                                         eUICC
EuiccPackageResult                                       The result      Binary 1          C(1)
                                                         of eUICC
                                                         Package
                                                         processing
IpaEuiccDataResponse                                     The             Binary 1          C(1)
                                                         response
                                                         containing
                                                         requested
                                                         IPA and/or
                                                         eUICC data
PendingNotificationList                                  List of         Binary 1          C(2)
                                                         pending
                                                         Notifications

NOTE 1:Either one and only one of EuiccPackageResult or IpaEuiccDataResponse can be present. NOTE 2: PendingNotificationList can be present if and only if EuiccPackageResults present.

Table 19 ProvideEimPackageResult Additional Input Data

Additional output data:

Output data name           Description                   Type            No.          MOC
EimAcknowledgements Sequence number(s) of                Binary          1            O
                    eUICC Package Result
                    and/or Notification(s)
                    acknowledged by the eIM.

Table 20 ProvideEimPackageResult Additional Output Data

Specific Status Codes

Subject                  Reason
            Subject                Reason              Description
Code                     code
                                                       EID parameter is invalid.
8.1.1       EID          2.1       Invalid
                                                       See EID format defined in [6] section 2.2.2
                                   Mandatory
8.1.1       EID          2.2                           Mandatory EID parameter is missing.
                                   Element Missing
8.1.1       EID          3.9       Unknown             No eUICC found with specified EID.

Table 21 ProvideEimPackageResult Specific Status Codes

5.14.7 Function (ESipa): HandleNotification

Related Procedures: Profile Download and Installation, eIM Package Retrieval

Function Provider Entity: eIM

Function Caller Entity: IPA

Description:

This function SHALL be called by the IPA to notify the eIM that a Profile has been successfully installed on the eUICC or that a Profile has been successfully enabled, disabled, or deleted on the eUICC. This function is also used in case a Fallback Profile was enabled, disabled or deleted on the eUICC. This function MAY also be used in case of disabling an Emergency Profile. This function MAY also be used to notify the eIM that a Profile has been successfully installed on the eUICC by sending either a ProfileInstallationResult Notification, compactProfileInstallationResult Notification or a ProfileDownloadTriggerResult.

In the context of Indirect Profile Download and if the Notification is a ProfileInstallationResult or compactProfileInstallationResult, this function is correlated to a previous execution of an ESipa.GetBoundProfilePackage through a TransactionID delivered by the SM-DP+. If the Notification is an OtherSignedNotification or compactOtherSignedNotification, then the Notification Receiver address is the NotificationAddress contained in the NotificationMetaData of the OtherSignedNotification or compactOtherSignedNotification.

On reception of this function call, the eIM SHALL:

•     If the function call contains a pendingNotification data object:
           o If the pendingNotification contains compact format of Notification,
               restore the Notification by using the data already available to the eIM.
           o Forward the (restored) Notification to the corresponding Notification Receiver.
•     If the function call contains a provideEimPackageResult data object: process the
      eIM Package Result. For that, the eIM SHALL:
           o If the eIM Package Result contains EuiccPackageResult:
                   ▪ Verify the eUICC signature using PK.EUICC.ECDSA of the eUICC. If
                       the signature is invalid, the eIM SHALL discard the input.
           ▪ Check if the sequence number of the EuiccPackageResult is
             greater than the expected sequence number of the eUICC. If not, the
             eIM SHALL discard the input.
         ▪ Manage the eIM Packages pending for the eUICC.
         ▪ Update the expected sequence number of the eUICC to the received
             sequence number.
o   If the eIM Package Result contains IpaEuiccDataResponse:
         ▪ Store the received IPA and/or eUICC information for future use.
o   If the eIM Package Result contains profileDownloadTriggerResult or
    eimPackageError:
         ▪ Manage the eIM Packages pending for the eUICC.

The eIM MAY perform additional operations, which are out of scope of this specification.

Additional Input Data:
Input data name                       Description                            Type          No. MOC
                                      PendingNotification data object as
                                      defined in section 5.7.10 of SGP.22
pendingNotification                   extended with                          Binary(1)     1   O
                                      compactProfileInstallationResult and
                                      compactOtherSignedNotification (see
                                      structures below).
provideEimPackageResult               ProvideEimPackageResult as defined     Binary(2,3)   1   C
                                      in section 6.3.2.7.
NOTE 1: pendingNotification SHALL be provided as an encoded PendingNotification data object.
NOTE 2: In the context of this function call, the provideEimPackageResult data object SHALL NOT
contain ePRAndNotifications.
NOTE 3: Either only one of pendingNotification or provideEimPackageResult SHALL be present.

Table 22 HandleNotification Additional Input Data

Compact format of Notifications

This specification extends the pendingNotification data object defined in section 5.6.4 of SGP.22 [4] with compact formats according to the below ASN.1 structure. The compact format reduces the number of bytes transmitted over ESipa.

An IPA with IPA Capability minimizeEsipaBytes SHOULD re-encode ProfileInstallationResult and OtherSignedNotification into CompactProfileInstallationResult and CompactOtherSignedNotification, respectively, where the eUICC signature is kept unchanged.

Before calling the ES9+’.HandleNotification function, an eIM receiving compact format of Notifications SHALL restore the pendingNotification by using information already available at the eIM (e.g., StoreMetadataRequest (e.g., from BoundProfilePackage), serverSigned1, serverCertificate/smdpCertificate, euiccCertificate, and eumCertificate, etc.).

-- ASN1START PendingNotification ::= CHOICE {

   profileInstallationResult [55] ProfileInstallationResult, -- tag 'BF37'
   otherSignedNotification OtherSignedNotification,
   compactProfileInstallationResult [0] CompactProfileInstallationResult,
   compactOtherSignedNotification [1] CompactOtherSignedNotification
}
ProfileInstallationResult ::= [55] SEQUENCE { -- Tag 'BF37'
   profileInstallationResultData [39] ProfileInstallationResultData,
   euiccSignPIR EuiccSignPIR
}
CompactProfileInstallationResult ::= SEQUENCE {
   compactProfileInstallationResultData [0] CompactProfileInstallationResultData,
   euiccSignPIR EuiccSignPIR
}
CompactProfileInstallationResultData ::= SEQUENCE {
   transactionId [0] TransactionId, -- The TransactionID generated by the SM-DP+
   seqNumber INTEGER,
   iccidPresent BOOLEAN DEFAULT TRUE,
   compactFinalResult [2] CHOICE {
      compactSuccessResult CompactSuccessResult,
      errorResult ErrorResult
   }
}
CompactSuccessResult ::= SEQUENCE {
   compactAid [APPLICATION 15] OCTET STRING (SIZE (2)), -- Byte 14 and 15 of ISD-P
AID
   simaResponse OCTET STRING OPTIONAL -- MUST be present if the simaResponse value
(EUICCResponse) is different from the 9-byte value ‘30 07 A0 05 30 03 80 01 00’
representing success
}
CompactOtherSignedNotification ::= SEQUENCE {
   tbsOtherNotification NotificationMetadata,
   euiccNotificationSignature [APPLICATION 55] OCTET STRING -- eUICC signature of
tbsOtherNotification, Tag '5F37'
}
-- ASN1STOP

5.14.8 Function (ESipa): CancelSession

Related Procedures: Profile Download and Installation

Function Provider Entity: eIM

Description:

This function SHALL be called by the IPA to request the cancellation of an on-going RSP
session. This decision MAY originate from the eIM, or IPA based on where the failure occurred.
The     eIM     MAY     return     error    codes      in   ESipa.AuthenticateClient     and
ESipa.GetBoundProfilePackage that triggers IPA to cancel the session.

This function is correlated to a previous execution of an ESipa.AuthenticateClient or ESipa.GetBoundProfilePackage through a TransactionID delivered by the SM-DP+.

On reception of this function call, the eIM SHALL call the ES9+’.CancelSession function based
on the received input data. The input parameters of this function are identical to the those of
ES9+.CancelSession defined in section 5.6.5 of SGP.22 [4]. However, the
cancelSessionResponse is extended according to the below ASN.1 structure where a
compactCancelSessionResponseOk is added. An IPA with IPA Capability
minimizeEsipaBytes            SHOULD        re-encode     a   cancelSessionResponse        with
cancelSessionResponseOk received from eUICC into a cancelSessionResponse with
compactCancelSessionResponseOk in order to reduce the number of bytes to transmit to the

eIM. Before calling the ES9+’.CancelSession function, an eIM that receives a cancelSessionResponse from an IPA with IPA Capability minimizeEsipaBytes SHALL restore the cancelSessionResponse prepared by the eUICC based on the received cancelSessionResponse and data already available to the eIM (transactionId (e.g., from serverSigned1) and serverCertificate/smdpCertificate).

Additional Input Data:
Input data name        Description                                     Type           No. MOC
transactionId             Transaction ID as generated by the SM-DP+ Binary[1-16]       1   M
                          (section 3.1.1.4 of SGP.22 [4]).
                          CancelSessionResponse data object defined
                          in section 5.7.14 of SGP.22 extended with
                          compactCancelSessionResponseOk         (see
cancelSessionResponse     structure      below).   IPA      retrieves Binary(1)        1   M
                          authenticateServerResponse     from     the
                          eUICC by calling "ES10b.CancelSession"
                          (section 5.9.9).
NOTE 1: cancelSessionResponse SHALL be provided as an encoded CancelSessionResponse data
object.
                      Table 23 CancelSession Additional Input Data
-- ASN1START
CancelSessionResponse ::= [65] CHOICE { -- Tag 'BF41'
   cancelSessionResponseOk CancelSessionResponseOk,
  cancelSessionResponseError INTEGER {invalidTransactionId(5), undefinedError(127)},
   compactCancelSessionResponseOk CompactCancelSessionResponseOk
}
CompactCancelSessionResponseOk ::= SEQUENCE {
   compactEuiccCancelSessionSigned CompactEuiccCancelSessionSigned,       -- Compact
version of euiccCancelSessionSigned
   euiccCancelSessionSignature [APPLICATION 55] OCTET STRING -- tag 5F37 signature on
euiccCancelSessionSigned
}
CompactEuiccCancelSessionSigned ::= SEQUENCE {
   reason CancelSessionReason OPTIONAL
}
-- ASN1STOP
The eIM SHALL forward the status/error code of ES9+’.CancelSession as the status/error
code of ESipa.CancelSession.

6 Interface Binding

This section defines how to use HTTP with TLS as the transport layer to exchange ES2+, ES9+, ES9+’, ES11, ES11’, ES12, and ESipa function requests and responses.

This section also defines how to use CoAP with DTLS as the transport layer to exchange ESipa function requests and responses.

For the ES2+, ES9+, ES9+’, ES11 and ES11’, the interface binding as described in section 6 of SGP.22 [4] SHALL be used; where for ES9+ and ES11, IPA plays the role of the LPA and for ES9+’ and ES11’ eIM plays the role of the LPA.

For ESipa, the interface binding when using HTTP with TLS and CoAP with DTLS are described in section 6.1 and section 6.2, respectively. This interface binding leverages either the ASN.1 function binding described in section 6.3 of this specification, or the JSON function binding described in section 6.4 of this specification. The ASN.1 function binding MAY also be leveraged by other protocols such as LwM2M (see Annex B) used in the communication between eIM and IPA.

For better IPA interoperability, the eIM SHALL support both the ASN.1 binding and the JSON binding on ESipa.

For better IPA interoperability:

-the SM-DP+ SHOULD support both the JSON binding and the ASN.1 binding on ES9+.

-the SM-DS SHOULD support both the JSON binding and the ASN.1 binding on ES11.

6.1 ESipa interface binding over HTTP

The ESipa interface binding over HTTP SHALL follow the interface binding over HTTP in SGP.22 [4] section 6 relevant for the ES9+ interface with the following exceptions:

•TLS requirements SHALL follow section 2.6.3 in this document.

•"X-Admin-Protocol" header field SHALL be set to v2.1.0 in both HTTP request and HTTP response.

NOTE:this value provides interoperability with previous versions of SGP.22 [4].

•The ASN.1 message definition SHALL follow section 6.1.1 below replacing section 6.6.1 of SGP.22 [4] and the ASN.1 list of functions SHALL follow section 6.3 replacing section 6.6.2 of SGP.22 [4].

•A JSON binding SHALL be indicated by the value "application/json;charset=UTF-8", which also mandates UTF-8 encoding. The JSON message definition SHALL follow section 6.1.2 below.

6.1.1 ASN.1 message definition

The Function requester and the Function provider SHALL exchange the DER encoded ASN.1 objects in HTTP messages as follows. HTTP Request SHALL have the following format: HTTP POST gsma/rsp2/asn1 HTTP/1.1 Host: <Server Address> User-Agent: <User Agent> X-Admin-Protocol: gsma/rsp/v<x.y.z> Content-Type: application/x-gsma-rsp-asn1 Content-Length: <Length of the ASN.1 EsipaMessageFromIpaToEim>

<ASN.1 EsipaMessageFromIpaToEim>

Any function execution request using ASN.1 binding SHALL be sent to the generic HTTP path 'gsma/rsp2/asn1'. The body part of the HTTP POST request SHALL contain one EsipaMessageFromIpaToEim data object as defined in section 6.3. HTTP Response SHALL have the following format: HTTP/1.1 <HTTP Status Code> X-Admin-Protocol: gsma/rsp/v<x.y.z> Content-Type: application/x-gsma-rsp-asn1 Content-Length: <Length of the ASN.1 EsipaMessageFromEimToIpa>

<ASN.1 EsipaMessageFromEimToIpa>

The body part of the HTTP POST response SHALL contain one EsipaMessageFromEimToIpa data object as defined in section 6.3.

6.1.2 JSON message definition

The Function requester and the Function provider SHALL exchange the JSON objects in HTTP messages as follows. HTTP Request SHALL have the following format: HTTP POST <HTTP Path> HTTP/1.1 Host: <Server Address> User-Agent: <User Agent> X-Admin-Protocol: gsma/rsp/v<x.y.z> Content-Type: application/json;charset=UTF-8 Content-Length: <Length of the JSON requestBody>

<JSON requestBody> The <HTTP Path> is used to indicate which function execution is requested by the HTTP client. The list of defined <HTTP Path> and <JSON requestBody> are described in section 6.4.1.

HTTP Response SHALL have the following format: HTTP/1.1 <HTTP Status Code> X-Admin-Protocol: gsma/rsp/v<x.y.z> Content-Type: application/json;charset=UTF-8 Content-Length: <Length of the JSON responseBody>

<JSON responseBody> The list of defined <HTTP Path> and <JSON requestBody> are described in section 6.4.1.

6.2 ESipa interface binding over CoAP

The ESipa interface binding over CoAP SHALL follow the ESipa interface binding over HTTP described in section 6.1. The ASN.1 function binding SHALL be used. In the ASN.1 message binding in section 6.1.1, the HTTP headers SHALL be translated to CoAP options as described by RFC 7252 [7].

•The <HTTP Path> SHALL be converted to a sequence of corresponding Uri-Path options.

•The <Server Address> SHALL be converted to a Uri-Host option if necessary. If the server address is simply the IP address of the eIM server, this option SHALL be omitted.

•The <User Agent> SHALL NOT be included in the CoAP transport layer.

•The Content-Type SHALL be omitted. The content type to be used is determined by the Uri-Path options, and the response type SHALL be equivalent to the request type.

•Content-Length is not relevant to CoAP and SHALL be omitted. If the payload is too large to be sent in a single CoAP UDP packet, then block-wise CoAP SHALL be used as defined in RFC 7959 [12]. In this case the CoAP Request-Tag option SHALL be used as defined in RFC 9175 [13], in order to associate the separate blocks of a CoAP request together.

NOTE:It is RECOMMENDED to send CoAP/UDP messages in a single UDP Packet.

•The CoAP Echo Option SHALL be used to enable lightweight freshness verifications as defined in RFC 9175 [13]

6.3 ESipa function binding in ASN.1

This section presents the ASN.1 function binding for ESipa. The ASN.1 structures for ESipa messages between IPA and eIM, that are used in 6.1.1 and 6.2 respectively for the HTTP and CoAP interface bindings to select between ESipa functions, are presented in section 6.3.1. The request and response ASN.1 structures for each ESipa function are presented in sections 6.3.2 and 6.3.3. The ASN.1 structures in this section MAY be leveraged by other interface bindings, see for example Annex B.

Both eIM and IPAd SHALL support the ASN.1 encoding/decoding attribute "EXTENSIBILITY IMPLIED". This is useful when processing data definitions from a newer specification and to help for interoperability between entities of various vendors (to handle proprietary tag values).

6.3.1 ASN.1 structures for ESipa messages between IPA and eIM

The EsipaMessageFromIpaToEim and EsipaMessageFromEimToIpa ASN.1 structures that contain the ESipa function requests and responses are defined as follows: -- ASN1START EsipaMessageFromIpaToEim ::= CHOICE { initiateAuthenticationRequestEsipa [57] InitiateAuthenticationRequestEsipa, -- Tag 'BF39' authenticateClientRequestEsipa [59] AuthenticateClientRequestEsipa, -- Tag 'BF3B' getBoundProfilePackageRequestEsipa [58] GetBoundProfilePackageRequestEsipa, -- Tag 'BF3A' cancelSessionRequestEsipa [65] CancelSessionRequestEsipa, -- Tag 'BF41' handleNotificationEsipa [61] HandleNotificationEsipa, -- Tag 'BF3D' transferEimPackageResponse [78] TransferEimPackageResponse, -- Tag 'BF4E' getEimPackageRequest [79] GetEimPackageRequest, -- Tag 'BF4F' provideEimPackageResult [80] ProvideEimPackageResult -- Tag 'BF50' } EsipaMessageFromEimToIpa ::= CHOICE { initiateAuthenticationResponseEsipa [57] InitiateAuthenticationResponseEsipa, -- Tag 'BF39' authenticateClientResponseEsipa [59] AuthenticateClientResponseEsipa, -- Tag 'BF3B' getBoundProfilePackageResponseEsipa [58] GetBoundProfilePackageResponseEsipa, -- Tag 'BF3A' cancelSessionResponseEsipa [65] CancelSessionResponseEsipa, -- Tag 'BF41'

transferEimPackageRequest [78] TransferEimPackageRequest, -- Tag 'BF4E' getEimPackageResponse [79] GetEimPackageResponse, -- Tag 'BF4F' provideEimPackageResultResponse [80] ProvideEimPackageResultResponse -- Tag 'BF50' } -- ASN1STOP

6.3.2 ESipa functions provided by eIM

6.3.2.1 ESipa.InitiateAuthentication

The request and response structures of ESipa.InitiateAuthentication are defined as follows: -- ASN1START InitiateAuthenticationRequestEsipa ::= [57] SEQUENCE { -- Tag 'BF39' euiccChallenge [1] Octet16, -- random eUICC challenge smdpAddress [3] UTF8String OPTIONAL, euiccInfo1 EUICCInfo1 OPTIONAL, eimTransactionId [2] TransactionId OPTIONAL }

InitiateAuthenticationResponseEsipa ::= [57] CHOICE { -- Tag 'BF39'
   initiateAuthenticationOkEsipa InitiateAuthenticationOkEsipa,
   initiateAuthenticationErrorEsipa INTEGER {
      invalidDpAddress(1),
      euiccVersionNotSupportedByDp(2),
      ciPKIdNotSupported(3),
      smdpAddressMismatch(50),
      smdpOidMismatch(51),
      invalidEimTransactionId(52),
      undefinedError(127)
   }
}
InitiateAuthenticationOkEsipa ::= SEQUENCE {
   transactionId [0] TransactionId OPTIONAL, -- The TransactionID generated by the
SM-DP+
   serverSigned1 ServerSigned1, -- Signed information
   serverSignature1 [APPLICATION 55] OCTET STRING, -- Server Sign1, Tag '5F37'
   euiccCiPKIdentifierToBeUsed OCTET STRING, -- Key identifier (possibly truncated)
of the CI Public Key to be used as required by ES10b.AuthenticateServer
   serverCertificate Certificate,
   matchingId UTF8String OPTIONAL,
   ctxParams1 [2] CtxParams1 OPTIONAL
}
-- ASN1STOP

6.3.2.2 ESipa.AuthenticateClient

The request and response structures of ESipa.AuthenticateClient are defined as follows:
-- ASN1START
AuthenticateClientRequestEsipa ::= [59] SEQUENCE { -- Tag 'BF3B'
   transactionId [0] TransactionId, -- The TransactionID generated by the SM-DP+/SM-
DS
   authenticateServerResponse [56] AuthenticateServerResponse -- This is the response
from ES10b.AuthenticateServer, possibly in compact format
}
AuthenticateClientResponseEsipa ::= [59] CHOICE { -- Tag 'BF3B'
   authenticateClientOkDPEsipa AuthenticateClientOkDPEsipa,
   authenticateClientOkDSEsipa AuthenticateClientOkDSEsipa,
   authenticateClientErrorEsipa INTEGER {
      eumCertificateInvalid(1),
      eumCertificateExpired(2),
      euiccCertificateInvalid(3),
      euiccCertificateExpired(4),
      euiccSignatureInvalid(5),
      matchingIdRefused(6),
      eidMismatch(7),
       noEligibleProfile(8),
       ciPKUnknown(9),
       invalidTransactionId(10),
       insufficientMemory(11),
       pprNotAllowed(50),
       eventIdUnknown(56),
       undefinedError(127)
   }
}
AuthenticateClientOkDPEsipa ::= SEQUENCE {
   transactionId [0] TransactionId OPTIONAL, -- The TransactionID generated by the
SM-DP+
   profileMetaData [37] StoreMetadataRequest OPTIONAL,
   smdpSigned2 SmdpSigned2, -- Signed information
   smdpSignature2 [APPLICATION 55] OCTET STRING, -- Tag '5F37'
   smdpCertificate Certificate, -- CERT.DPpb.ECDSA
   hashCc Octet32 OPTIONAL -- Hash of confirmation code
}
AuthenticateClientOkDSEsipa ::= SEQUENCE {
   transactionId [0] TransactionId, -- The TransactionID generated by the SM-DS
   profileDownloadTrigger [84] ProfileDownloadTriggerRequest OPTIONAL -- Tag 'BF54'
}
-- ASN1STOP

6.3.2.3 ESipa.GetBoundProfilePackage

The request and response structures of ESipa.GetBoundProfilePackage are defined as
follows:
-- ASN1START
GetBoundProfilePackageRequestEsipa ::= [58] SEQUENCE { -- Tag 'BF3A'
   transactionId [0] TransactionId, -- The TransactionID generated by the SM-DP+
   prepareDownloadResponse [33] PrepareDownloadResponse -- This is the response from
ES10b.PrepareDownload, possibly in compact format
}
GetBoundProfilePackageResponseEsipa ::= [58] CHOICE { -- Tag 'BF3A'
   getBoundProfilePackageOkEsipa GetBoundProfilePackageOkEsipa,
   getBoundProfilePackageErrorEsipa INTEGER {
      euiccSignatureInvalid(1),
      confirmationCodeMissing(2),
      confirmationCodeRefused(3),
      confirmationCodeRetriesExceeded(4),
      bppRebindingRefused(5),
      downloadOrderExpired(6),
      profileMetadataMismatch(50),
      invalidTransactionId(95),
      undefinedError(127)
   }
}
GetBoundProfilePackageOkEsipa ::= SEQUENCE {
   transactionId [0] TransactionId OPTIONAL, -- The TransactionID generated by the
SM-DP+
   boundProfilePackage [54] BoundProfilePackage
}
-- ASN1STOP

6.3.2.4 ESipa.HandleNotification

The request structure of ESipa.HandleNotification is defined as follows (there is no response structure defined): -- ASN1START HandleNotificationEsipa ::= [61] CHOICE { -- Tag 'BF3D' pendingNotification [0] PendingNotification, -- A Notification to be delivered to a Notification Receiver, possibly in compact format provideEimPackageResult [80] ProvideEimPackageResult -- Tag 'BF50'

} -- ASN1STOP

6.3.2.5 ESipa.CancelSession

The request and response structures of ESipa.CancelSession are defined as follows:
-- ASN1START
CancelSessionRequestEsipa ::= [65] SEQUENCE { -- Tag 'BF41'
   transactionId TransactionId, -- The TransactionID generated by the SM-DP+
   cancelSessionResponse CancelSessionResponse -- This is the response from ES10b.
CancelSession function, possibly in compact format
}
CancelSessionResponseEsipa ::= [65] CHOICE { -- Tag 'BF41'
   cancelSessionOk CancelSessionOk,
   cancelSessionError INTEGER {
      invalidTransactionId(1),
      euiccSignatureInvalid(2),
      undefinedError(127)
   }
}
CancelSessionOk ::= SEQUENCE { -- This function has no output data
}
-- ASN1STOP

6.3.2.6 ESipa.GetEimPackage

The request and response structures of ESipa.GetEimPackage are defined as follows: -- ASN1START StateChangeCause ::= INTEGER { otherEim(0), -- for change(s) requested by another registered eIM fallback(1), -- for change(s) following fallback requested by IPA emergencyProfile(2), -- for change(s) following Emergency Profile swap requested by IPA local(3), -- for change(s) applied locally (RFU, not supported in this version) reset(4), -- for change(s) following an euicc reset immediateEnableProfile(5), -- for change(s) following immediate Profile enabling requested by IPA deviceChange(6), -- for change(s) detected by IPAe following a IoT Device change (removable eSIMs) undefined(127) -- unknown cause }

GetEimPackageRequest ::= [79] SEQUENCE { -- Tag 'BF4F'
   eidValue [APPLICATION 26] Octet16, -- Tag '5A'
   notifyStateChange [0] NULL OPTIONAL, -- Notification to the eIM that it should
update its information about the eUICC (e.g. list of profiles, profile states...)
   stateChangeCause [1] StateChangeCause OPTIONAL, -- Provide the cause of the
notified state change(s)
   rPLMN [2] OCTET STRING (SIZE(3)) OPTIONAL -- MCC and MNC of the last registered
PLMN, coded as defined in 3GPP TS 24.008 [22]
}
GetEimPackageResponse ::= [79] CHOICE { -- Tag 'BF4F'
   euiccPackageRequest [81] EuiccPackageRequest, -- Tag 'BF51'
   ipaEuiccDataRequest [82] IpaEuiccDataRequest, -- Tag 'BF52'
   profileDownloadTriggerRequest [84] ProfileDownloadTriggerRequest, -- Tag 'BF54'
   eimPackageError INTEGER {
      noEimPackageAvailable(1),
      eidNotFound(2),
      invalidEid(3),
      missingEid(4),
undefinedError(127)
   }
}
-- ASN1STOP

6.3.2.7 ESipa.ProvideEimPackageResult

The request and response structures of ESipa.ProvideEimPackageResult are defined as follows: -- ASN1START EimPackageResultErrorCode ::= INTEGER { invalidPackageFormat(1), unknownPackage(2), undefinedError(127) }

EimPackageResultResponseError ::= SEQUENCE { eimTransactionId [0] TransactionId OPTIONAL, eimPackageResultErrorCode EimPackageResultErrorCode }

EimPackageResult ::= CHOICE {
   euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
   ePRAndNotifications SEQUENCE {
      euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
      notificationList [0] PendingNotificationList -- Tag 'A0'
   },
   ipaEuiccDataResponse [82] IpaEuiccDataResponse, -- Tag 'BF52'
   profileDownloadTriggerResult [84] ProfileDownloadTriggerResult, -- Tag 'BF54'
   eimPackageResultErrorCode EimPackageResultErrorCode,
   eimPackageResultResponseError [0] EimPackageResultResponseError
}

ProvideEimPackageResult ::= [80] SEQUENCE { -- Tag 'BF50' eidValue [APPLICATION 26] Octet16 OPTIONAL, -- Tag '5A' eimPackageResult EimPackageResult } ProvideEimPackageResultResponse ::= [80] SEQUENCE { -- Tag 'BF50' eimAcknowledgements [83] EimAcknowledgements OPTIONAL -- Tag 'BF53' } -- ASN1STOP

If eimTransactionId was present in the eIM Package, the IPA SHALL return the same eimTransactionId in the ProvideEimPackageResult.

6.3.3 ESipa functions provided by IPA

6.3.3.1 ESipa.TransferEimPackage

The request and response structures of ESipa.TransferEimPackage are defined as follows:
-- ASN1START
TransferEimPackageRequest ::= [78] CHOICE { -- Tag 'BF4E'
   euiccPackageRequest [81] EuiccPackageRequest, -- Tag 'BF51'
   ipaEuiccDataRequest [82] IpaEuiccDataRequest, -- Tag 'BF52'
   eimAcknowledgements [83] EimAcknowledgements, -- Tag 'BF53'
   profileDownloadTriggerRequest [84] ProfileDownloadTriggerRequest -- Tag 'BF54'
}
TransferEimPackageResponse ::= [78] CHOICE { -- Tag 'BF4E'
   euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
   ePRAndNotifications SEQUENCE {
      euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
      notificationList [0] PendingNotificationList -- Tag 'A0'
   },
   ipaEuiccDataResponse [82] IpaEuiccDataResponse, -- Tag 'BF52'
   eimPackageReceived NULL,
   eimPackageError INTEGER {
      invalidPackageFormat(1),
         unknownPackage(2),
         undefinedError(127)
   }
}
-- ASN1STOP

6.4 ESipa function binding in JSON

"format": "base64": unless specified otherwise below, the value of a JSON field of this format SHALL contain the base64 coding defined in RFC 4648 [71] of the DER encoded ASN.1 data object (including its tag and length fields), referenced in "description".

NOTE           In most of the cases, the ASN.1 data object is defined in ES10x
               request/responses. Otherwise, the 'description' of the base64 field
               references the section where the ASN.1 type is specified.

"pattern": "^[0-9,A-F]{n,m}$": specifies the hexadecimal representation of the data referred to in "description".

6.4.1 List of functions

Function                        Path                                                    MXP
InitiateAuthentication          /gsma/rsp2/esipa/initiateAuthentication                 Synchronous
AuthenticateClient              /gsma/rsp2/esipa/authenticateClient                     Synchronous
GetBoundProfilePackage          /gsma/rsp2/esipa/getBoundProfilePackage                 Synchronous
TransferEimPackage              /gsma/rsp2/esipa/transferEimPackage                     Synchronous
GetEimPackage                   /gsma/rsp2/esipa/getEimPackage                          Synchronous
ProvideEimPackageResult         /gsma/rsp2/esipa/provideEimPackageResult                Synchronous
HandleNotification              /gsma/rsp2/esipa/handleNotification                     Notification
CancelSession                   /gsma/rsp2/esipa/cancelSession                          Synchronous

Table 24 List of functions

6.4.1.1 ESipa.InitiateAuthentication

Only the characters that are mandatory to escape (Quotation mark, reverse solidus, and the control characters) SHALL be escaped in JSON string value as specified in RFC 7159 [36] section 7. Other characters SHALL NOT be escaped.

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.InitiateAuthentication" function:

{
   "type": "object",
   "properties": {
      "euiccChallenge": {
         "type": "string",
         "format": "base64",
         "description": "base64 encoding of the value field of the eUICC Challenge
as defined in SGP.22 [4] (without tag and length fields)"
      },
      "euiccInfo1": {
         "type": "string",
         "format": "base64",
         "description": "euiccinfo1 as defined in SGP.22 [4]"
      },
      "smdpAddress": {
         "type": "string",
         "description": "SM-DP+ Address as defined in SGP.22 [4]"
      },
      "eimTransactionId": {
         "type": "string",
         "pattern": "^[0-9,A-F]{2,32}$",
         "description": "Transaction ID received from the eIM in
ProfileDownloadTriggerRequest"
      }
   },
   "required": ["euiccChallenge"]
}
Hereunder is the definition of the JSON schema for the <JSON responseBody>
corresponding to the "ESipa.InitiateAuthentication" function:
{
   "type": "object",
   "properties": {
      "transactionId": {
         "type": "string",
         "pattern": "^[0-9,A-F]{2,32}$",
         "description": "TransactionID as defined in SGP.22 [4]"
      },
      "serverSigned1": {
         "type": "string",
         "format": "base64",
         "description": "The data object as required by ES10b.AuthenticateServer"
      },
      "serverSignature1": {
         "type": "string",
         "format": "base64",
         "description": "The signature as required by ES10b.AuthenticateServer"
      },
      "euiccCiPKIdentifierToBeUsed": {
         "type": "string",
         "format": "base64",
         "description": "The Public Key Identifier (possibly truncated) of the CI
Public Key to be used as required by ES10b.AuthenticateServer"
      },
      "serverCertificate": {
         "type": "string",
         "format": "base64",
         "description": "The server Certificate as required by
ES10b.AuthenticateServer"
      },
      "matchingId": {
         "type": "string",
         "description": "MatchingID as defined in SGP.22 [4]"
      },
      "ctxParams1": {
         "type": "string",
         "format": "base64",
         "description": "ctxParams1 as required by ES10b.AuthenticateServer"
      }
   },
   "required": ["serverSigned1", "serverSignature1", "serverCertificate"]
}

NOTE:IPA is in charge of transcoding the transactionId.

6.4.1.2 ESipa.AuthenticateClient

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.AuthenticateClient" function:

{
   "type": "object",
   "properties": {
      "transactionId": {
         "type": "string",
         "pattern": "^[0-9,A-F]{2,32}$",
         "description": "TransactionID as defined in SGP.22 [4]"
      },
      "authenticateServerResponse": {
         "type": "string",
         "format": "base64",
         "description": "AuthenticateServerResponse as provided by
ES10b.AuthenticateServer, possibly in compact format"
      }
   },
   "required": ["transactionId", "authenticateServerResponse"]
}
Hereunder is the definition of the JSON schema for the <JSON responseBody>
corresponding to the "ESipa.AuthenticateClient" function:
{
    "type": "object",
    "properties": {
       "transactionId": {
          "type": "string",
          "pattern": "^[0-9,A-F]{2,32}$",
          "description": "TransactionID as defined in SGP.22 [4]"
       },
       "profileMetadata": {
          "type": "string",
          "format": "base64",
          "description": "StoreMetadataRequest as defined SGP.22 [4]"
       },
       "smdpSigned2": {
          "type": "string",
          "format": "base64",
          "description": "SmdpSigned2 encoded data object"
       },
       "smdpSignature2": {
          "type": "string",
          "format": "base64",
          "description": "SM-DP+ signature as required by ES10b.PrepareDownload"
       },
       "smdpCertificate": {
          "type": "string",
          "format": "base64",
          "description": "The Certificate as required by ES10b.PrepareDownload"
       },
       "hashCc": {
          "type": "string",
          "format": "base64",
          "description": "hashCc as required by ES10b.PrepareDownload"
       }
    },
    "required" : [" smdpSigned2", "smdpSignature2", "smdpCertificate"]
}

6.4.1.3 ESipa.GetBoundProfilePackage

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.GetBoundProfilePackage" function:

{
   "type": "object",
   "properties": {
      "transactionId": {
         "type": "string",
         "pattern": "^[0-9,A-F]{2,32}$",
         "description": "TransactionID as defined in SGP.22 [4]"
      },
      "prepareDownloadResponse": {
         "type": "string",
         "format": "base64",
         "description": "PrepareDownloadResponse as provided by
ES10b.PrepareDownload, possibly in compact format"
      }
   },
   "required": ["transactionId", "prepareDownloadResponse"]
}

Hereunder is the definition of the JSON schema for the <JSON responseBody> corresponding to the "ESipa.GetBoundProfilePackage" function:

{
   "type": "object",
   "properties": {
      "transactionId": {
         "type": "string",
         "pattern": "^[0-9,A-F]{2,32}$",
         "description": "TransactionID as defined in SGP.22 [4]"
      },
      "boundProfilePackage": {
         "type": "string",
         "format": "base64",
         "description": "Bound Profile Package required by
ES10b.LoadBoundProfilePackage"
      }
   },
   "required": ["transactionId", "boundProfilePackage"]
}

6.4.1.4 ESipa.TransferEimPackage

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.TransferEimPackage" function:

{
    "type": "object",
    "oneOf": [
       {
        "properties": {
           "euiccPackageRequest": {
              "type": "string",
              "format": "base64",
              "description": "EuiccPackageRequest as defined in section 2.11.1.1.1"
           }
        },
        "required": ["euiccPackageRequest"]
     },{
        "properties": {
           "ipaEuiccDataRequest": {
              "type": "string",
              "format": "base64",
              "description": "IpaEuiccDataRequest as defined in section 2.11.1.2"
           }
        },
        "required": ["ipaEuiccDataRequest"]
     },{
        "properties": {
           "eimAcknowledgements": {
              "type": "string",
              "format": "base64",
              "description": "EimAcknowledgements as defined in section 2.11.1.4"
           }
        },
        "required": ["eimAcknowledgements"]
     },{
        "properties": {
           "profileDownloadTriggerRequest": {
              "type": "string",
              "format": "base64",
              "description": "ProfileDownloadTriggerRequest as defined in section
2.11.2.3"
           }
        },
        "required": ["profileDownloadTriggerRequest"]
     }
   ]
}
Hereunder is the definition of the JSON schema for the <JSON responseBody>
corresponding to the "ESipa.TransferEimPackage" function:
{
    "type": "object",
    "oneOf": [
       {
          "properties": {
             "euiccPackageResult": {
                "type": "string",
                "format": "base64",
                "description": "EuiccPackageResult as defined in section 2.11.2.1"
             }
          },
          "required": ["euiccPackageResult"]
       },{
          "properties": {
             "ePRAndNotifications": {
                "type": "object",
                "properties": {
                    "euiccPackageResult": {
                       "type": "string",
                       "format": "base64",
                       "description": "EuiccPackageResult as defined in section
2.11.2.1"
                    },
                    "notificationList": {
                       "type": "string",
                       "format": "base64",
                       "description": "PendingNotificationList   as defined in section
2.11.2.2"
                    }
                 },
                 "required": ["euiccPackageResult", "notificationList"]
              }
           },
           "required": ["ePRAndNotifications"]
        },{
           "properties": {
              "ipaEuiccDataResponse": {
                 "type": "string",
                 "format": "base64",
                 "description": "IpaEuiccDataResponse as defined in section 2.11.2.2"
              }
           },
           "required": ["ipaEuiccDataResponse"]
        },{
           "properties": {
              "eimPackageError": {
                 "type": "integer",
                 "description": "eimPackageError code as defined in section 6.3.3.1"
              }
           },
           "required": ["eimPackageError"]
        }
    ]
}

6.4.1.5 ESipa.GetEimPackage

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.GetEimPackage" function:

{
    "type": "object",
    "properties": {
       "eidValue": {
          "type" : "string",
          "pattern" : "^[0-9]{32}$",
          "description" : "EID as described in SGP.22 [4]"
       },
         "notifyStateChange": {
             "type" : "boolean",
         "description" : "Notification to the eIM that it should update its
information about the eUICC (e.g. list of profiles, profile states...)"
        },
         "stateChangeCause": {
            "type" : "integer",
        "description" : "Provide the cause of the notified state change(s), as
defined at section 6.3.2.6"
       },
       "rPlmn": {
            "type" : "string",
            "format" : "base64",
        "description" : "MCC and MNC of the last registered PLMN, coded as defined
in 3GPP TS 24.008 [22]"
      }
   },
   "required": ["eidValue"]
}
Hereunder is the definition of the JSON schema for the <JSON responseBody>
corresponding to the "ESipa.GetEimPackage" function:
{
    "type": "object",
    "oneOf": [
       {
          "properties": {
             "euiccPackageRequest": {
                "type": "string",
                "format": "base64",
                "description": "EuiccPackageRequest as defined in section 2.11.1.1.2"
             }
          },
          "required": ["euiccPackageRequest"]
       },{
          "properties": {
             "ipaEuiccDataRequest": {
                "type": "string",
                "format": "base64",
                "description": "IpaEuiccDataRequest as defined in section 2.11.1.2"
             }
          },
          "required": ["ipaEuiccDataRequest"]
       },{
        "properties": {
           "profileDownloadTriggerRequest": {
              "type": "string",
              "format": "base64",
              "description": "ProfileDownloadTriggerRequest as defined in section
2.11.2.3"
           }
        },
        "required": ["profileDownloadTriggerRequest"]
     },{
        "properties": {
           "eimPackageError": {
              "type": "integer",
              "description": "eimPackageError code as defined in section 6.3.2.6"
           }
        },
        "required": ["eimPackageError"]
        }
    ]
}

6.4.1.6 ESipa.ProvideEimPackageResult

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.ProvideEimPackageResult" function:

{
    "type": "object",
    "properties": {
       "eidValue": {
          "type" : "string",
          "pattern" : "^[0-9]{32}$",
          "description" : "EID as described in SGP.22 [4]"
       },
       "eimPackageResult": {
          "type": "string",
          "format": "base64",
          "description": "EimPackageResult as defined in section 6.3.2.7"
       }
    },
    "required": ["eidValue","eimPackageResult"]}
Hereunder is the definition of the JSON schema for the <JSON responseBody>
corresponding to the "ESipa.ProvideEimPackageResult" function:
{
    "type": "object",
    "properties": {
       "eimAcknowledgements": {
          "type": "string",
          "format": "base64",
          "description": "EimAcknowledgements as defined in section 2.11.1.4"
       }
    },
    "required": ["eimAcknowledgements"]
}

6.4.1.7 ESipa.HandleNotification

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.HandleNotification" function:

{
    "type" : "object",
    "oneOf": [
       {
    "properties" : {
       "pendingNotification" : {
          "type" : "string",
          "format" : "base64",
          "description" : "PendingNotification as defined in section 5.14.7"
       }
    },
    "required" : ["pendingNotification"]
    },{
          "properties": {
             "provideEimPackageResult": {
                  "type": "string",
                  "format": "base64",
                  "description": "ProvideEimPackageResult as defined in section
6.3.2.7"
                }
             },
             "required": ["provideEimPackageResult"]
        }
    ]
}

6.4.1.8 ESipa.CancelSession

Hereunder is the definition of the JSON schema for the <JSON requestBody> corresponding to the "ESipa.CancelSession" function:

{
    "type": "object",
    "properties" : {
       "transactionId" : {
          "type" : "string",
          "pattern" : "^[0-9,A-F]{2,32}$",
          "description" : "TransactionID as defined in SGP.22 [4]"
       },
       "cancelSessionResponse" : {
          "type" : "string",
          "format" : "base64",
          "description" : "CancelSessionResponse as provided by ES10b.CancelSession"
       }
    },
    "required" : ["transactionId", "cancelSessionResponse"]
}
"ESipa.CancelSession" function has no <JSON responseBody>.

A IoT Device Requirements (Normative)

A.1 Functional IoT Device Requirements

Functional
IoT Device
                        Requirement
Requirements
No.
IoTDEV1                 The IoT Device SHALL support the following proactive command:
                        REFRESH Command (At least mode 4 – “UICC Reset”), as defined in ETSI
                        TS 102 223 [5].

Table 25 IoT Device requirements

A.2 Support for CAT Mechanisms

Dependent on the deployment, the IoT Device SHALL support at least the CAT mechanisms (ETSI TS 102 223 [5]) indicated in the table below.

         CAT mechanism                         IPAd                          IPAe
TERMINAL PROFILE                                 X                             X
SET UP EVENT LIST                                X                             X
REFRESH with “UICC Reset”
or “eUICC Profile State                          X                             X
Change” mode
PROVIDE LOCAL
INFORMATION                                                                    X
(IMEI)
SEND SHORT MESSAGE
ENVELOPE (SMS-PP                                 X                             X
DOWNLOAD)
TIMER MANAGEMENT
ENVELOPE (TIMER                                                                X
EXPIRATION)
OPEN CHANNEL related to                          X                             X
packet data service bearer
CLOSE CHANNEL
RECEIVE DATA
SEND DATA
GET CHANNEL STATUS
                                                 X                             X
EVENT DOWNLOAD - Data
available
EVENT DOWNLOAD -
Channel status
                                 Table 26 CAT Mechanisms

NOTE:The table also includes requirements for ES6.

B Mapping of procedures to IoT protocols (Informative)

B.1 LwM2M

In case of LwM2M implementation of the ESipa it is expected that the eIM is a component that is integrated into Device Management platform and the IPA is a component that is part of the Device Management Client functionality in the IoT Device. For efficient message transfer LwM2M 1.1 and higher protocol version is RECOMMENDED.

B.1.1 Secure connection

A secure connection needs to be ensured so that ESipa security requirements are fulfilled. Specifically, LwM2M unsecured mode is not used unless appropriate lower-layer provided security is used, that the LwM2M server is in the same security realm as the element terminating the lower-layer security between it and the IoT Device, and it is ensured that only elements within the same security realm can access the unsecured traffic.

B.1.2 LwM2M object

The following object has been defined and registered to handle the ESipa implementation in LwM2M, see OMA LwM2M Object and Resource Registry [30].

Object definition

Name      Object ID                                               Object Version LWM2M Version
eSIM IoT 3443                                                     1.0              1.0
Object URN                                                        Instances        Mandatory
urn:oma:lwm2m:ext:3443                                            Single           Optional

Table 27 Object Definition

Resource definition

                                                                           Range or
ID      Name          Operations Instances   Mandatory   Type                            Units Description
                                                                           Enumeration
                                                                                               Status
                                                                                               0 – ready to receive
                                                                                               eIM message
                                                                                               1 – not able to
                                                                                               receive eIM
                                                                                               message
0       State         R          Single      Mandatory   Integer
                                                                                               Note: In case value
                                                                                               is >0 then writing to
                                                                                               resource 2 SHALL
                                                                                               NOT be possible
                                                                                               EID of the eUICC
1       EID           R          Single      Mandatory   String                                that is target of the
                                                                                               object
                                                                                               the message from
                                                                                               eIM to IPA. The
        eIM                                                                                    message SHALL be
2                     W          Single      Mandatory
        message                                          Opaque                                in the ASN.1 DER
                                                                                               format defined in
                                                                                               section 6.3.1
                                                                                               The message from
                                                                                               IPA to eIM. The
        IPA                                                                                    message SHALL be
3                     R          Single      Mandatory   Opaque
        message                                                                                in the ASN.1 DER
                                                                                               format defined in
                                                                                               section 6.3.1
                                                                                               In case Send or
                                                                                               Confirmable
                                                                                               Notifications is not
                                                                                               used to deliver IPA
        Clear IPA                                                                              message then
4                     E          Single      Mandatory
        message                                                                                execution of this
                                                                                               resource will confirm
                                                                                               delivery of the IPA
                                                                                               message and clear
                                                                                               the resource 3.

Table 28 Resource Definition

B.1.3 Procedures

For purpose of simplification, the IPA in this section will represent LwM2M client integrating also IPA functionality and eIM will represent LwM2M server integrating also eIM functionality.

B.1.3.1 Transferring messages between eIM and IPA (LwM2M)

Following procedure is an example generic implementation of transfer of an eIM message to IPA and IPA message to eIM using LwM2M. This example uses functions introduced in LwM2M version 1.1.

@startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid

participant "<b>eIM" as EIM participant "<b>IPA" as IPA participant "<b>eUICC" as E

rnote over EIM, IPA : [IPA is LwM2M-registered to eIM and secure connection is established]

EIM -> IPA : [1] Write eIM message to /x/0/2 IPA -> EIM : [2] Write success IPA -> E : [3] Deliver the eIM message to the eUICC E -> E : [4] Process the eIM message E -> IPA : [5] Deliver the eIM message processing result to the IPA IPA -> EIM : [6] Send IPA message /x/0/3 EIM -> IPA : [7] Send success @enduml

Figure 31 Transferring messages between eIM and IPA (LwM2M)

Start Conditions:

The LwM2M client in IPA is registered to the LwM2M server in eIM and secure connection between the client and the server is established.

Procedure:

1. The eIM sends Write request with the eIM message in resource /x/0/2 2. The IPA confirms delivery of the Write request

3.   The IPA provides to the eUICC the message from eIM with provided parameters.
4.   The eUICC processes the eIM message.
5.   The eUICC returns the result of message processing to the IPA.
6.   The IPA uses the Send request to deliver the IPA message in resource /x/0/3
7.   The eIM confirms delivery of the Send message and the content of resource x/0/3 is
     cleared in the IPA

B.2 MQTT

In case of an MQTT implementation of the ESipa, it is expected that the eIM is a component that is integrated into a device management platform and the IPA is a component that is part of the device management client functionality in the IoT Device. For efficient message transfer MQTT v5.0 [23] or higher is RECOMMENDED.

NOTE:MQTT is running over TCP.

B.2.1 Mapping of MQTT Roles

Both the entity hosting the eIM and the IoT Device implementing the IPA will act as clients of the MQTT broker and both will be able to publish and subscribe to topics.

For the IPA to connect to the MQTT broker, the FQDN of the MQTT broker is used and configured in the eimFqdn within the EimConfigurationData.

B.2.2 Secure connection

The security of the MQTTs connection between involved entities (i.e. IPA and eIM) and the MQTT broker has to be ensured by using TLS transport security with certificate authentication. The security of the MQTT application level uses the same certificate for authenticating the client to the MQTT broker. MQTT broker uses port 8883 as default MQTT secure port.

NOTE:MQTT v5.0 [23] uses TLS 1.2 as defined in RFC 5246 [8].

B.2.3 Description

The following topics are proposed to handle the ESipa implementation in MQTT. The topics are focused on transferring eIM Packages and eIM Package Results between eIM and IPA and direct Profile download is assumed.

Name              Topic                   Description
eIM message                               Topic used by the eIM to publish an
                  eim-to-ipa/{eid}
                                          EsipaMessageFromEimToIpa to an IoT Device
IPA message                               Topic used by the IPA to publish an
                  ipa-to-eim
                                          EsipaMessageFromIpaToEim to the eIM

Table 29 eIM and IPA Message

eIM Message

Publisher: eIM

Subscriber: IPA of the matching eID

Usage: This topic is used by the eIM to publish the requests to the IPA. The IPA will be subscribed and receive all the requests in order to process them.

Topic: eim- to-ipa/{eid}

Parameter                          Type       Description
EsipaMessageFromEimToIpa                      EsipaMessageFromEimToIpa following the ASN.1
                                   Binary
                                              structure as described in section 6.3.1.

Table 30 EsipaMessageFromEimToIpa

IPA message

Publisher: IPA

Subscriber: eIM

Usage: This topic is used by the IPA to publish the responses to the eIM requests. The eIM will be subscribed and receive all the responses from the processed requests.

Topic: ipa-to-eim

Parameter                      Type         Description
EsipaMessageFromIpaToEim                    EsipaMessageFromIpaToEim following the ASN.1
                               Binary
                                            structure as described in section 6.3.1.

Table 31 EsipaMessageFromIpaToEim

B.2.4 Procedures

B.2.4.1 Connection

@startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid participant "<b>eIM" as EIM participant "<b>MQTT broker" as BROKER participant "<b>IPA" as IPA participant "<b>eUICC" as E rnote over EIM, BROKER : [1] [TLS session establishment] EIM -> BROKER: [2] Subscribe to ipa-to-eim

rnote over IPA : [IoT Device internal trigger (e.g., power on, reconnection, etc.)] alt IoT Device power on IPA -> E: [3] ES10b.GetEid activate E E --> IPA: eid deactivate E end rnote over IPA, BROKER : [4] [TLS session establishment] IPA -> BROKER: [5] Subscribe to eim-to-ipa/{eid} @enduml

Figure 32 Connection

1. Establish TLS session between the eIM and MQTT broker

2. eIM subscribes to the ipa-to-eim topic to be able to receive IPA responses

3. IPA reads the eUICC EID using ES10b.GetEid

4. TLS session is established between the IPA and the MQTT broker

5. IPA subscribes to the eim-to-ipa/{eid} to receive the eIM request

B.2.4.2 Communication (Retrieval)

@startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid

participant "<b>eIM" as EIM participant "<b>MQTT broker" as BROKER participant "<b>IPA" as IPA

rnote over IPA: [IoT Device internal trigger] rnote over EIM, IPA : [1] [Secure connection establishment] loop until GetEimPackageResponse is noEimPackageAvailable IPA -> BROKER : [2] Publish GetEimPackageRequest \n to topic ipa-to-eim BROKER --> EIM : [3] Message EIM -> EIM : [4] Fetch pending eIM Package(s) for the EID EIM -> BROKER : [5] Publish GetEimPackageResponse \n to topic eim-to-ipa/{eid} BROKER --> IPA : [6] Message rnote over IPA : [7] [Process the eIM Package] group If GetEimPackageResponse is not a noEimPackageAvailable

alt If GetEimPackageResponse is not a ProfileDownloadTriggerRequest IPA -> BROKER : [8] Publish ProvideEimPackageResultRequest \n to topic ipa-to-eim BROKER --> EIM : [9] Message EIM -> EIM : [10] Manage eIM Package queue EIM -> BROKER : [11] Publish ProvideEimPackageResultResponse \n to topic eim-to- ipa/{eid} BROKER --> IPA : [12] Message rnote over IPA : [13] [Process the eimAcknowledgements if any] else Otherwise IPA -> BROKER : [14] Publish HandleNotificationEsipa \n to topic ipa-to-eim BROKER --> EIM : [15] Message EIM -> EIM : [16] Manage eIM Package queue EIM -> BROKER : [17] Publish ProvideEimPackageResultResponse \n to topic eim-to- ipa/{eid} BROKER --> IPA : [18] Message rnote over IPA : [19] [Process the eimAcknowledgements] end end end @enduml

Figure 33 Communication (Retrival)

1. Secure connection is established.

2. IPA publishes GetEimPackageRequest to topic ipa-to-eim.

3. Message is transferred to eIM.

4. eIM fetches the pending eIM Package(s) for the received EID.

5. eIM publishes the GetEimPackageResponse to topic eim-to-ipa/{eid}.

6. Message is transferred to the IPA.

7. The IPA processes the eIM Package by forwarding it to the eUICC.The eUICC
   processes the request and prepares the eIM Package Result and sends the result to
   the IPA.
8. If the GetEimPackageResponse is a ProfileDownloadTriggerRequest, the procedure
   continues in step 14, otherwise the IPA publishes the ProvideEimPackageResult in
   ipa-to-eim.

9. Message is transferred to the eIM

10. eIM manages the eIM Package queue.

11. The eIM publishes ProvideEimPackageResultResponse to eim-to-ipa/{eid}.

12. Message is sent to the IPA.

13. The IPA processes the eimAcknowledgements (if any).

14. The IPA publishes HandleNotificationEsipa.

15. Message is transferred to the eIM.

16. The eIM manages the eIM Package queue.

17. the eIM publishes ProvideEimPackageResultResponse to topic eim-to-ipa/{eid}.

18. Message is transferred to the IPA.

19. The IPA processes the eimAcknowledgement.

B.2.4.3 Communication (Injection)

@startuml hide footbox skinparam sequenceMessageAlign center skinparam sequenceArrowFontSize 11 skinparam noteFontSize 11 skinparam monochrome true skinparam lifelinestrategy solid participant "<b>eIM" as EIM participant "<b>MQTT broker" as BROKER participant "<b>IPA" as IPA participant "<b>eUICC" as E EIM->BROKER: [1]Publish TransferEimPackageRequest \n to topic eim-to-ipa/{eid} BROKER-->IPA: [2] Message IPA->E: [3] Received request E->E: [4] Process request E-->IPA: [5] Response IPA->BROKER: [6] Publish TransferEimPackageResponse \n to topic ipa-to-eim BROKER-->EIM: [7] Message @enduml

Figure 34 Communication (injection)

1. eIM publishes TransferEimPackageRequest to topic ipa-to-ipa/{eid}.

2. Message is transferred to the IPA.

3. The IPA forwards the received request to the eUICC.

4. The eUICC processes the request and prepares the eIM Package Result.

5. The eUICC sends the response to the IPA.

6. The IPA publishes the TransferEimPackageResponse in ipa-to-eim.

7. Message is transferred to the eIM.

C ASN.1 Definitions (Normative)

-- 2.1.3   ASN.1

SGP32Definitions {joint-iso-itu-t(2) international-organizations(23) gsma(146) rsp(1) asn1modules(1) sgp32v1(31)} DEFINITIONS AUTOMATIC TAGS EXTENSIBILITY IMPLIED ::= BEGIN

IMPORTS Certificate, SubjectPublicKeyInfo FROM PKIX1Explicit88 {iso(1) identified-
organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-
pkix1-explicit(18)}
SubjectKeyIdentifier FROM PKIX1Implicit88 {iso(1) identified-organization(3) dod(6)
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-pkix1-implicit(19)}
CancelSessionReason,    ServerSigned1,   RspCapability,   Iccid,    TransactionId,
ProfileInfoListRequest,       RulesAuthorisationTable,  EUICCInfo1,    DeviceInfo,
VersionType, UICCCapability, PprIds, CertificationDataObject, Octet1, Octet16,
Octet32,          PrepareDownloadResponseOk,             PrepareDownloadResponseError,
AuthenticateResponseError,         CtxParams1,          ProfileInstallationResultData,
OtherSignedNotification,     EuiccSignPIR,      ErrorResult,     NotificationMetadata,
CancelSessionResponseOk,   SmdpSigned2,     BoundProfilePackage,    NotificationEvent,
VendorSpecificExtension,                DpProprietaryData,                 OperatorId,
NotificationConfigurationInformation,     ProfileClass,     IconType,    ProfileState,
OctetTo16 FROM RSPDefinitions {joint-iso-itu-t(2) international-organizations(23)
gsma(146) rsp(1) asn1modules(1) sgp22v2(2)};
-- 2.11.1.1      EuiccPackageRequest
EuiccPackageRequest ::= [81] SEQUENCE { -- Tag ' BF51', #SupportedForPsmoV1.0.0#
     euiccPackageSigned EuiccPackageSigned,
     eimSignature [APPLICATION 55] OCTET STRING -- Tag '5F37'
}
EuiccPackageSigned ::= SEQUENCE {
     eimId [0] UTF8String (SIZE(1..128)),
     eidValue [APPLICATION 26] Octet16, -- Tag '5A'
     counterValue [1] INTEGER,
     eimTransactionId [2] TransactionId OPTIONAL,
     euiccPackage EuiccPackage
}
EuiccPackage ::= CHOICE {
     psmoList SEQUENCE OF Psmo, -- #SupportedForPsmoV1.0.0#
     ecoList   SEQUENCE OF Eco -- #SupportedForEcoV1.0.0#
}
-- 2.11.1.1.1      eIM Configuration Data
  EimConfigurationData ::= SEQUENCE {
       eimId [0] UTF8String (SIZE(1..128)), -- eimId of eIM
       eimFqdn [1] UTF8String OPTIONAL, -- FQDN of eIM or intermediate server, if used
       eimIdType [2] EimIdType OPTIONAL,
       counterValue [3] INTEGER OPTIONAL, -- initial counterValue for the eIM
       associationToken [4] INTEGER OPTIONAL,
       eimPublicKeyData [5] CHOICE {
      eimPublicKey SubjectPublicKeyInfo, -- public key of eIM, used for eUICC Package
signature verification, where the encoding follows X.509 standard
      eimCertificate Certificate -- certificate of eIM, used for eUICC Package
signature verification, where the encoding follows X.509 standard
       } OPTIONAL,
       trustedPublicKeyDataTls [6] CHOICE {
       trustedEimPkTls SubjectPublicKeyInfo, -- public key of eIM, used for TLS or
DTLS, where the encoding follows X.509 standard
       trustedCertificateTls Certificate -- either the certificate of eIM, used for
(D)TLS, or the certificate of the CA, where the encoding follows X.509 standard
        } OPTIONAL,
       eimSupportedProtocol [7] EimSupportedProtocol OPTIONAL,
    euiccCiPKId [8] SubjectKeyIdentifier OPTIONAL,        --   CI   Public   Key   Identifier
supported on the eUICC for signature creation
    indirectProfileDownload[9] NULL OPTIONAL -- support of Indirect Profile download
with indicated EimSupportedProtocol
  }
  EimIdType ::= INTEGER {
       eimIdTypeOid(1),
       eimIdTypeFqdn(2),
       eimIdTypeProprietary(3)
  }
  EimSupportedProtocol ::= BIT STRING {
       eimRetrieveHttps(0),
       eimRetrieveCoaps(1),
       eimInjectHttps(2),
       eimInjectCoaps(3),
       eimProprietary(4)
  }
-- 2.11.1.1.2       eUICC Package Request Containing eCOs
Eco ::= CHOICE {
     addEim [8] EimConfigurationData, -- for eIM configuration data see 2.11.1
     deleteEim [9] SEQUENCE {eimId [0] UTF8String},
     updateEim [10] EimConfigurationData,
     listEim [11] SEQUENCE {}
}
-- 2.11.1.1.3       eUICC Package Request Containing PSMOs
Psmo ::= CHOICE {
     enable [3] SEQUENCE {
       iccid [APPLICATION 26] Iccid,
       rollbackFlag NULL OPTIONAL
     },
     disable [4] SEQUENCE {iccid [APPLICATION 26] Iccid},
     delete [5] SEQUENCE {iccid [APPLICATION 26] Iccid},
     listProfileInfo [45] ProfileInfoListRequest, -- Tag 'BF2D'
     getRAT [6] SEQUENCE {},
     configureImmediateEnable [7] SEQUENCE {
       immediateEnableFlag [0] NULL OPTIONAL,
         defaultSmdpOid [1] OBJECT IDENTIFIER OPTIONAL,
         defaultSmdpAddress [2] UTF8String OPTIONAL
     },
     setFallbackAttribute [8] SEQUENCE {iccid [APPLICATION 26] Iccid},
     unsetFallbackAttribute [9] SEQUENCE {},
     setDefaultDpAddress [101] SetDefaultDpAddressRequest -- Tag 'BF65'
}
-- 2.11.1.2       IpaEuiccDataRequest
  IpaEuiccDataRequest ::= [82] SEQUENCE { -- Tag BF52
       tagList    [APPLICATION 28] OCTET STRING, -- Tag '5C'
    euiccCiPKIdentifierToBeUsed OCTET STRING OPTIONAL, -- CI Public Key Identifier
(possibly truncated) supported on the eUICC for signature creation
       searchCriteriaNotification [1] CHOICE {
           seqNumber [0] INTEGER,
           profileManagementOperation [1] NotificationEvent
       } OPTIONAL,
       searchCriteriaEuiccPackageResult [2] CHOICE {
           seqNumber [0] INTEGER
       } OPTIONAL,
       eimTransactionId [3] TransactionId OPTIONAL -- Tag '82'
  }
-- 2.11.1.3       ProfileDownloadTriggerRequest
ProfileDownloadTriggerRequest ::= [84] SEQUENCE { -- Tag 'BF54'
     profileDownloadData [0] ProfileDownloadData OPTIONAL,
     eimTransactionId [2] TransactionId OPTIONAL
}
ProfileDownloadData ::= CHOICE {
     activationCode [0] UTF8String (SIZE(0..255)),
     contactDefaultSmdp [1] NULL,
     contactSmds [2] SEQUENCE {
         smdsAddress UTF8String OPTIONAL
     }
}
-- 2.11.1.4       EimAcknowledgements

EimAcknowledgements ::= [83] SEQUENCE OF SequenceNumber -- Tag BF53 SequenceNumber ::= [0] INTEGER

-- 2.11.2.1     EuiccPackageResult
EuiccPackageResult ::= [81] CHOICE { -- Tag 'BF51' #SupportedForPsmoV1.0.0#
     euiccPackageResultSigned EuiccPackageResultSigned,
     euiccPackageErrorSigned EuiccPackageErrorSigned,
     euiccPackageErrorUnsigned EuiccPackageErrorUnsigned
}
EuiccPackageResultSigned ::= SEQUENCE {
     euiccPackageResultDataSigned EuiccPackageResultDataSigned,
     euiccSignEPR [APPLICATION 55] OCTET STRING -- Tag '5F37'
}
EuiccPackageResultDataSigned ::= SEQUENCE { -- #SupportedForPsmoV1.0.0#
     eimId [0] UTF8String (SIZE(1..128)),
     counterValue [1] INTEGER,
     eimTransactionId[2] TransactionId OPTIONAL,
     seqNumber [3] INTEGER,
     euiccResult SEQUENCE OF EuiccResultData
}
EuiccResultData ::= CHOICE {
     enableResult [3] EnableProfileResult,
     disableResult [4] DisableProfileResult,
     deleteResult [5] DeleteProfileResult,
     listProfileInfoResult [45] ProfileInfoListResponse,
     getRATResult [6] RulesAuthorisationTable, -- see SGP.22
     configureImmediateEnableResult [7] ConfigureImmediateEnableResult,
     addEimResult [8] AddEimResult,
     deleteEimResult [9] DeleteEimResult,
     updateEimResult [10] UpdateEimResult,
     listEimResult [11] ListEimResult,
     rollbackResult [12] RollbackProfileResult,
     setFallbackAttributeResult [13] SetFallbackAttributeResult,
     unsetFallbackAttributeResult [14] UnsetFallbackAttributeResult,
     processingTerminated INTEGER {
       resultSizeOverflow(1),
       unknownOrDamagedCommand(2),
       interruption(3),
       undefinedError(127)
     },
     setDefaultDpAddressResult [101] SetDefaultDpAddressResponse
}
EuiccPackageErrorSigned ::= SEQUENCE {
     euiccPackageErrorDataSigned EuiccPackageErrorDataSigned,
     euiccSignEPE [APPLICATION 55] OCTET STRING -- Tag '5F37'
    }
    EuiccPackageErrorDataSigned ::= SEQUENCE {
        eimId [0] UTF8String (SIZE(1..128)),
        counterValue [1] INTEGER,
        eimTransactionId [2] TransactionId OPTIONAL,
        euiccPackageErrorCode EuiccPackageErrorCode
    }
    EuiccPackageErrorCode ::= INTEGER {
        invalidEid(3),
        replayError(4),
        counterValueOutOfRange(6),
        sizeOverflow(15),
        ecallActive(104),
        undefinedError(127)
}
EuiccPackageErrorUnsigned ::= SEQUENCE {
    eimId [0] UTF8String (SIZE(1..128)),
    eimTransactionId [2] TransactionId OPTIONAL,
    associationToken [4] INTEGER OPTIONAL
}
ConfigureImmediateEnableResult ::= INTEGER {
    ok(0),
    insufficientMemory(1),
    commandError(7),
    undefinedError(127)
}
EnableProfileResult ::= INTEGER {
    ok(0),
    iccidOrAidNotFound(1),
    profileNotInDisabledState(2),
    disallowedByPolicy(3),
    catBusy(5),
    rollbackNotAvailable(20),
    undefinedError(127)
}
DisableProfileResult ::= INTEGER {
    ok(0),
    iccidOrAidNotFound(1),
    profileNotInEnabledState(2),
    disallowedByPolicy(3),
    catBusy(5),
    undefinedError(127)
}
DeleteProfileResult ::= INTEGER {
     ok(0),
     iccidOrAidNotFound(1),
     profileNotInDisabledState(2),
     disallowedByPolicy(3),
     rollbackNotAvailable(20),
     returnFallbackProfile(21),
     undefinedError(127)
}
ProfileInfoListResponse ::= [45] CHOICE {
     profileInfoListOk SEQUENCE OF ProfileInfo, -- see SGP.22
     profileInfoListError ProfileInfoListError
}
ProfileInfoListError ::= INTEGER {
     incorrectInputValues(1),
     profileChangeOngoing (11),
     undefinedError(127)
}
RollbackProfileResult ::= INTEGER {
     ok(0),
     undefinedError(127)
}
SetFallbackAttributeResult ::= INTEGER {
     ok(0),
     iccidOrAidNotFound (1),
     fallbackNotAllowed (2),
     fallbackProfileEnabled (3),
     undefinedError (127)
}
UnsetFallbackAttributeResult ::= INTEGER {
     ok(0),
     noFallbackAttribute(2),
     fallbackProfileEnabled (3),
     commandError(7),
     undefinedError (127)
}
AddEimResult ::= CHOICE {
     associationToken [4] INTEGER,
     addEimResultCode INTEGER {
       ok(0),
       insufficientMemory(1),
       associatedEimAlreadyExists(2),
           ciPKUnknown(3),
           invalidAssociationToken(5),
           counterValueOutOfRange(6),
           commandError(7),
           undefinedError(127)
       }
  }
  DeleteEimResult ::= INTEGER {
       ok(0),
       eimNotFound(1),
       lastEimDeleted(2), -- no eIM Configuration Data available in eUICC,
       commandError(7),
       undefinedError(127)
  }
  UpdateEimResult ::= INTEGER {
       ok(0),
       eimNotFound (1),
       ciPKUnknown(3),
       counterValueOutOfRange(6),
       commandError(7),
       undefinedError(127)
  }
  ListEimResult ::= CHOICE {
       eimIdList SEQUENCE OF EimIdInfo,
       listEimError INTEGER {
           undefinedError(127)
       }
  }
  EimIdInfo ::= SEQUENCE {
       eimId [0] UTF8String (SIZE(1..128)),
    eimIdType      [2]   EimIdType   OPTIONAL   --   present   in   case   of   eimIdTypeOid   and
eimIdTypeFqdn
  }
-- 2.11.2.2       IpaEuiccDataResponse
IpaEuiccDataErrorCode ::= INTEGER {
     incorrectTagList (1),
     euiccCiPKIdNotFound(5),
     ecallActive(104),
     undefinedError(127)
}
IpaEuiccDataResponseError ::= SEQUENCE {
     eimTransactionId [0] TransactionId OPTIONAL,
     ipaEuiccDataErrorCode IpaEuiccDataErrorCode
}
IpaEuiccDataResponse ::= [82] CHOICE { -- Tag 'BF52'
     ipaEuiccData IpaEuiccData,
     ipaEuiccDataResponseError IpaEuiccDataResponseError
}

PendingNotificationList ::= SEQUENCE OF PendingNotification EuiccPackageResultList ::= SEQUENCE OF EuiccPackageResult

IpaEuiccData ::= SEQUENCE {
     notificationsList [0] PendingNotificationList OPTIONAL, -- Tag 'A0'
     defaultSmdpAddress [1] UTF8String OPTIONAL, -- Tag '81'
     euiccPackageResultList [2] EuiccPackageResultList OPTIONAL, -- Tag 'A2'
     euiccInfo1 [32] EUICCInfo1 OPTIONAL, -- Tag 'BF20'
     euiccInfo2 [34] EUICCInfo2 OPTIONAL, -- Tag 'BF22'
     rootSmdsAddress [3] UTF8String OPTIONAL, -- Tag '83'
     associationToken [4] INTEGER OPTIONAL, -- Tag '84'
     eumCertificate [5] Certificate OPTIONAL, -- Tag 'A5'
     euiccCertificate [6] Certificate OPTIONAL, -- Tag 'A6'
     eimTransactionId [7] TransactionId OPTIONAL, -- Tag '87'
     ipaCapabilities [8] IpaCapabilities OPTIONAL, -- Tag 'A8'
     deviceInfo [9] DeviceInfo OPTIONAL -- Tag 'A9'
}
-- 2.11.2.3         ProfileDownloadTriggerResult
ProfileDownloadTriggerResult ::= [84] SEQUENCE { -- tag 'BF54'
     eimTransactionId [2] TransactionId OPTIONAL,
     profileDownloadTriggerResultData CHOICE {
         profileInstallationResult [55] ProfileInstallationResult, -- see SGP.22 [4]
         profileDownloadError SEQUENCE {
             profileDownloadErrorReason [0] INTEGER {
               ecallActive (104),
               undefinedError(127)
             },
             errorResponse OCTET STRING OPTIONAL
         }
     }
}
-- 3.8.4        ISD-R Selection and IPAe Activation
ISDRProprietaryApplicationTemplateIoT ::= [PRIVATE 1] SEQUENCE { -- Tag 'E1'
     euiccConfiguration BIT STRING {
         ipaeSupported(0), -- IPA in the eUICC (IPAe) supported
         enabledProfile(1) -- eUICC contains an Enabled Profile
     }
}
IpaeActivationRequest ::= [66] SEQUENCE { -- Tag 'BF42'
     ipaeOption BIT STRING {
         activateIpae(0) -- IPAe activation
     }
}
IpaeActivationResponse ::= [66] SEQUENCE { -- Tag 'BF42'
     ipaeActivationResult INTEGER {ok(0), notSupported(1)}
}
-- 4.1       IPA Capabilities
IpaCapabilities ::= SEQUENCE {
     ipaFeatures [0] BIT STRING {
     directRspServerCommunication (0),
     indirectRspServerCommunication (1),
     eimDownloadDataHandling (2),
     eimCtxParams1Generation (3),
     eimProfileMetadataVerification (4),
     minimizeEsipaBytes (5)
     },
     ipaSupportedProtocols [1] BIT STRING {
         ipaRetrieveHttps(0),
         ipaRetrieveCoaps(1),
         ipaInjectHttps(2),
         ipaInjectCoaps(3),
         ipaProprietary(4)
     } OPTIONAL
}

-- 4.4 Profile MetaData

-- Definition of ProfileInfo

  ProfileInfo ::= [PRIVATE 3] SEQUENCE { -- Tag 'E3'
       iccid Iccid OPTIONAL,
    isdpAid [APPLICATION 15] OctetTo16 OPTIONAL, -- AID of the ISD-P containing the
Profile, tag '4F'
       profileState [112] ProfileState OPTIONAL, -- Tag '9F70'
       profileNickname [16] UTF8String (SIZE(0..64)) OPTIONAL, -- Tag '90'
       serviceProviderName [17] UTF8String (SIZE(0..32)) OPTIONAL, -- Tag '91'
       profileName [18] UTF8String (SIZE(0..64)) OPTIONAL, -- Tag '92'
       iconType [19] IconType OPTIONAL, -- Tag '93'
    icon [20] OCTET STRING (SIZE(0..1024)) OPTIONAL, -- Tag '94', see condition in
ES10b:GetProfilesInfo
       profileClass [21] ProfileClass OPTIONAL, -- Tag '95'
    notificationConfigurationInfo            [22]                  SEQUENCE            OF
NotificationConfigurationInformation OPTIONAL, -- Tag 'B6'
       profileOwner [23] OperatorId OPTIONAL, -- Tag 'B7'
       dpProprietaryData [24] DpProprietaryData OPTIONAL, -- Tag 'B8'
       profilePolicyRules [25] PprIds OPTIONAL, -- Tag '99'
    serviceSpecificDataStoredInEuicc [34] VendorSpecificExtension OPTIONAL, -- Tag
'BF22'
       ecallIndication [123] BOOLEAN OPTIONAL, -- Tag '9F7B'
    fallbackAttribute [38] BOOLEAN DEFAULT FALSE, -- Tag '9F26', indicates a Fallback
Profile if set to TRUE
    fallbackAllowed [103] BOOLEAN OPTIONAL -- Tag '9F67', indicates if Fallback is
authorized by the Profile Owner
  }

-- 5.5 ES8+ beetween SM-DP+ and eUICC

  StoreMetadataRequest ::= [37] SEQUENCE { -- Tag 'BF25'
       iccid Iccid,
       serviceProviderName [17] UTF8String (SIZE(0..32)), -- Tag '91'
    profileName [18] UTF8String (SIZE(0..64)), -- Tag '92' (corresponds to 'Short
Description' defined in SGP.21 [2])
       iconType [19] IconType OPTIONAL, -- Tag '93' (JPG or PNG)
    icon [20] OCTET STRING (SIZE(0..1024)) OPTIONAL, -- Tag '94' (Data of the icon.
Size 64 x 64 pixel. This field SHALL only be present if iconType is present)
       profileClass [21] ProfileClass DEFAULT operational, -- Tag '95'
    notificationConfigurationInfo            [22]                  SEQUENCE            OF
NotificationConfigurationInformation OPTIONAL,
       profileOwner [23] OperatorId OPTIONAL, -- Tag 'B7'
       profilePolicyRules [25] PprIds OPTIONAL, -- Tag '99'
    serviceSpecificDataStoredInEuicc [34] VendorSpecificExtension OPTIONAL, -- Tag
'BF22'
    serviceSpecificDataNotStoredInEuicc [35] VendorSpecificExtension OPTIONAL, --
Tag ‘BF23’
       ecallIndication [123] BOOLEAN OPTIONAL, -- Tag '9F7B'
       fallbackAllowed [103] BOOLEAN OPTIONAL -- Tag '9F67'

}

-- 5.6.1 Function (ES9+): AuthenticateClient

  AuthenticateClientRequest ::= [59] SEQUENCE { -- Tag 'BF3B'
       transactionId [0] TransactionId,
    authenticateServerResponse [56] AuthenticateServerResponse          --    This   is   the
response from ES10b.AuthenticateServer
  }
-- 5.9.2     Function (ES10b): GetEUICCInfo
  EUICCInfo2 ::= [34] SEQUENCE { -- Tag 'BF22'
       profileVersion [1] VersionType, -- Base eUICC Profile package version supported
       svn [2] VersionType, -- GSMA SGP.22 version supported (SVN)referenced by SGP.32
       euiccFirmwareVer [3] VersionType, -- eUICC Firmware version
    extCardResource [4] OCTET STRING, -- Extended Card Resource Information according
to ETSI TS 102 226
       uiccCapability [5] UICCCapability,
       ts102241Version [6] VersionType OPTIONAL,
       globalplatformVersion [7] VersionType OPTIONAL,
       rspCapability [8] RspCapability,
    euiccCiPKIdListForVerification [9] SEQUENCE OF SubjectKeyIdentifier, -- List of
CI Public Key Identifiers supported on the eUICC for signature verification
    euiccCiPKIdListForSigning [10] SEQUENCE OF SubjectKeyIdentifier, -- List of CI
Public Key Identifier supported on the eUICC for signature creation
       euiccCategory [11] INTEGER {
         other(0),
         basicEuicc(1),
         mediumEuicc(2),
         contactlessEuicc(3)
       } OPTIONAL,
       forbiddenProfilePolicyRules [25] PprIds OPTIONAL, -- Tag '99'
       ppVersion VersionType, -- Protection Profile version
       sasAcreditationNumber UTF8String (SIZE(0..64)),
       certificationDataObject [12] CertificationDataObject OPTIONAL,
       treProperties [13] BIT STRING {
         isDiscrete(0),
         isIntegrated(1),
      usesRemoteMemory(2) -- refers to the usage of remote memory protected by the
Remote Memory Protection Function described in SGP.21 [4]
       } OPTIONAL,
    treProductReference [14] UTF8String OPTIONAL, -- Platform_Label as defined in
GlobalPlatform DLOA specification [57]
       additionalEuiccProfilePackageVersions [15] SEQUENCE OF VersionType OPTIONAL,
       ipaMode [16] IpaMode OPTIONAL, -- active IPA, mandatory within SGP.32
    euiccCiPKIdListForSigningV3 [17] SEQUENCE OF SubjectKeyIdentifier OPTIONAL, --
not used by this version of SGP.32.
    additionalEuiccInfo [18] OCTET STRING (SIZE(0..32)) OPTIONAL,      --    not   used   by
this version of SGP.32
       highestSvn [19] VersionType OPTIONAL, -- not used by this version of SGP.32
       iotSpecificInfo [20] IoTSpecificInfo OPTIONAL -- mandatory within SGP.32
  }
  -- Definition of IoTSpecificInfo
  IoTSpecificInfo ::= SEQUENCE {
    iotVersion [0] SEQUENCE OF VersionType, -- SGP.32 version(s) supported by the
eUICC, at least one must be present
    ecallSupported [1] NULL OPTIONAL, -- if present, eUICC supports the Emergency
Mechanism
    fallbackSupported [2] NULL OPTIONAL -- if present, eUICC supports the Fallback
Mechanism
  }
-- Definition of IpaMode
IpaMode ::= INTEGER {
     ipad (0), -- IPAd is active
     ipae (1) -- IPAe is active
}
-- 5.9.4       Function (ES10b): AddInitialEim
AddInitialEimRequest ::= [87] SEQUENCE { -- Tag 'BF57'
     eimConfigurationDataList [0] SEQUENCE OF EimConfigurationData
}
AddInitialEimResponse ::= [87] CHOICE { -- Tag 'BF57'
     addInitialEimOk SEQUENCE OF CHOICE {
         associationToken [4] INTEGER,
         addOk NULL
     },
     addInitialEimError INTEGER {
          insufficientMemory(1),
         associatedEimAlreadyExists (2),
         ciPKUnknown(3),
         invalidAssociationToken(5),
         counterValueOutOfRange(6),
         commandError(7),
         undefinedError(127)
     }

}

-- 5.9.5       Function (ES10b): eUICCMemoryReset
EuiccMemoryResetRequest ::= [100] SEQUENCE { -- Tag 'BF64'
     resetOptions [2] BIT STRING {
         deleteOperationalProfiles(0),
         deleteFieldLoadedTestProfiles(1),
         resetDefaultSmdpAddress(2),
         deletePreLoadedTestProfiles(3),
         deleteProvisioningProfiles(4),
         resetEimConfigData(5),
         resetImmediateEnableConfig (6)
     }
}
  EuiccMemoryResetResponse ::= [100] SEQUENCE { -- Tag 'BF64'
    resetResult INTEGER {ok(0), nothingToDelete(1), catBusy(5), ecallActive(104),
undefinedError(127)},
    resetEimResult INTEGER {ok(0),           nothingToDelete(1),   eimResetNotSupported(2),
undefinedError(127)} OPTIONAL,
    resetImmediateEnableConfigResult         INTEGER   {ok(0),   resetIECNotSupported   (1),
undefinedError(127)} OPTIONAL
  }
-- 5.9.10       Function (ES10b): GetCerts
  GetCertsRequest ::= [86] SEQUENCE { -- Tag 'BF56'
    euiccCiPKId SubjectKeyIdentifier OPTIONAL -- CI Public Key Identifier supported
on the eUICC for signature creation
  }
GetCertsResponse ::= [86] CHOICE { -- Tag 'BF56'
     certs SEQUENCE {
         eumCertificate [5] Certificate, -- Tag 'A5'
         euiccCertificate [6] Certificate -- Tag 'A6'
     },
     getCertsError INTEGER {invalidCiPKId(1), undfinedError(127)}
}
-- 5.9.11       Function (ES10b): RetrieveNotificationsList
RetrieveNotificationsListRequest ::= [43] SEQUENCE { -- Tag 'BF2B'
     searchCriteria CHOICE {
         seqNumber [0] INTEGER,
         profileManagementOperation [1] NotificationEvent,
         euiccPackageResults [2] NULL
     } OPTIONAL
}
RetrieveNotificationsListResponse ::= [43] CHOICE { -- Tag 'BF2B'
     notificationList PendingNotificationList, -- Tag 'A0'
     notificationsListResultError INTEGER { undefinedError(127)}, -- Tag '81'
     euiccPackageResultList EuiccPackageResultList -- Tag 'A2'
}
-- 5.9.15         Function (ES10b): ImmediateEnable
ImmediateEnableRequest ::= [90] SEQUENCE { -- Tag 'BF5A'
     refreshFlag BOOLEAN -- indicating whether REFRESH is required
}
ImmediateEnableResponse ::= [90] SEQUENCE { -- Tag 'BF5A'
     immediateEnableResult [0] INTEGER {
         ok(0),
         immediateEnableNotAvailable (1),
         noSessionContext(4),
         catBusy(5),
         undefinedError(127)
     }
}
-- 5.9.16         Function (ES10b): ProfileRollback
ProfileRollbackRequest ::= [88] SEQUENCE { -- Tag 'BF58'
     refreshFlag BOOLEAN -- indicating whether REFRESH is required
}
ProfileRollbackResponse ::= [88] SEQUENCE { -- Tag 'BF58'
     cmdResult INTEGER {
         ok(0),
         rollbackNotAllowed(1), -- Usage of rollback was not granted by the eIM
         catBusy(5),
         commandError(7),
         undefinedError(127)
     },
     eUICCPackageResult [81] EuiccPackageResult OPTIONAL

}

-- 5.9.17         Function (ES10b): ConfigureImmediateProfileEnabling
ConfigureImmediateProfileEnablingRequest ::= [89] SEQUENCE { -- Tag 'BF59'
     immediateEnableFlag [0] NULL OPTIONAL,
     defaultSmdpOid [1] OBJECT IDENTIFIER OPTIONAL,
     defaultSmdpAddress [2] UTF8String OPTIONAL
}
ConfigureImmediateProfileEnablingResponse ::= [89] SEQUENCE { -- Tag 'BF59'
     configImmediateEnableResult [0] INTEGER {
         ok(0),
         insufficientMemory(1),
         associatedEimAlreadyExists(2),
         undefinedError(127)
     }
}
-- 5.9.18         Function (ES10b): GetEimConfigurationData
GetEimConfigurationDataRequest ::= [85] SEQUENCE { -- Tag 'BF55'
     searchCriteria CHOICE {
         eimId [0] UTF8String (SIZE(1..128))
     } OPTIONAL
}
GetEimConfigurationDataResponse ::= [85] SEQUENCE { -- Tag 'BF55'
     eimConfigurationDataList [0] SEQUENCE OF EimConfigurationData
}
-- 5.9.20         Function (ES10b): ExecuteFallbackMechanism
ExecuteFallbackMechanismRequest ::= [93] SEQUENCE { -- Tag ' BF5D'
     refreshFlag BOOLEAN -- indicating whether REFRESH is required
}
ExecuteFallbackMechanismResponse ::= [93] SEQUENCE { -- Tag ' BF5D'
     executeFallbackMechanismResult [0] INTEGER {
         ok(0),
         profileNotInDisabledState(2),
         catBusy(5),
         fallbackNotAvailable(6), -- Fallback Attribute not set
         commandError(7),
         ecallActive(104),
         undefinedError(127)
     }
}
-- 5.9.21         Function (ES10b): ReturnFromFallback
ReturnFromFallbackRequest ::= [94] SEQUENCE { -- Tag 'BF5E'
     refreshFlag BOOLEAN -- indicating whether REFRESH is required
}
ReturnFromFallbackResponse ::= [94] SEQUENCE { -- Tag 'BF5E'
     returnFromFallbackResult [0] INTEGER {
         ok(0),
         catBusy(5),
         fallbackNotAvailable(6), -- Fallback Attribute not set
         commandError(7),
         undefinedError(127)
     }
}

-- 5.9.22 Function (ES10b): EnableEmergencyProfile

EnableEmergencyProfileRequest ::= [91] SEQUENCE { -- Tag 'BF5B'
     refreshFlag BOOLEAN -- indicating whether REFRESH is required
}
EnableEmergencyProfileResponse ::= [91] SEQUENCE { -- Tag 'BF5B'
     enableEmergencyProfileResult [0] INTEGER {
         ok(0),
         profileNotInDisabledState(2),
         catBusy(5),
         ecallNotAvailable(8), -- Emergency Profile does not exist
         undefinedError(127)
     }
}

-- 5.9.23 Function (ES10b): DisableEmergencyProfile

DisableEmergencyProfileRequest ::= [92] SEQUENCE { -- Tag 'BF5C'
     refreshFlag BOOLEAN -- indicating whether REFRESH is required
}
DisableEmergencyProfileResponse ::= [92] SEQUENCE { -- Tag 'BF5C'
     disableEmergencyProfileResult [0] INTEGER {
         ok(0),
         profileNotInEnabledState(2),
         catBusy(5),
         undefinedError(127)
     }
}

-- 5.9.24 Function (ES10b): GetConnectivityParameters

GetConnectivityParametersRequest ::= [95] SEQUENCE { -- Tag 'BF5F' }

GetConnectivityParametersResponse ::= [95] CHOICE { -- Tag 'BF5F'
      connectivityParameters ConnectivityParameters,
      connectivityParametersError ConnectivityParametersError
}
ConnectivityParameters ::= SEQUENCE {
      httpParams [1] OCTET STRING OPTIONAL         -- Also used for CoAP
}
ConnectivityParametersError ::= INTEGER {
      parametersNotAvailable(1),
      undefinedError(127)
}
-- 5.9.25         Function (ES10b): SetDefaultDpAddress
SetDefaultDpAddressRequest ::= [101] SEQUENCE { -- Tag 'BF65'
     defaultDpAddress UTF8String -- Default SM-DP+ address as an FQDN
}
SetDefaultDpAddressResponse ::= [101] SEQUENCE { -- Tag 'BF65'
     setDefaultDpAddressResult INTEGER { ok (0), undefinedError (127)}
}
-- 5.14.2         Function: (ESipa) GetBoundProfilePackage
PrepareDownloadResponse ::= [33] CHOICE { -- Tag 'BF21'
     downloadResponseOk PrepareDownloadResponseOk,
       downloadResponseError PrepareDownloadResponseError,
       compactDownloadResponseOk CompactPrepareDownloadResponseOk
  }
  CompactPrepareDownloadResponseOk ::= SEQUENCE {
       compactEuiccSigned2 CompactEuiccSigned2, -- Compact version of EuiccSigned2
    euiccSignature2     [APPLICATION    55]   OCTET    STRING     --    tag    '5F37'    signature   on
EuiccSigned2
  }
  CompactEuiccSigned2 ::= SEQUENCE {
    euiccOtpk [APPLICATION 73] OCTET STRING OPTIONAL, -- otPK.EUICC.ECKA, tag '5F49'
euiccOtpk is always present except if bppEuiccOtpk was chosen by the eUICC
       hashCc Octet32 OPTIONAL -- Hash of confirmation code, if not received from eIM
  }
-- 5.14.3     Function: (Esipa) AuthenticateClient
  EuiccSigned1 ::= SEQUENCE {
       transactionId [0] TransactionId,
       serverAddress [3] UTF8String,
       serverChallenge [4] Octet16, -- The RSP Server Challenge
       euiccInfo2 [34] EUICCInfo2,
       ctxParams1 CtxParams1
  }
  AuthenticateResponseOk ::= SEQUENCE {
       euiccSigned1 EuiccSigned1,             -- Signed information
       euiccSignature1 [APPLICATION 55] OCTET STRING,           --EUICC_Sign1, tag 5F37
    euiccCertificate Certificate,             --      eUICC   Certificate        (CERT.EUICC.ECDSA)
signed by the EUM
    eumCertificate Certificate         -- EUM Certificate (CERT.EUM.ECDSA) signed by the
requested CI
  }
  AuthenticateServerResponse ::= [56] CHOICE { -- Tag 'BF38'
       authenticateResponseOk AuthenticateResponseOk,
       authenticateResponseError AuthenticateResponseError,
       compactAuthenticateResponseOk CompactAuthenticateResponseOk
  }
  CompactAuthenticateResponseOk ::= SEQUENCE {
       signedData CHOICE {
         euiccSigned1 EuiccSigned1,
         compactEuiccSigned1 [0] CompactEuiccSigned1 -- Compact version of EuiccSigned1
       },
    euiccSignature1     [APPLICATION    55]   OCTET     STRING,    --    tag    5F37     signature   on
EuiccSigned1
       euiccCertificate [1] Certificate OPTIONAL, -- eUICC Certificate (CERT.EUICC.ECDSA)
       eumCertificate [2] Certificate OPTIONAL -- EUM Certificate (CERT.EUM.ECDSA)
  }
  CompactEuiccSigned1 ::= SEQUENCE {
    extCardResource [4] OCTET STRING, -- Extended Card Resource Information according
to ETSI TS 102 226 extracted from euiccInfo2,
    ctxParams1 [2] CtxParams1 OPTIONAL -- ctxParams1 may be left out by IPA if eIM
ctxParams1 was received from the eIM
  }
-- 5.14.7       Function (ESipa): HandleNotification
  PendingNotification ::= CHOICE {
       profileInstallationResult [55] ProfileInstallationResult, -- tag 'BF37'
       otherSignedNotification OtherSignedNotification,
       compactProfileInstallationResult [0] CompactProfileInstallationResult,
       compactOtherSignedNotification [1] CompactOtherSignedNotification
  }
  ProfileInstallationResult ::= [55] SEQUENCE { -- Tag 'BF37'
       profileInstallationResultData [39] ProfileInstallationResultData,
       euiccSignPIR EuiccSignPIR
  }
  CompactProfileInstallationResult ::= SEQUENCE {
       compactProfileInstallationResultData [0] CompactProfileInstallationResultData,
       euiccSignPIR EuiccSignPIR
  }
  CompactProfileInstallationResultData ::= SEQUENCE {
       transactionId [0] TransactionId, -- The TransactionID generated by the SM-DP+
       seqNumber INTEGER,
       iccidPresent BOOLEAN DEFAULT TRUE,
       compactFinalResult [2] CHOICE {
           compactSuccessResult CompactSuccessResult,
           errorResult ErrorResult
       }
  }
  CompactSuccessResult ::= SEQUENCE {
       compactAid [APPLICATION 15] OCTET STRING (SIZE (2)), -- Byte 14 and 15 of ISD-P
AID
    simaResponse OCTET STRING OPTIONAL -- MUST be present if the simaResponse value
(EUICCResponse) is different from the 9-byte value ‘30 07 A0 05 30 03 80 01 00’
representing success
  }
  CompactOtherSignedNotification ::= SEQUENCE {
       tbsOtherNotification NotificationMetadata,
    euiccNotificationSignature [APPLICATION 55] OCTET STRING -- eUICC signature of
tbsOtherNotification, Tag '5F37'
  }
-- 5.14.8     Function (ESipa): CancelSession
  CancelSessionResponse ::= [65] CHOICE { -- Tag 'BF41'
       cancelSessionResponseOk CancelSessionResponseOk,
    cancelSessionResponseError                     INTEGER          {invalidTransactionId(5),
undefinedError(127)},
       compactCancelSessionResponseOk CompactCancelSessionResponseOk
  }
  CompactCancelSessionResponseOk ::= SEQUENCE {
    compactEuiccCancelSessionSigned         CompactEuiccCancelSessionSigned,      --   Compact
version of euiccCancelSessionSigned
    euiccCancelSessionSignature [APPLICATION 55] OCTET STRING -- tag 5F37 signature
on euiccCancelSessionSigned
  }
  CompactEuiccCancelSessionSigned ::= SEQUENCE {
       reason CancelSessionReason OPTIONAL
  }
-- 6.3.1     ASN.1 structures for ESipa messages between IPA and eIM
  EsipaMessageFromIpaToEim ::= CHOICE {
    initiateAuthenticationRequestEsipa [57] InitiateAuthenticationRequestEsipa, --
Tag 'BF39'
    authenticateClientRequestEsipa          [59]    AuthenticateClientRequestEsipa,    --   Tag
'BF3B'
    getBoundProfilePackageRequestEsipa [58] GetBoundProfilePackageRequestEsipa, --
Tag 'BF3A'
       cancelSessionRequestEsipa [65] CancelSessionRequestEsipa, -- Tag 'BF41'
       handleNotificationEsipa [61] HandleNotificationEsipa, -- Tag 'BF3D'
       transferEimPackageResponse [78] TransferEimPackageResponse, -- Tag 'BF4E'
       getEimPackageRequest [79] GetEimPackageRequest, -- Tag 'BF4F'
       provideEimPackageResult [80] ProvideEimPackageResult -- Tag 'BF50'
  }
  EsipaMessageFromEimToIpa ::= CHOICE {
    initiateAuthenticationResponseEsipa [57] InitiateAuthenticationResponseEsipa, -
- Tag 'BF39'
    authenticateClientResponseEsipa         [59]    AuthenticateClientResponseEsipa,   --   Tag
'BF3B'
    getBoundProfilePackageResponseEsipa [58] GetBoundProfilePackageResponseEsipa, -
- Tag 'BF3A'
       cancelSessionResponseEsipa [65] CancelSessionResponseEsipa, -- Tag 'BF41'
       transferEimPackageRequest [78] TransferEimPackageRequest, -- Tag 'BF4E'
       getEimPackageResponse [79] GetEimPackageResponse, -- Tag 'BF4F'
    provideEimPackageResultResponse         [80]     ProvideEimPackageResultResponse   --   Tag
'BF50'
  }

-- 6.3.2.1 ESipa.InitiateAuthentication

InitiateAuthenticationRequestEsipa ::= [57] SEQUENCE { -- Tag 'BF39'
     euiccChallenge [1] Octet16, -- random eUICC challenge
     smdpAddress [3] UTF8String OPTIONAL,
     euiccInfo1 EUICCInfo1 OPTIONAL,
     eimTransactionId [2] TransactionId OPTIONAL
}
  InitiateAuthenticationResponseEsipa ::= [57] CHOICE { -- Tag 'BF39'
       initiateAuthenticationOkEsipa InitiateAuthenticationOkEsipa,
       initiateAuthenticationErrorEsipa INTEGER {
           invalidDpAddress(1),
           euiccVersionNotSupportedByDp(2),
           ciPKIdNotSupported(3),
           smdpAddressMismatch(50),
           smdpOidMismatch(51),
           invalidEimTransactionId(52),
           undefinedError(127)
       }
  }
  InitiateAuthenticationOkEsipa ::= SEQUENCE {
    transactionId [0] TransactionId OPTIONAL, -- The TransactionID generated by the
SM-DP+
       serverSigned1 ServerSigned1, -- Signed information
       serverSignature1 [APPLICATION 55] OCTET STRING, -- Server Sign1, Tag '5F37'
    euiccCiPKIdentifierToBeUsed OCTET STRING, -- Key identifier (possibly truncated)
of the CI Public Key to be used as required by ES10b.AuthenticateServer
       serverCertificate Certificate,
       matchingId UTF8String OPTIONAL,
       ctxParams1 [2] CtxParams1 OPTIONAL
  }
-- 6.3.2.2       ESipa.AuthenticateClient
  AuthenticateClientRequestEsipa ::= [59] SEQUENCE { -- Tag 'BF3B'
       transactionId [0] TransactionId, -- The TransactionID generated by the SM-DP+/SM-
DS
    authenticateServerResponse [56] AuthenticateServerResponse --         This   is   the
response from ES10b.AuthenticateServer, possibly in compact format
  }
  AuthenticateClientResponseEsipa ::= [59] CHOICE { -- Tag 'BF3B'
       authenticateClientOkDPEsipa AuthenticateClientOkDPEsipa,
       authenticateClientOkDSEsipa AuthenticateClientOkDSEsipa,
       authenticateClientErrorEsipa INTEGER {
           eumCertificateInvalid(1),
           eumCertificateExpired(2),
           euiccCertificateInvalid(3),
           euiccCertificateExpired(4),
           euiccSignatureInvalid(5),
           matchingIdRefused(6),
           eidMismatch(7),
           noEligibleProfile(8),
           ciPKUnknown(9),
           invalidTransactionId(10),
           insufficientMemory(11),
           pprNotAllowed(50),
           eventIdUnknown(56),
           undefinedError(127)
       }
  }
  AuthenticateClientOkDPEsipa ::= SEQUENCE {
    transactionId [0] TransactionId OPTIONAL, -- The TransactionID generated by the
SM-DP+
       profileMetaData [37] StoreMetadataRequest OPTIONAL,
       smdpSigned2 SmdpSigned2, -- Signed information
       smdpSignature2 [APPLICATION 55] OCTET STRING, -- Tag '5F37'
       smdpCertificate Certificate, -- CERT.DPpb.ECDSA
       hashCc Octet32 OPTIONAL -- Hash of confirmation code
  }
  AuthenticateClientOkDSEsipa ::= SEQUENCE {
       transactionId [0] TransactionId, -- The TransactionID generated by the SM-DS
       profileDownloadTrigger [84] ProfileDownloadTriggerRequest OPTIONAL -- Tag 'BF54'
  }
-- 6.3.2.3       ESipa.GetBoundProfilePackage
  GetBoundProfilePackageRequestEsipa ::= [58] SEQUENCE { -- Tag 'BF3A'
       transactionId [0] TransactionId, -- The TransactionID generated by the SM-DP+
    prepareDownloadResponse [33] PrepareDownloadResponse -- This is the response from
ES10b.PrepareDownload, possibly in compact format
  }
  GetBoundProfilePackageResponseEsipa ::= [58] CHOICE { -- Tag 'BF3A'
       getBoundProfilePackageOkEsipa GetBoundProfilePackageOkEsipa,
       getBoundProfilePackageErrorEsipa INTEGER {
           euiccSignatureInvalid(1),
           confirmationCodeMissing(2),
           confirmationCodeRefused(3),
           confirmationCodeRetriesExceeded(4),
           bppRebindingRefused(5),
           downloadOrderExpired(6),
           profileMetadataMismatch(50),
           invalidTransactionId(95),
           undefinedError(127)
       }
  }
  GetBoundProfilePackageOkEsipa ::= SEQUENCE {
    transactionId [0] TransactionId OPTIONAL, -- The TransactionID generated by the
SM-DP+
       boundProfilePackage [54] BoundProfilePackage
  }
-- 6.3.2.4       ESipa.HandleNotification
  HandleNotificationEsipa ::= [61] CHOICE { -- Tag 'BF3D'
    pendingNotification [0] PendingNotification, -- A Notification to be delivered
to a Notification Receiver, possibly in compact format
     provideEimPackageResult [80] ProvideEimPackageResult -- Tag 'BF50'
}
-- 6.3.2.5       ESipa.CancelSession
  CancelSessionRequestEsipa ::= [65] SEQUENCE { -- Tag 'BF41'
       transactionId TransactionId, -- The TransactionID generated by the SM-DP+
    cancelSessionResponse CancelSessionResponse -- This is the response from ES10b.
CancelSession function, possibly in compact format
  }
  CancelSessionResponseEsipa ::= [65] CHOICE { -- Tag 'BF41'
       cancelSessionOk CancelSessionOk,
       cancelSessionError INTEGER {
           invalidTransactionId(1),
           euiccSignatureInvalid(2),
           undefinedError(127)
       }
  }
  CancelSessionOk ::= SEQUENCE { -- This function has no output data
  }
-- 6.3.2.6       ESipa.GetEimPackage
  StateChangeCause ::= INTEGER {
       otherEim(0), -- for change(s) requested by another registered eIM
       fallback(1), -- for change(s) following fallback requested by IPA
    emergencyProfile(2), -- for change(s) following Emergency Profile swap requested
by IPA
       local(3), -- for change(s) applied locally (RFU, not supported in this version)
       reset(4), -- for change(s) following an euicc reset
    immediateEnableProfile(5), -- for change(s) following immediate Profile enabling
requested by IPA
    deviceChange(6), -- for change(s) detected by IPAe following a IoT Device change
(removable eSIMs)
       undefined(127)   -- unknown cause
  }
  GetEimPackageRequest ::= [79] SEQUENCE { -- Tag 'BF4F'
       eidValue [APPLICATION 26] Octet16, -- Tag '5A'
    notifyStateChange [0] NULL OPTIONAL, -- Notification to the eIM that it should
update its information about the eUICC (e.g. list of profiles, profile states...)
    stateChangeCause [1] StateChangeCause OPTIONAL, -- Provide the cause of the
notified state change(s)
    rPLMN [2] OCTET STRING (SIZE(3)) OPTIONAL -- MCC and MNC of the last registered
PLMN, coded as defined in 3GPP TS 24.008 [22]
  }
  GetEimPackageResponse ::= [79] CHOICE { -- Tag 'BF4F'
       euiccPackageRequest [81] EuiccPackageRequest, -- Tag 'BF51'
       ipaEuiccDataRequest [82] IpaEuiccDataRequest, -- Tag 'BF52'
       profileDownloadTriggerRequest [84] ProfileDownloadTriggerRequest, -- Tag 'BF54'
       eimPackageError INTEGER {
           noEimPackageAvailable(1),
           eidNotFound(2),
           invalidEid(3),
           missingEid(4),
           undefinedError(127)
       }
  }
-- 6.3.2.7       ESipa.ProvideEimPackageResult
EimPackageResultErrorCode ::= INTEGER {
     invalidPackageFormat(1),
     unknownPackage(2),
     undefinedError(127)
}

EimPackageResultResponseError ::= SEQUENCE {

     eimTransactionId [0] TransactionId OPTIONAL,
     eimPackageResultErrorCode EimPackageResultErrorCode
}
EimPackageResult ::= CHOICE {
     euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
     ePRAndNotifications SEQUENCE {
       euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
       notificationList [0] PendingNotificationList -- Tag 'A0'
     },
     ipaEuiccDataResponse [82] IpaEuiccDataResponse, -- Tag 'BF52'
     profileDownloadTriggerResult [84] ProfileDownloadTriggerResult, -- Tag 'BF54'
     eimPackageResultErrorCode EimPackageResultErrorCode,
     eimPackageResultResponseError [0] EimPackageResultResponseError
}
ProvideEimPackageResult ::= [80] SEQUENCE { -- Tag 'BF50'
     eidValue [APPLICATION 26] Octet16 OPTIONAL, -- Tag '5A'
     eimPackageResult EimPackageResult
}
ProvideEimPackageResultResponse ::= [80] SEQUENCE { -- Tag 'BF50'
     eimAcknowledgements [83] EimAcknowledgements OPTIONAL -- Tag 'BF53'
}
-- 6.3.3.1     ESipa.TransferEimPackage
TransferEimPackageRequest ::= [78] CHOICE { -- Tag 'BF4E'
     euiccPackageRequest [81] EuiccPackageRequest, -- Tag 'BF51'
     ipaEuiccDataRequest [82] IpaEuiccDataRequest, -- Tag 'BF52'
     eimAcknowledgements [83] EimAcknowledgements, -- Tag 'BF53'
     profileDownloadTriggerRequest [84] ProfileDownloadTriggerRequest -- Tag 'BF54'
}
TransferEimPackageResponse ::= [78] CHOICE { -- Tag 'BF4E'
     euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
     ePRAndNotifications SEQUENCE {
       euiccPackageResult [81] EuiccPackageResult, -- Tag 'BF51'
       notificationList [0] PendingNotificationList   -- Tag 'A0'
     },
     ipaEuiccDataResponse [82] IpaEuiccDataResponse, -- Tag 'BF52'
     eimPackageReceived NULL,
     eimPackageError INTEGER {
       invalidPackageFormat(1),
        unknownPackage(2),
        undefinedError(127)
    }
}

END

D Tag allocation (Normative)

This annex lists the tags allocated to data objects that SHALL be used for the definition of
the eUICC functions.
Tag           Data name                                                                             Introduced
                                                                                                    in
'BF20'        EUICCInfo1                                                                            SGP.22
'BF21'        PrepareDownloadResponse                                                               SGP.22
'BF22'        EUICCInfo2                                                                            SGP.22
'BF25'        StoreMetadataRequest                                                                  SGP.22
'BF2B'        PendingNotificationsListRequest or PendingNotificationsListResponse                   SGP.22
'BF2D'        ProfileInfoListRequest or ProfileInfoListResponse                                     SGP.22
'BF5F'        EuiccMemoryResetRequest or EuiccMemoryResetResponse                                   SGP.32
'BF37'        ProfileInstallationResult                                                             SGP.22
'BF38'        AuthenticateServerResponse                                                            SGP.22
'BF39'        InitiateAuthenticationRequest or InitiateAuthenticationResponse                       SGP.22
              (InitiateAuthenticationRequestEsipa or InitiateAuthenticationResponseEsipa)           (SGP.32)
'BF3A'        GetBoundProfilePackageRequest or GetBoundProfilePackageResponse                       SGP.22
              (GetBoundProfilePackageRequestEsipa or GetBoundProfilePackageResponseEsipa)           (SGP.32)
'BF3B'        AuthenticateClientRequest or AuthenticateClientResponse                               SGP.22
              (AuthenticateClientRequestEsipa or AuthenticateClientResponseEsipa)                   (SGP.32)
'BF3D'        HandleNotification                                                                    SGP.22
              (HandleNotificationEsipa)                                                             (SGP.32)
'BF41'        CancelSessionRequest or CancelSessionResponse or CancelSessionRequestEs9 or           SGP.22
              CancelSessionResponseEs9
              (CancelSessionRequestEsipa or CancelSessionResponseEsipa)                             (SGP.32)
'BF4E'        TransferEimPackageRequest or TransferEimPackageResponse                               SGP.32
‘'BF4F'       GetEimPackageRequest or GetEimPackageResponse                                         SGP.32
'BF50'        ProvideEimPackageResult or ProvideEimPackageResponse                                  SGP.32
'BF51'        EuiccPackageRequest or EuiccPackageResult                                             SGP.32
'BF52'        IpaEuiccDataRequest or IpaEuiccDataResponse                                           SGP.32
'BF53'        EimAcknowledgements                                                                   SGP.32
'BF54'        ProfileDownloadTriggerRequest or ProfileDownloadTriggerResponse                       SGP.32
'BF55'        GetEimConfigurationDataRequest or GetEimConfigurationDataResponse                     SGP.32
Tag          Data name                                                                       Introduced
                                                                                             in
'BF56'       GetCertsRequest or GetCertsResponse                                             SGP.32
'BF57'       AddInitialEimRequest or AddInitialEimResponse                                   SGP.32
'BF58'       ProfileRollbackRequest or ProfileRollbackResponse                               SGP.32
'BF59'       ConfigureImmediateProfileEnablingRequest or                                     SGP.32
             ConfigureImmediateProfileEnablingResponse
'BF5A'       ImmediateEnableRequest or ImmediateEnableResponse                               SGP.32
'BF5B'       EnableEmergencyProfileRequest or EnableEmergencyProfileResponse                 SGP.32
'BF5C'       DisableEmergencyProfileRequest or DisableEmergencyProfileResponse               SGP.32
'BF5D'       ExecuteFallbackMechanismRequest or ExecuteFallbackMechanismResponse             SGP.32
'BF5E'       ReturnFromFallbackRequest or ReturnFromFallbackResponse                         SGP.32
'BF5F'       GetConnectivityParametersRequest or GetConnectivityParametersResponse           SGP.32
'BF60'       Reserved
to
'BF63'
'BF64'       EuiccMemoryResetRequest or EuiccMemoryResetResponse                             SGP.32
'BF65'       SetDefaultDpAddressRequest or SetDefaultDpAddressResponse                       SGP.32
'9F26'       fallbackAttribute                                                               SGP.32
'9F67'       fallbackAllowed                                                                 SGP.32
'9F7B'       ecallIndication                                                                 SGP.32

Table 32 Tag Allocation

E Document Management (Informative)

E.1 Document History

                                                                  Approval     Editor /
Version      Date                         CR
                                                                  Authority   Company
                      CR001R01 – Overview
                      CR002R01 – Scope
                      CR003R01 – Document Purpose
                      CR004R01 – Intended Audience
                      CR005R01 – Conventions
                      CR006R01 – General Architecture
                      CR007R00 – Roles
                      CR008R01 – Interfaces
                      CR0012R01 – eUICC Architecture diagram
                      CR0009R05 – eUICC Architecture
                      CR0010R03 - Security Overview
                      CR0014R00 - ESIMWG7_52_AP2 - LPA                           Gloria
     V1.0     26      within SGP.22 vs IPA within SGP.32                        Trujillo,
             May      CR0017R02 - Introduction of procedures        ISAG
                                                                                 GSMA
             2023
                      CR0018R01 – eUICC Initialisation                          (Editor)
                      CR0024R04 - ESipa procedure (1/2): eIM
                      Command Retrieval
                      CR0025R03 - ESipa procedure (2/2): eIM
                      Command Injection
                      CR0015R09 - Direct Profile Download
                      CR0026R01 - Add PSMO generic description
                      CR0030R01 - Implementation of ESipa
                      interface
                      CR0031R00 - Communication between EIM
                      and IPA
                      CR0034R02 – Add definition of PSMO
                      structures
                      CR0016R10 Indirect Profile Download
                      Procedure
                      CR0023R03 CR_PSMO enable procedure
                      CR0035R02 Add generic PSMO Package
                      download and execution
                      CR0037R00 Delete Event Registration
                      Editor’s notes
                      CR0038R00 Removal of some editor's notes
                      CR0040R00 Remove continueonfailure
                      CR0042R01 Add PSMO Functions
                      CR0045R01 - REFRESH Mandatory for IoT
                      Devices
                      CR0049R01 Introduction of the ES8+
                      Interface
                      CR0050R01 Introduction Certificate
                      Revocation
                      CR0051R01 Indirect Profile Download
                      functions
                      CR0011R07 – Esipa
                      CR0052R00 - Deletion of editor note in
                      section 2.4.1
                      CR0060R01 - Add eIM Package Description
                 CR0248R00 - Correction of Typo in Section
                 3.2.3.1 "Direct Profile Download"
                 CR0249R00 - List of status codes for
                 ESipa.GetEimPackage
                 CR0251R01 - Editorial modification to
                 mapping of procedures to LwM2M
                 CR0252R00 - Editorial change of Tag
                 number for IpaCapabilities in IpaEuiccDat
                 CR0253R02 - Correction to correlate
                 package requests and results
                 CR0254R01 - Editorial change to add Annex
                 ASN.1 Definitions (Normative)
                 CR0255R01 - Editorial change for ASN-1
                 imports
                 CR0256R01 - Clarify ES10 CancelSession
                 CR0258R01 - Correlate InitiateAuthentication
                 with ProfileDownloadTriggerRequest
                 CR0260R00 - Various minor editorials
                 CR0261R00 - Fix provideEimPackageResult
                 tag number in ESipa.HandleNotification
                 CR0262R01 Editorial changes to rename the
                 functions & procedures related to “Automatic    eSIMWG7
                 Profile Enabling”
                 CR0263R03 - Correction of Enable Profile
                 PSMO command                                                    Gloria
         26      CR0264R01 - Correction of Delete Profile                       Trujillo,
V1.1
        April    PSMO command                                                    GSMA
        2024                                                                    (Editor)
                 CR0265R00 - Editorial change Missing
                 ASN1START and ASN1STOP tags
                 CR0266R00 - Editorial change Add Missing
                 tag number in ESipa.HandleNotification
                 CR0268R01 - Clarification on Update Eim
                 CR0269R01 - Correction to eIM ID
                 CR0270R01 - Correction to Generic eUICC
                 Package download procedure
                 CR0274R01 - Keep RetrieveNotificationsList
                 function with empty argument compatible
                 with SGP.22
                 CR0275R00 Editorial fixing Add Eim
                 Transaction ID in ASN.1 binding of
                 Esipa.InitiateAuthentication
                 CR0277R01 - Add eIM Transaction ID in
                 ASN.1 binding of ESipa.InitiateAuthentication
                 CR0273R01 - Referencing EUICCInfo2 from
                 SGP32
                 CR0279R00 - Fix diagram to reflect changes
                 agreed in CR269R01
                 CR0280R00 - Add missing error field in
                 InitiateAuthenticationErrorEsipa
                 CR0281R01 - Fix ESipa.HandleNotification
                 function decription for
                 IndirectProfileDownload
CR0283R00 - Add missing parameters to
GetEimConfiguration
CR0284R00 - Error code for bad correlation
of eimTransactionId after
ProfileDownloadTriggerRequest
CR0287R00 - Clarification about default SM-
DP+ parameters for Immediate Profile
Enabling procedures
CR0288R00 - eUICCMemoryReset response
CR0290R01 - Clarify behaviour of IPAe in
Immediate Profile Enabling
CR0240R04 - Introduction of Profile Fallback
Mechanism
CR0271R03 - Correction of eUICC Memory
Reset function
CR0272R03 - Completion of eCall
Mechanism
CR0285R03 - Fix inconsistency in updateEim
description
CR0289R01 - eIM TLS/DTLS Certificate
(CERT.EIM.TLS)
CR0276R03 - Clarify the need of connectivity
of parameters for constrained devices
CR0294R03 - Add setDefaultDpAddress
function
CR0296R01 - Fix error code inconsistencies
for some eCO commands
CR0297R00 - Editorial change to fix
HandleNotifications tipo
CR0298R00 - Clarifying empty response of
ES10b.GetEimConfigurationData
CR0300R01 - eIM TLS/DTLS Certificate
format – update
CR0302R03 - Add command data to
emergency call function
CR0303R01 - Editorial corrections to
Fallback
CR0278R02 - optimisation of
EuiccPackageResult
CR0291R00 - Field-Test eUICC Clarification
CR0295R00 - Fix error code inconsistencies
for some PSMO commands
 CR0312R00 - Editorial changes ASN_1
definition fixes
CR0314R01 - Clarify triggering of Indirect
Profile Donwload
CR0257R09 - IPAe configuration
CR0292R04 - EuiccMemoryReset and
Provisioning Profiles
CR0301R01 - Correction to MQTT Broker
address
CR0304R02 - Rollback procedure update
CR0305R01 - Align enable and disable
PSMO with SGP.22
CR0306R01 -
ES10b.getEimConfigurationData update
CR0310R01 - Clarification of the use of the
IoTSpecificInfo data object
CR0313R01 - Support of SNI
CR0315R00 - Update of references
CR0316R00 - Correcting error in eUICC
Memory Reset
CR0317R01 - No space in eUICC with
deleted Notifications
CR0320R01 - Add Tag Allocation Annex
CR0321R01 - Editorial changes for some
SGP 32 tags
CR0323R01 - Clarify TransacationID in PIR
and HandleNotification addresses
CR0325R01 - Clarifications to Emergency
Profile handling
CR0326R03 - Miscellaneous corrections to
fallback mechanism
CR0327R01 - Resetting fallback
authorization upon ecall
CR0328R00 - Editorial changes to fix ASN-1
compilation issues
CR0293R07 - Support of JSON and ASN.1
bindings by Eim
CR0308R04 - Support of JSON and ASN.1
bindings by SM-DP+ and SM-DS
CR0307R02 -
ESipa.ProvideEimPackageResult request
update
CR0309R00 - Clarification of Delete Profile
procedure and Provisioning profiles
CR0318R02 - Clarification on generating
Notifications
CR0319R01 - Replace sessionAborted
reason code
CR0322R01 - Adding EID to
ESipa.ProvideEimPackageResult
CR0329R00 - Add reference RFC 6066
CR0330R00 - Editorial changes to ES9+’
HandleNotification
CR0331R00 - Clarification to Indirect Profile
Download and Instalation procedure
CR0333R02 - Extend use of default SM-DP+
to Indirect Profile Download
CR0334R04 - Clarifications on Emergency
Mechanism
CR0335R01 - Clarify that fallback functions
are optional to support
CR0338R01 - Clarification on Enable and
Disable PSMO procedure
CR0339R00 - Editorial changes to fix ASN-1
compilation issues
CR0340R01 - Introducing a flag for Fallback
Support into eUICCInfo2
CR0341R01 - SNI section updates
CR0343R00 - Correcting behavior in
ES10b.AuthenticateServer
CR0344R00 - GetEimPackage update
CR0345R00 - TLS certificate retrieval for
IPAd in constrained IoT Devices
CR0346R00 - Rollback notifications
CR0324R07 - Revision of Annex B.2
CR0332R03 - Clarify the conditions of using
delault SM-DP+
CR0348R01 - List Profile default tag list
CR0350R01 - Editorial changes to align
CR0338 and CR0334
CR0351R01 - Clarify Note 3 in
ESipa.InitiateAuthentication function
CR0353R01 - Clarify how the eIM verify
Profile metadata
CR0352R02 - Rename
euiccCiPKIdToBeUsed to avoid
incompatibility with with SGP.22
CR0354R00 - Fix Setting the Fallback
Attribute
CR0355R02 - Fix
ExecuteFallbackMechanism function
CR0356R00 - Fix EuiccPackageResult errors
in case of eCall
CR0357R00 - Editorial correction section
2.6.5
CR0358R00 - Clarification of REFRESH
handling in Enable and Disable Emergency
Profile
CR0359R01 - Corrections to ASN.1
CR0360R00 - Editorial changes to fix ASN-1
compilation issues
CR0361R01 - Correction to terminal
capability - option 1
CR0363R01 - Correction to eIM ID
CR0364R01 - Correction to notification
retrieval if searchCriteria is NULL
 CR0365R00 - Clarification of Fallback
procedure
CR0366R02 - Use of REFRESH in Enable
and Disable Emergency Profile
CR0367R01 - Clarification on character set
for JSON binding
CR0369R01 - Editorial fix
EuiccPackageResult errors in case of eCall
CR0368R01 Correction to
ES10b.PrepareDownload function handling
CR0370R01                           Clean-up
ESipa.AuthenticateClient function description
CR0371R00 Editorial Correction to Eim
CR0373R00 Editorial Correction to align
capitalisation of eimId
CR0374R01 Editorial change to Annex B.2
MQTT on topic usage
CR0375R00 Editorial Correction to eimId
formatting
CR0376R02 Change to correct ASN.1 for
IpaEuiccDataRequest & Response
CR0377R00 Yet another         correction     to
TERMINAL CAPABILITY
CR0378R01 Reworking the tag numbers of
ES10b.EuiccMemoryReset
CR0379R00 Editorial to correct use of
eimPackageResponse
CR0381R01 Reworking the tag number of
ES10b.SetDefaultDpAddress function
CR0382R01 Correction of ASN.1 TAGs
CR0383R01 Add ecallActive error code to
euiccPackageResult
CR0384R00 Editorial correction to reason
metadataMismatch
CR0385R00 Add Event & EventID as per .22
in terms as used but undefined
CR0386R00 Add MatchingID as per .22 into
Terms as used but undefined
CR0387R00 Clean-up of Definition and
Abbreviation sections
CR0388R00 Add Event Retrieval definition
CR0390R01 Correction to Profile Download
Option (b)
CR0392R00 Add Activation Code Token to
Terms as used but undefined
CR0393R01     Remove       NOTE          from
GetEimPackage section 5.14.5
CR0395R00 Correction to storemetadata
request in relation to fallback
CR0396R00       Editorial   correction      for
GetProfilesInfo
CR0397R00 Editorial changes for ES10b
Enable    and   DisableEmergencyProfile
functions
CR0399R00 Complete section 5.2.1 Common
Data Types
CR0400R00 Editorial to make Profile Rollback
Procedure a new section
CR0402R01       Add     ecallActive         for
IPAEuiccDataRequest                        and
ProfileDownloadTriggerRequest
CR0403R01 Add indirect Profile Download
description to the eIM Cofiguration data
CR0404R00 Disable profile error conditions
simplification
CR0405R01 Editorial changes for 'Profile
MetaData' section
CR0408R01     Editorial   correction        for
ESipa.GetEimPackage function
CR0409R00 Alignment of error codes for
Enable/Disable/Delete Profile   PSMO
commands with SGP 22
CR0410R00       Add         refreshflag      to
ImmediateEnable
CR0411R01 Clarification about Notification
sending
CR0412R01 Clarification of ipaeActivation by
eUICC
CR0413R01 Clarification of the definition of
Connectivity Parameters
CR0414R00 Delete IpaEuiccDataErrorCode
from IpaEuiccDataResponse
CR0380R01 - Editorial correction to change
command to function
CR0389R00 - Editorial Add definition for
Event Deletion
CR0391R00 - Add missing ES11' function
calls & associated refs
CR0401R00 - Editorial to update
StoreMetadata in text to correct function
CR0415R00 - Renumber “ISD-R Selection
and IPAe Activation” section
CR0417R02- Split searchCriteria in
IpaEuiccDataRequest

CR0418R01 - ASN.1 RFU fields naming

CR0419R00 - Correction to
SetFallbackAttribute & Emergency Profile –
alternative
CR0420R00 - Fixing rework of the tag
numbers of ES10b.EuiccMemoryReset

CR0421R01 - invalidPackageFormat error

CR0422R00 - Cleaning error code for
EnableProfile PSMO command
CR0424R02 - Correction to tag number
overlaps with SGP.22 v3.1
CR0423R00 - Correction to
ImmediateEnable function

Other Information

Type                              Description
Document Owner                    eSIM Group
Editor / Company                  Gloria Trujillo, GSMA

It is our intention to provide a quality product for your use. If you find any errors or omissions, please contact us with your comments. You may notify us at [email protected]

Your comments or suggestions & questions are always welcome.

© GSM Association. Converted automatically from the published PDF; layout, figures and tables may differ from the original. The authoritative version is the original: https://www.gsma.com/solutions-and-impact/technologies/esim/wp-content/uploads/2024/04/SGP.32-v1.1.0.pdf.