4 General test conditions
37.571-13GPPPart 1: Conformance test specificationRelease 16TSUser Equipment (UE) conformance specification for UE positioning
4.1 Introduction
This clause defines the various common test conditions required for the various measurement requirements in the remainder of the document.
4.2 GNSS test conditions
4.2.0 General
In this clause the terms GNSS and A-GNSS also include the cases where the only satellite system used is GPS unless otherwise stated.
4.2.1 GNSS signals
The GNSS signal is defined at the A-GNSS antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
4.2.2 GNSS frequency
The GNSS signals shall be transmitted with a frequency accuracy of ± 0.025 PPM.
4.2.3 GNSS static propagation conditions
The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model.
4.2.4 GNSS multi-path conditions
Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GNSS signals are defined in table 4.2.1.
Table 4.2.1: Multi-path Conditions for GNSS Signals
Initial relative Delay |
Carrier Doppler frequency of tap [Hz] |
Code Doppler frequency of tap [Hz] |
Relative mean Power [dB] |
0 |
Fd |
Fd / N |
0 |
X |
Fd – 0.1 |
(Fd-0.1) /N |
Y |
NOTE: Discrete Doppler frequency is used for each tap. |
Where the X and Y depends on the GNSS signal type and is shown in Table 4.2.2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in Table 4.2.3 (where k in Table 4.2.3 is the GLONASS frequency channel number).
Table 4.2.2: Values of X and Y for GNSS Signals
System |
Signals |
X [m] |
Y [dB] |
Galileo |
E1 |
125 |
-4.5 |
E5a |
15 |
-6 |
|
E5b |
15 |
-6 |
|
GPS/Modernized GPS |
L1 C/A |
0.5 chip / 150m |
-6 |
L1C |
125 |
-4.5 |
|
L2C |
150 |
-6 |
|
L5 |
15 |
-6 |
|
GLONASS |
G1 |
275 |
-12.5 |
G2 |
275 |
-12.5 |
|
BDS |
B1I |
75 |
-4.5 |
B1C |
75 |
-4.5 |
Table 4.2.3: Values of N for GNSS Signals
System |
Signals |
N |
Galileo |
E1 |
1540 |
E5a |
115 |
|
E5b |
118 |
|
GPS/Modernized GPS |
L1 C/A |
1540 |
L1C |
1540 |
|
L2C |
1200 |
|
L5 |
115 |
|
GLONASS |
G1 |
3135.03 + k ⋅ 1.10 |
G2 |
2438.36 + k ⋅ 0.86 |
|
BDS |
B1I |
763 |
B1C |
770 |
The initial carrier phase difference between taps shall be randomly selected between 0 and 2radians. The initial value shall have uniform random distribution.
4.2.5 UEs supporting multiple satellite signals
For UEs supporting multiple satellite signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the UE. Signals not supported by the UE do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 4.2.4. The individual test scenarios in clauses 6, 7 and 13 define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario in clauses 6, 7 and 13 plus the relative power level defined in Table 4.2.4.
Table 4.2.4: Relative signal power levels for each signal type for each GNSS
Galileo |
GPS/Modernized GPS |
GLONASS |
QZSS |
SBAS |
BDS |
||||||||
Signal power levels relative to reference power levels |
E1 |
0 dB |
L1 C/A |
0 dB |
G1 |
0 dB |
L1 C/A |
0 dB |
L1 |
0 dB |
B1I |
D1 |
0 dB |
D2 |
+5 dB |
||||||||||||
E6 |
+2 dB |
L1C |
+1.5 dB |
G2 |
-6 dB |
L1C |
+1.5 dB |
B1C |
D1 |
0 dB |
|||
E5 |
+2 dB |
L2C |
-1.5 dB |
L2C |
-1.5 dB |
||||||||
L5 |
+3.6 dB |
L5 |
+3.6 dB |
NOTE 1: For test cases which involve “Modernized GPS”, the satellite simulator shall also generate the GPS L1 C/A signal if the UE supports “GPS” in addition to “Modernized GPS”.
NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately.
NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites for B1I and B1C signal types and D2 represents GEO satellites for B1I signal type.
4.2.6 GNSS multi System Time Offsets
If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than 3 ns.
4.3 UTRA test conditions
4.3.1 UTRA frequency band and frequency range
The UTRA tests in clauses 5 and 6 in the present document are performed at mid range of the UTRA operating frequency band of the UE. The UARFCNs to be used for mid range are defined in 3GPP TS 34.108 [28], clause 5.1.1.
If the UE supports multiple UTRA frequency bands then the Sensitivity tests in clauses 5.2 and 6.2 shall be repeated in each supported UTRA frequency band.
4.3.2 UTRA frequency
For the UTRA tests in clause 5 the UTRA frequency shall be offset with respect to the nominal frequency by an amount equal to the sum of +0.025 PPM and the offset in PPM of the actual transmitted GPS carrier frequency with respect to the nominal GPS frequency.
4.3.3 Sensors
The UTRA tests in clause 6 shall be met without the use of any data coming from sensors that can aid the positioning. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 34.109 [29] for the purpose of disabling any such sensors.
4.4 E-UTRA test conditions
4.4.1 E-UTRA frequency band and frequency range
The E-UTRA A-GNSS tests in clause 7, MBS tests in clause 11, WLAN and BLE tests in clause 12 are performed on the mid range EARFCN of the E-UTRA operating frequency band of the UE and the channel bandwidth as defined in TS 36.508 [18] clause 4.3.1.
If the UE supports multiple E-UTRA frequency bands then the A-GNSS Sensitivity tests in clause 7.1 shall be repeated in each supported E-UTRA frequency band.
The E-UTRA ECID tests in clause 8 and the OTDOA tests in clauses 9 and 10 are performed on the EARFCN(s) of the E-UTRA operating frequency band of the UE and the channel bandwidth(s) specified in the test cases and as defined in TS 36.508 [18] clause 4.3.1 and 4.4.2.
4.4.2 Groups of bands
The E-UTRA tests use the band groupings defined in TS 36.521-3 [25] clause 3.5.1 in order to increase the readability of the specification.
Table 4.4.2-1: Void
Table 4.4.2-2: Void
Table 4.4.2-3: Void
4.4.3 Sensors
All the minimum performance requirements in clause 7 shall be met without the use of any data coming from sensors that can aid the positioning. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 36.509 [11] for the purpose of disabling any such sensors.
4.4A LPP transport mechanism for E-UTRA
The E-UTRA A-GNSS minimum performance requirements tested in this specification are agnostic as to whether the LPP session is performed over the Control Plane or the User Plane. Thus, the E-UTRA A-GNSS test cases in clause 7 support both configurations. The user can select either of the two options to run the test.
4.5 A-GNSS test conditions
4.5.1 General
Clauses 5, 6, 7 and 13 define the minimum performance requirements for both UE based and UE assisted A‑GNSS UEs. If a UE supports both modes then it shall be tested in both modes.
4.5.2 UTRAN measurement parameters
4.5.2.1 UE based A-GNSS measurement parameters
In case of UE-based A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING POSITION ESTIMATE INFO IE. The measurement parameter is the horizontal position estimate reported by the UE and expressed in latitude/longitude.
4.5.2.2 UE assisted A-GNSS measurement parameters
In case of UE-assisted A-GNSS, the measurement parameters are contained in the RRC UE POSITIONING GANSS MEASURED RESULTS IE and/or the RRC UE POSITIONING GPS MEASURED RESULTS IE. The measurement parameters are the UE GANSS Code Phase measurements and/or the UE GPS Code Phase measurements, as specified in 3GPP TS 25.302 [32] and 3GPP TS 25.215 [33]. The UE GANSS Code Phase measurements and/or the UE GPS Code Phase measurements are converted into a horizontal position estimate using the procedure detailed in Annex B.
4.5.2.3 2D position error
The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the UE Measurement Report and the actual simulated position of the UE in the test case considered.
4.5.2.4 Response time
Max Response Time is defined as the time starting from the moment that the UE has received the final RRC measurement control message containing reporting criteria different from "No Reporting" sent before the UE sends the measurement report containing the position estimate or the GANSS and/or GPS measured result, and ending when the UE starts sending the measurement report containing the position estimate or the GANSS and/or GPS measured result on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re‑use any information on GNSS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ specified in 3GPP TS 34.109 [29], clause 5.4, has been defined for the purpose of deleting this information.
4.5.3 E-UTRAN and NR measurement parameters
4.5.3.1 UE based A-GNSS measurement parameters
In case of UE-based A-GNSS, the measurement parameters are contained in the LPP GNSS‑LocationInformation IE which is included in the A‑GNSS‑ProvideLocationInformation IE provided in the LPP message of type PROVIDE LOCATION INFORMATION. The measurement parameter in case of UE-based A-GNSS is the horizontal position estimate reported by the UE and expressed in latitude/longitude.
4.5.3.2 UE assisted A-GNSS measurement parameters
In case of UE-assisted A-GNSS, the measurement parameters are contained in the LPP GNSS‑SignalMeasurementInformation IE which is included in the A‑GNSS‑ProvideLocationInformation IE provided in the LPP message of type PROVIDE LOCATION INFORMATION. The measurement parameters in case of UE-assisted A-GNSS are the UE GNSS code phase measurements, as specified in TS 36.302 [5] and TS 36.214 [6]. The UE GNSS code phase measurements are converted into a horizontal position estimate using the procedure detailed in Annex B.
4.5.3.3 2D Error definition
The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the LPP message of type PROVIDE LOCATION INFORMATION and the actual position of the UE in the test case considered.
4.5.3.4 Response time
Max Response Time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. The response times specified for all test cases are Time-to-First-Fix (TTFF) unless otherwise stated, i.e. the UE shall not re‑use any information on GNSS time, location or other aiding data that was previously acquired or calculated and stored internally in the UE. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 36.509 [11] clause 6.9 and in TS 38.509 [44] clause 6.3.5 for the purpose of deleting this information.
4.5.4 Converting A-GNSS UE-assisted measurement reports into position estimates
To convert the A-GNSS UE measurement reports in case of UE-assisted mode of A-GNSS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in Annex B.
4.6 ECID test conditions
4.6.1 Simulated cells
For the ECID performance test cases in clause 8.1, a cell environment as defined in 3GPP TS 36.508 [18] with Cell 1 is used. The default parameters for simulated cells are the same as specified in 3GPP TS 36.508 [18].
4.6.2 Propagation conditions
4.6.2.1 Static
See TS 36.521-1 [24] clause B.1.
4.6.2.2 Multi-path fading
See TS 36.521-1[24] clauses B.2, B.2.1 and B.2.2.
4.6.3 UE Rx – Tx time difference reporting range
The reporting range of FDD UE Rx – Tx time difference is defined from 0 to 20472Ts with 2Ts resolution for UE Rx – Tx time difference less than 4096Ts and 8Ts for UE Rx – Tx time difference equal to or greater than 4096Ts.
The mapping of measured quantity for FDD is defined in Table 4.6.3-1.
Table 4.6.3-1: FDD UE Rx – Tx time difference measurement report mapping
Reported value |
Measured quantity value |
Unit |
RX-TX_TIME_DIFFERENCE_FDD _0000 |
TUE Rx-Tx < 2 |
Ts |
RX-TX_TIME_DIFFERENCE_FDD _0001 |
2 ≤ TUE Rx-Tx < 4 |
Ts |
RX-TX_TIME_DIFFERENCE_FDD _0002 |
4 ≤ TUE Rx-Tx < 6 |
Ts |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_FDD _2046 |
4092 ≤ TUE Rx-Tx < 4094 |
Ts |
RX-TX_TIME_DIFFERENCE_FDD _2047 |
4094 ≤ TUE Rx-Tx < 4096 |
Ts |
RX-TX_TIME_DIFFERENCE_FDD _2048 |
4096 ≤ TUE Rx-Tx < 4104 |
Ts |
RX-TX_TIME_DIFFERENCE_FDD _2049 |
4104 ≤ TUE Rx-Tx < 4112 |
Ts |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_FDD _4093 |
20456 ≤ TUE Rx-Tx < 20464 |
Ts |
RX-TX_TIME_DIFFERENCE_FDD _4094 |
20464 ≤ TUE Rx-Tx < 20472 |
Ts |
RX-TX_TIME_DIFFERENCE_FDD _4095 |
20472 ≤ TUE Rx-Tx |
Ts |
The reporting range of TDD UE Rx – Tx time difference is defined from 624 to 21096Ts with 2Ts resolution for UE Rx – Tx time difference less than 4720Ts and 8Ts for UE Rx – Tx time difference equal to or greater than 4720Ts.
The mapping of measured quantity for TDD is defined in Table 4.6.3-2.
Table 4.6.3-2: TDD UE Rx – Tx time difference measurement report mapping
Reported value |
Measured quantity value |
Unit |
RX-TX_TIME_DIFFERENCE_TDD_0000 |
TUE Rx-Tx < 626 |
Ts |
RX-TX_TIME_DIFFERENCE_TDD_0001 |
626 ≤ TUE Rx-Tx < 628 |
Ts |
RX-TX_TIME_DIFFERENCE_TDD_0002 |
628 ≤ TUE Rx-Tx < 630 |
Ts |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_TDD_2046 |
4716 ≤ TUE Rx-Tx < 4718 |
Ts |
RX-TX_TIME_DIFFERENCE_TDD_2047 |
4718 ≤ TUE Rx-Tx < 4720 |
Ts |
RX-TX_TIME_DIFFERENCE_TDD_2048 |
4720 ≤ TUE Rx-Tx < 4728 |
Ts |
RX-TX_TIME_DIFFERENCE_TDD_2049 |
4728 ≤ TUE Rx-Tx < 4736 |
Ts |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_TDD_4093 |
21080 ≤ TUE Rx-Tx < 21088 |
Ts |
RX-TX_TIME_DIFFERENCE_TDD_4094 |
21088 ≤ TUE Rx-Tx < 21096 |
Ts |
RX-TX_TIME_DIFFERENCE_TDD_4095 |
21096 ≤ TUE Rx-Tx |
Ts |
4.7 OTDOA test conditions
4.7.1 Simulated cells
For the intra-frequency OTDOA measurement test cases in clause 9.1, a multi cell environment as defined in 3GPP TS 36.508 [18] with Cell 1, Cell 2, and Cell 4 (if needed in the test) is used.
For the inter-frequency OTDOA measurement test cases in clause 9.2, a multi cell environment as defined in 3GPP TS 36.508 [18] with Cell 1 (called Cell 1 in the tests), Cell 3 (called Cell 2 in the tests), and Cell 6 (called Cell 3 in the tests) (if needed in the test) is used.
For the intra-frequency OTDOA measurement test cases for UE Category M1/M2 in clause 9.3, a multi cell environment as defined in 3GPP TS 36.508 [18] with Cell 1, Cell 2, and Cell 4 (if needed in the test) is used.
For the inter-frequency OTDOA measurement test cases for UE Category M1/M2 in clause 9.4, a multi cell environment as defined in 3GPP TS 36.508 [18] with Cell 1 (called Cell 1 in the tests), Cell 3 (called Cell 2 in the tests), and Cell 6 (called Cell 3 in the tests) (if needed in the test) is used.
For the intra-frequency NB-IOT OTDOA measurement accuracy test cases in clause 9.5, a multi cell environment with LTE Cell 1 and Cell 1a (see 3GPP TS 36.508 [18] Clause 4.4.2) and NB-IOT Ncell 1 and Ncell 1a (see 3GPP TS 36.508 [18] Clause 8.1.4.2) is used.
For the intra-frequency NB-IOT OTDOA measurement reporting delay test cases in clause 9.5, a multi cell environment with NB-IOT Ncell 1, Ncell 1a and Ncell 2 (see 3GPP TS 36.508 [18] Clause 8.1.4.2) is used.
For the inter-frequency NB-IOT OTDOA measurement accuracy test cases in clause 9.6, a multi cell environment with LTE Cell 1 and Cell 1a (see 3GPP TS 36.508 [18] Clause 4.4.2) and NB-IOT Ncell 1 and Ncell 1a (see 3GPP TS 36.508 [18] Clause 8.1.4.2) is used.
For the inter-frequency NB-IOT OTDOA measurement reporting delay test cases in clause 9.9, a multi cell environment with NB-IOT Ncell 1, Ncell 1a and Ncell 2 (see 3GPP TS 36.508 [18] Clause 8.1.4.2) is used.
For the OTDOA measurement test cases for Carrier Aggregation in clause 10, a multi cell environment is used with Cell 1 as the PCell on the PCC, Cell 2 is an active SCell on the SCC, and Cell 3 is a neighbour cell on the SCC. For the OTDOA measurement test cases for 3 DL Carrier Aggregation in clause 10, a multi cell environment is used with Cell 1 as the PCell on the PCC, Cell 2 is an active SCell on SCC1, Cell 3 is an active SCell on SCC2and Cell 4 is a neighbour cell on SCC2.
The default parameters for simulated cells are the same as specified in 3GPP TS 36.508 [18], with the following exceptions:
– All cells transmit PRS according to the PRS configuration provided in the OTDOA assistance data defined for each test. The positioning subframes are low-interference subframes, i.e. contain no PDSCH transmissions.
– The physical layer cell identities are selected such that the relative shifts of PRS patterns among cells used in the tests are as given by the test parameters of the individual test cases.
– The cells shall be synchronized and the timing offset (the RSTD) between the cells referenced to the UE’s antenna input is given in the individual test cases.
4.7.2 Propagation conditions
4.7.2.1 Static
See TS 36.521-1 [24] clause B.1.
4.7.2.2 Multi-path fading
See TS 36.521-1[24] clauses B.2, B.2.1 and B.2.2.
4.7.3 Response time
The response time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. The response time specified for the Measurement Reporting Delay test cases assumes that the UE shall not reuse any RSTD information or other aiding data that was previously acquired and stored internally in the UE. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 36.509 [11] clause 6.9 and in TS 38.509 [44] clause 6.3.5 for the purpose of deleting this information.
4.7.4 RSTD reporting range
The reporting range of RSTD is defined from -15391Ts to 15391Ts with 1Ts resolution for absolute value of RSTD less or equal to 4096Ts and 5Ts for absolute value of RSTD greater than 4096Ts.
The mapping of measured quantity is defined in Table 4.7.4-1.
Table 4.7.4-1: RSTD report mapping
Reported Value |
Measured Quantity Value |
Unit |
RSTD_0000 |
-15391 > RSTD |
Ts |
RSTD_0001 |
-15391 ≤ RSTD < -15386 |
Ts |
… |
… |
… |
RSTD_2258 |
-4106 ≤ RSTD < -4101 |
Ts |
RSTD_2259 |
-4101 ≤ RSTD < -4096 |
Ts |
RSTD_2260 |
-4096 ≤ RSTD < -4095 |
Ts |
RSTD_2261 |
-4095 ≤ RSTD < -4094 |
Ts |
… |
… |
… |
RSTD_6353 |
-3 ≤ RSTD < -2 |
Ts |
RSTD_6354 |
-2 ≤ RSTD < -1 |
Ts |
RSTD_6355 |
-1 ≤ RSTD ≤ 0 |
Ts |
RSTD_6356 |
0 < RSTD ≤ 1 |
Ts |
RSTD_6357 |
1 < RSTD ≤ 2 |
Ts |
RSTD_6358 |
2 < RSTD ≤ 3 |
Ts |
… |
… |
… |
RSTD_10450 |
4094 < RSTD ≤ 4095 |
Ts |
RSTD_10451 |
4095 < RSTD ≤ 4096 |
Ts |
RSTD_10452 |
4096 < RSTD ≤ 4101 |
Ts |
RSTD_10453 |
4101 < RSTD ≤ 4106 |
Ts |
… |
… |
… |
RSTD_12709 |
15381 < RSTD ≤ 15386 |
Ts |
RSTD_12710 |
15386 < RSTD ≤ 15391 |
Ts |
RSTD_12711 |
15391 < RSTD |
Ts |
4.7.5 RSTD Carrier Aggregation Test Cases with Different Channel Bandwidth Combinations
RSTD carrier aggregation test cases may be defined with different channel bandwidth combinations to verify the same requirement.
If multiple carrier aggregation test cases with different channel bandwidth combinations are defined to verify the same requirement that is channel bandwidth independent, then the UE needs to be tested only with one bandwidth combination out of the bandwidth combination sets supported by that UE.
4.8 MBS test conditions
4.8.1 MBS signals
A single or multi MBS beacon environment, depending on the test, is used.
The MBS signal is defined at the antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
The beacons shall be synchronized, and the beacon code phase delays are defined in each test. The MBS signals shall be transmitted with a frequency accuracy of ± 2.5 PPM from the specified MBS carrier centre frequency.
4.8.2 Propagation conditions
4.8.2.1 Static
See TS 36.521-1 [24] clause B.1.
4.8.2.2 Multi-path fading
According to the Extended Pedestrian A model with a Maximum Doppler frequency of 5Hz (EPA 5Hz) in TS 36.521-1 [24] clauses B.2, B.2.1 and B.2.2.
4.8.3 Response time
The response time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. The response time specified for the Measurement Reporting Delay test case assumes that the UE shall not reuse any information that was previously acquired and stored internally in the UE. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 36.509 [11] clause 6.9 and in TS 38.509 [44] clause 6.3.5 for the purpose of deleting this information.
4.9 WLAN test conditions
4.9.1 Simulated WLAN Access Points
A multi‐WLAN AP environment is used.
The WLAN signal is defined at the antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
The beacon signals from multiple WLAN APs shall be available at the UE with a periodicity of at least 102.4 ms (Beacon Interval). In order to ensure that the UE is in passive scan mode, this interval can be reduced. Beacon signals from different APs shall be received at different time slots or in non-overlapping frequency channels. Non-overlapping frequency channels shall be at least 25 MHz apart in the WLAN 2.4 GHz band and at least 20 MHz apart in the WLAN 5 GHz band.
The WLAN Test Frequency IDs to be used during the tests are specified in the test cases and are as defined in TS 36.508 [18] clause 4.3.1.6.
4.9.2 Propagation conditions
4.9.2.1 Static
See TS 36.521-1 [24] clause B.1.
4.9.3 Response time
The response time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. The response time specified for the Measurement Reporting Delay test case assumes that the UE shall not reuse any information that was previously acquired and stored internally in the UE. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 36.509 [11] clause 6.9 and in TS 38.509 [44] clause 6.3.5 for the purpose of deleting this information.
4.9.4 Void
4.10 BLE test conditions
4.10.1 Simulated BLE
A multi‐BLE device environment is used.
The BLE signal is defined at the antenna connector of the UE. For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed.
The beacon signals from multiple BLE devices shall be available at the UE with a broadcast interval of 100 ms. Signals from different BLE devices shall be received at different time slots or in non-overlapping BLE advertising frequency channels. The BLE advertising channels are Channel 37 (2402 MHz), Channel 38 (2426 MHz) and Channel 39 (2480 MHz). The beacons shall be of type Non-Connectable Advertising beacons.
4.10.2 Propagation conditions
4.10.2.1 Static
See TS 36.521-1 [24] clause B.1.
4.10.3 Response time
The response time is defined as the time starting from the moment that the UE has received the LPP message of type REQUEST LOCATION INFORMATION, and ending when the UE starts sending the LPP message of type PROVIDE LOCATION INFORMATION on the Uu interface. The response time specified for the Measurement Reporting Delay test case assumes that the UE shall not reuse any information that was previously acquired and stored internally in the UE. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 36.509 [11] clause 6.9 and in TS 38.509 [44] clause 6.3.5 for the purpose of deleting this information.
4.11 NB-IOT test conditions
4.11.1 Groups of bands
The NB-IOT tests use the band groupings defined in TS 36.521-3 [25] clause 3.5.1 in order to increase the readability of the specification
Table 4.11.1-1: Void
4.11.2 NB-IOT inband mode
The E-UTRA donor cell shall use the settings defined in Clause 4.4.1 unless otherwise stated.
4.12 NR test conditions
4.12.1 NR terminology
The terminology used in this specification for NR architecture options is described below.
Table 4.12.1-1: NR terminology
Terminology |
Abbreviation |
NSA |
|
E-UTRA-NR Dual Connectivity |
EN-DC |
NR-E-UTRA Dual Connectivity |
NE-DC |
NG-RAN E-UTRA-NR Dual Connectivity |
NGEN-DC |
SA |
|
NG-RAN NR Radio Access |
NG-RAN NR |
NG-RAN E-UTRA Radio Access |
NG-RAN E-UTRA |
4.12.2 NR frequency band and frequency range
The A-GNSS tests in clause 13, MBS tests in clause 11, WLAN tests in clause 15 and BLE tests in clause 16 are, where relevant, performed on the NR test frequency and default channel bandwidth of the NR operating frequency band of the UE as defined in TS 38.508-1 [45] clause 4.3.1. .
The A-GNSS requirements and tests in clause 13 apply for NR UE in FR1 and FR2.
If connectivity is NR (see TS 38.508-1 [45] clause 4.5) and if the UE supports multiple NR frequency bands then the A-GNSS Sensitivity tests in clause 13.2 shall be repeated in each supported NR frequency band.
If connectivity is EN-DC (see TS 38.508-1 [45] clause 4.5) and if the UE supports multiple EN-DC configurations, then the A-GNSS Sensitivity tests in clause 13.2 shall be performed in one EN-DC band combination in each of the applicable frequency group combination as specified in clause 4.12.6.
The NR OTDOA tests in clause 14 are performed on the ARFCN(s) of the operating frequency band of the UE and the channel bandwidth(s) specified in the test cases and as defined in FFS.
4.12.3 Groups of bands
The NR tests use the band groupings defined in TS 38.533 [47] clause 3A.4 in order to increase the readability of the specification.
Table 4.12.3-1: Void
Table 4.12.3-2: Void
4.12.4 Sensors
All the minimum performance requirements in clause 13 shall be met without the use of any data coming from sensors that can aid the positioning. A dedicated test message ‘RESET UE POSITIONING STORED INFORMATION’ has been defined in TS 38.509 [44] clause 6.3.5 for the purpose of disabling any such sensors.
4.12.5 Default signal conditions for FR2
For NR FR2, the connection between the SS and the DUT shall be OTA.
For the RAT-Independent test cases defined in clause 13, the SS shall ensure that a stable OTA link between the SS and the DUT can be established and maintained throughout the test. This link shall be sufficient to provide stable LPP message transmissions between the SS and the DUT. The connection for the other technologies (i.e. non-NR) used for the tests in clause 13 (e.g. LTE, GNSS, WLAN …) shall be conducted.
For the RAT-Dependent test cases defined in clauses 14, 15 and 16, a calibrated NR FR2 signal is required. The requirements OTA test method are defined in clause 7.1.3 of TS 38.508-1 [45].
4.12.6 Frequency Bands for Testing
4.12.6.1 EN-DC band combination groups
For the A-GNSS sensitivity requirements in EN-DC operation mode with uplink assigned to E-UTRA and NR frequency bands, the A-GNSS Sensitivity tests in clause 13.2 shall be performed in one EN-DC band combination in each of the supported frequency group combination specified in TS 38.171 [43] Table B.1.13.1-1, where the frequency groups are defined in TS 38.171 [43] Table B.1.13.1-2.
4.12.6.2 Applicable EN-DC band combinations for performing A-GNSS Sensitivity Requirements
The A-GNSS Sensitivity tests in clause 13.2 when in EN-DC operation mode shall be performed in EN-DC band combinations that can generate second or third order intermodulation products falling into the following GNSS receiver bands for the particular GNSS (where supported by the UE):
– GPS L1 C/A: 1574.3970 – 1576.4430 MHz
– Galileo E1 / GPS L1C: 1573.3740 – 1577.4660 MHz
– GLONASS G1: 1597.5515 – 1605.8860 MHz
– BDS B1I: 1559.0520 – 1563.1440 MHz
For each frequency group combination in TS 38.171 [43] Table B.1.13.2-1, in the case that the UE supports only one GNSS, only one EN-DC band combination shall be used for testing for the supported GNSS. In the case the UE supports more than one GNSS then the one EN-DC band combination used for testing shall be common across the supported GNSSs unless there is no common EN-DC band combination in which case the tests shall be repeated as necessary.
4.12.6.3 Test frequencies for EN-DC band combinations
For performing the A-GNSS Sensitivity tests in clause 13.2 in EN-DC operation mode, the E-UTRA and NR frequencies and channel configurations shall be selected to ensure the intermodulation products fall into the GNSS receiver bands as defined in TS 38.171 [43] clause B.1.13.2 for the particular GNSS.
4.13 LPP transport mechanism for NR
The NR A-GNSS minimum performance requirements tested in this specification are agnostic as to whether the LPP session is performed over the Control Plane or the User Plane. Thus, the NR A-GNSS test cases in clause 13 support both configurations. The user can select either of the two options to run the test.
4.14 Multi-RTT test conditions
4.14.1 Simulated cells
For the Multi-RTT measurement test cases in clause 15 a cell environment as defined in 3GPP TS 38.508-1 [45] with NR Cell 1 and NR cell 2 are used. The default parameters for simulated cells are the same as specified in 3GPP TS 38.508-1 [45].
4.14.2 Propagation conditions
See TS 38.533 [47] clause C 2.
4.14.3 Measurement Reporting Requirements
This requirement assumes that the measurement report is not delayed by other LPP signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH where TTIDCCH is the duration of subframe or slot or subslot when the measurement report is transmitted on the PUSCH with subframe or slot or subslot duration. This measurement reporting delay excludes any delay caused by no UL resources for UE to send the measurement report.
4.14.4 Measurement Period Requirements
When physical layer receives last of NR-Multi-RTT-ProvideAssistanceData message and NR-Multi-RTT-RequestLocationInformation message from LMF via LPP [49], UE shall be able to measure multiple (up to the UE capability specified in TS 38.133 [50] clause 9.9.4.3) UE Rx-Tx time difference measurements as defined in TS 38.215 [57] in configured positioning frequency layers within the measurement period ms.
.
where is the index of positioning frequency layer,
is the measurement period for UE Rx-Tx time difference measurements in positioning frequency layer i as further defined in this clause,
L is total number of positioning frequency layers, and
is the periodicity of the UE Rx-Tx time difference measurement in positioning frequency layer i as defined further in this clause.
Where
is the carrier-specific scaling factor for NR PRS-based measurement in the positioning frequency layer i as defined in TS 38.133 [50] clause 9.1.5.2,
is the scaling factor for Rx beam sweeping, and =1 if positioning frequency layer i is in FR1 and =8 if positioning frequency layer i is in FR2,
is the time duration of available PRS resources in the positioning frequency layer i, to be measured during , and is calculated in the same way as PRS duration K defined in clause 5.1.6.5 of TS 38.214 [56]. For calculation of , only the PRS resources unmuted and fully or partially overlapped with MG are considered.
is the maximum number of DL PRS resources of positioning frequency layer i configured in a slot,
is UE capability combination per band where N is a duration of DL PRS symbols in ms corresponding to durationOfPRS-ProcessingSysmbols in TS 37.355 [49] processed every T ms corresponding to durationOfPRS-ProcessingSymbolsInEveryTms in TS 37.355 [49] for a given maximum bandwidth supported by UE corresponding to supportedBandwidthPRS in clause 4.2.7.2 of TS 37.355 [49],
is UE capability for number of DL PRS resources that it can process in a slot corresponding to maxNumOfDL-PRS-ResProcessedPerSlot as specified in clause 6.4.3 of TS 37.355 [49],
is the number of UE Rx-Tx time difference measurement samples and = 4,
is the measurement duration for the last UE Rx-Tx time difference measurement sample in the positioning layer i, including the sampling time and processing time, = + ,
is periodicity of UE Rx-Tx time difference measurement in positioning frequency layer i:
where
corresponds to durationOfPRS-ProcessingSymbolsInEveryTms in TS 37.355 [49],
, the least common multiple between and
is the measurement gap repetition periodicity in positioning frequency layer i.
is the PRS resource periodicity in positioning frequency layer i. If the positioning frequency layer i has more than one DL PRS resource sets with different PRS periodicities with muting, , the least common multiple of among DL PRS resource sets is used to derive , where
is the periodicity of PRS resource sets given by the higher-layer parameter DL-PRS-Periodicity.
is the scaling factor considering PRS resource muting. , where is the muting repetition factor given by the higher-layer parameter DL-PRS-MutingBitRepetitionFactor, and is the size of the bitmap .
Note: For the purpose of calculating TPRS,i, only the PRS resources fully or partially covered by the MG are considered.
The time starts from the first MG instance aligned with DL PRS resources in the assistance data after both the NR-Multi-RTT-RequestLocationInformation message and NR-Multi-RTT-ProvideAssistanceData message from LMF via LPP [49] are delivered to the physical layer of UE.
Note: No per-positioning frequency layer requirement is applied in scenarios when multiple positioning frequency layers are configured.
The UE Rx-Tx time difference measurement period is restarted if HO occurs during the measurement period and after SRS reconfiguration on the target cell is complete.
The measurement requirements do not apply for a PRS resource:
– if the PRS resource is across two sampling duration of N within duration or
– if time span of the PRS resource instance (including at least the minimum number of repetitions specified in the accuracy requirements) is greater than UE reported capability N.
If during the measurement period of one or more positioning frequency layers, the MG pattern is reconfigured either per UE request or not per UE request, the measurement period can be longer.
The requirements in this section apply, provided no PRS symbols are dropped during the measurement period TUERxTx,Total within measurement gaps due to collisions with other signals; otherwise, a longer measurement period may be used.
When PRS-RSRP is configured for multi-RTT, the UE Rx-Tx time difference measurements and PRS-RSRP measurements are performed over the same measurement period.
The requirements in TS 38.133 [50] clause 9.9.4 do not apply if the PRS configuration given by higher layer parameters NR-DL-PRS-AssistanceData exceeds any of the UE measurement capabilities given by NR-DL-PRS-ResourcesCapability in NR-Multi-RTT-ProvideCapabilities, and it is up to UE implementation which PRS resources are measured, subject to UE measurement capabilities.
When PSCell or SCell addition or release does not cause SRS reconfiguration during the measurement period, UE continues the UE Rx-Tx time difference measurement, and the measurement period requirements apply.
When PSCell or SCell addition or release causes SRS reconfiguration during the measurement period, UE shall restart the UE Rx-Tx time difference measurement after the SRS reconfiguration on the target cell is complete.
When SRS is reconfigured without serving cell change during the measurement period, UE shall restart the UE Rx-Tx time difference measurement after the SRS reconfiguration is complete. If UE uplink transmission timing changes due to the network-configured Timing Advance command during the UE Rx-Tx measurement period, then the UE Rx-Tx time difference measurement period is restarted after uplink transmission timing changes, and the UE Rx-Tx time difference measurement period requirements in this clause shall not apply.
If UE uplink transmission timing changes due to the change in the NTA_offset defined in TS 38.133 [50] Table 7.1.2-2 during the UE Rx-Tx measurement period, then the UE Rx-Tx time difference measurement period is restarted after uplink transmission timing changes, and the UE Rx-Tx time difference measurement period requirements in this clause shall not apply.
4.14.5 Measurement Accuracy Requirements
FFS
4.14.6 Reporting mapping
4.14.6.1 Absolute UE Rx-Tx Measurement Report Mapping
The reporting range for the absolute UE Rx-Tx time difference measurement (TUE Rx-Tx) is defined from -985024Tc to 985024Tc with the resolution step of 2kTc, where:
Tc is defined in TS 38.211 [53],
kmin≤k≤kmax,
kmin=[2] and kmax=5, when at least one of the PRS and the SRS resources configured for TUE Rx-Tx is in FR1,
kmin=0 and kmax=5, when both PRS and SRS resources configured for TUE Rx-Tx are in FR2,
k≥ timingReportingGranularityFactor [49] configured by LMF via LPP for the UE Rx-Tx time difference measurement.
The TUE Rx-Tx report mapping for k = 0, 1, 2, 3, 4, and 5 are specified in Tables 4.14.6.1-1, 14.14.6.1-2, 4.14.6.1-3, 4.14.6.1-4, 4.14.6.1-5, and 4.14.6.1-6, respectively.
Table 4.14.6.1-1: Absolute UE Rx-Tx time difference measurement report mapping for k=0
Reported Quantity Value |
Measured Quantity Value |
Unit |
RX-TX_TIME_DIFFERENCE_0000 |
TUE Rx-Tx < -985024 |
Tc |
RX-TX_TIME_DIFFERENCE_0001 |
-985024 TUE Rx-Tx < -985023 |
Tc |
RX-TX_TIME_DIFFERENCE_0002 |
-985023 TUE Rx-Tx < -985022 |
Tc |
|
|
… |
RX-TX_TIME_DIFFERENCE_985024 |
-1 TUE Rx-Tx < 0 |
Tc |
RX-TX_TIME_DIFFERENCE_985025 |
0 TUE Rx-Tx < 1 |
Tc |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_1970047 |
985022 TUE Rx-Tx < 985023 |
Tc |
RX-TX_TIME_DIFFERENCE_1970048 |
985023 TUE Rx-Tx < 985024 |
Tc |
RX-TX_TIME_DIFFERENCE_1970049 |
985024 TUE Rx-Tx |
Tc |
Table 4.14.6.1-2: Absolute UE Rx-Tx time difference measurement report mapping for k=1
Reported Quantity Value |
Measured Quantity Value |
Unit |
RX-TX_TIME_DIFFERENCE_0000 |
TUE Rx-Tx < -985024 |
Tc |
RX-TX_TIME_DIFFERENCE_0001 |
-985024 TUE Rx-Tx < -985022 |
Tc |
RX-TX_TIME_DIFFERENCE_0002 |
-985022 TUE Rx-Tx < -985020 |
Tc |
|
|
… |
RX-TX_TIME_DIFFERENCE_492512 |
-2 TUE Rx-Tx < 0 |
Tc |
RX-TX_TIME_DIFFERENCE_492513 |
0 TUE Rx-Tx < 2 |
Tc |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_985023 |
985020 TUE Rx-Tx < 985022 |
Tc |
RX-TX_TIME_DIFFERENCE_985024 |
985022 TUE Rx-Tx < 985024 |
Tc |
RX-TX_TIME_DIFFERENCE_985025 |
985024 TUE Rx-Tx |
Tc |
Table 4.14.6.1-3: Absolute UE Rx-Tx time difference measurement report mapping for k=2
Reported Quantity Value |
Measured Quantity Value |
Unit |
RX-TX_TIME_DIFFERENCE_0000 |
TUE Rx-Tx < -985024 |
Tc |
RX-TX_TIME_DIFFERENCE_0001 |
-985024 TUE Rx-Tx < -985020 |
Tc |
RX-TX_TIME_DIFFERENCE_0002 |
-985020 TUE Rx-Tx < -985016 |
Tc |
|
|
… |
RX-TX_TIME_DIFFERENCE_246256 |
-4 TUE Rx-Tx < 0 |
Tc |
RX-TX_TIME_DIFFERENCE_246257 |
0 TUE Rx-Tx < 4 |
Tc |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_492511 |
985016 TUE Rx-Tx < 985020 |
Tc |
RX-TX_TIME_DIFFERENCE_492512 |
985020 TUE Rx-Tx < 985024 |
Tc |
RX-TX_TIME_DIFFERENCE_492513 |
985024 TUE Rx-Tx |
Tc |
Table 4.14.6.1-4: Absolute UE Rx-Tx time difference measurement report mapping for k=3
Reported Quantity Value |
Measured Quantity Value |
Unit |
RX-TX_TIME_DIFFERENCE_0000 |
TUE Rx-Tx < -985024 |
Tc |
RX-TX_TIME_DIFFERENCE_0001 |
-985024 TUE Rx-Tx < -985016 |
Tc |
RX-TX_TIME_DIFFERENCE_0002 |
-985016 TUE Rx-Tx < -985008 |
Tc |
|
|
… |
RX-TX_TIME_DIFFERENCE_123128 |
-8 TUE Rx-Tx < 0 |
Tc |
RX-TX_TIME_DIFFERENCE_123129 |
0 TUE Rx-Tx < 8 |
Tc |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_246255 |
985008 TUE Rx-Tx < 985016 |
Tc |
RX-TX_TIME_DIFFERENCE_246256 |
985016 TUE Rx-Tx < 985024 |
Tc |
RX-TX_TIME_DIFFERENCE_246257 |
985024 TUE Rx-Tx |
Tc |
Table 4.14.6.1-5: Absolute UE Rx-Tx time difference measurement report mapping for k=4
Reported Quantity Value |
Measured Quantity Value |
Unit |
RX-TX_TIME_DIFFERENCE_0000 |
TUE Rx-Tx < -985024 |
Tc |
RX-TX_TIME_DIFFERENCE_0001 |
-985024 TUE Rx-Tx < -985008 |
Tc |
RX-TX_TIME_DIFFERENCE_0002 |
-985008 TUE Rx-Tx < -984992 |
Tc |
|
|
… |
RX-TX_TIME_DIFFERENCE_61564 |
-16 TUE Rx-Tx < 0 |
Tc |
RX-TX_TIME_DIFFERENCE_61565 |
0 TUE Rx-Tx < 16 |
Tc |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_123127 |
984992 TUE Rx-Tx < 985008 |
Tc |
RX-TX_TIME_DIFFERENCE_123128 |
985008 TUE Rx-Tx < 985024 |
Tc |
RX-TX_TIME_DIFFERENCE_123129 |
985024 TUE Rx-Tx |
Tc |
Table 4.14.6.1-6: Absolute UE Rx-Tx time difference measurement report mapping for k=5
Reported Quantity Value |
Measured Quantity Value |
Unit |
RX-TX_TIME_DIFFERENCE_0000 |
TUE Rx-Tx < -985024 |
Tc |
RX-TX_TIME_DIFFERENCE_0001 |
-985024 TUE Rx-Tx < -984992 |
Tc |
RX-TX_TIME_DIFFERENCE_0002 |
-984992 TUE Rx-Tx < -984960 |
Tc |
|
|
… |
RX-TX_TIME_DIFFERENCE_30782 |
-32 TUE Rx-Tx < 0 |
Tc |
RX-TX_TIME_DIFFERENCE_30783 |
0 TUE Rx-Tx < 32 |
Tc |
… |
… |
… |
RX-TX_TIME_DIFFERENCE_61563 |
984960 TUE Rx-Tx < 984992 |
Tc |
RX-TX_TIME_DIFFERENCE_61564 |
984992 TUE Rx-Tx < 985024 |
Tc |
RX-TX_TIME_DIFFERENCE_61565 |
985024 TUE Rx-Tx |
Tc |
4.14.6.2 Differential UE Rx-Tx Measurement Report Mapping
The reporting range for differential UE Rx-Tx time difference measurement (TUE Rx-Tx) is defined from 0 up to 8191Tc where:
TUE Rx-Tx = TUE Rx-Tx1 – TUE Rx-Tx2; where:
TUE Rx-Tx1 > TUE Rx-Tx2,
TUE Rx-Tx1 is the first absolute UE Rx-Tx time difference measurement,
TUE Rx-Tx1 is the second absolute UE Rx-Tx time difference measurement,
Tc is defined in TS 38.211 [53],
kmin≤k≤kmax,
kmin=[2] and kmax=5, when at least one of the PRS and the SRS resources configured for TUE Rx-Tx is in FR1,
kmin=0 and kmax=5, when all the PRS and SRS resources configured for TUE Rx-Tx are in FR2,
k≥ timingReportingGranularityFactor [49] configured by LMF via LPP for the UE Rx-Tx time difference measurement.
The TUE Rx-Tx report mapping for k = 0, 1, 2, 3, 4, and 5 are specified in Tables 4.14.6.2-1, 4.14.6.2-2, 4.14.6.2-3, 4.14.6.2-4, 4.14.6.2-5, and 4.14.6.2-6, respectively.
Table 4.14.6.2-1: Differential UE Rx-Tx time difference measurement report mapping for k=0
Reported Quantity Value |
Measured Quantity Value |
Unit |
DIFF_RX-TX_TIME_DIFFERENCE_0000 |
0 TUE Rx-Tx < 1 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0001 |
1 TUE Rx-Tx < 2 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0002 |
2 TUE Rx-Tx < 3 |
Tc |
|
|
… |
DIFF_RX-TX_TIME_DIFFERENCE_8189 |
8189 TUE Rx-Tx < 8190 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_8190 |
8190 TUE Rx-Tx < 8191 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_8191 |
8191 TUE Rx-Tx |
Tc |
Table 4.14.6.2-2: Differential UE Rx-Tx time difference measurement report mapping for k=1
Reported Quantity Value |
Measured Quantity Value |
Unit |
DIFF_RX-TX_TIME_DIFFERENCE_0000 |
0 TUE Rx-Tx < 2 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0001 |
2 TUE Rx-Tx < 4 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0002 |
4 TUE Rx-Tx < 6 |
Tc |
|
|
… |
DIFF_RX-TX_TIME_DIFFERENCE_4093 |
8186 TUE Rx-Tx < 8188 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_4094 |
8188 TUE Rx-Tx < 8190 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_4095 |
8190 TUE Rx-Tx |
Tc |
Table 4.14.6.2-3: Differential UE Rx-Tx time difference measurement report mapping for k=2
Reported Quantity Value |
Measured Quantity Value |
Unit |
DIFF_RX-TX_TIME_DIFFERENCE_0000 |
0 TUE Rx-Tx < 4 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0001 |
4 TUE Rx-Tx < 8 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0002 |
8 TUE Rx-Tx < 12 |
Tc |
|
|
… |
DIFF_RX-TX_TIME_DIFFERENCE_2045 |
8180 TUE Rx-Tx < 8184 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_2046 |
8184 TUE Rx-Tx < 8188 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_2047 |
8188 TUE Rx-Tx |
Tc |
Table 4.14.6.2-4: Differential UE Rx-Tx time difference measurement report mapping for k=3
Reported Quantity Value |
Measured Quantity Value |
Unit |
DIFF_RX-TX_TIME_DIFFERENCE_0000 |
0 TUE Rx-Tx < 8 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0001 |
8 TUE Rx-Tx < 16 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0002 |
16 TUE Rx-Tx < 24 |
Tc |
|
|
… |
DIFF_RX-TX_TIME_DIFFERENCE_1021 |
8168 TUE Rx-Tx < 8176 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_1022 |
8176 TUE Rx-Tx < 8184 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_1023 |
8184 TUE Rx-Tx |
Tc |
Table 4.14.6.2-5: Differential UE Rx-Tx time difference measurement report mapping for k=4
Reported Quantity Value |
Measured Quantity Value |
Unit |
DIFF_RX-TX_TIME_DIFFERENCE_0000 |
0 TUE Rx-Tx < 16 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0001 |
16 TUE Rx-Tx < 32 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0002 |
32 TUE Rx-Tx < 48 |
Tc |
|
|
… |
DIFF_RX-TX_TIME_DIFFERENCE_509 |
8144 TUE Rx-Tx < 8160 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_510 |
8160 TUE Rx-Tx < 8176 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_511 |
8176 TUE Rx-Tx |
Tc |
Table 4.14.6.2-6: Differential UE Rx-Tx time difference measurement report mapping for k=5
Reported Quantity Value |
Measured Quantity Value |
Unit |
DIFF_RX-TX_TIME_DIFFERENCE_0000 |
0 TUE Rx-Tx < 32 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0001 |
32 TUE Rx-Tx < 64 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_0002 |
64 TUE Rx-Tx < 96 |
Tc |
|
|
… |
DIFF_RX-TX_TIME_DIFFERENCE_253 |
8096 TUE Rx-Tx < 8128 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_254 |
8128 TUE Rx-Tx < 8160 |
Tc |
DIFF_RX-TX_TIME_DIFFERENCE_255 |
8160 TUE Rx-Tx |
Tc |
4.14.6.3 Additional Path Report Mapping for UE Rx-Tx Time Difference
The reporting range for the additional path reporting for an UE Rx-Tx time difference measurement is defined up to the range from -8175×Tc to 8175×Tc with the resolution step of 2k×Tc, where
Tc is defined in TS 38.211 [53],
kmin≤k≤kmax,
kmin=[2] and kmax=5, when at least one of the PRS resource and SRS resource configured for the UE Rx-Tx time difference measurement is in FR1,
kmin=0 and kmax=5, when both of the PRS resource and SRS resource configured for the UE Rx-Tx time difference measurement is in FR2,
k≥ timingReportingGranularityFactor [49] configured by LMF via LPP for the UE Rx-Tx time difference measurement.
The UE can report the timing of up to two additional paths with respect to the path timing determining the UE Rx-Tx time difference measurement.
The report mappings for different k values are specified in Tables 4.14.6.3-1 − 4.14.6.3-6.
Table 4.14.6.3-1: Report mapping for k=0
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_00000 |
Δpath < -8175 |
Tc |
path_00001 |
-8175 ≤ Δpath < -8174 |
Tc |
path_00002 |
-8174 ≤ Δpath < -8173 |
Tc |
… |
… |
… |
path_08175 |
-1 ≤ Δpath < 0 |
Tc |
path_08176 |
0 ≤ Δpath < 1 |
Tc |
… |
… |
… |
path_ 16349 |
8173 ≤ Δpath < 8174 |
Tc |
path_ 16350 |
8174 ≤ Δpath < 8175 |
Tc |
path_ 16351 |
8175 ≤ Δpath |
Tc |
Table 4.14.6.3-2: Report mapping for k=1
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8175 |
Tc |
path_0001 |
-8175 ≤ Δpath < -8173 |
Tc |
path_0002 |
-8173 ≤ Δpath < -8171 |
Tc |
… |
… |
… |
path_4088 |
-1 ≤ Δpath < 1 |
Tc |
… |
… |
… |
path_8174 |
8171 ≤ Δpath < 8173 |
Tc |
path_8175 |
8173 ≤ Δpath < 8175 |
Tc |
path_8176 |
8175 ≤ Δpath |
Tc |
Table 4.14.6.3-3: Report mapping for k=2
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8174 |
Tc |
path_0001 |
-8174 ≤ Δpath < -8170 |
Tc |
path_0002 |
-8170 ≤ Δpath < -8166 |
Tc |
… |
… |
… |
path_2044 |
-2 ≤ Δpath < 2 |
Tc |
… |
… |
… |
path_4086 |
8166 ≤ Δpath < 8170 |
Tc |
path_4087 |
8170 ≤ Δpath < 8174 |
Tc |
path_4088 |
8174 ≤ Δpath |
Tc |
Table 4.14.6.3-4: Report mapping for k=3
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8172 |
Tc |
path_0001 |
-8172 ≤ Δpath < -8164 |
Tc |
path_0002 |
-8164 ≤ Δpath < -8156 |
Tc |
… |
… |
… |
path_1022 |
-4 ≤ Δpath < 4 |
Tc |
… |
… |
… |
path_2042 |
8156 ≤ Δpath < 8164 |
Tc |
path_2043 |
8164 ≤ Δpath < 8172 |
Tc |
path_2044 |
8172 ≤ Δpath |
Tc |
Table 4.14.6.3-5: Report mapping for k=4
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8168 |
Tc |
path_0001 |
-8168 ≤ Δpath < -8152 |
Tc |
path_0002 |
-8152 ≤ Δpath < -8136 |
Tc |
… |
… |
… |
path_511 |
-8 ≤ Δpath < 8 |
Tc |
… |
… |
… |
path_1020 |
8136 ≤ Δpath < 8152 |
Tc |
path_1021 |
8152 ≤ Δpath < 8168 |
Tc |
path_1022 |
8168 ≤ Δpath |
Tc |
Table 4.14.6.3-6: Report mapping for k=5
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_000 |
Δpath < -8160 |
Tc |
path_001 |
-8160 ≤ Δpath < -8128 |
Tc |
path_002 |
-8128 ≤ Δpath < -8096 |
Tc |
… |
… |
… |
path_256 |
0 ≤ Δpath < 32 |
Tc |
… |
… |
… |
path_509 |
8096 ≤ Δpath < 8128 |
Tc |
path_510 |
8128 ≤ Δpath < 8160 |
Tc |
path_511 |
8160 ≤ Δpath |
Tc |
4.15 DL-TDOA test conditions
4.15.1 Simulated cells
For the DL-TDOA measurement test cases in clause 14, a multi cell environment as defined in 3GPP TS 38.508-1 [45] with NR Cell 1, NR Cell 2 and NR Cell 3 (if needed in the test) are used. The default parameters for simulated cells are the same as specified in 3GPP TS 38.508-1 [45].
4.15.2 Propagation conditions
See TS 38.533 [47] clause C 2.
4.15.3 Measurement Reporting Requirements
The measurement reporting delay is defined as the time between the moment when the periodic measurement report is triggered and the moment when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH where TTIDCCH is the duration of subframe or slot or subslot when the measurement report is transmitted on the PUSCH with subframe or slot or subslot duration. This measurement reporting delay excludes any delay caused by no UL resources for UE to send the measurement report.
4.15.4 Measurement Period Requirements
When physical layer receives last of NR-TDOA-ProvideAssistanceData message and NR-TDOA-RequestLocationInformation message from LMF via LPP [49], the UE shall be able to measure multiple (up to the UE capability specified in TS 38.133 [50] Clause 9.9.2.3) DL RSTD measurements, defined in TS 38.215 [57], during the measurement period defined as:
Where ,
is the index of positioning frequency layer,
is total number of positioning frequency layers, and
is the periodicity of the PRS RSTD measurement in positioning frequency layer i
is the measurement period for PRS RSTD measurement in positioning frequency layer i as specified below:
,
where:
is the UE Rx beam sweeping factor. In FR1, = 1; and in FR2, = 8.
is the carrier-specific scaling factor for NR PRS-based positioning measurements in positioning frequency layer i as defined in TS 38.133 [50] clause 9.1.5.2.
is the maximum number of DL PRS resources in positioning frequency layer i configured in a slot.
is the time duration of available PRS in the positioning frequency layer i to be measured during , and is calculated in the same way as PRS duration K defined in clause 5.1.6.5 of TS 38.214 [56]. For calculation of , only the PRS resources unmuted and fully or partially overlapped with MG are considered.
is the number of PRS RSTD samples and = 4.
is the measurement duration for the last PRS RSTD sample in positioning frequency layer i, including the sampling time and processing time, = + ,
is the periodicity of the PRS RSTD measurement in positioning frequency layer i defined as:
=
Where,
corresponds to durationOfPRS-ProcessingSymbolsInEveryTms in TS 37.355 [49],
, the least common multiple between and .
is the repetition periodicity of the measurement gap applicable for measurement in the PRS frequency layer i.
is the periodicity of DL PRS resource with muting on positioning frequency layer i.
If more than one PRS periodicities are configured in positioning frequency layer i, the least common multiple of PRS periodicities among all DL PRS resource sets in the positioning frequency layer is used to derive , where,
, is the PRS periodicity with muting per PRS resource,
is the periodicity of PRS resource sets given by the higher-layer parameter DL-PRS-Periodicity.
is the scaling factor considering PRS resource muting. , where
is the muting repetition factor given by the higher-layer parameter DL-PRS-MutingBitRepetitionFactor, and is the size of the bitmap .
- Note: For the purpose of calculating TPRS,i, only the PRS resources fully or partially covered by the MG are considered.
is UE capability combination per band where N is a duration of DL PRS symbols in ms corresponding to durationOfPRS-ProcessingSysmbols in TS 37.355 [49] processed every T ms corresponding to durationOfPRS-ProcessingSymbolsInEveryTms in TS 37.355 [49] for a given maximum bandwidth supported by UE corresponding to supportedBandwidthPRS in TS 37.355 [49].
is UE capability for number of DL PRS resources that it can process in a slot as indicated by maxNumOfDL-PRS-ResProcessedPerSlot specified in TS 37.355 [49].
The time starts from the first MG instance aligned with a DL PRS resource(s) in the assistance data after both the NR-TDOA-ProvideAssistanceData message and NR-TDOA-RequestLocationInformation message are delivered from LMF to the physical layer of UE via LPP [34].
Note: No per-positioning frequency layer requirement is applied in scenarios when multiple positioning frequency layers are configured.
If during the measurement period of one or more positioning frequency layers, the MG pattern is reconfigured, the measurement period can be longer. When PRS-RSRP is configured for DL-TDOA, RSTD and RSRP are performed over the same measurement period.
The measurement requirements in this clause apply, provided no PRS symbols are dropped during the measurement period TRSTD,Total within measurement gaps due to collisions with other signals; otherwise, the measurement period can be longer.
If CSSF changes during the measurement period, the measurement period could be longer.
The measurement requirements do not apply for a PRS resource, if the PRS resource is across two sampling duration of N within duration .
The measurement requirements do not apply for a PRS resource, if time span of the PRS resource instance (including at least the minimum number of repetitions specified in the accuracy requirements) is greater than UE reported capability N.
The requirements in TS 38.133 [50] clause 9.9.2 do not apply if the PRS configuration given by higher layer parameters NR-DL-PRS-AssistanceData exceeds any of the UE measurement capabilities given by NR-DL-PRS-ResourcesCapability in NR-DL-TDOA-ProvideCapabilities, and it is up to UE implementation which PRS resources are measured, subject to UE measurement capabilities.
If handover occurs while RSTD measurements are being performed, then the UE shall continue and complete the on-going RSTD measurements. The RSTD measurement period can be longer. The UE shall meet the RSTD measurement accuracy requirements in TS 38.133 [50] clause 10.1.23.
4.15.5 Measurement Accuracy Requirements
FFS
4.15.6 Reporting mapping
4.15.6.1 Absolute DL RSTD Measurement Reporting
The reporting range for the DL RSTD measurement is defined from -985024×Tc to 985024×Tc with the resolution step of 2k×Tc, where
Tc is defined in TS 38.211 [53],
kmin≤k≤kmax,
kmin=[2] and kmax=5, when configured PRS resource of at least one of the reference cell and neighbour cell measured for the RSTD measurement is in FR1,
kmin=0 and kmax=5, when configured PRS resource of both the reference cell and neighbour cell measured for the RSTD measurement are in FR2,
k≥ timingReportingGranularityFactor [49] configured by LMF via LPP for the RSTD measurement.
The measurement report mapping for different k values are specified in Tables 4.15.6.1-1 − 4.15.6.1-6.
Table 4.15.6.1-1: Report mapping for k=0
Reported Quantity Value, |
Measured Quantity Value, |
Unit |
RSTD_i |
RSTD |
|
RSTD_0000000 |
RSTD < -985024 |
Tc |
RSTD_0000001 |
-985024 ≤ RSTD < -985023 |
Tc |
RSTD_0000002 |
-985023 ≤ RSTD < -985022 |
Tc |
… |
… |
… |
RSTD_0985024 |
-1 ≤ RSTD < 0 |
Tc |
RSTD_0985025 |
0 ≤ RSTD < 1 |
Tc |
… |
… |
… |
RSTD_1970047 |
985022 ≤ RSTD < 985023 |
Tc |
RSTD_1970048 |
985023 ≤ RSTD < 985024 |
Tc |
RSTD_1970049 |
985024 ≤ RSTD |
Tc |
Table 4.15.6.1-2: Report mapping for k=1
Reported Quantity Value, |
Measured Quantity Value, |
Unit |
RSTD_i |
RSTD |
|
RSTD_000000 |
RSTD < -985024 |
Tc |
RSTD_000001 |
-985024 ≤ RSTD < -985022 |
Tc |
RSTD_000002 |
-985022 ≤ RSTD < -985020 |
Tc |
… |
… |
… |
RSTD_492512 |
-2 ≤ RSTD < 0 |
Tc |
RSTD_492513 |
0 ≤ RSTD < 2 |
Tc |
… |
… |
… |
RSTD_985023 |
985020 ≤ RSTD < 985022 |
Tc |
RSTD_985024 |
985022 ≤ RSTD < 985024 |
Tc |
RSTD_985025 |
985024 ≤ RSTD |
Tc |
Table 4.15.6.1-3: Report mapping for k=2
Reported Quantity Value, |
Measured Quantity Value, |
Unit |
RSTD_i |
RSTD |
|
RSTD_000000 |
RSTD < -985024 |
Tc |
RSTD_000001 |
-985024 ≤ RSTD < -985020 |
Tc |
RSTD_000002 |
-985020 ≤ RSTD < -985016 |
Tc |
… |
… |
… |
RSTD_246256 |
-4 ≤ RSTD < 0 |
Tc |
RSTD_246257 |
0 ≤ RSTD < 4 |
Tc |
… |
… |
… |
RSTD_492511 |
985016 ≤ RSTD < 985020 |
Tc |
RSTD_492512 |
985020 ≤ RSTD < 985024 |
Tc |
RSTD_492513 |
985024 ≤ RSTD |
Tc |
Table 4.15.6.1-4: Report mapping for k=3
Reported Quantity Value |
Measured Quantity Value, |
Unit |
RSTD_i |
RSTD |
|
RSTD_000000 |
RSTD < -985024 |
Tc |
RSTD_000001 |
-985024 ≤ RSTD < -985016 |
Tc |
RSTD_000002 |
-985016 ≤ RSTD < -985008 |
Tc |
… |
… |
… |
RSTD_123128 |
-8 ≤ RSTD < 0 |
Tc |
RSTD_123129 |
0 ≤ RSTD < 8 |
Tc |
… |
… |
… |
RSTD_246255 |
985008 ≤ RSTD < 985016 |
Tc |
RSTD_246256 |
985016 ≤ RSTD < 985024 |
Tc |
RSTD_246257 |
985024 ≤ RSTD |
Tc |
Table 4.15.6.1-5: Report mapping for k=4
Reported Quantity Value, |
Measured Quantity Value, |
Unit |
RSTD_i |
RSTD |
|
RSTD_000000 |
RSTD < -985024 |
Tc |
RSTD_000001 |
-985024 ≤ RSTD < -985008 |
Tc |
RSTD_000002 |
-985008 ≤ RSTD < -984992 |
Tc |
… |
… |
… |
RSTD_061564 |
-16 ≤ RSTD < 0 |
Tc |
RSTD_061565 |
0 ≤ RSTD < 16 |
Tc |
… |
… |
… |
RSTD_123127 |
984992 ≤ RSTD < 985008 |
Tc |
RSTD_123128 |
985008 ≤ RSTD < 985024 |
Tc |
RSTD_123129 |
985024 ≤ RSTD |
Tc |
Table 4.15.6.1-6: Report mapping for k=5
Reported Quantity Value, |
Measured Quantity Value, |
Unit |
RSTD_i |
RSTD |
|
RSTD_00000 |
RSTD < -985024 |
Tc |
RSTD_00001 |
-985024 ≤ RSTD < -984992 |
Tc |
RSTD_00002 |
-984992 ≤ RSTD < -984960 |
Tc |
… |
… |
… |
RSTD_30782 |
-32 ≤ RSTD < 0 |
Tc |
RSTD_30783 |
0 ≤ RSTD < 32 |
Tc |
… |
… |
… |
RSTD_61563 |
984960 ≤ RSTD < 984992 |
Tc |
RSTD_61564 |
984992 ≤ RSTD < 985024 |
Tc |
RSTD_61565 |
985024 ≤ RSTD |
Tc |
4.15.6.2 Differential Reporting for DL RSTD Measurement
A first DL RSTD measurement is reported by means of differential reporting, i.e. as ΔRSTD, relative to a second DL RSTD measurement (RSTD2), provided that:
– the absolute measured quantity value of the second DL RSTD measurement (RSTD2) is not larger than the absolute measured quantity value of the first DL RSTD measurement (RSTD1), i.e., ΔRSTD=RSTD1-RSTD2≥0, and
– the absolute value of the second DL RSTD measurement (RSTD2) is reported together with ΔRSTD for the first DL RSTD measurement.
The reporting range for differential reporting ΔRSTD of the first DL RSTD measurement is defined from 0 up to 8191×Tc with the resolution step of 2k×Tc, where
Tc is defined in TS 38.211 [53],
kmin≤k≤kmax,
kmin=[2] and kmax=5, when configured PRS resource of at least one of the reference cell and neighbour cell measured for the first RSTD measurement or second RSTD measurement is in FR1,
kmin=0 and kmax=5, when configured PRS resource of both the reference cell and neighbour cell measured for both of the first RSTD measurement and the second RSTD measurement are in FR2,
k≥ timingReportingGranularityFactor [49] configured by LMF via LPP for the RSTD measurement.
The measurement report mapping for different k values are specified in Tables 4.15.6.2-1 − 4.15.6.2-6.
Table 4.15.6.2-1: Report mapping for k=0
Reported Quantity Value, DIFFRSTD_i |
ΔRSTD = RSTD1 − RSTD2 |
Unit |
DIFFRSTD_0000 |
0 ≤ ΔRSTD < 1 |
Tc |
DIFFRSTD_0001 |
1 ≤ ΔRSTD < 2 |
Tc |
DIFFRSTD_0002 |
2 ≤ ΔRSTD < 3 |
Tc |
… |
… |
… |
DIFFRSTD_8189 |
8189 ≤ ΔRSTD < 8190 |
Tc |
DIFFRSTD_8190 |
8190 ≤ ΔRSTD < 8191 |
Tc |
DIFFRSTD_8191 |
8191 ≤ ΔRSTD |
Tc |
Table 4.15.6.2-2: Report mapping for k=1
Reported Quantity Value, DIFFRSTD_i |
ΔRSTD = RSTD1 − RSTD2 |
Unit |
DIFFRSTD_0000 |
0 ≤ ΔRSTD < 2 |
Tc |
DIFFRSTD_0001 |
2 ≤ ΔRSTD < 4 |
Tc |
DIFFRSTD_0002 |
4 ≤ ΔRSTD < 6 |
Tc |
… |
… |
… |
DIFFRSTD_4093 |
8186 ≤ ΔRSTD < 8188 |
Tc |
DIFFRSTD_4094 |
8188 ≤ ΔRSTD < 8190 |
Tc |
DIFFRSTD_4095 |
8190 ≤ ΔRSTD |
Tc |
Table 4.15.6.2-3: Report mapping for k=2
Reported Quantity Value, DIFFRSTD_i |
ΔRSTD = RSTD1 − RSTD2 |
Unit |
DIFFRSTD_0000 |
0 ≤ ΔRSTD < 4 |
Tc |
DIFFRSTD_0001 |
4 ≤ ΔRSTD < 8 |
Tc |
DIFFRSTD_0002 |
8 ≤ ΔRSTD < 12 |
Tc |
… |
… |
… |
DIFFRSTD_2045 |
8180 ≤ ΔRSTD < 8184 |
Tc |
DIFFRSTD_2046 |
8184 ≤ ΔRSTD < 8188 |
Tc |
DIFFRSTD_2047 |
8188 ≤ ΔRSTD |
Tc |
Table 4.15.6.2-4: Report mapping for k=3
Reported Quantity Value, DIFFRSTD_i |
ΔRSTD = RSTD1 − RSTD2 |
Unit |
DIFFRSTD_0000 |
0 ≤ ΔRSTD < 8 |
Tc |
DIFFRSTD_0001 |
8 ≤ ΔRSTD < 16 |
Tc |
DIFFRSTD_0002 |
16 ≤ ΔRSTD < 24 |
Tc |
… |
… |
… |
DIFFRSTD_1021 |
8168 ≤ ΔRSTD < 8176 |
Tc |
DIFFRSTD_1022 |
8176 ≤ ΔRSTD < 8184 |
Tc |
DIFFRSTD_1023 |
8184 ≤ ΔRSTD |
Tc |
Table 4.15.6.2-5: Report mapping for k=4
Reported Quantity Value, DIFFRSTD_i |
ΔRSTD = RSTD1 − RSTD2 |
Unit |
DIFFRSTD_000 |
0 ≤ ΔRSTD < 16 |
Tc |
DIFFRSTD_001 |
16 ≤ ΔRSTD < 32 |
Tc |
DIFFRSTD_002 |
32 ≤ ΔRSTD < 48 |
Tc |
… |
… |
… |
DIFFRSTD_509 |
8144 ≤ ΔRSTD < 8160 |
Tc |
DIFFRSTD_510 |
8160 ≤ ΔRSTD < 8176 |
Tc |
DIFFRSTD_511 |
8176 ≤ ΔRSTD |
Tc |
Table 4.15.6.2-6: Report mapping for k=5
Reported Quantity Value, DIFFRSTD_i |
ΔRSTD = RSTD1 − RSTD2 |
Unit |
DIFFRSTD_000 |
0 ≤ ΔRSTD < 32 |
Tc |
DIFFRSTD_001 |
32 ≤ ΔRSTD < 64 |
Tc |
DIFFRSTD_002 |
64 ≤ ΔRSTD < 96 |
Tc |
… |
… |
… |
DIFFRSTD_253 |
8096 ≤ ΔRSTD < 8128 |
Tc |
DIFFRSTD_254 |
8128 ≤ ΔRSTD < 8160 |
Tc |
DIFFRSTD_255 |
8160 ≤ ΔRSTD |
Tc |
4.15.6.3 Additional Path Report Mapping for DL RSTD
The reporting range for the additional path reporting for an RSTD measurement is defined up to the range from -8175×Tc to 8175×Tc with the resolution step of 2k×Tc, where
Tc is defined in TS 38.211 [53],
kmin≤k≤kmax,
kmin=[2] and kmax=5, when configured PRS resource of at least one of the reference cell and neighbour cell measured for the RSTD measurement is in FR1,
kmin=0 and kmax=5, when configured PRS resource of both the reference cell and neighbour cell measured for the RSTD measurement are in FR2,
k≥ timingReportingGranularityFactor [49] configured by LMF via LPP for the RSTD measurement.
The UE can report the timing of up to two additional paths with respect to the path timing determining the RSTD measurement.
The report mappings for different k values are specified in Tables 10.1.23.3.3-1 − 10.1.23.3.3-6.
Table 10.1.23.3.3-1: Report mapping for k=0
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_00000 |
Δpath < -8175 |
Tc |
path_00001 |
-8175 ≤ Δpath < -8174 |
Tc |
path_00002 |
-8174 ≤ Δpath < -8173 |
Tc |
… |
… |
… |
path_08175 |
-1 ≤ Δpath < 0 |
Tc |
path_08176 |
0 ≤ Δpath < 1 |
Tc |
… |
… |
… |
path_ 16349 |
8173 ≤ Δpath < 8174 |
Tc |
path_ 16350 |
8174 ≤ Δpath < 8175 |
Tc |
path_ 16351 |
8175 ≤ Δpath |
Tc |
Table 10.1.23.3.3-2: Report mapping for k=1
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8175 |
Tc |
path_0001 |
-8175 ≤ Δpath < -8173 |
Tc |
path_0002 |
-8173 ≤ Δpath < -8171 |
Tc |
… |
… |
… |
path_4088 |
-1 ≤ Δpath < 1 |
Tc |
… |
… |
… |
path_8174 |
8171 ≤ Δpath < 8173 |
Tc |
path_8175 |
8173 ≤ Δpath < 8175 |
Tc |
path_8176 |
8175 ≤ Δpath |
Tc |
Table 10.1.23.3.3-3: Report mapping for k=2
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8174 |
Tc |
path_0001 |
-8174 ≤ Δpath < -8170 |
Tc |
path_0002 |
-8170 ≤ Δpath < -8166 |
Tc |
… |
… |
… |
path_2044 |
-2 ≤ Δpath < 2 |
Tc |
… |
… |
… |
path_4086 |
8166 ≤ Δpath < 8170 |
Tc |
path_4087 |
8170 ≤ Δpath < 8174 |
Tc |
path_4088 |
8174 ≤ Δpath |
Tc |
Table 10.1.23.3.3-4: Report mapping for k=3
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8172 |
Tc |
path_0001 |
-8172 ≤ Δpath < -8164 |
Tc |
path_0002 |
-8164 ≤ Δpath < -8156 |
Tc |
… |
… |
… |
path_1022 |
-4 ≤ Δpath < 4 |
Tc |
… |
… |
… |
path_2042 |
8156 ≤ Δpath < 8164 |
Tc |
path_2043 |
8164 ≤ Δpath < 8172 |
Tc |
path_2044 |
8172 ≤ Δpath |
Tc |
Table 10.1.23.3.3-5: Report mapping for k=4
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_0000 |
Δpath < -8168 |
Tc |
path_0001 |
-8168 ≤ Δpath < -8152 |
Tc |
path_0002 |
-8152 ≤ Δpath < -8136 |
Tc |
… |
… |
… |
path_511 |
-8 ≤ Δpath < 8 |
Tc |
… |
… |
… |
path_1020 |
8136 ≤ Δpath < 8152 |
Tc |
path_1021 |
8152 ≤ Δpath < 8168 |
Tc |
path_1022 |
8168 ≤ Δpath |
Tc |
Table 10.1.23.3.3-6: Report mapping for k=5
Reported Quantity Value, path_i |
Measured Quantity Value, Δpath |
Unit |
path_000 |
Δpath < -8160 |
Tc |
path_001 |
-8160 ≤ Δpath < -8128 |
Tc |
path_002 |
-8128 ≤ Δpath < -8096 |
Tc |
… |
… |
… |
path_256 |
0 ≤ Δpath < 32 |
Tc |
… |
… |
… |
path_509 |
8096 ≤ Δpath < 8128 |
Tc |
path_510 |
8128 ≤ Δpath < 8160 |
Tc |
path_511 |
8160 ≤ Δpath |
Tc |
4.16 DL-AoD test conditions
4.16.1 Simulated cells
For the DL-AoD measurement test cases in clause 16, a multi cell environment as defined in 3GPP TS 38.508-1 [45] with NR Cell 1 and NR Cell 2 are used. The default parameters for simulated cells are the same as specified in 3GPP TS 38.508-1 [45].
4.16.2 Propagation conditions
See TS 38.533 [47] clause C 2.
4.16.3 Measurement Reporting Requirements
The measurement reporting delay is defined as the time between the moment when the periodic measurement report is triggered and the moment when the UE starts to transmit the measurement report over the air interface. This requirement assumes that that the measurement report is not delayed by other LPP signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is: 2 x TTIDCCH where TTIDCCH is the duration of subframe or slot or subslot when the measurement report is transmitted on the PUSCH with subframe or slot or subslot duration. This measurement reporting delay excludes any delay caused by no UL resources for UE to send the measurement report.
4.16.4 Measurement Period Requirements
When the physical layer receives NR-DL-AoD-ProvideAssistanceData message and NR-DL-AoD-RequestLocationInformation message from LMF via LPP [49], the UE shall be able to measure multiple (up to the UE capability specified in TS 38.133 [50] Clause 9.9.3.3) PRS-RSRP measurements, defined in TS 38.215 [57], from configured PRS resources for configured TRPs on configured positioning frequency layers, within ms.
where
i is the index of positioning frequency layer,
L is total number of positioning frequency layers,
is the periodicity of the PRS-RSRP measurement in positioning frequency layer i.
where
is the carrier specific scaling factor for PRS-RSRP measurements specified in TS 38.133 [50] clause 9.1.5.2,
is the scaling factor for Rx beam sweeping, and =1 if positioning frequency layer i is in FR1 and =8 if positioning frequency layer i is in FR2,
is the time duration of available PRS to be measured in the positioning frequency layer i to be measured during , and is calculated in the same way as PRS duration K defined in clause 5.1.6.5 of TS 38.214 [46]. For calculation of , only the PRS resources unmuted and fully or partially overlapped with MG are considered.
is the maximum number of DL PRS resources of positioning frequency layer i configured in a slot,
is UE capability combination per band where N is a duration of DL PRS symbols in ms corresponding to durationOfPRS-ProcessingSysmbols in TS 37.355 [49] processed every T ms corresponding to durationOfPRS-ProcessingSymbolsInEveryTms in TS 37.355 [49] for a given maximum bandwidth supported by UE corresponding to supportedBandwidthPRS in TS 37.355 [49],
is UE capability for number of DL PRS resources that it can process in a slot as indicated by maxNumOfDL-PRS-ResProcessedPerSlot in clause 6.4.3 of TS 37.355 [49],
is the number of PRS-RSRP measurement samples and = 4,
= + is the measurement duration for the last PRS-RSRP sample, including the sampling time and processing time,
is the periodicity of PRS-RSRP measurement in positioning frequency layer i,
corresponds to durationOfPRS-ProcessingSymbolsInEveryTms in TS 37.355 [49],
the least common multiple between and ,
is the maximum PRS resource periodicity among all PRS resources in positioning frequency layer i,
is the measurement gap repetition period in positioning frequency layer i.
If positioning frequency layer i has more than one DL PRS resource set with different PRS periodicities with muting, , the least common multiple of among the DL PRS resource sets is used to derive , where:
is the periodicity of PRS resource sets given by the higher-layer parameter DL-PRS-Periodicity.
is the scaling factor considering PRS resource muting. , where is the muting repetition factor given by the higher-layer parameter DL-PRS-MutingBitRepetitionFactor, and is the size of the bitmap .
Note: For the purpose of calculating TPRS,i, only the PRS resources fully or partially covered by the MG are considered.
When PRS-RSRP measurements are configured for DL-AoD, the time starts from the first MG instance aligned with DL PRS resources in the assistance data after both the NR-DL-AoD-RequestLocationInformation message and NR-DL-AoD-ProvideAssistanceData message from LMF via LPP [49] are delivered to the physical layer of UE.
Note: No per-positioning frequency layer requirement is applied in scenarios when multiple positioning frequency layers are configured.
When the PRS-RSRP measurement is configured together with RSTD measurement then the PRS-RSRP measurement shall meet the RSTD measurement requirements defined in TS 38.133 [50] clause 9.9.2.
When the PRS-RSRP measurement is configured together with UE Rx-Tx time difference measurement then the PRS-RSRP measurement shall meet the UE Rx-Tx time difference measurement requirements defined in TS 38.133 [50] clause 9.9.4.
If CSSF changes during the measurement period, the measurement period could be longer.
The measurement requirements do not apply for a PRS resource:
– if the PRS resource is across two sampling duration of N within duration or
– if time span of the PRS resource instance (including at least the minimum number of repetitions specified in the accuracy requirements) is greater than UE reported capability N.
If during the measurement period of one or more positioning frequency layers, the MG pattern is reconfigured either per UE request or not per UE request, the measurement period can be longer.
The requirements in this section apply, provided no PRS symbols are dropped during the measurement period within measurement gaps due to collisions with other signals; otherwise, a longer measurement period may be used.
The requirements in TS 38.133 [50] clause 9.9.3 do not apply if the PRS configuration given by higher layer parameters NR-DL-PRS-AssistanceData exceeds any of the UE measurement capabilities given by NR-DL-PRS-ResourcesCapability in NR-DL-AoD-ProvideCapabilities, and it is up to UE implementation which PRS resources are measured, subject to UE measurement capabilities.
If handover occurs while PRS-RSRP measurements are being performed then the UE shall complete the ongoing PRS-RSRP measurements session. The PRS-RSRP measurement period can be longer. The UE shall meet the PRS-RSRP measurement accuracy requirements in TS 38.133 [50] clause 10.1.24.
4.16.5 Measurement Accuracy Requirements
FFS
4.16.6 Reporting mapping
4.16.6.1 Absolute PRS-RSRP Measurement Report Mapping
The reporting range of absolute PRS-RSRP measurement is defined from -156 dBm to -31 dBm with 1 dB resolution.
The mapping of measured quantity is defined in Table 4.16.6.1-1. The range in the signalling may be larger than the guaranteed accuracy range.
Table 4.16.6.1-1: Measurement report mapping for PRS-RSRP
Reported value |
Measured quantity value |
Unit |
PRS_RSRP_0 |
PRS-RSRP<-156 |
dBm |
PRS_RSRP_1 |
-156≤PRS-RSRP<-155 |
dBm |
PRS_RSRP_2 |
-155≤PRS-RSRP<-154 |
dBm |
PRS_RSRP_3 |
-154≤PRS-RSRP<-153 |
dBm |
PRS_RSRP_4 |
-153≤PRS-RSRP<-152 |
dBm |
PRS_RSRP_5 |
-152≤PRS-RSRP<-151 |
dBm |
PRS_RSRP_6 |
-151≤PRS-RSRP<-150 |
dBm |
PRS_RSRP_7 |
-150≤PRS-RSRP<-149 |
dBm |
PRS_RSRP_8 |
-149≤PRS-RSRP<-148 |
dBm |
PRS_RSRP_9 |
-148≤PRS-RSRP<-147 |
dBm |
PRS_RSRP_10 |
-147≤PRS-RSRP<-146 |
dBm |
PRS_RSRP_11 |
-146≤PRS-RSRP<-145 |
dBm |
PRS_RSRP_12 |
-145≤PRS-RSRP<-144 |
dBm |
PRS_RSRP_13 |
-144≤PRS-RSRP<-143 |
dBm |
PRS_RSRP_14 |
-143≤PRS-RSRP<-142 |
dBm |
PRS_RSRP_15 |
-142≤PRS-RSRP<-141 |
dBm |
PRS_RSRP_16 |
-141≤PRS-RSRP<-140 |
dBm |
PRS_RSRP_17 |
-140≤PRS-RSRP<-139 |
dBm |
PRS_RSRP_18 |
-139≤PRS-RSRP<-138 |
dBm |
… |
… |
… |
PRS_RSRP_111 |
-46≤PRS-RSRP<-45 |
dBm |
PRS_RSRP_112 |
-45≤PRS-RSRP<-44 |
dBm |
PRS_RSRP_113 |
-44≤PRS-RSRP<-43 |
dBm |
PRS_RSRP_114 |
-43≤PRS-RSRP<-42 |
dBm |
PRS_RSRP_115 |
-42≤PRS-RSRP<-41 |
dBm |
PRS_RSRP_116 |
-41≤PRS-RSRP<-40 |
dBm |
PRS_RSRP_117 |
-40≤PRS-RSRP<-39 |
dBm |
PRS_RSRP_118 |
-39≤PRS-RSRP<-38 |
dBm |
PRS_RSRP_119 |
-38≤PRS-RSRP<-37 |
dBm |
PRS_RSRP_120 |
-37≤PRS-RSRP<-36 |
dBm |
PRS_RSRP_121 |
-36≤PRS-RSRP<-35 |
dBm |
PRS_RSRP_122 |
-35≤PRS-RSRP<-34 |
dBm |
PRS_RSRP_123 |
-34≤PRS-RSRP<-33 |
dBm |
PRS_RSRP_124 |
-33≤PRS-RSRP<-32 |
dBm |
PRS_RSRP_125 |
-32≤PRS-RSRP<-31 |
dBm |
PRS_RSRP_126 |
-31≤PRS-RSRP |
dBm |
4.16.6.2 Differential Report Mapping for PRS-RSRP Measurement
The reporting range of differential PRS-RSRP is defined from -30 dB to 0 dB with 1 dB resolution when nr-DL-AoD-RequestLocationInformation message is received.
The mapping of measured quantity is defined in Table 4.16.6.2-1. The range in the signalling may be larger than the guaranteed accuracy range.
The reporting range of differential PRS-RSRP is defined from -30 dB to 30 dB with 1 dB resolution when nr-DL-TDOA-RequestLocationInformation or nr-Multi-RTT-RequestLocationInformation is received.
The mapping of measured quantity is defined in Table 4.16.6.2-2. The range in the signalling may be larger than the guaranteed accuracy range or the range supported by the UE receiver for different ail[?] RSRP measured on different PRS resources in frequency domain at the same time.
Table 4.16.6.2-1: Measurement report mapping for differential PRS-RSRP
Reported value |
Measured quantity value |
Unit |
DIFFRSRP_0 |
-30≥ΔRSRP |
dB |
DIFFRSRP_1 |
-29≥ΔRSRP>-30 |
dB |
DIFFRSRP_2 |
-28≥ΔRSRP>-29 |
dB |
DIFFRSRP_3 |
-27≥ΔRSRP>-28 |
dB |
DIFFRSRP_4 |
-26≥ΔRSRP>-27 |
dB |
DIFFRSRP_5 |
-25≥ΔRSRP>-26 |
dB |
DIFFRSRP_6 |
-24≥ΔRSRP>-25 |
dB |
DIFFRSRP_7 |
-23≥ΔRSRP>-24 |
dB |
DIFFRSRP_8 |
-22≥ΔRSRP>-23 |
dB |
DIFFRSRP_9 |
-21≥ΔRSRP>-22 |
dB |
DIFFRSRP_10 |
-20≥ΔRSRP>-21 |
dB |
DIFFRSRP_11 |
-19≥ΔRSRP>-20 |
dB |
DIFFRSRP_12 |
-18≥ΔRSRP>-19 |
dB |
DIFFRSRP_13 |
-17≥ΔRSRP>-18 |
dB |
DIFFRSRP_14 |
-16≥ΔRSRP>-17 |
dB |
DIFFRSRP_15 |
-15≥ΔRSRP>-16 |
dB |
DIFFRSRP_16 |
-14≥ΔRSRP>-15 |
dB |
DIFFRSRP_17 |
-13≥ΔRSRP>-14 |
dB |
DIFFRSRP_18 |
-12≥ΔRSRP>-13 |
dB |
DIFFRSRP_19 |
-11≥ΔRSRP>-12 |
dB |
DIFFRSRP_20 |
-10≥ΔRSRP>-11 |
dB |
DIFFRSRP_21 |
-9≥ΔRSRP>-10 |
dB |
DIFFRSRP_22 |
-8≥ΔRSRP>-9 |
dB |
DIFFRSRP_23 |
-7≥ΔRSRP>-8 |
dB |
DIFFRSRP_24 |
-6≥ΔRSRP>-7 |
dB |
DIFFRSRP_25 |
-5≥ΔRSRP>-6 |
dB |
DIFFRSRP_26 |
-4≥ΔRSRP>-5 |
dB |
DIFFRSRP_27 |
-3≥ΔRSRP>-4 |
dB |
DIFFRSRP_28 |
-2≥ΔRSRP>-3 |
dB |
DIFFRSRP_29 |
-1≥ΔRSRP>-2 |
dB |
DIFFRSRP_30 |
0≥ΔRSRP>-1 |
dB |
Table 4.16.6.2-2: Measurement report mapping for differential PRS-RSRP
Reported value |
Measured quantity value |
Unit |
DIFFRSRP_0 |
-30≥ΔRSRP |
dB |
DIFFRSRP_1 |
-29≥ΔRSRP>-30 |
dB |
DIFFRSRP_2 |
-28≥ΔRSRP>-29 |
dB |
DIFFRSRP_3 |
-27≥ΔRSRP>-28 |
dB |
DIFFRSRP_4 |
-26≥ΔRSRP>-27 |
dB |
DIFFRSRP_5 |
-25≥ΔRSRP>-26 |
dB |
DIFFRSRP_6 |
-24≥ΔRSRP>-25 |
dB |
DIFFRSRP_7 |
-23≥ΔRSRP>-24 |
dB |
DIFFRSRP_8 |
-22≥ΔRSRP>-23 |
dB |
DIFFRSRP_9 |
-21≥ΔRSRP>-22 |
dB |
DIFFRSRP_10 |
-20≥ΔRSRP>-21 |
dB |
DIFFRSRP_11 |
-19≥ΔRSRP>-20 |
dB |
DIFFRSRP_12 |
-18≥ΔRSRP>-19 |
dB |
DIFFRSRP_13 |
-17≥ΔRSRP>-18 |
dB |
DIFFRSRP_14 |
-16≥ΔRSRP>-17 |
dB |
… |
… |
… |
DIFFRSRP_25 |
-5≥ΔRSRP>-6 |
dB |
DIFFRSRP_26 |
-4≥ΔRSRP>-5 |
dB |
DIFFRSRP_27 |
-3≥ΔRSRP>-4 |
dB |
DIFFRSRP_28 |
-2≥ΔRSRP>-3 |
dB |
DIFFRSRP_29 |
-1≥ΔRSRP>-2 |
dB |
DIFFRSRP_30 |
0≥ΔRSRP>-1 |
dB |
DIFFRSRP_31 |
1≥ΔRSRP>0 |
dB |
DIFFRSRP_32 |
2≥ΔRSRP>1 |
dB |
DIFFRSRP_33 |
3≥ΔRSRP>2 |
dB |
DIFFRSRP_34 |
4≥ΔRSRP>3 |
dB |
DIFFRSRP_35 |
5≥ΔRSRP>4 |
dB |
DIFFRSRP_36 |
6≥ΔRSRP>5 |
dB |
… |
… |
… |
DIFFRSRP_47 |
17≥ΔRSRP>16 |
dB |
DIFFRSRP_48 |
18≥ΔRSRP>17 |
dB |
DIFFRSRP_49 |
19≥ΔRSRP>18 |
dB |
DIFFRSRP_50 |
20≥ΔRSRP>19 |
dB |
DIFFRSRP_51 |
21≥ΔRSRP>20 |
dB |
DIFFRSRP_52 |
22≥ΔRSRP>21 |
dB |
DIFFRSRP_53 |
23≥ΔRSRP>-22 |
dB |
DIFFRSRP_54 |
24≥ΔRSRP>23 |
dB |
DIFFRSRP_55 |
25≥ΔRSRP>24 |
dB |
DIFFRSRP_56 |
26≥ΔRSRP>25 |
dB |
DIFFRSRP_57 |
27≥ΔRSRP>26 |
dB |
DIFFRSRP_58 |
28≥ΔRSRP>27 |
dB |
DIFFRSRP_59 |
29≥ΔRSRP>28 |
dB |
DIFFRSRP_60 |
30≥ΔRSRP>29 |
dB |
DIFFRSRP_61 |
ΔRSRP>30 |
dB |