ACARS End System Routing via ARINC 618 Label Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Aircraft communication systems face issues where messages from one end system are not transmitted when another end system is enabled, particularly when using the same ARINC 619 origin/destination codes, affecting systems like CMC/ACMF and DFDAMU or two CMCs and electronic flight bags.
Innovation Solution
Implement a method in the communication management function (CMF) that uses internal label/sublabel mapping to differentiate between two ACARS end systems with the same ARINC 619 origin/destination codes, allowing simultaneous support without modifying the end systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the same ARINC 619 origin/destination code is used for multiple end systems, then system simplicity and standardization are improved, but message transmission reliability deteriorates because messages from one end system are not transmitted when another end system is enabled
Solution Approach 1:
The patent segments the identification system by introducing a secondary identifier (label/sublabel from ARINC 618) to distinguish between multiple end systems that share the same primary identifier (origin/destination code from ARINC 619). This segmentation allows the system to maintain unique identification for each end system while preserving the simplicity of using shared codes for communication routing.
Solution Approach 2:
The patent introduces an intermediary mapping mechanism within the communication management function that translates between the shared ARINC 619 codes and the unique ARINC 618 label/sublabel pairs. This intermediary layer resolves the conflict by maintaining the simplicity of shared codes at the communication interface while ensuring unique identification internally through the label/sublabel mapping.
2Reliability
If separate identification codes are assigned to each end system, then message transmission reliability is improved, but system complexity increases requiring modification of end systems
Solution Approach 1:
The patent makes the ARINC 618 label/sublabel mechanism serve multiple functions: it provides unique identification for each end system, enables differentiation of messages from different systems, and maintains compatibility with existing ARINC 619 communication protocols. This multi-functionality allows the system to achieve reliable message transmission without requiring separate identification codes for each end system.
Solution Approach 2:
The patent uses the existing ARINC 618 label/sublabel structure (originally designed for other purposes) as a copy or additional layer of identification that can be leveraged to solve the message routing problem. Instead of creating a new identification system, the patent repurposes the label/sublabel mechanism to provide unique end system identification while maintaining compatibility with existing protocols.
3Measurement precision
If end systems are modified to support unique identification, then message routing accuracy is improved, but ease of operation deteriorates requiring hardware or software updates
Solution Approach 1:
The patent performs the identification differentiation action preliminarily within the communication management function, before messages are routed to or from end systems. The label/sublabel mapping is established in advance in the mapping data structure, allowing the system to automatically differentiate messages based on the shared ARINC 619 codes without requiring any modifications to the end systems themselves.
Data Source
AI summary
A method comprises providing first and second end systems sharing the same A619 origin and destination codes, wherein the first end system has a first A618 label/sublabel, and the second end system has a second A618 label/sublabel different from the first label/sublabel. When an uplink message is an A618 uplink with the first label/sublabel, the method sends an A619 uplink with A619 destination code via a first end system port. If an uplink message is an A618 uplink with the second label/sublabel, the method sends an A619 uplink with A619 destination code via a second end system port. When downlink message is received with the A619 origin code on the first end system port, the method sends an A618 downlink with the first label/sublabel. If downlink message is received with the A619 origin code on the second end system port, the method sends an A618 downlink with the second label/sublabel.