hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.12 NG-u interface | The NG-u interface, as defined by 3GPP, is between the gNB-CU-UP and the UPF in the 5GC as specified in ETSI TS 138 300 [8]. It is also referred as N3 in ETSI TS 138 300 [8]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted between the O-CU-UP and the 5GC. |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.13 X2-c interface | The X2-c interface is defined in 3GPP for transmitting control plane information between eNBs or between eNB and en-gNB in EN-DC as specified in ETSI TS 136 420 [6] and ETSI TS 138 300 [8]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profil... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.14 X2-u interface | The X2-u interface is defined in 3GPP for transmitting user plane information between eNBs or between eNB and en- gNB in EN-DC as specified in ETSI TS 136 420 [6] and ETSI TS 138 300 [8]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profile ... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.15 Xn-c interface | The Xn-c interface is defined in 3GPP for transmitting control plane information between gNBs, ng-eNBs or between ng-eNB and gNB as specified in ETSI TS 138 300 [8] and ETSI TS 138 420 [12]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profi... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.16 Xn-u interface | The Xn-u interface is defined in 3GPP for transmitting user plane information between gNBs, ng-eNBs or between ng-eNB and gNB as specified in ETSI TS 138 300 [8] and ETSI TS 138 420 [12]. In O-RAN, it reuses the principles and protocol stack defined by 3GPP but is adopted for the definition of interoperability profile ... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.17 Uu interface | The UE to eNB/gNB interface in 3GPP is denoted as the Uu interface. The Uu is a complete protocol stack from L1 to L3 and as such, seen as a whole, it terminates in the NG-RAN. If the NG-RAN is decomposed, different protocols terminate at different reference points and none of them has been defined by O-RAN. Since the ... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.18 CTI (Cooperative Transport Interface) | Interface between the O-DU and TN to dynamically control bandwidth allocations to TUs when using a shared point-to- multipoint transport network. The CTI is specified in CTI Control [20] and CTI Management [21]. |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.19 Y1 interface | Y1 service interface as specified in Y1GAP [39] allows the Y1 consumers to subscribe or request the RAN analytics information provided by Near-RT RIC. |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.20 R1 interface | The R1 interface is a service-based interface between the rApps and the Non-RT RIC framework via which R1 services can be produced and consumed as specified in Non-RT RIC Architecture [27]. The producers of R1 services can be part of the Non-RT RIC and/or the SMO Framework. R1 services are specified in R1GAP [35]. |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.21 Near-RT RIC APIs | The Near-RT RIC APIs are a set of service-based interfaces that can be produced and consumed by the Near-RT RIC Platform and xApps as specified in Near-RT RIC Architecture [26]. |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.4.22 D2 interface | The D2 interface is between two O-DU nodes connected to the same O-CU-CP. O-CU-UP for both the O-DUs can be same or different. One O-DU can be connected to multiple O-DUs. D2 interface is used for supporting inter O-DU NR carrier aggregation across O-DUs. An O-DU can be a PCell O-DU for a particular UE and a SCell O-DU... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.5 UE associated identifiers used in O-RAN | As described earlier (clauses 5.3.1 and 5.3.2), the Non-RT RIC and Near-RT RIC enable intelligent RAN optimization via A1, O1 and E2 interfaces respectively. To support intelligent RAN optimization, the Non-RT RIC with rApps and Near-RT RIC with xApps utilize the knowledge of different UE associated events reported by ... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 5.6 O-RAN security architecture | The goals of the O-RAN ALLIANCE are to achieve a secure, open, and interoperable RAN. Building upon security advancements from the 3GPP and IETF standards development organizations, the O-RAN ALLIANCE specifies an O-RAN security architecture with the goal to enable 5G CSPs (Communication Service Provider) to deploy and... |
4899d1727043708ef519c9d2ec1465a3 | 103 982 | 6 O-RAN Information Model (IM) principles | O-RAN shall align its Information Model (IM) with 3GPP to the extent possible. The additional O-RAN extensions to its IM and DMs (Data Model) are described in O-RAN Information Model and Data Models Specification [30]. ETSI ETSI TS 103 982 V14.0.0 (2026-03) 28 Annex A (informative): Implementation options of O-RAN func... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 1 Scope | The present document specifies the test descriptions, test environment and conformance requirements for services running in the Smart Secure Platform and in any terminal hosting a Smart Secure Platform application. The present document specifies the test descriptions for: • SSP characteristics • Physical interfaces • S... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 2 References | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. • In the case of a reference... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. • In the case of a reference... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3 Definition of terms, symbols and abbreviations | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 465 [i.8] and ETSI TS 103 666-1 [1] apply. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 103 465 [i.8] and ETSI TS 103 666-1 [1] apply. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AA Accessor Authentication AAA Accessor Authentication Application AAS Accessor Authentication Service AAUTH Accessor AUTHentication ACL Access Control List AID Application IDentifier APDU Application Protocol Data Unit ASN.1 Abstract Syntax N... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4 Formats | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4.1 Format of the table of optional features: Table 4.1 | The columns in the optional features table, Table 4.1, have the following meaning: Column Meaning Item Item number, incrementing with each item added to the table Service Description of the service that might be supported by the implementation Status The status of the service is described following notations defined in... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4.2 Format of the table of optional features: Table 4.2 | The columns in the optional features table, Table 4.2, have the following meaning: Column Meaning Item Item number, incrementing with each item added to the table Service Option/ Optional Feature Description of the service option, or optional feature that might be supported by the implementation Status The status of th... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4.3 Format of the applicability Tables 4.3 and 4.4 | The columns in the applicability tables, Table 4.3 and Table 4.4, have the following meaning: Column Meaning Test ID A reference to the test identification(s), or range of test identifications detailed in the present document and required to validate the implementation of the corresponding item in the "Description" col... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4.4 Format of the conformance requirements tables | The columns in the requirement tables in clause 5 have the following meaning: Column Meaning Req.ID This column shows the ordinal term assigned to a requirement identified in the referenced specification. The following syntax has been used to define the unique R(equirement) terms: R<n><XX><YY>_<ZZZ> n: Identification l... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4.5 Numbers and Strings | The conventions used for decimal numbers, binary numbers and strings. Table 3.1: Convention of Numbering and Strings Convention Description nnnnn A decimal number, e.g. PIN value or phone number 'b' A single digit binary number 'bbbbbbbb' An 8-bit binary number 'hh' A single octet hexadecimal number 'hh hh…hh' A multi-... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4.6 Format of test description clauses | In general clauses with test descriptions use the following basic format: X.Y Group of test descriptions for a particular topic X.Y.1 Configurations This header is used in every clause that includes configuration descriptions. It may be followed by a sentence explaining that there are no specific configurations require... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 3.4.7 Dynamic content validation in ASN.1 structure | In certain test cases, dynamic content returned by the DUT (e.g. value within ASN.1 structure, signature, integer, …) is processed according to the following textX grammar: operations ::= '<' operation ( logical_operator operation)* '>' operation ::= operation_Identifier ' (' variable_identifier (',' parameter)* ')' op... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4 Tests environment architecture | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.1 Overview | Figure 4.1 illustrates the overview of the architecture for the SSP test environment. TEST TOOL REPORT FUNCTIONS APPLICATION EMULATOR FUNCTIONS Report SCL ANALYZER FUNCTIONS Test Descriptions SSP Rich OS ROUTER TERMINAL Test Tool Interface SUT Figure 4.1: SSP test environment overview The terminal shall contain: • An S... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.2 Test Tool Data exchange | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.2.1 Introduction | Figure 4.2 illustrates the data exchange between test tool and test tool interface. Figure 4.2: Data exchange between test tool and test tool interface ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 30 Release 15 The communication between the SUT and its environment is essentially based on the SCL network conveying the SCL p... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.2.2 Test tool requirements | The test tool shall be able to: • extract the semantic from the SCL packets and compare it with the expected results extracted from a test case; • emulate SSP/terminal applications to stimulate the SUT; • collect the events from the SUT in order to get the state of the SCL host in the SUT; • control the test tool inter... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.2.3 Test Tool interface requirements | The test tool interface plugged into the router shall support the following requirements: • It shall copy all SCL packets routed by the router into it, excluding the SCL packets from the SCL analyser. • It shall timestamp the copy of the SCL packet. • It shall be possible to disable the identification of the host issui... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.3 Test of a service in the SSP | Figure 4.3 illustrates the perspective of the tests of a service running in the SSP from an application running on the terminal. SSP SERVICE TERMINAL APPLICATION EMULATOR FUNCTIONS SCL ANALYZER FUNCTIONS REPORT SUT TEST TOOL REPORT FUNCTIONS Figure 4.3: Tests of a service in the SSP |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.4 Test of a service in the terminal | Figure 4.4 illustrates the perspective of the tests of a service running in the terminal from an application running in the SSP. ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 31 Release 15 TERMINAL SERVICE SCL ANALYZER FUNCTIONS SSP APPLICATION EMULATOR FUNCTIONS REPORT SUT TEST TOOL REPORT FUNCTIONS Figure 4.4: Tests of a ... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.5 Table of services | The product vendor shall declare which services are supported by their implementation. The services are listed in Table 4.1. See clause 3.4.1 for the format of the table. Table 4.1: Table of optional services Item Service Status Release Support Mnemonic 1 UICC File System Service Rel-15 O O_UICC_FS 2 Card Application T... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.6 Table of service options and other optional features | The product vendor shall declare which service options and other optional features are supported by their implementation. The service options and optional features are listed in Table 4.2. See clause 3.4.2 for the format of the table. Table 4.2: Table of service options and optional features Item Service Option/Optiona... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 4.7 Applicability table | The applicability tables in this clause are formatted as described in clause 3.4.3. Table 4.3: Applicability table for SSP Test ID Description Release Rel-15 FSS_0011 - FSS_0094 SSP File System Rel-15 C004 INI_001 Capability Exchange of SSPCapabilities Rel-15 M SCL_031 Data-flow control in multiple hosts environment Re... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5 Conformance requirements | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.0 Introduction | All references given in the conformance requirement descriptions are related to text, figures or tables provided in ETSI TS 103 666-1 [1]. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.1 SSP architecture | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.1.1 Overview | Reference: ETSI TS 103 666-1 [1], clause 5.1 RQ number Clause Description RQ0501_001 5.1 The SSP is a secure element platform intended for use in a number of use cases which may have very different requirements. For that reason, the SSP is designed to be a modular platform offering a core set of features as well as a n... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.1.2 SSP software architecture | Reference: ETSI TS 103 666-1 [1], clause 5.2 RQ number Clause Description RQ0502_001 5.2 SSP Applications are programs running in the SSP. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.1.3 SSP hardware architecture | Reference: ETSI TS 103 666-1 [1], clause 5.3 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 34 Release 15 |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.1.4 Protocol stacks | Reference: ETSI TS 103 666-1 [1], clause 5.4 RQ number Clause Description RQ0504_001 5.4 The physical interface(s) between the SSP and the device might be selected from a range of options. RQ0504_002 5.4 The SSP may have multiple physical interfaces. RQ0504_003 5.4 The data link layer used over the physical interface m... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.1.5 Execution framework | Reference: ETSI TS 103 666-1 [1], clause 5.5 RQ number Clause Description RQ0505_001 5.5 The optional or mandatory support of specific execution frameworks is defined for each specific SSP class. RQ0505_002 5.5 The SSP may support an execution framework as defined for the UICC according to ETSI TS 102 241 [14] based on... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2 SSP characteristics | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.1 Form factors | Reference: ETSI TS 103 666-1 [1], clause 6.1 RQ number Clause Description RQ0601_001 6.1 The overall definition of the SSP is independent of the form factor, unless specified differently for a particular SSP class. ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 35 Release 15 |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.2 Power | Reference: ETSI TS 103 666-1 [1], clause 6.2 RQ number Clause Description 6.2.1 Power mode RQ0602_001 6.2.1 The following power modes are defined: • OPERATIONAL: when the SSP performs an internal process or processes incoming data from any of its interfaces. This mode also includes the transmission of data from and to ... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.3 Clock | Reference: ETSI TS 103 666-1 [1], clause 6.3 RQ number Clause Description RQ0603_001 6.3 The SSP shall have its own clock for the processing of all the commands, for the execution of its applications and for the access to its volatile and non-volatile memory, unless specified otherwise by the SSP class. RQ0603_002 6.3 ... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.4 SSP initialization | Reference: ETSI TS 103 666-1 [1], clause 6.4 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 37 Release 15 RQ number Clause Description 6.4.1 SSP interface session RQ0604_001 6.4.1 The SSP interface session begins when the physical interface and the data link layer are initialized, and the SSP is in a state where it can recei... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.5 Storage | Reference: ETSI TS 103 666-1 [1], clause 6.5 RQ number Clause Description RQ0605_001 6.5 Whether the NVM is within the SSP or external to the SSP is SSP class dependant. Consequently, the technical specification of each SSP class shall indicate if the NVM is allowed to be internal and/or external. RQ0605_002 6.5 When t... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.6 Data Management | Reference: ETSI TS 103 666-1 [1], clause 6.6 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 39 Release 15 RQ number Clause Description 6.6.1 UICC file system RQ0606_001 6.6.1 The SSP may support the UICC file system as specified in ETSI TS 102 221 [7], clause 8.1, clause 8.2 and clause 8.3, and the associated security featur... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.7 SSP identification | Reference: ETSI TS 103 666-1 [1], clause 6.7 RQ number Clause Description RQ0607_001 6.7 The SSP identification mechanism for the SSP is dependent on the SSP class and is specified for each class. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.8 Runtime environment | Reference: ETSI TS 103 666-1 [1], clause 6.8 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 44 Release 15 RQ number Clause Description 6.8.1 CAT Runtime environment RQ0608_001 6.8.1 If SSP supports the CAT Runtime Environment as specified in ETSI TS 102 241 [14] based on the Java Card™ Platform [15], [16] and [17], then clau... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.9 SSP suspension | Reference: ETSI TS 103 666-1 [1], clause 6.9 RQ number Clause Description RQ0609_001 6.9 The usage of the suspension mechanism by terminal is allowed only if the SSP has a single active physical interface. RQ0609_002 6.9 When the SSP is suspended, the terminal deactivates the physical interface to the SSP, following th... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.10 SSP applications | Reference: ETSI TS 103 666-1 [1], clause 6.10 RQ number Clause Description 6. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.1 Overview | RQ0610_002 6.10.1 The SSP shall allow one or more SSP Applications to exchange data with other entities outside the SSP. RQ0610_003 6.10.1 If there are no restrictions of the execution environment and/or of the application protocol, One SSP Application shall not block another SSP Application from exchanging data with t... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.11 SSP security | Reference: ETSI TS 103 666-1 [1], clause 6.11 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 46 Release 15 RQ number Clause Description 6.11.1 SSP security architecture RQ0611_001 6.11.1 The SSP is intended to provide a programmable, secure execution environment for applications. RQ0611_002 6.11.1 Any entity external to the ... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.12 User interface | Reference: ETSI TS 103 666-1 [1], clause 6.12 RQ number Clause Description 6.12.1 Web-based user interface 6.12.1.1 Overview RQ0612_001 6.12.1.1 If the SSP supports the web-based user interface, it shall: • indicate the URL to be used for the entry page in the capability exchange, as defined in clause 6.4.2.5 of ETSI T... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.2.13 Accessor authentication service | Reference: ETSI TS 103 666-1 [1], clause 6.13 RQ number Clause Description 6.13.1. Overview RQ0613_001 6.13.1 Prior to access to a resource, an accessor shall authenticate itself based on some credentials with the accessor authentication service. 6.13.2. Access Control 6.13.2.1 Overview RQ0613_002 6.13.2.1 If an access... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.3 Physical interfaces | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.3.1 Overview | Reference: ETSI TS 103 666-1 [1], clause 7.1 RQ number Clause Description RQ0701_01 7.1 When the SSP contains two or more interfaces, each of them is completely independent, both electrically and logically. This implies that signalling on a contact assigned to one interface shall not affect the state of other contacts ... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.3.2 Reset | Reference: ETSI TS 103 666-1 [1], clause 7.2 RQ number Clause Description RQ0702_01 7.2 Each physical interface shall support at least one of the following reset types: • 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... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.3.3 ISO/IEC 7816 interface | Reference: ETSI TS 103 666-1 [1], clause 7.3 RQ number Clause Description 7.3.1 Electrical specifications 7.3.1.1 Electrical specifications of the interface RQ0703_01 7.3.1.1 For the electrical specifications of the interface the provisions of ETSI TS 102 221 [7], clause 5 shall apply with the following exceptions: • T... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.3.4 SPI interface | Reference: ETSI TS 103 666-1 [1], clause 7.4 RQ number Clause Description RQ0704_01 7.4 For the SPI interface the provisions of ETSI TS 103 713 [25] shall apply. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.4 SSP Common Layer (SCL) | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.4.1 Introduction | Reference: ETSI TS 103 666-1 [1], clause 8.1 RQ number Clause Description RQ0801_001 8.1 The SSP may support the SSP Common Layer (SCL) implementation comprised of optional network, transport and session layers. RQ0801_002 8.1 SCL shall be implemented using VNP, as specified in the GlobalPlatform VPP - Network Protocol... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.4.2 SCL network | Reference: ETSI TS 103 666-1 [1], clause 8.2 RQ number Clause Description RQ0802_001 8.2 The provisions of GlobalPlatform VPP - Network Protocol [10], clause 3 shall apply RQ0802_001a 8.2 The provisions of GlobalPlatform VPP - Network Protocol [10], clause 3 shall apply, with the exception listed below: • One of the en... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.4.3 Protocol layers | Reference: ETSI TS 103 666-1 [1], clause 8.3 RQ number Clause Description 8.3.1 Overview RQ0803_001 8.3.1 The provisions of GlobalPlatform VPP - Network Protocol [10], clauses 4.1 and 4.2 shall apply, with the exception listed below: • the MTU shall be 20 bytes or greater. RQ0803_002 8.3.1 For proper operation, the pro... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.4.4 SCL core services | Reference: ETSI TS 103 666-1 [1], clause 8.4 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 58 Release 15 RQ number Clause Description 8.4.1 Overview RQ0804_001 8.4.1 The provisions of GlobalPlatform VPP - Network Protocol [10], clause 5.1 shall apply for SCL core services. 8.4.2 Common core features RQ0804_002 8.4.2 The pro... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.4.5 SCL procedures | Reference: ETSI TS 103 666-1 [1], clause 8.5 RQ number Clause Description 8.5.1 Host registration RQ0805_001 8.5.1 The provisions of GlobalPlatform VPP - Network Protocol [10], clause 6.1.2 shall apply for the SCL host registration. 8.5.2 Host deregistration RQ0805_002 8.5.2 The provisions of GlobalPlatform VPP - Netwo... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.5 Secure SCL | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.5.1 Protocol Stack | Reference: ETSI TS 103 666-1 [1], clause 9.1 |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.5.2 Secure datagram | Reference: ETSI TS 103 666-1 [1], clause 9.2 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 60 Release 15 RQ number Clause Description RQ0902_001 9.2 The value of the DIVERSIFIER defined in clause C.4.2 of ETSI TS 103 666-1 [1] shall be the logical XOR of the aChallenge value as defined in clause 6.13.5.7 of ETSI TS 103 666-... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.5.3 Security protocol | Reference: ETSI TS 103 666-1 [1], clause 9.3 RQ number Clause Description 9.3.1 Overview 9.3.2 Shared secret initialization RQ0903_001 9.3.2 The Accessor Authentication Service (AAS) generates a challenge (aChallenge) and sends it with the certification path of the accessor authentication service to the Accessor Authen... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.5.4 Accessor authentication service procedure | Reference: ETSI TS 103 666-1 [1], clause 9.4 RQ number Clause Description 9.4.1 Initialization RQ0904_001 9.4.1 The accessor authentication application gate requests the initialization of the security protocol through AAS-OP-GET-CHALLENGE-Service-Command. RQ0904_002 9.4.1 The accessor authentication service gate return... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.6 Communication layers above SCL | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.6.1 Overview | Reference: ETSI TS 103 666-1 [1], clause 10.1 |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 5.6.2 APDU protocol | Reference: ETSI TS 103 666-1 [1], clause 10.2 ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 63 Release 15 RQ number Clause Description |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.2 Command-response pairs | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.2.1 General definition | RQ1002_001 10.2.2.1 The provisions of ISO/IEC 7816-4 [8], clause 5.1 shall apply, with the exceptions listed in the ETSI TS 103 666-1 [1], clause 10.2.2. 10.2.2.2 CLA Byte RQ1002_002 10.2.2.2 The provisions of ETSI TS 102 221 [7], clause 10.1.1 shall apply. 10.2.2.3 INS Byte RQ1002_003 10.2.2.3 SSP shall support follow... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.3 SSP commands | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.3.2 EXCHANGE CAPABILITIES | 10.2.3.2.1 Description RQ1002_007 10.2.3.2.1 EXCHANGE CAPABILITIES command shall be executed immediately after the SSP Interface Session is started. The command might be executed again if some of the capabilities change. RQ1002_008 10.2.3.2.1 The SSP and the terminal shall use the values exchanged during the last execu... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.3.3 SELECT | RQ1002_012 10.2.3.3 The provisions of ISO/IEC 7816-4 [8] and of ETSI TS 102 221 [7] for the SELECT command with P1 = '04' ("Select by DF name") shall apply. The coding of P2 is described in ETSI TS 103 666-1 [1], Table 10.3. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.4 Logical channels | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.4.1 Overview | RQ1002_013 10.2.4.1 The SSP indicates the maximum number of supported logical channels during the capability exchange with the terminal. RQ1002_014 10.2.4.1 A logical channel is opened by using a MANAGE CHANNEL command, in which the card assigns a channel number and returns it in the response. RQ1002_015 10.2.4.1 The l... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.5 UICC file system commands | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.5.2 Methods for selecting a file | RQ1002_018 10.2.5.2 The provisions of ETSI TS 102 221 [7], clause 8.4 shall apply. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.5.3 Reservation of file IDs | RQ1002_019 10.2.5.3 The provisions of ETSI TS 102 221 [7], clause 8.6 shall apply. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.5.4 Security features | RQ1002_020 10.2.5.4 The provisions of ETSI TS 102 221 [7], clause 9 shall apply. |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.5.5 Additional commands | RQ1002_021 10.2.5.5 In addition to the commands described in clause 10.2.3, these additional commands, as defined in ETSI TS 103 666-1 [1], Table 10.4, shall be supported by the SSP on the default logical channel. ETSI ETSI TS 103 999-1 V15.2.0 (2023-01) 64 Release 15 RQ number Clause Description |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.6 Card Application Toolkit | |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.6.1 Overview | RQ1002_022 10.2.6.1 When the SSP indicates support for Card Application Toolkit according to ETSI TS 102 223 [9], the provisions of ETSI TS 102 221 [7], clause 7.4.2 shall apply. RQ1002_023 10.2.6.1 When the physical interface used to transport APDUs allows the SSP to remotely wake up the terminal in case of proactive ... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.6.2 Terminal profile | RQ1002_026 10.2.6.2 The Card Application Toolkit terminal profile allows the SSP to determine what the terminal is capable of, and the SSP shall then limit its instruction range accordingly. RQ1002_027 10.2.6.2 If the terminal supports the Card Application Toolkit, the terminal profile shall be included in the capabili... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.6.3 Proactive polling | RQ1002_029 10.2.6.3 When the proactive polling is indicated as required in the capability exchange procedure, the terminal shall perform proactive polling as defined in ETSI TS 102 221 [7]. RQ1002_030 as defined in ETSI TS 102 221 [7] is optional: when the physical interface used to transport APDUs allows the SSP to re... |
3a2c501030e41dae8fd6f9bbdf81d510 | 103 999-1 | 10.2.6.4 Additional commands | RQ1002_032 10.2.6.4 In addition to the commands described in ETSI TS 103 666-1 [1], clause 10.2.3, these additional commands shall be supported by the SSP on the default logical channel as defined in Table 10.5 of ETSI TS 103 666-1 [1]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.