What Is LoRaWAN — RED?
LoRaWAN test, according to EN 300 220, in terms of output power, duty cycle, channel usage and unwanted broadcasts of the LoRa modulated device operating in sub-GHz short-range device bands; This is the experimental group where it is evaluated according to the LoRa Alliance qualification specifications in terms of protocol behavior.
Purpose of LoRaWAN — RED
The goal is to verify that the device complies with the power and duty cycle limits on the sub-GHz bands and operates correctly on the LoRaWAN network.
Which Products Is LoRaWAN — RED Applied To?
- smart meters
- Agricultural and environmental sensors
- Asset tracking devices
- City infrastructure sensors
In Which Sectors Is LoRaWAN — RED Used?
Standards Related to LoRaWAN — RED
- REDEU radio equipment directive test
- ETSIEuropean telecommunications standards test
- FCCUS radio and EMC regulations test
LoRaWAN — RED Conditions
- Bantlar
- Regional sub-GHz short-range device bands (e.g. 863–870 MHz in Europe)
- Quantities measured
- Output power/EIRP, bandwidth occupied, spam, duty cycle compliance
- Protokol
- Join process, classroom behavior (A/B/C), ADR and safety
- Regional parameters
- The target region parameter set must be defined
Equipment for LoRaWAN — RED
- semi-reflective room
- Spectrum analyzer and power measurement setup
- LoRaWAN test server and gateway
- Kalibre anten seti
Sample Requirements for LoRaWAN — RED
- The device must support continuous transmission and test modes
- Target area and band plan must be documented
- Antenna gain must be specified
- Final production software must be used
Duration of LoRaWAN — RED
1–3 weeks depending on coverage.
LoRaWAN — RED Procedure
- 1Target region parameters are determined.
- 2Output power and bandwidth are measured.
- 3Unwanted publications are scanned.
- 4Duty cycle behavior is verified.
- 5Protocol qualification sequences are run.
- 6Results are compared with the limits.
LoRaWAN — RED Acceptance Criteria
The acceptance criteria are the power, band and duty cycle limits in EN 300 220 and the passing conditions of the qualification specification.
Evaluation of Results
The duty cycle limit is a legal restriction on European sub-GHz bands; If the application software transmits in excess of this, the device loses compliance. Regional parameter sets are not interchangeable.
LoRaWAN — RED Report
- Applied standards and target region
- Device and antenna description
- Power, band and emissions results
- Duty cycle verification
- Protocol qualification results
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 authorisationsRelated Regulations
- Radio Equipment Directive 2014/53/EU (RED)
- LoRa Alliance qualification program
RF and Wireless Testing — What Does This Testing Field Cover?
The section below describes the field that the LoRaWAN 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 LoRaWAN — RED
According to which standard is LoRaWAN made?
LoRaWAN is executed in scope EN 300 220 serisi, LoRa Alliance LoRaWAN qualification test specification, LoRaWAN Regional Parameters, FCC Part 15.247 (US market), 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 LoRaWAN apply to?
Mainly applied to smart meters, Agricultural and environmental sensors, Asset tracking devices and City infrastructure sensors. Whether your product is included in the scope is determined by examining its technical specifications and intended use.
Under what conditions is LoRaWAN done?
The determining parameters are: Bantlar — Regional sub-GHz short-range device bands (e.g. 863–870 MHz in Europe), Quantities measured — Output power/EIRP, bandwidth occupied, spam, duty cycle compliance and Protokol — Join process, classroom behavior (A/B/C), ADR and safety. 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 LoRaWAN?
The device must support continuous transmission and test modes, Target area and band plan must be documented and Antenna gain must be specified. The number of samples is determined according to the product standard and the scope to be reported.
How long does LoRaWAN take?
1–3 weeks depending on coverage. 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 LoRaWAN result called "appropriate"?
The acceptance criteria are the power, band and duty cycle limits in EN 300 220 and the passing conditions of the qualification specification.