Key takeawayA gateway and collar must use the frequency plan required in the deployment country. Similar product names do not make different regional versions interchangeable.

Why regional plans exist

LoRaWAN uses license-exempt spectrum regulated by national or regional authorities. Available frequencies, channel spacing, transmit limits and duty-cycle rules differ. The LoRa Alliance defines regional parameters so devices and networks can operate within those rules.

High-level comparison

PlanTypical regionCommon planning point
EU868Many European countriesDuty-cycle and channel configuration require attention
US915United States and related marketsUses a larger channel set and sub-band planning
AU915Australia and some other marketsSimilar band family to US915 but uses its own channel plan

This table is an orientation only. Always confirm the current rules and approved frequency plan for the specific country.

Hardware implications

Some gateways cover several sub-GHz bands, while others are built for one range. Antennas are also frequency-specific. A poorly matched antenna reduces performance even if the gateway radio can be configured for the correct plan. Collar hardware must include the corresponding radio version and firmware configuration.

Channel-plan implications

US915 and AU915 networks commonly use channel subsets or sub-bands to coordinate end devices and gateways. Devices must join using compatible settings. EU868 networks typically use a different set of default and optional channels. Do not copy configuration files between regions without review.

Deployment checklist

  1. Identify the exact country and local regulator.
  2. Confirm the supported LoRaWAN regional parameter version.
  3. Order gateway, antenna and collars for the same plan.
  4. Configure the network server and channel plan before field testing.
  5. Verify join, uplink and downlink operation with production hardware.

International projects

A manufacturer serving several countries should manage product variants by region. Record the radio version on purchase orders and device inventory. If a project spans borders, treat each regulatory region as a separate network design and confirm whether roaming or multi-region hardware is permitted.

Questions to ask a supplier

  • Which exact frequency-plan version does the device support?
  • Can the antenna be supplied for the same band?
  • Which network servers and channel plans have been tested?
  • Can the firmware configuration be locked by project?
  • How is the regional variant identified on the device and packaging?