The same LoRaWAN production line ships sensors to both China and Europe. The device firmware is nearly identical — the only difference is the RF configuration: frequency band, channel list, and power limits. Behind that "only difference" is the LoRaWAN Regional Parameters specification.
Many developers ask when first encountering multi-region deployment: Why does CN470 have dozens of uplink channels while EU868 has only a few? Why does the same DR (Data Rate) index map to different modulation parameters across regions? Why does a device fail to connect after moving from one region to another?
This article breaks down the core logic of Regional Parameters and answers these questions.
What Are Regional Parameters
LoRaWAN is a global protocol, but radio spectrum is regulated at the national/regional level. The LoRa Alliance publishes a separate Regional Parameters document (current recommended revision: RP002-1.0.5) alongside the LoRaWAN specification. This document defines, for each region:
- Frequency band: The upper and lower bounds of usable spectrum
- Channel plan: Number of channels, center frequencies, and spacing
- Data rate mapping (DR table): How DR indices map to SF/BW modulation parameters
- Maximum transmit power: ERP/EIRP limits set by regional regulations
- Dwell time limits: Restrictions on single-transmission duration in some regions
- Duty cycle: Spectrum occupancy ratio caps in some regions
- Maximum payload size: Constrained jointly by DR, direction, dwell time, and repeater compatibility
In one sentence: The LoRaWAN specification defines how devices communicate; Regional Parameters define on which frequencies, with what parameters, and under what constraints they communicate.
Source: LoRa Alliance RP002-1.0.5 Regional Parameters specification Official document: https://resources.lora-alliance.org/technical-specifications/rp002-1-0-5-lorawan-regional-parameters
CN470 vs EU868: Bandwidth Difference
This is the root of all differences.
| Dimension | CN470 (China) | EU868 (Europe) |
|---|---|---|
| Frequency range | 470–510 MHz | 863–870 MHz |
| Available bandwidth | 40 MHz | ~7 MHz |
| Spectrum type | Dedicated band, no duty cycle limit | SRD band, 1% duty cycle limit |
| Max transmit power | 17 dBm (50 mW ERP) | 14 dBm (25 mW ERP) |
CN470 has 40 MHz of available bandwidth — nearly 6 times that of EU868. This directly determines that the two regions take fundamentally different approaches to channel plan design:
- CN470: Abundant bandwidth allows for a large number of channels, giving devices more frequency choices and lower collision probability
- EU868: Only 7 MHz of bandwidth requires careful allocation — fewer channels, duty cycle restrictions, and devices cannot occupy the channel for extended periods
Evidence source: ThinkLink official documentation records "CN470 uses 470–510 MHz, Europe uses 863–870 MHz" Official document: https://www.think-link.net/docs/zh/Knowledge/index.html#lorawan
Channel Count Differences
A typical gateway based on the SX1302 chip supports 8 frequency channels (Frequency Channel), each with 125 kHz bandwidth. The gateway simultaneously monitors these 8 frequency positions.
CN470 Channel Plans
CN470 has multiple channel plan types. When deploying, you must explicitly specify which plan type is in use — you cannot simply write "CN470" and reuse another type's channel set. Common CN470 channel plans divide the 40 MHz bandwidth into multiple sub-bands, each containing 8 uplink channels, with downlink channels in a different frequency range.
MCP verified: In the RP002-1.0.5 CN470-510 specification, CN470 has multiple channel-plan types. The plan type must be determined at deployment time.
Thanks to the abundant bandwidth, CN470 can define dozens of uplink channels (the exact number depends on the channel plan type). The gateway selects 8 of them for monitoring. This means that within the same physical area, different networks can use different frequency combinations without interfering with each other.
EU868 Channel Plans
The 7 MHz bandwidth of EU868 only allows for a small number of channels. The standard defines 3 fixed uplink channels (default channels) that all devices must support for join:
- 868.10 MHz (DR0–DR5 supported)
- 868.30 MHz (DR0–DR5 supported)
- 868.50 MHz (DR0–DR5 supported)
The network server can define additional channels, but the 7 MHz bandwidth and duty cycle limit leave little room for expansion.
Comparison Summary
| Dimension | CN470 | EU868 |
|---|---|---|
| Available bandwidth | 40 MHz | ~7 MHz |
| Channel design approach | Many sub-bands, many channels | Few fixed channels + optional channels |
| Gateway simultaneous monitoring | 8 channels (selected from dozens) | 8 channels (selected from a small pool) |
| Collision probability | Low (large channel pool) | Relatively higher (small channel pool) |
| Duty cycle limit | None | 1% (per sub-band) |
Evidence source: ThinkLink official documentation records "A typical SX1302-based gateway has 8 frequency channels (each with BW=125 kHz)... The frequency channel refers to the frequency position the gateway monitors at any given moment. 8 frequency channels means it can simultaneously monitor 8 different frequencies, with specific values determined by regional spectrum regulations" Official document: https://www.think-link.net/docs/zh/Knowledge/index.html#gateway-ops
Data Rate Mapping: Same DR Index, Potentially Different Meaning
Many people assume DR0 means DR0 everywhere. In reality, the mapping from DR index to modulation parameters (SF/BW) is defined per region.
CN470 Data Rates
In the RP002-1.0.5 CN470 specification, the data rate mapping is as follows (for LoRa 125 kHz):
| DR | Modulation | SF | BW | Bit rate |
|---|---|---|---|---|
| DR0 | LoRa | SF12 | 125 kHz | 250 bps |
| DR1 | LoRa | SF11 | 125 kHz | 440 bps |
| DR2 | LoRa | SF10 | 125 kHz | 980 bps |
| DR3 | LoRa | SF9 | 125 kHz | 1,760 bps |
| DR4 | LoRa | SF8 | 125 kHz | 3,125 bps |
| DR5 | LoRa | SF7 | 125 kHz | 5,470 bps |
MCP verified: In the RP002-1.0.5 CN470-510 specification, DR3 is LoRa SF9 / 125 kHz, available for both uplink and downlink.
EU868 Data Rates
The DR0–DR5 mapping for EU868 is identical to CN470, but EU868 additionally defines higher-rate tiers:
| DR | Modulation | SF | BW | Bit rate |
|---|---|---|---|---|
| DR0 | LoRa | SF12 | 125 kHz | 250 bps |
| DR1 | LoRa | SF11 | 125 kHz | 440 bps |
| DR2 | LoRa | SF10 | 125 kHz | 980 bps |
| DR3 | LoRa | SF9 | 125 kHz | 1,760 bps |
| DR4 | LoRa | SF8 | 125 kHz | 3,125 bps |
| DR5 | LoRa | SF7 | 125 kHz | 5,470 bps |
| DR6 | LoRa | SF7 | 250 kHz | 11,000 bps |
| DR7 | FSK | — | 125 kHz | 50,000 bps |
DR0–DR5 mappings are consistent across both regions — this is the foundation of LoRaWAN's cross-region device compatibility. However, EU868's additional DR6 (SF7/250 kHz) and DR7 (FSK) are not available in CN470, because CN470's band design and channel plan do not require these additional modes.
Important: Maximum payload size is not determined by DR alone. You must specify the Regional Parameters revision, region, direction (uplink/downlink), DR, dwell time condition, and repeater compatibility condition. Without any one of these, the effective payload limit cannot be determined.
Transmit Power and Regulatory Constraints
| Dimension | CN470 | EU868 |
|---|---|---|
| Max ERP | 17 dBm (50 mW) | 14 dBm (25 mW) |
| Duty cycle limit | None | 1% (per sub-band) |
| Dwell time limit | Not mandatory | Limited for some DRs |
| LBT (Listen Before Talk) | Not required | Required in some sub-bands |
CN470's 17 dBm is 3 dB higher than EU868's 14 dBm, meaning CN470 devices have theoretically longer communication range (~1.4×) under identical conditions. However, actual range also depends on antenna gain, deployment environment, and SF selection.
EU868's 1% duty cycle is a critical engineering constraint: within each sub-band, a device's cumulative transmit time per hour must not exceed 36 seconds. This means EU868 devices cannot report data as frequently as CN470 devices, and reporting intervals must be designed with margin.
Why These Differences Matter for Deployment
1. Device Firmware Must Match the Region
Device RF parameters (channel list, DR table, power limits) are bound to the regional configuration at manufacturing or join time. A CN470 device brought to Europe will have completely mismatched frequencies and cannot communicate. Open-source gateways like GD6 also require selecting the correct regional standard during configuration, and the regional standard comes from the factory configuration and cannot be changed through the web interface.
MCP verified: The GD6 configuration guide states "the regional standard comes from the factory configuration and cannot be changed on the page" and "you cannot change one frequency band's hardware into another through page modifications."
2. Network Planning Strategies Differ
CN470's lack of duty cycle limits, higher power, and more channels support denser device deployments and more frequent data reporting.
EU868 requires more conservative network planning: control reporting frequency, prioritize unconfirmed packets to reduce downlink load, and enable ADR to move devices from high SF to low SF as quickly as possible to shorten airtime.
3. Multi-Region Deployment Requires Differentiated Design
For multinational IoT projects (such as those by ManThink, which serves both Chinese and European markets), products must support multiple frequency bands at the hardware level and match different regional channel plans at the firmware level. ManThink's sensor products (e.g., SE72/KS52 temperature and humidity sensors) support CN470, EU868, EU433, AS923, AU915, US902, and other bands, with different model codes distinguishing regional versions.
Quick Comparison of Other Major Regions
| Region | Band | Bandwidth | Characteristics |
|---|---|---|---|
| US915 | 902–928 MHz | 26 MHz | 64+8 channels, FHSS |
| AU915 | 915–928 MHz | 13 MHz | Similar structure to US915 |
| AS923 | 915–928 MHz (multiple sub-regions) | Variable | Country-specific variant (AS923-1 to AS923-4) |
| EU433 | 433.05–434.79 MHz | ~1.74 MHz | Extremely narrow band, very few channels |
| CN779 | 779–787 MHz | 8 MHz | China alternate band |
AS923 deserves particular attention: different countries map to different sub-region variants (AS923-1 through AS923-4). When selecting, first determine the Regional Parameters revision, then use that revision's Country Cross Reference Table to resolve the country-to-sub-region mapping. Country regulations and alliance tables are updated over time, so historical mappings should not be treated as permanent defaults.
MCP verified: For AS923, first select the Regional Parameters revision, then use that revision's Country Cross Reference Table to resolve AS923-1 through AS923-4. For example, the current RP002-1.0.5 maps Israel (IL) to AS923-4.
Practical Recommendations
- Specify region and channel plan type: When deploying CN470, you must determine the channel plan type simultaneously. You cannot simply write "CN470" and reuse another type's channel set.
- Budget for power margin: EU868's 14 dBm limit is 3 dB lower than CN470. Factor this into link budget design.
- Calculate duty cycle: EU868's 1% duty cycle is a hard constraint. Verify reporting frequency during design.
- Prioritize ADR: Regardless of region, enable ADR to let devices adapt to optimal rates, shortening airtime and reducing power consumption.
- Match hardware: RF hardware determines supported bands — you cannot change bands via software. The GD6 configuration guide explicitly states "you cannot change one frequency band's hardware into another through page modifications."
Conclusion
The fundamental reason CN470 and EU868 have different channel counts is that radio spectrum regulations in different countries allocate different amounts of bandwidth to each region. The 40 MHz vs 7 MHz bandwidth difference directly determines the channel plan design approach — CN470 can define many channels for low-collision deployment, while EU868 must carefully allocate scarce spectrum and add duty cycle restrictions.
Understanding Regional Parameters is not optional — it is the foundation of LoRaWAN multi-region deployment. From device selection and firmware configuration to network planning, every step requires correct decisions based on the target region's specification.
References:
- LoRa Alliance RP002-1.0.5 Regional Parameters: https://resources.lora-alliance.org/technical-specifications/rp002-1-0-5-lorawan-regional-parameters
- ThinkLink Official Knowledge Base (LoRaWAN Frequency Bands and Gateway Parameters): https://www.think-link.net/docs/zh/Knowledge/index.html#lorawan
- ThinkLink Official Knowledge Base (Gateway Frequency Channels/Channels/Demodulators): https://www.think-link.net/docs/zh/Knowledge/index.html#gateway-ops
- ThinkLink Official Knowledge Base (Regional Parameters Complete Snapshot): https://www.think-link.net/docs/zh/Knowledge/index.html#lorawan
- GD6 Configuration Guide: https://www.think-link.net/docs/zh/Device/LoRaWANGateway/gd6-configuration-guide.html
Evidence coverage: High. Core facts in this article (frequency ranges, channel counts, DR mappings, channel plan types, power limits) are sourced from ThinkLink official MCP documentation and the LoRa Alliance Regional Parameters specification.