4.11 GNSS Requirements for NR sidelink
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
4.11.1 General
This clause defines the GNSS scenarios and requirements which apply for all NR sidelink 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 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 [49] Annex B are given in Table 4.11.2-1.
Table 4.11.2-1: Rinex navigation data files for NR sidelink testing
|
GNSS supported by UE |
Rinex navigation 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 NR sidelink 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 |
||
|
Note 1: Geographical area #1 is defined in clause 4.7.5.5-9 and is defined by three 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 |
|||
Table 4.11.2-3: Location descriptions for NR sidelink 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 |
Table 4.11.2-4: Zone id calculations for NR sidelink 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 (Note 2, Note 3) |
|
Centre of zone |
35.74478 |
139.70333 |
11061850 |
3957225 |
Zone_id = 2613 x1= 53, y1= 40 |
|
Note 1: all distances are +/- 1m Note 2: sl-ZoneLength is set to 50m in accordance with Table 4.6.6-36, this allows for the accuracy with which a UE can define its position which is assumed to be +/- 15m. Note 3: zone id is calculated according to TS 38.331 [6] clause 5.8.11. |
|||||
– Nominal start time:
17th September 2020 23:40:00 (GPS time) (UTC time: 17th September 2020 23:39:42).
– 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 NR sidelink 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 (2) |
|
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 +/- 3dB. These conditions are defined for when there is no GNSS assistance data available at the UE and are specified in TS 38.133 [13] clause B.4.
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 does not need to support all systems. The DUT UE shall support at least one system and will be tested 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 [50].