21 octobre 2020 | International, C4ISR

Are software-defined ground stations the next big leap? Kratos is betting on it.

WASHINGTON — Software-defined payloads have revolutionized how industry and the government approach satellites. So why not software-defined ground stations?

That's the question Kratos is asking. On Oct. 20, the longtime Pentagon contractor with experience building satellite support systems unveiled its new OpenSpace platform — a family of virtual products that applies the software-defined approach to the ground station. OpenSpace uses an open standards, cloud-based system that can be continuously adjusted to mission needs without having to install new hardware.

Pentagon officials often complain that the nation's current satellite ground architecture is stymied by stovepiped, custom-built proprietary ground systems. The department has said it plans to move to an enterprise ground system, but it's not there yet.

Kratos hopes that OpenSpace can at least be part of the solution.

Because the platform is software-based, satellite operators no longer need to use custom-built hardware to connect to and control their on-orbit systems. Instead, OpenSpace virtualizes the ground system in software, effectively allowing it to be linked up to any antenna with a digital converter.

“It's a big announcement from our perspective in that it's going to address a lot of the key issues that are challenging the space industry across the board, and especially some of the issues that the defense and government world is going through,” Neil Oatley, Kratos' vice president for marketing, told C4ISRNET.

Software-defined payloads have opened up new possibilities in the space industry. Previously, satellites were designed to be rather static tools — once placed in orbit, it becomes all but impossible to physically replace the payload hardware or refigure the software. That means that the system you launch is the system you've got, regardless of whether your mission needs change or you want to do something new with your orbital tech.

The Defense Department is investing in capabilities that could eventually allow physical access to operational satellites via robotic space vehicles, but that's still in development.

All that is just to say, when the military builds a satellite, it builds it with the expectation that the space-bound payload will be largely static over the lifetime of the spacecraft. In other words, it will do the mission it was meant to do, and not much else.

“When you look at the ground today, it's the one area where we're really stuck back in 2G-type technology,” said Phil Carrai, president of Kratos' Space, Training and Cyber division. “Systems are stovepiped. They're static. They're built with custom hardware. They have software-specific technologies that are dedicated to specific satellites. And that's really making them unable to play in the coming new world.”

Building a new, custom ground system for each new satellite or constellation is not only costly, but it limits flexibility. The satellite-specific nature of existing ground systems makes it difficult to build third-party applications that can easily be installed across systems. Moreover, it limits the ability of operators to simultaneously connect to multiple constellations using the same ground system.

However, industry has created a workaround.

Satellites may not be physically inaccessible, but they frequently communicate with operators over radio frequency signals. If a given payload's functions are largely virtualized — meaning they are software-defined and not hardware-defined — then operators can alter a given satellite's capabilities and mission by simply installing new software.

Hence, the growing interest in building software-defined payloads. In fact, the next GPS payload will feature an entirely digital payload.

With OpenSpace, Kratos is applying the basic principles of software-defined payloads to satellite ground systems — the technology used to command and control the spacecraft once it's on orbit. The ground system is what operators use to cue, download data from, and monitor their satellites. According to Kratos, its OpenSpace platform is the first dynamic, software-defined ground system that will apply those lessons learned from the space layer to the ground layer.

“What we did with OpenSpace is we actually started from scratch with an entirely new platform that is based on the fundamentals of network function virtualization (NFV) and software-defined networking (SDN),” said Greg Quiggle, vice president of product management at Kratos, comparing the platform to the architecture underlying new 5G networks. “We took that same basic premise and we applied it to the way a ground system should be built to interconnect software-defined satellites, multi-constellation networks and a terrestrial network.”

A key feature that enables OpenSpace is the digitization of the radio frequency signal as close to the antenna as possible, transforming that flow of data into what is effectively a large ethernet network.

“Once you've done that — you move from [radio frequency] to digital — you now can process those subchannels, that bandwidth, in software through something called virtualized network functions,” Quiggle explained.

The platform takes typical purpose-built ground station hardware — splitters, channelizers, matrix switches, modulators, demodulators and much more — and recreates them in a virtual environment. Once the radio frequency data is digitized, it can be processed through all of these virtual tools.

One consequence of that is the software can be run anywhere — it does not have to be located at the antenna. Operators can run this solution in the cloud or in a classified data center, said Quiggle.

That also means any ground station using OpenSpace can be quickly adjusted for different uses. For instance, take an operator who needs to interact with satellites. By using an OpenSource-enabled ground station, that individual can load his or her own software-defined solution into the system, connect with the satellite, download any data and cue the spacecraft for its next tasks. Once that satellite passes out of view, a second operator can take over the ground station, load an entirely different software-defined solution and interact with the satellite as it passes over. In this scenario, both users were able to use a single ground station to communicate with their own unique satellites.

In another example, the first user is ready to use one ground station to interact with a satellite as it passes overhead, but inclement weather disrupts the process. Instead of waiting for the satellite to pass overhead again, the user simply needs to find the next available ground station on the satellite's course, virtually load software and then access the satellite from there.

Military applications

OpenSpace is clearly set to have commercial implications. In fact, Microsoft announced Oct. 20 that it will use OpenSpace as part of its Azure Orbital ground-station-as-a-service.

Azure Orbital is Microsoft's answer to Amazon Web Services' Ground Station model, which allows customers to access their satellites by renting time on Amazon's ground stations and the AWS platform. It's a business model that could be attractive to small companies looking to field small satellites without building massive, cost-prohibitive ground systems to support them.

But a product like OpenSpace could make an even bigger splash in the military space community, especially when it comes to satellite communications.

In a statement released earlier this year, the Space Force laid out its concept of “fighting SATCOM.” The service envisions enabling war fighters to roam among satellite communications providers to ensure forces remain connected even if one provider is jammed or unavailable. That level of fluidity requires some major changes to how the military has traditionally approached satellite communications.

“One of the things that the government is looking for very specifically is the ability to create an open enterprise-wide architecture for their protected communications systems,” said Frank Backes, senior vice president for federal space-related business at Kratos.

“And as they move forward with proliferated LEO [low-Earth orbit] and MEO [medium-Earth orbit] constellations to add communication options, resiliency and capability to their current geosynchronous space communications environment ... this ground architecture is very critical to the defense goals and what they're trying to achieve,” he added.

Currently, the ability to roam between constellations to avoid jamming is hampered by stovepiped systems, which are designed to work with a single satellite or a set of satellites. Because OpenSpace can leverage any radio frequency antenna, digitizes that signal and process that data in software, the operator can use the same ground station for multiple constellations. Kratos certainly hopes that its system could be the ground solution for the “fight SATCOM” concept.

“Today, the U.S. government on the defense side is very dependent on their own antennas and their own hardware that is deployed for their communications infrastructure and their satellite command-and-control environment. And one of the reasons for that is the hardware that is out in the field today is protected hardware: It may have specialized waveforms, it may have specialized components, it may even have specialized encryption infrastructure,” Backes said. “That limits the military to only using certain apertures for communications. As soon as you move to this dynamic environment — this OpenSpace environment that Kratos is talking about — now you have the ability to use any commercial or military antenna infrastructure for your system and dynamically configure that as needed.

“Combined with the ability to move protected hardware out of the field and putting that into a controlled cloud environment, now all of a sudden I have the ability to create the resilient environment that the Department of Defense is looking for.”

Kratos told C4ISRNET in a statement that the company “is providing satellite ground system engineering support on several DoD pLEO space segment teams.” In addition, the company noted it “will be bidding our OpenSpace and [Eterprise Ground Services] capabilities on pLEO systems as those opportunities mature.”

“When you look at ... the new LEO and MEO constellations — just from a pure imaging/sensing perspective — we don't see how you make those happen without an element of a dynamic software-defined ground,” Carrai said. “The timing has to be second or milliseconds. That we think is going to be essential for us to really get what we're paying for and we need from a U.S. constellation perspective.”

https://www.c4isrnet.com/battlefield-tech/space/2020/10/20/are-software-defined-ground-stations-the-next-big-leap-kratos-is-betting-on-it/

Sur le même sujet

  • NASA accidentally broadcasts simulation of distressed astronauts on space station
  • UK facilities for American F-35 jets are delayed and over budget

    7 août 2020 | International, Aérospatial

    UK facilities for American F-35 jets are delayed and over budget

    By: Valerie Insinna WASHINGTON — The U.S. Air Force is on track to begin permanently basing its F-35 jets abroad next year, with RAF Lakenheath in England set to become the service's first international F-35 base. But construction on new hangars and facilities necessary for supporting the high-tech stealth jet have gone over budget and over schedule, and many buildings won't be ready when the first planes arrive in November 2021. On average, construction projects associated with the F-35 beddown at Lakenheath are about 25 percent over the initial $480 million budget estimated in 2015, said Lt. Col. Clinton Warner, who leads the 48th Fighter Wing's F-35 program integration office. “The overall trend has been projects are late and also over budget,” he told Defense News during a July interview. “A lot of the assumptions that were made back in 2015 weren't necessarily valid. There's been cost growth that was outside of the planning assumptions that were made back in 2015.” The cost increase is not the only problem. As RAF Lakenheath's first F-35 squadron stands up, neither the hangars planned to house the jets nor the headquarters building used for planning operations and maintenance will be ready, Warner said. A training simulator building will also be late. Despite the delays, the Air Force still plans to move forward with the beddown of the jet. Warner said the service is exploring options to keep operations on track, such having the new F-35 squadron share space with existing units — which include three American F-15 squadrons — or potentially leasing additional facilities on base from the United Kingdom. “In terms of getting here and flying the aircraft, we will still do that. [There is] really no difference in terms of the capability is going to be delivered, but it'll just look different in how we do it,” Warner said. “It will be some strain on the units here at the base, as there's more crowding and with waiting for those facilities to come online.” The arrival of U.S. Air Force F-35s in Europe has been a long-awaited milestone for the service, which announced in 2015 that RAF Lakenheath would become the first international location to get the jets. Since then, F-35s temporarily deployed to the base in 2017. “Having a fighter with the capability of the F-35s one hop closer to a part of the world that's seemingly less stable certainly will have a deterrent effect,” said Frank Gorenc, a retired four-star general who commanded U.S. Air Forces in Europe from 2013 to 2016. “Being able to daily train with the partners that have F-35s will have a deterrent effect,” Gorenc told Defense News. “It will cause interoperability to soar both on the maintenance side and on the operations side. I think the benefits of having that equipment — the demonstration of having a fifth-generation [fighter jet] in theater combined with F-15Es and F-16s — I think is the right signal.” Under the current plans, F-35 pilots and maintainers will begin to arrive at RAF Lakenheath in June 2021, with the first aircraft to follow in November. The base will eventually be home to two F-35 squadrons, each with a total of 24 jets. That beddown will follow more than five years of planning and development on the part of the Air Force, which stood up a team in 2015 to get the base ready for the incoming jets. In 2018, the U.S. Air Force chose Kier-Volker Fitzpatrick, a joint venture of U.K.-based design and construction firms Kier Group and VolkerFitzpatrick, to build and renovate all installations associated with the F-35 presence at RAF Lakenheath. Construction began in July 2019, with seven of 14 new facilities — which will include new hangars, a building for flight simulation, a maintenance unit and storage facilities — currently either being built or already complete. As unforeseen costs have mounted, the base's program integration office has had to request $90 million in additional funding from Congress, as well as permission from the Pentagon to revise the scope of the projects, Warner said. But there's no overarching answer for why costs have ballooned. “Each individual project had a different set of assumptions, a different set of risk profiles, and some were correct and some are not correct,” Warner said. With only a few years between the decision to base F-35s at Lakenheath in 2015 and the original planned start of operations in 2020, the U.S. government wanted to put a construction firm under contract sooner rather than later, said Stephen King of the Defence Infrastructure Organisation, a U.K. government agency charged with overseeing the building and maintenance of military facilities. But workforce costs grew as the project was discovered to be more complex than originally anticipated. “When the workers are tendered, the prices that are coming back in are found to be different from those originally estimated, and it seems to be the price of doing business on a military establishment. There seems to be an ‘add-on' to the outside market,” King said. Because the F-35 is a stealth jet that processes large amounts of classified information, many of the installations linked with its operations must meet certain security specifications. Building those structures to both U.S. and U.K. standards while using a foreign workforce of U.K. citizens posed challenges that the U.S. Air Force did not foresee during the design process, Warner said. “Luckily most of these problems are behind us, but they did cause delays in terms of when we were programming out in the schedule and looking at what we thought it would look like,” he said. “Some of the challenges associated with building those secure facilities were not fully understood.” Air Force officials have said keeping the projects on track was always going to be a challenge. In 2016, Col. Robert Novotny, who was then the commander of the base's 48th Fighter Wing, predicted construction projects could face troubles getting funding or finding a skilled workforce to build the new facilities, and that F-35s likely wouldn't begin to arrive on base until at least 2021 or 2022. “For me, the concern I have when I look at Lakenheath is not the F-35,” he told Defense News in July 2016. “For me, the concern I have is: Are we going to be able to build enough stuff fast enough?” https://www.defensenews.com/smr/nato-air-power/2020/08/06/uk-facilities-for-american-f-35-jets-are-delayed-and-over-budget/

  • Countering missile threats means addressing the present while planning for the future

    25 juin 2020 | International, Aérospatial

    Countering missile threats means addressing the present while planning for the future

    By: Ian Williams In 2017, I helped author the CSIS report “Missile Defense 2020,” a broad look at the history, status and future of the U.S. homeland missile defense system known as Ground-based Midcourse Defense. The report argued that the establishment of GMD had put the United States in an advantageous position relative to the North Korean missile threat, but this advantage would be short-lived if the United States failed to improve GMD through incremental milestones and regular testing. GMD has had some notable achievements with this strategy. The Pentagon, however, seems to be moving away from this proven approach to GMD, attempting great leaps rather than manageable steps. This riskier approach could make the United States less secure over the near and long term. Until recently, GMD had been following a well-defined road map, with good results. After a series of flight-test failures from 2010-2013, the Missile Defense Agency began a rigorous effort to root out anomalies within the system's Ground-Based Interceptors, or GBI. MDA carried out a successful intercept in 2014, followed by intercepting an intercontinental ballistic missile-class target for the first time in 2017. In 2019, GMD engaged an ICBM target with a salvo of two GBIs, marking another first for the system. MDA also expanded the fleet to 44 GBIs and is constructing a new Long Range Discrimination Radar in Alaska to provide the system much-needed sensor support. These achievements were supposed to be followed by an incremental modernization of the GBIs. The plan was to incorporate a new Redesigned Kill Vehicle around the year 2020. The RKV would be similar in concept to those currently deployed but incorporate new technologies and nearly 20 years of lessons learned. Another part of the plan was to give the GBIs a new booster, one that gave the war fighter the option of using either two or three stages, thereby providing the system more time and space to engage incoming missiles. MDA also set its sights on a set of longer-term objectives. These goals included a space-based sensor layer for tracking missile threats, and a GBI equipped with multiple kill vehicles that would greatly expand the capacity of the GBI fleet. While the volume kill concept had great appeal, MDA recognized the need for a developmental step between the current kill vehicles and a more advanced, unproven concept. Historically, U.S. missile defense has done best when pursuing steady, achievable goals. The highly successful Aegis Ballistic Missile Defense program, for example, has consistently adhered to the mantra: “Build a little, test a little, learn a lot.” The RKV program, however, ran into delays. Yet, rather than continue trying to fix the program, the Pentagon opted to abandon it and skip directly to a more advanced, multi-kill vehicle approach called the Next Generation Interceptor. NGI is an ambitious, 10-plus year endeavor that carries significant risk. In the near term, it means that the president's goal to add 20 more GBIs to the fleet will go unmet, as those GBIs were supposed to be capped with RKVs. Any expansion to the GBI fleet before 2030 will require the design and construction of a modernized unitary kill vehicle of some kind. Absent any effort to expand or modernize the GBI fleet, homeland missile defense will likely fall behind the North Korean missile threat while NGI matures over the next 10 years. The decline will increase U.S. vulnerability to coercion by North Korean leader Kim Jong Un at a time when the U.S. military is scrambling to address Chinese and Russian aggression. Furthermore, a major delay of NGI a decade from now (or worse, a failure for NGI to materialize at all) would leave the United States with a fleet of GBIs falling rapidly into obsolescence, squandering decades of resources and effort. To be clear, the United States should continue developing NGI. Missile threats to the U.S. homeland continue to grow at an alarming pace, in quantity and complexity. But the Pentagon and Congress should support these longer-term efforts while still investing in nearer-term options that keep U.S. homeland defenses current to North Korean missile capabilities, hedge against NGI failure and preserve U.S. investments in the GMD system. A potential path forward may lie in the Senate's version of the fiscal 2021 National Defense Authorization Act, which contains draft language that would require the deployment of 20 additional GBIs equipped with an interim, unitary kill vehicle by 2026. Three years ago, we titled our study of GMD “Missile Defense 2020” because we believed that this year would be the start of a new chapter in U.S. homeland missile defense. Obviously, much has changed with the cancellation of RKV. Yet, despite all its challenges, this year may still provide the opportunity to make the kind of decisions that will strengthen our national security in the near and long term. https://www.defensenews.com/opinion/commentary/2020/06/24/countering-missile-threats-means-addressing-the-present-while-planning-for-the-future/

Toutes les nouvelles