NB-IoT vs LoRaWAN for Smart Manhole Covers: Which Connectivity Wins Underground?

Tuesday in March 2024: a singular LoraWAN packet transmitted from a sensor in collection, sewers, leaking water in some downtown street in Calgary. In 18 minutes, a storm drain pump was redirected by public works, thus saving $70,000 in potential flood damage on 1 packet.

Imagine what could have happened if that sensor had been outfitted with the wrong radio. A 50 mm-thick cast iron manhole cover could absorb between 20 and 40 dB of a wireless signal. Wrong protocol and $700 manhole cover morphs into a $700 piece of junk buried underground. Right protocol and one transmission uplink addresses six-figure bankruptcy to your city before your operations team even has had its coffee break.

When it comes to the Internet of Things tender notice about smart cities, it specifically says ‘NB-IoT or LoRaWAN’ paving the idea that the two could supplement each other. Regrettably, it is a no to the theory of such a symbiosis: these are totally different specs made with different objectives in terms of power that one assumes the other, in terms of the kind of topology in use, or by the model of ownership recruiting them in practice. In contrast, the NB-IoT vs LoRaWAN decision is one of a kind and breaks in the face of the thought of using both for use in smart manhole cover deployments. It is peculiar to realize that, given the multiyear power supply in an integrated enclosure, the possibility of compressing alert patterns over time.

Certainly, this paper contrasts them based on points relevant to an engineering team currently constructing the device/system. Here, and beyond, we debate issues relating to signal penetration, battery economics, and security and how they influence latency and the net 10-year total cost of ownership. Then, we conclude by providing a framework of consideration called a five-point decision form that anybody can use in all smart market bids. For readers who want a broader overview before diving into protocol selection, see Smart Manhole Covers: A Complete Guide to IoT-Enabled Urban Infrastructure.  To learn about smart manhole covers, please read: What Is a Smart Manhole Cover? Definition, Sensors & How It Works.

Why Connectivity Is the Hardest Decision in Smart Manhole Design

The selection of the protocol is very critical due to the constraints in engineering under which manhole sensors must function.

At the heart of the complications are two great concerns: When cast iron or ductile iron covers are dominant as in ANSI EN 1 2 4 D400 streets, they go RF-opaque. The antenna seems to need to live inside the cover or beneath it, mostly under nothing or below the ground-height level. For every dB of mechanism power loss, you give towards penetration; you may fail to regain one dB for base station coverage.

No-certification-battery may also arise as unseen trivia. Their indefatigable statements seem to rest on an answer expected elsewhere. Some good fellows say IP68 is for 10-year batteries stored beneath the manhole cover. This is not for either the battery system itself or the sensors fed with it. Deployment sizing will consider 6 to 10 years or more on a primary lithium pack, being reported 4 to 24 times a day plus event-driven alerts. Protocol energy efficiency prevails in the bill of materials.

The duty cycle challenge! Manhole sensors blend two traffic patterns: telemetry slow heartbeat (uploads to cloud every few hours) and event triggers by means of alerts (tilt, water level, gas, tamper). Generic LPWAN comparisons consider this as one single workload, but a real manhole IoT device requires two unrelated paths: fast wake-on-event paths as well as frugal heartbeat paths. If you want a deeper breakdown of the sensing layer behind these alert types, see Smart Manhole Cover Sensors: Tilt, Gas, Level & Flood Detection Explained.

This is why the existence of the misleading “NB-IoT range of 1 km, LoRaWAN range of 10 km.” Free-space range numbers will hardly give you anything about whether your sensor will reach a base station below a steel-reinforced street from 1.5 m.

Want a manufacturer’s view of the full sensor stack? See our smart manhole cover product range for hardware engineered around these constraints.

NB-IoT for Smart Manhole Covers: How It Works and Where It Wins

NB-IoT (Narrowband IoT) is a 3GPP-standardized cellular LPWAN that runs on licensed spectrum, defined in 3GPP Release 13 and refined through Releases 14 and 15. It reuses existing 4G/LTE base stations, so the network is already deployed in most urban areas in China, the EU, and parts of the Americas.

Where NB-IoT wins for manhole deployments:

• Deep penetration in dense urban environments. Licensed sub-GHz bands (B5, B8, B20, B28) propagate through concrete, asphalt, and metal grates better than most ISM bands. The Estonian Rakvere field study published by IWA Publishing measured a planning threshold of −104 dBm NB-RSRP at ground level for energy-optimal communication with sensors 0.5 m below plastic covers. That is a real number an RF engineer can design to.
• Security is carrier-grade. Using 3GPP encryption in NB-IoT includes an option for 256-bit AES, with SIM-based authentication. Each device does not bear a burden of having to manage shared application keys.
• Lower latency for alerts. Connections in connected mode are completed in seconds. This on-the-second turnaround is important for alarms such as tampers or sewer overflows.
• Higher data rates. Up to approximately 250 kbps of data within the downlink. A greater capacity may potentially be a nice feature for ultrasound level profiles, gas sampling, or firmware updating.

Where NB-IoT struggles:

• Recurrent SIM card and data charges should be taken into account. Nothing comes with free access; every piece has to pay a carrier monthly. Note that by the time the product reaches 10,000 units, that cost balloons.
• Fracture in regional bands usually occurs. B3 and B20 are the most dominant and prevalent in Europe; B5 and B8 are popular in Asia; and B2, B4, and B12 are used in the Americas. True multiregion OEM products would require software-defined radios or regional SKUs.
• All devices’ battery lives would be driven into the ground under aggressive duty cycles. PSM and eDRX undoubtedly help; however, still under identical parameters, NB-IoT devices expire 1 to 3 years earlier than a replica LoRaWAN-based device.

NB-IoT Power Profile: What 10-Year Battery Life Really Looks Like

A vendor promising “10-year battery life on NB-IoT” must respond seriously to three questions. Firstly, what is the reporting interval-some 4 uplinks per day, with a serious cycle of one hour, span 10 years? Second question is about PSM (Power Saving Mode) to be negotiated with the network. Few operators keep PSM TAU (Tracking Area Update) timers below the value that the device requests. Third, what is the cell-edge RSRP? Below −115 dBm and device wakes up mere seconds early.

In summary, NB-IoT will put up a good 6 to 10 years on a 19,000 mAh class lithium pack, with a 4 reports per day in good coverage. Outward of that assignment, your battery model is in desperate need of revision.

LoRaWAN for Smart Manhole Covers: How It Works and Where It Wins

LoRaWAN is an open protocol stewarded by the LoRa Alliance, running over Semtech’s chirp spread spectrum (CSS) modulation on unlicensed ISM spectrum: 433 MHz and 470 MHz in parts of Asia, 868 MHz in Europe, and 902–928 MHz in the Americas. Unlike NB-IoT, the network is yours to deploy. You install gateways; you operate the network server (TTN, ChirpStack, or a commercial stack); you own the data path end to end.

LoRaWAN would be better for manhole deployments in the following areas:

• Battery life. Eight to fifteen years alone on the primary cell are not bad for a LoRaWAN Class A device sleeping between messages; equivalently, NB-IoT will survive on a 6- to 10-year-old single primary cell. It is because its radio just about demands a little less power per bit at the typical manhole payload size.
• No per-device recurring fees. This will amount to recurring cost savings once hardware rolls out and gateways are installed. Mid-six-figure savings over a 10-year run with a 5,000-manhole deployment in capex shift.
• City-owned network model. While over a period in which a municipality can use similar nodes and his or her citywide distributed network with respect to water level, traffic counting, or parking-bandwidth sharing, the decrease in per gateways of costs is shunted through sectors of assets.
• Wide gateway range in line of sight. In-store areas should boast approximations of 5-15 km; cities will fall to the range of 2-5 km. A gateway charge can privilege up a hundred or more manholes in the area of the east or behind bars of aghast factories.

Where LoRaWAN loses is:

• Gateway capital costs. Outdoor LoRaWAN gateways cost round $1,500 to $5,000 per equipment, power, backhaul, and mountings are extra; so for small-scale organizations, these would never be amounting to accept and operate.
• Payload and periods/frequency inactive limits. As per object constrains, the payloads only reach around 51 bytes for an uplink, that too at low data rates. EU ETSI EN 300 220 (100kHz chirp spread spectrum, 27dBm EIRP, 1.5% LBT duty cycle) restricts most sub-bands to under 1% transmission, which in turn translates to about 36 seconds of radio active transmission per hourly period for a device.
• Indoor penetration. High frequency bands used in the geography (meaning 902–928 or 868 MHz) are rather weak for coverage in deep urban environments compared to low bands of NB-IoT. The 433 MHz and 470 MHz bands used in some Asian markets, for instance, are better options, but again are not successful on a universal ground.

LoRaWAN Class A vs Class B vs Class C: Which Class for Manhole Alerts?

Battery-powered devices shunned Class A. A sleeping end node wakes up to cut loose a transmission and then planks open two tiny judgement windows, gradually acquiring more energy-efficient status, but still affords no downlink until it transmits again.

All Class B did was schedule the receive windows to coordinate with the head-end gateways. The ability to offer the download command makes up a thrilling thought-very useful for acknowledging any valid information or incorporating any configuration updates in the down channel without waiting for another backhaul on the uplink.

Class C keeps the receive window open all the time. It supports near-real-time downlink but for the price of power consumption. It cannot be used for power-manhole sensors with a targeted lifetime of about ten years.

For smart manhole covers, Class A takes event-uplinks (tilt, water levels, gas), the uplinks on those events occurring within a few seconds upon activation of the event. Early enough for almost any local alarming workflow.

NB-IoT vs LoRaWAN: Side-by-Side for Manhole Cover Deployments

The following table consolidates the engineering tradeoffs into the dimensions that matter for a manhole sensor specifically. Use it as a reference; we unpack each row in the framework below.

Factor	NB-IoT	LoRaWAN	Winner for Manhole Covers
Underground / metal-cover signal penetration	Excellent in licensed sub-GHz bands	Moderate; better at 433/470 MHz than 868/915	NB-IoT in dense urban; LoRaWAN if antenna is above grade
Battery life (4 reports/day + event alerts)	6–10 years	8–15 years	LoRaWAN
Data rate	Up to ~250 kbps	0.3–50 kbps	NB-IoT
Latency for tamper / overflow alert	Seconds	Seconds (Class A on uplink)	NB-IoT for downlink-heavy workflows
Security	3GPP 256-bit encryption + SIM auth	AES-128 (network and app layers)	NB-IoT
Network ownership	Carrier-operated	Self-deployed gateways or public TTN	LoRaWAN for city-owned networks
Recurring per-device cost	Carrier subscription per SIM	Effectively zero	LoRaWAN
Upfront infrastructure cost	None	Gateway capex (~1,500–1,500–5,000 each)	NB-IoT for small fleets; LoRaWAN for large
Regional band complexity	High (B1/B3/B5/B8/B20/B28)	Lower (regional sub-bands well-defined)	LoRaWAN for multi-region OEM products
Best-fit deployment	Dense urban, frequent telemetry	Campus, rural, or city-owned LPWAN	Context-dependent (see framework)

Ready to pressure-test these tradeoffs against a live tender? Contact our engineering team for a deployment-specific protocol review.

The 5-Question Decision Framework

When a city authority approached our engineering team in early 2026 about a 1,200-cover pilot, the conversation lasted 40 minutes and turned on five questions. Apply them in this order.

Question 1: Is the Deployment Urban or Rural?

Strong-quality indoor coverages for NB-IoT are held in favor of dense, urban 4G/LTE environments. The LoRaWAN is more advantageous for suburban, rural, or-campus deployments that stand in the direct view of the gateway. Mostly, hybrid is more competing, where spatial availability allows (check next section).

To the City: Can You or Do You Plan to Use LoRaWAN?

Reinforcing a LoRaWAN infrastructure for other devices by another public works department, water utility, or parking authority is almost always more cost-effective when manhole covers opt to share the gateway capex. If there is no infrastructure or any lines of instruction for LoRaWAN, NB-IoT cancel out the capex and also the inaugural yearly operations commitment.

Question 3: How Sensitive Are the Alerts?

An operation that will have operations reacting within minutes should be handled differently from the quarterly water-level survey. Some NB-IoT connected mode they can complete within seconds. LoRaWAN Class A can achieve the same objective on uplink, but no acknowledgment on the downlink surface until the next transmission. In most applications that involve municipalities, Class A is operational. On the other hand, NB-IoT proves beneficial for activities that require downlink acknowledgments within around 60 seconds.

Question 4: What Is the 10-Year TCO Budget Envelope?

Some rough calculations are done on a deployment of 1,000 nodes:

• NB-IoT: no gateway capex, but a cost of appx. $1.50-$4 per device per month for the carrier. Total cost here projected to be between, say, $180,000-$480,000 over 10 years.
• LoRaWAN: 4-8 gateways that cost $3,000 each therefore $12,000-$24,000 capex, plus some hosting of network server and backhaul for the gateways. One can anticipate $50,000-$110,000 for operations over 10 years.

Take into account that NB-IoT will often have a lower TCO when covered networks amount to less than 100, as capex on gateways does not get amortized. Nevertheless, capex that has already been amortized becomes an interest in LoRaWAN implementations of 1,000 nodes or more, with the exact point depending heavily on the price structure where carriers engage and on gateway densification.

Question 5: Does the Device Need to Roam Across Regions?

If OEM customers, in dual regions, bring their device suppliers and cover providers for multiple geographies, overheads of NB-IoT bands in regional contexts become manufacturing finance problems; regional sub-bands for LoRaWAN are much easier, with only a single hardware platform and regional profiles in firmware that show specific interests. This leads, and leads even more, OEM Black Ant customers who are sending their product into Europe, Asia, and the Americas from one SKU to configure it as needed to LoRaWAN with regional profiles through provisioning time.

When 4G Cat.1 or Hybrid Multi-Protocol Devices Make More Sense

The good faith has it all. This is evident when the terrible options were laid bare.

Imagine a scenario where a Chinese smart city integrator plans to deploy 8000 covers over a second-tier city by 2025; In this case, the integrator would need downlink command channels for remote firmware updates, verification of cover-displacement events by means of video, and seamless integration with the existing operator-grade 4G network. The integrator called for 4G Cat. 1 with a Bluetooth provisioning channel. The BOM was also more expensive than what might be expected on the NB-IoT or LoRaWAN side; however, the data rate-all the way to 10 Mbps downlink-supported the imaging payload, plus the network was already paid for as part of a broader contract with the city.

Black Ant’s HMC platform instalment comprises 4G Cat. 1 plus Bluetooth from today. For the emerging customer profile and the application pain points, we needed assurance of an image and video review, super quick firmware uploads, and performance. For permits needed to operate without those features, the same platform can have an NB-IoT or LoRaWAN modules inserted in place of the Cat. 1 module.

One dual-mode famous novelty in high-volume projects. This could mean an NB-IoT primary radio with the LoRaWAN falling back or vice versa under the supposition that a single carrier failure or gateway failure would spell blackout otherwise. The benefit outdoes the BOM cost, usually 10-25 percent real, typically higher in operational reliability terms than would compete favorably in a tender.

It makes sense to go either way depending mainly on the scale and criticality of a specific project combined with a budget, and then proceed along the five-question framework to select a primary protocol, complementing it with a redundant secondary-unit.

How Black Ant Engineers Manhole Covers for Both Protocols

Black Ant’s smart manhole cover product range is engineered around a modular radio architecture. The same IP68 enclosure, sensor stack (tilt, magnetic, water level, gas, temperature/humidity), and lithium battery pack accept different radio modules at the manufacturing stage:

• NB-IoT with B1/B3/B5/B8/B20/B28 band support, 3GPP 256-bit encryption, and SIM-or-eSIM authentication
• LoRaWAN Class A with regional sub-band firmware profiles for EU 868, US 915, AS 433/470, and AU 915
• 4G Cat.1 for image, firmware, and high-throughput payloads (Black Ant’s HMC H501 monitoring instrument ships in this configuration)
• Hybrid NB-IoT + LoRaWAN modules for redundancy-critical deployments

All the variants possess identical certification benchmarks—ISO 9001 for high-quality management, CE and RoHS for open entry to the European market and IP68 for sealing from shallow water conditions. The battery longevity targets are deemed realistic for a 4-uplink per day baseline cycle with event-triggered alerts, resulting in real-world numbers instead of open-world maximums.

The covers integrate naturally into a broader smart city stack. Telemetry routes through Black Ant’s IoT Data Collection Terminal for multi-protocol aggregation, with edge data acquisition computers handling local inference for time-sensitive workflows. For cities deploying environmental monitoring stations alongside manhole sensors, the same network and management platform serves both asset classes. For municipalities planning to visualize this data spatially across districts and underground assets, it is also worth exploring GIS Integration for Smart Manhole Monitoring: A Municipal Engineer’s Field-to-Map Guide.

Under the standard ODM (Original Design Manufacturer) scope, OEM partners can perform regional band conversions, firmware tunings, and private labeling. We do not wish to have the protocol determined at random. Instead, we will make the device configurable so that you can choose yourself. If supplier selection is part of your next procurement step, you may also find Smart Manhole Cover OEM Manufacturer China: How to Choose the Right Partner useful as a practical reference.

Conclusion: There Is No Universal Winner, Only the Right Protocol

Choosing between NB-IoT and LoRaWAN for a smart manhole cover is not merely a competitive question. It is actually an issue of fitness between parameters like deployment density, network ownership nuances, alert latency, 10-year TCO, and regional complexity that push the decision to one side or the other.

The five takeaways:

1. NB-IoT takes the gold for dense urban deployments with strong cellular coverage, frequently checking in on the telemetry and being tightly limited in regards to latency.
2. LoRaWAN takes the gold for city-owned networks, large fleet with over a thousand devices, and deployments where battery life is crucial.
3. 4G Cat. 1 is the winner when the volume of data transmission (image/video or firmware) exceeds the LPWAN payload limitations.
4. Hybrid dual-mode is the winner when there is no tolerance for downtime in the event of carrier switching or gateway failure.
5. Therefore, the correct answer lies within this decision-making framework, not amid marketing rhetoric.

If your team is preparing a smart city tender or a pilot program, the next step is to apply the framework to your actual deployment context. Request a Black Ant smart manhole cover spec sheet or reach out to our engineering team for a deployment-specific protocol consultation. We will help you specify the right radio, the right battery, and the right enclosure for the streets you actually have, not the streets in a generic LPWAN comparison.

Cities that make the distinction correctly will save drivers, check flooding and spray, and save on routine city maintenance costs during the next decade. Those cities making a mistake will put thousands of works of art in there. So the standard made above is the distinction.