End-to-End Testing of Satcom-based Applications in Aircrafts

In the near future, we expect to see existing cockpit applications and new cockpit applications to rely on always-on connectivity via satellite. Introduction of any new process into the cockpit operation must be thoroughly tested to ensure adherence to the highest standards and safety protocols. However, while standards and guidelines set the overall safety requirements for software such as satellite enabled cockpit applications, it does not provide methodologies or any one way of attaining the desired requirements. So why should you, and how do you go about performing end-to-end testing of satcom-based applications in aircrafts?

Currently, the vast majority of cockpits are reliant on static information. Flights are planned prior to take-off and all needed information such as route plan, travel time and weather forecasts are brought into the cockpit before take-off. With satcom-enabled connectivity such information will be online available including changes and updated information from both ground and aircraft side. For example, updated weather forecasts can lead to changed travel routes. From ground it will be possible to have a 4D representation of aircraft – longitude, latitude, height and time.

However, introduction of in-flight cockpit connectivity is no trivial process. A satellite link is characterized by latency, fading and other impairments. And on top of that it is not possible to control or even reproduce a satellite connection by use of a real link (on-air) in the test setup.

A solution to this is using an emulated satellite connection like shown in the illustration where the application is connected to the server via a satellite terminal connected to a satellite network emulator. A network specific emulator can be fully controlled with regards to emulating different real-life satellite link behavior. This is important to verify robustness and user experience of an application under different conditions.