Cockpit Display System VNC Integration for Non-ARINC 661 Protocols
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current aircraft display systems face challenges in efficiently incorporating non-ARINC 661 compliant systems, such as cabin control systems, which do not require high DAL certifications, due to the stringent protocols of ARINC 661, leading to increased costs and complexity for manufacturers.
Innovation Solution
The integration of Virtual Network Computing (VNC) into Cockpit Display Systems (CDS) allows for the use of VNC clients in remote non-aircraft systems and VNC servers in CDS, enabling data exchange using both ARINC 661 and VNC protocols, facilitating the incorporation of non-ARINC 661 compliant systems without the need for high DAL certifications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If ARINC 661 protocols are used for all aircraft systems, then system reliability and safety are improved, but device complexity and manufacturing costs increase
Solution Approach 1:
The patent segments aircraft systems into two categories: critical systems requiring ARINC 661 protocols with high DAL certifications, and non-critical systems using simplified VNC protocols without DAL requirements. This segmentation allows each system type to use appropriate protocol complexity levels, reducing overall system complexity while maintaining safety for critical functions.
Solution Approach 2:
The patent introduces a protocol translation layer that acts as an intermediary between ARINC 661 and VNC protocols. This mediator enables non-ARINC 661 compliant systems to communicate with the cockpit display system using VNC, while maintaining compatibility with ARINC 661 standards where required, thus resolving the contradiction between protocol strictness and system integration flexibility.
2Reliability
If ARINC 661 protocols are used for all aircraft systems, then communication reliability is improved, but manufacturing costs increase
Solution Approach 1:
The patent applies segmentation by categorizing aircraft systems into critical and non-critical groups. Critical systems maintain ARINC 661 protocol requirements for communication reliability, while non-critical systems use cost-effective VNC protocols, thereby reducing overall manufacturing costs without compromising communication reliability for essential functions.
Solution Approach 2:
The patent changes the protocol parameter from ARINC 661 to VNC based on system criticality. This parameter change allows non-critical systems to use simpler, less expensive communication protocols while maintaining ARINC 661 for critical systems, thus reducing manufacturing costs while preserving communication reliability where needed.
3Reliability
If strict ARINC 661 protocols are implemented, then system safety is improved, but ease of operation decreases
Solution Approach 1:
The patent introduces a protocol translation intermediary that simplifies system integration by automatically handling protocol conversions between ARINC 661 and VNC. This mediator transparently manages the complexity of protocol compatibility, making system integration easier while maintaining safety standards for critical systems.
Solution Approach 2:
The patent creates a universal communication framework that supports both ARINC 661 and VNC protocols within the same cockpit display system. This multi-functional approach allows the system to operate with different protocol types depending on system requirements, improving ease of operation and integration while maintaining safety for critical functions.
Data Source
AI summary
System and methods for incorporating virtual network computing (“VNC”) into a cockpit display system (“CDS”) are disclosed. A system and method for incorporating VNC into the CDS is comprised of a non-aircraft remote system and a CDS, where the non-aircraft remote system is comprised of a VNC client and a remote display unit, and the CDS comprised of, in part, a VNC server and a PM configured with a method employing an aviation-industry standard protocol (e.g., ARINC 661) and a VNC protocol. A Second method for incorporating VNC into the CDS is comprised of a non-aircraft remote system and a CDS, where the non-aircraft remote system is comprised of a VNC server and a remote display unit, and the CDS comprised of, in part, a VNC client and a processing module (“PM”) configured with a method employing an aviation-industry standard protocol and a VNC protocol.