Using HDMI-CEC to identify a codeset
Claim Score by NHIP
Abstract
A home entertainment device eliminates the need to use multiple remote's. The device is connected (by wired and/or wireless links) to electronic consumer devices (ECDs) to be controlled. A user uses a portable display device to view pages served by the device, and thereby to communicate with the device and indirectly control the ECDs. In a first aspect, a HDMI-CEC communication is used to identify a codeset from a codeset database. In a second aspect, the codeset of a remote is identified by serving pictures of remotes to the user. The user selects a picture and the system looks up its codeset. In a third aspect, keys on an illustration of a remote are dragged and dropped to create a new custom remote. In a fourth aspect, the user supplies a digital photograph of a remote. The system performs optical recognition and identifies the type of remote and its codeset.

Term
8.5 yearsto projected expiry
Projected expiry 25 March 2035, counted from filing; an application has no term until it is granted.
- Priority and filed
- Published
- Today
- Projected expiry
8 claims: 3 independent, 5 dependent
- 15Broadest claimClaim Score 74, broad(NHIP)A method comprising:(a) using a HDMI-CEC (High Definition Multimedia-Consumer Electronic Control) communication to identify an IR codeset (Infrared Codeset) for an electronic consumer device (ECD) from a database of IR codesets and to identify an image for a control device for the ECD from a database of images;and (b) causing the image for the control device for the ECD to be displayed.
93 paragraphs in 5 sections, as filed
TECHNICAL FIELD
p-0002This application relates to systems including control devices for performing methods for control of electronic consumer devices.
BACKGROUND INFORMATION
p-0003Consumers purchase many electronic devices for their homes. One device might be a television. The television comes with a remote control, which has various functions, such as on off; channel up and down; volume up and down; and so on. The remote control communicates with the television via an infrared signal. Another electronic consumer device is a DVD player. The DVD player likewise comes with its own remote control with its own shape, button layout, button functions, and text and other characters on the remote. The same can be said for an audiovisual receiver, a cable box, and a game console. Some of these devices may be connected together. For example, the game console can output a video signal that is connected to the audiovisual receiver via S-video. The same can be said for the DVD player. Other methods of same can be said for the DVD player. Other methods of connecting devices can also be used. For example, a cable box may be connected to the audiovisual receiver using a High Definition Multimedia Interface (HDMI) cable. The net result of all of this is that the consumer must have anywhere from two to five or more remote controls, each one being needed to control its respective associated electronic consumer device (ECD). Not only does this make for a lot of clutter in the consumer's home, but it also is confusing to remember which remote goes with which device, and which of the many multitudes of possible choices on each remote the consumer is most interested in.
p-0004A more detailed example <b>20</b> is shown in <figref idrefs="DRAWINGS">FIG. 1</figref>. One remote <b>31</b>, with its own unique button layout, is used to control a television <b>21</b>. Another remote <b>32</b> is used to control an audiovisual receiver <b>22</b>. Another remote <b>34</b> is used to control a game console <b>24</b>, and another remote <b>36</b> is used to control a cable box <b>26</b>. Lastly, another remote <b>38</b> is used to control a DVD player <b>28</b>. Each remote has its own unique button layout, as illustrated schematically in <figref idrefs="DRAWINGS">FIG. 1</figref>.
SUMMARY
p-0005The system of the preferred embodiment eliminates the need to use multiple remote control devices on a regular basis. Instead of needing a multitude of different remote controls, a single browser device (for example, a cellular telephone having a display) can be used. The browser device can illustrate all of the various remotes currently used by the consumer, only one at a time. The illustrated remotes each function in the same manner as the original remotes. By using the browser device, the clutter and the need to keep and locate a number of different remotes is eliminated.
p-0006In one embodiment, the browser device communicates via Wi-Fi with a central function device. The function device has information regarding all the various remote controls needed by the consumer. The function device communicates wirelessly with the browser device and in turn then operates all of the consumer's electronic devices.
p-0007In a first novel aspect, the single-line HDMI-CEC (High Definition Multimedia Interface-Consumer Electronic Control) bus or protocol is used to identify an IR codeset for an electronic consumer device (ECD) from a database of IR codesets. When the ECD is coupled to an AV system via an HDMI cable, the system automatically queries the new ECD using the single-wire HDMI-CEC bus to identify itself. The ECD automatically responds by sending back information across the HDMI-CEC bus. This information is usable to identify the ECD. In one example, the returned information includes a brand name in ACSII format of the ECD, a device type in ASCII format of the ECD, and a model number in ASCII format of the ECD. The system uses the returned information to identify particular IR codeset in the database that is usable to control the ECD. The system then enables an IR remote control device to use the identified codeset to send IR remote control operational signals to the ECD device so that the IR remote control device can control the ECD. The use of HDMI-CEC to identify a codeset is not, however, limited to IR applications but rather also applies to codesets used to generate and detect other wireless remote control operational signals such as, for example, RF remote control operational signals for remote control devices that transmit RF signals.
p-0008In a second novel aspect, illustrations (for example, digital pictures) of a plurality of remote control devices are displayed to a user on a portable display device. The user then uses the portable display device to select one of the illustrations that looks like a remote control device that the user is trying to imitate. When the user selects the illustration, the system uses the user selection to identify an IR codeset for the associated ECD from many IR codesets in a database of IR codesets. In one example, a portable display device such as a PDA, or cellular telephone, or Apple iPhone having a browser communicates with an AV system. The AV system serves the illustrations of the remote control devices, and the portable display device and associated browser displays the illustrations to the user. The user then uses the portable display device and browser to select the illustration of the remote control device that the user wishes to emulate. Alternatively, the portable display device displays illustrations or pictures of ECDs and the user might want to control. The user uses the portable display device to select the picture of the ECD that the user wishes to control. In either case, the portable display device communicates the user selection information back to the system. The system uses the information to identify the IR codeset in the database that controls the ECD (the ECD controlled by the remote control device). In one example, the system then enables the portable display device to use the identified codeset to send IR remote control operational signals to the ECD device so that the portable display device can operate as (imitate) the original remote control device picture selected by the user. By showing the user pictures of ECDs that the user might want to control, the system is usable to emulate a remote control device that the user has lost.
p-0009In a third novel aspect, pictures of a plurality of remote control devices are displayed to a user on a portable display device. The user can use the portable display device to select icons or buttons on the pictures, and to cause functionality of the selected icons or buttons to be associated with another rendering of a remote control device. For example, the user can copy (for example, by “dragging and dropping”) a selected icon or key or button from the pictured remote control device to a template of a remote control device illustrated elsewhere on the portable display device. Both the pictured remote control device and the template remote control device are displayed on the portable display device. As the user “drags and drops” icons or keys or buttons, the icons or keys or buttons are added to and appear on the template. In this way, icons or keys or buttons from multiple different pictured remote control devices can be dragged and dropped onto the same template, and the functionalities associated with the original icons, key and buttons in the pictured remote control devices are automatically assumed by the associated new icons or keys or buttons on the template. Using this feature, the user builds a new custom hybrid remote control device, a rendering of which can be displayed on the portable display device. When the user later selects an icon or key or button on the hybrid remote control device, the portable display device performs the function that the original pictured remote control device that had the same key would have performed.
p-0010In a fourth novel aspect, the user takes a digital picture of a remote control device to be imitated, and this picture is communicated to a system. The system performs optical recognition on the digital picture. In one example, a user has a portable display device such as a PDA, or cellular telephone, or Apple iPhone that has a camera functionality. The user uses the portable display device to take a digital picture of an IR remote control device. The display device then communicates the digital picture (for example, in the form of a JPEG file) to the system. The system performs optical object recognition on the digital picture and identifies which one of a plurality of codesets in a database of codeset is the codeset for the remote control device in the digital picture. The database may, for example, contain information on what the various remote control device look like so that the optical recognition results will be usable to identify the pictured remote control device. This information may include information on the shape of the contour of the remote control device, the number of keys and placement of keys on the remote control device, and text that is printed on the remote control device. Once the system has identified the codeset associated with the pictured remote control device, the system communicates back to the portable display device such that the portable display device is enabled to use the identified codeset to send IR remote control operational signals in accordance with the codeset. In this way, a user may use the portable display device to take a picture of a remote control device that operates a particular ECD. The system then responds by enabling the portable display device to emulate the remote control device. A picture or rendering of the emulated remote control device may thereafter be displayed on the portable display device. When the selects an icon or key or button on this picture or rendering, the portable display device performs the same function that the original remote control device would have performed.
p-0011In another example, the internet-accessible computer system receives from a user a digital image of an electrical device via the internet. The electrical device may, for example, be a remote control device or an electronic consumer device (ECD) that is controlled by a remote control device. The internet-accessible computer system then automatically performs optical object recognition on the digital image, and charges the user a fee to return information obtained from the optical recognition. The returned information may, for example, be codeset information.
p-0012Further details and embodiments are described in the detailed description below. This summary does not purport to define the invention. The invention is defined by the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
p-0013The accompanying drawings, where like numerals indicate like components, illustrate various embodiments.
p-0014<figref idrefs="DRAWINGS">FIG. 1</figref> (Prior Art) is a diagram of a collection of various electronic consumer devices, including various means of communication.
p-0015<figref idrefs="DRAWINGS">FIG. 2</figref> is a schematic illustration of a system for communicating with electronic consumer devices.
p-0016<figref idrefs="DRAWINGS">FIG. 2A</figref> is a schematic illustration of a system for communicating with electronic consumer devices, where a device includes among other parts: the functionality of the function device of <figref idrefs="DRAWINGS">FIG. 2</figref>, the records database of <figref idrefs="DRAWINGS">FIG. 2</figref>, a speaker, a display output, and a signal output <b>125</b>.
p-0017<figref idrefs="DRAWINGS">FIG. 3</figref> is a schematic illustration of a database including a plurality of records regarding various remote controls, including a schematic illustration of some of the detail included in each of the records.
p-0018<figref idrefs="DRAWINGS">FIG. 4</figref> is an illustration of various control devices used for controlling electronic consumer devices.
p-0019<figref idrefs="DRAWINGS">FIG. 5</figref> is an illustration of other control devices for controlling electronic consumer devices including a device for controlling lights that may be turned on or off or dimmed or brightened.
p-0020<figref idrefs="DRAWINGS">FIG. 6</figref> is a schematic illustration of a display device illustrating a picture of a remote control with a user's finger on one of the illustrated buttons.
p-0021<figref idrefs="DRAWINGS">FIG. 7</figref> is an illustration of a display device including buttons that cause a collection of changes in the function of electronic consumer devices, based on the different interests or moods of the user.
p-0022<figref idrefs="DRAWINGS">FIG. 8</figref> is a diagram of a display with an illustration of a possible main menu that permits a user to select various functions.
p-0023<figref idrefs="DRAWINGS">FIG. 9</figref> is an illustration of a method of how a consumer can set up the system to control electronic consumer devices.
p-0024<figref idrefs="DRAWINGS">FIG. 10</figref> is a schematic illustration of how possible choices available to a user can be limited.
p-0025<figref idrefs="DRAWINGS">FIG. 11</figref> is an illustration of a method of using a digital image to narrow down the possible choices of which particular device for consumers interested in.
p-0026<figref idrefs="DRAWINGS">FIG. 12</figref> is a flowchart showing how a consumer can obtain a digital image of a particular device, and then use that image to identify a specific database record referencing that particular control device.
p-0027<figref idrefs="DRAWINGS">FIG. 13</figref> illustrates how a custom device screen can be created.
p-0028<figref idrefs="DRAWINGS">FIG. 14</figref> illustrates a resulting smaller custom device screen.
p-0029<figref idrefs="DRAWINGS">FIG. 15</figref> illustrates a possible device button layout that can be programmed for a particular control device of interest.
p-0030<figref idrefs="DRAWINGS">FIG. 16</figref> an illustration of a template custom control device with existing buttons, where the user then assigns a button function to each of the buttons on the template.
p-0031<figref idrefs="DRAWINGS">FIG. 17</figref> is a schematic illustration of a function device.
p-0032<figref idrefs="DRAWINGS">FIGS. 17A through 17M</figref> illustrate the details of the components that make up the function device shown in <figref idrefs="DRAWINGS">FIG. 17</figref>.
DETAILED DESCRIPTION
p-0033The drawings illustrate a system for controlling electronic consumer devices (ECDs). Household ECDs, as used in this description, can be anything that can be controlled by a remote control device or a keypad or some other control device, such as a DVD, a television, an audiovisual receiver, a sprinkler system, a light switch, an alarm panel, a game console, a computer, and so on.
p-0034Overview
p-0035<figref idrefs="DRAWINGS">FIG. 2</figref> is one embodiment of a system <b>100</b> for controlling electronic consumer devices (ECDs). System <b>100</b> includes a function device <b>101</b>, a display <b>102</b>, a plurality of ECDs <b>103</b>-<b>111</b>, a database <b>112</b> and a memory <b>113</b>. Database <b>112</b> and memory <b>113</b> are accessible via a network connection <b>131</b> to a network such as the internet <b>115</b>. The ECDs <b>103</b>-<b>111</b> include, in this example, a light switch <b>103</b>, a heating ventilation and air conditioning (HVAC) controller <b>104</b>, sprinkler system controller <b>105</b>, an alarm system controller <b>106</b>, a DVD player <b>107</b>, a set-top box <b>108</b>, an audio-visual receiver <b>104</b> (sometimes also referred to as an “audio-video receiver” or “AV receiver”), a game console <b>110</b>, and a television <b>111</b>. In other embodiments, more or fewer ECDs may be present.
p-0036Function device <b>101</b> communicates with the database <b>112</b>. In one example, the database <b>112</b> is a database of codesets. For details on an example of a codeset and what a codeset entails and how a codeset is used, see: U.S. Pat. No. 7,259,696, the subject matter of which is incorporated herein by reference. Database <b>112</b> includes information on the identities of many different types of ECDs, and information on the functions of each ECD. These functions may, for example, be volume up or down, channel up or down, turn on sprinkler, etc., which can be controlled by a remote control device. The ECD manufacturer usually supplies such a remote control device at the time the ECD is originally sold to consumers. How to generate the various signals needed to be received by the ECD in order to make the ECD perform a desired function is set forth in database <b>112</b>.
p-0037In a further example, database <b>112</b> is or includes a pictorial record database of illustrations of remotes or control devices with buttons that are used to control the ECD functions. The term “illustration” as it is used here includes both digital photographs and schematic renderings. The term “control device” as it is used here encompasses, but is not limited to, a remote control device.
p-0038In a further example, in addition to an illustration of the control device, database <b>112</b> includes extracted graphical information on each control device. Such extracted graphical information may, for example, include information on the shape of the control device, the buttons (keys) on the control device, the number of buttons and the locations of the buttons, and characters or other printing that appears on the control device. The database also includes the ECD function information (keycodes and other codeset information) associated with each button.
p-0039Central function device <b>101</b> communicates with the database <b>112</b> to obtain the control device's information, such as the devices shape, devices button labels, button shapes, and the button locations i.e., the button layout. Function device <b>101</b> also includes a display output <b>116</b> that outputs a signal to a display device <b>102</b>. Display device <b>102</b> displays an input screen that illustrates the control device's information, such as the device's shape, button labels, button shapes and button locations or layout.
p-0040Although function device <b>101</b>, database <b>112</b>, memory <b>113</b> and display device <b>102</b> are illustrated in <figref idrefs="DRAWINGS">FIG. 2</figref> as separate devices or functionalities, in another embodiment (see <figref idrefs="DRAWINGS">FIG. 2A</figref>) some or all of these system elements can be combined into a single device. In one example (not shown), the function device <b>101</b> is functionality that is physically incorporated (not shown) into one of the ECDs, such as the cable set-top box <b>108</b>. More particularly, a processor can provide some or all of the function device's functionality. The term “processor” as the term is used herein is a digital processing unit such as a microcontroller or microprocessor, along with its associated functional hardware and software. The term includes a microprocessor such as is normally found in a personal computer, and its functional software.
p-0041In one example of operation of system <b>100</b>, a consumer (not shown) purchases a new ECD. The consumer takes the new ECD home, and plugs it into an existing home entertainment/ECD system. For example, if the ECD were a set-top box, such as a cable box, a consumer can connect a cable wire to the box, and then connect the box to an audio-visual system. If the system includes an AV receiver, the consumer might use a high-definition media interface (HDMI) cable to connect the cable box to the AV receiver, as further explained-below. Once connected into system <b>100</b>, the following would occur. In this example, the cable box includes a novel function device. The function device within the cable box begins to recognize the various ECDs in the consumer's home system. For example, the function device can determine the manufacturer, type, and particular model of the AV receiver using the CEC protocol over the HDMI cable. Once the identity of the AV receiver is determined, the function device then communicates with the database <b>112</b> that includes information about the various control devices. By communicating to database <b>112</b> the particular identity of the AV receiver, the database can use the identity information to identify information associated with the particular control device normally supplied to the consumer when the AV receiver is sold. Using the ECD identity information, database <b>112</b> returns to the function device in the cable box that particular ECD function information. In some embodiments, it also returns an illustration of the control device supplied by the ECD device manufacturer at the time the ECD is sold to consumers.
p-0042Not all ECDs have an ability to communicate via HDMI with the function device. In the case of these other ECDs, the consumer may identify the ECD for the function device. Using a setup procedure, as further explained below, the consumer identifies the other ECDs in the consumer's home entertainment/ECD system.
p-0043Once all of the ECDs in the system have been identified, the consumer can then use a single display device (for example, display <b>102</b>) with two-way communication to the function device to control all of the ECDs, as further explained below.
p-0044Display Device
p-0045More particularly, as illustrated in <figref idrefs="DRAWINGS">FIG. 2</figref>, display <b>102</b> is a mobile communication device that has a touch screen <b>114</b>. Display <b>102</b> can respond to a user interacting with the input screen <b>114</b>. For example, when the screen <b>114</b> displays a button <b>130</b>, and the user can interact with the button <b>130</b>. If the display <b>102</b> is a multi-touch screen, the display <b>102</b> can react to a user touching the button <b>130</b> on the screen <b>114</b>. In other less preferred embodiments, a user may use a keyboard (not shown) to tab between buttons and touch a key in order to interact with the button, or the user can use a mouse (not shown) to mouse over each button and click to interact with the button. There are many different ways for users to interact with an input screen on a display, all of which are considered possible embodiments.
p-0046As a result of the user interaction with the input screen, the user input is communicated to function device <b>101</b>, and function device <b>101</b> takes the information from the button function information database <b>112</b> and uses it to create a signal with the control devices button function information. This signal is then output through a signal output to the ECD to be controlled. In one case, the signal output is an IR transmitter, and the signal is an infrared transmission. In other case, the signal output is an HDMI port, and the signal is an HDMI communication that is communicated to the ECD to be controlled by an HDMI cable.
p-0047Communication Between Display Device and Function Device
p-0048The function device <b>101</b> can communicate with the display <b>102</b> in many ways. For example, if display <b>102</b> is physically located (not shown) in the same device housing as functional device <b>101</b>, then a data bus can communicate between the display and the function device <b>101</b>. If the display is physically located in a separate device in a separate housing, as shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, other means for communicating between the display and the function device <b>101</b> are required. In one example (not shown), the display is hard wired to the function device <b>101</b>. In another example, as shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, the display communicates wirelessly with the function device <b>101</b>. While all methods of wireless communication can be used, a preferred method of communication is to use Wi-Fi. In other embodiments (not shown) a cellular network can be used for communication between the function device <b>101</b> and the display <b>102</b>. Other methods of communication can include using coaxial cable, like an RF signal, and an HDMI cable, including using consumer electronic communication (CEC). The communication between the display device <b>102</b> and the function device <b>101</b> can be one-way or two-way communication. For example, for two-way communication, the function device <b>101</b> can output the input screen information to the display device, and the display device can return to the function device <b>101</b> information about user interaction.
p-0049The display device can take many forms. It could be a television, a personal computer, or a smart phone or smart device such as an Apple Inc. iPhone or iPod Touch, both of which have Wi-Fi communication capabilities. With Wi-Fi communication capabilities; the display device can interact using Wi-Fi with the function device <b>101</b>.
p-0050Communication Between Function Device and Databases
p-0051Function device <b>101</b> communicates with the button function information database and the database with pictorial records of other devices. These databases can be stored in a database server within the function device <b>101</b>, or the database can be located remote from function device <b>101</b>. For example, if the database is on the Internet, then communication with the Internet can permit the function device <b>101</b> to communicate with the database. Such communication could be over each Ethernet cable through a modem to a remotely located database server.
p-0052Memory
p-0053In some instances, user input needs to be recorded. For example if the user of display device <b>102</b> selects, as explained below, a particular control device, then the function device <b>101</b> will want to retain this information. As a result, the function device <b>101</b> will need to communicate with memory to retain this information. So the function device <b>101</b> will include some form of memory. The memory may be physically within the same device housing as the function device <b>101</b>, or it may be located remotely from the function device <b>101</b>. If located remotely, then some form of communication will need to occur between the function device <b>101</b> and the remote memory in order to retrieve the user interaction information. The communication between the memory and the function device <b>101</b> can be over a data bus, if located in the same physical housing, or can be over network communication, if located remote from the function device <b>101</b>. If located remotely, then any of the previously described methods of communication can be used.
p-0054Page Server
p-0055In order to display the input screen on display device <b>102</b>, function device <b>101</b> creates an input screen output. In the preferred embodiment, the input screen is a page in a plurality of linked pages. The function device <b>101</b> serves the pages using HTML. In other embodiments, other methods, such as by using a stand-alone application to create the input screen can be used. In the preferred embodiment, a browser executing in display device <b>102</b> is used to render the input screen on the display of display device <b>102</b>. Since the user will interact repeatedly with the input screen, it is beneficial if the web browser on the display device supports HTML and user interaction with the HTML. More particularly, in the preferred embodiment, the web browser should support JavaScript to permit user interaction with a button without having to refresh the entire user input screen, or some other form of AJAX (Asynchronous JavaScript and XML) process. Still more particularly, in a preferred embodiment, the display device <b>102</b> should support enlargement of any illustration on the display, as shown in <figref idrefs="DRAWINGS">FIG. 6</figref>.
p-0056The page server can be either software processed by the same function device <b>101</b> referred to above, or the web server can be located remotely from the function device <b>101</b>. For example, the web server can be on a network web server, and the function device <b>101</b> can communicate with the networked web server. The term “web server” as it is used here is not limited to use on the World Wide Web, but rather is a page server of linked pages, regardless of whether the pages are part of the World Wide Web or whether the pages are only locally accessible.
p-0057Function Device and ECD Communication
p-0058As mentioned earlier, function device <b>101</b> communicates with various ECDs. The communication can use any of the above-described methods of communicating a signal, such as using infrared Wi-Fi, HDMI, CEC and/or RF. Another form of communication between the function device <b>101</b> in the ECDs may be a zWave, or Zigbee, which is a known method of communication between household ECDs such as light switches and devices for its controlling the light switch. In many cases, the communication will be one way. For example, the function device <b>101</b> can cause a television to turn on. Or function device <b>101</b> can tell the television volume to increase. In other circumstances, two-way communication can occur between function device <b>101</b> and the ECD. For example, if communicating over HDMI or zWave, a signal to turn on can be communicated to a light switch, and some sort of response indicating the light did in fact turn on can be returned to function device <b>101</b>, so that the user can confirm that the light was turned on. In still other examples, as described below, the existence of a particular ECD may be communicated to function device <b>101</b> through such two-way communication. Other methods of communication can also include X10 and RS-485, as illustrated in <figref idrefs="DRAWINGS">FIG. 17</figref>.
p-0059Mood Buttons
p-0060In addition to merely responding to user input regarding button interaction, the system can also handle more complicated actions. For example, a combination of many button functions can occur in response to the user interaction with one particular button. For example, a user can in the morning turn on various ECDs. Lights can be turned on, and a coffee pot started. For example, one button labeled MORNING, as illustrated in <figref idrefs="DRAWINGS">FIG. 7</figref>, can be used on the display device to cause these various different ECD function commands to be output by the function device <b>101</b>, in response to the user interacting with the MORNING button on the display device.
p-0061Pictorial Database
p-0062Referring again to the database that contains the pictorial records, an example database <b>120</b> is illustrated in <figref idrefs="DRAWINGS">FIG. 3</figref>. Database <b>120</b> includes records <b>124</b> for different control devices, and each record <b>124</b> includes information on the control device's shape, the button layout of the control device, and the button labels and other text that can appear on the control device. Each record <b>124</b> also includes the code <b>126</b> or signals associated with each button <b>128</b> on the control device <b>124</b>. These codes may, for example, be referred to as keycodes.
p-0063<figref idrefs="DRAWINGS">FIG. 4</figref> illustrates a sample selection of device shapes and button layouts. Various pieces of text (such as the ECD manufacturer, as best seen in <figref idrefs="DRAWINGS">FIG. 14</figref>) also appear in various locations on each device. In addition to such text, various symbols also appear on each device, either on the buttons or otherwise. The pictorial database includes this information regarding the symbols, the buttons, the shapes of the buttons, the button locations, and the shape of the overall control device. In other less preferred embodiments, a subset of this information can be used.
p-0064Types of Control Devices
p-0065The pictorial database includes information on many different kinds of other devices. For example, reference can be made to <figref idrefs="DRAWINGS">FIGS. 5A and 5B</figref> illustrating various sample control devices used for control of ECDs, such as a DVD, cable box, a DVD player, and a television. Other ECDs include, for example, referring to the Figure illustrating other control devices, an alarm system, and HVAC control, as well as a light switch wall plate.
p-0066Types of ECD Interaction and Display Response
p-0067In regard to lights, lights can be turned on or off or dimmed or brightened. In addition to having the buttons merely respond to user input, the buttons can also change color or otherwise respond to user interaction. For example, if a light is turned on, a button on display device <b>102</b> can change color to indicate that the light is on.
p-0068Main Input Screen
p-0069The main input screen shown on the display device can permit a user to select generally the category of user desired ECD interaction. An example of a main input screen is shown in <figref idrefs="DRAWINGS">FIG. 8</figref>. The user can select which type of ECD to use. In addition, the user can select various custom control devices, created as explained below. In addition, the user can choose to build a new custom control device, to teach the device to learn how to behave like an existing control device, or to set up the function device <b>101</b>, as explained below.
p-0070IR Learning
p-0071In addition to the function device <b>101</b> communicating with a database of pictorial records and other button information, the system can also learn a particular control device's button function information. This can be done using an IR learning process, as commonly known in the art.
p-0072System Setup
p-0073An important aspect of the system of <figref idrefs="DRAWINGS">FIG. 2</figref> is the ability of the system to permit easy setup of the system. Setup as used herein means the selection of the choice of control devices to be imitated. An example of a setup procedure, as illustrated in <figref idrefs="DRAWINGS">FIG. 10</figref>, is as follows. Function device <b>101</b> outputs a user input screen to display device <b>102</b>. The input screen, as rendered on the display of display device <b>102</b>, presents the user with a choice of a one of the following criteria: a control device's shape, a control device manufacturer, a control device type of ECD to be controlled, and a selection of other device button layouts. The user interacts with the input screen to select one of the criteria. Display device <b>102</b> then communicates with function device <b>101</b>, and the function device <b>101</b> communicates with the device pictorial database to reduce the number of other devices of interest to the user. For example, if the user selects the manufacturer “Sony” from a list of ECD manufacturers presented to the user, then only Sony devices would be available to the user for further selection. More particularly, as illustrated in <figref idrefs="DRAWINGS">FIG. 11</figref>, the second criterion will depend on the first criterion selected by the user. For example, if ECD type, such as DVD or television or receiver, was selected as the first criterion, than a second choice presented to the user may be a list of ECD manufacturers. Another option would be to show a selection of button layouts for other devices, or to show the shapes of other devices. When the second criterion is then selected, the display device <b>102</b> will communicate again with function device <b>101</b>, which in turn will communicate with the device database. As a result of the narrower criterion, the set of possible choices presented to the user will be further narrowed. The set of possible choices is then returned to the function device <b>101</b>, and the function device <b>101</b> creates an input display screen with a more limited selection choices. The user interacts with the user input screen to select a particular device of interest to the user. If, in the first instance, the user selected device manufacturer, then the second criterion may be to show the types of ECDs made by that manufacturer. In the alternative, after selecting a device manufacturer, the second criteria may be button layouts of devices made by that manufacturer, or the shapes of such devices. Likewise, if device shape is the first criterion, then the second criterion can be either a button layout or the device manufacturer or the type of ECD.
p-0074Processing the Selected Device
p-0075Once a particular control device is selected, then display device <b>101</b> communicates the device selection to the function device <b>101</b>. Function device <b>101</b> in turn communicates with the device pictorial record database to return to the function device <b>101</b> a pictorial record for the selected device. The pictorial record shows the control device shape, the button layout on the control device, and any text that appears on the control device. Function device <b>101</b> also obtains all of the button function information from the button information database. The button function database referred to here is sometimes referred to as a codeset database. The button information database can be the same database as the pictorial database, or it may be another database.
p-0076Once function device <b>101</b> has obtained all necessary the information about the control device to imitate the control device, an illustration of the control device is output, via the page server, to the display device along with codeset information and/or other information usable to imitate the original control device. The illustration appears on the user input screen that is displayed on the display device. The user then can interact with the buttons on the user input screen to select various device functions of the control device.
p-0077Using Communication With an ECD to Identify a Control Device
p-0078Another method of obtaining information about what ECDs the user wants to control involves having function device <b>101</b> output a communication query signal across the HDMI-CEC bus to any newly connected ECDs, as shown in <figref idrefs="DRAWINGS">FIG. 9</figref>. The newly connected ECD automatically responds by communicating back ECD identification information across the CEC bus. This ECD identification information may include a brand name in ASCII characters, a device type in ASCII characters, and a model number in ASCII characters. Function device <b>101</b> parses and interprets this returning ECD identification information, and then forwards some or all of it, or a determination based on it, to the control device pictorial database. The pictorial database returns an illustration of the associated control device, which is forwarded to display device <b>102</b> so an image of the control device is displayed to the user on display device <b>102</b>.
p-0079Using an Image of a Control Device to Identify a Control Device
p-0080Another method of obtaining information from a user regarding a particular control device to be imitated by the system, is to begin with a digital photograph of the control device to be imitated, as illustrated in <figref idrefs="DRAWINGS">FIGS. 11 and 12</figref>. The user can obtain this digital photograph (image) using a digital camera. For example, the Apple iPhone has a digital camera built into the smart phone. Once the digital camera captures an image of the control device to be imitated (for example, as a JPEG file), the image is communicated to the function device <b>101</b> using any suitable method of communication. With an Apple iPhone, the image could be transferred via Wi-Fi to the function device <b>101</b>. In one particular embodiment, display device <b>102</b> is a cellular telephone having a camera functionality, and the cellular telephone is used to capture a digital image and to transmit the digital photograph to function device <b>101</b>.
p-0081Function device <b>101</b> then analyzes the digital photograph (image) or communicates with another function device <b>101</b> that analyzes the digital photograph or image. The analyzing function device typically uses optical recognition techniques to analyze one of more of the following characteristics of the image: the shape of the outer contour of the pictured control device, the location and number of buttons on the pictured control device, the characters or text appearing on the buttons, and any characters or text of other printing that appears on the control device. Any one or all of the above pieces of extracted graphical information can be extracted from the raw digital photograph. This information can be obtained from the digital image using known optical recognition approaches, or by using techniques used with facial recognition, for example. Once the graphical information has been extracted using optical recognition, the extracted information is communicated to a database that includes similar types of previously extracted graphical information about other control devices. Based on such extracted graphical information, a particular control device in the database is selected as the best match. After the particular control device has been selected, information particular to the particular control device is communicated back to the function device <b>101</b>. Function device <b>101</b> may forward the information to display device <b>102</b>.
p-0082More Particulars Regarding What is analyzed in the Digital Image
p-0083By referring to <figref idrefs="DRAWINGS">FIG. 4</figref> illustrating a sample selection of control device shapes and button layouts, it can be observed that often control devices have unique shapes. For example, in <figref idrefs="DRAWINGS">FIG. 4B</figref>, one remote has a tear drop type of shape. The control device in <figref idrefs="DRAWINGS">FIG. 4D</figref> has a relatively straight sided shape with parallel sides, but with rounded ends. The device in <figref idrefs="DRAWINGS">FIG. 4A</figref> has straight parallel sides and relatively straight parallel ends, while the device in <figref idrefs="DRAWINGS">FIG. 4C</figref> has a rounded contour in the middle of the device, which makes it readily distinguishable from the control devices. This device shape information can be used by the optical recognition software executing in function device <b>101</b> to identify a particular control device. In addition, by referring to this same figure, one can observe various characters on the devices. In some instances, the characters identify the device manufacturer. This information can be used to select or narrow down the particular devices of interest. In addition, the button layout, and the symbols on the buttons, as illustrated in this figure, can also be used.
p-0084Device Operation
p-0085Once the narrowing down process has concluded and a particular control device has been identified, an illustration of the identified control device is made to be displayed on display device <b>102</b> and the user can interact with the control device illustration to select a control device button to create a signal to control an ECD function. Once the user has identified multiple such control devices (for example, that might be usable to operate various different ECDs in the user's home), the user can then interact with the illustrations of the control devices to imitate the operation of the control devices. When the user selects a particular button on an illustration, for example, the display device communicates with the function device <b>101</b>, telling the function device <b>101</b> what button was selected. The function device <b>101</b> then outputs a signal to a signal output, which, for example, can be an IR emitter, that then emits the appropriate IR code for that function for that particular ECD, so that the particular ECD can respond to that command. Alternatively the signal output is a hardwired bus port such as, for example, an HDMI port into which an HDMI cable is plugged.
p-0086Custom Control Device Creation
p-0087In addition to permitting the user to interact with ECDs by using illustrations of the control devices typically used to control such ECDs, the system of <figref idrefs="DRAWINGS">FIG. 2</figref> offers the creation of a custom control device. A custom control device is one that realized a selection of button functions from multiple different control devices. To create such a custom control device, the function device <b>101</b> outputs at least one collection of button information from one of the control devices of interest to the user. In the preferred embodiment, the original button layout, including the shape of the control device, is displayed on the user input screen, as illustrated in <figref idrefs="DRAWINGS">FIG. 14</figref>. The user then interacts with the buttons on the user input screen, by either selecting a button, choosing a menu option or other control that says use such button, or, in the preferred embodiment, by dragging and dropping the illustrated button to another location on the input screen. In this manner, the user makes that particular button part of the custom control device illustration <b>140</b>. By then continuing to choose various buttons, these various buttons and button functions are added to the custom control device. In the end, the custom control device includes a collection of buttons and button functions from the depicted other control devices of interest to the user. After completing the building or creating of the custom control device, a done or finish button <b>142</b> is selected by the user, and this user input is communicated to the function device <b>101</b>. The function device <b>101</b> then creates the custom control device illustration. The custom control device illustration is then output to the display device.
p-0088In one embodiment, as illustrated in <figref idrefs="DRAWINGS">FIG. 14</figref>, the custom control device buttons used to control a television, for example, can be the buttons used to control the television in a custom control device area labeled TV. Likewise, the buttons used to control a cable set-top box could be gathered in a custom control device location entitled Cable. To build the custom control device, the user drags and drops selected buttons from the illustrations appearing to the right in <figref idrefs="DRAWINGS">FIG. 14</figref>. These selected buttons are dropped in the area illustrated to the left in <figref idrefs="DRAWINGS">FIG. 14</figref>.
p-0089By including only particular buttons of interest to the user on the custom control device, the custom control device offers a simpler device for control of ECDs. In the preferred embodiment, the custom control device ends up with an illustration of buttons, as shown in <figref idrefs="DRAWINGS">FIG. 15</figref>, which is much more compact in size than the original shape of the various other devices of interest to the user. This permits the button sizes to be larger, making it easier for user interaction. This also simplifies the amount of information the user has to deal with in order to interact with the various ECDs.
p-0090Assigning Functions to Custom Control Device Buttons
p-0091In <figref idrefs="DRAWINGS">FIG. 16</figref>, another approach to custom control device creation is illustrated. In this procedure, the user input screen begins with a template custom control device with existing buttons. The user then assigns various button functions to each of the buttons on the template custom control device. This is done in a fashion similar to the description of selection of buttons referred to earlier. The control device of interest to the user is illustrated, and the user drags and drops buttons of interest from the illustrated control device to the template custom control device, thereby assigning functions of the selected buttons to the buttons on the custom control device. As shown in <figref idrefs="DRAWINGS">FIGS. 15 and 16</figref>, the resulting custom control device input screens are much simpler than the original, relatively busy, control devices.
p-0092Function Device Construction
p-0093The function device <b>101</b> can include various components. These components may be housed in one housing, or in separate housings with communication between the various housings. In the embodiment in <figref idrefs="DRAWINGS">FIG. 17</figref>, the function device <b>101</b> includes a power source, a fan control, a RS-232 port, and a general-purpose processor board. The function device <b>101</b> also includes flash memory, z-Wave, X10 and RS-485 wireless communication, and IR learning. The function device <b>101</b> also includes IR outputs, HDMI ports, and a level shifter. The function device <b>101</b> also includes Wi-Fi inputs and outputs, SRAM, RS485, an Ethernet router, and an X10 TW523. The particulars regarding these various components are illustrated in <figref idrefs="DRAWINGS">FIGS. 17A through 17M</figref>.
p-0094Although certain specific exemplary embodiments are described above in order to illustrate the invention, the invention is not limited to the specific embodiments. The use of an HDMI-CEC communication to identify a remote control device usable to control an ECD, or to identify a codeset usable to control an ECD, has general applicability. The use of a digital photograph of a remote control device (and/or of an ECD controllable by the remote control device) to identify information about the remote control device (and/or about the ECD) has general applicability. For example, a web-based service can receive a digital photograph via the internet, can perform optical recognition on the digital photograph and use the results of the optical recognition to identify information in a database about the remote control device and/or an ECD controllable by the remote control device. The identified information can be returned to the user via the internet and the user can be billed for the service. Accordingly, the lookup function performed by function device <b>101</b> and database <b>112</b> need not be localized to a user's home. The storage of digital images of remote control devices in a codeset database has general applicability, and does the storage of extracted graphical information about remote control devices in the codeset database. Accordingly, various modifications, adaptations, and combinations of various features of the described embodiments can be practiced without departing from the scope of the invention as set forth in the claims.
Contents5
31 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11635786B2 | Cited by | United States of America | Applicant |
| US8897897B2 | Cited by | United States of America | Search report |
| US2012068857A1 | Cited by | United States of America | Pre-grant |
| US2017215028A1 | Cited by | United States of America | Pre-grant |
| US2012303138A1 | Cited by | United States of America | Pre-grant |
| US2012176405A1 | Cited by | United States of America | Pre-grant |
| US2015304797A1 | Cited by | United States of America | Pre-grant |
| US2022027119A1 | Cited by | United States of America | Search report |
| US10795460B2 | Cited by | United States of America | Applicant |
| US8929877B2 | Cited by | United States of America | Search report |
| US9310787B2 | Cited by | United States of America | Applicant |
| US10003763B2 | Cited by | United States of America | Applicant |
| US9491392B2 | Cited by | United States of America | Applicant |
| US10431074B2 | Cited by | United States of America | Search report |
| US12148291B2 | Cited by | United States of America | Search report |
| US12273618B2 | Cited by | United States of America | Applicant |
| US2012119998A1 | Cited by | United States of America | Pre-grant |
| US9247177B2 | Cited by | United States of America | Applicant |
| US9800818B2 | Cited by | United States of America | Search report |
| US9437102B2 | Cited by | United States of America | Search report |
| US11930270B2 | Cited by | United States of America | Applicant |
| US2014240104A1 | Cited by | United States of America | Pre-grant |
| US10055030B2 | Cited by | United States of America | Applicant |
| CN103716653A | Cited by | China | Search report |
| US10045064B2 | Cited by | United States of America | Search report |
| US9582994B2 | Cited by | United States of America | Applicant |
| US11983035B2 | Cited by | United States of America | Applicant |
| US9558654B2 | Cited by | United States of America | Search report |
| US2012297419A1 | Cited by | United States of America | Pre-grant |
| US10075665B2 | Cited by | United States of America | Search report |
| US11353969B2 | Cited by | United States of America | Applicant |
| US12082768B2 | Cited by | United States of America | Applicant |
| US9627163B2 | Cited by | United States of America | Applicant |
| US10698648B2 | Cited by | United States of America | Search report |
| US10198236B2 | Cited by | United States of America | Search report |
| US9565512B2 | Cited by | United States of America | Search report |
| US2014167933A1 | Cited by | United States of America | Pre-grant |
| US9454899B2 | Cited by | United States of America | Search report |
| US2022262235A1 | Cited by | United States of America | Search report |
| US9367144B2 | Cited by | United States of America | Search report |
| US9430129B2 | Cited by | United States of America | Search report |
| US11144274B2 | Cited by | United States of America | Search report |
| US2023152947A1 | Cited by | United States of America | Search report |
| CN108322798A | Cited by | China | Search report |
| US8339416B2 | Cited by | United States of America | Search report |
| US11587432B2 | Cited by | United States of America | Applicant |
| US2014282044A1 | Cited by | United States of America | Pre-grant |
| US2014167932A1 | Cited by | United States of America | Pre-grant |
| US10231027B2 | Cited by | United States of America | Search report |
| US2014096030A1 | Cited by | United States of America | Pre-grant |
| US9753436B2 | Cited by | United States of America | Applicant |
| US2016124402A1 | Cited by | United States of America | Pre-grant |
| US9918183B2 | Cited by | United States of America | Search report |
| US2014218182A1 | Cited by | United States of America | Pre-grant |
| GB2542777A | Cited by | United Kingdom | Search report |
| US11269376B2 | Cited by | United States of America | Applicant |
| US9886845B2 | Cited by | United States of America | Applicant |
| US2019377587A1 | Cited by | United States of America | Search report |
| US2016191838A1 | Cited by | United States of America | Pre-grant |
| US2012071989A1 | Cites | United States of America | Pre-grant |
| US7653212B2 | Cites | United States of America | Pre-grant |
183 members in 11 offices; this record represents the family
Members183
| Document | Office | Kind | |
|---|---|---|---|
| US2007052547A1 | United States of America | A1 | |
| WO2007030540A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007030540A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP1929732A2 | European Patent Office (EPO) | A2 | |
| EP1929732A4 | European Patent Office (EPO) | A4 | |
| US2010207778A1 | United States of America | A1 | |
| US7907222B2 | United States of America | B2 | |
| US2011102158A1 | United States of America | A1 | |
| US2011133906A1 | United States of America | A1 | |
| US7969514B2 | United States of America | B2 | |
| WO2011079189A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US2011289113A1 | United States of America | A1 | |
| US2012041925A1 | United States of America | A1 | |
| US2012071989A1 | United States of America | A1 | |
| US2012086563A1 | United States of America | A1 | |
| US2012194325A1 | United States of America | A1 | |
| US2012200400A1 | United States of America | A1 | |
| WO2012112197A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CN102667647A | China | A | |
| US2012242526A1 | United States of America | A1 | |
| WO2012134681A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2012134732A1 | World Intellectual Property Organization (WIPO) | A1 | |
| EP2517077A1 | European Patent Office (EPO) | A1 | |
| WO2013019256A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2013043208A2 | World Intellectual Property Organization (WIPO) | A2 | |
| EP2613484A2 | European Patent Office (EPO) | A2 | |
| EP2613485A2 | European Patent Office (EPO) | A2 | |
| US8525938B2 | United States of America | B2 | |
| EP2676435A1 | European Patent Office (EPO) | A1 | |
| EP2676435A4 | European Patent Office (EPO) | A4 | |
| EP2689303A1 | European Patent Office (EPO) | A1 | |
| EP2689574A1 | European Patent Office (EPO) | A1 | |
| US2014028922A1 | United States of America | A1 | |
| EP2613485A3 | European Patent Office (EPO) | A3 | |
| US8659400B2 | United States of America | B2 | |
| EP2517077A4 | European Patent Office (EPO) | A4 | |
| WO2013043208A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2013019256A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP2613484A3 | European Patent Office (EPO) | A3 | |
| EP2740027A2 | European Patent Office (EPO) | A2 | |
| US2014167932A1 | United States of America | A1 | |
| US2014167933A1 | United States of America | A1 | |
| CN103917927A | China | A | |
| EP1929732B1 | European Patent Office (EPO) | B1 | |
| EP2758838A2 | European Patent Office (EPO) | A2 | |
| US2014218182A1 | United States of America | A1 | |
| US2014222861A1 | United States of America | A1 | |
| US2014222862A1 | United States of America | A1 | |
| US8812629B2 | United States of America | B2 | |
| EP2689574A4 | European Patent Office (EPO) | A4 | |
| US2014240104A1 | United States of America | A1 | |
| EP2689303A4 | European Patent Office (EPO) | A4 | |
| US8854556B2 | United States of America | B2 | |
| US2014337879A1 | United States of America | A1 | |
| EP2740027A4 | European Patent Office (EPO) | A4 | |
| EP2758838A4 | European Patent Office (EPO) | A4 | |
| US2015130597A1 | United States of America | A1 | |
| US9047761B2 | United States of America | B2 | |
| US2015154858A1 | United States of America | A1 | |
| US9087100B2 | United States of America | B2 | |
| US9088663B2 | United States of America | B2 | |
| US2015244965A1 | United States of America | A1 | |
| US9123236B2 | United States of America | B2 | |
| US2015279205A1 | United States of America | A1 | |
| US2015279206A1 | United States of America | A1 | |
| EP2689574B1 | European Patent Office (EPO) | B1 | |
| WO2015179165A1 | World Intellectual Property Organization (WIPO) | A1 | |
| US9208679B2 | United States of America | B2 | |
| EP2689303B1 | European Patent Office (EPO) | B1 | |
| US2016063856A1 | United States of America | A1 | |
| US9350850B2 | United States of America | B2 | |
| WO2016126609A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US9437102B2 | United States of America | B2 | |
| US9437104B2 | United States of America | B2 | |
| US9454899B2 | United States of America | B2 | |
| US9478125B2 | United States of America | B2 | |
| WO2016126609A3 | World Intellectual Property Organization (WIPO) | A3 | |
| US9489835B2 | United States of America | B2 | |
| US2016343246A1 | United States of America | A1 | |
| US9530308B2 | United States of America | B2 | |
| US9558654B2 | United States of America | B2 | |
| KR20170030477A | Republic of Korea | A | |
| CN106537926A | China | A | |
| EP3146727A1 | European Patent Office (EPO) | A1 | |
| BR112014006930A2 | Brazil | A2 | |
| EP3146727A4 | European Patent Office (EPO) | A4 | |
| JP2017523740A | Japan | A | |
| EP2676435B1 | European Patent Office (EPO) | B1 | |
| CN103917927B | China | B | |
| KR20170109054A | Republic of Korea | A | |
| IL253817A0 | Israel | A0 | |
| IL253817D0 | Israel | D0 | |
| EP2740027B1 | European Patent Office (EPO) | B1 | |
| US9805591B2 | United States of America | B2 | |
| ES2640969T3 | Spain | T3 | |
| CN107408331A | China | A | |
| ES2645537T3 | Spain | T3 | |
| EP3254264A2 | European Patent Office (EPO) | A2 | |
| EP3254264A4 | European Patent Office (EPO) | A4 | |
| US9852615B2 | United States of America | B2 |
90 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 appeal.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 0
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Amendment/Argument after BPAI DecisionBD.A | BD.A | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail BPAI Decision on Appeal - Affirmed in PartMAPDP | MAPDP | |
| BPAI Decision - Examiner Affirmed in PartAPDP | APDP | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Email NotificationEML_NTR | EML_NTR | |
| Docketing Notice Mailed to AppellantAP_DK_M | AP_DK_M | |
| Assignment of Appeal NumberAPAS | APAS | |
| Appeal Awaiting BPAI DocketingAPWD | APWD | |
| Reply Brief FiledAPRB | APRB | |
| Exam. Ans. Review CompletePACC | PACC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Examiner's AnswerMAPEA | MAPEA | |
| Examiner's Answer to Appeal BriefAPEA | APEA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Appeal Brief FiledAP.B | AP.B | |
| Mail Appeals conf. Proceed to BPAIMAPCP | MAPCP | |
| Pre-Appeals Conference Decision - Proceed to BPAIAPCP | APCP | |
| Request for Pre-Appeal Conference FiledAP.C | AP.C | |
| Notice of Appeal FiledN/AP | N/AP | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| PG-Pub RequestPG-RQST | PG-RQST | |
| Rescind Nonpublication Request for Pre Grant PublicationRESC | RESC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Is Now CompleteCOMP | COMP | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| Applicant has submitted new drawings to correct Corrected Papers problemsCORRDRW | CORRDRW | |
| Corrected PaperCPAP | CPAP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX | |
| PGPubs nonPub RequestNPRQ | NPRQ | |
| Preliminary AmendmentA.PE | A.PE |
8 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20120041925
- Application
- 14844408
Titles
- English
- Using HDMI-CEC to identify a codeset
Patent term adjustment
- A delay
- +766 daysthe office missed an examination deadline
- B delay
- +825 dayspendency past three years
- C delay
- +1,038 daysinterference, secrecy order or appeal
- Overlap
- −97 daysdelays counted once
- Net adjustment
- 2,532 days
Classification
- CPC, 15
- G06F3/0486
- H04M1/72415
- G08C17/02
- G08C19/28
- G08C23/04
- G08C2201/20
- G08C2201/93
- H04M2250/22
- H04N21/42204
- H04N21/42208
- H04N21/4222
- H04N21/42221
- H04N21/42224
- H04N21/42225
- H04N21/41265
- IPC, 5
- G06F17 00
- H04M1 72415
- G06F3 048
- H04M1 00
- H04N3 27