Patent Grant
8918544
The present invention generally relates to remote-control systems. More particularly, embodiments of the present invention relate to a remote-control system configured to operate on a variety of remote control platforms, such as High Definition Multi-Media Interface appliances.
Traditional remote-control devices for controlling appliances have typically been hand-held electronic devices, and have typically been configured to control a variety of appliances including televisions, DVD players, stereo equipment (e.g., CD players, tuners, amplifiers, etc.), personal video recorders (PVRs), set-top-boxes (cable television tuners, satellite dish tuners, etc.), surround sound devices, other remote-control devices (e.g., IR blasters, RF blasters, etc.), media applications on a computer, or other types of processor controlled devices, etc. Some remote-control devices are also configured to control heating systems, cooling systems, lighting, window coverings, and the like.
Modern remote-control devices have progressed from traditional hand-held electronic devices to remote-control systems that may be embedded in appliances, blasters, set-top-boxes, bridges, etc. One or more components of such embedded systems may continue to be hand-held, either in a form factor similar to a traditional remote-control device, or as a software-based controller embedded in hand-held devices, such as smartphones. As is well known by those of skill in the art, the High Definition Multi-Media Interface (HDMI) standard specifies the Consumer Electronic Control (CEC) standard, which provides for connected HDMI appliances (e.g., connected via HDMI cables) to remotely control one another. That is, the CEC standard provides that connected HDMI appliance may each include a remote-control system, which is embedded in an HDMI appliance, where each remote-control system in each connected HDMI appliance may control the other connected HDMI appliances. The CEC standard is an option standard and is not required to be implemented in HDMI appliances. The goal of the CEC standard is to simplify the remote control of HDMI appliances by providing that a single command entered in one HDMI appliance may be proliferated throughout a set of HDMI appliances to place the set of HDMI appliances in a desired state. For example, one of the more commonly expected remote control functions under the CEC standard is “one touch play.” For one touch play, an HDMI DVD player, for example, receiving a play command to play a DVD may issue CEC command codes to an HDMI TV to power on, switch the input to the HDMI DVD player, and format the screen dimensions (e.g., widescreen) for the DVD. The HDMI DVD player may also issue CEC command codes to an HDMI surround sound system to power on and adjust to a given volume level and sound equalization setting. The foregoing described remote-control operation has traditionally required a series of button presses on one or more traditional remote-control devices. The CEC standard provides that these multiple commands may be accomplished with a single button press (e.g., press of the play button on the HDMI DVD player, the press of the play button on a traditional remote-control device configured to control the HDMI DVD player, etc.).
While the CEC standard was designed to simplify remote control operations, the CEC standard introduces a number of complications into remote-control systems embedded in HDMI devices. One complication that the CEC standard introduces is the allowance of custom CEC command codes for HDMI appliances. More specifically, custom CEC command codes may be created for some HDMI appliances where these custom CEC command codes are unrecognized and not understood by other HDMI appliances. Therefore, not all HDMI appliances that are interconnected will be configured to understand the custom CEC command codes of other HDMI appliances. Further, the CEC standard provides limited solutions for correcting and compensating for failed CEC command codes.
Therefore, new remote-control systems, such as new embedded remote-control systems, are needed to provide solutions for known short comings in the CEC standard as well as to provide enhanced functions not specified by the CEC standard.
The present invention generally relates to remote-control systems. More particularly, embodiments of the present invention relate to a remote-control system configured to operate on a variety of remote control platforms, such as HDMI appliances.
According to one embodiment of the present invention, a method for configuring a remote-control system includes querying via a bus a High Definition Multi-Media Interface (HDMI) display for an Extended Display Identification Data (EDID) for the HDMI display; receiving via the bus from the HDMI display the EDID for the HDMI display; and storing via a processor in a memory the EDID and a link between the EDID of the HDMI display a set of command codes configured for controlling the HDMI display.
According to a specific embodiment, the set of command codes is a set of IR command codes or a set of CEC command codes. According to another specific embodiment, the method further includes storing via a processor in the memory another link between the EDID of the HDMI display and a model number for the HDMI display. According to another specific embodiment, the method further includes determining the model number from an inference from operation of a remote-control device, from querying a user of the remote-control device, or from downloading to the remote-control system the model number from a remote database.
According to another specific embodiment, the method further includes storing via a processor in the memory another link between the EDID of the HDMI display and a make of the HDMI display. The memory may be a local memory of the remote-control system or a remote memory accessible by a plurality of remote-control systems.
According to one embodiment of the present invention, a method for configuring a remote-control system includes querying via a bus a set of High Definition Multi-Media Interface (HDMI) appliances for a set of Consumer Electronic Control (CEC) identifiers, where the HDMI appliances of the set of HDMI appliances are respectively associated with the CEC vendor identifiers of the set of CEC vendor identifiers. The method further includes receiving via the bus from the set of HDMI appliances the set of CEC vendor identifiers. The method further includes storing via a processor in a memory the set of CEC vendor identifiers, and a set of links that respectively link in the memory the CEC vendor identifiers in the set of CEC vendor identifiers with sets of command codes for the set of HDMI appliances.
According to a specific embodiment, the method further includes storing via a processor in the memory another set of links respectively linking the CEC vendor identifiers of the set of CEC vendor identifiers and make identifiers of a set of make identifiers, which identify the HDMI appliances in set of HDMI appliances. According to another specific embodiment, the method further includes storing via a processor in the memory another set of links between the CEC vendor identifiers of the set of CEC vendor identifiers and model numbers of a set of model number for the HDMI appliances in the set of HDMI appliances.
According to one embodiment of the present invention, a method for operating a remote-control system includes monitoring a Consumer Electronic Control (CEC) bus for a CEC command code transmitted over the CEC bus from a first HDMI appliance to a second HDMI appliance, which is connected to the first HDMI appliances via an HDMI link. The method further includes monitoring the CEC bus for a response issued from the second HDMI appliance in response to receipt and execution of the CEC command code. The method further includes, if a response is not issued from the second HDMI appliance: i) determining an IR command code that corresponds to the CEC command code for the second HDMI appliance, and ii) transmitting the IR command code to the second HDMI appliance to perform a function associated with the CEC command code. The method further includes, if a response is issued from the second HDMI appliance, not transmitting an IR command code to the second HDMI appliance.
According to a specific embodiment, the method further includes not transmitting an IR command code to the second HDMI appliance if a response is not issued from the second HDMI appliance and if the second HDMI appliance is not configured to issue a response for receipt and execution of the CEC command code. According to another specific embodiment, the method further includes determining whether the second HDMI appliance is configured to transmit a response for receipt and execution of the CEC command code. The determining step may includes receiving from a remote database information for whether the second HDMI appliance is configured to transmit a response for receipt and execution of the CEC command code.
According to another specific embodiment, the method further includes if a response is not issued from the second HDMI appliance, then storing failure information in a memory for the CEC command code; and if a response is issued from the second HDMI appliance, then storing in memory pass information for the CEC command code. A function of the IR command code matches a function of the CEC command code.
According to one embodiment of the present invention, a method for building a database of command codes includes monitoring a CEC bus for a set of CEC command codes transmitted over the CEC bus; and comparing the set of CEC command codes transmitted over the CEC bus with sets of known CEC command codes for an HDMI appliances that received the set of CEC command codes. The method further includes identifying a subset of CEC command codes, which are included in the set of CEC command codes and which are not in the sets of known CEC command codes; and storing the subset of CEC command codes in memory as unrecognized.
According to a specific embodiment, the method further includes transferring the subset of CEC command codes to a remote database to query the remote database whether the CEC command codes in the subset of CEC command codes are stored in the remote database as recognized. According to another specific embodiment, the method further includes transferring function information for the subset of CEC command codes to the remote-control engine for use thereby, if the subset of CEC command codes are included in a set of known CEC command codes stored in the remote database. According to another specific embodiment, the method further includes analyzing the subset of CEC command codes to determine the functions of the subset of CEC command codes, if the subset of CEC command codes are not included in a set of known CEC command codes stored in the remote database.
According to one embodiment of the present invention, a volume control method for controlling a volume of sound output from an appliance configured to receive a media stream, the method includes receiving an input at a multi-media gateway for raising the volume of sound output by an appliance for a media stream; and raising in the multi-media gateway an embedded-digital volume embedded in the media stream. The method further includes thereafter, transmitting the media-stream to the appliance for play on the appliance.
According to a specific embodiment, the method further includes if the received input causes the embedded-digital volume to be raised by the multi-media appliance to an embedded-digital volume maximum, directing the appliance to raise an analog volume control for the media stream. According to another specific embodiment, the method further includes if the received input causes the embedded-digital volume to be raised to a level below the embedded-digital volume maximum, thereafter maintaining the analog volume at a constant level.
According to another specific embodiment, the method further includes receiving a second input at the multi-media gateway or lowering the volume of sound output by the appliance; and directing the appliance to lower an analog volume control for the appliance.
While the foregoing paragraphs of the summary section describe several embodiments related to i) linking sets of CEC command codes to EDIDs and CEC vendor IDs, ii) building CEC command code databases, iii) determining CEC command code failures and action taken in view thereof (e.g., determining substitute command codes therefore, building a CEC command code database, etc.), the embodiments described herein are not so limited. Specifically, embodiments that are described with respect to sets of CEC command codes may be equally applied to other sets of command codes, such as set of IR command code, set of RF command codes, etc. For example, the embodiment described herein may be applied to linking EDIDs to IR command codes, linking CEC vendor IDs to IR command codes, determining whether IR command codes fail and determining alternative command codes therefore. Various embodiment of the present invention may be operable with bi-directional and two-way wired and wireless protocols (e.g., IP, RF, such as BT, etc.) over a standard medium or an open medium.
These and other benefits of the embodiments of the present invention will be apparent from review the following specification and attached figures.
The present invention generally provides a remote-control system. More particularly, embodiments of the present invention provide a remote-control system configured to operate on a variety of remote control platforms, such as High Definition Multi-Media Interface (HDMI) appliances.
Entertainment System Overview
According to a further embodiment of the present invention, entertainment system 100 includes a remote-control device 115. Remote-control device 115 may be a hand-held remote-control device, such as a universal remote-control device. The remote-control device may be the remote-control keyboard of the Logitech Revue™ multi-media gateway, a Logitech Harmony™ Remote Control, a smart-phone device with a remote-control software application, etc.
According to another embodiment, entertainment system 100 includes a computer 122 or may be configured to communicate with computer 122. Computer 122 may include a computer memory (hard disk drive, flash memory, optical drive, etc.) configured to store computer code. Computer 122 may also include a display, and a set of input devices, which may include a computer keyboard, a mouse, etc. The remote-control system (e.g., operating on one of the HDMI appliances, the multi-media gateway, or the remote-control device) may be configured to communicate with computer 122 via a wired or wireless connection. For example, the remote-control system operating on the multi-media gateway may be configured to communicate with computer 122 via an Ethernet connection, a coaxial cable connection, a WiFi link provided by a local wireless router, Home RF, etc. Remote-control device 115 may similarly be configured to communicate with computer 122 via a docked connection, a WiFi link provided by a wireless router, Home RF, etc.
Computer 122 may be configured to communicate with a remote server 125 via a network 130 (e.g., the Internet). A server (e.g., remote server 125) as referred to herein includes one or both of a server computer and server software (e.g., a server operating system) operating on the server computer. Remote server 125 may include a computer memory (hard disk drive, flash memory, optical drive, etc.) configured to store computer code. Remote server 125 may also include a display, and a set of input devices, which may include a computer keyboard, a mouse, etc. Remote server 125 may be coupled to a remote database 135. Remote database 135 is configured to store sets of command codes, such as sets of IR command codes and sets of CEC command codes, which may include custom CEC command codes. The remote database is also configured to store a “link” that associates a set of command codes with an appliance (e.g., an HDMI appliance) that is configured to understand the set of command codes. The remote database may store the sets of command codes and the links under control of the remote server. For example, the remote server may be configured to direct the remote database to store a link that associates a given Sony Internet TV with the set of command codes (e.g., IR command codes and/or CEC command codes) configured to control the Sony Internet TV.
While the foregoing description describes a remote database being configured to store sets of command codes, links that associate sets of command codes with appliances, etc., the sets of command codes, links between set of command codes, etc., may be alternatively store, or additionally stored, in other storage devices, such as the storage devices of computer 122, the storage devices of the multi-media gateway, any of the HDMI appliances, etc.
According to some embodiments, the multi-media gateway and the circuits therein may be configured to perform the methods of operation of computer 122 described above. According to an embodiment where the multi-media gateway is configured to perform the methods of operation of computer 122, the multi-media gateway may communicate directly with the remote server 125 and/or the remote database 135 via the network. According to an embodiment where the HDMI display includes computer 122 or is configured to perform the methods of computer 122, the HDMI display may communicate directly with the remote server 125 and/or the remote database 135 via the network.
According to one embodiment, one or more of the HDMI appliances and/or the multi-media gateway may be configured to operate as remote-control devices for the other HDMI appliances. Each HDMI appliance and the multi-media gateway may include a remote-control system 140, which is configured to run a remote-control engine 145.
According to a further embodiment, entertainment system 100 may includes other HDMI appliances configured to play media, such as sound. These other HDMI appliance may include speakers, headsets, headphones, in-ear monitors etc.
Memory 210 may be configured to store a local file or a local database 220, which includes sets of command codes. The sets of command codes in the local file or the local database may include at least one set of IR command codes (configured to be transmitted in IR or RF). The sets of command codes in the local file or the local database may also include at least one set of Consumer Electronic Control (CEC) command codes. The set of CEC command codes may be the standard CEC command codes specified by the HDMI standard or may be custom CEC command codes, which are permitted by the CEC standard. Memory 210 may be also configured to store computer code (e.g., compiled computer code) for one or more applications executable by the processor. According to one specific embodiment, memory 210 is configured to store an application for remote-control engine 145, which may include Logitech's Harmony Link™ engine.
The set of transceivers 210 may include an IR transceiver 210a and/or an RF transceiver 210b. An IR transceiver in at least one of the HDMI appliances may be configured to transmit IR command codes to, and receive IR command codes from, other IR transceivers in other HDMI appliances or the multi-media gateway. An IR transceiver in the multi-media gateway may be similarly configured to transmit IR command codes to, and receive IR command codes from, other IR transceivers in the HDMI appliances. The RF transceivers in the HDMI appliances and the multi-media gateway may be similarly configured to the IR transceivers. According to one embodiment, bus 215 includes a CEC bus over which CEC command codes may be communicated between the HDMI appliances and the multi-media gateway. According to one embodiment, the remote-control engine operating on the processor is configured to monitor transmission over the CEC bus. Monitoring of the CEC bus is described in further detail below.
Elements of a given remote-control system 140 in an HDMI appliance may be shared with other systems in the HDMI appliance. Elements of a given remote-control system 140 in the multi-media gateway may be shared with other systems in the multi-media gateway. For example, the processor may be configured for use by one or more application operating on an HDMI appliance. The bus may similarly be configured to be used (i.e., included) in one or more system. For example, the CEC bus may be used by the HDMI systems in the HDMI appliances.
Remote-control device 115 may similarly be configured to include a processor configured to operate the remote-control engine and a memory configured to store the remote control engine. The memory may also be configured to store a local file or a local database where the local file or the local database includes sets of command codes. The sets of command codes may be sets of IR command codes and sets of CEC command codes for controlling the HDMI appliances, the multi-media gateway, and/or other appliances (e.g., non-HDMI appliances). Remote-control device 115 may be configured to transmit and receive in IR, RF, etc. and may include a communication port for communication of CEC command codes. According to one embodiment, the multi-media gateway is a bridge device for communicating command codes received from remote-control device 115 to the HDMI appliances. The multi-media gateway may be configured to translate command codes, such as translating received command codes (e.g., received IR command codes) to CEC command codes, or translating received command codes (e.g., received IR command codes) to RF command codes. U.S. patent application Ser. No. 12/731,086, filed Mar. 24, 2010, of Saumil Makim et al., describes many embodiments of bridge devices configured to translate command codes for different communication networks and is incorporated by reference in its entirety herein for all purposes.
Collect the EDID from the HDMI Display
According to one embodiment, the remote-control engine operating on the remote-control system of the multi-media gateway is configured to collect the Extended Display Identification Data (EDID) of HDMI display 105a. For example, the remote-control engine may collect the EDID of the HDMI display if the multi-media gateway and HDMI display are coupled by an HDMI cable. The remote-control engine of the multi-media gateway or the remote control device may query the HDMI display via a two-way IR or RF communication to collect the EDID. The multi-media gateway or the remote-control device may be configured to “link” the EDID for the HDMI display with the locally stored set of command codes (IR command codes and/or CEC command codes) for the HDMI display. The link may be an entry in a local memory in a file, database, etc. where the EDID is stored with the sets of command codes.
According to another embodiment, the multi-media gateway is configured to transfer the EDID, for example, via computer 122 to remote server 125 and remote database 135 where the EDID may be linked with the sets of command codes for the HDMI display. Alternatively, according to the embodiment where the multi-media gateway includes computer 122 or is otherwise network enabled, the multi-media gateway is configured to transmit the EDID directly to the remote server via a network connection. According to another embodiment, the EDID is linked locally by the remote-control engine to the sets of command codes for the HDMI display, and then the links are transferred to the remote server 125 and remote database 135. According to another alternative embodiment, the HDMI display may be configured to transmit its EDID to remote server 125 for storage in remote database 135, for example, via computer 122, so that the EDID may be linked to the sets of command codes for the HDMI display in the remote database. According to a further embodiment, the EDID for the HDMI display may also be linked to the make (e.g., manufacturer name) and/or the model number of the HDMI display in the local memory in the multi-media gateway, in the local memory of the remote-control device, or in remote database 135. The remote-control engine operating on one of the HDMI display, the multi-media gateway, or the remote-control device may collect the EDID, transmit the EDID to the remote database, and request that above described links be established.
According to one embodiment, the multi-media gateway, the HDMI display, and/or the computer may be configured to configure the multi-media gateway. That is, the multi-media gateway, the HDMI display, and/or the computer may be configured to store computer code on a non-transitory memory device for configuring the multi-media gateway. The multi-media gateway may be configured by supplying sets of command codes to the multi-media gateway for the appliances that are in entertainment system 100, by setting up user preferences, establishing user tracking preferences, etc.
The make and/or the model number of an HDMI appliance or other appliance may be determined by inferring the make and/or the model number via user interaction with the user's remote-control device, by collecting the make and/or the model number from a user, or collecting a make and model number from the remote database where the where the make and/or model number may be stored and retrieved. The make and/or the model number for an HDMI appliance is typically determined during a setup process of the remote-control device, the multi-media gateway, or the HDMI appliance (e.g., at the time the HDMI appliance is added to entertainment system 100). Once a make and/or a model number for an appliance is determined, the make and/or the model number may be transmitted to the remote server for storage in the remote database where the make and/or the model number may be provided for use by other entertainment systems of other users of the remote server and remote database. U.S. patent application Ser. No. 11/267,528, filed Nov. 3, 2005, titled “Configuration Method for a Remote Control Via Model Number Entry for a Controlled Device,” of Glen McLean Harris et al. describes a user interactive method for inferring a make and/or model number of an appliance and is incorporated by reference herein in its entirety for all purposes.
According to one embodiment, during a “setup” process of the remote-control device, the multi-media gateway, or any device including the remote-control system and remote-control engine are configured to install sets of command codes for controlling appliances, such as HDMI appliances. A setup process may be executed, for example, at the time a user first purchases a remote-control device, a multi-media gateway, etc., may be executed at a user's request, or may be executed at the initiation of computer system 122 or the remote server 135, etc. During the execution of a setup process
Collect the CEC Vendor ID from HDMI Appliances
According to another embodiment of the present invention, remote-control engine operating on the remote-control system of the multi-media gateway is configured to collect the CEC vendor identifier (ID) of one or more of the HDMI appliances in entertainment system 100. In one embodiment an HDMI appliance is identified by the HDMI appliance's CEC vendor ID. In one embodiment an HDMI appliance is identified by its On Screen Display (OSD) string. In one embodiment, the HDMI appliance is identified by aggregating the set of CEC protocol properties. In one embodiment an HDMI appliance is identified by transmitting one or more CEC command codes to the HDMI display and monitoring how the HDMI display responds to one or more standard or custom CEC command codes. In one embodiment an HDMI appliance is identified by its response time to reply to one or more CEC command codes. In one embodiment an HDMI appliance is identified by a combination of the previously described methods. The determined identity of the HDMI appliance is further referred to as the CEC vendor ID.
The remote-control engine of the multi-media gateway or the remote-control device may be configured to “link” the CEC vendor ID for an HDMI appliance with the locally stored (e.g., in the local memory of the multi-media gateway or the remote-control device) sets of command codes (set of IR command codes and/or set of CEC command codes) for the HDMI appliance. Alternatively, the multi-media gateway or the remote-control device may be configured to transfer the CEC vendor ID, for example, via computer 122 to remote server 125 for storage in remote database 135 where the CEC vendor ID may be linked with the sets of command codes for the HDMI appliance. According to a further embodiment, the CEC vendor ID for an HDMI appliance may also be linked to the make (i.e., manufacturer name, such as Sony, Magnavox, etc.) and/or the model number of the HDMI appliance in the local memory (e.g., in a file, a database, etc.) in the multi-media gateway, the remote-control device, or in the remote database 135. The remote-control engine operating on the multi-media gateway or the remote-control device may collect the CEC vendor ID, transmit the CEC vendor ID as described above, and/or request that the links be established. According to another embodiment, the remote server controlling the remote database is configured to establish the links in the remote database.
According to one embodiment, linking an EDID to a make or a model number of the HDMI display initiates the remote server to link the EDID to a set of IR command codes for the HDMI display stored in remote database 135, and/or to link the EDID to a set of CEC command codes for the HDMI display stored in remote database 135. According to one embodiment, linking a CEC vendor ID to a make or a model number of an HDMI appliance initiates the remote server to link the CEC vendor ID to a set of IR command codes for the HDMI appliance stored in remote database 135, and/or to link the CEC vendor ID to a set of CEC command codes for the HDMI appliance stored in remote database 135.
Build Database of Command Codes
According to one specific embodiment, the unrecognized CEC command codes may be transferred from the remote-control engine (e.g., from the multi-media gateway) to the remote server, step 440. The remote server may query the remote database to determine whether the unrecognized CEC command codes are included in sets of known CEC command codes, which are stored in the remote database, step 450. If the unrecognized CEC command codes are included in sets of known CEC command codes stored in the remote database, the remote server may be configured to transfer function information for the unrecognized CEC command code to the remote-control engine so that the remote-control engine will thereafter recognize the previously unrecognized CEC command codes, step 460. The remote-control engine may be configured to store the function information and the CEC command code associated with the function information in the local memory, such as the local memory of the multi-media gateway, step 470. Alternatively, if the remote server determines that the unrecognized CEC command codes are not stored in the remote database, the remote server may store the unrecognized CEC command codes in the remote database, step 480, with information indicating that these CEC command codes are unrecognized.
The unrecognized CEC command codes stored in the remote database may thereafter be analyzed to determine the functions associated with the unrecognized command codes. For example, the unrecognized CEC command codes may be analyzed by a human user to determine the functions associated with the unrecognized command codes. A human user may use a remote-control engine (e.g., operating on a multi-media gateway or other test device) to transfer the unrecognized CEC command codes to a set of HDMI appliance and monitor the changes that occur on the set of HDMI appliances. The human user may then direct the remote server to store the functions for the previously unrecognized CEC command codes in the remote database for distribution to various entertainment system of various users that include the HDMI appliance.
According to one embodiment of the present invention, the remote server may be configured to send a transmission to the remote-control engine to inform the remote-control engine that the unrecognized CEC command codes are unrecognized by the remote server. Thereafter, the remote-control engine may be configured to attempt to determine the functions associated with the unrecognized CEC command codes. For example, the remote-control engine may be configured to compare two sets of states of an HDMI appliance where the first set of states is for the HDMI appliance before the set of unrecognized CEC command codes is issued to the HDMI appliance, and the second set of states is for the HDMI appliance after the set of unrecognized CEC command codes is issued to the HDMI appliance. If the remote-control engine determines a difference in the sets of states, the remote-control engine may be able to determine the functions of the set of unrecognized CEC command codes. The remote-control engine, via the multi-media gateway may transmit IR command codes to the HDMI appliance to determine the state of the HDMI appliance. Alternatively, the remote-control device may be configured to display a set of interactive questions on the display of the remote-control device for interaction with a user of the remote-control device to determine the functions associated with the set of unrecognized CEC command codes. The remote-control engine operating on the multi-media appliance might direct the remote-control device to display the interactive questions and perform the analysis of the unrecognized CEC command codes. For example, the remote-control device might display to the user that the remote-control engine operating on the mulit-media appliance is issuing one of the unrecognized CEC command codes to the HDMI display, and then ask the user to input any observed changes into the remote-control device. If the remote-control device determines the functions for the previously unrecognized CEC command codes, the remote-control device may store function information for the previously unrecognized CEC command codes and transfer the function information to the remote-control engine operating on the multi-media gateway.
The remote-control engine (e.g., operating on the multi-media gateway) may transfer the determined functions for the previously unrecognized CEC command codes to the remote server for storage in the remote database. The remote server may generate soft buttons and macros for the remote-control engine for the previously unrecognized CEC command codes. The remote serve may transfer the soft buttons and macros for the previously unrecognized CEC command codes to the remote-control engine for storage and use by the remote-control engine. The determined functions, soft button, and/or macros for the previously unknown CEC command codes may be transferred to the multi-media gateway of other users. The remote server may share the function information with other entertainment systems of other users.
In accordance with one embodiment of the present invention, the remote database is “continually” built and expanded over a period of time, such as days, months, and years, using information from a plurality of users, a plurality of remote control engines, a plurality of multi-media gateways, etc. Information from various users, remote control engines, multi-media gateways is uploaded to the remote database to build, improve, and expand the remote database, and this expanded information may be “continually” downloaded (e.g., hourly, daily, weekly, monthly, etc.) onto several remote control engines for use by those several remote control engines, which may be owned and operated by a plurality of other users. Details of various methods for uploading command codes to a remote database and downloading command codes from the remote database to various remote control devices, such as the multi-media gateway operating the remote control engine may be found in U.S. Pat. No. 7,436,319, titled “Method an Apparatus for Uploading and Downloading Remote Control Codes,” of Glen McLean Harris et al. and is herein incorporated by reference in its entirety.
Operation of the Remote Control Engine
According to a particular embodiment, the method described above with respect to
According to another alternative embodiment, the remote-control engine of the remote-control system operating on the multi-media gateway may determine from the remote server that a given HDMI appliance is not configured to receive CEC command codes, and will by default send IR command codes to the given HDMI appliance instead of sending CEC command codes.
According to another alternative embodiment, the remote-control engine (e.g., operating on the multi-media gateway) may receive a set of custom CEC command codes from the remote server for an HDMI appliance. The remote-control engine may then transmit these custom CEC command codes to the HDMI appliance instead of sending IR command codes to the HDMI appliance to control the HDMI appliance.
According to another embodiment, the states of the HDMI appliances are tracked by a remote-control engine of a remote-control system on the multi-media gateway. The remote-control engine may track the power on/off state of an HDMI appliance and track the input state of the HDMI appliance, such as the HDMI display. The states may be tracked by knowing initial states of the HDMI appliance, and thereafter calculating and updating the states based on the CEC command codes transmitted to the HDMI appliance. The remote-control engine may track the states of the HDMI appliance based on the CEC command codes transmitted from the multi-other media gateway to the HDMI appliance and/or based on the CEC command codes transmitted by remote-control engines (e.g., operating on other HDMI appliances). For example, the remote-control engine tracking the states of the HDMI appliance, which received the CEC command codes, may monitor the CEC bus to track all of the CEC command codes transmitted to this HDMI appliance. According to one alternative embodiment, the power on/off state of an HDMI appliance is determined from the absence of a CEC command code being detected on the CEC bus by the remote control engine (i.e. by detecting that a given HDMI appliance has not sent any CEC command codes for a predetermined time). Some HDMI appliance do transmit regular CEC packets (e.g., get VendorID or query OSD name) after being powered on.
Thereafter, the remote-control engine may determine whether a response is issued by the HDMI appliance indicating whether the CEC command codes were received and executed by the HDMI appliance. The response may be issued to the remote-control engine if the remote-control engine issued to the CEC command codes, or the remote-control engine may monitor the CEC bus for all responses issued by the HDMI appliance to other HDMI appliances to determine whether the HDMI appliance received and executed the CEC command codes.
If the remote-control engine determines that an HDMI appliance is not in an intended state (e.g., powered off when the power is supposed to be on, or not in the correct input, e.g., HDMI 1 input instead of the intended HDMI 2 input) after the CEC command codes are transmitted to the HDMI appliance, then the remote-control engine is configured to determine a set of IR command codes to transmit to the HDMI appliance to place the HDMI appliance in the intended states (e.g., power on and input set to HDMI 2). It will be understood the while the foregoing description describes the remote-control engine of the multi-media gateway determining the states of the HDMI appliance, the described remote-control engine may operate on any of the HDMI appliances. U.S. Pat. No. 6,784,805, titled “State-Based Remote Control System” of Glen McLean Harris et al. describes a remote-control device that is configured to operate a remote-control engine that is configured to track the states of appliances based on command codes issued to the appliances, and is incorporated by reference herein in its entirety.
The following specific example is provided to add clarity to the foregoing described embodiment. If a DVD player (e.g., a first HDMI appliance) sends CEC command codes to the HDMI display to power on the HDMI display and to set the input of the HDMI display to the HDMI 2 input, the remote-control engine (e.g., operating on the multi-media gateway) monitoring the CEC bus will store information that indicates that the HDMI display is supposed to be in a power on state, and the HDMI display is supposed to have the input set to HDMI 2 input. The intended states may be stored locally by the remote-control engine in local memory (e.g., of the multi-media gateway which may be operating the remote-control engine). The remote-control engine by tracking the CEC command codes issued there from or by monitoring the CEC bus, is configured to determine that the HDMI display is supposed to be powered on and in the HDMI 2 input state. The remote-control engine monitoring the responses from the HDMI display may then determine whether the HDMI display is powered on and in the HDMI 2 input. If the HDMI display does not issue a response to the CEC command codes, the remote-control engine is configured to determine the CEC command was not successfully received and/or executed by the HDMI display. If the remote-control engine determines that power is off for the HDMI display and the input for the HDMI display is not the HDMI 2 input, then the remote-control engine may direct the multi-media gateway to send a set of IR command codes to the HDMI display to power on the HDMI display and change the input to the HDMI 2 input. The foregoing described example is not limiting on the claims as will be well understood by those of skill in the art. According to an alternative embodiment, other states in addition to the power on/off state and the input state may be monitored by the remote-control engine such as the channel state, the volume state, the surround sound state, the output state (e.g., the audio output state), etc. According to another alternative embodiment, remote-control engine may track the states of the HDMI appliances by transmitting queries to an HDMI appliance receiving a set of CEC command codes via IR communication, RF communication, or other CEC command codes.
According to a further embodiment, if the remote-control engine determines that a set of CEC command codes has not been executed correctly by an HDMI appliance, the remote-control engine may set a display on the display screen (e.g., LED display) of the remote-control device (e.g., a smartphone operating a remote control application, which may include the remote-control engine, a handheld remote-control device, etc.) based on the incorrect execution of the set of CEC command codes. The remote-control engine may set the display to include a set of screen buttons (sometimes referred to as soft button in the art) for CEC command codes that failed and/or for macros (i.e., sets of CEC command codes) that include the failed CEC command codes. For example, the remote-control engine operating on the multi-media gateway may determine that a power-on CEC command code issued to the HDMI display did not power on the HDMI display. The remote-control engine may thereafter be configured to display screen buttons for CEC command codes or for macros that include the power-on CEC command code, but not display screen buttons for CEC command codes and macros that do not include the power-on CEC command code. For example, a Watch TV command (e.g., a macro) may include a set of CEC command codes that includes the power-on CEC command code for the HDMI display, include a CEC command code for setting the input of the HDMI display for the set-top-box, and includes a CEC command code for setting the volume of the HDMI display to a predetermined volume (e.g., a relatively comfortable volume). Because the Watch TV command includes the power-on CEC command code, this command may be displayed on the display if the power-on command code for the HDMI display failed in the previous issued set of command codes. According to a further example, the Change to HDMI 2 input command will not be displayed on the display if the power-on CEC command code failed because the set of CEC command codes for the command Change to HDMI 2 input does not include the power-on CEC command code. More specifically, the Change to HDMI 2 input command will not be displayed because the Change to HDMI 2 input will not be executed by the HDMI display if the HDMI display is powered off.
According to a further embodiment, the CEC command code option may be disabled for one or more HDMI appliances. For example, the DVD player may not be configured to issue CEC command codes. The remote-control engine is configured to query each HDMI appliance to determine whether CEC command codes are disabled for the HDMI appliances. If the CEC command codes are disabled for an HDMI appliance, the remote-control system is configured to direct the multi-media gateway to transmit IR command codes in place of the disabled CEC command codes. For example, if a command is issued to the DVD player to play a DVD, and the multi-media gateway has determined that CEC command codes are disabled for the DVD player, then the multi-media gateway will send an IR command code or a CEC command code to the HDMI display to power on the HDMI display (if the HDMI display is not already on) and send an IR command code or a CEC command code to the HDMI display to change the input to the HDMI 2 input.
According to another embodiment, after the remote-control engine determines the EDID for the HDMI display and/or the CEC vendor IDs for the other HDMI appliances, the remote-control engine is configured to transfer the EDID and the CEC vendor IDs to the remote server. The remote-control engine may query the remote server to determine whether specific CEC command codes do not exist in the set of CEC command codes for the HDMI display and sets of CEC command codes for the other HDMI appliances. The remote server may use the EDID and the CEC vendor IDs to retrieve sets of CEC command codes from the remote database for the EDID and the CEC vendor IDs. The remote server may then compare the sets of CEC command codes retrieved from the remote database with a set of CEC command codes specified by the CEC standard to determine whether CEC command codes are missing from the sets of CEC command codes retrieved from the remote database. If the remote server determines that a specific CEC command code does not exist in a set of command codes retrieved from the remote database, the remote server will send information to the remote-control engine where the information indicates the CEC command code does not exist in the sets of CEC command codes presently available for the HDMI display or the other HDMI appliances. The remote-control engine may then determine an IR command codes for the CEC command codes missing from the sets of CEC command codes, and issue those determined IR command codes should the missing CEC command codes need to be transmitted to an HDMI appliance. While the foregoing analysis of CEC command codes is described to happen when the remote-control engine transfers its CEC command code or CEC vendor ID, the analysis may also have been previously performed on the remote server, the result of which has been persisted in the remote database 135 and is retrieved and served back to the remove-control engine upon such request. While the foregoing analysis of missing CEC command codes is described as taking place on the remote server operating in cooperation with the remote database, the remote-control engine may be configured to execute the same analysis locally using the local database in the multi-media gateway or the like to determine whether CEC command codes are missing from sets of CEC command codes stored in the local database of the multi-media gateway or the like.
For example, the multi-media gateway may send the CEC vendor ID for the DVD player to the remote server and query the remote server to determine whether any CEC command codes for the DVD player are not included in the set of CEC command codes for the DVD player compared to the standard set of CEC command codes specified by the CEC standard. The remote server may use the CEC vendor ID to identify the set of CEC command codes for the DVD player in the remote database. If the remote server determines that a CEC command code does not exist for directing an HDMI display to change input to the HDMI 2 input, for example, then the remote server will send information to the remote-control engine indicating that the CEC command code for changing the input to the HDMI 2 input in not included in the set of CEC command codes for the DVD player. The remote-control engine will then store the information locally, and will issue an IR command code to the HDMI display to change the input to the HDMI 2 input, for example, if the DVD player receives a command to play a DVD.
According to another embodiment, the remote-control engine is configured to query the remote server for custom CEC command codes and/or device-specific CEC command codes for the HDMI display and the HDMI appliances for which the remote-control engine collected the EDID and the CEC vendor IDs. The remote server may use the EDID and the CEC vendor IDs to query the remote database for custom CEC command codes and device-specific CEC command codes associated with the EDID and the CEC vendor IDs. The remote server is configured to send the custom CEC command codes and/or device-specific CEC command codes to the remote-control engine for the HDMI display and/or the HDMI appliances. The remote-control engine is configured to store the received custom CEC command codes and the device-specific CEC command codes in a local database. More specifically, the remote-control engine is configured to store received custom CEC command codes and device-specific CEC command codes in the sets of CEC command codes for the specific HDMI devices for which the custom CEC command codes and device-specific CEC command codes are configured to control. The remote-control engine will then be configured to transmit the custom CEC command codes and/or device-specific CEC command codes to the HDMI display and/or the HDMI appliances to control the HDMI display and/or the HDMI appliances. The custom CEC command codes and device-specific CEC command codes may be transferred to each HDMI appliance for local storage therein and for use.
According to one embodiment, the remote server and/or the remote-control engine are configured to determine the appropriate conditions for transmitting the custom CEC command codes and/or the device-specific CEC command codes. The remote server and/or the remote-control engine may also be configured to determine macros into which the custom CEC command codes and/or the device-specific CEC command codes may be inserted for transmission by the remote-control engine. U.S. patent application Ser. No. 11/199,922 (U.S. Pat. No. 7,436,319), filed Aug. 8, 2005, titled “Method an Apparatus for Uploading and Downloading Remote Control Codes,” of Glen McLean Harris et al. described a method and apparatus for uploading command codes or identifiers for command codes that are determined to correctly control an appliance (such as an HDMI appliance) via a remote-control device, and thereafter downloading the command codes or the identifiers to other remote-control devices for other users. U.S. patent application Ser. No. 11/199,922 is incorporated by reference herein in its entirety for all purposes.
Volume Control of Appliances
According to one embodiment, the remote-control engine (e.g., operating on the multi-media gateway) is configured to control the volume output of a sound system of an HDMI appliance (e.g., the speakers in the HDMI display, a surround sound system, etc.) or other appliance (e.g., a television, a surround sound system, etc.) for optimal sound quality. For example, the remote-control engine may be configured to receive an input for raising the volume output of a sound system. The received input of the remote-control engine may come via the remote-control device, which may receive an input for raising the volume via a button press by a user. While button presses are discussed herein for providing input to a remote-control device, it will be understood that a remote-control device or other device (e.g., an HDMI appliance) may receive an input via a variety of devices and methods, such as touchpad, voice recognition, gesture recognition (e.g., a swipe of a finger on a touch pad, a free space gesture, etc.), a slider, etc.
The input received by the remote-control engine may be for raising the embedded-digital volume to the embedded-digital volume maximum or may be for raising the embedded-digital volume to less than the embedded-digital volume maximum. If the embedded-digital volume is raised to the embedded-digital volume maximum, the remote-control engine (e.g., operating on the multi-media gateway) is configured to direct the sound system to raise the analog volume for subsequent inputs received (e.g., via the remote-control device) for raising the volume of the sound system. Raising the embedded-digital volume before raising the analog volume provides that the signal to noise ratio for the audio signal output by the sound system is kept relatively low. The embedded-digital volume ideally should not introduce any noise, while the analog volume raises both the desired audio and the noise.
If the embedded-digital volume is not raised to the embedded-digital volume maximum based on the received input for raising the volume level, the remote-control engine for subsequent received inputs for raising the volume level is configured to direct the source to raise the embedded-digital volume until the embedded-digital volume is at the embedded-digital volume maximum. If the embedded-digital volume is raised to the embedded-digital volume maximum, the remote-control engine is configured to direct the sound system to raise the analog volume for subsequent inputs received for raising the volume of the sound system.
According to an alternative embodiment, the remote-control engine (based on the received input for raising the volume) may direct the multi-media gateway to increase the embedded-digital volume of the media stream, if, for example, the source of the media stream providing the media stream to the multi-media gateway is not configured to raise the embedded-digital volume of the media stream. The remote-control engine may be operating on the multi-media gateway to control the multi-media gateway to raise the embedded digital volume. According to one embodiment, the remote-control engine operating on the multi-media gateway may be configured to raise the embedded-digital volume.
According to another alternative embodiment, the display (e.g., the HDMI display) is configured to raise the embedded-digital volume of a media stream if the display receives an input for raising the volume. The display may be configured to raise the embedded digital volume to a maximum volume level as described above prior to raising the analog volume.
According to one embodiment, the multi-media gateway may know that the source is configured to raise the embedded-digital volume, and therefore control the source to raise the embedded-digital volume as described above. The multi-media gateway may determine the specific sources (e.g., the set-top-box) that are configured to raise the embedded-digital volume during setup of the multi-media gateway from a user, computer 122, remote server 125, etc. Alternatively, the multi-media gateway may be configured to query a source to determine whether the source is configured to raise an embedded-digital volume of a media stream.
According to a further embodiment, if the remote-control engine receives an input (e.g., via the remote-control device) for lowering the volume of the sound system, the remote-control engine is configured to direct the sound system to lower the analog volume. For example, the multi-media gateway may direct the display (e.g., the HDMI display to lower the analog volume).
According to one alternative embodiment, if the remote-control engine receives an input for lowering the volume level of the sound system, the remote control is configured to direct the sound system to lower the analog volume if the analog volume is greater than a threshold-analog-volume level (e.g., 80% of the maximum analog-volume level). If the analog volume of the sound system is equal to or less than the threshold-analog-volume level, then the remote-control engine is configured to direct the source to lower the embedded-digital volume.
For example, if a DVD player is the source of the media stream, the remote-control engine is configured to direct the DVD player to raise the embedded-digital volume in the media stream for received inputs for raising the volume until the embedded-digital volume is at the embedded-digital volume maximum. More specifically, the DVD player is configured to decode the media stream from a DVD, raise the embedded-digital volume, and then encode the media stream with the raised embedded-digital volume. The DVD player is then configured to transmit the media stream to the multi-media gateway, and the multi-media gateway is configured to transmit the media stream to an appliance (e.g., the HDMI display) configured to play the media stream. After the embedded-digital volume is at the embedded-digital volume maximum, the remote-control engine is configured to direct the appliance (e.g., the HDMI display) to raise the analog-volume level.
According to one embodiment, the remote-control device is configured to send command codes to the multi-media gateway (e.g., acting as a bridge) for raising and lowering the embedded-digital volume and the analog volume as described above. According to further embodiment, one of the HDMI appliances (e.g., the HDMI display) may be configured to operate a remote-control engine configured to perform the foregoing described volume control steps. For example, the HDMI display may be receive a button press or the like for raising or lowering the volume of the sound system of the HDMI display. The HDMI display may send command codes to a source (e.g., a DVD player) to raise the embedded-digital volume until the embedded-digital volume is at the embedded-digital volume maximum, and thereafter the HDMI display will raise its analog volume for received inputs for raising the volume.
According to one embodiment, the embedded-digital volume may be controlled in multiple devices. For example, a first appliance (e.g., a first HDMI appliance, such as a DVD player, a set-top-box, etc.) may be a source for a media stream, which is transmitted from the first appliance to the multi-media gateway (or more generally a pass-through device) and then transmitted from the multi-media gateway to a second appliance (e.g., a second HDMI appliance, such as the HDMI display and/or sound system) configured to play the media stream.
The first appliance and the multi-media gateway may both be configured to raise the embedded-digital volume of the media stream, and the second appliance may be configured to raise the analog volume for the media stream when the media stream is played. According to one embodiment, in response to an input for raising the volume output from the second appliance the embedded-digital volume may first be raised by the first appliance to a first embedded-digital volume maximum, and then may be raised by the multi-media gateway to a second embedded-digital volume maximum. That is, the first appliance is configured to decode the media stream, raise the embedded-digital volume, and then encode the media stream. The multi-media gateway may be configured to perform that same encoding and decoding. The multi-media gateway during decoding may be configured to determine whether the embedded-digital volume of the media stream received from the first appliance is at the embedded-digital volume maximum, and raise the embedded-digital volume if the embedded-digital volume is less than the embedded-digital volume maximum. Otherwise, if the embedded-digital volume is at the embedded-digital volume maximum, the multi-media gateway may be configured to direct the second appliance to raise the analog volume. The embedded-digital volume and the analog volume may be controlled via the remote-control engine operating on the remote control device or the multi-media gateway after receiving an input to raise the volume. According to a further embodiment, the volume output by an appliance may be lowered by first lowering the analog volume of the appliance to a first volume threshold level, and thereafter lowering the embedded-digital volume first in the multi-media gateway to a first digital-volume threshold level and then lowering the embedded-digital volume in the first appliance.
According to one embodiment, the multi-media gateway is configured to receive two media streams from two sources, such as HDMI sources. Each media stream includes an audio track. The multi-media gateway may be configured to equalize the embedded-digital volumes of the two media streams. For example, the multi-media gateway may be configured to equalize the embedded-digital volume of a latter received media stream received from a first source to the same level as the embedded-digital volume of a previous received media stream received from a second source. Equalizing the embedded-digital volumes of the two media streams provides that that volume output from an appliance playing the two received media stream will be approximately the same. Equalizing the embedded-digital volumes of the two media streams as described provides that if the input for the source is changed from the second source to the first source the volume output from the appliance playing the sources will not be so loud so as to be uncomfortable, or so low as to be not understandable. For example, the embedded-digital volume of the first media stream may be higher than the embedded-digital volume of the second media stream, and the multi-media gateway may lower the embedded-digital volume of the first media stream to the same level as the embedded-digital volume of the second media stream so that the volume output by the appliance playing the media steam is not so high as to be uncomfortable. Alternatively, the embedded-digital volume of the first media stream may be lower than the embedded-digital volume of the second media stream, and the multi-media gateway may raise the embedded-digital volume of the first media stream to the same level as the embedded-digital volume of the second media stream is not so low as to not be understandable. The multi-media gateway may be configured to store in a local memory the embedded-digital volume of a previously received media stream and raise or lower the embedded-digital volume based on the stored embedded-digital volume.
It is to be understood that the examples and embodiments described above are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art, and are to be included within the spirit and purview of this application and scope of the appended claims. For example, the different steps described above for the various embodiments are not limited to the embodiments in the context in which they have been specifically described and may have broader application. For example, in one embodiment, the failed command codes identified during the operation of the remote control engine may be used to further expand the remote database of command codes.
According to a further example, while the remote-control engine is described herein as being computer code operable on a processor, the remote-control engine may be a circuit, such as an application specific circuit, firmware, or a combination of one or more of software, firmware, and circuits. According to another example, while the application describes several embodiments related to i) linking sets of CEC command codes to EDIDs and CEC vendor IDs, ii) building CEC command code databases, iii) determining CEC command code failures and action taken in view thereof (e.g., determining substitute command codes therefore, building a CEC command code database, etc.), the embodiments described herein are not so limited. Specifically, embodiments that are described with respect to sets of CEC command codes may be equally applied to other sets of command codes, such as set of IR command code, set of RF command codes, etc. For example, the embodiment described herein may be applied to linking EDIDs to IR command codes, linking CEC vendor IDs to IR command codes, determining whether IR command codes fail and determining alternative command codes therefore. Various embodiment of the present invention may be operable with bi-directional and two-way wired and wireless protocols (e.g., IP, RF, such as BT, etc.) over a standard medium or an open medium. Therefore, the above description should not be understood as limiting the scope of the invention as defined by the claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3990012 | Karnes | Nov 1976 | A |
| 4174517 | Mandel | Nov 1979 | A |
| 4394691 | Amano et al. | Jul 1983 | A |
| 4488179 | Kruger et al. | Dec 1984 | A |
| 4566034 | Harger et al. | Jan 1986 | A |
| 4626848 | Ehlers | Dec 1986 | A |
| 4774511 | Rumbolt et al. | Sep 1988 | A |
| 4837627 | Mengel | Jun 1989 | A |
| 4918439 | Wozniak et al. | Apr 1990 | A |
| 4959810 | Darbee et al. | Sep 1990 | A |
| 5109222 | Welty | Apr 1992 | A |
| 5140326 | Bacrania et al. | Aug 1992 | A |
| 5161023 | Keenan | Nov 1992 | A |
| 5177461 | Budzyna et al. | Jan 1993 | A |
| 5228077 | Darbee | Jul 1993 | A |
| 5255313 | Darbee | Oct 1993 | A |
| 5272418 | Howe et al. | Dec 1993 | A |
| 5374999 | Chuang et al. | Dec 1994 | A |
| 5410326 | Goldstein | Apr 1995 | A |
| 5414426 | O'Donnell et al. | May 1995 | A |
| 5414761 | Darbee | May 1995 | A |
| 5422783 | Darbee | Jun 1995 | A |
| 5481251 | Buys et al. | Jan 1996 | A |
| 5481256 | Darbee et al. | Jan 1996 | A |
| 5515052 | Darbee | May 1996 | A |
| 5537463 | Escobosa et al. | Jul 1996 | A |
| 5552917 | Darbee et al. | Sep 1996 | A |
| 5568367 | Park | Oct 1996 | A |
| 5579221 | Mun | Nov 1996 | A |
| 5614906 | Hayes et al. | Mar 1997 | A |
| 5619196 | Escobosa | Apr 1997 | A |
| 5629868 | Tessier et al. | May 1997 | A |
| 5638050 | Sacca et al. | Jun 1997 | A |
| 5671267 | August et al. | Sep 1997 | A |
| 5677711 | Kuo | Oct 1997 | A |
| 5686891 | Sacca et al. | Nov 1997 | A |
| 5689353 | Darbee et al. | Nov 1997 | A |
| 5778256 | Darbee | Jul 1998 | A |
| 5907322 | Kelly et al. | May 1999 | A |
| 5943228 | Kim | Aug 1999 | A |
| 5949351 | Hahm | Sep 1999 | A |
| 5953144 | Darbee et al. | Sep 1999 | A |
| 5959751 | Darbee et al. | Sep 1999 | A |
| 5963145 | Escobosa | Oct 1999 | A |
| 6002450 | Darbee et al. | Dec 1999 | A |
| 6014092 | Darbee et al. | Jan 2000 | A |
| 6097309 | Hayes et al. | Aug 2000 | A |
| 6097441 | Allport | Aug 2000 | A |
| 6104334 | Allport | Aug 2000 | A |
| 6130625 | Harvey | Oct 2000 | A |
| 6130726 | Darbee et al. | Oct 2000 | A |
| 6133847 | Yang | Oct 2000 | A |
| 6147677 | Escobosa et al. | Nov 2000 | A |
| 6154204 | Thompson et al. | Nov 2000 | A |
| 6157319 | Johns et al. | Dec 2000 | A |
| 6169451 | Kim | Jan 2001 | B1 |
| 6173330 | Guo et al. | Jan 2001 | B1 |
| 6177931 | Alexander et al. | Jan 2001 | B1 |
| 6195033 | Darbee et al. | Feb 2001 | B1 |
| 6211870 | Foster | Apr 2001 | B1 |
| 6223348 | Hayes et al. | Apr 2001 | B1 |
| 6225938 | Hayes et al. | May 2001 | B1 |
| 6243035 | Walter et al. | Jun 2001 | B1 |
| 6255961 | Van Ryzin et al. | Jul 2001 | B1 |
| 6271831 | Escobosa et al. | Aug 2001 | B1 |
| 6275268 | Ellis et al. | Aug 2001 | B1 |
| 6278499 | Darbee | Aug 2001 | B1 |
| 6288799 | Sekiguchi | Sep 2001 | B1 |
| 6330091 | Escobosa et al. | Dec 2001 | B1 |
| 6374404 | Brotz et al. | Apr 2002 | B1 |
| 6496135 | Darbee | Dec 2002 | B1 |
| 6522262 | Hayes et al. | Feb 2003 | B1 |
| 6538556 | Kawajiri | Mar 2003 | B1 |
| 6563430 | Kemink et al. | May 2003 | B1 |
| 6567011 | Young et al. | May 2003 | B1 |
| 6567984 | Allport | May 2003 | B1 |
| 6587067 | Darbee et al. | Jul 2003 | B2 |
| 6628340 | Graczyk et al. | Sep 2003 | B1 |
| 6629077 | Arling et al. | Sep 2003 | B1 |
| 6640144 | Huang et al. | Oct 2003 | B1 |
| 6642852 | Dresti et al. | Nov 2003 | B2 |
| 6650247 | Hayes | Nov 2003 | B1 |
| 6657679 | Hayes et al. | Dec 2003 | B2 |
| 6690290 | Young et al. | Feb 2004 | B2 |
| 6701091 | Escobosa et al. | Mar 2004 | B2 |
| 6720904 | Darbee | Apr 2004 | B1 |
| 6722984 | Sweeney, Jr. et al. | Apr 2004 | B1 |
| 6724339 | Conway et al. | Apr 2004 | B2 |
| 6747591 | Lilleness et al. | Jun 2004 | B1 |
| 6748248 | Pan et al. | Jun 2004 | B1 |
| 6781518 | Hayes et al. | Aug 2004 | B1 |
| 6781638 | Hayes | Aug 2004 | B1 |
| 6784804 | Hayes et al. | Aug 2004 | B1 |
| 6785579 | Huang et al. | Aug 2004 | B2 |
| 6788241 | Arling et al. | Sep 2004 | B2 |
| 6826370 | Escobosa et al. | Nov 2004 | B2 |
| 6829512 | Huang et al. | Dec 2004 | B2 |
| 6847101 | Ejelstad et al. | Jan 2005 | B2 |
| 6859197 | Klein et al. | Feb 2005 | B2 |
| 6870463 | Dresti et al. | Mar 2005 | B2 |
| 6882729 | Arling et al. | Apr 2005 | B2 |
| 6885952 | Hayes | Apr 2005 | B1 |
| 6917302 | Lilleness et al. | Jul 2005 | B2 |
| 6933833 | Darbee | Aug 2005 | B1 |
| 6938101 | Hayes et al. | Aug 2005 | B2 |
| 6946988 | Edwards et al. | Sep 2005 | B2 |
| 6947101 | Arling | Sep 2005 | B2 |
| 6968570 | Hayes et al. | Nov 2005 | B2 |
| 7005979 | Haughawout et al. | Feb 2006 | B2 |
| 7010805 | Hayes et al. | Mar 2006 | B2 |
| 7013434 | Masters et al. | Mar 2006 | B2 |
| RE39059 | Foster | Apr 2006 | E |
| 7046161 | Hayes | May 2006 | B2 |
| 7079113 | Hayes et al. | Jul 2006 | B1 |
| 7091898 | Arling et al. | Aug 2006 | B2 |
| 7093003 | Yuh et al. | Aug 2006 | B2 |
| 7102688 | Hayes et al. | Sep 2006 | B2 |
| 7119710 | Hayes et al. | Oct 2006 | B2 |
| 7126468 | Arling et al. | Oct 2006 | B2 |
| 7129995 | Arling | Oct 2006 | B2 |
| 7136709 | Arling et al. | Nov 2006 | B2 |
| 7142127 | Hayes et al. | Nov 2006 | B2 |
| 7142934 | Janik | Nov 2006 | B2 |
| 7142935 | Janik | Nov 2006 | B2 |
| 7143214 | Hayes et al. | Nov 2006 | B2 |
| 7154428 | De Clercq et al. | Dec 2006 | B2 |
| 7155305 | Hayes et al. | Dec 2006 | B2 |
| 7161524 | Nguyen | Jan 2007 | B2 |
| 7167765 | Janik | Jan 2007 | B2 |
| 7167913 | Chanmbers | Jan 2007 | B2 |
| 7193661 | Dresti et al. | Mar 2007 | B2 |
| 7200357 | Janik et al. | Apr 2007 | B2 |
| 7209116 | Gates et al. | Apr 2007 | B2 |
| 7218243 | Hayes et al. | May 2007 | B2 |
| 7221306 | Young | May 2007 | B2 |
| RE39716 | Huang et al. | Jul 2007 | E |
| 7253765 | Edwards et al. | Aug 2007 | B2 |
| 7254777 | Hayes et al. | Aug 2007 | B2 |
| 7266701 | Hayes et al. | Sep 2007 | B2 |
| 7266777 | Scott et al. | Sep 2007 | B2 |
| 7268694 | Hayes et al. | Sep 2007 | B2 |
| 7274303 | Dresti et al. | Sep 2007 | B2 |
| 7281262 | Hayes et al. | Oct 2007 | B2 |
| 7319409 | Hayes et al. | Jan 2008 | B2 |
| 7319426 | Garfio | Jan 2008 | B2 |
| 7436319 | Harris et al. | Oct 2008 | B1 |
| 7436346 | Walter et al. | Oct 2008 | B2 |
| 7877328 | Tanaka | Jan 2011 | B2 |
| 7944370 | Harris et al. | May 2011 | B1 |
| 8031270 | Wisniewski et al. | Oct 2011 | B1 |
| 8054294 | Sakai et al. | Nov 2011 | B2 |
| 8117590 | Kataoka | Feb 2012 | B2 |
| 8281047 | Yoshida et al. | Oct 2012 | B2 |
| 20020046083 | Ondeck | Apr 2002 | A1 |
| 20020056084 | Harris et al. | May 2002 | A1 |
| 20020190956 | Klein et al. | Dec 2002 | A1 |
| 20030046579 | Hayes et al. | Mar 2003 | A1 |
| 20030048295 | Lilleness et al. | Mar 2003 | A1 |
| 20030095156 | Klein et al. | May 2003 | A1 |
| 20030103088 | Dresti et al. | Jun 2003 | A1 |
| 20030117427 | Haughawout et al. | Jun 2003 | A1 |
| 20030151538 | Escobosa et al. | Aug 2003 | A1 |
| 20030164773 | Young et al. | Sep 2003 | A1 |
| 20030164787 | Dresti | Sep 2003 | A1 |
| 20030189509 | Hayes et al. | Oct 2003 | A1 |
| 20030193519 | Hayes et al. | Oct 2003 | A1 |
| 20030233664 | Huang et al. | Dec 2003 | A1 |
| 20040046677 | Dresti | Mar 2004 | A1 |
| 20040056789 | Arling et al. | Mar 2004 | A1 |
| 20040056984 | Hayes et al. | Mar 2004 | A1 |
| 20040070491 | Huang et al. | Apr 2004 | A1 |
| 20040093096 | Huang et al. | May 2004 | A1 |
| 20040117632 | Arling et al. | Jun 2004 | A1 |
| 20040136726 | Escobosa et al. | Jul 2004 | A1 |
| 20040169590 | Haughawout et al. | Sep 2004 | A1 |
| 20040169598 | Arling et al. | Sep 2004 | A1 |
| 20040189508 | Nguyen | Sep 2004 | A1 |
| 20040189509 | Lilleness et al. | Sep 2004 | A1 |
| 20040210933 | Dresti | Oct 2004 | A1 |
| 20040246165 | Conway et al. | Dec 2004 | A1 |
| 20040263349 | Haughawout et al. | Dec 2004 | A1 |
| 20040266419 | Arling et al. | Dec 2004 | A1 |
| 20040268391 | Clercq et al. | Dec 2004 | A1 |
| 20050024226 | Hayes et al. | Feb 2005 | A1 |
| 20050030196 | Harris et al. | Feb 2005 | A1 |
| 20050052423 | Harris et al. | Mar 2005 | A1 |
| 20050055716 | Louie et al. | Mar 2005 | A1 |
| 20050062614 | Young | Mar 2005 | A1 |
| 20050062636 | Conway et al. | Mar 2005 | A1 |
| 20050066370 | Alvarado | Mar 2005 | A1 |
| 20050073914 | Yabe | Apr 2005 | A1 |
| 20050078087 | Gates et al. | Apr 2005 | A1 |
| 20050080496 | Hayes et al. | Apr 2005 | A1 |
| 20050088315 | Klein et al. | Apr 2005 | A1 |
| 20050094610 | De Clerq et al. | May 2005 | A1 |
| 20050096753 | Arling et al. | May 2005 | A1 |
| 20050097618 | Arling et al. | May 2005 | A1 |
| 20050107966 | Hayes | May 2005 | A1 |
| 20050116930 | Gates | Jun 2005 | A1 |
| 20050134578 | Chambers et al. | Jun 2005 | A1 |
| 20050159823 | Hayes et al. | Jul 2005 | A1 |
| 20050162282 | Dresti | Jul 2005 | A1 |
| 20050179559 | Edwards et al. | Aug 2005 | A1 |
| 20050183104 | Edwards et al. | Aug 2005 | A1 |
| 20050195979 | Arling et al. | Sep 2005 | A1 |
| 20050200598 | Hayes et al. | Sep 2005 | A1 |
| 20050210101 | Janik | Sep 2005 | A1 |
| 20050216606 | Hayes et al. | Sep 2005 | A1 |
| 20050216843 | Masters et al. | Sep 2005 | A1 |
| 20050231649 | Arling | Oct 2005 | A1 |
| 20050258806 | Janik et al. | Nov 2005 | A1 |
| 20050280743 | Dresti et al. | Dec 2005 | A1 |
| 20050283814 | Scott et al. | Dec 2005 | A1 |
| 20050285750 | Hayes et al. | Dec 2005 | A1 |
| 20060007306 | Masters et al. | Jan 2006 | A1 |
| 20060012488 | Hilbrink et al. | Jan 2006 | A1 |
| 20060031400 | Yuh et al. | Feb 2006 | A1 |
| 20060031437 | Chambers | Feb 2006 | A1 |
| 20060031549 | Janik et al. | Feb 2006 | A1 |
| 20060031550 | Janik et al. | Feb 2006 | A1 |
| 20060050142 | Scott et al. | Mar 2006 | A1 |
| 20060055554 | Hayes et al. | Mar 2006 | A1 |
| 20060101498 | Arling et al. | May 2006 | A1 |
| 20060125800 | Janik | Jun 2006 | A1 |
| 20060132458 | Garfio et al. | Jun 2006 | A1 |
| 20060143572 | Scott et al. | Jun 2006 | A1 |
| 20060150120 | Dresti et al. | Jul 2006 | A1 |
| 20060161865 | Scott et al. | Jul 2006 | A1 |
| 20060194549 | Janik et al. | Aug 2006 | A1 |
| 20060200538 | Yuh et al. | Sep 2006 | A1 |
| 20060259183 | Hayes et al. | Nov 2006 | A1 |
| 20060259184 | Hayes et al. | Nov 2006 | A1 |
| 20060259864 | Klein et al. | Nov 2006 | A1 |
| 20060262002 | Nguyen | Nov 2006 | A1 |
| 20060283697 | Garfio | Dec 2006 | A1 |
| 20060288300 | Chambers et al. | Dec 2006 | A1 |
| 20060294217 | Chambers | Dec 2006 | A1 |
| 20070052547 | Haughawout et al. | Mar 2007 | A1 |
| 20070061027 | Janik | Mar 2007 | A1 |
| 20070061028 | Janik | Mar 2007 | A1 |
| 20070061029 | Janik | Mar 2007 | A1 |
| 20070063860 | Escobosa et al. | Mar 2007 | A1 |
| 20070073958 | Kalayjian | Mar 2007 | A1 |
| 20070077784 | Kalayjian et al. | Apr 2007 | A1 |
| 20070097275 | Dresti et al. | May 2007 | A1 |
| 20070136693 | Lilleness et al. | Jun 2007 | A1 |
| 20070156739 | Black et al. | Jul 2007 | A1 |
| 20070178830 | Janik et al. | Aug 2007 | A1 |
| 20070206949 | Mortensen | Sep 2007 | A1 |
| 20070225828 | Huang et al. | Sep 2007 | A1 |
| 20070233740 | Nichols et al. | Oct 2007 | A1 |
| 20070258595 | Choy | Nov 2007 | A1 |
| 20070271267 | Lim et al. | Nov 2007 | A1 |
| 20070279244 | Haughawout et al. | Dec 2007 | A1 |
| 20070296552 | Huang et al. | Dec 2007 | A1 |
| 20080005764 | Arling et al. | Jan 2008 | A1 |
| 20080016467 | Chambers et al. | Jan 2008 | A1 |
| 20080016468 | Chambers et al. | Jan 2008 | A1 |
| 20080042982 | Gates et al. | Feb 2008 | A1 |
| 20080184196 | Kataoka | Jul 2008 | A1 |
| 20080243698 | Tanaka | Oct 2008 | A1 |
| 20080314232 | Hansson et al. | Dec 2008 | A1 |
| 20090300580 | Heyhoe et al. | Dec 2009 | A1 |
| 20100005503 | Kaylor et al. | Jan 2010 | A1 |
| 20100169414 | Pavot et al. | Jul 2010 | A1 |
| 20120036538 | Kudelski et al. | Feb 2012 | A1 |
| 20120128334 | Cheok et al. | May 2012 | A1 |
| 20120274863 | Chardon et al. | Nov 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1399444 | Feb 2003 | CN |
| 1434422 | Aug 2003 | CN |
| 103 438 | Mar 1984 | EP |
| 398 550 | Nov 1990 | EP |
| 1014577 | Jun 2000 | EP |
| 2081948 | Feb 1982 | GB |
| 2175724 | Dec 1986 | GB |
| 2002058079 | Feb 2002 | JP |
| 2002271871 | Sep 2002 | JP |
| 2003087881 | Mar 2003 | JP |
| WO 0169567 | Sep 1991 | WO |
| WO 9934564 | Jul 1999 | WO |
| WO 0034851 | Jun 2000 | WO |
| WO 03045107 | May 2003 | WO |
| WO 03060804 | Jul 2003 | WO |
| WO 2005000003 | Jan 2005 | WO |
| Entry |
|---|
| Ciarcia, S., “Build a Trainable Infrared Master Controller,” Byte, 12(3):113-123. |
| Ciarcia, S., The Best of Ciarcia's Circuit Cellar, pp. 345-354 (1987). |
| Konstan, J. A., “State problems in programming human-controlled devices,” Digest of Tech. Papers of Int. Conf. on Consumer Electronics (ICCE), pp. 122-123 (1994). |
| Radio Shack, Universal Remote Control Owners Manual, pp. 1-19, (1987). |
| “ProntoEdit User Manual”; 2002, http://www.pronto.philips.com/index.cfm?id=241, 85 pages. |
| “Pronto Review”; www.remotecentral.com/pronto/index.html, 3 pages, 2005. |
| Press Release: “Philips Revolutionizes Home Theatre Control”; 1998, 3 pages. |
| Pronto link to downloadable files for components from different manufacturers; http://www.remotecentral.com/files/index.html, 3 pages, 2005. |
| U.S. Appl. No. 12/731,086, filed Mar. 24, 2010. |
| U.S. Appl. No. 13/284,668, filed Oct. 28, 2011. |
| U.S. Appl. No. 13/284,775, filed Oct. 28, 2011. |
| U.S. Appl. No. 11/267,528, filed Nov. 3, 2005. |
| U.S. Appl. No. 11/199,922, filed Aug. 8, 2005. |
| Office Action issued on U.S. Appl. No. 13/284,668 dated Apr. 21, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| 20120249890 A1 | Oct 2012 | US |
