7 E-UTRA A-GNSS minimum performance requirements
37.571-13GPPPart 1: Conformance test specificationRelease 16TSUser Equipment (UE) conformance specification for UE positioning
7.0 General
This clause defines the minimum performance requirements for both UE based and UE assisted A-GNSS FDD and TDD E-UTRA UEs. If a UE supports both UE based and UE assisted modes then it shall be tested in both modes.
7.1 Sensitivity
7.1.1 Sensitivity Coarse time assistance
7.1.1.1 Sub-tests
This test includes sub-tests dependent on the GNSS supported by the UE. Each sub-test is identified by a Sub-Test Number as defined in Table 7.1.1.1
Table 7.1.1.1: Sub-Test Number Definition
Sub-Test Number |
Supported GNSS |
1 |
UE supporting A-GPS L1 C/A |
2 |
UE supporting A-GLONASS |
3 |
UE supporting A-Galileo |
4 |
UE supporting A-GPS and Modernized GPS |
5 |
UE supporting A-GPS and A-GLONASS (Note) |
8 |
UE supporting A-GPS and A-Galileo (Note) |
9 |
UE supporting A-BDS |
10 |
UE supporting A-GPS and A-BDS (Note) |
11 |
UE supporting A-GPS and A-GLONASS and A-BDS (Note) |
12 |
UE supporting A-GPS and A-Galileo and A-GLONASS (Note) |
13 |
UE supporting A-GPS and A-Galileo and A-BDS (Note) |
Note: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |
7.1.1.2 Test purpose
To verify the performance of the first position estimate, when the UE is provided with only coarse time assistance.
7.1.1.3 Test applicability
This test applies to all types of E-UTRA UE that supports A-GNSS except Category M1 and Category M2 devices that do not support VoLTE.
7.1.1.4 Minimum conformance requirements
The first fix position estimates shall meet the accuracy and response time requirements in table 7.1.1.2 for the parameters specified in table 7.1.1.3 or 7.1.1.4.
Table 7.1.1.2: Requirements for Sensitivity Coarse time assistance
Success rate |
2-D position error |
Max response time |
---|---|---|
95 % |
100 m |
20 s |
Table 7.1.1.3: Parameters for Sensitivity Coarse time assistance – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
8 |
HDOP Range |
– |
1.1 to 1.6 |
Propagation conditions |
– |
AWGN |
GPS Coarse time assistance error range |
seconds |
±2 |
GPS L1 C/A Signal for one satellite |
dBm |
-142 |
GPS L1 C/A Signal for remaining satellites |
dBm |
-147 |
Table 7.1.1.4: Parameters for Sensitivity Coarse time assistance – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.1.1.5 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP range |
1.4 to 2.1 |
||
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±2 |
|
Galileo |
Reference high signal power level |
dBm |
-142 |
Reference low signal power level |
dBm |
-147 |
|
GPS(1) |
Reference high signal power level |
dBm |
-142 |
Reference low signal power level |
dBm |
-147 |
|
GLONASS |
Reference high signal power level |
dBm |
-142 |
Reference low signal power level |
dBm |
-147 |
|
BDS |
Reference high signal power level |
dBm |
-136 |
Reference low signal power level |
dBm |
-145 |
|
NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.1.1.5: Power level and satellite allocation
Satellite allocation for each constellation |
||||
GNSS-1(1) |
GNSS-2 |
GNSS-3 |
||
Single constellation |
High signal level |
1 |
– |
– |
Low signal level |
5 |
– |
– |
|
Dual constellation |
High signal level |
1 |
– |
– |
Low signal level |
2 |
3 |
– |
|
Triple constellation |
High signal level |
1 |
– |
– |
Low signal level |
2 |
2 |
2 |
|
Note 1: Up to Rel-14: for GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS. |
The normative reference for this requirement is TS 36.171 [3] clause 5.1.1 and 6.1.1.
7.1.1.5 Test description
7.1.1.5.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
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.
Channel Bandwidth to be tested: as defined in TS 36.508 [18] clause 4.3.1.
1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in Annex A.
2. Set the GNSS test parameters as specified in table 7.1.1.6 or 7.1.1.7 for GNSS scenario #1 in TS 37.571-5 [20]. For GNSS-1, select the first satellite SV ID defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20] for the one satellite with the higher level.
3. The parameter settings for the cell are set up according to TS 36.508 [18] clause 4.4.3, single cell scenario.
4. Switch on the UE.
5. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
7.1.1.5.2 Test procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 37.571-5 [20] with the UE location randomly selected to be within 3 km of the Reference Location and the altitude of the UE randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in clause 6.2.1.2.6 of TS 37.571-5 [20]
2. Send a RESET UE POSITIONING STORED INFORMATION message.
3. Depending on how the LPP session is performed:
– In the case of C-Plane, the SS shall send an LPP REQUEST CAPABILITIES message.
– In the case of U-Plane, the SS shall establish a SUPL session with the UE for positioning.
4. The UE returns an LPP PROVIDE CAPABILITIES message indicating the assistance data supported by the UE in the Assistance Data Support List in the A GNSS Provide Capabilities IE.
5. Send an LPP PROVIDE ASSISTANCE DATA message to provide the assistance data that is supported by the UE as indicated in step 4 and in accordance with clause 6.2.6 of TS 37.571-5 [20], and with the values defined in clause 6.2.7 of TS 37.571-5 [20] with the value of GNSS Reference Time offset by a random value as specified in clause 6.2.7.2 of TS 37.571-5 [20]. If the LPP session is performed over C-Plane, then if the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
6. Send an LPP REQUEST LOCATION INFORMATION message to obtain a fix.
7. If the UE returns a valid result in the LPP PROVIDE LOCATION INFORMATION message within the Max response time specified in table 7.1.1.9 then record the result and process it as specified in step 8. If the UE does not return a valid result within the Max response time specified in table 7.1.1.9 or reports an Error in the LPP PROVIDE LOCATION INFORMATION message then record one Bad Result.
7a. If the UE message at step 7 includes the ackRequested IE set to TRUE, then the SS shall send a LPP acknowledgment message.
8. For UE based testing compare the reported Location Information in the LPP PROVIDE LOCATION INFORMATION message against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.1.1.9 and record one Good Result or Bad Result as appropriate; or
For UE assisted testing convert the GNSS Signal Measurement Information reported in the LPP PROVIDE LOCATION INFORMATION message to a 2D position using the method described in clause 4.4.3 and then compare the result against the simulated position of the UE, used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.1.1.9 and record one Good Result or Bad Result as appropriate.
9. Repeat steps 1 to 8 using GNSS scenario #2 instead of #1 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. For GNSS-1, select the first satellite SV ID defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20] for the one satellite with the higher level. Use new random values for the UE location and altitude in step 1 and for the GNSS Reference Time offset in step 5.
10. Repeat steps 1 to 9 until the statistical requirements of clause 7.1.1.6 are met. Each time scenario #1 or #2 is used, the start time of the GNSS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again. Each time scenario #1 or #2 is used, for GNSS-1 select the next satellite SV ID from the one used previously, defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20], for the one satellite with the higher level.
11. Release the signalling connection.
7.1.1.5.3 Message contents
Message contents are according to TS 36.508 [18] clauses 4.6 and 4.7 and as follows:
RESET UE POSITIONING STORED INFORMATION
Information Element |
Value/remark |
UE POSITIONING TECHNOLOGY |
AGNSS |
LPP REQUEST CAPABILITIES
Information Element |
Value/remark |
a‑gnss‑RequestCapabilities |
TRUE |
LPP REQUEST LOCATION INFORMATION
Information Element |
Value/remark |
Comment |
commonIEsRequestLocationInformation |
||
> locationInformationType |
‘locationEstimateRequired’ or ‘locationMeasurementsRequired’ |
Depending on test case and UE capabilities, i.e. support for UE-based or UE-assisted |
> additionalInformation |
‘onlyReturnInformationRequested’ |
|
> qos |
||
>> horizontalAccuracy |
‘19’ (51.2m) |
|
>> verticalCoordinateRequest |
FALSE |
|
>> responseTime |
||
>>>time |
‘20’ |
|
a-gnss-RequestLocationInformation |
||
> gnss-PositioningInstructions |
||
>> gnssMethods |
||
>>> gnss-ids |
Sub-test 1: ‘gps’ Sub-test 2: ‘glonass’ Sub-test 3: ‘galileo’ Sub-test 4: ‘gps’ Sub-test 5: ‘gps’ and ‘glonass’ Sub-test 8: ‘gps’ and ‘galileo’ Sub-test 9: ‘bds’ Sub-test 10: ‘gps’and’bds’ Sub-test 11: ‘gps’ and ‘glonass’ and ‘bds’ Sub-test 12: ‘gps’ and ‘galileo’ and ‘glonass’ Sub-test 13: ‘gps’ and ‘galileo’ and ‘bds’ |
|
>> fineTimeAssistanceMeasReq |
FALSE |
|
>> adrMeasReq |
FALSE |
|
>> multiFreqMeasReq |
TRUE or FALSE |
Depending on UE capabilities |
>> assistanceAvailability |
FALSE |
7.1.1.6 Test requirement
For the parameters specified in table 7.1.1.6 or 7.1.1.7 the UE shall meet the requirements and the success rate specified in table 7.1.1.9 with a confidence level of 95% according to Annex D.
Table 7.1.1.6: Test parameters for Sensitivity Coarse time assistance – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
8 |
HDOP Range |
– |
1.1 to 1.6 |
Propagation conditions |
– |
AWGN |
GPS Coarse Time assistance error range |
seconds |
±1.8 |
GPS L1 C/A Signal for one satellite |
dBm |
-141 |
GPS L1 C/A Signal for remaining satellites |
dBm |
-146 |
Table 7.1.1.7: Test parameters for Sensitivity Coarse time assistance – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.1.1.8 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP range |
1.4 to 2.1 |
||
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±1.8 |
|
Galileo |
Reference high signal power level |
dBm |
-141 |
Reference low signal power level |
dBm |
-146 |
|
GPS(1) |
Reference high signal power level |
dBm |
-141 |
Reference low signal power level |
dBm |
-146 |
|
GLONASS |
Reference high signal power level |
dBm |
-141 |
Reference low signal power level |
dBm |
-146 |
|
BDS |
Reference high signal power level |
dBm |
-135 |
Reference low signal power level |
dBm |
-144 |
|
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.1.1.8: Power level and satellite allocation
Satellite allocation for each constellation |
||||
GNSS-1(1) |
GNSS-2 |
GNSS-3 |
||
Single constellation |
High signal level |
1 |
– |
– |
Low signal level |
5 |
– |
– |
|
Dual constellation |
High signal level |
1 |
– |
– |
Low signal level |
2 |
3 |
– |
|
Triple constellation |
High signal level |
1 |
– |
– |
Low signal level |
2 |
2 |
2 |
|
Note 1: Up to Rel-14: for GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS. |
Table 7.1.1.9: Test requirements for Sensitivity Coarse Time Assistance
System |
Success rate |
2-D position error |
Max response time |
---|---|---|---|
All |
95 % |
101.3 m |
20.3 s |
7.1.2 Sensitivity Fine time assistance
7.1.2.1 Sub-tests
This test includes sub-tests dependent on the GNSS supported by the UE. Each sub-test is identified by a Sub-Test Number as defined in Table 7.1.2.1
Table 7.1.2.1: Sub-Test Number Definition
Sub-Test Number |
Supported GNSS |
1 |
UE supporting A-GPS L1 C/A |
2 |
UE supporting A-GLONASS |
3 |
UE supporting A-Galileo |
4 |
UE supporting A-GPS and Modernized GPS |
5 |
UE supporting A-GPS and A-GLONASS (Note) |
8 |
UE supporting A-GPS and A-Galileo (Note) |
9 |
UE supporting A-BDS |
10 |
UE supporting A-GPS and A-BDS (Note) |
11 |
UE supporting A-GPS and A-GLONASS and A-BDS (Note) |
12 |
UE supporting A-GPS and A-Galileo and A-GLONASS (Note) |
13 |
UE supporting A-GPS and A-Galileo and A-BDS (Note) |
Note: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |
7.1.2.2 Test purpose
To verify the performance of the first position estimate, when the UE is additionally provided with fine time assistance.
7.1.2.3 Test applicability
This test applies to all types of E-UTRA UE that supports A-GNSS and that is capable of providing an enhanced performance when the network provides Fine Time Assistance, except Category M1 and Category M2 devices that do not support VoLTE.
7.1.2.4 Minimum conformance requirements
The first fix position estimates shall meet the accuracy and response time requirements in table 7.1.2.2 for the parameters specified in table 7.1.2.3 or 7.1.2.4.
Table 7.1.2.2: Requirements for Sensitivity Fine time assistance
Success rate |
2-D position error |
Max response time |
---|---|---|
95 % |
100 m |
20 s |
Table 7.1.2.3: Parameters for Sensitivity Fine time assistance – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
8 |
HDOP Range |
– |
1.1 to 1.6 |
Propagation conditions |
– |
AWGN |
GPS Coarse time assistance error range |
seconds |
±2 |
GPS L1 C/A Fine time assistance error range |
μs |
±10 |
GPS L1 C/A Signal for all satellites |
dBm |
-147 |
Table 7.1.2.4: Parameters for Sensitivity Fine time assistance – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.1.2.5 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP range |
1.4 to 2.1 |
||
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±2 |
|
GNSS fine time assistance error range |
s |
±10 |
|
Galileo |
Reference signal power level |
dBm |
-147 |
GPS(1) |
Reference signal power level |
dBm |
-147 |
GLONASS |
Reference signal power level |
dBm |
-147 |
BDS |
Reference signal power level |
dBm |
-147 |
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.1.2.5: Satellite allocation
Satellite allocation for each constellation |
|||
GNSS-1 |
GNSS-2 |
GNSS-3 |
|
Single constellation |
6 |
– |
– |
Dual constellation |
3 |
3 |
– |
Triple constellation |
3 |
2 |
2 |
The normative reference for this requirement is TS 36.171 [3] clause 5.1.2 and 6.1.2.
7.1.2.5 Test description
7.1.2.5.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
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.
Channel Bandwidth to be tested: as defined in TS 36.508 [18] clause 4.3.1.
1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in Annex A.
2. Set the GNSS test parameters as specified in table 7.1.2.6 or 7.1.2.7 for GNSS scenario #1 in TS 37.571-5 [20].
3. The parameter settings for the cell are set up according to TS 36.508 [18] clause 4.4.3, single cell scenario.
4. Switch on the UE.
5. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
7.1.2.5.2 Test procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 37.571-5 [20] with the UE location randomly selected to be within 3 km of the Reference Location and the altitude of the UE randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in clause 6.2.1.2.6 of TS 37.571-5 [20]
2. Send a RESET UE POSITIONING STORED INFORMATION message.
3. Depending on how the LPP session is performed:
– In the case of C-Plane, the SS shall send an LPP REQUEST CAPABILITIES message.
– In the case of U-Plane, the SS shall establish a SUPL session with the UE for positioning.
4. The UE returns an LPP PROVIDE CAPABILITIES message indicating the assistance data supported by the UE in the Assistance Data Support List in the A GNSS Provide Capabilities IE.
5. Send an LPP PROVIDE ASSISTANCE DATA message to provide the assistance data that is supported by the UE as indicated in step 4 and in accordance with clause 6.2.6 of TS 37.571-5 [20], and with the values defined in clause 6.2.7 of TS 37.571-5 [20] with the value of GNSS Reference Time and GNSS Reference Time for one cell offset by a random value as specified in clause 6.2.7.2 of TS 37.571-5 [20]. If the LPP session is performed over C-Plane, then if the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
6. Send an LPP REQUEST LOCATION INFORMATION message to obtain a fix.
7. If the UE returns a valid result in the LPP PROVIDE LOCATION INFORMATION message within the Max response time specified in table 7.1.2.9 then record the result and process it as specified in step 8. If the UE does not return a valid result within the Max response time specified in table 7.1.2.9 or reports an Error in the LPP PROVIDE LOCATION INFORMATION message then record one Bad Result.
7a. If the UE message at step 7 includes the ackRequested IE set to TRUE, then the SS shall send a LPP acknowledgment message.
8. For UE based testing compare the reported Location Information in the LPP PROVIDE LOCATION INFORMATION message against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.1.2.9 and record one Good Result or Bad Result as appropriate; or
For UE assisted testing convert the GNSS Measurement Information reported in the LPP PROVIDE LOCATION INFORMATION message to a 2D position using the method described in clause 4.4.3 and then compare the result against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.1.2.9 and record one Good Result or Bad Result as appropriate.
9. Repeat steps 1 to 8 using GNSS scenario #2 instead of #1 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. Use new random values for the UE location and altitude in step 1 and for the GNSS Reference Time GNSS Reference Time for one cell offsets in step 5.
10. Repeat steps 1 to 9 until the statistical requirements of clause 7.1.2.6 are met. Each time scenario #1 or #2 is used, the start time of the GNSS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again.
11. Release the signalling connection.
7.1.2.5.3 Message contents
Message contents are according to TS 36.508 [18] clauses 4.6 and 4.7 and as follows:
RESET UE POSITIONING STORED INFORMATION
Information Element |
Value/remark |
UE POSITIONING TECHNOLOGY |
AGNSS |
LPP REQUEST CAPABILITIES
Information Element |
Value/remark |
a‑gnss‑RequestCapabilities |
TRUE |
LPP REQUEST LOCATION INFORMATION
Information Element |
Value/remark |
Comment |
commonIEsRequestLocationInformation |
||
> locationInformationType |
‘locationEstimateRequired’ or ‘locationMeasurementsRequired’ |
Depending on test case and UE capabilities, i.e. support for UE-based or UE-assisted |
> additionalInformation |
‘onlyReturnInformationRequested’ |
|
> qos |
||
>> horizontalAccuracy |
‘19’ (51.2m) |
|
>> verticalCoordinateRequest |
FALSE |
|
>> responseTime |
||
>>>time |
‘20’ |
|
a-gnss-RequestLocationInformation |
||
> gnss-PositioningInstructions |
||
>> gnssMethods |
||
>>> gnss-ids |
Sub-test 1: ‘gps’ Sub-test 2: ‘glonass’ Sub-test 3: ‘galileo’ Sub-test 4: ‘gps’ Sub-test 5: ‘gps’ and ‘glonass’ Sub-test 8: ‘gps’ and ‘galileo’ Sub-test 9: ‘bds’ Sub-test 10: ‘gps’and’bds’ Sub-test 11: ‘gps’ and ‘glonass’ and ‘bds’ Sub-test 12: ‘gps’ and ‘galileo’ and ‘glonass’ Sub-test 13: ‘gps’ and ‘galileo’ and ‘bds’ |
|
>> fineTimeAssistanceMeasReq |
FALSE |
|
>> adrMeasReq |
FALSE |
|
>> multiFreqMeasReq |
TRUE or FALSE |
Depending on UE capabilities |
>> assistanceAvailability |
FALSE |
7.1.2.6 Test requirement
For the parameters specified in table 7.1.2.6 or 7.1.2.7 the UE shall meet the requirements and the success rate specified in table 7.1.2.9 with a confidence level of 95% according to Annex D.
Table 7.1.2.6: Test parameters for Sensitivity Fine time assistance – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
8 |
HDOP Range |
– |
1.1 to 1.6 |
Propagation conditions |
– |
AWGN |
GPS Coarse time assistance error range |
seconds |
±1.8 |
GPS Fine Time assistance error range |
μs |
±9 |
GPS L1 C/A Signal for all satellites |
dBm |
-146 |
Table 7.1.2.7: Test parameters for Sensitivity Fine time assistance – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.1.2.8 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP range |
1.4 to 2.1 |
||
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±1.8 |
|
GNSS fine time assistance error range |
s |
±9 |
|
Galileo |
Reference signal power level |
dBm |
-146 |
GPS(1) |
Reference signal power level |
dBm |
-146 |
GLONASS |
Reference signal power level |
dBm |
-146 |
BDS |
Reference signal power level |
dBm |
-146 |
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.1.2.8: Satellite allocation
Satellite allocation for each constellation |
|||
GNSS-1 |
GNSS-2 |
GNSS-3 |
|
Single constellation |
6 |
– |
– |
Dual constellation |
3 |
3 |
– |
Triple constellation |
3 |
2 |
2 |
Table 7.1.2.9: Test requirements for Sensitivity Fine Time Assistance
System |
Success rate |
2-D position error |
Max response time |
---|---|---|---|
All |
95 % |
101.3 m |
20.3 s |
7.2 Nominal Accuracy
7.2.1 Sub-tests
This test includes sub-tests dependent on the GNSS supported by the UE. Each sub-test is identified by a Sub-Test Number as defined in Table 7.2.1
Table 7.2.1: Sub-Test Number Definition
Sub-Test Number |
Supported GNSS |
1 |
UE supporting A-GPS L1 C/A |
2 |
UE supporting A-GLONASS |
3 |
UE supporting A-Galileo |
4 |
UE supporting A-GPS and Modernized GPS |
5 |
UE supporting A-GPS and A-GLONASS (Note) |
8 |
UE supporting A-GPS and A-Galileo (Note) |
9 |
UE supporting A-BDS |
10 |
UE supporting A-GPS and A-BDS (Note) |
11 |
UE supporting A-GPS and A-GLONASS and A-BDS (Note) |
12 |
UE supporting A-GPS and A-Galileo and A-GLONASS (Note) |
13 |
UE supporting A-GPS and A-Galileo and A-BDS (Note) |
Note: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |
7.2.2 Test purpose
To verify the performance of the first position estimate, when the UE is provided with ideal GNSS signal conditions.
7.2.3 Test applicability
This test applies to all types of E-UTRA UE that supports A-GNSS, except Category M1 and Category M2 devices that do not support VoLTE.
7.2.4 Minimum conformance requirements
The first fix position estimates shall meet the accuracy and response time requirements in table 7.2.2 or 7.2.3 for the parameters specified in table 7.2.4 or 7.2.5.
Table 7.2.2: Requirements for Nominal Accuracy – Sub-Test 1
Success rate |
2-D position error |
Max response time |
---|---|---|
95 % |
30 m |
20 s |
Table 7.2.3: Requirements for Nominal Accuracy – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
Success rate |
2-D position error |
Max response time |
---|---|---|
95 % |
15 m |
20 s |
Table 7.2.4: Parameters for Nominal Accuracy – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
8 |
HDOP Range |
– |
1.1 to 1.6 |
Propagation conditions |
– |
AWGN |
GPS Coarse Time assistance error range |
seconds |
±2 |
GPS L1 C/A Signal for all satellites |
dBm |
-130 |
Table 7.2.5: Parameters for Nominal Accuracy – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.2.6 |
|
Total number of generated satellites |
– |
6, 7(2) or 8(3) |
|
HDOP Range |
– |
1.4 to 2.1 |
|
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±2 |
|
GPS(1) |
Reference signal power level for all satellites |
dBm |
-128.5 |
Galileo |
Reference signal power level for all satellites |
dBm |
-127 |
GLONASS |
Reference signal power level for all satellites |
dBm |
-131 |
QZSS |
Reference signal power level for all satellites |
dBm |
-128.5 |
SBAS |
Reference signal power level for all satellites |
dBm |
-131 |
BDS |
Reference signal power level for all satellites |
dBm |
-133 |
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites apply only for SBAS case or sub-tests with 3 different GNSSs. NOTE 3: 8 satellites apply only for sub-tests with 3 different GNSSs and SBAS. |
If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support.
If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario.
Table 7.2.6: Satellite allocation
Satellite allocation for each constellation |
||||
GNSS 1(1) |
GNSS 2(1) |
GNSS 3(1) |
SBAS |
|
Single constellation |
6 |
— |
— |
1 |
Dual constellation |
3 |
3 |
— |
1 |
Triple constellation |
3 |
2 |
2 |
1 |
NOTE 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |
The normative reference for this requirement is TS 36.171 [3] clause 5.2 and 6.2.
7.2.5 Test description
7.2.5.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
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.
Channel Bandwidth to be tested: as defined in TS 36.508 [18] clause 4.3.1.
1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in Annex A.
2. Set the GNSS test parameters as specified in table 7.2.7 or 7.2.8 for GNSS scenario #3 in TS 37.571-5 [20].
3. The parameter settings for the cell are set up according to TS 36.508 [18] clause 4.4.3, single cell scenario.
4. Switch on the UE.
5. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
7.2.5.2 Test procedure
1. Start GNSS scenario #3 as specified in clause 6.2.1.2 of TS 37.571-5 [20] with the UE location randomly selected to be within 3 km of the Reference Location and the altitude of the UE randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in clause 6.2.1.2.6 of TS 37.571-5 [20]
2. Send a RESET UE POSITIONING STORED INFORMATION message.
3. Depending on how the LPP session is performed:
– In the case of C-Plane, the SS shall send an LPP REQUEST CAPABILITIES message.
– In the case of U-Plane, the SS shall establish a SUPL session with the UE for positioning.
4. The UE returns an LPP PROVIDE CAPABILITIES message indicating the assistance data supported by the UE in the Assistance Data Support List in the A GNSS Provide Capabilities IE.
5. Send an LPP PROVIDE ASSISTANCE DATA message to provide the assistance data that is supported by the UE as indicated in the step 4 and in accordance with clause 6.2.6 of TS 37.571-5 [20], and with the values defined in clause 6.2.7 of TS 37.571-5 [20] with the value of GNSS Reference Time offset by a random value as specified in clause 6.2.7.2 of TS 37.571-5 [20]. If the LPP session is performed over C-Plane, then if the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the (first) LPP PROVIDE ASSISTANCE DATA message.
6. Send an LPP REQUEST LOCATION INFORMATION message to obtain a fix.
7. If the UE returns a valid result in the LPP PROVIDE LOCATION INFORMATION message within the Max response time specified in table 7.2.10 then record the result and process it as specified in step 8. If the UE does not return a valid result within the Max response time specified in table 7.2.10 or reports an Error in the LPP PROVIDE LOCATION INFORMATION message then record one Bad Result.
7a. If the UE message at step 7 includes the ackRequested IE set to TRUE, then the SS shall send a LPP acknowledgment message.
8. For UE based testing compare the reported Location Information in the LPP PROVIDE LOCATION INFORMATION message against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.2.10 and record one Good Result or Bad Result as appropriate; or
For UE assisted testing convert the GNSS Measurement Information reported in the LPP PROVIDE LOCATION INFORMATION message to a 2D position using the method described in clause 4.4.3 and then compare the result against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table7.2.10 and record one Good Result or Bad Result as appropriate.
9. Repeat steps 1 to 8 using GNSS scenario #4 instead of #3 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. Use new random values for the UE location and altitude in step 1 and for the GNSS Reference Time offset in step 5.
10. Repeat steps 1 to 9 until the statistical requirements of clause 7.2.6 are met. Each time scenario #3 or #4 is used, the start time of the GNSS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again.
11. Release the signalling connection.
7.2.5.3 Message contents
Message contents are according to TS 36.508 [18] clauses 4.6 and 4.7 and as follows:
RESET UE POSITIONING STORED INFORMATION
Information Element |
Value/remark |
UE POSITIONING TECHNOLOGY |
AGNSS |
LPP REQUEST CAPABILITIES
Information Element |
Value/remark |
a‑gnss‑RequestCapabilities |
TRUE |
LPP REQUEST LOCATION INFORMATION
Information Element |
Value/remark |
Comment |
commonIEsRequestLocationInformation |
||
> locationInformationType |
‘locationEstimateRequired’ or ‘locationMeasurementsRequired’ |
Depending on test case and UE capabilities, i.e. support for UE-based or UE-assisted |
> additionalInformation |
‘onlyReturnInformationRequested’ |
|
> qos |
||
>> horizontalAccuracy (Sub-Test 1) |
’10’ (15.9m) |
|
>> horizontalAccuracy (Sub-Tests 2 to 5 and 8 to 13) |
’6’ (7.7m) |
|
>> verticalCoordinateRequest |
FALSE |
|
>> responseTime |
||
>>>time |
‘20’ |
|
a-gnss-RequestLocationInformation |
||
> gnss-PositioningInstructions |
||
>> gnssMethods |
||
>>> gnss-ids |
Sub-test 1: ‘gps’ and possibly ‘sbas’ and/or ‘qzss’ Sub-test 2: ‘glonass’ and possibly ‘sbas’ and/or ‘qzss’ Sub-test 3: ‘galileo’ and possibly ‘sbas’ and/or ‘qzss’ Sub-test 4: ‘gps’ and possibly ‘sbas’ and/or ‘qzss’ Sub-test 5: ‘gps’ and ‘glonass’ and possibly ‘sbas’ and/or ‘qzss’ Sub-test 8: ‘gps’ and ‘galileo’ and possibly ‘sbas’ and/or ‘qzss’ Sub-test 9: ‘bds’ and possibly ‘sbas’ and /or ‘qzss’ Sub-test 10: ‘gps’and’bds’and possibly ‘sbas’and/or’qzss’ Sub-test 11: ‘gps’ and ‘glonass’ and ‘bds’ and possibly ‘sbas’ and/or ‘qzss’ Sub-test 12: ‘gps’ and ‘galileo’ and ‘glonass’ Sub-test 13: ‘gps’ and ‘galileo’ and ‘bds’ |
Depending on UE capabilities |
>> fineTimeAssistanceMeasReq |
FALSE |
|
>> adrMeasReq |
FALSE |
|
>> multiFreqMeasReq |
TRUE or FALSE |
Depending on UE capabilities |
>> assistanceAvailability |
FALSE |
7.2.6 Test requirement
For the parameters specified in table 7.2.7 or 7.2.8 the UE shall meet the requirements and the success rate specified in table 7.2.10 or 7.2.11 with a confidence level of 95% according to Annex D.
Table 7.2.7: Test parameters Nominal Accuracy – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
8 |
HDOP Range |
– |
1.1 to 1.6 |
Propagation conditions |
– |
AWGN |
GPS Coarse Time assistance error range |
seconds |
±1.8 |
GPS L1 C/A Signal for all satellites |
dBm |
-130 |
Table 7.2.8: Test parameters Nominal Accuracy – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.2.9 |
|
Total number of generated satellites |
– |
6, 7(2) or 8(3) |
|
HDOP Range |
– |
1.4 to 2.1 |
|
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±1.8 |
|
GPS(1) |
Reference signal power level for all satellites |
dBm |
-128.5 |
Galileo |
Reference signal power level for all satellites |
dBm |
-127 |
GLONASS |
Reference signal power level for all satellites |
dBm |
-131 |
QZSS |
Reference signal power level for all satellites |
dBm |
-128.5 |
SBAS |
Reference signal power level for all satellites |
dBm |
-131 |
BDS |
Reference signal power level for all satellites |
dBm |
-133 |
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites apply only for SBAS case or sub-tests with 3 different GNSSs. NOTE 3: 8 satellites apply only for sub-tests with 3 different GNSSs and SBAS. |
If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support.
If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario.
Table 7.2.9: Satellite allocation
Satellite allocation for each constellation |
||||
GNSS 1(1) |
GNSS 2(1) |
GNSS 3(1) |
SBAS |
|
Single constellation |
6 |
– |
– |
1 |
Dual constellation |
3 |
3 |
– |
1 |
Triple constellation |
3 |
2 |
2 |
1 |
NOTE 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |
Table 7.2.10: Test requirements for Nominal Accuracy – Sub-Test 1
System |
Success rate |
2-D position error |
Max response time |
---|---|---|---|
All |
95 % |
31.3 m |
20.3 s |
Table 7.2.11: Test requirements for Nominal Accuracy – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Success rate |
2-D position error |
Max response time |
---|---|---|---|
All |
95 % |
16.3 m |
20.3 s |
7.3 Dynamic Range
7.3.1 Sub-tests
This test includes sub-tests dependent on the GNSS supported by the UE. Each sub-test is identified by a Sub-Test Number as defined in Table 7.3.1
Table 7.3.1: Sub-Test Number Definition
Sub-Test Number |
Supported GNSS |
1 |
UE supporting A-GPS L1 C/A |
2 |
UE supporting A-GLONASS |
3 |
UE supporting A-Galileo |
4 |
UE supporting A-GPS and Modernized GPS |
5 |
UE supporting A-GPS and A-GLONASS (Note) |
8 |
UE supporting A-GPS and A-Galileo (Note) |
9 |
UE supporting A-BDS |
10 |
UE supporting A-GPS and A-BDS (Note) |
11 |
UE supporting A-GPS and A-GLONASS and A-BDS (Note) |
12 |
UE supporting A-GPS and A-Galileo and A-GLONASS (Note) |
13 |
UE supporting A-GPS and A-Galileo and A-BDS (Note) |
Note: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |
7.3.2 Test purpose
To verify the performance of the first position estimate, when the UE is provided with GNSS signals with large dynamic ranges.
7.3.3 Test applicability
This test applies to all types of E-UTRA UE that supports A-GNSS, except Category M1 and Category M2 devices that do not support VoLTE.
7.3.4 Minimum conformance requirements
The first fix position estimates shall meet the accuracy and response time requirements in table 7.3.2 for the parameters specified in table 7.3.3 or 7.3.4.
Table 7.3.2: Requirements for Dynamic Range
Success rate |
2-D position error |
Max response time |
---|---|---|
95 % |
100 m |
20 s |
Table 7.3.3: Parameters for Dynamic Range – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
6 |
HDOP Range |
– |
1.4 to 2.1 |
GPS Coarse Time assistance error range |
seconds |
±2 |
Propagation conditions |
– |
AWGN |
GPS L1 C/A Signal for 1st satellite |
dBm |
-129 |
GPS L1 C/A Signal for 2nd satellite |
dBm |
-135 |
GPS L1 C/A Signal for 3rd satellite |
dBm |
-141 |
GPS L1 C/A Signal for 4th satellite |
dBm |
-147 |
GPS L1 C/A Signal for 5th satellite |
dBm |
-147 |
GPS L1 C/A Signal for 6th satellite |
dBm |
-147 |
Table 7.3.4: Parameters for Dynamic Range – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.3.5 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP Range |
– |
1.4 to 2.1 |
|
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±2 |
|
Galileo |
Reference high signal power level |
dBm |
-127.5 |
Reference low signal power level |
dBm |
-147 |
|
GPS(1) |
Reference high signal power level |
dBm |
-129 |
Reference low signal power level |
dBm |
-147 |
|
GLONASS |
Reference high signal power level |
dBm |
-131.5 |
Reference low signal power level |
dBm |
-147 |
|
BDS |
Reference high signal power level |
dBm |
-133.5 |
Reference low signal power level |
dBm |
-145 |
|
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.3.5: Power level and satellite allocation
Satellite allocation for each constellation |
||||
GNSS 1(1) |
GNSS 2(1) |
GNSS 3(1) |
||
Single constellation |
High signal level |
2 |
— |
— |
Low signal level |
4 |
— |
— |
|
Dual constellation |
High signal level |
1 |
1 |
— |
Low signal level |
2 |
2 |
— |
|
Triple constellation |
High signal level |
1 |
1 |
1 |
Low signal level |
2 |
1 |
1 |
|
NOTE 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |
The normative reference for this requirement is TS 36.171 [3] clause 5.3 and 6.3.
7.3.5 Test description
7.3.5.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
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.
Channel Bandwidth to be tested: as defined in TS 36.508 [18] clause 4.3.1.
1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in Annex A.
2. Set the GNSS test parameters as specified in table 7.3.6 or 7.3.7 for GNSS scenario #1 in TS 37.571-5 [20]. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20] for the satellites with the higher levels.
3. The parameter settings for the cell are set up according to TS 36.508 [18] clause 4.4.3, single cell scenario.
4. Switch on the UE.
5. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
7.3.5.2 Test procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 37.571-5 [20] with the UE location randomly selected to be within 3 km of the Reference Location and the altitude of the UE randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in clause 6.2.1.2.6 of TS 37.571-5 [20]
2. Send a RESET UE POSITIONING STORED INFORMATION message.
3. Depending on how the LPP session is performed:
– In the case of C-Plane, the SS shall send an LPP REQUEST CAPABILITIES message.
– In the case of U-Plane, the SS shall establish a SUPL session with the UE for positioning.
4. The UE returns an LPP PROVIDE CAPABILITIES message indicating the assistance data supported by the UE in the Assistance Data Support List in the A GNSS Provide Capabilities IE.
5. Send an LPP PROVIDE ASSISTANCE DATA message to provide the assistance data that is supported by the UE as indicated in the step 4 and in accordance with clause 6.2.6 of TS 37.571-5 [20], and with the values defined in clause 6.2.7 of TS 37.571-5 [20] with the value of GNSS Reference Time offset by a random value as specified in clause 6.2.7.2 of TS 37.571-5 [20]. If the LPP session is performed over C-Plane, then if the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the (first) LPP PROVIDE ASSISTANCE DATA message.
6. Send an LPP REQUEST LOCATION INFORMATION message to obtain a fix.
7. If the UE returns a valid result in the LPP PROVIDE LOCATION INFORMATION message within the Max response time specified in table 7.3.9 then record the result and process it as specified in step 8. If the UE does not return a valid result within the Max response time specified in table 7.3.9 or reports an Error in the LPP PROVIDE LOCATION INFORMATION message then record one Bad Result.
7a. If the UE message at step 7 includes the ackRequested IE set to TRUE, then the SS shall send a LPP acknowledgment message.
8. For UE based testing compare the reported Location Information in the LPP PROVIDE LOCATION INFORMATION message against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.3.9 and record one Good Result or Bad Result as appropriate; or
For UE assisted testing convert the GNSS Measurement Information reported in the LPP PROVIDE LOCATION INFORMATION message to a 2D position using the method described in clause 4.4.3 and then compare the result against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.3.9 and record one Good Result or Bad Result as appropriate.
9. Repeat steps 1 to 8 using GNSS scenario #2 instead of #1 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20] for the satellites with the higher levels. Use new random values for the UE location and altitude in step 1 and for the GNSS Reference Time offset in step 5.
10. Repeat steps 1 to 9 until the statistical requirements of clause 7.3.6 are met. Each time scenario #1 or #2 is used, the start time of the GNSS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again. Each time scenario #1 or #2 is used, randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20], for the satellites with the higher levels.
11. Release the signalling connection.
7.3.5.3 Message contents
Message contents are according to TS 36.508 [18] clauses 4.6 and 4.7 and as follows:
RESET UE POSITIONING STORED INFORMATION
Information Element |
Value/remark |
UE POSITIONING TECHNOLOGY |
AGNSS |
LPP REQUEST CAPABILITIES
Information Element |
Value/remark |
a‑gnss‑RequestCapabilities |
TRUE |
LPP REQUEST LOCATION INFORMATION
Information Element |
Value/remark |
Comment |
commonIEsRequestLocationInformation |
||
> locationInformationType |
‘locationEstimateRequired’ or ‘locationMeasurementsRequired’ |
Depending on test case and UE capabilities, i.e. support for UE-based or UE-assisted |
> additionalInformation |
‘onlyReturnInformationRequested’ |
|
> qos |
||
>> horizontalAccuracy |
‘19’ (51.2m) |
|
>> verticalCoordinateRequest |
FALSE |
|
>> responseTime |
||
>>>time |
‘20’ |
|
a-gnss-RequestLocationInformation |
||
> gnss-PositioningInstructions |
||
>> gnssMethods |
||
>>> gnss-ids |
Sub-test 1: ‘gps’ Sub-test 2: ‘glonass’ Sub-test 3: ‘galileo’ Sub-test 4: ‘gps’ Sub-test 5: ‘gps’ and ‘glonass’ Sub-test 8: ‘gps’ and ‘galileo’ Sub-test 9: ‘bds’ Sub-test 10: ‘gps’and’bds’ Sub-test 11: ‘gps’ and ‘glonass’ and ‘bds’ Sub-test 12: ‘gps’ and ‘galileo’ and ‘glonass’ Sub-test 13: ‘gps’ and ‘galileo’ and ‘bds’ |
|
>> fineTimeAssistanceMeasReq |
FALSE |
|
>> adrMeasReq |
FALSE |
|
>> multiFreqMeasReq |
TRUE or FALSE |
Depending on UE capabilities |
>> assistanceAvailability |
FALSE |
7.3.6 Test requirement
For the parameters specified in table 7.3.6 or 7.3.7 the UE shall meet the requirements and the success rate specified in table 7.3.9 with a confidence level of 95% according to Annex D.
Table 7.3.6: Test parameters for Dynamic Range – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
6 |
HDOP Range |
– |
1.4 to 2.1 |
GPS Coarse Time assistance error range |
seconds |
±1.8 |
Propagation conditions |
– |
AWGN |
GPS L1 C/A Signal for 1st satellite |
dBm |
-128.2 |
GPS L1 C/A Signal for 2nd satellite |
dBm |
-134 |
GPS L1 C/A Signal for 3rd satellite |
dBm |
-140 |
GPS L1 C/A Signal for 4th satellite |
dBm |
-146 |
GPS L1 C/A Signal for 5th satellite |
dBm |
-146 |
GPS L1 C/A Signal for 6th satellite |
dBm |
-146 |
Table 7.3.7: Test parameters for Dynamic Range – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.3.8 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP Range |
– |
1.4 to 2.1 |
|
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±1.8 |
|
Galileo |
Reference high signal power level |
dBm |
-126.7 |
Reference low signal power level |
dBm |
-146 |
|
GPS(1) |
Reference high signal power level |
dBm |
-128.2 |
Reference low signal power level |
dBm |
-146 |
|
GLONASS |
Reference high signal power level |
dBm |
-130.7 |
Reference low signal power level |
dBm |
-146 |
|
BDS |
Reference high signal power level |
dBm |
-132.7 |
Reference low signal power level |
dBm |
-144 |
|
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.3.8: Power level and satellite allocation
Satellite allocation for each constellation |
||||
GNSS 1(1) |
GNSS 2(1) |
GNSS 3(1) |
||
Single constellation |
High signal level |
2 |
— |
— |
Low signal level |
4 |
— |
— |
|
Dual constellation |
High signal level |
1 |
1 |
— |
Low signal level |
2 |
2 |
— |
|
Triple constellation |
High signal level |
1 |
1 |
1 |
Low signal level |
2 |
1 |
1 |
|
NOTE 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |
Table 7.3.9: Test requirements for Dynamic Range
System |
Success rate |
2-D position error |
Max response time |
---|---|---|---|
All |
95 % |
101.3 m |
20.3 s |
7.4 Multi-Path scenario
7.4.1 Sub-tests
This test includes sub-tests dependent on the GNSS supported by the UE. Each sub-test is identified by a Sub-Test Number as defined in Table 7.4.1
Table 7.4.1: Sub-Test Number Definition
Sub-Test Number |
Supported GNSS |
1 |
UE supporting A-GPS L1 C/A |
2 |
UE supporting A-GLONASS |
3 |
UE supporting A-Galileo |
4 |
UE supporting A-GPS and Modernized GPS |
5 |
UE supporting A-GPS and A-GLONASS (Note) |
8 |
UE supporting A-GPS and A-Galileo (Note) |
9 |
UE supporting A-BDS |
10 |
UE supporting A-GPS and A-BDS (Note) |
11 |
UE supporting A-GPS and A-GLONASS and A-BDS (Note) |
12 |
UE supporting A-GPS and A-Galileo and A-GLONASS (Note) |
13 |
UE supporting A-GPS and A-Galileo and A-BDS (Note) |
Note: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |
7.4.2 Test purpose
To verify the performance of the first position estimate, when the UE is provided with GNSS signals with multi-path components.
7.4.3 Test applicability
This test applies to all types of E-UTRA UE that supports A-GNSS, except Category M1 and Category M2 devices that do not support VoLTE.
7.4.4 Minimum conformance requirements
The first fix position estimates shall meet the accuracy and response time requirements in table 7.4.2 for the parameters specified in table 7.4.3 or 7.4.4.
Table 7.4.2: Requirements for Multi-Path scenario
Success rate |
2-D position error |
Max response time |
---|---|---|
95 % |
100 m |
20 s |
Table 7.4.3: Parameters for Multi-Path scenario – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites (Satellites 1, 2 unaffected by multi-path) (Satellites 3, 4, 5 affected by multi-path) |
– |
5 |
GPS Coarse time assistance error range |
seconds |
±2 |
HDOP Range |
– |
1.8 to 2.5 |
GPS L1 C/A Signal for satellite 1, 2 |
dBm |
-130 |
GPS L1 C/A Signal for satellite 3, 4, 5 |
dBm |
LOS signal of -130 dBm, multi-path signal of -136 dBm |
Table 7.4.4: Parameters for Multi-Path scenario – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.4.5 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP range |
1.4 to 2.1 |
||
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±2 |
|
Galileo |
Reference signal power level |
dBm |
-127 |
GPS(1) |
Reference signal power level |
dBm |
-128.5 |
GLONASS |
Reference signal power level |
dBm |
-131 |
BDS |
Reference signal power level |
dBm |
-133 |
NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.4.5: Channel model allocation
Channel model allocation for each constellation |
||||
GNSS-1 |
GNSS-2 |
GNSS-3 |
||
Single constellation |
One-tap channel |
2 |
— |
— |
Two-tap channel |
4 |
— |
— |
|
Dual constellation |
One-tap channel |
1 |
1 |
— |
Two-tap channel |
2 |
2 |
— |
|
Triple constellation |
One-tap channel |
1 |
1 |
1 |
Two-tap channel |
2 |
1 |
1 |
|
Note: One-tap channel: no multi-path. Two-tap channel: multi-path defined in clause 4.2.4 |
The normative reference for this requirement is TS 36.171 [3] clause 5.4 and 6.4.
7.4.5 Test description
7.4.5.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
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.
Channel Bandwidth to be tested: as defined in TS 36.508 [18] clause 4.3.1.
1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in Annex A.
2. Set the GNSS test parameters as specified in table 7.4.6 or 7.4.7 for GNSS scenario #1 in TS 37.571-5 [20]. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20] for the satellites with one-tap channels.
3. The parameter settings for the cell are set up according to TS 36.508 [18] clause 4.4.3, single cell scenario.
4. Switch on the UE.
5. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
7.4.5.2 Test procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 37.571-5 [20] with the UE location randomly selected to be within 3 km of the Reference Location and the altitude of the UE randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in clause 6.2.1.2.6 of TS 37.571-5 [20]. The initial carrier phase difference between taps of the multi-path model shall be randomly selected between 0 and 2radians by selecting the next random number from a standard uniform random number generator, in the range 0 to 2, representing radians with a resolution of 0.1, representing 0.1 radians.
2. Send a RESET UE POSITIONING STORED INFORMATION message.
3. Depending on how the LPP session is performed:
– In the case of C-Plane, the SS shall send an LPP REQUEST CAPABILITIES message.
– In the case of U-Plane, the SS shall establish a SUPL session with the UE for positioning.
4. The UE returns an LPP PROVIDE CAPABILITIES message indicating the assistance data supported by the UE in the Assistance Data Support List in the A GNSS Provide Capabilities IE.
5. Send an LPP PROVIDE ASSISTANCE DATA message to provide the assistance data that is supported by the UE as indicated in the step 4 and in accordance with clause 6.2.6 of TS 37.571-5 [20], and with the values defined in clause 6.2.7 of TS 37.571-5 [20] with the value of GNSS Reference Time offset by a random value as specified in clause 6.2.7.2 of TS 37.571-5 [20]. If the LPP session is performed over C-Plane, then if the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
6. Send an LPP REQUEST LOCATION INFORMATION message to obtain a fix.
7. If the UE returns a valid result in the LPP PROVIDE LOCATION INFORMATION message within the Max response time specified in table 7.4.10 then record the result and process it as specified in step 8. If the UE does not return a valid result within the Max response time specified in table 7.4.10 or reports an Error in the LPP PROVIDE LOCATION INFORMATION message then record one Bad Result.
7a. If the UE message at step 7 includes the ackRequested IE set to TRUE, then the SS shall send a LPP acknowledgment message.
8. For UE based testing compare the reported Location Information in the LPP PROVIDE LOCATION INFORMATION message against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.4.10 and record one Good Result or Bad Result as appropriate; or
For UE assisted testing convert the GNSS Measurement Information reported in the LPP PROVIDE LOCATION INFORMATION message to a 2D position using the method described in clause 4.4.3 and then compare the result against the simulated position of the UE used in step 1, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.4.10 and record one Good Result or Bad Result as appropriate.
9. Repeat steps 1 to 8 using GNSS scenario #2 instead of #1 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20] for the satellites with the one-tap channels. Use new random values for the UE location and altitude, and the initial carrier phase difference between taps of the multi-path model in step 1 and for the GNSS Reference Time offset in step 5.
10. Repeat steps 1 to 9 until the statistical requirements of clause 7.4.6 are met. Each time scenario #1 or #2 is used, the start time of the GNSS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again. Each time scenario #1 or #2 is used, randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 37.571-5 [20], for the satellites with the one-tap channels.
11. Release the signalling connection
7.4.5.3 Message contents
Message contents are according to TS 36.508 [18] clauses 4.6 and 4.7 and as follows:
RESET UE POSITIONING STORED INFORMATION
Information Element |
Value/remark |
UE POSITIONING TECHNOLOGY |
AGNSS |
LPP REQUEST CAPABILITIES
Information Element |
Value/remark |
a‑gnss‑RequestCapabilities |
TRUE |
LPP REQUEST LOCATION INFORMATION
Information Element |
Value/remark |
Comment |
commonIEsRequestLocationInformation |
||
> locationInformationType |
‘locationEstimateRequired’ or ‘locationMeasurementsRequired’ |
Depending on test case and UE capabilities, i.e. support for UE-based or UE-assisted |
> additionalInformation |
‘onlyReturnInformationRequested’ |
|
> qos |
||
>> horizontalAccuracy |
‘19’ (51.2m) |
|
>> verticalCoordinateRequest |
FALSE |
|
>> responseTime |
||
>>>time |
‘20’ |
|
a-gnss-RequestLocationInformation |
||
> gnss-PositioningInstructions |
||
>> gnssMethods |
||
>>> gnss-ids |
Sub-test 1: ‘gps’ Sub-test 2: ‘glonass’ Sub-test 3: ‘galileo’ Sub-test 4: ‘gps’ Sub-test 5: ‘gps’ and ‘glonass’ Sub-test 8: ‘gps’ and ‘galileo’ Sub-test 9: ‘bds’ Sub-test 10: ‘gps’and’bds’ Sub-test 11: ‘gps’ and ‘glonass’ and ‘bds’ Sub-test 12: ‘gps’ and ‘galileo’ and ‘glonass’ Sub-test 13: ‘gps’ and ‘galileo’ and ‘bds’ |
|
>> fineTimeAssistanceMeasReq |
FALSE |
|
>> adrMeasReq |
FALSE |
|
>> multiFreqMeasReq |
TRUE or FALSE |
Depending on UE capabilities |
>> assistanceAvailability |
FALSE |
7.4.6 Test requirement
For the parameters specified in table 7.4.6 or 7.4.7 the UE shall meet the requirements and the success rate specified in table 7.4.10 with a confidence level of 95% according to Annex D.
Table 7.4.6: Test parameters for Multi-Path scenario – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites (see note) |
– |
5 |
GPS Coarse Time assistance error range |
seconds |
±1.8 |
HDOP Range |
– |
1.8 to 2.5 |
GPS L1 C/A Signal for Satellite 1, 2 (see note) |
dBm |
-130 |
GPS L1 C/A Signal for Satellite 3, 4, 5 (see note) |
dBm |
LOS signal of -130 dBm, multi-path signal of -136.2 dBm |
NOTE: Satellites 1, 2 no multi-path. Satellites 3, 4, 5 multi-path defined in clause 4.2.4. |
Table 7.4.7: Test parameters for Multi-Path scenario – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.4.8 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP Range per system |
– |
1.4 to 2.1 |
|
Propagation conditions |
– |
AWGN |
|
GNSS coarse time assistance error range |
seconds |
±2 |
|
Galileo |
Reference signal power level for all satellites |
dBm |
-127 |
GPS(1) |
Reference signal power level for all satellites |
dBm |
-128.5 |
GLONASS |
Reference signal power level for all satellites |
dBm |
-131 |
BDS |
Reference signal power level for all satellites |
dBm |
-133 |
NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.4.8: Channel model allocation
Channel model allocation for each constellation |
||||
GNSS-1 |
GNSS-2 |
GNSS-3 |
||
Single constellation |
One-tap channel |
2 |
— |
— |
Two-tap channel |
4 |
— |
— |
|
Dual constellation |
One-tap channel |
1 |
1 |
— |
Two-tap channel |
2 |
2 |
— |
|
Triple constellation |
One-tap channel |
1 |
1 |
1 |
Two-tap channel |
2 |
1 |
1 |
|
Note: One-tap channel: no multi-path. Two-tap channel: multi-path defined in clause 4.2.4 with Relative mean Power (Y) defined in Table 7.4.9. |
Table 7.4.9: Relative mean Power (Y) for use in Table 7.4.8
Galileo |
E1 |
-4.7 |
E5a |
-6.2 |
|
E5b |
-6.2 |
|
GPS/Modernized GPS |
L1 C/A |
-6.2 |
L1C |
-4.7 |
|
L2C |
-6.2 |
|
L5 |
-6.2 |
|
GLONASS |
G1 |
-12.7 |
G2 |
-12.7 |
|
BDS |
B1I |
-4.7 |
B1C |
-4.7 |
Table 7.4.10: Test requirements for Multi-Path scenario
System |
Success rate |
2-D position error |
Max response time |
---|---|---|---|
All |
95 % |
101.3 m |
20.3 s |
7.5 Moving scenario and periodic update (Rel-9 to Rel-13)
7.5.1 Sub-tests
This test includes sub-tests dependent on the GNSS supported by the UE. Each sub-test is identified by a Sub-Test Number as defined in Table 7.5.1.
Table 7.5.1: Sub-Test Number Definition
Sub-Test Number |
Supported GNSS |
1 |
UE supporting A-GPS L1 C/A |
2 |
UE supporting A-GLONASS |
3 |
UE supporting A-Galileo |
4 |
UE supporting A-GPS and Modernized GPS |
5 |
UE supporting A-GPS and A-GLONASS (Note) |
8 |
UE supporting A-GPS and A-Galileo (Note) |
9 |
UE supporting A-BDS |
10 |
UE supporting A-GPS and A-BDS (Note) |
11 |
UE supporting A-GPS and A-GLONASS and A-BDS (Note) |
12 |
UE supporting A-GPS and A-Galileo and A-GLONASS (Note) |
13 |
UE supporting A-GPS and A-Galileo and A-BDS (Note) |
Note: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. |
7.5.2 Test purpose
To verify the performance when the UE is requested to use periodical reporting with a reporting interval of 2 seconds.
7.5.3 Test applicability
This test applies to all types of E-UTRA UE that supports A-GNSS with LPP Release 9 to 13, except Category M1 and Category M2 devices that do not support VoLTE.
7.5.4 Minimum conformance requirements
The position estimates, after the first reported position estimate, shall meet the accuracy requirement in table 7.5.2 or 7.5.3 with the periodical reporting interval of 2 seconds for the parameters specified in table 7.5.4 or 7.5.5.
NOTE: In the actual testing the UE may report error messages until it has been able to acquire GNSS measured results or a position estimate. The SS shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 7.5.2 or 7.5.3.
Table 7.5.2: Requirements for Moving scenario and periodic update – Sub-Test 1
Success Rate |
2-D position error |
Periodical reporting interval |
---|---|---|
95 % |
100 m |
2 s |
Table 7.5.3: Requirements for Moving scenario and periodic update – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
Success Rate |
2-D position error |
Periodical reporting interval |
---|---|---|
95 % |
50 m |
2 s |
Table 7.5.4: Parameters for Moving scenario and periodic update – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
5 |
HDOP Range |
– |
1.8 to 2.5 |
Propagation condition |
– |
AWGN |
GPS L1 C/A signal for all satellites |
dBm |
-130 |
Table 7.5.5: Parameters for Moving scenario and periodic update – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.5.6 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP range |
1.4 to 2.1 |
||
Propagation conditions |
– |
AWGN |
|
Galileo |
Reference signal power level |
dBm |
-127 |
GPS(1) |
Reference signal power level |
dBm |
-128.5 |
GLONASS |
Reference signal power level |
dBm |
-131 |
BDS |
Reference signal power level |
dBm |
-133 |
NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.5.6: Satellite allocation
Satellite allocation for each constellation |
|||
GNSS 1(1) |
GNSS 2(1) |
GNSS 3(1) |
|
Single constellation |
6 |
— |
— |
Dual constellation |
3 |
3 |
— |
Triple constellation |
3 |
2 |
2 |
NOTE 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |
The normative reference for this requirement is TS 36.171 [3] clause 5.5 and 6.5.
7.5.5 Test description
7.5.5.1 Initial conditions
Initial conditions are a set of test configurations the UE needs to be tested in and the steps for the SS to take with the UE to reach the correct measurement state.
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.
Channel Bandwidth to be tested: as defined in TS 36.508 [18] clause 4.3.1
The UE moves on a rectangular trajectory of 940 m by 1 440 m with rounded corner defined in Figure 7.1. The initial reference is first defined followed by acceleration to final speed of 100 km/h in 250 m. The UE then maintains the speed for 400 m. This is followed by deceleration to final speed of 25 km/h in 250 m. The UE then turn 90 degrees with turning radius of 20 m at 25 km/h. This is followed by acceleration to final speed of 100 km/h in 250 m. The sequence is repeated to complete the rectangle.
Figure 7.1: Rectangular trajectory of the moving scenario and periodic update test case
Trajectory Parameters
Parameter |
Distance (m) |
Speed (km/h) |
l11, l15, l21, l25 |
20 |
25 |
l12, l14, l22, l24 |
250 |
25 to 100 and 100 to 25 |
l13 |
400 |
100 |
l23 |
900 |
100 |
1. Connect SS and GSS to the UE antenna cofor nnector or antenna connectors as shown in Annex A.
2. Set the GNSS test parameters as specified in table 7.5.7 or 7.5.8 for GNSS scenario #5 in TS 37.571-5 [20].
3. The parameter settings for the cell are set up according to TS 36.508 [18] clause 4.4.3, single cell scenario.
4. Switch on the UE.
5. Establish a signalling connection according to the generic procedure in TS 36.508 [18] clause 4.5.3 (State 3, Generic RB established) on a channel in the Mid EARFCN range.
7.5.5.2 Test procedure
1. Start GNSS scenario #5 as specified in clause 6.2.1.2 of TS 37.571-5 [20]
2. Send a RESET UE POSITIONING STORED INFORMATION message.
3. Depending on how the LPP session is performed:
– In the case of C-Plane, the SS shall send an LPP REQUEST CAPABILITIES message.
– In the case of U-Plane, the SS shall establish a SUPL session with the UE for positioning.
4. The UE returns an LPP PROVIDE CAPABILITIES message indicating the assistance data supported by the UE in the Assistance Data Support List in the A GNSS Provide Capabilities IE.
5. Send an LPP PROVIDE ASSISTANCE DATA message to provide the assistance data that is supported by the UE as indicated in the step 4 and in accordance with clause 6.2.6 of TS 37.571-5 [20], and with the values defined in clause 6.2.7 of TS 37.571-5 [20]. If the LPP session is performed over C-Plane, then if the UE message at step 4 includes the ackRequested IE set to TRUE, then the SS shall send an acknowledgment in the LPP PROVIDE ASSISTANCE DATA message.
6. Send an LPP REQUEST LOCATION INFORMATION message to obtain a fix.
7. Ignore any Error messages that the UE may report in LPP PROVIDE LOCATION INFORMATION messages until it has been able to acquire the GNSS signals and reports the first GNSS Measurement Information or Location Information.
8. Discard the first GNSS Measurement Infofor rmation or Location Information.
9. Record the time of reception of the next LPP PROVIDE LOCATION INFORMATION message after reception of the first GNSS Measurement Information or Location Information.
10. After the reception of the first GNSS Measurement Information or Location Information reported in a LPP PROVIDE LOCATION INFORMATION message, every time the UE returns a GNSS Measurement Information or Location Information in the LPP PROVIDE LOCATION INFORMATION message record the time of reception and the result. If the difference between the time of reception and the time of reception of the previous result is less than 1.5 seconds or greater than 2.5 seconds, or if the UE reports an Error in any LPP PROVIDE LOCATION INFORMATION messages, then record one Bad Result. Otherwise process the result as specified in step 11.
10a. If the UE messages at steps 7 to 10 include the ackRequested IE set to TRUE, then the SS shall send LPP acknowledgment messages as required.
11. For UE based testing compare the reported Location Information in the LPP PROVIDE LOCATION INFORMATION message against the simulated position of the UE at the time of applicability reported in the Location Information, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.5.10 or 7.5.11 and record one Good Result or Bad Result as appropriate; or
For UE assisted testing convert the GNSS Measurement Information reported in the LPP PROVIDE LOCATION INFORMATION message to a 2D position using the method described in clause 4.4.3 and then compare the result against the simulated position of the UE at the time of applicability reported in the GNSS Measurement Information, and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 7.5.10 or 7.5.11 and record one Good Result or Bad Result as appropriate.
12. If the UE sends the first LPP PROVIDE LOCATION INFORMATION that contains GNSS Measurement Information or Location Information later than 240s after the start of the GNSS scenario, fail the UE and stop the test early. Otherwise collect LPP PROVIDE LOCATION INFORMATION results during 900s, starting from the time recorded in step 9. If at any time the difference between the times of reception of two consecutive results is greater than 240s, fail the UE and stop the test early. Use the collected Good Results and Bad Results to determine the PASS/FAIL according to clause 7.5.6.
13. Release the signalling connection.
7.5.5.3 Message contents
Message contents are according to TS 36.508 [18] clauses 4.6 and 4.7 and as follows:
RESET UE POSITIONING STORED INFORMATION
Information Element |
Value/remark |
UE POSITIONING TECHNOLOGY |
AGNSS |
LPP REQUEST CAPABILITIES
Information Element |
Value/remark |
a‑gnss‑RequestCapabilities |
TRUE |
LPP REQUEST LOCATION INFORMATION
Information Element |
Value/remark |
Comment |
commonIEsRequestLocationInformation |
||
> locationInformationType |
‘locationEstimateRequired’ or ‘locationMeasurementsRequired’ |
Depending on test case and UE capabilities, i.e. support for UE-based or UE-assisted |
> periodicalReporting |
||
>> reportingAmount |
‘ra-Infinity‘ |
Infinite means during the complete test time |
>> reportingInterval |
‘ri0-5’ |
2 seconds |
> additionalInformation |
‘onlyReturnInformationRequested’ |
|
> qos |
||
>> horizontalAccuracy (Sub-Test 1) |
‘19’ (51.2m) |
|
>> horizontalAccuracy (Sub-Tests 2 to 5 and 8 to 13) |
‘13’ (24.5m) |
|
>> verticalCoordinateRequest |
FALSE |
|
>> responseTime |
Not present |
|
a-gnss-RequestLocationInformation |
||
> gnss-PositioningInstructions |
||
>> gnssMethods |
||
>>> gnss-ids |
Sub-test 1: ‘gps’ Sub-test 2: ‘glonass’ Sub-test 3: ‘galileo’ Sub-test 4: ‘gps’ Sub-test 5: ‘gps’ and ‘glonass’ Sub-test 8: ‘gps’ and ‘galileo’ Sub-test 9: ‘bds’ Sub-test 10: ‘gps’and’bds’ Sub-test 11: ‘gps’ and ‘glonass’ and ‘bds’ Sub-test 12: ‘gps’ and ‘galileo’ and ‘glonass’ Sub-test 13: ‘gps’ and ‘galileo’ and ‘bds’ |
|
>> fineTimeAssistanceMeasReq |
FALSE |
|
>> adrMeasReq |
FALSE |
|
>> multiFreqMeasReq |
TRUE or FALSE |
Depending on UE capabilities |
>> assistanceAvailability |
FALSE |
7.5.6 Test requirement
For the parameters specified in table 7.5.7 or 7.5.8 the UE shall meet the requirements and the success rate specified in table 7.5.10 or 7.5.11 after the first reported position estimates.
NOTES: 1. In the testing the UE may report error messages until it has been able to acquire GNSS measured results or a position estimate. The test equipment shall only consider the first measurement report different from an error message as the first position estimate in the requirement in table 7.5.10 or 7.5.11.
2. Due to the statistical nature of the results it is not possible to design a test with predefined confidence level for the success rate in table 7.5.10 or 7.5.11, therefore a simple PASS/FAIL of the results gathered against this success rate is used.
Table 7.5.7: Test parameters Moving scenario and periodic update – Sub-Test 1
Parameters |
Unit |
Value |
---|---|---|
Number of generated satellites |
– |
5 |
HDOP Range |
– |
1.8 to 2.5 |
Propagation condition |
– |
AWGN |
GPS L1 C/A Signal for all satellites |
dBm |
-130 |
Table 7.5.8: Test parameters Moving scenario and periodic update – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Parameters |
Unit |
Value |
---|---|---|---|
Number of generated satellites per system |
– |
See Table 7.5.9 |
|
Total number of generated satellites |
– |
6 or 7(2) |
|
HDOP Range per system |
– |
1.4 to 2.1 |
|
Propagation conditions |
– |
AWGN |
|
Galileo |
Reference signal power level for all satellites |
dBm |
-127 |
GPS(1) |
Reference signal power level for all satellites |
dBm |
-128.5 |
GLONASS |
Reference signal power level for all satellites |
dBm |
-131 |
BDS |
Reference signal power level for all satellites |
dBm |
-133 |
NOTE 1: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities. NOTE 2: 7 satellites are used for sub-tests with 3 different GNSSs |
Table 7.5.9: Satellite allocation
Satellite allocation for each constellation |
|||
GNSS 1(1) |
GNSS 2(1) |
GNSS 3(1) |
|
Single constellation |
6 |
— |
— |
Dual constellation |
3 |
3 |
— |
Triple constellation |
3 |
2 |
2 |
NOTE 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS. |
Table 7.5.10: Test requirements for Moving scenario and periodic update – Sub-Test 1
System |
Success rate |
2-D position error |
Periodical reporting interval |
---|---|---|---|
All |
95 % |
101.3 m |
Between 1.5 s and 2.5s |
Table 7.5.11: Test requirements for Moving scenario and periodic update – Sub-Tests 2 to 5 and Sub-Tests 8 to 13
System |
Success rate |
2-D position error |
Periodical reporting interval |
---|---|---|---|
All |
95 % |
51.3 m |
Between 1.5 s and 2.5s |
7.5A Moving scenario and periodic update (Rel-14 onwards)
7.5A.1 Sub-tests
Same as defined in clause 7.5.1.
7.5A.2 Test purpose
Same as defined in clause 7.5.2.
7.5A.3 Test applicability
This test applies to all types of E-UTRA UE with LPP Release 14 onwards that supports A-GNSS with periodical reporting, except Category M1 and Category M2 devices that do not support VoLTE.
NOTE: The capability to support periodical reporting is indicated in LPP [4] by either omitting the field periodicalReportingNotSupported-r14 in the LPP PROVIDE CAPABILITIES message, or by including the field periodicalReportingNotSupported-r14 in the LPP PROVIDE CAPABILITIES message but with bits for UE-assisted or UE-based mode set to zero.
7.5A.4 Minimum conformance requirements
Same as defined in clause 7.5.4.
7.5A.5 Test description
Same as defined in clause 7.5.5.
7.5A.6 Test requirement
Same as defined in clause 7.5.6.