hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.8 Handling Orientation Changes | The HSML Sink shall provide the framebuffer content in landscape orientation. Portrait orientation is not supported by the present document and shall not be used. The MirrorLink Client and Server should therefore disable the orientation switch support flag (bit 0 of the Framebuffer Configuration word) in the VNC Client... |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.2.9 Handling Content Attestation | The current HSML specification only supports the attestation of the Context Information via the exchange VNC ContentAttestation messages. See [2] for details. ETSI ETSI TS 103 544-21 V1.3.1 (2019-10) 27 |
d98880b80ed64a60a9499a4946d97f0e | 103 544-21 | 6.3.3 HSML Protocol Finite State Machine | Below is a diagram describing state transition of the HSML source and sink after receiving various requests from the HSML sink: • Uninitialized - Initial State; HSML Source and Sink are uninitialized. • Unconfigured - HSML Source and Sink are initialized but not configured. • Configured - HSML Source and Sink are initi... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 1 Scope | The present document specifies a protocol to enable secure communication sessions between network endpoints and one or more enterprise networks or between data centre middleboxes using encryption, whilst enabling network operations. The present document specifies an implementation variant of Transport Layer Security (T... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 2 References | |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-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... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-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... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 3 Definitions and abbreviations | |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: 1-sided: middlebox traffic observability enabled unilaterally by one endpoint such that the other endpoint is not able to reject or negotiate the traffic observability, other than by ceasing the communication eTLS: MSP profile describe... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN Abstract Syntax Notation CMS Cryptographic Message Syntax DDOS Distributed Denial Of Service DER Distinguished Encoding Rules eTLS enterprise TLS HTTP HyperText Transfer Protocol MSP Middlebox Security Protocol RSA Rivest-Shamir-Adleman TL... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4 The eTLS MSP profile | |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.1 MSP requirements mapping | MSP Part 1 [i.1] will define several Capability Requirements that are demanded of a profile wishing to comply with the MSP framework. The full and complete mapping of MSP Part 1 requirements to eTLS, the profile described in the current document, is left to a future revision of the present document when MSP Part 1 [i.1... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.2 eTLS implementation architecture | |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.2.1 eTLS with enterprise servers | Figure 4.1 depicts the eTLS implementation architecture when used with enterprise servers. TLS connections to clients that are external to an enterprise network or data centre may be made using TLS 1.3 [2], using forward secrecy and enhanced protections. The firewall terminates the Internet TLS 1.3 sessions and uses eT... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.2.2 eTLS with enterprise clients | Figure 4.2 depicts the eTLS implementation architecture when used with enterprise clients. TLS connections to servers that are external to an enterprise network may be made using TLS 1.3 [2], using forward secrecy and enhanced protections. Figure 4.2: eTLS architecture with enterprise clients The firewall terminates th... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3 eTLS protocol | |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.1 Normal TLS 1.3 Diffie-Hellman key exchange | For reference, a description of the normal TLS 1.3 Diffie-Hellman key exchange is included. Unless a pre-shared key is in use, the TLS 1.3 key exchange mechanism proceeds at the start of a new session as follows [2]: 1) The client generates an ephemeral Diffie-Hellman public and private key. The public key is transmitt... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.2 eTLS Diffie-Hellman key exchange | The eTLS key exchange shall use exactly the same messages and procedures to establish a set of session keys as a TLS 1.3 ephemeral Diffie-Hellman key exchange, except for two differences [2]. 1) the server shall use a static public/private key pair at Step 2 in clause 4.3.1; and 2) the server's certificate at Step 5 sh... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.3 Visibility information | In eTLS, the server certificate, as defined in Recommendation ITU-T X.509 [10], shall send visibility information in its certificate that shall: 1) Indicate that eTLS is being used. 2) Be bound to the static Diffie-Hellman public/private key pair for Step 2 of the eTLS protocol, described in clause 4.3.2. This public/p... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.4 Directly installed keys | The means by which an eTLS implementation shares the static Diffie-Hellman public/private key pair of clause 4.3.3 between an eTLS server and a middlebox is not specified, however the current clause and subsequent clauses 4.3.5 to 4.3.8 provide possible means without being exhaustive. The current clause describes perha... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.5 Centrally managed keys | Figure 4.3 shows the basic architecture for using a central key manager to deploy the eTLS static Diffie-Hellman key pairs to a key consumer, which could be an eTLS server or a passive decryption middlebox. The key manager generates the key pair. The key manager can actively push keys to the key consumer or the key con... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.6 Asymmetric key package | When an eTLS static Diffie-Hellman public/private key pair are sent from the key manager to a key consumer, they shall be packaged using the Asymmetric Key Package defined in IETF RFC 5958 [3]. Each Asymmetric Key Package shall contain one or more OneAsymmetricKey elements. Such an element will be one of either: a) a s... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.7 Protecting the key package | The Cryptographic Message Syntax (CMS) defined in IETF RFC 5652 [i.i.4] and IETF RFC 5083 [i.i.5] may be used to provide authentication, integrity and/or confidentiality to the Asymmetric Key Package transported between the key manager and the key consumer. |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.8 Transferring keys | |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.8.1 Protocol overview | eTLS Asymmetric Key Packages shall be transferred between the key manager and key consumer using HTTPS [11]. The HTTP messages containing key packages shall comprise a suitable HTTP header followed by the Asymmetric Key Package encoded using Distinguished Encoding Rules (DER) in binary format. The HTTP Content-Type hea... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.8.2 Transfer initiated by the key manager | Key consumers may support key transfers initiated by the key manager via an HTTPS key installation service, whereby the key manager initiates an HTTPS connection to the key consumer, which acts as an HTTP server. When key transfers initiated by the key manager via an HTTPS key installation service are supported by the ... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 4.3.8.3 Transfer initiated by the key consumer | Key managers may support key transfers initiated by the key consumer via an HTTPS key retrieval service, whereby the key consumer initiates an HTTPS connection to the key manager, which acts as an HTTP server. When key transfers initiated by the key consumer via an HTTPS key retrieval service are not supported by the k... |
2f52aae7bda3222c0108c2d10c7dd7a4 | 103 523-3 | 5 Security | eTLS does not provide all of the security guarantees provided by TLS 1.3. EXAMPLE 1: eTLS does not provide per-session forward secrecy. Knowledge of a given static Diffie-Hellman private key can be used to decrypt all sessions encrypted with that key, and forward secrecy for all of those sessions begins when all copies... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 1 Scope | The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1]. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 2 References | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 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... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 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... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 226 [1], ETSI TS 102 127 [11] and the following apply: Controlling Authority Security Domain (CASD): on-card controlling entity representing an off card trusted third party NOTE: It provides services to confidentially load or generate Secure Chann... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 3.2 Symbols | Void. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 226 [1], ETSI TS 102 127 [11] and the following apply: ACK ACKnowledge ADD Access Domain Data ADF Application Data File ADP Access Domain Parameter AES Advanced Encryption Standard AID Application IDentifier APDU Application Protocol Data ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 3.4 Formats | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 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 IUT. 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 [29], are used for the su... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 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 clause 3.4.3. 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 descrip... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 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 [29], 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 impossib... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 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 number 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: Identificati... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4 Test Environment | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.1 Test Applicability | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.1.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 CAT TP protocol is supported O O_CAT_TP 2 SMS protocol supported O O_SMS 3 HTTPS protocol supported O O_HTTPS 4 The TAR may be taken out of t... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.1.2 Applicability table | Table 4.2 a) and table 4.2 b) specify the applicability of each test case to the device under test. See clause 3.4 for the format of table 4.2 a). Table 4.2 a): Applicability of tests Clause Test case number and description Release Rel-11 UICC Rel-12 UICC Rel-13 UICC Rel-14 UICC Rel-15 UICC Rel-16 UICC Support 6.2.2.1 ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.1.1 Test case 1: DELETE command | Rel-11 M M M M M M 6.5.2.1 Test case 1: SET STATUS command within a command session Rel-11 M M M M M M ETSI ETSI TS 103 481 V16.5.0 (2026-03) 20 Release 16 Clause Test case number and description Release Rel-11 UICC Rel-12 UICC Rel-13 UICC Rel-14 UICC Rel-15 UICC Rel-16 UICC Support 6.5.3.1.1 Test case 1: INSTALL [for ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.4.1 Test case 1: LOAD with DES for DAP verification | Rel-11 C009 C009 C009 C009 C009 C009 |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.5.1 Test case 1: PUT KEY - create new 3DES 2 keys | Rel-11 M M M M M M 6.5.5.2 Test case 2: PUT KEY - create new 3DES 3 keys Rel-11 M M M M M M |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.5.4 Test case 4: PUT KEY - create new 16 bytes AES keys | Rel-11 M M M M M M 6.5.5.5 Test case 5: PUT KEY - create new 24 bytes AES keys Rel-11 M M M M M M |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.5.6 Test case 6: PUT KEY - create new 32 bytes AES keys | Rel-11 M M M M M M |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.6.1 Test case 1: GET STATUS with different P1 values | Rel-11 M M M M M M |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.6.2 Test case 2: GET STATUS with optional P1 values | Rel-11 C008 C008 C008 C008 C008 C008 6.5.6.3 Test case 3: GET STATUS returns Menu Entries in the LOCKED state Rel-11 M M M M M M |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.7.1 Test case 1: GET DATA for ISD | Rel-11 M M M M M M |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.7.2 Test case 2: GET DATA for APSD | Rel-11 M M M M M M |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.8.1 Test case 1: STORE DATA | Rel-11 FFS FFS FFS FFS FFS FFS |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.5.8.2 Test case 2: STORE DATA with a Forbidden Load File List | Rel-11 FFS FFS FFS FFS FFS FFS ETSI ETSI TS 103 481 V16.5.0 (2026-03) 23 Release 16 Clause Test case number and description Release Rel-11 UICC Rel-12 UICC Rel-13 UICC Rel-14 UICC Rel-15 UICC Rel-16 UICC Support 6.6.2.1 Test case 1: Send Secured Data (READ BINARY) using Expanded and Compact format with the same TAR val... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.6.2.3 Test case 3: PUSH Command, PoR required - No Error | Rel-11 C005 C005 C005 C005 C005 C005 Table 4.2 b): Conditional items referenced by table 4.2 a) Conditional item Description C001 IF ((O_CAT_TP OR O_SMS) AND O_CREATE_APSD) THEN M ELSE N/A C002 If ((O_CAT_TP OR O_SMS) AND O_Default_TAR AND O_CREATE_APSD) THEN M ELSE N/A C003 IF O_RM_A THEN M ELSE N/A C004 IF O_RM_B THE... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.2 Test environment description | The general architecture for the test environment is: Remote Applet Management OTA Security Mechanism Remote File Managment Implementation Under Test (IUT) Test Procedure exchange JCRE Scope of the Test Suite. Elements of the Test Suite Converter Loader Test applet Remote APDU Test Applets Applet Instalation parameter ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.3 Tests format | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.3.1 Initial Conditions | In addition to the general preconditions defined in clause 4.3, this clause defines the initial conditions prior to the execution of each test case; i.e. for each ID. ETSI ETSI TS 103 481 V16.5.0 (2026-03) 25 Release 16 |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.3.2 Test procedure | Each test procedure contains a table to indicate the expected responses form the UICC as follows: Step Description Expected Result RQ Commands with Secured Data content description Each step consists of a command which may contain a single command or a sequence of commands Expected returned Response with Secured Data c... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.4 General initial conditions | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.4.1 Common rules | The Initial Conditions are a set of general prerequisites for the IUT 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 stated, the file system and files content shall be restored to the contents definiti... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.4.2 File system and files content | Figure 4.3 shows the file system and the files content that the IUT shall contain to execute the test cases of this test specification, unless otherwise stated. The definition of other files is out of scope of the present document. ETSI ETSI TS 103 481 V16.5.0 (2026-03) 26 Release 16 Figure 4.3 Further information can ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.4.3 AID and TAR coding | The AID coding for the Test Packages, Applet classes and Applets shall be as specified in ETSI TS 101 220 [6]. 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 spe... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.5 Test equipment / OTA server | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.5.1 Test equipment / OTA server requirements | These sub-clauses recommend a minimum specification for each of the items of test equipment referenced in the tests. The simulator shall meet the following requirements: • be able to send and receive secure data commands to the IUT; • the result of I/O commands shall be presented at the application layer; • the structu... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.5.2 Default conditions for DUT operation | • Any level 1 user verification requirement (PIN, CHV if O_SIM is supported) on the IUT shall be enabled with three attempts remaining and ten unblock attempts remaining. • The default PIN value shall be set on the IUT to '31 31 31 31 FF FF FF FF'. • The default UNBLOCK PIN value shall be set on the IUT to '33 33 33 33... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.5.4 Exercising RFM application | An RFM application is required by various test cases in order to exercise the functionality which is being tested by these test cases. The term "exercising RFM application" is used for this RFM application: • If the UICC supports O_UICC_SHAR_RFM, the exercising RFM application shall be the UICC Shared File System RFM a... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 4.5.5 Test Applications | When communicating with Test Applications directly on the UICC-Terminal interface, a channel which is not the basic logical channel (channel 0) shall be used. Unless otherwise stated, a logical channel for this purpose shall be opened just before the first attempted selection of the Test Application directly on the UIC... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5 Conformance Requirements | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5.1 Overview of remote management | Reference: ETSI TS 102 226 [1], clause 4. RQ number Clause Release Description RQ01_0001 4 All data exchanged between the Sending Entity and Receiving Entity shall be formatted as "Secured data" according to ETSI TS 102 225 [2]. RQ01_0002 4 The parameter(s) (the command string) in the "Secured data" is either a single ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5.2 Remote APDU format | Reference: ETSI TS 102 226 [1], clause 5. RQ number Clause Description RQ02_0101 5.1.1 A command string may contain a single command or a sequence of commands. RQ02_0102 5.1.1 The structure of each command shall be according to the generalized structure defined below; each element other than the Data field is a single ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5.3 Security parameters assigned to applications | Reference: ETSI TS 102 226 [1], clause 6. RQ number Clause Release Description RQ03_0101 6.1 The Receiving Entity shall check the Minimum Security Level, set for the Receiving Application, before processing the security of the Command Packet. RQ03_0102 6.1 Up to Rel-11 If the check fails, the Receiving Entity shall rej... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5.4 Remote File Management (RFM) | Reference: ETSI TS 102 226 [1], clause 7. RQ number Clause Description RQ04_0101 7.0 The concept of embedding APDUs in a command packet and the Additional Response data in a response packet shall be as defined in the previous clauses describing the Compact and expanded Remote Application data format. RQ04_0102 7.0 Unle... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5.5 Remote Application Management (RAM) | Reference: ETSI TS 102 226 [1], clause 8. RQ number Clause Release Description RQ05_0101 8.0 Up to Rel-11 Remote Application Management on a UICC card includes the ability to load, install, and remove applications. RQ05_0102 8.0 Up to Rel-11 The Remote Application Management is under the control of a security domain wi... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5.6 Additional command for push | Reference: ETSI TS 102 226 [1], clause 9. RQ number Clause Description RQ06_0101 9.0 The PUSH command enables an application to open a BIP channel, to establish a CAT_TP link, to open a TCP connection and/or to send an identification packet on TCP upon a remote entity request. NOTE: RQ06_0101 is a definition. RQ number... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 5.7 Confidential application management | Reference: ETSI TS 102 226 [1], clause 10. NOTE: Requirements have only been extracted up to and including Rel-11 of ETSI TS 102 226 [1]. Requirements from Rel-12 and onwards of ETSI TS 102 226 [1] have not been extracted. RQ number Clause Description RQ07_0201 10.1 If confidential loading of applications is supported,... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6 Test Cases | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.1 Overview of remote management | Test cases verifying the requirements from this clause are defined under clauses 6.2.1, 6.4.1 and 6.5.3 of the present document. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2 Remote APDU format | |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.1 Compact Remote Application data format | Test cases verifying the requirements from this clause are defined under clause 6.4.1 of the present document. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2 Expanded Remote Application data format | 6.2.2.1 Test case 1: A command session with C-APDU TLV Structure with definite length coding |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.1.1 Initial Conditions | • None. ETSI ETSI TS 103 481 V16.5.0 (2026-03) 55 Release 16 |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.1.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains: - SELECT: MF - SELECT: DFTEST TLV Structure: C-APDU TLV Definite length coding Secured Response Data is returned: 'AB 07 80 01 02 23 02 90 00' RQ01_0001 R... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.2.1 Initial Conditions | • None. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.2.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains: - SELECT: MF - SELECT: DFTEST - SELECT: EFTARU - READ BINARY with wrong C-APDU Tag coded as: '23 05 00 B0 00 00 00' TLV Structure: C-APDU TLV Definite len... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.3.1 Initial Conditions | • None. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.3.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains: - SELECT: MF - SELECT: DFTEST TLV Structure: C-APDU TLV Indefinite length coding Secured Response Data is returned: 'AF 80 23 02 90 00 23 02 90 00 00 00' ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.4.1 Initial Conditions | • None. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.4.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains: - SELECT: MF - SELECT: DFTEST - SELECT: EFTARU - READ BINARY with wrong C-APDU coded as ' 23 05 00 B0 00 00 00' TLV Structure: C-APDU TLV Indefinite lengt... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.5.1 Initial Conditions | • On the UICC-Terminal interface, prior to this test the Terminal shall have been powered on and performed the PROFILE DOWNLOAD procedure. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.5.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains: - Immediate Action TLV, normal format, DISPLAY TEXT - C-APDU TLV, SELECT: MF Definite length coding On the UICC-Terminal interface: The proactive session ... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.6.1 Initial Conditions | • On the UICC-Terminal interface, prior to this test the Terminal shall have been powered on and performed the PROFILE DOWNLOAD procedure on the UICC/terminal interface. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.6.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains the following in Definite length coding: - Immediate Action TLV, referenced format containing proactive session indication ('81') - Immediate Action TLV, n... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.7.1 Initial Conditions | • On the UICC-Terminal interface, prior to this test the Terminal shall have been powered on and performed the PROFILE DOWNLOAD procedure. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.7.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which consist of 2 Command TLV having the following TLV Structure: Immediate Action TLV using referenced format containing proactive session indication ('81') followed by... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.8.1 Initial Conditions | • On the UICC-Terminal interface, prior to this test the Terminal shall have been powered on and performed the PROFILE DOWNLOAD procedure. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.8.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains: - Immediate Action TLV, normal format, DISPLAY TEXT - C-APDU TLV, SELECT: MF Indefinite length coding. On the UICC-Terminal interface: The proactive sessi... |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.9.1 Initial Conditions | • On the UICC-Terminal interface, prior to this test the Terminal shall have been powered on and performed the PROFILE DOWNLOAD procedure. |
6e25bf9319de604515be87f207fb2d40 | 103 481 | 6.2.2.9.2 Test Procedure | Step Description Expected Result RQ 1 Send Command with Secured Data coded as: [Expanded Remote command structure] to the Exercising RFM application, which contains the following: - Immediate Action TLV, referenced format containing proactive session indication ('81') - Immediate Action TLV, normal format, DISPLAY TEXT... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.