12.3 Low-Power Wide-Area Network (LPWAN) Technology Selection
12.3.1 LPWAN Requirements Analysis for Agriculture
The smart irrigation control logic introduced in the previous section — whether it relies on steady-state threshold decisions or adds feed-forward correction from weather forecasts — rests on one precondition: that field sensor data and actuator commands can be transmitted reliably and at low cost across the farmland environment. A typical farm spans several hectares, with nodes scattered across open fields or inside greenhouses; wired deployments are costly to cable and difficult to maintain, while short-range wireless technologies (Zigbee, BLE, etc.) are limited by communication distance. LPWAN is then almost the only reasonable choice — it was designed precisely for IoT scenarios that need long range, low data rates, and long battery life, which matches the communication demands of an agricultural environment closely.
Before making the technology selection, engineers need to sort out the specific constraints that agricultural scenarios impose on LPWAN. These constraints come mainly from four dimensions: coverage distance, data rate, power consumption and battery life, and device and operations cost.
Coverage distance. An open-field farm typically runs from several hectares up to a hundred or more, and the plot boundaries of a large plantation or farm can stretch a considerable distance. Structured greenhouses are smaller in area, but their metal frames, film covering, and dense crops (corn, tall fruit trees) visibly block and absorb wireless signals. The water content of plant leaves attenuates electromagnetic waves markedly, and a densely planted crop canopy pushes the link budget down further. The LPWAN technology must therefore not only cover line-of-sight distances of several kilometers but also carry a link budget high enough to penetrate the crop canopy and obstacles. In open countryside, LoRa's typical coverage radius reaches several kilometers, and NB-IoT, riding on operator base stations, achieves similar coverage over open ground — both meet the basic distance requirements of agricultural scenarios.
Data rate. Agricultural monitoring is a classic "uplink-dominated" traffic pattern. Most sensors (soil moisture, temperature, weather stations) upload only tens to a few hundred bytes at a time, and infrequently — soil parameters may be reported once an hour, weather parameters every 15-30 minutes. A few scenarios (such as high-resolution pest and disease images) generate larger data volumes, but that is a special requirement, usually carried by a separate high-bandwidth channel (such as 4G/5G) so it does not crowd LPWAN's narrowband channel. Downlink traffic is even scarcer — mainly occasional parameter configuration, threshold updates, or irrigation on/off commands, mostly no more than a few bytes. The agricultural requirement on data rate is therefore "extremely low but stable": a few hundred bits per second to a few tens of kilobits per second is enough. LoRa's over-the-air rate sits at the low end, and NB-IoT's peak rate is somewhat higher — both can cover this class of need.
Power consumption and battery life. This is the cost core of an agricultural deployment. Mains power is hard to obtain in the field, so most sensor nodes run on batteries (for example, two AA lithium thionyl chloride cells) or on small photovoltaic panels. The three common battery chemistries each have their place: lithium thionyl chloride suits long-life, maintenance-free nodes; alkaline cells are cheap but limited in lifetime and low-temperature performance; photovoltaic plus lithium-ion suits higher-power nodes that receive periodic maintenance. Promotional material from the LoRa chip vendors and the LoRa Alliance often uses "running for years on one battery" as a selling point; for an uplink service with agriculture's extremely low duty cycle, that claim largely holds and is consistent with what one expects of node endurance — a target of at least 1-2 years, ideally 3-5 years of maintenance-free operation — and the worked example in Section 12.3.3 will give a recomputable basis for it. Power consumption comes down to three factors: the energy to acquire sensor readings, the transmit energy of the communication module, and sleep consumption. The communication module's instantaneous transmit current is not low, but its duty cycle is extremely low (it may transmit only a few times a day); the bulk of the energy instead comes from the MCU's sleep leakage current and the management circuitry. A carefully designed node can hold its total average current to a low level, and a sufficiently large battery keeps it running for more than two years. Because NB-IoT must synchronize with and attach to a base station, the act of getting connected itself incurs a fixed energy overhead, and its standby current is typically an order of magnitude higher than LoRa's; still, for most agricultural uplink applications, paired with long sleep cycles, it too can reach multi-year battery life.
Cost. Cost has two sides: hardware cost and operations cost. On the hardware side, agricultural IoT is a high-volume, thin-margin business, and the bill of materials for each node must be cheap. LPWAN is itself positioned as a low-cost wireless option, and module prices in volume are usually already low enough. Sensors are usually the bigger share: some commercial-grade sensors carry a high unit price, which bears directly on the selection decision. The crux of operations cost is communication fees: LoRa runs in unlicensed spectrum, and once you build your own gateway there is no service charge; NB-IoT needs a SIM card and an operator tariff. For large growers or farms that own their land, building a private LoRaWAN network is more economical; for scattered plots or policy-driven projects, relying on an operator's NB-IoT network lowers the maintenance barrier.
Table 12-2 pulls these requirements into one clear comparison sheet for direct reference during the technology selection that follows.
Table 12-2 Core requirements that the agricultural IoT scenario places on LPWAN communication technology
| Requirement dimension | Typical requirement | Importance and key details |
|---|---|---|
| Coverage distance | Open farmland requires coverage over longer distances; extra attenuation must be allowed for when penetrating densely planted crops | High. The link budget must account for crop-canopy attenuation. |
| Data rate | Uplink: low rate; downlink: very low rate | Medium. Suits periodic sensor reporting; high-resolution images need a separate broadband channel. |
| Power and battery life | Low average current; target endurance 1-5 years | High. The key is optimizing MCU sleep current and communication duty cycle. |
| Device cost | Communication module and sensor costs are the main consideration; overall cost should be as low as possible | High. Sensor cost often exceeds the communication module itself. |
| Downlink control frequency | Very rare; wake-up-style reception is acceptable | Low. Fits occasional operations such as irrigation on/off and threshold setting. |
| Deployment model | Nodes scattered; self-built gateways or reliance on operator base stations | Medium. Self-built gateways are more economical over large areas; relying on operator NB-IoT is simpler for small areas. |
This table outlines a clear selection framework: agriculture's core demands on LPWAN can be summarized as "long coverage, low rate, long battery life, low cost," with predominantly one-way uploading. In the actual engineering of technology selection, then, the engineer must answer one central question: of the two mainstream LPWAN technologies, LoRa and NB-IoT, which one satisfies all of the above demands while having the most mature ecosystem — and where are the trade-offs on each side? (Sigfox was once a third path, but after the Sigfox company was acquired by UnaBiz in 2022 it no longer operates as an independent company — its 0G network is still operating and has shifted toward a multi-LPWAN convergence strategy, so it is retained in the comparison table only as a historical reference.) The next section, 12.3.2, compares them one by one.
12.3.2 LoRa vs NB-IoT vs Sigfox Technology Comparison
The previous section sorted out the four constraints agriculture places on LPWAN — coverage, rate, power, and cost. Now those constraints must land on concrete options. The band attributes, modulation principles, and PSM/eDRX power-saving mechanisms of LoRa and NB-IoT were laid out systematically in Sections 4.1 and 4.2; this section does not re-derive them and discusses only how agricultural constraints change the selection weights. LoRa, NB-IoT, and Sigfox have each billed themselves as the rightful heir of LPWAN, yet the three differ radically in implementation philosophy: LoRa hands you the autonomy to build your own network, NB-IoT lets you lean on the operators' existing base stations, and Sigfox used its "ultra-narrowband" to lock in a closed path (after the Sigfox company was acquired by UnaBiz in 2022 it no longer operates as an independent company — its 0G network is still operating and has shifted toward a multi-LPWAN convergence strategy; it is retained in this comparison only as a historical route reference). No option is perfect by nature — selection is essentially a matter of weighting the four dimensions according to the scenario.
12.3.2.1 Parameter Overview
Table 12-3 compares them side by side across five aspects: frequency band, rate, link budget, network architecture, and cost structure. The data are based on the technical specifications published by each technology alliance, with some figures being industry consensus or ranges (actual values fluctuate with configuration and purchase volume); the qualitative conclusions on band ownership and networking model are grounded in Section 4.1 and are not separately annotated.
| Comparison dimension | LoRa / LoRaWAN | NB-IoT | Sigfox |
|---|---|---|---|
| Operating frequency band | Unlicensed Sub-GHz (868/915/433 MHz, etc.) | Licensed LTE bands (Band 8/20, etc.) | Unlicensed Sub-GHz (868/902 MHz) |
| Modulation | CSS (Chirp Spread Spectrum) | OFDMA (Orthogonal Frequency Division Multiple Access) / SC-FDMA | UNB (Ultra Narrow Band) |
| Typical uplink rate | As low as 0.3 kbps, as high as 50 kbps (depending on the spreading factor) | Theoretical uplink on the order of 150 kbps (multi-subcarrier); in practice limited by coverage and scheduling | Extremely low (typically about 100 bps) |
| Uplink payload per message | 51 – 242 bytes (SF12 → SF7) | Usually > 100 bytes | 12 bytes |
| Link budget | Extremely high (built on CSS sensitivity) | High (about 164 dB as defined by the 3GPP standard) | Extremely high (inferred from UNB) |
| Typical transmit current | Lower (typical values for common modules; the transmit peak can reach about 120 mA @ +20 dBm depending on the power setting — see 12.3.3) | Higher (200–300 mA) | Lower (20–40 mA) |
| Network architecture | Star of self-built / public gateways | Star of operator base stations | Star of proprietary base stations |
| Module cost | Moderate (amortized by LoRa Alliance scale) | Slightly higher (must support LTE) | Lower (ultra-narrowband simplifies the chip) |
| Gateway/base-station investment | Gateways must be purchased (hundreds to thousands of US dollars) | No self-built base stations needed | No self-built base stations needed (but coverage is limited) |
| Connectivity fees | No operator fees (the backhaul link cost is on you) | Tens of RMB per device per year | A few US dollars per device per year |
| Ecosystem openness | LoRa Alliance ~360 members (2025); data sovereignty can be kept in-house | Closed to operators; data tied to the SIM card | Closed ecosystem; a single chip supplier |
Table 12-3 Core parameter comparison of LoRa / NB-IoT / Sigfox (Sigfox has left the mainstream and appears in the table only as a historical route reference) (Module cost and fees are qualitative ranges, not precise market quotations; specific values vary considerably with purchase volume, region, and time.)
Two Things the Physical-Layer Differences Come Down to in the Field
Band ownership determines how freely you can build your own network, which Section 4.1 has already made clear: LoRa runs in unlicensed Sub-GHz and can be self-built; NB-IoT occupies licensed LTE bands and rides on the operators; Sigfox also uses unlicensed Sub-GHz, but its physical layer is ultra-narrowband with only 100 Hz of bandwidth per channel, and its uplink message frequency is limited by local regulations such as Europe's ETSI. What really carries weight for farmland selection are two other things.
The first is the payload ceiling. LoRa's payload shrinks with the spreading factor from 242 bytes (SF7) down to 51 bytes (SF12); a JSON sampling frame with a timestamp and status bits (a few dozen bytes) fits at the low SF tiers but gets tight at SF12. Sigfox allows only 12 bytes per uplink — not even a complete JSON fits — so only predefined enumerated status codes can be sent; for agricultural sensor firmware accustomed to "sending JSON directly," this is a hard constraint.
The second is airtime. A high spreading factor stretches airtime out multiplicatively: a frame of a few dozen bytes sends in under a second at SF7 but takes 2–3 seconds at SF12 — four to six times the 0.5-second estimate used in the worked example of Section 12.3.3 — and far-end nodes with tight link margins must book this cost into the power budget. Unlicensed-band options carry one more restriction: remote upgrade is all but infeasible — even streamed continuously at LoRa's fastest over-the-air rate of 50 kbps, the raw transfer of 2 MB of firmware takes about 5 minutes; long-range deployments commonly sit at the 0.3–1 kbps high-spreading-factor tiers, where the raw transfer stretches to roughly 4–15 hours; stack the 1% duty-cycle limit on top and one upgrade is counted in weeks — the node's battery cannot sustain that drain. The firmware strategy for LoRa nodes should therefore rely mainly on on-site upgrades during maintenance windows back in the field, while the NB-IoT side can support FOTA (Firmware Over-The-Air).
Link Budget and Obstacle Penetration
All three have nominal link budgets on the order of 150 dB. In a real field, though, vegetation and terrain eat part of that budget. Vegetation-attenuation propagation models such as ITU-R P.833 and multiple field-measurement studies commonly report signal attenuation of 20–30 dB inside a densely planted cornfield, and every Sub-GHz option is affected. What actually separates the contenders is not the nominal link budget but how freely base stations and end devices can in fact be placed. A self-built LoRa gateway can stand at the center or the highest point of each field, keeping the distance from end device to gateway within a few hundred meters to 1–2 km; NB-IoT base stations, meanwhile, tend to sit near villages or transport lines, with signals having to cross hills and valleys. Even though NB-IoT's link budget is higher, in remote agricultural areas its actual communication success rate often falls short of a well-placed LoRa gateway.
Network Architecture and Networking Flexibility
This is the sharpest strategic divergence among the three. LoRaWAN can be built, customized, and managed by anyone, and the roughly 360 alliance members (2025) listed in Table 12-3 underpin a cross-vendor device ecosystem. You can install your own LoRa gateway on the farm, connect it to a private network server, and keep the data isolated within the campus, with no operator fees. The gateway needs power and a backhaul link (usually 4G/5G or fiber). For a farm of tens of hectares, one or two gateways are enough to cover it. NB-IoT uses operator base stations directly: a device joins the network once fitted with a SIM card or eSIM, at zero network-planning cost. But LTE coverage is thin in remote areas — if the base station is several kilometers from the farm with hills in between, NB-IoT reliability drops sharply. Sigfox is also an operator-built network model, but its coverage concentrates in cities and along main roads and is very weak in agricultural areas. Its ecosystem is closed, its chip supply carries a high barrier, and its flexibility and room to evolve fall short of LoRaWAN.
Where a plot lies beyond the reach of both operator base stations and self-built gateways — pastoral areas, mountain forest farms, open-sea aquaculture — the Non-Terrestrial Network (NTN) satellite IoT introduced by 3GPP in Release 17 is becoming a fourth option: it adapts the NB-IoT protocol to low-Earth-orbit satellite relaying, trading lower rates and higher latency for full-area coverage. For now, satellite IoT modules and connectivity fees remain markedly higher than terrestrial options; in agriculture it fits better as a supplementary means at coverage gaps than as the mainstay.
Cost Structure
Selection is in substance a trade-off between "one-time self-build investment vs. recurring operating fees." If the farm is small, the node count low (a few dozen), existing LTE coverage good, and in-house IT operations capability limited, NB-IoT's total cost is usually the lowest. If the nodes number in the thousands, the plots are scattered, and the site is remote, the one-time investment in a self-built LoRa/LoRaWAN network is amortized by scale — and there is no recurring connectivity fee. Sigfox holds a cost edge where payloads are tiny and reporting is infrequent, but its usability in agriculture is limited.
Selection Guidance
No all-purpose parameter table can substitute for field testing. Take one LoRa node and a handheld gateway, and spend a morning walking the field boundary measuring SNR and RSSI; or ask the operator for NB-IoT coverage simulation maps and measured values. Judging after seeing measured data is far more reliable than judging from a table alone.
12.3.3 Estimating Node Power Consumption and Battery Life
Agricultural IoT nodes usually sit in fields far from the power grid, and once a battery runs out, the replacement cost far exceeds the node itself. Power estimation directly determines the maintenance cycle and the project's acceptability. Many projects focus only on communication range and data rate in the early phase, overlook the cumulative effect of sleep current and system wake-up time on battery life, and end up six months later with nodes dropping offline across the field. This subsection gives an estimation framework usable in the early design phase, with a worked example based on typical parameters. Actual selection must defer to device datasheets and measured data. The precise power parameters of each device must be taken from its datasheet, so the current and capacity figures below should all be treated as values from a worked engineering example.
Power Consumption Components and Typical Parameters
The power draw of an agricultural sensor node breaks down into four phases:
- Sensor sampling: in measurement mode, sensors such as soil moisture and temperature typically draw a few to a dozen-odd milliamperes for tens to hundreds of milliseconds.
- MCU data preprocessing: reading the data from the sensors and packing it; the MCU typically runs at a few milliamperes for tens of milliseconds.
- Radio transmission: taking a common Sub-1GHz transceiver (designed for the +20 dBm power class, for example), the peak transmit current is about 120 mA; the transmission time depends on the payload and the over-the-air rate and is usually sub-second.
- Sleep: between events, the node enters deep sleep. A modern low-power MCU's sleep current can be as low as the microampere level, and the transceiver's standby mode is also close to microamps. In engineering practice, leave margin and budget 10 μA.
For quick estimation at the solution stage, the following takes a conservative combination of typical node parameters (all numbers are illustrative values and do not represent any specific device):
| Phase | Current | Duration (per event) | Notes |
|---|---|---|---|
| Sensor sampling + MCU processing | 15 mA | 0.3 s | Covers warm-up through completed acquisition |
| Radio transmission (+20 dBm) | 120 mA | 0.5 s | Includes preamble and payload |
| Sleep | 10 μA | Remaining time | MCU + module standby |
Duty Cycle and Daily Consumption
Suppose the node wakes and transmits once per hour, so the period is T = 3600 s. Each wake-up is active for t_active = 0.3 + 0.5 = 0.8 s, and sleeps for t_sleep = T − t_active ≈ 3599.2 s.
Energy consumed per wake-up (mAh):
- Active part: 15 mA × (0.3 / 3600) h + 120 mA × (0.5 / 3600) h ≈ 0.00125 + 0.01667 = 0.01792 mAh
- Sleep part: 10 μA × (3599.2 / 3600) h ≈ 0.01000 mAh Total per cycle ≈ 0.02792 mAh.
Daily consumption = 0.02792 mAh × 24 = 0.670 mAh.
Battery Life Estimation Formula
A battery's usable capacity is affected by temperature and discharge rate. With a typical series arrangement of AA alkaline cells, the nominal capacity must be taken from the specific manufacturer's datasheet. Across the temperature range common in field environments, the actually usable capacity is usually below the nominal value, and self-discharge exists on top of that. Engineering calculations adopt a derating factor to simplify:
life (days) = (nominal battery capacity × derating factor) / daily average consumptionTaking the derating factor = 0.75, life ≈ (3000 × 0.75) / 0.670 ≈ 3358 days, about 9.2 years.
Worked Example: Life Estimates at Different Reporting Intervals
The table below uses the same node parameters and varies only the reporting period, with the derating factor fixed at 0.75 (battery self-discharge is ignored so the rows can be compared side by side). All numbers are illustrative values; actual life must be recalculated from device datasheets and the chosen battery.
Table 12-4 Battery life estimates at different reporting periods
| Reporting interval | Daily consumption (mAh) | Theoretical life (years) | Notes |
|---|---|---|---|
| 1 hour | 0.67 | 9.2 | Suits real-time soil-moisture and weather monitoring |
| 2 hours | 0.455 | 13.5 | Suits scenarios with slowly changing ambient temperature |
| 6 hours | 0.31 | 19.8 | Suits stored data (e.g., cumulative totals) |
| 10 minutes | 2.82 | 2.2 | High-real-time scenarios (e.g., irrigation valve feedback); life is already pressing the maintenance-free floor |
Note: transmit duration in the table is taken as 0.5 seconds, corresponding to sending short frames at the SF7–SF9 tiers; if a tight link margin forces a climb to SF12, the same few dozen bytes take roughly 2–3 seconds of airtime, and this alone lifts the 1-hour tier's daily consumption from 0.67 mAh to about 2.3 mAh and squeezes its life from 9.2 years down to about 2.7 years — link planning and power planning for far-end nodes must therefore be done together.
Table 12-4 also shows that life does not double proportionally as the reporting period lengthens: beyond the 1-hour period, the bulk of daily consumption has shifted from transmission to the 10 μA sleep floor current, and the life curves of the 2-hour and 6-hour tiers flatten out; at that point the roughly 2%–3% annual self-discharge of alkaline cells (about 0.16–0.25 mAh/day when converted) is of the same order as the 6-hour tier's reporting consumption and becomes the life ceiling ahead of discharge depth — this is precisely the basis for switching to lithium thionyl chloride cells, whose self-discharge is an order of magnitude lower, in long-period maintenance-free scenarios. The 1-hour tier is the usual engineering balance point, and its theoretical life covers a typical project's maintenance-free expectation; the 10-minute tier's theoretical life of about 2.2 years will most likely not be reached once low-temperature derating and self-discharge stack on top, so a larger-capacity battery (such as D size), lithium thionyl chloride cells, or solar-assisted charging should be used instead.
Engineering Considerations
- Low-temperature derating: alkaline cells lose capacity sharply at low temperature, and NiMH rechargeable cells suffer increased internal resistance and severe voltage sag. In northern winter conditions, be sure to use low-temperature lithium cells or insulation measures, and increase the derating factor.
- The sleep-current trap: quite a few nodes still leak current while "sleeping" (regulator quiescent current, DC-DC converters); the measured total sleep current can exceed 50 μA, cutting life in half at a stroke. The hardware must be constrained up front with a low-power component list and verified at the prototype stage with a µA-level current meter.
- Actual life is shorter than the theoretical value: battery self-discharge, aging from high-low temperature cycling, and extra wake-ups caused by sensor drift all shorten life. Multiply the theoretical value by 0.6–0.8 as the basis for maintenance planning.
Summary of the Estimation Method
Battery-life estimation is, in essence, the engineering application of the average-current method. Once you hold the current-time integral of each active phase and the static power draw of the sleep period, you can decide the duty cycle and battery configuration early in design. For the agricultural IoT architect, power estimation is not a one-off — it should be embedded in every evaluation round that touches reporting frequency, sensor selection, and firmware upgrades. When the node count reaches thousands, the cost of one round of battery replacement can cover the development cost of a new product. The worked examples in this section provide the starting point; the real engineering judgment comes from checking device datasheets one by one and continuously measuring the actual environment.