9.3.18 E-UTRAN TDD intra-frequency RSTD measurement period test case in CE Mode B with longer PRS occasions
37.571-13GPPPart 1: Conformance test specificationRelease 16TSUser Equipment (UE) conformance specification for UE positioning
9.3.18.1 Test purpose
To verify that the RSTD measurement reporting delay with longer PRS occasions for UE Category M1 and M2 meets the performance requirements in normal coverage mode in an environment with fading propagation conditions.
9.3.18.2 Test applicability
This test applies to E-UTRA TDD UE Category M1 and M2 release 15 and forward that supports UE-assisted OTDOA and dense PRS configuration or additional PRS configuration and CE Mode B. Test 2 is applicable only to UE Category M2.
9.3.18.3 Minimum conformance requirements
Same as in clause 9.3.4.1.3
The normative reference for this requirement is TS 36.133 [23] clause 8.13.3.3.2, 8.16.3.3.2 and A.8.12.14.
9.3.18.4 Test description
9.3.18.4.1 Initial conditions
Same as in clause 9.3.13.4.1 but replacing Table 9.3.13.4.1-1 with Table 9.3.18.4.1-1
Table 9.3.18.4.1-1: General test parameters
|
Parameter |
Unit |
Value |
Comment |
|
|
Test 1 |
Test 2 |
|||
|
Reference cell |
Cell 1 |
Reference cell is the cell in the OTDOA assistance data with respect to which the RSTD measurement is defined, as specified in 3GPP TS 36.214 [6] and 3GPP TS 36.355 [4]. The reference cell is the serving cell in this test case. |
||
|
Neighbour cells |
Cell 2 and Cell 3 |
Cell 2 and Cell 3 appear at random places in the neighbour cell list in the OTDOA assistance data, but Cell 2 always appears in the first half of the list, whilst Cell 3 appears in the second half of the list. |
||
|
MPDCCH |
DL Reference Measurement Channel R.16 TDD |
As specified in TS 36.521-3 [25] clause A.7.1 |
||
|
mPDCCH-startSF-UESS |
10 |
Parameter G in which determines subframe k0 in which MPDCCH starts
|
||
|
Channel Bandwidth (BWchannel) |
MHz |
10 |
||
|
PRS Transmission Bandwidth Note 2 |
RB |
6 |
24 |
PRS are transmitted in the centre RBs |
|
PRS configuration index |
624 |
This corresponds to periodicity of 320 ms and PRS subframe offset of |
||
|
Gap pattern Id |
rstd15 |
rstd10 |
As specified in TS 36.133 [23] Table 8.1.2.1-3. Applies for measurements on Cell 1, Cell 2, and Cell 3 |
|
|
Gap offset |
143 |
As specified in TS 36.331 [22], Clause 6.3.5 |
||
|
Number of consecutive downlink positioning subframes |
30 |
8 |
As defined in 3GPP TS 36.211 [26]. The number of subframes in a positioning occasion. Corresponds to parameter add-numDL-Frames in TS 36.355 [4], for UE with additional-prs-config capability |
|
|
40 |
10 |
As defined in 3GPP TS 36.211 [26]. The number of subframes in a positioning occasion. Corresponds to parameter add-numDL-Frames in TS 36.355 [4], for UE with densePrsConfig capability |
||
|
Physical cell ID PCI Note 2 |
(PCI of Cell 1 – PCI of Cell 2)mod6=0 and (PCI of Cell 1 – PCI of Cell 3)mod6=0 |
The cell PCIs are selected such that the relative shifts of PRS patterns among cells are as given by the test parameters |
||
|
TDD uplink-downlink configuration |
2 |
1 |
As specified in TS 36.211 [16], Clause 4.2; corresponds to a configuration with 5 ms switch-point periodicity and two downlink consecutive subframes |
|
|
TDD special subframe configuration |
6 |
As specified in TS 36.211 [16], Clause 4.2; corresponds to DwPTS of |
||
|
Radio frame receive time offset between the cells at the UE antenna connector Note 3 |
μs |
Cell 2 to Cell 1: 1 Cell 3 to Cell 1: -1 |
PRS are transmitted from synchronous cells |
|
|
Expected RSTD Note 1 |
μs |
Cell 2: 3 Cell 3: 3 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 |
|
|
Number of cells provided in OTDOA assistance data |
16 |
Including the reference cell |
||
|
PRS muting info Note 2 |
Cell 1: ‘11110000’ Cell 2: ‘00001111’ Cell 3: ‘11110000’ |
Corresponds to prs-MutingInfo defined in TS 36.355 [4] |
||
|
T1 |
s |
3 |
The length of the time interval from the beginning of each test |
|
|
T2 |
s |
2.56 |
The length of the time interval that follows immediately after time interval T1 |
|
|
T3 |
s |
2.56 |
The length of the time interval that follows immediately after time interval T2 |
|
|
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.3.18.4.3-5 and TS 37.571-5 [20], clause 7.2.5. Note 2: Parameters “PRS Transmission Bandwidth”, “PRS configuration index”, “Number of consecutive downlink positioning subframes”, “Physical cell ID PCI”, “CP length”, and “PRS muting info” are settable parameters and also parameters signalled in LPP. The values to be used for “Physical cell ID PCI” are as follows: Cell 1: 0, Cell 2: 6, Cell 3: 12. For all the values to be used in LPP see Table 9.3.18.4.3-5 and TS 37.571-5 [20], clause 7.2.5. 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.3.18.4.1. Note 4: If the PRS transmission bandwidth is larger than the UE RF bandwidth, the UE is measuring RSTD within its RF bandwidth. |
||||
Note 2
DL subframes, as defined in 3GPP TS 36.211 [26], Table 6.10.4.3-1
Note 2
and UpPTS of 
Table 9.3.18.4.1-2: DRX parameters
|
Field |
Value |
Comment |
|
onDurationTimer |
psf1 |
As specified in 3GPP TS 36.331 [22], clause 6.3.2 |
|
drx-InactivityTimer |
psf1 |
|
|
drx-RetransmissionTimer |
sf1 |
|
|
longDRX-CycleStartOffset |
sf320 |
|
|
shortDRX |
Disable |
9.3.18.4.2 Test procedure
Same as in clause 9.3.13.4.2 but with the following additional step:
14. Repeat step 1-13 for each sub-test in Table 9.3.18.4.1-1 as appropriate
9.3.18.4.3 Message contents
Same as in clause 9.3.1.1.4.3 with the following exceptions:
Table 9.3.18.4.3-1: LPP RequestLocationInformation
|
Derivation Path: Table 9.3.1.1.4.3-4 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
|||
|
lpp-MessageBody CHOICE { |
|||
|
c1 CHOICE { |
|||
|
requestLocationInformation SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
requestLocationInformation-r9 SEQUENCE { |
|||
|
commonIEsRequestLocationInformation SEQUENCE { |
|||
|
qos SEQUENCE { |
|||
|
responseTime SEQUENCE { |
|||
|
time |
6 |
See clause 9.3.18.5 |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
9.3.18.5 Test requirement
Table 9.3.3.1.5-1 and 9.3.3.1.5-2 define the primary level settings including test tolerances for the test.
The response time including test tolerance is 6300ms. The response time is equal to the LPP time IE value plus the test tolerance. The LPP time IE value is derived from the RSTD reporting delay plus ΔT, where ΔT = Nrepx TTIDCCH = Nrepx 75 ms, giving a value of 5285 ms. This is rounded up to the next allowed LPP value of 6 seconds. The RSTD measurement reporting delay in the test is derived from the following expression 
+TMIB, where TPRS=640ms, M=8, 
= 
and 
=16 are the parameters specified in clause 9.3.13.3, Table 9.3.1.1.3‑1 and Note 4 of Table 9.3.13.4.1-1. This gives the total RSTD reporting delay of 5210 ms for the 15 neighbour cells including Cell 2 and Cell 3 with respect to the reference cell, Cell 1.
The test tolerances are defined in clauses C.1.3 and C4.
The rate of successful tests during repeated tests shall be at least 90% with a confidence level of 95%.