GNSS Compliance and Certification: What Manufacturers Need to Know

Global Navigation Satellite Systems (GNSS) are widely used in products that require positioning, navigation, timing or location-related information. From industrial tracking devices and connected vehicles to medical equipment and consumer electronics, GNSS receivers have become an important part of many modern products.

For manufacturers, integrating GNSS is not simply a matter of selecting a receiver module. The compliance assessment depends on the receiver architecture, operating frequency bands, antenna implementation, other radio technologies in the product and the markets where the product will be placed on the market.

This article explains the main GNSS technologies, the distinction between GNSS reception and radio transmission, and the regulatory considerations manufacturers should address when planning compliance testing and certification.

1. What Is GNSS?

Global Navigation Satellite System (GNSS) is a general term for satellite-based systems that provide positioning, navigation and timing information.

Examples include:

GPS – Global Positioning System, operated by the United States.
Galileo – the European Union’s global navigation satellite system.
GLONASS – the Russian global navigation satellite system.
BeiDou – China’s global navigation satellite system.
Regional and augmentation systems – including systems that supplement or improve GNSS positioning performance.

A GNSS receiver processes signals transmitted by navigation satellites to determine information such as position, velocity and time.

GNSS is commonly integrated into:

Automotive navigation and telematics systems
Fleet management and asset tracking devices
Industrial IoT equipment
Wearables and handheld devices
Surveying and positioning equipment
Timing and synchronisation systems
Drones and other remotely operated equipment
Connected infrastructure and smart-city applications

2. GNSS Reception Versus Radio Transmission

A key point for compliance planning is that a conventional GNSS receiver primarily receives satellite signals. It does not normally transmit a signal back to the navigation satellites.

This distinguishes GNSS reception from technologies such as cellular, Wi-Fi and Bluetooth, which include radio transmission functions.

However, the presence of a GNSS receiver does not mean that the complete product is exempt from radio compliance requirements. Manufacturers must assess the actual product configuration, including:

The GNSS receiver and its operating frequency bands
The antenna and RF front-end implementation
Any additional radio transmitters in the product
Digital circuitry and potential unwanted emissions
The intended use and applicable product legislation
The destination markets and relevant national requirements

A product containing GNSS and cellular connectivity, for example, needs an assessment of both the GNSS reception function and the cellular transmission function. The testing scope cannot be determined from the GNSS module alone.

3. GNSS Frequency Bands and Receiver Architecture

GNSS systems operate in several frequency bands. The frequencies supported by a receiver depend on the satellite systems and signals it is designed to process.

Common GNSS frequency bands include:

Band or signal family	Approximate frequency
GPS L1 / Galileo E1	1,575.42 MHz
GPS L2	1,227.60 MHz
GPS L5 / Galileo E5a	1,176.45 MHz
Galileo E5b	1,207.14 MHz
BeiDou B1 family	Around 1,561–1,575 MHz, depending on signal
GLONASS L1	Around 1,602 MHz, with signal-dependent channel frequencies

These are examples rather than a complete list of GNSS signals. Exact supported frequencies and signal configurations should be confirmed against the receiver’s technical documentation.

Single-band and multi-band receivers

A single-band receiver processes signals in one GNSS frequency band. Multi-band receivers can process signals in multiple bands and may support improved positioning performance in challenging environments.

From a compliance perspective, the supported frequency bands matter because the applicable receiver standard may define its scope by frequency range. The antenna, RF filtering, receiver sensitivity and unwanted emissions also need to be considered.

Integrated modules and external antennas

GNSS functionality may be implemented using:

A GNSS receiver module with an integrated antenna
A receiver module connected to an external antenna
A receiver chipset integrated directly into the product’s PCB
A multi-constellation or multi-band receiver with a specialised antenna system

The chosen architecture affects the compliance assessment. Changes to the antenna, RF front end, PCB layout, shielding or enclosure can affect receiver performance and unwanted emissions.

4. GNSS Industry Certification Versus Regulatory Compliance

Manufacturers should distinguish between industry or ecosystem-related qualification and regulatory compliance.

Industry-specific requirements may apply depending on the product, customer, application or intended operating environment. These may concern interoperability, positioning performance, safety, reliability or compatibility with other systems.

Regulatory compliance addresses the legal requirements for placing the product on a market.

A GNSS module’s existing documentation or test results may support the manufacturer’s assessment, but they do not automatically establish compliance of the finished product.

The manufacturer remains responsible for assessing the complete equipment, including the host device, antenna configuration, power supply, enclosure and any additional radio functions.

5. GNSS Compliance in the European Union

In the European Union, the applicable legislation depends on the product and its functions.

Radio Equipment Directive (RED)

The Radio Equipment Directive 2014/53/EU is relevant to radio equipment within its scope. GNSS receiver equipment may fall under the RED, but the assessment must consider the actual equipment and its intended function.

The RED includes essential requirements relating to:

Health and safety
Electromagnetic compatibility
Efficient use of radio spectrum and avoidance of harmful interference

For GNSS receivers, the applicable standards and assessment route depend on the equipment type and operating frequency bands.

ETSI EN 303 413

ETSI EN 303 413 addresses GNSS receivers operating in the frequency bands:

1,164 MHz to 1,300 MHz
1,559 MHz to 1,610 MHz

The standard specifies technical characteristics and measurement methods for GNSS user equipment within its scope. Its application should be checked against the receiver’s supported bands and equipment configuration.

The European Commission’s harmonised standards references should be checked at the time of assessment to confirm the applicable version and the extent to which it provides a presumption of conformity with the relevant RED requirements.

EMC assessment

The GNSS receiver is only one part of the complete product. The EMC assessment may need to consider emissions and immunity arising from the host equipment, including:

Digital processing and clock circuits
DC/DC converters and switching power supplies
Displays, processors and memory
Interfaces and connected cables
Cellular, Wi-Fi, Bluetooth or other radio transmitters

The applicable EMC standards depend on the product category and intended environment. A generic GNSS receiver standard should not be treated as a substitute for the complete product’s EMC assessment.

Other EU requirements

Additional legislation or standards may apply depending on the product, for example where it is medical equipment, automotive equipment, machinery, or equipment intended for a specific safety-related application.

The regulatory assessment should therefore begin with the complete product classification rather than the GNSS receiver alone.

6. GNSS Compliance in the United States

In the United States, the compliance route depends on the equipment’s radio functions and the applicable FCC rules.

FCC requirements for receivers

GNSS receivers are generally reception-oriented devices, but this does not eliminate the need to consider FCC requirements. Applicable provisions may address receiver emissions, digital circuitry and other functions incorporated into the equipment.

The specific requirements depend on the device classification, operating characteristics and whether the product includes transmitters.

Products with additional transmitters

If a GNSS product also includes cellular, Wi-Fi, Bluetooth or another transmitter, those radio functions require their own assessment under the relevant FCC requirements.

The manufacturer should also consider how the transmitters operate together, including simultaneous transmission and the effect of the final antenna configuration.

Host product and module integration

Where a GNSS module or another radio module has existing FCC documentation, the manufacturer should review the conditions and limitations associated with that approval.

The finished product may still require assessment of:

Module integration conditions
Antenna type and gain
Host emissions
Co-location or simultaneous-transmission conditions
Labelling and user information
Any additional transmitter functions

Module documentation should be treated as supporting evidence, not as an automatic approval of the finished product.

7. GNSS Compliance in Canada

In Canada, ISED requirements should be considered according to the product’s radio functions and equipment classification.

ISED’s general requirements include provisions for receivers, including receiver functions incorporated into transceivers. The applicable measurement and compliance obligations depend on the equipment and the relevant standards.

For products containing GNSS alongside cellular, Wi-Fi, Bluetooth or other radio technologies, the manufacturer should assess each relevant radio function and the complete host configuration.

The compliance review should establish:

Which ISED standards apply to the receiver and any transmitters
Whether certification is required for any radio function
Which receiver emission requirements apply
Whether antenna and module integration conditions are relevant
Whether RF exposure assessment is required for transmitting functions
What labelling and documentation are required

The exact requirements should be confirmed against the current ISED standards and the equipment’s configuration.

8. RF Exposure and GNSS Products

A conventional GNSS receiver does not transmit navigation signals, so its reception function does not normally create the same RF exposure assessment as a transmitter.

However, many GNSS products include other radio technologies. Examples include cellular modems, Wi-Fi, Bluetooth and proprietary telemetry links.

For those products, the manufacturer should assess the transmitting functions and consider:

Transmitter output power
Operating frequency
Antenna type and gain
Intended use and separation distances
Whether the product is body-worn or used close to the body
Simultaneous transmission between multiple radio technologies
Applicable market-specific RF exposure requirements

A GNSS receiver should therefore not be used as the basis for concluding that the entire product has no RF exposure obligations.

9. Changes to a GNSS Product and Their Compliance Impact

Changes to a GNSS implementation can affect receiver performance, emissions or the applicability of existing evidence.

Examples include:

Replacing the GNSS module or chipset
Adding support for additional GNSS frequency bands
Changing the antenna type, location or gain
Modifying the PCB layout or RF matching network
Changing the enclosure or introducing metallic components
Modifying shielding or filtering
Adding cellular, Wi-Fi, Bluetooth or another transmitter
Changing the power supply or clock architecture
Changing the intended use or operating environment

The manufacturer should evaluate each change to determine whether existing test evidence remains valid, whether additional testing is needed, and whether the technical documentation must be updated.

10. Common GNSS Compliance Mistakes

Assuming that a receiver has no compliance requirements

Although a conventional GNSS receiver does not normally transmit, the equipment may still be subject to applicable radio, EMC, safety and other product requirements.

Treating module documentation as approval of the finished product

Module documentation may be useful, but the host product and its integration conditions must still be assessed.

Ignoring the supported frequency bands

A receiver may support several GNSS systems and bands. The manufacturer should verify the actual configuration against the scope of the relevant standards.

Overlooking other radio technologies

GNSS is often integrated with cellular, Wi-Fi or Bluetooth. These functions can substantially change the compliance scope.

Ignoring antenna and enclosure changes

Antenna placement, nearby metal, shielding and enclosure materials can affect receiver performance and emissions.

Using an incomplete test plan

A test plan based only on the GNSS receiver may overlook host EMC, other transmitters, RF exposure or product-specific requirements.

11. A Practical GNSS Compliance Workflow

A structured workflow helps manufacturers establish the applicable requirements before testing begins.

Step 1 – Define the product

Document the product category, intended use, operating environment and destination markets.

Step 2 – Identify the GNSS implementation

Record the receiver module or chipset, supported constellations, frequency bands, antenna configuration and relevant integration conditions.

Step 3 – Identify all other radio functions

List cellular, Wi-Fi, Bluetooth, NFC, proprietary radio links and any other transmitters incorporated into the product.

Step 4 – Determine the applicable legislation and standards

Identify the relevant radio, EMC, safety, RF exposure and product-specific requirements for each target market.

Step 5 – Review existing evidence

Collect module documentation, test reports, declarations, antenna information and integration conditions. Determine which evidence can be used for the finished product.

Step 6 – Establish the test plan

Define the required tests, sample configurations, operating modes, accessories and expected laboratory effort.

Step 7 – Evaluate changes and final configuration

Confirm that the tested configuration reflects the production product, including its antenna, enclosure, firmware and radio functions.

Step 8 – Complete the technical documentation

Maintain the test reports, compliance assessment, declarations and other documentation required for the target markets.

12. System-Level Architecture: Why the Complete Product Matters

GNSS is frequently one component within a larger electronic system.

A typical connected device may include:

GNSS receiver and antenna
Cellular modem and antenna
Wi-Fi and Bluetooth connectivity
Processor, memory and digital interfaces
Switching power supply
Display, sensors and external interfaces
Metal enclosure or shielding components

These subsystems can interact. Digital noise or switching electronics may affect GNSS reception, while transmitting radios can create interference or introduce additional compliance requirements.

The compliance assessment should therefore consider the product as a complete system rather than treating each module as an isolated component.

GNSS receiver → frequency bands and antenna → host integration → EMC and unwanted emissions → additional radio transmitters → RF exposure where applicable → market-specific requirements

Conclusion

GNSS enables positioning, navigation and timing across a wide range of products. While a conventional GNSS receiver primarily receives satellite signals, its integration into a finished product still requires a structured compliance assessment.

Manufacturers should identify the supported GNSS bands, assess the receiver and antenna implementation, review host-level EMC and emissions, and account for any additional radio transmitters. Existing module documentation can support the process, but it should not be assumed to establish compliance of the complete product.

A clear test plan helps identify the applicable requirements, avoid unnecessary testing and ensure that the final product configuration is properly assessed for its intended markets.

How ScopeRight Helps

ScopeRight helps manufacturers define the compliance scope for products incorporating GNSS and other radio technologies.

The platform supports the process by helping manufacturers:

Identify potentially applicable standards based on product characteristics and target markets
Structure RF, EMC and safety compliance requirements
Develop a test plan before approaching a test laboratory
Estimate laboratory effort and prepare for quotation requests
Consider multiple radio technologies within the same product
Organise compliance activities and supporting documentation

By defining the scope before testing begins, manufacturers can approach laboratories with a clearer understanding of the product configuration, applicable requirements and expected work.

Explore the platform and compliance tools at ScopeRight.