Patent Application
20230222233
The application relates generally to aircrafts and, more particularly, to data access from an aircraft.
When troubleshooting malfunctions of aircraft engines or engine components, maintenance personnel generally connect a portable computing device to a data acquisition device installed on the aircraft or engine in order to retrieve data, including engine fault codes, and take appropriate corrective actions. Wired connections, such as through the use of specialized cables and other electrical connectors, are often required, which increases complexity and troubleshooting time. In addition, secured connections for data access from the aircraft may be lacking in remote locations. Therefore, there is room for improvement.
In one aspect, there is provided a data access method for an aircraft, the method comprising obtaining, at a computing device, password data for use in providing access to aviation data collected by at least one data acquisition device from one or more locations in the aircraft, causing, at the computing device, the password data to be rendered on at least one display provided in at least one secured location of the aircraft, receiving, at the computing device, subsequent to the password data being rendered on the at least one display, input data from at least one user device requesting access to the aviation data, comparing, at the computing device, the input data to the password data, and, when the input data matches the password data, establishing, at the computing device, a connection between the at least one user device and the at least one data acquisition device for providing the at least one user device access to the aviation data.
In some embodiments, the obtaining the password data comprises generating a random string of characters to form the password data.
In some embodiments, the obtaining the password data comprises retrieving the password data from a memory communicatively coupled to the computing device.
In some embodiments, the obtaining the password data comprises obtaining new password data upon receipt of a user-initiated command or a system-initiated command.
In some embodiments, the system-initiated command is generated by the at least one data acquisition device in response to the at least one data acquisition device being powered on.
In some embodiments, the password data is caused to be rendered on the at least one display provided in a cockpit of the aircraft.
In some embodiments, a wireless connection is established between the at least one data acquisition device and the at least one user device for routing the aviation data from the at least one data acquisition device to the at least one user device via the wireless connection.
In some embodiments, the at least one user device is provided access to the aviation data for performing a maintenance operation while the aircraft is on ground.
In some embodiments, the at least one user device is provided access to the aviation data for performing a data recording operation while the aircraft is in flight.
In some embodiments, the aviation data is collected by the at least one data acquisition device from at least one of one or more sensors, an engine computer, and an aircraft computer during operation of the aircraft in-flight.
In another aspect, there is provided a data access system for an aircraft, the system comprising a processing unit, and a non-transitory computer-readable medium having stored thereon instructions executable by the processing unit for obtaining password data for use in providing access to aviation data collected by at least one data acquisition device from one or more locations in the aircraft, causing the password data to be rendered on at least one display provided in at least one secured location of the aircraft, receiving, subsequent to the password data being rendered on the at least one display, input data from at least one user device requesting access to the aviation data, comparing the input data to the password data, and, when the input data matches the password data, establishing, at the computing device, a connection between the at least one user device and the at least one data acquisition device for providing the at least one user device access to the aviation data.
In some embodiments, the instructions are executable by the processing unit for obtaining the password data comprising generating a random string of characters to form the password data.
In some embodiments, the instructions are executable by the processing unit for obtaining the password data comprising retrieving the password data from a memory.
In some embodiments, the instructions are executable by the processing unit for obtaining the password data comprising obtaining new password data upon receipt of a user-initiated command or a system-initiated command.
In some embodiments, the system-initiated command is generated by the at least one data acquisition device in response to the at least one data acquisition device being powered on.
In some embodiments, the instructions are executable by the processing unit for causing the password data to be rendered on the at least one display provided in a cockpit of the aircraft.
In some embodiments, the instructions are executable by the processing unit for establishing the connection comprising establishing a wireless connection between the at least one data acquisition device and the at least one user device for routing the aviation data from the at least one data acquisition device to the at least one user device via the wireless connection.
In some embodiments, the instructions are executable by the processing unit for providing the at least one user device access to the aviation data for performing a maintenance operation while the aircraft is on ground.
In some embodiments, the instructions are executable by the processing unit for providing the at least one user device access to the aviation data for performing a data recording operation while the aircraft is in flight.
In some embodiments, the aviation data is collected by the at least one data acquisition device from at least one of one or more sensors, an engine computer, and an aircraft computer during operation of the aircraft in-flight.
Reference is now made to the accompanying figures in which:
It will be noticed that throughout the appended drawings, like features are identified by like reference numerals.
There is described herein systems and methods for providing access to data from an aircraft. The aircraft is equipped with at least one engine.
Although illustrated as a turbofan engine, the gas turbine engine 10 may alternatively be another type of engine, for example a turboshaft engine, also generally comprising in serial flow communication a compressor section, a combustor, and a turbine section, and a possible boost rotor through which ambient air is propelled. A turboprop engine may also apply. Other types of aircraft engines may also apply including, but not limited to, auxiliary power units (APUs), rotary engines, electric engines, and hybrid electric propulsion systems having a propeller driven in a hybrid architecture (series, parallel, or series/parallel) or turboelectric architecture (turboelectric or partial turboelectric).
The sensor(s) 102 may be configured to collect one or more measurements (also referred to herein as “measurement data” or “sensor data”) associated with operation of the engine 10 and/or the aircraft 100. The sensor(s) 102 are configured to acquire measurement(s) of parameter(s) of the engine 10 (referred to herein as “engine parameter(s)”) and/or parameter(s) aircraft 100 (referred to herein as “aircraft parameter(s)”) including, but not limited to, pressure (e.g., engine inlet total pressure, interstage pressure, engine pressure ratio or EPR), temperature (e.g., engine inlet total temperature, turbine inlet temperature, interstage temperature, engine exhaust gas temperature or EGT), altitude, speed (e.g., rotor speed of the engine's low-pressure rotor and high-pressure rotor, measured in Revolutions Per Minute (RPM)), acceleration, power, and torque. The sensor(s) 102 may also be configured to acquire measurement(s) of one or more parameters describing flight and ambient conditions (e.g., ambient pressure and temperature). It should however be understood that any other suitable measurements including, but not limited to, engine bleed valve position, bleed flow, and control actuator feedback, may be collected by the sensor(s) 102. Other sensor inputs may include, but are not limited to, Radio Frequency Identification (RFID) or component configuration status data. Indeed, the parameters measured by the sensor(s) 102 may vary according to the type of the engine 10 and/or aircraft 100, and according to the application.
The sensor(s) 102 are illustratively configured to collect the one or more measurements during operation of the engine 10 and/or the aircraft 100 in-flight. The one or more measurement(s) may be collected continuously and in real-time, in order to provide a complete indication of the performance of the engine 10 and/or aircraft 100 during flight. The one or more measurement(s) may, alternatively or in addition, be collected at one or more points in time during the flight mission. In one embodiment, the measurement(s) may be acquired by the sensor(s) 102 during a stable cruise flight condition. As understood by those skilled in the art, a stable cruise condition corresponds to an operating condition of the aircraft 100 during which certain flight criteria, which may correspond to engine parameters and/or aircraft parameters, are attained. Stable cruise condition may be operator-specific. It should however be understood that the measurement(s) may be acquired by the sensor(s) 102 during any other suitable flight condition. For example, measurements(s) may be acquired during a constant climb phase of flight, which corresponds to a flight phase during which the aircraft 100 climbs to a given altitude at a constant climb rate. The measurement(s) may also be collected during operation of the engine 10 and/or aircraft 100 on the ground, during maintenance inspections or during ground tests for instance.
The one or more measurements are then transmitted from the sensor(s) 102 to one or more aircraft- or engine-mounted electronic devices (referred to herein as “data acquisition device(s)”) 104, continuously or at regular intervals, via the existing aircraft harness and/or additional cables, adapters, connectors, and/or harnesses. The Aeronautical Radio Inc. (ARINC) 429 data transfer standard for aircraft avionics may be used. Other data standards may also be used, including, but not limited to, ARINC 615, ARINC 629, ARINC 717, ARINC 664, Controller Area Network (CAN), UART RS-422, Ethernet and MIL-STD-1553. Alternatively, transmission of the data collected by the sensor(s) 102 is performed wirelessly. Therefore, the sensor(s) 102 may be configured for providing the measurement data to the data acquisition device(s) 104 via any suitable wired or wireless communication path, including RS-232, USB, USB 2.0, USB 3.0, USB-C, SATA, e-SATA, Thunderbolt™, Ethernet, Wi-Fi, Zigbee™, Bluetooth™, and the like.
In one embodiment, the data acquisition device(s) 104 may also receive data from an aircraft computer 106 and/or an engine computer 108. This data will be collectively referred to as aircraft data, and denotes engine and/or aircraft performance parameters. The aircraft computer 108 may be an aircraft management controller (AMC), a flight management system (FMS), an aircraft digital computer system, or any other device used for computing inside an aircraft 100. The engine computer 106 may be any type of computing unit of an engine 10, such as an engine control unit (ECU), an engine electronic controller (EEC), an engine electronic control system, and a Full Authority Digital Engine Controller (FADEC). Data transmitted from the aircraft computer 108 and/or engine computer 106 to the data acquisition device(s) 104 (or vice versa) may be provided over a dedicated communication bus (e.g., a CAN bus) or any other existing communication system of the aircraft 100. Example data provided by the aircraft computer 108 comprises airspeed, altitude, stability, and position of the aircraft 100 at any point in time during a flight. Example data provided by the engine computer 106 comprises engine torque, engine speed, engine rating, engine torque stability, propeller speed stability, and engine compressor speed stability at any point in time during engine operation. The engine computer 106 may further be configured to detect fault(s) of the engine 10 (i.e. a physical fault that affects the thermodynamic performance of the engine 10 or a system fault) and accordingly generate engine fault data, which may also be sent to the data acquisition device(s) 104. It should however be understood that engine fault detection may alternatively be performed in the data acquisition device(s) 104, based on the data received from the sensor(s) 102, engine computer 106, and/or aircraft computer 108. In some embodiments, the sensor(s) 102 may be connected to or read by the engine computer 106 and/or the aircraft computer 108 such that the measurement(s) collected by the sensor(s) 102 are received by the data acquisition device(s) 104 from the engine computer 106 and/or the aircraft computer 108 (instead of directly from the sensor(s) 102).
The data received at the data acquisition device(s) 104 from the sensor(s) 102, engine computer 106, and/or aircraft computer 108 data is collectively referred to herein as “aviation data”. In other words, the term “aviation data” refers to the sensor data received from the sensor(s) 102 and/or the aircraft data received from the aircraft computer 108 and/or the engine computer 106. The aviation data may be collected from one or more locations of the aircraft 100 and received at the data acquisition device(s) 104 in real-time or at regular intervals during a flight mission of the aircraft 100 or ground operation of the engine 10 and/or aircraft 100, based on specific operational conditions of the engine 10 and/or the aircraft 100. In other embodiments, the data acquisition device(s) 104 receive data from the sensor(s) 102, engine computer 106, and/or aircraft computer 108 at the end of the aircraft's flight mission. As used herein, the term “mission” refers to a flight to perform a specific task. The mission may be defined by various parameters, such as duration, destination, cargo, and any flying parameters to be used during the mission, such as speed or maximum altitude. For example, operator X may have aircraft A and B fly at a cruise speed of Mach 0.7 while aircraft C flies at a cruise speed of Mach 0.82. The value associated for the flight criteria “speed” may therefore differ between aircraft A and B and aircraft C. In some embodiments, operator X may define a unique set of flight criteria and associated values for each flight of an aircraft as a function of the specific flight parameters of a given flight, such as speeds, cruising altitudes, etc.
A data acquisition device 104 may take various forms, such as a Data Acquisition and Transmission Unit (DCTU), a Flight Data Acquisition Storage and Transmission (FAST™) system, as manufactured by Pratt & Whitney Canada, or any other computer-controlled unit that receives data from various sensors and/or aircraft and engine systems. It should be understood that, while
A data acquisition device 104 may comprise one or more antenna, one or more processors, and a memory (none shown). The processor(s) may be coupled to one or more data buses of the aircraft 100 for receiving the aviation data from the sensor(s) 102, engine computer 106, and/or aircraft computer 108. As previously noted, the aviation data may be transmitted to and received at the data acquisition device 104 using any suitable wired or wireless communication path. In some embodiments, the data acquisition device 104 is configured to process the received aviation data. The data acquisition device 104 may perform a conversion of the aviation data to a digitized form if received in analog form. It should however be understood that digitization of the aviation data may alternatively be performed by a dedicated device provided on the aircraft 100 separately from the data acquisition device 104. In some embodiments, the data acquisition device 104 may be configured to store the received aviation data in memory.
The data acquisition device 104 may be configured to transmit the aviation data to a server or other computing device (not shown) located remotely from the aircraft 100 (e.g., on the ground), using any suitable communication means (e.g. wireless communication). The wireless communication may be established upon engine start up with the aircraft 100 parked, after completion of a flight mission of the aircraft 100, or after engine shutdown. For example, the data acquisition device 104 may transmit the aviation data off-aircraft to a remote data and application server. This may occur without any human intervention, when the wireless communication is available at the destination point of the aircraft 100. As will be described further below, the aviation data may also be transmitted off-aircraft from the data acquisition device 104 to one or more client device(s) (also referred to herein as user device(s)) 110, upon the client device(s) 110 requesting access to the aviation data. The data acquisition device 104 may be configured to establish communication with the client device(s) 110, over a communication link 112. In one embodiment, the data acquisition device 104 is configured to communicate with more than one client device 110, although not necessarily with more than one type of client device 110 at one time. In one embodiment, the communication link 112 is wireless. As used herein, the term “wireless” refers to the transfer of information (or data) between two points that are not connected by an electrical conductor. Any suitable wireless technology may be used to establish a wireless connection as in 112 including, but not limited to, radio waves (e.g., VHF radio, HF radio), Bluetooth™, Ultra-wideband (UWB), mobile broadband, wireless spread spectrum such as Wi-Fi (Standardized as IEEE 802.11 a, b, g, n, ac, ax), cellular data service, and satellite communication (SATCOM), and the like. In other embodiments, the communication link 112 may be wired (e.g., USB, Ethernet, or the like). For example, upon landing of the aircraft 100, the user may connect their client device 110 to the data acquisition device 104 using any suitable wired connection (e.g. USB, Ethernet, or the like) for the purpose of manually retrieving the aviation data from the memory of the data acquisition device 104 and downloading the retrieved aviation data onto their client device 110.
As will be described further below, the systems and methods described herein provide the client device(s) 110 access to the aviation data using passwords. For this purpose, prior to authorizing access to the aviation data, passwords (referred to herein as “password data”) is used to authenticate the client device(s) 110 requiring access to the aviation data. The authentication procedure may be performed at the data acquisition device 104, the engine computer 106, the aircraft computer 108, or any other suitable computing device (not shown) communicatively coupled to the data acquisition device 104. As will also be described further below, the password data is rendered on one or more displays 114 provided in a secure location of the aircraft 100, the display(s) 114 being accessible to the user(s) associated with the client device(s) 110. The password data may be simultaneously rendered on multiple displays 114. In one embodiment, the display(s) 114 are provided in the cockpit of the aircraft 100 and are controlled by the aircraft computer 108. For example, the display(s) 114 may be the flight display or any other display provided in the cockpit. It should however be understood that the display(s) 114 may be provided in any suitable location of the aircraft 100 other than the cockpit. For example, the display(s) 114 may be provided outside of the cockpit, in a locked cabin or a secured compartment located in the aircraft 100. Although not illustrated, the display(s) 114 may also be mounted in the data acquisition device 104 or adjacent thereto. The display(s) 114 may also be associated with the engine computer 106. Upon the user accessing the display(s) 114 (e.g., by entering in the cockpit) and viewing the password data displayed thereon, the user may then enter the password data using any suitable input device (e.g., a keyboard, touchscreen, or the like) associated with their client device 110. The input data from the client device 110 is then received at the computing device provided on-board the aircraft 100 (i.e. at the data acquisition device 104, the engine computer 106, the aircraft computer 108, or any other suitable computing device) and compared to the password data. The client device 110 is provided access to the aviation data when the input data matches the password data.
The client device(s) 110 comprise any portable or handheld communication device, such as a smartphone, a desktop computer, a portable (or laptop) computer, a tablet, a hand-held electronic device, an electronic flight bag, or the like, adapted to communicate over the communication link 112. In one embodiment, the client device(s) 110 are external to the aircraft 100 and provided for maintenance (e.g., troubleshooting) purposes. It should be understood that the client device(s) 110 may, in some embodiments, be located within the aircraft 100. Maintenance personnel may use their client device 110 to access the data acquisition device 104 and retrieve the aviation data therefrom for the purpose of performing maintenance on the engine 10 to troubleshoot malfunctions. Fault codes and associated indication messages contained in the aviation data collected by the data acquisition device 104 may be accessed and used to direct maintenance efforts, which may be performed while the aircraft 100 on the ground. After carrying out appropriate corrective actions or responses to each fault code, the maintenance personnel may update maintenance logs (or records) associated with the engine 10 and/or the aircraft 100. The maintenance record(s) may be indicative of date(s) and time(s) at which engine and/or aircraft maintenance has been performed. In another embodiment, the client device(s) 110 may be used to access the data acquisition device 104 and retrieve the aviation data therefrom for the purpose of performing a data recording operation (e.g. reviewing of in-flight data from live engine testing) while the aircraft 100 is in flight. Other embodiments may apply.
With reference to
The computing device 200 comprises a processing unit 202 and a memory 204 which has stored therein computer-executable instructions 206. The processing unit 202 may comprise any suitable devices configured to implement the method 400 such that instructions 206, when executed by the computing device 200 or other programmable apparatus, may cause the functions/acts/steps performed as part of the method 400 as described herein to be executed. The processing unit 202 may comprise, for example, any type of general-purpose microprocessor or microcontroller, a digital signal processing (DSP) processor, a central processing unit (CPU), an integrated circuit, a field programmable gate array (FPGA), a reconfigurable processor, other suitably programmed or programmable logic circuits, or any combination thereof.
The memory 204 may comprise any suitable known or other machine-readable storage medium. The memory 204 may comprise non-transitory computer readable storage medium, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. The memory 204 may include a suitable combination of any type of computer memory that is located either internally or externally to device, for example random-access memory (RAM), read-only memory (ROM), compact disc read-only memory (CDROM), electro-optical memory, magneto-optical memory, erasable programmable read-only memory (EPROM), and electrically-erasable programmable read-only memory (EEPROM), Ferroelectric RAM (FRAM) or the like. Memory 204 may comprise any storage means (e.g., devices) suitable for retrievably storing machine-readable instructions 206 executable by processing unit 202.
The instructions 206 may be implemented in a high level procedural or object oriented programming or scripting language, or a combination thereof, to communicate with or assist in the operation of a computer system, for example the data acquisition device(s) 104. Alternatively, the instructions 206 may be implemented in assembly or machine language. The language may be a compiled or interpreted language. The instructions 206 may be readable by a general or special-purpose programmable computer.
The methods and systems described herein may be implemented in a high level procedural or object oriented programming or scripting language, or a combination thereof, to communicate with or assist in the operation of a computer system, for example the computing device 200. Alternatively, the methods and systems described herein may be implemented in assembly or machine language. The language may be a compiled or interpreted language. Program code for implementing the methods and systems described herein may be stored on a storage media or a device, for example a ROM, a magnetic disk, an optical disc, a flash drive, or any other suitable storage media or device. The program code may be readable by a general or special-purpose programmable computer for configuring and operating the computer when the storage media or device is read by the computer to perform the procedures described herein. Embodiments of the methods and systems described herein may also be considered to be implemented by way of a non-transitory computer-readable storage medium having a computer program stored thereon. The computer program may comprise computer-readable instructions which cause a computer, or more specifically the processing unit 202 of the computing device 200, to operate in a specific and predefined manner to perform the functions described herein, for example those described in the method 400.
Computer-executable instructions may be in many forms, including program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments.
Referring now to
The input unit 302 illustratively comprises a data interface (not shown) configured to receive, directly or indirectly, data from the sensor(s) 102, the data acquisition device(s) 104, the engine computer 106, the aircraft computer 108 (e.g., via one or more data buses, connectors, and the like, as described herein above), and/or the client device(s) 110 (e.g., via the communication link 112). In some embodiments, the input unit 302 may be configured to digitize the data if received in analog form.
In response to a data acquisition device 104 being powered on, a command (referred to herein as a “system-initiated command”) may be output (e.g., by the data acquisition device 104, the engine computer 106 or the aircraft computer 108). The system-initiated command comprises instructions to cause new password data to be obtained for the purpose of providing the at least one client device 110 with access to aviation data collected by the data acquisition device 104. It should however be understood that the password data may alternatively be obtained in response to a command (referred to herein as a “user-initiated command”) generated as a result of an action by a user, regardless of whether the data acquisition device 104 is being powered on. For example, the user-initiated command may be output as a result of a user (e.g., a pilot) actuating a button, switch, knob, or other input or control means provided in the cockpit (or other suitable location) of the aircraft 100. The command (i.e. the user-initiated command or the system-initiated command) is received at the input unit 302, which in turn sends the command to the password data unit 304 for password data to be obtained.
In one embodiment, the password data unit 304 may be part of the data acquisition device 104 such that the password data is obtained (e.g., dynamically generated) by the latter. The password data unit 304 may alternatively be part of the engine computer 106 and/or the aircraft computer 108 such that the password data is obtained (e.g., dynamically generated) by the latter. For example, the EEC may be configured to generate the password data. One or more computing devices may also be configured to obtain (e.g. dynamically generate) the password data. For example, first password data (e.g. a first random string of characters) may be generated by the engine computer 106 and second password data (e.g. a second random string of characters) may be generated by the aircraft computer 108. The first and second password data may then be combined (e.g., concatenated) in order to form further password data that is then used to provide access to the aviation data.
In one embodiment, the password data unit 304 obtains the password data by generating a random string of characters using any suitable technique. For example, the password data unit 304 may be configured to implement a random password generator (e.g., a random number generator) that dynamically generates the password data (e.g., comprising a random sequence of numbers) upon receipt of the command. In another embodiment, the password data unit 304 may be configured to access a memory (or other suitable storage) communicatively coupled thereto and to retrieve therefrom the password data. Password data (e.g., random strings of characters) may indeed be generated in advance (i.e. ahead of the data acquisition device 104 being powered and of the command being received) and stored in the memory for subsequent retrieval by the password data unit 304. In one embodiment, the password data unit 304 may be configured to rotate through pre-generated (e.g., random) passwords stored in memory upon receipt of the command to obtain the password data. For example, the password data unit 304 may retrieve from memory a first pre-generated password upon receipt of a first command. The next time a command is received, the password data unit 304 may retrieve from the memory a second pre-generated password (different from the first pre-generated password). The second pre-generated password may be randomly selected and retrieved from the memory or selected according to any suitable logic that ensures that different passwords at retrieved at any given time and that the passwords are rotated. It should be understood that the password data unit 304 may also be configured to obtain fixed (i.e. non random) password data for use in providing access to the aviation data.
In some embodiments, new password data is obtained by the password data unit 304 each time a command is received from the input unit 302, e.g. during power on initialization of the data acquisition device 104. In one embodiment, changing the password every time the data acquisition device 104 is powered on may ensure that the password cannot be written down or remembered by a user. This may enhance security in the event that users who were previously authorized to connect to the data acquisition device 104 are no longer authorized (e.g., after having changed jobs). Once a client device 110 is authorized to connect to the data acquisition device 104 to access the aviation data, the password data may remain the same for a predetermined time duration (e.g., 12 hours, 24 hours, or any other suitable duration). In this manner, users may be prevented from having to repeatedly enter new passwords while performing a given action (e.g., a maintenance task on the aircraft 100). In addition, the risk of forgetting or losing the password may be decreased. Moreover, by rendering the password data in a secured location of the aircraft 100 (e.g., in the cockpit), it can be ensure that only user(s) having had physical access to the secured location are authorized to connect to the data acquisition device(s) 104. Therefore, a client device 110 within communication range of the data acquisition device(s) 104 may not be authorized to establish a secure connection with the data acquisition device(s) 104 and access the aviation data unless the user can view the password data by physically accessing the secured location of the aircraft 100 (e.g., by entering the cockpit).
In one embodiment, the password data is numeric and each password comprises a string of numerical characters. In another embodiment, the password data is numeric and each password comprises a string of alphabetical characters. In other embodiments, alphanumeric password data may be used where each password comprises a string of alphanumeric characters. In yet other embodiments, special characters may be used as part of the password. It should be understood that the password data may be any suitable combination of numerical, alphabetical, alphanumerical, and/or special characters. It should also be understood that symbols may also be used. The length of each password may vary depending on the engine and/or aircraft configuration and on the application. For example, the password data may comprise a string of four (4) to sixteen (16) characters. Other embodiments may apply.
The password data obtained (i.e. generated or retrieved from memory) by the password data unit 304 is then sent to the output unit 310 for rendering on the display(s) 114 provided on-board the aircraft 100. The output unit 310 may be configured to format the password data for rendering on the display(s) 114. In some embodiments, the password data may be rendered on the display(s) 114 for a pre-determined duration (e.g., a few minutes). In some embodiments, the password data unit 304 may be provided as part of the data acquisition device 104 such that the latter generates the password data and communicates it (using the output unit 310) to the engine computer 106. The engine computer 106 then communicates the password data to the aircraft computer 108 which causes the password data to be rendered on the display(s) 114. In other embodiments, the password data unit 304 may be provided as part of the data acquisition device 104 such that the latter generates the password data and communicates it (using the output unit 310) to the display(s) 114 via an intermediary device other than the engine computer 106 or the aircraft computer 108. For example, a crash recording device communicatively coupled to the data acquisition device 104 may be used as the intermediary device. A laptop interface may alternatively be used to transmit the password data from the data acquisition device 104 to the display(s) 114. In yet other embodiments, the data acquisition device 104 may be configured to directly transmit the password data to the display(s) 114. Other embodiments may apply.
When a user wishes to access the aviation data collected by the data acquisition device 104, the user may then physically access the secured location in which the display(s) 114 are provided in order to view the password data. The user may then enter, using a suitable input device (e.g., keyboard, touchscreen, or the like) associated with their client device 110, input data indicative of a request to access the aviation data. For this purpose, a suitable graphical user interface may be presented on the client device 110 to enable the user to gain access to the aviation data and the input data may be entered via the graphical user interface. Alternatively, the client device 110 may access a secured web portal or a webpage (e.g. an engine maintenance webpage) and enter the input data therein in order to be provided access to the aviation data. The input data is then received at the input unit 302 and sent, along with the password data (generated or retrieved from memory by the password data unit 304), to the comparison unit 306.
In order for the user to be authenticated and authorized access to the aviation data, the input data entered by the user should comprise the password data rendered on the display(s) 114. The comparison unit 306 therefore compares the input data to the password data to assess whether the input data matches (i.e. is the same as) the password data. The comparison unit 306 may then provide the outcome of the comparison to the access unit 308, which may be configured to authorize or deny access to the aviation data based on the outcome of the comparison. The access unit 308 may further be configured to generate an indication (or notification) of whether access is granted or denied and send this indication to the output unit 310 for output on the client device 110. The output unit 310 causes the indication to be output to the client device 110 using any suitable means. For example, the indication may be output in a visual manner, e.g. rendered on a screen of the client device 110 or transmitted, using any suitable communication means, as a text message, email, or the like, to the client device 110. An audible indication may also be output using any suitable output means (e.g., a speaker) associated with the client device 110.
When the input data fails to match (i.e. differs from) the password data and data access is to be denied, the access unit 308 may be configured to generate a message or an alert indicating that access to the aviation data has been denied due to a wrong password having been entered. When the input data matches the password data and data access is to be granted, the access unit 308 is configured to generate an indication to this effect. The indication is then sent from the access unit 308 to the output unit 310, which may cause the indication to the be output to the client device(s) 110 as described herein above. The output unit 310 may also generate a control signal to allow or prevent the client device 110 to be provided access to the aviation data. For example, when access is granted, the control signal may comprise instructions for allowing a secure connection to be established between the data acquisition device 104 and the client device 110 for routing the aviation data from the data acquisition device 104 to the client device 110 over the connection. The secure connection may be established using any suitable means. For example, in some embodiments, a virtual private network (VPN) may be used. In one embodiment, the connection is a wireless connection, as described herein above. It should however be understood that, in some embodiments, the connection may alternatively be a wired connection. When access is denied, the control signal may comprise instructions for preventing establishment of the connection between the data acquisition device 104 and the client device 110.
Referring now to
At step 404, the password data is caused to be rendered on at least one display provided in at least one secured location of the aircraft. In one embodiment, the password data is caused to be rendered on the at least one display provided in a cockpit of the aircraft. It should however be understood that the password data may be rendered on any other suitable display provided in a secured location of the aircraft. Step 406 comprises receiving, subsequent to the password data being rendered on the at least one display, input data from at least one user device requesting access to the aviation data. Step 408 then comprises comparing the input data to the password data obtained at step 402. At step 410, a determination is made as to whether the input data matches (i.e. is the same as) the password data. If this is the case, a secure connection is established between the at least one user device and the data acquisition device(s) for providing the at least one user device access to the aviation data at step 412. In one embodiment, step 412 comprises establishing a wireless connection between the data acquisition device(s) and the at least one user device for routing the aviation data from the data acquisition device(s) to the at least one user device via the wireless connection. Otherwise, if the input data fails to match the password data, the at least one user device is denied access to the aviation data at step 414. Step 414 may comprise preventing establishment of the wireless connection between the data acquisition device(s) and the at least one user device.
The embodiments described herein are implemented by physical computer hardware, including computing devices, servers, receivers, transmitters, processors, memory, displays, and networks. The embodiments described herein provide useful physical machines and particularly configured computer hardware arrangements. The embodiments described herein are directed to electronic machines and methods implemented by electronic machines adapted for processing and transforming electromagnetic signals which represent various types of information. The embodiments described herein pervasively and integrally relate to machines, and their uses; and the embodiments described herein have no meaning or practical applicability outside their use with computer hardware, machines, and various hardware components. Substituting the physical hardware particularly configured to implement various acts for non-physical hardware, using mental steps for example, may substantially affect the way the embodiments work. Such computer hardware limitations are clearly essential elements of the embodiments described herein, and they cannot be omitted or substituted for mental means without having a material effect on the operation and structure of the embodiments described herein. The computer hardware is essential to implement the various embodiments described herein and is not merely used to perform steps expeditiously and in an efficient manner.
The term “connected” or “coupled to” may include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements).
The technical solution of embodiments may be in the form of a software product. The software product may be stored in a non-volatile or non-transitory storage medium, which can be a compact disk read-only memory (CD-ROM), a USB flash disk, or a removable hard disk. The software product includes a number of instructions that enable a computer device (personal computer, server, or network device) to execute the methods provided by the embodiments.
The embodiments described in this document provide non-limiting examples of possible implementations of the present technology. Upon review of the present disclosure, a person of ordinary skill in the art will recognize that changes may be made to the embodiments described herein without departing from the scope of the present technology. Yet further modifications could be implemented by a person of ordinary skill in the art in view of the present disclosure, which modifications would be within the scope of the present technology.
