GNSS – RED / ETSI / FCC

What Is GNSS — RED?

GNSS testing is a set of performance experiments in which the GPS, Galileo, GLONASS or BeiDou receiver is measured in terms of time to first position (TTFF), tracking precision and position accuracy under controlled satellite signal simulation.

Purpose of GNSS — RED

The aim is to verify under repeatable conditions that the positioning receiver provides the expected precision and accuracy in the target application.

Which Products Is GNSS — RED Applied To?

Vehicle tracking and telematics units
eCall modules
Smartphone and wearable devices
Industrial and agricultural positioning devices

In Which Sectors Is GNSS — RED Used?

TelecommunicationsElectronicsSoftwareCyber Security

Standards Related to GNSS — RED

REDEU radio equipment directive test
ETSIEuropean telecommunications standards test
FCCUS radio and EMC regulations test

GNSS — RED Conditions

constellations: GPS, Galileo, GLONASS, BeiDou; Combinations supported by the device
Quantities measured: Cold/hot start TTFF, tracking sensitivity, position accuracy, recapture time
Sinyal seviyeleri: Defined in the specification; gradually lowered for sensitivity
Senaryolar: Static and dynamic motion profiles

Equipment for GNSS — RED

Multi-constellation GNSS signal simulator
Calibrated attenuator network and wired connection
Semi-reflective room (for diffuse measurements)
Location data recording and evaluation software

Sample Requirements for GNSS — RED

The device must be able to export location data
Antenna type and gain must be documented
Use of auxiliary data (A-GNSS) must be defined
Final software version must be used

Duration of GNSS — RED

Typically 1–3 weeks depending on number of scenarios.

GNSS — RED Procedure

1The device is connected to the emulator and the location output is recorded.
2Cold and hot start TTFF is measured.
3Sensitivity is determined by gradually decreasing the signal level.
4Accuracy is measured in static and dynamic scenarios.
5Recapture time is measured.
6The results are compared with the specification.

GNSS — RED Acceptance Criteria

Acceptance criteria are given as TTFF, sensitivity and accuracy limits in the applicable specification or customer requirement.

Evaluation of Results

The use of auxiliary data (A-GNSS) significantly changes the TTFF result; The results cannot be compared without specifying which aid mode was measured.

GNSS — RED Report

Applied specifications and scenarios
Constellation and help mode
Sinyal seviyeleri
TTFF, precision and accuracy results
Measurement uncertainty

Accreditation

EUROLAB holds internationally recognised accreditation obtained from accreditation bodies party to the IAF and ILAC multilateral recognition arrangements, under ISO/IEC 17025 for laboratory testing, ISO/IEC 17020 for inspection and surveillance, and ISO/IEC 17021-1 and ISO/IEC 17065 for system and product certification. This chain ensures the reports and certificates issued are accepted worldwide.

Whether this test can be offered within accredited scope depends on your product and the standard applied; since accreditation is method-based, the scope is confirmed in writing at the quotation stage.

Scope and authorisations

Related Regulations

EN 303 413 (GNSS receivers under RED)
eCall legislation (where applicable)

RF and Wireless Testing — What Does This Testing Field Cover?

The section below describes the field that the GNSS test belongs to; the conditions and acceptance criteria of this particular test are given in the sections above. The scope specific to your product is confirmed in writing at the quotation stage.

RF and wireless testing shows that a device containing a radio uses the spectrum correctly and operates within the limits the relevant legislation allows. This family is a separate body of work from EMC: EMC addresses unwanted interference, whereas here INTENTIONAL emission is assessed.

Spectrum is a public and limited resource, and this determines the legal character of the field. A device spilling outside its permitted band or emitting excess power is not merely a technical defect but a violation that disrupts someone else's service. Radio conformity is therefore policed more strictly than other test fields and markets maintain their own national regimes.

Measurements run separately on the transmitter and receiver sides. On the transmitter side, output power, occupied bandwidth, frequency error, unwanted emissions, adjacent channel power and the power envelope are measured. On the receiver side, sensitivity, selectivity, blocking and spurious response rejection are assessed. The receiver side is often neglected, but in some bands it is a regulatory requirement.

Access protocol specific behaviours are a third axis: listen before talk (LBT), duty cycle, dynamic frequency selection (DFS) and transmit power control (TPC). These mechanisms enable spectrum sharing and it must be shown that they work correctly.

HUMAN EXPOSURE is the fourth axis and one of the most commercially critical. For devices used close to the body, SAR (specific absorption rate) is measured; for devices used at a distance, a field strength assessment is made. Limits and measurement methods vary by market; the same device is assessed separately for Europe and the United States.

Market regimes are decisive in this family and do not substitute for one another: the Radio Equipment Directive and ETSI harmonised standards in Europe, FCC authorisation in the United States (through a TCB for intentional radiators), ISED in Canada, MIC in Japan, KC in South Korea and SRRC in China each carry their own set of requirements. The same device requires a separate file for each market, and some markets impose a local representative or local testing requirement.

Module integration is the subject that raises the most questions in the field. Using a certified radio module does not automatically make the device compliant. A module certificate is valid for a defined antenna, a defined supply and defined conditions of use; if the antenna changes, the layout changes or the module is operated at a different power level, reassessment is required.

The presence of several radios in the same device (Wi-Fi + Bluetooth + cellular + NFC) gives rise to a simultaneous transmission assessment: SAR and unwanted emission measurements are made for the worst case in which the radios operate together.

Method groups in this field

Transmitter measurements
Output power, occupied bandwidth, frequency error, unwanted emissions, adjacent channel power, power spectral density.
Receiver measurements
Sensitivity, selectivity, blocking, spurious response rejection.
Spectrum sharing mechanisms
Verification of listen before talk, duty cycle, dynamic frequency selection and transmit power control.
Human exposure
SAR measurement (handheld and body-worn devices), field strength assessment, multi-radio scenarios.
Protocol conformity
Cellular network conformity testing, Bluetooth and Wi-Fi certification testing, GNSS performance.
Antenna measurements
Gain, radiation pattern, efficiency and total radiated power (TRP) measurements.

Commonly confused in this field

Using a certified module does not automatically make the device compliant; if the antenna, layout or power level changes, reassessment is required.
An FCC file does not replace a CE file; each market operates its own regime.
Receiver side measurements are a regulatory requirement in some bands; measuring only the transmitter produces an incomplete file.
SAR limits and measurement methods differ by market; a result in one market does not carry over to another.
For devices carrying several radios the simultaneous transmission scenario must be assessed; measuring them individually is not sufficient.
Some markets impose local testing or a local representative requirement; technical conformity alone does not secure market access.

Which decisions these results support

Market access under radio equipment legislation
Verification of the antenna and RF front end design
SAR and RF exposure conformity
Verification of module integration and the scope of reassessment
Determining the worst case in multi-radio scenarios

Related Tests

Frequently Asked Questions About GNSS — RED

According to which standard is GNSS made?

GNSS is executed in scope 3GPP TS 37.571 serisi, GNSS receiver performance measurement methods, EN 303 413 (GNSS receiver radio requirements), RED, ETSI and FCC. The limit values and acceptance criteria to be applied are defined in the product standard; The version valid for your product is confirmed in writing at the offer stage.

Which products does GNSS apply to?

Mainly applied to Vehicle tracking and telematics units, eCall modules, Smartphone and wearable devices and Industrial and agricultural positioning devices. Whether your product is included in the scope is determined by examining its technical specifications and intended use.

Under what conditions is GNSS done?

The determining parameters are: constellations — GPS, Galileo, GLONASS, BeiDou; Combinations supported by the device, Quantities measured — Cold/hot start TTFF, tracking sensitivity, position accuracy, recapture time and Sinyal seviyeleri — Defined in the specification; gradually lowered for sensitivity. The full terms are in the "Test Conditions" section on the page and vary depending on the product standard.

What kind of sample is needed for GNSS?

The device must be able to export location data, Antenna type and gain must be documented and Use of auxiliary data (A-GNSS) must be defined. The number of samples is determined according to the product standard and the scope to be reported.

How long does GNSS take?

Typically 1–3 weeks depending on number of scenarios. This duration belongs to the experiment itself; sample preparation, queuing and reporting are also evaluated. A realistic schedule for your product is given in the offer.

What is the GNSS result called "appropriate"?

Acceptance criteria are given as TTFF, sensitivity and accuracy limits in the applicable specification or customer requirement.