LoRaWAN Frequency Plan Guide for US Networks

LoRaWAN Frequency Plan Guide for US Networks

Admin |

A LoRaWAN frequency plan is not a minor configuration detail. It determines whether devices can join, whether gateways hear the traffic you expect, and whether a network can expand without costly field rework. This LoRaWAN frequency plan guide focuses on the decisions US organizations need to make before installing gateways, commissioning sensors, or standardizing on a device fleet.

For a smart metering deployment, industrial site, municipal rollout, or private enterprise network, the right plan aligns four things: local spectrum rules, gateway radio capability, end-device channel settings, and network server configuration. A mismatch in any one of them can create an issue that looks like weak coverage but is actually a channel-plan problem.

What a LoRaWAN frequency plan controls

A frequency plan defines the radio channels and operating parameters available to LoRaWAN devices in a given region. It specifies uplink and downlink frequencies, channel bandwidths, data rates, transmit-power limits, and other regional constraints. LoRaWAN Regional Parameters provide the technical framework, while national regulators define the rules a deployment must follow.

The plan affects more than the frequency printed on a product specification. Gateways must listen on the appropriate channels. End devices must transmit on channels that gateways can receive. The network server must apply the same regional plan when processing joins, managing data rates, and sending downlinks.

This is why a gateway described simply as supporting LoRaWAN is not enough for procurement. A gateway intended for EU868 cannot be substituted for a US915 deployment. Even products built for the 902-928 MHz ISM band may need specific configuration before they operate correctly together.

The US915 plan in practical terms

Most LoRaWAN deployments in the United States use the US915 frequency plan within the 902-928 MHz unlicensed ISM band. The standard plan provides 64 uplink channels at 125 kHz bandwidth, eight additional uplink channels at 500 kHz, and eight 500 kHz downlink channels.

The 125 kHz uplink channels span 902.3 MHz through 914.9 MHz in 200 kHz steps. The 500 kHz uplink channels are interleaved across the same spectrum. Downlinks use channels from 923.3 MHz through 927.5 MHz. This separation matters: a gateway must be configured to receive the intended uplink channels and transmit on valid downlink channels.

In theory, the full US915 channel set offers broad capacity and frequency diversity. In practice, many private deployments use a subset of those channels, often called a sub-band. A standard multi-channel gateway commonly receives eight 125 kHz channels concurrently, plus an associated 500 kHz channel. That radio architecture is well suited to a defined sub-band, but it does not automatically mean the gateway hears all 64 US915 uplink channels at once.

Why sub-band selection causes so many deployment issues

US915 divides its 64 narrowband uplink channels into eight groups of eight. Installers often refer to these groups as sub-bands or frequency sub-bands. Selecting one is a sensible way to deploy a cost-effective private network, provided the gateway and devices use the same group.

The problem usually appears during over-the-air activation. A device configured to attempt joins across all 64 US915 channels may transmit its join request on a channel outside the gateway's active sub-band. The gateway never hears it, so the network server has no opportunity to accept or correct the request. From the installer's perspective, the sensor appears offline despite being within excellent RF range.

Network-server channel masks can manage an end device after it has joined, but they cannot solve an initial join request that the gateway never received. For this reason, the initial device configuration is especially important. A device should be programmed for the active sub-band before field installation, or the network should use gateway infrastructure capable of receiving the device's expected join channels.

This decision has operational implications. A single-sub-band approach simplifies gateway configuration and is often appropriate for contained private networks. A broader channel strategy can improve compatibility with mixed device fleets and reduce onboarding friction, but it may require more radio capacity, more gateways, or different hardware choices. The right answer depends on device volume, site size, application criticality, and how tightly the organization controls endpoint provisioning.

Start with geography, then validate the hardware

Frequency planning begins with the country where each radio will operate, not the country where the equipment was purchased. US915 is common in the United States, but nearby markets and other regions use different regional parameters. Canada also operates in the 902-928 MHz range, yet organizations should validate applicable ISED requirements and device certification rather than assuming a US configuration transfers without review.

Equipment intended for Australia may use AU915, which occupies a similar frequency range but uses a different channel arrangement. A device that is physically capable of transmitting in the band is not necessarily configured for the same LoRaWAN channel plan. EU868, AS923, KR920, IN865, and other regional plans have their own frequency sets and operating constraints.

For cross-border operations, standardize configuration by deployment country. Keep the radio region, channel mask, antenna specification, regulatory approvals, and network-server plan recorded for every hardware SKU. This discipline prevents a warehouse team from sending a correctly functioning but incorrectly regionalized device to a field crew.

A practical LoRaWAN frequency plan guide for private networks

A reliable plan should be established before device purchasing and site surveys are finalized. Begin by defining where gateways and endpoints will operate, then choose the appropriate regional plan. In a US-only deployment, that usually means US915 hardware and a documented decision on sub-band strategy.

Next, confirm the gateway's concentrator capability. Ask how many 125 kHz channels it can receive simultaneously, whether it supports the 500 kHz channel required by the selected configuration, and which channel maps are available in its management interface. Outdoor and industrial gateways may offer the environmental durability and backhaul options needed for the site, but their radio configuration still needs to match the network design.

Then validate the end devices. Many sensors, meters, and trackers allow a US915 channel mask or predefined frequency sub-band to be set through a mobile application, downlink tool, configuration cable, or manufacturing profile. Confirm that the setting applies before the first join attempt. If a vendor uses labels such as FSB 1 through FSB 8, verify the exact channels behind that label rather than relying on naming alone.

Finally, configure the network server to the same regional parameters and test joining at the actual site. Perform tests with the production gateway configuration, not a temporary lab setup that listens on a different channel set. A device that joins successfully in the office can still fail at the deployment site if the gateway channel plan changes during installation.

Dwell time, power, and downlink capacity

Channel selection is only one part of RF compliance and performance. LoRaWAN parameters also address dwell time, maximum payload sizes at certain data rates, and transmit-power behavior. In the US915 regional parameters, dwell-time settings can affect allowable payload sizes and data-rate behavior. These settings should reflect the deployment's regulatory interpretation, device capabilities, and network policy.

Do not treat maximum transmit power as a target. The effective radiated power depends on the radio output, antenna gain, cable loss, and installation characteristics. A high-gain outdoor antenna may improve coverage in one direction while creating compliance or interference concerns if the total system is not engineered correctly. Antenna selection should therefore be evaluated alongside gateway placement, not after coverage problems emerge.

Downlink traffic deserves the same attention. LoRaWAN is designed for low-power uplink-oriented applications. Frequent acknowledgments, remote control commands, and configuration changes consume downlink capacity and can limit scale, especially where many devices share a gateway. A frequency plan will not compensate for an application that relies on excessive confirmed messages or routine downlinks.

Frequency-plan checks before rollout

Before approving a deployment, document these five items:

  • The country-specific LoRaWAN regional plan and applicable regulatory requirements.
  • The gateway's active uplink and downlink channels, including its selected US915 sub-band.
  • The end-device channel mask or sub-band setting used for initial joins.
  • The network server region, data-rate policy, and dwell-time settings.
  • The antenna, cable, and transmit-power assumptions used in the site design.
This record becomes valuable when adding gateways, replacing failed equipment, or onboarding a second device manufacturer. It also gives installers a clear acceptance test: a device should join reliably, send uplinks across the intended operating conditions, and receive only the downlinks the application genuinely requires.

Choosing infrastructure with the plan in mind

The gateway is where frequency planning becomes physical infrastructure. A well-specified LoRaWAN gateway from an established manufacturer can provide the channel capacity, remote management, environmental protection, and backhaul resilience needed for professional deployments. However, the hardware must be selected and configured for the actual regional plan, not just the application's estimated range.

For organizations building private US915 networks, LoRaWorld can help align gateway selection, antenna accessories, and device onboarding requirements with the intended channel plan. This is particularly useful when a project combines indoor gateways, outdoor coverage points, and different endpoint types across a large operational area.

A frequency plan should make every new device easier to deploy, not turn each installation into an RF troubleshooting exercise. Set the regional parameters and sub-band policy early, test the first joins under production conditions, and treat that configuration as part of the network standard.