Open world communication device for communicating with avionics systems, related communication system and communication method
By intercepting and testing request states through the communication and cloning modules in the interface component, the security and complexity issues of connecting open-world communication devices with avionics systems are resolved, achieving direct secure connection and stable communication.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- THALES SA
- Filing Date
- 2021-03-16
- Publication Date
- 2026-05-01
AI Technical Summary
When existing open-world communication devices are connected to avionics systems, there are security and complexity issues. Existing systems cannot completely prevent malicious requests and require complex filtering structures.
Using interface components, including a clone of the communication module, authorization module, and avionics system, the status of each request is intercepted and tested. Only requests with a valid status are sent, and error messages or application components are blocked when a request is invalid.
It enables direct and secure connection between open-world communication equipment and avionics systems, avoids the introduction of complex structures, improves system security and stability, and reduces the risk of errors.
Smart Images
Figure CN115769288B_ABST
Abstract
Description
[0001] This invention relates to an open-world communication device.
[0002] The present invention also relates to communication systems and methods associated with open-world communication devices.
[0003] Specifically, the present invention is applicable to avionics systems with flight management systems.
[0004] In the aviation field, the flight management system, known as the "FMS (flight management system)," is an important aircraft system. Pilots can use this system to input flight data that they need to track, such as flight plans, arrival points, waypoints, etc.
[0005] Therefore, the "FMS" system can be used for flight planning, specifically to predict the flight path that the aircraft will take and all data related to that path, such as flight time and fuel consumption.
[0006] Therefore, for example, an autopilot system can control the flight path planned by the "FMS" system so as to automatically guide the aircraft to fly along the path.
[0007] The FMS system is typically connected to a display screen and input devices that allow pilots to input data into the system. The data processed by the FMS system can then be displayed on the screen and / or sent to other systems.
[0008] The “FMS” system is part of the avionics system and has a closed-world system for this purpose.
[0009] Pilots typically use other electronic devices that are not part of the closed-world system to input data into the "FMS" system; in contrast, such devices are referred to as open-world communication devices.
[0010] Specifically, this means that such open-world communication devices do not follow the same rules as devices in closed-world systems, and therefore, such open-world communication devices do not possess the same integrity and security as devices in closed-world systems.
[0011] Among the open-world communication devices available to pilots, one known specific device is an electronic flight bag (EFB).
[0012] Such devices are typically in the form of electronic tablets or other portable electronic devices, and in particular, they allow pilots to perform a series of calculations related to flight plans.
[0013] The “EFB” system can be further used to store flight process and other useful information.
[0014] To avoid any interference between open-world communication equipment and avionics systems, pilots typically manually input data from devices such as the EFB into the FMS system or, more commonly, other avionics systems.
[0015] However, to make pilots' work smoother, reduce their workload, and lower the risk of errors, there is a greater desire to be able to directly connect at least some open-world communication devices to specific avionics systems such as the FMS system.
[0016] In the existing technology, some solutions can already be used to at least partially provide connectivity between open-world communication devices and avionics systems (specifically, such as the "FMS" system).
[0017] Specifically, such solutions use numerous filtering systems to filter every request sent by open-world communication devices to the FMS system.
[0018] However, existing systems still have shortcomings because they require relatively complex structures and cannot completely prevent potential malicious requests.
[0019] The purpose of this invention is to overcome these shortcomings of existing systems and to propose an open-world communication device that provides a high level of security for direct communication with avionics systems without introducing complex structures.
[0020] Therefore, the subject of this invention is an open-world communication device for communicating with the electronic aviation systems of an aircraft, comprising application components capable of sending requests to and receiving data from the avionics systems.
[0021] The device is characterized by further including an interface component, the interface component comprising a communication module capable of intercepting each request sent by the application component and a clone of an avionics system capable of testing each request intercepted by the communication module to determine the state of the request between a qualified state and a non-qualified state.
[0022] The communication module can only send requests with a qualified status to the avionics system.
[0023] According to other advantageous aspects of the invention, the open-world communication device includes at least one of the following features, employing a single feature or all technically possible combinations thereof.
[0024] - The communication module can also send error information to the application component for each request with an unqualified status;
[0025] - The interface component further includes an authorization module, which is capable of authorizing the application component to send requests to the avionics system;
[0026] - The data transmitted by the avionics system is in the form of a data stream propagated by the avionics system, and the interface component is capable of directly sending the data stream to the application component;
[0027] -The communication module is capable of sending corresponding requests to the avionics system in encrypted form;
[0028] - The interface component is the only component of the device that connects to the avionics system;
[0029] -The interface component is in the form of an application;
[0030] - The form of the clone is a software clone of the avionics system.
[0031] - The clone will determine the requested status as unqualified if at least one of the following conditions is met:
[0032] - The number of requests sent within the predetermined time interval is incompatible with the cloning's processing capacity.
[0033] - The requested format does not match the expected format.
[0034] - Unexpected data caused during request execution
[0035] - The avionics system shall not be permitted to execute the request without endangering passengers;
[0036] - The communication module is capable of blocking the application component when at least one request sent by the application component has an invalid status;
[0037] - The device includes multiple application components, and each application component is capable of sending requests to the avionics system and receiving data from the avionics system through an interface component;
[0038] -The avionics system is a flight management system;
[0039] The present invention also relates to a communication system for an aircraft, comprising:
[0040] -Avionics systems;
[0041] - An open-world communication device that communicates with the avionics system, the device being defined above.
[0042] According to other advantageous aspects of the invention, the communication system further includes an interface for connecting the open-world communication device to the avionics system.
[0043] The present invention also relates to a method for communicating with the avionics system of an aircraft, the method being implemented by an open-world communication device as defined above;
[0044] The method includes the following steps:
[0045] - Generate requests for avionics systems;
[0046] - Intercept the request;
[0047] - Test the requests intercepted by the communication module and determine the status of the requests between a qualified state and an unqualified state;
[0048] - When the request is in a qualified state, the request will be sent to the avionics system.
[0049] The features and advantages of the present invention will become apparent upon reading the following description, which is given by way of non-limiting example only, and upon referring to the accompanying drawings, in which:
[0050] Figure 1 This is a schematic diagram of the communication system of the present invention, which specifically includes the open-world communication device of the present invention;
[0051] Figure 2 yes Figure 1 A detailed schematic diagram of the open-world communication device is shown below;
[0052] Figure 3 This is a flowchart of the communication method of the present invention, which is composed of... Figure 2 The open-world communication device shown is implemented;
[0053] Figure 4 This is an explanation Figure 3 A schematic diagram illustrating the implementation of the communication method.
[0054] Figure 1 A communication system 10 for an aircraft is shown.
[0055] Specifically, an aircraft refers to an airplane, helicopter, drone, or any other flying vehicle that is piloted at least partially by at least one pilot using the avionics system described below. This avionics system can be directly mounted on the aircraft or can be remotely controlled. In the latter case, the piloting of the aircraft is also performed remotely.
[0056] like Figure 1 As shown, the communication system 10 includes an avionics system 12, an interface 14, and an open-world communication device 16.
[0057] Specifically, the avionics system is a flight management system 12 known as the "FMS" system. The system 12 will be referred to as FMS 12 below.
[0058] Specifically, FMS 12 can be used to calculate the aircraft's trajectory starting from data input by the pilot and to predict data associated with said trajectory. Specifically, this data is input in the form of a request from open communication device 16, as will be explained below.
[0059] FMS 12 can further generate data, such as data for another avionics system, and / or the pilot, and / or open-world communications equipment 16. This data is later referred to as flight management data.
[0060] Specifically, the FMS 12 is connected to one or more displays and devices for inputting data, such as a keyboard.
[0061] In itself, FMS 12 can be doubled through another flight management system associated with another pilot.
[0062] Interface 14 can be used to connect open-world communication device 16 to FMS 12.
[0063] Interface 14 has a channel for connecting to FMS 12 via, for example, a wire, and wirelessly connects to open-world communication device 16.
[0064] In some implementations, interface 14 also has a support unit that serves as a base for open-world communication device 12.
[0065] Therefore, in this configuration, the open-world communication device 16 can be placed on the support for example for charging or connected to the FMS 12 via a wire; when the open-world communication device 16 is removed from the support, the device 16 can, for example, be wirelessly connected to the FMS 12 via a wireless data transmission protocol.
[0066] The open-world communication device 16 has, for example, a tablet computer, or other portable electronic devices such as a smartphone configured for the pilot to communicate with the FMS 12.
[0067] Generally speaking, the open-world communication device 16 may have the functionality of an electronic device known in the prior art as an "electronic flight bag" or "EFB".
[0068] Specifically, the open-world communication device 16 allows pilots to perform at least certain computation-related operations during flight planning.
[0069] The following will refer to Figure 2A more detailed description of Open World Communication Device 16 is provided.
[0070] like Figure 2 As shown, the open-world communication device 16 includes multiple application components 22-1, ..., 22-N and an interface component 24, wherein the interface component 24 enables each application component 22-1, ..., 22-N to be connected to the FMS 12 via an interface 14.
[0071] Open-world communication device 16 also includes components known in itself (not in...) Figure 2 (Displayed in the image), such as processor, memory, screen, input device, etc.
[0072] Each application component 22-1, ..., 22-N has, for example, an application stored in the memory of the open-world communication device 16, which can be used to implement at least some of the FMS12-related functions that can be used by the pilot.
[0073] Therefore, each application component 22-1, ..., 22-N can generate a request to be sent to FMS12 and can receive flight management data from FMS12.
[0074] To connect each application component 22-1, ..., 22-N to the FMS, interface component 24 includes communication module 31, authorization module 32, and clone 33 of FMS 12.
[0075] Specifically, the interface component 24 is in the form of one or more software programs, or at least in part in the form of programmable logic circuits, such as FPGA (Field Programmable Gate Array).
[0076] The communication module 31 enables the interception of each request from each application component 22-1, ..., 22-N, so that the request can be sent to clone 33.
[0077] The communication module 31 also enables requests with a valid status to be encrypted and sent to the FMS module 12.
[0078] Finally, communication module 31 enables requests with unqualified status to be rejected or sent back to the appropriate application component, which will be explained in detail below.
[0079] The authorization module 32 authorizes each application component from 22-1 to 22-N so that the application component can communicate with the interface component 24.
[0080] For this purpose, the authorization module 32 includes, for example, a database for identifying all application components authorized to communicate with FMS 12.
[0081] According to another example of the implementation scheme, the authorization module 32 is able to perform specific analysis on each application component in order to determine whether to deliver an authorization to communicate with FMS 12 to that application component.
[0082] Cloning 33 enables the autonomous replication of FMS 12. For this purpose, Cloning 33 is, for example, a software clone of FMS 12.
[0083] In other words, clone 33 can emulate the operation of FMS 12.
[0084] Additionally, clone 33 can receive each request intercepted by communication module 31 in order to determine its eligibility.
[0085] Specifically, clone 33 makes it possible to determine the state of each intercepted request between a qualified and an unqualified state.
[0086] Based on the modeling performed by clone 33, when executing a request would cause FMS 12 to function normally, the intercepted request would be associated with a qualified status.
[0087] Based on the modeling performed by clone 33, if executing a request would cause FMS 12 to malfunction or result in at least one abnormal data, the intercepted request would be associated with an unqualified status.
[0088] Specifically, a blocked request will be associated with an unqualified status if at least one of the following conditions is met:
[0089] - The number of requests sent within a predetermined time interval is incompatible with the processing capacity of clone 33;
[0090] - The format of the request does not match the expected format;
[0091] Specifically, based on the aircraft's current flight environment, request the execution of data that leads to unexpected events;
[0092] - The aircraft will not execute the flight plan to be sent to FMS 12 without endangering the passengers;
[0093] Specifically, it is clear, for example, based on the modeling performed by clone 33, that when a request causes instability in the normal operation of FMS, the request is associated with an unqualified state.
[0094] According to another example, when a request causes performance data to exceed the aircraft's capabilities, the request is also associated with a non-compliant status.
[0095] When a request is associated with an unqualified status, the communication module 31 can send the request and error information back to the application component that generated the request.
[0096] The error message may include, for example, a complete report about the request.
[0097] Open-world communication device 16 can implement the communication method of the present invention, as will be described below with reference to Figure 3 The flowchart of its steps is shown and Figure 4 The implementation of these steps will be explained.
[0098] The initial step 110 corresponds to the authorization step for the authorized application components 22-1 to 22-N to communicate with FMS 12.
[0099] Step 110 can be performed, for example, before the aircraft takes flight, during the installation of the corresponding application components, or while the application components are turned on on the open-world communication device 16.
[0100] Specifically, during the steps described above, the corresponding application component sends an authorization request to the authorization module 32.
[0101] Depending on the specific characteristics of the application component, the authorization module 32 may authorize or not authorize the application component to communicate with FMS 12.
[0102] Subsequently, it is assumed that each application component 22-1 to 22-N is authorized to communicate with FMS 12.
[0103] When an application component, such as application component 22-1, sends a request to FMS 12, subsequent step 120 is executed.
[0104] This can be done, for example, during the preparation or modification of flight plans, such as at the pilot's request.
[0105] like Figure 4 As shown, during step 120, application component 22-1 sends a corresponding request to communication module 31.
[0106] During the next step 130, the communication module 31 intercepts the request sent by the application component 22-1 and sends it to the clone 33.
[0107] During the next step 140, clone 33 determines the eligibility of the received request.
[0108] To this end, clone 33 simulates the execution of the request by FMS 12.
[0109] Clone33 then analyzes the results of the execution.
[0110] Once the execution has enabled FMS 12 to operate normally, clone 33 determines that the request is in a qualified state and sends the qualified state request to communication module 31 during step 145. In this case, during step 150, communication module 31 encrypts the information to be sent to FMS module 12 before sending it through interface 14; in other words, the request is sent to FMS 12 in encrypted form by communication module 31.
[0111] When clone 33 determines that the corresponding request has caused an FMS malfunction, for example, when one of the conditions mentioned above is met, during step 155, clone 33 sends a request with an unqualified status to communication module 31. During the next step 160, communication module 31 then sends an error message to the application component 22-1 that sent the request. This error message may be sent along with a complete report related to the corresponding request and / or error.
[0112] If appropriate, when a request has been associated with an unqualified status, the communication module will block the application component 22-1 from sending the corresponding request.
[0113] When FMS 12 executes a request with a qualified status, the system propagates flight management data in the form of a data stream, for example, received by all authorized application components. This process is, for example, performed directly and is not controlled by interface component 24.
[0114] Therefore, the present invention has several advantages:
[0115] First, this invention enables open-world communication devices, such as tablet computers, to connect to FMS securely.
[0116] This is achieved by directly integrating a clone of FMS into open-world communication devices.
[0117] Therefore, if a request sent by one of the device's application components is risky, the request will be intercepted and not sent to FMS.
[0118] Finally, the present invention does not modify the avionics world, and specifically, does not modify any component of the FMS by integrating a new set of components into an open-world communication device.
[0119] In this way, the simple and easy operations described in this invention can be performed using existing hardware components.
[0120] Of course, other implementation schemes are also possible.
[0121] Specifically, it is clear that the present invention is equally applicable to any avionics system other than FMS. In this case, a clone integrated into the open-world communication device of the present invention can replicate the operation of that avionics system. Therefore, it is evident that the foregoing description also applies to any avionics system.
Claims
1. An open-world remote communication device (16) for communicating with an avionics system (12) of an aircraft, comprising application components (22-1, ..., 22-N) capable of sending requests to the avionics system (12) and receiving data from the avionics system (12), wherein the avionics system (12) and the open-world remote communication device (16) communicate remotely; The device (16) is characterized in that it further includes an interface component (24), which includes a communication module (31) capable of intercepting each request sent by the application components (22-1, ..., 22-N) and a clone (33) of an avionics system (12) capable of testing each request intercepted by the communication module (31) to determine the state of the request between a qualified state and an unqualified state; The communication module (31) can only send requests with a valid status to the avionics system (12); The clone (33) is configured to associate the intercepted request with a qualified state when executing the request would result in the normal operation of the avionics system (12), and to associate the intercepted request with a non-qualified state when executing the request would result in the abnormal operation of the avionics system (12) or at least one abnormal result data.
2. The device (16) according to claim 1, wherein the communication module (31) is also capable of sending error information to the application components (22-1, ..., 22-N) for each request with an unqualified status.
3. The device (16) according to claim 1, wherein the interface component (24) further includes an authorization module (32) capable of authorizing the application components (22-1, ..., 22-N) to authorize the application components (22-1, ..., 22-N) to send requests to the avionics system (12).
4. The device (16) according to claim 1, wherein the data transmitted by the avionics system (12) is in the form of a data stream propagated by the avionics system (12), and the interface component (24) is capable of directly transmitting the data stream to the application components (22-1, ..., 22-N).
5. The device (16) according to claim 1, wherein the communication module (31) is capable of sending corresponding requests to the avionics system (12) in encrypted form.
6. The device (16) according to claim 1, wherein the interface component (24) is the only component of the device (16) connected to the avionics system (12).
7. The device (16) according to claim 1, wherein the interface component (24) is in the form of an application.
8. The device (16) according to claim 1, wherein the clone (33) is in the form of a software clone of the avionics system (12).
9. The device (16) according to claim 1, wherein the clone (33) determines the requested status as unqualified when at least one of the following conditions is met: - The number of requests sent within a predetermined time interval is incompatible with the processing capacity of the clone (33); - The format of the request does not match the expected format; - Data that caused unexpected errors during request execution; - The avionics system (12) shall not be permitted to execute the request without endangering passengers.
10. The device (16) according to claim 1, wherein the communication module (31) is capable of blocking the application component when at least one request sent by the application component (22-1, ..., 22-N) has an unqualified state.
11. The device (16) according to claim 1, comprising a plurality of application components (22-1, ..., 22-N), each application component (22-1, ..., 22-N) being able to send requests to the avionics system (12) and receive data from the avionics system (12) via the interface component (24).
12. The device (16) according to claim 1, wherein the avionics system (12) is a flight management system.
13. The device (16) according to claim 1, which is a device that needs to be certified by the avionics system (12).
14. The device (16) according to claim 1, including electronic flight bag functionality.
15. A communication system (10) for an aircraft, comprising: -Avionics systems (12); - An open-world remote communication device (16) that communicates with the avionics system (12), wherein the device (16) is the device (16) of any of the preceding claims.
16. The communication system (10) according to claim 15 further includes an interface (14) for connecting the open-world communication device (16) to the avionics system (12).
17. A method for communicating with an avionics system (12) of an aircraft, implemented by an open-world remote communication device (16) according to any one of claims 1-14; The method includes the following steps: - Generate (120) a request for the avionics system (12); - Intercept the request described in (130); - Test (140) the request intercepted by the communication module (31) to determine the state of the request between a qualified state and an unqualified state; - When the request is in a qualified state, the request is sent to the avionics system (12).