Series note: This is article #12 in the ManThink "LoRaWAN Technical Reading" series (the 2nd article in the "Industry Trends" track). Reading the previous 11 articles in order is recommended.

Sources: MIIT Announcement No. 52 of 2019 ("Catalogue and Technical Requirements for Micro-Power Short-Range Radio Transmitting Equipment"); MIIT Order No. 57 ("Regulations on the Administration of Radio Transmitting Equipment"), effective 2023-07-01; LoRa Alliance RP002-1.0.5 LoRaWAN Regional Parameters; Semtech's official LoRa Q&A; ThinkLink official documentation (gwTool6 Configuration Guide / GD61x User Guide).

Disclaimer: This article is a technical reading of public regulatory texts and the public LoRaWAN specification. It is not legal advice. Before deploying any 470–510 MHz radio equipment in mainland China, consult your local radio management authority or a qualified compliance advisor.

Introduction: From "Group Networking Ban" to "Small-Area Group Networking"

On 14 December 2017, the Ministry of Industry and Information Technology (MIIT) Radio Administration Bureau released a draft for comment on the "Technical Requirements for Micro-Power Short-Range Radio Transmitting Equipment (Draft for Comment)". A single line in the civil metering band subsection shocked the entire Sub-GHz IoT industry in China:

Under the condition that the transmitter's single-shot working time does not exceed 5 seconds, the 470–510 MHz band can be used as the band for civil radio metering equipment. Limited to single-frequency use, not allowed for group networking applications.

"Not allowed for group networking"—for an IoT technology that depends on multi-gateway, wide-area coverage to be viable, this was nearly a death sentence for Sub-GHz deployment in China. On 11 January 2018, China's LoRa industry chain—CLAA, Alibaba, Tencent, August Technology, HuiLian Infinite and others—gathered in Beijing for the "IoT Micro-Power Spectrum Application Workshop" and issued a joint statement.

Two years later, the plot reversed. On 28 November 2019, MIIT officially issued Announcement No. 52 of 2019 ("Announcement #52" hereafter), effective from 1 January 2020. The civil metering equipment clause was changed from the draft's "not allowed for group networking" to "limited to small-area group networking applications in building complexes, residential communities and villages", and the strict "integrated antenna" constraint was dropped. In effect, the regulator "carved out a piece of land, gave it a legal identity, but set seven rules."

Why revisit this in 2026? Five reasons:

  1. From 1 January 2022, manufacturing/import of civil metering equipment under the older document (Xin Bu Wu [2005] No. 423) was completely banned; the new rules fully apply.
  2. From 1 July 2023, MIIT Order No. 57 ("Regulations on the Administration of Radio Transmitting Equipment") took effect, adding new requirements for "special markings" and "sales record-keeping" on micro-power equipment.
  3. LoRa Alliance RP002-1.0.5 significantly tightened the maximum payload for CN470-510 compared to v1.0.3, actively aligning with the 1-second rule.
  4. Many gateways ship with 27 dBm (≈ 500 mW) transmit power enabled by default, which already exceeds the 50 mW (e.r.p.) cap of Announcement #52.
  5. China State Grid occupies 66 of the 96 uplink channels, and China's DTMB terrestrial digital TV continues to broadcast on UHF 470–566 MHz. "The spectrum is partitioned" only on paper.

This article lays out the seven hard constraints, three hidden landmines, one measured "1-second red line" comparison table, and one deployable engineering checklist.

1. The 7 Hard Constraints of Announcement #52 for LoRaWAN CN470

The attachment of Announcement #52 ("Catalogue and Technical Requirements for Micro-Power Short-Range Radio Transmitting Equipment") divides equipment into 8 categories. LoRaWAN CN470 falls under the Civil Metering Equipment category. The hard constraints on 470–510 MHz (all values from the attachment's original text and Semtech's official LoRa Q&A summary):

# Constraint Regulatory Requirement Engineering Meaning
1 Operating frequency 470–510 MHz Only this segment; CN779-787 is not open in China
2 Transmit power limit 50 mW (e.r.p.) ≈ 17 dBm ERP, equivalent to ≈ 19.15 dBm EIRP
3 Power spectral density For occupied bandwidth ≤ 200 kHz: 50 mW / 200 kHz (e.r.p.); for 200–500 kHz: 10 mW / 100 kHz (e.r.p.) LoRa 125 kHz channels fit the first tier; 500 kHz modes (e.g., SX1303 with BW500) follow the second tier
4 Single-shot transmission duration No more than 1 second The critical red line, hitting DR0/DR1 hardest
5 Occupied bandwidth No more than 500 kHz 125 kHz / 250 kHz / 500 kHz are all compliant
6 Frequency tolerance 100 × 10⁻⁶ At 470 MHz, drift ≤ 47 kHz; SX1302 typically ±10 ppm, far better
7 Networking scope and transmit behavior Limited to small-area group networking in building complexes, residential communities and villages; only one channel may transmit at any given moment; civil metering equipment must have interference-avoidance functions such as "transmit-before-search" that cannot be user-adjusted or disabled Gateway downlink is also constrained to single-channel transmission at any moment; multi-channel parallelism is receive-only

The full text also requires: "If the operating frequency coincides with a local sound or TV broadcast station's frequency, it must not be used locally; if it causes interference to local sound or TV broadcast reception, it must be stopped immediately and may only be resumed after the interference is eliminated or the frequency is adjusted to a non-interfering one." This clause is often forgotten, but applied to LoRaWAN it means: each city's DTMB UHF channels must be avoided in your channel plan if they overlap with yours.

Key fact: LoRa Alliance / Semtech have publicly reconciled with Announcement #52 multiple times, concluding that LoRa's physical layer (including CAD channel detection, frequency hopping, and spread-spectrum anti-interference) is naturally compatible with "transmit-before-search" and "small-area group networking", and the compliance boundary is generally clear. But compliance doesn't mean carelessness—each of the seven items above maps to a specific engineering action. Missing one is non-compliance.

Sources: - "Announcement No. 52 of 2019 of the Ministry of Industry and Information Technology of the People's Republic of China" (MIIT official website / State Council policy interpretation) - TÜV SÜD interpretation of Announcement No. 52 of 2019 - Semtech LoRa Q&A ("LoRa meets all the requirements of China's MIIT Announcement No. 52")

2. What the LoRaWAN CN470 Specification Actually Says

Putting the regulatory "constraints" and the LoRaWAN standard's "parameters" into the same table reveals "what's a real conflict and what's just a style difference". The table below covers both RP v1.0.3 and RP002-1.0.5 so you can correlate legacy devices in the wild against modern stacks.

Item LoRaWAN RP v1.0.3 (CN470-510) LoRa Alliance RP002-1.0.5 (CN470-510)
Uplink channels 96 channels, 470.3–489.3 MHz, 125 kHz BW, 200 kHz step Same (still 96)
Downlink channels 48 channels, 500.3–509.7 MHz, 125 kHz BW, 200 kHz step Same (still 48)
Data rates DR0–DR5 SF12 / SF11 / SF10 / SF9 / SF8 / SF7, all 125 kHz, CR 4/5 Same
Default transmit power 14 dBm (power index 2) 17 dBm ERP ≈ 19.15 dBm EIRP (power index 0)
Maximum EIRP 50 mW (i.e., 17 dBm EIRP) 19.15 dBm (50 mW ERP)
RX2 default window 505.3 MHz / DR0 (SF12/125 kHz) Same
Maximum MACPayload DR0/1/2 = 59 B (M) / 51 B (N), DR3 = 123 B / 115 B, DR4/5 = 230 B / 222 B DR0 = 15 B (M) / N=N/A; DR1 = 31 / 23; DR2 = 94 / 86; DR3 = 192 / 184; DR4-5 = 230 / 222 (repeater) or 250 / 242 (not repeater)
JoinAccept CFList Not supported (v1.0.3 explicitly says terminal must ignore if non-empty) Supported (CFListType=0x01, carries ChMask fields, interpreted by a virtual ChMaskCntl for 20 MHz / 26 MHz antenna plans)
Single-shot transmission duration No more than 5000 ms (RP default) Same
Dwell time Unlimited (CN470 has no dwell time limit) Same
China State Grid occupied channels Index 6–38 and 45–77 mainly used by China Electric Power; disable in affected areas Same
ChMaskCntl 0→0-15 / 1→16-31 / 2→32-47 / 3→48-63 / 4→64-79 / 5→80-95 / 6→all on / 7→RFU Split tables for 20 MHz antenna and 26 MHz antenna; meaning similar
Default Max EIRP (constant) 19.15 dBm 19.15 dBm

Two differences worth singling out:

  • DR0 max payload dropped from 51 bytes to 15 bytes (N even becomes N/A). RP002-1.0.5 cuts this so aggressively precisely because it actively aligns with Announcement #52's 1-second red line—as Section 3 will prove, with the LoRaWAN default LDRO enabled, anything over 11 bytes at DR0 SF12 breaks the 1-second rule. The direct engineering impact: any "long payload + DR0" low-rate uplink design needs to be redesigned.
  • CFList goes from "not supported" to "supported". Combined with ChMaskCntl and the 20/26 MHz antenna plans, this means CN470 in RP002 can carry sub-band channel masks in JoinAccept and fully configure an 8-channel gateway. For terminals that only support v1.0.3, this field is ignored automatically.

Sources: - "LoRaWAN 1.0.3 Regional Parameters" §2.7 CN470-510 MHz Band (LoRa Alliance official PDF) - "RP002-1.0.5 LoRaWAN Regional Parameters" §3.9 CN470-510 (LoRa Alliance official document) - SX126x-Arduino Region CN470 SDK header constants

3. The 1-Second Red Line: How Many Bytes Can DR0/DR1 Actually Send

Announcement #52 Item 4 says: "Single-shot transmission duration: no more than 1 second."

This is the most-overlooked rule, but it's nearly fatal for low-rate uplinks (DR0/DR1). The table below uses SX1262-style parameters (preamble = 8, explicit header, CRC on, LDRO auto-enabled for SF11/SF12@125 kHz) to measure per-packet airtime:

DR SF BW 10 B 11 B 20 B 36 B 37 B 40 B 51 B 115 B 222 B
DR0 SF12 125 kHz 991 ms ✅ 1155 ms ❌ 1318 ms ❌ — — — — — —
DR1 SF11 125 kHz — — — 987 ms ✅ 1069 ms ❌ — — — —
DR2 SF10 125 kHz — — — — — — 616 ms ✅ — —
DR3 SF9 125 kHz — — — — — — — 615 ms ✅ —
DR4 SF8 125 kHz — — — — — — — — 615 ms ✅
DR5 SF7 125 kHz — — — — — — — — 379 ms ✅

Measured conclusions:

  1. DR0's compliant payload ceiling is only 10 bytes. Just one more byte (11 B) jumps airtime straight to 1155 ms, exceeding the 1-second red line by over 15%. This isn't "close to the ceiling"—it's a 155 ms violation, single-packet non-compliance.
  2. DR1's compliant payload ceiling is 36 bytes. 37 bytes jumps to 1069 ms, 7% over.
  3. DR2 and above are not affected by the 1-second red line—DR2's 51-byte cap, DR3's 115-byte cap, DR4/5's 222-byte cap all stay around 600 ms.

Data source: ThinkLink LoRa Calculator (based on Semtech SX126x formulas). The same dataset is independently produced in Semtech's official LoRa Q&A §3 (Table 2 "Transmission Time (ms)"), which lists SF11/40 B = 905.22 ms, SF11/60 B blank, SF12 only up to 10 B—same order of magnitude; Semtech's table mixes explicit/im implicit header conventions, but the order of magnitude is identical.

Key fact: If you design uplink payloads on CN470 according to the v1.0.3 default of DR0/DR1 + 51 bytes, you're treating the 1-second red line as a "theoretical ceiling" while every packet in production is non-compliant. RP002-1.0.5 cutting DR0 max MACPayload to 15 B is essentially the Alliance closing this red line for you at the compliance layer.

3.1 Three Hidden Engineering Actions

  • If your terminal uses SX1276/SX1262's default LDRO configuration (SF11/SF12 @ 125 kHz auto-enabled), the table above is your directly usable compliance boundary.
  • If your terminal explicitly disables LDRO (some low-power SDKs do this to save 1 symbol of processing overhead), the DR0/10 B airtime is slightly shorter, but receive sensitivity degrades significantly (processing gain drops) and network capacity shrinks—it's a bad trade-off.
  • If your device is Class B / Class C, the same "single packet ≤ 1 second" constraint also exists in RX1/RX2/RX2b downlink windows—Announcement #52 doesn't explicitly exempt these, so Class B/C downlinks should stay at DR2 or above.

4. The Unit Trap: 50 mW e.r.p. ≠ 50 mW EIRP

This deserves a section of its own because nearly all public LoRaWAN documents quote Announcement #52's 50 mW as if it's EIRP—but the announcement's original text uses e.r.p. (Effective Radiated Power, relative to a half-wave dipole).

  • 50 mW = 16.99 dBm ≈ 17 dBm;
  • ERP is 2.15 dB lower than EIRP (because a half-wave dipole antenna has 2.15 dBi more gain than an isotropic radiator);
  • Therefore 50 mW e.r.p. = 17 dBm ERP ≈ 19.15 dBm EIRP.

LoRa Alliance RP002-1.0.5 §CN470-510 explicitly states: CN470_DEFAULT_MAX_EIRP = 19.15—this 19.15 is the EIRP expression of 50 mW ERP.

Engineering impact:

Regulatory expression LoRaWAN expression Difference
50 mW (e.r.p.) ≈ 17 dBm ERP Max EIRP 19.15 dBm 2.15 dB
Default power index 0 (17 dBm output) 17 dBm output + 2 dBi antenna = 19 dBm EIRP (compliant) —
19 dBm output + 2 dBi antenna = 21 dBm EIRP Exceeds Max EIRP by 1.85 dB (non-compliant) —
27 dBm output + 2 dBi antenna = 29 dBm EIRP Exceeds Max EIRP by 9.85 dB (severely non-compliant) —

If your gateway defaults to 27 dBm output (the default for many EU/US gateways), adding a 2 dBi antenna gives 29 dBm EIRP—10 dB above the 19.15 dBm EIRP red line, i.e., 10× the power. For CN470 deployment in China, you must turn the power down to ≤ 17 dBm ERP / 19.15 dBm EIRP, then leave 1–2 dB of margin depending on antenna gain and link budget.

The GD61x power setting is locked by the regional variant at the factory (the gwTool6 Configuration Guide §6 explicitly says "the regional standard comes from factory configuration and cannot be changed on the page"); the GD614 regional variant for CN470 ships within the compliant range by default. Other regional variants need their power re-validated before domestic use.

Sources: - RP002-1.0.5 §3.9 CN470-510 (CN470_DEFAULT_MAX_EIRP = 19.15, CN470_DEFAULT_ANTENNA_GAIN = 2.15) - Semtech LoRa Q&A §3 ("50 mW E.R.P is already a large output power; equivalent to 50 mW output power connected to a 2 dBi antenna") - ThinkLink docs-zh-device-lorawangateway-gd6-configuration-guide

5. Three Hidden Landmines on the Spectrum

The seven hard constraints are the "surface". Stack your deployment map onto the actual spectrum, and three hidden landmines appear.

5.1 Landmine #1—China State Grid Occupies 66 of 96 Channels

Both RP v1.0.3 and RP002-1.0.5 explicitly state in the CN470-510 section:

Channel Index 6 to 38 and 45 to 77 are mainly used by China Electric Power. In the areas where these channels are used by China Electric Power, they should be disabled.

In plain English: out of 96 uplink channels, State Grid has long-term deployments for distribution automation, AMI and station-area monitoring on channels 6–38 and 45–77, totaling 66 channels. This means:

  • In cities/neighborhoods where State Grid has deployed LoRa/micro-power wireless systems, only 30 channels remain usable (0–5, 39–44, 78–95);
  • These 30 channels aren't contiguous—they're scattered across 470.3–471.3 MHz, 478.1–479.1 MHz, and 485.9–489.3 MHz in three disjoint segments;
  • Even in cities where State Grid hasn't deployed yet, there's still the long-term risk that "State Grid could enter at any time".

Deployment recommendations:

Region Recommended channel subset (ChMask = all on, 0xFFFF…) Recommended channel subset (avoiding State Grid)
Areas known to have no electric micro-power cn470_0..cn470_11 all on cn470_0 + cn470_11 (i.e., 0–7 + 88–95)
Areas with electric micro-power deployments Only enable 0–5, 39–44, 78–95 Same, and deprioritize 39–44

The gwTool6 Configuration Guide for GD61x explicitly states: "GD6 only supports 8 receive frequency points; the frequency span within the same radio group must satisfy the IF window constraint shown on the page." This means the GD6 can only demodulate 8 channels at any moment, so "avoiding the electric-power channels" strategy must be done together with "sub-band selection", not retroactively via ChMask.

5.2 Landmine #2—DTMB Terrestrial Digital TV Co-Channel

Announcement #52's original text: "If the operating frequency coincides with a local sound or TV broadcast station's frequency, it must not be used locally."

China's UHF TV broadcasting planning has long used 470–566 MHz and 606–798 MHz. 470–510 MHz falls right within DTMB terrestrial digital TV's UHF channels 14–20 range (each channel is 8 MHz wide). In most prefecture-level cities and above:

  • 470–478 MHz (ch 14) may have DTMB transmitters;
  • 478–486 MHz (ch 15) is typically assigned to local news/educational channels;
  • 486–494 MHz (ch 16) starts being used at county level;
  • 502–510 MHz (ch 19–20) is usually reserved for provincial SFNs (single frequency networks).

In other words, LoRaWAN CN470's downlink 500.3–509.7 MHz partially overlaps with the DTMB city coverage network in most cities.

Deployment recommendations:

  • Before deployment, do an on-site DTMB survey. An RTL-SDR plus a spectrogram will tell you which UHF channel DTMB is centered on.
  • If DTMB lands on ch 19 (502–510 MHz), the downlink RX2 (505.3 MHz) is directly drowned by DTMB's 8 MHz signal—you need to either make this gateway uplink-only and disable RX2, or concentrate all downlink packets into ch 17/ch 18 (488–502 MHz) in your channel plan.
  • Uplink 470.3–489.3 MHz is relatively clean, but once county-level DTMB ch 14/15 transmitters come online, channels 0–5 (470.3–471.3 MHz) must yield.

5.3 Landmine #3—"Single-Channel Transmission at Any Moment"

Among Announcement #52's civil metering requirements is one that LoRaWAN practitioners often overlook:

Only one channel may transmit at any given moment.

The literal meaning is: transmission (including uplink and gateway downlink) must guarantee "only one channel is occupied at any moment". For terminals, LoRaWAN's random channel hopping is per-frame, and there's no "simultaneous multi-channel transmission"—compliant. But for gateways:

  • SX1302's 8-channel RX path allows 8-way parallel reception, and the regulation doesn't restrict reception (the "operation" refers to transmission)—compliant.
  • SX1302 only has 1 TX channel, so downlink is naturally compliant.
  • However, if you try to use SX1303's dual-TX (dual-GW mode) for accelerated downlink, you must revert to single-TX mode for CN470.

Deployment recommendations:

  • A normal LoRaWAN CN470 gateway with 8-channel RX and 1-channel downlink meets Announcement #52's literal requirement.
  • If you use ChirpStack's "centralized gateway downlink" or similar schemes to make one gateway concurrently transmit downlink to multiple channels, you need to first evaluate whether this breaks the single-channel-transmit compliance boundary—per Announcement #52's literal reading, it does.
  • This also means CN470 gateways should not be deployed as "regional primary gateways", but rather as building/community/village-level local access points.

6. The 7-Item Compliance Deployment Checklist

All the constraints above mapped to a checklist:

# Check Item Verification Method Non-Compliance Action
1 Device regional variant is CN470 (with SX1302/SX1301) Gateway nameplate / order model Switch to the CN470 regional variant (GD61x must be something like GD614-AN-CN470-N-2)
2 Transmit power ≤ 50 mW ERP / 19.15 dBm EIRP Gateway RF parameters + antenna gain calculation Turn TX Power down to 17 dBm ERP (with 2 dBi antenna = 19 dBm EIRP) or below
3 Channel plan avoids State Grid channels 6–38, 45–77 Gateway Channel Mask configuration LinkADRReq ChMask only opens 0–5, 39–44, 78–95, or adjust per requirement
4 On-site DTMB survey: channels don't overlap with local DTMB UHF channels Spectrum scan / DTMB channel list Disable or shift frequency on DTMB co-channels
5 Per-packet payload ≤ 10 B for DR0, ≤ 36 B for DR1 Terminal firmware + uplink packet capture verification Disabling LDRO is suboptimal; the right approach is to cap MACPayload size and align with RP002
6 Gateway downlink does not use multi-channel concurrent TX Gateway model and platform configuration Revert to SX1302 single-TX mode (GD61x defaults are compliant)
7 Terminal has "transmit-before-search" that cannot be disabled Terminal SDK CAD configuration Semtech LoRa CAD is enabled by default; check LoRaMac-node / RadioLib configuration

If items 1–6 all pass, but item 7 doesn't explicitly enable LoRa CAD channel detection, then strictly speaking you've only "got the technical capability"—you haven't proven "it's been activated". Semtech's LoRa Q&A states: "Semtech's LoRa chips themselves provide the Channel Activity Detection (CAD) function, which already provides a good technical basis for 'transmit-before-search' and other interference-avoidance functions. At the same time, LoRa chips all have frequency hopping, which can also be used for interference avoidance."—the essence of this is "hardware has CAD", but whether the software invokes it and whether it's been disabled by the end user is the key at the compliance audit level.

7. ManThink GD6 Compliance Configuration on CN470

The GD61x (GD614 regional variant) gives a complete "region, sub-band and channel" configuration flow in the gwTool6 Configuration Guide:

  1. Model selection: CN470 deployment requires the GD614 400 MHz-class radio variant. With SX1302, that's GD614-AN-CN470-N-2 (without 4G/PoE; with 4G/PoE use GD614-AG-CN470-N-2).
  2. Login to gwTool6: default Web password wifi!0804; change immediately on first login (the two passwords can be modified separately).
  3. Configure LoRaWAN NS: choose ThinkLink or ChirpStack + Semtech UDP / Basic Station / ThinkLink MQTT Bridge. Basic Station and Packet Forwarder are mutually exclusive—switching interrupts service for 30–60 seconds.
  4. Configure "Radio Parameters": - Regional standard: CN470-510. - Sub-band (cn470_0..cn470_11) chosen per §5.1 above, avoiding electric-power channels. - Frequency point span must satisfy the page's IF window limit. - When Basic Station is active, the channel plan is pushed by LNS/CUPS, and the local "Radio Parameters" only takes effect after switching back to Packet Forwarder.
  5. Don't do hardware-level magic: gwTool6 §6 explicitly warns "you cannot change one band into another band by modifying the page".
  6. REST API / Remote Configuration: uses an independent MQTT channel (credentials independent from the LoRaWAN data channel); prepare a local recovery path before enabling.

On top of the above, the ManThink team has validated these two patterns at CN470 customer sites:

  • In cities known to have State Grid LoRa deployments, disable cn470_0..cn470_11 sub-bands 1–9, keep only cn470_0 (ch 0–7) and cn470_11 (ch 88–95), fill the 8 frequency points, then let the network server do fine-grained ChMask adjustment.
  • In cities with DTMB, use cn470_11 (ch 88–95 in 487.9–489.3 MHz) as the only active sub-band, keep downlink RX2 at 505.3 MHz, but avoid placing the receive channels in 502–510 MHz (ch 19, a common DTMB segment)—this means the customer must accept that the uplink only covers the 1.4 MHz sub-band of 487.9–489.3 MHz.

8. Five Common Misconceptions

Misconception 1: "50 mW maps directly to EIRP"

Fact: 50 mW is ERP, equivalent to EIRP 19.15 dBm. Power tables or device specs that say "50 mW output" or "17 dBm output" implicitly include 2 dBi antenna gain; with a 5 dBi high-gain antenna, the transmit power must be turned down to about 14 dBm to keep total EIRP unchanged.

Misconception 2: "RP v1.0.3 and RP002-1.0.5 Are the Same"

Fact: The biggest differences for CN470-510 between the two versions are maximum MACPayload (DR0 dropped from 59 B to 15 B) and CFList support (v1.0.3 unsupported, RP002 supported). If your terminal firmware strictly follows v1.0.3 but the server and gateway use RP002, and DevNonce/Join flows conflict with ChMask—this is the most common hidden bug from version mismatch.

Misconception 3: "A Gateway in a Community/Building Covers 5 km"

Fact: Announcement #52 explicitly says "small-area networking". The "5–15 km LoRa long-range" marketing is measured in open space, no DTMB, no electric-power conflicts, no co-channel interference; CN470 in urban scenarios usually falls back to 1–3 km radius, denser areas need denser gateways. "Small area" is not only a regulatory requirement but also physical reality.

Misconception 4: "CN470 Is an ISM Band, So It's Globally Compliant"

Fact: CN470 is not ISM in ITU Region 3 (including China). It's listed in the "Radio Frequency Allocation Regulations" as "radiolocation, fixed, mobile services"; micro-power use is "shared" not "exclusive". 433 MHz is ISM in Europe, 902–928 MHz is ISM in the US. If you "export CN470 equipment" to other regions, you either change the regional variant (GD618 EU868/US902/AS923/AU915) or follow that region's compliance path.

Misconception 5: "Micro-Power Equipment Doesn't Need SRRC Type Approval"

Fact: Half-true. Announcement #52 Item 1 says "no need to obtain... radio transmitting equipment type approval", but the "Regulations on the Administration of Radio Transmitting Equipment" (MIIT Order No. 57, effective 2023-07-01) Item 25 adds: "the special marking for micro-power short-range radio transmitting equipment shall be marked on the equipment and in its user manual"—i.e., SRRC type approval certificate is still exempt, but the device and its manual must carry the "micro-power special marking" (style to be defined separately). In other words: compliance cost shifts from "send for testing" to "label + write a regulatory reference in the manual", but it doesn't disappear.

9. A Final Word of Grounding

Returning to the opening line: "LoRa wasn't restricted—it was permitted."

Announcement No. 52 of 2019, the 2021 "Industrial Internet and IoT Radio Frequency Usage Guide", and the 2023 "Regulations on the Administration of Radio Transmitting Equipment" together form the compliance framework for CN470. Its core features:

  • No frequency occupancy fee, no type approval, no station license, but must meet the 7 hard constraints;
  • "Small-area networking" is both the regulatory boundary and the fundamental reason LoRa has long been positioned in China as "LAN/private network" rather than "carrier WAN";
  • The 1-second single-packet red line + 50 mW ERP power red line are the two main constraints for engineering deployment—the former affects payload design for low-rate uplink scenarios, the latter affects power budget on every transmit side;
  • Three hidden landmines on the spectrum (China State Grid, DTMB, single-channel transmission) are the real divide between "meeting the spec" and "actually deployable";
  • RP002-1.0.5 has already done part of the compliance work for you (tightening max payload, supporting CFList), but only when "terminal firmware + server + gateway" are all upgraded to RP002.

For engineering teams, the gap between "can I use LoRaWAN CN470?" and "can I use LoRaWAN CN470 compliantly in China?" isn't technology, but the discipline of checking off the 7 hard constraints, 3 landmines, and 1 checklist.

Appendix A: Glossary

Term Meaning
ERP Effective Radiated Power, relative to a half-wave dipole
EIRP Effective Isotropic Radiated Power, relative to an isotropic radiator
ISM Industrial, Scientific and Medical; CN470 is not ISM in China
OTAA Over-The-Air Activation
ABP Activation By Personalization
LBT Listen Before Talk
LDRO Low Data Rate Optimization, enabled by default for LoRa at SF11/SF12@125 kHz
CAD Channel Activity Detection, LoRa chip's channel activity detection, equivalent to LBT
Dwell time Maximum single-channel occupancy time
ChMask Channel mask in the LinkADRReq command
DTMB Digital Terrestrial Multimedia Broadcast, China's terrestrial digital TV standard
EIRP 19.15 dBm EIRP expression of 50 mW ERP, corresponding to LoRa Alliance's CN470_DEFAULT_MAX_EIRP constant

Appendix B: References

  1. "Announcement No. 52 of 2019 of the Ministry of Industry and Information Technology of the People's Republic of China—Catalogue and Technical Requirements for Micro-Power Short-Range Radio Transmitting Equipment." Source: MIIT official website / State Council policy interpretation.
  2. "Regulations on the Administration of Radio Transmitting Equipment" (MIIT Order No. 57), promulgated 2022-12-22, effective 2023-07-01.
  3. "Industrial Internet and IoT Radio Frequency Usage Guide (2021 Edition)" (Gong Xin Bu Wu [2021] No. 61), issued 2021-05-25.
  4. LoRa Alliance "LoRaWAN 1.0.3 Regional Parameters" §2.7 CN470-510 MHz Band.
  5. LoRa Alliance "RP002-1.0.5 LoRaWAN Regional Parameters" §3.9 CN470-510.
  6. Semtech official LoRa Q&A ("LoRa meets all the requirements of China's MIIT Announcement No. 52").
  7. ThinkLink official documentation: gwTool6 Configuration Guide, GD61x Indoor LoRaWAN Gateway Specification and User Guide. Source: https://www.think-link.net/docs/zh/Device/LoRaWANGateway/gd6-configuration-guide and https://www.think-link.net/docs/zh/Device/LoRaWANGateway/gd61x-user-guide .
  8. "RF Metrics and Test Guide for Narrowband Low-Power IoT Gateway Equipment in the 470 MHz–510 MHz Band" (industry test specification—adjacent-channel leakage, occupied bandwidth, etc.).
  9. SX126x-Arduino Region CN470 SDK header constants (CN470_DEFAULT_MAX_EIRP, CN470_DEFAULT_ANTENNA_GAIN, etc.).
  10. "Technical Requirements and Test Guidelines for RF Metrics of Narrowband Low-Power IoT Gateway Equipment in the 470 MHz–510 MHz Band" (industry reference for adjacent-channel leakage, occupied bandwidth, etc.).