Display brightness control based on location data

Information

  • Patent Grant
  • 10321549
  • Patent Number
    10,321,549
  • Date Filed
    Friday, February 12, 2016
    8 years ago
  • Date Issued
    Tuesday, June 11, 2019
    5 years ago
Abstract
The exemplary embodiments herein provide a method for controlling the luminance of an electronic display, including the steps of determining the sunset and sunrise times for the day and determining whether the present time is between sunrise and sunset or between sunset and sunrise. The backlight may be driven at a daytime level if the present time is between sunrise and sunset, while the backlight may be driven at a nighttime level if the present time is between sunset and sunrise. In some embodiments, artificial ambient sensor (AAS) data is used to determine the desired backlight or display luminance. The AAS data may be adjusted for a sunset or sunrise transition time, as well as for an approximate percentage of cloud cover in the sky.
Description
TECHNICAL FIELD

Exemplary embodiments relate generally to a system and method for controlling the brightness of a display based on several types of data.


BACKGROUND

Electronic displays have become useful for not only indoor entertainment purposes, but are now being utilized for indoor and outdoor advertising/informational purposes. For example, liquid crystal displays (LCDs), plasma displays, OLEDS, and many other flat panel displays are now being used to display information and advertising materials to consumers in locations outside of their own home or within airports, arenas, stadiums, restaurants/bars, gas station pumps, billboards, and even moving displays on the tops of automobiles or on the sides of trucks.


The rapid development of flat panel displays has allowed users to mount these displays in a variety of locations that were not previously available. Further, the popularity of high definition (HD) television has increased the demand for larger and brighter displays, especially large displays which are capable of producing HD video. The highly competitive field of consumer advertising has also increased the demand for large displays which are positioned outdoors, sometimes within direct sunlight or other high ambient light situations (street lights, building signs, vehicle headlights, and other displays). In order to be effective, outdoor displays must compete with the ambient natural light to provide a clear and bright image to the viewer.


SUMMARY OF THE EXEMPLARY EMBODIMENTS

The exemplary embodiments herein provide a system and method for controlling the luminance of a display based on a combination of metrics. In some embodiments, the luminance is controlled based on the time of day, which is compared with sunrise/sunset data. In other embodiments, the system is controlled based on the time of day (when operating at nighttime) but controlled based on ambient light levels in the daytime. Other embodiments primarily operate based on the ambient light levels but switch to operation based on the time of day when a failure is detected in the ambient light sensor.


Some embodiments operate without the use of data from the ambient light sensor. In these embodiments, sunset and sunrise transition periods are calculated by the system and used to gradually ramp the display brightness up/down during these transition periods. Further embodiments also access local weather information and adjust the display brightness based on the percentage of cloud cover.


The exemplary embodiments herein disclosed are not intended to be exhaustive or to unnecessarily limit the scope of the embodiments. The exemplary embodiments were chosen and described in order to explain the principles so that others skilled in the art may practice the embodiments. Having shown and described exemplary embodiments, those skilled in the art will realize that many variations and modifications may be made to affect the described invention. Many of those variations and modifications will provide the same result and fall within the spirit of the exemplary embodiments. It is the intention, therefore, to limit the embodiments only as indicated by the scope of the claims.





BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding will be obtained from a reading of the following detailed description and the accompanying drawings wherein identical reference characters refer to identical parts and in which:



FIG. 1 provides a block diagram for various electronic components which may be used within an exemplary electronic display assembly.



FIG. 2 provides a logical flow chart for performing a first embodiment of the method which is controlled only based on the display location data.



FIG. 3 provides a logical flow chart for performing a second embodiment of the method which is controlled initially by data from the ambient light sensor but switches to display location data if a failure is observed in the ambient light sensor.



FIG. 4 provides a logical flow chart for performing a third embodiment of the method which is controlled based on the display location data in the nighttime but switches to control based on the ambient light sensor in the daytime.



FIG. 5 provides a logical flow chart for performing a fourth embodiment of the method which is controlled based on the display location data in the nighttime but switches to control based on the ambient light sensor in the daytime unless a failure is detected in the ambient light sensor, at which point the system is controlled only by the display location data.



FIG. 6 provides a graphical representation of a desired display brightness in response to raw ambient light sensor data.



FIG. 7 provides a graphical representation of a desired display brightness in response to raw ambient light sensor data for this type of curve where the low ambient environments require a display set to a higher luminance level.



FIG. 8 provides a logical flowchart for performing an embodiment that uses the AAS technique during sunset/sunrise transition times while using a nighttime/daytime level for the remaining times.



FIG. 9 provides a logical flowchart for performing an embodiment that uses the AAS technique with only a single transition period while using a nighttime/daytime level for the remaining times.



FIG. 10 provides a logical flowchart for performing the advanced embodiment that uses the AAS technique during sunset/sunrise transition times as well as the daytime while factoring in the local weather information.





DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The invention is described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. In the drawings, the size and relative sizes of layers and regions may be exaggerated for clarity.


It will be understood that when an element or layer is referred to as being “on” another element or layer, the element or layer can be directly on another element or layer or intervening elements or layers. In contrast, when an element is referred to as being “directly on” another element or layer, there are no intervening elements or layers present. Like numbers refer to like elements throughout. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.


It will be understood that, although the terms first, second, third, etc., may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer or section from another region, layer or section. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the present invention.


Spatially relative terms, such as “lower”, “upper” and the like, may be used herein for ease of description to describe the relationship of one element or feature to another element(s) or feature(s) as illustrated in the figures. It will be understood that the spatially relative terms are intended to encompass different orientations of the device in use or operation, in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as “lower” relative to other elements or features would then be oriented “upper” relative the other elements or features. Thus, the exemplary term “lower” can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted accordingly.


The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.


Embodiments of the invention are described herein with reference to cross-section illustrations that are schematic illustrations of idealized embodiments (and intermediate structures) of the invention. As such, variations from the shapes of the illustrations as a result, for example, of manufacturing techniques and/or tolerances, are to be expected. Thus, embodiments of the invention should not be construed as limited to the particular shapes of regions illustrated herein but are to include deviations in shapes that result, for example, from manufacturing.


For example, an implanted region illustrated as a rectangle will, typically, have rounded or curved features and/or a gradient of implant concentration at its edges rather than a binary change from implanted to non-implanted region. Likewise, a buried region formed by implantation may result in some implantation in the region between the buried region and the surface through which the implantation takes place. Thus, the regions illustrated in the figures are schematic in nature and their shapes are not intended to illustrate the actual shape of a region of a device and are not intended to limit the scope of the invention.


Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.



FIG. 1 provides a block diagram for various electronic components which may be used within an exemplary electronic display assembly. One or more power modules 21 may be placed in electrical connection with a backplane 29, which could be provided as a printed circuit board which may facilitate electrical communication and/or power between a number of components in the display assembly. A display controlling assembly 20 may also be in electrical connection with the backplane 22. The display controlling assembly 20 preferably includes a number of different components, including but not limited to a video player, electronic storage, and a microprocessor which is programmed to perform any of the logic that is described within this application.


This figure also shows a backlight 23, LCD assembly 24, and a front transparent display panel 25. The backlight 23 may be a CCFL or light emitting diode (LED) backlight. It should be noted that although the setup for an LCD is shown, embodiments can be practiced with any electronic image-producing assembly. Thus any other flat panel display could be used such as plasma, light-emitting polymers, and organic light emitting diode (OLED) displays. When the display type does not include a traditional backlight, then the term “drive backlight” as used herein, can be replaced with “drive display” and the term “backlight level” as used herein, can be replaced with “display level.” A fan assembly 26 is shown for optionally cooling displays which may reach elevated temperatures. One or more temperature sensors 27 may be used to monitor the temperature of the display assembly, and selectively engage fan assembly 26 when cooling is needed. An ambient light sensor 28 may be positioned to measure the amount of ambient light that is contacting the front display panel 25, although this is not required. As described below, some embodiments may use the ambient light sensor 28 in a limited capacity, but a preferred embodiment would operate without the need for the ambient light sensor 28 at all.


A variety of different electrical inputs/outputs are also shown, and all or only a select few of the inputs/outputs may be practiced with any given embodiment. The AC power input 30 delivers the incoming power to the backplane 22. A video signal input 31 can receive video signals from a plurality of different sources. In a preferred embodiment the video signal input 31 would be an HDMI input. Two data interface connections 32 and 33 are also shown. The first data interface connection 32 may be an RS2332 port or an IEEE 802.3 jack which can facilitate user setup and system monitoring. Either form of the connection should allow electrical communication with a personal computer. The second data interface connection 33 may be a network connection such as an Ethernet port, wireless network connection, or a satellite network connection. The second data interface connection 33 preferably allows the display assembly to communicate with the internet, and may also permit a remote user to communicate with the display assembly. The second data interface connection 33 can also provide the video data through a network source. The second data interface connection 33 can also be utilized to transmit display settings, error messages, and various other forms of data to a website for access and control by the user. Optional audio connections 34 may also be provided for connection to internal or external speaker assemblies. It is not required that the data inputs 31, 32, and 33 received their data through a wired connection, as many embodiments may utilize wireless networks or satellite networks to transmit data to the display assembly. The various types of wireless/satellite receivers and transmitters have not been specifically shown due to the large number of variable types and arrangements, but these are understood by a person of ordinary skill in the art.


A backlight sensor 29 is preferably placed within the backlight cavity to measure the amount of luminance being generated within the backlight cavity. Additionally, a display luminance sensor 40 is preferably positioned in front of the display 24 in order to measure the amount of luminance exiting the display 24. Either sensor can be used in a traditional feed-back loop to evaluate the control signals being sent to the power modules 21 and what resulting backlight luminance or display luminance is generated by the display in response. As shown below, ambient light data (either actual measurements or artificial ambient light sensor data, herein “AAS”) may be used to select either the desired display luminance or backlight luminance. Either technique can be used with the various embodiments herein.


Information for monitoring the status of the various display components may be transmitted through either of the two data interface connections 32 and 33, so that the user can be notified when a component may be functioning improperly, about to fail, or has already failed and requires replacement. The information for monitoring the status of the display may include, but is not limited to: power supply status, power supply test results, AC input current, temperature sensors, fan speed, video input status, firmware revision, and light level sensors. Also, the user may adjust settings including, but not limited to: on/off, brightness level, enabling ambient light sensor, various alert settings, IP address, customer defined text/video, display matrix settings, display of image settings via OSD, and various software functions. In some embodiments, these settings can be monitored and altered from either of the two data interface connections 32 and 33.



FIG. 2 provides a logical flow chart for performing a first embodiment of the method which is controlled only based on the display location data. As an initial step in this embodiment, the system preferably determines the geographical location data for the display. This can be performed in a number of ways. First, the physical address of the display may be used to determine the city/state in which the display is located. Second, the physical address of the display can be exchanged for the latitude and longitude coordinates. This technique can be performed by accessing a number of online tools, including but not limited to www.latlong.net. Third, the location of the display can be determined by reading coordinates from a GPS capable smart device which may form a part of the display controlling assembly 20. If the coordinates result in a physical address then this can be converted to the latitude and longitude coordinates, or vice versa by the techniques noted above.


Once the location of the display is determined, the sunset and sunrise times for this location are preferably determined. The timing for performing this step can vary. In some embodiments, this step could be performed only once, with 365 days of data being used for the display throughout the remainder of the display's lifetime. Alternatively, this step could be performed annually, monthly, weekly, or even daily. This step can also be performed in a number of ways. First, when given a physical address, the system can determine the sunrise/sunset times based on this address and store them within the electronic storage on the display controlling assembly 20. Second, when given latitude/longitude coordinates, the system can determine the sunrise/sunset times based on these coordinates and store them within the electronic storage on the display controlling assembly 20. The location data can be converted to sunrise/sunset times by accessing any number of online databases, including but not limited to: www.sunrisesunset.com, www.suncalc.net, and various NOAA online tools. Additionally, the latitude and longitude data can be used to calculate sunrise/sunset times based on the sunrise equation:

cos ωo=−tan ϕ×tan δ where:


ωo is the hour angle at either sunrise (when negative value is taken) or sunset (when positive value is taken);


ϕ is the latitude of the observer on the Earth; and


δ is the sun declination.


It should be noted that the steps of determining geographical location data for the display and determining approximate sunrise/sunset times based on the geographical location data, may be performed before the display is shipped to its actual location. In other embodiments, the display may be installed within its actual location prior to performing these steps.


Once the approximate sunrise/sunset times are determined (and preferably stored at the display), the system would then check to see what the current time is and determine whether it is currently night or day. While the figure reads the logic as “does the current time fall after sunset and before sunrise,” it seems clear that this could also be performed by determining “does the current time fall after sunrise and before sunset” and it makes no difference in any of the subject embodiments. In this first embodiment, if the system determines that it is currently nighttime, the backlight is driven at the nighttime level. Alternatively, if the system determines that it is daytime, the backlight is driven at the daytime level.


The relative daytime level and nighttime level for the backlight can be selected for this embodiment through a simple binary operation where a first luminance value for the backlight is desired during nighttime and a second luminance value for the backlight is desired during daytime. The system may push as much power as necessary to the backlight 23 in order to read the desired luminance value from the backlight sensor 29. The power levels can be adjusted through the feedback coming from the backlight sensor 29 to ensure that the desired luminance level of the backlight 23 is maintained. Alternatively, the desired luminance can be measured based on the level of luminance for the light which is exiting the display 24, measured by the light sensor 40. The sensor 40 can also provide the feedback to the system to ensure that the proper amount of power is being sent to the backlight 23 to ensure adequate luminance levels exiting the display.


The dashed lines on the figure indicate the option of the system returning to determine the approximate sunrise/sunset times, if practicing an embodiment where this data is updated annually, monthly, weekly, or daily.



FIG. 3 provides a logical flow chart for performing a second embodiment of the method which is controlled initially by data from the ambient light sensor 28 but switches to display location data if a failure is observed in the ambient light sensor 28. In this embodiment, the system regularly checks to determine if the ambient light sensor 28 is working properly. This can be checked in a number of ways, including a quick reference to the time of day and the ambient light sensor readings. Thus, if it is 3:00 a.m. in Lincoln, Nebr. in an area without significant proximate artificial light, we should see very low light levels and a very high light level reading would indicate some error or failure in the ambient light sensor 28. Alternatively, if it is 3:00 p.m. in Lincoln, Nebr. in an area where light is not blocked and there is a very low light reading, this could also indicate some error or failure in the ambient light sensor 28. Other signal analysis steps could also be performed where no signal whatsoever would indicate an error or failure or a very high voltage reading could also indicate an error or failure. Failures in the ambient light sensor 28 can also be determined by signal analysis methods which look at the amount of noise and randomness in the sensor data. A measured amount of noise or randomness that is above some threshold level can also be used to indicate a failure in the sensor.


If the ambient light sensor 28 is working properly, it is preferably used to determine the amount of luminance contacting the front display panel 25. Based on this information, the system may determine the desired backlight level based on this data. This step can also be performed in a number of ways. First, a lookup table may be used where a particular reading from the ambient light sensor 28 will correspond with a desired luminance reading from the light sensor 29 in the backlight cavity or light sensor 40 in front of the display 24. Second, an equation or ratio can be used where the desired luminance from the light sensor 29 or light sensor 40 may be calculated based on the data from the ambient light sensor 28. Third, the more simplistic daytime/nighttime settings can be used when the sensor 28 indicates daytime/nighttime and when the sensor 28 indicates a transition period (i.e. dawn/dusk) the display may default to the daytime setting.


If at any point during this operation the system determines that the ambient light sensor 28 is not working properly, the system preferably shifts to the display location data method described above.



FIG. 4 provides a logical flow chart for performing a third embodiment of the method which is controlled based on the display location data in the nighttime but switches to control based on the ambient light sensor 28 in the daytime. This is a type of hybrid approach where the backlight is driven at a desired (preferably constant) nighttime level anytime the display is between sunset and sunrise while adjusting to the various levels of ambient light when operating during the daytime or other transition periods (i.e. dawn/dusk).



FIG. 5 provides a logical flow chart for performing a fourth embodiment of the method which is controlled based on the display location data in the nighttime but switches to control based on the ambient light sensor 28 in the daytime unless a failure is detected in the ambient light sensor 28, at which point the system is controlled only by the display location data. This embodiment is similar to the embodiment shown and described for FIG. 4 above, with the additional check to see if the ambient light sensor 28 is functioning properly. If not, then the backlight may be driven to a desired daytime level (preferably constant) based on the time of day, and will not consider the readings of the ambient light sensor.


It should be noted that when driving the backlight based on the location data and/or time of day, the system does not have to choose one luminance for daytime and one luminance for nighttime (although some embodiments use this method). The system can also use the time of day to slightly adjust the amount of luminance from the backlight. Thus, while 7:15 a.m. and 1:30 p.m. are each occurring after sunrise and before sunset, the system does not have to drive the backlight at the same luminance for each time. Thus, as used herein, the terms “nighttime level” and “daytime level” can represent luminance values that are also obtained through a lookup table (based on time of day) or an equation/calculation (based on time of day). In this manner, the system could drive the daytime level at 1:30 p.m. higher than the daytime level at 7:15 a.m. given the assumption that there will be more ambient light present during the afternoon than in the early morning (or late evening for that matter).



FIG. 6 provides a graphical representation of a desired display brightness in response to raw ambient light sensor data. This is an example, and not required for any specific embodiment. It has been found, that the human eye is more sensitive to luminance variations in low ambient light environments as compared to high ambient light environments. Therefore, some embodiments of the invention may use a more aggressive response curve at the lower ambient light environments. FIG. 7 provides a graphical representation of a desired display brightness in response to raw ambient light sensor data for this type of curve where the low ambient environments require a display set to a higher luminance level. Either curve (FIG. 6 or FIG. 7), or another curve, could be used to create the look-up table or perform an equation to determine the desired display brightness for each ambient environment.


It should be noted that while FIGS. 6 and 7 are shown in terms of display brightness, the exemplary embodiments herein can be based on either display brightness or backlight brightness, depending on which type(s) of electronic display is being used and the sensors used to measure the luminance output (if used). It should also be noted that the values for FIGS. 6 and 7 are based on actual raw data from ambient light sensors, but actual data is not necessarily used when using some of the exemplary embodiments herein. Thus, the calculation of artificial ambient sensor (AAS) values is described below, and these AAS values can be used with the relationships shown in FIGS. 6 and 7 to determine the desired display brightness. In other words, using the relationship shown in FIGS. 6 and 7 does not require the use of actual ambient light sensor data, as it can be used when working with AAS data as well. While based on the performance of real ambient sensors with real data, it is not required that actual raw data from ambient light sensors is used for any of the embodiments herein.


It should also be noted that changes from “nighttime level” backlight luminance to “daytime level” backlight luminance should not happen in a drastic manner, where an abrupt change or flicker in the display could be observed by a viewer. It is preferable that the changes in backlight luminance occur in a ramp-wise fashion, where the backlight does not suddenly shift to a new luminance, but instead gradually changes to a new luminance over a (shorter or longer) period of time that would make it less noticeable to a viewer.


It has been discovered, that anomalies in the display environment can sometimes create variations in the ambient light sensor data that can cause the display to change brightness levels drastically, even though the surrounding environment has not changed quite as drastically. For example, the ambient light sensor may be positioned within a shadow while the rest of the display is not. This select-shadowing can be caused by a number of obstructions, including but not limited to light posts, trees, passing vehicles, and/or construction equipment. Other anomalies can create variability in the ambient light sensor data, including variations in: the response of each different sensor, the response of the sensor over temperature changes, variations in the positioning of the light sensor in each display, and variations in the typical ambient environment of the display over time.


In some embodiments, as mentioned above, the system can function without the use of data from the ambient light sensor. This however does typically limit some of the functionality of the system and its benefits, specifically power saving benefits, and can sometimes produce drastic changes in the display luminance. However, the following embodiments provide a system and method for controlling the luminance of an electronic display by producing artificial ambient light sensor data (AAS).


In one embodiment, generating artificial ambient sensor data involves defining the following parameters:


(1) Desired Nighttime Level—the desired display brightness at nighttime.


(2) Desired Daytime Level—the desired display brightness during the daytime.


(3) High Ambient Reading (HA)—the approximate raw data received by the ambient light sensor when experiencing the highest ambient light levels for the display environment.


(4) GPS coordinates for the display location or the address/City/State.


(5) Sunrise transition period (tsr)—the amount of time (usually measured in seconds) to transition from a nighttime ambient light sensor reading to a daytime ambient light sensor reading.


(6) Sunset transition period (tss)—the amount of time (usually measured in seconds) to transition from a daytime ambient light sensor reading to a nighttime ambient light sensor reading.


For this embodiment, during the sunrise transition period, the artificial ambient sensor (AAS) data can be calculated in the following manner, where ti provides the time in transition (i.e. ti varies between zero and tsr).

AAS for sunrise=(ti*HA)/tsr.


Similarly, the AAS for sunset can be calculated in the following manner, where ti provides the time in transition (i.e. ti varies between zero and tss).

AAS for sunset=HA−(ti*HA)/tss.


Once AAS for either transition period has been calculated, the desired backlight level can be determined from any of the ambient light vs. display brightness relationships described above.



FIG. 8 provides a logical flowchart for performing an embodiment that uses the AAS technique during sunset/sunrise transition times while using a nighttime/daytime level for the remaining times.


In some embodiments, the sunset transition period and the sunrise transition period may be similar or substantially the same. In this case, it may not be necessary to have two transition periods. Instead, one transition period may be used. FIG. 9 provides a logical flowchart for performing an embodiment that uses the AAS technique with only a single transition period while using a nighttime/daytime level for the remaining times.


In an advanced embodiment, the system and method can also utilize local weather information to further tailor the display brightness, without requiring actual data from the ambient light sensor. The local weather information can be obtained from available web APIs or other online weather information which may be accessed at a predetermined time interval (ex. every 15 minutes). Here, a weather factor (WF) is used where:


If it is daytime or any transition period: WF=4*Ci, where Ci=Clearness percentage with a higher percentage representing a clear sky and a lower percentage representing a large amount of cloud cover. Of course the inversion could be used, where a higher percentage represents more cloud cover and a lower percentage represents less cloud cover.


For this embodiment, during the sunrise transition period, the artificial ambient sensor (AAS) data can be calculated in the following manner.

AAS for sunrise=(ti*(HA*WF))/tsr.


Similarly, the AAS for sunset can be calculated in the following manner.

AAS for sunset=(HA*WF)−(ti*(HA*WF))/tss.


If it is daytime, AAS=HA*WF.


If it is nighttime, AAS=0.


Once AAS for either transition period or the daytime has been calculated, the desired backlight level can be determined from any of the ambient light vs. display brightness relationships described above.



FIG. 10 provides a logical flowchart for performing the advanced embodiment that uses the AAS technique during sunset/sunrise transition times as well as the daytime while factoring in the local weather information.


For example, when during the daytime (i.e. not within either transition period or nighttime) and where it is overcast and raining, the relevant calculations would be:


Ci=10% clearness percentage


HA=500


Weather factor=4*0.10=0.40


AAS=500*0.40=300


Referencing FIG. 6 with ambient sensor input of 300, Desired Display Luminance˜=1040 nits.


Referencing FIG. 7 with ambient sensor input of 300, Desired Display Luminance˜=1965 nits.


Note that without correction for local weather conditions, the daytime value would likely be 500, which would mean the Desired Display Luminance=2500 nits. From here we see significant power savings due to the overcast skies.


For the same example, if the display is halfway through a sunrise or sunset transition, the calculated light sensor value and corresponding desired brightness would be:


tsr=1800 seconds


ti=900 seconds


HA=500


Weather factor=4*0.10=0.40


AAS=(900*500*0.40)/1800=100


Referencing FIG. 6 with ambient light sensor input of 100, Desired Display Luminance˜=465 nits*


Referencing FIG. 7 with ambient sensor input of 100 Desired Display Luminance˜=1030 nits.


Without correction for local conditions, the AAS value would be 250 which corresponds with a Desired Display Luminance˜=850 nits.


Having shown and described preferred embodiments, those skilled in the art will realize that many variations and modifications may be made to affect the described embodiments and still be within the scope of the claims. Thus, many of the elements indicated above may be altered or replaced by different elements which will provide the same result and fall within the spirit of the claimed embodiments. It is the intention, therefore, to limit the invention only as indicated by the scope of the claims.

Claims
  • 1. A method for controlling the luminance of an electronic display having a backlight, comprising the steps of: determining the sunset and sunrise times for the present day;determining whether the present time is between a sunrise transition period, daytime, a sunset transition period, or nighttime;driving the backlight based on whether the present time is during the sunrise transition period, daytime, the sunset transition period, or nighttime such that the backlight is driven at a daytime level if the present time is during daytime and the backlight is driven at a nighttime level that is less than the daytime level if the present time is during nighttime; andremotely monitoring or adjusting a brightness of the electronic display independent of normal operational input if the present time is during the sunrise transition period or the sunset transition period;wherein the backlight is adapted to be on for daytime use and nighttime use of the electronic display; andwherein the electronic display is directly backlit by the backlight.
  • 2. The method of claim 1 further comprising the steps of: gradually increasing the backlight level during the sunrise transition period when transitioning from the nighttime level to the daytime level; andgradually decreasing the backlight level during the sunset transition period when transitioning from the daytime level to the nighttime level.
  • 3. The method of claim 2 wherein: the step of driving the backlight at the daytime level is performed by driving the backlight at a predetermined constant daytime level, without utilizing any input from an ambient light sensor.
  • 4. The method of claim 2 wherein: the step of driving the backlight at the daytime level is performed by calculating artificial ambient sensor (AAS) data for the present time and driving the backlight based on the AAS data;wherein said AAS data, depending on time of day, takes into account: a desired display brightness level at nighttime; a desired display brightness level during daytime; data that approximates ambient light level for a display environment; the sunrise transition period; and the sunset transition period.
  • 5. The method of claim 2 wherein: the step of driving the backlight at the daytime level is performed by reading data from an ambient light sensor and selecting a desired backlight level based on the data from the ambient light sensor.
  • 6. The method of claim 1 further comprising the steps of: determining whether the present time is during the sunset transition period or the sunrise transition period; andcalculating AAS data if during the sunset transition period or the sunrise transition period; anddriving the backlight based on the AAS data if during the sunset transition period or the sunrise transition period;wherein said AAS data, depending on time of day, takes into account: a desired display brightness level at nighttime; a desired display brightness level during daytime; data that approximates ambient light level for a display environment; the sunrise transition period; and the sunset transition period.
  • 7. The method of claim 1 further comprising the steps of: determining local weather information;calculating AAS data based on the local weather information; anddriving the backlight based on the AAS data;wherein said AAS data, depending on time of day, further takes into account: a desired display brightness level at nighttime; a desired display brightness level during daytime; data that approximates ambient light level for a display environment; the sunrise transition period; and the sunset transition period.
  • 8. The method of claim 1 wherein: the step of driving the backlight is performed without any actual input from an ambient light sensor.
  • 9. The method of claim 1 wherein the step of remotely monitoring or adjusting brightness of the electronic display allows a user to be notified when a component may be functioning improperly, about to fail, or has already failed and requires replacement.
  • 10. The method of claim 1 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises monitoring power supply status, power supply test results, AC input current, temperature sensors, fan speed, video input status, firmware revision, or light level sensor status.
  • 11. The method of claim 1 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises adjusting on/off, brightness level, ambient light sensor status, alert settings, IP address, customer defined text/video, display matrix settings, display of image settings via on-screen display (OSD), or software functions.
  • 12. The method of claim 1 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises monitoring or adjusting the status of the backlight.
  • 13. A method for controlling the luminance of an electronic display having a backlight, comprising the steps of: determining the sunset and sunrise times for the present day, including a sunset transition period and a sunrise transition period;determining if the present time is during the sunrise transition period, daytime, the sunset transition period, or nighttime;calculating AAS data for sunrise and driving the backlight based on the AAS data if the present time is during the sunrise transition period;driving the backlight at a daytime level if the present time is daytime,calculating AAS data for sunset and driving the backlight based on the AAS data if the present time is during the sunset transition period;driving the backlight at a nighttime level if the present time is nighttime; andremotely monitoring or adjusting a brightness of the electronic display independent of normal operational input if the present time is during the sunrise transition period or the sunset transition period;wherein the electronic display is directly backlit by the backlight; andwherein said AAS data, depending on time of day, takes into account: a desired display brightness level at nighttime; a desired display brightness level during daytime; data that approximates ambient light level for a display environment; the sunrise transition period; and the sunset transition period.
  • 14. The method of claim 13 further comprising the step of: determining local weather information;wherein the step of calculating the AAS data is performed based on the determined local weather information.
  • 15. The method of claim 14 wherein: the step of determining the local weather information is performed by calculating a percentage of cloud cover.
  • 16. The method of claim 13 wherein the step of driving the backlight based on AAS data is performed by: determining a desired display luminance based on ambient light sensor readings; anddriving the backlight to obtain the desired display luminance.
  • 17. The method of claim 13 wherein the step of driving the backlight based on AAS data is performed by: retrieving a desired display luminance from a table of desired display luminance values based on ambient light sensor readings, by matching the AAS data to an ambient light sensor reading and corresponding desired display luminance; anddriving the backlight to obtain the desired display luminance.
  • 18. The method of claim 13 wherein the step of driving the backlight based on AAS data is performed by: calculating a desired backlight luminance based on a mathematical relationship between ambient light sensor readings and backlight luminance where the AAS data is used as the ambient light sensor reading; anddriving the backlight to the desired backlight luminance.
  • 19. The method of claim 13 wherein the step of driving the backlight based on AAS data is performed by: using a table of desired backlight luminance values based on ambient light sensor readings where the AAS data is used as the ambient light sensor readings to determine a desired backlight luminance value; anddriving the backlight to the desired backlight luminance value.
  • 20. The method of claim 13 wherein the step of remotely monitoring or adjusting the brightness of the electronic display allows a user to be notified when a component may be functioning improperly, about to fail, or has already failed and requires replacement.
  • 21. The method of claim 13 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises monitoring power supply status, power supply test results, AC input current, temperature sensors, fan speed, video input status, firmware revision, or light level sensor status.
  • 22. The method of claim 13 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises adjusting on/off, brightness level, ambient light sensor status, alert settings, IP address, customer defined text/video, display matrix settings, display of image settings via on-screen display (OSD), or software functions.
  • 23. The method of claim 13 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises monitoring or adjusting the status of the backlight.
  • 24. A method for controlling the luminance of an electronic display having a backlight, comprising the steps of: determining present location data for the electronic display through a GPS device;based on the location data from the GPS device, determining if a present time is during a sunset transition period or a sunrise transition period;driving the luminance of the electronic display based on the location data from the GPS device without using any data from an ambient light sensor; andremotely monitoring or adjusting a brightness of the electronic display independent of normal operational input if the present time is during the sunrise transition period or the sunset transition period;wherein the electronic display is directly backlit by the backlight.
  • 25. The method of claim 24 wherein: the step of determining if the present time is during the sunset transition period or the sunrise transition period includes calculating the sunrise and sunset times based on the location data from the GPS device.
  • 26. The method of claim 25 wherein: the step of calculating the sunrise and sunset times is performed based on the longitude and latitude coordinates of the electronic display.
  • 27. The method of claim 26 wherein: the step of calculating the sunrise and sunset times is performed by calculating the sunrise equation.
  • 28. The method of claim 24 wherein the step of remotely monitoring or adjusting the brightness of the electronic display allows a user to be notified when a component may be functioning improperly, about to fail, or has already failed and requires replacement.
  • 29. The method of claim 24 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises monitoring power supply status, power supply test results, AC input current, temperature sensors, fan speed, video input status, firmware revision, or light level sensor status.
  • 30. The method of claim 24 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises adjusting on/off, brightness level, ambient light sensor status, alert settings, IP address, customer defined text/video, display matrix settings, display of image settings via on-screen display (OSD), or software functions.
  • 31. The method of claim 24 wherein the step of remotely monitoring or adjusting the brightness of the electronic display comprises monitoring or adjusting the status of the backlight.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Application No. 62/161,673 filed on May 14, 2015 and is herein incorporated by reference in its entirety.

US Referenced Citations (258)
Number Name Date Kind
4093355 Kaplit et al. Jun 1978 A
4593978 Mourey et al. Jun 1986 A
4634225 Haim et al. Jan 1987 A
5029982 Nash Jul 1991 A
5086314 Aoki et al. Feb 1992 A
5088806 McCartney et al. Feb 1992 A
5162785 Fagard Nov 1992 A
5247374 Tereda Sep 1993 A
5559614 Urbish et al. Sep 1996 A
5661374 Cassidy et al. Aug 1997 A
5748269 Harris et al. May 1998 A
5767489 Ferrier Jun 1998 A
5783909 Hochstein Jul 1998 A
5786801 Ichise Jul 1998 A
5808418 Pitman Sep 1998 A
5818010 McCann Oct 1998 A
5952992 Helms Sep 1999 A
5991153 Heady et al. Nov 1999 A
6089751 Conover et al. Jul 2000 A
6144359 Grave Nov 2000 A
6153985 Grossman Nov 2000 A
6157143 Bigio Dec 2000 A
6157432 Helbing Dec 2000 A
6181070 Dunn et al. Jan 2001 B1
6191839 Briley Feb 2001 B1
6259492 Imoto Jul 2001 B1
6292228 Cho Sep 2001 B1
6297859 George Oct 2001 B1
6380853 Long et al. Apr 2002 B1
6388388 Weindorf et al. May 2002 B1
6400101 Biebl et al. Jun 2002 B1
6417900 Shin et al. Jul 2002 B1
6496236 Cole et al. Dec 2002 B1
6509911 Shimotono Jan 2003 B1
6535266 Nemeth et al. Mar 2003 B1
6556258 Yoshida et al. Apr 2003 B1
6628355 Takahara Sep 2003 B1
6712046 Nakamichi Mar 2004 B2
6753661 Muthu et al. Jun 2004 B2
6753842 Williams et al. Jun 2004 B1
6762741 Weindorf Jul 2004 B2
6798341 Eckel et al. Sep 2004 B1
6809718 Wei et al. Oct 2004 B2
6812851 Dukach et al. Nov 2004 B1
6813375 Armato, III et al. Nov 2004 B2
6839104 Taniguchi et al. Jan 2005 B2
6850209 Mankins et al. Feb 2005 B2
6885412 Ohinishi et al. Apr 2005 B2
6886942 Okada et al. May 2005 B2
6891135 Pala et al. May 2005 B2
6943768 Cavanaugh et al. Sep 2005 B2
6982686 Miyachi et al. Jan 2006 B2
6996460 Krahnstoever et al. Feb 2006 B1
7015470 Faytlin et al. Mar 2006 B2
7038186 De Brabander et al. May 2006 B2
7064733 Cok et al. Jun 2006 B2
7083285 Hsu et al. Aug 2006 B2
7136076 Evanicky et al. Nov 2006 B2
7174029 Agostinelli et al. Feb 2007 B2
7176640 Tagawa Feb 2007 B2
7236154 Kerr et al. Jun 2007 B1
7307614 Vinn Dec 2007 B2
7324080 Hu et al. Jan 2008 B1
7330002 Joung Feb 2008 B2
7354159 Nakamura et al. Apr 2008 B2
7474294 Lee Jan 2009 B2
7480042 Phillips et al. Jan 2009 B1
7518600 Lee Apr 2009 B2
7595785 Jang Sep 2009 B2
7639220 Yoshida et al. Dec 2009 B2
7659676 Hwang Feb 2010 B2
7692621 Song Apr 2010 B2
7724247 Yamazaki et al. May 2010 B2
7795574 Kennedy et al. Sep 2010 B2
7795821 Jun Sep 2010 B2
7800706 Kim et al. Sep 2010 B2
7804477 Sawada et al. Sep 2010 B2
7982706 Ichikawa et al. Jul 2011 B2
8087787 Medin Jan 2012 B2
8111371 Suminoe et al. Feb 2012 B2
8125163 Dunn et al. Feb 2012 B2
8144110 Huang Mar 2012 B2
8175841 Ooghe May 2012 B2
8194031 Yao et al. Jun 2012 B2
8248203 Hanwright et al. Aug 2012 B2
8352758 Atkins et al. Jan 2013 B2
8508155 Schuch Aug 2013 B2
8569910 Dunn et al. Oct 2013 B2
8605121 Chu et al. Dec 2013 B2
8700226 Schuch et al. Apr 2014 B2
8797372 Liu Aug 2014 B2
8810501 Budzelaar et al. Aug 2014 B2
8823630 Roberts et al. Sep 2014 B2
8829815 Dunn et al. Sep 2014 B2
8895836 Amin et al. Nov 2014 B2
8901825 Reed Dec 2014 B2
8982013 Sako Mar 2015 B2
8983385 Macholz Mar 2015 B2
8988011 Dunn Mar 2015 B2
9030129 Dunn et al. May 2015 B2
9167655 Dunn et al. Oct 2015 B2
9286020 Dunn et al. Mar 2016 B2
9448569 Schuch et al. Sep 2016 B2
9451060 Bowers et al. Sep 2016 B1
9516485 Bowers et al. Dec 2016 B1
9536325 Bray et al. Jan 2017 B2
9622392 Bowers et al. Apr 2017 B1
9867253 Dunn et al. Jan 2018 B2
9924583 Schuch et al. Mar 2018 B2
20020020090 Sanders Feb 2002 A1
20020050974 Rai et al. May 2002 A1
20020101553 Enomoto et al. Aug 2002 A1
20020112026 Fridman et al. Aug 2002 A1
20020126248 Yoshida Sep 2002 A1
20020154138 Wada et al. Oct 2002 A1
20020164962 Mankins et al. Nov 2002 A1
20020167637 Burke et al. Nov 2002 A1
20020190972 Ven de Van Dec 2002 A1
20030007109 Park Jan 2003 A1
20030088832 Agostinelli et al. May 2003 A1
20030122810 Tsirkel et al. Jul 2003 A1
20030204342 Law et al. Oct 2003 A1
20030214242 Berg-johansen Nov 2003 A1
20030230991 Muthu Dec 2003 A1
20040032382 Cok et al. Feb 2004 A1
20040036697 Kim et al. Feb 2004 A1
20040036834 Ohnishi et al. Feb 2004 A1
20040113044 Ishiguchi Jun 2004 A1
20040165139 Anderson et al. Aug 2004 A1
20040201547 Takayama Oct 2004 A1
20040243940 Lee et al. Dec 2004 A1
20050012734 Johnson et al. Jan 2005 A1
20050043907 Eckel et al. Feb 2005 A1
20050049729 Culbert et al. Mar 2005 A1
20050073518 Bontempi Apr 2005 A1
20050094391 Campbell et al. May 2005 A1
20050127796 Olesen et al. Jun 2005 A1
20050140640 Oh et al. Jun 2005 A1
20050184983 Brabander et al. Aug 2005 A1
20050231457 Yamamoto et al. Oct 2005 A1
20050242741 Shiota et al. Nov 2005 A1
20060007107 Ferguson Jan 2006 A1
20060022616 Furukawa Feb 2006 A1
20060038511 Tagawa Feb 2006 A1
20060049533 Kamoshita Mar 2006 A1
20060087521 Chu et al. Apr 2006 A1
20060125773 Ichikawa et al. Jun 2006 A1
20060130501 Singh et al. Jun 2006 A1
20060197474 Olsen Sep 2006 A1
20060197735 Vuong Sep 2006 A1
20060214904 Kimura et al. Sep 2006 A1
20060215044 Masuda et al. Sep 2006 A1
20060220571 Howell et al. Oct 2006 A1
20060238531 Wang Oct 2006 A1
20060244702 Chu et al. Nov 2006 A1
20070013828 Cho et al. Jan 2007 A1
20070047808 Choe et al. Mar 2007 A1
20070152949 Sakai Jul 2007 A1
20070171647 Artwohl et al. Jul 2007 A1
20070173297 Cho Jul 2007 A1
20070200513 Ha et al. Aug 2007 A1
20070222730 Kao et al. Sep 2007 A1
20070230167 McMahon et al. Oct 2007 A1
20070242153 Tang et al. Oct 2007 A1
20070247594 Tanaka Oct 2007 A1
20070268234 Wakabayashi Nov 2007 A1
20070268241 Nitta et al. Nov 2007 A1
20070273624 Geelen Nov 2007 A1
20070279369 Yao et al. Dec 2007 A1
20070291198 Shen Dec 2007 A1
20070297163 Kim et al. Dec 2007 A1
20070297172 Furukawa et al. Dec 2007 A1
20080019147 Erchak et al. Jan 2008 A1
20080055297 Park Mar 2008 A1
20080074382 Lee et al. Mar 2008 A1
20080078921 Yang et al. Apr 2008 A1
20080084166 Tsai Apr 2008 A1
20080111958 Kleverman et al. May 2008 A1
20080136770 Peker et al. Jun 2008 A1
20080143187 Hoekstra et al. Jun 2008 A1
20080151082 Chan Jun 2008 A1
20080170031 Kuo Jul 2008 A1
20080176345 Yu et al. Jul 2008 A1
20080185976 Dickey et al. Aug 2008 A1
20080204375 Shin et al. Aug 2008 A1
20080218501 Diamond Sep 2008 A1
20080246871 Kupper et al. Oct 2008 A1
20080266554 Sekine et al. Oct 2008 A1
20080278099 Bergfors et al. Nov 2008 A1
20080278100 Hwang Nov 2008 A1
20080303918 Keithley Dec 2008 A1
20090009997 Sanfilippo et al. Jan 2009 A1
20090033612 Roberts et al. Feb 2009 A1
20090079416 Vinden et al. Mar 2009 A1
20090085859 Song Apr 2009 A1
20090091634 Kennedy et al. Apr 2009 A1
20090104989 Williams et al. Apr 2009 A1
20090135167 Sakai et al. May 2009 A1
20090152445 Gardner, Jr. Jun 2009 A1
20090278766 Sake et al. Nov 2009 A1
20090284457 Botzas et al. Nov 2009 A1
20090289968 Yoshida Nov 2009 A1
20100039366 Hardy Feb 2010 A1
20100039440 Tanaka et al. Feb 2010 A1
20100060861 Medin Mar 2010 A1
20100177750 Essinger et al. Jul 2010 A1
20100194725 Yoshida et al. Aug 2010 A1
20100231602 Huang Sep 2010 A1
20100253660 Hashimoto Oct 2010 A1
20110032285 Yao et al. Feb 2011 A1
20110050738 Fujioka et al. Mar 2011 A1
20110058326 Idems et al. Mar 2011 A1
20110074737 Hsieh Mar 2011 A1
20110074803 Kerofsky Mar 2011 A1
20110102630 Rukes May 2011 A1
20110163691 Dunn Jul 2011 A1
20110175872 Chuang et al. Jul 2011 A1
20110193872 Biernath et al. Aug 2011 A1
20110231676 Atkins et al. Sep 2011 A1
20110260534 Rozman et al. Oct 2011 A1
20110279426 Imamura et al. Nov 2011 A1
20110283199 Schuch Nov 2011 A1
20120075362 Ichioka et al. Mar 2012 A1
20120081279 Greenebaum et al. Apr 2012 A1
20120176420 Liu Jul 2012 A1
20120182278 Ballestad Jul 2012 A1
20120212520 Matsui et al. Aug 2012 A1
20120268436 Chang Oct 2012 A1
20120269382 Kiyohara et al. Oct 2012 A1
20120284547 Culbert et al. Nov 2012 A1
20130027370 Dunn et al. Jan 2013 A1
20130098425 Amin et al. Apr 2013 A1
20130113973 Miao May 2013 A1
20130158730 Yasuda et al. Jun 2013 A1
20130278868 Dunn et al. Oct 2013 A1
20140002747 Macholz Jan 2014 A1
20140132796 Prentice et al. May 2014 A1
20140139116 Reed May 2014 A1
20140204452 Branson Jul 2014 A1
20140232709 Dunn et al. Aug 2014 A1
20140365965 Bray et al. Dec 2014 A1
20150062892 Krames et al. Mar 2015 A1
20150070337 Bell et al. Mar 2015 A1
20150346525 Wolf et al. Dec 2015 A1
20150348460 Cox et al. Dec 2015 A1
20160037606 Dunn et al. Feb 2016 A1
20160198545 Dunn et al. Jul 2016 A1
20160334811 Marten Nov 2016 A1
20160338181 Schuch et al. Nov 2016 A1
20160358530 Schuch et al. Dec 2016 A1
20160358538 Schuch et al. Dec 2016 A1
20170111486 Bowers et al. Apr 2017 A1
20170111520 Bowers et al. Apr 2017 A1
20170168295 Iwami Jun 2017 A1
20180012565 Dunn Jan 2018 A1
20180040297 Dunn et al. Feb 2018 A1
20180132327 Dunn et al. May 2018 A1
20180206316 Schuch et al. Jul 2018 A1
Foreign Referenced Citations (51)
Number Date Country
2016203550 Mar 2018 AU
2754371 Nov 2017 CA
0313331 Feb 1994 EP
2299723 Mar 2011 EP
2401738 Jan 2012 EP
2577389 Apr 2013 EP
2769376 Aug 2014 EP
3295452 Mar 2018 EP
2401738 May 2018 EP
3338273 Jun 2018 EP
2369730 May 2002 GB
03153212 Jul 1991 JP
5-18767 Jan 1993 JP
8193727 Jul 1996 JP
8-338981 Dec 1996 JP
11160727 Jun 1999 JP
2000122575 Apr 2000 JP
2004325629 Nov 2004 JP
2005265922 Sep 2005 JP
2005-148490 Dec 2005 JP
2005-338266 Dec 2005 JP
2006145890 Jun 2006 JP
2006318733 Nov 2006 JP
2007003638 Jan 2007 JP
2007322718 Dec 2007 JP
200803481 Feb 2008 JP
2008-83290 Apr 2008 JP
2008122695 May 2008 JP
2009031622 Feb 2009 JP
2010-181487 Aug 2010 JP
2010282109 Dec 2010 JP
2011-59543 Mar 2011 JP
2018-523148 Aug 2018 JP
2018-0525650 Sep 2018 JP
10-2006-0016469 Feb 2006 KR
100768584 Oct 2007 KR
1020080000144 Jan 2008 KR
1020080013592 Feb 2008 KR
1020080086245 Sep 2008 KR
10-2011-0125249 Nov 2011 KR
10-1759265 Jul 2017 KR
2008050402 May 2008 WO
2010141739 Dec 2010 WO
2011052331 May 2011 WO
2011130461 Oct 2011 WO
2011150078 Dec 2011 WO
2013044245 Mar 2013 WO
2016183576 Nov 2016 WO
2017031237 Feb 2017 WO
WO2017210317 Dec 2017 WO
2018009917 Jan 2018 WO
Non-Patent Literature Citations (4)
Entry
Zeef, Hubing, EMC analysis of 18′ LCD Monitor, Aug. 2000, 1 page.
Kunkely, H. et al., Photochemistry and Beer, Journal of Chemical Education, Jan. 1982, pp. 25-27, vol. 59, No. 1.
Novitsky, T. et al., Design How-To, Driving LEDs versus CCFLs for LCD backlighting, EE Times, Nov. 12, 2007, 6 pages, AspenCore.
Lee, X., What is Gamma Correcton in Images and Videos?, http://xahlee.info/img/what_is_gamma_correction.html, Feb. 24, 2010, 1 page.
Related Publications (1)
Number Date Country
20160338182 A1 Nov 2016 US
Provisional Applications (1)
Number Date Country
62161673 May 2015 US