hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5.5 AAS-OP-AUTHENTICATE-ACCESSOR-Service-Command | With the command AAS-OP-AUTHENTICATE-ACCESSOR-Service-Command, the accessor authentication application provides the credentials for performing the authentication. -- ASN1START AccessorTokenCredential ::= SEQUENCE { aAuthenticationToken AuthenticationToken, -- The authentication token generated by the AAA aTokenCertific... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5.6 AAS-OP-ACCESS-SERVICE-Service-Command | With the command AAS-OP-ACCESS-SERVICE-Service-Command, an accessor provides the parameter for initiating a pipe session between a service and application gate identified by aServiceIdentifier identifier. This allows access to resources that are protected by an access control list (e.g. SSP files in the SSP file system... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5.7 AAS-OP-GET-CHALLENGE-Service-Command | With the command AAS-OP-GET-CHALLENGE-Service-Command, an accessor provides the parameter for authenticating an accessor using token mechanism. -- ASN1START AAS-OP-GET-CHALLENGE-Service-Command ::= [PRIVATE 21] SEQUENCE { } -- ASN1STOP This command has no parameters. When the accessor authentication request is successf... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.6 Response code | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.6.1 Overview | The accessor authentication service provides the following response codes to accessor authentication service primitives. -- ASN1START AAS-Service-Response ::= ENUMERATED { eAAS-OK (0), -- Operation successful eAAS-E-CMD-PAR-UNKNOWN (2), -- Unknown parameters used for an operation eAAS-E-NOK (3), -- Operation failed eAA... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.6.2 Response codes to accessor authentication service commands | Table 6.6 shows the possible response codes returned for each accessor authentication service command. Table 6.6: Accessor authentication service commands/responses Command eAAS-OK eAAS-E-CMD-PAR-UNKNOWN eAAS-E-NOK eAAS-ACL-RULES-VIOLATIONS eAAS-NOT-AUTHENTICATED eAAS-POLICY-RULES-VIOLATIONS aAAS-OP-GET-CAPABILITIES-Se... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7 Physical interfaces | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.1 Overview | The SSP may have multiple physical interfaces of the same type or of different types. These interfaces may connect to the same or to different end-points in the terminal (e.g. baseband, NFC controller). When the SSP contains two or more interfaces, each of them is completely independent, both electrically and logically... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.2 Reset | There are three types of reset of the physical interface: • Reset with dedicated line: this reset requires the presence of a dedicated line in the physical interface that indicates the reset (e.g. the RST line on the ISO/IEC 7816-3 [3] physical interface). • Logical reset: this reset is performed sending a command over... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3 ISO/IEC 7816 interface | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.1 Electrical specifications | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.1.1 Electrical specifications of the interface | The provisions of ETSI TS 102 221 [1], clause 5 shall apply with the following exceptions: • The SSP may support a clock up to 20 MHz for the ISO/IEC 7816-3 [3] physical interface. • The SSP shall use an internal clock for the processing, when this is mandated by the SSP class. The SSP may use an internal clock in all ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.1.2 Contacts | The provisions of ETSI TS 102 221 [1], clause 4.5 shall apply with the following exception: • References to the usage of contacts C4 and C8 for the Inter-Chip USB interface. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2 Initial communication establishment procedures | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.1 SSP interface activation and deactivation | The provisions of ETSI TS 102 221 [1], clause 6.1 shall apply with the same exceptions described in clause 7.3.1.2 of the present document. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.2 Supply voltage switching | The provisions of ETSI TS 102 221 [1], clauses 6.2.0, 6.2.1 and 6.2.2 shall apply. The maximum power consumption of the SSP after ATR shall be restricted to the minimum power supply values indicated in ETSI TS 102 221 [1], table 6.4, until a different value is negotiated using the SSP capability exchange procedure, des... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.3 Answer To Reset content | The ATR shall be the first string of bytes sent from the SSP to the terminal after a reset has been performed. The ATR is defined in ISO/IEC 7816-3 [3]. The historical bytes indicate to the external world how to use the SSP. The information carried by the historical bytes shall follow ISO/IEC 7816-4 [4]. Additionally, ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.4 PPS procedure | The provisions of ETSI TS 102 221 [1], clause 6.4 shall apply. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 68 Release 17 |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.5 Reset procedure | The provisions of ETSI TS 102 221 [1], clause 6.5 shall apply. The warm reset is a reset with dedicated line, as described in clause 7.2. The cold reset is a hard reset, as described in clause 7.2. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.6 Clock stop mode | The provisions of ETSI TS 102 221 [1], clause 6.6 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.7 Bit/character duration and sampling time | The provisions of ETSI TS 102 221 [1], clause 6.7 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.2.8 Error handling | The provisions of ETSI TS 102 221 [1], clause 6.8 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.3 Data link protocols | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.3.1 Overview | The provisions of ETSI TS 102 221 [1], clause 7.0 shall apply, with the exceptions listed below. Only the protocol T=1 is mandatory for the terminal. The SSP shall support the protocol T=1. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.3.2 Character frame | The provisions of ETSI TS 102 221 [1], clause 7.2.1 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.3.3.3 Protocol T=1 | The provisions of ETSI TS 102 221 [1], clause 7.2.3 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.4 SPI interface | The provisions of ETSI TS 103 713 [32] shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.5 I2C interface | The usage of the I2C interface for SSP is for future study. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.6 SWP interface | The provisions of ETSI TS 102 613 [5] shall apply with the following exceptions: • Contacts names C1 (Vcc), C5 (Gnd), C6 (SWIO), C2 (RSET), C3 (CLK), C7 (IO), C4 (IC_DP), C8 (IC_DM) are irrelevant. • The provisions of ETSI TS 102 613 [5], clauses 5.2, 5.3, 5.4, 6.1, 6.2.1 and 7.1.1 are optional, as the SSP needs not to... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.7 USB interface | The usage of the USB interface for SSP is for future study. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 7.8 Proprietary interface | In addition to standardized physical interfaces, some SSP classes may have a proprietary interface. The SSP shall be able to trigger communication over this proprietary physical interface. Further definition of this physical interface is outside the scope of the present document. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8 SSP Common Layer (SCL) | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.1 Introduction | The SSP may support the SSP Common Layer (SCL) implementation comprised of optional network, transport and session layers. The SCL is the common protocol layer in the protocol stack of the SSP. The SCL is independent of any of its optional underlying and upper communication layers. The SCL is supported by several under... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.2 SCL network | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 3 shall apply, with the exception listed below: • One of the end points of any dynamic pipe shall be in the SSP host domain or in the network controller host. NOTE: The usage of pipes between two hosts outside the SSP host domain is for further study.... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.3 Protocol layers | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.3.1 Overview | The provisions of GlobalPlatform VPP - Network Protocol [13], clauses 4.1 and 4.2 shall apply, with the exception listed below: • the VNP MTU value of the link service gate registry shall be 20 bytes or greater (as defined in clause 8.4.3.1.2). For proper operation, the protocol stack underlying the SCL shall provide a... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.3.2 Network layer | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 4.3 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.3.3 Transport layer | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 4.4 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.3.4 Session layer | The session layer is mapped on the pipe session as defined in GlobalPlatform VPP - Network Protocol [13], clause 3.10.2. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4 SCL core services | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.1 Overview | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.1 shall apply. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 71 Release 17 |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.2 Common core features | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.2 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.3 Link gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.3.1 Link service gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.3.1.1 General description | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.3 shall apply, with the following additions. NOTE: The credit-based data flow control mechanism and the data acknowledgement mechanism are not used in the link service gate. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.3.1.2 Additional registry entries | The following entry defined in GlobalPlatform VPP - Network Protocol [13], clause 5.3.5 of the link service gate registry is modified according to the table 8.2. Table 8.2: Additional registry entries in the link service gate Type Identifier Parameter Access Right Comment Length Default Mandatory '05' VNP_MTU RO MTU va... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.3.1.3 SSP_MTU | It contains the value in bytes of the MTU of the link layer between the SCL router and the SSP. The entry shall have a value equal to or greater than 20. An SCL host shall be able to send an SCL packet to the SSP without fragmentation, if the size of the SCL packet is less or equal to the value provided in this registr... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.3.2 Link application gate | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.4 shall apply. NOTE: The credit-based data flow control mechanism and the data acknowledgement mechanism are not used in the link application gate. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.4 Administration gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.4.1 Administration service gate | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.5 shall apply, with the exception listed in clause 8.5.3. NOTE: The credit-based data flow control mechanism and the data acknowledgement mechanism are not used in the administration service gate for its own usage (e.g. the reception of an event EVT... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.4.2 Administration application gate | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.6 shall apply. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 72 Release 17 NOTE: The credit-based data flow control mechanism and the data acknowledgement mechanism are not used in the administration service gate for its own usage (e.g. the reception of ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.5 Identity gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.5.1 Identity service gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.5.1.1 General description | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.7 shall apply, with the following additions. The identity service gate should not list gates that are created dynamically as a result of an operation on a service of the SSP (e.g. the file system data service gates described in clause 10.3.5, the TC... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.5.1.2 Additional registry entries | The following additional entries defined in GlobalPlatform VPP - Network Protocol [13], clause 5.7.5 of the identity service gate are modified according to the table 8.3. Table 8.3: Additional registry entries in the identity service gate Type Identifier Parameter Access Right Comment Length Default Optional '06' NB_PI... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.5.1.3 CAPABILITY_EXCHANGE | The capabilities of the host are coded with ASN.1 syntax as defined in: • clause 6.4.2.4, for SCL hosts outside the SSP host domain; • clause 6.4.2.5, for SCL hosts inside the SSP host domain. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.5.1.4 GATE_URN_LIST | The GATE_URN_LIST provides an ASN.1 object containing an array of URNs according to IETF RFC 8141 [29] used to compute gate identifiers and the UUID resulting from the computation. The Identity Application Gate may use this entry for service discovery. The GATE_URN_LIST may have less, but shall not have more URNs than ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.5.2 Identity application gate | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.8 shall apply. In addition, the additional entries in the gate registry defined in clause 8.4.5.1.2 shall apply. The credit-based data flow control mechanism and the data acknowledgement mechanism shall not be used in the identity application gate. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.6 Loopback gate | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.6.1 Loopback service gate | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.9 shall apply with the following exception: • The credit-based data flow control mechanism and the data acknowledgement mechanism are optional for the loopback service gate in the SSP host and their support is indicated in the LOOPBACK_CAPABILITIES ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.6.2 Loopback application gate | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 5.10 shall apply with the following exception: • The credit-based data flow control mechanism and the data acknowledgement mechanism shall be enabled in the loopback application gate outside the SSP host according to the support indicated by the loopb... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.4.6.3 Registry | The following registry entry is defined for the loopback service gate in the SSP host. Table 8.4: Registry entry in the loopback gate Type Identifier Parameter Access Right Comment Length Default Optional '80' LOOPBACK_CAPABILITIES R Capabilities of the loopback service gate 1 '00' The capabilities of the loopback serv... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.5 SCL procedures | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.5.1 Host registration | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 6.1.2 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.5.2 Host deregistration | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 6.1.4 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.5.3 Pipe management | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 6.2 shall apply, with the following additions in the binding procedure described in GlobalPlatform VPP - Network Protocol [13], clause 6.2.1: • a host shall not request a pipe binding for a service gate if this service gate has already a pipe session ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.5.4 Registry access | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 6.3 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.5.5 Hosts and gates discovery | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 6.4 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 8.5.6 Loopback testing | The provisions of GlobalPlatform VPP - Network Protocol [13], clause 6.5 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9 Secure SCL | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.1 Protocol stack | Figure 9.1 illustrates the protocol supporting a secure communication layer between a generic service X and application X. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 75 Release 17 Figure 9.1: Protocol stack for secure SCL |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.2 Structure of secure SCL message | The messages, data streams, commands and responses between a service gate and an application gate may be authenticated and their data encrypted in secure SCL messages conveyed in SCL packets. The value of the DIVERSIFIER defined in clause C.4.2 shall be the logical XOR of the aChallenge value as defined in clause 6.13.... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.3 Security protocol | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.3.1 Overview | The security protocol between an accessor authentication service and application has the following steps: • The initialization of the shared secret by using the security protocol described in clause 9.3.2. • The generation of shared keys between a service and an application using the secure SCL described in clause 9.3.... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.3.2 Shared secret initialization | The shared secret initialization is using the security protocol defined in figure 9.3. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 77 Release 17 Figure 9.3: Secure SCL security protocol shared secret initialization The procedure supporting the security protocol is the following: 1) The Accessor Authentication Service (AAS... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.3.3 Secure SCL shared keys generation | From the shared secret ShS obtained from the procedure described in clause 9.3.2, any service or application may initiate the generation of the key data by using the KDF function defined in clause C.4 and a DIVERSIFIER128BIT that is equal to aGateIdentifier defined in clause 6.13.5.6. This generation of key data is per... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.4 Accessor authentication service procedure | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 9.4.1 Initialization | Figure 9.4 illustrates the exchanges between the accessor authentication service and accessor authentication application gates for supporting the security protocol defined in clause 9.3 and details the parameters of the procedure. Figure 9.4: Accessor authentication service initialization The procedure supporting the a... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10 Communication layers above SCL | 10.1 Overview The SSP may support multiple application protocols. An SCL gate shall not send a command when this gate is waiting for a response to a previous command. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2 APDU protocol | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.1 Introduction | This clause describes the interaction between the SSP and the terminal using APDUs. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.2 Command-response pairs | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.2.1 General definition | The provisions of ISO/IEC 7816-4 [4], clause 5.1 shall apply, with the exceptions listed in the clauses below. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.2.2 CLA byte | The provisions of ETSI TS 102 221 [1], clause 10.1.1 shall apply. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.2.3 INS byte | The INS byte indicates the command to process and its meaning depends on the application selected on the logical channel indicated in the CLA byte of the command APDU. The following instructions are applicable on the basic logical channel. Table 10.1: Coding of Instruction Byte Command APDUs INS Clause Support (M/O/C) ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.2.4 Coding of SW1 and SW2 | The status bytes SW1 SW2 indicate the status of the UICC at the end of a command. The meaning depends on the application selected on the logical channel indicated in the CLA byte of the command APDU. If no application is selected and the SSP has support for the UICC file system, the provisions of ETSI TS 102 221 [1], c... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3 SSP commands | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3.1 Overview | The following clauses describe the list of commands that may be supported by the SSP. NOTE: This list is not exhaustive. Additional commands may be supported depending on the selected application (e.g. GET CHALLENGE, AUTHENTICATE and GET IDENTITY as defined in ETSI TS 102 221 [1]). |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3.2 EXCHANGE CAPABILITIES | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3.2.1 Description | This command is used to inform the SSP of the capabilities of the terminal and to retrieve the capabilities of the SSP. This command shall be executed immediately after the SSP Interface Session is started. The command might be executed again if some of the capabilities change. The SSP and the terminal shall use the va... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3.2.2 Command parameters | Table 10.2 Code Value CLA As specified in clause 10.2.2.2 INS As specified in table 10.1 P1 '00' P2 '00' Lc Length of subsequent data field or empty Data Capabilities of the terminal Le '00' |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3.2.3 Command data | The command data contains a sequence of TLVs, coded as per clause 6.4.2.4. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3.2.4 Command response | The command data contains a sequence of TLVs, coded as per clause 6.4.2.5. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.3.3 SELECT | The provisions of ISO/IEC 7816-4 [4] and of ETSI TS 102 221 [1] for the SELECT command with P1 = '04' ("Select by DF name") shall apply. The coding of P2 is described in table 10.3. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 81 Release 17 Table 10.3: Coding of P2 b8 b7 b6 b5 b4 b3 b2 b1 Meaning 0 - - 0 - - - - Other valu... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.4 Logical channels | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.4.1 Overview | Logical channels are defined in ISO/IEC 7816-4 [4]. The SSP can support up to 20 logical channels, which are 19 logical channels in addition to the basic logical channel 0. The SSP indicates the maximum number of supported logical channels during the capability exchange with the terminal. Channel 0 is always available ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.4.2 MANAGE CHANNEL | The provisions of ETSI TS 102 221 [1], clause 11.1.17 shall apply. Support for this command is mandatory if the SSP indicates support for logical channels during the capability exchange procedure. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.5 UICC file system commands | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.5.1 Overview | This clause describes the behaviour of the SSP and the terminal when the SSP indicates support for the UICC file system. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.2.5.2 Methods for selecting a file | The provisions of ETSI TS 102 221 [1], clause 8.4 shall apply. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.