E-Scooter and E-Bike
Fleet Telematics
A full-stack telematics solution for shared e-scooter and e-bike fleets, spanning the IoT controller, smart lock firmware, and cloud platform. Geofenced parking enforcement, battery state of charge, and rebalancing logic come together to keep a micromobility operation running.
THE CHALLENGEMicromobility Lives and Dies on the IoT Controller
A shared scooter fleet is only as good as the box bolted to the stem. If the smart lock misfires, riders cannot start a trip. If GPS drifts, vehicles get parked in no-ride zones and cities pull your permit. If battery state of charge is wrong, your rebalancing crew drives to dead scooters. Most operators buy hardware from one vendor and an app from another, then spend their margin reconciling the two. The IoT controller, the lock mechanism firmware, the connectivity, and the rider app are designed as one system so the unlock, the location, and the battery reading all agree.
Part of the Telematics and GPS Tracking stack, and commonly built alongside Two-Wheeler and Bike Tracking.
WHAT'S INCLUDED
The Full Micromobility Stack
IoT Controller and Smart Lock
The on-vehicle controller is built around an STM32 or Nuvoton MCU driving the lock actuator, the QR scan unlock, and the motor controller interface. Smart lock firmware handles unlock authentication, tamper detection, and a fail-safe that keeps a paid rider mobile even if the network drops mid-trip.
GNSS and Cellular Connectivity
A Quectel L76 or u-blox GNSS receiver with dead-reckoning holds position in urban canyons, paired with a Quectel BG95 or BC660 module on Cat-M1 and NB-IoT for low-power, low-cost connectivity. NavIC and IRNSS support is available where regional accuracy matters.
Geofenced Parking and No-Ride Zones
On-device and server-side geofencing covers slow zones, no-ride zones, and designated parking hubs. The controller can throttle or cut motor power on no-ride zone entry and refuse to end a trip outside an approved parking polygon, with the rules pushed over the air per city.
Battery and State of Charge Telemetry
The battery management system is read over UART or CAN to report state of charge, cell voltages, temperature, and charge cycles. Accurate SoC means your rebalancing crew swaps the right batteries and never drives to a scooter that is already dead.
Rebalancing and Operations Dashboard
The operator dashboard clusters low-battery and stranded vehicles, generates swap and pickup routes, and tracks crew tasks. Heatmaps show demand by hour so you stage vehicles where the next trips start.
Rider App and Trip Engine
A white-label rider app provides QR scan, BLE unlock fallback, live trip metering, in-app parking guidance, and payment. The trip engine reconciles GPS, lock state, and battery draw into a clean ride record and fare.
THE RIDE, AS THE RIDER FEELS IT
Scan, Ride, Park, Done
The rider never thinks about CoAP frames or geofence polygons. They scan, the lock pops, the motor wakes, and they ride. Every one of those moments is engineered to work the first time, every time, across thousands of vehicles in a city.
Unlock in Under Two Seconds
The QR code resolves to a vehicle ID, the server validates the rider and pushes an unlock command over MQTT, with a BLE direct unlock fallback when the cell link is weak. The lock fires and the trip starts before the rider lowers their phone.
Guided Riding
As the rider approaches a slow zone the app warns them and the controller eases the speed cap. Enter a no-ride zone and the motor cuts cleanly without throwing the rider, then resumes on exit.
Parking That Sticks
To end the trip the rider must be inside an approved parking polygon. The app shows the nearest hub, and a photo-parking check confirms the scooter is upright and clear of the footpath before billing stops.
HOW IT WORKS
From Controller to Cloud
On-Vehicle Firmware
FreeRTOS on the controller MCU sequences lock, GNSS, BMS polling, and the modem. A local store-and-forward buffer holds trip and telemetry data through dead zones and flushes on reconnect, so no ride is ever lost.
Connectivity and Protocol
Devices speak MQTT over TLS for commands and telemetry, with CoAP available for the most constrained NB-IoT scenarios. Over-the-air firmware and geofence updates roll out in staged waves with rollback on failure.
Cloud Platform
A time-series ingestion layer absorbs GPS and battery pings, the trip engine builds ride records, and the operations and rider services run on the same data. City geofence rules and pricing are managed centrally and pushed per fleet.
DURABILITY AND COMPLIANCE
Built for the Street
Ingress and Vibration
The controller and lock enclosure are designed to IP67 so rain, puddles, and pressure washing do not kill the electronics. Validation covers the vibration and shock a scooter takes on kerbs and cobbles every day.
City Permit Reporting
Cities increasingly require MDS and GBFS feeds for parking compliance, trip data, and fleet caps. The platform exposes those feeds so your permit team has the reporting regulators ask for.
Data and Payment Security
Telemetry and commands run over TLS, payment flows through PCI-compliant processors, and rider data handling follows GDPR and local privacy rules. Lock commands are signed so a vehicle cannot be unlocked by a spoofed message.
FAQ
Common Questions
Do you build the smart lock hardware or just the software?
Both are in scope. The IoT controller PCB and the smart lock firmware are designed around an STM32 or Nuvoton MCU, with the cloud platform and rider app built on top. Designing both ends together is why the unlock, the GPS fix, and the battery reading stay consistent.
How do you stop riders parking in no-ride zones?
Geofencing is enforced on two layers. The controller can throttle or cut motor power on no-ride zone entry, and the rider app refuses to end a trip outside an approved parking polygon. City rules are pushed over the air so each market runs its own zones.
How accurate is the battery state of charge reading?
The battery management system is read directly over UART or CAN rather than estimating from voltage alone, so true state of charge, cell health, and temperature are reported. That accuracy is what makes rebalancing efficient instead of sending crews to dead vehicles.
What connectivity do the scooters use?
The typical setup is Cat-M1 and NB-IoT through a Quectel BG95 or BC660 module for low power draw and low data cost, with MQTT over TLS for telemetry and commands. BLE provides a direct unlock fallback when the cellular link is weak.
Can you support your existing vehicle hardware?
In many cases yes. If your scooters use a standard controller and BMS interface, the cloud platform and rider app can be built against them. Where the existing controller is closed or unreliable, a dedicated IoT controller is the better path for full control of lock and motor behavior.
Do you provide the city reporting feeds?
Yes. The platform can publish GBFS and MDS feeds for trip data, parking compliance, and fleet status, which is what most city permits now require to operate a shared micromobility fleet.
Ready to Launch Your Micromobility Fleet?
Share your vehicle type, target cities, and fleet size to get a tailored plan for the controller, the lock, the connectivity, and the platform that puts the fleet on the street.
Schedule a Free Consultation