Patent Description:
Contemporary gas turbine engines, such as gas turbine engines for aircraft, may generate large quantities of engine data during operation. In some cases, it may be necessary or desirable to transmit portions of the engine data to offboard communications systems for remote monitoring of the gas turbine engine. With the proliferation of regulations governing data localization and data security, strict compliance with local regulations may be cumbersome, as requirements for data residency and the use of encryption technologies are not uniform throughout the world. Accordingly, what is need are improved systems and methods for controlling data communications between "connected" gas turbine engines and offboard communications systems.

<CIT> and <CIT> disclose arrangements of the prior art.

In an aspect of the present invention, a communication system of a gas turbine engine for an aircraft is provided according to claim <NUM>.

In any of the aspects or embodiments described above and herein, the processing circuitry is configured to receive at least one of a GPS location, a cellular location, or a city pair location to determine the location of the gas turbine engine.

In any of the aspects or embodiments described above and herein, the processing circuitry is configured to selectively record a portion of the generated engine data based on the data management strategy.

In any of the aspects or embodiments described above and herein, the data management strategy includes an encryption strategy, and the processing circuitry is configured to encrypt the first portion of the recorded engine data with a first encryption rule of the encryption strategy.

In any of the aspects or embodiments described above and herein, the processing circuitry is configured to selectively record the generated engine data to the memory system as a first data stream, including the first portion of the recorded engine data, and a second data stream which is different than the first data stream and wherein a data stream content of the first data stream and the second data stream is based on the data management strategy.

In any of the aspects or embodiments described above and herein, the processing circuitry is configured to encrypt recorded engine data of the first data stream with the first encryption rule of the encryption strategy and to encrypt recorded engine data of the second data stream with a second encryption rule of the encryption strategy, which is different than the first encryption rule.

In any of the aspects or embodiments described above and herein, the offboard system includes a plurality of ground stations and the processing circuitry is configured to direct the communication interface to transmit the first portion of the recorded engine data to a particular ground station of the plurality of ground stations based on the data management strategy.

In any of the aspects or embodiments described above and herein, the processing circuitry is configured to direct the communication interface to receive an updated data management strategy, associated with the determined location, from the offboard system and to direct the communication interface to transmit a second portion of the recorded engine data to the offboard system. A second data content of the second portion of the recorded engine data is based on the updated data management strategy.

In any of the aspects or embodiments described above and herein, the processing circuitry is configured to disable transmission of the recorded engine data to the offboard system by the communication interface based on the data management strategy.

In any of the aspects or embodiments described above and herein, the engine control system includes a plurality of sensors configured to capture state data associated with the gas turbine engine and the engine data includes the state data.

In another aspect of the present invention, a method for controlling communications between a gas turbine engine for an aircraft and an offboard system is provided according to claim <NUM>.

In any of the aspects or embodiments described above and herein, receiving the location of the gas turbine engine includes determining at least one of a GPS location, a cellular location, or a city pair location.

In any of the aspects or embodiments described above and herein, selectively recording the generated engine data includes selectively recording a portion of the generated engine data based on the data management strategy.

In any of the aspects or embodiments described above and herein, the data management strategy includes an encryption strategy. The method further includes encrypting the first portion of the recorded engine data with a first encryption rule of the encryption strategy.

In any of the aspects or embodiments described above and herein, selectively recording the generated engine data includes selectively recording the generated engine data as a first data stream, including the first portion of the recorded engine data, and a second data stream different than the first data stream and a data stream content of the first data stream and the second data stream is based on the data management strategy.

In any of the aspects or embodiments described above and herein, encrypting the recorded engine data further includes encrypting recorded engine data of the first data stream with the first encryption rule of the encryption strategy and encrypting recorded engine data of the second data stream with a second encryption rule of the encryption strategy which is different than the first encryption rule.

In any of the aspects or embodiments described above and herein, the offboard system includes a plurality of ground stations and transmitting the first portion of the recorded engine data to the offboard system includes transmitting the first portion of the recorded engine data to a particular ground station of the plurality of ground stations based on the data management strategy.

In any of the aspects or embodiments described above and herein, the method further includes receiving an updated data management strategy, associated with the determined location, from the offboard system.

In any of the aspects or embodiments described above and herein, the method further includes disabling transmission of the recorded engine data to the offboard system based on the data management strategy.

In another aspect of the present invention, a gas turbine engine for an aircraft is provide according to claim <NUM>.

The present disclosure, and all its aspects, embodiments and advantages associated therewith will become more readily apparent in view of the detailed description provided below, including the accompanying drawings.

It is noted that various connections are set forth between elements in the following description and in the drawings. It is noted that these connections are general and, unless specified otherwise, may be direct or indirect and that this specification is not intended to be limiting in this respect. A coupling between two or more entities may refer to a direct connection or an indirect connection. An indirect connection may incorporate one or more intervening entities. It is further noted that various method or process steps for embodiments of the present disclosure are described in the following description and drawings. The description may present the method and/or process steps as a particular sequence. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. As one of ordinary skill in the art would appreciate, other sequences of steps may be possible. Therefore, the particular order of the steps set forth in the description should not be construed as a limitation.

Referring now to the drawings, <FIG> illustrates a system <NUM> supporting wireless communication between a communication adapter <NUM> of a gas turbine engine <NUM> and a plurality of offboard systems <NUM>. The gas turbine engine <NUM> can be coupled to an aircraft <NUM>, where the aircraft <NUM> can include multiple instances of the gas turbine engine <NUM>. The gas turbine engine <NUM> can include a fan section <NUM>, a compressor section <NUM>, a combustor section <NUM>, and a turbine section <NUM>. The fan section <NUM> drives air along a bypass flow path, while the compressor section <NUM> drives air along a core flow path for compression and communication into the combustor section <NUM> then expansion through the turbine section <NUM>. A fan case <NUM> of the fan section <NUM> can be covered by a cowling <NUM> and may provide an installation surface that is cooler than other sections <NUM>-<NUM> of the gas turbine engine <NUM>.

An engine control system <NUM> can be mounted on the fan case <NUM> and covered by the cowling <NUM>. The engine control system <NUM> is configured to monitor and control operation of the gas turbine engine <NUM> in real-time. In order to transfer configuration items, such as programs and data to and from the engine control system <NUM>, contemporary systems typically require that the cowling <NUM> is opened and multiple cables of bundled wires are coupled to the engine control system <NUM>. Such a process can ensure deliberate actions are taken in extracting data and performing updates to the engine control system <NUM>; however, the process can be slow and require large lengths of customized cables. In various embodiments, the communication adapter <NUM>, also referred to as a gas turbine engine communication gateway, is configured to establish communication with the engine control system <NUM> and wireless communication with one or more offboard systems <NUM> external to the aircraft <NUM>. Similar to the engine control system <NUM>, the communication adapter <NUM> can be mounted on the fan case <NUM> and covered by the cowling <NUM> of the gas turbine engine <NUM>. Wireless communication can alleviate the need for customized cables or physically opening the cowling <NUM> to establish communication with the offboard systems <NUM>. In various embodiments, the communication adapter <NUM> may be integral with the engine control system <NUM>, while in other embodiments the communication adapter <NUM> may be an independent electronic system external to the engine control system <NUM>.

The offboard systems <NUM> can include, for example, one or more ground stations <NUM>, a near-wing maintenance computer <NUM>, an access portal <NUM>, and/or other devices that may establish one-way or two-way wireless communication with the communication adapter <NUM>. For example, a global positioning system (GPS) can provide one-way wireless signaling to the communication adapter <NUM> to assist in confirming a geographic location of the gas turbine engine <NUM> while the communication adapter <NUM> is coupled to the gas turbine engine <NUM>. Wireless communication performed by the communication adapter <NUM> can be through a variety of technologies with different ranges supported. As one example, the communication adapter <NUM> can support Wi-Fi (e.g., radio wireless local area networking based on IEEE <NUM> or other applicable standards), GPS, cellular networks, satellite communication, and/or other wireless communication technologies known in the art. The wireless communication configuration of the communication adapter <NUM> may permit the communication adapter <NUM> to receive or otherwise determine a location (e.g., a geographical location) of the gas turbine engine <NUM> based on at least one of a GPS location, a cellular location, and/or a city pair location (e.g., a location based on known aircraft city pairs). In various embodiments, the communication adapter <NUM> may be configured to receive location data from one or more sources internal or external to the aircraft <NUM>. For example, the communication adapter <NUM> may receive a location data signal from one or more electronic systems of the aircraft <NUM> flight deck or by interception of an external broadcast (e.g., an Automated Dependent Surveillance Broadcast ("ADS-B")). In various embodiments, for example, the communication adapter <NUM> may determine a location based on multiple location data sources (e.g., GPS location, cellular location, and city pair location), thereby allowing validation of the gas turbine engine <NUM> location based on the multiple location data inputs. Accordingly, communication adapter <NUM> may accurately determine a location of the gas turbine engine <NUM> despite spurious location data or loss of a location signal from one or more location data sources. Additionally, the ability to handle multiple types of location data inputs allows the communication adapter <NUM> to be used on different aircraft having different location data sources and equipment. Wireless communication between the communication adapter <NUM> and the offboard systems <NUM> can be direct or indirect. For instance, wireless communication between the communication adapter <NUM> and the one or more ground station <NUM> may pass through one or more network interface components <NUM>, such as a repeater, while wireless communication between the communication adapter <NUM> and the near-wing maintenance computer <NUM> may be direct wireless communication without any relay components.

The ground station <NUM> can provide communication with a variety of support systems, such as an access portal <NUM> that provides authorized users to access data, initiate tests, configure software, and perform other actions with respect to the engine control system <NUM>, where the communication adapter <NUM> acts as a secure gateway to limit access and interactions with the engine control system <NUM>. As another example, the ground station <NUM> can communicate with a notification system <NUM>, which may trigger alerts, text messages, e-mails, and the like to authorized recipients regarding operational status of the gas turbine engine <NUM>. The near-wing maintenance computer <NUM> may provide an authorized user with limited authority a capability to query the communication adapter <NUM> for fault data, test parameters, and other such information. In various embodiments, the near-wing maintenance computer <NUM> can be authorized with limited authority to make updates to select configuration parameters or data collection parameters of the communication adapter <NUM>.

<FIG> is a block diagram illustrating further details of the system <NUM> of <FIG>, in accordance with one or more embodiments of the present disclosure. The engine control system <NUM> can control effectors <NUM> of the gas turbine engine <NUM> by generating one or more effector commands <NUM>. Examples of effectors <NUM> can include one or more motors, solenoids, valves, relays, pumps, heaters, and/or other such actuation control components. The engine control system <NUM> can generate engine data associated with the configuration, operation, status, and/or other aspects of the gas turbine engine <NUM>. In various embodiments, the engine data may additionally include data associated with the aircraft <NUM>. The engine control system <NUM> may include a plurality of sensors <NUM> which can capture state data associated with the gas turbine engine <NUM> and provide sensed values <NUM> as feedback to the engine control system <NUM> to provide closed-loop control of the gas turbine engine <NUM> according to one or more control laws. The engine data generated by the engine control system <NUM> may include the state data captured by the plurality of sensors <NUM>. Examples of the sensors <NUM> can include one or more temperature sensors, pressure sensors, strain gauges, speed sensors, accelerometers, lube sensors, and the like.

The engine control system <NUM> can be a full authority digital engine control system that includes processing circuitry <NUM> and a memory system <NUM> configured to store a plurality of configuration items, where at least one of the configuration items includes a sequence of the computer executable instructions for execution by the processing circuitry <NUM>. Other types of configuration items can include data, such as constants, configurable data, and/or fault data. Examples of computer executable instructions can include boot software, operating system software, and/or application software. The executable instructions may be stored or organized in any manner and at any level of abstraction, such as in connection with controlling and/or monitoring operation of the gas turbine engine <NUM>. The processing circuitry <NUM> can be any type or combination of central processing unit (CPU), including one or more of: a microprocessor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Also, in various embodiments, the memory system <NUM> may include volatile memory, such as random access memory (RAM), and nonvolatile memory, such as Flash memory, read only memory (ROM), and/or other electronic, optical, magnetic, or any other computer readable medium onto which is stored data and algorithms in a non-transitory form.

The engine control system <NUM> can also include one or more of an input/output interface <NUM>, a communication interface <NUM>, and/or other elements. The input/output interface <NUM> can include support circuitry for interfacing with the effectors <NUM> and sensors <NUM>, such as filters, amplifiers, digital-to-analog converters, analog-to-digital converters, and other such circuits to support digital and/or analog interfaces. Further, the input/output interface <NUM> can receive or output signals to/from other sources. The communication interface <NUM> can be communicatively coupled to the communication adapter <NUM>. The communication interface <NUM> may also communicate with an aircraft bus <NUM> of the aircraft <NUM> of <FIG>. The aircraft bus <NUM> may provide aircraft-level parameters and commands that are used by the engine control system <NUM> to control the gas turbine engine <NUM> in real-time.

Similar to the engine control system <NUM>, the communication adapter <NUM> can include processing circuitry <NUM>, a memory system <NUM>, an input/output interface <NUM>, and a communication interface <NUM>. The processing circuitry <NUM> can be any type or combination of central processing unit (CPU), including one or more of: a microprocessor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Also, in various embodiments, the memory system <NUM> may include volatile memory, such as random access memory (RAM), and nonvolatile memory, such as Flash memory, read only memory (ROM), and/or other electronic, optical, magnetic, or any other computer readable medium onto which is stored data and algorithms in a non-transitory form. The communication adapter <NUM> can also include a plurality of internal sensors <NUM>. The internal sensors <NUM> can be, for example, one or more accelerometers, gyroscopes, barometers, a compass, a GPS, and other such sensors. The input/output interface <NUM> can process data collected from the internal sensors <NUM> and condition the data in a format usable by the processing circuitry <NUM>. The communication interface <NUM> can interface with one or more antennas <NUM>, which may be integrated with the communication adapter <NUM> or located remotely from the communication adapter <NUM>, e.g., a shark-fin antenna mounted under or on the cowling <NUM> of <FIG>.

The communication adapter <NUM> can act as a secure communication gateway with respect to the offboard systems <NUM>. For example, the offboard systems <NUM> can request to load new/updated configuration items to the memory system <NUM> of the engine control system <NUM> through the communication adapter <NUM>. The communication interface <NUM> of the engine control system <NUM> can interface to the communication interface <NUM> of the communication adapter <NUM> through a wired, optical, or magnetic coupling. The communication interface <NUM> can communicate wirelessly through antennas <NUM> to the offboard systems <NUM>. For example, the communication interface <NUM> of the communication adapter <NUM> can transmit data, such as engine data, stored in memory system <NUM> and/or memory system <NUM> to the offboard systems <NUM>. The communication interface <NUM> may also have access to receive data directly from the aircraft bus <NUM>, the memory system <NUM>, and/or the memory system <NUM> in various embodiments. In various embodiments, the communication adapter <NUM> may be configured to send a request to the engine control system <NUM> to provide aircraft parameters received via the aircraft bus <NUM> and/or engine parameters computed by the engine control system <NUM> while in other embodiments the communication adapter <NUM> may be configured to passively monitor aircraft parameters, engine parameters, and other data output from aircraft systems such as the aircraft bus <NUM> and/or the engine control system <NUM>.

The communication adapter <NUM> can manage credentials and user authentication to limit access of the memory system <NUM> of the engine control system <NUM>. User authentication can be defined for particular users or classes of users, such as equipment-owner users, maintenance technicians, engineering users, and the like. For example, a maintenance technician may have authority to adjust trimmable constants or reprogram certain regions of the memory system <NUM>. An engineering user may have authority to reprogram an operating system, boot program code, or application software in the memory system <NUM>, in addition to having permissions of the maintenance technician and the equipment-owner user. If user authentication fails, for instance, by user credentials not being recognized with respect to user authentication data, then the communication adapter <NUM> can block access of the offboard systems <NUM> from reading from or writing to the memory system <NUM>.

Configuration items received for the engine control system <NUM> and/or the communication adapter <NUM> may be encrypted using various cryptographic methods to further enhance security. For example, the communication adapter <NUM> can apply a cryptographic algorithm using one or more parameters received and cryptographic information to decrypt an encrypted configuration item. A combination of transmitted and stored cryptographic information can be used together for decryption based on 'shared secrets' such that not all of the information is sent from the offboard systems <NUM> nor stored completely within the communication adapter <NUM>. After decryption, authenticity of the configuration item can be verified using, for example, a digital signature of the configuration item. The resulting file can be a decrypted and authenticated configuration item, which may be temporarily stored in memory system <NUM> or otherwise buffered during authentication and passed to the engine control system <NUM> upon authentication.

Separating the communication adapter <NUM> from the engine control system <NUM> can provide the communication adapter <NUM> and the engine control system <NUM> to have different expected service life durations. For example, to stay compatible with changes in wireless communication technologies used by the offboard systems <NUM>, the communication adapter <NUM> may be upgraded at a faster interval than the engine control system <NUM>. The communication adapter <NUM> can have a lower processing and storage capacity than the engine control system <NUM> to reduce power requirements, weight, and other costs associated with the communication adapter <NUM>. Since the communication adapter <NUM> does not actively control the gas turbine engine <NUM>, development cycles may be reduced as compared to implementing flight critical control algorithms and hardware of the engine control system <NUM>.

<FIG>show simplified block diagrams illustrating further exemplary details of the relationship between the engine control system <NUM>, the communication adapter <NUM>, and the offboard systems <NUM> of <FIG>, in accordance with one or more embodiments of the present disclosure. Referring to <FIG> and <FIG>, the engine control system <NUM> can provide engine data <NUM> to the communication adapter <NUM> in the form of a data stream <NUM>. The engine data <NUM> can be provided to the communication adapter from the memory system <NUM>, directly from the plurality of sensors <NUM>, and/or from one or more other electronic components of the engine control system <NUM>, the gas turbine engine <NUM>, and/or the aircraft <NUM>. The memory system <NUM> of the communication adapter <NUM> may be configured to selectively record the engine data <NUM> (e.g., as recorded engine data <NUM>) from the engine control system <NUM>. In various embodiments, the memory system <NUM> of the engine control system <NUM> may additionally or alternatively be configured to selectively record the engine data <NUM>.

As previously discussed, the communication adapter <NUM> may be configured with one or more electronic systems (e.g., GPS systems, wireless communication systems, etc.) which may be used by the processing circuitry <NUM> to determine a location of the gas turbine engine <NUM>. Because regulations governing engine data localization and security may vary by location, country, region, etc., aircraft operators may need to be capable of quickly and accurately tailoring data communication strategies for compliance with local regulations when using in-country infrastructure (e.g., offboard systems <NUM>) to transmit engine data. Accordingly, the processing circuitry <NUM> may be configured to determine an appropriate data management strategy which is unique to the determined location of the gas turbine engine <NUM>.

The geofencing capability of the communication adapter <NUM> may provide for the communication adapter <NUM> to trigger a unique communication response when the gas turbine engine <NUM> enters or leaves a particular area (e.g., geographical area, country, etc.). For example, a plurality of data management strategies (e.g., profiles) corresponding to a respective plurality of locations (geographical, national, etc.) may be stored in the memory system <NUM> of the communication adapter <NUM> for selective retrieval by the processing circuitry <NUM> based on the determined location of the gas turbine engine <NUM>. Data management strategies may be centrally managed (e.g., using a computer server, cloud-based computing platform, etc.) and may be periodically uploaded to the communication adapter <NUM> from, for example, the offboard systems <NUM> or any other suitable communication system. As used herein, the term "unique" with respect to a data management strategy means that the particular data management strategy is specific to the determined location. In other words, data sharing and encryption rules of the data management strategy for a particular location (e.g., country) are based on regulations and other data compliance considerations associated with that particular location. However, it should be understood that a data management strategy which is "unique" to one location may be similar or the same as a second data management strategy which is unique to a second different location.

Based on the unique data management strategy for the determined location, the processing circuitry <NUM> may be configured to direct the communication interface <NUM> to transmit a first portion <NUM> of the recorded engine data <NUM> to the offboard system <NUM>. The data content of the first portion <NUM> of the recorded engine data <NUM> may be selected based on the data management strategy for the determined location in order to comply with local data communication and security regulations. In various embodiments, a second portion <NUM> of the recorded engine data <NUM> may not be transmitted to the offboard system <NUM> and may continue to be stored by the memory system <NUM> or discarded. In various embodiments, all of the recorded engine data <NUM> may be transmitted to the offboard system <NUM>. In various embodiments, the processing circuitry <NUM> may be configured to direct the memory system <NUM> to selectively record a portion of the generated engine data <NUM> from the engine control system <NUM>. The portion of the generated engine data <NUM> to be selectively recorded may be based on the data management strategy for the determined location. In various embodiments, the processing circuitry <NUM> may be configured to disable transmission of the recorded engine data <NUM> to the offboard system <NUM> by the communication interface <NUM> based on the data management strategy.

Various data management strategies of the plurality of data management strategies may include one or more types of encryption (e.g., encryption rules) for different kinds of data such that what data content may be decrypted depends on the party receiving the data and which encryption key the party may possess. For example, a first encryption key may allow a first party to decrypt a portion of the recorded engine data <NUM> transmitted by the communication adapter <NUM> while a second encryption key may allow a second party to decrypt all of the recorded engine data <NUM> transmitted by the communication adapter <NUM>. In various embodiments, the data management strategy for the determined location may include an encryption strategy and the processing circuitry <NUM> may be configured to encrypt the recorded engine data <NUM> with an encryption rule <NUM> of the encryption strategy. For example, in various embodiments, the first portion <NUM> of the recorded engine data <NUM> may be encrypted with the encryption rule <NUM> prior to transmitting the first portion <NUM> of the recorded engine data <NUM> to the offboard system <NUM>.

In various embodiments, the processing circuitry <NUM> may be configured to direct the memory system <NUM> to selectively record the generated engine data <NUM> using a plurality of data streams. For example, memory system <NUM> may selectively record the generated engine data <NUM> as the data stream <NUM> and a second data stream <NUM> which is different than the data stream <NUM>. In order to comply with multiple data storage, data sharing, and/or data encryption regulations, the plurality of data streams (e.g., the data streams <NUM>, <NUM>) may include different data content (e.g., different datasets, parameters, etc.) and/or may be encrypted using different encryption rules, based on the data management strategy for the determined location. For example, the processing circuitry <NUM> may be configured to encrypt recorded engine data <NUM> of the data stream <NUM> with the encryption rule <NUM> and to encrypt the recorded engine data <NUM> of the second data stream <NUM> with a second encryption rule <NUM> which is different than the encryption rule <NUM>. The processing circuitry <NUM> may be configured to determine the data content of the data stream <NUM> and/or the second data stream <NUM> which may be transmitted to the offboard systems <NUM> based on the data management strategy for the determined location. For example, the data stream <NUM> may include the first portion <NUM> of the recorded engine data <NUM> which may be transmitted to the offboard system <NUM> based on data management strategy for the determined location.

The offboard system <NUM> may include a plurality of ground stations <NUM>. In various embodiments, the processing circuitry <NUM> may be configured to direct the communication interface <NUM> to transmit recorded engine data <NUM> (e.g., the first portion <NUM> of the recorded engine data <NUM>) to a particular ground station of the plurality of ground stations <NUM> based on the data management strategy for the determined location.

As previously discussed, data management strategies may be centrally managed and may be periodically uploaded to the communication adapter <NUM> from, for example, the offboard systems <NUM> or any other suitable communication system. In various embodiments, the processing circuitry <NUM> may be configured to direct the communication interface <NUM> to receive one or more updated data management strategies corresponding to a respective one or more locations. For example, the processing circuitry <NUM> may be configured to direct the communication interface <NUM> to receive an updated data management strategy, associated with the determined location, from the offboard system <NUM> and to direct the communication interface <NUM> to transmit the recorded engine data <NUM> in accordance with the updated data management strategy which may change one or more data recording, data transmittal, or data encryption rules associated with the determined location.

Referring now to <FIG> with continued reference to <FIG>, <FIG>, and <FIG>, <FIG> is a flow chart illustrating a method <NUM> for controlling communications between a gas turbine engine <NUM> for an aircraft <NUM> and an offboard system <NUM>. At Block <NUM>, the engine control system <NUM> may generate engine data <NUM> associated with the configuration, operation, status, and/or other aspects of the gas turbine engine <NUM> or aircraft <NUM>. At Block <NUM>, the engine control system <NUM> and/or the communication adapter <NUM> may selectively record all or a portion of the generated engine data <NUM>. At Block <NUM>, the communication adapter <NUM> may determine a location of the gas turbine engine <NUM> using one or more methods including, but not limited to, determining a location using GPS, determining a location using wireless communication signals, and/or determining a location using known city pair combinations. At Block <NUM>, the communication adapter <NUM> may determine a data management strategy based on the determined location which is unique to the determined location of the gas turbine engine <NUM>. At Block <NUM>, the communication adapter <NUM> may, optionally, encrypt the recorded engine data <NUM> using or more encryption rules <NUM>, <NUM> of an encryption strategy for the data management strategy. In Block <NUM>, the communication adapter <NUM> may transmit all or a portion of the recorded engine data <NUM> to an offboard system <NUM> based on the data management strategy.

Claim 1:
A communication system of a gas turbine engine (<NUM>) for an aircraft (<NUM>), the communication system comprising:
an engine control system (<NUM>) configured to generate engine data (<NUM>); and
a communication device (<NUM>) comprising:
a memory system (<NUM>) configured to store the generated engine data (<NUM>) from the engine control system (<NUM>);
a communication interface (<NUM>) configured to wirelessly communicate with an offboard system (<NUM>) external to the aircraft (<NUM>) and to communicate with the engine control system (<NUM>) and the memory system (<NUM>), the communication interface (<NUM>) further configured to receive the generated engine data (<NUM>) from the engine control system (<NUM>); and characterised by
processing circuitry (<NUM>) configured to:
selectively record the generated engine data (<NUM>) received by the communication interface (<NUM>) to the memory system (<NUM>);
determine a location of the gas turbine engine (<NUM>);
determine a unique data management strategy based on the determined location, the unique data management strategy including data sharing and encryption rules for the determined location; and
transmit, using the communication interface (<NUM>), a first portion (<NUM>) of the recorded engine data (<NUM>) to the offboard system (<NUM>), a data content of the first portion (<NUM>) of the recorded engine data (<NUM>) based on the unique data management strategy.