Patent Description:
In an aircraft, measurement systems typically include multiple devices distributed throughout the aircraft to observe various aircraft operations. These measurement systems often need to be accurately synchronized in time such that events measured by one device can be communicated to another device. In this way, measurement systems can correlate events measured by spatially separated devices.

Current synchronization solutions can include network time protocol (NTP) and precision time protocol (PTP). However, such protocols can include accuracy limitations and induce high processor loads. While a global position system (GPS) receiver can be used at each device of the measurement system, outfitting such hardware can be costly, as well as, less reliable due to GPS signal unavailability.

<CIT> describes a synchronization process that comprises attaching time stamps to messages in a wireless communications system.

Claim <NUM> defines a computer-implemented method of providing time reference synchronization for an aircraft system. In the following, apparatus and/or methods referred to as embodiments that nevertheless do not fall within the scope of the claims should be understood as examples useful for understanding the invention. The advantages of various examples will become better understood with reference to the following description and appended claims. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate examples of the present disclosure and, together with the description, serve to explain the related principles.

Detailed discussion of examples directed to one of ordinary skill in the art are set forth in the specification, which makes reference to the appended figures, in which:.

Reference now will be made in detail to embodiments of the present disclosure, one or more example(s) of which are illustrated in the drawings. Each example is provided by way of explanation of the present disclosure, not limitation of the present disclosure. In fact, it will be apparent to those skilled in the art that various modifications and variations can be made in the present disclosure without departing from the scope of the present disclosure. Thus, it is intended that the present disclosure covers such modifications and variations as come within the scope of the appended claims and their equivalents.

Example aspects of the present disclosure are directed to systems and methods of providing time reference synchronization for an aircraft system. For instance, an aircraft can include a master clock computing system and one or more data acquisition system(s) (e.g., accelerometer, tachometer) associated with a component (e.g., engine) of the aircraft. The master clock computing system can encode a specialized, unique signal with time synchronization information (e.g., a reference time, local time). The master clock computing system can send the signal to the data acquisition system(s). For example, the master clock computing system can send the signal via one or more power line(s) of the aircraft to leverage the existing aircraft hardware and avoid adding extra cable.

The data acquisition system(s) can receive the signal including the time synchronization information, for example, via the power line(s) and filter the signal from noise. The data acquisition system(s) can verify that the signal is a signal-of-interest by examining, at least a first portion of, the signal. The data acquisition system(s) can identify and extract the time synchronization information based, at least in part, on another portion of the signal. The data acquisition system(s) can synchronize a set of data associated with a component of the aircraft with the time synchronization information and send the synchronized data to another computing system (e.g., ground-based system, data repository). In this way, the data acquisition systems can use time synchronization information from a centralized master clock computing system to measure local events, thereby achieving highly accurate time referencing, without needing a real clock on each of the individual data acquisition system(s).

More particularly, the master clock computing system can encode a signal with time synchronization information to create the specialized signal. For instance, the signal can include a carrier wave, such as a high frequency carrier wave. The signal can include a first portion and a second portion. The first signal portion can include at least one of a preamble portion, a time reference portion, and/or a post-amble portion, each including one or more signal cycle(s). The second signal portion can include a time synchronization portion, which can include one or more pulse(s). In some implementations, at least one cycle and/or pulse can be amplitude shift keyed.

The master clock computing system can send the signal (with the time synchronization information) to one or more data acquisition system(s). For example, the master clock computing system can modulate the one or more power line(s) associated with the data acquisition system(s) with the signal (e.g., including the carrier wave). In this way, the time synchronization information can be provided to the data acquisition system(s) using power lines already existing in the aircraft, without adding additional cables to the aircraft for time synchronization. The data acquisition system(s) can receive the signal, including the time synchronization information. For example, the power line(s) can be configured to feed the signal to the data acquisition system(s) (e.g., a channel, a sensor ADC, etc. associated therewith), which can sample the signal at a multiple of the carrier frequency.

The data acquisition system(s) can determine the time synchronization information by processing one or more individual portion(s) of the signal. To do so, the computing device(s) can verify the signal and identify the time synchronization information of the signal. For instance, as indicated above, the first portion of the signal can include, at least one of, a preamble portion, a time reference portion, and/or a post-amble portion. The data acquisition system(s) can verify that the signal is a specialized, unique signal from the master clock computing system by examining the preamble portion, the time reference portion, and/or the post-amble portion and its associated structure/cycle(s). For example, the data acquisition system(s) can compare the structure/cycle(s) included in those portions to one or more threshold(s) that are indicative of whether the signal includes the time synchronization information. If the signal structure/cycle(s) are above the threshold, then the signal can be accepted. In this way, the first signal portion can indicate to the data acquisition system(s) that a specialized time synchronization signal is being sent to the data acquisition system(s). However, if the structure/cycle(s) are below the threshold, the data acquisition system can reject the signal (e.g., as error-ridden, corrupt, lacking time synchronization information).

The data acquisition system(s) can identify and extract the time synchronization information of the signal based, at least in part, on the second portion of the signal. More specifically, in some implementations, the data acquisition system(s) can identify the time synchronization information based, at least in part, on the time synchronization portion, including one or more time synchronization pulse(s). For example, the data acquisition system(s) can identify a local zero crossing associated with one or more of the time synchronization pulse(s) to identify the time synchronization information (e.g., a reference time, local time), as further described herein. The data acquisition system(s) can synchronize a set of data acquired by the data acquisition system(s) (e.g., associated with an engine component, auxiliary power unit) with the time synchronization information. Moreover, the data acquisition system(s) can send a message including the time synchronized data to another computing system (e.g., ground-based data center).

The systems and methods according to example aspects of the present disclosure provide an efficient, cost-effective approach for providing accurate time references for acquired data. Particularly, systems and methods can provide simplified time synchronization information by leveraging the existing aircraft hardware. Replicated electronics across the systems can lead to similar delays for each data acquisition system, which can be easily predicted and compensated for during synchronization and/or analysis. Moreover, the systems and methods employ simple software decoding of the time synchronization information to incur very little processor load. In this way, the systems and methods according to example aspects of the present disclosure have a technical effect of producing simple, highly accurate time synchronization using existing aircraft hardware, which can limit the bandwidth expended on time synchronization.

<FIG> depicts an example system <NUM> according to example embodiments of the present disclosure. As shown, the system <NUM> can include an aircraft <NUM> having one or more engine(s) <NUM>, a fuselage <NUM>, a master clock computing system <NUM>, and one or more data acquisition system(s) <NUM>.

As shown in <FIG>, the computing system <NUM> can include one or more computing device(s) <NUM> that can be associated with, for instance, an avionics system. The computing device(s) <NUM> can include various components for performing various operations and functions. For example, and as further described herein, the computing device(s) <NUM> can include one or more processor(s) and one or more memory device(s). The one or more memory device(s) can store instructions that when executed by the one or more processor(s) cause the one or more processor(s) to perform the operations and functions, for example, as those described herein for providing a time reference synchronization signal.

The computing device(s) <NUM> can be coupled to a variety of systems included on the aircraft <NUM>. For instance, the computing device(s) <NUM> can be coupled to the data acquisition system(s) <NUM> via one or more power line(s) <NUM> associated with the data acquisition(s) <NUM>. The power line(s) <NUM> can be those already existing on an aircraft <NUM>. In some implementations, the computing device(s) <NUM> can be coupled to a variety of systems (including the data acquisition(s) <NUM>) over a network. The network can include a data bus or a combination of wired and/or wireless communication links.

The data acquisition system(s) <NUM> can be configured to monitor and collect data with respect to one or more components of the aircraft <NUM>. The data acquisition system(s) <NUM> can include an accelerometer, tachometer, magnetic tachometer, optical tachometer, sensor, and/or any other suitable type of measurement device included on the aircraft <NUM>. By way of example, the data acquisition system(s) <NUM> can be associated with a component <NUM> of the engine(s) <NUM>, a component of an auxiliary power unit, etc. The data acquisition system(s) <NUM> can be configured to measure the vibration experienced by the component <NUM> of the aircraft <NUM> (e.g., engine gearbox, rotor, shaft).

<FIG> depicts an example system <NUM> according to example embodiments of the present disclosure. The system <NUM> can include the computing system <NUM> and one or more data acquisition system(s) <NUM>, which can include one or more computing device(s) <NUM>, as further described herein. As shown, the computing system <NUM> can include the computing device(s) <NUM>, which can be coupled to the data acquisition system(s) <NUM> via one or more power line(s) <NUM>. In some implementations, the data acquisition system(s) <NUM> can include a plurality of channels 202A-C such as, for instance, channels associated with a multi-channel analog-to-digital converter (ADC). In some implementations, the power line(s) <NUM> can be coupled to one or more of the channels 202A-C. By way of example, a first channel 202A can be associated with the receipt of a signal including time synchronization information, a second channel 202B can be associated with a tachometer, and/or a third channel 202C can be associated with an accelerometer.

The computing system <NUM> can be configured to provide a time reference synchronization signal to the data acquisition system(s) <NUM>. The computing device(s) <NUM> can be configured to send a signal <NUM>, including time synchronization information <NUM> to the data acquisition system(s) <NUM>. In some implementations, the computing device(s) <NUM> can be configured to send the signal <NUM> via one or more of the power line(s) <NUM> associated with the data acquisition system(s) <NUM>. The time synchronization information <NUM> can include data indicative of a local time <NUM>, a reference time, etc. Moreover, the computing device(s) <NUM> can be configured to encode the signal <NUM> such that it is a specialized signal that can indicate to the data acquisition system(s) <NUM> that it contains the time synchronization information <NUM>.

For instance, <FIG> depicts an example signal <NUM> according to example embodiments of the present disclosure. <FIG> includes a signal structure that is not intended to be limiting. The signal <NUM> can include a different structure than the one shown. The signal <NUM> can include more, less, and/or different portions, cycles, pulses, spaces, etc. than those shown in <FIG>. Moreover, the portions of signal <NUM> can be arranged in a different order than that shown in <FIG>.

In some implementations, the signal <NUM> can include a carrier wave <NUM> (e.g., a high frequency carrier wave). At least one cycle of the signal <NUM> can be amplitude shift keyed (e.g., varying amplitude of the signal <NUM> to change signal mode/state). The computing device(s) <NUM> can be configured to encode the signal <NUM> to include one or more state(s) such as, for example: a space (e.g., indicating no carrier present), a one (e.g., indicating carrier at full amplitude), and/or a zero (e.g., indicating carrier at half amplitude). Moreover, the computing device(s) <NUM> can be configured to encode the signal <NUM> to include a first signal portion <NUM> and/or a second signal portion <NUM>. In some implementations, the signal <NUM> can include a space <NUM> (e.g., equivalent to a plurality of bits) between the first portion <NUM> and the second portion <NUM>. For example, the space <NUM> can be equivalent to five bits.

The first signal portion <NUM> can include, at least one of, a preamble portion <NUM>, a time reference portion <NUM>, and/or a post-amble portion <NUM>. The preamble portion can include one or more first signal cycle(s) <NUM>. For instance, the one or more first signal cycle(s) <NUM> can include a plurality of carrier wave cycles decoded as ones. By way of example, the first signal cycles(s) <NUM> can include ten carrier wave cycles, as shown in <FIG>. The time reference portion <NUM> can include one or more second signal cycle(s) <NUM>. For instance, the one or more second signal cycle(s) <NUM> can include a multi-bit time reference (e.g., a plurality of carrier waves amplitude keyed shifted). For example, the second cycle(s) <NUM> can include ten carrier wave cycles (e.g., encoded at full amplitude, half amplitude), as shown in <FIG>. The post-amble portion <NUM> can include one or more third signal cycle(s) <NUM>. For instance, the third cycle(s) <NUM> can include a plurality of carrier wave cycles decoded as ones. The third cycles(s) <NUM> can include, for example, ten carrier wave cycles, as shown in <FIG>. The inclusion of the preamble portion <NUM>, the time reference portion <NUM>, and/or the post-amble portion <NUM> in the signal <NUM> can create a unique, specialized signal that can be analyzed by the computing device(s) <NUM> of the data acquisition system(s) <NUM> to verify that the signal <NUM> includes time synchronization information <NUM>, as further described herein.

The second portion <NUM> can include a time synchronization portion <NUM>. The time synchronization portion <NUM> can include one or more time synchronization pulse(s) <NUM>. For example, the time synchronization pulse(s) <NUM> can include one or more cycles decoded as ones, as shown in <FIG>. The second portion <NUM> (e.g., the time synchronization portion <NUM>) can include the time synchronization information <NUM>. For example, the one or more time synchronization pulse(s) <NUM> can be encoded with the local time <NUM>. As further described herein, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to process the second portion <NUM>, including the time synchronization portion <NUM>, to identify the time synchronization information <NUM>.

Returning to <FIG>, the computing device(s) <NUM> can be configured to encode the signal <NUM> with the time synchronization information <NUM>, such as in the first portion <NUM> and/or the second portion <NUM>. Additionally, and/or alternatively, the computing device(s) <NUM> can be configured to encode the signal <NUM> with the time synchronization information <NUM> in at least one of the preamble portion <NUM>, the time reference portion <NUM>, the post-amble portion <NUM>, and/or the time synchronization portion <NUM>.

In some implementations, the computing device(s) <NUM> can encode the signal <NUM> such that the computing device(s) <NUM> of the data acquisition system(s) <NUM> can verify that the signal <NUM> includes the time synchronization information <NUM> and also identify the time synchronization information <NUM>. For example, the one or more first signal cycle(s) <NUM>, the one or more second signal cycle(s) <NUM>, and/or the one or more third signal cycle(s) <NUM> can be encoded to verify that the signal <NUM> includes the time synchronization information <NUM>, as further described herein. The one or more time synchronization pulse(s) <NUM> can be encoded with a local time <NUM>, which can be used for data synchronization.

The computing device(s) <NUM> can be configured to send the signal <NUM> with the time synchronization information <NUM>, for example, to one or more computing device(s) <NUM> of the data acquisition system(s) <NUM>. By way of example, the signal <NUM> can include a carrier wave <NUM> (e.g., high frequency carrier wave) and the computing device(s) <NUM> can be configured to modulate the one or more power line(s) <NUM> associated with the data acquisition system(s) <NUM> with the signal <NUM>, including the carrier wave <NUM>. In this way, the time synchronization information <NUM> can be provided to the data acquisition system(s) <NUM> using power lines already existing in the aircraft <NUM>, without adding additional cables to the aircraft <NUM> for time synchronization. Moreover, the signal <NUM> can be associated with a short burst, which can lead to bandwidth limiting of the signal modulation to have little effect on the time synchronization information <NUM>.

The computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to receive the signal <NUM>, including the time synchronization information <NUM>. For example, the power line(s) <NUM> can be configured to feed the signal <NUM> to the data acquisition system(s) <NUM> (e.g., a channel 202A-C, a sensor ADC, etc. associated therewith), which can be configured to sample the signal <NUM> at a multiple of the carrier frequency.

The computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to analyze the signal <NUM> to extract the time synchronization information <NUM>. For instance, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to determine the time synchronization information <NUM> based, at least in part, on the signal <NUM>. In some implementations, this can be done based, at least in part, on at least one of the preamble portion <NUM>, the time reference portion <NUM>, the post-amble portion <NUM>, and/or the time synchronization portion <NUM>.

For example, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to verify that the signal <NUM> is encoded with time synchronization information <NUM>. In some implementations, this can based, at least in part, on at least one of the preamble portion <NUM>, the time reference portion <NUM>, and/or the post-amble portion <NUM>. More specifically, in some implementations, computing device(s) <NUM> can be configured to verify that the signal <NUM> is encoded with time synchronization information <NUM> based, at least in part, on at least one of the one or more first signal cycle(s) <NUM>, the one or more second signal cycle(s) <NUM>, and/or the one or more third signal cycle(s) <NUM>. For example, and as further described below, the computing device(s) <NUM> can be configured to compare the particular cycle structure of the first portion <NUM> with one or more thresholds <NUM> (shown in <FIG>) to confirm that the signal <NUM> includes the time synchronization information <NUM>.

In some implementations, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to identify the time synchronization information <NUM> based, at least in part, on the second portion <NUM>. More specifically, in some implementations, the computing device(s) <NUM> can be configured to identify the time synchronization information <NUM> based, at least in part, on the time synchronization portion <NUM>. For example, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to identify the time synchronization information <NUM> based, at least in part, on the one or more time synchronization pulse(s) <NUM>, as further described herein.

The computing device(s) <NUM> of the data acquisition system(s) <NUM> can be configured to synchronize a set of data <NUM>, acquired by the data acquisition system(s) <NUM>. For example, the data acquisition system(s) <NUM> can be configured to acquire the set of data <NUM> associated with one or more component(s) <NUM> (e.g., of engine <NUM>). The computing device(s) <NUM> can be configured to synchronize the set of data <NUM> with the time synchronization information <NUM>. In some implementations, the data acquisition system(s) <NUM> can be configured to synchronize data acquired from another device and/or data acquisition system <NUM>.

The computing device(s) <NUM> can be configured to send a message <NUM>, including the set of data <NUM> acquired by the data acquisition system(s) <NUM> and synchronized with the time synchronization information <NUM>. The message can be sent to a remote computing system <NUM> that can be remote from the data acquisition system(s) <NUM> and/or the aircraft <NUM>. For example, the remote computing system <NUM> can be associated with a ground-based data analysis system and/or repository.

<FIG> depicts a flow diagram of example method <NUM> for providing time reference synchronization for an aircraft system according to example embodiments of the present disclosure. <FIG> can be implemented by one or more computing device(s), such as the computing device(s) <NUM> and <NUM>. One or more step(s) of the method <NUM> can be performed while aircraft <NUM> is in-flight. In addition, <FIG> depicts steps performed in a particular order for purposes of illustration and discussion. Those of ordinary skill in the art, using the disclosures provided herein, will understand that the various steps of any of the methods disclosed herein can be modified, adapted, expanded, rearranged and/or omitted in various ways without deviating from the scope of the present disclosure.

At (<NUM>), the method <NUM> can include encoding a signal with time synchronization information. For example, the computing device(s) <NUM> of computing system <NUM> can encode the signal <NUM> with time synchronization information <NUM>. The signal <NUM> can include the first portion <NUM> and the second portion <NUM>. In some implementations, the first signal portion <NUM> can include at least one of the preamble portion <NUM>, the time reference portion <NUM>, and the post-amble portion <NUM>. The second signal portion <NUM> can include the time synchronization portion <NUM>. Additionally, and/or alternatively, the signal <NUM> can include a carrier wave <NUM> (e.g., high frequency carrier wave) and can include one or more cycle(s) and/or pulse(s) (e.g., <NUM>, <NUM>, <NUM>, <NUM>) as described herein. In some implementations, at least one cycle and/or pulse can be amplitude shift keyed.

At (<NUM>) and (<NUM>), the method <NUM> can include sending and receiving the signal including the time synchronization information. For example, the computing device(s) <NUM> of computing system <NUM> can send (e.g., via one or more power line(s)) the signal <NUM> with the time synchronization information <NUM> to one or more data acquisition system(s) <NUM>. The computing device(s) <NUM> of the data acquisition system(s) <NUM> can receive the signal <NUM> including the time synchronization information <NUM>, as described above.

At (<NUM>), the method can include filtering the signal. For instance, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can filter the signal <NUM> including the time synchronization information <NUM> to distinguish the first signal portion <NUM> and/or the second signal portion <NUM> from noise associated with the signal <NUM>. The computing device(s) <NUM> of the data acquisition system(s) <NUM> can filter the signal <NUM> to eliminate any noise and/or interference other than the signal <NUM> at the carrier frequency.

At (<NUM>), the method can include determining the time synchronization information. For instance, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can determine the time synchronization information <NUM> based, at least in part, on the first signal portion <NUM> and/or the second signal portion <NUM> of signal <NUM>. To do so, in some implementations, the computing device(s) <NUM> can verify that the signal <NUM> includes the time synchronization information <NUM> and identify the time synchronization information <NUM> of the signal <NUM>.

The computing device(s) <NUM> can verify the signal <NUM> based, at least in part, on the first portion <NUM>. As described above, the first portion <NUM> can include at least one of a preamble portion <NUM>, a time reference portion <NUM>, and a post-amble portion <NUM>. The computing device(s) <NUM> can verify the signal <NUM> based, at least in part, on at least one of the preamble portion <NUM>, the time reference portion <NUM>, and/or the post-amble portion <NUM>.

In some implementations, the computing device(s) <NUM> can verify the signal <NUM> based, at least in part, on one or more threshold(s) <NUM>. For example, the preamble portion <NUM> can include one or more first signal cycle(s) <NUM>, the time reference portion <NUM> can include one or more second signal cycle(s) <NUM>, and/or the post-amble portion <NUM> can include one or more third signal cycle(s) <NUM>. The computing device(s) <NUM> can determine whether the first signal cycle(s) <NUM>, the second signal cycle(s) <NUM>, and/or the third signal cycle(s) <NUM> (e.g., their associated amplitudes) are above one or more threshold(s) <NUM>. In some implementations, the one or more threshold(s) <NUM> can be indicative of whether the signal <NUM> includes the time synchronization information <NUM>. For instance, the computing device(s) <NUM> can accept the signal <NUM> as including the time synchronization information <NUM> when the first signal cycle(s) <NUM>, the second signal cycle(s) <NUM>, and/or the third signal cycle(s) <NUM> are above the one or more threshold(s) <NUM>. Such acceptance can indicate that the signal <NUM> does indeed include the time synchronization information <NUM>, the signal <NUM> is not corrupt or error-ridden, etc. In this way, the computing device(s) <NUM> can verify that the signal <NUM> includes the time synchronization information <NUM> when the cycles of the first portion <NUM> are above the threshold(s) <NUM> and accordingly accept such a signal.

Additionally, and/or alternatively, the computing device(s) <NUM> can reject the signal <NUM> when at least one of the first signal cycle(s) <NUM>, the second signal cycle(s) <NUM>, and/or the third signal cycle(s) <NUM> are below the one or more threshold(s) <NUM>. Such rejection can indicate an error and/or corruption of the signal <NUM> (e.g., associated with the first and/or second portions <NUM>, <NUM>) and/or the time synchronization information <NUM>. In some implementations, a rejection can indicate that the signal <NUM> fails to include the time synchronization information <NUM>.

The computing device(s) <NUM> of data acquisition system(s) <NUM> can also, and/or alternatively, identify and extract the time synchronization information <NUM> included in the signal <NUM>. The computing device(s) <NUM> can identify the time synchronization information <NUM> based, at least in part, on the time synchronization portion <NUM>. More specifically, in some implementations, the computing device(s) <NUM> can identify the time synchronization information <NUM> based, at least in part, on the one or more time synchronization pulse(s) <NUM>.

By way of example, as shown in <FIG>, the computing device(s) <NUM> can identify a local zero crossing <NUM> associated with one or more of the time synchronization pulse(s) <NUM> to determine a time <NUM>. The local zero crossing <NUM> can be a point where one or more of the time synchronization pulse(s) <NUM> crosses a reference axis (e.g., the zero axis shown in <FIG>). In some implementations, the computing device(s) <NUM> can identify the local zero crossing <NUM> based, at least in part, on an interpolation of two or more points associated with the local zero crossing <NUM>. For instance, the two or more points can include a first point associated with the local zero crossing <NUM> that is above the reference axis (e.g., the zero axis shown in <FIG>) and a second point associated with the local zero crossing <NUM> that is below the reference axis. The computing device(s) <NUM> can interpolate between the first point and the second point. The computing device(s) <NUM> can be configured to identify the time synchronization information <NUM> based, at least in part, on where the interpolation of the first and second points crosses the reference axis. Accordingly, the computing device(s) <NUM> can identify time synchronization information <NUM>, including a time <NUM> associated therewith.

Returning to <FIG>, at (<NUM>), the method can include synchronizing a set of data with the time synchronization information. For instance, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can synchronize the set of data <NUM> acquired by the data acquisition system(s) <NUM> with the time <NUM>. As described herein, the set of data <NUM> can be associated with a component <NUM> of the aircraft <NUM>. The computing device(s) <NUM> can synchronize the set of data <NUM> with the time <NUM> (e.g., a local time).

At (<NUM>), the method can include sending a message that includes the time synchronized set of data. For instance, the computing device(s) <NUM> of the data acquisition system(s) <NUM> can send the message <NUM> comprising the set of data <NUM> (acquired by the data acquisition system(s) <NUM>) synchronized with the time synchronization information <NUM>. The message <NUM> can be sent to the remote computing system <NUM> that can be remote from the data acquisition system(s) <NUM> and/or the aircraft <NUM>.

<FIG> depicts an example system <NUM> according to example embodiments of the present disclosure. The system <NUM> can include the computing system <NUM> and the data acquisition system(s) <NUM>, which can be configured to communicate between one another, as described herein. In some implementations, the system <NUM> can include the remote computing system <NUM>. The remote computing system <NUM> can be located onboard the aircraft <NUM>. In some implementations, the remote computing system <NUM> can be associated with the computing system <NUM>. In some implementations, the remote computing system <NUM> can be physically separated and remote from the data acquisition system(s) <NUM> and/or the computing system <NUM>. For instance, the remote computing system <NUM> can be associated with a ground-based system for analyzing and collecting aircraft data. The computing system <NUM> and the data acquisition system(s) <NUM> can be configured to communicate with the remote computing system <NUM> via one or more communications network(s) <NUM>. The communications network(s) <NUM> can include at least one of a SATCOM network, VHF network, a HF network, a Wi-Fi network, a WiMAX network, a gatelink network, and/or any other suitable communications network for transmitting messages to and/or from an aircraft.

The computing system <NUM> can include one or more computing device(s) <NUM>. The computing device(s) <NUM> can include one or more processor(s) 117A and one or more memory device(s) 117B. The one or more processor(s) 117A can include any suitable processing device, such as a microprocessor, microcontroller, integrated circuit, logic device, and/or other suitable processing device. The one or more memory device(s) 117B can include one or more computer-readable media, including, but not limited to, non-transitory computer-readable media, RAM, ROM, hard drives, flash drives, and/or other memory devices.

The one or more memory device(s) 117B can store information accessible by the one or more processor(s) 117A, including computer-readable instructions 117C that can be executed by the one or more processor(s) 117A. The instructions 117C can be any set of instructions that when executed by the one or more processor(s) 117A, cause the one or more processor(s) 117A to perform operations. In some embodiments, the instructions 117C can be executed by the one or more processor(s) 117A to cause the one or more processor(s) 117A to perform operations, such as any of the operations and functions for which the computing system <NUM> and/or the computing device(s) <NUM> are configured, one or more operations for providing time reference synchronization for an aircraft system (e.g., method <NUM>), as described herein, and/or any other operations or functions of the one or more computing device(s) <NUM>. The instructions 117C can be software written in any suitable programming language or can be implemented in hardware. Additionally, and/or alternatively, the instructions 117C can be executed in logically and/or virtually separate threads on processor(s) 117A.

The memory device(s) 117B can further store data 117D that can be accessed by the processors 117A. For example, the data 117D can include data associated with the signal <NUM> (and/or any portions thereof), the time synchronization information <NUM>, data associated with the data acquisition system(s) <NUM>, and/or any other data and/or information described herein.

The computing device(s) <NUM> can also include a network interface 117E used to communicate, for example, with the other components of the system <NUM>. The network interface 117E can include any suitable components for interfacing with one or more network(s), including for example, transmitters, receivers, ports, controllers, antennas, and/or other suitable components.

The data acquisition system(s) <NUM> can include one or more sensor(s) <NUM> and one or more computing device(s) <NUM>. As described herein, the sensor(s) <NUM> (e.g., accelerometer, tachometer, magnetic tachometer, optical tachometer, and/or any other suitable type of measurement device) can be configured to acquire data associated with one or more component(s) of aircraft <NUM>. The sensor(s) <NUM> can be associated with the computing device(s) <NUM>. In some implementations, the sensor(s) <NUM> can be configured to perform one or more functions of the computing device(s) <NUM>.

The computing device(s) <NUM> can include one or more processor(s) 220A and one or more memory device(s) 220B. The one or more processor(s) 220A can include any suitable processing device, such as a microprocessor, microcontroller, integrated circuit, logic device, and/or other suitable processing device. The one or more memory device(s) 220B can include one or more computer-readable media, including, but not limited to, non-transitory computer-readable media, RAM, ROM, hard drives, flash drives, and/or other memory devices.

The one or more memory device(s) 220B can store information accessible by the one or more processor(s) 220A, including computer-readable instructions 220C that can be executed by the one or more processor(s) 220A. The instructions 220C can be any set of instructions that when executed by the one or more processor(s) 220A, cause the one or more processor(s) 220A to perform operations. In some embodiments, the instructions 220C can be executed by the one or more processor(s) 220A to cause the one or more processor(s) 220A to perform operations, such as any of the operations and functions for which the data acquisition system(s) <NUM> and/or the computing device(s) <NUM> are configured, one or more operations for providing time reference synchronization for an aircraft system (e.g., method <NUM>), as described herein, and/or any other operations or functions of the one or more computing device(s) <NUM>. The instructions 220C can be software written in any suitable programming language or can be implemented in hardware. Additionally, and/or alternatively, the instructions 220C can be executed in logically and/or virtually separate threads on processor(s) 220A. The memory device(s) 220B can further store data 220D that can be accessed by the processors 220A. For example, the data 220D can include data associated with the signal <NUM> (and/or any portions thereof), the time synchronization information <NUM>, the set of data <NUM>, other data acquired and/or used by the data acquisition system(s) <NUM>, and/or any other data and/or information described herein.

The computing device(s) <NUM> can also include a network interface 220E used to communicate, for example, with the other components of the system <NUM>. The network interface 220E can include any suitable components for interfacing with one or more network(s), including for example, transmitters, receivers, ports, controllers, antennas, and/or other suitable components.

The circuitry configuration of the computing device(s) <NUM> and <NUM>, shown in <FIG>, is not intended to be limiting. For example, the computing device(s) <NUM> and/or <NUM> can include other processing circuitry and/or components to perform the functions described herein, than that shown in <FIG>. The computing device(s) <NUM> and/or <NUM> can include more, less, and/or different components than shown.

Although specific features of various embodiments may be shown in some drawings and not in others, this is for convenience only. In accordance with the principles of the present disclosure, any feature of a drawing may be referenced and/or claimed in combination with any feature of any other drawing.

Claim 1:
A computer-implemented method of providing time reference synchronization for an aircraft system, comprising:
receiving, by one or more computing devices (<NUM>) associated with a data acquisition system (<NUM>) of an aircraft (<NUM>), a signal (<NUM>) comprising time synchronization information (<NUM>), wherein the signal (<NUM>) comprises a first signal portion (<NUM>) and a second signal portion (<NUM>);
wherein the first signal portion (<NUM>) comprises a preamble portion (<NUM>), a time reference portion (<NUM>), and a post-amble portion (<NUM>), and wherein the second signal portion (<NUM>) comprises a time synchronization portion (<NUM>);
wherein the preamble portion (<NUM>) comprises one or more first signal cycles (<NUM>), the time reference portion (<NUM>) comprises one or more second signal cycles (<NUM>), and the post-amble portion (<NUM>) comprises one or more third signal cycles (<NUM>);
filtering, by the one or more computing devices (<NUM>), the signal (<NUM>) comprising the time synchronization information (<NUM>) to distinguish the first signal portion (<NUM>) and the second signal portion (<NUM>) from noise associated with the signal (<NUM>);
verifying, by the one or more computing devices (<NUM>), whether the signal is encoded with time synchronization information by determining whether the one or more first signal cycles (<NUM>), the one or more second signal cycles (<NUM>), and the one or more third signal cycles (<NUM>) are above one or more thresholds (<NUM>), wherein the one or more thresholds (<NUM>) are indicative of whether the signal (<NUM>) comprises the time synchronization information (<NUM>);
identifying, by the one or more computing devices (<NUM>), the time synchronization information (<NUM>) based at least in part on the first signal portion (<NUM>) and the second signal portion (<NUM>); and
synchronizing, by the one or more computing devices (<NUM>), a set of data (<NUM>) acquired by the data acquisition system (<NUM>) with the time synchronization information (<NUM>);
wherein the signal (<NUM>) comprises a high frequency carrier wave (<NUM>) comprising one or more cycles (<NUM>, <NUM>, <NUM>), wherein at least one cycle (<NUM>, <NUM>, <NUM>) is amplitude shift keyed.