4.12 GNSS Requirements for aerial testing
36.5083GPPCommon test environments for User Equipment (UE) conformance testingEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Release 17TS
4.12.1 General
This clause defines the GNSS scenarios and requirements which apply for all aerial test cases that require simulated GNSS signals, unless otherwise specified.
The term SV ID used in this clause is defined as the satellite PRN for GPS and Modernized GPS, as Code Number for Galileo, as the satellite Slot Number for GLONASS and as the Ranging Code Number for BDS.
4.12.2 GNSS Scenarios
The PIXIT px_GnssScenario2012 is specified in TS 37.571-5 [68] clause 6.1.2.
If px_GnssScenario2012 = FALSE, the following GNSS scenarios shall be used.
– Rinex navigationdata: the required navigation data file(s) available in the GNSS orbital data sig zip file specified in TS 37.571-5 [68] Annex B are given in Table 4.12.2-0.
Table 4.12.2-0: Rinex navigation data files for Aerial testing
|
GNSS supported by UE |
Rinex file(s) (1) |
|
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(s) and motion:
Latitude: the simulated latitude is given in Table 4.12.2-2
Longitude: the simulated longitude is given in Table 4.12.2-2
Height: the simulated heights above sea level are given in Table 4.12.2-2
Motion: the simulated motion(s) are given in Table 4.12.2-1
Table 4.12.2-1: UE locations and motions for aerial testing
|
Scenario number and description |
Step # |
Action (Location details given in Table 4.12.2-2) |
Notes |
|
Scenario #1: move from location #1 to location #2 to location #3 |
1 |
Static at location #1 |
|
|
2 |
Trigger from test case to move in a straight line at 5m/s from current location to next location |
||
|
3 |
Static at location #2 |
||
|
4 |
Trigger from test case to move in a straight line at 5m/s from current location to next location |
Simulation will take 40 seconds to move between locations given the nominal values specified in the test case. An additional 10 seconds is added to allow for UE position update. Total time 50 seconds. |
|
|
5 |
Static at location #3 |
Table 4.12.2-2: Location descriptions for aerial testing
|
Location number |
Latitude (degrees) |
Longitude (degrees) |
Height above sea level (m) |
Notes |
|
#1 |
43.308318 |
-5.697122 |
See test case |
|
|
#2 |
43.308318 |
-5.697122 |
See test case |
|
|
#3 |
43.308318 |
-5.697122 |
See test case |
– Nominal start time:
Current date at 07:31:00 (GPS time).
– Visible satellites to be simulated are given in Table 4.12.2-3 and are above 15 degrees elevation with respect to the UE. These satellites have been selected to give a reasonable HDOP for the duration of the test.
Table 4.12.2-3: Satellites to be simulated for Aerial testing
|
GNSS supported by UE |
SV IDs of Satellites to be simulated (1) |
|
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 1: Where the UE supports more than one GNSS then all the relevant satellites are simulated Note 2: For BDS, the satellite types are as follows: GEO: 59, 60, IGSO: 38, 40, MEO: 42, 43 |
|
– The levels of the simulated satellites are given in Table 4.11.2-6 and shall be generated with an accuracy of +/- 3 dB.
– Ionospheric model: simulated values are given in Tables 4.11.2-7 and 4.11.2-8.
– Tropospheric model: STANAG with SRI equal to 324.8, as defined in STANAG 4294 [70].
If px_GnssScenario2012 = TRUE, the following GNSS scenarios shall be used.
– Yuma / Rinex Almanac data: the required file(s) available in the GNSS data sig zip file specified in TS 37.571-5 [68] Annex B are given in Table 4.12.2-4.
Table 4.12.2-4: Yuma / Rinex Almanac data files for Aerial testing
|
GNSS supported by UE |
Yuma / Rinex file(s) (1) |
|
GPS |
globalAlmanac_gpsYuma.txt |
|
GLONASS |
globalAlmanac_glonass.agl |
|
Galileo |
globalAlmanac_galileo.xml |
|
BDS |
Navmodel_beidou.rnx |
|
Note 1: Where the UE supports more than one GNSS then all the relevant Yuma / Rinex data files are used |
|
– UE location(s) and motion:
Latitude: the simulated latitude is given in Table 4.12.2-2
Longitude: the simulated longitude is given in Table 4.12.2-2
Height: the simulated heights above sea level are given in Table 4.12.2-2
Motion: the simulated motion(s) are given in Table 4.12.2-1
– Nominal start time:
Current date at 07:31:00 (GPS time).
– Visible satellites to be simulated are given in Table 4.12.2-5 and are above 15 degrees elevation with respect to the UE. These satellites have been selected to give a reasonable HDOP for the duration of the test.
Table 4.12.2-5: Satellites to be simulated for Aerial testing
|
GNSS supported by UE |
SV IDs of Satellites to be simulated (1) |
|
GPS |
2, 12, 14, 24, 25, 29 |
|
GLONASS |
4, 5, 13, 14, 15, 23 |
|
Galileo |
2, 7, 8, 11, 19, 30 |
|
BDS |
13, 15, 19, 27, 28, 30 |
|
Note 1: Where the UE supports more than one GNSS then all the relevant satellites are simulated |
|
– The levels of the simulated satellites are given in Table 4.11.2-6 and shall be generated with an accuracy of +/- 3 dB.
– Ionospheric model: simulated values are given in Tables 4.11.2-7 and 4.11.2-8.
– Tropospheric model: STANAG with SRI equal to 324.8, as defined in STANAG 4294 [70].