Abstract:
A system and method for systemically addressing failures in electronic displays without user interaction comprises an electronic display connected to a timing and control board, connected to a system control board having a network interface component with a power button. A video player is connected to the system control board and has a video player power button. The system control board may simulate pushing the power button, the video power button, and/or disrupting the power supply to the video player if the video player is not communicating.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application claims the benefit of U.S. Provisional Application No. 62/216,470, filed Sep. 10, 2015, the disclosure of which is incorporated herein by reference. 
     
    
     TECHNICAL FIELD 
       [0002]    Embodiments generally relate to electronic displays typically used for advertising, information, and point of sale applications. 
       BACKGROUND OF THE ART 
       [0003]    Electronic displays are now being used in indoor, outdoor, and semi-outdoor environments for advertising, information, as well as point of sale applications. Generally speaking, once installed, it is desirable to ensure operation throughout the life of the device. Downtime can be costly in that advertising revenue and opportunities can be lost, information will not be effectively transmitted to the public, and customers cannot view the purchase options in a point of sale application. 
       SUMMARY OF THE EXEMPLARY EMBODIMENTS 
       [0004]    The exemplary embodiments herein provide a system and method for monitoring one or more remote electronic displays for possible failures, and providing system logic so that failures can be addressed immediately by the system, without requiring any user intervention. The system can monitor a number of system attributes such as heartbeat signals, status messages, LED light signals, video/image frame data, and network communications, while making near instantaneous changes in operation of the device in order to reduce or eliminate downtime of the displays. 
         [0005]    The foregoing and other features and advantages of the present invention will be apparent from the following more detailed description of the particular embodiments, as illustrated in the accompanying drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0006]    A better understanding of an exemplary embodiment 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: 
           [0007]      FIG. 1  is a simplified bock diagram of an exemplary embodiment of the overall system architecture. 
           [0008]      FIG. 1A  is a simplified block diagram of another exemplary embodiment of the overall system architecture. 
           [0009]      FIG. 2  is a logical flowchart for operating a first embodiment of the system. 
           [0010]      FIG. 3  is a logical flowchart for operating a second embodiment of the system. 
           [0011]      FIG. 4  is a logical flowchart for operating a third embodiment of the system. 
           [0012]      FIG. 5  is a logical flowchart for operating a fourth embodiment of the system. 
           [0013]      FIG. 6  is a logical flowchart for operating a fifth embodiment of the system. 
           [0014]      FIG. 7  is a logical flowchart for operating a sixth embodiment of the system. 
           [0015]      FIG. 8  is a logical flowchart for operating a seventh embodiment of the system. 
           [0016]      FIG. 9  is a logical flowchart for operating an eighth embodiment of the system. 
       
    
    
     DETAILED DESCRIPTION 
       [0017]    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. 
         [0018]    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. 
         [0019]    Embodiments of the invention are described herein with reference to 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. 
         [0020]    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. 
         [0021]    Initially it should be noted that one of ordinary skill in the art understands that electronic displays as described herein are capable of displaying both still images as well as videos. Thus, it should be recognized that the terms ‘image’ and ‘video’ may be used interchangeably herein. Further, one having an ordinary level of skill in the arts will also understand that the electrical connections described herein may be wired or wireless. 
         [0022]      FIG. 1  is a simplified bock diagram of an exemplary embodiment of the overall system architecture. A system control board  101  preferably contains at least a processor  50 , electronic storage  60 , and a network interface component  70  (which preferably includes a power button  75 ). In exemplary embodiments of the present invention, the power button  75  is electrically connected to the system control board  101  such that the system control board  101  may simulate the user physically pressing the power button  75  as will be explained in greater detail herein. For example, but without limitation, the network interface component  70  may be electrically connected to the power button  75  via the power control header on the system control board  101 . Similarly, the system control board  101  may be electrically connected to a power supply for the display assembly  200   a  such that the system control board  101  may simulate the user physically removing the power supply (i.e., unplugging) and reattaching the power supply (i.e., plugging back in). 
         [0023]    A timing and control board (TCON)  102  is preferably in electrical connection with the system control board  101  as well as the electronic display  30 . A primary video player  103   a  is also preferably in electrical connection with the system control board  101 . An optional secondary video player  103   b  may also be in electrical connection with the system control board  101 . Each video player preferably includes a power button  104  and a power LED  105  (labeled  104   a,    105   a,    104   b,  and  105   b,  respectively). Similar to the power button  75 , the network interface component  70  may be electrically connected to the power button  104  and the power LED  105  as well as the power supply source to the video players  103   a  and  103   b  by way of the system control board  101  such that the system may simulate physically pressing the power button  104  as well as physically removing the power supply to the video players  103  and reattaching it. 
         [0024]    A network operations center device  200  preferably contains at least a processor  51 , electronic storage  61 , and a network interface component  71  which communicates with the network interface component  70  on the display assembly  200   a.  Two other display assemblies  200   b  and  200   c  are shown in electrical connection with the network operations center device  200 , and each would preferably have the same components as shown and described for the display assembly  200   a,  but this is not required. In some embodiments however, there could be even more than three display assemblies in electrical connection with the network operations center device. 
         [0025]      FIG. 1A  is a simplified block diagram of another exemplary embodiment of the overall system architecture. In this embodiment the display assembly  200   d  may be similar to that show in  FIG. 1 , but be comprised of a first display  30   a  and a second display  30   b.  The first display  30   a  may be in electrical connection with a first TCON  102   a  and the second display  30   b  may be in electrical connection with a second TCON  102   b . The first and second TCONs  102   a  and  102   b,  respectively, may be in electrical communication with the system control board  101 . The video players  103   a  and  103   b  may each comprise two electrical connections with the system control board  101  such that each video player  103   a  and  103   b  may control both the first and the second displays  30   a  and  30   b.    
         [0026]      FIG. 2  is a logical flowchart for operating a first embodiment of the system. In this embodiment, the system begins by applying power to the video player  103   a.  The system may next allow time for the display assembly to boot up, such as but not limited to, by use of a timer or counter. 
         [0027]    In this embodiment, the system may then monitor the video player  103   a  to see if it is communicating, thus indicating normal operation. The system may monitor the video player  103   a  by checking for a heartbeat signal, which is periodically generated by the video player  103   a  to indicate normal operation or to synchronize other parts of the system. Alternatively, the system may monitor the signal from the power LED  105  to see if it is active. As another alternative, the system may transmit a ping to see if the video player  103   a  responds. In still further alternate embodiments, the system may check for status messages that may be periodically sent from the player  103   a  to the control board  101 . If the video player  103   a  is communicating though any of the aforementioned or other means, the system may continue to apply power to the video player  103   a.    
         [0028]    If the video player  103   a  is not communicating, the system may do one of two things. First, the system may initiate a recovery sequence as described in greater detail in  FIG. 9 . Second, the system may store a downtime event or failure data at the system control board  101  and optionally transmit the downtime event or failure data to the NOC device  200 . In some embodiments, the system may perform both functions when no communication is detected from the player  103   a.    
         [0029]    Regardless, if the video player  103  is communicating, the system may return to the beginning of the logic and simply apply power to the video player  103   a  while continuing to monitor the signal from the power LED  105   a.    
         [0030]      FIG. 3  is a logical flowchart for operating a second embodiment of the system. Here the system begins by driving the display  30  from the primary player  103   a . The system would then check to determine if any failure data or downtime event had been stored for the primary player  103   a  and if not, the system continues the normal operations with the primary player  103   a.  If any failure data or downtime event had been stored for the primary player  103   a,  the system may then switch to drive the display  30  from the secondary player  103   b.  For example, but not to serve as a limitation, a failure or downtime event may include no video being shown on the display  30 , an unsupported resolution format being received, an unsupported frame rate being received, an error message being received, or the like. 
         [0031]    Those having an ordinary level of skill in the arts will recognize that any threshold of amount, frequency, or type of failure data or downtime events may be set such that the system will not switch between the primary player  103   a  and the secondary player  103   b  until the threshold has been met or exceeded. 
         [0032]      FIG. 4  is a logical flowchart for operating a third embodiment of the system. In this embodiment, the system begins with logic similar to that shown and described above with respect to  FIG. 3 . 
         [0033]    Under normal operating conditions, the system may drive the display  30  from the first video player  103   a.  However, once the system switches to the secondary player  103   b,  the system would preferably check to determine if the second video player  103   b  is communicating. If so, the system may continue normal operations with the second video player  103   b.  If not, the system may then do one of two things. First, the system may initiate a recovery sequence on the second video player  103   b  as previously discussed. Second, or in addition, the system may check to see if the first video player  103   a  is communicating. Preferably, the system first initiates the recovery sequence and only checks to see if the primary players is communicating after finding that the recovery sequence in unsuccessful. If the first video player  103   a  is communicating, the system may switch back to the first video player  103   a.  If not, the system may store a downtime event or failure data at the system control board  101  and optionally transmit the downtime event or failure data to the NOC device  200 . In some embodiments, the system may perform both functions when the first video player  103   a  is not communicating. Further, if both the first and second video players  103   a  and  103   b  are not communicating, the system may direct the display assembly  200   d  to remain in a failure or downtime event condition. For example, but without limitation, the failure or downtime event condition may display a default or error message. 
         [0034]      FIG. 5  is a logical flowchart for operating a fourth embodiment of the system. Here the system begins by driving the display  30  from the primary player  103   a.  The system would then check to determine if the primary player  103   a  is communicating. If so, the system continues normal operations with the primary player  103   a.  If not, the secondary player  103   b  would then be used to drive the display  30  and the system may force a power off of the primary player  103   a  and then initiate a recovery sequence on the primary player  103   a.  The system would then return to check if the primary player  103   a  is communicating. If so, the system resumes operations from the primary player  103   a , using it to drive the display  30 . If not, the system continues operations with the secondary player  103   b  and may store a downtime event or failure data at the system control board  101  and optionally may transmit the downtime event or failure data to the NOC device  200 . 
         [0035]      FIG. 6  is a logical flowchart for operating a fifth embodiment of the system. In this embodiment, the system begins by pinging an outside server or internal network address that is known (or assumed) to be operational. If there is no response from the ping, a downtime event is stored for the network connection, indicating some type of failure within the network and/or the network interface component  70 . The system may then return to ping an outside server or internal network address that is known (or assumed) to be operational. If there is again no response, then a downtime event is again stored for the network connection. Once the system receives a response for the ping, it may optionally transmit one or all of the downtime events to the NOC device  200 . 
         [0036]      FIG. 7  is a logical flowchart for operating a sixth embodiment of the system. In this embodiment, the system begins by pinging an outside server or internal network address that is known (or assumed) to be operational. If there is a response to the ping, the system may return to re-ping an outside server or internal network address again in the future to confirm that the network is operating correctly. If there is no response from the ping, the system may initiate a recovery sequence of the network interface component  70 . The system would preferably return again to re-ping an outside server or internal network address again in the future to confirm that the network is operating correctly. 
         [0037]      FIG. 8  is a logical flowchart for operating a seventh embodiment of the system. In this embodiment, the system control board  101  may analyze each frame of video/image data from the video player  103   a  to determine if the frame data has changed over a period of time (T), which can be any period of time chosen by the user, where an exemplary period of time (T) may be on the order of 10-15 minutes, but again could be any period of time. If the frame data has changed, the system would return to have the control board  101  analyze more frames of video/image data. If the frame data has not changed over T, then a default image or video may be displayed while the system initiates a recovery sequence on the video player  103   a.  Optionally, the system may store a downtime event or failure data for the video player  103   a  at the system board  101 . After running the recovery sequence on the video player  103   a,  the system may return to normal operations so that the control board  101  may analyze more frames of video/image data to confirm that either the video player  103   a  is now operating properly, continues to operate properly, or continues to have downtime or a failure. 
         [0038]      FIG. 9  is a logical flowchart for operating an eighth embodiment of the system. Specifically,  FIG. 9  describes an exemplary embodiment of the recovery sequence. The recovery sequence may include a simulation of the user depressing the power button  104   a  and/or attaching and reattaching the power supply (i.e., unplugging and re-plugging in the display assembly  200  or individual components thereof). The recovery sequence may comprise a simulated “short push” of the power button  104   a,  a “long push” of the power button  104   a,  and/or ceasing to supply power to the video player  103   a  and then reapplying power after a period of time has elapsed. The short push may simply command the video player  103   a  to restart. The long push may force the video player  103   a  to restart. Alternatively, or in addition, the recovery sequence may cut power to the video player  103  and then reapply power after a period of time has elapsed. 
         [0039]    In exemplary embodiments of the present invention, the system may first simulate a short push of the power button  104   a  for the video player  103   a  and allow time for it to restart. The system may then check to see if the video player  103   a  is communicating. If so, the system may store a downtime event and optionally may transmit the downtime event to the network operations center  200 . If not, the system may simulate a long push of the power button  104   a  and allow time for the video player  103   a  to reboot. The system may then check to see if the video player  103   a  is communicating. If so, the system may store a downtime event and optionally may transmit the downtime event to the network operations center  200 . If not, the system may cease applying power to the video player  103   a,  wait a predetermined amount of time, and reapply power to the video player. 
         [0040]    Optionally, the system may then check to see if the video player  103   a  is communicating. If so, the system may store a downtime event and optionally may transmit the downtime event to the network operations center  200 . If not, the system may store a failure, optionally place the display assembly  200   d  in a default or failure mode, and optionally may transmit the failure to the network operations center  200 . 
         [0041]    While the recovery sequence is discussed with respect to the video player  103   a  and the respective power button  104   a,  it may be utilized with the second video player  103   b  and the respective power button  104   b,  the power button  75 , as well as with other components of the system. 
         [0042]    As used herein, a downtime event and/or failure is a data package representing any number of pieces of data including but not limited to the date and time for when the particular portion of the system went down, specifically which component of the system went down, how long the component was down, and the date and time for when operations resumed. 
         [0043]    In exemplary embodiments of the present invention, and as discussed herein, the first video player  103   a  may be designated as the primary player, and the second video player  103   b  may be designated as the secondary player, though the reverse is contemplated. 
         [0044]    The electronic display  30  can be any flat panel electronic display including but not limited to: liquid crystal displays (LCD), organic light emitting diode (OLED) displays, plasma displays, electroluminescent polymer displays, and the like. 
         [0045]    Those having an ordinary level of skill in the arts will recognize that the buttons described herein, such as but not limited to the power button  75  and the power button  104 , may be physical buttons or may be non-physical buttons such as an electrical signal, switch, circuit, transistor, or the like. 
         [0046]    Having shown and described a preferred embodiment of the invention, those skilled in the art will realize that many variations and modifications may be made to affect the described invention and still be within the scope of the claimed invention. Additionally, 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 invention. It is the intention, therefore, to limit the invention only as indicated by the scope of the claims.