Satellite messaging, broadband, positioning and Earth observation
Four different jobs often get grouped under “satellite”. Separate the device uplink, a network backhaul, position/time input and remotely observed data.
By Admin · Checked 20 October 2026.
Ask what information must move and between which endpoints. Sending a small field reading, carrying a site network, calculating a position and receiving an Earth-observation dataset require different equipment and evidence.
Start with three decisions
Send a reading
Satellite IoT messaging carries device/application data. Specify payload, direction, reporting interval and delivery deadline for the exact service and terminal.
Connect a site
A broadband or backhaul connection can carry traffic from a gateway or local network. Specify the total traffic, installation, power, service plan and upstream application.
Add context
Position/time and Earth-observation information are inputs. They do not by themselves deliver your field sensor’s latest reading to your application.
Work through the practical questions
Messaging: small records with explicit meaning
A status code or sensor record needs an identifier, timestamp, encoding and application endpoint. Do not confuse the ability to deliver a message with the ability to stream video or control equipment within a fixed deadline.
Backhaul: a connection for a local network
Draw every local sensor and gateway before estimating traffic. Include protocol overhead, updates, diagnostics and access management. A gateway still needs functioning local links and an application even when its external connection is available.
Positioning: where and when
A GNSS receiver uses satellite signals as inputs to a position/time solution. To report an asset’s location remotely, a tracker also needs a communication path. Check the receiver, antenna, environment and intended accuracy evidence separately from that uplink.
Earth observation: context across space and time
ESA describes space-based observation as data about Earth and its environment. When combining imagery with ground sensors, record acquisition date, spatial resolution, location alignment, cloud/quality flags and uncertainty. A pixel and a probe do not measure the same area by default.
A field example
A soil probe can generate a local reading; a positioning receiver can identify the observation location; a satellite uplink can transmit the record; an Earth-observation dataset can add regional context. Each input has its own timestamp and limits.
Choose the job before the company
Use the service directories to find the role you need. A company may offer several service families. Confirm the exact package rather than transferring the capabilities or pricing of one family to another.
Primary sources
Iridium messaging example · Viasat service-family map · ESA Earth-observation introduction
Continue with your next decision


NEXT DECISION
Open an exact messaging service
See the terminal, plan and pilot questions.

NEXT DECISION
Connect data to a field decision
Consider placement and maintenance.
