hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.8.3 SF-IDCHANGE-TRIGGER.confirm | SF-IDCHANGE-TRIGGER.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF-IDCHANGE-TRIGGER.request. The parameters shall be as described in Table 17. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 20 Table 17: SF-IDCHANGE-TRIGGER.confirm Name Type Valid range Description Status (none)... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.9 SF-ID-LOCK | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.9.1 Description | This service is needed in order to ask the Security entity to avoid IDCHANGEs for the number of seconds specified in duration. The lock will be released automatically afterwards or can be released by using SF-ID-UNLOCK. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.9.2 SF-ID-LOCK.request | SF-ID-LOCK.request is sent from the Facilities layer to the Security entity for executing the ID-LOCK service. The parameters shall be as described in Table 18. Table 18: SF-ID-LOCK.request Name Type Valid range Description Status Duration INTEGER 0 to 28 - 1 Number of seconds to lock Mandatory |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.9.3 SF-ID-LOCK.confirm | SF-ID-LOCK.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF-ID- LOCK.request. The parameters shall be as described in Table 19. Table 19: SF-ID-LOCK.confirm Name Type Valid range Description Status lock_handle INTEGER 0 to 264 - 1 Handle to unlock manually Mandatory |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.10 SF-ID-UNLOCK | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.10.1 Description | This service is used to release SF-ID-LOCK. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.10.2 SF-ID-UNLOCK.request | SF-ID-UNLOCK.request is sent from the Facilities layer to the Security entity for executing the ID-UNLOCK service. The parameters shall be as described in Table 20. Table 20: SF-ID-UNLOCK.request Name Type Valid range Description Status lock_handle INTEGER 0 to 264 - 1 Handle to unlock manually Mandatory |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.10.3 SF-ID-UNLOCK.confirm | SF-ID-UNLOCK.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF-ID- UNLOCK.request. The parameters shall be as described in Table 21. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 21 Table 21: SF-ID-UNLOCK.confirm Name Type Valid range Description Status (none) - - - - |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.11 SF-LOG-SECURITY-EVENT | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.11.1 Description | This service is used to insert external security events and is not specified in the present document. An example of a possible set of parameters associated to a SF-LOG-SECURITY-EVENT.request message is shown in clause 5.2.11.2. In this example, a SF-LOG-SECURITY-EVENT.confirm message (clause 5.2.11.3) does not contain ... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.11.2 SF-LOG-SECURITY-EVENT.request message example | SF-LOG-SECURITY-EVENT.request is sent from the Facilities layer to the Security entity for executing the LOG-SECURITY-EVENT service. Table 22 shows a possible set of parameters (and related status) associated to this message based on the example provided in [i.8] but further studies are needed. Table 22: SF-LOG-SECURIT... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.11.3 SF-LOG-SECURITY-EVENT.confirm message example | SF-LOG-SECURITY-EVENT.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to SF-LOG-SECURITY-EVENT.request. In this example, no parameters are associated to this message. Table 23: SF-LOG-SECURITY-EVENT.confirm Name Type Valid range Description Status (none) - - - - |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.12 SF-ENCAP | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.12.1 Description | This service is used for encapsulating outbound messages in a security envelope. This is an alternative way of calling the same functionality that SF-SIGN and/or SF-ENCRYPT offer, where the security parameter selection is done via a security profile parameter or security entity pre-sets. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.12.2 SF-ENCAP.request | The service primitive SF-ENCAP.request is sent from the Facilities layer to the security entity for executing the ENCAP service. The parameters shall be as described in Table 24. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 24 Table 24: SF-ENCAP.request Name Type Valid range Description Status tbe_packet_length INTEGER 0 to... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.12.3 SF-ENCAP.confirm | The service primitive SF-ENCAP.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to a SF-ENCAP.request. The parameters shall be as described in Table 25. Table 25: SF-ENCAP.confirm Name Type Valid range Description Status sec_packet_length INTEGER 0 to 216 – 1 Length of the Secur... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.13 SF-DECAP | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.13.1 Description | This service is used to decapsulate inbound messages from a security envelope. This is an alternative way of calling the same functionality that SF-VERIFY and/or SF-DECRYPT offer, and should be used together with SF-ENCAP. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.13.2 SF-DECAP.request | The service primitive SF-DECAP.request is sent from the Facilities layer to the Security entity for executing the DECAP service. The parameters shall be as described in Table 26. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 25 Table 26: SF-DECAP.request Name Type Valid range Description Status sec_packet_length INTEGER 0 to... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 5.2.13.3 SF-DECAP.confirm | The service primitive SF-DECAP.confirm is sent from the Security entity to the Facilities layer as a corresponding reply to a SF-DECAP.request. The parameters shall be as described in Table 27. Table 27: SF-DECAP.confirm Name Type Valid range Description Status plaintext_packet_ length INTEGER 0 to 216 - 1 Length of th... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6 SF-SAP procedures | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.1 Outbound message handling | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.1.1 Using SF-SIGN, SF-ENCRYPT | This clause specifies which service primitives can be used to secure outbound communication. Two different models can be distinct. First, using SF-SIGN and SF-ENCRYPT and second using SF-ENCAP, see clause 6.1.2. ETSI ETSI TS 102 723-9 V1.1.1 (2021-03) 26 The Facilities layer implementation can choose to add authorizati... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.1.2 Using SF-ENCAP | The difference in using SF-ENCAP over SF-SIGN and/or SF-ENCRYPT is that the selection of adding authorization information or encrypting a message is done inside the Security entity implementation. Therefore, SF-ENCAP always returns a security envelope, instead of a security header or encrypted message. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.2 Inbound message handling | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.2.1 Using SF-VERIFY and SF-DECRYPT | This clause specifies which service primitives can be used to secure inbound communication. Two different models can be distinct. First, using SF-VERIFY and SF-DECRYPT and second using SF-DECAP (see clause 6.2.2). When a Facilities layer message is received, the Facilities layer implementation can verify the sender aut... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.2.2 Using SF-DECAP | The SF-DECAP service corresponds to the SF-ENCAP service on the outbound side and shall decapsulate the security envelope and verify and/or decrypt its contents. |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.3 ID Management | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.3.1 IDCHANGE Notifications | |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.3.1.1 Introduction | Changing authorization tickets in the communication stack may only provide unlinkable pseudonymity, if all identifiers are exchanged at the same time. Therefore, all the IDs associated with an ITS station across different layers of the ITS stack shall be changed synchronously using the IDCHANGE Notification procedure. ... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.3.1.2 Id-change event hook | Each component, which wants to be notified by ID changes, has to offer a callback "Hook Function". This function shall accept the following commands: a) PREPARE Prepare for upcoming IDCHANGE b) COMMIT Commit IDCHANGE now c) ABORT IDCHANGE is aborted d) DEREG Registration cancelled by the Security entity |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.3.1.3 Two phase commit process | 1) Subscription For the Facilities layer subscription see Figure 10. 2) Two phase notification This is outlined in Figure 11, Figure 12 and Figure 13. An ID change notification is done in a two-phase commit process. First, the Hook Function is called with a PREPARE command. When all registered hooks have successfully r... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.3.2 Prevent IDCHANGES | Call ID-LOCK is used to prevent the Security entity from invoking IDCHANGES. Call ID-UNLOCK is used to unlock. The message flow is shown in Figure 16. NOTE 1: This could be used for example during sending of DENMs. They include a fixed action ID derived from the ITS station ID. NOTE 2: Safety applications such as colli... |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.3.3 Trigger IDCHANGES | Call IDCHANGE-TRIGGER is used to trigger the security entity to invoke an IDCHANGE. The message flow is shown in Figure 17. NOTE: This will not lead to an immediate IDCHANGE. The IDCHANGE two phase commit above will be invoked. Figure 17: Using IDCHANGE-TRIGGER |
99a51480dd5e479a2966fc75076aa11d | 102 723-9 | 6.4 Log security event | The security layer shall provide an interface that enables a stack layer to send a notification about a detected security event by the layer. Validation of plausibility of commonly used data (i.e. mobility and location information) is part of the Secure entity. Nevertheless, additional checks related to specific applic... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) and partial PIXIT pro forma to test the Application layer of ETSI ES 200 674-1 [1]. The objective of the present document is to provide test scripts for testing conformance of DSRC-HDR equipment specified in ETSI ES 200 674-1 [1] giving a high probability of i... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 2 References | |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 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. Referenced documents which a... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 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. NOTE: While any hyperlinks i... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 3 Definitions and abbreviations | |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI ES 200 674-1 [1], ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ETSI ES 201 873-1 [8] and the following apply: Abstract test case: Refer to ISO/IEC 9646-1 [4]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [4]. Abstract Test Suite (ATS): ... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI ES 200 674-1 [1], ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ETSI ES 201 873-1 [8] and the following apply: AL Application Layer APDU Application Protocol data Unit ASN.1 Abstract Syntax Notation 1 ATS Abstract Test Suite DLL Data Link Layer FCS Fra... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4 Abstract Test Method (ATM) | |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.0 Introduction | Clause 4 describes the Abstract Test Method used to test ETSI TS 102 708-2-2 [3]. |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.1 Protocol layer architecture | The implementation under test is the Application layer of ETSI ES 200 674-1 [1]. The System under test includes also the PHY layer and the LLC layer, which are necessary to perform the IUT tests. The tester executes the TTCN-3 scripts of the present document, running on an emulated PHY layer. Figure 1: Protocol layer a... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.2 Test system architecture | |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.2.1 The TTCN-3 test architecture | An abstract architecture for a test system (TS) implementing a TTCN-3 ATS is displayed in figure 2 and also stated in ETSI ES 201 873-5 [9]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adap... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.2.2 The HDR Application Layer test architecture | TTCN-3 Test Case _ MTC (TE + TM) Component type: AL_simu SUT Adapter TRI PHY testing controller HDR AL SUT (OBU or RSU) HDR AL Test System PHY layer emulation llc port ctrl port IUT (AL) DLL PHY Layer Client Application TTCN-3 action operation Figure 3: The HDR Application Layer Test System Architecture The HDR AL Test... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.2.3 Port mapping | |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.2.3.1 Mapping rules for the llc port | Only one TTCN-3 types is sent and received over the llc port: • the Lpdu type. ETSI ETSI TS 102 708-2-3 V1.5.1 (2018-08) 10 Table 2: Lpdu type mapping TTCN-3 type LLC frame field LlcAddressField LLC Address Field of the LPDU Apdu Information Field of the LPDU, containing the AL messages |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.2.3.2 Mapping rules for APDUs | In the ATS, the information field containing APDU is using a regular TTCN-3 type: Apdu. This type declares a message type structure that is defined with ASN.1 in the base standard ETSI ES 200 674-1 [1]. The ASN.1 definitions are mapped one to one to standard TTCN-3 type definitions. The encoding rules of ETSI ES 200 67... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 4.3 Type of SUT | Two types of systems under test (SUT) are distinguished, i.e. on-board units (OBUs) and road side units (RSUs). |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 5 Untestable test purposes | This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or other restrictions. Table 4: Untestable TP Test Case Name Reason void |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6 The ATS development process | |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of ETSI TS 102 708-2-2 [3]. The requirements applicable to this TP are given by a reference to ETSI ES 200 674-1 [1]. There are no explicit formulations of requirements. ETSI ETSI TS 102 708-2-3 V1.5.1 (2018-08) 11 |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6.2 Test case grouping | The ATS structure is based on the structuring of Test Purposes in clause 4 of ETSI TS 102 708-2-2 [3]. |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6.3 Test case identifier | The test case names are built in the TSS & TP document (ETSI TS 102 708-2-2 [3]) according to the following scheme: Table 5: TC identifier naming convention scheme TC_<st>_<pl_<g>_<x>_<nn> <st> = side type OBU On Board Unit RSU Road Side Unit <pl> = protocol layer AL Application Layer <g> test group KU Kernel Unit RA R... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6.4 ATS Library | For this ATS the TTCN-3 library modules are basically organized as: 1) LibCommon modules (only a sub-part of the modules of this library is used); 2) AL test suite modules. Table 6 shows the organization of the ATS as library of modules. Table 6: Library of modules Module Class Module Id Description LibCommon LibCommon... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6.5 TTCN-3 naming conventions | The naming conventions applied to the ATS are based on the following underlying principles: • the names of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or othe... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6.6 PICS information | Test purposes, which form the base test specification for this ATS, contain selection criteria using PICS parameters. Actually, a major part of the features described in the PICS are likely to be supported, even if the PICS status is "optional". Thus, the selection criteria will not be applied as a condition for the ex... |
660dcef4a04ff59b9c1067cce6004091 | 102 708-2-3 | 6.7 ATS archive | Annex B contains the ATS archive (.zip file expanding to text files with TTCN-3 code). ETSI ETSI TS 102 708-2-3 V1.5.1 (2018-08) 13 Annex A (normative): Partial PIXIT pro forma A.0 The right to copy Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 1 Scope | The present document covers additional test cases for the Host Controller to those specified in ETSI TS 102 695-1 [10]. The present document specifies the test cases for: • the HCI core as described in the first part of ETSI TS 102 622 [1]; • the contactless platform as described in the second part of ETSI TS 102 622 [... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 2 References | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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. NOTE: While any hyperlinks i... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 622 [1] and the following apply: allowed error response code: response code which is not ANY_OK and which is allowed for the referenced command as specified in ETSI TS 102 622 [1] non-occurrence RQ: RQ which has been extracted from ETSI TS 102 622... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 622 [1] and the following apply: PIPE0 the static pipe connected to the link management gate of the device under test. PIPE1 the static pipe connected to the administration gate of the device under test. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 622 [1] and the following apply: AC Alternating Current DUT Device Under Test FFS For Further Study HCUT Host Controller Under Test HS Host Simulator ICRx Initial Condition Requirement (where x is a number) NOTE: As used in the applicabili... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.4 Formats | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.4.1 Format of the table of optional features | The columns in table 4.1 have the following meaning. Column Meaning Option The optional feature supported or not by the DUT. Status See clause 3.4.3. Support The support columns are to be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [9], are used for the sup... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.4.2 Format of the applicability table | The applicability of every test in table 4.2 is formally expressed by the use of Boolean expression defined in the following clause. The columns in table 4.2 have the following meaning. Column Meaning Clause The "Clause" column identifies the clause containing the test case referenced in the "Test case number and descr... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.4.3 Status and Notations | The "Rel-x" columns show the status of the entries as follows: The following notations, defined in ISO/IEC 9646-7 [9], are used for the status column: M mandatory - the capability is required to be supported. ETSI ETSI TS 102 695-3 V13.0.0 (2019-04) 13 Release 13 O optional - the capability may be supported or not. N/A... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 3.4.4 Format of the conformance requirements tables | The conformance requirements tables contained in the present document have the following format and meaning: Column Status Meaning Mandatory This mandatory column contains the conformance requirement number (e.g. RQ3). Optional This optional column is present when the containing clause sources conformance requirements ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4 Test environment | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.1 Table of optional features | The device supplier shall state the support of possible options in table 4.1. See clause 3.4 for the format of table 4.1. Table 4.1: Options Item Option Status Support Mnemonic 1 Data link layer specified in ETSI TS 102 613 [2] is used. O O_102_613 2 ANY_OPEN_PIPE command transmission is implemented in the terminal. O ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.2 Applicability table | Tables 4.2 specifies the applicability of each test case to the device under test. See clause 3.4 for the format of tables 4.2. Clause 4.5.2 should be referenced for usage of the execution requirements which are referenced in table 4.2 a) and described in table 4.2 c). Table 4.2 a): Applicability of tests Clause Test c... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.1.1.2 Test case 1: valid pipe creation from host simulator to another host | Rel-7 SR2 M M M M M M M 5.5.1.1.3 Test case 2: pipe creation from host simulator to another host, host simulator not in other host's WHITELIST Rel-7 SR3 M M M M M M M 5.5.1.1.4 Test case 3: pipe creation from host simulator to another host, other host rejects pipe creation Rel-7 SR4 M M M M M M M |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.1.1.5 Test case 4: valid pipe creation from host controller to host simulator | Rel-7 TR4 C104 C104 C104 C104 C104 C104 C104 5.5.1.1.6 Test case 5: pipe creation from host simulator to host controller, pipe not supported by host controller Rel-7 SR5 M M M M M M M |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.1.2.2 Test case 1: valid pipe deletion from host simulator to another host | Rel-7 SR2 M M M M M M M 5.5.1.3.2 Test case 1: clear all pipes from host controller - static pipes, dynamic pipes to host Rel-7 TR5 C105 C105 C105 C105 C105 C105 C105 |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.5.2 Test case 1: pipe creation | Rel-7 M M M M M M M 5.6.3.3.4.2.2 Test case 1: MODE parameter Rel-7 C106 C106 C106 C106 C106 C106 C106 5.6.3.3.4.2.3 Test case 2: UID_REG - verify parameter Rel-7 C106 C106 C106 C106 C106 C106 C106 5.6.3.3.4.2.4 Test case 3: FWI, SFGI Rel-7 C106 C106 C106 C106 C106 C106 C106 5.6.3.3.4.3.2 MODE parameter Rel-7 C107 C107... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.4.2 Test case 1: NFCIP-1 command is not forwarded to UICC | Rel-9 N/A N/A C108 C108 C108 C108 C108 ETSI ETSI TS 102 695-3 V13.0.0 (2019-04) 16 Release 13 Clause Test case number and description Release Execution requirements Rel-7 Rel-8 Rel-9 Rel-10 Rel-11 Rel-12 Rel-13 Support 5.9.2.3.2 Test case 1: initial activation of APDU gate – Client APDU host Rel-12 TR6 N/A N/A N/A N/A ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.3 Information to be provided by the device supplier | The device supplier shall provide the information indicated in table 4.3. Table 4.3: Default configuration Item Description Presence/Value Status Mnemonic 1 Indication of presence of VERSION_SW, and value if supported. M V_VERSION_SW 2 Indication of presence of VERSION_HARD, and value if supported. M V_VERSION_HAR D 3 ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4 Test equipment | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4.0 Base Requirements | The test equipment shall provide a host simulator which is connected to the DUT during test procedure execution, unless otherwise specified. With respect to the DUT, the host simulator shall act as a valid host according to ETSI TS 102 622 [1] unless otherwise specified. In particular, the host simulator shall ensure t... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4.1 Measurement / setting uncertainties | Void. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4.2 Default conditions for DUT operation | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4.2.1 General | Unless otherwise specified, the following applies during test procedure execution. The test equipment shall attempt to ensure that the identity check mechanism of the lower layer passes (see ETSI TS 102 622 [1], clause 8.4). If the test procedure indicates that the host simulator is to send ANY_OK in response to an ANY... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4.2.2 Status of UICC interfaces | Void. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4.3 Minimum/maximum conditions for DUT operation | Void. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.4.4 Conventions | Unless otherwise specified, ADM_CREATE_PIPE is sent by the test equipment with source HID = HID of host simulator and destination HID = HID of host controller. If the pipe for a response is not explicitly specified, then the pipe for the response is required to be the pipe on which the preceding command was sent. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.5 Test execution | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.5.1 Parameter variations | Unless otherwise specified, all test cases shall be carried out in full power mode only, and for the parameter variations specified individually for each test case. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.5.2 Execution requirements | Table 4.2, Applicability of tests, specifies "execution requirements" for several test cases. For these test cases, it has not been possible to specify the corresponding test procedure in such a way that it can be guaranteed that the test procedure can be executed against every possible DUT. Some sample scenarios of te... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.6 Pass criterion | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.6.0 Principle | A test shall only be considered as successful, if the test procedure was carried out successfully under all parameter variations with the DUT respecting all conformance requirements referenced in the test procedure. This is subject to the additional qualifications described in clause 4.6.1. NOTE: Within the test proced... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 4.6.1 Unanticipated behaviour from the DUT | In the specification of the test procedures, every attempt has been made to ensure that the interface between the simulator and the DUT is in a known state before and during test procedure execution. However, as the DUT is an autonomous device, it is not possible to fully guarantee this. If the DUT unexpectedly closes ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5 Test cases | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.1 HCI architecture | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.1.1 Overview | Reference: ETSI TS 102 622 [1], clause 4.1. There are no conformance requirements for the terminal for the referenced clause. ETSI ETSI TS 102 695-3 V13.0.0 (2019-04) 20 Release 13 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.