Drones & robots: A2P SMS and mobile data

Machines that work outdoors, linked while they work.

In figures

  • Agricultural drones operate under per-country aviation rules (NOM-107 in Mexico, RBAC 100 in Brazil); connectivity planning starts only after the operating category is named.
  • A drone link carries two streams with different needs: command and control is low-rate and reliability-critical, payload video is high-rate and tolerant of a short gap. That is why they are often separated.
  • A robot that must stop safely cannot depend on the mobile link; the safety-rated stop lives on the machine, and the network carries supervision, telemetry and updates.
  • Remote teleoperation is latency-bound: a few hundred milliseconds of round-trip delay is the difference between driving the machine and waiting for it to answer.
  • Robot fleets update like phones: firmware, maps and logs are far larger than the telemetry sent while working.

This page is not legal advice.

Scenarios

Drones

Where the host network permits aerial use, agricultural spraying and mapping drones plus infrastructure inspection flights run with command links and payload offload on separate bearers where the regulation requires it. Command and control is a heartbeat with position and intent, so it is small and constant; the bearer comparison explains why the two streams are sized differently. Payload is the opposite: a mapping flight can produce several gigabytes of imagery, and a live inspection feed at 4 Mbps is about 1.8 GB an hour. Upload after landing where the mission allows it, and keep the airborne link for control and thumbnails.

Agricultural operations

Spraying, seeding and crop-monitoring fleets coordinated per field and per season, with operating categories named upfront. The work is seasonal and bursty: a fleet may fly every day for three weeks and then sit idle, so a monthly plan sized for the peak is the wrong shape. Flight logs, prescription maps and coverage imagery are downloaded at the field edge, often over the same link that carried the flight. Where the field has no coverage, the mission plan is loaded before take-off and the drone returns with the data rather than depending on a live stream.

Robots

Service, cleaning, lawn-mowing and industrial-inspection robots on supervised routes, reporting position, task state and maintenance needs. The link carries supervision, not control: the robot runs its route locally, and the network tells the fleet where it is and what it has done. A cleaning robot in a shopping center or an office block may have Wi-Fi in part of the route and cellular in the rest, so the software has to survive a handover without restarting the task. Give each robot a stable identity, log every task, and let a lost link stop the robot safely rather than leave it driving blind.

Industrial inspection

Chimney, tank, solar-row and facade inspection robots with video backhaul sized from the clip plan. Telemetry alone fits a narrow budget; a live camera changes the design. The operator needs to see enough to steer, not cinema quality, so stream a compressed preview and record the full-resolution video on the robot for upload later. Where the robot works inside a metal structure, the radio path is the constraint, not the bandwidth, and a relay or a tether may be the only workable option. Check the site's own permit rules before assuming a link is allowed.

Docks and remote operations

A drone dock turns a flight into a scheduled task: the dock opens, the aircraft launches, flies the route, lands and charges, and the data moves to the platform. That pattern needs an always-on site link rather than a link on the aircraft, and the upload of the day's imagery can be the largest traffic on the site. Docks face weather and power cuts, so pair the link with a UPS and a low-bandwidth fallback that still reports dock health. Walk the site with a signal tool before fixing the antenna.

Who buys this

  • Named operating categories with matching links.
  • Separate command and payload bearers where required.
  • Upload after landing, with live video only where it earns its budget.

Data reality

Indicative device profiles compiled from public research. Confirm the profile for your hardware at quote time.

ProfileMB/moRATSIM
Crop-spraying drone with RTK (work season) 300–1500 Cat-4 multi-IMSI, MFF2, SGP.32
Drone dock or service robot 10000–60000 Cat-4, 5G local profile, data pool
Delivery drone 5000–30000 4G, 5G multi-IMSI
Service or reception robot (4G backup) 100–1000 Cat-4 SGP.32
Commercial cleaning robot 200–2000 Cat-4, Wi-Fi SGP.32
Robotic lawn mower (RTK and 4G) 50–500 Cat-1 factory SIM
Quadruped or facility inspection robot 1000+ Cat-4, 5G SGP.32, local profile

Device admission

  • Buyers name the operating category and the sites at quote time.
  • Fleets with live video name the resolution and the session length.
  • Docks and fixed sites name their power and fallback arrangements.

RAT

BearerNote
LTE Cat-1 and above Command links and telemetry default; aerial use confirmed per market at quote time.
LTE Cat-4 Live inspection video and dock uploads.
5G where deployed Video backhaul for inspection payloads; check the site coverage first.

Product bundle

FAQ

Which drone uses fit?

Agricultural and inspection uses with a named operating category. The category decides the link budget, the separation of command and payload, and whether a beyond-line-of-sight approval is needed before the design starts.

Do inspection robots need high uplink?

Video backhaul is sized from the clip plan; telemetry alone fits narrow budgets. A compressed preview plus on-board recording is usually a better design than a full-resolution live stream over a contested radio path.

What about Brazil's drone rules?

ANAC RBAC 100 with DECEA procedures applies; agricultural work additionally follows MAPA rules. Mexico's NOM-107 is the equivalent there. Neither replaces the connectivity plan, which starts from the site survey.

Is cellular reliable enough for command and control?

For supervised operations where the machine fails safe on a lost link, yes. For safety-critical control, no: the stop function and the autonomy have to work without the network. Test the fail-safe behavior before the first flight.

How much data does a flight or a shift use?

It depends on what leaves the machine live. A 4 Mbps inspection feed is about 1.8 GB an hour; a mapping flight is several gigabytes uploaded after landing; command and telemetry are negligible. Decide what must be live before choosing a plan.

Request a quote