Multi-Orbit Needs Multi-Tech Beyond Antennas

4/2/2024

Multi-orbit antennas were in the spotlight at the recent SATELLITE 2024 show. I heard much talk about them in meetings, on the floor and in panels.

There’s no lack of reasons for the attention. It’s being generated by trends such as mission requirements from government customers, product announcements from companies, including Kymeta and ALL.SPACE, and, maybe most of all, the explosive success of Starlink with subsequent business reactions from other satellite operators.

Suitable antennas are the essential element of any multi-orbit solution. But, as the logicians say, they are “necessary, but not sufficient.”

One thing missing is interoperability for those antennas. Last month, DIFI announced the formation of a working group to develop a state-of-the-tech industry standard for the ESA antennas needed for multi-orbit operations. Without such a standard, you might be able to support multi-orbit, but not multi-satellite, multi-operator or multi-mission, which will be needed for many, if not most, multi-orbit strategies implemented at scale.

That requirement raises another. Today’s antenna standards are based upon a legacy scenario in which a single-purpose antenna is controlled by a single modem. Those modems are the next issue. Most current approaches to multi-orbit terminals are still hardware-based, leading to a bad kind of multi: cobbling many proprietary boxes into a “Franken-modem” terminal needed to access each network in each orbit. As we have already seen in most proposed multi-orbit solutions today, that’s going to be big, heavy, inefficient, power-hungry and expensive.

The only realistic way multi-orbit works, especially at scale, is with a digital ground network architecture anchored by software modems and other virtualized components. That’s especially true when you consider that an increasing number of multi-orbit antennas are starting to generate a native digital signal. Let’s be generous here: at minimum, it’s sub-optimal to convert that back into analog just to transport it to a hardware modem. This is one reason why so many of the traditional satcom infrastructure companies are racing to bring out software versions of their legacy platforms.

Modems aren’t the only software apps that could be added to a modern uCPE-type terminal to enhance multi-orbit operations at the near or far edge of the network: virtual FEPs, security functions, signal monitoring and much more could be resident and orchestrated to match multi-orbit mission and service needs. But they only work at scale when they can interoperate.

If you are interested in participating in the DIFI ESA Working Group or any other DIFI effort, please visit https://dificonsortium.org/join-now/ for more information on this and other working groups.

---

What’s Jamming Up Flat Panel ESA Interoperability?

3/6/2024

One reason is that they’re not parabolic antennas.

Most industry standards for satellite terminals that cover antenna functions, such as Open-AMIP/BMIP, are based upon the legacy scenario in which a single-purpose parabolic antenna is controlled by a single modem.

Electronically Steerable Arrays (ESA), on the other hand, use an entirely different model to support many different modern use cases, especially those involving mobility. ESAs enable combinations of multi-orbit, multi-beam, multi-band operations, meaning standards and architectures determined by parabolics simply don’t work.

This “multi-, multi-, multi-” capability drives the case for integration with digital ground systems to efficiently package and switch between different modems and applications quickly, something that can be done easily in a digital ground system with virtualized modems… especially if the pieces can talk to each other seamlessly and work in an orchestrated way. Without that, the problem of vendor lock-in remains.

To address this much needed challenge, the Digital IF Interoperability (DIFI) Consortium has launched a new effort to develop an interoperability standard for flat panel ESAs. Multiple aspects will be considered over time, from seemingly simple things like defining signal levels in the digital domain to the more complex, such as differences between small form factors and enterprise use cases, which have different driving requirements.

The new DIFI-ESA Working Group will hold its first organizational meeting this month during the Satellite 2024 Conference in Washington, D.C. Jeremy Turpin, Chief Scientist at ALL.SPACE will chair the group, which already includes participation from organizations including All.Space, Bascom Hunter, ETL, Kratos, Kymeta, STE iDirect, Systems Technologies, Viasat and Wavestream. If you are interested in participating in the ESA Working Group (even if not attending Satellite 2024) please visit https://dificonsortium.org/join-now/ for more information on this and other DIFI working groups. If your organization is not yet a DIFI member, that same link will help you join. I encourage any organization with an interest in this very important topic to reach out.

---

Sharpening the Space Network’s Edge

2/6/2024

My recent post about satellite D2D service triggered a flashback for Reino Tantilla, who replied remembering the days when flip phones, digital assistants and cameras were three separate devices. “What’s the next step in convergence?” he wondered.

As Yogi Berra said, “It’s difficult to make predictions, especially about the future.” In the case of satellite ground systems, however, we’re already seeing the next step in convergence taking shape: reinvention of what we mean by the edge of a satellite network. Predicting here is pretty safe because many in our industry are following the same playbook the IT and networking worlds already used to enable previous generations of convergence—digitalization, virtualization and standards.

In the satellite world, especially for satcom, the network’s edge has almost always meant an end-user terminal, usually consisting of an antenna, a fixed-purpose hardware modem and some kind of user interface. When you wanted to do more, or if you needed to support multiple missions, services or waveforms, you had additional dedicated equipment, as in Reino’s remembered multi-device world of the 90s.

That is until everything gets digitized, virtualized and orchestrated on standards-based platforms, as has happened with smartphones and is starting to happen now in satellite. Then, purpose-built, proprietary terminals can be replaced with generic compute (called uCPEs in the terrestrial network world) that can host multiple virtual modems, sensors, apps, recorders, Bluetooth, Wi-Fi, security functions and more, all on the same device. The more satellite can be digitized, the more convergence can result.

In fact, the whole idea of what constitutes an edge is changing and converging. You could argue that multiple and hosted payloads were a step toward convergence in a sense, and as satellites and payloads increasingly become software-defined and multi-function, they become more like converged “edges,” not just a bend in the pipe. And the “places” where a satellite operator’s network meets a terrestrial network are edges where functionality can be added to better manage and orchestrate each set of systems. Sensor arrays can similarly be made more flexible, intelligent and convergent network edges.

Satellite D2D efforts have promise because smartphones and the networks behind them have already been digitized, standardized and stabilized enough that satellite can follow suit, eventually plugging into terrestrial network operating environments. How much capability we can offer from satellites will depend on resolving a few physics problems and getting our network systems integrated with theirs. The latter is certainly doable, and I have faith we’ll figure out the former enough to make an impact in the market.

---

Satellite D2D: When, Where and Especially How

1/7/2024

Is the business opportunity for satellite direct-to-device (D2D) on cell phones a done deal? Sort of. That was the consensus at the recent “Future of Wireless, AI and Convergence” web event organized by New Street Research and BCG, where execs from MNOs and other ecosystem players including AT&T, Verizon, Iridium and Deutsche Telekom said they see value.

Maybe it’s more accurate to say that the case has been accepted that there is viability in D2D, but different possible models: Which ones for which markets? How big will the markets be? And when? More about the discussion here from Constellations content partner Space Intelligence Report.

And there are some big “how” questions, too, when you look at the technology under the hood, driven by those business cases. Once you get past LEO vs. GEO, wideband vs. narrow, text vs. voice—more “vs.” than a Godzilla film festival—you get back to an essential how: How well will the various technologies and partners interoperate in the ecosystem? Remember the early days of 3G and 4G when some cell phones worked only with certain networks?

Skylo Technologies CEO Parth Trivedi spoke at the event. The company has built a Radio Access Network (RAN) using 3GPP standards, partnered with Qualcomm, Samsung, MediaTek and Sony. He emphasized the importance of the 3GPP standard, a given for any network to play in a non-customized cell phone world. Compliance with other standards will be necessary, too. For example, will the gNodeB signal processing live on the satellite to enhance downlink performance? Then you’ll want to virtualize the ground as much as possible with the DIFI standard. But if signal processing is to occur on the ground, putting less of a burden on the satellite, then eCPRI will be relevant, or a combination of both depending on the network architecture.

Here’s a key takeaway though: As Skylo’s Trivedi pointed out, well-designed standards like these aren’t a limitation, they actually spur innovation across the ecosystem and support flexible business decisions, like where to locate the signal processing, while maintaining interoperability. Across a rich and complex D2D supply chain, a lot of things will have to work together in different ways as the digital transformation of space continues.

---

TIPS from Telecom

11/28/2023

Recently I saw that Telefónica, one of the largest telephone operators and mobile network providers in the world, announced that it would keep its existing white box hardware from Edgecore Networks at more than 1,000 locations, but swap in software from a new vendor, Adtran.

According to Telefónica’s Cayetano Carbajo, “I believe this is the first time that router software has been replaced [in this way].” He added, “This is how it should be, changing the vendor without visiting the site.”

That’s just one data point in a movement toward disaggregation of hardware from software that’s been picking up steam across telecom. In a quick search, I saw similar announcements from other companies, including MTN Group, the largest mobile operator in Africa, implementing white box transponders from NEC Corporation that can be programmed to run any vendor’s software—a first for that continent where affordability and flexibility are greatly needed. According to MTN, “This disaggregation leads to cost reductions, accelerates innovation, and enables quicker and easier deployment of new network services.”

Besides routers and transponders, a number of communications industry groups have initiatives underway, especially The Telecom Infra Project (TIP), which has hundreds of participating companies in project groups running the gamut from OpenOptical to OpenLAN to Non-Terrestrial Connectivity.

Because of our stovepiped history, space is a networking domain that can particularly benefit from disaggregation, virtualization and open standards efforts.

Johannes Springer of Deutsche Telekom speaking at the recent ESA Commercialization Days: Transportation conference noted, “Very often— and I can say this after collaboration with the space industry for 20 years— the satellite industry has problems with standards. They are creating encapsulated systems, not taking into account that something is already there.”

“I want to organize a system that creates added value, and to integrate this system into an existing ecosystem that is based on standards,” he added. “In the terrestrial world, we have standards¬: 3GPP, 5G and going to 6G. We need to talk 5G on the satellites.”

Standards and disaggregation aren’t the same thing, of course, but you can’t have the second without the first. And it’s the disaggregation of software and logic from hardware that fully enables companies to optimize beyond proprietary vertical networks to embrace innovation across the entire ecosystem.

---

Plug-and-Playing at a Network Near You

10/31/2023

Space network interoperability reached another significant milestone. We completed our first “plugfest” for the DIFI standard recently in Colorado Springs with seven ground systems equipment makers participating.

Plugfests are a standard way for standards bodies to validate the effectiveness of their … well… standards by testing how well devices from different manufacturers work together.

Participating companies were Calian, Evertz, iDirect, Keysight, Kratos, Wavestream and Welkin Sciences. Tested devices included BUCs, combiners, dividers, DIFI stream generator/testers, IFCs (ADC/DAC), modems and modulators in 110 combinations across manufacturers in low, mid and high transfer rates up to 750 Msps.

Plugfests are intended to do two things: first, to check how well the standard achieves its intended purpose in working environments; second, to test how well individual devices or software implement that standard. I’d say DIFI hit a home run on the first by demonstrating interoperability across multiple devices in a range of profiles from manufacturers that have not worked together natively before.

On the second front, I’d call it a triple, with an 87% overall success rate on the tests, in large part because some of the devices were still in prototype phase. These results will help us advance the device certification process currently under development by the DIFI Certification Working Group, led by Keith King of Wavestream and Todd Renking of Welkins.

In addition to demonstrating that it works in the real world, we also learned some valuable information that will help the DIFI standard mature, especially for specific use cases. The plugfest was conducted using version 1.1 of the standard, and we are already starting to plan a second to be held in Europe that will use version 1.2. Companies interested in learning more can contact plugfest@dificonsortium.org.

---