Remote management system, remote management device, remote management method and program

Abstract

To provide a remote management system, device, method and program for setting a time in which a device is regarded as abnormal, in accordance with an environment in which the device is installed.SOLUTION: In a remote management system 1 including an IoT device and a remote management server which manages abnormality detection time information of the IoT device, the server comprises: a reception section for receiving input of installation place information for installing the device and management target information to be managed by the device; an operation UI section which is functioned as a determination section for determining abnormality detection time information for regarding the device as abnormal in accordance with the installation place information and the management target information which are received by the reception section; an error period setting data storage section which is an information storage section for storing the abnormality detection time information that is determined by the determination section; and a device communication section for transmitting the abnormality detection time information to the device. The device comprises a reception section for receiving the abnormality detection time information from the remote management server and a storage section for storing the received abnormality detection time information.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a remote management system, a remote management device, a remote management method, and a program. [Background technology]

[0002] Conventionally, a technology has been known that detects device abnormalities by arbitrarily setting the time period for which the device is considered to be abnormal, and notifying the user of the device abnormality if the time period since data was not received from the device exceeds the set time period for considering the device to be abnormal.

[0003] Patent Document 1 discloses a technique that enables a device administrator to set an arbitrary value for the time period during which a device is considered to be abnormal. Summary of the Invention [Problem to be solved by the invention]

[0004] Incidentally, the appropriate time for a device to be considered abnormal varies depending on where the device is installed and what it manages. For example, an abnormality in a temperature sensor (device) in a freezer can affect food and perishable items, so abnormality detection is required within a short period of time, such as 30 minutes. On the other hand, an abnormality in a temperature sensor (device) in an office does not have an immediate impact, so abnormality detection within a period of several hours to several days is not a problem.

[0005] However, it has been difficult for a device administrator to set the time period during which a device is considered to be abnormal, depending on the location where the device is installed and the target that the device manages.

[0006] The present invention has been made in view of the above, and has an object to set a time period during which a device is considered to be abnormal depending on the location where the device is installed and the object managed by the device. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the present invention provides a remote management system comprising a device and a remote management device that manages abnormality detection time information of the device, wherein the remote management device comprises: a reception unit that receives input of installation location information where the device is installed and management target information managed by the device; a determination unit that determines abnormality detection time information at which the device is considered to be abnormal based on the installation location information and the management target information received by the reception unit; an information storage unit that stores the abnormality detection time information determined by the determination unit; and a transmission unit that transmits the abnormality detection time information to the device, and the device comprises: a reception unit that receives the abnormality detection time information from the remote management device; and a storage unit that stores the received abnormality detection time information. [Effects of the Invention]

[0008] According to the present invention, it is possible to set the time period during which a device is considered to be abnormal, depending on the location where the device is installed and the object that the device manages. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an example of a remote management system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of a remote management system. [Figure 4] FIG. 4 shows screen transitions of the basic screen for setting the abnormality detection time. [Figure 5] FIG. 5 is a sequence diagram showing the flow of a process for setting an abnormality detection time. [Figure 6] FIG. 6 is a diagram illustrating an example of the management table. [Figure 7] FIG. 7 illustrates an example of a configuration of a remote management system according to the second embodiment. [Figure 8]FIG. 8 is a sequence diagram showing the flow of a process for setting an abnormality detection time. [Figure 9] FIG. 9 is a diagram illustrating an example of a recommendation. [Figure 10] FIG. 10 illustrates an example of a configuration of a remote management system according to the third embodiment. [Figure 11] FIG. 11 is a flowchart showing the flow of processing in the analysis unit and the display reception unit. [Figure 12] FIG. 12 is a diagram showing an example of a display screen. DETAILED DESCRIPTION OF THE INVENTION

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of a remote management system, a remote management device, a remote management method, and a program will be described in detail with reference to the accompanying drawings.

[0011] (First embodiment) FIG. 1 illustrates an example of a remote management system 1 according to a first embodiment. The remote management system 1 illustrated in FIG. 1 uses a remote management server 3 on the cloud to centrally and remotely manage multiple IoT devices 53, such as sensors and cameras, provided in an IoT gateway device 50 located in a remote location. Specifically, the remote management system 1 acquires data from each of the multiple IoT devices 53 and transmits it to the remote management server 3. If data from one of the multiple IoT devices 53 does not arrive at the remote management server 3 for a predetermined period of time, the remote management server 3 manages the IoT device 53 by regarding the IoT device 53 as abnormal. An abnormality occurs when the target device behaves differently from normal operation or when a value of a measurement target falls outside the normal range. For example, the IoT device 53 may be a temperature sensor installed in a freezer or a surveillance camera installed in a warehouse.

[0012] The remote management system 1 includes a remote management server 3, which is a remote management device, an IoT gateway device 50, and a user terminal 90. The IoT gateway device 50 is connected to the management system 3 via a communication network 5. The communication network 5 is constructed using the Internet, a mobile communication network, etc. The communication network 5 may include not only wired communication, but also mobile communication networks such as 3G (3rd Generation), 4G (4th Generation), 5G (5th Generation), or LTE (Long Term Evolution), and wireless communication networks such as Wi-Fi (Wireless Fidelity (registered trademark)) or WiMAX (Worldwide Interoperability for Microwave Access). The communication network 5 may also include a network constructed using blockchain.

[0013] The IoT gateway device 50 is a device to be managed that is a target of remote management in the remote management system 1.

[0014] The IoT gateway device 50 is a device to be managed by the remote management server 3 for maintenance or counter meter reading. The IoT gateway device 50 includes an MFP (Multi-Function Peripheral), a PJ (Projector), an IWB (Interactive Whiteboard: a whiteboard with an electronic blackboard function capable of intercommunication), a PC (Personal Computer), and a sensor device (e.g., an electronic balance, barometer, accelerometer, ammeter, thermometer, photometer, human sensor, camera, and illuminance meter, which are capable of communicating with the outside world). The IoT gateway device 50 is not limited to the above, and may be, for example, industrial machinery such as a processing device, an inspection device, a conveyance device, or a picking device; medical equipment such as an ophthalmoscope, an X-ray inspection device, a blood pressure monitor, a body fat scale, an optometry device, or a pacemaker; a 3D printer; or an imaging device. The IoT gateway device 50 may also be a vending machine, a power supply, an air conditioning system, a metering system for gas, water, electricity, or the like; or an autonomous robot. Furthermore, the IoT gateway device 50 may be a device with a communication function attached to a terminal that does not have a communication function, such as a human presence sensor.

[0015] The remote management server 3 is a system for managing the IoT gateway device 50. The remote management server 3 is, for example, a server computer that provides a remote management service for remotely managing the IoT gateway device 50. As an example of management, the remote management server 3 monitors the status of the IoT gateway device 50 in real time, or periodically acquires maintenance information (such as part usage status or alarm information) of the IoT gateway device 50.

[0016] The remote management server 3 may be constructed by a single computer, or may be constructed by a plurality of computers to which the parts (functions or means) of each device are divided and arbitrarily assigned.

[0017] The user terminal 90 is a terminal such as a laptop PC used by a client who is a device administrator who monitors the IoT gateway devices 50 using the remote management server 3. The user terminal 90 provides the client with information about the IoT gateway devices 50 that are under management by displaying the device information about the IoT gateway devices 50 managed by the remote management server 3 using a web browser or the like. Furthermore, multiple user terminals 90 can each access the remote management server 3 from different locations.

[0018] The remote management server 3 can set the content of the applications to be provided according to, for example, the usage environment of the IoT gateway device 50, the type of IoT gateway device 50, or the contract details of the client, and manages the applications to be provided for each user terminal 90.

[0019] The user terminal 90 is not limited to a notebook PC, but may be, for example, a tablet terminal, a smartphone, a wearable terminal, or a desktop PC.

[0020] Next, the hardware configuration of each device (remote management server 3, IoT gateway device 50, user terminal 90, etc.) according to the embodiment will be described. Each device (remote management server 3, IoT gateway device 50, user terminal 90, etc.) constituting the remote management system 1 has a general computer configuration. Here, an example of the hardware configuration of a general computer will be described.

[0021] 2 is a diagram showing an example of the hardware configuration of a computer. Note that the hardware configuration of the computer shown in FIG. 2 may have the same configuration in each embodiment, and components may be added or deleted as necessary. The computer includes a CPU (Central Processing Unit) 101, a ROM (Read Only Memory) 102, a RAM (Random Access Memory) 103, a HD (Hard Disk) 104, an HDD (Hard Disk Drive) controller 105, a display 106, an external device connection I / F (Interface) 108, a communication I / F 109, a bus line 110, a keyboard 111, a pointing device 112, a DVD-RW (Digital Versatile Disc Rewritable) drive 114, and a media I / F 116.

[0022] Of these, the CPU 101 controls the operation of the entire computer. The ROM 102 stores programs used to drive the CPU 101, such as the IPL. The RAM 103 is used as a work area for the CPU 101. The HD 104 stores various data, such as programs. The HDD controller 105 controls the reading and writing of various data from and to the HD 104 under the control of the CPU 101. The display 106 displays various information, such as a cursor, menus, windows, characters, or images. The display 106 is an example of a display unit. The display 106 may be a touch panel display equipped with input means. The external device connection I / F 108 is an interface for connecting various external devices. The communication I / F 109 is an interface for transmitting and receiving data to and from other computers or electronic devices. The communication I / F 109 is, for example, a communication interface such as a wired or wireless LAN. The communication I / F 109 may also include a communication interface for mobile communication such as 3G, 4G, 5G, or LTE, Wi-Fi, WiMAX, etc. The bus line 110 is an address bus or a data bus for electrically connecting the components such as the CPU 101 shown in FIG.

[0023] The keyboard 111 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 112 is a type of input means for selecting or executing various instructions, selecting a processing target, moving a cursor, etc. The input means may be not only the keyboard 111 and the pointing device 112, but also a touch panel, a voice input device, etc. The DVD-RW drive 114 controls reading and writing of various data from a DVD-RW 113, which is an example of a removable recording medium. The removable recording medium is not limited to a DVD-RW, but may also be a DVD-R or a Blu-ray (registered trademark) Disc, etc. The media I / F 116 controls reading and writing (storing) of data from a recording medium 115, such as a flash memory.

[0024] Note that components may be added or deleted from the hardware configuration of each device according to the embodiment as needed. For example, the IoT gateway device 50 may be configured without an input means such as the keyboard 111 and the display 106. The IoT gateway device 50 may also be configured with modules for providing functions or services according to the type of each device.

[0025] Furthermore, each of the above programs may be recorded as an installable or executable file on a computer-readable recording medium and distributed. Examples of recording media include CD-Rs (Compact Disc Recordables), DVDs (Digital Versatile Disks), Blu-ray Discs, SD cards, and USB (Universal Serial Bus) memories. Furthermore, the recording media may be provided domestically or internationally as a program product. For example, the remote management server 3 executes the program according to the present invention to realize the remote management method according to the present invention.

[0026] Next, the configuration of the remote management system 1 will be described.

[0027] FIG. 3 is a diagram showing an example of the configuration of the remote management system 1. As shown in FIG.

[0028] The IoT gateway device 50 includes a plug-in 51, an IoT gateway application 52, and an IoT device 53. The IoT gateway device 50 notifies the remote management server 3 of data acquired from the IoT device 53 and any abnormalities in the IoT device 53.

[0029] The plug-in 51 receives data from each IoT device 53, converts it into an appropriate format, and notifies the IoT gateway application 52.

[0030] The IoT gateway application 52 notifies the remote management server 3 of the various data received from the plug-in 51. The IoT gateway application 52 includes a device log storage unit 521, a device registration information storage unit 522, and a cloud communication unit 523.

[0031] The device log storage unit 521 stores the device log, which is a log of the operation status of the IoT gateway application 52 and the plug-in 51.

[0032] The device registration information storage unit 522 stores the device registration information of the IoT device 53. The device registration information includes information on whether the device is registered in the user environment. The information on whether the device is registered in the user environment is used to notify data only to the IoT device 53 registered in the user environment. More specifically, the device registration information storage unit 522 is a storage unit that stores received anomaly detection time information.

[0033] The cloud communication unit 523 is a module that communicates with the remote management server 3. More specifically, the cloud communication unit 523 is a receiving unit that receives abnormality detection time information from the remote management server 3.

[0034] The IoT devices 53 are devices used by users, such as various sensors and cameras, etc. The installation locations of the IoT devices 53 vary depending on the type of business of the user.

[0035] The remote management server 3 includes an operation UI (User Interface) unit 31 that functions as a decision unit, an authentication unit 32, a device communication unit 33, a device data storage unit 34, a device status management unit 35, a log file storage unit 36, and an error period setting data storage unit 37.

[0036] The operation UI unit 31 provides an operation UI operated by the user. The operation UI unit 31 can register or cancel the IoT device 53 and set an error period via the operation UI. More specifically, the operation UI unit 31 functions as a reception unit that receives input of installation location information where the IoT device 53 is installed and management target information managed by the IoT device 53. The operation UI unit 31 also functions as a determination unit that determines abnormality detection time information at which the IoT device 53 is considered to be abnormal, based on the installation location information and management target information. The installation location information is information about the location where the target device is installed. Examples include a "freezer" and a "clean room." The management target information is information indicating the target to be managed by the target device. Examples include "perishable food" and "processed food." The abnormality detection time information is recommended setting information that indicates the time until the target device is considered to be abnormal. For example, "30 minutes" is a recommended value for the elapsed time after temperature data is no longer received from the target device.

[0037] The authentication unit 32 provides a login function for the remote management server 3 and the like.

[0038] The device communication unit 33 communicates with the IoT device 53. More specifically, the device communication unit 33 is a transmission unit that transmits the anomaly detection time information to the IoT device 53.

[0039] The device data storage unit 34 is a database that stores device data, which is data of the IoT device 53 sent from the IoT gateway device 50.

[0040] The device state management unit 35 manages the device state. More specifically, the device state management unit 35 manages the device registration status and various statuses (such as the type of business, installation location, and information on the managed objects) of the IoT devices 53 and the IoT gateway devices 50.

[0041] The log file storage unit 36 ​​is a database that stores log files sent from the IoT gateway application 52. More specifically, the log file storage unit 36 ​​stores the log file of the IoT device 53 that is automatically uploaded when the abnormality continues beyond the error period. This allows the system provider to quickly analyze the problem using the log and reduce user downtime.

[0042] The error period setting data storage unit 37 is a database (information storage unit) that stores and accumulates error period setting data. The error period setting data is information that indicates the error period of each IoT device 53. The error period setting data is data that indicates the time until the target device is considered to be abnormal. One example is a setting value that is set in the error period setting data storage unit 37 by accepting a selection from the user after the operation UI unit 31 displays a recommended value. Furthermore, the error period setting data storage unit 37 has a function (determination unit) that determines the abnormality detection time information associated with the installation location information and the management target information by checking the management table T1 in response to a request for abnormality detection time information from the operation UI unit 31.

[0043] Each functional unit of the remote management system 1 shown in FIG. 3 may be realized by CPU 101 executing a program stored in ROM 102 and HD 104, i.e., by software, or by hardware such as an IC (Integrated Circuit), or by a combination of software and hardware.

[0044] Next, the abnormality detection time setting in the remote management server 3 will be described.

[0045] Fig. 4 is a diagram showing screen transitions of the basic screen for setting the anomaly detection time. As shown in Fig. 4, when a user accesses the operation UI provided by the operation UI unit 31 of the remote management server 3 via the user terminal 90 and performs an authentication operation via the authentication screen P1 provided by the authentication unit 32, the operation UI unit 31 displays a list screen P2 of IoT gateway devices registered in the user's environment.

[0046] Next, when the user performs an operation to select a desired IoT gateway device from the IoT gateway device list screen P2, the operation UI unit 31 displays an IoT device list screen P3 of the selected IoT gateway device.

[0047] Next, when the user selects the IoT device 53 for which they want to set the abnormality detection time from the IoT device list screen P3, the operation UI unit 31 displays the abnormality detection time setting screen (top) P4, where the user can choose whether to set the abnormality detection time for the selected IoT device 53 as a "recommended setting" or a "manual setting."

[0048] If the user selects "Manual Setting" on the anomaly detection time setting screen (top) P4, the operation UI unit 31 displays a screen P5 for setting the anomaly detection time for the selected IoT, and reflects the setting according to the user's instructions.

[0049] When the user selects "recommended settings" on the anomaly detection time setting screen (top) P4, the operation UI unit 31 displays a screen P6 for selecting an industry type of business. When the user selects an industry type of business on the screen P6 for selecting an industry type of business, the operation UI unit 31 transitions to the next individual setting screen P7. When the user selects the installation location and management target of each IoT device 53 on the individual setting screen P7, the operation UI unit 31 sets recommended values ​​based on the installation location and management target of each IoT device 53 and reflects the settings according to the user's instructions.

[0050] When the setting of the abnormality detection time for the IoT device 53 is completed as described above, the operation UI unit 31 of the remote management server 3 updates the error time setting data stored in the error period setting data storage unit 37 and notifies the IoT gateway device 50 connected to the IoT device 53 of the setting value.

[0051] The operation UI unit 31 also provides a UI that allows the error period to be set by time period or day of the week, so that it is possible to set a day of the week when no abnormality detection is to be performed.

[0052] Furthermore, the operation UI unit 31 can also reflect the setting values ​​of the setting UI by having the system provider update the setting values ​​of the business type, installation location, and the like.

[0053] Furthermore, the operation UI unit 31 can also reflect the setting values ​​of the setting UI by updating the setting items themselves by the system provider.

[0054] Next, the flow of the process of setting the abnormality detection time as described above will be explained.

[0055] Fig. 5 is a sequence diagram showing the flow of the process of setting the anomaly detection time. Note that the process shown in Fig. 5 is premised on the fact that the user is logged in with administrator privileges of the customer tenant of the cloud service when operating the operation UI provided by the operation UI unit 31.

[0056] 5, in steps S1 to S4, the operation UI unit 31 prompts the user to select an IoT device 53 for which anomaly detection settings are to be made. Specifically, in step S1, the operation UI unit 31 requests the device data storage unit 34 to acquire list information of the IoT devices 53. In step S2, the device data storage unit 34 transmits the list information of the IoT devices 53 to the operation UI unit 31. In step S3, the operation UI unit 31 displays the list information of the IoT devices 53 received from the device data storage unit 34 on the display screen. In step S4, the operation UI unit 31 accepts, from the user, the selection of an IoT device 53 for which anomaly detection settings are to be made.

[0057] Next, in steps S5 and S6, the operation UI unit 31 acquires information on the business type, installation location, and managed objects from the device status management unit 35, and displays the anomaly detection time setting screen (top) P4 in step S7. Specifically, in step S5, the operation UI unit 31 requests the device status management unit 35 to acquire information on the business type, installation location, and managed objects. In step S6, the device status management unit 35 transmits the information on the business type, installation location, and managed objects to the operation UI unit 31. In step S7, the operation UI unit 31 displays the anomaly detection time setting screen (top) P4.

[0058] In step S8, the user selects whether to set the anomaly detection time of the IoT device 53 to the "recommended setting" or to the "manual setting." If the user selects to set the anomaly detection time of the IoT device 53 to the "manual setting" in step S8, the user himself inputs an arbitrary time. When the operation UI unit 31 receives the selection of "manual setting" from the user, it reflects the setting by updating the error period setting data (setting information) stored in the error period setting data storage unit 37 using the arbitrary time information input by the user. After the setting is reflected, the operation UI unit 31 performs the processing from step S19 onwards.

[0059] If the user selects to set the anomaly detection time of the IoT device 53 to the "recommended setting" in step S8, the operation UI unit 31 accepts settings of information related to the business type and the installation location of the IoT device 53 in steps S10 to S12. Specifically, in step S8, the operation UI unit 31 accepts the selection of the "recommended setting" from the user. In step S9, the operation UI unit 31 displays a screen P6 for selecting the business type. In step S10, the operation UI unit 31 accepts the selection of the business type from the user. In step S11, the operation UI unit 31 displays the next individual setting screen P7. In step S12, the operation UI unit 31 accepts the selection of the installation location and management target for each device from the user.

[0060] Next, in steps S13 to S16, the operation UI unit 31 acquires and displays abnormality detection time information under the relevant conditions based on the information input up to step S12. Specifically, in step S13, the operation UI unit 31 requests the error period setting data storage unit 37 to acquire the abnormality detection time information stored in the error period setting data storage unit 37.

[0061] Here, Fig. 6 is a diagram showing an example of the management table T1. As shown in Fig. 6, abnormality detection time information is stored in the management table T1 in the error period setting data storage unit 37. As an example, when the installation location information for device A (temperature sensor) is "freezer" and the management object information is "perishable food," "30 minutes" is set as the abnormality detection time information (setting value) for the time when device A is considered to be abnormal. This "30 minutes" indicates that an abnormality is considered to have occurred when 30 minutes have passed since temperature data was not received from device A.

[0062] In step S13, the error period setting data storage unit 37 transmits the abnormality detection time information in the management table T1 to the operation UI unit 31. In response to a request for abnormality detection time information from the operation UI unit 31, the error period setting data storage unit 37 checks the management table T1 to determine the abnormality detection time information associated with the installation location information and the management target information. As an example, the error period setting data storage unit 37 receives information from the operation UI unit 31 regarding device A (temperature sensor), where the installation location information is "freezer" and the management target information is "perishable food." The error period setting data storage unit 37 determines "30 minutes" as the abnormality detection time information associated with the information regarding device A (temperature sensor), where the installation location information is "freezer" and the management target information is "perishable food."

[0063] In step S14, the operation UI unit 31 receives the abnormality detection time information. In step S15, the operation UI unit 31 updates the screen information on the display screen with the received abnormality detection time information for the setting value corresponding to the installation location and management target selected by the user. In step S16, the operation UI unit 31 displays the updated screen information. In this case, if the user inputs the installation location information as "freezer" and the management target information as "perishable food," "30 minutes" is displayed on the screen as the setting value corresponding to "freezer" and "perishable food."

[0064] Then, in step S17, the operation UI unit 31 updates the settings as they are, or the user rewrites the setting values ​​and updates them. Specifically, in step S17, the operation UI unit 31 accepts a selection from the user of the "Reflect Settings" button or the "Cancel" button. When the operation UI unit 31 accepts the selection of the "Reflect Settings" button, it proceeds to the processing of step S18.

[0065] In the following step S18, the operation UI unit 31 updates the error time setting data (setting information) stored in the error period setting data storage unit 37. Specifically, the operation UI unit 31 stores the abnormality detection time information, acquired in step S14, at which the device is considered to be abnormal, in the error period setting data storage unit 37 as error period setting data of the device.

[0066] Furthermore, in steps S19 and S20, the operation UI unit 31 updates the device status of the device status management unit 35 and notifies the IoT gateway device 50 of the abnormality detection time of each IoT device 53. Specifically, in step S19, the operation UI unit 31 updates the setting information of the device status management unit 35. In step S20, the device status management unit 35 transmits the updated setting information to the IoT gateway device 50. The IoT gateway device 50 receives the updated setting information and updates the setting information of the IoT gateway device 50. The IoT gateway device 50 stores the abnormality notification time information (e.g., "30 minutes") determined by the error period setting data storage unit 37 in a storage unit within the device 53 in the IoT gateway device 50. Note that the storage destination is not limited to a storage unit within the device 53, and may be a storage unit within the IoT gateway device 50.

[0067] As described above, according to this embodiment, the time period for which a device is considered to be abnormal can be set according to the location where the device is installed and the object that the device manages. Specifically, based on the environmental information about the surroundings where the device is installed, for example, if the ambient temperature is high, the time period for detecting an error period can be shortened, and if the ambient temperature is low, the time period for detecting an error period can be lengthened, thereby preventing false detection.

[0068] That is, according to this embodiment, when the appropriate setting time differs depending on the user's industry or the location where the device is installed, as described below, the user can appropriately understand and set the time for detecting abnormalities in each device. Industry: Manufacturing, manufacturing (food), medical, transportation, construction, distribution, retail, etc. Location: Refrigerators, cold rooms, freezers, freezer rooms, room temperature warehouses, factories, clean rooms, etc. Target: Perishable foods, processed foods, machinery, equipment parts, frozen foods, etc. Time: During business hours, including holidays

[0069] (Second embodiment) Next, a second embodiment will be described.

[0070] The second embodiment differs from the first embodiment in that it accumulates and analyzes error periods set by the user and proposes them to other users. In the following explanation of the second embodiment, explanations of the same parts as in the first embodiment will be omitted, and only the parts that differ from the first embodiment will be explained.

[0071] 7 is a diagram showing an example of the configuration of the remote management system 1 according to the second embodiment. As shown in Fig. 7, the remote management server 3 of this embodiment includes an error period analysis unit 41 in addition to the configuration shown in Fig. 3.

[0072] The error period analysis unit 41 analyzes the error period setting data accumulated in the remote management server 3. When the recommended setting values ​​for a specific business type or installation location are updated, the error period analysis unit 41 makes a recommendation to a user who owns the corresponding IoT device 53.

[0073] Next, the flow of the process for setting the abnormality detection time will be described.

[0074] 8 is a sequence diagram showing the flow of the process of setting the abnormality detection time. Note that a description of the same processes as those shown in FIG. 5 will be omitted.

[0075] As shown in FIG. 8, in steps S21 to S23, the error period analysis unit 41 acquires the error period setting data (setting value) stored in the error period setting data storage unit 37, and calculates the optimal recommended setting value from the acquired error period setting data (setting value).

[0076] Furthermore, in step S24, the error period analysis unit 41 updates the error period setting data stored in the error period setting data storage unit 37 with the optimal recommended setting value.

[0077] Next, in steps S25 to S28, the error period analysis unit 41 acquires user information from the authentication unit 32, creates an email message from the acquired information (attributes of the setting values ​​and user information), and creates and sends a recommendation to the user who owns the corresponding IoT device 53.

[0078] FIG. 9 is a diagram showing an example of a recommendation R. As shown in FIG. 9, the recommendation R includes a recommendation statement R1 indicating that the recommended setting values ​​for a specific business type or installation location have been updated, and a link L to an individual setting screen P7. When the user clicks on the link L of the recommendation R in step S29 and is successfully authenticated, the operation UI unit 31 acquires the optimal recommended setting values ​​for the device used by the user in steps S30 to S31, and transitions to the individual setting screen P7. When the user selects the installation location and management targets of each IoT device 53 on the individual setting screen P7, the operation UI unit 31 sets the optimal recommended setting values ​​based on the installation location and management targets of each IoT device 53, and reflects the settings in accordance with the user's instructions.

[0079] As described above, according to this embodiment, the error period set by the user is accumulated, analyzed, and proposed to other users, so that it is possible to easily set an error period according to the installation environment, which is difficult for users. In other words, by utilizing information when the error period is changed during actual operation, it becomes possible to make optimal proposals. In other words, according to this embodiment, the setting values ​​set by each user are collected and analyzed, and updates to the recommended settings are proposed to the user from the cloud, so that the user can easily update the setting values ​​to optimal values ​​according to the installation environment of the IoT device and the type of business.

[0080] (Third embodiment) Next, a third embodiment will be described.

[0081] The third embodiment differs from the first embodiment in that it analyzes operator feedback regarding the setting results of past anomaly detection time information settings and proposes changes to the parameters of the anomaly detection time information, etc. In the following description of the second embodiment, the same parts as in the first embodiment will be omitted, and only the parts that differ from the first embodiment will be described.

[0082] FIG. 10 is a diagram showing an example of the configuration of the remote management system 1 according to the third embodiment.

[0083] As shown in FIG. 10, the remote management server 3 of this embodiment includes an analysis unit 42 and a display reception unit 43 in addition to the components shown in FIG.

[0084] The remote management server 3 of this embodiment notifies the user of the results of past settings of abnormality detection time information and proposes changing the abnormality detection time information. For example, if the abnormality detection time for perishable items in the freezer is set to 30 minutes in the past settings of abnormality detection time information in this system, the state of the perishable items may not change even if temperature data is not transmitted for 30 minutes. Therefore, to address such cases, the remote management server 3 of this embodiment allows the user to input feedback and proposes changing the abnormality detection time to 60 minutes.

[0085] The analysis unit 42 analyzes the results of setting the anomaly detection time multiple times in the past. Furthermore, the analysis unit 42 analyzes user feedback regarding the results of setting the anomaly detection time multiple times in the past using the learning effect of machine learning, and proposes changes to the parameters of the anomaly detection time information, etc.

[0086] Here, machine learning is a technology that allows a computer to acquire human-like learning capabilities, in which the computer autonomously generates algorithms necessary for judgments such as data classification from learning data that is input in advance, and applies these to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning, or may be a combination of these learning methods; any learning method for machine learning is acceptable.

[0087] The display receiving unit 43 displays the analysis results by the analysis unit 42 on the display 106 which is a display unit, and also receives changes to the setting conditions in the remote management server 3 based on the analysis results by the analysis unit 42.

[0088] FIG. 11 is a flowchart showing the flow of processing in the analysis unit 42 and the display reception unit 43.

[0089] 11, first, the analysis unit 42 checks the number of times the abnormality detection time information has been set (step S51). If the analysis unit 42 determines that the number of times the abnormality detection time information has been set is not 10 or more (No in step S52), the analysis unit 42 returns to step S51.

[0090] On the other hand, if the analysis unit 42 determines that the number of times the abnormality detection time information has been set is 10 or more (Yes in step S52), the display acceptance unit 43 notifies the user by displaying the analysis result by the analysis unit 42 on the display 106 (step S53). For example, if the abnormality detection time information has been set 10 times, the setting results of the abnormality detection time information for the past 10 times may be displayed on the screen, and an input may be accepted from the user as to whether the setting results of the abnormality detection time information are correct (the time desired by the administrator).

[0091] Here, Fig. 12 is a diagram showing an example of the display screen. In the example of the display screen shown in Fig. 12, the setting results X of the anomaly detection time information for the past 10 times are displayed in a list.

[0092] 12, the display receiving unit 43 displays notification content Y to the user on the screen of the display 106. In the example of notification content Y to the user on the display screen shown in FIG. 12, the display receiving unit 43 displays the following message: "The last 10 setting results for the abnormality detection time information will be displayed. Are the setting results for the abnormality detection time information correct (the result intended by the operator)?"

[0093] 12, the display receiving unit 43 displays a "Yes" button B1 and a "No" button B2 on the screen of the display 106, which indicate a response to the notification content Y to the user.

[0094] 11, the display receiving unit 43 determines whether the user has clicked the "No" button B2 on the screen (step S54). If the display receiving unit 43 determines that the user has clicked the "Yes" button B1 on the screen (No in step S54), the setting of the abnormality detection time information in the example display screen shown in Fig. 12 is correct (as intended by the user), and therefore the parameter for changing the abnormality detection time is not changed and the process returns to step S51.

[0095] On the other hand, if the display receiving unit 43 determines that the user has clicked the "No" button B2 on the screen (Yes in step S54), the setting of the abnormality detection time information in the example display screen shown in FIG. 12 is not correct (not as intended by the user), so the display receiving unit 43 changes the parameter for changing the abnormality detection time (step S55) and terminates the processing.

[0096] As a specific example of parameter change in step S55, when the user selects a device for which the anomaly detection time is to be changed from among the devices displayed on the display screen shown in Fig. 12, the display accepting unit 43 displays new anomaly detection time candidates (e.g., 15 minutes, 30 minutes, 60 minutes, 90 minutes, 120 minutes) on the display screen. When the user selects one of the candidates, the analysis unit 42 sets the anomaly detection time candidate whose selection has been accepted as the new anomaly detection time.

[0097] Specifically, if the abnormality detection time for perishable items in the freezer is set to 30 minutes, the condition of the perishable items may not change even if temperature data is not sent for 30 minutes. Therefore, if the user clicks the "No" button B2 on the screen, the abnormality detection time is changed from 30 minutes to 60 minutes, for example. With this configuration, the notification time and frequency can be reduced compared to when the abnormality detection time is 30 minutes, reducing the effort required for the administrator to go to the freezer every 30 minutes.

[0098] Note that the example of changing the anomaly detection time is not limited to this. Alternatively, when the user clicks the "No" button B2 on the screen, the display receiving unit 43 may display the device for which the anomaly detection time is to be changed and the anomaly detection time information on the screen, and have the user directly input the parameters of the target device and the anomaly detection time information to change the time.

[0099] As described above, according to this embodiment, feedback from the operator regarding the setting results of past abnormality detection time information settings can be analyzed, and suggestions can be made to change the parameters of the abnormality detection time information.

[0100] Each function of each of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to perform each function by software, such as a processor implemented by an electronic circuit, as well as devices such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and conventional circuit modules designed to perform each of the above-described functions.

[0101] The remote management server 3 is not limited to a personal computer as long as it is a device equipped with a communication function. The remote management server 3 may be, for example, an image forming device, a PJ (Projector), an IWB (Interactive White Board: a white board with an electronic blackboard function that allows mutual communication), an output device such as digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network home appliance, an automobile (Connected Car), a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, a desktop PC, or the like.

[0102] For example, aspects of the present invention are as follows. <1> A remote management system including a device and a remote management apparatus that manages abnormality detection time information of the device, The remote management device a receiving unit that receives input of information about a location where the device is installed and information about a management target managed by the device; a determination unit that determines abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received by the reception unit; an information storage unit that stores the anomaly detection time information determined by the determination unit; a transmitting unit that transmits the abnormality detection time information to the device; Equipped with The device comprises: a receiving unit that receives the abnormality detection time information from the remote management device; a storage unit that stores the received abnormality detection time information; Equipped with A remote management system characterized by: <2> a device status management unit that manages the installation location information, the management target information, and the abnormality detection time information received by the reception unit; Characterized by <1> The remote management system according to claim 1. <3> The determination unit further determines the anomaly detection time information according to an industry type and business. Characterized by <1> or <2> The remote management system according to claim 1. <4> an error period analysis unit that notifies a user who owns a corresponding device when the installation location information, the management target information, and the abnormality detection time information managed by the device status management unit are updated; Characterized by <2> The remote management system according to claim 1. <5> an analysis unit that analyzes the determination results of the anomaly detection time determined by the determination unit multiple times in the past; a display accepting unit that displays the analysis result by the analyzing unit on a display unit and accepts changes to the setting conditions based on the analysis result; characterized by comprising <1> Or <4> 10. The remote management system according to claim 9, wherein <6> A remote management device for managing abnormality detection time information of a device, a receiving unit that receives input of information about a location where the device is installed and information about a management target managed by the device; a determination unit that determines abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received by the reception unit; an information storage unit that stores the anomaly detection time information determined by the determination unit; a transmitting unit that transmits the abnormality detection time information to the device; A remote management device comprising: <7> A remote management method in a remote management device that manages abnormality detection time information of a device, comprising: a receiving step of receiving input of information on a location where the device is installed and information on a management target managed by the device; a determining step of determining abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received in the receiving step; an information storage step of storing the abnormality detection time information determined by the determination step; a transmitting step of transmitting the abnormality detection time information to the device; A remote management method comprising: <8> A computer that controls a remote management device that manages abnormality detection time information of a device, a receiving unit that receives input of information about a location where the device is installed and information about a management target managed by the device; a determination unit that determines abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received by the reception unit; an information storage unit that stores the anomaly detection time information determined by the determination unit; a transmitting unit that transmits the abnormality detection time information to the device; A program to function as a [Explanation of symbols]

[0103] 1 Remote management system 3 Remote management device 31 Reception and Decision Section 33 Transmitter 35 Device Status Management Unit 37 Information storage section, decision section 41 Error Period Analysis Unit 42 Analysis Department 43 Display Reception Department 53 devices 522 Storage section 523 Receiving Unit [Prior art documents] [Patent documents]

[0104] [Patent Document 1] Japanese Patent Application Laid-Open No. 2001-290383

Claims

1. A remote management system including a device and a remote management apparatus that manages abnormality detection time information of the device, The remote management device a receiving unit that receives input of information about a location where the device is installed and information about a management target managed by the device; a determination unit that determines abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received by the reception unit; an information storage unit that stores the anomaly detection time information determined by the determination unit; a transmitting unit that transmits the abnormality detection time information to the device; Equipped with The device comprises: a receiving unit that receives the abnormality detection time information from the remote management device; a storage unit that stores the received abnormality detection time information; Equipped with A remote management system characterized by:

2. a device status management unit that manages the installation location information, the management target information, and the abnormality detection time information received by the reception unit; The remote management system according to claim 1 .

3. The determination unit further determines the anomaly detection time information according to an industry type and business. The remote management system according to claim 1 .

4. an error period analysis unit that notifies a user who owns a corresponding device when the installation location information, the management target information, and the abnormality detection time information managed by the device status management unit are updated; The remote management system according to claim 2 .

5. an analysis unit that analyzes the determination results of the anomaly detection time determined by the determination unit multiple times in the past; a display accepting unit that displays the analysis result by the analyzing unit on a display unit and accepts changes to the setting conditions based on the analysis result; 5. The remote management system according to claim 1, further comprising:

6. A remote management device for managing abnormality detection time information of a device, a receiving unit that receives input of information about a location where the device is installed and information about a management target managed by the device; a determination unit that determines abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received by the reception unit; an information storage unit that stores the anomaly detection time information determined by the determination unit; a transmitting unit that transmits the abnormality detection time information to the device; A remote management device comprising:

7. A remote management method in a remote management device that manages abnormality detection time information of a device, comprising: a receiving step of receiving input of information on a location where the device is installed and information on a management target managed by the device; a determining step of determining abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received in the receiving step; an information storage step of storing the abnormality detection time information determined by the determination step; a transmitting step of transmitting the abnormality detection time information to the device; A remote management method comprising:

8. A computer that controls a remote management device that manages abnormality detection time information of a device, a receiving unit that receives input of information about a location where the device is installed and information about a management target managed by the device; a determination unit that determines abnormality detection time information for determining whether the device is abnormal, based on the installation location information and the management target information received by the reception unit; an information storage unit that stores the anomaly detection time information determined by the determination unit; a transmitting unit that transmits the abnormality detection time information to the device; A program to function as a

Images