10.8 TDD RSTD Measurement Accuracy for 3DL Carrier Aggregation
37.571-13GPPPart 1: Conformance test specificationRelease 16TSUser Equipment (UE) conformance specification for UE positioning
10.8.1 Test purpose
To verify that the TDD RSTD measurement accuracy is within the specified limits.
10.8.2 Test applicability
This test applies to all types of E-UTRA TDD UE release 12 and forward that supports UE-assisted OTDOA for 3DL Carrier Aggregation.
10.8.3 Minimum conformance requirements
This section contains RSTD measurement accuracy requirements for a UE configured with one or two downlink SCell(s). The UE may operate in one of the E-UTRA carrier aggregations listed in TS 36.133 [23] section 8.3.1. The requirements in this section shall apply regardless of whether the configured downlink secondary cell is activated or deactivated by the MAC-CE command [34]. The requirements apply for bandwidths defined in the bandwidth combination set for the CA configurations supported by the UE defined in TS 36.101 [2].
The RSTD measurements, which are obtained when both the reference cell and neighbouring cell belong to the primary component carrier, shall meet the intra-frequency RSTD accuracy requirements defined in TS 36.133 [23] section 9.1.10.1.
The RSTD measurements, which are obtained when both the reference cell and neighbouring cell belong to the same secondary component carrier, shall meet the intra-frequency RSTD accuracy requirements defined in TS 36.133 [23] section 9.1.10.1.
The RSTD measurements, which are obtained when the reference cell and neighbouring cell do not belong to the same carrier, shall meet the inter-frequency RSTD accuracy requirements defined in TS 36.133 [23] section 9.1.10.2.
The normative reference for this requirement is TS 36.133 [23] clause 9.1.12 and A.9.8.15.
10.8.4 Test description
10.8.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.1.
Channel bandwidths to be tested: the largest and the smallest aggregated bandwidth combinations supported by the UE of the Channel bandwidths defined in Table 10.8.4.1-1. The Channel bandwidths for CA Intra-Band combinations are as defined in TS 36.508 [18] clause 4.3.1 and for CA Inter-Band combinations are defined in TS 36.521-1[24] clause 5.4.2A. In case of multiple possible Channel bandwidth combinations, the first combination listed in the above mentioned clauses shall be selected.
1. Connect the SS (node B emulator) and AWGN noise sources to the UE antenna connectors as follows:
– For UEs supporting only 2Rx in all the bands under test, use TS 36.508 [18] Annex A, Figure group A.68 as appropriate.
– For UEs supporting 4Rx in any of the bands under test use TS 36.508 [18] Annex A, Figure A.90. Use the 2Rx module for cells on bands supporting 2Rx and the 4Rx module for cells on bands supporting 4Rx.
2. The general test parameter settings are set up according to Table 10.8.4.1-1.
3. Propagation conditions are set according to clause 4.7.2.1.
4. Message contents are defined in clause 10.8.4.3.
5. There are four synchronized cells on three different carrier frequencies. Cell 1 is the PCell on primary component carrier F1 (RF channel number 1), Cell 2 is an SCell on secondary component carrier F2 (RF channel number 2), Cell 3 is an SCell and reference cell on secondary component carrier F3 (RF channel number 3), and Cell 4 is the neighbour cell on F3. PCell (Cell 1) is the cell used for connection setup with the power level and mapping set according to TS 36.521-1 [24] Annex C.0 and C.1 as appropriate for this test. Cell 2, Cell 3 and Cell 4 are powered OFF.
Cell 1, Cell 2, Cell 3, and Cell 4 are included in the OTDOA assistance data neighbour cell list.
The assistance data neighbour cell list includes in total 15 cells, where 12 of the cells are not simulated (dummy cells; as defined in 3GPP TS 37.571‑5 [20], clause 7.3.2).
Note that the measurement gap is not configured in the test because of UE carrier aggregation capability.
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 31 Ts (about 1 s) between Cell 1 and OTDOA assistance data reference cell, Cell 3, and set to -31 Ts (about -1 s) between Cell 2 and OTDOA assistance data reference cell, Cell 3, and set to 92 Ts (about 3 s) between neighbour Cell 4 and OTDOA assistance data reference cell, Cell 3.
Note that the related expectedRSTD values to be signalled over LPP are defined in Table 10.8.4.1-1.
Table 10.8.4.1-1: General Test Parameters for RSTD Test for E-UTRAN TDD for Carrier Aggregation
Parameter |
Unit |
Value |
Comment |
PCell |
Cell 1 |
Cell 1 on RF channel number 1 |
|
SCell 1 |
Cell 2 |
Cell 2 is an SCell on RF channel number 2 |
|
SCell 2 (Assistance data reference cell) |
Cell 3 |
Cell 3 is an SCell on RF channel number 3 |
|
Neighbour cell |
Cell 4 |
Cell 4 on RF channel number 3 |
|
Channel Bandwidth (BWchannel) |
MHz |
5,10,20 |
|
PRS Transmission Bandwidth (PRS transmission bandwidth depends on selected channel bandwidth) Note 2 |
RB |
5MHz: 25 10MHz: 50 20MHz:100 |
PRS are transmitted over the system bandwidth. PRS Bandwidth: bandwidth is as indicated in prs-Bandwidth in the OTDOA assistance data defined in 3GPP TS 36.355 [4]. |
PCFICH/PDCCH/PHICH parameters (PCFICH/PDCCH/PHICH parameters depend on selected channel bandwidth) |
5MHz: R.11 TDD 10MHz: R.6 TDD 20MHz: R.10 TDD |
As specified in TS 36.521-3 [25] clause A.2.1 |
|
OCNG Patterns defined in TS 36.521-3 [25] clause D.1 (There is no PDSCH allocated in the subframe transmitting PRS) (OCNG Patterns depend on selected channel bandwidth) |
5MHz: OP.10 TDD 10MHz: OP.2 TDD 20MHz: OP.8 TDD |
OCNG shall be used such that all 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). |
|
PRS configuration Index Note 2 |
171 for all cells on PCC 181 for all cells on SCC1 191 for all cells on SCC2 |
This corresponds to periodicity of 320 ms and PRS subframe offset of |
|
Number of consecutive positioning downlink subframes |
5MHz: 2 10MHz: 1 20MHz:1 |
As defined in 3GPP TS 36.211 [26] |
|
prs-SubframeOffset Note 2 |
Cells on PCC: 300 Cells on SCC1: 310 Cells on SCC2, except reference cell: 0 |
Subframe offset, counted in full subframes. The corresponding parameter in the OTDOA assistance data is prs-SubframeOffset specified in TS 36.355 [4] |
|
slotNumberOffset Note 2 |
Cells on PCC: 0 Cells on SCC1: 0 Cells on SCC2, except reference cell: 0 |
The slot number offset at the transmitter between a neighbour cell and the assistance data reference cell. The corresponding parameter in the OTDOA assistance data is slotNumberOffset specified in TS 36.355 [4]. |
|
prs-MutingInfo Note 2 |
Cell 1:‘11110000’ Cell 2:‘11110000’ Cell 3:’11110000’ Cell 4:’11110000’ |
See section 6.5.1.2 in 3GPP TS 36.355 [4] for more information |
|
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 |
1 |
As specified in table 4.2-2 in TS 36.211 [26] and table 8.1.2.5.2-2 in TS 36.133 [23]. The same configuration in both cells. |
|
Cell ID Note 2 |
(Cell ID of cell 4 – Cell ID of cell 3) mod 6 = 3 |
PCIs of cell 1 and cell 2 are selected randomly. |
|
Radio frame receive time offset between the cells at the UE antenna connector Note 3 |
μs |
Cell 1 to Cell 3: 1 Cell 2 to Cell 3: -1 Cell 4 to Cell 3: 3 |
PRS are transmitted from synchronous cells |
Expected RSTD Note 1 |
μs |
Cell 1: -2 Cell 2: 0 Cell 4: 2 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 |
||
Number of cells provided in OTDOA assistance data |
16 |
The list includes the assistance-data-reference cell and 15 other cells. Cell 1 and Cell 2 appear at random places in the first half of the neighbour cell list in the OTDOA assistance data. Cell 4 always appears at random places in the second half of the list. |
|
|
ms |
4960 |
Derived according to the RSTD measurement requirements specified in Section 10.6.3 |
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 10.8.4.3-3 and TS 37.571-5 [20], clause 7.3.2. NOTE 2: Parameters “PRS Transmission Bandwidth”, “PRS configuration index”, “Number of consecutive positioning downlink subframes”, “prs-SubframeOffset”, “slotNumberOffset”, “prs-MutingInfo”, “Cell ID” and “CP length” are settable parameters and also parameters signalled in LPP. The values to be used for “Cell ID” are as follows: Cell 1: 0, Cell 2: 3, Cell 3: 7, Cell 4: 10. For the values to be used in LPP see Table 10.8.4.3-3 and TS 37.571-5 [20], clause 7.3.2. NOTE 3: The parameter “Radio frame receive time offset between the cells at the UE antenna connector” is used to set the “true RSTD” value in step 6 of clause 10.8.4.1. NOTE 4: The parameter “ |
10.8.4.2 Test procedure
The RSTD measurements are performed:
– between Cell 4 and Cell 3 to verify the accuracy of RSTD measurement when the reference cell and neighbouring cell belong to the same secondary component carrier can meet the intra-frequency RSTD accuracy requirements defined in section 10.8.3.
– between Cell 1 and Cell 3 to verify the accuracy of RSTD measurement between the PCell and an SCell can meet the inter-frequency RSTD accuracy requirements defined in section 10.8.3.
– between Cell 2 and Cell 3 to verify the accuracy of RSTD measurement between two SCells can meet the inter-frequency RSTD accuracy requirements defined in section 10.8.3.
The test consists of a set-up period and a measurement period. All cells are 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 10.8.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. Configure Cell 2 on SCC1 and Cell 3 and Cell 4 on SCC2 according to TS 36.521-3 [25] Annex C.0 and C.1 for all downlink physical channels.
3. The SS shall configure the SCells (Cell 2 and Cell 3) on the SCCs as per TS 36.508 [18] clause 5.2A.4.
4. The SS activates the SCells (Cell 2 and Cell 3) by sending the Activation/Deactivation MAC control element according to TS 36.321 [34] clauses 5.13 and 6.1.3.8. Wait for at least 2 seconds as per TS 36.133 [23] clause 8.3.3.2.
5. The SS shall send a RESET UE POSITIONING STORED INFORMATION message.
6. Set the parameters according to Table 10.8.5-1 as appropriate. Propagation conditions are set according to clause 4.7.2.1.
6a. The SS shall send an LPP REQUEST CAPABILITIES message.
6b. The UE shall send an LPP PROVIDE CAPABILITIES message indicating the OTDOA capabilities supported by the UE in the OTDOA-ProvideCapabilities IE
7. The SS shall send a LPP PROVIDE ASSISTANCE DATA message, including the OTDOA‑ProvideAssistanceData IE. The position of Cell 1 in the OTDOA-NeighbourCellInfoList and the position of Cell 2 are randomly selected in the relevant sequence and the position of Cell 4 is randomly selected in the relevant sequence as described in 3GPP TS 37.571-5 [20], clause 7.3.2. If the UE message at step 6b includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
8. 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.
9. The UE shall transmit a LPP PROVIDE LOCATION INFORMATION message, including the OTDOA‑ProvideLocationInformation IE.
10. If the UE message at step 9 includes the ackRequested IE set to TRUE, the SS shall send a LPP acknowledgement message.
11. The SS shall check the rstd values for Cell 1, Cell 2 and Cell 4 in the OTDOA-SignalMeasurementInformation IE according to Table 10.8.5-2.
12. Repeat step 5-11 until the confidence level according to Annex D is achieved. For each iteration, at step 7 change the random positions of Cell 1 and Cell 2 and Cell 4 in the relevant sequence in the OTDOA-NeighbourCellInfoList.
13. Repeat complete test for the other channel bandwidth(s) supported by the UE (if any).
10.8.4.3 Message contents
Table 10.8.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 10.8.4.3-1a: LPP Request Capabilities
Information Element |
Value/remark |
otdoa‑RequestCapabilities |
TRUE |
Table 10.8.4.3-2: 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 10.8.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 |
|||
assistanceAvailability |
FALSE |
||
} |
|||
ecid-RequestLocationInformation |
Not present |
||
epdu-RequestLocationInformation |
Not Present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 10.8.4.3-3: 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.3.2. |
||
otdoa-NeighbourCellInfo |
As defined in TS 37.571‑5 [20], clause 7.3.2. |
||
otdoa-Error |
Not present |
||
} |
|||
epdu-ProvideAssistanceData |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 10.8.4.3-4: 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 3 |
|||
cellGlobalIdRef |
||||
earfcnRef |
||||
referenceQuality |
||||
neighbourMeasurementList SEQUENCE{ |
||||
NeighbourMeasurementElement SEQUENCE { |
||||
physCellIdNeighbour |
Cell 1 |
|||
cellGlobalIdNeighbour |
||||
earfcnNeighbour |
||||
rstd |
Set according to Table 10.8.5-2 |
With respect to Cell 3 |
||
rstd-Quality |
||||
} |
||||
NeighbourMeasurementElement SEQUENCE { |
||||
physCellIdNeighbour |
Cell 2 |
|||
cellGlobalIdNeighbour |
||||
earfcnNeighbour |
||||
rstd |
Set according to Table 10.8.5-2 |
With respect to Cell 3 |
||
rstd-Quality |
||||
} |
||||
NeighbourMeasurementElement SEQUENCE { |
||||
physCellIdNeighbour |
Cell 4 |
|||
cellGlobalIdNeighbour |
||||
earfcnNeighbour |
||||
rstd |
Set according to Table 10.8.5-2 |
With respect to Cell 3 |
||
rstd-Quality |
||||
} |
||||
} |
||||
} |
||||
otdoa-Error |
May be present with error reason ‘undefined’ or ‘attemptedButUnableToMeasureSomeNeighbourCells’ |
|||
} |
||||
ecid-ProvideLocationInformation |
Not present |
|||
epdu-ProvideLocationInformation |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
10.8.5 Test requirement
Table 10.8.5-1 defines the primary level settings including test tolerances for the test.
The TDD RSTD accuracy test shall meet the reported values in Table 10.8.5-2.
Table 10.8.5-1: Cell Specific Test Parameters for RSTD Test for E-UTRAN TDD for Carrier Aggregation
Parameter |
Unit |
Cell 1 |
Cell 2 |
Cell 3 |
Cell 4 |
E-UTRA RF Channel Number |
1 |
2 |
3 |
3 |
|
PBCH_RA |
dB |
0 |
0 |
0 |
0 |
PBCH_RB |
|||||
PSS_RA |
|||||
SSS_RA |
|||||
PCFICH_RB |
|||||
PHICH_RA |
|||||
PHICH_RB |
|||||
PDCCH_RA |
|||||
PDCCH_RB |
|||||
OCNG_RANote1 |
|||||
OCNG_RBNote1 |
|||||
PRS_RA |
dB |
-3 |
0 |
0.3 |
0.3 |
|
dBm/15 kHz |
-98 |
|||
PRS |
dB |
-6 |
-6 |
-5.7 |
-12.7 |
PRS |
dB |
-6 |
-6 |
-5.7 |
-12.7 |
Io Note3 |
dBm/9 MHz |
-70.04 +10log (NRB,c /50) |
-70.04 +10log (NRB,c /50) |
-69.99 +10log (NRB,c /50) |
-69.99 +10log (NRB,c /50) |
PRP Note3 |
dBm/15kHz |
-104 |
-104 |
-103.7 |
-110.7 |
RSRP Note3 |
dBm/15kHz |
-101 |
-104 |
-104 |
-111 |
|
dB |
-3 |
-6 |
-6 |
-13 |
Propagation condition |
AWGN |
||||
Note 1: OCNG shall be used such that all 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 10.8.5-2: RSTD TDD accuracy requirements for the reported values for Carrier Aggregation
Value Cell 1 |
Value Cell 2 |
Value Cell 4 |
|
Lowest reported value (depends on selected channel bandwidth) |
5MHz: RSTD_6374 10MHz: RSTD_6375 20MHz: RSTD_6376 |
5MHz: RSTD_6313 10MHz: RSTD_6314 20MHz: RSTD_6315 |
5MHz: RSTD_6440 10MHz: RSTD_6441 20MHz: RSTD_6442 |
Highest reported value(depends on selected channel bandwidth) |
5MHz: RSTD_6398 10MHz: RSTD_6397 20MHz: RSTD_6396 |
5MHz: RSTD_6337 10MHz: RSTD_6336 20MHz: RSTD_6335 |
5MHz: RSTD_6454 10MHz: RSTD_6453 20MHz: RSTD_6452 |
For the test to pass, the ratio of successful reported values shall be more than 90% with a confidence level of 95% for each of Cell 1, Cell 2 and Cell 4 for each supported channel bandwidth.