System and method for data transfer via a display device including a bezel light sensor

A display system may include a bezel. The bezel may include a bezel light sensor. The display system may include a screen set within the bezel. The display system may include a controller coupled to the bezel light sensor. The controller may be configured to receive a flashing light signal via the bezel light sensor. The flashing light signal may include a set of coded information. The flashing light signal may be transmitted by a light generator. The controller may be configured to generate a response to the set of coded information. The controller may be configured to provide the response to the set of coded information via the screen.

BACKGROUND OF THE INVENTION

Operational errors are typically difficult to reproduce during testing, production, and/or field maintenance of avionics systems due to a limited availability of data and a difficulty in correlating data to a display event. Known troubleshooting methods such as PEEK or POKE, where specific memory regions and/or memory addresses are provided upon request, require bi-directional communication and special factory diagnostic modes. In avionics systems, PEEK capabilities may be impractical due to interface accessibility, and factory diagnostic modes may be impractical due to control limitations on production aircraft.

Bi-directional communication in avionics systems typically requires customized instrument buses (e.g., specific test equipment with customized wired inputs). The customized instrument buses may include complicated configurations, interfaces, functions, and/or faults. In addition, the instrument buses may be required to conform with select standard protocols (e.g., Ethernet, ARINC 429, ARINC 615A, ARINC 661, or the like). Further, the customized instrument buses may be limited by constraints imposed upon by original equipment manufacturers (OEMs) and/or component purchasers (e.g., airlines, or the like). Further, the customized instrument buses may require an advanced level of knowledge of relevant systems to configure the connections between customized instrument buses and an aircraft.

These configurations, interfaces, functions, faults, and/or standard protocols must be fully realized and completely defined during development. As such, production of the customized instrument buses may require considerable amounts of time, funds, paperwork, and coordination between involved parties during design, testing, and certification phases.

Therefore, it would be advantageous to provide a system and method that cures the shortcomings described above.

SUMMARY

In one aspect, embodiments of the inventive concepts disclosed herein are directed to an avionics display system. The avionics display system may include a bezel. The bezel may include a bezel light sensor. The avionics display system may include a screen set within the bezel. The avionics display system may include a controller coupled to the bezel light sensor. The controller may be configured to receive a flashing light signal via the bezel light sensor. The flashing light signal may include a set of coded information. The flashing light signal may be transmitted by a light generator. The controller may be configured to generate a response to the set of coded information. The controller may be configured to provide the response to the set of coded information via the screen.

In a further aspect, embodiments of the inventive concepts disclosed herein are directed to a method. The method may include receiving a flashing light signal via a bezel light sensor in a bezel of a display. The flashing light signal may include a set of coded information. The flashing light signal may be transmitted by a light generator. The method may include generating a response to the set of coded information. The method may include providing the response via a screen set within the bezel of the display.

In a further aspect, embodiments of the inventive concepts disclosed herein are directed to a system. The system may include a display. The display may include a bezel and a screen set within the bezel. The bezel may include a bezel light sensor. The system may include a controller coupled to the bezel light sensor. The controller may be configured to receive a flashing light signal via the bezel light sensor. The flashing light signal may include a set of coded information. The controller may be configured to generate a response to the set of coded information. The controller may be configured to provide the response to the set of coded information via the screen. The system may include a personal electronic device. The personal electronic device may include an imaging device configured to acquire one or more images. The personal electronic device may include a light generator configured to generate the flashing light signal. The flashing light signal may include a wavelength from a range of wavelengths. The personal electronic device may include a user controller. The user controller may be configured to transmit the set of coded information via the flashing light signal generated by the light generator. The user controller may be configured to acquire the response to the set of coded information from the screen via the imaging device.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Further, any arrangement of components to achieve a same functionality is effectively “associated” such that the desired functionality is achieved, such that any two components herein combined to achieve a particular functionality can be seen as “associated with” each other (irrespective of architectures or intermedial components). Any two components so associated can also be viewed as being “operably connected” or “operably coupled” to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable” to each other to achieve the desired functionality. Examples of operably couplable include, but are not limited to, physically mateable and/or physically interacting components, wirelessly interactable and/or wirelessly interacting components, logically interacting and/or logically interactable components, or the like.

FIGS. 1-14generally illustrate exemplary embodiments of a system and method for data transfer via a display device including a bezel light sensor in accordance with the inventive concepts disclosed herein.

Broadly, embodiments of the inventive concepts disclosed herein are directed to a system and method for data transfer via a display device including a bezel light sensor. More particularly, embodiments of the inventive concepts disclosed herein are directed to a system and method for data transfer via a display device including a bezel light sensor, where data is transmitted to and/or acquired from the display device including the bezel light sensor.

FIGS. 1-3generally illustrate example embodiments of an avionics environment in which a system and method for data transfer via a display device including a bezel light sensor may be implemented, in accordance with the inventive concepts disclosed herein. For example, as illustrated inFIG. 1, the avionics environment may include a cockpit100of an aircraft. By way of another example, as illustrated inFIG. 2, the avionics environment may include a galley200of an aircraft. By way of another example, as illustrated inFIG. 3, the avionics environment may include a cabin300of an aircraft.

The avionics environment (e.g., the cockpit100, the galley200, the cabin300, or the like) may include one or more display devices102. For example, the one or more display devices102may be employed to present electronic maps, aircraft performance parameters, aircraft performance parameter predictions, sensor readings, aircraft data, flight data, communications, alerts, and the like. For instance, the one or more display devices102may include, but are not limited to, one or more primary flight displays and/or one or more multi-function displays that are viewable by a flight crew member (e.g., pilot, co-pilot, or other on-board crew). It is noted herein, however, that the avionics environment (e.g., the cockpit100, the galley200, the cabin300, or the like) may include any number of display devices102(e.g., one, two, three, or more displays) including one or more primary flight displays, secondary flight displays, and/or multi-function displays.

Where the environment includes an avionics environment, it is noted herein the system and method for data transfer via a display device including a bezel light sensor may be configured in accordance with avionics guidelines and/or standards put forth by, but not limited to, the Federal Aviation Administration (FAA), the European Aviation Safety Agency (EASA) or any other flight certification agency or organization; the American National Standards Institute (ANSI), Aeronautical Radio, Incorporated (ARINC), or any other standards setting organization or company; the Radio Technical Commission for Aeronautics (RTCA) or any other guidelines agency or organization; or the like.

Although example embodiments of the present disclosure are directed to an avionics environment, it is noted herein the system and method for data transfer via a display device including a bezel light sensor may be configured to operate in any type of vehicle known in the art. For example, the vehicle may be any air, land, or water-based personal equipment or vehicle; any air, land, or water-based commercial equipment or vehicle; any air, land, or water-based military equipment or vehicle known in the art. For instance, an automobile may include a display device102. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

Although example embodiments of the present disclosure are directed to a vehicle including one or more display devices with a bezel light sensor, it is noted herein the system and method for data transfer via a display device including a bezel light sensor may be coupled to and/or configured to operate with any type of display device including a bezel light sensor known in the art.

For example, the system and method for data transfer via a display device including a bezel light sensor may be implemented by one or more unmanned aerial vehicle (UAV) control stations400, as illustrated inFIG. 4. The UAV control station400may include the one or more display devices102. The UAV control station400may be a standalone portable device (e.g., as illustrated inFIG. 4). It is noted herein, however, that the UAV control station400may be housed within and/or coupled to a facility or a moving vehicle (e.g., van, truck, boat, other aircraft, or the like). In addition, it is noted herein the UAV control station400may be subject to the avionics guidelines and/or standards as set forth above.

By way of another example, the system and method for data transfer via a display device including a bezel light sensor may be coupled to and/or configured to operate with any type of display device including a bezel light sensor known in the art, where the display device is sold for commercial or industrial use in either a home or a business. For example, a general-purpose computer or other consumer electronic device may include a display device102including a bezel light sensor. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

FIGS. 5-10generally illustrate an embodiment of a system500for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein.

The system500may include a controller502. The controller502may include one or more processors504and memory506. The memory may store one or more sets of program instructions508. The controller502may include one or more communication interfaces510. The controller502may be coupled to one or more display devices. For example, the one or more display devices may include, but are not limited to, the one or more display devices102. The controller502may be coupled to one or more input devices512. For example, the one or more input devices512may include, but are not limited to, an imaging device. For instance, the imaging device may include, but is not limited to, a bezel light sensor514(BLS514). It is noted herein that the controller502and the one or more display devices102may be considered an avionics display system, for purposes of the present disclosure.

The system500may include a flight management system (FMS)516. The FMS516may include a flight management system controller518(FMS controller518). THE FMS controller518may include one or more processors520and memory522. The memory522may store one or more sets of program instructions524. The FMS controller518may include one or more communication interfaces526. The FMS516may include one or more flight management system communication interfaces528(FMS communication interfaces528). The FMS516may be coupled to one or more sensors530. The FMS516may be coupled to the controller502.

Although embodiments of the present disclosure are directed to the controller502and the FMS controller518as separate components of the system500, it is noted herein that the controller502and the FMS controller518may be the same component within the system500. In addition, although embodiments of the present disclosure are directed to the one or more communication interfaces510, the one or more communication interfaces526, and/or the one or more FMS communication interfaces528as separate components of the system500, it is noted herein the one or more communication interfaces510, the one or more communication interfaces526, and/or the one or more FMS communication interfaces528may be the same component within the system500. In this regard, the one or more display devices102and/or the one or more input devices512may be coupled to the controller502and/or the FMS controller518. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

The system500may include a user controller532. The user controller532may include one or more processors534and memory536. The memory536may store one or more sets of program instructions538. The user controller532may include one or more communication interfaces540. The user controller532may be coupled to one or more display devices542.

The user controller532may be coupled to one or more input devices544. For example, the one or more input devices544may include an imaging device configured to acquire one or more images. For instance, the imaging device may include, but is not limited to, a camera546. The user controller532may be coupled to one or more output devices548. For example, the one or more output devices548may include a light generator. For instance, the light generator may include, but is not limited to, a device configured to produce a light such as a camera flash550. The user controller532may be coupled to one or more accessories552. For example, the one or more accessories522may include, but are not limited to, a case554.

Although embodiments of the present disclosure are directed to the one or more input devices544(e.g., a camera546) and the one or more output devices548(e.g., a camera flash550) being coupled to the user controller532, it is noted herein that the input device544and/or the output device548may be standalone components from the user controller532.

The controller502, the FMS controller518, and/or the user controller532may be a computer including, but not limited to, a desktop computer, a mainframe computer system, a workstation, an image computer, a parallel processor, a networked computer, or the like. The controller502, the FMS controller518, and/or the user controller532may be a personal electronic device. For example, the personal electronic device may include a handheld computer such as, but not limited to, a smartphone, a tablet, a phablet, or the like. By way of another example, the personal electronic device may include a laptop computer such as, but not limited to, a laptop with a single-fold hinge, a laptop with a double-fold hinge, a laptop with a twist-and-fold hinge, a laptop with a detachable display device and/or a detachable user input device, or the like.

The one or more processors504,520,534may include any one or more processing elements known in the art. In this sense, the one or more processors504,520,534may include any microprocessor device configured to execute algorithms and/or program instructions. In general, the term “processor” may be broadly defined to encompass any device having one or more processing elements, which execute a set of program instructions from a non-transitory memory medium (e.g., the memory506,522,536), where the one or more sets of program instructions508,524,538is configured to cause the one or more processors504,520,534to carry out any of one or more process steps.

The memory506,522,536may include any storage medium known in the art suitable for storing the one or more sets of program instructions508,524,538executable by the associated one or more processors504,520,534. For example, the memory506,522,536may include a non-transitory memory medium. For instance, the memory506,522,536may include, but is not limited to, a read-only memory (ROM), a random access memory (RAM), a magnetic or optical memory device (e.g., disk), a magnetic tape, a solid state drive, and the like. The memory506,522,536may be configured to provide display information to the display device (e.g., display devices102,542). In addition, the memory506,522,536may be configured to store user input information from a user input device (e.g., input devices512,544). The memory506,522,536may be housed in a common controller housing with the one or more processors504,520,534. The memory506,522,536may, alternatively or in addition, be located remotely with respect to the spatial location of the processors504,520,534and/or the controller502,518,532. For instance, the one or more processors504,520,534and/or the controller502,518,532may access a remote memory506,522,536(e.g., server), accessible through a network (e.g., internet, intranet, and the like) via the one or more communication interfaces510,526,528,540.

The controller502,518,532may be configured to receive and/or acquire data or information from other systems or tools via the one or more communication interfaces510,526,528,540that may include wireline and/or wireless portions. In addition, the controller502,518,532may be configured to transmit data or information (e.g., the output of one or more procedures of the inventive concepts disclosed herein) to one or more systems or tools via the one or more communication interfaces510,526,528,540that may include wireline and/or wireless portions. In this regard, the transmission medium may serve as a data link between the controllers502,518,532and other subsystems. In addition, the controllers502,518,532may be configured to send data to external systems via a transmission medium (e.g., network connection).

The one or more display devices102,542may include any display device known in the art. For example, the one or more display devices102,542may include, but are not limited to, a liquid crystal display (LCD), a light-emitting diode (LED) based display, an organic light-emitting diode (OLED) based display, an electroluminescent display (ELD), an electronic paper (E-ink) display, a plasma display panel (PDP), a display light processing (DLP) display, or the like. Those skilled in the art should recognize that a variety of display devices may be suitable for implementation in the present invention and the particular choice of display device may depend on a variety of factors, including, but not limited to, form factor, cost, and the like. In a general sense, any display device capable of integration with the user input device (e.g., touchscreen, bezel mounted interface, keyboard, mouse, trackpad, and the like) is suitable for implementation in the present invention.

The one or more input devices512,544may include any user input device known in the art. For example, the one or more input devices512,544may include, but are not limited to, a keyboard, a keypad, a touchscreen, a lever, a knob, a scroll wheel, a track ball, a switch, a dial, a sliding bar, a scroll bar, a slide, a handle, a touch pad, a paddle, a steering wheel, a joystick, a bezel input device, or the like. In the case of a touchscreen interface, those skilled in the art should recognize that a large number of touchscreen interfaces may be suitable for implementation in the present invention. For instance, the one or more display devices102,542may be integrated with a touchscreen interface, such as, but not limited to, a capacitive touchscreen, a resistive touchscreen, a surface acoustic based touchscreen, an infrared based touchscreen, or the like. In a general sense, any touchscreen interface capable of integration with the display portion of a display device is suitable for implementation in the present invention. In another embodiment, the input devices512,544may include, but is not limited to, a bezel mounted interface.

Although embodiments of the present disclosure are directed to the one or more display devices102,542being indirectly coupled to the corresponding one or more input devices512,544indirectly (e.g., via the controller502or the user controller532), it is noted herein the one or more display devices102,542may be directly coupled to the corresponding one or more input devices512,544. For example, the one or more display devices102,542may be housed with the one or more input devices512,544in a common user interface housing. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

As illustrated inFIG. 6, the display device102coupled to the controller502may include a bezel600. The bezel light sensor514may be attached to a surface of, or inset within, the bezel600. A screen602may be set within (e.g., housed within and/or mounted to) the bezel600. A filter604may be coupled to the bezel600of the display device102in a position proximate to (e.g., in front of) the bezel light sensor514. For example, the filter604may be coupled directly to a surface of the bezel600via an adhesive, one or more fasteners, or the like. By way of another example, the filter604may be a component of an assembly that interacts with a mounting bracket (e.g., via an interlocking tab assembly, an adhesive, one or more fasteners, or the like), where the mounting bracket is coupled to the surface of the bezel600.

As generally illustrated inFIGS. 7A-7C, the user controller532may include a smartphone or other handheld computer. The user controller532may include and/or be coupled to the camera546. The user controller532may include and/or be coupled to the one or more output devices548(e.g., the camera flash550) configured to operate in conjunction with and/or independently of the one or more input devices (e.g., the camera546). A filter604may be coupled to the user controller532in a position proximate to (e.g., in front of) the one or more output devices548.

As illustrated inFIG. 7A, the filter604may be coupled to a surface700of the user controller532in a position proximate to (e.g., in front of) the camera flash550such that the filter604at least partially covers the camera flash550. For example, the filter604may be coupled directly to the surface700of the user controller532via an adhesive, one or more fasteners, or the like. By way of another example, the filter604may be a component of an assembly that interacts with a mounting bracket (e.g., via an interlocking tab assembly, an adhesive, one or more fasteners, or the like), where the mounting bracket is coupled to the surface700of the user controller532.

As illustrated inFIG. 7B, the user controller532may be housed within the case554. The filter604may be coupled to the case554in a position proximate to (e.g., in front of) the camera flash550such that the filter604at least partially covers the camera flash550. For example, the filter604may be coupled directly to a surface of the case554via an adhesive, one or more fasteners, or the like. By way of another example, the filter604may be a component of an assembly that interacts with a mounting bracket (e.g., via an interlocking tab assembly, an adhesive, one or more fasteners, or the like), where the mounting bracket is coupled to the surface of the case554.

As illustrated inFIG. 7C, the user controller532may be housed within the case554. The filter604may be at least partially integrated with the case554in a position proximate to (e.g., in front of) the camera flash550such that the filter604at least partially covers the camera flash550. For example, the filter604may be installed or otherwise inset within a hole or groove of the case554. By way of another example, the case554may be fabricated from a material with light-altering qualities similar to those provided by the filter604.

Although embodiments of the present disclosure are directed to the camera546and/or the camera flash550being integrated components of the user controller532, it is noted herein that the camera546and/or the camera flash550may be separate components (e.g., are accessories552) of the user controller532. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

FIG. 8illustrates the system500for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein.

The screen602of the display device102may include a graphical user interface (GUI)800, where the GUI800includes one or more GUI windows. For example, the one or more GUI windows may include one or more menus802. By way of another example, the one or more GUI windows may include one or more display areas804. For instance, where the system500is implemented in an avionics environment, the one or more display areas804may include, but are not limited to, an avionics systems list, a command list corresponding to the avionics systems list, an avionics systems selection display area for displaying data following a selection being made from the command list, or the like. By way of another example, the one or more GUI windows may include a set of display area controls806for the one or more display areas804.

The bezel600may include the bezel light sensor514. The bezel light sensor514may assist in performing a number of functions. For example, the bezel light sensor514may assist in preventing screen white-out when entering a sunlit portion of the sky after exiting cloud cover by adjusting screen brightness level. In this regard, the system500may be utilized in an avionics environment (e.g., the aircraft cockpit100, the aircraft galley200, the aircraft cabin300), utilized with the UAV control station400. More generally, the system500may be utilized in any vehicle including a display device102including the bezel light sensor514. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

The system500may allow for bi-directional wireless communication between the controller502and the user controller532. For example, the user controller532may include a smartphone with the camera546and the camera flash550. For instance, the camera flash550may transmit data via a flashing light signal to the controller502via the bezel light sensor514of the display device102. In addition, the camera546may be utilized to receive information displayed on the display device102, where the information is displayed either prior to or in response to the data transmitted via the flashing light signal from the camera flash550received by the bezel light sensor514.

The wavelength of the light may be variable and/or adjustable. For example, the light emanating from the camera flash550may be of a wavelength that is readable by the bezel light sensor514. For instance, the bezel light sensor514may be configured to receive light emanating from the camera flash550of a wavelength in the visible light spectrum wavelength range (e.g., 400 nanometers (nm)-700 nm). In addition, the filter604coupled to the bezel600in a position proximate to the bezel light sensor514, and/or coupled to the user controller532in a position proximate to the camera flash550may convert the wavelength of a light emanating from the camera flash550to fall within a spectrum range including, but not limited to, the infrared spectrum wavelength range (e.g., 700 nm-1000 nm or 1 millimeter (mm)), the ultraviolet spectrum wavelength range (e.g., 10 nm-400 nm), or any other spectrum wavelength range known in the art. As illustrated inFIGS. 6-7Cand described above, the filter604may be coupled to the bezel600proximate to the bezel light sensor514and/or may be coupled to the user controller532proximate to the camera flash550.

The rate of flash for the light may be variable and/or adjustable. For example, the light may be transmitted in the form of a known code at a select flash speed. For instance, the code may include, but is not limited to, Morse code. The code transmitted by the flashing light may be pre-determined or dynamic via an application configured to operate with the user controller532. For example, the code transmitted by the flashing light may be a hexadecimal memory address, a data upload request, or the like. It is noted herein the code transmitted by the flashing light may be patterned or un-patterned. In addition, it is noted herein that the code transmitted by the flashing light may be proprietary, which may provide a layer of security to prevent unauthorized users from accessing the system. Further, it is noted herein the code transmitted by the flashing light may be preceded by an authentication process (e.g., an authentication handshake, a pre-defined security password code, or the like). Further, where the system500is implemented in an avionics environment, it is noted herein the avionics environment may include an in-air interlock or lock-out to prevent the requesting and/or uploading of data during operation (e.g., limiting the use of the system500to flight testing and/or production access phases).

FIG. 9illustrates a graph of a received code utilized for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein. InFIG. 9, a graph900illustrates data902generated by the receipt of a code transmitted by the flashing light including the letters A, B, C, D, E, and F in Morse code via the bezel light sensor514. It is noted herein the flashing light was generated via the camera flash550coupled to the user controller532. In addition, it is noted herein the data902was processed by the bezel light sensor514, digitized, and monitored through physical output ports coupled to the display device102, where the physical output ports are subject to the definitions set forth in the ARINC 429 data transfer standard, to illustrate the applicability of the system500to avionics systems.

In graph900, pulses904in the data902of light intensity correspond to the dots and dashes representing the letters provided via Morse code. For example, the graph900shows a short light pulse906and a long pulse908that corresponds to the portion of the received code transmitted by the flashing light representing the letter A. For instance, the short light pulse906may correspond to a one-hundred millisecond (ms) light pulse, while the long light pulse908may correspond to a three-hundred millisecond light pulse. Overlaid data910is provided to illustrate the correspondence between the light pulses906,908to the letters transmitted in Morse code as provided above the graph900. It is noted herein the example provided with respect to the letter A extends to the other letters B-F.

The light intensity inFIG. 9is provided as a percentage of possible output for the light source generating the code transmitted by the flashing light and converted to a range between 0 and 1. It is noted herein that the pulse speed inFIG. 9should not be interpreted as a limitation on the present disclosure but merely an illustration. For example, it is noted herein that the sampling speed of the light should be at least three times the speed of data use, and that the sampling rate would preferably be at least five times the speed of data use.

The duration of the light may be variable and/or adjustable. For example, the light may be flashed for a set period of time, where the set period of time is either pre-determined or dynamic via the application configured to operate with the user controller532. For instance, a patterned code may be provided once over a set period of time. In addition, a patterned code may be repeated and/or cycled for a set period of time.

The intensity of the light may be variable and/or adjustable via the application configured to operate with the user controller532. It is noted herein, however, where the user controller532is a smartphone with a camera flash550, different smartphone manufacturers may include camera flashes550of different intensities.

Although the graph900illustrates the transmission of data via a binary flash on/off pairing, it is noted herein that a variable and/or adjustable wavelength, rate of flash, duration, intensity, or the like may provide a more advanced and/or more efficient algorithm able to accomplish a broader range of data transmission than possible via a binary flash on/off pairing. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

In addition, it is noted herein that one or more operations of the light production and transmittal by the user controller532may be accomplished with the application configured to operate with the user controller532. For example, the application may include controls to create a flashing light signal that includes a patterned code. By way of another example, the application may include one or more controls necessary to generate a flashing light signal of varying wavelength, flash speed, duration, intensity, or the like. By way of another example, the application may provide a series of one or more calibration tests to allow the camera flash550to generate a flashing light signal of varying wavelength, flash speed, duration, intensity, or the like. The application may be proprietary and/or designed in-house. However, it is noted herein that one or more operations of the light production and transmittal by the user controller532may be accomplished with built-in and/or third-party applications.

The user controller532may transmit different types of information depending on the wavelength, flash speed, duration, intensity, or the like of the light provided by the camera flash550.

The user controller532may transmit a request for one or more sets of data from the controller502. Upon receipt of the request for one or more sets of data via the bezel light sensor514, one or more responses may be provided on the display device102.

FIG. 10is an example embodiment of a display device utilized for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein.

The one or more responses may include, but are not limited to, one or more dynamic quick response (QR) codes displayed on the screen602and/or data encoded into one or more graphical elements on the screen602using one or more steganography techniques, where data is hidden within an ordinary image in an unnoticeable way via an encoding algorithm (e.g., an encoding algorithm that defines bit values as corresponding to colors, where the colors may include minor variations in standard pixel color). It is noted herein that systems and methods for responding to memory retrieval requests via steganography is described in U.S. Pat. No. 10,425,461 to James M. Zaehring, filed on Sep. 24, 2019, which is incorporated herein by reference in the entirety. In addition, it is noted herein that systems and methods for responding to memory retrieval requests via QR code under the ARINC 661 standard protocol is described in U.S. Pat. No. 10,108,889 to James M. Zaehring and Travis J. Floyd, filed on Oct. 23, 2018, which is incorporated herein by reference in the entirety.

The QR code1000may be displayed on the GUI800(e.g., a QR code widget) on the display device102. One or more QR code data area GUI windows1002may be provided with the QR code1000to provide supplementary information with the QR code1000(e.g., memory location of data provided with the QR code1000, or the like). The QR code1000may correspond to a particular data set located in response to the request for one or more data sets. Where the display device102including the bezel light sensor514is a component on an aircraft, the QR code1000may be subject to the definitions set forth in the ARINC 661 cockpit display system (CDS) and user applications (UA) standard. The camera546may be utilized to scan the QR code1000for recordation and/or analysis by the user controller532and/or another coupled controller.

It is noted herein that a graphical element may be displayed over the location of the QR code1000within the QR code widget. For example, the graphical element may be displayed while the controller502is preparing the QR code1000and/or while the controller502is awaiting a response from the user controller532. For instance, the graphical element may be a dynamic element including, but not limited to, an hourglass or the like. In addition, the graphical element may be a static element including, but not limited to, a confirmation symbol, a colored box, a logo, or the like.

The one or more responses may be in the form of data dynamically encoded into one or more graphical elements of the one or more GUI windows802,804,806, and/or1002of the GUI800. For example, the data may be hidden by the encoding algorithm within one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002of the GUI800. For example, a pixel1004may include three eight-bit values. The camera546may be utilized to scan the one or more graphical elements for recordation and/or analysis (e.g., decoding) by the user controller532and/or another coupled controller. For example, the camera546may be of sufficient resolution to distinguish the one or more pixels1004including the encoded data from the remainder of the one or more pixels1004.

It is noted herein that the user controller532may scan and/or record the QR code and/or a set of steganographic data may be accomplished with an application. For example, the application may include a QR code reader that utilizes the camera546to scan and/or record the QR code1000displayed on the screen602of the display device102coupled to the controller502. By way of another example, the application may utilize the camera546to scan, record, and/or decode the steganographic data displayed on the screen602of the display device102coupled to the controller502. The application may be proprietary and/or designed in-house. However, it is noted herein that one or more operations of the light production and transmittal by the user controller532may be accomplished with built-in and/or third-party applications.

In addition, it is noted herein that a QR code and/or a set of steganographic data may only contain a select amount of data, Where the requested one or more sets of data are too large to be provided within a single response (e.g., a single QR code or embedded within available pixels1004), the controller502may need to generate and display multiple QR codes and/or multiple sets of steganographic data, where each QR code and/or set of steganographic data provides only a portion of the requested one or more sets of data. In this example, the user controller532may transmit a flashing light signal including a continue signal (e.g., a single flash, a code including a continue command, or the like) indicating that the controller502may provide an additional response including a portion of the requested one or more sets of data when the user controller532is ready to receive the additional response. In the alternative, the controller502may transmit the additional portion after waiting a pre-determined amount of time. In this regard, the QR code1000and/or the set of steganographic data hidden within the one or more pixels1004may be dynamic, allowing for the increased amount of transferable data via the GUI800.

It is noted herein that feedback (e.g., a success signal) regarding the success of data capture via steganography and QR codes increases the reliability of the data transfer. For example, the feedback may be in the form of an ACK/NAK (or ACK/NACK) protocol utilizing acknowledgement and negative-acknowledgement signals, a flash from the camera flash550, a graphical element displayed on the screen602of the display device102, or the like.

In this regard, dynamic QR codes and dynamically-hidden data encoded via steganographic techniques may provide targeted information (e.g., targeted troubleshooting data, or the like) specific to a current issue in response to requests for the one or more sets of data from the user controller532via the bezel light sensor514. For example, where the system500is implemented in an avionics environment, this dynamic providing of data may allow for the routing of memory troubleshooting via PEEK and/or POKE techniques through the ARINC 661 protocol instead of wired physical ports, expanding the use of the PEEK and/or POKE techniques. It is noted herein, however, that PEEK and/or POKE techniques are not limited to the ARINC 661 protocol. In addition, it is noted herein that the system500is not limited to providing dynamic QR codes and dynamically-hidden data encoded via steganographic techniques as responses to received data requests. Therefore, the above description should not be interpreted as a limitation on the present disclosure but merely an illustration.

The user controller532may transmit one or more sets of data to be uploaded to the controller502as a whole or in one or more packets. For example, the data may include updates to software or firmware, new data for the controller502to analyze, or the like. For instance, the data may be uploaded via protocols that transmit data at speeds ranging from kbits/sec to Mbits/sec utilizing infrared light (e.g., protocols defined by the Infrared Data Association (IrDA) including, but not limited to, Infrared Physical Layer Specification (IrPHY), Infrared Link Access Protocol (IrLAP), Infrared Link Management Protocol (IrLMP), (Infrared Local Area Network (IrLAN), IrSimple, or the like), where the bezel light sensor514and/or the camera flash550is covered by the filter604. In addition, the data may be uploaded via protocols adapted to visible light spectrums.

Where the data is uploaded in packets, the controller502may indicate it is ready to receive the next data upload packet (e.g., via an ACK/NA(C)K protocol response, a dynamic or static graphical element, or the like) via a continue signal on the display device102. In the alternative, the user controller532may transmit the next data upload packet after waiting a pre-determined amount of time. Once all data upload packets are received, the update may be reconstructed and installed. In addition, the user controller532may provide a code to reset the controller502to factory settings if necessary.

Where the system500is implemented within an avionics environment, implementing the improved diagnostic capabilities afforded by the system500may only require updating of software and/or firmware within the controller502as the system500is wireless and employs pre-existing aircraft sensors (e.g., the bezel light sensor514). In this regard, additional hardware (e.g., wired diagnostic ports) may not need to be added to the avionics environment, greatly reducing the amount of time and/or funding required to incorporate the improved diagnostic capabilities within the avionics environment.

As such, the system500may allow for dynamic and live-configurable requesting of and retrieval of troubleshooting data of an avionics environment. In addition, the system500may also reduce the amount of time necessary to analyze avionics systems within the avionics environment. Further, the system500may allow for dynamic updating of software and/or resetting to factory options via wireless operations instead of wired physical ports. In this regard, the amount and/or criticality of time, funds, paperwork, and coordination between involved parties during design, testing, and certification phases may be reduced.

FIGS. 11-14generally illustrate methods for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts herein.

FIG. 11illustrates a method1100for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein. In one example, the method1100may be implemented by the user controller532of the system500.

A step1102may include generating a data request. The data request may be generated via an application loaded onto the user controller532, where the application includes one or more sets of program instructions configured to cause the processors of the user controller532to generate the data request.

A step1104may include transmitting the data request to a controller via a bezel light sensor in a display device. The data request may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. The controller502may receive the data request via the bezel light sensor514in the display device102.

A step1106may include scanning a screen of the display device for a response to the data request. The user controller532may be positioned to allow the camera546to scan the one or more GUI windows802,804,806, and/or1002of the GUI800. The controller502may generate a response to the data request and provide it on the GUI800. For example, the response may be in the form of the QR code1000. By way of another example, the response may include data encoded via one or more steganographic techniques into the one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800. It is noted herein the response may be the first response of a set of multiple responses.

A step1108may include constructing the requested data from the scanned response. Where the scanned response is the only response from the controller502, the requested data is the scanned response.

A step1110may include generating a continue signal. The continue signal may be generated via an application loaded onto the user controller532, where the application includes one or more sets of program instructions configured to cause the processors of the user controller532to generate the continue signal.

A step1112may include transmitting the continue signal to the controller via the bezel light sensor in the display device. The continue signal may be transmitted to the controller502by the user controller532. For example, the continue signal may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. The controller502may receive the continue signal via the bezel light sensor514on the display device102.

As an alternative to steps1110and1112, a step1114may include waiting a pre-determined amount of time. The one or more sets of program instructions configured to cause the processors of the user controller532may include a pre-determined amount of time between receiving responses. For example, the pre-determined period of time may take into account the amount of time necessary for the user controller532to stop transmitting the data request with the camera flash550, be re-positioned to a scanning position, activate the camera546, scan the screen602of the display device102for a response, store the scanned response to memory536, analyze the scanned and/or stored response with the one or more processors534, or take another action.

A step1116may include scanning the screen of the display device for an additional response to the data request. The controller502may generate an additional response to the data request and provide it on the GUI800. For example, the additional response may be in the form of the QR code1000. By way of another example, the additional response may include data encoded via one or more steganographic techniques into the one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800.

It is noted herein the response to the data request and the additional response may be repeated on the screen of the display device. For example, the response to the data request and the additional response may be repeated a set number of cycles. By way of another example, the response to the data request and the additional response may be repeated a set amount of time. By way of another example, the response to the data request and the additional response may be repeated until a stop signal is received from the user controller532.

A step1118may include constructing the requested data from the multiple scanned responses (e.g., the first response and the additional response, or the like). For example, the user controller532may reconstruct the requested data from multiple scanned dynamic QR codes1000. By way of another example, the user controller532may reconstruct the requested data from multiple scanned sets of data encoded into pixels1004via one or more steganographic techniques. By way of another example, the user controller532may reconstruct the requested data from a combination of one or more scanned dynamic QR codes1000and one or more scanned sets of data encoded into the one or more pixels1004via the one or more steganographic techniques. It is noted herein the one or more sets of program instructions538may be configured to cause the processors534of the user controller532to store the responses and construct the requested data from the scanned responses after all responses are scanned and stored, to store the responses and construct the requested data in batches after a select number of the responses are scanned and stored, and/or to construct the requested data as each response is scanned. In addition, it is noted herein the scanned responses may include a marker (e.g., sequential number, value, label, or the like) to assist the user controller532in constructing the response from the scanned responses.

An optional step1120may include transmitting a data capture success signal to the controller via the bezel light sensor in the display device. The success signal may be generated via an application loaded onto the user controller532, where the application includes one or more sets of program instructions configured to cause the processors of the user controller532to generate the success signal. The success signal may be transmitted by the user controller532to the controller502. For example, the success signal may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. By way of another example, the controller502may receive the success signal via the bezel light sensor514on the display device102.

FIG. 12illustrates a method1200for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein. In one example, the method1200may be implemented by the controller502coupled to the one or more display devices102of the system500.

A step1202may include receiving a data request from an electronic device via a bezel light sensor in a display device. The controller502may receive the data request via the bezel light sensor514on the display device102. The data request may be transmitted by the user controller532. For example, the data request may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532.

A step1204may include analyzing the data request. The user controller532may include one or more sets of program instructions configured to cause the processors of the user controller532to analyze the data request for a pattern, and one or more additional sets of program instructions to decode the pattern. For example, the pattern may include a request for data such as, but not limited to, error data, log data, system state data, or other data that may be utilized to perform diagnostic tests.

A step1206may include generating a response to the data request. The controller502may locate the data corresponding to the requested information. For example, the controller502may retrieve data stored at the hexadecimal memory addresses. By way of another example, the controller502may retrieve operational statuses of systems coupled to the controller502. For instance, where the system500is implemented in an avionics environment, the operational statuses may include data obtained via the one or more sensors530coupled to the FMS516, error checks performed by the FMS516, or the like. It is noted herein the generated response may be the first generated responses of a set of multiple generated responses.

A step1208may include providing the response to the electronic device on a screen of the display device. For example, the response may be in the form of a QR code1000. By way of another example, the response may include data encoded via one or more steganographic techniques into one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800.

A step1210may include generating an additional response to the data request. The controller502may locate the data corresponding to the requested information. For example, the controller502may retrieve data stored at the hexadecimal memory addresses. By way of another example, the controller502may retrieve operational statuses of systems coupled to the controller502. For instance, where the system500is implemented in an avionics environment, the operational statuses may include data obtained via the one or more sensors530coupled to the FMS516, error checks performed by the FMS516, or the like.

A step1212may include receiving a continue signal via the bezel light sensor in the display device. The continue signal may be transmitted to the controller502by the user controller532. For example, the continue signal may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. The controller502may receive the continue signal via the bezel light sensor514on the display device102.

As an alternative to step1212, a step1214may include waiting a pre-determined amount of time. The one or more sets of program instructions configured to cause the processors of the controller502may include a pre-determined period of wait time between providing responses. For example, the pre-determined amount of wait time may take into account the amount of time necessary for the user controller532to stop transmitting the data request with the camera flash550, be re-positioned to a scanning position, activate the camera546, scan the screen602of the display device102for a response, store the scanned response to memory536, analyze the scanned and/or stored response with the one or more processors534, or take another action.

A step1216may include providing the additional response to the electronic device via the screen of the display device. For example, the response may be in the form of a QR code1000. By way of another example, the response may include data encoded via one or more steganographic techniques into one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800.

It is noted herein the response to the data request and the additional response may be repeated on the screen of the display device. For example, the response to the data request and the additional response may be repeated a set number of cycles. By way of another example, the response to the data request and the additional response may be repeated a set amount of time. By way of another example, the response to the data request and the additional response may be repeated until a stop signal is received from the user controller532.

An optional step1218may include receiving a data capture success signal from the electronic device via the bezel light sensor in the display device. The success signal may be transmitted by the user controller532. For example, the success signal may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. The controller502may receive the success signal via the bezel light sensor514on the display device102.

FIG. 13illustrates a method1300for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein. In one example, the method1300may be implemented by the user controller532of the system500.

A step1302may include generating a data upload packet. The data upload packet may be generated via an application loaded onto the user controller532, where the application includes one or more sets of program instructions configured to cause the processors of the user controller532to generate the data upload packet. It is noted herein the data upload packet may be the first data upload packet of a set of multiple data upload packets.

A step1304may include transmitting the data upload packet to a controller via a bezel light sensor in a display device. The data upload packet may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. The controller502may receive the data upload packet via the bezel light sensor514in the display device102.

A step1306may include generating an additional data upload packet. The additional data upload packet may be generated via an application loaded onto the user controller532, where the application includes one or more sets of program instructions configured to cause the processors of the user controller532to generate the additional data upload packet.

A step1308may include scanning a screen of the display device for a continue signal from the controller. The user controller532may be positioned to allow the camera546to scan the one or more GUI windows802,804,806, and/or1002of the GUI800. The controller502may generate a continue signal and provide it on the GUI800. For example, the continue signal may be in the form of a QR code1000. By way of another example, the continue signal may include data encoded via one or more steganographic techniques into one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800.

As an alternative to step1308, a step1310may include waiting a pre-determined amount of time. The one or more sets of program instructions configured to cause the processors of the user controller532may include a pre-determined period of wait time between transmitting data upload packets. For example, the pre-determined period of wait time may take into account the amount of time necessary for the user controller532to stop transmitting the data upload packet with the camera flash550, be re-positioned to a scanning position, activate the camera546, retrieve and/or compile the additional data uploaded packet, or take another action.

A step1312may include transmitting the additional data upload packet to the controller via the bezel light sensor in the display device. The additional data upload packet may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. The controller502may receive the additional data upload packet via the bezel light sensor514in the display device102.

It is noted herein the data upload packet and the additional data upload packet may be repeated on the screen of the display device. For example, the data upload packet and the additional data upload packet may be repeated a set number of cycles. By way of another example, the data upload packet and the additional data upload packet may be repeated a set amount of times. By way of another example, the data upload packet and the additional data upload packet may be repeated until a stop signal is received by the user controller532.

An optional step1314may include scanning the screen of the display device for a data capture success signal. The user controller532may be positioned to allow the camera546to scan the one or more GUI windows802,804,806, and/or1002of the GUI800. The controller502may generate a success signal and provide it on the GUI800. For example, the success signal may be in the form of a QR code1000. By way of another example, the success signal may include data encoded via one or more steganographic techniques into one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800.

FIG. 14illustrates a method1400for data transfer via a display device including a bezel light sensor, in accordance with the inventive concepts disclosed herein. In one example, the method1400may be implemented by the controller502coupled to the one or more display devices102of the system500.

A step1402may include receiving a data upload packet from an electronic device via a bezel light sensor in a display device. The controller502may receive the data upload packet via the bezel light sensor514on the display device102. The data upload packet may be transmitted by the user controller532. For example, the data upload packet may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532. It is noted herein the data upload packet may be the first data upload packet of a set of multiple data upload packets.

A step1404may include constructing an uploaded data file from the received data upload packet. Where the uploaded data packet is the only received packet from the user controller532, the uploaded data file includes the received uploaded data packet.

A step1406may include generating a continue signal. The continue signal may be generated via an application loaded onto the controller502, where the application includes one or more sets of program instructions configured to cause the processors of the controller502to generate the continue signal.

A step1408may include providing the continue signal to the electronic device on a screen of the display device. For example, the continue signal may be in the form of the QR code1000. By way of another example, the continue signal may include data encoded via one or more steganographic techniques into the one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800.

As an alternative to steps1406and1408, a step1410may include waiting a pre-determined amount of time. The one or more sets of program instructions configured to cause the processors of the controller502may include a pre-determined period of wait time between receiving data upload packets. For example, the pre-determined period of wait time may take into account the amount of time necessary for the user controller532to stop transmitting the data upload packet with the camera flash550, be re-positioned to a scanning position, activate the camera546, retrieve and/or compile the additional data uploaded packet, or take another action.

A step1412may include receiving an additional data upload packet from the electronic device via the bezel light sensor in the display device. The controller502may receive the additional data upload packet via the bezel light sensor514on the display device102. The additional data upload packet may be transmitted by the user controller532. For example, the additional data upload packet may be transmitted as one or more light flashes from the camera flash550coupled to the user controller532.

It is noted herein the data upload packet and the additional data upload packet may be repeated on the screen of the display device. For example, the data upload packet and the additional data upload packet may be repeated a set number of cycles. By way of another example, the data upload packet and the additional data upload packet may be repeated a set amount of times. By way of another example, the data upload packet and the additional data upload packet may be repeated until a stop signal is received by the user controller532.

A step1414may include constructing the uploaded data file from multiple data upload packets. The data upload packets may include a marker (e.g., sequential number, value, or the like) to assist the controller502in constructing the response from the scanned responses. In addition, it is noted herein the one or more sets of program instructions508may be configured to cause the processors504of the controller502to store the data upload packets and construct the uploaded data file from the data upload packets after all are uploaded and stored, to store the data upload packets and construct the uploaded data file in batches after a select number of the data upload packets are uploaded and stored, and/or to construct the data upload packets as each data upload packet is uploaded.

An optional step1416may include providing a data capture success signal to the electronic device on the screen of the display device. The success signal may be generated via an application loaded onto the controller502, where the application includes one or more sets of program instructions configured to cause the processors of the controller502to generate the success signal. The success signal may be provided by the controller502to the user controller532. For example, the continue signal may be in the form of the QR code1000. By way of another example, the continue signal may include data encoded via one or more steganographic techniques into the one or more pixels1004of the one or more graphical elements within the one or more GUI windows802,804,806, and/or1002on the GUI800.

A step1418may include installing the uploaded data file. The uploaded data file may include one or more updates to software and/or firmware installed on the controller502and/or on systems coupled to the controller502.

It is noted herein the methods1100,1200,1300,1400are not limited to the steps provided. For example, the methods1100,1200,1300,1400may instead include more or fewer steps. By way of another example, the methods1100,1200,1300,1400may perform the steps in an order other than provided. Therefore, the above description should not be interpreted as a limitation on the scope of the present disclosure, but merely an illustration.

As will be appreciated from the above embodiments, the inventive concepts disclosed herein are directed to a system and method for data transfer via a display device including a bezel light sensor, where data is transmitted to and/or acquired from the display device including the bezel light sensor.