End system for an avionics communication system and associated avionics communication system
The end system optimizes avionics network operation by processing mixed ARINC 664 P7 and IEEE 802 frames using shared components, reducing size and weight while maintaining deterministic performance.
Patent Information
- Application Number
- FR2021000167
- Authority / Receiving Office
- FR · FR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-01-08
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2041-01-08
AI Technical Summary
Existing avionics networks using ARINC 664 P7 and IEEE 802 protocols require separate physical components, leading to increased size, weight, and electricity consumption due to segregation, and end systems operate sub-optimally in mixed networks.
An end system for avionics communication systems that processes frames of both ARINC 664 P7 and IEEE 802 types using the same physical components, with a configuration table to determine processing protocols based on frame identification, ensuring priority transmission of ARINC 664 P7 frames and managing bandwidth for IEEE 802 frames.
This solution reduces network size and weight by using shared components, optimizes end system operation, and maintains deterministic performance by prioritizing ARINC 664 P7 frames while managing IEEE 802 frames efficiently.
Smart Images

Figure 00000015_0000 
Figure 00000017_0000 
Figure 00000018_0000
Abstract
Description
Title of the invention: End system for an avionics communication system and associated avionics communication system
[0001] The present invention relates to an end system for an avionics communication system.
[0002] The present invention also relates to an avionics communication system associated with this end system.
[0003] The invention makes it possible in particular to implement a mixed avionics network transmitting frames conforming to the ARINC 664 P7 type protocol and to an IEEE 802 type protocol different from this ARINC 664 P7 protocol.
[0004] As is known per se, the ARINC 664 standard allows for the implementation of avionics computer networks. Derived from the Ethernet standard, it allows, in particular, for the adaptation of this standard to the avionics context and, specifically, to avionics constraints. It should be noted that the A664 standard is, due to these adaptations, incompatible with the IEEE 802.3 Ethernet standard.
[0005] The ARINC 664 standard is composed of several parts, such as: a part dedicated to system concepts, a part dedicated to the physical layer, a part dedicated to services and protocol (IP).
[0006] Among these parts, we know in particular the part referenced by "P7" and generally denoted by "ARINC 664 P7" or "ARINC 664 Part 7" or even "AFDX ®".
[0007] This part P7 can be used to transmit avionics data between different avionics systems implementing essential functions of the aircraft and thus presents the greatest number of constraints.
[0008] Thus, an avionics network implemented according to Part P7 potentially presents a segregated, redundant, and deterministic network. The determinism of this network means, in particular, that each transmitted frame reaches its destination within a known maximum time. The segregation means, in particular, that one or more subscribers who do not comply with the timing constraints of the A664 P7 standard cannot disrupt the proper functioning of the network.
[0009] In certain avionics networks, it is also possible to use one or more protocols from the IEEE 802 family. As is known in itself, this family includes in particular the Ethernet 802.3 protocol or the WiFi IEEE 802.11 protocol.
[0010] The A664 P7 standard was created to allow the use of a data network in a critical environment. More specifically, it allows for the segregation of data streams with very low granularity, which is not allowed by the protocols of the IEEE 802 family.
[0011] In the avionics world, the Ethernet protocol can also be used to transfer data, which may include, for example, maintenance data, downloads, passenger entertainment, and / or crew service functions related to various avionics systems. Thus, in the event of data loss, this data can be retransmitted without creating a risk to aircraft safety.
[0012] Typically in an aircraft, ARINC 664 P7 and IEEE 802 type networks are segregated from each other. This segregation is achieved by using different physical means to implement these networks.
[0013] This means in particular that, in order to ensure such segregation, these networks use physically different switches and means of transmission.
[0014] It is therefore understandable that this type of segregation implies at least a doubling of each physical component implementing these networks. This then implies numerous problems in terms of space, power consumption, and weight in a structure housing these networks, such as an aircraft.
[0015] In the state of the art, we already know some examples of so-called mixed networks, that is to say networks of both ARINC 664 P7 type and IEEE 802 type.
[0016] Thus, for example, the Applicant's application FR 18 74166 discloses a mixed avionics system implementing a mixability of the ARINC 664 P7 and Ethernet protocols with predetermined routing.
[0017] In particular, such a system includes switches which are adapted to determine upon receipt of each frame the protocol of that frame and to process that frame in accordance with the determined protocol.
[0018] The system described in the aforementioned document further includes equipment, also called "End System" in English or "Système d'extrême" in French. Like the switches, the end systems must be adapted to handle mixed flows. However, the operation of these end systems is not always optimal.
[0019] The present invention aims to optimize the operation of the end systems of a mixed avionics system.
[0020] For this purpose, the invention relates to an end system for an avionics communication system, the avionics communication system further comprising a plurality of switches connected together to form one or more computer networks, the end system being configured to be connected to at least one of the switches to receive and / or transmit digital data in the form of frames through that switch;
[0021] each frame having an identification field and being of first type or second type, the identification field of each frame defining an identification value, the first type frames conforming to a protocol of type ARINC 664 P7 and the second type frames conforming to a protocol of type IEEE 802, the set of first type frames having the same identification value forming the same first type stream and the set of second type frames having the same identification value forming the same second type stream;
[0022] the endpoint system being characterized in that it comprises at least one input port capable of receiving frames, and a configuration table comprising, for each identification value, parameters for processing frames having that identification value; and
[0023] in that it is capable of determining a processing protocol for each frame received via the input port exclusively from the processing parameters corresponding to the identification value of that frame in the configuration table, regardless of the type of that frame.
[0024] According to other advantageous aspects of the invention, the end system comprises one or more of the following features, taken individually or in any technically possible combination:
[0025] - the identification value is a destination address of the frame;
[0026] - the identification field of each frame corresponds to the MAC DEST field of this framework;
[0027] - the set of frame identification values of each type and the parameters corresponding processing steps are statically determined in the configuration table;
[0028] - for each identification value, the processing parameters include a parameter indicating the need for redundancy management of each frame having this identification value;
[0029] - at least one output port capable of transmitting first-type frames and / or second type;
[0030] - the system is configured to transmit each second-type frame according to a predefined timing period determined by the identification value of this frame;
[0031] - each timing period is defined by the associated processing parameters to the corresponding identification value;
[0032] - the system is configured to transmit each second type frame by rem pleating of the available bandwidth after the transmission of the corresponding first-type frames.
[0033] The present invention also relates to an avionics communication system comprising at least two end systems as defined above and at least one switch connected to each of the end systems.
[0034] These features and advantages of the invention will become apparent from the following description, given solely by way of non-limiting example, and made with reference to the accompanying drawings, in which:
[0035] [fig. 1] the [fig.1] is a schematic view of an aircraft comprising an ARINC 664 P7 type avionics network and an IEEE 802 type avionics network;
[0036] [fig.2] [fig.2] is a schematic view of a communication system according to the invention, the communication system implementing the avionics networks of the [fig.l];
[0037] [fig.3] [fig.3] is a schematic view of frames transmitted by the system of communication of the [fig.2];
[0038] [fig-4] [fig.4] is a schematic view of an end system forming part of the communication system of the [fig.2];
[0039] [fig.5] [fig.5] is a schematic view of the distribution of a bandwidth implemented by the end system of [fig. 4], according to a first embodiment of the invention; and
[0040] [fig.6] [fig.6] is a schematic view of the distribution of a bandwidth implemented by the end system of [fig.4], according to a second embodiment of the invention.
[0041] In all that follows, any reference to a norm or standard, in particular a computer standard, refers to general principles of that standard which are well known to a person skilled in the art and which are independent of different versions of that standard, unless explicitly stated otherwise.
[0042] Fig. 1 illustrates an aircraft 10 such as an airplane.
[0043] The aircraft 10 includes an avionics network 12 of type ARINC 664 P7 and an avionics network 14 of type IEEE 802.
[0044] The avionics network 12 allows sensitive data to be transmitted between different avionics systems. Sensitive data includes, in particular, any data whose loss or delayed transmission could affect the safety of the aircraft 10.
[0045] The avionics network 14 allows the transmission of less sensitive data compared with the avionics network 12. Thus, for example, this data corresponds to maintenance data exchanged between the aircraft 10 and the ground and / or to functional data exchanged with the crew and / or to passenger entertainment data and / or to any other type of data.
[0046] The digital data circulating in the two networks 12, 14 are respectively in the form of first type frames and second type frames.
[0047] Thus, the first type frames conform to the ARINC 664 type protocol P7 and second type frames conform to the IEEE 802 type protocol.
[0048] In particular, "IEEE 802 type protocol" means one of the protocols in the IEEE 802 protocol family. Such a protocol is, for example, the Ethernet 802.3 type protocol or one of the 802.1xxx type protocols, i.e., the IEEE 802.11 WiFi type protocol, the 802.1Q type protocol or the MilStd 1553 type protocol.
[0049] An example of a frame of each type is illustrated in [fig.3]. In particular, with reference to this figure, the example of a first-type frame is designated by the numerical reference "15" and the example of a second-type frame is designated by the numerical reference "16".
[0050] Each frame transmitted in the corresponding network 12, 14 includes an identification field.
[0051] In the example described, this identification field is included in a frame header and forms, for example, a field called "MAC DEST". In [Fig. 3], the header is denoted by the reference "MAC HEADER".
[0052] As is known in itself, the MAC DEST field designates the MAC address of the receiving equipment of the corresponding frame.
[0053] Each identification field takes an identification value which, in the example described, corresponds to the MAC address of the receiving equipment of the corresponding frame. In other words, the identification value defines a virtual link (also called a VL) in the case of frames of the ARINC 664 P7 protocol.
[0054] According to other embodiments, the identification field is formed by any other field in the frame header such as, for example, the MAC SOURCE field designating the MAC address of the equipment sending the corresponding frame.
[0055] According to yet other embodiment examples, the identification field is formed by at least a part of the useful data field of the frame.
[0056] In general, the identification field of a frame should be understood as any field of the frame that allows the switching rules of that frame to be determined within a given switch, as will be explained later.
[0057] The set of frames of the first type having the same identification value form the same flow of the first type and the set of frames of the second type having the same identification value form the same flow of the second type.
[0058] In other words, each stream of each type is formed from the set of frames having the same identification value. Thus, the identification field of each frame also contains an identifier of the stream to which that frame is associated.
[0059] According to the invention, the avionics networks 12 and 14 are implemented by the same physical avionics communication system 20.
[0060] An example of such an avionics communication system 20 is illustrated on the [fig-2].
[0061] Thus, with reference to this figure, this communication system 20 comprises a plurality of switches 22A,...,22N and a plurality of end systems 24A,...,24M. The number of these different components and the manner of their interconnection can of course vary depending on the examples.
[0062] The switches 22A,... ,,22N are connected to each other by means of transmission also having, for example, a twisted pair cable or any other type of cable allowing bidirectional data transmission or wireless links transmitting digital data via radio waves.
[0063] The switches 22A, ..., 22N are, for example, substantially analogous to each other. Thus, in the described example, each switch 22A, ..., 22N is capable of receiving each frame via an input port and transmitting it via an output port. To do this, upon receiving each frame, each switch 22A, ..., 22N is, for example, capable of determining the type of that frame and transmitting it to a corresponding output port. According to another embodiment, upon receiving each frame, each switch 22A, ..., 22N is capable of determining the identification value of that frame and determining the corresponding output port based on that value. In this case, each switch 22A, ..., 22N is, for example, capable of storing a configuration table comprising, for each identification value, rules for switching frames having that identification value. In all cases, each 22A switch,...,22N is capable of transmitting each frame of the first type with priority over each frame of the second type.
[0064] According to various embodiments, each switch 22A,... ,22N is also capable of applying at least one filtering operation to each frame of the first type and, in some examples, to each frame of the second type. This filtering operation may include controlling the timing period of frames having the same identification value, controlling the size of the packets transmitted by the frames, controlling the frame lifetime, etc.
[0065] Each end system 24A,...,24M, also known by the English term "End System" or simply by the term "equipment", is integrated into an avionics system and ensures communication of this system with the networks 12, 14.
[0066] Thus, depending on the avionics system in which it is integrated, each end system 24A,...,24M can be a transmitter and / or receiver of digital data.
[0067] Furthermore, at least some of the 24A, ..., 24M end systems may belong solely to network 12 or solely to network 14. In this case, such an end system is capable of transmitting and / or receiving digital data only from that network. At least some other 24A, ..., 24M end systems may belong to both network 12 and network 14 insofar as they are capable of transmitting and / or receiving digital data from these two networks.
[0068] Each end system 24A, ..., 24M is connected to at least one of the switches 22A, ..., 22N via transmission means and via at least one port of that switch. The transmission means include, for example, twisted-pair cable or any other type of cable allowing bidirectional data transmission, or wireless links transmitting digital data via radio waves.
[0069] Just like the end systems 24A,...,24M, each transmission means can belong only to one of the networks 12 and 14, or to both networks 12 and 14. This depends in particular on the nature of the end system 24A,...,24M that the corresponding transmission means connects to the corresponding network.
[0070] Within the corresponding network 12, 14, each end system 24A,...,24M is identified by its MAC address. In particular, in the case of the ARINC 664 P7 type network 12, several MAC addresses can be associated with the same end system 24A,...,24M. Each of these addresses corresponds to a virtual link leading to this end system 24A,...,24N.
[0071] In the case of an IEEE 802 type 14 network, generally only one MAC address (a "unicast" type address) is associated with each corresponding end system. There are also "multicast" and "broadcast" type MAC addresses that an end system must be able to receive.
[0072] Thus, when the same end system belongs to both networks 12 and 14, it can be associated with a MAC address (of the "unicast" type) for network 14 and with one or more MAC addresses for network 12.
[0073] The structure of the end system 24A will subsequently be described in detail with reference to [Fig. 4]. It will also be assumed that this end system 24A belongs to both networks 12 and 14, and is capable of transmitting frames to and from these networks. The structure of the other end systems 24B, ..., 24M is analogous to this one, with obvious adaptations depending on the nature of the system.
[0074] Thus, with reference to this [Fig. 4], the end system 24A comprises a plurality of input ports 31, a plurality of output ports 32, a configuration table 33, and control means 34. It should be noted that in this figure, only the external ports, i.e., the ports connecting the system 24A to networks 12 and 14, are shown. Any internal ports or links connecting this end system 24A to the various components (applications) of the avionics system in which it is integrated are therefore not shown and will not be described in detail hereafter.
[0075] Each input port 31 is capable of receiving first-type frames and / or second type.
[0076] Each output port 32 is capable of transmitting first type and / or second type frames.
[0077] The configuration table 33 allows the rules for processing frames to be determined within the end system 24A.
[0078] To achieve this, the configuration table 33 is stored in a dedicated memory of the end system 24A, and includes a list of identification values and, for each identification value, frame processing parameters for frames having that identification value. These processing parameters are then defined for each stream that can be transmitted or received by the end system 24A.
[0079] According to an advantageous embodiment of the invention, the memory of the end system 24A dedicated to storing the configuration table is of the CAM type. In other words, this memory is implemented according to CAM technology (from the English "Content Addressable Memory"), which means that this memory is content-addressable.
[0080] According to this example, the memory of the end system 24A is initialized with the list of identification values. This means, in particular, that each identification value has a memory address referring to a storage field containing the processing parameters corresponding to that identification value. This makes it possible to search for the identification parameters corresponding to a given identification value very fast, even virtually instantaneous, compared to a traditional search in a list.
[0081] In one embodiment, the list of identification values is statically determined. This means that this list is determined, for example, at the system design stage and cannot be modified during its operation. It therefore involves a predetermined processing of frames of each type.
[0082] According to another embodiment, at least some of the identification values in this list are determined dynamically. That is, these values can be deleted or added during the operation of the system 20. In this case, these identification values relate only to second-type streams. It should be noted that when a CAM-type memory is used, an address of this memory can also be dynamically added or deleted as a result of adding or deleting an identification value.
[0083] As for the identification values of the first type frames, that is to say the identification values of the ARINC 664 P7 flows, these can only be defined statically in order to guarantee the determinism of the network 12.
[0084] For each identification value of the flows intended to be received by the terminal system 24A, the processing parameters are of the same nature and are in particular independent of the protocol of the frames of the corresponding stream. In other words, for each identification value of the streams intended to be received by the end system 24A, the processing parameters are advantageously composed of the same number of parameters which are ordered in the same way and this regardless of the protocol of the corresponding stream.
[0085] Thus, these parameters for processing the streams intended to be received by the end system 24A, include for each identification value at least one identifier of an internal port or an internal transmission link to which each frame received by the system 24A must be transmitted.
[0086] Advantageously, the processing parameters for streams intended to be received by the end system 24A further include, for each identification value, a parameter indicating the need for redundancy management of each frame having this identification value.
[0087] Advantageously, in a particular embodiment of the invention, this parameter is "true" for each identification value corresponding to a first-type flow and "false" for each identification value corresponding to a second-type flow.
[0088] Redundancy management conforms to the requirements of the ARINC 664 P7 protocol. In particular, and in a manner known per se, the redundancy management of a frame comprises, upon transmission of that frame by the corresponding end system, the generation of several replicas of that frame and, upon reception by the corresponding end system, the comparison of all the replicas and, based on this comparison, the rejection of these replicas or the deletion of at least some of them to retain only the original frame. The replicas corresponding to the same frame can, for example, be determined using a sequential number written at the end of each frame. In the example of frames of the first type, this can correspond to the SN field illustrated in [Fig. 3] in relation to frame 15.
[0089] Thus, advantageously according to the invention, the redundancy mechanism is applied to each first-type frame and is not disturbed by the traffic of second-type frames.
[0090] Just like the processing parameters for the identification values of the streams intended to be received by the end system 24A, the processing parameters for the identification values of the streams intended to be transmitted by the end system 24A are of the same nature and are, in particular, independent of the protocol of the frames of the corresponding stream. In other words, for each identification value of the streams intended to be transmitted by the end system 24A, the processing parameters advantageously consist of the same number of parameters ordered in the same order. in this way, and this regardless of the protocol of the corresponding stream.
[0091] For each identification value of the streams intended to be emitted by the end system 24A, the processing parameters include at least one frame timing period of the corresponding stream and at least one output port 32 of the frames of that stream.
[0092] The timing period then defines a timing for the frames of the stream corresponding to a minimum transmission interval of two consecutive frames of the same stream.
[0093] For first-type flows, the timing period is known by the English term "BAG" (for "Bandwidth Allocation Gap"). This timing allows, in particular, the definition of an authorized bandwidth for the corresponding flow.
[0094] According to a first embodiment, timing periods are also associated with second-type flows. In this case, the second-type flows are said to be "Bagged" insofar as properties similar to those of first-type flows are associated with these second-type flows. In this case, it is therefore also possible to associate a predetermined bandwidth with each second-type flow.
[0095] The transmission of frames according to this first embodiment by the same output port 32 is schematically illustrated in [fig.5].
[0096] In particular, according to the example in this figure, a timing period BAGVLx is determined for a first-type flow and a timing period BAGVLy is determined for a second-type flow. The timing period BAGVLx is shown on the time axis VLx and the timing period BAGVLy is shown on the time axis VLy.
[0097] These periods are determined according to the bandwidth available at the corresponding times.
[0098] Thus, during the transmission of first-type frames denoted in [Fig. 5] by "A664P7 REQUEST T0", ..., "A664P7 REQUEST T4" and second-type frames denoted in [Fig. 5] by "ETHERNET REQUEST T0", ..., "ETHERNET REQUEST T3", these frames are transmitted according to their timing periods as illustrated on the NETWORK timeline. Furthermore, the transmission of first-type frames takes priority over the transmission of second-type frames, as explained in relation to switches 22A, ..., 22N.
[0099] According to a second embodiment, predetermined timing periods are not associated with the second type of flows. In this case, the corresponding values in configuration table 33 can be equal to a predetermined value (for example, 0), which then means that no timing period per- particular is not associated with the corresponding flow.
[0100] According to this embodiment, each output port 32 is configured to transmit each second type frame by filling the available bandwidth after the transmission of the corresponding first type frames.
[0101] The transmission of frames according to this second embodiment by the same output port 32 is schematically illustrated in [fig.6].
[0102] In particular, according to the example in this figure, a timing period BAGVLx is determined for a first-type flow and is illustrated on the time axis VLx.
[0103] When transmitting the first-type frames denoted in [Fig. 6] by "A664P7 REQUEST T0", ..., "A664P7 REQUEST T4", these frames are transmitted according to their timing period, as illustrated on the NETWORK timeline. As for the second-type frames denoted by "ETHERNET REQUEST T0", ..., "ETHERNET REQUEST T3", these are transmitted in the "gaps" formed between the transmissions of the frames denoted by "A664P7 REQUEST T0", ..., "A664P7 REQUEST T4", as also visible on the NETWORK timeline. Here, as in the previous case, the first-type frames are transmitted with priority over the second-type frames.
[0104] In a particular embodiment of the invention, only the processing parameters for the identification values of the streams intended to be received by the end system 24A are stored in the configuration table 33 along with these identification values. As for the processing parameters for the streams intended to be transmitted by the end system 24A, these are stored in a separate table or in any other available means.
[0105] The control means 34 allow control of the operation of each input port 31 and output port 32 and are presented for example in the form of a central unit connected to each of these ports, as shown in [fig.4].
[0106] According to another embodiment, the control and switching means 34 are distributed at least partially between the ports 31, 32 and thus allow local control of the operation of each of these ports.
[0107] The control means 34 also allow switching of frames within the end system 24A between each input port 31 and an internal port or link, and between such an internal port or link and an output port 32, in accordance with the corresponding flow processing parameters in the configuration table 33, as explained previously.
[0108] The control means 34 also allow the implementation of redundancy management mechanisms as explained previously.
[0109] It is therefore understood that the present invention has a number of advantages.
[0110] First, the invention makes it possible to implement a mixability of ARINC 664 P7 and IEEE 802 type networks using the same physical components, i.e. the same means of transmission, the same switches and the same input and output ports.
[0111] This then makes it possible to considerably reduce the size and weight of the networks 12 and 14 on board the aircraft 10.
[0112] Finally, the end systems are configured to process frames independently of their type, that is, independently of the protocol of those frames. The operation of each end system can thus be substantially identical for each frame, so that there is no longer any need to distinguish frames of different protocols. This then allows for the optimization of the operation of the end systems.
Claims
Claims
1. An end system (24A) for an avionics communication system (20), the avionics communication system (20) further comprising a plurality of switches (22A, ..., 22N) connected together to form one or more computer networks, the end system (24A) being configured to be connected to at least one of the switches (22A, ..., 22N) to receive and / or transmit digital data in the form of frames through that switch (22A, ..., 22N);each frame having an identification field and being of first type or second type, the identification field of each frame defining an identification value, the frames of first type conforming to a protocol of ARINC 664 P7 type and the frames of second type conforming to a protocol of IEEE 802 type, all of the frames of first type having the same identification value forming a same flow of first type and all of the frames of second type having the same identification value forming a same flow of second type; the end system (24A) being characterized in that it comprises at least one input port (31) capable of receiving frames, and a configuration table (33) comprising for each identification value parameters for processing the frames having this identification value;and in that it is capable of determining a processing protocol for each frame received via the input port (31) exclusively from the processing parameters corresponding to the identification value of this frame in the configuration table (33), independently of the type of this frame.;
2. The end system (24A) of claim 1, wherein the identification value is a destination address of the frame.
3. The end system (24A) of claim 2, wherein the identification field of each frame corresponds to the MAC DEST field of that frame.
4. An end system (24A) according to any preceding claim, wherein the set of frame identification values of each type and the corresponding processing parameters are statically determined in the configuration table (33).
5. An end system (24A) according to any preceding claim, wherein for each identification value, the processing parameters include a parameter indicating the need for redundancy management of each frame having that identification value.
6. An end system (24A) according to any preceding claim, further comprising at least one output port (32) capable of transmitting frames of the first type and / or of the second type.
7. Endpoint system (24A) according to claim 6, configured to transmit each second type frame according to a timing period predefined by the identification value of this frame.
8. The endpoint system (24A) of claim 7, wherein each clocking period is defined by the processing parameters associated with the corresponding identification value.
9. An end system (24A) according to claim 6, configured to transmit each second type frame by filling the available bandwidth after transmitting the corresponding first type frames.
10. An avionics communication system (20) comprising at least two end systems (24A, ..., 24M) and at least one switch (22A, ..., 22N) connected to each of the end systems (24A, ..., 2M), each end system (24A, ..., 24M) being according to any one of the preceding claims.
