Export Form Data

Verify Form Data

Import Form Data

GlobalPlatform
Supported Configuration Options(SCO)
for Secure Element Products
Version 5.5
SCO Reference Number and Validity Period(for GP administrative use only)

SCO Reference Number:
Valid from:
Valid to:
Notice:This SCO form shall be completed for Products submitted for GlobalPlatform
Qualification Functional evaluations. The form shall be completed in its entirety. All Yes
and No questions shall be answered. If a feature/option is NOT supported, i.e. a questionis answered “No,” the sub-questions for that feature/question shall be left blank.

A - Administrative
Product Provider Identification
A.1.1 – Company Legal Name

GlobalPlatform submitted Configuration Description
A.2.1 UICC Configurations
A.2.1.1 – UICC Configuration v1.0.1
A.2.1.2 – UICC Configuration v2.0
A.2.2 UICC Extensions
A.2.2.1 – The UICC Configuration is submitted with the SCP81 extension,
Amendment B, v1.1.1
Note:This Option can only be selected for UICC v1.0.1 productA.2.2.2 –VOID
A.2.2.3 – The UICC Configuration is submitted with the Contactless Extension,
v1.0
Note: This Option can only be selected for UICC v1.0.1 productA.2.2.4 – The UICC Configuration is submitted with the Contactless Extension,v2.0
Note:This Option can only be selected for UICC v2.0 product

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:GlobalPlatform submitted Configuration Description
A.2.2.5 – The UICC Configuration is submitted with the Memory Management
Extension (Subset of Contactless Extension v1.0)
Note:This Option can only be selected for UICC v1.0.1 productA.2.2.6 – The UICC Configuration is submitted with the Memory ManagementExtension, (Subset of Contactless Extension v2.0)
Note:This Option can only be selected for UICC v2.0 productA.2.2.7 – The UICC Configuration is submitted with the ‘SCP11 (a and b) –Amendment F v1.2 ’ package of the SE Configuration, v2.0
Note:This Option can only be selected for UICC v2.0 productA.2.2.8 – The UICC Configuration is submitted with the ‘ELF Upgrade –Amendment H v1.1 ’ package of the SE Configuration, v2.0
Note:This Option can only be selected for UICC v2.0 productA.2.3 Financial Configurations
A.2.3.1 – The GP product submitted follows Basic Financial Configuration, v1.5
A.2.3.2 – The GP product submitted follows Financial Configuration v1.0.2
A.2.4 Financial Configurations Extensions
A.2.4.1 – The Financial Configuration is submitted with the ‘SCP11 (a and b) –Amendment F v1.2’ package of the SE Configuration, v2.0
Note This Option can only be selected for Financial Configuration v1.0.2 productA.2.4.2 – The Financial Configuration is submitted with the ‘ELF Upgrade –Amendment H v1.1 ’ package of the SE Configuration, v2.0
Note This Option can only be selected for Financial Configuration v1.0.2 productA.2.4.3 – The Financial Configuration is submitted with the ContactlessExtension, v2
Note: This Option can only be selected for Financial Configuration v1.0.2 productA.2.4.4 – The Financial Configuration is submitted with the Memory Management
Extension (Subset of Contactless Extension v2.0)
Note: This Option can only be selected for Financial Configuration v1.0.2 productA.2.5 Common Implementation Configurations (CIC)
A.2.5.1 – The GP product submitted follows CIC v2.1
A.2.6 CIC Extensions
A.2.6.1 – The CIC is submitted with the Contactless Extension, v2.0
A.2.6.2 – The CIC is submitted with Memory Management Extension, (Subset ofContactless Extension v2.0)

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:GlobalPlatform submitted Configuration Description
A.2.7 Secure Element Configuration
A.2.7.1 –VOID
A.2.7.2 –The GP product submitted follows Secure Element Configuration v2.0
A.2.8 Secure Element Configuration Extensions
A.2.8.1 – VOID
A.2.8.2 – VOID
A.2.8.3 – The SE Configuration is submitted with Contactless Extension, v2.0
A.2.8.4 – The SE Configuration is submitted with Memory ManagementExtension, (Subset of Contactless Extension v2.0)
A.2.9 – The GP product submitted follows Secure Element Access Control, v1.0
Note This option has to be selected together with a card platform configuration listedabove, it cannot be selected alone.

A.2.10 – The GP product submitted follows Mapping Guidelines, v1.0.1
A.2.11 – The GP product submitted follows ID Configuration, v1.0
A.2.12 – The GP product submitted follows Compact IoT Configuration, v1.0

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:GlobalPlatform submitted Configuration Description
eUICC M2M and eUICC Consumer(Products qualified by GlobalPlatform based on GSMA & SIMalliance/TCA Test Specifications)eUICC M2M
A.2.20 – The product submitted follows eUICC M2M SGP.02 v3.2
A.2.21 – The product submitted follows eUICC M2M SGP.02 v4.2
eUICC Consumer
A.2.31 – The product submitted follows eUICC Consumer SGP.22 v2.2.x or v2.3 orv2.4 or v2.5

GlobalPlatform SPI/I2C Test Suite
A.2.100 – SPI and I2C v1.0 Test suite
A.2.101 The GP product submitted is to be tested over I2C with the SPI/I2C
Test suite
A.2.102 The GP product submitted is to be tested over SPI with the SPI/I2C
Test suite
Note: The two options above have to be selected together in case both SPI and I2C aresupported by the GP product. In such case, two SCO Configuration XML files need to beprovided by the SE manufacturer.

GlobalPlatform SWP/HCI Test Suite
A.2.110 – SWP and HCI Test suite version 2.0.X
A.2.111 The GP product submitted is to be tested using SWP Test suite v2.0.X
A.2.112 The GP product submitted is to be tested using HCI Test suite v2.0.X

Copyright  2011 - 2023 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:

SCO Version Number
A.3.1 –This SCO is for:(only one answer possible)

A new submission
A replacement of a previously accepted SCO (*)
A derivative Product submission
A change Product submission
A renewal submission(*) For a product under qualification and only if the Test Report related

to the initial SCO has not been submitted yet.

A.3.2 – If the answer to question A.3.1 is a SCO replacement:
A.3.2.1 – provide the reference number ofthe previously accepted SCO
A.3.2.2 – provide the reason for updatingthe SCO
A.3.3 – If the answer to question A.3.1 is a Derivative Product:
A.3.3.1 – provide the SCO reference
number of the Intial ProductA.3.3.2 – provide the LOQ reference
number of the Intial ProductA.3.3.3 – please explain which derivation
A.3.3.4 – Type of derivation of thesubmitted product (As defined in section
4.8.1 of the GP qualification process)<Select>

A.3.3.5 – If a Conformance Assessment
Report has been performed on the initial
Product, please provide the CAR reference
A.3.4 – If the answer to question A.3.1 is a Change Product:
A.3.4.1 – provide the SCO reference
number of the Product to change
A.3.4.2 – provide the LOQ reference
number of the Product to change
A.3.4.3 – please explain which change
A.3.4.4 – If a Conformance Assessment
Report has been performed on the Productto change, please provide the CARreference
A.3.5 – If the answer to question A.3.1 is a Renewal Submission:
A.3.5.1 – provide the SCO reference
number of the Initial ProductA.3.5.2 – provide the LOQ reference
number of the the Initial ProductA.3.5.3 – you require a Derivative productrenewal without any tests (See if you canCopyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:

apply for such derogation in the GP
qualification process).
A.3.5.4 – If you require a Derivative
product renewal without any tests, please
explain why
A.3.5.5 – If Conformance Assessment
Reports have been performed on the
Product to renew, please provide all
relevant CAR reference(s) (up to 3)

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:

Product Specification References
Name

VersionNumber

A.4.1 – Java Card
Specification
supported

A.4.2 – GP
Amendments
supported(list all applicable)

A.4.3 – GP Errata
List supported(list all applicable)

A.4.4 – GP API &Export file used
(list all applicable)

A.4.5 – Java Card
API & Export fileused(list all applicable)

A.4.6 – Other
Specification used
(e.g. GSMA, …)(list all applicable)

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:

Released byProduct and Chip Descriptions
A.5.1 – Product Reference and Version No:(Same reference as in QLA or Exhibit A)(This is the name that will appear on the Qualified
Products List)
A.5.2 –Manufacturer name of the Productsubmitted for testing:
A.5.3 – Provider Operating System Type:
A.5.4 – Provider Operating System Name andVersion Number:

Name:
Version Number:

Chip Feature Description
A.5.5 – RAM size (Kbytes)
A.5.6 – ROM size (Kbytes)
A.5.7 – Total EEPROM or Flash size(Kbytes)
A.5.8 – Available EEPROM or Flash size(Kbytes)
A.5.9 – CPU (8, 16 or 32 bit etc.)
A.5.10 – Form factor

Card format based on ISO 7810
SoC
USB Token
Other form factor//Description:

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:

Product and Chip Descriptions
A.5.11 – Communication Protocol(s) used by the
Test Tool to qualify the Product for the GP
configuration selected in A.2.1(if Multi-Protocol, list all protocols to be used)

Contact interfaces
T=0
T=1
Contactless interfaces
Contactless Protocol Type A (1)Contactless Protocol Type B (1)SWP Protocol (2) (GP HCI gate)
TCP/IP interface
GP SE Abstract Communication Layer (3)Other interfaces
SPI Protocol (4)I2C Protocol (4)NOTE: in case multiple Test Suites and multiple
Protocols are chosen, please indicate whichprotocol(s) shall be used for each Test Suite/Description:(1) This option is only supported for Mapping
Guidelines, Basic Financial, Financial and Common
Implementation configurations(2) This option is only supported for Secure Element
Configurations.
(3) This option, based on TCP/IP, is agnostic from thetransport protocol(s) supported by the Product.

(4) This option is only supported for SPI/I2C Test Suite.

A.5.12 – Platform Hardware (CHIP) Provider
Name

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:GlobalPlatform Detailed Configuration Description
GP.1.1 – Provide detailed SCO options supported by each configuration submitted(cut and past each configuration XML file)

Configuration XML file 1
Configuration XML file 2
Configuration XML file 3
Configuration XML file 4
Configuration XML file 5
Configuration XML file 6
Configuration XML file 7Configuration XML file 8
Configuration XML file 9
Configuration XML file 10
Configuration XML file 11
Configuration XML file 12
Configuration XML file 13
Configuration XML file 14
Configuration XML file 15
Configuration XML file 16
Configuration XML file 17
Configuration XML file 18
Configuration XML file 19
Configuration XML file 20

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number:

Laboratory Identification (Section to be completed by the Lab)
Company Name:
GP Registration Number:
SCO Reviewer’s Name:
Title:
Telephone Number:
Fax Number:
Email Address:
Signature:

Date:

Comments

I agree and understand that if an issue requires a change to the code of the GP Productsubmitted or the addition of a patch or new executable code to the GP Product, GP must benotified. In case of such change, new GP Product must be submitted for testing.
I hereby declare that the above referenced product currently is and will remain in compliancewith the above referenced GP specifications for all mandatory and supported optional
requirements.
Product Provider’s Officer
Name:
Telephone Number:
Fax Number:
Email Address:
Address:
Title:
Signature:

Date:

GP Compliance Secretariat
Signature:

Copyright  2011 - 2024 GlobalPlatform Inc. All Rights Reserved.

SCO Reference Number: