hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.4 Minimum level of interoperability | Reference: ETSI TS 103 666-2 [10], clause 7.4. Req.ID Clause Description RQ0704_001 7.4 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 7 and its subclauses shall apply. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 32 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.5 Primary Platform identification | Reference: ETSI TS 103 666-2 [10], clause 7.5. Req.ID Clause Description RQ0705_001 7.5 The Primary Platform instance is identified by a Primary Platform identifier. The Primary Platform identifier is a sequence of 32 characters, divided in 8 groups of 4 characters each, with a dash between each group. RQ0705_002 7.5 The Primary Platform identifier shall not be changed irrespective of the Firmware update of the Secondary Platform Bundle Loader. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.6 Provisioning of Primary Platform software | Reference: ETSI TS 103 666-2 [10], clause 7.6. Req.ID Clause Description RQ0706_001 7.6 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.7 REQ85 shall apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.5.7 Part Number Identifier | Reference: ETSI TS 103 666-2 [10], clause 7.7. Req.ID Clause Description RQ0707_001 7.7 It shall be possible to retrieve the Primary Platform manufacturer, the model of the Primary Platform, the assurance level of the Primary Platform and the Secondary Platform Bundle Loader using the Part Number identifier. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.6 Primary Platform Interface | Reference: ETSI TS 103 666-2 [10], clause 8. Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 8.1 Kernel functions ABI/API | RQ0801_001 8.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.8.5 shall apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 8.2 Communication service interface | RQ0802_001 8.2 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.9 shall apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 8.3 Secondary Platform Bundle management service interface | RQ0803_001 8.3 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.10 and its subclauses shall apply with the exception that the states Active and Deleted as defined in clause 9.2 of ETSI TS 103 666-2 [10] are not relevant for this Secondary Platform Bundle management service interface. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.7 Secondary Platform Bundle | Reference: ETSI TS 103 666-2 [10], clause 9. Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 9.2 States | RQ0902_001 9.2 The states and transitions of the Secondary Platform Bundle container shall be as defined in GlobalPlatform VPP - Concepts and Interfaces [15], clause 5.10 and its subclauses. RQ0902_002 9.2 The state of the Secondary Platform Bundle instance shall be as defined in GlobalPlatform VPP - Concepts and Interfaces [15], clause 6.3. RQ0902_003 9.2 The Secondary Platform Bundle Loader manages the states of the Secondary Platform Bundle container, and not the states of the Secondary Platform Bundle instance. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 33 Release 15 Req.ID Clause Description RQ0902_004 9.2 The mechanism to make sure that the Secondary Platform Bundle Loader can disable an active Secondary Platform Bundle is the host arbitration process described in ETSI TS 103 666-1 [9], clause 8.2. RQ0902_005 9.2 The context of the Secondary Platform Bundle and of its applications is valid only in the Enabled and Active states. The context is created when the Secondary Platform Bundle moves to Active state for the first time. RQ0902_006 9.2 If the state of a Secondary Platform Bundle changes from Disabled to Enabled, upon the next state change to Active, the Secondary Platform Bundle shall erase its context and the context of its SSP Applications. RQ0902_007 9.2 No more than a single Secondary Platform Bundle shall be in an Active state. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 9.3 Secondary Platform Bundle container format | RQ0903_001 9.3 The provisions of GlobalPlatform VPP - Firmware Format [14] shall apply. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 9.4 Secondary Platform | 9.4.1 High Level OS RQ0904_001 9.4.1 The Secondary Platform Bundle contains a High Level OS as defined in GlobalPlatform VPP - Concepts and Interfaces [15], clause 6.4 and its subclauses. 9.4.2 Execution Framework RQ0904_002 9.4.2 The provisions of ETSI TS 103 666-1 [9], clause 5.4 shall apply. 9.4.3 UICC platform as a Secondary Platform RQ0904_003 9.4.3 The Secondary Platform may emulate a UICC platform as defined in ETSI TS 102 221 [4] and ETSI TS 102 223 [5]. In this case the Secondary Platform shall support the UICC APDU gate, as described in ETSI TS 103 666-1 [9], clause 10.2.8.2 and the UICC specific mechanisms defined in ETSI TS 103 666-1 [9], clauses 5.5, 6.6.1, 6.8.1, 6.10 and 10.2. 9.4.4 Capability exchange RQ0904_004 9.4.4 The data field sent by the terminal to the iSSP during the capability exchange procedure shall contain the data structure defined in ETSI TS 103 666-1 [9], clause 6.4.2.4, with the following modifications: • aPhysicalInterfaces in the TerminalCapability should not be present. RQ0904_005 9.4.4 The data field sent by the terminal to the iSSP during the capability exchange procedure shall contain the data structure defined in ETSI TS 103 666-1 [9], clause 6.4.2.4, with the following modifications: • aPhysicalInterfaces in the TerminalCapability shall be ignored if present. RQ0904_006 9.4.4 The data field sent by the iSSP to the terminal during the capability exchange procedure shall contains the data structure defined in ETSI TS 103 666-1 [9], clause 6.4.2.5, with the following modifications: • SSPClass field shall have the eSSPClass-Integrated (0) value. RQ0904_007 9.4.4 The data field sent by the iSSP to the terminal during the capability exchange procedure shall contains the data structure defined in ETSI TS 103 666-1 [9], clause 6.4.2.5, with the following modifications: • aClassSpecificCapabilities, aPhysicalInterfaces; and • aSspExternalMaxPowerConsumption in the SSPCapability should not be present. RQ0904_008 9.4.4 The data field sent by the iSSP to the terminal during the capability exchange procedure shall contains the data structure defined in ETSI TS 103 666-1 [9], clause 6.4.2.5, with the following modifications: • aClassSpecificCapabilities, aPhysicalInterfaces; and • aSspExternalMaxPowerConsumption in the SSPCapability shall be ignored if present. 9.4.5 Identifiers of Secondary Platform Bundle RQ0904_009 9.4.5 The Secondary Platform Bundle shall be provided with two identifiers: 1) The Secondary Platform Bundle identifier (i.e. SpbId), UUID which is the same as the public UUID of a firmware as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ0904_010 9.4.5 The Secondary Platform Bundle shall be provided with two identifiers: 2) The Secondary Platform Bundle private identifier (i.e. PrivateSpbId), UUID which is the same as the private UUID of a firmware as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]; where the NSS used to create the UUID shall have an entropy in its of at least 32 bytes. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 34 Release 15 Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 9.5 SSP Application | 9.5.2 Lifecycle management RQ0905_001 9.5.2 After the Secondary Platform Bundle has been loaded by the Secondary Platform Bundle Loader, the Secondary Platform Bundle and its SSP Applications are in their initial lifecycle state: • for a Secondary Platform Bundle supporting the legacy execution framework defined in ETSI TS 102 241 [7], the initial lifecycle state is determined by the Secondary Platform Bundle maker; • for a Secondary Platform Bundle supporting a native application, the initial lifecycle state is determined by the Secondary Platform Bundle maker; • for a Secondary Platform Bundle supporting a new type of execution framework, the initial lifecycle state is for future study. RQ0905_002 9.5.2 After the Secondary Platform Bundle has been enabled by the Secondary Platform Bundle Loader, the Secondary Platform Bundle internal lifecycle states and their management shall be governed by the following rules: • for a Secondary Platform Bundle supporting the legacy framework defined in ETSI TS 102 241 [7], the rules and mechanisms for the management of the lifecycle of the Security Domains and Applications shall be compliant with the GlobalPlatform Card Specification [12] and ETSI TS 102 226 [6]; • for a Secondary Platform Bundle supporting native SSP Applications, the rules and mechanisms for the management of the lifecycle state of the SSP application(s) are proprietary and out of the scope of the present document; • for a Secondary Platform Bundle supporting a new type of execution framework, the rules and mechanisms for the management of the lifecycle states of the SSP application(s) are for future study. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 9.6 Lifecycle management of Secondary Platform Bundles | RQ0906_001 9.6 The Secondary Platform Bundle Loader shall enforce that the number of Telecom Secondary Platform Bundles in the Enabled or Active state is not greater than the TELECOM_CAPABILITY parameter value defined in clause 7.3.1 of ETSI TS 103 666-2 [10]. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 9.7 Secondary Platform Bundle family identifier | RQ0907_001 9.7 A family of Secondary Platform Bundles is identified by a family identifier. A family identifier is a UUID computed from a URN using IETF RFC 4122 UUID version 5 [19]. It is equivalent to the Firmware Family in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.8 Communication interface | Reference: ETSI TS 103 666-2 [10], clause 10. Req.ID Clause Description 10.2 SSP Common Layer RQ1002_001 10.2 The iSSP shall support the SCL protocol layer, as defined in ETSI TS 103 666-1 [9], clause 8. RQ1002_002 10.2 The SCL router and the network controller host shall share the same security perimeter as the Primary Platform in order to ensure the correct mapping of host aliases with the corresponding SCL host. RQ1002_003 10.2 Each Secondary Platform Bundle is responsible for the implementation of the SCL protocol as needed for its operation. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 35 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.9 Certification | Reference: ETSI TS 103 666-2 [10], clause 11. Req.ID Clause Description 11.1 Introduction RQ1101_001 11.1 The iSSP shall be able to support a certification by composition of a Secondary Platform Bundle from the Primary Platform certification. 11.2 Primary Platform certification 11.2.1 Overview RQ1102_001 11.2.1 The provisions of GlobalPlatform VPP - Concepts and Interfaces [15], clause 4 shall apply. RQ1102_002 11.2.1 The certification of the Primary Platform shall include the Loader Package 2, as defined in BSI-CC-PP-0084-2014 [2]. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10 iSSP ecosystem and interfaces | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.1 Security overview | Reference: ETSI TS 103 666-2 [10], clause 12.2. Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.2.1 Public key infrastructure for Si4 interface | RQ1202_001 12.2.1.1.1.1 The Secondary Platform Bundle Loader certification path for digital signature shall include the following certificates: • CI certificate. • SSP maker certificate. • SPBL certificate: The SPBL certificate shall contain the public key used to verify the signature generated by the Secondary Platform Bundle Loader. RQ1202_002 12.2.1.1.1.1 The Secondary Platform Bundle Loader certification path may include the following certificates: • CI subordinate CA certificate: The CI subordinate CA certificate shall be issued by a CI. The CI subordinate CA certificate can be used to verify an SSP maker certificate. • SSP maker subordinate CA certificate: The SSP maker subordinate CA certificate shall be issued by an SSP maker. The SSP maker subordinate CA certificate can be used to verify an SPBL certificate. RQ1202_003 12.2.1.1.1.2 The SPBM certification path for digital signature shall include the following certificates: • CI certificate. • SPBM DS certificate: The SPBM DS certificate shall be used to verify the signature generated by the SPB Manager. RQ1202_004 12.2.1.1.1.2 The SPBM certification path for key agreement shall include the following certificates: • CI certificate. • SPBM KA certificate: The SPBM KA certificate shall be used to generate a session key for secure communication between the SPB Manager and the Secondary Platform Bundle Loader. RQ1202_005 12.2.1.1.1.2 The SPBM certification path for digital signature and key agreement may include the following certificates: • CI subordinate CA certificate: The CI subordinate CA certificate shall be issued by a CI. The CI subordinate CA certificate can be used to verify an SPBM Subordinate CA certificate. The CI subordinate CA certificate can be used to verify an SPBM DS certificate and SPBM KA certificate. • SPBM subordinate CA certificate: The SPBM subordinate CA certificate shall be issued by an SPBM or CI. The SPBM subordinate CA certificate can be used to verify an SPBM DS certificate and SPBM KA certificate. RQ1202_006 12.2.1.1.2.1 Basic certificate fields for all certificates used by the Secondary Platform Bundle Loader and the SPB Manager are identified in Table 12.2 of ETSI TS 103 666-2 [10] and follow the X.509 v3 certificate format as defined in IETF RFC 5280 [21]. RQ1202_007 12.2.1.1.2.2 The Authority key identifier (IETF RFC 5280 [21], section 4.2.1.1) is a considered extension field for Certificates: • All the certificate except for CI certificate shall contain the extension for authority key identifier. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 36 Release 15 Req.ID Clause Description RQ1202_008 12.2.1.1.2.2 The Subject key identifier (IETF RFC 5280 [21], section 4.2.1.2) is a considered extension field for Certificates: • All the certificate shall contain the extension for subject key identifier. The value of this field shall be the identifier of the public key contained in the certificate. RQ1202_009 12.2.1.1.2.2 The Key usage (IETF RFC 5280 [21], section 4.2.1.3) is a considered extension field for Certificates: • For a certificate used for verifying its subject certificate, keyCertSign (bit 5) shall be asserted to the key usage extension field of the certificate. • For the last certificate in the Secondary Platform Bundle Loader certification path for signature generation, digitalSignature (bit 0) shall be asserted to the key usage extension. • For the last certificate in the SPB Manager certification path for key agreement, key Agreement (bit 4) bit shall be asserted to the key usage extension. RQ1202_010 12.2.1.1.2.2 Certificate polices (IETF RFC 5280 [21], section 4.2.1.4) are a considered extension field for Certificates: • Each certificate shall have the appropriate value of the extension for certificate policies. • The OIDs used for value of the extension for certificate polices are defined as follows: − SubjectAltName (IETF RFC 5280 [21], section 4.2.1.6): A certificate may have the extension forsubjectAltName. − Basic constraints (IETF RFC 5280 [21], section 4.2.1.9): For any CA or subordinate CA certificate, the value of the extension for basic constraints shall be asserted. RQ1202_011 12.2.1.1.2.2 The following additional extension fields shall be present according to the following rules: • Primary Platform identifier: The Primary Platform identifier extension field shall only be contained in the SPBL certificate. RQ1202_012 12.2.1.1.2.2 The following additional extension fields shall be present according to the following rules: • The Primary Platform identifier extension field shall contain the Primary Platform identifier of the SSP. RQ1202_013 12.2.1.1.2.2 The following additional extension fields shall be present according to the following rules: • Family identifier: A certificate shall contain the family identifier extension field if it is present in its parent-certificate. If it is not present in the parent-certificate, a certificate may contain the family identifier extension field. The family identifier extension field shall indicate the list of family identifiers associated with the certification path to load a Secondary Platform Bundle image. If the family identifier extension field is present in the parent certificate, this list may contain the list or a subset of the list of family identifiers indicated in the family identifier extension field of the parent certificate. RQ1202_014 12.2.1.1.2.2 The following additional extension fields shall be present according to the following rules: • Custodian identifier: A certificate shall contain the custodian identifier extension field if it is present in its parent-certificate. If it is not present in the parent- certificate, a certificate may contain the custodian identifier extension field. The custodian identifier extension field shall indicate the list of OIDs of custodians associated with the certification path to load a Secondary Platform Bundle image. If the custodian identifier extension field is present in the parent certificate, this list may contain the list or a subset of the list of custodian identifiers indicated in the custodian identifier extension field of the parent certificate as defined in table 12.3 of ETSI TS 103 666-2 [10]. RQ1202_015 12.2.1.1.3 For 'subjectPublicKeyInfo' field, the following settings shall apply: • 'AlgorithmIdentifier.algorithm' field shall be set to: − if the value of 'Extension for KeyUsage' field is set to digitalSignature(0) and/or keyCertSign(5); − for Elliptic Curve Digital Signature Algorithm (ECDSA), "iso(1) member- body(2) us(840) ansi-X9-62(10045) keyType(2) ecPublicKey(1)" as defined in IETF RFC 5480 [22]. RQ1202_016 12.2.1.1.3 For 'subjectPublicKeyInfo' field, the following settings shall apply: • 'AlgorithmIdentifier.algorithm' field shall be set to: − if the value of 'Extension for KeyUsage' field is set to digitalSignature(0) and/or keyCertSign(5); − for SM2 digital signature algorithm, "iso(1) standard(0) digital-signature-with- appendix(14888) part3(3) algorithm(0) sm2(14)" as defined in ISO/IEC 14888-3 [29]. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 37 Release 15 Req.ID Clause Description RQ1202_017 12.2.1.1.3 For 'subjectPublicKeyInfo' field, the following settings shall apply: • 'AlgorithmIdentifier.algorithm' field shall be set to: − if the value of 'Extension for KeyUsage' field is set to keyAgreement(4): − for Elliptic Curve Diffie-Hellman (ECDH), "iso(1) identified-organization(3) certicom(132) schemes (1) ecdh(12)" as defined in IETF RFC 5480 [22]. RQ1202_018 12.2.1.1.3 For 'subjectPublicKeyInfo' field, the following settings shall apply: • '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 IETF RFC 5639 [23]. RQ1202_019 12.2.1.1.3 For 'subjectPublicKeyInfo' field, the following settings shall apply: • 'AlgorithmIdentifier.parameters' field shall be set to: − for BrainpoolP384r1: "iso(1) identified-organization(3) teletrust(36) algorithm(3) signatureAlgorithm(3) ecSign(2) ecStdCurvesAndGeneration(8) ellipticCurve(1) versionOne(1) brainpoolP384r1(11)" as defined in IETF RFC 5639 [23]. RQ1202_020 12.2.1.1.3 For 'subjectPublicKeyInfo' field, the following settings shall apply: • AlgorithmIdentifier.parameters' field shall be set to: − for NIST P-256: "iso(1) member-body(2) us(840) ansi-X-9-62(10045) curves(3) prime(1) secp256v1(7)" as defined in IETF RFC 5480 [22]. RQ1202_021 12.2.1.1.3 For 'subjectPublicKeyInfo' field, the following settings shall apply: • 'AlgorithmIdentifier.parameters' field shall be set to: − for NIST P-384: "iso(1) identified-organization(3) certicom(132) curve(0) secp384r1(34)" as defined in IETF RFC 5480 [22]. RQ1202_022 12.2.1.1.3 For 'signature' and 'signatureAlgorithm' fields, the following settings shall apply: • 'AlgorithmIdentifier.algorithm' field shall be set to: − for ECDSA-with-SHA256: "iso(1) member-body(2) us(840) ansi-X9- 62(10045) signatures(4) ecdsawith-SHA2(3) ecdsa-with-SHA256(2)" as defined in IETF RFC 5758 [25]. RQ1202_023 12.2.1.1.3 For 'signature' and 'signatureAlgorithm' fields, the following settings shall apply: • 'AlgorithmIdentifier.algorithm' field shall be set to: − for ECDSA-with-SHA384: "iso(1) member-body(2) us(840) ansi-X9- 62(10045) signatures(4) ecdsawith-SHA2(3) ecdsa-with-SHA384(3)" as defined in IETF RFC 5758 [25]. RQ1202_024 12.2.1.1.3 For 'signature' and 'signatureAlgorithm' fields, the following settings shall apply: • 'AlgorithmIdentifier.algorithm' field shall be set to: − for SM2 digital signature algorithm, "iso(1) standard(0) digital-signature-with- appendix(14888) part3(3) algorithm(0) sm2(14)" as defined in ISO/IEC 14888-3 [29]. RQ1202_025 12.2.1.1.3 For 'signature' and 'signatureAlgorithm' fields, the following settings shall apply: • 'AlgorithmIdentifier.parameters' field shall be set to: − for ECDSA-with-SHA256 and ECDSA-with-SHA384: the parameters field shall be omitted as defined in IETF RFC 5754 [24], section 3.2. RQ1202_026 12.2.1.1.4 Both the Secondary Platform Bundle Loader and the SPB Manager shall verify the certificate chain received by each other. RQ1202_027 12.2.1.1.4 A certificate chain to be verified shall satisfy the following conditions: • The value of Authority Key Identifier extension field in a subject's certificate shall be the same as the value of Subject Key Identifier extension field in the issuer's certificate which is used to verify the subject's certificate. • The value of issuer field in a subject's certificate shall be the same as the value of subject field in the issuer's certificate which is used to verify the subject's certificate. • All certificates in the certificate chain shall use the same digital signature algorithm and parameter set indicated by one of the algorithm Identifiers defined in clause 12.2.1.1.3 of ETSI TS 103 666-2 [10]. • All certificates in the certificate chain shall not have been expired. • All certificates in the certificate chain shall not have been revoked. The certificate revocation status shall be checked as defined in clause 12.2.1.1.5 of ETSI TS 103 666-2 [10]. RQ1202_028 12.2.1.1.4 The Secondary Platform Bundle Loader and the SPB Manager shall manage the trusted Public Key information to verify received certificate chain. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 38 Release 15 Req.ID Clause Description RQ1202_029 12.2.1.1.4 Each set of trusted public key information shall contain the following: • Public Key information (SubjectPublicKeyInfo as defined in IETF RFC 5280 [21]). • Subject Key Identifier of the Public Key. • Family identifier(s) associated with that Public Key, if any. • Custodian identifier(s) associated with that Public Key, if any. RQ1202_030 12.2.1.1.4 The Secondary Platform Bundle Loader and the SPB Manager shall verify the received certificate chain by using one set of trusted Public Key information as the trust anchor information for the certification path validation procedure defined in IETF RFC 5280 [21]. The trust anchor shall be determined during the download procedure as defined in clause 12.3.3 of ETSI TS 103 666-2 [10]. RQ1202_031 12.2.1.1.4 The Secondary Platform Bundle Loader and the SPB Manager shall: • Perform the certification path validation defined in IETF RFC 5280 [21] to verify the received certificate chain. • Verify that the received certificate chain follows one of the certificate chains as defined in clause 12.2.1.1.1 of ETSI TS 103 666-2 [10]. • Verify that all certificate(s) in the received certificate chain follow the corresponding certificate description(s) as defined in clause 12.2.1.1.2 of ETSI TS 103 666-2 [10]. RQ1202_032 12.2.1.1.4 In addition, the Secondary Platform Bundle Loader and the SPB Manager shall verify that the certificates in the received certificate chain satisfy the condition as described below: • If a certificate contains the list of family identifier(s) in the family identifier extension field, the list shall contain the family identifier associated with the trust anchor used for the certification path validation. • If a certificate contains the list of custodian identifier(s) in the custodian identifier extension field, the list shall contain the custodian identifier associated with the trust anchor used for the certification path validation. RQ1202_033 12.2.1.1.4 If any of the verifications described above fails, the certificate chain shall be considered as invalid. RQ1202_034 12.2.1.1.5 The Secondary Platform Bundle Loader and the SPB Manager may verify the revocation status of certificates in the received certification path by using a Certificate Revocation List (CRL) as defined in IETF RFC 5280 [21]. RQ1202_035 12.2.1.1.5 The SPB Manager may verify the revocation status of certificates in the received certification path by using a Certificate Revocation List (CRL) as defined in IETF RFC 5280 [21]. RQ1202_036 12.2.1.1.5 The SPB Manager may obtain a CRL by accessing a public repository with the uniform resource identifier indicated in cRLDistributionPoint extension of a certificate as defined in IETF RFC 5280 [21]. RQ1202_037 12.2.1.1.5 The Secondary Platform Bundle Loader may obtain a CRL with the following mechanism: • The SPB Manager may provide the list of the latest CRL for each certificate in its certification path along with the certification path. The Secondary Platform Bundle Loader shall verify the revocation status of the certificates with the corresponding CRLs provided by the SPB Manager. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.2.2 Cryptographic algorithms | RQ1202_038 12.2.2.1 The Secondary Platform Bundle Loader and the SPB Manager shall support at least one out of the following elliptic curve domain parameter sets: • NIST P-256 as defined in NIST 800-56A [31]. • NIST P-384 as defined in NIST 800-56A [31]. • brainpoolP256r1 as defined in IETF RFC 5639 [23]. • brainpoolP384r1 as defined in IETF RFC 5639 [23]. RQ1202_039 12.2.2.2 The Secondary Platform Bundle Loader and the SPB Manager shall support at least one of the following algorithms to generate and verify signatures: • Elliptic Curve Digital Signature Algorithm (ECDSA) as defined in ANSI X9.62-2005 [1]. RQ1202_040 12.2.2.2 The Secondary Platform Bundle Loader and the SPB Manager shall support at least one of the following algorithms to generate and verify signatures: • SM2 digital signature algorithm as defined in ISO/IEC 14888-3 [29]. The hash function shall be the SM3 hash function as defined in ISO/IEC 10118-3 [28]. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 39 Release 15 Req.ID Clause Description RQ1202_041 12.2.2.3 The Secondary Platform Bundle Loader and the SPB Manager shall support at least one of the following key agreement algorithms to establish session keys: • Elliptic Curve Key Agreement Algorithm (ECKA) as defined in BSI TR-03111 [3]. • SM2 Key exchange Algorithm (SM2KA) as defined in SM2 Digital Signature Algorithm [17], section 6.2. If ECKA is used as the key agreement algorithm, a shared secret shall be generated by using one between either the ElGamal key agreement protocol or the Diffie-Hellman key agreement protocol. The session key shall be computed from the generated shared secret value using the X9.63 key derivation function as described in GP Open Firmware Loader for Tamper Resistant Element [13], clause 3.2.1. RQ1202_042 12.2.2.4 The Secondary Platform Bundle Loader and the SPB Manager shall support at least one of the following block cipher algorithms to encrypt data: • eGCM based on AES-128 as defined in GP Open Firmware Loader for Tamper Resistant Element [13], Annex A. • eGCM based on AES-256 as defined in GP Open Firmware Loader for Tamper Resistant Element [13], Annex A. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.2 Secondary Platform Bundle provisioning procedure | Reference: ETSI TS 103 666-2 [10], clause 12.3. Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.3.1 Overview | RQ1203_001 12.3.1 The preparation procedure shall be performed between a Service Provider and an SPB Manager over the Si1 interface and a Service Provider and a Subscriber. The Subscriber is able to obtain from the service provider the relevant information for loading a Secondary Platform Bundle, including the URL of the SPB Manager to which the iSSP shall establish a secure communication channel to start the download procedure. RQ1203_002 12.3.1 The download procedure shall be performed between a Secondary Platform Bundle Loader and an SPB Manager over the Si2 and Si3 interfaces. The bound Secondary Platform Bundle image shall be delivered securely from the SPB Manager to the LBA through the download procedure. RQ1203_003 12.3.1 The installation procedure shall be performed between an LBA and a Secondary Platform Bundle Loader over the Si3 interface. The bound Secondary Platform Bundle image shall be delivered from the LBA to the Secondary Platform Bundle Loader through the installation procedure. The Secondary Platform Bundle Loader installs the Secondary Platform Bundle container by decrypting the bound Secondary Platform Bundle image. RQ1203_004 12.3.1 The notification procedure shall be performed between the Secondary Platform Bundle Loader and the SPB Manager over the Si1, Si2 and Si3 interfaces with either: • Case 1: the preparation procedure is completed before the download procedure is triggered. RQ1203_005 12.3.1 The notification procedure shall be performed between the Secondary Platform Bundle Loader and the SPB Manager over the Si1, Si2 and Si3 interfaces or: • Case 2: the preparation procedure is not completed before the download procedure is triggered, i.e. the service provider needs additional information from the terminal and/or the SSP to select the Secondary Platform Manager. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.3.2 Preparation procedure | RQ1203_006 12.3.2.1 The preparation procedure consists of the following two processes: • Secondary Platform Bundle selection process: the selection of the Secondary Platform Bundle allowing the service provider to select a Secondary Platform Bundle that matches the terminal and the SSP capabilities. • Service provider reference creation process: the creation of a reference shared between the service provider and the SPB Manager. This allows the end user to trigger the download procedure as defined in clause 12.3.3 of ETSI TS 103 666-2 [10]. The Secondary Platform Bundle selection process and the service provider reference creation process may be executed in any order or in once, according to the service provider's implementation choices. RQ1203_007 12.3.2.2 The selection of the Secondary Platform Bundle allows the service provider to select a Secondary Platform Bundle that matches the terminal and the SSP capabilities. This is performed using the "Si1.SelectSpb" function. This process may be executed regardless of the service provider reference creation process defined in clause 12.3.2.3 of ETSI TS 103 666-2 [10]. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 40 Release 15 Req.ID Clause Description RQ1203_008 12.3.2.2 If a CodeM is provided as input parameter of the "Si1.SelectSpb" function and is known by the SPB Manager and not already linked to another Secondary Platform Bundle, the service provider reference creation process is not needed. RQ1203_009 12.3.2.2 If the service provider has set aFlagFinalize to TRUE in the "Si1.SelectSpb" function command, the SPB Manager shall wait for the completion of the Secondary Platform Bundle selection process (i.e. after it has sent the response to the "Si1.FinalizePreparation" function related to this Secondary Platform Bundle) to continue with the Bound SPB image download as defined in clause 12.3.3.2 of ETSI TS 103 666-2 [10]. RQ1203_010 12.3.2.3 The service provider reference creation process shall be performed using the "Si1.CreateSPReference" function and may be executed regardless of the Secondary Platform Bundle selection process defined in clause 12.3.2.2 of ETSI TS 103 666-2 [10]. RQ1203_011 12.3.2.3 The service provider may pass the CodeM value to be used as a parameter of the "Si1.CreateSPReference" function command. If this is not present, the SPB Manager shall generate the CodeM. RQ1203_011 a 12.3.2.3 The service provider may pass the CodeM value to be used as a parameter of the "Si1.CreateSPReference" function command. RQ1203_011 b 12.3.2.3 If service provider is not passing over the CodeM value this is not present, the SPB Manager shall generate the CodeM. RQ1203_012 12.3.2.3 The service provider may pass the CodeM value to be used as a parameter of the "Si1.CancelPreparation" function command. This procedure allows the service provider to cancel a pending preparation procedure. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.3.3 Download procedure | RQ1203_013 12.3.3.1 The following shall be determined by the capability negotiation procedure: • SPBM certificate for key agreement and its certification path. • Public Key provisioned on the SPB Manager to verify the SPBL certificate and its certification path. • Data encryption algorithm used by the SPB Manager and the Secondary Platform Bundle Loader. RQ1203_014 12.3.3.1 The LBA shall obtain the address of the SPB Manager (spbmAddr) e.g. from the end user. RQ1203_015 12.3.3.1 The LBA may obtain the family identifier of the Secondary Platform Bundle container (spbFamilyId) to load. If the family identifier is present, the LBA may also obtain the OID of a custodian of that family identifier. The Secondary Platform Bundle Loader shall have the following: • Private key(s) for creating the Secondary Platform Bundle Loader signature. • Secondary Platform Bundle Loader certificate(s) for the digital signature used to verify the Secondary Platform Bundle Loader signature. • Secondary Platform Bundle Loader certificate chain(s) to be used by an SPB Manager for verifying Secondary Platform Bundle Loader certificate for digital signature. • Trusted public key(s) and algorithmIdentifier value(s) to be used to verify certificate(s) from an SPB Manager as per the family identifier(s) and/or custodian(s). • List of supported algorithmIdentifier value(s) for key agreement and data encryption. RQ1203_016 12.3.3.1 The SPB Manager shall have the following: • Private key(s) for creating the SPB Manager signature. • Private key(s) for key agreement. • SPB Manager certificate(s) for digital signature used to verify the SPB Manager signature. • SPB Manager certificate(s) for key agreement. • SPB Manager certificate chain(s) to be used by a Secondary Platform Bundle Loader for verifying the SPB Manager certificates for key agreement and for digital signature. • Trusted public key(s) and algorithmIdentifier value(s) to be used to verify the certificate(s) from the Secondary Platform Bundle Loader as per the family identifier(s) and/or custodian(s). RQ1203_017 12.3.3.1 The capability negotiation procedure shall use the following steps: 1) The LBA shall call the "Si3.GetSspInfo" function. The function command may contain the spbFamilyId. If spbFamilyId is present, the function command may also contain the OID of the custodian for this spbFamilyId. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 41 Release 15 Req.ID Clause Description RQ1203_018 12.3.3.1 The capability negotiation procedure shall use the following steps: 2) On reception of the "Si3.GetSspInfo" function command, the Secondary Platform Bundle Loader shall build aSspInfoPublic as defined in clause 12.6.2.2.2 of ETSI TS 103 666-2 [10]: a) aSpblSpecVerInfo; b) aSspGeneralCryptoInfo; and/or c) aSspFamilyCryptoInfoBlock, that may contain multiple SspFamilyCryptoInfoBlock data structures. RQ1203_019 12.3.3.1 Each aSspFamilyCryptoInfoBlock data structure shall contain a family identifier and may contain the aSspFamilyCryptoInfo and/or the set of SspOidCryptoInfoBlock data structures. RQ1203_020 12.3.3.1 If aSspFamilyCryptoInfoBlock data structure contains a SspOidCryptoInfoBlock data structure it shall contain the aCustodianOid and aSspOidCryptoInfo. RQ1203_021 12.3.3.1 The aSspGeneralCryptoInfo, the aSspFamilyCryptoInfo and the aSspOidCryptoInfo shall comprise the following: • aSspPkIdForSpbmVerification: trusted public key identifier(s) available for the Secondary Platform Bundle Loader to verify SPB Manager certificate chain. • aSspPkIdForSpblVerification: trusted public key identifier(s). The SPB Manager shall use one of these trusted public key identifiers to verify Secondary Platform Bundle Loader certificate chain. • aKeyAgreementAlgorithmList: the list of algorithm identifiers for key agreement algorithms supported by the Secondary Platform Bundle Loader. • aCipherAlgorithmList: the list of algorithm identifiers of data encryption algorithms supported by the Secondary Platform Bundle Loader. RQ1203_022 12.3.3.1 The capability negotiation procedure shall use the following steps: 3) The Secondary Platform Bundle Loader shall return the aSspInfoPublic to the LBA. RQ1203_023 12.3.3.1 The capability negotiation procedure shall use the following steps: 4) The LBA shall establish a TLS connection with the SPB Manager in server authentication mode. NOTE: The establishment and management of the TLS connection are outside the scope of the present document. RQ1203_024 12.3.3.1 The capability negotiation procedure shall use the following steps: 5) The LBA shall call the "Si2.GetSpbmCertificate" function with its input data comprising aSspInfoPublic and aTerminalInfo. RQ1203_025 12.3.3.1 The capability negotiation procedure shall use the following steps: 6) On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall verify that it supports the contents in aSspInfoPublic and aTerminalInfo. RQ1203_026 12.3.3.1 The capability negotiation procedure shall use the following steps: 7) Using aSspInfoPublic, the SPB Manager shall choose: a) An SPB Manager certificate for key agreement that can be verified by the trusted public key indicated by one of the trusted public key identifiers in the aSspPkIdListForSpbmVerification. The algorithmIdentifier of the selected certificate shall be one of the algorithmIdentifier in aKeyAgreementAlgorithmList. b) An SPB Manager certificate for digital signature that can be verified by the trusted public key indicated by one of the trusted public key identifiers in the aSspPkIdListForSpbmVerification. c) One of trusted public key identifier(s) in the aSspPkIdListForSpblVerification that shall be used by the Secondary Platform Bundle Loader to select its certificate(s). The SPB Manager shall set the selected trusted public key identifier into aSspCiPkIdToBeUsed. d) One of algorithmIdentifiers in the aCipherAlgorithmList that shall be used by the Secondary Platform Bundle Loader and the SPB Manager for data encryption. The SPB Manager shall set the selected algorithmIdentifier into aSspCryptoToBeUsed. The SPB Manager shall generate a random challenge (ChallengeS) which is used in the authentication of the Secondary Platform Bundle Loader. If the SPB Manager cannot find the appropriate certificate(s), trusted public key identifier, or algorithmIdentifier value, the SPB Manager shall return an error to the LBA and shall terminate the procedure. NOTE: The handling of aTerminalInfo is outside the scope of the present document and may be defined by other organizations. RQ1203_027 12.3.3.1 The capability negotiation procedure shall use the following steps: 8) The SPB Manager shall return the SPB Manager certificate for key agreement, aSspCiPkIdToBeUsed, aSspCryptoToBeUsed and aSpbFamilyId, and optionally the certificate chain for SPB Manager certificate for key agreement and the OID of a custodian of the aSpbFamilyId to the LBA. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 42 Release 15 Req.ID Clause Description RQ1203_028 12.3.3.2 The bound SPB image download procedure shall use the following steps: 1) The LBA shall call the "Si3.SetSpbmCredential" function. The function command shall contain the index of IDS_CREDENTIAL_PARAMETER registry and the aSpbmCredential which is defined in clause 12.6.2.3 of ETSI TS 103 666-2 [10]. RQ1203_029 12.3.3.2 The bound SPB image download procedure shall use the following steps: 2) On reception of the "Si3.SetSpbmCredential" function command, the Secondary Platform Bundle Loader shall: a) Set the aSpbmCredential to IDS_CREDENTIAL_PARAMETER registry. b) Verify that the received SPB Manager's certificate for key agreement contained in the aSpbmCredential by using the certification path verification as defined in clause 12.2.1.1.4 of ETSI TS 103 666-2 [10]. c) Select the appropriate Secondary Platform Bundle Loader certificate that shall be verifiable by the trusted public key which is identified by the aSspPkIdForSpblVerification contained in the aSpbmCredential. d) Generate an ephemeral key pair and generate the first session key. e) Build the aSspCredential which is defined in clause 12.6.2.4 of ETSI TS 103 666-2 [10]. f) Set the aSspCredential to the TRE_CREDENTIAL_PARAMETER registry. RQ1203_030 12.3.3.2 The bound SPB image download procedure shall use the following steps: 3) The Secondary Platform Bundle Loader shall return ANY_OK to the LBA. RQ1203_031 12.3.3.2 The bound SPB image download procedure shall use the following steps: 4) The LBA shall call "Si3.GetSspCredential" function. The function command shall contain the index of TRE_CREDENTIAL_PARAMETER registry. RQ1203_032 12.3.3.2 The bound SPB image download procedure shall use the following steps: 5) The Secondary Platform Bundle Loader shall return ANY_OK with the aSspCredential. RQ1203_033 12.3.3.2 The bound SPB image download procedure shall use the following steps: 6) The LBA shall call the "Si2.GetBoundSpbImage" function. The function command shall contain aSspCredential, aTerminalInfo, and aRequestType. RQ1203_034 12.3.3.2 The bound SPB image download procedure shall use the following steps: 7) On reception of the "Si2.GetboundSpbImage" function command, the SPB Manager shall: a) Generate the first session key. b) Decrypt the encrypted data contained in the aSspCredential by using the first session key. c) Verify the Secondary Platform Bundle Loader certificate by using the certification path verification as defined in clause 12.2.1.1.4 of ETSI TS 103 666-2 [10] with the public key identified by the aSspPkIdForSpblVerification. The aSspPkIdForSpblVerification shall be determined in the capability negotiation as defined in clause 12.3.3.1 of ETSI TS 103 666-2 [10]. d) Find the Secondary Platform Bundle identifier linked to the aCodeM contained in the aSspCredential. RQ1203_035 12.3.3.2 If the aCodeM is a reference which is not linked to a Secondary Platform Bundle identifier, the steps 8 and 9 shall be performed. Otherwise the step 10 shall be performed after finishing the step 7: 8) The SPB Manager shall call the "Si1.HandleNotification" function. The function command shall contain the aSspInfoProtected, aTerminalInfo and aCodeM. 9) The service provider shall perform the Secondary Platform Bundle selection process as defined in clause 12.3.2.2 of ETSI TS 103 666-2 [10]. 10) The SPB Manager shall perform the eligibility check based on the aSspInfoProtected and the aTerminalInfo. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 43 Release 15 Req.ID Clause Description RQ1203_036 12.3.3.2 If the aRequestType is "RequestSpbMetadata", the steps from 11 to 15 shall be performed. Otherwise, the step 16 shall be performed after finishing the step 10: 11) The SPB Manager shall build aSpbMetadata and link the aSpbMetadata to the aIdTransac contained in aSspCredential. 12) The SPB Manager shall return the aSpbMetadata to the LBA. 13) The LBA: a) Shall store the aSpbMetadata. b) May display the aSpbMetadata to the end user and require the end user intent if configured. 14) The LBA shall call the "Si2.GetBoundSpbImage" function. The function command shall containaSspCredential, aTerminalInfo and aBoundSpbImageByTransacId as aRequestType. 15) Upon reception of "Si2.GetBoundSpbImage" function command and if the received function command contains the aBoundImageByTransacId, the SPB Manager shall verify the step 7 of this procedure was performed with the same aSspCredential. 16) The SPB Manager shall: a) Generate TIME_STAMP and ephemeral key pair. b) Generate the second session key. c) Build an aBoundSpbImage as defined in clause 12.6.2.5 of ETSI TS 103 666-2 [10]. 17) The SPB Manager shall return the aBoundSpbImage to the LBA. 18) On reception of the "Si2.GetBoundSpbImage" response, the LBA shall verify that the aSpbMetdatanreceived in step 13 and the aSpbMetadata contained in the aBoundSpbImage are the same. If the LBA did not request aSpbMetadata previously, the LBA shall display the aSpbMetadata to the end user and request the end user intent if configured. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.3.4 Installation procedure | RQ1203_037 12.3.4 The installation procedure shall use the following steps: 1) The LBA shall call the "Si3.LoadBoundSpbInfo" function. The function command shall contain aDoOperateParameter contained in the aBoundSpbImage received from the SPB Manager. RQ1203_038 12.3.4 The installation procedure shall use the following steps: 2) On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: a) Verify SPBM certificate for digital signature. b) Verify the content in the aDoOperateParameter. c) Generate the second session key. d) Decrypt the aM-TimeStamp contained in the aDoOperateParameter by using the first session key and decrypt the aM-IMD and aM-ARP contained in the aDoOperateParameter by using the second session key. NOTE: The first session key and the second session key are generated during the download procedure as defined in clause 12.3.3 of ETSI TS 103 666-2 [10]. e) Verify the content in the decrypted data. RQ1203_039 12.3.4 The installation procedure shall use the following steps: 3) The Secondary Platform Bundle Loader shall return ANY_OK to the LBA. RQ1203_040 12.3.4 The installation procedure shall use the following steps: 4) The LBA shall perform the following steps for aNumberSegment times. The aNumberSegment shall be in the aBoundSpbImage: a) The LBA shall call the "Si3.LoadBoundSpbSds" function. The function command shall contain the aChangeSegmentParameter contained in the aBoundSpbImage. b) On reception of the "Si3.LoadBoundSpbSds" function command, the Secondary Platform Bundle Loader shall decrypt the aChangeSegmentParameter by using the second session key. If successful, the Secondary Platform Bundle Loader shall return ANY_OK to the LBA. c) The LBA shall call the "Si3.LoadBoundSpbSeg" function. The function command shall contain the aLoadSegmentParameter contained in the aBoundSpbImage. d) On reception of the "Si3.LoadBoundSpbSeg" function command, the Secondary Platform Bundle Loader shall decrypt the aLoadSegmentParameter by using the key obtained by decrypting the aChangeSegmentParameter. If successful, the Secondary Platform Bundle Loader shall return ANY_OK to the LBA. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 44 Release 15 Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.3.5 SSP activation code | RQ1203_041 12.3.5 The SSP activation code contains the information which is needed by the LBA to trigger the Secondary Platform Bundle provisioning procedure. The SSP activation code is encoded using a URI, as defined in IETF RFC 3986 [18], using the following rules: • The scheme shall have the value "lba". • The authority shall have the value of the FQDN of the SPB Manager to which the terminal shall establish a connection to download a Secondary Platform Bundle. • The path shall contain the action to be performed. The string "bundle" identifies the action to download a Secondary Platform Bundle. • The query contains the other parameters, in the form of key/value pairs. The following keys are defined: Key Value M/O/C codem It describes the CodeMatching identifier used to indicate the specific Secondary Platform Bundle which is linked to the CodeM during the bundle ordering process. M familyid It describes the family identifier of the Secondary Platform Bundle. O (see note) oid It indicates the OID of the custodian of the family identifier. O NOTE: If oid is provided, familyid shall be present. RQ1203_042 12.3.5 The LBA shall reject SSP activation codes containing an unknown path value. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.3 Secondary Platform Bundle management procedure | Reference: ETSI TS 103 666-2 [10], clause 12.4. Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.4.1 Enable a Secondary Platform Bundle | RQ1204_001 12.4.1 The procedure to enable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 1) The end user selects the Secondary Platform Bundle to enable through the LBA (out of scope of the present document). RQ1204_002 12.4.1 The procedure to enable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 2) The LBA shall get the user intent if the Secondary Platform Bundle to enable is a Telecom Secondary Platform Bundle and if the user intent is configured in the Secondary Platform Bundle metadata. RQ1204_003 12.4.1 The procedure to enable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 3) The LBA shall send the Si3.EnableSpb command to the Secondary Platform Bundle Loader with the identifier of the Secondary Platform Bundle to enable. RQ1204_004 12.4.1 The procedure to enable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 4) If the Secondary Platform Bundle to enable is a Telecom Secondary Platform Bundle, the Secondary Platform Bundle Loader shall verify if it can be enabled as described in clause 12.6.5.5.7 of ETSI TS 103 666-2 [10]. RQ1204_005 12.4.1 The procedure to enable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 5) The Secondary Platform Bundle Loader shall use the Si3.EnableSpb response to indicate the execution status of the command. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.4.2 Disable a Secondary Platform Bundle | RQ1204_006 12.4.2 The procedure to disable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 1) The end user selects the Secondary Platform Bundle to disable through the LBA (out of scope of the present document). RQ1204_007 12.4.2 The procedure to disable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 2) The LBA shall get the user intent if the Secondary Platform Bundle to disable is a Telecom Secondary Platform Bundle and if the user intent is configured in the Secondary Platform Bundle metadata. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 45 Release 15 Req.ID Clause Description RQ1204_008 12.4.2 The procedure to disable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 3) The LBA shall send the Si3.DisableSpb command to the Secondary Platform Bundle Loader with the identifier of the Secondary Platform Bundle to disable. RQ1204_009 12.4.2 The procedure to disable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 4) The Secondary Platform Bundle Loader shall use the Si3.DisableSpb response to indicate the execution status of the command. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.4.3 Delete a Secondary Platform Bundle | RQ1204_010 12.4.3 The procedure to delete a Secondary Platform Bundle installed on the iSSP shall use the following steps: 1) The end user selects the Secondary Platform Bundle to delete through the LBA (out of scope of the present document). RQ1204_011 12.4.3 The procedure to disable a Secondary Platform Bundle installed on the iSSP shall use the following steps: 2) The LBA shall get the user intent if the Secondary Platform Bundle to delete is a Telecom Secondary Platform Bundle and if the user intent is configured in the Secondary Platform Bundle metadata. RQ1204_012 12.4.3 If the Secondary Platform Bundle to delete is currently disabled, steps 3 and 4 should be skipped: 3) The LBA shall disable the Secondary Platform Bundle by sending the Si3.DisableSpb command to the Secondary Platform Bundle Loader with the identifier of the Secondary Platform Bundle to disable. RQ1204_013 12.4.3 4) The Secondary Platform Bundle Loader shall use the Si3.DisableSpb response to indicate the execution status of the command. RQ1204_014 12.4.3 5) The LBA shall send the Si3.DeleteSpb command to the Secondary Platform Bundle Loader with the identifier of the Secondary Platform Bundle to delete. RQ1204_015 12.4.3 The Secondary Platform Bundle Loader shall use the Si3.DeleteSpb response to indicate the execution status of the command. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.4.4 SPB metadata retrieving procedure | RQ1204_016 12.4.4 The SPB metadata retrieving procedure shall use the following steps: 1) The LBA shall call the "Si3.GetSpbMetadata" function. The function command shall contain the identifier of the Secondary Platform Bundle (aSpbId) corresponding to the SPB metadata that the LBA intends to retrieve. RQ1204_017 12.4.4 The SPB metadata retrieving procedure shall use the following steps: 2) The Secondary Platform Bundle Loader shall extract the SPB metadata from the firmware session of the Secondary Platform Bundle container identified by the aSpbId contained in the "Si3.GetSpbMetadata" function command. RQ1204_018 12.4.4 The SPB metadata retrieving procedure shall use the following steps: 3) The Secondary Platform Bundle Loader shall return ANY_OK with the SPB as the "Si3.GetSpbMetadata" function response. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.4.5 SPB state retrieving procedure | RQ1204_019 12.4.5 The SPB state retrieving procedure shall use the following steps: 1) The LBA shall call the "Si3.UpdateSpbState" function. The function command shall contain the index of SPB_ID registry and the Secondary Platform Bundle identifier (SpbId) corresponding to the SPB of which the LBA intends to retrieve the state. RQ1204_020 12.4.5 The SPB state retrieving procedure shall use the following steps: 2) On reception of the "Si3.UpdateSpbState" function command, the Secondary Platform Bundle Loader shall: a) Set the SpbId to SPB_ID registry. b) Update the value of SPB_STATE registry with the current state of the Secondary Platform Bundle identified by the SpbId. RQ1204_021 12.4.5 The SPB state retrieving procedure shall use the following steps: 3) The Secondary Platform Bundle Loader shall return ANY_OK to the LBA. RQ1204_022 12.4.5 The SPB state retrieving procedure shall use the following steps: 4) The LBA shall call "Si3.GetSpbState" function. The function command shall contain the index of SPB_STATE registry. RQ1204_023 12.4.5 The Secondary Platform Bundle Loader shall return ANY_OK with the value of SPB_STATE registry to the LBA. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 46 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.4 Notification procedure | Reference: ETSI TS 103 666-2 [10], clause 12.5. Req.ID Clause Description |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.5.2 Notification of the service provider | RQ1205_001 12.5.2 If any of the following steps has to be notified to the service provider according to the configuration of the SPB metadata, the SPB Manager shall call the "Si1.HandleNotification" function after the execution of this step: • The eligibility check procedure, as defined in Annex C, has been executed. • The user rejected the download of a Secondary Platform Bundle. • The download of a bound Secondary Platform Bundle image. • The maximum retry attempts to download a Secondary Platform Bundle image has been reached. • The installation of a Secondary Platform Bundle. • The enablement, disablement or deletion of a Secondary Platform Bundle. RQ1205_002 12.5.2 If, for this step, a notification containing a notification token was previously received from the LBA, as defined in clause 12.5.3 of ETSI TS 103 666-2 [10], the notification event contained in the "Si1.HandleNotification" function command shall be the notification event retrieved from this notification token. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 12.5.3 Notification from the LBA | RQ1205_003 12.5.3 The notification procedure consists of the following steps: 1) A Secondary Platform Bundle container is installed or the state of the Secondary Platform Bundle container is changed as defined in clauses 12.3 and 12.4 of ETSI TS 103 666-2 [10]. RQ1205_004 12.5.3 If the state of the Secondary Platform Bundle container shall be notified to the SPB Manager according to the configuration of the SPB metadata, the steps 2, 3, 4 and 7 shall be performed. 2) The LBA shall retrieve a notification token by using ANY_GET_PARAMETER with the index of OPERATION_TOKEN registry. RQ1205_005 12.5.3 3) The LBA shall establish a TLS connection with the SPB Manager in server authentication mode. RQ1205_006 12.5.3 4) The LBA shall call the "Si2.HandleNotification" function. The function command shall include a notification token. RQ1205_007 12.5.3 The LBA shall store the notification token retrieved at step 2 until that notification token is successfully delivered to the SPB Manager. Once the notification is successfully delivered to the SPB Manager, the LBA shall delete that notification token. RQ1205_008 12.5.3 Otherwise, the steps 5, 6 and 7 shall be performed. 5) The LBA shall establish a TLS connection with the SPB Manager in server authentication mode. RQ1205_009 12.5.3 6) The LBA shall call the "Si2.HandleNotification" function without a notification token. RQ1205_010 12.5.3 7) The SPB Manager shall respond to the LBA to notify a successful reception of the notification. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 47 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.5 Interfaces and functions - Overview | Reference: ETSI TS 103 666-2 [10] clause 12.6.1. Req.ID Clause Description RQ1206_001 12.6.1 If the Service provider is the function requester and the Secondary Platform Bundle Manager is the Function provider the Si1 Interface provides the functions: • Si1.SelectSpb • Si1.CreateSPReference • Si1.FinalizePreparation • Si1.CancelPreparation RQ1206_002 12.6.1 If the Secondary Platform Bundle Manager is the function requester and the Service provider is the Function provider the Si1 Interface provides the functions: • Si1.HandleNotification RQ1206_003 12.6.1 If the Local Bundle Assistant is the function requester and the Secondary Platform Bundle Manager is the Function provider the Si2 Interface provides the functions: • Si2.GetSpbmCertificate • Si2.GetBoundSpbImage RQ1206_004 12.6.1 If the Local Bundle Assistant is the function requester and the Secondary Platform Bundle Loader is the Function provider the Si3 Interface provides the functions: • Si3.GetSspInfo • Si3.SetSpbmCredential • Si3.LoadBoundSpbInfo • Si3.LoadBoundSpbSds • Si3.LoadBoundSpbSeg • Si3.GetSspCredential • Si3.EnableSpb • Si3.DisableSpb • Si3.DeleteSpb |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.6 Interfaces and functions - Common features | Reference: ETSI TS 103 666-2 [10] clause 12.6.2. Req.ID Clause Description RQ1206_005 12.6.2.2.1 The SSP information comprises SspInfoPublic and sspInfoProtected. The SPB Manager shall perform eligibility check based on Annex C of ETSI TS 103 666-2 [10] by using the received SspInfoPublic and sspInfoProtected. RQ1206_006 12.6.2.2.2 The SspInfoPublic is used during the capability negotiation procedure defined in clause 12.3.3 of ETSI TS 103 666-2 [10] to provide the SPB Manager with the trusted public key identifiers and cryptographic algorithms supported by the Secondary Platform Bundle Loader allowing the SPB Manager to select an appropriate certificate and cryptographic algorithm. RQ1206_007 12.6.2.2.2 aSpblSpecVerInfo: • the release of the specification that is implemented by the Secondary Platform Bundle Loader. The first byte indicates the major version of the specification. The second byte indicates the minor version of the specification. RQ1206_008 12.6.2.2.2 aSspPkIdListForSpbmVerification: • For aSspGeneralCryptoInfo, the list indicates the Public Key identifiers supported by the Secondary Platform Bundle Loader that allows for the Secondary Platform Bundle Loader to verify the SPBM certificate chain. • For aSspFamilyCryptoInfo, this list indicates the Public Key identifiers only allowed for the loading Secondary Platform Bundles with the aSpbFamilyId contained in the same SspFamilyCryptoInfoBlock. • For aSspOidCryptoInfo, this list indicates the Public Key identifiers only allowed for loading Secondary Platform Bundles with the aSpbFamilyId contained in the same SspFamilyCryptoInfo and the OID contained in the same SspOidCryptoInfoBlock. RQ1206_009 12.6.2.2.2 aSspPkIdListForSpblVerification: • For aSspGeneralCryptoInfo, the list indicates the Public Key identifiers supported by the Secondary Platform Bundle Loader that allows for the SPB Manager to verify the SPBL certificate chain. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 48 Release 15 Req.ID Clause Description • For aSspFamilyCryptoInfo, the list indicates the Public Key identifiers only allowed for the loading of Secondary Platform Bundles with the aSpbFamilyId contained in the same SspFamilyCryptoInfoBlock. • For aSspOidCryptoInfo, the list indicates the Public Key identifiers only allowed for the loading of Secondary Platform Bundles with the aSpbFamilyId contained in the same SspFamilyCryptoInfo and the OID contained in the same SspOidCryptoInfoBlock. RQ1206_010 12.6.2.2.2 aKeyAgreementAlgorithmList: • For aSspGeneralCryptoInfo, the list indicates the algorithm identifiers for key agreement algorithms supported by the Secondary Platform Bundle Loader. • For aSspFamilyCryptoInfo, the list indicates the key agreement algorithms only allowed for the loading of Secondary Platform Bundles with the aSpbFamilyId contained in the same SspFamilyCryptoInfoBlock. • For aSspOidCryptoInfo, the list indicates the key agreement algorithms only allowed for the loading of Secondary Platform Bundles with the aSpbFamilyId in the same SspFamilyCryptoInfoBlock and the OID contained in the same SspOidCryptoInfoBlock. RQ1206_011 12.6.2.2.2 aCipherAlgorithmList: • For aSspGeneralCryptoInfo, the list indicates the algorithm identifiers of data encryption algorithms supported by the Secondary Platform Bundle Loader. • For aSspFamilyCryptoInfo, the list indicates the data encryption algorithms only allowed for the loading of Secondary Platform Bundles with the aSpbFamilyId contained in the same SspFamilyCryptoInfoBlock. • For aSspOidCryptoInfo, the list indicates the data encryption algorithms only allowed for the loading of Secondary Platform Bundles with the aSpbFamilyId in the same aSspFamilyCryptoInfoBlock and the OID contained in the same aSspOidCryptoInfoBlock. RQ1206_012 12.6.2.2.2 aSpbFamilyId: • a family identifier supported by the Secondary Platform Bundle Loader. RQ1206_013 12.6.2.2.2 aOid: • the OID of a custodian of the family identifier aSpbFamilyId. RQ1206_014 12.6.2.2.3 The Secondary Platform Bundle Loader shall provide the SPB Manager with sspInfoProtected containing the primary platform identifier and family identifier-specific SSP information. RQ1206_015 12.6.2.2.3 aPpIdentifier: • the Primary Platform identifier as defined in clause 7.5 of ETSI TS 103 666-2 [10]. RQ1206_016 12.6.2.2.3 aPartNumberId: • the Part Number identifier as defined in clause 7.7 of ETSI TS 103 666-2 [10] (the identifier of the Part Number in the format of UUID as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13].) The aPartNumberId shall be used by the SPB Manager to identify the Primary Platform manufacturer and the model of the Primary Platform. RQ1206_017 12.6.2.2.3 aMaxSpbSizeSupported: • it indicates the maximum size, in bytes, of the Secondary Platform Bundle container that the iSSP supports. The value of the aMaxSpbSizeSupported shall be the same as the value of MK_MEMORY_PARTITION_SIZE as defined in clause 7.2 of GlobalPlatform VPP - Concepts and Interfaces [15]. RQ1206_018 12.6.2.2.3 aFamilySpecificSspInfo: • it shall include the family identifier-specific SSP information which may be defined for that family identifier. RQ1206_019 12.6.2.2.3 aSpbFamilyId: • the family identifier of the Secondary Platform Bundle. RQ1206_020 12.6.2.2.3 aOidSpecificSspInfoBlock: • it shall include the family identifier-specific SSP information which may be defined by an organization that is responsible for that family identifier and referenced by aOID. RQ1206_021 12.6.2.3 The SPBM credential shall be delivered to the Secondary Platform Bundle Loader during the Secondary Platform Bundle provisioning procedure in clause 12.3 of ETSI TS 103 666-2 [10]. RQ1206_022 12.6.2.3 The LBA shall provide the SPBM credential to the Secondary Platform Bundle Loader by calling the "Si3.GetSspCredential" function and obtain SSP credential as the response. RQ1206_023 12.6.2.3 aCodeM: • the value of the CODE_M as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. It indicates the code matching identifier for a Secondary Platform Bundle image within a SPB Manager. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 49 Release 15 Req.ID Clause Description RQ1206_024 12.6.2.3 aChallengeS: • the value of CHALLENGE_S as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. The aChallengeS is generated by the SPB Manager and used in authentication of the Secondary Platform Bundle Loader. RQ1206_025 12.6.2.3 aSpbFamilyId: • the family identifier of the Secondary Platform Bundle. RQ1206_026 12.6.2.3 aCustodianOid: • the OID of a custodian of the aSpbFamilyId. The custodian shall be associated with a certification path. RQ1206_027 12.6.2.3 aSpbmKaCertificates: • SPBM Certificates for key agreement. RQ1206_028 12.6.2.3 aSspCiPkIdToBeUsed: • CI Public Key identifier for SPBL Certificate which shall be used by the Secondary Platform Bundle Loader for signature generation. RQ1206_029 12.6.2.3 aSspCryptoToBeUsed: • Algorithm identifiers for data encryption which shall be used by the Secondary Platform Bundle Loader and the SPB Manager. RQ1206_030 12.6.2.4 The SSP credential is delivered from the Secondary Platform Bundle Loader to the SPB Manager for authentication, key agreement, and for the binding of a Secondary Platform Bundle container. RQ1206_031 12.6.2.4 aTbsSspImageSessionToken: it contains: • aIdTransac: the ID_TRANSAC as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. • aEPkSpblKa: the SPBL ephemeral public key. • aSpbmKaPkIdToBeUsed: the subject key identifier of the SPBM certificate for key agreement which shall be used to generated the first session key. • aUuidL: the UUIDL as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_032 12.6.2.4 aSspImageSessionTokenSignature: • the signature of aTbsSspImageSessionToken which can be verified by SPBL Certificate. RQ1206_033 12.6.2.4 aM-SSP: • EncryptedBlock of data containing SPBL Certificate, TbsSspToken, and SSP Token signature. The SSP Token, SSP Token signature, and aM-SSP are generated by the Secondary Platform Bundle Loader as defined in clause 12.6.5.5.2 of ETSI TS 103 666-2 [10]. RQ1206_034 12.6.2.4 aEncryptionType: • it indicates the encryption algorithm used to generate the items of type EncryptedBlock. RQ1206_035 12.6.2.4 EncryptedBlock: • data structure containing the encrypted message and the integrity check. RQ1206_036 12.6.2.4 aSpblCertChain: • it contains Certificates used for the SPB Manager to verify SPBL Certificate. RQ1206_037 12.6.2.4 aTbsSspToken: it contains: • aCodeM: the value of the CODE_M as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. • aChallengeS: the value of CHALLENGE_S as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. • aSspInfoProtected: the protected SSP information. RQ1206_038 12.6.2.5 The Secondary Platform Bundle container shall be bound to the iSSP as defined in clause 12.6.4.3 of ETSI TS 103 666-2 [10] and delivered to the LBA as the bound SPB image. RQ1206_039 12.6.2.5 aImageOwnerId: • Owner Identifier of the Secondary Platform Bundle container. RQ1206_040 12.6.2.5 aNumberSegment: • Number of Segment Structures in the bound SPB image. RQ1206_041 12.6.2.5 aServerNotifyBaseUrls: • URLs of the servers for notifications. RQ1206_042 12.6.2.5 aImageMakerId: • Identifier of the Secondary Platform Bundle maker as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_043 12.6.2.5 aMetaDataImage: • Metadata of the image from the Image Maker. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 50 Release 15 Req.ID Clause Description RQ1206_044 12.6.2.5 aM-IMD: • EncryptedBlock of Image Descriptor as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_045 12.6.2.5 aM-ARP: • EncryptedBlock of ATK.ARP.ECDSA as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_046 12.6.2.5 aM-TimeStamp: • EncrytedBlock of TIME_STAMP as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_047 12.6.2.5 aSpbmToken: • Data structure containing TbsSpbmToken and signature of the TbsSpbmToken. RQ1206_048 12.6.2.5 aTbsSpbmToken: • Data structure containing the ephemeral public key of the SPB Manager and the image session identifier (ID_TRANSAC). RQ1206_049 12.6.2.5 aSpbmCerts: • List of the Certificate of the certification path from a trusted certificate to the SPBM certificate. RQ1206_050 12.6.2.5 aDoOperateParameter: • The parameter for the OFL_DO_OPERATE command as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13] including the SPB metadata. RQ1206_051 12.6.2.5 aChangeSegmentParameter: • The parameter for the OFL_CHANGE_SEGMENT command as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_052 12.6.2.5 aLoadSegmentParameter: • The parameter for the OFL_LOAD_SEGMENT command as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_053 12.6.2.6 The SPB metadata contains specific information of the Secondary Platform Bundle. During the download procedure described in clause 12.3.3 of ETSI TS 103 666-2 [10], the SPB metadata shall be provided to the LBA in a plaintext. RQ1206_054 12.6.2.6 The SPB metadata contains specific information of the Secondary Platform Bundle. After the Secondary Platform Bundle is successfully installed, the SPB metadata shall be accessible by the LBA via Si3 interface irrespective of the state of that Secondary Platform Bundle. RQ1206_055 12.6.2.6 The SPB metadata shall include the following: • aSpbId: identifier of the Secondary Platform Bundle. • aSpbFamilyId: family identifier of the Secondary Platform Bundle as defined in clause 9.7 of ETSI TS 103 666-2 [10]. • aCustodianOid: OID of one of the custodians associated with a SpbFamilyId which defines specific requirement (e.g. trusted CIs, product certification, operational modes of the terminal) applied to this Secondary Platform Bundle. RQ1206_056 12.6.2.6 The SPB metadata may include the following: • aSupportedCustodianList: list of OIDs of custodians associated with supported certification path used to load the Secondary Platform Bundle. If the aSupportedCustodianList contains multiple OIDs, the first OBJECT IDENTIFIER denotes the most preferred custodian to select a certification path. The aSupportedCustodianList may contain the aCustodianOid. • aSpbNotificationConfig: it includes the configuration set by a service provider as per a notification recipient. The configuration shall include the address of a notification recipient and the list of events which shall be notified. NOTE: Eligibility check and maximum retry attempts notification status are only intended to be used for Si1 notifications. aFamilySpecificData: family identifier-specific metadata defined as per the family identifier. • aOidSpecificData: family identifier-specific metadata defined by custodian(s) of the family identifier. The aOidSpecificData may consists of multiple OidSpecificInfoBlock data structures. Each OidSpecificInfoBlock shall have a custodian-defined metadata and the OID identifying that custodian-defined metadata. RQ1206_057 12.6.2.7 The terminal information contains details about the capabilities of the terminal. It is delivered by the LBA to the SPB Manager. RQ1206_058 12.6.2.7 aLbaSpecVerInfo: • the release of the specification that is implemented by the LBA. The first byte indicates the major version of the specification. The second byte indicates the minor version of the specification. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 51 Release 15 Req.ID Clause Description RQ1206_059 12.6.2.7 aSpbFamilyId: • a family identifier of the Secondary Platform Bundle. RQ1206_060 12.6.2.7 aFamilySpecificTerminalInfoBlock: • it shall include the family identifier-specific terminal information which may be defined for that family identifier. RQ1206_061 12.6.2.7 aOidSpecificTerminalInfoBlock: • it shall include family identifier-specific terminal information which may be defined by an organization that is responsible for that family identifier and referenced by the OID. RQ1206_062 12.6.2.8 The notification token contains the information about the state change of the Secondary Platform Bundle container. RQ1206_063 12.6.2.8 The Secondary Platform Bundle Loader shall generate the notification token after installation, enabling, disabling or deleting of the Secondary Platform Bundle container if it is configured in the SPB metadata. RQ1206_064 12.6.2.8 Prior to the generation of the notification token, the notification counter of the firmware session of the Secondary Platform Bundle container as described in clause 7.3.1.5 of ETSI TS 103 666-2 [10] shall be incremented by one. RQ1206_065 12.6.2.8 If the maximum value is reached, the counter shall return to the initial value. RQ1206_066 12.6.2.8 After generating the notification token, the Secondary Platform Bundle Loader shall set the value of the notification token data object into OPERATION_TOKEN registry. RQ1206_067 12.6.2.8 The LBA shall use ANY_GET_PARAMETER command with the index of OPERATION_TOKEN registry to retrieve the most recently generated notification token. RQ1206_068 12.6.2.8 aSpbId: • the identifier of the Secondary Platform Bundle. The aSpbId shall be the Public image UUID. RQ1206_069 12.6.2.8 aNotificationEvent: • it indicates the procedure related to this notification. RQ1206_070 12.6.2.8 aCounter: • the notification counter value managed in the firmware session of the Secondary Platform Bundle identified by the aSpbId. RQ1206_071 12.6.2.8 aNotificationTokenHash: • the hashed value generated by an HMAC-SHA-256 as defined in IETF RFC 4868 [20] of the message being the string concatenating the aSpbId, the aNotificationEvent, the aCounter, and the Primary Platform identifier (of 32 bytes, as defined in clause 7.5 of ETSI TS 103 666-2 [10]), and with the secondary platform private identifier described in clause 9.4.5 of ETSI TS 103 666-2 [10] as the key. aNotificationTokenHash is therefore computed with following parameters: aNotificationTokenHash = HMAC-SHA-256 (message, key) where: message = aSpbId | aNotificationEvent | aCounter | aPpId, and key = aPrivateSpbId. NOTE: The Primary Platform Identifier is used to compute the aNotificationTokenHash but is not included in the aTbhNotificationToken. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.7 Interfaces and functions - Si1 interface | Reference: ETSI TS 103 666-2 [10] clause 12.6.3. Req.ID Clause Description 12.6.3.1 Overview RQ1206_072 12.6.3.1 The Si1 interface is used between the service provider and the SPB Manager to prepare the download of a Secondary Platform Bundle. RQ1206_073 12.6.3.1 The binding of the Si1 interface shall be performed over Hypertext Transfer Protocol version 2 (HTTP/2) as defined in IETF RFC 7540 [26] and the Transport Layer Security (TLS) version 1.3 or higher in mutual authentication mode as defined in IETF RFC 8446 [27]. RQ1206_074 12.6.3.1 The service provider shall be in charge of managing the connection establishment to the SPB Manager for the Si1 interface. RQ1206_075 12.6.3.1 The service provider shall use HTTP POST request message with HTTP path 'etsi/issp/si1/asn1' to deliver any function command over the Si1 interface. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 52 Release 15 Req.ID Clause Description 12.6.3.2 Si1 common headers RQ1206_076 12.6.3.2.1 aFunctionRequesterId: • identifier of the function requester. RQ1206_077 12.6.3.2.1 aFunctionCallId: • identifier of the function call. This identifier is used to manage function call retries. RQ1206_078 12.6.3.2.2 aFunctionExecutionStatus: • indicates the status after the execution of the function. 12.6.3.3 Si1 error codes RQ1206_079 12.6.3.3 For error codes used to indicate an error over the Si1 interface, Table 12.5 of ETSI TS 103 666-2 [10] gives the applicability matrix according to the Si1 function. 12.6.3.4 Si1.SelectSpb RQ1206_080 12.6.3.4.1 The "Si1.SelectSpb" function shall be used by the service provider during the Secondary Platform Bundle selection as defined in clause 12.3.2.2 of ETSI TS 103 666-2 [10]. RQ1206_081 12.6.3.4.1 The service provider shall use the "Si1.SelectSpbm" function to select a Secondary Platform Bundle that matches the terminal and the SSP capabilities. RQ1206_082 12.6.3.4.1 The body part of the HTTP POST request for the "Si1.SelectSpbm" function command shall contain Si1SelectSpbCommand defined as follows: • aSi1CommandHeader: − header of the command as defined in clause 12.6.3.2.1 of ETSI TS 103 666-2 [10]. It may be used by aNotificationReceiverId in subsequent Si1.HandleNotification calls related to this selection. • aSpbId: − identifier of the Secondary Platform Bundle to reserve. • aSpbType: − type of Secondary Platform Bundle in which the SPB Manager shall select an available Secondary Platform Bundle identifier. • aPpIdentifier: − the primary platform identifier to link with the Secondary Platform Bundle reserved by the Si1.SelectSpb function. • aCodeM: − CodeM to be linked with the Secondary Platform Bundle reserved by the Si1.SelectSpb function. This parameter shall be present if the creation of the service provider reference defined in clause 12.3.2.3 of ETSI TS 103 666-2 [10] has been previously executed. • aFlagFinalize: − Boolean that indicates whether the "Si1.FinalizePreparation" function will be called later. • aCustodianSpecificInfoBlock: − specific parameter which may be defined by the custodian of the family identifier issuing the command. How this parameter is handled by the SPB Manager is out of scope of the present document. • aServiceProviderSpecificInfoBlock: − specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. RQ1206_083 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. RQ1206_084 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • If the Secondary Platform Bundle identifier (spbId) was provided as input data: − return an error with the code eSpbIdNotAvailable if the spbId is not available; − return an error with the code eSpbIdUnknown if the spbId does not exist; − return an error with the code eSpbTypeMismatch if a Secondary Platform Bundle type (spbType) was provided as input data and does not match the type of the spbId. RQ1206_085 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • If a Secondary Platform Bundle type (spbType) was provided as input data: − return an error with the code eSpbTypeUnknown if the spbType is unknown to the SPB Manager; − return an error with the code eSpbTypeNotAvailable if the SPM Manager cannot find an available spbId corresponding to the requested sbpType. RQ1206_086 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Return an error with the code eCodeMNotAllowed if a CodeM was provided as input data and is already linked to another Secondary Platform Bundle identifier. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 53 Release 15 Req.ID Clause Description RQ1206_087 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Store the CodeM if provided as input data and is not known to the SPB Manager. RQ1206_088 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Reserve a Secondary Platform Bundle among those available in its inventory and that corresponds to the requested spbId and/or sbpType. RQ1206_089 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Link the CodeM with the reserved spbId. RQ1206_090 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Link the reserved spbId to the primary platform identifier if the function command contains the primary platform identifier (aPpIdentifier). RQ1206_091 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Memorize whether the "Si1.FinalizePreparation" function will be called later. If aFlagFinalize is not present, it is considered as set to FALSE. RQ1206_092 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Build Si1SelectSpbResponse containing either an error code if one of the above steps has failed or the selected Secondary Platform identifier (spbId) together with its type (sbpType) and, optionally the Primary Platform Identifier (aPpIdentifier) if it was provided in the command and the CodeM (aCodeM) if it was provided in the incoming command. Si1SelectSpbResponse may also contain family identifier and/or service provider specific information. Their content is not in the scope of the present document. RQ1206_093 12.6.3.4.2 Upon reception of the "Si1.SelectSpb" function command, the SPB Manager shall: • Send the response to the service provider. RQ1206_094 12.6.3.4.3 The body part of the HTTP POST response for the "Si1.SelectSpb" function shall contain Si1SelectSpbResponse defined as follows: • aSi1ResponseHeader: header of the response as defined in clause 12.6.3.2.2 of ETSI TS 103 666-2 [10]. • aSpbId:identifier of the Secondary Platform Bundle reserved by the SPB Manager. • aSpbType: type of Secondary Platform Bundle tied to aSpbId. • aPpIdentifier: identifier of the primary platform linked with aSpbId, if present in the incoming command. • aCodeM: CodeM to linked with the aSpbId, if present in the incoming command. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the response. How this parameter is handled by the SPB Manager is out of scope of the present document. • aServiceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. • aFamilySpecificSelectSpbmResponse: family identifier-specific parameter which may be defined for that family identifier. How this parameter is handled by the SPB Manager is out of scope of the present document. 12.6.3.5 Si1.CreateSPReference RQ1206_095 12.6.3.5.1 The "Si1.CreateSPReference" function shall be used by the service provider during the procedure of creation of a service provider reference as defined in clause 12.3.2.3. of ETSI TS 103 666-2 [10]. RQ1206_096 12.6.3.5.1 The service provider may use the "Si1.CreateSPReference" function to create a reference shared between the service provider and the SPB Manager. This reference, i.e. CodeM shall be provided to the End User by the service provider as part of the activation code, allowing the End User to trigger the download procedure as defined in clause 12.3.3 of ETSI TS 103 666-2 [10]. RQ1206_097 12.6.3.5.1 The body part of the HTTP POST request for the "Si1.CreateSPReference" function command shall contain Si1.CreateSPReferenceCommand defined as follows: • aSi1CommandHeader: header of the command as defined in clause 12.6.3.2.1 of ETSI TS 103 666-2 [10]. It may be used by aNotificationReceiverId in subsequent Si1.HandleNotification calls related to the CodeM provided as input parameter or generated by the SPB Manager. • aSpbId: identifier of the Secondary Platform Bundle. This parameter shall be present if the Secondary Platform Bundle selection procedure has been executed first, else it shall be ignored. • aCodeM: CodeM generated by the service provider. • aTaskType: type of task associated with the reference. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the command. How this parameter is handled by the SPB Manager is out of scope of the present document. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 54 Release 15 Req.ID Clause Description • aServiceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. RQ1206_098 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. RQ1206_099 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Return an error with the code eTaskTypeUnknown if the Si1TaskType is not eSi1TaskType-DownloadSPB. RQ1206_100 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Return an error with the code eTaskNotAllowed if the function caller is not allowed to use the Si1TaskType. NOTE: How the function caller is allowed to use is not in the scope of ETSI TS 103 666-2 [10]. RQ1206_101 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Generate a CodeM if it was not provided as input data and ensure that it is unique on its own context. RQ1206_102 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Return an error with the code eCodeMNotAllowed if the CodeM was provided as input data and is already linked to another Secondary Platform Bundle identifier. RQ1206_103 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Store the CodeM. RQ1206_104 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. RQ1206_105 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Build Si1CreateSPReferenceResponse containing either an error code if one of the above step has failed or the CodeM (aCodeM) provided as input data or generated by the SPB Manager and the Secondary Platform identifier (spbId) if it was provided as input data. Si1CreateSPReferenceResponse may also contain family identifier and/or service provider specific information. Their content is not in the scope of the present document. RQ1206_106 12.6.3.5.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Send the response to the service provider. RQ1206_107 12.6.3.5.3 The body part of the HTTP POST response for the "Si1.CreateSPReference" function shall contain Si1CreateSPReferenceResponse defined as follows: • aSi1ResponseHeader: header of the response as defined in clause 12.6.3.2.2 of ETSI TS 103 666-2 [10]. • aCodeM: CodeM generated by the SPB manager if not present in the incoming command or CodeM as it was in the incoming command. • aSpbId: identifier of the Secondary Platform Bundle as if was in the incoming command. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the response. How this parameter is handled by the SPB Manager is out of scope of the present document. • aServiceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. 12.6.3.6 Si1.FinalizePreparation RQ1206_108 12.6.3.6.1 The "Si1.CreateSPReference" function shall be used by the service provider during the procedure of creation of a service provider reference as defined in clause 12.3.2.3. of ETSI TS 103 666-2 [10]. RQ1206_109 12.6.3.6.1 If the selection of the Secondary Platform Bundle procedure, as defined in clause 12.3.2.2 of ETSI TS 103 666-2 [10] has been executed after the creation of the CodeM procedure, as defined in clause 12.3.2.3 of ETSI TS 103 666-2 [10], the service provider may use the "Si1.FinalizePreparation" function to indicate that its internal procedures are completed, e.g. the provisioning of its technical platforms or data bases. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 55 Release 15 Req.ID Clause Description RQ1206_110 12.6.3.6.1 If the service provider has set aFlagFinalize to TRUE in the "Si1.SelectSpb" function command, the SPB Manager shall wait for the completion of the Secondary Platform Bundle selection process as described in clause 12.3.2.2 of ETSI TS 103 666-2 [10] (i.e. after it has sent the response to the "Si1.FinalizePreparation" function related to this Secondary Platform Bundle) to continue with the Bound SPB image download as defined in clause 12.3.3.2. of ETSI TS 103 666-2 [10]. RQ1206_111 12.6.3.6.1 The body part of the HTTP POST request for the "Si1.FinalizePreparation" function command shall contain Si1.FinalizePreparationCommand defined as follows: • aSi1CommandHeader: header of the command as defined in clause 12.6.3.2.1 of ETSI TS 103 666-2 [10]. It may be used by aNotificationReceiverId in subsequent Si1.HandleNotification calls related to aCodeM. • aCodeM: reference to the preparing procedure to finalize. • aSpbId: identifier of the Secondary Platform Bundle as if was in the incoming command. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the command. How this parameter is handled by the SPB Manager is out of scope of the present document. • aSrviceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. RQ1206_112 12.6.3.6.2 Upon reception of the "Si1.FinalizePreparation" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. RQ1206_113 12.6.3.6.2 Upon reception of the "Si1.FinalizePreparation" function command, the SPB Manager shall: • Verify the CodeM provided as input data. RQ1206_114 12.6.3.6.2 Upon reception of the "Si1.FinalizePreparation" function command, the SPB Manager shall: • Return an error with the code eCodeMUnknown if the CodeM is unknown to the SPB Manager. RQ1206_115 12.6.3.6.2 Upon reception of the "Si1.FinalizePreparation" function command, the SPB Manager shall: • Return an error with the code eCodeMNotAllowed if the CodeM is not linked to a Secondary Platform Bundle identifier. RQ1206_116 12.6.3.6.2 Upon reception of the "Si1.FinalizePreparation" function command, the SPB Manager shall: • Build Si1FinalizePreparationResponse containing either an error code if the above step has failed or the CodeM (aCodeM) provided as input data. Si1FinalizePreparationResponse may also contain family identifier and/or service provider specific information. Their content is not in the scope of the present document. RQ1206_117 12.6.3.6.2 Upon reception of the "Si1.FinalizePreparation" function command, the SPB Manager shall: • Send the response to the service provider. RQ1206_118 12.6.3.6.2 Upon reception of the "Si1.CreateSPReference" function command, the SPB Manager shall: • Allow the bound SPB image download procedure as defined in clause 12.3.3.2 of ETSI TS 103 666-2 [10]. RQ1206_119 12.6.3.6.3 The body part of the HTTP POST response for the "Si1.finalizePreparation" function shall contain Si1FinalizePreparationResponse defined as follows: • aSi1ResponseHeader: header of the response as defined in clause 12.6.3.2.2 of ETSI TS 103 666-2 [10]. • aCodeM: CodeM as it was in the incoming command. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the response. How this parameter is handled by the SPB Manager is out of scope of the present document. • aServiceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. 12.6.3.7 Si1.CancelPreparation RQ1206_120 12.6.3.7.1 The "Si1.CancelPreparation" function shall be used by the service provider to cancel a pending preparation procedure as defined in clause 12.3.2 of ETSI TS 103 666-2 [10]. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 56 Release 15 Req.ID Clause Description RQ1206_121 12.6.3.7.1 The body part of the HTTP POST request for the "Si1.CancelPreparation" function command shall contain Si1CancelPreparationCommand defined as follows: • aSi1CommandHeader: header of the command as defined in clause 12.6.3.2.1 of ETSI TS 103 666-2 [10]. It may be used by aNotificationReceiverId in subsequent Si1.HandleNotification calls related to aCodeM or aSpbId. • aCodeM: task's reference to cancel. This parameter shall be present if aSpbId is not provided as input parameters. • aSpbId: identifier of the Secondary Platform Bundle associated to the procedure to cancel. This parameter shall be present if aCodeM is not provided as input parameters. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the command. How this parameter is handled by the SPB Manager is out of scope of the present document. • aServiceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. RQ1206_122 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Store the value of aSi1CommandHeader. RQ1206_123 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Return an error with the code eCodeMUnknown if a CodeM is provided as input data and is unknown to the SPB Manager. RQ1206_124 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Return an error with the code eCodeMNotAllowed if the bound SPB image download procedure as defined in clause 12.3.3.2 of ETSI TS 103 666-2 [10] associated with the Secondary Platform Bundle identifier linked to the CodeM provided as input data is completed. RQ1206_125 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Return an error with the code eSpbIdUnknown if a aSpbId is provided as input data and is unknown to the SPB Manager. RQ1206_126 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Return an error with the code eSpbIdNotAllowed if a aSpbId is provided as input data and is not linked with the CodeM provided as input data. RQ1206_127 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Cancel any pending procedure associated with the CodeM and/or the SpbId provided as input parameter(s), e.g. download procedure. RQ1206_128 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Unreserved the Secondary Platform Bundle identifier provided as input data and/or linked to the CodeM provided as input data. RQ1206_129 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Remove any reference to the CodeM if provided as input data. RQ1206_130 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Build Si1CancelPreparationResponse containing either an error code if one of the above step has failed or either the CodeM (aCodeM) or the Secondary Platform Bundle identifier (aSpbId) if provided as input data and the linked Secondary Platform identifier if any. Si1CancelPreparationResponse may also contain family identifier and/or service provider specific information. Their content is not in the scope of the present document. RQ1206_131 12.6.3.7.2 Upon reception of the "Si1.CancelPreparation" function command, the SPB Manager shall: • Send the response to the service provider. RQ1206_132 12.6.3.7.3 The body part of the HTTP POST response for the "Si1.CancelPreparation" function shall contain Si1CancelPreparationResponse defined as follows: • aSi1ResponseHeader: header of the response as defined in clause 12.6.3.2.2 of ETSI TS 103 666-2 [10]. • aCodeM: CodeM as it was in the incoming command. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 57 Release 15 Req.ID Clause Description • aSpbId: identifier of the Secondary Platform Bundle linked to aCodeM if aCodeM was provided as input data or aSpbId as if was in the incoming command. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the response. How this parameter is handled by the SPB Manager is out of scope of the present document. • aServiceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. 12.6.3.8 Si1.HandleNotification RQ1206_133 12.6.3.8.1 The "Si1.HandleNotification" function shall be used by the SPB Manager to send any notifications as agreed with the service provider owning the pending related task. The agreement of the notifications to send is outside the scope of the present document. RQ1206_134 12.6.3.8.1 The body part of the HTTP POST request for the "Si1.HandleNotification" function shall contain Si1HandleNotificationBlock defined as follows: • aNotificationReceiverId: identifier of the recipient of the notification. It may equal to the function requester identity extracted from the last request-response function related to the same pending task, e.g. to the same download procedure. • aNotificationCallId: identifier of the function caller in the context of the recipient of the notification. It may be equal to the function caller identity extracted from the last request-response function related to the same pending task, e.g. to the same download procedure. • aCodeM: task's reference to cancel. This parameter shall be present if aSpbId is not provided as input parameters. • aSpbId: identifier of the Secondary Platform Bundle associated to the procedure to cancel. This parameter shall be present if aCodeM is not provided as input parameters. • aSpbType: type of Secondary Platform Bundle in which the SPB Manager shall select an available Secondary Platform Bundle identifier. • aPpIdentifier: identifier of the primary platform to link with the Secondary Platform Bundle reserved by the Si1.SelectSpb function. • aTimeStamp: indicates the date/time when the operation has been performed or when the notification has been received by the SPB Manager. • aNotificationEvent: indicates the step reached by the procedure that was executed. • aNotificationEventStatus: indicates the status after the execution of the notification. • aCustodianSpecificInfoBlock: specific parameter which may be defined by the custodian of the family identifier issuing the command. How this parameter is handled by the SPB Manager is out of scope of the present document. • aServiceProviderSpecificInfoBlock: specific parameter which may be defined by the service provider. How this parameter is handled by the SPB Manager is out of scope of the present document. RQ1206_135 12.6.3.8.2 Table 12.6 ETSI TS 103 666-2 [10] indicates which parameters shall be present depending on aNotificationEvent. NOTE: RQ1206_136 to RQ1206_139 are set to void due to numbering and duplication issues. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.8 Interfaces and functions - Si2 interface | Reference: ETSI TS 103 666-2 [10] clause 12.6.4. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 58 Release 15 Req.ID Clause Description 12.6.4.1 Overview RQ1206_140 12.6.4.1 The Si2 interface is used between the LBA and SPB Manager to provide a transport of the bound Secondary Platform Bundle image and the management commands on the Secondary Platform Bundles installed in the iSSP. RQ1206_141 12.6.4.1 The binding of the Si2 interface shall be performed over Hypertext Transfer Protocol version 2 (HTTP/2) as defined in IETF RFC 7540 [26] and the Transport Layer Security (TLS) version 1.3 in server authentication mode as defined in IETF RFC 8446 [27]. RQ1206_142 12.6.4.1 The LBA shall be in charge of managing the connection establishment to the SPB Manager for the Si2 interface. RQ1206_143 12.6.4.1 The LBA shall use HTTP POST request message with HTTP path 'etsi/issp/si2/asn1' to deliver any function command over the Si2 interface. 12.6.4.2 Si2.GetSpbmCertificate RQ1206_144 12.6.4.2.1 The "Si2.GetSpbmCertificate" function shall be used by the LBA during the capability negotiation procedure as defined in clause 12.3.3.1 of ETSI TS 103 666-2 [10]. RQ1206_145 12.6.4.2.1 The LBA shall use the "Si2.GetSpbmCertificate" function to provide the SPB Manager with the public SSP information (SspInfoPublic) as defined in clause 12.6.2.2.2 of ETSI TS 103 666-2 [10] and terminal information (TerminalInfo) as defined in clause 12.6.2.7 of ETSI TS 103 666-2 [10]. RQ1206_146 12.6.4.2.1 The body part of the HTTP POST request for the "Si2.GetSpbmCertificate" function command shall contain Si2GetSpbmCertificateCommand with aSspInfoPublic - Public SSP information as defined in clause 12.6.2.2.2 of ETSI TS 103 666-2 [10] and aTerminalInfo - Terminal information as defined in clause 12.6.2.7 of ETSI TS 103 666-2 [10]. RQ1206_147 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 1) Perform eligibility check based on Annex C as follows: a) The SPB Manager shall verify that the aSpblSpecVerInfo contained in the aSspInfoPublic and aLbaSpecVerInfo contained in aTerminalInfo are supported by itself. If a version is not supported, the SPB Manager shall return eNotSupportedLbaVersion or eNotSupportedSpblVersion (the error indicating that the version of the Secondary Platform Bundle Loader or the LBA is not supported). RQ1206_148 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 2) Determine the family identifier of the Secondary Platform Bundle container to be provisioned as follows: a) If the SPB Manager supports only one family identifier, the SPB Manager shall select that family identifier. If there is an aSspFamilyCryptoInfoBlock and no aSspGeneralCryptoInfo inside the aSspInfoPublic, the SPB Manager shall check whether one of the family identifiers contained in the aSspFamilyCryptoInfoBlock is supported. If supported, the SPB Manager shall select that family identifier. If not supported, the SPB Manager shall return eNotSupportedFamilyId (the error indicating that the family identifier is not supported). b) If the SPB Manager supports multiple family identifiers: − If there is only one SspFamilyCryptoInfoBlock data structure containing a family identifier supported by the SPB Manager, the SPB Manager shall select that family identifier. If there is no SspFamilyCryptoInfoBlock data structure containing a family identifier supported by the SPB Manager, the SPB Manager shall return eNotSupportedFamiyId (the error indicating that the family identifier is not supported). − If there are multiple aSspFamilyCryptoInfoBlock data structure containing the family identifier supported by the SPB Manager inside the aSspInfoPublic or there is only aSspCryptoInfo inside the aSspInfoPublic, the SPB Manager shall return eSpblSelectOneFamilyId (the error indicating that one family identifier shall be selected by the Secondary Platform Bundle Loader). RQ1206_148a 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 2) Determine the family identifier of the Secondary Platform Bundle container to be provisioned as follows: a) If the SPB Manager supports only one family identifier, the SPB Manager shall select that family identifier. If there is an aSspFamilyCryptoInfoBlock and no aSspGeneralCryptoInfo inside the aSspInfoPublic, the SPB Manager shall check whether one of the family identifiers contained in the aSspFamilyCryptoInfoBlock is supported. If supported, the SPB Manager shall select that family identifier. If not supported, the SPB Manager shall return eNotSupportedFamilyId (the error indicating that the family identifier is not supported). ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 59 Release 15 Req.ID Clause Description RQ1206_148b 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 2) Determine the family identifier of the Secondary Platform Bundle container to be provisioned as follows: b) If the SPB Manager supports multiple family identifiers: − If there is only one SspFamilyCryptoInfoBlock data structure containing a family identifier supported by the SPB Manager, the SPB Manager shall select that family identifier. If there is no SspFamilyCryptoInfoBlock data structure containing a family identifier supported by the SPB Manager, the SPB Manager shall return eNotSupportedFamiyId (the error indicating that the family identifier is not supported). RQ1206_148c 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 2) Determine the family identifier of the Secondary Platform Bundle container to be provisioned as follows b) If the SPB Manager supports multiple family identifiers: − If there are multiple aSspFamilyCryptoInfoBlock data structure containing the family identifier supported by the SPB Manager inside the aSspInfoPublic or there is only aSspCryptoInfo inside the aSspInfoPublic, the SPB Manager shall return eSpblSelectOneFamilyId (the error indicating that one family identifier shall be selected by the Secondary Platform Bundle Loader). RQ1206_149 12.6.2.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 3) Set the selected family identifier into the aSpbFamilyId. RQ1206_150 12.6.2.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 4) Using the selected family identifier, select one of aSspCryptoInfo, aSspFamilyCrytoInfo and aSspOidCryptoInfo inside the aSspInfoPublic as follows: a) If there is a SspFamilyCryptoInfoBlock data structure containing the selected family identifier, the SPB Manager shall select that SspFamilyCryptoInfoBlock data structure. Using the selected SspFamilyCryptoInfoBlock data structure: − If the SPB Manager supports only one custodian for the selected family identifier and there is a SspOidCryptoInfoBlock data structure containing the OID of that custodian, the SPB Manager shall select the aSspOidCyrptoInfo data structure contained in that SspOidCryptoInfoBlock data structure. If there is no SspOidCryptoInfoBlock data structure containing the OID of that custodian, the SPB Manager shall select the aSspFamilyCryptoInfo inside the SspFamilyCryptoInfoBlock data structure. − If the SPB Manager supports multiple custodians for the selected family identifier and there is only one SspOidCryptoInfoBlock data structure containing the Oid of one of the custodians supported by the SPB Manager, the SPB Manager shall select the aSspOidCryptoInfo contained in that SspOidCryptoInfoBlock data structure. − If the SPB Manager supports multiple custodians for the selected family identifier and there are multiple SspOidCryptoInfoBlock data structures containing the OIDs of custodians supported by the SPB Manager, the SPB Manager shall return eSpblSelectOneOid (the error indicating that one custodian shall be selected by the Secondary Platform Bundle Loader). − If there is no SspOidCryptoInfo data structure containing the OID of a custodian supported by the SPB Manager, the SPB Manager shall select the aSspFamilyCryptoInfo. b) If there is no SspFamilyCryptoInfoBlock data structure containing the selected family identifier, the SPB Manager shall select the aSspGeneralCryptoInfo inside the aSspInfoPublic. RQ1206_151 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 5) Using the selected SspCryptoInfo data structure, choose the following: a) An SPB Manager certificate for key agreement that can be verified by the trusted public key indicated by one of the trusted public key identifiers in the aSspPkIdListForSpbmVerification. If none of the trusted public key identifiers in the aSspPkIdListForSpbmVerification is supported, the SPB Manager shall return eNotSupportedPkIdSpbmVerification. The algorithmIdentifier of the selected certificate shall be one of the algorithmIdentifier in aKeyAgreementAlgorithmList. If the algorithmIdentifier of the selected certificate is not supported, the SPB Manager shall return eNotSupportedKeyAgreementAlgorithm. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 60 Release 15 Req.ID Clause Description b) An SPB Manager certificate for digital signature that can be verified by the trusted public key indicated by one of the trusted public key identifiers in the aSspPkIdListForSpbmVerification. If any trusted public key identifiers in the aSspPkIdListForSpbmVerification is not supported, the SPB Manager shall return eNotSupportedPkIdSpbmVerification. c) One of trusted public key identifier(s) in the aSspPkIdListForSpblVerification that shall be used by the Secondary Platform Bundle Loader to select its certificate(s). The SPB Manager shall set the selected trusted public key identifier into aSspCiPkIdToBeUsed. If any trusted public key identifiers in the aSspPkIdListForSpblVerification is not supported, the SPB Manager shall return eNotSupportedPkIdSpblVerification. d) d) One of algorithmIdentifiers in the aCipherAlgorithmList that shall be used by the Secondary Platform Bundle Loader and the SPB Manager for data encryption. The SPB Manager shall set the selected algorithmIdentifier into aSspCryptoToBeUsed. If none of the algorithmIdentifier in the aCipherAlgorithmList is supported, the SPB Manager shall return eNotSupportedEncryptionAlgorithm. RQ1206_151a 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 5) Using the selected SspCryptoInfo data structure, choose the following: a) An SPB Manager certificate for key agreement that can be verified by the trusted public key indicated by one of the trusted public key identifiers in the aSspPkIdListForSpbmVerification. If none of the trusted public key identifiers in the aSspPkIdListForSpbmVerification is supported, the SPB Manager shall return eNotSupportedPkIdSpbmVerification.The algorithmIdentifier of the selected certificate shall be one of the algorithmIdentifier in aKeyAgreementAlgorithmList. If the algorithmIdentifier of the selected certificate is not supported, the SPB Manager shall return eNotSupportedKeyAgreementAlgorithm. RQ1206_151b 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 5) Using the selected SspCryptoInfo data structure, choose the following: b) An SPB Manager certificate for digital signature that can be verified by the trusted public key indicated by one of the trusted public key identifiers in the aSspPkIdListForSpbmVerification. If any trusted public key identifiers in the aSspPkIdListForSpbmVerification is not supported, the SPB Manager shall return eNotSupportedPkIdSpbmVerification. RQ1206_151c 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 5) Using the selected SspCryptoInfo data structure, choose the following: c) One of trusted public key identifier(s) in the aSspPkIdListForSpblVerification that shall be used by the Secondary Platform Bundle Loader to select its certificate(s). The SPB Manager shall set the selected trusted public key identifier into aSspCiPkIdToBeUsed. If any trusted public key identifiers in the aSspPkIdListForSpblVerification is not supported, the SPB Manager shall return eNotSupportedPkIdSpblVerification. RQ1206_151d 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 5) Using the selected SspCryptoInfo data structure, choose the following: d) One of algorithmIdentifiers in the aCipherAlgorithmList that shall be used by the Secondary Platform Bundle Loader and the SPB Manager for data encryption. The SPB Manager shall set the selected algorithmIdentifier into aSspCryptoToBeUsed. If none of the algorithmIdentifier in the aCipherAlgorithmList is supported, the SPB Manager shall return eNotSupportedEncryptionAlgorithm. RQ1206_152 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 6) Generate a new random octet string for aChallengeS which shall be used to authenticate the Secondary Platform Bundle Loader. RQ1206_153 12.6.4.2.2 On reception of "Si2.GetSpbmCertificate" function command, the SPB Manager shall: 7) Build Si2GetSpbmCertificateResponse containing the SPB Manager certificate for key agreement, the aSspCiPkIdToBeUsed, the aSspCryptoToBeUsed, aChallengeS, and the aSpbFamilyId and optionally the certificate chain for SPB Manager certificate for key agreement. RQ1206_154 12.6.4.2.3 The body part of the HTTP POST response for the "Si2.GetSpbmCertificate" function shall contain Si2GetSpbmCertificateResponse defined as follows: • aSspPkIdForSpblVerification: CI Public Key identifier for SPBL Certificate which shall be used by the Secondary Platform Bundle Loader for signature generation. • aSspCryptoToBeUsed: algorithm identifiers for data encryption which shall be used by the Secondary Platform Bundle Loader and the SPB Manager. • aSpbmKaCert: SPBM certificate for key agreement. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 61 Release 15 Req.ID Clause Description • aSpbFamilyId: the family identifier of the Secondary Platform Bundle. • CustodianOid: the OID of a custodian for the aSpbFamilyId. • aChallengeS: the value of CHALLENGE_S as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. The aChallengeS is generated by the SPB Manager and used in authentication of the Secondary Platform Bundle Loader. • aSpbmCertChain: the certificates to be used to construct certification path for verification of SPBM certificate for key agreement. 12.6.4.3 Si2.GetBoundSpbImage RQ1206_155 12.6.4.3.1 The "Si2.GetBoundSpbImage" function shall be used by the LBA during the download procedure as defined in clause 12.3.3 of ETSI TS 103 666-2 [10]. RQ1206_156 12.6.4.3.1 The LBA shall use "Si2.GetBoundSpbImage" function to provide the SPB Manager with SSP credential (SspCredential) as defined in clause 12.6.2.4 of ETSI TS 103 666-2 [10] and terminal information (TerminalInfo) as defined in clause 12.6.2.7 of ETSI TS 103 666-2 [10]. RQ1206_157 12.6.4.3.1 The LBA shall provide RequestType to the SPB Manager to indicate the request type. The LBA shall set: • "RequestBoundSpbImage" to the RequestType if the LBA requests a bound Secondary Platform Bundle image. • "RequestSpbMetadata" to the RequestType if the LBA requests only SPB metadata before requesting a bound Secondary Platform Bundle image to check the SPB metadata and, if configured, require the user intent. • "BoundSpbImageByTransacId" to the RequestType if the LBA requests a bound Secondary Platform Bundle image after receiving the SPB metadata via "Si2.GetBoundSpbImage" function with "RequestSpbMetadata" as the requestType. RQ1206_158 12.6.4.3.1 The body part of the HTTP POST request for the "Si2.GetBoundSpbImage" function command shall contain Si2GetBoundSpbImageCommand defined as follows: • aSspCredential: − SSP credential as defined in clause 12.6.2.4 of ETSI TS 103 666-2 [10] • aTerminalInfo: − Terminal Information as defined in clause 12.6.2.7 of ETSI TS 103 666-2 [10] • aRequestType: − eRequestBoundSpbImage − eRequestSpbMetadata − eBoundSpbImageByTransacId RQ1206_159 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: a) Extract the aSpbmKaPkIdToBeUsed contained in the aSspImageSessionToken in the aSspCredential. RQ1206_160 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: b) Selecta aSpbmKaCertificate which can be verified by the CI certificate indicated in aSpbmKaPkIdToBeUsed. RQ1206_161 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: c) Generate the first session key as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. The first session key shall be generated by using the private key corresponding to the SPB Manager certificate for key agreement and the aEPkSpblKa contained in the aTbsSspImageSessionToken in the aSspCredential. NOTE: The first session key is the same as 'KS1' in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 62 Release 15 Req.ID Clause Description RQ1206_162 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: d) Decrypt the aM-SSP contained in the aSspCredential by using the first session key. The SPB Manager shall use the algorithm identified by the aSspCryptoToBeUsed. The SPB Manager shall obtain the Secondary Platform Bundle Loader certificate, aTbsSspToken, and the signature of TbsSspToken by decrypting the aM-SSP. RQ1206_163 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: e) Verify the Secondary Platform Bundle Loader certificate by using the trust public key which is identified by the aSspPkIdForSpblVerification. The Secondary Platform Bundle Loader certificate shall be verified based on the certification path verification as defined in clause 12.2.1.1.4 of ETSI TS 103 666-2 [10]. If the verification fails, the SPB Manager shall return eInvalidSpblCertificate. RQ1206_164 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: f) Verify the aSspImageSessionTokenSignature and aTbsSspTokenSignature by using the Secondary Platform Bundle Loader certificate. RQ1206_165 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: g) Store the aIdTransac contained in the aTbsSspImageSessionToken and attach aChallengeS to the aIdTransac to manage this on-going image session. RQ1206_166 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: h) Find the Secondary Platform Bundle identifier corresponding to the aCodeM contained in the aTbsSspToken. If there is not the Secondary Platform Bundle identifier corresponding to aCodeM, the SPB Manager shall call the "Si1.HandleNotification" function. The function command shall contain the aNotificationEvent, the aCodeM, the aSspInfoProtected and aTerminalInfo. The aNotificationEvent shall be set to eNotificationStatus_Eligibility. The SPB Manager shall suspend the bound SPB image download procedure until the service provider has completed the Secondary Platform Bundle selection process as defined in clause 12.3.2.2 of ETSI TS 103 666-2 [10]. RQ1206_167 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: i) Perform the eligibility check based on Annex C by using the aSspInfoProtected contained in aTbsSspToken and aTermianlInfo. The SPB Manager shall: • Verify the aPpIdentifier contained in the aSspInfoProtected. • Verify the aFamilySpecificSspInfoBlock contained in the aSspInfoProtected (out of scope of the present document). • Verify the aFamilySpecificTerminalInfo and aOidSpecificInfo contained in the aTermianlInfo (out of scope of the present document). • Check whether the selected Secondary Platform Bundle image is supported by the iSSP based on aPpIdentifier, aSspInfoProtected, and aTerminalInfo. If the selected Secondary Platform Bundle image is not supported, the SPB Manager shall return eInvalidSpbImage. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 63 Release 15 Req.ID Clause Description RQ1206_168 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: j) Build aSpbMetadata corresponding to the selected Secondary Platform Bundle image (out of scope of the present document). The SPB Manager may construct aFamilySpecificData and aOidSpecificData in aSpbMetadata based on aFamilySpecificSspInfoBlock and aFamilySpecificTerminalInfoBlock contained in Si2GetBoundSpbImageCommand. RQ1206_169 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 1) If the value of aRequestType is "eRequestBoundSpbImage (0)" or "eRequestSpbMetadata (1)", the SPB Manager shall: k) If the aRequestType is "eRequestSpbMetadata (1)", the SPB Manager shall: • Bind the aSspCredential to the aIdTransac. • Return aSpbMetadata to the LBA as the response of the "Si2.GetBoundSpbImage" function. RQ1206_170 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 2) If the aRequestType is " eBoundSpbImageByTransacId (2)", the SPB Manager shall verify that the aSspCredential is verified in step 1 with aRequestType set to "eRequestSpbMetadata (1)". If the verification fails, the SPB Manager shall return eInvalidBoundSpbImageByTransacId. RQ1206_171 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: a) Generate TIME_STAMP and generate aM-TimeStamp by encrypting the TIME_STAMP by using the first session key and the encryption algorithm identified by the aSspCyrptoToBeUsed determined in the capability negotiation procedure as defined in clause 12.3.3.1 of ETSI TS 103 666-2 [10]. RQ1206_172 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: b) Generate an SPB Manager's ephemeral key pair. The domain parameter used to generate the ephemeral key pair shall be the same as the one used by the SPB Manager certificate for key agreement. RQ1206_173 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: c) Generate the second session key as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. The second session key shall be generated with the SPB Manager's ephemeral private key and the aEPkSpblKa contained in aTbsSspImagesessionToken. NOTE: The second session key is the same as 'KS2' in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_174 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: d) Generate aSpbmToken data structure containing the SPB Manager's ephemeral public key and the aIdTransac as defined in clause 12.6.2.5 of ETSI TS 103 666-2 [10]. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 64 Release 15 Req.ID Clause Description RQ1206_175 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: e) Select an SPB Manager certificate for digital signature which can be verified by the trusted public key indicated by one of the trusted public key identifiers in the aSspPkIdListForSpbmVerification. The selected SPB Manager certificate for digital signature shall be verified by the same trusted public key as the one used to verify the SPB Manager certificate for key agreement determined by the "Si2.GetSpbmCertificate" function. RQ1206_176 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: f) Compute the aSpbmTokenSignature over the aTbsSpbmToken using the private key corresponding to the SPB Manager certificate for digital signature. RQ1206_177 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: g) Obtain aM-IMD by encrypting the Image Descriptor (IMD) by using the second session key as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_178 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: h) Obtain aM-ARP by encrypting the ATK.ARP.ECDSA by using the second session key as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_179 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: i) Build aDoOperateParameter data structure as defined in clause 12.6.2.5 of ETSI TS 103 666-2 [10]. RQ1206_180 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: j) Build aChangeSegmentParameters data structure as defined in clause 12.6.2.5 of ETSI TS 103 666-2 [10]. The aChangeSegmentParameters shall be the list of ChangeSegmentParameters. Each ChangeSegmentParameter shall be generated by encrypting the Segment Descriptor Structure by using the second session key as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_181 12.6.4.3.2 Void RQ1206_182 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: k) Build aBoundSpbImage data structure as defined in clause 12.6.2.5. of ETSI TS 103 666-2 [10]. RQ1206_183 12.6.4.3.2 On reception of the Si2.GetBoundSpbImage function command, the SPB Manager shall check the value of the aRequestType contained in the Si2GetBoundSpbImage and perform the procedure as described below: 3) After successfully finishing the above steps, the SPB Manager shall: l) Return the aBoundSpbImage data structure to the LBA as the response of the "Si2.GetBoundSpbImage" function. RQ1206_184 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" shall contain Si2GetBoundSpbImageResponse defined as follows: • aBoundSpbImage: Secondary Platform Bundle image bound to the Secondary Platform Bundle Loader. • aSpbMetadata: the SPB metadata of the Secondary Platform Bundle corresponding to the aCodeM. • aSi2GetBoundSpbImageErrorCode: ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 65 Release 15 Req.ID Clause Description − eInvalidSpblCertificate: the error indicating that the SPBL certification path could not be verified. − eInvalidCodeM: the error indicating that the aCodeM has not been reserved by the Service Provider. − eInvalidChallengeS: the error indicating that aChallengeS is not valid in this image session. − eInvalidSpbImage: the error indicating that the Secondary Platform Bundle corresponding to the aCodeM is not compatible with the SSP. − eInvalidBoundSpbImageByTransacId: the error indicating that the aSspCredential containing this aIdTransac has not been verified with aRequestType set to "eRequestSpbMetadata (1)". − aSpbFamilyId: the family identifier of the Secondary Platform Bundle referenced by the aCodeM. − aFamilySpecificError: a family identifier-specific error container which may be defined for the aSpbFamilyId. − aOidSpecificError: a family identifier-specific error container which may be defined by the custodian indicated in aOid contained in aOidSpecificError. RQ1206_184a 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" may contain error codes in the Si2GetBoundSpbImageResponse as defined as follows: • aSi2GetBoundSpbImageErrorCode: − eInvalidSpblCertificate: the error indicating that the SPBL certification path could not be verified. RQ1206_184b 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" may contain error codes in the Si2GetBoundSpbImageResponse as defined as follows: • aSi2GetBoundSpbImageErrorCode: − eInvalidCodeM: the error indicating that the aCodeM has not been reserved by the Service Provider. RQ1206_184c 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" may contain error codes in the Si2GetBoundSpbImageResponse as defined as follows: • aSi2GetBoundSpbImageErrorCode: − eInvalidChallengeS: the error indicating that aChallengeS is not valid in this image session. RQ1206_184d 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" may contain error codes in the Si2GetBoundSpbImageResponse as defined as follows: • aSi2GetBoundSpbImageErrorCode: − eInvalidSpbImage: the error indicating that the Secondary Platform Bundle corresponding to the aCodeM is not compatible with the SSP. RQ1206_184e 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" may contain error codes in the Si2GetBoundSpbImageResponse as defined as follows: • aSi2GetBoundSpbImageErrorCode: − eInvalidBoundSpbImageByTransacId: the error indicating that the aSspCredential containing this aIdTransac has not been verified with. RQ1206_184f 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" may contain error codes in the Si2GetBoundSpbImageResponse as defined as follows: • aFamilySpecificError: a family identifier-specific error container which may be defined for the aSpbFamilyId. RQ1206_184g 12.6.4.3.3 The body part of the HTTP POST response of the "Si2.GetBoundSpbImage" may contain error codes in the Si2GetBoundSpbImageResponse as defined as follows: • aOidSpecificError: a family identifier-specific error container which may be defined by the custodian indicated in aOid contained in aOidSpecificError. 12.6.4.4 Si2.HandleNotification RQ1206_185 12.6.4.4.1 The "Si2.HandleNotification" function shall be used by the LBA to send any notification about the result of the Secondary Platform Bundle management to the SPB Manager. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 66 Release 15 Req.ID Clause Description RQ1206_186 12.6.4.4.1 The body part of the HTTP POST request for the "Si2.HandleNotification" function command shall contain Si2HandleNotificationCommand defined as follows: • aNotificationEvent: it indicates the procedure related to this notification. • aTimeStamp: it indicates the time when this notification message is constructed by the LBA. • aSpbId: identifier of the Secondary Platform Bundle related to aNotificationEvent. • aNotificationToken: notification token which contains the information about the state change of the Secondary Platform Bundle container in the iSSP as defined in clause 12.6.2.8 of ETSI TS 103 666-2 [10]. • aCodeM: the CodeMatching identifier linked with the Secondary Platform Bundle to download. If the Si2NotificationEvent is 'eNotificationStatus_SPBInstallationError', this parameter shall be present. • aFamilySpecificNotificationCommand: family identifier-specific Si2HandleNotificationCommand which may be defined for that family identifier. How this parameter is handled by the SPB Manager is out of scope of the present document. • aCustodianSpecificNotificationCommand: Custodian-specific Si2HandleNotificationCommand which may be defined by a custodian identified by aOid inside the aCustodianSpecificNotificationCommand. RQ1206_187 12.6.4.4.2 On reception of Si2HandleNotificationCommand, the SPB Manager shall respond to the LBA to notify a successful reception of the notification. The response may contain a family identifier-specific notification response or a custodianspecific notification response. RQ1206_188 12.6.4.4.3 The body part of the HTTP POST response for the "Si2.HandleNotification" function shall contain Si2HandleNotificationResponse defined as follows: • aFamilySpecificNotificationResponse: a family identifier-specific Si2HandleNotificationResponse which may be defined for that family identifier. • aCustodianSpecificNotificationResponse: a custodian-specific Si2HandleNotificationResponse which may be defined by the custodian identified by aOid inside the aCustodianSpecificNotificationResponse. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.10.9 Interfaces and functions - Si3 interface | Reference: ETSI TS 103 666-2 [10] clause 12.6.5. Req.ID Clause Description 12.6.5.1 Overview RQ1206_274 12.6.5.1 The Si3 interface is used between the LBA and the Secondary Platform Bundle Loader. The LBA shall use the Si3 interface to transfer a bound Secondary Platform Bundle image and management commands to the Secondary Platform Bundle Loader. RQ1206_189 12.6.5.1 The OFL agent host in the LBA and the OFL service hosted in the Secondary Platform Bundle Loader shall exchange commands, responses, and events over the Si3 interface as defined in as defined in GlobalPlatform VPP - OFL VNP Extension [16] with the additional commands, responses and registry defined in clauses 12.6.5.2, 12.6.5.3 and 12.6.5.4 of ETSI TS 103 666-2 [10]. RQ1206_190 12.6.5.2 The OFL service Gate in the Secondary Platform Bundle Loader shall support the commands defined in clause 7.3.1.3 of ETSI TS 103 666-2 [10]. RQ1206_191 12.6.5.3 The OFL service Gate in the Secondary Platform Bundle Loader shall support the commands defined in clause 7.3.1.3 of ETSI TS 103 666-2 [10]. RQ1206_192 12.6.5.4 The OFL service Gate in the Secondary Platform Bundle Loader shall support the responses defined in clause 7.3.1.4 of ETSI TS 103 666-2 [10]. 12.6.5.5 Functions 12.6.5.5.1 Si3.GetSspInfo RQ1206_193 12.6.5.5.1 The "Si3.GetSspInfo" function shall be used by the LBA during the capability negotiation procedure as defined in clause 12.3.3.1 of ETSI TS 103 666-2 [10]. RQ1206_194 12.6.5.5.1 The LBA shall use the "Si3.GetSspInfo" function to retrieve aSspInfoPublic from the Secondary Platform Bundle Loader. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 67 Release 15 Req.ID Clause Description RQ1206_195 12.6.5.5.1 The "Si3.GetSspInfo" function command shall be GET_SSP_INFO. The parameter of GET_SSP_INFO command is defined as follows: On reception of the "Si3.GetSspInfo" function command, the Secondary Platform Bundle Loader shall: 1) Set the GET_SSP_INFO command parameter into the GET_SSP_INFO_PARAMETER registry. RQ1206_196 12.6.5.5.1 The parameter of GET_SSP_INFO command is defined as follows: On reception of the "Si3.GetSspInfo" function command, the Secondary Platform Bundle Loader shall: 2) Build aSspInfoPublic data structure defined in clause 12.6.2.2.2 of ETSI TS 103 666-2 [10] as follows: a) The Secondary Platform Bundle Loader shall set the release of the specification that is implemented by the Secondary Platform Bundle Loader into the aSpblSpecVerInfo. RQ1206_197 12.6.5.5.1 The parameter of GET_SSP_INFO command is defined as follows: On reception of the "Si3.GetSspInfo" function command, the Secondary Platform Bundle Loader shall: 2) Build aSspInfoPublic data structure defined in clause 12.6.2.2.2 of ETSI TS 103 666-2 [10] as follows: b) If GET_SSP_INFO contains both the aSpbFamilyId and the aCustodianOid, the Secondary Platform Bundle Loader shall build aSspInfoPublic containing: • One aSspFamilyCryptoInfoBlock which shall contain the aSpbFamilyId and only one aSspOidCryptoInfoBlock if there is a configuration for both of the aSpbFamilyId and the aOid. The aSspOidCryptoInfoBlock shall have aCustodianOid and aSspOidCryptoInfo which contains the list of trusted public key identifiers and the list of algorithm identifiers which are allowed to be used for loading of the Secondary Platform Bundles with that aSpbFamilyId and that aCustodianOid. • One aSspFamilyCryptoInfoBlock which shall contain the aSpbFamilyId and aSspFamilyCryptoInfo if there is a configuration for the aSpbFamilyId but not for the aCustodianOid. The aSspFamilyCryptoInfo shall contain the list of trusted public key identifiers and the list of algorithm identifiers which are allowed to be used for loading of the Secondary Platform Bundles with that aSpbFamilyId. • aSspGeneralCryptoInfo if there is no configuration for the aSpbFamilyId. The aSspGeneralCryptoInfo shall contain the list of trusted public key identifiers and the list of algorithm identifiers which are not associated with any family identifier and any custodian. RQ1206_198 12.6.5.5.1 The parameter of GET_SSP_INFO command is defined as follows: On reception of the "Si3.GetSspInfo" function command, the Secondary Platform Bundle Loader shall: 2) Build aSspInfoPublic data structure defined in clause 12.6.2.2.2 of ETSI TS 103 666-2 [10] as follows: c) If GET_SSP_INFO command parameter contains only aSpbFamilyId, the Secondary Platform Bundle Loader shall build aSspInfoPublic containing: • One aSspFamilyCryptoInfoBlock which shall contain the aSpbFamilyId if there is a configuration for the aSpbFamilyId. The aSspFamilyCryptoInfoBlock may contain the set of aSspOidCryptoInfoBlocks as many as the configurations for the custodians of that aSpbFamilyId. Each aSspOidCryptoInfoBlock shall have aCustodianOid and aSspOidCryptoInfo which contains the list of trusted public key identifiers and the list of algorithm identifiers which are allowed to be used for loading of the Secondary Platform Bundles with that aSpbFamilyId and that aCustodianOid. The aSspFamilyCryptoInfoBlock may also contain aSspFamilyCryptoInfo. • aSspGeneralCryptoInfo if there is no configuration for the aSpbFamilyId. The aSspGeneralCryptoInfo shall contain the list of trusted public key identifiers and the list of algorithm identifiers which are not associated with any family identifier and any custodian. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 68 Release 15 Req.ID Clause Description RQ1206_199 12.6.5.5.1 The parameter of GET_SSP_INFO command is defined as follows: On reception of the "Si3.GetSspInfo" function command, the Secondary Platform Bundle Loader shall: 2) Build aSspInfoPublic data structure defined in clause 12.6.2.2.2 of ETSI TS 103 666-2 [10] as follows: d) If GET_SSP_INFO command parameter is empty, the Secondary Platform Bundle Loader shall build aSspInfoPublic containing: • SspFamilyCryptoInfoBlock data structures as many as the number of family identifiers supported by the Secondary Platform Bundle Loader. Each SspFamilyCryptoInfoBlock data structure may contain aSspFamilyCryptoInfo. Each SspFamilyCrytoInfoBlock data structure may contain the set of SspOidCryptoInfoBlock data structures as many as custodians supported by the Secondary Platform Bundle Loader for the family identifier contained in the SspFamilyCryptoInfoBlock data structure. Each SspOidCryptoInfoBlock data structure shall contain the aCustodianOid and aSspOidCryptoInfo. The Secondary Platform Bundle Loader may include aSspGeneralCryptoInfo. RQ1206_200 12.6.5.5.1 The parameter of GET_SSP_INFO command is defined as follows: On reception of the "Si3.GetSspInfo" function command, the Secondary Platform Bundle Loader shall: 3) Return ANY_OK with the aSspInfoPublic. 12.6.5.5.2 Si3.SetSpbmCredential RQ1206_201 12.6.5.5.2 The "Si3.SetSpbmCredential" function shall be used by the LBA during the bound SPB image download procedure as defined in clause 12.3.3.2 of ETSI TS 103 666-2 [10]. RQ1206_202 12.6.5.5.2 The LBA shall use "Si3.GetSspCredential" function to deliver aSpbmCredential to the Secondary Platform Bundle Loader. RQ1206_203 12.6.5.5.2 The "Si3.SetSpbmCredential" function command shall be ANY_SET_PARAMETER command defined in ETSI TS 103 666-2 [10], clause 8.5.4 which allows the LBA to update the registry. RQ1206_204 12.6.5.5.2 The parameter of ANY_SET_PARAMETER command shall contain the index of IDS_CREDENTIAL_PARAMETER registry and the aSpbmCredential data structure defined in clause 12.6.2.3 of ETSI TS 103 666-2 [10]. RQ1206_205 12.6.5.5.2 The LBA shall build the aSpbmCredential containing the aSpbFamilyId, the aSpbmKaCertificates, the aSspCiPkIdToBeUsed, and the aSspCryptoToBeUsed contained in the aSi2GetSpbmCertificateResponse. RQ1206_206 12.6.5.5.2 On reception of the "Si3.SetSpbmCredential" command, the Secondary Platform Bundle Loader shall: 1) Set the received SpbmCredential data structure to the IDS_CREDENTIAL_PARAMETER registry. RQ1206_207 12.6.5.5.2 On reception of the "Si3.SetSpbmCredential" command, the Secondary Platform Bundle Loader shall: 2) Verify the received elements as follows: a) Verify that the aSpbmKaCertificates contained in the aSpbmCredential based on the certification path verification as defined in clause 12.2.1.1.4 of ETSI TS 103 666-2 [10]. The trusted public key used to verify the aSpbmKaCertificates shall be allowed to be used for loading the Secondary Platform Bundles with the aSpbFamilyId and aCustodianOid contained in the aSpbmCredential. b) Verify that the aSspCiPkIdToBeUsed is supported by itself for the loading of the Secondary Platform Bundles with the aSpbFamilyId and the aCustodianOid contained in the aSpbmCredential. c) Verify that the aSspCryptoToBeUsed is supported by itself for the loading of the Secondary Platform Bundles with the aSpbFamilyId and the aCustodianOid contained in the aSpbmCredential. RQ1206_208 12.6.5.5.2 On reception of the "Si3.SetSpbmCredential" command, the Secondary Platform Bundle Loader shall: 3) Select the appropriate Secondary Platform Bundle Loader certificate that shall be verifiable by the trusted public key which is indicated by the aSspCiPkIdToBeUsed contained in the aSpbmCredential. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 69 Release 15 Req.ID Clause Description RQ1206_209 12.6.5.5.2 On reception of the "Si3.SetSpbmCredential" command, the Secondary Platform Bundle Loader shall: 4) Generate the following: a) A Secondary Platform Bundle Loader's ephemeral key pair. The domain parameter used to generate the ephemeral key pair shall be the same as the one indicated by the SubjectPublicKeyInfo in the SPB Manager certificate for key agreement contained in aSpbmCredential. b) ID_TRANSAC as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. c) aTbsSspImageSessionToken as defined in clause 12.6.2.4 of ETSI TS 103 666-2 [10]. d) aSspImageSessionTokenSignature by signing the aTbsSspImageSessionTokenwith the private key of the SPB Manager corresponding to the SPB Manager certificate for digital signature. e) The first session key as defined in Global Platform Open Firmware Loader for Tamper Resistant Element [13]. The first session key shall be generated with the Secondary Platform Bundle Loader's ephemeral private key and the public key contained in the SPB Manager certificate for key agreement. NOTE: The first session key is the same as 'KS1' in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_210 12.6.5.5.2 On reception of the "Si3.SetSpbmCredential" command, the Secondary Platform Bundle Loader shall: 4) Generate the following: f) aSspInfoProtected as defined in clause 12.6.2.2.3 of ETSI TS 103 666-2 [10]. g) aTbsSspToken containing aCodeM, aChallengeS and aSspInfoProtected which shall be protected. The aCodeM and aChallengeS shall be the same as those in the aSpbmCredential contained in GET_SSP_CREDENTIAL command parameter. h) aTbsSspTokenSignature by signing the TbsSspToken with the private key of the SPB Manager corresponding to the SPB Manager certificate for digital signature. i) aM-SSP as defined in clause 12.6.2.4 of ETSI TS 103 666-2 [10]. The aM- SSP shall be generated by encrypting the aTbsSspToken, the aTbsSspTokenSignature, and the Secondary Platform Bundle Loader certificate for digital signature. The encryption algorithm indicated by the aSspCryptoToBeUsed and the first session key shall be used to generate the aM-SSP. j) aSspInfoProtected as defined in clause 12.6.2.2.3 of ETSI TS 103 666-2 [10]. RQ1206_211 12.6.5.5.2 On reception of the "Si3.SetSpbmCredential" command, the Secondary Platform Bundle Loader shall: 5) Generate aSspCredential as defined in clause 12.6.2.4 of ETSI TS 103 666-2 [10] and set the aSspCredential into the TRE_CREDENTIAL_PARAMETER registry. RQ1206_212 12.6.5.5.2 On reception of the "Si3.SetSpbmCredential" command, the Secondary Platform Bundle Loader shall: 6) Return ANY_OK with the GetSspCredentialResponse data structure to the LBA. 12.6.5.5.3 Si3.LoadBoundSpbInfo RQ1206_213 12.6.5.5.3 The "Si3.LoadBoundSpbInfo" function shall be used by the LBA during the installation procedure as defined in clause 12.3.4 of ETSI TS 103 666-2 [10]. RQ1206_214 12.6.5.5.3 The LBA shall use the "Si3.LoadBoundSpbInfo" function to provide the Secondary Platform Bundle Loader with the aDoOperateParameter contained in the bound SPB image received from the SPB Manager as the response of the "Si2.GetBoundSpbImage" function. RQ1206_215 12.6.5.5.3 The "Si3.LoadBoundSpbInfo" function command shall be OFL_DO_OPERATE as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_216 12.6.5.5.3 The parameter of OFL_DO_OPERATE command shall be aDoOperateParameter defined in clause 12.6.2.5 of ETSI TS 103 666-2 [10]. RQ1206_217 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 1) Verify the aSpbmCerts contained in the aDoOperateParameter based on the certification path verification as defined in clause 12.2.1.1.4 of ETSI TS 103 666-2 [10]. The trusted public key used to verify the aSpbmCerts shall be the same as the one used to verify the aSpbmKaCertificates. RQ1206_218 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 2) Verify the aSpbmTokenSignature contained in the aSpbmToken by using the SPB Manager certificate for digital signature. The SPB Manager certificate for digital signature shall be the last certificate in the aSpbmCerts. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 70 Release 15 Req.ID Clause Description RQ1206_219 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 3) Verify that the aIdTransac contained in the aTbsSpbmToken matches to the previously generated ID_TRANSAC. RQ1206_220 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 4) Generate the second session key as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. The second session key shall be generated with the aEPkSpbmKa contained in the aTbsSpbmToken and the Secondary Platform Bundle Loader's ephemeral private key. NOTE: The second session key is the same as 'KS2' in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_221 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 5) Obtain the TIME_STAMP by decrypting the aM-TimeStamp by using the first session key and the encryption algorithm indicated by the aEncryptionType as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_222 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 6) Obtain the ATK.ARP.DS by decrypting the aM-ARP by using the second session key and the encryption algorithm indicated by the aEncryptionType as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_223 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 7) Obtain Image Descriptor by decrypting the aM-IMD by using the second session key and the encryption algorithm indicated by the aEncryptionType as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. RQ1206_224 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 8) Verify the Image Descriptor as follows: a) Verify that the family identifier contained in the Image Descriptor matches to the value of the family identifier in SSP_INFO_PUBLIC registry. RQ1206_225 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 9) Verify the aSpbMetadata as follows: a) Verify that the family identifier contained in the aSpbMetadata matches to the value of the family identifier in SSP_INFO_PUBLIC registry. b) Verify that the aSpbId contained in the aSpbMetadata matches to the value of the public UUID of the image contained in the Image Descriptor. c) Verify the aFamilySpecificData and aOidSpecificMetadata (out of scope of the present document). RQ1206_226 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 10) Verify that the trusted public key used to verify the SPB Manager certificate is one of the trusted public keys supported by the Secondary Platform Bundle Loader used to load the Secondary Platform Bundle according to the rules below: a) if the Secondary Platform Bundle family identifier is not part of any SspFamilyCryptoInfoBlock: • the keys in aSspGeneralCryptoInfo. b) Else: • the keys in aSspFamilyCryptoInfo, if none of the custodian OIDs in aSpbMetadata (either aCustodianOid or in aSupportedCustodianList) is part of any aSspOidCryptoInfoBlock; • else, the keys in aSspOidCryptoInfo of the SspOidCryptoInfoBlock data structure which the custodian OID has been found in aSpbMetadata. RQ1206_226a 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 10) Verify that the trusted public key used to verify the SPB Manager certificate is one of the trusted public keys supported by the Secondary Platform Bundle Loader used to load the Secondary Platform Bundle, if the Secondary Platform Bundle family identifier is not part of any SspFamilyCryptoInfoBlock: • the keys in aSspGeneralCryptoInfo. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 71 Release 15 Req.ID Clause Description RQ1206_226b 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 10) Verify that the trusted public key used to verify the SPB Manager certificate is one of the trusted public keys supported by the Secondary Platform Bundle Loader used to load the Secondary Platform Bundle if the Secondary Platform Bundle family identifier is part of any SspFamilyCryptoInfoBlock: • the keys in aSspFamilyCryptoInfo, if none of the custodian OIDs in aSpbMetadata (either aCustodianOid or in aSupportedCustodianList) is part of any aSspOidCryptoInfoBlock; • else, the keys in aSspOidCryptoInfo of the SspOidCryptoInfoBlock data structure which the custodian OID has been found in aSpbMetadata. RQ1206_227 Void RQ1206_228 Void RQ1206_229 12.6.5.5.3 On reception of the "Si3.LoadBoundSpbInfo" function command, the Secondary Platform Bundle Loader shall: 11) Return ANY_OK without any parameters to the LBA. 12.6.5.5.4 Si3.LoadBoundSpbSds RQ1206_230 12.6.5.5.4 The "Si3.LoadBoundSpbSds" function shall be used by the LBA during the installation procedure as defined in clause 12.3.4 of ETSI TS 103 666-2 [10]. RQ1206_231 12.6.5.5.4 The LBA shall use the "Si3.LoadBoundSpbSds" function to provide the Secondary Platform Bundle Loader with an element of aChangeSegmentParameter contained in the bound SPB image received from the SPB Manager as the response of the "Si2.GetBoundSpbImage" function. RQ1206_232 12.6.5.5.4 The "Si3.LoadBoundSpbSds" function command shall be OFL_CHANGE_SEGMENT as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_233 12.6.5.5.4 The parameter of OFL_CHANGE_SEGMENT command shall be aChangeSegmentParameter defined in clause 12.6.2.5 of ETSI TS 103 666-2 [10]. RQ1206_234 12.6.5.5.4 On reception of the "Si3.LoadBoundSpbSds" function command, the Secondary Platform Bundle Loader shall decrypt aChangeSegmentParameter to obtain Segment Descriptor as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. The Secondary Platform Bundle Loader shall return ANY_OK to the LBA after successful decryption of the aChangeSegmentParameter. NOTE: The aChangeSegmentParameter is the same as the Segment Descriptor Structure defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. 12.6.5.5.5 Si3.LoadBoundSpbSeg RQ1206_235 12.6.5.5.5 The "Si3.LoadBoundSpbSeg" function shall be used by the LBA during the installation procedure as defined in clause 12.3.4 of ETSI TS 103 666-2 [10]. RQ1206_236 12.6.5.5.5 The LBA shall use the "Si3.LoadBoundSpbSeg" function to provide the Secondary Platform Bundle Loader with an element of aLoadSegmentParameter contained in the bound SPB image received from the SPB Manager as the response of the "Si2.GetBoundSpbImage" function. RQ1206_237 12.6.5.5.5 The "Si3.LoadBoundSpbSeg" function command shall be OFL_LOAD_SEGMENT as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_238 12.6.5.5.5 The parameter of OFL_LOAD_SEGMENT command shall be aLoadSegmentParameter defined in clause 12.6.2.5 of ETSI TS 103 666-2 [10]. RQ1206_239 12.6.5.5.5 On reception of the "Si3.LoadBoundSpbSeg" function command, the Secondary Platform Bundle Loader shall decrypt the aLoadSegmentParameter and install the decrypted segment into the iSSP as defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. The Secondary Platform Bundle Loader shall return ANY_OK to the LBA after the successful installation of the segment. NOTE: The aLoadSegmentParameter is the same as the Segment Structure defined in GlobalPlatform Open Firmware Loader for Tamper Resistant Element [13]. 12.6.5.5.6 Si3.GetSspCredential RQ1206_240 12.6.5.5.6 The "Si3.GetSspCredential" function shall be used by the LBA during the bound SPB image download procedure as defined in clause 12.3.3.2 of ETSI TS 103 666-2 [10]. RQ1206_241 12.6.5.5.6 The LBA shall use the "Si3.GetSspCredential" function to retrieve aSspCredential from the Secondary Platform Bundle Loader. RQ1206_242 12.6.5.5.6 The "Si3.GetSspCredential" function command shall be ANY_GET_PARAMETER command defined in ETSI TS 103 666-2 [10], clause 8.5.4 which allows the LBA to retrieve the value of the registry. RQ1206_243 12.6.5.5.6 The parameter of ANY_GET_PARAMETER command shall contain the index of TRE_CREDENTIAL_PARAMETER registry. RQ1206_244 12.6.5.5.6 On reception of the "Si3.GetSspCredential" command, the Secondary Platform Bundle Loader shall return ANY_OK with the value of TRE_CREDENTIAL_PARAMETER registry which contains aSspCredential. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 72 Release 15 Req.ID Clause Description 12.6.5.5.7 Si3.EnableSpb RQ1206_245 12.6.5.5.7 The "Si3.EnableSpb" function shall be used by the LBA for the procedure to enable a Secondary Platform Bundle as defined in clause 12.4.1 of ETSI TS 103 666-2 [10]. RQ1206_246 12.6.5.5.7 The LBA shall use the "Si3.EnableSpb" function to provide the Secondary Platform Bundle Loader with the Secondary Platform Bundle identifier to enable. RQ1206_247 12.6.5.5.7 The "Si3.EnableSpb" function command shall be OFL_ENABLE_FIRMWARE as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_248 12.6.5.5.7 The Secondary Platform Bundle identifier to enable shall be the Public Image UUID as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_249 12.6.5.5.7 If the Secondary Platform Bundle to enable is a Telecom Secondary Platform Bundle, the Secondary Platform Bundle Loader shall check the number of currently enabled Telecom Secondary Platform Bundles and operate depending on the value of TELECOM_CAPABILITY as follows: • If the number of currently enabled Telecom Secondary Platform Bundles is smaller than the value of TELECOM_CAPABILITY, the Secondary Platform Bundle Loader shall enable the Telecom Secondary Platform Bundle to enable. • Otherwise, the Secondary Platform Bundle Loader shall reject the "Si3.EnableSpb" command with an error indicating that enabling the Telecom Secondary Platform Bundle is limited by TELECOM_CAPABILITY. RQ1206_250 12.6.5.5.7 After successfully enabling the Secondary Platform Bundle, the Secondary Platform Bundle Loader shall update the value of the state to 'Enabled' in the Firmware session of that Secondary Platform Bundle. 12.6.5.5.8 Si3.DisableSpb RQ1206_251 12.6.5.5.8 The "Si3.DisableSpb" function shall be used by the LBA for the procedure to disable a Secondary Platform Bundle as defined in clause 12.4.2 of ETSI TS 103 666-2 [10]. RQ1206_252 12.6.5.5.8 The LBA shall use the "Si3.DisableSpb" function to provide the Secondary Platform Bundle Loader with the Secondary Platform Bundle identifier to disable. RQ1206_253 12.6.5.5.8 The "Si3.DisableSpb" function command shall be OFL_DISABLE_FIRMWARE as defined in GlobalPlatform VPP - OFL VNP Extension [11]. RQ1206_254 12.6.5.5.8 The Secondary Platform Bundle identifier to disable shall be the Public Image UUID as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_255 12.6.5.5.8 After successfully disabling the Secondary Platform Bundle, the Secondary Platform Bundle Loader shall update the value of the state to 'Disabled' in the Firmware session of that Secondary Platform Bundle. 12.6.5.5.9 Si3.DeleteSpb RQ1206_256 12.6.5.5.9 The "Si3.DeleteSpb" function shall be used by the LBA for the procedure to delete a Secondary Platform Bundle as defined in clause 12.4.3 of ETSI TS 103 666-2 [10]. RQ1206_257 12.6.5.5.9 The LBA shall use the "Si3.DeleteSpb" function to provide the Secondary Platform Bundle Loader with the Secondary Platform Bundle identifier to delete. RQ1206_258 12.6.5.5.9 The "Si3.DeleteSpb" function command shall be OFL_DELETE_SESSION as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_259 12.6.5.5.9 The Secondary Platform Bundle identifier to disable shall be the Public Image UUID as defined in GlobalPlatform VPP - OFL VNP Extension [16]. 12.6.5.5.10 Si3.GetSpbMetadata RQ1206_260 12.6.5.5.10 The "Si3.GetSpbMetadata" function shall be used by the LBA to retrieve the SPB metadata of a Secondary Platform Bundle container installed in the iSSP. RQ1206_261 12.6.5.5.10 The "Si3.GetSpbMetadata" function command shall be GET_SPB_METADATA. RQ1206_262 12.6.5.5.10 The parameter of GET_SPB_METADATA command is a Secondary Platform Bundle identifier. RQ1206_263 12.6.5.5.10 The Secondary Platform Bundle identifier shall be the Public Image UUID as defined in GlobalPlatform VPP - OFL VNP Extension [16]. RQ1206_264 12.6.5.5.10 On reception of the "Si3.GetSpbMetadata" function command, the Secondary Platform Bundle Loader shall: 1) find the firmware session which contains the Public Image UUID same as the received Secondary Platform Bundle identifier; 2) extract the SPB metadata contained in that firmware session; 3) return ANY_OK with the SPB metadata as the "Si3.GetSpbMetadata" function response. 12.6.5.5.11 Si3.UpdateSpbState RQ1206_265 12.6.5.5.11 The "Si3.UpdateSpbState" function shall be used by the LBA during the SPB state retrieving procedure as defined in clause 12.4.5 of ETSI TS 103 666-2 [10]. RQ1206_266 12.6.5.5.11 The LBA shall use "Si3.UpdatetSpbState" function to request the Secondary Platform Bundle Loader to update the value of SPB_ID registry. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 73 Release 15 Req.ID Clause Description RQ1206_267 12.6.5.5.11 The "Si3.UpdateSpbState" function command shall be ANY_SET_PARAMETER command defined in ETSI TS 103 666-1 [9], clause 8.5.4 which allows the LBA to update the registry. RQ1206_268 12.6.5.5.11 The parameter of ANY_SET_PARAMTER command shall contain the index of SPB_ID registry and the Secondary Platform Bundle identifier. RQ1206_269 12.6.5.5.11 On reception of the "Si3.UpdateSpbState" command, the Secondary Platform Bundle Loader shall: 1) Set the received Secondary Platform Bundle identifier (SpbId) to the SPB_ID registry. 2) Extract the SPB state from the firmware session which contains the Public Image UUID same as the received SpbId. 3) Update the SPB_STATE registry with the value of the extracted SPB state. 4) Return ANY_OK to the LBA as "Si3.UpdateSpbState" function response to the LBA. 12.6.5.5.12 Si3.GetSpbState RQ1206_270 12.6.5.5.12 The "Si3.GetSpbState" function shall be used by the LBA during the SPB state retrieving procedure as defined in clause 12.4.5 of ETSI TS 103 666-2 [10]. RQ1206_271 12.6.5.5.12 The "Si3.GetSpbState" function command shall be ANY_GET_PARAMETER command defined in ETSI TS 103 666-1 [9], clause 8.5.4 which allows the LBA to retrieve the value of the registry RQ1206_272 12.6.5.5.12 The parameter of ANY_GET_PARAMETER command shall contain the index of SPB_STATE registry. RQ1206_273 12.6.5.5.12 On reception of the "Si3.GetSpbState" command, the Secondary Platform Bundle Loader shall return ANY_OK with the value of SPB_STATE registry to the LBA. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.11 Requirements not covered by ETSI test descriptions | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.11.1 Requirements assigned to the Security Certification labs | As mentioned in clause 4.1.1 of the present document, Evaluation Level Assurance certification for the SSP Primary Platform and the SPB certification by composition on the Primary Platform, except for the SPB loader, is out of scope of the present document. Requirements the iSSP maker identifies to be fulfilled for the intended EAL best will be provided to a security certification lab, accredited by the certification body, where the verification can take place. Therefore, the following requirements will not be verified by tests defined in the present document: RQ number RQ number RQ number RQ number RQ number RQ number RQ0502_002 RQ0701_010 RQ0701_017 RQ0701_021 RQ0702_007 RQ1101_001 RQ0502_003 RQ0701_011 RQ0701_018 RQ0701_023 RQ0703_002 RQ1102_001 RQ0701_008 RQ0701_013 RQ0701_019 RQ0701_025 RQ0803_001 RQ1102_002 RQ0701_009 RQ0701_014 RQ0701_020 RQ0701_026 RQ1002_002 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.11.2 Requirements referencing GlobalPlatform specifications | Some requirements identified in ETSI TS 103 666-2 [10] are based on descriptions or specifications generated by GlobalPlatform. Services, interfaces and functionality described by GlobalPlatform specifications need to fulfill GlobalPlatform regulations. Therefore, the following requirements will not be verified by tests defined in the present document: RQ number RQ number RQ number RQ number RQ number RQ number RQ0601_001 RQ0701_001 RQ0701_007 RQ0702_002 RQ0703_008 RQ0902_001 RQ0602_001 RQ0701_002 RQ0701_015 RQ0702_003 RQ0703_010 RQ0902_002 RQ0603_001 RQ0701_003 RQ0701_016 RQ0702_004 RQ0703_015 RQ0903_001 RQ0604_001 RQ0701_004 RQ0701_022 RQ0702_005 RQ0706_001 RQ0904_001 RQ0605_001 RQ0701_005 RQ0701_028 RQ0702_006 RQ0801_001 RQ0606_001 RQ0701_006 RQ0702_001 RQ0703_006 RQ0802_001 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 74 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 5.11.3 Descriptive requirements and not explicitly testable requirements | Some requirements identified in ETSI TS 103 666-2 [10] are descriptive text. In some cases, it is not possible to explicitly verify requirements generated from descriptive text in other cases the verification of such requirements is out of scope of the present document. Implicitly verified and 'out of scope' requirements are identified and listed in the respective clauses. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 6 Security requirements and iSSP architecture testing | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 6.1 Configurations | There are no specific configurations defined for security requirements an iSSP architecture testing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 6.2 Procedures | There are no specific procedures defined for security requirements an iSSP architecture testing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 6.3 Test descriptions | There are no specific test descriptions defined for testing the Security requirements and iSSP architecture. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 6.4 Requirements verified elsewhere | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 6.4.1 Overview - Security requirements | The following requirements, identified in ETSI TS 103 666-2 [10] clause 5.2 are not tested in accordance with the present document, as they are either referencing requirements from other standardization bodies; best verified by a certified security certification laboratory outside the ETSI remits, or as they are descriptive without identifiable specific usage: RQ0502_001, RQ0502_002, RQ0502_003, RQ0502_004. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 6.4.2 iSSP Architecture | The following requirements, identified in ETSI TS 103 666-2 [10] clause 6 are not tested in accordance with the present document, as they are referencing requirements from another standardization body (GlobalPlatform): RQ0601_001, RQ0602_001, RQ0603_001, RQ0604_001, RQ0605_001, RQ0606_001. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7 Primary Platform | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1 Hardware Platform | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.1 Configurations | There are no specific configurations defined for hardware platform testing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.2 Procedures | There are no specific procedures defined for hardware platform testing. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 75 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.3 Test descriptions | There are no specific test descriptions defined for testing the Low-level Operating System. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4 Requirements not testable, implicitly verified or verified elsewhere | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.1 Architecture | The following requirements, identified in ETSI TS 103 666-2 [10] are not tested in accordance with the present document, as they are referencing requirements from another standardization body (GlobalPlatform): RQ0701_001, RQ0701_002, RQ0701_003, RQ0701_004. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.2 Security functions | The following requirements, identified in ETSI TS 103 666-2 [10] are not tested in accordance with the present document, as they are referencing requirements from another standardization body (GlobalPlatform): RQ0701_005, RQ0701_006, RQ0701_007, RQ0701_015, RQ0701_016. The following requirements, identified in ETSI TS 103 666-2 [10] are not tested in accordance with the present document: RQ0701_008, RQ0701_009, RQ0701_010, RQ0701_011, RQ0701_012, RQ0701_013, RQ0701_014, RQ0701_017, RQ0701_018. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.3 Memories | The following requirements, identified in ETSI TS 103 666-2 [10] are not tested in accordance with the present document, as they need to be verified by a security certification laboratory outside the ETSI domain (in accordance with BSI regulations): RQ0701_019, RQ0701_020, RQ0701_021. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.4 Cryptographic functions | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0701_0022. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.5 Clock | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it needs to be verified by a security certification laboratory outside the ETSI domain (in accordance with BSI regulations): RQ0701_023. The following requirement, identified in ETSI TS 103 666-2 [10] refers to descriptive text in ETSI TS 103 666-1 [9]. It shall be verified in accordance with tests defined for the clock signal in ETSI TS 103 999-1 [11] clause 6.3 (see note): RQ0701_024. NOTE: Check with the recent version of ETSI TS 103 999-1 [11] if appropriate tests are defined. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 76 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.6 SSP internal interconnect | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it needs to be verified by a security certification laboratory outside the ETSI domain (in accordance with BSI regulations): RQ0701_025. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.7 Secure CPU | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is recommended to be verified by a security certification laboratory outside the ETSI remits (e.g.: in accordance with BSI regulations): RQ0701_026. The following requirements, identified in ETSI TS 103 666-2 [10] are not tested in accordance with the present document, as they are referencing requirements from another standardization body (GlobalPlatform): RQ0701_027, RQ0701_028. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.1.4.8 Random Number Generator | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0701_029. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2 Low-level Operating System | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.1 Configurations | There are no specific configurations defined for low-level operating system testing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.2 Procedures | There are no specific procedures defined for low-level operating system testing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.3 Test descriptions | There are no specific test descriptions defined for testing the Low-level Operating System. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.4 Requirements not testable, implicitly verified or verified elsewhere | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.4.1 Introductions | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0702_001. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.4.2 Kernel objects | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0702_002. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 77 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.4.3 Global requirements and mandatory Access Control rules | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0702_003. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.4.4 Process states diagram | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0702_004. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.4.5 Definition of the process states | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0702_005. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.2.4.6 Mandatory access control | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing a requirement from another standardization body (GlobalPlatform): RQ0702_006. The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document: RQ0702_007. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3 Services | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.1 Configurations | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.1.1 CSVC_311 | Configuration ID CSVC_311 Configuration description Other host domain (Tester) SSP host domain (SUT) SSP host Other host Administation Administration Gate Identity Application Identity Application Gate Identity Service Identity Service Gate Administation Administration Gate ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 78 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.1.2 CSVC_312 | Configuration ID CSVC_312 Configuration description Other host domain (Tester) SSP host domain (SUT) SSP host Other host Administation Administration Gate SPBL Application SPBL Application Gate SPBL Service SPBL Service Gate Administation Administration Gate |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.2 Procedures | 7.3.2.1 PSVC_321 - Open a pipe session on the Identity Service Gate Procedure ID PSVC_321 Objectives The SSP host shall have implemented the registry entries of the OFL service gate defined in GlobalPlatform OFL VNP Extension [16]. Configuration reference CSVC_311 Initial conditions Test sequence Step Description 1 Administration gate sends EVT_ADM_BIND to Administration gate in the SSP with: • PIPEXY: a dynamically assigned pipe identifier for the identity service gate. • GATEIDENTITY: The UUID gate identifier of the identity gate (416B66AC-A134-5082-8160- FA1BA497F917). 2 Administration gate sends EVT_ADM_BIND to Administration gate in the other host with: • PIPEYX: a dynamically assigned pipe identifier for the identity application gate. • GATEIDENTITY: The UUID gate identifier of the identity gate (416B66AC-A134-5082-8160- FA1BA497F917). ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 79 Release 15 7.3.2.1 PSVC_322 - Open a pipe session on the SPBL Service Gate Procedure ID PSVC_322 Objectives The other host shall be able to open a pipe session to the service gate of the SSP host. The SPBL service identifier is defined as the OFL service identifier in GlobalPlatform OFL VNP extension [16]. Configuration reference CSVC_312 Initial conditions Test sequence Step Description 1 Administration gate sends EVT_ADM_BIND to Administration gate in the SSP with: • PIPEXY: a dynamically assigned pipe identifier for the SPBL service gate. • GATESPBL: The UUID gate identifier of the SPBL service gate (BB780E30-419A-5B71-9B98- 18A042E75899). 2 Administration gate sends EVT_ADM_BIND to Administration gate in the other host with: • PIPEYX: a dynamically assigned pipe identifier for the SPBL application gate. • GATESPBL: The UUID gate identifier of the identity gate (BB780E30-419A-5B71-9B98- 18A042E75899). 3 Identity application gate sends ANY_GET_PARAMETER command (pipe PIPEXY) to the identity service gate in the SSP host with the register '04'H. 4 Identity service gate sends ANY_GET_PARAMETER response (pipe PIPEYX) to the identity application gate in the other host. The service identifier 'BB780E30-419A-5B71-9B98-18A042E75899' shall be present. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3 Test descriptions | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1 Secondary Platform Bundle Loader | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.1 SVC_3311 - SPBL ARP state | Test ID SVC_3311 Test objectives To verify the availability and correct configuration of the ARP state from the extract of the OFL_DO_OPERATE command. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_PARAMETER (CODE_M ?) command for getting the initial SSP credentials parameter computed from the Service Provider parameter. 4 The SPBL service gate returns ANY_OK if the command is successfully executed. 5 The SPBL application gate sends the OFL_DO_OPERATE command with M3 encrypted by KS213 including ARP '02' to administrate the SSP (ARP management) to the SPBL host. 6 The SPBL service gate returns ANY_OK if the command is successfully executed. RQ0703_001 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 80 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.2 SVC_3312 - Registry entries in the SPBL Service Gate | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.3 SVC_3313 - Additional registry entries in the SPBL Service Gate | 7.3.3.1.4 SVC_3314 – Content of registry entry TELECOM_CAPABILITY Test ID SVC_3312 Test objectives To verify that the SPBL has implemented at least the registry entries provided in Table 7.1 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_PARAMETER (CODE_M) command for getting the initial SSP credentials parameter computed from the Service Provider parameter. 4 The SPBL service gate returns ANY_OK if the command is successfully executed. 5 The SPBL application gate sends the OFL_DO_OPERATE command with the registry entries defined in Table 7.1 of ETSI TS 103 666-2 [10] to the SPBL host. 6 The SPBL service gate returns ANY_OK if the command is successfully executed. RQ0703_003 Test ID SVC_3313 Test objectives To verify that the SPBL has implemented the additional registry entries provided in Table 7.2 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_PARAMETER (CODE_M ?) command for getting the initial SSP credentials parameter computed from the Service Provider parameter. 4 The SPBL service gate returns ANY_OK if the command is successfully executed. 5 The SPBL application gate sends the OFL_DO_OPERATE command with mandatory registry entries defined in Table 7.1 and additional registry entries defined in Table 7.2 of ETSI TS 103 666-2 [10] to the SPBL host. 6 The SPBL service gate returns ANY_OK if the command is successfully executed. RQ0703_004 Test ID SVC_3314 Test objectives To verify that the registry entry TELECOM_CAPABILITY on an iSSP hosting a Telecom Secondary Platform Bundle contains the maximum number of distinct concurrent 3GPP network registrations. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. The pre-configured SPB container indicates a maximum number of concurrent 3GPP network registrations other that the default. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 81 Release 15 7.3.3.1.5 SVC_3315 – Additional responses supported by the OFL Service Gate #1 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.6 SVC_3316 - Additional responses supported by the OFL Service Gate #2 | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.7 SVC_3317 - Additional responses supported by the OFL Service Gate #3 | 3 The SPBL application gate sends the GET_PARAMETER (CODE_M) command for getting the initial SSP credentials parameter computed from the Service Provider parameter. 4 The SPBL service gate returns ANY_OK if the command is successfully executed. 5 The SPBL application gate sends the OFL_DO_OPERATE command containing the conditional parameter TELECOM_CAPABILITY to the SPBL host. 6 The SPBL service gate returns ANY_OK if the command is successfully executed. RQ0703_005 Test ID SVC_3315 Test objectives To verify that the SPBL supports the additional response: eSPBL_E_NO_CI_FOR_SPBM_VERIFICATION as defined in Table 7.4 to the additional command entry: GET_SSP_INFO_PARAMETER defined in Table 7.3 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. The pre-configured SPB container indicates that the provided CIs are not supported for SPBM verification. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_SSP_INFO_PARAMETER command. 4 The SPBL service gate sends the response value '10' (eSPBL_E_NO_CI_FOR_SPBM_VERIFICATION). RQ0703_009 Test ID SVC_3316 Test objectives To verify that the SPBL supports the additional response: eSPBL_E_NO_CI_FOR_SPBL_VERIFICATION as defined in Table 7.4 to the additional command entry: GET_SSP_INFO_PARAMETER defined in Table 7.3 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. The pre-configured SPB container indicates that it does not support CIs to sign the SPBL. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_SSP_INFO_PARAMETER command. 4 The SPBL service gate sends the response value '11' (eSPBL_E_NO_CI_FOR_SPBL_VERIFICATION). RQ0703_010 Test ID SVC_3317 Test objectives To verify that the SPBL supports the additional response: eSPBL_E_NO_CI_FOR_KEYAGREEMENT as defined in Table 7.4 to the additional command entry: GET_SSP_INFO_PARAMETER defined in Table 7.3 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. The pre-configured SPB container indicates that it does not support any CIs for key agreement. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 82 Release 15 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.8 SVC_3318 - Additional responses supported by the OFL Service Gate #4 | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.9 SVC_3319 - Additional responses supported by the OFL Service Gate #5 | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.3.1.10 SVC_33110 - Additional responses supported by the OFL Service Gate #6 | Test ID SVC_33110 Test objectives To verify that the SPBL supports the additional response: eSPBL_E_EXCEED_TELECOM_CAPABILITY as defined in Table 7.4 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. The pre-configured SPB container holds a number of Telecom Secondary Platform Bundles higher than the limit indicated in the TELECOM_CAPABILITY. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_SSP_INFO_PARAMETER command. 4 The SPBL service gate sends the response value '12' (eSPBL_E_NO_CI_FOR_KEYAGREEMENT). RQ0703_011 Test ID SVC_3318 Test objectives To verify that the SPBL supports the additional response: eSPBL_E_NO_SUPPORTED_CRYPTO as defined in Table 7.4 to the additional command entry: GET_SSP_INFO_PARAMETER defined in Table 7.3 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. The pre-configured SPB container indicates that it does not support any cryptographic algorithms. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_SSP_INFO_PARAMETER command. 4 The SPBL service gate sends the response value '13' (eSPBL_E_NO_SUPPORTED_CRYPTO). RQ0703_012 Test ID SVC_3319 Test objectives To verify that the SPBL supports the additional response: eSPBL_E_INVALID_SPBM_CERT as defined in Table 7.4 of ETSI TS 103 666-2 [10]. Configuration reference CSVC_311, CSVC_312 Initial conditions Pipe sessions are opened and established as defined in PSVC_321 and PSVC_322. The pre-configured SPB container indicates that the received SPBM certificate (chain) is not valid. Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the GET_SPB_METADATA command. 4 The SPBL service gate sends the response value '14' (eSPBL_E_INVALID_SPBM_CERT). RQ0703_013 ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 83 Release 15 Test sequence Step Description Requirements 1 The SPBL application gate sends the SET_PARAMETER command for storing the SPBM credentials parameters from the Service Provider in the SPBL service gate. 2 The SPBL service gate returns ANY_OK if the command is successfully executed. 3 The SPBL application gate sends the SWITCH_TELECOM_SPB command. 4 The SPBL service gate sends the response value '15' eSPBL_E_EXCEED_TELECOM_CAPABILITY. RQ0703_014 |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.4 Requirements not testable, implicitly verified or verified elsewhere | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.4.1 OFL service | The following requirements, identified in ETSI TS 103 666-2 [10] are not tested in accordance with the present document, as they are referencing requirements from another standardization body (GlobalPlatform): RQ0703_006, RQ0703_008. The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document: RQ0703_002. The following requirement, identified in ETSI TS 103 666-2 [10] are tested in the context of clause 9.4 of the present document: RQ0703_017. The following requirement, identified in ETSI TS 103 666-2 [10] are tested in the context of clause 12 of the present document: RQ0703_007, RQ0703_015, RQ0703_016, RQ0703_018. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.4.2 Communication service | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing requirements from another standardization body (GlobalPlatform): RQ0703_020. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.3.4.3 Management service | The following requirement, identified in ETSI TS 103 666-2 [10] is not tested in accordance with the present document, as it is referencing requirements from another standardization body (GlobalPlatform): RQ0703_021, RQ0703_022, RQ0703_023. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.4 Cryptographic functions | |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.4.1 Configurations | There are no specific configurations defined for cryptographic functions testing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.4.2 Procedures | There are no specific procedures defined for cryptographic functions testing. |
c5b8b907189990fab42768042356ae8b | 103 999-2 | 7.4.3 Test descriptions | There are no specific test descriptions defined for testing the provisioning of cryptographic functions. ETSI ETSI TS 103 999-2 V15.0.0 (2021-12) 84 Release 15 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.