# US 2014/0157041 A1 · Distributed avionics system and method for backup handling in an avionics system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0157041 A1 - Document ID: US20140157041A1 - Status: Published application - Kind: A1 - Application number: 14/113,554 - Filed: 2011-05-17 - Published: 2014-06-05 - Earliest claimed: 2011-05-17 - Assignees: Saab AB - Inventors: Torkel Danielsson; Jan Håkegård; Anders Gripsborn - Web page: https://patentgrep.com/patent/US20140157041A1 ## CPC - G06F 11/2041: {with more than one idle spare processing component} - G06F 11/143: {with loss of software functionality} - G06F 11/203: {using migration} - G06F 11/2035: {without idle spare hardware} - G06F 11/2043: {where the redundant components share a common memory address space} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract The present invention relates to a distributed avionics system (100, 500) having a plurality of computer nodes arranged to execute a plurality of partitions/applications (P1, P2, P3, P4, P5, P6). The distributed avionics system comprises reconfiguration means (332) arranged to reconfigure the distributed avionics system upon detection of failure in at least one of the computer nodes. Each partition/application is associated to a application/partition availability level. The reconfiguration means are arranged to reconfigure the distributed avionics system based on the partition/application availability levels of the partition/applications (P1, P2, P3, P4, P5, P6). The present invention further relates to a method for back-up handling in a distributed avionics system having a plurality of computer nodes (A, B, C). ## Claims ### Claim at position 1 1-13. (canceled) ### Claim 14 A distributed avionics system (100, 500) having a plurality of computer nodes configured to execute a plurality of partitions/applications (P1, P2, P3, P4, P5, P6), said distributed avionics system comprising reconfiguration means (332) configured to reconfigure the distributed avionics system upon detection of failure in at least one of the computer nodes, wherein: each of the partition/applications (P1, P2, P3, P4, P5, P6) is associated to an application/partition availability level; the reconfiguration means are configured to reconfigure the distributed avionics system based on the partition/application availability levels of each of the partition/applications (P1, P2, P3, P4, P5, P6); each computer node is assigned to at least one unique role and each role comprises a subset of the partitions/applications (P1, P2, P3, P4, P5, P6); each role is associated to a role availability level defining a maximum allowable partition/application availability level to be executed in that role, the maximum allowable partition/application availability level indicating a criticality of the role; and the reconfiguration means are configured to assign the subset of partitions/applications of the role associated to the computer node in which failure has been detected to one computer node presently associated to the role having the lowest availability level. ### Claim 15 (depends on 14) A distributed avionics system according to claim 14, wherein the reconfiguration means are configured to prevent execution of the subset of partitions/applications associated to the role having the lowest availability level. ### Claim 16 (depends on 15) A distributed avionics system according to claim 15, wherein the reconfiguration means are configured to prevent execution of partitions/applications associated to the same availability level as the availability level of the role prevented from execution also in other roles. ### Claim 17 (depends on 14) A distributed avionics system according to claim 14, wherein the reconfiguration means (332) are configured to reconfigure the distributed avionics system so as to prevent partitions/applications from execution associated to a lowest partition/application availability level. ### Claim 18 (depends on 14) A distributed avionics system according to claim 14, wherein the reconfiguration means are configured to prevent the execution of partitions/applications as long as the computer node failure remains. ### Claim 19 (depends on 14) A distributed avionics system according to claim 14, wherein the reconfiguration means (332) are operatively connected to presentation means (334) configured to present information related to the failure in at least one computer node. ### Claim 20 (depends on 18) A distributed avionics system according to claim 18, wherein the presentation means (334) are configured to present information related to the availability level(s) which is/(are) presently not executed. ### Claim 21 (depends on 14) A distributed avionics system according to claim 14, the system further comprising fault detection means (331) configured to perform the detection of failure in at least one of the computer nodes. ### Claim 22 (depends on 21) A distributed avionics system according to claim 21, wherein: the fault detection means (331) further are configured to detect whether the faulty computer node is functioning again; and the reconfiguration means (332) are configured to reconfigure the faulty node upon detection that it is functioning again so as execute those partitions/applications excluded from execution during the computer node failure. ### Claim 23 (depends on 14) A distributed avionics system according to claim 14, wherein each node has access to at least all partitions/application having at least one of the same or higher partition/application availability level than the role availability level of the role to which it is associated. ### Claim 24 (depends on 23) A distributed avionics system according to claim 23, wherein each node has access to all partitions/applications. ### Claim 25 (depends on 14) A distributed avionics system according to claim 14, wherein the role availability levels and/or partition/application availability levels are represented by discrete Aircraft Capability Levels classified based on at least one of the contents or functionality of the applications/partitions. ### Claim 26 A method for back-up handling in a distributed avionics system having a plurality of computer nodes (A, B, C), said method comprising the following steps: providing a set of partitions/applications (P1, P2, P3, P4, P5, P6) to be executed by the distributed avionics system; assigning a partition/application availability level to each partition/application (P1, P2, P3, P4, P5, P6); assigning each computer node (A, B, C) to at least one unique role, wherein each role comprises a subset of the partitions/applications (P1, P2, P3, P4, P5, P6) and associating each role to a role availability level defining a maximum allowable partition/application availability level to be executed in that role, the maximum allowable partition/application availability level indicating a criticality of the role; assigning a separate subset of the partitions/applications for execution by each node based on the partition/application availability levels; monitoring operation of the computer nodes (A, B, C) so as to detect at least one fault condition in one of the computer nodes; and re-assigning the subset of partitions/applications of the role associated to the computer node in which the fault condition has been detected to that computer node presently associated to the role having the lowest availability level.