Terminal device, apparatus management system, apparatus management method, and program

Abstract

An identical apparatus determination unit (513) determines whether or not a first apparatus registered via a first controller conforming to a first communication standard and a second apparatus registered via a second controller conforming to a second communication standard are identical apparatuses. A function execution unit (512) displays the first apparatus and the second apparatus as the identical apparatus on a function execution screen for executing the function of the first apparatus and the function of the second apparatus when it is determined by the identical apparatus determination unit (513) that the first apparatus and the second apparatus are identical apparatuses.

Description

Terminal device, device management system, device management method and program

[0001] The present disclosure relates to a terminal device, a device management system, a device management method, and a program.

[0002] There are known techniques for remotely managing devices. For example, Patent Literature 1 discloses a method for efficiently controlling a system in a so-called smart house in which devices of different communication standards coexist.

[0003] Japanese Patent Application Laid-Open No. 2022-184741

[0004] In the technology for remotely managing devices as described above, when a single device supports multiple different communication standards, the terminal device operated by the user may determine that the single device is a separate device for each communication standard. This reduces usability. In light of this situation, there is a need to improve usability when managing devices that support multiple different communication standards.

[0005] The present disclosure has been made to solve the above-mentioned problems, and aims to provide a terminal device, etc. that can improve usability when managing devices that support multiple different communication standards.

[0006] In order to achieve the above object, the terminal device according to the present disclosure comprises: an identical device determination means for determining whether a first device registered via a first controller corresponding to a first communication standard and a second device registered via a second controller corresponding to a second communication standard are the same device; and a function execution means for, when the identical device determination means determines that the first device and the second device are the same device, displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and functions of the second device.

[0007] When a terminal device according to the present disclosure determines that a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device, the terminal device displays the first device and the second device as the same device on a function execution screen for executing functions of the first device and the second device. Thus, according to the present disclosure, usability can be improved when managing devices compatible with multiple different communication standards.

[0008] FIG. 1 is a diagram showing the overall configuration of a device management system according to embodiment 1; FIG. 2 is a block diagram showing the configuration of a terminal device according to embodiment 1; FIG. 3 is a diagram showing an example of a function list according to embodiment 1; FIG. 4 is a diagram showing an example of a function execution screen according to embodiment 1; FIG. 5 is a diagram showing an example of a function database according to embodiment 1; FIG. 6 is a diagram showing an example of a usage standard table according to embodiment 1; FIG. 7 is a reference diagram of a function execution screen when functions of devices compatible with multiple communication standards are not integrated; FIG. 8 is a diagram showing an example of a function execution screen when functions of devices compatible with multiple communication standards are integrated in embodiment 1;

[0009] Hereinafter, embodiments will be described in detail with reference to the drawings, in which the same or corresponding parts are designated by the same reference numerals.

[0010] (First Embodiment) A device management system 1 according to a first embodiment is a system capable of remotely managing devices 10, and in particular, is a system capable of improving usability when managing devices 10 that are compatible with multiple different communication standards. As shown in Fig. 1 , the device management system 1 includes multiple devices 10, multiple controllers 20, a server 30, and a terminal device 50.

[0011] The multiple devices 10 and the multiple controllers 20 are installed in a building 5. The building 5 is a structure such as a detached house, an apartment building, an office building, a commercial facility, a factory, etc. In the following, the building 5 is described as a dwelling such as a detached house or an apartment building, and the device management system 1 is described as a system that provides so-called smart home functions to a user U of the building 5.

[0012] Each of the multiple devices 10 is a home appliance such as an air conditioner, a refrigerator, a water heater, lighting, an electronic lock, an induction heating (IH) cooker, etc. In the example of Fig. 1, the multiple devices 10, such as device A, device B, ..., are installed in appropriate locations within the building 5. Hereinafter, when there is no need to distinguish between devices A, B, ..., they will be collectively referred to as "devices 10".

[0013] Although not shown, each device 10 includes a central processing unit (CPU), read-only memory (ROM), random access memory (RAM), a communication interface, and a readable / writable non-volatile semiconductor memory. Each device 10 is communicably connected to at least one of the multiple controllers 20, and transmits and receives data to and from the at least one controller 20. Each device 10 operates in accordance with control instructions transmitted from the at least one controller 20, and transmits status data indicating the status of each device 10 to the at least one controller 20.

[0014] Each of the multiple controllers 20 is a device that manages and controls the operations of the multiple devices 10. In the example of Fig. 1, three controllers, namely, controller A, controller B, and controller C, are installed as the multiple controllers 20 in appropriate locations within the building 5. Hereinafter, when the controllers A to C are referred to without distinction, they will be collectively referred to as "controllers 20."

[0015] Although not shown, each controller 20 includes a CPU, ROM, RAM, a communication interface, and a readable / writable nonvolatile semiconductor memory. In each controller 20, the CPU controls the operation of the controller 20 by executing a control program stored in the ROM while using the RAM as a work memory.

[0016] The controllers A to C are compatible with different communication standards A to C, respectively, and communicate with each device 10 using the different communication standards A to C. As an example, the controller A is an ENL controller that communicates based on the communication standard A of ECHONET Lite (registered trademark). The controller B is a controller that communicates based on the communication standard B of Matter (registered trademark). The controller C is an infrared smart remote control that communicates using the communication standard C that uses infrared communication.

[0017] Each of the multiple devices 10 is controlled by at least one of the multiple controllers 20. In the example of FIG. 1 , device A supports all of communication standards A to C and can communicate with all of controllers A to C. Therefore, device A can be controlled by any of controllers A to C. In contrast, device B supports communication standards A and B, but does not support communication standard C. Therefore, device B can be controlled by controller A and controller B, but cannot be controlled by controller C. In this way, the supported communication standards differ depending on the device 10, and therefore the controllers 20 with which it can communicate differ.

[0018] The server 30 is installed outside the building 5 and is a device that manages the entire device management system 1. As an example, the server 30 is a cloud server that provides resources in cloud computing. Although not shown, the server 30 includes a CPU, ROM, RAM, a communication interface, and a readable / writable non-volatile semiconductor memory. The server 30 communicates with the multiple controllers 20 and terminal devices 50 via a wide area communication network such as the Internet, and relays communications between the terminal devices 50 and each controller 20.

[0019] The terminal device 50 is a communication terminal operated by a user U, such as a smartphone, a PC (Personal Computer), a tablet terminal, etc. The user U is a resident, a user, etc. of the building 5. By operating the terminal device 50, the user U can operate or monitor the equipment 10 installed in the building 5 from inside or outside the building 5. As shown in FIG. 2 , the terminal device 50 includes a control unit 51, a storage unit 52, an operation unit 53, a display unit 54, and a communication unit 55.

[0020] The control unit 51 includes a CPU, a ROM, and a RAM. The CPU is also called a central processing unit, a processor, a microprocessor, a microcomputer, etc., and functions as a central processing unit that executes processing and calculations related to the control of the terminal device 50. In the control unit 51, the CPU reads out programs and data stored in the ROM and uses the RAM as a work area to perform overall control of the terminal device 50.

[0021] The storage unit 52 includes a nonvolatile semiconductor memory such as a flash memory, an EPROM (Erasable Programmable ROM), or an EEPROM (Electrically Erasable Programmable ROM), and serves as a so-called secondary storage device or auxiliary storage device. The storage unit 52 stores programs and data used by the control unit 51 to perform various processes. The storage unit 52 also stores data generated or acquired by the control unit 51 performing various processes. Specifically, the storage unit 52 stores a function list 521, a function database 522, a usage standard table 523, and a determination logic 524. These will be described in detail later.

[0022] The operation unit 53 includes input devices such as a touch panel, physical buttons, and a keyboard, and receives operations from the user U. The user U can input various instructions to the terminal device 50 by operating the operation unit 53. When the operation unit 53 receives an operation instruction input by the user, it transmits the received operation instruction to the control unit 51.

[0023] The display unit 54 includes a display device such as a liquid crystal display, an organic EL (Electro Luminescence) display, etc. The display unit 54 is driven by a display drive circuit (not shown), and displays various images under the control of the control unit 51.

[0024] The communication unit 55 includes a communication interface for the terminal device 50 to communicate with external devices. The communication unit 55 communicates with the server 30 via a wide area communication network, and with each of the plurality of controllers 20 via the server 30. Furthermore, when the terminal device 50 is located inside the building 5, the communication unit 55 can communicate directly with each of the plurality of controllers 20 via a local communication network established in the building 5, without going through the server 30.

[0025] The control unit 51 functionally includes a device registration unit 511, which is an example of a device registration means, a function execution unit 512, which is an example of a function execution means, a same-device determination unit 513, which is an example of a same-device determination means, and a function integration unit 514, which is an example of a function integration means. Each of these functions is realized in the control unit 51 by software, firmware, or a combination of software and firmware. The software and firmware are written as programs and stored in the ROM or the storage unit 52. Then, in the control unit 51, the CPU executes the programs stored in the ROM or the storage unit 52 to realize each function.

[0026] The device registration unit 511 registers the device 10 in the terminal device 50. Here, registering the device 10 in the terminal device 50 means making settings so that the device 10 can be operated or monitored from the terminal device 50 via the controller 20. The registration process for the device 10 is executed, for example, when a new device 10 is installed in the building 5 or when a new controller 20 is installed in the building 5.

[0027] More specifically, smart home application software for remotely managing the devices 10 is pre-installed in the terminal device 50. When the application software is launched, the device registration unit 511 displays a registration screen for the device 10 on the display unit 54 in response to an operation by the user U. The registration screen, not shown, is a screen that provides the user U with a trigger for starting registration of the device 10. On the registration screen, the device registration unit 511 receives a registration instruction from the user U to register a device 10 that is not registered in the terminal device 50, out of the multiple devices 10 that can be controlled by any of the controllers A to C.

[0028] When a registration instruction is received from the user U, the device registration unit 511 transmits the received registration instruction to the corresponding controller 20 among the controllers A to C via the communication unit 55. For example, when registering device A via controller A, the device registration unit 511 transmits the registration instruction to controller A via the server 30. As a result, the device registration unit 511 causes controller A to start the registration process for device A.

[0029] When the controller 20 receives an instruction to register the device 10 from the terminal device 50, the controller 20 transmits function information and device information of the device 10 in the controller 20 to the terminal device 50. The device registration unit 511 acquires the function information and device information transmitted from the controller 20.

[0030] The function information of the device 10 in the controller 20 is information indicating functions of the device 10 that can be executed from the terminal device 50 via the controller 20. Here, the function of the device 10 means at least one of operating and monitoring the device 10. In other words, executing the function of the device 10 by the controller 20 means at least one of operating the device 10 via the controller 20 and monitoring the state of the device 10 via the controller 20.

[0031] For example, if the device 10 is an air conditioner, the functions of the device 10 include turning the power on / off, setting a set temperature, monitoring the current set temperature, changing the set mode, monitoring the current set mode, etc. Alternatively, if the device 10 is a light, the functions of the device 10 include turning the power on / off, setting brightness, monitoring the current brightness, etc.

[0032] The device information of the device 10 is information about the device 10 for identifying the device 10. The device information is information indicating characteristics of the device 10, such as the model name, model number, serial number, device type, etc. of the device 10. The device information may also be wireless information used for wireless communication, such as an IP (Internet Protocol) address, a MAC (Media Access Control) address, etc. Here, the serial number, IP address, MAC address, etc. correspond to identification information that can uniquely identify the device 10. On the other hand, the model name, device type, etc. cannot uniquely identify the device 10, but correspond to narrowing-down information that can narrow down candidates for the device 10.

[0033] When the controller 20 establishes communication with the device 10, the controller 20 acquires such function information and device information from the device 10 and stores them in the storage unit. When the controller 20 receives a registration instruction for the device 10, the controller 20 transmits the function information and device information previously acquired from the device 10 to the terminal device 50 via the server 30.

[0034] Upon receiving the function information and device information transmitted from the controller 20, the device registration unit 511 generates a function list 521 based on the received function information and device information. The function list 521 is a list of functions that can be executed from the terminal device 50 for the device 10 registered in the terminal device 50.

[0035] As an example, Fig. 3 shows the function list 521 of device A when device A, whose device type is an air conditioner, is first registered in terminal device 50 from controller A. In Fig. 3, "Set" in the "Communication Standard A" column means that information for the corresponding item can be set, in other words, the information for the corresponding item can be operated for device A using communication standard A. "Get" in the "Communication Standard A" column means that information for the corresponding item can be obtained, in other words, the information for the corresponding item can be monitored for device A using communication standard A. Also, in Fig. 3, "ON" and "OFF" mean power on and power off, respectively.

[0036] Specifically, device A has the function of setting and acquiring information on "ON," "OFF," "set temperature," and "set mode," and the function of acquiring information on "indoor temperature." More specifically, device A has the function of setting and acquiring information on "set temperature" in units of 1°C. Device A also has the function of setting and acquiring information on each of the following modes as "set modes," namely, "cooling," "heating," "auto," and "setback." Device A also does not have the functions of "dehumidification" and "ECO" as "set modes," and does not have the functions of "timer setting" and "outdoor temperature."

[0037] The device registration unit 511 generates a function list 521 of the newly registered device 10 every time a new device 10 is registered in the terminal device 50. As a result, the device registration unit 511 performs settings so that the terminal device 50 can execute the multiple functions indicated by the function information acquired from the controller 20.

[0038] 2 , the function execution unit 512 executes the function of the device 10 registered by the device registration unit 511 in response to a user operation. Specifically, the function execution unit 512 displays a function execution screen on the display unit 54 in response to a user U operation while the application software is running. Here, the function execution screen is a screen for executing the function of the device 10 registered by the device registration unit 511. The function execution screen includes a device selection screen 541 shown on the left side of FIG. 4 and a monitor screen 542 shown on the right side of FIG. 4 .

[0039] When an operation to execute a function of any of the devices 10 registered in the terminal device 50 is received from the user U, the function execution unit 512 displays a device selection screen 541 on the display unit 54, as shown on the left side of Fig. 4. On the device selection screen 541, the function execution unit 512 displays a list of the devices 10 registered by the device registration unit 511 as items selectable by the user U. In the example of Fig. 4, the function execution unit 512 displays "Device A" and "Device B".

[0040] When the user U operates the operation unit 53 to select one of the multiple devices 10 displayed on the device selection screen 541, the function execution unit 512 displays a monitor screen 542 of the selected device 10 on the display unit 54. The monitor screen 542 is a screen that displays the results of monitoring the current state of the selected device 10.

[0041] As an example, when "Device A" is selected on the device selection screen 541, the function execution unit 512 displays a monitor screen 542 of device A, as shown on the right side of Fig. 4, on the display unit 54. On the monitor screen 542, the function execution unit 512 displays monitor information such as the current set temperature of device A, the current set mode of device A, and the current indoor temperature.

[0042] The function execution unit 512 acquires the monitor information of device A to be displayed on the monitor screen 542 from device A using controller A and communication standard A via which device A was registered. The function execution unit 512 acquires the monitor information of device A from device A at regular intervals, such as every minute or every three minutes, or at any timing, and updates the monitor screen 542.

[0043] On such a monitor screen 542, the user U can operate the operation unit 53 to input an operation for the device A. In the example of Fig. 4, the user U can set the set temperature of the device A in 1°C increments, and can switch the setting mode of the device A from heating to cooling, automatic, or setback.

[0044] When the function execution unit 512 receives such an operation on device A from the user U, it transmits operation information indicating the received operation to device A using the controller A and communication standard A via which device A was registered. As a result, the function execution unit 512 executes the operation received from user U on device A. In this way, the function execution unit 512 executes, as a function of device 10, monitoring the status of device 10 and executing an operation on device 10 using the controller 20 and communication standard via which device 10 was registered.

[0045] 2, when a new device 10 is registered by the device registration unit 511, the same device determination unit 513 determines whether the newly registered device 10 is the same device 10 as a device 10 that has already been registered in the terminal device 50. Specifically, since multiple controllers A to C corresponding to different communication standards A to C are installed in the building 5, one device 10 may be registered separately via different controllers 20. In the example of FIG. 1, device A may be registered separately via controllers A to C, and device B may be registered separately via controllers A and B.

[0046] In this way, when there is a possibility that one device 10 may be registered via different controllers 20, if it is determined that the devices 10 are different devices 10 despite being the same device 10, this causes complication or confusion for the user U, leading to a decrease in usability. To avoid such a situation, when a new device 10 is registered by the device registration unit 511 via one controller 20, the same device determination unit 513 determines whether the newly registered device 10 is the same device 10 as a device 10 that has already been registered via another controller 20.

[0047] Specifically, the same device determination unit 513 determines whether a first device 10 registered via a first controller 20 compatible with a first communication standard and a second device 10 registered via a second controller 20 compatible with a second communication standard are the same device 10. For example, if device A has already been registered via controller A and device A is newly registered by the device registration unit 511 via controller B, device A registered via controller A corresponds to the first device 10, and device A registered via controller B corresponds to the second device 10.

[0048] More specifically, the same-device determination unit 513 compares the first device information acquired from the first controller 20 when the first device 10 was registered via the first controller 20 with the second device information acquired from the second controller 20 when the second device 10 was registered via the second controller 20. If the first device 10 and the second device 10 are the same device 10, their respective device information, such as the model name, serial number, device type, and IP address, will all match. Therefore, if the first device information and the second device information match, the same-device determination unit 513 determines that the first device 10 and the second device 10 are the same device 10.

[0049] On the other hand, if the first device 10 and the second device 10 are different devices 10, at least one of the pieces of device information does not match. Therefore, if the first device information and the second device information do not match, the same device determination unit 513 determines that the first device 10 and the second device 10 are different devices 10. In this way, the same device determination unit 513 determines whether the first device 10 and the second device 10 are the same device 10 based on the first device information and the second device information.

[0050] When the same-device determination unit 513 determines that the first device 10 and the second device 10 are the same device 10, the function integration unit 514 integrates the functions of the first device 10 and the second device 10. Here, the function of the first device 10 is at least one function that is defined by a first communication standard and is executable on the first device 10 under the first communication standard, and the function of the second device 10 is at least one function that is defined by a second communication standard and is executable on the second device 10 under the second communication standard.

[0051] More specifically, when the same device 10 is registered separately via multiple different controllers 20, the executable functions are not necessarily the same because different communication standards are used, even for the same device 10. Therefore, when the same device 10 is registered separately via multiple different controllers 20, the function integration unit 514 integrates the functions indicated by the function information acquired at the time of each registration.

[0052] In the following, an example will be described in which device A has already been registered via controller A, device A is newly registered via controller B, and device A is further newly registered via controller C. In this case, function integration unit 514 generates function database 522 shown in Fig. 5 by combining function lists 521 generated when device A was registered via each of controllers A to C. Function database 522 contains information indicating functions that can be executed by device A under each of communication standards A to C.

[0053] 5, even for a single device A, the executable functions differ depending on the communication standards A to C. In this case where the executable functions differ depending on the communication standards A to C, the function integration unit 514 integrates the executable functions for device A. Specifically, the function integration unit 514 performs an OR operation, i.e., a logical sum, on the functions executable for each of the communication standards A to C. In other words, the function integration unit 514 determines the functions executable under at least one of the communication standards A to C as the integrated functions that are executable for device A.

[0054] Specifically, in the example of FIG. 5 , functions such as "ON," "OFF," "cooling," and "heating" are executable under any of communication standards A to C, while the "automatic" function is executable only under communication standards A and B, and the "timer setting" function is executable only under communication standard C. The function integration unit 514 determines these functions as executable functions for device A. In contrast, the "dehumidification" function is not executable under any of communication standards A to C. Therefore, the function integration unit 514 excludes the "dehumidification" function from the executable functions for device A.

[0055] More specifically, for each of the multiple functions defined in the function database 522, the function integration unit 514 determines, from among communication standards A to C, a communication standard to be used when executing the integrated function on device A. Specifically, the function integration unit 514 generates a usage standard table 523 shown in Fig. 6 from the function database 522 shown in Fig. 5. Here, the usage standard table 523 is a table that defines the communication standard to be used when executing the integrated function.

[0056] First, when only one communication standard is supported for one function, the function integration unit 514 determines that one communication standard as the standard to be used. For example, in the function database 522 shown in FIG. 5, the "setback" function in the "setting mode" is only possible with communication standard A, so the function integration unit 514 determines communication standard A as the standard to be used for this function. Also, the "ECO" function in the "setting mode" is only possible with communication standard B, so the function integration unit 514 determines communication standard B as the standard to be used for this function. Also, the "timer setting" and "outdoor temperature" functions are only possible with communication standard C, so the function integration unit 514 determines communication standard C as the standard to be used for these functions.

[0057] Second, when multiple communication standards are supported for one function, the function integration unit 514 determines which of the multiple communication standards to use in accordance with predetermined criteria. For example, in the function database 522 shown in FIG. 5, functions such as "ON," "OFF," "cooling," and "heating" are possible with any of communication standards A to C. Therefore, the function integration unit 514 determines which of the communication standards A to C to use for these functions. Furthermore, the functions "auto" and "indoor temperature" are possible with two of the communication standards A to C. Therefore, the function integration unit 514 determines which of the communication standards A to C to use for these functions.

[0058] The determination criteria are determined in advance in the determination logic 524 and stored in the storage unit 52. The function integration unit 514 determines the communication standard to be used for the integrated function by referring to the determination logic 524. More specifically, when the integrated function is compatible with multiple communication standards, the function integration unit 514 determines the communication standard to be used for the integrated function based on the number of function items or granularity of each of the multiple communication standards.

[0059] Here, the number of function items in a communication standard refers to the number of types of functions, such as "ON," "OFF," and "set temperature," that can be implemented using that communication standard. When an integrated function is compatible with multiple communication standards, the function integration unit 514 determines the communication standard with the largest number of executable function items as the communication standard to be used for the integrated function. For example, in the function database 522 shown in FIG. 5 , communication standards A and C each have eight items, which is more than the seven items of communication standard B. Therefore, the function integration unit 514 determines either communication standard A or C as the communication standard to be used for a function that is compatible with both communication standards A to C. Note that when communication standards A and C have the same number of items, the function integration unit 514 can arbitrarily determine which of communication standards A and C to use for a function that is compatible with both communication standards A and C.

[0060] Furthermore, the granularity of a function refers to the level of detail of information that can be operated or monitored by that function, in other words, the accuracy of the information. For example, in the function database 522 shown in FIG. 5, communication standards A and C allow the "set temperature" information to be set and acquired in 1.0°C increments, whereas communication standard B allows the "set temperature" information to be set and acquired in 0.5°C increments. In this case, the granularity of the "set temperature" function is finer, i.e., superior, to communication standards A and C. Therefore, the function integration unit 514 determines communication standard B as the communication standard to be used for the integrated "set temperature" function.

[0061] In this way, when the integrated function is compatible with all of multiple communication standards, the function integration unit 514 determines, among the multiple communication standards, the communication standard that has the most complete number of executable function items or granularity as the communication standard to be used for the integrated function. This makes it possible to provide the user U with the best possible integrated function. Note that whether the number of items or granularity is used as the determination criterion may be set in advance, or may be freely selectable by the user U.

[0062] 2 , when the same-device determination unit 513 determines that the first device 10 and the second device 10 are the same device 10, the function execution unit 512 displays the first device 10 and the second device 10 as the same device 10 on the function execution screen. In other words, when one device 10 is registered separately via multiple different controllers 20, the function execution unit 512 does not display each device 10 as a separate device 10 on the function execution screen, but displays it so that the user U can recognize that it is one device 10.

[0063] First, for ease of understanding, Fig. 7 shows an example of a function execution screen in a case where device A registered via each of controllers A to C is not determined to be the same device 10 and the functions are not integrated. In this case, "Device A," "Device A," "Device A," and "Device B" are displayed on the device selection screen 541, as shown in the upper left of Fig. 7. In other words, device A registered separately via each of controllers A to C is managed as separate devices 10 in the application software, and is displayed as if it were a different device 10.

[0064] When the user U selects the first "Device A" on this device selection screen 541, a monitor screen 542 showing monitor information acquired from device A using communication standard A is displayed, as shown in the upper right of Fig. 7. When the user U selects the second "Device A," a monitor screen 542 showing monitor information acquired from device A using communication standard B is displayed, as shown in the lower right of Fig. 7. When the user U selects the third "Device A," a monitor screen 542 showing monitor information acquired from device A using communication standard C is displayed, as shown in the lower left of Fig. 7. In this way, because the functions are not integrated, different monitor screens 542 are displayed for the same device A depending on communication standards A to C, and the operations that can be performed also differ.

[0065] In contrast, Fig. 8 shows an example of a function execution screen in a case where the same-device determination unit 513 determines that devices A registered separately via each of the controllers A to C are the same device 10 and the functions are integrated by the function integration unit 514. In this case, the function execution unit 512 displays items indicating devices A registered separately via each of the controllers A to C as a single item on the device selection screen 541 shown on the left side of Fig. 8. This allows the user U to easily recognize that devices A registered separately via different controllers A to C are the same device. In this way, the function execution unit 512 manages devices A registered separately via each of the controllers A to C as a single device 10 on the application software.

[0066] When the user U selects "Device A" on such device selection screen 541, the function execution unit 512 displays a monitor screen 542 shown on the right side of Fig. 8. On the monitor screen 542, the function execution unit 512 displays the functions integrated by the function integration unit 514 as functions executable on device A. Specifically, on the monitor screen 542, the function execution unit 512 displays functions executable on device A using at least one of communication standards A to C.

[0067] 8, the function execution unit 512 displays that it is possible to acquire information on "indoor temperature" and "outdoor temperature," that it is possible to set and acquire information on "set temperature" in increments of 0.5°C, that it is possible to set and acquire information on each of the "setting modes" - "cooling," "heating," "automatic," "setback," and "ECO," and that it is possible to set a "timer." In this way, the information displayed on the monitor screen 542 shown in FIG. 8 is information obtained by ORing the information displayed on the three monitor screens 542 shown in FIG. 7.

[0068] On such a monitor screen 542, the function execution unit 512 executes the integrated function using the communication standard determined by the function integration unit 514. Specifically, the function execution unit 512 periodically acquires monitor information of the integrated function from device A using the communication standard defined for the corresponding function in the used standard table 523, and updates the monitor screen 542. For example, the function execution unit 512 acquires information such as "cooling" and "heating" using communication standard A and controller A, acquires information on "set temperature" and "ECO" using communication standard B and controller B, and acquires information on "indoor temperature" and "outdoor temperature" using communication standard C and controller C.

[0069] Furthermore, when the function execution unit 512 accepts an operation from the user U on the monitor screen 542, it transmits operation information indicating the accepted operation to the device A using the communication standard defined for the corresponding function in the used standard table 523. For example, the function execution unit 512 transmits operation information for setting "cooling," "heating," etc. to the device A using communication standard A and controller A, transmits operation information for setting the "set temperature" to the device A using communication standard B and controller B, and transmits operation information for setting the "timer" to the device A using communication standard C and controller C. In this way, the function execution unit 512 executes the operation accepted from the user U on the device A.

[0070] In this way, the function execution unit 512 comprehensively displays functions compatible with at least one of the communication standards A to C and executes them in response to an operation by the user U. This improves usability because it eliminates the need for the user U to change the communication standard to be used depending on the function he or she wishes to execute. Furthermore, when executing overlapping functions for multiple communication standards, the function is executed using one of the communication standards, thereby suppressing an increase in communication traffic.

[0071] Next, the flow of processing executed in the device management system 1 will be described with reference to FIGS.

[0072] 9 is a process for registering device A via controller A when device A has not yet been registered in terminal device 50. The process shown in Fig. 9 is executed, for example, when device A is newly installed in building 5 or when controller A is newly installed in building 5.

[0073] 9 starts, the controller A makes an initial connection to the device A (step S1). In the initial connection, the controller A establishes communication with the device A according to the communication standard A, and makes it possible to communicate with the device A according to the communication standard A.

[0074] When communication is successfully established, device A notifies controller A of the completion of the initial connection (step S2). At this time, device A transmits its function information and device information to controller A. Controller A stores the function information and device information acquired from device A in a storage unit.

[0075] Next, in the terminal device 50, the control unit 51 receives a registration instruction for device A from the user U (step S3). Upon receiving the registration instruction, the control unit 51 transmits the received registration instruction to the controller A via the server 30 (step S4). Upon receiving the registration instruction from the terminal device 50, the controller A transmits function information and device information for device A to the terminal device 50 via the server 30 (step S5).

[0076] In the terminal device 50, when the control unit 51 receives the function information and device information of device A from the controller A, it generates a function list 521 indicating the functions that can be executed by the controller A on device A, for example, as shown in Figure 3 (step S6).

[0077] After generating the function list 521, the control unit 51 notifies the user U that the registration of device A has been completed (step S7). For example, the control unit 51 displays a screen indicating that the registration of device A has been completed on the display unit 54. This allows the user U to confirm that the registration of device A has been completed successfully. This completes the device registration process shown in Fig. 9. In steps S3 to S7, the control unit 51 functions as the device registration unit 511.

[0078] Next, the device registration process shown in Fig. 10 will be described. The device registration process shown in Fig. 10 is a process for registering device A via a controller B different from controller A after device A has already been registered in terminal device 50 via controller A through the device registration process shown in Fig. 9. The process shown in Fig. 10 is executed, for example, when device A and controller A are already installed in building 5 and controller B is newly installed in building 5.

[0079] 10, the processing of steps S11 to S16 is the registration processing of device A via controller B. The processing of steps S11 to S16 is the same as the registration processing of device A via controller A in steps S1 to S6 shown in FIG. 9, except that "controller A" is replaced with "controller B," and therefore a description thereof will be omitted.

[0080] When device A is registered via controller B in steps S11 to S16, control unit 51 functions as identical device determination unit 513 and determines whether newly registered device A is identical to any of devices 10 already registered in terminal device 50 (step S17). Specifically, control unit 51 compares device information of newly registered device A with device information of already registered devices 10 to determine the identity of the devices 10.

[0081] If the newly registered device A is identical to any of the registered devices 10 (step S17; YES), the control unit 51 functions as the function integration unit 514 and executes the function integration process (step S18). Details of the function integration process of step S18 will be described with reference to FIG. 11.

[0082] When the function integration process shown in FIG. 11 starts, the control unit 51 combines the function lists 521 of multiple devices 10 that are determined to be identical to generate a function database 522 such as that shown in FIG. 5 (step S181).

[0083] After generating the function database 522, the control unit 51 sets a variable n, which indicates the number of a function in the function database 522, to 1 (step S182). Then, the control unit 51 determines the number of communication standards for which the nth function is defined in the function database 522 (step S183).

[0084] If the nth function is defined for multiple communication standards (step S183; multiple), the control unit 51 determines which communication standard to use from the multiple communication standards based on the determination criteria defined in the determination logic 524 (step S184). On the other hand, if the nth function is defined for only one communication standard (step S183; one), the control unit 51 determines that one communication standard is the communication standard to use (step S185). Furthermore, if the nth function is defined for zero communication standards (step S183; zero), the control unit 51 determines that there is no communication standard to use (step S186).

[0085] After steps S184 to S186, the control unit 51 increments the variable n (step S187). Then, the control unit 51 determines whether the nth function is defined in the function database 522 (step S188). If the nth function is defined (step S188; YES), the control unit 51 returns the process to step S183 and executes the processes of steps S183 to S188 on the incremented variable n. In this way, the control unit 51 determines the usage standard for each of the multiple functions defined in the function database 522.

[0086] Finally, when the n-th function is no longer defined in the function database 522 (step S188; NO), the control unit 51 associates each function defined in the function database 522 with the usage standard determined for each function, thereby generating, for example, the usage standard table 523 shown in Fig. 6 (step S189). This completes the function integration process shown in Fig. 11.

[0087] 10, after the function integration process is executed, the control unit 51 notifies the user U that the registration of the device A has been completed (step S19). The process of step S19 is the same as the process of step S7 shown in FIG.

[0088] On the other hand, if the newly registered device A is not identical to any of the registered devices 10 in step S17 (step S17; NO), the control unit 51 skips the function integration process in step S18 and notifies the completion of registration in step S19. This completes the device registration process shown in FIG.

[0089] Next, the function execution process shown in Fig. 12 will be described. The function execution process is executed when the user U causes any of the registered devices 10 to execute a function after at least one device 10 has been registered in the terminal device 50 by the device registration process shown in Fig. 9 or 10. In the function execution process, the control unit 51 functions as a function execution unit 512.

[0090] When the function execution process starts, the control unit 51 displays a device selection screen 541 on the display unit 54 (step S21). On the device selection screen 541, the control unit 51 displays a list of registered devices 10 as items selectable by the user U, as shown on the left side of Fig. 8, for example. At this time, the control unit 51 aggregates and displays devices 10 that are registered using different communication standards and that are determined to be the same as the same device 10 under a single item.

[0091] When the device selection screen 541 is displayed, the control unit 51 accepts the selection of the device 10 from the user U (step S22). When the selection of the device 10 is accepted, the control unit 51 acquires the monitor information of the selected device 10 from the selected device 10 (step S23). At this time, if the functions of the selected device 10 are integrated, the control unit 51 acquires the monitor information from the selected device 10 using the communication standard defined in the used standard table 523.

[0092] When the monitor information is acquired, the control unit 51 displays a monitor screen 542 showing the acquired monitor information on the display unit 54 (step S24), as shown on the right side of Fig. 8. On the monitor screen 542, the control unit 51 accepts an operation selection from the user U (step S25).

[0093] When the selection of the operation is accepted, the control unit 51 transmits operation information indicating the accepted operation to the selected device 10 (step S26). As a result, the control unit 51 operates the selected device 10. At this time, if the functions of the selected device 10 are integrated, the control unit 51 transmits the operation information to the selected device 10 using the communication standard defined in the used standard table 523. This completes the function execution process shown in FIG. 12.

[0094] As described above, the terminal device 50 according to the first embodiment determines whether the first device 10 registered via the first controller corresponding to the first communication standard and the second device 10 registered via the second controller corresponding to the second communication standard are the same device, and if it is determined that the first device 10 and the second device 10 are the same device 10, the terminal device 50 displays the first device 10 and the second device 10 as the same device 10 on a function execution screen for executing the functions of the first device 10 and the second device 10. In this way, the same device 10 is not treated as separate devices 10 for each communication standard, but is aggregated and displayed as a single device 10, thereby improving usability when managing devices 10 that are compatible with multiple different communication standards.

[0095] In particular, in recent years, a variety of communication standards have been developed and proliferated as communication standards for remotely managing devices 10. In such a situation, as the number of devices 10 registered separately using different communication standards increases, it becomes difficult to understand which device 10 each represents. In contrast, in the first embodiment, devices 10 registered separately using different communication standards are automatically consolidated into one without the user U being aware of it. Therefore, the number of physical devices 10 can be made to match the number of logical devices 10 on the application software without the user U having to go to the trouble of sorting and deleting the registered devices 10.

[0096] Furthermore, when the terminal device 50 according to the first embodiment determines that the first device 10 and the second device 10 are the same device 10, the terminal device 50 integrates the functions of the first device 10 and the second device 10. This allows the user U to comprehensively recognize functions that can be executed by a single device 10 using multiple communication standards. Furthermore, since the user U does not need to change the communication standard to be used depending on the function that he or she wishes to execute, usability can be improved.

[0097] (Embodiment 2) Next, a description will be given of embodiment 2. Description of the same configurations and functions as embodiment 1 will be omitted as appropriate.

[0098] In the first embodiment, when the integrated function is compatible with all of a plurality of communication standards, the function integration unit 514 determines the communication standard to be used for the integrated function based on the number of function items or granularity of each of the plurality of communication standards. In contrast, in the second embodiment, when the integrated function is compatible with all of a plurality of communication standards, the function integration unit 514 determines the communication standard to be used for the integrated function based on at least one of the communication line, presence or absence of encryption, response speed, and communication method for each of the plurality of communication standards.

[0099] More specifically, in the second embodiment, the function integration unit 514 determines the standard to be used in accordance with a criterion selected depending on the situation from among a plurality of criterion defined in the determination logic 524 shown in Fig. 13. In the example of Fig. 13, the determination logic 524 defines the communication line, the presence or absence of encryption, the response speed, and the communication method as the criterion.

[0100] For example, when emphasis is placed on communication speed or communication stability, the function integration unit 514 determines the standard to be used by prioritizing a wired communication standard over a wireless communication standard. When emphasis is placed on communication reliability, the function integration unit 514 determines the standard to be used by prioritizing an encrypted communication standard over an unencrypted communication standard. When emphasis is placed on usability, the function integration unit 514 determines the standard to be used by prioritizing a communication standard with a fast response speed over a communication standard with a slow response speed. When emphasis is placed on communication reliability, the function integration unit 514 determines the standard to be used by prioritizing a communication standard with a bidirectional communication method over a communication standard with a unidirectional communication method. The function integration unit 514 may use a combination of such multiple determination criteria.

[0101] Which of these multiple determination criteria to use may be preset or may be freely selectable by the user U. Alternatively, the determination criteria to be used may be changed for each device type or function. For example, reliability is emphasized for devices 10 that pose safety risks, such as electronic locks and induction cookers. In this case, the function integration unit 514 determines an encrypted communication standard or a two-way communication standard to be used. Alternatively, response speed is emphasized for simple devices 10 such as lighting or simple functions such as "ON" and "OFF." In this case, the function integration unit 514 determines a high-speed communication standard to be used.

[0102] As described above, in the second embodiment, the function integration unit 514 determines the usage standard in accordance with the criteria selected depending on the situation. This allows the function integration unit 514 to flexibly determine the usage standard in various situations such as the device type, the request of the user U, etc.

[0103] Third Embodiment Next, a third embodiment will be described. Descriptions of the same configurations and functions as those of the first and second embodiments will be omitted where appropriate.

[0104] In the first embodiment, the same-device determination unit 513 determines, based on the device information, whether the first device 10 registered via the first controller 20 and the second device 10 registered via the second controller 20 are the same device 10. In contrast, in the third embodiment, the same-device determination unit 513 determines, based on an input from the user U, whether the first device 10 and the second device 10 are the same device 10.

[0105] The device registration process shown in Fig. 14 is a process of registering device A via controller A and controller C separately. The device registration process according to the third embodiment will be described below with reference to Fig. 14. In the following, device A registered via controller A corresponds to the first device 10, and device A registered via controller C corresponds to the second device 10.

[0106] 14 starts, the control unit 51 executes the registration process for device A via controller A by the processes of steps S1 to S7 shown in Fig. 9. Next, the control unit 51 executes the registration process for device A via controller C (steps S301 to S306). The processes of steps S301 to S306 are the same as those in the case where "controller A" in steps S1 to S6 is replaced with "controller C."

[0107] However, the second device information, which is the device information acquired from the controller C in the processing of step S305, includes information on the device type of the device A, which is the second device 10, but does not include identification information that can uniquely identify the device A. In other words, the following describes a case where the control unit 51 can identify the device type of the second device 10 but cannot uniquely identify the second device 10.

[0108] When device A is registered via controller C in steps S301 to S306, the control unit 51 identifies candidates for identical devices 10 for device A based on the device information of device A acquired from controller C (step S307). In steps S307 to S309, the control unit 51 functions as an identical device determination unit 513.

[0109] Specifically, based on the device type information included in the device information of device A acquired from the controller C, the control unit 51 identifies at least one device 10 having a matching device type from among the multiple devices 10 already registered by the device registration unit 511 as a candidate for the same device 10. For example, if the device type of the second device 10 is an air conditioner, the control unit 51 identifies at least one device 10 having a device type of air conditioner from among the multiple registered devices 10 as a candidate for the device 10 that is the same as the second device 10.

[0110] When the candidates for the same device 10 are identified, the control unit 51 displays an integrated proposal screen 543 showing the identified candidates on the display unit 54 (step S308). On the integrated proposal screen 543, the control unit 51 displays "device A registered via controller A" and "device A' registered via controller A" as candidates for the same device 10 for device A registered via controller C, as shown in Fig. 15, for example.

[0111] On the integration proposal screen 543, the control unit 51 displays a message suggesting to the user U to select the same device 10 as the newly registered device A. The control unit 51 also displays a message suggesting integration of functions between the newly registered device A and the selected device 10. If the user U permits the integration, the user U operates the operation unit 53 to select a device 10 that the user U determines to be the same as the newly registered device A from among the candidates displayed on the integration proposal screen 543.

[0112] When the integration proposal screen 543 is displayed, the control unit 51 determines whether or not integration has been permitted by the user U (step S309). If integration has been permitted (step S309; ​​YES), the control unit 51 executes function integration processing (step S310). The function integration processing of step S310 is the same as the function integration processing shown in FIG. 11.

[0113] When the function integration process is completed, the control unit 51 notifies the user U that the registration of the device A has been completed (step S311). On the other hand, if the integration is not permitted (step S309; ​​NO), the control unit 51 skips the process of step S310.

[0114] As described above, the terminal device 50 according to the third embodiment determines whether the devices 10 registered separately using different communication standards are the same, based on the input of the user U. In this way, by using the judgment of the user U as part of the process of determining the identity of the devices 10, it becomes possible to determine the identity of the devices 10 even when identification information of the newly registered device 10 cannot be obtained, and functions can be integrated.

[0115] (Fourth Embodiment) Next, a fourth embodiment will be described. Descriptions of the same configurations and functions as those of the first to third embodiments will be omitted where appropriate.

[0116] In the first embodiment, the same-device determination unit 513 determines, based on the device information, whether the first device 10 registered via the first controller 20 and the second device 10 registered via the second controller 20 are the same device 10. In contrast, in the fourth embodiment, the same-device determination unit 513 determines, based on the state of the first device 10 when the second device 10 is operated, whether the first device 10 and the second device 10 are the same device 10.

[0117] The device registration process shown in Fig. 16 is a process of registering device A via controller A and controller D separately. The device registration process according to the fourth embodiment will be described below with reference to Fig. 16. In the following, device A registered via controller A corresponds to the first device 10, and device A registered via controller D corresponds to the second device 10.

[0118] 16 starts, the control unit 51 executes the registration process for device A via controller A by the processes of steps S1 to S7 shown in Fig. 9. Next, the control unit 51 executes the registration process for device A via controller D (steps S401 to S406). The processes of steps S401 to S406 are the same as those in the case where "controller C" in steps S301 to S306 of the third embodiment is replaced with "controller D."

[0119] When device A is registered via controller D in steps S401 to S406, control unit 51 transmits operation information for device A to controller D to determine whether or not there is a device 10 identical to the newly registered device A (step S407). For example, control unit 51 transmits operation information indicating an operation to change the set temperature, set mode, etc. of device A to controller D. In steps S407 to S416, control unit 51 functions as identical device determination unit 513.

[0120] When controller D receives operation information from terminal device 50, it transmits the received operation information to device A using communication standard D (step S408). When device A receives operation information from controller D, it changes the state of device A in accordance with the received operation information (step S409). When device A successfully completes the state change, it transmits an operation completion notification to controller D (step S410). When controller D receives the operation completion notification from device A, it transmits the received completion notification to terminal device 50 (step S411).

[0121] Next, in the terminal device 50, the control unit 51 requests the status information of device A from the controller A to determine whether device A that has already been registered via the controller A is the same as device A newly registered via the controller D (step S412). When the controller A receives the request from the terminal device 50, it transmits the received request to device A using the communication standard A (step S413). When the device A receives the request from the controller A, it transmits status information indicating the current status of device A to the controller A (step S414). When the controller A receives the status information from device A, it transmits the received status information to the terminal device 50 (step S415).

[0122] In the terminal device 50, when the control unit 51 receives the status information from the controller A, the control unit 51 determines whether the newly registered device A via the controller D is the same as the device A already registered via the controller A (step S416). Specifically, the control unit 51 determines that the two devices 10 are the same when the status indicated in the status information received in step S415 matches the operation content in the operation information transmitted in step S407. For example, when operation information for changing the set temperature to 25° C. is transmitted to the device A via the controller D and the set temperature indicated in the status information acquired via the controller A is 25° C., the control unit 51 determines that the two devices 10 are the same.

[0123] The control unit 51 executes the processes of steps S412 to S416 for at least one device 10, of the multiple devices 10 already registered by the device registration unit 511, whose device type matches that of device A registered via controller D. In this way, the control unit 51 determines whether or not there is a device 10 identical to the newly registered device A.

[0124] If the newly registered device A is identical to any of the registered devices 10 (step S416; YES), the control unit 51 executes a function integration process (step S417). The function integration process of step S417 is the same as the function integration process shown in FIG.

[0125] When the function integration process is completed, the control unit 51 notifies the user U of the completion of the registration of the device A (step S418). On the other hand, if the newly registered device A is not identical to any of the registered devices 10 (step S416; NO), the control unit 51 skips the process of step S417.

[0126] As described above, the terminal device 50 according to the fourth embodiment determines whether the first device 10 and the second device 10 are the same device 10, based on the state of the first device 10 when the second device 10 is operated. In this way, even if the identification information of the newly registered device 10 cannot be acquired, it is possible to determine the identity of the devices 10 without requiring operation by the user U, and functions can be integrated.

[0127] Note that even if the newly registered device 10 is different from the device A, there is a possibility that the operation content on the device A coincidentally matches the state of the device 10. To avoid such an erroneous determination due to coincidence, the control unit 51 may repeat the processes of steps S407 to S416 multiple times and determine the identity of the device 10 based on the results of the multiple determinations.

[0128] Alternatively, instead of operating the newly registered device A, the control unit 51 may acquire status information at the same time from both the newly registered device A and the already registered device 10. Then, the control unit 51 may compare the acquired status information to determine whether they are identical.

[0129] (Embodiment 5) Next, a description will be given of embodiment 5. Descriptions of the same configurations and functions as those of embodiments 1 to 4 will be omitted where appropriate.

[0130] In the above-described first embodiment, the function integration unit 514 determines the communication standard to be used for the integrated functions in accordance with the determination criteria defined in the determination logic 524. In contrast, in the fifth embodiment, the function integration unit 514 determines the communication standard in accordance with an input from the user U.

[0131] In the fifth embodiment, the function integration unit 514 displays, for example, a communication standard selection screen 544 shown in Fig. 17 on the display unit 54 before the monitor screen 542 shown on the right side of Fig. 8 is displayed and before or after the device selection screen 541 shown on the left side of Fig. 8 is displayed. On the communication standard selection screen 544, the function integration unit 514 displays, as items selectable by the user U, the multiple communication standards used when the device 10 selected on the device selection screen 541 was registered.

[0132] For example, when "Device A" is selected on device selection screen 541, function integration unit 514 displays three communication standards A to C on communication standard selection screen 544. On communication standard selection screen 544, function integration unit 514 accepts from user U a selection of a communication standard to be preferentially used when executing the functions of device A from among communication standards A to C.

[0133] For example, if user U selects "communication standard A," the function integration unit 514 determines that, among the multiple functions executable on device A, the communication standard to be used for functions executable on communication standard A is communication standard A. In addition, among the multiple functions executable on device A, the function integration unit 514 determines, from communication standards B and C, the communication standard to be used for functions that cannot be executed on communication standard A.

[0134] Once the communication standard is determined in this manner, the function execution unit 512 displays the monitor screen 542. On the monitor screen 542, the function execution unit 512 operates or monitors the device A using the communication standard determined by the function integration unit 514. In this manner, the terminal device 50 according to the fifth embodiment determines the communication standard in accordance with the input of the user U. This allows the user U's requests to be reflected in the integration of functions.

[0135] (Modifications) Although the embodiments have been described above, it is possible to combine the embodiments, or to modify or omit the embodiments as appropriate.

[0136] For example, in the above embodiment, the control unit 51 of the terminal device 50 includes the device registration unit 511, the function execution unit 512, the same device determination unit 513, and the function integration unit 514. However, this configuration is just an example, and the functions of each unit may be provided in any device in the device management system 1. For example, the function of the same device determination unit 513 or the function integration unit 514 may be provided in the server 30.

[0137] Furthermore, the terminal device 50 or the device management system 1 may not have the functionality of the function integration unit 514. For example, when "communication standard A" is selected on the communication standard selection screen 544 shown in FIG. 17 , the function execution unit 512 displays only functions executable for device A using communication standard A on the monitor screen 542 and executes only functions defined by communication standard A. Similarly, when "communication standard B" or "communication standard C" is selected, the function execution unit 512 displays only functions executable for device A using communication standard B or communication standard C on the monitor screen 542 and executes only functions defined by communication standard B or communication standard C. In this way, even without integrating functions, multiple devices 10 registered separately via different controllers can be displayed as the same device 10, thereby improving usability.

[0138] In the above embodiment, the control unit 51 functions as the device registration unit 511, the function execution unit 512, the same device determination unit 513, and the function integration unit 514 by the CPU executing a program stored in the ROM or the storage unit 52. However, the control unit 51 may be dedicated hardware. Examples of dedicated hardware include a single circuit, a composite circuit, a programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a combination thereof. When the control unit 51 is dedicated hardware, the functions of each unit may be realized by individual hardware, or the functions of each unit may be realized together by a single piece of hardware.

[0139] In addition, some of the functions of each unit may be realized by dedicated hardware, and other functions may be realized by software or firmware. In this way, the control unit 51 can realize each of the above-mentioned functions by hardware, software, firmware, or a combination of these.

[0140] By applying a program that defines the operation of the control unit 51 to an existing computer such as a personal computer or an information terminal device, the computer can be made to function as the terminal device 50.

[0141] Furthermore, the method of distribution of such a program is arbitrary, and for example, it may be stored on a computer-readable recording medium such as a CD-ROM (Compact Disk ROM), a DVD (Digital Versatile Disk), an MO (Magneto Optical Disk), or a memory card and distributed, or it may be distributed via a communication network such as the Internet.

[0142] The present disclosure allows various embodiments and modifications without departing from the broad spirit and scope of the present disclosure. Furthermore, the above-described embodiments are intended to illustrate the present disclosure and do not limit the scope of the present disclosure. That is, the scope of the present disclosure is defined by the claims, not the embodiments. Various modifications made within the scope of the claims and the meaning of equivalent disclosures are considered to be within the scope of the present disclosure.

[0143] This application is based on Japanese Patent Application No. 2024-90496 filed on June 4, 2024. The entire specification, claims, and drawings of Japanese Patent Application No. 2024-90496 are incorporated herein by reference.

[0144] The present disclosure is applicable to a system for managing devices.

[0145] Various aspects of the present disclosure are summarized below as appendices.

[0146] (Supplementary Note 1) A terminal device comprising: identical device determination means for determining whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and function execution means for, when the identical device determination means determines that the first device and the second device are the same device, displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and the second device. (Supplementary Note 2) The terminal device according to Supplementary Note 1 further comprises: function integration means for, when the identical device determination means determines that the first device and the second device are the same device, integrating the functions of the first device and the second device, and the function execution means displays the functions integrated by the function integration means on the function execution screen as functions executable for the same device. (Supplementary Note 3) The terminal device according to Supplementary Note 2, wherein the function integration means determines a function compatible with at least one of the first communication standard and the second communication standard as the integrated function, determines a communication standard to be used for the integrated function from among the first communication standard and the second communication standard, and the function execution means executes the integrated function using the communication standard determined by the function integration means. (Supplementary Note 4) The terminal device according to Supplementary Note 3, wherein, when the integrated function is compatible with both the first communication standard and the second communication standard, the function integration means determines the communication standard to be used for the integrated function based on the number of function items or granularity of each of the first communication standard and the second communication standard. (Supplementary Note 5) The terminal device according to Supplementary Note 3 or 4, wherein, when the integrated function is compatible with both the first communication standard and the second communication standard, the function integration means determines the communication standard to be used for the integrated function based on at least one of the communication line, presence or absence of encryption, response speed, and communication method for each of the first communication standard and the second communication standard.(Supplementary Note 6) The terminal device according to any one of Supplements 1 to 5, wherein the same device determination means determines whether the first device and the second device are the same device based on first device information about the first device acquired from the first controller and second device information about the second device acquired from the second controller. (Supplementary Note 7) The terminal device according to any one of Supplements 1 to 6, wherein the same device determination means, when the second device is registered via the second controller, displays at least one device as a candidate for the same device for the second device, and determines that a device selected by a user from the at least one device is the same device. (Supplementary Note 8) The terminal device according to claim 7, wherein the same device determination means identifies the at least one device based on device information about the second device acquired from the second controller, and displays the identified at least one device. (Supplementary Note 9) The terminal device according to any one of Supplementary Notes 1 to 8, wherein the same-device determination means determines whether the first device and the second device are the same device based on a state of the first device when the second device is operated. (Supplementary Note 10) A device management system comprising: same-device determination means for determining whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and function execution means for displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and the second device when the same-device determination means determines that the first device and the second device are the same device.(Supplementary Note 11) A device management method comprising: determining whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and, when it is determined that the first device and the second device are the same device, displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and the second device. (Supplementary Note 12) A program causing a computer to function as: same-device determination means for determining whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and, when it is determined by the same-device determination means that the first device and the second device are the same device, displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and the second device.

[0147] 1 Equipment management system, 5 Building, 10 Equipment, 20 Controller, 30 Server, 50 Terminal device, 51 Control unit, 52 Memory unit, 53 Operation unit, 54 Display unit, 55 Communication unit, 511 Equipment registration unit, 512 Function execution unit, 513 Same equipment determination unit, 514 Function integration unit, 521 Function list, 522 Function database, 523 Usage standard table, 524 Determination logic, 541 Equipment selection screen, 542 Monitor screen, 543 Integration proposal screen, 544 Communication standard selection screen

Claims

1. A terminal device comprising: an identical device determination means for determining whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and a function execution means for displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and functions of the second device when the identical device determination means determines that the first device and the second device are the same device.

2. The terminal device according to claim 1, further comprising a function integration means for integrating functions of the first device and functions of the second device when the same device determination means determines that the first device and the second device are the same device, and the function execution means displays the functions integrated by the function integration means on the function execution screen as functions that can be executed on the same device.

3. The terminal device according to claim 2, wherein the function integration means determines a function corresponding to at least one of the first communication standard and the second communication standard as the integrated function, determines a communication standard to be used for the integrated function from among the first communication standard and the second communication standard, and the function execution means executes the integrated function using the communication standard determined by the function integration means.

4. The terminal device according to claim 3, wherein, when the integrated function is compatible with both the first communication standard and the second communication standard, the function integration means determines the communication standard to be used for the integrated function based on the number of function items or granularity in each of the first communication standard and the second communication standard.

5. The terminal device according to claim 3 or 4, wherein, when the integrated function is compatible with both the first communication standard and the second communication standard, the function integration means determines the communication standard to be used for the integrated function based on at least one of the communication line, presence or absence of encryption, response speed, and communication method for each of the first communication standard and the second communication standard.

6. A terminal device according to any one of claims 1 to 5, wherein the same device determination means determines whether the first device and the second device are the same device based on first device information about the first device obtained from the first controller and second device information about the second device obtained from the second controller.

7. A terminal device according to any one of claims 1 to 6, wherein the same device determination means, when the second device is registered via the second controller, displays at least one device as a candidate for the same device for the second device, and determines that a device selected by a user from the at least one device is the same device.

8. The terminal device according to claim 7, wherein the same device determination means identifies the at least one device based on device information relating to the second device acquired from the second controller, and displays the identified at least one device.

9. A terminal device according to any one of claims 1 to 8, wherein the same device determination means determines whether the first device and the second device are the same device based on the state of the first device when the second device is operated.

10. A device management system comprising: an identical device determination means for determining whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and a function execution means for displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and functions of the second device when the identical device determination means determines that the first device and the second device are the same device.

11. A device management method comprising: determining whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and, if it is determined that the first device and the second device are the same device, displaying the first device and the second device as the same device on a function execution screen for executing functions of the first device and the second device.

12. A program that causes a computer to function as: an identical device determination means that determines whether a first device registered via a first controller compatible with a first communication standard and a second device registered via a second controller compatible with a second communication standard are the same device; and a function execution means that, when the identical device determination means determines that the first device and the second device are the same device, displays the first device and the second device as the same device on a function execution screen for executing the functions of the first device and the second device.

Images