9.2.5 TDD-TDD inter-frequency RSTD Accuracy
37.571-13GPPPart 1: Conformance test specificationRelease 16TSUser Equipment (UE) conformance specification for UE positioning
9.2.5.1 Test purpose
To verify that the Reference Signal Time Difference (RSTD) of TDD-TDD inter-frequency measurement accuracy is within the specified limit for all bands in AWGN channels
9.2.5.2 Test applicability
This test applies to all types of E-UTRA TDD UE release 10 and forward that support inter-frequency RSTD measurements except UE Category 1bis.
9.2.5.3 Minimum conformance requirements
This RSTD measurement is used for UE positioning purposes.
The accuracy of TDD-TDD inter-frequency RSTD measurement shall meet the requirement defined in the Table 9.2.4.3-1 without DRX as well as for all the DRX cycles specified in TS 36.331 [22].
The accuracy requirements in Table 9.2.4.3-1 are valid under the following conditions:
Conditions defined in TS 36.101 [2] Section 7.3 for reference sensitivity are fulfilled.
PRP 1,2|dBm according to clause E.3 for a corresponding Band
There are no measurement gaps overlapping with the PRS subframes in cells belonging to the serving carrier frequency.
The parameter expectedRSTDUncertainty signalled over LPP by E-SMLC as defined in TS 36.355 [4] is less than 5 µs.
The normative reference for this requirement is TS 36.133 [23] clause 9.1.10.2 and A.9.8.4.
9.2.5.4 Test description
9.2.5.4.1 Initial conditions
Test Environment: Normal; as defined in TS 36.508 [18] clause 4.1.
Frequencies to be tested: Mid Range, as defined in TS 36.508 [18] clause 4.3.1.2.
Channel bandwidth to be tested: 1.4 MHz (Test 1) and 10 MHz (Test 2). In the case that 1.4 MHz channel bandwidth is not defined for the operating band under test, as defined in TS 36.101 [2] clause 5.6.1, then this part of the test shall be omitted.
1. Connect the SS and AWGN noise sources to the UE antenna connector or antenna connectors as shown in Annex A, Figure A.3a for 4RX capable UE without any 2RX bands. Otherwise use Annex A figure A.3.
2. The general test parameter settings are set up according to Table 9.2.5.4.1-1.
3. Propagation conditions are set according to clause 4.7.2.1.
4. Message contents are defined in clause 9.2.5.4.3.
5. Two cells are on the different carrier frequencies. Cell 1 is the serving cell and OTDOA assistance data reference cell; Cell 2 is the neighbour cell. The assistance data neighbour cell list includes in total 15 cells, where 14 of the cells are not simulated (dummy cells; as defined in 3GPP TS 37.571‑5 [20], clause 7.2.2).
6. The true RSTD (which is the receive time difference for frame 0 between the two cells as seen at the UE antenna connector) is set to 92 Ts (about 3 s) between neighbour cell 2 and serving cell 1 for Test 1 and -92 Ts (about -3 s) for Test 2.
Note that the related expectedRSTD values to be signalled over LPP are defined in Table 9.2.5.4-1.
7. The gap pattern configuration # 0 as defined in Table 8.1.2.1-1 in 3GPP TS 36.133 [23] is configured and does not overlap with PRS subframes of Cell 1.
Table 9.2.5.4.1-1: General Test Parameters for inter-frequency RSTD Tests for E-UTRAN TDD-TDD
Parameter |
Unit |
Value |
Comment |
|
Test 1 |
Test 2 |
|||
PCFICH/PDCCH/PHICH parameters |
R.14 TDD |
R.6 TDD |
As specified in TS 36.521-3 [25] clause A.2.2. |
|
OCNG Patterns defined in TS 36.521-3 [25] clause D.2 |
OP.4 TDD |
OP.2 TDD |
OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols (other than those in the PRS subframes). |
|
Reference cell |
Cell 1 |
Cell 1 on RF channel number 1 |
||
Neighbour cell |
Cell 2 |
Cell 2 on RF channel number 2 |
||
E-UTRA RF Channel Number |
1,2 |
Two TDD carrier frequencies are used. |
||
Channel Bandwidth (BWchannel) |
MHz |
1.4 |
10 |
|
PRS Bandwidth Note 2 |
RB |
6 |
50 |
|
GapOffset |
34 |
13 |
For Cell 1 |
|
Gap Pattern ID |
0 |
For Cell 1 |
||
Special subframe configuration |
6 |
As specified in table 4.2-1 in TS 36.211 [26]. The same configuration in both cells. |
||
Uplink-downlink configuration |
3 |
1 |
As specified in table 4.2-2 in TS 36.211 [26] and table 9.1.2.3-2. The same configuration in both cells. |
|
PRS configuration Index |
Cell 1: 15 Cell 2: 35 |
Cell 1: 4 Cell 2: 14 |
As defined in 3GPP TS 36.211 [26] |
|
PRS subframe offset |
20 |
10 |
For Cell 2 |
|
Number of consecutive positioning downlink subframes |
6 |
1 |
As defined in 3GPP TS 36.211 [26] |
|
prs-MutingInfo Note 2 |
Cell 1:‘11110000’ Cell 2:‘11110000’ |
See section 6.5.1.2 in 3GPP TS 36.355 [4] for more information |
||
Cell IDNote 2 |
Cell 1: 0 Cell 2: 1 |
|||
Expected RSTDNote 1 |
μs |
Cell 2: 1 Other neighbour cells: randomly between -3 and 3 |
The expected RSTD is what is expected at the receiver. The corresponding parameter in the OTDOA assistance data specified in TS 36.355 [4] is the expectedRSTD indicator |
|
Expected RSTD uncertainty for all neighbour cells Note 1 |
μs |
5 |
The corresponding parameter in the OTDOA assistance data specified in TS 36.355 [4] is the expectedRSTD-Uncertainty index |
|
CP length Note 2 |
Normal |
|||
DRX |
OFF |
|||
Radio frame receive time offset between the cells at the UE antenna connector Note 3 |
μs |
Cell 2 to Cell 1: 3 |
Cell 2 to Cell 1: -3 |
PRS are transmitted from synchronous cells |
Number of cells provided in OTDOA assistance data |
16 |
The list includes the reference cell (received in OTDOA-ReferenceCellInfo [4]) on RF channel 1 and 15 other cells on RF channel 2, all received in OTDOA-ProvideAssistanceData [4]. |
||
|
ms |
5120 |
Derived according to the RSTD measurement requirements specified in Section 8.1.2.6.3 in TS 36.133 [23]. |
|
NOTE 1: Parameters “Expected RSTD” and “Expected RSTD uncertainty for all neighbour cells” are not settable parameters. These are parameters signalled in LPP only. For the values to be used in LPP see Table 9.2.5.4.3-4 and TS 37.571-5 [20], clause 7.2.2. NOTE 2: Parameters “PRS Bandwidth”, “PRS configuration index”, “Number of consecutive positioning downlink subframes”, “prs-MutingInfo”, “Cell ID” and “CP length” are settable parameters and also parameters signalled in LPP. For all the values to be used in LPP see Table 9.2.5.4.3-4 and TS 37.571-5 [20], clause 7.2.2. NOTE 3: The parameter “Radio frame receive time offset between the cells at the UE antenna connector” is not a settable parameter but is used to set the “true RSTD” values in step 6 of clause 9.2.5.4.1. NOTE 4: The parameter “ |
9.2.5.4.2 Test procedure
The test consists of a set-up period and a measurement period. Cell 1 and Cell 2 are both active during the complete test. The beginning of the measurement period shall be aligned with the first PRS positioning subframe of a positioning occasion in the reference cell.
NOTE: The information on when PRS is muted is conveyed to the UE using PRS muting information in the OTDOA assistance data.
The OTDOA-RequestLocationInformation message and the OTDOA assistance data as defined in clause 9.2.5.4.3 shall be provided to the UE during the set-up period. The last TTI containing the OTDOA-RequestLocationInformation message shall be provided to the UE ΔT ms before the start of the measurement period, where ΔT = 150 ms is the maximum processing time of the OTDOA-RequestLocationInformation message and the OTDOA assistance data in the UE.
1. Ensure that the UE is in state Generic RB Established State 3A-RF according to 3GPP TS 36.508 [18] clause 7.2A.3.
2. The SS shall send a RESET UE POSITIONING STORED INFORMATION message.
3. Set the parameters according to Table 9.2.5.5-1 as appropriate. Propagation conditions are set according to clause 4.7.2.1.
4. The SS shall transmit an RRCConnectionReconfiguration message with the measurement gap configuration.
5. The UE shall transmit RRCConnectionReconfigurationComplete message.
5a. The SS shall transmit an LPP REQUEST CAPABILITIES message.
5b. The UE shall transmit an LPP PROVIDE CAPABILITIES message indicating the OTDOA capabilities supported by the UE in the OTDOA-ProvideCapabilities IE.
6. The SS shall send a LPP PROVIDE ASSISTANCE DATA message, including the OTDOA‑ProvideAssistanceData IE. If the UE message at step 5b includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
7. The SS shall send a LPP REQUEST LOCATION INFORMATION message, including the OTDOA‑RequestLocationInformation IE such that the UE receives the message T ms before the start of the measurement period, where T = 150 ms.
8. The UE shall transmit a LPP PROVIDE LOCATION INFORMATION message, including the OTDOA‑ProvideLocationInformation IE.
9. If the UE message at step 8 includes the ackRequested IE set to TRUE, the SS shall send a LPP acknowledgement message.
10. The SS shall check the rstd value for Cell 2 in the OTDOA-SignalMeasurementInformation IE according to Table 9.2.5.5-2.
11. Repeat step 2-10 until the confidence level according to Annex D is achieved.
12. Repeat step 1-11 for each sub-test in Table 9.2.5.5-1 as appropriate.
9.2.5.4.3 Message contents
Table 9.2.5.4.3-1: RESET UE POSITIONING STORED INFORMATION
Derivation Path: 36.509 [11] clause 6.9 |
|||
Information Element |
Value/remark |
Comment |
Condition |
UE Positioning Technology |
0 0 0 0 0 0 0 1 |
OTDOA |
Table 9.2.5.4.3-2: MeasGapConfig-GP1: TDD-TDD inter-frequency RSTD Accuracy
Derivation Path: TS 36.508 [18] clause 4.6.6, Table 4.6.6-1A: MeasGapConfig-GP1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MeasGapConfig-GP1 ::= CHOICE { |
|||
setup SEQUENCE { |
|||
gapOffset CHOICE { |
|||
gp0 |
34 (Test 1) 13 (Test 2) |
TGRP = 40 ms |
|
} |
|||
} |
|||
} |
Table 9.2.5.4.3-2a: LPP Request Capabilities
Information Element |
Value/remark |
otdoa‑RequestCapabilities |
TRUE |
Table 9.2.5.4.3-3: LPP RequestLocationInformation
Derivation Path: 36.355 clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
initiator |
locationServer |
||
transactionNumber |
1 |
||
} |
|||
endTransaction |
FALSE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
requestLocationInformation-r9 SEQUENCE { |
|||
commonIEsRequestLocationInformation SEQUENCE { |
|||
locationInformationType |
locationMeasurementsRequired |
||
triggeredReporting |
Not present |
||
periodicalReporting |
Not present |
||
additionalInformation |
onlyReturnInformationRequested |
||
qos SEQUENCE { |
|||
horizontalAccuracy |
Not present |
||
verticalCoordinateRequest |
FALSE |
||
verticalAccuracy |
Not present |
||
responseTime SEQUENCE { |
|||
time |
6 |
See Note 4 of Table 9.2.5.4.1-1 |
|
responseTimeEarlyFix-r12 |
Not present |
Rel-12 onwards |
|
} |
|||
velocityRequest |
FALSE |
||
} |
|||
environment |
Not present |
||
locationCoordinateTypes |
Not present |
||
velocityTypes |
Not present |
||
} |
|||
a-gnss-RequestLocationInformation |
Not present |
||
otdoa-RequestLocationInformation SEQUENCE { |
|||
assistanceAvailability |
FALSE |
||
} |
|||
ecid-RequestLocationInformation |
Not present |
||
epdu-RequestLocationInformation |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 9.2.5.4.3-4: LPP ProvideAssistanceData
Derivation Path: 36.355 clause 6.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
LPP-Message ::= SEQUENCE { |
|||
transactionID SEQUENCE { |
|||
Initiator |
locationServer |
||
transactionNumber |
(0..255) |
||
} |
|||
endTransaction |
TRUE |
||
sequenceNumber |
Not present |
||
acknowledgement |
Not present |
||
lpp-MessageBody CHOICE { |
|||
c1 CHOICE { |
|||
provideAssistanceData SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE { |
|||
provideAssistanceData-r9 SEQUENCE { |
|||
commonIEsProvideAssistanceData |
Not present |
||
a-gnss-ProvideAssistanceData |
Not present |
||
otdoa-ProvideAssistanceData SEQUENCE { |
|||
otdoa-ReferenceCellInfo |
As defined in TS 37.571‑5 [20], clause 7.2.2. |
||
otdoa-NeighbourCellInfo |
As defined in TS 37.571‑5 [20], clause7.2.2. |
||
otdoa-Error |
Not present |
||
} |
|||
epdu-ProvideAssistanceData |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 9.2.5.4.3-5: LPP ProvideLocation Information
Derivation Path: 36.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
initiator |
locationServer |
|||
transactionNumber |
1 |
|||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
acknowledgement |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
Not present. |
|||
a-gnss-ProvideLocationInformation |
Not present |
|||
otdoa-ProvideLocationInformation |
||||
otdoaSignalMeasurementInformation |
||||
systemFrameNumber |
||||
physCellIdRef |
Cell 1 |
|||
cellGlobalIdRef |
||||
earfcnRef |
||||
referenceQuality |
||||
neighbourMeasurementList SEQUENCE (SIZE(1)) { |
||||
physCellIdNeighbor |
Cell 2 |
|||
cellGlobalIdNeighbour |
||||
earfcnNeighbour |
RF channel 2 |
|||
rstd |
Set according to Table 9.2.5.5-2 for each specific test |
|||
rstd-Quality |
||||
} |
||||
} |
||||
otdoa-Error |
May be present with error reason ‘undefined’ or ‘attemptedButUnableToMeasureSomeNeighbourCells’ |
|||
} |
||||
ecid-ProvideLocationInformation |
Not present |
|||
epdu-ProvideLocationInformation |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.2.5.4.3-6: CQI-ReportConfig-DEFAULT: TDD-TDD inter-frequency RSTD Accuracy
Derivation Path: TS 36.508 [18] clause 4.6.3, Table 4.6.3-2 CQI-ReportConfig-DEFAULT |
|||
Information Element |
Value/remark |
Comment |
Condition |
CQI-ReportConfig-DEFAULT ::= SEQUENCE { |
|||
cqi-ReportModeAperiodic |
rm30 |
This IE should be omitted for Test 1 |
|
nomPDSCH-RS-EPRE-Offset |
0 |
||
cqi-ReportPeriodic CHOICE { |
|||
release |
NULL |
||
} |
9.2.5.5 Test requirement
Table 9.2.5.5-1 defines the primary level settings including test tolerances for all tests.
The RSTD TDD-TDD inter frequency measurement accuracy test shall meet the reported values in Table 9.2.5.5-2.
Table 9.2.5.5-1: Cell Specific Test Parameters for inter frequency RSTD Tests for E-UTRAN TDD-TDD
Parameter |
Unit |
Test 1 |
Test 2 |
||
Cell 1 |
Cell 2 |
Cell 1 |
Cell 2 |
||
E-UTRA RF Channel Number |
1 |
2 |
1 |
2 |
|
PBCH_RA |
dB |
0 |
|||
PBCH_RB |
|||||
PSS_RA |
|||||
SSS_RA |
|||||
PCFICH_RB |
|||||
PHICH_RA |
|||||
PHICH_RB |
|||||
PDCCH_RA |
|||||
PDCCH_RB |
|||||
OCNG_RANote 1 |
|||||
OCNG_RBNote 1 |
|||||
PRS_RA |
dB |
-2.7 |
0.3 |
-2.7 |
0.3 |
|
dBm/15 kHz |
-98 |
|||
PRS |
dB |
-5.7 |
-12.7 |
-5.7 |
-12.7 |
PRS |
dB |
-5.7 |
-12.7 |
-5.7 |
-12.7 |
Io Note 3 |
dBm/1.08 MHz |
-79.24 |
-79.39 |
N/A |
N/A |
dBm/9 MHz |
N/A |
N/A |
-70.03 |
-70.18 |
|
PRP Note 3 |
dBm/15kHz |
-103.7 |
-110.7 |
-103.7 |
-110.7 |
|
dB |
-3 |
-13 |
-3 |
-13 |
RSRP Note 3 |
dBm/15kHz |
-101 |
-111 |
-101 |
-111 |
Propagation condition |
AWGN |
||||
Note 1: OCNG shall be used such that both cells are fully allocated and a constant total transmitted power spectral density is achieved for all OFDM symbols (other than those in the PRS subframes). Note 2: Interference from other cells and noise sources not specified in the test is assumed to be constant over subcarriers and time and shall be modelled as AWGN of appropriate power for Note 3: |
Table 9.2.5.5-2: RSTD TDD inter-frequency accuracy requirements for the reported values
Test 1 |
Test 2 |
|
Lowest reported value |
RSTD_6424 |
RSTD_6253 |
Highest reported value |
RSTD_6470 |
RSTD_6275 |
For the overall test to pass, the ratio of successful reported values in each sub-test shall be more than 90% with a confidence level of 95%. In the case that 1.4 MHz channel bandwidth is not defined for the operating band under test then Test 1 shall be omitted.