hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 3 Definitions and abbreviations | |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: exclusion zone: geographical area within which LSA Licensees are not allowed to have active radio transmitters NOTE: An exclusion zone is normally applicable for a defined frequency range and time period. ETSI ETSI TS 103 154 V1.1.1 (2... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project CEPT Conférence des administrations Européennes des Postes et Télécommunications ECC Electronic Communications Committee of the CEPT ECS Electronic Communications Services EIRP Effective Isotropic Radiat... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 4 Requirement Organization and Methodology | This clause contains a description of how the requirements are organized and the format of the requirement. |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 4.1 Requirement Organization | As shown in Figure 4.1, the requirements described in the present document belong to two different categories: the functional requirements and the performance requirements. Each category, in turn, is organized into groups. Figure 4.1: Requirements Organization |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 4.2 Requirement Format | A letter code system is defined which makes a unique identification of each requirement R-<CAT>-<GROUP>-<XX>. It should be constructed as follows: • R- : Standard requirement prefix • <CAT>: Code Category FUNC Functional aspects PERF Performance aspects • <GROUP>:Requirement group identifier. A three-letter code will b... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 4.3 Requirement Formulation | A requirement is formulated in such a way that it is uniquely defined. It is built as follows: Title: <Title Description> Description: the description of a requirement will be formulated using one of the following terms: • "shall" is used to express mandatory requirements (i.e. provisions that have to be followed) • "s... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 4.3.1 LSA Roles | Requirements are formulated in regards of the "LSA System" and make use of generic "LSA roles", as shown in Figure 4.2. Figure 4.2: LSA Roles Roles are abstracted concepts defined for requirement formulation; in specific deployments, roles will be performed by specific entities (e.g. the LSA Licensee role would be perf... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 5 Working Assumptions | The working assumptions described below are based on ETSI TR 103 113 [i.1], and particularly the use case "Bandwidth Expansion for Mobile Network Operator" in clause 7.1.2 of [i.1], as well as the ECC Report 205 [i.2] and the RSPG opinion on LSA [i.3]. ETSI ETSI TS 103 154 V1.1.1 (2014-10) 10 |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 5.1 Regulatory Background | It is assumed that, prior to implementation of LSA, the 2 300 - 2 400 MHz frequency band (or a sub-band) is used by one or more non-IMT services, provided by current holder(s) of spectrum rights of use. LSA provides for some administrations a solution to enable access to the 2 300 - 2 400 MHz frequency band for MFCN an... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 5.2 Spectrum Sharing Arrangement | The set of practical details for a given LSA spectrum resource is referred to in the present document as a Sharing Arrangement. A Sharing Arrangement may be subject to change, but it should remain consistent with the Sharing Framework defined by the Administration/NRA and the obligations placed in the "Authorization" D... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 5.3 LSA System Administration by Trusted 3rd Party Users | It is assumed that the LSA System or part(s) thereof may be administered by trusted 3rd party user(s) with defined access rights. ETSI ETSI TS 103 154 V1.1.1 (2014-10) 11 |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6 Functional System Requirements | |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1 General System Operation | This clause comprises functional requirements that relate to the general system operation. |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.1 R-FUNC-GEN-01 LSA Spectrum Resource Sharing | The LSA System shall support flexible spectrum resource sharing in the 2 300 - 2 400 MHz frequency band (or a sub-band thereof) between the Incumbent(s), and a limited number of LSA Licensees (MFCNs), according to the applicable LSA Sharing Framework. Explanation: In general, spectrum assigned to Incumbent(s), may be u... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.2 R-FUNC-GEN-02 Quality of Service | The LSA System shall facilitate the provision of a predictable Quality of Service (QoS) for both Incumbents and LSA Licensees, whenever operation by a particular service is allowed by the system. Explanation: The LSA System supports sharing on a non-interfering basis, meaning that the sharing systems will operate witho... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.4 R-FUNC-GEN-04 Multiple MFCN Support | The LSA System shall allow the Incumbent to interact with one or more LSA Licensees for spectrum sharing purposes. Explanation: A single Incumbent user may communicate with multiple MFCNs to provide information on the LSA spectrum resource available to each. For example, an Incumbent may have usage rights for a 20 MHz ... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.5 R-FUNC-GEN-05 Multiple Incumbent User Support | The LSA System shall allow an MFCN to interact with one or more Incumbents for spectrum sharing purposes. Explanation: A particular MFCN may be authorized as an LSA Licensee of different LSA spectrum resources, each shared with a particular Incumbent. For example, it may have usage rights to two different sub-bands, ea... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.6 R-FUNC-GEN-06 Sharing Framework Support | The LSA System shall support the use of a Sharing Framework as defined on national level. Explanation: The Sharing Framework is described in the working assumptions (clause 5.1). |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.7 R-FUNC-GEN-07 Confidentiality of Spectrum Resource Information | The LSA System shall support mechanisms to ensure that, for a particular Sharing Framework, the information on the associated available LSA spectrum resource may only be accessed by the concerned Incumbent and LSA Licensee. Explanation: The LSA System contains information as to which entity (the Incumbent or the LSA Li... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.8 R-FUNC-GEN-08 Provision of Failure Indication | The LSA System shall have means to provide failure indications to both the LSA Licensee and the Incumbent, following the detection of any critical system failure that may result in harmful interference. Explanation: Under some circumstances, failures may occur which prevent normal operation of the LSA System. A simple ... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.9 R-FUNC-GEN-09 LSA System Data Storage Function | The LSA System shall support the entry, storage and modification of information required for LSA operation. Explanation: The LSA System supports receiving and maintaining information required for the operation of LSA, including LSA spectrum resource definitions, sharing rule definitions (from the Sharing Framework, the... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.10 R-FUNC-GEN-10 LSA System Reporting Function | The LSA System shall support the capability to generate reports on LSA operation, covering as a minimum the availability of LSA spectrum resource through LSA operation, and the occurrence of critical events such as LSA spectrum resource evacuation. Such reports may be provided on-demand, or according to a schedule. ETS... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.11 R-FUNC-GEN-11 Support of Scheduled Operation | The LSA System shall support a scheduled mode of operation for spectrum resource sharing. Explanation: In this mode of operation, the LSA spectrum resource availability information changes at pre-set times according to a schedule. For example, the schedule may be part of the sharing rules, or it could be entered by the... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.12 R-FUNC-GEN-12 Support of On-Demand Operation | The LSA System shall support an on-demand mode of operation for spectrum resource sharing. Explanation: In this mode of operation, the Incumbent's LSA spectrum resource usage and protection requirements are modified, and the resulting LSA spectrum resource availability information is communicated to the LSA Licensee. T... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.13 R-FUNC-GEN-13 Support for Pre-Configuration | The LSA System shall support the pre-configuration of the Incumbent's LSA spectrum resource usage and protection requirements (and associated LSA spectrum resource availability information), such that there will be a finite set of possible combinations of such requirements. Such pre-configuration may apply to the entir... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.14 R-FUNC-GEN-14 Verification of Inputs to the LSA System | The LSA System shall support the capability to verify the consistency and validity of its inputs, and in particular, it shall be able to: • reject a requested change in the Incumbent's LSA spectrum resource usage and protection requirements, if it fails to meet a specific condition (e.g. within the Sharing Framework, t... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.1.15 R-FUNC-GEN-15 LSA System Availability to Stakeholders | The LSA System shall incorporate mechanisms to maintain robustness against failures and malicious attacks such that the spectrum sharing arrangement between an Incumbent and an LSA Licensee can be fulfilled by the LSA system with a predictable level of certainty in its availability to stakeholders. Explanation: The LSA... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.2 Incumbent Protection Requirements | This clause contains functional requirements that relate to the protection of the Incumbent. |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.2.1 R-FUNC-INC-01 Protection of Information of the Incumbent | The LSA System shall allow the Incumbent to store a description of the LSA spectrum resource and its availability. This excludes any need to provide details on the network and actual usage of the LSA spectrum resource not available to the LSA Licensee. Explanation: Neither network details of the Incumbent (e.g. deploym... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.2.2 R-FUNC-INC-02 General Protection of the Incumbent | The LSA System shall support mechanisms to ensure that the Incumbent's LSA spectrum resource usage and protection requirements are met, and in particular it shall provide LSA spectrum resource availability information to the LSA Licensee that will be such as to meet these requirements. Explanation: The LSA System is ab... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.3 Resource Grant Requirements | This clause contains functional requirements that relate to the process of granting the use of LSA spectrum resource to the LSA Licensee. Note that the term "grant" refers here to the process of providing information to the Licensee regarding the available LSA spectrum resource, and is different from usage in a regulat... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.3.1 R-FUNC-GRA-01 Protection of Information of the LSA Licensee | The LSA System shall be able to derive and communicate the LSA spectrum resource availability information to the appropriate LSA Licensee, without knowledge of the information related to its MFCN, or related to its usage of the LSA spectrum resource. Explanation: Information related to the MFCN is confidential data of ... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.3.3 R-FUNC-GRA-03 General Protection of the LSA Licensee | The LSA System shall support mechanisms to ensure that the LSA Licensee's protection requirements related to the LSA spectrum resource are met, when the LSA spectrum resource is available to the LSA Licensee. Explanation: The LSA System needs to ensure that the LSA Licensee will not experience harmful interference when... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.3.4 R-FUNC-GRA-04 Variation of LSA Licensee's Protection | The LSA System shall support a modification of the LSA Licensee's LSA spectrum resource usage and protection requirements following a change in the spectrum sharing arrangement. Explanation: The sharing arrangement may contain an option to change practical details (e.g. this input is typically used to optimize the LSA ... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.4 Security Requirements | This clause contains functional requirements that relate specifically to security aspects of the LSA System. |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.4.1 R-FUNC-SEC-01 Data Integrity | The LSA System shall incorporate mechanisms to ensure the integrity of the data stored in the system and the data exchanged between any of: the LSA System, Incumbents, LSA Licensees and Administration/NRA. The LSA System shall ensure the availability of the information to the authorized recipients and shall support sec... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.4.2 R-FUNC-SEC-02 Data Authenticity | The LSA System shall incorporate mechanisms to ensure the authenticity of the information stored in the system and exchanged between any of: the LSA System, Incumbents, LSA Licensees and Administration/NRA. Explanation: In contrast to integrity, which relates to the content of the information, the authenticity is conce... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.4.3 R-FUNC-SEC-03 Data Confidentiality | The LSA System shall incorporate mechanisms to prevent unauthorized disclosure of confidential information that the system maintains and that is exchanged between any of: the LSA System, Incumbents, LSA Licensees and Administration/NRA. Explanation: An LSA System may support many Incumbents and LSA Licensees and mainta... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.4.4 R-FUNC-SEC-04 Identity management and authentication | The LSA System shall allow to manage identities and authentication of users. This includes configuration, reconfiguration and deletion of identities. Explanation: In order to enforce the limitations of access rights and other security requirements, it is necessary to identify the users who access the system and to prov... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 6.4.5 R-FUNC-SEC-05 Support of Authorization Profiles | The LSA System shall distinguish between different authorization profiles assigned to user groups of the LSA System based on their identification, and shall allow the specification and enforcement of applicable access rights. Explanation: Different authorization profiles may be used to differentiate authorizations of i... |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 7 Performance Requirements | |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 7.1 Incumbent Protection Performance Requirements | Not applicable. |
a541ae1ff4a82f536d9e1205a5551308 | 103 154 | 7.2 Resource Grant Performance Requirements | 7.2.1 R-PERF-GRA-01 Lead Time for Modification of LSA Spectrum Resource The LSA System shall allow modification of the definition of LSA spectrum resource and of respective sharing arrangement provisions to become operational after a lead time. Explanation: The definition of the LSA spectrum resource and respective sha... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 1 Scope | The present document provides a definition of Duty Cycle Template (DCT) to be used as a frequency and application independent passive mitigation technique, and associated conformance measurement methods. DCT consists of an active transmission interval followed by an inactive idle interval. The combination of these two ... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 2 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... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TR 100 028 (V1.4.1) (all parts): "Electromagnetic compatibility and Radio spectrum Matters (ERM); Uncertainties in the measurement of mobile radio equipment characteristics". [2] ANSI C63.5-2006: "American National St... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 3 Definitions, symbols and abbreviations | |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Duty Cycle Template (DCT): result of Cumulative On-Time (Ton_cum) divided by the Observation period (Tobs) NOTE: The DCT could be defined for one or more values of Observation period (Tobs). More details are described in clause 4.2. |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: Fmb Mitigation bandwidth NOTE: See clause 4.1. PThresh Threshold NOTE: See clauses 4.1 and 4.2. T Time Tdis Disregard-Time Tobs Observation period NOTE: See clause 4.1.4. Toff Off-Time NOTE: See clause 4.1.7. Ton On-Time NOTE: See clause 4.1.5. Ton_... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CF Centre Frequency DC Duty Cycle DCT Duty Cycle Template NOTE: See clause 4.2. DSO Digital Storage Oscilloscope ERM Electromagnetic compatibility and Radio spectrum Matters EUT Equipment under Test ETSI ETSI TS 103 060 V1.1.1 (2013-09) 7 FFT ... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4 Duty Cycle Template | |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1 Parameter Definitions | |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1.1 Transmission | A Transmission is a continuous radio emission, or sequence of emissions separated by intervals shorter than Tdis (see clause 4.1.7.2), with a signal level greater than PThresh (see clause 4.1.2), within the Mitigation Bandwidth Fmb (see clause 4.1.3). |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1.2 PThresh | Unless otherwise defined PThresh is -26 dBc for systems other than UWB and -10 dBc for UWB systems. 4.1.3 Mitigation bandwidth (Fmb) Fmb is the victim receiver bandwidth in which the energy of a DCT device occurs during the operation of that DCT device. If the victim receiver is frequency agile, Fmb includes the time-f... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1.4 Observation period (Tobs) | Tobs is defined as a reference interval of time. 4.1.5 On-Time (Ton) Ton is defined as the duration of a Transmission. This is illustrated in Figure 1. |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1.5.1 Maximum On-Time (Ton_max) | Ton_max is defined as the maximum permissible value of Ton. |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1.6 Cumulative On-Time (Ton_cum) | Ton_cum is defined as the sum of the individual Ton times, or part thereof, within Tobs, example, see Figure 1. ETSI ETSI TS 103 060 V1.1.1 (2013-09) 8 In this example: Ton_cum = Ton,1 +Ton,2*. Figure 1: Example for Cumulative On-Time |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1.7 Off-Time (Toff) | Toff is defined as the time duration between two consecutive Transmissions (see Figure 1). 4.1.7.1 Minimum Off – Time (Toff_min) Toff_min is defined as the minimum permissible value of Toff. 4.1.7.2 Disregard-Time (Tdis) Tdis is defined as the time interval below which interruptions within a Transmission are considered... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.1.8 Average Off-Time (Toff_avg) | Toff_avg is defined as the average (mean) Toff time over Tobs. This parameter is only relevant for UWB systems. |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 4.2 DCT Definition | DCT is defined as: Respecting the constraints of Ton_max and Toff_min. Tobs may take different values for specific cases. DCT is defined for one or more values of Tobs. It has to be noted that values of Tobs shall be defined by regulation. |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5 Conformance test methods | 5.1 Measurement setup for measuring Ton, Toff, Ton_cum using declared Tdis To measure the duty cycle template (DCT) the measurement instrument shall have a sufficiently high acquisition bandwidth, sampling rate, and data storage capacity suitable for the mitigation bandwidth and the observation time Tobs. Possible solu... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5.1.1 Conducted measurements | The preferred method of measurement is conducted (see Figure 3). The antenna output of the EUT is directly connected to the input of the measurement equipment, if possible via a variable attenuator. The preferred setup consists of a band pass filter (pass band equal to Fmb) connected to either a threshold detector (sen... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5.1.3 Triggered acquisition of signals | For large observation periods Tobs continuous recording of the EUT signal may not be feasible due to memory limitations of the measurement equipment. In this case acquisition of the signal is triggered on a defined power level. This trigger level should be lower than Ptresh in order to capture the entire signal of inte... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5.2.1 Single channel measurement | 1) The Ton time of a transmission is the period that the envelope is above the Pthres. The measurement shall be done over at least 10 transmissions and the highest Ton value shall be noted. 2) The highest cumulative Ton time within the reference period Tobs shall be calculated and noted. 3) The Toff time between transm... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5.2.2 Multiple channel measurement | 1) The Ton time of a transmission is the period that the envelope is above the Pthres. The measurement shall be done over at least 10 transmissions and the highest Ton value shall be noted. 2) The highest cumulative Ton time within the reference period Tobs shall be calculated and noted. 3) The Toff time between transm... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5.3 Measurement Procedure for UWB systems | |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5.3.1 Time domain measurement | This procedure uses the preferred measurement setup depicted in Figure 3, Figure 4, Figure 6, or Figure 7: 1) For this measurement, a DSO will be used. 2) Switch the EUT to normal operation. For frequency hopping devices, hopping shall be enabled. 3) Adjust the DSO settings so that the signal is displayed for duration ... |
aed6db47ecc7782a4757cdd9316bba19 | 103 060 | 5.3.2 Time and Frequency Domain measurement (Spectrogram) | This procedure uses the alternative measurement setup depicted in Figure 5 or Figure 8: 1) Switch the EUT to normal operation. For frequency hopping devices, hopping shall be enabled. 2) If a DSO is used it shall be switched to frequency domain analysis mode (FFT). 3) On the RTSA or DSO select a frequency and span suit... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 1 Scope | The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 600 [1]. The present document specifies the test cases for: • the characteristics of the Inter-Chip USB electrical interface between the USB UICC and the USB UICC-enabled ter... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 2 References | |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 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... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 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... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 600 [1] and ETSI TS 102 221 [2] apply. |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 600 [1] and ETSI TS 102 221 [2] apply. ETSI ETSI TS 102 922-2 V7.1.0 (2025-10) 12 Release 7 |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 600 [1], ETSI TS 102 221 [2] and the following apply: CBW Command Block Wrapper CSW Command Status Wrapper DUT Device Under Test EEM Ethernet Emulation Model FFS For Further Study GND GrouND IC Inter-Chip ICCD Integrated Circuit Card Devic... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 3.4 Formats | |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 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 implementation. Status See clause 3.4.3 "Status and Notations" Support The support columns should be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 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 of the present document. The columns in table 4.2 have the following meaning. Column Meaning Test case The "Test case" column gives a reference to the test case number(s) detailed in the presen... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 3.4.3 Status and Notations | The "Rel-x Terminal" columns show the status of the entries as follows: The following notations, defined in ISO/IEC 9646-7 [i.2], 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 i... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4 Test environment | |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.1 Table of optional features | The supplier of the implementation 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 EEM class O O_EEM 2 Mass Storage class O O_MSC 3 ICCD Bulk Interface O O_ICCD_BULK ETSI ETSI TS 102 922-2 V7.1.0 (2025-10) 14 ... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 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). Table 4.2 a): Applicability of tests Test case Description Release Rel-7 Terminal Support Physical Tests 6.2.1 Dimensions of the UICC card Rel-7 M 6.2.2 Mechanical characteristics Rel-7 M ... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.3 Information provided by the device supplier | The device supplier shall provide the list of configurations used by the device (i.e. configuration index and configuration value 'bConfigurationValue' and its description for each configuration). EXAMPLE: Index 0, 'bConfigurationValue'=1, EEM and Mass Storage supported. |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.4 Test equipment | |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.4.0 Introduction | The test equipment shall provide a Terminal simulator which is connected to the DUT during test procedure execution, unless otherwise specified. With respect to the UICC, the Terminal simulator shall act as a valid Terminal according to ETSI TS 102 600 [1] and ETSI TS 102 221 [2], unless otherwise specified. In particu... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.4.1 Measurement/setting uncertainties | Void. ETSI ETSI TS 102 922-2 V7.1.0 (2025-10) 16 Release 7 |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.4.2 Default conditions for DUT operation | |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.4.2.1 Temperature | The tests shall be run at a fully operational temperature (i.e. between -25 °C and +85 °C). |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.4.3 Minimum/maximum conditions for DUT operation | Void. |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.5 Test execution | |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.5.1 Parameter variations | Unless otherwise specified, all tests shall be carried out once for each voltage class available in the UICC in addition to the parameter variations specified individually for each test case. |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 4.6 Pass criterion | 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. |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 5 Conformance Requirements | |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 5.1 USB UICC system architecture | Reference: ETSI TS 102 600 [1], clause 4. RQ number Clause Description RQ01_0101 4.1 USB UICCs shall remain compliant with ETSI TS 102 221 [2]. RQ01_0201 4.2 The ETSI TS 102 221 [2] interface shall be activated when a terminal with only ETSI TS 102 221 [2] capability is connected to a USB UICC. RQ01_0202 4.2 The ETSI T... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 5.2 Physical characteristics | Reference: ETSI TS 102 600 [1], clause 5. ETSI ETSI TS 102 922-2 V7.1.0 (2025-10) 17 Release 7 RQ number Clause Description RQ02_0001 5 The physical characteristics of the USB UICC-Terminal interface are as defined in ETSI TS 102 221 [2] except for the specific provisions specified in the present document. RQ02_0101 5.... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 5.3 Electrical characteristics | Reference: ETSI TS 102 600 [1], clause 6. RQ number Clause Description RQ03_0101 6.1 The operating conditions defined in ETSI TS 102 221 [2] apply to USB UICCs, except when otherwise specified in the present document. RQ03_0102 6.1 The contacts C4 and C8 operate as specified in Inter-Chip USB [5] for IC_DP and IC_DM re... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 5.4 Initial communication establishment procedures | Reference: ETSI TS 102 600 [1], clause 7. RQ number Clause Description RQ04_0101 7.1 USB UICCs shall support voltage class B and C/C' operating conditions. RQ04_0102 7.1 Any voltage class defined in the present document which is supported by the USB UICC shall be supported on both the IC_USB interface and the ETSI TS 1... |
cc725a86775f5379efd6316472d76bc0 | 102 922-2 | 5.5 USB interface operational features | Reference: ETSI TS 102 600 [1], clause 8. RQ number clause description RQ05_0101 8.1 USB Full Speed, as defined in USB 2.0 [4], shall be supported on the USB UICC. RQ05_0201 8.2 A USB UICC shall support the Get Interface Power request as defined in ETSI TS 102 600 [1], tables 8.1 and 8.2. RQ05_0202 8.2 A USB UICC shall... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.