4 General

36.521-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Part 1: Conformance testingRadio transmission and receptionRelease 17TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

Unless otherwise stated, the following reference conditions used by all test cases in this document are specified in TS 36.508 [7]:

– Connection Diagrams,

– Test Frequencies,

– Cell Settings,

– Reference Environments,

– Environmental Conditions,

– Generic Connection Setup Procedures,

– System Information (SI),

– Message Contents.

Where a test requires one of the above reference conditions that are different, this will be specified within the test itself.

The Minimum Requirements defined in each test make no allowance for Measurement Uncertainty. Therefore, Test Tolerances are used to relax the Minimum Requirements. If the Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for that test is non-zero. For each test the Test Tolerances are individually calculated to create the Test Requirements. The Test Tolerance for each test and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in Annex F.3.

Downlink and Uplink transmissions are organized into radio frames with duration. Two radio frame structures are supported in this document:

– Type 1, applicable to FDD,

– Type 2, applicable to TDD.

In clauses 6 and 7 TX and RX test cases for FDD/TDD test cases are defined. FDD and TDD test scenarios/ requirements are included within the same test case. For test cases with any difference between the FDD and TDD branches the test description part of the test case has been separated in two sections to cover the two technologies. The applicability for the FDD and TDD branches are specified in TS 36.521-2. For some test cases requiring a complex test coverage analysis, TR 36.905 [19] is used for this purpose.

In clause 8 the performance requirement test cases are defined. FDD and TDD performance requirement test cases are defined in different clauses accordingly to the requirements specified in TS 36.101.

Unless otherwise stated, each test case is tested for every operating band supported by the UE and repeated with the applicable test configurations (i.e. test environment, test frequencies, test channel bandwidths, channel bandwidth parameters) indicated in each test case. For test cases in clauses 6, 7, 8 the initial conditions of the downlink physical channels signal levels and downlink physical channels required are specified in Annex C.0, Annex C.1 and Annex C.2.

For test cases in clauses 6 and 7 that require measurements with maximum output power, the UE shall transmit at its maximum output power state with output power level of P_UMAX level. This range of maximum output power shall not be modified for any further additional relaxation.

For UL-MIMO cases, the UE output power is the sum of mean powers as measured at each antenna connector unless otherwise stated.

For test cases in clauses 6 and 7, the partial RB allocations refer to any RB allocation less than full RB allocation except 1 RB allocation.

4.1 Categorization of test requirements in CA, UL-MIMO, ProSe, Dual Connectivity, UE category 0, UE category M1, UE category M2, UE category 1bis, UE category NB1, UE category NB2, V2X Communication

The test requirements for Clauses 6 (Tx Characteristics) and 7 (Rx Characteristics), which are specific to CA, UL-MIMO, ProSe, Dual Connectivity, UE category 0, UE category M1, UE category, UE category 1bis, UE category NB1, UE category NB2, V2X Communication are specified as suffix A, B, C, D, E , F and G where;

a) Suffix A additional requirements need to support CA

b) Suffix B additional requirements need to support UL-MIMO

c) Suffix C additional requirements need to support Dual Connectivity

d) Suffix D additional requirements need to support ProSe

e) Suffix E additional requirements need to support UE category 0, category M1, category M2, and category 1bis

f) Suffix F additional requirements need to support UE category NB1, UE category NB2

g) Suffix G additional requirements need to support V2X Communication

A terminal which supports the above features needs to meet both the general requirements and the additional requirement applicable to the additional sub-clause (suffix A, B, C, D, E, F and G).

Where there is a difference in requirement between the general requirements and the additional subclause requirements (suffix A, B, C, D, E, F and G) in clauses 5, 6 and 7, the tighter requirements are applicable unless stated otherwise in the additional subclause.

A terminal which supports more than one feature (CA, UL-MIMO, ProSe, Dual Connectivity, UE category 0, UE category M1, UE category M2, UE category 1bis, UE category NB1, UE category NB2 and V2X Communication) in clauses 5, 6 and 7 shall meet all of the separate corresponding requirements.

For a terminal supporting CA, compliance with minimum requirements for non-contiguous intra-band carrier aggregation in any given operating band does not imply compliance with minimum requirements for contiguous intra-band carrier aggregation in the same operating band.

For a terminal supporting CA, compliance with minimum requirements for contiguous intra-band carrier aggregation in any given operating band does not imply compliance with minimum requirements for non- contiguous intra-band carrier aggregation in the same operating band.

A terminal which supports a DL CA configuration shall support all the lower order fallback DL CA combinations and it shall support at least one bandwidth combination set for each of the constituent lower order DL combinations containing all the bandwidths specified within each specific combination set of the upper order DL combination.

A terminal which supports CA, for each supported CA configuration, shall support Pcell transmissions in each of the aggregated Component Carriers unless indicated otherwise in clause 5.4.2A.1.

Terminal supporting Dual Connectivity configuration shall meet the minimum requirements for corresponding CA configuration (suffix A), unless otherwise specified.

NOTE 1: Test Case 6.5.2.1A, PUSCH-EVM with exclusion period, is a Release 8 non-CA test case and does not indicate a requirement to support CA.

NOTE 2: This categorization of test requirements reflects only the categorization of minimum requirements as done by RAN4 in 3GPP TS 36.101. For the categorization of the tests requirements done on behalf of RAN5 follow the information given in Annex I.

For a terminal that supports ProSe Direct Communication and/or ProSe Direct Discovery, the minimum requirements are applicable when

– the UE is associated with a serving cell on the ProSe carrier, or

– the UE is not associated with a serving cell on the ProSe carrier and is provisioned with the preconfigured radio parameters for ProSe Direct Communications and/or ProSe Direct Discovery that are associated with known Geographical Area, or

– the UE is associated with a serving cell on a carrier different than the ProSe carrier, and the radio parameters for ProSe Direct Discovery on the ProSe carrier are provided by the serving cell, or

– the UE is associated with a serving cell on a carrier different than the ProSe carrier, and has a non-serving cell selected on the ProSe carrier that supports ProSe Direct Discovery and/or ProSe Direct Communication.

When the ProSe UE is not associated with a serving cell on the ProSe carrier, and the UE does not have knowledge of its geographical area, or is provisioned with preconfigured radio parameters that are not associated with any Geographical Area, ProSe transmissions are not allowed, and the requirements in Section 6.3.3D apply.

A terminal that supports simultaneous E-UTRA ProSe sidelink transmissions and E-UTRA uplink transmissions for the inter-band E-UTRA ProSe/E-UTRA bands specified in Table 5.2D-2, shall meet the minimum requirements for the corresponding inter-band UL CA configuration (suffix A), unless otherwise specified. For transmitter characteristics specified in clause 6, the terminal is required to meet the conformance tests for the corresponding inter-band UL CA configuration and is not required to be retested with simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions.

A terminal that supports E-UTRA V2X intra-band multi-carrier operation for the band specified in Table 5.5G-3, shall meet the corresponding transmitter characteristics requirements (in subclauses with suffix G in Section 6) only when there are multiple active transmissions on all of the configured carrier components. When there is only one active transmission on one of the configured carrier components, the corresponding requirements for V2X single carrier operation apply for the corresponding active carrier component.

4.2 RF requirements in later releases

The standardisation of new frequency bands may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band of operation that is specified in a later release, it is necessary to specify some extra requirements. TS 36.307 [16] specifies requirements on UEs supporting a frequency band that is independent of release.

NOTE: For UEs conforming to the 3GPP release of the present document, some RF requirements of later releases may be mandatory independent of whether the UE supports the bands specified in later releases or not. The set of RF requirements of later releases that is also mandatory for UEs conforming to the 3GPP release of the present document is determined by regional regulation.