JP2024044957A - Equipment management system, mobile terminal and program - Google Patents

Abstract

[Problem] To improve the operability of a graphical user interface for operating multiple devices arranged within a facility. [Solution] A mobile terminal is capable of displaying multiple graphical user interfaces for operating each of multiple devices arranged within the facility on a touch panel display. The mobile terminal identifies the location of the mobile terminal within the facility based on location information received from a location information transmission device. The mobile terminal limits the graphical user interfaces displayed on the touch panel display to graphical user interfaces for operating devices associated with the location of the mobile terminal identified based on the location information. [Selected Figure] Figure 1

Description

This specification discloses technology relating to device management systems, mobile terminals, and programs.

In recent years, a system has been proposed that allows users to operate multiple devices, such as lighting 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).

JP 2021-108152 A

For facility users, it is often sufficient to be able to operate devices located at their current location within the facility. However, with a graphical user interface that can operate devices in locations unrelated to the current location, the structure becomes complicated depending on the number of operable devices, making operation cumbersome. Furthermore, with such a graphical user interface, there is a risk of accidentally operating a device in a location unrelated to the current location.

The technology disclosed in this specification can be realized as the following form.

(1) One aspect disclosed in this specification is a mobile terminal configured to be capable of operating a plurality of devices arranged within a facility, the mobile terminal including 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 a location 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 interface 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 interface; 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 current location of the mobile terminal.

(2) The mobile terminal of the above-described embodiment may use the first wireless circuit to acquire, by the processor executing the program instructions, operation status information indicating the operation status of a device that can be operated using the graphical user interface displayed on the touch panel display from the device control device; and may notify the operation status using the graphical user interface displayed on the touch panel display based on the operation status information received from the device control device. With this embodiment of the mobile terminal, the operator of the mobile terminal can operate the device while checking the operation status using the graphical user interface.

(3) The mobile terminal of the above-mentioned form is identified based on the location information by inquiring the device control device using the first wireless circuit by executing the program instruction by the processor. specifying a device associated with the location of the mobile terminal; changing 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; may be limited to. According to this type of mobile terminal, it is possible to set the device to be operated by the graphical user interface based on the judgment of the device control device. Furthermore, the processing load on the mobile terminal can be reduced compared to the case where the device to be operated by the graphical user interface is set without interacting with the device control device.

(4) In the mobile terminal of the above-mentioned form, each of the plurality of devices is associated with each location in the facility using the first wireless circuit by executing the program instruction by the processor. acquires equipment location data from the equipment control device; stores the equipment location data acquired from the equipment control device in the memory; and acquires the location information based on the equipment location data stored in the memory; identifying a device associated with the location of the mobile terminal identified based on; identifying the graphical user interface displayed on the touch panel display from among the plurality of graphical user interfaces based on the device location data; It may be limited to a graphical user interface for operating the device. According to the mobile terminal of this form, it is possible to set the device to be operated by the graphical user interface based on the device location data acquired from the device control device. Furthermore, the processing load on the device control device can be reduced compared to the case where the device to be operated by the graphical user interface is set through interaction with the device control device.

(5) The mobile terminal of the above-mentioned form stores in the memory in advance equipment location data in which each of the plurality of devices is associated with each location in the facility; the device arrangement stored in the memory; identifying a device associated with the location of the mobile terminal identified based on the location information based on the data; selecting the graphical user interface displayed on the touch panel display from among the plurality of graphical user interfaces; The present invention may be limited to a graphical user interface for operating a device specified based on the device location data. According to this type of mobile terminal, it is possible to set the device to be operated on the graphical user interface based on the device placement data stored in advance in the memory. Furthermore, the processing load on the device control device can be reduced compared to the case where the device to be operated by the graphical user interface is set through interaction with the device control device.

(6) The mobile terminal of the above-mentioned embodiment may delete the graphical user interface displayed on the touch panel display based on an instruction from the device control device received using the first wireless circuit by executing the program instructions by the processor. According to the mobile terminal of this embodiment, 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.

(7) The mobile terminal of the above-mentioned form may delete the graphical user interface displayed on the touch panel display 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. According to the mobile terminal of this form, 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 the facility.

(8) In the mobile terminal of the above-described embodiment, the multiple 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 embodiment of the mobile terminal, location information indicating a location within a facility can be easily used via wireless communication.

(9) In the mobile terminal of the above-described embodiment, 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. With this type of mobile terminal, it is possible to improve the operability of equipment that requires adjustment for each location within a facility.

The technology disclosed in this specification can be implemented in various forms different from mobile terminals. The technology disclosed in this specification can be realized in the form of, for example, a device management system, a device control device, a position information transmitting device, a computer program, and the like.

FIG. 1 is an explanatory diagram showing the configuration of a device management system. FIG. 2 is an explanatory diagram showing the detailed configuration of a mobile terminal. FIG. 4 is an explanatory diagram showing an example of a GUI displayed on a touch panel display. FIG. 2 is an explanatory diagram showing a detailed configuration of a device control server. It is a flowchart which shows GUI display processing performed by a mobile terminal. 10 is a flowchart showing a GUI display process executed by the device control server. 11 is a flowchart showing a GUI reception process executed by the mobile terminal. 10 is a flowchart showing a GUI reception process executed by the device control server. 11 is a flowchart showing a GUI deletion process executed by a mobile terminal. 3 is a flowchart showing GUI deletion processing executed by the device control server. FIG. 11 is an explanatory diagram showing a detailed configuration of a mobile terminal according to a second embodiment. It is a flow chart which shows GUI display processing performed by a mobile terminal in a 2nd embodiment.

A. First Embodiment Fig. 1 is an explanatory diagram showing the configuration of a device management system 10. The device management system 10 is a system that manages a plurality of devices 20 arranged in a facility 800. The facility 800 is a relatively large space in which a plurality of 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.

The device management system 10 manages devices 20 arranged in a facility 800 by associating them with locations 810 in the facility 800 in which 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.

Each of the multiple devices 20 is an electronically controllable device arranged in the facility 800. In the description of this specification, the symbol "20" is used to collectively indicate the multiple devices, and a symbol with a subnumber added to the symbol "20" is used to individually indicate a specific device among the multiple devices (for example, 20-1a, 20-1b, 20-1c, etc.). In the example of FIG. 1, device 20-1a is a lighting device arranged in location 810-1a. Device 20-1b is a lighting device arranged in location 810-1b. Device 20-1c is an air conditioning device arranged in location 810-1. Device 20-2a is a lighting device arranged in location 810-2. Device 20-2c is an air conditioning device arranged in location 810-2. The multiple devices 20 may be electronically controllable devices, and may include not only air conditioning devices and lighting devices, but also motorized shades, floor heating, audio equipment, video equipment, motorized doors (gates), electric locks, etc. This improves the operability of the equipment 20 that requires adjustment for each location 810 within the facility 800.

The equipment 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, an equipment control server 200, and an equipment control device 300. The equipment management system 10 is configured to enable users of a facility 800 to operate a plurality of equipment 20 arranged within the facility 800 using the mobile terminals 100.

Each of the multiple beacon devices 50 is a location information transmission device that is arranged in the 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). In the example of FIG. 1, beacon device 50-1 is located at location 810-1. Beacon device 50-2 is located at location 810-2.

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 own 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). In the example of FIG. 1, RFID tag 60-1a is located at location 810-1a. RFID tag 60-1b is located at location 810-1b. RFID tag 60-2 is located at location 810-2.

Each of the multiple access points 70 is arranged in the facility 800 and is 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 subnumber 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).

Each of the plurality of human sensors 80 is a sensor that is placed within the facility 800 and detects people within the facility 800. In the equipment management system 10, each of the plurality of human sensors 80 is managed in association with at least one of the plurality of locations 810 within the facility 800.

Each of the plurality of 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 plurality of mobile terminals 100 may be any portable information device, and may include not only smartphones but also tablet terminals, personal computers, and the like. The mobile terminal 100 is configured to be able to operate a plurality of devices 20 arranged within the facility 800. Mobile terminal 100 is configured to be able to receive location information from beacon device 50. Mobile terminal 100 is configured to be able to receive location information from 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 code "100" is used to comprehensively indicate a plurality of mobile terminals, and the code "100" is used to indicate a specific mobile terminal among the plurality of mobile terminals individually. Use numbered codes (eg, 100-1, 100-2). Details of the mobile terminal 100 will be described later.

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 controls the plurality of devices 20 in cooperation with the facility control device 300. The device control server 200 is communicably connected to a plurality of access points 70 and the facility control device 300 via a computer network (for example, 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.

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 plurality of devices 20 so as to be electronically controllable. The equipment control device 300 is connected to each of the plurality of human sensors 80 so as to be able to receive sensor signals. In this embodiment, the equipment control device 300 is a device compliant with KNX (registered trademark).

Figure 2 is an explanatory diagram showing the 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.

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 contained in the program 122 stored in the memory 120. The number of processors 110 may be one or more.

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.

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 complies with the wireless LAN standard and can be connected to the access point 70.

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 is compliant with BLE, which is one of the short-range wireless communication standards, and can communicate with the beacon device 50.

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

The touch panel display 130 of the mobile terminal 100 is an electronic component that is configured to be able to display images and receive operational input on the screen. The touch panel display 130 is capable of displaying multiple graphical user interfaces 170 (GUIs) for operating each of the multiple devices 20. In the description of this specification, the reference number "170" is used to collectively refer to multiple GUIs, and a reference number with a subnumber added to the reference number "170" is used to individually refer to a specific GUI among the multiple GUIs (e.g., 170-1, 170-2, 170-3).

Mobile terminal 100 receives operation input for operating device 20 via GUI 170 displayed on touch panel display 130 . Thereafter, 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.

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. The mobile terminal 100 then 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 equipment 20 associated with the location of the mobile terminal 100.

The mobile terminal 100 uses the wireless module 152 to acquire operating status information indicating the operating status of the device 20 that can be operated using the GUI 170 displayed on the touch panel display 130 from the device control server 200. The mobile terminal 100 reports the operating status of the device 20 using the GUI 170 displayed on the touch panel display 130 based on the operating status information acquired from the device control server 200.

Figure 3 is an explanatory diagram showing an example of a GUI 170 displayed on the touch panel display 130. The example in Figure 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 Figure 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 Figure 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.

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 lighting equipment includes a location display field 171, a power icon 172, a dimming icon 173, and a color adjusting icon 174. The location display column 171 displays information indicating the location where the device 20 to be operated is located.

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

The dimming icon 173 indicates the degree of brightness of light set in the device 20 to be operated, which is a lighting device, as an operating state, and also accepts an operation input for adjusting the brightness of the light. In the example of FIG. 3, the dimming icon 173 of the GUI 170-1 indicates the third brightness level among the four levels of brightness, and the dimming icon 173 of the GUI 170-2 indicates the third level of brightness among the four levels of brightness. The fourth level of brightness is shown.

The color adjustment icon 174 indicates the operating state of the light color set in the target device 20, which is a lighting device, and accepts 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, and the color adjustment icon 174 of GUI 170-2 indicates the second level of color out of five levels.

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 operating target device 20, 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 air volume at the "medium" level among the four air volume levels "off", "low", "medium", and "high".

Figure 4 is an explanatory diagram showing the 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.

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

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, respectively. 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.

The network module 250 of the device control server 200 is an electronic circuit that processes communications 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.

The device control server 200 uses the network module 250 to receive a request to control the device 20 from the mobile terminal 100. The device control server 200 instructs the equipment control device 300 to control the device 20 based on a control request from the mobile terminal 100.

The device control server 200 uses the network module 250 to obtain operation status information indicating the operation status of the device 20 from the equipment control device 300. The device control server 200 transmits the operation status information obtained from the equipment control device 300 to the mobile terminal 100.

Figure 5 is a flowchart showing the GUI display process executed by the mobile terminal 100. The GUI display process in Figure 5 is a process for displaying the GUI 170 on the touch panel display 130. The processor 110 executes the program instructions of the program 122, causing the mobile terminal 100 to periodically execute the GUI display process in Figure 5 at a predetermined timing.

After starting the GUI display process in FIG. 5, the mobile terminal 100 determines whether position information has been received from at least one position information transmitting device of the plurality of beacon devices 50 and the plurality of RFID tags 60 (step S112). ).

When location information is received 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 multiple pieces of location information from multiple beacon devices 50, it identifies the location of the mobile terminal 100 by taking into account 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, it identifies the location of the mobile terminal 100 by taking into account each piece of location information.

After identifying the position of the mobile terminal 100 (step S114), the mobile terminal 100 queries the device control server 200 using the wireless module 152 to identify the device 20 associated with the position of the mobile terminal 100 identified based on the position information (step S116). In response to the query 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 allows the mobile terminal 100 to identify the device 20 associated with the position of the mobile terminal 100.

After identifying the device 20 associated with the location of the mobile terminal 100 (step S116), the mobile terminal 100 uses the GUI 170 displayed on the touch panel display 130 to identify the device 20 identified based on the inquiry to the device control server 200. It is limited to the GUI 170 for operation (step S117).

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

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 with 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 with the GUI 170 being displayed from the device control server 200 (step S126).

After acquiring the operating status information of the device 20 from the device control server 200 (step S126), the mobile terminal 100 reports the operating status of the device 20 using the GUI 170 displayed on the touch panel display 130 based on the operating status information. (Step S128). As described using FIG. 3, the mobile terminal 100 is configured to be able to notify the operating status of the device 20 using the power icon 172, dimming icon 173, color adjustment icon 174, and air volume adjustment icon 177 of the GUI 170. ing. After notifying the operating status of the device 20 through the GUI 170 (step S128), the mobile terminal 100 ends the GUI display process of FIG. 5.

FIG. 6 is a flowchart showing the GUI display processing 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. By executing the program instructions of the program 222 by the processor 210, the device control server 200 periodically executes the GUI display process of FIG. 6 at a predetermined timing.

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 location 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 comparing the device location data 224 stored in the memory 220 with the location of the mobile terminal 100 notified by 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. If the location of the mobile terminal 100 is location 810-1a, which is identified by the location information transmitted from the RFID tag 60-1a, the device control server 200 identifies devices 20-1a and 20-1c as devices 20 associated with the location of the mobile terminal 100.

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).

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 , it is determined whether an inquiry about the operating status of the device 20 has been received from the mobile terminal 100 (step S222).

When receiving an inquiry about the operation status of the device 20 (step S222: "YES"), the device control server 200 uses the network module 250 to check the operation status of the device 20 for which the operation status inquiry was made. Check with the equipment control device 300 (step S224). After confirming the operation status of the equipment 20 with the equipment control device 300 (step s224), the equipment control server 200 uses the network module 250 to transmit operation status information indicating the confirmed operation status of the equipment 20 to the equipment control device 300. The information is transmitted to the mobile terminal 100 (step S226). In another embodiment, when the equipment control device 300 notifies the equipment control server 200 of the operating status of the equipment 20 based on a predetermined condition, the equipment control server 200 controls the operation status of the equipment 20 based on the notification from the equipment control device 300. The operating status information held in the device control server 200 may be transmitted to the mobile terminal 100 in response to an inquiry from the mobile terminal 100. After transmitting the operating status information to the mobile terminal 100 (step S226), the device control server 200 ends the GUI display process of FIG. 6.

Figure 7 is a flowchart showing the GUI reception process executed by the mobile terminal 100. The GUI reception process in Figure 7 is a process for receiving operation input of the device 20 by the GUI 170 of the touch panel display 130. The processor 110 executes the program instructions of the program 122, causing the mobile terminal 100 to periodically execute the GUI reception process in Figure 7 at a predetermined timing.

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, dimming icon 173, color adjustment icon 174, and airflow adjustment icon 177 of the GUI 170.

When the GUI 170 accepts an operation input for the device 20 (step S132: "YES"), the mobile terminal 100 uses the wireless module 152 to request the device control server 200 to control the device 20 that received the operation input ( Step S133).

After requesting the device control server 200 to control the device 20 (step S133), the mobile terminal 100 uses the wireless module 152 to receive a response to the request from the device control server 200 (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.

After receiving the 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 on the GUI 170 of the touch panel display 130 based on the information included in the response (step S136). S138). After reflecting the control results on the GUI 170 (step S138), or when the GUI 170 does not accept operation input to the device 20 (step S132: "NO"), the mobile terminal 100 ends the GUI reception process of FIG. .

Figure 8 is a flowchart showing the GUI reception process executed by the device control server 200. The GUI reception process in Figure 8 is a process for realizing reception of operation input of the device 20 in the GUI 170 of the mobile terminal 100. When the processor 210 executes the program instructions of the program 222, the device control server 200 periodically executes the GUI reception process in Figure 8 at a predetermined timing.

After starting the GUI reception process in FIG. 8, the device control server 200 determines whether a request to control the device 20 has been received from the mobile terminal 100 (step S233). When a control request for the device 20 is received from the mobile terminal 100 (step S233: “YES”), the device control server 200 uses the network module 250 to control the device 20 based on the control request received from the mobile terminal 100. Control is instructed to the equipment control device 300 (step S224).

After instructing the equipment control device 300 to control the equipment 20 (step S224), the equipment control server 200 uses the network module 250 to receive a response to the instruction from the equipment control device 300 (step S225). The response from the equipment control device 300 includes information indicating the control result of the equipment 20 based on the operation input, as well as information indicating the operating status of the equipment 20.

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, as well as information indicating the operating 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. 8.

FIG. 9 is a flowchart showing the GUI deletion process executed by the mobile terminal 100. The GUI deletion process in FIG. 9 is a process for deleting the GUI 170 currently displayed on the touch panel display 130. By executing the program instructions of the program 122 by the processor 110, the mobile terminal 100 periodically executes the GUI deletion process of FIG. 9 at a predetermined timing.

After starting the GUI deletion process in FIG. 9, the mobile terminal 100 determines whether 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. 9.

If GUI 170 is being displayed (step S141: "YES"), the mobile terminal 100 determines whether or not location information has been received from the beacon device 50 and the RFID tag 60 for a predetermined period (e.g., 5 minutes) (step S142). If 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.

If the location information has been received for a predetermined period (step S142: "NO"), the mobile terminal 100 determines whether 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 the instruction to delete the GUI 170 is received from the device control server 200 (step S146: “YES”), the mobile terminal 100 deletes the displayed GUI 170, which 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. .

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

After starting the GUI deletion process of FIG. 10, 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 met (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 location 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 display of the GUI 170.

If the GUI deletion condition is satisfied (step S245: "YES"), the device control server 200 uses the network module 250 to send 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 conditions are not satisfied (step S245: "NO"), the device control server 200 ends the GUI deletion process in FIG.

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 location of the mobile terminal 100 within the facility 800, thereby improving the operability of the GUI 170. In addition, 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.

Furthermore, since the GUI 170 displayed on the touch panel display 130 can notify the operating status of the device 20 to be operated, the operator of the mobile terminal 100 can operate the device 20 while checking the operating status using the GUI 170.

The mobile terminal 100 also limits the GUI 170 displayed on the touch panel display 130 to the GUI 170 for operating the device 20 identified based on an 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 judgment 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.

Further, by the GUI deletion processing shown in FIGS. 9 and 10, it is possible to delete the GUI 170 that has been determined by the device control server 200 to be inappropriate for display on the touch panel display 130. Further, by steps S142 and S143 in the GUI deletion process in FIG. 9, the GUI 170 can be deleted from the touch panel display 130 when there is a possibility that the mobile terminal 100 does not exist in the facility 800.

B. Second embodiment The device management system 10 of the second embodiment is similar to the first embodiment, except that the mobile terminal 100 identifies the device 20 to be operated by the GUI 170 based on the 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 on the GUI 170 in the GUI display process of FIG.

Figure 11 is an explanatory diagram showing a detailed configuration of the 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.

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 pre-stored in the memory 120 by being stored in the memory 120 in conjunction with the installation of the program 122.

FIG. 12 is a flowchart showing GUI display processing 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 117B are executed instead of steps S116 and S117 in the GUI display process in FIG.

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).

After specifying the device 20 based on the device placement data 124 (step S116B), the mobile terminal 100B uses the GUI 170 displayed on the touch panel display 130 to operate the device 20 specified based on the device placement data 124. It is limited to the GUI 170 (step S117B). Thereafter, the mobile terminal 100 executes step 122.

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. In addition, it is possible to prevent the mobile terminal 100B from erroneously operating a device 20 located in a place 810 that is unrelated to the current location of the mobile terminal 100B.

The mobile terminal 100B also 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 allows the device 20 to be set as the target device for operation of 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 the target device for operation of the GUI 170 is set through communication with the device control server 200.

C. Other Embodiments The technology disclosed in this specification is not limited to the embodiments, examples, and modifications described above, and can be realized in various configurations without departing from the spirit thereof. For example, among the technical features of the embodiments, examples, and modifications described above, those corresponding to the technical features of each form described in the summary column solve part or all of the above problems. or to achieve some or all of the above-mentioned effects, they can be replaced and combined as appropriate. Furthermore, technical features that are not described as essential in this specification can be deleted as appropriate.

The device 20 associated with the location of the mobile terminal 100 that is the target of operation of the GUI 170 is not limited to the device 20 provided at the location of the mobile terminal 100, but may include a device 20 provided near the location of the mobile terminal 100, or may include a device 20 provided at a location related to the location of the mobile terminal 100.

10... Equipment management system 20... Equipment 50... Beacon device 60... RFID tag 70... Access point 80... Human sensor 100,100B... Mobile terminal 110... Processor 120... Memory 122... Program 124... Equipment placement data 130... Touch panel display 152 ...Wireless module 154...Wireless module 156...Wireless module 170...Graphical user interface (GUI)
171...Location display field 172...Power icon 173...Dimmer icon 174...Toning color icon 176...Location display field 177...Air volume adjustment icon 200...Equipment control server 210...Processor 220...Memory 222...Program 224...Equipment placement data 250... Network module 300... Equipment control device 800... Facility 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 able to communicate via wireless communication with a device control device that controls the plurality of devices;
a second wireless circuit configured to be able to communicate via wireless communication with a plurality of location information transmission devices that transmit location information indicating a location within the facility;
A touch panel display,
A processor;
and a memory for storing program instructions, the program instructions being executed by the processor to
A plurality of graphical user interfaces for operating each of the plurality of devices can be displayed on the touch panel display;
receiving an operation input for operating the device via the graphical user interface displayed on the touch panel display;
using the first wireless circuit, to request the device control device to control the device based on the operation input received via the graphical user interface;
receiving the location information from at least one location information transmission device among the plurality of location information transmission devices using the second wireless circuit;
Identifying a location of the mobile terminal within the facility based on the location information received from the location information transmission device;
A mobile terminal that limits the graphical user interface displayed on the touch panel display to a graphical user interface among the multiple graphical user interfaces for operating an equipment associated with the position of the mobile terminal identified based on the position information.

Images