hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.11 Signal to Distortion | The ratio of the output signal to output C-notched noise with a 1 004 Hz input signal while providing an on-hook and off-hook transmission path. 0 to -30-dBm0 input: > 33-dB ratio. -30 to -40-dBm0 input: > 27-dB ratio. ETSI ETSI TS 103 161-14 V1.1.1 (2011-04) 25 -40 to -45-dBm0 input: > 22-dB ratio. Reference: clause 5... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.12 Impulse Noise | ≤ 15 impulses in 15 minutes with no holding tone applied at a threshold of 47 dBrnC0. ≤ 15 impulses in 15 minutes with a -13 dBm0 tone at 1 004 Hz at a threshold of 65 dBrnC0. These should be met for both the on-hook and off-hook transmission path. For a line under test, other lines on the MTA should be active (off-hoo... |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.13 Intermodulation Distortion | R2 > 43 dB using a -13 dBm0 input signal. R3 > 44 dB using a -13 dBm0 input signal. R2 and R3 are the 2nd and 3rd order intermodulation products measured using the IEEE 743-1984 [12] 4-tone method. Reference: clause 5.17 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.14 Single Frequency Distortion | Using a 0 dBm0 input signal between 0 kHz to 12 kHz, the output between 0 kHz to 12 kHz <-28 dBm0. Using a 0 dBm0 input signal between 1 004 Hz to 1 020 Hz, the output between 0 kHz to 4 kHz <-40 dBm0. Reference: clause 5.19 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.15 Generated Tones | <-50 dBm0 between 0 kHz - 16 kHz. Reference: clause 5.20 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.16 Peak-to-Average Ratio | P/AR > 90 with a -13 dBm0 input level. On-hook and off-hook transmission paths. Reference: clause 5.21 of [8]. |
d8191d09f0a6a07fd74a38780931e30d | 103 161-14 | 8.4.17 Channel Crosstalk | With a 0-dBm0 signal between 200 Hz to 3 400 Hz applied to a line, other lines on the MTA <-65 dBm0 C message weighted output between 200 Hz - 3 400 Hz. Reference: clause 5.22 of [8]. ETSI ETSI TS 103 161-14 V1.1.1 (2011-04) 26 History Document history V1.1.1 April 2011 Publication |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 1 Scope | The present document covers the minimum characteristics considered necessary in order to provide compliance to ETSI TS 102 705 [1]. It specifies conformance test cases for the UICC Application Programming Interface for Java Card™ for contactless Applications. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 2 References | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 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... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 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... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 3.1 Terms | For the purposes of the present document, the following terms apply: applet installation parameters: values for applet installation parameters in the Install(Install) command Conformance Requirement Reference (CRR): description of the expected HCI API behaviour according to ETSI TS 102 705 [1] contactless mode: is used... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 705 [1] apply. ETSI ETSI TS 103 115 V10.0.0 (2024-06) 12 Release 10 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AID Application IDentifier APDU Application Protocol Data Unit NOTE: According to ISO/IEC 7816-3 [2]. API Application Programming Interface CAT Card Application Toolkit CB Chaining Bit CLF Contactless Front-end NOTE: According to ETSI TS 102 6... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 3.4 Formats | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 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 [8], are used for the sup... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 3.4.2 Format of the applicability table | The applicability of every test in table 4.2 a) is formally expressed by the use of Boolean expression defined in the following clause. The columns in table 4.2 a) have the following meaning. Column Meaning Clause The "Clause" column identifies the clause containing the test case referenced in the "Test case number and... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 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 [8], are used for the status column: M mandatory - the capability is required to be supported. O optional - the capability may be supported or not. N/A not applicable - in the given context, it is impossibl... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 4 Applicability | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 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 Card emulation, Type A O O_CE_TYPE_A 2 Card emulation, Type B O O_CE_TYPE_B 3 Card emulation, Type B' O O_CE_TYPE_B_PRIME 4 Card emulation, T... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 4.2 Applicability table | Table 4.2 a) specifies the applicability of each test case to the device under test. See clause 3.4 for the format of table 4.2 a). Clause 4.4 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... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.1 Method getHCIService | (ID2, ID4) Rel-9 SAA1 M M (ID1-1) Rel-9 SAA1 M M (ID1-2) Rel-9 SAA2, SAA1 M M (ID1-3) Rel-9 SAA3 M M (ID3-1) Rel-9 SAA6 N/A M (ID3-2) Rel-9 SAA1, SAA7 N/A M (ID3-3) Rel-9 SAA8 N/A M (ID5-1) Rel-9 SAA4, SAA1 M M (ID5-2) Rel-9 SAA3, SAA5 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.2 Method getPowerMode | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.3 Method isHCIServiceAvailable | (ID1-1) Rel-9 SAA1 M M (ID1-2) Rel-9 SAA2, SAA1 M M (ID1-3) Rel-9 SAA3 M M (ID2) Rel-9 M M (ID3-1) Rel-9 SAA1, SAA7 M M (ID3-2) Rel-9 SAA8 M M (ID4-1) Rel-9 SAA1, SAA4 M M (ID4-2) Rel-9 SAA3, SAA5 M M (ID5-1) Rel-9 SAA10 M M (ID5-2) Rel-9 SAA11 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.1 Method register | (ID1-1, ID3-1, ID4) Rel-9 SAA1 M M (ID1-2, ID2, ID3-2) Rel-9 SAA1, SAA2 M M (ID1-3, ID3-3) Rel-9 SAA3 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.2 Method deregister | (ID1-1, ID1-3) Rel-9 SAA1 M M (ID1-2, ID2) Rel-9 SAA1, SAA2 M M ETSI ETSI TS 103 115 V10.0.0 (2024-06) 15 Release 10 Clause Test case number and description Release Execution requirements Rel-9 UICC Rel-10 UICC Support |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.3 Method activateEvent | (ID1, ID4, ID6, ID7, ID8, ID9, ID10) Rel-9 SAA1 M M (ID2) Rel-9 SAA3 M M (ID3) Rel-9 SAA1, SAA2 M M (ID5-1) Rel-9 SAA10, SAA3 M M (ID5-2) Rel-9 SAA11, SAA3 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.4 Method deactivateEvent | (ID1, ID4, ID5) Rel-9 SAA1 M M (ID2) Rel-9 SAA3 M M (ID7) Rel-9 SAA3, SAA1 M M (ID3, ID6) Rel-9 SAA1, SAA2 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.5 Method requestCallbackNotification | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.6 Method getEventNotificationStatus | (ID1, ID2, ID5-1) Rel-9 SAA1 M M (ID3,ID4, ID5-2) Rel-9 SAA3 M M (ID5-3, ID6, ID7) Rel-9 SAA2, SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.3.1 Method isHeading | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.3.2 Method isComplete | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.3.3 Method getType | (ID1) Rel-9 SAA1 M M (ID2) Rel-9 SAA2, SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.3.4 Method getInstruction | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.3.6 Method getReceiveLength | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.3.7 Method getReceiveBuffer | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.4.1 Method throwIt | Rel-9 SAA1 M M |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.5.1 Method onCallback | (ID1, ID2) Rel-9 SAA1 M M (ID4) Rel-9 SAA1 C002 C002 (ID5) Rel-9 SAA1 C001 C001 6.2.1.1.1 Method prepareAndSendGetParameterCommand (ID1) Rel-9 SAA1 C001 C001 6.2.1.1.1 Method prepareAndSendGetParameterCommand (ID2) Rel-9 SAA1 C002 C002 6.2.1.1.1 Method prepareAndSendGetParameterCommand (ID3-1) Rel-9 SAA1 C001 C007 C001... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 4.3 Information provided by the device supplier | The device supplier shall provide the information indicated in table 4.3. Table 4.3: Information provided by device suppliers Item Description Value Mnemonic 1 Presence of an application associated to an contactless applet that can be launched in the terminal host using EVT_TRANSACTION AID, Parameters 2 Supported recei... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 4.4 Execution requirements | Table 4.2 a) specifies execution requirement (SAAn) for several test cases, to define the service availability and access possibility for the different services. For these test cases, the availability of the different services shall be guaranteed in order to execute the corresponding test procedure against the DUT. In ... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5 Test environment | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.0 Introduction | This clause specifies requirements that shall be met and the testing rules that shall be followed during the test procedure. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.1 Test environment description | The general architecture for the test environment is: Figure 5.1 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.2 Tests format | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.2.1 Test area reference | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.2.1.0 General | Each test area is referenced as follows: For HCI Framework and HCI services Testing: 'Api_[package name]_[class name]_[method name]' where • package name: - uicc.hci.framework: '1'. - uicc.hci.services: '2'. ETSI ETSI TS 103 115 V10.0.0 (2024-06) 19 Release 10 • class name: - yyy: 3 letters for each class/interface. ... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.2.1.1 Conformance requirements | The conformance requirements are expressed in the following way: • Method prototype as listed in ETSI TS 102 705 [1]. • Normal execution: - Contains normal execution and correct parameters limit values, each referenced as a Conformance Requirement Reference Normal (CRRN). • Parameters error: - Contains parameter errors... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.2.1.2 Test suite files | Each test suite files contains a table to indicate the correspondence between the applet names and the different test cases. Applet Name Test case ID [Test Area Reference]_[Test applet number].java Test case The test applets and the related Cap Files use the following naming convention: • Test Applet: [Test Area Refere... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.2.1.3 Initial conditions | In addition to the general precondtions defined in clause 5.3, this clause defines the initial conditions prior to the execution of each test case; i.e. for each ID. ETSI ETSI TS 103 115 V10.0.0 (2024-06) 20 Release 10 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.2.1.4 Test procedure | Each test procedure contains a table to indicate the expected responses form the API and APDU as follows. Test Case Id HCI commands API Description API Expectation HCI Response CRR Commands sent on HCI interface Test Case detailed description API expected behaviour Expected behaviour at APDU/HCI level Conformance Requi... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.3 Initial conditions | Unless otherwise specified, test cases shall be executed in full power mode only. The Initial Conditions are a set of general prerequisites for the UICC prior to the execution of testing. For each test procedure described in the present document, the following rules apply to the Initial Conditions: • unless otherwise s... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.4 Package name | Java packages integrating this Test Suite shall follow this naming convention: uicc.hci.test.framework.[Test Area Reference]: Java Card packages containing Test Area References for the ETSI TS 102 705 [1] uicc.hci.framework package. uicc.hci.test.services.cardemulation.[Test Area Reference]: Java Card packages containi... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.5 AID coding | The AID coding for the Test Packages, Applet classes and Applets shall be as specified in ETSI TS 101 220 [4]. In addition, the following TAR and Application Provider specific data values are defined for use within the present document: AID coding Byte 1 Byte 12 Byte 13 Byte 14 Byte 15 Byte 16 Application Provider spec... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.6 Test equipment | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.6.0 Introduction | These clauses recommend a minimum specification for each of the items of test equipment referenced in the tests. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.6.1 Test tool | This test tool shall meet the following requirements: • be able to send and receive commands using the underlying HCI resources (e.g. gates and pipes) defined by the HCI protocol as specified in ETSI TS 102 622 [3]; • be able to send and receive the commands correctly on the lower layer; i.e ETSI TS 102 613 [14]; • the... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 5.6.2 Java Software Development Kit | Java Card™ software development kit (SDK) version supported by Java Card 3.0.1 specifications ([11], [12] and [13]) is 1.5. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6 Test cases | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1 Package uicc.hci.framework | |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1 Class HCIDevice | 6.1.1.1 Method getHCIService |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.1.0 Text Area Reference | Test Area Reference: Api_1_Hdv_Gsr. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.1.1 Conformance requirements | 6.1.1.1.1.0 API definition The method with the following header shall be compliant to its definition in the API. public static HCIService getHCIService(short serviceID) throws HCIException, javacard.framework.SystemException 6.1.1.1.1.1 Normal execution • CRRN1: used to retrieve instances that implement one of HCIServi... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.1.2 Test suite files | Applet Name Test case ID Api_1_Hdv_Gsr_1.java 1 Api_1_Hdv_Gsr_2.java 2 Api_1_Hdv_Gsr_1.java 3 Api_1_Hdv_Gsr_1.java 4 Api_1_Hdv_Gsr_1.java 5 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.1.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI Interface. ETSI ETSI TS 103 115 V10.0.0 (2024-06) 24 Release 10 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.1.4 Test procedure | Test case ID HCI Command API Description API Expectation HCI Response CRR 1 Select supported and registered service 1 - EVT_SEND_DATA (INS = '01') getHCIService() serviceID = CARD_EMULATION_SERVICE_ID No exception shall be thrown EVT_SEND_DATA (SW - '90 00') N1, N2 2 - EVT_SEND_DATA (INS = '02') getHCIService() service... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.2.1 Conformance requirements | 6.1.1.2.1.0 API definition The method with the following header shall be compliant to its definition in the API. public static byte getPowerMode() 6.1.1.2.1.1 Normal execution • CRRN1: returns the current power mode of the UICC as defined in ETSI TS 102 613 [14]. • CRRN2: returns -1 if the power mode cannot be retrieve... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.2.2 Test suite files | Applet Name Test case ID Api_1_Hdv_Gpm_1.java 1 Api_1_Hdv_Gpm_1.java 2 Api_1_Hdv_Gpm_1.java 3 ETSI ETSI TS 103 115 V10.0.0 (2024-06) 26 Release 10 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.2.3 Initial conditions | • The UICC is not powered up. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.2.4 Test procedure | Test case ID HCI Command API Description API Expectation HCI Response CRR 1 Verify power mode - Activate the UICC in full power mode. - EVT_FIELD_ON - EVT_CARD_ACTIVATED - EVT_SEND_DATA (select applet) - EVT_SEND_DATA(INS='05') getPowerMode() return = FULL_POWER_MODE EVT_SEND_DATA (SW - '90 03') N1, N3 2 Verify power m... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.3.1 Conformance requirements | 6.1.1.3.1.0 API definition The method with the following header shall be compliant to its definition in the API. public static byte isHCIServiceAvailable(short serviceID) 6.1.1.3.1.1 Normal execution • CRRN1: this method is used to retrieve information about the availability of a HCIService more related to user interfa... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.3.2 Test suite files | Applet Name Test case ID Api_1_Hdv_Isa_1.java 1 Api_1_Hdv_Isa_1.java 2 Api_1_Hdv_Isa_1.java 3 Api_1_Hdv_Isa_1.java 4 Api_1_Hdv_Isa_2.java 5-1 Api_1_Hdv_Isa_3.java 5-2 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.3.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI interface. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.1.3.4 Test procedure | Test Case ID HCI/APDU Command API Description API Expectation HCI/APDU Response CRR 1 Retrieve information of an available service 1 - EVT_SEND_DATA (INS = '06') isHCIServiceAvailable() serviceID = CARD_EMULATION_SERVICE_ID 0x00 EVT_SEND_DATA (SW - '90 00', data byte set to '00') N1, N2 2 - EVT_SEND_DATA (INS = '07') i... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2 Interface HCIService | 6.1.2.1 Method register 6.1.2.1.0 Text Area Reference Test Area Reference: Api_1_Hsr_Reg. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.1.1 Conformance requirements | 6.1.2.1.1.0 API definition The method with the following header shall be compliant to its definition in the API. void register(HCIListener listener) throws HCIException 6.1.2.1.1.1 Normal execution • CRRN1: registers a Listener object to the Service instance. • CRRN2: a certain listener type can only be registered to t... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.1.2 Test suite files | Applet Name Test case ID Api_1_Hsr_Reg_1.java 1-1 Api_1_Hsr_Reg_3.java 1-2 Api_1_Hsr_Reg_5.java 1-3 Api_1_Hsr_Reg_1.java 2 Api_1_Hsr_Reg_2.java 3-1 Api_1_Hsr_Reg_4.java 3-2 Api_1_Hsr_Reg_6.java 3-3 Api_1_Hsr_Reg_1.java 4 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.1.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI interface. ETSI ETSI TS 103 115 V10.0.0 (2024-06) 30 Release 10 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.1.4 Test procedure | Test case ID HCI Command Description API Expectation HCI Response CRR 1 Register Listener to a service 1 - EVT_SEND_DATA (INS = '09') register() Service = CardEmulationService Listener = CardEmulationListener No exception shall be thrown EVT_SEND_DATA (SW - '90 00') N1 2 - EVT_SEND_DATA (INS = '09') register() Service ... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.2.0 Text Area Reference | Test Area Reference: Api_1_Hsr_Drg. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.2.1 Conformance requirements | 6.1.2.2.1.0 API definition The method with the following header shall be compliant to its definition in the API. void deregister(HCIListener listener) 6.1.2.2.1.1 Normal execution • CRRN1: deregisters a Listener object from the Service instance. • CRRN2: Calling deregister with an argument that does not identify a curr... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.2.2 Test Suite Files | Applet Name Test case ID Api_1_Hsr_Drg_1.java 1 Api_1_Hsr_Drg_2.java 2 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.2.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI interface. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.2.4 Test procedure | Test case ID HCI Command API Description API Expectation HCI Response CRR 1 Deregister Listener to a Service - CardEmulation 1 - EVT_SEND_DATA (INS = '01') register() Service = CardEmulationService Listener = CardEmulationListener deregister() Service = CardEmulationService No exception shall be thrown EVT_SEND_DATA (S... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.3.0 Text Area Reference | Test Area Reference: Api_1_Hsr_Ace. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.3.1 Conformance requirements | 6.1.2.3.1.0 API definitionThe method with the following header shall be compliant to its definition in the API void activateEvent(byte event) throws HCIException 6.1.2.3.1.1 Normal execution • CRRN1: This method is used to activate an event. • CRRN2: for all service interfaces HCIListener.EVENT_HCI_TRANSMISSION_FAILED ... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.3.2 Test Suite Files | Applet Name Test case ID Api_1_Hsr_Ace_1.java 1 Api_1_Hsr_Ace_3.java 2 Api_1_Hsr_Ace_2.java 3 Api_1_Hsr_Ace_1.java 4 Api_1_Hsr_Ace_7.java 5-1 Api_1_Hsr_Ace_9.java 5-2 Api_1_Hsr_Ace_4.java 6 Api_1_Hsr_Ace_5.java 7 Api_1_Hsr_Ace_6.java 8 Api_1_Hsr_Ace_8.java 9 Api_1_Hsr_Ace_6.java 10 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.3.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI Interface. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.3.4 Test procedure | Test Case ID HCI Command Description API Expectation HCI Response CRR 1 Event activation - CardEmulationService 1 - EVT_SEND_DATA (INS = '10') HCIListener = CardEmulationListener HCIService = CardEmulationService activateEvent() event = HCIListener.EVENT_HCI_TRANSMI SSION_FAILED No exception shall be thrown EVT_SEND_DA... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.4.1 Conformance requirements | 6.1.2.4.1.0 API definition The method with the following header shall be compliant to its definition in the API. void deactivateEvent(byte event) throws HCIException 6.1.2.4.1.1 Normal execution • CRRN1: deactivates an event from the list of activated events. • CRRN2: for all service interfaces HCIListenr.EVENT_HCI_TRA... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.4.2 Test suite files | Applet Name Test case ID Api_1_Hsr_Dae_1.java 1-1 Api_1_Hsr_Dae_1.java 1-2 Api_1_Hsr_Dae_2.java 1-3 Api_1_Hsr_Dae_2.java 1-4 Api_1_Hsr_Dae_5.java 2 Api_1_Hsr_Dae_4.java 3 Api_1_Hsr_Dae_1.java 4 Api_1_Hsr_Dae_3.java 5 Api_1_Hsr_Dae_6.java 6 Api_1_Hsr_Dae_7.java 7 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.4.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI interface. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.4.4 Test procedure | Test case ID HCI Command API Description API Expectation HCI Response CRR 1 Event deactivation - CardEmulationService 1 - EVT_SEND_DATA(INS='10') HCIService = CardEmulationService Event has been successfully activated deactivateEvent() event = HCIListener.EVENT_HCI_TRA NSMISSION_FAILED No exception shall be thrown EVT_... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.5.1 Conformance requirements | 6.1.2.5.1.0 API definition The method with the following header shall be compliant to its definition in the API. void requestCallbackNotification(byte event) throws HCIException 6.1.2.5.1.1 Normal execution • CRRN1: the call of this method throws HCIException with reason code HCI_ACCESS_NOT_GRANTED. ETSI ETSI TS 103 11... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.5.2 Test Suite Files | Applet Name Test case ID Api_1_Hsr_Rcn_7.java 1 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.5.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI interface. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.5.4 Test procedure | Test case ID HCI Command API Description API Expectation HCI Response CRR 1 Request Callback Notification EVT_SEND_DAT A (INS = '10') Precondition: HCIService = CardEmulationService Corresponding listener registered No event is activated requestCallbackNotification () event = HCIListener.EVENT_HCI_TRANSMISS ION_FAILED ... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.6.1 Conformance requirements | 6.1.2.6.1.0 API definition The method with the following header shall be compliant to its definition in the API. boolean getEventNotificationStatus(byte event) throws HCIException 6.1.2.6.1.1 Normal execution • CRRN1: return the activation state of an event; if true the event is activated for this listener, else false.... |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.6.2 Test Suite Files | Applet Name Test case ID Api_1_Hsr_Gen_1.java 1 Api_1_Hsr_Gen_1.java 2 Api_1_Hsr_Gen_3.java 3 Api_1_Hsr_Gen_3.java 4 Api_1_Hsr_Gen_1.java 5-1 Api_1_Hsr_Gen_3.java 5-2 Api_1_Hsr_Gen_2.java 5-3 Api_1_Hsr_Gen_2.java 6 Api_1_Hsr_Gen_2.java 7 |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.6.3 Initial conditions | • EVT_FIELD_ON has been sent on HCI interface. • EVT_CARD_ACTIVATED has been sent on HCI interface. • According applet has been successfully installed and selected using HCI Interface. |
8ab30b177b687b5379d0f429914883e7 | 103 115 | 6.1.2.6.4 Test procedure | Test case ID HCI Command API Description API Expectation HCI Response CRR 1 Event notification status false - CardEmulationService 1 - EVT_SEND_DATA (INS = '10') HCIService = CardEmulationService getEventNotificationStatus() event = HCIListener.EVENT_HCI_TRANSMI SSION_FAILED No exception shall be thrown. getEventNotifi... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.