Product Requirements for Compliance with ETSI EN 300 328 V2.2.2

Enabling revolutionary progress

Enabling revolutionary progress

Product Requirements for Compliance with ETSI EN 300 328 V2.2.2

On the 6th August 2021 manufacturers of equipment that fall under the scope of EN 300 328 will need to make sure that they are declaring against EN 300 328 V2.2.2

Wednesday, 17 March 2021

On the 6th August 2021 manufacturers of equipment that fall under the scope of EN 300 328 will need to make sure that they are declaring against EN 300 328 V2.2.2. There are technical changes in the requirements of this standard compared to previous version that manufacturers will need to consider.

Who is this applicable to?

Manufacturers of equipment incorporating “Data transmission equipment operating in the 2,4 GHz band” such as Bluetooth, 2.4 GHz WLAN (Wi-Fi) and Zigbee will need to take action. It is important to note that this is not only applicable to those implementing chipset solutions but also those incorporating modules provided by third parties.

What is the timeline of events?

ETSI EN 300 328 V2.2.2 was published in July 2019 and cited on the Radio Equipment Directive (2014/53/EU) Official Journal in February 2020.
The RED Official Journal currently lists two versions of EN 300 328, V2.1.1 and V2.2.2; manufacturers can currently use either version to claim presumption of conformity. On the 6th August V2.1.1 will be withdrawn and from that date only V2.2.2 will remain.

Anyone claiming compliance to previous versions must update their DoC to the new version by 6th August 2021; on that date v2.1.1 will be withdrawn and therefore no longer provide presumption of conformity and manufacturers must update to v2.2.2 to meet the legislative requirements.

What are the changes?

  • Clarification in definitions and requirement
  • Relaxation in the Transmitter Unwanted Emissions requirements
  • Changes to test methods
  • Change to Receiver Blocking test method – this will require a retest.
  • Changes to Reporting requirements


  1. Review your Declaration of Conformity to see which version of EN 300 328 you are currently listing
  2. Identify if you need to update your compliance (Gap Analysis)
  3. Perform any testing required to meet the requirements of EN 300 328 V2.2.2
  4. Add this evidence to your technical file
  5. Update your Declaration of Conformity to list EN 300 328 V2.2.2

NOTE!! - If you incorporate a third party module and use the third parties Declaration of Conformity and test report in your technical file then you will need to ask your provider to issue you the latest documentation.


Clause 4.3.1. – Requirements for Frequency Hopping Spread Spectrum (FHSS) Equipment

There is a clarification on requirement for FHSS equipment capable of employing both adaptive and non-adaptive modes; when in non-adaptive mode the equipment must comply with the requirements for non-adaptive FHSS equipment [].

Note - Modern Bluetooth devices rarely implement a non-adaptive mode, because it is only used to pair with older Bluetooth devices that are no longer commonplace.

Clause - Accumulated Transmit Time, Frequency Occupation and Hopping Sequence

FHSS equipment must meet the requirements for Accumulated Transmit Time, Frequency Occupation and Hopping Sequence. The customer may provide a statistical analysis that the equipment meets the requirements for Accumulated Transmit Time (i.e. ‘on’-time over observation period on a specific hopping frequency is 95%). It is now a requirement that this statistical analysis is included in the test report if the customer has submitted it []. Ordinarily, TÜV SÜD perform this analysis and assume that it will not be provided by the customer.

There is a change in the test methodology used for Clause, whereas previously an RMS detector could have been used, V2.2.2. identifies that a Peak detector must be used. The change of detector type is almost certain to have no impact on the number of channels detected. A device deemed compliant when assessed against V2.1.1 can therefore be considered compliant with V2.2.2.

Clause & Transmitter unwanted emissions in the spurious domain

There is a relaxation in the Transmitter unwanted emissions in the spurious domain requirement.
Previously equipment had to meet -54 dBm from 470 MHz to 862 MHz and -36 dBm from 862 MHz to 1 GHz (when measured with a Resolution Bandwidth (RBW) of 100 kHz). These frequency ranges have been modified to -54 dBm from 470 MHz to 694 MHz and -36 dBm from 694 MHz to 1 GHz.

A device which complies with the more stringent limits in V2.1.1 complies with the limits in V2.2.2.


Clause – Receiver Blocking

The minimum performance criteria for receiver blocking has been updated to allow for a Frame Error Rate (FER) of less than or equal to 10%. The client may no longer declare an alternative performance criterion as was permitted in V2.1.1. Devices that do not facilitate a Packet Error Rate (PER) or FER should have no loss of transmission for the intended use of equipment.

A change in the test requirement mandates that all Receiver Categories outlined in clause now feature a blocking signal power of -34 dBm at the receiver of the equipment, after having compensated for in-band antenna assembly gain in conducted measurements or power flux density (PFD) in radiated measurements [].

Additionally, all Receiver Categories feature a wanted signal mean power from companion device (WSMPCD) that is derived from a calculation based on the occupied bandwidth (OCBW) of the device. The WSMPCD no longer uses calculations based on the level of the wanted signal at the input of the equipment (Pmin), unless in a radiated test where the wanted signal from the companion device cannot be determined [].

Lastly, all Receiver Categories must be tested to new blocking signals defined in V2.2.2 that were not required in V2.1.1 [,, and].

All equipment will need to be re-assessed (tested) to the revised Receiver Blocking requirements of V2.2.2 following the procedure in clause

TÜV SÜD are UKAS accredited to EN 300 328 V2.2.2 and can provide the testing required to generate the evidence manufactures need to support their EU Declaration of Conformity.

Next Steps

Site Selector