Insights
GPS tracker SIM cards: LTE-M, NB-IoT and mobility for vehicle trackers
Moving trackers depend on mobility support
GSMA distinguishes idle-mode mobility, where the device chooses a new cell before it next connects, from connected-mode mobility, where the network hands an active connection to the next cell. A tracker that reports every few seconds on a highway spends much of its time in the second situation.
GSMA describes LTE-M as supporting mobility and roaming and recommends connected-mode mobility for all LTE-M data traffic. For NB-IoT, its deployment guide lists connected-mode mobility among features that are useful but not yet widely adopted. Ask the device maker which technology and features the tracker uses, and verify the behaviour when a cell change happens during a transmission.
Power saving changes when you can reach the device
Power Saving Mode lets a device enter deep sleep, and GSMA notes that it is unreachable while asleep. Some networks buffer packets until the device wakes, but each operator sets how many and how large those packets can be, and the periodic tracking area update timer bounds how long the device may stay idle or asleep.
Decide how quickly a remote configuration change or an on-demand position request must reach a parked tracker, then configure sleep timers to match and test the delay on the intended networks. Battery-powered asset trackers and vehicle-powered trackers usually justify different settings.
Cross-border routes need per-country confirmation
GSMA explains that LTE-M and NB-IoT roaming relies on commercial roaming agreements between operators, and that bands, IP version, PSM, eDRX and buffering can differ between visited networks. A tracker that works at the depot may therefore behave differently after a border.
List every country on the route and where vehicles are based most of the time. Ask the supplier which radio technologies and networks the offered SIM can use in each country, and whether long-term use away from the home network is allowed there. Quanqiu IoT confirms these points per project; catalog presence is not a coverage statement.
Size the data budget from the reporting pattern
Reporting frequency drives usage. The figures below are hypothetical arithmetic that assumes 150 bytes per reporting cycle, including routine protocol exchanges, and a 30-day month with 220 driving hours; replace the assumption with a measured value from your tracker. Video uploads from dash cameras need a separate budget.
Use the data usage calculator to repeat the arithmetic with your own payload and intervals, and compare the result with the allowance and validity confirmed in a written quote.
| Reporting pattern | Reports per month | Estimated data |
|---|---|---|
| Moving, every 30 s, 10 h a day, 22 days | 26,400 | 3.96 MB |
| Same, plus a parked heartbeat every 30 min | 27,400 | 4.11 MB |
| Moving, every 10 s, plus the parked heartbeat | 80,200 | 12.03 MB |
Pilot on a real route before volume orders
A bench test cannot show handover, border crossing or wake-up behaviour. Run a short pilot with the production tracker, firmware and SIM on the routes the fleet actually drives.
- Record the tracker model, modem, radio technology and firmware version.
- Drive a route with frequent cell changes and check for gaps in position reports.
- Cross at least one border on the planned route, if the fleet does, and confirm reconnection.
- Park the vehicle, send a configuration change or position request, and measure the delay.
- Compare the device data counter with the supplier usage record for the same period.
Frequently asked questions
Is NB-IoT suitable for a moving vehicle tracker?
Test it carefully. The GSMA deployment guide lists NB-IoT connected-mode mobility as useful but not yet widely adopted, while GSMA describes LTE-M as supporting mobility. Verify the actual device on a real route.
Why does my parked tracker not respond immediately?
It may be in Power Saving Mode, during which GSMA notes the device is unreachable. Buffering and timers depend on the device configuration and each operator, so define and test the acceptable delay.
How much data does a GPS tracker use per month?
It depends on the bytes per report and the reporting interval. In the hypothetical example above, 150 bytes every 30 seconds for 220 driving hours is 3.96 MB; measure your own tracker and use the calculator.
Official references
Related reading
More insights
Send your tracker model, route countries, reporting interval and fleet size to Quanqiu IoT to confirm the connectivity options for each country.
Discuss your project