Between 2002 and 2012, alongside its Iridium and Thuraya satellite voice resale business, Tempest Telecommunications operated a parallel satellite data terminal practice. The product line was anchored on three platforms: Thuraya data terminals over the GEO regional constellation, Inmarsat Regional BGAN (R-BGAN) terminals over the I-3 satellites from 2002, and global BGAN terminals over the I-4 satellites from late 2005. All three sat inside the same unified Tempest customer platform that handled the voice handsets — one customer relationship, one login, consolidated billing across voice and data services, prepaid or postpaid at the customer's election.

The pre-BGAN era: Regional BGAN, 2002–2009

Inmarsat launched Regional BGAN in October 2002 over its existing Inmarsat-3 satellite constellation. Coverage extended across Europe, the Middle East, Africa, the Indian subcontinent, and parts of Central and South-East Asia — not global, but covering most of the population centers where satellite IP data was operationally relevant in the early 2000s. Data rates were modest by later standards: 144 kbps shared-channel IP, packet-switched, with a flat-rate or per-megabyte tariff structure that made the service economically realistic for short bursts of email, file transfer, and thin-client remote access from remote field sites.

The customer-side hardware was the R-BGAN UT terminal — a roughly laptop-sized, battery-powered unit with a directional flat-panel antenna that the operator pointed manually toward the appropriate Inmarsat-3 satellite, an Ethernet jack for the connected laptop, and a hardware activation key for service entitlement. The terminal worked stand-alone or attached to a vehicle and was designed for deployment by non-technical personnel after a short orientation. Tempest distributed the R-BGAN UT with multilingual customer documentation — English, French, Spanish, Russian, and Arabic versions of the terminal user guide survive in the company's archived documentation, reflecting the multinational deployment profile of the customer base.

Regional BGAN was Inmarsat's bridge between the company's pre-broadband satellite-IP services (Inmarsat Mini-M Data, GAN, Fleet) and the global broadband BGAN service that would launch on the next-generation I-4 constellation. R-BGAN gave Inmarsat a real-world service to operate while the I-4 satellites were being built and launched. It also gave resellers like Tempest a three-year head start on the satellite-IP customer-development curve: by the time global BGAN launched in late 2005, the customer base, the support workflows, the field-deployment documentation, and the integration into Tempest's billing platform were already in place. R-BGAN service continued in parallel with BGAN until 2008–2009, at which point Inmarsat retired the regional service and migrated the remaining customers onto the global product.

The BGAN era: global satellite IP, 2005 onward

Inmarsat launched the first of its I-4 satellites in March 2005, with global commercial BGAN service following in late 2005. BGAN extended the R-BGAN pattern in two important directions: it added global coverage with the three I-4 satellites (the Americas constellation was added in 2008), and it raised the per-terminal data rate to 492 kbps standard IP, with optional streaming-class channels that gave broadcast customers committed bit rates for live video uplink. The terminal form factor evolved as well, shrinking from the R-BGAN UT's laptop size to compact-briefcase units that field-deployed in under two minutes from cold storage.

The BGAN terminal market in the mid-2000s supported several manufacturer options, all of which Tempest carried:

Manufacturer Terminal Positioning
Hughes Network Systems HNS 9201 High-end full-duplex terminal; broadcast and enterprise deployments
Thrane & Thrane (later Cobham SATCOM) Explorer series Mid-range to high-end; widely adopted across NGO and oil-and-gas deployments
Nera (later EM Solutions) WorldPro 1010 / 1000 Mid-range portable terminals; maritime and field operations
Addvalue Wideye Sabre I Entry-level handheld-class terminal; price-sensitive deployments

Tempest's terminal catalog covered the full range from the entry-level Addvalue Sabre to the high-end Hughes 9201, which let the company match the terminal specification to the customer's use case rather than push a single hardware standard onto every deployment. A broadcast media team running live uplink from a conflict zone needed the Hughes or Thrane terminals' streaming channels and antenna gain; an NGO field office in a stable but remote location did fine on an Addvalue Sabre for email and occasional file transfer. The post-2005 BGAN customer base consequently spanned the same operational categories Tempest's voice business already served — humanitarian and development field operations, oil-and-gas exploration, conflict-zone broadcast media, emergency response, expeditionary military and contractor deployments — but with each category now able to provision data rates appropriate to its specific workflow.

The Thuraya data complement

Alongside the Inmarsat data platforms, Tempest also resold Thuraya's data offerings. Thuraya's data product line evolved across the 2000s from GPRS-rate data over the voice handsets (slow, but useful for SMS, email, and very small file transfers) toward dedicated data terminals and, by 2007, the ThurayaDSL satellite-IP service with rates up to approximately 444 kbps over the regional constellation. ThurayaDSL competed directly with R-BGAN in MENA, South Asia, and parts of Africa, often on price and on the dual-mode advantage Thuraya's hardware retained: a single terminal that operated both as a satellite IP modem and, where local GSM coverage existed, as a terrestrial fallback for cost-sensitive usage.

The Thuraya and Inmarsat data product lines did not directly substitute for one another in practice. They served different regional footprints, supported different deployment models, and had different price-and-rate trade-offs. A customer choosing satellite data for a specific deployment typically selected one or the other based on the geographic footprint of the operation and the data rate the workflow required. The unified Tempest platform let customers manage either or both from a single account view, with consolidated invoicing and a single support relationship across the carriers.

Unified platform mechanics

The architectural pattern Tempest had established for voice in 1997 carried through to data with some adjustments. Voice services across PSTN, Iridium, and Thuraya all decremented per-minute against a prepaid balance or accrued per-minute against a postpaid statement. Data services across R-BGAN, BGAN, and Thuraya data billed against per-megabyte or per-streaming-minute rate cards that varied by carrier and terminal class. For prepaid customers, the data consumption decremented the same balance pool the voice services drew from, with megabyte-to-balance conversion happening at the prevailing rate card. For postpaid customers — the majority of the data customer base, given the price-per-megabyte of satellite IP made unbounded prepaid exposure operationally difficult — the satellite data lines appeared as itemized entries on the same monthly statement as the voice services, with the unified customer relationship handling the cross-carrier reconciliation transparently.

The customer-side abstraction held in either billing model. A customer running Iridium voice on a handset, BGAN data on a Thrane Explorer terminal, and PSTN voice on a calling-card PIN experienced one supplier, one login to view usage and balances, one invoice or statement, and one set of customer support contacts. Under the unified platform layer, three distinct satellite carrier billing systems and one terrestrial calling-card platform fed the same account record. The complexity was absorbed where it belonged — in the platform — rather than passed through to the customer.

Customer workflows

Satellite data terminals served use cases that pure satellite voice could not. Email synchronisation for a field office where the alternatives were physical document courier or weekly trips to a city with terrestrial connectivity. Daily report uploads from a humanitarian field deployment to a headquarters server. Live video uplink from a broadcast crew covering a conflict zone or natural disaster. Remote-access sessions for an oil-and-gas crew querying central reservoir databases from offshore platforms. Wire-service photograph upload from staff photographers operating in countries where the local Internet infrastructure was either absent or untrusted.

Each of these workflows had been operationally impossible or commercially impractical before satellite IP services existed. Each became routine in the 2005–2012 BGAN era. The satellite data terminal was the field complement to the satellite voice handset: where the handset gave the field operator a voice channel back to headquarters, the BGAN or Thuraya data terminal gave the same operator a data channel for the things voice could not carry — documents, images, video, structured data, software updates pushed to field hardware. Together with the satellite voice handsets and the Tempest-provided pre-deployment training, the combined voice-plus-data field kit became a standard piece of equipment for the customer categories Tempest served through the late 2000s.

The 2012 closeout

The consumer-scale satellite-data reseller market faded on the same curve as the satellite voice market, and for the same reasons: terrestrial cellular data extension into previously unreached regions, the rapid improvement of cellular data rates from 3G to 4G to LTE during the late 2000s and early 2010s, smartphone tethering that made laptop-class data available wherever a smartphone could find a cell signal, and the maturation of regional satellite Internet services that bypassed the global incumbents on price. The high-end of the satellite data market — broadcast streaming, government-grade reliability, genuinely remote operations — remained, but consolidated upward toward enterprise contracts directly with Inmarsat, Thuraya, and the emerging high-throughput-satellite operators (Viasat, KA-SAT, later Starlink Business and others).

Tempest wound down its consumer-facing satellite operations in the early 2010s in tandem with the broader closeout of the international traveller and field-connectivity business that had been the company's core product line since 1997. The unified-platform architecture — one customer relationship spanning calling-card PSTN voice, dial-up Internet roaming, Iridium satellite voice, Thuraya satellite voice, Thuraya data, Inmarsat Regional BGAN, and Inmarsat global BGAN — closed with the business that had operated it. The pattern, again, did not. Modern unified-billing platforms that broker authentication, accounting, and reconciliation across multiple heterogeneous carrier back-ends use the same shape. In the intervening years the underlying market grew to a scale that made the platform investment reach billions of dollars. In 1997 through 2012, Tempest had built and operated a proportionate version of the same pattern against a much smaller market, and it had worked.

Sources and further reading

This page is part of an ongoing historical archive of the 1989–2012 international telecom industry, maintained by Jason Jacoby, a former operator at Interglobe (UK phone cards) and Tempest Telecommunications. Multilingual R-BGAN UT and BGAN terminal documentation referenced here is preserved in this site's documentation archive. Corrections and additions welcome via the contact page.