Patent Description:
For contemporary aircraft, an avionics 'platform' includes of a variety of elements such as sensors, data concentrators, a data communications network, radio frequency sensors and communication equipment, computational elements, operational or functional elements, and graphical displays. These components can share information with other components over the data communications network.

Transfer of platform elements data can either be periodic or aperiodic, meaning that data can be sent to a destination, or multiple destinations in either scheduled packages, or on demand from a user or other outside source. During operation, the platform element data can be identified by destination, supply the payload information to the destination, and perform an error check for each payload. In some instances, specialized data networks, such as Aeronautical Radio Inc. (ARINC) compliant data networks, can define standards or specifications for network operations, including data transmissions. Current ARINC specifications can be inefficient in the packaging of this information, and as a result, can decrease the transmission efficiency of the data communications network. For example, an ARINC <NUM> compliant data network or system can allow for <NUM> bits out of a total <NUM> bits per label or word for the payload to be relayed or transmitted to the destination.

Network components utilized to construct the data network can utilize a specialized data network protocol, hardware including relays, switches, communicative connections, and the like, to ensure performance of the network architecture for the specialized data, as for example, under the performance of the network communications defined by various data network specifications. <CIT> describes a transmitting device for easily adapting to different types of data to be exchanged on board an aircraft.

<CIT> relates to a user station for a bus system which enable a refinement of the CAN signal structures and necessary communication devices toward high data rates.

In one aspect, aspects of the disclosure relate to a method for transmitting a set of conforming data frames according to claim <NUM>.

In another aspect, aspects of the disclosure relate to an avionics-specific specialized data network, according to claim <NUM>.

Aspects of the disclosure described herein are provided with respect to a specialized avionics data protocol, but it will be understood that the apparatus and method described herein can be implemented in any environment using a data communications network interconnecting a set of data-generating components with a set of data-consuming components. Aspects of the disclosure can include data communications networks configured to operate according to defined network characteristics or specifications. For example, contemporary aircraft operate a set of components interconnected by way of a data network defined by a network standard, such as the ARINC, or a subdivision thereof, for example ARINC <NUM> (A429) specification, incorporated herein in its entirety. While aspects of the disclosure refer to the A429 specification, aspects of the disclosure are applicable to other specialized data networks, including, but not limited to the ARINC <NUM> specification, the ARINC <NUM> CAN bus specification, or the like. The A429 specification defines compliant network operations including, but not limited to, redundancy, dedicated bandwidth, and deterministic quality of service. In another non-limiting example, a specialized data network can include compliant network operations including network switching performance. While aspects of the disclosure are described with respect to the A429 specification or A429 data frames, transmissions, and the like, the disclosure can be applicable to any specialized data network, compliant data network, avionics data network, or the like utilized for data transmissions between a set of interconnected data sources and data destinations. As used herein, "compliant" is used to denote conformance (or conforming) to the specification of the specialized data network to enable operation of the specialized data network. For example, a "compliant" data transmission will be carried or otherwise delivered from a data source to a data destination. In contrast, a "non-compliant" data transmission may not be delivered, and the non-compliant data transmission may be eliminated, ignored, dropped, or otherwise discarded during or prior to transmission.

Additional, updated or new network standards can be incorporated into contemporary aircraft in order to operate the set of interconnected components. In some instances, it is desirable to ensure the updated or new network standards are compatible with legacy or future systems, including but not limited to the A429 specification, or A429 data transmissions.

Furthermore, as used herein, the term "set" or a "set" of elements can be any number of elements, including only one. Also, as used herein, while sensors can be described as "sensing" or "measuring" a respective value, sensing or measuring can include determining a value indicative of or related to the respective value, rather than directly sensing or measuring the value itself. The sensed or measured values can further be provided to additional components. For instance, the value can be provided to a controller module or processor, and the controller module or processor can perform processing on the value to determine a representative value or an electrical characteristic representative of said value.

All directional references (e.g., radial, axial, upper, lower, upward, downward, left, right, lateral, front, back, top, bottom, above, below, vertical, horizontal, clockwise, counterclockwise) are only used for identification purposes to aid the reader's understanding of the disclosure, and do not create limitations, particularly as to the position, orientation, or use thereof. Connection references (e.g., attached, coupled, connected, and joined) are to be construed broadly and can include intermediate members between a collection of elements and relative movement between elements unless otherwise indicated. As such, connection references do not necessarily infer that two elements are directly connected and in fixed relation to each other. In non-limiting examples, connections or disconnections can be selectively configured to provide, enable, disable, or the like, an electrical connection or communicative connection between respective elements. Additionally, as used herein, "electrical connection" or "electrically coupled" can include a wired or wireless power or data (e.g. communicative or transmissive) connection between respective components.

Additionally, as used herein, a "controller" or "controller module" can include a component configured or adapted to provide instruction, control, operation, or any form of communication for operable components to affect the operation thereof. A controller module can include any known processor, microcontroller, or logic device, including, but not limited to: field programmable gate arrays (FPGA), an application specific integrated circuit (ASIC), a full authority digital engine control (FADEC), a proportional controller (P), a proportional integral controller (PI), a proportional derivative controller (PD), a proportional integral derivative controller (PID controller), a hardware-accelerated logic controller (e.g. for encoding, decoding, transcoding, etc.), the like, or a combination thereof. Non-limiting examples of a controller module can be configured or adapted to run, operate, or otherwise execute program code to affect operational or functional outcomes, including carrying out various methods, functionality, processing tasks, calculations, comparisons, sensing or measuring of values, or the like, to enable or achieve the technical operations or operations described herein. The operation or functional outcomes can be based on one or more inputs, stored data values, sensed or measured values, true or false indications, or the like. While "program code" is described, non-limiting examples of operable or executable instruction sets can include routines, programs, objects, components, data structures, algorithms, etc., that have the technical effect of performing particular tasks or implement particular abstract data types. In another non-limiting example, a controller module can also include a data storage component accessible by the processor, including memory, whether transient volatile or non-transient, or non-volatile memory. Additional non-limiting examples of the memory can include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic memory, such as discs, DVDs, CD-ROMs, flash drives, universal serial bus (USB) drives, the like, or any suitable combination of these types of memory. In one example, the program code can be stored within the memory in a machine-readable format accessible by the processor. Additionally, the memory can store various data, data types, sensed or measured data values, inputs, generated or processed data, or the like, accessible by the processor in providing instruction, control, or operation to affect a functional or operable outcome, as described herein.

The exemplary drawings are for purposes of illustration only and the dimensions, positions, order and relative sizes reflected in the drawings attached hereto can vary.

As illustrated in <FIG>, an aircraft <NUM> can include at least one propulsion engine, shown as a left engine system <NUM> and right engine system <NUM>. The aircraft <NUM> can further include one or more data sources, that is, components that create, originate, or otherwise generate data, and data destinations, that is, components that receive, consume, process, or otherwise act on or effect an outcome or operation based on data received. As shown, the aircraft <NUM> can include a data destination <NUM> or receiver, including, but not limited to data storage or processing units, or functional systems such as the flight management system (FMS) or autopilot system, and a data source <NUM>, such as a set of fixed aircraft components, such as line-replaceable units (LRUs) <NUM>, networking end nodes, or modular components of a vehicle or aircraft. Alternatively, there can be two or more data destinations <NUM>, or two or more data sources <NUM> at various locations throughout the aircraft <NUM>. Non-limiting examples of data sources <NUM> can include sensors, a system, an electronic flight bag (EFB), or the like. Similarly, non-limiting examples of the data destination <NUM> can be various components of an aircraft <NUM> such as an aircraft computer, the LRU <NUM>, the electronic flight bag (EFB), a memory storage unit, or any other known component adapted to receive aircraft information. In the aircraft environment, the data destination <NUM>, or the data source <NUM> can be designed to operate according to a particular operation, interoperability, or form factor standards, such as those defined by ARINC series standards. In the exemplary aspects illustrated, the data destination <NUM> can be positioned near the nose, cockpit, or pilot of the aircraft <NUM> and the data source <NUM> can be positioned at various locations throughout the aircraft <NUM>, however, any relative arrangement can be included.

The data destinations <NUM> and data source <NUM> can be configured to be communicatively coupled by way of a series of transmission pathways <NUM>, network relays, or network switches <NUM>. While network switches <NUM> are schematically illustrated, non-limiting aspects of the disclosure can be applied to peer-to-peer networks. The transmission pathways <NUM> can include a physical connection between the data source <NUM>, and the data destination <NUM>, such as a wired connection including Ethernet, or can include wireless transmission connections, including, but not limited to, WiFi (e.g. <NUM> networks), Bluetooth, and the like. Collectively, the data destination <NUM>, data source <NUM>, transmission pathways <NUM>, and switches <NUM> can form an avionics data network, or avionics-specific data network for the aircraft.

The aircraft <NUM>, and the systems thereof, can be communicatively interconnected by way of the avionics-specific data network such has an ARINC-compatible data network. The avionics-specific data network can be an ARINC <NUM> (A429) compatible data network. It will be appreciated that the aircraft <NUM>, and the systems thereof can be any avionics-specific data network compatible with any ARINC data network, or any other known avionics-specific data network.

The data source <NUM> can include, for example, entirely contained systems, sensors, radios, or other auxiliary equipment to manage or operate aircraft functions. At least a set of data destination <NUM> or data source <NUM> can, for example, generate data, which can be modified, computed, or processed prior to, or in preparation for packaging the data into data frames to be transmitted over the avionics data network by way of the transmission pathways <NUM> or switches <NUM>. At least another set of data destination <NUM> or data source <NUM> can, for example, consume the data transmitted over the avionics data network. In some instances, a single data destination <NUM> or data source <NUM> can operate to both generate and consume data. As used herein, "consume," "consuming," or "consumption" of data will be understood to include, but is not limited to, performing or executing a computer program, routine, calculation, or process on at least a portion of the data, storing the data in memory, or otherwise making use of at least a portion of the data.

The data source <NUM>, and the data destination <NUM> can include non-stationary data sources. As used herein, "non-stationary" means any device that can be moveable relative to the aircraft or data network, such as carried by one the flight crew from one location to another either on, or off the aircraft <NUM>, compared with a "stationary" data source or "stationary" data destination that can include devices that are generally fixed or incorporated into the aircraft <NUM> and would require significant work or maintenance services to remove from the aircraft <NUM>. For example, a non-stationary data destination <NUM>, or data source <NUM> can be the EFB. The EFB can include a handheld device such as a tablet, palm-pilot, pager, portable computer, smart device, or the like, that can be carried onto the aircraft <NUM> by the flight crew. In contrast, a stationary data destination <NUM> can be, for example, a cockpit display, cockpit computer, or the like.

The data destination <NUM> can be utilized to receive aperiodic data transmissions, including, but not limited to, flight plan data transmitted to a data source <NUM> such as such as, but not limited to, an avionics device including a central processing unit.

The illustrated aircraft <NUM> is merely one non-limiting example of an aircraft <NUM> that can be used in aspects of the disclosure described herein. Particularities of the illustrated aircraft <NUM> aspects, including relative size, length, number of engines, type of engines, and location of various components are not germane to the aspects of the disclosure, unless otherwise noted.

In some example components, such as the data destination <NUM> or data source <NUM>, the components can be removably fixed to the aircraft for maintenance, diagnostics, or repair purposes, but statically fixed during, for example, flight. Additionally, while the data destination <NUM> and the data source <NUM> are described, any data generating or data receiving or consuming components fixed relative to an aircraft can be included as aspects of the disclosure as fixed components. For example, systems such as an FMS, primary flight display, cockpit display system, autopilot, or autoland systems can be considered fixed components, as used herein.

<FIG> illustrates a non-limiting schematic view of a specialized data network <NUM> according to aspects of the disclosure. The specialized data network <NUM> can include various components, and perform the functions of an avionics data network outlined herein. The specialized data network can include, but is not limited to, a set of redundant network switching units, such as a first set of switching units <NUM> defining a first path and a second set of switching units <NUM> defining a second, or redundant, path. The first and second switching units <NUM>, <NUM> collectively define a network mesh <NUM> for routing the transmission of data frames between respective components, such as to and from the data destination <NUM>, and data source <NUM> data sources <NUM> via the transmission pathways <NUM>. The network mesh <NUM> is further shown having a set of transmission pathways <NUM> between the network switching units <NUM> to provide redundancy in transmission pathways <NUM>. In one non-limiting example, the network mesh <NUM>, the first set of switching units <NUM>, the second set of switching units <NUM>, or a combination thereof, can be arranged, configured, or otherwise enabled to utilize a specialized data network <NUM> transmission schema. The aspects of the disclosure illustrated in <FIG> is merely one representation of the specialized data network <NUM>, and alternative configurations, organization, and component quantities, including, but not limited to, data destination <NUM>, data source <NUM>, or network switching units <NUM>, are envisioned.

The data source <NUM> can be operatively coupled to the specialized data network <NUM> such that it can transmit data based off of various avionic systems to the data destination <NUM>, or other destinations such as the LRU <NUM>.

<FIG> is a non-limiting example of a set of data transmissions in the specialized data network <NUM> of <FIG>, arranged relative to a time scale during which the set of data transmissions are provided to the specialized data network <NUM>. The specialized data network <NUM> can include one or more time slots TS1-TS6 to receive one or more data transmissions, or transmissions of data frames. The specialized data network <NUM> can include multiple specialized sets of conforming data frames <NUM> that can be transmitted over a time scale. As used herein, "conforming" data frames means any set of data transmitted through the specialized data network <NUM> that conforms with the various system requirements such as, but not limited to, those outlined by the various ARINC specifications, and are thus, delivered or deliverable by the specialized data network <NUM>, while "nonconforming" data frames can include any set of data sent through the specialized data network <NUM> that does not meet the various system requirements such as, but not limited to, those outlined by the various ARINC specifications such that they will not be delivered or deliverable. Stated another way, the specialized data network <NUM> has specific requirements that can be followed for a respective data frame to be "conforming," otherwise the respective transmission of the data frame will not occur. In the present example, the time scale can be over a <NUM> time frame or period of time wherein each of the time slots TS1-TS6 can be <NUM>.

Each conforming data frame <NUM> can include in this instance, for example, a specialized header <NUM>, payload data <NUM>, and an optional error check component, shown as an optional cyclic redundancy check (CRC) <NUM>. Alternatively, each of the conforming data frame <NUM> can include any number of specialized headers <NUM>, payloads <NUM>, or CRCs <NUM>.

The specialized header <NUM> can include various identifying information that can inform the data destination <NUM> of the characteristics of the data being transmitted from the data source <NUM>, the target destination of the conforming data frame <NUM>, the encoding of the conforming data frame <NUM>, or the like. The specialized header <NUM> is discussed in greater detail herein.

The payload data <NUM> can be any data transmitted from the data source <NUM>, or an input from an outside source. The transmitted data can include, for instance, an altitude, a flight plan, a maintenance database, an external temperature, a pressure reading, a speed reading, a fuel level, or any other data or input provided from the data source <NUM>. It will be appreciated that the payload can be any data utilized in the operation of the aircraft <NUM>, or a system therein. The conforming data frame <NUM> can include any one of internal FMS data such as, but not limited to, a predicted flight path, the flight plan, maintenance log, maintenance database, or the like.

The CRC <NUM> can be implemented into the conforming data frame <NUM> to ensure that potential errors in the data are detected. The CRC <NUM> can be performed by a processor, or microcontroller that ensures that the data being sent by the data source <NUM> to the data destination <NUM> does not include any potential errors. On the transmitting end, the data source <NUM> utilizes the CRC <NUM> to create a check or verification code that is compared to the CRC <NUM> check or verification code that is created at the receiving end, or data destination <NUM>. If the check or verification codes do not match, the data destination <NUM>, can request that the data source <NUM> retransmit the conforming data frame <NUM>, or the data destination <NUM>, can ignore the conforming data frame <NUM>. Alternatively, the data destination <NUM> can inform the specialized data network <NUM> of the faulty data, and the specialized data network can then notify a user of the aircraft <NUM>, or a ground operator of the faulty condition via a user interface (not shown), or any other notification device.

The conforming data frame <NUM> can be on either a periodic schedule, or an aperiodic schedule. As used herein, "periodic schedule" can include any data from a data source <NUM> that is transmitted during a predetermined time-frame. For example, periodic schedule conforming data frames <NUM> can include repeated, schedule transmissions such as airspeed and altitude. In contrast, "aperiodic schedule" conforming data frames <NUM> can be any data source <NUM> that is transmitted "on-demand" or on a non-predetermined regular or repeating time frame, such as in response to an event (e.g. "event-driven" or a "triggered" event).

The conforming data frames <NUM> of the specialized data network <NUM> can be of differing sizes. For example, the conforming data frame <NUM> of the first time slot TS <NUM> can take the entirety of the designated time to transmit its data from the data source <NUM>, while the specialized data set of the second time slot TS2 can take half of the designated time to transmit its data from the data source <NUM>. It will be appreciated that each conforming data frame <NUM> can be of varying sizes and can take more or less time to transmit its data form the data source <NUM> to the data destination <NUM>. In one example, one or more of the sets of conforming data frames <NUM> can include both the specialized header <NUM>, the payload data <NUM>, and optionally, the CRC <NUM>.

The specialized data network <NUM> can be a deterministic data network. The deterministic data network can be a specialized data network <NUM> considered to be a relatively reliable network in the sense that multiple redundancies and checks are built into the system to ensure that the correct, or unmodified data from the data source <NUM> is being transmitted to the correct data destination <NUM> at the correct time slot TS1-TS6. For instance, in one non-limiting example, a portion of data being transmitted from the data source <NUM> can be unintentionally or inadvertently modified by way of a single-event upset, such an electro-magnetic event, a solar flare, or the like. Additional "modifying" events can be included. Alternatively, the specialized data network <NUM> can be a broadcast-style bus. The broadcast-style network can be a specialized data network <NUM> that can transmit, or broadcast the data from the data source <NUM> to all receiving data destinations <NUM>. In the case of the broadcast-style bus, the specialized data network <NUM> can define a time slot TS1-TS6 limiting the amount of time the data source <NUM> has to generate, or transmit the conforming data frame <NUM> and its applicable components to the data destination <NUM>. In the instance of the broadcast-style bus, the specialized data network <NUM> can further be adapted such that a set of data destinations <NUM> not expect or receiving a subset of the conforming data frames <NUM> simply ignore that subset of conforming data frames <NUM>.

While <FIG> illustrated an example set of transmissions that spanned over multiple time slots (TS1-TS6), <FIG> illustrates another example set of transmissions, also in accordance with aspects of the specialized data networks, wherein a set of conforming data frames defining a larger set of payload data <NUM> spread over multiple frames (e.g. S1, S2, S5) can span over multiple data transmission time frames (not shown), including spanning over and between interweaved additional data (e.g. S3, S4, data not included as a portion of the set of conforming data frames). Stated another way, larger payload data <NUM> can be broken up and distributed over a set of conforming data frames <NUM> individually transmitted over the specialized data network <NUM>, where, for instance, they can be reassembled at a data destination (not shown) into the overall contiguous payload data. This can occur when the payload data <NUM> is larger than a maximum amount of data that can be transmitted in a single time slot. In one non-limiting example, payload data that is too large to transmit in a single time slot can be an aperiodic transmission of data from the data source <NUM> to an avionics flight computer. As used herein, a set of data frames utilized with aspects of the disclosure described here will be referred to as "payload data frames.

The set of conforming data frames <NUM> can include a specialized header frame <NUM>, and a set of specialized data frames, such as the described payload data frames <NUM>. In one non-limiting example, the size of each conforming data frame of the specialized data network <NUM> can be <NUM> bits. Alternatively, the size of each conforming data frames the specialized data network <NUM> can be of any size.

The specialized header frame <NUM> can include the specialized header <NUM>. The specialized header can include various identifying information such as, but not limited to, a label information <NUM>, an identification information <NUM>, a single bit indicator (SBI) <NUM> and a number of expected or to-be-delivered set of payload data frames <NUM>. The label information <NUM> can include a sequence of numbers that can identify the groupings of data and distinguish one set or frame of conforming data from another set or frame of conforming data. The identification information <NUM> can be any identifying information such as, but not limited to, a data group number, a data sequence number, a data source <NUM> status, or any other identifying information. In another non-limiting example, the number of payload data frames <NUM> can be a real number that identifies the number of payload data frames <NUM> that are being, or will be, transmitted and containing the payload to be reassembled. For instance, in the illustrated example, the specialized header frame <NUM> or the number of payload data frames <NUM> can define that three conforming data frames (e.g. S <NUM>, S2, and S5) will be or are being transmitted to complete a data payload delivered over the three frames (S1, S2, S5) and reassembled by the data destination <NUM> (not shown). While a singular special header frame <NUM> is shown, non-limiting aspects of the disclosure can be included wherein each data frame, or a subset of conforming data frames, can include a specialized header frame <NUM> either preceding the respective data frame, or included as a header for that respective data frame.

The information contained within the specialized header frame <NUM> can be transmitted from the data source <NUM> to the data destination <NUM>, to inform them on the size, type, and group numbers of the payload data frames <NUM>.

The specialized header frame <NUM> can be defined to either be extended or shortened. In some instances, it can be beneficial to utilize a shortened specialized header frame <NUM> that can give the data destination <NUM> only identifying information of the conforming data frame <NUM>, while in other instances it can be beneficial to use an extended specialized header frame <NUM> that can give the data destination <NUM> all identifying information of the expected payload data frames <NUM>. In the case of the shortened specialized header frame <NUM>, an SBI <NUM> can be used. In one non-limiting example, the SBI <NUM> can be included as one (or more) bit(s) of the header section or portion of a conforming data frame <NUM>, and the remainder of the header section can include payload data. In this sense, a receiver of the conforming data frame <NUM> would know not to read or interpret the full header, but rather interpret the remainder of the header (e.g. the non-SBI <NUM> portion of the "header") as payload data.

The specialized data network <NUM> can transmit the specialized header frame <NUM>. Upon receipt of the specialized header frame <NUM> by an intended data destination <NUM>, the data destination <NUM> can receive and "read" the specialized header frame <NUM> to determine various identifying factors of the forthcoming payload data frames <NUM> to be received. The identifying factors can include, but not limited to, a size of the data or payload, a location of the taken data, a time or timestamp, or any other identifying information. In one non-limiting example the data destination <NUM>, in response to receiving the specialized header frame <NUM>, can be "primed" or "ready" itself to identify and receive the forthcoming set of payload data frames <NUM>. In one non-limiting example, the set of payload data frames <NUM> can be identified or identifiable by way of a defined data characteristic of the payload data frames <NUM>, such as each of the set of payload data frames <NUM>, and specialized header frame <NUM> can include a predetermined indicator by way of the SBI <NUM>. In this sense, the data destination <NUM> can then listen, or expect payload data, or identifying information from the data source <NUM> for as long as identified in, or identified by, the SBI <NUM>. It will be appreciated that the SBI <NUM> of the specialized header frame(s) <NUM>, and the payload data frame(s) <NUM> can both be used in the same way disclosed herein.

A subset of data frames S1-S5 can include one or more of payload data frames <NUM> indicated by the number "<NUM>", or interweaved data frames <NUM> indicated by the number "<NUM>" (e.g. data frames not included in the payload data frames <NUM> as defined herein, and wherein the identified SBI <NUM>, which may just be a portion of the header of the interweaved data frames <NUM> indicates the interweaved data frame <NUM> as not included in the set of payload data frames <NUM>). In this sense, the interweaved data frames <NUM> can be interwoven with the payload data frame <NUM> transmissions on the specialized data network <NUM>, and will be ignored or not acted upon by data destinations <NUM> expecting or receiving the payload data frames. The ARINC system can have a predetermined configuration that can indicate to the data destination <NUM> of what SBI <NUM> indicates the payload data frames <NUM>, and which SBI <NUM> indicates the interweaved data frames <NUM>. The interweaved data frames <NUM> can reference an interweaved specialized header frame (not shown) in the same way that the payload data frames <NUM> can reference the specialized header frame <NUM>. The interweaved specialized header frame can include the SBI <NUM> that can indicate it as being the interweaved specialized header frame, such that the data destination <NUM> can treat the interweaved specialized header frame in the same way that it treats the interweaved data frame <NUM> outlined herein.

The number of payload data frames <NUM> identified in the specialized header frame <NUM> can match the number of payload data frames <NUM> received or requested by the data destination <NUM> from the data source <NUM>.

The payload data frames <NUM>, and interweaved data frames <NUM> can be identified by the data destination(s) <NUM> as relevant or non-relevant data by way of the SBI <NUM>. The SBI <NUM> can most simply be a single bit binary identifier. For instance, an SBI <NUM> of binary one can indicate the received or transmitted data frame as a payload data frame <NUM>, while an SBI <NUM> of binary zero can indicate the received or transmitted data frame as interweaved data frames <NUM>, or simply non-payload data frames <NUM> as explained herein. Alternatively, this relationship can be flipped such that an the SBI <NUM> of binary zero can indicate the received or transmitted data frame as a payload data frame <NUM>, while the SBI <NUM> of binary one can indicate a received or transmitted data frame as interweaved data frames <NUM>. While a single bit indicator <NUM> is described, non-limiting aspects of the disclosure can be included wherein more than only one bit can be utilized to identify payload data frames <NUM> from interweaved data frame <NUM>. An indicator that can have more than only one bit can be used to conform to any ARINC system specification. This concept is discussed further herein.

The specialized header frame <NUM> may further include a number of transmission subsets (not shown) defined by the number of separate data transmissions that will occur before the entirety of the payload data <NUM> has been received by the data destination <NUM>. This can be included in instances where the data can be broken up over time, or when interweaved data frames <NUM> interrupt the data transmission. In either case, a second specialized header frame <NUM> can be transmitted to indicate to the data destination <NUM> that the incoming data transmissions refer back to, or continue from the payload data frames <NUM> already received by the data destination <NUM> that refer to or were indicated by the specialized header frame <NUM>. For example, the specialized header frame <NUM> can indicate to the data destination that the there will be <NUM> transmission subsets to require the entirety of the payload data <NUM> to be transmitted. The second specialized header frame <NUM> can indicate that it is transmission subset <NUM> out of <NUM>, the third specialized header frame (not shown) can indicate that it is transmission subset <NUM> out of <NUM>, and the fourth specialized header frame (not shown) can indicate that it is transmission subset <NUM> out of <NUM>. Alternatively, indicating the number of transmission subsets in the specialized header frame <NUM> can be forgone completely. For example, the entirety of the payload data <NUM> can be transmitted in a single transmission. In this case, the specialized header frame <NUM> can forgo indicating the number of transmission subsets as there is only one transmission. Alternatively, the data destination <NUM> can store the payload conforming data frames <NUM>, and the specialized header frame <NUM> in internal memory (not shown) and utilize the SBI <NUM> of subsequent data transmissions, whether they are interrupted as outlined herein or not, to indicate whether or not they are the conforming data frames <NUM>. It will be appreciated that many possibilities exist.

In the illustrated example, data subsets S1, S2, S5 can be the payload data frames <NUM> that can contain the payload data <NUM>, and the data subsets S3, S4 can be the interweaved data frames <NUM> that can include one or more interweaved data payload <NUM>. Each data subset S1, S2, S5 of the payload data frames <NUM> can be identified by, for example, an odd SBI <NUM> indicator or value, while each data subset S3, S4 of the interweaved data frames <NUM> can be identified by, for example, a different SBI <NUM> indicator or value, such an even SBI <NUM> indicator or value. While odd and even indicators are described, alternative indicators, including but not limited to, flagging, true or false indicators, or the alternative indication (e.g. the payload data frames indicated by even SBI <NUM> indicator or value), can be included in aspects of the disclosure. It will be appreciated that that there can be any number of data subset S1-S5 with any number of payload data frames <NUM>, or interweaved data frames <NUM>.

In the illustrated example, the interweaved data frames <NUM> of the data subsets S3, S4 can include interweaved data payload <NUM> defined by data that does not match what the data destination <NUM> is currently searching for, or expecting to receive the CRC <NUM>, or a parity bit <NUM>. The parity bit <NUM> can be defined by a bit added to the end of a data frame that can ensure that the total number of <NUM>-bits in the string is even or odd. The parity bit <NUM> can be used as a simple check bit at the end of a data frame, while the CRC <NUM> can be used as a more comprehensive check at the end of the data transmission. The payload data frames <NUM> of the data subsets S1, S2, S5 can include payload data <NUM> that the data destination <NUM> can receive and store for various avionic operations, the CRC <NUM>, or the parity bit <NUM>.

The data destination <NUM> can read the SBI <NUM> of each received data frame, and compare the SBI <NUM> received with a predetermined indicator of whether the data frame is one of the set of specialized data (e.g. the payload data frame <NUM> group identified). In one non-limiting example, it can be predetermined that an SBI <NUM> of binary one is indicative that the data frame received is one of the payload data frames <NUM>, whereas it can be predetermined that an SBI <NUM> of binary zero is indicative that the data frame received is not one of the interweaved data frames <NUM>. If the determination or comparison of the SBI <NUM> indicates a received data frame is one of the set of payload data frames <NUM>, the data destination <NUM> can receive the payload data frame <NUM> and perform some additional function, such as storing the payload data in a memory, assembling the data into a contiguous data file, performing processing functions on the data, or the like. In one non-limiting example an EFB can receive flight data by way of aspects of the disclosure, and delivered by way of the set of payload data frames <NUM>, wherein a flight computer can receive the flight data and, for instance, schedule or flight in accordance with a flight plan defined by the flight data. If the determination or comparison of the SBI <NUM> indicates a received data frame is not one of the set of payload data frames <NUM> and can therefore be the interweaved data frame <NUM>, the data destination <NUM> can chose to ignore the interweaved data frames <NUM>, or the interweaved specialized header frame and continue searching for, listening for, or determining whether future data frames received are part of the set of payload data frames <NUM>. Alternatively, the data destination <NUM> can decide to inform the user of the avionics system of the interweaved data frame <NUM> via a user interface or any other known notification device.

The specialized data network <NUM> can allow for an increased number of bits dedicated to the payload data <NUM>. Conventional data networks can require that a large portion (e.g., around <NUM>%) of the data frame be used by the header, the CRC (or the parity bit), or a source / destination identifier (SDI) while the rest can be used for payload data transmission. The specialized data network <NUM> can utilize a specialized header <NUM> that can use a reduced number of bits (e.g., <NUM> bit in the case of the SBI <NUM>, or lesser multiple bits when compared to the conventional data network) and the parity bit <NUM> which can be forgone altogether. Additionally, if the conforming data frame <NUM> includes a CRC <NUM>, the CRC <NUM> can be interweaved with additional data (e.g., payload data <NUM>). With that being said, in a <NUM> bit system, the specialized data network can utilize a maximum of <NUM> of the <NUM> bits for the payload data <NUM>, or around <NUM>% of the transmission can be used for the payload data <NUM>.

<FIG> is a schematic view of the specialized data network <NUM> that can include multiple data groups <NUM>, <NUM>, <NUM>, <NUM> transmitted over multiple frames or time slots TS1-TS6. The data groups <NUM>, <NUM>, <NUM> can each be periodic data groups from different sensors, or locations around the aircraft <NUM>. In contrast, the data frames <NUM> can include a larger data transmission that is broken up over multiple time slots, in accordance with aspects of the disclosure. In one non-limiting aspect, the data frames <NUM> can include data being transmitted across the specialized data network <NUM> from the flight computer to the EFB. The data frames <NUM> can be either aperiodic or periodic Each data group <NUM>, <NUM>, <NUM>, <NUM> can indicate to the data destination <NUM> of the origin, size, and type of the data or respective payloads. The data frames <NUM> can include the aforementioned information as part of the specialized header frame(s) <NUM>. While the specialized header frame(s) <NUM> are shown transmitted during each time slot TS3-TS6, aspects of the disclosure can be included wherein only a subset of time slots include the specialized header frame(s) <NUM>. During operation of the aircraft <NUM>, the data destination <NUM> may send out requests to the data sources <NUM> for different periodic data groups <NUM>, <NUM>, <NUM>. In this non-limiting example, data groups <NUM>, <NUM>, <NUM> can schematically represent periodic data, but aperiodic data can be included as data groups <NUM>, <NUM>, <NUM>. Some periodic data groups <NUM>, <NUM>, <NUM> can be larger or smaller than others. For example, the first, second, and third data groups <NUM>, <NUM>, <NUM> can be transmitted over a subset of the time slots (shown as TS1 and TS2, possibly by concatenating the data frames in a single time slot).

Each data group <NUM>, <NUM>, <NUM>, <NUM> can include one or more specialized header frame <NUM>, and one or more payload data frame <NUM> which can further include one or more SBI <NUM>, one or more payload data <NUM>, one or more CRC <NUM>, or one or more parity bit <NUM>. The SBI <NUM> and the parity bit <NUM> of each of the payload data frames <NUM>, of each data group <NUM>, <NUM>, <NUM>, <NUM>, can be, for example, <NUM> bit each, while the payloads <NUM> may use any percentage of the remaining <NUM> bits (in the <NUM> bit frame example). Alternatively, the specialized header <NUM>, and the CRC <NUM> can be larger than <NUM> bit each. Further, the parity bit <NUM> can be excluded from the payload data frames <NUM> such that <NUM> bits of the <NUM> bits can be allocated to payload data <NUM>. The payloads <NUM> can be of varying sizes depending on the payload data frame <NUM> from the data source <NUM>. In some instances, the payload data frame <NUM> can take longer than the allocated time slot (TS1-TS6) to transmit the payload data frame <NUM>. In this instance, the data grouping <NUM>, <NUM>, <NUM>, <NUM> can spill over to subsequent time slots (TS1-TS6). In each subsequent time slot allotted for transmission of the data grouping <NUM>, <NUM>, <NUM>, <NUM>, the specialized header frame <NUM> can be presented then the remaining payload data frames <NUM> that can include the SBI <NUM> can reference the specialized header frame <NUM> such that the data destination <NUM> can continue to store the payload data <NUM> until the transmission is over no matter how many time slots (TS1-TS6) are needed to complete the full data payload transmission. As illustrated, the third and fourth data groupings <NUM>, <NUM> extend over multiple time slots TS1-TS6. When the specialized data network <NUM> is unable to transmit all of the specialized header frames <NUM>, and the payload data frames <NUM> within a single defined time slot TS1-TS6, the specialized data network <NUM> can transmit the remaining specialized header frames <NUM>, and payload data frames <NUM> in a subsequent, or future time slot TS1-TS6.

The data source <NUM> can package the data groups <NUM>, <NUM>, <NUM>, <NUM> in such a way that the data destination <NUM> can receive multiple full, or partial, data groups <NUM>, <NUM>, <NUM>, <NUM> in a single <NUM> bit time slot TS1-TS6. For example, looking at only the first time slot TS1 and the second time slot TS2, the specialized data network <NUM> can include full data groups <NUM>, <NUM> and a partial of the data group <NUM> in the first time slot TS1. The remaining portion of the data group <NUM> can then be received or requested by the data destination <NUM> in subsequent time slots, for example, the second time slot TS2. The remaining parts of the data group <NUM> can be presented in the second time slot TS2 by resending the specialized header frame <NUM>, the remaining payload data frames <NUM>, the CRC <NUM>, and the parity bit(s) <NUM>.

A white space <NUM> (e.g. otherwise unallocated or unutilized data transmission capacity of the specialized data network <NUM>) can follow the CRC <NUM> (e.g., the end of the data transmission for a specific group) of any one or more of the data groups <NUM>, <NUM>, <NUM>, <NUM>. The white space <NUM> can be defined by the absence of transmission, or in other words, no grouped data is going into or out of either the data source <NUM> or the data destination <NUM>. Alternatively, it can be beneficial to reduce or eliminate all white space <NUM>. This can be done by after termination of the transmission or request of the data group <NUM>, <NUM>, <NUM>, <NUM>, and delivering or transmitting (or beginning to partially deliver) the subsequent data group <NUM>, <NUM>, <NUM>, <NUM> instead of waiting until the next time slot TS1-TS6. For example, it can be beneficial to transmit or request the fourth data group <NUM> after termination of the third data group <NUM> in the first white space <NUM> instead of transmitting or requesting it in the third time slot TS3 as shown. It will be appreciated that this can be applied to any subsequent conforming data frames <NUM>. For example, after termination of the fourth data group <NUM>, a fifth data set (not shown), or any of the prior data groups <NUM>, <NUM>, <NUM> can be delivered or transmitted (or beginning to partially deliver) in the second white space <NUM>. Alternatively, the white space <NUM> disclosed herein can be filled with an empty data set defined by a data set of data that can be completely ignored, or discarded by the data destination <NUM> (e.g., a data set of all <NUM>'s). This can provide the same effect as the use of the white space <NUM> as the data destination <NUM> will interpret the empty data set to be the same as a set of interweaved data. The data destination <NUM> will ignore the empty data set an continue looking for specialized header frames <NUM>, or payload data frames <NUM>, therefore, giving the empty data set the same use as the white space <NUM>.

The specialized data network <NUM> can include the various specialized components outlined herein that increase the overall efficiency of data transmission across the specialized data network <NUM> of the aircraft <NUM>. The specialized data network <NUM> can allow for a larger percentage of bits of a potential <NUM> bit data frame to be allocated toward data transfer of the payload. For example, conventional A429 systems data transfer can allow for <NUM>% of the <NUM> bits to be allocated for payload transfer. The specialized data network <NUM> can allow for data transfer where up to <NUM> of the <NUM> bits (or for example, <NUM> bit, if utilizing the CRC <NUM>) are allocated for payload transfer. It will be appreciated that the specialized data network <NUM> can be applied to any size system and still produce a more efficient data transfer system. It will be appreciated that this specialized data network can be applied to other ARINC systems with differing sizes and should not be limited to A429 systems.

In some ARINC systems, the SBI <NUM> can be more than <NUM> bit, defined by the first bit being in accordance with the binary identifier outlined herein, while the subsequent bits are bits to be ignored. This can be necessary in some ARINC systems, as the SBI <NUM><NUM> bit, placed next to the payload data <NUM> bits can create a conflicting bit-sequence, such as a conflicting or "collision" when coinciding with another predetermined bit sequence. For example, the ARINC system can include an executable demand that can be executed when the first <NUM> bits of a data frame read "<NUM>", so if the SBI <NUM> is "<NUM>" and the first two bits of the payload data <NUM> are "<NUM>", the ARINC system can read this is the executable demand instead of, or in addition to, the SBI <NUM> and the payload data <NUM> as it should. The same can occur in another relationship, wherein, for instance, and executable demand is received by the data destination <NUM> as a payload data frame <NUM>.

Non-limiting aspects of the disclosure can be included to prevent the confliction or collision instances by way of a configuration file applied in the specialized data network <NUM>. For example, a configuration file can be implemented and define a predetermined set or list of potentially conflicting bit streams such that, upon receiving a potentially conflicting bit stream, the data destination <NUM> can take additional actions or processes to ensure it is interpreted as desired. For instance, in the above-mentioned example, a data destination <NUM> can interpret the first <NUM> bits to be the SBI <NUM> by reading the potentially conflicting bit stream (e.g. "<NUM>", and then reading the following bits which can be enabled, operative, or otherwise configured or generated to confirm the intention of the bit stream in question. In this sense, collisions can be avoided, and the SBI <NUM> can effectively be utilized with addition bit indicators for a subset of possible bit streams that may result in collision or conflict. While these aspects would decrease the overall number of bits left for the payload data <NUM> for this subset of possible bit streams that may result in collision, the bits left for the payload data <NUM> can still be expanded when compared to conventional ARINC systems and allow, for example, for <NUM> bits of the <NUM> bits to be allocated for the payload data (and well as expanded in any payload data frames <NUM> without possibly colliding bitstreams). It will be appreciated that this is a non-limiting example, and the configuration file can be applied to any ARINC system and designate the SBI <NUM> to be any number of bits as required by the ARINC system.

An additional improvement can be that the specialized data network <NUM> can reduce or eliminate white (or otherwise unutilized or underutilized) space <NUM> and can allow for multiple data groups <NUM>, <NUM>, <NUM>, <NUM> to be either transmitted, or received from either the data source <NUM> or the data destination <NUM> consecutively or concatenated in the same time slot TS1-TS6. This can further increase the overall efficiency of the data transfer system for the aircraft <NUM>.

<FIG> is a flow diagram of the method <NUM> of transmitting a set of payload data frames <NUM> in a specialized data network <NUM> in accordance with <FIG>. During operation of the aircraft, there can be a request or transmission of either aperiodic or periodic conforming data frames <NUM>. When this occurs, the data source <NUM> can generate at least one specialized header frame <NUM> indicating imminent data transfer of the set of payload data frames <NUM>, at <NUM>. From there, at least one specialized header frame <NUM> can be provided, or transmitted to the data destination <NUM> by way of the specialized data network <NUM>, at <NUM>. The payload data frames <NUM> can then be generated at the data source <NUM>, and each set of payload data frames <NUM> can be identified by an SBI <NUM>, at <NUM>. The subset of payload data frames <NUM> can then be provided to the data destination <NUM> by way of the specialized data network <NUM>, at <NUM>. The subset of payload data frames <NUM> can then be identified by the data destination <NUM> by way of the SBI <NUM>, at <NUM>. Further, each subset of payload data frames <NUM> can then be stored in various memory components such as, but not limited to, RAM, ROM, flash memory, or one or more different types of portable electronic memory, such as discs, DVDs, CD-ROMs, etc., or any suitable combination of these types of memory, at <NUM>. Processing operations can then be performed on the one or more subsets of payload data frames <NUM>, at <NUM>. Processing operations can be done by way of a controller module.

The sequence depicted is for illustrative purposes only and is not meant to limit the method <NUM> in any way as it is understood that the portions of the method can proceed in a different logical order, additional or intervening portions can be included, or described portions of the method can be divided into multiple portions, or described portions of the method can be omitted without detracting from the described method. For example, the method <NUM> can further include determining if the full set of payload data frames <NUM> can be presented in a single time slot (e.g. TS3), and if it cannot be, presenting the remaining payload data frames <NUM> in a subsequent time slot (e.g. TS4, TS5, TS6, etc.).

Many other possible aspects and configurations in addition to that shown in the above figures are contemplated by the present disclosure.

To the extent not already described, the different features and structures of the various aspects can be used in combination with others as desired. That one feature cannot be illustrated in the aspects is not meant to be construed that it cannot be, but is done for brevity of description. Thus, the various features of the different aspects can be mixed and matched as desired to form new aspects, whether or not the new aspects are expressly described. All combinations or permutations of features described herein are covered by this disclosure.

Claim 1:
A method (<NUM>) for transmitting a set of conforming data frames (<NUM>) in a specialized data network (<NUM>), the method comprising:
providing, at a data source (<NUM>), a specialized header frame (<NUM>) including imminent data transfer of the set of conforming data frames (<NUM>) to a data destination, by way of the specialized data network
generating, at the data source, the set of conforming data frames, with each data frame of the set of conforming data frames is indicated as one of the set of conforming data frames by a respective single bit indicator (SBI) (<NUM>);
providing (<NUM>) at least a subset (S1, S2, S3, S4, S5) of the conforming data frames (<NUM>) to the data destination (<NUM>), by way of the specialized data network (<NUM>); and
providing, by a set of other data sources (<NUM>), the another set of data frames (<NUM>) indicated as not one of the set of conforming data frames (<NUM>) by the single bit indicator (<NUM>), wherein the another set of data frames (<NUM>) are interweaved with the subset (S1, S2, S3, S4, S5) of conforming data frames (<NUM>) during transmitting, and wherein the another set of data frames (<NUM>) are ignored by the data destination (<NUM>).