Smart Metering, Asset Tracking, and Smart City Deployments
In 60 Seconds
NB-IoT excels in applications requiring deep indoor coverage and 10+ year battery life, with primary use cases in smart metering (water, gas, electricity), asset tracking (logistics, supply chain), and smart city deployments (parking, waste management) where devices send small, infrequent data updates over licensed cellular spectrum.
Key Concepts
Smart Water Metering: Primary NB-IoT use case; municipality deploys NB-IoT modules in water meters in basements and underground vaults; daily reading transmission; 10-year battery life targets
Smart Grid AMI (Advanced Metering Infrastructure): NB-IoT-connected electricity meters replacing manual reading; supports remote meter reading, outage detection, and demand response
Environmental Monitoring: NB-IoT sensors for air quality (PM2.5, NO2, O3), soil moisture, flood level, and weather; typically 15–60 minute reporting intervals; solar or primary cell powered
Smart Agriculture: NB-IoT soil sensors, irrigation valves, and weather stations across farms; covers areas where cellular coverage exists but other wireless does not; LoRaWAN alternative for off-grid
Waste Management: Smart bin sensors detecting fill level via ultrasonic distance; NB-IoT reports level daily; city optimizes collection routes saving 20–40% in collection costs
Asset Tracking (Non-Powered): NB-IoT tracker on shipping containers, tools, or industrial equipment; reports location (GPS/OTDOA) on tamper, tilt, or scheduled interval; 1–5 year battery life
Structural Health Monitoring: NB-IoT accelerometers and strain gauges on bridges, dams, and buildings; detects micro-movements and transmits anomalies; 10–20 year deployment lifetime
Smart Parking: NB-IoT magnetic or ultrasonic sensors detect vehicle presence in parking spots; transmit state changes; reduces urban parking search time by 30–50%
Design NB-IoT solutions: Justify the selection of NB-IoT for smart metering, asset tracking, and environmental monitoring based on application requirements
Calculate power budgets: Derive battery life estimates from PSM sleep current, TX duration, CE repetitions, and real-world derating factors
Analyze link budgets: Compute received signal strength and link margin for underground and deep-indoor deployment scenarios
Evaluate deployment economics: Contrast NB-IoT total cost of ownership against LoRaWAN, Sigfox, and LTE-M for a given fleet size and data profile
For Beginners: NB-IoT Applications
NB-IoT is used for smart meters that report utility usage, parking sensors that detect occupied spots, agricultural sensors that monitor soil moisture, and building systems that track temperature and humidity. This chapter showcases real NB-IoT deployments to illustrate what this cellular IoT technology does best.
Sensor Squad: NB-IoT in the Real World!
“I am an NB-IoT smart water meter!” Sammy the Sensor said proudly. “I sit in a basement three floors underground and send one tiny message per day telling the water company how much water was used. Thanks to NB-IoT’s amazing coverage, my signal punches right through all that concrete. No human needs to visit me for years!”
“Smart parking is another great use,” Lila the LED added. “Imagine sensors buried in parking spots that detect when a car is parked. They send a quick signal – just a few bytes – saying ‘occupied’ or ‘empty.’ An app on your phone can then show you exactly where to find an open spot. NB-IoT is perfect because each sensor sends tiny messages and needs to last years on a battery.”
Max the Microcontroller explained, “Agriculture is where NB-IoT really shines. Farmers spread hundreds of sensors across their fields to measure soil moisture, temperature, and nutrient levels. The farm might be kilometers wide with no Wi-Fi anywhere, but NB-IoT reaches cell towers kilometers away. I collect the readings and send them once or twice a day.”
“The key to all these applications,” Bella the Battery said, “is that they share three things: small data, infrequent updates, and the need for long battery life. A parking sensor sends fifty bytes once an hour. A water meter sends one hundred bytes once a day. With NB-IoT’s Power Saving Mode, I can power these devices for ten to fifteen years. That is why NB-IoT is the champion of low-power IoT!”
8.2 Application Examples
8.2.1 Smart Metering
Use case: Smart Water Meters
Smart water meter PSM cycle
Figure 8.1: NB-IoT Smart Water Meter PSM Sleep Cycle with Daily Reading
8.3 Worked Example: Battery Life Calculation for Smart Meter
Scenario: A utility company is deploying NB-IoT smart water meters in residential basements. Each meter needs to send a 50-byte reading once per day and operate for 10+ years on a single 6000 mAh battery.
Given:
Battery capacity: 6000 mAh (lithium thionyl chloride, 3.6V)
TX energy = 220 mA x 1.5 s = 330 mAs = 0.0917 mAh
RX energy = 40 mA x 0.5 s = 20 mAs = 0.0056 mAh
Active total per transmission = 0.0973 mAh
Step 2: Calculate daily sleep energy consumption
Sleep duration = 24 hours - 2 seconds = 23.9994 hours
Sleep energy = 3 uA x 23.9994 hours = 0.072 mAh
Step 3: Calculate total daily energy and theoretical battery life
Daily consumption = 0.0973 mAh + 0.072 mAh = 0.1693 mAh
Theoretical life = 6000 mAh / 0.1693 mAh/day = 35,440 days = 97 years
Step 4: Apply real-world derating factors
Battery self-discharge: 1%/year over 15 years = 15% loss
Temperature derating (basement, 10-20C): 5% capacity reduction
End-of-life threshold (3.0V cutoff): 10% unusable capacity
Effective capacity = 6000 x 0.85 x 0.95 x 0.90 = 4,373 mAh
Practical life = 4,373 mAh / 0.1693 mAh/day = 25,830 days = 70.7 years
Step 5: Account for coverage enhancement repetitions
Basement installation may require CE Mode B (up to 2048 repetitions)
Worst-case TX duration: 1.5s x 4 (repetitions) = 6 seconds
Revised TX energy = 220 mA x 6 s = 0.367 mAh
Revised daily = 0.367 + 0.0056 + 0.072 = 0.445 mAh
Practical life with CE = 4,373 / 0.445 = 9,826 days = 26.9 years
Result: Even with coverage enhancement for deep basement penetration, the meter achieves 26+ year theoretical battery life, well exceeding the 10-year requirement.
Key insight: PSM (Power Saving Mode) is the critical enabler - without it, sleep current of 15-50 mA would reduce battery life to weeks. The 3 uA PSM sleep current represents a 5000x reduction in idle power consumption.
Putting Numbers to It
Let’s quantify how PSM transforms NB-IoT battery life. Without PSM, the module stays in idle mode (eDRX) at 15 mA. With PSM, it enters deep sleep at 3 µA. The power savings factor is:
With PSM: Active: \(35.5 \text{ mAh/year}\) Sleep: \(0.003 \text{ mA} \times 24 \text{ h} \times 365 = 26.3 \text{ mAh/year}\)Total: 61.8 mAh/year → 6000 mAh battery lasts 97 years (theoretical)
The PSM sleep current (3 µA) is so low that it contributes only 42% of total energy despite being active 99.998% of the time. The 2-second daily transmission consumes 58% of energy. This explains why NB-IoT can achieve 10+ year battery life while other cellular technologies manage only months.
8.5 Worked Example: Link Budget for Underground Parking Sensor
Scenario: A smart city wants to deploy occupancy sensors in an underground parking garage (2 levels below ground). Will NB-IoT provide reliable coverage?
Step 2: Add building and underground penetration losses
Ground floor penetration: 15 dB
Underground Level 1: 12 dB
Underground Level 2: 12 dB
Total penetration loss = 15 + 12 + 12 = 39 dB
Step 3: Calculate total path loss
Total path loss = FSPL + penetration + shadow fading
Total path loss = 94.56 + 39 + 8 (urban shadow fading)
Total path loss = 141.56 dB
Step 4: Determine received signal strength
RSSI = EIRP - Path Loss + Antenna Gain
RSSI = 43 dBm - 141.56 dB + 0 dBi (sensor antenna)
RSSI = -98.56 dBm
Step 5: Compare to sensitivity and calculate margin
NB-IoT sensitivity (CE Mode B): -141 dBm
Link margin = RSSI - Sensitivity = -98.56 - (-141) = 42.44 dB
Required margin: 10 dB
Available margin: 42.44 dB > 10 dB (Sufficient)
Result: NB-IoT provides 42 dB of link margin for the underground parking sensor, well above the 10 dB requirement.
Key insight: NB-IoT’s 164 dB Maximum Coupling Loss (MCL) specification - achieved through repetition coding and narrow bandwidth - provides 20 dB more coverage than standard LTE.
8.6 Worked Example: Coverage Enhancement Repetitions
Scenario: A building management system deploys environmental sensors inside elevator shafts and mechanical rooms. These locations have severe RF attenuation. How many NB-IoT repetitions are required?
Given:
Base station EIRP: 46 dBm (typical macro cell)
Frequency: 700 MHz (Band 28)
Distance to base station: 800 meters
Building penetration losses:
Exterior wall: 15 dB
Interior concrete walls (2): 10 dB each
Elevator shaft steel: 25 dB
NB-IoT module sensitivity (no repetitions): -124 dBm
Target reliability: 99.9%
Required link margin: 8 dB
Step 1: Calculate path loss to elevator shaft
Free-space path loss (800m at 700 MHz):
FSPL = 20 x log10(0.8) + 20 x log10(700) + 32.45
FSPL = -1.94 + 56.9 + 32.45 = 87.4 dB
Building penetration:
- Exterior wall: 15 dB
- Interior walls (2x10): 20 dB
- Elevator shaft steel: 25 dB
- Total penetration: 60 dB
Total path loss = 87.4 + 60 = 147.4 dB
Step 2: Calculate repetitions needed
NB-IoT repetition gain:
Repetitions
Processing Gain
Effective Sensitivity
1 (none)
0 dB
-124 dBm
2
3 dB
-127 dBm
4
6 dB
-130 dBm
8
9 dB
-133 dBm
16
12 dB
-136 dBm
32
15 dB
-139 dBm
64
18 dB
-142 dBm
128
21 dB
-145 dBm
256
24 dB
-148 dBm
Step 3: Analyze worst-case scenario
Add worst-case factors:
- Body absorption (technician nearby): 3 dB
- Electrical interference: 5 dB
- Shadow fading (99.9% reliability): 10 dB
Total additional margin needed: 18 dB
For extreme environments, maximum 2048 repetitions -> +33 dB gain
Result: For extreme deep indoor deployments, NB-IoT Coverage Enhancement Mode B with maximum repetitions provides connectivity but at cost: 20-minute transmission time and reduced battery life.
Key Insight: NB-IoT’s 164 dB MCL is achieved through repetition coding, but each 3 dB of coverage extension doubles transmission time. For extreme environments (>150 dB path loss), consider in-building DAS or femtocell deployment.
8.7 Real-World Case Study: Municipal Water Utility
The Challenge: A mid-sized city wants to modernize water metering to detect leaks, eliminate manual meter reading, and enable time-of-use billing.
The NB-IoT Solution:
Hardware per meter:
NB-IoT module: $8
Battery (AA lithium): $3
Installation: $15
Total per meter: $26
Data transmission pattern:
Daily consumption report: 200 bytes/day
Leak alert (if triggered): 150 bytes
Monthly billing data: 500 bytes
Average: 6.4 KB/month per meter
Annual operational costs (50,000 meters):
Cost Component
Per Meter
50,000 Meters
Cellular data plan
$2.00/year
$100,000
Network maintenance
$0.50/year
$25,000
Battery replacement (year 12)
$0.25/year amortized
$12,500
Total Annual
$2.75
$137,500
Comparison to manual reading:
Method
Annual Cost
Notes
Manual meter reading
$600,000
$1/read x 12 months x 50,000
NB-IoT automated
$137,500
Cellular + maintenance
Annual Savings
$462,500
77% reduction
Results after 3 years:
Leak detection: Identified 847 leaks, saving 42 million gallons/year
Billing accuracy: Reduced disputed bills by 94%
Operational savings: $1.4 million over 3 years
No cellular outages: 99.7% uptime (carrier SLA: 99.5%)
Zero battery failures (ongoing monitoring confirms 12+ year projection)
Key insight: The payback period was 4.2 months. After that, the city saves $462k annually compared to manual reading.
8.8 Knowledge Check
Question: Technology Selection for Asset Tracking
You’re designing a nationwide asset tracking system for shipping containers that need to report location and temperature every 4 hours. Your containers travel across highways, rural areas, and inside cities. Battery replacement is expensive (containers are scattered globally), so you need 5-10 year battery life.
2. Battery Life Calculation: 5-10 Years is Achievable
Container reporting cycle (every 4 hours):
1. Wake up from PSM (deep sleep)
2. Get GPS fix: ~30 seconds (100mA)
3. Read temperature sensor: 50ms (5mA)
4. Send NB-IoT uplink (100 bytes): ~2 seconds (200mA)
5. Enter PSM (deep sleep): 3uA
Daily consumption:
6 reports/day x 0.984 mAh = 5.9 mAh/day
Battery life with 20,000 mAh battery:
20,000 mAh / 5.9 mAh/day = 3,389 days = 9.3 years
3. Roaming and Cell Reselection
NB-IoT supports cell reselection in idle mode – after PSM wake-up, the device connects to the strongest available cell
Carrier roaming agreements enable global tracking across borders
Containers report every 4 hours, so brief disconnections during cell transitions are acceptable (unlike real-time fleet tracking, which would require LTE-M handover)
Coverage: Operates in 130+ countries with roaming agreements
ROI: Reduced cargo loss by 30% through real-time monitoring
Interactive Quiz: Match NB-IoT Application to Key Advantage
Interactive Quiz: Order the NB-IoT Battery Life Calculation
8.9 Technology Selection: When NOT to Use NB-IoT
NB-IoT excels in specific scenarios but is the wrong choice for others. This decision table helps avoid common selection mistakes:
Requirement
NB-IoT Suitability
Better Alternative
Why
Streaming video/audio
Not suitable
Wi-Fi, 4G LTE
26 kbps (Cat-NB1) to 159 kbps (Cat-NB2) max, high latency
Sub-second control response
Not suitable
LTE-M, Wi-Fi
1.6-10s latency with PSM wake-up
Moving vehicles >30 km/h
Marginal
LTE-M
No handover support in most deployments
Firmware updates >50 KB
Slow but feasible
LTE-M
20+ minute OTA at CE Mode B
Private/unlicensed spectrum
Not available
LoRaWAN, Wi-Fi
NB-IoT requires licensed carrier spectrum
Zero recurring cost
Not possible
LoRaWAN, Zigbee
Carrier subscription required per device
<$5 module cost
Approaching
LoRa, BLE
NB-IoT modules $6-8 (2025), LoRa $3-4
The “NB-IoT or LoRaWAN?” question comes up in nearly every LPWAN project. The deciding factors are:
Do you need guaranteed delivery for billing? NB-IoT (carrier SLA, licensed spectrum)
Do you own the coverage area? LoRaWAN (deploy your own gateways, zero recurring fees)
Are devices in deep basements? NB-IoT (164 dB MCL vs LoRaWAN 157 dB)
Is the deployment in a rural area without cellular? LoRaWAN (deploy gateways where needed)
Scale above 10,000 devices? LoRaWAN TCO advantage above ~9,000 units (see Sigfox comparison in related chapter)
🏷️ Label the Diagram
💻 Code Challenge
8.10 Summary
Smart metering is ideal for NB-IoT: daily readings, basement coverage, 10+ year battery life, no gateway infrastructure
Asset tracking benefits from NB-IoT’s global roaming agreements and dual PSM/eDRX power modes for stationary-vs-transit state adaptation
Smart city applications (parking, lighting) leverage existing cellular coverage and carrier-grade reliability
Battery life calculations must account for PSM sleep current, TX duration, CE repetitions, and battery derating
Link budget analysis confirms NB-IoT’s +20 dB coverage advantage for deep indoor deployments
8.11 Concept Relationships
NB-IoT applications build on: NB-IoT Architecture Control Plane optimization for smart metering, Cellular IoT Overview network architecture (eNodeB, MME, SCEF), and Power Optimization PSM/eDRX timers. Link budget calculations connect to Coverage Enhancement repetition mechanisms achieving 164 dB MCL for basement penetration.
1. Selecting NB-IoT for Applications Requiring <1 Second Response Time
NB-IoT’s PSM sleep cycles and eDRX windows mean devices may not respond to downlink commands for minutes to hours. For emergency alert systems, remote valve control, or interactive commands, NB-IoT’s latency profile is unsuitable. Applications needing sub-10-second response times should use LTE-M (with short eDRX or always-on connection) or use NB-IoT for one-way telemetry only, with a separate command channel via a different technology.
2. Deploying NB-IoT Applications Without Offline Data Buffering
NB-IoT coverage in deep-indoor or underground locations is intermittent — a meter may lose connectivity for hours or days during maintenance windows or coverage outages. Applications that discard sensor readings during connectivity loss create data gaps in time series. Implement local data buffering in device flash storage (minimum 30-day capacity at normal reporting rate) and batch upload buffered readings upon connectivity restoration with original timestamps.
3. Using IPv6 Without Verifying Operator Support
NB-IoT natively supports IPv6, but many operator NB-IoT networks still route traffic over IPv4 or use NAT. Firmware designed for IPv6-only communication fails on IPv4-only networks. Support both IPv4 and IPv6 in firmware, or use application-layer addressing (e.g., device ID in payload, DTLS-PSK identity) independent of IP version. Test with the actual operator network to verify the IP version and NAT configuration before finalizing the communication stack.
4. Not Accounting for NB-IoT Transmission Retransmissions in Power Budget
In poor coverage locations (basements, thick-wall environments), NB-IoT uses CE Mode B with up to 2048 repetitions per block, increasing single-transmission energy by 10–100×. A power budget calculated for nominal CE Mode A (few repetitions) will underestimate actual energy consumption by 5–50× in challenging locations. Use coverage probability distributions from site surveys to model energy consumption across the deployment area, not just the average-coverage case.
