Patent Description:
An application program described in Non Patent Literature <NUM> has a function to perform a remote control and remote monitoring of a plurality of amplifiers. The application program accepts, for example, a setting of a threshold value for a temperature of a heat sink. With the application program, a warning is emitted when the temperature of the heat sink exceeds the threshold value.

[Non Patent Literature <NUM>] <NPL> Document <CIT> discloses a method for running applications depending on different conditions.

Document <CIT> discloses an application driving method that allows setting conditions for specific situations.

However, the application program described in Non Patent Literature <NUM> is the one that performs individual management of a plurality of devices, and thus has been unable to perform management of as far as the entire system. As the number of devices within a system increases, the number of objects to manage increases; then, it becomes difficult to perform management of the entire system.

On that account, the present invention, in some embodiments thereof, is directed to providing an information display apparatus, an information display method and a program that are capable of performing management of an entire system.

The above-mentioned problem is solved by the features of the independent claims.

The information display apparatus is capable of performing management of an entire system.

An information display apparatus according to an embodiment of the present invention sets a main widget that integrates a plurality of sub-widgets. Also, the information display apparatus sets a condition for each sub-widget, and sets a relationship between conditions for the sub-widget and the main widget. Thus, by performing management of the main widget, the user can perform management of states of a plurality of devices or functions that are allocated to a plurality of sub-widgets.

<FIG> is a block diagram showing a configuration of a sound system. The sound system includes a laptop PC <NUM>, a tablet PC <NUM>, an audio mixer <NUM>, an audio I/O unit <NUM>, an amplifier <NUM>, a speaker <NUM> and a LAN (Local Area Network) <NUM>. The laptop PC <NUM>, the tablet PC <NUM>, the audio mixer <NUM>, the audio I/O unit <NUM>, the amplifier <NUM> and the speaker <NUM> are connected to each other through the LAN <NUM>. However, in the present invention, connection mode for each device is not limited to a network connection through a LAN. For example, each device may be connected through a MIDI (Musical Instrument Digital Interface).

The laptop PC <NUM> and the tablet PC <NUM> are respectively examples of the information display apparatus of the present invention, and are general purpose computers (information processing devices). <FIG> is a block diagram showing a configuration of the PC <NUM>. The laptop PC <NUM> includes a display <NUM>, a user interface (I/F) <NUM>, a CPU <NUM>, a flash ROM <NUM>, a RAM <NUM> and a network interface (I/F) <NUM>. These components are connected to a bus <NUM>. The tablet PC <NUM> also has a configuration similar to that of the laptop PC <NUM>.

The display <NUM> consists of, for example, a LCD (Liquid Crystal Display), and displays various information. The user I/F <NUM> consists of, for example, a mouse, a keyboard, a touch panel and/or the like, and receives user's operation. The user I/F <NUM>, together with the display <NUM>, constitutes a GUI (Graphical User Interface).

The CPU <NUM> corresponds to a control portion, an information obtaining portion and so forth of the present invention. The CPU <NUM> reads out a program that is stored in the flash ROM <NUM>, which is a storage medium, into the RAM <NUM> and realizes a predetermined function. For example, the CPU <NUM> realizes a GUI by causing the display <NUM> to display an image of an operation portion (receiving portion) for receiving a user's operation and then by receiving, through the user I/F <NUM>, a selection operation or the like to an image of the operation portion. Here, the program is not necessarily stored in the flash ROM <NUM> in the own apparatus, but may be stored in a storage medium in an external device such as a server or the like, as is well-known. In such a case, the CPU <NUM> may each time read out the program from the server into the RAM <NUM> to execute.

<FIG> is an example of a GUI displayed on the display <NUM>. With the GUI shown in this example, the user performs operations such as placement of widgets, setting of devices or functions that are to be associated with the widgets, and so forth. A widget is an element to constitute a GUI. In the example of <FIG>, as widgets, an alert indicator <NUM>, an ON/OFF button <NUM>, a slider <NUM>, a knob <NUM> and a meter <NUM> are displayed.

<FIG> is a flow chart showing an operation of the CPU <NUM>. The CPU <NUM>, on receiving edit instructions of widgets through the user I/F <NUM>, causes an edit screen shown in <FIG> to open (S11).

In the edit screen, the CPU <NUM> places a main widget (S12) at first. The main widget is a widget that integrates a plurality of below-mentioned sub-widgets into one. In the example of <FIG>, the alert indicator <NUM>, the ON/OFF button <NUM>, the slider <NUM>, the knob <NUM> and the meter <NUM> are each correspond to a main widget. The user can, as indicated on the right side in the edit screen in the diagram, place main widgets that are going to be used by drugging and dropping a plurality of main widgets.

Then, the CPU <NUM> determines whether or not the user has selected a main widget (S13). If the user does not select a main widget (S13, No), the CPU <NUM> repeats the determination of S13. If the user selects a main widget (S13, Yes), the CPU <NUM>, as shown in <FIG>, causes a balloon for sub-widgets to be displayed (S14), and then causes the sub-widgets to be displayed in the balloon (S15). For example, in <FIG>, since the user has selected the alert indicator <NUM>, the CPU <NUM> causes a balloon image <NUM> corresponding to the alert indicator <NUM> to be displayed. Then, the CPU <NUM> causes a plurality of sub-widgets to be displayed inside the balloon image <NUM>. In this example, the CPU <NUM> causes four sub-widgets consisting of a sub-indicator <NUM>, a sub-indicator <NUM>, a sub-indicator <NUM> and a sub-indicator <NUM> to be displayed. The number of sub-widgets displayed in the balloon image <NUM> can also be specified by the user, and so can deletion or addition thereof be made.

Each sub-widget is associated with a predetermined device or a predetermined function. For example, the sub-indicator <NUM> is associated with the amplifier <NUM>, the sub-indicator <NUM> is associated with the audio mixer <NUM>, the sub-indicator <NUM> is associated with the speaker <NUM>, and the sub-indicator <NUM> is associated with the audio I/O unit <NUM>. Further, a sub-widget can even be associated with, instead of an entire device, one constituent of the device (for example, a heat sink for one channel of the amplifier, or the like). Also, each sub-widget can be associated with a predetermined function (for example, a level controller) installed on each device.

Moreover, the laptop PC <NUM> may detect devices inside the system by performing a network search or the like and then automatically associate each sub-widget with each device; otherwise, the user may manually associate any sub-widget with any device or any function. In the case where each sub-widget is automatically associated with each device, the laptop PC <NUM> may, for example, obtain information on a device name (for example, computer name, MAC address, IP address, or the like) and then associate a sub-widget with the device name.

Subsequently, <FIG> is a flow chart showing an editing operation of a sub-widget, and <FIG> is a diagram showing an example of an edit screen.

The CPU <NUM> determines whether or not the user has selected a sub-widget (S21). If the user does not select a sub-widget, the CPU <NUM> repeats the determination of S21 (S21, No). If the user has selected each sub-widget and has given edit instructions (S21, Yes), the CPU <NUM> causes the sub-widget edit screen as shown in <FIG> to be displayed, and receives each editing operation (S22).

The user can edit device name (Model), Device Identifier, function name (Parameter), channel number (Channel), condition and so forth.

The device name is automatically inputted by contacting the target device and so on; otherwise, the user can edit freely. As to the device identifier, although an IP address is displayed in the example of <FIG>, a MAC address or specific identification information such as serial number or the like may be used, instead. A function name becomes capable of being edited when a sub-widget is associated with a predetermined function in a predetermined device. In this example, in order to perform management of a level controller (fader) of an output channel <NUM> with the sub-indicator <NUM> being associated with the audio mixer <NUM>, "Output Level" is displayed as the function name. The channel number corresponds to a channel number for the parameter that is associated with the sub-widget. In this example, channel <NUM> is set. Therefore, the sub-indicator <NUM> becomes a widget to indicate a state (alert) of the level controller of the output channel <NUM> of the audio mixer <NUM>.

The condition (threshold value) indicated in the bottom line means a condition that is set for the sub-widget. For a device or a function that is associated with each sub-widget, each predetermined condition is set. For example, the sub-indicator <NUM> is associated with the heat sink for the channel <NUM> of the amplifier <NUM>. Since the sub-indicator <NUM> is an alert indicator, for the sub-indicator <NUM> an alert condition is set. Also, in the example shown in <FIG>, for the sub-indicator <NUM> a condition of +5dB is set as a level of the output channel <NUM>. Thus, when the level of the output channel <NUM> of the audio mixer <NUM> becomes greater than or equal to +5dB, the condition for the sub-indicator <NUM> is met. If the condition is met, the CPU <NUM> performs an alert notification by causing a corresponding widget (indicator) to be turned on or blinked. Otherwise, the CPU <NUM> may perform an alert notification by causing an indication color of the indicator to change. Moreover, it is also possible to set multi-step conditions with the indication color being changed multi-stepwise. For example, the indication color becomes yellow in a case where the level becomes greater than or equal to +3dB, and red in a case where the level becomes greater than or equal to +5dB.

In the above-mentioned manner, the user can edit each sub-widget. Next, <FIG> is a flow chart showing an operation of the CPU <NUM> in a case of setting a relationship between conditions set for the sub-widgets and a condition set for the main widget. <FIG> is a diagram showing an example of a relationship setting screen.

The CPU <NUM> determines whether or not the user has selected a relationship setting button <NUM> (S31). If the user does not select the relationship setting button <NUM>, the CPU <NUM> repeats the determination of S31 (S31, No). If the user selects the relationship setting button <NUM> (S31, Yes), the CPU <NUM> causes a screen for setting a relationship between conditions set for the sub-widgets and a condition set for the main widget as shown in <FIG> to be displayed (S32).

The user selects, as the relationship between conditions set for the sub-widgets and a condition set for the main widget, a logical expression of the conditions set for a plurality of sub-widgets, for example. In the example of <FIG>, the user selects one from among "AND", "OR", "XOR" and "XNOR". When "AND" is selected, the CPU <NUM> decides, as the relationship, that the condition for the main widget is met when all the conditions for the sub-widgets are met. As a result, the alert condition for the alert indicator <NUM> as the main widget is met when all the alert conditions for the sub-indicator <NUM>, the sub-indicator <NUM>, the sub-indicator <NUM> and the sub-indicator <NUM> are met.

When "OR" is selected, the CPU <NUM> decides, as the relationship, that the condition for the main widget is met when a condition for at least any one corresponding sub-widget is met. When "XNOR" is selected, the CPU <NUM> decides, as the relationship, that the condition for the main widget is met when states of all the sub-widgets match. That is, the alert condition for the alert indicator <NUM> as the main widget is met when all the alert conditions for the sub-indicator <NUM>, the sub-indicator <NUM>, the sub-indicator <NUM> and the sub-indicator <NUM> are met, or when all the alert conditions for the sub-indicator <NUM>, the sub-indicator <NUM>, the sub-indicator <NUM> and the sub-indicator <NUM> are not met.

When "XOR" is selected, the CPU <NUM> decides, as the relationship, that the condition for the main widget is met when states of at least any one of the sub-widgets are different from other(s). That is, the CPU <NUM> decides that the condition for the main widget is met when at least any one of the alert conditions for the sub-indicator <NUM>, the sub-indicator <NUM>, the sub-indicator <NUM> and the sub-indicator <NUM> are not met while the alert condition(s) for the other sub-indicator(s) are met, or when at least any one of the alert conditions for the sub-indicator <NUM>, the sub-indicator <NUM>, the sub-indicator <NUM> and the sub-indicator <NUM> are met while the alert condition(s) for the other sub-indicator(s) are not met.

Additionally, the user may also set a relationship such that the condition for the main widget is met when the number of the sub-widgets the conditions for which are met reaches a predetermined number (<NUM>, for example). Further, it is also possible to set multi-step relationships with the indication color of the main widget being changed multi-stepwise. On decision that a first-step condition for the main widget is met when the conditions for two sub-widgets are met, the indication color of the main widget (alert indicator <NUM>) is changed to yellow. On decision that a second-step condition for the main widget is met when the conditions for all the sub-widgets are met, the indication color of the main widget (alert indicator <NUM>) is changed to red.

This enables the user to manage a plurality of devices or a plurality of functions integrally through one main widget, and thus to manage an entire sound system. For example, in a case where the user sets device temperatures as the conditions for a plurality of sub-widgets and sets "OR" as the relationship, it is possible to perform an alert notification on decision that the condition for the main widget is met when a temperature of any one of the devices in the sound system exceeds a threshold value.

Also, it is possible for the user to cause an alert notification when a specific condition for a specific device or a specific function is met. For example, in the fader of the mixer, setting of greater than or equal to 0dB is also acceptable, so that it is possible to cause the level of the output signal to be greater than that of the input signal. The greater-than-or-equal-to-zero dB setting for a fader of a certain portion on the sound system influence slightly; however, if many greater-than-or-equal-to-zero dB settings are made for a plurality of portions, there is a possibility that the signal level increases substantially. On that account, the user sets the condition for each sub-widget such that each fader value is greater than or equal to 0dB, and sets "AND" as the relationship. This makes it possible to perform an alert notification on decision that the condition for the main widget is met when the fader values for all the plurality of faders become greater than or equal to 0dB simultaneously.

Subsequently, <FIG> is a flow chart showing an operation of the PC in an operating mode. <FIG> are diagrams showing an example of the display screen in the operating mode. Although the operating mode may be carried out in the laptop PC <NUM>, in this embodiment, it is assumed that the operation shown in <FIG> is carried out in the tablet PC <NUM> that has increased portability. The tablet PC <NUM> has a configuration same or similar to that of the laptop PC <NUM> shown in <FIG>.

The CPU <NUM> of the tablet PC <NUM>, in the operating mode, first causes a management screen as shown in <FIG> to be displayed (S40). On the management screen, as shown in <FIG>, only the main widgets are displayed, and no sub-widget is displayed. Therefore, the management screen occupies just a small area on the display; and this is preferable for mobile information processing devices such as tablet PC <NUM> (or smart phone) or the like with a small display area.

The CPU <NUM> obtains information on each device or each function thereof that is connected through the network (S41). A parameter value (level, temperature, power consumption, load impedance or the like) for a function as a management target is transmitted from each device.

The CPU <NUM>, comparing an obtained present value for each device or each function with a condition (threshold value) set for each sub-widget to check if or not a condition for each sub-widget is met (S42). The CPU <NUM>, on determining that a condition for a sub-widget is met (S42, Yes), causes the state of the relevant sub-widget to change (S43). The CPU <NUM>, on determining that a condition for a sub-widget is not met (S42, No), omits the processing of S43. However, in the example of <FIG>, since the main widgets are displayed but no sub-widget is displayed on the management screen, it is not possible to be visually recognized that there is a change in state of any sub-widget until the condition for a main widget is met.

Then, the CPU <NUM> determines whether or not a condition for a main widget is met (S44). The CPU <NUM> determines that the condition for the main widget is met when one or more conditions for the sub-widgets meet the above-mentioned relationship (logical expression). When the condition for the main widget is met (S44, Yes), the CPU <NUM> causes the indication of the main widget to change (S45). For example, as shown in <FIG>, the CPU <NUM> causes the alert indicator <NUM> to be turned on. The CPU <NUM>, on determining that the condition for the main widget is not met (S44, No), repeats form the processing of S41.

After completing the processing of S45, the CPU <NUM> further determines whether or not the selection of a main widget has been made (S46). When a main widget is selected (S46, Yes), the CPU <NUM> causes sub-widgets corresponding to the selected main widget to be displayed (S47). The CPU <NUM>, on determining that a main widget is not selected (S46, No), omits the processing of S47.

For example, as shown in <FIG>, when the alert indicator <NUM> is selected, the CPU causes the sub-indicator <NUM>, the sub-indicator <NUM>, the sub-indicator <NUM> and the sub-indicator <NUM> to be displayed. In this example, for each sub-widget a device name is displayed. In a case of performing management of a specific function and a specific channel, names for these function and channel are also displayed.

In the example of <FIG>, because the level of the output channel <NUM> of the audio mixer <NUM> exceeds a predetermined threshold value and "OR" is set as the relationship with the main widget, both the alert indicator <NUM> and the sub-indicator <NUM> are in turn-on states. As shown in <FIG>, in a case where the level controller of the input channel <NUM> is assigned to the sub-indicator <NUM>, where the level controller of the output channel <NUM> is assigned to the sub-indicator <NUM>, and where a gain of a compressor of the input channel <NUM> is assigned to the sub-indicator <NUM>, and when "AND" is set as the relationship with the main widget, the alert indicator <NUM> remains turned-off even when the level of the output channel <NUM> of the audio mixer <NUM> exceeds a predetermined threshold value.

As stated above, the sound system according to the embodiment of the present invention makes it possible to manage a plurality of any devices or any functions integrally through the main widget even when the number of the devices increases.

Further, although, in the operation example of <FIG>, an example in which the tablet PC <NUM> obtains a present value of each function from each device is shown, instead, for example, such a procedure that each device performs an operation of comparing a present value with a condition (threshold value) for a sub-widget and that if the condition is met (if the threshold value is exceeded by the present value) information to the effect that the condition is met is transmitted from the device to the tablet PC <NUM> may be acceptable.

Also, such a procedure that the tablet PC <NUM> compares a present value obtained from a certain device with the condition whereas from another device if the condition for the sub-widget is met (if the threshold value is exceeded by the present value) information to the effect that the condition is met is transmitted to the tablet PC <NUM> may be acceptable.

Claim 1:
An information display apparatus (<NUM>, <NUM>), comprising:
a display portion (<NUM>) that displays widgets including a main widget (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) and a plurality of sub-widgets (<NUM>, <NUM>, <NUM>, <NUM>) that indicate states of devices (<NUM>, <NUM>, <NUM>, <NUM>) or states of functions installed on the devices (<NUM>, <NUM>, <NUM>, <NUM>);
a receiving portion (<NUM>) that receives user's operation; and
a control portion (<NUM>) that executes:
a process of placing the main widget (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) by the user on any place of the display portion (<NUM>);
a process of placing the plurality of sub-widgets (<NUM>, <NUM>, <NUM>, <NUM>) against the main widget (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) by the user in a balloon displayed after selection of the main widget by the user;
a process of setting the device (<NUM>, <NUM>, <NUM>, <NUM>) or the function that is associated with each of the plurality of sub-widgets (<NUM>, <NUM>, <NUM>, <NUM>) by the user;
a process of setting a condition for the device (<NUM>, <NUM>, <NUM>, <NUM>) or a condition for the function that is associated with each of the plurality of sub-widgets (<NUM>, <NUM>, <NUM>, <NUM>) by the user; and
a process of setting a relationship between conditions set for the plurality of sub-widgets (<NUM>, <NUM>, <NUM>, <NUM>) and a condition set for the main widget (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>), by the user
wherein:
the relationship between the plurality of sub-widgets (<NUM>, <NUM>, <NUM>, <NUM>) and the main widget (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) is such that the condition for the main widget (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) is defined by a logical expression of the conditions set for the plurality of sub-widgets (<NUM>, <NUM>, <NUM>, <NUM>); and
the logical expression of the conditions set for the plurality of sub widget (<NUM>, <NUM>, <NUM>, <NUM>) is set by a user through the receiving portion (<NUM>).