5 A-GANSS minimum performance requirements

25.1723GPPRelease 17Requirements for support of Assisted Galileo and Additional Navigation Satellite Systems (A-GANSS) Frequency Division Duplex (FDD)TS

The A-GANSS minimum performance requirements are defined by assuming that all relevant and valid assistance data is received by the UE in order to perform GPS and GANSS measurements and/or position calculation. This clause does not include nor consider delays occurring in the various signalling interfaces of the network.

In the following subclauses the minimum performance requirements are based on availability of the assistance data information and messages defined in Annexes D and E.

The requirements in CELL_PCH and URA_PCH states are for further study.

5.1 Sensitivity

A sensitivity requirement is essential for verifying the performance of A-GANSS receiver in weak satellite signal conditions. In order to test the most stringent signal levels for the satellites the sensitivity test case is performed in AWGN channel. This test case verifies the performance of the first position estimate, when the UE is provided with only coarse time assistance and when it is additionally supplied with fine time assistance.

5.1.1 Coarse time assistance

In this test case 6 satellites are generated for the terminal. AWGN channel model is used.

Table 5.1.1-1: Test parameters

System

Parameters

Unit

Value

Number of generated satellites per system

–

See Table 5.1.1-2

Total number of generated satellites

–

6

HDOP range

1.4 to 2.1

Propagation conditions

–

AWGN

GANSS 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 5.1.1-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 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.

5.1.1.1 Minimum requirements (coarse time assistance)

The position estimates shall meet the accuracy and response time specified in table 5.1.1.1-1.

Table 5.1.1.1-1: Minimum requirements (coarse time assistance)

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

5.1.2 Fine time assistance

This requirement is only valid for fine time assistance capable UEs. In this requirement 6 satellites are generated for the terminal. AWGN channel model is used.

Table 5.1.2-1: Test parameters

System

Parameters

Unit

Value

Number of generated satellites per system

–

See Table 5.1.2-2

Total number of generated satellites

–

6

HDOP range

1.4 to 2.1

Propagation conditions

–

AWGN

GANSS coarse time assistance error range

seconds

2

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

Table 5.1.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

5.1.2.1 Minimum requirements (fine time assistance)

The position estimates shall meet the accuracy and response time requirements in table 5.1.2.1-1.

Table 5.1.2.1-1: Minimum requirements for fine time assistance capable terminals

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

5.2 Nominal accuracy

Nominal accuracy requirement verifies the accuracy of A-GANSS position estimate in ideal conditions. The primarily aim of the test is to ensure good accuracy for a position estimate when satellite signal conditions allow it. This test case verifies the performance of the first position estimate.

In this requirement 6 satellites are generated for the terminal. If SBAS is to be tested one additional satellite shall be generated. AWGN channel model is used. The number of simulated satellites for each constellation is as defined in table 5.2-2.

Table 5.2-1: Test parameters

System

Parameters

Unit

Value

Number of generated satellites per system

–

See Table 5.2-2

Total number of generated satellites

–

6 or 7(2)

HDOP Range

–

1.4 to 2.1

Propagation conditions

–

AWGN

GANSS 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 5.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 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

5.2.1 Minimum requirements (nominal accuracy)

The position estimates shall meet the accuracy and response time requirements in table 5.2.1-1.

Table 5.2.1-1: Minimum requirements

System

Success rate

2-D position error

Max response time

All

95 %

15 m

20 s

5.3 Dynamic range

The aim of a dynamic range requirement is to ensure that a GANSS receiver performs well when visible satellites have rather different signal levels. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross‑correlation products. Hence, it is important in this test case to keep use AWGN in order to avoid loosening the requirements due to additional margin because of fading channels. This test case verifies the performance of the first position estimate.

In this requirement 6 satellites are generated for the terminal. Two different reference power levels, denoted as "high" and "low" are used for each GNSS. The allocation of "high" and "low" power level satellites depends on the number of supported GNSSs and it is defined in Table 5.3-2. AWGN channel model is used.

Table 5.3-1: Test parameters

System

Parameters

Unit

Value

Number of generated satellites per system

–

See Table 5.3-2

Total number of generated satellites

–

6

HDOP Range

–

1.4 to 2.1

Propagation conditions

–

AWGN

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

Table 5.3-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 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

5.3.1 Minimum requirements (dynamic range)

The position estimates shall meet the accuracy and response time requirements in table 5.3.1-1.

Table 5.3.1-1: Minimum requirements

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

5.4 Multi-path scenario

The purpose of the test case is to verify the receiver’s tolerance to multipath while keeping the test setup simple. This test case verifies the performance of the first position estimate.

In this test 6 satellites are generated for the terminal. Some of the satellites have a one tap channel representing the Line-Of-Sight (LOS) signal. The other satellites have a two-tap channel, where the first tap represents the LOS signal and the second represents a reflected and attenuated signal as specified in Annex C.2. The number of satellites generated for each GNSS as well as the channel model used depends on the number of systems supported by the UE and is defined in table 5.4-2. The channel model as specified in Annex C.2 further depends on the generated signal.

Table 5.4-1: Test parameter

System

Parameters

Unit

Value

Number of generated satellites per system

–

See Table 5.4-2

Total number of generated satellites

–

6

HDOP range

1.4 to 2.1

Propagation conditions

–

AWGN

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

Table 5.4-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

5.4.1 Minimum requirements (multi-path scenario)

The position estimates shall meet the accuracy and response time requirements in table 5.4.1-1.

Table 5.4.1-1: Minimum requirements

System

Success rate

2-D position error

Max response time

All

95 %

100 m

20 s

5.5 Moving scenario and periodic update

The purpose of the test case is to verify the receiver’s capability to produce GANSS measurements or location fixes on a regular basis, and to follow when it is located in a vehicle that slows down, turns or accelerates. A good tracking performance is essential for certain location services. A moving scenario with periodic update is well suited for verifying the tracking capabilities of an A-GANSS receiver in changing UE speed and direction. In the requirement the UE moves on a rectangular trajectory, which imitates urban streets. AWGN channel model is used. This test is not performed as a Time to First Fix (TTFF) test.

In this requirement 6 satellites are generated for the terminal. The UE is requested to use periodical reporting with a reporting interval of 2 seconds.

The UE moves on a rectangular trajectory of 940 m by 1440 m with rounded corner defined in figure 5.5-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 5.5-1: 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

Figure 5.5-1: Rectangular trajectory of the moving scenario and periodic update test case

Table 5.5-2: Test Parameters

System

Parameters

Unit

Value

Number of generated satellites per system

–

See Table 5.5-3

Total number of generated satellites

–

6

HDOP Range per system

–

1.4 to 2.1

Propagation conditions

–

AWGN

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

Table 5.5-3: 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 1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.

5.5.1 Minimum requirements (moving scenario and periodic update)

The position estimates shall meet the accuracy requirement of table 5.5.1-1 with the periodical reporting interval defined in table 5.5.1-1 after the first reported position estimates.

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

Table 5.5.1-1: Minimum requirements

System

Success rate

2-D position error

Periodical reporting interval

All

95 %

50 m

2 s

Annex A (normative):
Test cases