6 UTRA A-GNSS Minimum Performance requirements

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

6.1 General

This clause defines the minimum performance requirements for both UE based and UE assisted A-GNSS UTRA UEs. If a UE supports both modes then it shall be tested in both modes. It excludes performance requirements for FDD UEs where the only A-GNSS supported is A-GPS L1 C/A which are specified in clause 5. It excludes performance requirements for TDD UEs where the only A-GNSS supported is A-GPS L1 C/A for which there is no requirement.

The requirements 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.

6.2 Sensitivity

6.2.1 Sensitivity Coarse Time Assistance

6.2.1.1 Definition and applicability

Sensitivity with coarse time assistance is the minimum level of GNSS satellite signals required for the UE to make an A-GNSS 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 UE that supports A-GNSS.

This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 6.2.1.1.

Table 6.2.1.1: Sub-Test Case Number Definition

Sub-Test Case Number

Supported GNSS

1

UE supporting A-GLONASS

2

UE supporting A-Galileo

3

UE supporting A-GPS and Modernized GPS

4

UE supporting A-GPS and A-GLONASS

8

UE supporting A-GPS and A-Galileo

9

UE supporting A-BDS

10

UE supporting A-GPS and A-BDS

6.2.1.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 6.2.1.2-3 for the parameters specified in table 6.2.1.2-1.

Table 6.2.1.2-1: Test parameters for Sensitivity Coarse Time Assistance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.2.1.2-2

Total number of generated satellites

6

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.

Table 6.2.1.2-2: 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

1

2

2

Note: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.

Table 6.2.1.2-3: Minimum requirements for Sensitivity Coarse Time Assistance

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.172 [19], clause 5.1.1.1, and 3GPP TS 25.173 [36], clause 5.1.1.1.

6.2.1.3 Test purpose

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

6.2.1.4 Method of test

6.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 GNSS test parameters as specified in table 6.2.1.5-1 for GNSS scenario #1. For GNSS-1, select the first satellite SV ID defined in the relevant table in 3GPP TS 37.571-5 [20] clause 6.2.1.2 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.

6.2.1.4.2 Procedure

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

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 6.2.2 and 6.2.7 for UE based testing; or clauses 6.2.4 and 6.2.7 for UE assisted testing with the value of GPS TOW msec or GANSS TOD offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 6.2.7.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.6 or 7.5.8.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 6.2.1.5-3 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 6.2.1.5-3 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 6.2.1.5-3 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GNSS 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 6.2.1.5-3 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 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 in 3GPP TS 37.571-5 [20] clause 6.2.1.2 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 or GANSS TOD offset in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 6.2.1.5 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 in 3GPP TS 37.571-5 [20] clause 6.2.1.2, for the one satellite with the higher level.

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

6.2.1.5 Test Requirements

For the parameters specified in table 6.2.1.5-1 the UE shall meet the requirements and the success rate specified in table 6.2.1.5-3 with a confidence level of 95% according to Annex D.

Table 6.2.1.5-1: Test parameters for Sensitivity Coarse Time Assistance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.2.1.5-2

Total number of generated satellites

6

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.

Table 6.2.1.5-2: 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

1

2

2

Note: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.

Table 6.2.1.5-3: 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

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.

6.2.2 Sensitivity Fine Time Assistance

6.2.2.1 Definition and applicability

Sensitivity with fine time assistance is the minimum level of GNSS satellite signals required for the UE to make an A-GNSS 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 UE that supports A-GNSS and that is capable of providing an enhanced performance when the network provides Fine Time Assistance.

This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 6.2.2.1.

Table 6.2.2.1: Sub-Test Case Number Definition

Sub-Test Case Number

Supported GNSS

1

UE supporting A-GLONASS

2

UE supporting A-Galileo

3

UE supporting A-GPS and Modernized GPS

4

UE supporting A-GPS and A-GLONASS

8

UE supporting A-GPS and A-Galileo

9

UE supporting A-BDS

10

UE supporting A-GPS and A-BDS

6.2.2.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 6.2.2.2-3 for the parameters specified in table 6.2.2.2-1.

Table 6.2.2.2-1: Test parameters for Sensitivity Fine Time Assistance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.2.2.2-2

Total number of generated satellites

6

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: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.2.2.2-2: Satellite allocation

Satellite allocation for each constellation

GNSS-1

GNSS-2

GNSS-3

Single constellation

6

Dual constellation

3

3

Triple constellation

2

2

2

Table 6.2.2.2-3: Minimum requirements for Sensitivity Fine Time Assistance

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.172 [19], clause 5.1.2.1, and 3GPP TS 25.173 [36], clause 5.1.2.1.

6.2.2.3 Test purpose

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

6.2.2.4 Method of test

6.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 GNSS test parameters as specified in table 6.2.2.5-1 for GNSS scenario #1.

3. Switch on the UE.

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

6.2.2.4.2 Procedure

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

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 6.2.2 and 6.2.7 for UE based testing; or clauses 6.2.4 and 6.2.7 for UE assisted testing with the values of GPS TOW msec or GANSS TOD, and UTRAN GPS timing of cell frames or UTRAN GANSS timing of cell frames offset by random values as specified in 3GPP TS 37.571-5 [20] clause 6.2.7.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.6 or 7.5.8.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 6.2.2.5-3 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 6.2.2.5-3 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 6.1.1.3. Compare the 2D position error against the value in table 6.2.2.5-3 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GNSS 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 6.1.1.3. Compare the 2D position error against the value in table 6.2.2.5-3 and record one Good Result or Bad Result as appropriate.

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

6. Repeat steps 1 to 5 until the statistical requirements of clause 6.2.2.5 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.

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

6.2.2.5 Test Requirements

For the parameters specified in table 6.2.2.5-1 the UE shall meet the requirements and the success rate specified in table 6.2.2.5-3 with a confidence level of 95% according to Annex D.

Table 6.2.2.5-1: Test parameters for Sensitivity Fine Time Assistance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.2.2.5-2

Total number of generated satellites

6

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: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.2.2.5-2: Satellite allocation

Satellite allocation for each constellation

GNSS-1

GNSS-2

GNSS-3

Single constellation

6

Dual constellation

3

3

Triple constellation

2

2

2

Table 6.2.2.5-3: 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

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.

6.3 Nominal Accuracy

6.3.1 Definition and applicability

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

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

This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 6.3.1.

Table 6.3.1: Sub-Test Case Number Definition

Sub-Test Case Number

Supported GNSS

1

UE supporting A-GLONASS

2

UE supporting A-Galileo

3

UE supporting A-GPS and Modernized GPS

4

UE supporting A-GPS and A-GLONASS

8

UE supporting A-GPS and A-Galileo

9

UE supporting A-BDS

10

UE supporting A-GPS and A-BDS

6.3.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 6.3.2-3 for the parameters specified in table 6.3.2-1.

Table 6.3.2-1: Test parameters for Nominal Accuracy

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.3.2-2

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

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.

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 6.3.2-2: 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

2

2

2

1

Note: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

Table 6.3.2-3: Minimum requirements for Nominal Accuracy

System

Success rate

2-D position error

Max response time

All

95 %

15 m

20 s

The reference for this requirement is 3GPP TS 25.172 [19], clause 5.2.1, and 3GPP TS 25.173 [36], clause 5.2.1.

6.3.3 Test purpose

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

6.3.4 Method of test

6.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 GNSS test parameters as specified in table 6.3.4.2 for GNSS scenario #3.

3. Switch on the UE.

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

6.3.4.2 Procedure

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

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 6.2.2 and 6.2.7 for UE based testing; or clauses 6.2.4 and 6.2.7 for UE assisted testing with the value of GPS TOW msec or GANSS TOD offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 6.2.7.2; using the exception to the RRC MEASUREMENT CONTROL message listed in table 6.3.5-1; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.6 or 7.5.8.

Table 6.3.4.2: Contents of RRC MEASUREMENT CONTROL message

Information Element

Value/Remark

– UE positioning reporting quantity

– Horizontal accuracy

’6’ (7.7m)

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 6.3.5-3 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 6.3.5-3 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 6.1.1.3. Compare the 2D position error against the value in table 6.3.5-3 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GNSS 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 6.1.1.3. Compare the 2D position error against the value in table 6.3.5-3 and record one Good Result or Bad Result as appropriate.

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

6. Repeat steps 1 to 5 until the statistical requirements of clause 6.3.5 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.

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

6.3.5 Test Requirements

For the parameters specified in table 6.3.5-1 the UE shall meet the requirements and the success rate specified in table 6.3.5-3 with a confidence level of 95% according to Annex D.

Table 6.3.5-1: Test parameters for Nominal Accuracy

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.3.5-3

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

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.

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 6.3.5-2: 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

2

2

2

1

Note: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

Table 6.3.5-3: Test requirements for Nominal Accuracy

System

Success rate

2-D position error

Max response time

All

95 %

16.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.

6.4 Dynamic Range

6.4.1 Definition and applicability

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

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

This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 6.4.1.

Table 6.4.1: Sub-Test Case Number Definition

Sub-Test Case Number

Supported GNSS

1

UE supporting A-GLONASS

2

UE supporting A-Galileo

3

UE supporting A-GPS and Modernized GPS

4

UE supporting A-GPS and A-GLONASS

8

UE supporting A-GPS and A-Galileo

9

UE supporting A-BDS

10

UE supporting A-GPS and A-BDS

6.4.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 6.4.2-3 for the parameters specified in table 6.4.2-1.

Table 6.4.2-1: Test parameters for Dynamic Range

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.4.2-2

Total number of generated satellites

6

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: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.4.2-2: 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

1

1

1

Note: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

Table 6.4.2-3: Minimum requirements for Dynamic Range

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.172 [19], clause 5.3.1, and 3GPP TS 25.173 [36], clause 5.3.1.

6.4.3 Test purpose

To verify the UE’s first position estimate meets the minimum requirements under GNSS 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.

6.4.4 Method of test

6.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 GNSS test parameters as specified in table 6.4.5-1 for GNSS scenario #1. Randomly select from the satellite SV IDs defined in the table in 3GPP TS 37.571-5 [20] clause 6.2.1.2 for the satellites with the higher levels.

3. Switch on the UE.

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

6.4.4.2 Procedure

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

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 6.2.2 and 6.2.7 for UE based testing; or clauses 6.2.4 and 6.2.7 for UE assisted testing with the value of GPS TOW msec or GANSS TOD offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 6.2.7.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.6 or 7.5.8.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 6.4.5-3 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 6.4.5-3 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 6.1.1.3. Compare the 2D position error against the value in table 6.4.5-3 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GNSS 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 6.1.1.3. Compare the 2D position error against the value in table 6.4.5-3 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 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 table in 3GPP TS 37.571-5 [20] clause 6.2.1.2 for the satellites with the higher levels. Use new random values for the UE location and altitude in step 1 and for the GPS TOW msec or GANSS TOD offset in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 6.4.5 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 set of satellite SV IDs defined in the table in 3GPP TS 37.571-5 [20] clause 6.2.1.2, for the satellites with the higher levels.

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

6.4.5 Test Requirements

For the parameters specified in table 6.4.5-1 the UE shall meet the requirements and the success rate specified in table 6.4.5-3 with a confidence level of 95% according to Annex D.

Table 6.4.5-1: Test parameters for Dynamic Range

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.4.5-2

Total number of generated satellites

6

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

-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

BSD

Reference high signal power level

dBm

-132.7

Reference low signal power level

dBm

-144

Note: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.4.5-2: 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

1

1

1

Note: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

Table 6.4.5-3: Test requirements for Dynamic Range

System

Success rate

2-D position error

Max response time

All

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.

6.5 Multi-path Performance

6.5.1 Definition and applicability

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

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

This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 6.5.1.

Table 6.5.1: Sub-Test Case Number Definition

Sub-Test Case Number

Supported GNSS

1

UE supporting A-GLONASS

2

UE supporting A-Galileo

3

UE supporting A-GPS and Modernized GPS

4

UE supporting A-GPS and A-GLONASS

8

UE supporting A-GPS and A-Galileo

9

UE supporting A-BDS

10

UE supporting A-GPS and A-BDS

6.5.2 Minimum requirements

The first fix position estimates shall meet the accuracy and response time requirements in table 6.5.2-3 for the parameters specified in table 6.5.2-1.

Table 6.5.2-1: Test parameters for Multi-path Performance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.5.2-2

Total number of generated satellites

6

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: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.5.2-2: 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

1

1

1

Note: One-tap channel: no multi-path. Two-tap channel: multi-path defined in clause 4.2.4

Table 6.5.2-3: Minimum requirements for Multi-path Performance

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

The reference for this requirement is 3GPP TS 25.172 [19], clause 5.4.1, and 3GPP TS 25.173 [36], clause 5.4.1.

6.5.3 Test purpose

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

6.5.4 Method of test

6.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 GNSS test parameters as specified in table 6.5.5-1 for GNSS scenario #1. Randomly select from the satellite SV IDs defined in the table in 3GPP TS 37.571-5 [20] clause 6.2.1.2 for the satellites with one-tap channel.

3. Switch on the UE.

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

6.5.4.2 Procedure

1. Start GNSS scenario #1 as specified in 3GPP TS 37.571-5 [20] clause 6.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 6.2.1.2.6. 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 6.2.2 and 6.2.7 for UE based testing; or clauses 6.2.4 and 6.2.7 for UE assisted testing with the value of GPS TOW msec or GANSS TOD offset by a random value as specified in 3GPP TS 37.571-5 [20] clause 6.2.7.2; as required to obtain a fix using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.6 or 7.5.8.

3. If the UE returns a valid result in the MEASUREMENT REPORT message within the Max response time specified in table 6.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 6.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 6.1.1.3. Compare the 2D position error against the value in table 6.5.5-4 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GNSS 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 6.1.1.3. Compare the 2D position error against the value in table 6.5.5-4 and record one Good Result or Bad Result as appropriate.

5. Repeat steps 1 to 4 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 table in 3GPP TS 37.571-5 [20] clause 6.2.1.2 for the satellites with one-tap channel. 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 or GANSS TOD offset in step 2.

6. Repeat steps 1 to 5 until the statistical requirements of clause 6.5.5 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 table in 3GPP TS 37.571-5 [20] clause 6.2.1.2, for the satellites with one-tap channel.

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

6.5.5 Test Requirements

For the parameters specified in table 6.5.5-1 the UE shall meet the requirements and the success rate specified in table 6.5.5-4 with a confidence level of 95% according to Annex D.

Table 6.5.5-1: Test parameters for Multi-path Performance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.5.5-2

Total number of generated satellites

6

HDOP range

1.4 to 2.1

Propagation conditions

AWGN

GNSS coarse time assistance error range

seconds

±1.8

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: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.5.5-2: 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

1

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 6.5.5-3.

Table 6.5.5-3: Relative mean Power (Y) for use in Table 6.5.5-2

System

Signals

Y [dB]

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

B1l

-4.7

Table 6.5.5-4: Test requirements for Multi-path Performance

System

Success rate

2-D position error

Max response time

All

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.

6.6 Moving Scenario and Periodic Update Performance

6.6.1 Definition and applicability

Moving scenario and periodic update performance measures the accuracy of the UE’s A-GNSS 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 UE that supports A-GNSS.

This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 6.6.1.

Table 6.6.1: Sub-Test Case Number Definition

Sub-Test Case Number

Supported GNSS

1

UE supporting A-GLONASS

2

UE supporting A-Galileo

3

UE supporting A-GPS and Modernized GPS

4

UE supporting A-GPS and A-GLONASS

8

UE supporting A-GPS and A-Galileo

9

UE supporting A-BDS

10

UE supporting A-GPS and A-BDS

6.6.2 Minimum requirements

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

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 6.6.2-1.

Table 6.6.2-1: Test parameters for Moving Scenario and Periodic Update Performance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.6.2-2

Total number of generated satellites

6

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: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.6.2-2: 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

2

2

2

Note: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

Table 6.6.2-3: Minimum requirements for Moving Scenario and Periodic Update Performance

System

Success rate

2-D position error

Periodical reporting interval

All

95 %

50 m

2 s

The reference for this requirement is 3GPP TS 25.172 [19], clause 5.5.1, and 3GPP TS 25.173 [36], clause 5.5.1.

6.6.3 Test purpose

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

6.6.4 Method of test

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

Table 6.6.4.1: 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 6.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 GNSS test parameters as specified in table 6.6.5-1 for GNSS scenario #5.

3. Switch on the UE.

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

6.6.4.2 Procedure

1. Start GNSS scenario #5 as specified in 3GPP TS 37.571-5 [20], clause 6.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 6.2.2 and 6.2.7 for UE based testing; or clauses 6.2.4 and 6.2.7 for UE assisted testing; using the exception to the RRC MEASUREMENT CONTROL message listed in table 6.6.4.2; as required to obtain fixes using the procedure specified in 3GPP TS 34.108 [28], clauses 7.5.7 or 7.5.9.

Table 6.6.4.2: Contents of RRC MEASUREMENT CONTROL message

Information Element

Value/Remark

– UE positioning reporting quantity

– Horizontal accuracy

’13’ (24.5m)

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

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

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

6. After the reception of the first GNSS measured result or position estimate reported in a MEASUREMENT REPORT message, every time the UE returns a GNSS 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 6.1.1.3. Compare the 2D position error against the value in table 6.6.9 and record one Good Result or Bad Result as appropriate; or

For UE assisted testing convert the GNSS 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 GNSS measured results and calculate the 2D position error as specified in clause 6.1.1.3. Compare the 2D position error against the value in table 6.6.9 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 GNSS 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 6.6.5.

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

6.6.5 Test Requirements

For the parameters specified in table 6.6.5-1, after the first reported position estimate, the UE shall meet the accuracy requirement and the success rate specified in table 6.6.5-3 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 6.6.5-3; therefore a simple PASS/FAIL of the results gathered against this success rate is used.

Table 6.6.5-1: Test parameters for Moving Scenario and Periodic Update Performance

System

Parameters

Unit

Value

Number of generated satellites per system

See Table 6.6.5-2

Total number of generated satellites

6

HDOP Range per system

1.4 to 2.1

Propagation conditions

AWGN

GNSS coarse time assistance error range

seconds

±1.8

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: "GPS" here means GPS L1 C/A, Modernized GPS, or both, dependent on UE capabilities.

Table 6.6.5-2: 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

2

2

2

Note: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

Table 6.6.5-3: Test requirements for Moving Scenario and Periodic Update Performance

System

Success rate

2-D position error

All

95 %

51.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 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 6.6.5-3.