# US 10,319,240 B2 · Open architecture for flight management system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,319,240 B2 - Document ID: US10319240B2 - Status: Granted - Kind: B2 - Application number: 15/389,216 - Filed: 2016-12-22 - Published: 2017-06-29 - Granted: 2019-06-11 - Earliest claimed: 2015-12-23 - Assignees: Thales - Applicants: Thales - Inventors: Julien Beernaert - Web page: https://patentgrep.com/patent/US10319240B2 ## CPC - G08G 5/30: Flight plan management - B64D 45/00: Aircraft indicators or protectors not otherwise provided for - B64F 5/60: Testing or inspecting aircraft components or systems - G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database} - G08G 5/20: Arrangements for acquiring, generating, sharing or displaying traffic information (arrangements for monitoring traffic G08G5/72) - G08G 5/50: Navigation or guidance aids - G08G 5/55: for a single aircraft - G08G 5/70: Arrangements for monitoring traffic-related situations or conditions - B64D 2045/0075: {Adaptations for use of electronic flight bags in aircraft; Supports therefor in the cockpit} - G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93}) - B64D: EQUIPMENT FOR FITTING IN OR TO AIRCRAFT; FLIGHT SUITS; PARACHUTES; ARRANGEMENT OR MOUNTING OF POWER PLANTS OR PROPULSION TRANSMISSIONS IN AIRCRAFT - B64F: GROUND OR AIRCRAFT-CARRIER-DECK INSTALLATIONS SPECIALLY ADAPTED FOR USE IN CONNECTION WITH AIRCRAFT; DESIGNING, MANUFACTURING, ASSEMBLING, CLEANING, MAINTAINING OR REPAIRING AIRCRAFT, NOT OTHERWISE PROVIDED FOR; HANDLING, TRANSPORTING, TESTING OR INSPECTING AIRCRAFT COMPONENTS, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A method for managing avionic data between a flight management system FMS and one or more clients, the FMS comprising resources accessible through avionic services Ci (1,n); the execution of the Ci (1,n) determining an avionic functionality Fj (1,m); each of the Fj (1,m) associated with an intrusiveness parameter Ik and a criticality parameter Ck; the method comprises the steps of receiving a request specifying the call to an Fj (1,m); and determining a predefined execution right for a Ci (1,n), dependent on the predefined intrusiveness and/or criticality parameters associated with the Fj (1,m). Developments describe particularly the comparison of the execution rights, notice of a rejection, various avionic services and functionalities, the management of criticality ranges, consideration of the flight context, etc. Software and system aspects are described (e.g. equipment of EFB type). ## Claims ### Claim 1 A method for managing avionic data between a flight management system FMS and one or more clients of said the flight management system FMS, the flight management system FMS comprising physical resources accessible through one or more avionic services Ci (1,n); an execution of one or more avionic services Ci (1,n) determining an avionic functionality Fj (1,m); each avionic functionality Fj (1,m) being associated with an intrusiveness parameter Ik and a criticality parameter Ck; the method comprising the steps of: receiving a request from a client, said request specifying a call to an avionic functionality Fj (1,m); determining a parameter associated with a predefined execution right for an avionic service Ci (1,n), said parameter being dependent on at least one of the following: a predefined intrusiveness and criticality parameters associated with said avionic functionality Fj (1,m); and comparing the determined execution right parameter with one or more predefined execution rights, wherein an avionic service corresponds to an avionic service comprising at least one of the following: an avionic service for accessing an information system of a functional core of the FMS, an avionic service for flight plan management or administration, and an avionic service for accessing data of a flight plan or of a trajectory of an aircraft; wherein a level of criticality being selected from among a plurality of predefined criticality ranges; wherein the plurality of predefined criticality ranges comprising four predefined criticality ranges, which comprise a level of criticality X1 strictly higher than a level of criticality of the functional core FMS, a level of criticality X2 equal to the level of criticality of the functional core FMS, a level of criticality X3 strictly lower than the level of criticality of the functional core FMS, and a level of criticality X4 much lower than the level of criticality of the functional core FMS; and wherein one or more intrusiveness or criticality parameters being dependent on a flight context. ### Claim 2 (depends on 1) The method as claimed in claim 1, further comprising a step of executing one or more avionic services and communicating a result to the client. ### Claim 3 (depends on 1) The method as claimed in claim 1, further comprising a step of notifying the client of a rejection of its request. ### Claim 4 (depends on 1) The method as claimed in claim 1, wherein an avionic functionality being selected from among the avionic functionalities comprising at least one of the following: a man/machine interface functionality F1, an automatic aircraft guidance functionality F2, a flight and trajectory surveillance and monitoring functionality F3, an air traffic and operational control centers contact functionality F4, a strategic decision making or flight optimization tool functionality F5, a flight simulation functionality F6, a maintenance and operational preparation functionality F7, a ground & flight development functionality F8, and a failure analysis and flight recorder functionality F9. ### Claim 5 (depends on 1) The method as claimed in claim 1, wherein an avionic functionality being executed according to a predefined avionic interaction model, the predefined avionic interaction model being chosen from among the interaction models comprising at least one of the following: a man/machine interaction model, an interaction model comprising automatic aircraft guidance, an interaction model comprising onboard surveillance, an interaction model known as ATM/Airlines Operation Center, and an interaction model known as Simulation/Maintenance/Development/Failure Analysis. ### Claim 6 (depends on 1) The method as claimed in claim 1, wherein the intrusiveness and the criticality parameters are configurable. ### Claim 7 (depends on 1) The method as claimed in claim 1, wherein one or more intrusiveness and criticality parameters are dependent on a flight context. ### Claim 8 A non-transitory computer program product, said computer program comprising code instructions for execution on a computer, the code instructions comprising: receiving a request from a client, said request specifying a call to an avionic functionality Fj (1,m); determining a parameter associated with a predefined execution right for an avionic service Ci (1,n), said parameter being dependent on at least one of the following: a predefined intrusiveness and criticality parameters associated with said avionic functionality Fj (1,m); and comparing the determined execution right parameter with one or more predefined execution rights, wherein an avionic service corresponds to an avionic service comprising at least one of the following: an avionic service for accessing an information system of a functional core of a FMS, an avionic service for flight plan management or administration, and an avionic service for accessing data of a flight plan or of a trajectory of an aircraft; wherein a level of criticality being selected from among a plurality of predefined criticality ranges; wherein the plurality of predefined criticality ranges comprising four predefined criticality ranges, which comprise a level of criticality X1 strictly higher than a level of criticality of the functional core FMS, a level of criticality X2 equal to the level of criticality of the functional core FMS, a level of criticality X3 strictly lower than the level of criticality of the functional core FMS, and a level of criticality X4 much lower than the level of criticality of the functional core FMS; and wherein one or more intrusiveness or criticality parameters being dependent on a flight context. ### Claim 9 A system comprising: the system being configured to receive a request from a client, said request specifying a call to an avionic functionality Fj (1,m); the system being configured to determine a parameter associated with a predefined execution right for an avionic service Ci (1,n), said parameter being dependent on at least one of the following: a predefined intrusiveness and criticality parameters associated with said avionic functionality Fj (1,m); and the system being configured to compare the determined execution right parameter with one or more predefined execution rights, wherein an avionic service corresponds to an avionic service comprising at least one of the following: an avionic service for accessing an information system of a functional core of a FMS, an avionic service for flight plan management or administration, and an avionic service for accessing data of a flight plan or of a trajectory of an aircraft; wherein a level of criticality being selected from among a plurality of predefined criticality ranges; wherein the plurality of predefined criticality ranges comprising four predefined criticality ranges, which comprise a level of criticality X1 strictly higher than a level of criticality of the functional core FMS, a level of criticality X2 equal to the level of criticality of the functional core FMS, a level of criticality X3 strictly lower than the level of criticality of the functional core FMS, and a level of criticality X4 much lower than the level of criticality of the functional core FMS; and wherein one or more intrusiveness or criticality parameters being dependent on a flight context. ### Claim 10 (depends on 9) The system as claimed in claim 9 wherein the system comprises a flight management system FMS and one or more clients of said flight management system FMS. ### Claim 11 (depends on 9) The system as claimed in claim 9, wherein the system comprises at least one electronic flight bag of EFB type.