Remote control device and system
Abstract
Problem to be solved.To control many functions without increasing the size and complexity, to control a controlled device having new functions, and to perform general-purpose function control easily by remote control. Provide the device. A remote control device, a commander 16, accesses, for example, a controlled device 11 via a network to acquire a self-described file, and assigns known functions, which are general-purpose functions, to key switches 41 to 56. , Other unknown functions are set up to be displayed on the display 36 as icons on the hierarchical menu page. With this setup, the commander 16 functions as a commander for the controlled device 11. [Selection diagram] Fig. 2

Term
Projected expiry 12 December 2028.
- Priority and filed
- Published
- Today
- Projected expiry
5 claims: 1 independent, 4 dependent
- 1被制御機器の機能制御コマンドが対応づけられた画像または文字が表示されるディスプレイと、 前記ディスプレイ上の前記画像または文字の指定操作を受け付けるポインティング操作部と、 前記被制御機器の所定の機能制御コマンドが対応づけられる1または複数のコマンドキーと、 前記被制御機器の複数の機能制御コマンドが記述された自己記述ファイルを取得し、 この自己記述ファイルに記述されている複数の機能制御コマンドのうち、前記所定の機能制御コマンドを前記キースイッチに対応づけるとともに、それ以外の機能制御コマンドが対応づけられた画像または文字を前記ディスプレイに表示し、 前記コマンドキーが操作されたとき、そのコマンドキーに対応づけられている機能制御コマンドを発行し、前記ポインティング操作部により前記ディスプレイに表示された画像または文字が指定されたとき、その画像または文字に対応づけられている機能制御コマンドを発行する制御部と、 を備えた遠隔制御装置。
- 2所定のページへの移動処理が対応づけられるページキーをさらに備え、 前記制御部は、前記ディスプレイは、前記機能制御コマンドが対応づけられた画像または文字を複数ページにわたって表示するとともに、該複数ページのうち一部または全部に、他のページへの移動処理が対応づけられた画像または文字を表示し、さらに、前記ページキーに所定ページへの移動処理を対応づける 請求項1に記載の遠隔制御装置。
- 3所定の機能が対応づけられるファンクションキーをさらに備え、 前記制御部は、前記ディスプレイに表示しているページに応じて、前記機能制御コマンドおよび/または他ページへの移動処理を前記ファンクションキーに対応づける 請求項2に記載の遠隔制御装置。
- 4前記被制御機器の自己記述ファイルは、通信により当該被制御機器から取得される請求項1乃至請求項3のいずれかに記載の遠隔制御装置。
- 5請求項4に記載の遠隔制御装置と、 少なくとも、前記遠隔制御装置と通信する通信手段、および、前記自己記述ファイルを記憶する記憶手段を備えた1または複数の被制御機器と、 を有する遠隔制御システム。
Independent claims5
72 paragraphs, as filed
The present invention relates to a remote control device capable of controlling a plurality of controlled devices, and a remote control system including the remote control device and the controlled device.
In recent years, the number of electric devices capable of remote control by command signals such as infrared rays is increasing. For this reason, a learning remote control system has been proposed in which command signals of a plurality of electric devices (controlled devices) can be stored and one device can control many devices (for example, Patent Document 1). In the learning remote control system of Patent Document 1, when a necessary command is selected from the commands listed on the controlled device, the selected commands are collectively stored in the learning remote control device. This saves the trouble of learning multiple command signals one by one.
<patcit num="1"><text>Japanese Unexamined Patent Publication No. 2004-072384</text></patcit>
<p> As described above, in the learning remote control system of Patent Document 1, a plurality of command signals can be collectively learned from the controlled device to the remote control device, which facilitates learning, but is controlled by the learning remote control device. The functions that can be performed are limited to the functions that can be assigned to the key switches of the learning remote controller, and many key switches are required to control many functions, which causes a problem that the remote controller becomes large and complicated. There was a point. In addition, a learning operation was still required for the remote control device to be able to control a new controlled device.</p><p> According to the present invention, many functions can be controlled without increasing the size and complexity, a controlled device having new functions can be controlled, and general-purpose function control can be easily operated by remote control. It is an object of the present invention to provide an operation device and a remote control system.</p>
<p> The remote control device according to claim 1 of the present application includes a display on which an image (such as an icon) or a character (such as a menu list) associated with a function control command of a controlled device is displayed, and the display. A pointing operation unit that accepts the above image or character designation operation, one or more command keys associated with a predetermined function control command of the controlled device, and a plurality of function control commands of the controlled device are described. The self-described file is acquired, and among the plurality of function control commands described in this self-description file, the predetermined function control command is associated with the key switch, and other function control commands are associated with each other. The image or character is displayed on the display, and when the command key is operated, a function control command associated with the command key is issued, and the image or character displayed on the display by the pointing operation unit is issued. It is characterized by including a control unit that issues a function control command associated with the image or the character when a character is specified.</p><p> The invention of claim 2 further includes, in the invention of claim 1, a page key to which the process of moving to a predetermined page is associated, the control unit, the display, and the image to which the function control command is associated. Alternatively, the characters are displayed over a plurality of pages, and an image or characters associated with the process of moving to another page are displayed on a part or all of the plurality of pages, and the page key is used to move to a predetermined page. It is characterized by associating movement processing.</p><p> The invention of claim 3 further includes a function key to which a predetermined function is associated with the invention of claim 2, and the control unit performs the function control command and / or the function control command according to the page displayed on the display. Alternatively, it is characterized in that the process of moving to another page is associated with the function key.</p><p> The invention of claim 4 is characterized in that, in the inventions of claims 1 to 3, the self-description file of the controlled device is acquired from the controlled device by communication. The remote control system according to claim 5 of the present application includes the remote control device of claim 4, at least a communication means for communicating with the remote control device, and a storage means for storing the self-description file. It is characterized by having one or more controlled devices.</p>
<p> According to the present invention, by providing a display and a command key, general-purpose functions (power on / off, etc.) can be associated with the command key to improve operability, and other functions can be displayed. It is possible to control many functions and new functions that have not existed in the past without increasing the number of key switches by associating them with images such as icons displayed on the screen or characters such as menu lists.</p><p> In addition, if the self-described file is automatically acquired, it is possible to set up a remote control device (commander) that operates the controlled device without the user performing a learning operation.</p>
<< Outline explanation of audio network and this invention >> FIG. 1 is a diagram showing a configuration of an audio system to which the present invention is applied. This type of audio network system is called a custom installation and is installed in a large detached house.
The audio device group 10 composed of a plurality of audio devices is housed in a rack provided on the wall of the living room, for example. As the audio device group 10, there are source devices such as AV receivers 11 and 12, a DVD player 13 that supplies an audio source to the AV receivers 11 and 12, and a personal computer (PC) 14. Audio equipment such as AV receivers 11 and 12 DVD players 13 includes audio circuit units 11A, 12A, 13A that reproduce and amplify audio signals, and control units 11B, 12B, 13B that control the operation of the equipment. In addition, AV receivers 11 and 12 have built-in tuners 11C and 12C that receive FM / AM broadcasts as source devices. Since the PC14 stores an audio file on the hard disk and plays it back by the CPU, it is indistinguishable from the control unit in terms of hardware, but the audio playback function unit of the PC14 controls the audio circuit unit 14A and the control function unit. Called part 14B. As described above, the configuration of the audio devices constituting the audio device group 10 is arbitrary and is not limited to the above. Source devices other than those shown include audio playback devices with built-in micro HDD drives, PCs, and the like.
The AV receiver 11 connects a source device such as the above DVD player 13 or PC 14 to the input side, and supplies an audio signal input from any of the plurality of source devices to the three zones (rooms). In order to supply an audio signal to each zone independently, the AV receiver 11 has three audio amplifiers. Further, the AV receiver 12 connects a source device such as the above DVD player 13 or PC 14 to the input side, and supplies an audio signal input from any of the plurality of source devices to one zone (room). This AV receiver 12 does not have a power amplifier, and transmits an audio signal to the amplifier 23 in the zone in charge via an optical fiber or the like.
Each of the four zones Z1 to 4 is a room inside the house, for example, zone 1 (Z1) is a living room (Livng), zone 2 (Z2) is a bedroom (Bed Room), and zone 3 (Z3) is a children's room (Kids). Room), Zone 4 (Z4) is the kitchen. Speakers 21 and wireless LAN access points 22 are installed in zones 1 to 4. In addition, an amplifier 23 is further installed in zone 4. An audio signal power-amplified by the AV receiver 11 is applied to the speakers 21 in zones 1 to 3. Further, in zone 4, the amplifier 23 receives the infrared audio signal of the AV receiver 12, amplifies the signal, and applies it to the speaker 21.
The control units 11B, 12B, 13B, 14B and access point 22 of each audio device are connected to each other by LAN15. LAN15 is connected to the Internet by a router (not shown), but each device (control 11B, 12B, 13B, 14B and access point 22, commander 16) is given a local IP address when connected to LAN15. Each device can access each other using its local IP address. The commander 16 which is a control device searches on the LAN 15 to detect an audio device which is a controlled device and acquires an IP address thereof. After that, it communicates with each audio device using this IP address. The LAN 15 may be in any form of a wired LAN, a wireless LAN, and a composite of a wired LAN and a wireless LAN.
The commander (remote controller) 16 according to the embodiment of the present invention communicates with the control units 11B, 12B, 13B, 14B of each audio device via the access point 22 by wireless LAN. In this figure, there is one commander 16, and this one commander 16 is used by moving it in four zones, but it is a form in which the commander 16 is in each zone. You may.
In the audio system having the above configuration, the user can use the commander 16 to control the audio device in the zone in which he / she is present and listen to desired music. The commander 16 receives a self-described file including a command list from audio devices 11 to 14 which are controlled devices via LAN 15, and sends each command to key switches 41 to 56 (see FIG. 2) and displays 36 which are hard switches. Assign to the menu displayed in (see Fig. 2), and issue (send) commands to audio devices 11 to 14 according to the on operation of key switches 41 to 56 or the selection of the menu. Therefore, one commander 16 can control all the audio devices 11 to 14.
Explanation of commander and audio equipment FIG. 2 is an external view of Commander 16. FIG. 3 is a block diagram of Commander 16. The commander 16 has a thin rectangular parallelepiped shape having a plane shape approximately the size of a postcard, and the upper surface thereof is an operation surface. FIG. 2 is a plan view showing the operation surface. A liquid crystal display 36 is provided slightly to the left of the center. A touch pad 37 is provided on the upper right side of the display 36. The touchpad 37 is a device for moving the cursor on the display 36 and selecting the object pointed to by the cursor. The cursor moves when the user touches it with his or her fingertip and moves the fingertip. Also, when the user taps the fingertip lightly, the object pointed to by the cursor is selected.
Further, a key switch group 35 is provided from the left side to the lower side of the operation surface. The key switch group 35 consists of 16 key switches 41 to 56. Along the left side of the operation surface, a zone selection key 41, an input selection key 42, a volume up / down key 43, 44, and a mute switch 45 are provided. The zone selection key 41 is a key switch for displaying the selection screens of the four zones Z1 to Z4 shown in FIG. The input selection key 42 is a key switch for displaying the selection screen of the source device to be played back in the selected zone. Volume up / down keys 43, 44 and mute switch 45 are key switches for raising or lowering or temporarily muting the playback volume of content (eg, audio) currently being played on the selected source device.
Three function keys 47, 48, and 49 are provided along the bottom edge of the display 36. The function keys 47, 48, and 49 are assigned various functions according to the operation stage.
Below the touchpad 37, a back key 51, a home key 52, and various performance control keys 53 to 56 are provided. The back key 51 is a key switch for returning the screen displayed on the display 36 to the previous one. The home key 52 is a key switch that switches the screen displayed on the display 36 to the initial screen. The performance operation keys 53 to 56 include a start key 53, a stop key 54, a rewind key 55, and a fast forward (skip) key 56.
In FIG. 3, the commander 16 has a CPU 31, a ROM 32, and a RAM 33, as well as a wireless LAN controller 34, a key switch group 35, a display 36, and a touch pad 37, which are connected to each other via a bus. There is. The ROM 32 stores a program or the like for controlling the commander 16. The wireless LAN control unit 34 communicates with the audio devices 11 to 14 which are controlled devices via the access point 22, and receives a self-described file, performance information, and the like. The RAM 33 stores the self-described files and performance information of the audio devices 11 to 14 received by the wireless LAN controller 34.
The CPU 31 sets up its own device as a commander for controlling the controlled device based on the self-described file of the controlled device stored in the RAM 33. The "known functions" in the self-described file are associated with the key switches 41 to 56 of the key switch group 35 to which each function is assigned, and the functions (unknown functions) for which no other key switches are assigned are It is displayed as a layered menu on the display 36, and commands are associated with the menu items on the bottom layer.
FIG. 4 is a block diagram of audio devices 11 to 14. The audio devices 11 to 14 have their own configuration in the audio circuit section 69 (corresponding to 11A, 12A, 13A, 14A), but the configuration of the control section 60 (corresponding to 11B, 12B, 13B, 14B) is almost the same. is there. The control unit 60 has a configuration in which the CPU 61, the non-volatile memory 62, the RAM 63, the LAN controller 64, the operation unit 65, and the interface 66 are connected to each other by a bus. A self-described file is stored in the non-volatile memory 62. The RAM63 stores performance information such as the artist name, album name, and song name being played. The LAN controller 64 communicates with another device (for example, commander 16) via the LAN 15. The CPU 61 controls the operation of the audio circuit unit 69 based on the operation of the operation unit 65 and the control command received by the LAN controller 64. Further, the performance information is received from the audio circuit unit 69 via the interface 66 and written to the RAM 63. Further, the CPU 61 makes the control unit 60 function as an http server so that the commander 16 can acquire the self-described file on the non-volatile memory 62 and the performance information on the RAM 63 by the GET method of http.
Explanation of self-written file The self-description file is a file transmitted from the audio devices 11 to 14 to the commander 16 so that the commander 16 can control the audio devices 11 to 14 which are controlled devices. By receiving the self-written file, the commander 16 can at least power the audio device (on / off, sleep setting), volume (volume level, mute on / off), and input switching (various connected sources). Controls such as device selection), playback control (play, pause, stop, etc.), playback information display (artist, album name, song name), content browsing (content list display, cursor operation, etc.) are possible. The functions listed here are referred to as "known functions".
FIG. 5 is a diagram showing an example of a self-described file. The self-described file is stored in the non-volatile memory (hard disk or flash memory) of the audio devices 11 to 14 which are the controlled devices, and is open to the public on LAN15. Commander 16 can freely retrieve the self-written file by accessing the directory.
Figure 5 shows a description example of a self-description file. As shown in the figure, the self-description file (Unit Description) is described in a structured language (XML language). The Menu tag <Menu> is used to describe the menu structure. Hierarchical menus are expressed by nesting this Menu tag.
The Menu tag <Menu> is a tag that is the basis of the hierarchical menu description in the self-described file as described above, and a plurality of attributes are described inside the tag. That is, while constructing the hierarchical structure of the menu with the Menu tag, various supplementary information such as the control target of the menu and the display form are given by the attributes. The attributes described in the Menu tag include Title_x attribute, Icon attribute, List_Type attribute, YNC_Tag attribute, Func attribute, and so on.
For example, the Menue tag 101 in FIG. 5 describes Func = Subunit, Title_1 = Main Zone and YNC_Tag = Main_Zone as attributes and their values, and Menu tag 102 describes the attributes and their values. , Func = Vol, Title_1 = Volume""and Icon = xxxx / yyyy.png are described.
The Title_x attribute is an attribute that represents the name of the controlled device / function of this Menu tag. Since one Menu tag may have attributes with multiple names assuming notation in multiple languages, x in Title_x is set to a numerical value in order from 1.
The Icon attribute is an attribute that specifies the icon of the controlled device / function of this Menu tag. The Icon attribute is an attribute described when an icon is used as a display form of this menu item on the display 36. The icon designation is described by the file name and the path name of the file. For example, "Icon =" icon / listen.png "". Since the path described is the path from the root of the http server installed in the controlled device, add the IP address of the controlled device here and access it with the http GET method to get the icon image file. To do. In the case of the above "Icon =" icon / listen.png "" example, the icon image file is acquired by "GET http://192.168.0.1/icon/listen.png". Note that this URL, file name, etc. are examples and are not limited to this.
The List_Type attribute is an attribute that describes the list format recommended when displaying the menu one level below this Menu tag. Attribute values (list format) include Menu, Icon, Slider, 10Key, etc. When the attribute value is Menu, the menu format with normal list display is recommended. This Menu format is the default and can be omitted. When the attribute value is Icon, the menu format using icons is recommended. When this Icon is recommended, the icon path is always described by the Icon attribute in the menu item of the next lower hierarchy. When the attribute value is Slider, the lower menu item is a numerical menu item, and it is recommended to build the menu on the assumption that it will be input by the slider. When the attribute value is 10Key, the lower menu item is a numerical menu item, and it is recommended to construct the menu by entering the numeric keypad. If it is not possible to build / display the menu in the recommended format due to circumstances (due to hardware, software, etc.), the default Menu format menu will be displayed.
The YNC_Tag attribute is an attribute that describes the name of the controlled zone or controlled device. The description below the Menu tag in which this attribute is described indicates that the description relates to a zone or source device having the name of this attribute. The Func attribute is an attribute that represents the controlled function. The values of the Func attribute are layered across other types. Figure 6 shows an example of the value of the Func attribute of the Menu tag.
FIG. 7 is a diagram showing a part of the description of the bottom layer menu among the descriptions of the self-description file. Further, FIG. 8 is a diagram showing an example of a menu configured by writing out the Title_x attribute in the Menu tag of this self-described file. This bottom layer menu is described as, for example, the bottom layer of the Menu tag 102 in FIG. In the bottom layer menu, in addition to the Menu tag, tags such as Cmd tag <Cmd>, Cmd_List <Cmd_List> tag, and Param_x tag <Param_x> are used to issue commands according to the user's operation. ing.
The Cmd tag is a tag that instructs command issuance, and the ID of the issued command (PUT command in this example) is described. As shown in FIG. 7, the character string Param_x is always described in the Cmd tag element 105, and the Param_x tag, which is a tag having the same name, is described following the Cmd tag. The parameter that can be selected as the lowest item of the menu is described in this Param_x tag element 106. Since multiple Param_x tags may be described, a number in order from 1 is set for x for identification. At least one of the following tags is placed under the Param_x tag.
The Direct tag <Direct> is a tag used when directly describing a parameter, and a character string of the parameter is described after the start tag. The required number of Direct tags are described in the area of the Param_x tag. In the Mute control in Fig. 7, two parameters "On" and "Off" are described in the Direct tag. In addition, the Drect tag may be accompanied by the Title_x attribute and Icon attribute. The Title_x attribute is an attribute that represents the name of the parameter, and the Icon tag is an attribute that specifies an icon image when the parameter (control content) is displayed as an icon when it is displayed as a menu item on the display 36.
The Range tag <Range> is a tag used when describing a parameter range and a step, and is described in the form of "<start value>, <end value>, <step>". The menu displays a step-by-step numerical list from the start value to the end value. In the volume level control in Fig. 7, the start value = -80.5 dB, the end value = 16.5 dB, and the step = 0.5 dB, and the menu shows the gain value in 0.5 dB increments between -80.5 dB and 16.5 dB. Is listed as a menu item. In addition to this, there are Text tag <Text> (tag for describing the character number range and character type of the parameter) and Indirect tag <Indirect> (tag when the parameter is acquired by the GET command).
In Commander 16, mute on / off is assigned to the key switch (mute key) 45, and volume control of -80.5 dB to 16.5 dB is assigned to the key switches (volume up / down keys) 43 and 44. Since the mute key 45 is a toggle operation, when assigning the mute on / off function to the mute key 45, the mute on / off state of the controlled device (main zone) is acquired by the GET command. After that, when the mute key 45 is turned on, a command is issued to set the state opposite to the state at that time. The mute-on command is, for example, a conversion of the character string "Main_Zone, Vol_Control, Mute, On" into XML format. Also, since the volume up / down keys 43,44 are key switches that instruct one step increase / decrease from the current value, when assigning the volume control function to the volume up / down keys 43,44, use the GET command to control the device. Get the volume level value of. After that, when the volume up / down keys 43 and 44 are turned on, a command is issued with the volume level value increased / decreased by one step from the volume value at that time as a parameter. The volume level control command is, for example, a conversion of the character string "Main_Zone, Vol_Control, Level, -25.0" into XML format.
Here, the GET command is a command issued by the GET tag, and is issued when some information is obtained from the controlled device.
The command actually issued is described in the Cmd_List tag <Cmd_List> shown in Fig. 7. Only one Cmd_List tag is described for each Func = Subunit or Func = Source_Device attribute in the Menu tag. The description position is at the end of the tag one level below, and the range of influence is the entire tag and below.
One or more Define tags <Define> are always placed in the lower hierarchy in the Cmd_List tag element 107. The Define tag 108 always has an ID attribute, and the command described below is specified by this ID attribute. As mentioned above, on the Cmd tag side, the command to be issued is specified by specifying this ID.
As shown in FIG. 7, at least one Define tag is described in the Cmd_List tag element 107, usually a plurality of Define tags, and a command (command body) identified by an ID is described in each. The commands are separated by commas and converted to XML format at the time of issuance.
In this way, the bottom layer of the hierarchical menu has a description for issuing commands, the commands actually issued are described in the area of Cmd_List, and the command body specified by the attribute of the Cmd tag and It consists of a combination of parameters described in the area of the Cmd tag. In general, one command body comes with multiple (possibly many) parameters, so it is possible to issue many types of commands with one command body.
Further, FIG. 9 is a diagram showing a part where the FKey tag <FKey> is described, which is another part of the self-description file.
The FKey tag is a tag used when assigning a specific function to function keys 47, 48, 49. The FKey tag is described for each Menu tag having the Func = "Subunit" or Func = "Source_Device" attribute. The description position is at the end one level below the Menu tag that has the same attribute, and the range of influence is the entire menu tag and below.
The following tags are placed in the hierarchy below the FKey tag. The Path tag <Path> is a tag for describing the effective range (path) of function assignment to the function keys 47, 48, 49 by the FKey tag. The path is represented by a relative path from the Fkey tag hierarchy. If this Path tag is an empty tag, it indicates the entire range of Menu tags to which the Path tag belongs.
The F1 tag <F1> is a tag for describing the function assigned to the function key 47 (F1 key), that is, the shortcut path of the menu item. The F2 tag <F2> is a tag for describing the function assigned to the function key 48 (F2 key), that is, the shortcut path of the menu item. The F3 tag <F3> is a tag for describing the function assigned to the function key 49 (F3 key), that is, the shortcut path of the menu item. The path is represented by a relative path from the Fkey tag hierarchy, and its description format is enclosed in double quotes "" "and separated by commas. If the F1, F2 or F3 tag is empty and the F1, F2 or F3 tag is not described, it means that the function (path) is not assigned to the function key corresponding to that tag.
In addition, a plurality of FKey tags can be described for each Menu tag having the Func = "Subunit" or Func = "Source_Device" attribute. Each FKey tag is valid in the range described in the Path tag, and the FKey tag described later is valid in the area where the ranges of a plurality of FKey tags overlap.
In the case of FIG. 9, the FKey tag description 111 covers the entire Menu tag description 110 because the Path tag is an empty tag, but the FKey tag description 112 described after that is a Path tag. Since "Play Info" is the valid range, the description of the Path tag of the later description 111 is valid, the description 111 is applied to "Play Info", and the description 110 is applied to the Menu tag area other than "Play Info". Will be done.
According to the description 110, the F1 key (function key 47) is assigned a function to display the performance information "Play Info" on the display 36, and the F2 key (function key 48) is assigned to "Repeat" to repeat the performance. Functions are assigned, and the F3 key (function key 49) is assigned the "Shuffle" function that allows the song order to be played randomly.
Further, according to the description 111, while "Play Info" is displayed, the F1 key (function key 47) is assigned a "List Control" function for displaying a playlist on the display 36 and adjusting the performance song, and F2. The key (function key 48) is assigned a function to display the menu that is the root path on the display 36, and the F3 key (function key 49) is not assigned a function.
Explanation of layered menu Figure 10 shows a part of the layered menu represented by the self-described file described above. Input selection (Input), volume control (Volume), and power control (Power Control) menus are arranged in a tree shape below the main zone. Below the volume control, the volume level control (Level) and mute control (Mute) menus are arranged in a tree shape. In addition, the power on / off control (Power) and sleep setting (Sleep) menus are arranged in a tree shape below the power control. A plurality of parameters are prepared in the menu item at the bottom of each tree, and the parameter is selected according to the operation content of the user and the state of the controlled device at that time. Then, the command body of the lowest menu item and the selected parameter are combined to form a command, which is issued (transmitted) to the audio device which is the controlled device.
The following parameters are prepared for each menu item. Tuner, DVD, ..., VCR values are prepared for the input selection (Input) of the menu item. Each parameter corresponds to the source device connected to this AV receiver. For the volume level control (Level) of the menu item, values in 0.5 dB increments are prepared from -80.5 dB to 16.5 dB. On and Off values are prepared for the menu item Mute. On and Standby values are prepared for the power on / off control (Power) of the menu item. In addition, the values of Last, 120, 90, 60, 30, and Off are prepared for the sleep setting (Sleep) of the menu item. Each parameter corresponds to the time (minutes) until the power is turned off, Off corresponds to the setting to turn off the sleep function and continue the power on, and Last corresponds to the setting to use the previous sleep setting as it is. There is. Of the above parameters, the input selection can be acquired by a command and dynamically merged into XML (indirect merge).
If the layered menu having the above structure is displayed on the display 36 for each layer, all the functions of the controlled device can be controlled by following the menu tree. However, the control of the above-mentioned "known function" is assigned to the key switches 41 to 56, and can be immediately and directly controlled by operating any of the key switches 41 to 56 without following the hierarchical menu. You can do it. The "known functions" assigned to the key switches 41 to 56 have been deleted from the layered menu displayed on the display 36, and the layered menu has been simplified.
Here, the "known function" is a group of functions shown at the beginning of "Explanation of self-described file", and is generally applied to any device such as power on / off and play start / stop. It is a general-purpose function. The Menu tag, which issues commands for known functions, is given the same unified Title_x attribute in the self-described file of any controlled device. On the other hand, the ROM 32 of the commander 16 stores the name (Title) of the function assigned to each key switch 41 to 56. The CPU 31 compares the Tille_x stored in the ROM 32 with the Title_x attribute of the Menu tag, and assigns the command of the corresponding function to each key switch 41 to 56.
FIG. 10 shows a part of the top level of the self-described file of the AV receiver 11 which is one of the audio devices. An example of the layered menu of the audio device other than the AV receiver 11 is shown in FIG. deep. In this figure, PlayInfo is not a layered menu but operating state data of the controlled device that can be acquired by the GET function.
In the layered menu of FIG. 10, the menu item Input is the lowest layer, and when the source device is selected, a command is issued to end the menu tree. However, when a source device is selected by the menu item Input, the commander 16 of the present embodiment receives a self-description file from the selected source device and jumps control to the menu item of the source device.
FIG. 12 is a diagram showing a link form between the layered menu of the AV receiver (main zone) and the layered menu of the source device (tuner). When the tuner 13 is selected in the menu item Input of the main zone, the commander 16 analyzes the self-described file acquired from the control unit 11B of the AV receiver 11 and performs the performance information of the built-in tuner 11C (see FIG. 11 (B)). ) Is acquired, and this performance information is displayed on the display 36. After that, the menu display (controlled object) is jumped to the tuner 11C (see Fig. 11 (A)).
On the other hand, when an external source device, for example, PC14, is selected in the menu item Input, the commander 16 accesses the control unit 14B of the PC14, acquires the performance information (see FIG. 11 (D)), and obtains the performance information of this source device. The current operating status is displayed on the display 36. After that, the self-description file is acquired from the control unit 14B of the PC14, the menu for controlling the music playback function of the PC14 is displayed (see FIG. 11 (C)), and the self is set up as a commander for the PC14.
By linking the layered menus on the plurality of controlled devices in this way, it is possible to improve the operability of the user when operating related menu items among the plurality of devices.
Explanation of commander operation The operation of the commander 16 will be described with reference to the flowchart of FIG. 13 and the display example of the display 36 of FIG. First, FIG. 13A is a flowchart showing the operation when the zone selection key 41 is turned on. When the user operates the commander 16 in any zone (room), the zone selection key 41 is first turned on. If zone selection key 41 is turned on (S1), to access via the access point 22 LAN 15, to search for communicable audio equipment that (S2). Select all AV receivers from the discovered audio devices, and acquire the self-written file and performance information of the selected AV receiver (S3). Based on the acquired self-description file and performance information, the zone configuration and the song being played in each zone are determined (S4). Get the icon of each zone from the AV receiver in charge of that zone and edit the menu screen (S5). Then, this screen is displayed as a zone selection screen (Fig. 14 (A)) (S6).
The self-described file can be obtained by using the http GET method. For example, "GET http://192.168.0.1/RemoteControl/UnitDesc.xml". Note that this IP address is an example, and the address of each audio device is actually specified. You can also get the icon with the http GET method. For example, "GET http://192.168.0.1/icon/listen.png". Note that this IP address is an example, and the address of each audio device is actually specified.
A display example of the zone selection screen displayed in S6 is shown in FIG. 14 (A). In this figure, four zones (Living, Bed Room, Kids Room, Kitchen) are displayed on the left side, and song information (song name, singer name) being played in each zone is displayed on the right side. The user can select the zone by operating the cursor on the touch pad 37 and clicking at the position of the desired zone. Normally, the user selects the zone (room) in which he / she is located.
When the above zone is selected, the commander 16 executes the process shown in FIG. 13 (B). In FIG. 13 (B), when a zone is selected (S10), it communicates with the AV receiver in charge of the selected zone and receives a self-described file (S11). If the self-description file received in S3 is saved, the self-description file acquisition process in S11 is not necessary again. Of the menu items included in the received self-described file, the menu items that control the above-mentioned "known functions" are assigned to the key switches 41 to 46 and 50 to 56, and the menu items (shortcuts) specified by the FKey tag. Is assigned to function keys 47 to 49 (S12). Next, the menu tree is reconstructed (only with unknown functions) except for the "known functions" assigned to the above key switches 41 to 46 and 50 to 56 (S13). At this time, the operating state such as the volume level value and mute on / off is acquired from the controlled device AV receiver, and when a menu item is selected or when key switches 41 to 56 are operated, which parameter Set whether to issue a command using (S14). For example, if the current value is mute On, set the mute Off command to be issued when the mute key 45 is turned on. Then, the input selection screen, which is the top menu of the selected zone, is edited (S15). At this time, since the list display format using icons is recommended for the input selection screen, the AV receiver in charge of the selected zone is accessed to acquire the icon of the source device of each input. The input selection screen (Fig. 14 (B)) using the acquired icon is displayed on the display 36 (S16).
When the input selection key (MUSIC key) is pressed by the user, the process of acquiring the self-described file has already been completed, so the process is executed from the process of S15.
An example of the input selection screen displayed in S15 is shown in FIG. 14 (B). In this figure, 6 source devices (Net Music Service, Internet Radio, PC Contents, Bluetooth, USB, Silicon Audio) can be selected. The user can select the source device by operating the cursor on the touch pad 37 and clicking at the position of the desired source device.
When the user selects one of the source devices displayed on the display 36, the commander 16 switches the controlled audio device to the selected source device and executes the operation shown in FIG. 13 (C). If the audio device to be controlled does not have a self-description file, the commander 16 may receive a description file related to the audio device from the AV receiver, and controls the audio device via the AV receiver. You may try to do it.
When a source device is selected on the input selection screen shown in Fig. 14 (B) (S20), it communicates with the selected source device, receives a self-written file, and acquires performance information (Play Info) (S21). ). Then, the Play Info screen as shown in FIG. 14 (C) is displayed on the display 36 (S22), and the menu item that controls the "known function among the menu items included in the received self-described file" is set by the key switch 41. Allocate to ~ 46 and 50 to 56, and assign the menu item (shortcut) specified by the FKey tag to function keys 47 to 49 (S23). Next, the menu tree is reconstructed (only with unknown functions) except for the "known functions" assigned to the above key switches 41 to 46 and 50 to 56 (S24). At the same time, the operating status is acquired from the source device, which is the controlled device, and which parameter is used to issue the command in response to the selection of the menu item or the on of the key switch is set (S25). After this, the band and frequency can be controlled. If the selected source device is a tuner built into the AV receiver, there is no need to acquire a new self-description file and performance information in S21, and the tuner is from the self-description file of the AV receiver that has already been acquired. All you have to do is analyze and retrieve the description.
As described above, in the above embodiment, the parameters of -80.5 dB to 16.5 dB are associated with the volume up / down keys 43 and 44, and when the volume up key 43 is turned on, the parameter is one step larger than the current volume value. When the volume down key 44 is turned on, the command is generated with a parameter that is one step smaller than the current volume value. This makes it possible to simplify keyswitches or menu items even if the command body comes with a large number of parameters.
The reverse is also possible. That is, when the parameter attached to the command body is UP / DOWN, all the values in the range that can be controlled by the command (for example, 1,2, ..., 9,10) are listed as menu items. , Direct control may be possible by selecting the desired numerical value. As the display form of the menu item, for example, a form such as a pull-down menu may be adopted.
In the above embodiment, the "known function" is associated with the key switch which is the hardware and is deleted from the hierarchical menu (menu tree), but it is not always necessary to delete the "known function". It may be possible to operate with both a key switch and a hierarchical menu.
In the above embodiment, the commander 16 is configured to be connected to the network by wireless LAN, but may be configured to be connected to the network by wired LAN. Further, in this embodiment, each controlled device and the commander are connected via a network, but as shown in FIG. 15, each controlled device and the commander communicate with each other individually. However, the present invention is applicable.
Further, in this embodiment, the present invention is applied to an audio system, and the controlled device is an audio device. However, the present invention can be applied not only to an audio system but also to any control system, and the controlled device is an audio device. Not limited to.
<figref num="1">Configuration diagram of an audio system to which the present invention is applied</figref><figref num="2">External view of the commander (remote control device) of the audio system</figref><figref num="3">Commander block diagram</figref><figref num="4">Block diagram of audio equipment in an audio system</figref><figref num="5">A diagram showing an example of a self-described file stored in an AV receiver, which is an audio device.</figref><figref num="6">A diagram showing an example of the value of the Func attribute of a self-written file.</figref><figref num="7">Diagram showing another example of a self-written file (including the Cmd tag)</figref><figref num="8">Diagram showing an example of a layered menu composed of self-written files</figref><figref num="9">Diagram showing another example of a self-written file (including the FKey tag)</figref><figref num="10">Diagram showing another example of a layered menu composed of self-written files</figref><figref num="11">Diagram showing an example of a layered menu composed of self-written files of audio equipment other than AV receivers</figref><figref num="12">The figure explaining the link form of the layered menu between a plurality of audio devices.</figref><figref num="13">Flowchart showing commander operation</figref><figref num="14">Diagram showing an example of a screen displayed on a commander display</figref><figref num="15">The figure which shows the form example of another audio system to which this invention is applied.</figref>
Code description
10 ... Audio equipment group (controlled equipment group) 11,12 ... AV receiver 13 ... Tuner 14 ... DVD player 16 ... Commander 36 ... Display 37 ... touchpad 41 ~ 56 ... key switch
16 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
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10606555B1 | Cited by | United States of America | Applicant |
| US12211490B2 | Cited by | United States of America | Applicant |
| US11017789B2 | Cited by | United States of America | Applicant |
| US10873819B2 | Cited by | United States of America | Applicant |
| US11798553B2 | Cited by | United States of America | Applicant |
| US11984123B2 | Cited by | United States of America | Applicant |
| US11032617B2 | Cited by | United States of America | Applicant |
| US11175880B2 | Cited by | United States of America | Applicant |
| US11961519B2 | Cited by | United States of America | Applicant |
| US10872194B2 | Cited by | United States of America | Applicant |
| US11405430B2 | Cited by | United States of America | Applicant |
| KR20190014495A | Cited by | Republic of Korea | Search report |
| US12047753B1 | Cited by | United States of America | Applicant |
| US12217748B2 | Cited by | United States of America | Applicant |
| US12160455B2 | Cited by | United States of America | Applicant |
| US11184704B2 | Cited by | United States of America | Applicant |
| WO2017147081A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US11133018B2 | Cited by | United States of America | Applicant |
| US10097919B2 | Cited by | United States of America | Applicant |
| US10959029B2 | Cited by | United States of America | Applicant |
| US11664023B2 | Cited by | United States of America | Applicant |
| US10602268B1 | Cited by | United States of America | Applicant |
| US10582322B2 | Cited by | United States of America | Applicant |
| US11832068B2 | Cited by | United States of America | Applicant |
| US10466962B2 | Cited by | United States of America | Applicant |
| US12230291B2 | Cited by | United States of America | Applicant |
| US10332537B2 | Cited by | United States of America | Applicant |
| US10446165B2 | Cited by | United States of America | Applicant |
| US11676590B2 | Cited by | United States of America | Applicant |
| US11698771B2 | Cited by | United States of America | Applicant |
| US10743101B2 | Cited by | United States of America | Applicant |
| US10509626B2 | Cited by | United States of America | Applicant |
| US11308958B2 | Cited by | United States of America | Applicant |
| US11432030B2 | Cited by | United States of America | Applicant |
| US10134399B2 | Cited by | United States of America | Applicant |
| US10051366B1 | Cited by | United States of America | Applicant |
| US11540047B2 | Cited by | United States of America | Applicant |
| US11734494B2 | Cited by | United States of America | Applicant |
| US11042355B2 | Cited by | United States of America | Applicant |
| US11212612B2 | Cited by | United States of America | Applicant |
| US12165651B2 | Cited by | United States of America | Applicant |
| US10880650B2 | Cited by | United States of America | Applicant |
| US11200894B2 | Cited by | United States of America | Applicant |
| US10021503B2 | Cited by | United States of America | Applicant |
| US10313812B2 | Cited by | United States of America | Applicant |
| US11983463B2 | Cited by | United States of America | Applicant |
| US12200034B2 | Cited by | United States of America | Applicant |
| US9965247B2 | Cited by | United States of America | Applicant |
| US11545169B2 | Cited by | United States of America | Applicant |
| US11354092B2 | Cited by | United States of America | Applicant |
| US9978390B2 | Cited by | United States of America | Applicant |
| US11736860B2 | Cited by | United States of America | Applicant |
| US11889160B2 | Cited by | United States of America | Applicant |
| US11501795B2 | Cited by | United States of America | Applicant |
| US11184969B2 | Cited by | United States of America | Applicant |
| US10445057B2 | Cited by | United States of America | Applicant |
| US11031014B2 | Cited by | United States of America | Applicant |
| US11899519B2 | Cited by | United States of America | Applicant |
| KR20200034839A | Cited by | Republic of Korea | Search report |
| US11514898B2 | Cited by | United States of America | Applicant |
| US11288039B2 | Cited by | United States of America | Applicant |
| US11138975B2 | Cited by | United States of America | Applicant |
| US10867604B2 | Cited by | United States of America | Applicant |
| US11696074B2 | Cited by | United States of America | Applicant |
| US10811015B2 | Cited by | United States of America | Applicant |
| US11308961B2 | Cited by | United States of America | Applicant |
| JP2019514237A | Cited by | Japan | Search report |
| US10482868B2 | Cited by | United States of America | Applicant |
| US11024331B2 | Cited by | United States of America | Applicant |
| US10778834B2 | Cited by | United States of America | Applicant |
| US10152969B2 | Cited by | United States of America | Applicant |
| US11899708B2 | Cited by | United States of America | Applicant |
| US10142754B2 | Cited by | United States of America | Applicant |
| US11100923B2 | Cited by | United States of America | Applicant |
| US10075793B2 | Cited by | United States of America | Applicant |
| US11134291B2 | Cited by | United States of America | Applicant |
| US11893308B2 | Cited by | United States of America | Applicant |
| US10846046B2 | Cited by | United States of America | Applicant |
| US11563842B2 | Cited by | United States of America | Applicant |
| US10866698B2 | Cited by | United States of America | Applicant |
| US11200889B2 | Cited by | United States of America | Applicant |
| US11451908B2 | Cited by | United States of America | Applicant |
| US11797263B2 | Cited by | United States of America | Applicant |
| US11641559B2 | Cited by | United States of America | Applicant |
| US11790911B2 | Cited by | United States of America | Applicant |
| US12283269B2 | Cited by | United States of America | Applicant |
| US12112121B2 | Cited by | United States of America | Applicant |
| US11557294B2 | Cited by | United States of America | Applicant |
| US11538460B2 | Cited by | United States of America | Applicant |
| US11726742B2 | Cited by | United States of America | Applicant |
| US11360643B2 | Cited by | United States of America | Applicant |
| US12327549B2 | Cited by | United States of America | Applicant |
| US11778259B2 | Cited by | United States of America | Applicant |
| US11710487B2 | Cited by | United States of America | Applicant |
| US12231477B2 | Cited by | United States of America | Applicant |
| US11132989B2 | Cited by | United States of America | Applicant |
| US10614807B2 | Cited by | United States of America | Applicant |
| US10225651B2 | Cited by | United States of America | Applicant |
| US10873612B2 | Cited by | United States of America | Applicant |
| US11120794B2 | Cited by | United States of America | Applicant |
2 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 2008317724 | Japan | A | |
| JP20080317724 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| JP2010141748AThis record | Japan | A | |
| JP5347472B2 | Japan | B2 |
11 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 2010141748
- Publication, DOCDB
- 2010141748
- Publication, EPODOC
- JP2010141748
- Application
- 317724
- Application, DOCDB
- 2008317724
- Application, EPODOC
- JP20080317724
Titles2
- Japanese
- 遠隔制御装置および遠隔制御システム
- English
- Remote control device and remote control system
Classification
- IPC, 2
- H04Q9 00
- H04R3 12