Computing unit for flight control system of aircraft, computing platform for aircraft and aircraft

Abstract

The invention relates to a computing unit for a flight control system of an aircraft, a computing platform for an aircraft and an aircraft. The top layer (401) includes a first group (4011) of one or more partitions that perform a flight control function and a first scheduler (4013) that schedules the partitions of the first group. The intermediate layer (402) comprises: an input / output management module (4022) providing access to the at least one interface (404) of the aircraft to the partitions of the first group; a communication module (4021) for the partitions of the first group; and a second scheduler (4020) that manages delays of data streams exchanged between the partitions of the first group on the one hand and the input / output management module (4022) and the first communication module (4021) on the other hand. Thus, the proposed architecture enables operation with multiple partitions. Furthermore, the proposed architecture is versatile and does not require adjustment to each new aircraft item.

Description

Technical Field

[0001] The field of the present invention is aircraft flight control systems (FCS), sometimes also called flight command systems.

[0002] More precisely, the invention relates to a computing unit for such a flight control system. The invention also relates to a computing platform for such a flight control system, the computing platform comprising a pair of computing units. Background Art

[0003] An aircraft's flight control system typically includes a plurality of computing units, also called “flight control computers” or “flight command computers” (FCC), which are avionics computers, present and executed on a plurality of computing platforms.

[0004] In a first known architecture, a computing platform includes a pair of computing units, commonly referred to as COM and MON (for command and monitor, respectively), a first computing unit (computing unit COM) acting in command mode, and a second computing unit (computing unit MON) acting in monitor mode, thereby monitoring the first computing unit.

[0005] In a second known architecture, the computing platform comprises a single computing unit. The computing platforms are distributed in COM / MON pairs, with a first computing platform (computing platform COM) functioning in command mode and a second computing platform (computing platform MON) functioning in monitor mode, thereby monitoring the first computing platform.

[0006] The present invention is particularly applicable to the two known architectures mentioned above.

[0007] Computing units can communicate with each other. More precisely, there is communication between computing units hosted by the same computing platform, as well as between computing units hosted by different computing platforms. To this end, an aircraft includes one or more communication networks, for which various standards exist (e.g., ARINC 664 Part 7 (AFDX), Ethernet, ARINC 429 (often abbreviated as A429), etc.).

[0008] Typically, each computing unit comprises a single partition. The computing unit implements flight control functions (also referred to as "avionics software functions"), for example, to command actuators of control surfaces. The computing unit comprises control loops. In one particular implementation, the computing platform also provides synchronization services for synchronization between computing units hosted by the computing platform.

[0009] In summary, a flight control system (FCS) of an aircraft generally includes one or more computing platforms (FCCs), each of which includes one or more computing units that perform flight control functions.

[0010] In the prior art, each flight control system computing platform (FCC) is a dedicated product for a specific aircraft program. For each new aircraft project, multiple operations are currently required:

[0011] - Redevelopment of each flight control system computing platform (FCC) with a dedicated team;

[0012] - Implement new specialized verification and monitoring activities;

[0013] - Execute new dedicated certification activities;

[0014] - Update different strategies;

[0015] -Design-specific specifications;

[0016] -etc.

[0017] It is desirable to provide a solution that makes it possible to facilitate the design of a computing platform (FCC) of a flight control system while avoiding or limiting the above-mentioned operations for each new aircraft procedure.

[0018] It is also expected that the provided solution may facilitate certain flight control functions and certain control loops in terms of execution. Summary of the Invention

[0019] An object of the present invention is to propose a computing unit for a flight control system of an aircraft, the computing unit comprising:

[0020] - A top layer, which contains:

[0021] * a first set of partitions, the first set of partitions including partitions each associated with a first priority and

[0022] partitions each performing at least one first flight control function; and

[0023] * A first scheduler that schedules partitions of the first group. Each of the first group

[0024] The partition is repeated by the first scheduler at a first frequency; and

[0025] - an intermediate layer, the intermediate layer comprising:

[0026] * Input / output management module, which provides

[0027] providing access to at least one interface of the aircraft;

[0028] a first inter-partition communication module enabling each partition of the first group to be associated with a first priority via a first dedicated communication channel or via at least one first communication network of the aircraft and included in another computing unit of the aircraft

[0029] at least one other partition of the communication; and

[0030] * A second scheduler that manages delays in data flows exchanged between the partitions of the first group on the one hand and the input / output management module and the first inter-partition communication module on the other hand.

[0031] Thus, the proposed architecture, comprising a top layer (including a first set of partitions and a first scheduler) and a middle layer (including an input / output management module, a first inter-partition communication module, and a second scheduler), enables operation using multiple partitions ("multi-partition operation"), wherein the multiple partitions of the first set are executed in parallel. Furthermore, the proposed architecture is versatile and requires little to no adjustments in the design of the computing platform (and the computing units contained therein) to accommodate each new aircraft program. Consequently, the design of a flight control system computing platform (FCC) can be facilitated while avoiding or limiting the aforementioned operations of the prior art.

[0032] According to a particular embodiment, the top layer further comprises:

[0033] * a second set of partitions, the second set of partitions including partitions each associated with a second priority level higher than the first priority level and each performing at least one second flight control function; and

[0034] * a third scheduler that schedules the partitions of the second group, each partition of the second group being repeated by the second scheduler at a second frequency that is higher than the first frequency of repetition of each partition of the first group;

[0035] The middle layer also includes:

[0036] * a second inter-partition communication module enabling each partition of the second group to communicate with at least one other partition associated with a second priority level and contained in another computing unit of the aircraft via a second dedicated communication channel or via at least one second communication network of the aircraft;

[0037] The input / output management module further provides access to the at least one interface of the aircraft to the partitions of the second group,

[0038] Furthermore, the second scheduler manages delays of data flows exchanged between the partitions of the second group on the one hand and the input / output management module and the second inter-partition communication module on the other hand.

[0039] According to a particular embodiment, the first scheduler and the second scheduler are synchronized with each other.

[0040] According to a particular embodiment, the first scheduler and the third scheduler are synchronized with each other.

[0041] According to a specific embodiment, the input / output management module comprises:

[0042] * a first input / output management submodule that provides a first access to the at least one interface of the aircraft to a partition of the first group; and

[0043] * A second input / output management submodule providing a second access to the at least one interface of the aircraft to partitions of the second group.

[0044] According to a particular embodiment, at least some of the first and second groups of partitions comprise at least one control loop, each control loop benefiting from the first or second frequency of repetition of the partition containing said control loop.

[0045] According to a particular embodiment, the input / output management module or top layer comprises at least one first other control loop having access to said at least one interface of the aircraft, said at least one first other control loop repeating at a third frequency higher than the second frequency and capable of communicating with the partitions of the second group.

[0046] According to a particular embodiment, the input / output management module comprises at least one second further control loop repeating at a fourth frequency higher than the third frequency. Furthermore, said at least one first further control loop accesses said at least one interface of the aircraft via said at least one second further control loop.

[0047] According to a specific embodiment, each partition associated with the first priority level is a partition of the first type, referred to as a user partition, or a partition of the second type, referred to as a system partition, the partition of the second type corresponding to at least one service provided to the partition of the first type. In addition, each partition associated with the second priority level is a partition of the first type.

[0048] According to a specific embodiment, the top layer is configured to provide an inter-partition communication service, thereby enabling partitions of a first group to communicate with partitions of a second group via at least one memory interface.

[0049] A computing platform for an aircraft is also proposed, comprising a pair of computing units, such as a pair of computing units outlined above (in any of their embodiments), a first of the two computing units acting in a command mode, and a second of the two computing units acting in a monitoring mode, thereby monitoring the first computing unit.

[0050] Also proposed is an aircraft comprising a flight control system comprising at least two computing units, such as at least two computing units outlined above (in any of their embodiments).

[0051] According to a particular embodiment, the flight control system comprises at least two computing platforms, such as at least two computing platforms outlined above. Furthermore, partitions of a first group of computing units of the at least two platforms communicate with each other via a first communication service of said computing units. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The above and other features of the present invention will become more apparent upon reading the following description of at least one exemplary embodiment, which is given with reference to the accompanying drawings, in which:

[0053] Figure 1 schematically illustrates a side view of an aircraft equipped with a flight control system;

[0054] Figure 2 schematically illustrates a flight control system in one embodiment;

[0055] Figure 3 schematically illustrates one example of a hardware architecture for a computing platform included in a flight control system in one embodiment;

[0056] Figure 4 Schematically illustrates a computing unit included in a computing platform in a first embodiment;

[0057] Figure 5 schematically illustrates a module included in an intermediate layer of a computing unit and providing a first inter-partition communication service according to one embodiment;

[0058] Figure 6 Schematically illustrates a module included in a middle layer of a computing unit and providing input / output management services according to one embodiment;

[0059] Figure 7 Schematically illustrating a module included in an intermediate layer of a computing unit and providing a second inter-partition communication service according to one embodiment;

[0060] Figure 8 schematically illustrates a computing unit included in a computing platform in a second embodiment; and

[0061] Figure 9 A computing unit included in a computing platform in a third embodiment is schematically illustrated. DETAILED DESCRIPTION

[0062] Figure 1 The diagram schematically illustrates a side view of an aircraft 100 equipped with a flight control system (FCS) 101. The flight control system 101 is a type of onboard electronic equipment. For example, the flight control system 101 forms part of the electronic circuitry of the aircraft 100's avionics equipment.

[0063] exist Figure 2 FIG2 schematically illustrates a flight control system 101, which in this embodiment includes N computing platforms, labeled 202-1 to 202-N. Each computing platform includes a pair of computing units (dual unit mode): one computing unit, called COM (for command) and labeled 203-A, functions in command mode, while the other computing unit, called MON (for monitoring) and labeled 203-B, functions in monitoring mode, thereby monitoring computing unit COM. Computing units of the same platform can communicate firstly with each other, as illustrated by the arrows labeled 204, and secondly with computing units of other platforms, as illustrated by the arrows labeled 205 and 206.

[0064] It will be noted that the present invention is also applicable to the case where the flight control system 101 comprises a single computing platform (single unit mode).

[0065] It will also be noted that the present invention is also applicable to the case where each computing platform comprises a single computing unit.In this case, the computing platforms (and therefore the computing units) can be distributed into COM / MON pairs.

[0066] Figure 3 The diagram schematically illustrates a computing platform (generally designated 202 and corresponding to a computer system) included in the flight control system 101 in one embodiment. Figure 2 An example of a hardware architecture of one of platforms 202-1 to 202-N.

[0067] In this embodiment, the computing platform 202 includes the following connected via a communication bus 310: a processor or CPU (central processing unit) 301; a random access memory (RAM) 302; a read-only memory (ROM) 303, such as flash memory; a data storage device, such as a hard disk drive (HDD) or a storage media reader, such as a secure digital (SD) card reader 304; and at least one communication interface 305 that enables the computing platform 202 to interact in the avionics equipment of the aircraft 100.

[0068] The processor 301 is capable of executing instructions loaded into the RAM 302 from the ROM 303, an external memory (not shown), a storage medium such as an SD card, or a communication network (not shown). When the computing platform 202 is powered on, the processor 301 is capable of reading instructions from the RAM 302 and executing them. These instructions form a computer program that causes the processor 301 to implement the behaviors described herein. In one variant, the instructions are executed directly from the ROM 303.

[0069] Thus, all or some of the behaviors described herein may be implemented in software by executing a set of instructions using a programmable machine, such as a digital signal processor (DSP) or a microcontroller, or may be implemented in hardware by a machine or a dedicated component (chip) or a dedicated set of components (chipset), such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). In general, the computing platform 202 includes electronic circuits designed and configured to implement the behaviors described herein.

[0070] Figure 4 The diagram schematically illustrates a computing unit (generally designated 203 and corresponding to the computing platform 202) included in a first embodiment. Figure 2 One of the computing units 203-A (COM) and 203-B (MON)).

[0071] The computing unit 203 includes a top layer 401 and a middle layer 402 .

[0072] The top layer 401 includes partitions that perform flight control functions (avionics software functions) and include control loops. More specifically, in the illustrated embodiment, the top layer includes two groups of partitions 4011 and 4012. Each partition in the first group 4011 is associated with a first priority and performs at least one first flight control function. Each partition in the second group 4012 is associated with a second priority that is higher than the first priority and performs at least one second flight control function.

[0073] In the illustrated embodiment, the first group 4011 includes two subsets of partitions. The first subset includes a first type of partition 4011a, referred to as a user partition PU (also known as an "application partition" or "aircraft partition"). The second subset includes a second type of partition 4011b, referred to as a system partition PS. The system partition PS corresponds to services provided to the user partition PU. For example, data loading is a service provided to the user partition. In the illustrated embodiment, each partition 4012a of the second group 4012 is a user partition PU.

[0074] In the illustrated embodiment, the top layer 401 is configured to provide inter-partition communication services (illustrated by the arrow labeled 413), thereby enabling one or more partitions of the first group 4011 to communicate with one or more partitions of the second group 4012, for example via at least one memory interface.

[0075] In a variant not shown, the top layer includes one or more additional groups of partitions (e.g., a third group of partitions). Each additional group includes partitions associated with the same priority that is different from the priorities associated with partitions of other groups (e.g., the first and second groups).

[0076] The top layer 401 also includes two schedulers. One, designated "Scheduler A" and labeled 4013, schedules the first group of partitions. These include, for example, the primary flight control system (PFCS), the secondary flight control system (high lift system (HLS)), the autopilot system (auto flight system (AFS)), etc. Another, designated "Scheduler B" and labeled 4014, schedules the second group of partitions. These include, for example, functions for servo-controlling control surfaces and monitoring critical components.

[0077] Each partition of the first group 4011 is repeated by scheduler A 4013 at a first frequency F1. Each partition of the second group 4012 is repeated by scheduler B 4014 at a second frequency F2 that is higher than the first frequency. In some specific implementations, the first frequency F1 is less than or equal to 200 Hz, and the second frequency F2 is between 500 Hz and 2 kHz. For example, F1 = 200 Hz and F2 = 1 kHz.

[0078] Thus, partition 4012a of second group 4012 is advantageous in terms of performance over partitions 4011a and 4011b of first group 4011 because second frequency F2 is higher than first frequency F1. The fact that the partitions of the second group are advantageous means that the flight control functions and control loops contained in these partitions of the second group are advantageous. The partitions of the second group can be referred to as "fast partitions" compared to the partitions of the first group, which can be referred to as "slow partitions." Similarly, the control loops contained in the fast partitions can be referred to as "fast control loops," and the control loops contained in the slow partitions can be referred to as "slow control loops." In other words, the performance (particularly end-to-end latency) of fast partition 4012a and the fast control loops is improved compared to the performance of slow partitions 4011a and 4011b and the slow control loops.

[0079] The middle layer 402 includes multiple entities: another scheduler (labeled as 4020 and called "scheduler C"), an input / output management module (illustrated by a module labeled as 4022 and called "I / O manager"), a first inter-partition communication module (illustrated by a module labeled as 4021 and called "SC1"), and a second inter-partition communication module (illustrated by a module labeled as 4021 and called "SC2").

[0080] The middle layer 402 is also configured to perform one or more types of synchronization. Intra-computing unit synchronization corresponds to the real-time clock (RTC) of the platform hosting the computing unit. Intra-computing unit synchronization is useful for ensuring that critical interfaces of the aircraft (e.g., flight control sensors) are acquired with proven latency. Inter-computing unit synchronization corresponds to synchronization between partitions of a pair of computing units (COM / MON) hosted by the same computing platform (dual-unit mode). In the case where each computing platform includes a single computing unit (single-unit mode), inter-computing unit synchronization is not managed.

[0081] Input / output management module 4022 provides access to at least one interface 404 of the aircraft to the first group 4011 and the second group 4012 of partitions. This is illustrated by arrows labeled 407 and 411 for the first group 4011 of partitions, and arrows labeled 408 and 411 for the second group 4012 of partitions. Aircraft interfaces 404 correspond, for example, to the global physical interfaces of the aircraft and specifically include analog sensors (which provide data) and control surface actuators (which receive commands), accessible via at least one bus or network (e.g., an ARINC 429 bus, a CAN bus, discrete signals, analog signals, etc.). Preferably, for analog sensors, input / output management service 4022 is configured to manage the sensors with proven latency, thereby ensuring access and partitioning policies (access to the sensors may be private (dedicated to one partition) or shared between partitions). Also, preferably, for actuators and commands (actuator commands, sensor actuations, switch commands, etc.), the input / output management service 4022 is configured to manage strong partitions and commands with proven latency (commands cannot be shared between multiple partitions).

[0082] The first inter-partition communication module 4021 enables each partition of the first group 4011 to communicate via a first dedicated communication channel or via at least one first communication network 403 of the aircraft (as illustrated by the arrows labeled 406 and 410) with at least one other partition associated with the first priority level and contained in another computing unit of the aircraft. This other computing unit is present on the same computing platform as the computing unit 203 in question (as illustrated by the arrows labeled 406 and 410). Figure 2 ), or on another computing platform (as illustrated by the arrow labeled 204 in FIG. Figure 2 In case of shared access to the first communication network 403, the first communication service 4021 manages the access policy (bandwidth allocation, partitioning, data integrity, etc.).

[0083] With the help of the first communication module 4021 implemented in each of the computing units of one or more computing platforms, all slow partitions among the slow partitions of various computing units (that is, those partitions associated with the first priority) are able to communicate with each other via intra-computing platform communication (in the case of communication between two slow partitions contained in two computing units (e.g., 203-A and 203-B) hosted by the same computing platform (e.g., 202-1)), or via inter-computing platform communication (in the case of communication between two slow partitions contained in two computing units hosted by two different computing platforms (e.g., 202-1 and 202-2)).

[0084] The second inter-partition communication module 4023 enables each partition of the second group 4012 to communicate via a second dedicated communication channel or via at least one second communication network 405 of the aircraft (as illustrated by the arrows labeled 409 and 412) with at least one other partition associated with a second priority level and contained in another computing unit of the aircraft. This other computing unit is present on the same computing platform as the computing unit 203 in question (illustrated by Figure 2 ), or on another computing platform (as illustrated by the arrow labeled 204 in FIG. Figure 2 In case of shared access to the second communication network 405, the second communication module 4023 manages the access policy (bandwidth allocation, partitioning, data integrity, etc.).

[0085] With the help of the second communication module 4023 implemented in each computing unit of one or more computing platforms, all partitions in the partition associated with the second priority (fast partition) can communicate with each other via intra-computing platform communication or via inter-computing platform communication.

[0086] Scheduler C (4020) manages the latency of various data flows from or to the partitions (that is, guarantees the latency of information received and sent by the first group 4011 and the second group 4012 of partitions), for example:

[0087] - data flows exchanged between the partitions of the first group 4011 and the input / output management module 4022;

[0088] - data flows exchanged between the partitions of the first group 4011 and the first inter-partition communication module 4021;

[0089] - data flows exchanged between the partitions of the second group 4012 and the input / output management module 4022; and

[0090] - Data flows exchanged between the partitions of the second group 4012 and the second inter-partition communication module 4023.

[0091] In some implementations, the scheduler C includes multiple sub-schedulers, each of which manages one or more types of flows. Figure 4 In the implementation illustrated in the figure, sub-scheduler C1 manages the delay of data flows exchanged between partitions of the first group 4011 and the first communication module 4021, sub-scheduler C2 manages the delay of data flows exchanged between partitions of the first group 4011 and the second group 4012 and the input / output management module 4022, and sub-scheduler C3 manages the delay of data flows exchanged between partitions of the second group 4012 and the second communication module 4023.

[0092] In one particular implementation, the sub-scheduler C2 itself includes multiple sub-schedulers C2a, C2b, etc. (see, for example, below) depending on the number of aircraft 100 and interfaces 404 to be managed. Figure 8 In this case, sub-schedulers C2a, C2b, etc. are synchronized with each other.

[0093] Since the three schedulers A, B, and C (4013, 4014, and 4020) are independent, there are some implementations in which one or more additional mechanisms are put in place to ensure communication between the main entities (the first group of partitions 4011, the second group of partitions 4012, the first communication module 4021, the input / output management module 4022, and the second communication module 4023). These are, for example, one or more of the following mechanisms:

[0094] - The base clocks of schedulers A, B, and C are stable over time;

[0095] - Robust time partitioning on interfaces of primary entities’ environments;

[0096] The partitions of the first group 4011 and the second group 4012 and the input / output management module 4022 have digital filters to prevent aliasing;

[0097] - In COM / MON implementation (see Figure 2 ), scheduler A (and accordingly scheduler B) of the top layer 401 of computing unit 203-A is synchronized with scheduler A (and accordingly scheduler B) of the top layer 401 of computing unit 203-B;

[0098] - Schedulers A and B of the top layer 401 are synchronized with each other (while remaining independent of scheduler C of the middle layer 402 or not);

[0099] - Each of schedulers A and B of the top layer 401 is synchronized with scheduler C of the middle layer 402;

[0100] -etc.

[0101] Figure 5 An exemplary embodiment of a communication module 4021 is schematically illustrated, which is included in the middle layer 402 of the computing unit 202 and provides an inter-partition communication service for communication between slow partitions.

[0102] The module 4021 itself includes a “Network Server” module 501 (also called “NTW_SERVER”) and a “Switch” module 502 .

[0103] The "Network Server" module 501 enables the first group 4011 of slow partitions to:

[0104] - accessing a slow partition of another computing unit hosted by the same computing platform as the one hosting the described computing unit 203 via a first type of connection (represented by the arrow labeled 503; for example, an ARINC 429 bus or an RS 485 bus for communicating with high latency, low bandwidth, and no configuration (point-to-point)); or

[0105] - Accessing a slow partition hosted by another platform via a second type of connection (represented by the arrow labeled 504; such as an AFDX network or a general Ethernet network with the capability to provide configuration, low latency and high bandwidth).

[0106] The “Switch” module 502 is configured to extend the connectivity capabilities of the “Network Server” module (a switch with improved characteristics in handling high quality of service (High QoS) with medium latency and medium bandwidth) and enables the slow partitions of the first group 4011 to:

[0107] - accessing a slow partition of another compute unit hosted by the same compute platform as the one hosting the described compute unit via a third type of connection (represented by the arrow labeled 505 and more efficient than the first type of connection represented by the arrow labeled 503); or

[0108] - Accessing a slow partition hosted by another platform via a fourth type of connection (represented by the arrow labeled 506 and more efficient than the second type of connection represented by the arrow labeled 504).

[0109] Figure 6 An exemplary embodiment of an input / output management module 4022 included in the middle layer 402 of the computing unit is schematically illustrated.

[0110] Module 4022 itself includes:

[0111] - an "I / O Server" module 601 (also called "IO Server"), which provides access to one or more interfaces 404 of the aircraft to a first group 4011 and a second group 4012 of partitions (which are illustrated by the arrows labeled 407, 605 and 606 for the first group 4011 of partitions and by the arrows labeled 408, 605 and 606 for the second group 4012 of partitions). The "I / O Server" module 601 is able to manage the various interfaces 404 by ensuring latency (proven latency) and time consistency between the interfaces. The "I / O Server" module 601 is also able to customize the pre-processing process in order to provide a configuration suitable for the aircraft program in question. The "I / O Server" module 601 partitions the input / output based on (slow and fast) user partitions;

[0112] - A "very fast loop" module 602 (also called VFL), the "very fast loop" module 602 is a control loop (at least one) of the interface 404 for accessing the aircraft, which is repeated by the dispatch service 4020 at a third frequency F3 higher than the second frequency F2 (for example, F2=1 kHz and F3=16 kHz) and which is able to communicate with the partitions of the second group 4012. The "very fast loop" module 602 is suitable for high-speed aircraft. It is proposed that this increase in execution frequency makes it possible to reduce delays and increase the bandwidth of commands. These characteristics define the performance of the aircraft. The very fast loop is designed on the basis of the actuators (electrical interfaces) of the aircraft and is fixed. In a variant embodiment, the module 602 is included in the top layer 401, for example in the module 4012 comprising the second group of partitions;

[0113] a "Control Loop" module 603 (also called "CTRL LOOP"), which is a control loop repeated by the dispatch service 4020 at a fourth frequency F4 higher than the third frequency F3 (e.g., F3 = 16 kHz and F4 = 64 kHz). The "Very Fast Loop" module 602 accesses the aircraft's interface 404 via the "Control Loop" module 603 (see arrow marked 607). The "Control Loop" 603 is an analog control loop that manages, for example, the position, velocity, and acceleration of the actuators; and

[0114] A “Fieldbus Controller” module 604 (also called “FB CTRL”) making it possible to manage the remote interface 404 (see arrow referenced 608 ) via a management fieldbus, for example a MIL-STD-1553 bus.

[0115] Figure 7An exemplary embodiment of a communication module 4023 is schematically illustrated, which is included in the middle layer 402 of the computing unit 202 and provides an inter-partition communication service for fast communication between partitions.

[0116] The communication module 4023 itself comprises an “FCOM controller” module 701 and a “switch” module 702. The “FCOM controller” module 701 is designed to have better performance than the “network server” module 501 and is therefore able to meet the needs of the fast partitions of the second group 4012 and therefore of the fast control loops contained in these fast partitions.

[0117] The "FCOM Controller" module 701 enables the fast partitions of the second group 4012 to:

[0118] - accessing, via a fifth type of connection (represented by the arrow labeled 703), a fast partition of another computing unit hosted by the same computing platform as the computing platform hosting the described computing unit 203; or

[0119] - Via a sixth type of connection (represented by the arrow labeled 704), accessing a quick partition hosted by another platform.

[0120] The “Switch” module 702 is configured to extend the connectivity capabilities of the “FCOM Controller” module 701 and enable the second set 4012 of fast partitions to:

[0121] - accessing a fast partition of another compute unit hosted by the same compute platform as the one hosting the described compute unit via a seventh type of connection (represented by the arrow labeled 705 and more efficient than the fifth type of connection represented by the arrow labeled 703); or

[0122] - Accessing a slow partition hosted by another platform via an eighth type of connection (represented by the arrow labeled 706 and more efficient than the sixth type of connection represented by the arrow labeled 704).

[0123] Figure 8 A schematic diagram illustrates a computing unit (generally designated 203 and corresponding to the computing platform 202) included in a second embodiment. Figure 2 The second embodiment is similar to the second embodiment in that the computing unit 203-A (COM) and the computing unit 203-B (MON) are connected to the computing unit 203-A (COM) and the computing unit 203-B (MON). Figure 4 The first embodiment differs in the following ways:

[0124] - Input / output management module 4022 includes:

[0125] o A first input / output management submodule 4022a, which provides a first input / output management submodule 4022a to the partitions of the first group 4011 with a first access to at least one interface 404 of the aircraft.

[0126] Access 411a; and

[0127] o A second input / output management submodule 4022b providing the partitions of the second group 4012 with a second access 411b to the at least one interface 404 of the aircraft.

[0128] -Sub-scheduler C2 includes two sub-schedulers C2a and C2b:

[0129] o The sub-scheduler C2a manages the partitions in the first group 4011 and the first input / output management

[0130] The delay of the data stream exchanged between submodules 4022a; and

[0131] o Sub-scheduler C2b manages the latency of data flows exchanged between the partitions of the second group 4012 and the second input / output management sub-module 4022b.

[0132] Refer to above Figures 1 to 7 The first embodiment described above and the Figure 8 The second described embodiments each correspond to a complete general architecture.

[0133] To adapt to various aircraft programs, various variant implementations can be envisaged by modifying the complete common architecture in modules. This greatly simplifies design, development, updates, verification and certification.

[0134] In a first variant (forming a third embodiment):

[0135] - The top level 401 does not include the second set of partitions 4012 or scheduler B;

[0136] - the middle layer 402 does not include a second inter-partition communication module 4023 for fast inter-partition communication; and

[0137] -In the middle layer 402, the scheduler C only includes sub-schedulers C1 and C2a, and the input / output management module 4022 only includes the first input / output management sub-module 4022a (the input / output management module 4022 does not include module 602 ("very fast loop"), module 603 ("control loop") and module 604 ("field bus controller")).

[0138] In a second variant, the input / output management module 4022 does not include module 602 ("very fast loop"), module 603 ("control loop") and module 604 ("field bus controller"), and the intermediate layer 402 does not include a second inter-partition communication module 4023 for fast communication between partitions.

[0139] In a third variant, the input / output management module 4022 does not include module 602 (“very fast loop”), module 603 (“control loop”) and module 604 (“field bus controller”), and the second inter-partition communication module 4023 for fast communication between partitions does not include the “switch” module 702.

[0140] In a fourth variant, module 602 (“very fast loop”) is included in the top layer 401 .

[0141] In a fifth variation, the input / output management module 4022 does not include module 602 (“very fast loop”) and module 603 (“control loop”), and the middle layer 402 does not include a second inter-partition communication module 4023 for fast inter-partition communication.

Claims

1. A computing unit (203) for a flight control system (101) of an aircraft (100), the computing unit (203) comprising: A top layer (401), the top layer (401) comprising: a first set of partitions (4011), the first set of partitions (4011) comprising partitions each associated with a first priority level and each performing at least one first flight control function; and A first scheduler (4013) that schedules partitions of a first group, each partition of the first group being repeatedly scheduled by the first scheduler at a first frequency; and an intermediate layer (402) comprising: an input / output management module (4022) that provides the first group of partitions with access to at least one interface (404) of the aircraft; a first inter-partition communication module (4021) enabling each partition of the first group to communicate with at least one other partition associated with the first priority level and contained in another computing unit of the aircraft via a first dedicated communication channel or via at least one first communication network (403) of the aircraft; and A second scheduler (4020) that manages delays in data flows exchanged between partitions of the first group on the one hand and the input / output management module (4022) and the first inter-partition communication module (4021) on the other hand.

2. The computing unit according to claim 1, wherein: The top layer (401) further comprises: a second set of partitions (4012), the second set of partitions (4012) including partitions each associated with a second priority level higher than the first priority level and each performing at least one second flight control function; and a third scheduler (4014) that schedules partitions of a second group, each partition of the second group being repeated by the second scheduler at a second frequency that is higher than the first frequency of repetition of each partition of the first group; Wherein, the intermediate layer (402) further comprises: a second inter-partition communication module (4023) enabling each partition of the second group to communicate with at least one other partition associated with the second priority level and contained in another computing unit of the aircraft via a second dedicated communication channel or via at least one second communication network (405) of the aircraft; wherein the input / output management module (4022) further provides access to the at least one interface (404) of the aircraft to the partitions of the second group, And wherein the second scheduler (4020) also manages the delay of data flows exchanged between the partitions of the second group on the one hand and the input / output management module (4022) and the second inter-partition communication module (4023) on the other hand.

3. The computing unit according to claim 1 or 2, wherein: The first scheduler (4013) and the second scheduler (4020) are synchronized with each other. The computing unit according to claim 2 , wherein: The first scheduler (4013) and the third scheduler (4014) are synchronized with each other. The computing unit according to claim 2 , wherein: The input / output management module (4022) includes: a first input / output management submodule (4022a) that provides first access (411a) to the at least one interface (404) of the aircraft to a first group of partitions; and A second input / output management submodule (4022b) provides a second access (411b) to the at least one interface (404) of the aircraft to a second group of partitions.

6. The computing unit according to any one of claims 1 to 5, wherein: At least some of the partitions of the first and second groups comprise at least one control loop, each control loop benefiting from the repetition of the first frequency or the second frequency of the partition containing the control loop.

7. The computing unit according to claim 6, wherein: The input / output management module (4022) or the top layer (401) comprises at least one first other control loop (602) capable of accessing the at least one interface (404) of the aircraft, the first other control loop (602) repeating at a third frequency higher than the second frequency and capable of communicating with the partitions of the second group (4012).

8. The computing unit according to claim 7, wherein: The input / output management module comprises at least one second further control loop (603) which repeats at a fourth frequency higher than the third frequency, And wherein the at least one first further control loop (602) accesses the at least one interface (404) of the aircraft via the at least one second further control loop (603).

9. The computing unit according to any one of claims 1 to 8, wherein: Each partition associated with the first priority is a partition of a first type, called a user partition (4011a), or a partition of a second type, called a system partition (4011b), the partition of the second type corresponding to at least one service provided to the partition of the first type, And wherein each partition (4012a) associated with the second priority level is a partition of the first type.

10. The computing unit according to any one of claims 1 to 9, wherein: The top layer (401) is configured to provide an inter-partition communication service (413) to enable partitions of a first group to communicate with partitions of a second group via at least one memory interface.

11. A computing platform (202-1 to 202-N) for an aircraft (100), characterized in that: The computing platform (202-1 to 202-N) includes a pair of computing units (203-A, 203-B) according to any one of claims 1 to 10, a first computing unit (203-A, COM) of the two computing units functions in a command mode, and a second computing unit (203-B, MON) of the two computing units functions in a monitoring mode, thereby monitoring the first computing unit.

12. An aircraft (100), characterized in that: The aircraft (100) comprises a flight control system (101) comprising at least two computing units (203) according to any one of claims 1 to 10.

13. The aircraft according to claim 12, wherein: The flight control system (101) comprises at least two computing platforms (202-1 to 202-N) according to claim 11, and wherein partitions of a first group (4011) of computing units (203) of the at least two platforms (202-1 to 202-N) communicate with each other via the first communication modules (4021) of the computing units.

Images