Direct-to-Device Satellite: The Next Connectivity Layer
D2D is becoming a service layer, not a separate network
Direct-to-device satellite connectivity allows a handset or another compatible device to communicate with a satellite when terrestrial coverage is unavailable. The commercial significance is not simply wider reach. It is the prospect of adding satellite coverage to familiar devices, subscriptions and applications without requiring customers to carry a traditional satellite terminal.
The market is not following one architecture. The International Telecommunication Union describes approaches ranging from mobile-satellite spectrum and geostationary infrastructure to low-Earth-orbit systems using terrestrial mobile spectrum. Those choices shape device compatibility, capacity, latency, coverage, capital intensity and the role of the mobile operator. Companies should treat D2D as a family of service models rather than a single interchangeable product.
Standards are improving the path to integration. ITU-R Recommendation M.2177, approved in February 2026, specifies satellite radio interfaces for IMT-2020. The ITU also reports that satellites are becoming embedded in the evolution of 5G and 6G systems. This does not make every device, band or market immediately compatible, but it strengthens the case for standards-based product roadmaps.
Start with the moment connectivity becomes valuable
A broad promise of coverage everywhere can obscure the economics. The strongest initial use cases occur where a short period without terrestrial service creates disproportionate cost, delay or risk. Examples include a field technician confirming a repair, a vehicle transmitting an exception alert, a logistics device reporting outside a mobile corridor, or a traveller sending a message from a remote location.
The required service level differs sharply by use case. Emergency messaging needs dependable access and clear user instructions, but little bandwidth. Asset telemetry may send small packets at intervals and tolerate delay. Voice requires continuity, and broadband applications need far more capacity. A company should define the minimum useful transaction before choosing a network or commercial model. Buying a broadband promise for a narrow telemetry need can destroy an otherwise sound case.
Demand analysis should use geography and event frequency, not population averages. Map where existing devices lose coverage, how often that occurs, what work stops, and what the fallback costs. The addressable volume is the number of valuable disconnected events, not the number of nominally covered users. This also reveals whether satellite is a primary requirement, an insurance layer or an occasional premium feature.
Match the proposition to the industry
In logistics, the initial value may be continuity for high-value or time-sensitive loads outside normal corridors, not continuous tracking for every parcel. In utilities and field service, it may be closure of work orders and exception alerts from isolated sites. Automotive propositions can begin with assistance and safety messaging before moving toward richer connected services. Wearables can focus on short, intentional interactions rather than background data synchronisation.
Each vertical has a different buyer and proof requirement. A consumer feature must be discoverable, simple and priced against occasional use. An enterprise service must integrate with fleet or workforce systems and provide auditable service records. An original-equipment manufacturer must make decisions years before launch about antennas, chipsets, certification, battery performance and regional variants. A single network capability therefore needs several product strategies.
The operator relationship remains central
D2D is often presented as satellites bypassing terrestrial networks. Current European activity points toward operator-led integration. Telefonica's March 2026 collaboration is evaluating technology, integration models and use cases in Spain and Germany while maintaining an operator-managed experience. That matters for identity, billing, support, roaming, network policy and customer trust.
Vodafone's launch announcement for Satellite Connect Europe describes an open-access provider intended to connect European mobile operators, with five European ground stations planned. It also emphasises service control, customer relationships and data handling. For enterprise buyers, this suggests that procurement may look less like buying an independent satellite terminal and more like extending an existing mobile estate through an operator and its satellite partner.
The contract map still needs scrutiny. Identify the mobile operator, satellite network, ground segment, core-network integration, device or chipset dependencies, service platform and application provider. Allocate responsibility for activation, failed sessions, security incidents, data residency, coverage claims and end-user support. A seamless customer proposition can conceal a complex multi-party delivery chain.
Design a progressive service ladder
Companies should resist launching every capability at once. A service ladder can begin with store-and-forward messaging or telemetry, then add richer data, voice and broadband as capacity, devices and regulation mature. Each step needs its own acceptance criteria and commercial proof.
The European market already shows this progression. Orange says it launched a satellite messaging offer in France in December 2025 and plans demonstrations in Romania covering voice, SMS and data in the second half of 2026. The sequence is instructive: start with a bounded service, learn how customers discover and use it, then test higher-demand capabilities in a controlled market.
Every tier should state what it does not guarantee. Coverage may depend on an outdoor view of the sky, handset configuration, satellite availability, local authorisation and network conditions. User interfaces should show when a device is attempting satellite access, whether a message is queued and when it has been delivered. Ambiguous status can turn a resilience feature into a support problem.
Integration is the real product work
A successful D2D service needs more than a radio link. Companies must integrate identity, provisioning, application logic, billing, consent, support, device management and operational monitoring. An enterprise workflow should recognise that satellite may offer lower throughput and intermittent availability than terrestrial service. Applications should compress data, prioritise essential transactions, retry safely and avoid duplicate actions.
For connected products, firmware and application teams should separate critical messages from background traffic. A vehicle may prioritise an exception event over diagnostics; a wearable may prioritise an assistance message over routine synchronisation. For field operations, forms can be designed to submit a compact confirmation first and attach rich media later when terrestrial coverage returns.
Security controls must span the full path. Device identity, encryption, keys, software updates, ground infrastructure, operator interfaces and application APIs all matter. Logging should reconcile what the application submitted, what the network accepted and what the destination received. Where the service supports a high-consequence workflow, the company needs a second verification step rather than assuming transport success proves business completion.
Put device strategy on the critical path
Network announcements can move faster than device estates. A company should maintain a compatibility register by model, operating system, radio capability, SIM profile, country and application version. Bring-your-own-device programmes need an explicit unsupported-device policy. Managed fleets need a refresh forecast showing when enough compatible equipment will be deployed to justify a scaled service.
Battery and user behaviour require field evidence. Satellite acquisition may consume more energy than routine terrestrial connectivity, and users may need to move outdoors or orient a device. Product teams should measure time to connect, power impact and failure recovery under realistic conditions. Training and interface cues should be designed for the stressed or time-pressured user, not only for a controlled demonstration.
Regulation is part of market design
Spectrum and device authorisation will influence both launch timing and the partner model. In the UK, Ofcom's June 2026 statement created a licence exemption for qualifying handsets and SIM-enabled devices connecting to D2D services in specified 900 MHz frequencies, following a licence variation for VodafoneThree. The rules were intended to take effect on 10 July 2026.
A company planning a multi-country service should not extrapolate one market's authorisation. It should maintain a country matrix covering permitted bands, responsible licensee, device requirements, lawful access, data handling, emergency-service treatment and consumer disclosures. Market entry should follow regulatory readiness and tested partner capability, not a uniform global date.
Build the economics around avoided failure
The cost comparison is rarely satellite versus no cost. The relevant alternatives may include extra terrestrial sites, private radio, specialist terminals, manual check-ins, delayed work or accepting outages. Quantify the value of the disconnected event: technician time, vehicle downtime, missed delivery, spoiled inventory, safety escalation or customer churn.
Model costs by active device, message, data volume and geography. Include integration, certification, support, testing, device refresh, roaming, minimum commitments and exit costs. Capacity is shared and may be constrained during widespread disruption, so a business case should not assume every device can transmit high-bandwidth data simultaneously. Priority rules and fair-use policies are commercial inputs, not footnotes.
A good pilot measures more than successful connections. Track acquisition time, delivery latency, success by device and environment, battery impact, duplicate transactions, support contacts, user comprehension and the proportion of sessions that produced a valuable outcome. These measures connect network performance to customer and operating value.
Test resilience without overstating it
D2D can diversify access, but the service still depends on satellites, gateways, spectrum authorisation, operator cores, devices and applications. Some components may share power, cloud or identity dependencies with the terrestrial service they are meant to back up. A resilience claim should be supported by dependency mapping and exercises, not by the presence of a second radio path alone.
Run scenarios that include a local mobile outage, a ground-station problem, congested satellite capacity and a failed partner interface. Decide which users and messages receive priority, how long queued transactions remain valid, and how service status is communicated. The exercise should verify that operations can distinguish a coverage limitation from a device, application or provider incident and route support accordingly.
A staged rollout for companies
Stage 1: prove the problem
Choose one user group, one geography and one disconnected event. Establish the current cost and fallback. Define the smallest useful satellite transaction and identify compatible devices already in the estate. Reject use cases where terrestrial improvements or workflow changes solve the problem more cheaply.
Stage 2: prove the service
Test outdoors and in representative terrain, weather and movement conditions. Validate activation, application behaviour, queuing, acknowledgement and support. Run security and privacy review across every partner. Confirm that customer language reflects actual availability and limitations.
Stage 3: prove repeatability
Expand only after performance is consistent across devices and locations. Automate provisioning and reconciliation. Establish service-level reporting, escalation paths and change control. Exercise a provider outage and a high-demand event. Compare the realised value per successful disconnected event with the complete service cost.
Stage 4: build a portfolio
Add use cases that reuse the same devices, contracts, operational controls and integration layer. Review when voice or broadband genuinely changes the value proposition. Preserve portability by keeping application logic and business records separate from provider-specific interfaces where practical.
FAQ: direct-to-device satellite connectivity
Does D2D work with ordinary smartphones?
Some services are designed for existing 4G or 5G devices, while others depend on compatible satellite bands, chipsets or software. Compatibility must be verified for the specific service, market and device estate.
Will satellite replace terrestrial mobile networks?
The near-term business model is complementary. Terrestrial networks provide capacity and indoor coverage where demand is concentrated; satellites extend reach where building that coverage is difficult or uneconomic.
Which use case should a company test first?
Choose a frequent, measurable coverage gap where a small message or telemetry event avoids meaningful cost or delay. A narrow operational case produces clearer evidence than a general promise of universal connectivity.
What is the biggest integration risk?
Assuming the radio link is the entire service. Provisioning, application behaviour, acknowledgement, billing, support and multi-party incident ownership determine whether connectivity creates a reliable outcome.
How should a buyer compare providers?
Compare verified device support, permitted markets, service tiers, capacity policy, ground and core-network integration, operational evidence, data handling, support ownership, change notice and exit terms.
References
· ITU: Direct-to-device satellites: Four ways to connect the world
· ITU: Direct to device services: Poised for the leap to 6G
· Ofcom: Direct to Device licence exemption regulations update
· Orange: D2D collaboration and Romania demonstrations
· Vodafone: Satellite Connect Europe launch
· Telefonica: Exploring D2D satellite connectivity in Europe