6.1 GNSS Scenarios and Assistance Data for Assisted GNSS signalling tests
37.571-53GPPPart 5: Test scenarios and assistance dataRelease 16TSUser Equipment (UE) conformance specification for UE positioning
6.1.1 General
This subclause defines the GNSS scenario and the associated assistance data that shall be used where required for UTRA, E-UTRA and NR Assisted GNSS signalling tests defined in TS 37.571-2 [7] subclauses 6.2.1 to 6.2.3 and subclauses 7 and 9.
In all cases the Assistance Data is given in the two necessary formats, RRC format for TS 37.571-2 [7] subclauses 6.2.1 to 6.2.3 and LPP format for TS 37.571-2 [7] subclauses 7 and 9. Other information is also given separately for TS 37.571-2 [7] subclauses 6.2.1 to 6.2.3 and subclauses 7 and 9 where it differs between the subclauses.
The satellite simulator shall generate all the UE supported GNSS satellite signals defined in subclause 6.1.2 and/or shall provide assistance data dependent on the UE capabilities defined in subclause 6.1.3. Note that some tests require assistance data to be provided even though satellite signals are not required.
The A-GNSS signalling test cases may include several 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 below. In some cases the detailed assistance data content defined in subclause 6.1.3 depends on the particular sub-test case.
Table 6.1.1-1: Sub-Test Case Number Definition for TS 37.571-2 subclauses 6.2.1 to 6.2.3
|
Sub-Test Case Number |
Supported GNSS |
|
1 |
UE supporting A-GLONASS only |
|
2 |
UE supporting A-Galileo only |
|
3 |
UE supporting A-GPS and Modernized GPS only |
|
4 |
UE supporting A-GPS and A-GLONASS only |
|
8 |
UE supporting A-GPS and A-Galileo only |
|
9 |
UE supporting A-BDS only |
|
10 |
UE supporting A-GPS and A-BDS only |
Table 6.1.1-2: Sub-Test Case Number Definition for TS 37.571-2 subclauses 7 and 9
|
Sub-Test Case Number |
Supported GNSS |
|
1 |
Void |
|
2 |
Void |
|
3 |
Void |
|
4 |
Void |
|
7 |
UE supporting GNSS(1) and OTDOA |
|
8 |
Void |
|
9 |
Void |
|
10 |
Void |
|
15 |
UE supporting GNSS(1) |
|
Note 1: The GNSS combination of GPS, GLONASS, Galileo or BDS supported by the UE |
|
The term SV ID used in this subclause is defined as the satellite PRN for GPS, as Code Number for Galileo, as the satellite Slot Number for GLONASS and as the Ranging Code Number for BDS.
6.1.2 GNSS Scenario
Table 6.1.2-0: GNSS Scenarios to be used
|
Scenarios |
Condition |
|
GNSS scenarios from 2020 with the navigation data files defined in Table 6.1.2-1 and Table 6.1.2-2 and the SV IDs defined in Tables 6.1.2-2A to 6.1.2-4 |
px_GnssScenario2012 = FALSE |
|
GNSS scenarios from 2012 with the navigation data files defined in Table 6.1.2-5 and Table 6.1.2-6 and the SV IDs defined in Table 6.1.2-7 and Table 6.1.2-8 |
px_GnssScenario2012 = TRUE |
|
Note: the GNSS scenarios from 2012 may be used until September 2023. |
|
If px_GnssScenario2012 = FALSE, the following GNSS scenario shall be used. The assistance data specified in the following subclauses is consistent with this GNSS scenario:
– Rinex navigation data files: the required file(s) in the GNSS orbital data sig zip file specified in Annex B are given below.
Table 6.1.2-1: Rinex navigation data files for TS 37.571-2 subclauses 6.2.1 to 6.2.3
|
Sub-Test Case Number |
Rinex navigation datafile(s) |
|
1 |
Sig GNSS GLONASS 2020_9_17 Rinex.txt |
|
2 |
Sig GNSS Galileo 2020_9_17 Rinex.txt |
|
3 |
Sig GNSS GPS 2020_9_17 Rinex.txt |
|
4 |
Sig GNSS GPS 2020_9_17 Rinex.txt and Sig GNSS GLONASS 2020_9_17 Rinex.txt |
|
8 |
Sig GNSS GPS 2020_9_17 Rinex.txt and Sig GNSS Galileo 2020_9_17 Rinex.txt |
|
9 |
Sig GNSS BDS 2020_9_17 Rinex.txt |
|
10 |
Sig GNSS GPS 2020_9_17 Rinex.txt and Sig GNSS BDS 2020_9_17 Rinex.txt |
Table 6.1.2-2: Rinex navigation data files for TS 37.571-2 subclauses 7 and 9
|
Sub-Test Case Number |
GNSS supported by the UE |
Rinex navigation datafile(s) (1) |
|
7 |
[FFS] |
[FFS] |
|
15 |
GPS |
Sig GNSS GPS 2020_9_17 Rinex.txt |
|
GLONASS |
Sig GNSS GLONASS 2020_9_17 Rinex.txt |
|
|
Galileo |
Sig GNSS Galileo 2020_9_17 Rinex.txt |
|
|
BDS |
Sig GNSS BDS 2020_9_17 Rinex.txt |
|
|
Note 1: Where the UE supports more than one GNSS then all the relevant Rinex navigation data files are used |
||
– UE location and Reference location: Static at latitude: 35 degrees 44 minutes 39.432 seconds north, longitude: 139 degrees 40 minutes 48.633 seconds east, (Tokyo Japan), height: = 300m.
– Nominal start time: 17th September 2020 23:40:00 (GPS time).
– The visible satellites available for simulation and for which Assistance Data (other than Almanac) shall be generated are given in Table 6.1.2-2A.
Table 6.1.2-2A: SV IDs of Visible satellites
|
GNSS |
SV IDs of Visible satellites |
|
GPS |
3, 4, 6, 17, 19, 28 |
|
GLONASS |
3, 4, 5, 10, 18, 19 |
|
Galileo |
3, 5, 13, 15, 21, 27 |
|
BDS |
38, 40, 42, 43, 59, 60 |
– For BDS, the satellite types are given in Table 6.1.2-2B
Table 6.1.2-2B: BDS satellite types
|
BDS Satellite type |
SV IDs of Satellites |
|
GEO |
59, 60 |
|
IGSO |
38, 40 |
|
MEO |
42, 43 |
– The visible satellites to be simulated in each sub-test case are given in Table 6.1.2-3 and Table 6.1.2-4
Table 6.1.2-3: Satellites to be simulated for TS 37.571-2 subclauses 6.2.1 to 6.2.3
|
Sub-Test Case Number |
SV IDs of Satellites to be simulated |
|
1 |
3, 4, 5, 10, 18, 19 (GLONASS) |
|
2 |
3, 5, 13, 15, 21, 27 (Galileo) |
|
3 |
3, 4, 6, 17, 19, 28 (GPS) (Note) |
|
4 |
GPS: 3, 4, 6, 28. GLONASS: 5, 16, 18, 19. |
|
8 |
GPS: 3, 4, 6, 28. Galileo: 3, 5, 13, 21. |
|
9 |
38, 40, 42, 43, 59, 60 (BDS) |
|
10 |
GPS: 3, 4, 6, 28. BDS: 38, 40, 59, 60. |
|
Note: For this sub-test the satellite simulator shall generate all the GPS signals supported by the UE for all the simulated satellites. |
|
Table 6.1.2-4: Satellites to be simulated for TS 37.571-2 subclauses 7 and 9
|
Sub-Test Case Number |
GNSS supported by the UE |
SV IDs of Satellites to be simulated |
|
7 |
[FFS] |
[FFS] |
|
15 (Note) |
GPS |
3, 4, 6, 17, 19, 28 |
|
GLONASS |
3, 4, 5, 10, 18, 19 |
|
|
Galileo |
3, 5, 13, 15, 21, 27 |
|
|
BDS |
38, 40, 42, 43, 59, 60 |
|
|
Note: For this sub-test the satellite simulator shall generate all the GNSS signals supported by the UE for all the simulated satellites. |
||
If px_GnssScenario2012 = TRUE, the following GNSS scenario shall be used. The assistance data specified in the following subclauses is consistent with this GNSS scenario:
– Yuma Almanac data: the required file(s) in the GNSS data sig zip file specified in Annex B are given below.
Table 6.1.2-5: Yuma / AGL Almanac data files for TS 37.571-2 subclauses 6.2.1 to 6.2.3
|
Sub-Test Case Number |
Yuma / AGL file(s) |
|
1 |
Sig GNSS 1-1 AGL.txt |
|
2 |
Sig GNSS 1-2 Yuma.txt |
|
3 |
Sig GNSS 1-3 Yuma.txt |
|
4 |
Sig GNSS 1-3 Yuma.txt and Sig GNSS 1-1 AGL.txt |
|
8 |
Sig GNSS 1-3 Yuma.txt and Sig GNSS 1-2 Yuma.txt |
|
9 |
Sig GNSS 1-9 Yuma.txt |
|
10 |
Sig GNSS 1-3 Yuma.txt and Sig GNSS 1-9 Yuma.txt |
Table 6.1.2-6: Yuma / AGL Almanac data files for TS 37.571-2 subclauses 7 and 9
|
Sub-Test Case Number |
GNSS supported by the UE |
Yuma / AGL file(s) (1) |
|
7 |
[FFS] |
[FFS] |
|
15 |
GPS |
Sig GNSS 1-3 Yuma.txt |
|
GLONASS |
Sig GNSS 1-1 AGL.txt |
|
|
Galileo |
Sig GNSS 1-2 Yuma.txt |
|
|
BDS |
Sig GNSS 1-9 Yuma.txt |
|
|
Note 1: Where the UE supports more than one GNSS then all the relevant Yuma / AGL data files are used |
||
– UE location and Reference location:
Static at latitude: 35 degrees 44 minutes 39.432 seconds north, longitude: 139 degrees 40 minutes 48.633 seconds east, (Tokyo Japan 2012), height: = 300m.
– Nominal start time:
1st January 2012 00:31:00 (GPS time).
– Visible satellites simulated are given below
Table 6.1.2-7: Satellites to be simulated for TS 37.571-2 subclauses 6.2.1 to 6.2.3
|
Sub-Test Case Number |
SV IDs of Satellites to be simulated |
|
1 |
3, 4, 9, 10, 18, 20 |
|
2 |
5, 10, 11, 18, 19, 20 |
|
3 |
1, 11, 17, 20, 23, 28 (Note) |
|
4 |
GPS: 1, 17, 20, 28. GLONASS: 3, 10, 18, 20 |
|
8 |
GPS: 1, 17, 20, 28. Galileo: 5, 10, 11, 18. |
|
9 |
1, 2, 7, 18, 21, 27 |
|
10 |
GPS: 1, 17, 20, 28. BDS: 1, 7, 18, 21. |
|
Note: For this sub-test the satellite simulator shall generate all the GPS signals supported by the UE for all the simulated satellites. |
|
Table 6.1.2-8: Satellites to be simulated for TS 37.571-2 subclauses 7 and 9
|
Sub-Test Case Number |
GNSS supported by the UE |
SV IDs of Satellites to be simulated |
|
7 |
[FFS] |
[FFS] |
|
15 (Note) |
GPS |
1, 11, 17, 20, 23, 28 |
|
GLONASS |
3,4,9,10,18,20 |
|
|
Galileo |
5,10,11,18,19,20 |
|
|
BDS |
1,2,7,18,21,27 |
|
|
Note: For this sub-test the satellite simulator shall generate all the GNSS signals supported by the UE for all the simulated satellites. |
||
– Ionospheric model: see values in subclause 6.1.3
– The levels of the simulated satellites shall all be at -125dBm +/- 6dB
6.1.3 Assistance Data
This subclause defines the GNSS scenarios and assistance data IEs which shall be available for use where required in A-GNSS signalling test cases defined in TS 37.571-2 [7] subclauses 6.2.1 to 6.2.3 and subclauses 7 and 9.
6.1.3.1 Default Assistance Data for TS 37.571-2 subclauses 6.2.1 to 6.2.3
The assistance data listed in subclause 6.1.3.1 are the assistance data elements pushed by the SS in some tests defined in TS 37.571-2 [7] subclauses 6.2.1 to 6.2.3. During the test the UE may request additional assistance data as specified in the tests and the SS shall then provide any other assistance data available as defined in subclause 6.1.3.
Table 6.1.3.1-1: GNSS assistance data to be provided to the UE
|
GNSS Assistance Data IE to be provided to the UE |
Mode used in test case |
|
|
UE-based |
UE-assisted |
|
|
GPS reference time |
Yes for sub-tests 3, 4, 8, 10 |
Yes for sub-tests 3, 4, 8, 10 |
|
GPS reference UE position |
Yes for sub-tests 3, 4, 8, 10 |
No |
|
GPS navigation model |
Yes for sub-tests 3, 4, 8, 10 |
No |
|
GPS ionospheric model |
Yes for sub-tests 3, 4, 8, 10 |
No |
|
GPS UTC model |
Yes for sub-tests 4, 8 |
Yes for sub-tests 4, 8 |
|
GPS acquisition assistance |
No |
Yes for sub-tests 3, 4, 8, 10 |
|
GANSS reference time |
Yes for sub-tests 1, 2, 9 |
Yes for sub-tests 1, 2, 9 |
|
GANSS reference UE position |
Yes for sub-tests 1, 2, 9 |
No |
|
GANSS ionospheric model |
Yes for sub-tests 2, 8 |
No |
|
GANSS additional ionospheric model |
Yes for sub-tests 1, 9, 10 |
No |
|
GANSS Time Models |
Yes for sub-tests 4, 8, 10 |
No |
|
GANSS navigation model |
Yes for sub-tests 2, 8 |
No |
|
GANSS additional navigation models |
Yes for sub-tests 1, 4, 9, 10 |
No |
|
GANSS reference measurement information |
No |
Yes for sub-tests 1, 2, 4, 8, 9, 10 |
|
GANSS auxiliary information |
Yes for sub-tests 1, 4 (for GLONASS). Yes for sub-test 3 (for multiple GPS signals). Yes for sub-tests 4, 8, 10 if the UE supports multiple GPS signals |
Yes for sub-tests 1, 4 (for GLONASS). Yes for sub-test 3 (for multiple GPS signals). Yes for sub-tests 4, 8, 10 if the UE supports multiple GPS signals |
6.1.3.2 Assistance Data values for TS 37.571-2 subclauses 6.2.1 to 6.2.3
Assistance data that is marked as “time varying” and the GPS TOW msec or GANSS TOD field are created and used in 1 second increments.
The accuracy of the GPS TOW msec or GANSS TOD and assistance data that is marked as “time varying” in the provided assistance data shall be within +/- 2 s relative to the GNSS time in the system simulator. In the case that assistance data is required but satellite signals are not required then this clause does not apply.
Assistance data Information Elements and fields that are not specified shall not be used.
The information elements detailed below are fully defined in TS 25.331 [16]
6.1.3.2.1 Assistance Data GPS Reference Time
GPS Reference Time (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
Release |
|
GPS Week |
weeks |
Derived from data in clause 6.1.2 |
|
|
GPS Week Cycle Number |
Derived from data in clause 6.1.2 |
Rel-10 onwards |
|
|
GPS TOW msec |
msec |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
|
UE Positioning GPS Reference Time Uncertainty |
125 (2.127 seconds) |
||
|
Note: GPS TOW msec This is the value of GPS TOW msec when the GNSS scenario is started in the GNSS simulator. The value of GPS TOW msec to be used in the Reference Time IE shall be calculated at the time the IE is required by adding the elapsed time since the time the scenario was started in the GNSS simulator to this value, rounded up to the next 1 second interval. This “current GPS TOW msec” is then also used to determine the value of any other Information Elements marked as “Time varying” in subclause 6.1.3.2. In the case that the (hardware) GPS simulator is switched off or not present then the value of GPS TOW msec given above may be used. |
|||
6.1.3.2.2 Assistance Data GPS Reference UE Position
GPS Reference UE Position
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
Latitude sign |
Derived from data in clause 6.1.2 |
|
|
Degrees Of Latitude |
degrees |
Derived from data in clause 6.1.2 |
|
Degrees Of Longitude |
degrees |
Derived from data in clause 6.1.2 |
|
Altitude Direction |
Derived from data in clause 6.1.2 |
|
|
Altitude |
m |
Derived from data in clause 6.1.2 |
|
Uncertainty semi-major |
m |
3000 |
|
Uncertainty semi-minor |
m |
3000 |
|
Orientation of major axis |
degrees |
0 |
|
Uncertainty Altitude |
m |
500 |
|
Confidence |
% |
68 |
6.1.3.2.3 Assistance Data GPS Navigation Model
Satellite Information
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
GPS Navigation Model (Fields occurring once per satellite)
|
Information Element |
Units |
Value/remark |
|
SatID |
– |
Derived from data in clause 6.1.2 |
|
Satellite Status |
0 |
GPS Ephemeris and Clock correction Information Elements (Fields occurring once per satellite)
Derived from data in clause 6.1.2
6.1.3.2.4 Assistance Data GPS Ionospheric Model
GPS Ionospheric Model
Derived from data in clause 6.1.2
6.1.3.2.5 Assistance Data GPS UTC model
GPS UTC Model
Derived from data in clause 6.1.2 and the following information:
A1: 0
A0: 0
6.1.3.2.6 Assistance Data GPS Almanac
GPS Almanac (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
Release |
|
WNa |
weeks |
Derived from data in clause 6.1.2 |
|
|
Complete Almanac Provided |
TRUE |
Rel-10 onwards |
Satellite Information
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
31 |
GPS Almanac (Fields occurring once per satellite)
FFS
6.1.3.2.7 Assistance Data GPS Acquisition Assistance
GPS Acquisition Assist – Information Elements appearing once per message
|
Information Element |
Units |
Value/remark |
|
GPS TOW msec |
msec |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
UE Positioning GPS Reference Time Uncertainty |
125 (2.127 seconds) |
|
|
Note: GPS TOW msec |
||
Satellite Information
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
GPS Acquisition Assist – Information Elements appearing once per satellite
These fields are time varying (see clause 6.1.3.2) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
6.1.3.2.8 Assistance Data GANSS reference time
GANSS reference time: sub-test 1
|
Information Element |
Units |
Value/remark |
Release |
|---|---|---|---|
|
GANSS Day |
Derived from data in clause 6.1.2 |
||
|
GANSS Day Cycle Number |
Derived from data in clause 6.1.2 |
Rel-10 onwards |
|
|
GANSS TOD |
Seconds |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
|
GANSS TOD Uncertainty |
125 (2.127 seconds) |
||
|
GANSS Time ID |
2 (GLONASS) |
||
|
Note: GANSS TOD This is the value of GANSS TOD when the GNSS scenario is started in the GNSS simulator. The value of GANSS TOD to be used in the Reference Time IE shall be calculated at the time the IE is required by adding the elapsed time since the time the scenario was started in the GNSS simulator to this value, rounded up to the next 1 second interval. This “current GANSS TOD” is then also used to determine the value of any other Information Elements marked as “Time varying” in subclause 6.1.3.3. In the case that the (hardware) GNSS simulator is switched off or not present then the value of GANSS TOD given above may be used. |
|||
GANSS reference time: sub-test 2
|
Information Element |
Units |
Value/remark |
Release |
|---|---|---|---|
|
GANSS Day |
Derived from data in clause 6.1.2 |
||
|
GANSS Day Cycle Number |
Derived from data in clause 6.1.2 |
Rel-10 onwards |
|
|
GANSS TOD |
Seconds |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
|
GANSS TOD Uncertainty |
125 (2.127 seconds) |
||
|
GANSS Time ID |
Not present (Galileo) |
||
|
Note: GANSS TOD This is the value of GANSS TOD when the GNSS scenario is started in the GNSS simulator. The value of GANSS TOD to be used in the Reference Time IE shall be calculated at the time the IE is required by adding the elapsed time since the time the scenario was started in the GNSS simulator to this value, rounded up to the next 1 second interval. This “current GANSS TOD” is then also used to determine the value of any other Information Elements marked as “Time varying” in subclause 6.1.3.3. In the case that the (hardware) GNSS simulator is switched off or not present then the value of GANSS TOD given above may be used. |
|||
GANSS reference time: sub-test 9
|
Information Element |
Units |
Value/remark |
Release |
|---|---|---|---|
|
GANSS Day |
Derived from data in clause 6.1.2 |
||
|
GANSS Day Cycle Number |
Derived from data in clause 6.1.2 |
Rel-12 onwards |
|
|
GANSS TOD |
Seconds |
Start time is derived from data in clause 6.1.2. Add integer number of 1 second as required. (Note) |
|
|
GANSS TOD Uncertainty |
125 (2.127 seconds) |
||
|
GANSS Time ID |
3 (BDS system time) |
||
|
Note: GANSS TOD This is the value of GANSS TOD when the GNSS scenario is started in the GNSS simulator. The value of GANSS TOD to be used in the Reference Time IE shall be calculated at the time the IE is required by adding the elapsed time since the time the scenario was started in the GNSS simulator to this value, rounded up to the next 1 second interval. This “current GANSS TOD” is then also used to determine the value of any other Information Elements marked as “Time varying” in subclause 6.1.3.3. In the case that the (hardware) GNSS simulator is switched off or not present then the value of GANSS TOD given above may be used. |
|||
6.1.3.2.9 Assistance Data GANSS reference UE position
GANSS reference UE position
|
Information Element |
Units |
Value/remark |
|
Latitude sign |
Derived from data in clause 6.1.2 |
|
|
Degrees Of Latitude |
degrees |
Derived from data in clause 6.1.2 |
|
Degrees Of Longitude |
degrees |
Derived from data in clause 6.1.2 |
|
Altitude Direction |
Derived from data in clause 6.1.2 |
|
|
Altitude |
m |
Derived from data in clause 6.1.2 |
|
Uncertainty semi-major |
m |
3000 |
|
Uncertainty semi-minor |
m |
3000 |
|
Orientation of major axis |
degrees |
0 |
|
Uncertainty Altitude |
m |
500 |
|
Confidence |
% |
68 |
6.1.3.2.10 Assistance Data GANSS ionospheric model
Derived from data in clause 6.1.2
6.1.3.2.11 Assistance Data GANSS additional ionospheric model
GANSS additional ionospheric model (QZSS)
Derived from data in clause 6.1.2 and the following information:
Data Id: 00
GANSS additional ionospheric model (BDS)
Derived from data in clause 6.1.2 and the following information:
Data Id: 01
6.1.3.2.12 Assistance Data GANSS time model
GANSS time model (GLONASS)
|
Information Element |
Units |
Value/remark |
Release |
|
GANSS Time Model Reference Time |
s |
Derived from data in clause 6.1.2 |
|
|
TA0 |
Seconds |
0 |
|
|
GNSS_TO_ID |
0 (GPS) |
||
|
Delta_T |
Seconds |
Derived from data in clause 6.1.2 |
Rel-10 onwards |
GANSS time model (Galileo)
|
Information Element |
Units |
Value/remark |
Release |
|
GANSS Time Model Reference Time |
s |
Derived from data in clause 6.1.2 |
|
|
TA0 |
Seconds |
0 |
|
|
GNSS_TO_ID |
0 (GPS) |
||
|
Delta_T |
Seconds |
Derived from data in clause 6.1.2 |
Rel-10 onwards |
GANSS time model (BDS)
|
Information Element |
Units |
Value/remark |
Release |
|
GANSS Time Model Reference Time |
s |
Derived from data in clause 6.1.2 |
|
|
TA0 |
Seconds |
0 |
|
|
GNSS_TO_ID |
0 (GPS) |
||
|
Delta_T |
Seconds |
Derived from data in clause 6.1.2 |
Rel-12 onwards |
6.1.3.2.13 Assistance Data GANSS navigation model
GANSS navigation model (Galileo)
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
Non-Broadcast Indication |
Not present |
Satellite Information (Galileo)
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
Satellite Information (Fields occurring once per satellite) (Galileo)
|
Information Element |
Units |
Value/remark |
|
SatID |
Derived from data in clause 6.1.2 |
|
|
SV Health |
0 |
|
|
IOD |
Derived from data in clause 6.1.2 |
GANSS Clock Model (Fields occurring once per satellite) (Galileo)
GANSS Clock Model: Satellite clock model (Model 1)
Derived from data in clause 6.1.2
GANSS Orbit Model (Fields occurring once per satellite) (Galileo)
GANSS Orbit Model: Keplerian Parameters (Model 1)
Derived from data in clause 6.1.2
6.1.3.2.14 Assistance Data GANSS additional navigation models
GANSS additional navigation models (GLONASS)
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
Non-Broadcast Indication |
Not present |
Satellite Information (GLONASS)
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
Satellite Information (Fields occurring once per satellite) (GLONASS)
|
Information Element |
Units |
Value/remark |
|
SatID |
Derived from data in clause 6.1.2 |
|
|
SV Health |
000000 |
|
|
IOD |
Derived from data in clause 6.1.2 |
GANSS additional Clock Models (Fields occurring once per satellite) (GLONASS)
GANSS additional clock models: GLONASS Satellite Clock Model (Model 4)
Derived from data in clause 6.1.2
GANSS additional orbit models (Fields occurring once per satellite) (GLONASS)
GANSS additional orbit models: GLONASS Earth-Centered, Earth-fixed Parameters (Model 4)
Derived from data in clause 6.1.2
GANSS additional navigation model (BDS)
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
Non-Broadcast Indication |
Not present |
Satellite Information (BDS)
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
Satellite Information (Fields occurring once per satellite) (BDS)
|
Information Element |
Units |
Value/remark |
|
SatID |
Derived from data in clause 6.1.2 |
|
|
SV Health |
0 |
|
|
IOD |
Derived from data in clause 6.1.2 |
GANSS additional Clock Model (Fields occurring once per satellite) (BDS)
GANSS additional clock models: BDS Satellite Clock Model (Model 6)
Derived from data in clause 6.1.2
GANSS additional Orbit Models (Fields occurring once per satellite) (BDS)
GANSS additional orbit models: BDS Keplerian Parameters (Model 6)
Derived from data in clause 6.1.2
6.1.3.2.15 Assistance Data GANSS reference measurement information
GANSS reference measurement information: sub-tests 1 and 4 (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
|
GANSS Signal ID |
Not present |
Satellite Information
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
GANSS reference measurement information: sub-tests 1 and 4 (Fields occurring once per satellite)
These fields are time varying (see clause 6.1.3.2) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
GANSS reference measurement information: sub-tests 2 and 8 (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
|
GANSS Signal ID |
Not present |
Satellite Information
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
GANSS reference measurement information: sub-tests 2 and 8 (Fields occurring once per satellite)
These fields are time varying (see clause 6.1.3.2) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
GANSS reference measurement information: sub-tests 9 and 10 (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
|
GANSS Signal ID |
Not present |
Satellite Information
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
GANSS reference measurement information: sub-tests 9 and 10 (Fields occurring once per satellite)
These fields are time varying (see clause 6.1.3.2) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
6.1.3.2.16 Assistance Data GANSS almanac
GANSS almanac: sub-tests 1 and 4 (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
|
Week Number |
Weeks |
N/A |
Satellite Information GLO-KP: sub-tests 1 and 4
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
24 |
GANSS almanac: sub-tests 1 and 4 (Fields occurring once per satellite)
GLONASS Keplerian Parameters (Model 5)
FFS
GANSS almanac: sub-tests 2 and 8 (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
Release |
|
Week Number |
Weeks |
Derived from data in clause 6.1.2 |
|
|
Complete Almanac Provided |
TRUE |
Rel-10 onwards |
GANSS almanac: sub-tests 2 and 8 (Field occurring once per message)
|
Information Element |
Units |
Value/remark |
|
Toa |
Derived from data in clause 6.1.2 |
|
|
IODa |
Derived from data in clause 6.1.2 |
Satellite Information KP: sub-tests 2 and 8
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
29 |
GANSS almanac: sub-tests 2 and 8 (Fields occurring once per satellite)
Keplerian parameters (Model 1)
FFS
GANSS almanac: sub-tests 9 and 10 (Fields occurring once per message)
|
Information Element |
Units |
Value/remark |
Release |
|
Week Number |
Weeks |
Derived from data in clause 6.1.2 |
|
|
Complete Almanac Provided |
TRUE |
Rel-12 onwards |
GANSS almanac: sub-tests 9 and 10 (Field occurring once per message)
|
Information Element |
Units |
Value/remark |
|
Toa |
Derived from data in clause 6.1.2 |
|
|
IODa |
Not present |
Satellite Information BDS-KP: sub-tests 9 and 10
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
30 |
GANSS almanac: sub-tests 9 and 10 (Fields occurring once per satellite)
BDS Keplerian Parameters (Model 7)
FFS
6.1.3.2.17 Assistance Data GANSS auxiliary information
GANSS auxiliary information (Fields occurring once per message) (GLONASS)
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
GANSS-ID-3 |
Present (GLONASS) |
Aux Info List (GLONASS)
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
GANSS auxiliary information (Fields occurring once per satellite) (GLONASS)
|
Information Element |
Units |
Value/remark |
|
Sat ID |
Derived from data in clause 6.1.2 |
|
|
Signals Available |
G1 |
|
|
Channel Number |
Derived from data in clause 6.1.2 |
GANSS auxiliary information (Fields occurring once per message) (multiple GPS signals)
|
Information Element |
Units |
Value/remark |
|
GANSS-ID-1 |
Present (Modernized GPS) |
Aux Info List (multiple GPS signals)
|
Information Element |
Units |
Value/remark |
|
Number of satellites |
– |
6 |
GANSS auxiliary information (Fields occurring once per satellite) (multiple GPS signals)
|
Information Element |
Units |
Value/remark |
|
Sat ID |
Derived from data in clause 6.1.2 |
|
|
Signals Available |
As supported by the UE |
6.1.3.2.18 Assistance Data GANSS ID
GANSS ID: sub-tests 1 and 4
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
GANSS ID |
3 (GLONASS) |
GANSS ID: sub-tests 2 and 8
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
GANSS ID |
Not present (Galileo) |
GANSS ID: sub-test 3
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
GANSS ID |
1 (Modernized GPS) |
GANSS ID: sub-tests 9 and 10
|
Information Element |
Units |
Value/remark |
|---|---|---|
|
GANSS ID |
4 (BDS) |
6.1.3.3 Default Assistance Data for TS 37.571-2 subclauses 7 and 9
This subclause defines the GNSS assistance data elements which shall be provided to the UE in certain tests in TS 37.571-2 [7] subclauses 7 and 9 in the LPP Provide Assistance Data messages in the absence of a corresponding LPP Request Assistance Data message. The GNSS assistance data provided depends on the mode being used in the test case, the assistance data supported by the UE and the GNSS(s) supported by the UE. GNSS assistance data IEs not supported by the UE shall not be sent. GNSS assistance data IEs supported by the UE but not listed below shall not be sent.
Table 6.1.3.3-1: Default GNSS assistance data to be provided to the UE
|
GNSS Assistance Data IE supported by the UE |
Mode used in test case |
||
|
UE-based |
UE-assisted. GNSS-Acquisition Assistance supported by the UE |
UE-assisted. GNSS-Acquisition Assistance not supported by the UE |
|
|
GNSS-Reference Time |
Yes |
Yes |
Yes |
|
GNSS-ReferenceLocation |
Yes |
No |
Yes |
|
GNSS-IonosphericModel |
Yes |
No |
No |
|
GNSS-TimeModelList |
Yes(1) |
No |
Yes(1) |
|
GNSS-NavigationModel |
Yes |
No |
Yes |
|
GNSS-AcquisitionAssistance |
No |
Yes |
No |
|
GNSS-Almanac |
No |
No |
Yes |
|
GNSS-UTC-Model |
Yes(2) |
Yes(2) |
Yes(2 |
|
GNSS-AuxiliaryInformation |
Yes(3) |
Yes(3) |
Yes(3) |
|
Note1: Only if more than one GNSS supported by the UE Note2: Only if GLONASS and at least one other GNSS supported by the UE. Note3: Only if GLONASS supported by the UE, and/or if the UE supports multiple GPS signals and/or if BDS B1C supported by the UE. |
|||
6.1.3.4 Assistance Data values for TS 37.571-2 subclauses 7 and 9
Assistance data that is marked as “time varying” and the gnss-TimeOfDay field are created and used in 1 second increments.
The accuracy of the gnss-TimeOfDay and assistance data that is marked as “time varying” in the provided assistance data shall be within +/- 2 s relative to the GNSS time in the system simulator. In the case that assistance data is required but satellite signals are not required then this clause does not apply.
Assistance data Information Elements and fields that are not specified shall not be used.
The information elements detailed below are fully defined in TS 37.355 [8].
6.1.3.4.1 GNSS REFERENCE TIME:
GNSS-ReferenceTime: If GPS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-SystemTime |
||
|
gnss-TimeID |
0 (gps) |
|
|
gnss-DayNumber |
Derived from data in clause 6.1.2 |
|
|
gnss-TimeOfDay |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
|
gnss-TimeOfDayFrac-msec |
Not present |
|
|
notificationOfLeapSecond |
Not present |
|
|
gps-TOW-Assist |
||
|
satelliteID |
Derived from data in clause 6.1.2 |
|
|
tlmWord |
Derived from data in clause 6.1.2 |
|
|
antiSpoof |
1 (for all PRNs) |
|
|
alert |
0 (for all PRNs) |
|
|
tlmRsvdBits |
Derived from data in clause 6.1.2 |
|
|
referenceTimeUnc |
‘117’ (2.274 seconds) |
|
|
gnss-ReferenceTimeForCells |
Not present |
|
|
Note: gnss-TimeOfDay |
||
GNSS-ReferenceTime: If GLONASS is the only GNSS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-SystemTime |
||
|
gnss-TimeID |
4 (glonass) |
|
|
gnss-DayNumber |
Derived from data in clause 6.1.2 |
|
|
gnss-TimeOfDay |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
|
gnss-TimeOfDayFrac-msec |
Not present |
|
|
notificationOfLeapSecond |
00 |
|
|
gps-TOW-Assist |
Not present |
|
|
referenceTimeUnc |
‘117’ (2.274 seconds) |
|
|
gnss-ReferenceTimeForCells |
Not present |
|
|
Note: gnss-TimeOfDay |
||
GNSS-ReferenceTime: If Galileo is the only GNSS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-SystemTime |
||
|
gnss-TimeID |
3 (galileo) |
|
|
gnss-DayNumber |
Derived from data in clause 6.1.2 |
|
|
gnss-TimeOfDay |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
|
gnss-TimeOfDayFrac-msec |
Not present |
|
|
notificationOfLeapSecond |
Not present |
|
|
gps-TOW-Assist |
Not present |
|
|
referenceTimeUnc |
‘117’ (2.274 seconds) |
|
|
gnss-ReferenceTimeForCells |
Not present |
|
|
Note: gnss-TimeOfDay |
||
GNSS-ReferenceTime: If BDS is the only GNSS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-SystemTime |
||
|
gnss-TimeID |
5 (bds) |
|
|
gnss-DayNumber |
Derived from data in clause 6.1.2 |
|
|
gnss-TimeOfDay |
Start time is derived from data in clause 6.1.2. Add integer number of 1 seconds as required. (Note) |
|
|
gnss-TimeOfDayFrac-msec |
Not present |
|
|
notificationOfLeapSecond |
Not present |
|
|
gps-TOW-Assist |
Not present |
|
|
referenceTimeUnc |
‘117’ (2.274 seconds) |
|
|
gnss-ReferenceTimeForCells |
Not present |
|
|
Note: gnss-TimeOfDay |
||
6.1.3.4.2 GNSS REFERENCE LOCATION:
GNSS-ReferenceLocation
|
Information Element |
Units |
Value/remark |
|
threeDlocation |
Derived from data in clause 6.1.2 |
|
|
latitudeSign |
Derived from data in clause 6.1.2 |
|
|
degreesLatitude |
degrees |
Derived from data in clause 6.1.2 |
|
degreesLongitude |
degrees |
Derived from data in clause 6.1.2 |
|
altitudeDirection |
Derived from data in clause 6.1.2 |
|
|
altitude |
m |
Derived from data in clause 6.1.2 |
|
uncertaintySemiMajor |
m |
3000 |
|
uncertaintySemiMinor |
m |
3000 |
|
orientationMajorAxis |
degrees |
0 |
|
uncertaintyAltitude |
m |
500 |
|
confidence |
% |
68 |
6.1.3.4.3 GNSS IONOSPHERIC MODEL:
GNSS-IonosphericModel (Klobuchar Model): If GPS or GLONASS or BDS B1I supported by the UE
Derived from data in clause 6.1.2 and the following information:
dataID: 00
neQuickModel: not present unless Galileo is also supported by the UE
klobucharModel2: not present unless BDS B1C is also supported by the UE
GNSS-IonosphericModel (NeQuick Model): If Galileo supported by the UE
Derived from data in clause 6.1.2 and the following information:
klobucharModel: not present unless GPS or GLONASS or BDS B1I is also supported by the UE
klobucharModel2: not present unless BDS B1C is also supported by the UE
GNSS-IonosphericModel (Klobuchar2 Model): If BDS B1C supported by the UE
Derived from data in clause 6.1.2 and the following information:
klobucharModel: not present unless GPS or GLONASS or BDS B1I is also supported by the UE
neQuickModel: not present unless Galileo is also supported by the UE
6.1.3.4.4 GNSS TIME MODEL:
GNSS-TimeModelList: If GLONASS and GPS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-TimeModelRefTime |
seconds |
Derived from data in clause 6.1.2 |
|
tA0 |
0 |
|
|
gnss-TO-ID |
1 (GPS) |
|
|
weekNumber |
Derived from data in clause 6.1.2 |
|
|
deltaT |
Derived from data in clause 6.1.2 |
GNSS-TimeModelList: If Galileo and GPS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-TimeModelRefTime |
Seconds |
Derived from data in clause 6.1.2 |
|
tA0 |
0 |
|
|
gnss-TO-ID |
1 (GPS) |
|
|
weekNumber |
Derived from data in clause 6.1.2 |
|
|
deltaT |
Derived from data in clause 6.1.2 |
GNSS-TimeModelList: If BDS and GPS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-TimeModelRefTime |
seconds |
Derived from data in clause 6.1.2 |
|
tA0 |
0 |
|
|
gnss-TO-ID |
1 (GPS) |
|
|
weekNumber |
Derived from data in clause 6.1.2 |
|
|
deltaT |
Derived from data in clause 6.1.2 |
6.1.3.4.5 GNSS NAVIGATION MODEL:
GNSS-NavigationModel (Model-2): If GPS supported by the UE
|
Information Element |
Units |
Value/remark |
|
nonBroadcastFlag |
0 |
|
|
gnss-SatelliteList |
(SIZE) 6 |
GNSS-NavModelSatelliteElement (Model-2): If GPS supported by the UE
Derived from data in clause 6.1.2 and the following information:
GNSS-ClockModel: nav-ClockModel, Model-2
GNSS-OrbitModel: nav-KeplerianSet, Model-2
Note: in the case that the UE supports Modernized GPS then the UE may also support the GNSS-NavigationModel (Model-3), however in this case the GNSS-NavigationModel (Model-2) for GPS shall still be used.
GNSS-NavigationModel (Model-4): If GLONASS supported by the UE
|
Information Element |
Units |
Value/remark |
|
nonBroadcastFlag |
0 |
|
|
gnss-SatelliteList |
(SIZE) 6 |
GNSS-NavModelSatelliteElement (Model-4): If GLONASS supported by the UE
Derived from data in clause 6.1.2 and the following information:
svHealth: 00000000
GNSS-ClockModel: glonass-ClockModel, Model-4
GNSS-OrbitModel: glonass-ECEF, Model-4
GNSS-NavigationModel (Model-1): If Galileo supported by the UE
|
Information Element |
Units |
Value/remark |
|
nonBroadcastFlag |
0 |
|
|
gnss-SatelliteList |
(SIZE) 6 |
GNSS-NavModelSatelliteElement (Model-1): If Galileo supported by the UE
Derived from data in clause 6.1.2 and the following information:
svHealth: 0
GNSS-ClockModel: standardClockModelList, Model-1.
standardClockModelList: (SIZE) 1 if the UE supports only Galileo E1, (SIZE) 2 if the UE supports multiple Galileo signals.
StandardClockModelElement (I/NAV):
- stanClockTgd: Not present if the UE supports multiple Galileo signals.
- stanModelID: 0 (I/NAV). Present only if the UE supports multiple Galileo signals
StandardClockModelElement (F/NAV): Present only if the UE supports multiple Galileo signals
- stanClockTgd: Not present
- stanModelID: 1 (F/NAV)
GNSS-OrbitModel: keplerianSet, Model-1
GNSS-NavigationModel (Model-6): If BDS supported by the UE
|
Information Element |
Units |
Value/remark |
|
nonBroadcastFlag |
0 |
|
|
gnss-SatelliteList |
(SIZE) 6 |
GNSS-NavModelSatelliteElement (Model-6): If BDS supported by the UE
Derived from data in clause 6.1.2 and the following information:
svHealth: 0
GNSS-ClockModel: BDS-ClockModel-r12, Model-6
GNSS-OrbitModel: BDS-KeplerianSet-r12, Model-6
Note: in the case that the UE supports BDS B1C then the UE may also support the GNSS-NavigationModel (Model-7), however in this case the GNSS-NavigationModel (Model-6) for BDS shall still be used.
6.1.3.4.6 GNSS ACQUISITION ASSISTANCE:
In the case that the UE only supports GPS L1 C/A for GPS then the GNSS-AcquisitionAssistance (GPS L1 C/A) shall be used for GPS.
In the case that the UE supports Modernized GPS then the GNSS-AcquisitionAssistance to be used for GPS depends on the GNSS-AcquisitionAssistance(s) supported by the UE for GPS. The possible GNSS-AcquisitionAssistances are as follows:
GNSS-AcquisitionAssistance (GPS L1 C/A)
GNSS-AcquisitionAssistance (Modernized GPS L5)
The GNSS-AcquisitionAssistance to be used shall be determined by the PICs pc_GNSS_AcquAssist_GPS_L1CA and pc_GNSS_AcquAssist_GPS_L5, in the case that both GNSS-AcquisitionAssistances are supported by the UE then the GNSS-AcquisitionAssistance (GPS L1 C/A) shall be used.
GNSS-AcquisitionAssistance (GPS L1 C/A)
|
Information Element |
Units |
Value/remark |
|
GNSS-AcquisitionAssistance |
||
|
gnss-SignalID |
0 (GPS L1 C/A) |
|
|
gnss-AcquisitionAssistList |
(SIZE) 6 |
|
|
confidence-r10 |
% |
98 |
GNSS-AcquisitionAssistElement (GPS L1 C/A)
These fields are time varying (see clause 6.1.3.4) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
GNSS-AcquisitionAssistance (Modernized GPS L5)
|
Information Element |
Units |
Value/remark |
|
GNSS-AcquisitionAssistance |
||
|
gnss-SignalID |
3 (GPS L5) |
|
|
gnss-AcquisitionAssistList |
(SIZE) 6 |
|
|
confidence-r10 |
% |
98 |
GNSS-AcquisitionAssistElement (Modernized GPS L5)
These fields are time varying (see clause 6.1.3.4) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
GNSS-AcquisitionAssistance: If GLONASS supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-AcquisitionAssistance |
||
|
gnss-SignalID |
0 (GLONASS G1) |
|
|
gnss-AcquisitionAssistList |
(SIZE) 6 |
|
|
confidence-r10 |
% |
98 |
GNSS-AcquisitionAssistElement: If GLONASS supported by the UE
These fields are time varying (see clause 6.1.3.4) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
In the case that the UE only supports Galileo E1 for Galileo then the GNSS-AcquisitionAssistance (Galileo E1) shall be used for Galileo.
In the case that the UE supports more than one Galileo signal then the GNSS-AcquisitionAssistance to be used for Galileo depends on the GNSS-AcquisitionAssistance(s) supported by the UE for Galileo. The possible GNSS-AcquisitionAssistances are as follows:
GNSS-AcquisitionAssistance (Galileo E1)
GNSS-AcquisitionAssistance (Galileo E5A)
The GNSS-AcquisitionAssistance to be used shall be determined by the PICs pc_GNSS_AcquAssist_Galileo_E1 and pc_GNSS_AcquAssist_Galileo_E5A, in the case that both GNSS-AcquisitionAssistances are supported by the UE then the GNSS-AcquisitionAssistance (Galileo E1) shall be used.
GNSS-AcquisitionAssistance (Galileo E1)
|
Information Element |
Units |
Value/remark |
|
GNSS-AcquisitionAssistance |
||
|
gnss-SignalID |
0 (Galileo E1) |
|
|
gnss-AcquisitionAssistList |
(SIZE) 6 |
|
|
confidence-r10 |
% |
98 |
GNSS-AcquisitionAssistElement (Galileo E1)
These fields are time varying (see clause 6.1.3.4) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
GNSS-AcquisitionAssistance (Galileo E5A)
|
Information Element |
Units |
Value/remark |
|
GNSS-AcquisitionAssistance |
||
|
gnss-SignalID |
1 (Galileo E5A) |
|
|
gnss-AcquisitionAssistList |
(SIZE) 6 |
|
|
confidence-r10 |
% |
98 |
GNSS-AcquisitionAssistElement (Galileo E5A)
These fields are time varying (see clause 6.1.3.4) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
In the case that the UE only supports BDS B1I for BDS then the GNSS-AcquisitionAssistance (BDS B1I) shall be used for BDS.
In the case that the UE supports more than one BDS signal then the GNSS-AcquisitionAssistance to be used for BDS depends on the GNSS-AcquisitionAssistance(s) supported by the UE for BDS. The possible GNSS-AcquisitionAssistances are as follows:
GNSS-AcquisitionAssistance (BDS B1I)
GNSS-AcquisitionAssistance (BDS B1C)
The GNSS-AcquisitionAssistance to be used shall be determined by the PICs pc_GNSS_AcquAssist_BDS_B1I and pc_GNSS_AcquAssist_BDS_B1C, in the case that both GNSS-AcquisitionAssistances are supported by the UE then the GNSS-AcquisitionAssistance (BDS B1I) shall be used.
GNSS-AcquisitionAssistance (BDS B1I)
|
Information Element |
Units |
Value/remark |
|
GNSS-AcquisitionAssistance |
||
|
gnss-SignalID |
0 (BDS B1I) |
|
|
gnss-AcquisitionAssistList |
(SIZE) 6 |
|
|
confidence-r10 |
% |
98 |
GNSS-AcquisitionAssistElement (BDS B1I)
These fields are time varying (see clause 6.1.3.4) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
GNSS-AcquisitionAssistance (BDS B1C)
|
Information Element |
Units |
Value/remark |
|
GNSS-AcquisitionAssistance |
||
|
gnss-SignalID |
FFS |
|
|
gnss-AcquisitionAssistList |
(SIZE) 6 |
|
|
confidence-r10 |
% |
98 |
GNSS-AcquisitionAssistElement (BDS B1C)
These fields are time varying (see clause 6.1.3.4) and are derived from data in clause 6.1.2 and the following information:
Doppler uncertainty: 2.5 m/s
Code Phase Search Window: derived for each satellite using a 3 km radius UE position uncertainty
6.1.3.4.7 GNSS ALMANAC:
GNSS-Almanac (Model-2): If GPS supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-Almanac |
||
|
weekNumber |
Derived from data in clause 6.1.2 |
|
|
toa |
Derived from data in clause 6.1.2 |
|
|
ioda |
Not present |
|
|
completeAlmanacProvided |
1 (TRUE) |
|
|
gnss-AlmanacList |
(SIZE) 31 |
GNSS-AlmanacElement (Model-2): If GPS supported by the UE
FFS
GNSS-AlmanacElement:keplerianNAV-Almanac (Model-2)
Note: in the case that the UE supports Modernized GPS then the UE may also support the GNSS-Almanac (Model-3) and/or GNSS-Almanac (Model-4), however in this case the GNSS-Almanac (Model-2) for GPS shall still be used.
GNSS-Almanac (Model-5): If GLONASS supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-Almanac |
||
|
completeAlmanacProvided |
1 (TRUE) |
|
|
gnss-AlmanacList |
(SIZE) 24 |
GNSS-AlmanacElement (Model-5): If GLONASS supported by the UE
FFS
GNSS-AlmanacElement: keplerianGLONASS (Model-5)
GNSS-Almanac (Model-1): If Galileo supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-Almanac |
||
|
weekNumber |
Derived from data in clause 6.1.2 |
|
|
toa |
Derived from data in clause 6.1.2 |
|
|
ioda |
0 |
|
|
completeAlmanacProvided |
1 (TRUE) |
|
|
gnss-AlmanacList |
(SIZE) 29 |
GNSS-AlmanacElement (Model-1): If Galileo supported by the UE
FFS
GNSS-AlmanacElement: keplerianAlmanacSet (Model-1)
kepSV-StatusFNAV: 0. Present only if the UE supports multiple Galileo signals.
GNSS-Almanac (Model-7): If BDS supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-Almanac |
||
|
weekNumber |
Derived from data in clause 6.1.2 |
|
|
toa |
Derived from data in clause 6.1.2 |
|
|
ioda |
Not present |
|
|
completeAlmanacProvided |
1 (TRUE) |
|
|
gnss-AlmanacList |
(SIZE) 30 |
GNSS-AlmanacElement (Model-7): If BDS supported by the UE
FFS
GNSS-AlmanacElement: BDS-AlmanacSet-r12 (Model-7)
Note: in the case that the UE supports BDS B1C then the UE may also support the GNSS-Almanac (Model-3) and/or GNSS-Almanac (Model-4), however in this case the GNSS-Almanac (Model-7) for BDS shall still be used.
6.1.3.4.8 GNSS UTC MODEL:
GNSS-UTC-Model: If both GPS and GLONASS supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-UTC-Model |
||
|
utcModel1 |
UTC-ModelSet1: If both GPS and GLONASS supported by the UE
|
Information Element |
Units |
Value/remark |
|
gnss-Utc-A1 |
0 |
|
|
gnss-Utc-A0 |
0 |
|
|
gnss-Utc-Tot |
Derived from data in clause 6.1.2 |
|
|
gnss-Utc-WNt |
Derived from data in clause 6.1.2 |
|
|
gnss-Utc-DeltaTls |
Derived from data in clause 6.1.2 |
|
|
gnss-Utc-WNlsf |
Derived from data in clause 6.1.2 |
|
|
gnss-Utc-DN |
Derived from data in clause 6.1.2 |
|
|
gnss-Utc-DeltaTlsf |
Derived from data in clause 6.1.2 |
6.1.3.4.9 GNSS AUXILIARY INFORMATION:
GNSS-AuxiliaryInformation: If multiple GPS signals supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-AuxiliaryInformation |
||
|
gnss-ID-GPS |
(SIZE) 6 |
|
|
svID |
Derived from data in clause 6.1.2 |
|
|
signalsAvailable |
As supported by the UE |
GNSS-AuxiliaryInformation: If GLONASS supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-AuxiliaryInformation |
||
|
gnss-ID-GLONASS |
(SIZE) 6 |
|
|
svID |
Derived from data in clause 6.1.2 |
|
|
signalsAvailable |
G1 |
|
|
channelNumber |
Derived from data in clause 6.1.2 |
GNSS-AuxiliaryInformation: If BDS B1C supported by the UE
|
Information Element |
Units |
Value/remark |
|
GNSS-AuxiliaryInformation |
||
|
gnss-ID-BDS-r16 |
(SIZE) 6 |
|
|
svID-r16 |
Derived from data in clause 6.1.2 |
|
|
satType-r16 |
Derived from data in clause 6.1.2 |