5 UTRA A-GPS Minimum Performance requirements

37.571-13GPPPart 1: Conformance test specificationRelease 16TSUser Equipment (UE) conformance specification for UE positioning

5.1 General

This clause defines the minimum performance requirements for FDD UTRA UEs where the only Assisted Global Navigation Satellite System (A-GNSS) supported is Assisted Global Positioning System (A-GPS) L1 C/A. The procedures for UEs that support other or additional A-GNSSs are specified in clause 6. Note that for TDD UTRA UEs where the only Assisted Global Navigation Satellite System (A-GNSS) supported is Assisted Global Positioning System (A-GPS) L1 C/A there are no requirements.

This clause defines requirements for both UE based and UE assisted modes; if a UE supports both modes then it shall be tested in both modes

The requirements in this clause are defined for CELL_DCH and CELL_FACH states. All tests shall be performed in CELL_DCH state and the Nominal Accuracy Performance test case shall be also performed in CELL_FACH state.

5.2 Sensitivity

5.2.1 Sensitivity Coarse Time Assistance

5.2.1.1 Definition and applicability

Sensitivity with coarse time assistance is the minimum level of GPS satellite signals required for the UE to make an A-GPS position estimate to a specific accuracy and within a specific response time when the network only provides coarse time assistance.

The requirements and this test apply to all types of UTRA for the FDD UE that supports A-GPS.

5.2.1.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 5.2.1.2 for the parameters specified in table 5.2.1.1.

Table 5.2.1.1: Test parameters for Sensitivity Coarse Time Assistance

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 Signal for one satellite

dBm

-142

GPS Signal for remaining satellites

dBm

-147

Table 5.2.1.2: Minimum requirements for Sensitivity Coarse Time Assistance

Success rate

2-D position error

Max response time

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.171 [31], clause 5.1.1.1.

5.2.1.3 Test purpose

To verify the UE’s first position estimate meets the minimum requirements under GPS satellite signal conditions that represent weak signal conditions and with only Coarse Time Assistance provided by the SS.

5.2.1.4 Method of test

5.2.1.4.1 Initial conditions

Test environment: normal; see Annex G.

1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in figures A.1 or A.2.

2. Set the GPS test parameters as specified in table 5.2.1.3 for GPS scenario #1. Select the first satellite PRN defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5 for the one satellite with the higher level.

3. Switch on the UE.

4. Set up a connection using the procedure in clause F.2.

5.2.1.4.2 Procedure

1. Start GPS scenario #1 as specified in 3GPP TS 37.571-5 [20] clause 5.2.1.2 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 3GPP TS 37.571-5 [20] clause 5.2.1.2.4

2. Send a RESET UE POSITIONING STORED INFORMATION message followed by RRC MEASUREMENT CONTROL messages containing appropriate assistance data; as specified in 3GPP TS 37.571-5 [20], clauses 5.2.2 and 5.2.6 for UE based testing; or clauses 5.2.4 and 5.2.6 for UE assisted testing with the value of GPS TOW msec offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 5.2.6.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.1 or 7.5.4.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 5.2.1.4 then record the result and process it as specified in step 4. If the UE does not return a valid result within the Max response time specified in table 5.2.1.4 or reports a UE positioning error in the MEASUREMENT REPORT message then record one Bad Result.

4. For UE based testing compare the reported position estimate in the MEASUREMENT REPORT 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 5.2.1.4 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GPS measured results reported in the MEASUREMENT REPORT message to a 2D position using the method described in Annex B 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 5.2.1.4 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. Select the first satellite PRN defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5 for the one satellite with the higher level. Use new random values for the UE location and altitude in step 1 and for the GPS TOW msec offset in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 5.2.1.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS 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 select the next satellite PRN from the one used previously, defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5, for the one satellite with the higher level.

7. Release the connection using the procedure in clause F.3.

5.2.1.5 Test Requirements

For the parameters specified in table 5.2.1.3 the UE shall meet the requirements and the success rate specified in table 5.2.1.4 with a confidence level of 95% according to annex D.

Table 5.2.1.3: Test parameters for Sensitivity Coarse Time Assistance

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 Signal for one satellite

dBm

-141

GPS Signal for remaining satellites

dBm

-146

Table 5.2.1.4: Test requirements for Sensitivity Coarse Time Assistance

Success rate

2-D position error

Max response time

95 %

101.3 m

20.3 s

NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in clause C.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in clause C.4.

5.2.2 Sensitivity Fine Time Assistance

5.2.2.1 Definition and applicability

Sensitivity with fine time assistance is the minimum level of GPS satellite signals required for the UE to make an A-GPS position estimate to a specific accuracy and within a specific response time when the network provides fine time assistance in addition to coarse time assistance.

The requirements and this test apply to all types of UTRA for the FDD UE that supports only A-GPS and that is capable of providing an enhanced performance when the network provides Fine Time Assistance.

5.2.2.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 5.2.2.2 for the parameters specified in table 5.2.2.1.

Table 5.2.2.1: Test parameters for Sensitivity Fine Time Assistance

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 Fine Time assistance error range

μs

±10

GPS Signal for all satellites

dBm

-147

Table 5.2.2.2: Minimum requirements for Sensitivity Fine Time Assistance

Success rate

2-D position error

Max response time

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.171 [31], clause 5.1.2.1.

5.2.2.3 Test purpose

To verify the UE’s first position estimate meets the minimum requirements under GPS satellite signal conditions that represent weak signal conditions and with Fine Time Assistance provided by the SS.

5.2.2.4 Method of test

5.2.2.4.1 Initial conditions

Test environment: normal; see Annex G.

1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in figures A.1 or A.2.

2. Set the GPS test parameters as specified in table 5.2.2.3 for GPS scenario #1.

3. Switch on the UE.

4. Set up a connection using the procedure in clause F.2.

5.2.2.4.2 Procedure

1. Start GPS scenario #1 as specified in 3GPP TS 37.571-5 [20] clause 5.2.1.2 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 3GPP TS 37.571-5 [20] clause 5.2.1.2.4

2. Send a RESET UE POSITIONING STORED INFORMATION message followed by RRC MEASUREMENT CONTROL messages containing appropriate assistance data; as specified in 3GPP TS 37.571-5 [20], clauses 5.2.2 and 5.2.6 for UE based testing; or clauses 5.2.4 and 5.2.6 for UE assisted testing with the values of GPS TOW msec and UTRAN GPS timing of cell frames offset by random values as specified in 3GPP TS 37.571-5 [20] clause 5.2.6.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.1 or 7.5.4.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 5.2.2.4 then record the result and process it as specified in step 4. If the UE does not return a valid result within the Max response time specified in table 5.2.2.4 or reports a UE positioning error in the MEASUREMENT REPORT message then record one Bad Result.

4. For UE based testing compare the reported position estimate in the MEASUREMENT REPORT 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 5.2.2.4 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GPS measured results reported in the MEASUREMENT REPORT message to a 2D position using the method described in Annex B 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 5.2.2.4 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 using GPS 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 GPS TOW msec and UTRAN GPS timing of cell frames offsets in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 5.2.2.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS 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.

7. Release the connection using the procedure in clause F.3.

5.2.2.5 Test Requirements

For the parameters specified in table 5.2.2.3 the UE shall meet the requirements and the success rate specified in table 5.2.2.4 with a confidence level of 95% according to annex D.

Table 5.2.2.3: Test parameters for Sensitivity Fine Time Assistance

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 Signal for all satellites

dBm

-146

Table 5.2.2.4: Test requirements for Sensitivity Fine Time Assistance

Success rate

2-D position error

Max response time

95 %

101.3 m

20.3 s

NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in clause C.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in clause C.4.

5.3 Nominal Accuracy

5.3.1 Definition and applicability

Nominal accuracy is the accuracy of the UE’s A-GPS position estimate under ideal GPS signal conditions.

The requirements and this test apply to all types of UTRA for the FDD UE that supports A-GPS.

5.3.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 5.3.2 for the parameters specified in table 5.3.1.

Table 5.3.1: Test parameters for Nominal Accuracy

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 Signal for all satellites

dBm

-130

Table 5.3.2: Minimum requirements for Nominal Accuracy

Success rate

2-D position error

Max response time

95 %

30 m

20 s

The reference for this requirement is 3GPP TS 25.171 [31], clause 5.2.1.

5.3.3 Test purpose

To verify the UE’s first position estimate meets the minimum requirements under GPS satellite signal conditions that represent ideal conditions.

5.3.4 Method of test

5.3.4.1 Initial conditions

Test environment: normal; see Annex G.

1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in figures A.1 or A.2.

2. Set the GPS test parameters as specified in table 5.3.3 for GPS scenario #1.

3. Switch on the UE.

4. Set up a connection using the procedure in clause F.2.

5.3.4.2 Procedure

1. Start GPS scenario #1 as specified in 3GPP TS 37.571-5 [20] clause 5.2.1.2 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 3GPP TS 37.571-5 [20] clause 5.2.1.2.4

2. Send a RESET UE POSITIONING STORED INFORMATION message followed by RRC MEASUREMENT CONTROL messages containing appropriate assistance data; as specified in 3GPP TS 37.571-5 [20], clauses 5.2.2 and 5.2.6 for UE based testing; or clauses 5.2.4 and 5.2.6 for UE assisted testing with the value of GPS TOW msec offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 5.2.6.2; using the exception to the RRC MEASUREMENT CONTROL message listed in table 5.3.2A; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.1 or 7.5.4.

Table 5.3.2A: Contents of RRC MEASUREMENT CONTROL message

Information Element

Value/Remark

– UE positioning reporting quantity

– Horizontal accuracy

10 (15.9 m)

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 5.3.4 then record the result and process it as specified in step 4. If the UE does not return a valid result within the Max response time specified in table 5.3.4 or reports a UE positioning error in the MEASUREMENT REPORT message then record one Bad Result.

4. For UE based testing compare the reported position estimate in the MEASUREMENT REPORT 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 5.3.4 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GPS measured results reported in the MEASUREMENT REPORT message to a 2D position using the method described in Annex B 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 5.3.4 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 using GPS 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 GPS TOW msec offset in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 5.3.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS 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.

7. Release the connection using the procedure in clause F.3.

5.3.5 Test Requirements

For the parameters specified in table 5.3.3 the UE shall meet the requirements and the success rate specified in table 5.3.4 with a confidence level of 95% according to annex D.

Table 5.3.3: Test parameters for Nominal Accuracy

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 Signal for all satellites

dBm

-130

Table 5.3.4: Test requirements for Nominal Accuracy

Success rate

2-D position error

Max response time

95 %

31.3 m

20.3 s

NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in clause C.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in clause C.4.

5.4 Dynamic Range

5.4.1 Definition and applicability

Dynamic Range is the maximum difference in level of the GPS signals from a number of satellites that allows the UE to make an A-GPS position estimate with a specific accuracy and a specific response time.

The requirements and this test apply to all types of UTRA for the FDD UE that supports A-GPS.

5.4.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 5.4.2 for the parameters specified in table 5.4.1.

Table 5.4.1: Test parameters for Dynamic Range

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 Signal for 1st satellite

dBm

-129

GPS Signal for 2nd satellite

dBm

-135

GPS Signal for 3rd satellite

dBm

-141

GPS Signal for 4th satellite

dBm

-147

GPS Signal for 5th satellite

dBm

-147

GPS Signal for 6th satellite

dBm

-147

Table 5.4.2: Minimum requirements for Dynamic Range

Success rate

2-D position error

Max response time

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.171 [31], clause 5.3.1.

5.4.3 Test purpose

To verify the UE’s first position estimate meets the minimum requirements under GPS satellite signal conditions that have a wide dynamic range. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross-correlation products.

5.4.4 Method of test

5.4.4.1 Initial conditions

Test environment: normal; see Annex G.

1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in figures A.1 or A.2.

2. Set the GPS test parameters as specified in table 5.4.3 for GPS scenario #1. Select the first three satellite PRNs defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5 for the three satellites with the higher levels.

3. Switch on the UE.

4. Set up a connection using the procedure in clause F.2.

5.4.4.2 Procedure

1. Start GPS scenario #1 as specified in 3GPP TS 37.571-5 [20] clause 5.2.1.2 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 3GPP TS 37.571-5 [20] clause 5.2.1.2.4

2. Send a RESET UE POSITIONING STORED INFORMATION message followed by RRC MEASUREMENT CONTROL messages containing appropriate assistance data; as specified in 3GPP TS 37.571-5 [20], clauses 5.2.2 and 5.2.6 for UE based testing; or clauses 5.2.4 and 5.2.6 for UE assisted testing with the value of GPS TOW msec offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 5.2.6.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.1 or 7.5.4.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 5.4.4 then record the result and process it as specified in step 4. If the UE does not return a valid result within the Max response time specified in table 5.4.4 or reports a UE positioning error in the MEASUREMENT REPORT message then record one Bad Result.

4. For UE based testing compare the reported position estimate in the MEASUREMENT REPORT 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 5.4.4 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GPS measured results reported in the MEASUREMENT REPORT message to a 2D position using the method described in Annex B 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 5.4.4 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. Select the first three satellite PRNs defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5 for the three satellites with the higher levels. Use new random values for the UE location and altitude in step 1 and for the GPS TOW msec offset in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 5.4.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS 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, increment the set of three satellite PRNs by one from the ones used previously, defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5, for the three satellites with the higher levels (i.e. if the set of satellites is a, b, c, d, e, f and the first set used was a, b, c, the second set shall be b, c, d and so on).

7. Release the connection using the procedure in clause F.3.

5.4.5 Test Requirements

For the parameters specified in table 5.4.3 the UE shall meet the requirements and the success rate specified in table 5.4.4 with a confidence level of 95% according to annex D.

Table 5.4.3: Test parameters for Dynamic Range

Parameters

Unit

Value

Number of generated satellites

6

HDOP Range

1.4 to 2.1

GPS Coarse Time assistance error range

seconds

±2+TT

Propagation conditions

AWGN

GPS Signal for 1st satellite

dBm

-128.2

GPS Signal for 2nd satellite

dBm

-134

GPS Signal for 3rd satellite

dBm

-140

GPS Signal for 4th satellite

dBm

-146

GPS Signal for 5th satellite

dBm

-146

GPS Signal for 6th satellite

dBm

-146

Table 5.4.4: Test requirements for Dynamic Range

Success rate

2-D position error

Max response time

95 %

101.3 m

20.3 s

NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in clause C.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in clause C.4.

5.5 Multi-path Performance

5.5.1 Definition and applicability

Multi-path performance measures the accuracy and response time of the UE’s A-GPS position estimate in a specific GPS signal multi-path environment.

The requirements and this test apply to all types of UTRA for the FDD UE that supports A-GPS.

5.5.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 5.5.2 for the parameters specified in table 5.5.1.

Table 5.5.1: Test parameters for Multi-path Performance

Parameters

Unit

Value

Number of generated satellites (see note)

5

GPS Coarse Time assistance error range

seconds

±2

HDOP Range

1.8 to 2.5

GPS signal for Satellite 1, 2 (see note)

dBm

-130

GPS signal for Satellite 3, 4, 5 (see note)

dBm

LOS signal of -130 dBm, multi-path signal of -136 dBm

NOTE: Satellites 1, 2 no multi-path. Satellites 3, 4, 5 multi-path defined in clause 4.2.4.

Table 5.5.2: Minimum requirements for Multi-path Performance

Success rate

2-D position error

Max response time

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.171 [31], clause 5.4.1.

5.5.3 Test purpose

To verify the UE’s first position estimate meets the minimum requirements under GPS satellite signal conditions that represent simple multi-path conditions.

5.5.4 Method of test

5.5.4.1 Initial conditions

Test environment: normal; see Annex G.

1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in figures A.1 or A.2.

2. Set the GPS test parameters as specified in table 5.5.3 for GPS scenario #1. Select the first two satellite PRNs defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5 for the two satellites with the higher levels.

3. Switch on the UE.

4. Set up a connection using the procedure in clause F.2.

5.5.4.2 Procedure

1. Start GPS scenario #1 as specified in 3GPP TS 37.571-5 [20] clause 5.2.1.2 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 3GPP TS 37.571-5 [20] clause 5.2.1.2.4. The initial carrier phase difference between taps of the multi-path model shall be randomly selected between 0 and 2radians 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 followed by RRC MEASUREMENT CONTROL messages containing appropriate assistance data; as specified in 3GPP TS 37.571-5 [20], clauses 5.2.2 and 5.2.6 for UE based testing; or clauses 5.2.4 and 5.2.6 for UE assisted testing with the value of GPS TOW msec offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 5.2.6.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.1 or 7.5.4.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 5.5.4 then record the result and process it as specified in step 4. If the UE does not return a valid result within the Max response time specified in table 5.5.4 or reports a UE positioning error in the MEASUREMENT REPORT message then record one Bad Result.

4. For UE based testing compare the reported position estimate in the MEASUREMENT REPORT 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 5.5.4 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GPS measured results reported in the MEASUREMENT REPORT message to a 2D position using the method described in Annex B 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 5.5.4 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the UE shall have to use the new assistance data. Select the first two satellite PRNs defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5 for the two satellites with the higher levels. 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 GPS TOW msec offset in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 5.5.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS 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, increment the set of two satellite PRNs by one from the ones used previously, defined in the table in 3GPP TS 37.571-5 [20] clause 5.2.1.2.5, for the two satellites with the higher level (i.e. if the set of satellites is a, b, c, d, e and the first set used was a, b the second set shall be b, c and so on).

7. Release the connection using the procedure in clause F.3.

5.5.5 Test Requirements

For the parameters specified in table 5.5.3 the UE shall meet the requirements and the success rate specified in table 5.5.4 with a confidence level of 95% according to annex D.

Table 5.5.3: Test parameters for Multi-path Performance

Parameters

Unit

Value

Number of generated satellites (see note)

5

GPS Coarse Time assistance error range

seconds

±2+TT

HDOP Range

1.8 to 2.5

GPS signal for Satellite 1, 2 (see note)

dBm

-130

GPS 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 5.5.4: Test requirements for Multi-path Performance

Success rate

2-D position error

Max response time

95 %

101.3 m

20.3 s

NOTE: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in clause C.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in clause C.4.

5.6 Moving Scenario and Periodic Update Performance

5.6.1 Definition and applicability

Moving scenario and periodic update performance measures the accuracy of the UE’s A-GPS position estimates and the periodic update capability of the UE in a moving scenario.

The requirements and this test apply to all types of UTRA for the FDD UE that supports only A-GPS.

5.6.2 Minimum requirements

The position estimates, after the first reported position estimate, shall meet the accuracy requirement in table 5.6.2 with the periodical reporting interval of 2 seconds for the parameters specified in table 5.6.1.

NOTE: In the actual testing the UE may report error messages until it has been able to acquire GPS 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 5.6.2.

Table 5.6.1: Test parameters for Moving Scenario and Periodic Update Performance

Parameters

Unit

Value

Number of generated satellites

5

HDOP Range

1.8 to 2.5

Propagation condition

AWGN

GPS signal for all satellites

dBm

-130

Table 5.6.2: Minimum requirements for Moving Scenario and Periodic Update Performance

Success Rate

2-D position error

95 %

100 m

The reference for this requirement is 3GPP TS 25.171 [31], clause 5.5.1.

5.6.3 Test purpose

To verify the UE’s position estimates, after the first reported position estimate, meet the minimum requirements under GPS satellite signal conditions that simulate a moving scenario. A good tracking performance, with regular position estimate reporting is essential for certain location services.

5.6.4 Method of test

5.6.4.1 Initial conditions

Test environment: normal; see Annex G.

The UE is requested to use periodical reporting with a reporting interval of 2 seconds.

The GPS signals simulate the UE moving on a rectangular trajectory of 940 m by 1 440 m with rounded corners defined in figure 5.6.1 and table 5.6.3. 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.

Table 5.6.3: Trajectory Parameters for Moving Scenario and Periodic Update Performance test case

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

Figure 5.6.1: Rectangular Trajectory for Moving Scenario and Periodic Update Performance test case

1. Connect SS and GSS to the UE antenna connector or antenna connectors as shown in figures A.1 or A.2.

2. Set the GPS test parameters as specified in table 5.6.4 for GPS scenario #3.

3. Switch on the UE.

4. Set up a connection using the procedure in clause F.2.

5.6.4.2 Procedure

1. Start GPS scenario #3 as specified in 3GPP TS 37.571-5 [20], clause 5.2.1.2

2. Send a RESET UE POSITIONING STORED INFORMATION message followed by RRC MEASUREMENT CONTROL messages containing appropriate assistance data; as specified in 3GPP TS 37.571-5 [20], clauses 5.2.2 and 5.2.6 for UE based testing; or clauses 5.2.4 and 5.2.6 for UE assisted testing; as required to obtain fixes using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.2 or 7.5.5.

3. Ignore any error messages that the UE may report in MEASUREMENT REPORT messages until it has been able to acquire the GPS signals and reports the first GPS measured result or position estimate.

4. Discard the first GPS measured result or position estimate.

5. Record the time of reception of the next MEASUREMENT REPORT message after reception of the first GPS measured result or position estimate.

6. After the reception of the first GPS measured result or position estimate reported in a MEASUREMENT REPORT message, every time the UE returns a GPS measured result or position estimate in the MEASUREMENT REPORT 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 a UE positioning error in any MEASUREMENT REPORT messages, then record one Bad Result. Otherwise process the result as specified in step 7.

7. For UE based testing compare the reported position estimate in the MEASUREMENT REPORT message against the simulated position of the UE at the time of applicability reported in the position estimate and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 5.6.5 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GPS measured results reported in the MEASUREMENT REPORT message to a 2D position using the method described in Annex B and then compare the result against the simulated position of the UE at the time of applicability reported in the GPS measured results and calculate the 2D position error as specified in clause 4.5.2.3. Compare the 2D position error against the value in table 5.6.5 and record one Good Result or Bad Result as appropriate.

8. If the UE sends the first MEASUREMENT REPORT that contains a measured result or position estimate later than 240s after the start of the GPS scenario, fail the UE and stop the test early. Otherwise collect MEASUREMENT REPORTs during 900s, starting from the time recorded in step 5. 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 5.6.5.

9. Release the connection using the procedure in clause F.3.

5.6.5 Test Requirements

For the parameters specified in table 5.6.4, after the first reported position estimate, the UE shall meet the accuracy requirement and the success rate specified in table 5.6.5 with a periodical reporting interval of 2 seconds +/- 20% plus measurement system uncertainty of 100ms.

NOTE: 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 5.6.5, therefore a simple PASS/FAIL of the results gathered against this success rate is used.

Table 5.6.4: Test parameters for Moving Scenario and Periodic Update Performance

Parameters

Unit

Value

Number of generated satellites

5

HDOP Range

1.8 to 2.5

Propagation condition

AWGN

GPS signal for all satellites

dBm

-130

Table 5.6.5: Test requirements for Moving Scenario and Periodic Update Performance

Success Rate

2-D position error

95 %

101.3 m

NOTE 1: If the above Test Requirement differs from the Minimum Requirement then the Test Tolerance applied for this test is non-zero. The Test Tolerance for this test is defined in clause C.2 and the explanation of how the Minimum Requirement has been relaxed by the Test Tolerance is given in clause C.4.

NOTE 2: In the actual testing the UE may report error messages until it has been able to acquire GPS 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 5.6.5.