Definition
Narrowband (Narrowband) refers to IoT communication technology that uses narrow bandwidth (such as 180 kHz single carrier), characterized by low power consumption, long distance, and massive connectivity. Narrowband IoT (NB-IoT) is a 3GPP standardized LPWAN technology, operating in licensed spectrum, supporting deep coverage, massive connections, low-cost modules, and is suitable for smart metering, remote meter reading, EV charging station status reporting, logistics trackers, and other low-data, low-power scenarios. Compared with broadband (4G/5G), narrowband has a lower data rate per device but supports more connections, wider coverage, and lower cost. In cross-border scenarios, narrowband devices need to support multiple frequency bands in different countries, and single card multi-country can ensure continuous connectivity during cross-border deployment.
Technical Features and Architecture
The narrowband technology architecture includes: Physical layer — single carrier 180 kHz, subcarrier spacing 15 kHz, supporting stand-alone deployment, guard-band deployment, and in-band deployment; Coverage enhancement — retransmission, increased power spectral density, supporting deep coverage such as basements and manholes; Low power — PSM, eDRX, and other power-saving modes, battery life can reach several years; Massive connectivity — a single cell can support tens of thousands of connections. Combined with multi-mode modules, narrowband can serve as a primary link or backup; combined with data compression, it can further reduce the data volume transmitted via narrowband. In cross-border scenarios, narrowband needs to adapt to the NB-IoT frequency bands of various countries (such as B8, B20, B28, etc.).
Application in IoT and cross-border scenarios
Narrowband is widely used in: smart meters—remote meter reading of water meters, gas meters, and electricity meters, metering data reporting; EV charging stations—EV charging stations device status and metering value low-frequency reporting, suitable for low-cost deployment; logistics tracking—logistics trackers positioning and status low-frequency reporting; energy monitoring—periodic data reporting of energy monitoring devices. Cross-border smart meters, cross-border EV charging stations, and cross-border logistics tracking can all use narrowband to achieve low-cost, wide-coverage connectivity, one card for multiple countries to ensure cross-border network access.
SimtoLink supports narrowband IoT devices, covering over 200 countries and regions, helping cross-border remote meter reading, EV charging stations and other scenario connectivity.
What kind of data a narrow channel can send reliably
Narrowband here means a cellular IoT bearer with a very narrow carrier, a low rate per terminal, and an easier path to deep coverage and power saving. NB-IoT is the common standardized form. It suits register readings, switch state, a small number of alarms, and sparse positioning. The payload of one exchange should be small, the interval should be sparse, and the terminal should spend most of its time in a power-saving mode. Coverage enhancement is bought with repeated transmissions. Being able to connect from a basement or from inside a box does not mean the terminal can connect often. During power-saving mode, downlink from the network waits until the terminal next wakes. The platform cannot treat it as a wideband module that can be called at any time.
Before choosing narrowband, confirm the application's packet size, how many times a day it sends, the downlink delay that can be accepted, and whether the destination country has opened the corresponding band. If any of the SIM subscription, the module bands, and the local radio network is missing, the terminal stays in network search. A firmware delta larger than the link is comfortable with should be done locally or over wideband. Cross-border roaming is not necessarily open for narrowband and wideband at the same time. A wideband test result does not imply that narrowband is available. After deployment, watch power on the real meter-reading cycle, rather than substituting the lab current of a continuous registration.
Stuffing wideband traffic into a narrowband bearer unchanged
The most common error is a prototype tuned on wideband for video or a remote desktop, then a production change that only swaps in a narrowband module and assumes the protocol need not change. On narrowband those applications occupy the radio resource, slow the small packets of neighboring terminals, and exhaust their own battery quickly. Another error is a very long power-saving cycle combined with a requirement for alarms within a minute. An alarm can leave only in the wake window. The timeliness is already gone, while the screen still says real-time monitoring.
If repeated radio transmissions are mistaken for packet loss and the application resends without pause, the result is an uplink storm. The application layer should recognize that the radio layer is already retransmitting, and should not add business retries with no gap. After a move to another country, if narrowband is absent there and the policy still forbids fallback to wideband, the terminal stays offline permanently. Whether fallback is allowed should be written in the networking policy. On a weak network in the field, reduce what is reported first, rather than raising the number of transmissions past what the battery can sustain.
A pilot should run the battery budget on the real meter-reading cycle in the destination country. Do not substitute the current drawn during continuous attach. If a downlink command must arrive inside the power-saving cycle, write that cycle into the application design, rather than resending continuously from the platform. When the radio layer is already repeating, the application layer should space out its retries. Where there is no narrowband coverage, fall back by the agreed policy or mark the service unavailable. Do not search the network without a limit.