Device management system, mobile terminal, and program

Abstract

To improve operability of graphical user interfaces for operating multiple devices arranged in a facility.SOLUTION: A mobile terminal can display, on a touch panel display, multiple graphical user interfaces for operating respective multiple devices arranged in a facility. The mobile terminal identifies the location of the mobile terminal within the facility based on location information received from a location information transmitting device. Among the graphical user interfaces displayed on the touch panel display, the mobile terminal displays only a graphical user interface for operating a device associated with the location of the mobile terminal specified based on the location information.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] This specification discloses techniques relating to a device management system, a mobile terminal, and a program. [Background technology]

[0002] In recent years, a system has been proposed that enables operation of multiple devices, such as lighting equipment and air conditioning equipment, located in facilities such as homes, office buildings, and factories, via a graphical user interface displayed on the touch panel of a mobile device (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2021-108152 A Summary of the Invention [Problem to be solved by the invention]

[0004] Although it is often sufficient for facility users to be able to operate devices installed at their current location within the facility, a graphical user interface that can operate devices in locations unrelated to the current location has a problem in that the structure becomes complicated according to the number of operable devices, making operation cumbersome. Also, with such a graphical user interface, there is a possibility that a device in a location unrelated to the current location may be mistakenly operated. [Means for solving the problem]

[0005] The technology disclosed in this specification can be realized in the following forms.

[0006] (1) One embodiment disclosed in this specification is a mobile terminal configured to be capable of operating a plurality of devices arranged in a facility. The mobile terminal includes a first wireless circuit configured to be capable of communicating via wireless communication with a device control device that controls the plurality of devices, a second wireless circuit configured to be capable of communicating via wireless communication with a plurality of location information transmission devices that transmit location information indicating locations within the facility, a touch panel display, a processor, and a memory that stores program instructions. By executing the program instructions by the processor, the mobile terminal is capable of displaying a plurality of graphical user interfaces on the touch panel display for operating each of the plurality of devices; accepting operation input for operating the device via the graphical user interfaces displayed on the touch panel display; using the first wireless circuit, requesting the device control device to control the device based on the operation input accepted via the graphical user interfaces; receiving the location information from at least one of the plurality of location information transmission devices using the second wireless circuit; identifying the location of the mobile terminal within the facility based on the location information received from the location information transmission device; and limiting the graphical user interface displayed on the touch panel display to a graphical user interface among the plurality of graphical user interfaces for operating a device associated with the location of the mobile terminal identified based on the location information. According to this embodiment of the mobile terminal, the graphical user interface displayed on the touch panel display is limited to a graphical user interface for operating devices associated with the location of the mobile terminal within the facility, thereby improving the operability of the graphical user interface and preventing the mobile terminal from accidentally operating devices located in places unrelated to the mobile terminal's current location.

[0007] (2) The mobile terminal of the above-mentioned embodiment may use the first wireless circuit to acquire, by the processor executing the program instructions, operation status information indicating an operation status of an apparatus operable by the graphical user interface displayed on the touch panel display from the apparatus control apparatus, and may notify the operation status by the graphical user interface displayed on the touch panel display based on the operation status information received from the apparatus control apparatus. According to the mobile terminal of this embodiment, an operator of the mobile terminal can operate an apparatus while checking the operation status by using the graphical user interface.

[0008] (3) The mobile terminal of the above-mentioned embodiment may, by executing the program instructions by the processor, use the first wireless circuit to inquire of the device control device, thereby identifying a device associated with the position of the mobile terminal identified based on the location information; and may limit the graphical user interface displayed on the touch panel display to a graphical user interface for operating the device identified based on the inquiry to the device control device. According to this embodiment of the mobile terminal, a device to be operated by the graphical user interface can be set based on the judgment of the device control device. Furthermore, the processing load of the mobile terminal can be reduced compared to a case where a device to be operated by the graphical user interface is set without interacting with the device control device.

[0009] (4) The mobile terminal of the above-mentioned embodiment may use the first wireless circuit to acquire equipment layout data from the equipment control device, in which each of the plurality of equipment is associated with each location in the facility, by executing the program instructions by the processor; store the equipment layout data acquired from the equipment control device in the memory; identify an equipment associated with the position of the mobile terminal identified based on the location information based on the equipment layout data stored in the memory; and limit the graphical user interface displayed on the touch panel display to a graphical user interface for operating the equipment identified based on the equipment layout data among the plurality of graphical user interfaces. According to the mobile terminal of this embodiment, an equipment to be operated by the graphical user interface can be set based on the equipment layout data acquired from the equipment control device. Furthermore, the processing load of the equipment control device can be reduced compared to a case in which an equipment to be operated by the graphical user interface is set through an exchange with the equipment control device.

[0010] (5) The mobile terminal of the above-mentioned embodiment may store in advance in the memory equipment location data in which each of the plurality of devices is associated with each location in the facility; identify an equipment associated with the position of the mobile terminal identified based on the location information based on the equipment location data stored in the memory; and limit the graphical user interface displayed on the touch panel display to a graphical user interface for operating the equipment identified based on the equipment location data among the plurality of graphical user interfaces. According to the mobile terminal of this embodiment, an equipment to be operated by the graphical user interface can be set based on the equipment location data stored in the memory in advance. Furthermore, the processing load of the equipment control device can be reduced compared to a case in which an equipment to be operated by the graphical user interface is set through an exchange with the equipment control device.

[0011] (6) In the mobile terminal of the above-mentioned aspect, the processor may execute the program instructions to delete the graphical user interface displayed on the touch panel display based on an instruction from the device control device received by the first wireless circuit. According to the mobile terminal of this aspect, it is possible to delete a graphical user interface that is determined by the device control device to be inappropriate for display on the touch panel display.

[0012] (7) In the mobile terminal of the above-mentioned aspect, when the location information cannot be received for a predetermined period of time using the second wireless circuit by executing the program instructions by the processor, the mobile terminal may delete the graphical user interface displayed on the touch panel display. According to this aspect of the mobile terminal, the graphical user interface can be deleted from the touch panel display when there is a possibility that the mobile terminal is not present within a facility.

[0013] (8) In the mobile terminal of the above aspect, the plurality of location information transmission devices may include at least one of a BLE beacon device, an RFID tag, and a wireless LAN access point. With this mobile terminal, location information indicating a location within a facility can be easily used via wireless communication.

[0014] (9) In the mobile terminal of the above aspect, the plurality of devices may include at least one of lighting equipment, air conditioning equipment, motorized shades, underfloor heating, audio equipment, video equipment, motorized doors, and electric locks. The mobile terminal of this aspect can improve the operability of devices that require adjustment for each location in the facility.

[0015] The technology disclosed in this specification can be realized in various forms other than a mobile terminal, such as a device management system, a device control device, a location information transmission device, and a computer program. [Brief description of the drawings]

[0016] [Figure 1] FIG. 1 is an explanatory diagram showing a configuration of a device management system. [Diagram 2] FIG. 2 is an explanatory diagram showing a detailed configuration of a mobile terminal. [Diagram 3] FIG. 2 is an explanatory diagram showing an example of a GUI displayed on a touch panel display. [Figure 4] 2 is an explanatory diagram showing a detailed configuration of a device control server; FIG. [Diagram 5] 11 is a flowchart showing a GUI display process executed by the mobile terminal. [Figure 6] 13 is a flowchart showing a GUI display process executed by the device control server. [Figure 7] 13 is a flowchart showing a GUI reception process executed by the mobile terminal. [Figure 8] 13 is a flowchart showing a GUI reception process executed by the device control server. [Figure 9] 13 is a flowchart showing a GUI deletion process executed by the mobile terminal. [Figure 10] 13 is a flowchart showing a GUI deletion process executed by the device control server. [Figure 11] FIG. 11 is an explanatory diagram showing a detailed configuration of a mobile terminal in a second embodiment. [Figure 12] 13 is a flowchart showing a GUI display process executed by a mobile terminal in the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] A. First embodiment 1 is an explanatory diagram showing the configuration of a device management system 10. The device management system 10 is a system that manages multiple devices 20 arranged in a facility 800. The facility 800 is a relatively large space in which multiple devices 20 can be installed. In this embodiment, the facility 800 is an office building. In other embodiments, the facility 800 may be a factory, a commercial facility, or a residence.

[0018] The device management system 10 manages devices 20 arranged in a facility 800 in association with locations 810 in the facility 800 where the devices 20 are arranged. The locations 810 in the facility 800 can be set in units of building floors, corridors, sections, rooms, partitioned seats, furniture, etc. In the description of this specification, the reference number "810" is used to collectively indicate multiple locations, and a reference number with a subnumber added to the reference number "810" is used to individually indicate a specific location among the multiple locations (e.g., 810-1, 810-2, 810-3). In the example of FIG. 1, each of the locations 810-1, 810-2, and 810-3 is a room provided in the facility 800. Each of the locations 810-1a and 810-1b is a partitioned seat (booth) provided in the location 810-1.

[0019] Each of the multiple devices 20 is an electronically controllable device disposed in the facility 800. In the description of this specification, the reference number "20" is used to collectively indicate the multiple devices, and a reference number with a subnumber attached to the reference number "20" is used to individually indicate a specific device among the multiple devices (e.g., 20-1a, 20-1b, 20-1c, etc.). In the example of FIG. 1, the device 20-1a is a lighting device disposed in the location 810-1a. The device 20-1b is a lighting device disposed in the location 810-1b. The device 20-1c is an air conditioner disposed in the location 810-1. The device 20-2a is a lighting device disposed in the location 810-2. The device 20-2c is an air conditioner disposed in the location 810-2. The multiple devices 20 may be electronically controllable devices, and may include not only air conditioners and lighting devices, but also motorized shades, floor heating, audio equipment, video equipment, motorized doors (gates), electric locks, and the like. This can improve the operability of the device 20 that requires adjustment for each location 810 within the facility 800.

[0020] The device management system 10 includes a plurality of beacon devices 50, a plurality of RFID tags 60, a plurality of access points 70, a plurality of motion sensors 80, a plurality of mobile terminals 100, a device control server 200, and an equipment control device 300. The device management system 10 is configured to enable a user of a facility 800 to operate a plurality of devices 20 arranged within the facility 800 using the mobile terminal 100.

[0021] Each of the multiple beacon devices 50 is a location information transmission device that is arranged in a facility 800 and transmits location information indicating a location 810 in the facility 800 using wireless communication. Each of the multiple beacon devices 50 transmits its own unique beacon identification information as location information using wireless communication. In the equipment management system 10, the beacon identification information of the beacon device 50 is managed in association with at least one of the multiple locations 810, and can be used as location information indicating the location 810 in the facility 800. In this embodiment, the beacon device 50 is a BLE beacon device that complies with BLE (Bluetooth Low Energy, registered trademark), which is one of the short-range wireless communication standards. This makes it easy to use the location information indicating the location 810 in the facility 800 via wireless communication. In the description of this specification, the symbol "50" is used to collectively indicate multiple beacon devices, and a symbol with a branch number added to the symbol "50" is used to individually indicate a specific beacon device among the multiple beacon devices (for example, 50-1, 50-2). 1, the beacon device 50-1 is located at a location 810-1, and the beacon device 50-2 is located at a location 810-2.

[0022] Each of the multiple RFID tags 60 is a location information transmission device that is placed in the facility 800 and transmits location information indicating a location 810 in the facility 800 using wireless communication. Each of the multiple RFID tags 60 transmits its unique tag identification information as location information using wireless communication. In the device management system 10, the tag identification information of the RFID tag 60 is managed in association with at least one of the multiple locations 810, and can be used as location information indicating the location 810 in the facility 800. In this embodiment, the RFID tag 60 is an NFC tag that complies with NFC (Near Field Communication, registered trademark), which is one of the short-range wireless communication standards. This makes it easy to use the location information indicating the location 810 in the facility 800 via wireless communication. In the description of this specification, the symbol "60" is used to collectively indicate multiple RFID tags, and a symbol with a branch number added to the symbol "60" is used to individually indicate a specific RFID tag among the multiple RFID tags (for example, 60-1a, 60-1b, 60-2). 1, RFID tag 60-1a is placed at location 810-1a, RFID tag 60-1b is placed at location 810-1b, and RFID tag 60-2 is placed at location 810-2.

[0023] Each of the multiple access points 70 is arranged in a facility 800 and configured to be able to construct a wireless LAN to which the mobile terminal 100 can be connected. The access point 70 relays between the wireless LAN connected to the mobile terminal 100 and the wired LAN connected to the device control server 200, thereby connecting the mobile terminal 100 and the device control server 200 so that they can communicate with each other. In the device management system 10, the identification information of the access point 70 used in the wireless LAN is managed in association with at least one of the multiple locations 810, and can be used as location information indicating the location 810 in the facility 800. This makes it easy to use the location information indicating the location 810 in the facility 800 via wireless communication. In the description of this specification, the symbol "70" is used to collectively indicate multiple access points, and a symbol with a branch number added to the symbol "70" is used to individually indicate a specific access point among the multiple access points (for example, 70-1, 70-2, 70-3).

[0024] Each of the multiple human presence sensors 80 is disposed within the facility 800 and is a sensor that detects people within the facility 800. In the device management system 10, each of the multiple human presence sensors 80 is managed in association with at least one of multiple locations 810 within the facility 800.

[0025] Each of the multiple mobile terminals 100 is an information device that can be carried by a user of the facility 800. In this embodiment, the mobile terminal 100 is a smartphone. The multiple mobile terminals 100 may be any information device that can be carried, and may include not only smartphones but also tablet terminals and personal computers. The mobile terminal 100 is configured to be able to operate the multiple devices 20 arranged in the facility 800. The mobile terminal 100 is configured to be able to receive location information from the beacon device 50. The mobile terminal 100 is configured to be able to receive location information from the RFID tag 60. The mobile terminal 100 is configured to be able to communicate with the device control server 200 via the wireless LAN of the access point 70. In the description of this specification, the symbol "100" is used to collectively indicate multiple mobile terminals, and a symbol with a branch number added to the symbol "100" is used to individually indicate a specific mobile terminal among the multiple mobile terminals (for example, 100-1, 100-2). Details of the mobile terminal 100 will be described later.

[0026] The device control server 200 is a computer that processes information between the mobile terminal 100 and the equipment control device 300. The device control server 200 functions as a device control device that cooperates with the equipment control device 300 to control multiple devices 20. The device control server 200 is communicably connected to multiple access points 70 and the equipment control device 300 via a computer network (e.g., at least one of a wired LAN, a wireless LAN, and the Internet). In the example of FIG. 1, the number of device control servers 200 is one, but in other embodiments, the number may be multiple depending on the processing load. Details of the device control server 200 will be described later.

[0027] The equipment control device 300 is a computer that controls equipment installed in the facility 800. The equipment control device 300 is connected to each of the multiple devices 20 so as to be electronically controllable. The equipment control device 300 is connected to each of the multiple human presence sensors 80 so as to be able to receive sensor signals. In this embodiment, the equipment control device 300 is a device that complies with KNX (registered trademark).

[0028] 2 is an explanatory diagram showing a detailed configuration of the mobile terminal 100. The mobile terminal 100 includes a processor 110, a memory 120, a touch panel display 130, a wireless module 152, a wireless module 154, and a wireless module 156.

[0029] The processor 110 of the mobile terminal 100 controls the touch panel display 130 and the wireless modules 152, 154, and 156 by executing a plurality of program instructions included in the program 122 stored in the memory 120. The number of the processors 110 may be one or more.

[0030] The memory 120 of the mobile terminal 100 stores data to be handled by the processor 110. The number of memories 120 may be one or more. The memory 120 stores a program 122 that describes program instructions to be executed by the processor 110. The program 122 can be installed via a network connected to the mobile terminal 100.

[0031] The wireless module 152 of the mobile terminal 100 is configured to be able to communicate with the device control server 200 via a wireless LAN established by the access point 70. The wireless module 152 is a wireless circuit that is connectable to the access point 70 and complies with the wireless LAN standard.

[0032] The wireless module 154 of the mobile terminal 100 is configured to be able to communicate with the beacon device 50 via wireless communication. The wireless module 154 is a wireless circuit that complies with BLE, which is one of the short-range wireless communication standards that allows communication with the beacon device 50.

[0033] The wireless module 156 of the mobile terminal 100 is configured to be able to communicate via wireless communication with the RFID tag 60. The wireless module 156 is a wireless circuit that complies with NFC, which is one of the short-range wireless communication standards that allows communication with the RFID tag 60.

[0034] The touch panel display 130 of the mobile terminal 100 is an electronic component configured to be capable of displaying images and receiving operational inputs on the screen. The touch panel display 130 is capable of displaying a plurality of Graphical User Interfaces 170 (GUI) for operating each of the plurality of devices 20. In the description of this specification, the reference numeral "170" is used to collectively indicate a plurality of GUIs, and a reference numeral with a subnumber added to the reference numeral "170" is used to individually indicate a specific GUI among the plurality of GUIs (for example, 170-1, 170-2, 170-3).

[0035] The mobile terminal 100 receives an operation input for operating the device 20 via the GUI 170 displayed on the touch panel display 130. After that, the mobile terminal 100 uses the wireless module 152 to request the device 200 to control the device 20 based on the operation input received via the GUI 170.

[0036] The mobile terminal 100 receives location information from at least one location information transmission device among the multiple beacon devices 50 and the multiple RFID tags 60, using the wireless modules 154, 156. After receiving the location information, the mobile terminal 100 identifies the location of the mobile terminal 100 within the facility 800 based on the location information. Thereafter, the mobile terminal 100 limits the GUI 170 displayed on the touch panel display 130 so as to be operable by the operator of the mobile terminal 100 to the GUI 170 for operating the device 20 associated with the location of the mobile terminal 100.

[0037] The mobile terminal 100 acquires, from the device control server 200, operation status information indicating the operation status of the device 20 that can be operated by the GUI 170 displayed on the touch panel display 130, using the wireless module 152. The mobile terminal 100 notifies the operation status of the device 20 by the GUI 170 displayed on the touch panel display 130, based on the operation status information acquired from the device control server 200.

[0038] 3 is an explanatory diagram showing an example of the GUI 170 displayed on the touch panel display 130. The example of FIG. 3 is the touch panel display 130 of the mobile terminal 100 that has received location information from the beacon device 50-1 located at the location 810-1 in FIG. 1. The devices 20 associated with the location 810-1 are the three devices 20-1a, 20-1b, and 20-1c installed at the location 810-1. The GUI 170 displayed on the touch panel display 130 in FIG. 3 is limited to GUIs 170-1, 170-2, and 170-3 for operating the three devices 20-1a, 20-1b, and 20-1c associated with the location 810-1 indicated by the location information of the beacon device 50-1 as the location of the mobile terminal 100.

[0039] The GUI 170-1 is a user interface for operating the device 20-1a which is a lighting device. The GUI 170-2 is a user interface for operating the device 20-1b which is a lighting device. Each of the GUIs 170-1 and 170-2 for the lighting devices includes a location display field 171, a power icon 172, a dimming icon 173, and a color adjustment icon 174. The location display field 171 displays information indicating the location where the device 20 to be operated is located.

[0040] The power icon 172 indicates the operating state of the target device 20, whether the device is powered on or off, and accepts an operation input to power on or off the target device 20. In the example of Fig. 3, the power icon 172 of GUI 170-1 indicates that the device is powered off, and the power icon 172 of GUI 170-2 indicates that the device is powered on.

[0041] The dimming icon 173 indicates the degree of brightness of the light set in the target device 20, which is a lighting device, as an operating state, and accepts an operation input to adjust the brightness of the light. In the example of Fig. 3, the dimming icon 173 of GUI 170-1 indicates the third brightness level out of four brightness levels, and the dimming icon 173 of GUI 170-2 indicates the fourth brightness level out of four brightness levels.

[0042] The color adjustment icon 174 indicates the color of light set in the target device 20, which is a lighting device, as an operating state, and accepts an operation input to adjust the color of the light. In the example of Fig. 3, the color adjustment icon 174 of GUI 170-1 indicates the second level of color out of five levels of color, and the color adjustment icon 174 of GUI 170-2 indicates the second level of color out of five levels of color.

[0043] The GUI 170-3 is a user interface for operating the device 20-1c, which is an air conditioner. The GUI 170-3 for the air conditioner includes a location display field 176 and an air volume adjustment icon 177. The location display field 176 displays information indicating the location where the device 20 to be operated is located. The air volume adjustment icon 177 indicates the air volume of the device 20 to be operated, which is an air conditioner, as an operating state, and accepts an operation input for adjusting the air volume. In the example of FIG. 3, the air volume adjustment icon 177 of the GUI 170-3 indicates the "medium" level of air volume among four air volumes: "off", "low", "medium" and "high".

[0044] 4 is an explanatory diagram showing a detailed configuration of the device control server 200. The device control server 200 includes a processor 210, a memory 220, and a network module 250.

[0045] The processor 210 of the device control server 200 controls the network module 250 by executing a plurality of program instructions included in a program 222 stored in the memory 220. The number of the processors 210 may be one or more.

[0046] The memory 220 of the device control server 200 stores data handled by the processor 210. The number of memories 220 may be one or more. The memory 220 stores a program 222 and device layout data 224. The program 222 is data describing program instructions to be executed by the processor 210. The device layout data 224 is data associating each of the multiple devices 20 with each location 810 in the facility 800 indicated by location information transmitted from the multiple beacon devices 50 and the multiple RFID tags 60. The device layout data 224 is stored in the memory 220 when the program 222 is installed, and is updated as appropriate by the administrator of the device management system 10.

[0047] The network module 250 of the device control server 200 is an electronic circuit that processes communication via a wired LAN. Using the network module 250, the device control server 200 is configured to be able to communicate with the mobile terminal 100 via the access point 70, and is also configured to be able to communicate with the facility control device 300.

[0048] The device control server 200 receives a control request for the device 20 from the mobile terminal 100 using the network module 250. The device control server 200 instructs the equipment control device 300 to control the device 20 based on the control request from the mobile terminal 100.

[0049] The device control server 200 acquires operation status information indicating the operation status of the device 20 from the equipment control device 300 using the network module 250. The device control server 200 transmits the operation status information acquired from the equipment control device 300 to the mobile terminal 100.

[0050] Fig. 5 is a flowchart showing GUI display processing executed by the mobile terminal 100. The GUI display processing in Fig. 5 is processing for displaying a GUI 170 on the touch panel display 130. When the processor 110 executes a program command of the program 122, the mobile terminal 100 periodically executes the GUI display processing in Fig. 5 at a predetermined timing.

[0051] After starting the GUI display process of FIG. 5, the mobile terminal 100 determines whether or not it has received location information from at least one of the location information transmission devices of the multiple beacon devices 50 and the multiple RFID tags 60 (step S112).

[0052] When the mobile terminal 100 receives location information from at least one location information transmission device (step S112: "YES"), the mobile terminal 100 identifies the location of the mobile terminal 100 (its own location) within the facility 800 based on the location information (step S114). When the mobile terminal 100 receives a plurality of pieces of location information from a plurality of beacon devices 50, the mobile terminal 100 identifies the location of the mobile terminal 100 by taking into consideration at least one of the received signal strength and the received radio wave phase angle when each piece of location information is received. When the mobile terminal 100 receives the location information of the beacon device 50 and the location information of the RFID tag 60, the mobile terminal 100 identifies the location of the mobile terminal 100 by taking into consideration each piece of location information.

[0053] After identifying the position of the mobile terminal 100 (step S114), the mobile terminal 100 inquires of the device control server 200 using the wireless module 152, thereby identifying the device 20 associated with the position of the mobile terminal 100 identified based on the position information (step S116). In response to the inquiry from the mobile terminal 100, the device control server 200 notifies the mobile terminal 100 of the device 20 associated with the position of the mobile terminal 100. This enables the mobile terminal 100 to identify the device 20 associated with the position of the mobile terminal 100.

[0054] After identifying the device 20 associated with the location of the mobile terminal 100 (step S116), the mobile terminal 100 limits the GUI 170 displayed on the touch panel display 130 to the GUI 170 for operating the device 20 identified based on the query to the device control server 200 (step S117).

[0055] If location information has not been received from the location information transmission device (step S112: "NO"), mobile terminal 100 determines whether or not GUI 170 is being displayed on touch panel display 130 (step S118). If GUI 170 is not being displayed (step S118: "NO"), mobile terminal 100 ends the GUI display process of Fig. 5. If GUI 170 is being displayed (step S118: "YES"), mobile terminal 100 maintains GUI 170 being displayed on touch panel display 130 (step S119).

[0056] After limiting or maintaining the GUI 170 on the touch panel display 130 (steps S117, S119), the mobile terminal 100 uses the wireless module 152 to inquire of the device control server 200 about the operation status of the device 20 that can be operated using the GUI 170 being displayed on the touch panel display 130 (step S122). After that, the mobile terminal 100 uses the wireless module 152 to obtain operation status information indicating the operation status of the device 20 that can be operated using the GUI 170 being displayed from the device control server 200 (step S126).

[0057] After acquiring the operation status information of the device 20 from the device control server 200 (step S126), the mobile terminal 100 notifies the operation status of the device 20 by the GUI 170 being displayed on the touch panel display 130 based on the operation status information (step S128). As described with reference to Fig. 3, the mobile terminal 100 is configured to be able to notify the operation status of the device 20 by using the power icon 172, the dimming icon 173, the color adjustment icon 174, and the airflow adjustment icon 177 of the GUI 170. After notifying the operation status of the device 20 by the GUI 170 (step S128), the mobile terminal 100 ends the GUI display process of Fig. 5.

[0058] Fig. 6 is a flowchart showing the GUI display process executed by the device control server 200. The GUI display process in Fig. 6 is a process for displaying the GUI 170 on the touch panel display 130 of the mobile terminal 100. The processor 210 executes a program command of the program 222, causing the device control server 200 to periodically execute the GUI display process in Fig. 6 at a predetermined timing.

[0059] After starting the GUI display process of Fig. 6, the device control server 200 judges whether or not an inquiry has been received from the mobile terminal 100 about the device 20 associated with the position of the mobile terminal 100 (step S214). If an inquiry has been received from the mobile terminal 100 (step S214: "YES"), the device control server 200 identifies the device 20 associated with the location 810 in the facility 800 indicated by the location of the mobile terminal 100 by collating the device location data 224 stored in the memory 220 with the location of the mobile terminal 100 notified from the mobile terminal 100 (step S215). In the example of Fig. 1, when the location of the mobile terminal 100 is the location 810-1 identified by the location information transmitted from the beacon device 50-1, the device control server 200 identifies the devices 20-1a, 20-1b, and 20-1c as the devices 20 associated with the location of the mobile terminal 100. When the location of the mobile terminal 100 is the location 810-1a identified by the location information transmitted from the RFID tag 60-1a, the device control server 200 identifies the devices 20-1a and 20-1c as the devices 20 associated with the location of the mobile terminal 100.

[0060] After identifying the device 20 associated with the location of the mobile terminal 100 (step S215), the device control server 200 notifies the mobile terminal 100 of the device 20 associated with the location of the mobile terminal 100 using the network module 250 (step S216).

[0061] If no inquiry has been received from the mobile terminal 100 (step S214: “NO”), or after notifying the mobile terminal 100 of the device 20 associated with the location of the mobile terminal 100 (step S216), the device control server 200 determines whether or not an inquiry about the operating status of the device 20 has been received from the mobile terminal 100 (step S222).

[0062] When an inquiry about the operation status of the device 20 is received (step S222: "YES"), the device control server 200 uses the network module 250 to confirm the operation status of the device 20 for which the inquiry about the operation status has been received from the equipment control device 300 (step S224). After confirming the operation status of the device 20 with the equipment control device 300 (step s224), the device control server 200 uses the network module 250 to transmit operation status information indicating the operation status of the device 20 confirmed with the equipment control device 300 to the mobile terminal 100 (step S226). In another embodiment, when the equipment control device 300 notifies the device control server 200 of the operation status of the device 20 based on a predetermined condition, the device control server 200 may hold operation status information of a plurality of devices 20 based on the notification from the equipment control device 300, and transmit the operation status information held in the device control server 200 to the mobile terminal 100 in response to an inquiry from the mobile terminal 100. After transmitting the operation status information to the mobile terminal 100 (step S226), the device control server 200 ends the GUI display process of FIG.

[0063] Fig. 7 is a flowchart showing a GUI reception process executed by the mobile terminal 100. The GUI reception process in Fig. 7 is a process for receiving an operation input of the device 20 by the GUI 170 of the touch panel display 130. The processor 110 executes a program command of the program 122, whereby the mobile terminal 100 periodically executes the GUI reception process in Fig. 7 at a predetermined timing.

[0064] After starting the GUI reception process of Fig. 7, the mobile terminal 100 determines whether or not an operation input for the device 20 has been received by the GUI 170 being displayed on the touch panel display 130 (step S132). As described with reference to Fig. 3, the mobile terminal 100 is configured to be able to receive an operation input for the device 20 by using the power icon 172, the dimming icon 173, the color adjustment icon 174, and the airflow adjustment icon 177 of the GUI 170.

[0065] When an operation input for the device 20 is accepted by the GUI 170 (step S132: "YES"), the mobile terminal 100 uses the wireless module 152 to request the device control server 200 to control the device 20 for which the operation input has been accepted (step S133).

[0066] After requesting the device control server 200 to control the device 20 (step S133), the mobile terminal 100 receives a response to the request from the device control server 200 using the wireless module 152 (step S136). The response from the device control server 200 includes information indicating the control result of the device 20 based on the operation input, and information indicating the operating status of the device 20.

[0067] After receiving a response from the device control server 200 (step S136), the mobile terminal 100 reflects the control result of the device 20 based on the operation input in the GUI 170 of the touch panel display 130 based on the information included in the response (step S138). After the control result is reflected in the GUI 170 (step S138), or if the GUI 170 has not accepted an operation input for the device 20 (step S132: "NO"), the mobile terminal 100 ends the GUI acceptance process of FIG.

[0068] Fig. 8 is a flowchart showing the GUI reception process executed by the device control server 200. The GUI reception process in Fig. 8 is a process for realizing reception of an operation input of the device 20 in the GUI 170 of the mobile terminal 100. The processor 210 executes a program command of the program 222, whereby the device control server 200 periodically executes the GUI reception process in Fig. 8 at a predetermined timing.

[0069] 8, the device control server 200 judges whether or not a control request for the device 20 has been received from the mobile terminal 100 (step S233). If a control request for the device 20 has been received from the mobile terminal 100 (step S233: "YES"), the device control server 200 instructs the equipment control device 300 to control the device 20 using the network module 250 based on the control request received from the mobile terminal 100 (step S224).

[0070] After instructing the equipment control device 300 to control the device 20 (step S224), the equipment control server 200 receives a response to the instruction from the equipment control device 300 using the network module 250 (step S225). The response from the equipment control device 300 includes information indicating the control result of the device 20 based on the operation input, and information indicating the operating status of the device 20.

[0071] After receiving a response from the equipment control device 300 (step S225), the device control server 200 uses the network module 250 to transmit a response to the control request received from the mobile terminal 100 to the mobile terminal 100 (step S226). The response from the device control server 200 includes information indicating the control result of the device 20 based on the operation input, and information indicating the operation status of the device 20. After responding to the mobile terminal 100 (step S226), the device control server 200 ends the GUI reception process of FIG.

[0072] Fig. 9 is a flowchart showing GUI deletion processing executed by mobile terminal 100. The GUI deletion processing in Fig. 9 is processing for deleting GUI 170 being displayed on touch panel display 130. When program instructions of program 122 are executed by processor 110, mobile terminal 100 periodically executes the GUI deletion processing in Fig. 9 at a predetermined timing.

[0073] 9, the mobile terminal 100 determines whether or not the GUI 170 is being displayed on the touch panel display 130 (step S141). If the GUI 170 is not being displayed (step S141: "NO"), the mobile terminal 100 ends the GUI deletion process of FIG.

[0074] If the GUI 170 is being displayed (step S141: "YES"), the mobile terminal 100 judges whether or not the location information from the beacon device 50 and the RFID tag 60 has not been received for a predetermined period (e.g., 5 minutes) (step S142). If the location information has not been received for the predetermined period (step S142: "YES"), all GUIs 170 being displayed on the touch panel display 130 are deleted (step S143). After deleting the displayed GUIs 170 (step S143), the mobile terminal 100 ends the GUI deletion process of FIG. 9.

[0075] If the mobile terminal 100 has received the location information within the predetermined period (step S142: "NO"), the mobile terminal 100 judges whether or not a deletion instruction to delete the GUI 170 from the touch panel display 130 has been received from the device control server 200 (step S146). If a deletion instruction to delete the GUI 170 has been received from the device control server 200 (step S146: "YES"), the mobile terminal 100 deletes the displayed GUI 170 that is the target of the deletion instruction received from the device control server 200 from the touch panel display 130 (step S147). After deleting the GUI 170 based on the deletion instruction (step S147), or if there is no deletion instruction from the device control server 200 (step S146: "NO"), the mobile terminal 100 ends the GUI deletion process of FIG. 9.

[0076] Fig. 10 is a flowchart showing GUI deletion processing executed by the device control server 200. The GUI deletion processing in Fig. 10 is processing for deleting the GUI 170 being displayed on the touch panel display 130 of the mobile terminal 100. When the processor 210 executes a program command of the program 222, the device control server 200 periodically executes the GUI deletion processing in Fig. 10 at a predetermined timing.

[0077] 10 starts, the device control server 200 determines whether or not a GUI deletion condition for deleting the GUI 170 being displayed on the touch panel display 130 of the mobile terminal 100 is satisfied (step S245). The GUI deletion condition is that the device 20 that is the target of operation of the GUI 170 is a device 20 that is placed in a place 810 where the human presence sensor 80 has not output a sensor signal indicating the presence of a person for a predetermined period of time (e.g., 15 minutes). The GUI deletion condition may also be that a predetermined period of time (e.g., 3 hours) has passed since the GUI 170 was displayed.

[0078] If the GUI deletion condition is met (step S245: "YES"), the device control server 200 uses the network module 250 to transmit a deletion instruction to the mobile terminal 100 to delete the GUI 170 that satisfies the GUI deletion condition from the touch panel display 130 (step S246). After transmitting the deletion instruction (step S246), or if the GUI deletion condition is not met (step S245: "NO"), the device control server 200 ends the GUI deletion process of FIG.

[0079] According to the first embodiment described above, the GUI 170 displayed on the touch panel display 130 is limited to the GUI 170 for operating the device 20 associated with the position of the mobile terminal 100 within the facility 800, thereby improving the operability of the GUI 170. Also, it is possible to prevent the mobile terminal 100 from erroneously operating a device 20 located in a place 810 that is unrelated to the current location of the mobile terminal 100.

[0080] Furthermore, since the operational status of the device 20 being operated can be notified by the GUI 170 displayed on the touch panel display 130, the operator of the mobile terminal 100 can operate the device 20 while checking the operational status using the GUI 170.

[0081] Furthermore, the mobile terminal 100 limits the GUI 170 displayed on the touch panel display 130 to the GUI 170 for operating the device 20 identified based on the inquiry to the device control server 200. This allows the mobile terminal 100 to set the device 20 to be operated by the GUI 170 based on the determination of the device control server 200. Furthermore, the processing load on the mobile terminal 100 can be reduced compared to when the device 20 to be operated by the GUI 170 is set without interacting with the device control server 200.

[0082] 9 and 10, it is possible to delete GUI 170 that is determined by device control server 200 to be inappropriate for display on touch panel display 130. Also, by steps S142 and S143 in the GUI deletion process of FIG. 9, it is possible to delete GUI 170 from touch panel display 130 when there is a possibility that mobile terminal 100 is not present within facility 800.

[0083] B. Second embodiment The device management system 10 of the second embodiment is similar to that of the first embodiment, except that the mobile terminal 100 identifies the device 20 to be operated by the GUI 170 based on device layout data 124 stored in the memory 120 of the mobile terminal 100. The device control server 200 of the second embodiment does not execute the process (steps S214, S215, S216) for identifying the device 20 to be displayed by the GUI 170 in the GUI display process of FIG.

[0084] 11 is an explanatory diagram showing a detailed configuration of a mobile terminal 100B in the second embodiment. The mobile terminal 100B is similar to the mobile terminal 100 in the first embodiment, except that the memory 120 stores device layout data 124.

[0085] The equipment layout data 124 is data that associates each of the multiple equipment 20 with each location 810 in the facility 800 indicated by the location information transmitted from the multiple beacon devices 50 and the multiple RFID tags 60. In this embodiment, the mobile terminal 100B acquires the equipment layout data 124 from the equipment control server 200 using the wireless module 152, and stores the equipment layout data 124 in the memory 120. In other embodiments, the equipment layout data 124 may be data that is stored in the memory 120 in advance by being stored in the memory 120 together with the installation of the program 122.

[0086] Fig. 12 is a flowchart showing the GUI display process executed by the mobile terminal 100B in the second embodiment. The GUI display process in Fig. 12 is similar to the GUI display process in Fig. 5, except that steps S116B and S117B are executed instead of steps S116 and S117 in the GUI display process in Fig. 5.

[0087] After identifying the location of the mobile terminal 100 (step S114), the mobile terminal 100B identifies the device 20 associated with the location of the mobile terminal 100B identified based on the location information by comparing the location of the mobile terminal 100B with the device location data 124 stored in the memory 120 (step S116B).

[0088] After identifying the device 20 based on the device layout data 124 (step S116B), the mobile terminal 100B limits the GUI 170 displayed on the touch panel display 130 to the GUI 170 for operating the device 20 identified based on the device layout data 124 (step S117B). Then, the mobile terminal 100 executes step 122.

[0089] According to the second embodiment described above, as in the first embodiment, the GUI 170 displayed on the touch panel display 130 is limited to the GUI 170 for operating the device 20 associated with the position of the mobile terminal 100B within the facility 800, thereby improving the operability of the GUI 170. Also, it is possible to prevent the mobile terminal 100B from erroneously operating the device 20 located in a place 810 that is unrelated to the current location of the mobile terminal 100B.

[0090] Furthermore, the mobile terminal 100B limits the GUI 170 displayed on the touch panel display 130 to the GUI 170 for operating the device 20 identified based on the device layout data 124 stored in the memory 120. This makes it possible to set the device 20 to be operated by the GUI 170 based on the device layout data 124 stored in the memory 120. Furthermore, the processing load on the device control server 200 can be reduced compared to when the device 20 to be operated by the GUI 170 is set through communication with the device control server 200.

[0091] C. Other Embodiments The technology disclosed in this specification is not limited to the above-mentioned embodiment, example, and modification, and can be realized in various configurations without departing from the spirit thereof. For example, among the technical features in the above-mentioned embodiment, example, and modification, those corresponding to the technical features in each form described in the Summary of the Invention column can be appropriately replaced and combined in order to solve some or all of the above-mentioned problems or to achieve some or all of the above-mentioned effects. In addition, technical features that are not described as essential in this specification can be appropriately deleted.

[0092] The device 20 associated with the position of the mobile terminal 100 that is the target of operation of the GUI 170 is not limited to the device 20 located at the position of the mobile terminal 100, but may include a device 20 located in the vicinity of the position of the mobile terminal 100, or a device 20 located in a location related to the position of the mobile terminal 100. [Explanation of symbols]

[0093] 10. Equipment management system 20…Equipment 50…Beacon device 60…RFID tag 70…Access point 80...Human sensor 100,100B…Mobile device 110…Processor 120…Memory 122…Program 124...Equipment layout data 130…Touch panel display 152...Wireless module 154...Wireless module 156…Wireless module 170...Graphical User Interface (GUI) 171...Location display column 172…Power icon 173…Dimming icon 174…Tone icon 176...Location display column 177…Airflow adjustment icon 200: Device control server 210…Processor 220…Memory 222…Program 224...Equipment layout data 250…Network module 300...Facility control device 800…Facilities 810…Location

Claims

1. A mobile terminal configured to be able to operate a plurality of devices arranged within a facility, a first wireless circuit configured to be communicable via wireless communication with a device control device that controls the plurality of devices, a second wireless circuit configured to be communicable via wireless communication with a plurality of RFID tags that transmit position information indicating locations within the facility, a touch panel display, a processor, a memory that stores program instructions and, when the program instructions are executed by the processor, a plurality of graphical user interfaces for operating each of the plurality of devices can be displayed on the touch panel display, an operation input for operating the device is received via the graphical user interface displayed on the touch panel display, using the first wireless circuit, a control of the device based on the operation input received via the graphical user interface is requested to the device control device, using the second wireless circuit, the position information is received from at least one of the plurality of RFID tags, by querying the device control device using the first wireless circuit, a device associated with the position of the mobile terminal specified based on the position information is specified, The graphical user interface displayed on the touch panel display is limited to a graphical user interface for operating the device specified based on the query to the device control device among the plurality of graphical user interfaces. A mobile terminal.

2. The mobile terminal according to claim 1, wherein when the program instructions are executed by the processor, using the first wireless circuit, operation status information indicating the operation status of a device operable by the graphical user interface displayed on the touch panel display is obtained from the device control device, Based on the operation status information received from the device control device, the operation status is notified by the graphical user interface displayed on the touch panel display. A mobile terminal.

3. The mobile terminal according to claim 1 or claim 2, wherein the plurality of devices includes at least one of a lighting device, an air conditioning device, an electric shade, floor heating, an audio device, a video device, an electric door, and an electric lock.

4. A program for causing a computer of a mobile terminal to realize a function of operating a plurality of devices arranged in a facility, a function of being able to display a plurality of graphical user interfaces for operating each of the plurality of devices on a touch panel display of the mobile terminal, a function of receiving an operation input for operating the device via the graphical user interface displayed on the touch panel display, a function of using a first wireless circuit of the mobile terminal configured to be communicable with a device control device that controls a plurality of devices via wireless communication to request the device control device to control the device based on the operation input received via the graphical user interface, a function of receiving the position information from at least one of the plurality of RFID tags using a second wireless circuit of the mobile terminal configured to be communicable with the plurality of RFID tags that transmit the position information indicating a location in the facility via wireless communication, a function of identifying a device associated with the position of the mobile terminal specified based on the position information by inquiring the device control device using the first wireless circuit, a function of limiting the graphical user interface displayed on the touch panel display to a graphical user interface for operating a device specified based on an inquiry to the device control device among the plurality of graphical user interfaces A program for realizing the above.

5. A device management system for managing a plurality of devices arranged in a facility, a mobile terminal configured to be able to operate the plurality of devices, a device control device for controlling the plurality of devices, a plurality of RFID tags that transmit position information indicating a location in the facility and comprising: The mobile terminal includes a first wireless circuit configured to be communicable with the device control device via wireless communication, a second wireless circuit configured to be communicable with the plurality of RFID tags via wireless communication, a touch panel display, a processor, and a memory for storing program instructions comprising, by executing the program instructions by the processor, a plurality of graphical user interfaces for operating each of the plurality of devices can be displayed on the touch panel display, receive an operation input for operating the device via the graphical user interface displayed on the touch panel display, using the first wireless circuit, request the device control device to control the device based on the operation input received via the graphical user interface, using the second wireless circuit, receive the position information from at least one RFID tag among the plurality of RFID tags, by querying the device control device using the first wireless circuit, identify the device associated with the position of the mobile terminal specified based on the position information, a device management system that limits the graphical user interface displayed on the touch panel display to a graphical user interface for operating the device specified based on the query to the device control device among the plurality of graphical user interfaces.

Images