4.11 GNSS Requirements for V2X and MCS 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.11.1 General
This clause defines the GNSS scenarios and requirements which apply for all V2X and MCS 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.11.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 navigation data: 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.11.2-1.
Table 4.11.2-1: Rinex navigation data files for V2X and MCS 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(s) are given in Table 4.11.2-3
Longitude: the simulated longitude(s) are given in Table 4.11.2-3
Height: the simulated height is 30m
Motion: the simulated motion(s) are given in Table 4.11.2-2
Table 4.11.2-2: UE location(s) and motion(s) for V2X and MCS testing
|
Scenario number and description |
Step # |
Action (Location details given in Table 4.11.2-3) |
Notes |
|
Scenario #1: static in Geographical area #1 Note 1 |
1 |
Static at location #1 |
|
|
Scenario #2: move from inside Geographical area #1 to outside Geographical area #1 Note 1 |
1 |
Static at location #1 |
|
|
2 |
Trigger from test case to move in a straight line at 15m/s from current location to next location |
Simulation leaves Geographical area #1 after 905 m, 60s after the trigger. An additional 1s is added to allow for UE position accuracy of +/- 15m. An additional 10s is added to allow for UE position update. Total time 71s |
|
|
3 |
Static at location #2 |
||
|
Scenario #3: move from zone id0 to zone id1 to zone id3 to zone id2 |
1 |
Static at location #3 |
|
|
2 |
Trigger from test case to move in a straight line at 2m/s from current location to next location |
Simulation crosses the boundary between zone id0 and zone id1 47s after the trigger. An additional 7.5s is added to allow for UE position accuracy of +/- 15m. An additional 10s is added to allow for UE position update. Total time 64.5s |
|
|
3 |
Static at location #4 |
||
|
4 |
Trigger from test case to move in a straight line at 2m/s from current location to next location |
Simulation crosses the boundary between zone id1 and zone id3 42s after the trigger. An additional 7.5s is added to allow for UE position accuracy of +/- 15m. An additional 10s is added to allow for UE position update. Total time 59.5s |
|
|
5 |
Static at location #5 |
||
|
6 |
Trigger from test case to move in a straight line at 2m/s from current location to next location |
Simulation crosses the boundary between zone id3 and zone id2 47s after the trigger. An additional 7.5s is added to allow for UE position accuracy of +/- 15m. An additional 10s is added to allow for UE position update. Total time 64.5s |
|
|
7 |
Static at location #6 |
||
|
Scenario #4: move from inside Geographical area #1 to location #7 and then location #8 inside Geographical area #1 Note 1 |
1 |
Static at location #1 |
|
|
2 |
Trigger from test case to move in a straight line at 10m/s from current location to next location |
Simulation takes approximately 10 secs to move from location #1 to location #7 |
|
|
3 |
Static at location #7 |
||
|
4 |
Trigger from test case to move in a straight line at 10m/s from current location to next location |
Simulation takes approximately 10 secs to move from location #7 to location #8 |
|
|
5 |
Static at location #8 |
||
|
Note 1: Geographical area #1 is defined in clause 4.9.3.1 and is defined by four points with the following coordinates: Point 1: latitude: 35.753056, longitude: 139.689167 Point 2: latitude: 35.735278, longitude: 139.689167 Point 3: latitude: 35.744167, longitude: 139.709167 Point 4: latitude: 35.753056, longitude: 139.709167 |
|||
Table 4.11.2-3: Location descriptions for V2X and MCS testing
|
Location number |
Description for information only |
Latitude (degrees) |
Longitude (degrees) |
|
#1 |
Approximate centre of Geographical area #1 |
35.74428 |
139.69916 |
|
#2 |
Approximately 1720m due west of location #1, outside Geographical area #1 |
35.74428 |
139.68017 |
|
#3 |
Centre of zone id0 inside Geographical area #1, see Table 4.11.2-4 and Figure 4.11.2-1 |
35.74478 |
139.70333 |
|
#4 |
Centre of zone id1 inside Geographical area #1, see Table 4.11.2-4 and Figure 4.11.2-1 |
35.74478 |
139.70540 |
|
#5 |
Centre of zone id3 inside Geographical area #1, see Table 4.11.2-4 and Figure 4.11.2-1 |
35.74523 |
139.70716 |
|
#6 |
Centre of zone id2 inside Geographical area #1, see Table 4.11.2-4 and Figure 4.11.2-1 |
35.74523 |
139.70508 |
|
#7 |
Approximately 100m due west of location #1, inside Geographical area #1 |
35.74428 |
139.69806 |
|
#8 |
Approximately 100m due west of location #7, inside Geographical area #1 |
35.74428 |
139.69695 |
Table 4.11.2-4: Zone id calculations for V2X testing
|
Description |
Latitude (degrees) |
Longitude (degrees) |
Long distance from 0,0 in m (x) Note 1 |
Lat distance from 0,0 in m (y) Note 1 |
Values for zone_id calculation (Nx, Ny = 2, L = 100, W = 50 Note 2) Note 3 |
|
Centre of zone id0 |
35.74478 |
139.70333 |
11061850 |
3957225 |
y1= 0, x1= 0 |
|
Centre of zone id1 |
35.74478 |
139.70540 |
11061950 |
3957225 |
y1= 0, x1= 1 |
|
Centre of zone id2 |
35.74523 |
139.70508 |
11061850 |
3957275 |
y1= 1, x1= 0 |
|
Centre of zone id3 |
35.74523 |
139.70716 |
11061950 |
3957275 |
y1= 1, x1= 1 |
|
Note 1: all distances are +/- 1m Note 2: zone length (longitude) is set to 100m, zone width (latitude) is set to 50m in accordance with TS 36.523-1 [18] Table 24.1.8.3.3-1 and Table 24.1.9.3.3-1, this allows for the accuracy with which a UE can define its position which is assumed to be +/- 15m. Zone id longitude modulus and zone id latitude modulus are set to 2 in accordance with TS 36.523-1 [18] Table 24.1.8.3.3-1 and Table 24.1.9.3.3-1. Note 3: zone ids are calculated according to TS 36.331 [17] clause 5.10.13.2 |
|||||
Figure 4.11.2-1: Zones and motions for scenario #3 for V2X testing (not to scale)
– Nominal start time:
17th September 2020 23:40:00 (GPS time)\
– Visible satellites to be simulated are given in Table 4.11.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.11.2-5: Satellites to be simulated for V2X and MCS 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 |
|
As an alternative, the contents of this clause in version 16.8.0 of this current specification may be used until September 2023.
– The levels of the simulated satellites are given in Table 4.11.2-6 and shall be generated with an accuracy of +/- 3 dB. These conditions are defined for when there is no GNSS assistance data available at the UE and are specified in TS 36.133 [39] clause B.6.
Table 4.11.2-6: GNSS Reference Signal Power Requirements
|
System |
Parameters |
Unit |
Value |
|---|---|---|---|
|
Number of generated satellites per system |
– |
6 |
|
|
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 |
|
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: The DUT UE shall support at least one system and will be configured for the supported system(s). |
|||
– Ionospheric model: simulated values are given in Tables 4.11.2-7 and 4.11.2-8.
Table 4.11.2-7: Klobuchar ionospheric model for GPS or GLONASS or BDS if supported by the UE
|
Model element |
Units |
Value/remark |
|
alfa0 |
seconds |
4.6566129 10E-9 |
|
alfa1 |
sec/semi-circle |
1.4901161 10E-8 |
|
alfa2 |
sec/(semi-circle)2 |
-5.96046 10E-8 |
|
alfa3 |
sec/(semi-circle)3 |
-5.96046 10E-8 |
|
beta0 |
seconds |
79872 |
|
beta1 |
sec/semi-circle |
65536 |
|
beta2 |
sec/(semi-circle)2 |
-65536 |
|
beta3 |
sec/(semi-circle)3 |
-393216 |
Table 4.11.2-8: neQuick ionospheric model for Galileo if supported by the UE
|
Model Element |
Units |
Value/remark |
|
ai0 |
solar flux unit |
64.4 |
|
ai1 |
solar flux unit/degree |
0 |
|
ai2 |
solar flux unit/degree2 |
0 |
– 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 instead.
– 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.11.2-1.
Table 4.11.2-9: Yuma / Rinex Almanac data files for V2X and MCS testing
|
GNSS supported by UE |
Yuma / Rinex file(s) (1) |
|
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 |
|
– Nominal start time:
1st January 2012 00:31:00 (GPS time) (UTC time: TBD).
– Visible satellites to be simulated are given in Table 4.11.2-10 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.11.2-10: Satellites to be simulated for V2X and MCS testing
|
GNSS supported by UE |
SV IDs of Satellites to be simulated (1) |
|
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 1: Where the UE supports more than one GNSS then all the relevant satellites are simulated |
|