Device management support device, device management support system, device management support method and program

The device management support system addresses the lack of detailed abnormality notifications in remote device management by transmitting specific error messages to user terminals, enhancing user understanding and reducing maintenance inefficiencies.

JP2024158582APending Publication Date: 2024-11-08MITSUBISHI ELECTRIC CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023073897
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-28
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing service support systems fail to quickly inform users about the details of abnormalities in remotely managed devices, necessitating a system that provides clear and timely notification of device issues.

Method used

A device management support system that includes an error notification acquisition unit, an error determination unit, and a message storage unit to identify and transmit relevant error message information to user terminals, ensuring users receive detailed information about device abnormalities.

Benefits of technology

Users can quickly grasp the details of device abnormalities, reducing the need for unnecessary service provider visits and improving maintenance efficiency by receiving precise error information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024158582000001_ABST
    Figure 2024158582000001_ABST
Patent Text Reader

Abstract

To provide a device management support device, a device management support system, a device management support method, and a program for enabling a user to quickly grasp a content of an abnormality when the abnormality occurs in a device.SOLUTION: A cloud server 1 comprises: an error notification acquisition unit 111 for acquiring error notification information sent from a device management server 2; an error determination unit 112 for determining whether or not error code information is error code information that identifies a content of an abnormality that should be notified to a user; and a message notification unit 113 for selecting message information corresponding to the acquired error code information from among message information stored in a message storage unit 132, and transmitting the selected message information to a terminal device 3.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] A service support system has been proposed that includes a management device that remotely manages devices within a local area network and acquires data from the devices, and a data processing device that converts the data acquired by the management device into data corresponding to the content of the service to be provided, stores the data, and transmits the stored data to the data utilization device using a specific API contracted for each data utilization device (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-86456 Summary of the Invention [Problem to be solved by the invention]

[0004] Meanwhile, there is a demand for this type of service support system that, when an abnormality occurs in a remotely managed device, can determine the type of abnormality that has occurred and provide a service that enables the user of the device to quickly become aware of the occurrence of the abnormality along with the details of the abnormality.

[0005] The present disclosure has been made in consideration of the above-mentioned reasons, and aims to provide an equipment management support device, an equipment management support system, an equipment management support method, and a program that enable a user to quickly grasp the content of an abnormality when an abnormality occurs in an equipment. [Means for solving the problem]

[0006] In order to achieve the above object, the device management support device according to the present disclosure comprises: an error notification acquisition unit that acquires error notification information including error code information for identifying the content of the abnormality occurring in the device, the error notification information being transmitted from a device management server that manages the state of the device when an abnormality occurs in the device; an error determination unit that determines whether the error code information included in the acquired error notification information is error code information that identifies the content of an abnormality that should be notified to a user; a message storage unit that stores at least one message indicating the content of the abnormality occurring in the device to be notified to the user in response to the occurrence of the abnormality, in association with the corresponding error code information; and a message notification unit that, when it is determined that the error code information included in the acquired error notification information is error code information that identifies the content of the abnormality to be notified to a user, selects message information corresponding to the acquired error code information from the at least one message information stored in the message storage unit, and transmits the selected message information to a terminal device carried by the user. Effect of the Invention

[0007] According to the present disclosure, when the message notification unit determines that the error code information transmitted from the device management server is error code information that identifies the content of the abnormality to be notified to the user, the message notification unit selects message information corresponding to the acquired error code information from at least one piece of message information that indicates the content of the abnormality that has occurred in the device stored in the message storage unit, and transmits the selected message information to the terminal device carried by the user. As a result, when an abnormality occurs in the device, the message information that indicates the content of the abnormality that has occurred in the device is transmitted to the terminal device carried by the user. Therefore, compared to the case where the user is simply notified of error code information, for example, the user can quickly grasp the content of the abnormality that has occurred in the device. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic configuration diagram of a device management support system according to a first embodiment of the present disclosure. [Diagram 2] FIG. 1 is a block diagram showing a hardware configuration of a device management support system according to a first embodiment. [Diagram 3] FIG. 1 is a block diagram showing a functional configuration of a part of a device management support system according to a first embodiment. [Figure 4] FIG. 1 is a diagram showing an example of information stored in a device state storage unit 231 according to the first embodiment. [Diagram 5] FIG. 1A is a diagram showing an example of information stored in an error code storage unit according to the first embodiment, and FIG. 1B is a diagram showing an example of information stored in a message storage unit according to the first embodiment. [Figure 6] FIG. 1 is a sequence diagram showing an operation of the device management support system according to the first embodiment. [Figure 7] FIG. 13 is a diagram showing an example of an error notification image displayed on a display unit of the terminal device according to the first embodiment; [Figure 8] FIG. 13 is a diagram showing an example of a graph display operation screen image displayed on a display unit of a terminal device according to the first embodiment; [Figure 9] FIG. 1 is a sequence diagram showing an operation of the device management support system according to the first embodiment. [Figure 10] 1 is a flowchart showing an example of the flow of a device management support process executed by a cloud server according to the first embodiment. [Figure 11] FIG. 11 is a block diagram showing a functional configuration of a device management support system according to a second embodiment. [Figure 12] FIG. 11 is a diagram for explaining the operation of an error occurrence status estimation unit according to the second embodiment; [Figure 13] FIG. 11 is a sequence diagram showing the operation of the device management support system according to the second embodiment. [Figure 14] FIG. 11 is a sequence diagram showing the operation of the device management support system according to the second embodiment. [Figure 15] 11 is a flowchart showing an example of the flow of a device management support process executed by a cloud server according to a second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (Embodiment 1) Hereinafter, the device management support device according to the embodiment of the present disclosure will be described with reference to the drawings. For example, as shown in FIG. 3, the device management support device V1 according to the present embodiment is realized in, for example, a cloud server 1, and includes an error notification acquisition unit 111 that acquires error notification information including error code information for identifying the content of the abnormality occurring in the device, which is transmitted from a device management server that manages the state of the device 4 when an abnormality occurs in the device, an error determination unit 112 that determines whether the error code information included in the acquired error notification information is error code information for identifying the content of the abnormality to be notified to the user, a message storage unit 132 that stores at least one message information representing the content of the abnormality occurring in the device to be notified to the user when an abnormality to be notified to the user occurs, in association with the corresponding error code information, and a message notification unit 113 that selects message information corresponding to the acquired error code information from the at least one message information stored in the message storage unit 132 when it is determined that the error code information included in the acquired error notification information is error code information for identifying the content of the abnormality to be notified to the user, and transmits the selected message information to a terminal device held by the user.

[0010] As shown in FIG. 1, the device management support system according to the present embodiment includes a cloud server 1, a device management server 2 that manages the state of a device 4, a terminal device 3 owned by a user of the device 4, and a terminal device 5 owned by a service provider that provides a maintenance service for the device 4. The device 4 is connected to a local network NW2 constructed in a building where the user lives. The local network NW2 is, for example, a wired LAN (Local Area Network) or a wireless LAN, and is connected to a wide area network NW1 via a router 82 and a data circuit-terminating device 81. The data circuit-terminating device 81 is a modem, a gateway, or the like. This allows the device 4 to communicate with the device management server 2 via the local network NW2, the router 82, the data circuit-terminating device 81, and the wide area network NW1. The cloud server 1 can communicate with the device management server 2 via the wide area network NW1, and the terminal devices 3 and 5 and the cloud server 1 can communicate with each other via the wide area network NW1.

[0011] The device 4 is, for example, a water heater, an air conditioner, etc., and is connected to the local network NW2. The device 4 periodically generates device status information indicating the status of the device 4, and transmits the information to the device management server 2 via the local network NW2 and the wide area network NW1.

[0012] 2, the device management server 2 includes a CPU (Central Processing Unit) 201, a main memory unit 202, an auxiliary memory unit 203, a communication unit 206, a clock unit 208, and a bus 209 connecting these units to each other. The CPU 201 is, for example, a multi-core processor. The main memory unit 202 has a volatile memory and is used as a working area for the CPU 201. The auxiliary memory unit 203 is composed of a large-capacity non-volatile memory and stores programs for realizing various functions of the device management server 2. The communication unit 206 is connected to the wide area network NW1. The clock unit 208 has, for example, a real-time clock.

[0013] The CPU 201 reads out the program stored in the auxiliary storage unit 203 into the main storage unit 202 and executes it, thereby functioning as a device status acquisition unit 211, an error detection unit 212, an error notification unit 213, and a device information notification unit 214, as shown in Fig. 3. The auxiliary storage unit 203 shown in Fig. 2 also has a device status storage unit 231 that stores device status information indicating the status of the device 4, as shown in Fig. 3. The device status storage unit 231 stores multiple types of device status information acquired from the device 4 for each device 4, in association with date and time information indicating the date and time when the device status information was acquired, device identification information that identifies the device 4, and model information indicating the model of the device 4, as shown in Fig. 4, for example. 4, the model of device 4 identified by device identification information "IDE[0]" is "CL[0]", and the device status information acquired on "2023 / 1 / 1" indicates that the corresponding values ​​of parameters "dataA1", "dataA2", ..., "dataA5", ... are "FALSE", "18", "-18", "24.5", "143748", .... Here, "FALSE" indicates, for example, that the acquired status is invalid or cannot be measured by device 4.

[0014] Returning to FIG. 3, when the device status acquisition unit 211 acquires the device status information periodically transmitted from the device 4, the device status acquisition unit 211 stores the acquired device status information in the device status storage unit 231 in association with date and time information indicating the date and time when the device status information was acquired, which is timed by the clock unit 208, the device identification information and the model information of the device 4. The error detection unit 212 refers to the device status information stored in the device status storage unit 231 and determines whether any of the parameters indicated by the device status information exceeds a preset allowable range. Then, when the error detection unit 212 determines that any of the parameters indicated by the device status information exceeds the above-mentioned allowable range, it determines that an abnormality has occurred in the device 4 and identifies an error code that identifies the content of the abnormality that has occurred. The error notification unit 213 generates error notification information including error code information indicating the identified error code and transmits it to the cloud server 1. When the device information notification unit 214 acquires the device information request information transmitted from the cloud server 1, it identifies, based on the search condition information included in the acquired graph request information, the device status information, device identification information, model information, and date and time information that match the search conditions indicated by the search condition information from the device status information stored in the device status storage unit 231. Then, the device information notification unit 214 generates device information including the identified device status information, device identification information, model information, and date and time information, and transmits it to the cloud server 1.

[0015] The terminal device 3 is, for example, a smartphone, and includes a CPU 301, a main memory unit 302, an auxiliary memory unit 303, a display unit 304, an input unit 305, a communication unit 306, and a bus 309 that connects them to each other, as shown in FIG. 2. The main memory unit 302 has a volatile memory such as a RAM (Random Access Memory), and is used as a work area for the CPU 301. The auxiliary memory unit 303 is a non-volatile memory such as a semiconductor flash memory, and stores programs for the CPU 301 to execute various processes. The display unit 304 is a display device such as a liquid crystal display or an organic EL (Electro-Luminescence) display. The input unit 305 is, for example, a transparent touch pad that is placed on the display unit 204. The communication unit 306 is connected to the wide area network NW1, and transmits information transferred from the CPU 301 to the terminal device 5 via the wide area network NW1, and transfers information acquired from the cloud server 1 via the wide area network NW1 to the CPU 301.

[0016] The CPU 301 reads out the program stored in the auxiliary storage unit 303 into the main storage unit 302 and executes it, thereby functioning as a message acquisition unit 311, a display control unit 312, and an error information notification unit 313, as shown in FIG. 3. When the message acquisition unit 311 acquires message information transmitted from the cloud server 1, indicating a message indicating the contents of an abnormality occurring in the device to be notified to the user when an abnormality to be notified to the user occurs, the message acquisition unit 311 notifies the acquired message information to the display control unit 312 and the error information notification unit 313. When the display control unit 312 is notified of the message information from the message acquisition unit 311, the display control unit 312 forms an error notification image for notifying the user that an abnormality has occurred in the device 4 based on the notified message information, and causes the display unit 304 to display the image. When the user performs an error notification operation on the input unit 305 to notify the above-mentioned service provider that an abnormality has occurred in the device 4, for example, the error information notification unit 313 generates error notification information including error code information, which will be described later, included in the above-mentioned message information, in response to the operation, and transmits the error notification information to the terminal device 5.

[0017] The terminal device 5 is, for example, a personal computer, and includes a CPU 501, a main memory unit 502, an auxiliary memory unit 503, a display unit 504, an input unit 505, a communication unit 506, and a bus 509 connecting them to each other, as shown in FIG. 2. The main memory unit 502 has a volatile memory and is used as a work area of ​​the CPU 501. The auxiliary memory unit 503 is composed of a non-volatile memory such as a ROM (Read Only Memory), an SSD (Solid State Drive), and an HDD (Hard Disk Drive), and stores programs for the CPU 501 to execute various processes. The display unit 504 is a display device such as a liquid crystal display or an organic EL display. The input unit 505 is a key input device such as a keyboard. The communication unit 506 is connected to the wide area network NW1, and transmits information transferred from the CPU 501 to the cloud server 1 via the wide area network NW1, and transfers information acquired from the cloud server 1 and the terminal device 3 via the wide area network NW1 to the CPU 501.

[0018] The CPU 501 reads out the program stored in the auxiliary storage unit 503 into the main storage unit 502 and executes it, thereby functioning as an error information acquisition unit 511, a display control unit 512, a graph request unit 513, and a graph acquisition unit 514, as shown in FIG. 3. When the error information acquisition unit 511 acquires error notification information transmitted from the terminal device 3, it notifies the display control unit 512 of error code information included in the acquired error notification information. When the display control unit 512 is notified of the error code information from the error information acquisition unit 511, it forms an error notification image for notifying the service provider that an abnormality has occurred in the device 4 used by the user based on the notified error code information, and causes the display unit 504 to display the image. When the graph request unit 513 performs a graph display operation for causing the cloud server 1 to display an equipment status display graph showing the status of the equipment 4 used by the user on the display unit 504 of the terminal device 5, it generates graph request information in response to the graph request and transmits it to the cloud server 1. Here, the graph request information includes search condition information indicating search conditions when searching for device status information for generating the above-mentioned device status display graph from among the device status information indicating the status of the device 4 managed by the device management server 2. In the graph display operation, the service provider inputs, for example, device identification information of the device 4 used by the user, period information indicating a period corresponding to the past state of the device 4 to be displayed in the graph, model information of the device 4, etc., to the input unit 505. Then, the graph request unit 513 generates graph request information including search condition information such as the device identification information, period information, and model information input via the input unit 505, and transmits it to the cloud server 1. The graph acquisition unit 514 acquires the graph information transmitted from the cloud server 1 by transmitting the above-mentioned graph request information to the cloud server 1, and notifies the display control unit 512 of the acquired graph information. Then, the display control unit 512 forms a status notification image including a graph image indicating the state transition of the device 4 based on the graph information notified from the graph acquisition unit 514, and displays it on the display unit 504.

[0019] Returning to FIG. 2, the cloud server 1 includes a CPU 101, a main memory unit 102, an auxiliary memory unit 103, a communication unit 106, and a bus 109 that interconnects these. The CPU 101 is, for example, a multi-core processor. The main memory unit 102 has a volatile memory and is used as a working area for the CPU 101. The auxiliary memory unit 103 is composed of a large-capacity non-volatile memory and stores programs for realizing various functions of the cloud server 1. The communication unit 106 is connected to a wide area network NW1.

[0020] The CPU 101 reads out the program stored in the auxiliary storage unit 103 into the main storage unit 102 and executes it, thereby realizing the device management support device V1 that functions as an error notification acquisition unit 111, an error determination unit 112, a message notification unit 113, a graph request acquisition unit 114, a device information acquisition unit 115, a graph generation unit 116, and a graph notification unit 117, as shown in Fig. 3. The auxiliary storage unit 103 shown in Fig. 2 also has an error code storage unit 131, a message storage unit 132, and a device status storage unit 133, as shown in Fig. 3. The error code storage unit 131 stores, in association with each other, error code information that identifies the content of an abnormality to be notified to the user and notification necessity information that specifies whether or not message information for notifying that an abnormality has occurred in the device 4 is to be sent to the terminal device 3 held by the user, as shown in Fig. 5(A), for example. In the example shown in Figure 5 (A), if the error code information included in the error notification information obtained from the equipment management server 2 indicates "E01", "E02", or "E04", message information is sent to the terminal device 3, and if the error code information indicates "E03", message information is not sent to the terminal device 3.

[0021] 5(B), for example, the message storage unit 132 stores a plurality of pieces of message information indicating the contents of the abnormality occurring in the device 4 to be notified to the user in the case where an abnormality that should be notified to the user occurs in the device 4, in association with the corresponding error code information. The message storage unit 132 also stores the message information in association with URL information indicating a Uniform Resource Locator (URL) including a domain name to which the terminal device 5 belongs. The device status storage unit 133 extracts device status information, device identification information, model information, and date and time information included in the device information transmitted from the device management server 2, and stores the extracted device status information, device identification information, model information, and date and time information in association with each other.

[0022] Returning to Fig. 3, when the error notification acquisition unit 111 acquires error notification information transmitted from the device management server 2, it extracts error code information contained in the acquired error notification information and notifies the error determination unit 112. When the error notification acquisition unit 111 notifies the error code information, the error determination unit 112 determines whether or not error code information matching the notified error code information is present among the error code information stored in the error code storage unit 131, and when it determines that the error code information is present, it refers to notification necessity information corresponding to the error code information and determines whether or not the error code information is an error code information that identifies the content of an abnormality that should be notified to the user. Then, when the error determination unit 112 determines that the error code information is an error code information that identifies the content of an abnormality that should be notified to the user, it notifies the message notification unit 113 of the error code information.

[0023] When the message notification unit 113 is notified of error code information from the error determination unit 112, it selects message information corresponding to the notified error code information from the message information stored in the message memory unit 132, and transmits the selected message information to the terminal device 3.

[0024] When the graph request acquisition unit 114 acquires the above-mentioned graph request information, it notifies the device information acquisition unit of the search condition information included in the acquired graph request information. When the device information acquisition unit 115 is notified of the search condition information, it generates device information request information including the notified search condition information and transmits it to the device management server 2. In this way, the device information acquisition unit 115 acquires device information transmitted from the device management server 2, including device status information searched and selected based on the search condition information. When the device information acquisition unit 115 acquires the device information, it extracts the device status information, device identification information, model information, and date and time information included in the acquired device information, and stores the extracted device status information, device identification information, model information, and date and time information in the device status storage unit 133 in association with each other.

[0025] The graph generating unit 116 generates a device status display graph using the device status information stored in the device status storage unit 133. Then, the graph generating unit 116 notifies the graph information indicating the generated device status display graph to the graph notifying unit 117. The graph notifying unit 117 transmits the notified graph information to the terminal device 5.

[0026] Next, the operation of the device monitoring support system according to the present embodiment will be described with reference to FIG. 6 to FIG. 9. Here, it is assumed that the device management server 2 executes a process in parallel to store the acquired device status information in the device status storage unit 231 in association with date and time information indicating the date and time when the device status information was acquired, every time the device management server 2 acquires device status information periodically transmitted from the device 4. First, it is assumed that an abnormality occurs in the device 4, and the device management server 2 determines that an abnormality occurs in the device 4 based on the device status information stored in the device status storage unit 231 (step S1). In this case, the device management server 2 specifies an error code that identifies the abnormality that has occurred (step S2), and generates error notification information including error code information indicating the specified error code (step S3). Next, the generated error notification information is transmitted from the device management server 2 to the cloud server 1 (step S4). On the other hand, it is assumed that the cloud server 1, upon acquiring the error notification information, determines that the error notification information is error code information that identifies the content of the abnormality to be notified to the user, by referring to notification necessity information corresponding to the error code information included in the acquired error notification information stored in the error code storage unit 131 (step S5). In this case, the cloud server 1 selects message information corresponding to the error code information from the message information stored in the message storage unit 132 (step S6). Then, the selected message information is transmitted from the cloud server 1 to the terminal device 3 (step S7).

[0027] On the other hand, when the terminal device 3 acquires the message information transmitted from the cloud server 1, it forms an error notification image for notifying the user that an abnormality has occurred in the device 4 based on the acquired message information, and displays the image on the display unit 304 (step S8). Here, the terminal device 3 displays an error notification image GA1, for example, as shown in FIG. 7, on the display unit 304. The error notification image GA1 includes a message image M11 for notifying the user that an error has occurred in the device 4, and a URL display image BU11 that links to a URL. Then, in a state in which the terminal device 3 is displaying the error notification image GA1, for example, as shown in FIG. 7, on the display unit 304, it is assumed that the user performs an error notification operation by touching a portion of the input unit 305, which is a touchpad, that corresponds to the URL display image BU11. In this case, as shown in FIG. 6, the terminal device 3 generates error notification information including error code information (step S9), and the generated error notification information is transmitted from the terminal device 3 to the terminal device 5 (step S10).

[0028] On the other hand, when the terminal device 5 acquires the error notification information transmitted from the terminal device 3, it forms an error notification image for notifying the service provider that an abnormality has occurred in the device 4 based on the error code information included in the acquired error notification information, and displays the image on the display unit 504 (step S11). Here, it is assumed that the service provider checks the error notification image displayed on the display unit 504 and performs a graph display operation for displaying, for example, a graph showing the history of the most recent state of the device 4 on the display unit 504. Here, the terminal device 5 displays, for example, a graph display operation image GA2 as shown in FIG. 8 on the display unit 504. This graph display operation image GA2 includes, for example, an input field B21 for inputting device identification information of the device 4 used by the user, and input fields B22 and B23 for inputting a period corresponding to the past state of the device 4 to be displayed on the graph. In addition, the graph display operation image GA2 includes a button image BU21 that is selected when input of the device identification information of the device 4 and the aforementioned period is completed. In this case, as shown in FIG. 6, the terminal device 5 generates graph request information including search condition information such as device identification information and period information input by the service provider via the input unit 505 (step S12), and the generated graph request information is transmitted from the terminal device 5 to the cloud server 1 (step S13).

[0029] On the other hand, when the cloud server 1 acquires the graph request information, it generates device information request information including the search condition information included in the acquired graph request information (step S14). After that, as shown in FIG. 9, the generated device information request information is transmitted from the cloud server 1 to the device management server 2 (step S15). On the other hand, when the device management server 2 acquires the device information request information transmitted from the cloud server 1, it identifies device status information, device identification information, model information, and date and time information that match the search condition indicated by the search condition information from among the device status information stored in the device status storage unit 231 based on the search condition information included in the acquired device information request information (step S16). Next, the cloud server 1 generates device information including the identified device status information, device identification information, model information, and date and time information (step S17), and the generated device information is transmitted from the device management server 2 to the cloud server 1 (step S18).

[0030] On the other hand, when the cloud server 1 acquires the device information transmitted from the device management server 2, it extracts the device status information, device identification information, model information, and date and time information included in the acquired device information, and stores the extracted device status information, device identification information, model information, and date and time information in the device status storage unit 133 in association with each other. Then, the cloud server 1 generates a device status display graph using the device status information stored in the device status storage unit 133 (step S19). Then, graph information showing the generated device status display graph is transmitted from the cloud server 1 to the terminal device 5 (step S20). On the other hand, when the terminal device 5 acquires the graph information transmitted from the cloud server 1, it forms a status notification image including a graph image showing the status transition of the device 4 based on the acquired graph information, and displays it on the display unit 504 (step S21).

[0031] Next, the device management support process executed by the cloud server 1 according to the present embodiment will be described with reference to FIG. 10. This device management support process is started, for example, when a program for executing the device management support process is started in the cloud server 1. First, the error notification acquisition unit 111 judges whether or not it has acquired error notification information transmitted from the device management server 2 (step S101). If the error notification acquisition unit 111 judges that it has not acquired error notification information (step S101: No), the process of step S105 described later is executed. On the other hand, if the error notification acquisition unit 111 judges that it has acquired error notification information (step S101: Yes), it extracts error code information included in the acquired error notification information and notifies the error determination unit 112. Then, when the error notification acquisition unit 111 notifies the error code information, the error determination unit 112 judges whether or not there is error code information that matches the notified error code information among the error code information stored in the error code storage unit 131 (step S102). Here, when the error determination unit 112 determines that there is no error code information that matches the notified error code information (step S102: No), the process of step S105 described later is executed. On the other hand, when the error determination unit 112 determines that there is error code information that matches the notified error code information (step S102: Yes), the error determination unit 112 refers to notification necessity information corresponding to the error code information and determines whether or not the error code information is error code information that identifies the contents of an abnormality that should be notified to the user (step S103). Here, when the error determination unit 112 determines that notification of the error code information is unnecessary (step S103: No), the process of step S105 described later is executed. On the other hand, it is assumed that the error determination unit 112 determines that the error code information is error code information that identifies the contents of an abnormality that should be notified to the user (step S103: Yes). In this case, the message notification unit 113 selects message information corresponding to the error code information included in the acquired error notification information from the message information stored in the message storage unit 132, and transmits the selected message information to the terminal device 3 (step S104).

[0032] Next, the graph request acquisition unit 114 judges whether or not the graph request information transmitted from the terminal device 5 has been acquired (step S105). If the graph request acquisition unit 114 judges that the graph request information has not been acquired (step S105: No), the process of step S101 is executed again. On the other hand, if the graph request acquisition unit 114 judges that the graph request information has been acquired (step S105: Yes), it notifies the device information acquisition unit of the search condition information included in the acquired graph request information. Then, the device information acquisition unit 115 generates device information request information including the notified search condition information and transmits it to the device management server 2 (step S106). Next, the device information acquisition unit 115 acquires device information including device status information that has been searched and selected based on the search condition information and transmitted from the device management server 2. Then, when the device information acquisition unit 115 acquires the device information, it extracts the device status information, device identification information, model information and date and time information contained in the acquired device information, and stores the extracted device status information, device identification information, model information and date and time information in the device status memory unit 133 in correspondence with each other (step S107).

[0033] Thereafter, the graph generating unit 116 generates a device status display graph using the device status information stored in the device status storage unit 133, and notifies the graph information indicating the generated device status display graph to the graph notifying unit 117. Then, the graph notifying unit 117 transmits the notified graph information to the terminal device 5 (step S108). Next, the process of step S101 is executed again.

[0034] As described above, in the cloud server 1 according to the present embodiment, when the message notification unit 113 determines that the error code information transmitted from the device management server 2 is error code information that identifies the content of the abnormality to be notified to the user, the message notification unit 113 selects message information corresponding to the acquired error code information from the message information that indicates the content of the abnormality that has occurred in the device stored in the message storage unit 132. Then, the message notification unit 113 transmits the selected message information to the terminal device 3 carried by the user. As a result, when an abnormality occurs in the device 4, the message information that indicates the content of the abnormality that has occurred in the device 4 is transmitted to the terminal device 3 carried by the user, so that the user can quickly grasp the content of the abnormality that has occurred in the device 4, compared to, for example, a case in which error code information is simply notified to the user.

[0035] Furthermore, according to this embodiment, if an abnormality requiring maintenance occurs in device 4, error code information is notified to the user in real time, so that the user of device 4 can quickly become aware of the abnormality in device 4.

[0036] Furthermore, according to this embodiment, the error determination unit 112 appropriately sets the notification necessity information stored in the error code storage unit 131, so that it is possible to set whether or not to notify the user of the device 4 of message information for each error code information. Therefore, only the message information necessary for the user can be transmitted to the terminal device 3. This makes it possible to reduce the number of unnecessary visits by the service provider to the user.

[0037] Moreover, in the cloud server 1 according to the present embodiment, the device information acquisition unit 115 transmits search condition information to the device management server 2, thereby acquiring device information including device status information selected by searching based on the search condition information from the device management server 2. Then, the graph generation unit 116 generates a device status display graph using the device status information included in the acquired device information. As a result, when an abnormality that requires maintenance occurs in the device 4, the service provider can check the device status display graph before visiting the user who uses the device 4, and can confirm or predict the date and time of the abnormality occurrence, the state of the abnormality occurrence, the content of the abnormality, and the like in advance, thereby reducing the number of visits to the user and the visit time. Therefore, the efficiency of the maintenance work can be improved.

[0038] (Embodiment 2) The equipment management support device of this embodiment differs from the equipment management support device of embodiment 1 in that it is equipped with an error occurrence situation estimation unit that estimates, from the equipment status information included in the acquired equipment information, whether or not an abnormality has occurred in the equipment 4 and error code information of the abnormality that occurs when an abnormality occurs in the equipment 4, using an error occurrence situation estimation model for estimating, from the equipment status information of the equipment 4, whether or not an abnormality has occurred in the equipment 4 and error code information that identifies the content of the abnormality that has occurred when an abnormality occurs in the equipment 4.

[0039] The device management support system according to this embodiment has the same configuration as the device management support system described in the first embodiment, and includes a cloud server 2001, a device management server 2, and terminal devices 3 and 2005, as shown in Fig. 11. The hardware configurations of the cloud server 2001 and the terminal device 2005 are the same as those of the cloud server 1 and the terminal device 5 described in the first embodiment. Therefore, in the following description, the hardware configurations of the cloud server 2001 and the terminal device 2005 will be described using the reference numerals shown in Fig. 2.

[0040] In the terminal device 2005, the CPU 501 reads out the program stored in the auxiliary storage unit 503 into the main storage unit 502 and executes it, thereby functioning as an error information acquisition unit 511, a display control unit 512, a graph request unit 513, a graph acquisition unit 514, and an error certification information notification unit 2515. When the service provider checks the actual state of the device 4 used by the user, determines that an abnormality has occurred in the device 4, and performs an error certification operation to notify that the service provider has certified that an abnormality has occurred in the device 4, the error certification information notification unit 2515 generates error certification information including error code information identifying the abnormality that the service provider has certified as occurring in the device 4, and transmits it to the cloud server 1.

[0041] In the cloud server 2001, the CPU 101 reads out the programs stored in the auxiliary storage unit 103 into the main storage unit 102 and executes them to realize a device management support device V2 that functions as an error notification acquisition unit 111, an error determination unit 112, a message notification unit 113, a graph request acquisition unit 114, a device information acquisition unit 2115, a graph generation unit 116, a graph notification unit 117, an error occurrence status estimation unit 2118, an error certification information acquisition unit 2119, and a model generation unit 2120. In addition, the auxiliary storage unit 103 has an error code storage unit 131, a message storage unit 132, a device status storage unit 2133, and a model storage unit 2134.

[0042] The model storage unit 2134 stores error occurrence situation estimation model information indicating an error occurrence situation estimation model for estimating the presence or absence of an abnormality in the device 4 and error code information for identifying the content of the abnormality when an abnormality occurs in the device 4 from the device status information of the device 4. The error occurrence situation estimation model is, for example, a forward propagation type neural network. In this case, the model storage unit 2134 stores information indicating the structure of the neural network and information indicating weighting coefficients in the neural network. Here, the information indicating the structure of the neural network includes information indicating the number of nodes and the number of layers of the neural network, and weighting coefficients and activation functions corresponding to each node. For example, as shown in FIG. 12, the state estimation model is a state estimation model that calculates an expected value vector Vout having parameters dataA1(IN[0]), detaA2(IN[1]), ... indicating the state of the device 4 indicated by the device status information. When an device state vector Vin having elements such as dataAk(IN[k]) (k is a positive integer), etc. is input, an expected value vector Vout is calculated having elements such as expected values ​​of each of a plurality of types of error occurrence situations set in advance. In the example shown in FIG. 12, the error occurrence status is classified into a plurality of types of statuses, such as "no error", an abnormality with an error code "E01", an abnormality with an error code "E02", and the like.

[0043] Returning to Fig. 11, when the error notification acquisition unit 111 acquires the error notification information transmitted from the device management server 2, it extracts the error code information included in the acquired error notification information and notifies the model generation unit 2120. When the error code information is notified from the error occurrence status estimation unit 2118, the error determination unit 112 determines whether or not there is error code information that matches the notified error code information among the error code information stored in the error code storage unit 131, and when it is determined that there is error code information, it refers to notification necessity information corresponding to the error code information and determines whether or not the error code information is error code information that identifies the content of an abnormality that should be notified to the user. Then, when the error determination unit 112 determines that the error code information is error code information that identifies the content of an abnormality that should be notified to the user, it notifies the message notification unit 113 of the error code information.

[0044] When a preset device information acquisition time arrives, the device information acquisition unit 2115 generates device information request information including search condition information for searching device status information at a preset estimation target time for all devices 4 used by the user, and transmits the generated device information to the device management server 2. Here, the device information acquisition time can be set to arrive periodically, for example, every few minutes to every few hours. The estimation target time can be set to the most recent date and time among the date and time information stored in the device status storage unit 231 of the device management server 2. In this way, the device information acquisition unit 2115 acquires device information including device status information at the estimation target time for all devices 4 used by the user, which is transmitted from the device management server 2. When acquiring the device information, the device information acquisition unit 2115 extracts device status information, device identification information, model information, and date and time information included in the acquired device information, and stores the extracted device status information, device identification information, model information, and date and time information in the device status storage unit 2133 in association with each other.

[0045] The error occurrence situation estimation unit 2118 estimates whether an abnormality occurs in the device 4 and error code information of the abnormality that occurs in the device 4 from the device status information stored in the device status storage unit 2133, using the error occurrence situation estimation model indicated by the error occurrence situation estimation model information stored in the model storage unit 2134. Specifically, the error occurrence situation estimation unit 2118 first generates an device status vector Vin having at least one parameter as an element, as shown in FIG. 12, from at least one parameter indicated by the device status information stored in the device status storage unit 2133. Then, the error occurrence situation estimation unit 2118 inputs the device status vector Vin to the above-mentioned error occurrence situation estimation model, and calculates the above-mentioned expected value vector Vout having as elements an expected value where no abnormality occurs and an expected value where an abnormality occurs that is identified by multiple types of preset error code information. Then, the error occurrence situation estimation unit 2118 specifies the error occurrence situation corresponding to the element with the highest expected value among the multiple elements of the calculated expected value vector Vout. 12, when no abnormality occurs, the value of element Q[0] of the expected value vector Vout is the highest. On the other hand, when abnormalities of error codes "E01", "E02", "E03", and "E04" occur, the values ​​of elements Q[1], Q[2], Q[3], and Q[4] are the highest, respectively. Furthermore, when the error occurrence status estimation unit 2118 estimates that an abnormality will occur in device 4, it notifies the error determination unit 112 of the error code information of the abnormality with the highest expected value.

[0046] When the error certification information acquisition unit 2119 acquires the error certification information transmitted from the terminal device 5, it extracts the error code information included in the acquired error certification information and notifies the model generation unit 2120 of the error code information. The model generation unit 2120 generates error occurrence situation estimation model information indicating an error occurrence situation estimation model based on the error code information notified from the error notification acquisition unit 111 or the error code information notified from the error certification information acquisition unit 2119. Here, the model generation unit 2120 identifies the device status information stored in the device status storage unit 2133 within the aforementioned estimation target period immediately preceding the time point at which the error code information is acquired. Then, the model generation unit 2120 generates a new error occurrence situation estimation model using the notified error code information and the identified device status information, and updates the error occurrence situation estimation model information stored in the model storage unit 2134 with the error occurrence situation estimation model information indicating the generated error occurrence situation estimation model. Specifically, the model generation unit 2120 first sets the expected value such that the expected value corresponding to the notified error code information among the expected values ​​constituting each element of the above-mentioned expected value vector is higher than the expected value corresponding to other labels. For example, the model generation unit 2120 sets the expected value of the notified error code information at which an abnormality occurs to a number greater than 0, and sets the expected value of the other error code information at which an abnormality occurs and the expected value of the other error code information at which an abnormality does not occur to "0". Then, the model generation unit 2120 calculates the error between the expected value vector calculated by the error occurrence situation estimation unit 2118 and the set expected value vector. Then, the model generation unit 2120 determines the weighting coefficient of the error occurrence situation estimation model by the error propagation method (backpropagation) method based on the calculated error. Then, the model generation unit 2120 updates the error occurrence situation estimation model information stored in the model storage unit 2134 with the error occurrence situation estimation model information indicating the determined weighting coefficient.

[0047] Next, the operation of the device monitoring support system according to the present embodiment will be described with reference to Figs. 13 and 14. In Figs. 13 and 14, the same processes as those in the first embodiment are denoted by the same reference numerals as those in Figs. 6 and 9. First, when the above-mentioned device information acquisition time arrives, the cloud server 2001 generates device information request information including search condition information for searching device status information for all devices 4 used by the user within the most recent, previously set, estimated target period (step S2001), and the generated device information request information is transmitted from the cloud server 2001 to the device management server 2 (step S2002). On the other hand, when the device management server 2 acquires the device status request information transmitted from the cloud server 2001, the device management server 2 identifies device status information, device identification information, model information, and date and time information that match the search condition indicated by the search condition information from among the device status information stored in the device status storage unit 231, based on the device identification information of the device 4 used by the user included in the acquired device information request information (step S2003). Next, the cloud server 2001 generates device information including the identified device status information, device identification information, model information and date and time information (step S2004), and the generated device information is transmitted from the device management server 2 to the cloud server 2001 (step S2005).

[0048] On the other hand, when the cloud server 2001 acquires the device information transmitted from the device management server 2, it extracts the device status information, device identification information, model information, and date and time information included in the acquired device information, and stores the extracted device status information, device identification information, model information, and date and time information in the device status storage unit 2133 in association with each other. Next, it is assumed that the cloud server 2001 estimates that an abnormality will occur in the device 4 from the device status information stored in the device status storage unit 2133 using the error occurrence situation estimation model indicated by the error occurrence situation estimation model information stored in the model storage unit 2134 (step S2006). In this case, it estimates the occurrence or non-occurrence and error code information of the abnormality that will occur if an abnormality occurs in the device 4. Then, it is assumed that the cloud server 2001 refers to the notification necessity information corresponding to the error code information included in the acquired error notification information stored in the error code storage unit 131, and determines that the error code information is error code information that identifies the content of the abnormality to be notified to the user (step S5). In this case, a series of processes from step S7 onwards are executed.

[0049] 14, it is assumed that an abnormality occurs in device 4 and a series of processes from steps S1 to S4 are executed. In this case, when cloud server 2001 acquires error notification information transmitted from device management server 2, it generates error occurrence situation estimation model information indicating an error occurrence situation estimation model based on error code information included in the acquired error notification information. Then, cloud server 2001 updates the error occurrence situation estimation model information stored in model storage unit 2134 with the generated error occurrence situation estimation model information (step S2007).

[0050] Also, it is assumed that the service provider checks the actual state of the device 4 used by the user, determines that an abnormality has occurred in the device 4, and performs an error certification operation to notify that the abnormality has been certified in the device 4. In this case, the terminal device 2005 generates error certification information including error code information that identifies the abnormality that the service provider has certified as occurring in the device 4 (step S2008), and the generated error certification information is transmitted from the terminal device 2005 to the cloud server 2001 (step S2009). On the other hand, when the cloud server 2001 acquires the error certification information transmitted from the terminal device 2005, it extracts error code information included in the acquired error certification information (step S2010). Next, the cloud server 2001 generates error occurrence situation estimation model information indicating an error occurrence situation estimation model based on the extracted error code information. Then, the cloud server 2001 updates the error occurrence situation estimation model information stored in the model storage unit 2134 with the generated error occurrence situation estimation model information (step S2011).

[0051] Next, the device management support process executed by the cloud server 2001 according to the present embodiment will be described with reference to FIG. 15. In FIG. 15, the same processes as those in the first embodiment are denoted by the same reference numerals as those in FIG. 10. First, the device information acquisition unit 2115 judges whether or not the preset device information acquisition time has arrived (step S2101). If the device information acquisition unit 2115 judges that the device information acquisition time has not yet arrived (step S2101: No), the process of step S105 is executed. On the other hand, if the device information acquisition unit 2115 judges that the device information acquisition time has arrived (step S2101: Yes), the device information acquisition unit 2115 generates device information request information including search condition information for searching for device status information within the most recent preset estimation target period for all devices 4 used by the user, and transmits the request information to the device management server 2 (step S2102). Next, the device information acquisition unit 115 acquires device information including device status information selected by searching based on the search condition information, which is transmitted from the device management server 2. Then, when the device information acquisition unit 115 acquires the device information, it extracts the device status information, device identification information, model information, and date and time information contained in the acquired device information, and stores the extracted device status information, device identification information, model information, and date and time information in the device status memory unit 2133 in association with each other (step S2103).

[0052] Thereafter, the error occurrence situation estimation unit 2118 uses the error occurrence situation estimation model indicated by the error occurrence situation estimation model information stored in the model storage unit 2134 to determine whether or not it has been estimated that an abnormality will occur in the device 4 from the device status information stored in the device status storage unit 2133 (step S2104). If the error occurrence situation estimation unit 2118 determines that it has estimated that the device 4 is normal (step S2104: No), processing from step S105 onwards, which will be described later, is executed. On the other hand, if the error occurrence situation estimation unit 2118 determines that it has estimated that an abnormality will occur in the device 4 (step S2104: Yes), it notifies the error determination unit 112 of error code information identifying the abnormality estimated to occur. Then, a series of processing from steps S102 to S108 is executed.

[0053] Next, the error notification acquisition unit 111 judges whether or not it has acquired error notification information transmitted from the device management server 2 (step S2105). If the error notification acquisition unit 111 judges that it has acquired error notification information (step S2105: Yes), the process of step S2108 described below is executed. On the other hand, if the error notification acquisition unit 111 judges that it has not acquired error notification information (step S2105: No), the error certification information acquisition unit 2119 judges whether or not it has acquired error certification information transmitted from the terminal device 2005 (step S2106). If the error certification information acquisition unit 2119 judges that it has not acquired error certification information (step S2106: No), the process of step S2101 is executed again. On the other hand, if the error certification information acquisition unit 2119 judges that it has acquired error certification information (step S2106: Yes), it extracts error code information included in the acquired error certification information (step S2107). Next, the model generation unit 2120 generates error occurrence situation estimation model information indicating an error occurrence situation estimation model based on the error code information notified by the error notification acquisition unit 111 or the extracted error code information. Then, the model generation unit 2120 updates the error occurrence situation estimation model information stored in the model storage unit 2134 with the generated error occurrence situation estimation model information (step S2108). After that, the process of step S2101 is executed again.

[0054] As described above, in the cloud server 2001 according to this embodiment, the error occurrence status estimation unit 2118 estimates whether an abnormality has occurred in the device 4 and error code information of the abnormality that occurs when an abnormality occurs in the device 4 from the device status information stored in the device status storage unit 2133, using the error occurrence status estimation model indicated by the error occurrence status estimation model information stored in the model storage unit 2134. This makes it possible to estimate the occurrence of an abnormality in the device 4 that has not been detected by the device management server 2, so that the user can quickly grasp the content of the abnormality that has occurred in the device 4.

[0055] Furthermore, according to this embodiment, it is possible to detect signs of an abnormality requiring maintenance in device 4 before such an abnormality occurs, and therefore it is possible to inform the user of the necessary measures for device 4 before device 4 completely stops.

[0056] Furthermore, when the error certification information is acquired by the error certification information acquisition unit 2119, the model generation unit 2120 according to this embodiment generates error occurrence situation estimation model information indicating an error occurrence situation estimation model, based on error code information included in the acquired error certification information. This allows the criterion for the service provider's abnormality determination of the device 4 when the service provider determines that an abnormality has occurred in the device 4 to be reflected in the estimation of whether or not an abnormality has occurred in the device 4 using the error occurrence situation estimation model, thereby improving the estimation accuracy of whether or not an abnormality has occurred in the device 4.

[0057] Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-mentioned embodiments. For example, in the second embodiment, the model storage unit 2134 may store error occurrence situation estimation model information indicating an error occurrence situation estimation model for estimating the presence or absence of an abnormality in the device 4 and error code information for identifying the content of the abnormality when an abnormality occurs in the device 4 based on the transition of the parameters indicated by the device status information of the device 4 during a past predetermined estimation target period. In this case, a recurrent neural network can be used as the error occurrence estimation model. Furthermore, when the above-mentioned device information acquisition time arrives, the device information acquisition unit 2115 generates device information request information including search condition information for searching for device status information within the most recent predetermined estimation target period for all devices 4 used by the user, and transmits the device information request information to the device management server 2. Here, the estimation target period is set to, for example, the most recent one month. As a result, the device information acquisition unit 2115 acquires device information including device status information for all devices 4 used by the user within the estimated target period, which is sent from the device management server 2, and extracts the device status information, device identification information, model information, and date and time information contained in the acquired device information, associates them with each other, and stores them in the device status memory unit 2133.

[0058] According to this configuration, since it is possible to estimate the occurrence of an abnormality in the device 4 based on the tendency of the transition of the state of the device 4 within the most recent estimation target period, it is possible to improve the accuracy of estimating the occurrence of an abnormality in the device 4.

[0059] In addition, the various functions of the cloud servers 1, 2001 and the terminal devices 3, 5, 2005 according to the present disclosure may be realized by software, firmware, or a combination of software and firmware. In this case, the software or firmware may be written as a program, and the program may be stored and distributed in a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc), or an MO (Magneto-Optical Disc), and the program may be read and installed in a computer to configure a computer capable of realizing each of the above-mentioned functions. In addition, when each function is realized by sharing the work between an OS (Operating System) and an application, or by cooperation between the OS and an application, only the parts other than the OS may be stored in the recording medium.

[0060] Furthermore, each program may be superimposed on a carrier wave and distributed via a network. For example, the program may be posted on a bulletin board (BBS, Bulletin Board System) on the network and distributed via the network. These programs may then be started and executed under the control of the OS in the same way as other application programs, thereby enabling the above-mentioned processing to be performed. [Industrial Applicability]

[0061] The present disclosure is suitable as a system for allowing a user to remotely manage a device. [Explanation of symbols]

[0062] 1,2001 Cloud server, 2 Device management server, 3,5,2005 Terminal device, 4 Device, 81 Data circuit terminating device, 82 Router, 101,201,301,501 CPU, 102,202,302,502 Main memory unit, 103,203,303,503 Auxiliary memory unit, 106,206,306,506 Communication unit, 108,208,310 Timer unit, 109,209,309 Bus, 111 Error notification acquisition unit, 112 Error judgment unit, 113 Message notification unit, 114 Graph request acquisition unit, 115,2115 Device information acquisition unit, 116,2116 Graph generation unit, 117 Graph notification unit, 131 Error code storage unit, 132 Message storage unit, 133,2133 Device status storage unit, 211 device status acquisition unit, 212 error detection unit, 213 error notification unit, 214 device status notification unit, 304, 504 display unit, 305, 505 input unit, 311 message acquisition unit, 312, 512 display control unit, 313 error information notification unit, 511 error information acquisition unit, 513 graph request unit, 514 graph acquisition unit, 2118 error occurrence status estimation unit, 2119 error certification notification information acquisition unit, 2120 model generation unit, 2134 model storage unit, 2515 error certification information notification unit, B21, B22, B23 input field image, BU11 URL display image, BU21 button image, GA1 error notification image, GA2 graph display operation screen image, M11 message image, NW1 wide area network, NW2 local network, V1, V2 device management support device

Claims

1. an error notification acquisition unit that acquires error notification information including error code information for identifying the content of the abnormality occurring in the device, the error notification information being transmitted from a device management server that manages the state of the device when an abnormality occurs in the device; an error determination unit that determines whether the error code information included in the acquired error notification information is error code information that identifies the content of an abnormality that should be notified to a user; a message storage unit that stores at least one message indicating the content of the abnormality occurring in the device to be notified to the user when an abnormality that should be notified to the user occurs, in association with a corresponding error code; a message notification unit which, when it is determined that the error code information included in the acquired error notification information is error code information that identifies the content of an abnormality to be notified to a user, selects message information corresponding to the acquired error code information from the at least one piece of message information stored in the message storage unit, and transmits the selected message information to a terminal device carried by the user. Equipment management support device.

2. a graph request acquisition unit that acquires graph request information including search condition information indicating search conditions for searching for device status information for generating a device status display graph representing the status of the device from device status information indicating the status of the device managed by the device management server; a device information acquiring unit that acquires device information including device status information searched and selected based on the search condition information from the device management server by transmitting the search condition information to the device management server; a graph generator that generates the device status display graph by using the device status information included in the acquired device information, The device management support device according to claim 1 .

3. a device information acquiring unit that acquires device information including device status information indicating a status of the device managed by a device management server from the device management server that manages a status of the device; an error occurrence status estimation unit that estimates, from the device status information included in the acquired device information, whether or not an abnormality has occurred in the device and the error code information of the abnormality that will occur when an abnormality occurs in the device, using an error occurrence status estimation model for estimating, from the device status information, whether or not an abnormality has occurred in the device and error code information that identifies the content of the abnormality that will occur when an abnormality occurs in the device; a message storage unit that stores at least one message indicating the content of the abnormality occurring in the device to be notified to the user when an abnormality that should be notified to the user occurs, in association with a corresponding error code; a message notification unit which, when it is estimated that an abnormality will occur in the device and it is determined that the estimated error code information is error code information that identifies the content of the abnormality to be notified to a user, selects message information corresponding to the acquired error code information from the at least one piece of message information stored in the message storage unit, and transmits the selected message information to a terminal device carried by the user. Equipment management support device.

4. a model storage unit that stores error occurrence situation estimation model information indicating the error occurrence situation estimation model; an error notification acquisition unit that acquires error notification information including the error code information transmitted from the device management server when an abnormality occurs in the device; a model generation unit that, when the error notification information is acquired, generates error occurrence situation estimation model information indicating the error occurrence situation estimation model based on the error code information included in the acquired error notification information, and updates the error occurrence situation estimation model information stored in the model storage unit with the generated error occurrence situation estimation model information; the error occurrence situation estimation unit estimates, from the device status information included in the acquired device information, whether or not an abnormality has occurred in the device and, when an abnormality occurs in the device, the error occurrence situation estimation unit estimates the error code information of the abnormality, using the error occurrence situation estimation model indicated by the updated error occurrence situation estimation model information stored in the model storage unit. The device management support device according to claim 3.

5. An error determination information acquisition unit is further provided for acquiring error determination information transmitted from a terminal device, the error determination information including error code information for identifying the abnormality that has been determined to have occurred in the device based on the state of the device, When the error determination information is acquired, the model generation unit generates error occurrence situation estimation model information indicating the error occurrence situation estimation model based on the error code information included in the acquired error determination information. The device management support device according to claim 4.

6. a first terminal device carried by a user; an error notification acquisition unit that acquires error notification information including error code information for identifying the content of the abnormality occurring in the device, the error notification information being transmitted from a device management server that manages the state of the device when an abnormality occurs in the device; an error determination unit that determines whether the error code information included in the acquired error notification information is error code information that identifies the content of an abnormality that should be notified to a user; a message storage unit that stores at least one message indicating the content of the abnormality occurring in the device to be notified to the user when an abnormality that should be notified to the user occurs, in association with a corresponding error code; a message notification unit which, when it is determined that error code information included in the acquired error notification information is error code information that identifies the content of an abnormality to be notified to a user, selects message information corresponding to the acquired error code information from the at least one piece of message information stored in the message storage unit, and transmits the selected message information to the first terminal device. Equipment management support system.

7. A second terminal device possessed by the service provider; a graph request acquisition unit that acquires graph request information including search condition information indicating search conditions for searching for device status information for generating a device status display graph representing the status of the device from device status information indicating the status of the device managed by the device management server, the device status information being transmitted from the second terminal device; a device information acquisition unit that generates device information request information including the search condition information included in the graph request information, and transmits the generated device information request information to the device management server, thereby acquiring device information including the device status information that is searched and selected based on the search condition information and transmitted from the device management server; a graph generating unit that generates the device status display graph by using the device status information included in the acquired device information; and a graph notification unit that transmits graph information indicating the generated device status display graph to the second terminal device. The device management support system according to claim 6.

8. A step in which a device management support device acquires error notification information including error code information for identifying the content of the abnormality occurring in the device, the error notification information being transmitted from a device management server that manages the state of the device when an abnormality occurs in the device; a step of determining whether the error code information included in the acquired error notification information is error code information that identifies the content of an abnormality that should be notified to a user, by the device management support device; when the equipment management support device determines that the error code information included in the acquired error notification information is error code information that identifies the content of the abnormality to be notified to the user, the equipment management support device selects message information corresponding to the acquired error code information from among at least one message information stored in a message storage unit that stores at least one message information indicating the content of the abnormality that has occurred in the equipment to be notified to the user in the event of an abnormality to be notified to the user in correspondence with the corresponding error code information, and transmits the selected message information to a first terminal device carried by the user. Equipment management support method.

9. acquiring graph request information including search condition information indicating search conditions for searching for device status information for generating a device status display graph representing the status of the device from device status information indicating the status of the device managed by the device management server, the graph request information being transmitted from a second terminal device possessed by a service provider; generating device information request information including the search condition information included in the graph request information, and transmitting the request information to the device management server, thereby acquiring device information including the device status information searched and selected based on the search condition information, which is transmitted from the device management server; generating the device status display graph using the device status information included in the acquired device information; and transmitting graph information indicating the generated device status display graph to the second terminal device. The device management support method according to claim 8.

10. Computer, an error notification acquisition unit that acquires error notification information including error code information for identifying the content of the abnormality occurring in the device, the error notification information being transmitted from a device management server that manages the state of the device when an abnormality occurs in the device; an error determination unit that determines whether or not the error code information included in the acquired error notification information is error code information that identifies the content of an abnormality that should be notified to a user; a message notification unit which, when it is determined that error code information included in the acquired error notification information is error code information identifying the content of an abnormality to be notified to a user, selects message information corresponding to the acquired error code information from the at least one message information stored in a message storage unit which stores at least one message information indicating the content of an abnormality which has occurred in the device and which is to be notified to a user when an abnormality to be notified to a user occurs, in correspondence with the corresponding error code information, and transmits the selected message information to a terminal device carried by the user; A program to function as a

Citation Information

Patent Citations

  • Data processor, service support system, data processing method, and program

    JP2021086456A