1. Why batch OTA
Batch OTA is for large firmware upgrades. One job can only cover so many devices. A fleet of hundreds of thousands or millions has to move in batches and in stages, or every device pulling at once will congest the network or fail together. On the SimtoLink Device Management Platform you pick targets by device group, tag, and region, then set a batch policy and an upgrade window. A task queue and progress tracking keep a large upgrade paced and visible.
The platform has already run batch OTA for customer fleets at the scale of hundreds of thousands and millions of devices. Jobs can run for a long time, and you can pause, resume, or stop them at any point.
2. What you control
Gray release (gray release)
Upgrade 5% of devices first and watch the success rate and alerts. If that slice stays healthy, open the job to 20%, 50%, and then 100%. Each batch records success, failure, and timeout counts. Failed devices can be retried or left out, and you can export the upgrade report.
Batch policy
Set how many devices are in a batch (for example, 1,000) and the gap between batches (for example, 30 minutes). Filter targets by device group, tag, and region when different parts of the fleet need different treatment.
Upgrade window and version filter
A maintenance window (for example, 2:00–5:00 a.m. only) holds every other device in the queue. Version filtering pushes the image only to devices already on the versions you named, so an incompatible build is not upgraded by mistake.
3. Upgrade path
4. Which batch policy fits
Each policy fits a different job:
| Policy | Typical setup | Use it when |
|---|---|---|
| Fixed batches | 1,000 devices per batch, 30 minutes apart | A routine large upgrade, and you need to cap the network peak |
| Gray release | 5% → 20% → 50% → 100% | A new version needs a staged check before the risk spreads |
| Maintenance window | Run from 2:00–5:00 a.m. | The quiet hours, so the upgrade does not hit live operations |
| Version filter | Upgrade only v1.x devices | You want a directed upgrade and need to skip incompatible builds |
5. Where teams use it
- Smart meters. Firmware updates and bulk parameter changes run by region and operator, so a single wave does not interrupt meter reading.
- In-vehicle terminals. The upgrade window follows when the vehicle is online, so the job runs while the vehicle is idle and still meets automotive-grade requirements.
- Industrial gateways. Lines and workshops upgrade in batches, inside a maintenance window, so production is not the thing that stops.
6. What the rollout gives you
Batch OTA on the SimtoLink Device Management Platform is how a fleet gets a large, orderly upgrade. Gray release checks a small batch before the rest of the fleet. Batch policy sets the pace so the network does not clog. Task control lets you pause, resume, or stop when something looks wrong. Progress you can see counts success, failure, and timeout as they happen, and you can export a report or retry the failures.
The platform includes an operating guide and practices for gray-release design and rollback plans. Contact SimtoLink if you want a large-upgrade plan reviewed, or a rehearsal before the production job.
7. Before you run it
Rehearse on a small set in a test environment before a large batch OTA, and confirm firmware compatibility and the rollback path. Task cloning copies a test job’s settings into production. Start gray release at 5%, watch for 24 hours, and widen the batch only if that window stays clean. Keep upgrade windows off peak hours. For smart meters, line the window up with the meter-reading cycle. For in-vehicle terminals, use the time the vehicle is idle. SimtoLink reviews batch OTA plans and can support the job on site.