7.9G Spurious emissions for V2X Communication
36.521-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Part 1: Conformance testingRadio transmission and receptionRelease 17TSUser Equipment (UE) conformance specification
7.9G.1 Spurious emissions for V2X Communication / Non-concurrent with E-UTRA uplink transmissions
7.9G.1.1 Test Purpose
The spurious emissions power is the power of emissions generated or amplified in a receiver that appear at the UE antenna connector.
7.9G.1.2 Test Applicability
This test applies to all types of UE that support V2X Sidelink Communication and Band 47.
7.9G.1.3 Minimum Conformance Requirements
The power of any narrow band CW spurious emission shall not exceed the maximum level specified in Table 7.9G.1.3-1.
Table 7.9G.1.3-1: General receiver spurious emission requirements
Frequency band |
Measurement bandwidth |
Maximum level |
NOTE |
30MHz ≤ f < 1GHz |
100 kHz |
-57 dBm |
|
1GHz ≤ f ≤ 12.75 GHz |
1 MHz |
-47 dBm |
|
12.75 GHz ≤ f ≤ 5th harmonic of the upper frequency edge of the DL operating band in GHz |
1 MHz |
-47 dBm |
1 |
12.75 GHz – 26GHz |
1 MHz |
-47dBm |
3 |
NOTE 1: Applies only for Band 22, Band 42, Band 43 and Band 48 NOTE 2: Unused PDCCH resources are padded with resource element groups with power level given by PDCCH_RA/RB as defined in Annex C.3.1. NOTE 3: Applies for Band 47 |
In addition, for a V2X UE operating in Region 1, the power of any spurious emission shall not exceed the levels specified in Table 7.9G.1.3-2.
Table 7.9G.1.3-2: Additional RX spurious emissions limits in Region 1
Frequency Range |
Maximum Level |
Measurement bandwidth |
NOTE |
5795 MHz ≤ f < 5815MHz |
[-65 dBm] |
1 MHz |
|
NOTE: The additional Rx spurious emission limits, however, are specified in EIRP in Region 1. Furthermore, the requirement varies based on antenna installation. It is FFS how to convert this to conducted requirements. |
The normative reference for this requirement is TS 36.101 [2] clause 7.9.
7.9G.1.4 Test Description
7.9G.1.4.1 Initial Conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
The initial test configurations consist of environmental conditions, test frequencies, and channel bandwidths based on E-UTRA operating bands specified in table 5.4.2G.1-1. All of these configurations shall be tested with applicable test parameters for each channel bandwidth, and are shown in table 7.9G.1.4.1-1. The details of the V2X reference measurement channels (RMCs) are specified in Annex A.8.3 and the GNSS configuration in TS 36.508 [7] subclause 4.11.
Table 7.9G.1.4.1-1: Test Configuration Table
Initial Conditions |
|||
Test Environment as specified in TS 36.508[7] subclause 4.1 |
NC |
||
Test Frequencies as specified in TS 36.508 [7] subclause 4.3.1 |
Mid range |
||
Test Channel Bandwidths as specified in TS 36.508 [7] subclause 4.3.1 |
Lowest, Highest |
||
Test Parameters for Channel Bandwidths |
|||
V2X Configuration to Receive |
|||
Ch BW |
Modulation |
PSSCH RB allocation |
|
10MHz |
QPSK |
0 |
|
20MHz |
QPSK |
0 |
1. Connect the SS to the UE antenna connectors and connect the GNSS simulator to the UE GNSS RX antenna connector as shown in TS 36.508 [7] Annex A, Figure A.89.
2. The parameter settings for the V2X sidelink transmission over PC5 are pre-configured according to TS 36.508 [7] subclause 6.8.2. Message content exceptions are defined in clause 7.9G.1.4.3.
3. The V2X reference measurement channel is set according to Table 7.9G.1.4.1-1.
3a. The GNSS simulator is configured for Scenario #1: static in Geographical area #1, as defined in TS36.508 [7] Table 4.11.2-2. Geographical area #1 is also pre-configured in the UE.
4. Propagation conditions are set according to Annex B.0.
5. Ensure the UE is in State 5A-V2X in Receive Mode according to TS 36.508 [7] clause 4.5.9.
6. Trigger the UE to reset UTC time. (NOTE: The UTC time reset may be performed by MMI or AT command (+CUTCR).)
7. The GNSS simulator is triggered to start step 1 of Scenario #1 to simulate a location in the centre of Geographical area #1. Wait for the UE to acquire the GNSS signal and start to transmit.
7.9G.1.4.2 Test Procedure
1. Sweep the spectrum analyzer (or equivalent equipment) over a frequency range and measure the average power of spurious emission. During measurement the resolution bandwidth is 1% of the measurement bandwidth, and the result should be integrated to achieve the measurement bandwidth. The sweep time shall be set larger than (symbol length)*(number of points in sweep) to improve the measurement accuracy. During measurement the spectrum analyser shall be set to ‘Detector’ = RMS, ‘Trace mode’ = average.
2. Repeat step 1 for all E-UTRA Rx antennas of the UE.
7.9G.1.4.3 Message Contents
Message contents are according to TS 36.508 [7] subclause 4.6.
7.9G.1.5 Test Requirement
The measured spurious emissions derived in step 1), shall not exceed the maximum level specified in Table 7.9G.1.5-1.
Table 7.9G.1.5-1: General receiver spurious emission requirements
Frequency band |
Measurement bandwidth |
Maximum level |
NOTE |
30MHz ≤ f < 1GHz |
100 kHz |
-57 dBm |
|
1GHz ≤ f ≤ 12.75 GHz |
1 MHz |
-47 dBm |
|
12.75 GHz ≤ f ≤ 5th harmonic of the upper frequency edge of the DL operating band in GHz |
1 MHz |
-47 dBm |
1 |
12.75 GHz – 26GHz |
1 MHz |
-47dBm |
3 |
NOTE 1: Applies only for Band 22, Band 42, Band 43 and Band 48 NOTE 2: Unused PDCCH resources are padded with resource element groups with power level given by PDCCH_RA/RB as defined in Annex C.3.1. NOTE 3: Applies for Band 47 |
In addition, for a V2X UE operating in Region 1, the measured spurious emissions derived in step 1) shall not exceed the levels specified in Table 7.9G.1.5-2.
Table 7.9G.1.5-2: Additional RX spurious emissions limits in Region 1
Frequency Range |
Maximum Level |
Measurement bandwidth |
NOTE |
5795 MHz ≤ f < 5815MHz |
[-65 dBm] |
1 MHz |
|
NOTE: The additional Rx spurious emission limits, however, are specified in EIRP in Region 1. Furthermore, the requirement varies based on antenna installation. It is FFS how to convert this to conducted requirements. |