Story
September 10, 2026
High-criticality and Design Assurance Level (DAL)-certifiable time-sensitive networking (TSN) networks for flight-critical systems may be a few years out, as any new technology takes time to harden and then prove airworthiness to the certification authorities. But for the large number of mission systems on today’s networked platforms, TSN can bring long-awaited time awareness to Ethernet communications. TSN is a critical technology now undergoing wider adoption, holding great promise as a transformative technology for connected systems. To be successful, industry must work together to align with common specifications and use cases to ensure interoperability.
The interconnected world is incredible: People can set a home thermostat from the highway and get alerts if they accidentally leave the garage door open. They can check their bank balance from across the world and pay bills online during halftime at a World Cup match. They are confident that when they hit “save” on the laptop, the file will be uploaded to a server somewhere, in the ambiguity of the cloud, pretty much without fail. It doesn’t matter if the user is hardwired or wireless, on a laptop or mobile device, running Windows or iOS, or if the save command takes 1 second or 3 seconds or 10 seconds. It just works.
All this is due in no small part to the brilliance of the OSI [Open Systems Interconnection] seven-layer communications model standardized over 40 years ago, which masterfully abstracts the complexity of communication into “mind-your-own-business” layers, each layer doing its part in perfect isolation in harmony with its neighbors.
Yet this networked system, the worldwide Internet built around thousands of Ethernet standards, has little concept of real time. True, the networked world has developed many methods to categorize and prioritize traffic, with increased priority to those streams which carry what it deems timely data, or perhaps prioritizing traffic for those sites who pay a premium to jump to the head of the queue. But for companies that build real-time systems that cannot accept the hourglass wait icon even for a millisecond, Ethernet has always been a “best-effort” medium.
Today’s aerospace and defense platforms are incredibly complicated systems of systems. Some systems can accept the concept of best-effort communications, where message determinism is not critical. Yet some systems must have guaranteed determinism, where there is no tolerance for message delays; even a millisecond delay can cause immeasurable misfortunes. For systems intolerant of timing uncertainty, industries generally use dedicated interfaces that avoid congestion and potential timing ambiguity. These isolated interfaces may solve the problem of real-time data communications, but at a great weight and cost expense.
Consider the wiring in any modern platform – for one, the F-35 is estimated to contain roughly 17 miles of copper wiring. Much of this is for point-to-point interfaces, designed as such to ensure the determinism needed to complete tasks on time, every time.
As defense and aerospace platforms evolve toward increasingly distributed, software-defined, and sensor-rich architectures, traditional “best-effort” Ethernet is struggling to meet the timing, synchronization, and determinism requirements of modern mission systems. Applications such as sensor fusion, autonomy, mission computing, coordinated control, and artificial-intelligence (AI)-driven edge processing demand predictable communications across compute, network, and I/O resources.
Time-sensitive networking (TSN) has emerged as a promising standards-based approach for enabling deterministic Ethernet messaging while coexisting with conventional Ethernet traffic. Developed and standardized within the IEEE 802 LAN/MAN Standards body, TSN is a collection of capabilities built upon and within IEEE 802.1 Ethernet standards to bring time awareness to Ethernet systems.
While the promise of time-accurate Ethernet may sound too good to be true, TSN promises just that: guaranteed time-accurate Ethernet messaging. TSN is not a simple thing you turn on – it’s a complex collection of standards that govern how connected systems manage time and synchronization, schedule and forward packets and control latency, add data replication and manage redundancy to ensure timely reliability, and manage resources. It’s a buffet of individual capabilities, often referred to as 802.1
- 802.1Qav for Credit Based Shaping (CBS)
- 802.1Qbv for Time Aware Shaping (TAS)
- 802.1Qbu for Frame Pre-Emption
- 802.1CB for Frame Replication and Elimination for Reliability (FRER)
- 802.1Qci for Per Stream Filtering and Policing (PSFP)
Most of these separate standards have been folded into the governing IEEE 802.1Q-2022 standard update, an enormously complex 2,000+-page specification governing most things related to switched, also known as bridged, networks.
To focus TSN on various application domains, the IEEE has worked with industry to develop TSN Profiles to define which subsets of the TSN standards, along with specific configuration options within them, are most appropriate for different usage domains. Like VITA specifications, they define which standards and configurations are mandatory vs. those which may be optional. They define specific parameter ranges and configuration values most appropriate for the domain, such as synchronization and cycle time accuracy. The Profiles also define how devices should interoperate within that domain. Put simply, the TSN profiles define which TSN standards apply, specify settings, and lay out requirements for a conformant device to interoperate with other devices.
TSN profiles narrow down the unbounded freedom within these specifications to a defined subset with the goal of better compatibility between vendors, all for the benefit of a given industry, much like the Sensor Open Systems Architecture, or SOSA, and VITA 65/OpenVPX standards are to the unbounded VITA 46.
TSN profiles exist for audio/video bridging (IEEE 802.1BA) and fronthaul mobile networks (IEEE 802.1CM), with the most applicable profiles for the aerospace and defense industry the IEEE 802.1DG TSN Profile for Automotive, and the IEEE 802.1DP TSN Profile for Aerospace. While the Automotive Profile sounds appealing for ground vehicles, the A&D industry is moving to support the Aerospace Profile, even for ground platforms.
The 802.1DP Aerospace Profile working group considered applications of TSN to a range of platforms, considering characteristics such as:
- Number of nodes, switches, and communication streams
- Platform network topologies and traffic types
- Network redundancy considerations
- Data rates and media types
- Dissimilarity, integrity, and security
- Maintenance and monitoring
- Certification requirements, such as the FAA or EASA frameworks RTCA DO-254 and DO-178
Key platform types considered included small and large commercial passenger aircraft, with consideration for passenger information and entertainment domains, airline information services, and aircraft control domains; military fixed-wing and rotary-wing aircraft, with consideration for air vehicle systems and mission systems; larger military networks, focused on mission systems; uncrewed airborne platforms; and satellite networks.
To illustrate how TSN fits into a system of connected systems, consider an arbitrary platform with dozens of networked subsystems. For network traffic control and redundancy, most platforms will be architected using isolated networks, with carefully controlled subsets of systems connected together. Not all systems and nodes will carry time-critical traffic, as time-critical TSN traffic can coexist with traditional best-effort traffic.
The key to integrating TSN into such a platform is to add TSN capabilities to those systems where time-aware determinism is needed, and to ensure that all network switches connecting TSN-aware nodes are also TSN-aware. The non-TSN nodes and switches can connect anywhere, as the policing of TSN traffic is implemented within the TSN nodes. A platform can start with a small TSN subsystem and slowly build out TSN capabilities as the needs of the platform grow.
In recent years, TSN has started to appear in platform capability surveys and defense-program flowdown requirements. Regrettably, a specification requiring TSN means very little by itself – TSN is not a yes or no feature. To make use of TSN, many network nodes must work together, cooperating in a TSN-aware and configured network, designed to meet the deterministic needs of the applications hosted on the platform. In applications such as flight-control systems, TSN systems may need to be safety-certified to the highest Design Assurance Level (DAL) specification, which may involve certification authorities such as the FAA and EASA and consume considerable time and expense to achieve the required levels of certification.
With the release of the IEEE 802.1DP Aerospace Profile in November 2025, the final piece of the interoperability puzzle has been made available to industry. Suppliers that have been developing and delivering TSN-capable equipment for some time can now begin to demonstrate end-to-end TSN capabilities aligned with standards, providing systems integrators with the tools and guidance necessary to bring TSN out of the research lab and into platform system integration labs to demonstrate real-world deterministic systems operating with deployable applications.
Curtiss-Wright Defense Solutions ·
Featured Companies
