<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ep-patent-document PUBLIC "-//EPO//EP PATENT DOCUMENT 1.5//EN" "ep-patent-document-v1-5.dtd">
<ep-patent-document id="EP14797427B1" file="EP14797427NWB1.xml" lang="en" country="EP" doc-number="2997559" kind="B1" date-publ="20180718" status="n" dtd-version="ep-patent-document-v1-5">
<SDOBI lang="en"><B000><eptags><B001EP>ATBECHDEDKESFRGBGRITLILUNLSEMCPTIESILTLVFIROMKCYALTRBGCZEEHUPLSK..HRIS..MTNORS..SM..................</B001EP><B003EP>*</B003EP><B005EP>J</B005EP><B007EP>BDM Ver 0.1.63 (23 May 2017) -  2100000/0</B007EP></eptags></B000><B100><B110>2997559</B110><B120><B121>EUROPEAN PATENT SPECIFICATION</B121></B120><B130>B1</B130><B140><date>20180718</date></B140><B190>EP</B190></B100><B200><B210>14797427.3</B210><B220><date>20140515</date></B220><B240><B241><date>20151116</date></B241></B240><B250>en</B250><B251EP>en</B251EP><B260>en</B260></B200><B300><B310>201313895992</B310><B320><date>20130516</date></B320><B330><ctry>US</ctry></B330></B300><B400><B405><date>20180718</date><bnum>201829</bnum></B405><B430><date>20160323</date><bnum>201612</bnum></B430><B450><date>20180718</date><bnum>201829</bnum></B450><B452EP><date>20180410</date></B452EP></B400><B500><B510EP><classification-ipcr sequence="1"><text>G08C  17/00        20060101AFI20160408BHEP        </text></classification-ipcr></B510EP><B540><B541>de</B541><B542>SYSTEM UND VERFAHREN ZUR SCHNELLEN KONFIGURATION EINER UNIVERSELLEN STEUERUNGSVORRICHTUNG</B542><B541>en</B541><B542>SYSTEM AND METHOD FOR RAPID CONFIGURATION OF A UNIVERSAL CONTROLLING DEVICE</B542><B541>fr</B541><B542>SYSTÈME ET PROCÉDÉ PERMETTANT UNE CONFIGURATION RAPIDE D'UN DISPOSITIF DE COMMANDE UNIVERSEL</B542></B540><B560><B561><text>US-A- 6 058 106</text></B561><B561><text>US-A1- 2006 109 138</text></B561><B561><text>US-A1- 2006 217 065</text></B561><B561><text>US-A1- 2009 292 375</text></B561><B561><text>US-A1- 2010 123 613</text></B561><B561><text>US-A1- 2010 123 613</text></B561><B561><text>US-A1- 2011 250 914</text></B561><B561><text>US-A1- 2013 069 769</text></B561><B565EP><date>20160414</date></B565EP></B560></B500><B700><B720><B721><snm>KOHANEK, Jeffrey</snm><adr><str>10241 Arundel Avenue</str><city>Westminster, California 92683</city><ctry>US</ctry></adr></B721><B721><snm>BLACK, Jeremy K.</snm><adr><str>12105 Red Hill Avenue</str><city>N. Tustin, California 92705</city><ctry>US</ctry></adr></B721></B720><B730><B731><snm>Universal Electronics, Inc.</snm><iid>101332627</iid><irf>17949.136</irf><adr><str>201 E. Sandpointe Avenue, 8th Floor</str><city>Santa Ana, CA 92707</city><ctry>US</ctry></adr></B731></B730><B740><B741><snm>CMS Cameron McKenna Nabarro 
Olswang LLP</snm><iid>101670164</iid><adr><str>Cannon Place 
78 Cannon Street</str><city>London EC4N 6AF</city><ctry>GB</ctry></adr></B741></B740></B700><B800><B840><ctry>AL</ctry><ctry>AT</ctry><ctry>BE</ctry><ctry>BG</ctry><ctry>CH</ctry><ctry>CY</ctry><ctry>CZ</ctry><ctry>DE</ctry><ctry>DK</ctry><ctry>EE</ctry><ctry>ES</ctry><ctry>FI</ctry><ctry>FR</ctry><ctry>GB</ctry><ctry>GR</ctry><ctry>HR</ctry><ctry>HU</ctry><ctry>IE</ctry><ctry>IS</ctry><ctry>IT</ctry><ctry>LI</ctry><ctry>LT</ctry><ctry>LU</ctry><ctry>LV</ctry><ctry>MC</ctry><ctry>MK</ctry><ctry>MT</ctry><ctry>NL</ctry><ctry>NO</ctry><ctry>PL</ctry><ctry>PT</ctry><ctry>RO</ctry><ctry>RS</ctry><ctry>SE</ctry><ctry>SI</ctry><ctry>SK</ctry><ctry>SM</ctry><ctry>TR</ctry></B840><B860><B861><dnum><anum>US2014038138</anum></dnum><date>20140515</date></B861><B862>en</B862></B860><B870><B871><dnum><pnum>WO2014186543</pnum></dnum><date>20141120</date><bnum>201447</bnum></B871></B870></B800></SDOBI>
<description id="desc" lang="en"><!-- EPO <DP n="1"> -->
<heading id="h0001">BACKGROUND</heading>
<p id="p0001" num="0001">Universal controlling devices, for example, remote controls, which are adaptable to issue commands to a multiplicity of appliances of different manufacture and/or type, and the features and functionality provided by such controlling devices are well known in the art. In this regard, early universal controlling devices such as described in <patcit id="pcit0001" dnum="US4623887A"><text>U.S. Patent No. 4,623,887</text></patcit> were generally "learners," that is, they were adapted to capture, store, and subsequently play back the command signals of the original equipment remote controls corresponding to the appliances to be controlled. However, the required initial teaching process used to configure such early universal controlling devices proved tedious and error prone.</p>
<p id="p0002" num="0002">To address this drawback, further universal controlling devices were introduced which included preprogrammed libraries of command data, such as those described in <patcit id="pcit0002" dnum="US4774511A"><text>U.S. Patent Nos. 4,774,511</text></patcit> or <patcit id="pcit0003" dnum="US4959810A"><text>4,959,810</text></patcit>. As particularly described in <patcit id="pcit0004" dnum="US4959810A"><text>U.S. Patent No. 4,959,810</text></patcit>, to configure such a universal controlling device a user is required to consult a reference manual or the like to obtain a setup code that corresponds to an intended target appliance. The setup code is then keyed into the universal controlling device where it is used to select a command data set from the library of command data sets stored in the universal controlling device whereupon the selected command data set is to be used when the universal controlling device is instructed to issue commands to that intended target appliance. <patcit id="pcit0005" dnum="US5451953A"><text>U.S. Patent Nos. 5,451,953</text></patcit> and <patcit id="pcit0006" dnum="US5614906A"><text>5,614,906</text></patcit> further illustrate and describe methods for configuring a controlling device using a library of command data sets stored in memory of the controlling device.</p>
<p id="p0003" num="0003">As alternatives to a user looking up a setup code and manually keying the setup code into the universal controlling device for the purpose of configuring the universal controlling device, <patcit id="pcit0007" dnum="US665642A" dnum-type="L"><text>U.S. Patent Application No. 10/665,642</text></patcit> and <patcit id="pcit0008" dnum="US7218243B"><text>U.S. Patent Nos. 7,218,243</text></patcit>, <patcit id="pcit0009" dnum="US6225398B"><text>6,225,398</text></patcit> and <patcit id="pcit0010" dnum="US6157319A"><text>6,157,319</text></patcit> illustrate and describe using information from, for example, an RFID tag, bar code, appliance generated signal, user interaction with a locally displayed or remotely (e.g., computer or Internet) accessible menu, etc. to identify the appliance intended to be controlled which information is accordingly used to select a command data set from a library of command data sets to be used when sending commands to that appliance. As further described in these references, the library of command data sets may be stored locally on the universal controlling device or in a database accessible to the universal controlling device where the selected command data sets are thus downloaded into the universal controlling device, or a combination thereof.</p>
<p id="p0004" num="0004">Still further, universal controlling devices are known that allow a user to key into the universal controlling device information that is used to configure the universal controlling device to command additional operations of an intended target appliance. One such universal controlling device is described and illustrated in <patcit id="pcit0011" dnum="US5515052A"><text>U.S. Patent No. 5,515,052</text></patcit>. A yet further system and method for configuring a universal controlling device to command operations of an intended target appliance is described and illustrated in co-pending <patcit id="pcit0012" dnum="US389627A" dnum-type="L"><text>U.S. Application No. 11/389,627</text></patcit>, entitled "System And Method For Defining A Controlled Device Command Set."<!-- EPO <DP n="2"> --></p>
<p id="p0005" num="0005">It is also known in the art to configure a universal controlling device to thereby provide to the universal controlling device a user interface that has the same appearance as the original equipment remote control corresponding to the appliances to be controlled. For example, <patcit id="pcit0013" dnum="US6938101A"><text>U.S. Patent No. 6,938, 101</text></patcit> illustrates and describes a universal controlling device that provides a user interface in the form of a virtual remote control that has the key layout and appearance of an original equipment remote control. Similarly, <patcit id="pcit0014" dnum="WO2005043484A"><text>PCT Published Application WO 2005/043484</text></patcit> illustrates and describes a universal controlling device having a camera where the camera is used to capture an image of an original equipment remote control which captured image is then used in the user interface of the universal controlling device. <patcit id="pcit0015" dnum="US20100123613A"><text>US 2010/012 3613</text></patcit> describes a controlling device having a key matrix. When a function key is actuated the device retrieves, from command data stored in a memory, a command value and a control protocol corresponding to the actuated key and transmits the command to an intended target appliance. A setup command may correspond to a two-way protocol which permits the controlling device to transmit to and receive from an appliance. The controlling device may issue a response-eliciting command using a specified protocol to detect the presence of a compatible appliance.</p>
<p id="p0006" num="0006">While these variously known systems and methods for configuring a universal controlling device generally work for their intended purpose, a need remains for a system and method that provides a yet more convenient and user friendly way for configuring a universal controlling device.</p>
<heading id="h0002">SUMMARY OF THE INVENTION</heading>
<p id="p0007" num="0007">In accordance with this and other needs, the following generally describes a system and method for rapid configuration of a universal controlling device.</p>
<p id="p0008" num="0008">According to the present invention, there is provided a universal controlling device and a method for configuring a universal controlling device to exchange communications with an intended target device via an RF communications channel as described in the accompanying claims.</p>
<p id="p0009" num="0009">In addition to one or more of the previously described configuration methods, a universal controlling device may be provided with one or more buttons which, when activated in a set up mode, may serve to initiate a rapid configuration of the controlling device to utilize one of a group of pre-selected command data sets. Such pre-selected command data sets may comprise a subset of the complete library of command data sets available within the controlling device, and may represent, for example, those command data sets most likely to be required for a particular application of the controlling device. The exact subset to be offered may be preset at time of shipment, deployment, or manufacture based upon, for example, the purchasing entity or geographic region to which the controlling device is to be shipped; a brand or type of equipment with which it is intended to be packaged; the environment in which it is destined to be used; etc.</p>
<p id="p0010" num="0010">In this manner a single universal controlling device with a comprehensive library of command data sets may nevertheless be adapted to be rapidly configurable via the use of abbreviated keystroke sequences which correspond to a substantial proportion of the target controlled appliance population in an intended field of application.</p>
<p id="p0011" num="0011">A better understanding of the objects, advantages, features, properties and relationships of the invention will be obtained from the following detailed description and accompanying drawings which set forth illustrative embodiments and which are indicative of the various ways in which the principles of the invention may be employed.<!-- EPO <DP n="3"> --></p>
<heading id="h0003">BRIEF DESCRIPTION OF THE DRAWINGS</heading>
<p id="p0012" num="0012">For a better understanding of the various aspects of the invention, reference may be had to preferred embodiments shown in the attached drawings in which:
<ul id="ul0001" list-style="none" compact="compact">
<li><figref idref="f0001">Figure 1</figref> illustrates an exemplary system in which an exemplary controlling device according to the instant invention may be used;</li>
<li><figref idref="f0002">Figure 2</figref> illustrates a block diagram of exemplary components of the exemplary controlling device of <figref idref="f0001">Figure 1</figref>;</li>
<li><figref idref="f0003">Figure 3</figref> further illustrates the exemplary controlling device of <figref idref="f0001">Figure 1</figref>;</li>
<li><figref idref="f0004">Figure 4</figref> illustrates an exemplary instruction card;</li>
<li><figref idref="f0004">Figure 5</figref> illustrates in symbolic form an exemplary memory configuration;</li>
<li><figref idref="f0005">Figure 6</figref> illustrates in flow chart form an exemplary method for rapid set up of a universal controlling device;</li>
<li><figref idref="f0006">Figure 7</figref> illustrates in flow chart form a further exemplary method for rapid set up of a universal controlling device;</li>
<li><figref idref="f0007">Figure 8</figref> illustrates in flow chart form a yet further exemplary method for rapid set up of a universal controlling device; and</li>
<li><figref idref="f0008">Figure 9</figref> illustrates in flow chart form a still further exemplary method for rapid set up of a universal controlling device in accordance with an embodiment of the invention.</li>
</ul></p>
<heading id="h0004">DETAILED DESCRIPTION</heading>
<p id="p0013" num="0013">The examples of <figref idref="f0004 f0005 f0006 f0007">Figures 4-8</figref> do not form a part of the claimed invention but are included herein to assist in understanding the invention.</p>
<p id="p0014" num="0014">Turning now to <figref idref="f0001">Figure 1</figref>, there is illustrated an exemplary system in which a controlling device 100 is configured to control various controllable appliances, such as a television 102 and a set top box ("STB") 104. As is known in the art, the controlling device 100 is capable of transmitting commands to the appliances, using any convenient IR, RF, Point-to-Point, or networked protocol, to cause the appliances to perform operational functions. While illustrated in the context of a television 102 and STB 104, it is to be understood that controllable appliances may include, but need not be limited to, televisions, VCRs, DVRs, DVD players, cable or satellite converter set-top boxes ("STBs"), amplifiers, CD players, game consoles, home lighting, drapery, fans, HVAC systems, thermostats, personal computers, etc.</p>
<p id="p0015" num="0015">With reference to <figref idref="f0002">Figure 2</figref>, for use in commanding the functional operations of one or more appliances, the controlling device 100 may include, as needed for a particular application, a processor 200 coupled to a ROM memory 204, a RAM memory 205, a key matrix 216 (e.g., hard keys, soft keys such as a touch sensitive surface overlaid on a liquid crystal (LCD), and/or an electroluminescent (EL) display), transmission circuit(s) and/or transceiver circuit(s) 210 (e.g., IR and/or RF), a non-volatile read/write memory 206, a means 202 to provide feedback to the user (e.g., one or more LEDs, display, speaker, and/or the like), a power source 208, an input/output port 218 such as a serial interface, USB port, modem, Zigbee, WiFi , or Bluetooth transceiver, etc., and clock and timer logic 212 with associated crystal or resonator 214.</p>
<p id="p0016" num="0016">As will be understood by those skilled in the art, some or all of the memories 204, 205, 206 may include executable instructions (collectively, the program memory) that are intended to be executed by the processor 200 to control the operation of the remote control 100, as well as data which serves to define to the operational software the necessary control protocols and command values for use in transmitting command signals to controllable appliances<!-- EPO <DP n="4"> --> (collectively, the command data). In this manner, the processor 200 may be programmed to control the various electronic components within the remote control 100, e.g., to monitor the power supply 208, to cause the transmission of signals, etc. The non-volatile read/write memory 206, for example an EEPROM, battery-backed up RAM, FLASH, Smart Card, memory stick, or the like, may additionally be provided to store setup data and parameters as necessary. While the memory 204 is illustrated and described as a ROM memory, memory 204 can also be comprised of any type of readable media, such as ROM, FLASH, EEPROM, or the like. Preferably, the memories 204 and 205 are non-volatile or battery-backed such that data is not required to be reloaded after battery changes. In addition, the memories 204, 205 and 206 may take the form of a chip, a hard disk, a magnetic disk, an optical disk, and/or the like. Still further, it will be appreciated that some or all of the illustrated memory devices may be physically combined (for example, a single FLASH memory may be logically partitioned into different portions to support the functionality of memories 204 and 206 respectively), and/or may be physically incorporated within the same IC chip as the microprocessor 200 (a so called "microcontroller") and, as such, they are shown separately in <figref idref="f0003">Fig. 3</figref> only for the sake of clarity.</p>
<p id="p0017" num="0017">To cause the controlling device 100 to perform an action, the controlling device 100 is adapted to be responsive to events, such as a sensed user interaction with the key matrix 216, etc. In response to an event, appropriate instructions within the program memory (hereafter the "operating program") may be executed. For example, when a function key is actuated on the controlling device 100, the controlling device 100 may retrieve from the command data stored in memory 204, 205, 206 a command value and control protocol corresponding to the actuated function key and, where necessary, current device mode and transmit that command to an intended target appliance, e.g., STB 104, in a format recognizable by that appliance to thereby control one or more functional operations of that appliance. It will be appreciated that the operating program can be used not only to cause the transmission of commands/or data to the appliances, but also to perform local operations. While not limiting, local operations that may be performed by the controlling device 100 may include displaying information/data, favorite channel setup, macro key setup, function key relocation, etc. Examples of local operations can be found in <patcit id="pcit0016" dnum="US5481256A"><text>U.S. Patent Nos. 5,481,256</text></patcit>, <patcit id="pcit0017" dnum="US5959751A"><text>5,959,751</text></patcit>, and <patcit id="pcit0018" dnum="US6014092A"><text>6,014,092</text></patcit>.</p>
<p id="p0018" num="0018">For selecting sets of command data to be associated with the appliances to be controlled (hereafter referred to as a setup procedure), data may be entered into the controlling device 100 that serves to identify each intended target appliance by its make, and/or model, and/or type. The data is typically entered via activation of those keys that are also used to cause the transmission of commands to an appliance, preferably the keys that are labeled with numerals. Such data allows the controlling device 100 to identify the appropriate command data set within a preprogrammed library of command data that is to be used to transmit recognizable commands in formats appropriate for such identified appliances. The library of command data may represent a plurality of controllable appliances of different types and manufacture, a plurality of controllable appliances of the same type but different manufacture, a plurality of appliances of the same manufacture but different type or model, etc., or any combination thereof as appropriate for a given embodiment. In conventional practice as is well known in the art, such data used to identify an appropriate command data set may take the form of a numeric setup code (obtained, for example, from a printed list of manufacturer names and/or models with corresponding code numbers, from a support Web site, etc.). Alternative setup procedures previously proposed in the art include scanning bar codes, sequentially transmitting a predetermined command in different formats until a target appliance response is detected, interaction with a Web site culminating in downloading of command data and/or setup codes to the controlling device, etc. Since such methods for setting up a controlling device to command the operation of specific home appliances are<!-- EPO <DP n="5"> --> well-known, these will not be described in greater detail herein. Nevertheless, for additional information pertaining to setup procedures, the reader may turn, for example, to <patcit id="pcit0019" dnum="US4959810A"><text>U.S. Patent Nos. 4,959,810</text></patcit>, <patcit id="pcit0020" dnum="US5614906A"><text>5,614,906</text></patcit>, or <patcit id="pcit0021" dnum="US6225938B"><text>6,225,938</text></patcit>.</p>
<p id="p0019" num="0019">To facilitate rapid setup of a select subset of available target appliances controlling device 100 may, in accordance with the instant invention and in addition to one or more of the previously known setup procedures described above, be adapted to support an abbreviated keypress sequence which will immediately configure the controlling device for use with one of a group of preselected device command data sets, as will now be described in further detail.</p>
<p id="p0020" num="0020">In an exemplary embodiment, universal controlling device 100 is intended for deployment by a cable system operator in conjunction with a cable STB (e.g., 104). Since a particular cable system operator typically utilizes only a small number of different STB models in the field, even though controlling device 100 may include a large library of STB command data sets only a few of the command data sets may be applicable within a given cable system. Accordingly, the operating software of controlling device 100 of <figref idref="f0003">Figure 3</figref> may be adapted to implement a method whereby, for example, any one of the four keys 302, 304, 306 and 308, when activated in conjunction with Setup key 310, may serve as a quick link to a predetermined numeric setup code value. These predetermined numeric setup code values may reside in a programmable area of memory (e.g. NV memory 206) and may for example be configured, i.e., mapped to the quick set keys, at a factory or distribution center prior to shipment to a cable system operator to match the STB equipment known to be deployed by the cable system operator for which the controlling device 100 is destined, or alternatively may be configured at a multiple cable system operator's central warehouse or distribution center to match the STB equipment known to be deployed in a particular region prior to onward shipment of controlling device 100 to that region (individually and collectively referred to hereinafter as "prior to deployment"). Such configuration may be performed, for example, by loading data via input/output port 218, by reception of data via transceiver 210, by entry of keystroke sequences on key matrix 216, etc. Combinations of such methods may also be used, for example the memory contents of a master unit may initially be configured using keystroke sequences, after which its memory contents may be read out through input/output port 218 and subsequently duplicated into other controlling devices by downloading through their input/output ports. In this regard, methods for configuration of controlling device programmable memory are well known in the art, for example as described in <patcit id="pcit0022" dnum="US5953144A"><text>U.S. Patents 5,953,144</text></patcit> or <patcit id="pcit0023" dnum="US6223348B"><text>6,223,348</text></patcit>.</p>
<p id="p0021" num="0021">By way of more detailed example, <figref idref="f0004">Figure 4</figref> illustrates a quick setup instruction card 400 such as might be provided to installers for a cable system operator. This card advises the cable system STB installer to hold down the "A" key 302 together with the "Setup" key 310 for three seconds in order to configure controlling device 100 to command the operation of a Motorola STB (numeric setup code 01376). Using the "B" key instead will result in configuration for a Scientific Atlanta/Cisco STB (numeric setup code 01877), using the "C" key will result in configuration for an STB which uses the XMP IR protocol (numeric setup code 01982), and so on. Referring now to <figref idref="f0004">Figure 5</figref>, the contents of those portions of an exemplary controlling device memory which may be used in support of this feature are illustrated in symbolic form. As is well known in the art, a portion 502 of non-configurable memory such as ROM, OTP, FLASH, etc. (e.g. a portion of memory 204 of <figref idref="f0002">Fig. 2</figref>) may be programmed at time of manufacture with a library of multiple appliance command data sets 504. As is also well known, each command data set may be identifiable via a unique numeric set up code and controlling device 100 may be configured to operate any of those appliances by direct entry of the appropriate numeric set up code, for example as described in the<!-- EPO <DP n="6"> --> ATLAS OCAP 5 -Device Remote Control User Guide, Universal Electronics Inc. document M1056 Rev 3.0 ©2006.</p>
<p id="p0022" num="0022">Additionally, in one example, a portion 506 of configurable memory such as EEPROM, FLASH, etc. (e.g. a portion of memory 206 of <figref idref="f0002">Fig. 2</figref>) may contain a table 508 of numeric set up codes 510, 512 comprising the available quick set up links assigned to the four buttons 302 through 308. The contents of table 508 may for example comprise numeric set up codes 510 which correspond to command data sets 504 stored in non-configurable memory, and/or numeric set up codes 512 which correspond to customized or upgraded command data sets 514 which are themselves stored in configurable memory.</p>
<p id="p0023" num="0023">It should be appreciated that in the above example, the specific selection and ordering of STB devices to be assigned to the available quick set up keys may be unique to a particular cable system operator, and accordingly different configurable memory contents and different instruction cards may be provisioned for each cable system operator, or even for different regions within the same cable system operation.</p>
<p id="p0024" num="0024">Turning now to <figref idref="f0005">Figure 6</figref>, the steps performed by an exemplary implementation of the inventive feature are presented in flowchart form. In reviewing this and other flowcharts of the instant disclosure, it will be appreciated that certain common elements well known in the art such as, for example, stuck key timeouts, low battery detection, etc. have been omitted for the sake of clarity, and also that the use of the term "step" herein is not intended to imply a required order to carry out the actions described and that the designated numbers are for convenience of reference only. When Setup key 310 of an exemplary controlling device 100 is activated, at step 602 the operating program of controlling device 100 first checks if one of the quick set up keys 302, 304, 306 or 308 is also activated. If so, at steps 604 and 606, the operating program waits to ensure that both keys remain continuously activated for a specified time, for example three seconds in accordance with the directions of instruction card 400. If not, at step 608 the operating program signals an error condition (e.g., via user feedback device 202) and exits without altering the current configuration setting of controlling device 100. Once the two keys have been continuously activated for the required period of time, at step 610 the operating program retrieves a numeric set up code value from the table 508 entry which corresponds to the activated quick set up key and uses that value to configure controlling device 100 to use the command data set corresponding to the indicated numeric set up code value, in this example, to control functional operations of the STB. Thereafter, at step 612 the operating program signals a successful set up completion to the user (e.g., via user feedback device 202), waits at step 614 for all keys to be released, and terminates the set up procedure. In this example, it will be understood that the STB device mode need not be specified to the remote control as the remote control will recognize that activation of a quick set up key is only being used to configure the STB device mode. This would also be true for alternative examples in which the command data set library of a controlling device supports only a single type of appliance, such as for example a remote control intended only for use with a cable STB, a remote control supplied by the manufacturer of a particular TV model which supports only that TV but includes a library of cable STB devices, etc. If, however, the quick set up keys are to be made available for quickly setting up multiple device types, e.g., the command code data sets for the most commonly purchased televisions are also mapped to the quick set up keys, the remote control will need to be informed of the device mode to be set up via activation of the quick set up key. To this end, a device mode key of the exemplary remote control of <figref idref="f0003">Figure 3</figref> may be activated prior to the simultaneous activation of the Setup key and quick setup key or thereafter.</p>
<p id="p0025" num="0025">Returning to step 602, if it is determined that a quick set up key is not active, at step 620 the operating program checks if three seconds has elapsed since Setup key 310 was activated.<!-- EPO <DP n="7"> --> If so (i.e., key 310 has been held down for 3 seconds) at step 622 the operating program signals (e.g., via user feedback device 202) that it is ready to accept conventional set up input (e.g., entry of a multi-digit numeric code). Once the Setup key is released, a conventional numeric code set up entry such as, for example, that described in the before referenced ATLAS OCAP 5-Device Remote Control User Guide may be performed at step 626. Upon completion of the numeric entry, if a valid code has been entered, at step 630 the operating program configures the indicated device mode of controlling device 100, signals a successful set up (e.g., via user feedback device 202) at step 616, and terminates the set up procedure. In the case of controlling devices adapted to offer multiple device modes supporting different appliance types, such as the example of <figref idref="f0003">Figure 3</figref>, the indicated device mode, in this example, may be the current device mode of the remote control or a device mode specified to the remote control by activation of a device mode key either prior to or after completion of the numeric entry. Alternatively, one of the numeric digits entered may be indicative of the device mode to be configured; numeric codes may be assigned to ranges representative of different appliance types, etc.</p>
<p id="p0026" num="0026">Returning to step 620, if three seconds have not yet elapsed, the operating software of controlling device 100 at step 640 determines if the Setup key 310 is still activated. If so the operating program repeats the series of tests starting at step 602. If not (i.e., Setup button 310 has been released before three seconds has elapsed and without any simultaneous activation of one of the quick set up buttons) at step 642 the operating software performs any other action which may have been defined to be initiated by a short activation of Setup key 310, by way of example, a function synthesis input as described in the before referenced <patcit id="pcit0024" dnum="US5515052A"><text>U.S. Patent 5,515,052</text></patcit>.</p>
<p id="p0027" num="0027">It will be appreciated that in certain embodiments, it may be desirable to protect against inadvertent activation of the quick set up method by a consumer during their normal use of controlling device 100. To this end the quick set up feature may, for example, only be activatable for a specified period of time after batteries have been inserted into controlling device 100. Alternatively, means such as a jumper, special keystroke sequence, etc., may be provided to allow a cable system STB installer to lock all or part of the controlling device configuration once the quick set up has been successfully performed.</p>
<p id="p0028" num="0028">Turning now to <figref idref="f0006">Figure 7</figref>, there is presented an alternative method for implementing entry into the quick set up mode. Unlike the method of <figref idref="f0005">Figure 6</figref> in which the Setup key and one of the quick set up keys are activated simultaneously, in the method of <figref idref="f0006">Figure 7</figref> the Setup key activated alone for three seconds, as in the conventional set up method described for example in the before referenced ATLAS OCAP 5 -Device Remote Control User Guide. However, once the three second time has been confirmed and the operating program commences the set up process, the next key activated may determine the set up method being used. If the next key activated is one of the numeric keys 312 or possibly a device mode key in those examples in which multiple device modes are supported, a conventional set up is initiated; but if the next key activated is one of the quick set up keys 302 through 308, a quick set up is performed. With reference to <figref idref="f0006">Figure 7</figref>, steps 702 through 708 time the initial activation of Setup key 310 and initiate the set up process (it being noted that activation of the Setup key for less than three seconds has the same effect as previously described in conjunction with <figref idref="f0005">Figure 6</figref> step 642). Once the set up mode has been initiated, steps 710 and 712 test for activation of a numeric key/device mode key or a quick set up key respectively. Activation of any other key (step 714) or no further activity within 30 seconds (step 716) constitute error conditions and will cause the operating program to terminate the set up process after signaling a failure to the user at step 718. However, if activation of a numeric key is detected at step 710, a conventional multi-digit set up is initiated as previously described in<!-- EPO <DP n="8"> --> conjunction with <figref idref="f0005">Figure 6</figref>, while if activation of a quick setup key is detected at 712, a quick set up is performed, also as previously described in conjunction with <figref idref="f0005">Figure 6</figref>.</p>
<p id="p0029" num="0029">Turning now to <figref idref="f0007">Figure 8</figref>, a third alternative method is presented, which method may be used where one or more of the selected quick set up command data sets corresponds to a bidirectional STB protocol, i.e., a two-way protocol which permits controlling device 100 to both transmit to and receive from a STB. In such cases, it may be possible for controlling device 100 to issue a response-eliciting command or enquiry using the specified protocol(s) in order to automatically detect the presence of a compatible STB and configure itself accordingly. Once again utilizing a universal controlling device 100 is intended for deployment by a cable system operator in conjunction with a cable STB as an example, when setup key 310 is activated, at step 802 the operating program of controlling device 100 first checks if the controlling device is currently set to the "cable" operational mode (e.g., by prior activation of the "Cable" mode button 314). If not, the operating software proceeds as previously described, continuing for example at step 650 of <figref idref="f0005">Figure 6</figref>. If, however, the "cable" mode is currently active, at step 804 the operating software next determines if any of the predetermined quick set up numeric codes (e.g., those contained in table 508) correspond to a bidirectional STB communication protocol. If not, the set up process continues at step 650 as before. If however any bidirectional protocol(s) are designated, at step 806 the operating software sets a pointer to the first such code and then at step 808 transmits a response-eliciting query using the indicated command data set. The operating software may then wait for a predetermined period of time (e.g., one second, as at step 814) for a response to that transmission. If the set up key is released during this period as determined by step 812, this constitutes an error condition and the operating software signals a set up failure at step 822 and the set up process terminated with no changes to the controlling device configuration. If a valid response is received from an STB as determined at step 810, at step 824 the cable device mode of the universal controlling device 100 is configured to use the indicated command data set, and the set up process is completed by signaling a successful set up at step 826 and terminating the process after the set up key is released at step 828. If no STB response is received within the allotted time period, at step 816 the operating software determines if any further bidirectional protocols are designated. If so, at step 818 the pointer is set to the next such code and the query/response sequence repeated. If not, at step 820 the operating software next determines if any numeric codes corresponding to non-bidirectional protocols are designated for quick set up. If so, the set up process continues as before, for example at step 650 of <figref idref="f0005">Figure 6</figref>. If no such codes are present, the set up process is terminated with no change to the configuration of controlling device 100.</p>
<p id="p0030" num="0030">In certain examples, the expected response from a bidirectionally-equipped STB may be a simple acknowledgement of the controlling device transmission. In other examples, the response may constitute additional configuration data for use by controlling device 100. By way of example, without limitation, controlling device 100 may include buttons intended to provide immediate access to a video-on-demand "barker" channel 316 or to a user's favorite channel(s) 318, for example ESPN, CNN, etc. Since these content streams may be mapped to different channel numbers in different regions of a cable service provider's territory, part of the STB response to an initial query may comprise data (extracted, for example, from an on-board program guide) for use by the operating software of controlling device 100 in configuring channel tuning macro sequences for those keys. Alternatively, such configuration data may be provided by the STB as a part of a separate transaction, distinct from the initial set up related confirmation.</p>
<p id="p0031" num="0031">In a yet further examples, the quick set up keys, rather than being mapped directly to a specific command data set, may be mapped to an entry in a brand table such as described in <patcit id="pcit0025" dnum="US5614906A"><text>U.S. Patent 5,614,906</text></patcit>,, which brand table in turn may identify a plurality of command data<!-- EPO <DP n="9"> --> sets attributable to a specific brand of device. In accordance with the teachings of <patcit id="pcit0026" dnum="US5614906A"><text>U.S. Patent 5,614,906</text></patcit>, upon identification of a particular brand to be set up by activation of a quick set up key, the operating program of controlling device 100 may cause an effects observable command from each of the plurality of command data sets mapped to the selected quick set up key to be assigned to each of a group of user actuatable keys for example, without limitation, digit keys 312, thereby enabling a user to test each of the command data sets and identify the one which operates their equipment. Alternatively, repetitive actuation of a single key may be used to sequentially step through the plurality of command data sets, as described for example in before referenced <patcit id="pcit0027" dnum="US4959810A"><text>U.S. Patent 4,959,810</text></patcit> or in <patcit id="pcit0028" dnum="US4703359A"><text>U.S. Patent 4,703,359</text></patcit>. The quick set up keys of the controlling device of this example may thus for example be mapped at time of deployment to the command data sets of those brands which enjoy the greatest popularity in the destination market based on, for example, geography, intended use, equipment the controlling device will be packaged with, etc.</p>
<p id="p0032" num="0032">Similarly, the quick set up keys may be mapped to an entry in a device type table, e.g., TV, DVD player, etc., which device type table in turn may identify a plurality of command data sets attributable to a specific type of device. Again, in accordance with the teachings of <patcit id="pcit0029" dnum="US5614906A"><text>U.S. Patent 5,614,906</text></patcit>, upon identification of a particular device type to be set up by activation of a quick set up key, the operating program of controlling device 100 may cause an effects observable command from each of the plurality of command data sets mapped to the selected quick set up key to be assigned to each of a group of user actuatable keys for example, without limitation, digit keys 312, thereby enabling a user to test each of the command data sets and identify the one which operates their equipment. Repetitive actuation of a single key may also be used to sequentially step through the plurality of command data sets, as described for example in before referenced <patcit id="pcit0030" dnum="US4959810A"><text>U.S. Patent 4,959,810</text></patcit> or in <patcit id="pcit0031" dnum="US4703359A"><text>U.S. Patent 4,703,359</text></patcit>. The quick set up keys of the controlling device of this example may thus for example be mapped at time of deployment to those command data sets within a particular device type which enjoy the greatest popularity in the destination market based on, for example, geography, intended use, equipment the controlling device will be packaged with, etc.</p>
<p id="p0033" num="0033">In instances where the controlling device 100 and the appliance to be controlled, e.g., STB 104, are intended to bi-directionally communicate via use of a one of a plurality of possible RF communication protocols each of which is capable of being supported by the controlling device 100, i.e., the controlling device 100 has stored in memory processor executable instructions for supporting a plurality of RF communication protocols, a further configuration method as illustrated in <figref idref="f0008">Figure 9</figref> may be utilized. In the illustrated, exemplary method shown in <figref idref="f0008">Figure 9</figref> the quick setup input elements, e.g., keys 302, 304, 306, and 308, are each linked to a one of the plurality of RF communication protocols that the controlling device 100 may use to exchange communications with an intended target appliance. Accordingly, to specify to the controlling device 100 which one of the plurality of RF communication protocols to use when communicating with an intended target appliance, a user may consult 902 a quick setup instruction card or the like type of reference as previously described wherein the reference/instructions will indicate which predetermined input elements of the controlling device 100 have been linked to which appliances (e.g., which brand and/or model of appliance is linked to each input element) and, accordingly, to which one of the plurality of RF communication protocols supported by the controlling device 100 that will support communication exchanges with that appliance. In this manner, when a user places the controlling device 100 into a setup mode 904 and activates the desired one of the quick setup elements (using any appropriate setup initiating procedure/key entry sequence as described above), the controlling device 100 will use the one of the plurality of RF communication protocols that was linked to the activated one of the quick setup elements to<!-- EPO <DP n="10"> --> transmit a query communication 906 to the intended target appliance for the purpose of attempting to pair 908 the controlling device 100 with that intended target appliance. In the event that the query communication causes a response to be successfully sent from the intended target appliance to the controlling device 100 the controlling device 100 will be paired 914 with the intended target appliance and the controlling device 100 will thereafter use the corresponding RF protocol 916 when communicating with the intended target appliance, e.g., when transmitting a command communication in response to an activation of a command input element of the controlling device 100. In the event that the query communication does not cause a response to be successfully sent from the intended target appliance to the controlling device 100, the controlling device 100 will not be paired 912 with the intended target appliance and alternative methods for attempting to pair the controlling device 100 with the intended target appliance may be utilized, e.g., the user may try another quick setup input element, be instructed to step through and try different one of the plurality of RF communication protocols supported by the controlling device 100, or the like. As before, the quick setup input elements as used in connection with the setup method illustrated in <figref idref="f0008">Figure 9</figref> could be dedicated for use in connection with configuring the controlling device 100 to use a one of a plurality of RF communication protocols for only one type of intended target device (e.g., a STB) or the quick setup input elements could be used in connection with configuring the controlling device 100 to use a one of a plurality of RF communication protocols for plural types of intended target devices. In the latter case, the user may be required to first indicate the device type (for example via activation of a device mode key) that is to be configured via use of the quick setup input elements as described previously. The linking of the quick setup elements to respective ones of the plurality of RF protocols supported by the universal controlling device may likewise be done in any of the manners described previously, e.g., at time of manufacture, prior to deployment of the universal controlling device 100, etc.</p>
<p id="p0034" num="0034">While various concepts have been described in detail, it will be appreciated by those skilled in the art that various modifications and alternatives to those concepts could be developed in light of the overall teachings of the disclosure. For example, while one disclosed example contemplates setup of a controlling device intended for use with a cable STB, it will be appreciated that the inventive methods described may be equally useful in other contexts, for example, a universal controlling device supplied together with a particular manufacturer's appliance, e.g. an AV receiver, may be adapted to support quick set up configuration of other device types (e.g. DVD player, TV, etc.) of the same manufacture. In will also be appreciated that the method described herein can be used to configure the controlling device such that it will use RF communications when communicating with one or more various types of devices while using IR communications when communicating with one or more various other types of devices. Further, while various aspects of this invention have been described in the context of functional modules and illustrated using block diagram or flow chart format, it is to be understood that, unless otherwise stated to the contrary, one or more of the described functions and/or features may be integrated in a single physical device and/or a software module, or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion of the actual implementation of each module is not necessary for an enabling understanding of the invention. Rather, the actual implementation of such modules would be well within the routine skill of an engineer, given the disclosure herein of the attributes, functionality, and inter-relationship of the various functional modules in the system. Therefore, a person skilled in the art, applying ordinary skill, will be able to practice the invention set forth in the claims without undue experimentation. It will be additionally appreciated that the particular concepts<!-- EPO <DP n="11"> --> disclosed are meant to be illustrative only and not limiting as to the scope of the invention which is to be given the full breadth of the appended claims and any equivalents thereof.</p>
</description>
<claims id="claims01" lang="en"><!-- EPO <DP n="12"> -->
<claim id="c-en-01-0001" num="0001">
<claim-text>A method for configuring a universal controlling device (100) to exchange communications with an intended target device (104) via an RF communications channel, comprising:
<claim-text>receiving into the universal controlling device (100) while in a setup mode a selection of a one of a plurality of quick setup input elements (302) of the universal controlling device (100) wherein each of the plurality of quick setup input elements (302) is linked to a one of a plurality of RF communication protocols usable by the universal controlling device (100) to exchange communications with a device type of the intended target device (104); <b>characterised in that</b> it comprises the steps of using the one of the plurality of RF communication protocols linked to the selected of the one of the plurality of quick setup input elements (302) by the universal controlling device (100) to issue a query message (906) to the intended target device (104); and</claim-text>
<claim-text>in response to a message being successfully received by the universal controlling device (100) from the intended target device (104) as transmitted in response to the query message causing the universal controlling device (100) to be paired with the intended target device (104) whereupon the universal controlling device (100) will use the selected one of the plurality of RF communication protocols when the universal controlling device (100) is subsequently placed into an operating mode in which the universal controlling device (100) is intended to exchange communications with the intended target device (104).</claim-text></claim-text></claim>
<claim id="c-en-01-0002" num="0002">
<claim-text>The method as recited in claim 1, wherein the device type of the intended target device (104) comprises a set top box type (104).</claim-text></claim>
<claim id="c-en-01-0003" num="0003">
<claim-text>The method as recited in claim 1, causing the universal controlling device (100) to use an IR protocol when the universal controlling device (100) is placed into an operating mode in which the universal controlling device (100) is intended to transmit communications to a device of a device type other than the device type of the intended target device (104).<!-- EPO <DP n="13"> --></claim-text></claim>
<claim id="c-en-01-0004" num="0004">
<claim-text>The method as recited in claim 1, comprising receiving into the universal controlling device (100) while in the setup mode data indicative of the device type of the intended target device (104).</claim-text></claim>
<claim id="c-en-01-0005" num="0005">
<claim-text>The method as recited in claim 4, comprising using the data indicative of the device type to link the plurality of quick setup input elements (302) to a one of a plurality of RF communication protocols usable to exchange communications with the device type of the intended target device (104).</claim-text></claim>
<claim id="c-en-01-0006" num="0006">
<claim-text>The method as recited in claim 1, wherein each of the plurality of quick setup input elements (302) is linked to a one of a plurality of RF communication protocols usable to exchange communications with a device type of the intended target device (104) at a time of manufacture of the universal controlling device (100).</claim-text></claim>
<claim id="c-en-01-0007" num="0007">
<claim-text>The method as recited in claim 1, wherein each of the plurality of quick setup input elements (302) is linked to a one of a plurality of RF communication protocols usable to exchange communications with a device type of the intended target device (104) at time prior to deployment of the universal controlling device (100).</claim-text></claim>
<claim id="c-en-01-0008" num="0008">
<claim-text>The method as recited in claim 1, comprising causing the universal controlling device (100) to enter into the setup mode (904) in response to an activation of a setup input element (310) of the universal controlling device (100), an activation of a setup input element (310) of the universal controlling device (100) for a predetermined period of time, a simultaneous activation of a setup input element (310) of the universal controlling device (100) and a one of the quick setup input elements (302), or a simultaneous activation of a setup input element (310) of the universal controlling device and a one of the quick setup input elements (302) for a predetermined period of time.</claim-text></claim>
<claim id="c-en-01-0009" num="0009">
<claim-text>A universal controlling device (100), comprising:
<claim-text>a RF communications circuit (210);</claim-text>
<claim-text>a processing unit (200) in communication with the RF communications circuit (210) configured for causing the RF communications circuit to exchange RF communications with an intended target device (104) using a selected one of a plurality of RF communications protocols; and<!-- EPO <DP n="14"> --></claim-text>
<claim-text>a key matrix (216) having a plurality of quick setup input elements (302) wherein each of the plurality of quick setup input elements (302) is linked to a one of a plurality of RF communication protocols usable by the processing circuit (200) in communication with the RF communications circuit (210) to exchange communications with a device type of the intended target device (104);</claim-text>
<claim-text>wherein the universal controlling device (100) is configured to select the one of the plurality of RF communication protocols to be used by the processing device (100) in communication with the RF communications circuit (210) to exchange RF communications with the intended target device (104) in response to a selection of a one of the plurality of quick setup input elements (302) while the universal controlling device (100) is in a setup mode of operation and <b>characterised in that</b> the processing circuit (200) in communication with the RF communications circuit (210) is configured to transmit a query message to the intended target device (104) using the selected one of the plurality of RF communication protocols and the universal controlling device (100) is configured, when a response is successfully received from the intended target device (104) in response to the query message to be paired with the intended target device (104) such that the processing circuit (200) in communication with the RF communications circuit (210) will use the selected one of the plurality of RF communication protocols when the universal controlling device (100) is subsequently placed into an operating mode in which the universal controlling device (100) is intended to exchange communications with the intended target device (104).</claim-text></claim-text></claim>
<claim id="c-en-01-0010" num="0010">
<claim-text>The universal controlling device (100) as recited in claim 9, wherein the universal controlling device (100) comprises a plurality of device mode input elements and wherein an activation of a device mode input element (314) indicates to the universal controlling device (100) the device type of the intended target device (104).</claim-text></claim>
<claim id="c-en-01-0011" num="0011">
<claim-text>The universal controlling device (100) as recited in claim 10, wherein the device mode input element (314) is configured, when it is activated, to select one of a plurality of predetermined linkages between the plurality of quick setup input elements (302) and a one of a plurality of RF communication protocols.<!-- EPO <DP n="15"> --></claim-text></claim>
<claim id="c-en-01-0012" num="0012">
<claim-text>The universal controlling device (100) as recited in claim 9, wherein the universal controlling device (100) comprises a setup input element (310) and the universal controlling device (100) is caused to enter into the setup mode in response to an activation of the setup input element (310), an activation of the setup input element (310) for a predetermined period of time, a simultaneous activation of the setup input element (310) and a one of the quick setup input elements (302), or a simultaneous activation of the setup input element (310) and a one of the quick setup input elements (302) for a predetermined period of time.</claim-text></claim>
</claims>
<claims id="claims02" lang="de"><!-- EPO <DP n="16"> -->
<claim id="c-de-01-0001" num="0001">
<claim-text>Verfahren zur Konfiguration einer universellen Steuerungsvorrichtung (100) zum Austauschen von Kommunikationen mit einer vorgesehenen Zielvorrichtung (104) über einen HF-Kommunikationskanal, umfassend:
<claim-text>Empfangen in die universelle Steuerungsvorrichtung (100), während eines Einrichtungsmodus, einer Auswahl von einem von einer Vielzahl von Schnelleinrichtungseingabeelementen (302) der universellen Steuerungsvorrichtung (100), wobei jedes von der Vielzahl von Schnelleinrichtungseingabeelementen (302) mit einem von einer Vielzahl von HF-Kommunikationsprotokollen verknüpft ist, welche von der universellen Steuerungsvorrichtung (100) verwendbar sind, um Kommunikationen mit einem Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) auszutauschen;</claim-text>
<claim-text><b>dadurch gekennzeichnet, dass</b> es die folgenden Schritte umfasst</claim-text>
<claim-text>Verwenden des einen von der Vielzahl von HF-Kommunikationsprotokollen, welche mit dem ausgewählten einen von der Vielzahl von Schnelleinrichtungseingabeelementen (302) verknüpft sind, durch die universelle Steuerungsvorrichtung (100), um eine Anfragenachricht (906) an die vorgesehene Zielvorrichtung (104) auszugeben; und</claim-text>
<claim-text>als Reaktion auf eine erfolgreich von der universellen Steuerungsvorrichtung (100) von der vorgesehenen Zielvorrichtung (104) empfangene Nachricht, wie als Reaktion auf die Anfragenachricht gesendet, Veranlassen der universellen Steuerungsvorrichtung (100) dazu, mit der vorgesehenen Zielvorrichtung (104) gekoppelt zu werden, woraufhin die universelle Steuerungsvorrichtung (100) das ausgewählte eine aus der Vielzahl von HF-Kommunikationsprotokollen verwenden wird, wenn die universelle Steuerungsvorrichtung (100) nachfolgend in einen Betriebsmodus versetzt wird, in welchem die universelle Steuerungsvorrichtung (100) vorgesehen ist, Kommunikationen mit der vorgesehenen Zielvorrichtung (104) auszutauschen.</claim-text></claim-text></claim>
<claim id="c-de-01-0002" num="0002">
<claim-text>Verfahren nach Anspruch 1, wobei der Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) einen Set-Top-Box-Typ (104) umfasst.<!-- EPO <DP n="17"> --></claim-text></claim>
<claim id="c-de-01-0003" num="0003">
<claim-text>Verfahren nach Anspruch 1, welches die universelle Steuerungsvorrichtung (100) veranlasst, ein IR-Protokoll zu verwenden, wenn die universelle Steuerungsvorrichtung (100) in einen Betriebsmodus versetzt wird, in welchem die universelle Steuerungsvorrichtung (100) vorgesehen ist, Kommunikationen an eine Vorrichtung eines Vorrichtungstyps zu senden, welcher sich von dem Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) unterscheidet.</claim-text></claim>
<claim id="c-de-01-0004" num="0004">
<claim-text>Verfahren nach Anspruch 1, umfassend Empfangen von Daten, welche auf den Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) hinweisen, in die universelle Steuerungsvorrichtung (100), während des Einrichtungsmodus.</claim-text></claim>
<claim id="c-de-01-0005" num="0005">
<claim-text>Verfahren nach Anspruch 4, umfassend Verwenden der Daten, welche auf den Vorrichtungstyp hinweisen, um die Vielzahl von Schnelleinrichtungseingabeelementen (302) mit einem von einer Vielzahl von HF-Kommunikationsprotokollen zu verknüpfen, welche verwendbar sind, um Kommunikationen mit dem Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) auszutauschen.</claim-text></claim>
<claim id="c-de-01-0006" num="0006">
<claim-text>Verfahren nach Anspruch 1, wobei jedes von der Vielzahl von Schnelleinrichtungseingabeelementen (302) mit einem von einer Vielzahl von HF-Kommunikationsprotokollen verknüpft ist, welche verwendbar sind, um Kommunikationen mit einem Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) zu einem Herstellungszeitpunkt der universellen Steuerungsvorrichtung (100) auszutauschen.</claim-text></claim>
<claim id="c-de-01-0007" num="0007">
<claim-text>Verfahren nach Anspruch 1, wobei jedes von der Vielzahl von Schnelleinrichtungseingabeelementen (302) mit einem von einer Vielzahl von HF-Kommunikationsprotokollen verknüpft ist, welche verwendbar sind, um Kommunikationen mit einem Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) vor der Bereitstellung der universellen Steuerungsvorrichtung (100) auszutauschen.</claim-text></claim>
<claim id="c-de-01-0008" num="0008">
<claim-text>Verfahren nach Anspruch 1, umfassend Veranlassen der universellen Steuerungsvorrichtung (100) zum Eintreten in den Einrichtungsmodus (904) als Reaktion<!-- EPO <DP n="18"> --> auf eine Aktivierung eines Einrichtungseingabeelements (310) der universellen Steuerungsvorrichtung (100), eine Aktivierung eines Einrichtungseingabeelements (310) der universellen Steuerungsvorrichtung (100) für eine vorbestimmte Zeitspanne, eine gleichzeitige Aktivierung eines Einrichtungseingabeelements (310) der universellen Steuerungsvorrichtung (100) und eines von den Schnelleinrichtungseingabeelementen (302) oder eine gleichzeitige Aktivierung eines Einrichtungseingabeelements (310) der universellen Steuerungsvorrichtung und eines von den Schnelleinrichtungseingabeelementen (302) für eine vorbestimmte Zeitspanne.</claim-text></claim>
<claim id="c-de-01-0009" num="0009">
<claim-text>Universelle Steuerungsvorrichtung (100), umfassend:
<claim-text>eine HF-Kommunikationsschaltung (210);</claim-text>
<claim-text>eine Verarbeitungseinheit (200) in Kommunikation mit der HF-Kommunikationsschaltung (210), welche konfiguriert ist, die HF-Kommunikationsschaltung zu veranlassen, HF-Kommunikationen mit einer vorgesehenen Zielvorrichtung (104) unter Verwendung eines ausgewählten einen von einer Vielzahl von HF-Kommunikationsprotokollen auszutauschen; und</claim-text>
<claim-text>eine Schlüsselmatrix (216) mit einer Vielzahl von Schnelleinrichtungseingabeelementen (302), wobei jedes von der Vielzahl von Schnelleinrichtungseingabeelementen (302) mit einem von einer Vielzahl von HF-Kommunikationsprotokollen verknüpft ist, welche von der Verarbeitungsschaltung (200) in Kommunikation mit der HF-Kommunikationsschaltung (210) verwendbar sind, um Kommunikationen mit einem Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) auszutauschen;</claim-text>
<claim-text>wobei die universelle Steuerungsvorrichtung (100) konfiguriert ist, das eine von der Vielzahl von HF-Kommunikationsprotokollen auszuwählen, welches von der Verarbeitungsvorrichtung (100) in Kommunikation mit der HF-Kommunikationsschaltung (210) verwendet werden soll, um HF-Kommunikationen mit der vorgesehenen Zielvorrichtung (104) als Reaktion auf eine Auswahl eines von der Vielzahl von Schnelleinrichtungseingabeelementen (302) auszutauschen während die universelle Steuerungsvorrichtung (100) sich in einem Einrichtungsmodus des Betriebs befindet und</claim-text>
<claim-text><b>dadurch gekennzeichnet, dass</b><!-- EPO <DP n="19"> --></claim-text>
<claim-text>die Verarbeitungsschaltung (200) in Kommunikation mit der HF-Kommunikationsschaltung (210) konfiguriert ist, eine Anfragenachricht unter Verwendung des ausgewählten einen von der Vielzahl von HF-Kommunikationsprotokollen an die vorgesehene Zielvorrichtung (104) zu senden, und die universelle Steuerungsvorrichtung (100) konfiguriert ist, wenn eine Antwort von der vorgesehenen Zielvorrichtung (104) erfolgreich empfangen wird, als Reaktion auf die Anfragenachricht mit der vorgesehenen Zielvorrichtung (104) gekoppelt zu werden, sodass die Verarbeitungsschaltung (200) in Kommunikation mit der HF-Kommunikationsschaltung (210) das ausgewählte eine von der Vielzahl von HF-Kommunikationsprotokollen verwenden wird, wenn die universelle Steuerungsvorrichtung (100) nachfolgend in einen Betriebsmodus versetzt wird, in welchem die universelle Steuerungsvorrichtung (100) vorgesehen ist, Kommunikationen mit der vorgesehenen Zielvorrichtung (104) auszutauschen.</claim-text></claim-text></claim>
<claim id="c-de-01-0010" num="0010">
<claim-text>Universelle Steuerungsvorrichtung (100) nach Anspruch 9, wobei die universelle Steuerungsvorrichtung (100) eine Vielzahl von Vorrichtungsmoduseingabeelementen umfasst und wobei eine Aktivierung eines Vorrichtungsmoduseingabeelements (314) der universellen Steuerungsvorrichtung (100) den Vorrichtungstyp der vorgesehenen Zielvorrichtung (104) angibt.</claim-text></claim>
<claim id="c-de-01-0011" num="0011">
<claim-text>Universelle Steuerungsvorrichtung (100) nach Anspruch 10, wobei das Vorrichtungsmoduseingabeelement (314) konfiguriert ist, wenn es aktiviert ist, eine von einer Vielzahl von vorbestimmten Verknüpfungen zwischen der Vielzahl von Schnelleinrichtungseingabeelementen (302) und einem von einer Vielzahl von HF-Kommunikationsprotokollen auszuwählen.</claim-text></claim>
<claim id="c-de-01-0012" num="0012">
<claim-text>Universelle Steuerungsvorrichtung (100) nach Anspruch 9, wobei die universelle Steuerungsvorrichtung (100) ein Einrichtungseingabeelement (310) umfasst und die universelle Steuerungsvorrichtung (100) veranlasst wird, als Reaktion auf eine Aktivierung des Einrichtungseingabeelements (310), eine Aktivierung des Einrichtungseingabeelements (310) für eine vorbestimmte Zeitspanne, eine gleichzeitige Aktivierung des Einrichtungseingabeelements (310) und eines von den Schnelleinrichtungseingabeelementen (302), oder eine gleichzeitige Aktivierung des<!-- EPO <DP n="20"> --> Einrichtungseingabeelements (310) und eines von den Schnelleinrichtungseingabeelementen (302) für eine vorbestimmte Zeitspanne in den Einrichtungsmodus einzutreten.</claim-text></claim>
</claims>
<claims id="claims03" lang="fr"><!-- EPO <DP n="21"> -->
<claim id="c-fr-01-0001" num="0001">
<claim-text>Procédé de configuration d'un dispositif de commande universel (100) pour échanger des communications avec un dispositif cible prévu (104) via un canal de communication RF, comprenant :
<claim-text>la réception dans le dispositif de commande universel (100), tandis qu'il est dans un mode installation, d'une sélection de l'un d'une pluralité d'éléments d'entrée d'installation rapide (302) du dispositif de commande universel (100), dans lequel chacun de la pluralité d'éléments d'entrée d'installation rapide (302) est lié à l'un d'une pluralité de protocoles de communication RF utilisables par le dispositif de commande universel (100) pour échanger des communications avec un type de dispositif du dispositif cible prévu (104) ;</claim-text>
<claim-text><b>caractérisé en ce qu'</b>il comprend les étapes de</claim-text>
<claim-text>l'utilisation de l'un de la pluralité de protocoles de communication RF liés à l'élément sélectionné de l'un de la pluralité d'éléments d'entrée d'installation rapide (302) par le dispositif de commande universel (100) pour émettre un message d'interrogation (906) au dispositif cible prévu (104) ; et</claim-text>
<claim-text>en réponse à la réception réussie d'un message par le dispositif de commande universel (100) en provenance du dispositif cible prévu (104) transmis en réponse au message d'interrogation, le fait d'amener le dispositif de commande universel (100) à être apparié au dispositif cible prévu (104), après quoi le dispositif de commande universel (100) utilisera l'un sélectionné de la pluralité de protocoles de communication RF lorsque le dispositif de commande universel (100) est par la suite placé dans un mode de fonctionnement dans lequel le dispositif de commande universel (100) est destiné à échanger des communications avec le dispositif cible prévu (104).</claim-text></claim-text></claim>
<claim id="c-fr-01-0002" num="0002">
<claim-text>Procédé selon la revendication 1, dans lequel le type de dispositif du dispositif cible prévu (104) comprend un type de boîtier décodeur (104).</claim-text></claim>
<claim id="c-fr-01-0003" num="0003">
<claim-text>Procédé selon la revendication 1, le fait d'amener le dispositif de commande universel (100) à utiliser un protocole IR lorsque le dispositif de commande universel (100) est placé dans un mode de fonctionnement dans lequel le dispositif de<!-- EPO <DP n="22"> --> commande universel (100) est destiné à transmettre des communications à un dispositif d'un type de dispositif autre que le type de dispositif du dispositif cible prévu (104).</claim-text></claim>
<claim id="c-fr-01-0004" num="0004">
<claim-text>Procédé selon la revendication 1, comprenant la réception dans le dispositif de commande universel (100), tandis qu'il est dans le mode installation, de données indicatives du type de dispositif du dispositif cible prévu (104).</claim-text></claim>
<claim id="c-fr-01-0005" num="0005">
<claim-text>Procédé selon la revendication 4, comprenant l'utilisation des données indicatives du type de dispositif pour lier la pluralité d'éléments d'entrée d'installation rapide (302) à l'un d'une pluralité de protocoles de communication RF utilisables pour échanger des communications avec le type de dispositif du dispositif cible prévu (104).</claim-text></claim>
<claim id="c-fr-01-0006" num="0006">
<claim-text>Procédé selon la revendication 1, dans lequel chacun de la pluralité d'éléments d'entrée d'installation rapide (302) est lié à un d'une pluralité de protocoles de communication RF utilisables pour échanger des communications avec un type de dispositif du dispositif cible prévu (104) à un moment de fabrication du dispositif de commande universel (100).</claim-text></claim>
<claim id="c-fr-01-0007" num="0007">
<claim-text>Procédé selon la revendication 1, dans lequel chacun de la pluralité d'éléments d'entrée d'installation rapide (302) est lié à un d'une pluralité de protocoles de communication RF utilisables pour échanger des communications avec un type de dispositif du dispositif cible prévu (104) à un moment avant le déploiement du dispositif de commande universel (100).</claim-text></claim>
<claim id="c-fr-01-0008" num="0008">
<claim-text>Procédé selon la revendication 1, comprenant le fait d'amener le dispositif de commande universel (100) à entrer dans le mode installation (904) en réponse à une activation d'un élément d'entrée d'installation (310) du dispositif de commande universel (100), une activation d'un élément d'entrée d'installation (310) du dispositif de commande universel (100) pendant une période de temps prédéterminée, une activation simultanée d'un élément d'entrée d'installation (310) du dispositif de commande universel (100) et d'un des éléments d'entrée d'installation rapide (302), ou une activation simultanée d'un élément d'entrée d'installation (310) du dispositif de<!-- EPO <DP n="23"> --> commande universel et d'un des éléments d'entrée d'installation rapide (302) pendant une période de temps prédéterminée.</claim-text></claim>
<claim id="c-fr-01-0009" num="0009">
<claim-text>Dispositif de commande universel (100), comprenant :
<claim-text>un circuit de communications RF (210) ;</claim-text>
<claim-text>une unité de traitement (200) en communication avec le circuit de communications RF (210) configurée pour amener le circuit de communications RF à échanger des communications RF avec un dispositif cible prévu (104) en utilisant un protocole sélectionné d'une pluralité de protocoles de communication RF ; et</claim-text>
<claim-text>une matrice clé (216) ayant une pluralité d'éléments d'entrée d'installation rapide (302), dans lequel chacun de la pluralité d'éléments d'entrée d'installation rapide (302) est lié à un d'une pluralité de protocoles de communication RF utilisables par le circuit de traitement (200) en communication avec le circuit de communications RF (210) pour échanger des communications avec un type de dispositif du dispositif cible prévu (104) ;</claim-text>
<claim-text>dans lequel le dispositif de commande universel (100) est configuré pour sélectionner l'un de la pluralité de protocoles de communication RF à utiliser par le dispositif de traitement (100) en communication avec le circuit de communications RF (210) pour échanger des communications RF avec le dispositif cible prévu (104) en réponse à une sélection d'un de la pluralité d'éléments d'entrée d'installation rapide (302) tandis que le dispositif de commande universel (100) est dans un mode de fonctionnement d'installation et</claim-text>
<claim-text><b>caractérisé en ce que</b></claim-text>
<claim-text>le circuit de traitement (200) en communication avec le circuit de communications RF (210) est configuré pour transmettre un message d'interrogation au dispositif cible prévu (104) en utilisant l'un sélectionné de la pluralité de protocoles de communication RF et le dispositif de commande universel (100) est configuré, lorsqu'une réponse est reçue avec succès en provenance du dispositif cible prévu (104) en réponse au message d'interrogation, pour être apparié au dispositif cible prévu (104) de sorte que le circuit de traitement (200) en communication avec le circuit de communications RF (210) utilisera l'un sélectionné de la pluralité de protocoles de communication RF lorsque le dispositif de commande universel (100) est par la suite placé dans un mode de fonctionnement dans lequel le dispositif de commande<!-- EPO <DP n="24"> --> universel (100) est destiné à échanger des communications avec le dispositif cible prévu (104).</claim-text></claim-text></claim>
<claim id="c-fr-01-0010" num="0010">
<claim-text>Dispositif de commande universel (100) selon la revendication 9, dans lequel le dispositif de commande universel (100) comprend une pluralité d'éléments d'entrée de mode de dispositif et dans lequel une activation d'un élément d'entrée de mode de dispositif (314) indique au dispositif de commande universel (100) le type de dispositif du dispositif cible prévu (104).</claim-text></claim>
<claim id="c-fr-01-0011" num="0011">
<claim-text>Dispositif de commande universel (100) selon la revendication 10, dans lequel l'élément d'entrée de mode de dispositif (314) est configuré, lorsqu'il est activé, pour sélectionner l'une d'une pluralité de liaisons prédéterminées entre la pluralité d'éléments d'entrée d'installation rapide (302) et l'un d'une pluralité de protocoles de communication RF.</claim-text></claim>
<claim id="c-fr-01-0012" num="0012">
<claim-text>Dispositif de commande universel (100) selon la revendication 9, dans lequel le dispositif de commande universel (100) comprend un élément d'entrée d'installation (310) et le dispositif de commande universel (100) est amené à entrer dans le mode installation en réponse à une activation de l'élément d'entrée d'installation (310), une activation de l'élément d'entrée d'installation (310) pendant une période de temps prédéterminée, une activation simultanée de l'élément d'entrée d'installation (310) et d'un des éléments d'entrée d'installation rapide (302), ou une activation simultanée de l'élément d'entrée d'installation (310) et d'un des éléments d'entrée d'installation rapide (302) pendant une période de temps prédéterminée.</claim-text></claim>
</claims>
<drawings id="draw" lang="en"><!-- EPO <DP n="25"> -->
<figure id="f0001" num="1"><img id="if0001" file="imgf0001.tif" wi="138" he="200" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="26"> -->
<figure id="f0002" num="2"><img id="if0002" file="imgf0002.tif" wi="138" he="191" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="27"> -->
<figure id="f0003" num="3"><img id="if0003" file="imgf0003.tif" wi="87" he="211" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="28"> -->
<figure id="f0004" num="4,5"><img id="if0004" file="imgf0004.tif" wi="153" he="221" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="29"> -->
<figure id="f0005" num="6"><img id="if0005" file="imgf0005.tif" wi="145" he="232" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="30"> -->
<figure id="f0006" num="7"><img id="if0006" file="imgf0006.tif" wi="165" he="217" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="31"> -->
<figure id="f0007" num="8"><img id="if0007" file="imgf0007.tif" wi="165" he="219" img-content="drawing" img-format="tif"/></figure><!-- EPO <DP n="32"> -->
<figure id="f0008" num="9"><img id="if0008" file="imgf0008.tif" wi="82" he="222" img-content="drawing" img-format="tif"/></figure>
</drawings>
<ep-reference-list id="ref-list">
<heading id="ref-h0001"><b>REFERENCES CITED IN THE DESCRIPTION</b></heading>
<p id="ref-p0001" num=""><i>This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.</i></p>
<heading id="ref-h0002"><b>Patent documents cited in the description</b></heading>
<p id="ref-p0002" num="">
<ul id="ref-ul0001" list-style="bullet">
<li><patcit id="ref-pcit0001" dnum="US4623887A"><document-id><country>US</country><doc-number>4623887</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0001">[0001]</crossref></li>
<li><patcit id="ref-pcit0002" dnum="US4774511A"><document-id><country>US</country><doc-number>4774511</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0002">[0002]</crossref></li>
<li><patcit id="ref-pcit0003" dnum="US4959810A"><document-id><country>US</country><doc-number>4959810</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0003">[0002]</crossref><crossref idref="pcit0004">[0002]</crossref><crossref idref="pcit0019">[0018]</crossref><crossref idref="pcit0027">[0031]</crossref><crossref idref="pcit0030">[0032]</crossref></li>
<li><patcit id="ref-pcit0004" dnum="US5451953A"><document-id><country>US</country><doc-number>5451953</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0005">[0002]</crossref></li>
<li><patcit id="ref-pcit0005" dnum="US5614906A"><document-id><country>US</country><doc-number>5614906</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0006">[0002]</crossref><crossref idref="pcit0020">[0018]</crossref><crossref idref="pcit0025">[0031]</crossref><crossref idref="pcit0026">[0031]</crossref><crossref idref="pcit0029">[0032]</crossref></li>
<li><patcit id="ref-pcit0006" dnum="US665642A" dnum-type="L"><document-id><country>US</country><doc-number>665642</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0007">[0003]</crossref></li>
<li><patcit id="ref-pcit0007" dnum="US7218243B"><document-id><country>US</country><doc-number>7218243</doc-number><kind>B</kind></document-id></patcit><crossref idref="pcit0008">[0003]</crossref></li>
<li><patcit id="ref-pcit0008" dnum="US6225398B"><document-id><country>US</country><doc-number>6225398</doc-number><kind>B</kind></document-id></patcit><crossref idref="pcit0009">[0003]</crossref></li>
<li><patcit id="ref-pcit0009" dnum="US6157319A"><document-id><country>US</country><doc-number>6157319</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0010">[0003]</crossref></li>
<li><patcit id="ref-pcit0010" dnum="US5515052A"><document-id><country>US</country><doc-number>5515052</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0011">[0004]</crossref><crossref idref="pcit0024">[0026]</crossref></li>
<li><patcit id="ref-pcit0011" dnum="US389627A" dnum-type="L"><document-id><country>US</country><doc-number>389627</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0012">[0004]</crossref></li>
<li><patcit id="ref-pcit0012" dnum="US6938101A"><document-id><country>US</country><doc-number>6938101</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0013">[0005]</crossref></li>
<li><patcit id="ref-pcit0013" dnum="WO2005043484A"><document-id><country>WO</country><doc-number>2005043484</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0014">[0005]</crossref></li>
<li><patcit id="ref-pcit0014" dnum="US20100123613A"><document-id><country>US</country><doc-number>20100123613</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0015">[0005]</crossref></li>
<li><patcit id="ref-pcit0015" dnum="US5481256A"><document-id><country>US</country><doc-number>5481256</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0016">[0017]</crossref></li>
<li><patcit id="ref-pcit0016" dnum="US5959751A"><document-id><country>US</country><doc-number>5959751</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0017">[0017]</crossref></li>
<li><patcit id="ref-pcit0017" dnum="US6014092A"><document-id><country>US</country><doc-number>6014092</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0018">[0017]</crossref></li>
<li><patcit id="ref-pcit0018" dnum="US6225938B"><document-id><country>US</country><doc-number>6225938</doc-number><kind>B</kind></document-id></patcit><crossref idref="pcit0021">[0018]</crossref></li>
<li><patcit id="ref-pcit0019" dnum="US5953144A"><document-id><country>US</country><doc-number>5953144</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0022">[0020]</crossref></li>
<li><patcit id="ref-pcit0020" dnum="US6223348B"><document-id><country>US</country><doc-number>6223348</doc-number><kind>B</kind></document-id></patcit><crossref idref="pcit0023">[0020]</crossref></li>
<li><patcit id="ref-pcit0021" dnum="US4703359A"><document-id><country>US</country><doc-number>4703359</doc-number><kind>A</kind></document-id></patcit><crossref idref="pcit0028">[0031]</crossref><crossref idref="pcit0031">[0032]</crossref></li>
</ul></p>
</ep-reference-list>
</ep-patent-document>
